CN114489350A

CN114489350A - Input method calling method and related equipment

Info

Publication number: CN114489350A
Application number: CN202111610264.5A
Authority: CN
Inventors: 贾宇刚
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2021-12-27
Filing date: 2021-12-27
Publication date: 2022-05-13
Anticipated expiration: 2041-12-27
Also published as: WO2023124141A1; WO2023124141A9; CN114489350B

Abstract

The application provides an input method calling method and related equipment. According to the input method calling method, the electronic equipment can trigger the input equipment to monitor when the input method application is started, and after the input method application receives the monitoring callback information, the input method to be called is determined according to the type of the input equipment included in the monitoring callback information. According to the method, the electronic equipment can adaptively provide a more reasonable input method according to the input mode and the input equipment, the user does not need to manually switch the input method, and the user experience is improved.

Description

Input method calling method and related equipment

Technical Field

The application relates to the technical field of terminals, in particular to an input method calling method and related equipment.

Background

At present, terminal devices such as mobile phones and tablet computers are developed more and more rapidly. With the continuous development of terminal devices, user requirements are changing continuously, and the final basic communication requirements are gradually changed into multi-dimensional communication and entertainment requirements such as vision, hearing, touch and the like, so that more and more terminal device manufacturers increasingly pay more attention to human-computer interaction. In order to improve the usability and user friendliness of the terminal device, some manufacturers have developed some devices for use with the terminal device. Such as a stylus, keyboard, etc. Users can better fulfill their own input requirements with these input devices. It can be appreciated that due to differences in the manner in which users make inputs via these input devices (e.g., touch inputs and keyboard inputs), there may be differences in the input modes that different input devices are often adapted to. For example, stylus input may be applied to handwriting input methods and keyboard input may be applied to keyboard input methods.

However, regardless of which input device the user uses for input, the input interface displayed first is often the default input interface set by the user. If the input equipment is changed, the user needs to manually switch the input method, and the user experience is influenced.

Therefore, how to adaptively call the input method according to the input device is a problem to be solved urgently at present.

Disclosure of Invention

The application provides an input method calling method and related equipment, which can determine the type of input equipment according to a generated input event, find an input method corresponding to the type of the input equipment in an input method calling rule, and then call the input method. By the method, the input method can be adaptively called according to the input equipment used by the user, the user does not need to manually switch the input method, the redundant operation of the user is reduced, and the user experience is improved.

In a first aspect, the present application provides an input method calling method. The method can be applied to electronic devices. The method can comprise the following steps: receiving a first operation, and responding to the first operation to display a first interface; the first operation is an input operation performed by a first input mode; the first interface displays a first input method; the first input method is an input method corresponding to the first input mode; receiving a second operation, and responding to the second operation to display a second interface; the second operation is an input operation performed by a second input mode; the second interface displays a second input method; the second input method is an input method corresponding to the second input mode; wherein the first input method is different from the second input method.

In the scheme provided by the application, at the first moment, the electronic device may receive an input operation performed by a user through a first input method, and in response to the input operation, the electronic device may display a first interface including a first input method. At the second moment, the electronic device may receive an input operation performed by the user through the second input method, and in response to the input operation, the electronic device may display a second interface including the second input method. The first input method corresponds to the first input mode, and the second input method corresponds to the second input mode. That is, the electronic device may determine an input method to be invoked according to an input manner of the user, and display the input method on the user interface. The input method is called by the input method calling mode, the input method called and displayed by the electronic equipment can be determined according to the input mode of the user, and the input method called each time is not a default input method or a historical input method. In this case, the user does not need to manually switch to an input method more matched with the current input mode, the use experience of the user is fully considered, and the user experience is improved.

In some embodiments of the present application, the first input mode may be a finger touch mode, a stylus touch mode, or a keyboard input mode. The corresponding first operation can be a finger touch operation, a stylus touch operation and a keyboard knocking operation. The second input mode may be a finger touch mode, a stylus touch mode, or a keyboard input mode. The corresponding second operation can be a finger touch operation, a stylus touch operation and a keyboard knocking operation.

For example, the first input mode may be a finger touch mode, and the second input mode may be a stylus touch mode. The user firstly inputs on the electronic equipment through finger touch operation, and the electronic equipment calls the pinyin input method and displays a soft keyboard on a user interface for the user to input. Then, the user uses the handwriting pen to input, the electronic device detects that the input device currently used by the user is a touch screen-handwriting pen, and the electronic device calls a handwriting input method and displays a handwriting area on a user interface for the user to input.

With reference to the first aspect, in a possible implementation manner of the first aspect, the first input manner is a manner of inputting by using a first input device; the second input mode is a mode of inputting by using second input equipment; the first input method is an input method corresponding to the first input mode, and specifically includes: the first input method is an input method corresponding to a first equipment type; the first equipment type is the equipment type corresponding to the first input equipment; the second input method is an input method corresponding to the second input mode, and specifically includes: the second input method is an input method corresponding to a second equipment type; the second device type is a device type corresponding to the second input device.

In the solution provided in the present application, the first input mode may be a mode in which input is performed by using a first input device, and the second input mode may be a mode in which input is performed by using a second input device. The electronic device includes a correspondence between a device type of the input device and the input method. After receiving the input operation of the user, the electronic device may find a corresponding input method according to the input device utilized by the input operation, and call and display the input method. That is, the electronic device may determine the input method that needs to be invoked according to the device type of the input device. The user does not need to manually switch to the input method which is more matched with the current input equipment, the use experience of the user is fully considered, and the user experience is improved.

In some embodiments of the present application, the electronic device may determine the input device based on the input mode, and further determine the input method that needs to be invoked. For example, in the case that the first input mode is a keyboard input mode, the first input device is a keyboard, and the electronic device may determine that the first device type is the keyboard based on the first input device. For example, when the first input mode is a finger touch mode, the first input device is a finger, and the electronic device may determine that the first device type is a finger. When the first input mode is a stylus pen touch mode, the first input device is a stylus pen, and the electronic device may determine that the first device type is the stylus pen.

In some embodiments of the present application, the electronic device may further determine the input method to be invoked according to the input mode and the input device. For example, when a user performs input in a finger touch manner or a stylus touch manner, the input device is a touch screen, but the generated input events are different due to different operations (different input manners) on the touch screen. In this case, the electronic device may determine the device type of the input device in combination with the input method and the input device, thereby determining the input method to be invoked. For example, in a case that the first input manner is a finger touch manner, the first input device is a touch screen, and the electronic device may determine that the first device type is a touch screen-finger based on the first input manner and the first input device. In the case that the first input mode is a stylus touch mode, the first input device is a touch screen, and the electronic device may determine that the first device type is a touch screen-stylus based on the first input mode and the first input device.

With reference to the first aspect, in a possible implementation manner of the first aspect, before the displaying the first interface in response to the first operation, the method further includes: sending a registration monitoring request to an input method management service in the electronic equipment through an input method application in the electronic equipment based on a first interface; the registration monitoring request is used for requesting the input method management service to monitor the input equipment; sending a first message to an input management service in the electronic device through the input method management service; the first message is used to request the input management service to listen to an input device.

In the scheme provided by the application, the electronic equipment can call the input method according to the input equipment only by monitoring the input equipment. Specifically, the input method application in the electronic device may send a registration monitoring request to the input method management service in the electronic device based on the first interface, and the input method management service then sends a first message to the input management service to request to monitor the input device. It is understood that what is listening is essentially implemented in the electronic device is the input management service. The input management service enables listening to input devices by listening to input events. That is, the input management service may determine the input device by inputting an input event reported by the distributor. Once the input device corresponding to the input event is changed, the input management service can transmit the changed input device type to the input method management service, and then call back to the input method application, and then the input method is used for determining the input method to be switched. The monitoring input device mentioned in the above process is a precondition for realizing the calling of the input method according to the type of the input device, and is an indispensable step for realizing the adaptive calling of the input method.

It will be appreciated that, in practice, an input method application does not require that a registration snoop request be sent to the input method management service every time an input method is invoked. In some embodiments of the present application, in the case that the lifecycle of the input method is not over, the input method application may invoke or switch the input method without sending a registration listening request.

In some embodiments of the present application, the user may manually switch the input method application used. In this case, although the input method application previously used by the user has requested to listen to the input device, the switched input method application needs to send a listening request to the input method management service again.

It should be noted that the first interface is a custom interface, and is used for sending the registration listening request. The related description of the first interface can refer to the following text, and is not explained herein.

With reference to the first aspect, in a possible implementation manner of the first aspect, the displaying a first interface in response to the first operation specifically includes: generating a first input event in response to the first operation; the first input event is an input event generated for the first input device; calling the first input method based on the first input event, and displaying the first interface; responding to the second operation, displaying a second interface, specifically comprising: generating a second input event in response to the second operation; the second input event is an input event generated for the second input device; and calling the second input method based on the second input event, and displaying the second interface.

In the scheme provided by the application, the electronic equipment can generate an input event in response to the input operation of the user. The electronic device may determine the input device type based on the input event, thereby determining the input method to invoke. Specifically, an input event distributor in the electronic device may report the generated input event to an input management service, and the input management service may determine the type of the input device according to the input event, transfer the type of the input device to an input method management service, and finally transfer the type of the input device to an input method application, thereby invoking a corresponding input method. By the mode, a user does not need to manually switch to an input method which is more matched with the current input equipment, the use experience of the user is fully considered, and the user experience is improved. In addition, the user need not use an application other than the input method application to determine the input method that needs to be invoked.

With reference to the first aspect, in a possible implementation manner of the first aspect, the invoking a first input method based on the first input event specifically includes: determining the first equipment type based on the first input event through the input management service, and reporting the first equipment type to the input method management service; comparing, by the input management service, the first device type to a first historical device type; the first historical device type is a device type of an input device corresponding to a last input event of the first input event generated by the electronic device; if the first equipment type is different from the first historical equipment type or the first historical equipment type does not exist, sending monitoring callback information to the input method application through the input method management service based on a second interface; the interception callback information comprises the first device type; the input method application searches the first input method in an input method calling rule according to the first equipment type in the monitoring callback information and calls the first input method; the input method calling rule comprises a corresponding relation between the equipment type corresponding to the input equipment and the input method.

In the scheme provided by the application, the input management service may determine the device type of the input device based on the input event, compare the current input device type with the historical device type, and determine whether the current input device type needs to be transferred to the input method management service according to the comparison result. If the current input device type is different from the historical device type or no historical device type exists, the input management service may pass the input device type to the input method management service. That is, if the type of the device input by the user changes or the user uses the input device for input for the first time, the input management service in the electronic device may transmit the type of the input device to the input method management service, and then transmit the input method management service to the input method application, and finally the input method application finds the input method corresponding to the type of the input device according to the input method calling rule, and calls and displays the input method. Understandably, in this way, the user does not need to manually switch the appropriate input method, and the user experience is improved.

It is understood that the input method calling rule includes a correspondence relationship between the input device type and the input method. The input method calling rules can be stored in the input method application and can also be stored in other areas for the input method application to call.

It is understood that the second interface is a custom interface for passing snoop callback information. The snoop callback information may include an input device type. The related description of the second interface can refer to the following text, and is not explained herein.

With reference to the first aspect, in a possible implementation manner of the first aspect, the invoking a second input method based on the second input event specifically includes: determining the second equipment type based on the second input event through the input management service, and reporting the second equipment type to the input method management service; comparing, by the input management service, the second device type to the second historical device type; the second historical device type is a device type of an input device corresponding to a last input event of the second input event generated by the electronic device; if the second device type is different from the second historical device type or the second historical device type does not exist, sending monitoring callback information to the input method application through the input method management service based on a second interface; the interception callback information comprises the second device type; and the input method application searches the second input method in the input method calling rule according to the second equipment type in the monitoring callback information and calls the second input method.

It is understood that the process of invoking the second input method based on the second input event may refer to the process of invoking the first input method based on the first input event. In the scheme provided by the application, the input management service may determine the device type of the input device based on the input event, compare the current input device type with the historical device type, and determine whether the current input device type needs to be transferred to the input method management service according to the comparison result. For specific description and beneficial effects, reference may be made to the above description, which is not repeated herein.

With reference to the first aspect, in a possible implementation manner of the first aspect, a last input event of the second input events generated by the electronic device is the first input event; the second historical device type is the first device type.

In the solution provided by the present application, the first input event may be a last input event of the second input event. That is, the user switches from the first input device to the second input device when entering an input on the electronic device. As the input device is changed, the type of the input device is changed, and the input method called and displayed by the electronic device is also changed, namely the previous first input method is changed into the second input method. In the process, the user does not need to manually switch the input method, and the user experience is improved.

Illustratively, the first input device is a touchscreen-finger and the second input device is a touchscreen-stylus. The user firstly inputs on a soft keyboard displayed on the electronic equipment through fingers and then switches to a stylus pen for inputting. It is understood that the user can directly input on the screen of the electronic device using the handwriting pen. That is, once the stylus contacts the touch screen of the electronic device, generating a stylus touch event, the electronic device may switch to display the corresponding input method.

With reference to the first aspect, in a possible implementation manner of the first aspect, the first interface and the second interface are user interfaces of a first application; the first application is an application in the electronic equipment; the first operation is used for prompting the first application to acquire a focus.

In the scheme provided by the application, the first interface and the second interface are both user interfaces of the first application. The electronic device may display a third interface before displaying the first interface. It is to be appreciated that the first operation can be an input operation (e.g., clicking on an edit control) for a respective edit control in the third interface. After the electronic equipment receives the first operation and before the first interface is displayed, the first application in the electronic equipment can acquire the focus and inform the input method management service that the focus is acquired and the input method is requested to be bound.

It is understood that an edit control is a control for making input edits. Such as an edit box, etc.

With reference to the first aspect, in a possible implementation manner of the first aspect, the second operation is used to prompt the first application to acquire a focus.

In the solution provided by the present application, the second operation may be an input operation (e.g., clicking on an edit control) for a corresponding edit control included in the other user interface in the first application. After the electronic device receives the second operation and before the second interface is displayed, the first application in the electronic device can acquire the focus and inform the input method management service that the focus is acquired and the input method is requested to be bound. That is, after the first application displays the first interface and before the second application displays the second interface, the focus needs to be obtained again so as to display the input method, thereby realizing the input.

With reference to the first aspect, in a possible implementation manner of the first aspect, the first interface is a user interface of a first application; the second interface is a user interface of a second application; the first application and the second application are applications in the electronic device; the first operation is used for prompting the first application to acquire a focus; the second operation is used for prompting the second application to acquire a focus.

In the scheme provided by the application, the first interface is a user interface of a first application, and the second interface is a user interface of a second application. The user can switch different input devices to input in different applications. In this case, the first operation may be an input operation for an edit control of the corresponding interface of the first application, and the second operation may be an input operation for an edit control of the corresponding interface of the second application.

In a second aspect, the present application provides an input method invocation method. The method can be applied to electronic devices. The method can comprise the following steps: receiving a target operation, and generating a target input event in response to the target operation; determining the type of target equipment based on the target input event through an input management service, and reporting the type of the target equipment to an input method management service; comparing, by the input management service, the target device type to a historical device type; the historical device type is a device type of an input device corresponding to a last input event of the target input event generated by the electronic device; if the type of the target equipment is different from the type of the historical equipment or the type of the historical equipment does not exist, sending monitoring callback information to an input method application in the electronic equipment through the input method management service; the interception callback information comprises the type of the target equipment; searching a target input method in an input method calling rule according to the type of the target equipment in the monitoring callback information through the input method application; the input method calling rule comprises a corresponding relation between a device type corresponding to the input device and the input method; calling the target input method and displaying an input interface; the target input method is displayed on the input interface.

In the scheme provided by the application, the electronic equipment can respond to the target operation of the user, generate the target input event and determine the type of the target equipment according to the target input event. The electronic equipment can search the input method corresponding to the type of the target equipment in the input method calling rule and call the input method. By the method, a user does not need to manually switch to an input method which is more matched with the current input equipment, the use experience of the user is fully considered, and the user experience is improved.

It is understood that the target operation is an input operation with the input device. The target input event is an input event generated for a target operation. The target device type is a device type of the input device.

With reference to the second aspect, in a possible implementation manner of the second aspect, before the generating a target input event in response to the target operation, the method further includes: sending a registration monitoring request to the input method management service through the input method application based on a first interface; the registration monitoring request is used for requesting the input method management service to monitor the input equipment; sending a first message to the input management service through the input method management service; the first message is used to request the input management service to listen to an input device.

With reference to the second aspect, in a possible implementation manner of the second aspect, the determining, by the input management service, the target device type based on the target input event specifically includes: determining, by the input management service, that the target device type is a first device type if the target input event is a first input event; determining, by the input management service, that the target device type is a second device type if the target input event is a second input event; determining, by the input management service, that the target device type is a third device type if the target input event is a third input event.

With reference to the second aspect, in a possible implementation manner of the second aspect, the first input event is a finger touch event, and the first device type is a touchscreen-finger; the second input event is a stylus touch event, and the second device type is a touch screen-stylus; the third input event is a keyboard event and the third device type is a keyboard.

It is understood that the user may make inputs using different input devices and that the input events generated by the electronic device may be different types of input events.

In some embodiments of the present application, the target operation may be a finger touch operation, a stylus touch operation, and a tap keyboard operation. Accordingly, the target input event may be a finger touch event, a stylus touch event, and a keyboard event.

It is understood that the target input event may also be other types of input events. Such as mouse events, keystroke events, and the like.

In a third aspect, the present application provides an electronic device. The electronic equipment comprises a receiving module and a display module. The receiving module is used for receiving a first operation; and the display module is used for responding to the first operation and displaying the first interface. It can be understood that the first operation is an input operation performed by a first input method, and the first interface displays a first input method. The first input method is an input method corresponding to the first input method. And the receiving module is also used for receiving the second operation. And the display module is also used for responding to the second operation and displaying the second interface. It is understood that the second operation is an input operation performed by a second input method, and the second interface displays a second input method. The second input method is an input method corresponding to the second input method. With reference to the third aspect, in a possible implementation manner of the third aspect, the first input manner is a manner of inputting with a first input device; the second input mode is a method for inputting by using the second input device. The first input method is an input method corresponding to the first input mode, and specifically includes: the first input method is an input method corresponding to a first device type, and the first device type is a device type corresponding to the first input device. The second input method is an input method corresponding to the second input mode, and specifically includes: the second input method is an input method corresponding to a second device type, and the second device type is a device type corresponding to the second input device.

With reference to the third aspect, in a possible implementation manner of the third aspect, the electronic device may further include an input method application, an input method management service, and an input management service. Wherein the input method application can be used for sending a registration listening request to the input method management service based on the first interface. The registration monitoring request is used for requesting the input method management service to monitor the input equipment. The input method management service may be operable to send a first message to the input management service. The first message is for requesting the input management service to listen to the input device.

With reference to the third aspect, in a possible implementation manner of the third aspect, the electronic device may further include an input event generation module. The input event generation module is used for responding to a first operation and generating a first input event. The input management service is also used for determining a first equipment type based on the first input event and reporting the first equipment type to the input method management service; the first device type is compared to a first historical device type. The first historical device type is the device type of the input device corresponding to the last input event of the first input event generated by the electronic device. The input method management service is further used for sending the interception callback information to the input method application through the second interface under the condition that the first equipment type is different from the first historical equipment type or the first historical equipment type does not exist. The listening callback information includes a first device type. And the input method application is used for searching the first input method in the input method calling rule according to the first equipment type in the monitoring callback information and calling the first input method. The input method calling rule comprises the corresponding relation between the equipment type corresponding to the input equipment and the input method.

With reference to the third aspect, in a possible implementation manner of the third aspect, the input event generating module is further configured to generate a second input event in response to the second operation. The input management service is also used for determining a second equipment type based on a second input event and reporting the second equipment type to the input method management service; the second device type is compared to a second historical device type. The second historical device type is the device type of the input device corresponding to the last input event of the second input event generated by the electronic device. And the input method management service is also used for sending the interception callback information to the input method application through the second interface under the condition that the second equipment type is different from the second historical equipment type or the second historical equipment type does not exist. The snoop callback information includes the second device type. And the input method application is also used for searching the second input method in the input method calling rule according to the second equipment type in the monitoring callback information and calling the second input method.

With reference to the third aspect, in a possible implementation manner of the third aspect, a last input event of the second input events generated by the electronic device is the first input event; the second historical device type is the first device type.

With reference to the third aspect, in a possible implementation manner of the third aspect, the first interface and the second interface are user interfaces of a first application; the first application is an application in the electronic equipment; the first operation is used for prompting the first application to acquire a focus.

With reference to the third aspect, in a possible implementation manner of the third aspect, the second operation is used to prompt the first application to acquire a focus.

With reference to the third aspect, in a possible implementation manner of the third aspect, the first interface is a user interface of a first application; the second interface is a user interface of a second application; the first application and the second application are applications in the electronic device; the first operation is used for prompting the first application to acquire a focus; the second operation is used for prompting the second application to acquire a focus.

In a fourth aspect, the present application provides an electronic device. The electronic device may include a receiving module, an input event generating module, an input management service, an input method application, and a display module. The receiving module is used for receiving the target operation. And the input event generation module is used for responding to the target operation and generating a target input event. The target operation is an input operation performed with the input device. The input management service is used for determining the type of the target equipment based on the target input event and reporting the type of the target equipment to the input method management service; the target device type is compared to the historical device types. The target device type is a device type of the input device. The historical device type is the device type of the input device corresponding to the last input event of the target input event generated by the electronic device. And the input method management service is used for sending the monitoring callback information to the input method application in the electronic equipment through the input method management service under the condition that the type of the target equipment is different from that of the historical equipment or the historical equipment does not exist. The snoop callback information includes a target device type. And the input method application is used for searching a target input method in the input method calling rule according to the type of the target equipment in the monitoring callback information and calling the target input method. The input method calling rule comprises the corresponding relation between the equipment type corresponding to the input equipment and the input method. And the display module is used for displaying the input interface. The input interface displays a target input method.

With reference to the fourth aspect, in a possible implementation manner of the fourth aspect, the input method application may be further configured to send a registration listening request to the input method management service based on the first interface. The registration monitoring request is used for requesting the input method management service to monitor the input equipment. The input method management service may also be configured to send a first message to the input management service. The first message is for requesting the input management service to listen to the input device.

With reference to the fourth aspect, in a possible implementation manner of the fourth aspect, when the input management service is configured to determine the type of the target device based on the target input event, the input management service is specifically configured to: determining the type of the target equipment as a first equipment type through the input management service under the condition that the target input event is a first input event; determining the type of the target equipment as a second equipment type through the input management service under the condition that the target input event is a second input event; and determining the target device type to be a third device type through the input management service in the case that the target input event is a third input event. The first input event is a finger touch event, and the first device type is a touch screen-finger; the second input event is a stylus touch event, and the second device type is a touch screen-stylus; the third input event is a keyboard event and the third device type is a keyboard.

In a fifth aspect, the present application provides an electronic device. The electronic device may include a display screen, a memory, one or more processors. Wherein the one or more processors are coupled to a memory for storing computer program code comprising computer instructions. The electronic device may receive a first operation. And the display screen is used for responding to the first operation and displaying the first interface and is also used for responding to the second operation and displaying the second interface. The first operation is an input operation performed by a first input mode. The first interface displays a first input method. The first input method is an input method corresponding to the first input method. The second operation is an input operation by a second input method. The second interface displays a second input method. The second input method is an input method corresponding to the second input method. The first input method is different from the second input method.

With reference to the fifth aspect, in a possible implementation manner of the fifth aspect, the first input manner is a manner of inputting with a first input device; the second input mode is a method for inputting by using the second input device. The first input method is an input method corresponding to the first input mode, and specifically includes: the first input method is an input method corresponding to a first device type, and the first device type is a device type corresponding to the first input device. The second input method is an input method corresponding to the second input mode, and specifically includes: the second input method is an input method corresponding to a second device type, and the second device type is a device type corresponding to the second input device.

With reference to the fifth aspect, in a possible implementation manner of the fifth aspect, the processor is configured to send, by an input method application in the electronic device, a registration listening request to an input method management service in the electronic device based on the first interface; the first message is sent by an input method management service to an input management service in the electronic device. The registration monitoring request is used for requesting the input method management service to monitor the input equipment. The first message is for requesting the input management service to listen to the input device.

With reference to the fifth aspect, in a possible implementation manner of the fifth aspect, the processor is further configured to generate a first input event in response to the first operation; a first input method is invoked based on the first input event. The first input event is an input event generated for a first input device. The processor is also used for responding to a second operation and generating a second input event; a second input method is invoked based on the second input event. The second input event is an input event generated for a second input device.

With reference to the fifth aspect, in a possible implementation manner of the fifth aspect, the processor, when configured to invoke the first input method based on the first input event, is specifically configured to: determining a first equipment type based on a first input event through an input management service, and reporting the first equipment type to an input method management service; comparing, by the input management service, the first device type to a first historical device type; if the first equipment type is different from the first historical equipment type or the first historical equipment type does not exist, sending monitoring callback information to the input method application through the input method management service based on the second interface; and searching the first input method in the input method calling rule according to the first equipment type in the monitoring callback information through the input method application, and calling the first input method. The first historical device type is the device type of the input device corresponding to the last input event of the first input event generated by the electronic device. The listening callback information includes a first device type. The input method calling rule comprises the corresponding relation between the equipment type corresponding to the input equipment and the input method.

With reference to the fifth aspect, in a possible implementation manner of the fifth aspect, the processor, when configured to invoke the second input method based on the second input event, is specifically configured to: determining a second equipment type based on a second input event through the input management service, and reporting the second equipment type to the input method management service; comparing the second device type with a second historical device type by the input management service; if the second equipment type is different from the second historical equipment type or the second historical equipment type does not exist, sending monitoring callback information to the input method application through the input method management service based on the second interface; and searching the second input method in the input method calling rule according to the second equipment type in the monitoring callback information by the input method application, and calling the second input method. The second historical device type is the device type of the input device corresponding to the last input event of the second input event generated by the electronic device. The listening callback information includes a second device type.

With reference to the fifth aspect, in a possible implementation manner of the fifth aspect, a last input event of the second input events generated by the electronic device is the first input event. The second historical device type is the first device type.

With reference to the fifth aspect, in a possible implementation manner of the fifth aspect, the first interface and the second interface are user interfaces of the first application. The first application is an application in an electronic device. The first operation is to prompt the first application to acquire focus.

With reference to the fifth aspect, in a possible implementation manner of the fifth aspect, the second operation is used to prompt the first application to acquire a focus.

With reference to the fifth aspect, in a possible implementation manner of the fifth aspect, the first interface is a user interface of the first application. The second interface is a user interface of a second application. The first application and the second application are applications in an electronic device. The first operation is to prompt the first application to acquire focus. The second operation is to prompt the second application to obtain focus.

In a sixth aspect, the present application provides an electronic device. The electronic device may include a display screen, a memory, one or more processors. Wherein the one or more processors are coupled to a memory for storing computer program code comprising computer instructions. The electronic device may receive a target operation. A processor operable, in response to a target operation, to generate a target input event; determining the type of target equipment based on the target input event through the input management service, and reporting the type of the target equipment to the input method management service; comparing the target device type with the historical device type through the input management service; if the type of the target equipment is different from that of the historical equipment or the historical equipment does not exist, sending monitoring callback information to input method application in the electronic equipment through the input method management service; searching a target input method in the input method calling rule according to the type of the target equipment in the monitoring callback information by using the input method application; calling a target input method and displaying an input interface; the input interface displays a target input method. Wherein the target operation is an input operation with an input device. The target device type is a device type of the input device. The historical device type is the device type of the input device corresponding to the last input event of the target input event generated by the electronic device. The snoop callback information includes a target device type. The input method calling rule comprises the corresponding relation between the equipment type corresponding to the input equipment and the input method.

With reference to the sixth aspect, in a possible implementation manner of the sixth aspect, the processor is further configured to send, by an input method application in the electronic device, a registration listening request to an input method management service in the electronic device based on the first interface; the first message is sent by an input method management service to an input management service in the electronic device. The registration monitoring request is used for requesting the input method management service to monitor the input equipment. The first message is for requesting the input management service to listen to the input device.

With reference to the sixth aspect, in a possible implementation manner of the sixth aspect, the processor, when configured to determine the type of the target device based on the target input event, is specifically configured to: determining the type of the target equipment as a first equipment type through the input management service under the condition that the target input event is a first input event; determining the type of the target equipment as a second equipment type through the input management service under the condition that the target input event is a second input event; and determining the target device type to be the third device type through the input management service in the case that the target input event is the third input event. The first input event is a finger touch event, and the first device type is a touch screen-finger; the second input event is a stylus touch event, and the second device type is a touch screen-stylus; the third input event is a keyboard event and the third device type is a keyboard.

In a seventh aspect, the present application provides a computer storage medium, which includes instructions that, when executed on an electronic device, cause the electronic device to perform any one of the possible implementations of the first aspect.

In an eighth aspect, the present application provides a computer storage medium including instructions that, when executed on an electronic device, cause the electronic device to perform any one of the possible implementations of the second aspect.

In a ninth aspect, an embodiment of the present application provides a chip applied to an electronic device, where the chip includes one or more processors, and the processor is configured to invoke computer instructions to cause the electronic device to execute any one of the possible implementation manners of the first aspect.

In a tenth aspect, an embodiment of the present application provides a chip applied to an electronic device, where the chip includes one or more processors, and the processor is configured to invoke computer instructions to cause the electronic device to execute any one of the possible implementation manners of the second aspect.

In an eleventh aspect, embodiments of the present application provide a computer program product including instructions, which, when run on a device, cause the electronic device to perform any one of the possible implementations of the first aspect.

In a twelfth aspect, embodiments of the present application provide a computer program product including instructions, which, when run on a device, cause the electronic device to perform any one of the possible implementations of the second aspect.

It can be understood that beneficial effects of the input method invoking method provided by the second aspect may refer to beneficial effects of any one of possible implementation manners of the first aspect, and are not described herein again. In addition, the electronic device provided by the third and fifth aspects, the computer storage medium provided by the seventh aspect, the chip provided by the ninth aspect, and the computer program product provided by the eleventh aspect are all configured to execute any one of the possible implementations of the first aspect. The electronic device provided by the fourth aspect and the sixth aspect, the computer storage medium provided by the eighth aspect, the chip provided by the tenth aspect, and the computer program product provided by the twelfth aspect are all configured to execute any one of the possible implementations of the second aspect. Therefore, the beneficial effects that can be achieved by the method can refer to the beneficial effects of any one of the possible implementation manners of the first aspect, and are not described herein again.

Drawings

Fig. 1 is a schematic diagram of an input method invocation scenario provided in an embodiment of the present application;

FIGS. 2A-2K are schematic diagrams of a set of user interfaces provided by embodiments of the present application;

fig. 3 is a schematic hardware structure diagram of an electronic device 100 according to an embodiment of the present disclosure;

fig. 4 is a schematic diagram of a software structure of an electronic device 100 according to an embodiment of the present disclosure;

fig. 5 is a schematic diagram of a process of invoking an input method according to an embodiment of the present application;

fig. 6 is a flowchart of an input method invocation method provided in the embodiment of the present application;

fig. 7 is a flowchart of another input method invoking method according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. In the description of the embodiments herein, "/" means "or" unless otherwise specified, for example, a/B may mean a or B; "and/or" in the text is only an association relationship describing an associated object, and means that three relationships may exist, for example, a and/or B may mean: three cases of a alone, a and B both, and B alone exist, and in addition, "a plurality" means two or more than two in the description of the embodiments of the present application.

It should be understood that the terms "first," "second," and the like in the description and claims of this application and in the drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.

Reference in the specification to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the specification. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.

When people work and entertain by using terminal equipment such as a mobile phone, a tablet personal computer and the like, input is often required through an input method. For example, a user may enter text by invoking an input method while chatting with friends or colleagues using social software in a cell phone. As another example, a user may search by entering text in a search box of a search engine.

The input mode of the user is various. For example, the user may directly touch the screen of the terminal device with a finger to realize input, or may realize input through some input devices. It is understood that if the user takes different input modes, the input modes may be different. That is, the specific input method suitable for different input modes may be different. For example, the finger touch input may be applied to a keyboard input mode, i.e., a full-spelling input method, a wubi input method, and the like, which require an input method using a keyboard, and the stylus input may be applied to a handwriting input mode, i.e., a handwriting input method. However, whatever input mode the user takes, the default input mode is displayed first on the input interface. It is understood that the default input mode mentioned herein may include a default input method set by the user and an input method used when the user makes an input last time. If the input mode needs to be switched because the input mode changes, the user generally needs to manually switch, which may affect the user experience.

It is understood that the invoked input method referred to in this application refers to a specific input method. Such as handwriting input methods, full-spelling input methods, stroke input methods, etc.

First, a brief description is given to an input method calling scenario provided in an embodiment of the present application with reference to fig. 1.

Referring to fig. 1, fig. 1 is a schematic diagram of an input method calling scenario provided in an embodiment of the present application. As shown in fig. 1, a user may enter input in electronic device 100 in a variety of input manners. The multiple input modes may include, but are not limited to, a finger touch input mode and an input mode using other external input devices for input. It is understood that the external input device referred to herein refers to an input device independent of the electronic device 100.

It can be understood that the finger touch input manner mentioned in the present application is specifically that the user realizes the input by contacting the finger with the touch screen of the electronic device 100. Similar to the finger touch input manner, the user may also perform input by contacting the touch screen of the electronic device 100 with other human skin.

It is understood that the input device is an external device that exists independently of the electronic device 100. Input devices may include, but are not limited to, a keyboard, stylus, mouse, and the like.

Specifically, in a case where the user performs an input in the electronic device 100 in a finger touch input manner, a finger touch operation acting on an input area of the electronic device 100 may trigger a finger touch event. The electronic device 100 may determine an input method to be taken when inputting in the input area after receiving the finger touch event. In the case where a user makes an input in the electronic apparatus 100 using an input device, a user operation acting on an input area on the input area of the electronic apparatus 100 may trigger an input event. The electronic device 100 may determine the input event type and the corresponding input device type after receiving the input event, and determine an input method to be taken when inputting in the input area based on the input event type and the input device type.

For example, a user may contact a stylus with a touch screen of the electronic device 100, and a stylus touch operation applied to an input area of the electronic device 100 may trigger a stylus touch event. The electronic device 100 may determine that the handwriting input method is adopted when inputting in the input area after receiving the handwriting pen touch event.

It should be noted that before the input device is used for inputting, a communication connection may be established between the input device and the electronic device 100. It is understood that the communication connection mode between the input device and the electronic device 100 may include a wired communication mode and a wireless communication mode. The wireless communication mode may include a communication mode such as bluetooth.

Some input scenarios provided by the embodiments of the present application are specifically described below.

It is understood that the terms "interface" and "user interface" in the description and claims and drawings of the present application are media interfaces for interaction and information exchange between an application or operating system and a user that enable the conversion of the internal form of information to a form acceptable to the user. A commonly used presentation form of the user interface is a Graphical User Interface (GUI), which refers to a user interface related to computer operations and displayed in a graphical manner. It may be an interface element such as an icon, a window, a control, etc. displayed in the display screen of the electronic device, where the control may include a visual interface element such as an icon, a button, a menu, a tab, a text box, a dialog box, a status bar, a navigation bar, a Widget, etc.

1. Entering input interface (fig. 2A)

Referring to fig. 2A, fig. 2A is a schematic view of a user interface according to an embodiment of the present disclosure.

As shown in FIG. 2A, the user interface 210 displays a page on which application icons are placed. The page may include a plurality of application icons (e.g., a weather application icon, a calendar application icon, an email application icon, a settings application icon 211, an application store application icon, a notes application icon, an album application icon, a recorder application icon, etc.). And page indicators can be displayed below the application icons to indicate the position relationship between the currently displayed page and other pages. Below the page indicator are a plurality of tray icons (e.g., a dial application icon, an information application icon, a browser application icon 212, a camera application icon). The browser application icon 212 is an icon of a browser application. Browsers are application programs used to retrieve, present, and deliver Web information resources. It is understood that the tray icon remains displayed as the page switches.

It is understood that the representations and names of the above application icons are only examples and should not be construed as limiting the present application. In addition, other content may also be displayed on the user interface 210, which is not limited in this application.

Electronic device 100 may detect a user operation acting on browser application icon 212, in response to which electronic device 100 may display user interface 220 (shown in fig. 2B and 2C). The user interface 220 is a browser home interface. The interface is also a browser search interface. That is, the user may input in a corresponding area of the interface to perform the search, and thus, the user interface 220 may also be understood as an input interface. The user interface 220 may include an edit box 221. Edit box 221 may be used for input to search through a browser.

It is understood that the user operation may include, but is not limited to, a touch operation, a key operation, a gesture operation, a voice operation, and the like, which is not limited in this application.

2. Calling and switching input method (fig. 2B-2H)

As shown in FIG. 2B, the user may click on an edit box 221 included in the user interface 220. Accordingly, the electronic device 100 may detect a finger touch operation applied to the edit box 221, thereby generating a finger touch event. It is appreciated that finger touch events may be collected by an input subsystem in a kernel layer of the electronic device 100 and communicated to the device node. Further, the input reader can read the finger touch event and then report the finger touch event to the input management service by the input dispatcher. The input management service may pass the finger touch event to a window management service that coordinates the input management service to assign the finger touch event to a browser application. This means that the browser application acquires focus. Colloquially, the browser application may learn that the area that the user needs to enter is the edit box 221, and determine that the edit box 221 is the location where the current cursor is activated. In this case, the browser application may notify the input method management service itself to get focus and request binding of the input method. And the input method management service informs the input method application of calling the input method and displays the called input method on an interface of the browser application acquisition focus.

On the other hand, after receiving the finger touch event reported by the input distributor, the input management service may determine that the input device is a touch screen according to the finger touch event, and may also determine that the trigger mode of the user is finger touch. The input management service may send the input device type corresponding to the finger touch event to the input method management service. The input method management service then sends the input device type to the input method application. The input method application can determine the input method to be called as a pinyin input method (soft keyboard) according to the type of the input device.

It should be noted that the browser application may determine that the interface in the application program for obtaining the focus is the user interface 220. After the browser application requests the input method management service to bind the input method, the input method may also be displayed by the input method management service request.

It is understood that the input method application may request registration of the listening input device with the input method management service. The request by the input method application to register with the input method management service may occur before or after the user clicks on the edit box 221 included in the user interface 220.

According to the above process, there are: in response to a finger touch operation by the user on the edit box 221, the electronic device 100 may display the user interface 230 illustrated in fig. 2C. The user interface 230 includes an edit box 231 and an input area 232. A cursor is displayed in edit box 231, as compared to edit box 221 included in user interface 220, indicating that the browser application has acquired focus. The input area 232 displays a pinyin full-key soft keyboard for user input.

As shown in fig. 2D, the user may click on an edit box 221 included in the user interface 220 with a stylus. Accordingly, the electronic device 100 may detect a stylus touch operation applied to the edit box 221, thereby generating a stylus touch event. The process of transferring stylus touch events may refer to the process of transferring finger touch events described above. What is different from the transmission process of the finger touch event is that after the input management service receives the stylus touch event reported by the input distributor, the input management service can determine that the input device is a touch screen according to the stylus touch event and can also determine that the trigger mode of the user is stylus touch. The input management service may send the input device type corresponding to the stylus touch event to the input method management service. The input method management service then sends the input device type to the input method application. The input method application can determine that the input method to be called is a handwriting input method according to the type of the input device.

It is appreciated that in response to a stylus touch operation acting on edit box 221, electronic device 100 may display user interface 240 shown in FIG. 2E. The user interface 240 includes an edit box 241 and an input area 242. A cursor is displayed in the edit box 241, compared to the edit box 221 included in the user interface 220, which indicates that the browser application has acquired focus. The input area 242 displays a handwriting area for the user to input.

It should be noted that, after the browser application acquires the focus, the input device for the user to input may be changed.

In some embodiments of the present application, where electronic device 100 displays user interface 230 shown in FIG. 2C, the user may tap on the keyboard (e.g., tap the "shift" key on the keyboard, etc.) to trigger a keyboard event. The keyboard event may be transferred by referring to the finger touch event and the stylus touch event as described above. Different from the two transfer processes, after receiving the keyboard event reported by the input distributor, the input management service may determine that the input device is a keyboard according to the keyboard event. The input management service may send the input device type corresponding to the keyboard event to the input method management service. The input method management service then sends the input device type to the input method application. The input method application may determine that the input method to be invoked is a pinyin input method (hover mode) according to the type of the input device.

It is appreciated that in response to user operations acting on the keyboard, the electronic device 100 may display the user interface 250 shown in FIG. 2F. The user interface 250 may include an edit box 231 and an input method hover toolbar 251. When the user inputs an input through the keyboard, the edit box 231 may display the input content of the user.

It can be appreciated that the keyboard struck by the user has established a communication connection (e.g., a bluetooth connection, etc.) with the electronic device 100.

In addition, when the input device for the user to input is changed, the electronic apparatus 100 may switch the input method according to the type of the input device.

In some embodiments of the present application, as shown in fig. 2G, the user firstly performs the finger touch operation for inputting, and then performs the input through the stylus pen. Accordingly, the electronic device 100 may detect a stylus touch operation applied to the edit box 221, thereby generating a stylus touch event. The process of transferring stylus touch events may refer to the process of transferring finger touch events described above. What is different from the transmission process of the finger touch event is that after the input management service receives the stylus touch event reported by the input distributor, the input management service can determine that the input device is a touch screen according to the stylus touch event and can also determine that the trigger mode of the user is stylus touch. The input management service may send the input device type corresponding to the stylus touch event to the input method management service. The input method management service then sends the input device type to the input method application. The input method application can determine that the input method to be called is a handwriting input method according to the type of the input equipment, and the originally called pinyin input method is switched into the handwriting input method.

It is understood that in a case where the browser application has acquired focus, an input operation by the user through the stylus pen may act on an arbitrary position on the touch screen of the electronic apparatus 100 (not necessarily act on the edit box 231).

It is appreciated that in response to a stylus touch operation acting on the touch screen of the electronic device 100, the electronic device 100 may display the user interface 260 shown in FIG. 2H. The user interface 260 may include an edit box 231, a handwriting input area 261, and an input tool area 262. The user may input on the handwriting input area 261 through a stylus pen, and accordingly, the edit box 231 may display the input content of the user. In addition, the user can also determine input contents, search contents, the size of the input area through the input tool area 262, and manually switch the input method.

It should be noted that the input method calling method may also be implemented for other applications including editing controls (e.g., an edit box). In addition, the above input method invoking and switching processes are only an overview and are not described, and the following may be referred to for specific description.

3. Setting the corresponding relationship between the input method and the input device (FIGS. 2I-2K)

The electronic apparatus 100 may detect a user operation acting on the setting application icon 211, and in response to the user operation, the electronic apparatus 100 may display the user interface 270 illustrated in fig. 2I. User interface 270 may include controls 271. The control 271 is used for opening an input method setting interface.

Electronic device 100 may detect a user operation acting on control 271, in response to which electronic device 100 may display user interface 280 shown in fig. 2J. The user interface 280 interfaces for input methods. The user interface 280 may include several input method settings. As shown in fig. 2J, user interface 280 can include

controls

281, 282, and 283. Among other things, control 281 is used to set a default input method application. If there are multiple input method applications in the electronic device 100, the user can set the default input method application for input through the control 281. Control 282 is used to set the secure input mode. In the secure input mode, when the user inputs a password, the secure input keyboard needs to be started. Control 283 is used to open a smart call input method interface. It is understood that intelligently invoking an input method refers to invoking a particular input method based on the type of input device.

Electronic device 100 may detect a user operation acting on control 283, in response to which electronic device 100 may display user interface 290 as shown in fig. 2K. User interface 290 is an intelligent invocation input method interface. The intelligent call input method interface may include a number of intelligent call input method settings. As shown in fig. 2K, user interface 290 may include a control 291 and a display area 292. The control 291 is used to open the intelligent call input method. The display area 292 is a setting area of the correspondence relationship between the input device type and the input method. The display area 292 may include controls 2921 and a personalization setting area 2922. The control 2921 is used for setting the corresponding relationship between the input device type and the input method as a default corresponding relationship. It is understood that the default correspondence is a correspondence preset by a technician. The personalized setting area 2922 is used for personalized setting of the corresponding relationship between the type of input device and the input method according to the user's needs. The personalization settings area 2922 may include a display area 29221 and a control 29222. The display area 29221 may include several controls. The controls can be used for managing the corresponding relation between the input device type set by the user and the input method. As shown in fig. 2K, the display area 29221 may include controls for managing input methods corresponding to three input devices, namely, a touch screen-finger, a touch screen-stylus, and a keyboard. According to the display area 29221 shown in fig. 2K, the input method corresponding to the touch screen and the finger is a pinyin input method (full-pinyin soft keyboard), the input method corresponding to the touch screen and the stylus pen is a handwriting input method, and the input method corresponding to the keyboard is a pinyin input method (floating mode). Control 29222 is used to add a new input device type to input method correspondence.

It should be noted that the user interfaces described in the above embodiments are only examples provided by the present application, and the user interfaces may also be represented in other forms, and the present application does not limit the specific forms of the user interfaces and other contents included in the user interfaces.

The following describes an apparatus according to an embodiment of the present application.

Fig. 3 is a schematic diagram of a hardware structure of an electronic device 100 according to an embodiment of the present disclosure.

The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a Universal Serial Bus (USB) interface 130, a charging management Module 140, a power management Module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication Module 150, a wireless communication Module 160, an audio Module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor Module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, a Subscriber Identity Module (SIM) card interface 195, and the like. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

It is to be understood that the illustrated structure of the embodiment of the present invention does not specifically limit the electronic device 100. In other embodiments of the present application, electronic device 100 may include more or fewer components than shown, or some components may be combined, some components may be split, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 110 may include one or more processing units. The different processing units may be separate devices or may be integrated into one or more processors.

A memory may also be provided in processor 110 for storing instructions and data.

In some embodiments, processor 110 may include one or more interfaces.

In some embodiments of the present application, the processor 110 may execute the input method invocation methods mentioned in the present solution.

The charging management module 140 is configured to receive charging input from a charger.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110.

The wireless communication function of the electronic device 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 may be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas.

The mobile communication module 150 may provide a solution including 2G/3G/4G/5G wireless communication applied to the electronic device 100. The modem processor may include a modulator and a demodulator.

The Wireless Communication module 160 may provide solutions for Wireless Communication applied to the electronic device 100, including Wireless Local Area Networks (WLANs) (e.g., Wireless Fidelity (Wi-Fi) network), Bluetooth (BT), Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), and the like. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves via the antenna 2 to radiate the electromagnetic waves.

In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150 and antenna 2 is coupled to wireless communication module 160 so that electronic device 100 can communicate with networks and other devices through wireless communication techniques.

The electronic device 100 implements display functions via the GPU, the display screen 194, and the application processor. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and an application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 194 is used to display images, video, and the like. In some embodiments, the electronic device 100 may include 1 or N display screens 194, with N being a positive integer greater than 1.

The electronic device 100 may implement the acquisition function via the ISP, camera 193, video codec, GPU, display screen 194, application processor, and the like.

The ISP is used to process the data fed back by the camera 193. For example, when a photo is taken, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing and converting into an image or video visible to the naked eye. The ISP can also carry out algorithm optimization on the noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in camera 193.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image to the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a Complementary Metal-Oxide-Semiconductor (CMOS) phototransistor. The light sensing element converts the optical signal into an electrical signal, which is then passed to the ISP where it is converted into a digital image or video signal. And the ISP outputs the digital image or video signal to the DSP for processing. The DSP converts the digital image or video signal into image or video signal in standard RGB, YUV and other formats.

The digital signal processor is used for processing digital signals, and can process digital images or video signals and other digital signals.

Video codecs are used to compress or decompress digital video.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to extend the memory capability of the electronic device 100.

The internal memory 121 may be used to store computer-executable program code, which includes instructions. The processor 110 executes various functional applications of the electronic device 100 and data processing by executing instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area.

The electronic device 100 may implement audio functions via the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone interface 170D, and the application processor. Such as music playing, recording, etc.

The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal.

The speaker 170A, also called a "horn", is used to convert the audio electrical signal into an acoustic signal.

The receiver 170B, also called "earpiece", is used to convert the electrical audio signal into an acoustic signal.

The microphone 170C, also referred to as a "microphone," is used to convert sound signals into electrical signals. The electronic device 100 may be provided with at least one microphone 170C.

The headphone interface 170D is used to connect a wired headphone.

The sensor module 180 may include 1 or more sensors, which may be of the same type or different types. It is understood that the sensor module 180 shown in fig. 1 is only an exemplary division, and other division is possible, which is not limited in this application.

The pressure sensor 180A is used for sensing a pressure signal, and converting the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be disposed on the display screen 194. When a touch operation is applied to the display screen 194, the electronic apparatus 100 detects the intensity of the touch operation according to the pressure sensor 180A. The electronic apparatus 100 may also calculate the touched position from the detection signal of the pressure sensor 180A. In some embodiments, the touch operations that are applied to the same touch position but different touch operation intensities may correspond to different operation instructions.

The gyro sensor 180B may be used to determine the motion attitude of the electronic device 100.

The air pressure sensor 180C is used to measure air pressure.

The magnetic sensor 180D includes a hall sensor. The electronic device 100 may detect the opening and closing of the flip holster using the magnetic sensor 180D.

The acceleration sensor 180E may detect the magnitude of acceleration of the electronic device 100 in various directions (typically three axes). The magnitude and direction of gravity can be detected when the electronic device 100 is stationary. The method can also be used for identifying the posture of the electronic equipment 100, and is applied to horizontal and vertical screen switching, pedometers and other applications.

A distance sensor 180F for measuring a distance. The electronic device 100 may measure the distance by infrared or laser. In some embodiments, taking a picture of a scene, electronic device 100 may utilize range sensor 180F to range for fast focus.

The proximity light sensor 180G may include, for example, a Light Emitting Diode (LED) and a light detector, such as a photodiode.

The ambient light sensor 180L is used to sense ambient light brightness.

The fingerprint sensor 180H is used to acquire a fingerprint.

The temperature sensor 180J is used to detect temperature.

The touch sensor 180K is also referred to as a "touch panel". The touch sensor 180K is used to detect a touch operation acting thereon or nearby. The touch sensor 180K may pass the detected touch operation to the application processor to determine the touch event type. The touch sensor 180K may also provide visual output related to touch operations through the display screen 194. In other embodiments, the touch sensor 180K may be disposed on a surface of the electronic device 100, different from the position of the display screen 194.

It is understood that the touch sensor 180K may be a touch screen. In some embodiments of the present application, the touch sensor 180K may be disposed on the display screen 194.

In some embodiments of the present application, the touch sensor 180K may be a projected capacitive touch screen.

Note that the touch screen of the electronic device 100 referred to in this application is the touch sensor 180K.

The bone conduction sensor 180M can acquire a vibration signal.

The keys 190 include a power-on key, a volume key, and the like. The keys 190 may be mechanical keys. Or may be touch keys. The electronic apparatus 100 may receive a key input, and generate a key signal input related to user setting and function control of the electronic apparatus 100.

The motor 191 may generate a vibration cue. The motor 191 may be used for incoming call vibration cues, as well as for touch vibration feedback.

Indicator 192 may be an indicator light that may be used to indicate a state of charge, a change in charge, or a message, missed call, notification, etc.

The SIM card interface 195 is used to connect a SIM card.

Fig. 4 is a schematic diagram of a software structure of an electronic device 100 according to an embodiment of the present disclosure.

As shown in FIG. 4, the software framework of the electronic device 100 may include an application layer, an application framework layer, a system library, an android runtime, a hardware abstraction layer, and a kernel layer.

The application layer may include a range of system applications and third party applications. It is understood that the system applications referred to herein refer to applications that are accompanying the android platform, while the third party refers to applications that the user chooses to install. The electronic device 100 may include an input method application and a first application. The input method application is an application providing an input method service. The first application is an application for acquiring focus when the user inputs.

It is understood that focus refers to the area of interest of the electronic device 100, which may be understood as the location where the current cursor is activated. Generally, whether certain areas on the interface displayed by the electronic device 100 are active and responsive depends on whether focus is obtained. For example, the electronic device 100 may display an interface that includes a text box into which characters typed by the user on the keyboard may be entered once the text box has gained focus.

It is understood that the first application may include an edit control. The edit control can provide a user with edit input functionality and can also display input content to the user. Editing controls may include, but are not limited to, text entry areas (such as the text boxes mentioned above), handwriting areas, and the like.

The input method application and the first application may be system applications or third-party applications. That is to say, the input method application in the application can be an input method application provided by an android platform, and can also be an application obtained by subsequent downloading and installation for a user.

The application framework layer provides an application programming interface and a programming framework for the application programs of the application layer. The application framework layer includes some predefined functions.

As shown in fig. 4, the application framework layer may include, but is not limited to, an input management service, an input method management service, a window management service, a bluetooth service, and the like.

The input management service mainly monitors the input device, timely transmits input events (such as screen clicking, key pressing, sliding and the like) generated by the input device to an operating system or an application program, and then the operating system or the application program performs corresponding processing. For example, a user touches a control of an activity in an application. The input management service may convert the user's touch into a touch event and transmit it to the application, which then performs corresponding processing.

It should be noted that, in practice, the input management service relates not only to the application framework layer but also to the Native layer. The Native layer is at a lower layer relative to the application framework layer. The application framework layer generally comprises some system services, and the Native layer generally comprises some local services and some link libraries, etc. For example, if complex operations need to be performed, the efficiency may be low if the operations are implemented by the application framework layer, but if the operations are implemented by the Native layer and then communicate with the application framework layer (i.e., the JNI mechanism in android), the efficiency is greatly improved. As another example, the electronic device 100 may need to interact with the underlying hardware drivers during operation, which may also pass through the Native layer.

It can be appreciated that the input management service involves an application framework layer, a JNI layer, and a Native layer. The main job of the input management service at the application framework layer is to provide implementation for read Policy (readersolicy) and dispatch Policy (Dispatcher Policy), and to cooperate with other system services (e.g., window management services, etc.). The Native input manager (Native input manager) is located in the JNI layer and is responsible for the intercommunication of the components of the Native layer and the input management services of the application framework layer, while it provides an interface for policy requests for the input reader (InputReader) and the input dispatcher (InputDispatcher), which are forwarded by it to the input management services of the application framework layer for subsequent processing by the input management services. An Input Manager (Input Manager) is a runtime container of Input Reader and Input Dispatcher, which creates two threads to carry the runtime of Input Reader and Input Dispatcher, respectively. The Input manager may include Input Reader, Input Dispatcher, and eventhb. The main role of Input Reader is to read events. The primary role of the Input Dispatcher is to distribute events. The EventHub mainly has the function of monitoring device events by using the inotify and epoll mechanisms of Linux. Device events as referred to herein include device plugging and unplugging as well as various touch, button events, and the like. EventHub is mainly oriented to device nodes under the/dev/input directory. For incoming events on the device node, listening and fetching may be performed by getEvents of EventHub.

The input method management service runs in a system process and is a system-level service. The main roles of the input method management service are to manage input methods, bind input methods, manage clients, and interact with other system-level services.

The bluetooth service is used to provide wireless communication functions between the electronic device 100 and associated peripherals. The related peripheral devices mentioned herein may include wireless headsets, tablet computers, notebook computers, etc. In some embodiments of the present application, a bluetooth service may be used to establish a bluetooth connection between the electronic device 100 and the input device.

The window management service is used to manage windows in the operating system. The window management service can work together with the corresponding client to realize the functions of creating, destroying, drawing, laying out and the like of the window. The client is responsible for interacting with the window management service and providing a window management interface for the application and other services, including providing interface functions such as adding, removing and updating window views.

The system library and the Android run contain function functions required to be called by the FWK, a core library of the Android and an Android virtual machine. The system library may include a plurality of functional modules. For example: browser kernel, three-dimensional (3D) graphics, font library, etc.

The hardware abstraction layer is a device kernel driven abstraction interface for implementing an application programming interface that provides a higher level Java API framework with access to the underlying device. The HAL contains a number of library modules such as audio, bluetooth, cameras, sensors etc. Wherein each library module implements an interface for a specific type of hardware component. When the system framework layer API requires access to the hardware of the portable device, the Android operating system loads the library module for the hardware component.

The kernel layer is the basis of the Android operating system, and the final functions of the Android operating system are completed through the kernel layer. The kernel layer can comprise a camera driver, an audio driver, a Bluetooth driver, a sensor driver, a display driver, a touch screen driver, a key driver and the like. For example, the interface language between the kernel layer and the hardware abstraction layer is a hardware abstraction layer interface description language (HIDL).

It should be noted that the software framework diagram of the electronic device 100 shown in fig. 4 provided in the embodiment of the present application is only an example, and specific module division in different hierarchies of an android operating system is not limited, and reference may be specifically made to an introduction of a software structure of the android operating system in the conventional technology. In addition, the electronic device 100 provided in the embodiment of the present application may also adopt other operating systems. It can be understood that the input method calling method provided in the embodiment of the present application can also be implemented based on other operating systems, which is not illustrated in this application.

The following describes an input method calling method provided in the embodiment of the present application.

Referring to fig. 5, fig. 5 is a schematic process diagram of invoking and switching an input method according to an embodiment of the present application.

As shown in fig. 5, a user may input with an input device to generate an input event, and original information related to the input event may be collected by the kernel layer and transmitted to a device node in the kernel layer. Additionally, the core layer may include device drivers. It is understood that the device node corresponds to an input device. The device driver also corresponds to the input device.

Next, the input event may be passed through the kernel layer to an input management service in the application framework layer. In this process, the input event can be read by the input reader, reported to the input management service through the input distributor, and then transmitted to the window management service. The window management service is used as a manager of the window, and can be matched with the input management service to distribute the input event to the window comprising the editing control in the first application for processing. According to the above, the first application is an application that acquires focus. That is, the user's input operation is directed to an edit control in the first application. It is appreciated that the first application may request a call to an input method from an input method management service. The input method management service then notifies the input method application to invoke the input method in accordance with the request for the first application to invoke the input method.

On the other hand, the input method application may request registration of the listening input device with the input method management service. The input method management service may send the registration snoop request to the input management service. After the input management service receives the registration snoop request, an input device type may be determined based on the type of input event received.

In some embodiments of the present application, the input event received by the input management service is the first input event after receiving the registration snoop request. In this case, the input management service may send the input device type to the input method management service. And the input method management service sends the monitoring receipt information to the input method application. It is understood that the listening receipt information may include the input device type. After receiving the listening response piece information, the input method application can determine the input method to be called according to the type of the input device included in the information and call the input method. Accordingly, the first application may display an interface including an input area. It is understood that the input area may be displayed with the input method invoked.

In some embodiments of the present application, the input management service determines that the input device type is different from the historical input device type. In this case, the input management service may send the input device type to the input method management service. And the input method management service sends the monitoring receipt information to the input method application. After receiving the listening receipt information, the input method application can determine the input method to be called according to the type of the input device included in the information, and switch the input method called before to the input method. Accordingly, the first application may display an interface including an input area. It is understood that the input area may be displayed with the input method switched.

It can be understood that the historical input device type is the type of input device corresponding to the input event that was last generated by the electronic device 100. It should be noted that there is a corresponding relationship between the input device type and the input method, which will be described in detail later and will not be described herein.

In some embodiments of the present application, the input management service determines that the input device type is the same as the historical input device type. In this case, the first application invokes the input method that was used the last time the user triggered the input event.

Referring to fig. 6, fig. 6 is a flowchart of an input method invoking method according to an embodiment of the present application, where the input method invoking method may be applied to an electronic device 100 including an input method application, an input method management service, an input distributor, and an input management service. Such as the electronic device 100 shown in fig. 3 and 4. The input method calling method may include, but is not limited to, the following steps:

s601: the input method application sends a registration listening request to an input method management service. The registration listening request is used for listening to the input device (the registration listening request is a request for listening to the input device).

It is understood that an input method application in the electronic device 100 may send a registration listening request to the input method management service. The registration snoop request is for snooping the input device. That is, the electronic device 100 may determine the input device type through the registration listening request.

In some embodiments of the present application, the input method application may send a registration listening request to the input method management service through the custom interface. It is understood that the custom interface is an interface that implements a listening input device. Illustratively, the custom interface may be: InputMethodManager # regiosterInputDeviceChange.

Note that before executing step S601, the electronic apparatus 100 may perform initialization processing on the input method application.

In some embodiments of the present application, in response to a user operation, the electronic apparatus 100 initially requests to invoke an input method, in which case the electronic apparatus 100 may perform an initialization process on an input method application. It is understood that the user operation mentioned here is an operation performed with respect to an input area in the electronic apparatus 100. For example, click on the edit box. In addition, the first request of the electronic device 100 to call the input method refers to the first request of binding the input method after the electronic device 100 is turned on.

In some embodiments of the present application, when the input method application in the electronic device 100 is initially started, the electronic device 100 may perform initialization processing on the input method application. It is understood that the initial start of the input method application refers to the first start of the input method application after the electronic device 100 is turned on. Notably, the input method application can be launched in the background, in which case the corresponding page is not displayed on the electronic device 100. For example, after the electronic device 100 is successfully powered on, the input method application may be started in the background, and the electronic device 100 may perform an initialization process on the input method application.

It is understood that after the input method application sends the registration interception request to the input method management service, the input method management service may receive the registration interception request accordingly.

In some embodiments of the present application, electronic device 100 may include multiple input method applications. If the user manually switches the default input method application, the switched input method application needs to send a registration monitoring request to the input method management service. That is, the registration listening request sent by the input method application before switching is not applicable to the input method application after switching.

S602: the input method management service sends a first message to the input management service. The first message is used for prompting the input management service to determine the input equipment type corresponding to the input event and returning the input equipment type to the input method management service.

After receiving the registration listening request sent by the input method application, the input method management service may send a first message to the input management service. The first message is used for prompting the input management service to determine the input equipment type corresponding to the input event and returning the input equipment type to the input method management service.

It is understood that after the input method management service sends the first message to the input management service, the input method management service may receive the first message accordingly.

S603: the input method management service sends a registration listening receipt to the input method application.

Specifically, after receiving the registration interception request, the input method management service may send a registration interception receipt to the input method application. It will be appreciated that the registration snoop response piece may be used to indicate that the input method management service has successfully received the registration snoop request sent by the input method application.

It is understood that after the input method management service sends the registration listening receipt to the input method application, the input method application may receive the registration listening receipt accordingly.

S604: the input dispatcher sends input events to the input management service. The input event is an event generated by the electronic device 100 in response to a user operation on the input device.

In particular, a user may make inputs on the electronic device 100 using an input device, thereby generating various types of input events. Such as a key event, touch event, mouse event, etc. The original information generated by these input events can be collected by the input subsystem in the kernel layer and uploaded to the input manager, and then sent to the input management service by the input dispatcher in the input manager. It is understood that there is a communication connection between the input device and the electronic device 100. The communication connection mode between them may be a wired communication connection, and may also be a wireless communication connection (for example, a bluetooth connection, etc.), which is not limited in this application.

It is to be appreciated that after the input dispatcher sends an input event to the input management service, the input management service can receive the input event accordingly.

It is understood that input events may include, but are not limited to, keyboard events, stylus touch events, finger touch events, and the like. The keyboard event is an input event triggered by a user hitting a key on a keyboard. The stylus touch event is an input event triggered by a user touching a touch screen of the electronic device 100 with a stylus. The finger touch event is an input event triggered by a user touching a touch screen of the electronic device 100 with a finger. It is understood that similar to the finger touch event, the touch of the touch screen of the electronic device 100 by other parts of the human body can trigger the generation of the input event.

In some embodiments of the present application, the input operation performed by the user may include, but is not limited to, hitting a key on a keyboard, touching a touch screen of the electronic device 100 by a stylus or a finger, and the like.

In some embodiments of the present application, the input operation performed by the user is a focus acquisition operation. It is understood that the focus acquisition operation mentioned here may be a trigger operation performed with respect to an input area displayed by the electronic apparatus 100. The input area may include an edit box, a handwriting area, and the like. For example, the focus acquisition operation may be a click operation for an edit box displayed by the electronic apparatus 100.

In some embodiments of the present application, the input operation performed by the user is an input operation after the focus is acquired. For example, a keyboard is tapped for input. For another example, a stylus pen is used to write in the input area, thereby implementing input.

S605: the input management service determines the type of input device that triggered the input event.

Specifically, after the input management service receives the input event sent by the input dispatcher, the source of the input event can be determined, i.e., the type of input device that triggered the input event is determined.

It should be noted that the input management service may determine the type of input device that triggered the input event in a variety of ways.

In some embodiments of the present application, the input management service may determine, based on the type of input event, the input device to which the input event corresponds. Specifically, the input management service may obtain a correspondence between an input event type and an input device type, and after receiving an input event sent by the input distributor, may search for an input device type corresponding to the input event according to the type of the input event. It is understood that the correspondence between the input event type and the input device type may be stored in the input management service, and may also be stored in other areas. The input management service may invoke the correspondence.

As shown in table 1, table 1 shows an exemplary correspondence between input event types and input device types provided in an embodiment of the present application.

TABLE 1

Inputting event type	Input device type
		Finger touch event	Touch screen-finger
Stylus touch event	Touch screen-stylus pen
		Keyboard events	Keyboard with a keyboard body
…	…

As can be seen from table 1, when the input event type is a finger touch event, the corresponding input device type is touchscreen-finger. When the input event type is a stylus touch event, the corresponding input device is a touch screen-stylus. And when the input event type is a keyboard event, the corresponding input equipment is a keyboard. It is to be understood that table 1 is merely an example provided for the embodiments of the present application and should not be construed as limiting the present application.

It should be noted that in the actual input process, the input events generated by the electronic device 100 may be different for the same input device due to different triggering manners of the user. In this case, the types of input devices corresponding to the input events can be distinguished according to the triggering manner of the user. As shown in table 1, the two types of input events are essentially touch events, i.e., input events triggered by a touch screen. That is, the input device type corresponding to the two types of input events is a touch screen. However, the final generated input events differ due to different triggering manners of the users. Specifically, the user touches the touch screen with a finger, and the electronic device 100 may generate a finger touch event. And the user touches the touch screen with a stylus, the electronic device 100 may generate a stylus touch event. For the two types of input events, the corresponding input device types can be distinguished according to the triggering mode of the user. As shown in table 1, the input device type corresponding to the finger touch event may be a touch screen-finger, and the input device type corresponding to the stylus touch event may be a touch screen-stylus.

That is to say, the embodiment of the application can more finely divide the input event type and the input device type, prepare for subsequent input method calling or switching, and fully consider the input requirements of the user.

It is understood that, where an input device is available, the Linux kernel of the electronic device 100 creates a corresponding device node in User space (User space). After the input event is generated, the raw information associated with the input event may be collected by an input subsystem in the kernel layer. Specifically, the original information may be passed by a driver layer of a Kernel space (Kernel space) in the Kernel layer up to the device nodes in the user space. It is understood that the driver layer in the kernel space may include device drivers. Such as a touch screen drive, a keyboard drive, a mouse drive, and the like. It can be understood that there is a correspondence between device drivers and input devices.

It is understood that the kernel space is a running space of the Linux kernel, and can execute any command and call all resources of the system. The user space is the running space of the user program, can only execute simple operation, can not directly call system resources, and can only send instructions to the kernel through a system interface.

In some embodiments of the present application, the input management service may monitor all device nodes in the user space, process the data and find a suitable window when the device nodes have data, and dispatch the input event to the device nodes. It is appreciated that the input management service can determine the device node to which the received input event corresponds. According to the above, there is a correspondence between the device nodes and the input devices. The input management service may determine the input device type based on the device node to which the input event corresponds.

In some embodiments of the present application, the input management service may look up a transmission route of the input event and determine an input device driver corresponding to the input event, thereby determining the input device type.

In some embodiments of the present application, the input event carries input device information, which may be used to represent an input device.

It should be noted that the input management service may determine the input devices triggering different types of input events in different ways, which are only examples given in this application, and there are many more ways, which are not listed here.

S606: in the case where the input device type is different from the historical input device type or there is no historical input device type, the input management service transmits the input device type to the input method management service. The historical input device type is the type of the input device corresponding to the input event generated last time by the electronic device 100.

Specifically, after the input management service determines the input device type that triggers the input event, the input management service may send the input device type to the input method management service in the event that the input device type is different from or does not exist from the historical input device type. It can be understood that the historical input device type is the type of input device corresponding to the input event that was last generated by the electronic device 100. The case where the type of the input device mentioned in the present application is different from the type of the historical input device is that the input device adopted by the user when inputting this time is different from the input device adopted when inputting last time. The case where there is no history input type mentioned in the present application is that the input management service receives an input event triggered by a user making an input with an input device for the first time.

In some embodiments of the present application, after the input management service of the electronic device 100 determines the input device type triggering the input event, the input device type may be converted into a form satisfying the interface specification, and then the input device type satisfying the interface specification may be sent to the input method management service. It is understood that there is a correspondence between different forms of input device types. The correspondence may be stored in the input management service, or may be stored in another area. The input management service may invoke the correspondence.

In some embodiments of the present application, the input management service may send the code value corresponding to the input device type to the input method management service.

As shown in table 2, table 2 provides the types of input devices and their meanings and code values that satisfy the interface specification according to the embodiment of the present application.

TABLE 2

Input device type	Means of	Code value
			STYLUS	Writing pen	0x00005002
FINGER	Finger(s)	0x00002002
			KEYBOARD	Keyboard with a keyboard body	0x00000101
…	…	…

It will be appreciated that the meaning in table 2 corresponds to the type of input device that the input management service determines to trigger the input event. After the input management service determines the input device type triggering the input event, the input management service searches table 2 for the same meaning, thereby determining the input device type meeting the interface specification and the corresponding code value. For example, according to table 2, after the input management service determines that the input device type triggering the input event is touch screen-STYLUS pen, the input management service may search for the input device type, sty, corresponding to the STYLUS pen. It is understood that STYLUS means that the input device type is a STYLUS and that STYLUS satisfies the form of the interface specification. Accordingly, the input management service may determine that the value of the code corresponding to the STYLUS is 0x 00005002.

It is understood that after the input management service sends the input device type to the input method management service, the input method management service may receive the input device type accordingly. It is understood that the input device type may satisfy the interface specification. In some embodiments of the present application, the input device type may be a code value corresponding to the input device type.

S607: the input method management service sends interception callback information to the input method application. The snoop callback information includes an input device type.

Specifically, if the input device type is different from the historical input device type or the historical input device type does not exist, the input management service sends the input device type to the input method management service, and after receiving the input device type, the input method management service may send the interception callback information to the input method application. It is understood that the snoop callback information may include the input device type.

In some embodiments of the present application, the input method management service may send the snoop callback information to the input method application through the custom interface. It is understood that the custom interface is an interface that implements snoop callbacks. By way of example, the custom interface may be: devicechange, InputMethodManager # inputdevicelisterner. It can be understood that the parameters corresponding to the custom interface are the types of input devices that meet the interface specification. Illustratively, the parameter corresponding to the custom interface is inputType. In some embodiments of the present application, inputType corresponds to the input device types shown in Table 2.

S608: and the input method application determines the input method and calls the input method to input according to the monitoring callback information and the input method calling rule.

Specifically, the input method application determines an input method for inputting according to the input device type and the input method calling rule included in the monitoring callback information, and calls the input method for inputting. It is understood that the input method invocation rule refers to the correspondence existing between the input device type and the input method. The input method application may determine the input method to be finally invoked according to the correspondence and the input device type.

In some embodiments of the present application, the input device type is different from the historical input device type, and the input method application may switch the input method invoked according to the listened-for information and input method invocation rules.

As shown in table 3, table 3 provides an exemplary input method invocation rule for the embodiments of the present application.

TABLE 3

Input device type	Input method
		STYLUS	Hand writing input method
FINGER	Pinyin input method (Soft keyboard)
		KEYBOARD	Pinyin input method (suspension mode)
…	…

According to table 3, if the type of the input device included in the listening callback information received by the input method application is sty, the input method application determines to call a handwriting input method for input. Similarly, if the type of the input device included in the interception callback information received by the input method application is FINGER, the input method application determines to call the pinyin input method (soft keyboard) to perform input. If the type of the input equipment included in the monitoring callback information received by the input method application is KEYBOARD, the input method application determines to call a pinyin input method (suspension mode) for input.

It should be noted that the input method corresponding to the type of the input device may be preset by a technician or may be set by a user, which is not limited in this application. It is understood that the correspondence between the input device types and the input methods shown in table 3 is only one example provided in the present application, and the correspondence may also exist in other forms, which are not limited in the present application. For example, in the case that the input device type is pointer, the corresponding input method may be a five-stroke input method, a stroke input method, or the like.

It is understood that when the input method application calls an input method, the electronic device 100 may display a corresponding input interface. It should be noted that, when the input method called by the input method application is the same, the input interface displayed by the electronic device 100 may be different.

For example, as shown in table 3, in the case that the input device type is filler, the input method application may determine to call a pinyin input method (soft keyboard) for input, and the input area in the input interface displayed by the electronic device 100 may include the soft keyboard. It is understood that the soft keyboard can be in the form of a Pinyin full-key soft keyboard (26 keys) or a Pinyin nine-key soft keyboard (9 keys). The specific form of the soft keyboard may be preset by a technician, or may be set by a user, which is not limited in this application.

For example, as shown in table 3, in the case that the input device type is KEYBOARD, the input method application may determine to call the pinyin input method (hover mode) for input, and the input area in the input interface displayed by the electronic device 100 may include a hover toolbar of the pinyin input method. It is understood that the pinyin input method hover toolbar may be used to switch to other input methods.

It should be noted that the input interface displayed when the electronic device 100 invokes the input method corresponding to the input device type may have various forms, and the content of the input area in the input interface may be preset by a technician or may be set by a user. For example, in the case that the input device type is pointer, the content of the input area in the input interface displayed by the electronic device 100 may be a pinyin full-key soft keyboard or a pinyin nine-key soft keyboard. For another example, in a case that the input device type is KEYBOARD, the content of the input area in the input interface displayed by the electronic device 100 may be a pinyin full-key soft KEYBOARD, or may be a pinyin input method floating toolbar.

It should be noted that, in some embodiments of the present application, when the user uses the input device to perform input in the electronic device 100, the input method does not send the registration listening request to the input method management service. This is because the input method has already sent the registration monitoring request to the input method management service when the user previously input, so the input method application does not need to send the registration monitoring request to the input method management service again when the user subsequently inputs again. In this case, the electronic apparatus 100 may not perform steps S601 to S603.

According to the above process, the electronic device 100 can adaptively call the input method or switch the input method according to the type of the input device, so that the user does not need to perform manual switching, and the user experience is improved.

Referring to fig. 7, fig. 7 is a flowchart of another input method invoking method according to an embodiment of the present application, where the input method invoking method may include, but is not limited to, the following steps:

s701: at a first time, in response to a first operation, the electronic device 100 generates a first input event. The first input event is an input event generated aiming at the first input device.

Specifically, the user may perform a first operation, and accordingly, at a first time, the electronic device 100 may generate a first input event in response to the first operation. It is understood that the first input event is an input event generated for the first input device.

It is understood that the first input device may include, but is not limited to, a keyboard, a stylus, etc. In some embodiments of the present application, the first input device may also be a touch screen.

It is understood that the first input event may include, but is not limited to, a keyboard event, a stylus touch event, a finger touch event, and the like. The keyboard event is an input event triggered by a user hitting a key on a keyboard. The stylus touch event is an input event triggered by a user touching a touch screen of the electronic device 100 with a stylus. The finger touch event is an input event triggered by a user touching a touch screen of the electronic device 100 with a finger. It is understood that, similar to the finger touch event, the input event triggered by touching the touch screen of the electronic device 100 with other parts of the human body may also belong to the first input event.

In some embodiments of the present application, the first operation performed by the user is an input operation for inputting with the first input device. It is understood that the input operations mentioned herein may include, but are not limited to, hitting keys on a keyboard, touching a touch screen of the electronic device 100 by a stylus or a finger, and the like.

In some embodiments of the present application, the first operation performed by the user is a focus acquisition operation. It is understood that the focus acquisition operation mentioned here may be a trigger operation performed with respect to an input area displayed by the electronic apparatus 100. The input area may include an edit box, a handwriting area, and the like. For example, the focus acquisition operation may be a click operation for an edit box displayed by the electronic apparatus 100.

It should be noted that before step S701 is executed, the electronic device 100 may register a listening input device, and details may refer to step S601, which is not described in detail herein.

In addition, before the electronic device 100 registers the listening input device, the input method application in the electronic device 100 may be initialized, and the detailed content may refer to step S601, which is not described in detail herein.

S702: the electronic device 100 calls a first input method based on the first input event and displays a first interface.

Specifically, after the electronic device 100 generates the first input event, the electronic device 100 may determine a source of the first input event, that is, determine a first input device corresponding to the first input event, call the first input method according to a device type of the first input device, and then display the first interface. It is understood that the first interface may include a first input method display area. The first input method display area may be used to display a first input method.

It should be noted that, reference may be made to the above for a specific manner of the electronic device 100 invoking the first input method based on the first input event, and details are not described herein again.

It is understood that the first input method is an input method specifically called by the electronic device 100. Such as a full-spelling input method, a five-stroke input method, a handwriting input method, etc.

It should be noted that the electronic device 100 may store the correspondence between the input device type and the input method. In some embodiments of the present application, the correspondence between the input device type and the input method may be preset by a technician, in which case, the electronic device 100 stores the correspondence when it leaves the factory. In still other embodiments of the present application, the correspondence between the input device type and the input method may be set by a user.

S703: at a second time, in response to a second operation, the electronic device 100 generates a second input event. Wherein the second input event is an input event generated for the second input device.

Specifically, the user may perform a second operation, and accordingly, at a second time, in response to the second operation, the electronic device 100 may generate a second input event. It is understood that the second input event is an input event generated for the second input device.

It is understood that the second input device may include, but is not limited to, a keyboard, a stylus, etc. In some embodiments of the present application, the second input device may also be a touch screen.

It is understood that the second input event may include, but is not limited to, a keyboard event, a stylus touch event, a finger touch event, and the like. For the description of the keyboard event, the stylus touch event, and the finger touch event, reference may be made to step S701, which is not described herein again.

In some embodiments of the present application, the second operation performed by the user is an input operation for inputting with the second input device. It is understood that the input operations mentioned herein may include, but are not limited to, hitting keys on a keyboard, touching a touch screen of the electronic device 100 by a stylus or a finger, and the like.

In some embodiments of the application, the second operation performed by the user is a focus obtaining operation, and may also be an input operation after obtaining the focus, and the detailed content may refer to step S701, which is not described herein again.

It should be noted that the first input device and the second input device are different input devices. Illustratively, the first input device is a stylus and the second input device is a keyboard.

S704: the electronic device 100 calls a second input method based on the second input event and displays a second interface.

Specifically, after the electronic device 100 generates the second input event, the electronic device 100 may determine a source of the second input event, that is, determine a second input device corresponding to the second input event, call the second input method according to the device type of the second input device, and then display the second interface. It is understood that the second interface may include a second input method display area. The second input method display area may be used to display a second input method.

It should be noted that, reference may be made to the above for a specific manner of the electronic device 100 invoking the second input method based on the second input event, and details are not described herein again.

It is understood that the second input method is an input method specifically called by the electronic device 100. Such as a full-spelling input method, a five-stroke input method, a handwriting input method, etc.

In some embodiments of the present application, the first input method and the second input method are different input methods. Illustratively, the first input method is a full-spelling input method, and the second input method is a handwriting input method. In yet other embodiments of the present application, the first input method and the second input method may be the same input method.

Illustratively, in the case that the first input device is a touch screen and the first operation is a finger touch operation, the first input method is a full-spelling input method, and the first input method display area on the first interface displays a full-spelling soft keyboard. And under the condition that the second input equipment is a keyboard and the second operation is a keyboard knocking operation, the second input method is a full-spelling input method, and the second input method display area on the second interface displays the input method suspension tool.

It should be noted that the first interface and the second interface are different interfaces. The first interface displays a first input method, and the second interface displays a second input method. The first input method is different from the second input method.

The above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and these modifications or substitutions do not depart from the scope of the technical solutions of the embodiments of the present application.

Claims

1. The input method calling method is characterized in that the method is applied to electronic equipment; the method comprises the following steps:

receiving a first operation, and responding to the first operation to display a first interface; the first operation is an input operation performed by a first input mode; the first interface displays a first input method; the first input method is an input method corresponding to the first input mode;

receiving a second operation, and responding to the second operation to display a second interface; the second operation is an input operation performed by a second input mode; the second interface displays a second input method; the second input method is an input method corresponding to the second input mode;

wherein the first input method is different from the second input method.

2. The method of claim 1, wherein the first input mode is a mode of input using a first input device; the second input mode is a mode of inputting by using second input equipment;

the first input method is an input method corresponding to the first input mode, and specifically includes: the first input method is an input method corresponding to a first equipment type; the first equipment type is the equipment type corresponding to the first input equipment;

the second input method is an input method corresponding to the second input mode, and specifically includes: the second input method is an input method corresponding to a second equipment type; the second device type is a device type corresponding to the second input device.

3. The method of claim 1 or 2, wherein prior to displaying the first interface in response to the first operation, the method further comprises:

sending a registration monitoring request to an input method management service in the electronic equipment through an input method application in the electronic equipment based on a first interface; the registration monitoring request is used for requesting the input method management service to monitor the input equipment;

sending a first message to an input management service in the electronic device through the input method management service; the first message is used to request the input management service to listen to an input device.

4. The method of claim 3, wherein the displaying the first interface in response to the first operation specifically comprises:

generating a first input event in response to the first operation; the first input event is an input event generated for the first input device;

calling the first input method based on the first input event, and displaying the first interface;

responding to the second operation, displaying a second interface, specifically comprising:

generating a second input event in response to the second operation; the second input event is an input event generated for the second input device;

and calling the second input method based on the second input event, and displaying the second interface.

5. The method of claim 4, wherein invoking the first input method based on the first input event specifically comprises:

determining the first equipment type based on the first input event through the input management service, and reporting the first equipment type to the input method management service;

comparing, by the input management service, the first device type to a first historical device type; the first historical device type is a device type of an input device corresponding to a last input event of the first input event generated by the electronic device;

if the first equipment type is different from the first historical equipment type or the first historical equipment type does not exist, sending monitoring callback information to the input method application through the input method management service based on a second interface; the interception callback information comprises the first device type;

searching the first input method in an input method calling rule according to the first equipment type in the monitoring callback information through the input method application, and calling the first input method; the input method calling rule comprises a corresponding relation between the equipment type corresponding to the input equipment and the input method.

6. The method according to claim 4 or 5, wherein the invoking a second input method based on the second input event specifically comprises:

determining the second equipment type through the input management service based on the second input event, and reporting the second equipment type to the input method management service;

comparing, by the input management service, the second device type to the second historical device type; the second historical device type is a device type of an input device corresponding to a last input event of the second input event generated by the electronic device;

if the second device type is different from the second historical device type or the second historical device type does not exist, sending monitoring callback information to the input method application through the input method management service based on a second interface; the interception callback information comprises the second device type;

and searching the second input method in the input method calling rule according to the second equipment type in the monitoring callback information by the input method application, and calling the second input method.

7. The method of claim 6, wherein a last input event of the second input event generated by the electronic device is the first input event; the second historical device type is the first device type.

8. The method of any of claims 1-7, wherein the first interface and the second interface are user interfaces of a first application; the first application is an application in the electronic equipment; the first operation is used for prompting the first application to acquire a focus.

9. The method of claim 8, wherein the second operation is to prompt the first application to obtain focus.

10. The method of any of claims 1-7, wherein the first interface is a user interface of a first application; the second interface is a user interface of a second application; the first application and the second application are applications in the electronic device; the first operation is used for prompting the first application to acquire a focus; the second operation is used for prompting the second application to acquire a focus.

11. The input method calling method is characterized in that the method is applied to electronic equipment; the method comprises the following steps:

receiving a target operation, and generating a target input event in response to the target operation; the target operation is an input operation performed by an input device;

determining the type of target equipment based on the target input event through an input management service, and reporting the type of the target equipment to an input method management service; the target equipment type is the equipment type of the input equipment;

comparing, by the input management service, the target device type to a historical device type; the historical device type is a device type of an input device corresponding to a last input event of the target input event generated by the electronic device;

if the target equipment type is different from the historical equipment type or the historical equipment type does not exist, sending monitoring callback information to an input method application in the electronic equipment through the input method management service; the interception callback information comprises the type of the target equipment;

searching a target input method in an input method calling rule according to the type of the target equipment in the monitoring callback information through the input method application; the input method calling rule comprises a corresponding relation between a device type corresponding to the input device and the input method;

calling the target input method and displaying an input interface; the target input method is displayed on the input interface.

12. The method of claim 11, wherein prior to generating a target input event in response to the target operation, the method further comprises:

sending a registration monitoring request to the input method management service through the input method application based on a first interface; the registration monitoring request is used for requesting the input method management service to monitor the input equipment;

sending a first message to the input management service through the input method management service; the first message is used to request the input management service to listen to an input device.

13. The method of claim 11 or 12, wherein determining, by the input management service, the target device type based on the target input event comprises:

determining, by the input management service, that the target device type is a first device type if the target input event is a first input event;

determining, by the input management service, that the target device type is a second device type if the target input event is a second input event;

determining, by the input management service, that the target device type is a third device type if the target input event is a third input event;

the first input event is a finger touch event, and the first device type is a touch screen-finger; the second input event is a stylus touch event, and the second device type is a touch screen-stylus; the third input event is a keyboard event and the third device type is a keyboard.

14. An electronic device comprising a display screen, memory, one or more processors, wherein the memory is configured to store a computer program; the processor is configured to invoke the computer program to cause the electronic device to perform the method of any of claims 1-10.

15. An electronic device comprising a display screen, memory, one or more processors, wherein the memory is configured to store a computer program; the processor is configured to invoke the computer program to cause the electronic device to perform the method of any of claims 11-13.

16. A computer storage medium, comprising: computer instructions; the computer instructions, when executed on an electronic device, cause the electronic device to perform the method of any of claims 1-10.

17. A computer storage medium, comprising: computer instructions; the computer instructions, when executed on an electronic device, cause the electronic device to perform the method of any of claims 11-13.