WO2021057808A1

WO2021057808A1 - Method and apparatus for traffic control

Info

Publication number: WO2021057808A1
Application number: PCT/CN2020/117212
Authority: WO
Inventors: 李华; 段宝平; 乔佳伟
Original assignee: 华为技术有限公司
Priority date: 2019-09-27
Filing date: 2020-09-23
Publication date: 2021-04-01
Also published as: CN112583726B; CN112583726A

Abstract

The present application relates to the technical field of communications, and disclosed therein are a method and apparatus for traffic control, which are used to solve the problem wherein current traffic control means are unreasonable and inflexible. The method comprises: a service end receives a first message sent by a client, the first message being used to indicate that the client supports traffic control; and the service end sends to the client a second message for the first message, the second message comprising a first traffic control policy, the first traffic control policy being used to determine a first number of service request messages that the client is allowed to send to the service end, and the first number being an integer greater than or equal to 0. When determined that the client supports traffic control, the service end may issue to the client a traffic control policy, which is used to indicate the number of service request messages reported by the client. As such, the client may send a reasonable number of service request messages to the service end according to the indication of the service end.

Description

Method and device for flow control

Cross-references to related applications

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office, the application number is 201910924070.9, and the application name is "a method and device for flow control" on September 27, 2019, the entire content of which is incorporated into this application by reference in.

Technical field

The embodiments of the present application relate to the field of communication technologies, and in particular, to a method and device for flow control.

Background technique

The client sends a service request message to the server to request service. Due to the limited traffic processing capability of the server (the number of service request messages that can be processed in a period of time), if the client sends a large number of service request messages to the server, which exceeds the traffic processing capability of the server, the server will be congested. In order to avoid congestion, the server can return a service unavailable response to the client for some service request messages.

At present, the client can use the following schemes for flow control to avoid congestion on the server: the client can receive the number of non-service unavailable responses (service request messages successfully processed by the server), and get it based on experience A scaling factor for discarding service request messages. In the current flow control scheme, it is easy to drop too many service request messages or insufficient service request messages.

Summary of the invention

The embodiments of the present application provide a flow control method and device to solve the problem of unreasonable and inflexible current flow control methods.

In the first aspect, a method and device for flow control are provided. The execution subject of the method may be a server, and the server may receive a first message sent by a client, and the first message may be used to instruct the client Support flow control. The server may also send a second message for the first message to the client, the second message may include a first flow control policy, and the first flow control policy may be used to determine to allow the The first number of server request messages sent by the client to the server, where the first number is an integer greater than or equal to zero.

When determining that the client supports flow control, the server can issue a flow control policy to the client to indicate the number of service request messages reported by the client. In this way, the client can reasonably discard the service request messages according to the instructions of the server, that is, send a reasonable number of service request messages to the server. The business data can be processed flexibly and reasonably between the client and the server.

In a possible implementation, the first message sent by the client to the server may include the second flow control strategy being executed by the client, and the second flow control strategy may be used to determine the first flow control Strategy. The second flow control policy is used to determine a second number of service request messages that the client is allowed to send to the server, and the second number is an integer greater than or equal to 0.

The client not only reports that it supports flow control, but also reports the second flow control strategy being executed, so that the server can determine the first flow control strategy in combination with the second flow control strategy, making the first flow control strategy formulated for the client more consistent The traffic processing capability of the server and the business requirements of the client.

In a possible implementation, when the server receives the first message, if the server is in a congested state, the server may determine the first flow control strategy according to its own flow processing capability. The server can formulate the first flow control strategy for the client when it is not in a congested state, or when it is in a congested state, determine the first flow control strategy according to the current flow processing capability. Further, if the first message includes the second flow control strategy being executed by the client, the server can determine the first flow control strategy according to its own flow processing capability and the second flow control strategy.

In a possible implementation, the server may also receive a fifth message from an upper-level server, the fifth message may include a third flow control strategy, and the third flow control strategy may be used to determine permission to The third number of service request messages sent by the server to the superior server, where the third number is an integer greater than or equal to 0. Further, the server may determine the first flow control strategy according to the local strategy of the server and the third flow control strategy. Furthermore, if the first message includes the second flow control strategy being executed by the client, the server may determine the current flow control strategy according to the local strategy of the server, the second flow control strategy, and the third flow control strategy. Describe the first flow control strategy.

In a possible implementation, not only can the first flow control strategy be used to determine the first number of server request messages that the client is allowed to send to the server, the first flow control strategy can also include but not It is limited to one or more of the effective time of the first flow control strategy, the flow control method, the type of service request message, the generation time of the first flow control strategy, and the increment counter. Wherein, the flow control method includes: sending service request messages exceeding the first number to other servers for processing or discarding service request messages exceeding the first number; the increment counter is used to determine the first flow Whether the control strategy is the latest flow control strategy.

In a possible implementation, the second flow control strategy can not only be used to determine the second number of server request messages that the client is allowed to send to the server, but can also include but is not limited to: a second flow control strategy One or more of the effective time, the flow control mode, the type of service request message, the generation time of the second flow control strategy, and the increment counter. Wherein, the flow control method includes: sending service request messages exceeding the second number to other servers for processing or discarding service request messages exceeding the second number; the incremented counter is used to determine the second flow Whether the control strategy is the latest flow control strategy.

In a possible implementation, the third flow control strategy can not only be used to determine the second number of server request messages that the server is allowed to send to the superior server, but also include but not limited to: the third flow control strategy One or more of valid time, flow control mode, type of service request message, generation time of the third flow control strategy, and increment counter. Wherein, the flow control method includes: sending service request messages exceeding the third number to other higher-level servers for processing or discarding service request messages exceeding the third number; the increment counter is used to determine the third Whether the flow control strategy is the latest flow control strategy.

In a possible implementation, the first message may be a service request message based on a hypertext transport protocol (HTTP), and the second message may be a service response message based on HTTP.

In a possible implementation, the server may also receive a third message sent by the client, and the third message may include the first flow control policy being executed by the client and/or the client support Indication of flow control; the server may send a fourth message for the third message to the client in the case that the congestion state of the server is determined to be released, and the fourth message may be used to indicate the service The congestion state of the end is lifted.

In a possible implementation, the fourth message may include a first field for indicating the congestion state, and the server may indicate that the congestion state of the server is released through the value of the first field. For example, when the value is "00", it indicates that the congestion state is released, and when the value is "01", it indicates that it is in the congestion state.

The server informs the client in time whether it is in a congested state, so that the client can reasonably execute the flow control strategy.

In a possible implementation, the third message may be an HTTP-based service request message, and the fourth message may be an HTTP-based service response message.

In a possible implementation, the message that the server interacts with the client has integrity protection. For example, the first message has integrity protection, and before the server sends the second message to the client, The integrity of the first message may also be verified. After the integrity check of the first message is passed, the second message is sent. The second message may also have integrity protection.

In another example, the third message has integrity protection, and the server may also perform an integrity check on the third message before sending the fourth message to the client. After the verification is passed, the fourth message is sent. The fourth message may also have integrity protection.

The messages exchanged between the server and the client can be integrity protected to avoid attacks by attackers.

In a possible implementation, the server may also receive a sixth message sent by an upper-level server, and the sixth message may include a first field for indicating the congestion state, and the upper-level server may use the first field The value of indicates that the congestion state of the upper-level server is removed. The server may also determine that its own congestion state is released upon receiving the congestion state release of the superior server, and then send a fourth message to the client. The fourth message may be used to indicate that the congestion state of the server is released. .

In a possible implementation, the fifth message is an HTTP-based service request message, and the sixth message is an HTTP-based service request message.

In a second aspect, a flow control method is provided. The execution subject of the method may be a client, and the client may send a first message to the server, and the first message may be used to indicate that the client supports flow control. . The client may also receive a second message from the server for the first message, the second message may include a first flow control policy, and the first flow control policy may be used to determine that the client is allowed The first number of service request messages sent to the server, where the first number is an integer greater than or equal to 0. The client performs flow control according to the first flow control strategy.

The client informs the server of its ability to support flow control, and performs flow control according to the first flow control strategy indicated by the server. In this way, the client can reasonably discard the service request message, that is, send a reasonable number of service request messages to the server to ensure the reasonable progress of the business.

In a possible implementation, the first message received by the server may include a second flow control strategy being executed by the client, and the second flow control strategy may be used to determine the first flow control Strategy. The second flow control policy is used to determine a second number of service request messages that the client is allowed to send to the server, and the second number is an integer greater than or equal to 0.

The client can not only report that it supports flow control, but it can also inform the server of the second flow control strategy it is currently executing, so that the server can formulate the first flow control strategy for the client according to the second flow control strategy, so that The first flow control strategy is more in line with the flow processing capabilities of the server and more in line with the business needs of the client.

In a possible implementation, not only can the first flow control strategy be used to determine the first number of server request messages that the client is allowed to send to the server, the first flow control strategy can also include but not It is limited to at least one of the following: effective time of the first flow control strategy, flow control mode, type of service request message, generation time of the first flow control strategy, and increment counter; wherein, the flow control mode includes: Sending service request messages exceeding the first number to other servers for processing or discarding service request messages exceeding the first number, and the incrementing counter is used to determine whether the first flow control strategy is the latest flow control strategy .

In a possible implementation, if the first flow control policy includes the generation time of the first flow control policy, before the client performs flow control according to the first flow control policy, the client The terminal can also determine whether the generation time of the second flow control strategy being executed is earlier than the generation time of the first flow control strategy; if so, it can perform flow control according to the first flow control strategy; if not, then The flow control can be performed according to the second flow control strategy.

The client can determine the latest generation time according to the generation time of each flow control strategy, that is, the latest flow control strategy. The client performs flow control according to the latest flow control strategy to achieve a more reasonable processing of business data.

In a possible implementation, if the first flow control policy includes an incrementing counter, before the client performs flow control according to the first flow control policy, the client may also compare the first The increment counter in the flow control strategy and the increment counter of the second flow control strategy being executed determine to use the first flow control strategy.

The client can determine the latest flow control strategy according to the counter of each flow control strategy. The client performs flow control according to the latest flow control strategy to achieve a more reasonable processing of business data.

In a possible implementation, the first message may be an HTTP-based service request message, and the second message may be an HTTP-based service response message.

In a possible implementation, the client may also send a third message to the server, and the third message may include the second traffic control strategy being executed by the client and/or the client supporting traffic For an indication of control, the client may also receive a fourth message sent by the server for the third message, and the fourth message may be used to indicate that the congestion state of the server is released. The client no longer executes the first flow control strategy. The fourth message is sent by the server after receiving the first flow control policy after it is determined that the congestion state is removed.

The server informs the client in time whether it is in a congested state, and the client can reasonably execute the flow control strategy.

In a possible implementation, the third message may be a service request message based on HTTP, and the fourth message may be a service response message based on HTTP.

In a possible implementation, the message exchanged between the server and the client may have integrity protection. For example, the second message has integrity protection, and the client may perform flow control according to the first flow control policy. , You can also verify the integrity of the second message. After passing the integrity check of the second message, flow control is performed according to the first flow control strategy, and the first message may also have integrity protection.

In another example, the fourth message may have integrity protection, and the client may also perform an integrity check on the fourth message before determining that the first flow control policy is no longer executed. After passing the integrity check of the fourth message, it is determined that the first flow control strategy is no longer executed. The third message may also have integrity protection.

In a third aspect, a communication device is provided, and the communication device has the function of realizing the server in the foregoing method embodiment. These functions can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more functional modules corresponding to the above-mentioned functions.

In a fourth aspect, a communication device is provided, and the communication device has the function of realizing the client in the foregoing method embodiment. These functions can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more functional modules corresponding to the above-mentioned functions.

In a fifth aspect, a communication device is provided. The communication device may be the server in the foregoing method embodiment, or a chip set in the server. The communication device includes a transceiver and a processor, and optionally, a memory, where the memory is used to store a computer program or instruction, and the processor is respectively coupled with the memory and the transceiver. When the processor executes the computer program or instruction At this time, the communication device is caused to execute the method executed by the server in the foregoing method embodiment.

In a sixth aspect, a communication device is provided. The communication device may be the client in the foregoing method embodiment, or a chip set in the client. The communication device includes a transceiver and a processor, and optionally, a memory, where the memory is used to store a computer program or instruction, and the processor is respectively coupled with the memory and the transceiver. When the processor executes the computer program or instruction At this time, the communication device is caused to execute the method executed by the client in the foregoing method embodiment.

In a seventh aspect, a computer program product is provided. The computer program product includes: computer program code, which when the computer program code runs on a computer, causes the computer to execute any of the above-mentioned first aspect and any possible aspect of the first aspect The method executed by the server in the implementation.

In an eighth aspect, a computer program product is provided, the computer program product comprising: computer program code, when the computer program code runs on a computer, the computer can execute any of the above-mentioned second aspect and any of the possible aspects of the second aspect Implementation of the method executed by the client.

In a ninth aspect, the present application provides a chip system including a processor and a memory, the processor and the memory are electrically coupled; the memory is used to store computer program instructions; the processor , Used to execute part or all of the computer program instructions in the memory. When the part or all of the computer program instructions are executed, they are used to implement the first aspect and any one of the possible implementation methods of the first aspect. Features.

In a possible design, the chip system further includes a transceiver, and the transceiver is configured to send a signal processed by the processor or receive a signal input to the processor. The chip system can be composed of chips, and can also include chips and other discrete devices.

In a tenth aspect, a chip system is provided. The chip system includes a processor and a memory, the processor and the memory are electrically coupled; the memory is used for storing computer program instructions; the processor is used for In executing part or all of the computer program instructions in the memory, when the part or all of the computer program instructions are executed, they are used to implement the functions of the client in the foregoing second aspect and any possible implementation method of the second aspect.

In an eleventh aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program. When the computer program is executed, the first aspect and any possible implementation of the first aspect are implemented by The method executed by the server.

In a twelfth aspect, this application provides a computer-readable storage medium that stores a computer program, and when the computer program is executed, the second aspect and any possible implementation of the second aspect are realized In the method executed by the client.

In a thirteenth aspect, a communication system is provided. The system may include a server that executes the method described in any possible implementation of the first aspect and the first aspect, and executes the second aspect and the second aspect. Any possible implementation of the method described in the client.

Description of the drawings

FIG. 1 is a schematic diagram of an architecture provided in an embodiment of the application;

Figure 2 is a flow control flow chart provided in an embodiment of the application;

Figure 3 is a flow control flow chart provided in an embodiment of the application;

Figure 4 is a flow control flow chart provided in an embodiment of the application;

FIG. 5 is a schematic diagram of a communication device provided in an embodiment of this application;

FIG. 6 is a schematic diagram of a communication device provided in an embodiment of this application;

FIG. 7 is a schematic diagram of a communication device provided in an embodiment of this application;

FIG. 8 is a schematic diagram of a communication device provided in an embodiment of this application.

detailed description

The embodiments of the present application will be described in detail below in conjunction with the accompanying drawings.

In order to facilitate the understanding of the embodiments of the present application, some terms of the embodiments of the present application are explained below to facilitate the understanding of those skilled in the art.

1) Terminal, also called user equipment (UE), mobile station (MS), mobile terminal (MT), etc., is a way to provide users with voice and/or data connectivity device of. For example, terminal devices include handheld devices with wireless connection functions, vehicle-mounted devices, and Internet of Things devices. At present, terminal devices can be: mobile phones (mobile phones), tablets, notebook computers, handheld computers, mobile Internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality ( augmented reality (AR) equipment, industrial control (industrial control) wireless terminals, unmanned driving (self-driving) wireless terminals, remote medical surgery (remote medical surgery) wireless terminals, smart grid (smart grid) Wireless terminals, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, etc.

2) The client, the end that actively sends a service request message to the server, or the end that calls the service of the server.

3), the server, after receiving the service request message sent by the client, and the end that responds to the client, or the end that provides services to the client.

4) Integrity protection refers to the process of transmitting and storing information or data to ensure that the information or data is not changed without authorization or can be quickly discovered after the change. It should be noted that messages with integrity protection generally include message authentication code (MAC) information. When verifying messages with integrity protection, the same hash algorithm can be used for integrity-protected messages. Hash the information in the information, calculate the MAC information, compare the calculated MAC information with the MAC information in the integrity-protected message, to determine whether the two MAC information is the same, if the MAC information is the same, then the integrity check by.

In addition, it should be noted that the integrity-protected messages in this application may also have confidentiality protection and/or anti-replay protection, where confidentiality protection means that the information cannot be accessed by unauthorized individuals, entities, or processes. Disclosure of characteristics. Anti-replay protection means that the receiver receives repeated packets from the attacker.

5) Traffic processing capacity refers to the number of service request messages that can be processed in a period of time.

6) Congestion means that the number of service request messages received in a period of time exceeds the number of service request messages that can be processed.

The "and/or" in this application describes the association relationship of the associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone. This situation. The character "/" generally indicates that the associated objects before and after are in an "or" relationship.

The multiple involved in this application refers to two or more.

In the description of this application, words such as "first" and "second" are only used for the purpose of distinguishing description, and cannot be understood as indicating or implying relative importance, nor as indicating or implying order.

In addition, in the embodiments of the present application, the word "exemplary" is used to mean serving as an example, illustration, or illustration. Any embodiment or implementation described as an "example" in this application should not be construed as being more preferable or advantageous than other embodiments or implementations. To be precise, the term example is used to present the concept in a concrete way.

The embodiments of the present application provide a method and device for flow control. The method and device are based on the same technical idea. Since the principles of the method and device to solve the problem are similar, the implementation of the device and the method can be referred to each other. No longer.

The technical solutions of the embodiments of this application can be applied to various communication systems, such as long term evolution (LTE) systems, worldwide interoperability for microwave access (WiMAX) communication systems, and the fifth generation of the future (5th Generation, 5G) systems, such as new radio access technology (NR), and future communication systems.

Figure 1 is a schematic diagram of a possible communication system architecture applicable to this application, including: UE, (radio access network, (R)AN), UPF network element, DN network element, AUSF network element, AMF network elements, SMF network elements, NESSF network elements, NEF network elements, NRF network elements, PCF network elements, UDM network elements, and AF network elements, among which network elements can also be called functional entity equipment, UPF network elements, DN network elements, AUSF network elements, AMF network elements, SMF network elements, NESSF network elements, NEF network elements, NRF network elements, PCF network elements, UDM network elements, and AF networks may be core network network elements. In this network architecture, Nnssf is the service-based interface displayed by NESSF, Nausf is the service-based interface displayed by AUSF, Namf is the service-based interface displayed by AMF, Nsmf is the service-based interface displayed by SMF, and Nnef is displayed by NEF. Nnrf is a service-based interface displayed by NRF, Npcf is a service-based interface displayed by PCF, Nudm is a service-based interface displayed by UDM, and Naf is a service-based interface displayed by AF. Service-based interfaces can also be called service-oriented interfaces. Each network element can provide one or more service-oriented interface services, which are called by other network elements, and at the same time, the service-oriented interface services of other network elements will also be called.

N1 is the reference point between UE and AMF, N2 is the reference point between (R)AN and AMF, used for sending non-access stratum messages, etc.; N3 is the reference point between (R)AN and UPF, used for Transmit user plane data, etc.; N4 is the reference point between SMF and UPF, used to transmit information such as N3 connection tunnel identification information, data buffer indication information, and downlink data notification messages; N6 interface is between UPF and DN The reference point is used to transmit user plane data, etc.

Among them, the access and mobility management function (AMF) has the core network control plane function, providing user mobility management and access management functions, and SEAF has security authentication, management, and deduction security. Functions such as keys.

Network repository function (NRF) network element: used to store information about the network functions deployed in the core network, and provide discovery of network functions and services.

User plane function (UPF) network element: used for packet routing and forwarding, and quality of service (QoS) processing of user plane data, etc.

Data network (DN) network element: a network used to provide data transmission.

Authentication server function (authentication server function, AUSF) network element: used to implement user authentication and authentication.

Session Management Function (SMF) network element: Mainly used for session management, terminal device Internet protocol (IP) address allocation and management, selection of manageable user plane functions, policy control and charging function interfaces The end point and downlink data notification, etc.

Network exposure function (NEF) network element: used to safely open the services and capabilities provided by the 3GPP network function network element to the outside.

Policy control function (PCF) network element: a unified policy framework used to guide network behavior, and provide policy rule information for control plane function network elements (such as AMF, SMF network elements, etc.).

Application function (AF) network element: a device used to manage a terminal, and store attribute information of the managed terminal, such as location information and type of the terminal.

Unified data management (UDM) network elements: used to process user identification, access authentication, registration, and mobility management.

Network slice selection function (SSF): used to select a group of network slice instances to serve the UE.

It should be understood that the above-mentioned network architecture applied to the embodiment of the present application is only an example of a network architecture described from the perspective of a service-oriented architecture, and the network architecture applicable to the embodiment of the present application is not limited to this, and any network element that can implement the above-mentioned various network elements The network architectures of all functions are applicable to the embodiments of this application.

In order to facilitate the understanding of the embodiments of this application, the application scenarios of this application will be introduced next. The business scenarios described in the embodiments of this application are intended to more clearly illustrate the technical solutions of the embodiments of this application, and do not constitute the provision of the embodiments of this application. As for the limitation of technical solutions, those of ordinary skill in the art will know that with the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.

The UE side or the R(AN) side may request a service from the network element on the core network side, and the lower-level network element on the core network side may also send a service request message to the upper-level network element to request the service. As shown in Figure 1, in an example, after the AMF network element (subordinate network element) receives the request from the UE side or the R(AN) side, it can send a service request message to the UDM network element (upper network element). The element processes the service request message and feeds back the service response message to the AMF. After the AMF network element receives the service response message for the service request message, it feeds back the response to the UE side or the R(AN) side. In this application, the end that actively sends the service request message or the end that calls the service of the server is called the client. The end that receives the service request message sent by the client and feeds back the response to the client, or the end that provides services to the client is called the server. If the AMF network element directly sends a service request message to the UDM network element, the AMF network element is the client and the UDM network element is the server.

In another example, the AMF network element communicates with the UDM network element through the AUSF network element, the AMF network element sends a service request message to the AUSF network element, and the AUSF network element sends a service request message to the UDM network element. When the AUSF network element receives the service request message of the AMF network element, the AMF network element is the client and the AUSF network element is the server. When the AUSF network element sends a service request message to the UDM network element, the AUSF network element is the client and the UDM network element is the server. It can be seen that the role of the AUSF network element may change when it communicates with different network elements. It can be concluded that a network element can be either a client or a server.

The traffic processing capability of the server is limited. If the client sends a large number of service request messages to the server in a period of time, which exceeds the traffic processing capability of the server, the server will be congested. In order to avoid congestion, the server can return a service unavailable response to the client for some service request messages.

At present, the client can use the following schemes for flow control to avoid congestion on the server: the client can receive the number of non-service unavailable responses (service request messages successfully processed by the server), and the experience obtained The proportional coefficient is used to estimate the traffic processing capacity of the server for the client. The client discards the service request message that exceeds the traffic processing capability of the server for the client according to the estimated traffic processing capability of the server for the client.

In the current flow control scheme, the client cannot accurately estimate the real situation of the server, and it is prone to discard too many service request messages or insufficient service request messages. And the server does not know whether the reason for the decrease in client service request messages is that the client performs flow control or the service request messages sent by the client itself decrease. Generally, there are multiple clients requesting services from the same server. If one client performs flow control, other clients do not perform flow control. The server responds to each client with a response that the service is unavailable according to a unified strategy (for example, the proportion of service request messages received), which will cause more and more request messages to be discarded by clients that actively perform flow control. There are fewer and fewer service request messages that are normally processed.

For example, there are three clients c1, c2, and c3 respectively connected to the server. C1, c2, and c3 respectively send 200 service request messages to the server. The server determines that it cannot be successfully processed (such as discarding or discarding) according to its own traffic processing capabilities. The number of request messages for reply service unavailable is 60*50=300. The server can process 100 service request messages for c1, c2, and c3, respectively, and the other 100 can be discarded or reply with unavailable services. If c3 is performing flow control at this time, c3 will think that the server can only handle 100 service request messages, and even if c3 has 150, 200 or more service request messages in the next cycle, c3 will only send to the server About 100 service request messages, redundant service request messages are discarded. The server does not know that c3 is reporting 100 service request messages because of flow control. The server thinks that c3 only has 100 service request messages. The server only processes 60 service messages for the 100 service messages reported by c3. Then the client thinks that the server can only process 60 service request messages, and then only about 60 service request messages will be reported in the next cycle, and so on, will cause more and more request messages discarded by clients that actively perform flow control. If more, there are fewer and fewer service request messages that are normally processed.

Based on this, the embodiment of the present application provides a flow control method. The client informs the server that it has flow control capabilities. The server can issue a flow control policy to the client. The flow control policy is used to determine the server. The number of service request messages that the client is expected to send to the server, or the number of service request messages that the client is expected to discard. Then the client can send a reasonable number of service request messages to the server according to the flow control strategy issued by the server, so that both parties can process business data more flexibly and reasonably.

As shown in Figure 2, a schematic flow diagram of flow control is provided. The client shown in FIG. 2 may be the AMF network element shown in FIG. 1, and the corresponding server may be the UDM network element shown in FIG. 1. The client shown in FIG. 2 may be the AMF network element shown in FIG. 1, and the corresponding server may be the AUSF network element shown in FIG. 1. The client shown in FIG. 2 may be the AUSF network element shown in FIG. 1, and the corresponding server may be the UDM network element shown in FIG. 1. Here are just a few examples of the client and server. It is believed that those skilled in the art can reasonably think of other examples of the client and server according to the business requirements in actual applications.

Step 201: The client sends a first message to the server. Correspondingly, the server receives the first message sent by the client. The first message is used to indicate that the client supports flow control.

Because the lower-layer network element can send a service request message to the upper-layer network element to request services, the upper-layer network element can reply to the lower-layer network element with a service response message to provide services. Therefore, as a network element, the client can send a service request message to an upper network element (that is, the server) when receiving a service request message sent by a lower network element. The client can inform the server that it supports flow control when sending a service request message to the server. For example, the first message may be a service request message, and further, the first message may be a service request message based on HTTP. The first message may carry an indication that the client supports flow control to indicate that the client supports flow control. The indication that the client supports flow control can be carried in the header of the HTTP message, and can also be carried in the body of the HTTP message. The first message may also be other messages independent of the service request message, for example, define a new message. The first message is not limited in this application.

The client can not only report its ability to support flow control to the server, but the client can also report the flow control method it supports to the server, so that the server can formulate a more reasonable flow control strategy for the client, then the first message It may also include a flow control method supported by the client, where the flow control method supported by the client may be sending the service request message to other servers for processing, or discarding the service request message, or both.

If the client is currently executing the second flow control strategy, the client can also inform the server of the second flow control strategy being executed, so that the server can formulate a more reasonable flow control strategy for the client, and the first message can also include The second flow control strategy.

Step 202: The server sends a second message for the first message to the client. Correspondingly, the client receives the second message sent by the server, where the second message includes the first flow control policy.

After receiving the indication from the client that the client supports flow control, the server may formulate a first flow control strategy for the client, and send the formulated first flow control strategy to the client. The first flow control policy may be used to determine a first number of service request messages that the client is allowed to send to the server, and the first number is an integer greater than or equal to zero. The first number may refer to the number of service request messages allowed to be sent in a fixed time length, or the number of service request messages allowed to be sent in an unfixed time length. The fixed time length is, for example, one cycle, and the variable time length is, for example, the time interval for the server to feed back two service response messages to the client, or the time interval for two specific types of service response messages. The first quantity may be a relative quantity, for example, the first quantity may be a proportion of service request messages that the server instructs the client to reduce. The first quantity may also be an absolute quantity. For example, the first quantity may be a value at which the server indicates the number of service request messages sent by the client.

Further, the first flow control strategy may also include but is not limited to at least one of the following items:

The effective time of the first flow control strategy, the flow control mode, the type of service request message, and the generation time of the first flow control strategy, increment the counter.

The valid time may be a duration value, such as 3s, 10s, etc., or a time point, such as 23:20 on May 1, 2019. If the effective time is a duration value, it can be reflected by a specific time value, such as 10s, or by the number of cycles. For example, the server and the client can pre-appoint a period of 2s, and the effective time can be 5 cycle. The client can execute the first flow control strategy within the effective time of the first flow control strategy.

The flow control method includes: the client sends the service request messages exceeding the first number to other servers for processing or discards the service request messages exceeding the first number. The client can pre-configure the identifiers of other servers, and the client can also query the identifiers of other servers through the network repository function (NRF), or the traffic control policy can carry the identifiers of other servers.

The type of the service request message may be that the server instructs the client to perform flow control for those types of messages, and may not perform flow control for other types of messages. The type of the service request message may be, for example, a registration request message, a read subscription data request message, a subscription data change request message, etc. For details, please refer to the definition in the 3GPP specification.

The generation time of the first flow control strategy may be used to determine whether the first flow control strategy is the latest flow control strategy.

The increment counter of the first flow control strategy can also be used to determine whether the first flow control strategy is the latest flow control strategy.

The client can inform the server of the second flow control policy it is executing. The second flow control policy can not only be used to determine the second number of server request messages that the client is allowed to send to the server, but also include But not limited to: one or more of the effective time of the second flow control strategy, the flow control mode, the type of service request message, the generation time of the second flow control strategy, and the increment counter. Wherein, the flow control method includes: the client sends the service request messages exceeding the second number to other servers for processing or discards the service request messages exceeding the second number; the increment counter is used to determine the first 2. Whether the flow control strategy is the latest flow control strategy.

If the client reports the second flow control strategy in the first message, the first flow control strategy issued by the server to the client may include the effective time, flow control method, and service of the first flow control strategy described above. One or more of the type of the request message, the generation time, and the incremented counter may also be that the server informs the client of the difference between the first flow control strategy and the second flow control strategy. The client can then adjust the second flow control strategy being executed according to the difference notified by the server, and the adjusted flow control strategy will be the first flow control strategy.

The server can be in any state, as long as it receives an instruction from the client to support flow control, it will formulate the first flow control strategy for the client. In a specific example, the server can also formulate the first flow control strategy for the client only when it is in a congested state. After the server receives the indication from the client that the client supports flow control, if the server is currently in a congested state, the server can formulate a first flow control strategy for the client according to the server's flow processing capability. If the server is not currently in a congested state, the server can ignore the instructions sent by the client to support flow control.

The following specifically introduces the process of making the first flow control strategy for the client based on the flow processing capacity when the server is in a congested state:

The server can estimate its own load level in this cycle according to its multiple resource usage (such as CPU usage, message processing time, etc.). For example, if the CPU usage rate is greater than 98%, it is estimated that the current cycle is extremely high; the CPU usage rate is between 90% and 98%, and the current cycle is estimated to be a high load; the CPU usage rate is between 80% and 90%, and the cost is estimated The cycle is high load; the CPU usage rate is less than 80%, and it is estimated that this cycle is light load. For another example, if the message processing delay is greater than 3 seconds, it is estimated that the current cycle is extremely high load, and the message processing delay is 1 to 3 seconds, then the current cycle is estimated to be high load, and the message processing delay is less than 1 second, then the current cycle is estimated to be a high load. The cycle is light load. The load level of the server can be the highest level of the load corresponding to multiple resources, or it can be calculated comprehensively according to the load level of multiple resources.

Based on the number of service request messages processed in the previous cycle, the load level of the current cycle, the load level of the previous cycle, and the trend of load changes, the server can first estimate that it can be processed in this cycle (may be processed successfully, or may be processed) The number of service request messages that failed) is the estimated traffic processing capacity. The server can also estimate the number of service request messages that will be received in this cycle based on the number of service request messages received in the previous cycle.

When carrying out flow control, the load of the system can be kept as high as possible. For example, processing 1000 messages in the previous cycle, the system load is extremely high. The estimated load this week is also extremely high, and the load situation has not changed, and it is considered that 900 messages can be processed in this cycle (the load is extremely high, and the number of messages to be processed needs to be reduced). For another example, if 1000 messages were processed in the previous cycle, the system load is high, and the estimated load in this cycle is also extremely high, and the load level has not changed, then it is considered that 1000 messages can be processed in this cycle (the system is stable under high load, and it is not necessary. Need to adjust the message). For another example, if 1000 messages were processed in the previous cycle, the system load is high, the estimated load in this cycle is medium load, and the load level changes from high to medium, then it is considered that 1100 messages can be processed in this cycle (the system load is decreasing, you can Process some more messages).

Furthermore, the server can estimate the number of service request messages that cannot be processed based on the estimated number of service request messages that can be processed in this cycle and the number of service request messages that will be received in this cycle. The server can directly discard the service request message that cannot be processed, or return a failure to the client (for example, the service is unavailable).

The server can make the number of service request messages sent by all clients connected to it close to the estimated traffic processing capacity (the number of service request messages that can be processed). For example, the estimated traffic processing capacity of the server in this cycle is to process 1000 service request messages, and it is estimated that 2000 service request messages are received in this cycle, and it is estimated that 1000 service request messages cannot be processed. The server can instruct all clients connected to it to send a total of 1000 service request messages.

In order to process more service request messages, the server can make the number of service request messages sent by all clients connected to it greater than the estimated traffic processing capacity. For example, the server multiplies the number of service request messages that it can process by a ratio value to indicate the total number of service request messages sent by all clients. The ratio value is generally greater than 1, for example, 1.1, 1.2, and so on. For example, the estimated traffic processing capacity of the server in this cycle is to process 1000 service request messages, and it is estimated that 2000 service request messages are received in this cycle, and it is estimated that 1000 service request messages cannot be processed. The server can instruct all clients connected to it to send a total of 1200 service request messages, and the ratio is 1.2. That is, the server can instruct the client to discard 800 service request messages for 1000 service request messages that are estimated to be unable to be processed. Among the 1200 messages sent by the client, the server can return 200 failures according to its own traffic processing capability, or the server can send the 200 service request messages to other servers for processing after receiving the 200 service request messages, or the server can indicate all connected to it. The client sends a total of 1200 service request messages, and can also instruct the client to send service request messages to other servers to disperse the pressure on the current server.

If the load on the server in this cycle is higher than the load in the previous cycle, it means that the number of service request messages that the server has caused the client to discard is not large enough, and the client can discard more service request messages in the next cycle. For example, in this cycle, the client is allowed to discard 60% of service request messages, and the client can be allowed to discard 80% of service request messages in the next cycle.

If the load of the current cycle is significantly reduced compared to the load of the previous cycle, for example, the load changes from a high load to a low load, the server can instruct the client to discard a smaller number of service request messages in the next cycle, or even not to discard service request messages. When the server develops a flow control strategy for the client, it can not only consider the current load level, but also the changing trend of the load level.

The second message delivered by the server to the client may be a service response message, and further, the second message may be a service response message based on HTTP. The first flow control policy can be carried in the header of the HTTP message, for example, the extended Retry-After header, or non-standard headers such as X-headers, can also be in the body of the HTTP message carry. The second message may also be another message independent of the service response message, for example, a new message is defined. The first message is not limited in this application.

In order to avoid an attacker’s attack, the client can protect the integrity of the first message. After receiving the first message, the server can perform an integrity check on the first message. After the integrity check passes, Then formulate the first flow control strategy for the client. If the integrity check of the first message fails, the server can ignore the first message, or inform the client that there is an attacker.

Step 203: The client performs flow control according to the first flow control strategy.

After the client determines the first number of service request messages allowed to be sent to the server according to the first flow control policy, it can send about the first number of service request messages to the server. In order to achieve the purpose of reasonably discarding service request messages. It should be noted that the first number may be larger than the number of service request messages that the client needs to send, and the client does not need to discard the service request messages.

The client can also have some traffic control strategies locally, for example, some types of service request messages have higher priority.

If the first flow control policy issued by the server includes the type of service request message, that is, the server instructs the client to limit the flow of this type of service request message. If the client sets the priority of this type of message to a higher priority When it is high, the client may not discard this type of service request message. Or a certain session is in progress, even if the server instructs the client to restrict the flow of the service request message of the session, in order to ensure the normal progress of the session, the client may not discard the subsequent service request message of the session.

The generation time of the first flow control strategy may be used to determine whether the first flow control strategy is the latest flow control strategy. If the first flow control strategy includes the generation time of the first flow control strategy, before the client performs flow control according to the first flow control strategy, the client may also determine the first flow control strategy being executed. 2. Whether the generation time of the flow control strategy is earlier than the generation time of the first flow control strategy, and if so, perform flow control according to the first flow control strategy. If not, flow control can be performed according to the second flow control strategy.

The client can determine the latest flow control strategy according to the generation time of each flow control strategy. The client performs flow control according to the latest flow control strategy to achieve a more reasonable processing of business data.

The increment counter of the first flow control strategy can also be used to determine whether the first flow control strategy is the latest flow control strategy. If the first flow control policy includes the increment counter, before the client performs flow control according to the first flow control policy, the client may also compare the increment in the first flow control policy The counter and the incremental counter of the second flow control strategy being executed determine which flow control strategy is used. For example, the larger the value of the increment counter, the later the flow control strategy, that is, the latest flow control strategy. Then, when the counter of the first flow control strategy is greater than the counter of the second flow control strategy, the first flow control strategy can be used.

If the flow control mode issued by the server is that the client sends service request messages exceeding the first number to other servers for processing. The flow control strategy can carry the identifiers of other servers. The client can also pre-configure the identifiers of other servers, and the client can also query the identifiers of other servers through the network repository function (NRF).

In order to avoid an attacker's attack and tampering with the first flow control strategy, the server can protect the integrity of the second message. If the second message has integrity protection, after receiving the second message, the client may first perform an integrity check on the second message, and after passing the integrity check, perform flow control according to the first flow control policy. If the integrity check of the first message fails, the client can ignore the first flow control policy in the second message, or inform the server that there is an attacker.

When performing integrity protection on the first message and the second message, the integrity protection key used can be a symmetric key preset between the server and the client, or an asymmetric key mechanism, such as using the server’s The certificate signs the first flow control policy.

The above has introduced the process of issuing the first flow control policy to the client when the server is in a congested state. With the passage of time, the congestion state of the server may be lifted, and the server may also issue an instruction to clear the congestion state to the client, and the client may reasonably report a service request message to the server.

Refer to Figure 3 to further introduce the flow control process:

Step 301 to step 303 are the same as step 201 to step 203, and the repetition will not be repeated.

Step 304: Optionally, the client sends a third message to the server. Correspondingly, the server receives the third message sent by the client. The third message may include the first flow control policy being executed by the client. And/or the client supports the instruction of the flow control strategy.

Step 305: The server determines that the congestion state is released, and sends a fourth message to the client. Accordingly, the client receives a fourth message, which is used to indicate that the congestion state of the server is released.

Step 306: The client determines that the first flow control strategy is no longer executed.

In an example, when the server determines that the congestion state is released, it may issue an indication of the congestion state release to all clients connected to the server.

In another example, in order to save signaling overhead, the server may send the congestion to the client after receiving the flow control policy sent by the client or the indication that the client supports the flow control policy, and when it determines that its congestion state is lifted Indication of status release. For example, step 304 and step 305 in FIG. 3.

In another example, the server may also save the flow control policy issued to the client for the client's identification. The server can monitor in real time whether the flow control strategy for each client is effective. If the congestion state of the server is released and it is monitored that certain flow control policies are still valid, the server can issue an indication of the congestion release to the clients whose flow control policies are still valid. For clients whose flow control policy is invalid, since the client no longer executes the flow control policy, the server may not issue an indication of the congestion state release to these clients.

In an example, the fourth message includes a first field for indicating the congestion state, and the value of the first field indicates that the congestion state of the server is released.

In another example, the server can indicate that the congestion state of the server is lifted by setting the effective time of the flow control policy to 0. For example, the fourth message may include a fourth flow control strategy, and the effective time of the fourth flow control strategy is zero.

The third message may be a service request message, and further, the third message may be a service request message based on HTTP. The first flow control policy and/or the indication that the client supports flow control may be carried in the header of the HTTP message, and may also be carried in the body of the HTTP message. The third message may also be another message independent of the service request message, for example, define a new message. The third message is not limited in this application.

In order to avoid an attack by an attacker, the client can perform integrity protection on the third message. If the third message has integrity protection, after receiving the third message, the server can perform an integrity check on the third message first, and after the integrity check is passed, the server can issue a congestion release for the client. Instructions. If the integrity check of the third message fails, the server can ignore the third message or inform the client that there is an attacker.

The fourth message may be a service response message, and further, the fourth message may be a service response message based on HTTP. For example, the fourth message may carry a fourth flow control policy, and the fourth flow control policy may be carried in the header of the HTTP message, such as an extended Retry-After header field, or a non-standard header field such as X -headers, can also be carried in the body of the HTTP message. In another example, the fourth message may also carry an identifier of the server's uncongested state, such as the value of a field. The fourth message may also be another message independent of the service response message, for example, a new message is defined. The fourth message is not limited in this application.

In order to avoid an attack by an attacker, the server can perform integrity protection on the fourth message. If the fourth message has integrity protection, after receiving the fourth message, the client may first perform an integrity check on the fourth message, and after the integrity check passes, it is determined that the first flow control strategy is no longer executed. If the integrity check of the first message fails, the client can ignore the indication of the server to release the congestion state in the fourth message, or inform the server that there is an attacker.

It should be noted that, according to the foregoing description, the flow control strategy may include a generation time and/or an increment counter. After receiving the second message, if the client determines to execute the first flow control strategy according to the generation time and/or incrementing counter of the first flow control side, the aforementioned third message includes the first flow control strategy; Time and/or increment the counter to determine not to execute the first flow control strategy, but to execute the second flow control strategy, then the aforementioned third message may include the second flow control strategy instead of the first flow control strategy. Of course, the third message may also include the second flow control strategy and the first flow control strategy.

In another example, the server can also act as a client to receive a third flow control policy sent by an upper-level server, where the third flow control policy is used to determine the service that the server is allowed to send to the upper-level server The third quantity of the request message, where the third quantity is an integer greater than or equal to zero. The server may formulate a first flow control policy for the client according to the local policy of the server and the third flow control policy.

As shown in Figure 4, a flow control flow diagram is provided. The client shown in FIG. 4 may be the AMF network element shown in FIG. 1, and the corresponding server may be the AUSF network element shown in FIG. 1. The upper-level server may be the UDM network element shown in Figure 1. Then the AUSF network element is the server for the AMF network element, and the AUSF network element is the client for the UDM network element. Here is only an example of the client, server, and upper-level server. It is believed that those skilled in the art can reasonably think of other examples of the client, server, and upper-level server according to the business requirements in actual applications.

Step 401: The client (AMF network element) sends a service request message to the server (AUSF network element). Correspondingly, the server (AUSF network element) receives the service request message sent by the client. The service request message includes Instruct the client (AMF network element) to support flow control.

Optionally, the service request message may also include a flow control mode supported by the AMF network element.

Step 402: The server (AUSF network element) acts as a client and sends a service request message to an upper server (UDM network element). The service request message includes instructions for instructing the client (AUSF network element) to support flow control. Instructions. Optionally, the service request message may also include a flow control mode supported by the AUSF network element.

Step 403: The UDM network element formulates a third flow control strategy for the AUSF network element.

For example, when the UDM network element is determined to be in a congested state, the third flow control strategy is formulated for the AUSF network element according to the system capability.

Step 404: The UDM network element sends a service response message to the AUSF network element. Correspondingly, the AUSF network element receives the service response message sent by the UDM network element. The service response message includes the third flow control policy.

Step 405: The AUSF network element determines the first flow control strategy according to the third flow control strategy and the local strategy.

Specifically, the AMF network element reports the second flow control strategy being executed by the AMF network element to the AUSF network element, and the AUSF network element determines the first flow control strategy according to the third flow control strategy and the local strategy, and the second flow control side. .

The following specifically introduces the process of determining the first flow control strategy by the AUSF network element according to the third flow control strategy and the local strategy:

For example, the third flow control strategy is that the UDM network element instructs the AUSF network element to send 1000 service request messages. For example, it may send 1000 messages in one cycle, and one cycle may be, for example, 1s. The AUSF network element expects to receive 1500 service request messages in this cycle, of which 500 are high-priority non-discardable messages, and 1000 are low-priority messages that can be discarded. Then the AUSF network element can send 500 messages to the UDM network element. High priority messages and 500 low priority messages.

In this scenario, the AUSF network element needs to discard 500 low-priority messages. The local policy of the AUSF network element can be, for example, that it discards the number of service request messages sent to the UDM network element and requires lower-level clients to reduce the number of messages sent to the AUSF network element. The ratio of the number of service request messages may be 1:1, 1:2, 1.5, etc., for example. If the AUSF network element itself discards and requires AMF to reduce the number of messages sent is 1:1, the AUSF network element can instruct all AMF network elements connected to the AUSF network element to send a total of 750 low-priority messages and all 500 messages in the next period. High priority message.

Step 406: The AUSF network element sends a service response message to the AMF network element. Correspondingly, the AMF network element receives the service response message sent by the AUSF network element. The service response message includes the first flow control policy.

Step 407: The AMF network element may perform flow control according to the first flow control strategy.

Further, optionally, step 408: the AMF network element may also send a service request message to the AUSF network element. Correspondingly, the AUSF network element receives the service request message sent by the AMF network element, and the service request message includes the AMF An indication that the network element supports flow control and/or the first flow control strategy being executed by the AMF network element.

Optionally, step 409: the AUSF network element sends a service request message to the UDM network element, and correspondingly, the UDM network element receives the service request message sent by the AUSF network element, and the service request message includes that the AUSF network element supports flow control The instructions and/or the third flow control strategy.

The AUSF network element plays the role of an intermediate node between the AMF network element and the UDM network element. The process of determining the third flow control strategy by the AUSF network element according to the first flow control strategy may be the reverse process of the above step 405.

Step 410: The UDM network element may send a service response message to the AUSF network element when it is determined that the congestion is removed. Correspondingly, the AUSF network element receives the service response message sent by the UDM network element, and the service response message is used to instruct the UDM network The meta-congestion state is removed.

Step 411: After the AUSF network element receives the indication that the congestion state of the UDM network element is released, it can no longer execute the third flow control strategy. Under normal circumstances, the AUSF network element does not need to perform flow control on the AMF anymore, then the AUSF network element industry A service response message can be sent to the AMF network element to indicate that the congestion state of the AUSF network element is released. AMF may no longer execute the first flow control strategy.

In FIG. 4, each network element can exchange information through a service request message and a service response message. The service request message can be a service request message based on HTTP, and the service response message can be a service response message based on HTTP. The service request message and service response message exchanged between the various network elements in FIG. 4 may have integrity protection, and the end receiving the message may perform integrity verification on it first, and then perform the corresponding process after the integrity verification is passed.

The HTTP-based service request messages and service response messages in the various embodiments provided above may be HTTP2.0-based service request messages and service response messages.

Based on the same technical concept as the above-mentioned flow control method, as shown in FIG. 5, a communication device 500 is provided, and the communication device 500 can perform each step performed by the server in the methods of FIG. 2, FIG. 3, and FIG. 4, In order to avoid repetition, it will not be detailed here. The communication device 500 may be a server or a chip applied to the server. The communication device 500 includes: a transceiver module 510, optionally, a processing module 520 and a storage module 530; the processing module 520 can be connected to the storage module 530 and the transceiver module 510 respectively, and the storage module 530 can also be connected to the transceiver module 510 :

The storage module 530 is used to store computer programs;

For example, the transceiver module 510 is configured to receive a first message sent by a client, where the first message is used to indicate that the client supports flow control; and send a message specific to the first message to the client The second message, the second message includes a first flow control strategy, the first flow control strategy is used to determine a first number of service request messages that the client is allowed to send to the device, and the first number is greater than Or an integer equal to 0.

In a possible implementation, the processing module 520 is configured to determine the first flow control strategy according to the flow processing capability of the device when the device is in a congested state.

In a possible implementation, the transceiver module 510 is further configured to receive a fifth message from an upper-level server, where the fifth message includes a third flow control strategy, and the third flow control strategy is used to determine permission to The third number of service request messages sent by the device to the upper-level server, where the third number is an integer greater than or equal to 0.

In a possible implementation, the processing module 520 is configured to determine the first flow control strategy according to the local strategy of the device and the third flow control strategy.

In a possible implementation, the transceiver module 510 is further configured to receive a third message sent by the client, where the third message includes the first flow control policy being executed by the client; and When the congestion state is released, a fourth message for the third message is sent to the client, where the fourth message is used to indicate that the congestion state of the device is released.

Based on the same technical concept as the above-mentioned flow control method, as shown in FIG. 6, a communication device 600 is provided, and the communication device 600 can perform the steps performed by the client in the methods of FIG. 2, FIG. 3, and FIG. 4, In order to avoid repetition, it will not be detailed here. The communication device 600 may be a client or a chip applied in the client. The communication device 600 includes: a transceiver module 610, optionally, a processing module 620 and a storage module 630; the processing module 620 can be connected to the storage module 630 and the transceiver module 610 respectively, and the storage module 630 can also be connected to the transceiver module 610 :

The storage module 630 is used to store computer programs;

For example, the transceiver module 610 is configured to send a first message to a server, the first message is used to indicate that the device supports flow control; and to receive a second message from the server for the first message Message, the second message includes a first flow control strategy, the first flow control strategy is used to determine a first number of service request messages that the device is allowed to send to the server, and the first number is greater than or equal to An integer of 0;

The processing module 620 is configured to perform flow control according to the first flow control strategy.

In a possible implementation, the first flow control strategy includes at least one of the following items:

The effective time of the first flow control strategy, the flow control method, the type of service request message, the generation time of the first flow control strategy, and the increment counter;

Wherein, the flow control method includes: sending service request messages exceeding the first number to other servers for processing or discarding service request messages exceeding the first number, and the increment counter is used to determine the first flow Whether the control strategy is the latest flow control strategy.

In a possible implementation, if the first flow control strategy includes the generation time of the first flow control strategy, the processing module 620 is configured to perform flow control according to the first flow control strategy. Before, it is also used to determine that the generation time of the second flow control strategy being executed is earlier than the generation time of the first flow control strategy.

In a possible implementation, if the first flow control strategy includes the increment counter, the processing module 620 is further used to: compare before performing flow control according to the first flow control strategy. The increment counter in the first flow control strategy and the increment counter in the second flow control strategy being executed determine to use the first flow control strategy.

In a possible implementation, the transceiver module 610 is further configured to send a third message to the server, where the third message includes the first flow control strategy being executed by the device; and to receive the service A fourth message for the third message of the terminal, where the fourth message is used to indicate that the congestion state of the server is released;

The processing module 620 is further configured to determine that the first flow control strategy is no longer executed.

FIG. 7 is a schematic block diagram of a communication device 700 according to an embodiment of the present application. It should be understood that the communication device 700 can execute each step performed by the server in the methods shown in FIG. 2, FIG. 3, and FIG. 4. In order to avoid repetition, the details are not described herein again. The communication device 700 includes: a processor 701 and a memory 703, and the processor 701 and the memory 703 are electrically coupled;

The memory 703 is used to store computer program instructions;

The processor 701 is configured to execute part or all of the computer program instructions in the memory. When the part or all of the computer program instructions are executed, the device receives a first message sent by a client, and the first message A message is used to indicate that the client supports flow control; and a second message for the first message is sent to the client, the second message includes a first flow control strategy, and the first flow control strategy is used to determine The first number of service request messages that the client is allowed to send to the device, where the first number is an integer greater than or equal to 0.

In a possible implementation, the processor 701 is configured to determine the first flow control strategy according to the flow processing capability of the device when the device is in a congested state.

In a possible implementation, the processor 701 is further configured to receive a fifth message from an upper-level server, where the fifth message includes a third flow control strategy, and the third flow control strategy is used to determine permission to The third number of service request messages sent by the device to the upper-level server, where the third number is an integer greater than or equal to 0.

In a possible implementation, the processor 701 is configured to determine the first flow control strategy according to the local strategy of the apparatus and the third flow control strategy.

In a possible implementation, the processor 701 is further configured to receive a third message sent by the client, where the third message includes the first flow control policy being executed by the client; and When the congestion state is released, a fourth message for the third message is sent to the client, where the fourth message is used to indicate that the congestion state of the device is released.

Optionally, it further includes: a transceiver 702 for communicating with other devices; for example, sending a second message and a fourth message to the client, and receiving a first message and a third message sent by the client.

It should be understood that the communication device 700 shown in FIG. 7 may be a chip or a circuit. For example, a chip or circuit can be installed in the server. The aforementioned transceiver 702 may also be a communication interface. The transceiver includes a receiver and a transmitter. Further, the communication device 700 may also include a bus system.

Among them, the processor 701, the memory 703, and the transceiver 702 are connected by a bus system. The processor 701 is used to execute the instructions stored in the memory 703 to control the transceiver to receive and send signals, and to complete the flow control method of the present application. step. The memory 703 may be integrated in the processor 701, or may be provided separately from the processor 701.

As an implementation manner, the function of the transceiver 702 may be implemented by a transceiver circuit or a dedicated chip for transceiver. The processor 701 may be implemented by a dedicated processing chip, a processing circuit, a processor, or a general-purpose chip.

FIG. 8 is a schematic block diagram of a communication device 800 according to an embodiment of the present application. It should be understood that the communication device 800 can execute each step executed by the client in the methods of FIG. 2, FIG. 3, and FIG. 4. In order to avoid repetition, details are not described herein again. The communication device 800 includes: a processor 801 and a memory 803, and the processor 801 and the memory 803 are electrically coupled;

The memory 803 is used to store computer program instructions;

The processor 801 is configured to execute part or all of the computer program instructions in the memory. When the part or all of the computer program instructions are executed, the device sends a first message to the server, and the first message For indicating that the device supports flow control; and receiving a second message from the server for the first message, where the second message includes a first flow control strategy, and the first flow control strategy is used to determine permission The first number of service request messages sent by the device to the server, where the first number is an integer greater than or equal to 0; and performing flow control according to the first flow control strategy.

In a possible implementation, if the first flow control strategy includes the generation time of the first flow control strategy, the processor 801 is configured to perform flow control according to the first flow control strategy. Before, it is also used to determine that the generation time of the second flow control strategy being executed is earlier than the generation time of the first flow control strategy.

In a possible implementation, if the first flow control strategy includes the increment counter, the processor 801 is further configured to: compare before performing flow control according to the first flow control strategy. The increment counter in the first flow control strategy and the increment counter in the second flow control strategy being executed determine to use the first flow control strategy.

In a possible implementation, the processor 801 is further configured to send a third message to the server, where the third message includes the first flow control strategy being executed by the device; and to receive the service A fourth message for the third message at the end, where the fourth message is used to indicate that the congestion state of the server is released; and it is determined that the first flow control strategy is no longer executed.

Optionally, it further includes: a transceiver 802 for communicating with other devices; for example, receiving the second message and the fourth message sent by the server, and sending the first message and the second message to the server.

It should be understood that the communication device 800 shown in FIG. 8 may be a chip or a circuit. For example, a chip or circuit can be installed in the client. The above-mentioned transceiver 802 may also be a communication interface. The transceiver includes a receiver and a transmitter. Further, the communication device 800 may also include a bus system.

Among them, the processor 801, the memory 803, and the transceiver 802 are connected by a bus system. The processor 801 is used to execute the instructions stored in the memory 803 to control the transceiver to receive and send signals, and complete the flow control method of the present application. step. The memory 803 may be integrated in the processor 801, or may be provided separately from the processor 801.

As an implementation manner, the function of the transceiver 802 may be implemented by a transceiver circuit or a dedicated transceiver chip. The processor 801 may be implemented by a dedicated processing chip, a processing circuit, a processor, or a general-purpose chip.

The processor may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP.

The processor may further include a hardware chip or other general-purpose processors. The aforementioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The above-mentioned PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (generic array logic, GAL) and other programmable logic devices , Discrete gates or transistor logic devices, discrete hardware components, etc. or any combination thereof. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.

It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. The volatile memory may be random access memory (Random Access Memory, RAM), which is used as an external cache. By way of exemplary but not restrictive description, many forms of RAM are available, such as 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, DDR SDRAM), Enhanced Synchronous Dynamic Random Access Memory (Enhanced SDRAM, ESDRAM), Synchronous Link Dynamic Random Access Memory (Synchlink DRAM, SLDRAM) ) And Direct Rambus RAM (DR RAM). It should be noted that the memories described in this application are intended to include, but are not limited to, these and any other suitable types of memories.

The embodiment of the present application provides a computer storage medium storing a computer program, and the computer program includes a method for performing the above-mentioned flow control.

The embodiment of the present application provides a computer program product containing instructions, which when running on a computer, causes the computer to execute the method for flow control provided above.

A person of ordinary skill in the art may realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed by hardware or software depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division, and there may be Other division methods, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual communication connections may be indirect couplings or communication connections through some interfaces, devices or units, and may be in electrical, mechanical, or other forms.

In addition, the units in the device embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

It is understandable that the processor in the embodiment of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (digital signal processors, DSP), and application specific integrated circuits. (application specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

The methods in the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented by software, it can be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer programs or instructions. When the computer program or instruction is loaded and executed on the computer, the process or function described in the embodiment of the present application is executed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer program or instruction may be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server integrating one or more available media. The usable medium may be a magnetic medium, such as a floppy disk, a hard disk, and a magnetic tape; it may also be an optical medium, such as a CD-ROM, a DVD; and it may also be a semiconductor medium, such as a solid state disk (SSD), random Access memory (random access memory, RAM), read-only memory (ROM), registers, etc.

Those skilled in the art should understand that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, this application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

This application is described with reference to flowcharts and/or block diagrams of methods, devices (systems), and computer program products according to embodiments of this application. It should be understood that each process and/or block in the flowchart and/or block diagram, and the combination of processes and/or blocks in the flowchart and/or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing equipment to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing equipment are generated It is a device that realizes the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device. The device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment. The instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

Although the preferred embodiments of the present application have been described, those skilled in the art can make additional changes and modifications to these embodiments once they learn the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the present application.

Obviously, those skilled in the art can make various changes and modifications to the embodiments of the present application without departing from the spirit and scope of the embodiments of the present application. In this way, if these modifications and variations of the embodiments of this application fall within the scope of the claims of this application and their equivalent technologies, this application is also intended to include these modifications and variations.

Claims

A flow control method, characterized in that the method includes:

The server receives a first message sent by the client, where the first message is used to indicate that the client supports flow control;

The server sends a second message for the first message to the client, the second message includes a first flow control policy, and the first flow control policy is used to determine that the client is allowed to send the service to the service The first number of service request messages sent by the terminal, where the first number is an integer greater than or equal to 0.
The method according to claim 1, wherein the first message comprises: a second flow control strategy being executed by the client.
The method of claim 1 or 2, further comprising:

When the server is in a congested state, the first flow control strategy is determined according to the flow processing capability of the server.
The method of claim 1 or 2, further comprising:

The server receives a fifth message from an upper-level server, the fifth message includes a third flow control policy, and the third flow control policy is used to determine the service request that the server is allowed to send to the upper-level server The third number of messages, where the third number is an integer greater than or equal to zero.
The method of claim 4, further comprising:

The server determines the first flow control strategy according to the local strategy of the server and the third flow control strategy.
The method according to any one of claims 1 to 5, wherein the first flow control strategy comprises at least one of the following items:

The effective time of the first flow control strategy, the flow control method, the type of service request message, the generation time of the first flow control strategy, and the increment counter;

Wherein, the flow control method includes: sending service request messages exceeding the first number to other servers for processing or discarding service request messages exceeding the first number; the increment counter is used to determine the first flow Whether the control strategy is the latest flow control strategy.
The method according to claim 1, characterized in that it further comprises:

Receiving, by the server, a third message sent by the client, where the third message includes the first flow control policy being executed by the client;

When determining that the congestion state is released, the server sends a fourth message for the third message to the client, where the fourth message is used to indicate that the congestion state of the server is released.
The method according to claim 7, wherein the fourth message includes a first field for indicating a congestion state, and the value of the first field indicates that the congestion state of the server is released.
A flow control method, characterized in that the method includes:

The client sends a first message to the server, where the first message is used to indicate that the client supports flow control;

The client receives a second message from the server for the first message, the second message includes a first flow control policy, and the first flow control policy is used to determine that the client is allowed to send the service to the service A first number of service request messages sent by the terminal, where the first number is an integer greater than or equal to 0;

The client performs flow control according to the first flow control strategy.
The method according to claim 9, wherein the first message comprises: a second flow control strategy being executed by the client, and the second flow control strategy is used to determine the first flow control strategy .
The method according to claim 9 or 10, wherein the first flow control strategy includes at least one of the following items:

The effective time of the first flow control strategy, the flow control method, the type of service request message, the generation time of the first flow control strategy, and the increment counter;

Wherein, the flow control method includes: sending service request messages exceeding the first number to other servers for processing or discarding service request messages exceeding the first number, and the increment counter is used to determine the first flow Whether the control strategy is the latest flow control strategy.
The method of claim 11, wherein if the first flow control strategy includes the generation time of the first flow control strategy, the client is performing flow control according to the first flow control strategy. Before, it also included:

The client determines that the generation time of the second flow control strategy being executed is earlier than the generation time of the first flow control strategy.
The method of claim 11, wherein if the first flow control strategy includes the increment counter, before the client performs flow control according to the first flow control strategy, the method further comprises:

The client compares the increment counter in the first flow control strategy with the increment counter of the second flow control strategy being executed, and determines to use the first flow control strategy.
The method of claim 9, further comprising:

Sending, by the client, a third message to the server, where the third message includes the first flow control policy being executed by the client;

Receiving, by the client, a fourth message from the server for the third message, where the fourth message is used to indicate that the congestion state of the server is released;

The client no longer executes the first flow control strategy.
The method according to claim 14, wherein the fourth message includes a first field for indicating a congestion state, and the value of the first field indicates that the congestion state of the server is released.
A communication device, characterized in that the device comprises:

The transceiver module is configured to receive a first message sent by a client, the first message is used to indicate that the client supports flow control; and a second message for the first message is sent to the client, the The second message includes a first flow control policy, and the first flow control policy is used to determine a first number of service request messages that the client is allowed to send to the device, and the first number is an integer greater than or equal to 0.
The apparatus according to claim 16, wherein the first message comprises: a second flow control strategy being executed by the client.
The device according to claim 16 or 17, further comprising:

The processing module is configured to determine the first flow control strategy according to the flow processing capability of the device when the device is in a congested state.
The device according to claim 16 or 17, wherein the transceiver module is further configured to receive a fifth message from an upper-level server, the fifth message including a third flow control strategy, and the third flow control The policy is used to determine a third number of service request messages that the device is allowed to send to the upper-level server, and the third number is an integer greater than or equal to 0.
The device of claim 19, further comprising:

The processing module is configured to determine the first flow control strategy according to the local strategy of the device and the third flow control strategy.
The device according to any one of claims 16-20, wherein the first flow control strategy comprises at least one of the following items:

The effective time of the first flow control strategy, the flow control method, the type of service request message, the generation time of the first flow control strategy, and the increment counter;

Wherein, the flow control method includes: sending service request messages exceeding the first number to other devices for processing or discarding service request messages exceeding the first number; the increment counter is used to determine the first flow control Whether the strategy is the latest flow control strategy.
The apparatus according to claim 16, wherein the transceiver module is further configured to receive a third message sent by the client, and the third message includes the first message being executed by the client A flow control strategy; and in a case where it is determined that the congestion state is released, a fourth message for the third message is sent to the client, the fourth message is used to indicate that the congestion state of the device is released.
The device according to claim 22, wherein the fourth message includes a first field for indicating a congestion state, and the value of the first field indicates that the congestion state of the device is released.
A communication device, characterized in that the device comprises:

The transceiver module is configured to send a first message to the server, where the first message is used to indicate that the device supports flow control; and to receive a second message from the server for the first message, the second message The message includes a first flow control strategy, the first flow control strategy is used to determine a first number of service request messages that the device is allowed to send to the server, and the first number is an integer greater than or equal to 0;

The processing module is configured to perform flow control according to the first flow control strategy.
The device of claim 24, wherein the first message comprises: a second flow control strategy being executed by the device, and the second flow control strategy is used to determine the first flow control strategy.
The device according to claim 24 or 25, wherein the first flow control strategy comprises at least one of the following items:

The effective time of the first flow control strategy, the flow control method, the type of service request message, the generation time of the first flow control strategy, and the increment counter;

Wherein, the flow control method includes: sending service request messages exceeding the first number to other servers for processing or discarding service request messages exceeding the first number, and the increment counter is used to determine the first flow Whether the control strategy is the latest flow control strategy.
The apparatus according to claim 26, wherein, if the first flow control strategy includes the generation time of the first flow control strategy, the processing module is configured to perform according to the first flow control strategy Before performing flow control, it is also used to determine that the generation time of the second flow control strategy being executed is earlier than the generation time of the first flow control strategy.
The device according to claim 26, wherein if the first flow control strategy includes the increment counter, the processing module, before being used to perform flow control according to the first flow control strategy, further It is used to compare the increment counter in the first flow control strategy with the increment counter in the second flow control strategy being executed, and determine to use the first flow control strategy.
The device of claim 24, further comprising:

The transceiver module is further configured to send a third message to the server, the third message including the first flow control strategy being executed by the device; and to receive the first message from the server for the third message Four messages, the fourth message is used to indicate that the congestion state of the server is released;

The processing module is also used to determine that the first flow control strategy is no longer executed.
A communication system, characterized by comprising: a server and a client;

The client is used for:

Sending a first message to the server, where the first message is used to indicate that the client supports flow control;

Receive a second message from the server for the first message, where the second message includes a first flow control policy, and the first flow control policy is used to determine the service request that the device is allowed to send to the server A first number of messages, where the first number is an integer greater than or equal to 0;

Perform flow control according to the first flow control strategy

The server is used to:

Receiving the first message sent by the client

Sending the second message for the first message to the client.