CN100461927C - A method for implementing an application based on terminal access attributes - Google Patents

Abstract

The present invention provides a technical solution for an application implementation method based on terminal access attributes. The SGSN in the present invention transmits the terminal access attribute information to the application side, so that the application side can realize the application based on the received access attribute information. The application of terminal access attributes. The application side here generally refers to network elements that need to use access attribute information, such as SGSN, GGSN, CCG, etc. The applications based on terminal access attributes here include content billing and terminal attachment. related performance statistics in the terminal routing area update process, related performance statistics in the terminal PDP activation process, PDP billing, terminal access control, service scheduling based on different scheduling policies, etc.; thus through this The technical solution provided by the invention achieves the purpose of improving the implementation flexibility of applications based on terminal access attributes.

Description

A method for implementing an application based on terminal access attributes

technical field

The present invention relates to the technical field of network communication, in particular to an application implementation method based on terminal access attributes.

Background technique

In the mobile communication system, in order to provide users with high-quality and diversified service quality to attract more users, applications based on terminal access attributes have been gradually developed, and have been increasingly valued by operators.

Applications based on terminal access attributes such as content billing, related performance statistics during the terminal attachment process, related performance statistics during the terminal cross-SGSN routing area update process, related performance statistics during the terminal PDP (packet data protocol) activation process, Access policies for terminals, access restrictions for terminals, scheduling policies for terminals, etc.

The application based on the terminal access attribute will be described below in conjunction with two specific examples.

Example 1. Content billing.

With the widespread application of users' group Internet access services through terminals, a group of SPs (Service Providers) that provide users with services and content have also emerged as the times require. In order to balance the interests of all parties in the service value chain and promote SP to provide users with richer services, operators have widely adopted content billing schemes.

At present, content charging schemes mainly include two types, one is to implement content charging by CCG through an external CCG (Content Charging Gateway) on the Gi interface; the other is to directly implement content charging by GGSN (GPRS Gateway Support Node) Billing. The two content billing schemes are:

The implementation principle of Scheme 1 is shown in Fig. 1 . In Figure 1, a charging gateway CCG is added between the GGSN and the external network. The CCG stores information such as the IP port number of the destination address accessed by the user, URL (Uniform Resource Locator) uplink and downlink traffic, and the CCG sends these information to The billing system, operators can provide flexible content-based billing policies according to the information received by the billing system.

The complete billing process when the terminal performs packet services is shown in Figure 2.

In Fig. 2, after receiving the creation PDP request sent by SGSN (GPRS service support node), GGSN sends an access request to the AAA (authentication, authorization, accounting) server when it is determined that the user is a non-transparent access, and the AAA The server authenticates the user, and after the authentication is passed, the GGSN sends an Accounting Request (accounting request) message carrying accounting start information to the CCG, and the CCG starts accounting for the user. When deactivating, the GGSN sends an AccountingRequest message carrying accounting stop information to the CCG, and the CCG ends accounting for the user.

In Solution 1, since the CCG cannot distinguish whether the user accesses from 2G or 3G, the operator can only adopt the same charging policy for 2G and 3G users. Some operators want to adopt different billing rates for 2G and 3G access users due to operational strategy considerations. The application side in Solution 1, that is, CCG, cannot meet the differentiated billing requirements of operators.

The realization principle of scheme 2 is shown in Fig. 3 . In Figure 3, the GGSN is responsible for the content billing function. The GGSN stores information such as the IP port number of the destination address accessed by the user, URL uplink and downlink traffic, etc., and the GGSN sends this information to the billing system, and the operator can receive it according to the billing system. The information provides flexible content-based charging policies.

In solution 2, the GGSN and CG (billing gateway) cannot distinguish whether the user accesses from 2G or 3G, which also causes the operator to only adopt the same charging policy for 2G and 3G users. The application side in solution 2, that is, the GGSN, also cannot meet the operator's differentiated billing requirements.

Example 2: Related performance statistics during the inter-SGSN attachment process of the terminal.

In the WCDMA system, after the terminal is turned on in the jurisdiction area of SGSN A, it attaches to SGSN A through the access network, after that, the terminal turns off and separates from SGSN A. When the terminal moves to the jurisdiction area of SGSN B in the shutdown state and is powered on, the terminal attaches to SGSN B through the access network. At this time, the terminal undergoes a cross-SGSN attachment process, which is the Inter SGSN Attach process. , SGSN A is the old SGSN, and SGSN B is the new SGSN.

According to the access attributes of the terminal on the old side SGSN and the new side SGSN, Inter SGSN Attach (cross-SGSN attachment) may have the following situations: Inter SGSN 3G to 3G Attach, Inter SGSN 2G to 2G Attach, Inter SGSN 3G to 2G Attach, Inter SGSN SGSN 2G to 3G Attach.

The old-side SGSN can know the terminal's access attributes at the local end, but it does not know the terminal's access attributes at the new-side SGSN. Therefore, the old-side SGSN cannot collect statistics on the relevant performance during the Inter SGSN Attach process. Make statistics on Inter SGSN 3G to 3G Attach handover success rate and other related performance.

Similarly, in other applications based on terminal access attributes, the application side cannot effectively distinguish the terminal access attributes.

It can be seen from the above description that in the application based on the terminal access attribute, since the application side cannot distinguish the terminal access attribute, the application side cannot flexibly implement various applications according to the terminal access attribute.

Contents of the invention

The purpose of the present invention is to provide a technical solution for implementing an application based on terminal access attributes. By transmitting the access attribute information of the terminal, the application side can implement various applications for terminals with different access attributes, and improve the efficiency of terminal access attributes. implementation flexibility in the application of input attributes.

In order to achieve the above object, the technical scheme of the implementation method based on the application of the terminal access attribute provided by the present invention, different access attributes correspond to different GTPC IP address information of the GPRS service support node SGSN, and the method includes:

a. The GPRS service support node SGSN determines the access attribute of the terminal according to the GTPC IP address accessed by the terminal, and transmits the access attribute information of the terminal to the application side;

b. The application side realizes the application based on the terminal access attribute according to the received access attribute information.

The access attributes include: 2G access, 3G access.

In the step b, the application based on the terminal access attribute is: content billing, or related performance statistics during the terminal attachment process, or related performance statistics during the terminal routing area update process, or terminal PDP (packet data protocol) activation Related performance statistics during the process, or PDP charging, or terminal access control, or service scheduling.

The application based on the terminal access attribute is: content charging, the application side is: the billing system, the access attribute information is: the GTPC IP address information of the SGSN that the terminal accesses, and different access attributes correspond to different GTPCs of the SGSN IP address information;

Described step a comprises:

The SGSN transmits the GTPC IP address corresponding to the terminal access attribute to the billing system through the GPRS gateway support node GGSN, or through the GGSN and CCG.

When different access networks use different SGSNs, different SGSNs are set with different GTPC IP addresses;

When different access networks share the same SGSN, in the SGSN, different access attributes are set with different GTPC IP addresses.

When different access networks share the same SGSN, in step a:

The SGSN carries the GTPC IP address corresponding to the terminal access attribute in the create PDP context request message and transmits it to the GGSN;

The GGSN obtains the GTPC IP address from the PDP Context Request message;

The GGSN carries the GTPC IP address in the Vendor-Specific field of the charging request message and transmits it to the charging system, or transmits it to the CCG, and the CCG transmits it to the charging system.

When different access networks use different SGSNs, in step a:

The GGSN carries the SGSN GTPC IP address corresponding to the terminal access attribute in the Vendor-Specific field of the RADIUS message and transmits it to the CCG, and the CCG transmits it to the billing system.

The method also includes:

When the terminal performs inter-system handover and the IP address of the SGSN corresponding to the terminal's access attribute changes, the SGSN notifies the GGSN, or notifies the GGSN and CCG, and updates the location information of the terminal to the HLR.

The application side is GSN, and the step a includes:

The SGSN transmits the terminal access attribute information to the GSN by adding the set GTP extension header.

When the application side cannot identify the GTP extension header in the message it receives, it transmits the information that does not recognize the extension header and the extension header information it supports to the SGSN;

After receiving the information that does not recognize the extension header, the SGSN deletes the extension header that cannot be recognized by the application side according to the supported extension header information, and resends the message.

In the step b, the relevant performance statistics during the terminal attachment process include:

Relevant performance statistics of the Inter SGSN 3G to 3G Attach process of the new/old side SGSN; and/or

Relevant performance statistics of the Inter SGSN 2G to 2G Attach process of the new/old side SGSN; and/or

Relevant performance statistics of the Inter SGSN 3G to 2G Attach process of the new/old side SGSN; and/or

Performance statistics related to the Inter SGSN 2G to 3G Attach process of the new/old side SGSN.

In the step b, the relevant performance statistics in the update process of the terminal routing area include:

Relevant performance statistics of the Inter SGSN 3G to 3G RAU process of the new/old side SGSN; and/or

Relevant performance statistics of the Inter SGSN 2G to 2G RAU process of the new/old side SGSN; and/or

Relevant performance statistics of the Inter SGSN 3G to 2G RAU process of the new/old side SGSN; and/or

Performance statistics of the Inter SGSN 2G to 3G RAU process of the new/old side SGSN.

In the step b, the relevant performance statistics during the PDP activation process of the terminal includes: the GGSN performs relevant performance statistics during the PDP activation process for the terminals accessed through the BSS, and/or the GGSN performs the PDP activation process for the terminals accessed through the UTRAN Relevant performance statistics in .

In the step b, the terminal access control includes: the GGSN controls the terminal access based on the access control strategy and/or the GGSN controls the terminal access based on the system load threshold.

From the description of the above technical solution, it can be seen that the application side can know the access attribute information of the terminal by transmitting the access attribute information of the terminal. etc., can implement content charging, performance statistics and other applications according to the access attributes of the terminal; in the content charging process, the SGSN in the present invention can use the PDP context creation request to transmit the access attribute information; in other applications, The SGSN in the present invention can transmit the access attribute information by adding the set message extension header, so that the purpose of improving the implementation flexibility of the application based on the terminal access attribute is realized through the technical solution provided by the present invention.

Description of drawings

FIG. 1 is a first schematic diagram of the implementation principle of content charging in the prior art;

Fig. 2 is a flow chart of charging for packet services performed by terminals in the prior art;

FIG. 3 is a second schematic diagram of the implementation principle of content charging in the prior art;

FIG. 4 is a flow chart of transmitting the access attribute information of the terminal to the GGSN and CCG according to the embodiment of the present invention;

FIG. 5 is a flow chart 1 of a complete 3G to 2G inter-system handover of a terminal according to an embodiment of the present invention;

FIG. 6 is a second flow chart of a complete handover between 2G and 3G systems of a terminal according to an embodiment of the present invention.

Detailed ways

In the application based on the terminal access mode, the SGSN (GPRS Service Support Node) can know the terminal's access mode. If the SGSN can transmit the terminal's access mode to the application side, the application side can know the terminal's access mode. In this way, the application side can perform different processing for different access methods of the terminal.

In the technical solution of the present invention, firstly, the SGSN needs to transmit the terminal's access attribute information to the application side, and the terminal's access attribute information can be transmitted to the application side in various ways, for example, the SGSN carries the terminal's access attribute information It is transmitted to the application side in the existing message, and for example, the SGSN transmits the terminal’s access attribute information to the application side through a newly set message, and the SGSN can directly transmit the terminal’s access attribute information to the application side. The access attribute information of the terminal may also be indirectly transmitted to the application side through other intermediate network elements. The present invention does not limit the method for transmitting terminal access attribute information between the SGSN and the application side.

After receiving the access attribute information of the terminal transmitted by the SGSN, the application side implements corresponding applications for the access attributes of different terminals. For example, the charging system adopts different charging methods to charge content for terminals with different access methods; For example, during the cross-SGSN attachment process of the terminal, the SGSNs on both sides can collect statistics on the related performance of the cross-SGSN attachment; for example, during the cross-routing area update process of the terminal, the SGSNs on both sides can perform statistics on the cross-SGSN routing area update related performance Statistics; if the terminal is in the PDP (packet data protocol) activation process, the GGSN can perform PDP activation-related performance statistics on the terminals accessed through BSS/UTRAN; if the terminal is in the PDP activation process, the GGSN can use differential PDP charging PDP billing for terminals with different access methods; for example, during the PDP activation process of the terminal, the GGSN controls the access of the terminal. The specific access control method can be determined according to the specific operation strategy, such as: configuration allows HPLMN users activate 3G PDP and 2G PDP, that is, users of this PLMN can activate PDP for packet domain data services no matter they access in 3G system or 2G system, but for VPLMN users, only 3G PDP is allowed to be activated , that is, if a VPLMN user accesses from a 3G access network, the user is allowed to activate PDP for packet domain data services, but if a VPLMN user accesses from a 2G access network, the user is not allowed to activate PDP in this GGSN; as another example, The operator can configure the load threshold of the GGSN system according to the needs, so as to ensure that when the number of users already connected to the GGSN reaches a certain threshold, certain system resources can be set aside to ensure the PDP activation success rate of certain access types of users.

The technical solution provided by the present invention will be further described below with several specific examples.

Example 1. Content billing.

During the content charging process, the SGSN needs to provide terminal access mode information to the GGSN or CCG, so that the CCG can distinguish the terminal access mode, and thus perform differentiated content charging for terminals with different access modes.

When 2G and 3G access networks share a SGSN, the present invention needs to set two GTPC (GPRS Tunneling Protocol Control, GPRS Tunneling Protocol Control Plane) IP addresses for this shared SGSN, and one of these two GTPC IP addresses is used for 2G access network and another for 3G access network. In this way, when the user accesses from the 2G access network, the GTPC IP address of the SGSN in the PDP context transmitted by the SGSN to the GGSN should be the GTPC IP address corresponding to the 2G access network; when the user accesses from the 3G access network, the SGSN The GTPC IP address of the SGSN in the PDP context transmitted to the GGSN should be the corresponding GTPC IP address of the 3G access network.

The GTPC IP address of the SGSN can be carried in the Create PDP Context Request (creating a PDP context request) message and transmitted to the GGSN. That is to say, in the charging process of the terminal performing the packet service in Figure 2, that is, in the PDP activation process, when the terminal accesses from the 2G access network, the GGSN can receive information from the CreatePDP Context Request (create PDP context request) message Obtain the GTPC IP address of the SGSN, and then, the GGSN carries the GTPC IP address of the SGSN in the Vendor-Specific field of the Accounting-Request message and transmits it to CCG, where the Accounting-Request message is the Accounting-Request message carrying the accounting start information . According to the GTPC IP address in the Vendor-Specific domain of the Accounting-Request message that it receives that carries the accounting start information, the CCG can accurately distinguish whether the terminal is connected from the 2G access network or the 3G access network. In this way, the CCG can perform content charging according to different charging policies corresponding to different preset access methods.

When the access attribute of the terminal changes, that is, when the terminal is handed over between systems, the SGSN needs to send the current access attribute information of the terminal, that is, the changed access attribute information, to the GGSN, so that the GGSN and CCG can know the terminal The changed access attribute information enables the CCG to change the charging policy of the terminal in time.

When the access attribute of the terminal changes, the SGSN in the present invention can send the current access attribute information of the terminal such as the GTPC IP address of the SGSN to the GGSN by updating the PDP context request, and the specific process is as shown in Figure 4.

In Fig. 4, in step 4-1, SGSN sends to GGSN an update PDP context request carrying the access attribute information of the terminal to notify GGSN: the GTPC IP address of the SGSN corresponding to the terminal has changed.

In step 4-2, after receiving the request to update the PDP context, the GGSN sends an Accounting Req (accounting request) message carrying Interim-Update information to the CCG to notify the CCG that the GTPC IP address of the SGSN corresponding to the terminal has changed. Change. The changed GTPC IP address of the SGSN can be carried in the Vendor-Specific field of the Accounting Req message.

In step 4-3, the CCG can accurately determine that the access attribute of the terminal has changed according to the GTPC IP address in the Vendor-Specific domain of the AccountingReq message that it receives with the Interim-Update information, and the CCG sends a message to the GGSN Accounting Res (accounting response) message.

In step 4-4, after receiving the Accounting Res message, the GGSN sends an update PDP context response message to the SGSN.

Through the process described in FIG. 4 , the CCG can update the access attribute information in the terminal bill in time, so that the CCG can use the terminal's current corresponding charging policy to charge the terminal for new content.

The above-mentioned inter-system handover of the terminal may be: a handover from 3G to 2G, that is, a handover from UMTS to GSM; it may also be: a handover from 2G to 3G, that is, a handover from GSM to UMTS.

When the terminal switches from 3G to 2G, the complete inter-system switching process of the terminal is shown in Fig. 5 .

In Fig. 5, steps 1 to 7, and steps 11 to 17 are the existing handover process of the terminal from 3G to 2G, and the present invention adds steps 8 to 10 in the existing handover process.

Step 8 is the process for the SGSN to update the PDP context to the GGSN. After SGSN updated PDP context to GGSN, to step 9, SGSN sends Update GPRS Location (update GPRS location) message to HLR, to update the location information of this terminal stored in HLR. The updated location information includes the GTPC IP address information of the SGSN. The purpose of updating the location information of the terminal is to enable the GGSN to obtain the correct SGSN GTPC information from the HLR during the activation process on the network side. To step 10, HLR updates the location information of the terminal stored in it according to the received message, and returns a Cancel Location (cancel location) message to the SGSN.

When the terminal switches from 2G to 3G, the complete inter-system switching process of the terminal is shown in Fig. 6 .

In Fig. 6, steps 1 to 3, and steps 7 to 10 are the existing handover process of the terminal from 2G to 3G, and the present invention adds steps 4 to 6 in the existing handover process.

Step 4 is the process for SGSN to update PDP context to GGSN. After the SGSN has updated the PDP context to the GGSN, go to step 5, and the SGSN sends an Update GPRS Location message to the HLR to update the location information of the terminal stored in the HLR. To step 6, the HLR updates the location information of the terminal it stores according to the received message, and returns a Cancel Location message to the SGSN, and the SGSN returns a Cancel Location Ack message to the HLR after receiving the Cancel Location message.

When the 2G and 3G access networks do not share the same SGSN, the GTPCIP addresses of the two SGSNs are different. Based on the existing protocol process, the IP address can be notified to the CCG through the Vendor-Specific field of the RADIUS message, and the CCG distinguishes according to the SGSN IP address. The type of access network used by the user.

The technical content described in the first example above is: the CCG provides the content charging information, so as to realize the content charging process based on the terminal access attribute. When adopting the technical scheme that GGSN provides content billing information, content billing can also be implemented according to the process descriptions in Figure 5 and Figure 6. It can be seen that GGSN can accurately obtain the IP address information of SGSN, and access When the network does not share a SGSN, based on the inter-system handover process stipulated in the current protocol, the GGSN can also obtain the IP address information of the SGSN, and can pass the SGSN IP to the CG in the GCDR. According to the GTPC IP address of the SGSN, the GGSN and the CG can distinguish from which access network the user accesses.

From the above description of Example 1, it can be known that the billing system of the present invention can provide the access attribute information of the terminal for the bill of content billing when performing content billing, so that the operator can formulate different Content charging rate, so as to achieve the purpose of differentiated charging.

Example 2: During the cross-SGSN attachment process of the terminal, the old SGSN of the terminal performs related performance statistics.

During the cross-SGSN attachment process of the terminal, the new SGSN can know the local access attributes of the terminal, and the new SGSN needs to transmit the local access attribute information of the terminal to the old SGSN. The new-side SGSN can use the existing message to transmit the terminal's local access attribute information to the old-side SGSN, or use a newly set message to transmit the terminal's local-side access attribute information to the old-side SGSN. In the following embodiments, the new side SGSN uses the newly set message header to transmit the access attribute information in detail.

Since the old-side SGSN can know the access attributes of the terminal at the local end, after receiving the access attributes transmitted by the new-side SGSN, the old-side can distinguish the access attributes of the terminal at the local end and the new-side SGSN. That is to say, it is possible to know which type of Inter SGSN Attach occurred on the terminal. Therefore, the old-side SGSN can collect statistics on related performance during the terminal attachment process. The related performance statistics here can be subdivided into: Inter SGSN 3G to 3G Attach related performance statistics, Inter SGSN 2G to 2G Attach related performance statistics, Inter SGSN 3G to 2G Attach related performance statistics, Inter SGSN 2G to 3G Attach related performance statistics.

Example 3: During the inter-SGSN attachment process of the terminal, the SGSN on the new side of the terminal performs related performance statistics.

During the cross-SGSN attachment process of the terminal, the old SGSN can know the local access attributes of the terminal, and the old SGSN needs to transmit the local access attribute information of the terminal to the new SGSN. The old-side SGSN can use the existing message to transmit the terminal's local access attribute information to the new-side SGSN, or use a newly set message to transmit the terminal's local-side access attribute information to the new-side SGSN. In the following embodiments, a detailed introduction will be given to the use of the newly set message header by the old SGSN to transmit the access attribute information.

Since the new SGSN can know the access attributes of the terminal at the local end, after receiving the access attributes transmitted by the old SGSN, the new side can distinguish the access attributes of the terminal at the local end and the old SGSN, and also That is to say, it is possible to know which type of Inter SGSN Attach occurred on the terminal. Therefore, the SGSN on the new side can collect statistics on related performance in the terminal attachment process. The related performance statistics here can be subdivided into: Inter SGSN 3G to 3G Attach related performance statistics, Inter SGSN 2G to 2G Attach related performance statistics, Inter SGSN 3G to 2G Attach related performance statistics, Inter SGSN 2G to 3G Attach related performance statistics.

Example 4: During the inter-SGSN routing area update process of the terminal, the old-side SGSN of the terminal performs related performance statistics.

During the cross-SGSN routing area update process of the terminal, the new-side SGSN can know the terminal's local access attributes, and the new-side SGSN needs to transmit the terminal's local access attribute information to the old-side SGSN. The new-side SGSN can use the existing message to transmit the terminal's local access attribute information to the old-side SGSN, or use a newly set message to transmit the terminal's local-side access attribute information to the old-side SGSN. In the following embodiments, the new side SGSN uses the newly set message header to transmit the access attribute information in detail.

Since the old-side SGSN can know the access attributes of the terminal at the local end, after receiving the access attributes transmitted by the new-side SGSN, the old-side can distinguish the access attributes of the terminal at the local end and the new-side SGSN. That is to say, it is possible to know which type of routing area update process has occurred in the terminal. Therefore, the old-side SGSN can make statistics on the relevant performance in the routing area update process of the terminal. The relevant performance statistics here can be subdivided into: Inter SGSN 3G to 3G RAU (cross-SGSN3G to 3G routing area update) related performance statistics items, Inter SGSN 2G to 2G RAU related performance statistics items, Inter SGSN 3G to2G RAU related performance statistics Items, Inter SGSN 2G to 3G RAU related performance statistics items.

Example 5: During the process of updating the cross-SGSN routing area of the terminal, the SGSN on the new side of the terminal performs related performance statistics.

During the cross-SGSN routing area update process of the terminal, the old-side SGSN can know the terminal's local access attributes, and the old-side SGSN needs to transmit the terminal's local access attribute information to the new-side SGSN. The old-side SGSN can use the existing message to transmit the terminal's local access attribute information to the new-side SGSN, or use a newly set message to transmit the terminal's local-side access attribute information to the new-side SGSN. In the following embodiments, a detailed introduction will be given to the use of the newly set message header by the old SGSN to transmit the access attribute information.

Since the new SGSN can know the access attributes of the terminal at the local end, after receiving the access attributes transmitted by the old SGSN, the new side can distinguish the access attributes of the terminal at the local end and the old SGSN, and also That is to say, it is possible to know which type of routing area update has occurred in the terminal. Therefore, the new-side SGSN can make statistics on the relevant performance in the update process of the terminal routing area. The relevant performance statistics here can be subdivided into: Inter SGSN 3G to 3G RAU related performance statistics items, Inter SGSN 2G to 2G RAU related performance statistics items, Inter SGSN 3G to 2G RAU related performance statistics items, Inter SGSN 2G to 3G RAU related performance Statistical items.

Example 6. During the terminal PDP activation process, the GGSN performs related performance statistics.

During the PDP activation process of the terminal, the SGSN can know the access attribute of the terminal, and the SGSN needs to transmit the access attribute information of the terminal to the GGSN. The SGSN can use the existing message to transmit the terminal's access attribute information to the GGSN, or use a newly set message to transmit the terminal's access attribute information to the old GGSN. In the following embodiments, the SGSN uses the newly set message header to transmit the access attribute information in detail.

Since the GGSN can know the access attribute of the terminal, the GGSN can distinguish in which type of access system the terminal performs PDP activation, and thus, the GGSN can make statistics on the relevant performance of the terminal's PDP activation process. The relevant performance statistics here can be subdivided into: relevant performance statistical items for PDP activation performed by users accessing through the BSS, and relevant performance statistical items for PDP activation performed by users accessing through the UTRAN.

Example 7. During the terminal PDP activation process, the GGSN performs PDP charging.

During the PDP activation process of the terminal, the SGSN can know the access attribute of the terminal, and the SGSN needs to transmit the access attribute information of the terminal to the GGSN. The SGSN can use the existing message to transmit the terminal's access attribute information to the GGSN, or use a newly set message to transmit the terminal's access attribute information to the old GGSN. In the following embodiments, the SGSN uses the newly set message header to transmit the access attribute information in detail.

Since the GGSN can know the access attributes of the terminal, the GGSN can distinguish which type of access system the terminal is in for PDP activation, so that the GGSN can perform PDP with different rates for different PDP activation processes of the terminal. Billing. That is to say, when GGSN sets the PDP charging rate, it needs to consider the access attribute of the terminal. For example, when a user accesses the 2G system and activates PDP for business, the charging rate is set as the charging rate A , and when the 3G system accesses and activates the PDP for business, the charging rate is set to be the charging rate B. The charging rate A and the charging rate B can be different, so that the GGSN can use different charging rates for different access activation modes for PDP charging.

Example 8: During the terminal PDP activation process, the GGSN controls the terminal's access based on the access control strategy.

During the PDP activation process of the terminal, the SGSN can know the access attribute of the terminal, and the SGSN needs to transmit the access attribute information of the terminal to the GGSN. The SGSN can use the existing message to transmit the terminal's access attribute information to the GGSN, or use a newly set message to transmit the terminal's access attribute information to the old GGSN. In the following embodiments, the SGSN uses the newly set message header to transmit the access attribute information in detail.

Since the GGSN can know the access attributes of the terminal, the GGSN can distinguish which type of access system the terminal is in for PDP activation, so that the GGSN can activate different PDP activation processes for the terminal based on the access control policy control. That is to say, when GGSN sets the access control policy, it needs to consider the access attribute of the terminal. In this way, the GGSN can judge whether to accept the PDP activation of the terminal according to the access attribute of the terminal and the access control policy; if the GGSN configuration allows HPLMN users activate 3G PDP and 2G PDP, that is, users of this PLMN can activate PDP for packet domain data services no matter they access in 3G system or 2G system, but for VPLMN users, only 3G is allowed to be activated. If the VPLMN user accesses from the 3G access network, the user is allowed to activate the PDP for packet domain data services; if the VPLMN user accesses from the 2G access network, the user is not allowed to activate the PDP in the GGSN.

Example 9: During the PDP activation process of the terminal, the GGSN controls the access of the terminal based on the system load threshold.

During the PDP activation process of the terminal, the SGSN can know the access attribute of the terminal, and the SGSN needs to transmit the access attribute information of the terminal to the GGSN. The SGSN can use the existing message to transmit the terminal's access attribute information to the GGSN, or use a newly set message to transmit the terminal's access attribute information to the old GGSN. In the following embodiments, the SGSN uses the newly set message header to transmit the access attribute information in detail.

Since the GGSN can know the access attributes of the terminal, the GGSN can distinguish which type of access system the terminal is in for PDP activation, so that the GGSN can activate and control the different PDP activation processes of the terminal based on the system load threshold , to ensure that when the number of users already connected to the GGSN reaches a certain threshold, certain system resources can be set aside to ensure the PDP activation success rate of certain access type users as much as possible. That is to say, when the GGSN performs activation control, it needs to consider the load of the system and the access type of the user. Operators can configure the load threshold of the GGSN system as required. In this way, the GGSN can judge whether to accept the PDP activation of the terminal according to the access attributes of the terminal, the system load threshold, and the current system load; if the number of activated users on the GGSN has reached 80% of the maximum number of users in the system, in order to ensure more 3G user access, before the system load is reduced to 70%, the GGSN rejects the activation request of the 2G user, but allows the activation of the 3G user.

Example 10: After the terminal PDP is activated, the GGSN uses the terminal's access attribute to schedule the service of the terminal.

When the number of PDP-activated users in the GGSN reaches a certain capacity, the traffic load of the GGSN is close to the maximum throughput of the GGSN. At this time, the GGSN must schedule user data packets according to a certain scheduling strategy to ensure that some PDP-activated user data It can be dispatched with priority, so as to ensure that these users can have better service quality.

At present, the scheduling strategy of most systems is based on priority. For example, PDPs of different Traffic Class types have different scheduling priorities. out of the way to achieve scheduling. If the GGSN can identify the user's access attributes, it can also perform priority scheduling for PDP data flows of the same priority type according to the access attributes; for example, when the GGSN is congested, the operator can configure that for the data flows of the same priority, The business data of the 3G users is dispatched first, so that the users accessing from the 3G and performing packet data services can be provided with better quality of service guarantee.

The method for the SGSN to use the newly set message header to transmit the access attribute information will be described below.

At present, the Gn/Gp interface between SGSN and SGSN, and between SGSN and GGSN uses the GTP protocol. There are two versions of the GTP protocol, GTP V0 and GTP V1. In the following description, GTP V1 is used as an example. of.

The message transmitted on the Gn/Gp interface consists of two parts: the GTP Header (GTP Header) and the GTP Message (GTPMessage). The structure of the GTP Header of the GTP V1 version is shown in Table 1.

Table 1

In Table 1, the position of ( ^* ) is vacant and should be set to zero, and the receiver does not interpret this field; when the S flag is set to "1", the receiver interprets this field; when the PN flag is set to "1", The receiving end interprets this field; when the E flag is set to "1", the receiving end interprets this field. This field shall be present when any one or more of the S, PN, E flags are set to "1".

The 12th byte of the GTP Header is Next Extension Header Type (the next extension header type). When any one or more of E, S, and PN is set to "1", the GTP Header will contain the "Next Extension Header Type" field; if and only when the E flag is set to "1", the NextExtension Header The Type field makes sense.

The structure of the extension header in the message transmitted on the Gn/Gp interface is shown in Table 2.

Table 2

In Table 2, if there are no other extension headers following an extension header, the value of the NextExtension Header Type field in the extension header is set to "0".

The "Next Extension Header Type" field in the extension header message structure is represented by a byte, the 7th and 8th bits of this byte define how the receiving end handles the unrecognized extension header type, the 7th and 8th bits The definition of is shown in Table 3.

table 3

Bits8 7 Meaning 0 0 Comprehension of this extension header is not required. An IntermediateNode shall forward it to any Receiver Endpoint 0 1 Comprehension of this extension header is not required. An IntermediateNode shall discard the Extension Header Content and not forward it to any Receiver Endpoint. Other extension headers shall be treated independently of this extension header. 1 0 Comprehension of this extension header is required by the Endpoint Receiver but not by an Intermediate Node. An Intermediate Node shall forward the whole field to the Endpoint Receiver. 1 1 Comprehension of this header type is required by recipient(either Endpoint Receiver or Intermediate Node)

Currently, in the protocol 3GPP 29060, three extension header types are defined, and these three extension header types are shown in Table 4.

Table 4

Next Extension Header Field Value Type of Extension Header 0000 0000 No more extension headers 1100 0000 PDCP PDU number 1100 0001 Suspend Request 1100 0010 Suspend Response

The present invention adds an extended header type to the extended header of the GTP Head, and the added extended header is used to define the access type of the terminal in the SGSN. After the extension header type is added and set, the extension header types are changed from the original three types to four types, and the four extension header types are shown in Table 5.

table 5

Next Extension Header Field Value Type of Extension Header 0000 0000 No more extension headers 1100 0000 PDCP PDU number 1100 0001 Suspend Request 1100 0010 Suspend Response 1100 0011 Access Mode

In Table 5, the last record is the extended header type defined in the present invention.

The structure of the AccessSS Mode extension header defined by the present invention is shown in Table 6.

Table 6

In Table 6, if there are no other extension headers following the extension header, the value of the NextExtension Header Type field in the extension header is set to "0".

The definition of Access Mode Value and 0xFF of the AccessSS Mode extension header defined in the present invention is as shown in Table 7.

Table 7

Access Mode Value Meaning 0 reserve 1 Access Mode＝GPRS 2 Access Mode = UMTS 3-OxFF reserve

In Table 7, when the Access Mode Value is 1, it means that the terminal is accessed by GPRS; when the Access Mode Value is 2, it means that the terminal is accessed by UMTS.

Between GSNs, such as between SGSNs, between SSGN and GGSN, the access attribute information of the terminal can be transmitted through the access type extension header defined above. The following takes the attachment process, the routing area update process and the PDP activation process as examples for SGSNs. Describe the process of transmitting access attribute information between

1. The terminal transmits the access attribute during the inter-SGSN attachment process.

The terminal attaches to SGSN A, that is, the old SGSN, and then shuts down. Thereafter, the terminal moves to SGSN B, that is, the jurisdiction area of the new SGSN, starts up, and attaches to SGSN B. At this time, the terminal undergoes a cross-SGSN attachment process, and the new SGSN carries the ID in the Identification Request (identity request) message. The Access Mode extension header transmits the access attribute information of the terminal on the new side to the old SGSN, and the old SGSN can also transmit the original access attribute information of the terminal on the old SGSN by carrying the Access Mode extension header in the Identification Response message to the new side SGSN. In this way, both the new-side SGSN and the old-side SGSN can know the access attributes of the terminal in the peer SGSN, so that both the new-side SGSN and the old-side SGSN can realize related performance statistics based on access attributes during cross-SGSN attachment.

2. The terminal transmits the access attribute during the inter-SGSN routing area update process.

During the movement of the terminal, when a cross-SGSN routing area update occurs, the new-side SGSN transmits the access attribute information of the terminal on the new side to the old-side SGSN by carrying the Access Mode extension header in the SGSNContext Request message, and the old-side SGSN passes Carry the Access Mode extension header in the SGSN Context Response message to transmit the terminal's original access attribute information on the old side to the new side SGSN. In this way, both the new-side SGSN and the old-side SGSN can know the access attributes of the terminal in the opposite-end SGSN, so that both the new-side SGSN and the old-side SGSN can realize related performance statistics based on access attributes during the cross-SGSN routing area update process .

3. Transmission of access attributes of the terminal during the PDP activation process.

When the terminal attaches to the SGSN and activates the PDP, the SGSN sends the Create PDPContext Request message to the GGSN with the Access Mode extension header, and transmits the terminal's access attribute information to the GGSN. If the terminal has a cross-SGSN routing area update during the PDP activation process, the new SGSN transmits the access attribute information of the terminal in the new SGSN by carrying the Access Mode extension header in the Update PDP Context Request message sent to the GGSN to GGSN.

In the above-mentioned access attribute transmission process, if one party's GSN does not support the AccessMode extension header defined in the present invention, it will be processed as follows according to the requirements of 3GPP29.060:

a. If the GSN receives an unknown extended header message as a request message, the GSN sends a response message to the opposite end, and the reason value of the response message is "unrecognized mandatory extended header".

b. The initiator of the GTP PDU, that is, the recipient of the Access Mode extension header, sends a "Supported Extension Header Notification" message to inform the peer of the type of extension header it supports.

c. Register in the error log.

After receiving the supported extension header notification message, the GSN that sent the Access Mode extension header removes the extension header that the peer GSN cannot recognize in the GTP message, resends the request message, and the subsequent process continues normally.

Although the present invention has been described by way of example, those of ordinary skill in the art know that there are many variations and changes in the present invention without departing from the spirit of the invention, and the claims of the application document of the present invention include these variations and changes.

Claims (14)

1. a kind of implementation method based on the application of terminal access attribute, it is characterized in that, the different GPRS tunnel protocol control plane GTPC IP address information of the corresponding GPRS service support node SGSN of different access attributes, described method comprises: a. The GPRS service support node SGSN determines the access attribute of the terminal according to the GTPC IP address accessed by the terminal, and transmits the access attribute information of the terminal to the application side; b. The application side realizes the application based on the terminal access attribute according to the received access attribute information. 2. The method according to claim 1, wherein the access attributes include: 2G access, 3G access. 3. The method according to claim 1 or 2, characterized in that, in the step b, the application based on the terminal access attribute is: content charging, or related performance statistics during the terminal attachment process, or terminal routing area Relevant performance statistics during the update process, or relevant performance statistics during the terminal packet data protocol PDP activation process, or PDP charging, or terminal access control, or service scheduling. 4. The method according to claim 3, wherein the application based on the terminal access attribute is: content charging, the application side is: the charging system, and the access attribute information is: the SGSN that the terminal accesses GPRS Tunneling Protocol Control Plane GTPC IP address information, and the different GTPC IP address information of corresponding SGSN of different access attributes; Described step a comprises: The SGSN transmits the GTPC IP address corresponding to the terminal access attribute to the charging system through the GPRS gateway support node GGSN, or through the GGSN and the content charging gateway CCG. 5. The method of claim 4, wherein: When different access networks use different SGSNs, different SGSNs are set with different GTPC IP addresses; When different access networks share the same SGSN, in the SGSN, different access attributes are set with different GTPC IP addresses. 6. The method according to claim 5, wherein, when different access networks share the same SGSN, in step a: The SGSN carries the GTPC IP address corresponding to the terminal access attribute in the create PDP context request message and transmits it to the GGSN; The GGSN obtains the GTPC IP address from the PDP Context Request message; The GGSN carries the GTPC IP address in the Vendor-Specific field of the charging request message and transmits it to the charging system, or transmits it to the CCG, and the CCG transmits it to the charging system. 7. The method according to claim 5, wherein, when different access networks use different SGSNs, in the step a: The GGSN carries the SGSN GTPC IP address corresponding to the terminal access attribute in the Vendor-Specific field of the RADIUS message and transmits it to the CCG, and the CCG transmits it to the billing system. 8. The method of claim 4, further comprising: When the terminal performs inter-system handover and the IP address of the SGSN corresponding to the terminal's access attribute changes, the SGSN notifies the GGSN, or notifies the GGSN and CCG, and updates the location information of the terminal to the HLR. 9. The method according to claim 3, wherein the application side is a GSN, and the step a comprises: The SGSN transmits the terminal access attribute information to the GPRS support node GSN by adding the set GPRS tunnel protocol GTP extension header. 10. The method of claim 9, wherein: When the application side cannot identify the GTP extension header in the message it receives, it transmits the information that does not recognize the extension header and the extension header information it supports to the SGSN; After receiving the information that does not recognize the extension header, the SGSN deletes the extension header that cannot be recognized by the application side according to the supported extension header information, and resends the message. 11. The method according to claim 9, characterized in that, in said step b, relevant performance statistics during the terminal attachment process include one or more of the following: Relevant performance statistics of Inter SGSN 3G to 3G Attach process of Inter SGSN 3G to 3G Attach of new/old side SGSN; Performance statistics of the Inter SGSN 2G to 2G Attach process of the new/old side SGSN; Performance statistics of the Inter SGSN 3G to 2G Attach process of the new/old side SGSN; Performance statistics related to the Inter SGSN 2G to 3G Attach process of the new/old side SGSN. 12. The method according to claim 9, wherein in said step b, the relevant performance statistics in the update process of the terminal routing area include one or more of the following: Inter SGSN 3G to 3G routing area update related performance statistics of Inter SGSN 3G to 3G RAU process of new/old side SGSN; Performance statistics of the Inter SGSN 2G to 2G RAU process of the new/old side SGSN; Performance statistics of the Inter SGSN 3G to 2G RAU process of the new/old side SGSN; Performance statistics of the Inter SGSN 2G to 3G RAU process of the new/old side SGSN. 13. The method according to claim 9, wherein in the step b, the relevant performance statistics during the PDP activation process of the terminal comprises: the GGSN performs relevant performance statistics during the PDP activation process for the terminals accessed through the BSS, And/or the GGSN performs relevant performance statistics during the PDP activation process for the terminals accessed through the UTRAN. 14. The method according to claim 9, wherein in the step b, the terminal access control comprises: GGSN controls the terminal access based on the access control policy and/or the GGSN controls the terminal access based on the system load threshold Control terminal access.

Images