CN105025454A - Billing method, system and network side equipment - Google Patents

Abstract

The embodiment of the invention discloses a charging method, comprising the steps of: a first network side device receiving a first call request, and determining the type of a calling user according to the first call request, wherein the first call request at least carries a calling number and a called number; when the calling user is a CS user, determining whether to perform long distance charging on a called user according to whether the called number carries a first callflag; and when the calling user is an IP IMS user, determining whether to perform long distance charging on the called user according to whether the access place of the calling user is inconsistent with the place where the first network side device is located. The embodiment of the invention also discloses a charging system and a network side device. The charging scheme of the embodiment is suitable for a group client to directly connect with an IMS domain through an ISBC in an SIP (Session Initiation Protocol) mode, can be applied to various user services, and has the characteristics of accurate charging and wide application range.

Description

Billing method, system and network side equipment

technical field

The present invention relates to the field of communication services, in particular to a charging method, system and network side equipment.

Background technique

In the business scenario where group customers access the operator's network through dedicated lines (time division multiplexing mode (TDM) dedicated lines and IP dedicated lines), the current billing principle stipulates that when a caller (individual user) calls a group customer through a direct dial special service number , and when long-distance traffic is involved, the called party (group customer) bears the long-distance charges of the calling party (individual user), and the calling party (individual user) only needs to pay local call charges or basic roaming charges.

Currently on the live network, group customers can only directly connect to the circuit domain (CS domain) through the Gateway Mobile Switching Center (GMSC) in the form of a TDM trunk. Since the bill cannot reflect the information of the calling place, the billing system of the operator cannot judge whether the bill is a long-distance bill, so it cannot collect the long-distance charges that the group customers need to bear, resulting in a large loss of revenue for the operator. The existing solution is to charge according to the incoming trunk of the GMSC. This solution requires the GMSC to strictly distinguish the incoming trunks as local trunks and long-distance trunks, and synchronize the trunk information to the billing system, and the billing system sorts all long-distance trunks. In the subsequent incoming calls, the called number is a special service number (such as 95588), and the long-distance fee will be charged to the group customer.

However, the above solution is only applicable to the business scenario where group customers are directly connected to the CS domain through the GMSC, and only for the case where the calling party (individual user) is a CS mobile phone. With the continuous upgrading of the internal communication system of group customers, more and more IP-based communication systems are deployed to the side of the group customer, and the group customer directly connects to the IMS domain through ISBC in the form of Session Initiation Protocol (SIP) relay It will soon become the mainstream access method, and its service objects will also be extended to all types of users, including CS mobile phone, IMS fixed-line and IMS mobile users. However, the application range of the above-mentioned billing scheme is narrow and not applicable. Therefore, in the scenario where group customers are directly connected to IMS, how to obtain the calling location of the calling CS user and the access location of the IMS user, and implement accurate billing for group customers is an urgent problem to be solved, and there is no relevant technical solution at present meet such needs.

Contents of the invention

In view of this, in order to solve the existing technical problems, the embodiments of the present invention provide:

A billing method comprising:

The first network side device receives a first call request, and determines the calling user type according to the first call request, and the first call request carries at least a calling number and a called number;

When the calling user is a circuit domain CS user, determine whether to perform toll charging for the called user according to whether the called number carries the first identifier; when the calling user is an IP Multimedia Subsystem IMS user, It is determined whether to perform long-distance charging for the called user according to whether the locality is inconsistent with the location of the first network side device.

Preferably, the first network-side device is an interworking border controller ISBC, and the first network-side device receives the first call request, including:

The ISBC receives the first call request from the media gateway control function MGCF, and the first call request does not carry the calling user access location information, or,

The ISBC receives a first call request from an I-CSCF or an S-CSCF, where the first call request carries information about the calling user's access location.

Preferably, the determining the calling user type according to the first call request includes:

Judging whether the first call request carries the information of the calling user's access location, if yes, determining that the calling user is an IMS user; otherwise, determining that the calling user is a CS user.

Preferably, the judging whether the first call request carries information about the calling user's access location includes:

Judging whether the value of the PANI header field of the first call request is not empty, if the value of the PANI header field is not empty, the first call request carries the information of the calling user's access location; otherwise, the first The call request does not carry the access location information of the calling user.

Preferably, before the ISBC receives the first call request from the media gateway control function MGCF, the method further includes:

The MGCF receives a second call request from a local trunk or a toll trunk, where the second call request carries a calling number and a called number;

When the second call request comes from a long-distance relay, and the called number does not include the area code of the called user, add the area code of the called user before the called number to generate the first call request; when the second call request When the second call request comes from a local relay, or the second call request comes from a long-distance relay, and the called number includes the area code of the called user, the called number is unified into a special service number that does not include the area code of the called user, and the second call request is generated. a call request;

Sending the first call request to ISBC.

Preferably, the method further includes: when it is determined that long-distance charging is performed on the called user, setting the value of the second identifier in the bill to true; The value of the second identifier of is set to false;

Carry out long-distance charging according to the second identifier in the bill.

A network side device, comprising: a receiving module, a first determining module, a second determining module, a third determining module and a billing module; wherein,

The receiving module is configured to receive a first call request, and the first call request carries at least a calling number and a called number;

The first determining module is configured to determine the calling user type according to the first call request;

The second determining module is configured to determine whether to perform long-distance charging for the called user according to whether the called number carries the first identifier when the first determining module determines that the calling user is a CS user;

The third determination module is configured to determine whether to perform long-distance charging for the called user according to whether the access location of the calling user is inconsistent with the location of the network side device when the first determination module determines that the calling user is an IMS user;

The billing module is configured to perform billing according to the determination result of the second determination module or the third determination module.

Preferably, the network side device is an ISBC.

Preferably, the first determination module is specifically configured to determine whether the first call request carries the information of the calling user's access location, and if so, determine that the calling user is an IMS user; otherwise, determine that the calling user is a CS user.

Preferably, the first determination module is specifically configured to determine whether the value of the PANI header field of the first call request is not empty, and if the value of the PANI header field is not empty, the first call request carries Information about the access location of the calling user; otherwise, the first call request does not carry the information about the access location of the calling user.

Preferably, the network side device also includes a bill storage module,

The bill storage module is used to store bills;

The second determination module or the third determination module is used to notify the bill storage module to set the value of the second identifier in the corresponding bill to true when determining toll charging for the called user; otherwise, the The value of the second identifier in the list is set to false;

The charging module is specifically configured to perform long-distance charging according to the second identifier in the bill.

A network side device, including: a receiving module, a conversion module and a sending module; wherein,

The receiving module is configured to receive a second call request, and the second call request carries a calling number and a called number;

The conversion module is used to add the area code of the called user before the called number to generate the first call request when the second call request comes from a long-distance relay and the called number does not include the area code of the called user; When the second call request comes from a local trunk, or the second call request comes from a toll trunk, and the called number includes the area code of the called user, unify the called number to not include the area code of the called user the special service number to generate the first call request;

The sending module is configured to send the first call request.

Preferably, the network side device is an MGCF,

The receiving module is specifically configured to receive a second call request from a local relay or a long-distance relay;

The sending module is specifically configured to send the first call request to ISBC.

A billing system includes the above-mentioned network side equipment.

In the charging method, system, and network-side equipment described in the embodiments of the present invention, the first network-side equipment receives the first call request, determines the type of the calling user according to the first call request, and the first call request at least carries the Calling number and called number; when the calling user is a circuit domain CS user, determine whether to perform long-distance charging for the called user according to whether the called number carries the first identifier; when the calling user is an IP Multimedia Subsystem IMS user At this time, it is determined whether to perform long-distance charging for the called user according to whether the access location of the calling user is inconsistent with the location of the first network-side device. The billing scheme described in the embodiment of the present invention is applicable to the scenario where group customers directly connect to the IMS domain through ISBC through SIP relay, and is oriented to various user services, with accurate billing and a wide application range.

Description of drawings

FIG. 1 is a schematic flow chart of a billing method according to an embodiment of the present invention;

FIG. 2 is a schematic structural diagram of a network side device according to an embodiment of the present invention;

FIG. 3 is a schematic structural diagram of yet another network-side device according to an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of yet another network-side device according to an embodiment of the present invention;

Fig. 5 is the calling routing figure that the group client directly connects to the IMS domain through the ISBC in Embodiment 1 of the present invention, and the CS mobile phone user is the calling party;

Fig. 6 is the call routing diagram of the group customer directly connected to the IMS domain through the ISBC in Embodiment 2 of the present invention, and the IMS mobile phone and the fixed-line user as the calling party;

Fig. 7 is a schematic flow chart of the billing method according to Embodiment 3 of the present invention.

Detailed ways

Table 1 shows the billing principles when a group customer accesses the operator's network through a TDM trunk and acts as a called party:

Table 1

As shown in Table 1, when the calling party (individual user) calls the group customer by direct dialing the special service number (95588), if long-distance traffic is involved, the called party (group customer) shall bear the long-distance charges of the calling party, and the calling party Calls (individual users) only need to pay local call charges or basic roaming charges.

In the billing scheme described in the embodiment of the present invention, the billing principles after the group customers directly connect to the IMS through SIP trunking will also follow the above principles.

The embodiment of the present invention proposes a charging method, as shown in Figure 1, the method includes:

Step 101: The first network side device receives a first call request, determines the calling user type according to the first call request, and the first call request carries at least a calling number and a called number;

Step 102: When the calling user is a circuit domain CS user, determine whether to perform toll charging for the called user according to whether the called number carries the first identifier; Whether the calling user's access location is inconsistent with the location of the first network-side device determines whether to perform long-distance charging for the called user.

Optionally, the first identifier may specifically be an area code.

Optionally, the first network-side device is an interworking border controller ISBC, and step 101, where the first network-side device receives the first call request, includes:

The ISBC receives the first call request from the media gateway control function MGCF, and the first call request does not carry the calling user access location information, or,

The ISBC receives a first call request from an I-CSCF or an S-CSCF, where the first call request carries information about the calling user's access location.

Optionally, determining the calling user type according to the first call request in step 101 includes:

Judging whether the first call request carries the information of the calling user's access location, if yes, determining that the calling user is an IMS user; otherwise, determining that the calling user is a CS user.

Optionally, the judging whether the first call request carries the calling user access location information includes:

Judging whether the value of the PANI header field of the first call request is not empty, if the value of the PANI header field is not empty, the first call request carries the information of the calling user's access location; otherwise, the first The call request does not carry the access location information of the calling user.

Optionally, before the ISBC receives the first call request from the media gateway control function MGCF, the method further includes:

The MGCF receives a second call request from a local trunk or a toll trunk, where the second call request carries a calling number and a called number;

When the second call request comes from a long-distance relay, and the called number does not include the area code of the called user, add the area code of the called user before the called number to generate the first call request; when the second call request When the second call request comes from a local relay, or the second call request comes from a long-distance relay, and the called number includes the area code of the called user, the called number is unified into a special service number that does not include the area code of the called user, and the second call request is generated. a call request;

Sending the first call request to ISBC.

Optionally, the method further includes: when it is determined that long-distance charging is performed on the called user, setting the value of the second identifier in the bill to true; The value of the second identifier of is set to false;

Carry out long-distance charging according to the second identifier in the bill.

The embodiment of the present invention also correspondingly proposes a network side device. As shown in FIG. fee module 25; where,

A receiving module 21, configured to receive a first call request, the first call request carrying at least a calling number and a called number;

The first determining module 22 is configured to determine the calling user type according to the first call request;

The second determining module 23 is used to determine whether to carry out long-distance charging to the called user according to whether the called number carries the first identifier when the first determining module 22 determines that the calling user is a CS user;

The third determining module 24 is used to determine whether to perform toll charging for the called user according to whether the calling user's access location is inconsistent with the location of the network side device when the first determining module 22 determines that the calling user is an IMS user;

The billing module 25 is configured to perform billing according to the determination result of the second determination module 23 or the third determination module 24 .

Optionally, the network side device is an ISBC.

Optionally, the first determination module 22 is specifically configured to determine whether the first call request carries the information of the calling user's access location, and if so, determine that the calling user is an IMS user; otherwise, determine that the calling user is a CS user.

Optionally, the first determination module 22 is specifically configured to determine whether the value of the PANI header field of the first call request is not empty, and if the value of the PANI header field is not empty, the first call request carries the main The calling user access information; otherwise, the first call request does not carry the calling user access information.

Optionally, as shown in FIG. 3, the network side device also includes a bill storage module 26,

Bill storage module 26, used for storing bills;

The second determination module 23 or the third determination module 24 are used to notify the bill storage module 26 to set the value of the second identifier in the corresponding bill to true when determining that the called user is charged for long distance; otherwise, The value of the second identifier in the bill is set to false;

The charging module 25 is specifically configured to perform long-distance charging according to the second identifier in the bill.

The embodiment of the present invention also correspondingly proposes a network side device, as shown in FIG. 4 , the network side device includes: a receiving module 41, a converting module 42, and a sending module 43; wherein,

A receiving module 41, configured to receive a second call request, the second call request carrying a calling number and a called number;

The conversion module 42 is used to add the area code of the called user before the called number to generate the first call request when the second call request comes from a long-distance relay and the called number does not include the area code of the called user. If the second call request comes from a local relay, or if the second call request comes from a long-distance relay, and the called number includes the area code where the called user is located, unify the called number to one that does not include the area code where the called user resides. Special service number, generate the first call request;

A sending module 43, configured to send the first call request.

Optionally, the network side device is an MGCF,

The receiving module 41 is specifically configured to receive a second call request from a local relay or a long-distance relay;

The sending module 43 is specifically configured to send the first call request to ISBC.

The embodiment of the present invention also correspondingly proposes a billing system, which includes the network-side device shown in FIG. 2 or 3 and the network-side device shown in FIG. 4 .

The technical solution of the present invention will be further described in detail through specific examples below.

It should be noted that, in the following embodiments of the present invention, the key to whether to charge the group customer the long-distance fee is to judge the information of the caller CS mobile phone's place of speech (i.e. roaming) and the IMS user's access location, and compare the group customer's location information, In this way, it is judged whether the call occupies long-distance network resources. Pass this information to the billing point of the group customer, and use this as a basis to charge the long-distance fee to the group customer. When a group customer directly connects to the IMS domain through ISBC, the billing point of the group customer is ISBC, and ISBC issues the called bill.

Example 1

In this embodiment, the group customer is directly connected to the IMS domain through the ISBC, the CS mobile phone user is the calling party, and the group customer is the called party.

Fig. 5 is the group client directly connected IMS domain by ISBC in the embodiment 1 of the present invention, and the call routing diagram of the CS mobile phone user as the calling party, as shown in Fig. To call a group customer from the location and non-group customer's location, the dialing method can be to directly dial the special service number (95588) or dial the group customer's area code (01095588) before the special service number.

In this scenario, in order to collect long-distance call charges from group customers, ISBC needs to know whether it is a long-distance call or a local call. Since the calling location (roaming location) information of the CS mobile phone cannot be transmitted from the CS network to the IMS network through the MGCF, and cannot be transmitted to the billing point ISBC of the group customer, this embodiment defines a special called number regulation principle for the MGCF. To realize the distinction between local and long-distance incoming calls, the solution is as follows:

1) The MGCF distinguishes between local and long distance relays.

2) MGCF performs number regulation on incoming calls, specifically:

Local trunk calls, and the called number is a special service number (such as 95588), and the called number is not regularized (still 95588);

Incoming calls from the local trunk, and the called number is the area code of the group customer + the special service number (01095588), and the called number is adjusted to the special service number (95588);

For long-distance relay incoming calls, and the called number is a special service number (95588), add the area code (regularly 01095588) before the called number;

For long-distance relay incoming calls, and the called number is the area code of the group customer + special service number (01095588), delete the area code (regularized to 95588).

In this embodiment, the first identifier is the area code.

3) ISBC generates a bill according to the call request from MGCF, and judges the caller (individual user) type by identifying the Access-Network-Info field in its own bill: if this field is empty, the caller is a CS mobile phone; If the field is not empty, the caller is an IMS user.

4) ISBC judges the type of the called number again. If the called number is a special service number (95588), the value of the identifier is true (Callflag is set to 1); if the called number is preceded by an area code (01095588), the identifier The value is false (Callflag is set to 0);

In this embodiment, the newly added identifier Callflag (i.e. the second identifier) in the ISBC call list is used to identify whether the bill needs to collect long-distance charges, and when the value of the identifier is true, it shows that long-distance charges need to be collected (Callflag= 1), when the value is false, it indicates that long-distance charges do not need to be charged (Callflag=0).

5) The operator's billing system charges group customers long-distance charges in the scenario of Callflag=1

Example 2

In this embodiment, the group customer is directly connected to the IMS domain through the ISBC, the IMS mobile phone and the fixed line user are the calling party, and the group customer is the called party.

Fig. 6 is the call routing diagram of the group customer directly connecting the IMS domain through ISBC in the embodiment 2 of the present invention, and the IMS mobile phone and the fixed-line user make the caller, as shown in Fig. Or IMS users in other provinces (including IMS mobile phones and fixed lines) call group customers respectively, and the dialing method can be to directly dial the special service number (95588) or dial the area code of the group customer (01095588) before the special service number.

In this scenario, in order to collect long-distance call charges from group customers, it is necessary to transfer the access location information of IMS users to the group customer's billing point ISBC, and then charge corresponding fees from the perspective of using network resources. The solution is as follows:

1) ISBC generates a bill according to the call request from I-CSCF or S-CSCF. The Access-Network-Info field in the ISBC bill comes from the PANI header field and is used to identify the information of the IMS user's access location. The format is SBC1.010 .SBC.chinamobile.com (this field is empty when a CS user dials)

2) When the Access-Network-Info field is not empty (indicating that the calling party is an IMS user):

ISBC compares its own location information with the Access-Network-Info field. If they are different, it means that the caller (IMS user) roams to a non-corporate customer location, and the call will occupy long-distance network resources. If the called number is a special service number (95588 ), then the value of the identifier is true (CallFlag=1);

If it is different, the caller (IMS user) roams to a non-group customer location, and the call will occupy long-distance network resources, but if the called number is preceded by an area code (01095588), there is no need to charge long-distance charges, and the value of the identifier is false (Callflag is set to 0)

If they are the same, the user roams to the location of the group customer, and the call will not occupy long-distance network resources. No matter whether the called number has an area code or not, long-distance charges do not need to be charged, and the value of the identifier is false (Callflag is set to 0).

It should be noted that, in this embodiment, a new identifier Callflag (corresponding to the second identifier) is added in the ISBC bill, which is used to identify whether the bill needs to collect long-distance charges. When the value of the identifier is true, it indicates that it needs to collect Long-distance fee (Callflag=1), when the value is false, it indicates that long-distance fee (Callflag=0) is not required.

3) The operator's billing system charges the group customer the long-distance fee in the scenario of Callflag=1.

Example 3

This embodiment describes the billing method when a group customer accesses the IMS domain through an ISBC with a SIP trunk, and when the group customer is called, FIG. 7 is a schematic flow chart of the billing method described in Embodiment 3 of the present invention, as As shown in Figure 7, the process includes:

Step 701: ISBC judges the source of the caller according to the IMS user access information, that is, judges whether the IMS user access information is empty, if yes, it means that the caller is a CS mobile phone, and proceeds to step 702; if the IMS user access information is not empty, Indicates that the calling party is an IMS user, go to step 705.

Step 702: Determine whether there is an area code before the called number and whether the called number is a special service number, if there is an area code before the called number and the called number is a special service number, go to step 703; otherwise, go to step 704.

Step 703: Determine to charge the long-distance fee to the called group customer.

Step 704: Determine that no long-distance fee will be charged to the called group customer.

Step 705: Determine whether the IMS user access location information is different from the ISBC location information, and whether the called number is a special service number, if the IMS user access location information is different from the ISBC location information, and the called number is a special service number, execute Step 706; otherwise, go to step 707.

Step 706: Determine to charge the long-distance fee to the called group customer.

Step 707: Determine that no long-distance fee will be charged to the called group customer.

In this embodiment, a new identifier is added in the ISBC call list, which is used to identify whether the call list charges long-distance charges to the called group customer. When it is false, it means that the long-distance fee will not be charged to the called group customer.

It should be noted that, for the scenario where the calling party is an IMS user, the ISBC obtains the call information from the MGCF, and the MGCF needs to perform the following processing after receiving the call request from the trunk:

Distinguish between local trunks and toll trunks;

Regularize the called number of the incoming call. When the long-distance relay incoming call and the called number is a special service number without an area code, the area code is added before the called number. In other cases, the called number is adjusted to be without an area code special service number.

In a word, in the above-mentioned embodiment of the present invention, in the scenario where the group customer is directly connected to the IMS domain through the ISBC through the SIP trunk, no matter the caller (individual user) is from the CS domain or the IMS domain, once the long-distance traffic is involved, the The unified principle is the method and process of billing group customers according to the usage of network resources; and, after knowing that the calling party is a mobile phone user, define a special number regulation principle for MGCF to distinguish between long-distance and local traffic; after knowing that the calling party is an IMS mobile phone Or fixed-line users, ISBC judges whether to charge long-distance charges to group customers based on the comparison of its own location information and IMS user access information.

Compared with related technologies, the embodiment of the present invention is applicable to the scenario where group customers directly connect to the IMS domain through ISBC, and can implement a unified charging principle for all users (CS mobile phone, IMS mobile phone and solidification), which is different from the current charging principle Be consistent and implement accurate billing based on network resource usage.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention.

Claims (14)

1. A billing method, characterized in that the method comprises: The first network side device receives a first call request, and determines the calling user type according to the first call request, and the first call request carries at least a calling number and a called number; When the calling user is a circuit domain CS user, determine whether to perform toll charging for the called user according to whether the called number carries the first identifier; when the calling user is an IP Multimedia Subsystem IMS user, It is determined whether to perform long-distance charging for the called user according to whether the locality is inconsistent with the location of the first network side device. 2. The method according to claim 1, wherein the first network-side device is an interworking border controller (ISBC), and the first network-side device receives the first call request, comprising: The ISBC receives the first call request from the media gateway control function MGCF, and the first call request does not carry the calling user access location information, or, The ISBC receives a first call request from an I-CSCF or an S-CSCF, where the first call request carries information about the calling user's access location. 3. The method according to claim 2, wherein said determining the calling user type according to the first call request comprises: Judging whether the first call request carries the information of the calling user's access location, if yes, determining that the calling user is an IMS user; otherwise, determining that the calling user is a CS user. 4. The method according to claim 3, wherein the judging whether the first call request carries the information of the calling user's access location comprises: Judging whether the value of the PANI header field of the first call request is not empty, if the value of the PANI header field is not empty, the first call request carries the information of the calling user's access location; otherwise, the first The call request does not carry the access location information of the calling user. 5. The method according to claim 2, wherein, before the ISBC receives the first call request from the Media Gateway Control Function MGCF, the method further comprises: The MGCF receives a second call request from a local trunk or a toll trunk, where the second call request carries a calling number and a called number; When the second call request comes from a long-distance relay, and the called number does not include the area code of the called user, add the area code of the called user before the called number to generate the first call request; when the second call request When the second call request comes from a local relay, or the second call request comes from a long-distance relay, and the called number includes the area code of the called user, the called number is unified into a special service number that does not include the area code of the called user, and the second call request is generated. a call request; Sending the first call request to ISBC. 6. The method according to any one of claims 1 to 5, characterized in that the method further comprises: when determining that the called user is charged for long distance, setting the value of the second identifier in the bill to true ; When it is determined that long-distance billing is not performed on the called user, the value of the second identifier in the bill is set to false; Carry out long-distance charging according to the second identifier in the bill. 7. A network-side device, characterized in that the network-side device comprises: a receiving module, a first determining module, a second determining module, a third determining module, and a billing module; wherein, The receiving module is configured to receive a first call request, and the first call request carries at least a calling number and a called number; The first determining module is configured to determine the calling user type according to the first call request; The second determining module is configured to determine whether to perform long-distance charging for the called user according to whether the called number carries the first identifier when the first determining module determines that the calling user is a CS user; The third determination module is configured to determine whether to perform long-distance charging for the called user according to whether the access location of the calling user is inconsistent with the location of the network side device when the first determination module determines that the calling user is an IMS user; The billing module is configured to perform billing according to the determination result of the second determination module or the third determination module. 8. The network-side device according to claim 7, wherein the network-side device is an ISBC. 9. The network side device according to claim 7, characterized in that, The first determination module is specifically used to determine whether the first call request carries the information of the calling user's access location, and if so, determine that the calling user is an IMS user; otherwise, determine that the calling user is a CS user. 10. The network side device according to claim 7, characterized in that, The first determining module is specifically configured to judge whether the value of the PANI header field of the first call request is not empty, and if the value of the PANI header field is not empty, the first call request carries the Incoming location information; otherwise, the first call request does not carry the information about the calling user's access location. 11. The network side device according to claim 7, characterized in that, the network side device further comprises a bill storage module, The bill storage module is used to store bills; The second determination module or the third determination module is used to notify the bill storage module to set the value of the second identifier in the corresponding bill to true when determining toll charging for the called user; otherwise, the The value of the second identifier in the list is set to false; The charging module is specifically configured to perform long-distance charging according to the second identifier in the bill. 12. A network side device, characterized in that the network side device includes: a receiving module, a conversion module and a sending module; wherein, The receiving module is configured to receive a second call request, and the second call request carries a calling number and a called number; The conversion module is used to add the area code of the called user before the called number to generate the first call request when the second call request comes from a long-distance relay and the called number does not include the area code of the called user; When the second call request comes from a local trunk, or the second call request comes from a toll trunk, and the called number includes the area code of the called user, unify the called number to not include the area code of the called user the special service number to generate the first call request; The sending module is configured to send the first call request. 13. The network side device according to claim 12, characterized in that the network side device is an MGCF, The receiving module is specifically configured to receive a second call request from a local relay or a long-distance relay; The sending module is specifically configured to send the first call request to ISBC. 14. A billing system, characterized in that the billing system comprises the network side device according to any one of claims 7 to 11, and the network side device according to claim 12 or 13.