text
stringlengths
537
1.44k
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: input VONR drop call solution data list query request. Data movement type: E. Data group: list query operation instruction. Data attributes: operation time, operation type.
Customer needs: 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: save the download data of the cause value of registration failure. Data movement type: W. Data group: Registration failure reason value download data. Data attributes: indicator name, reason for first removal, registration indicator, reason for process failure, first removal SIP status code, reason value for registration failure, first removal message.
Customer needs: 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: Read the key indicator data list information of 5G message business. Data movement type: R. Data group: 5G message business key indicator data list information. Data attributes: the number of successful TCP establishments, the total number of authentications initiated by the terminal to the storage server, the total delay of HTTP responses, key indicators of 5G message services, the total delay of TCP establishments, the average delay of HTTP responses, and the authentication initiated by the terminal on the storage server Success rate, TCP establishment average delay, HTTP business success times.
Customer needs: 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: Configuration data modification of poor quality rules for file transfers. Functional process: Modify the configuration data of the poor quality rule of the file transfer class. Sub-process description: Modify the configuration data of the file transfer class poor quality rule. Data movement type: W. Data group: the configuration data of the file transfer class poor quality rule to be modified. Data attributes: serial number, configuration of poor quality rules for file transfers, poor quality factors of wireless indicators, proportion of poor quality, success rate of file downloads, operators, poor quality factors of core network indicators, success rate of file uploads, poor quality factors of individual user indicators .
Customer needs: 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 export template of poor-quality terminal registration indicators. Data movement type: R. Data group: export template for poor-quality terminal registration indicators. Data attribute: export template for poor quality terminal registration indicators.
Customer needs: 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: Input messaging analysis (P2P) export request. Data movement type: E. Data group: message sending and receiving analysis (P2P) export operation instruction. Data attributes: data time, city, equipment manufacturer.
Customer needs: 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 aggregated dimension data with poor terminal quality. Functional process: Export of aggregated dimension data with poor terminal quality. Sub-process description: Read terminal poor-quality aggregation dimension data. Data movement type: R. Data group: Aggregate dimensional data with poor terminal quality. Data attributes: UP2.4 success rate of terminal users uploading messages to Chatbot, aggregation dimension of poor terminal quality, UP2.4 terminal message center receiving success rate of messages submitted by mobile phones, UP2.4 terminal Large Mode message receiving success rate (group sending), Time period, date, UP2.4 terminal 5G message fallback SMS success rate.
Customer needs: 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. Description of the sub-process: read the configuration data of the rule verification terminal rules for poor business development quality. Data movement type: R. Data group: Configure data verification rules for terminal rules with poor business development quality. Data attributes: non-null check and data format check for terminal rule configuration data with poor business development quality.
Customer needs: 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 reports aggregation dimension data query. Functional process: query the details of aggregated dimension data reported by the community. Sub-process description: Read the detailed data of aggregation dimension reported by the community. Data movement type: R. Data group: Community reports aggregate dimension detail data. Data attributes: Large Mode message receiving success rate (group sending), Large Mode message sending success rate (group sending), user uplink message success rate to Chatbot, city, date, Pager Mode message sending success rate (group sending), community report aggregation Dimensions, Pager Mode message receiving success rate (P2P), re-registration success rate, Pager Mode message sending success rate (P2P).
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: Input cell EPSFB delay derivation request. Data movement type: E. Data group: cell EPSFB delay derivation operation command. Data attributes: data time, city, equipment manufacturer.
Customer needs: 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: Return the modification result. Data movement type: X. Data group: send out the configuration data modification results of poor-quality terminal rules in groups. Data attributes: modification time, change record.
Customer needs: 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 & mass message early warning data table generation. Functional process: P2P & group message early warning data table generation (GP business library). Sub-process description: Generate P2P & group message warning and write abnormal data log. Data movement type: W. Data group: P2P & group message warning abnormal data log. Data attributes: error code, error description, P2P & group message warning exception source data information.
Customer needs: 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: output file transfer indicators city trend analysis data details query results. Data movement type: X. Data group: detailed query results of file transfer indicators, city trend analysis data. Data attributes: 5GM02 interface file download total delay, city, 5GM02 interface file upload success rate, 5GM02 interface file download failure times, 5GM02 interface file upload total delay, threshold value, 5GM02 interface file upload success times, 5GM02 interface file Download the total number of times, date, file transfer indicators city trend analysis.
Customer needs: 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: Input the request for exporting key indicators of 5G message business. Data movement type: E. Data group: operation instruction for exporting key indicators of 5G message business. Data attributes: data time, city, equipment manufacturer.
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 data analysis data for poor-quality terminal connection indicators. Functional process: downloading of factor analysis data for connection indicators of poor quality terminals. Sub-process description: input the request for downloading the factor analysis data of poor-quality terminal access indicators. Data movement type: E. Data group: download operation instruction. Data attributes: download time, download format.
Customer needs: 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: Update the file transfer indicator monitoring rule configuration data. Data movement type: W. Data group: Modified file transfer indicator monitoring rule configuration data. Data attributes: threshold type, effective or not, indicator unit, dynamic threshold position, file transfer indicators, file transfer indicator monitoring rule configuration, poor quality threshold.
Customer needs: 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: business index city trend analysis data list query. Sub-process description: output the query results of the data list of the business index prefecture and city trend analysis. Data movement type: X. Data group: query result of business index city trend analysis data list. Data attributes: HTTP total delay, threshold value, date, business index city trend analysis, city, HTTP average response delay, HTTP business success rate.
Customer needs: 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 P2P index city trend analysis data. Functional process: P2P index city trend analysis data export. Sub-process description: Input the export request of P2P index prefecture and city trend analysis. Data movement type: E. Data group: P2P index city trend analysis and export operation instructions. Data attributes: data time, city, equipment manufacturer.
Customer needs: 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 business quality index data details query. Sub-process description: output Chatbot business quality indicator data details query results. Data movement type: X. Data group: Chatbot service quality index data details query results. Data attributes: date, success rate of downlink messages from Chatbot to users, number of successful uplink messages from UP2.4 terminal users to Chatbot, number of successful downlink messages from UP2.4 terminal Chatbot to users, poor service quality indicators of Chatbot, downlink messages from Chatbot to users The total delay of the message, the total number of messages that the user uploads to the Chatbot, and the number of successful messages that the Chatbot downloads to the user.
Customer needs: 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 terminal group text message number prediction data list query. Sub-process description: Read the forecast data list information of UP2.4 terminal group text messages. Data movement type: R. Data group: UP2.4 terminal group SMS number prediction data list information. Data attribute: forecast of UP2.4 terminal group text message number, district and county, number of UP2.4 terminal group message number this month, n-4 month UP2.4 terminal group message number, city, n-3 UP2.4 terminal group message number Number, n-number of group messages sent by UP2.4 terminals in February, n-number of group messages sent by UP2.4 terminals in May, date.
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: Query the overall VONR delay data of the cell. Functional process: Query the details of the overall VONR delay data of the cell. Sub-process description: output the detailed query results of the overall VONR delay data of the cell. Data movement type: X. Data group: the detailed query result of the overall VONR delay data of the cell. Data attributes: overall cell VONR delay, 5G core network total delay 1 measurement times (VoNR), IMS forwarding and called paging total delay (VoNR), called response total delay (VoNR), 5G core network time Delay 2 (VoNR), IMS domain total delay measurement times (VoNR), wireless total delay measurement times (VoNR).
Customer needs: 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: Input file transfer index city trend analysis data list query request. Data movement type: E. Data group: list query operation instruction. Data attributes: operation time, operation type.
Customer needs: 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: Input the statistics request of poor-quality P2P service data. Data movement type: E. Data group: data statistics operation instructions. Data attributes: statistical date, statistical method, dimension.
Customer needs: 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 table generation (GP business library). Sub-process description: Read the verification rules to verify the cause value data of Chatbot business indicators. Data movement type: R. Data group: Chatbot business indicator cause value data verification rules. Data attributes: last SIP status code, MSRP (REPORT (Req (Status (Code)))), index value, first teardown message, first teardown SIP status code, Chatbot service index reason value, first teardown reason.
Customer needs: 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 is added. Function process: UP2.4 terminal user number prediction rule configuration data is added. Sub-process description: update UP2.4 terminal user number prediction rule configuration data. Data movement type: W. Data group: newly added UP2.4 terminal user number prediction rule configuration data. Data attribute: effective or not, n+1 month UP2.4 terminal 5G message user number growth rate, UP2.4 terminal user number forecast rule configuration, n+7 month UP2.4 terminal 5G message user number growth rate, n+4 month UP2.4 terminal 5G message user growth rate, index forecast historical data months, UP2.4 terminal 5G message user number this month, n+9 UP2.4 terminal 5G message user number growth rate, n+2 month UP2. 4Growth rate of terminal 5G messaging users.
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: Export the overall VONR delay data of the terminal. Data movement type: X. Data group: the overall VONR delay data of the terminal. Data attributes: 5G core network delay 1 (VoNR), tac, connection delay (VoNR), total called response delay (VoNR), total connection delay measurement times (VoNR), overall terminal VONR delay, 5G core network total delay 1 (VoNR), wireless total delay measurement times (VoNR), IMS domain total delay (VoNR), IMS forwarding and called paging delay (VoNR).
Customer needs: 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: export the configuration data of terminal rules with poor service development quality. Data movement type: X. Data group: configuration data of terminal rules with poor business development quality. Data attributes: effective or not, tcp establishment success rate index threshold, http establishment success rate index threshold, poor quality city proportion, http establishment average delay index threshold, tcp establishment average delay index threshold, operator, poor business development quality Terminal rule configuration.
Customer needs: 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 export template of terminal information with poor core network quality. Data movement type: R. Data group: template for exporting terminal information with poor core network quality. Data attribute: template for exporting terminal information with poor core network quality.
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 query. Functional process: cell EPSFB delay data list query. Sub-process description: Read cell EPSFB delay data list information. Data movement type: R. Data group: cell EPSFB delay data list information. Data attributes: EPSFB final call connection times, EPSFB initial call connection average delay, date, EPSFB final call drop average delay, cell EPSFB delay, EPSFB final call drop average delay, EPSFB drop average delay, EPSFB start The total number of calls back down, the number of successful EPSFB final call back down.
Customer needs: 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 download. Functional process: P2P failure reason value data download. Sub-process description: read P2P failure cause value data. Data movement type: R. Data group: P2P failure cause value data. Data attributes: MSRP (REPORT (Req (Status (Code)))), Reason (Protocol), indicator value, P2P failure reason value, first teardown message, last SIP status code, P2P index, process failure reason.
Customer needs: 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: business index city trend analysis data list query. Sub-process description: Input the query request for the list of business indicators, prefecture and city trend analysis data. Data movement type: E. Data group: list query operation instruction. Data attributes: operation time, operation type.
Customer needs: 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: Configuration data modification of poor quality rules for file transfers. Functional process: Modify the configuration data of the poor quality rule of the file transfer class. Sub-process description: Return the modification result. Data movement type: X. Data group: the configuration data modification result of the file transfer class poor quality rule. Data attributes: modification time, change record.
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 query. Functional process: Query the details of IMS domain delay index data. Sub-process description: Input the request for querying the details of IMS domain delay index data. Data movement type: E. Data group: query operation instructions for details. Data attributes: operation time, operator, operation type.
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 query. Functional process: query the details of 5G voice EPSFB user number analysis data. Sub-process description: output the detailed query results of 5G voice EPSFB user number analysis data. Data movement type: X. Data group: 5G voice EPSFB user number analysis data detailed query results. Data attributes: the number of successful initial registration of the called party (EPSFB), the number of times of initial registration delay measurement (EPSFB), the number of failed initial registration of the called party (EPSFB), the number of successful initial registration of the calling party (EPSFB), city, and the number of initial registration of the called party The number of requests (EPSFB), the number of calling initial registration failures (EPSFB), the number of calling initial registration requests (EPSFB), the number of 5G voice EPSFB users, the number of called initial registration delay measurements (EPSFB), the number of initial registration requests ( EPSFB).
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 fallback delay analysis data export. Functional process: EPSFB fallback delay analysis data export. Sub-process description: Read the EPSFB fallback delay analysis export template. Data movement type: R. Data group: EPSFB fallback delay analysis export template. Data attribute: EPSFB fallback delay analysis export template.
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 details of connection index data of poor-quality network elements. Sub-process description: output the detailed query results of connection index data of network elements with poor quality. Data movement type: X. Data group: Query results of the details of connection index data of poor-quality network elements. Data attribute: the number of normal 4G releases after the VoNR call is connected (called), the number of 4G network drops after the VoNR call is connected (called), the number of normal 4G releases after the VoNR call is connected, and the 4G network connection of the VoNR call Number of times (called), poor quality network element connection indicators, number of times VoNR calls fall back to 4G network but not connected (calling), number of times VoNR calls fall back to 4G network after being connected.
Customer needs: 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 detailed query. Sub-process description: Read the detailed data of the P2P index city trend analysis. Data movement type: R. Data set: detailed data of P2P index prefecture and city trend analysis. Data attributes: Pager Mode message sending total delay (P2P), cities, Large Mode message sending total delay (P2P), P2P index city trend analysis, Large Mode MRSP message sending times (P2P), Pager Mode message receiving times (P2P), Large Mode message sending times (P2P), Large Mode MRSP message sending success times (P2P).
Customer needs: 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 mass-poor terminal rules. Functional process: Export rule configuration data for group sending poor quality terminals. Description of the sub-process: Input the configuration export request of group-sending poor-quality terminal rules. Data movement type: E. Data group: batch sending operation instructions for bad quality terminal rule configuration export. Data attributes: data time, city, equipment manufacturer.
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: read the statistical rules and perform statistical calculations on the quality closed-loop data of the EPSFB fallback class. Data movement type: R. Data group: EPSFB fallback quality closed-loop data statistical rules. Data attributes: summary conditions, summary dimensions.
Customer needs: 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: export of P2P & group message warning data. Functional process: P2P & group message early warning data export. Sub-process description: Input P2P & group message warning export request. Data movement type: E. Data group: P2P & group message warning export operation command. Data attributes: data time, city, equipment manufacturer.
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 fallback delay analysis data query. Functional process: EPSFB fallback delay analysis data list query. Sub-process description: output the EPSFB fallback delay analysis data list query result. Data movement type: X. Data group: EPSFB fallback delay analysis data list query result. Data attributes: name of deterioration index, number of days of index deterioration, success rate of EPSFB initial call fall, recovery time of deterioration index, number of index deterioration time periods, success rate of EPSFB final call fallback, proportion of index deterioration period of this month, number of normal time periods of index, EPSFB fallback Time delay analysis, description of deterioration indicators, and normal days of indicators.
Customer needs: 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: registration class indicator analysis data query. Functional process: Query the details of the registration index analysis data. Sub-process description: output the detailed query results of the registration index analysis data. Data movement type: X. Data group: query result of registration index analysis data details. Data attributes: the number of initial registration requests of UP2.4 terminals, the total delay of initial registration, the total delay of re-registration, the number of successful re-registrations, the number of initial registration requests, the number of re-registration requests of UP2.4 terminals, and the analysis of registration indicators.
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: Read the call quality index data of poor quality cells. Data movement type: R. Data group: Call quality index data of poor quality cells. Data attributes: EPSFB (RTP uplink packet loss rate), VoNR (voice) downlink average MOS, EPSFB (RTP uplink MOS), EPSFB call drop rate, city, VoNR (voice) call drop rate, call quality indicators of poor quality cells , the number of poor quality indicators.
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: Analysis data query of low-quality terminal delay index factors. Functional process: Query the details of the analysis data of the delay index factors of poor-quality terminals. Sub-process description: Input a query request for detailed analysis data of delay index factors of poor-quality terminals. Data movement type: E. Data group: query operation instructions for details. Data attributes: operation time, operator, operation type.
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: uploading of on-delay indicator data. Functional process: upload the connection delay index data. Sub-process description: Input the request for uploading the on-delay index data. Data movement type: E. Data group: upload operation instructions. Data attributes: upload time, upload address.
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 table is generated. Functional process: 5G voice VOLTE user number analysis data table generation (GP service library). Sub-process description: Read the verification rules to verify the 5G voice VOLTE user number analysis data. Data movement type: R. Data group: 5G voice VOLTE user number analysis data verification rules. Data attributes: city, date, VOLTE initial registration average delay, VOLTE re-registration average delay, VOLTE network voice connection rate, 5G voice VOLTE user number analysis, VOLTE final call voice network connection rate, VOLTE initial call voice connection rate Average communication delay, VOLTE origination voice response rate.
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: output terminal EPSFB delay data list query results. Data movement type: X. Data group: query result of terminal EPSFB delay data list. Data attributes: EPSFB final call back drop average delay, EPSFB final call back drop success times, EPSFB final call back drop total times, terminal EPSFB delay, EPSFB first call connection average delay, EPSFB first call connection times, EPSFB first call back drop average latency.
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: Generation of IMS domain delay index data table (GP service library). Sub-process description: generate the IMS domain delay index data table. Data movement type: W. Data group: IMS domain latency index data table. Data attributes: IMS forwarding and called paging delay (VNR2VNR), total called response delay (VNR2VNR), total called response delay (VoNR), total called response delay measurement times (VNR2VNR), IMS domain Delay indicators, IMS forwarding and called paging total delay (VoNR), IMS domain total delay measurement times (VNR2VNR), IMS domain delay (VoNR), IMS forwarding and called paging total delay (VoNR) , IMS forwarding and called paging delay (VoNR), IMS domain total delay (VNR2VNR).
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 list query. Sub-process description: Input 5G voice EPSFB call duration prediction analysis data list query request. Data movement type: E. Data group: list query operation instruction. Data attributes: operation time, operation type.
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 query. Functional process: Query the details of cell EPSFB delay data. Sub-process description: output cell EPSFB delay data details query results. Data movement type: X. Data group: query result of cell EPSFB delay data details. Data attributes: EPSFB initial call connection average delay, cell, EPSFB initial call connection times, cell EPSFB delay, EPSFB final call connection times, EPSFB final call drop average delay, date, EPSFB initial call drop total times, EPSFB initial call fallback success times, EPSFB initial call fallback average delay.
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: Read the analysis data of 5G voice VOLTE users. Data movement type: R. Data group: 5G voice VOLTE user number analysis data. Data attributes: VOLTE initial call voice network connection rate, VOLTE initial call voice connection average delay, VOLTE voice connection rate, VOLTE initial call voice connection rate, VOLTE initial call voice response rate, 5G voice VOLTE user number analysis, VOLTE registration average delay, date, VOLTE registration success rate, VOLTE final call voice network completion rate.
Customer needs: 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 query. Functional process: 5G message terminal analysis data list query. Sub-process description: Read the 5G message terminal analysis data list information. Data movement type: R. Data group: 5G message terminal analysis data list information. Data attributes: growth rate of the number of 5G messaging terminals in n+2 months, cities, analysis of 5G messaging terminals, load of 5G messaging terminals this month, number of 5G messaging terminals this month, load of 5G messaging terminals in n+2 months, n+2 The number of 5G message terminals per month, the growth rate of the number of 5G message terminals in n+1 month, the load of 5G message terminals in month n+1, the growth rate of the number of 5G message terminals in month, n+3 months.
Customer needs: 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: data query of group sending failure reason value. Functional process: Query the data list of the cause value of mass sending failure. Sub-process description: Output the query result of the data list of the cause value of mass sending failure. Data movement type: X. Data group: the query result of the data list of the group sending failure reason value. Data attributes: indicator name, MSRP (REPORT (Req (Status (Code)))), first SIP status code, last SIP status code, first reason, reason value, Reason (Protocol), group sending failure reason value.
Customer needs: 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: read UP2.4 terminal user number prediction data. Data movement type: R. Data set: UP2.4 end user forecast data. Data attributes: date, UP2.4 terminal user number forecast, n-2 month UP2.4 terminal 5G message user number, n+1 month UP2.4 terminal 5G message user number, n-3 UP2.4 terminal 5G message user number Number, districts and counties, n+number of UP2.4 terminal 5G message users in February, number of UP2.4 terminal 5G message users this month, n-number of UP2.4 terminal 5G message users in May, n-4 month UP2.4 terminal Number of 5G messaging users.
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: Update the configuration data of VONR poor voice quality registration rules. Data movement type: W. Data group: Deleted VONR poor voice quality registration rule configuration data. Data attributes: the proportion of poor quality indicators in the community, the configuration of VONR voice quality poor registration rules, the proportion of network element quality indicators, the number of users in the community, the quality factors of individual user indicators (according to the number of attempts), the initial registration success of VoNR called rate, poor quality factors of core network indicators (proportion of poor quality core network), and the number of indicators participating in the judgment of poor quality cells.
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 modification. Functional process: Modify the configuration data of EPSFB poor voice quality registration rules. Sub-process description: update EPSFB poor voice quality registration rule configuration data. Data movement type: W. Data group: the modified EPSFB poor voice quality registration rule configuration data. Data attributes: the proportion of poor quality indicators of network elements, the quality factors of individual user indicators (according to the number of attempts), the quality factors of prefectural and city indicators (proportion of poor quality prefectures and cities), the initial registration success rate of EPSFB callers, and the poor quality of terminals Index ratio, EPSFB initial registration success rate, EPSFB poor voice quality registration rule configuration.
Customer needs: 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: Inquiry about the detailed index data of group messages sent by poor-quality terminals. Sub-process description: output the detailed query results of group messages sent by terminals with poor quality. Data movement type: X. Data group: detailed query results of group messages sent by poor-quality terminals. Data attributes: poor-quality terminal mass message indicators, conclusions, average mass message receiving delay, terminal model, wireless network factors, mass message sending success rate, city factors, core network factors, mass message sending average delay, user factors .
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: Export the poor quality terminal analysis data. Data movement type: X. Data set: Poor quality terminal analysis data. Data attributes: poor quality terminal analysis, tac, user factors, terminal model, VoNR call drop-off 4G network completion rate, initial registration success rate, VoNR call drop-back 4G network success rate after connection.
Customer needs: 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: output the detailed query results of UP2.4 terminal 5G message indicator data. Data movement type: X. Data group: UP2.4 terminal 5G message indicator data details query results. Data attributes: UP2.4 terminal Pager Mode message receiving success rate (P2P), UP2.4 terminal 5G message drop-back SMS times, UP2.4 terminal Pager Mode message sending success rate (P2P), UP2.4 terminal Large Mode message sending Number of times (P2P), UP2.4 terminal Large Mode message reception times (P2P), UP2.4 terminal Pager Mode message receiving average delay (P2P), UP2.4 terminal 5G message index, UP2.4 terminal 5G message fallback MMS Times, the number of times UP2.4 terminal Pager Mode messages are successfully received (P2P), and the total number of times UP2.4 terminal 5G messages fall back.
Customer needs: 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: return the export result. Data movement type: X. Dataset: Export results. Data attributes: export start time, end time, success or not.
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 terminals is added. Functional process: The analysis data of poor-quality terminals is added. Sub-process description: input a new request for analysis data of poor-quality terminals. Data movement type: E. Data group: add operation instructions. Data attribute: add person, add time.
Customer needs: 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: registration index analysis data statistics (HBASE library). Sub-process description: read statistical rules to perform statistical calculations on the analysis data of registered indicators. Data movement type: R. Data group: Statistical rules for registration index analysis data. Data attributes: summary conditions, summary dimensions.
Customer needs: 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: Input P2P index city trend analysis data list query request. Data movement type: E. Data group: list query operation instruction. Data attributes: operation time, operation type.
Customer needs: 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 analysis data of business development indicators. Data movement type: R. Data group: analysis data of business development indicators. Data attributes: total TCP establishment delay (wireless side), number of successful HTTP services, total TCP establishment delay (core network), total number of HTTP service requests, analysis of business development indicators, total HTTP response delay, terminal initiated storage server The total number of authentication times and the number of TCP establishment requests.
Customer needs: 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: Input chatbot poor quality terminal rule configuration data modification request. Data movement type: E. Data group: modify the operation instruction. Data attributes: modification person, modification time.
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 fallback delay analysis data export. Functional process: EPSFB fallback delay analysis data export. Sub-process description: return the export result. Data movement type: X. Dataset: Export results. Data attributes: export start time, end time, success or not.
Customer needs: 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: Input the request for exporting group message indicators of poor-quality terminals. Data movement type: E. Data group: Operation instructions for exporting indicators of group messages sent by poor-quality terminals. Data attributes: data time, city, equipment manufacturer.
Customer needs: 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: read the configuration data of business development indicator monitoring rules. Data movement type: R. Data group: business development indicator monitoring rule configuration data. Data attributes: business development indicator monitoring rule configuration, threshold type, indicator unit, KPI proportion, indicator Chinese name, poor quality threshold, and comparison conditions.
Customer needs: 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: export of P2P & group message warning data. Functional process: P2P & group message early warning data export. Sub-process description: Export P2P & group message warning data. Data movement type: X. Data group: P2P & group message early warning data. Data attributes: P2P message terminal load warning threshold, P2P & group message warning, P2P message terminal number growth rate, current P2P message number, P2P message number growth rate, P2P message number growth rate, P2P message number load warning threshold.
Customer needs: 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 processing. Data movement type: W. Data group: analysis data of business development indicators after exception processing. Data attributes: analysis of business development indicators, number of HTTP business successes, total TCP establishment delay (core network), total TCP establishment delay (wireless side), number of successful TCP establishments (core network), number of successful TCP establishments, HTTP response Total delay, the total number of authentications initiated by the terminal to the storage server.
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: download the connection index data of poor-quality cells. Data movement type: W. Data group: poor-quality community connection index data. Data attribute: success rate of 4G network drop after VoNR call is connected, 4G network connection rate of VoNR call drop (caller), 4G network connection rate of VoNR call drop, success rate of 4G network drop after VoNR call is connected (called) , EPS fallback success rate, VoNR call fallback 4G network connection rate (called), prefectures and cities, proportion of poor quality indicators, poor quality community connection indicators.
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 query. Functional process: query IMS domain delay index data list. Sub-process description: Output the query result of the IMS domain delay index data list. Data movement type: X. Data group: the query result of the IMS domain latency index data list. Data attributes: IMS domain delay index, IMS forwarding and called paging total delay (VNR2VNR), IMS domain total delay measurement times (VoNR), IMS domain total delay (VNR2VNR), IMS domain delay (VNR2VNR) , IMS forwarding and called paging total delay measurement times (VNR2VNR), called response total delay (VNR2VNR), IMS forwarding and called paging delay (VoNR), IMS forwarding and called paging total delay (VoNR), the number of total callee response delay measurements (VNR2VNR).
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: Enter a query request for the 5G voice VOLTE call duration analysis data list. Data movement type: E. Data group: list query operation instruction. Data attributes: operation time, operation type.
Customer needs: 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 data list of the cause of registration failure. Sub-process description: read the registration failure cause value data list information. Data movement type: R. Data group: registration failure cause value data list information. Data attributes: last SIP status code, reason value, MSRP (REPORT (Req (Status (Code)))), first demolition SIP status code, indicator value, registration failure reason value, indicator name, registration category indicator.
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 connection rule configuration data query. Functional process: Query the configuration data list of VOLTE poor voice quality connection rules. Sub-process description: read the configuration data list information of VOLTE poor voice quality connection rules. Data movement type: R. Data group: VOLTE poor voice quality connection rule configuration data list information. Data attributes: poor quality factors of prefectural and city indicators (proportion of poor quality prefectures and cities), VOLTE voice quality poor connection rule configuration, network element quality index ratio, VOLTE call drop 4G network connection rate, participation in poor quality cell judgment The number of indicators, the number of users in the community, the proportion of poor terminal quality indicators, the poor quality factors of core network indicators (the proportion of poor quality core network), and the poor quality factors of individual user indicators (according to the number of attempts).
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 display. Functional process: ranking and trend data display of VONR delay. Sub-process description: Input the ranking and trend display request of VONR delay. Data movement type: E. Data group: display operation instructions. Data attributes: request time, requester, request type.
Customer needs: 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: user-aware aggregation dimension data query. Functional process: user-perceived detailed query of aggregated dimension data. Sub-process description: output the detailed query results of user-perceived aggregation dimension data. Data movement type: X. Data group: The user perceives the detailed query results of aggregated dimension data. Data attributes: TCP establishment success rate (core network), HTTP business success rate, TCP establishment success rate (wireless side), UP2.4 terminal user uplink message success rate to Chatbot, user uplink message average delay to Chatbot, date , the aggregation dimension of user perception, time period, and the message success rate of UP2.4 terminal Chatbot downlinking to users.
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: Read the detailed data of 5G voice EPSFB call duration analysis. Data movement type: R. Data group: 5G voice EPSFB call duration analysis detailed data. Data attributes: EPSFB drop rate growth rate, EPSFB called voice call times, EPSFB calling voice call times, EPSFB call connection total delay (switching method), EPSFB call connection total delay measurement times (redirection method) , 5G voice EPSFB call duration analysis, EPSFB total connection delay measurement times (5T5), EPSFB total connection delay (5T5), EPSFB voice call times, EPSFB call connection total delay measurement times (switching mode), EPSFB Growth rate of talk time.
Customer needs: 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 reports aggregation dimension data query. Functional process: query the details of aggregated dimension data reported by the community. Description of the sub-process: Input the query request for the detailed aggregation dimension data reported by the community. Data movement type: E. Data group: query operation instructions for details. Data attributes: operation time, operator, operation type.
Customer needs: 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: save the download data of the business failure cause value. Data movement type: W. Data group: business failure cause value download data. Data attributes: business failure reason value, process failure reason, MSRP (REPORT (Req (Status (Code)))), first teardown reason, first teardown message, Reason (Protocol), indicator name, business development indicator, last SIP status code, the first SIP status code, and the reason value.
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 data list of poor-quality terminal connection index factor analysis data list. Sub-process description: Read the list information of the factor analysis data list of connection indicators of poor-quality terminals. Data movement type: R. Data group: data list information for factor analysis of poor-quality terminal access indicators. Data attributes: user factor, terminal model, factor analysis of poor quality terminal connection indicators, wireless network factors, success rate of 4G network drop after VoNR call is connected, 4G network connection rate of VoNR call drop, prefectural factors, conclusion, core network factor.
Customer needs: 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 details of P2P message index data of poor quality terminals. Sub-process description: Enter a detailed query request for P2P message index data of poor-quality terminals. Data movement type: E. Data group: query operation instructions for details. Data attributes: operation time, operator, operation type.
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: Update VOLTE voice indicator warning data. Data movement type: W. Data group: newly added VOLTE voice indicator warning data. Data attributes: average VOLTE registration delay, VOLTE final call voice connection rate, VOLTE voice connection average delay, VOLTE re-registration average delay, VOLTE initial registration success rate, VOLTE initial call voice connection average delay, VOLTE users Voice response rate, VOLTE initial registration average delay, VOLTE final call voice network connection rate, VOLTE re-registration success rate, VOLTE voice indicator warning.
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: Generate 5G voice VONR user number analysis data table. Data movement type: W. Data group: 5G voice VONR user number analysis data table. Data attributes: VoNR dedicated load establishment failure times (called), cities, VoNR untriggered dedicated load establishment times (calling), VoNR dedicated load establishment failure times (calling), VONR active user number growth rate, 5G voice VONR Analysis of the number of users, and the number of times VoNR is set up (calling).
Customer needs: 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: Inquiry about the detailed index data of group messages sent by poor-quality terminals. Sub-process description: Enter a request for querying the details of indicator data for group messages sent by poor-quality terminals. Data movement type: E. Data group: query operation instructions for details. Data attributes: operation time, operator, operation type.
Customer needs: 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: data query of group sending failure reason value. Functional process: Query the data details of the cause value of group sending failure. Sub-process description: output the detailed query result of the cause value of group sending failure. Data movement type: X. Data group: query result of group sending failure reason value data details. Data attributes: indicator name, first demolition SIP status code, mass sending failure reason value, first demolition message, reason value, MSRP (REPORT (Req (Status (Code)))), Reason (Protocol), first demolition reason, index value, Mass sending indicators, process failure reasons.
Customer needs: 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: Configuration data modification of poor quality rules for file transfers. Functional process: Modify the configuration data of the poor quality rule of the file transfer class. Sub-process description: read the configuration data of the poor quality rule of the file transfer class. Data movement type: R. Data group: configuration data for file transfer class poor quality rules. Data attributes: serial number, configuration of poor quality rules for file transfers, poor quality factors of wireless indicators, proportion of poor quality, success rate of file downloads, operators, poor quality factors of core network indicators, success rate of file uploads, poor quality factors of individual user indicators .
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 network element analysis data. Functional process: display of poor quality network element analysis data. Sub-process description: read the analysis data of poor-quality network elements. Data movement type: R. Data group: poor quality network element analysis data. Data attributes: VoNR call fallback 4G network completion rate (caller), poor quality network element analysis, poor quality network element, EPSFB (RTP downlink MOS), initial registration success rate, EPSFB (RTP uplink packet loss rate), VoNR Calls fall back to the 4G network completion rate, VoNR (voice) downlink average MOS.
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: Save the 5G voice VONR call duration analysis data table to the GP table library. Data movement type: W. Data set: 5G voice VONR call duration analysis data table. Data attributes: the total connection delay (VoNR), the number of normal release times after the VoNR call is connected, the analysis of the 5G voice VONR call duration, the number of times the VoNR call is dropped to the 4G network after the call is connected (calling), the VoNR call is dropped to the 4G network and is not connected Number of times, the number of normal release times after VoNR calls are connected (called), the number of times VoNR calls fall back to the 4G network connection (calling), the number of times VoNR calls fall back to the 4G network connection (called), prefectures and cities.
Customer needs: 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: read Chatbot business indicator monitoring data list information. Data movement type: R. Data group: Chatbot business indicator monitoring data list information. Data attribute: UP2.4 terminal Chatbot downlink message success rate to user, index value, Chatbot downlink message success rate to user, number of attempts, UP2.4 terminal Chatbot downlink message success rate to user, UP2.4 terminal user uplink Message success rate to Chatbot, monitoring of Chatbot service indicators, and total delay of messages uplinked by users to Chatbot.
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: return the export result. Data movement type: X. Dataset: Export results. Data attributes: export start time, end time, success or not.
Customer needs: 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: NE fallback aggregation dimension data query. Functional process: Query the details of NE fallback aggregation dimension data. Description of the sub-process: Input the detailed query request of the NE fallback aggregation dimension data. Data movement type: E. Data group: query operation instructions for details. Data attributes: operation time, operator, operation type.
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: update the configuration data of VOLTE voice quality delay rule. Data movement type: W. Data group: Deleted VOLTE voice quality delay rule configuration data. Data attributes: VOLTE voice quality delay rule configuration, VOLTE initial registration average delay, core network indicators poor quality factors (proportion of poor quality core network), VOLTE re-registration average delay, individual user indicators poor quality factors (according to try times), the proportion of poor quality indicators of network elements, the proportion of poor quality indicators of terminals, and the proportion of poor quality indicators of cells.
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: Input 5G voice VOLTE call duration analysis and export request. Data movement type: E. Data group: 5G voice VOLTE call duration analysis and export operation instructions. Data attributes: data time, city, equipment manufacturer.
Customer needs: 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: display of terminal rule configuration data with poor business development quality. Functional process: Display 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. Data group: configuration data of terminal rules with poor business development quality. Data attributes: effective or not, operator, tcp establishment success rate index threshold, poor quality city proportion, rule name, http establishment average delay index threshold, tcp establishment average delay index threshold, http establishment success rate index threshold, business Develop bad terminal rules for configuration, number, and unit.
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: Generation of IMS domain delay index data table (GP service library). Sub-process description: read IMS domain delay index data. Data movement type: R. Data group: IMS domain latency index data. Data attributes: IMS forwarding and called paging delay (VNR2VNR), total called response delay (VNR2VNR), total called response delay (VoNR), total called response delay measurement times (VNR2VNR), IMS domain Delay indicators, IMS forwarding and called paging total delay (VoNR), IMS domain total delay measurement times (VNR2VNR), IMS domain delay (VoNR), IMS forwarding and called paging total delay (VoNR) , IMS forwarding and called paging delay (VoNR), IMS domain total delay (VNR2VNR).
Customer needs: 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. Description of the sub-process: read the configuration data of the rules to verify the registration of poor-quality terminal rules. Data movement type: R. Data group: register poor quality terminal rules and configure data verification rules. Data attributes: Non-empty verification of configuration data for registration of poor-quality terminal rules, and data format verification.
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: Query of registration index data of poor-quality communities. Functional process: Query the details of registration index data of poor-quality communities. Sub-process description: output the detailed query results of registration index data of poor-quality communities. Data movement type: X. Data group: detailed query results of registration index data of poor-quality communities. Data attributes: proportion of poor quality indicators, community, called initial registration success rate, prefecture, city, poor quality community registration indicators, number of poor quality indicators, initial registration success rate, calling initial registration average delay, calling initial registration Success rate.
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: download of factor analysis data for poor quality terminal registration indicators. Functional process: Download the factor analysis data of poor quality terminal registration indicators. Sub-process description: Input the request for downloading the factor analysis data of poor-quality terminal registration indicators. Data movement type: E. Data group: download operation instruction. Data attributes: download time, download format.
Customer needs: 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 download. Functional process: P2P message detailed list data download. Sub-process description: input P2P message detailed list data download request. Data movement type: E. Data group: download operation instruction. Data attributes: download time, download format.