WO2016002692A1 - 基地局装置、第１の位置管理装置、端末装置、通信制御方法、および通信システム - Google Patents

基地局装置、第１の位置管理装置、端末装置、通信制御方法、および通信システム Download PDF

Info

Publication number
WO2016002692A1
WO2016002692A1 PCT/JP2015/068624 JP2015068624W WO2016002692A1 WO 2016002692 A1 WO2016002692 A1 WO 2016002692A1 JP 2015068624 W JP2015068624 W JP 2015068624W WO 2016002692 A1 WO2016002692 A1 WO 2016002692A1
Authority
WO
WIPO (PCT)
Prior art keywords
location management
management device
identification information
core network
tracking area
Prior art date
Application number
PCT/JP2015/068624
Other languages
English (en)
French (fr)
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 シャープ株式会社
Priority to EP15814108.5A priority Critical patent/EP3166363A4/en
Priority to JP2016531350A priority patent/JP6637418B2/ja
Priority to US15/320,957 priority patent/US10136407B2/en
Priority to CN201580031669.XA priority patent/CN106465323B/zh
Publication of WO2016002692A1 publication Critical patent/WO2016002692A1/ja
Priority to US16/180,773 priority patent/US11026208B2/en

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
    • H04W64/003—Locating users or terminals or network equipment for network management purposes, e.g. mobility management locating network equipment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/14—Interfaces between hierarchically different network devices between access point controllers and backbone network device
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers

Definitions

  • the present invention relates to a base station device, a first location management device, a terminal device, a communication control method, and a communication system.
  • EPS Evolved Packet System
  • EPC Evolved Packet Core
  • LTE Long Term Evolution
  • DECOR Dedicated Core Networks
  • a communication system is configured by multiplexing a plurality of networks, and a terminal device is connected to a different network according to a terminal type or the like. Thereby, terminal traffic can be distributed according to the terminal type, or traffic management according to the terminal type can be performed.
  • an M2M (Machine-to-Machine) terminal that has been increasing in recent years is connected to a core network dedicated to M2M, and a general mobile phone terminal such as a smartphone is connected to the main core network. it can.
  • DECOR stipulates that the main core network and the overlaid core network are separated according to the characteristics of the terminal device. Each of these core networks includes different mobility management devices.
  • the core network to which the terminal device is connected needs to be selected appropriately according to the terminal type and terminal characteristics.
  • the location management device needs to be appropriately selected according to the terminal type and terminal characteristics.
  • TAU tracking area update
  • the present invention has been made in view of such circumstances, and its purpose is to perform mobile communication by connecting a terminal to an appropriate core network in a mobile communication system in which a plurality of multiplexed core networks are configured. It is to provide a suitable means for doing this.
  • a base station apparatus is connected to a first core network including a first position management apparatus, and a second core network including a second position management apparatus and a third position management apparatus.
  • a redirect request message transmitted from the terminal device by receiving a first tracking area update request message including at least identification information of the terminal device and identification information of the second location management device from the terminal device.
  • receiving a tracking area update response message including at least identification information for identifying the third position management device, which is transmitted in response to the third tracking area update request message and transmitted from the third location management device.
  • at least identification information of the second location management device based on the reception of the first tracking area update request message.
  • the second tracking area update request message is transmitted to the first location management device, and on receipt of the redirect request message, the third tracking area update request message is transmitted to the third location management device, and tracking is performed.
  • a transmission unit which transmits a tracking area update response message to the terminal device, which is a response to the first tracking area update request message and includes identification information for identifying at least the third location management device, upon reception of the area update response message. It is characterized by having.
  • a base station apparatus is connected to a first core network including a first position management apparatus, and a second core network including a second position management apparatus and a third position management apparatus.
  • a redirect request message transmitted from the terminal device by receiving a first tracking area update request message including at least identification information of the terminal device and identification information of the second location management device from the terminal device.
  • a second tracking area update request message including at least identification information of the second location management device to the first location management device based on reception of the first tracking area update request message. If there is no connectivity in the second core network, the first tracking area update is received with the reception of the redirect request message. Is the response to the request message, and having a transmitter which transmits a tracking area update response message to the terminal device including an identification information identifying at least a first location management device.
  • the location management device of the present invention is a location management device arranged in a first core network, and the first location management device is connected to a base station device, and includes at least terminal device identification information, Receiving a first tracking area update request message including identification information of a second location management device arranged in the core network of the base station device, a response to the context request message, and a second location management device Unlike the above, a receiving unit that receives from the second location management device a context response message including identification information indicating redirection to the location management device arranged in the second core network, and a context requesting the context of the terminal device Send a request message to the second location management device and based on receiving the context response message, Unlike the second location management device, a transmission unit that transmits to the base station device a redirect request message for requesting redirection to the location management device arranged in the second core network is provided. .
  • the communication control method for a base station apparatus of the present invention is connected to a first core network including a first location management device and a second core network including a second location management device and a third location management device.
  • a step of transmitting a third tracking area update request message to the apparatus and a response to the third tracking area update request message, the identification identifying at least the third position management apparatus transmitted by the third position management apparatus A step of receiving a tracking area update response message including information, and a response to the first tracking area update request message upon receipt of the tracking area update response message, and identifying information for identifying at least the third location management device And a step of transmitting a tracking area update response message to the terminal device.
  • the communication control method for a base station apparatus of the present invention is connected to a first core network including a first location management device and a second core network including a second location management device and a third location management device. And receiving a first tracking area update request message including at least identification information of the terminal device and identification information of the second location management device from the terminal device, and the first tracking area update request message And a step of transmitting a second tracking area update request message including at least the identification information of the second location management device to the first location management device, and a redirect sent by the first location management device. Receiving the request message and, if the second core network does not have connectivity, accompanying the reception of the redirect request message. And a response to the first tracking area update request message, and at least a step of transmitting a tracking area update response message including identification information for identifying the first location management device to the terminal device. .
  • a communication control method for a location management device is a communication control method for a first location management device arranged in a first core network, and the first location management device is connected to a base station device.
  • Receiving from the base station device a first tracking area update request message including at least identification information of the terminal device and identification information of the second location management device arranged in the second core network;
  • a step of transmitting a context request message for requesting a context to the second location management device, and a response to the context request message.
  • location management is arranged at least in the second core network.
  • a context response message including identification information indicating redirection to the device is received from the second location management device.
  • a redirect request message for requesting redirection to the location management device arranged in the second core network is transmitted to the base station device based on the reception of the context response message.
  • a step of performing is a step of performing.
  • the terminal device of the present invention includes a terminal device, a base station device, a first core network including a first location management device, and a second core network including a second location management device.
  • a terminal apparatus in a communication system wherein a first tracking area update request message including at least identification information of a terminal apparatus and identification information of a first location management apparatus is transmitted to a base station apparatus, and a first tracking area update is performed
  • a reception unit that receives a tracking area update response message that is a response to the request message and includes at least identification information for identifying the second location management device, from the base station device.
  • the communication control method for a terminal device includes a terminal device, a base station device, a first core network including a first location management device, and a second core network including a second location management device.
  • the communication system of the present invention includes a terminal device, a base station device, a first core network including a first location management device, a second core including a second location management device and a third location management device.
  • the terminal device transmits a first tracking area update request message including at least identification information of the terminal device and identification information of the second location management device to the base station device.
  • the base station apparatus receives a first tracking area update request message including at least identification information of the terminal apparatus and identification information of the second location management apparatus from the terminal apparatus, and receives the first tracking area update request message. Based on the above, a second tracking area update request message including at least identification information of the second location management device is transmitted to the first location management device.
  • the first location management device sends at least a first tracking area update request message including identification information of the terminal device and identification information of the second location management device arranged in the second core network from the base station device. It is a response to the context request message that is received and transmitted to the second location management device requesting the context of the terminal device, and is different from the second location management device and is arranged in at least the second core network Unlike the second location management device, the second core network receives a context response message including identification information indicating redirection to the location management device from the second location management device. Redirect request message that requests redirection to the location management device The base station device receives the redirect request message transmitted from the first location management device, and performs third tracking to the third location management device based on the reception of the redirect request message.
  • a tracking area update response message that transmits an area update request message and is a response to the third tracking area update request message and includes at least identification information for identifying the third position management device transmitted by the third location management device
  • a tracking area update response message including at least identification information for identifying the third location management device is transmitted to the terminal device in response to the tracking area update response. Then, the terminal device makes a first tracking area update request
  • a tracking area update response message that is a response to the message and includes at least identification information for identifying the third location management device is received from the base station device.
  • the present invention it is possible to realize a tracking area update procedure for moving a terminal device and registering the position of the terminal device in a communication network constituting a multiplexed core network.
  • FIG. 1 is a diagram for explaining the outline of a mobile communication system in the present embodiment.
  • the mobile communication system 1 includes mobile terminal apparatuses UE_A10 and UE_B15, an access network 80, a core network (type 1) 90, a core network (type 2) 92, a PDN (Packet Data Network) _A100, and a PDN_B102. It is configured.
  • a core network type 1
  • a core network type 2
  • PDN Packet Data Network
  • the core network is an IP mobile communication network operated by a mobile operator.
  • the core network (type 1) 90 and the core network (type 2) 92 may be networks that are multiplexed in the mobile communication system 1.
  • the core network (type 1) 90 and the core network (type 2) 92 may be core networks operated and managed by a single mobile communication carrier. Alternatively, it may be a core network operated and managed by different mobile communication carriers.
  • the core network (type 1) 90 is a core network for a mobile communication operator that operates and manages the mobile communication system 1
  • the core network (type 2) 92 is a virtual movement such as MVNO (Mobile Virtual Network Operator). It may be a core network for a telecommunications carrier.
  • the core network (type 2) 92 may be configured as a virtual mobile communication carrier network.
  • types such as type 1 and type 2 are information for identifying the core network.
  • the information for identifying the core network is not limited to the type, and may be information that can identify the core network.
  • An identification number may be assigned to the core network, and a plurality of multiplexed core networks such as the core network 1 and the core network 2 may be identified by the identification number.
  • the core network may be identified by information for identifying the mobile communication carrier.
  • UE_A10 and UE_B15 may be assigned a core network type in advance.
  • type 1 is assigned to UE_A10
  • type 2 is assigned to UE_B15.
  • UEs to which the core network type is assigned there may be UEs to which the core network type is assigned and UEs to which the core network type is not assigned.
  • UEs that are not assigned a core network type may be connected to the default core network.
  • the default network which core network in advance by the mobile operator or the like to manage whether a default core network, may be determined by such management information.
  • the PDN connection may be established with the core network (type 1) 90, which is the main core network, as a default network.
  • a UE to which a core network type is assigned may connect to a dedicated core network corresponding to the specified type and establish a PDN connection.
  • each UE may be set when the terminal is shipped. Also, a plurality of types may be set at the time of shipment, and the user or the UE itself may change the types according to the purpose of communication.
  • the core network (type 1) 90 is a core network dedicated to UEs of type 1, and the core network (type 1) 90 includes MME (Mobility Management Entity) _A40.
  • MME Mobility Management Entity
  • the core network (type 2) 92 is a core network dedicated to UEs of type 2, and the core network (type 2) 92 includes MME_B42.
  • the core network (type 1) 90 and the core network (type 2) 92 can be connected to different PDNs (Packet Data Network).
  • PDNs Packet Data Network
  • PDN_A 100 and PDN_B 102 are packet data networks outside the core network corresponding to the purpose of the UE.
  • the PDN_A 100 may be an IMS (IP Multimedia ⁇ ⁇ Subsystem) or the like.
  • the core network (type 2) 92 is a core network dedicated to M2M terminals
  • the PDN_B 102 may be an M2M service network.
  • the configuration of the core network (type 2) 92 is the same as the configuration of the core network (type 1) 90, and detailed description thereof is omitted.
  • the core network (type 1) 90 includes an HSS (Home (Subscriber50Server) 50, an AAA (Authentication, Authorization, Accounting) 55, a PCRF (Policy and Charging Rules Function) 60, and a PGW (Packet Data).
  • HSS Home (Subscriber50Server) 50
  • AAA Authentication, Authorization, Accounting
  • PCRF Policy and Charging Rules Function
  • PGW Packet Data
  • Network Gateway 30 ePDG (enhanced Packet Data Gateway) 65, SGW (Serving Gateway) 35, and MME_A 40.
  • the core network (type 1) 90 is connected to each access network (LTE AN80, WLAN ANb75, WLAN ANa70).
  • the radio access network may be composed of a plurality of different access networks. Each access network is connected to a core network (type 1) 90. Furthermore, the UE 10 can wirelessly connect to the radio access network.
  • the access network that can be connected by the WLAN access system includes a WLAN access network b (WLAN ANb75) that connects the ePDG 65 as a connection device to the core network (Type 1) 90, and a WLAN access that connects the PGW 30, the PCRF 60, and the AAA 55.
  • Network a (WLAN ANa75) can be configured.
  • each apparatus is comprised similarly to the conventional apparatus in the mobile communication system using EPS, detailed description is abbreviate
  • each device will be briefly described.
  • the PGW 30 is connected to the PDN 100, the SGW 35, the ePDG 65, the WLAN ANa 70, the PCRF 60, and the AAA 55, and delivers user data as a gateway device of the PDN 9 and the core network (type 1) 90.
  • the SGW 35 is connected to the PGW 30, the MME_A 40, and the LTE AN 80, and performs user data delivery as a gateway device between the core network (type 1) 90 and the LTE AN 80.
  • the MME_A 40 is connected to the SGW 35, the LTE AN 80, and the HSS 50, and is an access control device that performs location information management and access control of the UE 15 via the LTE AN 80.
  • the core network (type 1) 90 may include a plurality of location management devices.
  • MME_C44 may be configured as a location management device different from MME_A40.
  • the MME_C 44 may be connected to the SGW 35, the LTE AN 80, and the HSS 50 in the same manner as the MME_A 40.
  • MME_C44 and MME_A40 may be connected. Thereby, MME_C44 and MME_A40 may perform transmission / reception of the context of UE10.
  • the HSS 50 is connected to the MME_A 40 and the AAA 55, and is a management node that manages subscriber information.
  • the subscriber information of the HSS 50 is referred to at the time of access control of the MME_A 40, for example.
  • the HSS 50 may be connected to the MME_B42.
  • the MME_B 42 is included in the core network (type 2) 92 and the overlay network of the core network (type 1) 90.
  • the HSS 50 may be connected to an MME included in a core network different from the core network including the HSS 50, such as the MME_B42. Furthermore, the subscriber information of the HSS 50 is also referred to during access control of the MME_B42.
  • the HSS 50 may be included in the core network (type 2) 92. In this case, the HSS 50 may be connected to the MME_A 40.
  • one HSS may be shared among a plurality of multiplexed core networks.
  • AAA 55 is connected to PGW 30, HSS 50, PCRF 60, and WLAN ANa 70, and performs access control for UE 10 connected via WLAN ANa 70.
  • PCRF 60 is connected to PGW 30, WLAN ANa 75, AAA 55, and PDN 100, and performs QoS management for data delivery. For example, the QoS of the communication path between UE_A10 and PDN_A100 is managed.
  • the ePDG 65 is connected to the PGW 30 and the WLAN ANb 75, and delivers user data as a gateway device between the core network (type 1) 90 and the WLAN ANb 75.
  • each radio access network includes a device (for example, a base station device or an access point device) to which UE_A 10 is actually connected.
  • a device used for connection a device adapted to a radio access network can be considered.
  • the LTE AN 80 includes the eNB 45.
  • the eNB 45 is a radio base station to which the UE 10 is connected in the LTE access system, and the LTE AN 80 may be configured to include one or a plurality of radio base stations.
  • the WLAN ANa 70 includes a WLAN APa 72 and a GW (Gateway) 74.
  • the WLAN APa 72 is a radio base station to which the UE 10 is connected with a WLAN access system that is reliable to the operator operating the core network (type 1) 90, and the WLAN ANa 70 includes one or more radio base stations. May be configured.
  • the GW 74 is a gateway device of the core network (type 1) 90 and the WLAN ANa 70. Further, the WLAN APa 72 and the GW 74 may be configured by a single device.
  • WLAN ANb75 is configured to include WLAN APb76.
  • the WLAN APb 76 is a radio base station to which the UE 10 is connected in the WLAN access system when a trust relationship is not established with the operator operating the core network (type 1) 90, and the WLAN ANb 75 includes one or more of them.
  • a radio base station may be included.
  • the WLAN ANb 75 is connected to the core network (type 1) 90 using the ePDG 65, which is a device included in the core network (type 1) 90, as a gateway.
  • the ePDG 65 has a security function for ensuring safety.
  • the fact that the UE 10 is connected to each radio access network means that the UE 10 is connected to a base station apparatus, an access point, etc. included in each radio access network. Also via a base station device or access point.
  • FIG. 3A shows a configuration diagram of the eNB 45.
  • the eNB 45 includes an IP mobile communication network interface unit 220, a control unit 200, and a storage unit 240.
  • the IP mobile communication network interface unit 220 and the storage unit 240 are connected to the control unit 200 via a bus.
  • the control unit 200 is a functional unit for controlling the eNB 45.
  • the control unit 200 implements various processes by reading and executing various programs stored in the storage unit 240.
  • the IP mobile communication network interface unit 220 is a functional unit for the eNB 45 to connect to the UE_A 10 and the UE_B 15 and to connect to the core network (type 1) 90 and the core network (type 2) 92.
  • the storage unit 240 stores MME information 242.
  • the MME information 242 stores MMEs that can be connected from the eNB 45. For example, as shown in FIG. 3B, identification information of MMEs connectable from the eNB 45 and area information for identifying service areas of the respective MMEs may be stored in association with each other. In the example of FIG. 3B, different MMEs are stored for each service area, and the base station apparatus arranged in each service area can be connected to the MME associated with the service area. ing. Note that MMEs included in different types of core networks may be stored for the same service area. For example, the MME installed in the type 1 core network and the MME installed in the type 2 core network may be stored in association with the service area “A”.
  • the MME identification information may be information that can identify the MME, and may be GUMME (Globally Unique MME Identifier), for example.
  • GUMMEI is identification information of the MME, and includes PLMN (Public land mobile ⁇ network) that is identification information of the mobile communication carrier network, an MME group number that identifies a plurality of MMEs, and an MME number that identifies the MME. include.
  • the MME group number may include information that can identify the type of the core network.
  • the core network can be identified by the MME group number.
  • the MME arranged in the corresponding core network may be managed as a group in association with the group number of the MME. Accordingly, the core network type including the MME may be identified based on the MME identification information and the MME group number.
  • the core network type information may be indicated by an information element independent of the MME identification information.
  • the MME information 242 may store type information that is identification information of the core network, area information, and MME identification information in association with each other. Thereby, an area can be comprised according to the type of a core network. Furthermore, MME arrange
  • the MME identification information may be GUMMEI.
  • the area information is not necessarily stored, and the core network type and the MME identification information may be stored in association with each other.
  • the area information described so far may be tracking area information or routing area information.
  • FIG. 4A shows a configuration diagram of the MME_A40.
  • the MME_A 40 includes an IP mobile communication network interface unit 320, a control unit 300, and a storage unit 340.
  • the IP mobile communication network interface unit 320 and the storage unit 340 are connected to the control unit 300 via a bus.
  • the control unit 300 is a functional unit for controlling the MME_A 40.
  • the control unit 300 implements various processes by reading and executing various programs stored in the storage unit 340.
  • the IP mobile communication network interface unit 320 is a functional unit for the MME_A 40 to connect to the eNB 45, the SGW 35, and the HSS 50.
  • the storage unit 340 stores MME information 342 and context information 344 as shown in the figure.
  • the MME information 342 may store MME identification information, MME service area information, and core network identification information in association with each other.
  • the MME identification information may be information that can identify the MME, and may be GUMME (Globally Unique MME Identifier), for example.
  • GUMMEI is identification information of the MME, and includes PLMN (Public land mobile ⁇ network) that is identification information of the mobile communication carrier network, an MME group number that identifies a plurality of MMEs, and an MME number that identifies the MME. include.
  • the MME group number may include information that can identify the type of the core network.
  • the core network can be identified by the MME group number.
  • the MME arranged in the corresponding core network may be managed as a group in association with the group number of the MME. Accordingly, the core network type including the MME may be identified based on the MME identification information and the MME group number.
  • the MME information 342 may store the MME identification information and the service area information in association with each other, and the core network type information may not necessarily be stored.
  • these MME identification information management methods do not necessarily store area information, but may store the core network type and MME identification information in association with each other.
  • the area information described so far may be tracking area information or routing area information.
  • the context information 344 has memorize
  • the context information of the UE may be an MM (Mobility Management) context that the MME conventionally stores, an EPS (Evolved Packet System) bearer context, or both.
  • the information identifying the core network such as type information, may be identification information assigned based on such a decision that determines that the core network is separated from the viewpoint of operation and management by the mobile communication carrier.
  • the information identifying the core network such as type information may be information associated with the type or attribute of the communication terminal.
  • identification information for identifying a core network to which an M2M terminal is connected and identification information for identifying a core network to which a general call terminal such as a smartphone is connected may be used.
  • the information identifying the core network such as type information may be identification information associated with a service provided by the mobile communication carrier.
  • information for identifying a specific service provided to an M2M terminal may be associated with identification information for providing a call service such as IMS and information for identifying a core network.
  • the core network can be configured separately for each service.
  • the core network connected for every terminal which provides each service can be divided by managing the terminal which provides a service for every service.
  • the UE performs a tracking area update procedure in order to register a location in the core network.
  • the tracking area update procedure is a procedure led by the UE, and the trigger for the UE to start the tracking area update procedure includes regular execution at regular intervals, and a plurality of conditions are defined by the 3GPP specifications. .
  • the tracking area update procedure is executed for the purpose of allowing the core network to manage the location of the UE_A 10 even when the UE_A 10 transitions to the idle mode and moves in a state where radio resources and the like are released.
  • a tracking area update procedure with MME relocation is defined. For example, when the UE moves significantly from the position registered last time, or when the tracking area where the previous UE performed position registration is different from the tracking area where the new position registration is performed, the MME needs to be changed.
  • the tracking area update procedure with MME relocation in this embodiment is different from the conventional procedure, and performs location registration that realizes movement while maintaining the core network type. Thereby, UE can maintain the connection to the same overlay network. In other words, the UE can maintain a connection to the core network identified by identification information (for example, type information) of the same core network.
  • FIG. 5 illustrates a system model for explaining the tracking area update procedure.
  • the system model includes an eNB 45, an eNB 47, a core network (type 1) 90, and a core network (type 2) 92.
  • ENB45 is an LTE base station connected before UE_A10 moves.
  • the eNB 47 is an LTE base station to which the UE_A 10 is connected after moving. Since the eNB 47 is the same as the eNB 45 except for the access area, a detailed description of the configuration is omitted.
  • Core network (type 1) 90 is a main core network and has connectivity with eNB 45 and eNB 47.
  • the main core network may be a core network in which a UE that does not require a dedicated core network establishes a PDN connection.
  • the core network (type 1) 90 may be used as a core network to be temporarily connected.
  • the core network (type 1) 90 includes MME_A40 and MME_C44.
  • MME_A 40 has connectivity with eNB 45
  • MME_C 44 has connectivity with eNB 47. Since MME_C44 has the same configuration as MME_A40, detailed description of the functional configuration is omitted.
  • the core network (type 2) 92 is a UE-dedicated core network whose core network type is type 2, and has connectivity with the eNB 45 and the eNB 47.
  • the core network (type 2) 92 includes MME_B42 and MME_D46.
  • the MME_B 42 has connectivity with the eNB 45
  • the MME_D 46 has connectivity with the eNB 47. Since the MME_D 46 has the same configuration as the MME_B 44, a detailed description of the functional configuration is omitted.
  • the eNB 45 stores MME_A 40 in association with the core network type 1 in the MME information 242. Further, MME_B 42 is stored in association with the core network type 2.
  • the eNB 45 stores MME_A 40 as the default MME.
  • the default MME is an MME that the eNB 45 selects as a connection destination when there is no special condition.
  • eNB45 may memorize
  • the eNB 47 stores MME_C 44 in association with the core network type 1 in the MME information 242. Further, MME_D 46 is stored in association with the core network type 2.
  • the eNB 47 stores MME_C44 as the default MME.
  • the default MME is an MME that the eNB 47 selects as a connection destination when there is no special condition.
  • eNB47 may memorize
  • MME_C44 MME_C44
  • the MME identification information does not include information for identifying the core network type. More specifically, in this example, the eNB 47 stores the MME information 242 as illustrated in FIG. 3B in the storage unit 240, and identifies the core network type in the GUMEI group information portion as the MME identification information. A case where information that can be performed is not included will be described.
  • the eNB 45 and the eNB 47 do not have a function of identifying the core network type to which the MME is connected based on the identification information of the MME.
  • UE_A 10 is a UE having a core network type of type 2, and UE_A 10 is connected to a core network (type 2) 92 via eNB 45 as an initial state. At that time, the MME_B 42 is performing location management of the UE_A 10.
  • a trigger for transmitting a tracking area update request occurs (S402).
  • the transmission trigger for the tracking area update request is not particularly limited, but may be a trigger that occurs periodically, for example, and may be the same as a conventional trigger, such as the end of the timer count. At this time, it is assumed that UE_A 10 has moved to the connection area of eNB 47.
  • UE_A 10 transmits a tracking area update request message to eNB 47 based on the tracking area update request trigger (S404).
  • UE_A10 may transmit the message including the identification information of UE_A10, the identification information of MME_B42 to which UE_A10 is connected before moving, and tracking area information indicating the position of UE_A10. As a result, the UE_A 10 requests the eNB 47 to update the tracking area information of the UE_A 10 managed by the MME.
  • GUTI GloballyAUnique Temporary Identity assigned globally unique to UE_A10 may be used as the identification information of UE_A10.
  • GUMEI may be used as the identification information of MME_B42.
  • GUMMEI may be configured to be included in GUTI.
  • GUMMEI for identifying the MME to which the UE is connected before moving is denoted as old GUMMEI.
  • the UE_A 10 may acquire and store the old GUMMEI from the core network when the UE_A 10 attaches, establishes a PDN connection, or by the previous tracking area update procedure or the like.
  • ENB 47 receives the tracking area update request message from UE_A 10.
  • the eNB 47 acquires the identification information of the UE included in the message, the identification information of the MME before movement such as old GUMMEI, and the tracking area information.
  • the eNB 47 performs MME selection processing based on the reception of the tracking area update request message (S406).
  • the MME corresponding to the old GUMMEI may be selected and connected.
  • the eNB 47 selects the MME to be temporarily connected. .
  • the method for selecting the MME is not particularly specified, but the default MME may be selected.
  • the default MME MME_C 44 is selected.
  • the eNB 47 transmits a tracking area update request message to the MME_C 44 based on the MME selection process (S408).
  • the eNB 47 may transmit the UE_A10 including the identification information of the UE_A10, the identification information of the MME_B42 to which the UE_A10 is connected before moving, and the tracking area information indicating the position of the UE_A10 in the message.
  • the eNB 47 may request the MME_C 44 to receive and store the context of the UE_A 10 from the MME to which the UE_A 10 is connected before moving and update the tracking area of the UE_A 10 included in the context of the UE_A 10.
  • MME_C 44 receives the tracking area update request message from the eNB 47.
  • MME_C44 acquires the identification information (for example, old GUMMEI) of MME_B42 which UE_A10 has connected before a movement contained in a message.
  • the MME_C 44 transmits a context request message to the MME_B 42 based on the old GUMMEI (S410). Thereby, MME_C44 requests
  • the MME_C 44 may transmit a message including identification information of the core network to which the MME_C 44 is connected. Specifically, the message may be transmitted including type information (type 1) of the core network to which the MME_C 44 is connected.
  • MME_B 42 receives the context request message from MME_C 44. Thereby, MME_B42 acquires the identification information of the core network of MME_C44 contained in a message.
  • the MME_B 42 executes MME reselection determination processing based on the acquisition of the core network identification information (S412).
  • the MME_B 42 may determine whether to perform reselection based on a comparison between the acquired identification information of the core network and the identification information of the core network to which the MME_B 42 is connected. Prior to the MME reselection determination process, the MME_B 42 may store in advance identification information of the core network to which the MME_B 42 is connected. More specifically, the MME_B 42 may store in advance type information (type 2) of the core network to which the MME_B 42 is connected.
  • the MME_B 42 is the same when the acquired identification information of the core network and the identification information of the core network to which the MME_B 42 is connected are the same. It may be determined that MME reselection is not performed.
  • the MME_B 42 may determine to reselect the MME.
  • the MME_B 42 is different from the type information indicating the type 1 that is the acquired identification information of the core network and the type information indicating the type 2 that is the identification information of the core network to which the MME_B 42 is connected. Decide to re-select.
  • the MME_B 42 transmits a context response message to the MME_C 44 as a response to the received context request (S414).
  • MME_B 42 When MME_B 42 performs MME reselection based on the determination process of MME reselection, MME_B 42 includes an information element indicating a rejection response to the context request and execution of redirection to another MME. Identification information indicating that it is requested may be included. In this case, the MME_B 42 may be transmitted without including the context of the UE_A 10 in the message.
  • redirection may mean reselection of the MME, may mean sending a tracking area update request message to the new MME, or may mean both.
  • the MME_B 42 may transmit a message including information for identifying the MME to be redirected by the eNB 47. As described above, the MME_B 42 may specify the MME to be redirected by including the identification information of the MME to be specified in the message.
  • the identification information indicating that another MME is requested to execute redirect may use a flag such as flag1 or information that identifies the redirected MME.
  • the MME_B 42 may include the identification information of the core network to which the MME_B 42 is connected, such as type information, as the identification information indicating that the execution of redirection is requested to another MME.
  • the MME_B 42 may transmit a specific control information such as a redirect request message or a context response rejection as a context response message when requesting execution of redirection.
  • a rejection response message for a context response it may be transmitted including reason information such as Cause Value indicating that redirection is necessary.
  • the MME_B 42 may transmit a context response to the MME_C 44 based on the reception of the context request message when the MME reselection is not performed based on the determination process of the MME reselection (S414).
  • the MME_B 42 may transmit the message including the context of the UE_A 10, identification information of the core network type of the MME_B 42, and identification information for identifying the MME_B 42 such as GUMMEI.
  • MME_C44 receives the context response message from MME_B42.
  • MME_C 44 detects the necessity of redirection based on the received context response message.
  • MME_C44 includes that the context response message includes identification information indicating that redirection is requested, that the context response message is a redirect request message, or that the context response message is a context response rejection response message.
  • redirection is necessary, for example, by reason information such as Cause Value included in the message indicating necessity of redirection.
  • the reselection determination process (S412) is executed in the MME_B42 and the necessity of redirection is determined.
  • the MME_B42 does not perform the reselection determination process
  • the MME_C44 performs the reselection determination process. May be performed.
  • the MME_C 44 may transmit the context request (S410) transmitted to the MME_B 42 without including the identification information of the core network to which the MME_C 44 is connected.
  • the MME_B 42 may transmit the context response to the MME_C 44 based on the reception of the context request message without performing the reselection determination process (S 412) (S 414).
  • the MME_B 42 may transmit the message including the context of the UE_A 10, identification information of the core network type of the MME_B 42, and identification information for identifying the MME_B 42 such as GUMMEI.
  • the MME_B 42 may hold the context information of the UE_A 10 without immediately deleting it. Note that the context information of the UE_A 10 may be deleted after a predetermined time has elapsed after the transmission of the context response. In this way, the MME_B 42 may continue to hold the UE_A 10 without deleting the context information so that it can respond to the context request that is executed again.
  • the MME_C 44 receives the context response and executes the MME reselection determination process (S415).
  • the MME_C 44 determines whether to perform reselection based on a comparison between the identification information of the core network acquired by the context response and the identification information of the core network to which the MME_C 44 is connected. Also good. Prior to the MME reselection determination process, the MME_C 44 may store in advance identification information of the core network to which the MME_C 44 is connected. More specifically, the MME_C 44 may store in advance core network type information (type 1) to which the MME_C 44 is connected.
  • the MME_C 44 is configured such that when the acquired core network identification information and the core network identification information to which the MME_B 42 is connected are the same core network, You may decide not to re-select MME.
  • the MME_C 44 may determine to reselect the MME.
  • the MME_C 44 is different from the type information indicating the type 2 that is the acquired identification information of the core network and the type information indicating the type 1 that is the identification information of the core network to which the MME_C 44 is connected. Decide to re-select.
  • the MME_C 44 may detect the necessity of redirection based on the reselection determination process.
  • the MME that has received the rejection response for the update procedure from the MME before moving executes the authentication and security establishment procedure by transmitting and receiving control information including the UE and HSS.
  • the MME_C 44 detects that redirection is necessary the authentication and security processing may be omitted and not executed (S417).
  • the MME_C 44 may omit acquisition of subscriber information such as identification information of the core network to which the UE_A 10 is connected from the HSS 60 or the like, or terminal attribute information for specifying the identification information of the core network.
  • the MME_C 44 When the MME_C 44 detects that redirection is not necessary, the MME_C 44 does not transmit a redirect request, and transmits a tracking area update response message including a GUMMEI for identifying a new MME to the eNB 47 based on a conventional tracking area update procedure. To do.
  • the eNB 47 that has received the tracking area update response message transmits a tracking area update response including GUMMEI for identifying a new MME to the UE_A 10 to complete the tracking area update procedure.
  • the MME_C 44 transmits a redirection request message to the eNB 47 (S416).
  • the message may include an information element indicating that another MME requests redirection, or may transmit specific control information indicating that redirection is requested.
  • the MME_C 44 may include the identification information of the specified MME in the message.
  • the MME_C 44 may further transmit a redirect request message including identification information of the designated MME.
  • the MME_C44 determines whether the MME_C44 is based on the identification information of the core network to which the MME_B42 is included included in the message received from the MME_B42.
  • the MME that is the redirect destination of the eNB 47 may be selected from the MME information included in the storage unit, and the identification information of the selected MME may be included in the redirect request message.
  • the MME_C 44 may transmit the message including the identification information of the core network to which the MME_B 42 is connected, instead of including the identification information of the MME.
  • the MME_C 44 may further transmit a redirect request message including identification information of the core network to which the MME_B 42 is connected.
  • ENB 47 receives the redirect request message from MME_C 44 as a response to the tracking area update request message.
  • the eNB 47 executes MME reselection processing based on the information element included in the message and indicating a redirect request to another MME (S418).
  • the eNB 47 selects the MME included in the message as the redirect destination MME.
  • the MME may be selected based on the received identification information of the core network.
  • the eNB 47 may store the identification information of the core network and the MME in advance, and may select the MME corresponding to the received identification information of the core network.
  • ENB 47 selects MME_D 46 as a new MME based on the MME reselection process, and transmits a tracking area update request message to MME_D 46 (S420).
  • the message includes the MME identification information (old GUMMEI (GUMMEI_B)) to which the UE_A 10 was connected before moving, and tracking area information indicating the location of the UE_A 10.
  • MME identification information old GUMMEI (GUMMEI_B)
  • the identification information of the MME before moving is the GUMEI of the MME_B42.
  • the tracking area identification information is UE location registration area information.
  • the eNB 47 may transmit a tracking area update request message to the MME_D 46 upon reception of the redirect request message. Also, the eNB 47 may transmit a tracking area update request message to the MME_D 46 when the MME can be selected by the MME reselection process. Further, the eNB 47 may transmit the tracking area update request message to the MME_D 46 by storing the identification information of the MME configured to be included in the core network corresponding to the identification information of the core network of the redirect destination. . Moreover, eNB47 may transmit the tracking area update request message to MME_D46 by memorize
  • MME_D 46 receives a tracking area update request from eNB 47.
  • the MME_D 46 transmits a context request message to the MME_B 42 based on the identification information of the MME included in the message (S422).
  • tracking area update request message received from the eNB 47 in the message. Furthermore, identification information of the core network type of MME_D 46 may be included.
  • MME_B 42 receives the context request message from MME_D 46.
  • the MMEB 42 acquires the identification information of the core network type of the MME_D 46 included in the message, compares the acquired core network type with the core network type of the MME_B 42, and determines that the MME reselection is unnecessary (S424).
  • the MME_B 42 transmits a context response message to the MME_D 46 based on the determination that reselection is unnecessary (S426).
  • the message is the UE_A10 context stored in the storage unit of the MME_B42, and includes the MM context and the EPS bearer context.
  • the MME_B 42 may transmit a context response to the MME_D 46 based on the reception of the message (S426).
  • the message includes the UE_A10 context and the MME_B42 core network type identification information.
  • the context of UE_A 10 may include a conventional MM context or an EPS bearer context.
  • MME_D 46 receives a context response message from MME_B 42 as a response to the context request message.
  • the MME_D46 acquires the core network type of MME_B42 and compares it with the core network type of MME_D46. As a result of the comparison, it is determined that reselection is unnecessary for MME_D 46 (S427).
  • the MME_D 46 stores the context of the UE_A 10 included in the message in the storage unit based on the reception of the context or the determination that reselection is unnecessary. Furthermore, the tracking area information included in the context is updated using the tracking area information (for example, tracking area ID) indicating the position of the UE_A 10 before movement included in the tracking area update request message received from the eNB 47.
  • the tracking area information for example, tracking area ID
  • the MME_D 46 transmits a tracking area update response message to the eNB 47 based on the reception of the context response message (S428).
  • the message includes an information element that notifies that the update of the tracking area has been completed, and identification information (for example, GUMMEI) of MME_D 46 that is a new MME.
  • ENB 47 receives the tracking area update response message from MME_D 46.
  • the eNB 47 acquires the new MME identification information included in the message, and transmits a tracking area update response message to the UE_A 10 based on the reception of the message (S430).
  • the message includes an information element for notifying that the tracking area update has been completed and identification information (for example, GUMMEI) of the new MME MME_D46.
  • UE_A 10 receives the tracking area update response message from eNB 47.
  • the identification information of the new MME included in the received message is acquired.
  • the MME relocation associated with the tracking area update procedure can be realized without changing the core network type.
  • the eNB 47 receives a paging request from the new MME, and the UE starts the service request procedure or tracking area update procedure.
  • the UE_A 10 can transmit the service request to the new MME to realize the service request procedure.
  • the eNB 45 stores MME_A 40 in association with the core network type 1 in the MME information 242. Further, MME_B 42 is stored in association with the core network type 2.
  • the eNB 45 stores MME_A 40 as the default MME.
  • the default MME is an MME that the eNB 45 selects as a connection destination when there is no special condition.
  • eNB45 may memorize
  • the eNB 47 stores MME_C 44 in association with the core network type 1 in the MME information 242. Furthermore, information on the MME associated with the core network type 2 is not stored.
  • the eNB 47 stores MME_C44 as the default MME.
  • the default MME is an MME that the eNB 47 selects as a connection destination when there is no special condition.
  • eNB47 may memorize
  • MME_C44 MME_C44
  • the UE_A 10 connected to the core network identified by type 2 specifically transmits the tracking area update request. explain.
  • the procedure after S416 will be described with reference to FIG.
  • the eNB 47 may determine whether to reject the tracking area update procedure or change the core network to execute the tracking area update procedure.
  • the setting information may be setting information set in the eNB 47 by the base station operator or setting information based on an operator policy determined by the network operator.
  • rejection of the tracking area update procedure may be executed when the eNB 47 has no connectivity with the MME configured in the core network that matches the core network requested by the UE.
  • the rejection of the tracking area update procedure may be executed when information of the MME configured in the core network that matches the identification information of the core network requested by the UE is not stored.
  • the rejection of the tracking area update procedure may be executed when the identification information of the core network requested by the UE is not stored.
  • FIG. 7A illustrates a case where the eNB 47 rejects the tracking area update request based on the setting information.
  • the eNB 47 receives the redirect message from the MME_C 44 (S416). An information element included in the received message indicating that another MME is requested to be redirected is acquired, and reselection of the MME is attempted based on the acquisition. However, the eNB 47 confirms from the MME information 242 included in the storage unit 240 of the eNB 47 that no other MME other than the already selected MME can select the MME in which the UE_A 10 is the service area (S502). That is, the eNB 47 confirms that the eNB 47 has no connectivity to the core network (type 2) 92.
  • the eNB 47 transmits a tracking area update rejection response message to the UE_A 10 in order to reject and end the tracking area update procedure (S504).
  • the message includes an information element indicating that the tracking area update request has been rejected.
  • the tracking area update rejection response message is a control message responding to the tracking area update request message transmitted by the UE_A 10, and may be a control message including information notifying that the tracking area update has failed or rejected. That's fine.
  • the UE_A10 receives the tracking area update rejection response message.
  • the UE_A 10 detects that the tracking area update procedure has failed based on information indicating that the racking area update request included in the tracking area update rejection response message has been rejected.
  • UE_A10 may disconnect the PDN connection based on information indicating that UE_A10 has rejected the racking area update request included in the tracking area update rejection response message.
  • the PDN connection may be disconnected by the UE_A 10 taking the lead in executing the PDN disconnection procedure.
  • UE_A 10 may start a disconnection request message including APN (Access (Point Name), receive a response message to the disconnection request message, and complete the PDN disconnection procedure.
  • APN Access (Point Name)
  • the eNB 47 receives the redirect message from the MME_C 44 (S416). An information element included in the received message indicating that another MME is requested to be redirected is acquired, and reselection of the MME is attempted based on the acquisition. However, the eNB 47 confirms from the MME information 242 included in the storage unit 240 of the eNB 47 that no other MME other than the already selected MME can select the MME in which the UE_A 10 is the service area (S502). That is, the eNB 47 confirms that the eNB 47 has no connectivity to the core network (type 2) 92.
  • the eNB 47 determines that reselection of the MME is not possible, the eNB 47 transmits a tracking area update request message to the MME_C 44 in order to register the location in the core network with different identification information based on the setting information (S506). ).
  • the message includes the identification information of the MME before the movement, the tracking area information indicating the position of the UE_A 10, and the identification information that means that the request for reselecting the MME such as flag2 is stopped.
  • the eNB 47 may request to update the tracking area information stored in the MME by changing the core network.
  • MME_C 44 receives the tracking area update request message from the eNB 47.
  • the MME_C 44 acquires identification information such as the identification information old GUMMEI and flag2 of the MME before movement included in the message.
  • MME_C44 transmits a context request message to MME_B42 based on the acquired old GUMMEI, and requests the context of UE_A10 again (S508).
  • identification information of the core network type of MME_C44 may be included.
  • MME_B 42 receives the context request message from MME_C 44. Further, the MME_B 42 transmits a context response message to the MME_C 44 (S510).
  • the MME_B 42 transmits the context response message without receiving the MME resetting determination process when receiving the context request by receiving the identification information such as flag2 included in the message received from the MME_C 44. Also good.
  • MME_B 42 includes the context of the UE_A 10 in the context response message. Furthermore, the core network type of MME_B42 may be included.
  • MME_C44 receives the context response message from MME_B42.
  • MME_C44 memorize
  • the MME_C 44 transmits a tracking area update response message to the eNB 47 (S514).
  • the MME_C 44 receives the identification information such as flag2 included in the message received from the eNB 47, and therefore, when receiving the context response from the MME_B 42, the MME_C 44 does not omit the MME reconfiguration determination process and does not perform the tracking area.
  • An update response message may be sent.
  • the MME_C 44 may transmit the context response message without including the core network type of the MME_B 42 by receiving the flag 2 included in the tracking area update request message received from the eNB 47.
  • the MME_C 44 does not perform the MME reconfiguration determination process when receiving the context response from the MME_B 42, and transmits the tracking area update response message. Good.
  • the MME_C 44 includes the information for identifying the MME_C 44 in the tracking area update response message and transmits it to the eNB 47.
  • the information for identifying MME_C44 may be GUMMEI for identifying MME_C44.
  • the MME_C 44 transmits the message including the information element that notifies the updating of the tracking area.
  • ENB 47 receives the tracking area update response message from MME_C 44.
  • the eNB 47 transmits a tracking area update response message to the UE_A 10 based on the reception of the message (S516).
  • the eNB 47 may include an information element for notifying that the update of the tracking area whose core network has been changed is completed in the message and the identification information of the new MME MME_C44.
  • the MME_C 44 may receive the context of the UE_A 10 from the MME_B 42 and hold the context of the UE_A 10 until the tracking area update request transmitted by the eNB 47 is received again.
  • the MME_C 44 may have the timer 1 for waiting for a certain period and may hold the context of the UE_A 10 until the timer 1 ends. This makes it possible to wait for a tracking area update request transmitted by the eNB 47 for a certain period of time.
  • the MME_C 44 may store the held context in the storage unit. Good. This makes it possible to omit the context request procedure (S512) executed again for the MME_B 42, including the context request transmission / reception (S508) and the context response transmission / reception (S510).
  • tracking area update request transmission / reception (S506), tracking area update response transmission / reception (S514), context request transmission / reception (S508), context response transmission / reception (S510), etc.
  • the update procedure (S518) may be omitted.
  • the context response message described in S414 of FIG. 6 is transmitted including the context of UE_A10. Furthermore, when the MME cannot be reselected, the context response message may be a notification requesting to update the tracking area by changing the core network.
  • the MME_B 42 After transmitting such a context response, the MME_B 42 starts counting the timer 2 for storing the context of the UE_A 10 in the storage unit for a certain period, and deletes the context of the UE_A 10 when the timer 2 is consumed. May be. Thereby, MME_B42 may detect that UE_A10 completed the update of the tracking area which changed the core network.
  • the MME_C 44 transmits the redirect request message (S416) to be transmitted to the eNB 47 based on the reception of the context response, including the context of the UE_A10. Further, the redirect request message may be a notification requesting to update the tracking area by changing the core network when the MME cannot be reselected.
  • the MME_C 44 may store the context of the UE_A 10 and the tracking area information in the storage unit for a certain period of time and start the timer 3 counting. Further, the MME_C 44 may delete the context of the UE_A 10 when the timer 3 is consumed. Thereby, MME_C44 can register the tracking area of UE_A10 in MME_C44 until the timer 3 is consumed. Note that the MME_C 44 may stop counting the timer 3 and register the tracking area of the UE_A 10 when a new message for requesting the tracking area update of the UE_A 10 is received before the timer 3 is consumed.
  • the eNB 47 receives such a redirect request message, and when the MME included in the same core network cannot be selected, the transmission of the tracking area update request (S506) is not omitted, and the GUMMEI that identifies the MME_C44, etc.
  • a tracking update response may be transmitted to the UE_A 10 including information for identifying the MME_C 44 to complete the tracking area update procedure.
  • the eNB 47 may transmit a message requesting the MME_C 44 to delete the context of the UE_A10.
  • the tracking area update procedure (S58) may be omitted.
  • eNB 47 detects the identification information of the core network to which UE_A 10 is connected, and determines the MME based on the identification information of the core network. A method of selecting and connecting will be described.
  • Figure 8 shows the tracking area update procedure.
  • the MME information included in the storage unit 240 of the eNB 47 may be information in which the MME identification information and the service area information are associated as illustrated in FIG. 3B, as illustrated in FIG.
  • the core network type may be associated with the information shown in FIG.
  • the MME identification information 242 may be GUMMEI.
  • the MME group number included in GUMMEI may indicate the core network type to which the MME is connected.
  • the eNB 47 has a function of identifying the core network to which the MME is connected based on the MME identification information.
  • a trigger for transmitting a tracking area update request is generated in UE_A 10 (S402).
  • the transmission trigger for the tracking area update request is not particularly limited, but may be a trigger that occurs periodically, for example, and may be the same as a conventional trigger, such as the end of the timer count. At this time, it is assumed that UE_A 10 has moved to the connection area of eNB 47.
  • UE_A 10 transmits a tracking area update request message to eNB 47 based on the tracking area update request trigger (S601).
  • UE_A10 may transmit the message including the identification information of UE_A10, the identification information of MME_B42 to which UE_A10 is connected before moving, and tracking area information indicating the position of UE_A10.
  • GUTI GloballyAUnique Temporary Identity assigned globally unique to UE_A10 may be used as the identification information of UE_A10.
  • GUMEI may be used as the identification information of MME_B42.
  • GUMMEI may be configured to be included in GUTI.
  • the MME identification information (old GUMMEI) to which the UE was connected before moving may include identification information for identifying the core network to which the UE_A 10 was connected. More specifically, the group identification information included in the old GUMMEI may be information corresponding to identification information for identifying the core network to which the UE_A 10 is connected.
  • the UE_A 10 may include identification information for identifying the core network, which is information independent of the identification information of the MME connected before the movement, in the message.
  • ENB 47 receives the tracking area update request message from UE_A 10.
  • the eNB 47 acquires identification information (old GUMMEI or independent core network type identification information) included in the message for the UE_A10 core network.
  • the eNB 47 selects the MME whose area information and core network type information most closely match the UE from the MME information 242 (S602).
  • the eNB 47 transmits a tracking area update request message to the selected MME (here, MME_D 46) based on the selection of the MME (S604).
  • the message includes the MME identification information (old GUMMEI) to which the UE_A 10 was connected before moving and the tracking area information indicating the location of the UE_A 10.
  • MME identification information old GUMMEI
  • the identification information of the MME before moving is the GUMEI of the MME_B42.
  • the tracking area identification information is UE location registration area information.
  • MME_D 46 receives a tracking area update request from eNB 47.
  • the MME_D 46 transmits a context request message to the MME_B 42 based on the identification information of the MME included in the message (S606).
  • tracking area update request message received from the eNB 47 includes identification information of the core network to which the MME_D 46 is connected.
  • MME_B 42 receives the context request message from MME_D 46.
  • the MMEB 42 acquires identification information of the core network connected to the MME_D 46 included in the message, compares the acquired core network with the core network connected to the MME_B 42, and determines whether or not MME reselection is necessary.
  • the acquired core network the core network to which the MME_D 46 is connected
  • the core network of the MME_B 42 are the same, it is determined that MME reselection is unnecessary (S608).
  • the MME_B 42 transmits a context response message to the MME_D 46 based on the determination that reselection is unnecessary (S610).
  • the message is the UE_A10 context stored in the storage unit of the MME_B42, and includes the MM context and the EPS bearer context.
  • the MME_B 42 may transmit a context response message to the MME_D 46 based on the reception of the message (S610).
  • the message includes the context of UE_A 10 and identification information of the core network to which MME_B 42 is connected.
  • the context of UE_A 10 may include a conventional MM context or an EPS bearer context.
  • the MME_D 46 receives the context response message from the MME_B 42 as a response to the context request message.
  • the MME_D46 acquires the identification information of the core network to which MME_B42 is connected, and the core network to which MME_D46 is connected Compare with type.
  • the MME_D 46 determines that MME reselection is unnecessary (S612).
  • the MME_D 46 stores the context of the UE_A 10 included in the message in the storage unit based on the reception of the context or the determination that reselection is unnecessary. Further, the tracking area information included in the context is updated using the tracking area information indicating the position of the UE_A 10 included in the tracking area update request message received from the eNB 47.
  • the MME_D 46 transmits a tracking area update response message to the eNB 47 based on the reception of the context response message (S614).
  • the message includes an information element for notifying that the tracking area has been updated.
  • ENB 47 receives the tracking area update response message from MME_D 46.
  • the eNB 47 transmits a tracking area update response message to the UE_A 10 based on the reception of the message (S616).
  • the message includes an information element for notifying that the tracking area update has been completed and identification information (for example, GUMMEI) of the new MME MME_D46.
  • UE_A 10 receives the tracking area update response message from eNB 47. Acquire new MME identification information included in the received message.
  • the eNB 47 stores the MME core network type, and the UE_A 10 transmits information for identifying the core network, whereby the eNB 47 can select the MME based on the core network identification information.
  • the number of tracking area update procedures can be reduced.
  • the eNB 47 does not necessarily have to store the identification information of the MME core network in advance. Therefore, for example, the eNB 47 stores the identification information of the core network of the MME, and when the UE_A 10 transmits the tracking area update request including the identification information of the core network, the MME described in this modification example. In other cases, the eNB 47 performs processing such as connection using the method described in the tracking area update procedure with MME relocation described in 1.3.1. May be.
  • the eNB 47 performs connection based on the MME selection process described in the present modification, or the eNB 47 connects using the method described in the tracking area update procedure with MME relocation described in 1.3.1.
  • Setting information for detecting whether to perform the process may be held in advance, and processing may be selected based on the setting information.
  • the setting information may be information set in the eNB 47 by the operator based on an operator policy such as a mobile communication carrier.
  • a program that operates in each device is a program that controls a CPU or the like (a program that causes a 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 non-volatile memory card, etc.), an optical recording medium / a magneto-optical recording medium (for example, DVD (Digital Versatile Disc), MO (Magneto Optical) Disc), MD (Mini Disc), CD (Compact Disc), BD, etc.), magnetic recording medium (eg, magnetic tape, flexible disk, etc.), etc.
  • a semiconductor medium for example, ROM, a non-volatile memory card, etc.
  • an optical recording medium / a magneto-optical recording medium for example, DVD (Digital Versatile Disc), MO (Magneto Optical) Disc), MD (Mini Disc), CD (Compact Disc), BD, etc.
  • magnetic recording medium eg, magnetic tape, flexible disk, etc.
  • 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 formed as a chip, 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.
  • LTE and WLAN are described as examples of the radio access network, but they may be connected by WiMAX instead of WLAN.
PCT/JP2015/068624 2014-07-01 2015-06-29 基地局装置、第１の位置管理装置、端末装置、通信制御方法、および通信システム WO2016002692A1 (ja)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP15814108.5A EP3166363A4 (en) 2014-07-01 2015-06-29 Base station device, first position management device, terminal device, communication control method, and communication system
JP2016531350A JP6637418B2 (ja) 2014-07-01 2015-06-29 第１のコアネットワーク装置、基地局装置及び通信制御方法
US15/320,957 US10136407B2 (en) 2014-07-01 2015-06-29 Base station device, first location management device, terminal device, communication control method, and communication system
CN201580031669.XA CN106465323B (zh) 2014-07-01 2015-06-29 第1核心网络装置及其通信控制方法、基站装置及其通信控制方法
US16/180,773 US11026208B2 (en) 2014-07-01 2018-11-05 Base station device, first location management device, terminal device, communication control method, and communication system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2014135495 2014-07-01
JP2014-135495 2014-07-01

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US15/320,957 A-371-Of-International US10136407B2 (en) 2014-07-01 2015-06-29 Base station device, first location management device, terminal device, communication control method, and communication system
US16/180,773 Continuation US11026208B2 (en) 2014-07-01 2018-11-05 Base station device, first location management device, terminal device, communication control method, and communication system

Publications (1)

Publication Number Publication Date
WO2016002692A1 true WO2016002692A1 (ja) 2016-01-07

Family

ID=55019228

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2015/068624 WO2016002692A1 (ja) 2014-07-01 2015-06-29 基地局装置、第１の位置管理装置、端末装置、通信制御方法、および通信システム

Country Status (5)

Country Link
US (2) US10136407B2 (zh)
EP (1) EP3166363A4 (zh)
JP (1) JP6637418B2 (zh)
CN (1) CN106465323B (zh)
WO (1) WO2016002692A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017146075A1 (ja) * 2016-02-22 2017-08-31 日本電気株式会社 通信システム、通信方法、及び、非一時的なコンピュータ可読媒体
WO2019098389A1 (ja) * 2017-11-20 2019-05-23 シャープ株式会社 ＡＭＦ（Ａｃｃｅｓｓ ａｎｄ Ｍｏｂｉｌｉｔｙ Ｍａｎａｇｅｍｅｎｔ Ｆｕｎｃｔｉｏｎ）、ＵＥ（Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ）、ＳＭＦ（Ｓｅｓｓｉｏｎ Ｍａｎａｇｅｍｅｎｔ Ｆｕｎｃｔｉｏｎ）、ＡＭＦの通信制御方法、ＵＥの通信制御方法及びＳＭＦの通信制御方法
JP2021073764A (ja) * 2021-01-06 2021-05-13 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． 通信方法、デバイス、及びシステム
US11412477B2 (en) 2016-09-29 2022-08-09 Huawei Technologies Co., Ltd. Communication method between core network device and terminal in communication system

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6630675B2 (ja) * 2014-10-06 2020-01-15 シャープ株式会社 Ｕｅ、基地局装置、ｕｅの通信制御方法及び基地局の通信制御方法
WO2016146219A1 (en) * 2015-03-18 2016-09-22 Nec Europe Ltd Communication system
JP6177845B2 (ja) * 2015-08-13 2017-08-09 株式会社Ｎｔｔドコモ 基地局、管理装置及び接続方法
JP2018538747A (ja) 2015-11-19 2018-12-27 エスケー テレコム カンパニー リミテッドＳｋ Ｔｅｌｅｃｏｍ Ｃｏ．， Ｌｔｄ． 移動通信システムにてコアネットワークを選択する方法及び装置
EP3494737B1 (en) * 2016-08-03 2021-05-26 Telefonaktiebolaget LM Ericsson (publ) Method and device for transmitting tracking area information
JP2020036055A (ja) * 2017-01-05 2020-03-05 シャープ株式会社 端末装置、コアネットワーク装置、及び通信制御方法
EP3698573B1 (en) 2017-10-17 2022-06-01 Telefonaktiebolaget LM Ericsson (publ) Pdn and pdu session type mapping and capability discovery
CN112042240B (zh) * 2018-06-25 2022-01-11 Oppo广东移动通信有限公司 网络设备配置终端设备的方法、终端设备和网络设备
CN113055960B (zh) * 2019-12-27 2023-02-24 北京融昱信息技术有限公司 基站重选方法、装置、设备及介质
CN114189853B (zh) * 2020-08-24 2023-12-12 海能达通信股份有限公司 一种终端的通信控制方法、装置及epc

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI20050369A0 (fi) * 2005-04-12 2005-04-12 Nokia Corp Verkkoelementin valinta
CN101355793B (zh) * 2007-07-27 2011-08-31 华为技术有限公司 识别用户设备的方法和装置及临时标识传递和分配方法
CN101370266B (zh) * 2007-08-19 2013-03-20 华为技术有限公司 切换方法、终端重新附着方法
JP5275366B2 (ja) * 2007-12-19 2013-08-28 テレフオンアクチーボラゲット エル エム エリクソン（パブル） Ｍｔおよびｍｏの呼のドメイン間調整
JP5538802B2 (ja) * 2008-11-04 2014-07-02 三菱電機株式会社 通信方法、移動体通信システム、移動端末および基地局制御装置
CN103703801B (zh) * 2011-08-09 2018-04-13 三菱电机株式会社 移动通信系统
US8983475B2 (en) * 2012-02-16 2015-03-17 Futurewei Technologies, Inc. System and method for partner network sharing architecture
CN104081826B (zh) * 2012-03-16 2018-04-13 Lg 电子株式会社 用于在无线通信系统中处理nas信令请求的方法和装置
EP2645672A1 (en) * 2012-03-30 2013-10-02 Vodafone IP Licensing Limited Method for discovering capabilities of offline users
WO2015062098A1 (zh) * 2013-11-01 2015-05-07 华为技术有限公司 一种网络选择方法及核心网设备

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "P-CR on Re-routing before NAS security setup", SA WG2 MEETING #103 S 2-141676, 13 May 2014 (2014-05-13), XP050836180, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_103_Phoenix/Docs/S2-141676.zip> *
N TT DOCOMO: "P-CR on Solution 1: Redirection Solution", SA WG2 MEETING #103 S 2-141710, 13 May 2014 (2014-05-13), XP050805066, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_103_Phoenix/Docs/S2-141710.zip> *
NTT DOCOMO: "Addition of Subscription Information for Selecting a Specific Network", SA WG2 MEETING #99 S 2-133742, 27 September 2013 (2013-09-27), pages 1,15 - 21, XP050727079, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_99_Xiamen/Docs/S2-133742.zip> *
See also references of EP3166363A4 *

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017146075A1 (ja) * 2016-02-22 2017-08-31 日本電気株式会社 通信システム、通信方法、及び、非一時的なコンピュータ可読媒体
JP2017152770A (ja) * 2016-02-22 2017-08-31 日本電気株式会社 通信システム、通信方法、及び、プログラム
US11412477B2 (en) 2016-09-29 2022-08-09 Huawei Technologies Co., Ltd. Communication method between core network device and terminal in communication system
US11832215B2 (en) 2016-09-29 2023-11-28 Huawei Technologies Co., Ltd. Communication method between core network device and terminal in communication system
WO2019098389A1 (ja) * 2017-11-20 2019-05-23 シャープ株式会社 ＡＭＦ（Ａｃｃｅｓｓ ａｎｄ Ｍｏｂｉｌｉｔｙ Ｍａｎａｇｅｍｅｎｔ Ｆｕｎｃｔｉｏｎ）、ＵＥ（Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ）、ＳＭＦ（Ｓｅｓｓｉｏｎ Ｍａｎａｇｅｍｅｎｔ Ｆｕｎｃｔｉｏｎ）、ＡＭＦの通信制御方法、ＵＥの通信制御方法及びＳＭＦの通信制御方法
JP2019096952A (ja) * 2017-11-20 2019-06-20 シャープ株式会社 ユーザ装置
US11405842B2 (en) 2017-11-20 2022-08-02 FG Innovation Company Limited Access and mobility management function (AMF), user equipment (UE), session management function (SMF), communication control method for AMF, communication control method for UE, and communication control method for SMF
AU2018369297B2 (en) * 2017-11-20 2023-03-02 FG Innovation Company Limited Access and mobility management function (AMF), user equipment (UE), session management function (SMF), communication control method for AMF, communication control method for UE, and communication control method for SMF
JP7441596B2 (ja) 2017-11-20 2024-03-01 鴻穎創新有限公司 ユーザ装置、セッション管理機能及び通信制御方法
JP2021073764A (ja) * 2021-01-06 2021-05-13 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． 通信方法、デバイス、及びシステム
JP7262491B2 (ja) 2021-01-06 2023-04-21 華為技術有限公司 通信方法、デバイス、及びシステム

Also Published As

Publication number Publication date
US20170164317A1 (en) 2017-06-08
US11026208B2 (en) 2021-06-01
EP3166363A1 (en) 2017-05-10
JP6637418B2 (ja) 2020-01-29
JPWO2016002692A1 (ja) 2017-04-27
US10136407B2 (en) 2018-11-20
US20190075542A1 (en) 2019-03-07
CN106465323A (zh) 2017-02-22
CN106465323B (zh) 2021-06-22
EP3166363A4 (en) 2018-04-04

Similar Documents

Publication Publication Date Title
JP6637418B2 (ja) 第１のコアネットワーク装置、基地局装置及び通信制御方法
US11770761B2 (en) Base station device, terminal device, location management device, and control method
US11089542B2 (en) Terminal apparatus, base station apparatus, mobility management entity (MME), and communication control method
US11785454B2 (en) Terminal apparatus, base station apparatus, mobility management entity (MME), and communication control method
RU2695809C2 (ru) Способы и объект управления мобильностью (мме) для перенаправления пользовательского оборудования (ue) на назначенный узел базовой сети
US20170318613A1 (en) Base station device, position management device, terminal device, and control method
US20160353498A1 (en) Communication control method, position management device, base station device, terminal device, and communication system
WO2016117505A1 (ja) 基地局装置、端末装置、及び通信制御方法
JP6749905B2 (ja) ＵＥの通信制御方法、ＰｒｏＳｅ機能部の通信制御方法、ＵＥ及びＰｒｏＳｅ機能部
WO2016117491A1 (ja) 基地局装置、端末装置、及び通信制御方法
US20170111273A1 (en) Server device and terminal device
US20220345997A1 (en) User equipment and core network apparatus
US20220295279A1 (en) User equipment, intra-core network apparatus, and communication control method
US20220256450A1 (en) User equipment, intra-core network apparatus, and communication control method
US20200329522A1 (en) Terminal device, pgw, and twag
US20220345885A1 (en) User equipment (ue)
US20220369220A1 (en) User equipment (ue)
EP4322689A1 (en) User equipment (ue) and communication control method executed by ue
US20240163784A1 (en) User equipment (ue) and communication control method performed by ue
EP4322690A1 (en) User equipment (ue) and communication control method executed by ue

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: 15814108

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2016531350

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 15320957

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2015814108

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015814108

Country of ref document: EP