WO2014068792A1 - アクセス制御方法およびアクセス制御システム - Google Patents
アクセス制御方法およびアクセス制御システム Download PDFInfo
- Publication number
- WO2014068792A1 WO2014068792A1 PCT/JP2012/078644 JP2012078644W WO2014068792A1 WO 2014068792 A1 WO2014068792 A1 WO 2014068792A1 JP 2012078644 W JP2012078644 W JP 2012078644W WO 2014068792 A1 WO2014068792 A1 WO 2014068792A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- terminal
- business
- information
- owner
- access control
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
- G06F21/316—User authentication by observing the pattern of computer usage, e.g. typical user behaviour
-
- 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
- G06Q10/063—Operations research, analysis or management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/107—Network architectures or network communication protocols for network security for controlling access to devices or network resources wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2111—Location-sensitive, e.g. geographical location, GPS
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2115—Third party
Definitions
- the present invention relates to an access control technique using schedule information and position information.
- Patent Document 1 it is determined whether or not the user's actual behavior matches a pre-registered schedule.
- Security control based on access regulations for applications and data according to a predetermined security pattern is realized.
- Patent Document 1 When the technology disclosed in Patent Document 1 is used, appropriate access control is possible using the user location information and the location information registered in the schedule.
- this technique is based on the premise that the schedule is correctly registered, but the schedule may be changed, and the user is not always engaged in business according to the registered schedule.
- the schedule may be changed, for example, the user forgets to register the schedule, the schedule is extended beyond the schedule, or the schedule is completed ahead of schedule.
- the technique as disclosed in Patent Document 1 there is a possibility that access may be denied even when access is made from an appropriate time and place, thus reducing the convenience for the user. I will let you.
- An object of the present invention is to realize the prevention of information leakage while ensuring the convenience of the user even when the registered schedule and the actual action are different.
- the present invention is an access control method for a terminal connected to a management device having a processor and a memory, wherein the management device stores position information corresponding to the time of the owner of the terminal in a schedule storage unit.
- the management device estimates a current job status of the owner of the terminal from history information of a person related to the owner of the terminal, and sends it to the terminal.
- FIG. 1 is a block diagram illustrating an example of an access control system according to a first embodiment of this invention.
- FIG. It is a block diagram which shows a 1st Example of this invention and shows an example of a management apparatus. It is a figure which shows the 1st Example of this invention and shows the model of the process performed with an access control system. It is a block diagram which shows a 1st Example of this invention and shows an example of a process in the model of the process performed with an access control system. It is a figure which shows the 1st Example of this invention and shows an example of the data structure of an employee information table. It is a figure which shows the 1st Example of this invention and shows an example of the data structure of a work schedule list
- FIG. 5 is a first half of a flowchart illustrating an example of processing performed by the position information-business schedule contradiction resolution unit according to the first embodiment of this invention.
- FIG. 10 is a second half of a flowchart illustrating an example of processing performed by the position information-business schedule contradiction resolution unit according to the first embodiment of this invention.
- It is a block diagram which shows the 2nd Example of this invention and shows the structure of a management apparatus.
- It is a flowchart which shows a 2nd Example of this invention and shows an example of the process performed in a positional information-business schedule inconsistency resolution part.
- It is a block diagram which shows the 3rd Example of this invention and shows an example of the management apparatus.
- FIGS. 2A and 2B The principle of the present invention will be described with reference to the model diagram of the access control system shown in FIGS. 2A and 2B.
- 2A is a diagram showing a model of processing performed in the computer system of the present invention
- FIG. 2B is a diagram showing an example of processing performed in the access control system.
- FIGS. 2A and 2B illustrate three embodiments among a plurality of embodiments that solve the above-described problems of the present invention.
- Hitachi Taro, Hitachi Jiro, and Hitachi Saburo are employees belonging to the same company, each employee is related in business, and each employee (user) is one each. Assume that terminals 10 to 12 equipped with the access control function realized in the present invention are held.
- Hitachi Taro makes a request for starting a business application on the terminal 10, the access control realized by the present invention is executed, and is there any inconsistency between the location information initially registered in the business schedule and the location information of Hitachi Taro? Judge whether or not. As mentioned above, Hitachi Taro has a contradiction between business schedule information and position information. The present invention performs strict access control even in such a case. The outline of the three embodiments will be described below.
- the management device 2000 considers that the position information of the terminal is close and the person related to the job is performing the same job as the target person when there is a contradiction between the job schedule and the position information.
- the business context of Hitachi Taro is estimated using the business schedule information of the relevant employee.
- the terminal 10 acquires an application policy to be applied to Hitachi Taro from the application policy correspondence table 34 in FIG. 2B, and performs file access control according to the policy.
- the management apparatus 2000 when there is a contradiction between the work schedule and the position information, the management apparatus 2000 resembles the change pattern of the current position information of the user or the past of people related to the work. Search location information history. Then, the management apparatus 2000 estimates the business context corresponding to the retrieved location information history as the current user business context.
- Hitachi Taro stays at the Yokohama 1st Building for a certain period of time to attend the mobile regular meeting.
- Hitachi Jiro who is related in business, was staying in the first building in Yokohama on a meeting on July 21st.
- the business context “in-house” applied to Hitachi Jiro, whose position information change pattern is similar, is estimated as the business context of Hitachi Taro on July 28.
- the terminal 10 of Hitachi Taro acquires the applied policy name applied to Hitachi Taro from the applied policy correspondence table 34 using the estimated business context, and performs access control of the terminal 10 according to the applied policy name.
- the management device 2000 stores what contradiction has occurred between the business schedule and the user's location information for each user's schedule, and there is a contradiction between the business schedule and the location information.
- the current business context is estimated from the schedule contradiction tendency using the past contradiction history.
- the mobile regular meeting with 7/28 Hitachi Taro participated, the scheduled time was extended and the meeting was continued, and there was a discrepancy between the registered schedule and the user's location information. Arise.
- the application policy applied to the terminal 10 of Hitachi Taro is acquired from the application policy correspondence table using the estimated business context, and access control is performed according to the application policy.
- the present invention allows the current business of the person related to the business when the location information of the terminal 10 and the location information in the business schedule information are determined to be different places.
- Access control including a position information-work schedule conflict resolution technique for resolving a conflict between the position information of the terminal 10 and the work schedule information using the context information, the past work context information, or the contradiction history is performed.
- FIG. 1A and 1B show the configuration of an access control system described as the first embodiment.
- FIG. 1A is a block diagram showing an example of a computer system to which the present invention is applied.
- FIG. 1B is a block diagram illustrating an example of a management apparatus that configures the access control system.
- the access control system includes a computer system including at least two or more terminals 1000, a management device 2000, a radio base station 100, and a public line (or the Internet) 200.
- the terminal 1000 is a mobile terminal such as a smartphone or a tablet, and has a hardware configuration of an auxiliary storage device 1200, a main storage device 1300, a CPU 1400, a touch panel display 1500, for example, a location information acquisition device 1600 such as a GPS, a wireless network interface. 1700, a proximity communication device 1800, a camera 1900, and a bus (or interconnect) 1100 connecting these devices.
- a location information acquisition device 1600 such as a GPS, a wireless network interface.
- a proximity communication device 1800 such as a GPS, a wireless network interface.
- a camera 1900 and a bus (or interconnect) 1100 connecting these devices.
- wireless network interface 1700 When the wireless network interface 1700 connects to the public line 200, data communication is performed via the wireless base station 100.
- the auxiliary storage device 1200 defines an application policy correspondence table 1210 in which an application policy corresponding to a business context is described, an application policy 3100, a private application 3110, business data 3120, and an access permission that defines various devices included in the terminal. It has a policy definition table 1220 in which a policy is described, a business context 1230 for storing business context data, and an applied policy 1240 for storing an applied policy name. Further, the business application 3100 and the private application 3110 are stored in the auxiliary storage device 1200 and loaded into the main storage device 1300 when executed. Note that the business application 3100 and the private application 3110 are collectively referred to as an application.
- the main storage device 1300 includes a business context determination request unit 1310 that makes a business context determination request to the management device 2000, an application policy determination unit 1320 that determines a policy to be applied from the business context, and an application according to the applied policy.
- the CPU 1400 reads an application activation control unit 1330 that performs activation control and data access control, a basic data acquisition unit 1340 that acquires time information and position information, and an OS 1350 that is a base for executing these processing units. Is executed.
- the functional units of the business context determination request unit 1310, the application policy determination unit 1320, the application activation control unit 1330, and the basic data acquisition unit 1340 are loaded into the main storage device 1300 as programs.
- the CPU 1400 operates as a functional unit that realizes a predetermined function by operating according to a program of each functional unit.
- the CPU 1400 functions as the basic data acquisition unit 1340 by operating according to the basic data acquisition program. The same applies to other programs.
- the CPU 1400 also operates as a functional unit that implements each of a plurality of processes executed by each program.
- a computer and a computer system are an apparatus and a system including these functional units.
- Information such as programs and tables for realizing each functional unit is stored in a storage device such as a nonvolatile semiconductor memory, hard disk drive, SSD (Solid State Drive) constituting the auxiliary storage device 1200, or an IC card, SD card, DVD, or the like. Can be stored in any computer-readable non-transitory data storage medium.
- a storage device such as a nonvolatile semiconductor memory, hard disk drive, SSD (Solid State Drive) constituting the auxiliary storage device 1200, or an IC card, SD card, DVD, or the like.
- SSD Solid State Drive
- the management device 2000 is, for example, a general business server, and has an auxiliary storage device 2200, a main storage device 2300, a CPU 2400, a network interface 2500, a display 2600, a mouse 2700, a keyboard 2800, and the like as hardware configurations.
- a bus 2100 for connecting the devices is provided.
- the auxiliary storage device 2200 describes an action history table 2210 in which a user's action history is recorded, a work area-position information correspondence table 2220 in which a correspondence between a department name and position information is described, and a context to be applied depending on the user's state.
- the business context estimation unit 2310 that estimates the user's business context resolves the contradiction and estimates the business context.
- the location information-business schedule contradiction resolution unit 2330 and the OS 2350 which is a base for executing these procedures are read.
- the functional units of the business context estimation unit 2310, the location information-business schedule inconsistency resolution unit 2330, and the OS 23500 are loaded into the main storage device 2300 as programs.
- the CPU 2400 operates as a functional unit that realizes a predetermined function by operating according to the program of each functional unit.
- the CPU 2400 functions as the business context estimation unit 2310 by operating according to the business context estimation program. The same applies to other programs.
- the CPU 2400 also operates as a functional unit that implements each of a plurality of processes executed by each program.
- a computer and a computer system are an apparatus and a system including these functional units.
- Information such as programs and tables for realizing each functional unit is stored in a storage device such as a nonvolatile semiconductor memory, hard disk drive, SSD (Solid State Drive) constituting an auxiliary storage device 2200, or an IC card, SD card, DVD, etc. Can be stored in any computer-readable non-transitory data storage medium.
- a storage device such as a nonvolatile semiconductor memory, hard disk drive, SSD (Solid State Drive) constituting an auxiliary storage device 2200, or an IC card, SD card, DVD, etc.
- SSD Solid State Drive
- the business context determination request unit 1310 When the user of the terminal 1000 makes an application activation request or a request to access the business data 3120 of the management device 2000, the business context determination request unit 1310 read into the main storage device 1300 in the terminal 1000 is executed.
- the business context determination request unit 1310 acquires basic data including date and time information and position information of the terminal 1000 using the basic data acquisition unit 1340 and passes the acquired basic data to the business context determination request unit 1310.
- the date and time information can be acquired from an NTP (Network Time Protocol) server
- the position information can be acquired from a position information acquisition device 1600 that uses GPS (Global Positioning System).
- the business context determination request unit 1310 that has received the basic data requests the management apparatus 2000 to estimate the business context of the terminal 1000 user. At this time, the name information and basic data of the owner of the terminal 10000 are also transmitted to the management apparatus 2000.
- the management apparatus 2000 Upon receiving the business context estimation request from the terminal 1000, the management apparatus 2000 executes the business context estimation unit 2310.
- the business context estimation unit 2310 receives the requester name, date, time, and location information requested to estimate the business context from the terminal 1000, and the location information set in the business schedule list 33 registered in advance and the terminal 1000 determines whether there is any contradiction with the position information acquired and measured. If there is no contradiction as a result of the determination, the business context estimation unit 2310 estimates the business context based on the registered schedule (S3). On the other hand, when there is a contradiction between the current location information and the location information in the business schedule list, the business context estimation unit 2310 estimates the business context using the location information-business schedule conflict resolution unit 2330, and the terminal 1000 The estimated business context is transmitted to (S1, S2).
- the location information-business schedule inconsistency resolution unit 2330 is close to the location information of the user who requested the estimation of the business context, and estimates the business context using the schedule information of the person related to the business.
- the business context determination request unit 1310 of the terminal 1000 that has received the estimated business context from the management device 2000 stores the estimation result in the business context 1230 in the auxiliary storage device 1200.
- the application policy determination unit 1320 acquires an application policy corresponding to the business context 1230 from the application policy correspondence table 1210 stored in the auxiliary storage device 1200 and stores it in the application policy 1240 in the auxiliary storage device 1200.
- the application activation control unit 1330 acquires the application policy corresponding to the application policy 1240 from the policy definition table 1220, and performs activation control of the acquired policy-defined application, access control to data, and the like (S4).
- FIG. 3 is a diagram illustrating a data structure of the employee information table 2250 used in the first embodiment.
- the employee information includes a name 2251 for storing the name of the employee, an employee number 2252 for storing the employee number, a business division 2253 for storing the employee's department, and an organization for storing the employee's department.
- the employee information table 2250 shown in FIG. 3 is used when searching for employees who are related to users in the present embodiment. For example, a method for acquiring a person who is business-related with Hitachi Taro 2251a in FIG. Search for.
- an employee having at least one of the affiliated business unit 2253, the affiliated part 2254, the affiliated PJ 2255, and the terminal ID 2256 of “Hitachi Taro” (2251) of the record 2255a is referred to as “Hitachi Jiro” of the record 2255b.
- “Saburo Hitachi” 251c in the record 2255c is referred to as “Hitachi Jiro” of the record 2255b.
- FIG. 4 is a diagram illustrating a data structure of the business schedule list 2240 used in the first embodiment.
- the work schedule list 2240 shown in FIG. 4 is used when acquiring position information scheduled to perform work for a user name and time.
- the business schedule information includes a name 2241 for storing the name of the registered user, a scheduled subject name 2242 for storing the business schedule subject, a date 2243 for storing the execution date of the business schedule, and a schedule start schedule. It consists of a time 2244 for storing the time and the scheduled end time, and a work area 2245 for storing the schedule execution location.
- a work area 2245 shown in FIG. 4 represents information on a place where the user performs work.
- a building name 2245-1 that stores the name of the building that performs the work
- a floor 2245- that stores the floor information. 2 is information including both.
- Hitachi Taro of record 2245-2a is scheduled to work on the work schedule at 12:00 (2244) on 2012/7/7 (2243), and the work area (2245) scheduled to work on is Yokohama 1st Building (2245-1). 1F (2245-2).
- FIG. 5 is a diagram illustrating the data structure of the action history table 2210 used in the first embodiment.
- the action history table 2210 includes a name 2211 for storing the name of the user who has acted, a date 2212 for storing the acted date, a time 2213 for storing the time when the action is measured, and a work schedule when the act is performed.
- the scheduled subject 2214 for storing the scheduled subject name the location information 2215 for storing the location information measured when acting, the business context 2216 for storing the business context when acting, and the location information-business schedule conflict resolution unit 2330 It is constituted by a contradiction flag 2217 for storing that it is resolved.
- the position information 2215 includes information of both the latitude / longitude 2215-1 for storing the longitude / latitude coordinate information and the wireless LAN identifier 2215-2 for storing the identifier unique to the wireless LAN, but the stored value is 2 Only one of the two is acceptable.
- the contradiction flag “1” is stored if it is resolved by the position information-business schedule conflict resolution unit 2330, and nothing is stored otherwise.
- the action history table 2210 shown in FIG. 5 is used when acquiring a person whose position information is close to the user at the same time in this embodiment.
- Hitachi Taro (2211) is 10:00 (2213)
- the position information (2215) is latitude / longitude (2215-1) is aaa, bbb
- the wireless LAN identifier (2215-2) ) Is “Yokohama No. 1 Building 1F”
- the management device 2000 acquires “Hitajiro Jiro” in the record 2217b as a user who was at the same place at the same time.
- FIG. 6 is a diagram exemplifying the data structure of the work area-position information correspondence table 2220 used for determining the work area where the user is located from the position information of the terminal 1000 in the first embodiment.
- the service area 2221 stores information such as the name of a building on which the user operates, and position information 2222 stores position information such as longitude and latitude.
- the work area position information correspondence table 2220 is created by the system administrator and stored in the auxiliary storage device 2200 in the management device 2000.
- the business area includes, for example, a building name that stores the building name of the company “Yokohama No. 1 Building” in record 2221-2a in FIG. 6 and the exhibition hall name “Tokyo Exhibition Hall” in record 2221-2d, although the information of both floors that store the number of floors is included, only one of the two values may be stored.
- the position information 2222 includes the same information as 2215 used in FIG.
- the business area 2221 includes a building name 2221-1 and a floor 2221-2, and the position information 2222 includes a latitude / longitude 2222-1 and a wireless LAN identifier 2222-2.
- the latitude / longitude information 2222-1 is “aaa, bbb”
- the wireless LAN identifier information 2222- 2 is determined to be “Yokohama No. 1 Building 1F”.
- the latitude / longitude 2222-1 of the position information measured by the terminal 1000 is “xxx, yyy” (2222-2d)
- FIG. 7 is a diagram illustrating a data structure of the business context correspondence table 2230 used when estimating the business context from the user name and the business area information in the first embodiment.
- the business context may differ depending on the user.
- a name 2231 for storing a user name to which a business context is applied a business area 2232 for storing a building name and floor information, and a business context 2234 for storing an estimated business context name are included.
- the business context correspondence table 2230 is created by the system administrator and stored in the auxiliary storage device 2200 in the management device 2000.
- the work area 2232 includes a building name 2232-1 and a floor 2232-2.
- the business area 2232 holds the same information as 2221 in FIG. For example, when “Hitachi Taro” of record 2233a is in the “1F” (2232-2) business area of “Yokohama No. 1 Building” (2232-1), the business context is “in-house” (2233) and management device 2000. presume.
- FIG. 8 is a diagram illustrating a data structure of the application policy correspondence table 1210 used in the first embodiment to determine the application policy from the business context.
- the application policy correspondence table 1210 includes a business context 1211 and a corresponding application policy name 1212.
- the application policy correspondence table 1210 is created by the system administrator, and is stored in the terminal 1000 by a method such as sending a file using a remote terminal management tool, sending by mail attachment, or downloading from a web page. It is stored in the auxiliary storage device 1200.
- the policy name 1212 applied when the user business context 1211 is “in-house” (1212b) is “business application / data available”.
- the applied policy name 1212 is “business application / data available”, and the terminal 1000 is permitted to use both the business application 3100 and the business data 3120.
- the applied policy name 1212 is “business application / data available”, and the terminal 1000 uses both the business application 3100 and the business data 3120. Is allowed.
- the business context 1211 is “business, business trip, customer”
- the applied policy name 1212 is “restricted business application / data available”, and the business application 3100 and business that can be used on the terminal 1000 are displayed. Only data 3120 set in advance is permitted. Further, if the business context 1211 is “business, business trip, exhibition, etc.”, the applied policy name 1212 is “impossible to edit business data”, and the terminal 1000 is prohibited from editing the business data 3120. .
- the application policy name 1212 is “all usable”, and the use of all the applications and data of the terminal 1000 is permitted.
- the application policy name 1212 is “available only for private applications”, and the private application 3110 excluding the business application 3100 of the terminal 1000 can be used.
- FIG. 10 is a diagram illustrating a data structure of a policy definition table 1220 that defines details of access control corresponding to a policy name shown in FIG.
- the configuration includes an applied policy name 1221, a private application 1222, a business application 1223, access to business data 1224, a business data edit 1225, a camera 1226, and a data sharing 1227 by a proximity communication device. Is done.
- the policy definition table 1220 is created by the system administrator as in FIG. 8, and is stored in the auxiliary storage device 1200 in the terminal 1000 by the method described above.
- the applied policy name 1221 is “business application / data available” (record 1227b)
- the application approved by the company can be started as the private application 1222, and the business application 1223 can be started up.
- the business data can be accessed 1224, the business data can be edited 1225, and the use of the camera 1226 is disabled.
- IrDA or Bluetooth Bluetooth is a registered trademark, the same applies hereinafter. Access control is performed such that data sharing 1227 by a close proximity communication device cannot be used.
- a URL for permitting or prohibiting access of a browser or the like, or a port number for permitting or prohibiting access can be set.
- the business context estimation unit 2310 estimates a user's business context (or business status).
- the business context estimation unit 2310 is executed when a business context estimation request is received from the business context determination request unit 1310 of the terminal 1000. Simultaneously with the business context estimation request, the terminal owner name, date information, time information, and location information of the terminal 1000 are sent from the terminal 1000.
- the business context estimation unit 2310 When the business context estimation unit 2310 is executed, the information received from the terminal 1000 first is stored in step 2311, the terminal owner name is stored in the variable P0, and the position information is stored in the variable L.
- step 2312 the business context estimation unit 2310 acquires the business schedule of the current time variable P 0 from the business schedule list 2240 and stores it in the variable S.
- the business context estimation unit 2310 acquires location information 2222 corresponding to the business area 2221 of the variable S from the business area-position information correspondence table 2220.
- the obtained position information 2222 is compared with the variable L. For example, if the two longitude and latitude information are linear distances within a predetermined value (for example, 10 m) or the wireless LAN identifiers are the same, the registered business schedule It is determined that there is no contradiction in the position information measured by the terminal 1000, and it is determined that there is a contradiction when the condition is not satisfied.
- the business context estimation unit 2310 passes the processing to the location information-business schedule conflict resolution unit 2330, and the estimated business context that resolves the conflict is generated. Wait for it to be returned and store the returned estimated business context in variable C.
- step 2314 the business context corresponding to the location of the variable S is acquired from the business context correspondence table, and the business context estimation unit 2310 acquires the estimated The business context is stored in variable C.
- step 2315 the business context estimation unit 2310 receives the variable P 0, date, time, variable L received from the terminal 1000, the variable S acquired by the management device 2000, and the step 2314 or position information-business schedule conflict resolution. Information on variable C estimated by unit 2330 is added to action history table 2210.
- step 2316 the business context estimation unit 2310 transmits the estimated business context variable C to the terminal 1000, and ends the business context estimation unit.
- Hitachi Taro starts the business application 3100 in the Yokohama 1st building 1F at 10:00 on July 28, the terminal of Hitachi Taro is the owner name: Hitachi Taro, current time: 7 / 28 At 10 o'clock, as a positional information, latitude / longitude: aaa, bbb Wireless LAN identifier: a business context estimation request including Yokohama 1st Building 1F is transmitted to the management apparatus 2000.
- the management apparatus 2000 Upon receiving the business context estimation request, the management apparatus 2000 executes the business context estimation unit 2310, and stores Hitachi Taro, which is the terminal owner name sent from the terminal 1000 in step 2311 of FIG. 10, in the variable P0.
- the terminal location information (latitude / longitude: aaa, bbb, wireless LAN identifier: Yokohama 1st Building 1F) is stored in the variable L.
- step 2312 the business context estimation unit 2310 acquires the business schedule (record 2245-2j) of the variable P0 scheduled at the current time (10:00 on July 28) from the business schedule list 2240 and stores it in the variable S.
- the business schedule (record 2245-2j) of the variable P0 scheduled at the current time (10:00 on July 28) from the business schedule list 2240 and stores it in the variable S.
- the business context estimation unit 2310 compares the business area information registered in the variable S with the variable L that stores the location information of the terminal 1000, and uses the business area-position information correspondence table 2220 in FIG.
- the position information stored in the variable L is converted into work area information.
- the determination in step 2313 exceeds the threshold value, and the process proceeds to step 2330.
- the threshold value is set to 10 m or 50 m, for example, and if the difference between the position information corresponding to the work area information registered in the variable S and the position information of the terminal 1000 is within the threshold value, the terminal 1000 You will be on the schedule.
- the threshold value may be determined to be within the threshold value if the same wireless LAN identifier is used.
- the position information of the terminal 1000 and the position information corresponding to the work area information registered in the variable S are within a predetermined range (for example, 10 m, 50 m, etc.), it is determined that they are the same work area. Also good.
- the location information-business schedule conflict resolution unit 2330 estimates the business context in which the conflict between the location information and the business schedule is resolved as “internal”, and stores the estimated business context “internal” in the variable C.
- the variable S for storing the work schedule for resolving the contradiction is the floor where the scheduled subject is “mobile regular”, the time is “10: 00-11: 00”, and the building name of the work area is “Yokohama No. 1 Building” Is changed to “1F” by the position information-business schedule conflict resolution unit 2330. Details of the business context estimation procedure and the business schedule change procedure of the location information-business schedule conflict resolution unit 2330 will be described later.
- step 2313 If it is determined in step 2313 that the difference in position information is within the threshold, the process proceeds to step 2314, and the business corresponding to the business area information stored in the variable P0 and the variable S is performed using the business context correspondence table 2230. The context is acquired, and the acquired business context is stored in the variable C.
- step 2315 the variable P0 that stores the name of Hitachi Taro who requested the estimation of the business context, the current date 7/28, the time of 10:00, the scheduled subject name of the variable S that stores the current business schedule "mobile regular”, Information of variable L “latitude / longitude: aaa, bbb wireless LAN identifier: Yokohama 1st building 1F”, business context “in-house”, and contradiction flag “1” that stores the current position information is added to the action history table 2210.
- step 2316 the estimated business context “in-house” is transmitted to the terminal 1000, and the business context estimation unit 2310 is terminated.
- the business context estimation unit 2310 estimates the user's business context from the business context of the related person using the positional information received from the terminal 1000 and the positional information stored in the management apparatus 2000, and Send the estimated business context.
- FIGS. 11A and 11B are first half of a flowchart showing an example of processing performed by the position information-business schedule conflict resolution unit
- FIG. 11B is a flowchart showing an example of processing performed by the location information-business schedule conflict resolution unit.
- the location information-business schedule conflict resolution unit 2330 is a process executed when it is determined in step 2313 of the business context estimation unit 2310 that there is a conflict between the business area information of the variable S and the variable L. This is a process for resolving inconsistencies by using business schedule information of business-related persons near the user.
- step 2330a the position information-business schedule inconsistency resolution unit 2330 acquires a person related to the business with the variable P0 from the employee information table 2250, and stores the acquired set in the variable P.
- the person who is business-related in the present invention indicates that at least one of the affiliated business unit 2253, the affiliated unit 2254, and the affiliated PJ2255 is the same person as the user.
- the latest line in which the name 2211 matches each value stored in the variable P from the action history table 2210 is stored in the variable H.
- H ′ information that is within a certain time, for example, within 15 minutes from the current time of variable H is stored in H ′.
- variable H ′ is the name of the person who has the information of the variable H ′ that satisfies the distance to L within a certain distance, for example, the distance is within 10 m or 50 m, or the wireless LAN identifier information is the same.
- the distance is within 10 m or 50 m, or the wireless LAN identifier information is the same.
- the position information-business schedule contradiction resolution unit 2330 determines whether or not the variable P ′ is empty. If it is empty, the process goes to Step 2330m, and if it is not empty, the process goes to Step 2330d. Proceed.
- the location information-business schedule inconsistency resolution unit 2330 determines whether at least one of the variables P 'has registered the business schedule at the current time. If no job schedule has been registered for the variable P ′, the process proceeds to step 2330j. If at least one of the variables P ′ has registered the work schedule, the process proceeds to 2330g.
- the position information-business schedule conflict resolution unit 2330 determines the person with the highest business relevance among the variables P 'in which the schedule is registered, and stores it in the variable P1.
- the degree of business relevance is determined by the number of matching information among the information on the business divisions, departments, and PJs belonging to the variables P0 and P ′.
- the method of calculating the degree of business relevance is not limited to the above, such as inclining each information or using other information such as the hire year.
- step 2330h the location information-business schedule conflict resolution unit 2330 overwrites the variable S that stores the business schedule currently performed by P0 with the business schedule registered at the variable P1.
- step 2330i the position information-business schedule inconsistency resolution unit 2330 acquires the business context corresponding to the business area information registered in the variable P0 and the variable S from the business context correspondence table 2230, and uses the acquired business context as a variable.
- P0 be the current estimated business context.
- the business context at this time is stored in the variable C.
- step 2330f which is a procedure executed when the work schedule is not registered in any of the variables P ′ in step 2330f, for example, the identity confirmation screen of the variable P0 is displayed on the terminal 1000 of the variable P ′. , Wait until one of the variables P ′ is pressed on the identity confirmation screen.
- Step 2330j is an example shown in the present embodiment.
- the variable P0 is an alternative means for indicating that the variable P0 is the same as that of the terminal user, such as a method of performing personal authentication using near field communication such as NFC or Bluetooth, etc. Be good.
- step 2330k the location information-business schedule conflict resolution unit 2330 determines whether or not the button that proves that the variable P 'is the user has been pressed. If the button for proving identity is not pressed, the process proceeds to step 2330n. If the button for proving identity is pressed, the process proceeds to step 2330l.
- the location information-business schedule conflict resolution unit 2330 acquires the business area corresponding to the variable L from the business area location information correspondence table 2220, and stores the acquired business area information in the variable A.
- the latitude / longitude information is the business area-position information correspondence table shown in FIG.
- the acquired business area information is that the building name 2222-1 is Tokyo 1st building and the floor 2221-2 is 1F. Become.
- step 2330m the business context corresponding to the variable P0 and the variable A is acquired from the business context correspondence table 2230 and stored in the variable C.
- variable P0 Assuming that Hitachi Taro is stored in variable P0, Tokyo 1st building is stored as variable name information, and 1F is stored as floor information, variable P0 has records 2233a to 2233d in the business context correspondence table 2230 shown in FIG. Since the variable A matches the building name 2232-1 of the record 2233c, the extracted business context is “other department” (record 2233c).
- step 2330n “out of business” is stored in the variable C that stores the estimated business context.
- step 2330o “unknown” is stored in variable C that stores the estimated business context.
- the procedure for the location information-business schedule conflict resolution unit 2330 to resolve the contradiction and estimate the business context when there is a conflict between the user location information and the business schedule will be described using an example.
- Hitachi Taro has started the business application 3100 in the first building 1F of Yokohama at 10:00 on July 28. Therefore, before the location information-business schedule conflict resolution unit 2330 is executed, Hitachi Taro is stored in the variable P0 storing the user name, and latitude / longitude: aaa, in the variable L storing the user location information.
- bbb Wireless LAN identifier It is assumed that the record 2245-2j in the work schedule list 2240 shown in FIG. 4 is stored in the variable S in which the Yokohama 1st building 1F stores the user's work schedule.
- step 2313 of FIG. 10 When it is determined in step 2313 of FIG. 10 that the difference between the work area information of the variable S and the position information of the variable L exceeds the threshold, the position information-work schedule inconsistency resolution unit 2330 shown in FIG. 11 is executed.
- step 2330a the affiliated business unit 2253 of the record 2255a corresponding to “Hitachi Taro” stored in the variable P0 from the employee information table 2250 is “Yokohama Business Division”, the affiliated unit 2254 is “first development department”, and the affiliated PJ2255 is Acquired “Corporate Mobile”.
- the affiliated business unit 2253 of the record 2255a corresponding to “Hitachi Taro” stored in the variable P0 from the employee information table 2250 is “Yokohama Business Division”
- the affiliated unit 2254 is “first development department”
- the affiliated PJ2255 is Acquired “Corporate Mobile”.
- at least one of the acquired department, department, and PJ acquires the same person from the employee information table 2250 and stores it in the variable P.
- two variables are stored in the time variable P: Jiro Hitachi (record 2255b), to which all of the affiliated business division, department, and PJ match, and Saburo Hitachi (record 2255c), to which the affiliated PJ matches. is there.
- step 2230b the latest line that matches "Hitachi Jiro" whose name 2211 is stored in the variable P from the action history table 2210 of FIG. 5 and the latest line that matches "Hitachi Saburo” are stored in the variable H. .
- the columns actually extracted from the action history table 2210 shown in FIG. 5 are acquired as 2217i as the latest row matching “Jiro Hitachi” and 2217j as the latest row matching “Hitachi Saburo” and stored in the variable H. Is done.
- step 2330c information within 15 minutes from the current time 10:00 is acquired from the information stored in the variable H and stored in the variable H '.
- Hitachi Jiro's information (record 2217i) is not applicable because the registered time is 9:00, and only Hitachi Saburo's information (record 2217j) is stored in H '.
- step 2330d first, the position information held by the variable H ′ is compared with the variable L.
- the position information held by the variable H ′ is aaa and bbb in the latitude / longitude 2215-1 and the Yokohama 1st building 1F is stored in the wireless LAN identifier 2215-2.
- the latitude and longitude in the variable L are aaa and bbb.
- Yokohama 1st Building 1F is stored. From these, since the position information held by the variable H ′ and the variable L match, the position information-business schedule inconsistency resolution unit 2330 determines that the person near the variable L is Hitachi Saburo, and sets the variable P ′ as Hitachi Saburo.
- the position information-business schedule inconsistency resolution unit 2330 determines that the person near the variable L is Hitachi Saburo, and sets the variable P ′ as Hitachi Saburo.
- Step 2330e it is determined whether or not the variable P ′ is empty. Since Saburo Hitachi is stored in the variable P ′ this time, 2330f is executed as the next step.
- Step 2330f it is determined whether or not a business schedule is registered for the user stored in the variable P 'at the current time. From the business schedule list 2240 shown in FIG. 4, a business schedule that matches the name: Saburo Hitachi Date: 2012/7/28 Time: 10:00 is acquired. If there is no match at this time, Step 2330j is executed. However, since the work schedule of the record 2245-2l in FIG. 4 matches this time, Step 2330g is executed next.
- Step 2330g the person with the highest degree of business relevance is acquired from the variable P ′ whose work schedule is registered at the current time, and stored in the variable P1.
- the business relevance level in this embodiment is registered in the variable P ′ because the determination is made based on the number of matching information among the information on the belonging business division, the belonging department, and the belonging PJ of the variables P0 and P ′.
- the degree of business relevance of all members who are present is calculated. Since only Saburo Hitachi is stored in the variable P ′ this time, the business relevance only for Saburo Hitachi is calculated. Since Hitachi Saburo matches only the affiliation PJ, the business relevance level is determined to be “1”. In this example, since the number of users stored in the variable P ′ is one, the person with the highest degree of business relevance is Hitachi Saburo, and the variable P1 for storing the person with the highest degree of business relevance is Saburo Hitachi.
- the number of users stored in the variable P ′ is one, the person with the highest degree of business relevance is Hit
- step 2330h the current business schedule of Saburo Hitachi stored in the variable P1 is acquired from the business schedule list, and the business schedule of the variable P1 is stored in the variable S that stores the user business schedule.
- the current P1 business schedule is obtained by the same method as the method performed in step 2330f, and the procedure is omitted.
- the acquired business schedule information is a record 2245-2k in FIG. 4 and is stored in the variable S.
- step 2330i the business context corresponding to the business area information stored in the variable S is acquired from the business context correspondence table 2230 shown in FIG. Since the work area currently stored in the variable S includes 2245-2k in the work schedule list 2240 shown in FIG. 4, the building name: Yokohama Building No. 1 Floor: 1F is stored. From the business context correspondence table 2230 shown in FIG. 7, the business context corresponding to the above-mentioned business area and Taro Hitachi stored in the variable P0 is in-house (record 2233a), and the estimated business context of the variable P0 is “in-house”. To do.
- the location information-business schedule conflict resolution unit 2330 estimates the business context by the above steps (2330g, or 2330k, 2330l, 2330m), and the business area information of the business schedule registered by the user and the location information of the terminal The contradiction that had occurred in
- the conflict between the business schedule and the terminal location information is resolved, and the user convenience Strict access control is possible without impairing performance.
- a business schedule registered by a person who is business related to the user of the terminal 1000 and who owns the terminal 1000 whose position information is close to the terminal 1000 owned by the user is regarded as the business schedule of the user.
- the management device 2000 determines an application policy based on the estimated business context and notifies the terminal 1000 of the application policy. May be.
- the access control method is effective when a person who is related in business is close to the same time (the difference in position information is within a threshold value or the wireless LAN identifier is the same).
- An example will be described in which access control is realized without impairing user convenience by using past actions of related persons.
- FIG. 12 shows the configuration of the access control system exemplified in this embodiment.
- FIG. 12 is similar to FIG. 1 which is a system configuration diagram of the first embodiment, but differs from FIG. 1 in that the location information-business schedule conflict resolution unit read into the main storage device 2300 in the management device 2000 2331. The processing is different from that of the position information-business schedule conflict resolution unit 2330 shown in FIG. Other configurations are the same as those in the first embodiment.
- the position information-business schedule conflict resolution unit 2331 is a process executed when it is determined in step 2313 of the process of the business context estimation unit 2310 that there is a contradiction between the business area information of the variable S and the variable L. Yes, it is a process for resolving contradiction using the action history information of a person related to the business who is near the user.
- step 2331a is first executed.
- step 2331a name information of a person who has a business relevance level with the user name is acquired from the employee information table 2250 and stored in the variable P.
- the business related person is a user who matches one or more of the belonging business department, the belonging department, and the belonging PJ.
- step 2331b the position information-business schedule contradiction resolution unit 2331 displays the change pattern of the user's past position information stored in the variable P similar to the change pattern of the user's current position information from the action history table 2210. Search for. Then, the action history information having a similar change pattern of position information is stored in the variable H. For example, in the present embodiment, a method of searching for a user having the same change pattern as the change pattern of the position information for the last three times of the user is used as a method of searching for similarity of the change pattern of the position information.
- step 2331c it is determined whether or not the variable H is empty. If it is empty, the process proceeds to step 2331f. If it is not empty, the process proceeds to step 2331d.
- variable H is not empty and the process proceeds to step 2331d, the latest history in the variable H is stored in the variable H1, and the name of the user who has performed the action of the variable H1 is stored in the variable P1.
- step 2331e the business context that was applied to the variable P1 when it was in the variable H1 is estimated as the business context of the variable P0, and the estimated business context is stored in the variable C.
- step 2331f the business context is estimated as “out of business”, and “out of business” is set in the variable C that stores the estimated business context.
- the location information-business schedule conflict resolution unit 2331 that performs the above-described processing resolves the conflict and estimates the business context when there is a conflict between the user location information and the business schedule. explain.
- Hitachi Taro has been in the 1st floor of the first building of Yokohama at 9:50 on July 28, and requested to start the business application 3100 at 10:00. Therefore, before the location information-business schedule conflict resolution unit 2331 is executed, Hitachi Taro is stored in the variable P0 storing the user name, and latitude / longitude: aaa, in the variable L storing the user location information.
- bbb Wireless LAN identifier It is assumed that the record 2245-2j in the work schedule list 2240 shown in FIG. 4 is stored in the variable S in which the Yokohama 1st building 1F stores the user's work schedule.
- step 2313 of FIG. 10 When it is determined in step 2313 of FIG. 10 that the difference between the work area information of the variable S and the position information of the variable L exceeds the threshold value, the position information-business schedule inconsistency resolution unit 2331 shown in FIG. 11 is executed.
- step 2331a is executed.
- step 2331a the affiliated business unit 2253 corresponding to “Hitachi Taro” stored in the variable P0 from the employee information table 2250 is “Yokohama Business Division”, the affiliated unit 2254 is “first development department”, and the affiliated PJ2255 is “company-wide mobile”. Is obtained.
- at least one of the acquired department, department, and PJ is acquired from the employee information table 2250 and stored in the variable P.
- two variables are stored in the variable P: Jiro Hitachi (record 2255b) in which all of the affiliated business division, department, and PJ match, and Saburo Hitachi (record 2255c) in which the affiliated PJ matches.
- the action history table 2210 obtains a pattern similar to the current user position information change pattern, but the user position information change pattern is 9:50, 9:55, 10 o'clock.
- the position information measured three times in succession was latitude / longitude: aaa, bbb Wireless LAN identifier: Yokohama Building No. 1F.
- Jiro 2217b, 2217d, and 2217f of location information whose latitude / longitude: aaa, bbb, wireless LAN identifier: Yokohama 1st Building 1F was measured three times consecutively from the action history table 2210 shown in FIG. It is. Therefore, the action history of records 2217b, 2217d, and 2217f is stored in variable H as an action history similar to the user's action pattern.
- step 2331c it is determined whether or not the variable H is empty. In this example, since the action history of Jiro Hitachi is stored in the variable H, it is determined that the variable H is not empty and the process proceeds to step 2331d.
- the position information-business schedule inconsistency resolution unit 2331 stores the latest history in the variable H1 among the action history information stored in the variable H, and performs the action stored in the variable H1.
- the stored user name is stored in the variable P1.
- the values of the records 2217b, 2217d, and 2217f in the action history table 2210 shown in FIG. 5 are stored in the variable H1, and the action of the variable H1 is stored.
- the performed Hitachi Jiro is stored in the variable P1.
- the position information-business schedule inconsistency resolution unit 2331 converts the business context applied to Jiro Hitachi stored in the variable P1 when the action stored in the variable H1 was performed into the variable P0.
- Estimated business context In this example, since the business context stored in the variable H1 is “in-house” (record 2217f), the business context of the variable P0 is estimated as “in-house”, and “in-house” is stored in the variable C that stores the estimated business context.
- the business relation having the past action history similar to the user who resolves the contradiction is generated.
- strict access control is realized without deteriorating the convenience for the user.
- this embodiment records a contradiction that has occurred between the work schedule, the location information of the terminal 1000, and the work schedule as a past contradiction history. This is a technique for realizing strict access control by resolving inconsistencies between the current business schedule and the location information of the terminal 1000 using the past inconsistency history.
- FIG. 14 shows a configuration diagram of a computer system exemplified in this embodiment.
- the configuration of this embodiment is also similar to that of Embodiment 1 and Embodiment 2.
- the difference in the configuration of the access control system is that a contradiction history table 2260 is added as a data structure stored in the auxiliary storage device 2200 in the management device 2000 in FIG. 14, and also in this embodiment, the management device 2000.
- the location information-business schedule contradiction resolution unit 2332 executed in the main storage device 2300 is stored, but the location information-business schedule conflict resolution unit used in the first and second embodiments (in FIG. 1) 2330 and 2331 in FIG. 13 are different in processing contents.
- FIG. 16 is a diagram illustrating a data structure of the contradiction history table 2260 used for acquiring past contradiction information that has occurred in a business schedule in which a user participates with the same schedule name in the past in this embodiment.
- the contradiction history table 2260 includes a date 2261 for storing the date when the business schedule is executed, a schedule name 2262 for storing the executed business schedule subject, and a person who is scheduled to participate in the executed business schedule. Participant 2263 who stores the name of the registered person, contradiction type 2264 that stores what kind of contradiction has occurred in the executed work schedule, and contradiction time that stores the length of time that the contradiction has occurred 2265.
- the contradiction history table 2260 shown in FIG. 16 is used for acquiring a history of contradiction that has occurred in the same business schedule.
- the past schedule contradiction of the mobile regular that Hitachi Taro participates in is information held by three rows including 2265a, 2265b, and 2265c.
- the row shown in FIG. 2265a indicates that the business schedule “mobile regular” performed on “2012/7/7” has been extended by 30 minutes.
- FIGS. 15A, 15B, and 15C An example of processing performed by the location information-business schedule contradiction resolution unit 2332 will be described with reference to the flowcharts shown in FIGS. 15A, 15B, and 15C.
- 15A is the first half of the flowchart
- FIG. 15B is the middle part of the flowchart
- FIG. 15C is the second half of the flowchart.
- the location information-business schedule conflict resolution unit 2332 is a process executed when it is determined in step 2313 of the business context estimation unit 2310 that there is a conflict between the business area information of the variable S and the variable L. This is a process for resolving a contradiction currently occurring using history information of a contradiction that has occurred in a past business schedule.
- step 2332a is first executed.
- step 2332a the position information-business schedule inconsistency resolution unit 2332 determines whether or not the variable L matches the business area 2245 of the business schedule list 2240 scheduled immediately before.
- the business schedule scheduled immediately before is assumed to be the closest to the current time among the business schedules already completed.
- step 2332a is executed next. If it is determined that they do not match, step 2332a 'is executed.
- step 2332a If it is determined in step 2332a that the locations match, “increase” is stored as the contradiction type in step 2332b, and the time from the end time of the previous schedule to the current time is stored in minutes as the contradiction time, and step 2332c is stored. Proceed to In this case, since the meeting is prolonged, the place is the same and the scheduled end time is exceeded, “extension” is set.
- step 2332c the contradiction history from the contradiction history table 2260 within a certain period, for example, one month, information including the name stored in the variable P0 in the prospective participant 2263 in the table, and the schedule in the table Information corresponding to the subject of the work schedule scheduled for the name 2262 immediately before is stored in the variable H. It is assumed that the variable number P0 stores the name information of the user who made the business context estimation request in the business context estimation unit 2310 shown in FIG.
- step 2332a If it is determined in step 2332a that the location does not match, it is determined in step 2332a 'whether or not the variable L matches the work area 2245 of the work schedule list 2240 scheduled immediately thereafter.
- the business schedule scheduled immediately after is assumed to have the scheduled start time closest to the current time among the business schedules scheduled in the future. This comparison is also performed in the same manner as the determination in step 2332a.
- step 2332a ′ if it is determined that the current position information and the work area 2245 immediately after the work schedule list 2240 match, step 2332b ′ is executed next, and if it is determined that they do not match, step 2332q. Is executed.
- step 2332b ′ stores “advance” as the contradiction type, and stores the time from the current time to the start time of the next schedule in minutes as the contradiction time, Proceed to step 2332c ′.
- step 2332c ′ the contradiction history from the contradiction history table 2260 within a certain period, for example, within one month, the information that the name of the variable P0 is included in the prospective participant 2263 in the table, and the schedule name 2262 in the table are stored. Information that matches the subject of the business schedule scheduled immediately after is stored in the variable H.
- step 2332d the position information-business schedule inconsistency resolution unit 2332 determines whether or not the content of the variable H is empty. If the contents of the variable H are not empty, the process proceeds to step 2332e, and if it is empty, the process proceeds to step 2332j.
- step 23332e the position information-business schedule inconsistency resolution unit 2332 acquires information for the latest three times from the variable H, and stores them in the variables H0, H1, and H2.
- step 2332f it is compared whether the contradiction time calculated in 2332b or 2332b 'is smaller than the three average contradiction times of the variable H0, the variable H1, and the variable H2. If it is determined to be small, the process proceeds to step 2332g, and if it is determined to be large, the process proceeds to step 2332j.
- step 2332f If it is determined in step 2332f that the current contradiction time is smaller than the average of the last three previous contradiction times, it is determined in step 2332g whether or not the current conflict type is extended. If the contradiction type is extension, the process proceeds to step 2332h, and if not, the process proceeds to step 2332h '.
- step 2332h the location information-business schedule conflict resolution unit 2332 stores the business schedule that the user has performed immediately before in the variable S that stores the current business schedule.
- step 2332h ' the location information-business schedule inconsistency resolution unit 2332 stores the business schedule scheduled to be performed immediately by the user in the variable S that stores the current business schedule.
- step 2332i the position information-business schedule inconsistency resolution unit 2332 acquires the business context corresponding to the business area information in the variable S overwritten in step 2332h or step 2332h ′ from the business context correspondence table 2230, Is stored in the variable C as the estimated business context.
- step 2332j the location information-business schedule conflict resolution unit 2332 adds the current date, the scheduled name in the variable S, the variable P0, the conflict type, and the conflict time to the conflict history table 2260.
- step 2332d If it is determined in step 2332d that the variable H is empty or it is determined in step 2332f that the current contradiction time is larger than the average of the last three contradiction times, the process proceeds to step 2332k.
- step 2332k the work area corresponding to the variable L storing the user position information is acquired from the work area position information correspondence table 2220.
- the acquired work area information is stored in variable A.
- step 23321 the business context corresponding to the variable P0 and the variable A is acquired from the business context correspondence table 2230.
- step 2332m the business context estimated in step 2332l, the approval button, and the non-approval button are displayed on the screen of the terminal owned by the approver, and the process is stopped until any button is pressed. If the approver presses any button, the process proceeds to step 2332n.
- an approver is defined as a person who is related in business and has business authority, such as a general manager of a department.
- step 2332n it is determined whether or not the approver has pressed the approval button for the business context estimated in step 2332l. If the approval button is pressed, the process proceeds to step 2332o, and if the non-approval button is pressed, the process proceeds to step 2332p.
- step 23321 When the approval button is pressed, it is determined that the business context estimated in step 23321 can be applied to the user, and the business context estimated in step 2332l is stored in the variable C that stores the estimated business context.
- step 2332p it is determined that the user is not currently in business, and the outside of business is stored in the variable C that stores the business context.
- step 2332a If it is determined in step 2332a 'that the locations do not match, the process proceeds to step 2332q, and unknown is stored in the variable C that stores the business context.
- the location information-business schedule conflict resolution unit 2332 that performs the above-described processing resolves the conflict and estimates the business context when there is a conflict between the user location information and the business schedule. explain.
- step 2313 of FIG. 10 When it is determined in step 2313 of FIG. 10 that the difference between the work area information of the variable S and the position information of the variable L exceeds the threshold, the position information-work schedule inconsistency resolution unit 2332 shown in FIG. 11 is executed.
- step 2332a is first executed.
- step 2332a it is determined whether or not the variable L matches the location of the previous work schedule.
- the immediately preceding work schedule is the work schedule shown in the line 2245-2g shown in FIG. 4 because the scheduled end time is the closest to the current time among the already completed work schedules. It becomes.
- the method used in step 2313 in the work context estimation unit 2310 shown in FIG. 10 is adopted. In this example, when the work area information and the position information are compared by the method described in the first embodiment, the results match, and therefore the process proceeds to step 2332b in FIG. 15A.
- step 2332b the contradiction type is stored as “extension”, and the contradiction time is calculated using the time information 2244g and the current time held by the immediately preceding business schedule. Specifically, since the end time of the work schedule stored in 2244g is 11:00 and the current time is 11:15, the contradiction time is calculated as 15 minutes.
- step 2332c with reference to the contradiction history table 2260 shown in FIG. 16, the history within one month from the current date and time, the variable P0 is included in the prospective participants, and the subject of the work schedule that was performed immediately before the schedule name Is acquired and stored in the variable H.
- step 2332d it is determined whether or not the variable H is empty. As described above, in this example, since three pieces of information are stored in the variable H, it is determined that the information is not empty, and the process proceeds to step 2332e.
- step 2332e the latest three pieces of information stored in variable H are stored in variable H0, variable H1, and variable H2, respectively.
- Step 2332f it is determined whether or not the contradiction time calculated in Step 2332b is smaller than the three average contradiction times of the variable H0, the variable H1, and the variable H2.
- “30” is stored in the variable H0
- “20” is stored in the variable H1
- “30” is stored in the variable H2. Therefore, the average of the three variables is 26 minutes and 40 seconds, and is calculated in step 2332b. Since “15” is stored in the contradiction time, it is determined that the contradiction time is smaller than the average of the variable H0, the variable H1, and the variable H2, and the process proceeds to 2232g.
- step 2332g it is determined whether or not the current contradiction type is “extension”. In this example, since it is stored in step 2332b that the contradiction type is “extension”, the determination is “extension”, and the process proceeds to step 2332h.
- step 2332h it is determined that the business schedule that has been performed immediately before the processing so far has been extended to the present, and the previous business schedule is stored in the variable S that stores the current user's business schedule.
- the variable S stores information on the line including 2245-2g in the work schedule list 2240 shown in FIG.
- step 2332i the business context is estimated from the business area information stored in the variable P0 and the variable S storing the user and the business context correspondence table 2230 shown in FIG.
- Hitachi Taro is stored in the variable P0
- the work area information of the variable S is shown in FIG. 7 because Yokohama Building 1 2245-1g is stored in the building name and 1F2245-2g is stored in the floor.
- the corresponding business context in the business context correspondence table 2230 is in-house (record 2233a)
- the current business context of the variable P0 is estimated to be in-house
- “in-house” is stored in the variable C that stores the estimated business context.
- step 2332j the current date, the business schedule name estimated to be currently performed, the variable P0, the contradiction type, and the contradiction time are added to the contradiction history table 2260.
- “2012/7/21” as the current date “mobile regular” as the name of the business schedule estimated to be currently performed
- “Hitachi Taro” stored in the variable P0 as the planner
- contradiction type As “extension” stored in step 2332b and “15” calculated in step 2332b as the contradiction time.
- this invention is not limited to an above-described Example, Various modifications are included.
- the above-described embodiments have been described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described.
- a part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment.
- the first embodiment and the second embodiment can be used in combination.
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Human Resources & Organizations (AREA)
- Theoretical Computer Science (AREA)
- Strategic Management (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Educational Administration (AREA)
- Development Economics (AREA)
- Game Theory and Decision Science (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- General Health & Medical Sciences (AREA)
- Social Psychology (AREA)
- Software Systems (AREA)
- Health & Medical Sciences (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Description
Claims (12)
- プロセッサとメモリを備えた管理装置に接続された端末のアクセス制御方法であって、
前記管理装置が、前記端末の所有者の時刻に対応する位置情報をスケジュール格納部に格納する第1のステップと、
前記端末が、位置情報と時刻情報を取得し、当該端末の所有者の識別子と、前記位置情報と時刻情報を前記管理装置に送信する第2のステップと、
前記管理装置が、前記端末から受信した所有者の識別子と前記位置情報及び時刻情報を、前記スケジュール格納部に格納した前記端末の所有者の時刻に対応する位置情報と比較して、当該端末の時刻情報に対応する位置情報が、前記スケジュール格納部に格納された時刻に対応する位置情報に合致しない場合には、前記位置情報及び時刻情報の少なくとも一方に矛盾が発生したと判定する第3のステップと、
前記管理装置は、前記矛盾が発生したときには、前記端末の所有者と関連する人の履歴情報から、現在の端末の所有者の業務状態を推定し、前記端末へ業務状態を送信する第4のステップと、
前記端末が、前記業務状態を受信し、当該業務状態に応じてアプリケーション及びデータへのアクセスを制御する第5のステップと、
を含むことを特徴とするアクセス制御方法。 - 請求項1に記載のアクセス制御方法であって、
前記端末の所有者と関連する人の履歴情報は、前記端末の所有者と関連する人の端末の時刻情報に応じた位置情報と業務状態を蓄積した行動履歴情報であって、
前記第4のステップは、
前記端末の所有者の時刻情報と、前記端末の所有者と関連する人の端末の時刻情報が同一の時刻で、前記端末の所有者の位置情報と、前記端末の所有者と関連する人の端末の位置情報が所定の範囲内であれば、前記端末の所有者と関連する人の業務状態を、前記端末の所有者の業務状態として推定することを特徴とするアクセス制御方法。 - 請求項1に記載のアクセス制御方法であって、
前記端末の所有者と関連する人の履歴情報は、前記端末の所有者と関連する人の端末の時刻情報に応じた位置情報と業務状態を蓄積した行動履歴情報であって、
前記第4のステップは、
前記端末の所有者の位置情報の第1の変化のパターンを取得し、前記端末の所有者と関連する人の端末の過去の位置情報の第2の変化のパターンのうち、前記第1の変化のパターンと一致する第2の変化のパターンを抽出し、当該第2の変化のパターンの前記端末の所有者と関連する人の業務状態を、前記端末の所有者の業務状態として推定することを特徴とするアクセス制御方法。 - 請求項1に記載のアクセス制御方法であって、
前記端末の所有者と関連する人の履歴情報は、前記端末の位置情報と前記スケジュール格納部の位置情報に矛盾が生じた履歴を格納した矛盾履歴情報と、位置情報と業務状態を格納した業務状態情報を含み、
前記第4のステップは、
前記端末の所有者の前記矛盾と一致する履歴を前記矛盾履歴情報から取得し、前記取得した履歴に含まれる位置情報から業務状態を取得し、当該業務状態を前記端末の所有者の業務状態として推定することを特徴とするアクセス制御方法。 - 請求項1に記載のアクセス制御方法であって、
前記第5のステップは、
前記業務状態に応じて、当該端末で起動するアプリケーションの種類、当該端末で操作するデバイス及びアクセスするデータを制限または解除することを特徴とするアクセス制御方法。 - 請求項1に記載のアクセス制御方法であって、
前記端末の所有者と関連する人は、前記端末の所有者が所属する組織の部署と、前記端末の所有者が行う業務のうちの少なくとも一つが同一であることを特徴とするアクセス制御方法。 - プロセッサとメモリを備えた管理装置と、プロセッサとメモリを備えて前記管理装置に接続された端末とを備えたアクセス制御システムであって、
前記端末は、
時刻情報と位置情報を取得する基礎データ取得部と、
業務状態に応じてアプリケーション及びデータへのアクセスを制御する起動制御部と、
前記時刻情報と位置情報及び当該端末の所有者の識別子を前記管理装置へ送信し、前記業務状態を前記管理装置から受信する通信部と、を有し、
前記管理装置は、
前記端末から所有者の識別子と前記位置情報及び時刻情報を受信し、前記端末へ業務状態を送信する通信部と、
前記端末の所有者の時刻に対応する位置情報を格納するスケジュール格納部と、
前記端末から受信した所有者の識別子と前記位置情報及び時刻情報を、前記スケジュール格納部に格納した前記端末の所有者の時刻に対応する位置情報と比較して、当該端末の時刻情報に対応する位置情報が、前記スケジュール格納部に格納された時刻に対応する位置情報に合致しない場合には、前記位置情報及び時刻情報の少なくとも一方に矛盾が発生したと判定し、前記矛盾が発生したときには、前記端末の所有者と関連する人の履歴情報から、現在の端末の所有者の業務状態を推定する業務状態推定部と、
を有することを特徴とするアクセス制御システム。 - 請求項7に記載のアクセス制御システムであって、
前記端末の所有者と関連する人の履歴情報は、前記端末の所有者と関連する人の端末の時刻情報に応じた位置情報と業務状態を蓄積した行動履歴情報であって、
前記業務状態推定部は、
前記端末の所有者の時刻情報と、前記端末の所有者と関連する人の端末の時刻情報が同一の時刻で、前記端末の所有者の位置情報と、前記端末の所有者と関連する人の端末の位置情報が所定の範囲内であれば、前記端末の所有者と関連する人の業務状態を、前記端末の所有者の業務状態として推定することを特徴とするアクセス制御システム。 - 請求項7に記載のアクセス制御システムであって、
前記端末の所有者と関連する人の履歴情報は、前記端末の所有者と関連する人の端末の時刻情報に応じた位置情報と業務状態を蓄積した行動履歴情報であって、
前記業務状態推定部は、
前記端末の所有者の位置情報の第1の変化のパターンを取得し、前記端末の所有者と関連する人の端末の過去の位置情報の第2の変化のパターンのうち、前記第1の変化のパターンと一致する第2の変化のパターンを抽出し、当該第2の変化のパターンの前記端末の所有者と関連する人の業務状態を、前記端末の所有者の業務状態として推定することを特徴とするアクセス制御システム。 - 請求項7に記載のアクセス制御システムであって、
前記端末の所有者と関連する人の履歴情報は、前記端末の位置情報と前記スケジュール格納部の位置情報に矛盾が生じた履歴を格納した矛盾履歴情報と、位置情報と業務状態を格納した業務状態情報を含み、
前記業務状態推定部は、
前記端末の所有者の前記矛盾と一致する履歴を前記矛盾履歴情報から取得し、前記取得した履歴に含まれる位置情報から業務状態を取得し、当該業務状態を前記端末の所有者の業務状態として推定することを特徴とするアクセス制御システム。 - 請求項7に記載のアクセス制御システムであって、
前記起動制御部は、
前記業務状態に応じて、当該端末で起動するアプリケーションの種類、当該端末で操作するデバイス及びアクセスするデータを制限または解除することを特徴とするアクセス制御システム。 - 請求項7に記載のアクセス制御システムであって、
前記端末の所有者と関連する人は、前記端末の所有者が所属する組織の部署と、前記端末の所有者が行う業務のうちの少なくとも一つが同一であることを特徴とするアクセス制御システム。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2014544203A JPWO2014068792A1 (ja) | 2012-11-05 | 2012-11-05 | アクセス制御方法およびアクセス制御システム |
US14/427,612 US20150229644A1 (en) | 2012-11-05 | 2012-11-05 | Access control method and access control system |
PCT/JP2012/078644 WO2014068792A1 (ja) | 2012-11-05 | 2012-11-05 | アクセス制御方法およびアクセス制御システム |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2012/078644 WO2014068792A1 (ja) | 2012-11-05 | 2012-11-05 | アクセス制御方法およびアクセス制御システム |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014068792A1 true WO2014068792A1 (ja) | 2014-05-08 |
Family
ID=50626755
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2012/078644 WO2014068792A1 (ja) | 2012-11-05 | 2012-11-05 | アクセス制御方法およびアクセス制御システム |
Country Status (3)
Country | Link |
---|---|
US (1) | US20150229644A1 (ja) |
JP (1) | JPWO2014068792A1 (ja) |
WO (1) | WO2014068792A1 (ja) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2018179604A1 (ja) * | 2017-03-27 | 2018-10-04 | 株式会社Nttドコモ | データ共有判断装置 |
Families Citing this family (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150006218A1 (en) * | 2013-06-27 | 2015-01-01 | Avaya Inc. | System and method for composing meeting invites in accordance with business rules |
US9716861B1 (en) | 2014-03-07 | 2017-07-25 | Steelcase Inc. | Method and system for facilitating collaboration sessions |
US10664772B1 (en) | 2014-03-07 | 2020-05-26 | Steelcase Inc. | Method and system for facilitating collaboration sessions |
US9766079B1 (en) | 2014-10-03 | 2017-09-19 | Steelcase Inc. | Method and system for locating resources and communicating within an enterprise |
US9955318B1 (en) | 2014-06-05 | 2018-04-24 | Steelcase Inc. | Space guidance and management system and method |
US9380682B2 (en) | 2014-06-05 | 2016-06-28 | Steelcase Inc. | Environment optimization for space based on presence and activities |
US11744376B2 (en) | 2014-06-06 | 2023-09-05 | Steelcase Inc. | Microclimate control systems and methods |
US10433646B1 (en) | 2014-06-06 | 2019-10-08 | Steelcaase Inc. | Microclimate control systems and methods |
US9852388B1 (en) * | 2014-10-03 | 2017-12-26 | Steelcase, Inc. | Method and system for locating resources and communicating within an enterprise |
US10733371B1 (en) | 2015-06-02 | 2020-08-04 | Steelcase Inc. | Template based content preparation system for use with a plurality of space types |
US9921726B1 (en) | 2016-06-03 | 2018-03-20 | Steelcase Inc. | Smart workstation method and system |
US10264213B1 (en) | 2016-12-15 | 2019-04-16 | Steelcase Inc. | Content amplification system and method |
US10491602B2 (en) * | 2017-02-28 | 2019-11-26 | Microsoft Technology Licensing, Llc | Content management based on spatial and temporal information |
US11984739B1 (en) | 2020-07-31 | 2024-05-14 | Steelcase Inc. | Remote power systems, apparatus and methods |
JP2022050899A (ja) | 2020-09-18 | 2022-03-31 | キオクシア株式会社 | メモリシステム |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH11282803A (ja) * | 1998-03-27 | 1999-10-15 | Mitsubishi Electric Corp | 不正アクセス防止システム |
JP2010246060A (ja) * | 2009-04-10 | 2010-10-28 | Hitachi Ltd | 携帯端末紛失防止システム |
JP2011215935A (ja) * | 2010-03-31 | 2011-10-27 | Ntt Docomo Inc | データ閲覧端末及びデータ閲覧制御方法 |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7747645B2 (en) * | 2007-03-17 | 2010-06-29 | Informed Control Inc. | System and method for calendar-based anomalous access detection |
-
2012
- 2012-11-05 US US14/427,612 patent/US20150229644A1/en not_active Abandoned
- 2012-11-05 JP JP2014544203A patent/JPWO2014068792A1/ja active Pending
- 2012-11-05 WO PCT/JP2012/078644 patent/WO2014068792A1/ja active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH11282803A (ja) * | 1998-03-27 | 1999-10-15 | Mitsubishi Electric Corp | 不正アクセス防止システム |
JP2010246060A (ja) * | 2009-04-10 | 2010-10-28 | Hitachi Ltd | 携帯端末紛失防止システム |
JP2011215935A (ja) * | 2010-03-31 | 2011-10-27 | Ntt Docomo Inc | データ閲覧端末及びデータ閲覧制御方法 |
Non-Patent Citations (1)
Title |
---|
YOKO HASE: "A Person Authentication System Using Schedule and GPS data", COMPUTER SECURITY SYMPOSIUM 2004 (CSS2004), vol. II OF II, 20 October 2004 (2004-10-20), pages 631 - 636 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2018179604A1 (ja) * | 2017-03-27 | 2018-10-04 | 株式会社Nttドコモ | データ共有判断装置 |
Also Published As
Publication number | Publication date |
---|---|
US20150229644A1 (en) | 2015-08-13 |
JPWO2014068792A1 (ja) | 2016-09-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2014068792A1 (ja) | アクセス制御方法およびアクセス制御システム | |
EP2936378B1 (en) | Orchestrated interaction in access control evaluation | |
US20150120577A1 (en) | Systems and methods for enterprise management using contextual graphs | |
JP5714937B2 (ja) | 在席確認システム | |
US10013571B2 (en) | Information management system and information management method | |
JP5697626B2 (ja) | アクセス権限管理システム | |
CN114008596A (zh) | 用于非成员用户账户管理的扩展域平台 | |
JP5723338B2 (ja) | データ共有システム | |
CN112989216B (zh) | 同事的推荐方法、装置、计算机设备及存储介质 | |
JP2008299453A (ja) | 情報処理プログラムおよび情報処理システム | |
Groba et al. | Context-dependent access control for contextual information | |
JP2017182293A (ja) | 情報処理装置、情報処理方法、プログラム | |
JP5907292B2 (ja) | 設備備品予約システム、情報処理装置、制御方法、及びプログラム | |
JP2006188922A (ja) | 入退室管理システムおよび方法 | |
JP2004172769A (ja) | 連絡先管理方法、連絡先管理システム、及び勤怠管理システム | |
JP2019083060A (ja) | 情報処理装置、情報処理方法、プログラム | |
JP6435676B2 (ja) | ファイル管理装置、ファイル管理システム及びプログラム | |
US20170351690A1 (en) | Providing notification based on destination of file operation | |
JP2006320022A (ja) | 勤怠管理システム | |
JP2012226672A (ja) | 設備備品予約システム、設備備品予約装置、制御方法、及びプログラム | |
US20220223265A1 (en) | Medical personnel information management method, medical personnel information management device and non-transitory memory computer-readable storage medium | |
JP2016167242A (ja) | 情報端末、情報管理システム及び情報端末の制御プログラム | |
JP5505533B2 (ja) | アクセス制御装置、端末装置、及びプログラム | |
JP5720817B2 (ja) | 設備備品予約システム、情報処理装置、制御方法、及びプログラム | |
JP2014102862A (ja) | アクセス制御装置、端末装置、及びプログラム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 12887791 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2014544203 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14427612 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 12887791 Country of ref document: EP Kind code of ref document: A1 |