WO2023124141A1

WO2023124141A1 - Input method calling method and related device

Info

Publication number: WO2023124141A1
Application number: PCT/CN2022/114289
Authority: WO
Inventors: 贾宇刚
Original assignee: 荣耀终端有限公司
Priority date: 2021-12-27
Filing date: 2022-08-23
Publication date: 2023-07-06
Also published as: CN114489350A; WO2023124141A9; CN114489350B

Abstract

An input method calling method and a device. In the input method calling method, an electronic device (100) triggers the monitoring of an input device when an input method application is started, and after the input method application receives monitoring callback information, an input method which needs to be called is determined according to the type of an input device that is included in the monitoring callback information. In the input method calling method, the electronic device (100) adaptively provides a more rational input method according to an input mode and the type of an input device, without the need for a user to manually switch the input method, thereby improving the user experience.

Description

An input method calling method and related equipment

This application claims the priority of the Chinese patent application with the application number 202111610264.5 and the application name "A Method for Calling Input Method and Related Equipment" submitted to the China Patent Office on December 27, 2021, the entire contents of which are incorporated herein by reference Applying.

technical field

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

Background technique

At present, terminal devices such as mobile phones and tablet computers are developing more and more rapidly. With the continuous development of terminal equipment, user needs are also constantly changing, gradually developing from the final basic communication needs to multi-dimensional communication and entertainment needs such as vision, hearing and touch. Therefore, more and more terminal equipment manufacturers are increasingly Pay attention to human-computer interaction. In order to improve the ease of use and user-friendliness of terminal equipment, some manufacturers have begun to develop some equipment used in conjunction with the terminal equipment. For example, stylus, keyboard, etc. Users can use these input devices to better realize their own input needs. It can be understood that, due to the differences in input methods of users through these input devices (for example, touch input and keyboard input), the applicable input modes of different input devices may be different. For example, stylus input may be applicable to handwriting input method, and keyboard input may be applicable to keyboard input method.

However, no matter 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 device changes, the user needs to manually switch the input method, which affects the user experience.

Therefore, how to call the input method according to the adaptability of the input device is an urgent problem to be solved at present.

Contents of the invention

The present application provides an input method calling method and related equipment, which can determine the input device type according to the generated input event, find the input method corresponding to the input device type in the input method calling rules, and then call the input method. In this way, the input method can be adaptively invoked according to the input device used by the user, without the need for the user to manually switch the input method, which reduces the redundant operation of the user and improves the user experience.

In a first aspect, the present application provides a method for invoking an input method. The method can be applied to electronic devices. The method may include: receiving a first operation, and displaying a first interface in response to the first operation; the first operation is an input operation performed through a first input method; the first interface displays a first input method ; The first input method is an input method corresponding to the first input method; receiving a second operation, and displaying a second interface in response to the second operation; the second operation is performed through the second input method input operation; the second interface displays a second input method; the second input method is an input method corresponding to the second input method; wherein, the first input method is different from the second input method Law.

In the solution provided by the present application, at the first moment, the electronic device may receive an input operation performed by the user through a first input method, and in response to the input operation, the electronic device may display a first interface including the first input method. At a 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. Wherein, the first input method corresponds to the first input method, and the second input method corresponds to the second input method. That is to say, the electronic device can determine the input method to be invoked according to the user's input method, and display the input method on the user interface. Invoking the input method through this input method calling method, the input method called and displayed by the electronic device can be determined according to the user's input method, and not every input method called is the default input method or the historical input method. In this case, the user does not need to manually switch to an input method that is more suitable for the current input method, which fully considers the user's experience and improves the user experience.

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 may be a finger touch operation, a stylus touch operation, and a keyboard tapping operation. The second input method may also be a finger touch method, a stylus touch method, or a keyboard input method. The corresponding second operation may be a finger touch operation, a stylus touch operation, and a keyboard tapping operation.

Exemplarily, the first input method may be a finger touch method, and the second input method may be a stylus touch method. The user first performs input on the electronic device through a finger touch operation, and the electronic device invokes a pinyin input method and displays a soft keyboard on the user interface for the user to input. Then, the user turns to use a stylus for input, and the electronic device detects that the current input device used by the user is a touch screen-stylus, and the electronic device invokes the handwriting input method and displays a handwriting area on the 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 method is an input method using a first input device; the second input method is an input method using a second input device method; the first input method is an input method corresponding to the first input method, specifically including: the first input method is an input method corresponding to the first device type; the first device type is the input method The device type corresponding to the first input device; the second input method is an input method corresponding to the second input method, specifically including: the second input method is an input method corresponding to the second device type; The second device type is a device type corresponding to the second input device.

In the solution provided by the present application, the first input method may be an input method using a first input device, and the second input method may be an input method using a second input device. The electronic device includes the corresponding relationship between the device type of the input device and the input method. After receiving the user's input operation, the electronic device can find the corresponding input method according to the input device used by the input operation, and invoke and display the input method. That is to say, the electronic device can determine the input method to be invoked according to the device type of the input device. In other words, the user does not need to manually switch to an input method that is more suitable for the current input device, which fully considers the user's experience and improves the user experience.

In some embodiments of the present application, the electronic device may determine the input device based on the input method, and then determine the input method that needs to be invoked. Exemplarily, when 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 a keyboard based on the first input device. Exemplarily, 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 touch mode, the first input device is a stylus, and the electronic device may determine that the first device type is a stylus.

In some embodiments of the present application, the electronic device may also determine the input method to be invoked according to the input method and the input device. For example, when the user uses a finger touch method and a stylus touch method for input, the input device is a touch screen, but due to different operations on the touch screen (different input methods), different input events are generated. In this case, the electronic device can combine the input method and the input device to determine the device type of the input device, so as to determine the input method that needs to be invoked. Exemplarily, when the first input mode is a finger 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-finger based on the first input mode and the first input device. When 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 displaying the first interface in response to the first operation, the method further includes: using an input method application in the electronic device based on the first An interface sends a registration monitoring request to the input method management service in the electronic device; the registration monitoring request is used to request the input method management service to monitor the input device; send the electronic device through the input method management service The input management service in sends a first message; the first message is used to request the input management service to monitor the input device.

In the solution provided by the present application, the electronic device needs to monitor the input device, so as to call the input method according to the input device. 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 monitoring of the input device. It can be understood that, in essence, it is the input management service that implements monitoring in the electronic device. The input management service monitors input devices by monitoring input events. That is to say, the input management service can determine the input device through the input event reported by the input distributor. Once the input device corresponding to the input event changes, the input management service can pass 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 determines the input method that needs to be switched. The monitoring input device mentioned in the above process is the premise of calling the input method according to the type of the input device, and is an indispensable step to realize the adaptive calling of the input method.

It can be understood that, in fact, the input method application does not need to send a registration monitoring request to the input method management service every time the input method is invoked. In some embodiments of the present application, when the life cycle of the input method is not over, the input method application can call or switch the input method without sending a registration monitoring request.

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

It should be noted that the first interface is a custom interface and is used to send a registration monitoring request. For the relevant description of the first interface, reference may be made later, and no further description is given here.

With reference to the first aspect, in a possible implementation manner of the first aspect, the displaying the 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; based on the first input event, the first input method is invoked, and the first interface is displayed; in response to the second operation, displaying The second interface specifically includes: 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; calling the second input event based on the second input event The second input method is selected, and the second interface is displayed.

In the solution provided by the present application, in response to a user's input operation, the electronic device can generate an input event. The electronic device can determine the type of the input device according to the input event, so as to determine the input method that needs to be invoked. Specifically, the input event dispatcher in the electronic device can report the generated input event to the input management service, and the input management service can determine the input device type according to the input event, and pass the input device type to the input method management service, and finally to the The input method is applied, thereby calling the corresponding input method. In this way, the user does not need to manually switch to an input method that is more suitable for the current input device, which fully considers the user's experience and improves the user experience. In addition, the user does not need to use other applications other than the input method application to determine the input method to be invoked.

With reference to the first aspect, in a possible implementation manner of the first aspect, invoking the first input method based on the first input event specifically includes: using the input management service to determine based on the first input event The first device type, and report the first device type to the input method management service; compare the first device type with the first historical device type through the input management service; the first historical device type The 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; if the first device type is different from the first historical device type or the first historical device type does not exist A historical device type, sending monitoring callback information to the input method application based on the second interface through the input method management service; the monitoring callback information includes the first device type; the input method application according to the monitoring callback For the first device type in the information, search for the first input method in the input method call rule, and call the first input method; the input method call rule includes the device type corresponding to the input device and the input method Correspondence between.

In the solution provided by this application, the input management service can 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 judge whether the current input device type needs to be changed according to the comparison result. Passed to the input method management service. If the current input device type is different from the historical device type or there is no historical device type, the input management service can pass the input device type to the input method management service. That is to say, if the device type used 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 can pass the input device type to the input method management service, and then the input method management service passes For the input method application, the input method application finally finds the input method corresponding to the input device type according to the input method calling rules, and calls and displays the input method. It can be understood that in this way, the user does not need to manually switch the appropriate input method, which improves the user experience.

It can be understood that the input method calling rule includes the corresponding 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 can be understood that the second interface is a custom interface, which is used to transmit monitoring callback information. The monitoring callback information may include the type of the input device. For the relevant description of the second interface, reference may be made later, and no further description is given here.

With reference to the first aspect, in a possible implementation manner of the first aspect, invoking the second input method based on the second input event specifically includes: using the input management service to determine based on the second input event the second device type, and report the second device type to the input method management service; use the input management service to compare the second device type with the second historical device type; the second The 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; if the second device type is different from the second historical device type or does not exist The second historical device type, through the input method management service to send monitoring callback information to the input method application based on the second interface; the monitoring callback information includes the second device type; the input method application according to the Monitoring the second device type in the callback information, searching for the second input method in the input method calling rules, and calling the second input method.

It can be 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 solution provided by this application, the input management service can 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 judge whether the current input device type needs to be changed according to the comparison result. Passed to the input method management service. Reference can be made to the above for specific descriptions and beneficial effects, and will not be repeated here.

With reference to the first aspect, in a possible implementation manner of the first aspect, the 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.

In the solution provided by this application, the first input event may be a previous input event of the second input event. That is to say, when the user performs input on the electronic device, he switches from the first input device to the second input device. Due to the change of the input device and the type of the input device, the input method invoked and displayed by the electronic device also changes—from the previous first input method to the second input method. In this process, the user no longer needs to manually switch the input method, which improves the user experience.

Exemplarily, the first input device is a touch screen-finger, and the second input device is a touch screen-stylus. The user first uses fingers to input on the soft keyboard displayed on the electronic device, and then switches to the stylus for input. It can be understood that the user can use the stylus to directly input on the screen of the electronic device. That is to say, once the stylus touches the touch screen of the electronic device and generates a touch event of the stylus, the electronic device can 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 device ; The first operation is used to prompt the first application to acquire focus.

In the solution provided by the present application, both the first interface and the second interface are user interfaces of the first application. Before displaying the first interface, the electronic device may display the third interface. It can be understood that the first operation may be an input operation for a corresponding edit control in the third interface (for example, clicking on the edit control). After the electronic device receives the first operation and before displaying the first interface, the first application in the electronic device can obtain the focus, and notify the input method management service that it has obtained the focus and request to bind the input method.

It can be understood that the edit control is a control used for input editing. For example, edit boxes, 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 obtain the focus.

In the solution provided by the present application, the second operation may be an input operation (for example, clicking on an edit control) on a corresponding edit control included in other user interfaces in the first application. After the electronic device receives the second operation and before displaying the second interface, the first application in the electronic device can obtain the focus, and notify the input method management service that it has obtained the focus and request to bind the input method. That is to say, after the first application displays the first interface and before displaying the second interface, it needs to reacquire the focus so as to display the input method, thereby implementing 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 is an application in the electronic device; the first operation is used to prompt the first application to obtain focus; the second operation is used to prompt the second application to obtain focus.

In the solution provided by the present application, the first interface is the user interface of the first application, and the second interface is the user interface of the second application. Users can switch between different input devices to input in different applications. In this case, the first operation may be an input operation directed at the edit control of the corresponding interface of the first application, and the second operation may be an input operation directed at the edit control of the corresponding interface of the second application.

In a second aspect, the present application provides an input method calling method. The method can be applied to electronic devices. The method may include: receiving a target operation, generating a target input event in response to the target operation; determining the target device type based on the target input event through the input management service, and reporting the target device type to the input method management service; Compare the target device type with the historical device type through the input management service; 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; if the If the target device type is different from the historical device type or the historical device type does not exist, the monitoring callback information is sent to the input method application in the electronic device through the input method management service; the monitoring callback information includes the Target device type; use the input method application to search for the target input method in the input method call rule according to the target device type in the monitoring callback information; the input method call rule includes the device type corresponding to the input device Correspondence between input methods; call the target input method, and display an input interface; the input interface displays the target input method.

In the solution provided by the present application, the electronic device can generate a target input event in response to a user's target operation, and determine the target device type according to the target input event. The electronic device can search the input method corresponding to the target device type in the input method calling rule, and call the input method. With this method, the user does not need to manually switch to an input method that is more suitable for the current input device, which fully considers the user's experience and improves the user experience.

It can be understood that the target operation is an input operation performed by an input device. A target input event is an input event generated for a target action. The target device type is the device type of the input device.

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

With reference to the second aspect, in a possible implementation manner of the second aspect, the determining the target device type based on the target input event through the input management service specifically includes: when the target input event is the first input event In this case, the input management service determines that the target device type is the first device type; when the target input event is the second input event, the input management service determines that the target device type is the second Two device types: when the target input event is a third input event, determine that the target device type is a third device type through the input management service.

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

It can be understood that the user may use different input devices to perform input, and 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 keyboard tapping operation. Correspondingly, the target input event may be a finger touch event, a stylus touch event, and a keyboard event.

Understandably, the target input event may also be other types of input events. For example, mouse events, key events, etc.

In a third aspect, the present application provides an electronic device. The electronic equipment includes a receiving module and a display module. Wherein, the receiving module is configured to receive the first operation; the display module is configured to display the first interface in response to the first operation. It can be understood that the first operation is an input operation performed through the first input method, and the first interface displays the first input method. The first input method is an input method corresponding to the first input mode. The receiving module is further configured to receive the second operation. The display module is further configured to display a second interface in response to the second operation. It can be understood that the second operation is an input operation performed through the second input method, and the second interface displays the 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 mode is an input mode using a first input device; the second input mode is an input mode using a second input device. The first input method is an input method corresponding to the first input method, specifically including: the first input method is an input method corresponding to the 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 method, specifically including: the second input method is an input method corresponding to the 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 may be configured to send a registration monitoring request to the input method management service based on the first interface. The registration monitoring request is used to request the input method management service to monitor the input device. The input method management service may be used to send the first message to the input management service. The first message is used to request the input management service to monitor 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 generating module. An input event generating module, configured to generate a first input event in response to the first operation. The input management service is further configured to determine the first device type based on the first input event, and report the first device type to the input method management service; compare the first device type with the first historical device type. Wherein, 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 configured to send monitoring callback information to the input method application through the second interface when the first device type is different from the first historical device type or the first historical device type does not exist. The monitoring callback information includes the first device type. The input method application is configured to search for the first input method in the input method calling rule according to the first device type in the monitoring callback information, and call the first input method. The input method calling rule includes the corresponding relationship between the device type corresponding to the input device 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 further configured to determine the second device type based on the second input event, and report the second device type to the input method management service; compare the second device type with the second historical device type. Wherein, 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 input method management service is further configured to send monitoring callback information to the input method application through the second interface when the second device type is different from the second historical device type or there is no second historical device type. The monitoring callback information includes the second device type. The input method application is further configured to search for the second input method in the input method calling rule according to the second device type in the monitoring callback information, and call the second input method.

With reference to the third aspect, in a possible implementation manner of the third aspect, the 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.

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 device ; The first operation is used to prompt the first application to acquire 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 obtain the 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 is an application in the electronic device; the first operation is used to prompt the first application to obtain focus; the second operation is used to prompt the second application to obtain 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 management service, an input method application and a display module. Wherein, the receiving module is used for receiving the target operation. The input event generating module is used for generating a target input event in response to the target operation. The target operation is an input operation performed using an input device. The input management service is used to determine the target device type based on the target input event, and report the target device type to the input method management service; compare the target device type with the historical device type. The target device type is the 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 input method management service is used to send monitoring callback information to the input method application in the electronic device through the input method management service when the target device type is different from the historical device type or there is no historical device type. The monitoring callback information includes the target device type. The input method application is used to search for the target input method in the input method calling rules according to the target device type in the monitoring callback information, and call the target input method. The input method calling rule includes the corresponding relationship between the device type corresponding to the input device and the input method. The display module is used for displaying the input interface. The input interface displays the target input method.

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

With reference to the fourth aspect, in a possible implementation manner of the fourth aspect, when the input management service is used to determine the target device type based on the target input event, it is specifically used to: when the target input event is the first input event , the target device type is determined to be the first device type by the input management service; if the target input event is the second input event, the target device type is determined to be the second device type by the input management service; if the target input event is the third input event In the case of an event, the target device type is determined to be the third device type through the input management service. Wherein, 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 second The third device type is keyboard.

In a fifth aspect, the present application provides an electronic device. The electronic device may include a display screen, memory, and one or more processors. Wherein, one or more processors are coupled with a memory, and the memory is used to store computer program codes, and the computer program codes include computer instructions. The electronic device may receive a first operation. The display screen is used to display the first interface in response to the first operation, and is also used to display the second interface in response to the second operation. Wherein, the first operation is an input operation performed through a first input mode. The first interface displays the first input method. The first input method is an input method corresponding to the first input mode. The second operation is an input operation performed through the second input mode. The second interface displays the 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 of the fifth aspect, the first input method is an input method using a first input device; the second input method is an input method using a second input device. The first input method is an input method corresponding to the first input method, specifically including: the first input method is an input method corresponding to the 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 method, specifically including: the second input method is an input method corresponding to the 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 of the fifth aspect, the processor is configured to use the input method application in the electronic device to send a registration monitoring request to the input method management service in the electronic device based on the first interface; The input method management service sends the first message to the input management service in the electronic device. Wherein, the registration monitoring request is used to request the input method management service to monitor the input device. The first message is used to request the input management service to monitor 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; and invoke the first input method based on the first input event. The first input event is an input event generated for the first input device. The processor is further configured to generate a second input event in response to the second operation; and invoke the second input method based on the second input event. The second input event is an input event generated for the second input device.

With reference to the fifth aspect, in a possible implementation manner of the fifth aspect, when the processor is configured to call the first input method based on the first input event, it is specifically configured to: use the input management service to determine based on the first input event The first device type, and report the first device type to the input method management service; compare the first device type with the first historical device type through the input management service; if the first device type is different from the first historical device type or there is no first device type A historical device type, through the input method management service to send monitoring callback information to the input method application based on the second interface; through the input method application, according to the first device type in the monitoring callback information, search for the first input method in the input method call rule, And call the first input method. Wherein, 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 monitoring callback information includes the first device type. The input method calling rule includes the corresponding relationship between the device type corresponding to the input device and the input method.

With reference to the fifth aspect, in a possible implementation manner of the fifth aspect, when the processor is configured to call the second input method based on the second input event, it is specifically configured to: use the input management service to determine based on the second input event The second device type, and report the second device type to the input method management service; compare the second device type with the second historical device type through the input management service; if the second device type is different from the second historical device type or there is no first Two historical device types, send monitoring callback information to the input method application based on the second interface through the input method management service; through the input method application, search for the second input method in the input method calling rules according to the second device type in the monitoring callback information, And call the second input method. Wherein, 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 monitoring callback information includes the second device type.

With reference to the fifth aspect, in a possible implementation manner of the fifth aspect, a previous 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.

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 used 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 obtain the 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 the second application. The first application and the second application are applications in the electronic device. The first operation is used to prompt the first application to obtain focus. The second operation is used to prompt the second application to obtain the focus.

In a sixth aspect, the present application provides an electronic device. The electronic device may include a display screen, memory, and one or more processors. Wherein, one or more processors are coupled with a memory, and the memory is used to store computer program codes, and the computer program codes include computer instructions. The electronic device can receive the target operation. The processor can be used to generate a target input event in response to the target operation; determine the target device type based on the target input event through the input management service, and report the target device type to the input method management service; compare the target device type through the input management service and the historical device type; if the target device type is different from the historical device type or there is no historical device type, send monitoring callback information to the input method application in the electronic device through the input method management service; through the input method application, according to the monitoring callback information Target device type, find the target input method in the input method call rule; call the target input method, and display the input interface; the input interface displays the target input method. Wherein, the target operation is an input operation performed by an input device. The target device type is the 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 monitoring callback information includes the target device type. The input method calling rule includes the corresponding relationship between the device type corresponding to the input device 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 use the input method application in the electronic device to send a registration monitoring request to the input method management service in the electronic device based on the first interface; Send the first message to the input management service in the electronic device through the input method management service. Wherein, the registration monitoring request is used to request the input method management service to monitor the input device. The first message is used to request the input management service to monitor the input device.

With reference to the sixth aspect, in a possible implementation manner of the sixth aspect, when the processor is configured to determine the target device type based on the target input event, it is specifically configured to: when the target input event is the first input event , the target device type is determined to be the first device type by the input management service; if the target input event is the second input event, the target device type is determined to be the second device type by the input management service; if the target input event is the third input event In the case of an event, the target device type is determined to be the third device type through the input management service. Wherein, 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 second The third device type is keyboard.

In a seventh aspect, the present application provides a computer storage medium, including instructions, which, when the instructions are run on an electronic device, cause the electronic device to execute any possible implementation manner in the first aspect above.

In an eighth aspect, the present application provides a computer storage medium, including instructions, which, when the instructions are run on an electronic device, cause the electronic device to execute any possible implementation manner in the second aspect above.

In the ninth aspect, the embodiment of the present application provides a chip, the chip is applied to electronic equipment, and the chip includes one or more processors, and the processor is used to call computer instructions to make the electronic equipment execute any one of the above first aspects a possible implementation.

In a tenth aspect, an embodiment of the present application provides a chip, the chip is applied to an electronic device, and the chip includes one or more processors, and the processor is used to invoke computer instructions so that the electronic device executes any one of the above-mentioned second aspects. a possible implementation.

In the eleventh aspect, the embodiment of the present application provides a computer program product containing instructions, which, when the computer program product is run on the device, causes the electronic device to execute any possible implementation of the first aspect above.

In a twelfth aspect, an embodiment of the present application provides a computer program product including instructions, which, when the computer program product is run on a device, cause the electronic device to execute any possible implementation manner in the second aspect above.

It can be understood that the beneficial effect of the input method invoking method provided by the second aspect above can refer to the beneficial effect of any possible implementation manner in the first aspect, which will not be repeated here. In addition, the electronic equipment provided in the third aspect and the fifth aspect, the computer storage medium provided in the seventh aspect, the chip provided in the ninth aspect, and the computer program product provided in the eleventh aspect are all used to implement the above-mentioned first aspect. any possible implementation. The electronic equipment provided by the fourth aspect and the sixth aspect above, 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 used to implement any one of the above second aspects a possible implementation. Therefore, for the beneficial effects that can be achieved, reference may be made to the beneficial effects of any possible implementation manner in the first aspect above, which will not be repeated here.

Description of drawings

FIG. 1 is a schematic diagram of an input method calling scenario provided by an embodiment of the present application;

2A-2K are schematic diagrams of a group of user interfaces provided by the embodiment of the present application;

FIG. 3 is a schematic diagram of a hardware structure of an electronic device 100 provided in an embodiment of the present application;

FIG. 4 is a schematic diagram of a software structure of an electronic device 100 provided in an embodiment of the present application;

FIG. 5 is a schematic diagram of a process of invoking an input method provided by an embodiment of the present application;

FIG. 6 is a flow chart of an input method calling method provided by an embodiment of the present application;

FIG. 7 is a flow chart of another method for invoking an input method provided by the embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Among them, in the description of the embodiments of this application, unless otherwise specified, "/" means or means, for example, A/B can mean A or B; "and/or" in the text is only a description of associated objects The association relationship indicates that there may be three kinds of relationships, for example, A and/or B, which may indicate: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiment of the present application , "plurality" means two or more than two.

It should be understood that the terms "first" and "second" in the specification, claims and drawings of the present application are used to distinguish different objects, rather than to describe a specific order. Furthermore, the terms "include" and "have", as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but optionally also includes unlisted steps or units, or optionally further includes For other steps or units inherent in these processes, methods, products or apparatuses.

Reference in this application 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 present application. The occurrences of this 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 understood explicitly and implicitly by those skilled in the art that the embodiments described in this application can be combined with other embodiments.

When people use terminal devices such as mobile phones and tablet computers for work and entertainment, they often need to use input methods for input. For example, when a user utilizes social software in a mobile phone to chat with friends or colleagues, he can input text by calling an input method. For another example, a user may search by inputting text in a search box of a search engine.

There are various ways for users to make input. For example, the user can directly touch the screen of the terminal device with a finger to realize input, and also can realize input through some input devices. It can be understood that if the input methods adopted by the user are different, the applicable input modes may be different. That is, the specific input methods applicable to different input methods may be different. For example, finger touch input may be suitable for keyboard input mode, that is, Quanpin input method, Wubi input method and other input methods that need to use a keyboard, and stylus input may be suitable for handwriting input mode, that is, handwriting input method. However, no matter what input method the user adopts, the default input mode is first displayed on the input interface. It can be understood that the default input mode mentioned here may include the default input method set by the user and the input method used by the user when inputting last time. If the input mode needs to be switched due to the change of the input mode, the user generally needs to switch manually, which will affect the user experience.

The application provides an input method calling method and related equipment. According to the input method calling method, the electronic device can trigger input device monitoring when the input method application is started, and after the input method application receives the monitoring callback information, determine the input device type to be called according to the input device type included in the monitoring callback information Law. According to this method, the electronic device can adaptively provide a more reasonable input method according to the input method and the input device, without requiring the user to manually switch the input method, thereby improving user experience.

It can be understood that the invoked input method mentioned in this application refers to a specific input method. For example, handwriting input method, Quanpin input method, stroke input method, etc.

Firstly, a brief description of the input method invocation scenario provided by the embodiment of the present application will be given with reference to FIG. 1 .

Please refer to FIG. 1 . FIG. 1 is a schematic diagram of an input method calling scenario provided by an embodiment of the present application. As shown in FIG. 1 , the user may input in the electronic device 100 in various input ways. The multiple input methods may include but not limited to a finger touch input method and an input method using other external input devices for input. It can be understood that the external input device mentioned here refers to an input device independent of the electronic device 100 .

It can be understood that the finger touch input method mentioned in this application specifically means that the user implements input by touching the touch screen of the electronic device 100 with a finger. Similar to the way of finger touch input, the user can also make input by contacting other human skin with the touch screen of the electronic device 100 .

It can be understood that the input device is an external device independent of the electronic device 100 . Input devices may include, but are not limited to, keyboards, stylus, mice, and the like.

Specifically, in the case that the user performs input in the electronic device 100 by finger touch input, the finger touch operation acting on the input area of the electronic device 100 may trigger a finger touch event. After receiving the finger touch event, the electronic device 100 may determine the input method adopted when inputting in the input area. When a user uses an input device to perform input in the electronic device 100 , the user's operation acting on the input area of the electronic device 100 may trigger an input event. After receiving the input event, the electronic device 100 may determine the type of the input event and the type of the corresponding input device, and based on the type of the input event and the type of the input device, determine the input method adopted when inputting in the input area.

Exemplarily, the user may touch the stylus to the touch screen of the electronic device 100, and the touch operation of the stylus acting on the input area of the electronic device 100 may trigger a touch event of the stylus. After receiving the stylus touch event, the electronic device 100 may determine to adopt a handwriting input method when performing input in the input area.

It should be noted that before using the input device to perform input, a communication connection may be established between the input device and the electronic device 100 . It can be 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. Wherein, the wireless communication method may include communication methods such as Bluetooth.

The following specifically introduces some input scenarios provided by the embodiments of the present application.

It can be understood that the terms "interface" and "user interface" in the specification, claims and drawings of this application are media interfaces for interaction and information exchange between application programs or operating systems and users. Transformation between forms and forms acceptable to users. The commonly used form of user interface is the graphical user interface (graphic user interface, GUI), which refers to the user interface related to computer operation displayed in a graphical way. It can be an icon, window, control and other interface elements displayed on the display screen of the electronic device, where the control can include icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, etc. visual interface elements.

1. Enter the input interface (Figure 2A)

Please refer to FIG. 2A . FIG. 2A is a schematic diagram of a user interface provided by an embodiment of the present application.

As shown in FIG. 2A, the user interface 210 displays a page on which application icons are placed. The page may include multiple application icons (eg, 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, a photo album application icon, a voice recorder application icon, etc.). A page indicator may also be displayed below the plurality of application icons to indicate the positional relationship between the currently displayed page and other pages. Below the page indicator are a number of tray icons (eg, dialer application icon, messaging application icon, browser application icon 212, camera application icon). Wherein, the browser application icon 212 is an icon of a browser application. A browser is an application program used to retrieve, display and deliver web information resources. Understandably, the tray icon remains displayed when the page is switched.

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

The electronic device 100 may detect a user operation on the browser application icon 212, and in response to the user operation, the electronic device 100 may display a user interface 220 (as shown in FIGS. 2B and 2C ). The user interface 220 is the main interface of the browser. This interface is also a browser search interface. That is to say, the user can perform input in the corresponding area of the interface to realize searching. Therefore, the user interface 220 can also be understood as an input interface. User interface 220 may include edit box 221 . The edit box 221 can be used for input to search through the browser.

It can be understood that user operations may include, but are not limited to, touch operations, key operations, gesture operations, and voice operations, which are not limited in this application.

2. Calling and switching input methods (Figure 2B ~ Figure 2H)

As shown in FIG. 2B , the user may click on an edit box 221 included in the user interface 220 . Correspondingly, the electronic device 100 may detect a finger touch operation acting on the edit box 221, thereby generating a finger touch event. It can be understood that the finger touch event can be collected by the input subsystem in the kernel layer of the electronic device 100 and transmitted to the device node. Further, the input reader can read the finger touch event, and then the input distributor reports the finger touch event to the input management service. The input management service may transmit the finger touch event to the window management service, and the window management service cooperates with the input management service to distribute the finger touch event to the browser application. This also means that the browser application has gained focus. Generally speaking, the browser application can know that the area that the user needs to input is the edit box 221, and determine that the edit box 221 is the position where the cursor is currently activated. In this case, the browser application can notify the input method management service that it has got the focus and request to bind the input method. The input method management service then notifies the input method application to call the input method, and displays the called input method on the interface where the browser application gets the focus.

On the other hand, after the input management service receives the finger touch event reported by the input distributor, it can determine that the input device is a touch screen according to the finger touch event, and can also determine that the user's trigger method 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 may determine that the input method to be invoked is the 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 focused interface in the application program is the user interface 220 . After the browser application requests the input method management service to bind the input method, it can also request to display the input method through the input method management service.

It can be understood that the input method application may request the input method management service to register the monitoring input device. The request of the input method application to the input method management service to register the monitoring input device may occur before or after the user clicks the edit box 221 included in the user interface 220 .

According to the above process, the electronic device 100 may display the user interface 230 shown in FIG. 2C in response to the user's finger touch operation on the edit box 221 . The user interface 230 includes an edit box 231 and an input area 232 . Compared with the edit box 221 included in the user interface 220, a cursor is displayed in the edit box 231, which indicates that the browser application has acquired the focus. The input area 232 displays a pinyin full-key soft keyboard for the user to input.

As shown in FIG. 2D , the user may use a stylus to click on an edit box 221 included in the user interface 220 . Correspondingly, the electronic device 100 may detect a stylus touch operation acting on the edit box 221, thereby generating a stylus touch event. For the transfer process of the stylus touch event, refer to the transfer process of the finger touch event described above. The difference from the transfer process of finger touch events is that after the input management service receives the stylus touch event reported by the input distributor, it can determine the input device as a touch screen according to the stylus touch event, and can also determine that the user’s trigger method is handwriting pen 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 may determine that the input method to be invoked is the handwriting input method according to the type of the input device.

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

It should be noted that after the browser application gets the focus, the input device used by the user for input may change.

In some embodiments of the present application, when the electronic device 100 displays the user interface 230 shown in FIG. 2C , the user may tap a keyboard (for example, tap the "shift" key on the keyboard, etc.), thereby triggering a keyboard event. For the transmission process of the keyboard event, refer to the transmission process of the finger touch event and the stylus touch event described above. Different from these two transfer processes, after receiving the keyboard event reported by the input distributor, the input management service can determine the input device as 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 can determine that the input method to be invoked is the pinyin input method (floating mode) according to the type of the input device.

It can be understood 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 floating toolbar 251 . When the user inputs through the keyboard, the edit box 231 can display the input content of the user.

It can be understood that the keyboard tapped by the user has established a communication connection (eg, Bluetooth connection, etc.) with the electronic device 100 .

It should also be noted that, when the input device used by the user changes, the electronic device 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 first uses a finger touch operation for input, and then uses a stylus for input. Correspondingly, the electronic device 100 may detect a stylus touch operation acting on the edit box 231, thereby generating a stylus touch event. For the transfer process of the stylus touch event, refer to the transfer process of the finger touch event described above. The difference from the transfer process of finger touch events is that after the input management service receives the stylus touch event reported by the input distributor, it can determine the input device as a touch screen according to the stylus touch event, and can also determine that the user’s trigger method is handwriting pen 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 may determine that the input method to be invoked is the handwriting input method according to the type of the input device, and switch from the originally invoked Pinyin input method to the handwriting input method.

It can be understood that, when the browser application has acquired the focus, the input operation performed by the user through the stylus can act on any position on the touch screen of the electronic device 100 (not necessarily on the edit box 231 ).

It can be understood that, in response to a stylus touch operation 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 can input on the handwriting input area 261 with a stylus, and correspondingly, the edit box 231 can display the input content of the user. In addition, the user can also determine input content, search content, size of the input area, and manually switch input methods through the input tool area 262 .

It should be noted that, for other applications including edit controls (for example, edit boxes, etc.), the above input method calling method can also be implemented. In addition, the above-mentioned input method calling and switching process is only an overview, and no explanation is given. For the specific description, please refer to the following.

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

The electronic device 100 may detect a user operation acting on the setting application icon 211, and in response to the user operation, the electronic device 100 may display the user interface 270 shown in FIG. 2I. User interface 270 may include controls 271 . The control 271 is used to open the input method setting interface.

The electronic device 100 may detect a user operation on the control 271, and in response to the user operation, the electronic device 100 may display the user interface 280 shown in FIG. 2J. The user interface 280 is an input method setting interface. The user interface 280 may include several input method setting items. As shown in FIG. 2J , user interface 280 may include

controls

281 , 282 , and 283 . Wherein, the 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 use the control 281 to set the input method application to be started by default when inputting. Control 282 is used to set the safe input mode. In the secure input mode, when the user enters the password, the secure input keyboard needs to be activated. The control 283 is used to open the smart call input method interface. It can be understood that calling an input method intelligently refers to calling a specific input method according to the type of the input device.

The electronic device 100 may detect a user operation on the control 283, and in response to the user operation, the electronic device 100 may display a user interface 290 as shown in FIG. 2K. The user interface 290 is a smart call input method interface. The smart call input method interface may include several smart call input method setting items. As shown in FIG. 2K , user interface 290 may include controls 291 and display area 292 . Wherein, the control 291 is used to enable the smart call input method. The display area 292 is an area for setting correspondence between input device types and input methods. The display area 292 may include controls 2921 and a personalized setting area 2922 . The control 2921 is used to set the corresponding relationship between the input device type and the input method as the default corresponding relationship. It can be understood that the default correspondence is a correspondence preset by a technician. The personalization setting area 2922 is used to personalize the corresponding relationship between input device types and input methods according to user requirements. The personalized setting area 2922 may include a display area 29221 and controls 29222 . Display area 29221 may include several controls. These controls can be used to manage the corresponding relationship between the input device type and the input method set by the user. As shown in FIG. 2K , the display area 29221 may include controls for managing the input methods corresponding to the three input devices: touch screen-finger, touch screen-stylus and keyboard. According to the display area 29221 shown in Figure 2K, the input method corresponding to the touch screen-finger is the pinyin input method (full spell soft keyboard), the input method corresponding to the touch screen-stylus is the handwriting input method, and the input method corresponding to the keyboard is the pinyin input method (floating mode). Control 29222 is used to add a new corresponding relationship between input device type and input method.

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

The devices involved in the embodiments of the present application are introduced below.

FIG. 3 is a schematic diagram of a hardware structure of an electronic device 100 provided in an embodiment of the present application.

The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (Universal Serial Bus, USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, and an antenna 2 , mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, earphone jack 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and Subscriber Identification Module (Subscriber Identification Module, SIM) card interface 195 and so on. 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, bone conduction sensor 180M, etc.

It can be understood that, the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the electronic device 100 . In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown in the figure, or combine certain components, or separate certain components, or arrange different components. The illustrated components can be realized in hardware, software or a combination of software and hardware.

Processor 110 may include one or more processing units. Wherein, different processing units may be independent devices, or may be integrated in one or more processors.

A memory may also be provided in the 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 calling method mentioned in this solution.

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

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

The wireless communication function of the electronic device 100 can be realized 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.

Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 may be used to cover single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization of the antennas.

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

The wireless communication module 160 can provide wireless local area network (Wireless Local Area Networks, WLAN) (such as wireless fidelity (Wireless Fidelity, Wi-Fi) network), bluetooth (Bluetooth, BT), global navigation satellite System (Global Navigation Satellite System, GNSS), frequency modulation (Frequency Modulation, FM), near field communication technology (Near Field Communication, NFC), infrared technology (Infrared, IR) and other wireless communication solutions. 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 , frequency-modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 . The wireless communication module 160 can also receive the signal to be sent from the processor 110 , frequency-modulate it, amplify it, and convert it into electromagnetic waves through the antenna 2 for radiation.

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

The electronic device 100 realizes the display function through 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 the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

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

The electronic device 100 may realize the acquisition function through an ISP, a camera 193 , a video codec, a GPU, a display screen 194 , and an application processor.

The ISP is used for processing the data fed back by the camera 193 . For example, when taking a picture, open the shutter, the light is transmitted to the photosensitive element of the camera through the lens, the light signal is converted into an electrical signal, and the photosensitive element of the camera transmits the electrical signal to the ISP for processing, and converts it into an image or video visible to the naked eye. ISP can also perform algorithm optimization on image noise, brightness, and skin color. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, the ISP may be located in the camera 193 .

Camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects it to the photosensitive element. The photosensitive element can be a charge coupled device (Charge Coupled Device, CCD) or a complementary metal oxide semiconductor (Complementary Metal-Oxide-Semiconductor, CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, and then transmits the electrical signal to the ISP for conversion into a digital image or video signal. ISP outputs digital image or video signal to DSP for processing. DSP converts digital images or video signals into standard RGB, YUV and other formats of images or video signals.

Digital signal processors are used to process digital signals. In addition to digital image or video signals, they can also process other digital signals.

Video codecs are used to compress or decompress digital video.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, so as to expand the storage capacity of the electronic device 100.

The internal memory 121 may be used to store computer-executable program codes including instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by executing instructions stored in the internal memory 121 . The internal memory 121 may include an area for storing programs and an area for storing data.

The electronic device 100 can implement audio functions through the audio module 170 , the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor. Such as music playback, recording, etc.

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

Speaker 170A, also referred to as a "horn", is used to convert audio electrical signals into sound signals.

Receiver 170B, also called "earpiece", is used to convert audio electrical signals into sound signals.

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

The earphone interface 170D is used for connecting wired earphones.

The sensor module 180 may include one or more sensors, which may be of the same type or of different types. It can be understood that the sensor module 180 shown in FIG. 1 is only an exemplary division manner, and there may be other division manners, which are not limited in the present application.

The pressure sensor 180A is used to sense the pressure signal and convert the pressure signal into an electrical signal. In some embodiments, pressure sensor 180A may be disposed on display screen 194 . When a touch operation acts on the display screen 194, the electronic device 100 detects the intensity of the touch operation according to the pressure sensor 180A. The electronic device 100 may also calculate the touched position according to the detection signal of the pressure sensor 180A. In some embodiments, touch operations acting on the same touch position but with different touch operation intensities may correspond to different operation instructions.

The gyro sensor 180B can be used to determine the motion posture 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 use the magnetic sensor 180D to detect the opening and closing of the flip leather case.

The acceleration sensor 180E can detect the acceleration of the electronic device 100 in various directions (generally three axes). The magnitude and direction of gravity can be detected when the electronic device 100 is stationary. It can also be used to identify the posture of the electronic device 100, and can be applied to applications such as horizontal and vertical screen switching, pedometers, etc.

The distance sensor 180F is used to measure the distance. The electronic device 100 may measure the distance by infrared or laser. In some embodiments, when shooting a scene, the electronic device 100 may use the distance sensor 180F for distance measurement to achieve fast focusing.

Proximity light sensor 180G may include, for example, light emitting diodes (LEDs) and light detectors, such as photodiodes.

The ambient light sensor 180L is used for sensing ambient light brightness.

The fingerprint sensor 180H is used to acquire fingerprints.

The temperature sensor 180J is used to detect temperature.

Touch sensor 180K, also known as "touch panel". The touch sensor 180K is used to detect a touch operation on or near it. The touch sensor 180K may transmit the detected touch operation to the application processor to determine the touch event type. The touch sensor 180K can also provide visual output related to the touch operation through the display screen 194 . In other embodiments, the touch sensor 180K may also be disposed on the surface of the electronic device 100 , which is different from the position of the display screen 194 .

It can be understood that the touch sensor 180K can 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.

It should be noted that the touch screen of the electronic device 100 mentioned in this application is the touch sensor 180K.

The bone conduction sensor 180M can acquire vibration signals.

The keys 190 include a power key, a volume key and the like. The key 190 may be a mechanical key. It can also be a touch button. The electronic device 100 may receive key input and generate key signal input related to user settings and function control of the electronic device 100 .

The motor 191 can generate a vibrating reminder. The motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback.

The indicator 192 can be an indicator light, and can be used to indicate charging status, power change, and can also be used to indicate messages, missed calls, notifications, and the like.

The SIM card interface 195 is used for connecting a SIM card.

FIG. 4 is a schematic diagram of a software structure of an electronic device 100 provided in an embodiment of the present application.

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 can include a series of system applications and third-party applications. It can be understood that the system application mentioned here refers to the application provided with the Android platform, and the third party refers to the application selected by the user to install. The electronic device 100 may include an input method application and a first application. An input method application is an application that provides input method services. The first application is an application that obtains focus when the user performs input.

It can be understood that the focus refers to the area that the electronic device 100 focuses on, and can be understood as the position where the cursor is currently activated. Generally speaking, whether certain areas on the interface displayed by the electronic device 100 function and respond depends on whether focus is acquired. For example, the interface displayed by the electronic device 100 includes a text box. Once the text box gets focus, the characters typed by the user on the keyboard can be input into the text box.

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

It should be noted that 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 this application may be an input method application provided by the Android platform, or may be an application downloaded and installed subsequently by the user.

The application framework layer provides application programming interfaces and programming frameworks for applications in the application layer. The application framework layer includes some pre-defined functions.

As shown in FIG. 4 , the application framework layer may include but not limited to input management service, input method management service, window management service, Bluetooth service and so on.

Among them, the main function of the input management service is to monitor the input device, and timely transmit the input events generated by the input device (for example, click on the screen, button, slide, etc.) to the operating system or application program, and then the operating system or application program Treat accordingly. For example, the user touches a control in an activity in an application. The input management service can convert the user's touch into a touch event, and deliver it to the application program, and then the application program will process it accordingly.

It should be noted that, in fact, the input management service involves not only the application framework layer, but also the Native layer. The Native layer is at a lower level than the application framework layer. The application framework layer generally includes some system services, while the Native layer generally includes some local services and some link libraries. For example, if you need to perform complex operations, if you implement it through the application framework layer, the efficiency may be very low, but if you choose to implement it through the Native layer, and then communicate with the application framework layer (that is, the JNI mechanism in Android), then Efficiency will be greatly improved. For another example, when the electronic device 100 is running, it needs to interact with the underlying hardware driver, and this process also passes through the Native layer.

It can be understood that the input management service involves the application framework layer, the JNI layer and the Native layer. The main job of the input management service in the application framework layer is to provide implementation methods for Reader Policy and Dispatcher Policy, and to cooperate with other system services (for example, window management services, etc.). The local input manager (NativeInputManager) is located in the JNI layer and is responsible for the mutual communication between the components of the Native layer and the input management service of the application framework layer. At the same time, it provides input readers (Input Reader) and input distributors (Input Dispatcher). The interface of the policy request, the policy request is forwarded to the input management service of the application framework layer, and the input management service performs subsequent processing. Input Manager (Input Manager) is the running container of Input Reader and Input Dispatcher. It creates two threads to host the operation of Input Reader and Input Dispatcher respectively. Input Manager can include Input Reader, Input Dispatcher and EventHub. The main function of Input Reader is to read events. The main function of Input Dispatcher is to distribute events. The main function of EventHub is to use Linux's inotify and epoll mechanisms to monitor device events. The device events mentioned here include device plugging and unplugging as well as various touch and button events, etc. EventHub is mainly for device nodes in the /dev/input directory. For the input event on the device node, it can be monitored and obtained through getEvents of EventHub.

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

The Bluetooth service is used to provide a wireless communication function between the electronic device 100 and related peripherals. The relevant peripherals mentioned here may include wireless earphones, tablet computers, notebook computers, and the like. In some embodiments of the present application, the Bluetooth service can 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 with the corresponding client to realize functions such as creating, destroying, drawing, and laying out windows. Among them, the client is responsible for interacting with the window management service, and providing window management interfaces for applications and other services, including providing interface functions such as adding, removing and updating window views.

The system library and the Android runtime include the functions that the FWK needs to call, the Android core library, and the Android virtual machine. A system library can include multiple function modules. For example: browser kernel, three-dimensional (3dimensional, 3D) graphics, font library, etc.

The hardware abstraction layer is an abstract interface driven by the device kernel, which is used to provide an application programming interface for accessing the underlying device to a higher-level Java API framework. HAL contains multiple library modules such as audio, bluetooth, camera, sensor, etc. Each of these library modules 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 will load the library module for the hardware component.

The kernel layer is the foundation of the Android operating system, and the final functions of the Android operating system are all completed through the kernel layer. The kernel layer can include camera driver, audio driver, Bluetooth driver, sensor driver, display driver, touch screen driver and button driver, etc. For example, the interface language between the kernel layer and the hardware abstraction layer is a hardware abstraction layer interface description language (HAL interface definition language, HIDL).

It should be noted that the schematic diagram of the software framework of the electronic device 100 shown in FIG. 4 provided in the embodiment of the present application is only used as an example, and does not limit the specific module division in different layers of the Android operating system. For details, refer to An introduction to the software architecture of the Android operating system. 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 method for invoking an input method provided in the embodiment of the present application can also be implemented based on other operating systems, and this application does not give examples one by one.

The input method calling method provided by the embodiment of the present application is introduced below.

Please refer to FIG. 5 . FIG. 5 is a schematic diagram of a process of invoking and switching an input method provided by an embodiment of the present application.

As shown in Figure 5, the user can use the input device to input, thereby generating an input event, and the original information related to the input event can be collected by the kernel layer and transmitted to the device node in the kernel layer. Additionally, the kernel layer may include device drivers. It can be understood that a device node corresponds to an input device. Device drivers also correspond to input devices.

Next, the input event can be delivered to the input management service in the application framework layer through the kernel layer. In this process, the input event can be read by the input reader, and then reported to the input management service through the input distributor, and then passed to the window management service. The window management service, as a window manager, may cooperate with the input management service to distribute the input event to the window including the edit control in the first application for processing. According to the above, the first application is an application that acquires focus. That is to say, the user's input operation is aimed at the edit control in the first application. It can be understood that the first application may request the input method management service to invoke the input method. The input method management service then notifies the input method application to invoke the input method according to the request of the first application to invoke the input method.

On the other hand, the input method application can request the input method management service to register the monitoring input device. The input method management service may send the registration monitoring request to the input management service. After receiving the registration monitoring request, the input management service may determine the type of the input device according to the type of the received input event.

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 monitoring request. In this case, the input management service can send the input device type to the input method management service. The input method management service then sends the monitoring receipt information to the input method application. It can be understood that the monitoring receipt information may include the input device type. After the input method application receives the monitoring receipt information, it can determine the input method to be called according to the input device type included in the information, and call the input method. Correspondingly, the first application can display an interface including an input area. It can be understood that the input area may display the called input method.

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

It can be understood that the historical input device type is the type of the input device corresponding to the last input event generated by the electronic device 100 . It is worth noting 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 explained here.

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

Please refer to FIG. 6. FIG. 6 is a flowchart of an input method invocation method provided by an embodiment of the present application. The input method invocation method can be applied to applications including input method applications, input method management services, input distributors, and input management services. Electronic device 100. For example, the electronic device 100 shown in FIG. 3 and FIG. 4 . The input method calling method may include but not limited to the following steps:

S601: The input method application sends a registration monitoring request to the input method management service. Wherein, the registration monitoring request is used to monitor the input device (the registration monitoring request is a request for monitoring the input device).

It can be understood that the input method application in the electronic device 100 may send a registration monitoring request to the input method management service. The registration monitoring request is used to monitor the input device. That is, the electronic device 100 can determine the input device type through the registration monitoring request.

In some embodiments of the present application, the input method application may send a registration monitoring request to the input method management service through a custom interface. It can be understood that the custom interface is an interface for implementing monitoring of an input device. Exemplarily, the custom interface may be: InputMethodManager#registerInputDeviceChange.

It should be noted that, before step S601 is performed, the electronic device 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 device 100 initially requests to invoke the input method, and in this case, the electronic device 100 may initialize the input method application. It can be understood that the user operations mentioned here are operations performed on the input area of the electronic device 100 . For example, click on the edit box. In addition, the initial request of the electronic device 100 to call the input method refers to the first request to bind 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 started for the first time, the electronic device 100 may perform initialization processing on the input method application. It can be understood that the initial startup of the input method application refers to the first startup of the input method application after the electronic device 100 is turned on. It should be noted that the input method application can be started in the background, in this case, the corresponding page will not be displayed on the electronic device 100 . Exemplarily, after the electronic device 100 is successfully powered on, the input method application can be started in the background, and the electronic device 100 can initialize the input method application.

It can be understood that after the input method application sends a registration monitoring request to the input method management service, the input method management service can receive the registration monitoring request accordingly.

In some embodiments of the present application, the 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 to say, the registration monitoring 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. Wherein, the first message is used to prompt the input management service to determine the input device type corresponding to the input event, and return the input device type to the input method management service.

After receiving the registration monitoring request sent by the input method application, the input method management service may send a first message to the input method management service. The first message is used to prompt the input management service to determine the input device type corresponding to the input event, and return the input device type to the input method management service.

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

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

Specifically, after receiving the registration monitoring request, the input method management service may send a registration monitoring receipt to the input method application. It can be understood that the registration monitoring receipt can be used to indicate that the input method management service has successfully received the registration monitoring request sent by the input method application.

It can be understood that after the input method management service sends the registration monitoring receipt to the input method application, the input method application can correspondingly receive the registration monitoring receipt.

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

Specifically, the user may use the input device to perform input on the electronic device 100, thereby generating various types of input events. For example, key events, touch events, mouse events, etc. The original information generated by these input events can be collected by the input subsystem in the kernel layer, uploaded to the input manager, and then sent to the input management service by the input distributor in the input manager. It can be understood that there is a communication connection between the input device and the electronic device 100 . The communication connection 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 can be understood that after the input distributor sends the input event to the input management service, the input management service can receive the input event accordingly.

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

In some embodiments of the present application, the input operation performed by the user may include but not limited to tapping a key on a keyboard, touching a touch screen of the electronic device 100 with 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 can be understood that the focus acquisition operation mentioned here may be a trigger operation performed on the input area displayed on the electronic device 100 . Wherein, the input area may include an edit box, a handwriting area, and the like. Exemplarily, the focus acquisition operation may be a click operation on an edit box displayed on the electronic device 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, typing on the keyboard. For another example, use a stylus to write in the input area, thereby realizing input.

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

Specifically, after receiving the input event sent by the input distributor, the input management service may determine the source of the input event, that is, determine the type of the input device that triggered the input event.

It should be noted that the input management service may determine the type of the input device that triggers the input event in various ways.

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

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

Table 1

输入事件类型input event type	输入设备类型input device type
手指触控事件finger touch event	触摸屏-手指touch screen - finger
手写笔触控事件Stylus touch events	触摸屏-手写笔touch screen - stylus
键盘事件keyboard events	键盘keyboard
……	……

According to Table 1, when the input event type is a finger touch event, the corresponding input device type is touch screen-finger. When the input event type is a stylus touch event, the corresponding input device is a touch screen-stylus. When the input event type is a keyboard event, the corresponding input device is a keyboard. It can be understood that Table 1 is only an example provided by the embodiment of the present application, and should not be regarded as a limitation of the present application.

It should also be noted that, in an actual input process, for the same input device, input events generated by the electronic device 100 may be different due to different triggering methods by the user. In this case, the input device types corresponding to these input events can be distinguished according to the user's triggering manner. As shown in Table 1, the finger touch event and the stylus touch event, these two types of input events are essentially touch events, that is, input events triggered through the touch screen. That is to say, the input device type corresponding to these two types of input events is a touch screen. However, due to the different triggering methods of users, the final generated input events are different. Specifically, the user touches the touch screen with a finger, and the electronic device 100 may generate a finger touch event. While the user touches the touch screen with a stylus, the electronic device 100 may generate a stylus touch event. For these two types of input events, the corresponding input device types can be distinguished according to the user's trigger mode. As shown in Table 1, the input device type corresponding to the finger touch event may be touch screen-finger, and the input device type corresponding to the stylus touch event may be touch screen-stylus.

That is to say, the embodiment of the present application can divide the input event type and the input device type in more detail to prepare for subsequent input method calling or switching, fully considering the user's input requirements.

It can be understood that, when the input device is available, the Linux kernel of the electronic device 100 will create a corresponding device node in the user space (User space). After the input event is generated, the original information related to the input event can be collected by the input subsystem in the kernel layer. Specifically, the original information can be transmitted from the driver layer of the kernel space (Kernel space) in the kernel layer to the device node in the user space. It can be understood that the driver layer in the kernel space may include device drivers. For example, touch screen driver, keyboard driver and mouse driver etc. It can be understood that there is a corresponding relationship between the device driver and the input device.

It can be understood that the kernel space is the running space of the Linux kernel, which can execute arbitrary commands and invoke all resources of the system. The user space is the running space of the user program. It can only perform simple calculations and cannot directly call system resources. It must send instructions to the kernel through the system interface.

In some embodiments of the present application, the input management service can monitor all device nodes in the user space, process the data when the device node has data, find a suitable window, and dispatch input events to it. It can be understood that the input management service may determine the device node corresponding to the received input event. According to the above, there is a corresponding relationship between the device node and the input device. The input management service can determine the input device type according to the device node corresponding to the input event.

In some embodiments of the present application, the input management service may search the transmission route of the input event, and determine the 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, and the input device information may be used to represent the input device.

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

S606: In the case that the input device type is different from the historical input device type or there is no historical input device type, the input management service sends the input device type to the input method management service. Wherein, the historical input device type is the type of the input device corresponding to the last input event generated by the electronic device 100 .

Specifically, after the input management service determines the input device type that triggers the input event, if the input device type is different from the historical input device type or there is no historical input device type, the input management service can send the input device type to the input method management Serve. It can be understood that the historical input device type is the type of the input device corresponding to the last input event generated by the electronic device 100 . The input device type mentioned in this application is different from the historical input device type because the input device used by the user when inputting this time is different from the input device used when inputting last time. The case where there is no historical input type mentioned in this application is that the input management service receives the input event triggered by the user's input using the 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 that triggers the input event, it may convert the input device type into a form that meets the interface specification, and then send the input device type that meets the interface specification. Provide input method management services. It can be understood that there is a corresponding relationship between different forms of input device types. The corresponding relationship can be stored in the input management service, and can also be stored in other areas. The input management service may invoke this 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 that meet the interface specifications and their meanings and code values provided by the embodiment of the present application.

Table 2

输入设备类型input device type	含义meaning	码值code value
STYLUSSTYLUS	手写笔stylus	0x000050020x00005002
FINGERFINGER	手指finger	0x000020020x00002002
KEYBOARDKEYBOARD	键盘keyboard	0x000001010x00000101
……	……	……

It can be understood that the meanings in Table 2 correspond to the types of input devices that trigger input events determined by the input management service. After the input management service determines the type of input device that triggers the input event, it looks up the meaning of the same content in Table 2, so as to determine the type of input device that meets the interface specification and its corresponding code value. Exemplarily, according to Table 2, after the input management service determines that the type of input device that triggers the input event is a touch screen-stylus, the input management service can search for the input device type corresponding to the stylus——STYLUS. It can be understood that the representation of STYLUS means that the input device type is a stylus, and the STYLUS satisfies the form of the interface specification. Correspondingly, the input management service can determine that the code value corresponding to STYLUS is 0x00005002.

It can be understood that after the input management service sends the input device type to the input method management service, the input method management service can receive the input device type accordingly. It can be understood that the input device type can meet 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 monitoring callback information to the input method application. The listener callback information includes the input device type.

Specifically, if the input device type is different from the historical input device type or there is no historical input device type, the input management service sends the input device type to the input method management service. After the input method management service receives the input device type, it can send the input method application Listen for callback information. It can be understood that the monitoring callback information may include the type of the input device.

In some embodiments of the present application, the input method management service may send monitoring callback information to the input method application through a custom interface. It can be understood that the custom interface is an interface for realizing the monitoring callback. Exemplarily, the custom interface may be: InputMethodManager#InputDeviceListerner.deviceChange. It can be understood that the parameter corresponding to the custom interface is an input device type meeting the interface specification. Exemplarily, 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: The input method application determines the input method and calls the input method for input according to the monitoring callback information and the input method calling rule.

Specifically, the input method application determines the input method for input according to the input device type and input method invocation rules included in the monitoring callback information, and invokes the input method for input. It can be understood that the input method calling rule refers to the corresponding relationship between the input device type and the input method. The input method application can determine the finally invoked input method according to the corresponding relationship and the type of the input device.

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

As shown in Table 3, Table 3 is an exemplary input method calling rule provided by the embodiment of the present application.

table 3

输入设备类型input device type	输入法Input
STYLUSSTYLUS	手写输入法handwriting input method
FINGERFINGER	拼音输入法(软键盘)Pinyin input method (soft keyboard)
KEYBOARDKEYBOARD	拼音输入法(悬浮模式)Pinyin input method (floating mode)
……	……

According to Table 3, if the input device type included in the monitoring callback information received by the input method application is STYLUS, the input method application determines to call the handwriting input method for input. Similarly, if the input device type included in the monitoring callback information received by the input method application is FINGER, the input method application determines to call the Pinyin input method (soft keyboard) for input. If the input device type included in the monitoring callback information received by the input method application is KEYBOARD, the input method application determines to call the Pinyin input method (floating mode) for input.

It should be noted that the input method corresponding to the input device type can be preset by a technician, or can be set by a user, which is not limited in this application. It can be understood that the correspondence between input device types and input methods shown in Table 3 is only an example provided by the present application, and the correspondence may also exist in other forms, which is not limited by the present application. For example, when the input device type is FINGER, the corresponding input method may be Wubi input method or stroke input method.

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

Exemplarily, as shown in Table 3, when the input device type is FINGER, the input method application may determine to call the 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. keyboard. Understandably, the form of the soft keyboard may be a pinyin full-key soft keyboard (26 keys), or a pinyin nine-key soft keyboard (9 keys). The specific form of the soft keyboard can be preset by a technician as a default form, or can be set by a user, which is not limited in this application.

Exemplarily, as shown in Table 3, when the input device type is KEYBOARD, the input method application may determine to call the Pinyin input method (floating mode) for input, and the input area in the input interface displayed by the electronic device 100 may include Pinyin input Method floating toolbar. It can be understood that the pinyin input method floating toolbar can 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 can have various forms, and the content of the input area in the input interface can be preset by a technician, or can be set by the user. set up. For example, when the input device type is FINGER, 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, when 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 a floating toolbar of a pinyin input method.

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 will not send a registration monitoring request to the input method management service. This is because the input method has already sent a registration monitoring request to the input method management service when the user made an input before, so when the user inputs again later, the input method application does not need to send a registration monitoring request to the input method management service. In this case, the electronic device 100 may not perform step S601-step 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 switch manually, which improves the user experience.

Please refer to Fig. 7, Fig. 7 is a flow chart of another input method calling method provided by the embodiment of the present application, the input method calling method may include but not limited to the following steps:

S701: At a first moment, in response to a first operation, the electronic device 100 generates a first input event. Wherein, the first input event is an input event generated for the first input device.

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

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

It can be understood that the first input event may include but not limited to a keyboard event, a stylus touch event, a finger touch event, and the like. Wherein, the keyboard event is an input event triggered by the user pressing a key on the keyboard. The stylus touch event is an input event triggered by the user touching the touch screen of the electronic device 100 with a stylus. The finger touch event is an input event triggered by the user touching the touch screen of the electronic device 100 with a finger. It can be understood that, similar to a finger touch event, an 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 performed by using a first input device. It can be understood that the input operation mentioned here may include but not limited to tapping a key on a keyboard, touching a touch screen of the electronic device 100 with 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 can be understood that the focus acquisition operation mentioned here may be a trigger operation performed on the input area displayed on the electronic device 100 . Wherein, the input area may include an edit box, a handwriting area, and the like. Exemplarily, the focus acquisition operation may be a click operation on an edit box displayed on the electronic device 100 .

It should be noted that, before step S701 is performed, the electronic device 100 may register a monitoring input device, and for details, refer to step S601 , which will not be described in detail here.

In addition, before the electronic device 100 registers to listen to the input device, the input method application in the electronic device 100 may be initialized. For details, please refer to step S601, which will not be described in detail here.

S702: The electronic device 100 invokes a first input method based on a 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 the source of the first input event, that is, determine the first input device corresponding to the first input event, and call the first input device according to the device type of the first input device. an input method, and then display the first interface. It can be understood that the first interface may include a first input method display area. The first input method display area can be used to display the first input method.

It should be noted that, the specific manner of invoking the first input method based on the first input event by the electronic device 100 may refer to the above, and will not be repeated here.

It can be understood that the first input method is an input method specifically invoked by the electronic device 100 . For example, Quanpin input method, Wubi input method, stroke input method, handwriting input method, etc.

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

S703: At a second moment, 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 correspondingly, at a second moment, the electronic device 100 may generate a second input event in response to the second operation. It can be understood that the second input event is an input event generated for the second input device.

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

It can be understood that the second input event may include but not limited to a keyboard event, a stylus touch event, a finger touch event, and the like. Wherein, the description about the keyboard event, the stylus touch event and the finger touch event can refer to step S701 , which will not be repeated here.

In some embodiments of the present application, the second operation performed by the user is an input operation performed by using a second input device. It can be understood that the input operation mentioned here may include but not limited to tapping a key on a keyboard, touching a touch screen of the electronic device 100 with a stylus or a finger, and the like.

In some embodiments of the present application, the second operation performed by the user is a focus acquisition operation, and may also be an input operation after the focus is acquired. For details, refer to step S701 , which will not be repeated here.

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

S704: The electronic device 100 invokes the second input method based on the second input event, and displays the second interface.

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

It should be noted that, the specific manner of invoking the second input method based on the second input event by the electronic device 100 can refer to the above, and will not be repeated here.

It can be understood that the second input method is an input method specifically invoked by the electronic device 100 . For example, Quanpin input method, Wubi input method, stroke input method, handwriting input method, etc.

In some embodiments of the present application, the first input method and the second input method are different input methods. Exemplarily, the first input method is Quanpin input method, and the second input method is handwriting input method. In some other embodiments of the present application, the first input method and the second input method may be the same input method.

Exemplarily, when the first input device is a touch screen and the first operation is a finger touch operation, the first input method is the Quanpin input method, and the first input method display area on the first interface displays the QuanPin soft keyboard . When the second input device is a keyboard and the second operation is a keystroke operation, the second input method is Quanpin input method, and the second input method display area on the second interface displays an input method floating tool.

It should be noted that the first interface and the second interface are different interfaces. The first interface displays the first input method, and the second interface displays the 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, rather than to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: it can still apply to the foregoing embodiments Modifications are made to the recorded technical solutions, or equivalent replacements are made to some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of each embodiment of the application.

Claims

An input method calling method, characterized in that the method is applied to electronic equipment; the method includes:

Receiving a first operation, and displaying a first interface in response to the first operation; the first operation is an input operation performed through a first input method; the first interface displays a first input method; the first The input method is an input method corresponding to the first input method;

Receiving a second operation, and displaying a second interface in response to the second operation; the second operation is an input operation performed through a second input method; the second interface displays a second input method; the second The input method is an input method corresponding to the second input method;

Wherein, the first input method is different from the second input method.
The method according to claim 1, wherein the first input mode is an input mode using a first input device; the second input mode is an input mode using a second input device;

The first input method is an input method corresponding to the first input method, specifically including: the first input method is an input method corresponding to the first device type; the first device type is the first Enter the device type corresponding to the device;

The second input method is an input method corresponding to the second input method, specifically including: the second input method is an input method corresponding to the second device type; the second device type is the second Enter the device type for the device.
The method according to claim 1 or 2, wherein, before displaying the first interface in response to the first operation, the method further comprises:

The input method application in the electronic device sends a registration monitoring request to the input method management service in the electronic device based on the first interface; the registration monitoring request is used to request the input method management service to monitor the input device;

Sending a first message to the 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 monitor the input device.
The method according to 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;

The displaying the second interface in response to the second operation specifically includes:

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;

calling the second input method based on the second input event, and displaying the second interface.
The method according to claim 4, wherein calling the first input method based on the first input event specifically comprises:

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

Using the input management service to compare the first device type with a first historical device type; the first historical device type is the input device corresponding to the last input event of the first input event generated by the electronic device type of equipment;

If the first device type is different from the first historical device type or the first historical device type does not exist, the input method management service sends monitoring callback information to the input method application based on the second interface; The monitoring callback information includes the first device type;

According to the first device type in the monitoring callback information, the input method application searches for the first input method in the input method calling rule, and calls the first input method; the input method calling rule Including the corresponding relationship between the device type corresponding to the input device and the input method.
The method according to claim 4 or 5, wherein calling the second input method based on the second input event specifically comprises:

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

Compare the second device type with the second historical device type through the input management service; the second historical device type is corresponding to the last input event of the second input event generated by the electronic device the device type of the input device;

If the second device type is different from the second historical device type or the second historical device type does not exist, send monitoring callback information to the input method application based on the second interface through the input method management service; The monitoring callback information includes the second device type;

The input method application searches for the second input method in the input method calling rule according to the second device type in the monitoring callback information, and calls the second input method.
The method according to claim 6, wherein the 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 input event Equipment type.
The method according to any one of claims 1-7, wherein the first interface and the second interface are user interfaces of a first application; and the first application is an application in the electronic device ; The first operation is used to prompt the first application to acquire focus.
The method according to claim 8, wherein the second operation is used to prompt the first application to acquire focus.
The method according to any one 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 is an application in the electronic device; the first operation is used to prompt the first application to obtain focus; the second operation is used to prompt the second application to obtain focus.
An input method calling method, characterized in that the method is applied to electronic equipment; the method includes:

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

Determine the target device type based on the target input event through the input management service, and report the target device type to the input method management service; the target device type is the device type of the input device;

Comparing the target device type with a historical device type through the input management service; 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;

If the target device type is different from the historical device type or the historical device type does not exist, send monitoring callback information to the input method application in the electronic device through the input method management service; the monitoring callback information includes the target device type;

According to the target device type in the monitoring callback information, the input method application searches for the target input method in the input method call rule; the input method call rule includes the device type corresponding to the input device and the input method Correspondence between;

calling the target input method, and displaying an input interface; the input interface displays the target input method.
The method according to claim 11, wherein before 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 the first interface; the registration monitoring request is used to request the input method management service to monitor the input device;

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 monitor the input device.
The method according to claim 11 or 12, wherein the determining the target device type based on the target input event through the input management service includes:

If the target input event is a first input event, determining that the target device type is a first device type through the input management service;

In a case where the target input event is a second input event, determining that the target device type is a second device type through the input management service;

If the target input event is a third input event, determining that the target device type is a third device type through the input management service;

Wherein, 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.
An electronic device, comprising a display screen, a memory, and one or more processors, wherein the memory is used to store a computer program; the processor is used to call the computer program, so that the electronic device executes the claims The method described in any one of 1-10.
An electronic device, comprising a display screen, a memory, and one or more processors, wherein the memory is used to store a computer program; the processor is used to call the computer program, so that the electronic device executes the claims The method described in any one of 11-13.
A computer storage medium, characterized by comprising: computer instructions; when the computer instructions are run on an electronic device, the electronic device is made to execute the method described in any one of claims 1-10.
A computer storage medium, characterized by comprising: computer instructions; when the computer instructions are run on an electronic device, the electronic device is made to execute the method described in any one of claims 11-13.