WO2013023678A1

WO2013023678A1 - Configuration of time zones in a telecommunication network

Info

Publication number: WO2013023678A1
Application number: PCT/EP2011/063958
Authority: WO
Inventors: Mika Juhani NEVANDER
Original assignee: Nokia Siemens Networks Oy
Priority date: 2011-08-12
Filing date: 2011-08-12
Publication date: 2013-02-21

Abstract

Disclosed is a system, methods, devices, apparatuses and computer program products for configuring time zone information related to an access network element (6-20) in a core network element (6-30). The access network element may transmit one or more messages (6-11) comprising time zone information and at least one a first information element (6-12) of the access network element to the core network element. The at least one first information element identifies at least a part of an area served by the access network element and the time zone information identifies a time zone for the area identified by the at least one first information element. The core network element receives one or more messages comprising time zone information from the access network element and at least one first information element of the access network element, extracts the time zone information and the at least one first information element and stores the extracted time zone information and the at least one first information element in a memory of the core network element and associate them to each other.

Description

Description Title

Configuration of time zones in a telecommunication network

FIELD OF THE INVENTION The present application relates generally to a system, methods, devices or apparatuses, computer programs and computer program products for configuring time zone information in one or more network elements of a telecommunication network.

BACKGROUND ART In telecommunication networks information about time zones related to locations of telecommunication network elements, or related to the locations of devices connecting to the telecommunication network, should be available to network applications and functions. Time zone information may be used for example as input for charging and billing functions of the telecommunication network in order to apply time specific tariffs to users. Today a common time zone is used network wide. Therefore the same time zone may be applied to all network elements and all connected users (a user of such a network may be from network point of view always in the same time zone).

For telecommunication networks, telecommunication network elements and devices connected to the telecommunication network elements, the model of a common network wide time zone may not fit anymore if the network elements/devices are located in different time zones. For example charging and billing might become inaccurate since time specific tariffs might be billed not correctly, because the network assumes a different time zone for billing compared to the one where the device, or the network element where the device is connected to, is located.

SUMMARY

In order to overcome the disadvantage of a common network wide time zone approach, the present invention proposes to configure in one or more core network elements the time zone as a parameter for smaller parts or areas of the network, like for example as an access network element specific parameter (for example for a BTS), or even as a cell or tracking area specific parameter of an access network element. The time zone which may be applied to a device which may connect (or may be connected) to the

telecommunication network may be then determined by one or more core network elements. The core network element may recognize the access network element (e.g. the BTS), the cell or the tracking area where the device of the user may be connected to, and may determine, based on this information, for example the time zone related to the device. Thus for example charging and billing in a network covering several time zones may be done accurately.

However manual configuration of time zone information for parts of a network in one or more core network elements may involve disadvantages:

- high manual configuration effort since for example the time zone of every base station, base station cell or tracking area of a base station may be configured. - difficult to keep up-to-date when the network may grow and new (access) network elements may be added or old (access) network elements may be replaced.

- manual configuration may be error prone, especially if it may happen on base

station cell and tracking area level, since there may be hundreds of base station and thousands of base station specific cells/tracking areas in a telecommunication network.

The present invention may overcome one or more of the listed disadvantages by configuring one or more time zones on access network element level, for example when installing or upgrading an access network element (then the access network element may be configured anyhow). The time zone information may be transmitted from the access network element to the core network element. The core network element may store the time zone information associated with one or more information elements of the access network element, so that the time zone of for example a device which may be connected to the network element, may be later on determined by the core network element based on information element(s) of the access network element which may be stored. According to an exemplary embodiment of the present invention, in a first aspect a method may be provided for configuring time zone information related to an access network element in a core network element, the method may comprise transmitting from the access network element to the core network element one or more messages that may comprise the time zone information and at least one first information element of the access network element, wherein the at least one first information element may identify at least a part of an area served by the access network element and wherein the time zone information may identify a time zone for the area identified by the at least one first information element. According to further refinements of the example of the present invention as defined under the above first aspect, the method may further comprises the claimed subject matter of claim 2 or 3.

According to an exemplary embodiment of the present invention, in a second aspect a method may be provided for configuring time zone information related to an access network element in a core network element, the method may comprise receiving at the core network element one or more first messages which may comprise time zone information from the access network element and at least one first information element of the access network element, extracting the time zone information and the at least one first information element from the one or more first messages, and storing the extracted time zone information and the at least one first information element in a memory and maybe associate them to each other, wherein the at least one first information element may identify at least a part of an area which may be served by the access network element and wherein the time zone information may identify a time zone for the area which may be identified by the at least one first information element. According to further refinements of the examples of the present invention as defined under the above second aspect, the method may further comprises the claimed subject matter of claim 5.

Still according to further refinements of the example of the present invention as defined under the above first and second aspect, the method may further comprises the claimed subject matter of any of the claims 6 to 14.

According to an exemplary embodiment of the present invention, in a third aspect an access network element may be provided which may comprise a transmitting means which may transmit one or more messages that may comprise time zone information and at least one first information element of the access network element from the access network element to a core network element, wherein the at least one first information element may identify at least a part of an area which may be served by the access network element and wherein the time zone information may identify a time zone for the area which may be identified by the at least one first information element. According to further refinements of the example of the present invention as defined under the above third aspect, the access network element may further comprises the claimed subject matter of claim 16 or 17, the transmitting means may be a transmitter or a transmitting unit or a transmitting device, and the storing means may be a storage or a storing unit or a storing device.

According to an exemplary embodiment of the present invention, in a fourth aspect a core network element may be provided which may comprise a first receiving means which may receive one or more first messages that may comprise time zone information from an access network element and at least one first information element of the access network element, a first extracting means which may extract the time zone information and the at least one first information element from the one or more first messages, a storing means which may store the extracted time zone information and the at least one first information element in a memory means and may associate them to each other, wherein the at least one first information element may identify at least a part of an area served by the access network element and wherein the time zone information may identify a time zone for the area which may be identified by the at least one first information element.

According to further refinements of the example of the present invention as defined under the above fourth aspect, the core network element may further comprises the claimed subject matter of any of the claims 19 to 21 , the first receiving means may be a first receiver or a first receiving unit or a first receiving device, the first extracting means may be a first extractor or a first extracting unit or a first extracting device, the storing means may be a storage or a storing unit or a storing device, the second receiving means may be a second received or a second receiving unit or a second receiving device, the second extracting means may be a second extractor or a second extracting unit or a second extracting device, the comparing means may be a comparator or a comparing unit or a comparing device and the determining means may be a determiner or a determining unit or a determining device.

Still according to further refinements of the examples of the present invention as defined under the above third and fourth aspect, the access network element or the core network element may further comprises the claimed subject matter of any of the claims 22 to 30.

According to an exemplary embodiment of the present invention, in a fifth aspect a system for configuring time zone information may be provided which may comprise at last one access network element as defined under the above third aspect and a core network element as defined under the above fourth aspect. According to an exemplary embodiment of the present invention, in a sixth aspect a computer program may be provided which may comprise code for performing the method defined under the above first or second aspect when the computer program may be run on a processor. According to further refinements of the example of the present invention as defined under the above sixth aspect, the computer program may be a computer program product which may comprise a computer-readable medium bearing computer program code which may be embodied therein which may be used with a computer.

According to an exemplary embodiment of the present invention, in a seventh aspect a computer program product may be provided which may comprise a computer-readable medium which may bear computer program code which may be embodied therein and may be used with a computer, the computer program code may comprising

code for performing the method defined under the above first aspect.

According to an exemplary embodiment of the present invention, in an eigth aspect a computer program product may be provided which may comprise a computer-readable medium which may bear computer program code which may be embodied therein and may be used with a computer, the computer program code may comprising code for performing the method as defined under the above second aspect.

The invention may offer the advantage that different time zones may be supported by a telecommunication network and the elements of the telecommunication network, and that time zone specific applications and functions of the telecommunication network may be supported. Thus for example charging and billing in a network covering several time zones may be done accurately.

Further on, according to an example of the invention, the approach how to configure and distribute time zone information in the telecommunication network and its network elements may be less error prone, and may ensure that for example one or more core network elements are automatically kept up-to-date with time zone information related to access network elements, if the telecommunication network may be expanded (for example by adding new access network elements) or if the telecommunication network may be upgraded (for example by upgrading network access elements).

A telecommunication network according to an example of the invention may be for example a fixed telecommunication network or a wireless telecommunication network. A wireless telecommunication networks may be for example Global System for Mobile communication (GSM) network, Universal Mobile Telecommunications System (UMTS) network, Wireless Local Area Network (WLAN), Long Term Evolution (LTE)/System Architecture Evolution (SAE) network or Worldwide Interoperability for Microwave Access (WMax) network.

An access network element may be for example a fixed access network node or a mobile network access node like for example a base station (BTS, BS, NodeB or an evolved NodeB [eNB]) or a base station controller (BSC or an RNC).

A device may be a fixed device (for example any end user device connected via fixed access to the core network) or a mobile device like for example a mobile phone, a Personal Digital Assistant (PDA), a portable computer, a pager, a stationary device capable to access a wireless network or any kind of other device connecting via a radio interface to a wireless network.

A core network element may be for example a Mobility Management Entity (MME).

A Gateway (GW) may be for example a Serving GW (SGW) or a Packet GW (PGW).

Time zone information may comprise a dedicated indication of the time zone or may indicate the offset between an universal time (for example the Greenwich Mean Time

GMT) and the local time where the device may reside, for example in steps of 15 minutes or one hour or with any other granularity.

An information element in the context of this application may be an identifier of an Access Network Element (for example a base station identifier), a cell identifier of a cell covered by the Access Network Element, a tracking area identifier or tracking area code of a tracking area supported by the Access Network Element or any other identifier related to the Access Network element identifying a sub-area covered by the Access Network element.

Various aspects of examples of the invention are set out in the claims.

BRIEF DESCRIPTION OF DRAWINGS

For a more complete understanding of example embodiments of the present invention, reference is now made to the following descriptions taken in connection with the accompanying drawings in which: FIGURE 1 illustrates an example network telecommunication system where access network elements (for example bases stations) may be located in areas of different time zones. FIGURE 2 shows one example access network element (a base station) which may cover various areas which may relate to different time zones.

FIGURE 3 is a flow diagram describing an example method how time zone information may be transmitted by an access network element (for example a base station). FIGURE 4 is a flow diagram showing an example method how time zone information may be configured/stored in a core network element (for example a MME).

FIGURE 5 illustrates an example message flow related to the time zone information transfer which may happen between an access network element (for example a base station) and a core network element (for example a MME). FIGURE 6 shows an example block diagram of an access network element (for example a base station) which may transmit time zone information.

FIGURE 7 shows an example block diagram of a core network element (for example a MME) which may be configured to receive and store time zone information.

DETAILED DESCRIPTION OF SOME EMBODIMENTS

Example embodiments of the present invention and its potential advantages are understood by referring to FIGURES 1 through FIGURE 7 of the drawings.

FIGURE 1 illustrates an example embodiment of the present invention in a

telecommunication network system 1-1. The telecommunication network system 1-1 may be a wireless network comprising of access network nodes 1-20 (in this example base stations - BTS) which are grouped in different time zones 1-71 , 1-72 and 1-73. The base stations 1-20 are connected 1-13 to a core network element 1-30 (for example a MME). The core network element 1-30 may be connected 1-11/1-12 via a gateway 1-50 to telecommunication networks applications or functions 1-60 like for example a billing and charging function/application. Only network elements which may be relevant to describe the present invention are presented in FIGURE 1. In reality more network elements may be located between the network elements shown in FIGURE 1.

When a new base station 1-20 is added to the network 1-1 , or an existing base station 1- 20 is upgraded, the base station 1-20 may be configured with time zone information related to it (for example when the initial configuration of the base station is done). The base station 1-20 may report the configured time zone information together with an information element, which may allow to identify either the base station itself (and so the area covered or served by the base station) or a sub-area covered or served by the base station (for example a base station cell or a tracking area), to the MME 1-30. The reporting may happen by transmitting one or more dedicated message(s) including the time zone information and the information element to the MME 1-30, or by adding the time zone information and the information element to one or more existing message. Those messages may be for example SETUP MESSAGES or CONFIGURATION UPDATE messages or any other kind of message send from BTS 1-20 to the MME 1-30.

A base station 1-20 may report a bunch of time zone information and information elements (for example as time zone information - information element pairs) to the MME 1-30. This may happen if the base station may cover different time zones, which may be the case for different cells served by the base station or different tracking areas where the base station belongs to. The reporting may happen either in one message or by distributing the bunch of time zone information and information elements over several messages. The message(s) may be sent to the MME 1-30 initially when a base station 1-20 is added to the network, when a base station is upgraded, at a later phase or within regular or irregular intervals.

The MME may extract the time zone information and the belonging (for example associated) information element(s) from the received one or more messages and may store it for example in a memory. The memory may be a MME 1-30 internal or external memory. The MME 1-30 may build up a database which may comprise information element - time zone information pairs from various base stations 1-20, base station cells or tracking areas where the base station belongs to. The storing may comprise adding new entries to the database or updating already existing entries (for example if a BTS 1- 20 is upgraded). If a device, for example a mobile device (MD, not shown in FIGURE 1), connects to one of the base stations 1-20, or moves into the area of one base station 1-20, or is handed over between different base stations 1-20, different cells of a base station 1-20 or if it changes its tracking area, at least one involved BTS 1-20 may send an indication (message) to the MME 1-30. The message may comprise information about the mobile device and at least one related information element which may identify for example the base station 1-20, the tracking area or the cell where the mobile device may be connected (=located) to or may be moving to.

The MME 1-30 may extract from the message the information about the mobile device (for example an identification of the mobile device) and the related information element, may compare the information element with the stored information elements in its database, and if a match is found the MME may determine the time zone where the mobile device is currently located (or moving in) by reading the time zone information related/associated to the information element that matches from the database.

The MME (the core network element 1-30) may then report the time zone information of the mobile device ("device time zone") via the gateway 1-50 to for example billing a charging application function 1-60, which may use the mobile device time zone for calculating fees, which may apply to the time zone where the mobile device is located. The transfer of the mobile device time zone from the MME 1-30 to the Billing and

Charging function is shown in 1-11 and 1-12 of FIGURE 1. FIGURE 2 illustrates an example embodiment 2-1 of an Access Network Element (AN) 1- 20 (here a base station) covering several time zones 2-71 , 2-72, 2-73. The base station 2- 20 covers/serves areas 2-81 to 2-86 which may be for example cells or tracking areas of the base station. Each of the areas may be identified by a dedicated information element of the base station 2-20. The areas 2-81 to 2-86 may be located in (or may be assigned to) different time zones, for example area 2-81 may be assigned/located to time zone 2-71 , area 2-82 and 2-86 may be assigned/located to time zone 2-72 and area 2-83 to 2-85 may be assigned/located to time zone 2-73.

The base station 2-20 may report the different information elements (related to areas 2-81 to 2-86) and the belonging time zone information, as described with respect to FIGURE 1 above, to the Core Network Element (for example MME 1-30 in FIGURE 1), which may then build up a database that may comprise entries for each information element and the associated (belonging) time zone information.

Further the base station 2-20 may report to the Core Network Element (for example MME 1-30 in FIGURE 1) if a mobile device (not shown) enters one of the areas 2-81 to 2-86 or moves between any of the areas. The reporting may comprise at least the information element related to the area where the mobile device moves or connects to, and a mobile device information which may be for example a mobile device identification allowing to identity the mobile device.

FIGURE 3 describes an example flow diagram 3-1 related to a method or a process of an Access Network Element (for example a base station 1-20 in FIGURE 1) for transmitting time zone related information to a Core Network Element (for example a MME 1-30 in FIGURE 1).

In step 3-1 1 the Access Network Element (AN) may receive time zone information. The time zone information may comprise information related to one time zone dedicated to the area covered/served by the AN, or may comprise more time zones related to different sub- areas covered/severed by the AN (like for example shown and described in relation to FIGURE 2). Receiving the time zone information may happen either by manual configuration to the AN when the AN may be installed or upgraded, or it may be downloaded to the AN in form of a configuration file for example via a local management port or remotely from a network management system, or it may be configured by any other known means.

In step 3-12 the received time zone information may be stored in the AN, for example in an internal memory of the AN, or an external medium/memory which may be connected to the AN. The time zone information may be stored together with information about the related area(s). Those area(s) may be identified by dedicated information elements as described above in relation to FIGURE 2. The storing may happen for example as dedicated time zone information - first information element(s) pairs, where one or more first information elements, which may be in the same time zone may be stored together with one time zone entry.

In step 3-13 the stored time zone information and the optionally stored related first information element(s) may be read from the memory and may be handed over to the transmitting step 3-14.

In step 3-14 the time zone information and the optionally read related first information element(s) may be transmitted by the AN towards a Core Network Element (CN), like for example the MME 1-30 in FIGURE 1. The transmission may happen either in one or more dedicated messages, or the information may be added to one or more existing messages. The message(s) may be transmitted for example when the AN may be initially configured (when it is installed into the network), when the AN may be upgraded or at any later time point. In order to ensure that information about the time zones and related first information element(s) may be always up-to-date in the Core Network Node (for example the MME), the transmission may happen in regular or irregular intervals from the AN to the Core Network Node. The CN may also request time zone information and the optionally related first information elements from an AN (not shown). The one or more messages may be S1 Application Protocol Messages, for example a S1

SETUP REQUEST or a CONFIGURATION UPDATE message (like an ENB

CONFIGURATION UPDATE message) which may be modified to comprise also the time zone information.

FIGURE 4 describes an example flow diagram 4-1 related to a method or a process of a Core Network Element (CN, for example a MME 1-30 in FIGURE 1) for receiving time zone related information for example from an Access Network Element (AN, BTS 1-20 in FIGURE 1) and for storing this information in the CN.

In step 4-1 1 the CN may receive one or more messages from an AN comprising time zone information and at least one related first information element, both may be related to an area covered/served by the AN. The at least one first information element may be an identifier, for example an AN identifier, a cell identifier, a tracking area identifier or tracking area code, or a combination of those identifiers (for example an AN identifier and a tracking area code or an AN identifier and a cell identifier).

The received time zone information may comprise one or more time zones related to one or more of the first information elements of the AN. Time Zone information and first information element(s) may be received by the one or more messages as pairs, as one to many assignment or many to many assignment (for example several first information elements may be associated to a single time zone like shown in FIGURE 2, where first information elements related to areas 2-83 to 2-85 are in the same time zone 2-73). The received one or more message may comprise time zone information for many time zones or for just one time zone. Further it may comprise time zone and information element pairs or many information elements within the same time zone and related time zone information.

The received one or more message may be a dedicated message or it may be an already existing message which may be extended to transport time zone information and/or at least one first information element.

The received one or more messages may be a S1 Application Protocol messages, for example a S1 SETUP REQUEST or a CONFIGURATION UPDATE message (like a ENB CONFIGURATION UPDATE message) which may be modified to comprise also the time zone information.

In step 4-12 the CN may extract from the in step 4-1 1 received one or more message(s) the time zone information and the related at least one first information elements. If a message may comprise multiple time zone information and multiple first information elements all of them may be extracted. In step 4-13 the extracted time zone information and first information element(s) may be stored. The storing may happen in an internal or external memory of the CN and may be done in a database which may comprise of fields for the time zone information and the related first information element(s). Several information elements may be grouped together with one time zone information. Elements may be stored in time zone - information element pairs in the database.

Such a database table may look like the one shown in table 1 below, where BTS 00001 and BTS 0003 are both members of tracking area TA-0001.

Table 1 : Example of a database table according to an

example of the present invention in a CN

For another example related to cells the tracking area identifier/code in Table 1 may be replaced with a Cell Identifier. At least for the tracking area identifier/code also the AN identifier may be stored, since a tracking area may cover areas belonging to different ANs. If the database may comprise AN identifier and related tracking area identifier(s)/code(s) it may be possible to assign different time zones to the same tracking area depending on the AN (identifier).

In step 4-14 the CN may receive from an AN (which may be the same AN who has sent the message received in step 4-11 or a different AN) one or more second messages which may comprise information about a device connected to the AN (for example an identifier identifying the device) and a second information element from the AN which may indentify the area covered/served by the AN where the device is connected to, and so the location of the device. The second information element may thus be used to identify via the location of the device the time zone of the device. The device may be a mobile device. The information element maybe an identifier of the AN and/or an identifier identifying a sub-area covered by the AN (for example in case of a BTS a cell identifier or a tracking area identifier/code).

In step 4-15 the device information and the second information element may be extracted from the message received in step 4-14. Further in step 4-16 the extracted second information element may be compared with the in step 4-13 in the CN stored first information elements. The second information element may be compared with all first information elements stored in the database of the CN. The comparing may be stopped when a match is found.

If no match is found, the information element (and so the area where the device is located) may not be mapped to a specific time zone. In this case a default time zone may be used (not shown) or the CN may request from the AN the missing time zone information (not shown). Further the CN may signal (for example towards a network management interface) that no match has been found. This may be done for example by generating an error or status message.

If a match is found the time zone related to the location of the mobile device may be determined in step 4-17. This may be done by reading the time zone information related to the first information element entry that matched to the second information element from the database in the CN. The read time zone information may then be the "device time zone" related to the location of the device.

Once the device time zone has been determined in step 4-17, the determined device time zone may be transmitted in step 4-18 by the CN, optionally together with the belonging device information, towards for example a charging and billing application function. The transmission may happen via a gateway as shown in FIGURE 1. Optionally the CN may store (not shown) the device information and the second information element and/or the determined time zone belonging to the device (not shown). FIGURE 5 illustrates an example signaling diagram 5-1 between an AN 5-20 (for example a BTS which may be an eNB) and a CN 5-30 (for example a MME) related to the present invention.

The message 5-11 which may be transmitted from the AN 5-20 to the CN 5-30 may comprise time zone information and/or an AN related first information element(s) and may be a S1 Application Protocol message, like for example a S1 SETUP REQUEST message or a ENB CONFIGURATION UPDATE message.

The message 5-12 may be either a S1 SETUP RESPONSE message or a ENB

CONFIGURATION UPDATE ACKNOWLEDGE message.

Examples of S1 SETUP REQUEST messages modified according to an example of the present invention are given in table 2 and table 3. IE/Group Name Presen Range Criticality Assigned ce Criticality

Message Type M YES reject

Global eNB ID M YES reject eNB Name 0 YES ignore

Supported TAs 1..<maxnoofTACs> GLOBAL reject

>TAC M -

>Broadcast PLMNs 1..<maxnoofBPLM - Ns>

»PLMN Identity M

CSG Id List O to < GLOBAL reject

maxnoofCSGIds >

>CSG Id M

Default paging DRX M YES Ignore eNB Time Zone 0 YES Ignore

Example of S1 SETUP REQUEST message with one

eNB Time Zone valid for the whole area covered

by the eNB

Table 3: Example of S1 SETUP REQUEST message with one

Time Zone parameter per tracking area

of a eNB

The S1 SETUP REQUEST messages may comprise the additional IE/Group Name "(eNB) Time Zone" like shown in table 2 and 3 above (not all fields of the messages are shown).

In table 2 the time zone information "eNB Time Zone" may refer to the time zone information related to an area covered/served by a base station (eNB). In table 3 the time zone information "Time Zone" may refer to the time zone information related to a tracking areas (TAs) covered by a base station (eNB). There may be one "Time Zone" entry per tracking area supported by the base station in the message.

Examples of a ENB CONFIGURATION UPDATE message modified according to an example of the present invention are given in table 4 and table 5.

Example of ENB CONFIGURATION UPDATE message with one eNB Time Zone valid for the whole

area covered by the eNB

Example of ENB CONFIGURATION UPDATE message with one Time Zone parameter per tracking

area of one eNB The ENB CONFIGURATION UPDATE messages may comprise the additional IE/Group Name "(eNB) Time Zone" like shown in table 4 and 5 above (not all fields of the messages are shown).

In table 4 the time zone information "eNB Time Zone" may refer to the time zone information related to an area covered/served by a base station (eNB).

In table 5 the time zone information "Time Zone" may refer to the time zone information related to a tracking areas (TAs) covered by a base station (eNB). There may be one "Time Zone" entry per tracking area supported by the base station in the message.

In table 2, 3, 4 or 5 the "Global eNB ID", the "eNB Name" or "TAC" (Tracking Area Code) may refer to the first information element(s). Instead of a Tracking Area Code also a Tracking Area Identifier (which may comprise of PLMN ID + TAC) may be used.

The Time Zone may be used to indicate the offset between universal time and local time in steps of 15 minutes.

Table 4: Example of eNB Time Zone information

Table 4 shows an example for an eNB Time Zone information. However Table 4 does not define or limit what might be understood as eNB time zone information. For example the shown type number of 1 14 may differ.

The spare bits may indicate unused bits, which may be set to 0 by the sending side and which may be not be evaluated by the receiving side.

Table 5 gives an example how daylight saving time coding, which may be part of the Time Zone information (refer to for example table 4), might be defined. Value

Daylight Saving Time (binary)

Bit 2 Bit 1

No adjustment for Daylight Saving Time 0 0

+1 hour adjustment for Daylight Saving Time 0 1

+2 hours adjustment for Daylight Saving Time 1 0

Spare 1 1

Table 5: Example of daylight saving time coding

FIGURE 6 illustrates an example structure of an AN 6-20 which may transmit time zone information towards a CN 6-30. The AN 6-20 may be a base station (BTS) and the CN 6- 30 may be a Mobility Management Entity (MME).

The AN may comprise of at least a receiving means 6-21 , a storing means 6-22, a memory means (6-26), transmitting means 6-23 and 6-24 and a processor means 6-25. The first and second transmitting means 6-23 and 6-24 may be combined to one means.

The processor means 6-25 may at least control, configure or monitor the other means of the AN 6-20. Further the processor means 6-25 may perform at least parts of the functionality of the other means of AN 6-20. The processor 6-25 may execute code which may perform functions of one or more of the other means of CN 6-20. The functions may be for example those shown in connection with the method described in FIGURE 3.

The AN 6-20 may receive time zone information 6-10 at the receiving means 6-21. Time zone information may be received in any known way, for example via a management command from a network management system (not shown), from a person installing or upgrading the AN 6-20 (not shown) or via a downloading a configuration file (not shown). In addition to the time zone information 6-10 the receiving means 6-21 may receive an information element 6-15 which may indicate to which area, covered by the AN 6-20, the time zone information 6-10 may relate.

The received time zone information 6-10, together with the optional received related information element 6-15, may be stored by the storing means 6-22. Storing may happen inside the AN 6-20, for example in an internal memory means 6-26 which may be part of the storing means 6-20. Optionally the memory means 6-26 may be also located external of the AN 6-20 (not shown), for example in any other kind of known storage means or in another element. The storing of the time zone information 6-10 and the related information element 6-15 may be done in form of a database.

The information stored by the storing means 6-22 may be transmitted by the AN 6-20 towards for example a CN 6-30 via a transmitting means 6-23. The transmitting means 6- 23 may read the information to be transmitted from the memory means 6-26 (for example via the storing means 6-22 if the memory means 6-26 may be part of the storing means 6- 22) and may transmit it in one or more messages towards the CN 6-30. The transmitted information may comprise time zone information 6-11 and a first information element 6-12 which may relate to each other. The first information element 6-12 maybe the optionally received information element 6-15 or another information element generated or configured inside the AN 6-20. The transmitted information may be grouped in time zone - first information element pairs. Optionally several first information elements may be also grouped with one time zone information, for example if the same time zone applies to those first information elements. One message to be transmitted may comprise time zone information of one or more time zones, as well as one or more information elements.

The message transmitted by the transmitting means 6-23 may be a S1 Application Protocol Message as further described in relation to FIGURE 5 (for example a S1 SETUP REQUEST message or a ENB CONFIGURATION UPDATE message). Further a device 6-40 (for example a mobile device) may be connected to the AN 6-20. The device may initially establish a connection to the AN 6-20, or it may move to the area covered by the AN 6-20 (for example handed over from another AN). The device 6-40 may either indicate to the AN 6-20 where it is located (for example to which cell/tracking area of the AN 6-20 it is connected) or the AN 6-20 may detect this by itself. The AN 6-20 may transmit (6-13/6-14) via a further transmitting means 6-24 a second information element 6-14 related to the location of the mobile device 6-40 to the CN 6-30. The information transmitted by the further transmitting means 6-24 may comprise also device 6-40 related information 6-13 (for example identification information of the device 6-40). The CN 6-30 may use this information (6-13, 6-14) to determine the time zone where the device is located.

The transmission of the information by the further transmission means 6-24 may be done either in one or more dedicated messages or the information may be added to one or more already existing messages. Those one or more messages may be for example one of an "INITIAL UE MESSAGE", a "HANDOVER REQUIRED" message or a "PATH SWITCH REQUEST" message.

FIGURE 7 illustrates and example structure of a CN 7-30 which may receive time zone information from an AN 7-20. In the example the AN 7-20 may be a base station (BTS) and the CN 7-30 may be a Mobility Management Entity (MME).

The CN 7-30 may comprise of at least a first receiving means 7-31 , an first extracting means 7-32, a storing means 7-33, a memory means 7-331 (which may be part of the storing means 7-33), a comparing means 7-34, a determining means 7-35, a transmitting means 7-36, a second receiving means 7-38, a second extracting means 7-39 and a processor means 7-37.

The first and second receiving means 7-31 and 7-38 may be combined to one means. The first and second extracting means 7-32 and 7-39 may be combined to one means.

The processor means 7-37 may at least control, configure or monitor the other means of the CN 7-30. Further the processor means 7-37 may perform at least parts of the functionality of the other means of CN 7-30. The processor 7-37 may execute code which may perform functions of one or more of the other means of CN 7-30. The functions may be for example those shown in connection with the method described in FIGURE 4.

The CN 7-30 may receive at the first receiving means 7-31 one or more first messages which may comprise time zone information 7-1 1 and at least one first information element 7-12 from an AN 7-20. The first receiving means 7-31 may receive separate messages for the time zone information 7-1 1 and the at least one first information element 7-12, or one message comprising of both or one message comprising of multiple time zone information 7-11 and/or multiple first information elements 7-12.

The time zone information 7-1 1 and the at least one first information element 7-12 may be extracted from the received one or more first messages by a first extracting means 7-32.

The extracted information may be forwarded to a storing means 7-33 which may store the information in a memory means 7-331. The memory means 7-331 may be part of the storing means 7-33 or may be a separate means of the AN 7-30 (not shown) or may be located outside AN 7-30 (not shown). The memory means 7-331 may be any kind of known means that is able to store information like for example RAMs, flash memories or hard disks. Storing of the time zone information 7-1 1 and the at least one first information element 7-

12 in the memory means 7-331 may be done in database format by for example storing separate database entries for each time zone information 7-1 1 / first information element 7-12 pair. Optionally different information elements 7-12 may be grouped if they belong to the same time zone and may be stored together with the related time zone information 7- 11 as one database entry.

Further the CN 7-30 may receive one or more second messages from an AN 7-20 (which may be the same AN from which the one or more first messages might have been received by the first receiving means 7-31 or a different AN) which may comprise a second information element 7-14 and optionally related device 7-40 information 7-13, which may allow the CN 7-30 to identify the device 7-40. The second information element 7-14 and the related device information 7-13 may be received in one message or in separate messages. The device may be a mobile device.

The one or more second messages may be send from an AN 7-20 where the device 7-40 may be connected to, or is trying to connect to. The second information element may identify the area where the device 7-40 is connected to, wherein the area may be the whole area covered by the AN 7-20 or a sub-area which may be covered by AN 7-20 (for example a cell of the AN 7-20 or a tracking area supported by the AN 7-20, for details refer to FIGURE 2 and the related description). Thus the information element may identify the area where the device 7-40 is located and may be used by the CN 7-30 to determine the time zone of the device 7-40 (see description related to the means 7-34 and 7-35 below).

The device information 7-13 and the second information element 7-14 may be extracted from the received one or more second message by a second extracting means 7-39. The information extracted by the second extracting means 7-39 may be used by a comparing means 7-34 which may compare the extracted second information element 7- 14 and the first information element(s) stored in the memory means 7-331. The comparing means 7-39 may compare the extracted second information element 7-14 with all first information elements stored in the memory means 7-331 of the CN 7-30. The comparing may be stopped when a match is found.

If no match is found, the second information element (and so the location where the device is located) may not be mapped to a specific time zone. In this case a default time zone may be used (not shown) or the CN 7-30 may request from the AN 7-20 the missing time zone information (not shown). Further the CN 7-30 may signal (for example towards a network management interface) that no match has been found. This may be done by for example generating an error or status message by the CN 7-30 (not shown).

If a match is found the time zone related to the location of the device 7-40 may be determined by the determining means 7-35. The determining means 7-35 may read the time zone information related to the first information element entry that matched to the second information element 7-14 from the memory means 7-331. The read time zone information may then be the time zone related to the location of the device 7-40 (the "device time zone").

When the time zone related to the device 7-40 has been determined by CN 7-30, the transmitting means 7-36 may transmit the device time zone information 7-15 (optionally together with the belonging device information 7-16) for example to a charging and billing application function. The device time zone 7-15 and the device information 7-16 may be transmitted by the transmitting means 7-36 in a single message or in separate messages. Transmission may happen after the device time zone has been detected, or later, for example if the information may be requested from the CN 7-30. The transmission may happen via a gateway as shown in FIGURE 1.

Optionally the CN 7-30 may store (not shown) the device information 7-13, 7-16 and the second information element 7-14 and/or the determined device time zone 7-15.

The AN 7-20, from which the CN 7-30 receives the first and the second message(s), may be the same or different access network element(s).

Without in any way limiting the scope, interpretation, or application of the claims appearing below, a technical effect of one or more of the example embodiments disclosed herein is that no manual configuration of time zones associated with access network elements or access network element information (for example cell identifier or tracking area identifier/code) in a core network element may be needed. Another technical effect of one or more of the example embodiments disclosed herein is that changes in the access network structure (for example when adding/removing or replacing access network nodes) may lead to a reconfiguration of belonging time zone information associated with those access network elements or related access network element information (for example cell identifier or tracking area identifier/code) in a core network element. Another technical effect of one or more of the example embodiments disclosed herein is that errors due to excessive manual configuration effort, which may be otherwise needed for the core network element, may be avoided.

The used term "means" throughout the description is equivalent to the term "unit" or "device". Therefore the term "means" may be also read and/or replaced throughout the whole description by the term "unit" or "device".

Time aspects shown in FIGURE 1 to FIGURE 7 do not restrict any one of the shown steps or means to be limited to the step or means sequence as outlined. This applies in particular to method steps that may be functionally disjunctive with each other. Embodiments of the present invention may be implemented in software, hardware, application logic or a combination of software, hardware and application logic. The software, application logic and/or hardware may reside on one or more network elements, network devices or network apparatuses. If desired, part of the software, application logic and/or hardware may reside on one or more core network elements (for example MMEs), part of the software, application logic and/or hardware may reside on one or more access network elements (for example a base stations). In an example embodiment, the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media. In the context of this document, a "computer- readable medium" may be any media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer, with one example of a computer described and depicted in FIGURE 6 and FIGURE 7. A computer-readable medium may comprise a computer-readable storage medium that may be any media or means that can contain or store the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.

If desired, the different functions discussed herein may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the above- described functions may be optional or may be combined. Although various aspects of the invention are set out in the independent claims, other aspects of the invention comprise other combinations of features from the described embodiments and/or the dependent claims with the features of the independent claims, and not solely the combinations explicitly set out in the claims.

It is also noted herein that while the above describes example embodiments of the invention, these descriptions should not be viewed in a limiting sense. Rather, there are several variations and modifications which may be made without departing from the scope of the present invention as defined in the appended claims.

Reference signs in the claims are added to show how the claims could be mapped to the example embodiments and are not limiting the scope of protection of the claims.

Claims

ims

A method for configuring time zone information related to an access network element (6-20) in a core network element (6-30), the method comprising of

- transmitting (3-14) from the access network element (6-20) to the core network element (6-30) one or more messages comprising the time zone information (6-1 1) and at least one first information element (6-12) of the access network element (6-20), wherein the at least one first information element (6-12) identifies at least a part of an area (2-81) served by the access network element (2-20) and

wherein the time zone information (6-1 1) identifies a time zone (2-71) for the area (2-81) identified by the at least one first information element (6-12).

The method according to claim 1 further comprising

- storing (3-12) time zone information related to an area covered by the access network element in a memory of the access network element; and

- reading (3-13) the time zone information from the memory of the access network element in order to transmit it.

The method according to any of the preceding claims wherein the method is used for the determination of a time zone where a device (6-40) connected to the access network element (6-20) is located.

A method for configuring time zone information related to an access network element (7-20) in a core network element (7-30), the method comprising of

- receiving (4-11) at the core network element (7-30) one or more first messages comprising time zone information from the access network element (7-1 1) and at least one first information element (7-12) of the access network element (7-20); and

- extracting (4-12) the time zone information (7-1 1) and the at least one first information element (7-12) from the one or more first messages; and

- storing (4-13) the extracted time zone information (7-1 1) and the at least one first information element (7-12) in a memory (7-331) and associate them to each other, wherein the at least one first information element (7-12) identifies at least a part of an area (2-81) served by the access network element (2-20) and

wherein the time zone information (7-1 1) identifies a time zone (2-71) for the area (2-81) identified by the at least one first information element (7-12).

The method according to claim 4, wherein the method is used for the determination of a time zone where a device (7-40) is located, the method further comprising of - receiving (4-14) at the core network element (7-20) one or more second messages comprising a device information (7-13) and a second information element (7-14) of an access network element (7-20) where the device (7-40) is connected to; and

- extracting (4-15) the device information (7-13) and the second information element (7-14) from the one or more second messages; and

- comparing (4-16) the second information element (7-14) with the stored at least one first information element (7-12); and

- determining (4-17) the time zone of the device (7-40) if the second information element (7-14) matches with the at least one first information elements (7-12) stored in the memory (7-331),

wherein if a match is detected the time zone of the device (7-40) is the time zone information (7-1 1) stored in the memory associated with the at least one first information element (7-12) that matches. 6. The method according to any of the preceding claims wherein the time zone information (7-11) is at least one of a time zone information per tracking area (2-72), a time zone information per cell (2-73) and a time zone information per base station (1-71).

7. The method according to any of the preceding claims wherein the first information

element (6-12, 7-12) or the second information element (6-14, 7-14) is at least one of an access network element identifier and a tracking area identifier and a tracking area code and a cell identifier.

8. The method according to any of the preceding claims wherein the by the access

network element (6-20, 5-20) transmitted message (5-11) or the by the core network element (7-30, 5-30) received first message (5-1 1) is a S1 APPLICATION

PROTOCOL message.

9. The method according to claim 8 wherein the S1 APPLICATION PROTOCOL message

(5-11) is one of a "S1 SETUP REQUEST" message and an ΈΝΒ CONFIGURATION UPDATE" message.

10. The method according to any of the preceding claims wherein the time zone

information comprises daylight saving information.

11. The method according to any of the preceding claims wherein the access network element (6-20, 7-20) or the access network element where the device is connected to (6-20, 7-20) is a base station (1-20).

12. The method according to claim 11 wherein the base station is a NodeB or an eNodeB.

13. The method according to any of the claims 2, 3 or 5 to 10 wherein the device is a

mobile device (6-40, 7-40).

14. The method according to any of the preceding claims wherein the core network

element is a Mobility Management Entity (1-30).

15. An access network element (6-20) comprising of

- a transmitting means (6-23) transmitting one or more messages comprising time zone information (6-1 1) and at least one first information element of the access network element (6-12) from the access network (6-20) element to a core network element (6-30),

wherein the at least one first information element (6-11) identifies at least a part of an area (2-81) served by the access network element (2-20) and

wherein the time zone information (6-12) identifies a time zone (2-71) for the area (2-81) identified by the at least one first information element (6-11).

16. The access network element (6-20) according to claim 15 further comprising

- a storing means (6-22) storing the time zone information (6-10) related to an area covered by the access network element (6-20) in a memory means (6-26).

17. The access network element (6-20) according to claim 15 or claim 16 wherein the time zone information (6-1 1) is used for the determination of a time zone where a device (6-40) connected to the access network element (6-20) is located.

18. A core network element (7-30) comprising of

- a first receiving means (7-31) receiving one or more first messages comprising time zone information (7-1 1) from an access network element (7-20) and at least one first information element (7-12) of the access network element (7-20); and

- a first extracting means (7-32) extracting the time zone information (7-1 1) and the at least one first information element (7-12) from the one or more first messages; and

- a storing means (7-33) storing the extracted time zone information (7-11) and the at least one first information element (7-12) in a memory means (7-331) and associate them to each other,

wherein the at least one first information element (7-12) identifies at least a part of an area (2-81) served by the access network element (2-20) and

19. The core network element (7-30) according to claim 18, wherein the time zone information (7-1 1) is used for the determination of a time zone where a device (7-40) is located, the core network element (7-30) further comprising of

- a second receiving means (7-38) receiving one or more second messages comprising a device information (7-13) and a second information element (7-14) of an access network element (7-20) where the device (7-40) is connected to; and

- a second extracting means (7-39) extracting the device information (7-13) and the second information element (7-14) from the one or more second messages; and

- a comparing means (7-34) comparing the extracted second information element (7- 14) with the at least one first information element (7-12) stored in the memory means

(7-331); and

- a determining means (7-35) determining the time zone of the device (7-40) if the second information element (7-14) matches with the at least one first information element (7-12) stored in the memory means (7-331), and wherein if a match is detected the time zone of the device (7-40) is the time zone information (7-11) stored in the memory means (7-331)associated with the at least one first information element (7-12) that matches.

20. The core network element (7-30) according to claims 18 and 19 wherein the first (7- 31) and second (7-38) receiving means are combined in one receiving means. 21. The core network element (7-30) according to any of the claims 18 to 20 wherein the first (7-32) and second (7-39) extracting means are combined in one extracting means.

22. The core network element (7-30) according any of the claims 18 to 21 or the access network element (6-20) according to any of the claims 15 or 17 wherein the time zone information (6-1 1 , 7-1 1) is at least one of time zone information per tracking area (2-

72) and time zone information per cell (2-73) and time zone information per network access element (1-20).

23. The core network element (7-30) according any of the claims 18 to 22 or the access network element (6-20) according to any of the claims 15 to 17 or 22 wherein the first information element (6-11 , 7-1 1) or the second information element (6-14, 7-14) is at least one of a base station identifier and a tracking area identifier and a tracking area code and a cell identifier.

24. The core network element (7-30, 5-30) according any of the claims 18 to 23 or the access network element (6-20, 5-20) according to any of the claims 15 to 17, 22 or 23 wherein the by the access network element (5-20) transmitted one or more message (5-11) or the by the core network element (5-30) received one or more first message (5-11) is a S1 APPLICATION PROTOCOL message.

25. The core network element (5-30) or the access network element (5-20) according to claim 24 wherein the S1 APPLICATION PROTOCOL message (5-11) is one of a "S1

SETUP REQUEST" message and an ΈΝΒ CONFIGURATION UPDATE" message.

26. The core network element (7-30) according to any of the claims 18 to 25 or the access network element (6-20) according to any of the claims 15 to 17 or 22 to 25 wherein the time zone information (6-1 1 , 7-1 1) comprises daylight saving information. 27. The access network element (6-20) according to any of the claims 15 to 17 or 22 to 26 wherein the access network element (6-20) is a base station (1-20).

28. The base station (1-20) according to claim 27 wherein the base station is a NodeB or an eNodeB.

29. The access network element (6-20) according to any of the claims 16 or 22 to 26 or the core network element (7-30) according to any of the claims 19 to 26 wherein the device (6-40, 7-40) is a mobile device.

30. The core network element (7-30) according to any of the claims 18 to 26 wherein the core network element is a Mobility Management Entity (1-30, 7-30).

31. A system (1-1) for configuring time zone information related to at last one access network element (1-20) in a core network element (1-30) the system comprising of at least one access network element (6-20) according to any of the claims 15 to 17 or 22 to 29 and a core network element (7-30) according to any of the claims 18 to 26 or 29 or 30.

32. A computer program comprising code for performing a method (3-1 , 4-1) according to any of the claims 1 to 14 when the computer program is run on a processor (6-25, 7- 37).

33. The computer program according to claim 32, wherein the computer program is a computer program product comprising a computer-readable medium bearing computer program code embodied therein for use with a computer.