Signaling identification method, electronic device and computer readable medium

Abstract

The present disclosure provides a signaling identification method, comprising: acquiring work parameter information of a network element, and establishing a network element work parameter table, wherein the network element work parameter table comprises an interface identifier of an interface of the network element and a process identifier of a service process in the interface (S1); acquiring uniform resource locator (URL) information, and establishing a URL work parameter table, wherein the URL information represents a unique feature of the service process (S2); acquiring cell feature information, and establishing a cell work parameter table, wherein the cell feature information represents a unique feature of a cell in signaling (S3); and matching 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, so as to determine the interface and the service process to which the signaling to be identified belongs (S4). The present disclosure further provides an electronic device and a computer readable medium.

Description

Signaling identification method, electronic device, and computer-readable medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to Chinese patent application 202311255016.2 filed with the State Intellectual Property Office of China on September 25, 2023, and the disclosure of this Chinese patent application is incorporated herein by reference in its entirety. Technical Field

[0003] 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

[0004] 5G New Calling is a 5G network-based ultra-HD voice and video calling service, along with related value-added services. These services include 5G VoNR ultra-HD video calling, 5G video customer service, intelligent translation, screen sharing, remote collaboration, augmented reality (AR), and fun calling. These services provide users with a visual, multimedia, and highly perceptual ultra-HD calling experience. Compared to the existing IP Multimedia Subsystem (IMS), the 5G New Calling system, as shown in Figure 1, adds network logical entities such as the VoNR+ capability network element, the VoNR+ media plane, the service access layer (AS), the media capability platform, and the New Calling Operations and Management Platform.

[0005] Unlike the IMS system, where the application layer protocol between network elements is primarily Session Initiation Protocol (SIP) signaling, the control plane messaging between different network elements introduced in 5G new calls follows HTTP / 2, the primary 5G communication application protocol defined by 3GPP. Messages between network elements are routed and distributed based on the Uniform Resource Locator (URL) of the resource.

[0006] Summary of the Invention

[0007] Embodiments of the present disclosure provide a signaling identification method, an electronic device, and a computer-readable medium.

[0008] In a first aspect, an embodiment of the present disclosure provides a signaling identification method, comprising: obtaining the working parameter information of a network element, and establishing a network element working parameter table, wherein the network element working 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, and establishing a URL working parameter table, wherein the URL information represents a unique feature of a business process; obtaining cell feature information, and establishing a cell working parameter table, wherein the cell feature information represents a unique feature of a cell in the signaling; matching the signaling to be identified with at least one of the network element working parameter table, the URL working parameter table, and the cell working parameter table to determine the interface and business process to which the signaling to be identified belongs.

[0009] 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.

[0010] In a third aspect, an embodiment of the present disclosure provides a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the method for identifying information elements described in the first aspect of the embodiment of the present disclosure.

[0011] In the disclosed embodiment, based on the establishment of the network element engineering parameter table, URL engineering parameter table, and signal element engineering parameter table, the network element engineering parameter table, URL engineering parameter table, and 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

[0012] FIG1 is a schematic diagram of a new call network architecture;

[0013] FIG2 is a flow chart of a signaling identification method according to an embodiment of the present disclosure;

[0014] FIG3 is a flow chart of a signaling identification method according to another embodiment of the present disclosure;

[0015] FIG4 is a flowchart of a signaling identification method according to another embodiment of the present disclosure;

[0016] FIG5 is a flowchart of a signaling identification method according to another embodiment of the present disclosure;

[0017] FIG6 is a schematic diagram of the composition of an electronic device according to an embodiment of the present disclosure;

[0018] FIG7 is a schematic diagram of the composition of a computer-readable medium according to an embodiment of the present disclosure;

[0019] FIG8 is a schematic diagram of a signaling identification system according to an embodiment of the present disclosure;

[0020] FIG9 is a schematic diagram of a processing flow of signaling identification according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0021] In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the signaling identification method, electronic device, and computer-readable medium provided by the present disclosure are described in detail below with reference to the accompanying drawings.

[0022] Example embodiments will be described more fully hereinafter 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. Rather, these embodiments are provided so that this disclosure will be thorough and complete and will fully convey the scope of this disclosure to those skilled in the art.

[0023] In the absence of conflict, the various embodiments of the present disclosure and the various features therein may be combined with each other.

[0024] As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0025] The terms used herein are used only 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.

[0026] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one 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 expressly defined as such herein.

[0027] Unlike the 3GPP-defined URLs for each interface and process, which have characteristic information, 5G New Call URLs are mostly defined by device manufacturers. Furthermore, due to security and other considerations, one of the functions assigned to VoNR+-capable network elements during the 5G New Call system's design is to serve as a bridge for internal and external communications within the IMS network. This results in a large number of control messages for the service ASes that embody 5G New Call characteristics being forwarded to the VoLTE and VoNR+ media planes via the VoNR+-capable network elements. The vast majority of these forwarded messages are also based on resource URLs. Because they are forwarded messages, the forwarded messages are virtually indistinguishable from the messages being forwarded.

[0028] 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 is to accurately identify the interface and business process to which each signaling on the network belongs. Without modifying the 3GPP-based 5G control plane message collection solution, the 5G new call can only identify less than 10% of the processes.

[0029] The embodiment of the present disclosure provides a signaling identification method. FIG2 is a flow chart of the signaling identification method according to the embodiment of the present disclosure. As shown in FIG2 , the signaling identification method includes steps S1 to S4.

[0030] In step S1, the working parameter information of the network element is obtained, and a network element working parameter table is established, wherein the network element working parameter table includes the interface identifier of the interface of the network element and the process identifier of the service process in the interface.

[0031] In step S2, URL information is obtained and a URL work parameter table is established, wherein the URL information represents the unique characteristics of the business process.

[0032] In step S3, cell characteristic information is obtained and a cell parameter table is established, wherein the cell characteristic information represents a unique characteristic of a cell in the signaling.

[0033] In step S4, the signaling to be identified is matched with at least one of the network element working parameter table, the URL working parameter table, and the cell working parameter table to determine the interface and service flow to which the signaling to be identified belongs.

[0034] In some embodiments, the network element is a network element in a 5G new call system.

[0035] In the embodiment of the present disclosure, a network element working parameter table is established, and the interface identifier of the interface and the process identifier of the business process are configured in the network element working parameter table, so that the interface and business process to which the signaling belongs can be identified based on the network element working parameter table.

[0036] In the embodiment of the present disclosure, a URL work parameter table is established. 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.

[0037] In the embodiment of the present disclosure, a cell 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 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 parameter table.

[0038] Based on the establishment of 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 achieving accurate identification of the signaling interface and business process 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.

[0039] The embodiments of the present disclosure do not impose any special limitation on how to establish the network element working parameter table.

[0040] In some embodiments, the working parameter information of the network element is obtained, and a network element working parameter table is established, including: obtaining the working parameter information of the network elements on both sides of each interface; assigning an interface identifier to each interface, wherein the interface identifiers of each interface are different; assigning a process identifier to the business process in the interface, wherein the process identifiers of each business process in the same interface are different.

[0041] In some embodiments, the process identifiers of the same business process in different interfaces are the same.

[0042] In the disclosed embodiments, as long as the process identifiers of each business process within the same interface are unique, the process identifiers of the same business process within different interfaces can be the same, which helps improve the accuracy of interface and business process identification. For example, if the process identifiers of the same business process within 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.

[0043] The embodiment of the present disclosure does not impose any special limitation on how to establish the URL work parameter table.

[0044] In some embodiments, URL information is obtained and a URL work parameter table is established, including: obtaining URL information according to the interface specification of the network element; determining the request method information corresponding to the business process; adding the URL information and the request method information to the URL work parameter table to obtain the URL work parameter table.

[0045] In some embodiments, self-learning of URL parameter tables is supported.

[0046] Accordingly, in some embodiments, obtaining URL information and establishing a URL work parameter table also includes: obtaining URL information during the processing of the association process according to the interface specification of the network element, wherein the association process carries URL information; and adding the URL information to the URL work parameter table.

[0047] The embodiment of the present disclosure does not impose any special limitation on how to establish the cell engineering parameter table.

[0048] In some embodiments, obtaining cell characteristic information and establishing a cell working parameter table include: decoding signaling to obtain cell characteristic information; and adding service process information, interface information, and cell characteristic information to the cell working parameter table.

[0049] In the embodiment of the present disclosure, the network element working parameter table, the URL working parameter table, and the signaling element working parameter table can be arbitrarily combined to identify the interface and service flow to which the signaling to be identified belongs.

[0050] In some embodiments, the signaling to be identified is matched with at least one of the network element working parameter table, the URL working parameter table, and the cell working parameter table to determine the interface and business process to which the signaling to be identified belongs, including: matching the signaling to be identified with the network element working parameter table to identify the interface to which the signaling to be identified belongs; matching the signaling to be identified with at least one of the URL working parameter table and the cell working parameter table to determine the business process to which the signaling to be identified belongs.

[0051] In some embodiments, the signaling to be identified is matched with at least one of the URL process parameter table and the cell process parameter table to determine the business process to which the signaling to be identified belongs, including: when the interface to which the signaling to be identified belongs is successfully identified through the network element process parameter table, the signaling to be identified is matched with the URL process parameter table or the cell process parameter table to determine the business process to which the signaling to be identified belongs; when the interface to which the signaling to be identified belongs fails to be identified through the network element process parameter table, the signaling to be identified is matched with the URL process 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 process 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 process parameter table and the cell process parameter table to determine the interface to which the signaling to be identified belongs.

[0052] In some embodiments, the signaling to be identified is matched with at least one of the network element working parameter table, the URL working parameter table, and the cell working parameter table to determine the interface and business process to which the signaling to be identified belongs, including: matching the signaling to be identified with at least one of the URL working parameter table and the cell working parameter table to determine the interface and business process to which the signaling to be identified belongs.

[0053] FIG3 is a flowchart of a signaling identification method according to another embodiment of the present disclosure.

[0054] 3 , after step S4 , the signaling identification method further includes steps S51 and S52 . Steps S1 to S4 shown in FIG3 are the same as steps S1 to S4 described with reference to FIG2 , and are not described again here.

[0055] In step S51, characteristic information of the signaling to be identified is extracted.

[0056] In step S52, association processing is performed on the characteristic information of the signaling to be identified according to an association algorithm.

[0057] FIG4 is a flowchart of a signaling identification method according to another embodiment of the present disclosure.

[0058] In some embodiments, referring to Figure 4 , the signaling identification method further includes step S6 . Steps S1 to S4 shown in Figure 4 are the same as steps S1 to S4 described with reference to Figure 2 , and are not described again herein.

[0059] In step S6, at least one of the network element engineering parameter table, the URL engineering parameter table, and the cell engineering parameter table is configured according to the signaling information of the office site.

[0060] In the embodiment of the present disclosure, the engineering parameter table is configured according to the signaling information of the office point, thereby achieving customization of specific office points supporting the network element engineering parameter table, URL engineering parameter table, and cell engineering parameter table.

[0061] FIG5 is a flowchart of a signaling identification method according to another embodiment of the present disclosure.

[0062] In some embodiments, referring to Figure 5 , the signaling identification method further includes step S7. Steps S1 to S4 shown in Figure 5 are the same as steps S1 to S4 described with reference to Figure 2 and are not described again herein.

[0063] In step S7, at least one of the network element engineering parameter table, the URL engineering parameter table, and the cell engineering parameter table is modified according to the modification instruction.

[0064] 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.

[0065] FIG6 is a schematic diagram showing the composition of an electronic device according to an embodiment of the present disclosure.

[0066] 6 , an embodiment of the present disclosure provides an electronic device, comprising: one or more processors 101; a memory 102 on which one or more programs are stored, and 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; and one or more I / O interfaces 103, connected between the processor and the memory, and configured to implement information interaction between the processor and the memory.

[0067] The processor 101 is a device with data processing capabilities, including but not limited to a central processing unit (CPU); 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), and 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 exchange between the processor 101 and the memory 102, including but not limited to a data bus (Bus).

[0068] 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.

[0069] FIG. 7 is a schematic diagram illustrating the composition of a computer-readable medium according to an embodiment of the present disclosure.

[0070] 7 , an embodiment of the present disclosure provides a computer-readable medium having a computer program stored thereon. 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.

[0071] 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 examples.

[0072] Example 1

[0073] Figure 1 shows the 5G new call network architecture. The service AS (short for intelligent network and new call application server), new call operation and management platform, VoNR+ capability network element, VoNR+ media plane, and media capability platform in Figure 1 are all new network elements added to the existing IMS network. The IMS network usually includes SBC (including control plane and user plane: SBC-C, SBC-U), P / I / S-CSCF, VoLTE AS, PCF / PCFRF, HSS / UDM, ENUM / DNS, and other network elements.

[0074] Control plane signaling between newly added network elements in 5G New Calls is almost entirely based on HTTP2. Table 1 lists the interface descriptions for 5G New Calls. Specifically, as shown in Table 1, interfaces 3, 4, 5, 7, 8, 9, 10, 11, 14, 16, and 17 are all based on HTTP2. Interface 3 is the communication entry point between 5G New Calls and the IMS control plane. After receiving subscription and control messages from VoNR+-capable network elements, the VoLTE AS reports notification messages and control result messages to the VoNR+-capable network elements. Due to the new features of 5G New Calls, the VoLTE AS forwards media resource application, modification, and release instructions to the VoNR+ media plane. Interface 9 is the interface between the service AS and VoNR+-capable network elements, and the key control plane signaling for 5G New Calls primarily originates from interface 9. After receiving messages from interface 9, the VoNR+ capability network element forwards call control messages to the VoLTE AS via interface 3 and service control messages to the VoNR+ media plane via interface 5. Interface 7 primarily handles resource negotiation, media data forwarding, and result processing between the VoNR+ media plane and the media capability platform. Interface 8 is where the service AS triggers specific new call applications.

[0075] Table 1

[0076] Table 2 shows the interface parameters for new 5G calls. Interface parameters are essentially another form of link parameter sets. The external data representation (XDR) output from the Internet log collection system uses interface fields to express the connection between two specific network elements. Table 2 provides configuration instructions for some interfaces in new 5G calls. The interface parameter table primarily specifies interface identifiers (i.e., interface IDs), which generally need to be consistent with the collection specification. New methods can also be used internally for differentiation, but when the XDR is ultimately output, it must be converted to a definition consistent with the collection specification.

[0077] Table 2

[0078] See Table 3 for the network element engineering parameter table for new 5G calls. The collection of Internet access logs must be accurate to the network element, interface, and process triggered by the message; the collection scope is limited by the network element engineering parameter information. The network element engineering parameter information mainly configures the specific network element name, IP address type, IP address, and other link-related information. During the initial deployment, the network element link information of the existing network is generally obtained in advance before the deployment. The network element engineering parameter information can be extracted from it, or the network element link information can be reused. After a period of operation, if the main device network element is added or changed, the configuration can be added after passively receiving the information, or it can be supplemented by the self-learning method in this example.

[0079] Table 3

[0080] See Table 4 for the request URL parameter table for the 5G new call request message. Some of the configuration information in the URL parameter table is derived from the explicit definitions in the master device interface specification, while others are derived through self-learning based on the understanding of the master device interface specification. The URL parameter table contains the request method, request URL characteristics, target interface, and target process for the matching target message. For example, numbers 1, 2, and 3 in Table 4 represent the call event subscription, call event subscription update, and call event subscription cancellation processes in interface 3, respectively. These three processes share 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 the URL + request method. Similar processes with unique request URL characteristics include numbers 4, 5, and 6 in Table 4. The request URLs for the subscribing processes related to multi-party conferencing in interface 9, as well as for processes in interfaces 7, 8, and 11, as specified in the master device interface specification, are also unique.

[0081] Table 4

[0082] The URL parameter table also includes some information derived from program self-learning. This self-learning is also based on understanding the definitions in the specification. When processing associated processes, parameters conveying meanings similar to callbackUrl are learned along with the request method of the associated process. For example, in sequence number 10 in Table 4, when a VoNR+-capable network element sends a call event control message to the VoLTE AS, the request message includes the URL for receiving subsequent call control result notifications, namely {callbackUrl}. For example, Table 5 defines the call event control interface in the specification, and Table 6 defines the call control result notification interface in the specification. The request parameter callbackUrl in Table 5 corresponds to the request URL in Table 6. In 5G new call scenarios, this method of specifying the callbackUrl used in subsequent messages accounts for the majority of process definitions. For example, interfaces 3, 5, 8, and 9 all have processes using callbackUrl as the request URL. Because the definitions in the interface specifications are largely similar, Table 4 only selects a few records. callbackUrl is just a representation. {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. For the sake of convenience, callbackUrl is used to represent them.

[0083] Table 5

[0084] Table 6

[0085] The request message uses the request line to match the URL parameter table. This can be achieved by quickly decoding and extracting the first line of signaling information. This method is simple to implement and has the highest performance.

[0086] The cell working parameter table of the cells in the network element of the 5G new call is shown in Table 7. The received HTTP2 code stream needs to be deeply decoded to obtain the cell working parameters (i.e., cell feature information). The cell working parameter table can be used to solve the problem when the URL working parameter table cannot be used to identify the interface to which the message belongs. For example, the sequence number 7 in Table 4 is registered as "101: Media stream copy application process", and the URL may be interface 5 or interface 9. If the network element working parameter table is not used, it can be found from Tables 8 and 9 (the media stream copy application interface definitions of interface 9 and interface 5, respectively) that both interfaces carry mandatory request parameters. For example, in Table 8, the media stream copy application of interface 9 carries the appId parameter. Then, after the URL working parameter (i.e., URL information) is matched, the cell working parameter table can be further used for identification. The use of cell engineering parameters is basically equivalent to a full decoding of the entire signaling. If performance is not considered, the use of cell engineering 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 receiving process for interface 5 and interface 9 has no signaling difference. At this time, if combined with network element engineering parameters, segmentation can be achieved.

[0087] Table 7

[0088] Table 8

[0089] Table 9

[0090] FIG8 is a schematic diagram of a signaling identification system according to an embodiment of the present disclosure.

[0091] As shown in Figure 8, the signaling recognition system's logical modules typically include data acquisition, data cleaning, data association and synthesis, and data distribution. Data acquisition primarily involves layered analysis of data after receiving network signaling, and then distribution based on interfaces, services, and processes. The data cleaning module parses data and extracts keywords according to acquisition specifications, then outputs the extracted information as XDR according to standard acquisition specifications.

[0092] FIG9 is a schematic diagram of a processing flow of signaling identification according to an embodiment of the present disclosure.

[0093] As shown in Figure 9, a hierarchical approach is used to gradually perform message recognition and self-learning of working parameters, primarily for performance reasons. Specific details are described in Examples 2 to 4.

[0094] Example 2

[0095] In this example, as shown in Figure 8, the signaling identification system includes a data acquisition module, a data cleaning module, a data association and synthesis module, and a data distribution module. Data association and synthesis primarily uses various association algorithms to correlate information such as phone numbers and locations in the XDR. These algorithms vary between systems. The data distribution module sends the processed XDR to a third-party server, such as an online log query system or a financial subsystem. While data cleaning and data association and synthesis are logically independent, they can be integrated in practice. For clarity, data cleaning and data association and synthesis are described separately.

[0096] Data collection module: Uses replication technologies such as optical splitting to copy the signaling of each network element between the main devices and then routes it to a designated access module, such as a convergence splitter. After receiving the signaling, the data collection module performs signaling layer identification, and finally identifies the application layer protocol, and then implements separate processing of different signaling based on the specific application protocol type. 5G new calls are an extended application of IMS, so the control plane signaling will also involve protocols currently used by the IMS network, such as SIP and Diameter. The data collection module remains unchanged for processing these messages. The communication between the newly added functional entities in 5G new calls is mainly based on the HTTP2 protocol processing, so the data collection module needs to add HTTP2 recognition when identifying the application layer protocol. After the data collection module recognizes that it is an HTTP2 message, it will send the message to the HTTP2 submodule for processing.

[0097] The HTTP2 submodule identifies and processes interfaces and processes. Due to the unique characteristics of 5G new calls, interface and process identification requires a combination of methods to improve message recognition accuracy. Specifically, these methods are divided into two major categories and multiple subcategories. These two major categories are primarily based on whether the signaling source and destination addresses are in the network element's engineering parameter table.

[0098] Example 3

[0099] This example is based on the signaling identification system provided in Example 2. Signaling identification includes the following process.

[0100] Step 1: Obtain the network element engineering parameter table from the operator for each network element on both sides of each interface in the existing 5G new call system. This table includes engineering parameter information for each network element, such as IMS network elements, VoNR+ capability network elements, VoNR+ media plane, service AS, media capability platform, new call operation and management platform, and VoLTE AS. This information includes the IP address of each network element. This information primarily includes link-related information such as the network element name, network element IP address, and IP type, as shown in Table 3.

[0101] Step 2: Assign a unique ID to each interface, such as 166 for interface 3 and 167 for interface 4, and 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 logical designs. In actual software implementation, these can be expressed through equivalent information such as link and office directions on the network management interface, or through scripts and code.

[0102] Step 3: Assign a unique ID to each specific service flow on the interface. For example, the service flow on interface 3 between the VoNR+ capable network element and the VoLTE AS can be assigned a process ID as follows:

[0103] 0: Session detection

[0104] 1: Call event subscription

[0105] 2: Call event subscription update

[0106] 3: Call event subscription cancellation

[0107] 4: Call event notification

[0108] 5: Call event control

[0109] 6: Call control result notification

[0110] 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 new 5G calls, because there is a large amount of message forwarding, the process ID of the same type of message can be defined as the same ID. For example, if interface 9 includes processes 1-6 of interface 3, 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 acquisition system, or they can follow the definition according to the acquisition specification. The specific implementation is not limited, as long as the uniqueness within the interface is guaranteed; the final ID can be converted according to the specification requirements.

[0111] Step 4: Create a URL work parameter table. This table should include the request method, request URL, destination interface, and destination process information, as shown in Table 4. First, by studying the main device interface specifications, collect all HTTP2-based process interface, process, request method, and request URL information. Based on this information, enter the URL information that uniquely identifies the process through the request URL as specified in the specification into the URL work parameter table, which serves as the baseline data for the URL work parameter table. For example, in several processes related to call subscriptions on interface 3, the request URL contains the characteristic string "subscriptions / call-events / notifications / number / ". When the protocol machine receives an HTTP2 request message, if the request URL contains this characteristic string, it can determine that the message belongs to interface 3. Furthermore, based on the request method, if the request method is POST, the message belongs to interface 3's call event subscription message; if the request method is DELETE, the message belongs to interface 3's call event subscription cancellation message. Similarly, processes such as GSCP query messages, location information acquisition, and short message sending on interface 9 can all be identified by simply matching the characteristic strings in the request method and request URL. The request URL configured in the URL parameter table can be the unique information in the process request URL that is clearly stated in the interface specification. For example, in Table 4, No. 4 records the definition of the intelligent translation control process request URL for interface 8: "{callbackURL} / translationcontrol." Because "translationcontrol" is a typical business feature, "translationcontrol" can also be used directly instead of the full URL. To improve accuracy, the receiver parameter obtained from the media copy process response of interface 9 and " / translationcontrol" can also be concatenated and learned in the URL parameter table.

[0112] Step 5: The data in the URL parameter table can come not only from standardized process information but also from self-learned information. Furthermore, the request URLs for most processes in new 5G calls are derived from other related processes, so self-learning is crucial. The process of self-learning interfaces and processes involves studying the interface specifications of the master device, obtaining the correlation algorithm, and then implementing it through software. For example, see numbers 10-15 in Table 4. Number 10 is learned within the interface. When the call control message sent from the VoNR+-capable network element to the Volte AS on interface 3 carries the information element callbackUrl: the call control result notification URL (see Table 5). Table 6 shows that, according to the definition of the call control result notification request URL, the request URL in this message contains only {callbackUrl}, from which the information "{callbackUrl}, the notification address, is obtained from the {callbackUrl} parameter in the call control instruction. The format of {callbackUrl} is customized by the platform manufacturer." Based on the interface definition of the master device, the data cleaning module needs to learn this {callbackUrl} along with the request method of the process call control result notification message when processing call control messages. This is combined with the interface and process parameter table to facilitate subsequent interface and process identification. Similar related processes exist on almost every interface. For example, the playback request on interfaces 5 and 9 carries the request URL for playback result notification. The response to the media element synthesis application process carries the request URL for stopping media element synthesis. The request message for the number collection request carries the request URL for number collection result notification. The response message for the number collection request carries the request URL for stopping number collection. Interfaces 4, 7, 8, and 11 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 (Intelligent Translation Control Interface Definition of Interface 8), in the intelligent translation control interface process of Interface 8, the request parameter carries notifyURL. In Table 11 (Intelligent Translation Result Notification Interface Definition of Interface 7), the request URL for the intelligent translation result notification of Interface 7 directly uses {notifyURL} / send. Therefore, when processing the 201 process of Interface 8: Intelligent Translation Control Process, {notifyURL} and " / send" need to be concatenated 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 learned. For example, in the push media duplication process: VoNR+ media pushes a duplication code stream application to the media capability platform. The request URL is defined as the receiving end URL address obtained from the interface 5 media duplication request according to the interface definition {duplicationCallbackUrl}. From Table 9, we can see that the definition of the request parameter url in the "101: Media stream duplication / forwarding application" process of interface 5 is "the URL of the media duplication receiving end. The media side pushes the control plane information of the media stream duplication through this URL." Therefore, when processing the "101: Media stream duplication / forwarding 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 in cross-interface learning and they are not described in full.

[0113] Table 10

[0114] Table 11

[0115] Step 6: Create a cell parameter table, as shown in Table 7. Cell parameters configure a unique cell within a signaling message. When similar processes require segmentation, cell feature information can improve data flow identification. Cell parameters involve full decoding and should be used last, considering performance resources. Their configuration should be kept as simple as possible. If performance consumption is not a concern, cell parameters can also serve the same purpose as URL parameters. Cell parameters can be used to match interfaces and processes. However, because some messages in 5G new calls are forwarded, cell parameters cannot solve all problems. Cell parameters need to be used in conjunction with network element parameters and URL parameters. For example, in the process 101: Media Stream Copy Request, which exists on both interfaces 5 and 9, the subtle difference between the two signaling messages is that interface 9 carries the cell appId (as shown in Table 8). If the request URL is the same and the interface is undefined, deep parsing can determine if the appId is present, indicating the process is for interface 9; otherwise, it indicates the process is for interface 5. This discrepancy can be recorded in the cell parameter table shown in Table 7. Furthermore, if the dependent request URL doesn't have an associated process, but the message matches the parameters of interface 7, the cell parameter can be used to best identify the interface and process. For example, if the associated URL for interface 7's "221: Push Media Copy / Forward Information" is not learned, the inclusion of the MediaType and SDP cells in the cell can be used to determine that the message belongs to the "221: Push Media Copy / Forward Information" process of interface 7. The cell parameter table should be concise, ensuring the most accurate process identification possible in the event that the network element parameter table or URL parameter table fails.

[0116] Step 7: The data collection module uses the network element work parameter table, URL work parameter table, and cell work parameter table in pairs or in combination to identify the interface and process to which the HTTP2 signaling belongs.

[0117] Method 1: NE Engineering Parameters Table + URL Engineering Parameters Table: Use the NE Engineering Parameters Table to match the source and destination addresses. If a match is successful, the interface can be determined. After the interface is determined, the process information can be obtained through the URL Engineering Parameters Table.

[0118] Method 2: Identification process of network element engineering parameter table + cell engineering parameter table: In method 1, the interface can be determined by successfully matching the network element engineering parameter table, and the process can be further determined through the cell engineering parameter table.

[0119] Method 3: Combined use of the URL engineering parameter table and the cell engineering parameter table: When the NE engineering parameter table fails to match, the URL engineering parameter table can be used to identify the process if the match is successful. If the interface is unique, the interface can also determine the interface and process. If the interface obtained from the URL engineering parameter table is not unique, the cell engineering parameter table must be used to obtain the interface.

[0120] Method 4: Directly use the URL parameter table or the cell parameter table for matching to obtain the interface and process.

[0121] Method 5: Using the URL engineering parameter table first and then the NE engineering parameter table is also acceptable. In short, the use of the NE engineering parameter table, URL engineering parameter table, or cell engineering parameter table is arbitrary. For performance reasons, the order of advancement is to first use the NE engineering parameter table to determine the interface, then use the URL engineering parameter table and then the cell engineering parameter table to determine the process.

[0122] Step 8: If the interface is learned through URL engineering parameters or cell engineering parameters, such as methods 3 and 4 in step 7, the source and destination addresses of the stream need to be learned from the network element engineering parameters. Self-learned network element engineering parameters can enrich the engineering parameter information omitted in manual configuration and accelerate the interface and process identification of subsequent messages.

[0123] Step 9: After identifying the specific interface and process, the data cleaning module learns the {callbackUrl} (a general term for the URL used to express subsequent messages in all interface definitions) required for the request URL of the subsequent process according to the master device specification. This information is combined with the request method, specific interface, and process information, and then stored in the URL work parameter table. This self-learned {callbackUrl} is part of the data source for the URL work parameter table and can accelerate the identification of interfaces and processes for subsequent messages.

[0124] Step 10: Specifically, the initial service operation request URLs in service control messages for new 5G calls are all based on resource streams. Therefore, the request URLs all contain {stream_url}. The request URLs for these service processes also contain service-specific information, such as numbers 7-9 in Table 4. This allows the URL to omit {stream_url}, but this only identifies the specific process for interface 9 or interface 5. If the network element engineering parameters are known, the specific interface and process can be determined. If the network element engineering parameters are unknown, further differentiation is required using the signal element engineering parameters. In addition to the special relationship between interface 9 and interface 5, the request URLs for some interfaces also contain characteristic information. It is also possible to remove the dynamically generated portion and directly store the characteristic information. For example, number 4 in Table 4, for intelligent translation control of interface 8, although the request URL is defined as {callbackURL} / translationcontrol, standardized learning shows that the characteristic characters "translationcontrol" can also be used to identify the interface and process. This step primarily demonstrates that request URLs can be simplified to improve efficiency. If performance impact is not a concern, using the full URL is also acceptable.

[0125] 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 working parameters are not learned.

[0126] 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.

[0127] Example 4

[0128] In this example, the source address and destination address of the signaling to be analyzed are in the network element engineering parameter table. In this case, as shown in FIG9 , the signaling identification process includes the following steps 1001 to 1008 .

[0129] In step 1001, the HTTP2 submodule of the data processing module receives original signaling.

[0130] In step 1002, the source address and destination address of the message are matched with the network element working parameter table (as shown in Table 3) in the most efficient way.

[0131] In step 1003, if both the source address and the destination address match successfully, the interface to which the message belongs can be accurately identified.

[0132] In step 1004, after further interface identification, the request URL characteristics of the interface signaling are then matched against the URL engineering parameter table. Specifically, after the network element engineering parameters are determined, the cell engineering parameter table can also be used in step 1004. The two methods are not prioritized and can be used separately or in combination. Because URLs can be quickly decoded and have the lowest performance, the URL engineering parameter table is preferred.

[0133] In step 1005, if the match is successful, the specific process can be accurately identified.

[0134] In step 1006, after the interface and process of this message are clear, 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.

[0135] In step 1007, the characteristic information in the signaling is extracted according to the requirements of the collection specification.

[0136] In step 1008, context information such as user number, location, service size and class is maintained.

[0137] The use of the URL work parameter table and the cell work parameter table in step 1004 is explained in detail as follows. Taking interface 3 as an example, 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 work 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, then the URL work parameter matching will fail. At this time, matching is performed through the cell work parameter. If the message carries the callEvent cell, the process can still be determined, that is, 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 be identified through the cell work parameter. Under the premise that the interface is known, the cell work parameter can also be used directly without considering the performance impact.

[0138] Example 5

[0139] In this example, the source and destination addresses of the signaling to be analyzed are not in the network element engineering parameter table. In this case, as shown in Figure 9, the signaling identification process includes the following steps 2001 to 2005 and steps 1006 to 1008, or the following steps 3001 to 3005 and steps 1006 to 1008. The processes 2001 and 3001 are two different sub-class methods, and both are equivalent to 1001. There is no particular order.

[0140] In step 2001, after receiving the original signaling, the HTTP2 submodule of the data processing module fails to match the network element parameters, or directly uses the URL parameter matching algorithm. In short, the interface is unknown.

[0141] In step 2002, the first line of the signaling is quickly decoded to obtain information, the request method and characteristic URL information are extracted, and matched with the URL parameter table.

[0142] In step 2003, the URL work parameter is matched successfully, the record corresponding to this process is retrieved, and the process and interface information are obtained.

[0143] In step 2004, after the process is confirmed, it is necessary to determine whether the interface is unique (e.g., sequence numbers 4, 5, and 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 16 in Table 4 are examples of non-unique request URL characteristics.

[0144] In step 2005, if the interface is unique, the network element information learned in this process can be compared with the network element engineering parameter library. If the network element information learned in this process does not exist in the engineering parameter library, the source address and destination address learned in this process can be learned into the network element engineering parameter table.

[0145] Then, step 1006 of learning the URL of the associated interface and process, step 1007 of extracting signaling features, and step 1008 of maintaining context information such as user number, location, service size, etc. are performed.

[0146] In step 3001, the cell parameters are used in the same way as the URL parameters. Interface and process information can also be directly obtained by matching the cell parameters. The cell content can include anything beyond the first line of the HTTP2 message (request line / response line), including the message header and message body. The message header, message body, and parameters within the message body are all cells.

[0147] In step 3002, a study of interface specifications reveals that different processes carry different headers. In other words, some specific processes carry specific header information. For example, the media stream copy process in Tables 8 and 9 carries the "Content-type" and "X-Type" headers. However, interface 9 may also include "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.

[0148] In step 3002, further: the existence or non-existence of the message body can also be used to determine the process under the interface. 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 combined with the request URL can be implemented in steps 2001 to 2003. If the request method is unknown (for example, the dynamic dictionary fails), 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, serial number 11 in Table 7, can also be identified by whether the message body exists or whether Content-type| exists.

[0149] In step 3002, for messages with a message body, the HTTP2 message can be fully decoded and then matched using the cell parameter table. Sequence number 8 in Table 7 records the USSD interface process information for interface 9. For all new 5G calls, only the USSD for interface 9 carries the three parameters "appId, address, and body." Similarly, the interface 9 settings screen (sequence number 9 in Table 7) also has a unique process-specific characteristic cell "videoTop." This unique cell parameter can successfully match the cell parameter.

[0150] In particular, because step 3002 involves full decoding and consumes significant performance, it is recommended that it be used after both network element parameter and URL parameter matching fail to identify the interface flow. For example, in case of sequence number 7 in Table 4, if network element parameter matching fails and URL parameter matching can only determine that the interface range is interface 9 or interface 5, full decoding can be followed by cell matching to identify the interface. For example, in case of sequence number 1 in Table 7, which records that the media stream copy request message for interface 9 must include the "appId" field, a successful match indicates that the signaling belongs to interface 9; a successful match indicates that the signaling belongs to interface 5.

[0151] In step 3003, after the match is successful, the interface and process information can be obtained from the cell process parameters.

[0152] In step 3004, the network element parameters, URL parameters, and cell parameters are used in no particular order. If the source address and destination address of the signaling are not in the network element parameter table, the new source address and destination address can be learned into the network element parameter table.

[0153] Example 6

[0154] In step 4001, unrecognized HTTP2 signaling is not discarded; instead, it is treated as unknown signaling and normalized. If the interface parameters match the interface information, then this information is filled in. Considering that out-of-order messages may arrive late due to signaling associated with the associated process, if resources permit, unknown signaling can be cached and, after a configurable cache period, the interface and process identification steps 1001 to 1003 can be repeated. The statistical results of unknown messages can also provide a reference for network optimization.

[0155] In step 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.

[0156] After receiving the signaling from the data acquisition module, the data cleaning module 120 extracts the corresponding feature information based on the results of the identified interface process. The collection of 5G new call signaling requires the data cleaning module to learn the URLs required for other related process identification and store them in the URL work parameter table (step 1006).

[0157] After the data cleaning module completes data extraction, it needs to generate XDR and output the data according to the collection specifications.

[0158] In principle, the identification of HTTP2 interfaces and processes involves the use of network element parameters, URL parameters, and message parameters without any order or dependency constraints. You can first use network element parameters to obtain the interface, then identify the process; you can also directly obtain the network element interface and process using URL parameters and message parameters. For interfaces identified with URL parameters and message parameters, if the network element is not in the network element parameter table, you can use self-learning to add the new network element parameters to the table. Furthermore, network element parameters, URL parameters, and message parameters are logically divided for ease of presentation, and the description is presented in a best-effort manner based on performance. In actual implementation, they can be combined as needed based on specific requirements.

[0159] 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.

[0160] The network element engineering parameters, URL engineering parameters, and signal element engineering parameters in this embodiment can also be customized for specific locations. By observing signaling over a period of time, 5G New Call Expert can extract URL patterns for specific processes at specific locations. By providing on-site configuration guidance, the engineering parameter content can be enriched, improving message recognition accuracy.

[0161] 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.

[0162] 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 is well 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 includes, but is 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 tape, 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 embodies 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.

[0163] 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 purposes of limitation. In some instances, it will be apparent to those skilled in the art that, unless otherwise expressly indicated, 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, it will be understood by those skilled in the art 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; Obtaining URL information and establishing 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; and 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 network element's engineering parameter information and create a network element engineering parameter table, including: Obtain the engineering parameter information of the network elements on both sides of each interface; Assigning an interface identifier to each interface, wherein the interface identifiers of each interface are different from each other; and A process identifier is allocated to the business process in the interface, wherein the process identifiers of various business processes in the same interface are different from each other.

3. The signaling identification method according to claim 2, wherein: The process identifier of the same business process in different interfaces is 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; and The URL information and the request method information are added to the URL tool accordingly. In the reference table, the URL working reference table is obtained.

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; and 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; and 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; and 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: When the interface to which the signaling to be identified belongs is successfully identified by the network element work parameter table, 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; and When the interface to which the signaling to be identified belongs fails to be identified by the network element engineering parameter table, In case of failure, 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; and 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: At least one of the network element engineering parameter table, the URL engineering parameter table, and the cell engineering parameter table is configured according to the signaling information of the office point.

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; as well as 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.

Images