Telecommunication incoming call priority display method and system based on network slices

Abstract

The invention relates to a telecommunication incoming call priority display method and system based on a network slice, and relates to the field of telecommunication communication, and the method comprises the following steps: S1, when a calling party user terminal initiates a call, a policy control function (PCF) of a home network attaches a currently used network slice identifier and a digital signature to an extension header of an SIP signaling, and the SIP signaling is sent to the calling party user terminal; wherein the digital signature is generated by the PCF through an HMAC-SHA256 algorithm based on a home network certificate; and S2, the called party user terminal receives the call request. Through the deep integration network slicing technology, accurate dynamic display of incoming call priorities is achieved, the user communication efficiency is remarkably improved, the system automatically matches display parameters according to service types by using standardized network slicing identifiers and priority mapping rules, the accuracy and consistency of priority judgment are ensured, and the user experience is improved. Through a digital signature mechanism, the security of signaling transmission is enhanced, tampering of priority information is effectively prevented, and the user experience is improved.

Description

Technical Field

[0001] This invention relates to the field of telecommunications, specifically to a method and system for displaying the priority of incoming calls based on network slicing. Background Technology

[0002] With the development of 5G and future network technologies, network slicing, as a key technology for customizing network resources on demand, is widely used to meet the differentiated needs of various business scenarios. As a basic communication service, the accurate display of call priorities is crucial for improving user communication efficiency and ensuring smooth interaction of critical business processes. In scenarios such as government and enterprise offices, emergency communications, and medical rescue, the ability to quickly identify the priority of incoming calls directly affects the timeliness of user responses to important calls, and the business attributes of network slicing provide the technical basis for distinguishing call priorities.

[0003] Currently, existing telecom caller ID technologies primarily focus on presenting basic information such as phone numbers and contact details, and have not yet developed a priority display mechanism deeply integrated with network slicing technology. Specifically, existing solutions lack standardized mapping rules between network slice identifiers and priorities, making it difficult to automatically match display parameters based on the service type corresponding to the slice. Furthermore, the security verification mechanism for slice information during signaling transmission is inadequate, potentially affecting the accuracy of priority judgment. Simultaneously, different terminals render priority identifiers in inconsistent ways, resulting in varying display effects and failing to meet users' needs for clear priority information identification in diverse scenarios. To address these issues, we propose a telecom caller priority display method and system based on network slicing. Summary of the Invention

[0004] This invention addresses the technical problems existing in the prior art by providing a method and system for displaying the priority of incoming calls based on network slicing. This technical solution solves the problems mentioned above, such as the prior art not integrating with network slicing to achieve call priority display, lacking standardized slice identifiers and priority mapping rules, and being unable to automatically match display parameters according to slice service type; insufficient security verification of slice information in signaling, affecting the accuracy of priority judgment; and inconsistent terminal rendering methods, resulting in different display effects and difficulty in meeting the requirements for clear identification.

[0005] The technical solution of this invention to solve the above-mentioned technical problems is as follows: A method for displaying the priority of incoming calls based on network slicing, comprising the following steps: S1. When the calling user terminal initiates a call, the policy control function (PCF) of the home network appends the currently used network slice identifier and digital signature to the extended header of the SIP signaling, wherein the digital signature is generated by the PCF based on the home network certificate using the HMAC-SHA256 algorithm. S2. After receiving the call request, the called party's user terminal extracts the network slice identifier from the signaling through the called party's service communication agent (SCP) and submits it to the unified data repository (UDR) of the home network to verify the digital signature. S3. When the verification is successful, the Policy Control Function (PCF) generates a display instruction based on the pre-configured slice type and business priority mapping table. The display instruction includes a standardized priority label, icon identifier, and color code. S4. The called party's user terminal parses the display instruction through the operating system's native call interface and calls the system rendering interface to start the terminal rendering process, dynamically rendering the caller's number and associated priority identifier on the incoming call interface. The network slice identifier is Single Network Slice Selection Auxiliary Information (S-NSSAI), and the service priority mapping table is predefined by the operator in the PCF and synchronized to the UDR storage.

[0006] Preferably, in step S1, the extension of the SIP signaling includes: The calling party's Session Management Function (SMF) sends a slice identifier request to the home PCF. The PCF generates a Base64-encoded slice identifier based on the S-NSSAI bound to the current session. PCF calls the home network certificate to perform HMAC-SHA256 signing on the slice identifier and generates a digital signature; The calling party's service communication agent (SCP) encapsulates the slice identifier and digital signature into a custom SIP header field "P-Slice-Info" and transmits it to the called party's network via the initial INVITE request. When the called SCP receives a signal, it separates the slice identifier and digital signature from the "P-Slice-Info" field for verification purposes.

[0007] Preferably, in step S3, the generation of the priority mapping table includes: Operators predefine mapping rules between slice types and service priorities in PCF. The mapping rules include at least a slice type field, a priority level field, and a corresponding display parameter field. The display parameter fields include color encoding, icon identifier, and priority label text; The PCF periodically synchronizes the mapping rules to the UDR of the home network. When the called party's PCF generates a display command, it queries the latest mapping rules through the UDR interface. When a custom priority policy is detected by the enterprise, PCF will prioritize the enterprise policy over the operator's default rules.

[0008] Preferably, in step S3, the generation of display instructions specifically includes: After matching the mapping table based on the slice identifier, PCF generates a JSON-formatted instruction data packet containing three mandatory fields: "priority_label": A string-type text description of the priority level; "color_code": Hexadecimal color code; "icon_id": An index identifier for a predefined icon library; The instruction data packet is sent to the called party's terminal through a dedicated interface between the called party's PCF and the terminal. The terminal parses the instruction and activates the rendering process through the operating system's native call interface.

[0009] Preferably, in step S4, the terminal rendering includes: The called terminal parses the "color_code" field in the JSON command and converts it into the operating system's native color object; Load the pre-set SVG format icon resources based on "icon_id" and scale them losslessly according to the screen resolution; Create a semi-transparent overlay in the top status bar area of ​​the system call interface to fix the display of the priority icon and label text; When a user answers or hangs up a call, the overlay is automatically hidden and the graphics resources are released.

[0010] A network slicing-based telecommunications call priority display system, used to implement the network slicing-based telecommunications call priority display method, includes: The signaling enhancement module, deployed on the calling party's home network as the calling party's service communication agent (SCP), is used to obtain the network slice identifier and digital signature from the calling party's PCF and insert them into the SIP signaling. The security verification module, located in the called party's home network as the called party's service communication agent (SCP), is used to extract the slice identifier from the signaling and submit it to the unified data repository (UDR) to verify the signature validity. The policy execution module, integrated into the policy control function PCF, queries the priority mapping table in the UDR based on the verified slice identifier and generates display instructions containing standardized icon identifiers, color codes, and priority labels. The terminal adaptation module is embedded in the call management framework of the called party's user terminal. It is used to parse the display instructions through the operating system's native call interface and drive the incoming call interface to render the priority identifier. The policy synchronization module is used to synchronize priority policies between the home networks of the calling and called parties via UDR. The system stores the priority mapping table of the calling and called networks and the certificate information required for signature verification through a UDR.

[0011] Preferably, the security verification module includes: The signature extraction unit parses the digital signature and slice identifier plaintext from the "P-Slice-Info" field in the SIP header; The certificate management unit obtains the public key certificate of the calling party's home network from the security credential management center of the home network and stores it in the UDR for verification and invocation; The verification execution unit uses the public key to perform HMAC-SHA256 inverse operation on the digital signature. When the result matches the plaintext of the slice identifier, the policy execution module is triggered. The audit trail unit reports failed call requests to the Network Data Analysis Function (NWDAF) in structured log format via the northbound interface.

[0012] Preferably, the strategy execution module includes: The rule matching unit matches the slice identifier with the mapping table stored in the UDR. If the match fails, it falls back to the default priority. The enterprise policy interface receives custom priority rules issued by the enterprise edge computing platform through the NEF interface; The dynamic degradation unit automatically downgrades the priority of non-high-priority slices when the Network Data Analysis Function (NWDAF) reports core network congestion. The instruction encapsulation unit converts the matching result into a JSON instruction and attaches a PCF digital signature, which is used by the terminal to verify the integrity of the instruction.

[0013] Preferably, the terminal adaptation module includes: The instruction receiving unit captures JSON instructions sent by PCF through the AndroidTelephony service or the iOSCallKit framework; The resource mapping unit queries the terminal's preset icon resource library based on the "icon_id" field and loads vector icon resources; The rendering execution unit calls the system graphics engine to overlay priority labels and icons on the TV layer; The compatibility fallback unit automatically disables the rendering process and displays only the caller ID when the terminal operating system version does not support the feature.

[0014] Preferably, the policy synchronization module includes: The calling party's PCF registers the slice priority policy in the UDR and synchronizes the policy summary to the called party's home network through the N32 interface; After receiving the policy summary, the called party's UDR initiates a policy retrieval request to the local PCF to update the mapping table; When a conflict between the calling and called party's network policies is detected, the called party's local policy is adopted first and a conflict alarm log is generated. The policy version management unit updates the timestamp and scope of each policy record.

[0015] The beneficial effects of this invention are as follows: By deeply integrating network slicing technology, it achieves accurate and dynamic display of incoming call priority, significantly improving user communication efficiency. The system utilizes standardized network slice identifiers and priority mapping rules to automatically match display parameters according to service type, ensuring the accuracy and consistency of priority judgment. The digital signature mechanism enhances the security of signaling transmission, effectively preventing tampering with priority information. In terms of terminal rendering, the system supports a unified cross-platform rendering method, ensuring clear display of priority identifiers on different terminals, improving user experience. It has a flexible policy synchronization and conflict resolution mechanism, which can adapt to the priority management needs of different network environments, providing strong communication support for scenarios such as government and enterprise offices and emergency communications. Attached Figure Description

[0016] Figure 1 This is a flowchart of the method of the present invention; Figure 2 This is a system module diagram of the present invention. Detailed Implementation

[0017] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0018] In the description of this application, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the stated features. In the description of this application, "multiple" means two or more, unless otherwise explicitly specified.

[0019] In the description of this application, the term "for example" is used to mean "used as an example, illustration, or description." Any embodiment described as "for example" in this application is not necessarily to be construed as being more preferred or advantageous than other embodiments. The following description is provided to enable any person skilled in the art to make and use the invention. Details are set forth in the following description for purposes of explanation. It should be understood that those skilled in the art will recognize that the invention can be made without using these specific details. In other instances, well-known structures and processes will not be described in detail to avoid obscuring the description of the invention with unnecessary detail. Therefore, the invention is not intended to be limited to the embodiments shown, but is consistent with the broadest scope of the principles and features disclosed in this application.

[0020] Example 1: A method for displaying the priority of incoming calls in telecommunications based on network slicing, refer to... Figure 1 As shown, its core lies in using network slice identifiers to transmit service priority information and ensuring the authenticity and reliability of the information through a secure end-to-end signaling process, ultimately achieving an intuitive visual presentation on the terminal interface. The entire process begins with the calling party initiating a call. During the call establishment process, the Policy Control Function (PCF) of the calling party's home network is responsible for attaching the network slice identifier bound to the current session to the signaling. This network slice identifier uses the standard Single Network Slice Selection Auxiliary Information (S-NSSAI). To ensure that this identifier is not tampered with during transmission, the PCF generates a message authentication code using a key based on the digital certificate held by its home network. Specifically, the HMAC-SHA256 algorithm is used to digitally sign the S-NSSAI. HMAC-SHA256 was chosen because it achieves a good balance between security and computational efficiency, effectively resisting forgery and replay attacks, and meeting telecommunications-grade security requirements. After generating the signature, the calling party's Service Communication Agent (SCP) is responsible for encapsulating the plaintext S-NSSAI and its corresponding digital signature into a custom SIP extended header field named "P-Slice-Info". This encapsulation operation occurs after the calling party's Session Management Function (SMF) requests and obtains the slice identifier information containing the signature from the PCF. The encapsulated "P-Slice-Info" header field is sent to the called party's network along with the initial INVITE request.

[0021] After the called party's user terminal receives a call request carrying "P-Slice-Info", the called party's Service Communication Agent (SCP) first extracts the content of this field from the SIP signaling and separates it into two parts: the plaintext S-NSSAI and the digital signature. The extracted information is then submitted to the Unified Data Repository (UDR) of the called party's home network for security verification. The UDR acts as a trust anchor and policy repository. The core of the verification process is to verify the validity of the digital signature. The UDR needs to obtain the public key certificate used for signing by the calling party's home network PCF. This certificate is usually pre-stored in the UDR or can be dynamically obtained through the Security Credentials Management Center (SCMC). The verification execution unit uses the public key to perform an HMAC-SHA256 inverse operation on the received digital signature and compares the result with the received plaintext S-NSSAI. If the two are completely identical, it proves that the S-NSSAI identifier does indeed originate from the calling party's home network PCF and has not been tampered with during transmission; the verification passes. All verification attempts, whether successful or not, are logged by the audit trail unit. In particular, failed verification requests generate structured logs and are reported to the Network Data Analysis Function (NWDAF) for security analysis and troubleshooting.

[0022] Once verification is successful, the policy execution process begins. The Policy Control Function (PCF) of the called party's home network uses the verified S-NSSAI identifier as the query key to access the service priority mapping table stored in the UDR. This mapping table is predefined and maintained by the telecom operator in the PCF, clearly defining the service priority levels corresponding to different S-NSSAI slice types and their visual presentation on the terminal. The mapping rules contain at least three key fields: slice type field, priority level field, and display parameter field. The display parameter field specifically defines how the priority should be displayed on the terminal screen, including standardized priority label text, a unique icon identifier, and specific hexadecimal color coding. The operator-defined mapping table is the foundation, but the system also supports customized policies with higher priorities. When it is detected that the called user belongs to a certain enterprise customer, and that enterprise has pushed custom priority rules through the edge computing platform and the Network Open Function (NEF) interface, the PCF's policy execution module will prioritize the enterprise's policy to override the operator's default rules to meet the unique needs of specific industries or VIP users. Furthermore, the mapping table is not entirely static; the PCF periodically synchronizes its latest version to the UDR to ensure that the called party's PCF can always query the latest rules when generating display commands. Network status information provided by NWDAF also affects policy execution. For example, when NWDAF reports core network congestion, the dynamic degradation unit will automatically and temporarily downgrade the service priority of all non-high-guarantee-level slices to ensure critical communication.

[0023] Based on the mapping table lookup results, the PCF's instruction encapsulation unit generates a standardized display instruction data packet. This data packet uses a lightweight and widely supported JSON format and contains three mandatory fields: the "priority_label" field stores an easy-to-understand priority text description string, the "color_code" field specifies the hexadecimal color code used for rendering, and the "icon_id" field is an index identifier pointing to a specific vector icon in the terminal's predefined icon library. To ensure the integrity and trustworthiness of the instruction itself during its delivery to the terminal, the PCF attaches an HMAC-SHA256 digital signature based on the home network certificate to this JSON data packet. The generated and signed JSON instruction is then securely sent to the called party's terminal through a dedicated interface between the PCF and the user terminal.

[0024] After the called party's terminal receives the display command, its operating system's built-in terminal adaptation module begins operation. The command receiving unit captures the JSON command issued by the PCF through the Telephony service of the Android system or the CallKit framework of the iOS system. The terminal first verifies the PCF signature attached to the command to confirm that the command has not been tampered with and that its source is legitimate. After successful verification, the terminal adaptation module begins to parse the command content. The resource mapping unit searches for and loads the corresponding icon resource from the terminal's local pre-built SVG vector icon resource library based on the "icon_id" field in the JSON command. SVG format vector icons can be losslessly scaled according to the actual resolution of the terminal screen, ensuring a clear and sharp display effect on devices of different sizes and resolutions. At the same time, the hexadecimal color code provided by the "color_code" field is converted into the operating system's native color object. The rendering execution unit then calls the operating system's underlying graphics rendering engine to dynamically render the system's native incoming call user interface. Specifically, the rendering method is to create a semi-transparent overlay in the top status bar area of ​​the system call interface. This overlay permanently displays a combined identifier consisting of a vector icon corresponding to the icon identifier and a priority label text. The use of a semi-transparent overlay and fixed position is designed to clearly and prominently convey the caller's priority information without interfering with the user's viewing of core information such as the caller ID. When the user finally answers or hangs up, this overlay automatically hides, triggering a graphics resource release process. The compatibility fallback unit ensures that the memory resources occupied by related icons and color objects are promptly reclaimed, preventing resource leaks. To ensure broad compatibility, if the terminal detects that its currently running operating system version does not support this priority display feature, the compatibility fallback unit automatically blocks the entire rendering process, and the terminal only displays the standard caller ID information.

[0025] To achieve interoperability across carrier networks, the policy synchronization module plays a crucial role. When the calling party's home network's PCF creates or updates its network slice's priority policy locally, it registers it with the calling party's UDR. Simultaneously, the policy's summary information (including the policy's key identifier, version number, and hash value) is securely synchronized to the called party's home network via the standardized N32 interface between carrier border gateways. Upon receiving the policy summary, the called party's UDR initiates a policy retrieval request to its local PCF. The called party's PCF then requests complete policy details from the calling party's UDR through the UDR interface to update its locally stored priority mapping table. This mechanism of retrieving complete policies based on summaries ensures timely policy synchronization while avoiding unnecessary data transmission. The policy version management unit is responsible for recording the precise update timestamp and effective scope for each priority policy. During policy synchronization, if a conflict is detected between the calling party's policy and the called party's local policy, the system defaults to prioritizing the called party's locally configured policy rules and generates detailed conflict alert logs for network administrator review.

[0026] Example 2: A telecommunications call priority display system based on network slicing, referenced Figure 2 As shown, the telecommunications call priority display system based on the above method is architecturally designed around five core functions: signaling enhancement, security verification, policy enforcement, terminal adaptation, and policy synchronization. The signaling enhancement module is deployed on the calling party's home network's calling-side service communication agent (SCP). Its core responsibility is to act as a bridge between the PCF and SIP signaling. This module receives the S-NSSAI plaintext and its corresponding HMAC-SHA256 digital signature from the calling party's PCF and accurately inserts these two key pieces of information into the extended header "P-Slice-Info" field of the SIP signaling, ensuring that the information is transmitted to the called party with the INVITE request.

[0027] The security verification module, located within the called party's home network's Called-Side Service Communication Proxy (SCP), serves as the first line of defense against deception and tampering. This module comprises several cooperating units: the signature extraction unit is responsible for accurately parsing the plaintext S-NSSAI and digital signature from the "P-Slice-Info" field in the received SIP signaling header. The certificate management unit is responsible for key management, dynamically acquiring or pre-caching the public key certificates used for signing by the calling party's home network's PCF from the home network's Security Credentials Management Center (PCF), and securely storing these certificates in the UDR for easy access. The verification execution unit is the core of the verification process. Using the calling party's public key certificate obtained from the UDR, it performs an HMAC-SHA256 inverse operation on the received digital signature and rigorously compares the result with the received plaintext S-NSSAI. Only a perfect match signifies successful verification and triggers subsequent policy execution procedures. The audit trail unit is responsible for recording all verification activities, especially failed verification attempts. It reports detailed verification results (including caller slice identifier, verification result, timestamp, etc.) in a structured log format to the Network Data Analysis Function (NWDAF) through the standard northbound interface for security monitoring, fault diagnosis, and network optimization.

[0028] The policy execution module is tightly integrated into the policy control function (PCF) and is the center of business logic decision-making. The rule matching unit queries the latest service priority mapping table stored in the UDR in real time based on the verified S-NSSAI identifier transmitted by the security verification module. If the query is successful, the corresponding display parameters (color, icon, label) are obtained; if the query fails (e.g., encountering an unknown S-NSSAI), it automatically falls back to the pre-configured default priority rules. The enterprise policy interface provides the system with high flexibility; it is responsible for receiving and processing custom priority policies issued by the enterprise edge computing platform through the NEF interface. These enterprise policies have the highest priority during matching, directly overriding the default rules defined by the operator. The dynamic degradation unit introduces network status awareness capabilities. When it receives a core network congestion alarm from the network data analysis function (NWDAF), this unit automatically performs temporary degradation processing on the service priorities corresponding to all non-urgent or non-high-security-level slices to ensure the smooth operation of critical communications. The instruction encapsulation unit is responsible for converting the final matching result (whether from the default rule, enterprise rule, or downgraded rule) into a JSON format instruction data packet that the terminal can recognize, and attaching PCF's own HMAC-SHA256 digital signature, which is used by the terminal to verify the integrity and authenticity of the instruction.

[0029] The terminal adaptation module is the system's manifestation on the user device, embedded deep within the call management framework of the called party's terminal operating system. The instruction receiving unit captures JSON display instructions issued by the PCF using the operating system's native communication interface. The resource mapping unit searches for and loads the corresponding SVG vector icon resource from the terminal device's local pre-built icon resource library based on the "icon_id" field in the instruction. The rendering execution unit utilizes the operating system's underlying graphics processing capabilities to precisely overlay and render the priority label text and corresponding vector icon onto the system's native incoming call icon interface. This icon is typically located in the status bar area at the top of the screen and uses a semi-transparent design to ensure it doesn't obscure core incoming call information. The compatibility fallback unit ensures system robustness. When it detects that the terminal operating system version is too old or other reasons prevent support for priority rendering features, this unit gracefully blocks the entire rendering process, and the terminal only displays the most basic caller ID information, ensuring that basic call functions are unaffected.

[0030] The policy synchronization module serves as the link for collaboration between operators or network domains, primarily relying on the UDR (User Dedicated DR). Its core mechanism is as follows: when the PCF (Principal Processing Function) of the calling party's home network creates or updates its network slice priority policy, the complete information of this policy is registered in the calling party's UDR. Simultaneously, a summary of this policy is securely transmitted to the called party's home network via a standardized N32 interface between operator boundaries. Upon receiving the policy summary, the called party's UDR proactively notifies its local PCF, triggering the local PCF to initiate a policy retrieval request to the calling party's UDR, thereby obtaining and updating its local priority mapping table. The policy version management unit records a precise update timestamp, effective scope, and unique version identifier for each stored policy. During policy synchronization, if a rule conflict is detected between the calling party's policy and the called party's existing local policy, the system prioritizes the control of the called party's local network, adopting the called party's local policy rules, and simultaneously generating a detailed conflict alarm log, recording the conflicting policy identifier, version information, and processing results for network operations personnel to analyze and handle. This module ensures that priority policies across different network domains can be synchronized in a timely, accurate, and consistent manner, forming the foundation for cross-network service priority display. The system centrally stores the priority mapping table required by the calling and called networks, the public key certificate information required for signature verification, and the metadata required for policy synchronization through a UDR, thus forming a unified and reliable data hub.

[0031] It should be noted that the descriptions of each embodiment in the above embodiments have different focuses. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0032] Although preferred embodiments of the invention have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including both the preferred embodiments and all changes and modifications falling within the scope of the invention.

[0033] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Therefore, if these modifications and variations fall within the scope of the claims of this invention and their equivalents, this invention also intends to include these modifications and variations.

Claims

1. A method for displaying the priority of incoming telecommunications calls based on network slicing, characterized in that, Includes the following steps: S1. When the calling user terminal initiates a call, the policy control function (PCF) of the home network appends the currently used network slice identifier and digital signature to the extended header of the SIP signaling, wherein the digital signature is generated by the PCF based on the home network certificate using the HMAC-SHA256 algorithm. S2. After receiving the call request, the called party's user terminal extracts the network slice identifier from the signaling through the called party's service communication agent (SCP) and submits it to the unified data repository (UDR) of the home network to verify the digital signature. S3. When the verification is successful, the Policy Control Function (PCF) generates a display instruction based on the pre-configured slice type and business priority mapping table. The display instruction includes a standardized priority label, icon identifier, and color code. S4. The called party's user terminal parses the display instruction through the operating system's native call interface and calls the system rendering interface to start the terminal rendering process, dynamically rendering the caller's number and associated priority identifier on the incoming call interface. The network slice identifier is Single Network Slice Selection Auxiliary Information (S-NSSAI), and the service priority mapping table is predefined by the operator in the PCF and synchronized to the UDR storage.

2. The method for displaying the priority of incoming calls based on network slicing according to claim 1, characterized in that, In step S1, the extension of the SIP signaling includes: The calling party's Session Management Function (SMF) sends a slice identifier request to the home PCF. The PCF generates a Base64-encoded slice identifier based on the S-NSSAI bound to the current session. PCF calls the home network certificate to perform HMAC-SHA256 signing on the slice identifier and generates a digital signature; The calling party's service communication agent (SCP) encapsulates the slice identifier and digital signature into a custom SIP header field "P-Slice-Info" and transmits it to the called party's network via the initial INVITE request. When the called SCP receives a signal, it separates the slice identifier and digital signature from the "P-Slice-Info" field for verification purposes.

3. The method for displaying call priority based on network slicing according to claim 1, characterized in that, In step S3, the generation of the priority mapping table includes: Operators predefine mapping rules between slice types and service priorities in PCF. The mapping rules include at least a slice type field, a priority level field, and a corresponding display parameter field. The display parameter fields include color encoding, icon identifier, and priority label text; The PCF periodically synchronizes the mapping rules to the UDR of the home network. When the called party's PCF generates a display command, it queries the latest mapping rules through the UDR interface. When a custom priority policy is detected, PCF will prioritize the enterprise policy over the operator's default rules.

4. The method for displaying the priority of incoming calls based on network slicing according to claim 1, characterized in that, In step S3, the specific steps for generating the display instruction are: After matching the mapping table based on the slice identifier, PCF generates a JSON-formatted instruction data packet containing three mandatory fields: "priority_label": A string-type text description of the priority level; "color_code": Hexadecimal color code; "icon_id": An index identifier for a predefined icon library; The instruction data packet is sent to the called party's terminal through a dedicated interface between the called party's PCF and the terminal. The terminal parses the instruction and activates the rendering process through the operating system's native call interface.

5. The method for displaying the priority of incoming calls based on network slicing according to claim 1, characterized in that, In step S4, the terminal rendering includes: The called terminal parses the "color_code" field in the JSON command and converts it into the operating system's native color object; Load the pre-set SVG format icon resources based on "icon_id" and scale them losslessly according to the screen resolution; Create a semi-transparent overlay in the top status bar area of ​​the system call interface to fix the display of the priority icon and label text; When a user answers or hangs up a call, the overlay is automatically hidden and the graphics resources are released.

6. A telecommunications call priority display system based on network slicing, characterized in that, A method for implementing a network slicing-based telecommunications call priority display as described in any one of claims 1-5 includes: The signaling enhancement module, deployed on the calling party's home network as the calling party's service communication agent (SCP), is used to obtain the network slice identifier and digital signature from the calling party's PCF and insert them into the SIP signaling. The security verification module, located in the called party's home network as the called party's service communication agent (SCP), is used to extract the slice identifier from the signaling and submit it to the unified data repository (UDR) to verify the signature validity. The policy execution module, integrated into the policy control function PCF, queries the priority mapping table in the UDR based on the verified slice identifier and generates display instructions containing standardized icon identifiers, color codes, and priority labels. The terminal adaptation module is embedded in the call management framework of the called party's user terminal. It is used to parse the display instructions through the operating system's native call interface and drive the incoming call interface to render the priority identifier. The policy synchronization module is used to synchronize priority policies between the home networks of the calling and called parties via UDR. The system stores the priority mapping table of the calling and called networks and the certificate information required for signature verification through a UDR.

7. A telecommunications call priority display system based on network slicing according to claim 6, characterized in that, The security verification module includes: The signature extraction unit parses the digital signature and slice identifier plaintext from the "P-Slice-Info" field in the SIP header; The certificate management unit obtains the public key certificate of the calling party's home network from the security credential management center of the home network and stores it in the UDR for verification and invocation; The verification execution unit uses the public key to perform HMAC-SHA256 inverse operation on the digital signature. When the result matches the plaintext of the slice identifier, the policy execution module is triggered. The audit trail unit reports failed call requests to the Network Data Analysis Function (NWDAF) in structured log format via the northbound interface.

8. A telecommunications call priority display system based on network slicing according to claim 6, characterized in that, The strategy execution module includes: The rule matching unit matches the slice identifier with the mapping table stored in the UDR. If the match fails, it falls back to the default priority. The enterprise policy interface receives custom priority rules issued by the enterprise edge computing platform through the NEF interface; The dynamic degradation unit automatically downgrades the priority of non-high-priority slices when the Network Data Analysis Function (NWDAF) reports core network congestion. The instruction encapsulation unit converts the matching result into a JSON instruction and attaches a PCF digital signature, which is used by the terminal to verify the integrity of the instruction.

9. A telecommunications call priority display system based on network slicing according to claim 6, characterized in that, The terminal adaptation module includes: The instruction receiving unit captures JSON instructions sent by PCF through the AndroidTelephony service or the iOSCallKit framework; The resource mapping unit queries the terminal's preset icon resource library based on the "icon_id" field and loads vector icon resources; The rendering execution unit calls the system graphics engine to overlay priority labels and icons on the TV layer; The compatibility fallback unit automatically disables the rendering process and displays only the caller ID when the terminal operating system version does not support the feature.

10. A telecommunications call priority display system based on network slicing according to claim 6, characterized in that, The policy synchronization module includes: The calling party's PCF registers the slice priority policy in the UDR and synchronizes the policy summary to the called party's home network through the N32 interface; After receiving the policy summary, the called party's UDR initiates a policy retrieval request to the local PCF to update the mapping table; When a conflict between the calling and called party's network policies is detected, the called party's local policy is adopted first and a conflict alarm log is generated. The policy version management unit updates the timestamp and scope of each policy record.

Images