[go: up one dir, main page]

WO2015048992A1 - Traitement de surcharge d'un nœud de réseau - Google Patents

Traitement de surcharge d'un nœud de réseau Download PDF

Info

Publication number
WO2015048992A1
WO2015048992A1 PCT/EP2013/070547 EP2013070547W WO2015048992A1 WO 2015048992 A1 WO2015048992 A1 WO 2015048992A1 EP 2013070547 W EP2013070547 W EP 2013070547W WO 2015048992 A1 WO2015048992 A1 WO 2015048992A1
Authority
WO
WIPO (PCT)
Prior art keywords
network node
information indicating
network
identity
overload
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/EP2013/070547
Other languages
English (en)
Inventor
Yong Yang
Anders FRÈDEN
Tony Olsson
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Priority to PCT/EP2013/070547 priority Critical patent/WO2015048992A1/fr
Publication of WO2015048992A1 publication Critical patent/WO2015048992A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/26—Flow control; Congestion control using explicit feedback to the source, e.g. choke packets
    • H04L47/263—Rate modification at the source after receiving feedback
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/11—Identifying congestion
    • 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/0247—Traffic management, e.g. flow control or congestion control based on conditions of the access network or the infrastructure network
    • 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/0284—Traffic management, e.g. flow control or congestion control detecting congestion or overload during communication

Definitions

  • Embodiments herein relate generally to a first network node, a method in the first network node, a third network node and a method in the third network node. More particularly the embodiments herein relate to for handling overload of a second network node in a communications network.
  • the Third Generation Partnership Project (3GPP) has concluded a new technical study - Core Network (CN) overload study, which aims for:
  • Such scenarios/events may include Home location register/Home Subscriber Server (HLR/HSS) overload by Radio Network Controller (RNC) restart, denial of service attacks, and misbehaving/3GPP-non-compliant wireless devices causing unpredictable system response.
  • HLR/HSS Home location register/Home Subscriber Server
  • RNC Radio Network Controller
  • Overload control is applicable to almost all interfaces specified in 3GPP, e.g. Gx interface which is covered by Diameter Overload control mechanism.
  • An objective of embodiments herein is therefore to provide improved overload control in a communications network.
  • the object is achieved by a method in a first network node for handling overload of a second network node in a communications network.
  • the first network node transmits, to a third network node, information indicating that the second network node is overloaded and information indicating the identity of the second network node, so as to enable the third network node to control the overload of the second network node.
  • transmitting overload and identity information from the first node to the third node may merely enable the third node to control the overload of the second node. This does not necessarily mean that the third node will actually do that, or that the third node is even capable of doing that. Rather, the information makes it possible for a capable third node to control the overload of the second node.
  • the object is achieved by a method in a third network node for handling overload of a second network node in a communications network.
  • the third network node receives information, from the first network node, information indicating that the second network node is overloaded and information indicating the identity of the second network node.
  • the third network node obtains information indicating at least one, PDN connection associated with the identity of the second network node.
  • the third network node determines to apply overload control towards the second network node and the associated at least one PDN connection for which information has been obtained.
  • the object is achieved by a first network node for handling overload of a second network node in a communications network.
  • the first network node comprises a transmitter which is adapted to detect overload of the second network node and then transmit, to a third network node, information indicating that the second network node is overloaded and information indicating the identity of the second network node, so as to enable the third network node to control the overload of the second network node.
  • the object is achieved by a third network node for handling overload of a second network node in a communications network.
  • the third network node comprises a receiver which is adapted to receive information, from a first network node, information indicating that the second network node is overloaded and information indicating the identity of the second network node.
  • the third network node comprises an obtaining unit which is adapted to obtain information indicating at least one PDN connection associated with the identity of the second network node.
  • the third network node comprises a determining unit which is adapted to determine to apply overload control towards the second network node and the associated at least one PDN connection for which information has been obtained.
  • Some embodiments herein allows receiving of signaling overload information in the first network node from the second network, and further transferring the signaling overload information from the first network node to the third network node.
  • the third network node may perform signaling reduction specifically towards the second network node.
  • Some embodiments herein provide an advantage of improved signaling efficiency.
  • the GTP request messages sent from the third network node to the second network node are deemed to be rejected due to downstream node overload situation according to the previous technology.
  • the signaling efficiency is improved by skipping transmission of those GTP messages which would have been deemed to be rejected in the previous technology.
  • Another advantage of some embodiments herein is that since the information transmitted in embodiments herein are piggybacked on existing signaling messages, the
  • embodiments herein does not provide any extra signaling.
  • a further advantage of some embodiments herein is that they are fully backward
  • Figure 1a is a schematic block diagram illustrating embodiments of a communications network.
  • Figure 1 b is a schematic block diagram illustrating embodiments of a communications network.
  • Figure 1c is a schematic block diagram illustrating embodiments of a communications network.
  • Figure 2 is a signaling diagram illustrating embodiments of a method in a communications network.
  • Figure 3 is a signaling diagram illustrating embodiments of a method in a communications network.
  • Figure 4 is a signaling diagram illustrating embodiments of a method in a communications network.
  • Figure 5 is a signaling diagram illustrating embodiments of a method in a communications network.
  • Figure 6 is a signaling diagram illustrating embodiments of a method in a communications network.
  • Figure 7 a is a signaling diagram illustrating embodiments of a method in a communications network.
  • Figure 7b is a continuation of figure 7a.
  • Figure 8 is a flow chart illustrating embodiments of a method in a first network node.
  • Figure 9 is a schematic block diagram illustrating embodiments of a first network node.
  • Figure 10a is a flow chart illustrating embodiments of a method in a third network node.
  • Figure 10b is a continuation of figure 10a.
  • Figure 1 1 is a schematic block diagram illustrating embodiments of a third network node.
  • the drawings are not necessarily to scale and the dimensions of certain features may have been exaggerated for the sake of clarity. Emphasis is instead placed upon
  • Embodiments herein relate to receiving and/or detecting in a first network node an
  • the third network node to control the overload of the second network node, e.g. perform signaling reduction specifically towards that second network node. This may involve associating a PDN connection with that overloaded second network node.
  • the overload may be signaling overload.
  • FIG. 1 a depicts a communications network 100 in which embodiments herein may be implemented.
  • the communications network 100 may in some embodiments apply to one or more radio access technologies such as for example Long Term Evolution (LTE), LTE Advanced, Wideband Code Division Multiple Access (WCDMA), WiMax, Wifi, Global
  • GSM Global System for Mobile Communications
  • WLAN Wireless Local Area Network
  • the communications network 100 comprises a first network node 101 connected to a second network node 103 and connected to a third network node 105. It should be noted that the links between the first network node 101 , the second network node 103 and the third network node 105 may be of any suitable wired link. The link may use any
  • the overloaded node may be referred to as a downstream node.
  • the upstream node is the node which may apply overload control, i.e. reduce the traffic towards the downstream node.
  • Figures 1 b and 1 c illustrates two different embodiments of the communications network 100 in figure 1.
  • Figure 1b illustrates an embodiment where the first network node 101 may be represented by a PGW or a GGSN and the second network node 103 may be represented by one of a PCRF, PCEF, OCS and Radius Server.
  • 10 105 may, in figure 1 b, be represented by one of a MME, a SGSN, an ePDG, a TWAN and a SGW.
  • the MME and SGSN are separate network nodes.
  • the MME and SGSN are co-located in one network node.
  • the term MME is used when referring to a standalone MME, a standalone SGSN or to a co-located MME/SGSN. The different abbreviations above will be
  • the right column represents the first network node 101
  • the middle column represents the second network node 103
  • the left column represents the third network node 105.
  • Figure 1 c illustrates another embodiment where the first network node may 101 may be represented by a PGW or a GGSN, similar to figure 1 b.
  • the second network node 103 may be represented by one of a MME, a SGSN, an ePDG, a TWAN and a SGW.
  • the third network node 101 may be represented by one of a PCRF, PCEF, OCS and Radius Server. In other words, the following combinations seen in table 2 may be valid.
  • the right column represents the first network node 101
  • the middle column represents the third network node 105
  • the left column represents the second network node 103.
  • a PGW short for Packet data network GateWay and sometimes referred to as PDN GW, is a network node of the communications network 100 which provides connectivity from a wireless device to external Packet Data Networks (PDN) by being the point of entry and/or exit of the traffic for the wireless device.
  • PDN Packet Data Networks
  • a wireless device may have simultaneous
  • the GGSN short for Gateway GPRS Support Node, is a network node which is responsible for the interworking between the GPRS network and an external network such as e.g. the Internet.
  • GPRS is short for general packet radio service.
  • the GGSN keeps a record of all active wireless devices and a Serving GPRS Support Node (SGSN) attached to the wireless device.
  • the GGSN allocates IP addresses to the wireless devices and is responsible for billing.
  • MME Mobility Management Entity
  • the MME sets up, modifies, and releases default and dedicated bearers.
  • a SGSN is a network node which is responsible for the delivery of data packets from and to the wireless device(s) within its geographical service area. Its tasks comprises packet routing and transfer, mobility management, logical link management, authentication and charging functions etc.
  • the MME is co-located with a SGSN in one network node.
  • An ePDG short for evolved Packet Data Gateway, is a network node which is responsible for securing the data transmission with a wireless device connected to the Evolved Packet Core (EPC) over an untrusted non-3GPP access.
  • EPC Evolved Packet Core
  • a TWAN short for Trusted WLAN Access Network, is a WLAN network interfaced with the Evolved Packet Core as a trusted non-3GPP access via the STa interface to the 3GPP
  • AAA Authentication, Authorization, and Accounting
  • a SGW short for Serving GateWay
  • a PCRF short for Policy and Charging Rules Function, is a function implemented in a network node which provides policy control and flow based charging control decisions in the
  • a PCEF short for Policy and Charging Enforcement Function, is a function implemented in a network node and provides policy enforcement along with follow based charging functionalities. It is responsible of providing controller functions in traffic handling and QOS at the network node in which it is implemented over the user plane, and providing service data flow detection, counting with including online and offline different charging interactions.
  • OCS short for Online Charging System, provides credit management and grants credit to the PCEF based on time, traffic volume or chargeable events.
  • a Radius Server where Radius is short for Remote access dial in user service, provides AAA management for wireless devices that connect and use a network service.
  • GTP General packet radio service Tunneling Protocol
  • GTPv2 GTP version 2
  • the second network node 103 e.g. the PCRF
  • the first network node 101 e.g. PGW not only per APN, but also per wireless device identifier, e.g. I MSI NS, MSISDN, and other selection algorisms may also be used. See the following excerpted requirements:
  • a PCEF may be served by one or more PCRF nodes. The PCEF shall contact the
  • PCRF is just one of example of a second network node 103.
  • Other examples of a second node 103 are PCEF, Online Charging System (OCS), Radius server etc.
  • the issue is also valid in the other "direction", i.e. in the example embodiment of figure 1 c, e.g. when a first network node 101 , e.g. PGW, has received overload control information from the second network node 103, e.g. MME/SGSN.
  • a question is how the first network node 101 should report the overload control information to the third network node 105, e.g. PCRF.
  • the PCRF may authorize/modify PCC rules for the PDN connections associated with that overloaded second network node 103, e.g. MME/SGSN, to generate more signaling.
  • Step 200 The method for handling overload of a second network node 103 in a communications network 100 according to some embodiments will now be described with reference to the signaling diagram depicted in Figure 2.
  • the embodiment of the communications network 100 in figure 1 a is used as an example.
  • the method of figure 2 is equally applicable to the embodiments seen in figures 1 b and 1 c.
  • Method steps which are specific for each of the embodiments in figures 1 b and 1 c will be described with reference to figures 3, 4 and 5.
  • the method of figure 2 comprises the following steps, which steps may as well be carried out in another suitable order than described below: Step 200
  • the third network node 105 sends, to the first network node 101 , information indicating that it supports receipt of overload information and that it has capability to control overload, i.e. that it is capable of receiving overload information.
  • Step 202 The second network node 103 is overloaded. Step 202
  • the first network node 101 detects that the second network node 103 is overloaded.
  • the detection may be that the first network node 101 receives information indicating the overload from the overloaded second network node 103 (indicated with a dotted arrow in figure 2).
  • the received information may further comprise information which indicates how much the third network node 105 needs to reduce its signaling towards the second network node 103 to control the overload.
  • the overload detection may be done internally within the first network node 101 , e.g. based on the number of unreplied messages sent to the second network node 103 and/or based on the average response time from the second network node 103.
  • the first network node 101 transmits information indicating that the second network node 103 is overloaded together with information indicating an identity of the second network node 103.
  • the information indicating the identity of the second network node will be referred to as second network node ID for the sake of simplicity.
  • the transmitted information indicates how much the third network node 105 needs to reduce its signaling towards the second network node 103 to control the overload, i.e. an amount of signaling to be reduced.
  • the third network node 105 receives the information in step 203 and, preferably based on this received information, obtains information indicating at least one PDN connection associated with the second network node ID. Step 205
  • the third network node 105 determines to apply overload control towards the second network node identified by the second network node ID and the obtained associated at least one PDN connection from step 204. This control may be to discard 3 of every 10 messages to be sent.
  • the third network node 305 transmits the controlled signaling towards the second network node 103 which substantially mitigates the overload in the second network node 103.
  • the method for handling overload of a second network node 103 in a communications network 100 will now be described with reference to the signaling diagram depicted in Figure 3.
  • the embodiment of the communications network 100 in figure 1 b applies.
  • the first network node 101 is e.g. a PGW or a GGSN
  • the second network node 103 is e.g. a PCRF, PCEF, OCS or a Radius server
  • the third network node 105 is e.g. a MME, a SGSN, a ePDG, a TWAN or a SGW.
  • the method comprises the following steps, which steps may as well be carried out in another suitable order than described below:
  • Step 301 corresponds to step 200 in figure 2.
  • the third network node 105 sends, to the first network node 101 , information indicating that it supports receipt of overload information and that it has capability to control overload, i.e. that it is capable of receiving overload information.
  • the second network node 103 at creation of a PDN connection, the second network node 103
  • the identification of the second network node 103 may be an explicit identification or an index to a location where the identification is found.
  • the identification may also be any other implicit identification, such as for example embedding the identification in an octet of the TEI D-C range.
  • the PDN connection information may comprise any suitable explicit or implicit identification of the PDN connection.
  • a PGW provides connectivity from a wireless device to a PDN by being the point of entry and/or exit of the traffic for the wireless device, and a wireless device may have simultaneous connectivity with more than one PGW for accessing multiple PDNs.
  • a PDN connection is the association between the wireless device and the PDN.
  • the second network node obtains information indicating the PDN connection during the PDN connection establishment procedure.
  • the PDN connection maybe represented by for example an Internet Protocol (IP) address together with an Access Pont Name (APN).
  • IP Internet Protocol
  • API Access Pont Name
  • the creation of the PDN connection may involve a PDN create session establishment procedure with for example the messages PDN create session Request and PDN create session Response.
  • figure 3 illustrates an embodiment where the second network node is a PCRF, PCEF, OCS or a Radius server.
  • a PCRF, PCEF, OCS or a Radius server would not be changed during the lifetime of a PDN connection. So as long as at the first network node 101 comprises the second network node address ID in the response
  • the third network node 105 may store the second network node ID and transfer it to the next second network node.
  • the third network node 105 stores the second network node ID together with the information indicating the PDN connection. This way, the third network node 105 comprises stored information about the association between the second network node ID and the PDN connection.
  • the information may be stored in for example the form of a table having the node ID in one column and the associated PDN connection in the other column.
  • Step 304 corresponds to step 201 in figure 2.
  • the second network node is overloaded. Step 304
  • the first network node 101 detects that the second network node 103 is overloaded.
  • the detection may be that the first network node 101 receives information indicating the overload from the overloaded second network node 103 (indicated with a dotted arrow in figure 3).
  • the received information may further comprise information which indicates how much the third network node 105 needs to reduce its signaling towards the second network node 103 to control the overload.
  • the overload detection may be done internally within the first network node 101 .
  • the first network node 101 transmits, to the third network node 105, information indicating that the second network node 103 is overloaded together with information indicating an identity of the second network node 103.
  • the transmitted information indicates how much the third network node 105 needs to reduce its signaling towards the second network node 103 to control the overload.
  • This step corresponds to step 204 in figure 2.
  • the third network node 105 receives the information in step 305 and, preferably based on this received information, obtains information indicating at least one PDN connection associated with the second network node ID.
  • the third network node 105 uses the stored information from step 302 to find which PDN connection that is associated with the second network ID that was sent from the first network node in step 305.
  • the third network node will only perform signaling reduction for those PDN connection associated with the overloaded node.
  • a PGW may be connected to several PCRFs, but maybe only one of the PCRFs is overloaded. Therefore should signaling reducing be performed towards that overloaded PCRF.
  • the third network node 105 may get to know which second network node 103 that is associated with a given PDN connection during e.g. a PDN connection creation
  • the second network node 103 e.g. a PCRF, would not be changed during the lifetime of a PDN
  • the third network node 105 For the embodiment of the communications network 100 illustrated in figure 1 c, for the transmission of the overload information to the third network node 105, e.g. a PCRF, the third network node 105 need to know which second network node 103 is associated with a given PDN connection. So during an inter-second network node change, the updated Identifier may need to be report to the third network node 105.
  • the third network node 105 e.g. a PCRF
  • This step corresponds to step 205 in figure 2.
  • the third network node 105 determines to apply overload control towards the second network node identified by the second network node ID and the obtained associated at least one PDN connection from step 306.
  • This step corresponds to step 206 in figure 2.
  • the third network node 305 transmits the controlled signaling towards the second network node 103 which substantially mitigates the overload in the second network node 103.
  • FIG. 15 The method for handling overload of a second network node 103 in a communications network 100 according to some embodiments will now be described with reference to the signaling diagram depicted in Figure 4.
  • the embodiment of the communications network 100 in figure 1 b also applies. This implies that figure 4 describes the method in the embodiment where the first network node 101 is e.g. a PGW or a GGSN, where the second network node
  • the method comprises the following steps, which steps may as well be carried out in another suitable order than described below:
  • the third network node 105 sends, to the first network node 101 , information indicating that it supports receipt of overload information and that it has capability to control overload, i.e. that it is capable of receiving overload information.
  • Step 402 corresponds to step 201 in figure 2 and step 303 in figure 3.
  • the second network node 103 is overloaded, which is in this embodiment for example a PCRF, PCEF, OCS or a Radius server.
  • the first network node 101 detects that the second network node 103 is overloaded.
  • the detection may be that the first network node 101 receives information indicating the overload from the overloaded second network node 103 (indicated with a dotted arrow in figure 2).
  • the received information may further comprise information which indicates how much the third network node 105 needs to reduce its signaling towards the second network node 103 to control the overload.
  • the overload detection may be done internally within the first network node 101.
  • the first network node 101 transmits information indicating that the second network node 103 is overloaded together with information indicating an identity of the second network node 103.
  • the information indicating the identity of the second network node will be referred to as second network node ID for the sake of simplicity.
  • the second network node ID is for example an IMSI NS, MSISDN NS or any charging characteristics.
  • the transmitted information indicates how much the third network node 105 needs to reduce its signaling towards the second network node 103 to control the overload.
  • This step corresponds to step 204 in figure 2 and to step 306 in figure 3.
  • the third network node 105 receives the information in step 403 and, preferably based on this received information, obtains information indicating at least one PDN connection associated with the second network node ID.
  • This step corresponds to step 205 in figure 2 and to step 307 in figure 3.
  • the third network node 105 determines to apply overload control towards the second network node identified by the second network node ID and the obtained associated at least one PDN connection from step 204.
  • This step corresponds to step 206 in figure 2 and to step 308 in figure 3.
  • the third network node 305 transmits the controlled signaling towards the second network node 103 which substantially mitigates the overload in the second network node 103.
  • FIG 5 describes the method in the embodiment where the first network node 101 is e.g. a PGW or a GGSN, where the second network node 103 is e.g. a MME, a SGSN, an ePDG, a TWAN or a SGW and where the third network node 105 is e.g. a PCRF, PCEF, OCS or a Radius server.
  • the method comprises the following steps, which steps may as well be carried out in another suitable order than described below: Step 500
  • the third network node 105 sends, to the first network node 101 , information indicating that it supports receipt of overload information and that it has capability to control overload, i.e. that it is capable of receiving overload information.
  • the second network node 103 transmits, to the third network node 105, information indicating identification of the second network node 103 and information indicating the PDN
  • the identification of the second network node 103 may be an explicit
  • the identification may also be any other implicit identification, such as for example embedding the
  • the TEID-C range may be assigned during a PDN connection creation procedure.
  • the PDN connection information may comprise any suitable explicit or implicit identification of the PDN connection.
  • IP-CAN is an access network that provides IP connectivity.
  • the IP-CAN procedure may be for example a session establishment procedure or a session modification procedure.
  • the IP-CAN session establishment may correspond to an IP address assignment. So, if the same wireless device is assigned multiple IP addresses (for example, if the same wireless device is assigned an IPv4 and IPv6 address), each such address assignment is considered as a new IP-CAN session establishment.
  • An IP-CAN procedure is associated with a PDN connection. For example, a PCEF establishes the IP-CAN Session during the Gateway Control session establishment. This happens when the wireless device
  • the PCEF is a functional entity in the Gateway node implementing the IP access to the PDN.
  • the second network node 103 obtains the information indicating the PDN connection during the IP_CAN session establishment procedure, which as part of a PDN connection establishment procedure.
  • An IP-CAN session establishment procedure is to setup an association between the PCEF and the PCRF for the PDN connection, to allow the PCRF to provide policy and charging control. It is the same wireless device IP address and APN which may be used to identify the IP-CAN.
  • the third network node 105 stores the second network node ID together with the information indicating the PDN connection. This way, the third network node 105 comprises stored information about the association between the second network node ID and the PDN connection.
  • the information may be stored in for example the form of a table having the node ID in one column and the associated PDN connection in the other column.
  • This step corresponds to step 201 in figure 2, step 303 in figure 2 and step 401 in figure 4.
  • the second network node 103 is overloaded.
  • the first network node 101 detects that the second network node 103 is overloaded.
  • the detection may be that the first network node 101 receives information indicating the overload from the overloaded second network node 103 (indicated with a dotted arrow in figure 5).
  • the received information may further comprise information which indicates how much the third network node 105 needs to reduce its signaling towards the second network node 103 to control the overload.
  • the overload detection may be done internally within the first network node 101.
  • This step corresponds to step 203 in figure 2, step 305 in figure 3 and step 403 in figure 4.
  • the first network node 101 transmits information indicating that the second network node 103 is overloaded together with information indicating an identity of the second network node 103.
  • the transmitted information indicates how much the third network node 105 needs to reduce its signaling towards the second network node 103 to control the overload.
  • This step corresponds to step 204 in figure 2, step 306 in figure 3 and step 404 in figure 4.
  • the third network node 105 receives the information in step 505 and, preferably based on this received information, obtains information indicating at least one PDN connection associated with the second network node ID.
  • the third network node 105 uses the stored information from step 502 to find which PDN connection that is associated with the second network ID that was sent from the first network node in step 505.
  • This step corresponds to step 205 in figure 2, step 307 in figure 3 and step 405 in figure 4.
  • the third network node 105 determines to apply overload control towards the second network node identified by the second network node ID and the obtained associated at least one PDN connection from step 506.
  • This step corresponds to step 206 in figure 2, step 308 in figure 3 and step 406 in figure 4.
  • the third network node 305 transmits the controlled signaling towards the second network node 103 which substantially mitigates the overload in the second network node 103.
  • the PGW may transfer such information to the MME/SGSN, to request the MME/SGSN to suppress sending GTP messages which trigger Gx signaling more than what the PCRF may handle. This requires that the MME/SGSN may associate the PDN connection to that overloaded PCRF.
  • the Gx signaling mentioned above is signaling on a Gx interface.
  • the Gx interface is between the PCRF and the PCEF.
  • the Gx interface is responsible for e.g. provisioning and removal of Policy and Charging Control (PCC) rules from the PCRF to the PCEF, transmission of traffic plane events from the PCEF to the PCRF, charging control, policy control or both.
  • PCC Policy and Charging Control
  • information indicating the identity of the second network node 103 e.g. a PCRF identifier, an OCS identifier or the index of them is provided by the first network node 101 via an explicit information element.
  • the information element comprises the second network node ID or an index of the second network node ID.
  • the second network node ID is provided implicitly to the first network node 101.
  • the first network node 101 may embed the index of second network node 103 in some bits of TEID.
  • the number of bits and position of those bits in the TEID are subject for standardization or by configuration based on operators provisioning.
  • the PGW 101 is connected with PCRF1 , PCRF2, OCS1 , OCS2 and Radius server 1.
  • the PGW 101 allocates TEID-C for a given PDN connection at creation. E.g. four bits in the TEID-C is used to identify the second network node 103 and starting from the second Octet of the TEID-C.
  • the TEID-C "xx 1x xx xx" may be allocated.
  • the TEID-C "xx 2x xx xx” may be allocated.
  • the MME/SGSN later receives overload control information associated with the TEID-C "xx 2x xx xx" from the PGW, the MME/SGSN shall perform signaling reduction only for the PGW TEID-C with "xx 2x xx xx". This is because the MME already knows which PGW is used for a certain PDN connection, and by using an "index" that points to a certain second network node 103, e.g.
  • PCRF PCRF
  • the first network node 101 e.g. the PGW
  • the parameters which are used for the selection of second network node 103 by the PGW directly with the overload control information may be e.g. IMSI Number Series, MSISDN NS, Charging Characteristics and so on.
  • the parameters are provide together with the overload control information to indicate to the MME/SGSN that signaling reduction (which may be indicated in the Overload Control information) is only applicable to those IMSI NS, MSISDN and so on.
  • the method for handling overload of the second network node 103 in the communications network 100 will now be described with reference to the signaling diagram depicted in Figure 6.
  • the first network node 101 is exemplified with a PGW
  • the second network node 103 is exemplified with a PCRF
  • the third network node 105 is exemplified with a MME, i.e. corresponding to the embodiment of the communications network 100 illustrated in figure 1 b.
  • the reference number 101 is therefore used when referring to the PGW
  • the reference number 103 is used when referring to the PCR
  • the reference number 105 is used when referring to the MME.
  • the PCRF 103 is the overloaded node
  • the MME 105 is the node which controls the overload.
  • a SGW 110 is illustrated in figure 6.
  • the method shown in figure 6 comprises an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) initial attach (steps 601-604) and a subsequent Service Request procedure with User Location Information (ULI) included (steps 606-609).
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • UMI User Location Information
  • the Service Request procedure triggers S5/S8 signaling towards the PGW 101 .
  • the PCRF 103 has been overloaded (step 605).
  • the method comprises the following steps, which steps may as well be carried out in another suitable order than described below:
  • the MME 105 sends a Create Session Request message to the SGW 1 10.
  • the message comprises information which indicates that the MME 105 supports receipt of overload information and that the MME 105 is capable of controlling overload of the second network node 103.
  • This information may be in the form of a flag, e.g. referred to as a "downstream node Flag".
  • downstream node Flag may be in the form of an Information Element (IE)
  • IE Information Element
  • the PCRF 103 which the MME 105 is capable of overload controlling may be identified with a TEID-C range, or additional parameters, e.g. I MSI NS, or any suitable given second network node identifier as described above in the three alternatives.
  • This step is part of the E-UTRAN initial attach procedure.
  • the SGW 1 10 forwards the Create Session Request message from step 301 to the PGW 101.
  • the PGW 101 may keep the information untouched which indicates that the MME 105 supports receipt of overload information and that the MME 105 is capable of controlling overload of the PCRF 103 if the PGW 101 supports this received information, i.e. if it supports the IE.
  • This step is part of the E-UTRAN initial attach procedure.
  • the PGW 101 sends a Create Session Response message to the SGW 110.
  • This Create Session Response message is a response to the Create Session Request message in step 602.
  • the messages comprises the same information as the Create Session Request message, i.e. the information which indicates that the MME 105 supports receipt of overload information and that the MME is capable of controlling overload of the PCRF 103.
  • the information is repeated in the Create Session Response message as a confirmation that the PGW 101 supports this function.
  • the Create Session Response message may comprise an identifier of the second network node 103.
  • the identifier of the PCRF 103 may be comprised in the response message in case alternative 1 ) of how to link the PDN connection with the overloaded PCRF 103 is used.
  • This step is part of the E-UTRAN initial attach procedure.
  • the SGW 1 10 forwards the Create Session Response message to the MME 105. It is the same message as in step 603 which is forwarded to the MME 105.
  • the PGW 101 detects that the PCRF 103 has overloaded.
  • the detection may be that the PGW 101 receives information indicating that the PCRF 103 has overloaded, , as seen with the arrow 605 in figure 6, or that the PGW 101 detects the overload using internal algorithms within the PGW 101 e.g. algorithms using such parameters at the number of un-replied messages sent to the PCRF 103 and/or the average response time from the PCRF 103.
  • the PGW 101 may also in this embodiment determine the how much the signaling should be reduced towards the PCRF 103 to control the overload.
  • the amount of signaling may be for example a percentage figure.
  • the overload information received from the PCRF 103 may for example comprise a request for that there should be a 30% signaling reduction towards the PCRF 103.
  • the MME 105 sends a Modify Bearer Request message to the SGW 1 10.
  • the Modify Bearer Request message may comprise User Location Information (ULI).
  • ULI may comprise information indicating the location of the user, i.e. the wireless device. Such information may be represented by e.g. Cell Global Identification (CGI), Service Area Identification (SAI), E-UTRAN Cell Global Identification (ECGI), Tracking Area Identity (TAI) or Routing Area Identity (RAI).
  • CGI Cell Global Identification
  • SAI Service Area Identification
  • ECGI E-UTRAN Cell Global Identification
  • TAI Tracking Area Identity
  • RAI Routing Area Identity
  • the SGW 1 10 forwards the Modify Bearer Request message to the PGW 101.
  • the forwarded message is the same message as in step 606.
  • This step corresponds to step 203 in figure 2 and to step 403 in figure 4.
  • the PGW 101 sends a Modify Bearer Response message to the SGW 1 10.
  • the PGW 101 comprises overload control information in the Modify Bearer Request message.
  • the overload control information may be a request to reduce the signaling with 30% towards the PCRF 103.
  • the Modify Bearer Response message may further comprise information which identifies the PCRF 103. Such identifying information may be an explicit PCRF ID or an index which points to the PCRF ID.
  • the identifying information may be a TEID-C range (which is for the PDN Connections associated with that PCRF 103), or an IMSI NS (which is for the PDN Connections associated with that PCRF 1013, i.e. PCRF 103 is selected using IMSI NS).
  • This step corresponds to step 203 in figure 2 and to step 403 in figure 4.
  • the SGW 110 forwards the Modify Bearer Response message to the MME 105.
  • the forwarded message is the same as the Modify Bearer Response message transmitted in step 308.
  • Step 610
  • This step corresponds to step 206 in figure 2, step 308 in figure 3, step 406 in figure 4 and step 508 in figure 5.
  • the MME 103 is able to control the overload of the PCRF 103, e.g. by performing signaling reduction with the requested rate towards the specific PCRF 103.
  • FIG. 7a and 7b illustrate the first network node 101 and the second network node 103 and exemplified with a second MME2 103 and the third network node 105 is exemplified with a PCRF 105, i.e. the embodiment of the communications network 100 seen in figure 1 c.
  • Figures 7a and 7b illustrates the following further nodes which may also be comprised in the communications network 100 illustrated in figures 1 a-c: a SGW 1 10 and a first MME1 113.
  • the second MME2 103 is the overloaded node and the PCRF is the overload control node.
  • the MME is just an example of the overloaded node and that the overloaded node may be any other node such as a SGSN, an MME, an ePDG, an SGW, a TWAN.
  • the PGW is just an example of the first network node 101 and that the first network node may also be for example a GGSN.
  • figure 7a and figure 7b depicts how the MME identifier is sent to the PCRF during an IP-CAN session establishment and session modification procedure (where there is and inter MME mobility procedure).
  • An inter MME TAU is used as an example.
  • Figure 7a comprises steps 701-706 and illustrates an embodiment of an E-UTRAN initial attach procedure, where an identifier of the second MME2 103 is provided to the third network node 105.
  • Figure 7b comprises steps 707-724. Steps 707-713 in figure 7b illustrate an embodiment of a Tracking Area Update (TAU) or Routing Area Update (RAU) procedure without a SGW change procedure.
  • TAU Tracking Area Update
  • RAU Routing Area Update
  • Steps 714-724 illustrates an embodiment of a PCRF initiated IP-CAN session modification procedure.
  • figures 7a and 7b may comprise further steps which are not shown in figure 7.
  • the method exemplified in figures 7a and 7b is a PCRF 105 initiated IP-CAN session modification procedure, where PCC rule(s) comprises a lead dedicate bearer creation over a GTP interface while the MME2 103 has overloaded.
  • the MME2 103 comprises Overload control information in its Create Bearer Response message and the PGW 101 transfers the overload information to the PCRF 105 in the new CCR update message, so that the PCRF 105 may perform signaling reduction towards the MME2 103, if such Gx signaling leads the GTP signaling towards the MME2 103.
  • Step 702 This step is seen in figure 7a. This step is part of the E-UTRAN initial attach procedure.
  • the first MME1 1 13 sends a Create Session Request message to the SGW 1 10.
  • Step 702 The first MME1 1 13 sends a Create Session Request message to the SGW 1 10.
  • Step 7a This step is seen in figure 7a. This step is part of the E-UTRAN initial attach procedure.
  • the SGW 1 10 forwards the Create Session Request message to the PGW 101.
  • the Create Session Request message is the same message as the one in step 701.
  • This step is seen in figure 7a. This step corresponds to step 301 in figure 3 and step 501 in figure 5. This step is part of the E-UTRAN initial attach procedure.
  • the SGW 1 10 sends a Credit Control Request (CCR) Initial message to the PCRF 105.
  • the CCR message comprises a MME identifier.
  • CCR is one of two Diameter messages which are used to support Credit Control via the Diameter protocol. The purpose of the diameter credit control is to provide a framework for real-time charging. CCR is used to request credit authorization for a given service.
  • the PCRF 105 stores IP-CAN session information together with the identifier of the MME1 1 13. Step 704
  • This step is seen in figure 7a. This step is part of the E-UTRAN initial attach procedure.
  • the PCR 105 sends a Credit-Control-Answer (CCA) initial message to the PGW 101.
  • CCA Credit-Control-Answer
  • the CCA initial message is a response to the CCR message in step 703.
  • the CCA Credit-Control-Answer
  • the 5 message may comprise an Event Trigger - MME change.
  • the CCA message is the second of the two Diameter messages which are used to support Credit Control via the Diameter Protocol.
  • CCA is used to acknowledge the CCR message.
  • the PCRF 105 If the PCRF 105 is configured 10 to perform overload control towards the MME (when the MME is overloaded), it needs to ask the PGW 101 to report if the MME has changed (due to mobility procedure of the wireless device). Therefore, the PCRF 105 needs to keep track of which MME is associated with the specific PDN connection/I P-CAN session. So later on, when the PCRF 105 receives the information indicating that the MME2 103 is overloaded and
  • the PCRF 105 may apply overload control.
  • the overload control implies that the PCRF 105 does not send any more signaling to the MME2 103 than it can handle.
  • the purpose of the Event Trigger is to inform the PGW 101 that the PCRF 105 supports this feature and that it needs to keep track of the MME.
  • This step is seen in figure 7a. This step is part of the E-UTRAN initial attach procedure.
  • the PGW 101 sends a Create Session Response message to the SGW 1 10.
  • This Create Session Response message is a response to the message in step 702.
  • This step is seen in figure 7a. This step is part of the E-UTRAN initial attach procedure.
  • the SGW 1 10 forwards the Create Session Response message to the first MME1 1 113.
  • This Create Session Response message is the same message as the one sent in step 30 705.
  • This step is seen in figure 7b. This step is part of the subsequent inter MME TAU/RAU procedure. A context transfer takes place between the first MME1 1 13 and the second 35 MME2 103. Stop 708
  • This step is seen in figure 7b. This step is part of the subsequent inter MME TAU/RAU procedure.
  • the second MME2 103 sends a Modify Bearer Request message to the SGW 5 1 10.
  • This step is seen in figure 7b. This step is part of the subsequent inter MME TAU/RAU procedure.
  • the SGW 1 10 forwards the Modify Bearer Request message to the PGW 10 101 .
  • the forwarded Modify Bearer Request message is the same message as the one in step 708.
  • the PGW 101 sends a CCR update message to the PCRF 105.
  • the CCR update message may comprise an updated MME Identifier, i.e. the MME2 103 identifier.
  • the PCRF 105 which is the node that will control overload later, comprises the identity of MME2 103.
  • the PCRF 105 sends a CCA update message to the PGW 101.
  • the CCA update message may comprise an Event Trigger - MME change.
  • This step is seen in figure 7b. This step is part of the subsequent inter MME TAU/RAU procedure.
  • the PGW 101 sends a Modify Bearer Response to the SGW 1 10.
  • This step is seen in figure 7b. This step is part of the subsequent inter MME TAU/RAU procedure.
  • the SGW 110 forwards the Modify Bearer Response message to the second MME2 103.
  • the forwarded Modify Bearer Response message is the same message as in step 712.
  • This step is seen in figure 7b. This step is part of the PCRF initiated IP-CAN session modification procedure.
  • the PCRF 105 sends a Re-Authorization Request message to the PGW 101 .
  • the PGW 101 sends a Re-Authorization Acknowledgement message to the PCRF 105.
  • the Re-Authorization Acknowledgement message is a response to the Re-Authorization Request message in step 714.
  • Step 717 The PGW 101 sends a Create Bearer Request message to the SGW 1 10. Step 717
  • Step 7b This step is seen in figure 7b.
  • the SGW 1 10 forwards the Create Bearer Request message to the second MME2 103.
  • the forwarded Create Bearer Request message is the same message as in step 716.
  • Step 718
  • Step 719 This step is seen in figure 7b.
  • the MME2 103 is overloaded.
  • the MME2 determines that the signaling needs to be reduced with a certain amount, e.g. 30%. Step 719
  • This step is seen in figure 7b.
  • the second MME2 103 sends a Create Bearer Response to the SGW 1 10.
  • This Create Bearer Response is a response to the request message sent in step 717.
  • the MME2 103 has overloaded in step 718 and provides information indicating the overload in the Create Bearer Response.
  • the information may be for example a request for signaling reduction of 30%.
  • the Create Barer Response comprises the MME2 identifier.
  • the SGW 1 10 forwards the Create Bearer Response message from step 719 to the PGW 101.
  • the forwarded Create Bearer Response comprises the overload information and the MME2 identifier.
  • This step is seen in figure 7b.
  • This step corresponds to step 203 in figure 2, step 305 in figure 3, step 403 in figure 4, step 505 in figure 5 and steps 608 and 609 in figure 6.
  • the PGW 101 sends a CCR update message to the PCRF 105.
  • the CCR update message comprises the overload information from MME2 103 together with the MME2 identifier.
  • the PCRF 105 sends a CCA update message to the PGW 101.
  • the CCA update message is a response to the CCR update message in step 721.
  • the CCA update message may comprise an Event Trigger - MME change.
  • the Event Trigger is the same as described above.
  • the PCRF 105 stores the information indicating that MME2 has overloaded together with the MME2 identifier and determines to apply overload control towards the MME2.
  • the PCRF 105 sends controlled signaling towards the MME2 103. For example, when the PCRF 105 sends Gx signaling to the PGW 101 which trigger further bearer signaling towards the MME2 103, the PCRF 105 applies signaling overload control as requested by the MME2 103 in the step 719.
  • Figure 8 is a flowchart describing the present method in the first network node 101 , for handling overload of a second network node 103 in a
  • the second network node 103 is represented by a PCRF, a PCEF, an OCS or a Radius Server and the third network node 101 is represented by a MME, a SGSN, an ePDG, a TWAN or a SGW.
  • the second network node 103 is represented by a MME, a SGSN, an ePDG, a TWAN or a SGW and the third network node 101 is represented by one of a PCRF, PCEF, OCS or Radius Server.
  • the method comprises the following steps to be performed by the first network node 101 , which steps may be performed in any suitable order than described below:
  • the first network node 101 receives, from the third network node 105, information indicating that the third network node 105 supports receipt of overload information and that the third network node 105 is capable of controlling the overload of the second network node 103.
  • the first network node 101 transmits, to the third network node 105, information indicating the identity of the second network node 103 and information indicating the created PDN connection associated with the second network node 103.
  • the information indicating the identity of the second network node 103 may be one of an explicit identity of the second network node 103, an index indicating the identity of the second network node 103, a TEID-C range, an IMSI NS, a MSISDN and a charging characteristic.
  • the first network node 101 transmits, to the third network node 105, information indicating the identity of the second network node 103 and information indicating the PDN connection associated with the second network node 103.
  • the IP-CAN procedure may be an IP-CAN session establishment procedure or an IP- CAN session modification procedure.
  • the information indicating the PDN connection may be at least one of an APN and an IP address.
  • This step corresponds to step 305 in figure 3, step 403 in figure 4, step 505 in figure 5, step 608 in figure 6 and step 721 in figure 7.
  • the first network node 101 transmits, to the third network node 105, information indicating that the second network node 103 is overloaded and information indicating the identity of the second network node 103.
  • the information indicating the PDN connection may be at least one of an APN and an IP address.
  • the first network node 101 itself detects that the second network node 103 is overloaded. In some embodiments, the first network node 101 detects that the second network node 103 is overloaded by receiving information indicating the overload from the second network node 103.
  • the information indicating that the second network node 103 is overloaded comprises information indicating how much, i.e. the amount, the third network node 103 should reduce its signaling traffic towards the second network node to control the overload of the second network node 103.
  • the first network node 101 comprises an arrangement as shown in Figure 9.
  • the second network node 103 is represented by a PCRF, a PCEF, an OCS or a Radius Server
  • the third network node 101 is represented by a MME, a SGSN, an ePDG, a TWAN or a SGW.
  • the first network node 101 when the first network node 101 is represented by a PGW or a GGSN, then the second network node 103 is represented by a MME, a SGSN, an ePDG, a TWAN or a SGW and the third network node 101 is represented by one of a PCRF, PCEF, OCS or Radius Server.
  • the first network node 101 comprises a transmitter 901 which is adapted to detect overload of the second network node 103 and then transmit, to the third network node 105, information indicating that the second network node 103 is overloaded and information indicating the identity of the second network node 103. 22.
  • the transmitter 901 is further adapted to, during a PDN connection creation procedure, transmit, to the third network node 105, information indicating the identity of the second network node 103 and information indicating the created PDN connection associated with the second network node 103.
  • the transmitter 901 is further adapted to, during an IP-CAN procedure for a PDN connection, transmit, to the third network node 105, information indicating the identity of the second network node 103 and information indicating the PDN connection associated with the second network node 103.
  • the information indicating the PDN connection may be at least one of an APN and an IP address.
  • the information indicating the identity of the second network node 103 may be one of an explicit identity of the second network node 103, an index indicating the identity of the second network node 103, a TEID-C range, an IMSI NS, a MSISDN and a charging characteristic.
  • the first network node 101 comprises a receiver 903 which is adapted to receive, from the third network node 105, information indicating that the third network node 105 supports receipt of overload information and that the third network node 105 is capable of controlling the overload of the second network node 103.
  • the first network node 101 itself detects that the second network node 103 is overloaded. In some embodiments, the first network node 101 detects that the second network node 103 is overloaded by receiving information indicating the overload from the second network node 103.
  • the information indicating that the second network node 103 is overloaded comprises information indicating how much the third network node 103 should reduce its signaling traffic towards the second network node to control the overload of the second network node 103.
  • the first network node 1001 may further comprise a memory 905 comprising one or more memory units.
  • the memory 905 is arranged to be used to store data, received data streams, power level measurements, overload information, information indicating the identity of the second network node 103, information indicating the PDN connection, information indicating overload, threshold values, time periods, configurations, scheduling, and applications to perform the methods herein when being executed in the first network node 101.
  • the transmitter 901 and receiver 903 described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g. stored in a memory, that when executed by the one or more processors such as the processor 910 perform as described below.
  • processors may be comprised in a single application-specific integrated circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a-chip (SoC).
  • ASIC application-specific integrated circuit
  • SoC system-on-a-chip
  • Figure 10a and figure 10b is a flowchart describing the present method in the third network node 105, for handling overload of a second network node 103 in a communications network 100.
  • Figure 10a shows steps 1000-1005 and figure 10b shows steps 1006-1010.
  • the first network node 101 is represented by a PGW or a GGSN
  • the second network node 103 is represented by a PCRF, a PCEF, an OCS or a Radius Server
  • the third network node 101 is represented by a MME, a SGSN, an ePDG, a TWAN or a SGW.
  • the first network node 101 when the first network node 101 is represented by a PGW or a GGSN, then the second network node 103 is represented by a MME, a SGSN, an ePDG, a TWAN or a SGW and the third network node 101 is represented by one of a PCRF, PCEF, OCS or Radius Server.
  • the method comprises the following steps, which steps may be performed in any suitable order than described below: Step 1000
  • the third network node 105 transmits, to the first network node 101 , information indicating that the third network node 105 supports receipt of overload information and that the third network node 105 is capable of controlling the overload of the second network node 103.
  • the third network node 105 receives, from the first network node 101 , information indicating the identity of the second network node 103.
  • the information indicating the identity of the second network node 103 may be one of an 5 explicit identity of the second network node 103, an index indicating the identity of the second network node 103, a TEID-C range, an IMSI NS, a MSISDN and a charging characteristic.
  • This step is seen in figure 10a. This step corresponds to step 301 in figure 3 and to steps 703 and 71 1 in figure 7.
  • the third network node 105 obtains information indicating the created PDN connection associated with the second network node 103.
  • the third network node 105 stores the received information indicating the identity of the second network node 103 and information indicating the created PDN connection associated with the second network 20 node 103.
  • this step is seen in figure 10a. This step corresponds to step 501 in figure 5.
  • the third network node 25 105 receives, from the first network node 101 , information indicating the identity of the second network node 103.
  • Step 1006 This step is seen in figure 10a. This step corresponds to step 501 in figure 5.
  • the third network node 105 obtains information indicating the PDN connection associated with the second network node 103. Step 1006
  • the third network node 105 stores the received information indicating the identity of the second network node 103 and information indicating the PDN connection.
  • This step is seen in figure 10b.
  • This step corresponds to step 203 in figure 2, step 305 in figure 3, step 403 in figure 4, step 505 in figure 5, step 608 in figure 6 and to step 721 in figure 7.
  • the third network node 105 receives information, from a first network node 105, information indicating that the second network node 103 is overloaded and information indicating the identity of the second network node 103.
  • the information indicating that the second network node 103 is overloaded comprises information indicating how much the third network node 103 should reduce its signaling traffic towards the second network node 103 to control the overload of the second network node 103.
  • the third network node 105 obtains information indicating at least one PDN connection associated with the identity of the second network node 103.
  • the information indicating the PDN connection may be at least one of an APN and an IP address.
  • step 10b This step corresponds to step 306 in figure 3 and to step 506 in figure 5.
  • step 1008 This is a substep of step 1008.
  • the third network node 105 obtains information indicating the at least one PDN connection associated with the identity of the second network node 103 from the stored information, i.e. the information stored in step 1003 or in step 1006.
  • This step is seen in figure 10b. This step corresponds to step 205 in figure 2, step 307 in figure 3, step 405 in figure 4 and to step 507 in figure 5.
  • the third network node 105 determines to apply overload control towards the second network node and the associated at least one PDN connection for which information has been obtained.
  • the third network node 105 transmits controlled signaling traffic to the second network node 103 as determined in step 1009.
  • the third network node 105 comprises an arrangement as shown in Figure 11.
  • the second network node 103 is represented by a PCRF, a PCEF, an OCS or a Radius Server and the third network node 101 is represented by a MME, a SGSN, an ePDG, a TWAN or a SGW.
  • the second network node 103 is represented by a MME, a SGSN, an ePDG, a TWAN or a SGW and the third network node 101 is represented by one of a PCRF, PCEF, OCS or Radius Server.
  • the third network node 105 comprises a receiver 1101 which is adapted to receive information, from a first network node 101 , information indicating that the second network node 103 is overloaded and information indicating the identity of the second network node 103.
  • the information indicating that the second network node 103 is overloaded may comprise information indicating how much the third network node 103 should reduce its signaling traffic towards the second network node 103 to control the overload of the second network node 103.
  • the receiver 1 101 may be further adapted to, during a PDN connection creation procedure, receive, from the first network node 101 , information indicating the identity of the second network node 103.
  • the receiver 1101 may be further adapted to, during an IP-CAN procedure for a PDN connection, receive, from the first network node 101 , information indicating the identity of the second network node 103.
  • the third network node 105 comprises an obtaining unit 1103 adapted to obtain information indicating at least one PDN connection associated with the identity of the second network node 103.
  • the obtaining unit 1 103 may be further adapted to obtain information indicating the created PDN connection associated with the second network node 103.
  • the obtaining unit 1 103 may be further adapted to obtain information indicating the PDN connection associated with the second network node 103.
  • the obtaining unit 1 103 may be further adapted to obtain information indicating the at least one PDN 5 connection associated with the identity of the second network node 103 from the stored information.
  • the third network node 105 comprises a determining unit 1105 which is adapted to determine to apply overload control towards the second network node and the associated 10 at least one PDN connection for which information has been obtained.
  • the third network node 105 comprises a transmitter 1108 which is adapted to transmit, to the first network node 101 , information indicating that the third network node 105 supports receipt of overload information and that the third network node 15 105 is capable of controlling the overload of the second network node 103.
  • transmitter 1 108 may be further adapted to transmit controlled signaling traffic to the second network node 103 as determined.
  • the third network node 105 may further comprise a memory 1110 which is adapted to 20 store the received information indicating the identity of the second network node 103 and information indicating the created PDN connection associated with the second network node 103.
  • the memory 1 110 may be further adapted to store the received information indicating the identity of the second network node 103 and information indicating the PDN connection.
  • the memory 11 10 may comprise one or more memory units.
  • the memory 25 1 110 is arranged to be used to store data, received data streams, power level
  • overload information information indicating the identity of the second network node 103, information indicating the PDN connection, information indicating overload, threshold values, time periods, configurations, scheduling, and applications to perform the methods herein when being executed in the third network node 105.
  • the information indicating the PDN connection is at least one of an APN and an IP address.
  • the information indicating the identity of the second network node 103 may be one of an 35 explicit identity of the second network node 103, an index indicating the identity of the second network node 103, a TEID-C range, an IMSI NS, a MSISDN and a charging characteristic.
  • the transmitter 1 1 108, the receiver 1 101 , the obtaining unit 1 103 and the determining unit 1105 described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g. stored in a memory, that when executed by the one or more processors such as the processor 1 120 perform as described below.
  • processors as well as the other digital hardware, may be comprised in a single application-specific integrated circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a-chip (SoC).
  • ASIC application-specific integrated circuit
  • SoC system-on-a-chip
  • the present mechanism for handling overload of a second network node 103 in a communications network 100 may be implemented through one or more processors, such as a processor 901 in the first network node arrangement depicted in Figure 9 and a processor 1 120 in the third network node arrangement depicted in Figure 1 , together with computer program code for performing the functions of the embodiments herein.
  • the processor may be for example a Digital Signal Processor (DSP), Application Specific Integrated Circuit (ASIC) processor, Field-programmable gate array (FPGA) processor or microprocessor.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-programmable gate array
  • the program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the first network node 101 and/or the third network node 105.
  • One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick.
  • the computer program code may furthermore be provided as pure program code on a server and downloaded to the first network node 101 and/or the third network node 105.
  • the identifier of the second network node may be provided to the third network node.
  • the third network node may subscribe to a new Event Trigger (new for EPS) indicating a change of second network node, e.g. a MME/SGSN change.
  • EPS Event Trigger
  • the updated second network node identifier may be provided to the third network node.
  • the first network node reports and transfers overload control information to the third network node.
  • support for the embodiments herein may need to involve a handshake between the second network node 103 and the first network node 101 either via a new flag (comprised in the request and response message) along the PDN connection creation procedure, or a supported feature notification procedure.
  • the first network node 101 may transfer the overload information received from the second network node 103 to the third network node 105, so that the third network node 105 may perform signaling reduction towards a specific second network node 103. This requires that the first network node 101 should provide the second network node identifier to the third network node 105 during e.g. an IP-CAN session establishment.
  • One embodiment is directed to a method in a first network node for handling overload of a second network node in a communications network.
  • the method compromises that when overload of the second network node is detected, transmitting, to a third network node, information indicating that the second network node is overloaded and information indicating the identity of the second network node, so as to enable the third network node to control the overload of the second network node.
  • the method may further comprise receiving, from the third network node, information indicating that the third network node supports receipt of overload information and that the third network node is capable of controlling the overload of the second network node.
  • the method may further comprise transmitting, during a Packet Data Network, PDN, connection creation procedure, to the third network node, information indicating the identity of the second network node and information indicating the created PDN connection associated with the second network node.
  • the method may further comprise transmitting, during an Internet Protocol-Connectivity Access Network, IP-CAN, procedure for a Packet Data Network, PDN, connection, to the third network node, information indicating the identity of the second network node and information indicating the PDN connection associated with the second network node.
  • the information indicating the PDN connection may be at least one of an Access Point Name, APN, and an Internet Protocol, IP, address.
  • the information indicating the identity of the second network node may be one of: an explicit identity of the second network node, an index indicating the identity of the second network node, a Tunnel Endpoint IDentifier-Control plane, TEID-C, range, a International Mobile Subscriber Identity Number Series, IMSI NS, a Mobile Subscriber Integrated Services Digital Network number series, MSISDN, and a charging
  • the first network node may itself detect that the second network node is overloaded; or the first network node may detect that the second network node is overloaded by receiving information indicating the overload from the second network node.
  • the information indicating that the second network node is overloaded may comprise information indicating how much the third network node should reduce its signaling traffic towards the second network node to control the overload of the second network node.
  • the first network node may be represented by a PGW or a GGSN
  • the second network node may be represented by a Policy and Charging Rules Function, PCRF, a Policy and Charging Enforcement Function, PCEF, an Online Charging System, OCS, or a Radius Server
  • the third network node may be represented by a Mobility Management Entity, MME,, a Serving General packet radio service Support Node, SGSN, an evolved Packet Data Gateway, ePDG, a Trusted Wireless local area network Access Network, TWAN; or a Serving GateWay, SGW; or the first network node may be represented by a PGW or a GGSN
  • the second network node may be represented by a MME, a SGSN, an ePDG, a TWAN or a SGW
  • the third network node may be represented by one of a PCRF, PCEF, OCS or Radius Server.
  • One embodiment is directed to a method in a third network node for handling overload of a second network node in a communications network.
  • the method comprises receiving information from a first network node, indicating that the second network node is overloaded and information indicating the identity of the second network node;
  • PDN Packet Data Network
  • the method may further comprise transmitting, to the first network node, information indicating that the third network node supports receipt of overload information and that the third network node is capable of controlling the overload of the second network node.
  • the method may further comprise receiving, during a Packet Data Network, PDN, connection creation procedure, from the first network node, information indicating the identity of the second network node; and obtaining information indicating the created PDN connection associated with the second network node (103); and storing the received information indicating the identity of the second network node and information indicating the created PDN connection associated with the second network node.
  • PDN Packet Data Network
  • the method may further comprise receiving - during an Internet Protocol-Connectivity Access Network, IP-CAN, procedure for a Packet Data Network, PDN, connection - from the first network node, information indicating the identity of the second network node; and obtaining information indicating the PDN connection associated with the second network node; and storing the received information indicating the identity of the second network node and information indicating the PDN connection.
  • IP-CAN Internet Protocol-Connectivity Access Network
  • PDN Packet Data Network
  • the obtaining information indicating at least one Packet Data Network, PDN, connection associated with the identity of the second network node may further comprise: obtaining information indicating the at least one PDN connection associated with the identity of the second network node from the stored information.
  • the information indicating the PDN connection may be at least one of: an Access Point Name, APN, and an Internet Protocol, I P, address.
  • the method may further comprise: transmitting controlled signaling traffic to the second network node as determined.
  • the information indicating the identity of the second network node (103) may be one of: an explicit identity of the second network node, an index indicating the identity of the second network node, a Tunnel Endpoint IDentifier-Control plane, TEI D-C, range, a International Mobile Subscriber Identity Number Series, IMSI NS, a Mobile Subscriber Integrated Services Digital Network number, MSISDN and a charging characteristic.
  • the information indicating that the second network node is overloaded may comprise information indicating how much the third network node should reduce its signaling traffic towards the second network node to control the overload of the second network node.
  • the first network node may be represented by a PGW or a GGSN
  • the second network node (103) may be represented by a Policy and Charging Rules
  • the third network node may be represented by a Mobility Management Entity, MME, a Serving General packet radio service Support Node, SGSN, an evolved Packet Data Gateway, ePDG, a Trusted Wireless local area network Access Network, TWAN, or a Serving GateWay, SGW; or the first network node may be represented by a PGW or a GGSN, the second network node may be represented by a MME, a SGSN, an ePDG, a TWAN or a SGW and the third network node may be represented by one of a PCRF, PCEF, OCS or Radius Server.
  • One embodiment is directed to a first network node for handling overload of a second network node in a communications network.
  • the first network node comprises: a transmitter adapted to detect overload of the second network node and then transmit, to a third network node, information indicating that the second network node is overloaded and information indicating the identity of the second network node, so as to enable the third network node to control the overload of the second network node.
  • the first network node may further comprise: a receiver adapted to receive, from the third network node, information indicating that the third network node supports receipt of overload information and that the third network node is capable of controlling the overload of the second network node.
  • the transmitter may be further adapted to: during a Packet Data Network, PDN, connection creation procedure, transmit to the third network node, information indicating the identity of the second network node and information indicating the created PDN connection associated with the second network node.
  • PDN Packet Data Network
  • the transmitter may be further adapted to: during an Internet Protocol-Connectivity Access Network, IP-CAN, procedure for a Packet Data Network, PDN, connection, transmit, to the third network node, information indicating the identity of the second network node and information indicating the PDN connection associated with the second network node.
  • the information indicating the PDN connection may be at least one of an Access Point Name, APN, and an Internet Protocol, IP, address.
  • the information indicating the identity of the second network node may be one of an explicit identity of the second network node, an index indicating the identity of the second network node, a Tunnel Endpoint IDentifier-Control plane, TEID- C, range, a International Mobile Subscriber Identity Number Series, IMSI NS, a Mobile Subscriber Integrated Services Digital Network number series, MSISDN, and a charging characteristic.
  • the first network node may itself detect that the second network node is overloaded; or the first network node may detect that the second network node is overloaded by receiving information indicating the overload from the second network node.
  • the information indicating that the second network node is overloaded may comprise information indicating how much the third network node should reduce its signaling traffic towards the second network node to control the overload of the second network node.
  • the first network node may be represented by a PGW or a GGSN
  • the second network node may be represented by a Policy and Charging Rules Function, PCRF, a Policy and Charging Enforcement Function, PCEF, an Online Charging System, OCS, or a Radius Server
  • the third network node may be represented by a Mobility Management Entity, MME,, a Serving General packet radio service Support Node, SGSN, an evolved Packet Data Gateway, ePDG, a Terrestrial Wide Area Network, TWAN; or a Serving GateWay, SGW; or
  • the first network node may be represented by a PGW or a GGSN
  • the second network node may be represented by a MME, a SGSN, an ePDG, a TWAN or a SGW
  • the third network node may be represented by one of a PCRF, PCEF, OCS or Radius Server.
  • One embodiment is directed to a third network node for handling overload of a second network node in a communications network.
  • the third network node comprises: a receiver adapted to receive information, from a first network node, information indicating that the second network node is overloaded and information indicating the identity of the second network node; and an obtaining unit adapted to obtain information indicating at least one Packet Data Network, PDN, connection associated with the identity of the second network node); and a determining unit adapted to determine to apply overload control towards the second network node and the associated at least one PDN connection for which
  • the third network node may further comprise: a transmitter adapted to transmit, to the first network node, information indicating that the third network node supports receipt of overload information and that the third network node is capable of controlling the overload of the second network node.
  • the receiver may be further adapted to: during a Packet Data
  • Network, PDN, connection creation procedure receive, from the first network node, information indicating the identity of the second network node; and the obtaining unit may be further adapted to: obtain information indicating the created PDN connection
  • the third network node may further comprise: a memory adapted to store the received information indicating the identity of the second network node and information indicating the created PDN connection associated with the second network node.
  • the receiver may be further adapted to: during an Internet Protocol-Connectivity Access Network, IP-CAN, procedure for a Packet Data Network, PDN, connection, receive, from the first network node, information indicating the identity of the second network node (103); and the obtaining unit may be further adapted to: obtain information indicating the PDN connection associated with the second network node; and the third network node may further comprise: a memory adapted to store the received information indicating the identity of the second network node and information indicating the PDN connection.
  • the obtaining unit may be further adapted to: obtain information indicating the at least one PDN connection associated with the identity of the second network node from the stored information.
  • the information indicating the PDN connection may be at least one of an Access Point Name, APN, and an Internet Protocol, IP, address.
  • the third network node may further comprise: a transmitter adapted to transmit controlled signaling traffic to the second network node as determined.
  • the information indicating the identity of the second network node may be one of: an explicit identity of the second network node, an index indicating the identity of the second network node, a Tunnel Endpoint IDentifier-Control plane, TEID- C, range, a International Mobile Subscriber Identity Number Series, IMSI NS, a Mobile Subscriber Integrated Services Digital Network number, MSISDN and a charging characteristic.
  • the information indicating that the second network node is overloaded may comprise information indicating how much the third network node should reduce its signaling traffic towards the second network node to control the overload of the second network node.
  • the first network node may be represented by a PGW or a GGSN
  • the second network node may be represented by a Policy and Charging Rules Function, PCRF, a Policy and Charging Enforcement Function, PCEF, and Online Charging System, OCS, or a Radius Server
  • the third network node may be represented by a Mobility Management Entity, MME, a Serving General packet radio service Support Node, SGSN, an evolved Packet Data Gateway, ePDG, a Terrestrial Wide Area Network, TWAN, or a Serving GateWay, SGW; or the first network node may be represented by a PGW or a GGSN
  • the second network node may be represented by a MME, a SGSN, an ePDG, a TWAN or a SGW

Landscapes

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

Abstract

La présente invention a trait à un procédé réalisé dans un premier nœud de réseau (101) et à un premier nœud destiné à réaliser le procédé. Le procédé sert à traiter une surcharge d'un deuxième nœud de réseau (103) dans un réseau de communications (100). Le procédé consiste à : lorsqu'une surcharge du deuxième nœud de réseau (103) est détectée, transmettre (203, 305, 403, 505, 608, 721, 803), au troisième nœud de réseau (105), des informations indiquant que le deuxième nœud de réseau (103) est surchargé et des informations indiquant l'identité du deuxième nœud de réseau (103).
PCT/EP2013/070547 2013-10-02 2013-10-02 Traitement de surcharge d'un nœud de réseau Ceased WO2015048992A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2013/070547 WO2015048992A1 (fr) 2013-10-02 2013-10-02 Traitement de surcharge d'un nœud de réseau

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2013/070547 WO2015048992A1 (fr) 2013-10-02 2013-10-02 Traitement de surcharge d'un nœud de réseau

Publications (1)

Publication Number Publication Date
WO2015048992A1 true WO2015048992A1 (fr) 2015-04-09

Family

ID=49354635

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2013/070547 Ceased WO2015048992A1 (fr) 2013-10-02 2013-10-02 Traitement de surcharge d'un nœud de réseau

Country Status (1)

Country Link
WO (1) WO2015048992A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016201707A1 (fr) * 2015-06-19 2016-12-22 华为技术有限公司 Procédé de transfert d'informations d'état de réseau et dispositif de réseau
EP3883198A1 (fr) * 2020-03-20 2021-09-22 Nokia Technologies Oy Contrôle de charge dans un système de communication sans fil
WO2025052401A1 (fr) * 2023-09-08 2025-03-13 Jio Platforms Limited Procédé et système de gestion d'une condition de surcharge dans un réseau

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012093832A2 (fr) * 2011-01-03 2012-07-12 삼성전자 주식회사 Procédé permettant de maîtriser la congestion dans un système de communication mobile

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012093832A2 (fr) * 2011-01-03 2012-07-12 삼성전자 주식회사 Procédé permettant de maîtriser la congestion dans un système de communication mobile

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ROACH MOZILLA E MCMURRY TEKELEC A B: "A Mechanism for Diameter Overload Control; draft-roach-dime-overload-ctrl-03.txt", A MECHANISM FOR DIAMETER OVERLOAD CONTROL; DRAFT-ROACH-DIME-OVERLOAD-CTRL-03.TXT, INTERNET ENGINEERING TASK FORCE, IETF; STANDARDWORKINGDRAFT, INTERNET SOCIETY (ISOC) 4, RUE DES FALAISES CH- 1205 GENEVA, SWITZERLAND, 17 May 2013 (2013-05-17), pages 1 - 49, XP015090987 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016201707A1 (fr) * 2015-06-19 2016-12-22 华为技术有限公司 Procédé de transfert d'informations d'état de réseau et dispositif de réseau
US10470105B2 (en) 2015-06-19 2019-11-05 Huawei Technologies Co., Ltd. Network status information transfer method and network device
EP3883198A1 (fr) * 2020-03-20 2021-09-22 Nokia Technologies Oy Contrôle de charge dans un système de communication sans fil
US11765618B2 (en) 2020-03-20 2023-09-19 Nokia Technologies Oy Wireless communication system
WO2025052401A1 (fr) * 2023-09-08 2025-03-13 Jio Platforms Limited Procédé et système de gestion d'une condition de surcharge dans un réseau

Similar Documents

Publication Publication Date Title
AU2017308378B2 (en) Terminal apparatus, gateway, and communication control method
US11246053B2 (en) Congestion/overload control method and apparatus
CN102075898B (zh) 业务控制方法、装置及系统
US9621444B2 (en) Method and device for handling dropped data packets
US9699038B2 (en) Node and method for service usage reporting and quota establishment
WO2017143915A1 (fr) Procédé et dispositif d'étranglement d'une largeur de bande d'un point d'accès
WO2014017630A1 (fr) Système de communication, appareil de nœud, procédé et programme
US10841835B2 (en) Maximum bit rate control in a multi-access network
CN102045867A (zh) 网络连接建立方法及装置、pcc策略制定方法及系统
WO2015120902A1 (fr) Sélection de nom de point d'accès (apn) assistée par fonction de règles de politique et de facturation (pcrf)
CN101577931B (zh) 一种实现多接入的方法及系统
US9877258B2 (en) Method and device for transferring data traffic
EP2878162A1 (fr) Noeud et procédé d'établissement de priorité d'application basée sur le traitement d'une demande de radiomessagerie
US9876881B2 (en) Node and method for obtaining priority information in a header of a control plane message
CN103002543B (zh) 一种多接入方法及系统
WO2015048992A1 (fr) Traitement de surcharge d'un nœud de réseau
EP3510726B1 (fr) Procédés et noeuds pour la gestion de la charge d'un équipement utilisateur par une politique d'orientation de trafic
CN102752796B (zh) 一种机器通信资源管理的方法和装置
CN103428684B (zh) 一种网关地址信息的传递方法及系统
CN103227983A (zh) 实现过载控制或差异化服务的方法、系统及设备
TW201201605A (en) Charging control message method of handover among heterogeneous networks

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: 13776443

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: 13776443

Country of ref document: EP

Kind code of ref document: A1