Data acquisition processing method and device, electronic equipment and readable storage medium

Abstract

The invention discloses a data acquisition processing method and device, electronic equipment and a readable storage medium, and belongs to the field of communication. The IMS DC data transmitted by the target transmission segment in the current service interaction process is collected, the target service layer key information identified based on the IMS DC data is obtained, and then the target XDR information corresponding to the current service interaction process is generated according to the target service layer key information. According to the method and the device, the IMS DC data service can be effectively monitored in an IMS DC encryption scene.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to a data acquisition and processing method, device, electronic device, and readable storage medium. Background Art

[0002] With the rapid development of the 5G industry, China Mobile and other operators have gradually launched some 5G feature applications, such as 5G New Calls. 5G New Calls are ultra-clear voice calls, video call services and related value-added services based on 5G networks, including 5G VoNR (Voice over NR, 5G voice solution) ultra-clear video calls, 5G video customer service, intelligent translation functions, screen sharing, remote collaboration and AR fun calls, etc., which can provide users with visual, multimedia and highly perceived ultra-clear call experience.

[0003] refer to Figure 1 One way to implement new 5G calls is to add an IMS (IP Multimedia Subsystem) DC (Data Channel) in addition to the traditional voice call audio and video stream channels, and transmit pictures, audio, video, menus, emoticons, locations, AR (Augmented Reality) / VR (Virtual Reality) and other media between the terminal and the network to implement various services. In order to improve user experience perception, it is necessary to introduce a signaling monitoring system to monitor the key indicators of IMS DC data service operation in real time, eliminate network risks in advance, and quickly demarcate and locate sudden failures.

[0004] A direct way to monitor IMS DC data services is to collect IMS DC data packets transmitted between the terminal and the network for deep packet identification. However, for security reasons, operators will encrypt IMS DC data packets transmitted between the terminal and the network. In this scenario, the signaling monitoring system cannot decrypt the encrypted IMS DC data packets, resulting in the inability to monitor IMS DC services. Therefore, how to monitor IMS DC data services in the IMS DC encryption scenario is an urgent problem to be solved. Summary of the invention

[0005] The main purpose of the present application is to provide a data collection and processing method, device, electronic device and readable storage medium, aiming to solve the technical problem of how to monitor IMS DC data services in an IMS DC encryption scenario.

[0006] To achieve the above objectives, the present application provides a data collection and processing method, comprising: Collect IMS DC data transmitted by the target transmission segment in the current service interaction process, where the target transmission segment is a service layer transmission segment between the 5G new call media plane and the 5G new call capability network element, or a service layer transmission segment between the 5G new call media plane and the service AS; The target service layer key information identified based on the IMS DC data is acquired, and the target XDR information corresponding to the current service interaction process is generated according to the target service layer key information.

[0007] In addition, to achieve the above purpose, the present application also provides a data acquisition and processing device, including: A data cleaning module is configured to collect IMS DC data transmitted in a target transmission segment in a current service interaction process, wherein the target transmission segment is a service layer transmission segment between a 5G new call media plane and a 5G new call capability network element, or a service layer transmission segment between the 5G new call media plane and a service AS; The XDR synthesis module is configured to obtain target service layer key information identified based on the IMS DC data, and generate target XDR information corresponding to the current service interaction process according to the target service layer key information.

[0008] In addition, to achieve the above-mentioned purpose, the present application also provides an electronic device, which includes: a memory, a processor, and a data acquisition and processing program stored in the memory and executable on the processor, and when the data acquisition and processing program is executed by the processor, the data acquisition and processing method as described above is implemented.

[0009] In addition, to achieve the above-mentioned purpose, the present application also provides a computer-readable storage medium, on which a data acquisition processing program is stored, and when the data acquisition processing program is executed by a processor, the data acquisition processing method as described above is implemented.

[0010] The 5G new call NF (Network Function) involved in the DC data interaction between the terminal and the 5G new call network includes VONR+ (Enhanced Voice over NR, 5G+ voice solution) media plane (i.e. 5G new call media plane), VONR+ capability network element (i.e. 5G new call capability network element) and service AS (Application Server). The DC service layer data between the terminal and the VONR+ media plane is encapsulated using the DC channel protocol stack SCTP (Stream Control Transmission Protocol, Stream Control Transmission Protocol) / DTLS (Datagram Transport Layer Security, Datagram Transport Layer Security Protocol) / UDP (User Datagram Protocol, User Datagram Protocol), where DTLS is responsible for encrypting the carried DC data. The DC service layer data between the VONR+ media plane and the service AS / VONR+ capability network element is encapsulated using HTTP / 2 (Hypertext Transfer Protocol Version 2) and TCP (Transmission Control Protocol, Transmission Control Protocol) protocol stack. This part is usually deployed in the core network trusted resource pool, which is secure and does not require encryption.

[0011] That is, the applicant found that no matter whether the terminal sends DC service layer data to the service AS / VONR+ capability network element or the service AS / VONR+ capability network element sends DC service layer data to the terminal, the DC service layer data will go through two transmissions, and the DC service layer data in these two transmissions are the same. Therefore, although the service layer data will be encrypted in the DC channel, resulting in the inability to monitor IMS DC data, the data between the VONR+ media plane and the service AS / VONR+ capability network element is not encrypted, so this segment of data can be collected for service monitoring of DC data.

[0012] Based on this principle, the present application proposes a data collection and processing method, device, electronic device and readable storage medium. In the data collection and processing method, even if the IMS DC data between the terminal and the VONR+ media plane is encrypted, it makes it impossible to monitor the IMS DC data service. The technical solution of the embodiment of the present application is to collect the IMS DC data transmitted by the target transmission segment in the current service interaction process, and the target transmission segment is the service layer transmission segment between the VONR+ media plane and the VONR+ capability network element, or the service layer transmission segment between the VONR+ media plane and the service AS, and then obtain the target service layer key information identified based on the IMS DC data, wherein the target service layer key information includes the first service layer key information of the service request process, and then generate the target XDR information corresponding to the current service interaction process according to the target service layer key information, so that in the IMS DC channel encryption scenario, the embodiment of the present application can effectively realize the IMS by utilizing the IMS DC (non-encrypted) data transmitted between the VONR+ media plane (i.e., the 5G new call media plane) and the service AS / VONR+ capability network element (i.e., the 5G new call capability network element). The monitoring of DC data services effectively solves the technical problem of how to monitor IMS DC data services in IMS DC encryption scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the structures shown in these drawings without paying any creative work.

[0014] Figure 1 This is a schematic diagram of the IMS DC channel of the 5G new call network; Figure 2 This is a flow chart of the first embodiment of the data collection and processing method of the present application; Figure 3 This is a schematic diagram of a transmission protocol stack for IMS DC data in an embodiment of the present application; Figure 4 This is a schematic diagram of a deployment scenario of an IMS DC signaling monitoring device in an embodiment of the present application; Figure 5 This is a module processing flow chart of an IMS DC signaling monitoring device in an embodiment of the present application; Figure 6 This is a processing flow chart of an XDR synthesis module in one embodiment of the present application; Figure 7This is a schematic diagram of a BDC requesting data transmission in an embodiment of the present application; Figure 8 This is a schematic diagram of ADC request data transmission carried by JSON initiated by a terminal in an embodiment of the present application; Fig. 9 This is a schematic diagram of ADC request data transmission carried by JSON initiated by a service AS / VONR+ capability network element in an embodiment of the present application; Fig.10 This is a flow chart of identifying request response signaling of IMS DC in one embodiment of the present application; Fig.11 This is a flowchart for identifying the main service type and sub-service type of the DC request signaling in an embodiment of the present application; Fig.12 This is a schematic diagram of the functional modules of the data acquisition and processing device according to an embodiment of the present application; Fig.13 This is a schematic diagram of the hardware structure of the electronic device involved in the embodiment of the present application.

[0015] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0016] It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0017] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0018] It should be noted that all directional indications in the embodiments of the present application (such as up, down, left, right, front, back, etc.) are only used to explain the relative position relationship, movement status, etc. between the components under a certain specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indication will also change accordingly.

[0019] In this application, unless otherwise clearly specified and limited, the terms "connection", "fixation", etc. should be understood in a broad sense. For example, "fixation" can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium, it can be the internal connection of two elements or the interaction relationship between two elements, unless otherwise clearly defined. For ordinary technicians in this field, the specific meanings of the above terms in this application can be understood according to specific circumstances.

[0020] In addition, in this application, descriptions such as "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying their relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In addition, the technical solutions between the various embodiments can be combined with each other, but they must be based on the ability of ordinary technicians in this field to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such combination of technical solutions does not exist and is not within the scope of protection required by this application.

[0021] refer to Figure 1 One way to implement new 5G calls is to add an IMS (IP Multimedia Subsystem) DC (Data Channel) in addition to the traditional voice call audio and video stream channels, and transmit pictures, audio, video, menus, emoticons, locations, AR (Augmented Reality) / VR (Virtual Reality) and other media between the terminal and the network to implement various services. In order to improve user experience perception, it is necessary to introduce a signaling monitoring system to monitor the key indicators of IMS DC data service operation in real time, eliminate network risks in advance, and quickly demarcate and locate sudden failures.

[0022] A direct way to monitor IMS DC data services is to collect IMS DC data packets transmitted between the terminal and the network for deep packet identification. However, for security reasons, operators will encrypt IMS DC data packets transmitted between the terminal and the network. In this scenario, the signaling monitoring system cannot decrypt the encrypted IMS DC data packets, resulting in the inability to monitor IMS DC services. Therefore, how to monitor IMS DC data services in the IMS DC encryption scenario is an urgent problem to be solved.

[0023] Based on this, the present application embodiment provides a data collection and processing method, referring to Figure 2 , Figure 2This is a flow chart of an embodiment of a data collection and processing method of the present application. In this embodiment, the data collection and processing method includes: Step S100, collecting IMS DC data transmitted in the target transmission segment in the current service interaction process; In this embodiment, the process type of the current service interaction process is a service request process or a service response process.

[0024] Among them, the target transmission segment is the service layer transmission segment between the 5G new call media plane and the 5G new call capability network element, or the service layer transmission segment between the 5G new call media plane and the service AS.

[0025] In this embodiment, the business process scenarios to which the data collection and processing method is applied include but are not limited to: starting intelligent translation, stopping intelligent translation, starting fun calls, and stopping fun calls, etc.

[0026] It can be understood that the IMS (IP Multimedia Subsystem) DC (Data Channel) data includes but is not limited to picture data, audio data, video data, menu data, expression data, location data and AR (Augmented Reality) / VR (Virtual Reality) data, etc.

[0027] Those skilled in the art will appreciate that, generally, the overall process of business interaction includes at least one business request process. Of course, the overall process of business interaction may also include a business response process corresponding to the business request process.

[0028] As an example only, the business request process may include but is not limited to: a start smart translation request in a start smart translation scenario, a stop smart translation request in a stop smart translation scenario, a start fun call request in a start fun call scenario, and a stop fun call request in a stop fun call scenario.

[0029] Correspondingly, the business response process may include but is not limited to: starting the intelligent translation response in the start intelligent translation scenario, stopping the intelligent translation response in the stop intelligent translation scenario, starting the fun call response in the start fun call scenario, and stopping the fun call response in the stop fun call scenario.

[0030] It should be noted that the target transmission segment in the current service interaction process refers to: the service layer transmission segment between the 5G new call media plane and the 5G new call capability network element, or the service layer transmission segment between the 5G new call media plane and the service AS (Application Server).

[0031] It will be understood by those skilled in the art that Figure 3 As shown in the figure, when the terminal sends DC service layer data to the service AS or VONR+ capability network element (i.e., 5G new call capability network element), the service layer data is first encapsulated and encrypted using the DC channel protocol stack and sent to the VONR+ media plane via the DC channel. After receiving the DC data, the VONR+ media plane decrypts and strips the DC channel protocol stack to obtain the DC service layer data, and then uses the HTTP / 2 protocol stack to encapsulate and send it to the service AS / VONR+ capability network element. If the service AS or 5G new call capability network element needs to send DC service layer data to the terminal, the DC service layer data is first encapsulated using the HTTP / 2 protocol stack and sent to the VONR+ media plane (i.e., 5G new call media plane). After receiving the HTTP / 2 data, the VONR+ media plane strips the HTTP / 2 protocol stack to obtain the service layer data, and then uses the DC channel protocol stack to encapsulate and encrypt and send it to the terminal via the DC channel.

[0032] From the above description, it can be seen that whether the terminal sends DC service layer data to the service AS / VONR+ capability network element, or the service AS / VONR+ capability network element sends DC service layer data to the terminal, the DC service layer data will go through two transmission segments, and the DC service layer data of these two transmission segments are the same. Therefore, although the service layer data will be encrypted in the DC channel, resulting in the inability to monitor DC data, the VONR+ media plane and the service AS / VONR+ capability network element are non-encrypted. Therefore, the embodiment of the present application collects IMS DC data of the service layer transmission segment between the 5G new call media plane and the 5G new call capability network element, or the service layer transmission segment between the 5G new call media plane and the service AS (Application Server), so as to facilitate service monitoring of DC data based on the collected data of the target transmission segment.

[0033] Step S200: Acquire target service layer key information identified based on the IMS DC data, and generate target XDR information corresponding to the current service interaction process according to the target service layer key information.

[0034] Exemplarily, the target business layer key information includes at least one of the following: The first service layer key information of the service request process in the current service interaction process identified based on the IMS DC data, Second service layer key information of a service response process in a current service interaction process identified based on the IMS DC data.

[0035] It should be noted that, in order to better achieve the purpose of effectively monitoring the IMS DC data service in the embodiment of the present application, generally, the target service layer key information includes at least the first service layer key information of the service request process.

[0036] In this embodiment, the current business interaction process is generally a request-response mode, one request corresponds to one response, that is, in general, the overall process of the business interaction process includes at least one business request process, and the business response process corresponding to the business request process. Of course, those skilled in the art can understand that in some cases, there are also cases where the current business interaction process only includes a request mode, that is, the overall process of the business interaction process only includes a business request process, and there is no business response process corresponding to the business request process. Therefore, in some implementation scenarios, the target business layer key information only includes the first business layer key information, but does not include the second business layer key information. In other implementation scenarios, the target business layer key information includes both the first business layer key information and the second business layer key information.

[0037] Exemplarily, the first business layer key information includes at least business type information. In one embodiment, the business type information includes main business type information and sub-business type information. In another embodiment, the business type information only includes main business type information. It is easy to understand that the business type information varies adaptively according to different specific business interaction types, and this embodiment does not make specific limitations on this.

[0038] The target XDR information refers to XDR (X Data Recording) information corresponding to the current interactive process. It is known to those skilled in the art that XDR information is generally an output product of a signaling monitoring device.

[0039] In a possible implementation manner, the step of acquiring target service layer key information identified based on the IMS DC data includes: Step A10, acquiring the first service layer key information identified based on the IMS DC data, and counting the cumulative duration from the time when the first service layer key information is acquired; Step A20, when the accumulated duration reaches the preset duration threshold and the second business layer key information is still not obtained, the first business layer key information is used as the target business layer key information, wherein the second business layer key information is the business layer key information of the business response process identified based on the IMS DC data.

[0040] The preset duration threshold can be set by those skilled in the art according to actual conditions, and is not specifically limited in this embodiment.

[0041] This embodiment obtains the first business layer key information identified based on IMS DC data, and counts the cumulative time starting from the acquisition of the first business layer key information. When the cumulative time reaches a preset time threshold and the second business layer key information is still not obtained, the first business layer key information is used as the target business layer key information. Therefore, this embodiment sets the preset time threshold through the timer, and automatically triggers the step of generating XDR information based on the first business layer key information when the second business layer key information is not received before the preset time threshold is reached, thereby effectively supporting the business scenario requirements in which some business interaction process types only have business request processes but no business response processes, thereby improving the robustness of the data collection and processing method of the embodiment of the present application.

[0042] Further, in another possible implementation, after the step of counting the cumulative duration starting from the acquisition of the first business layer key information, the method further includes: Step B10: before the accumulated time reaches the preset time threshold, if the second business layer key information is obtained, the first business layer key information and the second business layer key information are used as target business layer key information.

[0043] This embodiment uses the first business layer key information and the second business layer key information as the target business layer key information when the second business layer key information is obtained before the cumulative duration reaches the preset duration threshold. This allows this embodiment to set the preset duration threshold through a timer. When the second business layer key information is received before the preset duration threshold is reached, the step of generating XDR information based on the first business layer key information and the second business layer key information is executed, thereby effectively supporting the business scenario requirements of some business interaction process types that have both business request processes and business response processes, and further improving the robustness of the data collection and processing method of the embodiment of the present application.

[0044] In order to help understand the business interaction scenario of the data collection and processing method in the embodiment of the present application, a business interaction scenario of a specific embodiment is listed. In this embodiment, Figure 4 As shown, Figure 4 The deployment location of the signaling monitoring device in the 5G new call network is demonstrated. It can be seen that the signaling monitoring device is not a direct participant in network communications. It only uses the splitter equipment to split and replicate the real-time signaling data of the existing network, and then analyzes and evaluates the network operation status. The 5G new call NF will neither forward the signaling through the signaling monitoring device nor perceive its existence.

[0045] like Figure 3As shown in the figure, the 5G new call NF (Network Function) involved in the DC data interaction between the terminal and the 5G new call network includes VONR+ (Enhanced Voice over NR, 5G+ voice solution) media plane, VONR+ capability network element and business AS (Application Server). The DC service layer data between the terminal and the VONR+ media plane is encapsulated using the DC channel protocol stack SCTP (Stream Control Transmission Protocol, Stream Control Transmission Protocol) / DTLS (Datagram Transport Layer Security, Datagram Transport Layer Security Protocol) / UDP (User Datagram Protocol, User Datagram Protocol), where DTLS is responsible for encrypting the carried DC data. The DC service layer data between the VONR+ media plane and the business AS / VONR+ capability network element is encapsulated using HTTP / 2 (Hypertext Transfer Protocol Version 2, Hypertext Transfer Protocol Version 2) and TCP (Transmission Control Protocol, Transmission Control Protocol) protocol stack. This part is usually deployed in the core network trusted resource pool, which is secure and does not require encryption.

[0046] That is, the applicant found that no matter whether the terminal sends DC service layer data to the service AS / VONR+ capability network element or the service AS / VONR+ capability network element sends DC service layer data to the terminal, the DC service layer data will go through two transmissions, and the DC service layer data in these two transmissions are the same. Therefore, although the service layer data will be encrypted in the DC channel, resulting in the inability to monitor IMS DC data, the data between the VONR+ media plane and the service AS / VONR+ capability network element is not encrypted, so this segment of data can be collected for service monitoring of DC data.

[0047] Based on this principle, the present application proposes a data collection and processing method, device, electronic device and readable storage medium. In the data collection and processing method, even if the IMS DC data between the terminal and the VONR+ media plane is encrypted, it makes it impossible to monitor the IMS DC data service. The technical solution of the embodiment of the present application is to collect the IMS DC data transmitted by the target transmission segment in the current service interaction process, and the target transmission segment is the service layer transmission segment between the VONR+ media plane and the VONR+ capability network element, or the service layer transmission segment between the VONR+ media plane and the service AS, and then obtain the target service layer key information identified based on the IMS DC data, wherein the target service layer key information includes the first service layer key information of the service request process, and then generate the target XDR information corresponding to the current service interaction process according to the target service layer key information, so that in the IMS DC channel encryption scenario, the embodiment of the present application can effectively realize the IMS by utilizing the IMS DC (non-encrypted) data transmitted between the VONR+ media plane (i.e., the 5G new call media plane) and the service AS / VONR+ capability network element (i.e., the 5G new call capability network element). The monitoring of DC data services effectively solves the technical problem of how to monitor IMS DC data services in IMS DC encryption scenarios.

[0048] Exemplarily, after the step of generating target XDR information corresponding to the current service interaction process, the method further includes: Step C10: sending the target XDR information to a third-party application.

[0049] In this embodiment, it should be noted that before sending the target XDR information corresponding to the current business interaction process to the third-party application, it can be encoded by TLV (Type Length Value) encoding or fixed structure encoding and then sent to the third-party application. That is, sending the target XDR information to the third-party application should also include the protection scope of "encoding the target XDR information and sending it to the third-party application".

[0050] In this embodiment, the third-party application is an application platform other than the signaling monitoring system. In another example, the execution subject of the embodiment of the present application is a first NF (Network Function) unit, and the third-party application may be a second NF unit that performs service interaction with the first NF unit. In another example, the execution subject of the embodiment of the present application is a first signaling interface device, and the third-party application may be a second signaling interface device that performs service interaction with the first signaling interface. In another example, the execution subject of the embodiment of the present application is a first electronic device, and the third-party application may be a second electronic device that performs service interaction with the first electronic device. This embodiment does not make specific limitations on this.

[0051] This embodiment sends the target XDR information to a third-party application, so that the embodiment of the present application uses Socket to establish a link with the third-party application, and sends the target XDR information to the third-party application, thereby facilitating the use of IMS DC (unencrypted) data transmitted between the 5G new call media plane and the 5G new call capability network element / service AS to monitor the IMS DC data service.

[0052] Based on the first embodiment of the present application, a second embodiment of the data collection and processing method of the present application is proposed. The step of collecting IMS DC data transmitted by the target transmission segment in the current service interaction process includes: Step D10, collecting HTTP / 2 signaling transmitted by the target transmission segment in the current service interaction process; Step D20, identifying and filtering the target DC signaling carrying DC service layer data from the HTTP / 2 signaling; Step D30, determining the IMSDC data transmitted in the target transmission segment in the current service interaction process according to the target DC signaling.

[0053] This embodiment collects HTTP / 2 signaling transmitted in the target transmission segment in the current service interaction process, and identifies and filters the target DC signaling carrying DC service layer data from the HTTP / 2 signaling, thereby facilitating accurate acquisition of the IMS DC data transmitted in the target transmission segment in the current service interaction process based on the target DC signaling.

[0054] Further, the step of determining, according to the target DC signaling, the IMS DC data transmitted in the target transmission segment in the current service interaction process comprises: Step E10, decoding the HEADER frame and the DATA frame of the target DC signaling to obtain DC service layer data, and using the decoded DC service layer data as the IMS DC data transmitted in the target transmission segment in the current service interaction process.

[0055] This embodiment decodes the HEADER frame and DATA frame of the target DC signaling to obtain DC service layer data, and thus accurately obtains the IMS DC data transmitted in the target transmission segment in the current service interaction process based on the decoded DC service layer data.

[0056] In order to help understand the technical concept or technical principle of the present embodiment, a signaling monitoring device of a specific embodiment is listed. By way of example, in the IMS DC channel encryption scenario, the data acquisition and processing device in the embodiment of the present application can realize decoding of 5G new call DC service layer data, request or response identification, service type identification, key information extraction and storage, XDR (X Data Recording) synthesis and XDR distribution by collecting IMS DC data transmitted between the VONR+ media plane and the service AS / VONR+ capability network element.

[0057] like Figure 5 As shown, the signaling monitoring device of this embodiment is mainly composed of a data cleaning module, an XDR synthesis module and an XDR distribution module. The data cleaning module implements the screening of HTTP / 2 signaling that carries DC service layer data; the XDR synthesis module implements signaling decoding, request response identification, service type identification, key information extraction and storage, and XDR synthesis; the XDR distribution module distributes XDR to a third party.

[0058] The data cleaning module needs to identify HTTP / 2 signaling that carries DC data. The signaling monitoring device receives signaling from the 5G new call core network, which may contain HTTP / 2 signaling that carries non-DC data. This part of the data needs to be filtered out.

[0059] Specifically, the XDR synthesis module is set to: 1) Decode the HEADER frame and DATA frame of HTTP / 2 signaling that carries DC service layer data identified by the protocol cleaning module; 2) Determine whether this DC signaling interaction is a request or a response; 3) For the request signaling, determine the main service type and sub-service type of this service interaction, apply for a node (hereinafter referred to as the "preset target node") in the memory database (hereinafter referred to as the "database"), extract the key information of the DC's service layer and save it in the memory database; 4) For the response signaling, the query to the memory database is successful, and the key information of the DC service layer carried by the response signaling is also extracted and saved in the database, and then synthesized and output as XDR.

[0060] The XDR distribution module is configured to receive the XDR from the XDR synthesis module, and then transmit the received XDR to the third party using the socket connected to the third party.

[0061] It should be noted that although the above-mentioned specific embodiments show many details, they are only used to help understand the technical concepts or technical principles of the embodiments of the present application, and do not constitute a limitation on the present application. More simple transformations based on the technical concepts should all be within the scope of protection of the present application.

[0062] In a possible implementation manner, after the step of determining the IMSDC data transmitted in the target transmission segment in the current service interaction process, the method further includes: Step F10, identifying the process type of the current service interaction process according to the signaling type of the target DC signaling, wherein the signaling type includes request signaling and response signaling; Step F20: When it is identified that the process type is the service request process, the first service layer key information is identified according to the IMS DC data.

[0063] In this embodiment, after the first business layer key information is identified, the first business layer key information may be saved in a preset target node of the database.

[0064] It should be noted that the first business layer key information includes at least business type information. In one embodiment, the business type information includes main business type information and sub-business type information. In another embodiment, the business type information only includes main business type information. The business type information varies adaptively according to the specific business interaction type, and this embodiment does not make specific limitations on this.

[0065] The embodiment of the present application identifies the process type of the current service interaction process according to the signaling type of the target DC signaling, wherein the signaling type includes request signaling and response signaling, and then, when it is identified that the process type is a service request process, identifies the first service layer key information according to the IMS DC data, wherein the first service layer key information includes main service type information and sub-service type information, and saves the first service layer key information to the preset target node of the database, thereby completing the processing of the DC request signaling, facilitating the subsequent use of the first service layer key information transmitted between the 5G new call media plane and the service AS / 5G new call capability network element, and can effectively realize the monitoring of the first service layer key information in the IMS DC (non-encrypted) data.

[0066] In a possible implementation, the target business layer key information further includes second business layer key information of the business response process. After the step of identifying the process type of the current business interaction process, the method further includes: Step G10: When it is identified that the process type is the service response process, the second service layer key information is identified according to the IMS DC data.

[0067] In this embodiment, after the second business layer key information is identified, the preset target node where the first business layer key information is stored can be queried from the database, and the second business layer key information is stored in the preset target node obtained by the query.

[0068] Exemplarily, the step of generating the target XDR information corresponding to the current business interaction process based on the target business layer key information may include: extracting the first business layer key information and the second business layer key information from the preset target node of the database; filling the extracted first business layer key information and the second business layer key information into the initial XDR information corresponding to the current business interaction process to generate the target XDR information corresponding to the current business interaction process.

[0069] It should be noted that the second service layer key information at least includes response identification information of the response signaling.

[0070] This embodiment identifies the second business layer key information of the business response process according to the target DC signaling when the process type is identified as a business response process, wherein the second business layer key information includes the response identification information of the response signaling, and then obtains the preset target node where the first business layer key information is stored from the database, and saves the second business layer key information to the preset target node obtained by the query, thereby completing the processing of the DC response signaling, facilitating the subsequent use of the second business layer key information transmitted between the 5G new call media plane and the business AS / 5G new call capability network element, and can effectively realize the monitoring of the second business layer key information in the IMS DC (non-encrypted) data.

[0071] In order to further help understand the technical concept or technical principle of the embodiment of the present application, a specific embodiment 2 is listed, please refer to Figure 6 , Figure 6 The processing flow chart of the XDR synthesis module in one embodiment of the present application includes: S10: Decode the HEADER frame and DATA frame of HTTP / 2, which will not be described in detail here.

[0072] S20: Determine whether the current DC signaling is a request signaling or a response signaling.

[0073] The DC service interaction is a request-response mode, where one request corresponds to one response. In the signaling monitoring device, this embodiment needs to distinguish whether the signaling is a request signaling or a response signaling, so as to process it in different ways.

[0074] There are two common encodings for DC business layer data: HTTP / 1.1 (Hypertext Transfer Protocol Version 1.1) and JSON (JavaScript Object Notation). BDC (Bootsrap DC) is mainly used for terminal download of applets and uses HTTP / 1.1 encoding, while ADC (Application DC) is mainly used for transmitting various media information such as pictures, audio and video, menus, and AR / VR. This embodiment can use both HTTP / 1.1 and JSON encoding.

[0075] In this embodiment, for BDC (Bootsrap DC) data service interaction, the service party that initiates the DC request can only be the terminal. Figure 7 As shown, the terminal initiates a BDC request, encapsulates and encrypts the DC service layer HTTP / 1.1 data with the DC protocol stack, and then sends it to the VONR+ media plane. The VONR+ media plane decrypts and extracts the HTTP / 1.1 signaling data, extracts the request line Url in the signaling, and then concatenates it with the {appUrl} of the pre-stored service AS / VONR+ capability network element receiving DC data {appUrl} / url as the :path (i.e. path) of the HTTP / 2 request signaling, and then encapsulates it with the parsed HTTP / 1.1 header as a HEADER frame. Optionally, if the HTTP / 1.1 signaling carries a message body, it is encapsulated as a HTTP / 2 DATA frame, and an HTTP / 2 signaling is constructed and sent to the service AS / VONR+ capability network element.

[0076] For ADC (Application DC) data service interaction, either the terminal or the service AS / VONR+ capability network element can initiate a request. For HTTP / 1.1-encoded ADC service layer data, the processing method is the same as the request processing method initiated by BDC, which will not be repeated here. For JSON-encoded service layer data, the terminal initiates an ADC request, such as Figure 8 As shown, the DC service layer JSON data is encapsulated and encrypted with the DC protocol stack and then sent to the VONR+ media plane. The VONR+ media plane decrypts and extracts the JSON data, encapsulates it as an HTTP / 2 DATA frame, and then uses the {appUrl} of the pre-stored service AS / VONR+ capability network element to receive the DC data as the :path of the HTTP / 2 request signaling, and then encapsulates it with other header fields as a HEADER frame, constructs an HTTP / 2 signaling and sends it to the service AS / VONR+ capability network element. If the service AS / VONR+ capability network element initiates an ADC request, such as Fig. 9 As shown, the {dataUrl} of the DC data received by the VONR+ media plane is used as the :path of the HTTP / 2 request signaling, and then it is encapsulated with other header fields as a HEADER frame, and the JSON data is encapsulated as a DATA frame of HTTP / 2. HTTP / 2 signaling is constructed and sent to the VONR+ media plane. The VONR+ media plane takes out the JSON data in the DATA frame, and then encapsulates and encrypts it with the DC protocol stack and sends it to the terminal.

[0077] As can be seen from the above, the ADC request or the BDC request corresponds to the HTTP / 2 request. Therefore, this embodiment can indirectly determine whether the DC is a request signaling or a response signaling by determining whether the HTTP / 2 is a request or a response.

[0078] like Fig.10 As shown in the figure, if the header field decoded from the HEADER frame carries one of the three fields: path, :method and :scheme, it can be judged as HTTP / 2 request signaling, and the DC data carried can be judged as DC request signaling. If the header field decoded from the HEADER frame carries :status, it can be judged as HTTP / 2 response signaling, and the DC data carried can be judged as DC response signaling. All the above fields are not decoded and need further identification.

[0079] For JSON-encoded ADC, both request data and response data will carry the parameter innerUrl. If the innerUrl parameter decoded from the DATA frame ends with request, this DC data is a request signaling; if the innerUrl parameter decoded from the DATA frame ends with response, this DC data is a response signaling.

[0080] If none of the above identification conditions are met, the signaling is discarded.

[0081] After S20, S30 is executed: determining the main service type and sub-service type of this service interaction for the DC request signaling.

[0082] like Fig.11As shown, if it is a BDC or HTTP / 1.1 encoded ADC request at the business layer, the main business type can be identified by matching :path with the preset key strings for identifying each main business type. If the main business type identification fails, the signaling is discarded. If the business layer is a JSON-encoded ADC request, according to the innerUrl parameter encoding rules of the 5G new call DC service interaction, the main business type identification can remove the request at the end of the innerUrl and match it with the preset key identification strings of each main business type. If the match is successful, the main business type can be obtained. If the match fails, the signaling is discarded. After some JSON-encoded ADC processes identify the main business type, they need to continue to identify the sub-business type. They can rely on the bussType carried by the body parameter to match the key strings for identifying each sub-business type to identify the sub-business type. If the sub-business type identification fails, the signaling is discarded.

[0083] Take the user request to start and stop the business function process of the intelligent translation service as an example. The interface specification defines that its request business layer data is encoded in JSON, and the parameter innerUrl is fixed to " / service / request". The signaling monitoring device receives the DC data and finds that it is carried by HTTP / 2 request signaling or decodes to obtain innerUrl and innerUrl ends with request, then it can be identified as request signaling; if innerUrl is " / service / " after removing request, then the main business type of this signaling interaction is the user request to start and stop the business function. Further, the body parameter carried by the signaling is not empty and carries the bussType field. If the value of this field is SPEECH_TO_TEXT, the sub-service type is speech transcription; if the value of this field is SPEECH_TRANSLATION, the sub-service type is real-time translation; if the value of this field is SPEECH_ASSISTANT, the sub-service type is voice assistant.

[0084] After S30, S40 is executed: applying for a node (ie, a preset target node) in the memory database for the request signaling.

[0085] S50: Save key information such as the DC main service type and sub-service type into a memory database (ie, database). This completes the processing of the DC request signaling.

[0086] S60: For the response signaling, query the database for the node storing the corresponding request signaling.

[0087] S70: If the node query is successful, the DC key information (ie, the second service layer key information) and other DC key information carried by the response signaling are extracted and saved in the querying node.

[0088] S80: Receiving a response indicates that a DC service interaction is completed. At this time, an XDR can be issued, and the key information saved by the database node can be filled into the XDR, and sent to the XDR distribution module, and the database node can be released at the same time.

[0089] It should be noted that although the above-mentioned specific embodiment 2 shows many details, it is only used to help understand the technical concept or technical principle of the embodiment of the present application, and does not constitute a limitation of the present application. More simple transformations based on the technical concept should all be within the scope of protection of the present application.

[0090] In addition, the present application also provides a data acquisition and processing device, referring to Fig.12 , Fig.12 This is a functional module diagram of an embodiment of a data acquisition and processing device of the present application.

[0091] In this embodiment, the data acquisition and processing device includes: The data cleaning module 10 is configured to collect IMS DC data transmitted by a target transmission segment in a current service interaction process, wherein the target transmission segment is a service layer transmission segment between a 5G new call media plane and a 5G new call capability network element, or a service layer transmission segment between the 5G new call media plane and a service AS; The XDR synthesis module 20 is configured to obtain target service layer key information identified based on the IMS DC data, and generate target XDR information corresponding to the current service interaction process according to the target service layer key information.

[0092] In some embodiments, the target business layer key information includes at least one of the following: The first service layer key information of the service request process in the current service interaction process identified based on the IMS DC data, Second service layer key information of a service response process in a current service interaction process identified based on the IMS DC data.

[0093] In some embodiments, the data cleaning module 10 is further configured to: Collect HTTP / 2 signaling transmitted by the target transmission segment in the current business interaction process; Identify and filter the target DC signaling that carries DC service layer data from HTTP / 2 signaling; According to the target DC signaling, the IMS DC data transmitted in the target transmission segment in the current service interaction process is determined.

[0094] In some embodiments, the second service layer key information includes at least response identification information of the response signaling.

[0095] In some embodiments, the XDR synthesis module 20 is further configured to: The HEADER frame and the DATA frame of the target DC signaling are decoded to obtain DC service layer data, and the decoded DC service layer data is used as the IMS DC data transmitted in the target transmission segment in the current service interaction process.

[0096] In some embodiments, the first service layer key information includes at least service type information.

[0097] In some embodiments, the data collection and processing device further includes an XDR distribution module (not shown), and the XDR distribution module is configured to: The target XDR information is sent to a third-party application.

[0098] The data acquisition and processing device provided in this embodiment and the data acquisition and processing method provided in the above embodiment belong to the same inventive concept. The technical details not fully described in this embodiment can be found in the embodiments of the above data acquisition and processing method. This embodiment has the same beneficial effects as the embodiments of the data acquisition and processing method, which will not be repeated here.

[0099] The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0100] In addition, the present application also provides an electronic device, referring to Fig.13 , Fig.13 The hardware structure diagram of an electronic device provided in an embodiment of the present application is shown in FIG. Fig.13As shown, the electronic device may include: a processor 1001, a communication bus 1002, a user interface 1003, a network interface 1004 and a memory 1005. Among them, the processor 1001 may be a central processing unit (CPU). The communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a wireless fidelity (WIreless-FIdelity, WI-FI) interface). The memory 1005 may be a high-speed random access memory (Random Access Memory, RAM), or a stable non-volatile memory (Non-VolatileMemory, NVM), such as a disk memory. The memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0101] Those skilled in the art will understand that Fig.13 The structure shown in the figure does not constitute a limitation on the electronic device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. Fig.13 As shown, the memory 1005 as a storage medium may include an operating system, a data storage module, a network communication module, a user interface module and a data acquisition processing program.

[0102] exist Fig.13 In the electronic device shown, the network interface 1004 is mainly used for data communication with other devices; the user interface 1003 is mainly used for data interaction with the user; the processor 1001 and the memory 1005 in this embodiment can be set in the electronic device, and the electronic device calls the data acquisition and processing program stored in the memory 1005 through the processor 1001, and executes the data acquisition and processing method provided in any of the above embodiments.

[0103] The device proposed in this embodiment and the data acquisition and processing method proposed in the above embodiment belong to the same inventive concept. The technical details not fully described in this embodiment can be referred to any of the above embodiments, and this embodiment has the same beneficial effects as executing the data acquisition and processing method.

[0104] In addition, an embodiment of the present application also proposes a computer-readable storage medium, which may be a non-volatile computer-readable storage medium, on which a data acquisition processing program is stored, and when the data acquisition processing program is executed by a processor, the data acquisition processing method of the present application as described above is implemented.

[0105] The various embodiments of the electronic device and computer-readable storage medium of the present application can all refer to the various embodiments of the data acquisition and processing method of the present application, which will not be repeated here.

[0106] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or system including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or system. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or system including the element.

[0107] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0108] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes a number of instructions for an electronic device to execute the methods described in each embodiment of the present application.

[0109] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A data collection and processing method, characterized in that: include: Collect IMS DC data transmitted by the target transmission segment in the current service interaction process, where the target transmission segment is a service layer transmission segment between the 5G new call media plane and the 5G new call capability network element, or a service layer transmission segment between the 5G new call media plane and the service AS; The target service layer key information identified based on the IMS DC data is acquired, and the target XDR information corresponding to the current service interaction process is generated according to the target service layer key information.

2. The data collection and processing method according to claim 1, characterized in that: The target service layer key information includes at least one of the following: The first service layer key information of the service request process in the current service interaction process identified based on the IMS DC data, Second service layer key information of a service response process in a current service interaction process identified based on the IMS DC data.

3. The data collection and processing method according to claim 2, characterized in that: The first service layer key information includes at least service type information.

4. The data collection and processing method according to claim 2, characterized in that: The second service layer key information at least includes response identification information.

5. The data collection and processing method according to claim 1, characterized in that: The step of collecting IMS DC data transmitted in the target transmission segment in the current service interaction process includes: Collect HTTP / 2 signaling transmitted by the target transmission segment in the current business interaction process; Identify and filter the target DC signaling that carries DC service layer data from HTTP / 2 signaling; According to the target DC signaling, the IMS DC data transmitted in the target transmission segment in the current service interaction process is determined.

6. The data collection and processing method according to claim 5, characterized in that: The step of determining, according to the target DC signaling, the IMS DC data transmitted in the target transmission segment in the current service interaction process comprises: The HEADER frame and the DATA frame of the target DC signaling are decoded to obtain DC service layer data, and the decoded DC service layer data is used as the IMS DC data transmitted in the target transmission segment in the current service interaction process.

7. The data acquisition and processing method according to any one of claims 1 to 6, characterized in that: After the step of generating target XDR information corresponding to the current service interaction process, the method further includes: The target XDR information is sent to a third-party application.

8. A data acquisition and processing device, characterized in that: include: A data cleaning module is configured to collect IMS DC data transmitted by a target transmission segment in a current service interaction process, wherein the target transmission segment is a service layer transmission segment between a 5G new call media plane and a 5G new call capability network element, or a service layer transmission segment between the 5G new call media plane and a service AS; The XDR synthesis module is configured to obtain target service layer key information identified based on the IMS DC data, and generate target XDR information corresponding to the current service interaction process according to the target service layer key information.

9. An electronic device, characterized in that: include: A memory, a processor, and a data acquisition processing program stored in the memory and executable on the processor, wherein the data acquisition processing program, when executed by the processor, implements the data acquisition processing method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a data acquisition processing program, and when the data acquisition processing program is executed by a processor, the data acquisition processing method according to any one of claims 1 to 7 is implemented.

Images