Section: 12.3.10.4.1 Description
Content: For messages destined to a remote GTP-C entity (i.e. a GTP-C entity not in direct contact but reached via an intermediate GTP-C entity), the source GTP-C entity shall enforce the overload control based on the overload information of the target of the message, as well as the overload information of the intermediate GTP-C entity, e.g. the MME applies the overload control for messages targeted for the PGW based on the overload information of the SGW and PGW. For the received messages, the intermediate GTP-C entity shall not further enforce any overload control and hence, shall not reject any message towards the source GTP-C entity. Annex D.4.1 provides an (informative) example of a possible implementation. NOTE 1: This approach ensures the overload protection of the Target as well as Intermediate GTP-C entities. NOTE 2: The source GTP-C entity may be connected to the same Target GTP-C entity via multiple different Intermediate GTP-C entities. The exact algorithm used at the source GTP-C entity to enforce the overload control, as per the aforementioned requirements, is implementation specific.