WO2016119439A1 - 一种拥塞信息的管理方法、装置和系统 - Google Patents

一种拥塞信息的管理方法、装置和系统 Download PDF

Info

Publication number
WO2016119439A1
WO2016119439A1 PCT/CN2015/087045 CN2015087045W WO2016119439A1 WO 2016119439 A1 WO2016119439 A1 WO 2016119439A1 CN 2015087045 W CN2015087045 W CN 2015087045W WO 2016119439 A1 WO2016119439 A1 WO 2016119439A1
Authority
WO
WIPO (PCT)
Prior art keywords
pcrf
identifier
pdn
message
user
Prior art date
Application number
PCT/CN2015/087045
Other languages
English (en)
French (fr)
Inventor
周晓云
卢飞
吴锦花
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016119439A1 publication Critical patent/WO2016119439A1/zh

Links

Images

Definitions

  • Embodiments of the present invention relate to, but are not limited to, the field of communications, and in particular, to a method, an apparatus, and a system for managing congestion information.
  • FIG. 1 is a schematic diagram of a Policy and Charging Control (PCC) defined by a 3rd Generation Partnership Project (3GPP) in the related art, as shown in FIG.
  • the Policy and Charging Rules Function (PCRF) is the core of the entire PCC architecture.
  • the PCRF needs to combine the service information received from the Application Function (AF), the user subscription information received from the Subscription Profile Repository (SPR), and the policy configured by the operator.
  • the PCRF sends the control policy for the service to the Policy and Charging Enforcement Function (PCEF) or the Bearer Binding and Event Report Function (BBERF).
  • PCEF Policy and Charging Enforcement Function
  • BBERF Bearer Binding and Event Report Function
  • the PCRF can subscribe to the bearer layer related events to the PCEF and/or the BBERF to sense in time when the bearer layer occurs, and change the control strategy.
  • the PCEF can also support application detection control functions.
  • the PCEF can perform application detection and perform policy enforcement (such as gating, redirection, and bandwidth limitation) according to the local configuration or the PCC rule that is sent by the PCRF and includes the application identifier.
  • the PCEF is typically located on the gateway of the network, such as the Packet Data Network Gateway (PDN-GW) of the EPS.
  • the network can implement application detection control by deploying a separate traffic detection function (Traffic Detection Function, TDF for short).
  • TDF Traffic Detection Function
  • the TDF and the PCRF are connected through the Sd interface.
  • the TDF can perform application detection and policy execution according to the application detection and control (ADC) rules that are pre-configured or sent by the PCRF.
  • ADC application detection and control
  • the RAN Congestion Awareness Function uses the Np interface to encapsulate the user plane congestion information of the radio access network (RAN User Plane Congestion). Information, referred to as RUCI, is reported to the PCRF for PCRF to make policy decisions to mitigate network load.
  • the RCAF collects user plane congestion information from the RAN Operation Administration Maintenance (OAM) system.
  • OAM Operation Administration Maintenance
  • the RCAF obtains the Evolved NodeB (Evolved NodeB) from the MME (Mobility Management Entity) through the Nq interface.
  • the RCAF can directly obtain the IMSI list under the Node B (CB)/Cell Global Identifier (CGI) from the RAN. And the IMSI list for each activated APN is obtained through Nq'. In this way, the RCAF can obtain an IMSI list for each active APN under each congested base station (eNB/NB)/cell (ECGI/CGI). The RCAF reports this information to the correct PCRF, and the PCRF can adjust these UE policies to reduce the load on the congested base station or cell.
  • CB Node B
  • CGI Cell Global Identifier
  • each RCAF is responsible for managing one network area (eg, one cell list or base station list for each RCAF).
  • network area eg, one cell list or base station list for each RCAF.
  • management range in which the UE moves from one RCAF management range to another RCAF when the movement occurs.
  • the messages received and sent by the PCRF are in the order of steps.
  • the messages sent and received by RCAF1, RCAF2, and PCRF may be out of order due to delay, and thus message contention may occur.
  • the Race Condition occurs.
  • UE1 In the case of message contention, UE1 is initially in a congested area managed by RCAF1, and the context saved by the PCRF also indicates that UE1 is under the congestion area managed by RCAF1, and then UE1 moves and moves to the congested area managed by RCAF2. In practical applications, the following will occur:
  • the PCRF judges that UE1 has moved from RCAF1 to RCAF2, so the PCRF sends a Modify User Context Request (MUR) message to RCAF1 requesting deletion of the following (user ID 1, PDN ID 1) combination.
  • MUR Modify User Context Request
  • the PCRF After the PCRF sends the MUR message, the PCRF receives the Aggregated RUCI Report Request (ARR) message sent by the RCAF1. And RCAF1 is receiving the poly The MUR message is also received before the message of the Aggregated RUCI Report Answer (ARA), and the two messages are conflicting in content.
  • the PCRF may judge that the UE1 moves back to the RCAF2 managed area and then returns to the RCAF1.
  • the PCRF updates the context saved by the PCRF according to the RUCI reported by RCAF1.
  • RCAF1 decides to delete the context of the combination of (User ID 1, PDN1 ID 1) according to the MUR.
  • the embodiment of the invention provides a method, a device and a system for managing congestion information, so as to ensure correct management of congestion information by the RCAF.
  • the embodiment of the invention provides a method for managing congestion information, including:
  • the radio access network congestion sensing function RCAF receives the modified user context request MUR message sent by the policy and charging rule function PCRF, wherein the MUR message includes request information for requesting deletion of the user identifier and the packet data network PDN identifier;
  • the RCAF rejects the MUR message.
  • the method further includes: the RCAF returns a response message of the MUR message to the PCRF, where the response message of the MUR message carries indication information rejecting the MUR message and/or a reason for rejecting the MUR message.
  • the reason for the rejection is that the reported or undetermined transaction of the radio access network user plane congestion information RUCI report is being performed.
  • the method further includes: the context of the RCAF marking the user identifier and the PDN identifier is an undetermined state.
  • the method further includes: if the RCAF subsequently receives the user identifier and the PDN The RCAF sends a new RUCI report of the user identifier and the PDN identifier to the PCRF; if not received, the RCAF deletes the context of the user identifier and the PDN identifier saved by the RCAF .
  • the method further includes: after receiving the RUCI report, the PCRF updates the saved context of the user identifier and the PDN identifier according to the RUCI report.
  • the method further includes: if the PCRF does not receive the response message of the MUR message or receives a response message rejecting the MUR message when the PCRF receives the report of the RUCI, The PCRF rejects the RUCI report.
  • the embodiment of the present invention further provides a management system for congestion information, including a radio access network congestion sensing function RCAF receiving policy and a charging rule function PCRF, where:
  • the RCAF includes:
  • a first receiving module configured to receive a modified user context request MUR message sent by the PCRF, where the MUR message includes request information for requesting deletion of the user identifier and the packet data network PDN identifier;
  • the first management module is configured to reject the MUR message if the response message sent by the PCRF and the radio access network user plane congestion information RUCI report corresponding to the PDN identifier is not received;
  • the PCRF includes: a first sending module, configured to send a MUR message to the RCAF.
  • the RCAF further includes: a second sending module, configured to return a response message of the MUR message to the PCRF, where the response message of the MUR message carries indication information that rejects the MUR message and/or the reject MUR The reason for the message.
  • a second sending module configured to return a response message of the MUR message to the PCRF, where the response message of the MUR message carries indication information that rejects the MUR message and/or the reject MUR The reason for the message.
  • the reason for the rejection is that the reported or undetermined transaction of the radio access network user plane congestion information RUCI report is being performed.
  • the RCAF further includes: a first marking module, configured to mark the context of the user identifier and the PDN identifier as an undetermined state.
  • the RCAF further includes: a second management module, configured to send the user identifier and the PDN to the PCRF if the congestion information of the user identifier and the PDN identifier is subsequently received The identified new RUCI report; if not received, deletes the context of the combination of the user identity and the PDN identity saved by the RCAF.
  • a second management module configured to send the user identifier and the PDN to the PCRF if the congestion information of the user identifier and the PDN identifier is subsequently received The identified new RUCI report; if not received, deletes the context of the combination of the user identity and the PDN identity saved by the RCAF.
  • the PCRF further includes: an update module, configured to: after receiving the RUCI report, update the saved context of the combination of the user identifier and the PDN identifier according to the RUCI report.
  • an update module configured to: after receiving the RUCI report, update the saved context of the combination of the user identifier and the PDN identifier according to the RUCI report.
  • the PCRF further includes: a third management module, configured to: when receiving the RUCI report, rejecting the response message of the MUR message or receiving a response message rejecting the MUR message, rejecting The RUCI report.
  • a third management module configured to: when receiving the RUCI report, rejecting the response message of the MUR message or receiving a response message rejecting the MUR message, rejecting The RUCI report.
  • the embodiment of the invention further provides a device for managing congestion information, including:
  • a first receiving module configured to receive a modified user context request MUR message sent by a policy and charging rule function PCRF, where the MUR message includes request information for requesting deletion of a user identifier and a packet data network PDN identifier;
  • the second management module is configured to reject the MUR message if the response message sent by the PCRF and the radio access network user plane congestion information RUCI report corresponding to the PDN identifier is not received.
  • the device further includes: a third sending module, configured to return a response message of the MUR message to the PCRF, where the response message of the MUR message carries indication information that rejects the MUR message and/or the reject MUR The reason for the message.
  • a third sending module configured to return a response message of the MUR message to the PCRF, where the response message of the MUR message carries indication information that rejects the MUR message and/or the reject MUR The reason for the message.
  • the reason for the rejection is that the reported or undetermined transaction of the radio access network user plane congestion information RUCI report is being performed.
  • the apparatus further includes: a first marking module, configured to mark the context of the user identifier and the PDN identifier as an undetermined state.
  • a first marking module configured to mark the context of the user identifier and the PDN identifier as an undetermined state.
  • the device further includes: a second management module, configured to send a new RUCI report of the user identifier and the PDN identifier to the PCRF if the congestion information of the user identifier and the PDN identifier is subsequently received If not received, delete the context of the user identifier and the PDN identifier saved by the RCAF.
  • a second management module configured to send a new RUCI report of the user identifier and the PDN identifier to the PCRF if the congestion information of the user identifier and the PDN identifier is subsequently received If not received, delete the context of the user identifier and the PDN identifier saved by the RCAF.
  • the embodiment of the invention further provides a computer readable storage medium storing program instructions, which can be implemented when the program instructions are executed.
  • the RCAF when the PCRF interacts with the RCAF, after receiving the MUR report requesting to delete the combination of the user identifier and the PDN identifier, if the RCAF determines that the user identifier and the PDN identifier have been reported to the PCRF, If the corresponding RUCI report does not receive the response message, the RCAF rejects the MUR message from the PCRF, ensures that the correct context is saved locally, and reduces the occurrence of the misjudgment operation.
  • FIG. 1 is a schematic diagram of a policy and charging control architecture defined by a third generation partnership program in the related art
  • FIG. 2 is a schematic diagram of an architecture of a PCRF for sensing load information of a radio access network in the related art
  • FIG. 3 is a schematic flowchart diagram of an embodiment of a method for managing congestion information according to Embodiment 1 of the present invention
  • FIG. 4 is a schematic diagram of interaction of a method for managing congestion information according to application example 1 of the present invention.
  • FIG. 5 is a schematic diagram of interaction of a method for managing congestion information according to application example 2 of the present invention.
  • FIG. 6 is a schematic diagram of interaction of a method for managing congestion information provided by application example 3 of the present invention.
  • FIG. 7 is a schematic diagram of interaction of a method for managing congestion information according to application example 4 of the present invention.
  • FIG. 8 is a schematic structural diagram of an embodiment of a system for managing congestion information according to Embodiment 2 of the present invention.
  • FIG. 9 is a schematic structural diagram of an embodiment of a device for managing congestion information according to Embodiment 3 of the present invention.
  • FIG. 3 is a schematic flowchart of a method for managing congestion information according to Embodiment 1 of the present invention; Figure. As shown in Figure 3, it includes:
  • Step 301 The RCAF receives the MUR message sent by the PCRF, where the MUR message includes request information for requesting deletion of the user identifier and the packet data network identifier.
  • Step 302 If the RCAF does not receive the response message of the RUCI report corresponding to the user identifier and the packet data network identifier, the RCAF rejects the MUR message.
  • the method further includes: the RCAF returns a response message of the MUR message to the PCRF, where the response message of the MUR message carries indication information rejecting the MUR message and/or a reason for rejecting the MUR message.
  • the reason for the rejection is that the reported or undetermined transaction of the RUCI report is being executed.
  • the method further includes: the context of the RCAF marking the user identifier and the PDN identifier is an undetermined state.
  • the method further includes: if the RCAF receives the congestion information of the user identifier and the PDN identifier in a subsequent (ie, within a preset time period), the RCAF sends the user identifier to the PCRF. A new RUCI report identified by the PDN; if not received, the RCAF deletes the context of the user identity and PDN identity saved by the RCAF.
  • the method further includes: after receiving the RUCI report, the PCRF updates the saved context of the user identifier and the PDN identifier according to the RUCI report.
  • the method further includes: if the PCRF does not receive the response message of the MUR message or receives a response message rejecting the MUR message when the PCRF receives the report of the RUCI, The PCRF rejects the RUCI report.
  • the RCAF when the PCRF interacts with the RCAF, after receiving the MUR report requesting to delete the combination of the user identifier and the PDN identifier, if the RCAF determines that the user identifier and the PDN identifier have been reported to the PCRF, If the corresponding RUCI report does not receive the response message, the RCAF rejects the MUR message from the PCRF, ensures that the correct context is saved locally, and reduces the occurrence of the misjudgment operation.
  • FIG. 4 is a schematic diagram of interaction of a method for managing congestion information according to an application example 1 of the present invention.
  • UE1 is initially in a congested area managed by RCAF1, and the context saved by the PCRF also indicates that UE1 is under the congested area managed by RCAF1.
  • the RCAF1 acquires the congestion-related OAM information and the congestion area from the RAN OAM.
  • the RCAF1 also acquires the user identifier in the congestion area.
  • the RACF1 acquires the user in the congestion area from the MME.
  • the corresponding activated APN ie, the PDN identifier
  • the RCAF1 obtains the APN (ie, the PDN identifier) corresponding to the user identifier in the congestion area from the SGSN, and assumes that the UE1 (the user identifier 1) is located in the congestion area, and is activated.
  • the APN is (PDN identifier 1); here the congestion area where UE1 is located from congestion level 1 to congestion level 2;
  • Step 402. The RCAF1 constructs the RUCI according to the information obtained in the step 401; wherein the RUCI of the combination of the user identifier 1, the PDN identifier 1 is (user identifier 1, PDN identifier 1, congestion area identifier, congestion level 2, RCAF1 address);
  • the RCAF1 uses the NRR (Non-Aggregated RUCI Report) message to separately send the RUCI (User ID 1, PDN ID) combination to the PCRF; if the RCAF1 learns (User ID 1, PDN ID 1) the PCRF address corresponding to the combination, the RCAF1 also
  • the RUCI combined with (user ID 1, PDN identifier) and other RUCIs combined with the user identifier and PDN identifier may be encapsulated in an ARR (Aggregated RUCI Report) message and sent to the destination PCRF; since the message is delayed, the PCRF does not immediately receive To the message;
  • Step 404 The UE1 moves the congestion area managed by the RCAF1 to the congestion area managed by the RCAF2; the RCAF2 acquires the congestion-related OAM information and the congestion area from the RAN OAM, and the RCAF1 also acquires the user identifier in the congestion area for the UTRAN access; - UTRAN access, the RACF 2 obtains the user identity and the corresponding activated APN (ie, the PDN identity) in the congestion zone from the MME.
  • the RCAF2 acquires the congestion-related OAM information and the congestion area from the RAN OAM
  • the RCAF1 also acquires the user identifier in the congestion area for the UTRAN access
  • the RACF 2 obtains the user identity and the corresponding activated APN (ie, the PDN identity) in the congestion zone from the MME.
  • the RCAF2 obtains the APN corresponding to the user identity in the congestion zone from the SGSN (ie, the PDN identity) ); since UE1 moves to a congested area (congestion level is 1), RCAF2 obtains congestion information corresponding to user ID 1, PDN ID 1, and its combination;
  • Step 405. The RCAF2 constructs the RUCI according to the information obtained in step 404; wherein the RUCI of the combination of (user identifier 1, PDN identifier 1) is (user identifier 1, PDN identifier 1, congestion area identifier, congestion level 1, RCAF2 address);
  • Step 406 Since UE1 has just moved to the area managed by RCAF2, RCAF2 does not know (use User ID 1, PDN ID 1) Combine the corresponding PCRF address, so PCAF2 uses the NRR message to separately send the RUCI (User ID 1, PDN ID) combination to the PCRF;
  • Step 407 The PCRF combines the context saved on the PCRF according to the RUCI update (user identifier 1, PDN identifier 1) of step 406, and updates to (user identifier 1, PDN identifier 1, congestion area identifier, congestion level 1, RCAF2 address); The PCRF returns a confirmation message to RCAF2;
  • Step 408 The PCRF determines that the UE1 has moved from the RCAF1 to the RCAF2, so the PCRF sends a MUR message to the RCAF1 requesting to delete the following corresponding to the (User ID1, PDN ID1) saved on the RCAF1;
  • Step 409 At this time, the PCRF receives the RUCI report of step 403, and the context that the PCRF saves according to the new RUCI update is (user identifier 1, PDN identifier 1, congestion area identifier, congestion level 1, RCAF2 address);
  • Step 410 The RCAF1 receives the MUR message, and determines that the RUCI corresponding to the (User ID 1, PDN ID 1) has been reported to the PCRF and the response message is not received. Therefore, the RCAF1 carries the reject indication to the response message MUA returned by the PCRF. Carrying reasons, such as performing RUCI reporting or pending transactions (Pending Transaction); therefore RCAF1 does not perform delete context operations according to MUR;
  • Step 411 The PCRF returns an acknowledgement message to the RCAF1.
  • Step 412 Since the PCRF determines that the UE has moved from RCAF2 to RCAF1, the PCRF sends a MUR message to RCAF2 requesting deletion of the context corresponding to (user identifier 1, PDN identifier 1);
  • Step 413 RCAF2 deletes the context corresponding to the user identifier 1, the PDN identifier 1; if the PDN identifier 1 is the last PDN identifier of the user identifier 1, the RCAF2 deletes the context of the entire user identifier 1;
  • Step 414 Thereafter, the UE1 continues to stay in the congestion area managed by the RCAF2; the RCAF2 acquires the congestion-related OAM information and the congestion area from the RAN OAM again, and for the UTRAN access, the RCAF2 also acquires the user identity in the congestion area; for the E-UTRAN Accessing, the RACF 2 obtains the user identifier and the corresponding activated APN (ie, the PDN identifier) in the congestion area from the MME. For the UTRAN access, the RCAF1 obtains the APN corresponding to the user identifier in the congestion area from the SGSN. (ie, PDN identification); since UE1 is still in the congested area, RCAF2 obtains User ID 1 and PDN ID 1 again, and congestion information (congestion level is 1);
  • Step 415 Since the context originally for the UE in the RCAF2 has been deleted, the RCAF2 generates a new RUCI according to the information obtained in step 414; wherein, the (the user identifier 1, the PDN identifier 1) combination corresponds to the RUCI (user identifier 1, PDN) Identification 1, congestion area identification, congestion level 1, RCAF2 address);
  • Step 416 The RCAF2 sends the RUCI of the combination of the user identifier 1 and the PDN identifier 1 to the PCRF by using the NRR message.
  • the RUCI of the combination of the user identifier 1 and the PDN identifier 1 is the user identifier 1, the PDN identifier 1, and the congestion area identifier. , congestion level 1, RCAF2 address);
  • Step 417 The PCRF updates the context according to the latest RUCI report; wherein the context of the combination of (User Identity 1, PDN Identity 1) is (User Identity 1, PDN Identity 1, Congestion Region Identity, Congestion Level 1, RCAF2 Address).
  • FIG. 5 is a schematic diagram of interaction of a method for managing congestion information according to application example 2 of the present invention.
  • UE1 is initially under one congestion area managed by RCAF1
  • the context saved by the PCRF also indicates that UE1 is under the congestion area managed by RCAF1.
  • the RCAF1 obtains the congestion-related OAM information and the congestion area from the RAN OAM.
  • the RCAF1 also acquires the user identifier in the congestion area.
  • the RACF1 obtains the user in the congestion area from the MME.
  • the corresponding activated APN ie, the PDN identifier
  • the RCAF1 obtains the APN (ie, the PDN identifier) corresponding to the user identifier in the congestion area from the SGSN, and assumes that the UE1 (the user identifier 1) is located in the congestion area, and is activated.
  • the APN is (PDN identifier 1); here the congestion area where UE1 is located from congestion level 1 to congestion level 2;
  • Step 502. The RCAF1 constructs the RUCI according to the information obtained in step 501; wherein the RUCI of the combination of the user identifier 1, the PDN identifier 1 is (user identifier 1, PDN identifier 1, congestion area identifier, congestion level 2, RCAF1 address);
  • RCAF1 is separately sent to the PCRF by using an NRR message (User ID 1, PDN) Identifying the combined RUCI; if RCAF1 knows (user ID 1, PDN ID 1) that the corresponding PCRF address is combined, RCAF1 may also combine the RUCI (user ID 1, PDN identifier) combination with other user IDs and PDN identifiers.
  • the RUCI is encapsulated in an ARR message and sent to the destination PCRF; since the message is delayed, the PCRF does not immediately receive the message;
  • Step 504. The UE1 moves from the congestion area managed by the RCAF1 to the congestion area managed by the RCAF2; the RCAF2 acquires the congestion-related OAM information and the congestion area from the RAN OAM, and the RCAF1 also acquires the user identifier in the congestion area for the UTRAN access; - UTRAN access, the RACF 2 obtains the user identity and the corresponding activated APN (ie, the PDN identity) in the congestion zone from the MME.
  • the RCAF2 acquires the congestion-related OAM information and the congestion area from the RAN OAM
  • the RCAF1 also acquires the user identifier in the congestion area for the UTRAN access
  • the RACF 2 obtains the user identity and the corresponding activated APN (ie, the PDN identity) in the congestion zone from the MME.
  • the RCAF2 obtains the APN corresponding to the user identity in the congestion zone from the SGSN (ie, the PDN identity) ); since UE1 moves to a congested area (congestion level is 1), RCAF2 obtains congestion information corresponding to user ID 1, PDN ID 1, and its combination;
  • Step 505. The RCAF2 constructs the RUCI according to the information obtained in the step 404; wherein the RUCI of the combination of the (User ID 1, PDN ID 1) is (User ID 1, PDN ID 1, Congestion Area Identity, Congestion Level 1, RCAF2 Address);
  • Step 506 Since the UE1 has just moved to the area managed by the RCAF2, the RCAF2 does not know (the user identifier 1, the PDN identifier 1) combines the corresponding PCRF address, so the PCAF2 sends the (User ID 1, PDN ID) combination to the PCRF by using the NRR message. RUCI;
  • Step 507. The PCRF combines the context saved on the PCRF according to the RUCI update (user identifier 1, PDN identifier 1) of step 506, and updates to (user identifier 1, PDN identifier 1, congestion area identifier, congestion level 1, RCAF2 address); The PCRF returns a confirmation message to RCAF2;
  • Step 508 The PCRF determines that the UE1 has moved from the RCAF1 to the RCAF2, so the PCRF sends a MUR message to the RCAF1 requesting to delete the following corresponding to the (User ID1, PDN ID1) saved on the RCAF1;
  • Step 509 The RCAF1 receives the MUR message, and determines that the RUCI corresponding to the (User ID 1, PDN ID 1) has been reported to the PCRF and the response message is not received, and the RCAF1 marks the corresponding context as an undetermined state.
  • Step 510 The response message returned by the RCAF1 to the PCRF carries a rejection indication, and may also carry a reason, such as performing a RUCI report or a pending transaction (Pending Transaction);
  • Step 511 The PCRF receives the RUCI report of step 503, and the PCRF determines that the MUR message requesting deletion (user identifier 1, PDN identifier 1) combined context has been sent to RCAF1, but the response message has not been received yet, so the PCRF is not based on the new one.
  • the MUR message requesting deletion user identifier 1, PDN identifier 1
  • the RUCI updates the saved context; the PCRF returns a message to the RCAF1, the message carries a rejection indication, and may carry the reason, such as performing a RUCI report or a pending transaction (Pending Transaction); or, when the PCRF receives the RUCI, if before the PCRF Upon receiving the MUA message carrying the rejection indication, the PCRF may also decide to reject the RUCI report and not update the context, and return a response message carrying the rejection indication to the RCAF;
  • Step 512 In the next cycle, the RCAF1 acquires the congestion-related OAM information and the congestion area from the RAN OAM again.
  • the RCAF1 also acquires the user identity in the congestion area; for the E-UTRAN access, the RACF1 acquires from the MME.
  • the RCAF1 obtains the APN corresponding to the user identifier in the congestion area (that is, the PDN identifier) from the SGSN; since the UE1 has left the congestion area, the UE1 has left the congestion area.
  • RCAF1 does not obtain User ID 1 and PDN ID 1, and congestion information again;
  • Step 513 Because the context of (User Identity 1, PDN Identity 1) is in an undetermined state, and RCAF1 does not detect that UE1 is located in its managed congestion area, RCAF1 deletes its corresponding context.
  • FIG. 6 is a schematic diagram of interaction of a method for managing congestion information provided by application example 3 of the present invention.
  • UE1 is initially in a congestion area managed by RCAF1, and the context saved by the PCRF also indicates that UE1 is under the congestion area managed by RCAF1, and then UE1 moves, moves to the congestion area managed by RCAF2, and then UE1 It moves back to the scene of the congestion area managed by RCAF1.
  • the RCAF1 acquires the congestion-related OAM information and the congestion area from the RAN OAM.
  • the RCAF1 also acquires the user identifier in the congestion area.
  • the RACF1 acquires the user in the congestion area from the MME.
  • the corresponding activated APN ie, the PDN identifier
  • the RCAF1 obtains the APN (ie, the PDN identifier) corresponding to the user identifier in the congestion area from the SGSN;
  • the activated APN is (PDN identifier 1); where the congestion area where UE1 is located is from congestion level 1 to congestion level 2;
  • Step 602. The RCAF1 constructs the RUCI according to the information obtained in step 501; wherein the RUCI of the combination of the user identifier 1, the PDN identifier 1 is (user identifier 1, PDN identifier 1, congestion area identifier, congestion level 2, RCAF1 address);
  • Step 603. The RCAF1 separately sends the RUCI (the user identifier 1 and the PDN identifier) combination to the PCRF by using the NRR message; if the RCAF1 learns (the user identifier 1 and the PDN identifier 1) the PCRF address corresponding to the combination, the RCAF1 may also (the user identifier 1) And the RUCI of the combined combination of the RUCI and the other user identifiers and the PDN identifiers are sent in an ARR message to the destination PCRF;
  • Step 604. After receiving the RUCI, the PCRF updates the saved context and returns an acknowledgement message to the RCAF1; (the user identifier 1, the PDN identifier 1) the combined context is (user identifier 1, PDN identifier 1, congestion area identifier, congestion level 2) , RCAF1 address);
  • Step 605. The UE1 moves from the congestion area managed by the RCAF1 to the congestion area managed by the RCAF2; the RCAF2 acquires the congestion-related OAM information and the congestion area from the RAN OAM, and the RCAF2 also acquires the user identifier in the congestion area for the UTRAN access; - UTRAN access, the RACF 2 obtains the user identity and the corresponding activated APN (ie, the PDN identity) in the congestion zone from the MME.
  • the RCAF2 acquires the congestion-related OAM information and the congestion area from the RAN OAM
  • the RCAF2 also acquires the user identifier in the congestion area for the UTRAN access
  • the RACF 2 obtains the user identity and the corresponding activated APN (ie, the PDN identity) in the congestion zone from the MME.
  • the RCAF2 obtains the APN corresponding to the user identity in the congestion zone from the SGSN (ie, the PDN identity) ); since UE1 moves to a congested area (congestion level is 1), RCAF2 obtains user ID 1 and PDN ID 1, and corresponding congestion information;
  • Step 606 The RCAF2 constructs the RUCI according to the information obtained in the step 605; wherein the RUCI combined by the (user identifier 1, the PDN identifier 1) is (user identifier 1, PDN identifier 1, congestion area identifier, congestion level 1, RCAF2 address);
  • the PCRF is based on the context of the combination of the RUCI update (user identity 1, PDN identity 1), such as (user identity 1, PDN identity 1, congestion zone identity, congestion level 1, RCAF2). Address); PCRF returns a confirmation message to RCAF2;
  • Step 609 The PCRF determines that the UE1 has moved from the RCAF1 to the RCAF2, so the PCRF sends a MUR message to the RCAF1 requesting to delete the context corresponding to the (User ID1, PDN ID1) stored in the RCAF1;
  • Step 610 At the same time, after the RCAF2 senses that the UE1 moves to its managed congestion area and reports the RUCI corresponding to the combination of (User ID 1, PDN ID 1), the UE1 moves from the congestion area managed by the RCAF2 to the congestion area managed by the RCAF1.
  • RCAF1 acquires congestion-related OAM information and congestion area from RAN OAM.
  • RAN OAM For UTRAN access, RCAF1 also obtains the user identity under the congestion area; for E-UTRAN access, RACF1 obtains the user identity under the congestion area from the MME.
  • Corresponding activated APN ie, PDN identifier
  • RCAF1 obtains the APN (ie, PDN identifier) corresponding to the user identifier in the congestion area from the SGSN; in addition, the congestion level of the congestion area changes from 2 to 1;
  • Step 611 The RCAF1 generates the RUCI according to the information of the step 610; wherein, the (the user identifier 1, the PDN identifier 1) combination corresponding to the RUCI is (user identifier 1, PDN identifier 1, congestion area identifier, congestion level 1, RCAF1 address);
  • Step 612 RCAF1 separately sends the RUCI (user identifier 1, PDN identifier 1) combination to the PCRF by using the NRR message; if the RCAF1 learns (user identifier 1, PDN identifier 1) the PCRF address corresponding to the combination, the RCAF1 may also (the user identifier) 1.
  • the PDN identifier 1) The RUCI of the combined RUCI and other user identifiers and PDN identifiers are encapsulated in an ARR message to the destination PCRF;
  • Step 613 The context corresponding to the combination of the RUCI update (user identifier 1, PDN identifier 1) received by the PCRF according to step 612 is (user identifier 1, PDN identifier 1, congestion area identifier, congestion level 1, RCAF1 address);
  • Step 614 At this time, the RCAF1 receives the MUR message, and determines that the RUCI corresponding to the user identifier (the user identifier 1, the PDN identifier 1) has been reported to the PCRF and the response message is not received. Therefore, the RCAF1 carries the rejection indication in the response message MUA returned by the PCRF. , may also carry reasons, such as performing RUCI reporting or pending transactions; therefore RCAF1 does not perform delete context operations according to MUR;
  • Step 615 The PCRF returns an acknowledgement message to the RCAF1.
  • Step 616 Since the PCRF determines that the UE has moved from RCAF2 to RCAF1, the PCRF sends a MUR message to RCAF2 requesting deletion of the context corresponding to (user identifier 1, PDN identifier 1);
  • Step 617 RCAF2 deletes the context corresponding to (user ID 1, PDN ID 1).
  • FIG. 7 is a schematic diagram of interaction of a method for managing congestion information provided by application example 4 of the present invention.
  • UE1 is initially in a congestion area managed by RCAF1, and the context saved by the PCRF also indicates that UE1 is under the congestion area managed by RCAF1, and then UE1 moves, moves to the congestion area managed by RCAF2, and then UE1 It moves back to the scene of the congestion area managed by RCAF1.
  • the RCAF1 acquires the congestion-related OAM information and the congestion area from the RAN OAM.
  • the RCAF1 also acquires the user identifier in the congestion area.
  • the RACF1 acquires the user in the congestion area from the MME.
  • the corresponding activated APN ie, the PDN identifier
  • the RCAF1 obtains the APN (ie, the PDN identifier) corresponding to the user identifier in the congestion area from the SGSN, and assumes that the UE1 (the user identifier 1) is located in the congestion area, and is activated.
  • the APN is (PDN identifier 1); here the congestion area where UE1 is located from congestion level 1 to congestion level 2;
  • Step 702. The RCAF1 constructs the RUCI according to the information obtained in step 501; wherein the RUCI combined by the (user identifier 1, PDN identifier 1) is (user identifier 1, PDN identifier 1, congestion area identifier, congestion level 2, RCAF1 address);
  • Step 703. The RCAF1 separately sends the RUCI (the user identifier 1, the PDN identifier) combination to the PCRF by using the NRR message; if the RCAF1 learns (the user identifier 1 and the PDN identifier 1) the PCRF address corresponding to the combination, the RCAF1 may also be (the user identifier 1) And the RUCI of the combined combination of the RUCI and the other user identifiers and the PDN identifiers are sent in an ARR message to the destination PCRF;
  • Step 704 After receiving the RUCI, the PCRF updates the saved context and returns an acknowledgement message to the RCAF1; (the user identifier 1, the PDN identifier 1) the combined context is (user identifier 1, PDN) Identification 1, congestion area identification, congestion level 2, RCAF1 address);
  • Step 705. The UE1 moves from the congestion area managed by the RCAF1 to the congestion area managed by the RCAF2; the RCAF2 acquires the congestion-related OAM information and the congestion area from the RAN OAM, and the RCAF2 also acquires the user identifier in the congestion area for the UTRAN access; - UTRAN access, the RACF 2 obtains the user identity and the corresponding activated APN (ie, the PDN identity) in the congestion zone from the MME.
  • the RCAF2 acquires the congestion-related OAM information and the congestion area from the RAN OAM
  • the RCAF2 also acquires the user identifier in the congestion area for the UTRAN access
  • the RACF 2 obtains the user identity and the corresponding activated APN (ie, the PDN identity) in the congestion zone from the MME.
  • the RCAF2 obtains the APN corresponding to the user identity in the congestion zone from the SGSN (ie, the PDN identity) ); since UE1 moves to a congested area (congestion level is 1), RCAF2 obtains user ID 1 and PDN ID 1, and corresponding congestion information;
  • Step 706 The RCAF2 constructs the RUCI according to the information obtained in step 705; wherein the RUCI of the combination of the user identifier 1, the PDN identifier 1 is (user identifier 1, PDN identifier 1, congestion area identifier, congestion level 1, RCAF2 address);
  • Step 707 Since the UE1 has just moved to the area managed by the RCAF2, the RCAF does not know (the user identifier 1, the PDN identifier 1) combines the corresponding PCRF address, so the PCAF1 sends the (User ID 1, PDN ID) combination separately to the PCRF by using the NRR message. RUCI;
  • Step 708 The PCRF updates the context (user identity 1, PDN identity 1) according to the context, such as (user identity 1, PDN identity 1, congestion zone identity, congestion level 1, RCAF2 address); the PCRF returns an acknowledgement message to RCAF2;
  • Step 709 The PCRF determines that the UE1 has moved from the RCAF1 to the RCAF2, so the PCRF sends a MUR message to the RCAF1 requesting to delete the context corresponding to the (User ID1, PDN ID1) stored in the RCAF1;
  • Step 710 At the same time, after the RCAF2 senses that the UE1 moves to its managed congestion area and reports the RUCI corresponding to the combination of (User ID 1, PDN ID 1), the UE1 moves from the congestion area managed by the RCAF2 to the congestion area managed by the RCAF1.
  • RCAF1 acquires congestion-related OAM information and congestion area from RAN OAM.
  • RCAF1 also obtains the user identity under the congestion area; for E-UTRAN access, RACF1 obtains the user identity under the congestion area from the MME.
  • Corresponding activated APN ie, PDN identifier
  • RCAF1 obtains the APN (ie, PDN identifier) corresponding to the user identifier in the congestion area from the SGSN; in addition, the congestion level of the congestion area changes from 2 to 1;
  • Step 711 The RCAF1 generates the RUCI according to the information of the step 710; wherein, the (the user identifier 1, the PDN identifier 1), the corresponding RUCI is (user identifier 1, PDN identifier 1, congestion area identifier, congestion level 1, RCAF1 address);
  • Step 712 RCAF1 separately sends the RUCI (user identifier 1, PDN identifier 1) combined to the PCRF by using the NRR message; if RCAF1 knows (user identifier 1, PDN identifier 1) the PCRF address corresponding to the combination, RCAF1 may also (user identifier) 1.
  • the PDN identifier 1) The RUCI of the combined RUCI and other user identifiers and PDN identifiers are encapsulated in an ARR message to the destination PCRF;
  • Step 713 The RCAF1 receives the MUR message, and determines that the RUCI corresponding to the (User ID 1, PDN ID 1) has been reported to the PCRF and the response message is not received, and the RCAF1 marks the corresponding context as an undetermined state;
  • Step 714 The response message MUA returned by the RCAF1 to the PCRF carries a rejection indication, and may also carry a reason, such as performing an RUCI report or an undetermined transaction;
  • Step 715 The PCRF receives the RUCI report of step 712, and the PCRF determines that the MUR message requesting deletion (user identity 1, PDN identity 1) combined context has been sent to RCAF1, but the response message has not been received yet, so the PCRF is not based on the new one.
  • the MUR message requesting deletion user identity 1, PDN identity 1
  • the RUCI updates the saved context; the PCRF returns a message to the RCAF1, the message carries a rejection indication, and may carry the reason, such as performing a RUCI report or a pending transaction (Pending Transaction); or, when the PCRF receives the RUCI, if before the PCRF Upon receiving the MUA message carrying the rejection indication, the PCRF may also decide to reject the RUCI report and not update the context, and return a response message carrying the rejection indication to the RCAF;
  • Step 716 Thereafter, the UE1 continues to stay in the congestion area managed by the RCAF1; the RCAF1 acquires the congestion-related OAM information and the congestion area from the RAN OAM again, and for the UTRAN access, the RCAF1 also acquires the user identity in the congestion area; for the E-UTRAN Accessing, the RACF1 obtains the user identifier and the corresponding activated APN (ie, the PDN identifier) in the congestion area from the MME. For the UTRAN access, the RCAF1 obtains the APN (ie, the PDN identifier) corresponding to the user identifier in the congestion area from the SGSN. Since UE1 is still in the congested area, RCAF1 obtains user ID 1 and PDN ID 1 again, and congestion information (congestion level is 1);
  • Step 717 The RCAF1 generates the RUCI according to the information obtained in step 716; wherein, the (the user identifier 1, the PDN identifier 1) combination corresponds to the RUCI (the user identifier 1, the PDN identifier 1, and the The congestion area identifier, the congestion level 1, the RCAF1 address), because the context flag is undetermined, even if the newly generated RUCI of the RCAF1 is consistent with the originally saved RUCI, it needs to be reported to the PCRF;
  • Step 718 The RCAF1 separately sends the RUCI (the user identifier 1 and the PDN identifier 1) to the PCRF by using the NRR message.
  • the RUCI of the combination of the user identifier 1 and the PDN identifier 1 is the user identifier 1, the PDN identifier 1, and the congestion area identifier. , congestion level 1, RCAF1 address);
  • Step 719 The PCRF updates the context according to the RUCI of step 718; wherein the context of the combination of (user identity 1, PDN identity 1) is (user identity 1, PDN identity 1, congestion zone identity, congestion level 1, RCAF1 address); PCRF to RCAF1 A confirmation message is returned; after receiving the confirmation message, RCAF1 deletes the undetermined status flag of the context.
  • FIG. 8 is a schematic structural diagram of a congestion information management system according to Embodiment 2 of the present invention.
  • the system shown in FIG. 8 includes a radio access network congestion sensing function RCAF receiving policy and a charging rule function PCRF, wherein:
  • the RCAF includes:
  • the first receiving module 801 is configured to receive a MUR message sent by the PCRF, where the MUR message includes request information for requesting deletion of the user identifier and the PDN identifier;
  • the first management module 802 is configured to reject the MUR message if the user identifier sent by the PCRF and the response message of the RUCI report corresponding to the PDN identifier are not received;
  • the PCRF includes:
  • the first sending module 803 is configured to send a MUR message to the RCAF.
  • the RCAF further includes:
  • the second sending module is configured to return a response message of the MUR message to the PCRF, where the response message of the MUR message carries the indication information rejecting the MUR message and/or the reason for rejecting the MUR message.
  • the reason for the rejection may be that the reported or undetermined transaction of the radio access network user plane congestion information RUCI report is being performed.
  • the RCAF further includes: a first marking module, configured to mark the context of the user identifier and the PDN identifier as an undetermined state.
  • the RCAF further includes: a second management module, configured to send a new RUCI report of the user identifier and the PDN identifier to the PCRF if the congestion information of the user identifier and the PDN identifier is subsequently received; If not received, the context of the user identity and PDN identity combination saved by the RCAF is deleted.
  • a second management module configured to send a new RUCI report of the user identifier and the PDN identifier to the PCRF if the congestion information of the user identifier and the PDN identifier is subsequently received; If not received, the context of the user identity and PDN identity combination saved by the RCAF is deleted.
  • the PCRF further includes: an update module, configured to: after receiving the RUCI report, update the saved context of the combination of the user identifier and the PDN identifier according to the RUCI report.
  • the PCRF further includes: a third management module, configured to: when receiving the RUCI report, if the response message of the MUR message is not received or the response message of the MUR message carrying the rejection indication is received, the rejection Report the RUCI report.
  • the RCAF when the PCRF interacts with the RCAF, after receiving the MUR report requesting to delete the combination of the user identifier and the PDN identifier, if the RCAF determines that the user identifier and the PDN identifier have been reported to the PCRF, If the corresponding RUCI report does not receive the response message, the RCAF rejects the MUR message from the PCRF, ensures that the correct context is saved locally, and reduces the occurrence of the misjudgment operation.
  • FIG. 9 is a schematic structural diagram of an embodiment of a device for managing congestion information according to Embodiment 3 of the present invention.
  • the device shown in Figure 9 includes:
  • the first receiving module 901 is configured to receive a modified user context request MUR message sent by the policy and charging rule function PCRF, where the MUR message includes request information for requesting deletion of the user identifier and the packet data network PDN identifier;
  • the first management module 902 is configured to reject the MUR message if the response message sent by the PCRF and the radio access network user plane congestion information RUCI report corresponding to the PDN identifier is not received.
  • the device further comprises:
  • a second sending module configured to return a response message of the MUR message to the PCRF, where the The response message of the MUR message carries the indication information rejecting the MUR message and/or the reason for rejecting the MUR message.
  • the reason for the rejection is that the reported or undetermined transaction of the radio access network user plane congestion information RUCI report is being executed.
  • the device further comprises:
  • the first marking module is configured to mark the context of the user identifier and the PDN identifier as an undetermined state.
  • the device further comprises:
  • a second management module configured to send a new RUCI report of the user identifier and the PDN identifier to the PCRF if the congestion information of the user identifier and the PDN identifier is subsequently received; if not received, delete the The context of the user identity and PDN identity saved by the RCAF.
  • the device when the PCRF interacts with the RCAF, after receiving the MUR report requesting to delete the combination of the user identifier and the PDN identifier, if the RCAF determines that the user identifier and the PDN identifier have been reported to the PCRF, If the corresponding RUCI report does not receive the response message, the RCAF rejects the MUR message from the PCRF, ensures that the correct context is saved locally, and reduces the occurrence of the misjudgment operation.
  • all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve. Thus, embodiments of the invention are not limited to any specific combination of hardware and software.
  • the devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.
  • each device/function module/functional unit in the above embodiment When each device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium.
  • the above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
  • the RCAF when the PCRF interacts with the RCAF, after receiving the MUR report requesting to delete the combination of the user identifier and the PDN identifier, if the RCAF determines that the user identifier and the PDN identifier have been reported to the PCRF, If the corresponding RUCI report does not receive the response message, the RCAF rejects the MUR message from the PCRF, ensures that the correct context is saved locally, and reduces the occurrence of the misjudgment operation.

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种拥塞信息的管理方法、装置和系统；所述方法包括：无线接入网拥塞感知功能RCAF接收策略和计费规则功能PCRF发送的修改用户上下文请求MUR消息，其中所述MUR消息包括请求删除用户标识和分组数据网络PDN标识的请求信息；所述RCAF若未收到向所述PCRF发送的所述用户标识和PDN标识无线接入网用户面拥塞信息RUCI报告的应答消息，则所述RCAF拒绝所述MUR消息。

Description

一种拥塞信息的管理方法、装置和系统 技术领域
本发明实施例涉及但不限于通信领域，尤其涉及一种拥塞信息的管理方法、装置和系统。
背景技术
图1是相关技术中第三代合作伙伴计划(3rd Generation Partnership Project，简称为3GPP)定义的策略和计费控制架构(Policy and Charging Control，简称为PCC)的示意图，如图1所示，策略和计费规则功能(Policy and Charging Rules Function，简称为PCRF)是整个PCC架构的核心。PCRF制定所述控制策略需要结合从应用功能(Application Function，简称为AF)接收的业务信息，从用户签约数据库(Subscription Profile Repository，简称为SPR)接收的用户签约信息，运营商配置的策略等。PCRF将为业务制定的控制策略下发给策略和计费执行功能(Policy and Charging Enforcement Function，简称为PCEF)或者承载绑定和事件上报功能(Bearer Binding and Event Report Function，简称为BBERF)执行。同时PCRF可以向PCEF和/或BBERF订阅承载层相关事件，以便当承载层发生所述事件时及时感知，并更改控制策略。PCEF也可以支持应用检测控制功能。PCEF可以根据本地配置或是PCRF下发的包含应用标识的PCC规则进行应用检测并进行策略执行(如门控、重定向和带宽限制)。PCEF一般都位于网络的网关上，如EPS的分组数据网络网关(PDN-GW)。此外，网络还可以通过部署独立业务检测功能(Traffic Detection Function，简称为TDF)来实现应用检测控制。TDF与PCRF通过Sd接口连接，TDF可以根据预先配置的或PCRF下发的应用检测控制(Application Detection and Control，简称为ADC)规则进行应用检测和策略执行。
图2为相关技术中PCRF感知无线接入网负荷信息的架构的示意图。无线接入网拥塞感知功能(RAN Congestion Awareness Function，简称为RCAF)通过Np接口将无线接入网用户面拥塞信息(RAN User Plane Congestion  Information，简称为RUCI)报告给PCRF用于PCRF进行策略决策以减轻网络负荷。RCAF从RAN操作管理维护(Operation Administration Maintenance，简称为OAM)系统收集用户面拥塞信息。对于E-UTRAN(Evolved UMTS Terrestrial Radio Access Network，演进的UMTS陆地无线接入网)，RCAF通过Nq接口从MME(Mobility Management Entity，移动管理实体)获得在特定演进的节点B(Evolved NodeB，简称为eNB)/演进的小区全球标识(Evolved Cell Global Identifier，简称为ECGI)下的针对每个激活APN的UE(IMSI)列表。对于UTRAN(UMTS Terrestrial Radio Access Network，UMTS陆地无线接入网)接入，RCAF可以从RAN直接获得特定节点B(NodeB，简称NB)/小区全球标识(Cell Global Identifier,CGI)下的IMSI列表，并且通过Nq’获取针对每个激活APN的IMSI列表。这样RCAF就可以获得每个拥塞基站(eNB/NB)/小区(ECGI/CGI)下的针对每个激活APN的IMSI列表。RCAF将这些信息上报给正确的PCRF，PCRF就可以对这些UE策略调整，减轻拥塞基站或小区的负荷。
通常情况下，在一个网络中存在一个或多个RCAF，每个RCAF负责管理一个网络区域(譬如每个RCAF对应一个小区列表或基站列表)。这样，就会存在UE在发生移动时，从一个RCAF的管理范围内移动到另一个RCAF的管理范围。理想状态下，PCRF收到和发送的消息都是步骤顺序进行的，然而在实际环境下，RCAF1、RCAF2以及PCRF发送消息和接收消息可能因为时延的原因而导致乱序，进而出现消息竞争的情况(Race Condition)发生。
在出现消息竞争的情况下，UE1最初处于RCAF1管理的一个拥塞区域下，并且PCRF保存的上下文也指示UE1在RCAF1管理的拥塞区域下，后来UE1发生了移动，移动到RCAF2管理的拥塞区域。在实际应用中，会出现如下情况：
PCRF判断UE1已经从RCAF1移动到了RCAF2，因此PCRF向RCAF1发送修改用户设备上下文(Modify UEcontext Request,MUR)消息，请求删除(用户标识1、PDN标识1)组合对应的下文。
在PCRF发送MUR消息之后，PCRF收了RCAF1发送的聚合RUCI报告请求(Aggregated RUCI Report Request，ARR)消息。而RCAF1在收到聚 合RUCI报告应答(Aggregated RUCI Report Answer，ARA)消息之前也收到了MUR消息，而这两个消息在内容上是冲突的，PCRF可能会判断UE1移动到RCAF2管理的区域后又回到了RCAF1，因此PCRF会根据RCAF1上报的RUCI更新PCRF保存的上下文。RCAF1则根据MUR决定删除(用户标识1，PDN1标识1)组合的上下文。
由上可以看出，在UE发生从一个PCAF移动到另外一个PCAF时，如何保证RCAF对拥塞信息的正确管理，减少误判的出现是亟待解决的问题。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例提供一种拥塞信息的管理方法、装置和系统，以保证RCAF对拥塞信息的正确管理。
本发明实施例提供了一种拥塞信息的管理方法，包括：
无线接入网拥塞感知功能RCAF接收策略和计费规则功能PCRF发送的修改用户上下文请求MUR消息，其中所述MUR消息包括请求删除用户标识和分组数据网络PDN标识的请求信息；
所述RCAF若未收到向所述PCRF发送的所述用户标识和PDN标识对应的无线接入网用户面拥塞信息RUCI报告的应答消息，则所述RCAF拒绝所述MUR消息。
可选地，所述方法还包括：所述RCAF向PCRF返回MUR消息的应答消息，其中所述MUR消息的应答消息携带拒绝所述MUR消息的指示信息和/或所述拒绝MUR消息的原因。
可选地，所述拒绝的原因为正在执行无线接入网用户面拥塞信息RUCI报告的上报或未定事务。
可选地，若所述RCAF拒绝所述MUR消息后，所述方法还包括：所述RCAF标记所述用户标识和PDN标识的上下文为未定状态。
可选地，所述方法还包括：若所述RCAF后续收到所述用户标识和PDN 标识的拥塞信息，则所述RCAF向所述PCRF发送所述用户标识和PDN标识的新的RUCI报告；若未收到，所述RCAF删除所述RCAF保存的所述用户标识和PDN标识的上下文。
可选地，所述方法还包括：所述PCRF在收到所述RUCI报告后，根据所述RUCI报告更新保存的所述用户标识和PDN标识的上下文。
可选地，所述方法还包括：若所述PCRF在收到所述RUCI报告时，所述PCRF未收到所述MUR消息的应答消息或收到拒绝所述MUR消息的应答消息，则所述PCRF拒绝所述RUCI报告。
本发明实施例还提供一种拥塞信息的管理系统，包括无线接入网拥塞感知功能RCAF接收策略和计费规则功能PCRF，其中：
所述RCAF，包括：
第一接收模块，设置为接收PCRF发送的修改用户上下文请求MUR消息，其中所述MUR消息包括请求删除用户标识和分组数据网络PDN标识的请求信息；以及
第一管理模块，设置为若未收到向所述PCRF发送的所述用户标识和PDN标识对应的无线接入网用户面拥塞信息RUCI报告的应答消息，则拒绝所述MUR消息；
所述PCRF，包括：第一发送模块，设置为向所述RCAF发送MUR消息。
可选地，所述RCAF还包括：第二发送模块，设置为向PCRF返回MUR消息的应答消息，其中所述MUR消息的应答消息携带拒绝所述MUR消息的指示信息和/或所述拒绝MUR消息的原因。
可选地，所述拒绝的原因为正在执行无线接入网用户面拥塞信息RUCI报告的上报或未定事务。
可选地，所述RCAF还包括：第一标记模块，设置为标记所述用户标识和PDN标识的上下文为未定状态。
可选地，所述RCAF还包括：第二管理模块，设置为若后续收到所述用户标识和PDN标识的拥塞信息，则向所述PCRF发送所述用户标识和PDN 标识的新的RUCI报告；若未收到，则删除所述RCAF保存的所述用户标识和PDN标识组合的上下文。
可选地，所述PCRF还包括：更新模块，设置为在收到所述RUCI报告后，根据所述RUCI报告更新保存的所述用户标识和PDN标识组合的上下文。
可选地，所述PCRF还包括：第三管理模块，设置为在收到所述RUCI报告时，若未收到所述MUR消息的应答消息或收到拒绝所述MUR消息的应答消息，拒绝所述RUCI报告。
本发明实施例还提供了一种拥塞信息的管理装置，包括：
第一接收模块，设置为接收策略和计费规则功能PCRF发送的修改用户上下文请求MUR消息，其中所述MUR消息包括请求删除用户标识和分组数据网络PDN标识的请求信息；以及
第二管理模块，设置为若未收到向所述PCRF发送的所述用户标识和PDN标识对应的无线接入网用户面拥塞信息RUCI报告的应答消息，则拒绝所述MUR消息。
可选地，所述装置还包括：第三发送模块，设置为向PCRF返回MUR消息的应答消息，其中所述MUR消息的应答消息携带拒绝所述MUR消息的指示信息和/或所述拒绝MUR消息的原因。
可选地，所述拒绝的原因为正在执行无线接入网用户面拥塞信息RUCI报告的上报或未定事务。
可选地，所述装置还包括：第一标记模块，设置为标记所述用户标识和PDN标识的上下文为未定状态。
可选地，所述装置还包括：第二管理模块，设置为若后续收到所述用户标识和PDN标识的拥塞信息，则向所述PCRF发送所述用户标识和PDN标识的新的RUCI报告；若未收到，则删除所述RCAF保存的所述用户标识和PDN标识的上下文。
本发明实施例还提供一种计算机可读存储介质，存储有程序指令，当该程序指令被执行时可实现上述方法。
本发明实施例提供的方案，PCRF在与RCAF交互时，当收到请求删除用户标识和PDN标识组合的MUR报告后，若所述RCAF判断已经向所述PCRF上报了所述用户标识和PDN标识对应的RUCI报告并且未收到应答消息，则所述RCAF拒绝来自PCRF的MUR消息，保证本地保存的了正确的上下文，减少误判操作的发生。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
图1是相关技术中第三代合作伙伴计划定义的策略和计费控制架构的示意图；
图2为相关技术中PCRF感知无线接入网负荷信息的架构的示意图；
图3为本发明实施例一提供的拥塞信息的管理方法实施例的流程示意图；
图4为本发明应用示例一提供的拥塞信息的管理方法的交互示意图；
图5为本发明应用示例二提供的拥塞信息的管理方法的交互示意图；
图6为本发明应用示例三提供的拥塞信息的管理方法的交互示意图；
图7为本发明应用示例四提供的拥塞信息的管理方法的交互示意图；
图8为本发明实施例二提供的拥塞信息的管理系统实施例的结构示意图；
图9为本发明实施例三提供的拥塞信息的管理装置实施例的结构示意图。
本发明的实施方式
下面将结合附图对本发明实施例进行详细描述。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
实施例一
图3为本发明实施例一提供的拥塞信息的管理方法实施例的流程示意 图。如图3所示，包括：
步骤301、RCAF接收PCRF发送的MUR消息，其中所述MUR消息包括请求删除用户标识和分组数据网络标识的请求信息；
步骤302、若所述RCAF未收到所述用户标识和分组数据网络标识对应的RUCI报告的应答消息，则所述RCAF拒绝所述MUR消息。
可选地，所述方法还包括：所述RCAF向PCRF返回MUR消息的应答消息，其中所述MUR消息的应答消息携带拒绝所述MUR消息的指示信息和/或所述拒绝MUR消息的原因。其中，所述拒绝的原因为正在执行RUCI报告的上报或未定事务。
可选地，所述RCAF拒绝所述MUR消息后，所述方法还包括：所述RCAF标记所述用户标识和PDN标识的上下文为未定状态。
可选地，所述方法还包括：若所述RCAF后续(即预设时间段内)收到所述用户标识和PDN标识的拥塞信息，则所述RCAF向所述PCRF发送所述用户标识和PDN标识的新的RUCI报告；若未收到，所述RCAF删除所述RCAF保存的所述用户标识和PDN标识的上下文。
可选地，所述方法还包括：所述PCRF在收到所述RUCI报告后，根据所述RUCI报告更新保存的所述用户标识和PDN标识的上下文。
可选地，所述方法还包括：若所述PCRF在收到所述RUCI报告时，所述PCRF未收到所述MUR消息的应答消息或收到拒绝所述MUR消息的应答消息，则所述PCRF拒绝所述RUCI报告。
本发明实施例提供的方法，PCRF在与RCAF交互时，当收到请求删除用户标识和PDN标识组合的MUR报告后，若所述RCAF判断已经向所述PCRF上报了所述用户标识和PDN标识对应的RUCI报告并且未收到应答消息，则所述RCAF拒绝来自PCRF的MUR消息，保证本地保存的了正确的上下文，减少误判操作的发生。
下面以几个应用示例来进行说明：
应用示例一
图4为本发明应用示例一提供的拥塞信息的管理方法的交互示意图。图 4所示方法中，UE1最初处于RCAF1管理的一个拥塞区域下，并且PCRF保存的上下文也指示UE1为RCAF1管理的拥塞区域下。
步骤401.RCAF1从RAN OAM获取拥塞相关的OAM信息以及拥塞区域，对于UTRAN接入，RCAF1还获取了拥塞区域下的用户标识；对于E-UTRAN接入，RACF1从MME从获取拥塞区域下的用户标识和对应的激活的APN(即PDN标识)；对于UTRAN接入，RCAF1从SGSN中获取拥塞区域下用户标识对应的APN(即PDN标识)；假设UE1(用户标识1)位于拥塞区域中，激活的APN为(PDN标识1)；这里UE1位于的拥塞区域从拥塞等级1到了拥塞等级2；
步骤402.RCAF1根据步骤401中获得的信息构造RUCI；其中(用户标识1、PDN标识1)组合的RUCI为(用户标识1，PDN标识1，拥塞区域标识，拥塞等级2，RCAF1地址)；
步骤403.RCAF1采用NRR(非聚合RUCI报告)消息单独向PCRF发送(用户标识1、PDN标识)组合的RUCI；若RCAF1获知(用户标识1、PDN标识1)组合对应的PCRF地址，则RCAF1也可将(用户标识1、PDN标识)组合的RUCI和其他该用户标识、PDN标识组合的RUCI封装在一个ARR(聚合RUCI报告)消息向目的PCRF发送；由于该消息被延迟，所以PCRF没有立即收到消息；
步骤404.UE1由RCAF1管理的拥塞区域移动到RCAF2管理的拥塞区域；RCAF2从RAN OAM获取拥塞相关的OAM信息以及拥塞区域，对于UTRAN接入，RCAF1还获取了拥塞区域下的用户标识；对于E-UTRAN接入，RACF2从MME从获取拥塞区域下的用户标识和对应的激活的APN(即PDN标识)；对于UTRAN接入，RCAF2从SGSN中获取拥塞区域下用户标识对应的APN(即PDN标识)；由于UE1移动到了拥塞区域(拥塞等级为1)，所以RCAF2获得用户标识1，PDN标识1以及其组合对应的拥塞信息；
步骤405.RCAF2根据步骤404中获得的信息构造RUCI；其中(用户标识1、PDN标识1)组合的RUCI为(用户标识1，PDN标识1，拥塞区域标识，拥塞等级1，RCAF2地址)；
步骤406.由于UE1刚移动到RCAF2管理的区域，RCAF2不知道(用 户标识1、PDN标识1)组合对应的PCRF地址，因此PCAF2采用NRR消息单独向PCRF发送(用户标识1、PDN标识)组合的RUCI；
步骤407.PCRF根据步骤406的RUCI更新(用户标识1、PDN标识1)组合在PCRF上保存的上下文，更新为(用户标识1，PDN标识1，拥塞区域标识，拥塞等级1，RCAF2地址)；PCRF向RCAF2返回确认消息；
步骤408.PCRF判断UE1已经从RCAF1移动到了RCAF2，因此PCRF向RCAF1发送MUR消息，请求删除在RCAF1上保存的(用户标识1、PDN标识1)对应的下文；
步骤409：此时，PCRF收到步骤403的RUCI报告，PCRF根据新的RUCI更新保存的上下文为(用户标识1，PDN标识1，拥塞区域标识，拥塞等级1，RCAF2地址)；
步骤410：RCAF1收到了MUR消息，判断已经向PCRF上报了(用户标识1，PDN标识1)对应的RUCI且没有收到应答消息，因此RCAF1向PCRF返回的应答消息MUA中携带拒绝指示，还可携带原因，如正在执行RUCI上报或未定的事物(Pending Transaction)；因此RCAF1不根据MUR执行删除上下文操作；
步骤411：PCRF向RCAF1返回确认消息；
步骤412：由于PCRF判断UE已经从RCAF2移动到了RCAF1，因此PCRF向RCAF2发送MUR消息，请求删除(用户标识1、PDN标识1)对应的上下文；
步骤413：RCAF2删除(用户标识1、PDN标识1)对应的上下文；如果PDN标识1是用户标识1的最后一个PDN标识，则RCAF2删除整个用户标识1的上下文；
步骤414：此后，UE1继续停留在RCAF2管理的拥塞区域；RCAF2再次从RAN OAM获取拥塞相关的OAM信息以及拥塞区域，对于UTRAN接入，RCAF2还获取了拥塞区域下的用户标识；对于E-UTRAN接入，RACF2从MME从获取拥塞区域下的用户标识和对应的激活的APN(即PDN标识)；对于UTRAN接入，RCAF1从SGSN中获取拥塞区域下用户标识对应的APN (即PDN标识)；由于UE1仍然在拥塞区域，所以RCAF2再次获得用户标识1和PDN标识1，以及拥塞信息(拥塞等级为1)；
步骤415：由于RCAF2中原来针对UE的上下文已经删除，因此RCAF2根据步骤414获得的信息，生成新的RUCI；其中，(用户标识1、PDN标识1)组合对应的RUCI为(用户标识1，PDN标识1，拥塞区域标识，拥塞等级1，RCAF2地址)；
步骤416：RCAF2采用NRR消息单独向PCRF发送(用户标识1、PDN标识1)组合的RUCI；其中(用户标识1、PDN标识1)组合的RUCI为(用户标识1，PDN标识1，拥塞区域标识，拥塞等级1，RCAF2地址)；
步骤417：PCRF根据最新的RUCI报告更新上下文；其中(用户标识1、PDN标识1)组合的上下文为(用户标识1，PDN标识1，拥塞区域标识，拥塞等级1，RCAF2地址)。
应用示例二：
图5为本发明应用示例二提供的拥塞信息的管理方法的交互示意图。图5所示方法中，UE1最初处于RCAF1管理的一个拥塞区域下，并且PCRF保存的上下文也指示UE1为RCAF1管理的拥塞区域下。
步骤501.RCAF1从RAN OAM获取拥塞相关的OAM信息以及拥塞区域，对于UTRAN接入，RCAF1还获取了拥塞区域下的用户标识；对于E-UTRAN接入，RACF1从MME从获取拥塞区域下的用户标识和对应的激活的APN(即PDN标识)；对于UTRAN接入，RCAF1从SGSN中获取拥塞区域下用户标识对应的APN(即PDN标识)；假设UE1(用户标识1)位于拥塞区域中，激活的APN为(PDN标识1)；这里UE1位于的拥塞区域从拥塞等级1到了拥塞等级2；
步骤502.RCAF1根据步骤501中获得的信息构造RUCI；其中(用户标识1、PDN标识1)组合的RUCI为(用户标识1，PDN标识1，拥塞区域标识，拥塞等级2，RCAF1地址)；
步骤503.RCAF1采用NRR消息单独向PCRF发送(用户标识1、PDN 标识)组合的RUCI；若RCAF1获知(用户标识1、PDN标识1)组合对应的PCRF地址，则RCAF1也可将(用户标识1、PDN标识)组合的RUCI和其他该用户标识、PDN标识组合的RUCI封装在一个ARR消息向目的PCRF发送；由于该消息被延迟，所以PCRF没有立即收到消息；
步骤504.UE1由RCAF1管理的拥塞区域移动到RCAF2管理的拥塞区域；RCAF2从RAN OAM获取拥塞相关的OAM信息以及拥塞区域，对于UTRAN接入，RCAF1还获取了拥塞区域下的用户标识；对于E-UTRAN接入，RACF2从MME从获取拥塞区域下的用户标识和对应的激活的APN(即PDN标识)；对于UTRAN接入，RCAF2从SGSN中获取拥塞区域下用户标识对应的APN(即PDN标识)；由于UE1移动到了拥塞区域(拥塞等级为1)，所以RCAF2获得用户标识1，PDN标识1以及其组合对应的拥塞信息；
步骤505.RCAF2根据步骤404中获得的信息构造RUCI；其中(用户标识1、PDN标识1)组合的RUCI为(用户标识1，PDN标识1，拥塞区域标识，拥塞等级1，RCAF2地址)；
步骤506.由于UE1刚移动到RCAF2管理的区域，RCAF2不知道(用户标识1、PDN标识1)组合对应的PCRF地址，因此PCAF2采用NRR消息单独向PCRF发送(用户标识1、PDN标识)组合的RUCI；
步骤507.PCRF根据步骤506的RUCI更新(用户标识1、PDN标识1)组合在PCRF上保存的上下文，更新为(用户标识1，PDN标识1，拥塞区域标识，拥塞等级1，RCAF2地址)；PCRF向RCAF2返回确认消息；
步骤508.PCRF判断UE1已经从RCAF1移动到了RCAF2，因此PCRF向RCAF1发送MUR消息，请求删除在RCAF1上保存的(用户标识1、PDN标识1)对应的下文；
步骤509：RCAF1收到了MUR消息，判断已经向PCRF上报了(用户标识1，PDN标识1)对应的RUCI且没有收到应答消息，RCAF1将相应的上下文标记为未定状态；
步骤510：RCAF1向PCRF返回的应答消息MUA中携带拒绝指示，还可携带原因，如正在执行RUCI上报或未定的事务(Pending Transaction)；
步骤511：PCRF收到步骤503的RUCI报告，PCRF判断已经向RCAF1发送了请求删除(用户标识1，PDN标识1)组合上下文的MUR消息，但是还没有收到应答消息，因此PCRF不根据新的RUCI更新保存的上下文；PCRF向RCAF1返回应带消息，消息中携带拒绝指示，还可携带原因，如正在执行RUCI上报或未定的事务(Pending Transaction)；或者，当PCRF收到RUCI，若PCRF之前就收到了携带拒绝指示的MUA消息，PCRF也可决定要拒绝RUCI报告，并且不更新上下文，并向RCAF返回携带拒绝指示的应答消息；
步骤512：在下一个周期，RCAF1再次从RAN OAM获取拥塞相关的OAM信息以及拥塞区域，对于UTRAN接入，RCAF1还获取了拥塞区域下的用户标识；对于E-UTRAN接入，RACF1从MME从获取拥塞区域下的用户标识和对应的激活的APN(即PDN标识)；对于UTRAN接入，RCAF1从SGSN中获取拥塞区域下用户标识对应的APN(即PDN标识)；由于UE1已经离开拥塞区域，所以RCAF1没有再次获得用户标识1和PDN标识1，以及拥塞信息；
步骤513：因为(用户标识1、PDN标识1)的上下文为未定状态，同时RCAF1没有检测到UE1位于其管理的拥塞区域，因此RCAF1删除其对应的上下文。
应用示例三
图6为本发明应用示例三提供的拥塞信息的管理方法的交互示意图。图6所示方法中，UE1最初处于RCAF1管理的一个拥塞区域下，并且PCRF保存的上下文也指示UE1为RCAF1管理的拥塞区域下，后来UE1发生了移动，移动到RCAF2管理的拥塞区域，随后UE1又移动回RCAF1管理的拥塞区域的场景。
步骤601.RCAF1从RAN OAM获取拥塞相关的OAM信息以及拥塞区域，对于UTRAN接入，RCAF1还获取了拥塞区域下的用户标识；对于E-UTRAN接入，RACF1从MME从获取拥塞区域下的用户标识和对应的激活的APN(即PDN标识)；对于UTRAN接入，RCAF1从SGSN中获取拥塞区域下用户标识对应的APN(即PDN标识)；假设UE1(用户标识1)位 于拥塞区域中，激活的APN为(PDN标识1)；这里UE1位于的拥塞区域从拥塞等级1到了拥塞等级2；
步骤602.RCAF1根据步骤501中获得的信息构造RUCI；其中(用户标识1、PDN标识1)组合的RUCI为(用户标识1，PDN标识1，拥塞区域标识，拥塞等级2，RCAF1地址)；
步骤603.RCAF1采用NRR消息单独向PCRF发送(用户标识1、PDN标识)组合的RUCI；若RCAF1获知(用户标识1、PDN标识1)组合对应的PCRF地址，则RCAF1也可将(用户标识1、PDN标识)组合的RUCI和其他用户标识、PDN标识组合的RUCI封装在一个ARR消息向目的PCRF发送；
步骤604.PCRF收到RUCI后，更新保存的上下文，并向RCAF1返回确认消息；(用户标识1、PDN标识1)组合的上下文为(用户标识1，PDN标识1，拥塞区域标识，拥塞等级2，RCAF1地址)；
步骤605.UE1由RCAF1管理的拥塞区域移动到RCAF2管理的拥塞区域；RCAF2从RAN OAM获取拥塞相关的OAM信息以及拥塞区域，对于UTRAN接入，RCAF2还获取了拥塞区域下的用户标识；对于E-UTRAN接入，RACF2从MME从获取拥塞区域下的用户标识和对应的激活的APN(即PDN标识)；对于UTRAN接入，RCAF2从SGSN中获取拥塞区域下用户标识对应的APN(即PDN标识)；由于UE1移动到了拥塞区域(拥塞等级为1)，所以RCAF2获得用户标识1和PDN标识1，以及对应的拥塞信息；
步骤606.RCAF2根据步骤605中获得的信息构造RUCI；其中(用户标识1、PDN标识1)组合的RUCI为(用户标识1，PDN标识1，拥塞区域标识，拥塞等级1，RCAF2地址)；
步骤607.由于UE1刚移动到RCAF2管理的区域，RCAF不知道(用户标识1、PDN标识1)组合对应的PCRF地址，因此PCAF1采用NRR消息单独向PCRF发送(用户标识1、PDN标识)组合的RUCI；
步骤608.PCRF根据RUCI更新(用户标识1、PDN标识1)组合的上下文，如(用户标识1，PDN标识1，拥塞区域标识，拥塞等级1，RCAF2地 址)；PCRF向RCAF2返回确认消息；
步骤609.PCRF判断UE1已经从RCAF1移动到了RCAF2，因此PCRF向RCAF1发送MUR消息，请求删除保存在RCAF1上的(用户标识1、PDN标识1)对应的上下文；
步骤610.同时，当RCAF2感知到UE1移动到其管理的拥塞区域从而上报包含(用户标识1、PDN标识1)组合对应的RUCI之后，UE1又从RCAF2管理的拥塞区域移动到RCAF1管理的拥塞区域；RCAF1从RAN OAM获取拥塞相关的OAM信息以及拥塞区域，对于UTRAN接入，RCAF1还获取了拥塞区域下的用户标识；对于E-UTRAN接入，RACF1从MME从获取拥塞区域下的用户标识和对应的激活的APN(即PDN标识)；对于UTRAN接入，RCAF1从SGSN中获取拥塞区域下用户标识对应的APN(即PDN标识)；此外，拥塞区域的拥塞等级从2变成了1；
步骤611：RCAF1根据步骤610的信息生成RUCI；其中，(用户标识1、PDN标识1)组合对应的RUCI为(用户标识1，PDN标识1，拥塞区域标识，拥塞等级1，RCAF1地址)；
步骤612：RCAF1采用NRR消息单独向PCRF发送(用户标识1、PDN标识1)组合的RUCI；若RCAF1获知(用户标识1、PDN标识1)组合对应的PCRF地址，则RCAF1也可将(用户标识1、PDN标识1)组合的RUCI和其他用户标识、PDN标识组合的RUCI封装在一个ARR消息向目的PCRF发送；
步骤613：PCRF根据步骤612收到的RUCI更新(用户标识1、PDN标识1)组合对应的上下文为(用户标识1，PDN标识1，拥塞区域标识，拥塞等级1，RCAF1地址)；
步骤614：此时，RCAF1收到了MUR消息，判断已经向PCRF上报了(用户标识1，PDN标识1)对应的RUCI且没有收到应答消息，因此RCAF1向PCRF返回的应答消息MUA中携带拒绝指示，还可携带原因，如正在执行RUCI上报或未定事务；因此RCAF1不根据MUR执行删除上下文操作；
步骤615：PCRF向RCAF1返回确认消息；
步骤616：由于PCRF判断UE已经从RCAF2移动到了RCAF1，因此PCRF向RCAF2发送MUR消息，请求删除(用户标识1、PDN标识1)对应的上下文；
步骤617：RCAF2删除(用户标识1、PDN标识1)对应的上下文。
应用示例四
图7为本发明应用示例四提供的拥塞信息的管理方法的交互示意图。图7所示方法中，UE1最初处于RCAF1管理的一个拥塞区域下，并且PCRF保存的上下文也指示UE1为RCAF1管理的拥塞区域下，后来UE1发生了移动，移动到RCAF2管理的拥塞区域，随后UE1又移动回RCAF1管理的拥塞区域的场景。
步骤701.RCAF1从RAN OAM获取拥塞相关的OAM信息以及拥塞区域，对于UTRAN接入，RCAF1还获取了拥塞区域下的用户标识；对于E-UTRAN接入，RACF1从MME从获取拥塞区域下的用户标识和对应的激活的APN(即PDN标识)；对于UTRAN接入，RCAF1从SGSN中获取拥塞区域下用户标识对应的APN(即PDN标识)；假设UE1(用户标识1)位于拥塞区域中，激活的APN为(PDN标识1)；这里UE1位于的拥塞区域从拥塞等级1到了拥塞等级2；
步骤702.RCAF1根据步骤501中获得的信息构造RUCI；其中(用户标识1、PDN标识1)组合的RUCI为(用户标识1，PDN标识1，拥塞区域标识，拥塞等级2，RCAF1地址)；
步骤703.RCAF1采用NRR消息单独向PCRF发送(用户标识1、PDN标识)组合的RUCI；若RCAF1获知(用户标识1、PDN标识1)组合对应的PCRF地址，则RCAF1也可将(用户标识1、PDN标识)组合的RUCI和其他用户标识、PDN标识组合的RUCI封装在一个ARR消息向目的PCRF发送；
步骤704.PCRF收到RUCI后，更新保存的上下文，并向RCAF1返回确认消息；(用户标识1、PDN标识1)组合的上下文为(用户标识1，PDN 标识1，拥塞区域标识，拥塞等级2，RCAF1地址)；
步骤705.UE1由RCAF1管理的拥塞区域移动到RCAF2管理的拥塞区域；RCAF2从RAN OAM获取拥塞相关的OAM信息以及拥塞区域，对于UTRAN接入，RCAF2还获取了拥塞区域下的用户标识；对于E-UTRAN接入，RACF2从MME从获取拥塞区域下的用户标识和对应的激活的APN(即PDN标识)；对于UTRAN接入，RCAF2从SGSN中获取拥塞区域下用户标识对应的APN(即PDN标识)；由于UE1移动到了拥塞区域(拥塞等级为1)，所以RCAF2获得用户标识1和PDN标识1，以及对应的拥塞信息；
步骤706.RCAF2根据步骤705中获得的信息构造RUCI；其中(用户标识1、PDN标识1)组合的RUCI为(用户标识1，PDN标识1，拥塞区域标识，拥塞等级1，RCAF2地址)；
步骤707.由于UE1刚移动到RCAF2管理的区域，RCAF不知道(用户标识1、PDN标识1)组合对应的PCRF地址，因此PCAF1采用NRR消息单独向PCRF发送(用户标识1、PDN标识)组合的RUCI；
步骤708.PCRF根据RUCI更新(用户标识1、PDN标识1)组合的上下文，如(用户标识1，PDN标识1，拥塞区域标识，拥塞等级1，RCAF2地址)；PCRF向RCAF2返回确认消息；
步骤709.PCRF判断UE1已经从RCAF1移动到了RCAF2，因此PCRF向RCAF1发送MUR消息，请求删除保存在RCAF1上的(用户标识1、PDN标识1)对应的上下文；
步骤710.同时，当RCAF2感知到UE1移动到其管理的拥塞区域从而上报包含(用户标识1、PDN标识1)组合对应的RUCI之后，UE1又从RCAF2管理的拥塞区域移动到RCAF1管理的拥塞区域；RCAF1从RAN OAM获取拥塞相关的OAM信息以及拥塞区域，对于UTRAN接入，RCAF1还获取了拥塞区域下的用户标识；对于E-UTRAN接入，RACF1从MME从获取拥塞区域下的用户标识和对应的激活的APN(即PDN标识)；对于UTRAN接入，RCAF1从SGSN中获取拥塞区域下用户标识对应的APN(即PDN标识)；此外，拥塞区域的拥塞等级从2变成了1；
步骤711：RCAF1根据步骤710的信息生成RUCI；其中，(用户标识1、PDN标识1)组合对应的RUCI为(用户标识1，PDN标识1，拥塞区域标识，拥塞等级1，RCAF1地址)；
步骤712：RCAF1采用NRR消息单独向PCRF发送(用户标识1、PDN标识1)组合的RUCI；若RCAF1获知(用户标识1、PDN标识1)组合对应的PCRF地址，则RCAF1也可将(用户标识1、PDN标识1)组合的RUCI和其他用户标识、PDN标识组合的RUCI封装在一个ARR消息向目的PCRF发送；
步骤713：RCAF1收到了MUR消息，判断已经向PCRF上报了(用户标识1，PDN标识1)对应的RUCI且没有收到应答消息，RCAF1将相应的上下文标记为未定状态；
步骤714：RCAF1向PCRF返回的应答消息MUA中携带拒绝指示，还可携带原因，如正在执行RUCI上报或未定事务；
步骤715：PCRF收到步骤712的RUCI报告，PCRF判断已经向RCAF1发送了请求删除(用户标识1，PDN标识1)组合上下文的MUR消息，但是还没有收到应答消息，因此PCRF不根据新的RUCI更新保存的上下文；PCRF向RCAF1返回应带消息，消息中携带拒绝指示，还可携带原因，如正在执行RUCI上报或未定的事务(Pending Transaction)；或者，当PCRF收到RUCI，若PCRF之前就收到了携带拒绝指示的MUA消息，PCRF也可决定要拒绝RUCI报告，并且不更新上下文，并向RCAF返回携带拒绝指示的应答消息；
步骤716：此后，UE1继续停留在RCAF1管理的拥塞区域；RCAF1再次从RAN OAM获取拥塞相关的OAM信息以及拥塞区域，对于UTRAN接入，RCAF1还获取了拥塞区域下的用户标识；对于E-UTRAN接入，RACF1从MME从获取拥塞区域下的用户标识和对应的激活的APN(即PDN标识)；对于UTRAN接入，RCAF1从SGSN中获取拥塞区域下用户标识对应的APN(即PDN标识)；由于UE1仍然在拥塞区域，所以RCAF1再次获得用户标识1和PDN标识1，以及拥塞信息(拥塞等级为1)；
步骤717：RCAF1根据步骤716获得的信息，生成RUCI；其中，(用户标识1、PDN标识1)组合对应的RUCI为(用户标识1，PDN标识1，拥 塞区域标识，拥塞等级1，RCAF1地址)由于上下文标记为未定状态，即使RCAF1新生成的RUCI和原来保存的RUCI一致，也需要向PCRF上报；
步骤718：RCAF1采用NRR消息单独向PCRF发送(用户标识1、PDN标识1)组合的RUCI；其中(用户标识1、PDN标识1)组合的RUCI为(用户标识1，PDN标识1，拥塞区域标识，拥塞等级1，RCAF1地址)；
步骤719：PCRF根据步骤718的RUCI更新上下文；其中(用户标识1、PDN标识1)组合的上下文为(用户标识1，PDN标识1，拥塞区域标识，拥塞等级1，RCAF1地址)；PCRF向RCAF1返回确认消息；RCAF1收到确认消息后，删除上下文的未定状态标记。
实施例二
图8为本发明实施例二提供的拥塞信息的管理系统的结构示意图。图8所示的系统，包括无线接入网拥塞感知功能RCAF接收策略和计费规则功能PCRF，其中：
所述RCAF，包括：
第一接收模块801，设置为接收PCRF发送的MUR消息，其中所述MUR消息包括请求删除用户标识和PDN标识的请求信息；以及
第一管理模块802，设置为若未收到向所述PCRF发送的所述用户标识和PDN标识对应的RUCI报告的应答消息，则拒绝所述MUR消息；
所述PCRF，包括：
第一发送模块803，设置为向所述RCAF发送MUR消息。
其中，所述RCAF还包括：
第二发送模块，设置为向PCRF返回MUR消息的应答消息，其中所述MUR消息的应答消息携带拒绝所述MUR消息的指示信息和/或所述拒绝MUR消息的原因。
其中，所述拒绝的原因可以是正在执行无线接入网用户面拥塞信息RUCI报告的上报或未定事务。
其中，所述RCAF还包括：第一标记模块，设置为标记所述用户标识和PDN标识的上下文为未定状态。
其中，所述RCAF还包括：第二管理模块，设置为若后续收到所述用户标识和PDN标识的拥塞信息，则向所述PCRF发送所述用户标识和PDN标识的新的RUCI报告；若未收到，则删除所述RCAF保存的所述用户标识和PDN标识组合的上下文。
其中，所述PCRF还包括：更新模块，设置为在收到所述RUCI报告后，根据所述RUCI报告更新保存的所述用户标识和PDN标识组合的上下文。
其中，所述PCRF还包括：第三管理模块，设置为在收到所述RUCI报告时，若未收到MUR消息的应答消息或收到携带所述拒绝指示的MUR消息的应答消息，拒绝所述RUCI报告。
本发明实施例提供的系统，PCRF在与RCAF交互时，当收到请求删除用户标识和PDN标识组合的MUR报告后，若所述RCAF判断已经向所述PCRF上报了所述用户标识和PDN标识对应的RUCI报告并且未收到应答消息，则所述RCAF拒绝来自PCRF的MUR消息，保证本地保存的了正确的上下文，减少误判操作的发生。
实施例三
图9为本发明实施例三提供的拥塞信息的管理装置实施例的结构示意图。图9所示装置，包括：
第一接收模块901，设置为接收策略和计费规则功能PCRF发送的修改用户上下文请求MUR消息，其中所述MUR消息包括请求删除用户标识和分组数据网络PDN标识的请求信息；以及
第一管理模块902，设置为若未收到向所述PCRF发送的所述用户标识和PDN标识对应的无线接入网用户面拥塞信息RUCI报告的应答消息，则拒绝所述MUR消息。
其中，所述装置还包括：
第二发送模块，设置为向PCRF返回MUR消息的应答消息，其中所述 MUR消息的应答消息携带拒绝所述MUR消息的指示信息和/或所述拒绝MUR消息的原因。
其中，所述拒绝的原因为正在执行无线接入网用户面拥塞信息RUCI报告的上报或未定事务。
其中，所述装置还包括：
第一标记模块，设置为标记所述用户标识和PDN标识的上下文为未定状态。
其中，所述装置还包括：
第二管理模块，设置为若后续收到所述用户标识和PDN标识的拥塞信息，则向所述PCRF发送所述用户标识和PDN标识的新的RUCI报告；若未收到，则删除所述RCAF保存的所述用户标识和PDN标识的上下文。
本发明实施例提供的装置，PCRF在与RCAF交互时，当收到请求删除用户标识和PDN标识组合的MUR报告后，若所述RCAF判断已经向所述PCRF上报了所述用户标识和PDN标识对应的RUCI报告并且未收到应答消息，则所述RCAF拒绝来自PCRF的MUR消息，保证本地保存的了正确的上下文，减少误判操作的发生。
本领域普通技术人员可以理解上述实施例的全部或部分步骤可以使用计算机程序流程来实现，所述计算机程序可以存储于一计算机可读存储介质中，所述计算机程序在相应的硬件平台上(如系统、设备、装置、器件等)执行，在执行时，包括方法实施例的步骤之一或其组合。
可选地，上述实施例的全部或部分步骤也可以使用集成电路来实现，这些步骤可以被分别制作成一个个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明实施例不限制于任何特定的硬件和软件结合。
上述实施例中的各装置/功能模块/功能单元可以采用通用的计算装置来实现，它们可以集中在单个的计算装置上，也可以分布在多个计算装置所组成的网络上。
上述实施例中的各装置/功能模块/功能单元以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。上述提到的计算机可读取存储介质可以是只读存储器，磁盘或光盘等。
工业实用性
本发明实施例提供的方案，PCRF在与RCAF交互时，当收到请求删除用户标识和PDN标识组合的MUR报告后，若所述RCAF判断已经向所述PCRF上报了所述用户标识和PDN标识对应的RUCI报告并且未收到应答消息，则所述RCAF拒绝来自PCRF的MUR消息，保证本地保存的了正确的上下文，减少误判操作的发生。

Claims (20)

  1. 一种拥塞信息的管理方法，包括：
    无线接入网拥塞感知功能RCAF接收策略和计费规则功能PCRF发送的修改用户上下文请求MUR消息，其中所述MUR消息包括请求删除用户标识和分组数据网络PDN标识的请求信息；
    所述RCAF若未收到向所述PCRF发送的所述用户标识和PDN标识对应的无线接入网用户面拥塞信息RUCI报告的应答消息，则所述RCAF拒绝所述MUR消息。
  2. 根据权利要求1所述的方法，所述方法还包括：
    所述RCAF向PCRF返回MUR消息的应答消息，其中所述MUR消息的应答消息携带拒绝所述MUR消息的指示信息和/或所述拒绝MUR消息的原因。
  3. 根据权利要求2所述的方法，其中，所述拒绝的原因为正在执行RUCI报告的上报或未定事务。
  4. 根据权利要求1所述的方法，所述RCAF拒绝所述MUR消息后，所述方法还包括：
    所述RCAF标记所述用户标识和PDN标识的上下文为未定状态。
  5. 根据权利要求4所述的方法，所述方法还包括：
    若所述RCAF后续收到所述用户标识和PDN标识的拥塞信息，则所述RCAF向所述PCRF发送所述用户标识和PDN标识的新的RUCI报告；若未收到，所述RCAF删除所述RCAF保存的所述用户标识和PDN标识的上下文。
  6. 根据权利要求1所述的方法，所述方法还包括：
    所述PCRF在收到所述RUCI报告后，根据所述RUCI报告更新保存的所述用户标识和PDN标识的上下文。
  7. 根据权利要求1所述的方法，所述方法还包括：
    若所述PCRF在收到所述RUCI报告时，所述PCRF未收到所述MUR消息的应答消息或收到拒绝所述MUR消息的应答消息，则所述PCRF拒绝所述 RUCI报告。
  8. 一种拥塞信息的管理系统，包括无线接入网拥塞感知功能RCAF和策略和计费规则功能PCRF，其中：
    所述RCAF，包括：
    第一接收模块，设置为接收PCRF发送的修改用户上下文请求MUR消息，其中所述MUR消息包括请求删除用户标识和分组数据网络PDN标识的请求信息；以及
    第一管理模块，设置为若未收到向所述PCRF发送的所述用户标识和PDN标识对应的无线接入网用户面拥塞信息RUCI报告的应答消息，则拒绝所述MUR消息；
    所述PCRF，包括：
    第一发送模块，设置为向所述RCAF发送MUR消息。
  9. 根据权利要求8所述的系统，所述RCAF还包括：
    第二发送模块，设置为向PCRF返回MUR消息的应答消息，其中所述MUR消息的应答消息携带拒绝所述MUR消息的指示信息和/或所述拒绝MUR消息的原因。
  10. 根据权利要求9所述的系统，其中，所述拒绝的原因为正在执行RUCI报告的上报或未定事务。
  11. 根据权利要求8所述的系统，所述RCAF还包括：
    第一标记模块，设置为标记所述用户标识和PDN标识的上下文为未定状态。
  12. 根据权利要求11所述的系统，所述RCAF还包括：
    第二管理模块，设置为若后续收到所述用户标识和PDN标识的拥塞信息，则向所述PCRF发送所述用户标识和PDN标识的新的RUCI报告；若未收到，则删除所述RCAF保存的所述用户标识和PDN标识组合的上下文。
  13. 根据权利要求9所述的系统，所述PCRF还包括：
    更新模块，设置为在收到所述RUCI报告后，根据所述RUCI报告更新 保存的所述用户标识和PDN标识组合的上下文。
  14. 根据权利要求9所述的系统，所述PCRF还包括：
    第三管理模块，设置为在收到所述RUCI报告时，若未收到所述MUR消息的应答消息或收到拒绝所述MUR消息的应答消息，拒绝所述RUCI报告。
  15. 一种拥塞信息的管理装置，包括：
    第一接收模块，设置为接收策略和计费规则功能PCRF发送的修改用户上下文请求MUR消息，其中所述MUR消息包括请求删除用户标识和分组数据网络PDN标识的请求信息；以及
    第一管理模块，设置为若未收到向所述PCRF发送的所述用户标识和PDN标识对应的无线接入网用户面拥塞信息RUCI报告的应答消息，则拒绝所述MUR消息。
  16. 根据权利要求15所述的装置，所述装置还包括：
    第二发送模块，设置为向PCRF返回MUR消息的应答消息，其中所述MUR消息的应答消息携带拒绝所述MUR消息的指示信息和/或所述拒绝MUR消息的原因。
  17. 根据权利要求16所述的装置，其中，所述拒绝的原因为正在执行无线接入网用户面拥塞信息RUCI报告的上报或未定事务。
  18. 根据权利要求15所述的装置，所述装置还包括：
    第一标记模块，设置为标记所述用户标识和PDN标识的上下文为未定状态。
  19. 根据权利要求18所述的装置，所述装置还包括：
    第二管理模块，设置为若后续收到所述用户标识和PDN标识的拥塞信息，则向所述PCRF发送所述用户标识和PDN标识的新的RUCI报告；若未收到，则删除所述RCAF保存的所述用户标识和PDN标识的上下文。
  20. 一种计算机可读存储介质，存储有程序指令，当该程序指令被执行时可实现权利要求1-7任一项所述的方法。
PCT/CN2015/087045 2015-01-26 2015-08-14 一种拥塞信息的管理方法、装置和系统 WO2016119439A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510039408.4 2015-01-26
CN201510039408.4A CN105897607A (zh) 2015-01-26 2015-01-26 一种拥塞信息的管理方法、装置和系统

Publications (1)

Publication Number Publication Date
WO2016119439A1 true WO2016119439A1 (zh) 2016-08-04

Family

ID=56542311

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/087045 WO2016119439A1 (zh) 2015-01-26 2015-08-14 一种拥塞信息的管理方法、装置和系统

Country Status (2)

Country Link
CN (1) CN105897607A (zh)
WO (1) WO2016119439A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113872872A (zh) * 2021-09-29 2021-12-31 新华三信息安全技术有限公司 一种报文转发方法、装置及框式网络设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103905447A (zh) * 2014-04-01 2014-07-02 华为技术有限公司 业务链路选择控制方法以及设备
US20140369206A1 (en) * 2013-06-12 2014-12-18 Telefonaktiebolaget L M Ericsson Node and Method For RAN Congestion Status Handling
CN104284319A (zh) * 2013-07-02 2015-01-14 中兴通讯股份有限公司 一种基于拥塞控制的策略控制方法、装置和系统

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020087681A1 (en) * 2000-12-28 2002-07-04 Kenichi Kishi Co-evaluation system for component of electronic device
US20070286197A1 (en) * 2006-04-21 2007-12-13 Harper John A Interoperable transport protocol for internetwork routing
CN100546258C (zh) * 2007-07-24 2009-09-30 华为技术有限公司 实现策略与计费控制的方法、装置和系统
KR102046323B1 (ko) * 2012-03-08 2019-11-19 삼성전자주식회사 무선 통신 시스템에서 무선 억세스 네트워크의 트래픽 제어 방법 및 장치
CN104301250A (zh) * 2014-10-31 2015-01-21 华为技术有限公司 一种无线拥塞控制方法和设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140369206A1 (en) * 2013-06-12 2014-12-18 Telefonaktiebolaget L M Ericsson Node and Method For RAN Congestion Status Handling
CN104284319A (zh) * 2013-07-02 2015-01-14 中兴通讯股份有限公司 一种基于拥塞控制的策略控制方法、装置和系统
CN103905447A (zh) * 2014-04-01 2014-07-02 华为技术有限公司 业务链路选择控制方法以及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON.: "UE Mobility between RCAFs.", 3GPP TSG CT3 MEETING #79 C3-145240., 21 November 2014 (2014-11-21) *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113872872A (zh) * 2021-09-29 2021-12-31 新华三信息安全技术有限公司 一种报文转发方法、装置及框式网络设备
CN113872872B (zh) * 2021-09-29 2023-11-24 新华三信息安全技术有限公司 一种报文转发方法、装置及框式网络设备

Also Published As

Publication number Publication date
CN105897607A (zh) 2016-08-24

Similar Documents

Publication Publication Date Title
US20230138587A1 (en) Tracking qos violated events
US11596023B2 (en) Overload control and coordination between M2M service layer and 3GPP networks
JP7444153B2 (ja) 第１の装置による方法及びｐｃｒｆ装置による方法
US10616120B2 (en) Service layer southbound interface and quality of service
WO2020211855A1 (zh) 无人机的鉴权方法及装置
CN107637101B (zh) 用于提供监控服务的系统和方法
WO2011050689A1 (zh) 机器类通讯终端的接入控制方法和系统
WO2012051890A1 (zh) 终端接入限制的方法及系统
WO2017173941A9 (zh) 服务质量QoS策略的处理方法、装置及系统
US20240155316A1 (en) Method and apparatus for event monitoring
WO2011050688A1 (zh) 机器类通讯终端信息的获取方法和系统
WO2016119433A1 (zh) 一种拥塞信息的管理方法和装置
WO2016119439A1 (zh) 一种拥塞信息的管理方法、装置和系统
WO2017024843A1 (zh) 一种传递上下文的方法和装置
US10116457B1 (en) Methods, systems, and computer readable media for usage monitoring
WO2016029674A1 (zh) 接入网拥塞状态上报、拥塞信息的更新处理方法及装置
WO2016029673A1 (zh) 接入网拥塞状态上报、拥塞信息的更新处理方法及装置
WO2015154598A1 (zh) 策略控制方法、装置和系统
CN106686649A (zh) 一种实现拥塞信息处理的方法及装置
JP6212208B2 (ja) Ｒａｎ輻輳ステータスハンドリングのためのノード及び方法
WO2016045420A1 (zh) 用户信息处理方法、装置、系统、pcrf及rcaf
CN116889006A (zh) 通信控制方法、装置及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15879638

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15879638

Country of ref document: EP

Kind code of ref document: A1