WO2016128026A1

WO2016128026A1 - Periodic subscriber data resynchronization

Info

Publication number: WO2016128026A1
Application number: PCT/EP2015/052690
Authority: WO
Inventors: Peter Unbehau
Original assignee: Nokia Solutions and Networks Oy
Current assignee: Nokia Solutions and Networks Oy
Priority date: 2015-02-10
Filing date: 2015-02-10
Publication date: 2016-08-18
Anticipated expiration: 2017-08-10

Abstract

Systems, methods, apparatuses, and computer program products for subscriber data synchronization are provided. One method includes computing, by a server in a communications network, a synchronization parameter, and providing the synchronization parameter to at least one serving node. A value of the synchronization parameter indicates a maximum date and/or time that a subscriber is granted service without having subscriber data synchronized between the server and the at least one serving node.

Description

DESCRIPTION

TITLE

PERIODIC SUBSCRIBER DATA RESYNCHRONIZATION

BACKGROUND: Field:

[0001] Embodiments of the invention generally relate to wireless or mobile communications networks, such as, but not limited to, the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), future 5G radio access technology, and/or High Speed Packet Access (HSPA). In particular, some embodiments may relate to subscriber data management in such networks.

Description of the Related Art: [0002] Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN) refers to a communications network including base stations, or Node Bs, and for example radio network controllers (RNC). UTRAN allows for connectivity between the user equipment (UE) and the core network. The RNC provides control functionalities for one or more Node Bs. The RNC and its corresponding Node Bs are called the Radio Network Subsystem (RNS). In case of E-UTRAN (enhanced UTRAN), no RNC exists and most of the RNC functionalities are contained in the enhanced Node B (eNodeB or eNB).

[0003] Long Term Evolution (LTE) or E-UTRAN refers to improvements of the UMTS through improved efficiency and services, lower costs, and use of new spectrum opportunities. In particular, LTE is a 3GPP standard that provides for uplink peak rates of at least, for example, 75 megabits per second (Mbps) per carrier and downlink peak rates of at least, for example, 300 Mbps per carrier. LTE supports scalable carrier bandwidths from 20 MHz down to 1 .4 MHz and supports both Frequency Division Duplexing (FDD) and Time Division Duplexing (TDD).

[0004] As mentioned above, LTE may also improve spectral efficiency in networks, allowing carriers to provide more data and voice services over a given bandwidth. Therefore, LTE is designed to fulfill the needs for high-speed data and media transport in addition to high-capacity voice support. Advantages of LTE include, for example, high throughput, low latency, FDD and TDD support in the same platform, an improved end- user experience, and a simple architecture resulting in low operating costs.

[0005] Certain releases of 3GPP LTE (e.g., LTE Rel-10, LTE Rel-1 1 , LTE Rel-12, LTE Rel-13) are targeted towards international mobile telecommunications advanced (IMT-A) systems, referred to herein for convenience simply as LTE-Advanced (LTE-A).

[0006] LTE-A is directed toward extending and optimizing the 3GPP LTE radio access technologies. A goal of LTE-A is to provide significantly enhanced services by means of higher data rates and lower latency with reduced cost. LTE-A is a more optimized radio system fulfilling the international telecommunication union-radio (ITU-R) requirements for I MT- Advanced while keeping the backward compatibility. One the key features of LTE-A, introduced in LTE Rel-10, is carrier aggregation, which allows for increasing the data rates through aggregation of two or more LTE carriers.

SUMMARY: [0007] One embodiment is directed to a method that may include computing, by a server in a communications network, a synchronization parameter. The method may also include providing the synchronization parameter to at least one serving node. A value of the synchronization parameter indicates a maximum date and/or time that a subscriber is granted service without having subscriber data synchronized between the server and the at least one serving node.

[0008] Another embodiment is directed to an apparatus that may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus at least to compute a synchronization parameter, and provide the synchronization parameter to at least one serving node. A value of the synchronization parameter indicates a maximum date and/or time that a subscriber is granted service without having subscriber data synchronized between the server and the at least one serving node.

[0009] Another embodiment is directed to an apparatus that may include computing means for computing a synchronization parameter, and providing means for providing the synchronization parameter to at least one serving node. A value of the synchronization parameter indicates a maximum date and/or time that a subscriber is granted service without having subscriber data synchronized between the apparatus and the at least one serving node. [0010] Another embodiment is directed to a computer program embodied on a computer readable medium. The computer program may be configured to control a processor to perform a process which may include computing a synchronization parameter. The process may also include providing the synchronization parameter to at least one serving node. A value of the synchronization parameter indicates a maximum date and/or time that a subscriber is granted service without having subscriber data synchronized between the server and the at least one serving node.

[0011] Another embodiment is directed to a method that may include receiving, by a serving node, a synchronization parameter, where a value of the synchronization parameter indicates a maximum date and/or time that a subscriber is granted service without having subscriber data synchronized between the serving node and a home subscriber server (HSS). The method may also include determining based on the received synchronization parameter, at predetermined synchronization points, whether subscriber data synchronization with the home subscriber server (HSS) is required, and triggering synchronization with the home subscriber server (HSS) when it is determined that the subscriber data synchronization with the home subscriber server (HSS) is required.

[0012] Another embodiment is directed to an apparatus that may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus at least to receive a synchronization parameter, where a value of the synchronization parameter indicates a maximum date and/or time that a subscriber is granted service without having subscriber data synchronized between the apparatus and a home subscriber server (HSS). The at least one memory and the computer program code may be further configured, with the at least one processor, to cause the apparatus at least to determine based on the received synchronization parameter, at predetermined synchronization points, whether subscriber data synchronization with the home subscriber server (HSS) is required, and trigger synchronization with the home subscriber server (HSS) when it is determined that the subscriber data synchronization with the home subscriber server (HSS) is required.

[0013] Another embodiment is directed to an apparatus that may include receiving means for receiving a synchronization parameter, where a value of the synchronization parameter indicates a maximum date and/or time that a subscriber is granted service without having subscriber data synchronized between the apparatus and a home subscriber server (HSS). The apparatus may also include determining means for determining based on the received synchronization parameter, at predetermined synchronization points, whether subscriber data synchronization with the home subscriber server (HSS) is required, and triggering means for triggering synchronization with the home subscriber server (HSS) when it is determined that the subscriber data synchronization with the home subscriber server (HSS) is required.

[0014] Another embodiment is directed to a computer program embodied on a computer readable medium. The computer program may be configured to control a processor to perform a process which may include receiving a synchronization parameter, where a value of the synchronization parameter indicates a maximum date and/or time that a subscriber is granted service without having subscriber data synchronized between the serving node and a home subscriber server (HSS). The process may also include determining based on the received synchronization parameter, at predetermined synchronization points, whether subscriber data synchronization with the home subscriber server (HSS) is required, and triggering synchronization with the home subscriber server (HSS) when it is determined that the subscriber data synchronization with the home subscriber server (HSS) is required.

BRIEF DESCRIPTION OF THE DRAWINGS:

[0015] For proper understanding of the invention, reference should be made to the accompanying drawings, wherein:

[0016] Fig. 1 illustrates an example signaling diagram, according to one embodiment;

[0017] Fig. 2a illustrates a block diagram of an apparatus, according to an embodiment;

[0018] Fig. 2b illustrates a block diagram of an apparatus, according to another embodiment;

[0019] Fig. 3a illustrates a flow diagram of a method, according to one embodiment;

[0020] Fig. 3b illustrates a flow diagram of a method, according to another embodiment;

[0021] Fig. 4a illustrates a block diagram of an apparatus, according to another embodiment; and

[0022] Fig. 4b illustrates a block diagram of an apparatus, according to another embodiment.

DETAILED DESCRIPTION:

[0023] It will be readily understood that the components of the invention, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of embodiments of systems, methods, apparatuses, and computer program products for periodic subscriber data resynchronization, for example, between a serving node and home subscriber server (HSS), as represented in the attached figures, is not intended to limit the scope of the invention, but is merely representative of some selected embodiments of the invention.

[0024] The features, structures, or characteristics of the invention described throughout this specification may be combined in any suitable manner in one or more embodiments. For example, the usage of the phrases "certain embodiments," "some embodiments," or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present invention. Thus, appearances of the phrases "in certain embodiments," "in some embodiments," "in other embodiments," or other similar language, throughout this specification do not necessarily all refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0025] Additionally, if desired, the different functions discussed below may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the described functions may be optional or may be combined. As such, the following description should be considered as merely illustrative of the principles, teachings and embodiments of this invention, and not in limitation thereof.

[0026] Certain embodiments of the invention may generally relate to subscriber data management in 3GPP networks, for example. In a 3GPP network, subscriber data may be stored or held in the Home Subscriber Server (HSS) and downloaded towards the serving nodes, such as the mobility management entity (MME), the serving general packet radio service support node (SGSN), and/or the visitor location register (VLR). The subscriber data may be downloaded to the serving node(s) during an Update Location/Restore Data or standalone Insert Subscriber Data operations.

[0027] Subscriber data should be in synchronization between the HSS and the serving nodes. Service execution in the visited serving nodes relies on this data. Data inconsistencies between the HSS (having master copy of data) and serving nodes (having derived/downloaded copy of data) may result in faulty service execution.

[0028] There are a number of scenarios where the data in the serving nodes may become out of sync, for example: Unsuccessful standalone Insert Subscriber Data (ISD) operations: ISD/IDR messages can be lost in the network, for instance, due to network/transmission problems and overload situations. The repetition of these operations in the HSS (in case of unsuccessful outcome) might also fail. The serving nodes may be unaware of the fact that the subscriber data are not in sync.

Use of profile data in the HSS: The HSS might use subscriber data profiles assigned to a group of subscribers which have identical/similar requirements with regard to the service profile (e.g., Machine To Machine type communication subscribers). A modification of these profile data by the operator usually impacts a large number of subscribers and is usually not propagated towards the serving nodes with single update messages.

[0029] Data inconsistencies between the HSS and the serving nodes are prevented or corrected when the UE moves from one visited serving node (VLR/SGSN/MME) to another. In this situation, Update Location towards the HSS is performed and the subscriber data are downloaded towards the serving nodes in the Update Location transaction, thereby ensuring data consistency.

[0030] For low- and no-mobility subscribers (e.g., vending machines using Machine To Machine type communication) the situation is different since Update Location towards the HSS caused by a serving node area change takes place with only low frequency or does not take place at all. Consequently, in this case, data inconsistencies may persist for a long time period.

[0031] One embodiment of the invention allows for subscriber data resynchronization between the HSS and serving nodes based on a time interval or time out parameter. In an embodiment, this time out parameter may be referred to as a HSS synchronization time- out parameter. The value of this time-out parameter may be freely configured per subscriber (or subscriber type) in the HSS and may then be downloaded towards the serving node(s).

[0032] According to certain embodiments, when the serving node detects that, for a subscriber, the pre-configured time passes without Update Location towards the HSS, synchronization with the HSS (at the next radio contact) is forced by the serving node executing the Update Location or Restore Data procedure towards the HSS.

[0033] According to an embodiment, a new synchronization parameter is introduced/configured and optionally assigned to individual subscribers. In one embodiment, the synchronization parameter is an HSS-Synchronization-Time-out parameter. In this embodiment, the HSS-Synchronization-time-out represents the maximum time that a subscriber is granted service without having synchronized the subscriber data in the serving node(s) with the HSS database. In other words, in one embodiment, the value of the HSS-Synchronization-time-out parameter indicates the maximum time that a subscriber may be provided service without the subscriber data being synchronized between the serving node(s) and the HSS.

[0034] In certain embodiments, the HSS-Synchronization-time-out parameter may be freely chosen by the operator and may be different for different subscribers / subscriber types. For example, an operator could assign a HSS-synchronization-time-out to all Machine To Machine type communication subscribers only. In one example, the parameter may specify a time, for instance up to 1000 hours with a granularity of for example 1 hour. Of course other examples of time and granularity are also possible. In an embodiment, the parameter is a part of the subscriber data and stored in the HSS permanent data.

[0035] According to some embodiments, the protocols on the Gr-, D-, S6a- and S6d interfaces may be extended with the new (optional) HSS-Synchronization-time-out parameter. In certain embodiments, this parameter may be downloaded towards the serving nodes during the Update Location-, Restore Data- and/or standalone subscriber data management procedures and may be stored in the subscriber's data set.

[0036] In addition, in one embodiment, the serving node(s) may store a time stamp indicating the time of the last Update Location/Restore Data procedure towards the HSS (UTC, with the granularity of, e.g., 1 hour).

[0037] According to another embodiment, in addition to or instead of the HSS- Synchronization-Time-out parameter (which represents a duration), an HSS- Synchronization-Due-Date parameter (point in time) may be introduced and/or configured. For example, in this embodiment, during the Update Location-, Restore Data- and/or standalone subscriber data management procedures the HSS may compute the value of this parameter using the following formula:

HSS-Synchronization-Due-Date = current date (UTC) + HSS-Synchronization-Time- out

[0038] This HSS-Synchronization-Due-Date parameter may be downloaded towards the serving node(s) (instead of downloading the HSS-Synchronization-Time-out) during the Update Location-, Restore Data- and/or standalone subscriber data management procedures. For example, the HSS-Synchronization-Due-Date parameter may specify a date/time with the granularity of, e.g., 1 hour. [0039] In an embodiment, the serving node(s) may check whether subscriber data (re- )synchronization with the HSS is required when hitting pre-defined synchronization points, such as one of the following events: location area update (LAU)/routing area update (RAU)/tracking area update (TAU); any radio contact with the UE; serving node database access for the UE; any mobile originating event of the UE; or any mobile terminating event for the UE.

[0040] As discussed above, in one embodiment, an HSS-Synchronization-Time-out received and stored in the serving node(s). The serving node(s) may compare the current time (i.e., the time at which the check is performed) with the time the last Update Location / Restore Data operation was performed towards the HSS (as discussed above the serving node(s) may store a time stamp indicating the time of the last Update Location/Restore Data procedure towards the HSS) and compute the time difference. If the time difference is greater than the HSS-Synchronization-time-out parameter previously received from the HSS and stored in the subscriber's data set, it is determined that subscriber data synchronization with the HSS is required.

[0041] As also discussed above, in another embodiment, an HSS-Synchronization-Due- Date parameter is received and stored in the serving node(s). The serving node(s) may compare the current time (i.e., the time at which the check is performed) with the HSS- Synchronization-Due-Date previously received from the HSS and stored in the subscriber's data set. If the current time is greater (i.e., later in time) than the HSS- Synchronization-Due-Date, it is determined that subscriber data synchronization with the HSS is required.

[0042] If it is determined or detected that subscriber data (re-)synchronization is required, the HSS may perform an Update Location or Restore Data operation respectively towards the HSS in order to trigger the complete subscriber data download.

This download ensures data consistency by its transactional nature. In certain embodiments, the serving node(s) may make use of existing mechanisms in order to integrate the new functionality into the existing handling. Examples of these existing mechanisms, for example, may include:

· The serving node (e.g., MME) triggering Update Location towards the HSS upon receipt of a TAU when the "Subscriber Data Confirmed by HSS" flag in MME is set to false. So setting this flag when data re-synchronization is required would automatically cause Update Location towards the HSS. • The serving node (e.g., MSC/VLR) triggers Restore Data towards HSS upon receipt of 1AM (Initial Address Message during Mobile Terminating Call attempt) if "Subscriber Data_Confirmed by HSS" is set to false in the VLR. So setting this flag when data re-synchronization is required would automatically cause Restore data towards the HSS.

[0043] Fig. 1 illustrates an example flow diagram, according to one embodiment of the invention. As illustrated in Fig. 1 , at 1 , a UE (IMSI 1 ) attaches to the MME and the MME sends an update location request (ULR) towards the HSS. At 2, the HSS may apply new service logic and compute the HSS synchronization due date parameter. Then, at 3, the HSS may send the HSS synchronization due date parameter towards the MME in ULA. At 4, the subscriber data may be changed by an operator for IMSI 1 , HSS may attempt data download towards the MME, and in this example the attempt (including all re-attempts) fails. At 5, the UE may attempt periodic TAU and, at 6, the MME may apply new service logic and detect that HSS synchronization is required. At 7, the MME may perform Update Location towards the HSS, data synchronization takes place and a new value of HSS synchronization due date parameter (in this example the value is 02.09.2014 22:00 UTC + 10Oh) is downloaded.

[0044] Fig. 2a illustrates an example of an apparatus 10 according to an embodiment. In an embodiment, apparatus 10 may be a node, host, or server in a communications network or serving such a network. For example, apparatus 10 may be a network node or server in a radio access network, such as an HSS. It should be noted that one of ordinary skill in the art would understand that apparatus 10 may include components or features not shown in Fig. 2a.

[0045] As illustrated in Fig. 2a, apparatus 10 includes a processor 22 for processing information and executing instructions or operations. Processor 22 may be any type of general or specific purpose processor. While a single processor 22 is shown in Fig. 2a, multiple processors may be utilized according to other embodiments. In fact, processor

22 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples.

[0046] Apparatus 10 may further include or be coupled to a memory 14 (internal or external), which may be coupled to processor 22, for storing information and instructions that may be executed by processor 22. Memory 14 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and removable memory. For example, memory 14 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, or any other type of non- transitory machine or computer readable media. The instructions stored in memory 14 may include program instructions or computer program code that, when executed by processor 22, enable the apparatus 10 to perform tasks as described herein.

[0047] In some embodiments, apparatus 10 may also include or be coupled to one or more antennas 25 for transmitting and receiving signals and/or data to and from apparatus 10. Apparatus 10 may further include or be coupled to a transceiver 28 configured to transmit and receive information. For instance, transceiver 28 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 25 and demodulate information received via the antenna(s) 25 for further processing by other elements of apparatus 10. In other embodiments, transceiver 28 may be capable of transmitting and receiving signals or data directly.

[0048] Processor 22 may perform functions associated with the operation of apparatus 10 which may include, for example, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 10, including processes related to management of communication resources.

[0049] In an embodiment, memory 14 may store software modules that provide functionality when executed by processor 22. The modules may include, for example, an operating system that provides operating system functionality for apparatus 10. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 10. The components of apparatus 10 may be implemented in hardware, or as any suitable combination of hardware and software.

[0050] In one embodiment, as mentioned above, apparatus 10 may be a HSS, for example. According to one embodiment, apparatus 10 may be controlled by memory 14 and processor 22 to compute a new synchronization parameter, and to provide the new synchronization parameter to at least one serving node (e.g., MME, MSC, VLR). The value of the synchronization parameter may indicate a maximum date and/or time that a subscriber is granted service without having subscriber data synchronized between the apparatus 10 and the at least one serving node. In certain embodiments, the synchronization parameter may be provided to the at least one serving node during update location, restore data, and/or standalone subscriber data management procedures.

[0051] As outlined above, according to certain embodiments, the synchronization parameter may be a HSS-Synchronization-Time-Out parameter and/or a HSS- Synchronization-Due-Date parameter. In some embodiments, the value of the synchronization parameter may be assigned per subscriber and/or per subscriber type. In addition, the synchronization parameter may be part of or stored in the subscriber data. The synchronization parameter may also be stored in permanent data of the apparatus 10.

[0052] According to one embodiment, the HSS-Synchronization-Due-Date parameter may be computed according to the following formula: HSS-Synchronization-Due-Date = current date (UTC) + HSS-Synchronization-Time-out.

[0053] Fig. 2b illustrates an example of an apparatus 20 according to another embodiment. In an embodiment, apparatus 20 may be a node, host, server, or other element in a communications network or associated with such a network. For example, in certain embodiments, apparatus 20 may be a serving node, such as a MME, MSC, or VLR. It should be noted that one of ordinary skill in the art would understand that apparatus 20 may include components or features not shown in Fig. 2b.

[0054] As illustrated in Fig. 2b, apparatus 20 includes a processor 32 for processing information and executing instructions or operations. Processor 32 may be any type of general or specific purpose processor. While a single processor 32 is shown in Fig. 2b, multiple processors may be utilized according to other embodiments. In fact, processor 32 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples.

[0055] Apparatus 20 may further include or be coupled to a memory 34 (internal or external), which may be coupled to processor 32, for storing information and instructions that may be executed by processor 32. Memory 34 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and removable memory. For example, memory 34 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, or any other type of non- transitory machine or computer readable media. The instructions stored in memory 34 may include program instructions or computer program code that, when executed by processor 32, enable the apparatus 20 to perform tasks as described herein.

[0056] In some embodiments, apparatus 20 may also include or be coupled to one or more antennas 35 for transmitting and receiving signals and/or data to and from apparatus 20. Apparatus 20 may further include a transceiver 38 configured to transmit and receive information. For instance, transceiver 38 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 35 and demodulate information received via the antenna(s) 35 for further processing by other elements of apparatus 20. In other embodiments, transceiver 38 may be capable of transmitting and receiving signals or data directly.

[0057] Processor 32 may perform functions associated with the operation of apparatus 20 including, without limitation, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 20, including processes related to management of communication resources.

[0058] In an embodiment, memory 34 stores software modules that provide functionality when executed by processor 32. The modules may include, for example, an operating system that provides operating system functionality for apparatus 20. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 20. The components of apparatus 20 may be implemented in hardware, or as any suitable combination of hardware and software.

[0059] As mentioned above, according to one embodiment, apparatus 20 may be a serving node. In this embodiment, apparatus 20 may be controlled by memory 34 and processor 32 to receive a synchronization parameter, where a value of the synchronization parameter indicates a maximum date and/or time that a subscriber is granted service without having subscriber data synchronized between the apparatus 20 and a HSS. Apparatus 20 may then be controlled by memory 34 and processor 32 to determine based on the received synchronization parameter, at predetermined synchronization points, whether subscriber data synchronization with the HSS is required, and to trigger synchronization with the HSS when it is determined that the subscriber data synchronization with the HSS is required.

[0060] As discussed above, the synchronization parameter may be a HSS- Synchronization-Time-Out parameter and/or a HSS-Synchronization-Due-Date parameter. In an embodiment, apparatus 20 may be controlled by memory 34 and processor 32 to compute a difference between a current time and a time that last update location or restore data operation was performed towards the HSS, and, when the difference is greater than a value of the HSS-Synchronization-Time-Out parameter, to determine that the subscriber data synchronization is required.

[0061] In an embodiment, apparatus 20 may also be controlled by memory 34 and processor 32 to compare a current time with a value of the HSS-Synchronization-Due- Date parameter, and, when the current time is greater than the value of the HSS- Synchronization-Due-Date parameter, to determine that the subscriber data synchronization is required.

[0062] Fig. 3a illustrates an example flow diagram of a method for subscriber data synchronization, according to an embodiment of the invention. In one example, the method of Fig. 3a may be performed by a server in a communications network, such as a HSS.

[0063] As illustrated in Fig. 3a, the method may include, at 300, computing a synchronization parameter, and, at 310, providing the synchronization parameter to at least one serving node. The value of the synchronization parameter may indicate a maximum date and/or time that a subscriber is granted service without having subscriber data synchronized between the server and the at least one serving node. The synchronization parameter may be a HSS-Synchronization-Time-Out parameter and/or a HSS-Synchronization-Due-Date parameter. The providing of the synchronization parameter may further include providing the synchronization parameter to the at least one serving node during update location, restore data, and/or standalone subscriber data management procedures.

[0064] In some embodiments, the value of the synchronization parameter may be assigned per subscriber and/or per subscriber type. In addition, the synchronization parameter may be part of or stored in the subscriber data. The synchronization parameter may also be stored in permanent data of the server.

[0065] According to one embodiment, the method may further include computing the HSS-Synchronization-Due-Date parameter according to the following formula: HSS- Synchronization-Due-Date = current date (UTC) + HSS-Synchronization-Time-out.

[0066] Fig. 3b illustrates an example flow diagram of a method for subscriber data synchronization, according to another embodiment of the invention. In one example, the method of Fig. 3b may be performed by a serving node in a communications network or serving such a network, such as a MME, MSC, VLR. [0067] As illustrated in Fig. 3b, the method may include, at 350, receiving a synchronization parameter, where a value of the synchronization parameter indicates a maximum date and/or time that a subscriber is granted service without having subscriber data synchronized between the serving node and a HSS. The method may also include, at 360, determining based on the received synchronization parameter, at predetermined synchronization points, whether subscriber data synchronization with the HSS is required. At 370, the method may include triggering synchronization with the HSS when it is determined that the subscriber data synchronization with the HSS is required. The synchronization parameter may be a HSS-Synchronization-Time-Out parameter and/or a HSS-Synchronization-Due-Date parameter.

[0068] In an embodiment, the determining of whether subscriber data synchronization is required may include computing a difference between a current time and a time that last update location or restore data operation was performed towards the home subscriber server (HSS) and, when the difference is greater than a value of the HSS- Synchronization-Time-Out parameter, determining that the subscriber data synchronization is required.

[0069] In another embodiment, the determining of whether subscriber data synchronization is required may include comparing a current time with a value of the HSS- Synchronization-Due-Date parameter and, when the current time is greater than the value of the HSS-Synchronization-Due-Date parameter, determining that the subscriber data synchronization is required.

[0070] Fig. 4a illustrates a block diagram of an apparatus 400 according to an embodiment of the invention. In this embodiment, apparatus 400 may be a network node or server, such as a HSS. As illustrated in Fig. 4a, apparatus 400 may include a computing unit or means 410 and a providing unit or means 420. For example, the computing unit or means 410 may be a processor, controller or calculator. The providing unit or means 420 may be a transceiver, transmitter, and/or antenna, for example.

[0071] The computing unit or means 410 may compute a synchronization parameter, and the providing unit or means 420 may provide the synchronization parameter to at least one serving node. The value of the synchronization parameter may indicate a maximum date and/or time that a subscriber is granted service without having subscriber data synchronized between the apparatus and the at least one serving node. The synchronization parameter may be a HSS-Synchronization-Time-Out parameter or a HSS- Synchronization-Due-Date parameter. [0072] In an embodiment, the value of the synchronization parameter is assigned per subscriber and/or per subscriber type. In another embodiment, the synchronization parameter is part of the subscriber data. According to certain embodiments, the synchronization parameter may be stored in permanent data of the apparatus.

[0073] According to one embodiment, the providing unit or means 420 may also include means for providing the synchronization parameter to the at least one serving node during update location, restore data, and/or standalone subscriber data management procedures. In some embodiments, the computing unit or means 410 may include means for computing the HSS-Synchronization-Due-Date parameter according to the following formula: HSS-Synchronization-Due-Date = current date (UTC) + HSS-Synchronization- Time-out.

[0074] Fig. 4b illustrates a block diagram of an apparatus 401 according to another embodiment of the invention. In this embodiment, apparatus 401 may be a serving node, such as a MME, MSC, and/or VLR. As illustrated in Fig. 4b, apparatus 401 may include a receiving unit or means 450, a determining unit or means 460, and a triggering unit or means 470. For example, the receiving unit or means 450 may be a transceiver or receiver, the determining unit or means 460 may be a process or calculator, and the triggering unit or means 470 may be a controller or processor.

[0075] In an embodiment, the receiving unit or means 450 may receive a synchronization parameter, where a value of the synchronization parameter indicates a maximum date and/or time that a subscriber is granted service without having subscriber data synchronized between the apparatus and a HSS. The determining unit or means 460 may determine, based on the received synchronization parameter, at predetermined synchronization points, whether subscriber data synchronization with the HSS is required. The triggering unit or means 470 may trigger synchronization with the HSS when it is determined that the subscriber data synchronization with the HSS is required. The synchronization parameter may be a HSS-Synchronization-Time-Out parameter or a HSS- Synchronization-Due-Date parameter.

[0076] According to certain embodiments, the determining unit or means 460 may include means for computing a difference between a current time and a time that last update location or restore data operation was performed towards the home subscriber server (HSS), and, when the difference is greater than a value of the HSS- Synchronization-Time-Out parameter, means for determining that the subscriber data synchronization is required. [0077] In some embodiments, the determining unit or means 460 may include means for comparing a current time with a value of the HSS-Synchronization-Due-Date parameter, and, when the current time is greater than the value of the HSS- Synchronization-Due-Date parameter, means for determining that the subscriber data synchronization is required.

[0078] In view of the above, embodiments of the invention advantageously do not require the HSS or the serving node(s) to be aware of the data inconsistency since embodiments are time- and event-based. Additionally, the subscriber data re- synchronization is performed automatically and does not require an active intervention by service personnel. Furthermore, embodiments of the invention exploit existing trigger points in the serving nodes and are therefore resource and performance friendly. Certain embodiments may also allow for the distinguishing between subscribers and/or subscriber types (e.g., VIP-subscribers versus non-VIP subscribers, normal subscribers versus machine-to-machine type subscribers, etc.).

[0079] In some embodiments, the functionality of any of the methods described herein, such as those illustrated in Figs. 3a and 3b discussed above, may be implemented by software and/or computer program code or portions of it stored in memory or other computer readable or tangible media, and executed by a processor. In some embodiments, the apparatuses described herein may be, included or be associated with at least one software application, module, unit or entity configured as arithmetic operation(s), or as a program or portions of it (including an added or updated software routine), executed by at least one operation processor.

[0080] Programs, also called program products or computer programs, including software routines, applets and macros, may be stored in any apparatus-readable data storage medium and they include program instructions to perform particular tasks. A computer program product may comprise one or more computer-executable components which, when the program is run, are configured to carry out embodiments. The one or more computer-executable components may be at least one software code or portions of it. Modifications and configurations required for implementing functionality of an embodiment may be performed as routine(s), which may be implemented as added or updated software routine(s). Software routine(s) may be downloaded into the apparatus.

[0081] Software or a computer program code or portions of it may be in a source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers. The computer readable medium or computer readable storage medium may be a non- transitory medium.

[0082] In other embodiments, the functionality of any method or apparatus described herein may be performed by hardware, for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another embodiment, the functionality may be implemented as a signal, a non-tangible means that can be carried by an electromagnetic signal downloaded from the Internet or other network.

[0083] According to an embodiment, an apparatus, such as a node, device, or a corresponding component, may be configured as a computer or a microprocessor, such as single-chip computer element, or as a chipset, including at least a memory for providing storage capacity used for arithmetic operation and an operation processor for executing the arithmetic operation.

[0084] One having ordinary skill in the art will readily understand that the invention as discussed above may be practiced with steps in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although the invention has been described based upon these preferred embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of the invention. In order to determine the metes and bounds of the invention, therefore, reference should be made to the appended claims.

Claims

WE CLAIM:

1 . A method, comprising: computing, by a server in a communications network, a synchronization parameter; and providing the synchronization parameter to at least one serving node, wherein a value of the synchronization parameter indicates a maximum date and/or time that a subscriber is granted service without having subscriber data synchronized between the server and the at least one serving node.

2. The method according to claim 1 , wherein the server comprises a home subscriber server (HSS).

3. The method according to claims 1 or 2, wherein the synchronization parameter comprises a HSS-Synchronization-Time-Out parameter or a HSS-Synchronization-Due-

Date parameter.

4. The method according to any one of claims 1 -3, wherein the value of the synchronization parameter is assigned per subscriber and/or per subscriber type.

5. The method according to any one of claims 1 -4, wherein the synchronization parameter is part of the subscriber data.

6. The method according to any one of claims 1 -5, wherein the synchronization parameter is stored in permanent data of the server.

7. The method according to any one of claims 1 -6, wherein the providing further comprises providing the synchronization parameter to the at least one serving node during update location, restore data, and/or standalone subscriber data management procedures.

8. The method according to claim 3, further comprising computing the HSS- Synchronization-Due-Date parameter according to the following formula:

HSS-Synchronization-Due-Date = current date (UTC) + HSS-Synchronization-Time-out.

9. An apparatus, comprising: at least one processor; and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus at least to compute a synchronization parameter; and provide the synchronization parameter to at least one serving node, wherein a value of the synchronization parameter indicates a maximum date and/or time that a subscriber is granted service without having subscriber data synchronized between the server and the at least one serving node.

10. An apparatus, comprising: computing means for computing a synchronization parameter; and providing means for providing the synchronization parameter to at least one serving node, wherein a value of the synchronization parameter indicates a maximum date and/or time that a subscriber is granted service without having subscriber data synchronized between the apparatus and the at least one serving node.

1 1 . The apparatus according to claim 10, wherein the apparatus comprises a home subscriber server (HSS).

12. The apparatus according to claims 1 0 or 1 1 , wherein the synchronization parameter comprises a HSS-Synchronization-Time-Out parameter or a HSS-Synchronization-Due- Date parameter.

13. The apparatus according to any one of claims 1 0-1 2, wherein the value of the synchronization parameter is assigned per subscriber and/or per subscriber type.

14. The apparatus according to any one of claims 1 0-13, wherein the synchronization parameter is part of the subscriber data.

15. The apparatus according to any one of claims 1 0-14, wherein the synchronization parameter is stored in permanent data of the apparatus.

16. The apparatus according to any one of claims 10-15, wherein the providing means further comprises means for providing the synchronization parameter to the at least one serving node during update location, restore data, and/or standalone subscriber data management procedures.

17. The apparatus according to claim 12, further comprising computing the HSS- Synchronization-Due-Date parameter according to the following formula: HSS-Synchronization-Due-Date = current date (UTC) + HSS-Synchronization-Time-out.

18. A method, comprising: receiving, by a serving node, a synchronization parameter, wherein a value of the synchronization parameter indicates a maximum date and/or time that a subscriber is granted service without having subscriber data synchronized between the serving node and a home subscriber server (HSS); determining based on the received synchronization parameter, at predetermined synchronization points, whether subscriber data synchronization with the home subscriber server (HSS) is required; and triggering synchronization with the home subscriber server (HSS) when it is determined that the subscriber data synchronization with the home subscriber server (HSS) is required.

19. The method according to claim 18, wherein the synchronization parameter comprises a HSS-Synchronization-Time-Out parameter or a HSS-Synchronization-Due-Date parameter.

20. The method according to claims 18 or 19, wherein the determining comprises: computing a difference between a current time and a time that last update location or restore data operation was performed towards the home subscriber server (HSS); and when the difference is greater than a value of the HSS-Synchronization-Time-Out parameter, determining that the subscriber data synchronization is required.

21 . The method according to claims 18 or 19, wherein the determining comprises: comparing a current time with a value of the HSS-Synchronization-Due-Date parameter; and when the current time is greater than the value of the HSS-Synchronization-Due- Date parameter, determining that the subscriber data synchronization is required.

22. An apparatus, comprising: at least one processor; and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus at least to receive a synchronization parameter, wherein a value of the synchronization parameter indicates a maximum date and/or time that a subscriber is granted service without having subscriber data synchronized between the apparatus and a home subscriber server (HSS) ; determine based on the received synchronization parameter, at predetermined synchronization points, whether subscriber data synchronization with the home subscriber server (HSS) is required; and trigger synchronization with the home subscriber server (HSS) when it is determined that the subscriber data synchronization with the home subscriber server (HSS) is required.

23. An apparatus, comprising: receiving means for receiving a synchronization parameter, wherein a value of the synchronization parameter indicates a maximum date and/or time that a subscriber is granted service without having subscriber data synchronized between the apparatus and a home subscriber server (HSS); determining means for determining based on the received synchronization parameter, at predetermined synchronization points, whether subscriber data synchronization with the home subscriber server (HSS) is required; and triggering means for triggering synchronization with the home subscriber server (HSS) when it is determined that the subscriber data synchronization with the home subscriber server (HSS) is required.

24. The apparatus according to claim 23, wherein the synchronization parameter comprises a HSS-Synchronization-Time-Out parameter or a HSS-Synchronization-Due- Date parameter.

25. The apparatus according to claims 23 or 24, wherein the determining means comprises: computing means for computing a difference between a current time and a time that last update location or restore data operation was performed towards the home subscriber server (HSS) ; and when the difference is greater than a value of the HSS-Synchronization-Time-Out parameter, determining means for determining that the subscriber data synchronization is required.

26. The apparatus according to claims 23 or 24, wherein the determining means comprises: comparing means for comparing a current time with a value of the HSS- Synchronization-Due-Date parameter; and when the current time is greater than the value of the HSS-Synchronization-Due- Date parameter, determining means for determining that the subscriber data synchronization is required.

27. A computer program, embodied on a computer readable medium, the computer program configured to control a processor to perform a method according to any one of claims 1 -8 or 18-21 .