WO2025002329A1 - 应用程序的流量调度方法、装置、设备及存储介质 - Google Patents

应用程序的流量调度方法、装置、设备及存储介质 Download PDF

Info

Publication number
WO2025002329A1
WO2025002329A1 PCT/CN2024/102313 CN2024102313W WO2025002329A1 WO 2025002329 A1 WO2025002329 A1 WO 2025002329A1 CN 2024102313 W CN2024102313 W CN 2024102313W WO 2025002329 A1 WO2025002329 A1 WO 2025002329A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
registration
registration area
server
business
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2024/102313
Other languages
English (en)
French (fr)
Inventor
刘广航
王金辨
王一晖
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Youzhuju Network Technology Co Ltd
Original Assignee
Beijing Youzhuju Network Technology Co Ltd
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 Beijing Youzhuju Network Technology Co Ltd filed Critical Beijing Youzhuju Network Technology Co Ltd
Publication of WO2025002329A1 publication Critical patent/WO2025002329A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/30—Managing network names, e.g. use of aliases or nicknames
    • H04L61/3015—Name registration, generation or assignment
    • H04L61/302—Administrative registration, e.g. for domain names at internet corporation for assigned names and numbers [ICANN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/30—Managing network names, e.g. use of aliases or nicknames
    • H04L61/3015—Name registration, generation or assignment
    • H04L61/3025—Domain name generation or assignment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/50—Queue scheduling
    • H04L47/62—Queue scheduling characterised by scheduling criteria
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]

Definitions

  • the present disclosure relates to the field of computer technology, and in particular to a method, device, equipment and storage medium for traffic scheduling of an application program.
  • APP Application, APP
  • Some APPs will be available in multiple regions, which requires supporting users in different regions to use the same App. If an App is to support users in different regions, it must support dispatching user traffic to servers in different regions for business processing, or processing user business in all regions on a server in a fixed region.
  • a registration area label is added to the registered device or registered user, and the user traffic is dispatched to the corresponding server according to the registration area label.
  • the embodiments of the present disclosure provide a method, apparatus, device and storage medium for traffic scheduling of an application.
  • an embodiment of the present disclosure provides a traffic scheduling method for an application, the method comprising: obtaining a first registration area of a target business of the application and a second registration area where the account of the target object is located, wherein the first registration area is determined by the application in response to a registration operation of the target object for the target business, and the second registration area is determined by the application in response to an account registration operation of the target object; detecting whether the first registration area is the same as the second registration area; determining a target domain name corresponding to the first registration area based on a mapping relationship between the first registration area and the domain name, and when the first registration area is different from the second registration area, the mapping relationship is deployed in the application; and scheduling the business traffic generated by the target business to the target server corresponding to the target domain name information.
  • an embodiment of the present disclosure provides a traffic scheduling device for an application, the device comprising: a region acquisition module, used to acquire a first registration region of a target service of the application and a second registration region where the account of the target object is located, the first registration region being determined by the application in response to a registration operation of the target object for the target service, and the second registration region being determined by the application in response to an account registration operation of the target object;
  • a detection module is used to detect whether the first registration area is the same as the second registration area;
  • a domain name determination module is used to determine the target domain name corresponding to the first registration area based on the mapping relationship between the registration area and the domain name when the first registration area is different, and the mapping relationship is deployed in the application;
  • a traffic scheduling module is used to schedule the business traffic generated by the target business to the target server corresponding to the target domain name information.
  • an embodiment of the present disclosure provides a computer device, including: a memory and a processor, the memory and the processor are communicatively connected to each other, computer instructions are stored in the memory, and the processor executes the traffic scheduling method of the application program of the above-mentioned first aspect or any corresponding embodiment thereof by executing the computer instructions.
  • an embodiment of the present disclosure provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute a traffic scheduling method for an application program of the above-mentioned first aspect or any corresponding embodiment thereof.
  • FIG1 is a flow chart of a method for traffic scheduling of an application according to an embodiment of the present disclosure
  • FIG2 is a flow chart of a method for traffic scheduling of another application according to an embodiment of the present disclosure
  • FIG3 is a flow chart of another method for traffic scheduling of an application according to an embodiment of the present disclosure.
  • FIG4 is a structural block diagram of a traffic scheduling device for an application according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present disclosure.
  • a registration area tag is added to the registered device or registered user, and the user traffic is dispatched to the corresponding server according to the registration area tag. For example, when a user device starts the application for the first time, the device registration operation is performed, and the registration area tag is added according to the user area.
  • the registration area requests the control server to configure and send traffic scheduling rules (network control, NC), and subsequent service requests schedule the traffic generated by the application to the desired server according to the NC traffic scheduling rules.
  • traffic scheduling rules network control, NC
  • NC is a mapping from a host request to the real request URL (Uniform Resource Locator) of the server.
  • a host request will be sent to the real request URL issued by NC according to the mapping relationship of NC. For example, if the configuration in NC is [www.test.com->www.test-us.com], then when requesting www.test.com, it actually requests www.test-us.com, so as to achieve traffic scheduling.
  • a merchant located in region D may register a store business in region U (e.g., country U), and the registration area where the merchant is registered may be in region Y (e.g., country Y).
  • region D e.g., country D
  • region U e.g., country U
  • region Y e.g., country Y
  • the NC traffic scheduling rules may have long-tail traffic problems in off-site scheduling, that is, if you only rely on the NC traffic scheduling rules to schedule to the corresponding server, there will be long-tail traffic scheduled to the server that does not meet expectations during the interval (gap) between the successful response packets of the NC request.
  • the traffic generated by the default APP is scheduled to the server in the first area, and it is scheduled to the server in the second area through the NC traffic scheduling rules.
  • some traffic may still be scheduled to the server in the first area. If some key business requests are not requested to the correct server during this gap period, the business execution results will not be consistent with expectations.
  • the traffic on the APP can only be scheduled to the server corresponding to the default domain name. If the default domain name and the business area are not in the same area, there is still a problem that the traffic cannot be scheduled to the correct server.
  • this technical solution builds a traffic scheduling strategy for server domain names corresponding to different regions into the APP, and performs traffic scheduling in the APP according to the traffic scheduling strategy. As a result, the correct server corresponding to the corresponding region can be obtained in the APP without relying on network requests.
  • the type, scope of use, and usage scenarios of the personal information involved in the present disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.
  • a prompt message is sent to the user to clearly prompt the user that the operation requested to be performed will require the acquisition and use of the user's personal information.
  • the user can autonomously choose whether to provide personal information to software or hardware such as an electronic device, application, server, or storage medium that performs the operation of the technical solution of the present disclosure according to the prompt message.
  • the method of sending a prompt message to the user may be, for example, a pop-up window, in which the prompt message may be presented in text.
  • the pop-up window may also carry a selection control for the user to choose "agree” or "disagree” to provide personal information to the electronic device.
  • an embodiment of a traffic scheduling method for an application is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.
  • FIG. 1 is a flow chart of the method for traffic scheduling of an application according to an embodiment of the present disclosure. As shown in FIG. 1, the process includes the following steps:
  • Step S101 obtaining a first registration area of a target business of an application and a second registration area where a target object's account is located, wherein the first registration area is determined by the application responding to a registration operation of the target object for the target business, and the second registration area is determined by the application responding to an account registration operation of the target object.
  • An application is a computer program deployed in a computer device and runs in user mode. It has a visual user interface and can interact with users.
  • the target business is the function of the application, such as opening a store, live streaming of products, etc.
  • the first registration area is the business area determined when registering the target business, that is, the area where the target business can be performed, such as area A, area B, etc.
  • the first registration area can be obtained by the computer device by parsing the registration information of the target business.
  • the "area" can be one or more countries, regions within a country, states, provinces, or a certain geographical area.
  • the second registration area is the registration area of the application account, that is, the location of the application account. Specifically, the second registration area can be determined based on the Internet Protocol (IP) address of the computer device and the location of the operating system.
  • IP Internet Protocol
  • the second registration area can also be determined according to the location of the Subscriber Identity Module (SIM) installed in the mobile phone.
  • SIM Subscriber Identity Module
  • Step S102 detecting whether the first registration area is the same as the second registration area.
  • step S103 Compare the first registration area with the second registration area to determine whether the first registration area is consistent with the second registration area.
  • step S103 is executed; when the first registration area is the same as the second registration area, it means that the target service is consistent with the registration area of the account, and traffic scheduling can be performed within the registration area based on the registration area tag of the account.
  • Step S103 When the first registration area is different from the second registration area, a target domain name corresponding to the first registration area is determined based on a mapping relationship between registration areas and domain names, wherein the mapping relationship is deployed in the application.
  • mapping relationship between the first registration area and the domain name, and the mapping relationship is pre-deployed in the application.
  • the target domain name information corresponding to the first registration area is determined according to the mapping relationship.
  • the target domain name information indicates the domain name information corresponding to the first registration area.
  • the mapping relationship between the registration area and the domain name can be built into the application in the form of a configuration table, and the configuration table is provided with server domain name information corresponding to different business registration areas.
  • the computer device can parse the mapping relationship built into the application to determine the target domain name information corresponding to the first registration area.
  • Step S104 dispatching the service traffic generated by the target service to the target server corresponding to the target domain name information.
  • the business traffic is the data request traffic generated by the target business during operation. After determining the target domain name information, the business traffic generated by running the target business can be dispatched to the corresponding target server.
  • the business registration areas are area A, area B, and area C, and their corresponding domain name information are test1.com, test2.com, and test3.com, respectively. Then, the business traffic generated by the target business is scheduled according to the mapping relationship between the business registration area and the domain name information.
  • test1.com, test2.com, and test3.com are server 1, server 2, and server 3 respectively. If the servers corresponding to test1.com, test2.com, and test3.com are server 1, server 2, and server 3 respectively, then when the first registration area of the target business is determined to be area B by parsing the registration information of the target business, the mapping relationship between the business registration area and the domain name information is traversed, and it can be determined that the target domain name information corresponding to the first registration area is test2.com. Then, combined with test2.com, the business traffic generated by the target business can be dispatched to server 2 corresponding to test2.com.
  • the traffic scheduling method for an application deploys a mapping relationship between a first registration area and a domain name in an application.
  • the mapping relationship can be read from the application to determine the target domain name information corresponding to the first registration area, so as to schedule the service traffic to the target server corresponding to the target domain name information.
  • the scheduling decision of the service traffic does not depend on the network request, and the server corresponding to the area to which the service traffic belongs can be determined within the application, so as to accurately schedule the service traffic to the desired server, thereby achieving Effective remote scheduling of business traffic is achieved.
  • FIG. 2 is a flow chart of the method for traffic scheduling of an application according to an embodiment of the present disclosure. As shown in FIG. 2, the process includes the following steps:
  • Step S201 obtain the first registration area of the target business of the application and the second registration area where the target object's account is located.
  • the first registration area is determined by the application responding to the target object's registration operation for the target business
  • the second registration area is determined by the application responding to the target object's account registration operation.
  • step S201 may include:
  • Step S2011 obtaining the login account information of the application.
  • the login account information is used to represent the account data generated by the target object registration application, and the account data represents the registration area of the target object.
  • the login account information is stored in the cache space of the computer device.
  • the application can call the login interface and retrieve the corresponding login account information from the cache space of the computer device after successful login.
  • the registration page of the application can be entered, and in response to the target object's registration operation for the application, the login account information generated by the target object when registering the application can be obtained.
  • Step S2012 detecting whether the account corresponding to the login account information has registered the target service.
  • the target business is the business associated with the current account, that is, other businesses registered in the application after the target object registers the application. Since there is an association between the target business and the login account information, after the login account information is obtained, it can be determined whether the current account has registered the target business by detecting the data associated with the login account information. When it is determined that the current account has registered the target business, step S2013 is executed, otherwise step S2014 is executed.
  • Step S2013 when it is determined that the account is registered with the target business, the business information corresponding to the target business is retrieved, and the first registration area where the target business is located is determined according to the business information.
  • the business information represents the registration data of the target object for the target business, and includes business account data, business password data, business attribution area data, etc.
  • Step S2014 When it is determined that the account has not registered the target service, the registration page of the target service is entered.
  • the registration page includes multiple registration areas.
  • multiple business tags are displayed in the visualization page of the application, and the business tags are used to trigger the entry into the corresponding business page.
  • the target object clicks or triggers the tag of the target business the registration page of the target business is entered, and multiple registration areas are displayed in the registration page.
  • the multiple registration areas are different areas, which are used to determine the regional server to be requested by the subsequent business interface request.
  • Step S2015 In response to a selection operation on a registration area in the registration page, determining a first registration area based on the selection operation.
  • the target object selects the area where the target business is located on the registration page. Accordingly, the registration page of the target business can respond to the target object's selection operation on the registration area and call the registration interface to complete the registration for the target business. Then, combined with the registration information of the target business, the registration area selected by the target object is determined as the first registration area.
  • the target object can re-register and re-select the registration area.
  • Step S2016 obtaining the second registration area where the target object's account is located.
  • the second registration area please refer to the above embodiment, which will not be repeated here.
  • Step S202 Detect whether the first registration area is the same as the second registration area.
  • step S102 of the embodiment shown in FIG1 please refer to step S102 of the embodiment shown in FIG1 , which will not be described in detail here.
  • Step S203 When the first registration area is different from the second registration area, the target domain name corresponding to the first registration area is determined based on the mapping relationship between the registration area and the domain name.
  • the mapping relationship is deployed in the application. For details, please refer to step S103 of the embodiment shown in FIG. 1, which will not be repeated here.
  • the above method may further include: when a change in the registration area and/or domain name is detected, determining an updated registration area and/or domain name; and updating the mapping relationship between the registration area and the domain name using the updated registration area and domain name.
  • the computer device when the computer device detects that the registration area and/or domain name is modified, it determines the modified registration area and/or domain name, and redetermines the mapping relationship between the service registration area and the domain name based on the modified registration area and/or domain name.
  • the computer device when the computer device detects that a registration area and/or a domain name is added or deleted, it determines the newly added registration area and/or domain name. Then, the mapping relationship between the business registration area and the domain name is added or deleted.
  • mapping relationship between the registration area and the domain name can be flexibly updated.
  • Step S204 dispatch the service traffic generated by the target service to the target server corresponding to the target domain name information.
  • step S103 of the embodiment shown in FIG1 please refer to step S103 of the embodiment shown in FIG1 , which will not be described in detail here.
  • the traffic scheduling method for an application detects the login account information of the application to determine whether the corresponding account has registered the target service. If the account has registered the target service, the corresponding registration area can be read from the service information, so that the service traffic can be scheduled according to the registration area to ensure that the service traffic is scheduled to the desired server. When it is detected that the account has not registered the target service, it can jump to the target service registration page to register the target service, and select the registration area for the target service on the registration page, so that the service traffic can be scheduled according to the registration area when the target service is registered.
  • FIG3 is a flow chart of the method for traffic scheduling of an application according to an embodiment of the present disclosure. As shown in FIG3, the process includes the following steps:
  • Step S301 obtain the first registration area of the target business of the application and the second registration area where the target object's account is located.
  • the first registration area is determined by the application responding to the target object's registration operation for the target business
  • the second registration area is determined by the application responding to the target object's account registration operation. Please refer to step S201 of the embodiment shown in Figure 2 for details, which will not be repeated here.
  • Step S302 Detect whether the first registration area is the same as the second registration area.
  • step S202 of the embodiment shown in FIG2 please refer to step S202 of the embodiment shown in FIG2 , which will not be described in detail here.
  • Step S303 When the first registration area is different from the second registration area, the target domain name corresponding to the first registration area is determined based on the mapping relationship between the registration area and the domain name.
  • the mapping relationship is deployed in the application. For details, please refer to step S203 of the embodiment shown in FIG. 2, which will not be repeated here.
  • Step S304 dispatch the service traffic generated by the target service to the target server corresponding to the target domain name information.
  • step S304 may include:
  • Step S3041 In response to a data request generated in the first registration area for a target service, detecting a server load in the first registration area based on the data request, and determining an idle server in the first registration area.
  • the idle server is a server whose server load is lower than a preset threshold.
  • the data request is a request triggered by the target object for the target business in the first registration area.
  • the application in the computer device pulls the traffic scheduling configuration information of the first registration area after receiving the data request, and the traffic scheduling configuration information is configured with a mapping from the data request to the real request URL.
  • the domain name address corresponding to the idle domain name information in the first registration area is the domain name address of the real request URL.
  • a plurality of servers are configured in the first registration area, and different servers correspond to different domain names.
  • the server load in the first registration area can be detected to determine the domain name that is currently idle and the idle server corresponding to the domain name.
  • Step S3042 determine an idle server as a target server, and dispatch the service traffic generated by the data request to the idle server.
  • the idle server After an idle server is determined, the idle server is used as a target server for providing traffic scheduling, and traffic generated by the target service in the first registration area is scheduled to the idle server.
  • the above method may further include:
  • Step a1 obtaining the default domain name corresponding to the first registration area.
  • Step a2 when the business traffic generated by the data request cannot be successfully dispatched to the idle server, the default server corresponding to the default domain name is determined as the target server, and the business traffic generated by the data request is dispatched to the default server corresponding to the default domain name.
  • the default server is a pre-specified server used for service traffic scheduling.
  • the data request When pulling the traffic configuration information of the first registration area to determine the idle server, if the business traffic generated by the data request is not successfully dispatched to the idle server due to poor server load and network conditions, the data request will be linked to the default server corresponding to the default domain name. The business traffic generated by the target business will still be dispatched to the server in the first registration area, and will not be dispatched to servers in other areas.
  • the server No. 16 in the first registration area is an idle server
  • the data request will be sent to the real request domain name: test1-16.XXX.com. If the sending fails, the default request will be to test1.XXX.com, which is still a request to the server in the first registration area, and there will be no scheduling to the wrong server in other areas.
  • the business traffic generated by the first registration area cannot be successfully dispatched to the idle server, The business traffic is dispatched to the default server, thereby avoiding the situation where the business traffic is dispatched to the wrong server due to poor server load and network conditions, ensuring that the business traffic in the first registration area can be dispatched to the correct server, and to a certain extent realizing the fault tolerance capability of server scheduling in the first registration area.
  • the above method may further include:
  • Step S305 When data is communicated between the first registration area and other areas, the area identifier carried in the service traffic received by the gateway layer is parsed.
  • the data at the gateway layer is intercommunication. If data is intercommunication between the first registration area and other areas, data requests from other areas may be dispatched to the gateway layer of the first registration area. Then, when the gateway layer in the first registration area receives business traffic, it can parse the business traffic and obtain the area identifier it carries.
  • Step S306 determining whether the area identifier matches the server corresponding to the gateway layer.
  • the regional identifier carried by the business traffic is compared with the server region corresponding to the gateway layer to determine whether the two match, that is, whether the regional identifier is the server region corresponding to the gateway layer. If the regional identifier does not match the server corresponding to the gateway layer, step S308 is executed; if the regional identifier matches the server corresponding to the gateway layer, the gateway layer can directly dispatch the business traffic to the corresponding server.
  • Step S307 When it is determined that the area identifier does not match the server corresponding to the gateway layer, a server matching the area identifier is determined.
  • the gateway layer can determine the server matching the regional identifier based on the regional identifier.
  • Step 308 determine the server that matches the area identifier as the target server, and forward the service traffic to the target server that matches the area identifier.
  • the server that matches the regional identifier is determined as the target server, and the gateway layer forwards the business traffic to the target server that matches the regional identifier. For example, data intercommunication is allowed between the first registered area A1 and area C1.
  • the regional identifier of the first registered area A1 is I
  • the regional identifier of area C1 is S. If the business traffic carrying the regional identifier S is dispatched to the server gateway layer in the first registered area A1, the server gateway layer will forward the business traffic to the server in area C1 corresponding to the regional identifier S, so that the business traffic can be dispatched to the correct server at the gateway layer.
  • the traffic scheduling method for an application detects the server load in the first registration area, determines the idle servers in the first registration area, and optimizes the server load in the same area to achieve the same Regional traffic scheduling.
  • the gateway layer can forward the business traffic to the matching target server, further ensuring the accurate scheduling of business traffic.
  • a traffic scheduling device for an application is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated.
  • the term "module” can implement a combination of software and/or hardware for a predetermined function.
  • the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.
  • This embodiment provides a traffic scheduling device for an application program, as shown in FIG4 , including:
  • the region acquisition module 401 is used to acquire the first registration region of the target business of the application and the second registration region where the target object's account is located.
  • the first registration region is determined by the application responding to the target object's registration operation for the target business
  • the second registration region is determined by the application responding to the target object's account registration operation.
  • the detection module 402 is used to detect whether the first registration area is the same as the second registration area.
  • the domain name determination module 403 is used to determine the target domain name corresponding to the first registration area based on the mapping relationship between the first registration area and the domain name when the first registration area is different from the second registration area.
  • the mapping relationship is deployed in the application.
  • the traffic scheduling module 404 is used to schedule the service traffic generated by the target service to the target server corresponding to the target domain name information.
  • the region acquisition module 401 may include:
  • the data acquisition unit is used to obtain the login account information of the application.
  • the detection unit is used to detect whether the account corresponding to the login account information has registered the target business.
  • the information retrieving unit is used to retrieve the business information corresponding to the target business when it is determined that the current account has registered the target business, and to determine the first registration area where the target business is located according to the business information.
  • the region acquisition module 401 may further include:
  • the registration unit is used to enter the registration page of the target service when it is determined that the current account has not registered the target service.
  • the registration page includes multiple registration areas.
  • the area selection unit is used to respond to a selection operation of a registration area in the registration page and determine a first registration area based on the selection operation.
  • the above device may further include:
  • the update module is used to determine the updated registration area and/or domain name when a change in the registration area and/or domain name is detected, and to update the mapping relationship between the registration area and the domain name using the updated registration area and domain name.
  • the traffic scheduling module 403 may include:
  • the server load detection unit is used to respond to a data request generated in the first registration area for a target service, detect the server load of the first registration area based on the data request, and determine an idle server in the first registration area.
  • the scheduling unit is used to determine an idle server as a target server and schedule the business traffic generated by the data request to the idle server.
  • the traffic scheduling module 403 may further include:
  • the default domain name obtaining unit is used to obtain the default domain name corresponding to the first registration area.
  • the default scheduling unit is used to determine the default server corresponding to the default domain name as the target server and schedule the business traffic generated by the data request to the default server corresponding to the default domain name when the business traffic generated by the data request cannot be successfully scheduled to the idle server.
  • the default server is a pre-designated server for business traffic scheduling.
  • the traffic scheduling device of the above application may further include:
  • the identification acquisition module is used to parse the area identification carried by the service traffic received by the gateway layer when there is data intercommunication between the first registration area and other attribution areas.
  • the judgment module is used to judge whether the regional identifier matches the server corresponding to the gateway layer.
  • the matching module is used to determine a server matching the regional identifier when it is determined that the regional identifier does not match the server corresponding to the gateway layer.
  • the traffic forwarding module is used to determine the server matching the regional identifier as the target server and forward the business traffic to the target server matching the regional identifier.
  • the traffic scheduling device of the application in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC circuit, a processor and memory that executes one or more software or fixed programs, and/or other devices that can provide the above functions.
  • the traffic scheduling device for an application deploys a mapping relationship between a registration area and a domain name in an application.
  • the mapping relationship can be read from the application to determine the target domain name information corresponding to the first registration area, so as to schedule the service traffic to the target domain name information. Therefore, the scheduling decision of business traffic does not rely on network requests.
  • the server corresponding to the area where the business traffic belongs can be determined within the application, so that the business traffic can be accurately scheduled to the desired server, realizing effective remote scheduling of business traffic.
  • the embodiment of the present disclosure also provides a computer device having a traffic scheduling device for the application program shown in FIG. 4 above.
  • FIG. 5 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present disclosure.
  • the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces.
  • the various components are connected to each other using different buses for communication, and can be installed on a common motherboard or installed in other ways as needed.
  • the processor can process instructions executed in the computer device, including instructions stored in or on the memory to display graphical information of the GUI on an external input/output device (such as a display device coupled to the interface).
  • an external input/output device such as a display device coupled to the interface.
  • multiple processors and/or multiple buses can be used together with multiple memories and multiple memories.
  • multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system).
  • a processor 10 is taken as an example.
  • the processor 10 may be a central processing unit, a network processor or a combination thereof.
  • the processor 10 may further include a hardware chip.
  • the hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof.
  • the programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.
  • the memory 20 stores instructions executable by at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiment.
  • the memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc.
  • the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device.
  • the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
  • the memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include the above-mentioned types of memory. Storage combination.
  • a volatile memory such as a random access memory
  • the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive
  • the memory 20 may also include the above-mentioned types of memory. Storage combination.
  • the computer device further includes an input device 30 and an output device 40.
  • the processor 10, the memory 20, the input device 30 and the output device 40 may be connected via a bus or other means, and FIG5 takes the connection via a bus as an example.
  • the input device 30 can receive input digital or character information, and generate key signal input related to the user settings and function control of the computer device, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, an indicator bar, one or more mouse buttons, a trackball, a joystick, etc.
  • the output device 40 may include a display device, an auxiliary lighting device (e.g., an LED) and a tactile feedback device (e.g., a vibration motor), etc.
  • the above-mentioned display device includes but is not limited to a liquid crystal display, a light emitting diode, a display and a plasma display. In some optional embodiments, the display device can be a touch screen.
  • the computer device also includes a communication interface for data communication between the computer device and other devices or a communication network.
  • the embodiments of the present disclosure also provide a computer-readable storage medium.
  • the above-mentioned method according to the embodiments of the present disclosure can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium and downloaded through a network, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware.
  • the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state drive, etc.; further, the storage medium can also include a combination of the above-mentioned types of memory.
  • a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.
  • the embodiments of the present disclosure also provide a computer program product, which includes instructions executable by at least one processor 10, so that the at least one processor 10 performs the method shown in the above embodiment.
  • the embodiments of the present disclosure also provide a computer program, which includes instructions executable by at least one processor 10, so that the at least one processor 10 performs the method shown in the above embodiment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本公开涉及计算机技术领域，公开了一种应用程序的流量调度方法、装置、设备及存储介质。其中，该方法包括：获取应用程序的目标业务的第一注册区域以及目标对象的账户所处的第二注册区域；检测第一注册区域与第二注册区域是否相同；响应于第一注册区域与第二注册区域不同，基于第一注册区域与域名之间的映射关系，确定第一注册区域对应的目标域名，该映射关系部署在应用程序中；将目标业务产生的业务流量调度至目标域名信息所对应的目标服务器。

Description

应用程序的流量调度方法、装置、设备及存储介质
相关申请的交叉引用
本申请是以申请号为202310798556.9，申请日为2023年6月30日的中国申请为基础，并主张其优先权，该中国申请的公开内容在此作为整体引入本申请中。
技术领域
本公开涉及计算机技术领域，具体涉及一种应用程序的流量调度方法、装置、设备及存储介质。
背景技术
随着各大应用程序(Application，APP)的上线，部分APP会在多个区域上架，这就需要支持不同区域的用户使用同一个App。而一个App若要支持不同区域的用户进行使用，那么必然需要支持将用户流量调度到不同区域的服务器进行业务处理，或在一个固定区域的服务器处理所有区域的用户业务。
目前，相关技术中是在注册APP时，为注册设备或注册用户打上注册区域标签，根据注册区域标签将用户流量调度到对应服务器。
发明内容
本公开实施例提供了一种应用程序的流量调度方法、装置、设备及存储介质。
根据本公开的一个方面，本公开实施例提供了一种应用程序的流量调度方法，该方法包括：获取应用程序的目标业务的第一注册区域以及所述目标对象的账户所处的第二注册区域，其中，第一注册区域为应用程序响应目标对象针对目标业务的注册操作所确定的，所述第二注册区域为应用程序响应所述目标对象的账号注册操作所确定的；检测所述第一注册区域与所述第二注册区域是否相同；基于所述第一注册区域与域名之间的映射关系，确定第一注册区域对应的目标域名，当所述第一注册区域与所述第二注册区域不同时，该映射关系部署在应用程序中；将目标业务产生的业务流量调度至目标域名信息所对应的目标服务器。
根据本公开的一个方面，本公开实施例提供了一种应用程序的流量调度装置，该装置包括：区域获取模块，用于获取应用程序的目标业务的第一注册区域以及所述目标对象的账户所处的第二注册区域，第一注册区域为应用程序响应目标对象针对目标业务的注册操作所确定的，第二注册区域为应用程序响应目标对象的账号注册操作所确定的； 检测模块，用于检测第一注册区域与第二注册区域是否相同；域名确定模块，用于当第一注册区域与第二注册区域不同时，基于注册区域与域名之间的映射关系，确定所述第一注册区域对应的目标域名，该映射关系部署在应用程序中；流量调度模块，用于将目标业务产生的业务流量调度至目标域名信息所对应的目标服务器。
根据本公开的一个方面，本公开实施例提供了一种计算机设备，包括：存储器和处理器，存储器和处理器之间互相通信连接，存储器中存储有计算机指令，处理器通过执行计算机指令，从而执行上述第一方面或其对应的任一实施方式的应用程序的流量调度方法。
根据本公开的一个方面，本公开实施例提供了一种计算机可读存储介质，该计算机可读存储介质上存储有计算机指令，计算机指令用于使计算机执行上述第一方面或其对应的任一实施方式的应用程序的流量调度方法。
附图说明
为了更清楚地说明本公开具体实施方式或现有技术中的技术方案，下面将对具体实施方式或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图是本公开的一些实施方式，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是根据本公开实施例的应用程序的流量调度方法的流程示意图；
图2是根据本公开实施例的另一应用程序的流量调度方法的流程示意图；
图3是根据本公开实施例的又一应用程序的流量调度方法的流程示意图；
图4是根据本公开实施例的应用程序的流量调度装置的结构框图；
图5是本公开实施例的计算机设备的硬件结构示意图。
具体实施方式
为使本公开实施例的目的、技术方案和优点更加清楚，下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本公开保护的范围。
相关技术中是在注册APP时，为注册设备或注册用户打上注册区域标签，根据注册区域标签将用户流量调度到对应服务器。以某应用程序例，用户设备第一次启动该应用程序时会进行注册设备操作，根据用户区域打上注册区域标签，启动该应用程序时根据 注册区域请求控制服务器配置下发流量调度规则(network control，NC)，后续业务请求根据NC流量调度规则把该应用程序所产生的流量调度到期望的服务器。
其中，NC是一个主机host请求到服务器真实请求URL(Uniform Resource Locator，统一资源定位器)的映射，在App网络请求时会根据NC的映射关系把一个host请求到NC下发的真实请求URL中。例如NC里配置的是【www.test.com->www.test-us.com】，那么在请求www.test.com时，实际上是请求的是www.test-us.com，以此实现流量调度。
然而，若用户账号数据和用户业务数据归属不同区域，只依赖注册区域调度流量是行不通的。以具有商家功能的应用程序(即，Seller所使用的App)为例，一个位于区域D(例如，国家D)的商家可能会在区域U(例如，国家U)内注册店铺业务，而该商家注册的注册区域可能是在区域Y(例如，国家Y)。此时，由于店铺业务数据是在区域U注册的，那么商家的店铺业务数据是需要调度到区域U的，并且在选择区域U作为店铺业务后，该店铺业务的数据请求接口需要能够立即调度到区域U区域内的服务器。
而且，NC流量调度规则在异地调度中能够存在长尾流量问题，即如果只依赖NC流量调度规则调度到对应服务器，在NC请求成功回包之间的间隔期(gap)会有长尾流量调度到不符合预期的服务器。例如，默认APP产生的流量调度到第一区域的服务器，并通过NC流量调度规则将其调度到第二区域的服务器，在按照NC流量调度规则完成流量调度前可能有部分流量还是会调度到第一区域的服务器。若这个gap期内有一些关键业务请求未请求到正确服务器，就会出现业务执行结果与预期不符的情况。而且，如果按照NC流量调度规则拉取失败时，APP上流量就只能调度到默认域名对应的服务器了，若默认域名与业务区域并非一个区域，仍然存在流量调度不到正确服务器的问题。
基于此，本技术方案通过在APP中内置一份不同区域所对应服务器域名的流量调度策略，按照该流量调度策略在APP内进行流量调度。由此，在APP中可以不依赖网络请求就取到对应区域所对应的正确服务器。
可以理解的是，在使用本公开各实施例公开的技术方案之前，均应当依据相关法律法规通过恰当的方式对本公开所涉及个人信息的类型、使用范围、使用场景等告知用户并获得用户的授权。例如，在响应于接收到用户的主动请求时，向用户发送提示信息，以明确地提示用户，其请求执行的操作将需要获取和使用到用户的个人信息。从而，使得用户可以根据提示信息来自主地选择是否向执行本公开技术方案的操作的电子设备、应用程序、服务器或存储介质等软件或硬件提供个人信息。
作为一种可选的但非限定性的实现方式，响应于接收到用户的主动请求，向用户发送提示信息的方式例如可以是弹窗的方式，弹窗中可以以文字的方式呈现提示信息。此外，弹窗中还可以承载供用户选择“同意”或者"不同意”向电子设备提供个人信息的选择控件。可以理解的是，上述通知和获取用户授权过程仅是示意性的，不对本公开的实现方式构成限定，其它满足相关法律法规的方式也可应用于本公开的实现方式中。
根据本公开实施例，提供了一种应用程序的流量调度方法实施例，需要说明的是，在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行，并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
在本实施例中提供了一种应用程序的流量调度方法，可用于上述的计算设备，如手机、平板电脑、电脑等，该计算机设备安装有应用程序，图1是根据本公开实施例的应用程序的流量调度方法的流程图，如图1所示，该流程包括如下步骤：
步骤S101，获取应用程序的目标业务的第一注册区域以及目标对象的账户所处的第二注册区域。其中，第一注册区域为应用程序响应目标对象针对目标业务的注册操作所确定的，第二注册区域为应用程序响应目标对象的账号注册操作所确定的。
应用程序为部署在计算机设备中的计算机程序，运行在用户模式下，其具有可视的用户界面，能够与用户进行交互。目标业务为应用程序所具有的功能，例如，开店业务、产品直播业务等。
第一注册区域为注册目标业务时所确定的营业地区，即可以执行该目标业务的地区，例如区域A、区域B等。具体地，第一注册区域可以由计算机设备通过解析目标业务的注册信息得到。在本公开的实施例中，“区域”可以是一个或多个国家、一个国家内的地区、州、省或者某个地理区域。
第二注册区域为应用程序账号的注册地区，即应用程序账号的所在地。具体地，该第二注册区域可以根据计算机设备的互联网协议(Internet Protocol Address，IP)地址、操作系统的归属地确定。
在一些可选的实施方式中，若计算机设备为手机，第二注册区域还可以根据手机中所安装用户识别卡(Subscriber Identity Module，SIM)的归属地确定。
步骤S102，检测第一注册区域与第二注册区域是否相同。
将第一注册区域与第二注册区域进行比对，确定第一注册区域与第二注册区域是否 相同。当第一注册区域与第二注册区域不同时，执行步骤S103；当第一注册区域与第二注册区域相同时，表示目标业务与账户的注册区域一致，此时依赖账户的注册区域标签在注册区域内进行流量调度即可。
步骤S103，当第一注册区域与第二注册区域不同时，基于注册区域与域名之间的映射关系，确定第一注册区域对应的目标域名。其中，该映射关系部署在应用程序中。
第一注册区域与域名之间存在映射关系，且该映射关系预先部署在应用程序中，当第一注册区域与第二注册区域不同时，根据映射关系确定第一注册区域所对应的目标域名信息。
目标域名信息表示与第一注册区域所对应的域名信息。注册区域与域名之间的映射关系能够以配置表的形式内置于应用程序中，该配置表中设置有不同业务注册区域所对应的服务器域名信息。计算机设备可以解析内置在应用程序中的映射关系，从中确定出第一注册区域所对应的目标域名信息。
步骤S104，将目标业务产生的业务流量调度至目标域名信息所对应的目标服务器。
目标服务器与目标域名信息之间是一一对应的，业务流量为目标业务在运行过程中所产生的数据请求流量。在确定出目标域名信息后，后续则可以将运行目标业务所产生的业务流量调度至相应的目标服务器。
例如，业务注册区域为区域A、区域B、区域C，其对应的域名信息分别为test1.com、test2.com、test3.com，则根据业务注册区域与域名信息之间的映射关系，对目标业务所产生的业务流量进行调度。
若test1.com、test2.com、test3.com对应的服务器分别为服务器1、服务器2、服务器3，那么当通过解析目标业务的注册信息所确定出目标业务的第一注册区域为区域B时，则遍历业务注册区域与域名信息之间的映射关系，可以确定第一注册区域对应的目标域名信息为test2.com，继而结合该test2.com即可将目标业务所产生的业务流量调度至test2.com对应的服务器2。
本实施例提供的应用程序的流量调度方法，通过在应用程序中部署第一注册区域与域名之间的映射关系，在第一注册区域与第二注册区域不同时，可以从应用程序中读取映射关系，确定第一注册区域所对应的目标域名信息，以将业务流量调度至目标域名信息所对应的目标服务器。由此，业务流量的调度决策不依赖网络请求，在应用程序内就能确定出业务流量所归属区域对应的服务器，以将业务流量精准调度到期望服务器，实 现了业务流量的有效异地调度。
在本实施例中提供了一种应用程序的流量调度方法，可用于上述的计算设备，如手机、平板电脑、电脑等，该计算机设备安装有应用程序，图2是根据本公开实施例的应用程序的流量调度方法的流程图，如图2所示，该流程包括如下步骤：
步骤S201，获取应用程序的目标业务的第一注册区域以及目标对象的账户所处的第二注册区域。其中，第一注册区域为应用程序响应目标对象针对目标业务的注册操作所确定的，第二注册区域为应用程序响应目标对象的账号注册操作所确定的。
具体地，上述步骤S201可以包括：
步骤S2011，获取应用程序的登录账户信息。
登录账户信息用于表征目标对象注册应用程序所产生的账户数据，该账户数据表示目标对象的注册区域。
具体地，登录账户信息存储在计算机设备的缓存空间中，当检测到目标对象启动应用程序，进入应用程序的登录页面后，应用程序可以调用登录接口，待成功登录后从计算机设备的缓存空间中调取相应的登录账户信息。
需要说明的是，若目标对象当前并未注册该应用程序，则在启动该应用程序后，可以进入应用程序的注册页面，响应于目标对象对于应用程序的注册操作，获取目标对象在注册应用程序时所产生的登录账户信息。
步骤S2012，检测登录账户信息对应的账户是否注册有目标业务。
目标业务是与当前账户所关联的业务，即目标对象在注册应用程序之后，在应用程序中注册的其他业务。由于目标业务与登录账户信息之间存在关联关系，当获取到登录账户信息后，通过检测该登录账户信息所关联的数据，即可确定当前账户是否注册有目标业务。当确定当前账户注册有目标业务时，执行步骤S2013，否则执行步骤S2014。
步骤S2013，当确定账户注册有目标业务时，调取目标业务对应的业务信息，以及，根据业务信息，确定目标业务所处的第一注册区域。
业务信息表示目标对象对于目标业务的注册数据，该业务信息包括业务账号数据、业务密码数据以及业务归属区域数据等。当确定出登录账户信息对应的账户注册有目标业务时，并在目标对象成功登录目标业务之后，可以由目标业务接口返回的业务信息中调取出第一注册区域。
步骤S2014，当确定账户未注册有目标业务时，进入目标业务的注册页面。其中， 该注册页面中包括多个注册区域。
当确定登录账户信息对应的账户未注册有目标业务时，在应用程序的可视化页面中显示有多个业务标签，该业务标签用于触发进入相应业务页面。在目标对象点击或触发目标业务的标签时，进入目标业务的注册页面，并在该注册页面中展示出多个注册区域。其中，该多个注册区域为不同的区域，用于确定后续业务接口请求所要请求到的区域服务器。
步骤S2015，响应于在注册页面中对注册区域的选择操作，基于选择操作确定第一注册区域。
目标对象在注册页面选择目标业务所处的区域，相应地，目标业务的注册页面可以响应目标对象对于注册区域的选择操作，调用注册接口，以完成针对于目标业务的注册。继而，结合目标业务的注册信息，将目标对象所选择的注册区域确定为第一注册区域。
需要说明的是，此处暂不考虑目标业务是否注册成功，对于未注册成功的目标业务，目标对象可以重新注册并重新选择注册区域。
步骤S2016，获取目标对象的账户所处的第二注册区域。针对于第二注册区域的相关说明参见上述实施例，此处不再赘述。
步骤S202，检测第一注册区域与第二注册区域是否相同。详细请参见图1所示实施例的步骤S102，在此不再赘述。
步骤S203，当第一注册区域与第二注册区域不同时，基于注册区域与域名之间的映射关系，确定第一注册区域对应的目标域名。其中，该映射关系部署在应用程序中。详细请参见图1所示实施例的步骤S103，在此不再赘述。
在一些可选的实施方式中，上述方法还可以包括：当检测到注册区域和/或域名发生变化时，确定更新后的注册区域和/或域名；利用更新后的注册区域与域名，更新注册区域与域名之间的映射关系。
技术人员可以根据实际需求对业务注册区域与域名之间的映射关系进行修改、增删等。
例如，当计算机设备检测到注册区域和/或域名发生修改时，确定修改后的注册区域和/或域名，根据修改后的注册区域和/或域名，重新确定业务注册区域与域名之间的映射关系。
例如，当计算机设备检测到注册区域和/或域名发生增删时，确定新增的注册区域和/ 或域名，以及删除的注册区域和/或域名。继而，对业务注册区域与域名之间的映射关系进行新增或删除。
在该实施方式中，通过支持线上更新注册区域与域名之间的映射关系，由此能够灵活的更新注册区域与域名之间的映射关系。
步骤S204，将目标业务产生的业务流量调度至目标域名信息所对应的目标服务器。详细请参见图1所示实施例的步骤S103，在此不再赘述。
本实施例提供的应用程序的流量调度方法，通过检测应用程序的登录账户信息以确定其对应的账户是否注册有目标业务，若该账户注册有目标业务则从业务信息中读取相应的注册区域即可，从而，根据该注册区域进行业务流量的调度即可，保证将业务流量调度到所期望的服务器。在检测到该账户并未注册目标业务时，则可以跳转到目标业务注册页面以进行目标业务的注册，并在注册页面中选择针对于目标业务的注册区域，由此，后续便可以根据目标业务注册时的注册区域对业务流量进行调度。
在本实施例中提供了一种应用程序的流量调度方法，可用于上述的计算设备，如手机、平板电脑、电脑等，该计算机设备安装有应用程序，图3是根据本公开实施例的应用程序的流量调度方法的流程图，如图3所示，该流程包括如下步骤：
步骤S301，获取应用程序的目标业务的第一注册区域以及目标对象的账户所处的第二注册区域。其中，第一注册区域为应用程序响应目标对象针对目标业务的注册操作所确定的，第二注册区域为应用程序响应目标对象的账号注册操作所确定的。详细请参见图2所示实施例的步骤S201，在此不再赘述。
步骤S302，检测第一注册区域与第二注册区域是否相同。详细请参见图2所示实施例的步骤S202，在此不再赘述。
步骤S303，当第一注册区域与第二注册区域不同时，基于注册区域与域名之间的映射关系，确定第一注册区域对应的目标域名。其中，该映射关系部署在应用程序中。详细请参见图2所示实施例的步骤S203，在此不再赘述。
步骤S304，将目标业务产生的业务流量调度至目标域名信息所对应的目标服务器。
具体地，上述步骤S304可以包括：
步骤S3041，响应于针对目标业务在第一注册区域所产生的数据请求，基于数据请求检测第一注册区域的服务器负载量，确定第一注册区域中的空闲服务器。
其中，空闲服务器为服务器负载量低于预设阈值的服务器。
数据请求为目标对象针对目标业务在第一注册区域所触发的请求。具体地，目标对象在触发数据请求时，计算机设备中的应用程序在接收到该数据请求后，拉取第一注册区域的流量调度配置信息，该流量调度配置信息中配置有数据请求到真实请求URL的映射。第一注册区域中的空闲域名信息所对应的域名地址即为真实请求URL的域名地址。
具体地，第一注册区域中配置有多个服务器，不同的服务器对应不同的域名，在获取到数据请求时，可以检测第一注册区域中的服务器负载量，从中确定出当前处于空闲状态的域名以及该域名所对应空闲服务器。
步骤S3042，将空闲服务器确定为目标服务器，并将数据请求所产生的业务流量调度至空闲服务器。
在确定出空闲服务器后，将该空闲服务器作为提供流量调度的目标服务器，并将目标业务在第一注册区域中所产生的流量调度至空闲服务器。
在一些可选的实施方式中，上述方法还可以包括：
步骤a1，获取第一注册区域对应的默认域名。
步骤a2，当数据请求所产生的业务流量未能成功调度至空闲服务器时，将默认域名对应的默认服务器确定为目标服务器，并将数据请求所产生的业务流量调度至默认域名对应的默认服务器。
其中，默认服务器为预先指定的用于进行业务流量调度的服务器。
在拉取第一注册区域的流量配置信息确定出空闲服务器时，若由于服务器负载状况和网络情况不佳而导致数据请求所产生的业务流量未成功调度至空闲服务器时，则将该数据请求链接到默认域名所对应的默认服务器，由此目标业务所产生的业务流量仍然会调度到第一注册区域中的服务器，不会出现调度到其他区域服务器的情况。
以表1所示为例，若第一注册区域的16号服务器为空闲服务器，则将数据请求下发至真实请求域名：test1-16.XXX.com。如果下发失败，则默认请求到test1.XXX.com，同样还是请求到第一注册区域中的服务器，不会出现调度到其他区域中错误服务器的情况。
表1流量配置表
在该实施方式中，若第一注册区域所产生的业务流量未能成功调度至空闲服务器， 则将该业务流量调度至默认服务器，由此能够避免出现因服务器负载和网络情况不佳而调度到错误服务器的情况，保证了第一注册区域的业务流量能够调度到正确服务器，在一定程度上实现了第一注册区域中服务器调度的容错能力。
在一些可选的实施例方式中，上述方法还可以包括：
步骤S305，当第一注册区域与其他区域存在数据互通时，解析网关层接收到的业务流量所携带的区域标识。
对于允许数据区域互通的服务器区域中，其网关层的数据是互通的。若第一注册区域与其他区域之间存在数据互通，那么可能会存在其他区域的数据请求调度至第一注册区域的网关层。那么，在第一注册区域中网关层接收到的业务流量时，其可以解析该业务流量，获取其所携带的区域标识。
步骤S306，判断区域标识与网关层对应的服务器是否匹配。
将业务流量所携带的区域标识与网关层所对应的服务器区域进行比对，以确定两者是否相匹配，即确定该区域标识是否为网关层所对应的服务器区域。若区域标识与网关层对应的服务器不匹配，则执行步骤S308；若区域标识与网关层对应的服务器相匹配，则网关层直接将该业务流量调度至相应服务器即可。
步骤S307，当确定区域标识与网关层对应的服务器不匹配时，确定与区域标识相匹配的服务器。
当确定区域标识与网关层对应的服务器不匹配时，此时可以由网关层根据区域标识，确定出与该区域标识所匹配的服务器。
步骤308，将与区域标识相匹配的服务器确定为目标服务器，并将业务流量转发至与区域标识相匹配的目标服务器。
将与区域标识相匹配的服务器确定为目标服务器，由网关层将业务流量转发至与该区域标识所匹配的目标服务器上。例如，第一注册区域A1与区域C1之间是允许数据互通的，第一注册区域A1的区域标识为I，区域C1的区域标识为S，若携带有区域标识S的业务流量调度到第一注册区域A1中的服务器网关层，服务器网关层则会将该业务流量转发至区域标识S所对应的区域C1中的服务器，以在网关层将业务流量调度至正确服务器中。
本实施例提供的应用程序的流量调度方法，通过检测第一注册区域的服务器负载量，确定第一注册区域中的空闲服务器，以在同一区域内进行服务器的优化负载，实现同一 区域的流量调度。在数据互通的服务器区域中，当确定出业务流量所携带的区域标识与网关层所处的服务器不匹配时，网关层则能够将业务流量转发至相匹配的目标服务器，进一步保证了业务流量的精准调度。由此，通过多重流量调度实现了不同区域之间的灵活调度，同时保证了业务流量一定能够调度到正确的服务器。
在本实施例中还提供了一种应用程序的流量调度装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
本实施例提供一种应用程序的流量调度装置，如图4所示，包括：
区域获取模块401，用于获取应用程序的目标业务的第一注册区域以及目标对象的账户所处的第二注册区域。其中，第一注册区域为应用程序响应目标对象针对目标业务的注册操作所确定的，第二注册区域为应用程序响应目标对象的账号注册操作所确定的。
检测模块402，用于检测第一注册区域与第二注册区域是否相同。
域名确定模块403，用于当第一注册区域与第二注册区域不同时，基于第一注册区域与域名之间的映射关系，确定第一注册区域对应的目标域名。其中，该映射关系部署在应用程序中。
流量调度模块404，用于将目标业务产生的业务流量调度至目标域名信息所对应的目标服务器。
在一些可选的实施例方式中，上述区域获取模块401可以包括：
数据获取单元，用于获取应用程序的登录账户信息。
检测单元，用于检测登录账户信息对应的账户是否注册有目标业务。
信息调取单元，用于当确定当前账户注册有目标业务时，调取目标业务对应的业务信息，以及，根据业务信息，确定出目标业务所处的第一注册区域。
在一些可选的实施例方式中，上述区域获取模块401还可以包括：
注册单元，用于当确定当前账户未注册有目标业务时，进入目标业务的注册页面。其中，该注册页面中包括多个注册区域。
区域选择单元，用于响应于在注册页面中对注册区域的选择操作，基于选择操作确定第一注册区域。
在一些可选的实施方式中，上述装置还可以包括：
更新模块，用于当检测到注册区域和/或域名发生变化时，确定更新后的注册区域和/或域名，利用更新后的注册区域与域名，更新注册区域与域名之间的映射关系。
在一些可选的实施例方式中，上述流量调度模块403可以包括：
服务器负载检测单元，用于响应于针对目标业务在第一注册区域所产生的数据请求，基于数据请求检测第一注册区域的服务器负载量，确定第一注册区域中的空闲服务器。
调度单元，用于将空闲服务器确定为目标服务器，并将数据请求所产生的业务流量调度至空闲服务器。
在一些可选的实施例方式中，上述流量调度模块403还可以包括：
默认域名获取单元，用于获取第一注册区域对应的默认域名。
默认调度单元，用于当数据请求所产生的业务流量未能成功调度至空闲服务器时，将默认域名对应的默认服务器确定为目标服务器，并将数据请求所产生的业务流量调度至默认域名对应的默认服务器。其中，默认服务器为预先指定的用于进行业务流量调度的服务器。
在一些可选的实施例方式中，上述应用程序的流量调度装置还可以包括：
标识获取模块，用于当第一注册区域与其他归属区域存在数据互通时，解析网关层接收到的业务流量所携带的区域标识。
判断模块，用于判断区域标识与网关层对应的服务器是否匹配。
匹配模块，用于当确定区域标识与网关层对应的服务器不匹配时，确定与区域标识相匹配的服务器。
流量转发模块，用于将与区域标识相匹配的服务器确定为目标服务器，并将业务流量转发至与区域标识相匹配的目标服务器。
上述各个模块以及各个单元的更进一步的功能描述与上述对应实施例相同，在此不再赘述。
本实施例中的应用程序的流量调度装置是以功能单元的形式来呈现，这里的单元是指ASIC电路，执行一个或多个软件或固定程序的处理器和存储器，和/或其他可以提供上述功能的器件。
本实施例提供的应用程序的流量调度装置，通过在应用程序中部署注册区域与域名之间的映射关系，在第一注册区域与第二注册区域不同时，可以从应用程序中读取映射关系，确定第一注册区域所对应的目标域名信息，以将业务流量调度至目标域名信息所 对应的目标服务器。由此，业务流量的调度决策不依赖网络请求，在应用程序内就能确定出业务流量所归属区域对应的服务器，以将业务流量精准调度到期望服务器，实现了业务流量的有效异地调度。
本公开实施例还提供一种计算机设备，具有上述图4所示的应用程序的流量调度装置。
请参阅图5，图5是本公开可选实施例提供的一种计算机设备的结构示意图，如图5所示，该计算机设备包括：一个或多个处理器10、存储器20，以及用于连接各部件的接口，包括高速接口和低速接口。各个部件利用不同的总线互相通信连接，并且可以被安装在公共主板上或者根据需要以其它方式安装。处理器可以对在计算机设备内执行的指令进行处理，包括存储在存储器中或者存储器上以在外部输入/输出装置(诸如，耦合至接口的显示设备)上显示GUI的图形信息的指令。在一些可选的实施方式中，若需要，可以将多个处理器和/或多条总线与多个存储器和多个存储器一起使用。同样，可以连接多个计算机设备，各个设备提供部分必要的操作(例如，作为服务器阵列、一组刀片式服务器、或者多处理器系统)。图5中以一个处理器10为例。
处理器10可以是中央处理器，网络处理器或其组合。其中，处理器10还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路，可编程逻辑器件或其组合。上述可编程逻辑器件可以是复杂可编程逻辑器件，现场可编程逻辑门阵列，通用阵列逻辑或其任意组合。
其中，所述存储器20存储有可由至少一个处理器10执行的指令，以使所述至少一个处理器10执行实现上述实施例示出的方法。
存储器20可以包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需要的应用程序；存储数据区可存储根据计算机设备的使用所创建的数据等。此外，存储器20可以包括高速随机存取存储器，还可以包括非瞬时存储器，例如至少一个磁盘存储器件、闪存器件、或其他非瞬时固态存储器件。在一些可选的实施方式中，存储器20可选包括相对于处理器10远程设置的存储器，这些远程存储器可以通过网络连接至该计算机设备。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
存储器20可以包括易失性存储器，例如，随机存取存储器；存储器也可以包括非易失性存储器，例如，快闪存储器，硬盘或固态硬盘；存储器20还可以包括上述种类的存 储器的组合。
该计算机设备还包括输入装置30和输出装置40。处理器10、存储器20、输入装置30和输出装置40可以通过总线或者其他方式连接，图5中以通过总线连接为例。
输入装置30可接收输入的数字或字符信息，以及产生与该计算机设备的用户设置以及功能控制有关的键信号输入，例如触摸屏、小键盘、鼠标、轨迹板、触摸板、指示杆、一个或者多个鼠标按钮、轨迹球、操纵杆等。输出装置40可以包括显示设备、辅助照明装置(例如，LED)和触觉反馈装置(例如，振动电机)等。上述显示设备包括但不限于液晶显示器，发光二极管，显示器和等离子体显示器。在一些可选的实施方式中，显示设备可以是触摸屏。
该计算机设备还包括通信接口，用于该计算机设备与其他设备或通信网络进行数据通信。
本公开实施例还提供了一种计算机可读存储介质，上述根据本公开实施例的方法可在硬件、固件中实现，或者被实现为可记录在存储介质，或者被实现通过网络下载的原始存储在远程存储介质或非暂时机器可读存储介质中并将被存储在本地存储介质中的计算机代码，从而在此描述的方法可被存储在使用通用计算机、专用处理器或者可编程或专用硬件的存储介质上的这样的软件处理。其中，存储介质可为磁碟、光盘、只读存储记忆体、随机存储记忆体、快闪存储器、硬盘或固态硬盘等；进一步地，存储介质还可以包括上述种类的存储器的组合。可以理解，计算机、处理器、微处理器控制器或可编程硬件包括可存储或接收软件或计算机代码的存储组件，当软件或计算机代码被计算机、处理器或硬件访问且执行时，实现上述实施例示出的方法。
本公开实施例还提供了一种计算机程序产品，其包括可由至少一个处理器10执行的指令，以使所述至少一个处理器10执行实现上述实施例示出的方法。本公开实施例还提供了一种计算机程序，该计算机程序包括可由至少一个处理器10执行的指令，以使所述至少一个处理器10执行实现上述实施例示出的方法。
虽然结合附图描述了本公开的实施例，但是本领域技术人员可以在不脱离本公开的精神和范围的情况下做出各种修改和变型，这样的修改和变型均落入由所附权利要求所限定的范围之内。

Claims (12)

  1. 一种应用程序的流量调度方法，包括：
    获取应用程序的目标业务的第一注册区域以及目标对象的账户所处的第二注册区域，所述第一注册区域为所述应用程序响应目标对象针对所述目标业务的注册操作所确定的，所述第二注册区域为应用程序响应所述目标对象的账号注册操作所确定的；
    检测所述第一注册区域与所述第二注册区域是否相同；
    响应于所述第一注册区域与所述第二注册区域，基于所述第一注册区域与域名之间的映射关系，确定所述第一注册区域对应的目标域名，所述映射关系部署在所述应用程序中；
    将所述目标业务产生的业务流量调度至所述目标域名对应的目标服务器。
  2. 根据权利要求1所述的方法，其中，获取应用程序的目标业务的第一注册区域，包括：
    获取所述应用程序的登录账户信息；
    检测所述登录账户信息对应的账户是否注册有所述目标业务；
    响应于确定所述账户注册有所述目标业务，调取所述目标业务对应的业务信息，以及，根据所述业务信息，确定所述目标业务所处的所述第一注册区域。
  3. 根据权利要求2所述的方法，还包括：
    响应于确定所述账户未注册有所述目标业务，进入所述目标业务的注册页面，所述注册页面中包括多个注册区域；
    响应于在所述注册页面中对所述注册区域的选择操作，基于所述选择操作确定所述第一注册区域。
  4. 根据权利要求1-3中任一项所述的方法，还包括：
    响应于检测到所述注册区域和/或所述域名发生变化，确定更新后的注册区域和/或域名；
    利用更新后的注册区域与域名，更新注册区域与域名之间的映射关系。
  5. 根据权利要求1-4中任一项所述的方法，其中，将所述目标业务产生的业务流量调度至所述目标域名对应的目标服务器，包括：
    响应于针对所述目标业务在第一注册区域所产生的数据请求，基于所述数据请求检测所述第一注册区域的服务器负载量，确定所述第一注册区域中的空闲服务器，所述空闲服务器为服务器负载量低于预设阈值的服务器；
    将所述空闲服务器确定为所述目标服务器，并将所述数据请求所产生的业务流量调度至所述空闲服务器。
  6. 根据权利要求5所述的方法，还包括：
    获取所述第一注册区域对应的默认域名；
    响应于所述数据请求所产生的业务流量未能成功调度至所述空闲服务器，将默认域名对应的默认服务器确定为目标服务器，并将所述数据请求所产生的业务流量调度至所述默认域名对应的默认服务器，所述默认服务器为预先指定的用于进行所述业务流量调度的服务器。
  7. 根据权利要求1-6中任一项所述的方法，还包括：
    响应于所述第一注册区域与其他区域存在数据互通，解析网关层接收到的所述业务流量所携带的区域标识；
    判断所述区域标识与所述网关层所对应的服务器是否匹配；
    响应于确定所述区域标识与所述网关层对应的服务器不匹配，确定与所述区域标识相匹配的服务器；
    将与所述区域标识相匹配的服务器确定为目标服务器，并将所述业务流量转发至与所述区域标识相匹配的服务器。
  8. 一种应用程序的流量调度装置，包括：
    区域获取模块，用于获取应用程序的目标业务的第一注册区域以及目标对象的账户所处的第二注册区域，所述第一注册区域为所述应用程序响应目标对象针对所述目标业务的注册操作所确定的，所述第二注册区域为应用程序响应所述目标对象的账号注册操作所确定的；
    检测模块，用于检测所述第一注册区域与所述第二注册区域是否相同；
    域名确定模块，用于响应于所述第一注册区域与所述第二注册区域不同，基于所述第一注册区域与域名之间的映射关系，确定所述第一注册区域对应的目标域名，所述映射关系部署在所述应用程序中；
    流量调度模块，用于将所述目标业务产生的业务流量调度至所述目标域名对应的目标服务器。
  9. 一种计算机设备，包括：
    存储器和处理器，所述存储器和所述处理器之间互相通信连接，所述存储器中存储有计算机指令，所述处理器通过执行所述计算机指令，从而执行权利要求1至7中任一项所述的应用程序的流量调度方法。
  10. 一种计算机可读存储介质，其中，所述计算机可读存储介质上存储有计算机指令，所述计算机指令用于使计算机执行权利要求1至7中任一项所述的应用程序的流量调度方法。
  11. 一种计算机程序产品，包括计算机指令，所述计算机指令用于使计算机执行权利要求1至7中任一项所述的应用程序的流量调度方法。
  12. 一种计算机程序，包括计算机指令，所述计算机指令用于使计算机执行权利要求1至7中任一项所述的应用程序的流量调度方法。
PCT/CN2024/102313 2023-06-30 2024-06-28 应用程序的流量调度方法、装置、设备及存储介质 Ceased WO2025002329A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202310798556.9A CN119232701A (zh) 2023-06-30 2023-06-30 应用程序的流量调度方法、装置、设备及存储介质
CN202310798556.9 2023-06-30

Publications (1)

Publication Number Publication Date
WO2025002329A1 true WO2025002329A1 (zh) 2025-01-02

Family

ID=93937585

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/102313 Ceased WO2025002329A1 (zh) 2023-06-30 2024-06-28 应用程序的流量调度方法、装置、设备及存储介质

Country Status (3)

Country Link
US (1) US20250007876A1 (zh)
CN (1) CN119232701A (zh)
WO (1) WO2025002329A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110570282A (zh) * 2019-09-10 2019-12-13 腾讯科技（深圳）有限公司 跨区域资源转移方法、装置、设备及存储介质
US20210027261A1 (en) * 2019-07-25 2021-01-28 Incheon Metropolitan City System and method for operating region-originating development platform
CN115134412A (zh) * 2022-06-28 2022-09-30 中国工商银行股份有限公司 服务调用方法、装置、电子设备及计算机可读存储介质
CN116132377A (zh) * 2022-09-26 2023-05-16 北京有竹居网络技术有限公司 流量调度方法、装置、系统、终端设备及可读存储介质
CN117950828A (zh) * 2023-12-26 2024-04-30 马上消费金融股份有限公司 应用调用方法及装置、电子设备、计算机可读存储介质

Family Cites Families (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6484143B1 (en) * 1999-11-22 2002-11-19 Speedera Networks, Inc. User device and system for traffic management and content distribution over a world wide area network
US7627425B2 (en) * 2004-11-26 2009-12-01 Microsoft Corporation Location aware mobile-device software development
JP4464297B2 (ja) * 2005-03-10 2010-05-19 パナソニック株式会社 再生装置、再生方法、及び再生プログラム
US8762571B2 (en) * 2008-03-19 2014-06-24 Go Daddy Operating Company, LLC Interactive DNS for non-controlling party
US9015595B2 (en) * 2010-01-20 2015-04-21 Yahoo! Inc. Self-targeting local AD system
US8774169B2 (en) * 2010-04-20 2014-07-08 Qualcomm Incorporated Supporting a multimedia application based on network zone recognition
US20130263042A1 (en) * 2012-03-27 2013-10-03 Alexander Buening Method And System To Manage Multiple Applications and Corresponding Display Status On A Computer System Having A Touch Panel Input Device
US9678986B2 (en) * 2012-12-05 2017-06-13 Wgrs Licensing Company, Llc Systems and methods for registering, administering, and using non-locational identifiers as locational addresses through location name and identifier registries
US9282439B1 (en) * 2013-05-03 2016-03-08 Sprint Spectrum L.P. Systems and methods of wireless device push-to-talk registration
US9979674B1 (en) * 2014-07-08 2018-05-22 Avi Networks Capacity-based server selection
US10938919B1 (en) * 2015-09-15 2021-03-02 EMC IP Holding Company LLC Registering client devices with backup servers using domain name service records
US9908047B2 (en) * 2016-04-25 2018-03-06 Sony Interactive Entertainment America Llc User save data migration based on location information
US10805406B2 (en) * 2018-06-21 2020-10-13 Microsoft Technology Licensing, Llc Zone redundant computing services using multiple local services in distributed computing systems
US10728317B1 (en) * 2019-02-11 2020-07-28 Verizon Patent And Licensing, Inc. Usage-based server load balancing
FR3094518B1 (fr) * 2019-04-01 2021-02-26 Idemia Identity & Security France Procédé de détection de bots dans un réseau d’utilisateurs
CN110990868B (zh) * 2019-11-29 2023-02-10 花瓣云科技有限公司 应用登录及应用访问应用服务器的方法、电子设备
US11445352B2 (en) * 2020-02-05 2022-09-13 Jpmorgan Chase Bank, N.A. System and method for implementing a softphone emergency dialing architecture
WO2022012743A1 (en) * 2020-07-14 2022-01-20 Lenovo (Singapore) Pte. Ltd. Re-mapping a network profile
CN111738725B (zh) * 2020-07-31 2020-12-22 支付宝(杭州)信息技术有限公司 跨境资源转移真实性审核方法、装置及电子设备
US20220076251A1 (en) * 2020-09-08 2022-03-10 Joseph D. Hughes Payment card enabled distributed digital ledger system to handle security of both crypto and non-crypto transactions
US20250048213A1 (en) * 2021-10-04 2025-02-06 Lenovo (Singapore) Pte. Ltd. Adaptations based on a service continuity requirement
US12574464B2 (en) * 2023-02-20 2026-03-10 T-Mobile Innovations Llc Methods and systems to provide adaptable billing for devices within a geographic zone
US20250078073A1 (en) * 2023-08-30 2025-03-06 Mastercard International Incorporated Systems and methods for use in providing services across multiple regions

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210027261A1 (en) * 2019-07-25 2021-01-28 Incheon Metropolitan City System and method for operating region-originating development platform
CN110570282A (zh) * 2019-09-10 2019-12-13 腾讯科技（深圳）有限公司 跨区域资源转移方法、装置、设备及存储介质
CN115134412A (zh) * 2022-06-28 2022-09-30 中国工商银行股份有限公司 服务调用方法、装置、电子设备及计算机可读存储介质
CN116132377A (zh) * 2022-09-26 2023-05-16 北京有竹居网络技术有限公司 流量调度方法、装置、系统、终端设备及可读存储介质
CN117950828A (zh) * 2023-12-26 2024-04-30 马上消费金融股份有限公司 应用调用方法及装置、电子设备、计算机可读存储介质

Also Published As

Publication number Publication date
CN119232701A (zh) 2024-12-31
US20250007876A1 (en) 2025-01-02

Similar Documents

Publication Publication Date Title
CN110677405B (zh) 一种数据处理方法、装置、电子设备及存储介质
CN106572173B (zh) 一种配置信息更新方法、装置和系统
US10038788B1 (en) Self-learning adaptive routing system
US10999721B2 (en) Communication identifier binding processing method and terminal
CN109936587B (zh) 控制方法、控制装置、电子设备及存储介质
CN113366815B (zh) 网络资源请求方法、装置、电子设备以及存储介质
US20190158626A1 (en) Method, apparatus and computer readable storage medium for processing service
US10348579B2 (en) Ubiquitous trouble management and E-service ecosystem for the internet of things
US9722890B2 (en) Integrated incident management for hybrid landscapes
US9329817B2 (en) Information processing apparatus, information processing method, and computer-readable storage medium
CN110753091A (zh) 一种云平台管理方法和装置
CN113722228A (zh) 软件系统测试方法及装置
US20140075456A1 (en) Information processing apparatus and method for controlling information processing apparatus
CN115840604B (zh) 数据处理方法、装置、电子设备和计算机可读存储介质
JP6163170B2 (ja) サービス連携システム、サービス連携装置、端末装置、サービス連携方法及びサービス連携プログラム
CN120909944A (zh) 测试代码生成方法及相关设备
CN104184771A (zh) 通话记录调用方法和设备
WO2025002329A1 (zh) 应用程序的流量调度方法、装置、设备及存储介质
US20190007520A1 (en) Electronic device and operation method thereof and server host device
CN118747237B (zh) 商品搜索方法、装置、计算机设备及存储介质
CN114048457A (zh) 多平台用户关系创建方法、装置、系统及存储介质
CN113641384A (zh) 一种探针的升级管理方法、装置和系统
US20210021604A1 (en) Cloud system, information processing system, and user registration method
US10891096B2 (en) Communication device, non-transitory computer-readable recording medium storing computer-readable instructions for communication device, and method performed by communication device
CN119484530A (zh) 基于redfish的异构服务器管理方法、装置及设备

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: 24830958

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE