CN108734446B

CN108734446B - Preference setting and service processing system, method, device and equipment

Info

Publication number: CN108734446B
Application number: CN201810300856.9A
Authority: CN
Inventors: 温涛
Original assignee: Advanced New Technologies Co Ltd
Current assignee: Advanced Nova Technology Singapore Holdings Ltd
Priority date: 2018-04-04
Filing date: 2018-04-04
Publication date: 2021-08-24
Anticipated expiration: 2038-04-04
Also published as: CN113837731A; CN108734446A

Abstract

The present specification discloses a preference setting and service processing system, method, device and equipment, in the method, a preference management system can receive preference setting information sent by a user management system, and the preference setting information is determined by the user management system according to a preference setting request sent by a user through an App. The preference management system can judge whether the preference type to be set carried in the preference setting information exists in the preference type which is stored in advance and corresponds to the App, if so, the preference management system can be instructed to set the preference type to be set according to the preference execution mode carried in the preference setting request, otherwise, the preference management system is not instructed to set the preference type to be set.

Description

Preference setting and service processing system, method, device and equipment

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a method, an apparatus, and a device for preference setting and service processing.

Background

In order to provide services to users better, currently, each service provider may cooperate with the same third party to enable the App operated by each service provider to support the services provided by the third party. For example, multiple facilitators cooperate with the same third party that is capable of providing payment services, so that the apps each operate have the functionality to invoke the payment services provided by that third party.

In practical applications, the service provider may provide the user with a setting service of a preferred execution mode, so that the user can execute the service in a preferred execution mode. For example, different users prefer different authentication methods when performing payment services, some users are used to perform authentication through passwords, some users tend to use fingerprint authentication, and some users prefer to use gesture passwords to perform authentication. Therefore, the user can set the verification mode of the self preference through the setting function of the preference execution mode provided by the App.

The service providers may provide different preference types for setting the execution mode of the service based on their actual needs. This requires a third party staff member to manually set different preference types for different service providers in the third party user management system for the actual needs of the different service providers. When the service provider needs to modify, delete and add some preference types, the worker also needs to manually modify, delete and add the preference types stored in the user management system, so that the burden of the worker is greatly increased, and meanwhile, the period for the service provider to adjust the preference types is increased.

Based on the prior art, a more rapid and convenient preference setting mode is needed.

Disclosure of Invention

The specification provides a preference setting system, which is used for solving the problem that the prior art cannot flexibly set preference types.

The present specification provides a system of preference setting, comprising:

the system comprises a user management system, a preference setting request sent by a user through an application App, preference setting information determined according to a to-be-set preference type carried in the preference setting request, and the preference setting information sent to the preference management system, wherein when an indication message sent by the preference management system is received, the to-be-set preference type is set according to a preference execution mode carried in the preference setting request;

and the preference management system receives preference setting information sent by the user management system, judges whether a to-be-set preference type carried in the preference setting information exists in a pre-stored preference type corresponding to the App, sends the indication message if the preference setting information exists, and does not send the indication message if the preference setting information does not exist.

The specification provides a preference setting method, which is used for solving the problem that the prior art cannot flexibly set preference types.

The present specification provides a method of preference setting, comprising:

receiving preference setting information sent by a user management system, wherein the preference setting information is determined by the user management system according to a preference setting request sent by a user through the App;

judging whether the preference type to be set carried in the preference setting information exists in a pre-stored preference type corresponding to the App;

if yes, indicating the user management system to set the preference type to be set according to a preference execution mode carried in the preference setting request;

if not, the user management system is not instructed to set the preference type to be set.

The specification provides a preference setting device, which is used for solving the problem that the preference type cannot be flexibly set in the prior art.

The present specification provides a preference setting apparatus, comprising:

the receiving module is used for receiving preference setting information sent by a user management system, wherein the preference setting information is determined by the user management system according to a preference setting request sent by a user through the App;

the judging module is used for judging whether the preference type to be set carried in the preference setting information exists in a pre-stored preference type corresponding to the App or not; if yes, indicating the user management system to set the preference type to be set according to a preference execution mode carried in the preference setting request; if not, the user management system is not instructed to set the preference type to be set.

The present specification provides a preference setting device comprising one or more memories and a processor, the memories storing a program and configured to perform the following steps by the one or more processors:

The present specification provides a service processing system, which is used for solving the problem that the prior art cannot flexibly set preference types.

This specification provides a system for service processing, including:

the service system receives a service processing request sent by a user through an application App, determines a preference query request according to an App identifier of the App carried in the service processing request, sends the preference query request to a preference management system to acquire a preference type corresponding to the App identifier, queries a preference execution mode corresponding to the preference type from the user management system, and processes a service corresponding to the service processing request through the preference execution mode;

the preference management system receives a preference query request sent by a service system, queries a preference type corresponding to the App identifier carried in the preference query request, and returns the preference type to the service system;

and the user management system receives the preference type sent by the service system and returns the preference execution mode corresponding to the preference type.

The present specification provides a method for service processing, which is used to solve the problem that the prior art cannot flexibly set preference types.

The present specification provides a method for service processing, including:

receiving a preference query request sent by a service system, wherein the preference query request is determined by the service system according to an obtained application App identifier, and the App identifier is an App identifier corresponding to an App obtained by the service system from a service processing request sent by a user through the App;

inquiring a preference type corresponding to the App identifier carried in the preference inquiry request;

and sending the inquired preference type to the service system so that the service system determines a preference execution mode corresponding to the preference type from the user management system according to the preference type, and processing the service corresponding to the service processing request sent by the user through the preference execution mode.

The present specification provides a service processing apparatus, which is used to solve the problem that the prior art cannot flexibly set the preference type.

The present specification provides a service processing apparatus, including:

the system comprises a receiving module, a service system and a service processing module, wherein the receiving module is used for receiving a preference query request sent by the service system, the preference query request is determined by the service system according to an obtained application App identifier, and the App identifier is an App identifier corresponding to an App obtained by the service system from a service processing request sent by a user through the App;

the query module is used for querying a preference type corresponding to the App identifier carried in the preference query request;

and the sending module is used for sending the inquired preference type to the service system so that the service system determines a preference execution mode corresponding to the preference type from the user management system according to the preference type, and processes the service corresponding to the service processing request sent by the user through the preference execution mode.

The present specification provides a system of business processing comprising one or more memories and a processor, the memories storing programs and configured to perform the following steps by the one or more processors:

The present specification provides a method for service processing, including:

receiving a service processing request sent by a user through an application App;

determining a preference query request according to the App identifier of the App carried in the service processing request;

sending the preference query request to a preference management system to acquire a preference type corresponding to the App identifier;

inquiring a preference execution mode corresponding to the preference type from a user management system;

and processing the service corresponding to the service processing request through the preference execution mode.

The present specification provides a service processing apparatus, including:

the receiving module is used for receiving a service processing request sent by a user through an application App;

the determining module is used for determining a preference query request according to the App identifier of the App carried in the service processing request;

the sending module is used for sending the preference query request to a preference management system so as to obtain a preference type corresponding to the App identifier;

the query module is used for querying a preference execution mode corresponding to the preference type from the user management system;

and the processing module is used for processing the service corresponding to the service processing request through the preference execution mode.

The technical scheme adopted by the specification can achieve the following beneficial effects:

in one or more embodiments of the present specification, the preference management system may receive preference setting information sent by the user management system, where the preference setting information is determined by the user management system according to a preference setting request sent by the user through the App. The preference management system can judge whether the preference type to be set carried in the preference setting information exists in the preference type which is stored in advance and corresponds to the App, if so, the preference management system can be instructed to set the preference type to be set according to the preference execution mode carried in the preference setting request, otherwise, the preference management system is not instructed to set the preference type to be set.

The preference type can be set through the preference management system, and each set preference type is protected in the preference management system. When a subsequent user carries out preference setting through the preference type corresponding to the App contained in the preference management system, the preference management system only needs to judge that the preference type carried in the preference setting information exists in the stored preference type corresponding to the App, and can instruct the user management system to set the preference type to be set, so that the flexibility of setting the preference type is greatly improved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the specification and are incorporated in and constitute a part of this specification, illustrate embodiments of the specification and together with the description serve to explain the specification and not to limit the specification in a non-limiting sense. In the drawings:

fig. 1 is a schematic diagram of user preference setting and service processing in the prior art provided in this specification;

FIG. 2 is a process diagram of preference setting provided herein;

FIG. 3 is a process diagram of business processes provided herein;

fig. 4 is a schematic diagram illustrating a detailed process of user preference setting and service processing provided in the present specification;

FIG. 5 is a schematic diagram of an apparatus for setting preferences provided herein;

fig. 6 is a schematic diagram of a service processing apparatus provided in the present specification;

fig. 7 is a schematic diagram of a service processing apparatus provided in the present specification;

FIG. 8 is a schematic diagram of an apparatus for preference setting provided herein;

FIG. 9 is a schematic diagram of a business process apparatus provided herein;

fig. 10 is a schematic diagram of a service processing device provided in this specification.

Detailed Description

In the prior art, a user can make preference setting through an App, as shown in fig. 1.

Fig. 1 is a schematic diagram of user preference setting and service processing in the prior art provided in this specification.

According to the actual requirements of the user, the user needs to set a preference execution mode when executing the payment service. The App can show a corresponding payment preference setting page to a user, the user can select credit card payment as a preference execution mode required by executing the payment service in the payment preference setting page, and then the App generates a corresponding preference setting request according to the preference execution mode selected by the user, and sends the preference setting request to the user management system.

After receiving the preference setting request, the user management system can determine the preference type corresponding to the payment preference setting page according to the page identifier contained in the preference setting request: and the favorite is taken as a data main key, and is correspondingly stored with the field of 'payment by credit card' which is taken as value in the preference setting request, so that the setting of the user preference execution mode is completed, and the successful setting result is returned to the user.

When the user executes the payment service through the App, the user can send a payment request to the payment system through the App. The payment system can determine a preference type key corresponding to the page identifier through the page identifier contained in the payment request, then query a value corresponding to the preference type key in a user management system, determine that the user needs to pay through a credit card payment mode through the value, and further process the payment service through a credit card bound by the user in advance.

However, in the prior art, each preference type (i.e. key in the above example) in the customer management system is written into the customer management system by the system maintenance personnel in advance according to the actual needs of the service provider. In other words, if the service provider needs to change each preference type stored in the user management system, the system maintenance personnel needs to manually modify each preference type stored in the user management system, so that it is difficult for the service provider to change each preference type.

In practical application, multiple service providers may cooperate with the same third party, so that the apps operated by the service providers can support services provided by the third party. Therefore, the system maintenance personnel of the third party needs to manually set the preference type for each service provider according to the needs of different service providers and store the preference type in the user management system of the third party, which further increases the burden of the system maintenance personnel.

To this end, the present specification provides a method for setting preferences, in which a preference management system may receive preference setting information sent by a user management system, where the preference setting information is determined by the user management system according to a preference setting request sent by a user through an App. The preference management system can judge whether the preference type to be set carried in the preference setting information exists in the preference type which is stored in advance and corresponds to the App, if so, the preference management system can be instructed to set the preference type to be set according to the preference execution mode carried in the preference setting request, otherwise, the preference management system is not instructed to set the preference type to be set.

In order to make those skilled in the art better understand the technical solutions in one or more embodiments of the present disclosure, the technical solutions in one or more embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in one or more embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments in the present specification without any inventive step should fall within the scope of protection of the present specification.

Fig. 2 is a schematic process diagram of preference setting provided in this specification, which specifically includes the following steps:

s200: and receiving preference setting information sent by a user management system, wherein the preference setting information is determined by the user management system according to a preference setting request sent by a user through the App.

In this specification, a preference management system is provided, and each preference type corresponding to each App is stored in advance in the preference management system. The preference management system can instruct the user management system to set a preference execution mode required by the user through the stored corresponding relation between each App and each preference type and the received preference setting information sent by the user management system.

The preference setting information mentioned here may be determined by the user management system according to a preference setting request sent by the user. The App can generate a corresponding preference setting request according to a preference execution mode selected by a user in a preference setting page displayed by the App. The preference setting request comprises an App identifier of the App, a service type and a preference type corresponding to a preference execution mode selected by a user.

The service type mentioned here corresponds to the preference setting page. In practical application, when a user needs to perform preference setting on a service, a desired preference execution mode can be selected from a preference setting page for the service shown in an App. Therefore, different preference setting pages can correspond to different services, that is, different service types. For example, when the user sets the preferred payment method in the payment preference setting page, the payment preference setting page corresponds to the payment service (i.e., the service type).

In this specification, each preference type corresponding to the App is stored in advance in the App, and the App can determine the preference type corresponding to the preference type according to the preference execution mode set by the user. For example, when the user sets a preferred verification mode in the App, the App may determine the preference type corresponding to the verification mode: the facade authentication.

In practical application, different service providers may cooperate with the same third party, but in such a scenario, there may be a case where different service providers set the same preference type, but the same preference type is executed in different preference modes corresponding to apps launched by different service providers. For example, it is assumed that both the service provider a and the service provider B are provided with the preference type of fav1, but in the App introduced by the service provider a, the preference execution manner corresponding to the fav1 is the favorite payment manner, and in the App introduced by the service provider B, the preference execution manner corresponding to the fav1 is the favorite verification manner. In order to effectively distinguish preference types set by different service providers, an App identifier can be introduced, and each preference type set by each service provider is effectively isolated on the aspect of the App, so that the same preference types set by different service providers are prevented from being mixed.

Of course, each preference type can also be effectively isolated at the level of the service provider by the service provider identification (such as the service provider name, the service provider organization code, etc.). Correspondingly, the preference setting request sent by the App to the user management system also carries the service provider identifier.

The user management system may determine preference setting information according to the preference setting request. The preference setting information comprises an App identifier, a service type and a preference type. After receiving the preference setting information, the preference management system may verify the preference setting information in a subsequent process, and instruct the user management system to set a preference execution mode required by the user after determining that the preference setting information is verified.

It should be noted that, in this specification, a service provider operating an App may set a preference type in the preference management system according to an actual requirement of the service provider. When the service provider needs to add a preference type on the original basis, the preference type to be added can be sent to the preference management system, and the preference management system can correspondingly store the preference type to be added, the App identifier corresponding to the App and the service type applicable to the preference execution mode corresponding to the preference type to be added.

Similarly, when the service provider needs to delete the original preference type, the preference type to be deleted can be sent to the preference management system, the preference management system can delete the corresponding relation between the stored preference type to be deleted and the App identifier, and meanwhile, the user management system can be instructed to delete the preference type to be deleted and the preference execution mode corresponding to the preference type to be deleted.

If the service provider needs to modify the original preference type, the preference type to be modified and the modified preference type obtained by modifying the preference type to be modified can be sent to a preference management system, and the preference management system can modify the stored preference type to be modified into the modified preference type and instruct the user management system to modify the preference type to be modified into the modified preference type.

As can be seen from the above description, the preference management system provided in the whole system architecture can provide convenient preference type setting services for each service provider, which is equivalent to that the preference management system provides a window for setting preference types for each service provider. Each service provider can set, modify and delete each preference type according to the actual requirements of the service provider, so that the convenience and the flexibility of the service provider for setting the preference type are improved.

S202: and judging whether the preference type to be set carried in the preference setting information exists in a pre-stored preference type corresponding to the App, if so, executing the step S204, and if not, executing the step S206.

S204: and indicating the user management system to set the preference type to be set according to the preference execution mode carried in the preference setting request.

S206: the user management system is not instructed to set the preference type to be set.

In actual applications, there may be situations where the service provider updates the App, but does not update the preference type in a timely manner. It is assumed that the service provider adds a preference type to a service and adds a corresponding preference type to an App launched by the service provider, but the service provider does not synchronize the preference type in the preference management system in time.

Based on this, after receiving the preference setting information sent by the user management system, the preference management system can determine whether the corresponding relationship among the App identifier, the service type, and the preference type included in the preference setting information is already stored. If the preference type exists, the preference type can be determined to be preset by the service provider, and then in the subsequent process, an indication message can be sent to the user management system to indicate the user management system to correspondingly store the preference type and the preference execution mode contained in the preference setting request, otherwise, the indication message is not sent to the user management system, namely, the user management system is not indicated to correspondingly store the preference type and the preference execution mode.

Of course, if the preference management system determines that the correspondence is not stored, an inquiry message may be sent to the service provider corresponding to the App to inquire whether the service provider increases the preference type, so as to prompt the service provider to synchronize the preference type included in the preference management system in time in this manner.

In this specification, the user management system may store the preference identifier in association with the preference execution manner according to an instruction from the preference management system. Specifically, the user management system may use the preference type as a query primary key, and store a preference mode field indicating a preference execution mode set by the user in the preference setting request as a value, as shown in the following table.

key	value	Type of service
			favoritepayment	Credit card	Payment

TABLE 1

It is assumed that, after receiving the instruction sent by the preference management system, the user management system may make a favorite type as a favorite primary key, and set a preference mode field indicating a preference execution mode in the preference setting request: credit card, as the key: the value of the favorite is correspondingly stored, and the service types corresponding to the preference categories can be correspondingly stored. In this way, the subsequent App can use the preference type favorite as a query primary key, and query the key from the user management system: and determining that the user needs to complete payment in a payment mode by using a credit card according to the value corresponding to the favorite payment.

Of course, the App identifier (or service provider identifier) may also be added to the above corresponding relationship, that is, the user management system may correspondingly store the App identifier, the preference type, the preference mode field, and the service type.

As can be seen from the above method, since the preference type can be set by the preference management system, and each set preference type is protected in the preference management system. When a subsequent user carries out preference setting through the preference type corresponding to the App contained in the preference management system, the preference management system only needs to judge that the preference type carried in the preference setting information exists in the stored preference type corresponding to the App, and can instruct the user management system to set the preference type to be set, so that the flexibility of setting the preference type is greatly improved.

After the user completes the setting of the preferred execution mode, the service processing may be performed in a subsequent process through the set preferred execution mode, as shown in fig. 3.

Fig. 3 is a schematic process diagram of service processing provided in this specification.

S300: and receiving a service processing request sent by a user through the application App.

S302: and determining a preference query request according to the App identifier of the App carried in the service processing request.

In the service execution process, the user can send a service processing request to the service system through the App installed in the terminal to execute the service. The terminal mentioned here can be a mobile phone, a computer, etc. The service processing request sent by the App to the service system may carry an App identifier corresponding to the App and a service type corresponding to the service, and then a corresponding preference query request is determined according to the determined App identifier and the determined service type.

S304: and sending the preference query request to a preference management system to acquire a preference type corresponding to the App identifier.

Because the preference management system stores the corresponding relation among the App identifications, the service types and the preference types, the service system can send the preference query request to the preference management system, and the preference management system can determine at least one preference type corresponding to the service type and the App identification according to the App identification and the service type contained in the preference query request, and then returns the determined preference type to the service system.

S306: and inquiring a preference execution mode corresponding to the preference type from the user management system.

S308: and processing the service corresponding to the service processing request through the preference execution mode.

As can be seen from the above description, the service system stores the corresponding relationship between each preference type and each preference execution manner, so that the service system can further query the preference execution manner corresponding to the obtained preference type from the user management system, and further process the service corresponding to the obtained service processing request through the queried preference execution manner.

Specifically, the service type may use the obtained preference type as a query key, so as to query a value corresponding to the query key from the user management system, determine a preference execution mode corresponding to the preference type and set by the user according to the queried value, and then perform service processing according to the preference execution mode.

In order to further describe the preference setting and service processing method provided in this specification, the following will fully describe two procedures of preference setting and service processing by specific examples, as shown in fig. 5.

Fig. 4 is a schematic diagram illustrating a detailed process of user preference setting and service processing provided in this specification.

The user can set a preferred execution mode required when executing the payment service through the App. The App can generate a corresponding preference setting request according to the preference execution mode selected by the user so as to send the preference setting request to the user management system. The preference setting request comprises an App identifier corresponding to the App, a service type corresponding to the payment service and a preference type corresponding to the preference execution mode.

The user management system can generate preference setting information containing the App identifier, the service type and the preference type according to the preference setting request, and send the preference setting information to the preference management system. The preference management system may verify the correspondence between the three included in the preference setting information to determine whether the correspondence between the three exists in the correspondence between each App id, each service type, and each preference type included in the preference management system.

If the preference setting request exists, the user management system can be instructed to correspondingly store the preference type and the preference execution mode contained in the preference setting request.

When the user executes the payment service, the user can send a payment request (i.e. a service processing request) to a payment system (i.e. a service system) through the App. The payment system can determine the App identifier of the App sending the payment request from the payment request, and further inquire a preference type corresponding to the payment service provided by the App from a preference management system.

After the payment system obtains the preference type, a preference execution mode corresponding to the preference type and the user identifier (such as a user account) of the user can be queried from the user management system as follows: and the bank card pays, and further the payment service executed by the user can be completed in a bank card payment mode.

Based on the same idea, the present specification also provides a corresponding preference setting apparatus and a service processing apparatus, as shown in fig. 5, 6, and 7.

Fig. 5 is a schematic diagram of a preference setting apparatus provided in this specification, which specifically includes:

a receiving module 501, configured to receive preference setting information sent by a user management system, where the preference setting information is determined by the user management system according to a preference setting request sent by a user through the App;

the judging module 502 is used for judging whether the preference type to be set carried in the preference setting information exists in a pre-stored preference type corresponding to the App; if yes, indicating the user management system to set the preference type to be set according to a preference execution mode carried in the preference setting request; if not, the user management system is not instructed to set the preference type to be set.

The preference setting information further includes: an App identifier of the App and a service type corresponding to the service;

the determining module 502 determines whether a corresponding relationship among the App id, the service type, and the preference type is pre-stored.

The device further comprises:

the saving module 503 is configured to, when receiving the preference type to be added, correspondingly save the preference type to be added and the App identifier of the App; when a preference type to be deleted is received, deleting the stored corresponding relation between the preference type to be deleted and the App identifier; when the preference type to be modified and the modified preference type corresponding to the preference type to be modified are received, modifying the stored preference type to be modified into the modified preference type, and instructing the user management system to modify the preference type to be modified into the modified preference type.

Fig. 6 is a schematic diagram of a service processing apparatus provided in this specification, which specifically includes:

the receiving module 601 is configured to receive a preference query request sent by a service system, where the preference query request is determined by the service system according to an obtained application App identifier, and the App identifier is an App identifier corresponding to an App obtained by the service system from a service processing request sent by a user through the App;

the query module 602 is configured to query a preference type corresponding to the App identifier carried in the preference query request;

the sending module 603 sends the queried preference type to the service system, so that the service system determines a preference execution manner corresponding to the preference type from the user management system according to the preference type, and processes a service corresponding to a service processing request sent by the user through the preference execution manner.

The preference query request also carries a service type corresponding to the service;

the query module 602 queries a preference type corresponding to each App identifier and each service type from the pre-stored correspondence among each App identifier, each service type, and each preference type.

Fig. 7 is a schematic diagram of a service processing apparatus provided in this specification, which specifically includes:

a receiving module 701, configured to receive a service processing request sent by a user through an application App;

a determining module 702, configured to determine a preference query request according to the App identifier of the App carried in the service processing request;

a sending module 703, configured to send the preference query request to a preference management system to obtain a preference type corresponding to the App identifier;

the query module 704 is used for querying a preference execution mode corresponding to the preference type from the user management system;

the processing module 705, through the preference execution mode, processes the service corresponding to the service processing request.

The determining module 702 determines the preference query request according to the App identifier of the App carried in the service processing request and the service type corresponding to the service.

The sending module 703 is configured to send the preference query request to the preference management system, so as to obtain, from the preference management system, a preference type corresponding to the App identifier and the service type.

The query module 704 sends the obtained preference type as a query primary key to the user management system, so as to obtain a value corresponding to the query primary key from the user management system; and determining a preference execution mode corresponding to the preference type according to the acquired value.

Based on the above-described method for setting preferences, the present specification also correspondingly provides an apparatus for setting preferences, as shown in fig. 8. The apparatus includes one or more memories and a processor, the memories storing programs and configured to perform the following steps by the one or more processors:

Based on the service processing method described above, the present specification further provides a device for service processing, as shown in fig. 9. The apparatus includes one or more memories and a processor, the memories storing programs and configured to perform the following steps by the one or more processors:

Based on the service processing method described above, the present specification further provides a device for service processing, as shown in fig. 10. The apparatus includes one or more memories and a processor, the memories storing programs and configured to perform the following steps by the one or more processors:

In one or more embodiments of the present description, the preference management system may receive preference setting information sent by the user management system, where the preference setting information is determined by the user management system according to a preference setting request sent by the user through the App. The preference management system can judge whether the preference type to be set carried in the preference setting information exists in the preference type which is stored in advance and corresponds to the App, if so, the preference management system can be instructed to set the preference type to be set according to the preference execution mode carried in the preference setting request, otherwise, the preference management system is not instructed to set the preference type to be set.

In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, 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, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the various elements may be implemented in the same one or more software and/or hardware implementations of the present description.

As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, the description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The description has been presented with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to one or more embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may 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, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

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

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, 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 technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

This description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

The above description is merely one or more embodiments of the present disclosure and is not intended to limit the present disclosure. Various modifications and alterations to one or more embodiments of the present description will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement or the like made within the spirit and principle of one or more embodiments of the present specification should be included in the scope of the claims of the present specification.

Claims

1. A system of preference settings, comprising:

2. A method for setting preference, which prestores preference types corresponding to application apps, comprises the following steps:

3. The method of claim 2, the preference setting information further comprising: an App identifier of the App and a service type corresponding to the service;

judging whether the preference type to be set carried in the preference setting information exists in a pre-stored preference type corresponding to the App, specifically comprising:

and judging whether the corresponding relation among the App identification, the service type and the preference type is stored in advance.

4. The method according to claim 2, wherein the saving of the preference type corresponding to the App specifically comprises:

when a preference type to be added is received, correspondingly storing the preference type to be added and an App identifier of the App;

when a preference type to be deleted is received, deleting the stored corresponding relation between the preference type to be deleted and the App identifier;

when the preference type to be modified and the modified preference type corresponding to the preference type to be modified are received, modifying the stored preference type to be modified into the modified preference type, and instructing the user management system to modify the preference type to be modified into the modified preference type.

5. A system of business processing, comprising:

6. A method of service processing, comprising:

7. The method according to claim 6, wherein the preference query request further carries a service type corresponding to the service;

inquiring a preference type corresponding to the App identifier carried in the preference inquiry request, specifically comprising:

and inquiring preference types corresponding to the App identifications and the service types from the pre-stored corresponding relations among the App identifications, the service types and the preference types.

8. A method of service processing, comprising:

9. The method according to claim 8, wherein determining a preference query request according to the App identifier of the App carried in the service processing request specifically includes:

and determining the preference query request according to the App identifier of the App carried in the service processing request and the service type corresponding to the service.

10. The method according to claim 9, wherein the sending the preference query request to a preference management system to obtain a preference type corresponding to the App id specifically includes:

and sending the preference query request to the preference management system so as to acquire a preference type corresponding to the App identifier and the service type from the preference management system.

11. The method according to claim 8, wherein the step of querying the preference execution mode corresponding to the preference type from the user management system specifically comprises:

sending the acquired preference type serving as a query main key to the user management system so as to acquire a value corresponding to the query main key from the user management system;

and determining a preference execution mode corresponding to the preference type according to the acquired value.

12. A preference setting device for saving preference types corresponding to application apps in advance comprises:

13. The apparatus of claim 12, the preference setting information further comprising: an App identifier of the App and a service type corresponding to the service;

the judging module judges whether the corresponding relation among the App identification, the service type and the preference type is stored in advance.

14. The apparatus of claim 12, the apparatus further comprising:

the storage module is used for correspondingly storing the preference type to be added and the App identifier of the App when the preference type to be added is received; when a preference type to be deleted is received, deleting the stored corresponding relation between the preference type to be deleted and the App identifier; when the preference type to be modified and the modified preference type corresponding to the preference type to be modified are received, modifying the stored preference type to be modified into the modified preference type, and instructing the user management system to modify the preference type to be modified into the modified preference type.

15. An apparatus for traffic processing, comprising:

16. The apparatus according to claim 15, wherein the preference query request further carries a service type corresponding to the service;

and the query module queries preference types corresponding to the App identifications and the service types from the pre-stored corresponding relations among the App identifications, the service types and the preference types.

17. An apparatus for traffic processing, comprising:

18. The apparatus according to claim 17, wherein the determining module determines the preference query request according to an App identifier of the App and a service type corresponding to the service, which are carried in the service processing request.

19. The apparatus of claim 18, the sending module to send the preference query request to the preference management system to obtain a preference type corresponding to the App id and the service type from the preference management system.

20. The apparatus according to claim 17, wherein the query module sends the obtained preference type as a query primary key to the user management system, so as to obtain a value corresponding to the query primary key from the user management system; and determining a preference execution mode corresponding to the preference type according to the acquired value.

21. A preference setting device comprising one or more memories and a processor, the memories storing programs and configured to perform the following steps by the one or more processors:

receiving preference setting information sent by a user management system, wherein the preference setting information is determined by the user management system according to a preference setting request sent by a user through an App;

22. An apparatus of business processing comprising one or more memories and a processor, the memories storing programs and configured to perform the following steps by the one or more processors:

23. An apparatus of business processing comprising one or more memories and a processor, the memories storing programs and configured to perform the following steps by the one or more processors: