U.S. patent application number 12/133880 was filed with the patent office on 2008-11-06 for method and apparatus for mobile based access point name (apn) selection.
This patent application is currently assigned to INTERDIGITAL TECHNOLOGY CORPORATION. Invention is credited to Kamel M. Shaheen.
Application Number | 20080273488 12/133880 |
Document ID | / |
Family ID | 31190840 |
Filed Date | 2008-11-06 |
United States Patent
Application |
20080273488 |
Kind Code |
A1 |
Shaheen; Kamel M. |
November 6, 2008 |
METHOD AND APPARATUS FOR MOBILE BASED ACCESS POINT NAME (APN)
SELECTION
Abstract
A procedure is provided wherein a serving general packet radio
service (GPRS) support node (SGSN) receives a request for an access
point name (APN) the SGSN making a determination if the requested
packet data protocol (PDP) and APN are the same as subscribed
information. In the event that the requested and subscribed PDP
type and the requested and subscribed APN are not the same, the
SGSN advises that the APN requested is not authorized and agreement
to terms and conditions and the provision of credit (or debit) card
information must be provided to obtain the requested APN.
Inventors: |
Shaheen; Kamel M.; (King of
Prussia, PA) |
Correspondence
Address: |
VOLPE AND KOENIG, P.C.;DEPT. ICC
UNITED PLAZA, SUITE 1600, 30 SOUTH 17TH STREET
PHILADELPHIA
PA
19103
US
|
Assignee: |
INTERDIGITAL TECHNOLOGY
CORPORATION
Wilmington
DE
|
Family ID: |
31190840 |
Appl. No.: |
12/133880 |
Filed: |
June 5, 2008 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
11228619 |
Sep 16, 2005 |
7386301 |
|
|
12133880 |
|
|
|
|
10321331 |
Dec 17, 2002 |
6970694 |
|
|
11228619 |
|
|
|
|
60399593 |
Jul 30, 2002 |
|
|
|
Current U.S.
Class: |
370/328 ;
455/406 |
Current CPC
Class: |
H04W 4/24 20130101; H04W
76/18 20180201; H04W 48/17 20130101; H04W 76/12 20180201; H04W
80/04 20130101 |
Class at
Publication: |
370/328 ;
455/406 |
International
Class: |
H04Q 7/00 20060101
H04Q007/00; H04M 11/00 20060101 H04M011/00 |
Claims
1. A method comprising, a mobile station (UE): a) communicating to
a serving general packet radio service (GPRS) support node (SGSN),
a packet data protocol (PDP) context request to the network
requesting a PDP type and an access point name (APN); the SGSN: b)
validating the request and mapping the APN to a gateway GPRS
support node (GGSN); the GGSN: c) responding to the SGSN; the SGSN:
d) advising the UE that it is not authorized to receive the
requested APN and that the UE must agree to terms and conditions to
access the requested APN when the PDP type is the same as the PDP
type subscribed and when the APN requested is not the same as the
APN subscribed for said UE; and the UE: e) accepting said terms and
conditions to obtain the requested APN.
2. The method of claim 1 wherein step (d) includes sending a
requirement that the UE consent to charges, and further comprising.
said UE communicating information to the network to charge costs of
obtaining said APN.
3. The method of claim 2 wherein the step of communicating
information to charge costs of obtaining said APN further comprises
communicating credit card information.
4. The method of claim 1 further comprising, said UE receiving the
requested APN.
5. The method of claim 1 further comprising, said SGSN: rejecting
the requested APN when a subscribed PDP type of the UE is not the
same as the requested PDP type.
6. The method of claim 1 further comprising, said UE communicating
a rejection of the terms and conditions.
7. The method of claim 1 further comprising, said UE requesting a
PDP address as part of said context request.
8. The method of claim 1 further comprising, the SGSN providing a
radio access bearer (RAB) setup with the UE, employing a radio
access network (RAN).
9. The method of claim 1 wherein the SGSN, responsive the UE
consenting to the terms, providing a radio access bearer (RAB)
setup with the UE.
10. The method of claim 9 wherein the SGSN provides the RAB setup
employing a radio access network (RAN).
11. A method for a serving general packet radio services (GRPS)
support node (SGSN), which processes a context request for an
access point node (APN), said SGSN comprising: a) checking
subscribed information from a user equipment (UE) when none of a
PDP type, a PDP address and an APN are present; b) rejecting the UE
request if the UE has a multiple PDP subscription.
12. The method of claim 11 further comprising, said SGSN
communicating the requested APN when the UE has a single
subscription.
13. The method of claim 12 further comprising, said SGSN
communicating an address mode and PDP type as well as the requested
APN when the UE has a single subscription.
14. The method of claim 11 further comprising, said SGSN rejecting
the context request when a subscribed PDP type is not the same as
the requested PDP type.
15. The method of claim 11 further comprising, said SGSN providing
an address mode and PDP type as well as the requested APN when the
requested PDP type is the same as a subscribed type.
16. Apparatus configured as a serving general packet radio service
(GRPS) support node (SGSN), comprising: a receiver for receiving a
context request requesting a packet data protocol (PDP) type, a PDP
address, and an access point name (APN); a comparison device for
determining if at least the PDP address requested compares with
subscribed data, and a device for granting the request when a
comparison is present.
17. The apparatus of claim 16 wherein the granting device is
configured to provide address mode and PDP type as well as the
APN.
18. Apparatus configured as a serving general packet radio service
(GRPS) support node (SGSN), comprising: a receiver for receiving a
context request requesting only a packet data protocol (PDP) type;
a comparison device for determining if at least the PDP type
requested compares with subscribed data, and a device for granting
the request when a comparison is present.
19. The apparatus of claim 18 wherein the granting device is
configured to provide address mode and APN as well as PDP type.
20. Apparatus configured as a serving general packet radio service
(GRPS) support node (SGSN), comprising: a receiver for receiving a
context request requesting only a packet data protocol (PDP) type
and PDP address; a comparison device for determining if the PDP
type and PDP address requested compares with subscribed data, and a
device for granting the request when a comparison is present.
21. The apparatus of claim 20 wherein the granting device is
configured to provide APN as well as PDP type and PDP address.
22. Apparatus configured as a serving general packet radio service
(GRPS) support node (SGSN), comprising: a receiver for receiving a
context request requesting only an APN; a comparison device for
determining if the APN requested compares with subscribed data, and
a device for granting the request when a comparison is present.
23. The apparatus of claim 22 wherein the granting device is
configured to provide a PDP type and PDP address as well as the
requested APN.
24. The apparatus of claim 16 further comprising a device for
rejecting the context request when at least one of the requested
PDP type and the PDP address is not the same as the subscribed
criteria.
25. The apparatus of claim 18 further comprising a device for
rejecting the request when the PDP type requested does not compare
with the stored criteria.
26. The apparatus of claim 20 further comprising a device for
rejecting the request when at least one of the PDP type and PDP
address requested does not compare with the stored criteria.
27. Apparatus, comprising: a serving general packet radio service
(GPRS) support node (SGSN); at least one gateway GPRS support node
(GGSN); said SGSN configured for: receiving a context request
requesting a packet data protocol (PDP) type and an access point
name (APN) from a mobile unit (UE); examining the PDP type and APN
request; validating the request when the PDP type and APN requested
compare with a subscribed PDP type and APN and further providing a
PDP address; mapping the requested APN to said GGSN; said GGSN
configured to: provide a context response to said SGSN responsive
to said mapped context request; and said SGSN being further
configured to: communicate the context response to said UE.
28. The apparatus of claim 27 wherein said GGSN is further
configured to provide a tunnel endpoint identifier (TEIP), a PDP
type, a quality of service (QoS) and a charging ID to said SGSN as
part of said context response to said UE.
29. The communication apparatus of claim 28 wherein said SGSN
includes means for inserting a GGSN address of said GGSN and the
requested APN address as part of the PDP context, responsive to the
context response to the UE from said GGSN.
Description
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation of U.S. patent
application Ser. No. 11/228,619, filed Sep. 16, 2005, which is a
continuation of Ser. No. 10/321,331, filed Dec. 17, 2002, now U.S.
Pat. No. 6,970,694, issued Nov. 29, 2005, which claims the benefit
of U.S. Provisional Application Ser. No. 60/399,593, filed Jul. 30,
2002, which are incorporated by reference as if fully set
forth.
FIELD OF INVENTION
[0002] The present invention relates to wireless communication
systems. More particularly, the invention relates to method and
apparatus for permitting access to an access point name (APN) not
included within the subscribers list of services.
BACKGROUND
[0003] Existing standardized APN selection procedures will result
in a denial of service (reject packet data protocol (PDP) Context
activation procedures) in those cases where a mobile user has
requested access to a certain APN not included within the list to
which that user has subscribed.
SUMMARY
[0004] The present invention provides a procedure in which a user
is given an opportunity to access any APN he wishes provided that
the user is advised that he is not currently subscribed to this
particular APN and that additional charges will be billed to his
account. The user may also be requested to provide credit/debit
card (or the like) information to cover access and future traffic
charges. If the user agrees to the charges and/or provides
credit/debit card information, i.e., payment information, a serving
general packet radio service (GPRS) support node, i.e. (SGSN)
selects the requested APN and proceeds to select the appropriate
GGSN for the requested APN.
[0005] The present invention extends existing standardized APN
selection procedures enabling a user to select a domain name (APN)
of his choice, even though not among his subscription list,
providing that the user consents/agrees to the applied charges for
access and contents.
[0006] The technique of the present invention includes informing
the user that he is attempting to access a domain name that he is
not authorized to access. The procedure requests that a user
confirm his intent to access such a domain by requesting financial
verification which may be a credit/debit card, electronic check or
the like, for billing access and traffic charges. Upon agreement
and verification, the SGSN selects the requested APN and the
appropriate gateway GPRS support node (GGSN) to facilitate the
connection.
BRIEF DESCRIPTION OF THE DRAWINGS
[0007] The present invention will be understood from the
accompanying description and drawings wherein like elements are
designated by like numerals and, wherein:
[0008] FIG. 1 is a diagram useful in explaining the packet data
protocol (PDP) context activation procedure.
[0009] FIG. 2 is a diagram useful in explaining overall GGSN
selection.
[0010] FIG. 3 is a diagram showing the conventional APN selection
procedure.
[0011] FIG. 4 is a diagram showing the APN selection procedures
(SGSN) of the present invention.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT(S)
[0012] FIG. 1 shows a PDP context activation procedure in which the
mobile station 10, at step S1, activates a packet data protocol
(PDP) context request to SGSN14, which request includes information
such as PDP type, PDP address, access point name (APN), quality of
service (QoS) and the like. The APN is used to select a reference
point to a certain packet data network and/or to select a service.
SGSN 14, at step S2, validates the request, selects the requested
APN and maps the APN to a GGSN, such as GGSN 16. Thereafter, the
SGSN, at step S3, creates the packet data protocol (PDP) context
request which includes the PDP type, the PDP address, the access
point name (APN), quality of service (QoS) and the like. GGSN 16
creates the PDP context response including the tunnel endpoint
identifier (TEID), PDP address, PDP configuration options, QoS,
charging identification and cause, at step S4. At step S5, a radio
access bearer (RAB) setup is created between SGSN 14 and radio
access network (RAN) 12 (step S5A) and between the mobile station
10 and the radio access network (RAN) 12 (step S5B) utilizing a
known RAB assignment procedure. At step S6, SGSN 14 invokes a trace
with RAN 12 employing a known procedure.
[0013] At step S7, SGSN 14 updates the PDP context request to GGSN
16 and, responsive thereto, GGSN 16 updates the PDP context
response, at step S8. SGSN 14, at step S9, inserts the GGSN address
into its PDP context and sends the PDP address received from the
GGSN 16 to mobile station 10 and activates the PDP context accept
at step S10 which includes PDP type, PDP address, TI, QoS, radio
priority, packet flow ID and PDP configuration options.
[0014] FIG. 2 is a diagram useful in explaining the overall GGSN
selection. The UE 10, also shown as the mobile station in FIG. 1,
sends a request including PDP type, PDP address and APN to SGSN 14.
The SGSN 14 sends the APN and visited/home public land mobile
network (V/H) PLMN-OI to the directory name service (DNS) database
16 which either provides the GGSN address shown at 18 or indicates
an error at 20 if there is no associated GGSN.
[0015] The SGSN 14 receives from the home location register (HLR)
22 the subscribed: PDP type, PDP address, APN and the visited
public land mobile network (VPLMN) address which is allowed. SGSN
14 also receives the SGSN access point name (APN) from defaults 24
provided in software which is hard-coded in SGSN 14.
[0016] FIG. 3 shows the existing procedure for APN selection
wherein, at step S1, the SGSN receives an activate PDP context
request from the UE (note, for example UE 10 in FIG. 2). At step
S2, the SGSN checks the optional information which includes PDP
type, PDP address and APN. If there is no information, at step S3,
the SGSN, which branches to step S7, checks the subscribed
information and, at step S8, rejects the request if the UE has
multiple PDP subscriptions since only one PDP type can be
designated. Alternatively, after performing the checking step S7,
at step S9, if the checking step indicates that the UE has a single
subscription, the SGSN, branches to step S10 and provides
subscribed information which includes the address mode, either
dynamic or static, the PDP type and the subscribed APN of the SGSN
if the subscribed APN is a wildcard and there is no APN request.
WILDCARD=means that Any Name can be used without causing any
problems.
[0017] Returning to step S2, if there is only a PDP type request,
determined at step S4 and if the PDP type compares with the
subscribed PDP type, determined at step S11 the routine jumps to
step S10 wherein the SGSN provides the same information as set
forth above and as shown in step S10.
[0018] Returning to step S11, if the PDP type is not the subscribed
PDP type the routine branches to step S12, causing the request to
be rejected by the SGSN.
[0019] Again returning to step S11, if the PDP type is the
subscribed PDP type and the PDP add request (PDP ADD (R)) is the
same as the PDP add subscribed, determined at step S13, the SGSN
provides the data shown at step S10. However, returning to step
S13, if the PDP add request (PDP ADD(R)) is not the same as the PDP
add subscribed, the routine branches to step S12 wherein the
request is rejected. (R) here means Requested by the UE. It may or
may not be honored by the network depending on the subscription
information in the HLR.
[0020] Again returning to step S11, if the PDP type is the same as
the PDP type subscribed and, as determined at step S14, if the APN
request is the same as the APN subscribed, the SGSN branches to
step S10 providing the information set forth therein. However, if
the APN request is not the same as the APN subscribed, the routine
branches to step S12 in which the request is rejected.
[0021] Returning to step S2, if the PDP type request, the PDP type
the PDP address and the APN are all present, the program, at step
S16, branches to step S11 to determine if the PDP type is the same
as the PDP type subscribed. If so, the program branches to step S14
wherein, if the APN requested is the same as the APN subscribed,
the SGSN provides the information shown in step S10. If the APN
requested is not the same as the APN subscribed, the routine
branches to step S12 wherein the request is rejected.
[0022] Returning to step S14, if the APN request is the same as the
APN subscribed the routine branches to step S15 wherein, if the PDP
add request is the same as the PDP add subscribed, the SGSN
provides the information set forth at step S10. Alternatively, if
the PDP add request (PDP ADD (R)) is not the same as the PDP add
subscribed, the routine branches to step S12 in which the request
is rejected.
[0023] FIG. 4 shows the extended APN selection procedure in
accordance with the present invention wherein, when the SGSN, at
step S1 receives the activate PDP context request from the UE 10
(see FIGS. 1 and 2), the SGSN, at step S2, checks the optional
information such as PDP type, PDP address and APN. If only the PDP
type and APN are present, at step S3, the routine branches to step
S4 to determine if the PDP type is the subscribed PDP type. If not,
the routine branches to step S5, rejecting the request. If the PDP
type is the same as the subscribed PDP type, the routine branches
to step S5 to examine the APN. If the requested APN is the same as
the subscribed APN, the routine branches to provide the same
information shown at step S10 in FIG. 3.
[0024] If the APN requested and the APN subscribed are not the
same, the routine branches to step S7 to inform the user that the
APN requested is not authorized and that if the UE (mobile station)
wants to continue, the UE must agree to the terms and conditions
and provide credit (or debit) card or like information.
[0025] The SGSN, at step S8 examines the UE response and, if the
terms and conditions are accepted, the routine branches to step S9
wherein the requested APN is selected. If the UE does not accept
the terms and conditions, the routine branches to step S5 wherein
the SGSN rejects the request.
[0026] Returning to step S2, when the PDP type, PDP address and APN
are all present, the routine branches to step S10 wherein steps S4
and S6 are repeated and, dependent upon the results of these
comparisons, the routine branches to either steps S5, S7 or S10 of
FIG. 3, the remainder of the routine being the same as described
hereinabove for the case where only PDP type and APN are provided
to the SGSN by the UE, shown in step S3 in FIG. 4.
* * * * *