CN104168289B - A kind of user data query method and device based on IMS network - Google Patents

Abstract

Embodiments of the present invention provide a user data query method and device based on an IMS network, which relate to the field of communication, and can adopt the routing mode of "going out of the IMS network at the nearest and entering the IMS network at a distance" and "exiting the IMS network at a distance and entering the IMS network at the nearest""Routing mode, maximize the use of IMS network, reduce the load pressure of PSTN network. The method includes: the server receives the query request sent by the call processing device, the query request includes the number of the called user and a tag, and the tag is used to instruct the server to query the data area of the user data; according to the number of the called user, in the data area indicated by the tag Query the user data of the called user in the process, and obtain the query result of the user data, the query result is used to represent the routing mode adopted by the network to which the server belongs; and send the query result to the call processing device.

Description

A user data query method and device based on IMS network

technical field

The invention relates to the communication field, in particular to an IMS network-based user data query method and device.

Background technique

With the continuous progress of communication technology and the continuous improvement of user requirements, the network architecture that can provide high-quality voice and video and other multimedia services is gradually becoming a hot spot in the development of communication networks. 3GPP (Third Generation Partnership Project, Third Generation Partnership Project) proposed IMS (Internet Protocol Multimedia Subsystem, IP Multimedia Subsystem) in its R5 (Release5) version, in order to provide richer multimedia services.

In the IMS network, the ENUM (Telephone Number Mapping, telephone number mapping) server can complete the conversion of the E.164 telephone number of the IMS user to the SIP URI (Session Initiation Protocol Uniform Resource Identifier, the general resource identifier of the session initiation protocol), that is, the ENUM server The telephone number of the IMS user can be converted from a TEL URI (Telephone Uniform Resource Identifier, telephone universal resource identifier) to a SIP URI. At present, ENUM servers are divided into national first-level ENUM servers and provincial second-level ENUM servers in the enterprise standards of Chinese communication operators. Among them, the corresponding relationship between the area code of the telephone number and the domain name or IP address of the second-level ENUM server in each province is stored in the national first-level ENUM server, and the telephone number of the IMS network user in the province is stored in the provincial second-level ENUM server. TEL URI Data converted to SIP URI.

In the prior art, based on the storage principles of user data in the ENUM servers at all levels above, the method of querying the user data stored in the ENUM server is as follows: the network element device on the calling side sends a query request containing the number of the called user to the calling Second-level ENUM server on the calling side; when the second-level ENUM server on the calling side determines that the number of the called user is a remote number, it forwards the query request to the first-level ENUM server; The IP address of the corresponding second-level ENUM server on the called side, and forward the query request to the second-level ENUM server on the called side according to the IP address; number, and send the SIP URI of the called user's number to the first-level ENUM server, if the called user is not an IMS user, then send no such user to the first-level ENUM server; the first-level ENUM server will query the result (called SIP URI of the number of the calling user or no such user) to the secondary ENUM server at the calling side; the secondary ENUM server at the calling side sends the query result to the network element device at the calling side.

Using the above user data query method, when an IMS user dials a non-IMS user in a different place, the network element device on the calling side can only obtain the query result that there is no such user, so that the long-distance call traffic is carried by the PSTN long-distance network, that is, only " the nearest IMS network" routing method. When a non-IMS user dials a remote IMS user, the long-distance traffic is also carried by the PSTN long-distance network. Network" routing method.

It can be seen from the above that when the above method is used to query user data, when the IMS user communicates with the remote non-IMS user for voice services, the long-distance traffic is carried by the PSTN long-distance network. The routing mode restricts the use of the IMS network, and the pressure on the PSTN network is heavy, which is not conducive to the withdrawal and evolution of the old PSTN long-distance network.

Contents of the invention

Embodiments of the present invention provide a user data query method and device based on an IMS network, which solves the problem that using the existing user data query method, the intercommunication of voice services between an IMS user and a non-IMS user in a different place can only be done by "going out of the IMS network at the nearest Far into the IMS network" routing method leads to low utilization of the IMS network and high pressure on the PSTN network. It is possible to adopt the routing method of "going out of the IMS network nearby and entering the IMS network far away" and "going out of the IMS network as far as possible and entering the IMS network nearby". Network" routing method, maximize the use of IMS network, reduce the load pressure of PSTN network, which is conducive to the evolution and development of the network.

In order to achieve the above object, embodiments of the present invention adopt the following technical solutions:

In a first aspect, an embodiment of the present invention provides a user data query method based on an IMS network, including:

The server receives the query request sent by the call processing device, the query request includes the number of the called user and a tag, and the tag is used to instruct the server to query the data area of the user data;

The server queries the user data of the called user in the data area indicated by the tag according to the number of the called user, and obtains a query result of the user data, and the query result is used to represent the The routing method adopted by the network to which the server belongs;

sending the query result to the call processing device.

In a second aspect, an embodiment of the present invention provides a server, including:

A receiving unit, configured to receive a query request sent by the call processing device, the query request includes the number of the called user and a tag, and the tag is used to instruct the server to query the data area of the user data;

a processing unit, configured to query the user data of the called user in the data area indicated by the tag according to the number of the called user received by the receiving unit, and obtain a query result of the user data, The query result is used to represent the routing mode adopted by the network to which the server belongs;

A sending unit, configured to send the query result obtained by the processing unit to the call processing device.

The embodiment of the present invention provides a user data query method and device based on IMS network. , query the user data of the called user in the data area indicated by the label, and obtain the query result of the user data of the called user, wherein the query result is used to represent the routing mode adopted by the network to which the server belongs, and then the server will The query result is sent to the call processing device.

In this solution, a data area at the same level as the data area storing the E164 number is added to the ENUM servers at all levels in the IMS network, and corresponding user data is stored in each data area of the ENUM servers at all levels, so that the IMS user When intercommunicating with non-IMS user voice services in different places, the call processing device needs to indicate in the query request which data area of user data to query, that is, the query request needs to include a tag for instructing the server to query the data area of the user data. The user data stored in each data area is different, therefore, the server can obtain different user data query results in different data areas indicated by the label, and send the obtained query results to the call processing device, so that the call processing device can perform Subsequent routing. Because the query result in this solution can represent the routing mode adopted by the network to which the server belongs, the call processing device can select the routing mode according to the query result when the IMS user communicates with the voice service of a non-IMS user in a different place. Specifically, the call processing device may select the traffic to be borne by the IMS network according to the query result, that is, adopt the routing method of "going out of the IMS network as far as possible, and enter the IMS network nearby", or may select the traffic to be borne by the PSTN network according to the query result, that is, adopt The routing method of "going out of the IMS network nearby and entering the IMS network far away" can maximize the use of the IMS network, divert the traffic of the PSTN network, and reduce the load pressure of the PSTN network, thereby facilitating the evolution and development of the network.

Description of drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings that are required in the description of the embodiments or the prior art.

Fig. 1 is a schematic flow chart of a method for querying an ENUM server;

Figure 2 is a schematic diagram of the internal architecture of the existing ENUM server;

Fig. 3 is a schematic flow chart of the ENUM server recursive query method in the prior art;

FIG. 4 is a schematic structural diagram of a network system according to an embodiment of the present invention;

FIG. 5 is a first schematic flow diagram of a user data query method according to an embodiment of the present invention;

6 is a schematic diagram of the internal architecture of the ENUM server in the embodiment of the present invention;

FIG. 7 is a second schematic flow diagram of a user data query method according to an embodiment of the present invention;

FIG. 8 is a third schematic flow diagram of a user data query method according to an embodiment of the present invention;

FIG. 9 is a fourth schematic flow diagram of a user data query method according to an embodiment of the present invention;

FIG. 10 is a schematic structural diagram of a server according to an embodiment of the present invention;

FIG. 11 is a second structural diagram of a server according to an embodiment of the present invention;

FIG. 12 is a third schematic structural diagram of a server according to an embodiment of the present invention.

detailed description

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention.

IMS is an IP multimedia subsystem, a brand-new multimedia service form, which can meet the needs of more novel and more diversified multimedia services in current terminals. IMS meets the requirements of separating call control and transmission, and conforms to the development direction of the network to "multiple terminals-multiple accesses-unified control core network-multiple application network architecture", enabling multiple services to interact at the same time , to form a more flexible communication platform. IMS will eventually integrate various networks such as fixed network, mobile network, enterprise network, and wireless network, simplify the network structure, and support richer customized services. It can realize not only user-to-content multimedia communication, but also user-to-user multimedia communication.

The architecture of IMS is divided into business layer, control layer and link layer. The business layer consists of application servers and is responsible for providing value-added services to users. The control layer consists of network control servers, responsible for managing call setup, modification and release. The most important thing in the control layer is the SIP of CSCF (Call Session Control Function, call session control function). The link layer consists of routers and switches for the backbone and access networks.

The CSCF is a functional entity within the IMS and the core of the entire IMS network, and is mainly responsible for handling signaling control during a multimedia call session. It manages user authentication of the IMS network, IMS bearer plane QoS (Quality of Service, quality of service), cooperating with other network entities to conduct SIP sessions, service negotiation and resource allocation, etc.

ENUM defines the method of converting E.164 phone numbers into domain names and storing them in the database of the server. Each domain name converted from E.164 phone numbers can correspond to a series of SIP URIs, so that the internationally unified E. The 164 phone number becomes a network address resource that can be used on the Internet. In the IMS network, the network element device can perform subsequent routing after converting the TEL URI into a SIP URI by querying the ENUM server.

E.164 is an international public telephone number scheme used in PSTN (Public Switched Telephone Network, Public Switched Telephone Network) and some data networks defined by the International Telecommunication Union, and defines the specific format of the code number.

Specifically, an E.164 phone number consists of the following parts, and different parts can be connected with "-", "." or spaces: + country code (1-3 digits) - area code (n digits digits) - phone number (15-n digits).

The SIP URI is the same as an email address, and its format is: sip:x@y:Port, where x is the user name, and y is the domain name or IP address of the service host.

As shown in Figure 1, the ENUM server is queried by the CSCF in the IMS network, and a telephone number in Guangdong is converted from TELURI "+867551234567" to a SIP URI "sip:867551234567@guangdong.ims.cn".

The internal structure of ENUM is a tree structure, as shown in Figure 2, where e164.arpa is generally used as a storage area for telephone numbers and is used for storing E.164 telephone numbers. For the convenience of distributed operations, this data area is further divided into For multiple sub-data areas, an E.164 telephone number includes a country code and an area code, so sub-data areas can be divided by the country code of the phone number. For example, the country code of mainland China is 86, and the .6.8.e164.arpa sub-data The region is allocated to mainland China, and under .6.8.e164.arpa, the provincial sub-data region can be further subdivided according to the area code. For example: the sub-data area of Beijing is: 0.1.6.8.e164.arpa; the sub-data area of Shanghai is: 1.2.6.8.e164.arpa.

At present, ENUM servers are divided into national first-level ENUM servers and provincial second-level ENUM servers in the enterprise standards of Chinese communication operators. The second-level provincial ENUM server manages the data converted from TEL URI to SIPURI for the phone numbers of IMS network users in the province. For example, the ENUM server in Beijing manages the data in the 0.1.6.8.e164.arpa sub-data area. When an IMS user A in Beijing When calling another IMS user B in Beijing, the IMS network in Beijing queries the secondary ENUM server in Beijing, and converts the E.164 phone number B into its corresponding SIP URI. The first-level national ENUM server manages the data in the 6.8.e164.arpa sub-data area, which stores the corresponding relationship between the area code and the domain name or IP address of the second-level ENUM server in each province, and is used to forward calls to different provinces according to the area code of the called user's number Query requests between secondary ENUM servers.

Among them, the user data query between the provincial second-level ENUM servers needs to forward the query request through the national first-level ENUM server, that is, the provincial second-level ENUM server initiates a recursive query. Exemplarily, as shown in FIG. 3, when an IMS user A in Beijing calls a user B in Shanghai, the procedure for the ENUM server to query user data is as follows:

(1) On the calling side, the CSCF in Beijing converts the called user's number into an E.164 phone number, and initiates a recursive query to the ENUM server in the province in order to obtain the SIP URI of the called user's number.

(2) When the Beijing ENUM server accepts the query, it first queries its own server, and if the query fails, the query request is forwarded to the first-level ENUM server.

(3) The first-level ENUM server obtains the IP address of the ENUM server whose query destination is in Shanghai according to the corresponding record of the configured area code and the second-level ENUM server address, and forwards the query request to the Shanghai ENUM server.

(4) The Shanghai ENUM server obtains the SIP URI of the called user's number according to the E.164 telephone number, and returns the query result to the first-level ENUM server; if the called number is not an IMS user, the Shanghai ENUM server returns "No such user" and forward the query result to the Beijing ENUM server through the first-level ENUM server.

(5) The primary ENUM server returns the query result to the Beijing ENUM server.

(6) Beijing ENUM returns the query result to CSCF in Beijing.

At present, the original traditional CS (Circuit-switched, circuit-switched) network, such as PSTN (Public Switched Telephone Network, public switched telephone network) and PLMN (Public Land Mobile Network, public land mobile network) still have great potential for development. There are many users that can be tapped, so communication operators will try their best to protect and develop the existing telephone network resources. This requires that IMS must realize intercommunication with CS/PSTN.

According to the principle of existing ENUM servers at all levels to store user data, when an IMS user communicates with non-IMS user voice services in different places, the existing user data query method is used to make the traffic mainly be carried by the PSTN network, that is, currently between the IMS user and the non-IMS user When intercommunicating the voice services of non-IMS users in different places, only the routing method of "going out of the IMS network nearby and entering the IMS network far away" can only be used, which puts a lot of pressure on the PSTN network and limits the use of the IMS network.

Embodiment one

Fig. 4 is a schematic structural diagram of a network system provided by an embodiment of the present invention. Referring to FIG. 4, the network system includes a primary ENUM server 101, one or more secondary ENUM servers 102 connected to the primary ENUM server 101, and one or more network element devices 103 connected to the secondary ENUM server 102 . The first-level ENUM server 101, the second-level ENUM server 102, and the network element device 103 are respectively connected through a network.

In order to solve the problem of adopting the existing user data query method, when IMS users communicate with remote non-IMS users for voice services, they can only use the routing method of "going out of the IMS network at the nearest location and entering the IMS network at the far end", resulting in pressure on the PSTN network. large, low utilization of the IMS network, the embodiment of the present invention adds a data area in ENUM servers at all levels, stores corresponding user data in each data area in each ENUM server, and queries the data in each ENUM server For user data, different query results are obtained by querying different data areas, and then the routing method is selected for subsequent routing according to the query results. In this way, when the voice services of IMS users and non-IMS users in different places are intercommunicated, the traffic is carried by the IMS network , that is, adopt the routing method of "going out of the IMS network as far as possible and entering the IMS network as close as possible".

Fig. 5 is a schematic flowchart of an IMS network-based user data query method provided by an embodiment of the present invention. Referring to Figure 5, the method includes:

S101. The server receives the query request sent by the call processing device, where the query request includes the number and tag of the called user.

S102. The server queries the user data of the called user in the data area indicated by the tag according to the number of the called user, and obtains a query result of the user data.

S103. The server sends the query result to the call processing device.

The IMS network-based user data query method provided by the embodiment of the present invention is applied to the network system shown in Figure 4, which includes at least one primary ENUM server and at least two secondary ENUM servers, wherein at least one The primary ENUM server communicates with at least two secondary ENUM servers. Each ENUM server in the network system includes at least a first data area and a second data area, wherein the first data area and the second data area are respectively used to store corresponding user data, and the first data area and the second data area It is the data area of the same level.

Specifically, the user data stored in the first data area of each ENUM server at least includes the HLR (Home Location Register) identification code of the first mobile phone number, the home area code of the first mobile phone number, and the first mobile phone number. The corresponding relationship between the home network domain name and the corresponding relationship between the area code of the first fixed phone number and the home network domain name of the first fixed phone number; or at least including the corresponding relationship between the first mobile phone number and the SIP URI of the first mobile phone number, wherein , the server at the location of the first mobile phone number and the server at the location of the first fixed phone number are the ENUM server, that is, the first mobile phone number is the mobile phone number managed by the ENUM server, and the first fixed phone number is managed by the ENUM server fixed telephone number.

Among them, the HLR identification code is referred to as H code for short, and the home location register is responsible for the database of communication user management, storing the subscription data of the users under its jurisdiction and the location information of communication users, and the H code of the mobile phone number is generally used to indicate the attribution of the mobile phone number.

The user data stored in the second data area of each ENUM server at least includes the correspondence between the area code of the first fixed telephone number and the IP address of the protocol interconnected between the network of the second-level ENUM server at the place where the first fixed telephone number belongs; or , including at least the SIP URI of the first mobile phone number and the SIP URI of the first fixed phone number carrying the home area code.

Since the network system contains at least one first-level ENUM server and at least two second-level ENUM servers, and the management areas of the first-level ENUM server and the second-level ENUM server are different, the information stored in the first-level ENUM server and the second-level ENUM server User data is also different. Among them, if the user data is public data and the data will not be frequently modified, it will be preferentially stored in the first-level ENUM server.

Specifically, the user data stored in the first data area of the primary ENUM server includes at least the H code of the first mobile phone number, the corresponding relationship between the home area code of the first mobile phone number and the home network domain name of the first mobile phone number, and the first Correspondence between the area code of a fixed telephone number and the home network domain name of the first fixed telephone number, wherein the first mobile phone number is a mobile phone number managed by a first-level ENUM server, and the first fixed telephone number is a fixed telephone number managed by a first-level ENUM server Number: The user data stored in the second data area of the primary ENUM server at least includes the correspondence between the area code of the first fixed telephone number and the IP address of the secondary ENUM server where the first fixed telephone number belongs.

The user data stored in the first data area of the secondary ENUM server includes at least the correspondence between the second mobile phone number and the SIP URI of the second mobile phone number, wherein the second mobile phone number is the mobile phone number of the IMS user managed by the secondary ENUM server ; The user data stored in the second data area of the secondary ENUM server at least includes the SIP URI of the second mobile phone number and the SIP URI of the second fixed phone number that carry the home area code, wherein the second fixed phone number is the second level Fixed phone number of an IMS user managed by the ENUM server.

It can be known from the above that the internal architecture of the ENUM server in the embodiment of the present invention is different from that of the ENUM server in the prior art. Exemplarily, as shown in Figure 6, the ENUM server stores user data in two data areas (np.arpa and e164.arpa) in the embodiment of the present invention, and the two data areas of np.arpa and e164.arpa The stored user data is different. Based on this internal architecture and the storage principle of user data, the user data query method provided by the embodiment of the present invention is completed.

Preferably, in the embodiment of the present invention, the second data area is e164.arpa, and the first data area is a data area at the same level as e164.arpa in the ENUM server. Exemplarily, as shown in FIG. 6 , the first data area is np.arpa, the second data area is e164.arpa, and np.arpa and e164.arpa are data areas at the same level.

Any server in the network system first receives the query request sent by the call processing device and includes the number and label of the called user.

Wherein, the label in the query request is used to instruct the server to query the data area of the user data query.

It should be noted that the first-level ENUM server and at least two second-level ENUM servers in the network system in the embodiment of the present invention can respectively complete their user data query, that is, the first-level ENUM server and at least two second-level ENUM servers respectively receive calls Process the query request sent by the device.

Specifically, the combinations of the server and the call processing device in the embodiment of the present invention are as follows:

(1) If the server is a first-level ENUM server, the call processing device is a source second-level ENUM server, that is, the call processing device is a second-level ENUM server at the calling side.

(2) If the server is the source secondary ENUM server, the call processing device is the calling side network element device.

(3) If the server is the target secondary ENUM server, that is, the server is the called side secondary ENUM server, then the call processing device is the primary ENUM server or the called side network element device.

Optionally, the calling side network element device in the embodiment of the present invention may be the calling side CSCF, may also be the calling side MGCF (Media Gateway Control Function, media gateway control function), may also be the calling side IBCF (Interconnection Border Control Function, Internet border control function).

Similarly, optionally, the network element device at the called side in this embodiment of the present invention may be the CSCF at the called side, or the MGCF at the called side, or the IBCF at the called side.

Wherein, the label in the query request in the embodiment of the present invention is determined by the network element device according to a pre-configured query rule.

Specifically, the network element device (the calling side network element device and/or the called side network element device) analyzes the called number, and determines the label in the query request according to the pre-configured query rules. The specific query rules are as follows:

The first rule: if the number of the called user is a mobile phone number, the network element device uses a tag to indicate the first data area of the query server in the query request.

Rule 2: If the number of the called user is a fixed number, and the number of the called user is managed by the server corresponding to the network element device, then the network element device uses a tag to indicate the query server in the query request the second data area of .

Rule 3: If the called user's number is a fixed number, and the called user's number is not managed by the server corresponding to the network element device, and the area code of the called user's number is configured with IMS The network also supports the routing mode of "going out of the IMS network as far as possible and entering the IMS network as close as possible", so the network element device uses a label in the query request to indicate the first data area of the query server.

Rule 4: If the called user's number is a fixed number, and the called user's number is not managed by the server corresponding to the network element device, and the area code of the called user's number is configured with IMS network but does not support the routing method of "leave the IMS network far away and enter the IMS network nearby", or the area code of the called user's number does not have an IMS network configured, then the network element device uses a label in the query request to indicate the number of the query server. Two data areas.

Rule 5: If the number of the called user is the number managed by the server corresponding to the network element device, and the numbers of the called user all carry the home area code, then the network element device will use a label to indicate in the query request Query the server's second data area.

Specifically, in the embodiment of the present invention, when the server receiving the query request is the source secondary ENUM server, the source secondary ENUM server receives the query request sent by the calling side network element device, and the label in the query request is the calling side network element After the device analyzes the number of the called user, it is determined according to the preset query rules.

Further, the network element device at the calling side learns whether the IMS network at the calling side supports the routing mode of "entering the IMS network nearby and leaving the IMS network far away" according to the pre-configured query rules. Specifically, if the above-mentioned query rules are configured in the calling-side network element device, it is determined that the calling-side IMS network supports the routing mode of "entering the IMS network nearby and leaving the IMS network far away". In this way, the calling-side network element device according to The above query rules determine the label in the query request; if the above query rules are not configured in the network element equipment on the calling side, the IMS network on the calling side does not support the routing method of "entering the IMS network at the nearest place and leaving the IMS network far away". , only the second data area exists in the source secondary ENUM server, and the source secondary ENUM server can only query user data in its second data area.

Specifically, in the scenario where the calling-side network element device learns that the calling-side IMS network supports the routing method of "entering the IMS network nearby and leaving the IMS network far away" according to the pre-configured rules of the IMS network, the calling-side network element device passes The method to analyze the number of the called user and determine the label in the query request is:

(1) The network element device at the calling side analyzes the number of the called user, and determines whether the number of the called user is a mobile phone number or a landline phone number.

Wherein, the network element device at the calling side can know whether the number of the called user is a landline phone number or a mobile phone number according to the first three digits of the number of the called user. Because the first three digits of the mobile phone number are the network identification number, and the first three or four digits of the landline phone number are the area code.

(2) If the number of the called user is a mobile phone number, the label in the query request indicates that user data query is performed in the first data area.

(3) If the number of the called user is a fixed telephone number, the network element device at the calling side analyzes the area code of the fixed telephone number, and then judges whether the fixed telephone number belongs to the number managed by the source secondary ENUM server, that is, judges the Whether the attribution of the fixed-line phone number is another province. Specifically, if the fixed telephone number is a number managed by the source secondary ENUM server, the label in the query request indicates that user data query is performed in the second data area; if the fixed telephone number does not belong to the source secondary ENUM server managed number, the network element device on the calling side obtains whether an IMS network is configured in the area code's attribution. If the area code of the called user's number is configured with an IMS network and supports the routing method of "entering the IMS network nearby and leaving the IMS network far away", the label in the query request indicates that the user data is stored in the first data area. Query; if the area code is configured with an IMS network but does not support the routing method of "entering the IMS network nearby and leaving the IMS network far away" or the area code does not have an IMS network configured, the label in the query request indicates that the second Perform user data query in the data area.

Exemplarily, if the called user's number is a mobile phone number 136H0H1H2H3abcd, and the CSCF at the calling side determines that the called user's number is a mobile phone number by analyzing the first three digits of the called user's number, the calling side CSCF will include Send to the source secondary ENUM server with 136H0H1H2H3abcd and a label indicating to query the first data area.

Specifically, in the embodiment of the present invention, when the server receiving the query request is a primary ENUM server, the primary ENUM server receives the query request forwarded by the source secondary ENUM server, and the query request is sent to the source secondary ENUM server by the calling side network element device. Therefore, the tag in the query request received by the first-level ENUM server is also determined by the network element device on the calling side after analyzing the number of the called user and according to the pre-configured query rules.

Specifically, when the server receiving the query request in the embodiment of the present invention is the target secondary ENUM server, the target secondary ENUM server can receive the query request forwarded by the primary ENUM server, and the query request is forwarded by the source secondary ENUM server to the primary ENUM server. ENUM server, and forwarded by the primary ENUM server to the target secondary ENUM server. At this time, the tag in the query request received by the target secondary ENUM server is also the number of the called user analyzed by the network element device on the calling side. Determined by the configured query rules.

In addition, the destination secondary ENUM server can also receive the query request sent by the called side network element device. The query request is sent by the called side network element device according to the call request sent by the calling side network element device. At this time, the The tag in the query request is determined by the called side network element device after analyzing the called user's number according to the pre-configured query rules.

Specifically, the call request sent by the network element device on the calling side includes the number of the called user, and the call request is that the network element device on the calling side obtains the IP address of the network element device on the called side according to the number of the called user It is sent to the network element device on the called side later. Therefore, the number of the called user in the call request received by the network element device on the called side is the number managed by the destination secondary ENUM server. Like this, if the number of the called user is a fixed telephone number, then the tag instruction in the query request sent to the target secondary ENUM server is to perform user data query in the second data area; if the number of the called user is a mobile phone number, and If the mobile phone number carries an area code, the network element device on the called side regards the mobile phone number as a fixed phone, and the label in the query request sent to the target secondary ENUM server indicates that the user data query is performed in the second data area; if the called If the user's number is a mobile phone number without an area code, the tag in the query request sent to the target secondary ENUM server indicates that user data query should be performed in the first data area.

After the server receives the query request, the server queries the user data of the number of the called user in the data area indicated by the tag according to the number of the called user, and obtains the query result of the user data.

There are respective user data stored in the first data area and the second data area in the server, so after the server receives the query request, it searches the user data in the first data area or the second data area according to the query request and obtains the user data. Data query results. Since the user data stored in each data area of the first-level ENUM server is different from that of the second-level ENUM server, the query results obtained by the first-level ENUM server and the second-level ENUM server may be different.

Specifically, in the embodiment of the present invention, when the server receiving the query request is the source secondary ENUM server, the source secondary ENUM server searches whether there is user data of the called user in the data area indicated by the label. If the server at the place of origin of the number of the called user is not the source secondary ENUM server, then the source secondary ENUM server cannot find the user data corresponding to the number of the called user. At this time, it forwards the query request to a Level-1 ENUM server, so that the level-1 ENUM server performs user data query according to the query request, and the level-1 ENUM server forwards the query result to the source level-2 ENUM server after obtaining the query result; if the number of the called user belongs to the source level-2 ENUM server ENUM server management, the source secondary ENUM server searches for the SIP URI of the called user’s number in the data area indicated by the label, and if it exists, obtains the SIP URI of the called user’s number, wherein the called user’s The SIP URI of the number is part of the user data of the called user stored in the source secondary ENUM server.

Exemplarily, for the called fixed phone number B (02112345678) whose attribution is in Shanghai, there are several situations as follows:

(1) In the scenario where a user in Shanghai calls number B, the query request received by the Shanghai ENUM server includes number B and a tag indicating user data query in the second data area. According to the number B, the Shanghai ENUM server In the second data area of the Shanghai ENUM server, query whether there is corresponding user data of the number B. When the number B is an IMS user, the query result obtained by the Shanghai ENUM server is the SIP URI of the number B (for example, SIP:862112345678@shanghai .ims.cn); when number B is not an IMS user, the query result obtained by the Shanghai ENUM server is "No such user".

(2) In the scenario where a user in Beijing calls number B, the Beijing ENUM server cannot query the corresponding data of number B, and number B does not belong to the number managed by the Beijing ENUM server, and the Beijing ENUM server forwards the query request to the first-level ENUM server, so that the primary ENUM server obtains the query result according to the query request.

Further, in the embodiment of the present invention, when the server receiving the query request is a first-level ENUM server, the first-level ENUM server searches whether there is user data of the called user in the data area indicated by the label.

Specifically, if the label in the query request received by the primary ENUM server indicates that data query is performed in the first data area, the primary ENUM server obtains the extended SIP URI of the number of the called user in its first data area (by The extended SIP URI of the calling user's number includes the SIP URI of the called user's number and the user ID, which is used to indicate whether the user is an IMS user or not, because the user data stored in the primary ENUM server is the called user The corresponding relationship between the number and the network domain name or the area code of the called user's number and the IP address of the home server, optionally, the user identifier can be user=phone).

Wherein, when the number of the called user is a mobile phone number, the primary ENUM server obtains the extended SIP URI of the mobile phone number in its first data area according to the corresponding relationship between the H code, the home area code and the home network domain name; When the user's number is a fixed phone number, the primary ENUM server obtains the extended SIP URI of the fixed phone number in its first data area according to the correspondence between the area code and the home network domain name.

If the tag in the query request received by the first-level ENUM server indicates that data query is to be performed in the second data area, the first-level ENUM server will use the correspondence between the area code and the IP address of the second-level ENUM server at its home location in its second data area. The relationship obtains the IP address of the target secondary ENUM server, and forwards the query request to the target secondary ENUM server to obtain the query result.

Exemplarily, if the called user's number is Shanghai's mobile phone number 133H0H1H2H3ABCD, and the query request received by the first-level ENUM server includes the mobile phone number 133H0H1H2H3ABCD and a tag indicating user data query in the first data area, then the first-level ENUM According to the query request, the server obtains the extended SIP URI in its first data area according to the corresponding relationship between the H code of the mobile phone, the home area code and the home network domain name: sip:86133H0H1H2H3ABCD@shanghai.ims.cn, user=phone.

Further, in the embodiment of the present invention, when the server receiving the query request is the target secondary ENUM server, the target secondary ENUM server searches whether there is user data of the called user in the data area indicated by the label. If the called user is an IMS user, the destination secondary ENUM server obtains the SIP URI of the number of the called user.

After obtaining the query result, the server sends the query result to the call processing device.

After obtaining the query result, the server sends the query result to the corresponding call processing device for subsequent routing. Wherein, the query result is used to represent the routing mode adopted by the network to which the server belongs. After obtaining the query result sent by the server, the call processing device selects the corresponding routing mode according to the query result for subsequent routing. In this way, when an IMS user intercommunicates voice services with a non-IMS user in a different place, no longer only one routing method is used.

Exemplarily, if an IMS user in Shanghai calls a non-IMS user in Beijing, and the query result obtained by Shanghai CSCF is "no such user", Shanghai CSCF will route the call to the PSTN network according to the query result of "no such user", And route the call to the PSTN network in Beijing through the PSTN network, the routing method is "the nearest IMS network"; if the IMS user in Shanghai calls the non-IMS user in Beijing, and the query result obtained by Shanghai CSCF contains the network domain name of Beijing , Shanghai CSCF routes the call to the Beijing IMS network through the IMS network according to the Beijing network domain name, and then routes the call to the called user through the Beijing IMS network.

Specifically, after the source secondary ENUM server obtains the query result, it sends the query result to the calling side network element device, so that the calling side network element device performs subsequent routing according to the query result; after the primary ENUM server obtains the query result , send the query result to the source secondary ENUM server, so that the source secondary ENUM server forwards the query result to the calling side network element device; after the destination secondary ENUM server obtains the query result, it sends the query result to the called side network element device, so that the called side network element device performs subsequent routing according to the query result, or, after the destination secondary ENUM server obtains the query result, it sends the query result to the primary ENUM server, so that the primary ENUM server will The query result is forwarded to the source secondary ENUM server, and finally sent to the calling side network element device.

Further, in order to be able to detail the query of user data in each ENUM server in the network system, the query of user data in the source secondary ENUM server, the primary ENUM server and the target secondary ENUM server will now be illustrated.

Among them, Tianjin and Shanghai are both equipped with IMS networks, and both support the routing method of "going out of the IMS network at the far end and entering the IMS network at the nearest place". The IMS network in Tianjin and the IMS network in Shanghai are interoperable. The area code of Shanghai queries the newly added np.arpa sub-area, and the CSCF configuration of the called side Shanghai still queries the traditional e164.arpa sub-area for the local area code as an example to describe the user data query method provided by the embodiment of the present invention in detail. As shown in Figure 7, when the number of the called user is a fixed number (such as 02112345678) in Shanghai, the flow process of the query method is:

(1) The CSCF in Tianjin converts the called user's number into an E.164 telephone number, and sends a query request for the np.arpa data area to the ENUM server in Tianjin, in order to obtain the home network domain name of the called place.

(2) Tianjin ENUM server accepts the query, first queries the np.arpa data area of the server, if the query cannot be found, the query request is forwarded to the first-level ENUM server.

(3) After receiving the query request, the first-level ENUM server queries its np.arpa data area according to the query request, and obtains the query result (for example, sip:862112345678@ shanghai.ims.cn, user=phone), and then, the primary ENUM server returns the query result to the Tianjin ENUM server.

(4) Tianjin ENUM server returns the received query result to Tianjin CSCF, and Tianjin CSCF sends the call request to Shanghai CSCF according to the network domain name in the query result.

(5) Since the Shanghai CSCF is configured to query the e164.arpa data area for the local area code, the Shanghai CSCF sends a query request for the e164.arpa sub-area to the Shanghai ENUM server in order to obtain the SIP URI of the called user's number.

(6) The Shanghai ENUM server performs user data query in its e164.arpa data area, and inquires whether the user data of the number of the called user is stored in the e164.arpa data area. If the called user is not an IMS user, the Shanghai ENUM server cannot find the user data of the user in its e164.arpa data area, then the Shanghai ENUM server returns "No such user" and returns the result to Shanghai CSCF, Shanghai CSCF According to the query result of "no such user", the call is routed to the PSTN tandem office in Shanghai through the MGCF in Shanghai, so that the PSTN tandem office in Shanghai can route the call; if the called user is an IMS user, the Shanghai ENUM The server can find the user's SIP URI (for example: sip:862112345678@shanghai.ims.cn) in its e164.arpa data area. The Shanghai ENUM server returns the result to the Shanghai CSCF. (Home Subscription Server, Home Subscriber Server) inquires to obtain the SBC (Session Border Controller, Session Border Controller) corresponding to the number of the called user, so that the SBC routes the call to the called user.

It can be known from the above that in this example, even if the called user is a non-IMS user, the CSCF at the calling side selects traffic to be borne by the IMS network according to the query result.

In addition, if a Tianjin IMS user calls a mobile phone number in Shanghai, the Tianjin CSCF on the calling side configures all mobile numbers to query the np.arpa data area of the newly added sub-area, and the Shanghai CSCF on the called side configures all mobile numbers to query np. The arpa data area, that is, the Shanghai CSCF of the called home determines whether the mobile phone number is an IMS user (including whether it resides in the IMS network) as an example to describe the query method provided by the embodiment of the present invention in detail. As shown in Figure 8, when the called number is a Shanghai mobile number 186H0H1H2H31234, the process of the query method is as follows:

(1) Tianjin CSCF converts the number of the called user into an E.164 phone number, and sends a query request for the np.arpa data area to the ENUM server in the province, in order to obtain the home network domain name of the called place.

(2) Tianjin ENUM server accepts the query, and first queries the np.arpa data area of the server, and if the query cannot be found, forwards the query request to the first-level ENUM server.

(3) After the first-level ENUM server receives the query request, it queries its np.arpa data area according to the query request, and obtains the query result (such as sip: 86186H0H1H2H31234@shanghai.ims.cn, user=phone), the primary ENUM server returns the query result to the Tianjin ENUM server.

(4) Tianjin ENUM server returns the received query result to Tianjin CSCF, and Tianjin CSCF forwards the call request to Shanghai CSCF according to the network domain name in the query result.

(5) Since the CSCF in Shanghai is configured to query the np.arpa data area for all mobile numbers, the upper CSCF sends a query request for the np.arpa data area to the Shanghai ENUM server in order to obtain the SIPURI of the called user's number.

(6) The Shanghai ENUM server performs user data query in its np.arpa data area, and inquires whether the user data of the number of the called user is stored in the np.arpa data area. If the called user is not an IMS user, the Shanghai ENUM server cannot find the user data of the user in its np.arpa data area, then the Shanghai ENUM server returns "No such user" and returns the query result to the Shanghai CSCF; if If the called user is an IMS user, the Shanghai ENUM server can find the user's SIP URI (for example, sip:86186H0H1H2H31234@shanghai.ims.cn) in its np.arpa data area, and the Shanghai ENUM server returns the query result to Shanghai CSCF.

(7) Shanghai CSCF performs follow-up routing on the call according to the query result. If the returned result is "no such user", it will be routed to the gateway office in Shanghai; if the returned result is SIP URI, Shanghai CSCF will query the HSS according to the SIP URI to Obtain the SBC corresponding to the number of the called user, so that the SBC can route the call to the called user.

Further, as shown in Figure 9, the number of the called user is a mobile phone number, and the province to which the called mobile phone number belongs is divided into multiple city areas, and each city area has a unique area code (that is, a province contains multiple City, there are multiple area codes belonging to the province) in the application scenario where the query method provided in the embodiment of the present invention is adopted, the CSCF of the place where the number of the called user belongs will perform follow-up routing on the call according to the query result and the area code analysis, if it returns If the query result is "No such user", the CSCF at the called side routes to the gateway office where the area code of the called user's number is located, that is, the called side CSCF selects the gateway office according to the area code of the called user's number; if the returned query The result is a SIP URI, and the CSCF at the called side queries the HSS to route the call to the SBC. The query steps and principles performed by other ENUM servers are the same as the example shown in FIG. 8 , and will not be repeated here.

Embodiments of the present invention provide a user data query method based on an IMS network. After the server receives a query request including the number and label of the called user sent by the call processing device, according to the number of the called user in the query request, the Query the user data of the called user in the data area indicated by the label, and obtain the query result of the user data of the called user, wherein the query result is used to represent the routing mode adopted by the network to which the server belongs, and then the server will query the result sent to the call processing unit.

In this solution, a data area at the same level as the data area storing the E164 number is added to the ENUM servers at all levels in the IMS network, and corresponding user data is stored in each data area of the ENUM servers at all levels, so that IMS users can communicate with each other. When voice services of non-IMS users in different places are interoperable, the call processing device needs to indicate in the query request which data area the user data is to be queried, that is, the query request needs to include a tag for instructing the server to query the data area of the user data. The user data stored in the data area is different, therefore, the server can obtain different user data query results in different data areas indicated by the label, and send the obtained query results to the call processing device, so that the call processing device can carry out subsequent operations. routing. Because the query result in this solution can represent the routing mode adopted by the network to which the server belongs, the call processing device can select the routing mode according to the query result when the IMS user communicates with a non-IMS user in a different place for voice services. Specifically, the call processing device may select the toll traffic to be borne by the IMS network according to the query result, that is, adopt the routing method of "leaving the IMS network as far as possible and entering the IMS network nearby", or may select the toll traffic to be borne by the PSTN toll network according to the query result , that is, adopt the routing method of "going out of the IMS network nearby, and entering the IMS network far away", so that the IMS network can be used to the maximum extent, the traffic of the PSTN long-distance network can be diverted, and the load pressure of the PSTN network can be reduced, which is conducive to the evolution of the network and development.

Embodiment two

An embodiment of the present invention provides a server 1, as shown in FIG. 10 , including:

The receiving unit 10 is configured to receive the query request sent by the call processing device, the query request includes the number of the called user and a tag, and the tag is used to instruct the server to query the data area of the user data.

The processing unit 11 is configured to query the user data of the called user in the data area indicated by the label according to the number of the called user received by the receiving unit 10, and obtain the query of the user data As a result, the query result is used to characterize the routing mode adopted by the network to which the server belongs.

The sending unit 12 is configured to send the query result acquired by the processing unit 11 to the call processing apparatus.

Further, as shown in FIG. 11 , the server 1 further includes a storage unit 13,

The storage unit 13 is configured to store user data in a first data area and user data in a second data area, the first data area and the second data area are data areas at the same level in the server; The user data stored in the first data area at least includes the HLR identification code of the first mobile phone number, the corresponding relationship between the home area code of the first mobile phone number and the home network domain name of the first mobile phone number, and The corresponding relationship between the area code of the first fixed phone number and the domain name of the home network of the first fixed phone number; or, at least including the first mobile phone number and the session initiation protocol universal resource identifier SIP URI of the first mobile phone number Correspondence; the server at the location of the first mobile phone number and the server at the location of the first fixed phone number are the servers; the user data stored in the second data area includes at least the first fixed phone number The corresponding relationship between the area code of the telephone number and the secondary telephone number mapping ENUM server network of the attribution of the first fixed telephone number; or at least include the first mobile phone number carrying the attribution area code SIP URI and the SIP URI of the first landline number.

Optionally, the server may be a primary ENUM server or a secondary ENUM server.

Further, the number of the called user is one of the first mobile phone number or the first fixed phone number.

Further, the processing unit 11 is specifically configured to query whether there is a SIP URI of the number of the called user in the data area indicated by the tag of the source secondary ENUM server, and specifically configured to query if there is the SIP URI of the number of the called user. If the SIP URI of the number of the called user is obtained, the SIP URI of the number of the called user is obtained, and if there is no SIP URI of the number of the called user, and the SIP URI of the number of the called user If the server at the home location is the source secondary ENUM server, the user attribute identifier is obtained, and the user attribute identifier is used to indicate that the called user is a non-IP multimedia subsystem IMS user.

Further, the sending unit 12 is specifically configured to: if the processing unit 11 determines that the SIP URI of the number of the called user does not exist, and the server of the home of the number of the called user is not the source two If the first-level ENUM server is used, the query request is sent to the first-level ENUM server.

Further, the receiving unit 10 is specifically configured to receive the query result sent by the primary ENUM server.

Further, the processing unit 11 is further configured to query the home network domain name of the number of the called user in the first data area of the primary ENUM server, and obtain the home network domain name of the number of the called user. domain name; or, it is also used to obtain the IP address of the target secondary ENUM server in the second data area of the primary ENUM server, and the target secondary ENUM server is the server at the home of the called user.

Further, the sending unit 12 is specifically configured to send the query request to the target secondary ENUM server.

Further, the receiving unit 10 is specifically configured to receive the query result sent by the target secondary ENUM server.

Further, the processing unit 11 is specifically configured to query whether there is a SIP URI of the number of the called user in the data area indicated by the label of the target secondary ENUM server, and specifically configured to query if there is the SIP URI of the number of the called user. If the SIP URI of the number of the called user is obtained, the SIP URI of the number of the called user is obtained, and specifically used to obtain the user attribute identifier if there is no SIP URI of the number of the called user.

An embodiment of the present invention provides a server, which mainly includes a receiving unit, a processing unit, and a sending unit. After receiving the query request including the number of the called user and the tag sent by the call processing device, the server queries the user data of the called user in the data area indicated by the tag according to the number of the called user in the query request, and obtains the The query result of the user data of the called user, wherein the query result is used to characterize the routing mode adopted by the network to which the server belongs, and then the server sends the query result to the call processing device.

In this solution, a data area at the same level as the data area storing the E164 number is added to the ENUM servers at all levels in the IMS network, and corresponding user data is stored in each data area of the ENUM servers at all levels, so that IMS users can communicate with each other. When voice services of non-IMS users in different places are interoperable, the call processing device needs to indicate in the query request which data area the user data is to be queried, that is, the query request needs to include a tag for instructing the server to query the data area of the user data. The user data stored in the data area is different, therefore, the server can obtain different user data query results in different data areas indicated by the label, and send the obtained query results to the call processing device, so that the call processing device can carry out subsequent operations. routing. Because the query result in this solution can represent the routing mode adopted by the network to which the server belongs, the call processing device can select the routing mode according to the query result when the IMS user communicates with a non-IMS user in a different place for voice services. Specifically, the call processing device may select the toll traffic to be borne by the IMS network according to the query result, that is, adopt the routing method of "leaving the IMS network as far as possible and entering the IMS network nearby", or may select the toll traffic to be borne by the PSTN toll network according to the query result In this way, the IMS network can be used to the maximum extent, the traffic of the PSTN network can be diverted, and the load pressure of the PSTN network can be reduced, which is beneficial to the evolution and development of the network. develop.

Embodiment three

An embodiment of the present invention provides a server. As shown in FIG. 12 , the server may include a communication interface 20, a processor 21, a memory 22, and a system bus 23, wherein,

The communication interface 20 , the processor 21 and the memory 22 are connected through the system bus 23 and complete mutual communication.

The processor 21 may be a single-core or multi-core central processing unit, or a specific integrated circuit, or one or more integrated circuits configured to implement the embodiments of the present invention.

The memory 22 may be a high-speed RAM (Random Access Memory, Random Access Memory) memory, or a non-volatile memory (non-volatile memory), for example, at least one disk memory.

Optionally, the server provided in this embodiment of the present invention may be a first-level ENUM server or a second-level ENUM server, which is not limited in this embodiment of the present invention.

Specifically, the communication interface 20 is configured to receive a query request sent by the call processing device, the query request includes the number of the called user and a tag, and the tag is used to instruct the server to query the data area of the user data.

Specifically, the processor 21 is configured to query the user data of the called user in the data area indicated by the label according to the number of the called user received by the communication interface 20, and obtain the user data of the called user A query result of the data, the query result is used to characterize the routing mode adopted by the network to which the server belongs.

Specifically, the communication interface 20 is configured to send the query result acquired by the processor 21 to the call processing apparatus.

Specifically, the memory 22 is used to store user data in the first data area and user data in the second data area, the first data area and the second data area are data areas at the same level in the server .

The user data stored in the first data area at least includes the home location register HLR identification code of the first mobile phone number, the corresponding relationship between the home area code of the first mobile phone number and the home network domain name of the first mobile phone number, and The corresponding relationship between the area code of the first fixed telephone number and the domain name of the home network of the first fixed telephone number; or at least including the correspondence between the first mobile phone number and the SIP universal resource identifier SIPURI of the first mobile phone number Relationship; the server at the home of the first mobile phone number and the server at the home of the first fixed phone number are the servers.

The user data stored in the second data area at least includes the corresponding relationship between the area code of the first fixed telephone number and the IP address of the interconnection protocol between the network of the secondary ENUM server at the home of the first fixed telephone number ; Or, at least include the SIP URI of the first mobile phone number carrying the home area code and the SIP URI of the first fixed phone number.

Further, the number of the called user is one of the first mobile phone number or the first fixed phone number.

Further, the processor 21 is specifically configured to inquire whether there is a SIP URI of the number of the called user in the data area indicated by the label of the source secondary ENUM server, and specifically to query if there is the SIP URI of the number of the called user. If the SIP URI of the number of the called user is obtained, the SIP URI of the number of the called user is obtained, and if there is no SIP URI of the number of the called user, and the SIP URI of the number of the called user If the server at the home location is the source secondary ENUM server, the user attribute identifier is obtained, and the user attribute identifier is used to indicate that the called user is a non-IP multimedia subsystem IMS user.

Further, the communication interface 20 is specifically configured to: if the processor 21 determines that there is no SIP URI of the number of the called user, and the server of the home of the number of the called user is not the source 2 If the first-level ENUM server is used, the query request is sent to the first-level ENUM server.

Further, the communication interface 20 is specifically configured to receive the query result sent by the primary ENUM server.

Further, the processor 21 is further configured to query the home network domain name of the number of the called user in the first data area of the primary ENUM server, and obtain the home network domain name of the number of the called user. domain name; or, it is also used to obtain the IP address of the target secondary ENUM server in the second data area of the primary ENUM server, and the target secondary ENUM server is the server at the home of the called user.

Further, the communication interface 20 is specifically configured to send the query request to the target secondary ENUM server.

Further, the communication interface 20 is specifically configured to receive the query result sent by the target secondary ENUM server.

Further, the processor 21 is specifically configured to inquire whether there is a SIP URI of the number of the called user in the data area indicated by the label of the target secondary ENUM server, and specifically to query if there is the SIP URI of the number of the called user. If the SIP URI of the number of the called user is obtained, the SIP URI of the number of the called user is obtained, and specifically used to obtain the user attribute identifier if there is no SIP URI of the number of the called user.

An embodiment of the present invention provides a server, which mainly includes a communication interface, a processor, and a memory. After receiving the query request including the number of the called user and the tag sent by the call processing device, the server queries the user data of the called user in the data area indicated by the tag according to the number of the called user in the query request, and obtains the The query result of the user data of the called user, wherein the query result is used to characterize the routing mode adopted by the network to which the server belongs, and then the server sends the query result to the call processing device.

In this solution, a data area at the same level as the data area storing the E164 number is added to the ENUM servers at all levels in the IMS network, and corresponding user data is stored in each data area of the ENUM servers at all levels, so that IMS users can communicate with each other. When voice services of non-IMS users in different places are interoperable, the call processing device needs to indicate in the query request which data area the user data is to be queried, that is, the query request needs to include a tag for instructing the server to query the data area of the user data. The user data stored in the data area is different, therefore, the server can obtain different user data query results in different data areas indicated by the label, and send the obtained query results to the call processing device, so that the call processing device can carry out subsequent operations. routing. Because the query result in this solution can represent the routing mode adopted by the network to which the server belongs, the call processing device can select the routing mode according to the query result when the IMS user communicates with a non-IMS user in a different place for voice services. Specifically, the call processing device may select the toll traffic to be borne by the IMS network according to the query result, that is, adopt the routing method of "leaving the IMS network as far as possible and entering the IMS network nearby", or may select the toll traffic to be borne by the PSTN toll network according to the query result , that is, adopt the routing method of "going out of the IMS network nearby, and entering the IMS network far away", so that the IMS network can be used to the maximum extent, the traffic of the PSTN long-distance network can be diverted, and the load pressure of the PSTN network can be reduced, which is conducive to the evolution of the network and development.

Those skilled in the art can clearly understand that for the convenience and brevity of description, only the division of the above-mentioned functional modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional modules according to needs. The internal structure of the device is divided into different functional modules to complete all or part of the functions described above. For the specific working process of the above-described system, device, and unit, reference may be made to the corresponding process in the foregoing method embodiments, and details are not repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be Incorporation may either be integrated into another system, or some features may be omitted, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

If the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the essence of the technical solution of the present invention or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) execute all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes. .

The above is only a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Anyone skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present invention. Should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be determined by the protection scope of the claims.

Claims (10)

1. A method for querying user data based on an IMS network is characterized by comprising the following steps:

the server receives an inquiry request sent by a call processing device, wherein the inquiry request comprises the number of a called user and a label, and the label is used for indicating the server to inquire a data area of user data;

the server inquires the user data of the called user in the data area indicated by the label according to the number of the called user, and acquires the inquiry result of the user data, wherein the inquiry result is used for representing the routing mode adopted by the network to which the server belongs, and the routing mode is a routing mode of entering the IMS network when the server is far away from the IMS network or a routing mode of entering the IMS network when the server is near to the IMS network;

and sending the query result to the call processing device.

2. The user data query method of claim 1,

the server at least comprises a first data area and a second data area, wherein the first data area and the second data area are the same level data area;

the user data stored in the first data area at least comprises a Home Location Register (HLR) identification code of a first mobile phone number, a corresponding relation between a home area code of the first mobile phone number and a home network domain name of the first mobile phone number, and a corresponding relation between an area code of a first fixed phone number and a home network domain name of the first fixed phone number; or at least comprising the corresponding relation between the first mobile phone number and the Session Initiation Protocol (SIP) Universal Resource Identifier (URI) of the first mobile phone number; the server of the attribution of the first mobile phone number and the server of the attribution of the first fixed phone number are the servers;

the user data stored in the second data area at least comprises the corresponding relation between the area code of the first fixed telephone number and the interconnected protocol IP address between the secondary telephone number mapping ENUM server and the network of the home location of the first fixed telephone number; or at least comprises an SIP URI of a first mobile phone number carrying a home area number and an SIP URI of the first fixed phone number;

the server is a primary ENUM server or a secondary ENUM server.

3. The method according to claim 2, wherein the number of the called subscriber is one of the first mobile phone number or one of the first fixed phone number; the server is a source secondary ENUM server, and the source secondary ENUM server is a server of a home of a calling subscriber;

the server, according to the number of the called user, querying the user data of the called user in the data area indicated by the label, and obtaining a query result of the data of the called user, includes:

the source secondary ENUM server inquires whether the SIP URI of the number of the called user exists in a data area indicated by the label of the source secondary ENUM server;

if the SIP URI of the number of the called user exists, the source secondary ENUM server acquires the SIP URI of the number of the called user; or,

if the SIP URI of the number of the called user does not exist and the server of the home location of the number of the called user is the source secondary ENUM server, the source secondary ENUM server acquires a user attribute identifier, and the user attribute identifier is used for marking the called user as a non-IP Multimedia Subsystem (IMS) user; or,

if the SIP URI of the number of the called user does not exist and the server of the home location of the number of the called user is not the source second-level ENUM server, the source second-level ENUM server sends the query request to a first-level ENUM server; and receiving the query result sent by the primary ENUM server.

4. The method as claimed in claim 3, wherein the server is the primary ENUM server, and wherein the server queries the subscriber data of the called subscriber in the data area indicated by the tag according to the number of the called subscriber, and obtains the query result of the data of the called subscriber, the method includes:

the primary ENUM server inquires the home network domain name of the number of the called user in a first data area of the primary ENUM server and acquires the home network domain name of the number of the called user; or,

the primary ENUM server acquires an IP address of a target secondary ENUM server in a second data area of the primary ENUM server, wherein the target secondary ENUM server is a server of a home location of the called user; sending the query request to the destination secondary ENUM server; and receiving the query result sent by the target secondary ENUM server.

5. The method as claimed in claim 4, wherein the server is the destination secondary ENUM server, and wherein the server queries the subscriber data of the called subscriber in the data area indicated by the tag according to the number of the called subscriber and obtains the query result of the data of the called subscriber, the method comprising:

the destination secondary ENUM server inquires whether the SIP URI of the number of the called user exists in a data area indicated by the label of the destination secondary ENUM server;

if the SIP URI of the number of the called user exists, the SIP URI of the number of the called user is obtained; or,

and if the SIP URI of the number of the called user does not exist, acquiring the user attribute identification.

6. A server, comprising:

a receiving unit, configured to receive an inquiry request sent by a call processing device, where the inquiry request includes a number of a called subscriber and a tag, and the tag is used to instruct the server to inquire a data area of subscriber data;

a processing unit, configured to query, according to the number of the called user received by the receiving unit, user data of the called user in a data area indicated by the tag, and obtain a query result of the user data, where the query result is used to characterize a routing manner adopted by a network to which the server belongs, and the routing manner is a routing manner that the called user is far away from an IMS network and enters the IMS network nearby, or a routing manner that the called user is far away from the IMS network nearby;

and the sending unit is used for sending the query result acquired by the processing unit to the call processing device.

7. The server according to claim 6, wherein the server further comprises a storage unit,

the storage unit is used for storing data of a first data area and data of a second data area, and the first data area and the second data area are the same level data area;

the user data stored in the first data area at least comprises a Home Location Register (HLR) identification code of a first mobile phone number, a corresponding relation between a home area code of the first mobile phone number and a home network domain name of the first mobile phone number, and a corresponding relation between an area code of a first fixed phone number and a home network domain name of the first fixed phone number; or at least comprising the corresponding relation between the first mobile phone number and the session initiation protocol universal resource identifier (SIP URI) of the first mobile phone number; the server of the attribution of the first mobile phone number and the server of the attribution of the first fixed phone number are the servers;

the user data stored in the second data area at least comprises the corresponding relation between the area code of the first fixed telephone number and the interconnected protocol IP address between the secondary telephone number mapping ENUM server and the network of the home location of the first fixed telephone number; or at least comprises an SIP URI of a first mobile phone number carrying a home area number and an SIP URI of the first fixed phone number;

the server is a primary ENUM server or a secondary ENUM server.

8. The server according to claim 7,

the number of the called user is one of the first mobile phone number or the first fixed phone number;

the processing unit is specifically configured to query whether an SIP URI of the number of the called user exists in a data area indicated by the tag of the source secondary ENUM server, and specifically configured to acquire the SIP URI of the number of the called user if the SIP URI of the number of the called user exists, and specifically configured to acquire a user attribute identifier if the SIP URI of the number of the called user does not exist and a server to which the number of the called user belongs is the source secondary ENUM server, where the user attribute identifier is used to indicate that the called user is a non-IP multimedia subsystem IMS user;

the sending unit is specifically configured to send the query request to a primary ENUM server if the processing unit determines that the SIP URI of the number of the called subscriber does not exist and the server of the home location of the number of the called subscriber is not the source secondary ENUM server;

the receiving unit is specifically configured to receive the query result sent by the primary ENUM server.

9. The server according to claim 8,

the processing unit is further configured to query a home network domain name of the number of the called subscriber in a first data area of the primary ENUM server, and acquire the home network domain name of the number of the called subscriber; or, the second data area is further used for acquiring an IP address of a destination secondary ENUM server in the second data area of the primary ENUM server, where the destination secondary ENUM server is a server of a home location of the called subscriber;

the sending unit is specifically configured to send the query request to the destination secondary ENUM server;

the receiving unit is specifically configured to receive the query result sent by the destination secondary ENUM server.

10. The server according to claim 9,

the processing unit is specifically configured to query whether an SIP URI of the number of the called user exists in a data area indicated by the tag of the destination secondary ENUM server, and specifically configured to acquire the SIP URI of the number of the called user if the SIP URI of the number of the called user exists, and specifically configured to acquire the user attribute identifier if the SIP URI of the number of the called user does not exist.