WO2022188469A1 - 一种业务请求的处理方法、装置及电子设备 - Google Patents

一种业务请求的处理方法、装置及电子设备 Download PDF

Info

Publication number
WO2022188469A1
WO2022188469A1 PCT/CN2021/133842 CN2021133842W WO2022188469A1 WO 2022188469 A1 WO2022188469 A1 WO 2022188469A1 CN 2021133842 W CN2021133842 W CN 2021133842W WO 2022188469 A1 WO2022188469 A1 WO 2022188469A1
Authority
WO
WIPO (PCT)
Prior art keywords
pid
general
pids
service request
host
Prior art date
Application number
PCT/CN2021/133842
Other languages
English (en)
French (fr)
Inventor
徐正生
周中雨
刘斌
李明
赵腾
Original Assignee
中国民航信息网络股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中国民航信息网络股份有限公司 filed Critical 中国民航信息网络股份有限公司
Publication of WO2022188469A1 publication Critical patent/WO2022188469A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/02—Reservations, e.g. for tickets, services or events
    • G06Q50/40—

Definitions

  • the present invention relates to the field of service request processing, and more particularly, to a service request processing method, device and electronic equipment.
  • PID is a resource provided to users when accessing the reservation system host (USAS host), and the number is limited.
  • the controller When the user purchases tickets, refunds tickets, etc., after the escrow service system verifies the user identity information in the received service request, the controller will send the PID corresponding to the user identity information and the service request to the USAS host, so that the The USAS host executes the service corresponding to the service request.
  • the present invention adopts the following technical solutions:
  • a service request processing method applied to a controller, wherein a plurality of general-purpose PIDs are preset in the controller; the service request processing method includes:
  • the service request and the registration result are sent to the host of the reservation system, so that the host of the reservation system executes the service operation corresponding to the service request according to the registration result.
  • a service request processing device applied to a controller, wherein a plurality of general-purpose PIDs are preset in the controller; the service request processing device includes:
  • a request receiving module configured to receive a business request sent by the hosting service system; the business request is sent by the hosting service system after the user identity information in the received business request is authenticated and passed;
  • a PID determination module configured to select a usable general PID from the plurality of general PIDs and use it as a target general PID when it is determined that the user identity information in the service request does not have a corresponding special PID;
  • a registration module for carrying out a host PID registration operation with the user identity information and the target general PID to obtain a registration result
  • the service execution module is configured to send the service request and the registration result to the host of the reservation system, so that the host of the reservation system executes the service operation corresponding to the service request according to the registration result.
  • An electronic device wherein a plurality of general-purpose PIDs are preset in the electronic device; the electronic device comprises: a memory and a processor;
  • the memory is used to store programs
  • the processor invokes the program and is used to:
  • the service request and the registration result are sent to the host of the reservation system, so that the host of the reservation system executes the service operation corresponding to the service request according to the registration result.
  • the present invention has the following beneficial effects:
  • the invention provides a method, device and electronic equipment for processing a service request.
  • the service request is sent to the controller, and the controller receives the service request.
  • the service request sent by the hosting service system if it is determined that the user identity information does not have a corresponding dedicated PID, it will select an available general PID from the multiple general PIDs preset in the controller, and use the general PID.
  • the PID performs business processing operations. That is, the present invention can use multiple preset general-purpose PIDs for business processing in a high-concurrency ticketing scenario, so that business requests do not need to wait for usable PIDs to be processed, thereby improving business processing speed.
  • FIG. 1 is a method flowchart of a method for processing a service request provided by an embodiment of the present invention
  • FIG. 2 is a method flowchart of another method for processing a service request provided by an embodiment of the present invention
  • FIG. 3 is a method flowchart of still another service request processing method provided by an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a scenario of a method for processing a service request provided by an embodiment of the present invention
  • FIG. 5 is a schematic block diagram of a method for processing a service request according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of an apparatus for processing a service request according to an embodiment of the present invention.
  • the term “including” and variations thereof are open-ended inclusions, ie, "including but not limited to”.
  • the term “based on” is “based at least in part on.”
  • the term “one embodiment” means “at least one embodiment”; the term “another embodiment” means “at least one additional embodiment”; the term “some embodiments” means “at least some embodiments”. Relevant definitions of other terms will be given in the description below.
  • USAS host (hereinafter referred to as the host) for sales.
  • the PID of the host needs to be the same as the work number used by the corresponding system or personnel.
  • USAS host refers to the host system of TravelSky, which provides user authentication, various flight data, various control transactions and other functions.
  • the fundamental limitation comes from the host.
  • the number of PIDs of the host is limited in the architectural design, and the number of PIDs cannot be expanded arbitrarily and unlimitedly; moreover, under the existing management system, the modification of PIDs needs to go through a rigorous process , it takes a long time, and the multi-department and multi-link application approval execution process can be changed.
  • the inventor found through research that if some stateless PIDs can be pre-configured, and then in high-concurrency scenarios, the stateless PIDs are registered to ensure that the PIDs can be Carry out business operations normally. After the business operation is completed, log out the PID to obtain a stateless PID, which can ensure that the stateless PID can be called in time for business processing in a high-concurrency business scenario.
  • the managed service system After the managed service system authenticates the user identity information in the received service request, it will send the service request to the controller. After receiving the service request sent by the managed service system, the controller will determine the user If the identity information does not have a corresponding dedicated PID, select an available general PID from a plurality of general PIDs preset in the controller, and use the general PID to perform service processing operations. That is, the present invention can use multiple preset general-purpose PIDs for business processing in a high-concurrency ticketing scenario, so that business requests do not need to wait for usable PIDs to be processed, thereby improving business processing speed.
  • the embodiment of the present invention provides a method for processing a service request, which is applied to a controller, and can also be applied to a processor, a server, and the like, which is not required by the embodiment of the present invention.
  • a plurality of general-purpose PIDs are preset in the controller, and general-purpose PIDs are also called stateless PIDs.
  • These general-purpose PIDs can be stored in the API PID connection pool module in the controller. This module provides a series of API (Application The connection pool of the dynamic PID of the Programming Interface, application programming interface), which stores a large number of general-purpose API-specific PIDs. These PIDs can be called by multiple users, and there is no corresponding dedicated user.
  • the service request processing method may include:
  • the service request is sent by the hosting service system after the user identity information in the received service request is authenticated and passed.
  • a user will send a service request to the SAT hosting service system, and the service request includes user identity information, such as login name, password, and the like.
  • the SAT hosting service system After the SAT hosting service system receives the service request, it will send the user identity information to the IAM authentication module.
  • the IAM authentication module is a third-party account identity authentication module that provides IAM information that belongs to the user according to the identity information submitted by the user, etc. Function.
  • the IAM authentication module verifies the identity information and obtains the verification result. The verification result is then returned to the SAT hosting service system.
  • the SAT hosting service system After receiving the verification result, the SAT hosting service system will determine whether the verification result has passed or failed the verification, and if the verification has passed, it will send the service request to the controller. If the verification fails, it will return the authentication failure information to the user, so that the user can keep abreast of the login status.
  • the controller After the controller receives the service request, it will obtain the user identity information from the service request, and then determine whether the user identity information has a corresponding dedicated PID. Dedicated PID, the controller inquires whether the user identity information in this service request has a corresponding dedicated PID from the stored data.
  • PIDs may be allocated according to airlines when applying, for example, 10 PIDs are allocated to airline A, and employees in airline A share these 10 PIDs. Assign 20 PIDs to Airline B and employees in Airline B share these 20 PIDs.
  • the controller determines that the user identity information does not have a corresponding dedicated PID, it will select a usable general PID from the above-mentioned connection pool.
  • usable means that the target is not used, that is, a general-purpose PID that is not currently used is selected from the connection pool and used as the target general-purpose PID.
  • step S12 may include:
  • the preset PID screening rule may be to screen a general PID with the smallest or largest serial number, or randomly screen a general PID as the general PID to be processed.
  • step S22 Determine whether the general PID to be processed is in an unused state; if so, go to step S23; if not, go to step S24.
  • the general PID to be processed it is determined whether the general PID to be processed is in an unused state.
  • the attribute information of the general PID can be various, such as unused, abnormal use, normal use and so on.
  • unused means that the PID is currently not used
  • abnormal use means that the PID is used, but the PID has not been successfully logged out due to poor network and other reasons
  • normal use means that the PID is being used normally .
  • the attribute information of the PID can be obtained, and then it is determined whether the attribute information is unused.
  • the PID can be used directly, and then the PID to be processed is used as the target to pass the PID.
  • step S24 Determine whether the general PID to be processed is in an abnormal use state; if so, go to step S25.
  • the attribute information After the attribute information is obtained, it is determined whether the attribute information is abnormally used, and if so, it is determined that the general PID to be processed is in an abnormally used state.
  • performing the host PID logout operation is performing the SO operation, and the PID after the SO operation is performed is the target general PID.
  • the host PID registration operation is performed, that is, the SI registration operation is performed, and the SI registration operation is performed on the user identity information and the target general PID to obtain a registration result.
  • the PID that has performed the SI registration operation can process the service.
  • controller is provided with an APIPIDSignedIN module: this module is used to register (SI) the PIDs in the API PID connection pool, and to change the identity of the PIDs in the API PID connection pool.
  • APIPIDSignedIN this module is used to register (SI) the PIDs in the API PID connection pool, and to change the identity of the PIDs in the API PID connection pool.
  • an APIPIDSignedOUT module is set in the controller: this module is used to deregister (S0) the PIDs in the API PID connection pool, and the PIDs after deregistration become generic PIDs with no attributes.
  • the service request and the registration result can be sent to the host of the reservation system, that is, the above-mentioned USAS host.
  • the USAS host executes the service operation corresponding to the service request according to the registration result.
  • the USAS host After the USAS host successfully executes the service operation, it will return a service successful execution message to the controller in this embodiment. After receiving the service successful execution message returned by the reservation system host after successfully executing the service operation, the controller will The target general PID executes the host PID logout operation, that is, the SO operation, and the PID after performing the SO operation becomes stateless, that is, the general PID, and the general PID is put into the above-mentioned connection pool for next use.
  • the above embodiment describes how to use the general PID in the connection pool to perform service processing when it is determined that the user identity information in the service request does not have a corresponding dedicated PID.
  • the general PID is also obtained from the connection pool at this time.
  • the method further includes: judging whether all the dedicated PIDs corresponding to the user identity information are used; Select an available general PID from among the general PIDs and use it as the step of the target general PID, and execute it sequentially.
  • a generic PID can be selected from the connection pool to use. Specifically, when it is determined that the dedicated PIDs corresponding to the user identity information are all used, the steps of selecting an available general-purpose PID from the plurality of general-purpose PIDs as the target general-purpose PID are performed, and steps S13-S14 are performed.
  • the managed service system After the managed service system passes the identity authentication on the user identity information in the received service request, it will send the service request to the controller. After the controller receives the service request sent by the managed service system, it will determine the In the case that the user identity information does not have a corresponding dedicated PID, select an available general PID from a plurality of general PIDs preset in the controller, and use the general PID to perform service processing operations. That is, the present invention can use multiple preset general-purpose PIDs for business processing in a high-concurrency ticketing scenario, so that business requests do not need to wait for usable PIDs to be processed, thereby improving business processing speed.
  • the above-mentioned embodiment introduces that, in the case where there is no dedicated PID or the dedicated PID is not enough, a general-purpose PID can be selected from the above-mentioned connection pool to perform service processing. Then the number of general PIDs of the connection pool needs to be adjusted according to its usage to dynamically use the PID usage scenarios.
  • FIG. 3 it also includes:
  • the usage attribute information may be the number of general-purpose PIDs used at the same time, the usage frequency of PIDs, and the like.
  • the number of PIDs used at the same time is 30, 50, 150, etc.
  • the frequency of use can be every 5 minutes, every 20 minutes, etc.
  • step S32 Determine whether it is necessary to delete at least one general PID of the plurality of general PIDs; if so, go to step S33, and if not, go to step S34.
  • the use attribute information it is determined whether a deletion operation needs to be performed on at least one general PID of the plurality of general PIDs.
  • the number of deletions may be determined, for example, 5% of deletions and so on.
  • the specific number of deletions can be determined according to the usage of the general PID.
  • the number of deletions may be determined according to a preset deletion rule.
  • the deletion rule may be determined according to the frequency of use, or determined according to the number of PIDs used at the same time, or determined according to the frequency of use and the number at the same time.
  • step S34 determine whether a new general PID needs to be created; if so, go to step S35.
  • the number of PIDs used at the same time is 180, and the frequency of use is once every 4 minutes. It can be seen that there are more general-purpose PIDs set in the connection pool. PIDs are often used, that is, the number of general-purpose PIDs set is normal. In this case, some general-purpose PIDs can be added to ensure that the general-purpose PIDs are not enough when the traffic volume increases suddenly.
  • the created quantity when creating, may be determined, for example, five percent created and so on.
  • the specific number to be created can be determined according to the usage of the general PID.
  • the creation quantity can be determined according to the preset creation rules.
  • the creation rule can be determined according to the frequency of use, or according to the number of PIDs used at the same time, or determined according to both the frequency of use and the number of PIDs.
  • the number of PIDs in the connection pool can be dynamically adjusted according to the usage of general PIDs in the connection pool, which is more suitable for the usage of PIDs.
  • Fig. 4 provides a specific implementation process, specifically:
  • Step 1 IAM user authentication.
  • the IAM module will first verify the user's identity information, and obtain other information corresponding to the user, such as AgentNo number, level and other information.
  • Step 2 Get the PID in the API PID connection pool. According to the identity of the user accessing the API at this time, identify whether it has its own dedicated PID. If so, and the dedicated PID is not occupied, the dedicated PID will be used first. If there is no dedicated PID or the dedicated PID is occupied, At this point, the API general PID will be applied.
  • Step 3 API PID account registration or cancellation operation. First, judge the status of the PID obtained in the dynamic API PID pool. If the PID has not been subjected to the SO operation for some reason, the SO operation will be performed first, so that the PID becomes a stateless PID, and the SO operation will be performed after the SO operation is performed. SI operation. If the obtained PID itself is a stateless PID, the SI registration operation will be performed according to the information obtained from the IAM authentication information and the PID.
  • Step 4 Access the USAS host. Use the PID after SI to access the USAS host together with identity information and service request.
  • Step 5 API PID account logout operation.
  • the SO operation is performed on the API PID after the access to the USAU host function is performed to make it a stateless API PID, and it is recycled into the dynamic API PID connection pool.
  • the present invention relates to the following five modules, which are specifically explained as follows:
  • USAS host module This module refers to the host system of TravelSky, which provides user authentication, various flight data, various control transactions and other functions.
  • IAM authentication module This module is a third-party account identity authentication module, which provides functions such as confirming the IAM information belonging to the user according to the identity information submitted by the user.
  • API PID connection pool module This module provides a series of API dynamic PID connection pools, which store a large number of common API-specific PIDs.
  • APIPIDSignedIN module This module is used to register the PID in the APIPID connection pool, and change the identity of the PID in the APIPID connection pool.
  • APIPIDSignedOUT module This module is used to cancel the PID in the API PID connection pool, and the PID after the logout becomes a generic PID with no attributes.
  • the above USAS host module is the final module that provides general operations such as query, booking, change, refund, etc.
  • the connection between the user and the module requires a PID number dedicated to the USAS host, and the PID number plays a role in classification.
  • the control of user identity and authority provides different authority and background data according to the identity of the user accessing the USAS host.
  • the IAM authentication module provides an identity information authentication method approved by the USAS host module.
  • the API can use the IAM-authenticated identity and corresponding permissions to access the USAS host module. After IAM authentication, the user, role, permissions and other information will be provided. , the information is recognized by the USAS host module, and API users can use these identities to access the USAS host system.
  • the APIPID connection pool module provides an indiscriminate universal stateless PID for users to use.
  • the size range of the PID is provided by the USAS host module in advance and is used by the dedicated API.
  • One principle is that if the user has a dedicated PID, the dedicated PID will be used first. If not, the API general PID will be used.
  • the module will dynamically expand and configure the PID according to the user's concurrent number until it meets the requirements of high concurrent access. , after high concurrency becomes normal, the PIDs that have been idle for a long time will be recycled for reuse and use by other users.
  • the PIDs in the API general PID connection pool are always connected, and will ensure the normal working status of the PIDs in the connection pool, automatically isolate the PIDs that fail to connect/configure, and provide external alarms.
  • the APIPIDSignedIN module is used to configure the PID in the API general PID connection pool, obtain the eterm configuration from the configuration library and log in to obtain the PID. After obtaining the PID, obtain the information required by SI from IAM, such as AGENT NUMBER/USER Group/OFFICE/AIRLINE, Execute the SI operation on this PID to register the PID configuration. If the SI is successful, the configuration is successful, and the user can access the USAS host module through this PID.
  • the APIPIDSignedOUT module is used to de-associate the generic PID with the user attribute configuration of the API generic PID that has been configured and registered and has been used. Its function is to release the association between the generic PID and the specific API user attribute. It only performs necessary checks. For example, all RTs have already executed IG, the ticket machine has not been established, and all transactions that need to be rolled back have been rolled back.
  • the general PID after SO will be put back into the connection pool, and it can also be configured again as the identity attribute of other users according to the way of SI registration and configuration, realizing the infinite cycle of PID use.
  • the SI operation will be performed.
  • the function of the SI operation is to assign a reasonable IAM-authenticated identity information that can be recognized by the USAS host module to the PID.
  • the user can use the PID to go to the USAS. Obtain the required data in the host module or do permission transactions.
  • the PID will be returned, that is, the SO operation will be performed.
  • a specific example is given to illustrate the process of dynamically configuring the PID.
  • the identity information used is casatn1, pek069, this airline user does not have a dedicated PID number.
  • the SAT will perform IAM authentication according to the user's casatn1 and pek069, and obtain other information belonging to casatn1 and pek069 from the IAM authentication. For example, AGENTNO is 36751, level is 41 and other information; because the airline user does not have a dedicated PID number, it is necessary to obtain a stateless PID from the APIPID connection.
  • PIDs in the APIPID connection pool there are multiple PIDs in the APIPID connection pool at this time, such as 14598, 23569, 87965, 23568, etc. At this time, there will be two situations according to the status of the PID. If the obtained PID number is 23569, if the PID 23569 fails to create a connection to the USAS host or is suddenly interrupted after the last connection to the USAS host, there are unexpected reasons. If the PID cannot perform the SO operation normally, the SO operation will be performed on the PID number 23569 first. After the SO operation is successful, the SI operation will be performed according to the identity information obtained by the IAM authentication and the PID number. The user's IAM identity information is bound.
  • the SI operation can be performed directly, and the PID number 23569 and the identity information obtained by IAM authentication are bound.
  • SAT is The PID can be used to access the USAS host and perform the operation that the user wants to perform; after the complete host operation is performed, the host will perform the SO operation on the PID to make it a stateless PID, and recycle the dynamic APIPID connection in the pool.
  • the present invention formulates a processing method for service requests, aiming at the shortcomings of few PIDs under the system limitation of the USAS host module, long application and deletion cycles, and unbalanced allocation of fixed PID pool resources.
  • API general PID the PID is allocated from a fixed PID segment for dynamic configuration.
  • the API general PID is provided to users, so that it can easily deal with the uncertainty of the number of PIDs under the condition of high concurrency.
  • the growth of the service brings problems such as slow service response.
  • the ability to use the existing PID can be amplified, which is insensitive to the user, and the user only needs to set up services such as promotion, which is convenient and flexible.
  • each block in the flowchart or block diagrams may represent a module, segment, or portion of code that contains one or more logical functions for implementing the specified functions executable instructions.
  • the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
  • each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations can be implemented in dedicated hardware-based systems that perform the specified functions or operations , or can be implemented in a combination of dedicated hardware and computer instructions.
  • Computer program code for performing operations of the present disclosure may be written in one or more programming languages, including but not limited to object-oriented programming languages—such as Java, Smalltalk, C++, and This includes conventional procedural programming languages - such as the "C" language or similar programming languages.
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer, or entirely on the remote computer or server.
  • the remote computer may be connected to the user's computer through any kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (eg, using an Internet service provider through Internet connection).
  • LAN local area network
  • WAN wide area network
  • another embodiment of the present invention provides a service request processing apparatus, which is applied to a controller, and the controller is preset with a plurality of General PID; with reference to Figure 6, the service request processing device includes:
  • the request receiving module 11 is used to receive a service request sent by the hosting service system; the service request is sent by the hosting service system after the user identity information in the received service request is authenticated and passed;
  • the PID determination module 12 is configured to select a usable general PID from the plurality of general PIDs and use it as the target general PID when it is determined that the user identity information in the service request does not have a corresponding special PID;
  • the registration module 13 is used to perform a host PID registration operation with the user identity information and the target general PID to obtain a registration result;
  • the service execution module 14 is configured to send the service request and the registration result to the host of the reservation system, so that the host of the reservation system executes the service operation corresponding to the service request according to the registration result.
  • the PID determination module includes:
  • the screening sequence submodule is used to select a usable general PID from the plurality of general PIDs according to the preset PID screening rule, and use it as the general PID to be processed;
  • a first state determination submodule configured to determine whether the to-be-processed general-purpose PID is in an unused state according to the attribute information of the to-be-processed general-purpose PID;
  • the first PID determination sub-module is configured to pass the PID with the to-be-processed PID as a target if it is in an unused state.
  • the PID determination module also includes:
  • a second state determination submodule configured to determine whether the to-be-processed general-purpose PID is in an abnormally-used state according to attribute information of the to-be-processed general-purpose PID when it is determined that the to-be-processed general-purpose PID is in a used state;
  • the second PID determination sub-module is configured to perform a host PID logout operation on the to-be-processed general PID to obtain a target general PID if it is in an abnormal use state.
  • a PID use determination module is used to determine whether the dedicated PIDs corresponding to the user identity information are all used when it is determined that the user identity information in the service request has a corresponding dedicated PID;
  • the PID determining module is further configured to select a usable general PID from the plurality of general PIDs and use it as a target when the PID use determining module judges that all the dedicated PIDs corresponding to the user identity information are used Generic PID.
  • a logout operation module configured to receive a service successful execution message returned by the reservation system host after successfully executing a service operation, and perform a host PID logout operation on the target general PID.
  • PID adjustment module specifically used for:
  • the usage attribute information determine whether a deletion operation needs to be performed on at least one general PID in the plurality of general PIDs;
  • the managed service system After the managed service system passes the identity authentication on the user identity information in the received service request, it will send the service request to the controller. After the controller receives the service request sent by the managed service system, it will determine the In the case that the user identity information does not have a corresponding dedicated PID, select an available general PID from a plurality of general PIDs preset in the controller, and use the general PID to perform service processing operations. That is, the present invention can use a plurality of pre-set general-purpose PIDs for business processing in a high-concurrency ticketing scenario, so that business requests do not need to be processed until there are available PIDs, and the business processing speed is improved.
  • the units involved in the embodiments of the present disclosure may be implemented in a software manner, and may also be implemented in a hardware manner.
  • the name of the unit does not constitute a limitation of the unit itself under certain circumstances, for example, the first obtaining unit may also be described as "a unit that obtains at least two Internet Protocol addresses".
  • exemplary types of hardware logic components include: Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), Systems on Chips (SOCs), Complex Programmable Logical Devices (CPLDs) and more.
  • FPGAs Field Programmable Gate Arrays
  • ASICs Application Specific Integrated Circuits
  • ASSPs Application Specific Standard Products
  • SOCs Systems on Chips
  • CPLDs Complex Programmable Logical Devices
  • An embodiment of the present invention provides a storage medium on which a program is stored, and when the program is executed by a processor, a method for processing the service request is implemented.
  • a machine-readable medium may be a tangible medium that may contain or store a program for use by or in connection with the instruction execution system, apparatus or device.
  • the machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium.
  • Machine-readable media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or devices, or any suitable combination of the foregoing.
  • machine-readable storage media would include one or more wire-based electrical connections, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), fiber optics, compact disk read only memory (CD-ROM), optical storage, magnetic storage, or any suitable combination of the foregoing.
  • RAM random access memory
  • ROM read only memory
  • EPROM or flash memory erasable programmable read only memory
  • CD-ROM compact disk read only memory
  • magnetic storage or any suitable combination of the foregoing.
  • the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the above two.
  • the computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or a combination of any of the above. More specific examples of computer readable storage media may include, but are not limited to, electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable Programmable read only memory (EPROM or flash memory), fiber optics, portable compact disk read only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.
  • a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.
  • a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with computer-readable program code embodied thereon. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • a computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device .
  • Program code embodied on a computer readable medium may be transmitted using any suitable medium including, but not limited to, electrical wire, optical fiber cable, RF (radio frequency), etc., or any suitable combination of the foregoing.
  • the above-mentioned computer-readable medium may be included in the above-mentioned electronic device; or may exist alone without being assembled into the electronic device.
  • the present application also provides a computer program product, which, when executed on a data processing device, is adapted to execute a program initialized with the above-mentioned steps of the processing method of the service request.
  • embodiments of the present disclosure include a computer program product comprising a computer program carried on a non-transitory computer readable medium, the computer program containing program code for performing the method illustrated in the flowchart.
  • the computer program may be downloaded and installed from the network via the communication device 609, or from the storage device 606, or from the ROM 602.
  • the processing apparatus 601 the above-mentioned functions defined in the methods of the embodiments of the present disclosure are executed.
  • another embodiment of the present invention provides an electronic device, wherein a plurality of general-purpose PIDs are preset in the electronic device;
  • the device includes: a memory and a processor;
  • the memory is used to store programs
  • the processor invokes the program and is used to:
  • the service request and the registration result are sent to the host of the reservation system, so that the host of the reservation system executes the service operation corresponding to the service request according to the registration result.
  • select an available general PID from the plurality of general PIDs and use it as the target general PID including:
  • the preset PID screening rule select a usable general PID from the plurality of general PIDs and use it as the general PID to be processed;
  • the method further includes:
  • the attribute information of the general PID to be processed determine whether the general PID to be processed is in an abnormal use state
  • the user identity information in the service request has a corresponding dedicated PID, it also includes:
  • the step of selecting an available general-purpose PID from the plurality of general-purpose PIDs as the target general-purpose PID is performed, and the steps are performed in sequence.
  • the method further includes:
  • a service successful execution message returned by the reservation system host after the service operation is successfully executed is received, and a host PID logout operation is performed on the target general PID.
  • the usage attribute information determine whether a deletion operation needs to be performed on at least one general PID in the plurality of general PIDs;
  • the managed service system After the managed service system passes the identity authentication on the user identity information in the received service request, it will send the service request to the controller. After the controller receives the service request sent by the managed service system, it will determine the In the case that the user identity information does not have a corresponding dedicated PID, select an available general PID from a plurality of general PIDs preset in the controller, and use the general PID to perform service processing operations. That is, the present invention can use multiple preset general-purpose PIDs for business processing in a high-concurrency ticketing scenario, so that business requests do not need to wait for usable PIDs to be processed, thereby improving business processing speed.
  • an embodiment of the present invention provides a service request processing method, which is applied to a controller, where a plurality of general-purpose PIDs are preset in the controller; the service request processing method includes: :
  • the service request and the registration result are sent to the host of the reservation system, so that the host of the reservation system executes the service operation corresponding to the service request according to the registration result.
  • select an available general PID from the plurality of general PIDs and use it as the target general PID including:
  • the preset PID screening rule select a usable general PID from the plurality of general PIDs and use it as the general PID to be processed;
  • the method further includes:
  • the attribute information of the general PID to be processed determine whether the general PID to be processed is in an abnormal use state
  • the user identity information in the service request has a corresponding dedicated PID, it also includes:
  • the step of selecting an available general-purpose PID from the plurality of general-purpose PIDs as the target general-purpose PID is performed, and the steps are performed in sequence.
  • the method further includes:
  • a service successful execution message returned by the reservation system host after the service operation is successfully executed is received, and a host PID logout operation is performed on the target general PID.
  • the usage attribute information determine whether a deletion operation needs to be performed on at least one general PID in the plurality of general PIDs;
  • an embodiment of the present invention provides an apparatus for processing a service request, which is applied to a controller.
  • the controller is preset with a plurality of general-purpose PIDs; the apparatus for processing a service request includes: :
  • a request receiving module configured to receive a business request sent by the hosting service system; the business request is sent by the hosting service system after the user identity information in the received business request is authenticated and passed;
  • a PID determination module configured to select a usable general PID from the plurality of general PIDs and use it as a target general PID when it is determined that the user identity information in the service request does not have a corresponding special PID;
  • a registration module for carrying out a host PID registration operation with the user identity information and the target general PID to obtain a registration result
  • the service execution module is configured to send the service request and the registration result to the host of the reservation system, so that the host of the reservation system executes the service operation corresponding to the service request according to the registration result.
  • the PID determination module includes:
  • the screening sequence submodule is used to select a usable general PID from the plurality of general PIDs according to the preset PID screening rule, and use it as the general PID to be processed;
  • a first state determination submodule configured to determine whether the to-be-processed general-purpose PID is in an unused state according to the attribute information of the to-be-processed general-purpose PID;
  • the first PID determination sub-module is configured to pass the PID with the to-be-processed PID as a target if it is in an unused state.
  • the PID determination module also includes:
  • a second state determination submodule configured to determine whether the to-be-processed general-purpose PID is in an abnormally-used state according to attribute information of the to-be-processed general-purpose PID when it is determined that the to-be-processed general-purpose PID is in a used state;
  • the second PID determination sub-module is configured to perform a host PID logout operation on the to-be-processed general PID to obtain a target general PID if it is in an abnormal use state.
  • an embodiment of the present invention provides an electronic device, wherein a plurality of general-purpose PIDs are preset in the electronic device; the electronic device includes: a memory and a processor;
  • the memory is used to store programs
  • the processor invokes the program and is used to:
  • the service request and the registration result are sent to the host of the reservation system, so that the host of the reservation system executes the service operation corresponding to the service request according to the registration result.

Abstract

本发明提供了一种业务请求的处理方法、装置及电子设备，托管服务系统在对接收的业务请求中的用户身份信息进行身份认证通过之后，会发送业务请求至控制器，控制器在接收到托管服务系统发送的业务请求之后，会在确定出用户身份信息没有对应的专用PID的情况下，从控制器中预先设定的多个通用PID中选择一个可使用的通用PID，并使用该通用PID进行业务处理操作。即通过本发明，能够在高并发购票场景下，使用预先设定的多个通用PID进行业务处理，使得业务请求不需要等到有可使用的PID时才会被处理，提高业务处理速度。

Description

一种业务请求的处理方法、装置及电子设备
本申请要求于2021年3月10日提交中国专利局、申请号为202110260495.1、发明名称为“一种业务请求的处理方法、装置及电子设备”的国内申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及业务请求处理领域，更具体的说，涉及一种业务请求的处理方法、装置及电子设备。
背景技术
PID为访问订座系统主机(USAS主机)时提供给用户服务的一种资源，数量有限。
用户在进行购票、退票等业务时，托管服务系统在对接收的业务请求中的用户身份信息验证通过之后，控制器会将该用户身份信息对应的PID以及业务请求发送至USAS主机，以使USAS主机执行该业务请求对应的业务。
在一些高并发业务场景，如促销活动场景下，发送业务请求的用户会显著增多，此时由于已有的PID的数量是有限的，业务请求需要等到有可使用的PID时才能够被处理，业务处理效率较低。
发明内容
提供该发明内容部分以便以简要的形式介绍构思，这些构思将在后面的具体实施方式部分被详细描述。该发明内容部分并不旨在标识要求保护的技术方案的关键特征或必要特征，也不旨在用于限制所要求的保护的技术方案的范围。
为解决上述技术问题，本发明采用了如下技术方案：
一种业务请求的处理方法，应用于控制器，所述控制器中预先设置有多个通用PID；所述业务请求处理方法包括：
接收托管服务系统发送的业务请求；所述业务请求是所述托管服务系统在对接收的业务请求中的用户身份信息进行身份认证通过之后发送的；
在确定出所述业务请求中的用户身份信息没有对应的专用PID的情况 下，从所述多个通用PID中选择一个可使用的通用PID，并作为目标通用PID；
将所述用户身份信息和所述目标通用PID进行主机PID注册操作，得到注册结果；
将所述业务请求和所述注册结果发送至订座系统主机，以使所述订座系统主机依据所述注册结果，执行与所述业务请求对应的业务操作。
一种业务请求的处理装置，应用于控制器，所述控制器中预先设置有多个通用PID；所述业务请求处理装置包括：
请求接收模块，用于接收托管服务系统发送的业务请求；所述业务请求是所述托管服务系统在对接收的业务请求中的用户身份信息进行身份认证通过之后发送的；
PID确定模块，用于在确定出所述业务请求中的用户身份信息没有对应的专用PID的情况下，从所述多个通用PID中选择一个可使用的通用PID，并作为目标通用PID；
注册模块，用于将所述用户身份信息和所述目标通用PID进行主机PID注册操作，得到注册结果；
业务执行模块，用于将所述业务请求和所述注册结果发送至订座系统主机，以使所述订座系统主机依据所述注册结果，执行与所述业务请求对应的业务操作。
一种电子设备，所述电子设备中预先设置有多个通用PID；所述电子设备包括：存储器和处理器；
其中，所述存储器用于存储程序；
处理器调用程序并用于：
接收托管服务系统发送的业务请求；所述业务请求是所述托管服务系统在对接收的业务请求中的用户身份信息进行身份认证通过之后发送的；
在确定出所述业务请求中的用户身份信息没有对应的专用PID的情况下，从所述多个通用PID中选择一个可使用的通用PID，并作为目标通用PID；
将所述用户身份信息和所述目标通用PID进行主机PID注册操作，得 到注册结果；
将所述业务请求和所述注册结果发送至订座系统主机，以使所述订座系统主机依据所述注册结果，执行与所述业务请求对应的业务操作。
相较于现有技术，本发明具有以下有益效果：
本发明提供了一种业务请求的处理方法、装置及电子设备，托管服务系统在对接收的业务请求中的用户身份信息进行身份认证通过之后，会发送业务请求至控制器，控制器在接收到托管服务系统发送的业务请求之后，会在确定出用户身份信息没有对应的专用PID的情况下，从控制器中预先设定的多个通用PID中选择一个可使用的通用PID，并使用该通用PID进行业务处理操作。即通过本发明，能够在高并发购票场景下，使用预先设定的多个通用PID进行业务处理，使得业务请求不需要等到有可使用的PID时才会被处理，提高业务处理速度。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本发明实施例提供的一种业务请求的处理方法的方法流程图；
图2为本发明实施例提供的另一种业务请求的处理方法的方法流程图；
图3为本发明实施例提供的再一种业务请求的处理方法的方法流程图；
图4为本发明实施例提供的一种业务请求的处理方法的场景示意图；
图5为本发明实施例提供的一种业务请求的处理方法的模块示意图；
图6为本发明实施例提供的一种业务请求的处理装置的结构示意图。
具体实施方式
下面将参照附图更详细地描述本公开的实施例。虽然附图中显示了本 公开的某些实施例，然而应当理解的是，本公开可以通过各种形式来实现，而且不应该被解释为限于这里阐述的实施例，相反提供这些实施例是为了更加透彻和完整地理解本公开。应当理解的是，本公开的附图及实施例仅用于示例性作用，并非用于限制本公开的保护范围。
本文使用的术语“包括”及其变形是开放性包括，即“包括但不限于”。术语“基于”是“至少部分地基于”。术语“一个实施例”表示“至少一个实施例”；术语“另一实施例”表示“至少一个另外的实施例”；术语“一些实施例”表示“至少一些实施例”。其他术语的相关定义将在下文描述中给出。
需要注意，本公开中提及的“第一”、“第二”等概念仅用于对不同的装置、模块或单元进行区分，并非用于限定这些装置、模块或单元所执行的功能的顺序或者相互依存关系。
需要注意，本公开中提及的“一个”、“多个”的修饰是示意性而非限制性的，本领域技术人员应当理解，除非在上下文另有明确指出，否则应该理解为“一个或多个”。
随着航空业的蓬勃发展，越来越多的旅客选择航空出行，旅客在大部分场景下，希望不再采用人工前往购票处现场询价购票的方式，而是希望可以在任何时候获得航司的库存信息并直接购票。同样，现场购票也会使得航司浪费大量的人力物力，会提高航司的成本，所以航司也在逐渐采用在线自动销售车票的方式。
对航空公司来说，随着业务的发展，航线网络扩张到遍布全国甚至全球，航空公司需要更多的销售管理人员能够登入航空系统进行销售管理和业务控制。
在现有的业务体系下，销售业务还需要使用USAS主机(之后简称主机)进行销售，按照现在的安全控制管理模式，很多场景下，主机的PID需要与相应的系统或人员使用的工作号的航司，权限，部门严格的一一对应，用户才可以登录到主机使用其绑定的PID进行销售或控制操作。也就是说，用户在使用USAS主机购票时，需要有对应的PID。其中，USAS主机是指航信的主机系统，提供了用户认证，各种航班数据，各种控制交易等功能。
然而，无论是对于航司的在线自动销售，或涉及航线管理员、营业部控制和销售人员的场景下，现有的主机PID与工作号的固定搭配的模式极大的限制了业务的进一步发展；
首先，根本性的限制来自主机，主机的PID数在架构设计上就是有限的，无法随意地，无限制地扩充PID的数量；而且，在现有管理体系下，PID的修改需要经过严谨的流程，需要较长的时间，多部门多环节的申请审批执行流程方可变更。
航司的销售存在着很大的灵活性，虽然从长期来看，业务量处于动态稳定的状态，但随着非商务等非确定性非强烈刚性需求的出行如休闲旅行等的加入，航司在销售模式加入了很多创新，必然造成临时决策进行促销活动等时刻，相关业务量有爆发式普遍增长，而在特定突发事件产生的情况下，指定的某项业务也可能有短时阶段性的增加。航司不得不面对业务高峰时有业务需求但业务开展受限于PID资源，若是在业务高峰来临之时，申请额外的PID资源，由于PID申请需要多部门多环节的审批，操作复杂，所需时间较长，可能会出现业务高峰来临了，但是PID仍未申请下来的情况，导致用户请求不能被及时处理。
为了解决在一些高并发业务场景的PID的问题，发明人经过研究发现，若是能够预先配置一些无状态的PID，然后在高并发场景下，对该无状态的PID进行注册操作，以保证PID能够正常进行业务操作，在业务操作完成之后，对PID进行注销操作，得到无状态的PID，这样可以保证在高并发业务场景下，及时调用无状态的PID进行业务处理。
具体的，托管服务系统在对接收的业务请求中的用户身份信息进行身份认证通过之后，会发送业务请求至控制器，控制器在接收到托管服务系统发送的业务请求之后，会在确定出用户身份信息没有对应的专用PID的情况下，从控制器中预先设定的多个通用PID中选择一个可使用的通用PID，并使用该通用PID进行业务处理操作。即通过本发明，能够在高并发购票场景下，使用预先设定的多个通用PID进行业务处理，使得业务请求不需要等到有可使用的PID时才会被处理，提高业务处理速度。
在上述内容的基础上，本发明实施例提供了一种业务请求的处理方法， 应用于控制器，此外，还可以应用于处理器、服务器等，本发明实施例不做要求。
所述控制器中预先设置有多个通用PID，通用PID也称为无状态PID，这些通用PID可以存储在控制器中的API PID连接池模块中，该模块提供了一系列的属于API(Application Programming Interface，应用程序编程接口)的动态PID的连接池，里面存储了大量的通用的专属于API的PID。这些PID可以被多个用户调用，且没有对应的专属用户。
参照图1，业务请求处理方法可以包括：
S11、接收托管服务系统发送的业务请求。
其中，所述业务请求是所述托管服务系统在对接收的业务请求中的用户身份信息进行身份认证通过之后发送的。
在实际应用中，用户会发送业务请求至SAT托管服务系统，业务请求中包括用户身份信息，如，登录名、密码等。SAT托管服务系统接收到该业务请求之后，会将该用户身份信息发送至IAM认证模块，IAM认证模块是第三方的账户身份认证模块，提供根据用户提交的身份信息确认属于该用户的IAM信息等功能。IAM认证模块对身份信息进行验证，得到验证结果。然后将该验证结果返回至SAT托管服务系统。
SAT托管服务系统在接收到该验证结果之后，会确定该验证结果是验证通过，还是验证未通过，若是验证通过，则将业务请求发送至控制器。若是验证未通过，则会给用户返回身份验证未通过信息，以使用户及时了解登陆情况。
S12、在确定出所述业务请求中的用户身份信息没有对应的专用PID的情况下，从所述多个通用PID中选择一个可使用的通用PID，并作为目标通用PID。
控制器接收到该业务请求之后，会从业务请求中获取到用户身份信息，然后确定该用户身份信息有没有对应的专用PID，一般情况下，控制器中会保存有每一用户身份信息对应的专用PID，控制器从保存的数据中，查询本次业务请求中的用户身份信息是否有对应的专用PID。
在实际应用中，PID在进行申请时，可以是按照航空公司进行分配的， 比如，为航空公司A分配10个PID，航空公司A中的员工共享这10个PID。为航空公司B分配20个PID，航空公司B中的员工共享这20个PID。
若控制器确定出该用户身份信息没有对应的专用PID的情况下，会从上述的连接池中选取一个可使用的通用PID。其中，可使用的是指，目标未被使用的，也即从连接池中选取出目前未被使用的通用PID，并作为目标通用PID。
本发明的另一实现方式中，步骤S12可以包括：
S21、按照预设PID筛选规则，从所述多个通用PID中选择一个可使用的通用PID，并作为待处理通用PID。
在实际应用中，预设PID筛选规则，可以是筛选序列号最小或最大的一个通用PID，又或者，随机筛选一个通用PID，作为待处理通用PID。
S22、确定所述待处理通用PID是否处于未被使用状态；若是，则执行步骤S23；若否，则执行步骤S24。
具体的，依据所述待处理通用PID的属性信息，确定所述待处理通用PID是否处于未被使用状态。
通用PID的属性信息可以有多种，如未被使用、异常使用、正常使用等。其中，未被使用是指当前该PID未被使用，异常使用是指该PID被使用的，但是由于网络不好等原因导致该PID未被成功注销，正常使用是指该PID正在被正常使用中。
进而可以获取到PID的属性信息，然后确定该属性信息是否是未被使用。
S23、将所述待处理PID作为目标通过PID。
具体的，若属性信息是未被使用，则该PID能够直接被使用，进而将所述待处理PID作为目标通过PID。
S24、确定所述待处理通用PID是否处于异常使用状态；若是，执行步骤S25。
具体的，也是依据所述待处理通用PID的属性信息，确定所述待处理通用PID是否处于异常使用状态。
获取到该属性信息，确定该属性信息是否是异常使用，若是，则确定 待处理通用PID处于异常使用状态。
S25、对所述待处理通用PID进行主机PID注销操作，得到目标通用PID。
具体的，进行主机PID注销操作即为执行SO操作，执行完SO操作后的PID，即为目标通用PID。
S13、将所述用户身份信息和所述目标通用PID进行主机PID注册操作，得到注册结果。
具体的，进行主机PID注册操作，即进行SI注册操作，将所述用户身份信息和所述目标通用PID进行SI注册操作，得到注册结果。其中，进行了SI注册操作的PID就可以处理业务。
需要说明的是，控制器中设置有APIPIDSignedIN模块：该模块用于对API PID连接池中的PID进行注册(SI)的工作，对API PID连接池中的PID进行身份的更改。
此外，控制器中设置有APIPIDSignedOUT模块:该模块用于对API PID连接池中的PID进行注消(S0)工作，注销之后的PID又变为无属性的通用的PID。
S14、将所述业务请求和所述注册结果发送至订座系统主机，以使所述订座系统主机依据所述注册结果，执行与所述业务请求对应的业务操作。
在得到注册结果之后，就可以将所述业务请求和所述注册结果发送至订座系统主机，即上述的USAS主机。USAS主机依据所述注册结果，执行与所述业务请求对应的业务操作。
在USAS主机成功执行业务操作之后，会返回业务成功执行消息至本实施例中的控制器，控制器在接收到所述订座系统主机在成功执行业务操作之后返回的业务成功执行消息之后，对所述目标通用PID执行主机PID注销操作，即SO操作，执行完SO操作的PID又变成了无状态，即通用PID，把该通用PID放入到上述的连接池，共下次使用。
上述实施例介绍的是，在确定出所述业务请求中的用户身份信息没有对应的专用PID的情况下，如何使用连接池中的通用PID进行业务处理。此外，在确定出所述业务请求中的用户身份信息有对应的专用PID的情况 下，也可能会存在PID不够使用的情况，此时也会去连接池中获取通用PID。
具体的，在确定出所述业务请求中的用户身份信息有对应的专用PID的情况下，还包括：判断所述用户身份信息对应的专用PID是否均被使用，若是，则执行从所述多个通用PID中选择一个可使用的通用PID，并作为目标通用PID的步骤，并顺序执行。
在实际应用中，为航空公司分配了专用PID之后，航空公司中的用户共享使用该专用PID，比如A用户使用一个专用PID，B用户使用另一个专用PID……，以此类推。假设为该航空公司分配了10个专用PID，该航空公司中已经有10个人使用了这10个专用PID，则第11个员工想要使用专用PID时，就无可使用的专用PID，此时可以从连接池中选取一个通用PID来使用。具体的，在确定出用户身份信息对应的专用PID均被使用时，执行从所述多个通用PID中选择一个可使用的通用PID，并作为目标通用PID的步骤，并执行步骤S13-S14。
本实施例中，托管服务系统在对接收的业务请求中的用户身份信息进行身份认证通过之后，会发送业务请求至控制器，控制器在接收到托管服务系统发送的业务请求之后，会在确定出用户身份信息没有对应的专用PID的情况下，从控制器中预先设定的多个通用PID中选择一个可使用的通用PID，并使用该通用PID进行业务处理操作。即通过本发明，能够在高并发购票场景下，使用预先设定的多个通用PID进行业务处理，使得业务请求不需要等到有可使用的PID时才会被处理，提高业务处理速度。
上述实施例介绍了，在无专用PID或者是专用PID不够用的情况下，可以从上述的连接池中选取通用PID来进行业务处理。那么连接池的通用PID的数量则需要根据其使用情况进行调整，以动态使用PID的使用场景。
具体的，参照图3，还包括：
S31、确定多个通用PID的使用属性信息。
具体的，使用属性信息可以是同一时间使用的通用PID的数量，PID的使用频率等等。如，同一时间PID同时使用的数量是30个、50个、150个等。
使用频率可以是每隔5分钟使用一次，每隔20分钟使用一次等。
S32、确定是否需要对所述多个通用PID中的至少一个通用PID进行删除操作；若是，则执行步骤S33，若否，则执行步骤S34。
具体的，依据所述使用属性信息，确定是否需要对所述多个通用PID中的至少一个通用PID进行删除操作。
在实际应用中，假设一共有200个通用PID，同一时间PID同时使用的数量是30个，使用频率是每隔20分钟使用一次，由此可知，连接池中设置的通用PID中有较多的PID不能被经常使用，也即设置的通用PID的数量较多，此时可以删除些通用PID，以避免通用PID占据较大的内存。
S33、对所述多个通用PID中的至少一个通用PID进行删除操作。
具体的，在进行删除时，可以确定删除的数量，比如，删除百分之五等等。具体删除的数量可以依据通用PID的使用情况来定。在实际删除时，可以依据预先设定的删除规则确定删除数量。删除规则可以是依据使用频率来定，或者是依据同一时间使用的PID的数量来定，或者是同时依据使用频率和数量来定。
S34、确定是否需要创建新的通用PID；若是，执行步骤S35。
具体的，依据所述使用属性信息，确定是否需要创建新的通用PID。
在实际应用中，假设一共有200个通用PID，同一时间PID同时使用的数量是180个，使用频率是每隔4分钟使用一次，由此可知，连接池中设置的通用PID中有较多的PID被经常使用，也即设置的通用PID的数量一般，此时可以增加些通用PID，以保证业务量突增时，通用PID不够用的情况。
S35、创建新的通用PID。
具体的，在进行创建时，可以确定创建的数量，比如，创建百分之五等等。具体创建的数量可以依据通用PID的使用情况来定。在实际创建时，可以依据预先设定的创建规则确定创建数量。创建规则可以是依据使用频率来定，或者是依据同一时间使用的PID的数量来定，或者是同时依据使用频率和数量来定。
本实施例中，能够根据连接池中的通用PID的使用情况，来动态调整连接池中的PID的数量，更加适用于PID的使用情况。
为了本领域技术人员能够更加清楚的了解本发明的实现过程，现给出图4，图4给出了具体实现过程，具体的：
步骤1：IAM用户身份认证。当用户发起请求的时候，首先IAM模块会根据用户的身份信息进行验证，并获取到对应于该用户的其他信息，比如AgentNo号，level等级等信息。
步骤2：获取API PID连接池中的PID。根据此时访问API的用户身份，识别其是否有自己专用的PID，如果有的话，并且专用PID并没有被占用的话，优先使用专用的PID,若没有专用的PID或者专用的PID被占用，此时就会申请API通用PID。
步骤3：API PID账号注册或注销操作。首先判断动态API PID池中获取的PID的状态，若是该PID因为某种原因并没有被执行SO操作的话，会首先进行SO操作，使PID变为无状态的PID，执行完SO操作后即进行SI操作。如果获取到的PID本身就是无状态的PID的话，会根据从IAM认证信息中获取到的信息和PID一起进行SI注册操作。
步骤4：访问USAS主机。利用SI后的PID和身份信息、业务请求一起访问USAS主机。
步骤5：API PID账号注销操作。对执行完访问USAU主机功能后的API PID执行SO操作，使其变为无状态的API PID，并将其回收到动态API PID连接池中。
本发明实施例通过设置API通用PID连接池，使得用户在促销销售阶段或者需要高并发访问USAS主机系统时，能够不受PID数量少的限制，让用户减少周期长的PID申请流程，只关注系统的服务能力而不关注PID的数量是否能够满足使用，提升航信对航空公司和代理人的服务能力。
参照图5，本发明涉及下述五个模块，具体解释如下：
USAS主机模块：该模块就是指航信的主机系统，提供了用户认证，各种航班数据，各种控制交易等功能。
IAM认证模块：该模块是第三方的账户身份认证模块，提供根据用户提交的身份信息确认属于该用户的IAM信息等功能。
API PID连接池模块：该模块提供了一系列的属于API的动态PID的 连接池，里面存储了大量的通用的专属于API的PID。
APIPIDSignedIN模块：该模块用于对APIPID连接池中的PID进行注册的工作，对APIPID连接池中的PID进行身份的更改。
APIPIDSignedOUT模块:该模块用于对API PID连接池中的PID进行注消工作，注销之后的PID又变为无属性的通用的PID。
上述的USAS主机模块是最终的提供通用意义上的查询，订票，改签，退票等操作的模块，用户与该模块的连接是需要USAS主机专用的PID号，PID号起到的作用是分类用户的身份和权限的控制，根据访问USAS主机的用户身份的不同，提供不同的权限和后台的数据。IAM认证模块是提供了一种USAS主机模块认可的一种身份信息认证方法，API可以使用IAM认证过的身份和相应的权限访问USAS主机模块，IAM认证后的会提供用户，角色，权限等信息，该信息是USAS主机模块认可的，API用户即可用这些身份去访问USAS主机系统。APIPID连接池模块是提供了供用户使用的无差别的通用无状态的PID，该PID的大小范围由USAS主机模块事先规定提供好，专用API使用。一个原则就是如果用户有专用PID的话，会优先使用专用PID，没有的话，再去使用API通用PID，该模块还会动态的根据用户的并发数扩充并配置PID，直至满足高并发下访问的要求，在高并发后趋于正常后，长时间空闲的PID会回收，以便再次复用并供其他用户使用。API通用PID连接池中的PID是常连接的，并且会保证连接池中的正常的PID的工作状态，自动隔离连接/配置失败的PID并向外提供报警。APIPIDSignedIN模块用于配置API通用PID连接池中的PID，从配置库中获取eterm配置并登录得到PID，得到PID后，从IAM获取到SI需要的信息，如AGENT NUMBER/USER Group/OFFICE/AIRLINE，在此PID上执行SI的操作，进行PID的配置注册，SI成功即为配置成功，用户即可通过此PID访问USAS主机模块。APIPIDSignedOUT模块用于对已经配置注册完的，并且使用结束了的API通用PID执行解除通用PID的用户属性配置，它的功能就是解除通用PID与具体API用户属性的关联，他只执行必要的检查，比如已经所有的RT均已经执行了IG,未建控打票机，已经回滚了所有需要回滚的交易等。SO后的通用PID会放回连接池中，还可以按照SI注册配 置的方式，再次配置为其他用户的身份属性继续使用，实现了PID无限循环使用。
在真正的使用中，当航司用户或者代理人需要大量使用PID的时候，用户访问IBE的并发量就会上升，并发量一上升带来的最直观的需求就是需要的PID数会突增；当IBE(Internet Booking Engine，中国航信互联网订座引擎)端在接受到这么多的请求下，会动态的从APIPID连接池中获取到更多的无差别的通用API PID给用户用，每一个API PID连接池中的PID在被确认会被用户使用时，都会在APIPIDSignedIN模块中进行检查，如果该PID没有被注销的话，会在APIPIDSignedOUT模块中进行注销的操作，也即SO操作。执行完SO操作后，会执行SI操作，SI操作的功能是为该PID赋予一个合理的经过IAM认证的能够被USAS主机模块认可的身份信息，执行完SI操作之后，用户即可用该PID去USAS主机模块中获取需要的数据或做权限允许下交易。当这次用户的请求结束或者该次交易长期处于无响应状态下，该PID会被执行归还操作，也就是执行SO操作。
具体举例说明下动态配置PID的过程。假如一个航司用户调用IBE的接口，用到的身份信息是casatn1,pek069，此航司用户是没有专属的PID号。当IBE获取到用户的身份后，会调用SAT托管服务中相对应的接口，SAT去根据用户的casatn1和pek069去做IAM认证，从IAM认证中获取到属于casatn1,pek069的其他信息，比如AGENTNO为36751，level为41等信息；由于该航司用户没有专属的PID号，需要从APIPID连接中获取到无状态的PID，假如此时APIPID连接池中有多个PID，如14598，23569，87965，23568等，此时会根据PID的状态会有两种情况，假如获取到的PID号是23569,如果23569该PID在上一次的连接USAS主机后由于创建连接USAS主机失败或者突然中断等意外原因，导致该PID不能正常的执行SO操作的话，会首先对该PID号23569进行SO操作，SO操作成功后根据IAM认证获取到的身份信息和PID号一起执行SI操作，这就把该PID号和该用户的IAM身份信息进行了绑定，如果获取到的APIPID号23569本身就是无状态的PID的话，即可直接进行SI操作，把PID号23569和IAM认证获取到的身份信息进行绑定，SAT即可利用该PID进行USAS主机的访问，执行 用户想要执行的操作；完整的执行完主机操作后，主机会对该PID执行SO操作，使其变为无状态的PID，并回收到动态APIPID连接池中。
本发明是针对USAS主机模块的本身系统限制下的PID数量少，申请、删除周期长的，固定PID池资源分配不均衡的缺点，制定了一种可业务请求的处理方法。通过提出“API通用PID”的概念，实现从固定的PID段中分配出PID用于动态的配置API通用PID提供给用户使用，以便在需要高并发的条件下，能够轻松的应对PID数不确定的增长带来的服务响应慢等问题。通过这种方案，可以实现放大现有PID的使用能力，对用户是无感的，用户只需设置促销等业务即可，方便且灵活。
附图中的流程图和框图，图示了按照本公开各种实施例的系统、方法和计算机程序产品的可能实现的体系架构、功能和操作。在这点上，流程图或框图中的每个方框可以代表一个模块、程序段、或代码的一部分，该模块、程序段、或代码的一部分包含一个或多个用于实现规定的逻辑功能的可执行指令。也应当注意，在有些作为替换的实现中，方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如，两个接连地表示的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行，这依所涉及的功能而定。也要注意的是，框图和/或流程图中的每个方框、以及框图和/或流程图中的方框的组合，可以用执行规定的功能或操作的专用的基于硬件的系统来实现，或者可以用专用硬件与计算机指令的组合来实现。
本公开实施方式中的多个装置之间所交互的消息或者信息的名称仅用于说明性的目的，而并不是用于对这些消息或信息的范围进行限制。
虽然采用特定次序描绘了各操作，但是这不应当理解为要求这些操作以所示出的特定次序或以顺序次序执行来执行。在一定环境下，多任务和并行处理可能是有利的。
应当理解，本公开的方法实施方式中记载的各个步骤可以按照不同的顺序执行，和/或并行执行。此外，方法实施方式可以包括附加的步骤和/或省略执行示出的步骤。本公开的范围在此方面不受限制。
可以以一种或多种程序设计语言或其组合来编写用于执行本公开的操 作的计算机程序代码，上述程序设计语言包括但不限于面向对象的程序设计语言—诸如Java、Smalltalk、C++，还包括常规的过程式程序设计语言—诸如“C”语言或类似的程序设计语言。程序代码可以完全地在用户计算机上执行、部分地在用户计算机上执行、作为一个独立的软件包执行、部分在用户计算机上部分在远程计算机上执行、或者完全在远程计算机或服务器上执行。在涉及远程计算机的情形中，远程计算机可以通过任意种类的网络——包括局域网(LAN)或广域网(WAN)—连接到用户计算机，或者，可以连接到外部计算机(例如利用因特网服务提供商来通过因特网连接)。
可选地，在上述业务请求的处理方法的实施例的基础上，本发明的另一实施例提供了一种业务请求的处理装置，应用于控制器，所述控制器中预先设置有多个通用PID；参照图6，所述业务请求处理装置包括：
请求接收模块11，用于接收托管服务系统发送的业务请求；所述业务请求是所述托管服务系统在对接收的业务请求中的用户身份信息进行身份认证通过之后发送的；
PID确定模块12，用于在确定出所述业务请求中的用户身份信息没有对应的专用PID的情况下，从所述多个通用PID中选择一个可使用的通用PID，并作为目标通用PID；
注册模块13，用于将所述用户身份信息和所述目标通用PID进行主机PID注册操作，得到注册结果；
业务执行模块14，用于将所述业务请求和所述注册结果发送至订座系统主机，以使所述订座系统主机依据所述注册结果，执行与所述业务请求对应的业务操作。
进一步，所述PID确定模块包括：
筛序子模块，用于按照预设PID筛选规则，从所述多个通用PID中选择一个可使用的通用PID，并作为待处理通用PID；
第一状态确定子模块，用于依据所述待处理通用PID的属性信息，确定所述待处理通用PID是否处于未被使用状态；
第一PID确定子模块，用于若是处于未被使用状态，则将所述待处理PID作为目标通过PID。
进一步，所述PID确定模块还包括：
第二状态确定子模块，用于在确定出所述待处理通用PID处于被使用状态的情况下，依据所述待处理通用PID的属性信息，确定所述待处理通用PID是否处于异常使用状态；
第二PID确定子模块，用于若是处于异常使用状态，则对所述待处理通用PID进行主机PID注销操作，得到目标通用PID。
进一步，还包括：
PID使用确定模块，用于在确定出所述业务请求中的用户身份信息有对应的专用PID的情况下，判断所述用户身份信息对应的专用PID是否均被使用；
所述PID确定模块，还用于在PID使用确定模块判断所述用户身份信息对应的专用PID均被使用的情况下，从所述多个通用PID中选择一个可使用的通用PID，并作为目标通用PID。
进一步，还包括：
注销操作模块，用于接收所述订座系统主机在成功执行业务操作之后返回的业务成功执行消息，并对所述目标通用PID执行主机PID注销操作。
进一步，还包括PID调整模块，所述PID调整模块具体用于：
确定所述多个通用PID的使用属性信息；
依据所述使用属性信息，确定是否需要对所述多个通用PID中的至少一个通用PID进行删除操作；
若是，则对所述多个通用PID中的至少一个通用PID进行删除操作；
若否，依据所述使用属性信息，确定是否需要创建新的通用PID；
若是，则创建新的通用PID。
本实施例中，托管服务系统在对接收的业务请求中的用户身份信息进行身份认证通过之后，会发送业务请求至控制器，控制器在接收到托管服务系统发送的业务请求之后，会在确定出用户身份信息没有对应的专用PID的情况下，从控制器中预先设定的多个通用PID中选择一个可使用的通用PID，并使用该通用PID进行业务处理操作。即通过本发明，能够在高并发购票场景下，使用预先设定的多个通用PID进行业务处理，使得业务请求不 需要等到有可使用的PID时才会被处理，提高业务处理速度。
需要说明的是，本实施例中的各个模块和子模块的工作过程，请参照上述实施例中的相应说明，在此不再赘述。
描述于本公开实施例中所涉及到的单元可以通过软件的方式实现，也可以通过硬件的方式来实现。其中，单元的名称在某种情况下并不构成对该单元本身的限定，例如，第一获取单元还可以被描述为“获取至少两个网际协议地址的单元”。
本文中以上描述的功能可以至少部分地由一个或多个硬件逻辑部件来执行。例如，非限制性地，可以使用的示范类型的硬件逻辑部件包括：现场可编程门阵列(FPGA)、专用集成电路(ASIC)、专用标准产品(ASSP)、片上系统(SOC)、复杂可编程逻辑设备(CPLD)等等。
本发明实施例提供了一种存储介质，其上存储有程序，该程序被处理器执行时实现所述业务请求的处理方法。
在本公开的上下文中，机器可读介质可以是有形的介质，其可以包含或存储以供指令执行系统、装置或设备使用或与指令执行系统、装置或设备结合地使用的程序。机器可读介质可以是机器可读信号介质或机器可读储存介质。机器可读介质可以包括但不限于电子的、磁性的、光学的、电磁的、红外的、或半导体系统、装置或设备，或者上述内容的任何合适组合。机器可读存储介质的更具体示例会包括基于一个或多个线的电气连接、便携式计算机盘、硬盘、随机存取存储器(RAM)、只读存储器(ROM)、可擦除可编程只读存储器(EPROM或快闪存储器)、光纤、便捷式紧凑盘只读存储器(CD-ROM)、光学储存设备、磁储存设备、或上述内容的任何合适组合。
需要说明的是，本公开上述的计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质或者是上述两者的任意组合。计算机可读存储介质例如可以是——但不限于——电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。计算机可读存储介质的更具体的例子可以包括但不限于：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机访问存储器(RAM)、只读存储器(ROM)、可擦式可 编程只读存储器(EPROM或闪存)、光纤、便携式紧凑磁盘只读存储器(CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。在本公开中，计算机可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。而在本公开中，计算机可读信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了计算机可读的程序代码。这种传播的数据信号可以采用多种形式，包括但不限于电磁信号、光信号或上述的任意合适的组合。计算机可读信号介质还可以是计算机可读存储介质以外的任何计算机可读介质，该计算机可读信号介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。计算机可读介质上包含的程序代码可以用任何适当的介质传输，包括但不限于：电线、光缆、RF(射频)等等，或者上述的任意合适的组合。
上述计算机可读介质可以是上述电子设备中所包含的；也可以是单独存在，而未装配入该电子设备中。
本申请还提供了一种计算机程序产品，当在数据处理设备上执行时，适于执行初始化有上述的业务请求的处理方法步骤的程序。
特别地，根据本公开的实施例，上文参考流程图描述的过程可以被实现为计算机软件程序。例如，本公开的实施例包括一种计算机程序产品，其包括承载在非暂态计算机可读介质上的计算机程序，该计算机程序包含用于执行流程图所示的方法的程序代码。在这样的实施例中，该计算机程序可以通过通信装置609从网络上被下载和安装，或者从存储装置606被安装，或者从ROM 602被安装。在该计算机程序被处理装置601执行时，执行本公开实施例的方法中限定的上述功能。
可选地，在上述业务请求的处理方法及装置的实施例的基础上，本发明的另一实施例提供了一种电子设备，所述电子设备中预先设置有多个通用PID；所述电子设备包括：存储器和处理器；
其中，所述存储器用于存储程序；
处理器调用程序并用于：
接收托管服务系统发送的业务请求；所述业务请求是所述托管服务系 统在对接收的业务请求中的用户身份信息进行身份认证通过之后发送的；
在确定出所述业务请求中的用户身份信息没有对应的专用PID的情况下，从所述多个通用PID中选择一个可使用的通用PID，并作为目标通用PID；
将所述用户身份信息和所述目标通用PID进行主机PID注册操作，得到注册结果；
将所述业务请求和所述注册结果发送至订座系统主机，以使所述订座系统主机依据所述注册结果，执行与所述业务请求对应的业务操作。
进一步，从所述多个通用PID中选择一个可使用的通用PID，并作为目标通用PID，包括：
按照预设PID筛选规则，从所述多个通用PID中选择一个可使用的通用PID，并作为待处理通用PID；
依据所述待处理通用PID的属性信息，确定所述待处理通用PID是否处于未被使用状态；
若是，则将所述待处理PID作为目标通过PID。
进一步，在确定出所述待处理通用PID处于被使用状态的情况下，还包括：
依据所述待处理通用PID的属性信息，确定所述待处理通用PID是否处于异常使用状态；
若是，则对所述待处理通用PID进行主机PID注销操作，得到目标通用PID。
进一步，在确定出所述业务请求中的用户身份信息有对应的专用PID的情况下，还包括：
判断所述用户身份信息对应的专用PID是否均被使用；
若是，则执行从所述多个通用PID中选择一个可使用的通用PID，并作为目标通用PID的步骤，并顺序执行。
进一步，在将所述业务请求和所述注册结果发送至订座系统主机之后，还包括：
接收所述订座系统主机在成功执行业务操作之后返回的业务成功执行 消息，并对所述目标通用PID执行主机PID注销操作。
进一步，还包括：
确定所述多个通用PID的使用属性信息；
依据所述使用属性信息，确定是否需要对所述多个通用PID中的至少一个通用PID进行删除操作；
若是，则对所述多个通用PID中的至少一个通用PID进行删除操作；
若否，依据所述使用属性信息，确定是否需要创建新的通用PID；
若是，则创建新的通用PID。
本实施例中，托管服务系统在对接收的业务请求中的用户身份信息进行身份认证通过之后，会发送业务请求至控制器，控制器在接收到托管服务系统发送的业务请求之后，会在确定出用户身份信息没有对应的专用PID的情况下，从控制器中预先设定的多个通用PID中选择一个可使用的通用PID，并使用该通用PID进行业务处理操作。即通过本发明，能够在高并发购票场景下，使用预先设定的多个通用PID进行业务处理，使得业务请求不需要等到有可使用的PID时才会被处理，提高业务处理速度。
根据本公开的一个或多个实施例，本发明实施例提供了一种业务请求的处理方法，应用于控制器，所述控制器中预先设置有多个通用PID；所述业务请求处理方法包括：
接收托管服务系统发送的业务请求；所述业务请求是所述托管服务系统在对接收的业务请求中的用户身份信息进行身份认证通过之后发送的；
在确定出所述业务请求中的用户身份信息没有对应的专用PID的情况下，从所述多个通用PID中选择一个可使用的通用PID，并作为目标通用PID；
将所述用户身份信息和所述目标通用PID进行主机PID注册操作，得到注册结果；
将所述业务请求和所述注册结果发送至订座系统主机，以使所述订座系统主机依据所述注册结果，执行与所述业务请求对应的业务操作。
进一步，从所述多个通用PID中选择一个可使用的通用PID，并作为目标通用PID，包括：
按照预设PID筛选规则，从所述多个通用PID中选择一个可使用的通用PID，并作为待处理通用PID；
依据所述待处理通用PID的属性信息，确定所述待处理通用PID是否处于未被使用状态；
若是，则将所述待处理PID作为目标通过PID。
进一步，在确定出所述待处理通用PID处于被使用状态的情况下，还包括：
依据所述待处理通用PID的属性信息，确定所述待处理通用PID是否处于异常使用状态；
若是，则对所述待处理通用PID进行主机PID注销操作，得到目标通用PID。
进一步，在确定出所述业务请求中的用户身份信息有对应的专用PID的情况下，还包括：
判断所述用户身份信息对应的专用PID是否均被使用；
若是，则执行从所述多个通用PID中选择一个可使用的通用PID，并作为目标通用PID的步骤，并顺序执行。
进一步，在将所述业务请求和所述注册结果发送至订座系统主机之后，还包括：
接收所述订座系统主机在成功执行业务操作之后返回的业务成功执行消息，并对所述目标通用PID执行主机PID注销操作。
进一步，还包括：
确定所述多个通用PID的使用属性信息；
依据所述使用属性信息，确定是否需要对所述多个通用PID中的至少一个通用PID进行删除操作；
若是，则对所述多个通用PID中的至少一个通用PID进行删除操作；
若否，依据所述使用属性信息，确定是否需要创建新的通用PID；
若是，则创建新的通用PID。
根据本公开的一个或多个实施例，本发明实施例提供了一种业务请求的处理装置，应用于控制器，所述控制器中预先设置有多个通用PID；所 述业务请求处理装置包括：
请求接收模块，用于接收托管服务系统发送的业务请求；所述业务请求是所述托管服务系统在对接收的业务请求中的用户身份信息进行身份认证通过之后发送的；
PID确定模块，用于在确定出所述业务请求中的用户身份信息没有对应的专用PID的情况下，从所述多个通用PID中选择一个可使用的通用PID，并作为目标通用PID；
注册模块，用于将所述用户身份信息和所述目标通用PID进行主机PID注册操作，得到注册结果；
业务执行模块，用于将所述业务请求和所述注册结果发送至订座系统主机，以使所述订座系统主机依据所述注册结果，执行与所述业务请求对应的业务操作。
进一步，所述PID确定模块包括：
筛序子模块，用于按照预设PID筛选规则，从所述多个通用PID中选择一个可使用的通用PID，并作为待处理通用PID；
第一状态确定子模块，用于依据所述待处理通用PID的属性信息，确定所述待处理通用PID是否处于未被使用状态；
第一PID确定子模块，用于若是处于未被使用状态，则将所述待处理PID作为目标通过PID。
进一步，所述PID确定模块还包括：
第二状态确定子模块，用于在确定出所述待处理通用PID处于被使用状态的情况下，依据所述待处理通用PID的属性信息，确定所述待处理通用PID是否处于异常使用状态；
第二PID确定子模块，用于若是处于异常使用状态，则对所述待处理通用PID进行主机PID注销操作，得到目标通用PID。
根据本公开的一个或多个实施例，本发明实施例提供了一种电子设备，所述电子设备中预先设置有多个通用PID；所述电子设备包括：存储器和处理器；
其中，所述存储器用于存储程序；
处理器调用程序并用于：
接收托管服务系统发送的业务请求；所述业务请求是所述托管服务系统在对接收的业务请求中的用户身份信息进行身份认证通过之后发送的；
在确定出所述业务请求中的用户身份信息没有对应的专用PID的情况下，从所述多个通用PID中选择一个可使用的通用PID，并作为目标通用PID；
将所述用户身份信息和所述目标通用PID进行主机PID注册操作，得到注册结果；
将所述业务请求和所述注册结果发送至订座系统主机，以使所述订座系统主机依据所述注册结果，执行与所述业务请求对应的业务操作。
尽管已经采用特定于结构特征和/或方法逻辑动作的语言描述了本主题，但是应当理解所附权利要求书中所限定的主题未必局限于上面描述的特定特征或动作。相反，上面所描述的特定特征和动作仅仅是实现权利要求书的示例形式。
虽然在上面论述中包含了若干具体实现细节，但是这些不应当被解释为对本公开的范围的限制。在单独的实施例的上下文中描述的某些特征还可以组合地实现在单个实施例中。相反地，在单个实施例的上下文中描述的各种特征也可以单独地或以任何合适的子组合的方式实现在多个实施例中。
以上描述仅为本公开的较佳实施例以及对所运用技术原理的说明。本领域技术人员应当理解，本公开中所涉及的公开范围，并不限于上述技术特征的特定组合而成的技术方案，同时也应涵盖在不脱离上述公开构思的情况下，由上述技术特征或其等同特征进行任意组合而形成的其它技术方案。例如上述特征与本公开中公开的(但不限于)具有类似功能的技术特征进行互相替换而形成的技术方案。
对所公开的实施例的上述说明，使本领域专业技术人员能够实现或使用本发明。对这些实施例的多种修改对本领域的专业技术人员来说将是显而易见的，本文中所定义的一般原理可以在不脱离本发明的精神或范围的情况下，在其它实施例中实现。因此，本发明将不会被限制于本文所示的 这些实施例，而是要符合与本文所公开的原理和新颖特点相一致的最宽的范围。

Claims (10)

  1. 一种业务请求的处理方法，其特征在于，应用于控制器，所述控制器中预先设置有多个通用PID；所述业务请求处理方法包括：
    接收托管服务系统发送的业务请求；所述业务请求是所述托管服务系统在对接收的业务请求中的用户身份信息进行身份认证通过之后发送的；
    在确定出所述业务请求中的用户身份信息没有对应的专用PID的情况下，从所述多个通用PID中选择一个可使用的通用PID，并作为目标通用PID；
    将所述用户身份信息和所述目标通用PID进行主机PID注册操作，得到注册结果；
    将所述业务请求和所述注册结果发送至订座系统主机，以使所述订座系统主机依据所述注册结果，执行与所述业务请求对应的业务操作。
  2. 根据权利要求1所述的处理方法，其特征在于，从所述多个通用PID中选择一个可使用的通用PID，并作为目标通用PID，包括：
    按照预设PID筛选规则，从所述多个通用PID中选择一个可使用的通用PID，并作为待处理通用PID；
    依据所述待处理通用PID的属性信息，确定所述待处理通用PID是否处于未被使用状态；
    若是，则将所述待处理PID作为目标通过PID。
  3. 根据权利要求2所述的处理方法，其特征在于，在确定出所述待处理通用PID处于被使用状态的情况下，还包括：
    依据所述待处理通用PID的属性信息，确定所述待处理通用PID是否处于异常使用状态；
    若是，则对所述待处理通用PID进行主机PID注销操作，得到目标通用PID。
  4. 根据权利要求1所述的处理方法，其特征在于，在确定出所述业务请求中的用户身份信息有对应的专用PID的情况下，还包括：
    判断所述用户身份信息对应的专用PID是否均被使用；
    若是，则执行从所述多个通用PID中选择一个可使用的通用PID，并作为目标通用PID的步骤，并顺序执行。
  5. 根据权利要求1所述的处理方法，其特征在于，在将所述业务请求和所述注册结果发送至订座系统主机之后，还包括：
    接收所述订座系统主机在成功执行业务操作之后返回的业务成功执行消息，并对所述目标通用PID执行主机PID注销操作。
  6. 根据权利要求1所述的处理方法，其特征在于，还包括：
    确定所述多个通用PID的使用属性信息；
    依据所述使用属性信息，确定是否需要对所述多个通用PID中的至少一个通用PID进行删除操作；
    若是，则对所述多个通用PID中的至少一个通用PID进行删除操作；
    若否，依据所述使用属性信息，确定是否需要创建新的通用PID；
    若是，则创建新的通用PID。
  7. 一种业务请求的处理装置，其特征在于，应用于控制器，所述控制器中预先设置有多个通用PID；所述业务请求处理装置包括：
    请求接收模块，用于接收托管服务系统发送的业务请求；所述业务请求是所述托管服务系统在对接收的业务请求中的用户身份信息进行身份认证通过之后发送的；
    PID确定模块，用于在确定出所述业务请求中的用户身份信息没有对应的专用PID的情况下，从所述多个通用PID中选择一个可使用的通用PID，并作为目标通用PID；
    注册模块，用于将所述用户身份信息和所述目标通用PID进行主机PID注册操作，得到注册结果；
    业务执行模块，用于将所述业务请求和所述注册结果发送至订座系统主机，以使所述订座系统主机依据所述注册结果，执行与所述业务请求对应的业务操作。
  8. 根据权利要求7所述的处理装置，其特征在于，所述PID确定模块包括：
    筛序子模块，用于按照预设PID筛选规则，从所述多个通用PID中选 择一个可使用的通用PID，并作为待处理通用PID；
    第一状态确定子模块，用于依据所述待处理通用PID的属性信息，确定所述待处理通用PID是否处于未被使用状态；
    第一PID确定子模块，用于若是处于未被使用状态，则将所述待处理PID作为目标通过PID。
  9. 根据权利要求8所述的处理装置，其特征在于，所述PID确定模块还包括：
    第二状态确定子模块，用于在确定出所述待处理通用PID处于被使用状态的情况下，依据所述待处理通用PID的属性信息，确定所述待处理通用PID是否处于异常使用状态；
    第二PID确定子模块，用于若是处于异常使用状态，则对所述待处理通用PID进行主机PID注销操作，得到目标通用PID。
  10. 一种电子设备，其特征在于，所述电子设备中预先设置有多个通用PID；所述电子设备包括：存储器和处理器；
    其中，所述存储器用于存储程序；
    处理器调用程序并用于：
    接收托管服务系统发送的业务请求；所述业务请求是所述托管服务系统在对接收的业务请求中的用户身份信息进行身份认证通过之后发送的；
    在确定出所述业务请求中的用户身份信息没有对应的专用PID的情况下，从所述多个通用PID中选择一个可使用的通用PID，并作为目标通用PID；
    将所述用户身份信息和所述目标通用PID进行主机PID注册操作，得到注册结果；
    将所述业务请求和所述注册结果发送至订座系统主机，以使所述订座系统主机依据所述注册结果，执行与所述业务请求对应的业务操作。
PCT/CN2021/133842 2021-03-10 2021-11-29 一种业务请求的处理方法、装置及电子设备 WO2022188469A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110260495.1A CN112965821A (zh) 2021-03-10 2021-03-10 一种业务请求的处理方法、装置及电子设备
CN202110260495.1 2021-03-10

Publications (1)

Publication Number Publication Date
WO2022188469A1 true WO2022188469A1 (zh) 2022-09-15

Family

ID=76277077

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/133842 WO2022188469A1 (zh) 2021-03-10 2021-11-29 一种业务请求的处理方法、装置及电子设备

Country Status (2)

Country Link
CN (1) CN112965821A (zh)
WO (1) WO2022188469A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112965821A (zh) * 2021-03-10 2021-06-15 中国民航信息网络股份有限公司 一种业务请求的处理方法、装置及电子设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102129443A (zh) * 2010-12-30 2011-07-20 中国民航信息网络股份有限公司 基于usas主机的实时数据传输通道及其实时数据传输方法
WO2012028026A1 (zh) * 2010-09-01 2012-03-08 中兴通讯股份有限公司 一种多模共传输时传输资源的管理方法和装置
US10078539B1 (en) * 2013-10-30 2018-09-18 American Airlines, Inc. System and method for logging and searching history events such as airline flight or crew history
CN111343141A (zh) * 2020-01-22 2020-06-26 中国民航信息网络股份有限公司 一种用户身份识别方法及相关设备
CN112965821A (zh) * 2021-03-10 2021-06-15 中国民航信息网络股份有限公司 一种业务请求的处理方法、装置及电子设备

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11323925B2 (en) * 2017-09-21 2022-05-03 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Resource selection method, device and computer storage medium

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012028026A1 (zh) * 2010-09-01 2012-03-08 中兴通讯股份有限公司 一种多模共传输时传输资源的管理方法和装置
CN102129443A (zh) * 2010-12-30 2011-07-20 中国民航信息网络股份有限公司 基于usas主机的实时数据传输通道及其实时数据传输方法
US10078539B1 (en) * 2013-10-30 2018-09-18 American Airlines, Inc. System and method for logging and searching history events such as airline flight or crew history
CN111343141A (zh) * 2020-01-22 2020-06-26 中国民航信息网络股份有限公司 一种用户身份识别方法及相关设备
CN112965821A (zh) * 2021-03-10 2021-06-15 中国民航信息网络股份有限公司 一种业务请求的处理方法、装置及电子设备

Also Published As

Publication number Publication date
CN112965821A (zh) 2021-06-15

Similar Documents

Publication Publication Date Title
US11170118B2 (en) Network system and method for access management authentication and authorization
CN101647219B (zh) 用于许可证的安全的主机更换的机制
US10552796B1 (en) Approval service in a catalog service platform
CN111027936A (zh) 一种联盟网络中基于智能合约的工作流实现方法、设备及介质
US20120042354A1 (en) Entitlement conflict enforcement
US11245577B2 (en) Template-based onboarding of internet-connectible devices
WO2022188469A1 (zh) 一种业务请求的处理方法、装置及电子设备
CN104219326A (zh) 保洁服务信息管理系统中的资源共享装置和方法
US20220334896A1 (en) Managing and Routing Messages to Distributed User Devices in an Enterprise Computing Environment
CN113361838A (zh) 业务风控方法、装置、电子设备和存储介质
CN110673933A (zh) 基于ZooKeeper的分布式异步队列实现方法、装置、设备及介质
CN111127181A (zh) 一种凭证记账方法和装置
CN111126948A (zh) 用于审批流程的处理方法和装置
CN110910089A (zh) 一种智慧社区工单处理方法及装置、服务器、系统
WO2022252853A1 (zh) 一种常旅客信息的管理方法和相关装置
US11792015B2 (en) System and method for electronic signatures as a service
CN112001704A (zh) 基于微服务架构的部省级交通建设智慧工地管理平台
KR20210141601A (ko) 라이센스 분석을 위한 시스템들 및 방법들
EP4154441B1 (en) Access management of publisher nodes for secure access to maas network
US8042160B1 (en) Identity management for application access
CN108053288B (zh) 一种业务编排下发的方法及装置
CN109639746B (zh) 一种面向安全认证传输网关集群的负载均衡方法
CN110782223A (zh) Oa系统的通用工作流装置及通用工作流实现方法
US11880791B2 (en) Attachment and detachment of compute instances owned by different tenancies
CN110933071B (zh) 影像文件传输方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21929931

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21929931

Country of ref document: EP

Kind code of ref document: A1