Signaling identification method, electronic equipment and computer readable medium
By establishing network element industrial parameter tables, URL industrial parameter tables and cell industrial parameter tables to match the signaling to be identified, the problem of insufficient recognition capabilities of signaling interfaces and business processes of the new 5G call system is solved, and higher recognition accuracy and call network optimization are achieved.
Patent Information
- Application Number
- CN202311255016.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-09-25
- Publication Date
- 2025-03-25
AI Technical Summary
When identifying the interfaces and business processes of network signaling, the new 5G call system lacks recognition capabilities and can only accurately identify less than 10% of processes.
By obtaining the working parameters information, URL information and cell feature information of the network element, establish the network element working parameters table, URL working parameters table and cell working parameters table, and match the signaling to be identified with these tables to determine their belonging interfaces and business processes.
It realizes accurate identification of the signaling interfaces and business processes of the new 5G call system, improves signaling recognition capabilities, and is conducive to the collection and detection of Internet logs, thereby optimizing the call network.
Smart Images

Figure CN119697165A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of communication technology, and in particular to a signaling identification method, an electronic device, and a computer-readable medium. Background Art
[0002] 5G new calls are ultra-clear voice calls, video calls and related value-added services based on 5G networks, such as 5GVoNR ultra-clear video calls, 5G video customer service, intelligent translation functions, screen sharing, remote collaboration, augmented reality (AR), fun calls, etc., which can provide users with visual, multimedia, and highly perceived ultra-clear call experience. Compared with the existing IP multimedia system (IMS, IP Multimedia Subsystem), such as Figure 1 As shown in the figure, new network logical entities have been added, including VoNR+ capability network elements, VoNR+ media plane, service access layer (AS, Access-stratum), media capability platform, and new call operation and management platform.
[0003] Unlike the IMS system, where the application layer protocol between network elements is mainly the Session Initiation Protocol (SIP) signaling, the control plane messages between different network elements introduced by 5G new calls follow the main 5G communication application protocol HTTP2 defined by 3GPP, and the messages between network elements are routed and distributed based on the Uniform Resource Locator (URL) of the resource. Unlike the URLs of each interface and each process defined by 3GPP, which have characteristic information, most of the URL definitions of 5G new calls are defined by equipment manufacturers. On the other hand, based on security and other considerations, one of the functions of the VoNR+ capable network element in the design of the 5G new call system is to serve as a bridge for internal and external communications in the IMS network. This results in a large number of control messages for the business AS that reflects the characteristics of 5G new calls that need to be forwarded to VoLTE and VoNR+ media planes through the VoNR+ capable network element. Most of these forwarded messages are also based on resource URLs. Because they are forwarded messages, there is almost no difference between the forwarded messages and the forwarded messages.
[0004] In order to ensure the normal operation of the new call system and provide users with a better new service experience, the Internet log data collection function based on the 5G new call application also needs to be launched simultaneously. One of the basic capabilities of the Internet log collection system includes accurately identifying the interface and business process to which each signaling on the network belongs. Without modifying the 3GPP-based 5G control plane message collection solution, 5G new calls can only identify less than 10% of the processes. Summary of the invention
[0005] The embodiments of the present disclosure provide a signaling identification method, an electronic device, and a computer-readable medium.
[0006] In a first aspect, an embodiment of the present disclosure provides a signaling identification method, comprising: obtaining the industrial parameter information of a network element, establishing a network element industrial parameter table, wherein the network element industrial parameter table includes an interface identifier of an interface of the network element and a process identifier of a business process in the interface; obtaining URL information, establishing a URL industrial parameter table, wherein the URL information represents a unique feature of a business process; obtaining cell characteristic information, establishing a cell industrial parameter table, wherein the cell characteristic information represents a unique feature of a cell in a signaling; matching the signaling to be identified with at least one of the network element industrial parameter table, the URL industrial parameter table, and the cell industrial parameter table, and determining the interface and business process to which the signaling to be identified belongs.
[0007] In a second aspect, an embodiment of the present disclosure provides an electronic device, comprising: one or more processors; a memory on which one or more programs are stored, and when the one or more programs are executed by the one or more processors, the one or more processors implement the signal element identification method described in the first aspect of the embodiment of the present disclosure.
[0008] In a third aspect, an embodiment of the present disclosure provides a computer-readable medium having a computer program stored thereon, and when the program is executed by a processor, the method for identifying an information element described in the first aspect of the embodiment of the present disclosure is implemented.
[0009] In the disclosed embodiment, based on the establishment of the network element engineering parameter table, the URL engineering parameter table, and the signal element engineering parameter table, the network element engineering parameter table, the URL engineering parameter table, and the signal element engineering parameter table can be arbitrarily combined to identify the interface and business process to which the signaling to be identified belongs, thereby achieving accurate identification of the interface and business process of the signaling in the call system, improving the signaling identification capability in the call system, and facilitating the collection and detection of Internet access logs in the call system, thereby further optimizing the call network. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] Figure 1 It is a schematic diagram of a new call network architecture;
[0011] Figure 2 is a flow chart of a signaling identification method in an embodiment of the present disclosure;
[0012] Figure 3 is a flowchart of some steps in another signaling identification method in an embodiment of the present disclosure;
[0013] Figure 4 is a flowchart of some steps in another signaling identification method in an embodiment of the present disclosure;
[0014] Figure 5 is a flowchart of some steps in another signaling identification method in an embodiment of the present disclosure;
[0015] Figure 6 is a schematic diagram of the composition of an electronic device in an embodiment of the present disclosure;
[0016] Figure 7 is a schematic diagram of the composition of a computer-readable medium in an embodiment of the present disclosure;
[0017] Figure 8 is a schematic diagram of a signaling identification system in an embodiment of the present disclosure;
[0018] Fig. 9 It is a schematic diagram of a processing flow of signaling identification in an embodiment of the present disclosure. DETAILED DESCRIPTION
[0019] In order to enable those skilled in the art to better understand the technical solution of the present disclosure, the signaling identification method, electronic device, and computer-readable medium provided by the present disclosure are described in detail below in conjunction with the accompanying drawings.
[0020] Example embodiments will be described more fully below with reference to the accompanying drawings, but the example embodiments may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. On the contrary, the purpose of providing these embodiments is to make the present disclosure thorough and complete and to enable those skilled in the art to fully understand the scope of the present disclosure.
[0021] In the absence of conflict, the various embodiments of the present disclosure and the various features therein may be combined with each other.
[0022] As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.
[0023] The terms used herein are only used to describe specific embodiments and are not intended to limit the present disclosure. As used herein, the singular forms "a", "an" and "the" are also intended to include the plural forms, unless the context clearly indicates otherwise. It will also be understood that when the terms "comprising" and / or "made of" are used in this specification, the presence of the features, wholes, steps, operations, elements and / or components is specified, but the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or groups thereof is not excluded.
[0024] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and the present disclosure, and will not be interpreted as having an idealized or overly formal meaning unless explicitly defined as such herein.
[0025] First, refer to Figure 2 , the present disclosure provides a signaling identification method, including:
[0026] S1. Obtain the engineering parameter information of the network element and establish a network element engineering parameter table, wherein the network element engineering parameter table includes an interface identifier of an interface of the network element and a process identifier of a service process in the interface;
[0027] S2. Obtain URL information and establish a URL work parameter table, wherein the URL information represents the uniqueness of the business process;
[0028] S3, obtaining cell characteristic information and establishing a cell parameter table, wherein the cell characteristic information represents a unique characteristic of a cell in the signaling;
[0029] S4. Match the signaling to be identified with at least one of the network element work parameter table, the URL work parameter table, and the cell work parameter table to determine the interface and business process to which the signaling to be identified belongs.
[0030] In some embodiments, the network element is a network element in a 5G new call system.
[0031] In the disclosed embodiment, a network element engineering parameter table is established, and the interface identifier of the interface and the process identifier of the service process are configured in the network element engineering parameter table, so that the interface and service process to which the signaling belongs can be identified based on the network element engineering parameter table.
[0032] In the embodiment of the present disclosure, a URL work parameter table is established, and the URL information represents the unique characteristics of the business process, which means that the URL information in the URL work parameter table can be used to uniquely identify the business process, so that the interface and business process to which the signaling belongs can be identified based on the URL work parameter table.
[0033] In the embodiment of the present disclosure, a cell engineering parameter table is established, and the cell characteristic information represents the unique characteristics of the cell in the signaling, which means that the cell characteristic information in the cell engineering parameter table can be used to uniquely identify the cell in the signaling, so that the interface and business process to which the signaling belongs can be identified based on the cell engineering parameter table.
[0034] On the basis of establishing the network element engineering parameter table, URL engineering parameter table and cell engineering parameter table, the network element engineering parameter table, URL engineering parameter table and cell engineering parameter table can be arbitrarily combined to identify the interface and business process to which the signaling to be identified belongs, thereby realizing accurate identification of the interface and business process of the signaling in the call system, improving the signaling identification capability in the call system, and facilitating the collection and detection of Internet access logs in the call system, thereby further optimizing the call network.
[0035] The embodiments of the present disclosure do not specifically limit how to establish the network element engineering parameter table.
[0036] In some embodiments, obtaining the engineering parameter information of the network element and establishing the network element engineering parameter table includes:
[0037] Obtaining the engineering parameter information of the network elements on both sides of each of the interfaces;
[0038] Allocating an interface identifier to each of the interfaces, wherein the interface identifiers of the interfaces are different from each other;
[0039] A process identifier is allocated to the business process in the interface, wherein the process identifiers of the business processes in the same interface are different from each other.
[0040] In some embodiments, different interfaces correspond to the same business process with the same process identifier.
[0041] In the disclosed embodiment, as long as the process identifiers of each business process in the same interface are unique, the process identifiers of the same business processes in different interfaces are the same, which is conducive to improving the accuracy of interface and business process identification. For example, if the process identifiers of the same business processes in different interfaces are the same, even if the interface is unclear, as long as the business process is determined, the scope of the interface can be determined.
[0042] The disclosed embodiment does not impose any special limitation on how to establish the URL work parameter table.
[0043] In some embodiments, obtaining URL information and establishing a URL parameter table includes:
[0044] Acquire the URL information according to the interface specification of the network element;
[0045] Determine the request method information corresponding to the business process;
[0046] The URL information and the request method information are added to the URL work parameter table accordingly to obtain the URL work parameter table.
[0047] In some embodiments, self-learning of URL parameter tables is supported.
[0048] Accordingly, in some embodiments, obtaining URL information and establishing a URL work parameter table further includes:
[0049] According to the interface specification of the network element, the URL information is obtained during the processing of the association process, wherein the URL information is carried in the association process;
[0050] The URL information is added to the URL work parameter table.
[0051] The disclosed embodiment does not specifically limit how to establish the cell engineering parameter table.
[0052] In some embodiments, obtaining cell feature information and establishing a cell engineering parameter table includes:
[0053] Decoding the signaling to obtain the cell characteristic information;
[0054] The business process information, interface information, and the cell characteristic information are added to the cell work parameter table accordingly.
[0055] In the disclosed embodiment, the network element engineering parameter table, the URL engineering parameter table, and the signaling element engineering parameter table can be arbitrarily combined to identify the interface and service flow to which the signaling to be identified belongs.
[0056] In some embodiments, matching the signaling to be identified with at least one of the network element work parameter table, the URL work parameter table, and the cell work parameter table to determine the interface and service flow to which the signaling to be identified belongs includes:
[0057] Matching the signaling to be identified with the network element engineering parameter table to identify the interface to which the signaling to be identified belongs;
[0058] The signaling to be identified is matched with at least one of the URL work parameter table and the cell work parameter table to determine the business process to which the signaling to be identified belongs.
[0059] In some embodiments, matching the signaling to be identified with at least one of the URL work parameter table and the cell work parameter table to determine the service process to which the signaling to be identified belongs includes:
[0060] In the case that the interface to which the signaling to be identified belongs is identified successfully, matching the signaling to be identified with the URL work parameter table or the cell work parameter table to determine the service process to which the signaling to be identified belongs;
[0061] In the event that identification of the interface to which the signaling to be identified belongs fails, the signaling to be identified is matched with the URL industrial parameter table to determine the interface and business process to which the signaling to be identified belongs; or the signaling to be identified is matched with the URL industrial parameter table to determine the business process to which the signaling to be identified belongs, and the information to be identified is matched with the URL industrial parameter table and the cell industrial parameter table to determine the interface to which the signaling to be identified belongs.
[0062] In some embodiments, matching the signaling to be identified with at least one of the network element work parameter table, the URL work parameter table, and the cell work parameter table to determine the interface and service flow to which the signaling to be identified belongs includes:
[0063] The signaling to be identified is matched with at least one of the URL work parameter table and the cell work parameter table to determine the interface and business process to which the signaling to be identified belongs.
[0064] In some embodiments, reference Figure 3 After matching the signaling to be identified with at least one of the network element work parameter table, the URL work parameter table, and the cell work parameter table, and determining the interface and service flow to which the signaling to be identified belongs, the signaling identification method further includes:
[0065] S51, extracting characteristic information of the signaling to be identified;
[0066] S52: Perform association processing on the characteristic information of the signaling to be identified according to an association algorithm.
[0067] In some embodiments, reference Figure 4 , the signaling identification method further includes:
[0068] S6. Configure at least one of the network element engineering parameter table, the URL engineering parameter table, and the cell engineering parameter table according to the signaling information of the office site.
[0069] In the disclosed embodiment, the engineering parameter table is configured according to the signaling information of the office point, thereby realizing customization of specific office points supporting the network element engineering parameter table, URL engineering parameter table, and cell engineering parameter table.
[0070] In some embodiments, reference Figure 5 , the signaling identification method further includes:
[0071] S7. Modify at least one of the network element engineering parameter table, the URL engineering parameter table, and the cell engineering parameter table according to the modification instruction.
[0072] In the disclosed embodiment, the industrial parameter table supports modification, which is conducive to modifying the configuration to adapt to network changes without upgrading the software.
[0073] Second, refer to Figure 6 , an embodiment of the present disclosure provides an electronic device, comprising:
[0074] One or more processors 101;
[0075] A memory 102, on which one or more programs are stored. When the one or more programs are executed by one or more processors, the one or more processors implement the signaling identification method described in the first aspect of the embodiment of the present disclosure;
[0076] One or more I / O interfaces 103 are connected between the processor and the memory and are configured to implement information exchange between the processor and the memory.
[0077] Among them, the processor 101 is a device with data processing capabilities, including but not limited to a central processing unit (CPU) and the like; the memory 102 is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory (FLASH); the I / O interface (read-write interface) 103 is connected between the processor 101 and the memory 102, and can realize information interaction between the processor 101 and the memory 102, including but not limited to a data bus (Bus) and the like.
[0078] In some embodiments, the processor 101 , the memory 102 , and the I / O interface 103 are connected to each other via a bus 104 , and further connected to other components of the computing device.
[0079] Thirdly, refer to Figure 7 The embodiment of the present disclosure provides a computer-readable medium on which a computer program is stored. When the program is executed by a processor, the signaling identification method described in the first aspect of the embodiment of the present disclosure is implemented.
[0080] In order to enable those skilled in the art to more clearly understand the technical solutions provided by the embodiments of the present disclosure, the technical solutions provided by the embodiments of the present disclosure are described in detail below through specific embodiments:
[0081] Embodiment 1
[0082] 5G new call network architecture diagram Figure 1 , Figure 1The medium-service AS (short for intelligent network, new call application server), new call operation and management platform, VoNR+ capability network element, VoNR+ media plane, and media capability platform are all newly added network elements relative to the existing IMS network. The IMS network usually refers to the network elements including SBC (including control plane and user plane: SBC-C, SBC-U), P / I / S-CSCF, VoLTE AS, PCF / PCFRF, HSS / UDM, ENUM / DNS, etc.
[0083] Almost all the control plane signaling between the newly added network elements of 5G new calls is based on HTTP2. Specifically, as shown in Table 1, interface 3, interface 4, interface 5, interface 7, interface 8, interface 9, interface 11, interface 14, and interface 17 are all based on HTTP2. Interface 3 is the communication entrance between 5G new calls and IMS control plane. After receiving the subscription and control messages from the VoNR+ capable network element, the VoLTE AS will report notification messages and control result messages to VoNR+; interface 4 is due to the new features of 5G new calls. VoLTE AS will transfer instructions such as application, change, and release of media resources to the VoNR+ media plane. Interface 9 is the interface between the service AS and the VoNR+ capable network element. The key control plane signaling of 5G new calls basically comes from interface 9. After receiving the message from interface 9, the VoNR+ capable network element will forward the call control message to the VoLTE AS through interface 3; and will forward the service control message to the VoNR+ media plane through interface 5. Interface 7 is mainly used for resource negotiation, media data forwarding and result processing between the VoNR+ media plane and the media capability platform; interface 8 is the interface for the service AS to trigger a specific new call application.
[0084] Table 1
[0085]
[0086]
[0087] See Table 2 for the interface parameters of the 5G new call. The interface parameters are essentially another form of link parameter set. The XDR output in the Internet log collection system needs to use the Interface field to express the connection between two specific network elements. Table 2 gives the configuration instructions for some interfaces in the 5G new call. The interface parameter table mainly specifies the interface identifier, which usually needs to be consistent with the collection specification. It is also possible to use a new method to distinguish internally, but when the XDR is finally output, it is converted into a definition consistent with the collection specification.
[0088] Table 2
[0089] interface Interface ID Network element 1 Network element 2 Interface 3 166 VoNR+ Capability Network Elements VolteAS Interface 4 167 VolteAS VoNR+Media Interface 5 168 VoNR+ Capability Network Elements VoNR+Media Interface 7 170 VoNR+Media Media Capability Platform Interface 8 171 Business AS Media Capability Platform Interface 9 172 Business AS VoNR+ Capability Network Elements
[0090] Please refer to Table 3 for the engineering parameters of the new 5G call network elements. The collection of Internet logs needs to be accurate to the network elements, interfaces, and processes triggered by the messages; the collection scope is limited by the network element engineering parameters. The network element engineering parameters mainly configure the specific network element name, IP address type, IP address and other link-related information. During the initial start-up, the network element link information of the existing network is generally obtained in advance before the start-up, from which the network element engineering parameter information can be extracted, or the network element link information can be reused. After running for a period of time, if the main device network element is added or changed, the configuration can be increased after passively receiving the information, or it can be supplemented by the self-learning method of this embodiment.
[0091] Table 3
[0092] Network element name IP Type IP address source Business AS V4 10.126.128.194 Manual Configuration VoNR+ Capability Network Elements V4 10.126.126.104 Manual Configuration VoLTE AS V4 10.126.118.204 Manual Configuration Media Capability Platform V4 10.116.128.194 Manual Configuration VoNR+Media V4 10.106.126.104 Self-learning New call operation management platform V4 10.136.118.204 Self-learning
[0093] The request URL parameter of the 5G new call request message is shown in Table 4. Part of the configuration information in the URL parameter comes from the content clearly defined in the main device interface specification, and part of it is obtained by self-learning in combination with the understanding defined in the main device interface specification. The URL parameter table contains the request method, request URL feature information, destination interface, and destination process of the destination message used for matching. For example, the sequence numbers 1, 2, and 3 in Table 4 record the call event subscription, call event subscription update, and call event subscription cancellation processes in interface 3, respectively. These three processes have the same URL, but different request methods: the request method for call event subscription is POST, the request method for call event subscription update is PATCH, and the request method for call event subscription cancellation is DELETE. Therefore, these three processes can be identified by URL+request method. Similar processes with unique feature information in the request URL include sequence numbers 4, 5, and 6 in Table 4. According to the interface specification of the main device, the request URLs of some processes related to the multi-party conference of subscription interface 9, interface 7, interface 8, interface 11, and other interfaces are also unique.
[0094] Table 4
[0095]
[0096]
[0097] Some information in the URL parameter table comes from the self-learning of the program. The self-learning content is also understood in combination with the definition in the specification. When processing the associated process, the parameters carried in the associated process that express a meaning similar to callbackUrl are learned together with the request method of this process. For example, in sequence number 10 in Table 4, when the VoNR+ capable network element sends a call event control message to the VoLTE AS, it carries the URL for receiving subsequent call control result notifications in the request message, that is, {callbackUrl}. For example, Table 5 is the definition of the call event control interface from, and Table 6 is the interface definition of call control result notification in the specification. The request parameter callbackUrl in Table 5 is the content of the request URL in Table 6. In the new 5G call, the process definition of the callbackUrl method used for the subsequent message accounts for the vast majority. For example, interfaces 3, 5, 8, and 9 all have processes that use callbackUrl as the request URL. Because the definition expressions in the interface specifications are basically similar, Table 4 only selects a few records. Among them, callbackUrl is just a representation of meaning. The {notifyURL}, {callUrl}, {ttsCallbackUrl}, {duplicationCallbackUrl}, etc. in the interface specification all express the URL that the message sending network element hopes to use for subsequent request messages. The meaning is meaningful. For the convenience of expression, callbakUrl is used to represent them.
[0098] Table 5
[0099]
[0100]
[0101] Table 6
[0102]
[0103] The request message uses the request line to match the URL parameters. This can be achieved by quickly decoding and extracting the first line of information in the signaling. This method is simple to implement and has the highest performance.
[0104] See Table 7 for the cell parameters in the 5G new call network element. The information of the cell parameters requires deep decoding of the received HTTP2 code stream. The cell parameters table can be used to solve the problem that the use of URL parameters cannot identify the interface to which the message belongs. For example, record 7 in Table 4 registers 101: media stream replication application process. The URL may be interface 5 or interface 9. If the network element parameters are not used, it can be found from Tables 8 and 9 that both interfaces carry mandatory request parameters. For example, in Table 8, the media stream replication application of interface 9 carries the appId parameter. Then, after the URL parameters are matched, the cell parameters table can be further used for identification. The use of cell parameters is basically equivalent to fully decoding the entire signaling. If performance is not considered, the use of cell parameters alone can also achieve the effect of signaling process identification to a certain extent, but it cannot cover all. For example, the request number collection process for both interface 5 and interface 9 has no signaling difference. At this time, if the network element parameters are combined, segmentation can be achieved.
[0105] Table 7
[0106]
[0107]
[0108] Table 8
[0109]
[0110] Table 9
[0111]
[0112] Signaling identification system such as Figure 8 As shown, the logical module division of the online log data collection and data processing system usually includes four parts: data collection module, data cleaning module, data association synthesis module, and data distribution module. Among them, this embodiment mainly involves data collection module and data cleaning module. Among them, data collection mainly performs hierarchical analysis on data after accessing network signaling, and then distributes it according to interface, business, and process. The data cleaning module performs data analysis and keyword extraction according to the requirements of the collection specification and outputs the extracted information to XDR according to the standard collection specification.
[0113] The signaling identification process is as follows: Fig. 9 As shown, the message recognition and the self-learning of the working parameters are gradually performed in a hierarchical manner mainly from the perspective of performance. The specific details are described in the second embodiment, the third embodiment, and the fourth embodiment.
[0114] Embodiment 2
[0115] In this embodiment, Figure 8As shown in the figure, the signaling identification system includes: data acquisition module, data cleaning module, data association synthesis module, and data distribution module. Among them, data association synthesis mainly uses various association algorithms to associate the number, location and other information in the XDR, and the algorithms of different systems are different; the data distribution module sends the processed XDR to a third-party server such as an Internet log query system, a sub-system, etc. Because data cleaning and data association synthesis are logically independent, but they may be unified in specific implementation. If they are unified, data association synthesis will also be affected. For the sake of clarity, data cleaning and data association synthesis are described separately.
[0116] Data acquisition module: Uses replication technology such as splitting to replicate the signaling of each network element between the main devices and then routes it to the designated access module, such as a convergence splitter. After receiving the signaling, the data acquisition module performs signaling layer identification, and ultimately needs to identify the application layer protocol, and then implement separate processing of different signaling based on specific application protocol types. 5G new calls are an extended application of IMS, so the control plane signaling will also involve protocols currently used by IMS networks such as SIP and Diameter. The data acquisition module remains unchanged for processing these messages. The communication between the newly added functional entities in 5G new calls is mainly based on the processing of the HTTP2 protocol, so the data acquisition module needs to add HTTP2 identification when identifying the application layer protocol. After the data acquisition module identifies that it is an HTTP2 message, it will send the message to the HTTP2 submodule for processing.
[0117] The HTTP2 submodule performs interface and process identification. Due to the particularity of 5G new calls, the interface and process identification requires a combination of multiple methods to improve the accuracy of message identification; specifically, it is divided into two major categories and multiple subcategories. The two major categories are mainly subdivided based on whether the source address and destination address of the signaling are in the network element engineering parameter table.
[0118] Embodiment 3
[0119] This embodiment is based on the signaling identification system provided in Embodiment 2, and the signaling identification includes the following processes:
[0120] Step 1: Obtain IP engineering parameter information of network elements on both sides of each interface in the existing 5G new call system from the operator, including IMS network elements. In particular, it is necessary to see the IP information of network elements such as VoNR+ capability network elements, VoNR+ media plane, service AS, media capability platform, new call operation management platform, VoLTE AS, etc. The network element engineering parameters mainly need to include link-related information such as network element name, network element IP, IP type, etc., as shown in Table 3.
[0121] Step 2: Allocate a unique ID to all interfaces, such as interface 3: 166, interface 4: 167, etc. Generate an interface engineering parameter table, as shown in Table 2. The interface engineering parameter information shown in Table 2 and the network element engineering parameter sample shown in Table 3 are all logical designs. In actual software implementation, they can be expressed through equivalent information such as links and office directions on the network management interface, or they can be implemented in the form of scripts, codes, etc.
[0122] Step 3: Assign a unique ID to each specific service flow of the interface. For example, the interface 3 flow between the VoNR+ capability network element and the VoLTE AS can be assigned a flow ID as follows:
[0123] 0: Session detection
[0124] 1: Call event subscription
[0125] 2: Call event subscription update
[0126] 3: Call event subscription cancellation
[0127] 4: Call event notification
[0128] 5: Call event control
[0129] 6: Call control result notification
[0130] The process ID is allocated to ensure that it is unique within the interface. To improve the accuracy of the interface-process, the process ID of the same message of different interfaces can be defined as a unified one. In this way, even if the interface is unclear, the interface is limited in scope because the process is identified. In the new 5G call, because there are a large number of message forwardings, the process ID of the same message can be defined as the same ID. For example, interface 9 contains the 1-6 processes of interface 3, so the same process of interface 9 also uses the same ID. The interface ID of the second step and the process ID of the third step can be defined within the data collection system, or they can follow the definition according to the collection specification. The specific implementation is not limited, and the uniqueness within the interface can be guaranteed; the final ID can be converted according to the specification requirements. .
[0131] Step 4: Establish a URL work parameter table, which needs to include request method, request URL, destination interface, and destination process information. First, by studying the interface specification of the main device, collect all interfaces, processes, request methods, and request URL information based on the HTTP2 process, and then based on this information, enter the URL information in the specification that can identify the uniqueness of the process through the request URL into the URL work parameter table as the baseline data of the URL work parameter table. For example, in several processes related to call subscription of interface 3, the request URL contains the characteristic string "subscriptions / call-events / notifications / number / ". When the protocol machine receives the HTTP2 request message, if the request URL contains the above characteristic character information, it can be determined that the message belongs to the interface 3 message; further combined with the request method, if the request method is POST, the message belongs to the call event subscription message of interface 3; if the request method is DELETE, the message belongs to the call event subscription cancellation message of interface 3. Similarly, the processes of interface 9 such as GSCP query message, location information acquisition, and sending short messages can simply identify the interface and process by matching the characteristic characters in the request method + request URL. The request URL configured in the URL work parameter table is the unique information in the process request URL that has been clearly stated in the interface specification. For example, the intelligent translation control process request URL definition of interface 8 is recorded in sequence number 4 as: "{callbackURL} / translationcontrol". Because "translationcontrol" is a typical business feature, "translationcontrol" can also be used directly to replace the complete URL. If you want to improve the accuracy, you can also concatenate the parameters receiver and " / translationcontrol" obtained from the media copy process response of interface 9 and learn them in the URL work parameter table.
[0132] Step 5: The data in the URL parameter table can come not only from the standardized process information, but also from the self-learning information. Moreover, the request URLs of most processes in 5G new calls come from other related processes, so the content of self-learning is the focus. The process of self-learning interfaces and processes is: by studying the definition of the interface specification of the main device, obtaining the association algorithm, and then implementing it through software. Such as the sequence numbers 10-15 in Table 4. Among them, sequence number 10 is learned in the interface. When the call control message is sent from the VoNR+ capable network element to the Volte AS of interface 3, the information element callbackUrl is carried: the result notification URL of the call control, see Table 5. From Table 6, it can be seen that according to the definition of the call control result notification request URL, the content of the request URL of the message is only {callbackUrl}, from which the information "{callbackUrl}, notification address, the format of {callbackUrl} obtained from the {callbackUrl} parameter in the call control instruction is customized by the platform manufacturer". According to the interface definition of the main device, when processing the call control message, the data cleaning module needs to learn this {callbackUrl} together with the request method of the process call control result notification message into the interface and process parameter table to facilitate the subsequent interface and process identification. Similar related processes exist in almost every interface. For example, the playback request of interface 5 and interface 9 carries the request URL of the playback result notification, the response of the media element synthesis application process carries the request URL of the media element synthesis stop, the request message of the number collection request carries the request URL of the number collection result notification, and the response message of the number collection request carries the request URL of the number collection stop. Interfaces 4, 7, 8, 11, etc. also have similar related processes, which are not listed here. Sequence number 12 in Table 4 is obtained through cross-interface learning. As shown in Table 10, in the process of intelligent translation control interface of interface 8, the request parameter carries notifyURL. The request URL of the intelligent translation result notification of interface 7 in Table 11 directly uses {notifyURL} / send. Therefore, when processing the 201 process of interface 8: intelligent translation control process, {notifyURL} needs to be concatenated with " / send" and stored as a URL. In cross-interface learning, there are other processes of interface 7. The request URLs of all processes of interface 7 are obtained through learning, such as the push media replication process: VoNR+ media pushes the duplication code stream application to the media capability platform. The URL of the request is defined in the interface as {duplicationCallbackUrl}, which is the receiving end URL address obtained from the media replication request of interface 5. From Table 9, it can be seen that the definition of the request parameter url in the process of "101: media stream replication / forwarding application" of interface 5 is "the URL of the media replication receiving end. The media plane pushes the control plane information of media stream replication through this URL."Therefore, when processing the "101: Media stream copy / forward application" process of interface 5, it is necessary to learn the request parameter url together with the request method of interface 7 into a record and write it into the URL record table. There are other processes for cross-interface learning and they are not described in full.
[0133] Table 10
[0134]
[0135] Table 11
[0136]
[0137] Step 6: Establish a cell parameter table, as shown in Table 3. The cell parameter configures a unique cell in a signaling; when there are similar processes that need to be subdivided, the cell characteristics can improve the recognition rate of the data process. The cell parameter involves full decoding. Considering the performance resources, it needs to be used last, and the configuration of the cell parameter needs to be as simple as possible. Without considering the performance consumption, the use of the cell parameter can also play the same effect as the URL parameter. The cell parameter can match and obtain the interface and process; because some messages of the 5G new call are forwarded, the cell parameter cannot solve all problems. The use of the cell parameter needs to be combined with the network element parameter and the URL parameter. For example, in the process that exists in both interface 5 and interface 9: 101: media stream copy / forward application, the subtle difference between the two signalings is that interface 9 will carry the comparison cell appId (as shown in Table 8). Then, when the request URL is the same and the interface is uncertain, through deep analysis, if the appId exists, it means that it is the process of interface 9, otherwise it means the process of interface 5. Then, for this difference, it can be entered into the cell engineering parameters shown in Table 7. Also, when the dependent request URL does not collect the associated process, but the message has been matched to the engineering parameters of interface 7, the interface and process can be identified as much as possible through the cell engineering parameters. For example, if the associated URL of "221: Push media copy / forward information" of interface 7 is not learned, the message can be determined to belong to the "221: Push media copy / forward information" process of interface 7 by the fact that the cell contains Mediatype and sdp cells. The content filled in the cell engineering parameters should be concise, and the process identification should be as accurate as possible when the network element engineering parameters and / or URL engineering parameters are invalid.
[0138] Step 7: The data collection module uses the network element engineering parameters, URL engineering parameters, and information element engineering parameters in pairs or in combination to identify the interface and process to which the HTTP2 signaling belongs. Method 1: Network element engineering parameters + URL engineering parameters: Use network element engineering parameters to match the source address and destination address. If the match is successful, the interface can be determined. After the interface is determined, the process information is obtained through URL engineering parameters. Method 2: Network element engineering parameters + information element engineering parameters to identify the process: In method 1, the network element engineering parameters can be matched successfully to determine the interface, and the information element engineering parameters can be used to further determine the process. Method 3: Joint use of URL engineering parameters + information element engineering parameters: When the network element engineering parameters fail to match, the process can be identified through the URL engineering parameters if the match is successful. If the interface is unique, the interface can also determine the interface and process; if the interface obtained in the URL engineering parameters is not unique, the information element engineering parameters need to be used to obtain the interface. Method 4: Directly use URL engineering parameters or information element engineering parameters to match to obtain the interface and process. Method 5: It is also possible to use URL engineering parameters first and then use the network element engineering parameter table. In short, the use of network element engineering parameters, URL engineering parameters, and signal element engineering parameters is arbitrary. From the perspective of performance, the order of advancement is to first use network element engineering parameters to determine the interface, and then use URL engineering parameters and signal element engineering parameters to determine the process.
[0139] Step 8: If the interface is learned through URL engineering parameters or cell engineering parameters, such as method 3 in step 7, method 4 requires learning the source address and destination address of the code stream into the network element engineering parameters. Self-learned network element engineering parameters can enrich the engineering parameter information omitted in manual configuration, and can also speed up the interface and process identification of subsequent messages.
[0140] Step 9: After identifying the specific interface and process, the data cleaning module needs to learn the {callbackUrl} (here it refers to the URL used to express subsequent messages in all interface definitions) required for the request URL of the subsequent process in accordance with the definition of the main device specification, combined with the request method, specific interface, and process information, and store them in the URL work parameter table. These self-learned {callbackUrl} are part of the data source of the URL work parameter table, which can speed up the interface and process identification of subsequent messages.
[0141] Step 10: In particular, the initial service operation request URL in the service control message of the 5G new call is all based on the resource flow, so the composition of the request URL includes {stream_url}. At the same time, the request URL of these service processes also contains information with service characteristics, such as sequence numbers 7-9 in Table 4. In this way, the URL can omit {stream_url}, but this can only determine whether it is a specific process of interface 9 or interface 5. When the network element engineering parameters are determined, the specific interface and process can be determined; if the network element engineering parameters are uncertain, further distinction is required with the help of the signal element engineering parameters. In addition to the special relationship between interface 9 and interface 5, the request URL of some interfaces also contains characteristic information. The dynamically generated part can also be removed and the characteristic information can be directly stored. For example, sequence number 4 in Table 4: intelligent translation control of interface 8, although the request URL is defined as {callbackURL} / translationcontrol, after standard learning, it can be known that the interface and process can also be determined by using the characteristic character "translationcontrol". This step mainly wants to express that the request URL can be simplified to improve efficiency. If you don't mind the performance impact, it is also possible to use a complete URL.
[0142] Step 11: In particular, for unrecognized processes, it is recommended to archive them by interface. You can fill in the interface of the unrecognized message as much as possible, and extract the request method and request URL. In addition to simple identification of unknown processes, statistics are also required to facilitate data verification and quality analysis reference. In particular, if you want to improve the recognition rate of signaling processes, you can also sacrifice space and efficiency for accuracy. Specifically, cache the unknown process for 5 seconds or other appropriate time and then enter the interface and process learning again. It is mainly used to deal with extreme conditions: scenarios where the self-learning URL is not learned and the network element engineering parameters are not learned.
[0143] Step 12: After identifying the interface and message flow, it is necessary to extract the information in the signaling according to the collection specification requirements and output it to the data association synthesis module according to the collection specification requirements.
[0144] Embodiment 4
[0145] In this embodiment, the source address and destination address of the signaling to be analyzed are in the network element engineering parameter table. Fig. 9 As shown, including:
[0146] 1001: the HTTP2 submodule of the data processing module receives the original signaling;
[0147] 1002: Use the most efficient method: match the source address, destination address and network element working parameters (as shown in Table 3) of the message;
[0148] 1003: If both the source address and the destination address match successfully, the interface to which the message belongs can be accurately identified.
[0149] 1004: After further interface identification, the request URL features of the interface signaling are combined with the URL parameter table for matching and judgment. In particular, after the network element parameter is determined, the signal element parameter can also be used in 1004. The two can be used separately or in combination, because the URL can be obtained by fast decoding, and the performance digestion is the lowest, so the URL parameter is used first.
[0150] 1005: If the match is successful, the specific process can be accurately identified.
[0151] 1006: After the interface and process of this message are clarified, if there are callbackUrl parameters of other related interfaces in the process, the callbackUrl needs to be learned and recorded in the URL work parameter table together with the request method, interface, and process information of the related process.
[0152] 1007: Extract characteristic information from signaling according to the requirements of the collection specification
[0153] 1008: Maintenance of context information such as user number, location, service size and class.
[0154] The use of URL engineering parameters and cell engineering parameters in 1004 is explained in the following application examples. Interface 3 is used as an example. In interface 3, if the interface is clear, the call event subscription, call event subscription update, and call event subscription cancellation of interface 3 can be identified through the URL engineering parameter information entered in the specification, corresponding to sequence numbers 1-3 in Table 4. If the collection device does not collect processes 1 and 2, or preferentially collects the call event notification message of interface 3, the URL engineering parameter matching will fail. At this time, through the cell engineering parameter matching, if the message carries the callEvent cell, the process can still be determined, sequence number 2 in Table 7. Similarly, the call control of interface 3 (sequence number 3 in Table 7) and the call control result notification process (sequence number 4 in Table 7) can also identify the process through the cell engineering parameters. Under the premise that the interface is known, the cell engineering parameters can also be used directly without considering the performance impact.
[0155] Embodiment 5
[0156] In this embodiment, the source address and destination address of the signaling to be analyzed are not in the network element engineering parameter table. Fig. 9 As shown, the 2001 and 3001 processes are two different sub-category methods, both of which are equivalent to 1004, in no particular order.
[0157] 2001: After receiving the original signaling, the HTTP2 submodule of the data processing module fails to match the network element industrial parameters, or directly uses the URL industrial parameter matching algorithm. In short, the interface is unknown.
[0158] 2002: Quickly decode to obtain the information of the first line, extract the request method and characteristic URL information, and match it with the URL parameter table.
[0159] 2003: The URL work parameter is matched successfully, the record corresponding to this process is retrieved, and the process and interface information are obtained.
[0160] 2004: After the process is determined, it is also necessary to determine whether the interface is unique (such as sequence number 4, sequence number 5, sequence number 6 in Table 4). In particular, if the request URL is not unique, it may belong to multiple interfaces. For example, sequence numbers 7-9 and sequence number 16 in Table 4 are examples of non-unique request URL features.
[0161] 2005: If the interface is unique, the network element information learned in this process can be compared with the network element engineering parameter database. If the engineering parameter database does not exist, the source address and destination address learned in this process can be learned into the network element engineering parameter table.
[0162] Then comes the general process: 1006 learning the URL of the associated interface and process, 1007 signaling feature extraction, user number, location, 1008 service size category and other context information maintenance.
[0163] 3001: The use of cell parameters is the same as URL parameters. You can also directly obtain interface and process information by matching cell parameters. The content of the cell can be the content other than the first line of the HTTP2 message (request line / response line), including the message header and message body: the message header, message body, and the parameters in the message body are all cells.
[0164] 3002: Through the study of interface specifications, it can be found that different processes will also carry different headers, that is, some specific processes will carry specific header information. For example, the media stream copy process in Table 8 and Table 9 will carry the headers "Content-type" and "X-Type". But interface 9 may also have "Authorization". In sequence number 1 in Table 7, after the process is determined with the help of the URL, "Authorization" can also determine the interface.
[0165] 3002: Further: the existence or non-existence of the message body can also be used to determine the process under the interface determination. The request URLs of the two messages, subtitle video synthesis update and subtitle video synthesis stop, are exactly the same, but the request method, message header, and message body are different. These three conditions can be used to identify the process. When the request method is known, the request method and the request URL can be implemented in 2001-2003; if the request method is unknown (for example, the dynamic dictionary is invalid), the specific process can also be identified with the help of the cell parameters. For example, the subtitle video synthesis update process of interface 9, sequence number 11 in Table 7, can also be identified by whether the message body exists or whether Content-type| exists.
[0166] 3002: For messages with message bodies, the HTTP2 message can be fully decoded and matched using the cell parameters. Sequence number 8 in Table 7 records the USSD interface process information of interface 9. Among all new 5G calls, only the USSD of interface 9 will carry the three parameters of "appId&&address&&body" at the same time; similarly, the setting screen selection of interface 9 (sequence number 9 in Table 7) also has a unique characteristic cell "videoTop" in the process. Such unique cell parameters can be matched successfully when matching cell parameters.
[0167] In particular, the 3002 process involves full decoding, which consumes a lot of performance. It is recommended to use it after the network element parameter and URL parameter matching cannot achieve the effect of identifying the interface process. For example, in the case of No. 7 in Table 4, if the network element parameter matching fails and the URL parameter matching can only determine that the interface range is interface 9 or interface 5, the interface can be identified by using the cell matching after full decoding. For example, No. 1 in Table 7 records that the media stream copy application message of interface 9 must carry the field "appId". If the match is successful, it can be determined that the signaling belongs to interface 9. If the match is identified, the signaling belongs to interface 5.
[0168] 3003: After the match is successful, the interface and process information can be obtained from the cell parameters.
[0169] 3004: In particular, there is no order in which network element engineering parameters, URL engineering parameters, and cell engineering parameters are used. If the source address and destination address of the bearer signaling are not in the network element engineering parameter table, the new source address and destination address can be learned into the network element engineering parameter table.
[0170] Embodiment 6
[0171] 4001: Do not discard the unrecognizable HTTP2 signaling, and treat it as unknown signaling for normalization. If the interface information that can be matched by the interface parameters can be filled in, fill it in. Considering that the out-of-order part of the message depends on the signaling of the associated process and may arrive late, in this case, if resources permit, the unknown signaling can be cached, and the interface and process identification 1001\1002\1003 can be performed again after the configurable cache time. The statistical results of unknown messages can also provide a reference for network optimization.
[0172] 4002: When it is finally determined that it is an unknown message, basic information needs to be extracted: such as source address, destination address, source port, destination port, request method, request URL, response code and other basic information.
[0173] After receiving the signaling sent by the data acquisition module, the data cleaning module 120 will extract the corresponding feature information of the signaling according to the result of the identified interface process. This is a general demand function. The collection of 5G new call signaling requires the data cleaning module to learn the URLs needed for other related process identification and store them in the URL work parameter table 1006.
[0174] After the data cleaning module completes data extraction, it needs to generate XDR and send it out according to the collection specification requirements.
[0175] In principle, the identification of HTTP2 interfaces and processes is that the use of network element engineering parameters, URL engineering parameters, and information element engineering parameters has no order or dependency constraints. You can first use the network element engineering parameters to obtain the interface, and then identify the process; you can also directly obtain the network element interface and process through URL engineering parameters and information element engineering parameters; for the interfaces for identifying URL engineering parameters and information element engineering parameters, if the network element is not found in the network element engineering parameter table, the new network element engineering parameters can be learned into the network element engineering parameter table through self-learning. In addition, network element engineering parameters, URL engineering parameters, and information element engineering parameters are also logically divided for ease of expression, and the description is also explained in a best-effort manner from the perspective of performance. In actual implementation, they can be combined as needed in combination with specific needs.
[0176] The network element engineering parameters, URL engineering parameters, and cell engineering parameters mentioned in this embodiment are not required to be configurable through the interface, and can also be implemented through scripts, internal codes, etc., as long as they logically contain key information.
[0177] The contents of the network element engineering parameters, URL engineering parameters, and cell engineering parameters in this embodiment can also support customization of specific offices. Mainly, after observing the signaling for a period of time, the 5G new call expert can extract the URL rules of the specific process of a specific office, and enrich the engineering parameter content by guiding the on-site configuration, thereby improving the accuracy of message recognition.
[0178] The data acquisition equipment is divided into modules such as data acquisition and data cleaning, which is only a logical explanation. The specific implementation can be separated or combined.
[0179] It will be appreciated by those skilled in the art that all or some of the steps, systems, and functional modules / units in the methods disclosed above may be implemented as software, firmware, hardware, and appropriate combinations thereof. In hardware implementations, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed by several physical components in cooperation. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-transitory medium) and a communication medium (or temporary medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. In addition, it is well known to those skilled in the art that communication media typically contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.
[0180] Example embodiments have been disclosed herein, and although specific terms are employed, they are used and should be interpreted only in a general illustrative sense and not for limiting purposes. In some instances, it will be apparent to those skilled in the art that, unless otherwise expressly noted, features, characteristics, and / or elements described in conjunction with a particular embodiment may be used alone or in combination with features, characteristics, and / or elements described in conjunction with other embodiments. Therefore, those skilled in the art will appreciate that various changes in form and detail may be made without departing from the scope of the present disclosure as set forth in the appended claims.
Claims
1. A signaling identification method, comprising: Acquire the engineering parameter information of the network element and establish a network element engineering parameter table, wherein the network element engineering parameter table includes an interface identifier of an interface of the network element and a process identifier of a service process in the interface; Obtain URL information and establish a URL work parameter table, wherein the URL information represents the unique characteristics of the business process; Acquire cell characteristic information and establish a cell parameter table, wherein the cell characteristic information represents a unique characteristic of a cell in the signaling; The signaling to be identified is matched with at least one of the network element work parameter table, the URL work parameter table, and the cell work parameter table to determine the interface and business process to which the signaling to be identified belongs.
2. The signaling identification method according to claim 1, wherein: Obtain the engineering parameter information of the network element and establish the network element engineering parameter table, including: Obtaining the engineering parameter information of the network elements on both sides of each of the interfaces; Allocating an interface identifier to each of the interfaces, wherein the interface identifiers of the interfaces are different from each other; A process identifier is allocated to the business process in the interface, wherein the process identifiers of the business processes in the same interface are different from each other.
3. The signaling identification method according to claim 2, wherein: The process identifiers of the same business processes corresponding to different interfaces are the same.
4. The signaling identification method according to claim 1, wherein: Get URL information and create a URL parameter table, including: Acquire the URL information according to the interface specification of the network element; Determine the request method information corresponding to the business process; The URL information and the request method information are added to the URL work parameter table accordingly to obtain the URL work parameter table.
5. The signaling identification method according to claim 4, wherein: Obtain URL information and establish URL parameter table, including: According to the interface specification of the network element, the URL information is obtained during the processing of the association process, wherein the URL information is carried in the association process; The URL information is added to the URL work parameter table.
6. The signaling identification method according to claim 1, wherein: Obtain cell feature information and establish a cell parameter table, including: Decoding the signaling to obtain the cell characteristic information; The business process information, interface information, and the cell characteristic information are added to the cell work parameter table accordingly.
7. The signaling identification method according to any one of claims 1 to 6, wherein: Matching the signaling to be identified with at least one of the network element work parameter table, the URL work parameter table, and the cell work parameter table to determine the interface and service flow to which the signaling to be identified belongs, including: Matching the signaling to be identified with the network element engineering parameter table to identify the interface to which the signaling to be identified belongs; The signaling to be identified is matched with at least one of the URL work parameter table and the cell work parameter table to determine the business process to which the signaling to be identified belongs.
8. The signaling identification method according to claim 7, wherein: Matching the signaling to be identified with at least one of the URL work parameter table and the cell work parameter table to determine the service process to which the signaling to be identified belongs includes: In the case that the interface to which the signaling to be identified belongs is identified successfully, matching the signaling to be identified with the URL work parameter table or the cell work parameter table to determine the service process to which the signaling to be identified belongs; In the event that identification of the interface to which the signaling to be identified belongs fails, the signaling to be identified is matched with the URL industrial parameter table to determine the interface and business process to which the signaling to be identified belongs; or the signaling to be identified is matched with the URL industrial parameter table to determine the business process to which the signaling to be identified belongs, and the information to be identified is matched with the URL industrial parameter table and the cell industrial parameter table to determine the interface to which the signaling to be identified belongs.
9. The signaling identification method according to any one of claims 1 to 6, wherein: Matching the signaling to be identified with at least one of the network element work parameter table, the URL work parameter table, and the cell work parameter table to determine the interface and service flow to which the signaling to be identified belongs, including: The signaling to be identified is matched with at least one of the URL work parameter table and the cell work parameter table to determine the interface and business process to which the signaling to be identified belongs.
10. The signaling identification method according to any one of claims 1 to 6, wherein: After matching the signaling to be identified with at least one of the network element work parameter table, the URL work parameter table, and the cell work parameter table, and determining the interface and service flow to which the signaling to be identified belongs, the signaling identification method further includes: Extracting characteristic information of the signaling to be identified; The characteristic information of the signaling to be identified is subjected to association processing according to an association algorithm.
11. The signaling identification method according to any one of claims 1 to 6, wherein: The signaling identification method further includes: According to the signaling information of the office point, at least one of the network element engineering parameter table, the URL engineering parameter table, and the cell engineering parameter table is configured.
12. The signaling identification method according to any one of claims 1 to 6, wherein: The signaling identification method further includes: According to the modification instruction, at least one of the network element engineering parameter table, the URL engineering parameter table, and the cell engineering parameter table is modified.
13. An electronic device comprising: one or more processors; A memory having one or more programs stored thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the cell identification method according to any one of claims 1 to 12.
14. A computer-readable medium having a computer program stored thereon, wherein when the program is executed by a processor, the method for identifying an information element according to any one of claims 1 to 12 is implemented.