Management method and device of congestion information

[0062] Embodiment one

[0063] Figure 5 It is an interactive schematic diagram of the congestion information management method provided by Embodiment 1 of the present invention. Figure 5 In the shown method, UE1 is initially in a congested area managed by RCAF1, and the context saved by PCRF also indicates that UE1 is in the congested area managed by RCAF1, and then UE1 moves to a congested area managed by RCAF2.

[0064] Step 501. RCAF1 obtains congestion-related OAM information and congested area from RAN OAM. For UTRAN access, RCAF1 also obtains user IDs under the congested area. For E-UTRAN access, RACF1 obtains the user ID in the congested area and the corresponding activated APN (ie, PDN ID) from the MME. For UTRAN access, RCAF1 obtains the APN (ie, PDN identifier) ​​corresponding to the user identifier in the congested area from the SGSN. Assume that UE1 (user ID 1) is located in a congested area, and the activated APN is (PDN ID 1). Here, the congestion area where UE1 is located has changed from congestion level 1 to congestion level 2.

[0065] Step 502 . RCAF1 constructs RUCI according to the information obtained in step 501 . The RUCI of the combination of (user ID 1, PDN ID 1) is (user ID 1, PDN ID 1, congested area ID, congestion level 2, RCAF1 address).

[0066]Step 503. RCAF1 sends the combined RUCI (user ID 1, PDN ID) to the PCRF separately by using the NRR message. If RCAF1 knows the PCRF address corresponding to the combination of (user identity 1, PDN identity 1), RCAF1 can also encapsulate the RUCI of the combination of (user identity 1, PDN identity) and the RUCI of other combinations of the user identity and PDN identity in an ARR message Send to the destination PCRF. The PCRF did not receive the message immediately because the message was delayed;

[0067] Step 504. UE1 moves from the congested area managed by RCAF1 to the congested area managed by RCAF2. RCAF2 obtains the OAM information related to congestion and the congested area from the RAN OAM, and for UTRAN access, RCAF1 also obtains the user ID under the congested area. For E-UTRAN access, RACF2 obtains the user ID in the congested area and the corresponding activated APN (ie, PDN ID) from the MME. For UTRAN access, RCAF2 obtains the APN (ie, PDN identifier) ​​corresponding to the user identifier in the congested area from the SGSN. Since UE1 has moved to a congested area (congestion level is 1), RCAF2 obtains congestion information corresponding to user ID 1, PDN ID 1 and their combination.

[0068] Step 505 . RCAF2 constructs RUCI according to the information obtained in step 504 . The RUCI of the combination of (user ID 1, PDN ID 1) is (user ID 1, PDN ID 1, congested area ID, congestion level 1, RCAF2 address).

[0069] Step 506. Since UE1 has just moved to the area managed by RCAF2, RCAF2 does not know the PCRF address corresponding to the combination of (user ID 1, PDN ID 1), so PCAF2 uses NRR message to send the combination of (user ID 1, PDN ID) to PCRF separately RUCI.

[0070] Step 507.PCRF updates (user ID 1, PDN ID 1) according to the RUCI of step 506 and combines the context saved on the PCRF to update (user ID 1, PDN ID 1, congested area ID, congestion level 1, RCAF2 address). The PCRF returns an acknowledgment message to RCAF2.

[0071] Step 508. PCRF judges that UE1 has moved from RCAF1 to RCAF2, so PCRF sends a MUR message to RCAF1, requesting to delete the context corresponding to (User ID 1, PDN ID 1) saved on RCAF1.

[0072] Step 509: RCAF1 receives the MUR message, and deletes the context corresponding to the combination (user ID 1, PDN ID 1) on RCAF1 according to the message. If PDN identity 1 is the last PDN identity of user identity 1, RCAF1 deletes the entire context of user identity 1.

[0073] Step 510: RCAF1 returns an acknowledgment message MUA to the PCRF.

[0074] Step 511: PCRF receives the NRR/ARR message sent by RCAF1 in step 503 at this time, but PCRF judges that the MUR message has been sent to RCAF1, and deletes the context corresponding to (User ID 1, PDN ID 1), so PCRF responds to RCAF1 The message NRA/ARA carries an indication of rejecting the RUCI report, and may further carry a reason, such as deleting the context or pending transaction (Pending Transaction), and does not update the context saved by the PCRF according to the RUCI report. After receiving the NRA/ARA message, RCAF1 confirms that the RUCI report is invalid and the corresponding context has been deleted.

[0075] According to the above process, PCRF has saved correct congestion information, and RCAF1 has also correctly deleted the context corresponding to the combination of (user ID 1, PDN ID 1).

[0076] Embodiment two

[0077] Image 6 It is an interactive schematic diagram of the congestion information management method provided by Embodiment 2 of the present invention. Image 6 In the method shown, UE1 is initially in a congested area managed by RCAF1, and the context saved by PCRF also indicates that UE1 is in the congested area managed by RCAF1, and then UE1 moves to a congested area managed by RCAF2, and then UE1 moves again Back to the congested area managed by RCAF1.

[0078] Step 601. RCAF1 obtains congestion-related OAM information and congested area from RAN OAM. For UTRAN access, RCAF1 also obtains user IDs under the congested area. For E-UTRAN access, RACF1 obtains the user ID in the congested area and the corresponding activated APN (ie, PDN ID) from the MME. For UTRAN access, RCAF1 obtains the APN (ie, PDN identifier) ​​corresponding to the user identifier in the congested area from the SGSN. Assume that UE1 (user ID 1) is located in a congested area, and the activated APN is (PDN ID 1). Here UE1 is located in the congestion area from congestion level 1 to congestion level 2

[0079] Step 602. RCAF1 constructs RUCI according to the information obtained in step 601. The RUCI of the combination of (user ID 1, PDN ID 1) is (user ID 1, PDN ID 1, congested area ID, congestion level 2, RCAF1 address).

[0080] Step 603. RCAF1 sends the combined RUCI (user ID 1, PDN ID) to the PCRF separately by using the NRR message. If RCAF1 knows the PCRF address corresponding to the combination of (subscriber identification 1, PDN identification 1), then RCAF1 may also encapsulate the RUCI of the combination of (subscriber identification 1, PDN identification) and the RUCI of other user identification and PDN identification combinations in an ARR message to The destination PCRF is sent.

[0081] Step 604. After receiving the RUCI, the PCRF updates the saved context and returns a confirmation message to RCAF1. The combined context of (user ID 1, PDN ID 1) is (user ID 1, PDN ID 1, congested area ID, congestion level 2, RCAF1 address).

[0082] Step 605. UE1 moves from the congested area managed by RCAF1 to the congested area managed by RCAF2. RCAF2 obtains the OAM information related to congestion and the congested area from the RAN OAM. For UTRAN access, RCAF2 also obtains the user ID under the congested area. For E-UTRAN access, RACF2 obtains the user ID in the congested area and the corresponding activated APN (ie, PDN ID) from the MME. For UTRAN access, RCAF2 obtains the APN (ie, PDN identifier) ​​corresponding to the user identifier in the congested area from the SGSN. Since UE1 has moved to a congested area (congestion level is 1), RCAF2 obtains user ID 1, PDN ID 1, and corresponding congestion information.

[0083] Step 606 . RCAF2 constructs RUCI according to the information obtained in step 606 . The RUCI of the combination of (user ID 1, PDN ID 1) is (user ID 1, PDN ID 1, congested area ID, congestion level 1, RCAF2 address).

[0084] Step 607. Since UE1 has just moved to the area managed by RCAF2, RCAF does not know the PCRF address corresponding to the combination of (user ID 1, PDN ID 1), so PCAF1 sends the combination of (user ID 1, PDN ID) to PCRF separately using NRR message RUCI.

[0085] Step 608. The PCRF updates the combined context of (user ID 1, PDN ID 1) according to the RUCI, such as (user ID 1, PDN ID 1, congested area ID, congestion level 1, RCAF2 address). The PCRF returns an acknowledgment message to RCAF2.

[0086] Step 609. PCRF judges that UE1 has moved from RCAF1 to RCAF2, so PCRF sends a MUR message to RCAF1, requesting to delete the context corresponding to (User ID 1, PDN ID 1) stored on RCAF1.

[0087] Step 610. At the same time, when RCAF2 perceives that UE1 has moved to the congested area it manages and reports the RUCI corresponding to the combination of (User ID 1, PDN ID 1), UE1 moves from the congested area managed by RCAF2 to the congested area managed by RCAF1 . RCAF1 obtains the OAM information related to congestion and the congested area from the RAN OAM, and for UTRAN access, RCAF1 also obtains the user ID under the congested area. For E-UTRAN access, RACF1 obtains the user ID in the congested area and the corresponding activated APN (ie, PDN ID) from the MME. For UTRAN access, RCAF1 obtains the APN (ie, PDN identifier) ​​corresponding to the user identifier in the congested area from the SGSN. In addition, the congestion level of congested areas has been changed from 2 to 1;

[0088] Step 611: RCAF1 generates RUCI according to the information in step 610. Wherein, the RUCI corresponding to the combination of (user ID 1, PDN ID 1) is (user ID 1, PDN ID 1, congested area ID, congestion level 1, RCAF1 address);

[0089] Step 612: RCAF1 sends the combined RUCI of (subscriber ID 1, PDN ID 1) to PCRF separately by using the NRR message. If RCAF1 knows the PCRF address corresponding to the combination of (user ID 1, PDN ID 1), RCAF1 can also encapsulate the RUCI of the combination of (user ID 1, PDN ID 1) and the RUCI of other user IDs and PDN ID combinations in an ARR message Send to the destination PCRF.

[0090] Step 613: At this time, RCAF1 receives the MUR message sent in step 609, and RCAF1 deletes the context corresponding to the combination of (user ID 1, PDN ID 1). If PDN identity 1 is the last PDN identity of user identity 1, RCAF1 deletes the entire context of user identity 1.

[0091] Step 614: PCRF receives the NRR/ARR message sent by RCAF1 at this time, but PCRF judges that a MUR message has been sent to RCAF1, and deletes the context corresponding to (User ID 1, PDN ID 1), so PCRF sends the response message NRA to RCAF1 /ARA carries an indication of rejecting the RUCI report, and may further carry the reason, such as deleting the context or pending transaction (PendingTransaction), and not updating the (user ID 1, PDN ID 1) stored by the PCRF according to the RUCI report in step 612. context.

[0092] Step 615: RCAF1 deletes the context corresponding to the combination of (User ID 1, PDN ID 1) on RCAF1 according to the MUR message in Step 609.

[0093] Step 616: After that, UE1 continues to stay in the congested area managed by RCAF1. RCAF1 obtains the OAM information related to congestion and the congested area from the RAN OAM again. For UTRAN access, RCAF1 also obtains the user ID under the congested area. For E-UTRAN access, RACF1 obtains the user ID in the congested area and the corresponding activated APN (ie, PDN ID) from the MME. For UTRAN access, RCAF1 obtains the APN (ie, PDN identifier) ​​corresponding to the user identifier in the congested area from the SGSN. Since UE1 is still in the congested area, RCAF1 obtains user ID 1, PDN ID 1, and congestion information (congestion level is 1) again.

[0094]Step 617: RCAF1 generates RUCI according to the information obtained in step 616 because the original context for the combination of user identity 1 and PDN identity 1 in RCAF1 has been deleted. Wherein, the RUCI corresponding to the combination of (user ID 1, PDN ID 1) is (user ID 1, PDN ID 1, congested area ID, congestion level 1, RCAF1 address);

[0095] Step 618: RCAF1 sends the combined RUCI of (subscriber ID 1, PDN ID 1) to the PCRF separately by using the NRR message. The RUCI of the combination of (user ID 1, PDN ID 1) is (user ID 1, PDN ID 1, congested area ID, congestion level 1, RCAF1 address).

[0096] Step 619: PCRF updates the context according to the RUCI in step 618. The context of the combination of (user ID 1, PDN ID 1) is (user ID 1, PDN ID 1, congested area ID, congestion level 1, RCAF1 address).

[0097] According to the above process, RCAF1 and PCRF finally realize the synchronization of congestion information.

[0098] Embodiment three

[0099] Figure 7 It is a schematic diagram of interaction of the congestion information management method provided by Embodiment 3 of the present invention. Figure 7 In the shown method, UE1 is initially in a congested area managed by RCAF1, and the context saved by PCRF also indicates that UE1 is in the congested area managed by RCAF1, and then UE1 moves to a congested area managed by RCAF2.

[0100] Step 701. RCAF1 obtains congestion-related OAM information and congested area from RAN OAM. For UTRAN access, RCAF1 also obtains user IDs under the congested area. For E-UTRAN access, RACF1 obtains the user ID in the congested area and the corresponding activated APN (ie, PDN ID) from the MME. For UTRAN access, RCAF1 obtains the APN (ie, PDN identifier) ​​corresponding to the user identifier in the congested area from the SGSN. Assume that UE1 (user ID 1) is located in a congested area, and the activated APN is (PDN ID 1). Here UE1 is located in the congestion area from congestion level 1 to congestion level 2

[0101] Step 702. RCAF1 constructs RUCI according to the information obtained in step 701. The RUCI of the combination of (user ID 1, PDN ID 1) is (user ID 1, PDN ID 1, congested area ID, congestion level 2, RCAF1 address).

[0102] Step 703. RCAF1 sends the combined RUCI (user ID 1, PDN ID) to the PCRF separately by using the NRR message. If RCAF1 knows the PCRF address corresponding to the combination of (user identity 1, PDN identity 1), RCAF1 can also encapsulate the RUCI of the combination of (user identity 1, PDN identity) and the RUCI of other combinations of the user identity and PDN identity in an ARR message Send to the destination PCRF. The PCRF did not receive the message immediately because the message was delayed;

[0103] Step 704. UE1 moves from the congested area managed by RCAF1 to the congested area managed by RCAF2. RCAF2 obtains the OAM information related to congestion and the congested area from the RAN OAM, and for UTRAN access, RCAF1 also obtains the user ID under the congested area. For E-UTRAN access, RACF2 obtains the user ID in the congested area and the corresponding activated APN (ie, PDN ID) from the MME. For UTRAN access, RCAF2 obtains the APN (ie, PDN identifier) ​​corresponding to the user identifier in the congested area from the SGSN. Since UE1 has moved to a congested area (congestion level is 1), RCAF2 obtains congestion information corresponding to user ID 1, PDN ID 1 and their combination.

[0104] Step 705 . RCAF2 constructs RUCI according to the information obtained in step 704 . The RUCI of the combination of (user ID 1, PDN ID 1) is (user ID 1, PDN ID 1, congested area ID, congestion level 1, RCAF2 address).

[0105] Step 706. Since UE1 has just moved to the area managed by RCAF2, RCAF2 does not know the PCRF address corresponding to the combination of (user ID 1, PDN ID 1), so PCAF2 uses NRR message to send the combination of (user ID 1, PDN ID) to PCRF separately RUCI.

[0106] Step 707.PCRF is updated according to the RUCI of step 707 (subscriber identification 1, PDN identification 1) combination saves the context on PCRF, is updated as (subscriber identification 1, PDN identification 1, congested area identification, congestion level 1, RCAF2 address). The PCRF returns an acknowledgment message to RCAF2.

[0107] Step 708. PCRF judges that UE1 has moved from RCAF1 to RCAF2, so PCRF sends a MUR message to RCAF1, requesting to delete the context corresponding to (User ID 1, PDN ID 1) saved on RCAF1.

[0108] Step 709: RCAF1 receives the MUR message, but RCAF1 judges that the RUCI of (User ID 1, PDN ID 1) has been reported to the PCRF, and has not received a response message, so it combines (User ID 1, PDN ID 1) with the corresponding The context is marked as undecided.

[0109] Step 710: RCAF1 returns an acknowledgment message MUA to the PCRF.

[0110] Step 711: PCRF receives the NRR/ARR message sent by RCAF1 in step 703 at this time, but PCRF judges that the MUR message has been sent to RCAF1, and deletes the context corresponding to (User ID 1, PDN ID 1), so PCRF responds to RCAF1 The message NRA/ARA carries an indication of rejecting the RUCI report, and may further carry a reason, such as deleting the context or pending transaction (Pending Transaction), and does not update the context saved by the PCRF according to the RUCI report. After receiving the NRA/ARA message, RCAF1 confirms that the RUCI report is invalid.

[0111] It should be pointed out that in some cases RCAF1 receives the message in step 708 first, and then receives the message in step 711, so RCAF has already reported the RUCI of (user ID 1, PDN ID 1) to PCRF after receiving the MUR message , and no response message is received, it is judged that the context corresponding to the (subscriber ID 1, PDN ID 1) combination needs to be marked as undecided; in some cases, RCAF1 first receives the message in step 711, and then receives the message in step 706 message, the RCAF can judge that the context corresponding to the combination (user ID 1, PDN ID 1) needs to be marked as undecided according to the rejected indication carried.

[0112] Step 712: In the next period, RCAF1 obtains the congestion-related OAM information and the congested area from the RAN OAM again. For UTRAN access, RCAF1 also obtains the user ID under the congested area. For E-UTRAN access, RACF1 obtains the user ID in the congested area and the corresponding activated APN (ie, PDN ID) from the MME. For UTRAN access, RCAF1 obtains the APN (ie, PDN identifier) ​​corresponding to the user identifier in the congested area from the SGSN. Since UE1 has left the congested area, RCAF1 does not obtain user ID 1 and PDN ID 1 again, as well as congestion information (congestion level is 1).

[0113] Step 713: Because the context of (User ID 1, PDN ID 1) is undecided and RCAF1 does not detect that UE1 is located in the congested area it manages, RCAF1 deletes its corresponding context.