Telecommunication identification network identification query method, system, electronic equipment and medium

Abstract

The present disclosure provides a telecommunications identification network (TIN) identity query method, system, electronic device, and storage medium to address the technical issue that current mainstream identification technologies struggle to implement a TIN network resolution system. The method includes: a TIN-UE submitting a TIN identification code to a core network, which resolves the TIN identification code in an IMS through the core network, obtains the MEC address where the TIN identification data corresponding to the TIN identification code is located, and forwards the TIN identification code to the MEC corresponding to the MEC address. The TIN identification service in the MEC retrieves the corresponding TIN identification data based on the TIN identification code and returns the TIN identification data to the TIN-UE. This disclosure provides a feasible method for implementing TIN network identity query, achieving secure, fast, efficient, and comprehensive identity resolution and query.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a telecommunication identification network identification query method, a telecommunication identification network identification query system, an electronic device, and a computer-readable storage medium. Background Art

[0002] The Telecommunication Identification Network (TIN) is a novel telecommunications-based identification system that leverages existing network resources, including telecom operators' extensive user base, high-performance networks, high-level security and encryption technologies, efficient mobility management systems, and extensive network resource interfaces. The identification network binds identification resources to corporate or personal identity information, ensuring the reliability of both identification data and identity, while also enabling the mapping of identification to corporate or personal identity information. Identification resolution and routing are crucial components of identification. Its fundamental function is that users enter (or scan) identification codes through various terminals. The resolution system then finds the corresponding identification content (identification data) and returns it to the user terminal. For example, product traceability queries are a typical example of an identification-result feedback application. Building efficient, flexible, and secure resolution services requires a large, secure, stable, and fast data network, complex resolution and routing technologies, and significant investment in system network construction. These factors have impacted the development and adoption of identification technology.

[0003] However, for the telecommunications identification network, the following problems still exist in building a resolution system using existing technologies. Since the DNS (Domain Name System) service is single, its resource description capability is weak, and the resolution results are rigid, it can only provide resolution for IP address identification and cannot meet the diversified and differentiated needs of identification; the identification network needs to meet the needs of a large number of users, storage and query of massive data, distributed storage, and high-quality resolution services. It is difficult for the existing identification network to meet this requirement in the short term; the current technical research on identification resolution mechanisms, data management mechanisms, and security protection solutions is still immature, and some key technologies need further research; the construction of a new identification network requires large investment, a long construction cycle, and is difficult to popularize; the identification network should be scalable, and its architecture must be expandable according to actual needs to ensure that it can meet the needs of massive data and the ever-increasing identification application scenarios. The current mainstream identification technology is difficult to achieve. Summary of the Invention

[0004] In order to at least solve the above-mentioned technical problems existing in the telecommunication identification network construction and parsing system in the prior art, the present disclosure provides a telecommunication identification network identification query method, a telecommunication identification network identification query system, an electronic device and a computer-readable storage medium, which provide a feasible way to implement telecommunication identification network identification query and fully utilize the advantages of existing voice signaling technology such as advanced functions, open functions, security and reliability, and wide coverage; and realize safe, fast, efficient and rich identification resolution and query capabilities.

[0005] In a first aspect, the present disclosure provides a method for querying a telecommunication identification network identification.

[0006] The methods include:

[0007] The telecommunications identification network user terminal TIN-UE submits the TIN identification code to the core network, so that the core network resolves the TIN identification code in the IMS (IP Multimedia Subsystem IP Multimedia Subsystem technology), obtains the MEC (Multi-access Edge Computing) address where the TIN identification data corresponding to the TIN identification code is located, and forwards the TIN identification code to the MEC corresponding to the MEC address. The TIN identification service in the MEC queries the corresponding TIN identification data according to the TIN identification code and returns the TIN identification data to the TIN-UE;

[0008] The TIN-UE receives the TIN identification data returned from the MEC.

[0009] Furthermore, the method further comprises:

[0010] Activate the TIN user terminal TIN-UE's support for TIN services through the IMS service expansion process.

[0011] Further, the activation of TIN-UE support for TIN services includes activation of TIN services by the TIN-UE;

[0012] The TIN service activation of the TIN-UE includes:

[0013] The TIN-UE initiates a TIN service activation request to the AP (Authentication Proxy), which forwards the request to the AS (Application Server). The AS then forwards the request to the TIN service module. The TIN service module modifies TIN-related resources based on the TIN-UE information to support the TIN query service for the TIN-UE. The module then returns a TIN activation success result to the AP, which then forwards the TIN activation success result to the TIN-UE.

[0014] The TIN-UE receives the successful TIN activation result from the AS, and displays the TIN service activation mark on the terminal. The TIN can be queried through the TIN-APP installed on the TIN-UE.

[0015] Furthermore, the activation of TIN-UE support for TIN services also includes authentication of TIN-UE access to services:

[0016] The authentication of the TIN-UE access service includes:

[0017] The TIN-UE and the core network's BSF (Binding Support Function) complete the bootstrapping authentication and generate a shared key Ks;

[0018] The TIN-UE generates the key Ks_NAF for accessing the service and performs an authentication response, initiating an XCAP (XML Configuration Access Protocol) call to the AP. The AP then completes the authentication of accessing the service based on whether the Ks_NAF sent by the UE is consistent with the authentication result calculated by itself.

[0019] Furthermore, before the TIN-UE submits the TIN identification code to the core network, the method further includes:

[0020] TIN-UE submits a TIN identification query request to the base station;

[0021] The TIN-UE establishes an RRC (Radio Resource Control) connection with the base station, allowing the base station to transmit the TIN identification query request to the core network to complete the authentication and NAS (Network Attached Storage) encryption negotiation process between the TIN-UE and the core network. The base station also establishes an IMS signaling bearer for the TIN query request and completes the security configuration of the air interface AS.

[0022] The TIN-UE receives the capability query sent by the base station and reports the TIN capability information, so that the base station interacts with the core network to establish a dedicated bearer for TIN query.

[0023] Further, the TIN-UE submits the TIN identification code to the core network, so that the core network resolves the TIN identification code in the IMS, obtains the MEC address where the TIN identification data corresponding to the TIN identification code is located, and forwards the TIN identification code to the MEC corresponding to the MEC address, including:

[0024] The TIN-UE sends a TIN identification query message to the core network to request the establishment of a TIN query session based on voice signaling. The TIN identification query message includes a TIN identification code, so that the core network forwards the TIN identification query message to the P-CSCF (Proxy Call Session Control Function) in the IMS domain on the TIN-UE side. The P-CSCF forwards the TIN identification query message to the S-CSCF (Serving Call Session Control Function). The S-CSCF then obtains the I-CSCF (Interrogating Call Session Control Function) in the IMS domain where the TIN data storage MEC is located through DNS. The I-CSCF in the TIN data storage MEC domain then obtains the address information of the TIN data storage MEC from the TIN identification query message and sends it to the HSS (Home Subscriber Service). Server, home user server) queries to obtain the S-CSCF registered with the TIN data storage MEC, and then forwards the TIN identification query message to the S-CSCF of the TIN data storage MEC domain, so that the S-CSCF of the TIN data storage MEC domain forwards the TIN identification query message to the P-CSCF of the TIN data storage MEC domain, and the P-CSCF of the TIN data storage MEC domain forwards the TIN identification query message to the MEC of the TIN data storage, so that the MEC of the TIN data storage extracts the TIN identification code from the TIN identification query message.

[0025] In a second aspect, the present disclosure provides a method for querying a telecommunication identification network identification, the method comprising:

[0026] Receive the TIN identification code submitted by the TIN-UE through the core network;

[0027] The core network resolves the TIN identification code in the IMS to obtain the MEC address where the TIN identification data corresponding to the TIN identification code is located;

[0028] The TIN identification code is forwarded to the MEC corresponding to the MEC address, and the TIN identification service in the MEC queries the corresponding TIN identification data according to the TIN identification code, and returns the TIN identification data to the TIN-UE, so that the TIN-UE receives the TIN identification data returned from the MEC and completes the TIN identification query.

[0029] Furthermore, the method further comprises:

[0030] The TIN user information that provides the TIN identification data and the information of the MEC that stores the TIN identification data are compiled into a TIN identification data user profile through OSA-AS (Open Service Architecture). The TIN identification data user profile is stored in the HSS in the form of iFC (Initial Filter Criteria).

[0031] When the S-CSCF receives the Register request and the registration is successful, the S-CSCF downloads the initial filtering rule iFC from the HSS and sends a Register message to the AS specified by the iFC to notify the AS that the user corresponding to the registration request has been registered with the S-CSCF. The AS can obtain user information and service information.

[0032] Furthermore, the method further comprises:

[0033] After receiving the TIN query request, the S-CSCF identifies the service session and then triggers the service to the corresponding AS for processing according to the initial filtering criteria iFC, so that the AS forwards the TIN query request to the TIN-AS (TIN application service) for processing, and the TIN-AS completes the TIN identifier separation and resolution functions.

[0034] Furthermore, the method further comprises:

[0035] If the MEC for storing TIN data is mainly based on a public platform and services and adopts an independent TIN data storage service model, then on the MEC server side, the process of the TIN identification service in the MEC querying the corresponding TIN identification data according to the TIN identification code includes:

[0036] Each user is assigned a virtual SIP (Session Initialization Protocol) number and a complete TIN gateway and SIP protocol stack are deployed to independently complete the reception and feedback of TIN query applications based on voice signaling;

[0037] A public TIN-AS (TIN application server) is set up to receive the query TIN identification code forwarded by each TIN gateway, and to query the TIN identification data corresponding to the corresponding TIN identification code in the TIN-DB (TIN-Data Base TIN database), and submit the TIN identification data to the corresponding TIN gateway. The TIN gateway generates SIP signaling and feeds back the query results to the TIN-UE.

[0038] In a third aspect, the present disclosure provides a telecommunication identification network identification query system, the system including a telecommunication identification network user terminal TIN-UE, the TIN-UE including:

[0039] A first sending module is configured to submit the TIN identification code to the core network, so that the core network performs resolution of the TIN identification code in the IMS, obtains the MEC address where the TIN identification data corresponding to the TIN identification code is located, and forwards the TIN identification code to the MEC corresponding to the MEC address. The TIN identification service in the MEC queries the corresponding TIN identification data according to the TIN identification code, and returns the TIN identification data to the TIN-UE;

[0040] The first receiving module is configured to receive TIN identification data returned from the MEC.

[0041] In a fourth aspect, the present disclosure provides a telecommunication identification network identification query system, the system including an IMS, the IMS including:

[0042] A second receiving module is configured to receive a TIN identification code submitted by a TIN-UE through a core network;

[0043] A parsing module configured to parse the TIN identification code in the IMS through the core network to obtain the MEC address where the TIN identification data corresponding to the TIN identification code is located;

[0044] The second sending module is configured to forward the TIN identification code to the MEC corresponding to the MEC address, and the TIN identification service in the MEC queries the corresponding TIN identification data according to the TIN identification code, and returns the TIN identification data to the TIN-UE, so that the TIN-UE receives the TIN identification data returned from the MEC and completes the TIN identification query.

[0045] In a fifth aspect, the present disclosure provides an electronic device comprising a memory and a processor, wherein the memory stores a computer program. When the processor runs the computer program stored in the memory, the processor executes the telecommunication identification network identification query method as described in any one of the first and second aspects.

[0046] In a sixth aspect, the present disclosure provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the telecommunication identification network identification query method described in any one of the first and second aspects above is implemented.

[0047] Beneficial effects:

[0048] The telecommunication identification network identification query method, telecommunication identification network identification query system, electronic device and storage medium provided in the present disclosure provide a feasible way to realize telecommunication identification network identification query, and fully utilize the advantages of existing voice signaling technology such as advanced functions, open functions, security, reliability and wide coverage; realize the parsing of the virtual number of the TIN data storage MEC corresponding to the TIN identification code and the query and feedback process from the TIN identification code query request to the TIN identification data; realize safe, fast, efficient and rich identification resolution and query capabilities. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] Figure 1 A flowchart of a method for querying a telecommunication identification network identification provided in the first embodiment of the present disclosure;

[0050] Figure 2 The overall architecture diagram of the telecommunication identification network identification query provided by the embodiment of the present disclosure;

[0051] Figure 3 A schematic diagram of a process for activating TIN user terminal support for TIN services through an IMS service extension process provided in an embodiment of the present disclosure;

[0052] Figure 4 A schematic diagram of a successful activation result returned by the TIN service module provided in an embodiment of the present disclosure;

[0053] Figure 5 A schematic diagram of the TIN identification query and response process provided in an embodiment of the present disclosure;

[0054] Figure 6 A flowchart of a method for querying a telecommunication identification network identification provided in the second embodiment of the present disclosure;

[0055] Figure 7 A schematic diagram of the access method of UEs on the TIN query side and the TIN data side and the deployment method of MEC provided in an embodiment of the present disclosure;

[0056] Figure 8 The embodiment of the present disclosure provides an OSA-AS approach to expand IMS

[0057] Detailed architecture diagram for TIM support;

[0058] Figure 9 An architectural diagram illustrating the reception and feedback of TIN query requests on the MEC side of the TIN data storage provided in an embodiment of the present disclosure;

[0059] Figure 10 Another architecture diagram of receiving and responding to TIN query requests on the MEC side of TIN data storage provided in an embodiment of the present disclosure;

[0060] Figure 11 This is an architecture diagram of a TIN-UE provided in the fourth embodiment of the present disclosure;

[0061] Figure 12 This is an architectural diagram of an IMS system provided in Example 5 of the present disclosure;

[0062] Figure 13 This is an architectural diagram of an electronic device provided in Example 6 of the present disclosure. DETAILED DESCRIPTION

[0063] To enable those skilled in the art to better understand the technical solutions of the present disclosure, the present disclosure is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments and drawings described herein are only used to explain the present disclosure, rather than to limit the present disclosure.

[0064] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence; and, in the absence of conflict, the embodiments and features in the embodiments of the present disclosure can be arbitrarily combined with each other.

[0065] The terms used in the embodiments of the present disclosure are for the purpose of describing specific embodiments only and are not intended to limit the present disclosure. The singular forms "a," "an," "the," and "the" used in the embodiments of the present disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0066] In the subsequent description, suffixes such as "module," "component," or "unit" used to represent elements are used only to facilitate the description of the present disclosure and have no specific meaning. Therefore, "module," "component," or "unit" may be used interchangeably.

[0067] The TIN number consists of three parts: the first part is the Identification Country Code (ICC), which is used to identify different countries; the second part is the Identification Memory Code (IMC), which is used to identify and locate the location where the identification code is stored; and the third part is the Identification Subscriber Identification Code (ISIN), which is used to identify a specific user. The IMC is encoded based on the storage location of the identification code, which enables address-based addressing and routing.

[0068] The identification storage code IMC consists of 5 parts:

[0069] {National center node code} + {Regional center / provincial capital node code} + {Local core / edge node code} + {User virtual phone number} + {Edge internal node code}

[0070] The user virtual number is a virtual telephone number of the user used to identify the MEC storing the TIN identification data.

[0071] The PSTN (Public Switched Telephone Network) has evolved from a simple, circuit-switched network primarily focused on voice services to a complex network system that currently provides comprehensive voice and data services. The resolution of telephone numbers during PSTN voice communications is a complex process, with complex call control functions primarily accomplished through the signaling network. The 2G / 3G network primarily uses the packet-based Signaling System 7 (SS7) protocol. During the evolution of the 3G network, soft switching equipment (MSC Server) introduced H.248 and BICC signaling, enabling IP bearer during the network's voice-over-IP transformation. With the popularization of 4G and the introduction of VoLTE networks, IP-based signaling is increasingly being introduced into communication networks. The IMS network has introduced SIP and Diameter signaling, while the core network packet domain, EPC, and PCC have introduced Diameter signaling.

[0072] IMS (IP Multimedia Subsystem), proposed by the 3GPP standards organization based on Release 5, is a universal network architecture for providing multimedia services over IP-based networks. IMS technology further decomposes control layer functions, separating the call session control function (CSCF) and the media gateway control function (MGCF). This makes the network architecture more open and flexible. This addresses challenges unresolved by softswitch technology, such as user mobility support, standard open service interfaces, and flexible third-party service provision. Furthermore, its access-independence makes IMS the foundation for the converged evolution of fixed and mobile networks.

[0073] The 3GPP Release 15 standard confirms that 5G voice inherits the voice architecture of 4G VoLTE and continues to provide voice services based on the IMS. The specific voice solution adopted by operators will depend on the actual 5G deployment model and wireless deployment progress. 5G NSA (non-standalone) Option 3 relies on EPC and LTE network deployment. 3GPP froze the Release 15 NSA standard at the end of 2017. 5G SA (standalone) Option 2 is a standalone construction solution based on comprehensive service-oriented innovation. 3GPP froze the Release 16 SA standard in June 2018. 3GPP Release 16 continues to apply the advantages of a service-oriented architecture to IMS, primarily targeting IoT applications. It enhances the IMS architecture and some interfaces, while also expanding support for interoperability between 5G and 3G.

[0074] VoNR is a technical solution that uses 5G NR to carry voice services. The terminal resides on NR, and both voice and data services are carried on the NR network. When the phone moves to the edge of NR coverage, voice services are switched to LTE. This solution, adopted after large-scale 5G deployment, offers advantages such as short call setup times and high-speed data transmission, resulting in a good user experience. It is a target voice solution.

[0075] MEC is a network functional unit (network element) that provides the services and computing functions required by users at edge nodes in 5G, bringing application services and content closer to users, thereby achieving collaboration with the network and providing users with a reliable, high-quality business experience.

[0076] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field will know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0077] The following is a detailed description of the technical solutions of the present invention and how the technical solutions of the present invention solve the above-mentioned technical problems in the prior art with specific embodiments. It will be understood that in the embodiments of the present application, the execution subject may perform some or all of the steps in the embodiments of the present application, and these steps or operations are merely examples. The embodiments of the present application may also perform other operations or variations of various operations. In addition, the various steps may be performed in different orders as presented in the embodiments of the present application, and it may not be necessary to perform all the operations in the embodiments of the present application. Furthermore, the following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in certain embodiments.

[0078] Figure 1 A flowchart of a method for querying a telecommunication identification network identification provided in the first embodiment of the present disclosure is shown as follows: Figure 1 As shown, the method includes:

[0079] Step S101: The TIN-UE submits the TIN identification code to the core network, which resolves the TIN identification code in the IMS through the core network, obtains the MEC address where the TIN identification data corresponding to the TIN identification code is located, and forwards the TIN identification code to the MEC corresponding to the MEC address. The TIN identification service in the MEC queries the corresponding TIN identification data based on the TIN identification code and returns the TIN identification data to the TIN-UE;

[0080] Step S102: The TIN-UE receives the TIN identification data returned from the MEC.

[0081] With the development of the Internet of Things (IoT), 5G, and information technology, industrial production and various areas of social life are demanding "one-to-one" identification for every person, machine, object, service, content, and even digital objects (such as digital publications). The main functions of identification include distributing, registering, managing, resolving, and routing object identities. However, a mature telecommunications identification network currently lacks, let alone methods for performing identification queries.

[0082] To this end, the embodiment of the present disclosure provides a method for querying a telecommunication identification network identification. The overall architecture is as follows: Figure 2As shown, it includes user terminals (UE), core networks, IMS, and MEC. Due to the evolution from 4G to 5G, the core network includes two technical routes: a transitional 5G voice solution and a new 5G voice route based on 5GC, as well as other voice solutions based on 5G development, such as the 5G core network 5GC (5G Core 5GC) and the 4G core network EPC (Evolved Packet Core), or the core network of 6G technology. By fully leveraging the security, fast, efficient, and rich phone number resolution capabilities of 5G's high-performance voice signaling network, targeted solutions are provided for various scenarios in the evolution from 4G to 5G, realizing the resolution of the virtual number corresponding to the TIN data storage MEC in the TIN identification code, and the process from TIN identification code query request to TIN identification data query and feedback.

[0083] On the TIN-UE side, the terminal can scan the TIN identification code through the TIN-APP to query the TIN identification data stored in the corresponding MEC. The TIN identification code contains the phone number of the TIN data provider, and the service address information and port of the MEC corresponding to the number are stored in the HSS of the IMS. The TIN-UE submits the TIN identification code to the 5G network, parses the TIN through the 5G voice signaling network, obtains the MEC address where the TIN identification data is located, and then transfers the TIN identification code to the MEC corresponding to the MEC address. The TIN identification service in the MEC queries the corresponding TIN identification data based on the TIN identification code and returns the result to the TIN-UE, thus completing the TIN identification query.

[0084] Furthermore, the method further comprises:

[0085] Activate the TIN user terminal TIN-UE's support for TIN services through the IMS service expansion process.

[0086] For the two technical routes, the transitional 5G voice solution based on LTE / EPC and the new 5G voice route based on 5GC (5G Core), the terminal (UE) adopts a unified UE-based SIP / RTP (Real-time Transport Protocol) protocol layer and implements TIN service activation and TIN identification query and response by introducing software DSP (Digital Signal Processing).

[0087] like Figure 3 As shown, TIN service activation uses the IMS service extension process to activate the TIN user terminal TIN-UE's support for TIN services.

[0088] Further, the activation of TIN-UE support for TIN services includes activation of TIN services by the TIN-UE;

[0089] The TIN service activation of the TIN-UE includes:

[0090] The TIN-UE initiates a TIN service activation request to the AP, which forwards the TIN service activation request sent by the UE to the AS, which in turn forwards the TIN service activation request to the TIN service module. The TIN service module modifies TIN-related resources based on the TIN-UE information to support the TIN query service of the applied TIN-UE and returns a TIN activation success result to the AP, which then forwards the TIN activation success result to the TIN-UE.

[0091] The TIN-UE receives the successful TIN activation result from the AS, and displays the TIN service activation mark on the terminal. The TIN can be queried through the TIN-APP installed on the TIN-UE.

[0092] In the 5G VOLTE / VONR system, 3GPP stipulates that after the UE executes the GAA (Generic Authentication Architecture) / GBA (General Bootstrapping Architecture) authentication process, it connects to the AS (Application Server) of IMS through the Ut interface and uses the PUT, DELETE and GET methods of HTTP through XCAP (XML Configuration Access Protocol) to manage the AS, provide business data in the form of XML documents saved on various VoLTE services, and complete the activation, deactivation and query of supplementary services.

[0093] The business process for the added TIN part is as follows:

[0094] The UE initiates a TIN service activation request, and the AP forwards the TIN activation request sent by the UE to the AS;

[0095] AS forwards the TIN service activation request to the TIN service module. The TIN service module modifies TIN-related resources according to the information of TIN-UE, provides support for TIN query service for the applied TIN-UE, and returns the activation success result (such as Figure 4 ) to the AP, which then forwards it to the TIN-UE;

[0096] After the software DSP in the terminal receives the TIN activation result from the AS, it displays the TIN service activation mark on the terminal. TIN query and other services can be performed through the TIN-APP installed on the terminal.

[0097] Furthermore, the activation of TIN-UE support for TIN services also includes authentication of TIN-UE access to services:

[0098] The authentication of the TIN-UE access service includes:

[0099] The TIN-UE and the core network's BSF complete the bootstrapping authentication and generate a shared key Ks;

[0100] The TIN-UE generates the key Ks_NAF for accessing the service and performs an authentication response, initiating an XCAP to the AP so that the AP completes the authentication of accessing the service based on whether the Ks_NAF sent by the UE is consistent with the authentication result calculated by itself.

[0101] Through TIN-UE access service authentication, it can be determined whether the UE is legal and within its valid life cycle.

[0102] Furthermore, before the TIN-UE submits the TIN identification code to the core network, the method further includes:

[0103] TIN-UE submits a TIN identification query request to the base station;

[0104] The TIN-UE establishes an RRC connection with the base station, allowing the base station to transmit the TIN identification query request to the core network to complete the authentication and NAS encryption negotiation process between the TIN-UE and the core network. The base station also establishes an IMS signaling bearer for the TIN query request and completes the security configuration of the air interface AS.

[0105] The TIN-UE receives the capability query sent by the base station and reports the TIN capability information, so that the base station interacts with the core network to establish a dedicated bearer for TIN query.

[0106] Before performing identification query, it is necessary to establish a dedicated bearer channel for TIN query, and the implementation architecture is as follows: Figure 5 As shown, the specific process is as follows

[0107] TIN-UE submits a TIN identification query request;

[0108] The UE and gNodeB establish an RRC connection through RRC SetupRequest and RRCSetupComplete;

[0109] The gNodeB transparently transmits the TIN query request to the 5GC.

[0110] The UE and 5GC complete the authentication and NAS encryption negotiation process through (AUTHENTICATION REQUEST / AUTHENTICATION RESPONSE) and (SECURITY MODE COMMAND / SECURITY MODE COMPLETE);

[0111] The gNodeB establishes an IMS signaling bearer for the TIN query request;

[0112] The gNodeB completes the air interface AS security configuration through (Security Mode Command / Security Mode Complete);

[0113] The gNodeB sends a UE Capability Enquiry to the TIN-UE, and the TIN-UE reports the TIN Capability Information.

[0114] The gNodeB sends an INITIAL CONTEXT SETUP RESPONSE message to the 5GC indicating that the PDU Session is established.

[0115] The gNodeB receives the PDU SESSION RESOURCE MODIFY REQUEST message and establishes a dedicated bearer for TIN query.

[0116] Further, the TIN-UE submits the TIN identification code to the core network, so that the core network resolves the TIN identification code in the IMS, obtains the MEC address where the TIN identification data corresponding to the TIN identification code is located, and forwards the TIN identification code to the MEC corresponding to the MEC address, including:

[0117] The TIN-UE sends a TIN identification query message to the core network to request the establishment of a TIN query session based on voice signaling. The TIN identification query message includes a TIN identification code, which enables the core network to forward the TIN identification query message to the P-CSCF (Proxy-Call Control Service Network Element) in the IMS domain on the TIN-UE side. The P-CSCF forwards the TIN identification query message to the S-CSCF (Serving-Call Control Service Network Element). The S-CSCF then obtains the I-CSCF (Query-Call Control Service Network Element) in the IMS domain where the TIN data storage MEC is located through DNS. The I-CSCF in the MEC domain where the TIN data storage is located obtains the TIN identification code from the TIN-UE side. The address information of the TIN data storage MEC is obtained from the TIN identification query message, and the S-CSCF registered with the TIN data storage MEC is obtained through the HSS query. Then, the TIN identification query message is forwarded to the S-CSCF of the TIN data storage MEC domain, so that the S-CSCF of the TIN data storage MEC domain forwards the TIN identification query message to the P-CSCF of the TIN data storage MEC domain, and the P-CSCF of the TIN data storage MEC domain forwards the TIN identification query message to the MEC of the TIN data storage, so that the MEC of the TIN data storage extracts the TIN identification code from the TIN identification query message.

[0118] Specifically, such as Figure 5 As shown, after establishing a dedicated bearer for TIN query,

[0119] The TIN-UE initiates a SIP INVITE message to the 5GC to request the establishment of a TIN query session based on voice signaling. The Invite message includes the data types (hypertext, voice, video, files, etc.) supported by the returned TIN data, as well as the data rate and size limit. The 5GC forwards the Invite message to the P-CSCF (Proxy-Call Control Service Element) in the IMS domain on the TIN-UE side.

[0120] The P-CSCF forwards the Invite message to the S-CSCF (Service-Call Control Service Network Element). The S-CSCF obtains the I-CSCF (Inquiry-Call Control Service Network Element) of the IMS domain where the TIN data is stored in the MEC through DNS.

[0121] The I-CSCF on the TIN data storage MEC side obtains the address information of the TIN data storage MEC from the Invite message, obtains the S-CSCF registered with the TIN data storage MEC through HSS query, and then forwards the Invite message to the S-CSCF on the TIN data storage MEC side;

[0122] The S-CSCF on the TIN data storage MEC side forwards the Invite message to the P-CSCF, and the P-CSCF forwards the Invite message to the TIN data storage MEC;

[0123] TIN data storage MEC extracts the TIN identification code from the Invite message, then calls the local TIN query service to query the TIN data corresponding to the TIN code, and returns the TIN data to the TIN-UE via the same route as the response to the TIN-UE's Invite message;

[0124] After receiving the returned data, TIN-UE calls the system's TIN APP program to display that the query is complete.

[0125] 3GPP defines the 5G network system (5GS) as consisting of two major components: the 5G access network (5G NR) and the 5G core network (5GC). The 5G network architecture is divided into two modes: NSA (non-standalone) and SA (standalone). The NSA core network is an upgraded version of the 4G EPC (EPC+). The SA model adopts a new service-based network architecture, redefining each network function (NF). SA NFs communicate with each other using a new service-based interface, based on HTTP 2.0 signaling.

[0126] For the different types of 5G networks mentioned above, based on the actual scenarios of 4G to 5G transition, 3GPP provides eight options based on various existing networks. Option 1 is the existing LTE network architecture, Option 2 is the new 5G network architecture, and Options 3 to 8 correspond to the transition solutions from the LTE network architecture to the new 5G network architecture. The corresponding voice solutions can be summarized into two main technical routes:

[0127] 1) A transitional 5G voice solution based on LTE / EPC deploys 5G-NR, with the core network primarily using an upgraded EPC (EPC+) and voice provided by VoLTE over the IP Multimedia Subsystem (IMS).

[0128] 2) The new 5G voice route based on 5G Core (5G Core Network) requires the deployment of 5G-NR and 5G NR. Voice is provided directly by VoNR, and EPS Fallback can also be used to fall back to VoLTE to provide voice. IMS needs to be modified to adapt to the 5G voice solution.

[0129] In the above two technical routes, the terminal (UE) can access the IMS network through the VoLTE business process. The current 5G MODEM chip's VOLTE / VONR solution provides support for the above-mentioned voice processes of 5G. The terminal of this embodiment is based on the UE's SIP / RTP protocol layer. By introducing software DSP, the above-mentioned unified method is adopted for VoLTE and VoNR to implement TIN business activation and TIN identification query and response TIN business.

[0130] The disclosed embodiments fully utilize the resources of the 5G network to effectively overcome the problems existing in the current identity resolution system. The main manifestations are:

[0131] 1. IMS signaling provides a wealth of functions and extensions, which can meet the basic query of TIN identification and more comprehensive query functions;

[0132] 2. High-performance network provides the basic network for high-quality identification network. Ultra-large bandwidth, massive connections, and ultra-low latency are the basic characteristics of 5G networks. From the beginning of system design, 5G has regarded the characteristics of network time delay as an important part of 5G requirements: URLLC (Ultra reliable and low latency communication) ultra-low latency and ultra-high reliable communication to support industry applications with extremely high requirements for latency and reliability, such as smart factories, remote surgery, autonomous driving, etc. Each layer of the 5G user plane (physical layer PHY, media access control layer MAC, radio link control layer RLC) has been optimized to achieve a user plane latency of 0.5ms uplink and 0.5ms downlink, with a cumulative two-way latency of 1ms. mMTC (Massive Machine Type Communication) is one of the three major application scenarios of 5G. Achieving a connection density of 1000K per square kilometer is one of the key performance indicators of 5G networks;

[0133] 3. The voice signaling of the 5G network can complete large-scale phone number resolution. After the user enters the phone number, the terminal of the called number can be resolved in a short time and a reliable call service can be established. The 5G voice signaling network can meet the needs of large user volumes, low latency, and high reliability of resolution from caller to called party;

[0134] 4. The 5G voice signaling network is a mature and widely used network. Many of its technologies have undergone historical evolution and practical application optimization, resulting in extremely high reliability and ubiquity. By fully leveraging the control separation characteristics and new application expansion capabilities of IMS, it is possible to quickly and cost-effectively build an identification network system based on the 5G voice signaling network.

[0135] Due to the openness of IMS, new functions can be easily deployed in the future to meet the needs of evolving new identification application scenarios.

[0136] Therefore, the embodiments of the present disclosure fully utilize the secure, fast, efficient, and rich telephone number resolution capabilities of 5G's high-performance voice signaling network, and provide targeted solutions for various scenarios in the evolution from 4G to 5G, thereby realizing the resolution of the virtual number of the TIN data storage MEC corresponding to the TIN identification code and the process of querying and feedback from the TIN identification code query request to the TIN identification data.

[0137] Figure 6 A flowchart of a method for querying a telecommunication identification network identification provided in the second embodiment of the present disclosure is shown as follows: Figure 6 As shown, the method includes:

[0138] Step S201: receiving the TIN identification code submitted by the TIN-UE through the core network;

[0139] Step S202: The TIN identification code is parsed in the IMS through the core network to obtain the MEC address where the TIN identification data corresponding to the TIN identification code is located;

[0140] Step S203: The TIN identification code is forwarded to the MEC corresponding to the MEC address, and the TIN identification service in the MEC queries the corresponding TIN identification data according to the TIN identification code, and returns the TIN identification data to the TIN-UE, so that the TIN-UE receives the TIN identification data returned from the MEC and completes the TIN identification query.

[0141] The goal of this embodiment is to submit a TIN code query request through a 5G terminal (UE), use the 5G voice channel to resolve the MEC address where the TIN data corresponding to the TIN code is stored, and then the MEC's TIN query function reads the local TIN data and returns it to the UE.

[0142] Furthermore, the method further comprises:

[0143] The TIN user information providing the TIN identification data and the information of the MEC storing the TIN identification data are compiled into a TIN identification data user profile through the OSA-AS, and the TIN identification data user profile is stored in the HSS in the form of an initial filtering criterion iFC;

[0144] When the S-CSCF receives the Register request and the registration is successful, the S-CSCF downloads the initial filtering rule iFC from the HSS and sends a Register message to the AS specified by the iFC to notify the AS that the user corresponding to the registration request has been registered with the S-CSCF. The AS can obtain user information and service information.

[0145] In order to support the process of designing the TIN extension method for 5G terminals (UEs), corresponding extensions need to be made in the core network (5GC / EPC) and IMS network of the 5G network to integrate the TIN identification data query service.

[0146] The TIN identification data query service of IMS is implemented through the following two steps: 1. TIN identification data is provided to the user for registration; 2. S-CSCF triggers the corresponding application service AS based on the service request.

[0147] Among them, TIN identification data provided by user registration includes:

[0148] When a user who provides TIN identification data signs a contract, he / she will provide TIN user information. The information of the MEC storing the TIN identification data will be compiled by OSA-AS into a TIN identification data user profile, and then the TIN identification data user profile will be placed in the HSS in the form of initial filtering criteria.

[0149] Filter Criteria (FCs) are stored in user profiles and help the S-CSCF forward received requests to the appropriate application. When the S-CSCF receives an initial SIP request, it verifies each FC. If a SIP request matches a specific FC, the S-CSCF forwards the SIP request to the application service (AS) corresponding to that FC. Filter criteria include initial filter criteria (iFCs) and subsequent filter criteria (sFCs).

[0150] When the S-CSCF receives the Register request and the registration is successful, the S-CSCF downloads the iFC from the HSS and sends a Register message to the AS specified by the iFC, notifying the AS that the user has registered with the S-CSCF. The AS can then obtain user information and service information.

[0151] Furthermore, the method further comprises:

[0152] After receiving the TIN query request, the S-CSCF identifies the service session and then triggers the service to the corresponding AS for processing according to the initial filtering criteria iFC, so that the AS forwards the TIN query request to the TIN-AS (TIN application service) for processing, and the TIN-AS completes the TIN identifier separation and resolution functions.

[0153] The S-CSCF triggers the corresponding application service (AS) based on the service request, including:

[0154] After receiving a request, the S-CSCF identifies the service session and then triggers the service to the appropriate AS for processing based on initial filtering criteria. These filtering criteria are generated during registration and stored in the user profile. The FC determines how the S-CSCF handles a received request. For example, when the S-CSCF receives the initial INVITE message, it evaluates the initial filtering criteria to determine the next steps.

[0155] When a request is triggered by the S-CSCF to the AS, the AS handles the incoming request in five basic operating modes: inbound user agent, outbound user agent, SIP proxy, third-party call control, and non-participation. TIN query requests are set to inbound user agent mode in the filter rules during registration. The AS forwards the TIN query request to the TIN-AS (TIN application service) for processing. The TIN-AS completes the AS portion of the TIN identifier separation and resolution functions in the 5G terminal (UE) TIN extension method design process.

[0156] Furthermore, the method further comprises:

[0157] If the MEC for storing TIN data is mainly based on a public platform and services and adopts an independent TIN data storage service model, then on the MEC server side, the process of the TIN identification service in the MEC querying the corresponding TIN identification data according to the TIN identification code includes:

[0158] Each user is assigned a virtual SIP number and a complete TIN gateway and SIP protocol stack are deployed to independently complete the reception and feedback of TIN query applications based on voice signaling;

[0159] A public TIN-AS (TIN application server) is set up to receive the query TIN identification code forwarded by each TIN gateway, and to query the TIN identification data corresponding to the corresponding TIN identification code in the TIN-DB (TIN database), and submit the TIN identification data to the corresponding TIN gateway. The TIN gateway generates SIP signaling and feeds back the query results to the TIN-UE.

[0160] For the MEC side of TIN data storage, it mainly completes the registration of the virtual number of the user corresponding to the TIN data storage MEC, the MEC address, the MEC service port number, and the conversion of TIN query requests and query results into 5G voice signaling, thereby realizing the use of 5G voice signaling to complete the TIN identification resolution and query service.

[0161] Furthermore, if MEC is primarily targeted at large enterprises or industrial parks, TIN queries, other TIN service types, and TIN identification subcode allocation need to be easily accessible without going through the operator's operating system. To meet these requirements, after the TIN-GW parses the TIN identification code via voice signaling, TIN subcode operations are completed by the local TIN-ROUTER. Local users can directly configure the TIN-ROUTER to add, allocate, and revoke TIN subcodes. Each user has an independent TIN-AS and TIN-DB, allowing different users to deploy different TIN identification services.

[0162] In order to more clearly describe the technical solution of the present disclosure, the third embodiment of the present disclosure also provides a TIN identification query method, which includes three parts: 1) overall architecture 2) 5G terminal (UE) TIN expansion method 3) implementation of voice signaling fusion TIN identification data service of 5G and IMS network.

[0163] Part I: Overall Architecture

[0164] The TIN identification query method disclosed in this disclosure is implemented based on 5G voice signaling. The overall architecture is as follows: Figure 2 As shown, it includes user terminals (UE), core networks, IMS and MEC. As 4G evolves to 5G, the core network includes the 5G core network 5GC (5GCore5GC) and the 4G core network EPC (Evolved Packet Core). The implementation of this disclosure is located in two parts:

[0165] 1) Mobile terminal part: The 5G terminal (UE) TIN extension method describes the method and signaling process for UE to activate TIN services, analyze TIN identification codes using voice signaling, and query the feedback and display of TIN identification data corresponding to the TIN identification code by MEC;

[0166] 2) 5G Network: Implementation of TIN Data Service for Voice Signaling Integration in 5G and IMS Networks This section describes the method for implementing TIN request to TIN data storage based on voice signaling under different options proposed by 3GPP during the evolution from 4G to 5G.

[0167] Part 2: 5G Terminal (UE) TIN Expansion Method

[0168] 3GPP defines the 5G network system (5GS) as consisting of two major components: the 5G access network (5G NR) and the 5G core network (5GC). The 5G network architecture is divided into two modes: NSA (non-standalone) and SA (standalone). The NSA core network is an upgraded version of the 4G EPC (EPC+). The SA model adopts a new service-based network architecture, redefining each network function (NF). SA NFs communicate with each other using a new service-based interface, based on HTTP 2.0 signaling.

[0169] For the different types of 5G networks mentioned above, based on the actual scenarios of 4G to 5G transition, 3GPP provides eight options based on various existing networks. Option 1 is the existing LTE network architecture, Option 2 is the new 5G network architecture, and Options 3 to 8 correspond to the transition solutions from the LTE network architecture to the new 5G network architecture. The corresponding voice solutions can be summarized into two main technical routes:

[0170] 1) A transitional 5G voice solution based on LTE / EPC deploys 5G-NR, with the core network primarily using an upgraded EPC (EPC+) and voice provided by VoLTE over the IP Multimedia Subsystem (IMS).

[0171] 2) The new 5G voice route based on 5G Core (5G Core Network) requires the deployment of 5G-NR and 5G NR. Voice is provided directly by VoNR, and EPS Fallback can also be used to fall back to VoLTE to provide voice. IMS needs to be modified to adapt to the 5G voice solution.

[0172] In both technical routes, the terminal (UE) can access the IMS network through the VoLTE service process. The current 5G MODEM chip's VoLTE / VonR solution supports the above-mentioned 5G voice processes. The terminal of this embodiment is based on the UE's SIP / RTP protocol layer and, by introducing software DSP, implements TIN services for VoLTE and VoNR in the following unified manner:

[0173] 3) TIN service activation

[0174] In the 5G VOLTE / VONR system, 3GPP stipulates that after the UE executes the GAA / GBA authentication process, it connects to the AS (Application Server, VoLTE application server) of IMS through the Ut interface and uses the PUT, DELETE and GET methods of HTTP through XCAP (XML Configuration Access Protocol) to manage the AS, provide service data in the form of XML documents stored on various VoLTE services, and complete the activation, deactivation and query of supplementary services. This embodiment uses the process of IMS extended services to activate the support of TIN user terminal (TIN-UE) for TIN services, such as Figure 3 As shown, the specific implementation process is as follows:

[0175] The BSF (Binding Support Function) of TIN-UE and 5GC completes the bootstrapping authentication and generates a shared key Ks;

[0176] TIN-UE generates the key Ks_NAF for accessing the service, calculates the authentication response, and initiates XCAP;

[0177] The AP completes the authentication of the access service based on whether the Ks_NAF sent by the UE is consistent with the authentication result calculated by itself;

[0178] The UE initiates a TIN service activation request, and the AP forwards the TIN activation request sent by the UE to the AS;

[0179] AS forwards the TIN service activation request to the TIN service module. The TIN service module modifies TIN-related resources according to the information of TIN-UE, provides support for TIN query service for the applied TIN-UE, and returns the activation success result (such as Figure 4 ) to the AP, which transfers it to the TIN-UE;

[0180] After the software DSP receives the TIN activation result from the AS, it displays the TIN service activation mark on the terminal. You can perform TIN query and other services through the TIN-APP installed on the terminal.

[0181] 4) TIN identification query and response

[0182] After TIN-UE activates the TIN service, it can scan the TIN identification code through TIN-APP to query the TIN identification data stored in the corresponding MEC. The TIN identification code contains the phone number of the TIN data provider, so the service address information and port of the MEC corresponding to the number are saved in the HSS of IMS. TIN-UE submits the TIN identification code to the 5G network, parses the TIN through the 5G voice signaling network, obtains the MEC address where the TIN identification data is located, and then transfers the TIN identification code to the MEC address. The TIN identification service in MEC queries the corresponding TIN identification data based on the TIN identification code and returns the result to TIN-UE, thereby completing the TIN identification query. The implementation architecture is as follows: Figure 5 As shown, the specific process is as follows:

[0183] TIN-UE submits a TIN identification query request;

[0184] The UE and gNodeB establish an RRC connection through RRC SetupRequest and RRCSetupComplete;

[0185] The gNodeB transparently transmits the TIN query request to the 5GC.

[0186] The UE and 5GC complete the authentication and NAS encryption negotiation process through (AUTHENTICATION REQUEST / AUTHENTICATION RESPONSE) and (SECURITY MODE COMMAND / SECURITY MODE COMPLETE);

[0187] The gNodeB establishes an IMS signaling bearer for the TIN query request;

[0188] The gNodeB completes the air interface AS security configuration through (Security Mode Command / Security Mode Complete);

[0189] The gNodeB sends a UE Capability Enquiry to the TIN-UE, and the TIN-UE reports the TIN Capability Information.

[0190] The gNodeB sends an INITIAL CONTEXT SETUP RESPONSE message to the 5GC indicating that the PDU Session is established.

[0191] The gNodeB receives the PDU SESSION RESOURCE MODIFY REQUEST message and establishes a dedicated bearer for TIN query;

[0192] The TIN-UE initiates a SIP INVITE message to the 5GC to request the establishment of a TIN query session based on voice signaling. The Invite message includes the data types (hypertext, voice, video, files, etc.) supported by the returned TIN data, as well as the data rate and size limit. The 5GC forwards the Invite message to the P-CSCF (Proxy-Call Control Service Element) in the IMS domain on the TIN-UE side.

[0193] The P-CSCF forwards the Invite message to the S-CSCF (Service-Call Control Service Network Element). The S-CSCF obtains the I-CSCF (Inquiry-Call Control Service Network Element) of the IMS domain where the TIN data is stored in the MEC through DNS.

[0194] The I-CSCF on the TIN data storage MEC side obtains the address information of the TIN data storage MEC from the Invite message, obtains the S-CSCF registered with the TIN data storage MEC through HSS query, and then forwards the Invite message to the S-CSCF on the TIN data storage MEC side;

[0195] The S-CSCF on the TIN data storage MEC side forwards the Invite message to the P-CSCF, and the P-CSCF forwards the Invite message to the TIN data storage MEC;

[0196] TIN data storage MEC extracts the TIN identification code from the Invite message, then calls the local TIN query service to query the TIN data corresponding to the TIN code, and returns the TIN data to the TIN-UE via the same route as the response to the TIN-UE's Invite message;

[0197] After receiving the returned data, TIN-UE calls the system's TIN APP program to display that the query is complete.

[0198] Part 3: Implementation of TIN identification data service integrating voice signaling of 5G and IMS networks.

[0199] To support the process designed for the 5G terminal (UE) TIN extension method in the second part, corresponding extensions need to be made in the 5G network core network (5GC / EPC) and IMS network to integrate the TIN identification data query service.

[0200] Based on the actual scenarios of the transition from 4G to 5G, 3GPP provides eight options based on various existing networks. Option 1 is the existing LTE network architecture, Option 2 is the new 5G network architecture, and Options 3 to 8 correspond to the transition solutions from the LTE network architecture to the new 5G network architecture.

[0201] Option 1 is the traditional 4G network architecture with LTE connected to the EPC. Option 6 is a standalone 5G NR connected only to the EPC. Option 8 is a non-standalone 5G NR connected only to the EPC. Option 6 and Option 8 require direct signaling connection between the EPC and 5G NR, which requires major modifications to the EPC. However, during the transition from 4G to 5G, stable 4G operation must be maintained. Therefore, Option 6 and Option 8 deployment scenarios have no practical deployment value and are generally not considered.

[0202] Option 2, Option 3, Option 4, Option 5, and Option 7 are key deployment methods for 5G networks. Among them, the following belong to the NSA networking method:

[0203] 1) Option 2: The core network uses 5G GC and the wireless network uses 5G NR.

[0204] 2) Option 5: The core network adopts 5GC and the wireless network adopts LTE (LTE enhanced).

[0205] The following are NSA networking methods:

[0206] 1) Option 3 (including 3a and 3x): The core network uses EPC, signaling is anchored in LTE, and data is distributed in LTE (3a in EPC, 3x in 5G NR).

[0207] 2) Option 4 (including 4a): The core network uses 5G NR, signaling is anchored in 5G NR, and data is distributed in 5G NR (4a in 5G NR).

[0208] 3) Option 7 (including 7a and 7x): The core network uses 5GC, signaling is anchored on LTE, and data is distributed in LTE (7a in 5GC, 7x in 5G NR).

[0209] The goal of this embodiment is to submit a TIN code query request through a 5G terminal (UE), use the 5G voice channel to resolve the MEC address where the TIN data corresponding to the TIN code is stored, and then the MEC's TIN query function reads the local TIN data and returns it to the UE.

[0210] On the 5G terminal (UE) side, for different 5G deployment modes, the implementation method of the voice signaling of the UE accessing the 5G network can be as follows: Figure 7 The different combinations shown in the TIN query side are implemented as follows:

[0211] 1) Combination Method 1: The control plane is anchored in LTE, and TIN resolution is achieved through voice signaling when registering with IMS via LTE. This method is used in Option 3 mode. The TIN user terminal uses LTE, the control plane is anchored in the EPC core network, and TIN resolution is achieved when registering with IMS via EPC.

[0212] 2) Combination mode 2: Applicable to 5G EPS Fallback mode, TIN user terminals are accessed through 5G NR, and TIN data parsing and fallback are performed through LTE voice signaling;

[0213] 3) Combination method 3: The TIN user terminal accesses 5GC through 5G NR, adopts the technical route of 5G NR carrying voice, registers with IMS through 5GC, and uses voice signaling to implement TIN identification resolution.

[0214] For the 5G terminal (UE), the voice signaling methods of the above combinations 1-3 all access the IMS. Therefore, it is only necessary to expand the function of the IMS, implement TIN signaling to receive the TIN identification code, and implement the function of parsing to the IMS network on the MEC side.

[0215] IMS service applications are mainly divided into three types. According to the different application servers used, they can be divided into services developed based on SIP application servers (SIP-AS), mobile intelligent network services (IM-SSF) and services developed based on open service architecture application programming interfaces (OSA API) (OSA-AS). OSA-AS uses an open network programming interface API (Application Program Interface), which does not require understanding the details of the underlying communication network, so that new applications can access IMS quickly and securely. The service capability server between the S-CSCF and the OSA application server is equivalent to a gateway, mapping the signaling of the OSA API and the ISC interface, making the service and control independent of each other, and realizing the layered structure of the network. Therefore, this embodiment uses the OSA-AS method to expand IMS support for TIM. The specific architecture is as follows Figure 8 As shown:

[0216] The main network elements are introduced as follows:

[0217] The Home Subscriber Server (HSS) stores IMS user subscription information, including basic identification, routing information, and service subscription information. It is a centralized and comprehensive database located at the top layer of the IMS core network architecture. User information in the HSS related to this embodiment includes:

[0218] User information (TIN data storage MEC code, TIN identification code, network address, access port number, virtual number);

[0219] TIN data storage MEC registration and user information storage;

[0220] TIN service contract information (including TIN service types supported in MEC and other service data).

[0221] P-CSCF (Proxy Call Session Control Function): Proxy-transfers the SIP message containing the TIN identification code from the TIN-UE to the S-CSCF or I-CSCF of the MEC home location where the TIN data in the TIN identification code is stored, and its subsequent interactions.

[0222] I-CSCF (Interrogating-CSCF): The roaming TIN-UE access point. The I-CSCF contacts the HSS to obtain the address of the S-CSCF to which the TIN-UE belongs, and forwards all SIP requests and responses to the S-CSCF.

[0223] S-CSCF (SIP-CSCF): The S-CSCF is the core control unit for voice connections. It accepts registration requests forwarded by the P-CSCF, works with the HSS to authenticate the UE and MEC, downloads subscription data from the HSS, performs session routing, allocates connections to the SIP-AS / IM-SSF / OSA-AS service routing based on subscription triggering rules, and provides TIN service-related information to the TIN-UE. The S-CSCF uses a unified ISC interface to connect to the service platform, so that the S-CSCF and SIP-AS, OSA-AS, and IM-SSF all implement the same interface behavior.

[0224] OSA-GW (Open Service Architecture-Gateway): Responsible for providing an interface for the OSA application server and offering secure and fast access for the deployment of TIN's extended applications in the IMS.

[0225] OSA-AS (OSA Application Server): OSA application server, in which TIN's extended functional services are deployed.

[0226] The TIN data query service of IMS is implemented through the following two steps:

[0227] 1. TIN identification data provides user registration:

[0228] When a user who provides TIN identification data signs a contract, he / she will provide TIN user information. The information of the MEC storing the TIN identification data will be compiled by OSA-AS into a TIN identification data user profile, and then the TIN identification data user profile will be placed in the HSS in the form of initial filtering criteria.

[0229] Filter criteria (FC Filter Criteria) are stored in the user profile and help the S-CSCF forward received requests to the appropriate application. When the S-CSCF receives the initial SIP request, it verifies each FC. If the SIP request matches a specific FC, the S-CSCF forwards the SIP request to the application service (AS) corresponding to that FC. Filter criteria include initial filter criteria (iFC) and subsequent filter criteria (sFC).

[0230] When the S-CSCF receives the Register request and the registration is successful, the S-CSCF downloads the iFC from the HSS and sends a Register message to the AS specified by the iFC, notifying the AS that the user has registered with the S-CSCF. The AS can then obtain user information and service information.

[0231] 2. The S-CSCF triggers the corresponding application service AS based on the service request:

[0232] After receiving a request, the S-CSCF identifies the service session and then triggers the service to the appropriate AS for processing based on initial filtering criteria. These filtering criteria are generated during registration and stored in the user profile. The FC determines how the S-CSCF handles a received request. For example, when the S-CSCF receives the initial INVITE message, it evaluates the initial filtering criteria to determine the next steps.

[0233] When a request is triggered by the S-CSCF to the AS, the AS handles the incoming request in five basic operating modes: inbound user agent, outbound user agent, SIP proxy, third-party call control, and non-participation. TIN query requests are set to inbound user agent mode in the filter rules during registration. The AS forwards the TIN query request to the TIN-AS (TIN application service) for processing. The TIN-AS completes the AS-side TIN identifier separation and resolution functions described in the second part of the 5G terminal (UE) TIN extension method design process.

[0234] For the MEC side of TIN data storage, it mainly completes the registration of the virtual number of the user corresponding to the TIN data storage MEC, the MEC address, the MEC service port number, and the conversion of TIN query requests and query results into 5G voice signaling, thereby realizing the use of 5G voice signaling to complete the TIN identification resolution and query service.

[0235] MEC has multiple deployment modes in EPC and 5GC, such as Figure 7 The TIN data side is shown.

[0236] Among them, the MEC methods of EPC connection are:

[0237] 1) Mode 1: MEC and P-GW are deployed together. The UE initiates a TIN query request, which passes through the eNodeB, S-GW, and P-GW to the MEC.

[0238] 2) Method 2: The MEC server is deployed behind the RAN base station aggregation point, or deployed in a single RAN base station. The UE initiates a TIN query request, which passes through the eNodeB and S-GW to the MEC.

[0239] The MEC modes for 5GC connection are:

[0240] 1) Mode 1 (traffic sharing + platform sharing deployment mode): The traffic distribution network elements (UPF / GW-U) and the platform are deployed in the computer room, using a resource sharing model, with relatively low charges;

[0241] 2) Mode 2 (exclusive traffic diversion + exclusive platform deployment mode): The traffic diversion network element (UPF / GW-U) and the platform are deployed in the customer-side access room or on-site customer room. Both the traffic diversion network element and the platform are exclusive to a specific customer.

[0242] 3) Mode 3 (Traffic Sharing + Platform Dedicated Deployment): The UPF / GW-U (traffic distribution network element) is deployed in the core / aggregation room, and the platform is deployed in the customer-side access / field-level edge room. The UPF / GW-U and edge platform are connected via a bearer network or dedicated line, and different customers share the UPF / GW-U (traffic distribution network element).

[0243] For Mode 1 in EPC and Mode 1 in 5GC, since MEC is a public platform and service-oriented, an independent TIN data storage service mode is adopted. Each user is assigned a virtual SIP number, a complete TIN gateway and SIP protocol stack are deployed, and the reception and feedback of TIN query applications based on voice signaling are completed independently. The system sets up a public TIN-AS (TIN application server), receives the query TIN identification code forwarded by TIN-GW, and then queries the TIN identification data corresponding to the TIN query identification in TIN-DB (TIN database), and then submits it to TIN-GW, which generates SIP signaling and feeds back the query results. The structure is as follows Figure 9 As shown:

[0244] 1. TIN-GW (TIN gateway): Responsible for receiving and forwarding signaling corresponding to the user's virtual number to the TIN-SIP unit, separating the TIN identification code from the signaling and forwarding it to the TIN-AS, receiving query results from the TIN-AS, and combining them with the TIN-SIP signaling to form the feedback result;

[0245] 2. TIN-SIP (TIN SIP protocol stack): implements the complete SIP protocol stack for the user's virtual number, and completes the complete SIP signaling protocol including virtual number registration, incoming signaling, incoming feedback signaling, etc.

[0246] 3. TIN-AS (TIN application server): Receives TIN query requests forwarded by TIN-GW, separates the subcodes of the TIN identification code, queries the corresponding TIN identification data from TIN-DB according to the TIN subcode, and then forwards it to TIN-GW.

[0247] 4. TIN-DB (TIN database): TIN data is stored in the form of (TIN identification code-TIN identification data) (key-value). The corresponding TIN identification data can be queried based on the TIN identification code.

[0248] For Mode 2 in EPC and Mode 2 and Mode 3 in 5GC, since MEC is mainly for large enterprises or parks, TIN query and other TIN service types, TIN identification subcode allocation enterprises need to be easy to operate without going through the operator's operating system. Figure 10 In the illustrated architecture, after the TIN-GW parses the TIN identification code from voice signaling, TIN subcode operations are completed by the local TIN-ROUTER. Local users can directly configure the TIN-ROUTER to add, allocate, and revoke TIN subcodes. Each user has an independent TIN-AS and TIN-DB, allowing different users to deploy different TIN identification services.

[0249] The disclosed embodiments fully utilize the advantages of 5G network's advanced voice signaling technology, open functions, security and reliability, and wide coverage, and use the 5G network's voice signaling to build a TIN identification service system, providing a feasible way to implement the identification network. This has positive significance for fully utilizing existing 5G network resources, enriching 5G network applications, cultivating new services in 5G voice networks, and expanding the operator's business ecosystem.

[0250] The fourth embodiment of the present disclosure further provides a telecommunication identification network identification query system, the system comprising a telecommunication identification network user terminal TIN-UE, such as Figure 11 As shown, the TIN-UE includes:

[0251] A first sending module 11 is configured to submit the TIN identification code to the core network, so that the core network performs resolution of the TIN identification code in the IMS, obtains the MEC address where the TIN identification data corresponding to the TIN identification code is located, and forwards the TIN identification code to the MEC corresponding to the MEC address. The TIN identification service in the MEC queries the corresponding TIN identification data according to the TIN identification code, and returns the TIN identification data to the TIN-UE;

[0252] The first receiving module 12 is configured to receive TIN identification data returned from the MEC.

[0253] Furthermore, the TIN-UE further includes an activation module 13;

[0254] The activation module 13 is configured to activate the TIN user terminal TIN-UE's support for TIN services through the IMS service extension process.

[0255] Further, the activation of TIN-UE support for TIN services includes activation of TIN services by the TIN-UE;

[0256] The activation module 13 is specifically configured to activate the TIN service of the TIN-UE, including:

[0257] Initiating a TIN service activation request to the AP through the first sending module 11, so that the AP forwards the TIN service activation request sent by the UE to the AS, so that the AS forwards the TIN service activation request to the TIN service module. The TIN service module modifies TIN-related resources according to the TIN-UE information to provide support for the TIN query service of the applied TIN-UE, and returns a TIN activation success result to the AP, which forwards the TIN activation success result to the TIN-UE.

[0258] The first receiving module 12 receives the successful TIN activation result of the AS, and displays the TIN service activation mark on the terminal. The TIN query can be performed through the TIN-APP installed on the TIN-UE.

[0259] Furthermore, the activation of TIN-UE support for TIN services also includes authentication of TIN-UE access to services:

[0260] The activation module 13 is further configured to perform authentication for TIN-UE access to services, including:

[0261] Complete boot authentication with the core network's BSF and generate a shared key Ks;

[0262] Generate the key Ks_NAF for accessing the service and perform an authentication response, then initiate XCAP to the AP so that the AP can complete the authentication of accessing the service based on whether the Ks_NAF sent by the UE is consistent with the authentication result calculated by itself.

[0263] Furthermore, the TIN-UE further includes a connection module 14,

[0264] The first sending module 11 is further configured to submit a TIN identification query request to the base station before the TIN-UE submits the TIN identification code to the core network;

[0265] The connection module 14 is configured to establish an RRC connection with the base station, so that the base station transmits the TIN identification query request to the core network to complete the authentication and NAS encryption negotiation process between the TIN-UE and the core network; and the base station establishes an IMS signaling bearer for the TIN query request and completes the security configuration of the air interface AS;

[0266] The first receiving module 12 is further configured to receive a capability query sent by a base station and report TIN capability information, so that the base station interacts with the core network to establish a dedicated bearer for TIN query.

[0267] Furthermore, the first sending module 11 is specifically configured to:

[0268] Send a TIN identification query message to the core network to request the establishment of a TIN query session based on voice signaling. The TIN identification query message includes a TIN identification code, so that the core network forwards the TIN identification query message to the P-CSCF (proxy-call control service network element) in the IMS domain of the TIN-UE side. The P-CSCF forwards the TIN identification query message to the S-CSCF (service-call control service network element). The S-CSCF then obtains the I-CSCF (query-call control service network element) in the IMS domain where the TIN data storage MEC is located through DNS. Then the TIN data is stored in the MEC domain. The I-CSCF obtains the address information of the TIN data storage MEC from the TIN identification query message, and obtains the S-CSCF registered with the TIN data storage MEC through the HSS query, and then forwards the TIN identification query message to the S-CSCF of the TIN data storage MEC domain, so that the S-CSCF of the TIN data storage MEC domain forwards the TIN identification query message to the P-CSCF, and the P-CSCF forwards the TIN identification query message to the MEC of the TIN data storage, so that the MEC of the TIN data storage extracts the TIN identification code from the TIN identification query message.

[0269] The fifth embodiment of the present disclosure further provides a telecommunication identification network identification query system, the system including an IMS, such as Figure 12 As shown, the IMS includes:

[0270] A second receiving module 21 is configured to receive a TIN identification code submitted by a TIN-UE through a core network;

[0271] A parsing module 22 is configured to parse the TIN identification code in the IMS through the core network to obtain the MEC address where the TIN identification data corresponding to the TIN identification code is located;

[0272] The second sending module 23 is configured to forward the TIN identification code to the MEC corresponding to the MEC address, and the TIN identification service in the MEC queries the corresponding TIN identification data according to the TIN identification code, and returns the TIN identification data to the TIN-UE, so that the TIN-UE receives the TIN identification data returned from the MEC and completes the TIN identification query.

[0273] Furthermore, the IMS further includes an editing module 24 and a downloading module 25:

[0274] The editing module 24 is configured to edit the TIN user information providing the TIN identification data and the information of the MEC storing the TIN identification data into a TIN identification data user profile through the open service architecture application service OSA-AS, and store the TIN identification data user profile in the HSS in the form of an initial filtering criterion iFC; and

[0275] The download module 25 is configured to download the iFC from the HSS through the S-CSCF when the S-CSCF receives the Register request and the registration is successful, and send a Register message to the AS specified by the iFC to notify the AS that the user corresponding to the registration request has been registered with the S-CSCF, and the AS can obtain user information and service information.

[0276] Furthermore, the IMS further includes an identification module 26;

[0277] The identification module 26 is configured to identify the service session after the S-CSCF receives the TIN query request, and then trigger the service to the corresponding AS for processing according to the iFC, so that the AS forwards the TIN query request to the TIN application service TIN-AS for processing, and the TIN-AS completes the TIN identifier separation and resolution functions.

[0278] Furthermore, if the MEC for storing TIN data is mainly based on a public platform and services and adopts an independent TIN data storage service mode, then on the MEC server side, the process of the TIN identification service in the MEC querying the corresponding TIN identification data according to the TIN identification code includes:

[0279] Each user is assigned a virtual Session Initiation Protocol (SIP) number and a complete TIN gateway and SIP protocol stack are deployed to independently complete the reception and feedback of TIN query applications based on voice signaling;

[0280] A public TIN-AS is set up to receive the query TIN identification code forwarded by each TIN gateway, and to query the TIN identification data corresponding to the corresponding TIN identification code in the TIN database TIN-DB. The TIN identification data is submitted to the corresponding TIN gateway, and the TIN gateway generates SIP signaling to feedback the query result to the TIN-UE.

[0281] The telecommunication identification network identification query system of the embodiment of the present disclosure is used to implement the telecommunication identification network identification query method in method embodiments 1 to 3, so the description is relatively simple. For details, please refer to the relevant description in the previous method embodiments 1 to 2, which will not be repeated here.

[0282] In addition, if Figure 13As shown, embodiment six of the present disclosure further provides an electronic device, including a memory 100 and a processor 200, wherein the memory 100 stores a computer program. When the processor 200 runs the computer program stored in the memory 100, the processor 200 executes the above-mentioned various possible methods.

[0283] The memory 100 is connected to the processor 200 . The memory 100 may be a flash memory, a read-only memory, or other memory. The processor 200 may be a central processing unit or a single-chip microcomputer.

[0284] In addition, an embodiment of the present disclosure further provides a computer-readable storage medium, on which a computer program is stored, and the computer program is used by a processor to execute the above-mentioned various possible methods.

[0285] The computer-readable storage medium includes volatile or nonvolatile, removable or non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules or other data). Computer-readable storage media include, but are not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable read only memory), flash memory or other memory technology, CD-ROM (Compact Disc Read-Only Memory), Digital Versatile Disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer.

[0286] It is understood that the above embodiments are merely exemplary embodiments for illustrating the principles of the present disclosure, and the present disclosure is not limited thereto. Those skilled in the art may make various modifications and improvements without departing from the spirit and substance of the present disclosure, and such modifications and improvements are also considered to be within the scope of protection of the present disclosure.

Claims

1. A method for querying a telecommunication identification network identification, characterized in that: The method comprises: The telecommunications identification network user terminal TIN-UE submits the TIN identification code to the core network, so that the core network resolves the TIN identification code in the IP multimedia subsystem IMS, obtains the mobile edge computing MEC address where the TIN identification data corresponding to the TIN identification code is located, and forwards the TIN identification code to the MEC corresponding to the MEC address. The TIN identification service in the MEC queries the corresponding TIN identification data according to the TIN identification code and returns the TIN identification data to the TIN-UE; The TIN-UE receives the TIN identification data returned from the MEC.

2. The method according to claim 1, characterized in that The method further comprises: Activate the TIN user terminal TIN-UE's support for TIN services through the IMS service expansion process.

3. The method according to claim 2, characterized in that The activation of TIN-UE support for TIN services includes activation of TIN services by TIN-UE; The TIN service activation of the TIN-UE includes: The TIN-UE initiates a TIN service activation request to the service authentication and proxy forwarding unit AP, which forwards the TIN service activation request sent by the UE to the application service AS, which forwards the TIN service activation request to the TIN service module. The TIN service module modifies TIN-related resources based on the TIN-UE information to provide support for the TIN query service of the applied TIN-UE and returns a TIN activation success result to the AP, which then forwards the TIN activation success result to the TIN-UE. The TIN-UE receives the successful TIN activation result from the AS, and displays the TIN service activation mark on the terminal. The TIN can be queried through the TIN-APP installed on the TIN-UE.

4. The method according to claim 3, characterized in that Activating TIN-UE support for TIN services also includes authentication of TIN-UE access to services: The authentication of the TIN-UE access service includes: The binding support function BSF of the TIN-UE and the core network completes the bootstrapping authentication and generates the shared key Ks; The TIN-UE generates the key Ks_NAF for accessing the service and performs an authentication response, initiating an Extensible Markup Language Configuration Access Protocol (XCAP) to the AP, so that the AP completes the authentication of accessing the service based on whether the Ks_NAF sent by the UE is consistent with the authentication result calculated by itself.

5. The method according to claim 1, wherein Before the TIN-UE submits the TIN identification code to the core network, the method further includes: TIN-UE submits a TIN identification query request to the base station; The TIN-UE and the base station establish a radio resource control (RRC) connection, allowing the base station to transmit the TIN identification query request to the core network to complete the authentication and network-attached storage (NAS) encryption negotiation process between the TIN-UE and the core network. The base station also establishes an IMS signaling bearer for the TIN query request and completes the security configuration of the air interface application service (AS). The TIN-UE receives the capability query sent by the base station and reports the TIN capability information, so that the base station interacts with the core network to establish a dedicated bearer for TIN query.

6. The method according to claim 5, characterized in that The TIN-UE submits the TIN identification code to the core network, so that the core network resolves the TIN identification code in the IMS, obtains the MEC address where the TIN identification data corresponding to the TIN identification code is located, and forwards the TIN identification code to the MEC corresponding to the MEC address, including: The TIN-UE sends a TIN identification query message to the core network to request the establishment of a TIN query session based on voice signaling. The TIN identification query message includes a TIN identification code, so that the core network forwards the TIN identification query message to the proxy-call control service network element P-CSCF of the IMS domain on the TIN-UE side. The P-CSCF forwards the TIN identification query message to the service-call control service network element S-CSCF. The S-CSCF then obtains the query-call control service network element I-CSCF of the IMS domain where the TIN data storage MEC is located through the domain name system DNS. Then the I-CSCF of the TIN data storage MEC domain obtains the TIN identification query message from the TIN The address information of the TIN data storage MEC is obtained in the identification query message, and the S-CSCF registered with the TIN data storage MEC is obtained through the home user server HSS. Then, the TIN identification query message is forwarded to the S-CSCF of the TIN data storage MEC domain, so that the S-CSCF of the TIN data storage MEC domain forwards the TIN identification query message to the P-CSCF of the TIN data storage MEC domain, and the P-CSCF of the TIN data storage MEC domain forwards the TIN identification query message to the MEC of the TIN data storage, so that the MEC of the TIN data storage extracts the TIN identification code from the TIN identification query message.

7. A method for querying a telecommunication identification network identification, characterized in that: The method comprises: Receive the TIN identification code submitted by the TIN-UE through the core network; The core network resolves the TIN identification code in the IMS to obtain the MEC address where the TIN identification data corresponding to the TIN identification code is located; The TIN identification code is forwarded to the MEC corresponding to the MEC address, and the TIN identification service in the MEC queries the corresponding TIN identification data according to the TIN identification code, and returns the TIN identification data to the TIN-UE, so that the TIN-UE receives the TIN identification data returned from the MEC and completes the TIN identification query.

8. The method according to claim 7, characterized in that The method further comprises: The TIN user information providing the TIN identification data and the information of the MEC storing the TIN identification data are compiled into a TIN identification data user profile through the open service architecture application service OSA-AS, and the TIN identification data user profile is stored in the HSS in the form of an initial filtering criterion iFC; When the S-CSCF receives the Register request and the registration is successful, the S-CSCF downloads the iFC from the HSS and sends a Register message to the AS specified by the iFC to notify the AS that the user corresponding to the registration request has been registered with the S-CSCF. The AS can obtain user information and service information.

9. The method according to claim 8, characterized in that The method further comprises: After receiving the TIN query request, the S-CSCF identifies the service session and then triggers the service to the corresponding AS for processing according to the iFC, so that the AS forwards the TIN query request to the TIN application service TIN-AS for processing, and the TIN-AS completes the TIN identifier separation and resolution functions.

10. The method according to claim 7, characterized in that The method further comprises: If the MEC for storing TIN data is mainly based on a public platform and services and adopts an independent TIN data storage service model, then on the MEC server side, the process of the TIN identification service in the MEC querying the corresponding TIN identification data according to the TIN identification code includes: Each user is assigned a virtual Session Initiation Protocol (SIP) number and a complete TIN gateway and SIP protocol stack are deployed to independently complete the reception and feedback of TIN query applications based on voice signaling; A public TIN-AS is set up to receive the query TIN identification code forwarded by each TIN gateway, and to query the TIN identification data corresponding to the corresponding TIN identification code in the TIN database TIN-DB. The TIN identification data is submitted to the corresponding TIN gateway, and the TIN gateway generates SIP signaling to feedback the query result to the TIN-UE.

11. A telecommunication identification network identification query system, characterized in that: The system includes a telecommunications identification network user terminal TIN-UE, and the TIN-UE includes: A first sending module is configured to submit the TIN identification code to the core network, so that the core network performs resolution of the TIN identification code in the IMS, obtains the MEC address where the TIN identification data corresponding to the TIN identification code is located, and forwards the TIN identification code to the MEC corresponding to the MEC address. The TIN identification service in the MEC queries the corresponding TIN identification data according to the TIN identification code, and returns the TIN identification data to the TIN-UE; The first receiving module is configured to receive TIN identification data returned from the MEC.

12. A telecommunication identification network identification query system, characterized in that: The system includes an IMS, and the IMS includes: A second receiving module is configured to receive a TIN identification code submitted by a TIN-UE through a core network; A parsing module configured to parse the TIN identification code in the IMS through the core network to obtain the MEC address where the TIN identification data corresponding to the TIN identification code is located; The second sending module is configured to forward the TIN identification code to the MEC corresponding to the MEC address, and the TIN identification service in the MEC queries the corresponding TIN identification data according to the TIN identification code, and returns the TIN identification data to the TIN-UE, so that the TIN-UE receives the TIN identification data returned from the MEC and completes the TIN identification query.

13. An electronic device, characterized in that: The invention comprises a memory and a processor, wherein a computer program is stored in the memory, and when the processor runs the computer program stored in the memory, the processor executes the telecommunication identification network identification query method according to any one of claims 1 to 6 or claims 7 to 10.

14. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method for querying a telecommunication identification network identification according to any one of claims 1 to 6 or claims 7 to 10 is implemented.

Images