WO2014050607A1 - Système de communication mobile, dispositif de gestion de position, dispositif de station de base domestique, dispositif de station mobile et procédé de communication dans un système de communication mobile - Google Patents

Système de communication mobile, dispositif de gestion de position, dispositif de station de base domestique, dispositif de station mobile et procédé de communication dans un système de communication mobile Download PDF

Info

Publication number
WO2014050607A1
WO2014050607A1 PCT/JP2013/074819 JP2013074819W WO2014050607A1 WO 2014050607 A1 WO2014050607 A1 WO 2014050607A1 JP 2013074819 W JP2013074819 W JP 2013074819W WO 2014050607 A1 WO2014050607 A1 WO 2014050607A1
Authority
WO
WIPO (PCT)
Prior art keywords
sipto
permission information
local network
henb
network
Prior art date
Application number
PCT/JP2013/074819
Other languages
English (en)
Japanese (ja)
Inventor
政幸 榎本
真史 新本
Original Assignee
シャープ株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by シャープ株式会社 filed Critical シャープ株式会社
Publication of WO2014050607A1 publication Critical patent/WO2014050607A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H04W84/045—Public Land Mobile systems, e.g. cellular systems using private Base Stations, e.g. femto Base Stations, home Node B

Definitions

  • the present invention relates to a mobile communication system in which a home network to which a home base station device and an access control device to which a mobile station device is connected is connected, and a core network to which a location management device is connected are connected via an external network.
  • the standardization organization 3GPP The 3rd Generation Generation Partnership Project
  • EPS Evolved Packet System
  • Non-Patent Document 1 the next generation mobile communication system.
  • a HeNB Home eNodeB: home base station
  • a small base station installed in a house or the like has been studied.
  • the HeNB constructs a small-scale radio cell called a femto cell and accommodates a UE (User : Equipment: mobile terminal device) using the same radio access technology as that of a normal base station. And it connects to the core network of a mobile communication system via a broadband network, and the communication data of UE accommodated can be relayed.
  • a UE User : Equipment: mobile terminal device
  • Non-Patent Document 2 discloses a candidate architecture for realizing SIPTO (Selected IP Traffic Offload).
  • SIPTO provides data communication to a UE accommodated in an eNB via a broadband network without passing through a core network of a mobile communication system while the UE is connected to a base station (eNB).
  • eNB base station
  • Non-Patent Document 3 discloses architecture candidates for realizing LIPA (Local IP Access).
  • LIPA Local IP Access
  • HeNB home base station
  • Non-Patent Document 3 describes SIPTO, and data is transmitted to a UE accommodated in the HeNB via the broadband network without connecting the core network of the mobile communication system while the UE is connected to the HeNB. Provide communication.
  • SIPTO shown here access in the home network cannot be performed. That is, SIPTO provided to UE accommodated in HeNB is provided as data communication different from the above-mentioned LIPA.
  • Non-Patent Document 3 a method in which a UE performs data communication from an eNB or HeNB via an offload point (TOF) in a mobile communication network and a broadband network is defined as SIPTO @ RN (Radio Access Network: wireless access). Network), and a method for performing data communication from the HeNB via the LGW via the broadband network is described as SIPTO @ LN (Local Network).
  • SIPTO @ RN Radio Access Network: wireless access. Network
  • LN Local Network
  • SIPTO @ RN is an offload service using TOF arranged in the core network
  • SIPTO @ LN LGW is used. It is an off-road service.
  • Non-Patent Document 3 describes a procedure for establishing a SIPTO PDN connection.
  • the PDN connection is a communication path established between the access control apparatus and the UE for each service.
  • the PDN connection used for the offload service is established.
  • a location management device MME: Mobility Management Entity
  • MME Mobility Management Entity
  • the MME cannot select the LGW for performing SIPTO @ LN in the GW selection, and SIPTO @ LN Cannot be established.
  • the UE can move between HeNBs using the LGW as an anchor.
  • 3GPP TS23.401 General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access 3GPP TR 23.829 Local IP Access and Selected IP IP Traffic Offload 3GPP TR 23.859 LiPA Mobility and SIPTO at local Local Network
  • GPRS General Packet Radio Service
  • the PTO connection of the SIPTO @ LN is unnecessarily transmitted even though the PDN connection of the SIPTO @ LN cannot be established.
  • the power consumption of the UE is wasted due to an increase in signaling for establishing the UE.
  • the MME cannot select a SIPTO @ LN-capable LGW by sending a SIPTO @ LN PDN connection request unnecessarily.
  • a processing load is given to the MME.
  • the MME transmits information indicating that the PDN connection cannot be established by unnecessarily transmitting the SIPTO @ LN PDN connection request. Has increased signaling for this purpose.
  • the present invention has been made in view of such circumstances.
  • the purpose of the present invention is to enable a home base station device to offload (SIPTO @ LN) via a local network to a mobile station device in a PDN connection establishment procedure. It is to provide a mobile communication system or the like capable of transmitting a SIPTO @ LN PDN connection request by detecting a certain thing.
  • the mobile communication system of the present invention is In a mobile communication system in which a home network to which a mobile station device is located and a home network to which an access control device is connected and a core network to which a location management device is connected are connected via an external network
  • the location management device includes: Managing first permission information for offloading via a local network for the mobile station device and second permission information for offloading via a local network for the access control device; Notifying the mobile station apparatus via the home base station apparatus off-road permission information via the local network based on the first permission information and the second permission information,
  • the mobile station device requests establishment of a PDN connection for offloading via a local network at the home base station device, based on permission information for offloading via the local network.
  • the mobile communication system of the present invention is In a mobile communication system in which a home network to which a mobile station device is located and a home network to which an access control device is connected and a core network to which a location management device is connected are connected via an external network,
  • the home base station device Managing offload permission information via a local network for the access control device; Notifying the mobile station device of offload permission information via a local network for the access control device,
  • the mobile station apparatus requests establishment of a PDN connection for offloading via the local network at the home base station apparatus, based on permission information for offloading via the local network.
  • the mobile communication system of the present invention is In a mobile communication system in which a home network to which a mobile station device is located and a home network to which an access control device is connected and a core network to which a location management device is connected are connected via an external network,
  • the mobile station device Set offload permission information via the local network in the home base station device,
  • the mobile station apparatus requests establishment of a PDN connection for offloading via a local network based on permission information for offloading via the local network.
  • the position management device of the present invention is A home network to which a mobile station device is located and a home network to which an access control device is connected, and a location management device connected to a core network via an external network, Managing offload permission information via the local network for the mobile station device and offload permission information via the local network for the access control device; Notifying permission information for offload via a local network to the mobile station device via the home base station device,
  • the home base station apparatus permits establishment of a PDN connection for offloading via a local network based on offload permission information via the local network for the mobile station apparatus.
  • the home base station device Managing offload permission information via the local network of the home base station device; Notifying offload permission information via the local network of the home base station device,
  • the mobile station apparatus permits the home base station apparatus to establish a PDN connection for offloading via a local network based on offload permission information via the local network for the mobile station apparatus.
  • the mobile station device The first permission information for offloading via the local network of the mobile station device and the second permission information for offloading via the local network of the access control device are managed, Off-road permission information via a local network is notified to the mobile station device via the home base station device,
  • the home base station apparatus requests establishment of a PDN connection for offload via the local network based on offload permission information via the local network.
  • the home base station device Managing offload permission information via the local network of the home base station device; Notifying offload permission information via the local network of the home base station device,
  • the mobile station device The home base station apparatus requests establishment of a PDN connection for offload via the local network based on offload permission information via the local network.
  • the home base station apparatus requests establishment of a PDN connection for offload via the local network based on offload permission information via the local network in the home base station apparatus.
  • the location management device includes: Managing offload permission information via the local network of the mobile station device and offload permission information via the local network of the access control device; Notifying permission information for offloading via a local network to the mobile station device via the home base station device; Have The mobile station apparatus has a step of requesting the home base station apparatus to establish a PDN connection for offloading via a local network based on offload permission information via the local network.
  • the mobile station apparatus detects that the home base station apparatus can be offloaded (SIPTO @ LN) via the local network, thereby allowing the mobile station apparatus to offload (SIPTO @ L) via the local network.
  • LDN can request a PDN connection.
  • the mobile station apparatus can transmit the PDN connection request for starting the PDN connection establishment procedure only when SIPTO @ LN is possible.
  • the mobile station apparatus prevents an unnecessary transmission of the PDN connection request by transmitting the SIPTO @ LN PDN connection request only when the mobile station apparatus can establish the SIPTO @ LN PDN connection. Thus, it is possible to prevent the power consumption of the mobile station apparatus from being wasted.
  • the location management apparatus can select an access control apparatus capable of SIPTO @ LN. Therefore, it is possible to select the LGW only, prevent unnecessary selection of the access control device, and prevent the processing load on the location management device.
  • the location management apparatus transmits information indicating that the PDN connection cannot be established by transmitting the SIPTO @ LN PDN connection request. Increase in signaling can be prevented.
  • FIG. 1 is a diagram for explaining an outline of a mobile communication system 1 in the present embodiment.
  • the mobile communication system 1 includes a core network 3, a home network 5, and a broadband network 7.
  • the broadband network 7 is a wired access network that realizes broadband communication, and is constructed by, for example, ADSL (Asymmetric Digital Subscriber Line) or an optical fiber.
  • ADSL Asymmetric Digital Subscriber Line
  • optical fiber an optical fiber.
  • the present invention is not limited to this, and a wireless access network such as WiMAX (Worldwide Interoperability for Microwave Access) may be used.
  • the core network 3 is a mobile communication network operated by a mobile communication provider, and includes an MME 10 (Mobility Management Entity), an SGW 40, and a PGW 60.
  • MME 10 Mobility Management Entity
  • SGW 40 Serving Gateway
  • PGW 60 Packet Data Network
  • the MME 10 is an entity that performs signaling, and is a location management device that leads the location management of the mobile station device (UE 50) and the procedure for establishing the PDN connection.
  • the PDN connection is a logical path for transferring a user IP packet established between the PGW 60 and the UE 50 or between the LGW 20 and the UE 50 in the home network for each UE.
  • the MME 10 determines to establish a SIPTO @ LN PDN connection
  • the MME 10 performs GW selection processing.
  • the MME 10 selects a SIP GW capable of SIPTO @ LN.
  • the establishment of a PDN connection includes the establishment of an EPS bearer or a radio bearer, and each bearer can set a specific QoS level with factors such as communication speed and bandwidth.
  • the SGW 40 is used for transmission / reception transfer of user data via the core network.
  • the SGW 40 is a conventional device accommodated in the core network. Therefore, the description is omitted.
  • the PGW 60 is an anchor device for transmitting / receiving data to / from a PDN (Packet Data Network).
  • the PGW 60 is a conventional device accommodated in the core network. Therefore, the description is omitted.
  • the home network 5 is a home network in a home, a corporate network such as a company, and the like, and includes an LGW 20, a HeNB 30, and a UE 50. Further, the home network 5 is connected to the broadband network 7.
  • the LGW 20 is a gateway device between the home network 5 and the broadband network 7 and has a function as a conventional broadband router such as a router with a built-in ADSL modem.
  • the HeNB 30 can accommodate the UE 50 as a base station provided by the core network operator while being installed in the home network 5. Typically, this is a 3GPP LTE (Long Term Evolution) base station that forms a femto cell.
  • the UE 50 is a mobile station device that can be accommodated in the HeNB 30 or the like.
  • FIG. 2 shows a configuration of the MME 10 in the present embodiment.
  • a transmission / reception unit 110 an LGW detection unit 140, and a storage unit 150 are connected to the control unit 100 via a bus.
  • the control unit 100 is a functional unit for controlling the MME 10.
  • the control unit 100 implements various functions by reading and executing various programs stored in the storage unit 150.
  • the transmission / reception unit 110 is a functional unit that is wired to a router or a switch and transmits and receives packets.
  • transmission / reception is performed by Ethernet (registered trademark) or the like generally used as a network connection method.
  • the storage unit 150 is a functional unit in which various programs necessary for the operation of the MME 10 and various data are stored.
  • the storage unit 150 includes, for example, a semiconductor memory, an HDD (Hard Disk Drive), or the like. Further, the storage unit 150 stores a HeNB management table 152, an LHN / CSG management table 154, a SIPTO @ LN permission information management table 156, and an APN management table 158.
  • HeNB30 a HeNB identifier
  • LGW20 an LGW identifier
  • the LGW 20 managed here is an LGW capable of SIPTO @ LN.
  • the HeNB identifier may be information indicating the position of the HeNB where the UE is located, and may be managed by a cell identifier, a CSG identifier, or an HeNB IP address.
  • a cell identifier is an identifier which identifies the radio
  • the CSG identifier is an identifier for performing authentication on the network side in order for the UE 50 to connect the HeNB 30.
  • the LGW identifier may be information that can identify the LGW, and may be managed by an IP address.
  • APN identifiers that can be used in the LGW 20 are associated and managed. This indicates that the MME 10 can select the LGW 20 and establish a PDN connection to the UE 50 that connects using the APN identifier.
  • APN Access Point Name
  • APN indicates connection destination information for accessing the service.
  • APN1 is an APN indicating offload (SIPTO @ LN) via the local network. That is, the MME 10 manages that the LGW 20 to which the HeNB 30 is connected can be offloaded (SIPTO @ LN) via the local network, and can establish a PDN connection via the local network when the UE 50 is in the HeNB 30. Is shown.
  • the MME 10 may manage not only that offload (SIPTO @ LN) is possible via a local network but also that it is not possible to offload (SIPTO @ LN) via a local network. In other words, offload permission information via the local network may be managed.
  • the APN identifier may be permission information for permitting a specific service in the LGW 20, and when indicating permission information for an offload service via the local network, the SIPTO @ LN flag (SIPTO @ LN is permitted or (Information indicating non-permission).
  • the LGW 20 may manage that the SIPTO @ LN can be used functionally (Capability).
  • MME10 may manage SIPTO @ LN Capability according to SIPTO @ LN Capability ON / OFF information of LGW20. good.
  • the APN identifier and SIPTO @ LN permission information associated with the LGW 20 shown here are second permission information for convenience of explanation.
  • the LHN / CSG management table 154 includes an LHN identifier (for example, “LHN1”), a CSG identifier (for example, “CSG1”), an LGW identifier (for example, “LGW20”), and the like. , And a HeNB identifier (for example, “HeNB30”).
  • LHN1 for example, “LHN1”
  • CSG1 for example, “CSG1”
  • LGW identifier for example, “LGW20”
  • HeNB30 for example, “HeNB30”.
  • LHN1, CSG1, LGW20, and HeNB30 are managed, indicating that LGW20 and HeNB30 belong to LHN1 and CSG1.
  • the LHN (Local HeNB Network) identifier is managed by the LHN / CSG management table 154 in association with the LGW 20 by being transmitted from the HeNB 30.
  • the LHN (Local HeNB Network) identifier is an identifier for managing a plurality of HeNBs.
  • MME10 manages HeNB which belongs to the same home network using a LHN identifier.
  • the CSG (Closed Subscriber Group) identifier is managed in association with the HeNB 30.
  • the MME 10 manages the HeNB to which the UE 50 is connectable by authenticating the CSG identifier included in the PDN connection request.
  • MME10 can manage several HeNB using a CSG identifier.
  • the HeNB identifier may be information indicating the position of the HeNB where the UE is located, and may be managed by a cell identifier, a CSG identifier, or an HeNB IP address.
  • the SIPTO @ LN permission information management table 156 includes, as shown in FIG. 3 (c), mobile communication carrier permission information, broadband carrier permission information, UE permission information, and a UE identifier. Is done.
  • the UE identifier “UE50” the permission information “permitted” of the mobile carrier, the permission information “permitted” of the broadband operator, and the permission information “permitted” of the UE are managed. Since the permission information, the permission information of the broadband operator, and the permission information of the UE are permitted, the UE 50 can perform SIPTO @ LN.
  • the UE 50 cannot perform SIPTO @ LN.
  • the APN management table 158 is subscriber information managed for each UE. As shown in FIG. 3D, the APN identifier (for example, “APN1”) and permission information (for example, “SIPTO @ LN allowed only only”). )) And the UE identifier (UE50) are managed (stored), and by managing the permission information for each APN and for each UE, a service that can be used for each UE can be permitted.
  • the permission information shown here is the first permission information for convenience of explanation.
  • the APN (Access Point Name) identifier is connection destination information in the mobile communication carrier managed as shown in FIG.
  • the UE 50 needs to establish a connection destination for each service (PDN) prior to communication.
  • the APN identifier is notified to the MME 10 in the PDN connection establishment procedure. Thereby, the connection destination of PDN can be established.
  • the UE 50 detects that the PDN connection corresponding to the APN identifier can be established.
  • APN1 is associated with the UE identifier (UE50) and the first permission information “SIPTO @ LN allowed only”, and APN1 manages the permission information of SIPTO @ LN for UE50. , UE50 can use SIPTO @ LN in APN1.
  • the permission information “permission” of the mobile communication carrier, the permission information “permission” of the broadband network operator, and the permission information “permission” of the UE 50 are managed as, for example, “SIPTO @ LN allowed only” as permission information in the APN management table 158, and the UE 50 associated with the APN identifier and the first permission information.
  • the UE 50 can use SIPTO @ LN.
  • the SIPTO @ LN permission information management table 156 “not permitted (not permitted)” in any of the permission information of the mobile communication carrier, the permission information of the broadband network operator, and the permission information of the UE 50.
  • the permission information in the APN management table 158 cannot be managed as “SIPTO @ LN allowed only”, and the UE 50 associated with the APN identifier and the first permission information uses SIPTO @ LN. I can't do it.
  • the first permission information may be “SIPTO allowed included SIPTO @ LN” instead of “SIPTO @ LN allowed only”, “LIPA allowed” or “LIPA conditional”. There may be.
  • LGW 20 capable of SIPTO @ LN cannot always use LIPA. Also, it is indicated that SIPTO @ LN is not always available in LIPA capable LIP20. Furthermore, the LGW 20 may be able to use both SIPTO @ LN and LIPA.
  • the UE 50 can establish a PDN connection for an APN identifier in which permission information of the mobile communication carrier is not managed, such as APN2.
  • the LGW 20 is an LGW 20 that can perform SIPTO @ LN.
  • a broadband network interface unit 220, a home network interface unit 230, and a storage unit 250 are connected to the control unit 200 via a bus.
  • the control unit 200 is a functional unit for controlling the entire LGW 20.
  • the control unit 200 implements various functions by reading and executing various programs stored in the storage unit 250, and includes, for example, a CPU (Central Process Unit).
  • a CPU Central Process Unit
  • the broadband network interface unit 220 is a network interface unit connected to the broadband network 7.
  • the broadband network interface unit 220 receives a packet from the broadband network 7 and transfers it to the home network interface unit 230.
  • the broadband network interface unit 220 receives the packet from the home network interface unit 230 and transfers the packet to the broadband network 7.
  • the home network interface unit 230 is a network interface unit connected to the home network 5.
  • the home network interface unit 230 receives a packet from the home network 5 and transfers the packet to the broadband network interface unit 220.
  • the home network interface unit 230 receives a packet from the broadband network interface unit 220 and transfers the packet to the home network 5.
  • the storage unit 250 is a functional unit that stores various programs and various data necessary for the operation of the LGW 20.
  • the storage unit 250 includes, for example, a semiconductor memory, an HDD (Hard Disk Drive), or the like.
  • the storage unit 250 stores an LGW identifier 252 and a HeNB identifier 254.
  • FIG. 5 shows an example of the LGW identifier 252 and the HeNB identifier 254.
  • the LGW identifier 252 manages the LGW 20 (the identification information of the LGW 20 is stored).
  • the LGW identifier 252 may be set in advance, or may be notified from a broadband network operator, a mobile communication operator, or the HeNB 30. Also, management may be performed using an IP address.
  • HeNB30 is managed by HeNB identifier 256 (the identification information of HeNB30 is memorize
  • the HeNB identifier may be information indicating the position of the HeNB where the UE is located, and may be managed by a cell identifier, a CSG identifier, or an HeNB IP address.
  • FIG. 6 shows a configuration of the HeNB 30 in the present embodiment.
  • an LTE base station unit 310 a home network interface unit 320, and a storage unit 350 are connected to the control unit 300 via a bus.
  • the control unit 300 is a functional unit for controlling the entire HeNB 30.
  • the control unit 300 realizes various functions by reading and executing various programs stored in the storage unit 350, and includes, for example, a CPU (Central Process Unit).
  • a CPU Central Process Unit
  • the LTE base station unit 310 functions as an E-UTRAN base station and is a functional unit for accommodating UEs.
  • An antenna 312 is connected to the LTE base station unit 310.
  • the home network interface unit 320 is a functional unit that receives a packet from the home network 5, rewrites the destination IP address, and transfers the packet to the LTE base station unit 310.
  • the home network interface unit 320 transfers the packet received from the LTE base station unit 310.
  • the storage unit 350 is a functional unit that stores programs and data necessary for various operations of the HeNB 30, and stores a HeNB identifier 352, an LGW identifier 354, LHN management information 356, and an APN identifier 358.
  • FIG. 7 shows a HeNB identifier 352 (FIG. 7A), an LGW identifier 354 (FIG. 7B), LHN management information 356 (FIG. 7C), and an APN identifier 358 (FIG. 7D). .
  • the HeNB 30 is managed by the HeNB identifier 352.
  • the HeNB identifier 352 may be set in advance, or may be notified from a broadband network operator, a mobile communication operator, or the LGW 20.
  • the HeNB identifier may be information indicating the position of the HeNB where the UE is located, and may be managed by a cell identifier, a CSG identifier, or an HeNB IP address.
  • the LGW identifier connected to the HeNB 30 is managed by the LGW identifier 354.
  • the LGW identifier may be set in advance, or may be notified from a broadband network operator, a mobile communication operator, or the LGW 20.
  • An IP address may be used.
  • the HeNB identifier (HeNB30) may be an IP address indicating the HeNB or a cell ID for identifying the base station apparatus.
  • the LHN management information 356 is management information (LHN management information) for managing a Local HeNB Network (LHN) as shown in FIG. 7C, and the HeNB 30 and the LGW 20 belonging to the same LHN have the same LHN management information. Is assigned. Note that the LHN management information is manually set in the HeNB 30 by the mobile communication carrier.
  • LHN management information is manually set in the HeNB 30 by the mobile communication carrier.
  • the APN identifier 358 manages an identifier for identifying the APN.
  • APN indicates connection destination information for accessing the service.
  • the MME 10 notifies the UE 50 of the APN identifier via the HeNB 30, the UE 50 detects that the PDN connection corresponding to the APN 1 can be established.
  • the HeNB 30 transmits an APN identifier from the MME 10 to the UE 50, the HeNB 30 may manage the APN identifier from the MME 10 in the APN identifier 358.
  • the APN identifier is associated with the permission information of the mobile carrier, and for example, “SIPTO @ LN” can be used in the APN identifier associated with the permission information “SIPTO @ LN allowed only”. Is shown.
  • there are a plurality of types of permission information of the mobile carrier and it may be “SIPTO allowed included SIPTO @ LN” instead of “SIPTO @ LN allowed only”, and “LIPA allowed” or “LIPA conditional”. It may be.
  • LGW 20 capable of SIPTO @ LN cannot always use LIPA.
  • SIPTO @ LN cannot always be used in LIP20 capable of LIPA.
  • the LGW 20 may be able to use both SIPTO @ LN and LIPA.
  • the APN identifier may be permission information for permitting a specific service.
  • the SIPTO @ LN flag SIPTO @ LN Information indicating permission or non-permission.
  • FIG. 8 shows a configuration of the UE 50 in the present embodiment.
  • an LTE interface unit 510 and a storage unit 550 are connected to the control unit 500 via a bus.
  • the control unit 500 is a functional unit for controlling the entire UE 50.
  • the control unit 500 realizes various functions by reading and executing various programs stored in the storage unit 550, and is configured by, for example, a CPU (Central Process Unit).
  • a CPU Central Process Unit
  • the LTE interface unit 510 functions as an E-UTRAN base station and is a functional unit for accommodating UEs.
  • an antenna 512 is connected to the LTE interface unit 510.
  • the storage unit 550 is a functional unit that stores programs, data, and the like necessary for various operations of the UE 50, and stores a CSG identifier 552 and an APN management table 554.
  • FIG. 9 shows a CSG identifier 552 (FIG. 9A) and an APN management table 554 (FIGS. 9B and 9C).
  • the CSG identifier 552 is managed by the CSG identifier of the HeNB 30 (for example, “CSG identifier 1”).
  • CSG identifier 1 the CSG identifier of HeNB 30
  • UE50 can connect to HeNB30.
  • the APN management table 554 includes an APN identifier (for example, “APN1”) and a HeNB identifier (for example, “HeNB30”) to be included when the UE 50 transmits a PDN connection request. ) And are managed.
  • APN indicates connection destination information for accessing the service.
  • the UE 50 transmits a PDN connection request using APN1.
  • the HeNB 30 notifies the UE 50 of the APN 1. Furthermore, as a method for detecting that the UE 50 can use the APN 1, there is a method in which the UE 50 manages in advance that the APN 1 can be used in the HeNB 30.
  • the UE 50 sets “blank” in the HeNB identifier in the APN1, and when the HeNB identifier is not managed in the APN1, the UE 50 uses the APN1 to request a PDN connection. Cannot be sent.
  • the UE 50 manages “HeNB30” as the HeNB identifier in the APN1, and the UE50 transmits the PDN connection request using the APN1 when the UE 50 is in the HeNB 30. be able to.
  • a PDN connection can be requested regardless of the HeNB in which the UE 50 is located.
  • the HeNB identifier may be information indicating the position of the HeNB in which the UE is located, and may be managed by a cell identifier, a CSG identifier, or an HeNB IP address.
  • the APN identifier may be permission information for permitting a specific service.
  • the SIPTO @ LN flag SIPTO @ LN is permitted or not permitted. Information).
  • the MME 10 manages offload permission information via the local network for the UE 50 and offload permission information via the local network for the LGW 20, and transmits the offload permission information via the local network to the UE 50 via the HeNB 30.
  • the UE 50 requests the HeNB 30 to establish a PDN connection for offloading via the local network based on permission information for offloading via the local network.
  • the fact that the MME 10 notifies the offload permission information via the local network is that the MME 10 detects that the UE 50 permits offload (SIPTO @ LN) via the local network, and the LGW 20 It is detected that offloading via the network (SIPTO @ LN) is possible, and the UE 50 indicates that offloading via the local network (SIPTO @ LN) is possible.
  • MME10 does not detect that SIPTO @ LN is permitted in UE50, only LGW20 detects that SIPTO @ LN is possible, and indicates that UE50 is capable of SIPTO @ LN in HeNB30. May be.
  • “blank” is set in the HeNB identifier in the APN 1 for the UE 50, and the UE 50 cannot transmit the PDN connection request using the APN 1.
  • the APN identifier indicates connection destination information for accessing the service.
  • the APN identifier may be permission information for permitting a specific service.
  • the SIPTO @ LN flag SIPTO @ LN is permitted or not permitted. (Information indicating permission).
  • the HeNB identifier may be information indicating the position of the HeNB where the UE is located, and may be managed by a cell identifier, a CSG identifier, or an HeNB IP address.
  • the MME 10 manages the first permission information for offloading via the local network of the UE 50 and the second permission information for offloading via the local network of the LGW 20, and the first permission information and the second permission information.
  • the UE 50 uses the offload permission information via the local network to perform offload via the local network at the HeNB 30. A request for establishing a PDN connection can be suppressed.
  • the MME 10 detects that the UE 50 is located in the HeNB 30.
  • the HeNB 30 is connected to the LGW 20 capable of offloading (SIPTO @ LN) via the local network, and the MME 10 detects in advance that the LGW 20 capable of SIPTO @ LN is connected to the HeNB 30.
  • SIPTO @ LN the LGW 20 capable of offloading
  • the MME 10 includes a method for detecting by a PDN connection request transmitted by the UE 50.
  • the UE 50 establishes a PDN connection different from SIPTO @ LN. For example, it is possible to establish a PDN connection from the UE 50 via the HeNB 30 and the SGW 40 to the mobile communication carrier network up to the PGW 60.
  • the APN identifier included in the PDN connection request transmitted by the UE 50 need not be APN1, but may be APN2 or APN3.
  • APN2 and APN3 can establish services different from SIPTO @ LN, such as PDN connection via a mobile carrier network or SIPTO @ RN PDN connection.
  • the UE 50 makes a PDN connection request including an APN identifier different from the APN 1 capable of SIPTO @ LN.
  • the APN identifier indicates connection destination information for accessing the service.
  • the MME 10 detects that the PDN connection request has been received via the HeNB 30, and the MME 10 detects that the UE 50 is located in the HeNB 30.
  • the HeNB 30 is connected to the LGW 20 capable of SIPTO @ LN.
  • the UE 50 transmits a PDN connection request including the APN identifier different from the APN 1 to the MME 10 (S1000).
  • the APN identifier indicates connection destination information for accessing the service.
  • the APN identifier included here may be, for example, APN 2 that can establish a PDN connection to the mobile operator network.
  • the PDN connection request is transmitted via the HeNB 30.
  • the MME 10 that has received the PDN connection request performs GW selection (S1002).
  • the MME 10 first confirms the APN identifier included in the PDN connection request.
  • the MME 10 confirms the permission information set in the APN identifier.
  • the MME 10 determines to establish a PDN connection in the mobile carrier network using the permission information set in the APN identifier.
  • the MME 10 selects a PGW 60 that can establish a PDN connection in the mobile communication operator network.
  • the MME 10 detects that the UE 50 is capable of SIPTO @ LN (S1004).
  • the MME 10 detects that the UE 50 can be off-loaded via the local network (SIPTO @ LN), and the LGW 20 to which the HeNB 30 where the UE 50 is located can be off-loaded (SIPTO @ LN). By doing so, it can be detected.
  • the MME 10 detects that SIPTO @ LN is possible in the UE 50 (S1502).
  • the MME 10 associates the APN identifier (APN1), the first permission information “SIPTO @ LN allowed only”, and the UE identifier (UE50) in the APN management table 158 (FIG. 3 (d)). This can be confirmed, and it is possible to detect that SIPTO @ LN is possible in UE50 (that SIPTO @ LN is permitted for UE50).
  • the APN identifier indicates connection destination information for accessing the service.
  • the SIPTO @ LN permission information management table 156 the permission information “permission” of the mobile communication carrier, the permission information “permission” of the broadband network operator, and the permission information “permission” of the UE 50 (user) are respectively managed.
  • the MME 10 can manage, for example, “SIPTO @ LN allowed only” as the first permission information in the APN management table 158, and the UE 50 can use SIPTO @ LN.
  • the SIPTO @ LN permission information management table 156 “not permitted” is managed in any of permission information in the mobile communication carrier, permission information of the broadband network operator, and permission information of the UE 50 (user).
  • the first permission information in the APN management table 158 cannot be managed as “SIPTO @ LN allowed only”, and the SIPTO @ LN cannot be used.
  • UE50 detected that SIPTO @ LN was permitted using the APN identifier it should just be information which shows permission of SIPTO @ LN of UE.
  • the MME 10 determines not to notify that the SIPTO @ LN is possible (S1512).
  • the MME 10 that has detected that the UE 50 is capable of SIPTO @ LN confirms the HeNB 30 (S1504). By confirming HeNB30 which passed when UE50 transmitted the PDN connection request
  • the MME 10 extracts the LGW from the HeNB 30 (S1506).
  • the MME 10 extracts the LGW 20 from the HeNB 30 confirmed in S1504 using the LHN / CSG management table 154.
  • it may be detected that the UE 50 can connect to the HeNB 30 or the LGW 20 based on the LHN identifier or the CSG identifier.
  • the MME 10 detects that the LGW 20 extracted in S1506 is SIPTO @ LN (S1508).
  • the MME 10 detects that the LGW 20 is capable of SIPTO @ LN in the HeNB management table 152 and detects that the LGW 20 is capable of SIPTO @ LN based on the APN identifier (second permission information) associated with the LGW identifier. can do.
  • the APN identifier indicates connection destination information for accessing the service.
  • the LGW 20 is associated with the APN 1, a PDN connection corresponding to the APN 1 can be established.
  • APN1 may be an APN identifier that can use only SIPTO @ LN. I understand. That is, the LGW 20 can detect that SIPTO @ LN is possible. When the LGW 20 supports not only SIPTO @ LN but also other services, not only SIPTO @ LN but also other services may be detected.
  • the APN identifier may be permission information (second permission information) for permitting a specific service.
  • the SIPTO @ LN flag SIPTO @LN may be permitted or not permitted.
  • the MME 10 may use an LHN identifier or a CSG identifier in the LHN / CSG management table 154. For example, if the LHN identifier is managed in association with information indicating that SIPTO @ LN is possible, and the LHN to which the LGW 20 belongs is SIPTO @ LN is possible, the SIPTO @ LN is possible. Can be detected. Further, for example, a CSG identifier and information indicating that SIPTO @ LN is possible are managed in association with each other, and in the CSG to which the HeNB 30 belongs, when SIPTO @ LN is possible, it is detected that SIPTO @ LN is possible. can do.
  • the MME 10 that has not detected that SIPTO @ LN is possible in the extracted LGW 20 determines not to notify that SIPTO @ LN is possible (S1512). In addition, when not notifying that SIPTO @ LN is possible, it is not necessary to include permission information indicating that SIPTO @ LN is possible in subsequent procedures.
  • the MME 10 that has detected that SIPTO @ LN is possible in the extracted LGW 20 determines to notify that SIPTO @ LN is possible (1510).
  • the MME 10 detects that the UE 50 is capable of offloading (SIPTO @ LN) via the local network and permits the SIP 50 for the UE 50 (first permission information). Can be detected by detecting that offload (SIPTO @ LN) via the local network is possible in the LGW 20 to which the HeNB 30 in which the user is located is connected (second permission information).
  • the first permission information for the UE 50 is detected, and the second permission information for the LGW 20 is detected, so that the permission information of SIPTO @ LN based on the first permission information and the second permission information in the UE 50 is obtained. You can be notified.
  • SIPTO @ LN is possible but also that SIPTO @ LN is not possible may be notified. That is, it may be notified whether offload is possible via the local network.
  • the MME 10 may detect an LGW 20 that can be offloaded (SIPTO @ LN) via the local network.
  • SIPTO @ LN an LGW 20 that can be offloaded
  • the MME 10 has detected that the UE 50 is capable of SIPTO @ LN (S1502).
  • the MME 10 does not detect that the UE 50 is capable of SIPTO @ LN. It is possible to detect that @LN is possible and to notify that SIPTO @ LN is possible.
  • MME 10 since MME 10 does not detect that SIPTO @ LN for UE 50 is possible (first permission information), MME 10 detects the first permission information of SIPTO @ LN for UE 50 in MME 10. There is an advantage that processing load is not required.
  • the MME 10 confirms the HeNB 30 (S1604). By confirming HeNB30 which passed when UE50 transmitted the PDN connection request
  • the MME 10 extracts the LGW from the HeNB 30 (S1606). Using the LHN / CSG management table 154, the MME 10 extracts the LGW 20 from the HeNB 30 confirmed in S1604. At this time, it may be detected that the UE 50 can connect to the HeNB 30 or the LGW 20 based on the LHN identifier or the CSG identifier.
  • the MME 10 detects that the LGW 20 extracted in S1606 is SIPTO @ LN (S1608).
  • the MME 10 detects that the LGW 20 is capable of SIPTO @ LN in the HeNB management table 152 and detects that the LGW 20 is capable of SIPTO @ LN based on the APN identifier (second permission information) associated with the LGW identifier. can do.
  • the APN identifier indicates connection destination information for accessing the service.
  • the LGW 20 is associated with the APN 1, a PDN connection corresponding to the APN 1 can be established.
  • APN1 is set to “SIPTO @ LN allowed only” in the APN management table 158, it can be seen that APN1 is an APN identifier that can use only SIPTO @ LN. That is, the LGW 20 can detect that SIPTO @ LN is possible. When the LGW 20 supports not only SIPTO @ LN but also other services, not only SIPTO @ LN but also other services may be detected.
  • the APN identifier may be permission information (second permission information) for permitting a specific service.
  • the SIPTO @ LN flag SIPTO @LN may be permitted or not permitted.
  • the MME 10 may use an LHN identifier or a CSG identifier in the LHN / CSG management table 154. For example, if the LHN identifier is managed in association with information indicating that SIPTO @ LN is possible, and the LHN to which the LGW 20 belongs is SIPTO @ LN is possible, the SIPTO @ LN is possible. Can be detected.
  • a CSG identifier and information indicating that SIPTO @ LN is possible are managed in association with each other, and in the CSG to which the HeNB 30 belongs, when SIPTO @ LN is possible, it is detected that SIPTO @ LN is possible. can do.
  • the MME 10 that has not detected that SIPTO @ LN is possible in the extracted LGW 20 determines not to notify that SIPTO @ LN is possible (S1612). In addition, when not notifying that SIPTO @ LN is possible, it is not necessary to include permission information indicating that SIPTO @ LN is possible in subsequent procedures.
  • the MME 10 that has detected that SIPTO @ LN is possible in the extracted LGW 20 determines to notify that SIPTO @ LN is possible (S1610).
  • the MME 10 can be offloaded (SIPTO @ LN) via the local network at the UE 50, and can be offloaded (SIPTO @ LN) via the local network at the LGW 20 to which the HeNB 30 where the UE 50 is located is connected. It can be detected by detecting that it is (second permission information). That is, by detecting the second permission information for the LGW 20, the UE 50 can notify the permission information of SIPTO @ LN.
  • SIPTO @ LN is possible but also that SIPTO @ LN is not possible may be notified. That is, it may be notified whether offload is possible via the local network.
  • the MME 10 transmits a session generation request to the SGW 40 (S1006).
  • the SGW 40 that has received the session generation request transmits a session generation request for generating a session between the PGW 60 and the SGW 40 to the PGW 60 (S1008).
  • the PGW 60 that has received the session generation request generates a session between the PGW 60 and the SGW 40, and transmits the session generation response to the SGW 40 (S1010).
  • the SGW 40 that has received the session creation response from the PGW 60 transmits the session creation response to the MME 10 (S1012).
  • the MME 10 that has received the session generation response from the SGW 40 transmits a bearer setting request to the HeNB 30 (S1014).
  • the MME 10 uses SIPTO @ LN permission information indicating that SIPTO @ LN is possible in the UE 50 detected in S1004 (SIPTO @ LN permission information based on the first permission information and the second permission information). Or SIPTO @ LN second permission information).
  • SIPTO @ LN permission information for the UE may be an APN identifier (APN1).
  • APN identifier indicates connection destination information for accessing the service.
  • the APN identifier (APN1) is managed together with the permission information “SIPTO @ LN allowed only” and the UE identifier “UE50” in the APN management table 158 of the MME 10 (FIG. 3D).
  • permission information such as SIPTO allowed included SIPTO @ LN and SIPTO @ LN allowed only can be set as the permission information set in the APN identifier.
  • SIPTO allowed included SIPTO @ LN is set
  • SIPTO @ In addition to LN SIPTO @ RN can also be used, and SIPTO @ LN only indicates that only SIPTO @ LN can be used.
  • the APN identifier may be permission information for permitting a specific service.
  • the SIPTO @ LN flag SIPTO @ LN is permitted or not permitted. Information). Moreover, you may notify the information which shows that SIPTO @ LN is not possible.
  • the LGW 20 supports not only SIPTO @ LN but also other services, not only SIPTO @ LN but also other services may be notified.
  • HeNB30 which received the bearer setting request
  • the HeNB 30 is information indicating that the UE 50 notified from the MME 10 is capable of SIPTO @ LN (SIPTO @ LN permission information or SIPTO @ LN first information based on the first permission information and the second permission information). 2 permission information).
  • the permission information of SIPTO @ LN with respect to UE50 may notify an APN identifier (APN1).
  • the UE 50 manages the HeNB identifier (HeNB30) of the HeNB that transmitted the RRC connection reconfiguration in association with the APN identifier (APN1).
  • the APN identifier indicates connection destination information for accessing the service.
  • the HeNB identifier managed in FIG. 9C may be information indicating the position of the HeNB where the UE is located, and may be managed by a cell identifier, a CSG identifier, or an HeNB IP address.
  • the APN identifier associated with the HeNB identifier may be permission information for permitting a specific service.
  • SIPTO @ It may be an LN flag (information indicating that SIPTO @ LN is permitted or not permitted).
  • permission information such as SIPTO allowed included SIPTO @ LN and SIPTO @ LN allowed only can be set as the permission information set in the APN identifier.
  • SIPTO @ LN In the APN identifier in which SIPTO allowed included SIPTO @ LN is set, SIPTO @ LN
  • SIPTO @ RN can also be used, and SIPTO @ LN only indicates that only SIPTO @ LN can be used.
  • the UE 50 that has received the RRC connection resetting from the HeNB 30 resets the RRC connection in the HeNB 30 that has transmitted the RRC connection resetting.
  • UE50 which completed RRC connection reset reset transmits RRC connection reset completion to HeNB30 (S1018).
  • HeNB30 which received the completion of RRC connection reset transmits a bearer setting response to MME10 (S1020).
  • the UE 50 performs direct communication in order to confirm whether communication is possible (S1022).
  • the HeNB 30 that has received the direct communication transmits a PDN connection completion to the MME 10 (S1024).
  • the MME 10 that has received the PDN connection completion transmits a bearer setting request to the SGW 40 (S1026).
  • it is a message for notifying that the PDN connection is completed between the UE 50 and the PGW 60.
  • the SGW 40 that has received the bearer setting request confirms that the PDN connection is completed between the UE 50 and the PGW 60, and returns a bearer change response to the MME 10 (S1028).
  • the MME detects the first permission information of SIPTO @ LN for the UE 50 and the second permission information of SIPTO @ LN for the LGW 20, and performs offload (SIPTO @ LN) via the local network to the UE 50.
  • the permission information is notified, and the UE can detect that offload (SIPTO @ LN) via the local network is possible.
  • the MME 10 detects the second permission information of SIPTO @ LN for the LGW, notifies the UE 50 of permission information of offload (SIPTO @ LN) via the local network, and the UE performs offload (SIPTO via the local network). @LN) It is possible to detect that it is possible.
  • the UE 50 manages the HeNB identifier (HeNB30) that transmitted the RRC connection reconfiguration in association with the APN identifier (APN1).
  • the APN identifier indicates connection destination information for accessing the service.
  • the UE 50 can transmit a PDN connection using the APN1 in the HeNB 30.
  • the HeNB identifier managed in FIG. 9C may be information indicating the position of the HeNB in which the UE is located, and may be managed by a cell identifier, a CSG identifier, or an HeNB IP address.
  • the APN identifier managed in FIG. 9C may be permission information for permitting a specific service, and when indicating permission information for an offload service via a local network, the SIPTO @ LN flag ( SIPTO @ LN may be permitted or not permitted).
  • SIPTO @ LN is possible but also that SIPTO @ LN is not possible may be notified. That is, it may be notified whether offload is possible via the local network.
  • the UE 50 transmits the RRC connection reconfiguration as illustrated in FIG. 9C.
  • the identifier (HeNB30) may not be managed in association with the APN identifier (APN1).
  • APN APN identifier
  • FIG. 13 shows a procedure for establishing a SIPTO @ LN PDN connection.
  • UE50 which detected that SIPTO @ LN is possible in HeNB30 transmits a PDN connection request
  • the APN 1 is associated with permission information SIPTO @ LN only in the MME 10, and the UE 50 makes a SIPTO @ LN PDN connection request.
  • the MME 10 that has received the PDN connection request detects that SIPTO @ LN is possible in the LGW 20 connected to the HeNB 30 in which the UE 50 is located.
  • the MME 10 searches for the LGW 20 capable of SIPTO @ LN, and determines the LGW 20 as the establishment destination (anchor device) of the SIPTO @ LN PDN connection.
  • the MME 10 that has decided to establish the SIPTO @ LN PDN connection transmits a session generation request to the SGW 40 (S1704).
  • the MME 10 includes the information regarding the LGW 20 and the information regarding the APN 1 as the establishment destination of the PDN connection to the SGW 40.
  • the SGW 40 that has received the session generation request from the MME 10 confirms the LGW 20 that is the establishment destination of the PDN connection. Subsequently, the SGW 40 transmits a session generation request to the LGW 20 which is the establishment destination of the PDN connection (S1706). At this time, the SGW 40 includes information on APN1 in the session generation request.
  • the LGW 20 that has received the session generation request from the SGW 40 determines to establish a PDN connection of the service (SIPTO @ LN) in the APN 1 from the MME 10 using the information regarding the APN 1 included in the session generation request. Moreover, SGW40 determines establishing the PDN connection of UE50 and SIPTO @ LN using the information regarding UE50 contained in the session production
  • the LGW 20 decides to establish a SIPTO @ LN PDN connection with the UE 50, and transmits a session generation response to the SGW 40 (S1708).
  • the SGW 40 confirms that the LGW 20 can establish a PDN connection of SIPTO @ LN with the UE 50 by the session generation response from the LGW 20.
  • the SGW 40 transmits a session generation response to the MME 10 (S1710).
  • the MME 10 confirms that the LGW 20 can establish a PDN connection between the UE 50 and the SIPTO @ LN by the session generation response from the SGW 40.
  • the MME 10 transmits a bearer setting request to the HeNB 30 (S1712).
  • HeNB30 is HeNB in which UE50 exists.
  • the bearer setting request includes information on the UE 50, information on the LGW 20 that is a connection destination of SIPTO @ LN, and information on the APN1.
  • requirement confirms the information regarding UE50 contained in the bearer setting request
  • the RRC connection reconfiguration includes information related to the LGW 20 and information related to the APN1.
  • the UE 50 that has received the RRC connection reset confirms the information on the LGW 20 and the information on the APN 1 and performs RRC connection reset with the HeNB 50 already in the area.
  • the UE 50 confirming that the RRC connection reconfiguration has been completed transmits RRC connection reconfiguration completion to the HeNB 30 (S1716).
  • the HeNB 30 that has received the RRC connection reconfiguration completion confirms that the RRC connection reconfiguration has been completed, and transmits a bearer setting response to the MME 10 (S1718).
  • the UE 50 communicates directly with the HeNB 30 (S1720).
  • HeNB30 confirms that it can communicate directly and transmits PDN connection completion to MME10 (S1722).
  • MME10 which received the PDN connection completion transmits a bearer change request to SGW40 (S1724).
  • SGW40 S1740
  • the SGW 40 sets so as not to set a bearer from the SGW 40, and transmits a bearer change response to the MME 10 (S1726).
  • the HeNB 30 makes a SIPTO @ LN session generation request to the LGW 20 (S1728).
  • the LGW 20 that has received the SIPTO @ LN session generation request establishes a session between the HeNB 30 and the SIPTO @ LN.
  • LGW20 confirms that the session of Hep30 and SIPTO @ LN was established, and transmits a SIPTO @ LN session production
  • the UE 50 can establish a SIPTO @ LN PDN connection.
  • the MME 10 manages the first permission information for offloading via the local network for the UE 50 and the second permission information for offloading via the local network of the LGW 20, and the first permission information and the second permission information are managed. Based on the permission information, the offload permission information via the local network is notified to the UE 50 via the HeNB 30, and the UE 50 uses the offload permission information via the local network to notify the UE 50 of the PDN connection for offload via the local network. Can be requested.
  • the UE can transmit the PDN connection request for starting the PDN connection establishment procedure of SIPTO @ LN only when SIPTO @ LN is possible.
  • the MME 10 manages the first permission information for offloading via the local network of the UE 50 and the second permission information for offloading via the local network of the LGW 20, and the first permission information and the second permission information.
  • the UE 50 notifies the UE 50 via the HeNB 30 of offload permission information via the local network on the basis of the PDN connection for offloading via the local network in the HeNB 30 based on the offload permission information via the local network. It is possible to suppress the request for establishment.
  • the UE prevents the UE from sending a PDN connection request unnecessarily. It is possible to prevent waste of power consumption.
  • the LME only selects the LGW if it can select a SIPTO @ LN capable LGW by sending a SIPTO @ LN PDN connection request only if the UE can establish a SIPTO @ LN PDN connection. It is possible to prevent unnecessary selection of LGW and to prevent the processing load on the MME.
  • the MME increases the signaling for transmitting information indicating that the PDN connection cannot be established by sending the SIPTO @ LN PDN connection request. Can be prevented.
  • permission information such as SIPTO allowed included SIPTO @ LN or SIPTO @ LN allowed only is set as the permission information set in the APN identifier. Is possible.
  • the UE 50 transmits a PDN connection request including an APN identifier different from APN1, but may transmit a PDN connection request including APN1.
  • the APN identifier is connection destination information for accessing the service.
  • APN1 can establish not only SIPTO @ LN but also a PDN connection via the network of the mobile communication carrier.
  • the UE 50 can transmit the PDN connection request including the APN 1 to establish the PDN connection of the mobile communication carrier.
  • the MME 10 manages the first permission information for offloading via the local network of the UE 50 and the second permission information for offloading via the local network of the LGW 20, and the first permission information and the second permission are managed.
  • the UE 50 is notified of offload permission information via the local network to the UE 50 via the HeNB 30 based on the information, and the UE 50 uses the offload permission information via the local network to notify the UE 50 of the PDN connection for offload via the local network. Can be requested.
  • the UE can establish a SIPTO @ LN PDN connection by a PDN connection request by APN1, it can establish a SIPTO @ LN PDN connection, and if it cannot establish a SIPTO @ LN PDN connection, A PDN connection passing through the network of the communication carrier can be established, and the UE can prevent unnecessary transmission of a PDN connection request and waste of power consumption of the UE.
  • the UE can establish a SIPTO @ LN PDN connection by a PDN connection request from APN1, it establishes a SIPTO @ LN PDN connection, and if it cannot establish a SIPTO @ LN PDN connection, mobile communication
  • the MME can select an LGW that can be SIPTO @ LN, select an LGW, and move if it cannot select an LGW that can be SIPTO @ LN
  • a PGW for establishing a PDN connection via a network of a communication carrier it is possible to prevent unnecessary LGW selection and to prevent a processing load from being applied to the MME.
  • the UE when the UE transmits a PDN connection request and can establish a SIPTO @ LN PDN connection, it establishes a SIPTO @ LN PDN connection, and when it cannot establish a SIPTO @ LN PDN connection, mobile communication
  • the MME can prevent an increase in signaling for transmitting information indicating that the PDN connection cannot be established.
  • the MME 10 notifies the UE 50 of the APN identifier to notify that the SIPTO @ LN can be used.
  • the MME 10 is not limited to the APN identifier, and information indicating that the SIPTO @ LN is possible ( Flag) may be notified.
  • the SIPTO @ LN flag is information (ON or OFF) indicating that SIPTO @ LN is available in the HeNB 30 to which the UE 50 is connected as shown in FIG.
  • you may notify a HeNB identifier and a CSG identifier simultaneously with a SIPTO @ LN flag.
  • the SIPTO @ LN flag may not be notified.
  • the MME 10 notifies the UE 50 that SIPTO @ LN is possible, and the UE 50 that is notified that SIPTO @ LN is possible can transmit a PDN connection request.
  • the UE 50 manages the HeNB identifier (HeNB 30) that transmitted the RRC connection reconfiguration in association with the APN1.
  • HeNB 30 HeNB identifier
  • UE50 can transmit a PDN connection using APN1 in HeNB30.
  • the UE 50 may manage the HeNB that can be SIPTO @ LN not only in units of HeNBs but also in units of CSG identifiers or in units of LHN identifiers.
  • the UE 50 may manage the SIPTO @ LN-capable HeNB in advance without notification from the MME 10 so that a PDN connection request can be transmitted regardless of the SIPTO @ LN notification of the MME 10.
  • LGW 20 capable of LIPA cannot always use SIPTO @ LN. Further, it is indicated that LIPA cannot always be used in the LGW 20 capable of SIPTO @ LN. Further, the LGW 20 may be able to use both LIPA and SIPTO @ LN.
  • the MME 10 manages the first permission information for offloading via the local network of the UE 50 and the second permission information for offloading via the local network of the LGW 20, and the first permission information and the second permission information are managed. Based on the permission information, offload permission information via the local network is notified to the UE 50 via the HeNB 30, and the UE 50 uses the offload permission information via the local network to notify the UE 50 of the PDN for offloading via the local network. You can request the establishment of a connection.
  • the UE can transmit the PDN connection request for starting the PDN connection establishment procedure of SIPTO @ LN only when SIPTO @ LN is possible.
  • the UE prevents unnecessary transmission of a PDN connection request, and It is possible to prevent waste of power consumption.
  • the MME can only select an LGW capable of SIPTO @ LN. It is possible to prevent unnecessary selection of LGW and to prevent the processing load on the MME.
  • the MME increases signaling to send information indicating that the PDN connection cannot be established. Can be prevented.
  • the MME detects that SIPTO @ LN is possible. However, in the second embodiment, this is performed by movement of the UE. Using the Tracking Area Update (TAU) request sent from the UE to the MME, the MME detects that offload (SIPTO @ LN) via the local network is possible.
  • TAU Tracking Area Update
  • detecting that SIPTO @ LN can be used means that it is detected that UE50 allows SIPTO @ LN, and SIPTO @ LN is possible in the LGW to which the HeNB where the UE is located is connected. It is that the MME detects something.
  • the MME 10 manages the first permission information for the offload via the local network for the UE 50 and the second permission information for the offload via the local network for the LGW 20, and the first permission information and the second permission information.
  • the UE 50 is notified of the offload permission information via the local network to the UE 50 via the HeNB 30, and the UE 50 determines the PDN connection for offload via the local network at the HeNB 30 based on the offload permission information via the local network. Require establishment.
  • the fact that the MME 10 notifies the offload permission information via the local network is detected that the MME 10 permits the UE 50 to offload (SIPTO @ LN) via the local network, and the LGW 20 Is detected that offload (SIPTO @ LN) via the local network is possible, and indicates that offload (SIPTO @ LN) via the local network is possible in the UE 50.
  • the MME 10 manages the first permission information for offloading via the local network of the UE 50 and the second permission information for offloading via the local network of the LGW 20, and manages the first permission information and the second permission.
  • the UE 50 allows the HeNB 30 to perform offload via the local network according to the offload permission information via the local network. A request for establishing a PDN connection can be suppressed.
  • the MME 10 receives the TAU request transmitted by the UE 50, the MME 10 detects that SIPTO @ LN for the UE 50 is possible (first permission information), and for the LGW 20 to which the HeNB 30 where the UE 50 is located is connected. It is detected that SIPTO @ LN is possible (second permission information), and information indicating that SIPTO @ LN is possible in HeNB 30 is notified to UE 50 using TAU acceptance.
  • the information indicating that SIPTO @ LN is possible may be an APN identifier (APN1).
  • the APN identifier is connection destination information for accessing the service.
  • the information indicating that SIPTO @ LN is possible may be permission information for permitting a specific service.
  • the SIPTO @ LN flag SIPTO @LN may be permitted or not permitted).
  • the MME 10 detects that SIPTO @ LN is possible in the UE 50, and the MME 10 will explain a series of procedures for notifying the UE 50 of information indicating that SIPTO @ LN is possible with reference to FIG.
  • an APN identifier is used as information indicating that the MME 10 is capable of SIPTO @ LN to the UE 50.
  • the APN identifier is connection destination information for accessing the service.
  • the APN identifier used here may be permission information for permitting a specific service.
  • the SIPTO @ LN flag When indicating the permission information of the offload service via the local network, the SIPTO @ LN flag (Allow SIPTO @ LN or (Information indicating non-permission).
  • “blank” is set in the HeNB identifier in the APN 1 for the UE 50, and the UE 50 cannot transmit a PDN connection request using the APN 1.
  • the HeNB identifier in FIG. 9B may be information indicating the position of the HeNB where the UE is located, and may be managed by a cell identifier, a CSG identifier, or an HeNB IP address.
  • the APN identifier in FIG. 9B may be permission information for permitting a specific service.
  • the SIPTO @ LN flag SIPTO @ LN Information indicating permission or non-permission.
  • the mobile communication system in this embodiment can use FIG. 1 demonstrated in 1st Embodiment similarly, the detailed description is abbreviate
  • the MME 10 in the core network 3, the LGW 20 in the home network 5, and the HeNB 30 have the same configurations as those in the first embodiment, and thus detailed description thereof is omitted.
  • UE 50 detects movement and transmits a TAU request to HeNB 30 (S2002). Next, the HeNB 30 transmits a TAU request to the MME 10 (S2004).
  • the MME 10 that has received the TAU request detects that SIPTO @ LN is possible (S2006).
  • S2006 detects that SIPTO @ LN is possible
  • the method described in FIG. 11 or 12 in the first embodiment can be used in the same manner.
  • the MME 10 detects the first permission information of SIPTO @ LN to the UE 50 that the UE 50 can be offloaded via the local network (SIPTO @ LN), and the HeNB 30 where the UE 50 is located is connected. By detecting offload (SIPTO @ LN) second permission information via the local network for the LGW 20 to be detected. Thereby, MME10 can transmit the permission information of SIPTO @ LN based on the 1st permission information and the 2nd permission information.
  • the MME 10 indicates that the offload (SIPTO @ LN) via the local network is possible in the UE 50, and the permission information (SIPTO @ LN) via the local network for the LGW 20 to which the HeNB 30 where the UE 50 is located is connected. It can be detected by detecting the second permission information. Thereby, MME10 can transmit the permission information of SIPTO @ LN.
  • the MME 10 transmits a session generation request to the SGW 40 (S2008).
  • SGW40 which received the session production
  • the PGW 60 transmits a bearer change response to the SGW 40 (S2012).
  • SGW30 which received the session production
  • the MME 10 that has received the session generation response from the SGW 40 transmits a TAU (Tracking Area Update) acceptance to the UE 50 (S2016).
  • the MME 10 includes SIPTO @ LN permission information as information indicating that SIPTO @ LN is possible based on the first permission information and the second permission information detected in S2006.
  • the APN identifier is connection destination information for accessing the service.
  • APN1 is managed together with the permission information “SIPTO @ LN allowed only” and the UE identifier “UE50” in the APN management table 158 of the MME 10 (FIG. 3 (d)).
  • the permission information set in the APN identifier can be set as SIPTO allowed included SIPTO @ LN or SIPTO @ LN allowed only, and in the APN identifier with SIPTO allowed SIPTO @ LN set, SIPTO @ LN
  • SIPTO @ RN can also be used, and SIPTO @ LN only indicates that only SIPTO @ LN can be used. Moreover, you may notify the information which shows that SIPTO @ LN is not possible.
  • the SIPTO @ LN permission information may be permission information for permitting a specific service.
  • the SIPTO @ LN flag SIPTO @ LN is permitted.
  • information indicating non-permission information indicating non-permission
  • the LGW 20 supports not only SIPTO @ LN but also other services, not only SIPTO @ LN but also other services may be notified.
  • the UE 50 that has received the TAU acceptance transmits the SIPTO @ LN permission information (the SIPTO @ LN permission information or the SIPTO @ LN second information based on the first permission information and the second permission information) included in the TAU acceptance. ) Is detected and the HeNB 30 detects that SIPTO @ LN is possible.
  • UE50 manages in association with the fact that SIPTO @ LN is possible in HeNB30.
  • APN identifier APN1
  • the UE 50 manages the HeNB identifier (HeNB30) that transmitted the TAU acceptance in association with the APN identifier (APN1).
  • HeNB30 HeNB identifier
  • APN1 and HeNB30 can transmit a PDN connection using APN1 in HeNB30.
  • the HeNB identifier included in FIG. 9C may be information indicating the position of the HeNB where the UE is located, and may be managed by a cell identifier, a CSG identifier, or an HeNB IP address. Further, the APN identifier may be permission information for permitting a specific service. When indicating the permission information of the offload service via the local network, the SIPTO @ LN flag (SIPTO @ LN is permitted or not permitted). Information).
  • the UE 50 can transmit a PDN connection request without notification from the MME 10.
  • the UE 50 may manage not only in units of HeNBs but also in units of CSG identifiers or in units of LHN identifiers in the management of HeNBs capable of SIPTO @ LN.
  • the UE 50 may manage the SIPTO @ LN-capable HeNB in advance without notification from the MME 10 so that a PDN connection request can be transmitted regardless of the SIPTO @ LN notification of the MME 10.
  • the UE 50 transmits TAU completion to the MME 10 (S2018). Thereby, UE50 can confirm having notified the position of UE50 to MME10, and can show to MME10 that the TAU procedure was completed.
  • the MME 10 manages the first permission information for offloading via the local network for the UE 50 and the second permission information for offloading via the local network for the LGW 20, and the first permission information and the first permission information
  • the UE 50 is notified of off-load permission information via the local network to the UE 50 via the HeNB 30 based on the permission information of No. 2, and the UE 50 uses the off-load permission information via the local network for off-loading via the local network.
  • the establishment of a PDN connection can be requested.
  • the MME 10 manages the second permission information for offloading via the local network to the LGW 20 and notifies the UE50 of the second permission information for offloading via the local network via the HeNB 30. From the offload permission information, the HeNB 30 can request establishment of a PDN connection for offloading via the local network.
  • the UE can transmit the PDN connection request for starting the PDN connection establishment procedure of SIPTO @ LN only when SIPTO @ LN is possible.
  • the UE 50 manages the HeNB identifier (HeNB30) that transmitted the TAU acceptance in association with the APN identifier (APN1).
  • the UE 50 can transmit a PDN connection using the APN1 in the HeNB 30.
  • the APN identifier is connection destination information for accessing the service.
  • the UE is able to offload (SIPTO @ LN) via the local network for the PDN connection request for starting the SIPTO @ LN PDN connection establishment procedure using APN1, the UE is in the HeNB 30. Can only send).
  • the HeNB identifier managed in FIG. 9C may be information indicating the position of the HeNB where the UE is located, and may be managed by a cell identifier, a CSG identifier, or an HeNB IP address.
  • the APN identifier managed in FIG. 9C may be permission information for permitting a specific service, and when indicating permission information for an offload service via a local network, the SIPTO @ LN flag ( SIPTO @ LN may be permitted or not permitted).
  • SIPTO @ LN is possible but also that SIPTO @ LN is not possible may be notified. That is, it may be notified whether offload is possible via the local network.
  • the UE 50 transmits the RRC connection reconfiguration as illustrated in FIG. 9C.
  • the identifier (HeNB30) may not be managed in association with the APN identifier (APN1).
  • APN1 APN identifier
  • the UE 50 that has detected that SIPTO @ LN is possible can similarly use the procedure of FIG. 13 described in the first embodiment as a procedure for establishing a SIPTO @ LN PDN connection.
  • the MME 10 manages the first permission information for offloading via the local network for the UE 50 and the second permission information for offloading via the local network for the LGW 20, and the first permission information and the second permission are managed.
  • the UE 50 is notified of offload permission information via the local network to the UE 50 via the HeNB 30 based on the information, and the UE 50 uses the offload permission information via the local network to notify the UE 50 of the PDN connection for offload via the local network. Can be requested. Thereby, UE can transmit the PDN connection request
  • the MME 10 manages the first permission information for offloading via the local network for the UE 50 and the second permission information for offloading via the local network for the LGW 20, and the first permission information and the second permission are managed.
  • the UE 50 allows the HeNB 30 to perform offload via the local network according to the offload permission information via the local network. A request for establishing a PDN connection can be suppressed.
  • the UE prevents unnecessary transmission of a PDN connection request and It is possible to prevent waste of power consumption.
  • the LME only selects the LGW if it can select a SIPTO @ LN capable LGW by sending a SIPTO @ LN PDN connection request only if the UE can establish a SIPTO @ LN PDN connection. It is possible to prevent unnecessary selection of LGW and to prevent the processing load on the MME.
  • the MME transmits signaling information for transmitting information indicating that the PDN connection cannot be established by sending a SIPTO @ LN PDN connection request. An increase can be prevented.
  • permission information such as SIPTO allowed included SIPTO @ LN or SIPTO @ LN allowed only is set as the permission information set in the APN identifier. Is possible.
  • the information transmitted from the Source HeNB to the MME detects that the SIP 50 permits the SIPTO @ LN, and the Target HeNB can be offloaded (SIPTO @ LN) via the local network. And the MME notifies the UE that the target HeNB can be offloaded (SIPTO @ LN) via the local network.
  • the MME 10 manages the first permission information for the offload via the local network for the UE 50 and the second permission information for the offload via the local network for the LGW 20, and the first permission information and the second permission information.
  • the UE 50 is notified of the offload permission information via the local network to the UE 50 via the HeNB 30, and the UE 50 determines the PDN connection for offload via the local network at the HeNB 30 based on the offload permission information via the local network. Require establishment.
  • the fact that the MME 10 notifies the offload permission information via the local network is that the MME 10 detects that the UE 50 permits offload (SIPTO @ LN) via the local network, and the LGW 20 It is detected that offloading via the network (SIPTO @ LN) is possible, and the UE 50 indicates that offloading via the local network (SIPTO @ LN) is possible.
  • the MME 10 manages the first permission information for offloading via the local network for the UE 50 and the second permission information for offloading via the local network for the LGW 20, and manages the permission information for offload via the local network.
  • the UE 50 can suppress a request for establishing a PDN connection for offload via the local network in the HeNB 30 based on the offload permission information via the local network.
  • the handover destination HeNB detects that the UE is capable of SIPTO @ LN, and the MME notifies the UE that SIPTO @ LN is possible.
  • the SIPTO @ LN flag cannot detect that another service such as LIPA can be used.
  • LGW 20 that can use LIPA information indicating that LIPA is possible is required. To do. This indicates that LGW 20 capable of SIPTO @ LN cannot always use LIPA. In addition, it is indicated that SIPTO @ LN cannot always be used in LIP20 capable of LIPA. Furthermore, the LGW 20 may be able to use both SIPTO @ LN and LIPA.
  • an APN identifier is used as information indicating that the MME 10 is capable of SIPTO @ LN to the UE 50.
  • the APN identifier is connection destination information for accessing the service.
  • the APN identifier used here may be permission information for permitting a specific service.
  • the SIPTO @ LN flag When indicating the permission information of the offload service via the local network, the SIPTO @ LN flag (Allow SIPTO @ LN or (Information indicating non-permission).
  • “blank” is set in the HeNB identifier in the APN 1 for the UE 50, and the UE 50 cannot transmit the PDN connection request using the APN 1.
  • the APN identifier is connection destination information for accessing the service.
  • the HeNB identifier in FIG. 9B may be information indicating the position of the HeNB where the UE is located, and may be managed by a cell identifier, a CSG identifier, or an HeNB IP address.
  • the APN identifier in FIG. 9B may be permission information for permitting a specific service.
  • the SIPTO @ LN flag SIPTO @ LN Information indicating permission or non-permission.
  • the mobile communication system in this embodiment can use FIG. 1 demonstrated in 1st Embodiment similarly, the detailed description is abbreviate
  • the MME 10 in the core network 3, the LGW 20 in the home network 5, and the HeNB 30 have the same configurations as those in the first embodiment, and thus detailed description thereof is omitted.
  • the source HeNB and the target HeNB in this embodiment have the same configuration as the HeNB 30.
  • the source HeNB does not need to be a HeNB, and may be a base station apparatus (eNB).
  • the Source HeNB detects the movement of the UE 50 and transmits a handover request to the MME 10 (S3002). Note that the movement of the UE 50 can be detected based on control information that the UE 50 periodically transmits.
  • the Source HeNB includes information on the Target HeNB in the handover request.
  • the MME 10 that has received the handover request detects the Target HeNB included in the handover request, and detects that the UE 50 is capable of SIPTO @ LN (S3004).
  • the method described with reference to FIG. 11 or FIG. 12 in the first embodiment can be similarly used for the Target HeNB included in the handover request.
  • the MME 10 detects the first permission information of the SIPTO @ LN for the UE 50 that the UE 50 can be offloaded (SIPTO @ LN) via the local network, and the HeNB 30 that is the handover destination of the UE 50 is connected.
  • MME10 can transmit the permission information of SIPTO @ LN based on the 1st permission information and the 2nd permission information.
  • the MME 10 indicates that the UE 50 can be offloaded via the local network (SIPTO @ LN), and that the second offload via the local network (SIPTO @ LN) for the LGW 20 to which the HeNB 30 that is the handover destination of the UE 50 is connected By detecting the permission information, it can be detected. Thereby, MME10 can transmit the permission information of SIPTO @ LN.
  • the MME 10 transmits a handover request to the Target HeNB (S3006).
  • the Target HeNB that has received the handover request confirms that the handover to the Source HeNB can be performed, and transmits a handover request response to the MME (S3008).
  • the MME 10 that has received the handover request from the Target HeNB transmits a handover command to the Source HeNB if SIPTO @ LN is available (S3010).
  • the MME 10 uses SIPTO @ LN permission information detected in S33004 (SIPTO @ LN based on the first permission information and the second permission information) as information indicating that SIPTO @ LN detected in S3004 is possible.
  • the second permission information of SIPTO @ LN may be an APN identifier (APN1).
  • the APN identifier is connection destination information for accessing the service.
  • APN1 is managed with permission information “SIPTO @ LN allowed only” and UE identifier “UE50” in the APN management table 158 of MME10.
  • permission information such as SIPTO allowed included SIPTO @ LN and SIPTO @ LN allowed only can be set as the permission information set in the APN identifier.
  • SIPTO @ LN In addition to LN, SIPTO @ RN can also be used, and SIPTO @ LN only indicates that only SIPTO @ LN can be used.
  • SIPTO @ LN permission information (SIPTO @ LN permission information or SIPTO @ LN second permission information based on the first permission information and the second permission information) permits a specific service.
  • the SIPTO @ LN flag (information indicating permission or non-permission of SIPTO @ LN) may be used when indicating permission information of the offload service via the local network.
  • the Source HeNB that has received the handover command from the MME 10 transmits the handover command to the UE 50 (S3012).
  • the Source HeNB includes information indicating that the UE 50 notified from the MME 10 is capable of SIPTO @ LN.
  • the information indicating that SIPTO @ LN can be included may be permission information for permitting a specific service.
  • the SIPTO @ LN flag is used. (Information indicating whether or not SIPTO @ LN is permitted) may be used. Further, the information indicating that SIPTO @ LN is possible may notify the APN identifier.
  • the APN identifier is connection destination information for accessing the service.
  • permission information such as SIPTO allowed included SIPTO @ LN and SIPTO @ LN allowed only can be set as the permission information set in the APN identifier.
  • SIPTO @ LN SIPTO @ In addition to LN, SIPTO @ RN can also be used, and SIPTO @ LN only indicates that only SIPTO @ LN can be used.
  • information indicating that SIPTO @ LN is not possible may be notified.
  • the LGW 20 supports not only SIPTO @ LN but also other services, not only SIPTO @ LN but also other services may be notified.
  • the UE 50 that has received the handover command from the Source HeNB reconfigures the RRC connection with the Target HeNB included in the handover command.
  • UE50 receives the information which shows that SIPTO @ LN notified from HeNB30 is possible.
  • the information indicating that SIPTO @ LN is possible may be an APN identifier.
  • permission information such as SIPTO allowed included SIPTO @ LN and SIPTO @ LN allowed only can be set as the permission information set in the APN identifier.
  • SIPTO @ LN SIPTO @ In addition to LN, SIPTO @ RN can also be used, and SIPTO @ LN only indicates that only SIPTO @ LN can be used.
  • information indicating that SIPTO @ LN is not possible may be notified.
  • UE50 which received the information which shows that SIPTO @ LN is possible detects that SIPTO @ LN is possible in TargetHeNB. Further, when receiving information indicating that SIPTO @ LN is not possible or not receiving information indicating that SIPTO @ LN is possible, UE 50 detects that SIPTO @ LN is not possible.
  • the UE 50 may be associated with the APN identifier (APN1) and managed in the HeNB 30 as shown in FIG. 9C.
  • APN1 APN identifier
  • the service SIPTO @ LN
  • the UE 50 manages the HeNB identifier (HeNB30) in association with the APN identifier (APN1).
  • HeNB30 HeNB identifier
  • APN1 APN identifier
  • UE50 can transmit a PDN connection using APN1 in HeNB30.
  • the HeNB identifier included in FIG. 9C may be information indicating the position of the HeNB where the UE is located, and may be managed by a cell identifier, a CSG identifier, or an HeNB IP address. Further, the APN identifier may be permission information for permitting a specific service. When indicating the permission information of the offload service via the local network, the SIPTO @ LN flag (SIPTO @ LN is permitted or not permitted). Information). When the UE 50 is located in the HeNB managed to be capable of SIPTO @ LN, the UE 50 can transmit a PDN connection request without notification from the MME 10.
  • the UE 50 may manage not only in units of HeNBs but also in units of CSG identifiers or in units of LHN identifiers in the management of HeNBs capable of SIPTO @ LN. Further, the UE 50 may manage a HeNB capable of SIPTO @ LN without a notification from the MME 10 in advance so that a PDN connection request can be transmitted regardless of the notification of the SIPTO @ LN of the MME 10.
  • the UE 50 transmits a handover confirmation to the MME 10 (S3014). Thereby, UE50 can show having completed the handover to Target HeNB.
  • the Target HeNB transmits a handover notification to the MME 10 (S3016).
  • the MME 10 that has received the handover notification transmits, to the SGW 40, a session generation request for changing the session from the source HeNB to the target HeNB (S3018). Further, the SGW 40 that has received the session generation request changes the session from the source HeNB to the target HeNB, and transmits a session generation response to the MME 10 (S3020).
  • the MME 10 manages the first permission information for offloading via the local network for the UE 50 and the second permission information for offloading via the local network for the LGW 20.
  • the UE 50 is notified of the offload permission information via the local network to the UE 50 via the HeNB 30 based on the permission information of the local network, and the UE 50 uses the offload permission information via the local network for the offload via the local network.
  • the establishment of a PDN connection can be requested. Thereby, UE can transmit the PDN connection request
  • the UE 50 manages the HeNB identifier (HeNB30) included in the handover command in association with the APN identifier (APN1).
  • the APN identifier is connection destination information for accessing the service.
  • the UE 50 can transmit a PDN connection using the APN1 in the HeNB 30.
  • UE50 is located in HeNB30 when the PDN connection request
  • the HeNB identifier managed in FIG. 9C may be information indicating the position of the HeNB in which the UE 50 is located, and may be managed by a cell identifier, a CSG identifier, or an HeNB IP address.
  • the APN identifier managed in FIG. 9C may be permission information for permitting a specific service, and when indicating permission information for an offload service via a local network, the SIPTO @ LN flag ( SIPTO @ LN may be permitted or not permitted).
  • SIPTO @ LN is possible but also that SIPTO @ LN is not possible may be notified. That is, it may be notified whether offload is possible via the local network.
  • the UE 50 transmits the RRC connection reconfiguration as illustrated in FIG. 9C.
  • the identifier (HeNB30) may not be managed in association with the APN identifier (APN1).
  • APN APN identifier
  • the MME notifies the UE that SIPTO @ LN is possible (permission information), and the UE 50 can detect that SIPTO @ LN is possible. Thereby, UE can transmit the PDN connection request
  • the MME 10 manages the first permission information for offloading via the local network for the UE 50 and the second permission information for offloading via the local network for the LGW 20, and the first permission information, the second permission information,
  • the UE 50 is notified of offload permission information via the local network to the UE 50 via the HeNB 30, and the UE 50 establishes a PDN connection for offload via the local network at the HeNB 30 based on the offload permission information via the local network. Request.
  • the MME 10 manages the first permission information for offloading via the local network for the UE 50 and the second permission information for offloading via the local network for the LGW 20, and the first permission information, the second permission information,
  • the UE 50 notifies the UE 50 via the HeNB 30 of offload permission information via the local network on the basis of the PDN connection for offloading via the local network in the HeNB 30 based on the offload permission information via the local network. It is possible to suppress the request for establishment.
  • the UE prevents unnecessary transmission of a PDN connection request, and It is possible to prevent waste of power consumption.
  • the MME can only select an LGW capable of SIPTO @ LN. It is possible to prevent unnecessary selection of LGW and to prevent the processing load on the MME.
  • the MME increases signaling to send information indicating that the PDN connection cannot be established. Can be prevented.
  • permission information such as SIPTO allowed included SIPTO @ LN or SIPTO @ LN allowed only is set as the permission information set in the APN identifier. Is possible.
  • the UE 50 has detected that SIPTO @ LN is possible by notification from the MME 10, but in the fourth embodiment, the HeNB 30 notifies the UE 50. By doing so, it is detected that offload (SIPTO @ LN) is possible via the local network.
  • the MME 10 detects that the LGW 20 is capable of SIPTO @ LN, and detects and notifies that the SIP 50 is permitted in the UE 50.
  • the HeNB 30 does not detect that the UE50 is permitted for SIPTO @ LN, detects that the LGW 20 is capable of SIPTO @ LN, and allows the SIP e @ LN in the HeNB 30. Notify that.
  • the position of the UE 50 (that it is located in the HeNB 30) is detected and it is notified that SIPTO @ LN is possible.
  • it can notify that SIPTO @ LN is possible in HeNB30, without detecting the position (it exists in HeNB30) of UE50.
  • the UE 50 is set to “blank” in the HeNB identifier in the APN 1, and the UE 50 cannot transmit the PDN connection request using the APN 1.
  • the HeNB identifier may be information indicating the location of the HeNB where the UE is located, and may be managed by a cell identifier, a CSG identifier, or an HeNB IP address.
  • the APN identifier may be permission information for permitting a specific service.
  • the SIPTO @ LN flag SIPTO @ LN is permitted or not permitted. Information).
  • the HeNB 30 manages the offload permission information of the LGW 20 via the local network, notifies the UE of the offload permission information of the LGW 20 via the local network, and the UE 50 uses the offload permission information via the local network.
  • the HeNB 30 requests establishment of a PDN connection for offloading via the local network.
  • the HeNB 30 manages the offload permission information via the local network of the LGW 20, and by not notifying the UE of the offload permission information via the local network of the LGW 20, the UE 50 permits the offload via the local network. With the information, it is possible to suppress a request for establishing a PDN connection for offloading via the local network in the HeNB 30.
  • the mobile communication system in the present embodiment can use FIG. 1 described in the first embodiment in the same manner, detailed description thereof is omitted.
  • the MME 10 in the core network 3, the LGW 20 in the home network 5, and the HeNB 30 have the same configurations as those in the first embodiment, and thus detailed description thereof is omitted.
  • the HeNB detects that SIPTO @ LN is possible in the LGW, and describes a procedure in which the HeNB notifies the UE of information indicating that SIPTO @ LN is possible.
  • the LGW 20 notifies the HeNB 30 that SIPTO @ LN is possible (S4002).
  • an APN identifier may be notified as information indicating that SIPTO @ LN is possible.
  • the APN identifier is connection destination information for accessing the service.
  • the APN identifier may be permission information for permitting a specific service.
  • the SIPTO @ LN flag SIPTO @ LN is permitted or not permitted. Information).
  • the HeNB 30 that has detected that SIPTO @ LN is possible in the LGW 20 to which the HeNB 30 is connected notifies the UE 50 that SIPTO @ LN is possible (S4004). At this time, the HeNB 30 may not transmit to a specific UE, and may be notified to the UE 50 by periodic broadcast (simultaneous transmission) to all UEs residing in the HeNB 30.
  • Information indicating that SIPTO @ LN is possible includes a method of notifying an APN identifier and a method of notifying a SIPTO @ LN flag.
  • the APN identifier is connection destination information for accessing the service.
  • the UE 50 manages the HeNB identifier (HeNB30) in association with the APN1.
  • HeNB30 HeNB identifier
  • UE50 can transmit a PDN connection using APN1 in HeNB30.
  • the HeNB identifier may be information indicating the position of the HeNB where the UE is located, and may be managed by a cell identifier, a CSG identifier, or an HeNB IP address.
  • the APN identifier may be permission information for permitting a specific service.
  • the SIPTO @ LN flag SIPTO @ LN is permitted or not permitted. Information).
  • UE50 when UE50 is located in HeNB30 connected to LGW20 capable of SIPTO @ LN, UE50 can be SIPTO @ LN by transmitting information indicating that SIPTO @ LN is possible to UE50. Can be detected.
  • the HeNB where the UE 50 is located cannot receive the broadcast, the UE 50 cannot detect that SIPTO @ LN is possible. Moreover, UE50 does not need to perform the subsequent procedure, when it cannot detect that SIPTO @ LN is possible in HeNB30 in which UE50 exists.
  • UE50 can transmit the PDN connection request
  • the UE 50 that has detected that SIPTO @ LN is possible can similarly use the procedure of FIG. 13 described in the first embodiment as a procedure for establishing a SIPTO @ LN PDN connection.
  • the HeNB 30 manages the offload permission information of the LGW 20 via the local network, notifies the UE of the offload permission information of the LGW 20 via the local network, and the UE 50 permits the offload permission information via the local network. Accordingly, the HeNB 30 can request establishment of a PDN connection for offloading via the local network.
  • the UE can transmit the PDN connection request for starting the PDN connection establishment procedure of SIPTO @ LN only when SIPTO @ LN is possible.
  • the HeNB 30 manages the offload permission information via the local network of the LGW 20, and by not notifying the UE of the offload permission information via the local network of the LGW 20, the UE 50 permits the offload via the local network. With the information, it is possible to suppress a request for establishing a PDN connection for offloading via the local network in the HeNB 30.
  • the UE prevents unnecessary transmission of a PDN connection request, and It is possible to prevent waste of power consumption.
  • the MME can only select an LGW capable of SIPTO @ LN. It is possible to prevent unnecessary selection of LGW and to prevent the processing load on the MME.
  • the MME increases signaling to send information indicating that the PDN connection cannot be established. Can be prevented.
  • permission information such as SIPTO allowed included SIPTO @ LN or SIPTO @ LN allowed only is set as the permission information set in the APN identifier. Is possible.
  • the UE 50 detects that SIPTO @ LN is possible based on the notification from the MME 10 and the HeNB 30, but the fifth embodiment. Then, by setting the HeNB 30 that can be offloaded (SIPTO @ LN) via the local network to the UE 50 in advance, when the UE 50 is located in the HeNB 30, LN) Detect as possible HeNB.
  • the UE 50 sets offload permission information via the local network in the HeNB, and the UE 50 requests establishment of a PDN connection for offload via the local network based on the offload permission information via the local network. .
  • the UE 50 when the permission information for offloading via the local network in the HeNB is not set, the UE 50 establishes a PDN connection for offloading via the local network based on the permission information for offloading via the local network. Suppress requests.
  • the UE 50 can be realized by managing the HeNB identifier.
  • the UE 50 manages the HeNB identifier (HeNB30) in association with the APN identifier (APN1).
  • the APN identifier is connection destination information for accessing the service.
  • the HeNB identifier may be information indicating the position of the HeNB where the UE is located, and may be managed by a cell identifier, a CSG identifier, or an HeNB IP address.
  • APN1 is managed in association with HeNB 30, it indicates that HeNB 30 can request a PDN connection using APN1 (SIPTO @ LN).
  • APN1 SIPTO @ LN
  • another service such as LIPA, SIPTO @ RN, or a network of a mobile communication carrier
  • the APN identifier may be permission information for permitting a specific service.
  • the SIPTO @ LN flag SIPTO @ LN is permitted or not permitted. Information).
  • the UE can transmit the PDN connection request for starting the PDN connection establishment procedure of SIPTO @ LN only when SIPTO @ LN is possible.
  • UE50 does not need to perform the subsequent procedure, when the offload permission information via the local network in HeNB is not set.
  • the mobile communication system in this embodiment can use FIG. 1 demonstrated in 1st Embodiment similarly, the detailed description is abbreviate
  • the MME 10 in the core network 3, the LGW 20 in the home network 5, and the HeNB 30 have the same configurations as those in the first embodiment, and thus detailed description thereof is omitted.
  • the UE 50 that has detected that SIPTO @ LN is possible can similarly use the procedure of FIG. 13 described in the first embodiment as a procedure for establishing a SIPTO @ LN PDN connection.
  • the UE 50 sets offload permission information via the local network in the HeNB, and the UE 50 requests establishment of a PDN connection for offload via the local network based on the offload permission information via the local network. can do.
  • the UE 50 when the permission information for offloading via the local network in the HeNB is not set, the UE 50 establishes a PDN connection for offloading via the local network based on the permission information for offloading via the local network. Can be suppressed.
  • the UE can transmit the PDN connection request for starting the PDN connection establishment procedure of SIPTO @ LN only when SIPTO @ LN is possible.
  • the UE prevents unnecessary transmission of a PDN connection request, and It is possible to prevent waste of power consumption.
  • the MME can only select an LGW capable of SIPTO @ LN. It is possible to prevent unnecessary selection of LGW and to prevent the processing load on the MME.
  • the MME increases signaling to send information indicating that the PDN connection cannot be established. Can be prevented.
  • a mobile station device is described as an example of a terminal device or a communication device, but the present invention is not limited to this, and is a stationary or non-movable electronic device installed indoors and outdoors.
  • terminal devices or communication devices such as AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other daily life equipment.
  • the program that operates in each device is a program that controls the CPU and the like (a program that causes the computer to function) so as to realize the functions of the above-described embodiments.
  • Information handled by these devices is temporarily stored in a temporary storage device (for example, RAM) at the time of processing, then stored in various ROM or HDD storage devices, and read and corrected by the CPU as necessary. • Writing is performed.
  • a recording medium for storing the program a semiconductor medium (for example, ROM, a nonvolatile memory card, etc.), an optical recording medium / a magneto-optical recording medium (for example, a DVD (Digital Versatile Disc), MO ((Magneto Optical Disc), MD (Mini Disc), CD (Compact Disc), BD, etc.), magnetic recording medium (for example, magnetic tape, flexible disk, etc.), etc.
  • the loaded program is executed.
  • the program when distributing to the market, can be stored in a portable recording medium for distribution, or transferred to a server computer connected via a network such as the Internet.
  • a server computer connected via a network such as the Internet.
  • the storage device of the server computer is also included in the present invention.
  • each device in the above-described embodiment may be realized as an LSI (Large Scale Integration) which is typically an integrated circuit.
  • LSI Large Scale Integration
  • Each functional block of each device may be individually chipped, or a part or all of them may be integrated into a chip.
  • the method of circuit integration is not limited to LSI, and may be realized by a dedicated circuit or a general-purpose processor.
  • integrated circuit technology that replaces LSI appears due to progress in semiconductor technology, it is of course possible to use an integrated circuit based on this technology.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un dispositif de gestion de position qui : gère des premières informations d'autorisation pour un délestage par l'intermédiaire d'un réseau local pour un dispositif de station mobile et des secondes informations d'autorisation pour un délestage par l'intermédiaire du réseau local pour un dispositif de contrôle d'accès ; et notifie au dispositif de station mobile, par l'intermédiaire d'un dispositif de station de base domestique, les informations d'autorisation pour un délestage par l'intermédiaire du réseau local, sur la base des premières informations d'autorisation et des secondes informations d'autorisation. Le dispositif de station mobile demande l'établissement d'une connexion PDN pour un délestage par l'intermédiaire du réseau local dans le dispositif de station de base domestique, par utilisation d'informations d'autorisation pour un délestage par l'intermédiaire du réseau local.
PCT/JP2013/074819 2012-09-28 2013-09-13 Système de communication mobile, dispositif de gestion de position, dispositif de station de base domestique, dispositif de station mobile et procédé de communication dans un système de communication mobile WO2014050607A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2012215979A JP2015233170A (ja) 2012-09-28 2012-09-28 移動通信システム、位置管理装置、ホーム基地局装置、移動局装置及び移動通信システムにおける通信方法
JP2012-215979 2012-09-28

Publications (1)

Publication Number Publication Date
WO2014050607A1 true WO2014050607A1 (fr) 2014-04-03

Family

ID=50388014

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2013/074819 WO2014050607A1 (fr) 2012-09-28 2013-09-13 Système de communication mobile, dispositif de gestion de position, dispositif de station de base domestique, dispositif de station mobile et procédé de communication dans un système de communication mobile

Country Status (2)

Country Link
JP (1) JP2015233170A (fr)
WO (1) WO2014050607A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018003480A1 (fr) * 2016-06-30 2018-01-04 株式会社Ｎｔｔドコモ Dispositif de commande de communication, équipement utilisateur, et procédé de commande de communication

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011085290A1 (fr) * 2010-01-08 2011-07-14 Interdigital Patent Holdings, Inc. Procédé et appareil de déchargement d'un trafic sur protocole internet sélectionné
WO2011085370A2 (fr) * 2010-01-11 2011-07-14 Research In Motion Limited Système et procédé pour permettre la découverte de disponibilité de service local dans une zone de couverture cellulaire locale
WO2011130294A2 (fr) * 2010-04-13 2011-10-20 Qualcomm Incorporated Procédé et dispositif de gestion de la décharge d'un protocole internet local

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011085290A1 (fr) * 2010-01-08 2011-07-14 Interdigital Patent Holdings, Inc. Procédé et appareil de déchargement d'un trafic sur protocole internet sélectionné
WO2011085370A2 (fr) * 2010-01-11 2011-07-14 Research In Motion Limited Système et procédé pour permettre la découverte de disponibilité de service local dans une zone de couverture cellulaire locale
WO2011130294A2 (fr) * 2010-04-13 2011-10-20 Qualcomm Incorporated Procédé et dispositif de gestion de la décharge d'un protocole internet local

Also Published As

Publication number Publication date
JP2015233170A (ja) 2015-12-24

Similar Documents

Publication Publication Date Title
CN105684549B (zh) 终端装置、中继终端装置以及通信控制方法
JP5898907B2 (ja) Ｘ２インタフェース管理方法、ハンドオーバ方法及び装置
TWI549455B (zh) 混合網路匯聚閘道延伸區域ip存取
RU2701703C1 (ru) Радиотерминал, радиостанция, узел базовой сети и способ связи в них
EP2978246B1 (fr) Services de proximité (prose) efficace
WO2014148257A1 (fr) Dispositif terminal, dispositif de station de base et dispositif de commande
EP2983444A1 (fr) Terminal, station de base et dispositif de commande
JP6356118B2 (ja) Ｕｅ、制御装置及び通信方法
JPWO2015105183A1 (ja) 通信制御方法、位置管理装置、基地局装置、端末装置および通信システム
WO2011137685A1 (fr) Procédé et système de sélection et d'établissement d'une interface directe
US20140016613A1 (en) System and Method for Single Radio Handover
JP5889607B2 (ja) ホーム基地局装置、位置管理装置及び移動通信システム
WO2014007274A1 (fr) Système de communication mobile, dispositif de station de base domestique, dispositif de gestion de position, procédé de communication et dispositif de station mobile
TW201116101A (en) Controlling whether a network entity performs access control based on an indication from an access point
EP2981110A1 (fr) Dispositif terminal, dispositif de station de base et dispositif de commande
JP5247794B2 (ja) 移動通信システムにおける基地局及び情報取得方法
WO2014050607A1 (fr) Système de communication mobile, dispositif de gestion de position, dispositif de station de base domestique, dispositif de station mobile et procédé de communication dans un système de communication mobile
WO2011152999A1 (fr) Procédé et appareil destinés à mettre en œuvre une sélection de cellule assistée ou une sélection de cellule par informations coopératives
CN111869254A (zh) 管理非协调无线电接入网络
JPWO2014054644A1 (ja) 移動通信システム、第２の基地局装置、移動局装置及び移動通信システムの通信方法
JP5487736B2 (ja) コアネットワーク、宅内基地局装置、通信システム、通信方法及びプログラム
WO2014002749A1 (fr) Station mobile, station de base, procédé de communication, et programme
JP2013017093A (ja) 移動局装置、位置管理装置、ｌｇｗ、アクセス制御装置、移動通信システム及び移動通信方法
WO2013005786A1 (fr) Dispositif de station mobile, dispositif de gestion d'emplacement, lgw, dispositif de contrôle d'accès, système de communication mobile et procédé de communication mobile
CN103582083A (zh) Lte网络共享时cdma网络的选择方法、终端和基站

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13840391

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13840391

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP