Abstract: The embodiments herein relate to a method performed by a local subscriber node for handling attachment of a User Equipment (UE) to a central network. The local subscriber node comprises default subscription data which is common for all UEs which are associated with a local network. When a connection to a central subscriber node is accessible, the local subscriber node obtains authentication data associated with the default subscription data from the central subscriber node. When the UE requests attachment to the central network when the connection to the central subscriber node is inaccessible, the local subscriber node sends the obtained authentication data for the UE to a mobility management node.

Abstract: The embodiments herein relate to a method performed by a local subscriber node for handling attachment of a UE to a central network. The local subscriber node comprises default subscription data which is common for all UEs which are associated with a local network. When a connection to a central subscriber node is accessible, the local subscriber node obtains authentication data associated with the default subscription data from the central subscriber node. When the UE requests attachment to the central network when the connection to the central subscriber node is inaccessible, the local subscriber node sends the obtained authentication data for the UE to a mobility management node.

Abstract: The application relates to the procedures Routing Area Update RAU in UTRAN and Tracking Area Update TAU in LTE. Furthermore, it relates to PDP context procedure in UTRAN as well as PDN connection procedure in LTE. In the current RAU procedure, a SGSN, which fails to update the Routing Area, e.g. because it receives the DNS return error, sends a RAU Reject with the cause code CC#17 indicating a network failure back to the user equipment (114b). The cause code CC#17 in the RAU Reject causes the user equipment to send a new RAU Request. Thus, the user equipment is stuck in a loop of sending a RAU Request and receiving a RAU Reject. This problem is solved by the present application in that SGSN keeps track of the number of rejections when doing RAU. When the number of rejections is above a certain threshold, the SGSN will send a RAU Reject with cause code CC#10 to the user equipment (115b), whereby the cause code CC#10 indicates implicit detach of the user equipment.

Abstract: The application relates to the procedures Routing Area Update RAU in UTRAN and Tracking Area Update TAU in LTE. Furthermore, it relates to PDP context procedure in UTRAN as well as PDN connection procedure in LTE. In the current RAU procedure, a SGSN, which fails to update the Routing Area, e.g. because it receives the DNS return error, sends a RAU Reject with the cause code CC#17 indicating a network failure back to the user equipment (114b). The cause code CC#17 in the RAU Reject causes the user equipment to send a new RAU Request. Thus, the user equipment is stuck in a loop of sending a RAU Request and receiving a RAU Reject. This problem is solved by the present application in that SGSN keeps track of the number of rejections when doing RAU. When the number of rejections is above a certain threshold, the SGSN will send a RAU Reject with cause code CC#10 to the user equipment (115b), whereby the cause code CC#10 indicates implicit detach of the user equipment.