An interactive business processing method, apparatus, and device

Abstract

This invention discloses an interactive service processing method, apparatus, and device applied to a user mobile terminal. The method includes: collecting acceleration change data of the user mobile terminal; determining, based on the acceleration change data, whether the user mobile terminal is touching another entity; if so, detecting near-field communication (NFC) related signals to enable NFC communication with the other entity; if the NFC related signals are not successfully detected, identifying the other entity using other data besides the NFC related signals; and determining the current user's intent based on the identification result, and displaying a service page matching the intent on the user mobile terminal.

Description

Technical Field

[0001] This specification relates to the field of near-field communication technology, and in particular to an interactive service processing method, apparatus, and device. Background Technology

[0002] With the development of internet technology and the widespread use of smartphones, more and more businesses can be conducted through corresponding applications on smartphones, bringing great convenience to people's lives.

[0003] In the payment and other business fields, QR codes have been widely used. However, in practice, for some users or in some scenarios, QR code payment requires relatively cumbersome operations. With the increase in mobile terminals with near-field communication (NFC) capabilities, especially smartphones, many smartphones now support NFC payment methods.

[0004] By touching a smartphone to a point-of-sale (POS) device that also supports near-field communication (NFC), NFC payments can be conveniently made. Similarly, there are many other NFC devices that can interact with smartphones via NFC to enable corresponding services. However, the differences between different NFC devices may affect the reliability of smartphone interactions, which in turn affects the reliability of the corresponding services.

[0005] Therefore, solutions are needed to improve smartphone interaction and business reliability in response to the above situations. Summary of the Invention

[0006] This specification provides one or more embodiments of an interactive service processing method, apparatus, device, and storage medium to solve the following technical problem: the need for a solution that helps improve the reliability of smartphone interaction and services.

[0007] To solve the above-mentioned technical problems, one or more embodiments of this specification are implemented as follows:

[0008] This specification provides an interactive service processing method according to one or more embodiments, applied to a user's mobile terminal, the method comprising:

[0009] Collect acceleration change data of the user's mobile terminal, and determine whether the user's mobile terminal is touching other entities based on the acceleration change data;

[0010] If so, detect near-field communication related signals in order to conduct near-field communication with the other entities;

[0011] If the near-field communication related signal is not successfully detected, the other entities are identified using other data besides the near-field communication related signal;

[0012] Based on the recognition result, the current user's intent is determined, and a service page matching the intent is invoked on the user's mobile terminal.

[0013] This specification provides an interactive service processing apparatus according to one or more embodiments, applied to a user mobile terminal, the apparatus comprising:

[0014] The acceleration touch detection module collects acceleration change data of the user's mobile terminal and determines whether the user's mobile terminal is touching other entities based on the acceleration change data.

[0015] If so, the near-field communication detection module detects near-field communication related signals in order to conduct near-field communication with the other entities.

[0016] If other entity recognition modules fail to detect the near-field communication related signals, they will identify the other entities using other data besides the near-field communication related signals.

[0017] The intent matching and invocation module determines the current user's intent based on the recognition result and invokes a service page that matches the intent on the user's mobile terminal.

[0018] This specification provides one or more embodiments of an interactive service processing device applied to a user mobile terminal, the device comprising:

[0019] At least one processor; and,

[0020] A memory communicatively connected to the at least one processor; wherein,

[0021] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform:

[0022] Collect acceleration change data of the user's mobile terminal, and determine whether the user's mobile terminal is touching other entities based on the acceleration change data;

[0023] If so, detect near-field communication related signals in order to conduct near-field communication with the other entities;

[0024] If the near-field communication related signal is not successfully detected, the other entities are identified using other data besides the near-field communication related signal;

[0025] Based on the recognition result, the current user's intent is determined, and a service page matching the intent is invoked on the user's mobile terminal.

[0026] This specification provides one or more embodiments of a non-volatile computer storage medium for use in a user mobile terminal. The medium stores computer-executable instructions, which are configured as follows:

[0027] Collect acceleration change data of the user's mobile terminal, and determine whether the user's mobile terminal is touching other entities based on the acceleration change data;

[0028] If so, detect near-field communication related signals in order to conduct near-field communication with the other entities;

[0029] If the near-field communication related signal is not successfully detected, the other entities are identified using other data besides the near-field communication related signal;

[0030] Based on the recognition result, the current user's intent is determined, and a service page matching the intent is invoked on the user's mobile terminal.

[0031] The above-mentioned at least one technical solution adopted in one or more embodiments of this specification can achieve the following beneficial effects: It actively uses acceleration change data of the user's mobile terminal (e.g., a smartphone) to immediately sense when the user's mobile terminal is touching other entities (e.g., a POS device supporting near-field communication), rather than relying on near-field communication coil induction. This helps to prepare for and actually enter the near-field communication interaction state in advance, shortening the reaction time window and facilitating more efficient and reliable interaction. It can more autonomously trigger the timely activation of the corresponding business page on the user's mobile terminal without completely relying on the other device for triggering. Even if the near-field communication interaction process is unreliable, business can still be conducted reliably to a certain extent based on such a business page. Furthermore, even if the other entity is not a near-field communication device and does not have a near-field communication coil, it can still automatically trigger the user's mobile terminal to identify the other entity through data other than near-field communication related signals, and infer the user's intention in this touch action. Then, it can activate a business page matching that intention on the user's mobile terminal, thereby enabling more flexible and reliable business triggering and improving the business compatibility and practicality of traditional near-field communication touch actions. Attached Figure Description

[0032] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0033] Figure 1 A flowchart illustrating an interactive business processing method provided in one or more embodiments of this specification;

[0034] Figure 2 A schematic diagram showing acceleration change data corresponding to various different touch events provided in one or more embodiments of this specification;

[0035] Figure 3 Provided for one or more embodiments of this specification Figure 1 A schematic diagram illustrating the implementation principle and effect of the scheme;

[0036] Figure 4 A flowchart illustrating an intent matching scheme based on feature-free fusion provided for one or more embodiments of this specification;

[0037] Figure 5 This is a flowchart illustrating a local business authorization scheme based on human touch, provided for one or more embodiments of this specification.

[0038] Figure 6 A schematic diagram of the structure of an interactive service processing device provided for one or more embodiments of this specification;

[0039] Figure 7 This is a schematic diagram of the structure of an interactive service processing device provided for one or more embodiments of this specification. Detailed Implementation

[0040] This specification provides an interactive service processing method, apparatus, device, and storage medium through its embodiments.

[0041] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this application.

[0042] Figure 1 This is a flowchart illustrating an interactive service processing method provided in one or more embodiments of this specification. This method can be applied to a user's mobile terminal, specifically executed at the software level by an application client installed on the user's mobile terminal. The user's mobile terminal can primarily be a smartphone, but can also be other terminals such as smartwatches, tablets, or portable game consoles. Preferably, the user's mobile terminal has near-field communication (NFC) functionality.

[0043] Figure 1The process includes the following steps:

[0044] S102: Collect acceleration change data of the user mobile terminal, and determine whether the user mobile terminal is touching other entities based on the acceleration change data.

[0045] In one or more embodiments of this specification, since the user's mobile terminal itself is also an entity, for ease of distinction, the object it touches is referred to as another entity. Other entities may be near-field communication devices, ordinary objects without near-field communication functions, or animals or people.

[0046] It should be emphasized that the advantages of the solution proposed in this application are particularly evident if the other entity is an entity other than the device with good near-field communication performance.

[0047] Accelerometers are deployed in user mobile terminals. The principle of accelerometers is based on the changes in acceleration of an object in space. Through built-in sensing devices and conversion devices, they can accurately sense the changes in acceleration of the mobile phone in multiple directions, such as forward and backward, left and right, and up and down.

[0048] Accelerometers can collect real-time acceleration data reflecting the user's mobile terminal's movement. Based on this, it can be determined whether the user's mobile terminal has already touched another object; or whether it is in the process of touching another object but has not yet touched it but is expected to touch it soon; thus achieving the judgment in step S102. For the latter case, i.e., expected to touch another object, this judgment can specifically be a prediction of the corresponding touch event.

[0049] Furthermore, it may be possible to identify the user's mobile terminal's orientation (e.g., whether it's vertical, horizontal, or diagonal; whether it's facing directly, sideways, or opposite) or its movement process (e.g., whether it moves in a straight line, an arc, or a zigzag, etc.). It may also be able to identify, to some extent, other entities that have been touched, including their type, such as their hardness, material type, etc.

[0050] Intuitively, Figure 2 This is a schematic diagram showing the acceleration change data corresponding to various different touch events provided in one or more embodiments of this specification.

[0051] exist Figure 2In this study, acceleration data along the x, y, and z axes were collected for five different touch events (touch 1, touch 2, touch 3, touch 4, and touch 5). These five touch events involved the same smartphone touching five different objects. The waveforms of the acceleration corresponding to each touch event, especially the peaks and troughs, are distinct. By pre-learning these feature differences and using waveform feature matching, similar touch events can be identified. Furthermore, to improve reliability or prevent false triggers, the sensitivity of the recognition can be adjusted based on actual performance.

[0052] In one or more embodiments of this specification, the touch operation in step S102 can be similar to the "tap" operation performed by the user during current near-field communication (NFC) interactions between devices. This application breaks through the limitations of NFC interaction devices, allowing users to "tap" more other entities with their mobile terminals and obtain more flexible and intelligent service feedback.

[0053] S104: If so, detect near-field communication related signals in order to conduct near-field communication with the other entities.

[0054] If other entities are near-field communication devices, they will likely detect near-field communication-related signals.

[0055] Near-field communication (NFC) related signals can be NFC induction signals, which are actively generated by the NFC coil of the NFC device through active power supply, or passively generated in response to the proximity of the user's mobile terminal. NFC related signals can also be other characteristic signals actively emitted by the NFC device through coils or other antennas, such as signals used to trigger the user's mobile terminal to adjust its operating mode (e.g., switch from low-power mode to normal-power mode).

[0056] If near-field communication signals are successfully detected, then normal near-field communication can be attempted with other entities that are near-field communication devices to perform related services.

[0057] It should be noted that near-field communication (NFC) related signals can also be detected more independently, without relying on the judgment result of step S102. For example, when NFC is enabled, the presence of NFC related signals in the surrounding area may be detected in a timely manner under a set power mode. Following this approach, for step S104, when the judgment result is "yes," NFC related signals may already be being detected.

[0058] In one or more embodiments of this specification, the near-field communication (NFC) function can be disabled by default for a user mobile terminal. If it is determined that the user mobile terminal is touching another entity, the NFC function is then activated to detect whether there is a signal emitted by the NFC coil. If no NFC-related signal is successfully detected, it can be determined that the other entity does not have a NFC coil, and the NFC function is automatically turned off accordingly. This avoids wasting power and processing resources and helps to focus more efficiently on other processing besides NFC.

[0059] S106: If the near-field communication related signal is not successfully detected, the other entity is identified by other data besides the near-field communication related signal.

[0060] If the near-field communication related signal is not successfully detected, it means that no near-field communication related signal is detected at all, or that the detected signal strength or stability is insufficient, or the type is mismatched, making it unsuitable or impossible to further perform near-field communication interaction.

[0061] In this scenario, there is a high probability that the other entities are not near-field communication (NFC) devices. Unlike traditional solutions, this application supports and even encourages users to use their mobile terminals to touch entities other than NFC devices. This allows for more intelligent and automatic triggering of appropriate services without relying on NFC coil induction or NFC functionality. Consequently, users' NFC touch-based interaction habits can be expanded to include more application scenarios, overcoming the limitations of NFC devices, facilitating wider applications, providing users with more positive feedback experiences, and reducing the likelihood of interaction failures.

[0062] Alternatively, one could disregard whether near-field communication-related signals were detected (for example, not execute step S104, and not determine whether near-field communication-related signals were successfully detected), and more independently, after determining that the user's mobile terminal had touched other entities based on acceleration change data, directly identify other entities using data other than near-field communication-related signals.

[0063] Other data besides near-field communication signals can be collected in real-time starting at this point, or in advance during the contact process before or during the contact. Other data may include at least one of the following: image data, sound data, location data, temperature data, time data, etc.; correspondingly, they can be acquired through one or more different types of data acquisition modules such as camera modules, microphones, positioning modules, temperature sensors, and clock modules.

[0064] In step S106, other entities include daily necessities, desktops, walls, appliances that do not support near-field communication, people, or other animals.

[0065] In one or more embodiments of this specification, other entities or their environments are identified based on other data to determine what specific entities they are or their current environment. This information can directly or indirectly reflect why a user is interested in other entities, or even why they actively interact with these entities using their mobile device, thus providing an indication of intent. The dimensions of identification may include at least one of the following: type, name, appearance, purpose, and the relationship between the entity and its environment, etc.

[0066] S108: Based on the recognition result, determine the current user's intent and invoke a service page matching the intent on the user's mobile terminal.

[0067] Since the other entities that the user's mobile terminal is currently touching are most likely not near-field communication (NFC) devices, it is impossible to passively rely on information transmitted by the NFC devices themselves (such as pre-written NFC tag information) to trigger the user's mobile terminal to execute corresponding services. Furthermore, the other entities being touched are quite flexible. Therefore, this flexibility is adapted to infer the user's actual intention for this touch based on the recognition results. Then, catering to the inferred intention, the system proactively invokes matching service pages on the user's mobile terminal. These service pages can cover a wide range of different business areas, thus breaking through the limitations of traditional solutions that are confined to NFC-related service pages. This provides triggering opportunities for more service pages and helps to accurately meet the user's immediate needs.

[0068] The user's current intent can be directly reflected by the business page. In this case, the action of determining the current user's intent can specifically be to determine the matching business page.

[0069] Of course, determining the current user's intent can also include: judging which intent type the current situation belongs to based on predefined and categorized different intent types and specific meanings; or, providing a refined adaptive description or profile of the intent as the determined intent. Then, further matching the business page is done based on these intent types, descriptions, or profiles.

[0070] In one or more embodiments of this specification, based on the identified uses of other entities, it is determined that the current user needs a product or service related to that use (i.e., the current user's intent). Then, within a designated application on the user's mobile terminal, a business page providing the product or service is searched for and invoked. This page can be a business page owned by the designated application itself, such as a business subpage, or a business page of a partner's mini-program within the designated application, such as a business main page. In particular, a business page that facilitates direct use of the product or service can be invoked, allowing the user to fulfill their intent with a single click, providing good convenience. The designated application can be the implementing entity of this solution or other applications that cooperate with the implementing entity.

[0071] For example, assuming the other entity is a cup such as a drinking cup or a milk tea cup, the current user can touch the cup with their smartphone. The smartphone detects the touch event based on acceleration change data. Since it cannot detect any near-field communication signals emitted by the other party, it identifies the other party as a cup based on the automatically activated camera (in fact, when detecting the touch event, it may be possible to infer from the acceleration change data alone that the touch is likely a glass cup). Based on the identification result, it is determined that the current user's intention is to order a beverage (based on the specific appearance of the other entity, a more detailed and accurate intention may be determined, such as wanting to order a specific brand of milk tea). Then, based on this intention, the ordering page of a milk tea delivery mini-program in the current application is brought up on the smartphone, so that the user can directly and conveniently place an order.

[0072] pass Figure 1 This method proactively uses acceleration change data from the user's mobile terminal (e.g., a smartphone) to detect when the user's mobile terminal is touching other entities (e.g., a POS device supporting near-field communication), rather than relying on near-field communication coil sensing. This helps to prepare for and actually enter the near-field communication interaction state in advance, shortening the reaction time window and facilitating more efficient and reliable interaction. It can more autonomously trigger the timely display of corresponding service pages on the user's mobile terminal without relying entirely on the other device. Even if the near-field communication interaction process is unreliable, business can still be conducted to a certain extent based on such service pages. Moreover, even if the other entity is not a near-field communication device and does not have a near-field communication coil, it can still automatically trigger the user's mobile terminal to identify other entities through data other than near-field communication signals, and infer the user's intention for the touch action. Then, it can display a service page on the user's mobile terminal that matches that intention, thus triggering business more flexibly and improving the service compatibility and practicality of traditional near-field communication touch actions.

[0073] based on Figure 1In addition to the method described herein, this specification also provides some specific implementation schemes and extension schemes of this method, which will be further explained below.

[0074] Based on the preceding description, more intuitively, it provides Figure 1 See the implementation principle and effect diagram of the scheme. Figure 3 .

[0075] exist Figure 3 In this example, the user's mobile terminal is a smartphone, and the other entity touched is a cup.

[0076] Users can unlock their smartphones and then touch the cup with them. The touch event is detected by the acceleration change data during the process, as marked in the image as "touched". Then, based on various other data besides near-field communication data, the system can intelligently identify and judge the user's intention. Corresponding artificial intelligence models can be pre-trained to help improve the accuracy of the recognition and judgment. The data used may include real-time image data captured by the camera, current time, user habits, location data, or ambient sound data, etc.

[0077] Taking other data, including image data, as an example, the smartphone's camera (whether it's the front or rear camera, depending on the smartphone's orientation, can be automatically activated to capture image data as the smartphone moves towards or touches other objects) can be used.

[0078] Figure 3 Two different intent recognition results are given as examples.

[0079] The above is one possible user intent in this example, that is, the user may want to drink a beverage. Therefore, the user is asked "Thirsty? Go order milk tea", which will automatically bring up a milk tea ordering mini program.

[0080] The following scenario assumes that the system recognizes that the user wants to travel, and then asks the user "Do you want to travel?", which automatically brings up a travel-related page.

[0081] Similarly, based on the different intentions identified, prompts can be given to the user, who can then choose from the prompts, and the system can automatically bring up a more accurately matched business page based on the selection result.

[0082] This allows users to freely use their intuition to touch many different entities with their smartphones, conveniently and efficiently reaching business pages that may meet their current intentions, and then directly using the corresponding services. The experience is excellent, very fun, and also helps users discover and explore more diverse services.

[0083] In one or more embodiments of this specification, various other data can be used to identify other entities. In order to balance accuracy and processing speed, and to avoid wasting resources, other data can be accurately selected through a two-stage identification process.

[0084] Specifically, based on acceleration change data, the types of other entities are identified to obtain a first identification result; based on the first identification result, among various types of data acquisition modules, the data acquisition module corresponding to the type of other entities is determined as the target data acquisition module; the target data acquisition module is activated to collect data of the corresponding type; based on the collected data of the corresponding type, other entities are identified to obtain a second identification result, which is used to predict the current user's intent.

[0085] Other entity types. For example, these could include material type (soft or hard), glass, cardboard, or wood, degree of elasticity, etc., or shape type (vertical or horizontal), solid or hollow, regular or irregular shape, etc. These types can significantly affect the performance of acceleration change data. This impact might stem from the feedback of other entities when touched, or from the user adjusting their touch technique based on the different entities (e.g., a lighter touch on glass, a higher hand when touching a vertical entity, etc.).

[0086] Considering that in practical applications, some user business needs may not be fully represented by a single entity at hand, an intent matching scheme based on feature-free fusion is provided. (See [link to relevant documentation]). Figure 4 , Figure 4 This is a flowchart illustrating the scheme.

[0087] Figure 4 The process includes the following steps:

[0088] S402: Determine whether the user's mobile terminal has touched multiple other entities in sequence.

[0089] A short time range can be preset to determine whether multiple other entities have been touched sequentially within that time range. Alternatively, after each instance of touching another entity is detected, it can be checked whether another entity has been touched within the next preset time range; if not, the judgment should stop.

[0090] S404: If the near-field communication related signal is not successfully detected, the plurality of other entities are identified by other data besides the near-field communication related signal.

[0091] S406: Determine the basic purpose of the first other entity that the identified user mobile terminal touches among the plurality of other entities.

[0092] Starting with the first other entity encountered as the basis of intent, further refine the intent by encountering other entities, adding features to this foundation. Prioritize the business uses that the first other entity is most likely to involve, considering them as uses or needs. For example, the possible business uses of an entity like a cup include drinking beverages; similarly, the possible business uses of an entity like a wall include support, decoration, and advertising.

[0093] S408: Determine the appearance features or auxiliary uses of the remaining other entities touched by the identified user mobile terminal among the plurality of other entities.

[0094] The term "auxiliary" here refers to the auxiliary purpose relative to the first other entity. For other entities, the auxiliary purpose can be one or more of their basic purposes. In particular, it can be selected from the basic purposes that are more suitable for cooperating with the first other entity as auxiliary purposes, while avoiding the selection of basic purposes that may cause conflict.

[0095] S410: Based on the appearance features or auxiliary uses, and the basic uses, determine that the current user's intent includes needing a product with the basic uses and the appearance features, or needing a service with the basic uses and the auxiliary uses.

[0096] For example, the first other entity encountered is a cup, and the second other entity is a piece of fabric with a special pattern (which could be a portion of clothing). The basic use is drinking water, the appearance feature is the special pattern, and the secondary use is wrapping and covering. In this case, the intent is determined based on feature fusion. The intent might be: needing a drinking container with this special pattern, especially a drinking cup; or needing a cup sleeve to cover a drinking cup; or needing a beverage from a brand corresponding to the special pattern; and so on.

[0097] Similarly, you can interact with more other entities to achieve more complex feature fusion.

[0098] It needs to be emphasized that, Figure 4 The example process selected features related to purpose and appearance. More features can be freely combined as needed, such as features related to demand, structure, popularity, etc.

[0099] pass Figure 4This solution allows users to easily and freely trigger services that may align with their complex intentions through smooth, multiple touch operations. Even if it doesn't precisely target the user's complex intentions, it still has a high probability of inspiring other products or services that the user might also be interested in.

[0100] In one or more embodiments of this specification, the gestures of the user's mobile terminal during the touching process can be further distinguished, which can also reflect the user's attitude and the tendency of their intention.

[0101] Specifically, based on the recognition results and acceleration change data, it is determined whether the user's mobile terminal is touching other entities in a predefined informal posture; if so, the background image of the other entity is recognized, and based on the scene reflected by the recognized background image (which can be considered together with other entities), the user's business needs in the scene are determined, and a business page matching the business needs is invoked on the user's mobile terminal; otherwise, the background image of the other entity is ignored, and based on the other entity itself, the current user's intent is determined, and a business page matching the intent is invoked on the user's mobile terminal.

[0102] This at least distinguishes between predefined formal and informal postures. For formal postures, it can be assumed that the user's focus is precisely on the other entities being touched, rather than the current context. This is why the user touches things in a relatively "formal" and solemn manner. Conversely, for informal postures, it can be assumed that the user may pay more attention to the current context, and the other entities being touched are mainly used as a trigger, although there may also be some intentional connection. This is why the user touches things in a relatively "informal" and casual manner.

[0103] The preceding embodiments primarily illustrated using examples of other entities being objects. This application, in particular, also supports other entities such as people who touch, thereby creating a convenient licensing scheme. See also... Figure 5 , Figure 5 This is a flowchart illustrating a local business authorization scheme based on human touch, provided for one or more embodiments of this specification.

[0104] Figure 5 The process includes the following steps:

[0105] S502: Identify the other entities using data other than the near-field communication related signals, and determine whether the other entities are other users.

[0106] Other users here can be any human being, and do not need to be users who have registered with a specific application on the user's mobile device.

[0107] S504: Invoke the service page that matches the current scenario on the user's mobile terminal.

[0108] Optionally, this can also be introduced Figure 4 The approach in this solution involves determining whether the user's mobile terminal is touching other entities in a predefined informal posture, which helps to obtain more reliable scene information based on image background analysis.

[0109] Of course, the other users encountered are also part of the current scenario. Based on the appearance of other users (e.g., whether they are adults or children, what their relationship is with the current user, whether they are colleagues, friends or relatives, etc.), more information can be inferred, such as the services that may be suitable for other users to handle. This makes it easier to grant more intelligent and accurate local authorizations in the future.

[0110] In one or more embodiments of this specification, in response to the current user's confirmation operation, the service corresponding to the service page is authorized to other users. For example, the solutions in steps S506 and S508 can be used to help to authorize more reliably and accurately.

[0111] S506: In response to the current user's confirmation operation, determine one or more specified operations corresponding to the business page.

[0112] S508: Authorize the other user to perform the specified operation for the service on the user's mobile terminal, and refuse the other user to perform any other operation on the user's mobile terminal other than the specified operation, so that the current user can temporarily hand over the user's mobile terminal to the other user for use.

[0113] pass Figure 5 This solution, while addressing the issue that user mobile devices (typically smartphones) are highly personal items, allows for convenient, limited, and localized authorization. This enables users to confidently and temporarily entrust their mobile devices to another user, who can then use this permission to assist the current user with specific tasks (such as paying bills, registering for appointments, or entering information) or access specific services (such as temporarily using an application to access information). This approach effectively protects the current user's privacy and security.

[0114] Based on the same idea, one or more embodiments of this specification also provide apparatus and devices corresponding to the above methods, such as... Figure 6 , Figure 7 As shown. The apparatus and equipment are capable of performing the above methods and related alternatives accordingly.

[0115] Figure 6This specification provides a schematic diagram of the structure of an interactive service processing device according to one or more embodiments, applied to a user mobile terminal. The device includes:

[0116] The acceleration touch judgment module 602 collects the acceleration change data of the user mobile terminal and determines whether the user mobile terminal is touching other entities based on the acceleration change data.

[0117] The near-field communication detection module 604 detects near-field communication related signals to enable near-field communication with the other entities.

[0118] If the other entity recognition module 606 fails to detect the near-field communication related signal, it will identify the other entity using other data besides the near-field communication related signal.

[0119] The intent matching and invocation module 608 determines the current user's intent based on the recognition result and invokes a service page that matches the intent on the user's mobile terminal.

[0120] Optionally, the other entity recognition module 606 acquires image data captured by the camera of the user mobile terminal, which is automatically activated after the user mobile terminal touches another entity.

[0121] The other entities are identified based on the image data.

[0122] Optionally, the other entity recognition module 606 identifies the type of the other entity based on the acceleration change data to obtain a first recognition result;

[0123] Based on the first identification result, among various types of data acquisition modules, the data acquisition module corresponding to the type of the other entity is determined as the target data acquisition module;

[0124] The target data acquisition module is activated to collect the corresponding type of data;

[0125] Based on the collected data of the corresponding type, the other entities are identified to obtain a second identification result, which is used to predict the current user's intent.

[0126] Optionally, the various types of data acquisition modules include at least one of the following: a camera module, a microphone, a positioning module, and a temperature sensor.

[0127] Optionally, the intent matching invocation module 608 determines, based on the identified uses of the other entities, that the current user needs products or services related to those uses;

[0128] In a designated application on the user's mobile terminal, a business page providing the product or service is searched and invoked, wherein the page is a business sub-page of the designated application itself, or a business main page of a partner's mini-program in the designated application.

[0129] Optionally, the acceleration touch judgment module 602 determines whether the user mobile terminal has touched multiple other entities in sequence;

[0130] The intent matching invocation module 608 determines the basic purpose of the first other entity touched by the identified user mobile terminal among the plurality of other entities;

[0131] Determine the appearance features or auxiliary uses of the remaining entities touched by the identified user mobile terminal among the plurality of other entities;

[0132] Based on the appearance features or auxiliary uses, and the basic uses, the current user's intent is determined to include either needing a product with the basic uses and the appearance features, or needing a service with the basic uses and the auxiliary uses.

[0133] Optionally, the intent matching and invocation module 608 determines, based on the recognition result and the acceleration change data, whether the user's mobile terminal touches the other entity in a predefined informal posture;

[0134] If so, then identify the background image of other entities, determine the user's business needs in the scene based on the scene reflected by the identified background image, and invoke a business page that matches the business needs on the user's mobile terminal;

[0135] Otherwise, the background images of the other entities are ignored, and the user's intent is determined based on the other entities themselves, and a business page matching the intent is invoked on the user's mobile terminal.

[0136] Optionally, the intent matching invocation module 608 determines whether the other entities are other users;

[0137] The intent matching invocation module 608 determines, based on the recognition result, that the current user needs to grant corresponding authorization to other users according to the current scenario.

[0138] On the user's mobile terminal, a service page matching the current scenario is invoked. In response to the current user's confirmation operation, the service corresponding to the service page is authorized to other users.

[0139] Optionally, the intent matching invocation module 608 determines one or more specified operations corresponding to the service;

[0140] The user authorizes other users to perform the specified operation on the user's mobile terminal for the service, while refusing other users to perform any other operation on the user's mobile terminal other than the specified operation, so that the current user can temporarily hand over the user's mobile terminal to other users for use.

[0141] Optionally, the near-field communication detection module 604 activates the near-field communication function to detect whether there is a signal emitted by the near-field communication coil;

[0142] After the near-field communication-related signal is not successfully detected, it is determined that the other entity is an entity without a near-field communication coil, and the near-field communication function is automatically turned off accordingly.

[0143] Figure 7 This specification provides a schematic diagram of the structure of an interactive service processing device according to one or more embodiments, applied to a user mobile terminal. The device includes:

[0144] At least one processor; and,

[0145] A memory communicatively connected to the at least one processor; wherein,

[0146] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform:

[0147] Collect acceleration change data of the user's mobile terminal, and determine whether the user's mobile terminal is touching other entities based on the acceleration change data;

[0148] If so, detect near-field communication related signals in order to conduct near-field communication with the other entities;

[0149] If the near-field communication related signal is not successfully detected, the other entities are identified using other data besides the near-field communication related signal;

[0150] Based on the recognition result, the current user's intent is determined, and a service page matching the intent is invoked on the user's mobile terminal.

[0151] Based on the same idea, one or more embodiments of this specification also provide a non-volatile computer storage medium for use in a user mobile terminal, wherein the medium stores computer-executable instructions, the computer-executable instructions being configured as follows:

[0152] Collect acceleration change data of the user's mobile terminal, and determine whether the user's mobile terminal is touching other entities based on the acceleration change data;

[0153] If so, detect near-field communication related signals in order to conduct near-field communication with the other entities;

[0154] If the near-field communication related signal is not successfully detected, the other entities are identified using other data besides the near-field communication related signal;

[0155] Based on the recognition result, the current user's intent is determined, and a service page matching the intent is invoked on the user's mobile terminal.

[0156] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the customer's programming of the device. Designers can program a digital system themselves to "integrate" it onto a PLD, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must also be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0157] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0158] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0159] For ease of description, the above devices are described in terms of function, divided into various units. Of course, in implementing this specification, the functions of each unit can be implemented in one or more software and / or hardware components.

[0160] Those skilled in the art will understand that the embodiments of this specification can be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the embodiments of this specification can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0161] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0162] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0163] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0164] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0165] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0166] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0167] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0168] This specification can be described in the general context of computer-executable instructions that are executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This specification can also be practiced in distributed computing environments, where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0169] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments of apparatus, devices, and non-volatile computer storage media are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0170] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0171] The above description is merely one or more embodiments of this specification and is not intended to limit this specification. Various modifications and variations can be made to the one or more embodiments of this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of one or more embodiments of this specification should be included within the scope of the claims of this specification.

Claims

1. An interactive service processing method, applied to a user's mobile terminal, the method comprising: Collect acceleration change data of the user's mobile terminal, and determine whether the user's mobile terminal is touching other entities based on the acceleration change data; If so, detect near-field communication related signals in order to conduct near-field communication with the other entities; If the near-field communication related signal is not successfully detected, the other entities are identified using other data besides the near-field communication related signal; Based on the recognition result, the current user's intent is determined, and a service page matching the intent is invoked on the user's mobile terminal.

2. The method as described in claim 1, wherein identifying the other entity using data other than the near-field communication related signals specifically includes: Acquire image data captured by the camera of the user's mobile terminal, which is automatically activated after the user's mobile terminal touches another entity; The other entities are identified based on the image data.

3. The method as described in claim 1, wherein identifying the other entity using data other than the near-field communication related signals specifically includes: Based on the acceleration change data, the types of the other entities are identified to obtain a first identification result; Based on the first identification result, among various types of data acquisition modules, the data acquisition module corresponding to the type of the other entity is determined as the target data acquisition module; The target data acquisition module is activated to collect the corresponding type of data; Based on the collected data of the corresponding type, the other entities are identified to obtain a second identification result, which is used to predict the current user's intent.

4. The method as described in claim 3, wherein the various types of data acquisition modules include at least one of the following: a camera module, a microphone, a positioning module, and a temperature sensor.

5. The method as described in claim 1, wherein determining the current user's intent based on the recognition result and activating a service page matching the intent on the user's mobile terminal specifically includes: Based on the identified uses of the other entities, determine that the current user needs products or services related to those uses; In a designated application on the user's mobile terminal, a business page providing the product or service is searched and invoked, wherein the page is a business sub-page of the designated application itself, or a business main page of a partner's mini-program in the designated application.

6. The method as described in claim 1, wherein determining whether the user's mobile terminal is touching other entities specifically includes: Determine whether the user's mobile terminal has sequentially touched multiple other entities; The step of determining the current user's intent based on the recognition result specifically includes: Determine the basic purpose of the first other entity that the identified user mobile terminal touches among the plurality of other entities; Determine the appearance features or auxiliary uses of the remaining entities touched by the identified user mobile terminal among the plurality of other entities; Based on the appearance features or auxiliary uses, and the basic uses, the current user's intent is determined to include either needing a product with the basic uses and the appearance features, or needing a service with the basic uses and the auxiliary uses.

7. The method as described in claim 1, wherein determining the current user's intent based on the recognition result and activating a service page matching the intent on the user's mobile terminal specifically includes: Based on the identification results and the acceleration change data, it is determined whether the user's mobile terminal has touched the other entity in a predefined informal posture; If so, then identify the background image of other entities, determine the user's business needs in the scene based on the scene reflected by the identified background image, and invoke a business page that matches the business needs on the user's mobile terminal; Otherwise, the background images of the other entities are ignored, and the user's intent is determined based on the other entities themselves, and a business page matching the intent is invoked on the user's mobile terminal.

8. The method of claim 7, wherein determining whether the user mobile terminal touches the other entity in a predefined informal posture further comprises: Determine whether the other entities are other users; The step of determining the current user's intent based on the recognition result and then activating a service page matching the intent on the user's mobile terminal specifically includes: Based on the recognition result, it is determined that the current user needs to grant appropriate authorization to the other users according to the current scenario; On the user's mobile terminal, a service page matching the current scenario is invoked. In response to the current user's confirmation operation, the service corresponding to the service page is authorized to other users.

9. The method as described in claim 8, wherein authorizing the other users to access the services corresponding to the service page specifically includes: Determine one or more specified operations corresponding to the service; The user authorizes other users to perform the specified operation on the user's mobile terminal for the service, while refusing other users to perform any other operation on the user's mobile terminal other than the specified operation, so that the current user can temporarily hand over the user's mobile terminal to other users for use.

10. The method of claim 1, wherein detecting near-field communication related signals specifically includes: Activate the near-field communication function and detect if there is a signal emitted by the near-field communication coil; After the near-field communication-related signal is not successfully detected, the method further includes: The other entities are identified as entities that do not have a near-field communication coil, and the near-field communication function is automatically turned off accordingly.

11. An interactive service processing apparatus, applied to a user's mobile terminal, the apparatus comprising: The acceleration touch detection module collects acceleration change data of the user's mobile terminal and determines whether the user's mobile terminal is touching other entities based on the acceleration change data. If so, the near-field communication detection module detects near-field communication related signals in order to conduct near-field communication with the other entities. If other entity recognition modules fail to detect the near-field communication related signals, they will identify the other entities using other data besides the near-field communication related signals. The intent matching and invocation module determines the current user's intent based on the recognition result and invokes a service page that matches the intent on the user's mobile terminal.

12. The apparatus of claim 11, wherein the other entity recognition module acquires image data captured by the camera of the user mobile terminal, which is automatically activated after the user mobile terminal touches another entity; The other entities are identified based on the image data.

13. The apparatus of claim 11, wherein the other entity recognition module identifies the type of the other entity based on the acceleration change data to obtain a first recognition result; Based on the first identification result, among various types of data acquisition modules, the data acquisition module corresponding to the type of the other entity is determined as the target data acquisition module; The target data acquisition module is activated to collect data of the corresponding type; Based on the collected data of the corresponding type, the other entities are identified to obtain a second identification result, which is used to predict the current user's intent.

14. The apparatus of claim 13, wherein the various types of data acquisition modules include at least one of the following: a camera module, a microphone, a positioning module, and a temperature sensor.

15. The apparatus of claim 11, wherein the intent matching invocation module determines, based on the identified uses of the other entities, that the current user needs a product or service related to the uses; In a designated application on the user's mobile terminal, a business page offering the product or service is searched for and invoked, wherein... The page is either a business subpage of the specified application itself, or a business main page of a partner's mini-program within the specified application.

16. The apparatus of claim 11, wherein the acceleration touch determination module determines whether the user mobile terminal has sequentially touched multiple other entities; The intent matching invocation module determines the basic purpose of the first other entity touched by the user's mobile terminal among the plurality of other entities; Determine the appearance features or auxiliary uses of the remaining entities touched by the identified user mobile terminal among the plurality of other entities; Based on the appearance features or auxiliary uses, and the basic uses, the current user's intent is determined to include either needing a product with the basic uses and the appearance features, or needing a service with the basic uses and the auxiliary uses.

17. The apparatus of claim 11, wherein the intent matching wake-up module determines, based on the recognition result and the acceleration change data, whether the user mobile terminal touches the other entity in a predefined informal posture; If so, then identify the background image of other entities, determine the user's business needs in the scene based on the scene reflected by the identified background image, and invoke a business page that matches the business needs on the user's mobile terminal; Otherwise, the background images of the other entities are ignored, and the user's intent is determined based on the other entities themselves, and a business page matching the intent is invoked on the user's mobile terminal.

18. The apparatus of claim 17, wherein the intent matching invocation module determines whether the other entity is another user; The intent matching invocation module determines, based on the recognition result, whether the current user needs to grant corresponding authorization to other users according to the current scenario. On the user's mobile terminal, a service page matching the current scenario is invoked. In response to the current user's confirmation operation, the service corresponding to the service page is authorized to other users.

19. The apparatus of claim 18, wherein the intent matching invocation module determines one or more specified operations corresponding to the service; The user authorizes other users to perform the specified operation on the user's mobile terminal for the service, while refusing other users to perform any other operation on the user's mobile terminal other than the specified operation, so that the current user can temporarily hand over the user's mobile terminal to other users for use.

20. The apparatus of claim 11, wherein the near-field communication detection module activates the near-field communication function and detects whether there is a signal emitted by the near-field communication coil; After the near-field communication-related signal is not successfully detected, it is determined that the other entity is an entity without a near-field communication coil, and the near-field communication function is automatically turned off accordingly.

21. An interactive service processing device, applied to a user mobile terminal, the device comprising: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform: Collect acceleration change data of the user's mobile terminal, and determine whether the user's mobile terminal is touching other entities based on the acceleration change data; If so, detect near-field communication related signals in order to conduct near-field communication with the other entities; If the near-field communication related signal is not successfully detected, the other entities are identified using other data besides the near-field communication related signal; Based on the recognition result, the current user's intent is determined, and a service page matching the intent is invoked on the user's mobile terminal.

Images