WO2024109568A1

WO2024109568A1 - Service request processing method and apparatus, electronic device, and storage medium

Info

Publication number: WO2024109568A1
Application number: PCT/CN2023/131161
Authority: WO
Inventors: 屠强; 夏天; 管建池
Original assignee: 中兴通讯股份有限公司
Priority date: 2022-11-25
Filing date: 2023-11-13
Publication date: 2024-05-30
Also published as: CN118101764A

Abstract

The present application relates to the technical field of communications, and discloses a service request processing method and apparatus, an electronic device, and a storage medium. The method comprises: receiving a first service request; and when a first service discovery failure result corresponding to the first service request is stored, feeding back the first service discovery failure result.

Description

Business request processing method, device, electronic device and storage medium

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to a Chinese patent application filed with the Chinese Patent Office on November 25, 2022, with application number 202211497902.1 and invention name “Method, device, electronic device and storage medium for processing business requests”. The entire contents of the Chinese patent application are incorporated herein by reference.

Technical Field

The present application belongs to the field of communication technology, and specifically relates to a method, device, electronic device and storage medium for processing a service request.

Background technique

Service Discovery is the process by which a service consumer obtains the required service registration information from a network repository function (Net Repository Function, NRF) and calls the required service, where the service information stored in NRF is pre-registered by the service provider network function (NF). At present, conventional service discovery is that after receiving a service request, a service consumer (such as access and mobility management function (AMF), session management function (SMF), policy control function (PCF), unified data management function (UDM) and other network elements) will initiate a service discovery request corresponding to the service request to NRF. In the process of obtaining the required service registration information from NRF and calling the required service, service discovery failure may occur due to many reasons. When service discovery fails, NRF will reply with a response of service discovery failure.

After a service discovery failure, the consumer may initiate the same service discovery request to the NRF again. Repeated failed service discovery will have an impact on the network element, resulting in reduced performance of the network element.

Summary of the invention

The embodiments of the present application provide a method, device, electronic device and storage medium for processing a service request, which can solve the problem that repeated failed service discovery will have an impact on network elements, resulting in reduced performance of the network elements.

In a first aspect, an embodiment of the present application provides a method for processing a service request, the method comprising: receiving a first service request; and when a first service discovery failure result corresponding to the first service request is stored, feeding back the first service discovery failure result.

In a second aspect, an embodiment of the present application provides a device for processing a business request, the device comprising: a receiving module for receiving a first business request; an execution module for feeding back a first service discovery failure result when a first service discovery failure result corresponding to the first business request is stored.

In a third aspect, an embodiment of the present application provides an electronic device, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect.

In a fourth aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a flow chart of a method for processing a service request provided in an embodiment of the present application;

FIG2 is a flow chart of another method for processing a service request provided in an embodiment of the present application;

3 is a schematic diagram of the structure of a service request processing device provided in an embodiment of the present application;

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

Detailed ways

The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings in the embodiments of the present application. Clearly and completely described, it is obvious that the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present application.

The terms "first", "second", etc. in the specification and claims of this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and/or" in the specification and claims represents at least one of the connected objects, and the character "/" generally indicates that the objects associated with each other are in an "or" relationship.

The following, in conjunction with the accompanying drawings, describes in detail the service request processing method, device, electronic device and storage medium provided by the embodiments of the present application through specific embodiments and their application scenarios.

FIG1 shows a method for processing a service request provided by an embodiment of the present application. The method may be executed by a first network device for processing a service request. The method includes the following steps.

Step 102: Receive a first service request.

Specifically, the first network device may include but is not limited to an access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF) or a unified data management (UDM) network device, and the first network device is not specifically limited herein. The service request device may include a network device that can initiate a service request, such as a (Radio) Access Network (R)AN) or a user terminal (UE), and the service request device is not specifically limited herein. When the service request device initiates a first service request to the first network device, the first network device may receive the first service request sent by the service request device.

Step 104: When a first service discovery failure result corresponding to the first business request is stored, the first service discovery failure result is fed back.

Normally, after receiving the first business request, a first service discovery request corresponding to the first business request will be initiated to the second network device corresponding to the first business request. The first service discovery request is used to obtain the service registration information required for the first business request from the second network device and call the required service, wherein the second network device may be a network device that stores service registration information and services, such as a network repository function (Net Repository Function, NRF) network element. The second network device corresponding to the second business request is not specifically limited here. The service information and services are pre-registered in the second network device by the service provider network function (Network Function, NF) network element.

In an embodiment of the present application, the first network device may store the result of the failure of the first service discovery request. If the first network device stores the result of the failure of the first service discovery request, it means that before receiving the first service request, the first network device has also received other service requests, and the other service requests match the first service request. The first network device has initiated a service discovery request corresponding to the above-mentioned other service requests to the second network device, and the result of the service discovery request corresponding to the other service request is failure. The first network device can store the service discovery failure result. Since the above-mentioned other service requests match the first service request, the service discovery failure result corresponding to the above-mentioned other service requests is also the first service discovery failure result corresponding to the first service request. Therefore, when the first network device receives the first service request and finds that the first service discovery failure result corresponding to the first service request is stored, it can directly feedback the first service discovery failure result to the service request device, and there is no need to send the first service discovery request to the second network device corresponding to the first service request.

In an embodiment of the present application, by receiving a first business request, and in a case where a first service discovery failure result corresponding to the first business request is stored, the first service discovery failure result is fed back. Since the first service discovery failure result can be stored in advance, when it is determined that the first service discovery failure result corresponding to the first business has been stored, the first service discovery failure result can be directly fed back, and there is no need to send the first service discovery request to the second network device corresponding to the first service discovery request, thereby avoiding repeated impact of failed service discovery on the second network device corresponding to the first service discovery request, improving the performance of the second network device, and saving network resources.

In the embodiment of the present application, by receiving a first service request; storing the first service request In the case of a failure result of the first service discovery, the first service discovery failure result is fed back. Since the first service discovery failure result can be stored in advance, when it is determined that the first service discovery failure result corresponding to the first business has been stored, the first service discovery failure result can be directly fed back, thereby avoiding repeated impact of failed service discovery on the network element corresponding to the first business request, and improving the performance of the network element.

In one implementation, before the feedback of the first service discovery failure result, it also includes: receiving a second business request; sending a second service discovery request corresponding to the second business request to a second network device; and storing the second service discovery failure result when the second service discovery failure result sent by the second network device is received.

In an embodiment of the present application, after receiving the second service request sent by the service request device, if the first network device does not store the second service discovery failure result corresponding to the second service, the first network device may initiate a second service discovery request to the second network device corresponding to the second service request according to the second service request. If the second service discovery request is successful, the service registration information required for the second service request can be obtained from the second network device and the required service can be called. If the second service discovery request fails, an error response replied by the second network device will be received. If the second service discovery request fails, the second service discovery failure result can be stored, wherein the storage of the second service discovery failure result can be local storage or local cache, and the storage validity period of the second service discovery failure result can be between 0 and 86400 seconds. It should be understood that the above-mentioned storage validity period of the second service discovery failure result is exemplary and does not limit the storage validity period of the second service discovery failure result in the embodiment of the present application.

There may be many factors that cause the second service discovery request to fail. For example, the second network device does not allow the first network device to discover the service corresponding to the service discovery request, and the second network device returns a 403 Forbidden response; or due to an input data error in the Uniform Resource Locator (URL) query parameter in the service discovery request, the service discovery request fails in the second network device, and the second network device returns a 400 Bad Request status code; or due to an internal error in the second network device, the service discovery request fails on the second network device, and the second network device returns a 400 Bad Request status code. If the request fails, the second network device will return a 500 Internal Server Error status code; or if the service discovery returns successfully, but in the second network device, the configuration information (NF Profile List) of the NF instance providing the service list is empty, this scenario is also marked as a service discovery failure.

In this way, by receiving a second business request; sending a second service discovery request corresponding to the second business request to the second network device; and storing the second service discovery failure result when a second service discovery failure result sent by the second network device is received, and then when a business request matching the second business request is received again, there is no need to initiate a second service discovery request to the second network device again, and the stored second service discovery failure result can be directly fed back, thereby avoiding repeated impact of failed service discovery on the second network device corresponding to the first service discovery request, thereby improving the performance of the second network device and saving network resources.

In one implementation, when a first service discovery failure result corresponding to the first business request is stored, the first service discovery failure result is fed back, including: when the first business request matches the second business request, determining the second service discovery failure result as the result of the first service discovery; and feeding back the result of the first service discovery.

Specifically, if the received first service request matches the second service request, it means that the first service discovery request initiated based on the first service request also matches the second service discovery request initiated based on the second service request. Therefore, when the second service discovery failure result corresponding to the second service request is stored, the second service discovery failure result can be used as the result of the first service discovery to be fed back to the service request device, and there is no need to send the first service discovery corresponding to the first service request to the second network device.

In this way, when the first service request matches the second service request, the failure result of the second service discovery is determined as the result of the first service discovery; the result of the first service discovery is fed back, thereby avoiding the failed service discovery from repeatedly impacting the second network device corresponding to the first service discovery request, thereby improving the performance of the second network device and saving network resources.

In one implementation, if the received first service request matches the second service request, it indicates that the first service discovery request initiated according to the first service request matches the second service discovery request initiated according to the second service request. The second service discovery request also matches. Therefore, when the second service discovery failure result corresponding to the second business request is stored, it means that the result of the first service discovery request initiated according to the first business request will also fail. Therefore, the stored second service discovery request failure result can be determined as the first service discovery request failure result for feedback.

In this way, when the first service request matches the second service request, the second service discovery failure result is determined as the first service discovery failure result; the first service discovery failure result is fed back, thereby avoiding the failed service discovery from repeatedly impacting the second network device corresponding to the first service discovery request, thereby improving the performance of the second network device and saving network resources.

In one implementation, when a first service discovery failure result corresponding to the first business request is stored, the first service discovery failure result is fed back, including: when the first business request matches the second business request, the storage of the second service discovery failure result does not exceed a predetermined time threshold, and the number of times the second service discovery failure result is fed back does not exceed a first predetermined number threshold, determining the second service discovery failure result as the result of the first service discovery; and feeding back the result of the first service discovery.

Specifically, if the received first service request matches the second service request, the storage of the second service discovery failure result does not exceed the predetermined time threshold, and the number of times the second service discovery failure result is fed back does not exceed the first predetermined number threshold, it means that the first service discovery request initiated according to the first service request and the second service discovery request initiated according to the second service request also match. Therefore, when the second service discovery failure result corresponding to the second service request is stored, the second service discovery failure result can be fed back to the service request device as the result of the first service discovery request, and there is no need to send the first service discovery corresponding to the first service request to the second network device.

In this way, when the first service request matches the second service request, the storage of the second service discovery failure result does not exceed the predetermined time threshold, and the number of times the second service discovery failure result is fed back does not exceed the first predetermined number threshold, the second service discovery failure result is determined as the result of the first service discovery; the result of the first service discovery is fed back, thereby avoiding the failed service discovery from repeatedly impacting the second network device corresponding to the first service discovery request, improving the performance of the second network device, and saving network time. Network resources.

In one implementation, when the first service request matches the second service request, the storage of the second service discovery failure result does not exceed a predetermined time threshold, and the number of times the second service discovery failure result is fed back does not exceed a first predetermined number threshold, the second service discovery failure result is determined as the first service discovery failure result; and the first service discovery failure result is fed back.

Specifically, if the received first service request matches the second service request, the storage of the second service discovery failure result does not exceed the predetermined time threshold, and the number of times the second service discovery failure result is fed back does not exceed the first predetermined number threshold, it means that the first service discovery request initiated according to the first service request and the second service discovery request initiated according to the second service request also match. Therefore, when the second service discovery failure result corresponding to the second service request is stored, the second service discovery failure result can be fed back to the service request device as the result of the first service discovery request, that is, the second service discovery failure result is determined as the first service discovery failure result and fed back to the service request device, and there is no need to send the first service discovery corresponding to the first service request to the second network device.

In this way, when the first service request matches the second service request, the storage of the second service discovery failure result does not exceed the predetermined time threshold, and the number of times the second service discovery failure result is fed back does not exceed the first predetermined number threshold, the second service discovery failure result is determined as the first service discovery failure result; the first service discovery failure result is fed back, thereby avoiding the failed service discovery from repeatedly impacting the second network device corresponding to the first service discovery request, thereby improving the performance of the second network device and saving network resources.

In one implementation, after storing the second service discovery failure result, the method further includes: sending a first service discovery request corresponding to the first service request to a second network device when at least one of the following conditions is met; the storage time of the second service discovery failure result exceeds a predetermined time threshold; the number of times the second service discovery failure result is fed back exceeds a first predetermined number threshold.

Specifically, after the second service discovery failure result is stored, if the first service request is received and the first service request matches the second service request, that is, the first service request initiated according to the first service request If the service discovery request matches the second service discovery request initiated according to the second business request, it can be determined first whether the time for storing the second service discovery failure result exceeds the predetermined time threshold or the number of times the second service discovery failure result is fed back exceeds the first predetermined number threshold; if the time for storing the second service discovery failure result exceeds the predetermined time threshold or the number of times the second service discovery failure result is fed back exceeds the first predetermined number threshold, the first service discovery request corresponding to the first business request can be sent to the second network device.

In this way, when the storage time of the second service discovery failure result exceeds the predetermined time threshold or the number of times the second service discovery failure result is fed back exceeds the first predetermined number threshold, the first service discovery request corresponding to the first business request is sent to the second network device, which can reduce the impact of the service discovery request on the second network device and save network resources. In addition, the first service discovery request can be initiated to the second network device if the conditions are met, and then the service registration information and the service to be called required for the first business request can be obtained if the first service discovery is successful.

In one implementation, when a second service discovery failure result sent by the second network device is received, the second service discovery failure result is stored, including: when the number of times the second service discovery failure result is received exceeds a second predetermined number threshold, the second service discovery failure result is stored.

Specifically, after initiating a second service discovery request to the second network device, the received second service discovery failure results can be counted. The counting of the second service discovery failure results can be that the first network device counts the number of consecutive second service discovery failure results received. When the second service discovery request is initiated and the result of the second service discovery request is a failure, it is determined whether the counted number of second service discovery request failures exceeds a second predetermined number threshold. The second predetermined number threshold can be set according to actual needs and is not specifically limited here. If the counted number of second service discovery request failure results does not exceed the second predetermined number threshold, the second service discovery failure result will not be stored. If the counted number of second service discovery request failures exceeds the second predetermined number threshold, the second service discovery failure result can be stored.

In this way, when the number of times the second service discovery failure result is received exceeds the second predetermined number threshold, In this case, storing the second service discovery failure result can avoid erroneous storage due to a single service discovery failure.

FIG2 is a flow chart of another method for processing a service request provided in an embodiment of the present application. As shown in FIG2 , the method for processing a service request includes the following steps.

Step 1: Receive a second service request.

Specifically, in the embodiment of the present application, the first network device 202 may include but is not limited to a network device of an AMF network element, an SMF network element, a PCF network element or a UDM network element, and the first network device 202 is not specifically limited herein. The service request device 201 may include a network device such as an (R)AN or a user terminal that can initiate a service request, and the service request device 201 is not specifically limited herein. When the service request device 201 initiates a first service request to the first network device 202, the first network device 202 may receive the first service request sent by the service request device 201.

Step 2: Send a second service discovery request.

Specifically, the second network device 203 may be a network device including an NRF network element and the like storing service registration information and services, and the second network device 203 corresponding to the second service request is not specifically limited herein. The first network device 202 may initiate a second service discovery request to the second network device 203 corresponding to the second service request according to the second service request. If the second service discovery request is successful, the service registration information required for the second service request may be obtained from the second network device 203 and the required service may be called. If the second service discovery request fails, an error response replied by the second network device 203 may be received.

Step 3: Receive a second service discovery failure result.

Specifically, in the case where the second service discovery request fails, the second service discovery failure result sent by the second network device 203 can be received. For example, the second network device 203 does not allow the first network device 202 to discover the service corresponding to the service discovery request, and the second network device 203 will return a 403 Forbidden response; or due to an input data error in the URL query parameter in the service discovery request, the service discovery request fails in the second network device 203, and the second network device 203 will return a 400 Bad Request status code; or due to an internal error in the second network device 203, the service discovery request fails in the second network device 203, and the second network device 203 will return a 400 Bad Request status code. If the service discovery request on 203 fails, the second network device 203 will return a 500 Internal Server Error status code; or if the service discovery returns successfully, but in the second network device 203, the NF Profile List of the service list provided by the NF is empty, or the configuration information of the NF instance of the service list provided by the NF is empty, this situation is also marked as a service discovery failure.

Step 4: Store the second service discovery failure result.

Specifically, when a second service discovery failure result is received, the second service discovery failure result can be counted. The second service discovery failure result can be counted by the first network device 202 counting the number of second service discovery failure results received consecutively. When a second service discovery request is initiated and the reception of the second service discovery request fails, it is determined whether the counted number of second service discovery request failures exceeds a second predetermined number threshold. The second predetermined number threshold can be set according to actual needs and is not specifically limited here. If the counted number of second service discovery request failures does not exceed the second predetermined number threshold, the second service discovery failure result is not stored. If the counted number of second service discovery request failures exceeds the second predetermined number threshold, the second service discovery failure result can be stored. This can avoid erroneous storage caused by the failure of a single service discovery request.

Step 5: Receive a first service request.

Specifically, the first network device 202 may receive a first service request initiated by the service request device 201 .

Step 6: Feedback the result of the second service discovery failure.

Specifically, if the received first business request matches the second business request, the first service discovery request initiated according to the first business request also matches the second service discovery request. In the case where the second service discovery failure result is stored in the first network device 202, it can be determined whether the time for storing the second service discovery failure result exceeds the predetermined time threshold or whether the number of times the second service discovery failure result is fed back exceeds the first predetermined number threshold. If the time for storing the second service discovery failure result exceeds the predetermined time threshold or the number of times the second service discovery failure result is fed back exceeds the first predetermined number threshold, the first service discovery request corresponding to the first business request can be sent to the second network device 203. If the above conditions are not met, then when the first service request is received, the stored first service discovery failure result (second service discovery failure result) may be directly fed back to the service request device 201 .

Step 7: Receive the third service request.

Specifically, the first network device 202 may receive the third service request initiated by the service request device 201 .

Step 8: Send a third service discovery request.

Specifically, if the received third business request matches the second business request, the third service discovery request initiated based on the third business request also matches the second service discovery request. When the second service discovery failure result is stored in the first network device 202, it can be determined whether the time for storing the second service discovery failure result exceeds the predetermined time threshold or the number of times the second service discovery failure result is fed back exceeds the first predetermined number threshold. If the time for storing the second service discovery failure result exceeds the predetermined time threshold or the number of times the second service discovery failure result is fed back exceeds the first predetermined number threshold, the third service discovery request corresponding to the third business request can be sent to the second network device 203. If the above conditions are met, the third service discovery request can be sent to the second network device 203.

Step 9: Receive the third service discovery success result.

Specifically, when the third service discovery request is successful, a third service discovery success result is received, and the third service discovery success result may include service registration information required by the third service request and a service to be called.

Step 10: Feedback the successful result of the third service discovery.

Specifically, when the third service discovery success result is received, the third service discovery success result may be fed back to the service request device 201 .

In this way, when it is determined that the first service discovery failure result (second service discovery failure) corresponding to the first business has been stored, the first service discovery failure result can be directly fed back, and there is no need to send the first service discovery request to the second network device 203 corresponding to the first service discovery request, thereby avoiding the failed service discovery from repeatedly impacting the second network device 203 corresponding to the first service discovery request, improving the performance of the second network device 203, saving network resources, and, When the storage time of the second service discovery failure result exceeds the predetermined time threshold or the number of times the second service discovery failure result is fed back exceeds the first predetermined number of times, the received third service discovery request that matches the second service discovery request can be sent to the second network device 203 to obtain service registration information and services.

The method for processing the service request proposed in this application is further described below in conjunction with specific embodiments.

Example 1: (R)AN initiates a registration service request to AMF, and AMF initiates a service discovery request to NRF. However, NRF does not find a NF that matches the query parameters in the service discovery request, and NRF returns a "403 Forbidden" response. If the result of initiating a service discovery request for five consecutive times is still a failure, the service discovery failure result can be stored, and a validity period can be set for the storage, such as 86400 seconds. When a new service request triggers the above service discovery request, the service discovery failure result "403 Forbidden" is used for feedback within the storage validity period. When the storage validity period ends or the service discovery failure result has been fed back 1000 times in a row, the stored service discovery failure result becomes invalid, and service discovery can be directly initiated to NRF.

Example 2: (R)AN initiates a registration service request to SMF, and SMF sends a service discovery request to NRF. At this time, NRF replies "200OK", but the NF Profile List carried is empty, and it is judged that the service discovery failed. When the service discovery fails three times in a row, the service discovery failure result can be stored, and a validity period can be set for the storage, such as 43200 seconds. When a new service request triggers the service discovery request, the above-mentioned service discovery failure result "404" is used for feedback within the storage validity period. When the storage validity period ends or the service discovery failure result has been fed back 500 times in a row, the storage is invalid, and a service discovery request can be directly initiated to NRF.

Example 3: (R)AN initiates a registration service request to AMF, and AMF initiates a service discovery request to NRF. Due to an internal error in NRF, service discovery fails, and NRF returns a "500Internal Server Error" status code. When the service discovery request fails three times in a row, the service discovery failure result is stored, and a validity period can be set for the storage, such as 21600 seconds. When the storage validity period expires and a new service triggers the service discovery request, AMF can directly initiate a service discovery request to NRF even if the continuous feedback of the service discovery failure result does not reach the preset number of times.

Example 4: (R)AN initiates a registration service request to AMF, and SMF initiates a service discovery request to NRF. Due to the input data error of the URI query parameter in the service discovery request, the service discovery fails at NRF, and NRF returns a "400 Bad Request" status code. When the service discovery fails three times in a row, the service discovery failure result is stored, and a validity period is set for the storage, such as 43200 seconds. When the number of consecutive feedback service discovery failure results exceeds 200 times, the storage of the service discovery failure result will become invalid even if the storage validity period has not expired. At this time, SMF directly initiates service discovery to NRF. When the number of service discovery failures reaches 3 times again, the service discovery failure result is stored again.

It should be noted that the execution subject of the method for processing a business request provided in the embodiment of the present application may be a processing device for a business request, or a control module in the processing device for a business request for executing the method for processing a business request. In the embodiment of the present application, the processing device for processing a business request is taken as an example to illustrate the processing device for processing a business request provided in the embodiment of the present application.

Fig. 3 is a schematic diagram of the structure of a device for processing a service request according to an embodiment of the present invention. As shown in Fig. 3 , the device for processing a service request 300 comprises: a receiving module 310 and an executing module 320 .

The receiving module 310 is used to receive a first service request; the executing module 320 is used to feed back the first service discovery failure result when a first service discovery failure result corresponding to the first service request is stored.

In one implementation, the execution module 320 is further used to receive a second business request; send a second service discovery request corresponding to the second business request to a second network device; and store the second service discovery failure result when a second service discovery failure result sent by the second network device is received.

In one implementation, the execution module 320 is used to determine the second service discovery failure result as the result of the first service discovery when the first service request matches the second service request; and to feed back the result of the first service discovery.

In one implementation, the execution module 320 is configured to determine the second service discovery failure result as the result of the first service discovery if the first service request matches the second service request and the storage of the second service discovery failure result does not exceed a predetermined time threshold; Feedback the result of the first service discovery.

In one implementation, the execution module 320 is also used to send a first service discovery request corresponding to the first business request to the second network device when at least one of the following conditions is met; the storage time of the second service discovery failure result exceeds a predetermined time threshold; the number of times the first service discovery failure result is fed back exceeds a first predetermined number threshold.

In one implementation, the execution module 320 is configured to store the second service discovery failure result when the number of times the second service discovery failure result is received exceeds a second predetermined number threshold.

The processing device for the service request in the embodiment of the present application can be a device, or a component, integrated circuit, or chip in a terminal. The device can be a mobile electronic device or a non-mobile electronic device. Exemplarily, the mobile electronic device can be a mobile phone, a tablet computer, a laptop computer, a PDA, an in-vehicle electronic device, a wearable device, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a netbook or a personal digital assistant (personal digital assistant, PDA), etc., and the non-mobile electronic device can be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.

The service request processing device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

The service request processing device provided in the embodiment of the present application can implement each process implemented by the method embodiments of Figures 1 to 2, and will not be described again here to avoid repetition.

Optionally, as shown in Figure 4, an embodiment of the present application further provides an electronic device 400, including a processor 401 and a memory 402, and the memory 402 stores a program or instruction that can be executed on the processor 401, and when the program or instruction is executed by the processor 401, it implements: receiving a first business request; and in the case of storing a first service discovery failure result corresponding to the first business request, feeding back the first service discovery failure result.

In one implementation, before the first service discovery failure result is fed back, a second service request is received; a second service discovery request corresponding to the second service request is sent to a second network device; and upon receiving the second service discovery failure result sent by the second network device, the second service discovery failure result is stored.

In one implementation, when the first service request matches the second service request, the second service discovery failure result is determined as the result of the first service discovery; and the result of the first service discovery is fed back.

In one implementation, when the first service request matches the second service request and the storage of the second service discovery failure result does not exceed a predetermined time threshold, the second service discovery failure result is determined as the result of the first service discovery; and the result of the first service discovery is fed back.

In one implementation, after storing the second service discovery failure result, a first service discovery request corresponding to the first service request is sent to the second network device when at least one of the following conditions is met; the storage time of the second service discovery failure result exceeds a predetermined time threshold; the number of times the first service discovery failure result is fed back exceeds a first predetermined number threshold.

In one implementation, when the number of times the second service discovery failure result is received exceeds a second predetermined number threshold, the second service discovery failure result is stored.

The specific execution steps can refer to the various steps of the above-mentioned business request processing method embodiment, and can achieve the same technical effect. To avoid repetition, they will not be repeated here.

It should be noted that the electronic devices in the embodiments of the present application include: servers, terminals or other devices except terminals.

The above electronic device structure does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. For example, the input unit may include a graphics processing unit (GPU) and a microphone, and the display unit may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit includes at least one of a touch panel and other input devices. The touch panel is also called Other input devices may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here.

The memory can be used to store software programs and various data. The memory may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory may include a volatile memory or a non-volatile memory, or the memory may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. Volatile memory can be random access memory (Random Access Memory, RAM), static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDRSDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DRRAM).

The processor may include one or more processing units; optionally, the processor integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to the operating system, user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor.

An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned business request processing method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as ROM, RAM, magnetic disk or optical disk.

It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be noted that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM/RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.

The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

A method for processing a service request, applied to a first network device, comprising:

receiving a first service request;

In a case where a first service discovery failure result corresponding to the first business request is stored, the first service discovery failure result is fed back.
The processing method according to claim 1, wherein, before feeding back the first service discovery failure result, it further comprises:

receiving a second service request;

Sending a second service discovery request corresponding to the second service request to a second network device;

When the second service discovery failure result sent by the second network device is received, the second service discovery failure result is stored.
The processing method according to claim 2, wherein, when a first service discovery failure result corresponding to the first service request is stored, feeding back the first service discovery failure result comprises:

In a case where the first service request matches the second service request, determining the second service discovery failure result as the result of the first service discovery;

Feedback the result of the first service discovery.
The processing method according to claim 2, wherein, when a first service discovery failure result corresponding to the first service request is stored, feeding back the first service discovery failure result comprises:

If the first service request matches the second service request, the second service discovery failure result is stored for a period of time not exceeding a predetermined time threshold, and the number of times the second service discovery failure result is fed back does not exceed a first predetermined number of times threshold, determining the second service discovery failure result as the result of the first service discovery;

Feedback the result of the first service discovery.
The processing method according to claim 2, wherein the second service is found to be lost when storing the second service After the failure result is obtained, the method further comprises:

When at least one of the following conditions is met, sending a first service discovery request corresponding to the first service request to the second network device;

The storage time for storing the second service discovery failure result exceeds a predetermined time threshold;

The number of times that the second service discovery failure result is fed back exceeds a first predetermined number threshold.
The processing method according to claim 2, wherein, in the case of receiving the second service discovery failure result sent by the second network device, storing the second service discovery failure result comprises:

When the number of times the second service discovery failure result is received exceeds a second predetermined number threshold, the second service discovery failure result is stored.
A service request processing device, applied to a first network device, comprising:

A receiving module, configured to receive a first service request;

The execution module is used to feed back the first service discovery failure result when the first service discovery failure result corresponding to the first business request is stored.
An electronic device comprises a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method for processing a service request as described in any one of claims 1 to 6.
A readable storage medium stores a program or instruction, and when the program or instruction is executed by a processor, the steps of the method for processing a service request as described in any one of claims 1 to 6 are implemented.