Patent ID: 12234122

DETAILED DESCRIPTION

The present invention will be described more thoroughly with reference to the accompanying drawings, in which exemplary embodiments of the present invention are shown. However, the present invention can be implemented in many different forms, and should not be construed as being limited by the embodiments described here. On the contrary, these embodiments are provided such that the present disclosure becomes thorough and complete, and concepts of the present invention are fully conveyed to those skilled in the art.

Some block diagrams shown in the accompanying drawings are functional entities, and they are not necessarily corresponding to physically or logically independent entities. These functional entities can be implemented in a software form, or in one or more hardware modules or integrated circuits, or in different processing apparatuses and/or micro-controller apparatuses.

It is noted by the applicant that authorization for an elevator service request needs to be improved because the existing authorization process described in the background is complex and inflexible, the manager cannot manage an elevator system conveniently, cannot perform operations conveniently, and the workload is large, and passengers also have poor experience.

FIG.1is a schematic diagram of an elevator management system according to an embodiment of the present invention, wherein an authorization management apparatus for an elevator service request according to an embodiment of the present invention is used.FIG.2is a schematic diagram of an application scenario of a personal mobile terminal according to an embodiment of the present invention.FIG.3is a schematic diagram of an input interface of a personal mobile terminal according to an embodiment of the present invention. An elevator management system20, a personal mobile terminal200, and an authorization management apparatus300are described in detail through examples in the following with reference toFIG.1,FIG.2, andFIG.3.

The elevator management system20in the embodiment of the present invention can manage elevator systems installed or run in multiple buildings (for example, in a residential estate), for example, manage a permission of a passenger90accessing a corresponding elevator system. It should be understood that in this application, elevators of the elevator systems can be distinguished or identified by corresponding elevator identifiers. For example, an elevator101aand an elevator101bshown inFIG.2are elevator No. A and elevator No. B of building No. 10 of the residential estate, and can be allocated with corresponding elevator identifiers102aand102bby the manager. The elevator identifier102allocated to each elevator can be uniformly stored, for example, in the authorization management apparatus300of the elevator management system20.

As shown inFIG.2, the elevator identifier102allocated to the elevator101may be a QR code that can be scanned conveniently, or another identifier that can be acquired conveniently, such as a barcode. The elevator identifier102corresponding to an elevator101may be installed beside the elevator101to facilitate scanning. It will be appreciated that the installation position of the elevator identifier102is not limited. In other embodiments, for example, the elevator identifier102may also be presented on a network.

It will be appreciated that elevators of an elevator system may be divided into groups or elevators of multiple elevator systems in different buildings may be divided into groups according to management requirements. For example, elevators with the same passenger access permission management may be divided into one group. Correspondingly, the elevator identifier102may include group information, so that an elevator group to which the elevator101belongs can be learned according to the elevator identifier102.

It should be noted that one elevator101mainly refers to (e.g., one or more) elevator car(s) moving in the same hoistway section of a building.

The personal mobile terminal200may be various intelligent terminals with a wireless communication function (such as a Bluetooth communication function), and can be carried by the passenger90conveniently. The personal mobile terminal200may be provided with a memory, a processor with a computing function, and the like. Specifically, the personal mobile terminal200may be a smart phone, a wearable smart device (such as a smart band), a personal digital assistant (PAD), and the like. A corresponding application program or component (such as an APP) may be installed on the personal mobile terminal200to implement the elevator service request system in the embodiment of the present invention or the function thereof.

As shown inFIG.1, the personal mobile terminal200is provided with a short range communication unit210. Through the short range communication unit210provided therein, the personal mobile terminal200is capable of automatically sensing a wireless signal (such as a first wireless signal123) broadcast by a wireless beacon (for example, a first wireless beacon120installed in an elevator landing region shown inFIG.2) installed in the elevator system10(as shown inFIG.4). Moreover, the short range communication unit210can establish corresponding wireless communication (such as a Bluetooth connection) with the first wireless beacon120when a predetermined condition is met, thus interacting with the wireless beacon in the elevator system, for example, sending an elevator service request command (e.g., an elevator service request command representing an elevator call).

In an embodiment, the personal mobile terminal200is provided with an elevator service request unit250. The elevator service request unit250is configured to automatically send a corresponding elevator service request command to the wireless beacon in the elevator system10when a predetermined condition is met (for example, when a signal strength value is greater than or equal to a corresponding threshold), so that the passenger90can complete, for example, an elevator call request in an operation-free manner.

The elevator service request command generated by the elevator service request unit250may include a starting floor, or may include a starting floor and/or a destination floor. The elevator service request command generated by the elevator service request unit250may be sent, through a short range communication unit210, to a wireless beacon (such as the first wireless beacon120) that has established wireless communication with the short range communication unit210.

Based on the short range communication unit210and the elevator service request unit250in the foregoing example, the passenger90can automatically complete an elevator service requesting operation when carrying the personal mobile terminal200, and the passenger experience is good.

However, for the elevator management system20or an elevator manager, a permission of an elevator service request of the personal mobile terminal200is probably limited according to a management requirement. In other words, authorization of the elevator service request of the personal mobile terminal200needs to be managed. For example, a personal mobile terminal200of a passenger90living at the 9th floor in building No. 10 of a residential estate is only granted with an elevator service request function corresponding to an elevator of the building No. 10 of the residential estate, or is only granted with an elevator service request function corresponding to the 1st floor and the 9th floor of the building No. 10 of the residential estate.

Further, as shown inFIG.1, the personal mobile terminal200in the embodiment of the present invention can generate corresponding authorization request information. To enable the personal mobile terminal200to generate corresponding authorization request information conveniently, the personal mobile terminal200is provided with an acquiring unit220. The acquiring unit220is configured to acquire an elevator identifier102of a corresponding elevator of the elevator system10. In an embodiment, as shown inFIG.2, beside each elevator101, the elevator identifier102corresponding to the elevator101can be installed. In a particular elevator landing region, the passenger90can conveniently acquire the elevator identifier102of the elevator101through the personal mobile terminal200. The acquiring unit220specifically may be an image acquiring device, such as a camera. As shown inFIG.2, the image acquiring device is used to scan a QR code102aof the elevator101aon spot, so that the passenger90can conveniently acquire the elevator identifier.

Further, as shown inFIG.1, in an embodiment, the personal mobile terminal200is further provided with an input unit230. The input unit230can be configured to input at least information about a floor requested to be authorized. For example, after the scanning acquisition process shown inFIG.2is finished, the personal mobile terminal200displays an interface as shown inFIG.3, that is, the input unit230. For example, by sliding up and down to select a floor, the information about the floor requested to be authorized can be input conveniently. For example, it is assumed that the passenger90lives in the 9th floor, when requesting authorization, the passenger90inputs floor information, namely, the 1st floor and the 9th floor, as shown inFIG.2(that is, floors requested to be authorized are the 1st floor and the 9th floor). It will be appreciated that a specific inputting manner of the input unit230is not limited to the foregoing example, and the information about the floor requested to be authorized may include more than 2 floors.

Other information to be input, such as an ID card number used as identity certificate information of the passenger90, can further be input through the input unit230.

Further, as shown inFIG.1, in an embodiment, the personal mobile terminal200is further provided with an authorization request generating and sending unit240. The authorization request generating and sending unit240is configured to generate authorization request information and send the authorization request information. The authorization request information includes the acquired elevator identifier102and a terminal identifier of the personal mobile terminal200mapped to the elevator identifier102. The terminal identifier of the personal mobile terminal200can identify the personal mobile terminal200, and therefore can identify the passenger90using the personal mobile terminal200. The terminal identifier may be a communication number (for example, a mobile phone number when the personal mobile terminal200is a mobile phone); the terminal identifier may also be a unique identification code of the personal mobile terminal200, or even an ID of the passenger90using the personal mobile terminal200.

In an embodiment, the authorization request generating and sending unit240is further configured to establish a mapping relationship between the acquired elevator identifier102and the terminal identifier of the personal mobile terminal200such that the terminal identifier is mapped to the elevator identifier102or the elevator identifier102is mapped to the terminal identifier. For example, a mapping relationship is established between the elevator identifier102aacquired through scanning and the communication number of the personal mobile terminal200, thereby forming corresponding authorization request information. It will be appreciated that when the terminal identifier is mapped to the elevator identifier102, it also indicates that the elevator identifier102is mapped to the terminal identifier. A mapping relationship is established therebetween to facilitate subsequent authorization management.

In an embodiment, the generated authorization request information may include a floor requested to be authorized, which is input in the input interface as shown inFIG.3, and may further include identity certificate information (such as an ID card, an employee's card, and the like) of a passenger90. The identity certificate information may be pre-stored in the personal mobile terminal200, and definitely may also be acquired through, for example, the input unit230and/or the acquiring unit220in real time. The identity certificate information helps the manager quickly determine whether to allow authorization based on the authorization request information.

The personal mobile terminal200can establish a communication connection with the authorization management apparatus300through various types of wireless networks. Therefore, the authorization request generating and sending unit240of the personal mobile terminal200can send the authorization request information to the authorization management apparatus300corresponding to the elevator system10in real time.

Further, as shown inFIG.1, the authorization management apparatus300may be implemented by various types of computer devices, and may be provided in a building or provided at other places remotely, and its installation location is not limited. Authorization management for multiple elevator systems may be implemented by one authorization management apparatus300. In an embodiment, the authorization management apparatus300may be provided in a property management system of a building where the elevator system is located, thus facilitating a property manager to realize authorization management for an elevator service request.

The authorization management apparatus300may be provided with a receiving unit310. The receiving unit310is configured to receive authorization request information from various personal mobile terminals200(for example, authorization request information is transmitted through a communication connection established between the personal mobile terminal200and the authorization management apparatus300), so that the authorization request information is centralized and processed in the authorization management apparatus300.

The authorization management apparatus300is further provided with an authorization management unit320. The authorization management unit320is configured to determine, at least according to a mapping relationship between the elevator identifier102and the terminal identifier of the personal mobile terminal200in the authorization request information, whether the authorization request information from the corresponding personal mobile terminal200is allowed to be authorized.

In an embodiment, as shown in Table 1 below, the authorization management unit320is further configured to display multiple pieces of the authorization request information in a list as shown in Table 1, such that the manager grasps the authorization request information conveniently and manually performs authorization operation conveniently.

TABLE 1Floor requestedAuthori-Elevatorto beTerminalRequestzationidentifierauthorizedidentifiertimeoperation10-A19130XXXXXXXX2017 Oct. 3110-BB19131XXXXXXXX2017 Oct. 3101-C91132XXXXXXXX2017 Oct. 3120-D112133XXXXXXXX2017 Oct. 3020-A711134XXXXXXXX2017 Oct. 29

As shown in Table 1, “elevator identifier” and “terminal identifier” of the authorization request information are corresponding to or mapped to each other in the same row. The authorization request information further includes “floor requested to be authorized,” “request time,” and other items, which are all presented in the form of a list. Using the first row as an example, 10-A refers to elevator No. A of building No. 10 of a residential estate, and is another expression form of the QR code102aof the elevator101ashown inFIG.2, which can be read by the manager conveniently; “19” represents input floors requested to be authorized as shown inFIG.3, that is, the 1st floor and the 9th floor; “130XXXXXXXXX” is a communication number of the personal mobile terminal200scanning the QR code102a, and represents a terminal identifier; and “2017-10-31” represents a request time.

It should be noted that the arrangement of the authorization request information in the list is not limited to the example shown in Table 1. For example, the authorization request information can be arranged according to a chronological order of the request time. Authorization request information corresponding to the same elevator system or the same elevator may be classified and arranged together; or authorization request information may be classified and arranged according to terminal identifiers or floors requested to be authorized.

Further, as shown inFIG.1, the authorization management unit320may be configured to determine, based on any of the following authorization modes, whether the authorization request information is allowed to be authorized: (a) fully auto-allowed authorization or fully auto-disallowed authorization, (b) auto-allowed authorization or auto-disallowed authorization by batch, and (c) allowed authorization or disallowed authorization fully based on manual input.

In an embodiment, with reference to the content shown in Table 1, when the authorization management unit320is configured to determine, based on the authorization mode (c), whether the authorization request information is allowed to be authorized, multiple pieces of the authorization request information are displayed in the form of a list (for example, the form shown in Table 1). An “authorization operation” column is further set in the list. The authorization operation column includes icons (such as “” and “”) that are set corresponding to each piece of authorization request information and can be clicked or activated through manual input. The manager can operate on the “authorization operation” column to determine whether to allow authorization of the authorization request information in the corresponding row. For example, clicking or activating “” represents allowing authorization of the authorization request information, and clicking or activating “” represents not authorizing the authorization request information, that is, not authorizing the current request of the personal mobile terminal200. Specifically, if the elevator, the elevator system, or the elevator group needs to limit the access permission of each personal mobile terminal, the authorization management unit320can perform authorization management in the authorization mode (c) shown above, thus ensuring the security and reliability of permission management.

In another embodiment, when determining whether the authorization request information is allowed to be authorized based on the authorization mode (a), the authorization management unit320may be configured to automatically allow and/or automatically disallow authorization of all the authorization request information. Specifically, if the elevator, the elevator system, or the elevator group does not limit the access permission, the authorization management unit320can be configured to use the fully auto-allowed authorization in the authorization mode (a). Alternatively, if the elevator, the elevator system, or the elevator group has a permission limitation of not allowing access in the current time period, the authorization management unit320may be configured to use the fully auto-disallowed authorization in the authorization mode (a). As such, the authorization operation efficiency is significantly improved, and the workload of the manager is reduced.

In still another embodiment, when determining whether the authorization request information is allowed to be authorized based on the authorization mode (b), the authorization management unit320may be configured to automatically allow authorization/automatically disallow authorization of authorization request information in a corresponding batch. As such, at least partially auto-allowed authorization/auto-disallowed authorization is achieved, which also helps improve the authorization operation efficiency and reduce the work load of the manager while ensuring the security and reliability of the permission management. When the authorization mode (b) is used, a first terminal identifier list of personal mobile terminals200for auto-allowing authorization by batch and/or a second terminal identifier list of personal mobile terminals200for auto-disallowing authorization by batch may further be acquired. For example, the first terminal identifier list of personal mobile terminals200for auto-allowing authorization by batch which is pre-stored in the authorization management apparatus300may be acquired from the authorization management apparatus300through browsing. Specifically, the first terminal identifier list includes, for example, terminal identifiers (such as communication numbers) of personal mobile terminals200that do not have an access permission limitation with respect to an elevator or all elevators. As such, in the authorization management unit320, all authorization request information corresponding to the terminal identifiers in the first terminal identifier list is allowed to be authorized by batch. A similar exemplary operation can be performed for the second terminal identifier list.

It will be appreciated that remaining authorization request information that is not processed in the authorization mode (b) can be manually processed in the authorization mode (c). In an embodiment, after determining whether the authorization request information is allowed to be authorized based on the authorization mode (a) or the authorization mode (b), if the manager needs to manually verify or update the authorization request information, for which the operation of determining whether authorization is allowed has been performed, the manager can continue to perform, based on the authorization mode (c), an operation of manually updating at least part of the authorization request information determined based on the authorization mode (a) or the authorization mode (b) and determining whether the part of the authorization request information is allowed to the authorized.

It should be noted that the authorization management unit320is further configured to use different authorization modes for different elevators, different elevator systems, or different elevator groups. For example, the authorization mode (a) is used for authorization request information corresponding to elevators in a predefined elevator group M; the authorization mode (b) is used for authorization request information corresponding to elevators in a predefined elevator group N; and the authorization mode (c) is used for authorization request information corresponding to elevators in a predefined elevator group F.

Further, as shown inFIG.1, after the authorization operation is completed in the authorization management apparatus300, the authorization management apparatus300will return an “authorization result” indicating, for example, authorization is allowed or disallowed, to the personal mobile terminal200. The personal mobile terminal200can display the authorization result.

For example, if the authorization request information in the first row of Table 1 which is sent by the personal mobile terminal200is allowed to be authorized, the personal mobile terminal200will obtain a permission of automatically requesting an elevator service at the 1st floor an the 9th floor of the elevator101a. For example, the personal mobile terminal200can automatically send an elevator service request command representing an elevator call operation.

It will be appreciated that if the authorization request information does not include a floor requested to be authorized, the personal mobile terminal200will obtain a permission of requesting an elevator service at each floor of the elevator101a.

In an embodiment, in the case where the elevators101are divided into elevator groups according to the foregoing example, if authorization request information of a personal mobile terminal200corresponding to an elevator in an elevator group is allowed to be authorized, the personal mobile terminal200can be authorized to send an elevator service request command to another elevator in the elevator group. In other words, an “authorization result” of authorization request information of a personal mobile terminal200corresponding to one elevator in an elevator group can be shared by and applied to another elevator in the elevator group. For example, if the personal mobile terminal200obtains a permission of automatically requesting an elevator service in the elevator101a, according to a group relationship between the elevator101aand the elevator101bas shown inFIG.2, the personal mobile terminal200can automatically obtain a permission of automatically requesting an elevator service in the elevator101b.

FIG.4is a schematic diagram of an elevator system in which a personal mobile terminal according to an embodiment of the present invention is applied. The personal mobile terminal200is further configured to be able to automatically send an elevator service request command to the corresponding elevator of the elevator system10if the authorization request information is allowed to be authorized. In other words, the authorized personal mobile terminal200can automatically complete an elevator service request in the elevator system10in the example shown inFIG.4.

As shown inFIG.4, the elevator system10may be installed in various buildings, and the elevator system10includes multiple elevator cars110that move in a hoistway of a building.FIG.1shows two elevator cars, that is, elevator cars110-1and110-2. Each elevator car110is under control (for example, scheduling control, movement control, and the like) of an elevator controller140in the elevator system10, so as to move in the hoistway or stop at a corresponding landing. Generally, the elevator controller140needs to acquire an elevator service request command (for example, an elevator service request command representing an elevator call request, that is, an elevator call request command) from an elevator landing region410of each floor to control running of the elevator based on the command, for example, control scheduling of the elevator cars110. It will be appreciated that a specific control mode or control principle of the elevator controller140for one or more elevator cars110is not limited, and a specific structure, arrangement mode or the like of the elevator controller140is not limited either.

To acquire the elevator call request command from each elevator landing region410, the elevator system10is provided with a first wireless beacon120. The first wireless beacons120may be installed in the elevator landing regions410of the elevator system10(as shown inFIG.2). For example, at least one first wireless beacon120is installed in the elevator landing region of each floor, so that a first wireless signal123transmitted or broadcast by the first wireless beacon120can roughly cover at least each elevator landing region effectively, thereby forming a corresponding coverage.

Further, as shown inFIG.4, in an embodiment, an automatic elevator call system20of the elevator system10may be further provided with one or more second wireless beacons130(for example, second wireless beacons130-1and130-2). Each second wireless beacon130is installed in a corresponding elevator car110. For example, one second wireless beacon130-1is provided in the elevator car110-1, and one second wireless beacon130-2is provided in the elevator car110-2. In an embodiment, the second wireless beacon130is installed on a destination floor registration control board in the elevator car110, and integrated on the destination floor registration control board. The installation mode of the second wireless beacon130with respect to the elevator car110is not limited to the foregoing examples.

The second wireless beacon130may transmit or broadcast a second wireless signal133, for example, continuously (e.g., at intervals of a relatively short time) broadcast the second wireless signal133. The signal strength of the second wireless signal133is attenuated as the broadcast distance increases. The second wireless signal133broadcast by the second wireless beacon130can roughly effectively cover the region in the elevator car110where the second wireless beacon130is installed, thereby forming a corresponding coverage.

It should be noted that the second wireless beacon130is coupled to the elevator controller140. Therefore, during operation of each elevator car110, the second wireless beacon130can acquire desired information, for example, current floor information, travel direction information, and the like of the elevator car110, from the elevator controller140in real time, package the floor information and/or the travel direction information (the travel direction information includes, for example, “travel upward,” “travel downward,” and “halt”) into a Bluetooth data signal and the like, and broadcast the information as a second wireless signal.

In an embodiment, the first wireless beacon120and/or the second wireless beacon130may be a Bluetooth module, and specifically may be a Bluetooth Low Energy (BLE) module. Correspondingly, the first wireless signal123transmitted or broadcast by the first wireless beacon120and/or the second wireless signal133transmitted or broadcast by the second wireless beacon130may be a Bluetooth signal (such as a BLE signal).

In an embodiment, the first wireless signal123(such as a BLE signal) may include a wakeup signal for waking up a personal mobile terminal200. A personal mobile terminal200sensing the wakeup signal can wake up a corresponding application component (such as an automatic elevator call APP) of the personal mobile terminal200to work. Specifically, the first wireless signal123may further include a universally unique identifier (UUID) reflecting the identity of the first wireless beacon120, and/or a data signal about floor location information of the first wireless beacon120. The second wireless signal133may further include a UUID reflecting the identity of the second wireless beacon130, and/or a data signal about current floor location information of the second wireless beacon130.

Further, as shown inFIG.4, the elevator system10may include personal mobile terminals200carried by passengers90, for example, personal mobile terminals200-1and200-2carried by two passengers respectively. Each personal mobile terminal200is configured to sense a wireless signal broadcast by a wireless beacon in the elevator system10when a distance condition is met, for example, sense the first wireless signal123broadcast by the first wireless beacon120and sense the second wireless signal133broadcast by the second wireless beacon130. Moreover, in an embodiment, each authorized personal mobile terminal200is capable of automatically sending a corresponding elevator service request command to a wireless beacon in the elevator system10if a corresponding condition is met, for example, sending an elevator service request command representing an elevator call to the first wireless beacon120, and sending an elevator service request command representing a destination floor to the second wireless beacon130.

The personal mobile terminal200in the foregoing embodiment can conveniently acquire an elevator identifier as well as mapping data between the elevator identifier and a terminal identifier, and can generate and send authorization request information conveniently. Correspondingly, the authorization management apparatus300can conveniently learn the mapping data between the elevator identifier and the terminal identifier through the authorization request information, thereby easily knowing an access permission of which elevator should be granted to which passenger, so that access permission management for the elevator system can be realized easily, and the authorization operation also can be displayed easily. Particularly, in the elevator management system20in the foregoing example, it is unnecessary to perform authorization management for each passenger90face to face, and the whole authorization requesting process and the authorization management process are fast, convenient, and efficient.

FIG.5is a flowchart of an authorization requesting method for an elevator service request according to an embodiment of the present invention. The authorization requesting method shown inFIG.5is mainly completed in the personal mobile terminal200shown inFIG.1. The authorization requesting method is illustrated through examples in the following with reference toFIG.1toFIG.3andFIG.5.

In step S510, an elevator identifier of a corresponding elevator in an elevator system is acquired. For example, in the scenario shown inFIG.2, if a passenger90wants to obtain a permission to access an elevator101a, that is, be authorized to send an elevator service request command to the elevator101a, the passenger90may scan a QR code102aof the elevator101a, that is, an elevator identifier102a, through an acquiring unit220of a personal mobile terminal200, thereby obtaining the elevator identifier of the elevator101a, and may also obtain other related information of the elevator101a.

In step S520, a mapping relationship is established, and authorization request information is generated. In this step, because the terminal identifier of the personal mobile terminal200is known to the personal mobile terminal200or is pre-stored, after the elevator identifier of the elevator101ais acquired, a mapping relationship between the terminal identifier and the elevator identifier can be established to form mapping data. That is, the terminal identifier is mapped to the elevator identifier102a, or the elevator identifier102ais mapped to the terminal identifier. Further, authorization request information including the mapping relationship is generated. The authorization request information includes, for example, the elevator identifier102a, the terminal identifier, and the mapping relationship therebetween. In another embodiment, the authorization request information may further include identity certificate information (for example, an ID card image required in an authorization verification process, or the like) of a passenger90and/or a floor requested to be authorized (for example, multiple pieces of input floor information as shown inFIG.3).

In step S530, the authorization request information is sent. In this step, the authorization request information generated by the personal mobile terminal200can be remotely sent to the authorization management apparatus300.

The steps S510to S530above illustrate a main process of one authorization request. By repeating the steps S510to S530above, multiple authorization requests can be completed, for example, authorization requests for different floors of the same elevator, authorization requests for different elevators, and even authorization requests for the same elevator in different time periods (for example, an authorization request is performed again after an authorization expires). It will be appreciated that the whole authorization requesting process is simple and convenient.

FIG.6is a flowchart of an authorization management method for an elevator service request according to an embodiment of the present invention. The authorization management method shown inFIG.6is mainly completed in the authorization management apparatus300shown inFIG.1. The authorization requesting method is illustrated in the following with reference to Table 1 andFIG.6.

In step S610, authorization request information from one or more personal mobile terminals200is received.

In step S620, the authorization request information is displayed in a list. For example, multiple pieces of authorization request information are displayed in a list shown in Table 1, and a mapping relationship between elevator identifiers and terminal identifiers will also be presented in front of a manager intuitively. The manager can perform an authorization operation according to existing information.

In step S630, it is determined whether authorization request information from a corresponding personal mobile terminal is allowed to be authorized. In this step, based on an authorization mode (c) which is determined to be used, that is, allowed authorization or disallowed authorization fully based on manual input, a manual authorization operation is performed on each piece of authorization request information one by one. For example, by operating on the “authorization operation” column shown in Table 1, the manager can determine whether to allow authorization of authorization request information in a corresponding row. Clicking or activating “” represents allowing authorization of the authorization request information, and clicking or activating “” represents not authorizing the authorization request information. In the manual operation process, it is determined, at least according to the mapping relationship between the elevator identifier and the terminal identifier of the personal mobile terminal in the authorization request information, whether the authorization request information from the corresponding personal mobile terminal is allowed to be authorized. For example, as shown in the first row in Table 1, it can be determined, according to information about the terminal identifier200stored in the authorization management apparatus300, whether to allow authorization of an elevator service request for the elevator identifier “10-A” corresponding to the terminal identifier200. If authorization is allowed, “” is activated in the “authorization operation” column, and if the elevator service request is not authorized, “” is activated in the “authorization operation” column.

In step S640, an authorization result is returned to the corresponding personal mobile terminal200.

So far, a method process of completing authorization management by manual input of a manager is basically finished.

FIG.7is a flowchart of an authorization management method for an elevator service request according to another embodiment of the present invention. The authorization management method shown inFIG.7is mainly completed in the authorization management apparatus300shown inFIG.1. The authorization requesting method is illustrated in the following with reference toFIG.1andFIG.7.

In step S710, authorization request information from one or more personal mobile terminals200is received.

In step S720, the authorization request information is displayed in a list. For example, multiple pieces of authorization request information are displayed in a list, and a mapping relationship between elevator identifiers and terminal identifiers will also be presented in front of a manager intuitively. In another embodiment, the authorization request information may not be displayed according to a specific situation.

In step S730, it is fully auto-determined, in an authorization mode (a), whether the authorization request information from the personal mobile terminal is allowed to be authorized. In this step, authorization verification is performed on all the authorization request information automatically based on the already selected authorization mode (a), that is, fully auto-allowed authorization or fully auto-disallowed authorization. For example, all the authorization request information is automatically allowed to be authorized, or all the authorization request information is automatically disallowed to be authorized.

In step S740, an authorization result is returned to the corresponding personal mobile terminal200.

So far, a method process of completing fully auto-authorization management without depending on a manager is basically finished.

FIG.8is a flowchart of an authorization management method for an elevator service request according to still another embodiment of the present invention. The authorization management method shown inFIG.8is mainly completed in the authorization management apparatus300shown inFIG.1. The authorization requesting method is illustrated in the following with reference to Table.1andFIG.8.

In step S810, authorization request information from one or more personal mobile terminals200is received.

In step S820, the authorization request information is displayed in a list. For example, multiple pieces of authorization request information are displayed in a list, and a mapping relationship between elevator identifiers and terminal identifiers will also be presented in front of a manager intuitively. In another embodiment, the authorization request information may not be displayed according to a specific situation.

In step S830, it is fully auto-determined, in an authorization mode (b), whether the authorization request information from the personal mobile terminal is allowed to be authorized. In this step, authorization verification is performed on authorization request information in each batch automatically based on the selected authorization mode (b), that is, auto-allowed authorization or auto-disallowed authorization by batch. For example, all the authorization request information is automatically allowed to be authorized, or all the authorization request information is automatically disallowed to be authorized.

In an embodiment, a first terminal identifier list of personal mobile terminals200for auto-allowing authorization by batch and/or a second terminal identifier list of personal mobile terminals200for auto-disallowing authorization by batch may further be acquired. For example, the first terminal identifier list of personal mobile terminals200for auto-allowing authorization by batch which is pre-stored in the authorization management apparatus300may be acquired from the authorization management apparatus300through browsing. Specifically, the first terminal identifier list includes, for example, terminal identifiers (such as communication numbers) of personal mobile terminals200that do not have an access permission limitation with respect to an elevator or all elevators. As such, in the authorization management unit320, all authorization request information corresponding to the terminal identifiers in the first terminal identifier list is allowed to be authorized by batch. A similar exemplary operation can be performed for the second terminal identifier list.

In step S840, an authorization result is returned to the corresponding personal mobile terminal200.

So far, a method process of completing auto-authorization management by batch is basically finished.

It should be noted that at least two of the foregoing method processes shown inFIG.6toFIG.8can be performed in the same authorization management apparatus300. For example, the authorization management apparatus300manages authorization request information corresponding to an elevator A, an elevator B, and an elevator C. For the elevator A, the authorization mode (c) is selected, and authorization management for authorization request information is completed based on the authorization management method shown inFIG.8. For the elevator B, the authorization mode (a) is selected, and authorization management for authorization request information is completed based on the authorization management method shown inFIG.7. For the elevator C, the authorization mode (b) is selected, and authorization management for authorization request information is completed based on the authorization management method shown inFIG.8.

It will be appreciated that the authorization management method for an elevator service request in the foregoing example can be carried out for one piece of authorization request information or one batch of authorization request information. The whole authorization management process is simple and efficient, and is convenient for a manager to perform an authorization management operation. Especially, for the manager, the authorization management processes in the methods inFIG.7andFIG.8are simpler and more efficient.

It should be noted that the personal mobile terminal200in the foregoing embodiment of the present invention can be implemented by computer program instructions, for example, implemented through a special APP. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or another programmable data processing device to form the personal mobile terminal200in the embodiment of the present invention. Moreover, the processor of the computer or another programmable data processing device executes these instructions to create units or components for implementing these flowcharts and/or blocks and/or functions/operations specified in on or more flowchart blocks.

It should be noted that the authorization management apparatus300in the foregoing embodiment of the present invention can be implemented by computer program instructions, for example, implemented through a special computer program. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or another programmable data processing device to form the authorization management apparatus300in the embodiment of the present invention. Moreover, the processor of the computer or another programmable data processing device executes these instructions to create units or components for implementing these flowcharts and/or blocks and/or functions/operations specified in on or more flowchart blocks.

Moreover, these computer program instructions can be stored in a computer readable memory. These instructions can instruct a computer or another programmable processor to implement functions in a specific manner, such that these instructions stored in the computer readable memory construct a manufactured product including instruction components that implement functions/operations specified in one or more blocks of the flowcharts and/or block diagrams.

It should be further noted that in some alternative implementations, the functions/operations shown in the blocks may not occur according to the order shown in the flowchart. For example, two blocks shown sequentially may actually be executed basically at the same time or these blocks can be executed in a reversed order sometimes, which specifically depends on the involved functions/operations.

It should be noted that elements (including flowcharts and block diagrams in the accompanying drawings) disclosed and depicted in the specification mean logic boundaries between the elements. However, according to software or hardware engineering practice, the depicted elements and functions thereof can be executed on a machine via a computer executable medium. The computer executable medium has a processor capable of executing a program instruction stored on the computer executable medium. The program instruction is used as a single-chip software structure, an independent software module, or a module using an external program, code, service and the like, or a combination thereof, and all the execution solutions can fall within the scope of this disclosure.

Although different non-limitative implementation solutions have specifically illustrated components, implementation solutions of the present invention are not limited to these specific combinations. It is possible to use a combination of some of components or features in any non-limiting implementation solution with features or components from any other non-limiting implementation solution.

Although a specific step sequence is shown, disclosed and claimed, it should be understood that steps can be implemented in any order, separated or combined, and will still benefit from this disclosure unless otherwise specified.

The above description is exemplary, and is not defined to limit the present invention. Various non-limitative implementation solutions are disclosed. However, those of ordinary skill in the art can realize that various modifications and changes will fall within the scope of the appended claims according to the foregoing teachings. Therefore, it will be appreciated that disclosure content apart from the specific disclosure can be carried out within the scope of the appended claims. Due to this reason, the appended claims should be read up to determine the true scope and content.