text
stringlengths 439
700
|
---|
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. |
End of preview. Expand
in Dataset Viewer.
README.md exists but content is empty.
Use the Edit dataset card button to edit it.
- Downloads last month
- 35