Data collection processing method and apparatus, and electronic device and readable storage medium

Abstract

The present application belongs to the field of communications. Disclosed are a data collection processing method and apparatus, and an electronic device and a readable storage medium. The method of the present application comprises: collecting IMS DC data, which is transmitted in a target transmission band during the current business interaction process; and acquiring target business layer key information, which is identified on the basis of the IMS DC data, and according to the target business layer key information, generating target XDR information corresponding to the current business interaction process.

Description

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

[0001] Related applications

[0002] This application claims priority to Chinese patent application No. 202311180152.X filed on September 13, 2023, the entire contents of which are incorporated by reference into this application. Technical Field

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

[0004] With the rapid development of the 5G industry, operators such as China Mobile have gradually launched a number of 5G-themed applications, such as 5G New Call. 5G New Call is a 5G network-based ultra-HD voice and video calling service, along with related value-added services. These services include 5G VoNR (Voice over NR), a 5G voice solution, ultra-HD video calls, 5G video customer service, intelligent translation, screen sharing, remote collaboration, and AR-powered fun calls, providing users with a visual, multimedia, and highly perceptual ultra-HD calling experience.

[0005] Referring to Figure 1, one approach to implementing new 5G calls is to add an IMS (IP Multimedia Subsystem) DC (Data Channel) in addition to the traditional voice call audio and video streaming channels. This allows for the transmission of arbitrary media—pictures, audio, video, menus, emoticons, location, AR (Augmented Reality) / VR (Virtual Reality)—between the terminal and the network to implement various services. To enhance user experience, a signaling monitoring system is required to monitor key IMSDC data service operation indicators in real time, providing early warning and mitigation of network risks, and rapidly localizing sudden faults.

[0006] A straightforward method for monitoring IMSDC data services is to collect IMSDC data packets transmitted between terminals and the network and perform deep packet analysis. However, for security reasons, carriers encrypt IMSDC data packets transmitted between terminals and the network. Signaling monitoring systems are unable to decrypt these encrypted packets, making IMSDC service monitoring impossible. Therefore, how to monitor IMSDC data services in encrypted scenarios is a pressing issue.

[0007] Summary of the Invention

[0008] The main purpose of this application is to provide a data acquisition and processing method, device, electronic device and readable storage medium, aiming to solve the technical problem of how to monitor IMSDC data services in an IMSDC encryption scenario.

[0009] To achieve the above-mentioned purpose, the present application provides a data collection and processing method, including the following steps: collecting IMSDC data transmitted by the target transmission segment in the current service interaction process, wherein 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; obtaining the target service layer key information identified based on the IMSDC data, and generating the target XDR information corresponding to the current service interaction process according to the target service layer key information.

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

[0011] 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 on the memory and runnable on the processor, and when the data acquisition and processing program is executed by the processor, it implements the data acquisition and processing method as described above.

[0012] In addition, to achieve the above-mentioned purpose, the present application also provides a computer-readable storage medium, on which a data acquisition and processing program is stored. When the data acquisition and processing program is executed by a processor, the data acquisition and processing method as described above is implemented. 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 following briefly introduces the drawings required for use in the embodiments or the description of the prior art. 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 is a schematic diagram of the IMSDC channel of the 5G new call network;

[0015] FIG2 is a flow chart of a first embodiment of the data collection and processing method of the present application;

[0016] FIG3 is a schematic diagram of a transmission protocol stack for IMSDC data in an embodiment of the present application;

[0017] FIG4 is a schematic diagram of a deployment scenario of an IMSDC signaling monitoring device according to an embodiment of the present application;

[0018] FIG5 is a module processing flow chart of an IMSDC signaling monitoring device according to an embodiment of the present application;

[0019] FIG6 is a processing flow chart of an XDR synthesis module in an embodiment of the present application;

[0020] FIG7 is a schematic diagram of a BDC requesting data transmission in an embodiment of the present application;

[0021] FIG8 is a schematic diagram of ADC request data transmission carried by JSON initiated by a terminal in one embodiment of the present application;

[0022] FIG9 is a schematic diagram of ADC request data transmission carried by a JSON bearer initiated by a service AS / VONR+ capable network element in an embodiment of the present application;

[0023] FIG10 is a flowchart illustrating an identification flow of an IMSDC request response signaling in an embodiment of the present application;

[0024] FIG11 is a flowchart illustrating the identification of the main service type and sub-service type of DC request signaling in one embodiment of the present application;

[0025] FIG12 is a schematic diagram of the functional modules of the data acquisition and processing device according to an embodiment of the present application;

[0026] FIG13 is a schematic diagram of the hardware structure of the electronic device involved in the embodiment of the present application.

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

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

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

[0030] 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 various components under a certain specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indication will also change accordingly.

[0031] In this application, unless otherwise specified or limited, the terms "connection" and "fixation" should be understood in a broad sense. For example, "fixation" can mean fixed connection, detachable connection, or integration; mechanical connection or electrical connection; direct connection or indirect connection through an intermediate medium; internal communication between two elements or interaction between two elements, unless otherwise specified. For those skilled in the art, the specific meanings of the above terms in this application can be understood according to specific circumstances.

[0032] In addition, the descriptions of "first", "second", etc. in this application are for descriptive purposes only and should not be understood as indicating or implying their relative importance or implicitly indicating the number of the technical features indicated. Therefore, the features defined as "first" or "second" may explicitly or implicitly include at least one of such features. In addition, the technical solutions between the various embodiments can be combined with each other, but this must be based on the fact that they can be implemented by ordinary technicians in this field. 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.

[0033] Referring to Figure 1, one approach to implementing new 5G calls is to add an IMS (IP Multimedia Subsystem) DC (Data Channel) in addition to the traditional voice call audio and video streaming channels. This allows for the transmission of arbitrary media—pictures, audio, video, menus, emoticons, location, AR (Augmented Reality) / VR (Virtual Reality)—between the terminal and the network to implement various services. To enhance user experience, a signaling monitoring system is required to monitor key IMSDC data service operation indicators in real time, providing early warning and mitigation of network risks, and rapidly localizing sudden faults.

[0034] A straightforward method for monitoring IMSDC data services is to collect IMSDC data packets transmitted between terminals and the network and perform deep packet analysis. However, for security reasons, carriers encrypt IMSDC data packets transmitted between terminals and the network. Signaling monitoring systems are unable to decrypt these encrypted packets, making IMSDC service monitoring impossible. Therefore, how to monitor IMSDC data services in encrypted scenarios is a pressing issue.

[0035] Based on this, an embodiment of the present application provides a data acquisition and processing method, with reference to Figure 2, which is a flow chart of an embodiment of a data acquisition and processing method of the present application. In this embodiment, the data acquisition and processing method includes the following steps.

[0036] Step S100: collecting IMSDC data transmitted in a target transmission segment in a current service interaction process.

[0037] In this embodiment, the process type of the current service interaction process is a service request process or a service response process.

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

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

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

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

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

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

[0044] 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).

[0045] Those skilled in the art will understand that, as shown in FIG3 , when a terminal sends DC service layer data to a service AS or a VONR+ capability network element (i.e., a 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 off the DC channel protocol stack to retrieve 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 the 5G new call capability network element needs to send DC service layer data to the terminal, the DC service layer data is first encapsulated and sent to the VONR+ media plane (i.e., the 5G new call media plane) using the HTTP / 2 protocol stack. After receiving the HTTP / 2 data, the VONR+ media plane strips off the HTTP / 2 protocol stack to retrieve 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.

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

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

[0048] Exemplarily, the target business layer key information includes at least one of the following:

[0049] The first service layer key information of the service request process in the current service interaction process identified based on the IMSDC data,

[0050] Second service layer key information of the service response process in the current service interaction process identified based on the IMSDC data.

[0051] In order to better achieve the purpose of effectively monitoring the IMSDC 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.

[0052] In this embodiment, the current business interaction process is generally a request-response mode, where 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 a business response process corresponding to the business request process. Of course, those skilled in the art will understand that in some cases, 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.

[0053] Exemplarily, the first service layer key information includes at least service type information. In one embodiment, the service type information includes main service type information and sub-service type information. In another embodiment, the service type information includes only main service type information. It will be readily understood that the service type information will adapt to different specific service interaction types, and this embodiment does not impose any specific limitations thereon.

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

[0055] In a possible implementation, the step of acquiring target service layer key information identified based on the IMSDC data includes the following steps.

[0056] Step A10: Acquire the first service layer key information identified based on the IMSDC data, and count the cumulative duration from the time the first service layer key information is acquired.

[0057] 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 IMSDC data.

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

[0059] This embodiment obtains the first business layer key information identified based on IMSDC 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. This allows this embodiment to set a preset time threshold through a timer, and automatically trigger 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. This effectively supports 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.

[0060] 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 the following steps.

[0061] Step B10: If the second business layer key information is obtained before the accumulated time reaches the preset time threshold, the first business layer key information and the second business layer key information are used as target business layer key information.

[0062] 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, further improving the robustness of the data collection and processing method of the embodiment of the present application.

[0063] In order to help understand the business interaction scenario applied by the data collection and processing method of the embodiment of the present application, a business interaction scenario of a specific embodiment is listed. In this embodiment, as shown in Figure 4, Figure 4 shows the deployment location of the signaling monitoring device in the 5G new call network. It can be seen that the signaling monitoring device is not a direct participant in the network communication. It only uses the splitting equipment to perform optical replication on 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.

[0064] As shown in Figure 3, the 5G New Call NF (Network Function) involved in DC data exchange between the terminal and the 5G New Call Network includes the VONR+ (Enhanced Voice over NR, 5G+ Voice Solution) media plane, VONR+ capability network element, and service AS (Application Server). 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) / DTLS (Datagram Transport Layer Security) / UDP (User Datagram Protocol), where DTLS is responsible for encrypting the carried DC data. DC service layer data between the VONR+ media plane and the service AS / VONR+ capability network element is encapsulated using the HTTP / 2 (Hypertext Transfer Protocol Version 2) and TCP (Transmission Control Protocol) protocol stack. This part is typically deployed in the core network's trusted resource pool and is secure and does not require encryption.

[0065] That is, the applicant found 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 transmissions, and the DC service layer data of 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 IMSDC 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 DC data service monitoring.

[0066] 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 IMSDC data between the terminal and the VONR+ media plane is encrypted, it makes it impossible to monitor the IMSDC data service. The technical solution of the embodiment of the present application is to collect the IMSDC 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 IMSDC data. , wherein the target business layer key information includes the first business layer key information of the business request process, and then generates the target XDR information corresponding to the current business interaction process based on the target business layer key information, so that in the IMSDC channel encryption scenario, the embodiment of the present application utilizes the IMSDC (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), thereby effectively realizing the monitoring of IMSDC data services, thereby effectively solving the technical problem of how to realize the monitoring of IMSDC data services in the IMSDC encryption scenario.

[0067] Exemplarily, after the step of generating target XDR information corresponding to the current service interaction process, the method further includes the following steps.

[0068] Step C10: Send the target XDR information to a third-party application.

[0069] In this embodiment, before sending the target XDR information corresponding to the current business interaction process to the third-party application, it can be encoded using 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".

[0070] 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 the first NF (Network Function) unit, and the third-party application may be a second NF unit that performs business interaction with the first NF unit. In another example, the execution subject of the embodiment of the present application is the first signaling interface device, and the third-party application may be a second signaling interface device that performs business interaction with the first signaling interface. In another example, the execution subject of the embodiment of the present application is the first electronic device, and the third-party application may be a second electronic device that performs business interaction with the first electronic device. This embodiment does not make specific limitations on this.

[0071] 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 the IMSDC (unencrypted) data transmitted between the 5G new call media plane and the 5G new call capability network element / service AS to monitor the IMSDC data service.

[0072] Based on the above-mentioned first embodiment of the present application, a second embodiment of the data collection and processing method of the present application is proposed, and the step of collecting the IMSDC data transmitted by the target transmission segment in the current service interaction process includes the following steps.

[0073] Step D10: collecting HTTP / 2 signaling transmitted in the target transmission segment in the current service interaction process.

[0074] Step D20: Identify and filter the target DC signaling that carries DC service layer data from the HTTP / 2 signaling.

[0075] Step D30: Determine the IMSDC data transmitted in the target transmission segment in the current service interaction process according to the target DC signaling.

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

[0077] The step of determining the IMSDC data transmitted in the target transmission segment in the current service interaction process according to the target DC signaling includes the following steps.

[0078] Step E10: decode the HEADER frame and DATA frame of the target DC signaling to obtain DC service layer data, and use the decoded DC service layer data as the IMSDC data transmitted in the target transmission segment in the current service interaction process.

[0079] 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 IMSDC data transmitted in the target transmission segment in the current service interaction process based on the decoded DC service layer data.

[0080] In order to help understand the technical concept or technical principle of this embodiment, a signaling monitoring device of a specific embodiment is listed. For example, when the IMSDC channel is encrypted, the data acquisition and processing device in the embodiment of the present application collects IMSDC data transmitted between the VONR+ media plane and the service AS / VONR+ capability network element, and 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.

[0081] As shown in Figure 5, the signaling monitoring device of this embodiment mainly consists 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 and response identification, service type identification, key information extraction and storage, and XDR synthesis; the XDR distribution module distributes XDRs to third parties.

[0082] 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 data needs to be filtered out.

[0083] The XDR synthesis module is set to: 1) decode the HEADER frame and DATA frame of the HTTP / 2 signaling that carries the DC business 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 business type and sub-business type of this business 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 business layer and save it to the memory database; 4) for the response signaling, the query to the memory database is successful, and the key information of the DC business layer carried by the response signaling is also extracted and saved in the database, and then synthesized to output XDR.

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

[0085] 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 this application and do not constitute a limitation of this application. More simple transformations based on the technical concepts should all be within the scope of protection of this application.

[0086] 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 the following steps.

[0087] Step F10: Identify 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.

[0088] 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 IMSDC data.

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

[0090] The first service layer key information includes at least service type information. In one embodiment, the service type information includes main service type information and sub-service type information. In another embodiment, the service type information includes only main service type information. The service type information may vary adaptively depending on the specific service interaction type and is not specifically limited in this embodiment.

[0091] The embodiment of the present application identifies the process type of the current business 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 business request process, identifies the first business layer key information according to the IMSDC data, wherein the first business layer key information includes main business type information and sub-business type information, and saves the first business 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 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 first business layer key information in the IMSDC (non-encrypted) data.

[0092] 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 the following steps.

[0093] 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 IMSDC data.

[0094] In this embodiment, after identifying the second business layer key information, 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 queried preset target node.

[0095] 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 the following steps: 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 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.

[0096] The second service layer key information at least includes response identification information of the response signaling.

[0097] 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 IMSDC (non-encrypted) data.

[0098] 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, which is a processing flow chart of the XDR synthesis module in an embodiment of the present application, including the following steps.

[0099] S10: Decode the HTTP / 2 HEADER frame and DATA frame, which will not be described in detail here.

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

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

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

[0103] In this embodiment, for BDC (Bootsrap DC) data service interaction, the business party that initiates the DC request is only the terminal. As shown in Figure 7, the terminal initiates a BDC request, encapsulates and encrypts the DC service layer HTTP / 1.1 data using 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 splices it with the pre-stored service AS / VONR+ capability network element to receive DC data {appUrl} together {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. If the HTTP / 1.1 signaling carries a message body, it is encapsulated as an HTTP / 2 DATA frame, and an HTTP / 2 signaling is constructed and sent to the service AS / VONR+ capability network element.

[0104] 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, as shown in Figure 8. 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 / 2DATA 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 to construct an HTTP / 2 signaling and send it to the service AS / VONR+ capability network element. If the service AS / VONR+ capability network element initiates an ADC request, as shown in Figure 9, 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 encapsulated with other header fields as a HEADER frame, and the JSON data is encapsulated as the HTTP / 2 DATA frame. The HTTP / 2 signaling is constructed and sent to the VONR+ media plane. The VONR+ media plane extracts the JSON data in the DATA frame, and then encapsulates and encrypts it with the DC protocol stack and sends it to the terminal.

[0105] As can be seen from the above, the ADC request or 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.

[0106] As shown in Figure 10, if the decoded HEADER frame contains one of the three fields: :path, :method, and :scheme, it can be determined to be an HTTP / 2 request signaling, and the DC data it carries can be determined to be a DC request signaling. If the decoded HEADER frame contains the header field: :status, it can be determined to be an HTTP / 2 response signaling, and the DC data it carries can be determined to be a DC response signaling. All of the above fields are not decoded and require further identification.

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

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

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

[0110] As shown in Figure 11, if the BDC or service layer uses HTTP / 1.1 encoding for the ADC request, the main service type can be identified by matching the :path with the preset key strings for identifying each main service type. If the main service type identification fails, the signaling is discarded. If the service layer uses JSON-encoded ADC requests, according to the innerUrl parameter encoding rules for 5G new call DC service interactions, the main service type can be identified by removing the trailing request from the innerUrl and matching it with the preset key strings for identifying each main service type. If the match is successful, the main service type is obtained. If the match fails, the signaling is discarded. Some JSON-encoded ADC processes need to continue identifying sub-service types after identifying the main service type. This can be done by matching the bussType carried in the body parameter with the key strings for identifying each sub-service type. If the sub-service type identification fails, the signaling is discarded.

[0111] Take the process of starting and stopping the service function 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 DC data and finds that it is carried by HTTP / 2 request signaling or decodes to obtain innerUrl and the innerUrl ends with request, then it can be identified as request signaling; if the innerUrl is " / service / " after removing request, then the main business type of this signaling interaction is the user request to start and stop the service function. Furthermore, 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.

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

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

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

[0115] S70: If the node query is successful, the DC key information (ie, the second service layer key information) such as the response code (ie, a response identification information) carried in the response signaling is extracted and saved in the querying node.

[0116] S80: Receiving a response indicates that a DC business interaction is completed. At this time, an XDR can be generated, key information stored in the database node can be filled into the XDR, and sent to the XDR distribution module. At the same time, the database node can be released.

[0117] 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 this application and does not constitute a limitation of this application. More simple transformations based on this technical concept should all be within the scope of protection of this application.

[0118] In addition, an embodiment of the present application further proposes a data acquisition and processing device. Referring to FIG. 12 , FIG. 12 is a schematic diagram of functional modules of an embodiment of a data acquisition and processing device of the present application.

[0119] In this embodiment, the data acquisition and processing device includes the following components.

[0120] The data cleaning module 10 is configured to collect IMSDC data transmitted in the target transmission segment in the current service interaction process, where 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.

[0121] The XDR synthesis module 20 is configured to obtain target service layer key information identified based on the IMSDC data, and generate target XDR information corresponding to the current service interaction process according to the target service layer key information.

[0122] In some embodiments, the target business layer key information includes at least one of the following: first business layer key information of the business request process in the current business interaction process identified based on the IMSDC data, and second business layer key information of the business response process in the current business interaction process identified based on the IMSDC data.

[0123] In some embodiments, the data cleaning module 10 is also configured to: collect HTTP / 2 signaling transmitted in the target transmission segment in the current business interaction process; identify and filter out the target DC signaling that carries DC business layer data from the HTTP / 2 signaling; and determine the IMSDC data transmitted in the target transmission segment in the current business interaction process based on the target DC signaling.

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

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

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

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

[0128] 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 application concept. The technical details not fully described in this embodiment can be found in the embodiments of the above-mentioned data acquisition and processing method. This embodiment has the same beneficial effects as the embodiments of the data acquisition and processing method, and will not be repeated here.

[0129] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, i.e., they may be located in one place or distributed across multiple network units. Some or all of the modules may be selected based on actual needs to achieve the objectives of this embodiment.

[0130] In addition, an embodiment of the present application further provides an electronic device, with reference to Figure 13, which is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application. As shown in Figure 13, 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 implement 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 user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may 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-Volatile Memory, NVM), such as a disk storage. The memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0131] Those skilled in the art will appreciate that the structure shown in FIG13 does not limit the electronic device and may include more or fewer components than shown, or combine certain components, or arrange the components differently. As shown in FIG13 , 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 and processing program.

[0132] In the electronic device shown in Figure 13, 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.

[0133] The device proposed in this embodiment and the data acquisition and processing method proposed in the above embodiment belong to the same inventive concept. 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.

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

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

[0136] As used herein, the terms "comprises," "comprising," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or system that includes a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or system. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, method, article, or system that includes the element.

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

[0138] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course, by hardware, but in many cases the former is a better embodiment. Based on this 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 enabling an electronic device to execute the methods described in each embodiment of the present application.

[0139] The above are only some 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, 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.

2. The data collection and processing method according to claim 1, wherein: 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, wherein: The first service layer key information includes at least service type information.

4. The data acquisition and processing method according to claim 2, wherein: The second service layer key information at least includes response identification information.

5. The data acquisition and processing method according to claim 1, wherein: 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, wherein: 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, wherein: 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, comprising: 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, comprising: 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, wherein: 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