| text | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message quality indicators and trends. Trigger event: P2P poor quality indicator data query. Functional process: Query the details of P2P poor quality index data. Sub-process description: output the detailed query results of P2P poor quality indicator data. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Trigger event: export of chatbot terminal rule configuration data with poor quality. Functional process: Chatbot poor quality terminal rule configuration data export. Sub-process description: read chatbot poor quality terminal rule configuration export template. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, monitoring of 5G message indicators. Trigger event: Chatbot business indicator monitoring data export. Functional process: Chatbot business indicator monitoring data export. Sub-process description: read the Chatbot business indicator monitoring export template. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G messaging service indicators, key indicators and trends of business development. Trigger event: 5G message user number indicator data query. Functional process: Query the details of the 5G message user number indicator data. Sub-process description: output the detailed query results of the number of 5G news users index data. Data movement type: X." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice EPSFB call duration analysis data export. Functional process: 5G voice EPSFB call duration analysis data export. Sub-process description: Read the 5G voice EPSFB call duration analysis export template. Data movement type: R." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: VOLTE poor voice quality delay rule configuration data query. Function process: VOLTE poor voice quality delay rule configuration data list query. Sub-process description: output the query result of VOLTE voice quality delay rule configuration data list. Data movement type: X." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop analysis of indicators. Trigger event: Export of EPSFB network access analysis data. Functional process: EPSFB network access analysis data export. Sub-process description: input EPSFB network access analysis export request. Data movement type: E." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: Deletion of VONR voice quality delay rule configuration data. Functional process: Delete the configuration data of VONR voice quality delay rule. Sub-process description: Return the deletion result. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, analysis of key factors of poor quality business indicators. Trigger event: data export of key factors of poor business development quality. Functional process: Data export of key factors of poor business development quality. Sub-process description: read the data of key factors of poor business development quality. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: Intelligent monitoring of 5G message indicators, multi-dimensional aggregation and presentation. Trigger event: Query of aggregated dimension data with poor terminal quality. Functional process: Query the details of aggregated dimension data with poor terminal quality. Sub-process description: Input the request for querying the details of aggregated dimension data with poor quality in the terminal. Data movement type: E." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, multi-dimensional aggregation of indicators. Trigger event: Export of aggregated indicator data for message group sending. Functional process: export of aggregated indicator data for message group sending. Sub-process description: read the export template of aggregate indicators for message group sending. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: VONR poor voice quality delay rule configuration data modification. Functional process: VONR poor voice quality delay rule configuration data modification. Sub-process description: Update the configuration data of VONR voice quality delay rule. Data movement type: W." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message indicator system. Trigger event: Generate business development indicator analysis data table. Functional process: business development index analysis data table generation (GP business library). Sub-process description: Generate business development indicators and analyze abnormal data log writing. Data movement type: W." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G messaging service requirements, analysis and forecasting of 5G messaging terminal numbers. Trigger event: 5G message terminal analysis data export. Functional process: 5G message terminal analysis data export. Sub-process description: export 5G message terminal analysis data. Data movement type: X." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice VONR call duration analysis data collection. Functional process: 5G voice VONR call duration analysis data conversion. Sub-process description: Save 5G voice VONR call duration analysis data conversion data. Data movement type: W." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business rule configuration. Trigger event: Registration class poor quality rule configuration data export. Functional process: registration class poor quality rule configuration data export. Sub-process description: Export the configuration data of registration class poor quality rules. Data movement type: X." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, early warning of 5G voice indicators. Trigger event: EPSFB voice indicator warning data deletion. Functional process: EPSFB voice indicator warning data deletion. Sub-process description: update EPSFB voice index warning data. Data movement type: W." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, early warning of 5G voice indicators. Trigger event: VOLTE voice indicator warning data added. Function process: VOLTE voice indicator warning data is added. Sub-process description: read VOLTE voice indicator warning data. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: Intelligent monitoring of 5G message indicators, multi-dimensional aggregation and presentation. Trigger event: NE fallback aggregation dimension data export. Functional process: Network element fallback aggregation dimension data export. Sub-process description: read the data of the NE fallback aggregation dimension. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, configuration of 5G message demand forecasting rules. Trigger event: UP2.4 terminal P2P SMS prediction rule configuration data modification. Functional process: UP2.4 terminal P2P SMS prediction rule configuration data modification. Sub-process description: Return the modification result. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, 5G message quality terminal analysis. Trigger event: P2P message index data export of poor quality terminals. Functional process: Export the P2P message index data of poor quality terminals. Sub-process description: read the P2P message index data of poor-quality terminals. Data movement type: R." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: VONR intelligent analysis of calling delay, poor quality of terminal delay. Trigger event: Export of terminal overall VONR delay data. Functional process: export the overall VONR delay data of the terminal. Sub-process description: Read the overall VONR delay data of the terminal. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G news indicators, city ranking and trend analysis. Trigger event: data query of business indicators, city trend analysis. Functional process: Detailed query of business indicators, prefecture and city trend analysis data. Sub-process description: Output the detailed query results of business indicators, city trend analysis data. Data movement type: X." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop summary of service quality. Trigger event: VONR registration class quality closed-loop data export. Functional process: VONR registration class quality closed-loop data export. Sub-process description: Input VONR registration class quality closed-loop export request. Data movement type: E." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G news indicators, city ranking and trend analysis. Trigger event: data query of business indicators, city trend analysis. Functional process: Detailed query of business indicators, prefecture and city trend analysis data. Description of the sub-process: Input the inquiry request for the details of the business indicator city trend analysis data. Data movement type: E." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, early warning of 5G voice indicators. Trigger event: VOLTE voice indicator warning data added. Function process: VOLTE voice indicator warning data is added. Sub-process description: Input the new request for VOLTE voice index warning data. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G messaging service indicators, key indicators and trends of business development. Trigger event: Data export of key indicators of 5G message business. Functional process: export key indicator data of 5G message business. Sub-process description: export the key indicator data of 5G message business. Data movement type: X." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality network element analysis. Triggering event: Query for registration index data of poor quality NEs. Functional process: Query the list of registered index data of poor-quality network elements. Sub-process description: Read the list information of poor-quality network element registration index data. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, monitoring of 5G message indicators. Trigger event: business indicator monitoring data query. Functional process: query the details of business indicator monitoring data. Sub-process description: Output the detailed query results of business indicator monitoring data. Data movement type: X." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice VOLTE call duration analysis data query. Function process: 5G voice VOLTE call duration analysis data list query. Sub-process description: output 5G voice VOLTE call duration analysis data list query results. Data movement type: X." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality cell analysis. Trigger event: Inquiry of call quality indicator data in poor quality cells. Functional process: Query the call quality index data list of poor quality cells. Sub-process description: Output query results of call quality index data list of poor quality cells. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, configuration of 5G message demand forecasting rules. Trigger event: UP2.4 end user number prediction rule configuration data export. Functional process: UP2.4 end user number prediction rule configuration data export. Sub-process description: Read the UP2.4 terminal user number prediction rule configuration export template. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, 5G message quality terminal analysis. Trigger event: Export of poor-quality terminal registration indicator data. Functional process: Export of poor-quality terminal registration index data. Sub-process description: read the poor-quality terminal registration index data. Data movement type: R." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: IMS domain latency index data table is generated. Functional process: IMS domain delay index data statistics (HBASE library). Sub-process description: Save the statistical results of IMS domain delay index data to the HBASE library. Data movement type: W." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, early warning of 5G voice indicators. Trigger event: VONR voice indicator warning data deletion. Functional process: VONR voice indicator warning data deletion. Sub-process description: Update VONR voice indicator warning data. Data movement type: W." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message quality indicators and trends. Trigger event: Data query of poor quality indicators for business development. Functional process: Query the data list of poor quality indicators for business development. Sub-process description: Input query request for data list of poor quality indicators of business development category. Data movement type: E." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G news indicators, city ranking and trend analysis. Trigger event: Query the ranking data of registered cities and cities. Functional process: Query the details of the ranking data of registered index cities. Sub-process description: Read the detailed data of the ranking of the registration index cities. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice VONR call duration analysis data collection. Functional process: 5G voice VONR call duration analysis data collection. Sub-process description: Input 5G voice VONR call duration analysis data collection request. Data movement type: E." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, city ranking and trend of VoNR calling delay. Trigger event: EPSFB time delay ranking and trend data query. Functional process: query the ranking and trend data details of EPSFB delay. Sub-process description: output the ranking and trend data query results of EPSFB delay. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business analysis. Trigger event: Generation of poor-quality P2P service data tables. Functional process: poor quality P2P business data statistics (HBASE library). Sub-process description: read poor-quality P2P business data. Data movement type: R." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality terminal analysis. Triggering event: data query for the analysis data of poor-quality terminal connection indicators. Functional process: Query the details of the analysis data of poor-quality terminal connection indicators. Sub-process description: Input a request for querying the details of the analysis data of the poor-quality terminal connection indicator factors. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, monitoring of 5G message indicators. Trigger event: register indicator monitoring data query. Functional process: Query the details of registration indicator monitoring data. Sub-process description: Enter a query request for registration indicator monitoring data details. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business rule configuration. Trigger event: File transfer class poor quality rule configuration data export. Functional process: file transfer class poor quality rule configuration data export. Sub-process description: read the configuration data of the poor quality rule of the file transfer class. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G news indicators, city ranking and trend analysis. Trigger event: Query the ranking data of registered cities and cities. Functional process: query the list of ranking data of registered index cities. Sub-process description: Input the query request for the ranking data list of registered index prefectures and cities. Data movement type: E." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: EPSFB poor voice quality connection rule configuration data modification. Functional process: Modify the configuration data of EPSFB poor voice quality connection rules. Sub-process description: Return the modification result. Data movement type: X." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice service quality closed-loop management, voice service quality monitoring closed-loop presentation. Trigger event: EPSFB voice service quality monitoring indicator data display. Functional process: EPSFB voice service quality monitoring indicator data display. Sub-process description: read EPSFB voice service quality monitoring indicator data. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, monitoring of 5G message indicators. Trigger event: Group sending indicator monitoring data query. Functional process: query the group sending index monitoring data list. Sub-process description: Enter the query request for the monitoring data list of group sending indicators. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, monitoring of 5G message indicators. Trigger event: register indicator monitoring data query. Functional process: register indicator monitoring data list query. Sub-process description: Read the registration indicator monitoring data list information. Data movement type: R." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice service demand intelligent forecasting, 5G voice demand forecasting rule configuration. Trigger event: VOLTE voice demand forecast configuration data query. Functional process: VOLTE voice demand forecast configuration data list query. Sub-process description: read VOLTE voice demand forecast configuration data list information. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Trigger event: The configuration data of the chatbot poor quality terminal rule is added. Functional process: Added chatbot terminal rule configuration data with poor quality. Sub-process description: read chatbot poor quality terminal rule configuration data. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G messaging service requirements, early warning of 5G messaging performance indicators. Trigger event: 5G message user & terminal early warning data query. Functional process: 5G message user & terminal early warning data list query. Sub-process description: Read 5G message user & terminal early warning data list information. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G messaging service indicators, key indicators and trends of business development. Trigger event: 5G message user number indicator data query. Functional process: Query the list of 5G message user number index data. Sub-process description: Enter the query request for the list of 5G message user number index data. Data movement type: E." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice service quality closed-loop management, voice service quality monitoring closed-loop presentation. Trigger event: VOLTE voice service quality monitoring indicator data display. Functional process: VOLTE voice service quality monitoring indicator data display. Sub-process description: read VOLTE voice service quality monitoring index data. Data movement type: R." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: VONR voice quality poor registration rule configuration data is added. Function process: The configuration data of VONR poor voice quality registration rules is added. Sub-process description: Update the configuration data of VONR poor voice quality registration rules. Data movement type: W." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, configuration of indicator monitoring rules. Trigger event: P2P indicator monitoring rule configuration data modification. Functional process: P2P indicator monitoring rule configuration data modification. Sub-process description: update P2P indicator monitoring rule configuration data. Data movement type: W." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: VOLTE voice quality is poor and the connection rule configuration data is deleted. Functional process: Delete the connection rule configuration data for poor VOLTE voice quality. Sub-process description: Delete the connection rule configuration data of VOLTE poor voice quality. Data movement type: W." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop summary of service quality. Trigger event: EPSFB call quality quality closed-loop data table generation. Functional process: EPSFB call quality closed-loop data table generation (GP service library). Sub-process description: generate EPSFB call quality closed-loop data table. Data movement type: W." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G messaging service indicators, key indicators and trends of business development. Trigger event: 5G message terminal count indicator data export. Functional process: 5G message terminal number indicator data export. Sub-process description: export 5G message terminal number index data. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, analysis of indicator cause values. Trigger event: Data export of group sending failure reason value. Functional process: data export of group sending failure cause value. Sub-process description: return the export result. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G news indicators, city ranking and trend analysis. Trigger event: data query for file transfer indicators, city trend analysis. Functional process: detailed query of file transfer indicators, city trend analysis data. Sub-process description: Input file transfer index city trend analysis data details query request. Data movement type: E." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Triggering event: Export of configuration data for bad registration terminal rules. Functional process: export the rule configuration data for terminals with poor registration quality. Sub-process description: Input the request for exporting the rule configuration of the terminal with poor registration quality. Data movement type: E." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business analysis. Trigger event: Export of poor-quality mass-sending business data. Functional process: Export of poor-quality mass-sending business data. Sub-process description: return the export result. Data movement type: X." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: Deletion of VOLTE voice quality delay rule configuration data. Function process: Deletion of VOLTE voice quality delay rule configuration data. Sub-process description: Delete the VOLTE voice quality delay rule configuration data. Data movement type: W." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop analysis of indicators. Trigger event: EPSFB network access analysis data query. Functional process: EPSFB network connection analysis data list query. Sub-process description: Output EPSFB network access analysis data list query results. Data movement type: X." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G voice service demand, 5G voice demand and predicted city rankings and trends. Trigger event: 5G voice VONR call duration prediction analysis data query. Functional process: 5G voice VONR call duration prediction analysis data query. Sub-process description: Read the detailed data of 5G voice VONR call duration prediction analysis. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, multi-dimensional aggregation of indicators. Trigger event: Messaging analysis (P2P) data export. Functional process: message sending and receiving analysis (P2P) data export. Sub-process description: read messaging analysis (P2P) data. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: EPSFB poor voice quality registration rule configuration data is added. Functional process: The EPSFB poor voice quality registration rule configuration data is added. Sub-process description: return the newly added result of EPSFB poor voice quality registration rule configuration data. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business analysis. Trigger event: Generation of poor quality load indicator data table. Functional process: generation of poor quality load index data table (GP business library). Sub-process description: Generate and write abnormal data logs of poor quality load indicators. Data movement type: W." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message quality indicators and trends. Trigger event: Data export of poor quality indicators for business development. Functional process: Data export of poor quality indicators for business development. Sub-process description: Input the request for exporting business development category poor quality indicators. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, 5G message quality terminal analysis. Trigger event: bad-quality terminal chatbot business data query. Functional process: Query the details of chatbot business data of poor-quality terminals. Sub-process description: read the business details data of the poor-quality terminal chatbot. Data movement type: R." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: VONR poor voice quality registration rule configuration data query. Functional process: Query the configuration data list of VONR poor voice quality registration rules. Sub-process description: Output the query result of the configuration data list of VONR poor voice quality registration rules. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, configuration of 5G message demand forecasting rules. Trigger event: UP2.4 terminal P2P SMS prediction rule configuration data is added. Function process: UP2.4 terminal P2P SMS prediction rule configuration data is added. Sub-process description: update UP2.4 terminal P2P short message prediction rule configuration data. Data movement type: W." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality network element analysis. Trigger event: Inquiry of connection index data of poor-quality NEs. Functional process: Query the data list of connection indicators of poor-quality network elements. Description of the sub-process: Input the query request for the data list of connectivity indicators of network elements with poor quality. Data movement type: E." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: VONR intelligent analysis of calling delay, poor quality of cell delay. Trigger event: Export of the overall VONR delay data of the cell. Functional process: export the overall VONR delay data of the cell. Sub-process description: Read the overall VONR delay derivation template of the cell. Data movement type: R." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G voice service demand, 5G voice demand and predicted city rankings and trends. Trigger event: 5G voice EPSFB call duration prediction analysis data export. Functional process: 5G voice EPSFB call duration prediction analysis data export. Sub-process description: read 5G voice EPSFB call duration prediction and analysis data. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G messaging service requirements, early warning of 5G messaging performance indicators. Trigger event: 5G message user & terminal early warning data table generation. Functional process: 5G message user & terminal early warning data table generation (GP business library). Sub-process description: Timely trigger the task of generating 5G message user & terminal early warning data table. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: Intelligent monitoring of 5G message indicators, multi-dimensional aggregation and presentation. Trigger event: prefecture-city registration aggregation dimension data query. Functional process: Query the details of the aggregation dimension data of prefecture-city registration. Sub-process description: output the detailed query results of prefecture-city registration aggregation dimension data. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business rule configuration. Trigger event: The registration class poor quality rule configuration data is added. Functional process: The configuration data of the registration class poor quality rule is added. Sub-process description: read the configuration data of registration class poor quality rules. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message indicator system. Trigger event: export of business development indicator analysis data. Functional process: business development indicators analysis data export. Sub-process description: Read the business development indicator analysis export template. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, analysis of indicator cause values. Trigger event: P2P failure reason value data query. Functional process: P2P failure reason value data list query. Sub-process description: Input the P2P failure reason value data list query request. Data movement type: E." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business analysis. Trigger event: Export of poor-quality P2P service data. Functional process: Export of poor-quality P2P business data. Sub-process description: read the export template of poor-quality P2P services. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G messaging service indicators, key indicators and trends of business development. Trigger event: 5G message sending key indicator data query. Functional process: 5G message sending key indicator data list query. Sub-process description: Output 5G message sending key indicator data list query results. Data movement type: X." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, early warning of 5G voice indicators. Trigger event: VONR voice indicator warning data deletion. Functional process: VONR voice indicator warning data deletion. Sub-process description: Return the deletion result. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message quality indicators and trends. Trigger event: export of file transfer quality indicator data. Functional process: file transfer class poor quality indicator data export. Sub-process description: Input file transfer class poor quality index export request. Data movement type: E." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: core network latency index data collection. Functional process: core network delay index data collection interface. Sub-process description: Return the core network latency index data. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, drill-down of 5G message indicators. Trigger event: P2P message detailed list data query. Functional process: P2P message detailed list data query. Sub-process description: input P2P message detailed bill data query request. Data movement type: E." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, early warning of 5G voice indicators. Trigger event: EPSFB voice indicator warning data is added. Functional process: EPSFB voice index early warning data is added. Sub-process description: Read the rules to verify the EPSFB voice index early warning data. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G news indicators, city ranking and trend analysis. Trigger event: P2P index city trend analysis data query. Functional process: P2P index city trend analysis data list query. Sub-process description: output the query results of the P2P index city trend analysis data list. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: Intelligent monitoring of 5G message indicators, multi-dimensional aggregation and presentation. Triggering event: Community report aggregate dimension data export. Functional process: Community reporting and aggregation dimension data export. Sub-process description: export the aggregation dimension data reported by the community. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, multi-dimensional aggregation of indicators. Triggering event: querying aggregated indicator data for message group sending. Functional process: Query the details of aggregated indicator data for group message sending. Sub-process description: Read the detailed data of aggregated indicators of message group sending. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Triggering event: The modification of the configuration data of the registered poor quality terminal rule. Functional process: modify the configuration data of the registration rules for terminals with poor quality. Sub-process description: Return the modification result. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business analysis. Trigger event: Generation of poor quality file transfer business data table. Functional process: poor quality file transfer business data statistics (HBASE library). Sub-process description: Save the statistical results of poor-quality file transfer business data to the HBASE library. Data movement type: W." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, multi-dimensional aggregation of indicators. Trigger event: Messaging analysis (P2P) data export. Functional process: message sending and receiving analysis (P2P) data export. Sub-process description: export messaging analysis (P2P) data. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business analysis. Trigger event: poor quality file transfer business data query. Functional process: Query the details of poor-quality file transfer business data. Sub-process description: Input a query request for details of poor-quality file transfer business data. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, 5G message quality terminal analysis. Triggering event: Poor quality terminal group message index data query. Functional process: Query the index data list of group messages sent by poor-quality terminals. Sub-process description: Read the information of the index data list of group messages sent by poor-quality terminals. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Triggering event: The modification of the configuration data of the registered poor quality terminal rule. Functional process: modify the configuration data of the registration rules for terminals with poor quality. Sub-process description: Input a request for modifying the configuration data of the terminal rules with poor registration quality. Data movement type: E." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: export of on-delay indicator data. Functional process: Data export of on-time delay indicators. Sub-process description: export the on-delay index data. Data movement type: X." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality cell analysis. Trigger event: downloading of registration index data for poor-quality communities. Functional process: Download the registration index data of poor-quality communities. Sub-process description: Input the request for downloading the registration index data of poor-quality communities. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business rule configuration. Trigger event: The configuration data of the file transfer class poor quality rule is added. Functional process: The configuration data of the poor quality rule of the file transfer class is added. Sub-process description: Input a new request for the configuration data of the poor quality rule of the input file transfer class. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, analysis of key factors of poor quality terminal indicators. Trigger event: The core network quality is poor and the terminal information data is exported. Functional process: Export information and data of terminals with poor core network quality. Sub-process description: Read the information data of terminals with poor core network quality. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message indicator system. Trigger event: business development indicators analysis data collection. Functional process: business development indicators analysis data collection. Sub-process description: save the business development indicators analysis and collection data. Data movement type: W." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message indicator system. Trigger event: the collection of registered index analysis data. Functional process: registration index analysis data collection. Sub-process description: call the registration class index analysis data collection interface. Data movement type: X." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice VONR user number analysis data query. Functional process: Query the details of 5G voice VONR user number analysis data. Sub-process description: output the detailed query results of 5G voice VONR user number analysis data. Data movement type: X." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, early warning of 5G voice indicators. Trigger event: export of VOLTE voice indicator warning data. Functional process: VOLTE voice indicators early warning data export. Sub-process description: Read the VOLTE voice indicator warning export template. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, multi-dimensional aggregation of indicators. Trigger event: Chatbot class aggregation indicator data query. Functional process: Chatbot-like aggregation indicator data details query. Sub-process description: Output the detailed query results of Chatbot-like aggregation indicator data. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Trigger event: P2P poor quality terminal rule configuration data is added. Function process: P2P poor quality terminal rule configuration data is added. Sub-process description: Read rule verification P2P poor quality terminal rule configuration data. Data movement type: R." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: generation of on-delay index data table. Functional process: connect delay index data statistics (HBASE library). Sub-process description: read the statistical rules and perform statistical calculations on the connection delay index data. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G voice service demand, 5G voice demand and predicted city rankings and trends. Trigger event: 5G voice EPSFB user number prediction analysis data query. Functional process: 5G voice EPSFB user number prediction analysis data list query. Sub-process description: output 5G voice EPSFB user number prediction analysis data list query results. Data movement type: X." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: VONR intelligent analysis of calling delay, poor quality of cell delay. Trigger event: Cell VoNR call VoNR delay data query. Functional process: Query the details of VoNR delay data of VoNR calls in the community. Sub-process description: Input the cell VoNR call VoNR delay data query request. Data movement type: E." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, early warning of 5G voice indicators. Trigger event: EPSFB voice indicator early warning data query. Functional process: EPSFB voice indicator early warning data list query. Sub-process description: Input the EPSFB voice indicator early warning data list query request. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, monitoring of 5G message indicators. Trigger event: Export of group sending indicator monitoring data. Functional process: export of monitoring data for group sending indicators. Sub-process description: Input the group sending indicator monitoring export request. Data movement type: E." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice service demand intelligent forecasting, 5G voice demand forecasting rule configuration. Trigger event: EPSFB voice demand forecast configuration data deletion. Functional process: EPSFB voice demand forecast configuration data deletion. Sub-process description: read EPSFB voice demand forecast configuration data. Data movement type: R." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice EPSFB user number analysis data collection. Functional process: 5G voice EPSFB user number analysis data collection interface. Sub-process description: return 5G voice EPSFB user number analysis data. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G messaging service requirements, early warning of 5G messaging performance indicators. Trigger event: 5G message user & terminal early warning data table generation. Functional process: 5G message user & terminal early warning data table generation (GP business library). Sub-process description: Save the 5G message user & terminal early warning data table to the GP table library. Data movement type: W." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Trigger event: The terminal rule configuration data of poor business development quality is added. Functional process: The terminal rule configuration data of poor business development quality is added. Sub-process description: Return the new result of configuration data of terminal rules with poor business development quality. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, analysis of key factors of poor quality terminal indicators. Trigger event: Export of prefecture-level and poor-quality terminal indicator data. Functional process: Data export of prefecture-level and poor-quality terminal indicators. Sub-process description: return the export result. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business rule configuration. Trigger event: Export of configuration data for business development class poor quality rules. Functional process: business development class poor quality rule configuration data export. Sub-process description: Export the configuration data of business development class poor quality rules. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, analysis of key factors of poor quality terminal indicators. Trigger event: Query data of terminal indicators with poor granularity in prefectures and cities. Functional process: Inquiry about the details of terminal index data with poor granularity and quality in prefectures and cities. Sub-process description: Input the request for querying the details of the terminal index data with poor quality at the granularity of prefecture-level cities. Data movement type: E." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice VONR call duration analysis data export. Functional process: 5G voice VONR call duration analysis data export. Sub-process description: export 5G voice VONR call duration analysis data. Data movement type: X." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop summary of service quality. Trigger event: VONR registration class quality closed-loop data table generation. Functional process: VONR registration quality closed-loop data table generation (GP business library). Sub-process description: Generate VONR registration class quality closed-loop exception data processing. Data movement type: W." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G voice service demand, 5G voice demand and predicted city rankings and trends. Trigger event: 5G voice VONR call duration prediction analysis data export. Functional process: 5G voice VONR call duration prediction analysis data export. Sub-process description: Read the export template for 5G voice VONR call duration prediction analysis. Data movement type: R." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: VONR intelligent analysis of calling delay, poor quality of cell delay. Trigger event: export of VoNR delay data for VoNR calls in the cell. Functional process: export of VoNR delay data for cell VoNR calls. Sub-process description: Read the cell VoNR call VoNR delay derivation template. Data movement type: R." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: registration latency indicator data query. Functional process: query the registration delay index data list. Sub-process description: output the query result of the registration delay index data list. Data movement type: X." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: EPSFB poor voice quality registration rule configuration data query. Functional process: EPSFB poor voice quality registration rule configuration data list query. Sub-process description: Input EPSFB poor voice quality registration rule configuration data list query request. Data movement type: E." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, call auxiliary delay statistics. Trigger event: N26 interface delay data download. Functional process: N26 interface delay data download. Sub-process description: read the delay data of N26 interface. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice VONR call duration analysis data collection. Functional process: 5G voice VONR call duration analysis data conversion interface. Sub-process description: read 5G voice VONR talk time analysis data conversion rules. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice EPSFB call duration analysis data table is generated. Functional process: 5G voice EPSFB call duration analysis data table generation (GP service library). Sub-process description: Timing trigger the generation task of 5G voice EPSFB call duration analysis data table. Data movement type: E." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business analysis. Trigger event: data query of poor quality load indicators. Functional process: Query the details of poor quality load index data. Sub-process description: Read the detailed data of the poor quality load index. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message indicator system. Trigger event: upload of business development indicator analysis data. Functional process: business development indicators analysis data upload. Sub-process description: return the upload result. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Trigger event: Export of terminal rule configuration data with poor service development quality. Functional process: export of terminal rule configuration data with poor business development quality. Sub-process description: read the terminal rule configuration data of poor service development quality. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, drill-down of 5G message indicators. Trigger event: 5G message group sending detailed list data download. Functional process: 5G message group sending detailed list data download. Sub-process description: save the download data of 5G message group sending detailed list. Data movement type: W." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice service quality closed-loop management, voice service quality monitoring closed-loop presentation. Trigger event: VOLTE voice service quality monitoring indicator data export. Functional process: export VOLTE voice service quality monitoring index data. Sub-process description: Export VOLTE voice service quality monitoring indicator data. Data movement type: X." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice VOLTE user number analysis data collection. Functional process: 5G voice VOLTE user number analysis data collection. Sub-process description: Read the verification rules to verify the account information of the 5G voice VOLTE user number analysis data server. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice service demand intelligent forecasting, 5G voice demand forecasting rule configuration. Trigger event: VONR voice demand forecast configuration data export. Functional process: VONR voice demand forecast configuration data export. Sub-process description: Export VONR voice demand forecast configuration data. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G news indicators, city ranking and trend analysis. Trigger event: Export of file transfer indicator city trend analysis data. Functional process: file transfer indicators, city trend analysis data export. Sub-process description: Export file transfer indicators, city trend analysis data. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Trigger event: P2P poor quality terminal rule configuration data modification. Functional process: modify the configuration data of P2P poor quality terminal rules. Sub-process description: read the P2P poor quality terminal rule configuration data. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G news indicators, city ranking and trend analysis. Trigger event: data query for file transfer indicators, city trend analysis. Functional process: file transfer index city trend analysis data list query. Sub-process description: Read the list information of the file transfer index city trend analysis data list. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: Intelligent monitoring of 5G message indicators, multi-dimensional aggregation and presentation. Triggering event: The display of aggregated dimension data reported by the community. Functional process: display of aggregated dimension data reported by the community. Sub-process description: Read the aggregated dimension data reported by the community. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message quality indicators and trends. Trigger event: Data query of poor quality indicators for business development. Functional process: Query the data list of poor quality indicators for business development. Sub-process description: Output the query results of the data list of poor quality indicators of business development. Data movement type: X." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice VONR call duration analysis data collection. Functional process: 5G voice VONR call duration analysis data conversion interface. Sub-process description: Receive 5G voice VONR call duration analysis data conversion request. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, analysis of key factors of poor quality terminal indicators. Trigger event: Query data of terminal indicators with poor granularity in prefectures and cities. Functional process: Query the list of prefecture-level and poor-quality terminal indicator data. Sub-process description: Input the query request for the data list of poor-quality terminal indicators at the prefecture-level granularity. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Triggering event: Export of configuration data for bad registration terminal rules. Functional process: export the rule configuration data for terminals with poor registration quality. Sub-process description: read the configuration data of terminal rules with poor registration quality. Data movement type: R." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: EPSFB poor voice quality connection rule configuration data query. Functional process: EPSFB poor voice quality connection rule configuration data list query. Description of the sub-process: Input the EPSFB poor voice quality connection rule configuration data list query request. Data movement type: E." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G messaging service indicators, key indicators and trends of business development. Trigger event: 5G message sending key indicator data query. Functional process: 5G message sending key indicator data list query. Sub-process description: Read 5G message sending key indicator data list information. Data movement type: R." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: IMS domain latency indicator data export. Functional process: IMS domain delay index data export. Sub-process description: Input the IMS domain delay index export request. Data movement type: E." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice service demand intelligent forecasting, 5G voice demand forecasting rule configuration. Trigger event: EPSFB voice demand forecast configuration data deletion. Functional process: EPSFB voice demand forecast configuration data deletion. Sub-process description: Return the deletion result. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, analysis and forecast of 5G message user numbers. Trigger event: UP2.4 user analysis data query. Functional process: UP2.4 user analysis data list query. Sub-process description: Input UP2.4 user analysis data list query request. Data movement type: E." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business analysis. Trigger event: Generation of poor-quality P2P service data tables. Functional process: Generation of poor-quality P2P business data tables (GP business library). Sub-process description: generate a poor-quality P2P service data table. Data movement type: W." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business analysis. Trigger event: Generation of poor-quality mass-sending business data table. Functional process: Generation of poor-quality mass-sending business data tables (GP business library). Sub-process description: Read the verification rules to verify the poor-quality group sending business data. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business rule configuration. Trigger event: P2P poor quality rule configuration data modification. Functional process: modify the configuration data of P2P poor quality rules. Sub-process description: Return the modification result. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, analysis of key factors of poor quality business indicators. Trigger event: Chatbot poor quality business key factor data query. Functional process: query the data list of key factors of chatbot poor quality business. Sub-process description: Read the data list information of the key factors of chatbot poor quality business. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message indicator system. Trigger event: business development indicator analysis data query. Functional process: detailed query of business development indicators analysis data. Sub-process description: output the detailed query results of business development indicators analysis data. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, configuration of indicator monitoring rules. Trigger event: P2P indicator monitoring rule configuration data modification. Functional process: P2P indicator monitoring rule configuration data modification. Sub-process description: Modify the P2P indicator monitoring rule configuration data. Data movement type: W." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business analysis. Trigger event: Export of poor-quality mass-sending business data. Functional process: Export of poor-quality mass-sending business data. Sub-process description: read the export template of the poor-quality mass-sending business. Data movement type: R." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, early warning of 5G voice indicators. Trigger event: VOLTE voice indicator warning data added. Function process: VOLTE voice indicator warning data is added. Sub-process description: Read the rules to verify the VOLTE voice indicator warning data. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business rule configuration. Trigger event: Display of configuration data for poor quality rules of file transfer. Functional process: configuration data display of poor quality rules for file transfers. Sub-process description: Input file transfer class poor quality rule configuration display request. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, analysis of key factors of poor quality business indicators. Trigger event: data export of key factors of poor business development quality. Functional process: Data export of key factors of poor business development quality. Sub-process description: return the export result. Data movement type: X." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice VOLTE call duration analysis data collection. Functional process: 5G voice VOLTE call duration analysis data collection. Sub-process description: Input 5G voice VOLTE call duration analysis data collection request. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, multi-dimensional aggregation of indicators. Trigger event: Chatbot class aggregation indicator data query. Functional process: Chatbot class aggregation indicator data list query. Sub-process description: Output the query result of the Chatbot class aggregation index data list. Data movement type: X." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice VONR user number analysis data table is generated. Functional process: 5G voice VONR user number analysis data table generation (GP service library). Sub-process description: Timing triggers the generation task of 5G voice VONR user number analysis data table. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, configuration of 5G message demand forecasting rules. Trigger event: P2P SMS demand forecasting rule configuration data is added. Functional process: The configuration data of the P2P short message number demand prediction rule is added. Sub-process description: return the newly added result of P2P SMS demand forecasting rule configuration data. Data movement type: X." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: registration latency indicator data query. Functional process: query the registration delay index data list. Sub-process description: Input the registration delay index data list query request. Data movement type: E." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop analysis of indicators. Trigger event: VONR indicator closed-loop analysis data query. Functional process: Query the details of VONR indicator closed-loop analysis data. Sub-process description: Read the detailed data of the closed-loop analysis of the VONR indicator. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business analysis. Trigger event: Generation of poor quality load indicator data table. Functional process: Statistics of poor quality load indicators (HBASE library). Sub-process description: read the statistical rules and perform statistical calculations on the poor quality load index data. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, multi-dimensional aggregation of indicators. Triggering event: querying aggregated indicator data for message group sending. Functional process: Query the details of aggregated indicator data for group message sending. Sub-process description: Enter a request for querying the details of aggregated indicator data for message group sending. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message quality indicators and trends. Trigger event: The generation of data table of poor quality indicators of file transfer class. Functional process: generation of poor quality index data table for file transfer (GP business library). Sub-process description: Generate abnormal data processing of file transfer class poor quality indicators. Data movement type: W." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice VOLTE call duration analysis data collection. Functional process: 5G voice VOLTE call duration analysis data analysis. Sub-process description: Read the analysis rules to analyze the 5G voice VOLTE call duration analysis data. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G voice service demand, 5G voice demand and predicted city rankings and trends. Trigger event: 5G voice VONR call duration prediction analysis data export. Functional process: 5G voice VONR call duration prediction analysis data export. Sub-process description: export 5G voice VONR call duration prediction analysis data. Data movement type: X." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice EPSFB user number analysis data table is generated. Functional process: 5G voice EPSFB user number analysis data statistics (HBASE library). Sub-process description: Save the statistical results of 5G voice EPSFB user number analysis data to the HBASE library. Data movement type: W." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice service demand intelligent forecasting, 5G voice demand forecasting rule configuration. Trigger event: EPSFB voice demand forecast configuration data is added. Functional process: EPSFB voice demand forecasting configuration data is added. Sub-process description: Input the new request of EPSFB voice demand forecast configuration data. Data movement type: E." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice service demand intelligent forecasting, 5G voice demand forecasting rule configuration. Trigger event: VONR voice demand forecast configuration data query. Functional process: VONR voice demand forecast configuration data list query. Sub-process description: Input VONR voice demand forecast configuration data list query request. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, drill-down of 5G message indicators. Trigger event: P2P message detailed list data query. Functional process: P2P message detailed list data query. Sub-process description: read the detailed data of P2P message details. Data movement type: R." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality network element analysis. Trigger event: Export of poor-quality NE connectivity indicators. Functional process: Export the connection index data of poor-quality network elements. Sub-process description: read the connection index data of poor-quality network elements. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, analysis of key factors of poor quality business indicators. Trigger event: Data query of key factors of poor business development. Functional process: query the data list of key factors of poor business development quality. Sub-process description: output the data list query results of key factors of poor business development quality. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G messaging service indicators, key indicators and trends of business development. Trigger event: 5G message terminal number indicator data query. Functional process: Query the details of the 5G message terminal number indicator data. Sub-process description: Output the detailed query results of the 5G message terminal number indicator data. Data movement type: X." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop analysis of indicators. Trigger event: VONR drop call solution data export. Functional process: VONR dropped call solution data export. Sub-process description: return the export result. Data movement type: X." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice VOLTE user number analysis data export. Functional process: 5G voice VOLTE user number analysis data export. Sub-process description: return the export result. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, configuration of 5G message demand forecasting rules. Trigger event: 5G message user number demand prediction rule configuration data export. Functional process: 5G message user number demand prediction rule configuration data export. Sub-process description: return the export result. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, monitoring of 5G message indicators. Trigger event: Export of business indicator monitoring data. Functional process: Export of business indicator monitoring data. Sub-process description: export business indicator monitoring data. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, multi-dimensional aggregation of indicators. Trigger event: Chatbot class aggregation indicator data export. Functional process: Chatbot class aggregation indicator data export. Sub-process description: return the export result. Data movement type: X." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: VONR intelligent analysis of calling delay, poor quality of terminal delay. Trigger event: terminal EPSFB delay data query. Functional process: Query the details of the terminal EPSFB delay data. Sub-process description: output terminal EPSFB delay data details query results. Data movement type: X." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: VOLTE voice quality is poor and the connection rule configuration data is deleted. Functional process: Delete the connection rule configuration data for poor VOLTE voice quality. Sub-process description: Update the configuration data of connection rules for VOLTE poor voice quality. Data movement type: W." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, configuration of indicator monitoring rules. Trigger event: File transfer indicator monitoring rule configuration data display. Functional process: file transfer indicator monitoring rule configuration data display. Sub-process description: Read the configuration data of file transfer indicator monitoring rules. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice VOLTE call duration analysis data collection. Functional process: 5G voice VOLTE call duration analysis data collection. Sub-process description: Call the 5G voice VOLTE call duration analysis data collection interface. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business rule configuration. Trigger event: modification of the configuration data of the business development class poor quality rule. Functional process: modify the configuration data of business development class poor quality rules. Description of the sub-process: Input the modification request for configuration data of poor quality rules of business development category. Data movement type: E." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message indicator system. Trigger event: business development indicators analysis data collection. Functional process: business development indicators analysis data collection. Sub-process description: Call the business development index analysis data collection interface. Data movement type: X." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop summary of service quality. Trigger event: EPSFB fallback class quality closed-loop data table is generated. Functional process: EPSFB fallback quality closed-loop data statistics (HBASE library). Sub-process description: Save the statistical results of EPSFB fallback quality closed-loop data to the HBASE library. Data movement type: W." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, analysis of indicator cause values. Trigger event: Chatbot business index cause value data query. Functional process: Chatbot business indicator reason value data list query. Sub-process description: read the chatbot business indicator cause value data list information. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, analysis of key factors of poor quality business indicators. Trigger event: Data query of key factors of poor business development. Functional process: query the data list of key factors of poor business development quality. Sub-process description: input query request for data list of key factors of poor business development quality. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Trigger event: Modification of the configuration data of the group sending poor quality terminal rules. Functional process: Modify the configuration data of group sending poor quality terminal rules. Sub-process description: read the configuration data of the group sending poor quality terminal rules. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, configuration of indicator monitoring rules. Trigger event: File transfer indicator monitoring rule configuration data export. Functional process: file transfer indicator monitoring rule configuration data export. Sub-process description: Input file transfer indicator monitoring rule configuration export request. Data movement type: E." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality network element analysis. Trigger event: Export of call quality index data of poor-quality NEs. Functional process: Export call quality index data of poor quality network elements. Sub-process description: Read the call quality index data of poor quality network elements. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Trigger event: modification of chatbot terminal rule configuration data of poor quality. Functional process: Modify the configuration data of chatbot terminal rules with poor quality. Sub-process description: modify the configuration data of the chatbot poor-quality terminal rules. Data movement type: W." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Trigger event: P2P poor quality terminal rule configuration data modification. Functional process: modify the configuration data of P2P poor quality terminal rules. Sub-process description: update the P2P poor quality terminal rule configuration data. Data movement type: W." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality analysis data export. Trigger event: export of poor-quality cell analysis data. Functional process: export of poor quality cell analysis data. Sub-process description: Export the analysis data of the poor quality cell. Data movement type: X." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice EPSFB call duration analysis data query. Functional process: 5G voice EPSFB call duration analysis data list query. Sub-process description: output 5G voice EPSFB call duration analysis data list query results. Data movement type: X." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice VONR user number analysis data export. Functional process: 5G voice VONR user number analysis data export. Sub-process description: export 5G voice VONR user number analysis data. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business analysis. Trigger event: Export of poor-quality P2P service data. Functional process: Export of poor-quality P2P business data. Sub-process description: read poor-quality P2P business data. Data movement type: R." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice VONR user number analysis data collection. Functional process: 5G voice VONR user number analysis data collection. Sub-process description: Input the 5G voice VONR user number analysis data collection request. Data movement type: E." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality cell analysis. Trigger event: Inquiry of call quality indicator data in poor quality cells. Functional process: Query the details of call quality index data in poor quality cells. Sub-process description: Read the detailed data of call quality indicators in poor quality cells. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: Intelligent monitoring of 5G message indicators, multi-dimensional aggregation and presentation. Trigger event: Query of aggregated dimension data with poor terminal quality. Functional process: Query the details of aggregated dimension data with poor terminal quality. Sub-process description: Output the detailed query results of aggregated dimension data with poor quality at the terminal. Data movement type: X." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality terminal analysis. Trigger event: Analysis data query of call quality index factors of poor-quality terminals. Functional process: Query the list query of the call quality index factor analysis data of poor quality terminals. Sub-process description: Input a query request for the analysis data list of call quality indicators of poor-quality terminals. Data movement type: E." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: IMS domain latency indicator data upload. Functional process: IMS domain delay index data upload. Sub-process description: Input the IMS domain delay index data upload request. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message quality indicators and trends. Trigger event: Chatbot service quality indicator data query. Functional process: Chatbot service quality indicator data list query. Sub-process description: Enter the query request for Chatbot service quality index data list. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business rule configuration. Trigger event: P2P poor quality rule configuration data display. Functional process: P2P poor quality rule configuration data display. Sub-process description: The output shows the configuration data of P2P poor quality rules. Data movement type: X." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, early warning of 5G voice indicators. Trigger event: EPSFB voice indicator warning data is added. Functional process: EPSFB voice index early warning data is added. Sub-process description: update EPSFB voice index warning data. Data movement type: W." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice EPSFB call duration analysis data collection. Functional process: 5G voice EPSFB call duration analysis data conversion. Sub-process description: save the 5G voice EPSFB call duration analysis data conversion data. Data movement type: W." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice VONR call duration analysis data table is generated. Functional process: 5G voice VONR call duration analysis data table generation (GP service library). Sub-process description: read 5G voice VONR call duration analysis data. Data movement type: R." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice VONR user number analysis data table is generated. Functional process: 5G voice VONR user number analysis data statistics (HBASE library). Sub-process description: Save the statistical results of 5G voice VONR user number analysis data to the HBASE library. Data movement type: W." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, analysis of key factors of poor quality business indicators. Trigger event: Data export of key business factors of poor registration quality. Functional process: Data export of key business factors of poor registration quality. Sub-process description: Enter a request for exporting business key factors of poor registration quality. Data movement type: E." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message quality indicators and trends. Trigger event: The data table of poor quality indicators for business development is generated. Functional process: Generation of poor quality indicator data tables for business development (GP business library). Sub-process description: Generate a data table of poor quality indicators for business development. Data movement type: W." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: VONR poor voice quality registration rule configuration data query. Functional process: Query the configuration data list of VONR poor voice quality registration rules. Sub-process description: Read the configuration data list information of VONR poor voice quality registration rules. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice VOLTE user number analysis data collection. Functional process: 5G voice VOLTE user number analysis data conversion interface. Sub-process description: read 5G voice VOLTE user number analysis data conversion rules. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, monitoring of 5G message indicators. Trigger event: Export of business indicator monitoring data. Functional process: Export of business indicator monitoring data. Sub-process description: return the export result. Data movement type: X." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, early warning of 5G voice indicators. Trigger event: EPSFB voice indicator warning data deletion. Functional process: EPSFB voice indicator warning data deletion. Sub-process description: Delete EPSFB voice indicator warning data. Data movement type: W." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, configuration of indicator monitoring rules. Trigger event: File transfer indicator monitoring rule configuration data modification. Functional process: File transfer indicator monitoring rule configuration data modification. Sub-process description: Input file transfer indicator monitoring rule configuration data modification request. Data movement type: E." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, 5G message quality terminal analysis. Triggering event: Query of poor-quality terminal registration indicator data. Functional process: Query the data list of poor-quality terminal registration indicators. Sub-process description: Output the query results of the poor-quality terminal registration index data list. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business analysis. Trigger event: Generation of poor-quality P2P service data tables. Functional process: Generation of poor-quality P2P business data tables (GP business library). Sub-process description: Timing triggers the generation task of the poor-quality P2P service data table. Data movement type: E." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: VOLTE poor voice quality delay rule configuration data modification. Functional process: Modify the configuration data of the VOLTE voice quality delay rule. Sub-process description: modify the configuration data of VOLTE voice quality delay rule. Data movement type: W." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G news indicators, city ranking and trend analysis. Trigger event: Export of file transfer indicator city trend analysis data. Functional process: file transfer indicators, city trend analysis data export. Sub-process description: input file transfer index city trend analysis export request. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, 5G message quality terminal analysis. Trigger event: bad-quality terminal chatbot business data query. Functional process: query the chatbot business data list of poor-quality terminals. Sub-process description: Enter a query request for the chatbot business data list of poor-quality terminals. Data movement type: E." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop summary of service quality. Trigger event: VONR connected quality closed-loop data table is generated. Functional process: VONR connection quality closed-loop data statistics (HBASE library). Sub-process description: read VONR connection quality closed-loop data. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice EPSFB call duration analysis data query. Function process: 5G voice EPSFB call duration analysis data details query. Sub-process description: Input 5G voice EPSFB call duration analysis data details query request. Data movement type: E." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, monitoring of 5G message indicators. Trigger event: Chatbot business indicator monitoring data query. Functional process: Chatbot business indicator monitoring data list query. Sub-process description: Output the query result of Chatbot business indicator monitoring data list. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: Intelligent monitoring of 5G message indicators, multi-dimensional aggregation and presentation. Trigger event: display of aggregated dimension data with poor terminal quality. Functional process: Display of aggregated dimensional data with poor terminal quality. Sub-process description: The output shows the poor quality aggregation dimension data of the terminal. Data movement type: X." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop summary of service quality. Trigger event: EPSFB fallback quality closed-loop data export. Functional process: EPSFB fallback quality closed-loop data export. Sub-process description: read the EPSFB fallback quality closed-loop export template. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice service demand intelligent forecasting, 5G voice demand forecasting rule configuration. Trigger event: VOLTE voice demand forecast configuration data query. Functional process: Query the details of VOLTE voice demand forecast configuration data. Sub-process description: read VOLTE voice demand forecast configuration details data. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, analysis of indicator cause values. Triggering event: The data table of the cause value of mass sending failure is generated. Functional process: generation of data table of cause value of mass sending failure (GP business library). Sub-process description: Timing triggers the task of generating the data table of the reason value of group sending failure. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, drill-down of 5G message indicators. Trigger event: P2P message detailed list data query. Functional process: P2P message detailed list data list query. Sub-process description: output the query result of P2P message detailed list data list. Data movement type: X." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: VONR intelligent analysis of calling delay, poor quality of terminal delay. Trigger event: Terminal EPSFB delay data export. Functional process: terminal EPSFB delay data export. Sub-process description: input terminal EPSFB delay export request. Data movement type: E." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice EPSFB user number analysis data export. Functional process: 5G voice EPSFB user number analysis data export. Sub-process description: read 5G voice EPSFB user number analysis data. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business rule configuration. Trigger event: Registration class poor quality rule configuration data modification. Functional process: modify the configuration data of registration class poor quality rules. Sub-process description: update the configuration data of registration class poor quality rules. Data movement type: W." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, analysis of indicator cause values. Triggering event: The data table of the cause value of mass sending failure is generated. Functional process: Statistics of the cause value of mass sending failure (HBASE library). Sub-process description: Input the data statistics request for the reason value of mass sending failure. Data movement type: E." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, 5G message quality terminal analysis. Trigger event: Export of indicator data for group messages sent by poor-quality terminals. Functional process: Export the indicator data of group messages sent by poor quality terminals. Sub-process description: return the export result. Data movement type: X." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice service quality closed-loop management, voice service quality monitoring closed-loop presentation. Trigger event: EPSFB voice service quality monitoring index data query. Functional process: Query the details of EPSFB voice service quality monitoring index data. Sub-process description: output the query result of EPSFB voice service quality monitoring index data details. Data movement type: X." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice EPSFB call duration analysis data collection. Functional process: 5G voice EPSFB call duration analysis data conversion. Sub-process description: Input 5G voice EPSFB call duration analysis data conversion request. Data movement type: E." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice VOLTE call duration analysis data export. Functional process: 5G voice VOLTE call duration analysis data export. Sub-process description: export 5G voice VOLTE call duration analysis data. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business analysis. Trigger event: Generation of poor quality file transfer business data table. Functional process: Generation of poor-quality file transfer business data tables (GP business library). Sub-process description: Save the poor-quality file transfer business data table to the GP table library. Data movement type: W." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, city ranking and trend of VoNR calling delay. Trigger event: VONR time delay ranking and trend data query. Functional process: Query the ranking and trend data details of VONR delay. Sub-process description: Input the ranking and trend data query request of VONR delay. Data movement type: E." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: core network latency index data collection. Functional process: core network delay index data collection interface. Sub-process description: read the core network delay index data. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, analysis of key factors of poor quality terminal indicators. Trigger event: query of terminal information and data with poor core network quality. Functional process: Query the list of terminal information data lists with poor core network quality. Sub-process description: Input the query request for the list of information and data of terminals with poor core network quality. Data movement type: E." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G messaging service requirements, analysis and forecasting of 5G messaging terminal numbers. Trigger event: 5G message terminal analysis data export. Functional process: 5G message terminal analysis data export. Sub-process description: return the export result. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: Intelligent monitoring of 5G message indicators, multi-dimensional aggregation and presentation. Trigger event: user-aware aggregation dimension data export. Functional process: user-aware aggregation dimension data export. Sub-process description: Read user-perceived aggregation dimension data. Data movement type: R." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice VONR user number analysis data query. Functional process: Query the details of 5G voice VONR user number analysis data. Sub-process description: Read the detailed data of 5G voice VONR user number analysis. Data movement type: R." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice EPSFB call duration analysis data collection. Functional process: 5G voice EPSFB call duration analysis data collection. Sub-process description: Read the verification rules to verify the account information of the 5G voice EPSFB call duration analysis data server. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, analysis of key factors of poor quality business indicators. Trigger event: data export of key factors of poor business development quality. Functional process: Data export of key factors of poor business development quality. Sub-process description: Read the export template of key factors of poor business development quality. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message business demand, 5G message demand and forecasted city rankings and trends. Trigger event: UP2.4 end user forecast data export. Functional process: UP2.4 end user number forecast data export. Sub-process description: export UP2.4 end user forecast data. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, configuration of indicator monitoring rules. Trigger event: P2P indicator monitoring rule configuration data is added. Functional process: P2P indicator monitoring rule configuration data is added. Sub-process description: Return the result of adding P2P indicator monitoring rule configuration data. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Trigger event: The configuration data of the chatbot poor quality terminal rule is added. Functional process: Added chatbot terminal rule configuration data with poor quality. Sub-process description: Read rule verification chatbot poor quality terminal rule configuration data. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, analysis of key factors of poor quality business indicators. Trigger event: data export of chatbot's poor quality business key factors. Functional process: Data export of chatbot's poor quality business key factors. Sub-process description: read the export template of chatbot's poor quality business key factors. Data movement type: R." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: VONR intelligent analysis of calling delay, poor quality of cell delay. Trigger event: Cell VoNR call VoNR delay data query. Functional process: VoNR calling VoNR delay data list query in the cell. Sub-process description: read the cell VoNR call VoNR delay data list information. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: The connection rule configuration data of poor VOLTE voice quality is added. Functional process: The configuration data of connection rules for VOLTE poor voice quality is added. Sub-process description: Input a new request for configuration data of connection rules with poor voice quality of VOLTE. Data movement type: E." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: On-time delay indicator data collection. Functional process: connect to the time delay index data collection interface. Sub-process description: read the on-delay index data. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, analysis of indicator cause values. Trigger event: Chatbot business index cause value data query. Functional process: query the details of the cause value data of Chatbot business indicators. Sub-process description: Enter the query request for Chatbot business indicator cause value data details. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, analysis and forecast of 5G message user numbers. Trigger event: UP2.4 user analysis data query. Functional process: UP2.4 user analysis data details query. Sub-process description: read UP2.4 user analysis details data. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice EPSFB call duration analysis data table is generated. Functional process: 5G voice EPSFB call duration analysis data table generation (GP service library). Sub-process description: Save the 5G voice EPSFB call duration analysis data table to the GP table library. Data movement type: W." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business rule configuration. Trigger event: The configuration data of the poor quality rule of the business development category is added. Functional process: Added new configuration data for business development category poor quality rules. Sub-process description: Input new request for configuration data of poor quality rules of business development. Data movement type: E." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: The connection rule configuration data of poor VOLTE voice quality is added. Functional process: The configuration data of connection rules for VOLTE poor voice quality is added. Sub-process description: Update the configuration data of connection rules for VOLTE poor voice quality. Data movement type: W." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: Intelligent monitoring of 5G message indicators, multi-dimensional aggregation and presentation. Triggering event: display of prefecture-city registration aggregation dimension data. Functional process: data display of prefectural and city registration aggregation dimensions. Sub-process description: Read prefecture-city registration aggregation dimension data. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Trigger event: modification of terminal rule configuration data with poor service development quality. Functional process: modification of terminal rule configuration data for poor business development. Sub-process description: update the terminal rule configuration data with poor service development quality. Data movement type: W." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G voice service demand, 5G voice demand and predicted city rankings and trends. Trigger event: 5G voice EPSFB call duration prediction analysis data export. Functional process: 5G voice EPSFB call duration prediction analysis data export. Sub-process description: Input 5G voice EPSFB call duration prediction analysis export request. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business analysis. Trigger event: Generation of poor-quality mass-sending business data table. Functional process: Statistics of poor-quality mass-sending business data (HBASE library). Sub-process description: Input the statistics request of poor-quality mass-sending business data. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, drill-down of 5G message indicators. Trigger event: 5G message group sending detailed list data query. Functional process: 5G message group sending detailed list data detailed query. Sub-process description: Read the detailed data of 5G message group sending details. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, analysis of key factors of poor quality business indicators. Trigger event: data query of key factors of P2P poor quality business. Functional process: query the data list of key factors of P2P poor quality business. Sub-process description: Read the data list information of the key factors of P2P poor quality business. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, analysis of indicator cause values. Trigger event: business failure cause value data download. Functional process: business failure cause value data download. Sub-process description: input the business failure cause value data download request. Data movement type: E." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice service quality closed-loop management, voice service quality monitoring closed-loop presentation. Trigger event: VOLTE voice service quality monitoring indicator data export. Functional process: export VOLTE voice service quality monitoring index data. Sub-process description: read VOLTE voice service quality monitoring index data. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business analysis. Trigger event: Generation of poor quality file transfer business data table. Functional process: poor quality file transfer business data statistics (HBASE library). Sub-process description: read poor-quality file transfer business data. Data movement type: R." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: EPSFB poor voice quality connection rule configuration data query. Functional process: EPSFB poor voice quality connection rule configuration data list query. Sub-process description: Output EPSFB poor voice quality connection rule configuration data list query result. Data movement type: X." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: The configuration data of the VOLTE poor voice quality delay rule is added. Functional process: The configuration data of the delay rule for poor voice quality in VOLTE is added. Sub-process description: update the configuration data of VOLTE voice quality delay rule. Data movement type: W." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business analysis. Trigger event: data query of poor quality load indicators. Functional process: Query the details of poor quality load index data. Sub-process description: Input the request for querying the details of the poor quality load indicator data. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: Intelligent monitoring of 5G message indicators, multi-dimensional aggregation and presentation. Trigger event: Export of prefecture-city registration aggregation dimension data. Functional process: Export of prefecture-city registration aggregation dimension data. Sub-process description: export prefecture-city registration aggregation dimension data. Data movement type: X." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice VOLTE user number analysis data collection. Functional process: 5G voice VOLTE user number analysis data collection interface. Sub-process description: Return the analysis data of 5G voice VOLTE users. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business analysis. Trigger event: Generation of poor-quality mass-sending business data table. Functional process: Generation of poor-quality mass-sending business data tables (GP business library). Sub-process description: Generate and write abnormal data logs of poor-quality mass-sending business. Data movement type: W." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice service demand intelligent forecasting, 5G voice demand forecasting rule configuration. Trigger event: VONR voice demand forecast configuration data deletion. Functional process: VONR voice demand forecast configuration data deletion. Sub-process description: update VONR voice demand forecast configuration data. Data movement type: W." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message quality indicators and trends. Trigger event: P2P poor quality indicator data query. Functional process: P2P type poor quality index data list query. Sub-process description: read the P2P poor quality indicator data list information. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business rule configuration. Trigger event: P2P poor quality rule configuration data is added. Functional process: P2P class poor quality rule configuration data is added. Sub-process description: Input the new request for P2P poor quality rule configuration data. Data movement type: E." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, analysis of indicator cause values. Trigger event: registration failure reason value data download. Functional process: download the registration failure reason value data. Sub-process description: download the registration failure reason value data. Data movement type: W." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G messaging service indicators, key indicators and trends of business development. Trigger event: UP2.4 terminal 5G message index data query. Functional process: Query the details of UP2.4 terminal 5G message indicator data. Sub-process description: Input the detailed query request of UP2.4 terminal 5G message index data. Data movement type: E." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop summary of service quality. Trigger event: VONR registration class quality closed-loop data export. Functional process: VONR registration class quality closed-loop data export. Sub-process description: Read VONR registration class quality closed-loop data. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice EPSFB user number analysis data export. Functional process: 5G voice EPSFB user number analysis data export. Sub-process description: Input the 5G voice EPSFB user number analysis and export request. Data movement type: E." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality analysis data export. Trigger event: The analysis data of poor-quality communities is added. Functional process: The analysis data of poor-quality communities is added. Sub-process description: Input a new request for analysis data of poor-quality communities. Data movement type: E." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, analysis of indicator cause values. Trigger event: Chatbot business indicator reason value data export. Functional process: Chatbot business indicator cause value data export. Sub-process description: read the reason value data of Chatbot business indicators. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message quality indicators and trends. Trigger event: Chatbot service quality indicator data download. Functional process: Chatbot business quality indicator data download. Sub-process description: Download the chatbot service quality index data. Data movement type: W." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice service quality closed-loop management, voice service quality monitoring closed-loop presentation. Trigger event: VONR voice service quality monitoring indicator data export. Functional process: VONR voice service quality monitoring index data export. Sub-process description: export VONR voice service quality monitoring index data. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message indicator system. Trigger event: Generate registration index analysis data table. Functional process: generation of registration index analysis data table (GP business library). Sub-process description: generate registration index analysis data table. Data movement type: W." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, city ranking and trend of VoNR calling delay. Trigger event: EPSFB time-lapse ranking and trend data export. Functional process: EPSFB latency ranking and trend data export. Sub-process description: Read the ranking and trend export template of EPSFB delay. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message indicator system. Trigger event: export of business development indicator analysis data. Functional process: business development indicators analysis data export. Sub-process description: export the analysis data of business development indicators. Data movement type: X." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: VONR intelligent analysis of calling delay, poor quality of cell delay. Trigger event: Cell EPSFB delay data export. Functional process: Cell EPSFB delay data export. Sub-process description: return the export result. Data movement type: X." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality cell analysis. Trigger event: downloading of registration index data for poor-quality communities. Functional process: Download the registration index data of poor-quality communities. Sub-process description: Save the download data of registration indicators of poor-quality communities. Data movement type: W." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message indicator system. Trigger event: business development indicators analysis data collection. Functional process: business development indicators analysis data analysis. Sub-process description: Read and analyze rules to analyze the analysis data of business development indicators. Data movement type: R." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G voice service demand, 5G voice demand and predicted city rankings and trends. Trigger event: 5G voice VONR call duration prediction analysis data query. Functional process: 5G voice VONR call duration prediction analysis data list query. Sub-process description: Input the query request for the 5G voice VONR call duration prediction analysis data list. Data movement type: E." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice service demand intelligent forecasting, 5G voice demand forecasting rule configuration. Trigger event: VOLTE voice demand forecast configuration data export. Functional process: VOLTE voice demand forecast configuration data export. Sub-process description: Read the VOLTE voice demand forecast configuration export template. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G messaging service requirements, early warning of 5G messaging performance indicators. Trigger event: 5G message user & terminal early warning data table generation. Functional process: 5G message user & terminal early warning data table generation (GP business library). Sub-process description: Read 5G message user & terminal early warning data. Data movement type: R." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality network element analysis. Triggering event: Query for registration index data of poor quality NEs. Functional process: Query the details of registration index data of poor-quality NEs. Sub-process description: Read the detailed data of registration indicators of poor-quality network elements. Data movement type: R." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice EPSFB user number analysis data table is generated. Functional process: 5G voice EPSFB user number analysis data table generation (GP service library). Sub-process description: generate 5G voice EPSFB user number analysis abnormal data processing. Data movement type: W." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: core network latency index data collection. Functional process: core network delay index data collection interface. Sub-process description: Receive the core network delay index data collection request. Data movement type: E." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice EPSFB user number analysis data collection. Functional process: 5G voice EPSFB user number analysis data conversion. Sub-process description: save the 5G voice EPSFB user number analysis data conversion data. Data movement type: W." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business rule configuration. Trigger event: Registration class poor quality rule configuration data modification. Functional process: modify the configuration data of registration class poor quality rules. Description of the sub-process: Input the request for modifying the configuration data of the registration class poor quality rule. Data movement type: E." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice VOLTE user number analysis data collection. Functional process: 5G voice VOLTE user number analysis data collection interface. Sub-process description: Receive 5G voice VOLTE user number analysis data collection request. Data movement type: E." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop summary of service quality. Trigger event: VONR registration class quality closed-loop data table generation. Functional process: VONR registration quality closed-loop data table generation (GP business library). Sub-process description: Timing trigger the VONR registration class quality closed-loop data table generation task. Data movement type: E." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: core network latency index data collection. Functional process: core network delay index data collection. Sub-process description: Read the account information of the core network latency indicator data server. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business rule configuration. Trigger event: The registration class poor quality rule configuration data is added. Functional process: The configuration data of the registration class poor quality rule is added. Sub-process description: update the configuration data of registration class poor quality rules. Data movement type: W." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G news indicators, city ranking and trend analysis. Triggering event: downloading of the ranking data of prefectures and cities for mass distribution of indicators. Functional process: download the ranking data of prefectures and cities by group sending. Sub-process description: Save the downloaded data of the ranking of cities and towns for mass distribution indicators. Data movement type: W." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: core network latency index data query. Functional process: query the core network latency index data list. Sub-process description: Input the query request for the core network latency index data list. Data movement type: E." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice service quality closed-loop management, voice service quality monitoring closed-loop presentation. Trigger event: VOLTE voice service quality monitoring indicator data export. Functional process: export VOLTE voice service quality monitoring index data. Sub-process description: input the VOLTE voice service quality monitoring index export request. Data movement type: E." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality analysis data export. Trigger event: Export of poor-quality NE analysis data. Functional process: export the analysis data of poor quality network elements. Sub-process description: read the export template of poor quality network element analysis. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business rule configuration. Trigger event: P2P poor quality rule configuration data modification. Functional process: modify the configuration data of P2P poor quality rules. Sub-process description: modify the configuration data of P2P poor quality rules. Data movement type: W." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, analysis of key factors of poor quality business indicators. Trigger event: data query of key factors of P2P poor quality business. Functional process: query the data details of the key factors of P2P poor quality business. Sub-process description: read the detailed data of the key factors of P2P poor quality business. Data movement type: R." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality cell analysis. Triggering event: downloading of connection index data for poor quality cells. Functional process: downloading of connection index data for poor quality cells. Sub-process description: read the access index data of poor quality cells. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, configuration of 5G message demand forecasting rules. Trigger event: 5G message terminal number demand forecast rule configuration data export. Functional process: 5G message terminal number demand forecast rule configuration data export. Sub-process description: return the export result. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, configuration of indicator monitoring rules. Trigger event: Business development indicator monitoring rule configuration data modification. Functional process: business development indicator monitoring rule configuration data modification. Sub-process description: Input the service development indicator monitoring rule configuration data modification request. Data movement type: E." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop summary of service quality. Triggering event: VONR connected quality closed-loop data export. Functional process: VONR connected quality closed-loop data export. Sub-process description: return the export result. Data movement type: X." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: VONR intelligent analysis of calling delay, poor quality of cell delay. Trigger event: export of VoNR delay data for VoNR calls in the cell. Functional process: export of VoNR delay data for cell VoNR calls. Sub-process description: read VoNR delay data of cell VoNR calls. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice service demand intelligent forecasting, 5G voice demand forecasting rule configuration. Trigger event: VONR voice demand forecast configuration data is added. Function process: VONR voice demand forecast configuration data is added. Sub-process description: read VONR voice demand forecast configuration data. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message business demand, 5G message demand and forecasted city rankings and trends. Triggering event: UP2.4 export of prediction data on the number of group text messages sent by terminals. Functional process: UP2.4 terminal group text message number prediction data export. Sub-process description: export the prediction data of UP2.4 terminal group text messages. Data movement type: X." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: core network latency index data collection. Functional process: core network delay index data collection. Sub-process description: Read the verification rules to verify the account information of the core network latency index data server. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice VONR user number analysis data collection. Functional process: 5G voice VONR user number analysis data conversion interface. Sub-process description: read 5G voice VONR user number analysis data for conversion. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, analysis of indicator cause values. Trigger event: registration failure reason value data query. Functional process: Query the details of the reason value data of the registration failure. Sub-process description: Enter the query request for registration failure reason value data details. Data movement type: E." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, analysis of key factors of poor quality terminal indicators. Trigger event: Query data of terminal indicators with poor granularity in prefectures and cities. Functional process: Inquiry about the details of terminal index data with poor granularity and quality in prefectures and cities. Sub-process description: Output the detailed query results of the terminal index data with poor granularity and quality in cities. Data movement type: X." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice VOLTE call duration analysis data collection. Functional process: 5G voice VOLTE call duration analysis data collection interface. Sub-process description: return 5G voice VOLTE call duration analysis data. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, multi-dimensional aggregation of indicators. Triggering event: The data export of terminal business aggregation indicators. Functional process: export the aggregation indicator data of terminal business class. Sub-process description: return the export result. Data movement type: X." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice VONR user number analysis data table is generated. Functional process: 5G voice VONR user number analysis data table generation (GP service library). Sub-process description: Read the verification rules to verify the 5G voice VONR user number analysis data. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality cell analysis. Trigger event: Inquiry of connection index data of poor quality cells. Functional process: Query the data list of connection indicators of poor quality cells. Sub-process description: output query results of poor-quality cell connection index data list. Data movement type: X." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, early warning of 5G voice indicators. Trigger event: VONR voice indicators early warning data query. Functional process: Query the details of VONR voice index early warning data. Sub-process description: Read the detailed data of VONR voice indicator warning. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice VOLTE user number analysis data collection. Functional process: 5G voice VOLTE user number analysis data conversion. Sub-process description: Save the 5G voice VOLTE user number analysis data conversion data. Data movement type: W." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice VOLTE user number analysis data collection. Functional process: 5G voice VOLTE user number analysis data collection. Sub-process description: Input the 5G voice VOLTE user number analysis data collection request. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Triggering event: The configuration data of the registration poor quality terminal rule is added. Functional process: The configuration data for the registration of poor-quality terminal rules is added. Sub-process description: Enter a new request for configuration data of poor registered terminal rules. Data movement type: E." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: VONR intelligent analysis of calling delay, poor quality of terminal delay. Trigger event: terminal EPSFB delay data query. Function process: terminal EPSFB delay data list query. Sub-process description: Input terminal EPSFB delay data list query request. Data movement type: E." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G voice service demand, 5G voice demand and predicted city rankings and trends. Trigger event: 5G voice VONR call duration prediction analysis data query. Functional process: 5G voice VONR call duration prediction analysis data list query. Sub-process description: read 5G voice VONR call duration prediction analysis data list information. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G voice service demand, 5G voice demand and predicted city rankings and trends. Trigger event: 5G voice EPSFB call duration prediction analysis data query. Functional process: 5G voice EPSFB call duration prediction analysis data query. Sub-process description: Read the detailed data of 5G voice EPSFB call duration prediction analysis. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, 5G message quality terminal analysis. Trigger event: P2P message index data query of poor quality terminals. Functional process: Query the P2P message index data list of poor quality terminals. Sub-process description: Output the query result of the P2P message index data list of poor quality terminals. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, analysis of indicator cause values. Trigger event: P2P failure reason value data query. Functional process: P2P failure reason value data list query. Sub-process description: read P2P failure cause value data list information. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, configuration of 5G message demand forecasting rules. Trigger event: UP2.4 terminal user number prediction rule configuration data display. Functional process: UP2.4 terminal user number prediction rule configuration data display. Sub-process description: The output shows the UP2.4 terminal user number prediction rule configuration data. Data movement type: X." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality analysis data export. Trigger event: The analysis data of the poor quality cell is modified. Functional process: modify the analysis data of poor quality plots. Sub-process description: Update the analysis data of the poor-quality plots. Data movement type: W." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G news indicators, city ranking and trend analysis. Trigger event: download of ranking data of prefectures and cities of registration indicators. Functional process: download the ranking data of registration index cities. Sub-process description: read the ranking data of registered index prefectures and cities. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: VONR poor voice quality registration rule configuration data deletion. Functional process: Delete the registration rule configuration data for VONR poor voice quality. Sub-process description: Delete the registration rule configuration data of VONR poor voice quality. Data movement type: W." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G messaging service requirements, early warning of 5G messaging performance indicators. Trigger event: P2P & group message warning data query. Functional process: P2P & group message early warning data details query. Sub-process description: read P2P & group message warning details data. Data movement type: R." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop summary of service quality. Trigger event: VONR connected quality closed-loop data query. Functional process: VONR connected quality closed-loop data list query. Sub-process description: Input VONR access quality closed-loop data list query request. Data movement type: E." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality cell analysis. Triggering event: downloading of connection index data for poor quality cells. Functional process: downloading of connection index data for poor quality cells. Sub-process description: Save the download data of connection indicators of poor-quality cells. Data movement type: W." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop summary of service quality. Trigger event: EPSFB call quality quality closed-loop data table generation. Functional process: EPSFB call quality closed-loop data statistics (HBASE library). Sub-process description: Input EPSFB call quality closed-loop data statistics request. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Trigger event: Modification of the configuration data of the group sending poor quality terminal rules. Functional process: Modify the configuration data of group sending poor quality terminal rules. Sub-process description: Update the configuration data of the group sending poor quality terminal rules. Data movement type: W." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, analysis of indicator cause values. Trigger event: business failure reason value data query. Functional process: query the data list of business failure reasons. Sub-process description: Output the query result of the data list of the cause of business failure. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business analysis. Trigger event: Generation of poor quality load indicator data table. Functional process: Statistics of poor quality load indicators (HBASE library). Sub-process description: Save the statistical results of poor quality load index data to the HBASE library. Data movement type: W." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business rule configuration. Trigger event: Registration class poor quality rule configuration data modification. Functional process: modify the configuration data of registration class poor quality rules. Sub-process description: Return the modification result. Data movement type: X." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice VONR user number analysis data export. Functional process: 5G voice VONR user number analysis data export. Sub-process description: return the export result. Data movement type: X." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop summary of service quality. Trigger event: VONR connected quality closed-loop data table is generated. Functional process: VONR connection quality closed-loop data table generation (GP business library). Sub-process description: read VONR connection quality closed-loop data. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message business demand, 5G message demand and forecasted city rankings and trends. Trigger event: UP2.4 terminal mass SMS number prediction data query. Functional process: UP2.4 query the details of the prediction data of the number of group text messages sent by the terminal. Sub-process description: output the detailed query results of UP2.4 terminal group SMS number prediction data. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, configuration of 5G message demand forecasting rules. Trigger event: P2P SMS demand forecasting rule configuration data is added. Functional process: The configuration data of the P2P short message number demand prediction rule is added. Sub-process description: update the configuration data of the P2P short message number demand prediction rule. Data movement type: W." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: Core network latency index data export. Functional process: export core network latency index data. Sub-process description: Input the core network delay index export request. Data movement type: E." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Trigger event: modification of terminal rule configuration data with poor service development quality. Functional process: modification of terminal rule configuration data for poor business development. Sub-process description: input a request for modifying configuration data of terminal rules with poor service development quality. Data movement type: E." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: VONR intelligent analysis of calling delay, poor quality of terminal delay. Trigger event: terminal EPSFB delay data query. Functional process: Query the details of the terminal EPSFB delay data. Sub-process description: Input terminal EPSFB delay data query request. Data movement type: E." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop summary of service quality. Trigger event: EPSFB call quality quality closed-loop data table generation. Functional process: EPSFB call quality closed-loop data table generation (GP service library). Sub-process description: Trigger the generation task of EPSFB call quality closed-loop data table at regular intervals. Data movement type: E." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business rule configuration. Trigger event: File transfer class poor quality rule configuration data export. Functional process: file transfer class poor quality rule configuration data export. Sub-process description: Input file transfer class poor quality rule configuration export request. Data movement type: E." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message indicator system. Trigger event: upload of business development indicator analysis data. Functional process: business development indicators analysis data upload. Sub-process description: read the analysis data of business development indicators. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: EPSFB poor voice quality connection rule configuration data is added. Functional process: The EPSFB poor voice quality connection rule configuration data is added. Sub-process description: return the newly added result of EPSFB poor voice quality connection rule configuration data. Data movement type: X." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice VOLTE user number analysis data collection. Functional process: 5G voice VOLTE user number analysis data conversion interface. Sub-process description: return 5G voice VOLTE user number analysis data conversion data. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, analysis of key factors of poor quality business indicators. Trigger event: Data query of key factors of poor business development. Functional process: query the data list of key factors of poor business development quality. Sub-process description: read the data list information of key factors of poor business development quality. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, configuration of 5G message demand forecasting rules. Trigger event: P2P short message number demand prediction rule configuration data export. Functional process: P2P SMS number demand prediction rule configuration data export. Sub-process description: read the configuration data of P2P short message number demand prediction rules. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Trigger event: The configuration data of the chatbot poor quality terminal rule is added. Functional process: Added chatbot terminal rule configuration data with poor quality. Sub-process description: update chatbot poor-quality terminal rule configuration data. Data movement type: W." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop summary of service quality. Trigger event: EPSFB call quality quality closed-loop data table generation. Functional process: EPSFB call quality closed-loop data table generation (GP service library). Sub-process description: Read the verification rules to verify the quality closed-loop data of EPSFB call quality. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, 5G message quality terminal analysis. Trigger event: Poor quality terminal file transfer index data query. Functional process: Query the data list of poor-quality terminal file transfer indicators. Sub-process description: Read the index data list information of poor-quality terminal file transfers. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, configuration of 5G message demand forecasting rules. Trigger event: UP2.4 terminal user number prediction rule configuration data modification. Functional process: UP2.4 Modification of the configuration data of the prediction rules for the number of end users. Sub-process description: Input UP2.4 terminal user number prediction rule configuration data modification request. Data movement type: E." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: data query of connection delay index. Functional process: Query the details of connection delay index data. Description of the sub-process: Input the request for querying the details of the on-delay index data. Data movement type: E." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice VONR call duration analysis data export. Functional process: 5G voice VONR call duration analysis data export. Sub-process description: Input 5G voice VONR call duration analysis and export request. Data movement type: E." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, early warning of 5G voice indicators. Trigger event: Export of EPSFB voice index warning data. Functional process: EPSFB voice indicator early warning data export. Sub-process description: return the export result. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, configuration of 5G message demand forecasting rules. Trigger event: 5G message terminal number demand forecast rule configuration data export. Functional process: 5G message terminal number demand forecast rule configuration data export. Sub-process description: Input the export request of the 5G message terminal quantity demand forecasting rule configuration. Data movement type: E." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G poor voice quality perception analysis, 5G poor voice quality rule configuration. Trigger event: VONR poor voice quality registration rule configuration data query. Functional process: Query the configuration data list of VONR poor voice quality registration rules. Sub-process description: input VONR poor voice quality registration rule configuration data list query request. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G messaging service requirements, early warning of 5G messaging performance indicators. Trigger event: P2P & group message warning data query. Functional process: P2P & group message early warning data details query. Sub-process description: Input P2P & group message early warning data details query request. Data movement type: E." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message quality indicators and trends. Trigger event: The generation of data table of poor quality indicators of file transfer class. Functional process: Statistics of poor quality indicators for file transfers (HBASE library). Sub-process description: read file transfer class poor quality indicator data. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, drill-down of 5G message indicators. Trigger event: 5G message group sending detailed list data query. Functional process: 5G message group sending detailed list data detailed query. Sub-process description: Enter a request for querying the details of the 5G message group sending detailed list data. Data movement type: E." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, segmentation analysis of VoNR calling delay. Trigger event: On-time delay indicator data collection. Functional process: data analysis of connection delay index. Sub-process description: Input the data analysis request of the on-delay index. Data movement type: E." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, configuration of 5G message demand forecasting rules. Trigger event: 5G message terminal number demand forecasting rule configuration data is added. Functional process: 5G message terminal number demand forecasting rule configuration data is added. Sub-process description: Read the configuration data of the 5G message terminal number demand prediction rule. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, configuration of indicator monitoring rules. Trigger event: Business development indicator monitoring rule configuration data modification. Functional process: business development indicator monitoring rule configuration data modification. Sub-process description: modify the configuration data of the business development indicator monitoring rules. Data movement type: W." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, call auxiliary delay statistics. Trigger event: N26 interface delay data download. Functional process: N26 interface delay data download. Sub-process description: download the delay data of the N26 interface. Data movement type: W." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, multi-dimensional aggregation of indicators. Trigger event: Chatbot class aggregation indicator data export. Functional process: Chatbot class aggregation indicator data export. Sub-process description: read the export template of Chatbot class aggregation indicators. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G messaging service indicators, key indicators and trends of business development. Trigger event: Data export of key indicators of 5G message business. Functional process: export key indicator data of 5G message business. Sub-process description: return the export result. Data movement type: X." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice EPSFB call duration analysis data collection. Functional process: 5G voice EPSFB call duration analysis data conversion interface. Sub-process description: Receive 5G voice EPSFB call duration analysis data conversion request. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message quality indicators and trends. Trigger event: Data export of poor quality indicators for business development. Functional process: Data export of poor quality indicators for business development. Sub-process description: read the poor quality indicator data of business development category. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, 5G message quality terminal analysis. Triggering event: Query of poor-quality terminal registration indicator data. Functional process: Query the data list of poor-quality terminal registration indicators. Sub-process description: Read the information of the poor-quality terminal registration index data list. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, 5G message quality terminal analysis. Trigger event: bad-quality terminal chatbot business data query. Functional process: query the chatbot business data list of poor-quality terminals. Sub-process description: Output the query result of chatbot business data list of poor-quality terminals. Data movement type: X." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice EPSFB call duration analysis data query. Functional process: 5G voice EPSFB call duration analysis data list query. Sub-process description: Input the 5G voice EPSFB call duration analysis data list query request. Data movement type: E." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality terminal analysis. Trigger event: Analysis data query of call quality index factors of poor-quality terminals. Functional process: Query the list query of the call quality index factor analysis data of poor quality terminals. Sub-process description: output the query results of the call quality index factor analysis data list of the terminal with poor quality. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G messaging service indicators, key indicators and trends of business development. Trigger event: 5G message user number indicator data query. Functional process: Query the list of 5G message user number index data. Sub-process description: Read the 5G message user number index data list information. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, analysis of key factors of poor quality terminal indicators. Trigger event: Export of prefecture-level and poor-quality terminal indicator data. Functional process: Data export of prefecture-level and poor-quality terminal indicators. Sub-process description: Read the template for exporting city-level poor-quality terminal indicators. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, analysis of key factors of poor quality business indicators. Trigger event: data export of key factors of P2P poor quality business. Functional process: Data export of key factors of P2P poor quality business. Sub-process description: read the data of key factors of P2P poor quality business. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G news indicators, city ranking and trend analysis. Trigger event: download of ranking data of prefectures and cities of registration indicators. Functional process: download the ranking data of registration index cities. Sub-process description: Save the downloaded data of the registered index prefecture and city ranking. Data movement type: W." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, analysis and forecast of 5G message user numbers. Trigger event: UP2.4 user analysis data query. Functional process: UP2.4 user analysis data details query. Sub-process description: output the query result of UP2.4 user analysis data details. Data movement type: X." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: VONR intelligent analysis of calling delay, poor quality of cell delay. Trigger event: Cell VoNR call VoNR delay data query. Functional process: VoNR calling VoNR delay data list query in the cell. Sub-process description: Input the cell VoNR call VoNR delay data list query request. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Trigger event: The configuration data of the group sending poor quality terminal rule is added. Functional process: The configuration data of the group sending poor quality terminal rules is added. Sub-process description: Return the new result of configuration data of group sending poor quality terminal rules. Data movement type: X." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop analysis of indicators. Trigger event: VONR drop call solution data export. Functional process: VONR dropped call solution data export. Sub-process description: read VONR dropped call solution data. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, analysis and forecast of 5G message user numbers. Trigger event: UP2.4 user analysis data export. Functional process: UP2.4 user analysis data export. Sub-process description: read UP2.4 user analysis export template. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice EPSFB call duration analysis data collection. Functional process: 5G voice EPSFB call duration analysis data collection interface. Sub-process description: Receive 5G voice EPSFB call duration analysis data collection request. Data movement type: E." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality cell analysis. Trigger event: downloading of time delay index data for poor quality cells. Functional process: Download the time-delay index data of poor-quality cells. Sub-process description: Read the time-delay index data of poor-quality cells. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, analysis of indicator cause values. Triggering event: The data table of the cause value of mass sending failure is generated. Functional process: Statistics of the cause value of mass sending failure (HBASE library). Sub-process description: read the data of the cause value of the mass sending failure. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, 5G message quality terminal analysis. Trigger event: P2P message index data export of poor quality terminals. Functional process: Export the P2P message index data of poor quality terminals. Sub-process description: Export P2P message index data of poor quality terminals. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G messaging service indicators, key indicators and trends of business development. Trigger event: UP2.4 terminal 5G message index data query. Functional process: Query the list of UP2.4 terminal 5G message index data. Sub-process description: Read the UP2.4 terminal 5G message indicator data list information. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice VOLTE call duration analysis data collection. Functional process: 5G voice VOLTE call duration analysis data collection. Sub-process description: Read the account information of the 5G voice VOLTE call time analysis data server. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: Intelligent monitoring of 5G message indicators, multi-dimensional aggregation and presentation. Trigger event: prefecture-city registration aggregation dimension data query. Functional process: Query the details of the aggregation dimension data of prefecture-city registration. Description of the sub-process: Input the query request for the details of the aggregation dimension data of prefecture-city registration. Data movement type: E." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality cell analysis. Trigger event: downloading of call quality indicator data in poor quality cells. Functional process: Download call quality indicator data for poor quality cells. Sub-process description: Save the downloaded data of call quality indicators in poor quality cells. Data movement type: W." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, analysis and forecast of 5G voice user numbers. Trigger event: 5G voice EPSFB user number analysis data collection. Functional process: 5G voice EPSFB user number analysis data conversion interface. Sub-process description: return 5G voice EPSFB user number analysis data conversion data. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, poor quality terminal rule configuration. Trigger event: P2P poor quality terminal rule configuration data export. Functional process: P2P poor quality terminal rule configuration data export. Sub-process description: export P2P poor quality terminal rule configuration data. Data movement type: X." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, early warning of 5G voice indicators. Trigger event: Export of EPSFB voice index warning data. Functional process: EPSFB voice indicator early warning data export. Sub-process description: Input EPSFB voice index warning export request. Data movement type: E." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality analysis data export. Trigger event: The analysis data of poor-quality communities is added. Functional process: The analysis data of poor-quality communities is added. Sub-process description: Read the analysis data of poor quality plots. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message indicator system. Trigger event: Generate registration index analysis data table. Functional process: generation of registration index analysis data table (GP business library). Sub-process description: Generate registration class indicators and analyze abnormal data log writing. Data movement type: W." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice EPSFB call duration analysis data collection. Functional process: 5G voice EPSFB call duration analysis data analysis. Sub-process description: Read the analysis rules and analyze the 5G voice EPSFB call duration analysis data. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice VONR call duration analysis data query. Functional process: 5G voice VONR call duration analysis data list query. Sub-process description: Enter a query request for the 5G voice VONR call duration analysis data list. Data movement type: E." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice service demand intelligent forecasting, 5G voice demand forecasting rule configuration. Trigger event: EPSFB voice demand forecast configuration data query. Functional process: EPSFB voice demand forecast configuration data list query. Sub-process description: Output EPSFB voice demand forecast configuration data list query results. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, monitoring of 5G message indicators. Trigger event: Group sending indicator monitoring data query. Functional process: query the group sending index monitoring data list. Sub-process description: output the list query results of group sending indicator monitoring data. Data movement type: X." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message indicator system. Trigger event: business development indicators analysis data collection. Functional process: business development indicators analysis data collection. Sub-process description: Read the account information of the business development indicator analysis data server. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message poor quality perception analysis, poor quality business rule configuration. Trigger event: Export of configuration data for business development class poor quality rules. Functional process: business development class poor quality rule configuration data export. Sub-process description: Read the business development class poor quality rule configuration export template. Data movement type: R." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality analysis data export. Trigger event: Export of poor quality terminal analysis data. Functional process: export of poor quality terminal analysis data. Sub-process description: read the poor-quality terminal analysis export template. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality network element analysis. Trigger event: Query the call quality index data of poor quality NEs. Functional process: Query the call quality index data list of poor-quality network elements. Sub-process description: Read the call quality index data list information of poor quality network elements. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G message service demand, configuration of 5G message demand forecasting rules. Trigger event: UP2.4 end user number prediction rule configuration data export. Functional process: UP2.4 end user number prediction rule configuration data export. Sub-process description: input UP2.4 terminal user number prediction rule configuration export request. Data movement type: E." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice VOLTE call duration analysis data collection. Functional process: 5G voice VOLTE call duration analysis data collection interface. Sub-process description: Receive 5G voice VOLTE call duration analysis data collection request. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, analysis of indicator cause values. Trigger event: Chatbot business index cause value data table generation. Functional process: Chatbot business indicator cause value data statistics (HBASE library). Sub-process description: Save the statistical results of the chatbot business indicator cause value data to the HBASE library. Data movement type: W." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality analysis data export. Trigger event: display of poor quality terminal analysis data. Functional process: Display of poor quality terminal analysis data. Sub-process description: The output shows the poor quality terminal analysis data. Data movement type: X." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent forecasting of 5G voice service demand, 5G voice demand and predicted city rankings and trends. Trigger event: 5G voice EPSFB call duration prediction analysis data query. Functional process: 5G voice EPSFB call duration prediction analysis data query. Sub-process description: Input 5G voice EPSFB call duration prediction analysis data query request. Data movement type: E." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop analysis of indicators. Trigger event: VONR dropped call solution data query. Functional process: VONR dropped call solution data list query. Sub-process description: Output the query result of the VONR dropped call solution data list. Data movement type: X." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: closed-loop management of 5G voice service quality, closed-loop analysis of indicators. Trigger event: VONR indicator closed-loop analysis data export. Functional process: VONR indicator closed-loop analysis data export. Sub-process description: Read closed-loop analysis data of VONR indicator. Data movement type: R." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality terminal analysis. Triggering event: downloading of analysis data of poor-quality terminal delay index factors. Functional process: Download the analysis data of the time delay index factors of poor quality terminals. Sub-process description: read the factor analysis data of the delay index factor of the poor quality terminal. Data movement type: R." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent monitoring of 5G message indicators, analysis of indicator cause values. Trigger event: business failure reason value data query. Functional process: Query the details of the cause value data of business failure. Sub-process description: output the query result of the business failure cause value data details. Data movement type: X." | |
| "Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: VONR intelligent analysis of calling delay, poor quality of terminal delay. Trigger event: terminal EPSFB delay data query. Function process: terminal EPSFB delay data list query. Sub-process description: read terminal EPSFB delay data list information. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service demand, early warning of 5G voice indicators. Trigger event: EPSFB voice indicator warning data deletion. Functional process: EPSFB voice indicator warning data deletion. Sub-process description: Input the EPSFB voice index warning data deletion request. Data movement type: E." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice quality perception analysis, poor quality analysis data export. Trigger event: The analysis data of poor-quality network elements is added. Functional process: The analysis data of poor quality network elements is added. Sub-process description: Return the newly added results of poor-quality network element analysis data. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message quality indicators and trends. Trigger event: Chatbot service quality indicator data query. Functional process: Chatbot service quality indicator data list query. Sub-process description: output the query result of Chatbot business quality index data list. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G message quality perception analysis, 5G message quality terminal analysis. Trigger event: P2P message index data export of poor quality terminals. Functional process: Export the P2P message index data of poor quality terminals. Sub-process description: read the export template of P2P message indicators of poor quality terminals. Data movement type: R." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice service demand intelligent forecasting, 5G voice demand forecasting rule configuration. Trigger event: VOLTE voice demand forecast configuration data is added. Function process: VOLTE voice demand forecast configuration data is added. Sub-process description: Return the new result of VOLTE voice demand forecast configuration data. Data movement type: X." | |
| "Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: 5G voice service demand intelligent forecasting, 5G voice demand forecasting rule configuration. Trigger event: VOLTE voice demand forecast configuration data is added. Function process: VOLTE voice demand forecast configuration data is added. Sub-process description: Read the rules to verify the VOLTE voice demand forecast configuration data. Data movement type: R." | |
| "Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G messaging service indicators, key indicators and trends of business development. Trigger event: 5G messaging business key indicator data query. Functional process: Query the key indicator data list of 5G message business. Sub-process description: Enter a query request for the key indicator data list of the 5G messaging service. Data movement type: E." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: multi-dimensional cluster analysis of 5G message service indicators, 5G message quality indicators and trends. Trigger event: P2P poor quality indicator data query. Functional process: P2P type poor quality index data list query. Sub-process description: output the query result of P2P poor quality index data list. Data movement type: X." | |
| " Customer needs: Improve user perception portraits. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: Intelligent monitoring of 5G message indicators, multi-dimensional aggregation and presentation. Trigger event: Network element fallback aggregation dimension data display. Functional process: Network element fallback aggregation dimension data display. Sub-process description: Input the display request of network element fallback aggregation dimension. Data movement type: E." | |
| " Customer needs: end-to-end analysis of VONR and VOLTE services. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent prediction of 5G voice service requirements, analysis and prediction of 5G call duration. Trigger event: 5G voice VONR call duration analysis data query. Functional process: 5G voice VONR call duration analysis data list query. Sub-process description: Read the 5G voice VONR call duration analysis data list information. Data movement type: R." | |
| " Customer needs: business analysis for special applications. Functional user: the initiator is the user, and the receiver is the mobile network quality analysis system. Functional user requirements: intelligent analysis of VONR calling delay, call auxiliary delay statistics. Trigger event: N26 interface delay data query. Function process: N26 interface delay data list query. Sub-process description: output the N26 interface delay data list query result. Data movement type: X." | |