CN113037792B - A verification method, device and gateway for service identification parameters - Google Patents

Abstract

Embodiments of the present invention disclose a method, device and gateway for verifying service identification parameters, so as to solve the problem of verifying service identification parameters existing in the prior art. The verification method includes: the gateway obtains historical data, wherein the historical data includes historical service feature information and a historical service type identified according to the historical service feature information; the gateway matches the historical service feature information with the service identification parameters configured in the gateway, and The current service type corresponding to the historical service feature information is determined according to the matching result; the gateway compares the current service type with the historical service type, and verifies whether the service identification parameters configured in the gateway have changed according to the comparison result.

Description

A verification method, device and gateway for service identification parameters

technical field

The present invention relates to the field of data communication, and in particular, to a verification method, device and gateway for service identification parameters.

Background technique

In order to meet the diversified demands of increasingly abundant mobile Internet data services, mobile network operators need to identify specific service types of different services through service identification parameters configured in a PGW (Packet Data Network Gateway). Therefore, the service identification parameters have an important impact on the accuracy of the identification results, and it is necessary to verify the service identification parameters, such as verifying whether the service identification parameters have changed or whether the service identification parameters have been configured accurately.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide a method, device and gateway for verifying service identification parameters, so as to solve the problem of verifying service identification parameters existing in the prior art.

In order to solve the above-mentioned technical problems, the embodiments of the present invention are implemented as follows:

In a first aspect, a method for verifying a service identification parameter provided by an embodiment of the present invention includes:

The gateway obtains historical data, the historical data includes historical service feature information and a historical service type identified according to the historical service feature information;

The gateway matches the historical service feature information with the service identification parameters configured in the gateway, and determines the current service type corresponding to the historical service feature information according to the matching result;

The gateway compares the current service type with the historical service type, and verifies whether the service identification parameter configured in the gateway changes according to the comparison result.

In a second aspect, a method for verifying a service identification parameter provided by an embodiment of the present invention includes:

The gateway receives standard service feature information and a standard service type that matches the standard service feature information;

According to the standard service feature information, the gateway determines a historical service type that matches the standard service feature information from the historical data, wherein the historical service type is based on the historical service feature information of the historical service identification parameter configured by the gateway. identified;

The gateway compares the historical service type with the standard service type, and verifies the accuracy of the service identification parameters historically configured by the gateway according to the comparison result.

In a third aspect, an embodiment of the present invention provides a device for verifying service identification parameters, including:

a historical data acquisition unit, configured to acquire historical data, the historical data includes historical service feature information and a historical service type identified according to the historical service feature information;

a matching unit, configured to match the historical service characteristic information with the service identification parameters configured in the gateway, and determine the current service type corresponding to the historical service characteristic information according to the matching result;

A verification unit, configured to compare the current service type with the historical service type, and verify whether the service identification parameter configured in the gateway changes according to the comparison result.

In a fourth aspect, an embodiment of the present invention provides a device for verifying service identification parameters, including:

a standard service feature information receiving unit, configured to receive standard service feature information and a standard service type matching the standard service feature information;

A historical data query unit, configured to determine a historical service type matching the standard service characteristic information from historical data according to the standard service characteristic information, wherein the historical service type is based on the service identification configured by the gateway history The identification of historical business characteristic information by parameters is obtained;

A verification unit, configured to compare the historical service type with the standard service type, and verify the accuracy of the service identification parameters configured in the history of the gateway according to the comparison result.

In a fifth aspect, an embodiment of the present invention provides a gateway, including an apparatus for verifying any of the above-mentioned service identification parameters.

By adopting at least one of the above technical solutions provided by the embodiments of the present invention, the historical data acquired by the gateway includes historical service feature information of the service type identified by the gateway, and the historical service feature information is matched with the service identification parameters configured in the gateway to obtain The matching result is obtained based on the service identification parameters configured by the gateway. The current service type is compared with the historical service type, and the comparison result can indicate whether the service identification parameters have changed. Therefore, by using historical data to verify the service identification parameters, the verification of the service identification parameters can be completed quickly and accurately.

Description of drawings

In order to illustrate the embodiments of the present invention or the technical solutions in the prior art more clearly, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only These are some embodiments described in the present invention. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings without any creative effort.

1 is a schematic diagram of an application scenario of a verification method for a service identification parameter provided by an embodiment of the present invention;

2 is a schematic flowchart of a method for verifying a service identification parameter according to an embodiment of the present invention;

3 is a schematic flowchart of a method for verifying a service identification parameter according to an embodiment of the present invention;

4 is a schematic flowchart of a method for verifying a service identification parameter according to an embodiment of the present invention;

5 is a schematic flowchart of a method for verifying a service identification parameter according to an embodiment of the present invention;

6 is a schematic structural diagram of an apparatus for verifying service identification parameters according to an embodiment of the present invention;

7 is a schematic structural diagram of an apparatus for verifying service identification parameters according to an embodiment of the present invention;

8 is a schematic structural diagram of an apparatus for verifying service identification parameters according to an embodiment of the present invention;

9 is a schematic structural diagram of an apparatus for verifying service identification parameters according to an embodiment of the present invention;

FIG. 10 is a schematic structural diagram of a gateway according to an embodiment of the present invention.

Detailed ways

In order to make those skilled in the art better understand the technical solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described The embodiments are only some of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

In order to solve the problem of verifying the service identification parameters configured in the gateway in the prior art, an embodiment of the present invention provides a method for verifying the service identification parameters, which can be applied to the gateway. The gateway in the embodiment of the present invention may be a PGW (Packet Data Network Gateway), and a service identification parameter is configured in the PGW to match the service type. As shown in FIG. 1, when a terminal initiates a data service When accessing, the PGW receives the service data packet and identifies the service type.

Example 1

Embodiment 1 of the present invention provides a method for verifying service identification parameters, as shown in FIG. 2 , including the following steps:

Step 101: The gateway acquires historical data, where the historical data includes historical service feature information and a historical service type identified according to the historical service feature information.

Step 102: The gateway matches the historical service feature information with the service identification parameters configured in the gateway, and determines the current service type corresponding to the historical service feature information according to the matching result.

Step 103: The gateway compares the current service type with the historical service type, and verifies whether the service identification parameter configured in the gateway changes according to the comparison result.

In step 101, the historical data includes the historical service feature information and the historical service type identified according to the historical service feature information, that is, the service feature information that the gateway successfully matches the service type in the previous service identification process is the historical service feature information, which is The corresponding business type is the historical business type.

The historical data may include a preset number of historical service feature information that has recently matched the service type, and the preset number may be set according to the complexity of the configuration of the service identification parameters configured in the gateway and the accuracy requirements of the verification. If there are many business identification parameters, the configuration is more complex, and the verification accuracy is required to be high, the preset number can be set to a smaller value. On the contrary, if there are fewer business identification parameters, the configuration is relatively simple, and the verification accuracy requirements are low. Then the preset number can be set to a larger value.

The service feature information is the feature information of the user service, such as data packet size, delay, source IP address, source port number, URL, application layer protocol type, etc., which is obtained by the gateway by parsing the received service data packets.

For this embodiment of the present invention, the service feature information may be a destination address of data service access, for example, an IP (Internet Protocol, Internet Protocol address) applied to the OSI layer 3 protocol, or an IP address applied to the OSI layer 7 protocol. URL (Uniform Resoure Locator, Uniform Resource Locator).

The business type can be Sohu Video, Youku Video, Tencent Streaming Media or Xunlei Download, etc.

For the embodiment of the present invention, the service type may be characterized by a service identifier (full name in English: ServiceIdentification, English abbreviation: SID).

For the embodiment of the present invention, in step 101, the historical data acquired by the gateway may be as shown in Table 1.

Historical business type Historical business characteristic information 1 IP02, URL03 2 IP13 3 URL-12-1, URL-12-2

In step 102, the service identification parameter configured in the gateway may include multiple policy entries, and each policy entry may include a service type, an IP or URL matching condition satisfied by the service type, and a priority of the policy entry.

The service type may be characterized by a service identifier (full English name: ServiceIdentification, English abbreviation: SID).

The matching conditions for the IPs satisfied by the service type can be continuous IP address segments, such as IP01-10, or discontinuous independent IP addresses, such as "IP12, IP20". The matching condition of the URL that the service type satisfies can be an independent complete URL, such as URL-12, or it can be a simulated URL with an * sign.

The priority is the priority level set in the business identification parameter according to the implementation logic of business identification. Usually, the higher the priority, the smaller the priority value. For example, a priority value of 1 is usually the highest priority. When the gateway matches the service feature information with each policy entry in the service identification parameter, the matching is performed according to the order of priority from high to low, that is, the order of priority value from small to large.

For the embodiment of the present invention, in step 102, the service identification parameters configured in the gateway may be as shown in Table 2.

priority IP match condition URL matching conditions business identity 1 IP01-10 URL01-10 1 2 IP-13 2 3 IP-14 URL-13 3 4 URL-14 4

After the gateway obtains the historical data, it extracts the historical service feature information in the historical data, matches the historical service feature data with the service identification parameters configured in the gateway, and increases the priority value of each policy entry in the service identification parameter from small to large. Match the IP matching conditions and the URL matching conditions in order to determine the current service type corresponding to the historical service feature information.

The current service type corresponding to the historical service feature information may be as shown in Table 3.

Current business type Historical business characteristic information 1 IP02, URL03 2 IP13 3

In step 103, the gateway compares the current service type of the historical service characteristic information with the historical service type, and uses the historical service characteristic information of the changed service type as the comparison result, and the comparison result can be shown in Table 4.

Historical business characteristic information Historical business type Current business type URL-12-1 3 - URL-12-2 3 -

Based on the above comparison results, verify whether the service identification parameters configured in the gateway have changed.

It should be noted that, according to the verification result, the service identification parameters configured in the gateway may also be adjusted. For example, when the verification result shows that the service identification parameters configured in the gateway have changed, the changed service identification parameters can be adjusted according to the comparison result.

In the method for verifying service identification parameters provided by the embodiment of the present invention, the historical data acquired by the gateway includes all the service feature information of the service type identified by the gateway, and the historical service feature information is matched with the service identification parameters configured in the gateway to obtain The matching result is obtained based on the currently configured service identification parameters, and its corresponding historical service type is obtained based on the historically configured service identification parameters. Compare the current service type with the historical service type, and the comparison results Indicates whether the service identification parameters have changed. Therefore, using historical data to verify the service identification parameters can quickly and accurately verify whether the service identification parameters have changed.

Example 2

Embodiment 2 of the present invention provides a method for verifying service identification parameters. On the basis of Embodiment 1 as shown in FIG. 2 , in step 101, the gateway obtains historical data, which further includes the following steps as shown in FIG. 3 :

Step 201, the gateway identifies the historical service feature information based on the service identification parameters configured in the history to obtain the historical service type;

Step 202: The gateway stores the historical service feature information and the historical service type.

This embodiment mainly describes the acquisition process of historical data. The gateway must first receive service feature information, which can be understood as the gateway receiving service feature information of real-time services.

Generally speaking, the terminal sends a data service access request, and the gateway receives the data packet of the service access request, and parses the data packet to obtain service feature information. Therefore, the gateway receives the service characteristic information of the real-time service obtained by the analysis of the gateway, and this process is the actual working process of the gateway to identify the service type.

In step 201, the service identification parameters historically configured in the gateway can be understood as the service identification parameters configured in the gateway when the received service feature information performs service identification, as shown in Table 5.

priority IP match condition URL matching conditions business identity 1 IP01-10 URL01-10 1 2 IP-13 2 3 URL-12 3

The gateway matches the received service feature information with the service identification parameters configured in the history of the gateway. The gateway uses the service feature information whose service type is successfully determined as the historical service feature information. The gateway uses the historical service feature information and its corresponding history. The business type is stored in real time, and the business identification parameters can be verified as historical data later.

Example 3

Embodiment 3 of the present invention provides a method for verifying service identification parameters. On the basis of Embodiment 1 as shown in FIG. 2 , in step 101, the gateway obtains historical data, including the following steps as shown in FIG. 4 :

Step 301, the gateway detects whether the service identification parameter configured in the gateway changes;

Step 302: When it is detected that the service identification parameter configured in the gateway is suspected to have changed, the gateway acquires historical data.

In step 301, the gateway monitors the service identification parameters configured in the gateway, and mainly determines whether they have changed. The changes of the service identification parameters configured in the gateway may be addition, deletion and modification.

The addition of the service identification parameter can be understood as adding a new policy to the pre-stored service identification parameters, and configuring the service type, the IP or URL matching conditions satisfied by the service type, and the newly added policy entry for the newly added policy. priority.

The deletion of the service identification parameters can be understood as deleting one or several policies in the pre-stored service identification parameters.

The change of service identification parameters can be understood as a change in the priority of one or several policies. For example, the priority of a policy is lowered, and the priority value is changed from the original 2 to 3. It can also be understood as a policy or several policies. When the service type of a policy changes, for example, the service identifier of a policy changes from 1 to 2, it can also be understood as a change in the matching conditions of the IP or URL satisfied by the service type in a policy or several policies, such as a policy , the matching conditions of the IPs satisfied by the service type are changed from IP01-10 to IP01-05.

In step 302, when the service identification parameters configured in the gateway are found to be suspected of adding policies, deleting policies, changing priorities, changing service types, or changing the matching conditions of IPs or URLs that are satisfied by the service types, the gateway obtains historical data.

It should be noted that, in this embodiment of the present invention, for service identification parameters that are suspected to be deleted or changed, the gateway may acquire historical data, and complete verification of the service identification parameters based on the historical data. For a suspected newly added service identification parameter, that is, a policy newly added in the service identification parameter, when the gateway obtains historical data, the gateway may also obtain service feature information to be matched, which may include service feature information that satisfies the newly added service identification parameter.

It is understandable that, for the business identification parameters suspected to be deleted and suspected to be changed, the business feature information in the historical data is obtained for matching, and the historical business feature information in the historical data is based on the successful matching of all policies before the deletion and before the change. Therefore, all the service identification parameters of this part are verified; for the suspected newly added service identification parameters, since the feature information of the service to be matched may include the identification parameters that satisfy the suspected newly added service, this part of the service identification parameters is also verified. By using historical data to verify the suspected changed service identification parameters, and by comparing the matching results, it can be verified whether the service identification parameters configured in the gateway have changed.

In addition, the gateway can also periodically obtain historical data to verify the service identification parameters configured in the gateway. During specific implementation, historical data can be obtained for verification at predetermined time points every day, such as 7:00, 15:00 every day, etc. , or you can preset time intervals to periodically obtain historical data, such as every 30 minutes, every 60 minutes, etc.

It can be understood that the gateway periodically obtains historical data, verifies the service identification parameters configured in the gateway, and can also verify whether the service identification parameters configured in the gateway have changed by comparing the matching results.

Example 4

Embodiment 4 of the present invention provides a method for verifying service identification parameters, as shown in FIG. 5 , including the following steps:

Step 401, the gateway receives standard service feature information and a standard service type that matches the standard service feature information;

Step 402, the gateway determines the historical service type that matches the standard service characteristic information from the historical data according to the standard service characteristic information, wherein the historical service type is obtained based on the identification of the historical service characteristic information by the service identification parameters configured by the gateway history. ;

Step 403: The gateway compares the historical service type with the standard service type, and verifies the accuracy of the service identification parameters configured in the history of the gateway according to the comparison result.

In step 401, the standard service feature information can be understood as standard verification data for verifying a certain policy or several policies in the service identification parameters, and the standard service type corresponding to the standard service feature information is the confirmed and accurate service type.

For this embodiment of the present invention, the standard service feature information may be the destination address of data service access, for example, IP (Internet Protocol, Internet Protocol address) applied to the OSI layer 3 protocol, or applied to the OSI layer 7 protocol URL (Uniform Resoure Locator, Uniform Resource Locator).

Standard service feature information can be a single IP, a single URL, multiple IPs, or multiple URLs. When it is a single IP or a single URL, it can be used to verify whether a certain policy entry in the service identification parameter is correct. Multiple IPs or multiple URLs can be used to verify whether several policy entries in the service identification parameters are correct.

For the embodiment of the present invention, the standard service type may be characterized by a service identifier (full name in English: ServiceIdentification, abbreviation in English: SID).

The standard service feature information received by the gateway can be a suspicious IP or URL address, an IP or URL address selected according to verification requirements, or an IP or URL address selected according to the business requirements of a third-party service server.

In step 401, the standard service feature information and the standard service type of the standard service feature information received by the gateway may be as shown in Table 6.

Standard business type Standard Service Feature Information 1 IP12 3 URL-13

In step 402, the gateway determines the service type matching the standard service characteristic information in the historical data according to the standard service characteristic information. Among them, the historical data includes historical service feature information and historical service types identified according to the historical service feature information, that is, in the previous service identification process of the gateway, the service identification parameters configured in the gateway successfully matched the service type of the service feature information as the history. The service feature information, the corresponding service type is the historical service type.

The service identification parameters historically configured in the gateway may be shown in Table 7.

priority IP match condition URL matching conditions business identity 1 IP11-20 URL11-20 1 2 IP-15 URL-13 2 3 IP-5 URL-14 3

The historical service type in the historical data may be a matching result identified based on the service identification parameters in Table 7. In this embodiment of the present invention, the historical data may be as shown in Table 8.

Historical business type Historical business characteristic information 1 IP12 2 URL-13 3 IP-5 3 URL-14

The gateway queries the standard service feature information IP12 and URL-13 in Table 6 in the historical data such as Table 8, and it can be determined that in the historical data, the service type corresponding to the standard service feature information IP12 is 1, and the standard service feature The service type corresponding to the information URL-13 is 2. As shown in Table 9.

Historical business characteristic information Historical business type Standard business type IP12 1 1 URL-13 2 3

In step 403, the gateway compares the service type determined in the historical data with the standard service type, and uses the items with different historical service types and standard service types as the comparison result. In the embodiment of the present invention, the comparison result can be as shown in Table 10 shown.

Historical business characteristic information Historical business type target business type URL-13 2 3

The comparison result can be understood that among the service identification parameters historically configured in the gateway corresponding to the historical service feature information, the policy entries shown in Table 11 may be incorrectly configured.

priority IP match condition URL matching conditions business identity 2 IP-15 URL-13 2

As in the above steps, the gateway completes the verification of the accuracy of the service identification parameters configured in the history of the gateway according to the comparison result.

In the service identification parameter verification method provided by the embodiment of the present invention, the gateway determines the service type corresponding to the standard service feature information in the historical data, compares the service type determined in the historical data with the standard service type, and uses the historical data to verify the gateway. By verifying the service identification parameters historically configured in the gateway, incorrect parameters in the historically configured service identification parameters can be efficiently determined, and the accuracy of the historically configured service identification parameters of the gateway can be verified.

Example 5

Embodiment 5 of the present invention provides a verification device for service identification parameters, as shown in FIG. 6 , including the following units:

A historical data acquisition unit 501, configured to acquire historical data, wherein the historical data includes historical business feature information and a historical business type identified according to the historical business feature information;

A matching unit 502, configured to match the historical service feature information with the service identification parameters configured in the gateway, and determine the current service type corresponding to the historical service feature information according to the matching result;

The verification unit 503 is configured to compare the current service type with the historical service type, and verify whether the service identification parameter configured in the gateway has changed according to the comparison result.

In the device for verifying service identification parameters provided by the embodiment of the present invention, the historical data obtained by the gateway includes all service feature information of the service type identified by the gateway, and the historical service feature information is matched with the service identification parameters configured in the gateway to obtain The matching result is obtained based on the currently configured service identification parameters, and its corresponding historical service type is obtained based on the historically configured service identification parameters. Compare the current service type with the historical service type, and the comparison results Indicates whether the service identification parameters have changed. Therefore, using historical data to verify the service identification parameters can quickly and accurately verify whether the service identification parameters have changed.

Example 6

Embodiment 6 of the present invention provides a verification device for service identification parameters, which, on the basis of Embodiment 5 shown in FIG. 6 , further includes the following units as shown in FIG. 7 :

The historical service type identification unit 601 is used for identifying the historical service feature information based on the service identification parameters configured in the history to obtain the historical service type;

The historical data storage unit 602 is used for storing historical service feature information and historical service types.

Example 7

Embodiment 7 of the present invention provides a verification device for service identification parameters, which, on the basis of Embodiment 5 shown in FIG. 6 , further includes the following units as shown in FIG. 8 :

The monitoring unit 701 is configured to detect whether the service identification parameter configured in the gateway is suspected to have changed.

Example 8

Embodiment 8 of the present invention provides a verification device for service identification parameters, as shown in FIG. 9 , including the following units:

Standard service feature information receiving unit 801, configured to receive standard service feature information and a standard service type matching the standard service feature information;

The historical data query unit 802 is configured to determine the historical service type that matches the standard service characteristic information from the historical data according to the standard service characteristic information, wherein the historical service type is based on the service identification parameter configured by the gateway history to the historical service characteristic. information is identified;

The verification unit 803 is configured to compare the historical service type with the standard service type, and verify the accuracy of the service identification parameters configured in the history of the gateway according to the comparison result.

In the service identification parameter verification device provided by the embodiment of the present invention, the gateway determines the service type corresponding to the standard service feature information in the historical data, compares the service type determined in the historical data with the standard service type, and uses the historical data to verify the gateway. By verifying the service identification parameters historically configured in the gateway, incorrect parameters in the historically configured service identification parameters can be efficiently determined, and the accuracy of the historically configured service identification parameters of the gateway can be verified.

Example 9

An embodiment of the present invention further provides a gateway, the hardware structure shown in FIG. 10 includes: a processor, a memory, a bus, and a transceiver; wherein,

a processor for acquiring historical data, wherein the historical data includes historical service characteristic information and a historical service type identified according to the historical service characteristic information; and matching the historical service characteristic information with the service identification parameters configured in the gateway, and determine the current service type corresponding to the historical service feature information according to the matching result; and compare the current service type with the historical service type, and verify whether the service identification parameter configured in the gateway changes according to the comparison result;

A transceiver for receiving business information; and sending verification results;

The memory is used to store the service identification parameters and historical data configured in the gateway.

Example 10

An embodiment of the present invention further provides a gateway, including: a processor, a memory, a bus, and a transceiver; wherein,

The processor is used to determine the historical service type matching the standard service characteristic information from the historical data according to the standard service characteristic information, wherein the historical service type is based on the identification of the historical service characteristic information by the service identification parameters configured in the history of the gateway obtain; and, compare the historical service type with the standard service type, and verify the accuracy of the service identification parameters configured in the history of the gateway according to the comparison result;

a transceiver for receiving standard service feature information and a standard service type matched with the standard service feature information; and sending a verification result;

The memory is used to store the service identification parameters and historical data configured in the gateway.

The embodiment of the present invention further provides a system for verifying service identification parameters, including any gateway in the embodiment of the present invention.

Those skilled in the art can clearly understand that, for the convenience and conciseness of the description, only the division of the above-mentioned functional modules is used for illustration. In practical applications, the above-mentioned functions can be allocated to different functional modules as required. The internal structure of the device is divided into different functional modules to complete all or part of the functions described above. For the specific working process of the system, apparatus and unit described above, reference may be made to the corresponding process in the foregoing method embodiments, and details are not described herein again.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the device embodiments described above are only illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be Incorporation may either be integrated into another system, or some features may be omitted, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block in the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to the processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing device to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing device produce Means for implementing the functions specified in a flow or flow of a flowchart and/or a block or blocks of a block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture comprising instruction means, the instructions The apparatus implements the functions specified in the flow or flow of the flowcharts and/or the block or blocks of the block diagrams.

These computer program instructions can also be loaded on a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process such that The instructions provide steps for implementing the functions specified in the flow or blocks of the flowcharts and/or the block or blocks of the block diagrams.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

Memory may include non-persistent memory in computer readable media, random access memory (RAM) and/or non-volatile memory in the form of, for example, read only memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media includes both persistent and non-permanent, removable and non-removable media, and storage of information may be implemented by any method or technology. Information may be computer readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), Flash Memory or other memory technology, Compact Disc Read Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical storage, Magnetic tape cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media, such as modulated data signals and carrier waves.

It should also be noted that the terms "comprising", "comprising" or any other variation thereof are intended to encompass a non-exclusive inclusion such that a process, method, article or device comprising a series of elements includes not only those elements, but also Other elements not expressly listed, or which are inherent to such a process, method, article of manufacture, or apparatus are also included. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in the process, method, article of manufacture, or device that includes the element.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The above descriptions are merely embodiments of the present invention, and are not intended to limit the present invention. Various modifications and variations of the present invention are possible for those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included within the scope of the claims of the present invention.

Claims (10)

1. a verification method of a service identification parameter, is characterized in that, comprises: The gateway acquires historical data, and the historical data includes historical service feature information and a historical service type identified according to the historical service feature information; The gateway matches the historical service feature information with the service identification parameters configured in the gateway, and determines the current service type corresponding to the historical service feature information according to the matching result; The gateway compares the current service type with the historical service type, and verifies whether the service identification parameter configured in the gateway changes according to the comparison result. 2. The method of claim 1, wherein the method further comprises: According to the verification result, the service identification parameters configured in the gateway are adjusted. 3. The method according to claim 1 or 2, wherein before the gateway acquires historical data, the method further comprises: The gateway identifies the historical service feature information based on the service identification parameters configured in the history to obtain the historical service type; The gateway stores the historical service characteristic information and the historical service type. 4. The method of claim 1, wherein the gateway acquires historical data, specifically comprising: When it is detected that the service identification parameter configured in the gateway is suspected to have changed, the gateway acquires the historical data; or, The gateway obtains historical data periodically. 5. A verification method for a service identification parameter, comprising: The gateway receives standard service feature information and a standard service type that matches the standard service feature information; According to the standard service feature information, the gateway determines the historical service type that matches the standard service feature information from the historical data, wherein the historical data includes historical service feature information and historical service feature information identified according to the historical service feature information. Service type, the historical service type is obtained based on the identification of historical service feature information by service identification parameters configured in the history of the gateway; The gateway compares the historical service type with the standard service type, and verifies the accuracy of the service identification parameters historically configured by the gateway according to the comparison result. 6. A verification device for service identification parameters, comprising: a historical data acquisition unit, configured to acquire historical data, the historical data includes historical service feature information and a historical service type identified according to the historical service feature information; a matching unit, configured to match the historical service characteristic information with the service identification parameters configured in the gateway, and determine the current service type corresponding to the historical service characteristic information according to the matching result; A verification unit, configured to compare the current service type with the historical service type, and verify whether the service identification parameter configured in the gateway changes according to the comparison result. 7. The apparatus of claim 6, further comprising: A historical service type identification unit, configured to identify the historical service feature information based on the service identification parameters configured in the history to obtain the historical service type; A historical data storage unit, configured to store the historical service feature information and the historical service type. 8. The device according to claim 6 or 7, characterized in that, further comprising: A monitoring unit, configured to detect whether the service identification parameter configured in the gateway is suspected to have changed. 9. A verification device for service identification parameters, comprising: a standard service feature information receiving unit, configured to receive standard service feature information and a standard service type matching the standard service feature information; A historical data query unit, configured to determine a historical service type that matches the standard service characteristic information from the historical data according to the standard service characteristic information, wherein the historical data includes historical service characteristic information and according to the historical service characteristic information The historical service type identified by the feature information, the historical service type is obtained based on the identification of the historical service feature information by the service identification parameters configured in the history of the gateway; A verification unit, configured to compare the historical service type with the standard service type, and verify the accuracy of the service identification parameters configured in the history of the gateway according to the comparison result. 10. A gateway, characterized by comprising the service identification parameter verification device according to any one of claims 6-9.

Images