Report of serving network, time zone, and UCI

Abstract

A method in a mobility management node for handling information in a network. The node is associated with a wireless device being served by a serving network. The node obtains information about that at least one of the serving network and a time zone and a UCI, has been changed for the device, and information about that the change has not been transmitted to a SGW. When at least one of the serving network and the time zone and the UCI, has been changed, and information about the change has not been transmitted to the SGW, the node transmits the information about at least one of the changed serving network and time zone and UCI, to the SGW, enabling the SGW to forward this information to a PGW.

Claims

1. A method in a first network function for handling information in a communications network, the method comprising: obtaining information pertaining to a wireless device, wherein the information pertaining to the wireless device comprises: 1) a serving network identifier identifying a serving network currently serving the wireless device, 2) a time zone identifier identifying a time zone in which the wireless device is located, and/or 3) a group identifier identifying a group in which the wireless device is included; obtaining an indicator indicating that the information pertaining to the wireless device has not been transmitted to a second network function associated with the first network function; and as a result of obtaining the information indicating that the information pertaining to the wireless device has not been transmitted to the second network function, transmitting to the second network function the information pertaining to the wireless device, thereby enabling the second network function to forward this information to a third network function.

2. The method of claim 1, further comprising: receiving a request message transmitted by the wireless device or a source mobility management node (MMN), wherein the step of obtaining the indicator is performed in response to receiving the request message.

3. The method of claim 1, wherein the first network function is a target mobility management node (MMN) associated with the wireless device, the wireless device has previously been associated with a source MMN, and the target MMN obtains the indicator from the source MMN.

4. The method of claim 3, wherein the indicator is received in a context response message when the wireless device is in idle mode, and wherein the indicator is received in a forward relocation request message when the wireless device is in active mode.

5. The method of claim 3, wherein transmitting to the second network function the information pertaining to the wireless device comprises transmitting to the second network function a modify bearer request comprising the information pertaining to the wireless device.

6. The method of claim 3, wherein the indicator comprises a first bit, a second bit, and a third bit, the first bit corresponds to a report status for the serving network, the second bit corresponds to a report status for the time zone, and the third bit corresponds to a report status for the group.

7. The method of claim 3, wherein the indicator is associated with a Packet Data Network connection of the wireless device.

8. The method of claim 1, further comprising: receiving a request transmitted by the wireless device; in response to receiving the request transmitted by the wireless device, transmitting a context request to a source mobility management node (MMN), wherein the source MMN is operable to respond to the context request by transmitting a context response; receiving the context response, wherein the context response comprises the indicator, wherein obtaining the indicator comprises obtaining the indicator from the context response.

9. The method of claim 8, wherein transmitting to the second network function the information pertaining to the wireless device comprises transmitting to the second network function a modify bearer request comprising the information pertaining to the wireless device, wherein the modify bearer request is transmitted as a response to the context response.

10. The method of claim 9, wherein the second network function is a Serving Gateway (SGW).

11. A first network function for handling information in a communications network, wherein the first network function is configured to be associated with a wireless device being served by a serving network, the first network function comprising: a transmitter; a receiver; a memory; and a processor coupled to the transmitter, receiver and the memory, wherein the first network function is configured to: obtain information pertaining to a wireless device, wherein the information pertaining to the wireless device comprises: 1) a serving network identifier identifying a serving network currently serving the wireless device, 2) a time zone identifier identifying a time zone in which the wireless device is located, and/or 3) a group identifier identifying a group in which the wireless device is included; obtain an indicator indicating that the information pertaining to the wireless device has not been transmitted to a second network function associated with the first network function; and as a result of obtaining the information indicating that the information pertaining to the wireless device has not been transmitted to the second network function, transmit to the second network function the information pertaining to the wireless device, thereby enabling the second network function to forward this information to a third network function.

12. The first network function of claim 11, wherein the first network function is further adapted to receive a request message transmitted by the wireless device or a source mobility management node (MMN), wherein the first network function is configured to obtain the indicator in response to receiving the request message.

13. The first network function of claim 11, wherein the first network function is a target mobility management node (MMN) associated with the wireless device, the wireless device has previously been associated with a source MMN, and the target MMN is configured to obtain the indicator from a message transmitted by the source MMN.

14. The first network function of claim 13, wherein the indicator is received in a context response message when the wireless device is in idle mode, and wherein the indicator is received in a forward relocation request message when the wireless device is in active mode.

15. The first network function of claim 13, wherein the first network function is configured to transmit to the second network function the information pertaining to the wireless device by transmitting to the second network function a modify bearer request comprising the information pertaining to the wireless device.

16. The first network function of claim 13, wherein the indicator comprises a first bit, a second bit, and a third bit, the first bit corresponds to a report status for the serving network, the second bit corresponds to a report status for the time zone, and the third bit corresponds to a report status for the group.

17. The first network function of claim 13, wherein the indicator is associated with a Packet Data Network connection of the wireless device.

18. The first network function of claim 11, wherein the first network function is adapted to: receive a request transmitted by the wireless device; in response to receiving the request transmitted by the wireless device, transmit a context request to a source mobility management node (MMN), wherein the source MMN is operable to respond to the context request by transmitting a context response; and receive the context response, wherein the context response comprises the indicator, wherein the first network function is configured to obtain the indicator by obtaining the indicator from the context response.

19. The first network function of claim 18, wherein the first network function is configured to transmit to the second network function the information pertaining to the wireless device by transmitting to the second network function a modify bearer request comprising the information pertaining to the wireless device.

20. The first network function of claim 19, wherein the second network function is a Serving Gateway (SGW).

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) The embodiments herein will now be further described in more detail in the following detailed description by reference to the appended drawings illustrating the embodiments and in which:

(2) FIG. 1 is a schematic block diagram illustrating embodiments of a communications network.

(3) FIG. 2 is a signaling diagram illustrating embodiments of a method in the communications network.

(4) FIG. 3 is a signaling diagram illustrating embodiments of a non-mobility procedure in a communications network.

(5) FIG. 4 is a schematic block diagram illustrating embodiments of a mobility procedure in a communications network.

(6) FIG. 5 is a signaling diagram illustrating embodiments of a mobility procedure in a communications network.

(7) FIG. 6 is a signaling diagram illustrating embodiments of a mobility procedure in a communications network.

(8) FIG. 7 is a flow chart illustrating embodiments of a method in a mobility management node.

(9) FIG. 8 is a schematic block diagram illustrating embodiments of a mobility management node.

(10) 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 illustrating the principle of the embodiments herein.

DETAILED DESCRIPTION

(11) The embodiments herein enhance the report of at least one of the serving network and time zone and UCI, so that the SGW and the PGW has the latest information about at least one of serving network and time zone and UCI in time with the least additional signaling, in both a mobility scenario and a non-mobility scenario. The mobility management node needs sufficient information in order to know whether the latest information about the at least one of the serving network and time zone and UCI has been reported to the SGW and the PGW or not.

(12) The embodiments herein relate to the S4/S11 and/or the S5/S8 interfaces and/or to the S10/S3/S16 interfaces respectively, and with the improvements, the wholesome serving network and/or time zone and/or UCI report mechanism is obtained. The S4 is the interface between the SGSN and the SGW. The S11 is the interface between the MME and the SGW. S5 is the interface between the SGW and the PGW and S11 is the interface between the MME and the SGW. S10 is the interface between multiple MMEs. S3 is the interface between the SGSN and the MME, and S16 is the interface between multiple SGSNs.

(13) FIG. 1 depicts a communications network 100 in which embodiments described herein may be implemented. The communications network 100 may in some embodiments apply to one or more radio access technologies such as for example LTE, LTE Advanced, WCDMA, GSM, or any other 3GPP radio access technology, or other radio access technologies such as e.g. Wireless Local Area Network (WLAN).

(14) The communications network 100 comprises a mobility management node101 which is associated with a wireless device 103. The wireless device 103 is present in and served by a serving network. The serving network has a unique ID, which is referred to as SN ID in some of the drawings. The serving network may comprise multiple routing areas or tracking areas. The mobility management node may be a MME, a combined SGSN/MME or a S4-SGSN.

(15) The wireless device 103 may be a device by which a subscriber may access services offered by an operator's network and services outside operator's network to which the operators radio access network and core network provide access, e.g. access to the Internet. The wireless device 103 may be any device, mobile or stationary, enabled to communicate over a radio channel in the communications network, for instance but not limited to e.g. user equipment, mobile phone, smart phone, sensors, meters, vehicles, household appliances, medical appliances, media players, cameras, Machine to Machine (M2M) device or any type of consumer electronic, for instance but not limited to television, radio, lighting arrangements, tablet computer, laptop or Personal Computer (PC). The wireless device 103 may be portable, pocket storable, hand held, computer comprised, or vehicle mounted devices, enabled to communicate voice and/or data, via the radio access network, with another entity, such as another device or a server.

(16) The wireless device 103 is enabled to communicate wirelessly with the communications network 100. The communication may be performed e.g. between two wireless devices, between the wireless devices 103 and a server via the radio access network and possibly one or more core networks and possibly the Internet.

(17) The mobility management node101 is connected to a SGW 105. When the mobility management node101 is a S4-SGSN, the SGSN 101 has a S4 interface towards the SGW 105, and thereby referred to as a S4-SGSN. When the mobility management node 101 is a combined SGSN/MME, the interface between the combined SGSN/MME and the SGW 105 is the S4/S11 interface. When the mobility management node 101 is a MME, the interface between the MME and the SGW 105 is S11 interface.

(18) The SGW 105 is connected to a PGW 108. When the wireless device 103 is accessing multiple PDNs, there may be more than one PGW 108 for that wireless device 103, but only one PGW 108 is shown here for the sake of simplicity.

(19) FIG. 2 is a signaling diagram illustrating an embodiment of a method for handling information in the communications network 100, regardless whether there is a mobility or non-mobility associated with the mobility management node. The embodiments herein provide solutions for the mobility management node 101 to fulfill the serving network and/or time zone and/or UCI reporting task, especially when shared network is used. The method comprises the following steps, which steps may be performed in any suitable order:

(20) Step 201:

(21) The mobility management node 101 checks whether at least one of the following three parameters has changed: the serving network and/or time zone and/or UCI. When at least one of the serving network and time zone and UCI has not changed, the mobility management node 101 does not take any action. When at least one of the serving network and time zone and UCI has changed, the method proceeds to step 202.

(22) Step 202:

(23) When the mobility management node 101 determined in step 201 that at least one of the serving network and time zone and UCI has changed, the mobility management node 101 checks whether the information about the change has been transmitted to the SGW 105 or not. When the information has been transmitted to the SGW 105, the mobility management node 101 does not take any action. When the information has not been transmitted to the SGW 105, the method proceeds to step 203.

(24) Step 203:

(25) When at least one of the serving network and time zone and UCI has changed and has not previously been transmitted to the SGW 105, the mobility management node 101 transmits the information about the changed serving network and/or time zone and/or UCI to the SGW 105.

(26) Step 204:

(27) When the SGW 105 has received the information about the change, it forwards the information to the PGW 108. The PGW 108 uses the information for e.g. the CDR and reports it to the PCRF for the further policy decision, e.g. a serving network change leads different QoS; UCI change leads different charging rate and so on.

(28) The mobility procedure and the non-mobility procedure will now be described, starting with the non-mobility procedure.

(29) Serving Network/Time Zone/UCI Reporting without Change of Mobility Management Code Change (Non-Mobility):

(30) In this non-mobility procedure, the mobility management node 101 is a S4-SGSN or a combined SGSN/MME, and the S4-SGSN will be used as an example in the following description of the non-mobility. For WCDMA access, the S4-SGSN 101 checks direct tunnel conditions each time a Packet Data Protocol (PDP) context is activated, whether the wireless device 103 is activated or by means of an Inter-SGSN routing area update, an Inter SGSN Inter-Radio Access Technology (IRAT) Packet Switched (PS) handover from GSM to WCDMA systems, or an Inter-SGSN serving radio network subsystem relocation. The direct tunnel allows data traffic to bypass the S4-SGSN 101, significantly increasing network capacity and allowing the S4-SGSN 101 to function as an MME signaling server. When a direct tunnel is not used, either in the intra-routing area update procedure, or in the subsequent device initiated service request procedure, an additional modify bearer request is needed to report at least one of the serving network and time zone and UCI changes.

(31) For GSM access, the S4-SGSN 101 sends an additional modify bearer request to report at least one of the serving network and time zone and UCI changes due to no service request in 2G.

(32) At least one of the serving network and time zone and UCI IEs are introduced in at least one of a create bearer response and update bearer response and delete bearer response messages to piggyback the latest serving network to the SGW 105 when the change is not reported yet.

(33) The S4-SGSN 101 will remember each PDN connection report status. The S4-SGSN 101 only comprises the changed serving network in the modify bearer request messages with for those PDN connections which changes of at least one of serving network and time zone and UCI have not be reported yet.

(34) The non-mobility procedure with the S4-SGSN 101 solution to piggyback at least one of the serving network and time zone and UCI is illustrated in the signaling diagram in FIG. 3, which improves the S4/S11 and/or S5/S8 interface. In the non-mobility procedure exemplified in FIG. 3, the information about the time zone is already known by the SGW 105. In FIG. 3, the embodiment uses the S4-SGSN 101 as an example to fulfill the task of reporting at least one of the serving network and UCI via the S4/S11 and/or the S5/S8 interface independent from service request procedure, however a combined SGSN/MME may also be used. Instead, at least one of the serving network and UCI are piggybacked in the create bearer response message, step 312 in FIG. 3. Similarly, at least one of the serving network and UCI may be piggybacked to the SGW 105 in the update bearer response or the delete bearer response message (not shown in FIG. 3). This Piggyback solution for delivering at least one of the serving network and UCI is also applicable for the MME.

(35) This piggyback solution saves the required modify bearer signaling to report the change of at least one of the serving network and UCI. When there is no dedicated signaling triggered by the PGW 108, additional modify bearer request messages which per PDN connection to report the change of at least one of the serving network and UCI are anyway needed. In the example embodiment in FIG. 3, the wireless device 103 has established two PDN connections, one towards the PGW1 108a and one towards the PGW2 108b.

(36) The method for reporting of at least one of the serving network and UCI change without any S4-SGSN 101 change comprises the following steps, which steps may be performed in any suitable order:

(37) Step 301:

(38) The wireless device 103 transmits a routing area update (RAU) request message to the S4-SGSN 101. The serving network of the wireless device 103 changes during intra-routing area update.

(39) Step 302:

(40) The S4-SGSN 101 transmits a routing area update (RAU) accept message back to the wireless device 103.

(41) Step 303:

(42) The wireless device 103 transmits a routing area update (RAU) complete message to the S4-SGSN 101.

(43) Step 304:

(44) The Iu interface is released. The Iu interface is an external interface that connects a Radio Network Controller (RNC) 110 to the S4-SGSN 101 for packet switched traffic.

(45) Step 305:

(46) The PGW1 108a transmits a create bearer request to the SGW 105.

(47) Step 306:

(48) The SGW 105 forwards the create bearer request to the S4-SGSN 101.

(49) Step 307:

(50) The S4-SGSN 101 transmits a paging message to the wireless device 103 via the RNC 110.

(51) Step 308:

(52) The wireless device 103 transmits a service request to the S4-SGSN 101

(53) Step 309:

(54) An activate secondary PDP context request and response is transmitted between the S4-SGSN 101 and the wireless device 103.

(55) Step 310:

(56) Messages related to the radio access bearer assignment are transmitted between the S4-SGSN 101 and the wireless device 103 in order to establish one or more radio access bearers for the wireless device 103 and/or to modify or release already existing radio access bearers.

(57) Step 311:

(58) The S4-SGSN 101 transmits a create bearer response, as a response to the request transmitted in step 306, to the SGW 105, preferably via the S4 interface. The create bearer response comprises information about at least one of the changed serving network and UCI, i.e. the information about the change is piggybacked on the create bearer response. The time zone is already known, and is therefore not necessarily transmitted in the non-mobility procedure.

(59) Step 312:

(60) The SGW 105 forwards the create bearer response, comprising information about the changed serving network and/or UCI, to the PGW1 108a, thus PGW1 108a has the latest information about at least one of the serving network and UCI in time.

(61) Step 313:

(62) The Iu interface between the wireless device 103 and the S4-SGSN 101 is released.

(63) Step 314:

(64) The wireless device 103 transmits a service request to the S4-SGSN 101.

(65) Step 315:

(66) The S4-SGSN 101 transmits a modify bearer request associated with PGW2 108b to the SGW 105, preferably via the S4 interface. The modify bearer request comprises information about the changed serving network and/or UCI, i.e. the information about the change is piggybacked on the modify bearer request.

(67) The S4-SGSN needs to send a modify bearer request message for both the PGW1 108a and the PGW2 108b, however information about the change of at least one of the serving network and UCI is not comprised in the modify bearer request for the PGW1, thus S5/S8 signaling is reduced.

(68) Step 316:

(69) The SGW 105 forwards the modify bearer request comprising the information about the changed serving network and/or UCI to the PGW2 108b.

(70) Step 317:

(71) The PGW2 108b transmits a modify bearer response to the SGW 105.

(72) Step 318:

(73) The SGW 105 forwards the modify bearer response to the S4-SGSN 101.

(74) Step 319:

(75) The payload data is transmitted between the wireless device 103 and the PGW2 108b.

(76) The non-mobility procedure was described above, and the mobility procedure will now be described below.

(77) Serving Network/Time Zone/UCI Reporting with Change of Mobility Management Node (Mobility):

(78) FIG. 4 depicts an embodiment of the communications network 100 where the wireless device 103 changes from being served by a source serving network 100s to being served by a target serving network 100t, also referred to as the mobility procedure.

(79) The communications network 100 comprises a source mobility management node 101s which is associated with the wireless device 103. The wireless device 103 is present in and served by the source serving network 100s. The wireless device 103 moves from the source serving network 100s to the target serving network 100t, and changes from being associated with the source mobility management node 101s to being associated with a target mobility management node 101t. In the mobility procedure exemplified in FIG. 4, the source mobility management node 101s may be a source S4-SGSN or a combined source SGSN/MME or a source MME, and the target mobility management node 101t may be a target S4-SGSN or a combined target SGSN/MME or a target MME. The target mobility management node 101t may transmit a message request to the source mobility management node 101s, and the source mobility management node 101s may transmit a message response back go the target mobility management node 101t.

(80) The source serving network 100s and the target serving network 100t are identified with the same SN ID1. When the wireless device 103 is in the source serving network 100s or in the target serving network 100t, it is located in the time zone 1 and comprised in the UCI with the CSG ID1.

(81) The source mobility management node 101s and the target mobility management node 101t are connected to the same SGW 105. When the source mobility management node 101s and the target mobility management node 101t are S4-SGSNs, the source mobility management node 101s and the target mobility management node 101t each has a S4 interface towards the SGW 105. When the source mobility management node 101s and the target mobility management node 101t are MMEs or combined SGSN/MMEs, the interface between each of the source mobility management node 101s and the target mobility management node 101t on one hand and the SGW 105 on the other hand is the S11 interface. The target mobility management node 101t may transmit a modify bearer request message, a create bearer response, a delete bearer response or an update bearer response to the SGW 105. The source mobility management node 101s may transmit a modify bearer request message to the SGW 105.

(82) The SGW 105 is connected to the PGW 108 with the S5/S8 interface. As mentioned earlier, when the wireless device 103 is accessing multiple PDNs, there may be more than one PGW 108 for that wireless device 103, but only one PGW 108 is shown here for the sake of simplicity.

(83) The messages transmitted between the network nodes illustrated in FIG. 4 will be described in more detail below with reference to FIGS. 5 and 6.

(84) In one embodiment, an indication, e.g. in the form of an information element (IE), may indicate when there is any serving network and/or time zone and/or UCI changes that has not been reported yet. The indication may be called Change Reported Flag on PDN connection basis. In addition, in the existing GTPv2 specification, the current stored UCI in the source mobility management node 101s is preferably comprised in the context response message.

(85) In another embodiment, the target mobility management node 101t may always provide at least one of the serving network and/or time zone and UCI indications in the Modify Bearer Request message as part of inter mobility management node mobility procedure, instead of comparing the target/current serving network 100t with the source serving network 100s. The SGW 105 may check at least one of the serving network and time zone and UCI indications received from the target mobility management node 101t. Only when the value of at least one of the serving network and time zone and/or UCI indications changes, the SGW 105 will forward at least one of the serving network and time zone and UCI indications to the PGW 108. Thus there will be no redundant signaling on the S5/S8 interface.

(86) FIG. 5 illustrates embodiments of inter-mobility management node mobility, which improves the S10/S3/S16 interfaces. In FIG. 5, the mobility management node is exemplified with a combined SGSN/MME, but the mobility management node may also be a S4-SGSN or an individual MME. A precondition for the embodiments illustrated in FIG. 5 is that the source mobility management node 101s supports the following functionality:

(87) (1) in the case of inter-mobility management node mobility, the source mobility management node 101s sets the report status per PDN connection to the target SGSN/MME 101t; and

(88) (2) the target SGSN/MME 101t obtains information about at least one of the source serving network and time zone and UCI and compares it with at least one of the current target serving network and current time zone and current UCI for the wireless device 103. When they are different, the existing handling defined in 3GPP is kept to report at least one of the new serving network and time zone and UCI to the SGW 105.

(89) When at least one of the serving network and time zone and UCI are not changed, the target SGSN/MME 101t needs to further check the indications to decide when at least one of the serving network and/or time zone and UCI will be reported or not.

(90) When the indication, e.g. the Change Reported Flag, indicates that the change was already reported to the SGW 105 in the source side, the target SGSN/MME 101t does not need to report it any more until at least one of the serving network and time zone and UCI changes again.

(91) When the indication indicates that it was not reported in the source side, the target SGSN/MME 101t comprises at least one of the new serving network and/or time zone and/or UCI into the modify bearer request to inform the SGW 105 about at least one of the latest serving network and time zone and UCI.

(92) The indication may be comprised in the forward relocation request message and/or the context response message. The indication may be defined as a bitmap style IE, where each bit corresponds to the report status for at least one of the serving network and time zone and UCI. Since the changes of at least one of the serving network and time zone and UCI are independent. FIG. 5 depicting the report of at least one of serving network and time zone and UCI during idle mode mobility procedure, e.g. routing area update/tracking area update comprises the following steps, which steps may be performed in any suitable order:

(93) Step 501:

(94) When the wireless device 103 has detected that is has moved from the source serving network 100s to the target serving network 100t, the wireless device 103 transmits a routing area (RAU) update or a tracking area (TAU) update request to the target SGSN/MME 101t.

(95) Step 502:

(96) The target SGSN/MME 101t transmits a context request to the source SGSN/MME 101s.

(97) Step 503:

(98) The source SGSN/MME 101s transmits a context response message to the target SGSN/MME 101t. The context response message comprises the indication, e.g. a Change Reported Flag.

(99) Step 504:

(100) The target SGSN/MME 101t transmits a context acknowledgement to the source SGSN/MME 101s.

(101) Step 505:

(102) The target SGSN/MME 101t transmits a modify bearer request to the SGW 105, preferably via the S4 or the S11 interface. The modify bearer request comprises the information about at least one of the serving network and/or time zone and/or UCI. The information about at least one of the serving network and/or time zone and/or UCI is comprised in the modify bearer request in the following cases: (1) when at least one of the serving network and time zone and UCI has changed; (2) when at least one of the serving network and time zone and UCI has not changed but it was not reported by the source side.

(103) Step 506:

(104) The SGW 105 forwards the modify bearer request to the PGW 108. The forwarded modify bearer request comprises the information about at least one of the serving network and time zone and UCI. This information is comprised in the modify bearer request when at least one of the serving network and time zone and UCI was received by the SGW 105 in step 505. The modify bearer request is transmitted via the S5/S8 interface, and the SGW 105 closes the SGW-CDR as a result.

(105) Step 507:

(106) The PGW 108 transmits a modify bearer response to the SGW 105.

(107) Step 508:

(108) The SGW 105 forwards the modify bearer response to the target SGSN/MME 101t.

(109) Step 509:

(110) The target SGSN/MME 101t transmits information to a Home Location Register (HLR) 120 to update/insert the location of the wireless device 103 now being associated with the target SGSN/MME 101t. The HLR 120 is a database comprising details of each wireless device 103.

(111) Step 510:

(112) The source SGSN/MME 101s transmits information to the HLR 120 to cancel the previous location of the wireless device 103 associated with the source SGSN/MME 101s.

(113) Step 511:

(114) The target SGSN/MME 101t transmits a routing area update or a tracking area update accept message to the wireless device 103.

(115) FIG. 6 illustrates an embodiment wherein the indication mentioned above is comprised in the forward relocation request message. As mentioned above, the indication indicates whether there is a change in serving network and/or time zone and/or UCI for the wireless device 103 that has not been reported to the SGW 105. In FIG. 6, the mobility management node is exemplified with a combined SGSN/MME, but the mobility management node may also be a S4-SGSN or an individual MME. The inter-mobility management nodehandover procedure exemplified in FIG. 6 comprises the following steps, which steps may be performed in any suitable order:

(116) Step 601:

(117) A source RNC/eNB 130s transmits a relocation required message to the source SGSN/MME 101s when the wireless device 103 has relocated from the source serving network 100s to the target serving network 100t.

(118) Step 602:

(119) The source SGSN/MME 101s transmits a forward relocation required message to the target SGSN/MME 101t. The source SGSN/MME 101s comprises the indication mentioned above in the relocation required message.

(120) Step 603:

(121) The target SGSN/MME 101t transmits a handover request to a target RNC/eNB 130t.

(122) Step 604:

(123) The target RNC/eNB 130t transmits a handover request acknowledgement to the target SGSN/MME 101t.

(124) Step 605:

(125) The target SGSN/MME 101t transmits a forward request response to the source SGSN/MME 101s.

(126) Step 606:

(127) The handover of the wireless device 103 is executed.

(128) Step 607:

(129) The target RNC/eNB 130t transmits a handover notify message to the target SGSN/MME 101t.

(130) Step 608:

(131) The target SGSN/MME 101t transmits a modify bearer request to the SGW 105. The modify bearer request comprises information about at least one of the serving network and time zone and/or UCI when the information has changed and/or when the information (changed or not) has not been previously reported.

(132) Step 609:

(133) The SGW 105 forwards the modify bearer request to the PGW 108. The forwarded modify bearer request comprises information about at least one of the serving network and time zone and UCI.

(134) Step 610:

(135) The PGW 108 transmits a modify bearer response to the SGW 105.

(136) Step 611:

(137) The SGW 105 forwards the modify bearer response to the target SGSN/MME 101t.

(138) Step 612:

(139) The old resources, i.e. the source RNC/eNB 130s and the source SGSN/MME 101s, are released.

(140) In another embodiment, the target mobility management node 101t always comprises at least one of the serving network and/or time zone and UCI IE in the modify bearer request message, instead of comparing the current information about at least one of the serving network and time zone and UCI with the old serving network and/or time zone and/or UCI and be assisted by the indication. The SGW 105 will check at least one of the serving network and time zone and UCI information received from the target mobility management node 101t. Only when at least one of the serving network and time zone and UCI IE information changes, the SGW 105 forwards at least one of the serving network and time zone and UCI information to the PGW 108. Thus, there will be no redundant signaling on the S5/S8 interface.

(141) The method described above will now be described seen from the perspective of the mobility management node 101, 101t. FIG. 7 is a flowchart describing the present method in the mobility management node 101, 101t, for handling information in a communications network 100. As mentioned above the mobility management node 101, 101t is associated with the wireless device 103 being served by the serving network 100, 100t. The mobility management node 101, 101t may be a MME or a S4-SGSN or a combined SGSN/MME in the mobility scenario and it may be a S4-SGSN or a combined SGSN/MME in the non-mobility scenario.

(142) The method comprises the following steps to be performed by the mobility management node 101, 101t, which steps may be performed in any suitable order:

(143) Step 701:

(144) This step corresponds to steps 201 and 202 in FIG. 2. The mobility management node 101, 101t obtains information about that at least one of the serving network 100, 100t and a time zone and the UCI has been changed for the wireless device 103, and information about that the change has not been transmitted to the SGW 105 associated with the mobility management node 101, 101t.

(145) Step 701a:

(146) This step corresponds to step 503 in FIG. 5 and step 602 in FIG. 6. Step 701a is a substep of step 701. In some embodiments, e.g. in the mobility scenario, the mobility management node 101, 101t is a target mobility management node 101t associated with the wireless device 103 and the wireless device 103 has previously been associated with a source mobility management node 101s. The mobility management node 101t may receive an indication from the source mobility management node 101s. The indication indicates whether the information about the change has been transmitted to the SGW 105 or not.

(147) For example, in the mobility scenario, the indication may be received in a context response message when the wireless device 103 is in idle mode, and the indication may be received in a forward relocation request message when the wireless device 103 is in active mode.

(148) The indication may be an information element comprising bits. Each bit may correspond to a status for at least one the serving network and time zone and UCI. The status indicates whether the information about the change has been transmitted to the SGW 105 or not. The indication may be associated with one PDN connection of the wireless device 103 or individually associated with the wireless device 103. The indication may be a change reported flag.

(149) Step 701b:

(150) This step is a substep of step 701, and a step that is performed instead of step 701a. In some embodiments, e.g. in a non-mobility scenario, the mobility management node 101, 101t detects that at least one of the serving network or time zone or UCI has been changed and that the information about the change has not been transmitted to the SGW 105.

(151) Step 702:

(152) This step corresponds to step 203 in FIG. 2, step 311 and step 315 in FIG. 3, step 505 in FIG. 5 and step 608 in FIG. 6. When at least one of the serving network and the time zone and the UCI, has been changed for the wireless device 103, and information about the change has not been transmitted to the SGW 105, the mobility management node 101, 101t transmits the information about at least one of the changed serving network and time zone and UCI, to the SGW 105, enabling the SGW 105 to forward this information to the PGW 108.

(153) In some embodiments, e.g. in the mobility scenario, the information about the change is transmitted in a modify bearer request when the indication indicates that information about the change has not been transmitted to the SGW 105.

(154) In some embodiments, e.g. in a non-mobility scenario, the information about the change is transmitted to the SGW 105 in an update bearer response or a create bearer response or a delete bearer response when there is dedicated signaling triggered by the PGW 108.

(155) In some embodiments, e.g. in a non-mobility scenario, the information about the change comprises information about at least one of the serving network and UCI.

(156) In some embodiments, e.g. in a non-mobility scenario, the communications network 100 is based on UTRAN where a direct tunnel is not used in the communications network 100, or the communications network 100 is based on GSM where a direct tunnel is not existing in the communications network 100.

(157) The information about at least one of the changed serving network and time zone and UCI may be transmitted to the SGW 105 with least signaling messages over a S11/S4 interface and a S5/S8 interface.

(158) To perform the method steps shown in FIG. 7 for handling information in a communications network 100 the mobility management node 101, 101t comprises an arrangement as shown in FIG. 8. The mobility management node 101, 101t is configured to be associated with a wireless device 103 being served by a serving network 100, 100t. In some embodiments, the mobility management node 101, 101t is a target mobility management node 101t associated with the wireless device 103 and the wireless device 103 has previously been associated with a source mobility management node 101s. In the mobility scenario, the mobility management node 101, 101t may be a standalone MME or a S4-SGSN or a combined SGSN/MME. In the non-mobility scenario, the mobility management node 101, 101t may be a S4-SGSN or a combined SGSN/MME. In some embodiments, the communications network 100 is based on UTRAN where a direct tunnel is not used in the communications network 100, or the communications network 100 is based on GSM where a direct tunnel does not exist in the communications network 100.

(159) The mobility management node 101, 101t comprises an obtaining unit 801 which is configured to obtain information about that at least one of the serving network 100, 100t and a time zone and a UCI, has been changed for the wireless device 103, and information about that the change has not been transmitted to the SGW 105 associated with the mobility management node 101, 101t. In some embodiments, the obtaining unit 801 is configured to detect, in the mobility management node 101, 101t, that at least one of the serving network or time zone or UCI has been changed and that the information about the change has not been transmitted to the SGW 105.

(160) In some embodiments, e.g. in the mobility scenario, the obtaining unit 801 is a receiver 801a. The receiver 801a is configured to receive an indication from the source mobility management node 101s. The indication may indicate whether the information about the change has been transmitted to the SGW 105 or not. The receiver 801a may be configured to receive the indication in a context response message when the wireless device 103 is in idle mode, and to receive the indication in a forward relocation request message when the wireless device 103 is in active mode. The indication may be an information element comprising bits. Each bit may correspond to a status for at least one the serving network and time zone and UCI, and the status may indicate whether the information about the change has been transmitted to the SGW 105 or not. The indication may be associated with one PDN, connection of the wireless device 103 or individually associated with the wireless device 103. The indication may be a change reported flag.

(161) The mobility management node 101, 101t comprises a transmitter 803 which is configured to, when at least one of the serving network and the time zone and the UCI has been changed for the wireless device 103 and when information about the change has not been transmitted to the SGW 105, transmit the information about at least one of the changed serving network and time zone and UCI, to the SGW 105, enabling the SGW 105 to forward this information to the PGW 108. The transmitter 803 may be configured to transmit the information about the change in a modify bearer request when the indication indicates that information about the change has not been transmitted to the SGW 105. In some embodiments, the transmitter 803 is configured to transmit the information about the change to the SGW 105 in an update bearer response or a create bearer response or a delete bearer response when there is dedicated signaling triggered by the PGW 108. In some embodiments, the information about the change comprises information about at least one of the serving network and the UCI. In some embodiments, the transmitter 803 is configured to transmit the information about at least one of the changed serving network and time zone and UCI to the SGW 105 with least signaling messages over a S11/S4 interface and a S5/S8 interface.

(162) The present mechanism for handling information in a communications network 100 may be implemented through one or more processors, such as a processor 805 in the mobility management node arrangement depicted in FIG. 8, 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. 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 mobility management node 101, 101t and. 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 mobility management node 101, 101t.

(163) The mobility management node 101, 101t may further comprise a memory 808 comprising one or more memory units. The memory 808 is arranged to be used to store data, received data streams, power level measurements, threshold values, time periods, configurations, schedulings, the change reported flag, information about at least one of the serving network and time zone and UCI, information about idle and/or connected mode of the wireless device 103, information elements, messages and applications to perform the methods herein when being executed in the mobility management node 101, 101t.

(164) Those skilled in the art will also appreciate that the obtaining unit 801, the receiver 801a and the transmitter 803 as 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 805 perform as described above.

(165) Alternative embodiments of the mobility management node 101, 101t may comprise additional components beyond those shown in FIG. 8 that may be responsible for providing certain aspects of the mobility management nodes 100, 100t functionality, comprising any of the functionality described above and/or any functionality necessary to support the embodiments described above.

(166) The communications network 100 may further comprise any additional elements suitable to support communication between communication network nodes. The illustrated communications network nodes may represent communications network nodes that comprise any suitable combination of hardware and/or software.

(167) Summarized, the mobility management node 101, 101t has the following logic: (1) when at least one of the serving network and time zone and UCI has changed, transmit at least one of the current serving network and current time zone and current UCI to the SGW 105; and (2) when at least one of serving network and time zone and UCI has not changed, but the indication indicates there is and pending change which has not been reported yet, transmit at least one of the current serving network and time zone and UCI to SGW 105.

(168) For the non-mobility case, the embodiments herein are applicable to the S4-SGSN and the combined SGSN/MME. For the mobility case, the embodiments herein are applicable for the combined SGSN/MME, the standalone MME and the S4-SGSN.

(169) In some embodiments, the Change Reported Flag is comprised in the context response and/or forward relocation request messages. This is in order correct an error case. In some embodiments, at least one of the serving network and time zone and/UCI is comprised in at least one of the create bearer response message and update bearer response message and delete bearer response message when there is a change. This is in order to optimize and to avoid S5/S8 signaling, e.g. MBR, to report the change.

(170) Some embodiments described above may be summarized in the following manner:

(171) One embodiment is directed to a method in a mobility management node for handling information in a communications network, wherein the mobility management node is associated with a wireless device being served by a serving network. The method comprises: obtaining information about that at least one of the serving network or a time zone or a User Closed subscriber group Information, UCI, has been changed for the wireless device, and information about that the change has not been transmitted to a Serving GateWay, SGW associated with the mobility management node; and when at least one of the serving network and the time zone and the UCI, has been changed for the wireless device, and information about the change has not been transmitted to the SGW, transmitting the information about at least one of the changed serving network and time zone and UCI, to the SGW, enabling the SGW to forward this information to a Packet data network Gateway, PGW.

(172) The method may be done as a reaction to or in response to receiving a request message (e.g. a service request or a RAU update or a TAU update request) from the wireless device or receiving a request message (e.g. a relocation request) from a source mobility management node in case the wireless device has previously been associated with a source mobility management node.

(173) The mobility management node may be a target mobility management node associated with the wireless device and the wireless device may previously have been associated with a source mobility management node; and the obtaining information may then further comprise: receiving an indication from the source mobility management node, which indication indicates whether the information about the change has been transmitted to the SGW or not.

(174) The indication may be received in a context response message when the wireless device is in idle mode, and wherein the indication is received in a forward relocation request message when the wireless device is in active mode.

(175) The information about the change may be transmitted in a modify bearer request when the indication indicates that information about the change has not been transmitted to the SGW.

(176) The indication may be an information element comprising bits, wherein each bit corresponds to a status for at least one the serving network and time zone and UCI, which status indicates whether the information about the change has been transmitted to the SGW or not.

(177) The indication may be associated with one Packet Data Network, PDN, connection of the wireless device or individually associated with the wireless device.

(178) The indication may be a change reported flag.

(179) The mobility management node may be a S4-Serving General packet radio service Support Node, S4-SGSN or a Mobility Management Entity, MME, or a combined SGSN/MME.

(180) The obtaining of information may further comprise: detecting, in the mobility management node that at least one of the serving network or time zone or UCI has been changed and that the information about the change has not been transmitted to the SGW.

(181) The information about the change may be transmitted to the SGW in an update bearer response or a create bearer response or a delete bearer response when there is dedicated signaling triggered by the PGW.

(182) The information about the change may comprise information about at least one of the serving network and UCI.

(183) The mobility management node may be a S4-Serving General packet radio service Support Node, S4-SGSN or a combined SGSN/Mobility Management Entity, SGSN/MME.

(184) The communications network may be based on Universal Terrestrial Radio Access Network, UTRAN where a direct tunnel is not used in the communications network, or the communications network may be based on Global System for Mobile Communications, GSM where a direct tunnel is not existing in the communications network.

(185) The information about at least one of the changed serving network and time zone and UCI is transmitted to the SGW with least signaling messages over a S11/S4 interface and a S5/S8 interface.

(186) Some other embodiments described above may be summarized in the following manner:

(187) One embodiment may be directed to a mobility management node for handling information in a communications network, wherein the mobility management node is configured to be associated with a wireless device being served by a serving network. The mobility management node comprises: an obtaining unit configured to obtain information about that at least one of the serving network or a time zone or a User Closed subscriber group Information, UCI, has been changed for the wireless device, and information about that the change has not been transmitted to a Serving Gateway (SGW) associated with the mobility management node; and a transmitter configured to, when at least one of the serving network and the time zone and the UCI has been changed for the wireless device, and information about the change has not been transmitted to the SGW, transmit the information about at least one of the changed serving network and time zone and UCI, to the SGW, enabling the SGW to forward this information to a Packet data network Gateway (PGW).

(188) The obtaining unit may be configured to obtain the information as a reaction to or in response to receiving a request message from the wireless device or from a source mobility management node in case the wireless device has previously been associated with a source mobility management node.

(189) The mobility management node may be a target mobility management node associated with the wireless device and the wireless device may previously have been associated with a source mobility management node; and wherein the obtaining unit is a receiver, which receiver is configured to receive an indication from the source mobility management node, which indication indicates whether the information about the change has been transmitted to the SGW or not.

(190) The receiver may be configured to receive the indication in a context response message when the wireless device is in idle mode, and to receive the indication in a forward relocation request message when the wireless device is in active mode.

(191) The transmitter may be configured to transmit the information about the change in a modify bearer request when the indication indicates that information about the change has not been transmitted to the SGW.

(192) The indication may be an information element comprising bits, wherein each bit corresponds to a status for at least one the serving network and time zone and UCI, which status indicates whether the information about the change has been transmitted to the SGW or not.

(193) The indication may be associated with one Packet Data Network, PDN, connection of the wireless device or individually associated with the wireless device.

(194) The indication may be a change reported flag.

(195) The mobility management node may be a S4-Serving General packet radio service Support Node, S4-SGSN or a Mobility Management Entity, MME or a combined SGSN/MME.

(196) The obtaining unit is configured to detect, in the mobility management node that at least one of the serving network or time zone or UCI has been changed and that the information about the change has not been transmitted to the SGW.

(197) The transmitter may be configured to transmit the information about the change to the SGW in an update bearer response or a create bearer response or a delete bearer response when there is dedicated signaling triggered by the PGW.

(198) The information about the change comprises information about at least one of the serving network and the UCI.

(199) The mobility management node may be a S4-Serving General packet radio service Support Node, S4-SGSN or a combined SGSN/Mobility Management Entity, SGSN/MME.

(200) The communications network may be based on Universal Terrestrial Radio Access Network, UTRAN where a direct tunnel is not used in the communications network, or the communications network may be based on Global System for Mobile Communications, GSM where a direct tunnel is not existing in the communications network.

(201) The transmitter may be configured to transmit the information about at least one of the changed serving network and time zone and UCI to the SGW with least signaling messages over a S11/S4 interface and a S5/S8 interface.

(202) The embodiments described herein are not limited to the above described embodiments. Various alternatives, modifications and equivalents may be used. Therefore, the above embodiments should not be taken as limiting the scope of the embodiments, which is defined by the appending claims.

(203) It should be emphasized that the term comprises/comprising when used in this specification is taken to specify the presence of stated features, integers, steps or components, but does not preclude the presence or addition of one or more other features, integers, steps, components or groups thereof. It should also be noted that the words a or an preceding an element do not exclude the presence of a plurality of such elements.

(204) It should also be emphasized that the steps of the methods defined in the appended claims may, without departing from the embodiments herein, be performed in another order than the order in which they appear in the claims.