WO2011110000A1 - 无线承载丢失信息的上报方法和装置 - Google Patents

无线承载丢失信息的上报方法和装置 Download PDF

Info

Publication number
WO2011110000A1
WO2011110000A1 PCT/CN2010/076194 CN2010076194W WO2011110000A1 WO 2011110000 A1 WO2011110000 A1 WO 2011110000A1 CN 2010076194 W CN2010076194 W CN 2010076194W WO 2011110000 A1 WO2011110000 A1 WO 2011110000A1
Authority
WO
WIPO (PCT)
Prior art keywords
release
request message
cause value
loss information
radio bearer
Prior art date
Application number
PCT/CN2010/076194
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 华为技术有限公司
Priority to ES10847258T priority Critical patent/ES2724174T3/es
Priority to EP18210714.4A priority patent/EP3512240B1/en
Priority to CN2010800060214A priority patent/CN102232301A/zh
Priority to CN201610934314.8A priority patent/CN106488503B/zh
Priority to PCT/CN2010/076194 priority patent/WO2011110000A1/zh
Priority to EP10847258.0A priority patent/EP2574133B1/en
Publication of WO2011110000A1 publication Critical patent/WO2011110000A1/zh
Priority to US13/727,261 priority patent/US9060305B2/en
Priority to US14/720,472 priority patent/US10075865B2/en
Priority to US16/056,140 priority patent/US10812999B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/04—Error control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/26—Resource reservation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and apparatus for reporting loss of radio bearer information. Background technique
  • IP Internet Protocol
  • 3GPP Third Generation Partnership Project
  • PCC Policy and Charging Control
  • Different service flows are detected, and QoS control, billing statistics, and the like are implemented for the service flow.
  • IP-CAN IP-Connectivity Access Network, IP connection
  • IP-CAN bearers Bearers
  • GBR guard bandwidth
  • non-GBR bearers where the default bearer belongs to a non-GBR bearer.
  • GBR carries real-time services that are sensitive to bandwidth, such as VoIP (Voice over Internet Protocol) media streams and video streams.
  • Non-GBR bearers are used for bandwidth-insensitive non-real-time services. And some real-time services that do not require high bandwidth, such as FTP (File Transfer Protocol) download, HTTP (HyperText Transfer Protocol) browsing, email (electronic mail, email), VoIP signaling flow. Wait.
  • FTP File Transfer Protocol
  • HTTP HyperText Transfer Protocol
  • the operator can control the QoS, charging, and the like of the bearer layer data stream through the PCC architecture, thereby shielding the specific details of the transport network from the service layer upward, and perceiving the resource usage of the transport network downward.
  • the Policy and Charging Rule Function (PCRF) formulates a corresponding policy according to the session negotiation information indicated by the service layer, and controls the use of the network resources of the bearer layer.
  • the underlying bearer usage changes, For example, if the user enters the unreachable area, the radio bearer is lost, the gateway is faulty, and so on.
  • the service layer can be notified through the reporting mechanism, so that the service layer can make corresponding changes and provide corresponding policies.
  • the PGW Packet Data Network Gateway, packet
  • the data network gateway notifies the PCRF and AF (Application Function).
  • GBR Guaranteed Bandwidth
  • the release of the non-GBR bearer mechanism affects other services bound to the non-GBR bearer and releases the defect of the IP address release caused by the default bearer.
  • An embodiment of the present invention provides a method and a device for reporting radio bearer loss information, which are used to solve the problem of reporting a radio bearer loss information by releasing a non-GBR bearer after the radio bearer is abnormally released: The service carried by the GBR and the release of the IP address caused by the default bearer release.
  • a method for reporting radio bearer loss information includes: receiving a carrier release reason The user equipment UE context release request message or the release access bearer request message or the lu interface release request message; if the release cause value indicates abnormal release, the radio bearer loss information is reported to the gateway, and the non-guaranteed bandwidth GBR bearer is reserved.
  • the MME includes: a receiving unit, configured to receive a UE context release request message that carries a release cause value sent by an evolved base station eNB, and a reporting unit, configured to: when the release cause value indicates an abnormal release And reporting the radio bearer loss information to the gateway; the processing unit, configured to reserve the non-GBR bearer when the release cause value indicates abnormal release.
  • a serving gateway SGW includes: a receiving unit, configured to receive a release access bearer request message that carries a release cause value sent by the MME, and a reporting unit, configured to: when the release cause value indicates abnormal release, to the PGW The radio bearer loss information is reported; the processing unit is configured to reserve the non-GBR bearer when the release cause value indicates abnormal release.
  • a serving GPRS support node SGSN includes: a receiving unit, configured to receive a lu interface release request message that is sent by a radio network controller RNC and that carries a release cause value; and a reporting unit, configured to indicate an abnormality in the release cause value When released, the radio bearer loss information is reported to the gateway; the processing unit is configured to reserve the non-GBR bearer when the release cause value indicates abnormal release.
  • the method and the device of the embodiment of the invention not only realize the reporting of the loss information of the radio bearer, but also avoid the problem caused by releasing the non-GBR bearer.
  • FIG. 1 is a flowchart of a method for reporting radio bearer loss information according to an embodiment of the present invention
  • FIG. 2 is a flowchart of reporting radio bearer information by an MME according to the method shown in FIG. 1.
  • FIG. 4 is a flowchart of reporting radio bearer information by the SGSN according to the method shown in FIG.
  • FIG. 5 is a flowchart of a method for reporting radio bearer loss information according to another embodiment of the present invention;
  • FIG. 6 is a flowchart of a first embodiment for reporting radio bearer information by an MME according to the method shown in FIG. 5;
  • FIG. 7 is a flowchart of a second embodiment for reporting radio bearer information by an MME according to the method shown in FIG. 5;
  • FIG. 8 is a structural block diagram of an MME according to an embodiment of the present invention.
  • FIG. 9 is a structural block diagram of an SGW according to an embodiment of the present invention.
  • FIG. 10 is a structural block diagram of an SGSN according to an embodiment of the present invention. detailed description
  • FIG. 1 is a flowchart of a method for reporting radio bearer loss information according to an embodiment of the present invention.
  • the method is applied to a network side device, such as an MME (Mobile Management Entity) or an SGW or an SGSN (Service GPRS Supporting Node).
  • Service GPRS General Packet Radio Service
  • the MME or the SGW or the SGSN is responsible for reporting the radio bearer loss information.
  • the method includes:
  • Step 101 Receive a UE context release request message carrying a release cause value or release an access bearer request message or an Iu interface release request message.
  • the radio access network side device for example, the eNB
  • the UE context carrying the release cause value to the network side device (for example, the MME)
  • the request message is released, and the MME is notified that the wireless connection of the UE has been interrupted.
  • the MME performs reporting of radio bearer loss information.
  • the MME does not report the radio bearer loss information, but releases the release reason value to the SGW by releasing the access bearer request message, and the SGW performs wireless The report of the lost information is carried.
  • the radio access network side device for example, the RNC
  • the network side device for example, the SGSN
  • the network side device sends the Iu carrying the release cause value.
  • the interface release request message notifies the SGSN that the wireless connection of the UE has been interrupted.
  • the SGSN performs reporting of the radio bearer loss information.
  • the release cause value is used to indicate the release cause, for example, the loss of the wireless connection with the UE, the management maintenance cause, the UE entering the sleep state, or the integrity check failure with the UE is repeated, etc., when the cause value is released. If the wireless connection is lost between the UE, the management and maintenance reasons, and the integrity check failure between the UE and the UE fail, the device is confirmed to be abnormally released.
  • Step 102 If the release cause value indicates an abnormal release, report the radio bearer loss information to the gateway, and retain all non-GBR bearers.
  • the MME or the SGW or the SGSN After receiving the corresponding message carrying the release cause value, the MME or the SGW or the SGSN determines whether to perform the reporting of the radio bearer loss information according to the release reason value, wherein if the abnormal release is performed, the release cause value is: If any of the wireless connection loss, the reason for the management and maintenance, and the failure of the integrity check with the UE are repeated, the UE reports the radio bearer loss information of the UE, and still retains all non-GBR bearers on the MME or the SGW or the SGSN. .
  • non-GBR services not all services will interrupt the service when the radio bearer is released abnormally.
  • HTTP, FTP, email, P2P peer-to-peer, peer-to-peer
  • P2P peer-to-peer, peer-to-peer
  • one bearer can be bound to multiple services with the same QoS requirements, and if some services are concerned with bearer events, some If the bearer event is not concerned, the release bearer mechanism is adopted, which causes services that do not care about bearer events to be transmitted on the bearer. (Because the bearer has been released), even if these services can tolerate temporary interruptions; in addition, for non-GBR services, attention to bearer events does not necessarily mean that the service must interrupt the service when the radio bearer is abnormally released.
  • the default bearer is a non-GBR bearer
  • the default bearer transmits such a service that needs to be concerned about the bearer event
  • the default bearer is released after the mechanism is released, and the release of the default bearer releases the entire IP-CAN session, including All the bearers are released, and the IP address is released. This will cause the non-GBR bearers that are reserved for the reserved identifiers to be released.
  • the UE needs to re-attach the IP address after resuming the wireless connection. This can result in a large number of signaling interactions, resulting in unnecessary signaling interactions.
  • the reporting method of the radio bearer loss information solves the problem that the current network side device MME/SGSN uses the bearer release mechanism to notify the gateway of the non-GBR bearer after receiving the loss information of the radio bearer, and has the PCC.
  • the gateway notifies the PCRF that the non-GBR bearer is interrupted regardless of whether the service can tolerate the loss of the radio side bearer, and the IP address release caused by the default bearer release needs to be reattached.
  • FIG. 2 is a flowchart of a method for reporting radio bearer loss information by an MME according to the method of the present embodiment.
  • This embodiment is an EPS (Evolved Packet System) system defined by a 3GPP standard organization, and the radio access technology is eUTRAN (evolved type). Access Network).
  • EPS Evolved Packet System
  • eUTRAN evolved type
  • Access Network evolved type
  • Step 201 The eNB detects that a signaling connection and all radio bearers between the UE and the UE (user equipment) need to be released, and then sends a SI UE Context Release Request message to the MME.
  • the UE context release request message carries a release reason value, indicating a release reason, such as a loss of a wireless connection between the UE, a management maintenance cause, a UE entering a sleep state, and a failure of the integrity check between the UEs.
  • a release reason value such as a loss of a wireless connection between the UE, a management maintenance cause, a UE entering a sleep state, and a failure of the integrity check between the UEs.
  • Step 202 The MME receives the UE context release request message, and determines whether to report according to the release reason value. If the abnormal release is performed, the release cause value is: Loss of the wireless connection with the UE, management maintenance reason, complete with the UE If the severity check fails, the radio bearer loss information is reported to the gateway, and all non-GBR bearers are still retained.
  • Step 203 The MME sends a modify bearer request message or a Release Access Bearers Request message to the SGW (the service gateway), where the message carries the UE radio bearer loss information.
  • the radio bearer loss information may be only a general description, that is, the specific release reason is no longer distinguished, and the cause value may be further carried to indicate the specific cause of the radio bearer loss.
  • the radio bearer loss information is for all non-GBR bearers of the UE, not for a specific non-GBR bearer.
  • Step 204 After receiving the modify bearer request message or the access bearer release message, if the message carries the UE radio bearer loss information, the SGW reports the UE radio bearer loss information to the PGW by using a modify bearer request message. (PDN Gateway).
  • the MME completes the reporting of the radio bearer loss information, thereby solving the problem that the current network side device MME uses the bearer release mechanism to notify the gateway to the non-GBR bearer after receiving the radio bearer loss information, and in the case of PCC deployment.
  • the problem that the non-GBR bearer caused by the PCRF is interrupted by the gateway regardless of whether the service can tolerate the loss of the radio side bearer, and the IP address release caused by the default bearer release needs to be reattached.
  • FIG. 3 is a flowchart of the method for reporting the radio bearer loss information by the SGW according to the method in this embodiment.
  • the embodiment is an EPS (Evolved Packet System) system defined by the 3GPP standard organization, and the radio access technology is eUTRAN.
  • EPS Evolved Packet System
  • the process includes:
  • Step 301 The eNB detects that a signaling connection between the UE and the UE (User Equipment) and all radio bearers are required to be released, and then sends an SI UE Context Release Request. Information to the MME;
  • the UE context release request message carries a cause value, indicating a release reason, such as a loss of a wireless connection with the UE, a management maintenance cause, a UE entering a sleep state, and an integrity check failure between the UEs.
  • a release reason such as a loss of a wireless connection with the UE, a management maintenance cause, a UE entering a sleep state, and an integrity check failure between the UEs.
  • Step 302 The MME sends a Release Access Bearers Request message to the SGW (service gateway), where the message carries a release cause value, and the service gateway is required to release the connection between the access network device and the access network device.
  • SGW service gateway
  • Step 303 The SGW receives the release access bearer request message, and determines whether to report according to the release reason value. If the abnormal release, the release cause value is: Loss of the wireless connection with the UE, management and maintenance reasons, and the UE If the integrity check fails repeatedly, the radio bearer loss information is reported to the gateway PGW, and all non-GBR bearers are still retained.
  • Step 304 The SGW sends a modify bearer request message to the PGW (PDN GW), where the message carries the UE radio bearer loss information.
  • PGW GW PGW
  • the radio bearer loss information may be only a general description, that is, the specific release reason is no longer distinguished, and the cause value may be further carried to indicate the specific cause of the radio bearer loss.
  • the radio bearer loss information is For all non-GBR bearers of the UE, not for a specific non-GBR bearer.
  • the SGW completes the reporting of the radio bearer loss information, thereby solving the problem that the current network side device MME uses the bearer release mechanism to notify the gateway to the non-GBR bearer after receiving the radio bearer loss information, and in the case of PCC deployment.
  • the problem that the non-GBR bearer caused by the PCRF is interrupted by the gateway regardless of whether the service can tolerate the loss of the radio side bearer, and the IP address release caused by the default bearer release needs to be reattached.
  • FIG. 4 is a flowchart of a method for reporting radio bearer loss information by the SGSN according to the method of the present embodiment.
  • This embodiment is for GPRS (General Packet Radio) defined by the 3GPP standard organization.
  • GSM EDGE Enhanced Data rate for GSM Evolution, GSM evolution technology for increasing data rates
  • GSM/EDGE Radio Access Network / UTRAN UMTS Terrestrial Radio Access Network
  • GSM Global System for Mobile Communications
  • Step 401 The RNC discovers that the RRC (Radio Resource Control) connection between the UE and the UE has been released or needs to be released or detects that the radio resource between the UE and the UE needs to be released, and then sends an Iu interface release request (Release Request). Message to the SGSN;
  • RRC Radio Resource Control
  • the Iu interface release request message carries a cause of release, such as a loss of a wireless connection with the UE, a management and maintenance cause, a UE entering a dormant state, and a failure to complete the integrity check between the UEs.
  • a cause of release such as a loss of a wireless connection with the UE, a management and maintenance cause, a UE entering a dormant state, and a failure to complete the integrity check between the UEs.
  • the release cause value is: If the wireless connection is lost with the UE, the management maintenance causes, or the integrity check with the UE fails repeatedly, it is confirmed as abnormal release.
  • Step 402 The SGSN receives the Iu interface release request message, and determines whether to report the report according to the release reason value. If the abnormal release is performed, the release cause value is: Loss of the wireless connection with the UE, management maintenance reason, complete with the UE If any of the failovers are repeated, the radio bearer loss information is reported to the gateway GGSN, and all background PDP (Packet Data Protocol) contexts or all interactive PDP contexts or all background classes are retained. And the interaction class PDP context (the background class and the interaction class PDP context are also non-GBR bearers);
  • PDP Packet Data Protocol
  • Step 403 The SGSN sends an Update PDP Context Request message to the GGSN, where the message carries the UE radio bearer loss information.
  • the radio bearer loss information may be only a general description, that is, the specific release reason is no longer distinguished, and the cause value may be further carried to indicate the specific cause of the radio bearer loss.
  • the radio bearer loss information is for all UE-side background PDP contexts or all interactivity class PDP contexts or all background classes and interaction class PDP contexts, rather than for a specific context.
  • the Update PDP Context Request message must specify a PDP Context ID.
  • the PDP context ID is the first context ID, but it does not indicate that the radio bearer loss is only for the first context.
  • the SGSN completes the reporting of the radio bearer loss information, thereby solving the problem that the current network side device SGSN uses the bearer release mechanism to notify the gateway to the non-GBR bearer after receiving the wireless side bearer loss information, and in the case of PCC deployment.
  • the problem that the non-GBR bearer caused by the PCRF is interrupted by the gateway regardless of whether the service can tolerate the loss of the radio side bearer, and the IP address release caused by the default bearer release needs to be reattached.
  • FIG. 5 is a flowchart of a method for reporting radio bearer loss information according to an embodiment of the present invention.
  • the method is also applied to a network side device MME, an SGSN, or an SGW, which is subscribed to a network side device in advance by a PDN gateway PGW or a GGSN. If the radio bearer loses information, the MME or the SGW reports the radio bearer loss information to the PGW, or reports the radio bearer loss information to the GGSN through the SGSN.
  • the content of the embodiment is the same as that of the embodiment shown in FIG. 1. For details, please refer to FIG. 5.
  • the method includes:
  • Step 501 Receive a UE context release request message carrying a release cause value or release an access bearer request message or an Iu interface release request message.
  • the release cause value is used to indicate the release cause, for example, the loss of the wireless connection with the UE, the management maintenance cause, the UE entering the sleep state, or the integrity check failure with the UE is repeated, etc., when the cause value is released. If the wireless connection is lost between the UE, the management and maintenance reasons, and the integrity check failure between the UE and the UE fail, the device is confirmed to be abnormally released.
  • Step 502 Determine whether the PGW or the GGSN subscribes to the radio bearer loss information, and if yes, execute step 503, otherwise, the process ends.
  • the MME or the SGW determines whether the PGW subscribes to the radio bearer loss information, and the SGSN determines whether the GGSN subscribes to the radio bearer loss information.
  • the PCRF may subscribe to the radio bearer loss information to the PDN gateway PGW or the GGSN. After receiving the subscription of the PCRF, the PDN gateway or the GGSN subscribes to the network side device.
  • the network side device in this embodiment may be an MME, an SGSN, or an SGW.
  • Step 503 Determine whether the release cause value is an abnormal release, and if yes, execute step 504, otherwise end;
  • Step 504 Report the UE radio bearer loss information to the gateway, and retain all non-GBR bearers.
  • the gateway is specifically: a PGW or a GGSN.
  • the step 504 reports the radio bearer loss information to the gateway PGW by the MME through the SGW.
  • the step 504 is reported by the SGW to the gateway PGW.
  • the radio bearer loses information; when the method in this embodiment is applied to the SGSN, the step 504 reports the radio bearer loss information to the gateway GGSN by the SGSN.
  • the sequence of the steps 502 and 503 is not limited.
  • the release reason value may be determined first, and then the PGW or the GGSN is subscribed to the radio bearer loss information. This embodiment does not use this embodiment. As a limitation.
  • the method for reporting the radio bearer loss information provided by the embodiment of the present invention, after the PGW or the GGSN subscribes to the radio bearer loss information, reports the information to the PGW or the GGSN, and solves the problem that the current MME/SGSN receives the radio side bearer.
  • the non-GBR bearer is used to notify the gateway of the non-GBR bearer.
  • the gateway notifies the PCRF that the non-GBR bearer is interrupted regardless of whether the service can tolerate the loss of the radio side bearer.
  • the release of the IP address caused by the release of the bearer in the province requires the problem of reattachment.
  • FIG. 6 is a flowchart of one embodiment of an MME determining whether to report according to a radio bearer loss information reporting request of a PGW.
  • This embodiment is an EPS (Evolved Packet System) system defined by a 3GPP standard organization, and is connected to the wireless device.
  • the incoming technology is eUTRAN. Please refer to Figure 6.
  • the process includes:
  • Steps 601-602 The PCRF subscribes to the radio bearer loss information to the PGW, where the PGW includes a PCEF (Policy and Charging Enforcement Function), and in this embodiment, if not specified, the PGW refers to An entity containing a PCEF;
  • the information value may reuse the currently defined LOSS_OF_BEARER information, or newly define a message dedicated to the radio bearer loss, the information may be for the entire IP-CAN session, or for a specific rule, this embodiment This is not a limitation.
  • Step 603 After receiving the request for the subscription of the radio bearer loss information of the PCRF, the PGW sends an update bearer reques message to the SGW, and requests the MME to report the information to the PGW after detecting that the wireless bearer is lost.
  • the PGW can still select
  • the request for the radio bearer loss to the MME is for all non-GBR bearers, and may also choose to request the MME to be responsible for the radio bearer loss for a specific non-GBR bearer, and the specific non-GBR bearers are bound to the PCC mle described above.
  • Step 604-606 The SGW sends an update bearer request message to the MME, and requests the MME to report the information after detecting that the radio bearer is lost.
  • Step 607 The eNB detects that a signaling connection and all radio bearers between the UE and the UE (user equipment) need to be released, and then sends a SI UE Context Release Request message to the MME.
  • the message carries a release cause value, indicating a release reason, such as a loss of a wireless connection with the UE, a management maintenance cause, a UE entering a sleep state, and an integrity check failure between the UEs.
  • a release cause value is: If the wireless connection is lost with the UE, the management maintenance cause, or the integrity check with the UE fails repeatedly, it is confirmed as an abnormal release.
  • Step 608 The MME receives the UE context release request message, and first determines whether the PGW subscribes to the radio bearer loss information, and then determines whether to report the packet according to the release reason value. If the PGW requests the MME to report the radio bearer loss information, and the release cause value is abnormal. Release, ie release cause value: Loss of wireless connection with UE, management and maintenance reasons, integrity check with UE The MME reports the radio bearer loss information to the gateway PGW through the SGW, and still retains all non-GBR bearers;
  • Step 609 The MME sends a Modify Bearer Request message or a Release Access Bearers Request message to the SGW (Service Gateway), where the message carries the UE radio bearer loss information.
  • SGW Service Gateway
  • the radio bearer loss information may be only a general description, that is, the specific release reason is no longer distinguished, and the cause value may be further carried to indicate the specific cause of the radio bearer loss.
  • the radio bearer loss information may be for all non-GBR bearers of the UE, or may be for a specific non-GBR bearer.
  • Step 610 After receiving the modify bearer request message or releasing the access bearer request message, if the message carries the UE radio bearer loss information, the SGW notifies the PGW of the radio bearer loss information by modifying the bearer request message.
  • PDN gateway PDN gateway
  • Step 611 After receiving the modify bearer request message, the PGW reports the radio bearer loss information to the PCRF through a CCR (Credit Control Request) message, and if it is for a specific PCC mle (rule), passes the CCR message.
  • the parameter Charging-Rule-Report reports the affected rules;
  • Step 612 After receiving the radio bearer loss information, the PCRF may notify the AF bottom layer transmission interruption. If some services cannot be performed because the radio bearer is lost, the PCRF may notify the PGW to correspond to the services by using a CCA (Credit Control Answer) message.
  • the PCC rule is deleted. Specifically, the PGW can be used to notify the PGW to delete these PCC rules by using the parameter Charging-Rule-Remove in the CCA message.
  • Step 613 If the PCRF requests to release some PCC rules, the PGW may initiate some bearer operations according to the new bearer binding result, for example, update some bearers, if all the rules of a non-default bearer are released. , you can also initiate a bearer release operation.
  • the embodiment only describes the PGW to subscribe to the MME, the same applies to the PGW requesting the SGW to report the radio bearer loss information (refer to the embodiment shown in FIG. 3).
  • the SGW notifies the PGW when the radio bearer is abnormally released according to the request of the PGW.
  • the embodiment is also applicable to the GGSN requesting the SGSN to report the radio bearer loss information (refer to the embodiment shown in FIG. 4), and the SGSN notifies the GGSN when the radio bearer is abnormally released according to the request of the GGSN, for the sake of simplicity, here. No longer.
  • the MME can decide whether to report according to the PGW's subscription request (the subscription request can be initiated by the PCRF).
  • FIG. 7 is a flowchart of another embodiment of the MME determining whether to report according to the radio bearer loss information reporting request of the PGW.
  • the embodiment is an EPS (Evolved Packet System) system defined by the 3GPP standard organization, and the radio access technology is eUTRAN.
  • the PMG Proxy Mobile IP
  • GTP GPRS Tunneling Protocol
  • the PGW cannot.
  • the bearer binding cannot be performed by the MME to perform the radio bearer loss reporting by the PMIP protocol.
  • the SGW including the BBERF (Bearing Binding and Event Report Function).
  • the process includes:
  • Step 701-702 The PCRF subscribes to the radio bearer loss information to the SGW.
  • the SGW refers to an entity that includes the BBERF.
  • the information value may reuse the currently defined LOSS_OF_BEARER information, or newly define a message dedicated to the radio bearer loss, the information may be for the entire IPCAN session, or for a specific rule, this embodiment does not This is used as a limitation.
  • Step 703-704 After receiving the request for the subscription of the radio bearer loss information of the PCRF, the SGW sends an update bearer request message to the MME, and requests the MME to report the information to the PCEF after detecting the loss of the wireless bearer;
  • the MME is requested to request that the radio bearer loss is for all non-GBR bearers; if the radio bearer loss information of the PCRF subscription is for some QoS rules, the SGW can still select Request wireless inheritance from the MME
  • the bearer loss is for all non-GBR bearers, and may also choose to request the MME to be responsible for the radio bearer loss for a specific non-GBR bearer. These specific non-GBR bearers are bound to the above QoS mle.
  • Step 705 The eNB detects that a signaling connection and all radio bearers between the UE and the UE (user equipment) need to be released, and then sends a SI UE Context Release Request message to the MME.
  • the message carries the cause value, indicating the reason for the release, such as the loss of the wireless connection with the UE, the reason for managing the maintenance, the UE entering the dormant state, and the failure of the integrity check between the UEs.
  • the release cause value is: If the wireless connection is lost with the UE, the management maintenance cause, or the integrity check with the UE fails repeatedly, it is confirmed as abnormal release.
  • Step 706 The MME receives the UE context release request message, and first determines whether the PGW subscribes to the radio bearer loss information, and then determines whether to report the packet according to the release reason value. If the SGW requests the MME to report the radio bearer loss information, the release cause value is abnormal. Release, that is, the release cause value is non-user entering the user state (user inactivity), the MME notifies the gateway of the radio bearer loss information, and still retains all non-GBR bearers;
  • Step 707 The MME sends a Modify Bearer Request message or a Release Access Bearers Request message to the SGW (Service Gateway).
  • the message carries the UE radio bearer loss information.
  • the radio bearer loss information can be only a general description, that is, the specific release reason is no longer distinguished, and the cause value can be further carried to indicate the specific cause of the radio bearer loss.
  • the radio bearer loss information may be for all non-GBR bearers of the UE, or may be for a specific non-GBR bearer.
  • Step 708 After receiving the modify bearer request message, the SGW reports the radio bearer loss information to the PCRF through a CCR (Credit Control Request) message. If it is for a specific QoS rule, the parameter QOS- in the CCR message is adopted. Rule-Report reports the affected rules;
  • Step 709 After receiving the radio bearer loss information, the PCRF may notify the AF bottom layer transmission If the service fails due to the loss of the radio bearer, the PCRF can use the CCA (Credit Control Answer) message to notify the SGW to delete the PCC rule and the Qos rule corresponding to these services.
  • the parameter in the CCA message is Charging-Rule- Remove (accounting rule removal) to notify the SGW to delete these PCC rules and Qos rule;
  • Step 710 If the PCRF requests to release (that is, delete) certain QoS rules, the SGW may optionally initiate some bearer operations according to the new bearer binding result, such as updating some bearers, if a non-default bearer is all The rules are released, and the bearer release operation (which cannot be released for the default bearer) can also be initiated;
  • Steps 711-712 The PCRF requires the PGW (including PCEF) to delete the PCC mle.
  • the MME can decide whether to report according to the subscription request of the SGW (the subscription request can be initiated by the PCRF).
  • the reporting method of the radio bearer loss information solves the problem that the current MME uses the bearer release mechanism to notify the gateway of the non-GBR bearer after receiving the bearer loss information of the radio side, and in the case of PCC deployment, The gateway notifies the PCRF that the non-GBR bearer is interrupted regardless of whether the service can tolerate the loss of the radio side bearer, and the IP address release caused by the default bearer release needs to be reattached.
  • FIG. 8 is a structural block diagram of a mobility management entity MME according to an embodiment of the present invention.
  • the MME includes:
  • the receiving unit 81 is configured to receive a UE context release message that carries the release cause value sent by the evolved base station eNB.
  • the release cause value is used to indicate the release cause, for example, the loss of the wireless connection with the UE, the management maintenance cause, the UE entering the sleep state, or the integrity check failure with the UE is repeated, etc., when the cause value is released. If the wireless connection is lost between the UE, the management and maintenance reasons, and the integrity check failure between the UE and the UE fail, the device is confirmed to be abnormally released.
  • the reporting unit 82 is configured to report the radio bearer loss information to the gateway PGW by using the SGW when the release cause value indicates an abnormal release.
  • the processing unit 83 is configured to reserve all non-GBR bearers when the release cause value indicates an abnormal release.
  • the UE context release request message carrying the release cause value is sent to the network side device (for example, the MME) when the radio access network side device (for example, the eNB) detects that the radio signaling connection of the UE and all the radio bearers need to be released.
  • the MME is notified that the wireless connection of the UE has been interrupted.
  • the MME determines whether to perform the reporting of the radio bearer loss information according to the release cause value, where if the abnormal release, the release cause value is:
  • the SGW notifies the PGW of the radio bearer loss information of the UE, while still retaining all non-GBR bearers on the MME.
  • the reporting unit 82 is specifically configured to send a modify bearer request message carrying the radio bearer loss information or release the access bearer request message to the SGW, to send a modify bearer request carrying the radio bearer loss information to the PGW by using the SGW. Message.
  • the MME may further include:
  • the determining unit 84 is configured to determine, after the receiving unit 81 receives the UE context release message carrying the release cause value sent by the evolved base station eNB, whether the PGW subscribes to the radio bearer loss information, and if the PGW subscribes to the radio bearer loss information, It is judged whether the release cause value is an abnormal release, and the result of the judgment is supplied to the reporting unit 82 and the processing unit 83.
  • the components of the MME in this embodiment are respectively used to implement the steps of the method in the embodiment shown in FIG. 2. Since the steps in the embodiment shown in FIG. 2 have been described in detail, the steps are not described here. Let me repeat.
  • the MME provided by the embodiment of the present invention solves the problem that the current MME uses the bearer release mechanism to notify the gateway of the non-GBR bearer after receiving the loss information of the radio side bearer, and in response to the PCRF, the gateway notifies the PCRF. Whether the service is tolerable on non-GBR bearers The loss of the wireless side bearer will be interrupted, and the IP address release caused by the default bearer release needs to be reattached.
  • FIG. 9 is a structural block diagram of a serving gateway SGW according to an embodiment of the present invention.
  • the SGW includes:
  • the receiving unit 91 is configured to receive a release access bearer request message that is sent by the MME and that carries a release cause value.
  • the release cause value is used to indicate the release cause, for example, the loss of the wireless connection with the UE, the management maintenance cause, the UE entering the sleep state, or the integrity check failure with the UE is repeated, etc., when the cause value is released. If the wireless connection is lost between the UE, the management and maintenance reasons, and the integrity check failure between the UE and the UE fail, the device is confirmed to be abnormally released.
  • the reporting unit 92 is configured to notify the PGW of the wireless bearer loss information when the release cause value indicates an abnormal release
  • the processing unit 93 is configured to reserve all non-GBR bearers when the release cause value indicates an abnormal release.
  • the MME After receiving the corresponding UE context release message carrying the release cause value, the MME does not report the radio bearer loss information, but releases the access cause request message to the SGW by releasing the access bearer request message, and the SGW performs wireless The report of the lost information is carried.
  • the SGW After receiving the corresponding release access bearer request message carrying the release cause value, the SGW determines whether to perform the report of the radio bearer loss information according to the release cause value, where if the abnormal release, the release cause value is: When any one of the loss of the wireless connection, the management maintenance cause, and the integrity check failure between the UE and the UE fail, the PGW is notified of the radio bearer loss information of the UE, while all non-GBR bearers are still reserved on the SGW.
  • the reporting unit 92 is specifically configured to send a modify bearer request message carrying the radio bearer loss information to the PGW.
  • the SGW further includes:
  • the determining unit 94 is configured to receive, by the receiving unit 91, a carry release cause value sent by the MME After releasing the access bearer request message, determining whether the PGW subscribes to the radio bearer loss information, if the PGW subscribes to the radio bearer loss information, it is determined that the release cause value release is abnormal release, and the result of the judgment is provided.
  • the reporting unit 92 and the processing unit 93 are provided.
  • the components of the SGW of this embodiment are respectively used to implement the steps of the method of the embodiment shown in FIG. 3. Since the steps in the embodiment shown in FIG. 3 have been described in detail, the steps are not described here. Let me repeat.
  • the SGW provided by the embodiment of the present invention solves the problem that the current MME uses the bearer release mechanism to notify the gateway of the non-GBR bearer after receiving the loss information of the radio side bearer, and notifys the PCRF by the gateway when the PCC is deployed.
  • the non-GBR bearer will be interrupted regardless of whether the service can tolerate loss of the radio side bearer, and the IP address release caused by the default bearer release needs to be reattached.
  • FIG. 10 is a schematic structural diagram of a serving GPRS support node SGSN according to an embodiment of the present invention.
  • the SGSN includes:
  • the receiving unit 1001 is configured to receive an Iu interface release request message that is sent by the radio network controller RNC and that carries a release cause value.
  • the release cause value is used to indicate the release cause, for example, the loss of the wireless connection with the UE, the management maintenance cause, the UE entering the sleep state, or the integrity check failure with the UE is repeated, etc., when the cause value is released. If the wireless connection is lost between the UE, the management and maintenance reasons, and the integrity check failure between the UE and the UE fail, the device is confirmed to be abnormally released.
  • the reporting unit 1002 is configured to notify the gateway of the wireless bearer loss information when the release cause value indicates an abnormal release
  • the processing unit 1003 is configured to reserve all non-GBR bearers when the release cause value indicates an abnormal release.
  • the radio access network side device for example, the RNC
  • the radio access network side device detects that the radio signaling connection of the UE and all the radio bearers need to be released
  • the Iu interface carrying the release cause value is sent to the network side device (for example, the SGSN). Release the request message to inform the SGSN that the UE's wireless connection has been Interrupted.
  • the SGSN performs reporting of the radio bearer loss information.
  • the SGSN After receiving the corresponding Iu interface release request message carrying the release cause value, the SGSN determines whether to perform the report of the radio bearer loss information according to the release cause value, where if the abnormal release, the release cause value is: If any of the wireless connection is lost, the management and maintenance reasons, and the integrity check failure between the UE and the UE are repeated, the GGSN is notified of the radio bearer loss information of the UE, and all non-GBR bearers are still reserved on the SGSN.
  • the reporting unit 1002 is specifically configured to send an update PDP context request message carrying the radio bearer loss information to the gateway GPRS support node GGSN.
  • the SGSN may further include:
  • the determining unit 1004 is configured to determine, after the receiving unit 1001 receives the Iu interface release request message that carries the release cause value sent by the radio network controller RNC, whether the GGSN subscribes to the radio bearer loss information, if the GGSN subscribes to the radio bearer loss information. And determining whether the release cause value is an abnormal release, and providing the result of the judgment to the reporting unit 1002 and the processing unit 1003.
  • the components of the SGSN of this embodiment are respectively used to implement the steps of the method of the embodiment shown in FIG. 4. Since the steps in the embodiment shown in FIG. 4 have been described in detail, the steps are not described here. Let me repeat.
  • the SGSN provided by the embodiment of the present invention solves the problem that the current GGSN uses the bearer release mechanism to notify the gateway of the non-GBR bearer after receiving the bearer information of the radio side, and in the case of PCC deployment, the gateway notifies the PCRF.
  • the non-GBR bearer will be interrupted regardless of whether the service can tolerate loss of the radio side bearer, and the IP address release caused by the default bearer release needs to be reattached.
  • RAM random access memory
  • ROM read only memory
  • electrically programmable ROM electrically erasable A ROM
  • register a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明实施例提供了一种无线承载丢失信息的上报方法，所述方法包括：接收携带释放原因值的用户设备UE上下文释放请求消息或者释放接入承载请求消息或者Iu接口释放请求消息；如果所述释放原因值指示异常释放，则向网关上报无线承载丢失信息，并保留非保证带宽GBR承载。通过本发明实施例的方法和装置，既实现了承载上报，又避免了因为释放非GBR承载引起的问题。

Description

无线承载丟失信息的上报方法和装置
技术领域
本发明涉及通信领域， 尤其涉及一种无线承载丢失信息的上报方法和装 置。 背景技术
下一代通信网的承载已经全面开始换用 IP (Internet Protocol, 网络互连 协议）。 从通信网的发展来看， 经历了从传统电路交换网到控制承载分离的 IP包交换网络再到全 IP的多媒体网络这样一个演进过程。在向全 IP网络演 进过程中， 需要考虑端到端 QoS ( Quality of Service, 服务质量） 问题， 以 提供令客户满意的业务 （特别是实时类业务）。 因为 IP网络可以提供更多种 类的业务 （如多媒体呼叫， 文件下载， 网页浏览等）， 所以需要网络能够检 测不同的业务流并统计流量、 时长等计费信息以上报给计费中心。 为了解决 上述 QoS 和基于流计费等相关问题， 3GPP ( Third Generation Partnership Project, 第三代合作伙伴计划） 定义了 PCC (Policy and Charging Control , 策略和计费控制）架构， 通过该架构可以使得网络检测到不同的业务流， 并 针对业务流实现 QoS控制， 计费统计等需求。
在 PCC架构中，当 UE ( User Equipment，用户设备）在 PDN ( Public Data Network, 公用数据网） 分配了可寻址的 IP 地址后， UE 就建立 IP-CAN (IP-Connectivity Access Network, IP连接接入网络） 会话， 为了满足不同 的 QoS要求，在同一个 IP-CAN会话里可以建立不同 QoS要求的 IP-CAN承 载（Bearer) , 对于 IP-CAN承载， 可以分为 GBR (保证带宽）承载和非 GBR 承载， 其中缺省承载属于非 GBR承载。 一般情况下， GBR承载用于对带宽 敏感的实时业务， 如 VoIP (Voice over Internet Protocol, 互联网协议语音电 话） 的媒体流、 视频流等； 而非 GBR承载用于对带宽不敏感的非实时业务 以及一些对带宽要求不高的实时业务， 如 FTP (File Transfer Protocol, 文件 传输协议） 下载、 HTTP (HyperText Transfer Protocol, 超文本传输协议） 浏 览、 email (electronic mail, 电子邮件）、 VoIP信令流等。
目前， 运营商通过 PCC架构可以很好的实现对承载层数据流的 QoS、 计费等的控制， 从而实现向上向业务层屏蔽传送网络的具体细节， 向下感知 传送网络的资源使用情况。一方面 PCRF (Policy and Charging Rule Function, 策略和计费规则功能）根据业务层指示的会话协商信息制订相应的策略， 控 制承载层网络资源的使用；另一方面当底层承载使用情况发生变化时，例如， 用户进入不可覆盖区导致无线承载丢失、 网关故障等， 可以通过上报机制通 知业务层， 以便业务层作相应更改、 提供对应的策略。
然而， 现有技术中， 当 eNB (eNodeB, 演进型基站）需要释放和 UE之 间的信令连接和所有无线承载时， 是通过释放承载的机制通知 PGW (PDN Gateway, Packet Data Network Gateway,分组数据网络网关），进而通知 PCRF 和 AF( Application Function,应用功能）的。对于 GBR( Guaranteed bandwidth, 保证带宽）承载来说， 由于传输的基本是实时业务， 对于这种异常释放无线 承载， 即使时间很短， 也很有可能导致业务中断， 所以释放 GBR承载是合 理的， 但对于非 GBR承载来说， 采用释放非 GBR承载机制， 会影响其他绑 定在该非 GBR承载的业务， 以及释放缺省承载引起的 IP地址释放的缺陷。 发明内容
本发明实施例提供一种无线承载丢失信息的上报方法和装置， 以解决当 无线承载异常释放后， 通过释放非 GBR承载来实现无线承载丢失信息的上 报机制导致的： 影响其他绑定在该非 GBR承载的业务以及释放缺省承载引 起的 IP地址释放的问题。
本发明实施例的上述目的是通过如下技术方案实现的：
—种无线承载丢失信息的上报方法， 所述方法包括： 接收携带释放原因 值的用户设备 UE上下文释放请求消息或者释放接入承载请求消息或者 lu接 口释放请求消息； 如果所述释放原因值指示异常释放， 则向网关上报无线承 载丢失信息， 并保留非保证带宽 GBR承载。
一种移动管理实体 MME, 所述 MME包括： 接收单元， 用于接收演进 型基站 eNB发送的携带释放原因值的 UE上下文释放请求消息； 上报单元， 用于在所述释放原因值指示异常释放时， 向网关上报无线承载丢失信息； 处 理单元， 用于在所述释放原因值指示异常释放时， 保留非 GBR承载。
一种服务网关 SGW, 所述 SGW包括： 接收单元， 用于接收 MME发送 的携带释放原因值的释放接入承载请求消息； 上报单元， 用于在所述释放原 因值指示异常释放时， 向 PGW上报无线承载丢失信息； 处理单元， 用于在 所述释放原因值指示异常释放时， 保留非 GBR承载。
一种服务 GPRS支持节点 SGSN, 所述 SGSN包括： 接收单元， 用于接 收无线网络控制器 RNC发送的携带释放原因值的 lu接口释放请求消息； 上 报单元， 用于在所述释放原因值指示异常释放时， 向网关上报无线承载丢失 信息； 处理单元， 用于在所述释放原因值指示异常释放时， 保留非 GBR承 载。
通过本发明实施例的方法和装置， 既实现了无线承载丢失信息的上报， 又避免了因为释放非 GBR承载引起的问题。 附图说明
此处所说明的附图用来提供对本发明的进一歩理解， 构成本申请的一部 分， 并不构成对本发明的限定。 在附图中：
图 1为本发明实施例的无线承载丢失信息的上报方法的流程图； 图 2为根据图 1所示的方法由 MME上报无线承载信息的流程图； 图 3为根据图 1所示的方法由 SGW上报无线承载信息的流程图； 图 4为根据图 1所示的方法由 SGSN上报无线承载信息的流程图； 图 5为本发明另一实施例的无线承载丢失信息的上报方法的流程图； 图 6为根据图 5所示的方法由 MME上报无线承载信息的第一实施方式 的流程图；
图 7为根据图 5所示的方法由 MME上报无线承载信息的第二实施方式 的流程图；
图 8为本发明实施例提供的 MME的组成框图；
图 9为本发明实施例提供的 SGW的组成框图；
图 10为本发明实施例提供的 SGSN的组成框图。 具体实施方式
为使本发明实施例的目的、 技术方案和优点更加清楚明白， 下面结合实 施例和附图， 对本发明实施例做进一歩详细说明。 在此， 本发明的示意性实 施例及其说明用于解释本发明， 但并不作为对本发明的限定。
图 1 为本发明实施例提供的一种无线承载丢失信息的上报方法的流程 图， 该方法应用于网络侧设备， 例如 MME (Mobile Management Entity, 移 动管理实体） 或者 SGW或者 SGSN ( Service GPRS Supporting Node, 服务 GPRS ( General Packet Radio Service , 通用分组无线服务技术） 支持节点）， 由 MME或者 SGW或者 SGSN负责无线承载丢失信息的上报， 请参照图 1， 该方法包括：
歩骤 101 : 接收携带释放原因值的 UE上下文释放请求消息或者释放接 入承载请求消息或者 Iu接口释放请求消息；
在一个实施例中， 当无线接入网侧设备 （例如 eNB) 检测到需要释放 UE的无线信令连接以及所有无线承载时， 则向网络侧设备（例如 MME)发 送携带释放原因值的 UE上下文释放请求消息， 通知 MME该 UE的无线连 接已经中断。 此时， 该 MME在接收到该 UE上下文释放请求消息后， 进行 无线承载丢失信息的上报。 在另外一个实施例中， MME在接收到该 UE上下文释放请求消息后， 不进行无线承载丢失信息的上报， 而是通过释放接入承载请求消息将释放原 因值转发给 SGW, 由该 SGW进行无线承载丢失信息的上报。
在另外一个实施例中， 当无线接入网侧设备 （例如 RNC) 检测到需要 释放 UE的无线信令连接以及所有无线承载时，则向网络侧设备（例如 SGSN) 发送携带释放原因值的 Iu接口释放请求消息，通知 SGSN该 UE的无线连接 已经中断。 此时， 该 SGSN在接收到该 Iu接口释放请求消息后， 进行无线 承载丢失信息的上报。
其中， 释放原因值用于指示释放原因， 例如可以为： 与 UE之间失去无 线连接， 管理维护原因， UE进入休眠状态， 或者与 UE之间的完整性检查 重复失败等等， 当释放原因值为： 与 UE之间失去无线连接， 管理维护原因， 与 UE之间的完整性检查重复失败等任意一项时， 则确认为异常释放。
歩骤 102: 如果所述释放原因值指示异常释放， 则向网关上报无线承载 丢失信息， 并保留所有非 GBR承载。
其中， MME或者 SGW或者 SGSN在接收到对应的携带释放原因值的 消息后， 根据释放原因值决定是否进行无线承载丢失信息的上报， 其中， 如 果是异常释放， 即释放原因值为： 与 UE之间失去无线连接， 管理维护原因， 与 UE之间的完整性检查重复失败等任意一项时， 则向网关上报 UE的无线 承载丢失信息，同时仍在 MME或者 SGW或者 SGSN上保留所有非 GBR承 载。
对于非 GBR业务来说， 并不是所有业务在异常释放无线承载时， 都会 中断业务的， 比如像 HTTP、 FTP, email、 P2P (peer-to-peer, 点对点）等是 能够容忍短时间传输中断的， 特别是针对 UE临时进入不可覆盖区后又恢复 无线连接的情况， 根据目前的承载绑定机制看， 一个承载可以绑定多个 QoS 要求相同的业务， 如果有的业务关注承载事件， 有的不关注承载事件， 则采 用释放承载机制，会导致那些不关注承载事件的业务也无法在该承载上传输 (因为承载已经释放了），即使这些业务可以忍受临时中断;另外对于非 GBR 业务来说， 关注承载事件不一定意味着业务在无线承载异常释放时， 一定要 中断业务。
因为缺省承载是非 GBR承载， 如果缺省承载传输了这种需要关注承载 事件的业务， 则采用这种机制后， 会释放缺省承载， 而释放缺省承载会释放 整个 IP-CAN会话， 包括所有承载， 释放 IP地址， 这会导致对于那些预留标 识为预留的非 GBR承载也会释放， 另外释放 IP地址后， 当 UE重新恢复无 线连接后， 需要重新进行附着流程， 分配 IP地址， 这会导致大量的信令交 互， 造成不必要的信令交互。
通过本发明实施例提供的无线承载丢失信息的上报方法，解决了目前网 络侧设备 MME/SGSN在收到无线侧承载丢失信息后，对非 GBR承载采用承 载释放机制来通知网关， 并在有 PCC部署情况下， 由网关通知 PCRF所导 致的非 GBR承载上无论该业务是否可忍受无线侧承载丢失都会中断， 以及 缺省承载释放导致的 IP地址释放， 需要重新附着的问题。
为使图 1所示实施例的方法更加清楚易懂， 以下结合图 2—图 4所示的 流程对本实施例的方法进行详细说明。
图 2为根据本实施例的方法， 由 MME负责无线承载丢失信息的上报的 流程图， 本实施例是针对 3GPP 标准组织定义的 EPS ( Evolved Packet System) 系统， 无线接入技术为 eUTRAN (演进型接入网）。 请参照图 2， 该流程包括：
歩骤 201 : eNB检测到需要释放和 UE (用户设备） 之间的信令连接和 所有无线承载， 则发送 SI UE Context Release Request (上下文释放请求）消 息给 MME;
其中， 该 UE上下文释放请求消息中携带释放原因值， 指示释放原因， 比如和 UE之间失去无线连接、 管理维护原因、 UE进入休眠状态、 以及 UE 之间的完整性检查重复失败等。当释放原因值为：与 UE之间失去无线连接， 管理维护原因， 或者与 UE之间的完整性检查重复失败时， 则确认为异常释 放。
歩骤 202: MME收到 UE上下文释放请求消息，根据释放原因值决定是 否上报， 如果是异常释放， 即释放原因值为： 与 UE之间失去无线连接， 管 理维护原因， 与 UE之间的完整性检查重复失败等任意一项时， 则向网关上 报无线承载丢失信息， 同时仍保留所有的非 GBR承载；
歩骤 203: MME向 SGW (服务网关）发送修改承载请求（ modify Bearer request)消息或者释方夂接入承载请求 (Release Access Bearers Request)消息， 该消息中携带 UE无线承载丢失信息；
其中， 无线承载丢失信息可以只是一个通用的描述， 即不再区分具体的 释放原因， 也可以进一歩携带原因值， 指明无线承载丢失的具体原因。 在本 实施里， 这个无线承载丢失信息是针对该 UE所有非 GBR承载的， 而不是 针对一个特定的非 GBR承载。
歩骤 204: SGW收到修改承载请求消息或者接入承载释放消息后，如果 消息里携带有 UE无线承载丢失信息， 则通过修改承载请求 （modify Bearer request) 消息将 UE无线承载丢失信息上报给 PGW (PDN网关）。
至此， MME完成了无线承载丢失信息的上报， 由此解决了目前网络侧 设备 MME在收到无线侧承载丢失信息后， 对非 GBR承载采用承载释放机 制来通知网关，并在有 PCC部署情况下，由网关通知 PCRF所导致的非 GBR 承载上无论该业务是否可忍受无线侧承载丢失都会中断， 以及缺省承载释放 导致的 IP地址释放， 需要重新附着的问题。
图 3为根据本实施例的方法， 由 SGW负责无线承载丢失信息的上报的 流程图， 本实施例是针对 3GPP 标准组织定义的 EPS ( Evolved Packet System) 系统， 无线接入技术为 eUTRAN。 请参照图 3， 该流程包括：
歩骤 301 : eNB检测到需要释放和 UE (用户设备） 之间的信令连接和 所有无线承载， 则发送 SI UE Context Release Request (上下文释放请求）消 息给 MME;
其中， 该 UE上下文释放请求消息中携带原因值， 指示释放原因， 比如 和 UE之间失去无线连接、 管理维护原因、 UE进入休眠状态、 以及 UE之间 的完整性检查重复失败等。 当释放原因值为： 与 UE之间失去无线连接， 管 理维护原因，或者与 UE之间的完整性检查重复失败时，则确认为异常释放。
歩骤 302: MME向 SGW (服务网关） 发送释放接入承载请求 （Release Access Bearers Request) 消息， 该消息中携带释放原因值 (cause), 要求服 务网关释放和接入网设备之间的连接；
歩骤 303: SGW收到释放接入承载请求消息，根据释放原因值决定是否 上报， 如果是异常释放， 即释放原因值为： 与 UE之间失去无线连接， 管理 维护原因，与 UE之间的完整性检查重复失败等任意一项时，则向网关 PGW 上报无线承载丢失信息， 同时仍保留所有的非 GBR承载；
歩骤 304: SGW向 PGW (PDN GW)发送修改承载请求（ modify Bearer request) 消息， 该消息中携带 UE无线承载丢失信息。
其中， 该无线承载丢失信息可以只是一个通用的描述， 即不再区分具体 的释放原因， 也可以进一歩携带原因值， 指明无线承载丢失的具体原因； 在 本实施里， 这个无线承载丢失信息是针对该 UE所有非 GBR承载的， 而不 是针对一个特定的非 GBR承载。
至此， SGW完成了无线承载丢失信息的上报， 由此解决了目前网络侧 设备 MME在收到无线侧承载丢失信息后， 对非 GBR承载采用承载释放机 制来通知网关，并在有 PCC部署情况下，由网关通知 PCRF所导致的非 GBR 承载上无论该业务是否可忍受无线侧承载丢失都会中断， 以及缺省承载释放 导致的 IP地址释放， 需要重新附着的问题。
图 4为根据本实施例的方法， 由 SGSN负责无线承载丢失信息的上报的 流程图，本实施例是针对 3GPP标准组织定义的 GPRS (General Packet Radio
Service)系统，无线接入技术为 GERAN (GSM EDGE (Enhanced Data rate for GSM Evolution, 提高数据速率的 GSM演进技术） Radio Access Network, GSM/EDGE无线接入网） /UTRAN ( UMTS Terrestrial Radio Access Network ， UMTS 陆地无线接入网） /GSM (Global System for Mobile Communications , 全球移动通讯系统）。 请参照图 4， 该流程包括：
歩骤 401 : RNC发现和 UE之间的 RRC (Radio Resource Control, 无线 资源控制） 连接已经释放或者需要释放或者检测到需要释放和 UE之间的无 线资源， 则发送 Iu接口释放请求 （Release Request) 消息给 SGSN;
其中， 该 Iu接口释放请求消息中携带释放原因值 （cause), 比如和 UE 之间失去无线连接、 管理维护原因、 UE进入休眠状态、 和 UE之间的完整 性检查重复失败等。 当释放原因值为： 与 UE之间失去无线连接， 管理维护 原因， 或者与 UE之间的完整性检查重复失败时， 则确认为异常释放。
歩骤 402: SGSN收到 Iu接口释放请求消息， 根据释放原因值决定是否 上报， 如果是异常释放， 即释放原因值为： 与 UE之间失去无线连接， 管理 维护原因，与 UE之间的完整性检查重复失败等任意一项时，则向网关 GGSN 上报无线承载丢失信息， 同时仍保留所有的后台类 PDP ( Packet Data Protocol, 分组数据协议） 上下文或者所有的交互类 PDP上下文或者所有的 后台类和交互类 PDP上下文 （后台类和交互类 PDP上下文也是非 GBR承 载)；
歩骤 403: SGSN向 GGSN发送更新 PDP上下文请求（Update PDP Context Request) 消息， 该消息中携带 UE无线承载丢失信息。
其中， 无线承载丢失信息可以只是一个通用的描述， 即不再区分具体的 释放原因， 也可以进一歩携带原因值， 指明无线承载丢失的具体原因。 在本 实施里，这个无线承载丢失信息是针对该 UE所有的后台类 PDP上下文或者 所有的交互类 PDP上下文或者所有的后台类和交互类 PDP上下文， 而不是 针对一个特定的上下文。
根据现有标准，更新 PDP上下文请求消息必须指定一个 PDP上下文 ID, 在本实例里， 该 PDP上下文 ID为首次上下文 ID,但不是表明无线承载丢失 仅是针对首次上下文的。
至此， SGSN完成了无线承载丢失信息的上报， 由此解决了目前网络侧 设备 SGSN在收到无线侧承载丢失信息后， 对非 GBR承载采用承载释放机 制来通知网关，并在有 PCC部署情况下，由网关通知 PCRF所导致的非 GBR 承载上无论该业务是否可忍受无线侧承载丢失都会中断， 以及缺省承载释放 导致的 IP地址释放， 需要重新附着的问题。
图 5 为本发明实施例提供的一种无线承载丢失信息的上报方法的流程 图， 该方法也应用于网络侧设备 MME、 SGSN或者 SGW， 其是在 PDN网 关 PGW或者 GGSN预先向网络侧设备订阅无线承载丢失信息的情况下， 通 过 MME或者 SGW向 PGW上报无线承载丢失信息，或者通过 SGSN向 GGSN 上报无线承载丢失信息。其中， 本实施例与图 1所示实施例相同的内容不再 赘述， 请参照图 5， 该方法包括：
歩骤 501 : 接收携带释放原因值的 UE上下文释放请求消息或者释放接 入承载请求消息或者 Iu接口释放请求消息；
其中， 释放原因值用于指示释放原因， 例如可以为： 与 UE之间失去无 线连接， 管理维护原因， UE进入休眠状态， 或者与 UE之间的完整性检查 重复失败等等， 当释放原因值为： 与 UE之间失去无线连接， 管理维护原因， 与 UE之间的完整性检查重复失败等任意一项时， 则确认为异常释放。 歩骤 502： 判断 PGW或者 GGSN是否订阅了无线承载丢失信息， 如果是， 则执 行歩骤 503， 否则结束。
在本实施例中， 由 MME或者 SGW判断 PGW是否订阅了无线承载丢 失信息， 由 SGSN判断 GGSN是否订阅了无线承载丢失信息。
其中， PCRF可以向 PDN网关 PGW或者 GGSN订阅无线承载丢失信息， 当 PDN网关 PGW或者 GGSN收到 PCRF的订阅后， 再向网络侧设备订阅。
其中， 本实施例的网络侧设备可以是 MME、 SGSN、 或者 SGW。 歩骤 503: 判断所述释放原因值是否是异常释放， 如果是， 则执行歩骤 504， 否则结束；
歩骤 504:向网关上报 UE无线承载丢失信息，并保留所有非 GBR承载。 其中，所述网关具体为： PGW或 GGSN。当本实施例的方法应用于 MME 时， 该歩骤 504由 MME通过 SGW向网关 PGW上报该无线承载丢失信息； 当本实施例的方法应用于 SGW时，该歩骤 504由 SGW向网关 PGW上报该 无线承载丢失信息；当本实施例的方法应用于 SGSN时，该歩骤 504由 SGSN 向网关 GGSN上报该无线承载丢失信息。
在本实施例中， 并不限制歩骤 502和歩骤 503执行的先后顺序， 例如可 以先判断释放原因值， 再判断 PGW或者 GGSN是否订阅了该无线承载丢失 信息， 本实施例并不以此作为限制。
通过本发明实施例提供的无线承载丢失信息的上报方法， 在 PGW或者 GGSN预先订阅了无线承载丢失信息后， 向该 PGW或者 GGSN上报这一信 息，解决了目前 MME/SGSN在收到无线侧承载丢失信息后，对非 GBR承载 采用承载释放机制来通知网关， 并在有 PCC部署情况下， 由网关通知 PCRF 所导致的非 GBR承载上无论该业务是否可忍受无线侧承载丢失都会中断， 以及缺省承载释放导致的 IP地址释放， 需要重新附着的问题。
为使图 5所示实施例的方法更加清楚易懂， 以下结合图 6和图 7所示的 流程对本实施例的方法进行详细说明。
图 6为 MME根据 PGW的无线承载丢失信息上报请求来决定是否上报 的其中一个实施方式的流程图， 本实施例是针对 3GPP标准组织定义的 EPS (Evolved Packet System, 演进分组系统）系统， 无线接入技术为 eUTRAN。 请参照图 6， 该流程包括：
歩骤 601-602: PCRF向 PGW订阅无线承载丢失信息， 其中， PGW包 含有 PCEF (Policy and Charging Enforcement Function, 策略及计费执行功 能）， 在本实施例中， 若无特殊说明， PGW是指包含 PCEF的实体； 其中， 该信息值可以重用当前已经定义的 LOSS— OF— BEARER信息， 或 者新定义一个信息专用于无线承载丢失， 该信息可以是针对整个 IP-CAN会 话的， 或者针对特定规则的， 本实施例并不以此作为限制。
歩骤 603: PGW收到 PCRF的订阅无线承载丢失信息请求后， 向 SGW 发送更新承载请求 （update Bearer reques) 消息， 要求 MME检测到无线承 载丢失后， 把该信息上报给 PGW;
其中， 如果 PCRF订阅的无线承载丢失信息针对整个 IP-CAN会话， 则 向 MME请求无线承载丢失是针对所有非 GBR承载的； 如果 PCRF订阅的 信息是针对某些 PCC规则的，则 PGW仍可以选择向 MME请求无线承载丢 失是针对所有非 GBR承载的， 也可以选择向 MME请求无线承载丢失是针 对特定非 GBR承载的， 这些特定的非 GBR承载绑定了上述的 PCC mle。
例如， PCRF针对 PCC rule 1进行订阅， PGW发现 PCC rule 1绑定到非 GBR承载 2上， 则请求无线承载丢失仅针对非 GBR承载 2。
歩骤 604-606: SGW向 MME发送更新承载请求（update Bearer request) 消息， 要求 MME检测到无线承载丢失后， 上报该信息；
歩骤 607: eNB检测到需要释放和 UE (用户设备） 之间的信令连接和 所有无线承载， 则发送 SI UE Context Release Request (上下文释放请求）消 息给 MME;
其中， 该消息中携带释放原因值， 指示释放原因， 比如和 UE之间失去 无线连接、 管理维护原因、 UE进入休眠状态、 以及 UE之间的完整性检查 重复失败等。 当释放原因值为： 与 UE之间失去无线连接， 管理维护原因， 或者与 UE之间的完整性检查重复失败时， 则确认为异常释放。
歩骤 608: MME收到 UE上下文释放请求消息， 首先判断 PGW是否订 阅了无线承载丢失信息， 再根据释放原因值决定是否上报， 如果 PGW要求 MME上报无线承载丢失信息， 且释放原因值显示是异常释放， 即释放原因 值为： 与 UE之间失去无线连接， 管理维护原因， 与 UE之间的完整性检查 重复失败等任意一项时， 则 MME通过 SGW向网关 PGW上报无线承载丢 失信息， 同时仍保留所有的非 GBR承载；
歩骤 609: MME向 SGW (服务网关）发送修改承载请求（ modify Bearer request)消息或者释方夂接入承载请求 (Release Access Bearers Request)消息， 该消息中携带 UE无线承载丢失信息；
其中， 该无线承载丢失信息可以只是一个通用的描述， 即不再区分具体 的释放原因， 也可以进一歩携带原因值， 指明无线承载丢失的具体原因。 在 本实施里， 根据 PGW请求无线承载丢失的粒度， 这个无线承载丢失信息可 以是针对该 UE所有非 GBR承载的，也可以是针对一个特定的非 GBR承载。
歩骤 610: SGW收到修改承载请求消息或者释放接入承载请求消息后， 如果消息里携带有 UE 无线承载丢失信息， 则通过修改承载请求 （modify Bearer request) 消息将 UE无线承载丢失信息通知 PGW (PDN网关）；
歩骤 611 : PGW收到修改承载请求消息后， 通过 CCR (Credit Control Request, 信用控制请求）消息向 PCRF上报无线承载丢失信息， 如果是针对 特定 PCC mle (规则） 的， 则通过 CCR消息中的参数 Charging-Rule-Report (计费规则报告） 上报受影响的规则；
歩骤 612: PCRF接收到该无线承载丢失信息后，可以通知 AF底层传输 中断， 如果某些业务因为无线承载丢失后无法进行， PCRF 可以通过 CCA ( Credit Control Answer ) 消息通知 PGW将这些业务对应的 PCC rule删除， 具体可以通过 CCA消息中的参数 Charging-Rule-Remove (计费规则移除） 来通知 PGW删除这些 PCC rule;
歩骤 613: 如果 PCRF要求释放某些 PCC rule, 则 PGW则根据新的承 载绑定结果， 可选的发起一些承载操作， 比如更新某些承载， 如果一个非缺 省承载的全部规则都释放了， 也可以发起承载释放操作。
需要说明的是， 本实施例虽然仅描述了 PGW向 MME订阅， 但也同样 适用于 PGW向 SGW请求上报无线承载丢失信息（参考图 3所示的实施例）， 在这种情况下 SGW根据 PGW的请求， 在无线承载异常释放时通知 PGW。 同样的，本实施例也适用于 GGSN向 SGSN请求上报无线承载丢失信息（参 考图 4所示的实施例）， SGSN根据 GGSN的请求， 在无线承载异常释放时 通知 GGSN, 为了简化起见， 在此不再赘述。
至此， MME可以根据 PGW的订阅请求 （该订阅请求可以由 PCRF发 起） 决定是否上报。
图 7为 MME根据 PGW的无线承载丢失信息上报请求来决定是否上报 的另外一个实施方式的流程图， 本实施例是针对 3GPP标准组织定义的 EPS (Evolved Packet System) 系统， 无线接入技术为 eUTRAN。 与图 6所示的 流程不同的是， SGW和 PGW之间采用 PMIP (Proxy Mobile IP, 代理移动 IP协议） 协议而不是 GTP (GPRS Tunnelling Protocol, GPRS隧道协议） 协 议， 在这种情况下 PGW无法通过 PMIP协议要求 MME进行无线承载丢失 上报也无法执行承载绑定， 这些功能由包含有 BBERF (Bearing Binding and Event Report Function, 承载绑定及事件报告功能） 的 SGW实现。 请参照图 7， 该流程包括：
歩骤 701-702: PCRF向 SGW订阅无线承载丢失信息， 在本实施例中， 若无特殊说明， SGW是指包含 BBERF的实体；
其中， 该信息值可以重用当前已经定义的 LOSS— OF— BEARER信息， 或 者新定义一个信息专用于无线承载丢失， 该信息可以是针对整个 IPCAN会 话的， 或者针对特定规则的， 本实施例并不以此作为限制。
歩骤 703-704: SGW收到 PCRF 的订阅无线承载丢失信息请求后， 向 MME发送更新承载请求（update Bearer request)消息， 要求 MME检测到无 线承载丢失后， 把该信息上报给 PCEF;
其中， 如果 PCRF订阅的无线承载丢失信息针对整个会话， 则向 MME 请求无线承载丢失是针对所有非 GBR承载的； 如果 PCRF订阅的无线承载 丢失信息是针对某些 QoS规则的， 则 SGW仍可以选择向 MME请求无线承 载丢失是针对所有非 GBR承载的， 也可以选择向 MME请求无线承载丢失 是针对特定非 GBR承载的，这些特定的非 GBR承载绑定了上述的 QoS mle。
歩骤 705: eNB检测到需要释放和 UE (用户设备） 之间的信令连接和 所有无线承载， 则发送 SI UE Context Release Request (上下文释放请求）消 息给 MME;
其中， 该消息中携带原因值， 指示释放原因， 比如和 UE之间失去无线 连接、 管理维护原因、 UE进入休眠状态、 以及 UE之间的完整性检查重复 失败等。 当释放原因值为： 与 UE之间失去无线连接， 管理维护原因， 或者 与 UE之间的完整性检查重复失败时， 则确认为异常释放。
歩骤 706: MME收到 UE上下文释放请求消息， 首先判断 PGW是否订 阅了无线承载丢失信息， 再根据释放原因值决定是否上报， 如果 SGW要求 MME上报无线承载丢失信息， 且释放原因值显示是异常释放， 即释放原因 值为非用户进入休眠状态（user inactivity) , 则 MME通知网关无线承载丢失 信息， 同时仍保留所有的非 GBR承载；
歩骤 707: MME向 SGW (服务网关）发送修改承载请求（ modify Bearer request)消息或者释方夂接入承载请求 (Release Access Bearers Request)消息； 其中， 该消息中携带 UE无线承载丢失信息， 这个无线承载丢失信息可 以只是一个通用的描述， 即不再区分具体的释放原因， 也可以进一歩携带原 因值， 指明无线承载丢失的具体原因。 在本实施里， 根据 PGW请求无线承 载丢失的粒度， 这个无线承载丢失信息可以是针对该 UE所有非 GBR承载 的， 也可以是针对一个特定的非 GBR承载。
歩骤 708: SGW收到修改承载请求消息后， 通过 CCR (Credit Control Request, 信用控制请求）消息向 PCRF上报无线承载丢失信息， 如果是针对 特定 QoS rule的， 则通过 CCR消息中的参数 QOS-Rule-Report (计费规则报 告） 上报受影响的规则；
歩骤 709: PCRF接收到该无线承载丢失信息后，可以通知 AF底层传输 中断， 如果某些业务因为无线承载丢失后无法进行， PCRF 可以通过 CCA (Credit Control Answer) 消息通知 SGW将这些业务对应的 PCC rule以及 Qos rule删除， 具体可以通过 CCA消息中的参数 Charging-Rule-Remove (计 费规则移除） 来通知 SGW删除这些 PCC rule以及 Qos rule;
歩骤 710: 如果 PCRF要求释放（也即删除）某些 QoS rule, 则 SGW根 据新的承载绑定结果， 可选的发起一些承载操作， 比如更新某些承载， 如果 一个非缺省承载的全部规则都释放了， 也可以发起承载释放操作（对于缺省 承载是不能释放的）；
歩骤 711-712: PCRF要求 PGW (包含 PCEF) 删除 PCC mle。
至此， MME可以根据 SGW的订阅请求 （该订阅请求可以由 PCRF发 起） 决定是否上报。
在图 6和图 7所示的实施例中， 如果没有 PCC部署， 则虚线所示的歩 骤即不存在。
通过本发明实施例提供的无线承载丢失信息的上报方法， 解决了目前 MME在收到无线侧承载丢失信息后，对非 GBR承载采用承载释放机制来通 知网关， 并在有 PCC部署情况下， 由网关通知 PCRF所导致的非 GBR承载 上无论该业务是否可忍受无线侧承载丢失都会中断， 以及缺省承载释放导致 的 IP地址释放， 需要重新附着的问题。
图 8为本发明实施例提供的一种移动管理实体 MME的组成框图， 请参 照图 8， 该 MME包括：
接收单元 81， 用于接收演进型基站 eNB发送的携带释放原因值的 UE 上下文释放消息；
其中， 释放原因值用于指示释放原因， 例如可以为： 与 UE之间失去无 线连接， 管理维护原因， UE进入休眠状态， 或者与 UE之间的完整性检查 重复失败等等， 当释放原因值为： 与 UE之间失去无线连接， 管理维护原因， 与 UE之间的完整性检查重复失败等任意一项时， 则确认为异常释放。 上报单元 82， 用于在所述释放原因值指示异常释放时， 通过 SGW向网 关 PGW上报无线承载丢失信息；
处理单元 83，用于在所述释放原因值指示异常释放时，保留所有非 GBR 承载。
其中， 当无线接入网侧设备 （例如 eNB)检测到需要释放 UE的无线信 令连接以及所有无线承载时， 则向网络侧设备 （例如 MME) 发送携带释放 原因值的 UE上下文释放请求消息，通知 MME该 UE的无线连接已经中断。 此时， MME在接收到对应的携带释放原因值的 UE上下文释放消息后， 根 据释放原因值决定是否进行无线承载丢失信息的上报， 其中， 如果是异常释 放， 即释放原因值为： 与 UE之间失去无线连接， 管理维护原因， 与 UE之 间的完整性检查重复失败等任意一项时，则通过 SGW向 PGW通知 UE的无 线承载丢失信息， 同时仍在 MME上保留所有非 GBR承载。
在一个实施例中，上报单元 82具体用于向 SGW发送携带无线承载丢失 信息的修改承载请求消息或者释放接入承载请求消息， 以通过所述 SGW向 PGW发送携带无线承载丢失信息的修改承载请求消息。
在一个实施例中， 该 MME还可以包括：
判断单元 84，用于在接收单元 81接收演进型基站 eNB发送的携带释放 原因值的 UE上下文释放消息之后， 判断 PGW是否订阅了无线承载丢失信 息， 如果所述 PGW订阅了无线承载丢失信息， 则判断所述释放原因值是否 是异常释放， 并将判断的结果提供给上报单元 82和处理单元 83。
本实施例的 MME的各组成部分分别用于实现图 2所示实施例的方法的 各歩骤， 由于在图 2所示的实施例中， 已经对各歩骤进行了详细说明， 在此 不再赘述。
通过本发明实施例提供的 MME, 解决了目前 MME在收到无线侧承载 丢失信息后， 对非 GBR承载采用承载释放机制来通知网关， 并在有 PCC部 署情况下， 由网关通知 PCRF所导致的非 GBR承载上无论该业务是否可忍 受无线侧承载丢失都会中断， 以及缺省承载释放导致的 IP地址释放， 需要 重新附着的问题。
图 9为本发明实施例提供的一种服务网关 SGW的组成框图， 请参照图 9， 该 SGW包括：
接收单元 91，用于接收 MME发送的携带释放原因值的释放接入承载请 求消息；
其中， 释放原因值用于指示释放原因， 例如可以为： 与 UE之间失去无 线连接， 管理维护原因， UE进入休眠状态， 或者与 UE之间的完整性检查 重复失败等等， 当释放原因值为： 与 UE之间失去无线连接， 管理维护原因， 与 UE之间的完整性检查重复失败等任意一项时， 则确认为异常释放。
上报单元 92， 用于在所述释放原因值指示异常释放时， 向 PGW通知无 线承载丢失信息；
处理单元 93，用于在所述释放原因值指示异常释放时，保留所有非 GBR 承载。
其中， MME在接收到对应的携带释放原因值的 UE上下文释放消息后， 不进行无线承载丢失信息的上报， 而是通过释放接入承载请求消息将释放原 因值转发给 SGW, 由该 SGW进行无线承载丢失信息的上报。
其中， SGW在接收到对应的携带释放原因值的释放接入承载请求消息 后， 根据释放原因值决定是否进行无线承载丢失信息的上报， 其中， 如果是 异常释放， 即释放原因值为： 与 UE之间失去无线连接， 管理维护原因， 与 UE之间的完整性检查重复失败等任意一项时，则向 PGW通知 UE的无线承 载丢失信息， 同时仍在 SGW上保留所有非 GBR承载。
在一个实施例中，上报单元 92具体用于向 PGW发送携带无线承载丢失 信息的修改承载请求消息。
在一个实施例中， 该 SGW还包括：
判断单元 94， 用于在接收单元 91接收到 MME发送的携带释放原因值 的释放接入承载请求消息后，判断所述 PGW是否订阅了无线承载丢失信息， 如果所述 PGW订阅了无线承载丢失信息， 则判断所述释放原因值释放是异 常释放， 并将判断的结果提供给上报单元 92和处理单元 93。
本实施例的 SGW的各组成部分分别用于实现图 3所示实施例的方法的 各歩骤， 由于在图 3所示的实施例中， 已经对各歩骤进行了详细说明， 在此 不再赘述。
通过本发明实施例提供的 SGW, 解决了目前 MME在收到无线侧承载 丢失信息后， 对非 GBR承载采用承载释放机制来通知网关， 并在有 PCC部 署情况下， 由网关通知 PCRF所导致的非 GBR承载上无论该业务是否可忍 受无线侧承载丢失都会中断， 以及缺省承载释放导致的 IP地址释放， 需要 重新附着的问题。
图 10为本发明实施例提供的一种服务 GPRS支持节点 SGSN的组成框 图， 请参照图 10， 该 SGSN包括：
接收单元 1001， 用于接收无线网络控制器 RNC发送的携带释放原因值 的 Iu接口释放请求消息；
其中， 释放原因值用于指示释放原因， 例如可以为： 与 UE之间失去无 线连接， 管理维护原因， UE进入休眠状态， 或者与 UE之间的完整性检查 重复失败等等， 当释放原因值为： 与 UE之间失去无线连接， 管理维护原因， 与 UE之间的完整性检查重复失败等任意一项时， 则确认为异常释放。
上报单元 1002，用于在所述释放原因值指示异常释放时， 向网关通知无 线承载丢失信息；
处理单元 1003， 用于在所述释放原因值指示异常释放时， 保留所有非 GBR承载。
在本实施例中， 当无线接入网侧设备 （例如 RNC)检测到需要释放 UE 的无线信令连接以及所有无线承载时， 则向网络侧设备 （例如 SGSN) 发送 携带释放原因值的 Iu接口释放请求消息，通知 SGSN该 UE的无线连接已经 中断。 此时， 该 SGSN在接收到该 Iu接口释放请求消息后， 进行无线承载 丢失信息的上报。
其中， SGSN在接收到对应的携带释放原因值的 Iu接口释放请求消息后， 根据释放原因值决定是否进行无线承载丢失信息的上报， 其中， 如果是异常 释放， 即释放原因值为： 与 UE之间失去无线连接， 管理维护原因， 与 UE 之间的完整性检查重复失败等任意一项时，则向 GGSN通知 UE的无线承载 丢失信息， 同时仍在 SGSN上保留所有非 GBR承载。
在一个实施例中，上报单元 1002具体用于向网关 GPRS支持节点 GGSN 发送携带无线承载丢失信息的更新 PDP上下文请求消息。
在一个实施例中， 该 SGSN还可以包括：
判断单元 1004， 用于在接收单元 1001接收无线网络控制器 RNC发送 的携带释放原因值的 Iu接口释放请求消息之后， 判断 GGSN是否订阅了无 线承载丢失信息， 如果所述 GGSN订阅了无线承载丢失信息，则判断所述释 放原因值是否是异常释放， 并将判断的结果提供给上报单元 1002和处理单 元 1003。
本实施例的 SGSN的各组成部分分别用于实现图 4所示实施例的方法的 各歩骤， 由于在图 4所示的实施例中， 已经对各歩骤进行了详细说明， 在此 不再赘述。
通过本发明实施例提供的 SGSN,解决了目前 GGSN在收到无线侧承载 丢失信息后， 对非 GBR承载采用承载释放机制来通知网关， 并在有 PCC部 署情况下， 由网关通知 PCRF所导致的非 GBR承载上无论该业务是否可忍 受无线侧承载丢失都会中断， 以及缺省承载释放导致的 IP地址释放， 需要 重新附着的问题。
结合本文中所公开的实施例描述的方法或算法的歩骤可以直接用硬件、 处理器执行的软件模块， 或者二者的结合来实施。 软件模块可以置于随机存 储器（RAM)、 内存、 只读存储器（ROM)、 电可编程 ROM、 电可擦除可编 程 ROM、 寄存器、 硬盘、 可移动磁盘、 CD-ROM、 或技术领域内所公知的 任意其它形式的存储介质中。
以上所述的具体实施例， 对本发明的目的、 技术方案和有益效果进行了 进一歩详细说明， 所应理解的是， 以上所述仅为本发明的具体实施例而已， 并不用于限定本发明的保护范围， 凡在本发明的精神和原则之内， 所做的任 何修改、 等同替换、 改进等， 均应包含在本发明的保护范围之内。

Claims

权利要求书
1、 一种无线承载丢失信息的上报方法， 其特征在于， 所述方法包括： 接收携带释放原因值的用户设备 UE上下文释放请求消息或者释放接入 承载请求消息或者 Iu接口释放请求消息；
如果所述释放原因值指示异常释放， 则向网关上报无线承载丢失信息， 并保留非保证带宽 GBR承载。
2、 根据权利要求 1所述的方法， 其特征在于， 当所述方法应用于移动 管理实体 MME时， 所述接收携带释放原因值的用户设备 UE上下文释放请 求消息或者释放接入承载请求消息或者 Iu接口释放请求消息， 具体为： 接收演进型基站 eNB发送的所述携带释放原因值的用户设备 UE上下文 释放请求消息。
3、 根据权利要求 2所述的方法， 其特征在于， 向网关上报无线承载丢 失信息， 包括：
向服务网关 SGW发送携带无线承载丢失信息的修改承载请求消息或者 释放接入承载请求消息， 通过所述 SGW向分组数据网络 PDN网关 PGW发 送携带无线承载丢失信息的修改承载请求消息。
4、 根据权利要求 1所述的方法， 其特征在于， 当所述方法应用于服务 网关 SGW时， 所述接收携带释放原因值的用户设备 UE上下文释放请求消 息或者释放接入承载请求消息或者 Iu接口释放请求消息， 具体为：
接收 MME发送的所述携带释放原因值的释放接入承载请求消息。
5、 根据权利要求 4所述的方法， 其特征在于， 向网关上报无线承载丢 失信息， 包括：
向 PGW发送携带无线承载丢失信息的修改承载请求消息。
6、 根据权利要求 1所述的方法， 其特征在于， 当所述方法应用于服务 GPRS支持节点 SGSN时， 所述接收携带释放原因值的用户设备 UE上下文 释放请求消息或者释放接入承载请求消息或者 Iu接口释放请求消息， 具体为： 接收无线网络控制器 RNC发送的所述携带释放原因值的 Iu接口释放请 求消息。
7、 根据权利要求 6所述的方法， 其特征在于， 向网关上报无线承载丢 失信息， 包括：
向网关 GPRS支持节点 GGSN发送携带无线承载丢失信息的更新 PDP 上下文请求消息。
8、 根据权利要求 1所述的方法， 其特征在于， 接收携带释放原因值的 UE上下文释放请求消息或者释放接入承载请求消息或者 Iu接口释放请求消 息之后， 还包括：
判断网关是否订阅了无线承载丢失信息；
如果所述网关订阅了无线承载丢失信息， 则判断所述释放原因值是否是 异常释放。
9、 根据权利要求 8所述的方法， 其特征在于， 所述网关订阅所述无线 承载丢失信息之前， 还包括：
策略和计费规则功能实体 PCRF向所述网关订阅所述无线承载丢失信息。
10、 根据权利要求 1-9任意一项所述的方法， 其特征在于， 所述释放原 因值为： 与 UE之间失去无线连接、 管理维护原因、 UE进入休眠状态或者 与 UE之间的完整性检查重复失败。
11、 根据权利要求 10所述的方法， 其特征在于， 当所述释放原因值为： 与 UE之间失去无线连接、 管理维护原因或者与 UE之间的完整性检查重复 失败时， 为异常释放。
12、 一种移动管理实体 MME, 其特征在于， 所述 MME包括： 接收单元，用于接收演进型基站 eNB发送的携带释放原因值的 UE上下 文释放请求消息；
上报单元， 用于在所述释放原因值指示异常释放时， 向网关通知无线承 载丢失信息； 处理单元， 用于在所述释放原因值指示异常释放时， 保留非 GBR承载。
13、根据权利要求 12所述的 MME,其特征在于，所述释放原因值包括： 与 UE之间失去无线连接、管理维护原因、 UE进入休眠状态或者与 UE之间 的完整性检查重复失败；
当所述释放原因值为： 与 UE之间失去无线连接、 管理维护原因或者与 UE之间的完整性检查重复失败时， 为异常释放。
14、 根据权利要求 12所述的 MME, 其特征在于， 所述上报单元具体用 于： 向 SGW发送携带无线承载丢失信息的修改承载请求消息或者释放接入 承载请求消息， 以便所述 SGW向 PGW发送携带无线承载丢失信息的修改 承载请求消息。
15、 根据权利要求 12所述的 MME, 其特征在于， 所述 MME还包括： 判断单元， 用于在所述接收单元接收演进型基站 eNB 发送的携带释放 原因值的 UE上下文释放请求消息之后， 判断 PGW是否订阅了无线承载丢 失信息， 如果所述 PGW订阅了无线承载丢失信息， 则判断所述释放原因值 是否是异常释放。
16、 一种服务网关 SGW, 其特征在于， 所述 SGW包括：
接收单元， 用于接收 MME发送的携带释放原因值的释放接入承载请求 消息；
上报单元， 用于在所述释放原因值指示异常释放时， 向 PGW通知无线 承载丢失信息；
处理单元， 用于在所述释放原因值指示异常释放时， 保留非 GBR承载。
17、根据权利要求 16所述的 SGW,其特征在于，所述释放原因值包括： 与 UE之间失去无线连接、管理维护原因、 UE进入休眠状态或者与 UE之间 的完整性检查重复失败；
当所述释放原因值为： 与 UE之间失去无线连接、 管理维护原因或者与 UE之间的完整性检查重复失败时， 为异常释放。
18、 根据权利要求 16所述的 SGW， 其特征在于， 所述上报单元具体用 于向 PGW发送携带无线承载丢失信息的修改承载请求消息。
19、 根据权利要求 16所述的 SGW, 其特征在于， 所述 SGW还包括： 判断单元， 用于在所述接收单元接收到 MME发送的携带释放原因值的 释放接入承载请求消息后， 判断所述 PGW是否订阅了无线承载丢失信息， 如果所述 PGW订阅了无线承载丢失信息， 则判断所述释放原因值是否是异 常释放。
20、 一种服务 GPRS支持节点 SGSN, 其特征在于， 所述 SGSN包括： 接收单元， 用于接收无线网络控制器 RNC发送的携带释放原因值的 Iu 接口释放请求消息；
上报单元， 用于在所述释放原因值指示异常释放时， 向网关通知无线承 载丢失信息；
处理单元， 用于在所述释放原因值指示异常释放时， 保留非 GBR承载。
21、 根据权利要求 20所述的 SGSN, 其特征在于， 所述释放原因值包 括： 与 UE之间失去无线连接、 管理维护原因、 UE进入休眠状态或者与 UE 之间的完整性检查重复失败；
当所述释放原因值为： 与 UE之间失去无线连接、 管理维护原因或者与 UE之间的完整性检查重复失败时， 为异常释放。
22、 根据权利要求 20所述的 SGSN, 其特征在于， 所述上报单元具体 用于向网关 GPRS支持节点 GGSN发送携带无线承载丢失信息的更新 PDP 上下文请求消息。
23、 根据权利要求 20所述的 SGSN, 其特征在于， 所述 SGSN还包括： 判断单元， 用于在所述接收单元接收无线网络控制器 RNC发送的携带 释放原因值的 Iu接口释放请求消息之后， 判断 GGSN是否订阅了无线承载 丢失信息， 如果所述 GGSN订阅了无线承载丢失信息，则判断所述释放原因 值是否是异常释放。
PCT/CN2010/076194 2010-08-20 2010-08-20 无线承载丢失信息的上报方法和装置 WO2011110000A1 (zh)

Priority Applications (9)

Application Number Priority Date Filing Date Title
ES10847258T ES2724174T3 (es) 2010-08-20 2010-08-20 Método y aparato para informar mensaje de pérdida de portador de radio
EP18210714.4A EP3512240B1 (en) 2010-08-20 2010-08-20 Method and apparatus for reporting radio bearer loss information
CN2010800060214A CN102232301A (zh) 2010-08-20 2010-08-20 无线承载丢失信息的上报方法和装置
CN201610934314.8A CN106488503B (zh) 2010-08-20 2010-08-20 无线承载丢失信息的上报方法和装置
PCT/CN2010/076194 WO2011110000A1 (zh) 2010-08-20 2010-08-20 无线承载丢失信息的上报方法和装置
EP10847258.0A EP2574133B1 (en) 2010-08-20 2010-08-20 Method and apparatus for reporting radio bearer loss message
US13/727,261 US9060305B2 (en) 2010-08-20 2012-12-26 Method and apparatus for reporting radio bearer loss information
US14/720,472 US10075865B2 (en) 2010-08-20 2015-05-22 Method and apparatus for reporting radio bearer loss information
US16/056,140 US10812999B2 (en) 2010-08-20 2018-08-06 Method and apparatus for reporting radio bearer loss information

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2010/076194 WO2011110000A1 (zh) 2010-08-20 2010-08-20 无线承载丢失信息的上报方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/727,261 Continuation US9060305B2 (en) 2010-08-20 2012-12-26 Method and apparatus for reporting radio bearer loss information

Publications (1)

Publication Number Publication Date
WO2011110000A1 true WO2011110000A1 (zh) 2011-09-15

Family

ID=44562829

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/076194 WO2011110000A1 (zh) 2010-08-20 2010-08-20 无线承载丢失信息的上报方法和装置

Country Status (5)

Country Link
US (3) US9060305B2 (zh)
EP (2) EP3512240B1 (zh)
CN (2) CN102232301A (zh)
ES (1) ES2724174T3 (zh)
WO (1) WO2011110000A1 (zh)

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102726020A (zh) * 2009-11-24 2012-10-10 爱立信(中国)通信有限公司 通过未发送的下行链路数据量记录技术字段的过度计费防止
EP2517528B1 (en) * 2009-12-21 2015-07-22 Telefonaktiebolaget L M Ericsson (PUBL) Non-guaranteed bit rate bearer control in a mobile communication network
PL2613597T3 (pl) * 2012-01-06 2021-12-06 Alcatel Lucent Zmniejszanie obciążenia wynikającego z raportowania zmian informacji reguły PCC w systemie komunikacji mobilnej
CN102833729B (zh) * 2012-08-10 2016-05-25 华为终端有限公司 一种无线承载释放的报告方法、终端设备、3gpp服务器和网络系统
CN104769991B (zh) * 2012-11-01 2018-04-10 Lg 电子株式会社 Mtc监控方法
CN103813300A (zh) * 2012-11-14 2014-05-21 华为终端有限公司 数据传输方法、设备及系统
WO2014131158A1 (en) * 2013-02-27 2014-09-04 Telefonaktiebolaget L M Ericsson (Publ) Controlling resources of radio terminal in radio access node
WO2015163624A1 (en) * 2014-04-24 2015-10-29 Lg Electronics Inc. Method for releasing a sidelink radio bearer for d2d communication system and device therefor
CN110461012B (zh) * 2014-09-05 2022-09-02 华为技术有限公司 一种分流策略协商方法及装置
US10455460B2 (en) * 2015-03-18 2019-10-22 Lg Electronics Inc. Method for processing loss of access in a wireless communication system, and device therefor
CN106664540B (zh) * 2015-07-07 2020-01-31 华为技术有限公司 检测终端设备异常的方法、装置及系统
CN106921954B (zh) * 2015-12-25 2021-02-19 中兴通讯股份有限公司 进出区域监控的处理方法及装置
CN108616833B (zh) * 2016-12-08 2021-03-09 中国移动通信集团四川有限公司 Pcc会话的处理方法、装置、系统、pgw和pcrf
CN111567083B (zh) * 2017-12-25 2023-05-26 Oppo广东移动通信有限公司 释放终端上下文的通知方法、网络设备及计算机存储介质
CN108980951B (zh) * 2018-04-28 2020-07-07 东南大学 一种结合co2捕集的热网水分级加热系统
CN111726889B (zh) * 2020-05-08 2022-05-27 新华三技术有限公司成都分公司 上下文获取方法和装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090320100A1 (en) * 2008-06-20 2009-12-24 Qualcomm Incorporated Handling of integrity check failure in a wireless communication system
CN101742576A (zh) * 2008-11-07 2010-06-16 华为技术有限公司 恢复保留态gbr承载的方法及装置
CN101772010A (zh) * 2008-12-30 2010-07-07 联芯科技有限公司 分组交换业务小区更新时的终端和网络的异常处理方法

Family Cites Families (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050203673A1 (en) * 2000-08-18 2005-09-15 Hassanayn Machlab El-Hajj Wireless communication framework
US8594298B2 (en) * 2004-02-20 2013-11-26 Avaya Inc. Call management
WO2007022791A1 (en) * 2005-08-24 2007-03-01 Telefonaktiebolaget Lm Ericsson (Publ) Preserved bearers
US8150363B2 (en) * 2006-02-16 2012-04-03 Telecommunication Systems, Inc. Enhanced E911 network access for call centers
US8064875B2 (en) * 2006-08-04 2011-11-22 At&T Intellectual Property I, L.P. Methods and apparatus to update geographic location information associated with internet protocol devices for E-911 emergency services
CN101127610B (zh) * 2006-08-15 2012-07-04 华为技术有限公司 移动通信系统网络环境下的计费负流量的处理方法
JP2008129713A (ja) * 2006-11-17 2008-06-05 Fujitsu Ltd 複数のモダリティを関連付けるための方法、そのプログラムおよび複数モダリティを関連付けるマルチモーダルシステム
US8638713B2 (en) * 2006-12-01 2014-01-28 At&T Mobility Ii Llc Non-intrusive in-session QoS parameter modification method
US8576833B2 (en) * 2006-12-15 2013-11-05 At&T Intellectual Property I, L.P. Fault tolerant voice over Internet protocol (VoIP) systems and methods to operate the same
CN102695294B (zh) * 2007-05-28 2015-01-21 华为技术有限公司 网络锚点的地址删除方法及通信系统
CN101325780B (zh) * 2007-06-15 2010-07-07 华为技术有限公司 策略控制实现方法和系统、及策略和计费执行实体
US20080320149A1 (en) * 2007-06-25 2008-12-25 Stefano Faccin Service request device wireless access detach and bearer deactivation methods withou loss of internet protocol connectivity
JP5138045B2 (ja) * 2007-11-16 2013-02-06 ノキア シーメンス ネットワークス オサケユキチュア システム間ハンドオーバのためのサービス品質のマッピング
EP2215799B1 (en) * 2007-11-19 2016-03-23 Telefonaktiebolaget LM Ericsson (publ) Pre-authorization of bearer set-up
CN101478742A (zh) * 2008-01-04 2009-07-08 华为技术有限公司 移动通信系统承载修改的方法和设备
ATE516685T1 (de) * 2008-01-08 2011-07-15 Ericsson Telefon Ab L M Angebotene bitrate bei der übergabe
US20100174737A1 (en) * 2008-02-12 2010-07-08 Chazon Stein System and Method for Communications
US8599765B2 (en) * 2008-03-21 2013-12-03 Blackberry Limited Evolved packet system quality of service enforcement deactivation handling to prevent unexpected user equipment detach
CA2719823C (en) * 2008-03-28 2014-07-29 Research In Motion Limited System and method for multiple packet data network connectivity detachment
US8165068B2 (en) * 2008-04-18 2012-04-24 Research In Motion Limited User equipment detach with multiple packet data network connectivity
CN101478795B (zh) * 2008-04-30 2011-07-06 华为技术有限公司 资源处理的方法、通信系统和移动性管理网元
US8314683B2 (en) * 2008-05-09 2012-11-20 The Israelife Foundation Incident response system
US8005087B2 (en) * 2008-09-16 2011-08-23 Alcatel Lucent Application-level processing for default LTE bearer
US8724509B2 (en) * 2009-04-03 2014-05-13 Panasonic Corporation Mobile communication method, mobile communication system, and corresponding apparatus
EP2422547B1 (en) * 2009-04-23 2013-12-04 Telefonaktiebolaget LM Ericsson (publ) PS to CS handover indicator
US9668293B2 (en) * 2009-08-25 2017-05-30 Telefonaktiebolaget Lm Ericsson (Publ) Relocation of mobility anchor for nomadic subscribers
WO2011034175A1 (ja) * 2009-09-18 2011-03-24 日本電気株式会社 通信システムと通信制御方法
US8693367B2 (en) * 2009-09-26 2014-04-08 Cisco Technology, Inc. Providing offloads in a communication network
EP2517528B1 (en) * 2009-12-21 2015-07-22 Telefonaktiebolaget L M Ericsson (PUBL) Non-guaranteed bit rate bearer control in a mobile communication network
CN102714859B (zh) * 2010-01-21 2016-05-25 Lg电子株式会社 1x消息捆绑
US8948753B2 (en) * 2010-04-30 2015-02-03 Alcatel Lucent Method of providing notification of abnormal conditions during non-access stratum (NAS) message tunneling
CA2808460C (en) * 2010-08-18 2017-01-03 Research In Motion Limited Methods and apparatus to maintain call continuity
US9668199B2 (en) * 2010-11-08 2017-05-30 Google Technology Holdings LLC Wireless communication system, method of routing data in a wireless communication system, and method of handing over a wireless communication device, having an established data connection to a local network
JP5639281B2 (ja) * 2010-11-11 2014-12-10 クゥアルコム・インコーポレイテッドＱｕａｌｃｏｍｍ Ｉｎｃｏｒｐｏｒａｔｅｄ 回線交換フォールバック性能を改善するためのシステムおよび方法
US8923863B2 (en) * 2011-12-19 2014-12-30 Cisco Technology, Inc. Maintaining signaling reduction mode in communication networks

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090320100A1 (en) * 2008-06-20 2009-12-24 Qualcomm Incorporated Handling of integrity check failure in a wireless communication system
CN101742576A (zh) * 2008-11-07 2010-06-16 华为技术有限公司 恢复保留态gbr承载的方法及装置
CN101772010A (zh) * 2008-12-30 2010-07-07 联芯科技有限公司 分组交换业务小区更新时的终端和网络的异常处理方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2574133A4 *

Also Published As

Publication number Publication date
US20130114417A1 (en) 2013-05-09
CN102232301A (zh) 2011-11-02
US10812999B2 (en) 2020-10-20
ES2724174T3 (es) 2019-09-06
EP2574133A1 (en) 2013-03-27
EP3512240B1 (en) 2020-10-21
EP2574133A4 (en) 2013-07-31
CN106488503B (zh) 2020-07-14
EP2574133B1 (en) 2019-03-13
US9060305B2 (en) 2015-06-16
US10075865B2 (en) 2018-09-11
US20180352466A1 (en) 2018-12-06
EP3512240A1 (en) 2019-07-17
CN106488503A (zh) 2017-03-08
US20150257029A1 (en) 2015-09-10

Similar Documents

Publication Publication Date Title
WO2011110000A1 (zh) 无线承载丢失信息的上报方法和装置
US8832208B2 (en) Handling of aggregate maximum bit rate by policy and charge control
ES2424454T3 (es) Establecimiento de una sesión de comunicación
JP5970723B2 (ja) 輻輳状態報告方法およびアクセス・ネットワーク装置
US20130016658A1 (en) Reactivation of Dedicated Bearers
WO2012083795A1 (zh) 业务控制方法、装置及系统
US20150289304A1 (en) Method,system and device for switching communication paths
JP2012531143A (ja) サービス品質を向上させる方法、システム、及びアプリケーションネットワーク要素
WO2009132722A1 (en) Bearer control mode (nw-only or user-only) handling in intersystem handover
US20150003246A1 (en) Radio access network triggered bearer modification procedure
WO2011124106A1 (zh) 一种策略计费控制方法、系统和装置
WO2012097706A1 (zh) 一种承载修改的系统及方法
WO2009089790A1 (fr) Procédé pour l'acquisition du type d'un service support et pour la commutation entre réseaux supports pour des terminaux
WO2011120222A1 (zh) 优先级业务激活、去激活方法、装置和系统
CN111919501B (zh) 专用承载管理
WO2016107405A1 (zh) 业务流传输路径优化方法、装置及mme
WO2014067075A1 (zh) 缓解网络拥塞的方法、核心网设备和接入网设备
WO2018045834A1 (zh) 一种VoLTE业务处理方法及装置
WO2014166438A1 (zh) 一种基于拥塞控制的策略控制方法、装置和系统
WO2011150649A1 (zh) 分组数据网关重分配的方法和装置
CN108781475B (zh) 一种事件上报的方法及装置
WO2011157148A2 (zh) 非语音紧急业务会话建立方法、设备及系统
WO2016150115A1 (zh) 一种承载建立方法、分组数据网关、服务网关及系统
WO2011110006A1 (zh) 本地路由业务的计费方法、装置及网络系统
WO2011110013A1 (zh) 移动性管理网元故障的处理方法、网络设备及网络系统

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201080006021.4

Country of ref document: CN

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

Ref document number: 10847258

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2010847258

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE