WO2018002438A1

WO2018002438A1 - METHOD AND APPARATUS FOR FACILITATING SWx ENHANCED PPR BEHAVIOR

Info

Publication number: WO2018002438A1
Application number: PCT/FI2017/050485
Authority: WO
Inventors: Mkrishna MURTHY; Harish M
Original assignee: Nokia Technologies Oy
Priority date: 2016-06-29
Filing date: 2017-06-29
Publication date: 2018-01-04

Abstract

Various methods are provided for updating ACCESS POINT NAME subscription configuration information by facilitating enhanced behavior of Push-Profile-Requests. One example method may comprise receiving, at a network element such as an AUTHENTICATION, AUTHORIZATION AND ACCOUNTING server, an indication of modified user data, via a request invoked by a second network element such as an HOME SUBSCRIBER SERVER, utilizing at least one of a first or second newly defined Attribute-Value Pair and updating the user data in accordance with the modified user data. That is, a HOME SUBSCRIBER SERVER may be configured to invoke diameter request SWx-PUSH-PROFILE-REQUEST to communicate to an AUTHENTICATION, AUTHORIZATION AND ACCOUNTING server regarding modification of user data, the SWx-PUSH-PROFILE-REQUEST being enhanced to, for example, combine the behavior of S6a IDR and DSR in Push-Profile-Request itself by defining two new Attribute-Value Pairs.

Description

METHOD AND APPARATUS FOR

FACILITATING SWx ENHANCED PPR BEHAVIOR

TECHNOLOGICAL FIELD

[0001] Embodiments of the present invention relate generally to communications technologies including Core Network and Services technologies, and in particular to methods, apparatuses, and computer program products for facilitating enhanced behavior of Push-Profile -Requests and updating Access Point Name subscription configuration information.

BACKGROUND

[0002] According to the requirements described in, for example, 3GPP 29.273, known systems provide that a Home Subscriber Server (HSS) may invoke diameter request SWx-Push-Profile- Request (PPR) to communicate to an Authentication, Authorization and Accounting (AAA) server regarding the modification of user data, such as Access Point Name (APN) configuration information. In this regard, areas for improving known and existing systems have been identified. Through applied effort, ingenuity, and innovation, solutions to improve such systems have been realized and are described in connection with embodiments of the present invention.

BRIEF SUMMARY

[0003] Embodiments of the present invention relate generally to communications technologies including communications technologies including Core Network (Packet, Circuit) and Services (IMS,..) technologies. In particular, embodiments of the present invention provide methods, apparatuses and computer program products according to an example embodiment of the present invention for facilitating enhanced behavior of Push -Pro file -Requests through the defining and use of a plurality of Attribute -Value Pairs (AVP)s thereby enabling updating APN subscription configuration information.

[0004] In exemplary embodiment, certain methods, apparatuses and computer program products provided for facilitating enhanced behavior of Push-Profile -Requests through the defining and use of a plurality of AVPs may be utilized in conjunction with or in addition to 3GPP 29.273, the entirety of which is incorporated by reference.

[0005] In an exemplary embodiment, a HSS may be configured to invoke diameter request SWx-PPR (Push-Profile-Request) to communicate to an AAA server regarding modification of user data, the SWx-PPR (Push-Profile-Request) being enhanced to, for example, combine the behavior of S6a IDR and DSR in PPR itself by defining two new AVPs.

[0006] In an exemplary embodiment, a method for updating Access Point Name (APN) subscription configuration information may be provided, the method comprising enabling registration of at least one of two new AVPs, a first AVP configured to comprise an indication to add or modify user data and a second AVP configured to comprise an indication regarding the deletion of user data or an indication to delete user data. Additionally or alternatively, the method may comprise receiving and/or providing an indication, the indication comprising only a deleted APN, and modifying user data, the user data comprised of each of a plurality of attached APNs, where modifying the user data comprises deleting, from the set of attached APNs, the deleted APN.

[0007] A method may be provided for updating user data, the method comprisingreceiving, at a network element an indication of a modified user data, via a request invoked by a second network element utilizing at least one of a first defined AVP and a second defined AVP, and updating the user data in accordance with the modified user data. In some embodiments, an element of the request is configured to support first defined AVP, the first defined AVP configured to comprise an indication to add or modify user data, the method further comprising adding or modifying the user data in accordance with the data indicated within the first defined AVP. In some embodiments, the second defined AVP is configured to comprise an indication regarding the deletion of user data or an indication to delete user data, the method further comprising in an instance in which the request is a PPR request and is invoked utilizing the second defined AVP, detecting that the PPR request is invoked utilizing the second defined AVP, and deleting the user data in accordance with the user data the data indicated within the second defined AVP.

[0008] In some embodiments, the network element is an AAA server and the PPR request is received from a HSS server via a SWx interface. In some embodiments, the network element is a mobile management entity (MME) server and/or a Serving GPRS Support Node (SGSN) and the request is an IDR message received from a HSS server via an S6 interface.

[0009] In some embodiments, the first defined AVP is invoked by HSS only when a subscriber is attached and there is change in a subscriber profile at the HSS. In some embodiments, the second defined AVP is invoked only when a subscriber is attached and a portion of the user data is deleted at the HSS. In some embodiments, the user data is data indicative of one or more attached APNs. [0010] In some embodiments, an apparatus enabling updating user data may be provided, the apparatus comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the processor, cause the apparatus to receive, at a network element an indication of a modified user data, via a request invoked by a second network element utilizing at least one of a first defined AVP and a second defined AVP, and update the user data in accordance with the modified user data.

[0011] In some embodiments, an element of the request is configured to support first defined AVP, the first defined AVP configured to comprise an indication to add or modify user data, the apparatus further comprises computer program code configured to, with the processor, cause the apparatus to add or modify the user data in accordance with the data indicated within the first defined AVP.

[0012] In some embodiments, the second defined AVP is configured to comprise an indication regarding the deletion of user data or an indication to delete user data, wherein the apparatus further comprises computer program code configured to, with the processor, cause the apparatus to in an instance in which the request is a PPR request and is invoked utilizing the second defined AVP, detecting that the PPR request is invoked utilizing the second defined AVP, and deleting the user data in accordance with the user data the data indicated within the second defined AVP.

[0013] In some embodiments, the network element is an AAA server and the PPR request is received from a HSS server via a SWx interface. In some embodiments, the network element is an MME server and/or a SGSN and the request is an IDR message received from a HSS server via an S6 interface. In some embodiments, the first defined AVP is invoked by HSS only when a subscriber is attached and there is change in a subscriber profile at the HSS. In some embodiments, the second defined AVP is invoked only when a subscriber is attached and a portion of the user data is deleted at the HSS In some embodiments, the user data is data indicative of one or more attached APNs.

[0014] In some embodiments, a computer program product may be provided for updating user data comprising at least one non-transitory computer-readable storage medium having computer- executable program code instructions stored therein, the computer-executable program code instructions comprising program code instructions for receiving, at a network element an indication of a modified user data, via a request invoked by a second network element utilizing at least one of a first defined AVP and a second defined AVP, and updating the user data in accordance with the modified user data.

[0015] In some embodiments, an element of the request is configured to support first defined AVP, the first defined AVP configured to comprise an indication to add or modify user data, the method further comprising adding or modifying the user data in accordance with the data indicated within the first defined AVP. In some embodiments, the second defined AVP is configured to comprise an indication regarding the deletion of user data or an indication to delete user data, the method further comprising in an instance in which the request is a PPR request and is invoked utilizing the second defined AVP, detecting that the PPR request is invoked utilizing the second defined AVP, and deleting the user data in accordance with the user data the data indicated within the second defined AVP.

[0016] In some embodiments, the network element is an AAA server and the PPR request is received from a HSS server via a SWx interface. In some embodiments, the network element is an MME server and/or a SGSN and the request is an IDR message received from a HSS server via an S6 interface. In some embodiments, the first defined AVP is invoked by HSS only when a subscriber is attached and there is change in a subscriber profile at the HSS In some embodiments, the second defined AVP is invoked only when a subscriber is attached and a portion of the user data is deleted at the HSS. In some embodiments, the user data is data indicative of one or more attached APNs.

[0017] In some embodiments, a system maybe provided, the system comprising an HSS, AAA server, and an SWx interface enabling communication between the HSS and 3 GPP server, the SWx interface configured to provide a mechanism enabling changes, for example, to APN subscription configuration information, to be provided via a diameter message format of SWx- PPR enhanced via at least one of two newly defined AVPs.

BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Having thus described embodiments of the invention in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

[0019] Figure 1 is block diagram of a system that may be specifically configured in accordance with an example embodiment of the present invention; [0020] Figure 2 is a block diagram of an apparatus that may be specifically configured in accordance with an example embodiment of the present invention;

[0021] Figure 3 is a block diagram of a system that may be specifically configured in accordance with an example embodiment of the present invention; and

[0022] Figures 4 A, 4B, and 5 are flowcharts showing exemplary methods of operating an example apparatus in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION

[0023] Some example embodiments will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments are shown. Indeed, the example embodiments may take many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like reference numerals refer to like elements throughout. The terms "data," "content," "information," and similar terms may be used interchangeably, according to some example embodiments, to refer to data capable of being transmitted, received, operated on, and/or stored. Moreover, the term "exemplary", as may be used herein, is not provided to convey any qualitative assessment, but instead merely to convey an illustration of an example. Thus, use of any such terms should not be taken to limit the spirit and scope of embodiments of the present invention.

[0024] As used herein, the term "circuitry" refers to all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry); (b) to combinations of circuits and software (and/or firmware), such as (as applicable): (i) to a combination of processor(s) or (ii) to portions of processor(s)/software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions); and (c) to circuits, such as a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation, even if the software or firmware is not physically present.

[0025] This definition of "circuitry" applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term 'circuitry' would also cover an implementation of merely a processor (or multiple processors) or portion of a processor and its (or their) accompanying software and/or firmware. The term 'circuitry' would also cover, for example and if applicable to the particular claim element, a baseband integrated circuit or application specific integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, or other network device.

System Architecture

[0026] Referring now to Figure 1 , which illustrates an example system that supports communications between a plurality of stations 10 and one or more access points 12 (e.g., a high density system scenario where a plurality of access points may be deployed to a geographical area and may be operating on the same frequency channel), each access point may communicate with one or more stations and, in one embodiment, may communicate with a large number of stations, such as 6,000 or more stations. The access points may, in turn, communicate with a network 14. While the access points may communicate via an Long Term Evolution (LTE) or LTE-Advanced (LTE-A) network, other networks may support communications between the access points including those configured in accordance with wideband code division multiple access (W- CDMA), CDMA2000, global system for mobile communications (GSM), general packet radio service (GPRS), the IEEE 802.1 1 standard including, for example, the IEEE 802.11 ah or 802.11 ac standard or other newer amendments of the standard, wireless local access network (WLAN), Worldwide Interoperability for Microwave Access (WiMAX) protocols, universal mobile telecommunications systems (UMTS) terrestrial radio access network (UTRAN) and/or the like.

[0027] The access points 12 and the stations 10 may communicate via wireline communications, but most commonly communicate via wireless communications. For example, the access points and the stations may communicate in a sub 1 GHz band as defined by IEEE 802.11 ah standard or in a 5GHz band, which may be defined by, for example, IEEE 802.1 lac standard. The access point may be embodied by any of a variety of network entities, such as an access point, a base station, a Node B, an evolved Node B (eNB), a radio network controller (RNC), a mobile device / a station (e.g., mobile telephones, smart phones, portable digital assistants (PDAs), pagers, laptop computers, tablet computers or any of numerous other hand held or portable communication devices, computation devices, content generation devices, content consumption devices, or combinations thereof), or the like. The stations may also be embodied by a variety of devices, such as sensors, meters or the like. The sensors and meters may be deployed in a variety of different applications including in utility applications to serve as a gas meter, a water meter, a power meter or the like, in environmental and/or agricultural monitoring applications, in industrial process automation applications, in healthcare and fitness applications, in building automation and control applications and/or in temperature sensing applications. Stations that are embodied by sensors or meters may be utilized in some embodiments to backhaul sensor and meter data. Alternatively, the stations may be embodied by mobile terminals or user equipment(s) (UE), such as mobile communication devices, e.g., mobile telephones, smart phones, portable digital assistants (PDAs), pagers, laptop computers, tablet computers or any of numerous other hand held or portable communication devices, computation devices, content generation devices, content consumption devices, or combinations thereof. In an embodiment in which the station is embodied by a mobile terminal, the communication between an access point and the station may serve to extend the range of Wi-Fi or another wireless local area network (WLAN), such as by extending the range of a hotspot, and to offload traffic that otherwise would be carried by a cellular or other network.

[0028] The access point 12 and/or the station 10 may be embodied as or otherwise include an apparatus 20 that is specifically configured to perform the functions of the respective device, as generically represented by the block diagram of Figure 2. While the apparatus may be employed, for example, by an access point or a station, it should be noted that the components, devices or elements described below may not be mandatory and thus some may be omitted in certain embodiments. Additionally, some embodiments may include further or different components, devices or elements beyond those shown and described herein.

Apparatus Architecture

[0029] Regardless of the type of device that embodies the station 10, the station 10 may include or be associated with an apparatus 20 as shown in Figure 2. In this regard, the apparatus may include or otherwise be in communication with a processor 22, a memory device 24, a communication interface 26 and a user interface 28. As such, in some embodiments, although devices or elements are shown as being in communication with each other, hereinafter such devices or elements should be considered to be capable of being embodied within the same device or element and thus, devices or elements shown in communication should be understood to alternatively be portions of the same device or element. [0030] In some embodiments, the processor 22 (and/or co-processors or any other processing circuitry assisting or otherwise associated with the processor) may be in communication with the memory device 24 via a bus for passing information among components of the apparatus. The memory device may include, for example, one or more volatile and/or non-volatile memories. In other words, for example, the memory device maybe an electronic storage device (e.g., a computer readable storage medium) comprising gates configured to store data (e.g., bits) that may be retrievable by a machine (e.g., a computing device like the processor). The memory device may be configured to store information, data, content, applications, instructions, or the like for enabling the apparatus 20 to carry out various functions in accordance with an example embodiment of the present invention. For example, the memory device could be configured to buffer input data for processing by the processor. Additionally or alternatively, the memory device could be configured to store instructions for execution by the processor.

[0031] As noted above, the apparatus 20 may be embodied by a computing device 10 configured to employ an example embodiment of the present invention. However, in some embodiments, the apparatus may be embodied as a chip or chip set. In other words, the apparatus may comprise one or more physical packages (e.g., chips) including materials, components and/or wires on a structural assembly (e.g., a baseboard). The structural assembly may provide physical strength, conservation of size, and/or limitation of electrical interaction for component circuitry included thereon. The apparatus may therefore, in some cases, be configured to implement an embodiment of the present invention on a single chip or as a single "system on a chip." As such, in some cases, a chip or chipset may constitute means for performing one or more operations for providing the functionalities described herein.

[0032] The processor 22 may be embodied in a number of different ways. For example, the processor may be embodied as one or more of various hardware processing means such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing element with or without an accompanying DSP, or various other processing circuitry including integrated circuits such as, for example, an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), a microcontroller unit (MCU), a hardware accelerator, a special- purpose computer chip, or the like. As such, in some embodiments, the processor may include one or more processing cores configured to perform independently. A multi-core processor may enable multiprocessing within a single physical package. Additionally or alternatively, the processor may include one or more processors configured in tandem via the bus to enable independent execution of instructions, pipelining and/or multithreading.

[0033] In an example embodiment, the processor 22 may be configured to execute instructions stored in the memory device 24 or otherwise accessible to the processor. Alternatively or additionally, the processor may be configured to execute hard coded functionality. As such, whether configured by hardware or software methods, or by a combination thereof, the processor may represent an entity (e.g., physically embodied in circuitry) capable of performing operations according to an embodiment of the present invention while configured accordingly. Thus, for example, when the processor is embodied as an ASIC, FPGA or the like, the processor may be specifically configured hardware for conducting the operations described herein. Alternatively, as another example, when the processor is embodied as an executor of software instructions, the instructions may specifically configure the processor to perform the algorithms and/or operations described herein when the instructions are executed. However, in some cases, the processor may be a processor of a specific device (e.g., a head mounted display) configured to employ an embodiment of the present invention by further configuration of the processor by instructions for performing the algorithms and/or operations described herein. The processor may include, among other things, a clock, an arithmetic logic unit (ALU) and logic gates configured to support operation of the processor. In one embodiment, the processor may also include user interface circuitry configured to control at least some functions of one or more elements of the user interface 28.

[0034] Meanwhile, the communication interface 26 may be any means such as a device or circuitry embodied in either hardware or a combination of hardware and software that is configured to receive and/or transmit data between the computing device 10 and a server 12. In this regard, the communication interface 26 may include, for example, an antenna (or multiple antennas) and supporting hardware and/or software for enabling communications wirelessly. Additionally or alternatively, the communication interface may include the circuitry for interacting with the antenna(s) to cause transmission of signals via the antenna(s) or to handle receipt of signals received via the antenna(s). For example, the communications interface may be configured to communicate wirelessly with the head mounted displays 10, such as via Wi-Fi, Bluetooth or other wireless communications techniques. In some instances, the communication interface may alternatively or also support wired communication. As such, for example, the communication interface may include a communication modem and/or other hardware/software for supporting communication via cable, digital subscriber line (DSL), universal serial bus (USB) or other mechanisms. For example, the communication interface may be configured to communicate via wired communication with other components of the computing device.

[0035] The user interface 28 may be in communication with the processor 22, such as the user interface circuitry, to receive an indication of a user input and/or to provide an audible, visual, mechanical, or other output to a user. As such, the user interface may include, for example, a keyboard, a mouse, a joystick, a display, a touch screen display, a microphone, a speaker, and/or other input/output mechanisms. In some embodiments, a display may refer to display on a screen, on a wall, on glasses (e.g., near-eye-display), in the air, etc. The user interface may also be in communication with the memory 24 and/or the communication interface 26, such as via a bus.

[0036] Detailed descriptions of networks and systems can be found, for example, in Technical Specifications published by standardization bodies such as 3rd Generation Partnership Project (3 GPP).

Overview

[0037] In an exemplary embodiment, a HSS may be configured to invoke diameter request SWx-PPR (Push-Profile-Request) to communicate to an AAA server regarding modification of user data, the SWx-PPR (Push-Profile-Request) being enhanced to, for example, combine the behavior of S6a IDR and DSR in PPR itself by defining two new AVPs.

Exemplary Architecture

[0038] As described with reference to Figure 3, an exemplary architecture is shown. For some background, according to the requirements described in 3GPP TS 23.402, 3GPP TS 32.422 and 3GPP TS 23.380, a SWx reference point shall enable, for example, an indication to 3GPP AAA Server of change of non-3GPP subscriber profile within HSS; and activation and deactivation of the subscriber and equipment trace in the PDN GW. Furthermore, a SWx reference point may also be configured for or utilized for requesting identity and location information of the access network and/or UE local time zone; and/or providing an indication to the 3GPP AAA Server that the HSS-based P-CSCF restoration procedure for WLAN, shall be executed as described in 3GPP TS 23.380. [0039] As such, Figure 3 shows HSS 305 and AAA server 310 in communication via SWx interface 315. In accordance with the architecture of Figure 3 and the functionalities described above, HSS 305 may invoke a SWx-PPR diameter message towards AAA 310 to update a change in a user profile or a change in user data (e.g., subscription configuration information such as a set of APNs). This invocation may be made between the 3GPP AAA Server 310 and the HSS 305 via SWx interface 315.

[0040] Invocation of the SWx-PPR message by the HSS when the subscriber profile has been modified and needs to be sent to the 3GPP AAA Server and/or in an instance in which the HSS 305 updates the 3GPP AAA Server 310, for example, with the identity of a dynamically allocated PDN GW 320 which is included in the APN-Configuration AVP in the User Profile as a result of the first PDN connection establishment associated with an APN over 3GPP access. The procedure of providing modified user data and updating the AAA server invoking the PPR-request is mapped to the Diameter command codes PPR and Push-Profile -Answer (PPA) specified in the 3GPP TS 29.229. Diameter is an authentication, authorization, and accounting protocol for computer networks. A Diameter Application is not a software application but is a protocol based on the Diameter base protocol defined in RFC 6733. Each application is defined by an application identifier and can add new command codes and/or new mandatory AVPs. Adding a new optional AVP does not require a new application.

[0041] Accordingly, the HSS 305 shall make use of this procedure to update the relevant user profile in the 3GPP AAA server (e.g. change of subscription data or change of the identity of a dynamically allocated PDN GW associated with an APN), or activate /deactivate subscriber and equipment trace in the PDN GW. An Access Point Name (APN) is the name of a gateway, for example, a mobile network (e.g., 3G, 4G, etc.) and a second computer network (e.g., the Internet).

[0042] Figure 3 further shows other communication network architecture in accordance with some embodiments of the present invention. That is, Figure 3 includes an access terminal/user equipment (UE) 10 and an access point (AP) 12, the same or similar to those shown in Figure 1 , and an ePDG 325 configured for non-3G access, for example, to PDN services such as the internet. Conventionally through the SWx interface, 3GPP AAA retrieves security and authorization information stored in HSS. The HSS keeps track of the AAA Identity currently serving a user in the Non-3GPP access network. SWx is also used to update the HSS with PDN-GW Identity information to facilitate handover (HO) between 3GPP and Non-3GPP accesses. [0043] Conventionally, the 3GPP AAA Server shall overwrite, for the subscriber identity indicated in the request, current information with the information received from the HSS.

[0044] In short, in accordance with 3 GPP TS 23.402 chapter 12 "Interactions between HSS and AAA Server", a 3GPP AAA can be used in Non-3GPP access scenarios to authenticate and authorize a UE connecting from a Non-3GPP access network (e.g. CDMA2000) to an EPC network via the SWx interface towards HSS. In this respect, 3 GPP TS 29.273 chapter 8 "SWx description" describes the SWx interface.

Facilitating the Process

[0045] In an exemplary embodiment, in an instance in which a subscriber has 50 APN attached and subsequently, the subscription is changed at HSS to delete an APN, current standards require that SWx-PPR is initiated towards AAA for the subscriber indicating remaining all 49 APNs. However, in embodiments of the present invention, in an instance in which a subscriber has 50 APN attached and subsequently, the subscription is changed at HSS to delete an APN, through the defining and use of new AVPs, HSS may be configured to send a PPR message to AAA with only the one APN (or, in some embodiments, the plurality of APNs) that is deleted.

[0046] In some embodiments of the present invention, the above-described procedure may be extended over the S6a interface as well, for example, between MME/SGSN and HSS where currently two Diameter messages are defined by 3GPP (i.e. S6-DSR and S6-IDR) to indicate deletion and modification/addition of subscription data respectively.

[0047] In an exemplary embodiment, a HSS may be configured to invoke diameter request SWx-PPR (Push-Profile-Request) to communicate to an AAA server regarding modification of user data, the SWx-PPR (Push-Profile-Request) being enhanced to, for example, combine the behavior of S6a IDR and DSR in PPR itself by defining two new AVPs.

[0048] Diameter AVPs are the basic unit inside the Diameter message, and are configured carry data such, as, for example, authentication data, security data , data pertaining to application, or the like. Generally speaking, there must be at least one AVP inside a diameter message. A grouped AVP generally behaves like a single AVPs except that the data field of a grouped AVP comprises one or move AVPs rather than raw data. That is, within a group AVP, AVPS act as data. [0049] The advantage in introducing the AVPs enables, in some embodiments, a network elements (e.g., HSS) to, for example, instead of sending all remaining APNs from the subscription profile in Non-3GPP-User-Data even when a single APN deleted, to send only that APN that is deleted in Deleted-Non-3GPP-User-Data. In some embodiments, even though the Deleted-Non- 3GPP-User-Data AVP definition provided herein is the same or similar to the Non-3GPP-User- Data, Deleted-Non-3GPP-User-Data may be defined to have subset of AVPs which is present in Non-3GPP-User-Data, for example, since, not all AVPs in Non-3GPP-User-Data could be valid in new Deleted-Non-3GPP-User-Data.

[0050] Furthermore, embodiments of the present invention may be configured to adopt the same or similar behavior over an S6 interface as well, thereby, enabling/allowing/requiring only an IDR message of accomplishing DSR functionalities.

[0051] The current 3GPP defined SWx-PPR message is as shown below. SWx-PPR message depicts the diameter message format of SWx-PPR as shown in 3GPP standard 29.273.

< Push-Profile-Request > : := < Diameter Header: 305, REQ, 16777265 >

< Session-Id >

{ Vendor-Speciflc-Application-Id }

{ Auth-Session-State }

{ Origin-Host }

{ Origin-Realm }

{ Destination-Host }

{ Destination-Realm }

{ User-Name }

[ Non-3GPP-User-Data ]

[ PPR-Flags ]

*[ Supported-Features ]

*[ AVP ]

[0052] According to some embodiments of the present invention, the above-identified diameter structure may be enhanced as shown below to incorporate the following behavior.

[0053] First, to add or modify user data, Non-3GPP-User-Data group AVP may be configured to support new AVP "all-APN-Configuration-included-indication" (AVP code: 1428 as described in 3gpp 29.272) to indicate AAA about the data under Non-3GPP-User-Data. In some embodiments, this behavior may be similar S6a-IDR.

Non-3GPP-User-Data ::=< AVP Header: 1500 10415 > [ Subscription-ID ]

[ Non-3GPP-IP-Access ]

[ Non-3 GPP-IP- Access- APN ]

*[ RAT-Type ]

[ Session-Timeout ]

[ MIP6 -Feature -Vector ]

[ AMBR ]

[ 3GPP-Charging-Characteristics ]

[ Context-Identifier ]

[ APN-OI-Replacement ]

*[ APN-Configuration ]

[ Trace-Info ]

[ TWAN-De fault- APN-Context-Id ]

*[ TWAN- Access-Info]

[All-APN-Configurations-Included-Indicator]

*[ AVP ]

[0054] Second, in some embodiments, the system may be configured to add or register AVP Deleted-Non-3GPP-User-Data, which may be similar to Non-3GPP-User-Data AVP, (as described in 3gpp 29.273) which may be configured to provide an indication to AAA comprising, for example, user data that has been deleted. In some embodiments, this behavior may be similar to S6a-DSR.

Deleted-Non-3GPP-User-Data ::=< AVP Header: 1500 10415 >

[ Subscription-ID ]

[ Non-3GPP-IP-Access ]

[ Non-3GPP-IP-Access-APN ]

*[ RAT-Type ]

[ Session-Timeout ]

[ MIP6 -Feature- Vector ]

[ AMBR ]

[ 3GPP-Charging-Characteristics ]

[ Context-Identifier ]

[ APN-OI-Replacement ]

*[ APN-Configuration ]

[ Trace-Info ]

[ TWAN-Default-APN-Context-Id ]

*[ TWAN- Access-Info]

*[ AVP ]

[0055] In some embodiments, for example, for backward compatibility, AAA may be configured to indicate support of the features described above (i.e. AVP Deleted-Non-3GPP-User- Data and all-APN-Configuration-included-indication) in supported-feature AVP during registration. Operation

[0056] In an example embodiment of the present invention, an apparatus or computer program product may be provided to implement or execute a method, process, or algorithm for facilitating SWx enhanced PPR behavior and/or updating Access Point Name (APN) subscription configuration information.

[0057] Figures 4A, 4B, and 5 show flowcharts of the exemplary operations performed by a method, apparatus and computer program product in accordance with an embodiment of the present invention. It will be understood that each block of the flowcharts, and combinations of blocks in the flowcharts, may be implemented by various means, such as hardware, firmware, processor, circuitry and/or other device associated with execution of software including one or more computer program instructions. For example, one or more of the procedures described above may be embodied by computer program instructions. In this regard, the computer program instructions which embody the procedures described above may be stored by a memory 26 of an apparatus employing an embodiment of the present invention and executed by a processor 24 in the apparatus. As will be appreciated, any such computer program instructions may be loaded onto a computer or other programmable apparatus (e.g., hardware) to produce a machine, such that the resulting computer or other programmable apparatus provides for implementation of the functions specified in the flowchart block(s). These computer program instructions may also be stored in a non-transitory computer-readable storage memory that may direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage memory produce an article of manufacture, the execution of which implements the function specified in the flowchart block(s). The computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart block(s). As such, the operations of Figures 4A, 4B, and 5 when executed, convert a computer or processing circuitry into a particular machine configured to perform an example embodiment of the present invention. Accordingly, the operations of Figures 4A, 4B, and 5 define an algorithm for configuring a computer or processing to perform an example embodiment. In some cases, a general purpose computer may be provided with an instance of the processor which performs the algorithms of Figures 4A, 4B, and 5 to transform the general purpose computer into a particular machine configured to perform an example embodiment.

[0058] Accordingly, blocks of the flowchart support combinations of means for performing the specified functions and combinations of operations for performing the specified functions. It will also be understood that one or more blocks of the flowcharts, and combinations of blocks in the flowcharts, can be implemented by special purpose hardware -based computer systems which perform the specified functions, or combinations of special purpose hardware and computer instructions.

[0059] In some embodiments, certain ones of the operations herein may be modified or further amplified as described below. Moreover, in some embodiments additional optional operations may also be included as shown by the blocks having a dashed outline in Figures 4A, 4B , and 5. It should be appreciated that each of the modifications, optional additions or amplifications below may be included with the operations above either alone or in combination with any others among the features described herein.

[0060] In some example embodiments, a method, apparatus and computer program product may be configured for updating APN subscription configuration information. For example, some embodiments of the present invention may facilitate enhanced behavior of Push-Profile-Requests and updating Access Point Name subscription configuration information. Figure 4A is a flowchart showing an exemplary method of operating an example apparatus in accordance with an embodiment of the present invention.

[0061] As such, as shown in block 405 of Figure 4A, an apparatus, such as apparatus 20 embodied by the computing device 10, may be configured to receive, at a network element an indication of a modified user data, via a request invoked by a second network element utilizing at least one of a first defined AVP and a second defined AVP. The apparatus embodied by computing device 10 may therefore include means, such as the processor 22, the communication interface 26 or the like, for receiving, at a network element an indication of a modified user data, via a request invoked by a second network element utilizing at least one of a first defined AVP and a second defined AVP. In some embodiments, the first network element is an AAA server. In some embodiments, the second network element is a HSS. [0062] As shown in block 410 of Figure 4A, an apparatus, such as apparatus 20 embodied by the computing device 10, may be configured to update the user data in accordance with the modified user data. The apparatus embodied by computing device 10 may therefore include means, such as the processor 22, the communication interface 26 or the like, for updating the user data in accordance with the modified user data.

[0063] In an exemplary embodiment of the present invention, a method, apparatus and computer program product may be configured for updating APN subscription configuration information utilizing at least one of two newly defined AVPs. In some embodiments, an element of the request may be configured to support the first defined AVP, the first defined AVP configured to comprise an indication to add or modify user data. As such, as shown in block 415 of Figure 4B, an apparatus, such as apparatus 20 embodied by the computing device 10, may be configured to add or modify the user data in accordance with the data indicated within the first defined AVP. The apparatus embodied by computing device 10 may therefore include means, such as the processor 22, the communication interface 26 or the like, for adding or modifying the user data in accordance with the data indicated within the first defined AVP.

[0064] Additionally or alternatively, in some embodiments of the present invention, the second defined AVP may be configured to comprise an indication regarding the deletion of user data or an indication to delete user data, and in an instance in which the request is a PPR request and is invoked utilizing the second defined AVP. As such, as shown in block 420 of Figure 4B, an apparatus, such as apparatus 20 embodied by the computing device 10, maybe configured to detect that the PPR request is invoked utilizing the second defined AVP and delete the user data in accordance with the user data the data indicated within the second defined AVP. The apparatus embodied by computing device 10 may therefore include means, such as the processor 22, the communication interface 26 or the like, for detecting that the PPR request is invoked utilizing the second defined AVP and deleting the user data in accordance with the user data the data indicated within the second defined AVP.

[0065] In some example embodiments, a method, apparatus and computer program product may be configured for updating APN subscription configuration information, for example, in an instance in which a subscriber has a plurality of APN attached and subsequently, the subscription is changed at HSS to delete an APN. That is, in some embodiments of the present invention, in an instance in which a subscriber has 50 APN attached and subsequently, the subscription is changed at HSS to delete an APN, through the defining and use of new AVPs, and HSS may be configured to send a PPR message to AAA with only the one APN (or, in some embodiments, the plurality of APNs) that is deleted. For example, some embodiments of the present invention may facilitate enhanced behavior of Push-Profile-Requests and updating Access Point Name subscription configuration information by providing an indication of only those APNs that are deleted. Figure 4A is a flowchart showing an exemplary method of operating an example apparatus in accordance with an embodiment of the present invention.

[0066] As shown in block 505 of Figure 5, an apparatus, such as apparatus 20 embodied by the computing device 10, may be configured to receive, at a network element, an enhanced PPR command, the enhanced PPR command comprising an indication of a deleted APN. The apparatus embodied by computing device 10 may therefore include means, such as the processor 22, the communication interface 26 or the like, for receiving, at a network element, an enhanced PPR command, the enhanced PPR command comprising an indication of a deleted APN.

[0067] As shown in block 510 of Figure 5, an apparatus, such as apparatus 20 embodied by the computing device 10, may be configured to modifying subscription configuration information, the subscription configuration information including a plurality of attached APNs, the modification comprising the updating of the plurality of attached APNs by removing or deleting the deleted APN. The apparatus embodied by computing device 10 may therefore include means, such as the processor 22, the communication interface 26 or the like, for modifying subscription configuration information, the subscription configuration information including a plurality of attached APNs, the modification comprising the updating of the plurality of attached APNs by removing or deleting the deleted APN.

[0068] Many modifications and other embodiments of the inventions set forth herein will come to mind to one skilled in the art to which these inventions pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the inventions are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Moreover, although the foregoing descriptions and the associated drawings describe example embodiments in the context of certain example combinations of elements and/or functions, it should be appreciated that different combinations of elements and/or functions may be provided by alternative embodiments without departing from the scope of the appended claims. In this regard, for example, different combinations of elements and/or functions than those explicitly described above are also contemplated as may be set forth in some of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

We claim:

1. A method for updating user data, the method comprising:

receiving, at a network element an indication of a modified user data, via a request invoked by a second network element utilizing at least one of a first defined Attribute -Value Pair and a second defined Attribute -Value Pair; and

updating the user data in accordance with the modified user data.

2. The method according to Claim 1, wherein an element of the request is configured to support first defined Attribute -Value Pair, the first defined Attribute -Value Pair configured to comprise an indication to add or modify user data, the method further comprising:

adding or modifying the user data in accordance with the data indicated within the first defined Attribute -Value Pair.

3. The method according to Claim 1 , wherein the second defined Attribute -Value Pair is configured to comprise an indication regarding the deletion of user data or an indication to delete user data, the method further comprising:

in an instance in which the request is a Push-Pro file-Request request and is invoked utilizing the second defined Attribute -Value Pair, detecting that the Push-Profile -Request request is invoked utilizing the second defined Attribute -Value Pair; and

deleting the user data in accordance with the user data the data indicated within the second defined Attribute -Value Pair.

4. The method according to any of Claims 1 to 3, wherein the network element is an Authentication, Authorization and Accounting server and the Push-Pro file-Request request is received from a Home Subscriber Server via a SWx interface.

5. The method according to any of Claims 1 to 3, wherein the network element is a Mobile Management Entity server and/or a Serving GPRS Support Node and the request is an IDR message received from a Home Subscriber Server via an S6 interface.

6. The method according to any of Claims 1 to 4, wherein, the first defined Attribute- Value Pair is invoked by Home Subscriber Server only when a subscriber is attached and there is change in a subscriber profile at the Home Subscriber Server.

7. The method according to any of Claims 1 to 4, wherein, the second defined Attribute- Value Pair is invoked only when a subscriber is attached and a portion of the user data is deleted at the Home Subscriber Server.

8. The method according to any of Claims 1 to 5, wherein the user data is data indicative of one or more attached Access Point Names.

9. An apparatus enabling updating user data, the apparatus comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the processor, cause the apparatus to:

receive, at a network element an indication of a modified user data, via a request invoked by a second network element utilizing at least one of a first defined Attribute -Value Pair and a second defined Attribute -Value Pair; and

update the user data in accordance with the modified user data.

10. The apparatus according to Claim 9,

wherein an element of the request is configured to support first defined Attribute- Value Pair, the first defined Attribute -Value Pair configured to comprise an indication to add or modify user data,

wherein the apparatus further comprises computer program code configured to, with the processor, cause the apparatus to:

add or modify the user data in accordance with the data indicated within the first defined Attribute -Value Pair.

11. The apparatus according to Claim 9,

wherein the second defined Attribute -Value Pair is configured to comprise an indication regarding the deletion of user data or an indication to delete user data, wherein the apparatus further comprises computer program code configured to, with the processor, cause the apparatus to:

in an instance in which the request is a Push-Profile-Request request and is invoked utilizing the second defined Attribute -Value Pair, detecting that the Push-Profile-Request request is invoked utilizing the second defined Attribute -Value Pair; and

12. The apparatus according to any of Claims 9 to 11 , wherein the network element is an Authentication, Authorization and Accounting server and the Push-Pro file-Request request is received from a Home Subscriber Server via a SWx interface.

13. The apparatus according to any of Claims 9 to 11 , wherein the network element is a Mobile Management Entity server and/or a Serving GPRS Support Node and the request is an IDR message received from a HOME SUBSCRIBER server via an S6 interface.

14. The apparatus according to any of Claims 9 to 13 , wherein the first defined Attribute- Value Pair is invoked by Home Subscriber Server only when a subscriber is attached and there is change in a subscriber profile at the Home Subscriber Server.

15. The apparatus according to any of Claims 9 to 14, wherein the second defined Attribute -Value Pair is invoked only when a subscriber is attached and a portion of the user data is deleted at the Home Subscriber Server.

16. The apparatus according to any of Claims 9 to 15, wherein the user data is data indicative of one or more attached Access Point Names.

17. A computer program product for updating user data comprising at least one non- transitory computer-readable storage medium having computer-executable program code instructions stored therein, the computer-executable program code instructions comprising program code instructions for: receiving, at a network element an indication of a modified user data, via a request invoked by a second network element utilizing at least one of a first defined Attribute -Value Pair and a second defined Attribute -Value Pair; and

updating the user data in accordance with the modified user data.

18. The computer program product according to Claim 17, wherein an element of the request is configured to support first defined Attribute -Value Pair, the first defined Attribute- Value Pair configured to comprise an indication to add or modify user data, the method further comprising:

19. The computer program product according to Claim 17, wherein the second defined Attribute -Value Pair is configured to comprise an indication regarding the deletion of user data or an indication to delete user data, the method further comprising:

20. The computer program product according to any of Claims 17 to 20, wherein the network element is an Authentication, Authorization and Accounting server and the Push- Profile-Request request is received from a Home Subscriber Server via a SWx interface.

21. The computer program product according to any of Claims 17 to 20, wherein the network element is an MOBILE MANAGEMENT ENTITY server and/or a SERVING GPRS SUPPORT NODE and the request is an IDR message received from a HOME SUBSCRIBER server via an S6 interface.

22. The computer program product according to any of Claims 17 to 21 , wherein, the first defined Attribute -Value Pair is invoked by the Home Subscriber Server only when a subscriber is attached and there is change in a subscriber profile at the Home Subscriber Server.

23. The computer program product according to any of Claims 17 to 22, wherein the second defined Attribute -Value Pair is invoked only when a subscriber is attached and a portion of the user data is deleted at the Home Subscriber Server.

24. The computer program product according to any of Claims 17 to 23, wherein the user data is data indicative of one or more attached Access Point Names.