CN113542069B - Flow traction method and device, electronic equipment and storage medium - Google Patents

Flow traction method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN113542069B
CN113542069B CN202110802235.2A CN202110802235A CN113542069B CN 113542069 B CN113542069 B CN 113542069B CN 202110802235 A CN202110802235 A CN 202110802235A CN 113542069 B CN113542069 B CN 113542069B
Authority
CN
China
Prior art keywords
network element
flow traction
request
traction
flow
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202110802235.2A
Other languages
Chinese (zh)
Other versions
CN113542069A (en
Inventor
姜双双
傅强
袁林
邸学锋
马洪彬
窦晶
贾立军
米胜山
范晓波
张赫男
刘道林
阿曼太
梁彧
蔡琳
杨满智
王杰
田野
金红
陈晓光
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Eversec Beijing Technology Co Ltd
Original Assignee
Eversec Beijing Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Eversec Beijing Technology Co Ltd filed Critical Eversec Beijing Technology Co Ltd
Priority to CN202110802235.2A priority Critical patent/CN113542069B/en
Publication of CN113542069A publication Critical patent/CN113542069A/en
Application granted granted Critical
Publication of CN113542069B publication Critical patent/CN113542069B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0876—Network utilisation, e.g. volume of load or congestion level
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management

Abstract

The embodiment of the invention discloses a flow traction method, a flow traction device, electronic equipment and a storage medium. The flow traction method comprises the following steps: generating a flow traction request according to a flow traction setting instruction; the flow traction request comprises a flow traction establishing request, a flow traction deleting request, a flow traction inquiring request and a flow traction updating request; sending the flow traction request to a network open function network element so that the network open function network element indicates a network control surface network element to carry out flow traction on the terminal according to the flow traction request; receiving flow traction response data sent by a network open function network element, and verifying the flow traction response data according to a flow traction request; and under the condition that the flow traction response data is determined not to pass the verification, updating the flow traction request according to the flow traction response data. The technical scheme of the embodiment of the invention can realize accurate statistics on the flow traction and accurate management of the flow traction.

Description

Flow traction method and device, electronic equipment and storage medium
Technical Field
The embodiment of the invention relates to the technical field of communication, in particular to a flow traction method, a flow traction device, electronic equipment and a storage medium.
Background
The current network data shows explosive growth, pulls the flow, can effectively alleviate network flow pressure, more helps the realization of diversified network service in different service scenes (such as flow collection and wisdom garden etc.).
However, when traffic is currently pulled to a designated user plane network element through a third-party network element, only the issuing process of traffic pulling is considered, and the processing process of traffic pulling faults under the condition that the traffic pulling faults are not considered, which will result in wrong statistics of the traffic pulling, and the wrong statistics of the traffic pulling will be unfavorable for the management of the traffic pulling.
Disclosure of Invention
The embodiment of the invention provides a flow traction method, a flow traction device, electronic equipment and a storage medium, which realize accurate statistics on flow traction and accurate management on flow traction.
In a first aspect, an embodiment of the present invention provides a flow rate pulling method, including:
generating a flow traction request according to a flow traction setting instruction; the flow traction request comprises a flow traction establishing request, a flow traction deleting request, a flow traction inquiring request and a flow traction updating request;
sending the flow traction request to a network open function network element so that the network open function network element indicates a network control plane network element to carry out flow traction on the terminal according to the flow traction request;
receiving flow traction response data sent by a network open function network element, and verifying the flow traction response data according to a flow traction request;
and under the condition that the flow traction response data is determined not to pass the verification, updating the flow traction request according to the flow traction response data.
In a second aspect, an embodiment of the present invention further provides a flow traction apparatus, including:
the flow traction request generating module is used for generating a flow traction request according to the flow traction setting instruction; the flow traction request comprises a flow traction establishing request, a flow traction deleting request, a flow traction inquiring request and a flow traction updating request;
the flow traction request sending module is used for sending a flow traction request to the network open function network element so that the network open function network element indicates the network control plane network element to carry out flow traction on the terminal according to the flow traction request;
the flow traction response data verification module is used for receiving the flow traction response data sent by the network open function network element and verifying the flow traction response data according to the flow traction request;
and the flow traction request updating module is used for updating the flow traction request according to the flow traction response data under the condition of determining that the flow traction response data does not pass the verification.
In a third aspect, an embodiment of the present invention further provides an electronic device, where the electronic device includes:
one or more processors;
storage means for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement the traffic pulling method provided by any of the embodiments of the invention.
In a fourth aspect, an embodiment of the present invention further provides a computer storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the flow pulling method provided in any embodiment of the present invention.
According to the technical scheme of the embodiment, the flow traction request is generated according to the flow traction setting instruction, and then the flow traction request is sent to the network open function network element, so that the network open function network element indicates the network control plane network element to carry out flow traction on the terminal according to the flow traction request, the flow traction response data sent by the network open function network element is received, the flow traction response data is verified according to the flow traction request, and finally the flow traction request is updated according to the flow traction response data under the condition that the flow traction response data is determined not to pass the verification. The flow traction response data can reflect the actual flow traction condition of the terminal, and the flow traction response data is verified according to the flow traction request, so that whether the terminal performs flow traction according to the flow traction request can be determined, and accurate statistics on flow traction is further realized. Under the prerequisite of the accurate statistics of flow traction, when the flow traction condition at terminal is different from the flow traction request, the flow traction condition at terminal can be updated through updating the flow traction request to reach the accurate management and control of flow traction, the problem that flow traction error statistics and flow traction management effect are poor in the prior art is solved, the accurate statistics of flow traction is realized, and the accurate management of flow traction is realized.
Drawings
Fig. 1 is a flowchart of a flow traction method according to an embodiment of the present invention;
fig. 2 is a flowchart of a flow traction method according to a second embodiment of the present invention;
FIG. 3 is a schematic diagram of a flow pulling operation provided by a second embodiment of the present invention;
FIG. 4 is a schematic view of a flow traction device provided in accordance with a third embodiment of the present invention;
fig. 5 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention.
It should be further noted that, for the convenience of description, only some but not all of the relevant aspects of the present invention are shown in the drawings. Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the operations (or steps) as a sequential process, many of the operations can be performed in parallel, concurrently or simultaneously. In addition, the order of the operations may be re-arranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, subprograms, and the like.
Example one
The vision of network development is to change society, and as networks face various industries of society, network open-function network elements are produced in order to enable the interaction between the networks and third-party application services. The network open function network element is capable of providing a standardized service that is automatic and allows third party network elements to interact with the core network.
By adopting a network architecture with separated control plane and user plane, the user plane functional network element can be flexibly deployed according to the needs. After the terminal is registered, the session management function network element will make a session routing decision, and select a centralized user plane function network element instead of a newly deployed dedicated user plane function network element. And the centralized user plane functional network element is not favorable for flexible deployment of terminal traffic. The traffic of the terminal can be supervised by dragging the traffic of the terminal to a special user plane functional network element.
And after the application function network element sends a flow traction request to the network open function network element, the network open function network element and other network elements of the core network mutually exchange and store an updating traction message, and send a traction creation response to the application function network element. But even if the application function network element receives the response of successful traction creation of the network open function network element, the traffic is not successfully dragged to the designated user plane function network element on behalf of the traffic. Because whether the core network selects the user plane function network element to be delivered by pulling also depends on the policy of the network element inside the core network, in this case, the application function network element cannot know whether the traffic pulling is executed, and cannot supervise the traffic pulling. Based on the above situation, the present invention provides a traffic pulling method, so that an application function network element can obtain the actual situation of traffic pulling, and realize accurate management of traffic pulling.
Fig. 1 is a flowchart of a traffic pulling method according to an embodiment of the present invention, where the embodiment is applicable to a case where traffic pulling is accurately counted and precisely managed, and the method may be executed by a traffic pulling apparatus, where the apparatus may be implemented by software and/or hardware, and may be generally integrated in an electronic device. Accordingly, as shown in fig. 1, the method comprises the following operations:
and S110, generating a flow traction request according to the flow traction setting instruction.
The traffic pulling setting instruction may be an instruction sent to the application function network element, and is used to instruct the core network element to perform traffic pulling on the terminal through the application function network element. The traffic pulling request may be a request generated at an application function network element, and is used to instruct a core network element to perform traffic pulling on the terminal. The traffic pulling request can comprise a traffic pulling creating request, a traffic pulling deleting request, a traffic pulling inquiring request and a traffic pulling updating request. The traffic tow creation request may be used to create a traffic tow path. The traffic tow deletion request may be used to delete a specified traffic tow route. The traffic pulling query request may be used to query data associated with the traffic pulling request. The flow tractive update request may be used to update an existing flow tractive route. The traffic pulling route may be a transmission topology of the traffic during the traffic pulling. Illustratively, the traffic traction request may use a standard REStful API (development mode of a network application program interface) format, the transmission Protocol may use HTTP (Hyper Text Transfer Protocol), the carried data parameter uses JSON (JavaScript Object Notation) format, and an address of the uniform resource locator of the traffic traction request may be an address and a port number of an application function network element program server. The application function network element can provide an acquisition interface of the traffic traction setting instruction for the outside, and a user can issue the traffic traction setting instruction through a client. The corresponding methods of the traffic traction creation request, the traffic traction deletion request, the traffic traction inquiry request and the traffic traction UPDATE request are POST (component of HTTP), DELETE (component of HTTP), GET (component of HTTP) and PUT/UPDATE (component of HTTP), respectively.
In the embodiment of the present invention, after the application function network element receives the traffic pulling setting instruction, data format conversion may be performed on the traffic pulling setting instruction to obtain the traffic pulling request.
For example, the application function network element may start a server program that receives the traffic traction setting instruction and obtains the interface message, monitor the traffic traction setting instruction sent by the user, and perform data format conversion on the traffic traction setting instruction to obtain a traffic traction request with standard signaling parameters. The application function network element can be configured with a flow traction parameter configuration file, so that a flow traction request in a standard signaling parameter form is obtained by performing data format conversion on the flow traction setting instruction through the flow traction parameter configuration file.
And S120, sending the flow traction request to a network open function network element so that the network open function network element indicates a network control plane network element to carry out flow traction on the terminal according to the flow traction request.
The network control plane network element may be a network element in a core network and capable of performing traffic pulling operation according to a traffic pulling request sent by a network open function network element. The network control plane network element may include, but is not limited to, a policy control function network element, a session management function network element, a user plane function network element, and the like.
In the embodiment of the present invention, the application function network element may send the traffic pulling request to the network open function network element. After receiving the traffic pulling request, the network open function network element may send the traffic pulling request to the policy control function network element. After receiving the flow traction request, the policy control function network element generates a flow traction policy according to the flow traction request, and when the flow traction policy is the same as a flow traction path of the flow traction request, the policy control function network element can send a user plane function network element identifier and a terminal identifier of a terminal flow to be pulled to the session management function network element, and then the session management function network element instructs a terminal to establish communication connection with the user plane function network element of the terminal flow to be pulled according to the terminal identifier and the user plane function network element identifier. And when the flow traction strategy is different from the flow traction path of the flow traction request, the strategy control function network element does not send data to the session management function network element, so that the flow transmission path of the terminal is not changed. The user plane function network element identifier may be used to identify the user plane function network element. The traffic traction policy may be a policy generated by the policy control function network element according to the traffic traction request to perform traffic traction on the terminal.
For example, the application function network element may determine whether a traffic pulling creation request already exists, and if the same traffic pulling creation request exists, a new traffic pulling creation request is not generated, so as to avoid duplicate resource creation. The other types of flow pulling requests may also be subjected to duplicate checking, and the specific process is the same as the process of processing the flow pulling creation request, which is not described in detail. The flow traction update request can issue a flow traction update operation or a flow traction deletion operation to delete the flow traction related information stored in the network. In addition, the traffic pulling request sent by the application function network element includes an afTransId (a traffic pulling identifier), and the afTransId is maintained by the application function network element. The application function network element provides northbound afTransId to the network open function network element, and the network open function network element matches the identifier with the southbound identifier generated by the network open function network element. The network element with the network open function provides a southbound identifier of a UDR (Unified Data Repository) network element as a keyword for storing, updating and deleting the traffic traction Data by the UDR network element.
And S130, receiving the traffic traction response data sent by the network open function network element, and verifying the traffic traction response data according to the traffic traction request.
The traffic pulling response data may be response data that the network open function network element needs to send to the application function network element, and is used for the application function network element to verify a traffic pulling path.
In the embodiment of the present invention, the policy control function network element may send the traffic pulling policy to the network open function network element, and the network open function network element may further generate traffic pulling response data according to the traffic pulling policy. After the network open function network element obtains the traffic traction response data, the traffic traction response data can be sent to the application function network element, so that the application function network element can perform matching processing on the traffic traction response data according to the traffic traction request.
For example, the traffic traction response data may carry an aftransId, and the aftransId of the traffic traction response data is verified through the aftransId in the traffic traction request, so that preliminary verification of the traffic traction response data may be achieved.
And S140, under the condition that the flow traction response data is determined not to pass the verification, updating the flow traction request according to the flow traction response data.
In the embodiment of the invention, if the flow traction response data is not successfully matched with the related data in the flow traction request, the flow traction response data is proved to be not verified. And under the condition that the flow traction response data is not verified, generating a new flow traction request according to the flow traction response data, and sending the updated flow traction request to the network open function network element so that the network open function network element indicates the network control plane network element to carry out flow traction on the terminal according to the updated flow traction request. Therefore, the application function network element can verify and maintain the traffic traction. And the application program stability in the application function network element has little influence on the inside of the network.
In an optional embodiment of the present invention, the traffic pulling request may further include a batch traffic pulling request for performing traffic pulling on the batch terminal; the network open function network element is used for indicating the strategy control function network element to send a batch flow traction identifier to the session management function network element according to the batch flow traction request; the session management function network element is used for determining at least one user plane function network element according to the batch flow traction identification; and the at least one user plane functional network element is used for realizing the flow traction of the plurality of terminals according to the batch flow traction identification.
Wherein, the batch flow traction request can be used for carrying out flow traction on the batch terminal. The bulk traffic pulling identifier may be an equipment identifier that needs to be determined by the session management function network element when bulk traffic pulling is performed. The bulk traffic volume pulling identifier may include an identifier characterizing the plurality of terminals and an identifier of at least one user plane function network element performing traffic volume pulling for the plurality of terminals. The identifier for representing the plurality of terminals is a combined identifier, that is, the plurality of terminals have a corresponding relationship with the identifier. Optionally, one user plane functional network element may be used to perform traffic pulling on one terminal, and one user plane functional network element may also be used to perform traffic pulling on multiple terminals. The policy control function network element may identify the identifier representing the plurality of terminals as the plurality of terminals corresponding to the identifier, and the terminal identifiers corresponding to the plurality of terminals, respectively.
In the embodiment of the present invention, when traffic pulling needs to be performed on multiple terminals, a batch traffic pulling request may be generated by an application function network element, and the batch traffic pulling request may be sent to a network open function network element. The network open function network element further sends a batch flow traction request to the policy control function network element, the policy control function network element generates a flow traction policy according to the batch flow traction request, when the flow traction policy is the same as a flow traction path of the batch flow traction request, the policy control function network element can determine a batch flow traction identifier according to the batch flow traction request, the policy control function network element sends a plurality of terminal identifiers and at least one user plane function network element identifier corresponding to the terminal identifiers to the session management function network element, and the session management function network element indicates the plurality of terminals to establish communication connection with the at least one user plane function network element corresponding to the terminal identifiers according to the plurality of terminal identifiers and the user plane function network element identifier corresponding to the terminal identifiers.
For example, the traffic pulling response data returned by the network element with the network open function may carry an application session identifier, where the identifier is used to characterize a session corresponding to the traffic pulling operation. Subsequent traffic pulling updates, traffic pulling queries, and traffic deletion operations will also use this application session identification. The application session identification is stored and maintained by the application function network element. And the application functional network element determines the corresponding application session identifier by storing and retrieving the terminal identifier information in the traffic traction issuing parameter. When traffic pulling is performed, the traffic pulling can be divided into two different flows according to the difference of the terminal identifiers carried in the traffic pulling request. When traffic traction is performed on a specific single terminal IP (Internet Protocol Address) or Ethernet (Ethernet) Address, the network open function network element directly interacts with the user plane function network element to complete a traffic traction application, and the terminal IP may be IPv4 or IPv 6. When carrying out flow traction on a single terminal or a plurality of terminals identified by non-terminal IP or Ethernet addresses, the network open function network element stores the data of the flow traction request to the UDR, and the UDR informs the flow traction information to the user plane function network element according to the subscription information of the user plane function network element. The terminal information of the non-terminal IP or Ethernet address identifier may include a combination of a user identifier, a group user identifier, DNN (Deep neural Networks), and a network slice.
The network slice is an independent logic network in the network, the application function network element supports the issuing of a slice-based flow guide request, the traction parameter comprises the combination of DNN and the network slice, the DNN and the network slice information can be issued through a command interface or imported through a flow traction parameter configuration file, and the flow traction of the terminal in the specified network slice is realized. Meanwhile, the application function network element supports the issuing of the traction time, and issuing parameters comprise the starting time of traction and the ending time of traction and can be used for guiding the time of the flow traction action of the core network. The terminal information of the batch terminal flow traction can be issued by a command interface or can be the batch import of the flow traction parameter configuration file. The application function network element can simultaneously verify the information of each terminal dragged by the terminals in batch and respond to the flow dragging information of each terminal in time.
According to the technical scheme of the embodiment, the flow traction request is generated according to the flow traction setting instruction, and then the flow traction request is sent to the network open function network element, so that the network open function network element indicates the network control plane network element to carry out flow traction on the terminal according to the flow traction request, the flow traction response data sent by the network open function network element is received, the flow traction response data is verified according to the flow traction request, and finally the flow traction request is updated according to the flow traction response data under the condition that the flow traction response data is determined not to pass the verification. The flow traction response data can reflect the actual flow traction condition of the terminal, and the flow traction response data is verified according to the flow traction request, so that whether the terminal performs flow traction according to the flow traction request can be determined, and accurate statistics on flow traction is further realized. Under the prerequisite of the accurate statistics of flow traction, when the flow traction condition at terminal is different from the flow traction request, the flow traction condition at terminal can be updated through updating the flow traction request to reach the accurate management and control of flow traction, the problem that flow traction error statistics and flow traction management effect are poor in the prior art is solved, the accurate statistics of flow traction is realized, and the accurate management of flow traction is realized.
Example two
Fig. 2 is a flowchart of a traffic pulling method provided in the second embodiment of the present invention, which is embodied on the basis of the above embodiment, and in this embodiment, a specific alternative implementation is provided for receiving traffic pulling response data sent by a network element having an open function, verifying the traffic pulling response data according to a traffic pulling request, and updating the traffic pulling request according to the traffic pulling response data when it is determined that the traffic pulling response data is not verified, and accordingly, as shown in fig. 2, the method includes the following operations:
and S210, generating a flow traction request according to the flow traction setting instruction.
In an optional embodiment of the present invention, generating the flow pulling request according to the flow pulling setting instruction may include: extracting a setting parameter of the flow traction setting instruction, and checking the setting parameter; determining a data processing path in the setting parameter under the condition that the setting parameter meets the parameter verification condition; and determining a second data processing function according to the data processing path in the setting parameters, and performing data format conversion on the flow traction setting instruction according to the second data processing function to obtain a flow traction request.
The setting parameter may be a parameter carried in the traffic pulling setting instruction, and is used to generate part of data in the traffic pulling request. The parameter checking condition can be used for checking the set parameter so as to ensure the integrity, the reasonability and the correctness of the set parameter. The data processing path in the setting parameter may be an address of a uniform resource locator where a function capable of performing data processing on the setting parameter is located, and the function capable of performing data processing on the setting parameter may be determined according to the data processing path of the setting parameter. The second data processing data may be used to format convert the data.
In the embodiment of the present invention, after the application function network element receives the traffic pulling setting instruction, the application function network element may first analyze the traffic pulling setting instruction to extract the setting parameters in the traffic pulling setting instruction, and then verify the setting parameters. And under the condition that the set parameters meet the completeness, correctness and rationality, further acquiring a data processing path in the set parameters, acquiring a second data processing function in the road tree by using the data processing path, and performing data format conversion on data in the flow traction setting instruction according to the second data processing function to obtain a flow traction request. The route tree may be a tree composed of a plurality of routes, and the plurality of routes and data processing functions corresponding to the routes are registered in the route tree.
Illustratively, after the route and the data processing function are registered in the route tree, the setting parameters of the traffic traction setting instruction can be extracted, whether the parameter format of the setting parameters is correct, complete and reasonable is checked, and the check condition is fed back. And then acquiring a second data processing function in the routing tree according to the data processing path in the setting parameter, and performing data format conversion on the flow traction setting instruction through the second data processing function to obtain a flow traction request. If the corresponding data processing function cannot be found in the routing tree, a response of processing failure is fed back. It should be noted that different data processing functions are registered in the routing tree for the traffic pulling creation request, the traffic pulling deletion request, the traffic pulling query request, and the traffic pulling update request. After the application function network element analyzes the traffic pulling setting instruction, a corresponding data processing function is determined from the routing tree according to the specific type of the traffic pulling request to be generated.
Illustratively, the application function network element starts the application by using a simple and fast cli (command-line interface) framework, and performs network parameter configuration by using the traffic traction parameter configuration file. The flow traction parameter configuration file is in a JSON format which is fast and convenient to read and understand, and comprises a protocol type, a port number and an address for receiving a flow traction setting instruction, and a port number and an address for receiving an event notification message sent by a network open function network element, a port number and an address of the network open function network element, a database name of stored data and a uniform resource locator.
Optionally, in order to improve development efficiency and cope with emergency situations such as power failure of the application function network element, the pulling data maintained by the application function network element may be stored in a database (MongoDB), and when the program is started, the pulling data is connected to the database through the name and the uniform resource locator of the database stored in the traffic pulling parameter configuration file.
Optionally, for convenience of subsequent maintenance and management, the application function network element may output an effective log to the local log file, and may initialize, load, and set a local log variable when the program is started, and may also set different log levels.
And S220, sending the flow traction request to the network open function network element so that the network open function network element indicates the network control plane network element to carry out flow traction on the terminal according to the flow traction request.
And S230, receiving the traffic traction response data sent by the network open function network element, and determining a first data processing function according to a data processing path in the target traffic traction response data.
The target flow traction response data can be part of the flow traction response data and is used for representing the actual flow traction condition. The data processing path in the target traffic pulling response data may be an address of a uniform resource locator at which a function capable of data processing the target traffic pulling response data is located. A function capable of data processing the target flow tractive response data may be determined from a data processing path of the target flow tractive response data. The first data processing function may be used for data extraction and data verification of the target flow traction data.
Correspondingly, after receiving the traffic traction response data sent by the network open function network element, the application function network element may analyze the traffic traction response data to obtain target traffic traction response data, further extract data of the target traffic traction response data to obtain a data processing path capable of performing data processing on the target traffic traction response data, and obtain a first data processing function in the routing tree by using the data processing path.
In an optional embodiment of the present invention, the receiving traffic pulling response data sent by the network element with a network open function may include: receiving initial flow traction response data sent by a network open function network element; receiving target traffic pulling response data in the event subscription notification parameters included in the traffic pulling request.
The initial traffic pulling response data may be used to determine that the network open function network element completes the creation of the traffic pulling task. The event subscription notification parameter may be a parameter carried in the traffic pulling request, and is used for enabling the network function open network element to feed back the target traffic pulling response data to the application function network element.
In the embodiment of the invention, after the network open function network element sends the traffic traction request to the policy control function network element, the network open function network element also sends initial traffic traction response data to the application function network element, so that the application function network element knows the issuing condition of the traffic traction request. When the flow traction request includes the event subscription notification parameter, the network open function network element needs to perform data analysis and data extraction processing on the received flow traction policy issued by the policy control function network element to obtain target flow traction response data, and send the target flow traction response data to the application function network element, so that the application function network element knows the actual flow traction condition.
For example, the traffic pulling request may include the event subscription notification parameter and the event subscription notification type, as well as the uniform resource locator of the event notification message (target traffic pulling response data). When the session management function network element loads the strategy to reselect the user plane function network element, the strategy control function network element sends an event notification message to notify the network open function network element, and then the network open function network element sends the event notification message to the application function network element. And the application function network element receives the event notification message issued by the network open function network element and processes the event notification message by using the registered data processing function in the routing tree. And maintaining the stored afTransId by using the application function network element, checking the received event notification message, and sending a response to the network open function network element.
And S240, extracting the source user plane function network element data and the target user plane function network element data in the target traffic traction response data according to the first data processing function, and verifying the source user plane function network element data and the target user plane function network element data.
The source user plane function network element data may be related data of the user plane function network element that provides traffic for the terminal before the application function network element sends the traffic pulling request. The target user plane function network element data may be related data of the user plane function network element that provides traffic for the terminal according to the traffic pulling policy after the application function network element sends the traffic pulling request.
In this embodiment of the present invention, the application function network element may utilize the first data processing function to perform data extraction on the target traffic traction response data, so as to obtain source user plane function network element data and target user plane function network element data, and further perform verification on the source user plane function network element data and the target user plane function network element data according to the traffic traction request.
And S250, under the condition that the flow traction response data is determined not to pass the verification, updating the flow traction request according to the flow traction response data.
In an alternative embodiment of the present invention, determining that the flow tractive response data fails the verification may comprise: under the condition that any one of the source user plane functional network element data and the target user plane functional network element data is determined not to be matched with the source data, determining that the flow traction response data does not pass the verification; updating the traffic tow request based on the traffic tow response data may include: determining target retransmission data according to the source data; generating a flow traction updating request according to the target retransmission data; and carrying out flow traction on the terminal according to the flow traction updating request.
The source data may be partial data in the traffic pulling request, and is used to check the source user plane function network element data and the target user plane function network element data. The source data may include data of a user plane functional network element that needs to disconnect a traffic transmission path from the terminal and data of a user plane functional network element that needs to establish a new traffic transmission path with the terminal. The target retransmission data may be data corresponding to the failed check data in the source data.
Correspondingly, the application function network element can perform matching verification on the source user plane function network element data and the target user plane function network element data with the source data, and if any one of the source user plane function network element data and the target user plane function network element data cannot be completely matched with the source data, it indicates that the traffic traction response data fails to pass the verification. And under the condition that the flow traction response data is determined not to pass the verification, taking the data corresponding to the user plane function network element data which is not successfully matched in the source data as target retransmission data. And generating a flow traction updating request according to the user plane function network element data successfully matched with the source data and the target retransmission data, so as to correct the flow traction path of the terminal according to the flow traction updating request. Specifically, the process of performing matching verification on the source user plane functional network element data and the target user plane functional network element data with the source data is as follows: matching and checking the data of the user plane functional network element needing to disconnect the flow transmission path from the terminal in the source data with the data of the source user plane functional network element; and matching and checking the data of the user plane functional network element needing to establish a new flow transmission path with the terminal in the source data with the data of the target user plane functional network element.
In an alternative embodiment of the present invention, determining that the flow tractive response data fails the verification may comprise: determining that the flow traction response data does not pass the verification under the condition that the target user plane functional network element data is not extracted according to the target flow traction response data; updating the traffic pulling request according to the traffic pulling response data may further include: monitoring a user plane functional network element corresponding to the flow traction request; and generating a flow traction deletion request according to the flow traction request.
In the embodiment of the present invention, if the application function network element cannot extract the target user function network element data from the target traffic traction response data, the target user function network element data in the vacant state cannot be completely matched with the source data, so that it can be determined that the traffic traction response data does not pass the verification, and the user plane function network element corresponding to the traffic traction request data can be monitored. And when the number of times of data verification failure of one user plane function network element exceeds a set threshold, stopping establishing flow transmission paths between other terminals and the user plane function network element so as to realize accurate control on flow traction. The set threshold value may be a value that is created according to the flow rate traction and needs to be set. The application function network element can also generate a flow traction deletion request according to the source data of the flow traction request, so that the flow traction path corresponding to the source data is deleted through the flow traction deletion request, and the data storage load and the data maintenance load of the application function network element are reduced.
Fig. 3 is a schematic diagram of a traffic pulling operation according to a second embodiment of the present invention, and as shown in fig. 3, the application function network element initializes according to the configuration file and registers a routing and data processing function, so as to start the monitor to monitor that a user sends a traffic pulling setting instruction to the application function network element through the client. The flow traction setting instruction comprises relevant data capable of generating a flow traction creating request, a flow traction updating request, a flow traction inquiring request or a flow traction deleting request, and the data is different from the uniform resource locator of the flow traction setting instruction corresponding to different flow traction request types. After receiving the traffic traction setting instruction, the application function network element performs message reception, message processing and message maintenance processing on the traffic traction setting instruction, specifically: after receiving the traffic traction setting instruction, the application function network element obtains the registered second data processing function from the routing tree according to different uniform resource locators, and performs data format conversion on the traffic traction setting instruction to obtain a standard signaling parameter so as to obtain a traffic traction request. And after the application function network element receives the initial flow traction response data sent by the network open function network element, sending the response data to the client side sending the flow traction setting instruction. When the flow traction request comprises the event subscription notification parameter, the network open function network element establishes HTTP connection with the application function network element after receiving the event notification message sent by the policy management function network element, and sends the event notification message to the application function network element. The application function network element obtains a first data processing function from the routing tree according to the uniform resource locator corresponding to the event notification message, processes the event notification message, extracts the event notification parameter, judges whether the flow traction is executed or not, and sends a response message to the network open function network element when receiving the event notification message. And generating a new flow traction request according to the event notification message under the condition that the event notification message is not verified.
According to the technical scheme of the embodiment, the flow traction request is generated according to the flow traction setting instruction, and then the flow traction request is sent to the network open function network element, so that the network open function network element instructs the network control plane network element to perform flow traction on the terminal according to the flow traction request, the flow traction response data sent by the network open function network element is further received, and the first data processing function is determined according to the data processing path in the target flow traction response data. After the first data processing function is obtained, extracting the source user plane functional network element data and the target user plane functional network element data in the target flow traction response data according to the first data processing function, and verifying the source user plane functional network element data and the target user plane functional network element data. And under the condition that the flow traction response data is determined not to pass the verification, updating the flow traction request according to the flow traction response data. The flow traction response data can reflect the actual flow traction condition of the terminal, and the flow traction response data is verified according to the flow traction request, so that whether the terminal performs flow traction according to the flow traction request can be determined, and accurate statistics on flow traction is further realized. Under the prerequisite of the accurate statistics of flow traction, when the flow traction condition at terminal is different from the flow traction request, the flow traction condition at terminal can be updated through updating the flow traction request to reach the accurate management and control of flow traction, the problem that flow traction error statistics and flow traction management effect are poor in the prior art is solved, the accurate statistics of flow traction is realized, and the accurate management of flow traction is realized.
It should be noted that any permutation and combination between the technical features in the above embodiments also belong to the scope of the present invention.
EXAMPLE III
Fig. 4 is a schematic diagram of a flow traction device according to a third embodiment of the present invention, and as shown in fig. 4, the flow traction device includes: a traffic pulling request generating module 310, a traffic pulling request sending module 320, a traffic pulling response data verifying module 330, and a traffic pulling request updating module 340, wherein:
a flow traction request generating module 310, configured to generate a flow traction request according to a flow traction setting instruction; the flow traction request comprises a flow traction establishing request, a flow traction deleting request, a flow traction inquiring request and a flow traction updating request;
a traffic pulling request sending module 320, configured to send a traffic pulling request to a network open function network element, so that the network open function network element instructs a network control plane network element to perform traffic pulling on a terminal according to the traffic pulling request;
the flow traction response data verification module 330 is configured to receive flow traction response data sent by a network open function network element, and verify the flow traction response data according to a flow traction request;
and the flow traction request updating module 340 is configured to update the flow traction request according to the flow traction response data when it is determined that the flow traction response data does not pass the verification.
Optionally, the flow traction response data verification module 330 is specifically configured to: determining a first data processing function according to a data processing path in the target flow traction response data; and extracting source user plane function network element data and target user function network element data in the target flow traction response data according to the first data processing function, and verifying the source user plane function network element data and the target user function network element data.
Optionally, the flow traction request updating module 340 is specifically configured to: under the condition that any one of the source user plane functional network element data and the target user plane functional network element data is determined not to be matched with the source data, determining that the flow traction response data does not pass the verification; determining target correction retransmission data according to the source data streaming traction request; generating the flow traction updating request according to the target retransmission correction data; and carrying out flow traction on the terminal according to the flow traction updating request.
Optionally, the traffic pulling request updating module 340 is specifically configured to: under the condition that the target user function network element data are not extracted according to the target flow traction response data, determining that the flow traction response data do not pass the verification; monitoring a source user plane functional network element and a target user functional network element corresponding to the traffic traction request source data; and generating a flow traction deletion request according to the target user plane function network element data corresponding to the flow traction request.
Optionally, the traffic traction request further includes a batch traffic traction request for performing traffic traction on a batch terminal, and the network open function network element is configured to instruct the policy control function network element to send a batch traffic traction identifier to the session management function network element according to the batch traffic traction request; the session management function network element is used for determining a plurality of target user plane function network elements according to the batch flow traction identification; and the target user plane function network elements are used for realizing the flow traction of a plurality of terminals according to the batch flow traction identification.
Optionally, the flow pulling request generating module 310 is specifically configured to: extracting a setting parameter of the flow traction setting instruction, and checking the setting parameter; determining a data processing path in the setting parameter under the condition that the setting parameter meets a parameter verification condition; and determining a second data processing function according to the data path in the setting parameters, and performing data format conversion on the flow traction setting instruction according to the second data processing function to obtain the flow traction request.
Optionally, the flow traction response data verification module 330 is specifically configured to: receiving initial flow traction response data sent by the network open function network element; receiving target traffic pulling response data under the condition that the traffic pulling request comprises event subscription notification parameters; and the initial traffic traction response data is used for determining that the network open function network element completes the creation of a traffic traction task.
According to the technical scheme of the embodiment, the flow traction request is generated according to the flow traction setting instruction, and then the flow traction request is sent to the network open function network element, so that the network open function network element instructs the network control plane network element to perform flow traction on the terminal according to the flow traction request, the flow traction response data sent by the network open function network element is received, the flow traction response data is verified according to the flow traction request, and finally the flow traction request is updated according to the flow traction response data under the condition that the flow traction response data is determined not to pass the verification. The flow traction response data can reflect the actual flow traction condition of the terminal, and the flow traction response data is verified according to the flow traction request, so that whether the terminal performs flow traction according to the flow traction request can be determined, and accurate statistics on the flow traction is further realized. Under the premise of accurate statistics of flow traction, when the flow traction condition of a terminal is different from a flow traction request, the flow traction condition of the terminal can be updated through updating the flow traction request, so that accurate flow management and control of the flow traction are achieved, the problems of poor flow traction error statistics and poor flow traction management effect in the prior art are solved, and accurate statistics of the flow traction and accurate management of the flow traction are achieved.
The flow traction device can execute the flow traction method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method. For technical details not described in detail in this embodiment, reference may be made to the flow pulling method provided in any embodiment of the present invention.
Since the above-described flow rate pulling device is a device capable of executing the flow rate pulling method in the embodiment of the present invention, based on the flow rate pulling method described in the embodiment of the present invention, a person skilled in the art can understand a specific implementation of the flow rate pulling device of the embodiment and various modifications thereof, and therefore, a detailed description of how the flow rate pulling device implements the flow rate pulling method in the embodiment of the present invention is not provided here. The scope of the present application is intended to cover any apparatus that can be used by those skilled in the art to implement the method for pulling flow in the embodiments of the present invention.
Example four
Fig. 5 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present invention. FIG. 5 illustrates a block diagram of an electronic device 412 suitable for use in implementing embodiments of the present invention. The electronic device 412 shown in fig. 5 is only an example and should not impose any limitation on the functionality and scope of use of embodiments of the present invention. The electronic device 412 may be, for example, a computer device or a server device, etc.
As shown in fig. 5, the electronic device 412 is in the form of a general purpose computing device. The components of the electronic device 412 may include, but are not limited to: one or more processors 416, a storage device 428, and a bus 418 that couples the various system components including the storage device 428 and the processors 416.
Bus 418 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, or a local bus using any of a variety of bus architectures. By way of example, such architectures include, but are not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an enhanced ISA bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.
Electronic device 412 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by electronic device 412 and includes both volatile and nonvolatile media, removable and non-removable media.
Storage 428 may include computer system readable media in the form of volatile Memory, such as Random Access Memory (RAM) 430 and/or cache Memory 432. The electronic device 412 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 434 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 5, commonly referred to as a "hard drive"). Although not shown in FIG. 5, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a Compact disk-Read Only Memory (CD-ROM), a Digital Video disk (DVD-ROM), or other optical media) may be provided. In these cases, each drive may be connected to bus 418 by one or more data media interfaces. Storage 428 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
Program 436 having a set (at least one) of program modules 426 may be stored, for example, in storage 428, such program modules 426 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination may comprise an implementation of a network environment. Program modules 426 generally perform the functions and/or methodologies of embodiments of the invention as described herein.
The electronic device 412 may also communicate with one or more external devices 414 (e.g., keyboard, pointing device, camera, display 424, etc.), with one or more devices that enable a user to interact with the electronic device 412, and/or with any devices (e.g., network card, modem, etc.) that enable the electronic device 412 to communicate with one or more other computing devices. Such communication may be through an Input/Output (I/O) interface 422. Also, the electronic device 412 may communicate with one or more networks (e.g., a Local Area Network (LAN), Wide Area Network (WAN), and/or a public Network, such as the internet) via the Network adapter 420. As shown, network adapter 420 communicates with the other modules of electronic device 412 over bus 418. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 412, including but not limited to: microcode, device drivers, Redundant processing units, external disk drive Arrays, disk array (RAID) systems, tape drives, and data backup storage systems, to name a few.
The processor 416 executes programs stored in the storage device 428 to perform various functional applications and data processing, such as implementing the traffic pulling method provided by the above-described embodiments of the present invention: generating a flow traction request according to a flow traction setting instruction; the flow traction request comprises a flow traction establishing request, a flow traction deleting request, a flow traction inquiring request and a flow traction updating request; sending the flow traction request to a network open function network element so that the network open function network element indicates a network control surface network element to carry out flow traction on the terminal according to the flow traction request; receiving flow traction response data sent by a network open function network element, and verifying the flow traction response data according to a flow traction request; and under the condition that the flow traction response data is determined not to pass the verification, updating the flow traction request according to the flow traction response data.
According to the technical scheme of the embodiment, the flow traction request is generated according to the flow traction setting instruction, and then the flow traction request is sent to the network open function network element, so that the network open function network element instructs the network control plane network element to perform flow traction on the terminal according to the flow traction request, the flow traction response data sent by the network open function network element is received, the flow traction response data is verified according to the flow traction request, and finally the flow traction request is updated according to the flow traction response data under the condition that the flow traction response data is determined not to pass the verification. The flow traction response data can reflect the actual flow traction condition of the terminal, and the flow traction response data is verified according to the flow traction request, so that whether the terminal performs flow traction according to the flow traction request can be determined, and accurate statistics on flow traction is further realized. Under the prerequisite of the accurate statistics of flow traction, when the flow traction condition at terminal is different from the flow traction request, the flow traction condition at terminal can be updated through updating the flow traction request to reach the accurate management and control of flow traction, the problem that flow traction error statistics and flow traction management effect are poor in the prior art is solved, the accurate statistics of flow traction is realized, and the accurate management of flow traction is realized.
EXAMPLE five
An embodiment five of the present invention further provides a computer storage medium storing a computer program, which when executed by a computer processor is configured to execute the flow pulling method according to any one of the above embodiments of the present invention: generating a flow traction request according to a flow traction setting instruction; the flow traction request comprises a flow traction establishing request, a flow traction deleting request, a flow traction inquiring request and a flow traction updating request; sending the flow traction request to a network open function network element so that the network open function network element indicates a network control plane network element to carry out flow traction on the terminal according to the flow traction request; receiving flow traction response data sent by a network open function network element, and verifying the flow traction response data according to a flow traction request; and under the condition that the flow traction response data is determined not to pass the verification, updating the flow traction request according to the flow traction response data.
Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a Read-Only Memory (ROM), an Erasable Programmable Read-Only Memory (EPROM) or flash Memory), an optical fiber, a portable compact disc Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, Radio Frequency (RF), etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims (8)

1. A method of traffic pulling, comprising:
generating a flow traction request according to a flow traction setting instruction; the flow traction request comprises a flow traction establishing request, a flow traction deleting request, a flow traction inquiring request and a flow traction updating request;
sending the flow traction request to a network open function network element so that the network open function network element indicates a network control plane network element to carry out flow traction on a terminal according to the flow traction request;
receiving flow traction response data sent by the network open function network element, and verifying the flow traction response data according to the flow traction request;
updating the flow traction request according to the flow traction response data under the condition that the flow traction response data is determined not to pass the verification;
wherein the verifying the traffic pulling response data according to the traffic pulling request comprises:
determining a first data processing function according to a data processing path in the target flow traction response data;
extracting source user plane functional network element data and target user plane functional network element data in the target flow traction response data according to the first data processing function, and verifying the source user plane functional network element data and the target user plane functional network element data;
wherein the verifying the source user plane function network element data and the target user plane function network element data comprises:
matching and checking the source user plane function network element data and the target user plane function network element data with the source data, matching and checking the user plane function network element data which needs to disconnect a traffic transmission path from the terminal in the source data with the source user plane function network element data, and matching and checking the user plane function network element data which needs to establish a new traffic transmission path with the terminal in the source data with the target user plane function network element data;
wherein, the generating of the flow traction request according to the flow traction setting instruction comprises:
extracting the setting parameters of the flow traction setting instruction, and verifying the setting parameters;
determining a data processing path in the setting parameter under the condition that the setting parameter accords with a parameter verification condition;
and determining a second data processing function according to the data processing path in the setting parameters, and performing data format conversion on the flow traction setting instruction according to the second data processing function to obtain the flow traction request.
2. The method of claim 1,
the determining that the flow tractive response data fails verification comprises:
determining that the flow traction response data does not pass the verification under the condition that any one of the source user plane function network element data and the target user plane function network element data is determined to be not matched with the source data;
updating the traffic pulling request according to the traffic pulling response data, comprising:
determining target retransmission data according to the source data;
generating the flow traction updating request according to the target retransmission data;
and carrying out flow traction on the terminal according to the flow traction updating request.
3. The method of claim 2,
the determining that the flow tractive response data fails verification comprises:
under the condition that the target user plane functional network element data are not extracted according to the target flow traction response data, determining that the flow traction response data do not pass the verification;
updating the traffic pulling request according to the traffic pulling response data, further comprising:
monitoring a user plane function network element corresponding to the flow traction request;
and generating a flow traction deletion request according to the flow traction request.
4. The method of claim 1, wherein the traffic pulling request further comprises a bulk traffic pulling request to traffic pull bulk terminals;
the network open function network element is used for indicating the strategy control function network element to send a batch flow traction identifier to the session management function network element according to the batch flow traction request;
the session management function network element is used for determining at least one user plane function network element according to the batch flow traction identifier;
and the at least one user plane function network element is used for realizing the flow traction of a plurality of terminals according to the batch flow traction identification.
5. The method of claim 1, wherein the receiving the traffic pulling response data sent by the network open function network element comprises:
receiving initial flow traction response data sent by the network open function network element;
receiving target traffic pulling response data under the condition that the traffic pulling request comprises event subscription notification parameters;
and the initial traffic traction response data is used for determining that the network open function network element completes the creation of a traffic traction task.
6. A flow pulling apparatus, comprising:
the flow traction request generating module is used for generating a flow traction request according to the flow traction setting instruction; the flow traction request comprises a flow traction establishing request, a flow traction deleting request, a flow traction inquiring request and a flow traction updating request;
a traffic pulling request sending module, configured to send the traffic pulling request to a network open function network element, so that the network open function network element instructs a network control plane network element to perform traffic pulling on a terminal according to the traffic pulling request;
the flow traction response data verification module is used for receiving the flow traction response data sent by the network open function network element and verifying the flow traction response data according to the flow traction request;
the flow traction request updating module is used for updating the flow traction request according to the flow traction response data under the condition that the flow traction response data is determined not to pass the verification;
the flow traction response data verification module is specifically configured to: determining a first data processing function according to a data processing path in the target flow traction response data; extracting source user plane functional network element data and target user functional network element data in the target flow traction response data according to the first data processing function, and verifying the source user plane functional network element data and the target user functional network element data;
wherein the verifying the source user plane function network element data and the target user plane function network element data comprises:
matching and checking the source user plane functional network element data and the target user plane functional network element data with the source data, matching and checking the user plane functional network element data which needs to disconnect a flow transmission path from the terminal in the source data with the source user plane functional network element data, and matching and checking the user plane functional network element data which needs to establish a new flow transmission path with the terminal in the source data with the target user plane functional network element data;
the flow traction request generation module is specifically configured to: extracting a setting parameter of the flow traction setting instruction, and checking the setting parameter; determining a data processing path in the setting parameter under the condition that the setting parameter meets a parameter verification condition; and determining a second data processing function according to the data processing path in the setting parameters, and performing data format conversion on the flow traction setting instruction according to the second data processing function to obtain the flow traction request.
7. An electronic device, characterized in that the electronic device comprises:
one or more processors;
storage means for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement the traffic pulling method of any of claims 1-5.
8. A computer storage medium on which a computer program is stored, which program, when being executed by a processor, is adapted to carry out a method of traffic pulling according to any one of claims 1-5.
CN202110802235.2A 2021-07-15 2021-07-15 Flow traction method and device, electronic equipment and storage medium Active CN113542069B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110802235.2A CN113542069B (en) 2021-07-15 2021-07-15 Flow traction method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110802235.2A CN113542069B (en) 2021-07-15 2021-07-15 Flow traction method and device, electronic equipment and storage medium

Publications (2)

Publication Number Publication Date
CN113542069A CN113542069A (en) 2021-10-22
CN113542069B true CN113542069B (en) 2022-09-23

Family

ID=78128210

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110802235.2A Active CN113542069B (en) 2021-07-15 2021-07-15 Flow traction method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN113542069B (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103491095A (en) * 2013-09-25 2014-01-01 中国联合网络通信集团有限公司 Flow cleaning framework and device and flow lead and reinjection method

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
ATE475256T1 (en) * 2007-08-13 2010-08-15 Accenture Global Services Gmbh SERVICE REQUEST EXECUTION ARCHITECTURE FOR A COMMUNICATIONS SERVICE PROVIDER
CN101335709B (en) * 2008-08-07 2010-09-22 杭州华三通信技术有限公司 Method for implementing load sharing among flow analysis servers and shunting equipment
CN103001880B (en) * 2012-11-30 2015-11-25 北京百度网讯科技有限公司 Based on the flow lead method and apparatus of non-standard OSPF Routing Protocol
CN108449314B (en) * 2018-02-02 2020-12-29 杭州迪普科技股份有限公司 Flow traction method and device
CN108289104B (en) * 2018-02-05 2020-07-17 重庆邮电大学 Industrial SDN network DDoS attack detection and mitigation method
CN108833418B (en) * 2018-06-22 2021-05-25 京东数字科技控股有限公司 Method, device and system for defending attack
CN112118600B (en) * 2020-09-18 2024-05-03 恒安嘉新（北京）科技股份公司 Flow traction system under 5G independent networking SA architecture

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103491095A (en) * 2013-09-25 2014-01-01 中国联合网络通信集团有限公司 Flow cleaning framework and device and flow lead and reinjection method

Also Published As

Publication number Publication date
CN113542069A (en) 2021-10-22

Similar Documents

Publication Publication Date Title
CN111752799A (en) Service link tracking method, device, equipment and storage medium
CN107800565B (en) Inspection method, inspection device, inspection system, computer equipment and storage medium
CN112988485B (en) Simulation test method and device for electric power Internet of things equipment
CN109391673A (en) A kind of method, system and the terminal device of management update file
CN112613024A (en) Data interaction method, device and system and storage medium
CN112329001B (en) Data distribution method, system, terminal and medium between internal network and external network
CN113225339B (en) Network security monitoring method and device, computer equipment and storage medium
US10887408B2 (en) Remote monitoring of network communication devices
CN110932918A (en) Log data acquisition method and device and storage medium
CN112118600B (en) Flow traction system under 5G independent networking SA architecture
WO2020010906A1 (en) Method and device for operating system (os) batch installation, and network device
CN113542069B (en) Flow traction method and device, electronic equipment and storage medium
KR101395830B1 (en) Session checking system via proxy and checkhing method thereof
CN113411209A (en) Distributed password service full-link detection system and method
CN113760730A (en) Automatic testing method and device
CN110930110B (en) Distributed flow monitoring method and device, storage medium and electronic equipment
CN108900603A (en) A kind of server discovery methods, devices and systems
CN114610449B (en) Multi-cluster resource operation method and system based on unified request entry
CN114158074B (en) 5G network element address determination method and device, electronic equipment and storage medium
CN112491596B (en) Cloud-based fault processing method and device
CN113778709A (en) Interface calling method, device, server and storage medium
CN109412861B (en) Method for establishing security association display of terminal network
CN115361264B (en) Node management method, device, node, system and storage medium
CN115994072A (en) Log sampling method, related device and system
CN117499239A (en) Method, device, equipment and medium for automatically receiving and delivering cloud platform user into fort machine

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant