throbber
(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2012/0020318 A1
`
` Naoe et al. (43) Pub. Date: Jan. 26, 2012
`
`
`US 20120020318A1
`
`(54) MOBILE COMMUNICATION SYSTEM
`
`Publication Classification
`
`(76)
`
`Inventors:
`
`Hirokazu Naoe, Osaka (JP);
`Masafumi Aramoto, Osaka (JP)
`
`(51)
`
`Int. Cl.
`(2009.01)
`H04 W 72/04
`(2009.01)
`H04 W 76/00
`(52) US. Cl. ......................................... 370/329; 370/338
`
`(22) PCT Filed:
`
`Mar. 26, 2010
`
`(86) PCT No.:
`
`PCT/JP2010/002185
`
`§ 371 (0)0),
`(2), (4) Date:
`
`Sep. 22’ 2011
`
`(30)
`
`Foreign Application Priority Data
`
`Mar. 27, 2009
`
`(JP) ................................. 2009-079962
`
`A core network includes a PDN connection holding unit that
`associates and stores information regarding PDN connection
`with information indicating an address block configured as a
`set of a plurality of addresses identifying a plurality of the
`information terminal devices. Therefore, it is possible to sup-
`press an increase in the processing load and a limitation of
`providable services, even in the case in which an ad-hoc
`network is formed between a mobile terminal device and a
`
`plurality of terminal equipments and a PDN connection is
`made by the terminal equipments using the mobile terminal
`device as an MT.
`
`.
`
`‘
`
`ATTACH
`REQUEST {EN H
`
` 21:32
`
`
`
`
`
`A04
`
`AEERESS SL063;
`STBRAGE U165?
`
`“
`
`
`
`
`CGWUNEQAHGN UNET
`
`TE CfiNNECTlfiF‘é
`EE‘éTERFACE UM?
`
`1
`
`SAMSUNG 1009
`
`SAMSUNG 1009
`
`1
`
`

`

`Patent Application Publication
`
`Jan. 26, 2012 Sheet 1 0f 17
`
`US 2012/0020318 A1
`
`Fifi. i
`
`5p
`“K N; \\
`/"/"gfiw
`EXFERNAL Pm
`
`)
`
`:
`
`\\\
`
`f,» ,
`
`mama mmmm‘rmm SYSTEM
`
`SEQ
`
`,24
`H33 SEVEGE
`
`~~~~~~~~~~~~~~~~~~~~~~~N
`2‘3
`‘
`PEN—6W {>5va
`
`2,0
`“4::
`
`i
`“x
`
`22
`m 53mm;
`
`; H23
`Mar: [35mg
`
`GORE NETWGRK
`
`,
`1/
`
`
`
`
`ENE {BEVEGE
`
`3?
`
`WERELESS
`
`ACCESS NETWQRK
`
`“x,
`
`E
`
`24%
`
`531E
`mag
`TERMENAL 5&va
`
`Am
`
`I
`
`’
`
`TE
`BEVEGE
`
`AM:
`’
`
`YE
`{>5va
`
`2
`
`

`

`Patent Application Publication
`
`Jan. 26, 2012 Sheet 2 0f 17
`
`US 2012/0020318 A1
`
`MG, 2
`
`f“;
`
`21:
`
`AflDRESS BLGGK
`HGLBENE mm
`
`A
`
`‘
`
`234
`PEN camacnefi
`HGLBENG 15m
`
`5
`
`,2i2
`
`2;
`
`2§5
`
`PDN cemacmw
`SETTENG um
`
`um am
`YRANSFER mm
`
`‘
`
`(/213
`

`
`,Zifi
`

`
`3—139; CGNNECTEQN
`ENTERFAGE um
`
`ma camcmw
`EE‘éTERFACE mm
`
`Fifi 3
`
`{23
`
`,231
`
`
`
`
`
`
`iiSER DATA
`YRAM$FER ENE"?
`
`'
`
`
`
`
`
`
`
`GQMMUN EGAN {3N
`(SGMRGL ENE?
`
`,236
`
`PEN—(ii? CQNNEGTWN
`ENTERFAGE LENS?
`
`3
`
`

`

`Patent Application Publication
`
`Jan. 26, 2012 Sheet 3 0f 17
`
`US 2012/0020318 A1
`
`E?i(}.44
`
`f/zz
`
`22:
`
`A
`
`ENTERFASJE GMT
`
`‘
`
`HGLEEERG UNST
`
`”
`
`222
`
`,224
`
`225
`
`CGWUE‘HCAT 3 GM
`GONTRGL REM?
`
`355mm
`
`22? w ENABLEB/DESASLEEB
`
`JUBGMENT um ‘
`
`SUBSCRi BER
`ENFGRMAT E OE
`
`HGLBENG UN”
`
`,223
`
`K 422%
`
`EMfiflEE CGNNESTEGE‘Q
`iNYERf-"ASE UM?
`
`smaw Gfii‘éi‘éEfliiQSfi
`MERE-"ACE UM?
`
`E?i(}.f§
`
`
`
`
`
`WE BGWECHQN
`iNTERFACE-E UN”
`
`?
`
`swam um?
`
`J24
`
`
`
`24%
`
`242
`
`243
`
`LGCATESM
`ENFQRMATEQN
`HQLBENG UNET
`
`SUBSQREBER
`iNFDRMAfiGN
`
`‘W244
`
`
`
`
`
`
`
`j:
`
`HGLDEE‘EG {MET
`
`4
`
`

`

`Patent Application Publication
`
`Jan. 26, 2012 Sheet 4 0f 17
`
`US 2012/0020318 A1
`
`Fifi é
`
`WERELESS
`COMMUNHCAHQN UNET
`
`“
`
`smumwm
`GGNTRDL UNET
`
`‘
`
`ENTERFAGE LENS?
`
`#313
`
`SmGE’vF CGNNEQYEGN
`ENFERFAQE {EMT
`
`WE CGNNECTEQRE
`
`PEG. ‘1?
`
`433
`
`?
`
`REQUEST mm
`
`TE CONNECTEGN
`mug? mm
`
`
`
`
`
`
`.404
`
`AHEBRESS swag
`$TGRAGE UM?
`
`“
`
`’2? #48
`
`mum?
`mama; aim
`
`5
`
`
`
`
`.
`
`a;
`ABfiRESS
`ALLGCATEGN {MET
`
`406
`
`#403
`
`WERELESS
`GflifiifiUNEGAfififii UNET
`
`TE CQNNECTEQN
`EE‘éTERFACE ENE?
`
`5
`
`

`

`Patent Application Publication
`
`Jan. 26, 2012 Sheet 5 0f 17
`
`US 2012/0020318 A1
`
`HG, 8
`
`J41&
`
`4‘“
`
`
`
`
`m WWW-HM
`WERELESS
`
`
`
`CWWMGATEGN REM"?
`
`
`
`412
`
`6
`
`

`

`Patent Application Publication
`
`Jan. 26, 2012 Sheet 6 of 17
`
`US 2012/0020318 A1
`
`mm:
`
`magma
`
`~
`
`ww
`
`mgmwmmxi
`
`
`
`iiiilllliliiiiii“.....
`
`
`
`
`
`
`
`“gag.
`
`“gag mm1mmxgmmmmsm
`
`Wm)
`
`
`
`‘mama”
`
`mam
`
`m,“5%
`
`émmmmmw
`
`mafia
`
`a;
`
`
`
`mm,
`
`murflm
`
`mw‘mwmnw
`
`7
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Jan. 26, 2012 Sheet 7 of 17
`
`US 2012/0020318 A1
`
`
`
`
`
`
`
`wzfimmamflumzzmm2mm‘..\\iwmmwwwwmww
`
`mm
`
`
`
`
`
`
`
`mafia
`
`mmmwm
`
`.xmmmwmm
`
`
`
`
`
`Em“gum2“mgm;u:memwmmmagmmmmmmmwwmmham:
`
`
`
`
`
`GEE”$33awm¢§mm4%“ng35%m5Emafimwmmmb
`
`a‘y‘
`
`magma,mufia
`mmmHE$ng
`
`gmim
`
`mafia
`
`.{magma
`
`mg
`
`E@E
`
`flEma
`
`£3,“
`
`
`
`mafia.mamaEm3a
`
`8
`
`
`
`
`
`

`

`Patent Application Publication
`
`Jan. 26, 2012 Sheet 8 0f 17
`
`US 2012/0020318 A1
`
`ETEE ii
`
`START
`

`REEEEVE PACKET
`FRQM EXTERNAL PEN
`
`“Sai
`
`“Sa2

`VEREFY PACKET ADDREfifiEE
`
`:5:
`3‘
`
`,ESa
`
`3
`
`
`
`
`
`_ * ADDRESSEE
`
`ES mp1?
`
`A six: mamas :9
`
`~
`
`SELECT DEFAULT EPS BEARER 2
`
`
`BE THE PEN QQNNEQHGN 2
`
`i‘JSaS
`£33353ng :3" -
`
`SELECT? DEFAULT EPS SEARER 2 :
`GE EHE PEN GQNNEGTififi
`
`“i
`
`USE $ELECTED EPS BEARER
`"f9 TRANSFER PACKET T0 SEE!
`
`
`
`ENE
`
`9
`
`

`

`Patent Application Publication
`
`Jan. 26, 2012 Sheet 9 0f 17
`
`US 2012/0020318 A1
`
`MG“ 12
`
`{4&8
`
`4Qia
`
`QONNECTEW REQEEST um
`
`REQUEST UNET
`
`AWAGH
`
`:
`
`494
`
`AflfiRESS BLQGK
`SMRAGE UN”
`
`‘
`
`,J495
`

`
`495
`
`RGUTER
`FBEGTEGE UM?
`
`AEBRESS
`ALLGCMEGRE WET
`
`146?
`
`3
`
`3
`
`408
`
`WERELES
`“ GGMfiiUNECMMN UM?
`
`TE GQNNEGHGN MRELESS
`Cfiifiififii‘éii‘éflifii‘i WET
`
`10
`
`10
`
`

`

`Patent Application Publication
`
`Jan. 26, 2012 Sheet 10 of 17
`
`US 2012/0020318 A1
`
`mmimx
`
`
`
`mafiaWm35%mm>mafiammmafiammmafiaHNew.SEQ2%ng3w:magma
`SWwafimEK:EEMHH
`
`
`
`
`
`
`s...............................................Tmmfiw
`
`mw.mww%
`
`hmwwmx
`
`Hmsmmwwwx.WH3
`
`mammwWm
`
`
`
`
`mmwwwflulNwwpmmmwWm
`
`11
`
`11
`
`
`
`

`

`Patent Application Publication
`
`Jan. 26, 2012 Sheet 11 of 17
`
`US 2012/0020318 A1
`
`PK}: E4
`
`(2:5
`
`«M
`
`AflBRESS BLGGK
`HQLQENG UNET
`
`Q”
`
`Pgfi C3NNEGTES§
`HGLDEfiG uwar
`
`‘%
`
`#21 2
`
`12'? 5
`
`PM SSMNEGTEGN
`SEiTENG {WET
`
`‘
`
`{J3EE EMA
`YRANSFER ENE?
`
`3H6? SERVER UNET ‘
`
`H213
`
`:3;
`
`#2? 5
`
`SmGW CQNMECTEGEQ
`ENTERFAGE {EMT
`
`PM CQNNECTESN
`EE‘éTERFACE UNET
`
`#23?
`
`12
`
`12
`
`

`

`Patent Application Publication
`
`Jan. 26, 2012 Sheet 12 of 17
`
`US 2012/0020318 A1
`
`Fifi. 15
`
`,,,4m
`
`GONE‘éECTEGN REQEJES? {JNET
`"I
`
`
`ATTACH
`REQUEST 3N3?
`
`
`
`TE CONNECTEGN
`EQUEST {53% ET
`
`
`
`
`
`
`
`
`
`AEBRESS ELQGK
`STGRAGE WET
`
`”
`
`
`
` 5
`
`‘
`
`:;
`
`4%
`
`RGEJTER
`FUNCTEGN ENE?
`
`AflfiRESS
`ALLQGATEQN {Jim
`
`$
`
`,248?
`
`”
`
`4m»;
`
`403
`
`‘
`
`
`
`WE RELESS
`GflfiMUNEGAfiGN UNET
`
`TE GGNEEC‘FECE wERELESS
`CGEMBNECATEGN ENE?
`
`49g
`
`EH53? CHEN"? UM?
`
`
`
`13
`
`13
`
`

`

`Patent Application Publication
`
`Jan. 26, 2012 Sheet 13 of 17
`
`US 2012/0020318 A1
`
`mufimmmafia
`
`wmmwmr
`
`mmmfimmmamEgan
`
`zcfifimmmmmm
`
`
`‘mmxgwtzmnm
`‘ $1
`mm,mmrmm,mmafiaHmagmaHmag
`
`
`”aim‘Hmg”iHME
`
`mmwmmx
`
`wamm\
`
`wfimafi
`
`
`
`mwfimm.Ezmsmmmw
`
`mww,
`
`www,
`
`magmaE2
`
`magma
`
`‘
`
`a.
`
`3fig
`
`14
`
`14
`
`
`

`

`Patent Application Publication
`
`Jan. 26, 2012 Sheet 14 of 17
`
`US 2012/0020318 A1
`
`PEG“ 1”?
`
`ABDRESS BLQCK
`HGLBENG UNET
`
`{#2120
`
`PEN CGNNEQTEQN
`SETTENG UNiT
`

`
`‘,2§5
`
`6
`
`
`
`Sufi?! CGNNECWON
`iNTERFACE UNET
`
`MG. 38
`
`
`
`[436
`_.,4ma
`5"
`
` CGNE‘éECTEON REQUEST UNET
`1432
`AWAGH
`REQUEST um
`
`
`
`
`
`
`TE CGfiNEGTEGN
`REQUEST W
`
`
`
`ABBRESS ELQGK
`STQRAGE ENE?
`
`
`#404
`
`
`FEJNGTEGN UNET
`
`
`
`RGU'E'ER
`
`ADDRESS
`ALLOCATEGN UNET
`
`
`
`
`
`TE CQNNECTiQN WERELESS
`‘-
`WERELESS
`
`
`
`CGMMUNECAEGN UNET
`CQWUNECATEQN UNE?
`
`
`
`15
`
`15
`
`

`

`Patent Application Publication
`
`Jan. 26, 2012 Sheet 15 of 17
`
`US 2012/0020318 A1
`
`\wm
`
`www
`
`mm:
`
`mama
`
`gwimmm
`
`mmwin
`
`
`
`16
`
` m
`
`mm!
`
`awim
`
`mumEm
`
`.“2%WE
`
`,
`
`.mafia
`
`mam
`
`
`
`émmmmmh.35%
`
`murfim
`
`magmam3»MW
`
`“mamaE
`
`16
`
`
`
`

`

`Patent Application Publication
`
`Jan. 26, 2012 Sheet 16 0f 17
`
`US 2012/0020318 A1
`
`PEG. 2%
`
`,222
`
`,222
`
`.
`
`‘
`
`LQCATEGN ENFGRMATEGN
`HGLBENQ {5553?
`
`225
`
`SUBSCREBER ENF‘QRE‘JEAHGN
`HGLQEE‘EG UNET
`
`‘
`
`'
`
`,
`
`CGEEMUEECATBON
`
`CGNFRGL UNET
` 22"}
`SETTEE‘EG
`’
`, ENAELEfi/DESABLEfi
`
`JUDGMENT UNET
`
`
`
`ENQDEB GGNNECTEGN
`S—GW SONNEQTHEN
`
`MYERFACE UN”
`ENTERFACE UNET
`
`
`
`
`
`
`‘
`
`2;:
`
`AM
`
`ABBRESS BLQGK
`Si‘flRAGE UM?
`
`
`
`:
`
`
`’
`2223222
`
`
`» mmcmmuw »
`
`
`
`
`
`CQMEBNECATEUN UNET
`TE CGNE‘SECTEGN WERELESS
`
`2,2496
`
`
`
`
`ADDRBS
`ALLGCATEGN Uh“?
`
`
`
`
`
`422
`
`
`
`25222222
`22222322222202 um?
`
`'
`
`
`17
`
`17
`
`

`

`Patent Application Publication
`
`Jan. 26, 2012 Sheet 17 of 17
`
`US 2012/0020318 A1
`
`
`
` mme
`
`mwmwmx .‘wzmfiwmmmfim
`lemmama“mm20%E,305gamma
`
`
`
`kg$73.NN,‘mm,33.fix?my?
`
`%%%%ggH!
`mmfimmmagmawwfimmmafiamagmamagmaqumwmmmwmagma5:me
`
`
`
`
`
`
`
`mm.me
`
`Emg)
`
`mamg}
`
`gamma
`
`mama
`
`mmfimx
`
`18
`
`A:::::::H1aaaaaaaaaaaaaaaaaaaa
`
`{Sma
`
`
`
`“mammwx§
`
`18
`
`
`
`

`

`US 2012/0020318 A1
`
`Jan. 26, 2012
`
`MOBILE COMMUNICATION SYSTEM
`
`TECHNICAL FIELD
`
`[0001] The present invention relates to a mobile communi-
`cation system, and particularly to a mobile communication
`system connected to an external packet data network.
`[0002] The present application claims priority based on the
`patent application 2009-079962, filed on Mar. 27, 2009 in
`Japan, the content of which is incorporated herein by refer-
`ence.
`
`BACKGROUND ART
`
`In the UMTS (Universal Mobile Telecommunica-
`[0003]
`tions System) that has been standardized as a third-generation
`mobile communication system, an MT (Mobile Terminal) is
`established as a mobile terminal that has a UMTS wireless
`
`interface and a TE (Terminal Equipment) is established as a
`terminal equipment that connects to the MT. The MT and TE
`are collectively called UE (User Equipment).
`[0004] A TE-MT interface is set forth in the Non-Patent
`Document 1 (TS 27.060), wherein a communication protocol
`is indicated in which a TE such as a laptop PC (personal
`computer) that does not have a UMTS wireless interface
`connects to a PDN (Packet Data Network) that is an external
`network, via the UMTS wireless interface in an MT. Although
`the physical interface between the TE and MT can use not
`only a wired interface such as a serial cable or a USB (Uni-
`versal Serial Bus) cable, but also can use a wireless interface
`such as Bluetooth (registered trademark) or the like, the use of
`the PPP (Point-to-Point Protocol) is called for.
`[0005]
`Patent Document 1 discloses a method whereby,
`rather than a TE-MT interface, an Ethernet (registered trade-
`mark) and DHCP (Dynamic Host Configuration Protocol) are
`used to allocate an IP (Internet Protocol) address to the TE
`and make connection to the PDN. Additionally, it is assumed
`that it will be possible to use this TE-MT interface in the EPS
`(Evolved Packet System), which is standardized as the next-
`generation mobile communication system by the 3GPP (3rd
`Generation Partnership Project).
`[0006] The protocol for connecting a UE to the PDN in an
`EPS is set forth in the Non-Patent Document 2 (TS 23.401).
`The UE, after first being attached to the wireless access net-
`work, establishes a logical path connection to the PDN, which
`is known as a PDN connection.
`
`[0007] The PDN is uniquely identified by the APN (Access
`Point Name), and is connected to the core network via a
`PDN-GW, which is an external gateway equipment. The PDN
`connection is established individually for each PDN-GW that
`is connected to the UE. Even via one and the same PDN-GW,
`when connections are made to different PDNs, independent
`PDN connections are required.
`[0008] One PDN connection combines a plurality oflogical
`paths that is known as an EPS bearer when transferring a user
`IP packet, and it is further possible to assign a QoS (Quality of
`Service) class and a charging rule or the like to each EPS
`bearer. Therefore, using the UE packet transmission destina-
`tion and transport protocol, it is possible to apply different
`QoS classes and charging rules to each IP packet, using a port
`number.
`
`Patent Document 1: Japanese Unexamined Patent
`[0009]
`Application Publication (Translation of PCT Application)
`No. 2008-511222
`
`1: TS 27.060 Packet
`[0010] Non-Patent Document
`Domain; Mobile Station (MS) Supporting Packet
`Switched Services
`
`[0011] Non-Patent Document 2: TS 23.401 General Packet
`Radio Service (GPRS) Enhancements for Evolved Univer-
`sal Terrestrial Radio Access Network (E-UTRAN) Access
`
`DISCLOSURE OF INVENTION
`
`Problem to be Solved by the Invention
`
`[0012] However, when a user is walking around carrying a
`plurality of TEs such as a PDA or a laptop personal computer
`that does not have a wireless interface for direct connection to
`an EPS and a mobile terminal device that alone can connect to
`
`an EPS as a UE, an ad-hoc network being formed that locally
`makes connection between these devices, and the TE being
`connected to the ad-hoc network uses the mobile terminal
`device as an MT to make connection to the PDN, there is a
`problem that the processing load increases as noted below,
`and there is a limitation on the service that can be provided.
`[0013] Conventionally, PDN connections have been estab-
`lished for each TE. Therefore, even in the case in which a
`plurality of TEs are connected to one and the same PDN and
`also to one and the same PDN-GW, as many procedures for
`establishing PDN connections are necessary as there are TEs.
`The mobile terminal device itself to which the TE is con-
`nected is also connected to the EPS and establishes a PDN
`connection for the mobile terminal device in order to benefit
`
`from the communication service. However, with regard to any
`of these PDN connections, even though they are established
`from a common mobile terminal device as the point of origin,
`because they could not be combined, there was the problem of
`an increase in the processing load, because of the increase in
`the overall system administrative information. Additionally,
`at the time of handover as well, it is necessary to perform the
`protocol for re-establishing the PDN connections for all PDN
`connections, thereby causing an increase in the overall sys-
`tem processing load.
`[0014] A method that can be envisioned so that the number
`of PDN connections does not increase is that of providing an
`NAT (Network Address Translator)
`in the above-noted
`mobile terminal device, and sharing one IP address allocated
`to the mobile terminal device and one PDN connection
`
`between the mobile terminal device and a plurality of TEs. In
`this case, however, not only does the installation into the
`mobile terminal device becomes complex, but also process-
`ing for the mobile terminal device to check all the packets
`transmitted and received by the TE becomes necessary and, if
`necessary, to rewrite the packet header and payload, thereby
`increasing the processing load on the mobile terminal device.
`This results in the problems of a reduced throughput and an
`increase in battery consumption of the mobile terminal
`device. Additionally, because a packet transmitted by the
`mobile terminal device itself and a packet that the TE trans-
`mits cannot be distinguished when seen from the viewpoint of
`the core network, the limitation occurs that, in spite ofthe fact
`that it is the origin of a packet transmission, the same QoS
`class and charging rule must be applied, this leading to the
`problem ofhindering the implementation of a diverse service
`model
`in which different charging models are applied,
`depending upon the mode of use.
`[0015] The present invention was made in consideration of
`the above-described situation and has as an object the provi-
`sion of a mobile communication system capable of suppress-
`
`19
`
`19
`
`

`

`US 2012/0020318 A1
`
`Jan. 26, 2012
`
`ing an increase in the processing load and a limitation of
`providable services, even in the case in which an ad-hoc
`network is formed between a mobile terminal device and a
`
`via the wireless access network, may include in the request a
`request for setting of the information terminal PDN connec-
`tion.
`
`plurality of TEs and a PDN connection is made by the TE
`using the mobile terminal device as an MT.
`
`Means for Solving the Problem
`
`(1) In an aspect of the present invention, there is
`[0016]
`provided a mobile communication system including a mobile
`terminal device performing a communication connection
`with a plurality of information terminal devices, a wireless
`access network performing wireless communication with the
`mobile terminal device, and a core network performing com-
`munication with an external packet data network, and also
`performing communication with the mobile terminal device
`via the wireless access network, wherein: the core network
`includes a PDN connection holding unit that associates and
`stores information regarding PDN connection that is a logical
`path used for transfer of user data via the wireless access
`network between the external packet data network and the
`mobile terminal device with information indicating an
`address block configured as a set of a plurality of addresses
`identifying a plurality of the information terminal devices.
`[0017]
`(2) In the aspect of the present invention, the mobile
`terminal device may include: a connection request unit that
`requests the core network to set an information terminal PDN
`connection that is a PDN connection to be used for transfer of
`user data ofthe information terminal devices and that receives
`
`from the core network information indicating the address
`block assigned to the information terminal PDN connection
`set by the request; an address allocation unit that allocates an
`address belonging to an address block indicated by informa-
`tion received by the connection request unit to the informa-
`tion terminal devices; a router function unit that, when user
`data addressed to an address allocated to the information
`terminal devices is received, transfers the received user data
`to the information terminal devices to which the address is
`
`allocated; wherein the core network may include a PDN
`connection setting unit that, when a request is received from
`the mobile terminal device, allocates the address block to the
`PDN connection for the information terminal and associates
`
`and stores in the PDN connection holding unit information
`indicating the address block with information regarding the
`PDN connection for the information terminal, and transmits
`information indicating the allocated address block to the
`mobile terminal device.
`
`(3) In the aspect of the present invention, the con-
`[0018]
`nection request unit of the mobile terminal device, when
`requesting the setting of the information terminal PDN con-
`nection, may specify an address block class that is a type of
`the address block allocated the information terminal PDN
`
`connection and that specifies one of an address block indi-
`cated by the IPv4 network address, an address block indicated
`by the IPv6 prefix, or an address block indicated by the IPv4
`network address and by the IPv6 prefix, and wherein the PDN
`connection setting unit of the core network, when setting the
`information terminal PDN connection, may allocate to the set
`information terminal PDN connection the type of address
`block specified by the address block class.
`[0019]
`(4) In the aspect of the present invention, the con-
`nection request unit of the mobile terminal device, when
`requesting the core network to set a PDN connection for a
`mobile terminal that is a logic path used for transfer of user
`data of the mobile terminal device with an external network,
`
`(5) In the aspect of the present invention, the con-
`[0020]
`nection request unit of the mobile terminal device, when
`requesting the core network to set a PDN connection for a
`mobile terminal that is a logic path used for transfer of user
`data of the mobile terminal device between an external net-
`
`work and thereof, via the wireless access network, may
`include in the request a flag indicating that the mobile termi-
`nal device includes the router function unit, and wherein, the
`core network may include a setting enabled/disabled unit that,
`when a request to set the information terminal PDN connec-
`tion is received, judges, based on the flag, whether the infor-
`mation terminal PDN connection can bet set.
`
`(6) In the aspect of the present invention, the mobile
`[0021]
`terminal device may include an address block storage unit
`that stores information indicating the address block, and
`wherein the address allocation unit of the mobile terminal
`
`device, when the information terminal devices performs com-
`munication connection with the mobile terminal device, may
`allocate to the information terminal device an address that
`
`belongs to the address block stored by the address block
`storage unit.
`[0022]
`(7) In the aspect of the present invention, the core
`network may include a terminal information storage unit that
`stores information indicating an address block allocated to
`the information terminal PDN connection in association with
`information that
`identifies the mobile terminal device,
`wherein the PDN connection setting unit of the core network,
`upon receiving a request for an information terminal PDN
`connection setting, may allocate the address block stored by
`the terminal information storage unit, in association with
`information identifying the mobile terminal device that origi-
`nated the request.
`[0023]
`(8) In the aspect of the present invention, the core
`network may include a terminal information storage unit that
`stores information indicating whether a user of a mobile
`terminal device is subscribed to a network mobile service, in
`association with information identifying the mobile terminal
`device, wherein the setting enabled/disabledjudgment unit of
`the core network, upon receiving a request for setting of an
`information terminal PDN connection, may determine
`whether an information terminal PDN connection can be set,
`based on the flag in the request, and on information stored by
`the terminal information storage unit.
`[0024]
`(9) In the aspect of the present invention, the core
`network may include a terminal information storage unit that
`stores information indicating whether or not a user of the
`mobile terminal is subscribed to a network mobile service, in
`association with information identifying the mobile terminal
`device, wherein the setting enabled/disabledjudgment unit of
`the core network, upon receiving a request for setting of a
`mobile terminal PDN connection, may determine whether a
`mobile terminal PDN connection can be set, based on the flag
`in the request, and on information stored by the terminal
`information storage unit.
`the
`[0025]
`(10) In the aspect of the present invention,
`mobile terminal device may include a dynamic host setting
`client unit
`that, using a dynamic host setting protocol,
`requests an address block from the core network, and receive
`from the core network information indicating the address
`block allocated to the information terminal PDN connection
`
`by the request, wherein the core network may include a
`
`20
`
`20
`
`

`

`US 2012/0020318 A1
`
`Jan. 26, 2012
`
`dynamic host setting server unit that, upon receiving the
`request for the address block using the dynamic host setting
`protocol, allocate an address block to the information termi-
`nal PDN connection of the mobile terminal device that origi-
`nated the request, and transmit the address block to the mobile
`terminal device.
`
`the
`(l 1) In the aspect of the present invention,
`[0026]
`mobile terminal device may include: a connection request
`unit that requests the core network to set an information
`terminal PDN connection that is a logical path used for trans-
`fer of user data of the information terminal device with the
`
`external PDN, and receives as a response to the request infor-
`mation indicating an address allocated to the information
`terminal PDN connection set by the request; an address allo-
`cation unit that allocates an address received by the connec-
`tion request unit to the information terminal device; and a
`router function unit that, upon receiving user data addressed
`to the address allocated to the information terminal device,
`transfers the received user data to the information terminal to
`which the address had been allocated, wherein the core net-
`work, upon receiving a request from the mobile terminal
`device, may associate an address belonging to the address
`block allocated to the mobile terminal PDN connection used
`in transfer of user data of the mobile terminal device with
`
`information regarding the information terminal PDN connec-
`tion for which setting was requested, store these in the PDN
`connection holding unit, and transmit the allocated address to
`the mobile terminal device.
`
`Effect of the Invention
`
`[0027] According to the present invention, PDN connec-
`tions for a plurality of terminal devices connected to a com-
`mon mobile terminal device can be combined, and addition-
`ally the establishment of the PDN connection for the mobile
`terminal device and the establishment of the PDN connection
`
`for the mobile terminal device can be performed together,
`thereby enabling suppression of an increase in processing
`load and limitation of the providable service.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`FIG. 1 is a simplified block diagram showing the
`[0028]
`network configuration of a mobile communication system
`according to a first embodiment of the present invention.
`[0029]
`FIG. 2 is a simplified block diagram showing the
`configuration of a PDN-GW device 21 in the same embodi-
`ment.
`
`FIG. 3 is a simplified block diagram showing the
`[0030]
`configuration of an S-GW device 23 in the same embodiment.
`[0031]
`FIG. 4 is a simplified block diagram showing the
`configuration of an MME device 22 in the same embodiment.
`[0032]
`FIG. 5 is a simplified block diagram showing the
`configuration of an HSS device 24 in the same embodiment.
`[0033]
`FIG. 6 is a simplified block diagram showing the
`configuration of an ENB device 31 in the same embodiment.
`[0034]
`FIG. 7 is a simplified block diagram showing the
`configuration of a mobile terminal device 40 in the same
`embodiment.
`
`FIG. 8 is a simplified block diagram showing the
`[0035]
`configuration of a TE device 4111 in the same embodiment.
`[0036]
`FIG. 9 is a sequence diagram showing an example of
`the sequence of attaching the mobile terminal device 40 to an
`EPS in the same embodiment.
`
`FIG. 10 is a sequence diagram showing an example
`[0037]
`of connection of the TE device 4111 and the TE device 41b to
`the mobile terminal device 40 in the same embodiment.
`
`FIG. 11 is a flowchart showing the packet transfer
`[0038]
`processing of the PDN-GW device 21 in the same embodi-
`ment.
`
`FIG. 12 is a simplified block diagram showing the
`[0039]
`configuration of a mobile terminal device 40a in a second
`embodiment of the present invention.
`[0040]
`FIG. 13 is a sequence diagram showing an example
`ofthe sequence ofattaching the mobile terminal device 4011 to
`an EPS in the same embodiment.
`
`FIG. 14 is a simplified block diagram showing the
`[0041]
`configuration of a PDN-GW device 21b in a third embodi-
`ment of the present invention.
`[0042]
`FIG. 15 is a simplified block diagram showing the
`configuration of a mobile terminal device 40b in the same
`embodiment.
`
`FIG. 16 is a sequence diagram showing an example
`[0043]
`of the sequence of connection of the mobile terminal device
`40b in the same embodiment.
`
`FIG. 17 is a simplified block diagram showing the
`[0044]
`configuration of a PDN-GW device 210 in a fourth embodi-
`ment of the present invention.
`[0045]
`FIG. 18 is a simplified block diagram showing the
`configuration of a mobile terminal device 400 in the same
`embodiment.
`
`FIG. 19 is a sequence diagram showing an example
`[0046]
`of the sequence of the connection for the TE devices 4111 and
`41b performing communication with an external PDN 50 in
`the same embodiment.
`
`FIG. 20 is a simplified block diagram showing the
`[0047]
`configuration ofan MME device 22d in a fifth embodiment of
`the present invention.
`[0048]
`FIG. 21 is a simplified block diagram showing the
`configuration of a mobile terminal device 406 in a sixth
`embodiment of the present invention.
`[0049]
`FIG. 22 is a diagram showing an example of the
`sequence for establishing a TE PDN 21 connection in the
`same embodiment.
`
`BEST MODE FOR CARRYING OUT THE
`INVENTION
`
`First Embodiment
`
`[0050] The first embodiment of the present invention is
`described below, with references made to drawings. FIG. 1 is
`a simplified block diagram showing the network configura-
`tion of a mobile communication system according to the first
`embodiment of the present invention. The mobile communi-
`cation system 10 in this embodiment is connected to an exter-
`nal PDN (Packet Data Network) 50, and has a core network
`20, a wireless access network 30, and at least one mobile
`terminal device 40. In the example shown in FIG. 1, the
`mobile terminal device 10 has TE devices 4111 and 41b that
`
`are connected to the mobile terminal device 40. Although this
`embodiment is described for the example of an EPS as the
`mobile communication system that is standardized by 3GPP,
`the present invention is not limited in this manner, and can be
`applied in the same manner to a mobile communication sys-
`tem that has a node configuration.
`[0051] The core network 20 has a PDN-GW device 21, an
`MME (Mobile Management Entity) device 22, an S-GW
`device 23, and an HSS (Home Subscriber Server) device 24.
`
`21
`
`

`

`US 2012/0020318 A1
`
`Jan. 26, 2012
`
`The S-GW device 23 transmits and receives, as a local mobil-
`ity anchor, packets from the ENB (eNodeB: base station
`device) 31 to which the mobile terminal device 40 is con-
`nected.
`
`[0052] The PDN-GW device 21 is connected to the external
`PDN 50, which is the Internet or an IMS (IP Multimedia
`Subsystem), and functions as a gateway that connects the core
`network 20 to these types ofexternal PDNs 50. The PDN-GW
`device 21 allocates an IP address and performs sorting by
`packet QoS. The PDN-GW device 21 and the S-GW device
`23 may be constituted on one and the same physical node.
`[0053] The MME (Mobility Management Entity) 22 is an
`entity that performs only signaling, and has as its main func-
`tion management, including paging of mobility ofthe mobile
`terminal device 40 that connects to the wireless access net-
`work 30.
`
`[0054] The HSS device 24 performs user authentication
`and manages subscription data. Subscription data includes a
`subscriber’s service subscription information, and whether
`the subscriber is subscribed to NEMO (Network Mobility)
`service. The wireless access network 30 has at least one ENB
`device 31, which is a base station.
`[0055] The mobile terminal device 40 is a device that has
`the functions of both an MT and a UE in UMTS. The TE
`devices 4111 and 41b are TEs in UMTS.
`
`[0056] GTP (General Packet Radio Service Tunneling Pro-
`tocol) or GRE (Generic Routing Encapsulation) is used as the
`packet tunneling protocol between the S-GW device 23 and
`the PDN-GW device 21. With GTP, exchange is performed of
`the TEIDs (Tunnel Endpoint IDs) between two nodes and two
`TEIDs are set individually for each direction. Because differ-
`ent TEIDs are allocated for each EPS bearer, the GTP end-
`point node (S-GW device 23 or PDN-GW device 21) refer-
`ences the TEM included in the packet header to be able to
`uniquely distinguish between the mobile terminal device 40
`and its EPS bearer. Similar to GTP, GRE performs exchange
`of GRE keys, which correspond to the TEIDs in GTP,
`between two nodes, and sets two GRE keys (downlink GRE
`key and uplink GRE key) individually for each direction.
`[0057]
`FIG. 2 is a simplified block diagram showing the
`configuration of the PDN-GW 21 in the present embodiment.
`The PDN-GW 21 has an address block holding unit 211, a
`PDN connection setting unit 212, an S-GW connection inter-
`face unit 213, a PDN connection holding unit 214, a user data
`transfer unit 215, and a PDN connection interface unit 216.
`[0058] The S-GW connection interface unit 213 is a com-
`munication interface unit for performing communication
`connection with the S-GW device 23. Each unit of the PDW-
`
`GW device 21 performs communication with the S-GW
`device 23, via this S-GW connection interface unit 213. The
`PDN connection interface unit 216 is a communication inter-
`
`face unit for performing communication with the external
`PDN 50. Each unit of the PDN-GW device 21 performs
`communication with the external PDN 50, via this PDN con-
`nection interface unit 216.
`
`[0059] The address block holding unit 211 holds informa-
`tion indicating an address block that can be allocated to the
`PDN connection by the PDN connection setting unit 212,
`which is described later. An address block as used herein is a
`
`set of a plurality of addresses, and in the present embodiment
`is a network address in IPv4 (for example, 192.63.25.0/24 of
`l92.63.25.0 to 192.63.25.255) and an IPv6 prefix in IPv6 (for
`example, 13922d38c22/32 of l392:d38c:: to 13922d38cszff:
`ffffzz).
`
`[0060] The PDN connection holding unit 214 stores infor-
`mation regarding a PDN connection, associating it with infor-
`mation that indicates an address block. The PDN connection
`
`in this case is a logical path used for transfer of user data, via
`the wireless access network 30, between the external PDN 50
`and the mobile terminal device 40. There are two types of
`PDN connections, a PDN connection for UE (PDN connec-
`tion for a mobile terminal) for transferring user data of the
`mobile terminal device 40, and a PDN connection for a TE
`(PDN connection for an information terminal) for transfer-
`ring user data of the information terminals 41a and 41b.
`[0061] The PDN connection setting unit 212, upon receiv-
`ing a request from the mobile terminal device 40, allocates an
`address bloc

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket