WO2016056321A1 - 基地局装置、端末装置、位置管理装置および制御方法 - Google Patents
基地局装置、端末装置、位置管理装置および制御方法 Download PDFInfo
- Publication number
- WO2016056321A1 WO2016056321A1 PCT/JP2015/074483 JP2015074483W WO2016056321A1 WO 2016056321 A1 WO2016056321 A1 WO 2016056321A1 JP 2015074483 W JP2015074483 W JP 2015074483W WO 2016056321 A1 WO2016056321 A1 WO 2016056321A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- core network
- identification information
- mme
- information
- request message
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/18—Selecting a network or a communication service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/16—Discovering, processing access restriction or access information
-
- 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
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/04—Interfaces between hierarchically different network devices
- H04W92/045—Interfaces between hierarchically different network devices between access point and backbone network device
Definitions
- the present invention relates to a base station device, a terminal device, a location management device, and a control method.
- 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.
- 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 of the present invention is a base station apparatus connected to a first core network including a first location management device and a second core network including a second location management device, and at least a first Receiving a context release request message or a route reconfiguration request message including identification information of one from the first location management device, the first identification information indicating or requesting connection to the second core network
- the attach request message or the tracking area update request message is received from the terminal device, the second location management device is selected based on the first identification information, and the attach request message or the tracking area update request message is selected. It transmits to a position management apparatus, It is characterized by the above-mentioned.
- the base station apparatus of the present invention is characterized in that the first identification information is a core network type associated with the second core network.
- the base station apparatus of the present invention is characterized in that the first identification information is group identification information of a location management apparatus included in the second core network.
- the base station apparatus of the present invention starts a timer upon reception of the context release request message, and selects the second location management apparatus based on the first identification information when the timer is being executed. Is not executed, an attach request message or a tracking area update request message is transmitted to the first location management device.
- the base station apparatus of the present invention transmits an RRC connection release request message to the terminal apparatus based on the reception of the context release request message, and the RRC connection release request message instructs to connect to the second core network or
- the requested identification information includes at least second identification information.
- the terminal device of the present invention receives a detach request message including at least first identification information and information indicating that attachment is required from the first location management device included in the first core network,
- the identification information is identification information for instructing or requesting connection to the second core network, and based on reception of the detach message, transmits an attach request message including at least the second identification information to the base station apparatus.
- the second identification information is identification information for instructing or requesting connection to the second core network, and the gateway included in the second core network upon completion of the attach procedure. It is characterized in that a PDN (Packet Data Network) connection is established with the device.
- PDN Packet Data Network
- the terminal device of the present invention receives a paging message including at least first identification information from the first location management device included in the first core network, and the first identification information is connected to the second core network.
- Identification information instructing or requesting to be transmitted, and based on reception of the paging message, the service request message is transmitted to the first location management device, and is a response to the service request message, and identification information indicating at least a detached state Is received from the first location management device, and based on the reception of the service reject message, an attach request message including at least the second identification information is transmitted to the base station device to start the attach procedure.
- the second identification information indicates connection to the second core network. Or identification information requesting, upon the completion of the attach procedure, and establishes a PDN (Packet Data Network) connection between the gateway device included in the second core network.
- PDN Packet Data Network
- the terminal device is characterized in that the first identification information and / or the second identification information is a core network type associated with the second core network.
- the terminal device of the present invention is characterized in that the first identification information and / or the second identification information is group identification information of a location management device included in the second core network.
- the location management device of the present invention is a location management device included in the first core network, and transmits a context release request message or a route reconfiguration request message including at least first identification information to the base station device,
- the identification information 1 is identification information for instructing or requesting connection to the second core network, and receives a response message of a context release request message or a route reconfiguration request message from the base station apparatus. .
- the location management device of the present invention transmits a detach request message or a paging message including at least first identification information to the terminal device, and after transmitting the detach request message or the paging message, sends a context release request message or a route reconfiguration request message. It is characterized by transmitting.
- the location management apparatus of the present invention is characterized in that the first identification information is a core network type associated with the second core network.
- the location management device of the present invention is characterized in that the first identification information is group identification information of the location management device included in the second core network.
- the base station apparatus control method is a base station apparatus control method connected to a first core network including a first location management device and a second core network including a second location management device.
- the base station apparatus control method is a base station apparatus control method connected to a first core network including a first location management device and a second core network including a second location management device. Receiving a context release request message or a route reconfiguration request message including at least first identification information from the first location management device; and connecting the first identification information to the second core network.
- the base station apparatus control method according to the present invention is characterized in that the first identification information is a core network type associated with the second core network.
- the base station apparatus control method of the present invention is characterized in that the first identification information is group identification information of a location management apparatus included in the second core network.
- the base station apparatus control method includes a step of transmitting an RRC connection release request message to a terminal apparatus based on reception of a context release request message, and an RRC connection release request message is connected to the second core network. Including at least second identification information for identifying or instructing to perform the identification information.
- the terminal device control method of the present invention includes a step of receiving a detach request message including at least first identification information and information indicating that attachment is required from a first location management device included in the first core network.
- the first identification information is identification information for instructing or requesting connection to the second core network.
- the first identification information includes at least the second identification information as a base.
- the step of transmitting to the station apparatus and starting the attach procedure, and the second identification information is identification information for instructing or requesting connection to the second core network.
- PDN Packet Data Network
- the terminal device control method of the present invention includes a step of receiving a paging message including at least first identification information from a first location management device included in the first core network, and the first identification information includes a second Identification information for instructing or requesting connection to the core network of the mobile station, the step of transmitting a service request message to the first location management device based on reception of the paging message, and a response to the service request message, at least A step of receiving a service reject message including identification information indicating a detached state from the first location management device, and a base station device including an attach request message including at least the second identification information based on reception of the service reject message To initiate an attach procedure, and 2 is identification information for instructing or requesting connection to the second core network. Upon completion of the attach procedure, the identification information of PDN (Packet Data Network) connection is established.
- PDN Packet Data Network
- the terminal device control method of the present invention is characterized in that the first identification information and / or the second identification information is a core network type associated with the second core network.
- the terminal device control method of the present invention is characterized in that the first identification information and / or the second identification information is group identification information of a location management device included in the second core network.
- the location management device control method is a location management device control method included in a first core network, and transmits a context release request message or a route reconfiguration request message including at least first identification information to a base station.
- the step of transmitting to the device, and the first identification information is identification information for instructing or requesting connection to the second core network, and a response message of the context release request message or the route reconfiguration request message is sent to the base station device And receiving from.
- the position management device control method of the present invention includes a step of transmitting a detach request message or paging message including at least first identification information to a terminal device, and a context release request message or route after transmitting the detach request message or paging message. Transmitting a reset request message.
- the control method of the location management device is characterized in that the first identification information is a core network type associated with the second core network.
- the position management device control method of the present invention is characterized in that the first identification information is group identification information of the location management device included in the second core network.
- the present invention in a communication network constituting a multiplexed core network, it is possible to realize a procedure for the terminal device to switch and connect the 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 a mobile terminal device UE10, 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. ing.
- 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.
- the type such as type 1 or type 2 may be 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.
- a communication carrier assigns an identification number to a core network and identifies a plurality of multiplexed core networks by the identification number, or a plurality of mobile communication carriers including MVNO each constitute a core network
- the core network may be identified by information for identifying the mobile communication carrier.
- the UE 10 may be assigned a core network type in advance.
- the UE 10 may be managed as a terminal that can be connected to a type 2 core network.
- the UE 10 may be managed as a terminal that can be connected to the type 1 core network in a place where the type 2 core network is not deployed.
- Such management information may be stored as subscriber information in a control device inside the core network such as HSS (Home Subscriber Server) and MME (Mobility Management Entity). Further, such management information may also be stored in the UE 10.
- HSS Home Subscriber Server
- MME Mobility Management Entity
- 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 includes MME (Mobility Management Entity) _A40.
- the core network (type 2) 92 includes the MME_B 42 in the core network (type 2) 92.
- the core network is connected to PDN (Packet Data Network).
- the PDN is a packet data service network that provides a communication service to the UE 10, and may be configured for each service.
- a communication terminal is connected to the PDN, and the UE 10 can transmit and receive user data to and from the communication terminal arranged in the PDN.
- the core network (type 1) 90 may be connected to the PDN_A 100, and the core network (type 2) 92 may be connected to the PDN_B 102. In this way, the core networks may be connected to different PDNs.
- PDN_A 100 and PDN_B 102 may be 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.
- Core networks include HSS (Home Subscriber Server), AAA (Authentication, Authorization, Accounting), PCRF (Policy and Charging Rules), PGW (Packet Data Network Gateway), ePDG (enhanced Packet Data Gateway), SGW (Serving Gateway) ) And MME.
- HSS Home Subscriber Server
- AAA Authentication, Authorization, Accounting
- PCRF Policy and Charging Rules
- PGW Packet Data Network Gateway
- ePDG enhanced Packet Data Gateway
- SGW Serving Gateway
- Such devices may be arranged for each core network.
- the multiplexing of the core network is intended to distribute control message traffic and user data traffic. Therefore, management devices such as HSS, AAA, and PCRF are arranged for each core network. Instead, it may be shared by a plurality of core networks.
- a user data transfer device such as PGW or SGW is not arranged for each core network, It may be shared in the core network.
- the core network (type 1) 90 will be described mainly with an example including the HSS 50, AAA 55, PCRF 60, PGW_A 30, ePDG 65, SGW_A 35, and MME_A 40.
- the core network (type 2) 92 will be described mainly with reference to an example configured with HSS 50, AAA 55, PCRF 60, PGW_B32, ePDG65, SGW_B37, and MME_B42.
- HSS50, AAA55, PCRF60, and ePDG65 are shared by each core network. Further, an example in which MME, PGW, and SGW are arranged in each core network will be mainly described.
- Each core network can be connected to a plurality of access networks (LTE AN80, WLAN ANb75, WLAN ANa70).
- the radio access network may be configured to be connected to a plurality of different access networks, or may be configured to be connected to any one access network. Furthermore, the UE 10 can wirelessly connect to the radio access network.
- the access network connectable with the WLAN access system includes a WLAN access network b (WLAN ANb75) connected to the core network via the ePDG 65, a WLAN access network a connected to the PGW (PGW_A30, PGW_B32), the PCRF 60, and the AAA 55. (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.
- PGW_A 30 is connected to PDN_A 100, SGW_A 35, ePDG 65, WLAN ANa 70, PCRF 60 and AAA 55, and is a relay device that transfers user data as a gateway device between PDN_A 100 and core network 90.
- the SGW_A 35 is connected to the PGW_A 30, the MME_A 40, and the LTE AN 80 and is a relay device that transfers user data 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_A 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_C may be configured as a location management device different from MME_A40.
- the MME_C may be connected to the SGW_A 35, the LTE AN 80, and the HSS 50 in the same manner as the MME_A 40.
- MME_C and MME_A 40 may be connected. Thereby, MME_C 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.
- AAA 55 is connected to PGW_A 30, HSS 50, PCRF 60, and WLAN ANa 70, and performs access control of UE 10 connected via WLAN ANa 70.
- PCRF 60 is connected to PGW_A 30, WLAN ANa 75, AAA 55, and PDN 100, and performs QoS management for data delivery. For example, QoS management of the communication path between the UE 10 and the PDN_A 100 is performed.
- the ePDG 65 is connected to the PGW_A 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 the UE 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.
- each device included in the core network (type 2) 92 will be briefly described.
- PGW_B 32 is connected to PDN_B 102, SGW_B 37, ePDG 65, WLAN ANa 70, PCRF 60 and AAA 55, and is a relay device that transfers user data as a gateway device of PDN 102 and core network 92.
- the SGW_B 37 is connected to the PGW_B 32, the MME_B 42, and the LTE AN 80, and is a relay device that transfers user data as a gateway device between the core network (type 2) 92 and the LTE AN 80.
- the MME_B 42 is connected to the SGW_B 37, 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 10 via the LTE AN 80.
- the core network (type 2) 92 may include a plurality of location management devices.
- MME_D may be configured as a location management device different from MME_B42.
- the MME_D may be connected to the SGW_B 37, the LTE AN 80, and the HSS 50 in the same manner as the MME_B 42.
- MME_D and MME_B42 may be connected. Thereby, MME_D and MME_B42 may perform transmission / reception of the context of UE10.
- the HSS 50 is connected to the MME_B 42 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_B 42, for example.
- AAA55, PCRF60, and ePDG65 have already been described and will not be described.
- 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 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 be MMEGI (MME Group Identifier).
- MMEGI MME Group Identifier
- a different MMEGI may be stored for each core network type.
- 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.
- the eNB 45 may store the UE context information in the active state (Connected state) in which the radio resource is allocated to the UE 10 while the UE 10 is attached.
- GUTI Globally10Unique Temporary Identity assigned globally unique to UE10 may be used as the identification information of UE10.
- subscriber information such as IMGI (International Mobile Subscriber Identity) may be used.
- identification information such as P-TMSI (Packet (Temporary Mobile Subscriber Identity) may be used. Or it is good also as identification information of UE10 combining two or more of these identification 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_A 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 be MMEGI (MME Group Identifier).
- MMEGI MME Group Identifier
- a different MMEGI may be stored for each core network type.
- 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 context information 344 may store UE identification information.
- GUTI Globally10Unique Temporary Identity assigned globally unique to UE10
- subscriber information such as IMGI (International Mobile Subscriber Identity) may be used.
- identification information such as P-TMSI (Packet (Temporary Mobile Subscriber Identity) may be used.
- P-TMSI Packet (Temporary Mobile Subscriber Identity) may be used.
- the MME_A 40 may store context information when the UE 10 is attached. That is, the context information may be generated by attaching.
- the UE 10 is connected to the core network (type 1) 90. More specifically, the UE 10 is connected to the eNB 45. Furthermore, UE10 is connected to MME_A40 via eNB45. Furthermore, the UE 10 has established a PDN connection with the PGW_A 30.
- the PDN connection is a communication path for delivering user data.
- the core network (type 1) 90 may be configured to include PGW_A30
- the core network (type 2) 92 may be configured to include PGW_B32.
- SGWs may be arranged in the core network (type 1) 90 and the core network (type 2) 92, respectively.
- the SGW_A 35 may be included in the core network (type 1) 90
- the SGW_B 37 may be included in the core network (type 2) 92.
- the UE 10 in the initial state, has established a PDN connection with the PGW_A 30. Furthermore, the PDN connection between the UE 10 and the PGW_A 30 is established via the SGW_A 35.
- the identification information of the UE 10 may use GUTI (Globally Unique Unique Temporary Identity) assigned to the UE 10 globally and uniquely.
- subscriber information such as IMGI (International Mobile Subscriber Identity) may be used.
- identification information such as P-TMSI (Packet (Temporary Mobile Subscriber Identity) may be used.
- P-TMSI Packet (Temporary Mobile Subscriber Identity) may be used.
- the MME identification information may be a GUMMEI (Globally Unique MME Identifier) corresponding to each MME.
- GUMMEI Globally Unique MME Identifier
- the MME identification information may be an MMEGI (MME Group Identifier) that identifies an MME group.
- the eNB 45 holds MMEGI and GUMMEI belonging to the MME group identified by the MMEGI in advance, and when receiving the MMEGI, selects the GUMMEI belonging to the MMEGI based on the received MMEGI. Can do.
- the eNB 45 may associate the MMEGI having the MME belonging to the core network (type 2) as a group with the MMEGI of the MME belonging to the group such as the MME_B42 and store the MMEGI in the MME information in advance.
- the MME_A 40 detects a trigger for starting a procedure for changing the core network to which the UE 10 is connected (S502).
- the MME_A 40 may detect the trigger based on the update of the subscriber information. More specifically, based on the change of the subscriber information corresponding to the UE 10 stored in the HSS 50, the HSS 50 transmits a control message including identification information indicating the change to the MME_A 40. The MME_A 40 may detect that it is necessary to change the core network to which the UE 10 is connected based on reception of a control message transmitted by the HSS 50 or identification information included in the control message.
- the identification information included in the control message may be core network information indicating the core network type 2 or information such as a flag indicating that a change of the core network type is requested.
- the control message may be a control message for requesting switching of the core network. Further, the control message may include identification information of the UE 10.
- the eNB 45 may receive the MMEGI that groups the MMEs belonging to the core network (type 2) and perform the MME selection process. Note that the eNB 45 may select the MME_B 42 based on the received MMEGI.
- the MME_A 40 may detect a trigger based on the core network (type 2) 92 being configured. More specifically, it may be started when a control device included in the core network (type 2) 92 such as MME_B42 or PGW_B32 is installed. The core network operator may install such a control device and manually operate the MME_A 40 based on the installation. The MME_A 40 may detect a trigger based on such an operator's manual operation.
- the MME_A 40 transmits a detach request message to the UE 10 based on the trigger detection (S504).
- the MME_A 40 may transmit the detach request message including at least the first instruction information (Indicator 1).
- the first instruction information may be information requesting or instructing to switch the core network.
- the first instruction information may be a core network type.
- the core network type may be information for identifying the core network (type 2). Specifically, NRI (Network Resource Identifiers) for identifying the core network (type 2) 92 may be used.
- NRI Network Resource Identifiers
- the first instruction information may be information indicating that the core network type is switched. More specifically, the information indicating that the core network type is switched may be a reason display information element (Cause Value) indicating that the core network needs to be switched.
- the information indicating that the core network type is switched may be a reason display information element (Cause Value) indicating that the core network needs to be switched.
- the first instruction information may be information indicating that the UE 10 needs to be reattached. More specifically, the information indicating that the UE 10 needs to be reattached may be a reason display information element (Cause Value) indicating Attach Required.
- a reason display information element (Cause Value) indicating Attach Required.
- the first instruction information may be MME identification information.
- the MME identification information may be information for identifying the MME included in the core network (type 2) 92.
- the MME identification information may be GUMMEI for identifying MME_B42.
- the MMEGI may identify a group of MMEs included in the core network (type 2) 92.
- the first instruction information needs to be reattached as described above, the information for requesting or instructing to switch the core network, the information indicating that the core network type and the core network type are switched, and the like.
- the information which shows 2 and the information which combined 2 or more identification information of MME may be sufficient.
- the first instruction information that is combined two or more in this way is information indicating that the core network type or the core network type is switched, information indicating that reattachment is necessary, or identification information of the MME. It may be used.
- the MME_A 40 may transmit a UE context release message to the eNB 45 in parallel with the transmission of the detach request message or after the transmission of the detach request message (S506).
- the MME_A 40 may request to release the radio resource.
- the MME_A 40 may transmit a UE context release message including at least the second instruction information (Indicator 2).
- the second instruction information may be information requesting or instructing to switch the core network.
- the second instruction information may be a core network type.
- the core network type may be information for identifying the core network (type 2). Specifically, NRI (Network Resource Identifiers) for identifying the core network (type 2) 92 may be used.
- NRI Network Resource Identifiers
- the second instruction information may be information indicating that the core network type is switched. More specifically, the information indicating that the core network type is switched may be a reason display information element (Cause Value) indicating that the core network needs to be switched.
- the information indicating that the core network type is switched may be a reason display information element (Cause Value) indicating that the core network needs to be switched.
- the second instruction information may be information indicating that the UE 10 needs to be reattached. More specifically, the information indicating that the UE 10 needs to be reattached may be a reason display information element (Cause Value) indicating Attach Required.
- a reason display information element (Cause Value) indicating Attach Required.
- the second instruction information may be MME identification information.
- the MME identification information may be information for identifying the MME included in the core network (type 2) 92.
- the MME identification information may be GUMMEI for identifying MME_B42.
- the MMEGI may identify a group of MMEs included in the core network (type 2) 92.
- the second instruction information needs to be reattached as described above, the information that requests or instructs to switch the core network, the information that indicates the core network type, and the core network type that is to be switched.
- the information which shows 2 and the information which combined 2 or more identification information of MME may be sufficient.
- the second instruction information that is a combination of two or more in this way is information indicating that the core network type or the core network type is switched, information indicating that reattachment is necessary, or identification information of the MME. It may be used.
- the MME_A 40 may transmit a transmission UE context release message including at least the identification information of the UE 10 and a timer value.
- the timer value may be a timer value used by the eNB 45 for selecting an MME.
- the eNB 45 receives the UE context release message from the MME_A 40.
- the eNB 45 may execute the MME information update process based on the information included in the UE context release message (S508). More specifically, the MME information update process may be executed based on the second instruction information.
- the MME information update process is a process of updating the MME information so that the eNB 45 selects an MME included in the core network (type 2) 92 in the MME selection performed in accordance with the reception of the attach request message transmitted by the UE 10. It may be.
- the eNB 45 may store the identification information of the UE 10 and the second instruction information in association with each other in the MME information update process.
- the eNB 45 may continue to hold the UE context information without deleting it by acquiring the second instruction information. On the other hand, the eNB 45 may delete the UE context information when the second instruction information is not acquired.
- the eNB 45 may start a timer count based on the second instruction information. The eNB 45 may continue to hold the updated MME information or UE context while the timer is being executed. Furthermore, when the timer is consumed or when the timer is stopped for some reason, the eNB 45 may delete the updated MME information or UE context.
- timer value a value held in advance by the eNB 45 may be used, or a timer value included in the UE context release message may be used.
- the eNB 45 may continue to hold the MME information held before the MME information update process.
- MMEI corresponding to the MME_A 40 included in the core network (type 1) 90, MMEGI indicating the group of MMEs to which the MME_A 40 belongs may be kept.
- the MME information update process is completed.
- the eNB 45 may transmit the RRC connection release message to the UE 10 based on the reception of the UE context release message or the completion of the MME information update process (S510).
- the eNB 45 may release the radio resource allocated to the UE 10 based on the transmission of the UE context release message.
- the eNB 45 may transmit the UE context release message including information that requires a response, such as setting the Acknowledge mode to 1.
- the UE 10 transmits a response to the UE context release message to the eNB 45 as a response to the UE context release message.
- the eNB 45 may release the radio resource allocated to the UE 10 based on the reception of the response message.
- the eNB 45 may continue to hold the UE 10 context including the identification information of the UE 10 when the timer is being executed when the UE context release message is transmitted or the response message is received. Alternatively, the eNB 45 deletes the UE context, but may store the identification information of the UE 10 and the second instruction information in association with each other during execution of the timer.
- the RRC connection release message may be transmitted including at least the third instruction information (Indicator 3).
- the third instruction information may be information requesting or instructing to switch the core network.
- the third instruction information may be identification information indicating that the UE 10 is requested or instructed to reattach.
- the identification information for requesting reattachment may be a reason display information element (Cause Value) that is Attach Required.
- the third instruction information may be identification information indicating that the UE 10 needs a tracking area update procedure.
- the identification information indicating that the tracking area update procedure is necessary may be a reason display information element (Cause Value) of TAU Request.
- the third instruction information may be identification information indicating that the core network needs to be switched.
- the identification information indicating that the core network needs to be switched may be a core network type that identifies the core network (type 2) 92.
- NRI Network Resource Identifiers
- the third instruction information may be MME identification information.
- the MME identification information may be information for identifying the MME included in the core network (type 2) 92.
- the MME identification information may be GUMMEI for identifying MME_B42.
- the MMEGI may identify a group of MMEs included in the core network (type 2) 92.
- the third instruction information requires information for requesting or instructing switching of the core network, identification information indicating requesting reattachment to the UE 10, and a tracking area update procedure for the UE 10 as described above.
- Information obtained by combining two or more identification information indicating that there is identification information indicating that switching of the core network is necessary, and identification information of the MME may be used.
- the third instruction information combined two or more in this way is identification information indicating that the UE 10 is requested to reattach, or identification information indicating that the UE 10 needs a tracking area update procedure, or a core It may be used as identification information indicating that network switching is necessary, or MME identification information.
- the eNB 45 transmits a context release completion message to the MME_A 40 as a response to the UE context release message (S512).
- the context release completion message is a response message to the UE context release message.
- the context release completion message indicates that these processes are completed. It becomes a message to notify.
- the eNB 45 when the eNB 45 performs the MME information update process based on the acquisition of the second instruction information and keeps the MME information and the like based on the MME information update process, the eNB 45 or the core network (type 2) 92
- the UE context release completion message may be transmitted including information indicating that the MME information is held.
- the MME_A 40 may receive the UE context release completion message and delete the UE context held by the MME_A 40.
- the UE 10 may receive the detach request message and start the attach procedure. Note that the UE 10 may start the attach procedure based on the first instruction information. In this case, the UE 10 may start the attach procedure even if the UE 10 does not necessarily receive the RRC connection release message.
- the UE 10 may start the attach procedure after receiving the RRC connection release message.
- the UE 10 may start the attach procedure based on the reception of the first instruction information and the RRC connection release message.
- the UE 10 may start the attach procedure based on the third instruction information.
- the attach procedure may be started based on the first instruction information and the third instruction information.
- the UE 10 may delete the held MME information based on the reception of the first instruction information, the second instruction information, or both.
- the information on the MME to be deleted may be the GUMEI of MME_A40.
- the MME information to be deleted may be MMEGI indicating the group to which MME_A 40 belongs.
- the first instruction information or the second instruction information may be used as information indicating that old MME information is to be deleted.
- UE10 transmits an attach request message to eNB45, and starts an attachment procedure (S514).
- the UE 10 requests connection to the core network again by transmitting the attach request message.
- the UE 10 may transmit the attach request message including the identification information of the UE.
- the UE 10 may transmit an attach request message including at least the fourth instruction information (Indicator 4). Note that the UE 10 may determine to include the fourth instruction information based on reception of the first instruction information, the third instruction information, or both of the instruction information.
- the fourth instruction information may be information requesting or instructing to switch the core network.
- the fourth instruction information may be a core network type.
- the core network type may be information for identifying the core network (type 2). Specifically, NRI (Network Resource Identifiers) for identifying the core network (type 2) 92 may also be used.
- NRI Network Resource Identifiers
- the fourth instruction information may be identification information indicating that the core network needs to be switched.
- the identification information indicating that the core network needs to be switched may be a core network type that identifies the core network (type 2) 92.
- NRI Network Resource Identifiers
- the fourth instruction information may be MME identification information.
- the MME identification information may be information for identifying the MME included in the core network (type 2) 92.
- the MME identification information may be GUMMEI for identifying MME_B42.
- the MMEGI may identify a group of MMEs included in the core network (type 2) 92.
- the fourth instruction information includes information that requests or instructs switching of the core network, identification information that indicates that switching of the core network is required, and identification of the MME described above. Information combining two or more pieces of information may be used.
- the second instruction information that is a combination of two or more in this way is information indicating that the core network type or the core network type is switched, information indicating that reattachment is necessary, or identification information of the MME. It may be used.
- the UE 10 does not necessarily have to transmit the fourth instruction information included in the attach request message.
- the UE 10 may be transmitted by being included in a control message transmitted by the UE 10 within the attach procedure.
- the eNB 45 receives an attach request message from the UE 10.
- the eNB 45 performs MME selection processing based on the reception of the attach request message (S516).
- the eNB 45 selects the MME_B 42 based on the MME information update process.
- the eNB 45 may select the MME_B 42 based on the fourth instruction information. Thus, when the fourth instruction information is not received, the eNB 45 may select the MME_A 40.
- the eNB 45 may select the MME_B 42 based on the MME information update process and the reception of the fourth instruction information.
- the eNB 45 may select the MME_A 40.
- the eNB 45 may select the MME_A 40 when the MME information update process is not executed.
- the eNB 45 determines whether the MME_A 40 included in the core network (type 1) 90 or the core network (type) by the second instruction information, the fourth instruction information, or the second instruction information and the fourth instruction information. 2) Any of MME_B42 included in 92 can be selected.
- the eNB 45 selects an MME included in the core network (type 2) 92 during execution of the timer, and when the timer is not executed or when there is no need to switch the core network, the information transmitted by the UE 10 is transmitted.
- the MME included in the core network (type 1) may be selected based on the base.
- the selection method in that case may be selected based on information transmitted by the UE 10.
- the UE 10 includes information for identifying the MME, such as GUMMEI, and transmits it in the attach request message.
- the eNB may select the MME.
- the eNB 45 may determine whether or not the MME is available based on the connectivity of the MME.
- the information transmitted by the UE 10 may be information for identifying the MME_A 40 that has managed the location of the UE 10.
- the UE 10 When the MME received from the UE 10 is not available, the UE 10 identifies the MME group identification information such as MMEI, the UE 10 identification information such as P-TMSI, or the TAI (Tracking Area ID) or TAC (Tracking). Position information such as (Area Code) or any two or more pieces of information may be included in the attach request message and transmitted.
- the eNB 45 may receive these pieces of information and select an MME based on these pieces of information.
- the eNB 45 completes the MME selection process.
- the eNB 45 may determine whether to execute the MME selection process based on a timer that starts counting based on the MME information update process. For example, when the timer is counted, the MME selection process is performed, and after the timer has already ended or when the timer is not counted, the MME selection process may not be performed.
- the eNB 45 may select the MME_B 42 when the timer is being executed, and may select the MME_A 40 when the timer is not being executed. If the timer is not executed, the MME may be selected based on the MME identification information included in the attach request. For example, the MME identified by GUMMEI included in the attach request message may be selected, the MME may be selected based on the MMEGI included in the attach request message, or the default MME may be selected. . In this case, the eNB 45 may select the MME_A 40.
- eNB45 may stop a timer, when the attach request message which UE10 transmits is received.
- the eNB 45 may perform MME selection based on the MME identification information included in the attach request when a terminal device that has not performed the MME information update process transmits an attach request message. For example, the MME identified by GUMMEI included in the attach request message may be selected, the MMEGI may be selected based on the MMEGI included in the attach request message, or the MMEGI included in the attach request message may be selected. An MME may be selected, or a default MME may be selected. In this case, the eNB 45 may select the MME_A 40.
- the eNB 45 selects the MME_B 42, the eNB 45 transmits an attach request message to the MME_B 42 (S518).
- the attach procedure after sending the attach request message may be the transmission / reception and processing of the control message similar to the conventional attach procedure. Therefore, detailed description is omitted.
- the eNB 45 may transmit an attach request message to the MME_A 40. Further, the eNB 45 may receive a route reconfiguration request from the MME_A 40. Further, the eNB 45 may select the MME_B 42 based on the route reconfiguration request and transmit an attach request message to the MME_B 42. Note that the attach procedure after sending the attach request message may be the transmission / reception and processing of the control message similar to the conventional attach procedure. Therefore, detailed description is omitted.
- the eNB 45 selects the MME_B 42 by the MME selection process, it is possible to reduce the transmission and reception of the control message and the process such as being able to execute the attach procedure without receiving the reroute resetting request.
- the MME_B 42 receives the attach request message from the eNB 45 and selects the SGW and the PGW.
- the MME_B 42 may select the SGW_B 37 and the PGW_B 32 for the core network (type 2) 92 and establish a PDN connection between the UE 10 and the PGW_B 32.
- the UE 10 establishes a PDN connection with the PGW_B 32 by the attach procedure. Furthermore, the PDN connection between the UE 10 and the PGW_B 32 is established via the SGW_B 37. Furthermore, UE10 can perform transmission / reception of a user data with the communication apparatus contained in PDN_B102 using the established PDN connection.
- the core network (type 1) 90 and the core network (type 2) 92 have been described as being connected to the PDN_A 100 and the PDN_B 102, respectively.
- the PDN_A 100 and the PDN_B 102 are connected to the same network (PDN 100).
- PGW_A30 and PGW_B32 may be the same device (PGW_A30).
- the UE 10 changes the MME that performs mobility control from the MME_A 40 to the MME_B 42. Furthermore, a new PDN connection may be established without changing the PGW serving as the end point of the PDN connection. Further, in the attach procedure described in this procedure, the MME_B 42 may select the PGW_A 30 that is the end point of the PDN connection that the UE 10 has previously established. Thereby, UE10 may establish a PDN connection between PGW_A30.
- the UE 10 is connected to the core network (type 1) 90. More specifically, the UE 10 is connected to the eNB 45. Furthermore, UE10 is connected to MME_A40 via eNB45. Furthermore, the UE 10 has established a PDN connection with the PGW_A 30.
- the PDN connection is a communication path for delivering user data.
- the core network (type 1) 90 may be configured to include PGW_A30
- the core network (type 2) 92 may be configured to include PGW_B32.
- SGWs may be arranged in the core network (type 1) 90 and the core network (type 2) 92, respectively.
- the SGW_A 35 may be included in the core network (type 1) 90
- the SGW_B 37 may be included in the core network (type 2) 92.
- the UE 10 has established a PDN connection with the PGW_A 30 in the initial state. Furthermore, the PDN connection between the UE 10 and the PGW_A 30 is established via the SGW_A 35.
- GUTI Globally Unique Unique Temporary Identity assigned globally uniquely to the UE 10
- subscriber information such as IMGI (International Mobile Subscriber Identity) may be used.
- identification information such as P-TMSI (Packet (Temporary Mobile Subscriber Identity) may be used.
- P-TMSI Packet (Temporary Mobile Subscriber Identity) may be used.
- the MME identification information may be a GUMMEI (Globally Unique MME Identifier) corresponding to each MME.
- GUMMEI Globally Unique MME Identifier
- the MME identification information may be an MMEGI (MME Group Identifier) that identifies an MME group.
- the eNB 45 holds MMEGI and GUMMEI belonging to the MME group identified by the MMEGI in advance, and when receiving the MMEGI, selects the GUMMEI belonging to the MMEGI based on the received MMEGI. Can do.
- the eNB 45 may store the MMEGI grouped with the MME belonging to the core network (type 2) and the MMEGI group MMEGI such as MME_B42 in the MME information in advance.
- the MME_A 40 detects a trigger for starting a procedure for changing the core network to which the UE 10 is connected (S702).
- the trigger detection process may be the same process as the trigger detection process (S502) described in the first procedure example. Hereinafter, the trigger detection process will be described.
- the MME_A 40 may detect the trigger based on the update of the subscriber information. More specifically, based on the change of the subscriber information corresponding to the UE 10 stored in the HSS 50, the HSS 50 transmits a control message including identification information indicating the change to the MME_A 40. The MME_A 40 may detect that it is necessary to change the core network to which the UE 10 is connected based on reception of a control message transmitted by the HSS 50 or identification information included in the control message.
- the identification information included in the control message may be core network information indicating the core network type 2 or information such as a flag indicating that a change of the core network type is requested.
- the control message may be a control message for requesting switching of the core network. Further, the control message may include identification information of the UE 10.
- the eNB 45 may receive the MMEGI that groups the MMEs belonging to the core network (type 2) and perform the MME selection process. Note that the eNB 45 may select the MME_B 42 based on the received MMEGI.
- the MME_A 40 may detect a trigger based on the core network (type 2) 92 being configured. More specifically, it may be started when a control device included in the core network (type 2) 92 such as MME_B42 or PGW_B32 is installed. The core network operator may install such a control device and manually operate the MME_A 40 based on the installation. The MME_A 40 may detect a trigger based on such an operator's manual operation.
- the MME_A 40 may transmit a UE context release message to the eNB 45 based on the trigger detection (S704).
- the MME_A 40 may request to release the radio resource.
- the MME_A 40 may transmit a UE context release message including at least the second instruction information (Indicator 2).
- the second instruction information may be information requesting or instructing to switch the core network.
- the second instruction information may be a core network type.
- the core network type may be information for identifying the core network (type 2). Specifically, NRI (Network Resource Identifiers) for identifying the core network (type 2) 92 may also be used.
- NRI Network Resource Identifiers
- the second instruction information may be information indicating that the core network type is switched. More specifically, the information indicating that the core network type is switched may be a reason display information element (Cause Value) indicating that the core network needs to be switched.
- the information indicating that the core network type is switched may be a reason display information element (Cause Value) indicating that the core network needs to be switched.
- the second instruction information may be information indicating that the UE 10 needs to be reattached. More specifically, the information indicating that the UE 10 needs to be reattached may be a reason display information element (Cause Value) indicating Attach Required.
- a reason display information element (Cause Value) indicating Attach Required.
- the second instruction information may be MME identification information.
- the MME identification information may be information for identifying the MME included in the core network (type 2) 92.
- the MME identification information may be GUMMEI for identifying MME_B42.
- the MMEGI may identify a group of MMEs included in the core network (type 2) 92.
- the second instruction information needs to be reattached as described above, the information that requests or instructs to switch the core network, the information that indicates the core network type, and the core network type that is to be switched.
- the information which shows 2 and the information which combined 2 or more identification information of MME may be sufficient.
- the second instruction information that is a combination of two or more in this way is information indicating that the core network type or the core network type is switched, information indicating that reattachment is necessary, or identification information of the MME. It may be used.
- the MME_A 40 may transmit a transmission UE context release message including at least the identification information of the UE 10 and a timer value.
- the timer value may be a timer value used by the eNB 45 for selecting an MME.
- the eNB 45 receives a UE context release message from the MME_A 40.
- the eNB 45 may execute the MME information update process based on the information included in the UE context release message (S706). More specifically, the MME information update process may be executed based on the second instruction information.
- the MME information update process updates the MME information so that the eNB 45 selects the MME included in the core network (type 2) 92 in the MME selection performed in accordance with the reception of the tracking area update request message transmitted by the UE 10. It may be a process.
- the eNB 45 may store the identification information of the UE 10 and the second instruction information in association with each other in the MME information update process.
- the eNB 45 may continue to hold the UE context information without deleting it by acquiring the second instruction information. On the other hand, the eNB 45 may delete the UE context information when the second instruction information is not acquired.
- the eNB 45 may start a timer count based on the second instruction information. The eNB 45 may continue to hold the updated MME information or UE context while the timer is being executed. Furthermore, when the timer is consumed or when the timer is stopped due to some factor, the eNB 45 may delete the updated MME information or UE context.
- timer value a value held in advance by the eNB 45 may be used, or a timer value included in the UE context release message may be used.
- the eNB 45 may continue to hold the MME information held before the MME information update process.
- MMEI corresponding to the MME_A 40 included in the core network (type 1) 90, MMEGI indicating the group of MMEs to which the MME_A 40 belongs may be kept.
- the NB 45 may transmit the RRC connection release message to the UE 10 based on the reception of the UE context release message or the completion of the MME information update process (S708).
- the eNB 45 may release the radio resource allocated to the UE 10 based on the transmission of the UE context release message.
- the eNB 45 may transmit the UE context release message including information that requires a response, such as setting the Acknowledge mode to 1.
- the UE 10 transmits a response to the UE context release message to the eNB 45 as a response to the UE context release message.
- the eNB 45 may release the radio resource allocated to the UE 10 based on the reception of the response message.
- the eNB 45 may continue to hold the UE 10 context including the identification information of the UE 10 when the timer is being executed when the UE context release message is transmitted or the response message is received. Alternatively, the eNB 45 deletes the UE context, but may store the identification information of the UE 10 and the second instruction information in association with each other during execution of the timer.
- the RRC connection release message may be transmitted including at least the third instruction information.
- the third instruction information may be information requesting or instructing to switch the core network.
- the third instruction information may be identification information indicating that the UE 10 is requested to reattach.
- the identification information for requesting reattachment may be a reason display information element (Cause Value) that is Attach Required.
- the third instruction information may be identification information indicating that the UE 10 needs a tracking area update procedure.
- the identification information indicating that the tracking area update procedure is necessary may be a reason display information element (Cause Value) of TAU Require.
- the third instruction information may be identification information indicating that the core network needs to be switched.
- the identification information indicating that the core network needs to be switched may be a core network type that identifies the core network (type 2) 92.
- NRI Network Resource Identifiers
- the third instruction information may be MME identification information.
- the MME identification information may be information for identifying the MME included in the core network (type 2) 92.
- the MME identification information may be GUMMEI for identifying MME_B42.
- the MMEGI may identify a group of MMEs included in the core network (type 2) 92.
- the third instruction information requires information for requesting or instructing switching of the core network, identification information indicating requesting reattachment to the UE 10, and a tracking area update procedure for the UE 10 as described above.
- Information obtained by combining two or more identification information indicating that there is identification information indicating that switching of the core network is necessary, and identification information of the MME may be used.
- the third instruction information combined two or more in this way is identification information indicating that the UE 10 is requested to reattach, or identification information indicating that the UE 10 needs a tracking area update procedure, or a core It may be used as identification information indicating that network switching is necessary, or MME identification information.
- the eNB 45 transmits a context release completion message to the MME_A 40 as a response to the UE context release message (S710).
- the context release completion message is a response message to the UE context release message.
- the context release completion message indicates that these processes are completed. It becomes a message to notify.
- the eNB 45 when the eNB 45 performs the MME information update process based on the acquisition of the second instruction information and keeps the MME information and the like based on the MME information update process, the eNB 45 or the core network (type 2) 92
- the UE context release completion message may be transmitted including information indicating that the MME information is held.
- the MME_A 40 may receive the UE context release completion message and delete the UE context held by the MME_A 40.
- the UE 10 may receive the RRC connection release and start the tracking area update procedure. Note that the UE 10 may start the tracking area update procedure based on the third instruction information. Alternatively, the UE 10 may start the tracking area update procedure when the tracking area update timer for counting the transmission interval of the tracking area update request is consumed.
- the UE 10 may delete the held MME information based on the reception of the first instruction information.
- the information on the MME to be deleted may be the GUMEI of MME_A40.
- the MME information to be deleted may be MMEGI indicating the group to which MME_A 40 belongs.
- the first instruction information or the second instruction information may be used as information indicating that old MME information is to be deleted.
- UE10 transmits a tracking area update request message to eNB45, and starts a tracking area update procedure (S712).
- the UE 10 requests confirmation or update of the tracking area where the UE 10 is located by transmitting the tracking area update message.
- the UE 10 may transmit a tracking area update message including at least the identification information of the UE.
- the UE 10 may transmit an attach request message including at least the fourth instruction information (Indicator 4). Note that the UE 10 may determine to include the fourth instruction information based on the third instruction information.
- the fourth instruction information may be information requesting or instructing to switch the core network.
- the fourth instruction information may be a core network type.
- the core network type may be information for identifying the core network (type 2). Specifically, NRI (Network Resource Identifiers) for identifying the core network (type 2) 92 may also be used.
- NRI Network Resource Identifiers
- the fourth instruction information may be identification information indicating that the core network needs to be switched.
- the identification information indicating that the core network needs to be switched may be a core network type that identifies the core network (type 2) 92.
- NRI Network Resource Identifiers
- the fourth instruction information may be MME identification information.
- the MME identification information may be information for identifying the MME included in the core network (type 2) 92.
- the MME identification information may be GUMMEI for identifying MME_B42.
- the MMEGI may identify a group of MMEs included in the core network (type 2) 92.
- the fourth instruction information includes information that requests or instructs switching of the core network, identification information that indicates that switching of the core network is required, and identification of the MME described above. Information combining two or more pieces of information may be used.
- the second instruction information in which two or more are combined in this way may be used as core network type, information indicating switching of the core network type, or MME identification information.
- the eNB 45 receives the tracking update request message from the UE 10.
- the eNB 45 may execute the MME selection process based on the reception of the tracking area request message. (S714).
- the eNB 45 selects the MME_B 42 based on the MME information update process.
- the eNB 45 may select the MME_B 42 based on the fourth instruction information. Thus, when the fourth instruction information is not received, the eNB 45 may select the MME_A 40.
- the eNB 45 may select the MME_B 42 based on the MME information update process and the reception of the fourth instruction information.
- the eNB 45 may select the MME_A 40.
- the eNB 45 may select the MME_A 40 when the MME information update process is not executed.
- the eNB 45 determines whether the MME_A 40 included in the core network (type 1) 90 or the core network (type) by the second instruction information, the fourth instruction information, or the second instruction information and the fourth instruction information. 2) Any of MME_B42 included in 92 can be selected.
- the eNB 45 selects an MME included in the core network (type 2) 92 during execution of the timer, and when the timer is not executed or when there is no need to switch the core network, the information transmitted by the UE 10 is transmitted.
- the MME included in the core network (type 1) may be selected based on the base.
- the selection method in that case may be selected based on information transmitted by the UE 10.
- the UE 10 transmits information for identifying the MME such as GUMMEI in the tracking area update request message.
- the eNB may select the MME.
- the eNB 45 may determine whether or not the MME is available based on the connectivity of the MME.
- the information transmitted by the UE 10 may be information for identifying the MME_A 40 that has managed the location of the UE 10.
- the UE 10 When the MME received from the UE 10 is not available, the UE 10 identifies the MME group identification information such as MMEI, the UE 10 identification information such as P-TMSI, or the TAI (Tracking Area ID) or TAC (Tracking). Position information such as (Area Code) or any two or more pieces of information may be included in the tracking area update request message and transmitted. The eNB 45 may receive these pieces of information and select an MME based on these pieces of information.
- MME group identification information such as MMEI
- P-TMSI the UE 10 identification information
- TAI Track Area ID
- TAC Tracking Area ID
- Position information such as (Area Code) or any two or more pieces of information may be included in the tracking area update request message and transmitted.
- the eNB 45 may receive these pieces of information and select an MME based on these pieces of information.
- the eNB 45 completes the MME selection process.
- the eNB 45 may determine whether to execute the MME selection process based on a timer that starts counting based on the MME information update process. For example, when the timer is counted, the MME selection process is performed, and after the timer has already ended or when the timer is not counted, the MME selection process may not be performed.
- the eNB 45 may select the MME_B 42 when the timer is being executed, and may select the MME_A 40 when the timer is not being executed. If the timer is not executed, the MME may be selected based on the MME identification information included in the tracking area update request message. For example, the MME identified by the tracking area update request message may be selected, the MME may be selected based on the MMEGI included in the tracking area update request message, or the default MME may be selected. . In this case, the eNB 45 may select the MME_A 40.
- eNB45 may stop a timer, when the tracking area update request message which UE10 transmits is received.
- the eNB 45 may perform MME selection based on the MME identification information included in the tracking area update request message. Good. For example, the MME identified by GUMMEI included in the tracking area update request message may be selected, or the MME may be selected based on the MMEGI included in the tracking area update request message, or the default MME may be selected. May be. In this case, the eNB 45 may select the MME_A 40.
- eNB45 when MME_B42 is selected, eNB45 transmits a tracking area request message to MME_B42 (S716).
- the tracking area update procedure after sending the tracking area request message may be the same as the transmission / reception and processing of the control message similar to the conventional tracking update procedure. Therefore, detailed description is omitted.
- the eNB 45 may transmit a tracking area update request message to the MME_A 40. Further, the eNB 45 may receive a route reconfiguration request from the MME_A 40. Further, the eNB 45 may select the MME_B 42 based on the route reconfiguration request and transmit a tracking update request message to the MME_B 42. Note that the attachment procedure after the transmission of the tracking update request message may be the transmission / reception and processing of the control message similar to the conventional tracking update request message. Therefore, detailed description is omitted.
- the control message transmission / reception and the process can be reduced such that the tracking update request message can be transmitted without receiving the reroute reset request.
- UE 10 completes the tracking area update procedure and can communicate using the PDN connection.
- the core network (type 1) 90 and the core network (type 2) 92 have been described as being connected to the PDN_A 100 and the PDN_B 102, respectively.
- the PDN_A 100 and the PDN_B 102 are connected to the same network (PDN 100).
- PGW_A30 and PGW_B32 may be the same device (PGW_A30).
- the UE 10 changes the MME that performs mobility control from the MME_A 40 to the MME_B 42, but the PDN connection does not need to be re-established.
- UE10 can continue communication using the PDN connection established between PGW_A30.
- the UE 10 is connected to the core network (type 1) 90. More specifically, the UE 10 is connected to the eNB 45. Furthermore, UE10 is connected to MME_A40 via eNB45. Furthermore, the UE 10 has established a PDN connection with the PGW_A 30.
- the PDN connection is a communication path for delivering user data.
- the core network (type 1) 90 may be configured to include PGW_A30
- the core network (type 2) 92 may be configured to include PGW_B32.
- SGWs may be arranged in the core network (type 1) 90 and the core network (type 2) 92, respectively.
- the SGW_A 35 may be included in the core network (type 1) 90
- the SGW_B 37 may be included in the core network (type 2) 92.
- the UE 10 in the initial state, has established a PDN connection with the PGW_A 30. Furthermore, the PDN connection between the UE 10 and the PGW_A 30 is established via the SGW_A 35.
- the identification information of the UE 10 may use GUTI (Globally Unique Unique Temporary Identity) assigned globally uniquely to the UE 10.
- subscriber information such as IMGI (International Mobile Subscriber Identity) may be used.
- identification information such as P-TMSI (Packet (Temporary Mobile Subscriber Identity) may be used.
- P-TMSI Packet (Temporary Mobile Subscriber Identity) may be used.
- the MME identification information may be a GUMMEI (Globally Unique MME Identifier) corresponding to each MME.
- GUMMEI Globally Unique MME Identifier
- the MME identification information may be an MMEGI (MME Group Identifier) that identifies an MME group.
- the eNB 45 holds MMEGI and GUMMEI belonging to the MME group identified by the MMEGI in advance, and when receiving the MMEGI, selects the GUMMEI belonging to the MMEGI based on the received MMEGI. Can do.
- the eNB 45 may store the MMEGI grouped with the MME belonging to the core network (type 2) and the MMEGI group MMEGI such as MME_B42 in the MME information in advance.
- the MME_A 40 detects a trigger for starting a procedure for changing the core network to which the UE 10 is connected (S802).
- the trigger detection process may be the same process as the trigger detection process (S502) described in the first procedure example. Hereinafter, the trigger detection process will be described.
- the MME_A 40 may detect the trigger based on the update of the subscriber information. More specifically, based on the change of the subscriber information corresponding to the UE 10 stored in the HSS 50, the HSS 50 transmits a control message including identification information indicating the change to the MME_A 40. The MME_A 40 may detect that it is necessary to change the core network to which the UE 10 is connected based on reception of a control message transmitted by the HSS 50 or identification information included in the control message.
- the identification information included in the control message may be core network information indicating the core network type 2 or information such as a flag indicating that a change of the core network type is requested.
- the control message may be a control message for requesting switching of the core network. Further, the control message may include identification information of the UE 10.
- the eNB 45 may receive the MMEGI that groups the MMEs belonging to the core network (type 2) and perform the MME selection process. Note that the eNB 45 may select the MME_B 42 based on the received MMEGI.
- the MME_A 40 may detect a trigger based on the core network (type 2) 92 being configured. More specifically, it may be started when a control device included in the core network (type 2) 92 such as the MMEB 42 or the PGW_B 32 is installed. The core network operator may install such a control device and manually operate the MME_A 40 based on the installation. The MME_A 40 may detect a trigger based on such an operator's manual operation.
- the MME_A 40 transmits a paging message to the UE 10 based on the trigger detection (S804).
- the MME_A 40 may transmit the paging message including at least the first instruction information (Indicator 1).
- the first instruction information may be information requesting or instructing to switch the core network.
- the first instruction information may be a core network type.
- the core network type may be information for identifying the core network (type 2). Specifically, NRI (Network Resource Identifiers) for identifying the core network (type 2) 92 may be used.
- NRI Network Resource Identifiers
- the first instruction information may be information indicating that the core network type is switched. More specifically, the information indicating that the core network type is switched may be a reason display information element (Cause Value) indicating that the core network needs to be switched.
- the information indicating that the core network type is switched may be a reason display information element (Cause Value) indicating that the core network needs to be switched.
- the first instruction information may be information indicating that the UE 10 needs to be reattached. More specifically, the information indicating that the UE 10 needs to be reattached may be a reason display information element (Cause Value) indicating Attach Required.
- a reason display information element (Cause Value) indicating Attach Required.
- the first instruction information may be MME identification information.
- the MME identification information may be information for identifying the MME included in the core network (type 2) 92.
- the MME identification information may be GUMMEI for identifying MME_B42.
- the MMEGI may identify a group of MMEs included in the core network (type 2) 92.
- the first instruction information needs to be reattached as described above, the information for requesting or instructing to switch the core network, the information indicating that the core network type and the core network type are switched, and the like.
- the information which shows 2 and the information which combined 2 or more identification information of MME may be sufficient.
- the first instruction information that is combined two or more in this way is information indicating that the core network type or the core network type is switched, information indicating that reattachment is necessary, or identification information of the MME. It may be used.
- the MME_A 40 may transmit a route reconfiguration request message to the eNB 45 in parallel with the transmission of the paging message or after the transmission of the paging message (S806).
- MME_A may request an update of MME information by transmitting a route reset request message.
- the MME_A 40 may transmit a route reconfiguration request message including at least the second instruction information (Indicator 2).
- the second instruction information may be information requesting or instructing to switch the core network.
- the second instruction information may be a core network type.
- the core network type may be information for identifying the core network (type 2). Specifically, NRI (Network Resource Identifiers) for identifying the core network (type 2) 92 may also be used.
- NRI Network Resource Identifiers
- the second instruction information may be information indicating that the core network type is switched. More specifically, the information indicating that the core network type is switched may be a reason display information element (Cause Value) indicating that the core network needs to be switched.
- the information indicating that the core network type is switched may be a reason display information element (Cause Value) indicating that the core network needs to be switched.
- the second instruction information may be information indicating that the UE 10 needs to be reattached. More specifically, the information indicating that the UE 10 needs to be reattached may be a reason display information element (Cause Value) indicating Attach Required.
- a reason display information element (Cause Value) indicating Attach Required.
- the second instruction information may be MME identification information.
- the MME identification information may be information for identifying the MME included in the core network (type 2) 92.
- the MME identification information may be GUMMEI for identifying MME_B42.
- the MMEGI may identify a group of MMEs included in the core network (type 2) 92.
- the second instruction information needs to be reattached as described above, the information that requests or instructs to switch the core network, the information that indicates the core network type, and the core network type that is to be switched.
- the information which shows 2 and the information which combined 2 or more identification information of MME may be sufficient.
- the second instruction information that is a combination of two or more in this way is information indicating that the core network type or the core network type is switched, information indicating that reattachment is necessary, or identification information of the MME. It may be used.
- the MME_A 40 may transmit a transmission UE context release message including at least the identification information of the UE 10 and a timer value.
- the timer value may be a timer value used by the eNB 45 for selecting an MME.
- the route reconfiguration request message may be a control message for requesting or instructing an update of MME information, and any control message may be used. Therefore, the MME_A 40 may request or instruct the eNB 45 to update the information on the MME using another control message. At that time, the description of the route reconfiguration request message in the present embodiment can be applied to a control message for requesting or instructing to update the information of the MME.
- the eNB 45 receives a route reconfiguration request message from the MME_A 40.
- the eNB 45 may execute the MME information update process based on the information included in the route reconfiguration request message (S808). More specifically, the MME information update process may be executed based on the second instruction information.
- the MME information update process is a process of updating the MME information so that the eNB 45 selects an MME included in the core network (type 2) 92 in the MME selection performed in accordance with the reception of the attach request message transmitted by the UE 10. It may be.
- the eNB 45 may store the identification information of the UE 10 and the second instruction information in association with each other in the MME information update process.
- the eNB 45 may continue to hold the UE context information without deleting it by acquiring the second instruction information. On the other hand, the eNB 45 may delete the UE context information when the second instruction information is not acquired.
- the eNB 45 may start a timer count based on the second instruction information. The eNB 45 may continue to hold the updated MME information or UE context while the timer is being executed. Furthermore, when the timer is consumed or when the timer is stopped due to some factor, the eNB 45 may delete the updated MME information or UE context.
- timer value a value held in advance by the eNB 45 may be used, or a timer value included in the UE context release message may be used.
- the eNB 45 may continue to hold the MME information held before the MME information update process.
- MMEI corresponding to the MME_A 40 included in the core network (type 1) 90, MMEGI indicating the group of MMEs to which the MME_A 40 belongs may be kept.
- the eNB 45 may transmit a route reconfiguration response message to the MME_A 40 as a response to the route reconfiguration request message based on the completion of the MME information update process (S810).
- the eNB 45 may notify that the update process of the MME information has been completed by transmitting a route reconfiguration response message.
- the route reconfiguration response message may be transmitted including information indicating that the MME information is held.
- the route resetting response message may be a response to a control message for requesting or instructing update of MME information, and an arbitrary control message may be used. Therefore, MME_A40 may transmit a response to MME_A40 using another control message. At that time, the description of the route reconfiguration response message in the present embodiment can be applied to a control message for response.
- the MME_A 40 may receive the route reconfiguration response message and perform the detach process (Implicitly detach) without the MME_40 taking the initiative to start the control procedure (S812).
- the detach process the UE context held by the MME_A 40 may be deleted.
- the UE 10 may receive a paging message and start a service request procedure. Note that the UE 10 may start a service request procedure based on the first instruction information.
- the UE 10 may transmit a service request message to the MME_A 40 (S814).
- UE10 may request
- the MME_A 40 may receive the service request message and transmit a service reject message as a response to the service request message (S816).
- the service reject message may be transmitted based on the fact that the detach process has been completed in the MME_A 40.
- the MME_A 40 may transmit the service reject message including at least information indicating that the detach process has been completed. More specifically, the information indicating that the detachment consideration has been completed may be a reason display information element (Cause Value) of “Implicitly Detach”.
- the first instruction information may be transmitted to the UE 10 in a service reject message instead of a paging message.
- the attach procedure may be started based on information indicating that the service rejection has been received or the detach process has been completed. Alternatively, the attach procedure may be started based on the fact that the first instruction information is acquired with the reception of the service reject message.
- the UE 10 may delete the held MME information based on the reception of the first instruction information.
- the information on the MME to be deleted may be the GUMEI of MME_A40.
- the MME information to be deleted may be MMEGI indicating the group to which MME_A 40 belongs.
- the first instruction information may be used as information indicating that old MME information is to be deleted.
- the deletion of the retained MME information may be executed after receiving the service reject message.
- the attach procedure will be described.
- the UE 10 transmits an attach request message to the eNB 45 and starts an attach procedure (S818).
- the UE 10 requests connection to the core network again by transmitting the attach request message.
- the UE 10 may transmit the attach request message including the identification information of the UE.
- the UE 10 may transmit an attach request message including at least the fourth instruction information (Indicator 4). Note that the UE 10 may determine to include the fourth instruction information based on reception of the first instruction information, the third instruction information, or both of the instruction information.
- the fourth instruction information may be information requesting or instructing to switch the core network.
- the fourth instruction information may be a core network type.
- the core network type may be information for identifying the core network (type 2). Specifically, NRI (Network Resource Identifiers) for identifying the core network (type 2) 92 may also be used.
- NRI Network Resource Identifiers
- the fourth instruction information may be identification information indicating that the core network needs to be switched.
- the identification information indicating that the core network needs to be switched may be a core network type that identifies the core network (type 2) 92.
- NRI Network Resource Identifiers
- the fourth instruction information may be MME identification information.
- the MME identification information may be information for identifying the MME included in the core network (type 2) 92.
- the MME identification information may be GUMMEI for identifying MME_B42.
- the MMEGI may identify a group of MMEs included in the core network (type 2) 92.
- the fourth instruction information includes information that requests or instructs switching of the core network, identification information that indicates that switching of the core network is required, and identification of the MME described above. Information combining two or more pieces of information may be used.
- the second instruction information that is a combination of two or more in this way is information indicating that the core network type or the core network type is switched, information indicating that reattachment is necessary, or identification information of the MME. It may be used.
- the UE 10 does not necessarily have to transmit the fourth instruction information included in the attach request message.
- the UE 10 may be transmitted by being included in a control message transmitted by the UE 10 within the attach procedure.
- the eNB 45 receives an attach request message from the UE 10.
- the eNB 45 performs MME selection processing based on the reception of the attach request message (S820).
- the eNB 45 selects the MME_B 42 based on the MME information update process.
- the eNB 45 may select the MME_B 42 based on the fourth instruction information. Thus, when the fourth instruction information is not received, the eNB 45 may select the MME_A 40.
- the eNB 45 may select the MME_B 42 based on the MME information update process and the reception of the fourth instruction information.
- the eNB 45 may select the MME_A 40.
- the eNB 45 may select the MME_A 40 when the MME information update process is not executed.
- the eNB 45 determines whether the MME_A 40 included in the core network (type 1) 90 or the core network (type) by the second instruction information, the fourth instruction information, or the second instruction information and the fourth instruction information. 2) Any of MME_B42 included in 92 can be selected.
- the eNB 45 selects an MME included in the core network (type 2) 92 during execution of the timer, and when the timer is not executed or when there is no need to switch the core network, the information transmitted by the UE 10 is transmitted.
- the MME included in the core network (type 1) may be selected based on the base.
- the selection method in that case may be selected based on information transmitted by the UE 10.
- the UE 10 includes information for identifying the MME, such as GUMMEI, and transmits it in the attach request message.
- the eNB may select the MME.
- the eNB 45 may determine whether or not the MME is available based on the connectivity of the MME.
- the information transmitted by the UE 10 may be information for identifying the MME_A 40 that has managed the location of the UE 10.
- the UE 10 When the MME received from the UE 10 is not available, the UE 10 identifies the MME group identification information such as MMEI, the UE 10 identification information such as P-TMSI, or the TAI (Tracking Area ID) or TAC (Tracking). Position information such as (Area Code) or any two or more pieces of information may be included in the attach request message and transmitted.
- the eNB 45 may receive these pieces of information and select an MME based on these pieces of information.
- the eNB 45 completes the MME selection process.
- the eNB 45 may determine whether to execute the MME selection process based on a timer that starts counting based on the MME information update process. For example, when the timer is counted, the MME selection process is performed, and after the timer has already ended or when the timer is not counted, the MME selection process may not be performed.
- the eNB 45 may select the MME_B 42 when the timer is being executed, and may select the MME_A 40 when the timer is not being executed. If the timer is not executed, the MME may be selected based on the MME identification information included in the attach request. For example, the MME identified by GUMMEI included in the attach request message may be selected, the MME may be selected based on the MMEGI included in the attach request message, or the default MME may be selected. . In this case, the eNB 45 may select the MME_A 40.
- eNB45 may stop a timer, when the attach request message which UE10 transmits is received.
- the eNB 45 may perform MME selection based on the MME identification information included in the attach request when a terminal device that has not performed the MME information update process transmits an attach request message. For example, the MME identified by GUMMEI included in the attach request message may be selected, the MMEGI may be selected based on the MMEGI included in the attach request message, or the MMEGI included in the attach request message may be selected. An MME may be selected, or a default MME may be selected. In this case, the eNB 45 may select the MME_A 40.
- the eNB 45 When the eNB 45 selects the MME_B 42, the eNB 45 transmits an attach request message to the MME_B 42 (S822). Note that the attach procedure after sending the attach request message may be the transmission / reception and processing of the control message similar to the conventional attach procedure. Therefore, detailed description is omitted.
- the eNB 45 may transmit an attach request message to the MME_A 40. Further, the eNB 45 may receive a route reconfiguration request from the MME_A 40. Further, the eNB 45 may select the MME_B 42 based on the route reconfiguration request and transmit an attach request message to the MME_B 42. Note that the attach procedure after sending the attach request message may be the transmission / reception and processing of the control message similar to the conventional attach procedure. Therefore, detailed description is omitted.
- the eNB 45 selects the MME_B 42 by the MME selection process, it is possible to reduce the transmission and reception of the control message and the process such as being able to execute the attach procedure without receiving the reroute resetting request.
- the MME_B 42 receives the attach request message from the eNB 45 and selects the SGW and the PGW.
- the MME_B 42 may select the SGW_B 37 and the PGW_B 32 for the core network (type 2) 92 and establish a PDN connection between the UE 10 and the PGW_B 32.
- the UE 10 establishes a PDN connection with the PGW_B 32 by the attach procedure. Furthermore, the PDN connection between the UE 10 and the PGW_B 32 is established via the SGW_B 37. Furthermore, UE10 can perform transmission / reception of a user data with the communication apparatus contained in PDN_B102 using the established PDN connection.
- the core network (type 1) 90 and the core network (type 2) 92 have been described as being connected to the PDN_A 100 and the PDN_B 102, respectively.
- the PDN_A 100 and the PDN_B 102 are connected to the same network (PDN 100).
- PGW_A30 and PGW_B32 may be the same device (PGW_A30).
- the UE 10 changes the MME that performs mobility control from the MME_A 40 to the MMEB. Furthermore, a new PDN connection may be established without changing the PGW serving as the end point of the PDN connection. Further, in the attach procedure described in this procedure, the MME_B 42 may select the PGW_A 30 that is the end point of the PDN connection that the UE 10 has previously established. Thereby, UE10 may establish a PDN connection between PGW_A30.
- the UE 10 is connected to the core network (type 1) 90. More specifically, the UE 10 is connected to the eNB 45. Furthermore, UE10 is connected to MME_A40 via eNB45. Furthermore, the UE 10 has established a PDN connection with the PGW_A 30.
- the PDN connection is a communication path for delivering user data.
- the core network (type 1) 90 may be configured to include PGW_A30
- the core network (type 2) 92 may be configured to include PGW_B32.
- SGWs may be arranged in the core network (type 1) 90 and the core network (type 2) 92, respectively.
- the SGW_A 35 may be included in the core network (type 1) 90
- the SGW_B 37 may be included in the core network (type 2) 92.
- the UE 10 in the initial state, has established a PDN connection with the PGW_A 30. Furthermore, the PDN connection between the UE 10 and the PGW_A 30 is established via the SGW_A 35.
- GUTI Globally Unique Unique Temporary Identity assigned to the UE 10
- subscriber information such as IMGI (International Mobile Subscriber Identity) may be used.
- identification information such as P-TMSI (Packet (Temporary Mobile Subscriber Identity) may be used.
- P-TMSI Packet (Temporary Mobile Subscriber Identity) may be used.
- the MME identification information may be a GUMMEI (Globally Unique MME Identifier) corresponding to each MME.
- GUMMEI Globally Unique MME Identifier
- the MME identification information may be an MMEGI (MME Group Identifier) that identifies an MME group.
- the eNB 45 holds MMEGI and GUMMEI belonging to the MME group identified by the MMEGI in advance, and when receiving the MMEGI, selects the GUMMEI belonging to the MMEGI based on the received MMEGI. Can do.
- the eNB 45 may store the MMEGI grouped with the MME belonging to the core network (type 2) and the MMEGI group MMEGI such as MME_B42 in the MME information in advance.
- the MME_A 40 detects a trigger for starting a procedure for changing the core network to which the UE 10 is connected (S902).
- the trigger detection process may be the same process as the trigger detection process (S502) described in the first procedure example. Hereinafter, the trigger detection process will be described.
- the MME_A 40 may detect the trigger based on the update of the subscriber information. More specifically, based on the change of the subscriber information corresponding to the UE 10 stored in the HSS 50, the HSS 50 transmits a control message including identification information indicating the change to the MME_A 40. The MME_A 40 may detect that it is necessary to change the core network to which the UE 10 is connected based on reception of a control message transmitted by the HSS 50 or identification information included in the control message.
- the identification information may be core network information indicating the core network type 2 or information such as a flag indicating that a change of the core network type is requested.
- the control message may be a control message for requesting switching of the core network. Further, the control message may include identification information of the UE 10.
- the eNB 45 may receive the MMEGI that groups the MMEs belonging to the core network (type 2) and perform the MME selection process. Note that the eNB 45 may select the MME_B 42 based on the received MMEGI.
- the MME_A 40 may detect a trigger based on the core network (type 2) 92 being configured. More specifically, it may be started when a control device included in the core network (type 2) 92 such as the MMEB 42 or the PGW_B 32 is installed. The core network operator may install such a control device and manually operate the MME_A 40 based on the installation. The MME_A 40 may detect a trigger based on such an operator's manual operation.
- the MME_A 40 may transmit a route reconfiguration request message to the eNB 45 based on the trigger detection.
- the MME_A may request an update of MME information by transmitting a route reset request message (S906).
- MME_A may request an update of MME information by transmitting a route reset request message.
- the MME_A 40 may transmit a route reconfiguration request message including at least the second instruction information (Indicator 2).
- the second instruction information may be information requesting or instructing to switch the core network.
- the second instruction information may be a core network type.
- the core network type may be information for identifying the core network (type 2). Specifically, NRI (Network Resource Identifiers) for identifying the core network (type 2) 92 may also be used.
- NRI Network Resource Identifiers
- the second instruction information may be information indicating that the core network type is switched. More specifically, the information indicating that the core network type is switched may be a reason display information element (Cause Value) indicating that the core network needs to be switched.
- the information indicating that the core network type is switched may be a reason display information element (Cause Value) indicating that the core network needs to be switched.
- the second instruction information may be information indicating that the UE 10 needs to be reattached. More specifically, the information indicating that the UE 10 needs to be reattached may be a reason display information element (Cause Value) indicating Attach Required.
- a reason display information element (Cause Value) indicating Attach Required.
- the second instruction information may be MME identification information.
- the MME identification information may be information for identifying the MME included in the core network (type 2) 92.
- the MME identification information may be GUMMEI for identifying MME_B42.
- the MMEGI may identify a group of MMEs included in the core network (type 2) 92.
- the second instruction information needs to be reattached as described above, the information that requests or instructs to switch the core network, the information that indicates the core network type, and the core network type that is to be switched. And information combining two or more MME identification information.
- the second instruction information combined two or more in this way is information indicating that the core network type or the core network type is switched, information indicating that reattachment is necessary, or identification information of the MME. It may be used.
- the MME_A 40 may transmit a transmission UE context release message including at least the identification information of the UE 10 and a timer value.
- the timer value may be a timer value used by the eNB 45 for selecting an MME.
- the timer value may be a value set at the same time as the interval at which the UE 10 executes the tracking area update procedure or a time longer than that.
- the value of the timer may be a value set for a time until the UE 10 executes the next tracking area update procedure, or a time longer than that.
- the timer value may be a value set to the remaining time of the tracking area update timer of the UE 10 or a time longer than that.
- the tracking area update timer is a timer in which the UE 10 and the MME_A 40 start counting with the execution of the tracking area update procedure, and the UE 10 starts the tracking area update procedure with the consumption of the timer (expire). Therefore, the remaining time of the tracking area update timer is the time until the next tracking area update procedure is started.
- the eNB 45 receives a route reconfiguration request message from the MME_A 40.
- the eNB 45 may execute the MME information update process based on the information included in the route reconfiguration request message (S908). More specifically, the MME information update process may be executed based on the second instruction information.
- the MME information update process is a process of updating the MME information so that the eNB 45 selects an MME included in the core network (type 2) 92 in the MME selection performed in accordance with the reception of the tracking area request message transmitted by the UE 10. It may be.
- the eNB 45 may store the identification information of the UE 10 and the second instruction information in association with each other in the MME information update process.
- the eNB 45 may continue to hold the UE context information without deleting it by acquiring the second instruction information. On the other hand, the eNB 45 may delete the UE context information when the second instruction information is not acquired.
- the eNB 45 may start a timer count based on the second instruction information. The eNB 45 may continue to hold the updated MME information or UE context while the timer is being executed. Furthermore, when the timer is consumed or when the timer is stopped due to some factor, the eNB 45 may delete the updated MME information or UE context.
- timer value a value held in advance by the eNB 45 may be used, or a timer value included in the UE context release message may be used.
- timer value may be set to a timer value that is equal to or greater than the tracking area update procedure of the UE 10. Or you may set the value more than the remaining time of the tracking area update timer of UE10.
- the eNB 45 may continue to hold the MME information held before the MME information update process.
- MMEI corresponding to the MME_A 40 included in the core network (type 1) 90, MMEGI indicating the group of MMEs to which the MME_A 40 belongs may be kept.
- the eNB 45 may transmit a route reconfiguration response message to the MME_A 40 as a response to the route reconfiguration request message based on the completion of the MME information update process (S910).
- the eNB 45 may notify that the update process of the MME information has been completed by transmitting a route reconfiguration response message.
- the route reconfiguration response message may be transmitted including information indicating that the MME information is held.
- the UE 10 may start a tracking area update procedure. Note that the UE 10 may start the tracking area update procedure when the tracking area update timer that counts the transmission interval of the tracking area update request is consumed.
- UE10 transmits a tracking area update request message to eNB45, and starts a tracking area update procedure (S912).
- ENB 45 receives the tracking update request message from UE 10.
- the eNB 45 may execute the MME selection process based on the reception of the tracking area request message (S914).
- the eNB 45 selects the MME_B 42 based on the MME information update process. Moreover, eNB45 may select MME_A40, when the MME information update process is not performed.
- the eNB 45 can select either the MME_A 40 included in the core network (type 1) 90 or the MME_B 42 included in the core network (type 2) 92 according to the second instruction information.
- the eNB 45 selects an MME included in the core network (type 2) 92 during execution of the timer, and when the timer is not executed or when there is no need to switch the core network, the information transmitted by the UE 10 is transmitted.
- the MME included in the core network (type 1) may be selected based on the base.
- the MME included in the core network (type 1) may be selected based on the information transmitted by the UE 10.
- the selection method in that case may be selected based on information transmitted by the UE 10.
- the UE 10 transmits information for identifying the MME such as GUMMEI in the tracking area update request message.
- the eNB may select the received MME when the received MME is available.
- the eNB 45 may determine whether or not the MME is available based on the connectivity of the MME.
- the information transmitted by the UE 10 may be information for identifying the MME_A 40 that has managed the location of the UE 10.
- the UE 10 When the MME received from the UE 10 is not available, the UE 10 identifies the MME group identification information such as MMEI, the UE 10 identification information such as P-TMSI, or the TAI (Tracking Area ID) or TAC (Tracking). Position information such as (Area Code) or any two or more pieces of information may be included in the tracking area update request message and transmitted. The eNB 45 may receive these pieces of information and select an MME based on these pieces of information.
- MME group identification information such as MMEI
- P-TMSI the UE 10 identification information
- TAI Track Area ID
- TAC Tracking Area ID
- Position information such as (Area Code) or any two or more pieces of information may be included in the tracking area update request message and transmitted.
- the eNB 45 may receive these pieces of information and select an MME based on these pieces of information.
- the eNB 45 completes the MME selection process.
- the eNB 45 may determine whether to execute the MME selection process based on a timer that starts counting based on the MME information update process. For example, when the timer is counted, the MME selection process is performed, and after the timer has already ended or when the timer is not counted, the MME selection process may not be performed.
- the eNB 45 may select the MME_B 42 when the timer is being executed, and may select the MME_A 40 when the timer is not being executed. If the timer is not executed, the MME may be selected based on the MME identification information included in the tracking area update request message. For example, the MME identified by the tracking area update request message may be selected, the MME may be selected based on the MMEGI included in the tracking area update request message, or the default MME may be selected. . In this case, the eNB 45 may select the MME_A 40.
- eNB45 may stop a timer, when the tracking area update request message which UE10 transmits is received.
- the eNB 45 may perform MME selection based on the MME identification information included in the tracking area update request message. Good. For example, the MME identified by GUMMEI included in the tracking area update request message may be selected, or the MME may be selected based on the MMEGI included in the tracking area update request message, or the default MME may be selected. May be. In this case, the eNB 45 may select the MME_A 40.
- the eNB 45 When the eNB 45 selects the MME_B 42, the eNB 45 transmits a tracking area request message to the MME_B 42 (S916).
- the tracking area update procedure after sending the tracking area request message may be the same as the transmission / reception and processing of the control message similar to the conventional tracking update procedure. Therefore, detailed description is omitted.
- the eNB 45 may transmit a tracking area update request message to the MME_A 40. Further, the eNB 45 may receive a route reconfiguration request from the MME_A 40. Further, the eNB 45 may select the MME_B 42 based on the route reconfiguration request and transmit a tracking update request message to the MME_B 42. Note that the attachment procedure after the transmission of the tracking update request message may be the transmission / reception and processing of the control message similar to the conventional tracking update request message. Therefore, detailed description is omitted.
- the control message transmission / reception and the process can be reduced such that the tracking update request message can be executed without receiving the reroute reconfiguration request.
- UE 10 completes the tracking area update procedure and can communicate using the PDN connection.
- the core network (type 1) 90 and the core network (type 2) 92 have been described as being connected to the PDN_A 100 and the PDN_B 102, respectively.
- the PDN_A 100 and the PDN_B 102 are connected to the same network (PDN 100).
- PGW_A30 and PGW_B32 may be the same device (PGW_A30).
- the UE 10 changes the MME that performs mobility control from the MME_A 40 to the MMEB, but it is not necessary to re-establish the PDN connection.
- UE10 can continue communication using the PDN connection established between PGW_A30.
- the MME_A 40 may select a procedure according to the state of the UE 10 that is attaching. More specifically, the MME_A 40 manages the state of the UE 10 to which it is attached. As the state of the UE 10, it may be managed whether it is an idle state in which radio resources are released or an active state in which radio resources are allocated and data transmission / reception is possible.
- the MME_A 40 may select a procedure based on whether or not the PGW needs to be changed when the core network is changed. Whether or not to change the PGW may be determined based on a telecommunications carrier policy.
- the MME_A 40 may select the first procedure. More specifically, when the UE 10 is in the active state and the PGW needs to be changed, the UE 10 may transmit a detach request message (S504) and execute the subsequent first procedure.
- the MME_A 40 may select the second procedure. More specifically, when the UE 10 is in an active state and the PGW does not need to be changed, the UE 10 may transmit a UE context release message (S704), and execute the subsequent second procedure.
- the MME_A 40 may select the third procedure. More specifically, when the UE 10 is in an idle state and the PGW needs to be changed, the UE 10 may transmit a paging message (S804) and execute the subsequent third procedure.
- the MME_A 40 may select the fourth procedure. More specifically, when the UE 10 is in an idle state and the PGW does not need to be changed, the UE 10 may transmit a route reconfiguration request message (S904) and execute the subsequent fourth procedure.
- the MME_A 40 may execute selection of these procedures after detecting a trigger for starting the procedures.
- the MME_A 40 can take the lead and change the core network to which the UE 10 is connected.
- 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.
Abstract
Description
を提供するための移動通信システムであり、EPC(Evolved Packet Core)と呼ばれるコアネットワークやLTE(Long Term Evolution)とよばれる無線通信規格に基づくアクセスネットワーク等を含めて構成されている。
以下、図面を参照しながら本発明の実施形態による無線通信技術について詳細に説明する。
図1は、本実施形態における移動通信システムの概略を説明するための図である。本図に示すように、移動通信システム1は、移動端末装置UE10とアクセスネットワーク80とコアネットワーク(タイプ1)90とコアネットワーク(タイプ2)92とPDN(Packet Data Network)_A100とPDN_B102により構成されている。
続いて、各装置構成について図を用いて簡単に説明する。
図3(a)にeNB45の構成図を示す。図に示すように、eNB45は、IP移動通信ネットワークインターフェース部220と制御部200と記憶部240で構成されている。IP移動通信ネットワークインターフェース部220と記憶部240は、制御部200とバスを介して接続されている。
次に、MME_A40の構成を説明する。なお、MME_B42の構成も同様であるため、具体的な説明は省略する。
次に、コアネットワークを変更するための手続きを説明する。
まず、UE10が接続するコアネットワークを変更するための第1手続き例を説明する。手続きの初期状態において、UE10はコアネットワーク(タイプ1)90に接続している。より具体的には、UE10はeNB45に接続している。さらに、UE10はeNB45を介してMME_A40に接続している。さらに、UE10は、PGW_A30との間にPDNコネクションを確立している。ここで、PDNコネクションとはユーザデータを配送するための通信路のことである。
次に、UE10が接続するコアネットワークを変更するための第2手続き例を説明する。手続きの初期状態は、第1手続き例で説明した初期状態と同様であってよい。
次に、UE10が接続するコアネットワークを変更するための第3手続き例を説明する。手続きの初期状態は、第1手続き例で説明した初期状態と同様であってよい。
続いてアタッチ手続きについて説明する。UE10は、アタッチ要求メッセージをeNB45に送信し、アタッチ手続きを開始する(S818)。UE10は、アタッチ要求メッセージの送信により、再度コアネットワークへの接続を要求する。なお、UE10はアタッチ要求メッセージにUEの識別情報を含めて送信してもよい。
次に、UE10が接続するコアネットワークを変更するための第4手続き例を説明する。手続きの初期状態は、第1手続き例で説明した初期状態と同様であってよい。
タイマーを実行していない場合やコアネットワークを切り替える必要が無い場合は、UE10が送信する情報を基にコアネットワーク(タイプ1)に含まれるMMEを選択してもよい。
これまで、コアネットワークを変更するための手続きとして、第1手続き例から第4手続き例まで詳述してきた。なお、MME_A40は、条件により第1手続き例から第4続き例のうちどの手続きを実行するか決定してもよい。
以上、この発明の実施形態および変形例について図面を参照して詳述してきたが、具体的な構成はこの実施形態に限られるものではなく、この発明の要旨を逸脱しない範囲の設計等も特許請求の範囲に含まれる。
10 UE
30 PGW_A
32 PGW_B
35 SGW_A
37 SGW_B
40 MME_A
42 MME_B
45 eNB
50 HSS
55 AAA
60 PCRF
65 ePDG
70 WLAN ANa
75 WLAN ANb
80 LTE AN
90 コアネットワーク(タイプ1)
92 コアネットワーク(タイプ2)
100 PDN_A
102 PDN_B
Claims (26)
- 第1の位置管理装置を含む第1のコアネットワークと、第2の位置管理装置とを含む第2のコアネットワークとに接続する基地局装置であって、
少なくとも第1の識別情報を含むコンテキスト解放メッセージまたはルート再設定要求メッセージを前記第1の位置管理装置から受信し、
前記第1の識別情報は、前記第2のコアネットワークへ接続することを指示または要求する識別情報であり、
端末装置からアタッチ要求メッセージまたはトラッキングエリア更新要求メッセージを受信し、
前記第1の識別情報に基づいて前記第2の位置管理装置を選択し、
前記アタッチ要求メッセージまたは前記トラッキングエリア更新要求メッセージを、選択した前記第2の位置管理装置に送信する、
ことを特徴とする基地局装置。 - 前記第1の識別情報は、前記第2のコアネットワークに対応づけられたコアネットワークタイプである、
ことを特徴とする請求項1に記載の基地局装置。 - 前記第1の識別情報は、前記第2のコアネットワークに含まれる位置管理装置のグループ識別情報である、
ことを特徴とする請求項1に記載の基地局装置。 - 前記コンテキスト解放メッセージを受信した場合、
前記コンテキスト解放メッセージの受信に伴いタイマーを開始し、
前記タイマーを実行中である場合には、前記第1の識別情報に基づいて前記第2の位置管理装置を選択し、
前記タイマーを実行していない場合には、前記第1の位置管理装置を選択し、
前記アタッチ要求メッセージまたは前記トラッキングエリア更新要求メッセージを選択した前記第1の位置管理装置又は前記第2の位置管理装置に送信する、
ことを特徴とする請求項1から3の何れか一項に記載の基地局装置。 - 前記コンテキスト解放メッセージを受信した場合、
前記コンテキスト解放メッセージの受信に基づいて、RRCコネクション解放要求メッセージを前記端末装置に送信し、
前記RRCコネクション解放要求メッセージには、前記第2のコアネットワークへ接続することを指示または要求する第2の識別情報を少なくとも含める、
ことを特徴とする請求項1から4の何れか一項に記載の基地局装置。 - 端末装置であって、
少なくとも第1の識別情報とアタッチが必要であることを示す情報とを含むデタッチ要求メッセージを第1のコアネットワークに含まれる第1の位置管理装置から受信し、
前記第1の識別情報は、再度アタッチを指示または要求する識別情報であり、
前記デタッチ要求メッセージの受信に基づいて、少なくとも第2の識別情報を含めてアタッチ要求メッセージを基地局装置に送信してアタッチ手続きを開始し、
前記第2の識別情報は、第2のコアネットワークへ接続することを指示または要求する識別情報であり、
前記アタッチ手続きの完了に伴い、前記第2のコアネットワークに含まれるゲートウェイ装置との間にPDN(Packet Data Network)コネクションを確立する、
ことを特徴とする端末装置。 - 端末装置であって、
少なくとも第1の識別情報を含むページングメッセージを第1のコアネットワークに含まれる第1の位置管理装置から受信し、
前記第1の識別情報は、第2のコアネットワークへ接続することを指示または要求する識別情報であり、
前記ページングメッセージの受信に基づいて、サービス要求メッセージを前記第1の位置管理装置に送信し、
前記サービス要求メッセージの応答であり、少なくともデタッチした状態を示す識別情報を含むサービスリジェクトメッセージを第1の位置管理装置から受信し、
前記サービスリジェクトメッセージの受信に基づいて、少なくとも第2の識別情報を含めてアタッチ要求メッセージを基地局装置に送信してアタッチ手続きを開始し、
前記第2の識別情報は、前記第2のコアネットワークへ接続することを指示または要求する識別情報であり、
前記アタッチ手続きの完了に伴い、前記第2のコアネットワークに含まれるゲートウェイ装置との間にPDN(Packet Data Network)コネクションを確立する、
ことを特徴とする端末装置。 - 前記第1の識別情報及び/又は前記第2の識別情報は、前記第2のコアネットワークに対応づけられたコアネットワークタイプである、
ことを特徴とする請求項6又は7に記載の端末装置。 - 前記第1の識別情報及び/又は前記第2の識別情報は、前記第2のコアネットワークに含まれる位置管理装置のグループ識別情報である、
ことを特徴とする請求項6又は7に記載の端末装置。 - 第1のコアネットワークに含まれる位置管理装置であって、
少なくとも第1の識別情報を含むコンテキスト解放メッセージまたはルート再設定要求メッセージを基地局装置に送信し、
前記第1の識別情報は、第2のコアネットワークへ接続することを指示または要求する識別情報であり、
前記コンテキスト解放メッセージまたは前記ルート再設定要求メッセージの応答メッセージを前記基地局装置から受信する、
ことを特徴とする位置管理装置。 - 前記コンテキスト解放メッセージまたは前記ルート再設定要求メッセージを前記基地局装置に送信するために、少なくとも前記第1の識別情報を含むデタッチ要求メッセージまたはページングメッセージを端末装置に送信する、
ことを特徴とする請求項10に記載の位置管理装置。 - 前記第1の識別情報は、前記第2のコアネットワークに対応づけられたコアネットワークタイプである、
ことを特徴とする請求項10または11に記載の位置管理装置。 - 前記第1の識別情報は、前記第2のコアネットワークに含まれる位置管理装置のグループ識別情報である、
ことを特徴とする請求項10または11に記載の位置管理装置。 - 第1の位置管理装置を含む第1のコアネットワークと、第2の位置管理装置を含む第2のコアネットワークとに接続する基地局装置の制御方法であって、
少なくとも第1の識別情報を含むコンテキスト解放メッセージまたはルート再設定要求メッセージを前記第1の位置管理装置から受信するステップと、
前記第1の識別情報は、前記第2のコアネットワークへ接続することを指示または要求する識別情報であり、
端末装置からアタッチ要求メッセージまたはトラッキングエリア更新要求メッセージを受信するステップと、
前記第1の識別情報に基づいて前記第2の位置管理装置を選択し、
前記アタッチ要求メッセージまたは前記トラッキングエリア更新要求メッセージを選択した前記第2の位置管理装置に送信するステップと、
を有することを特徴とする基地局装置の制御方法。 - 第1の位置管理装置を含む第1のコアネットワークと、第2の位置管理装置を含む第2のコアネットワークとに接続する基地局装置の制御方法であって、
少なくとも第1の識別情報を含むコンテキスト解放メッセージを前記第1の位置管理装置から受信するステップと、
前記第1の識別情報は、前記第2のコアネットワークへ接続することを指示または要求する識別情報であり、
前記コンテキスト解放メッセージの受信に伴いタイマーを開始するステップと、
端末装置からアタッチ要求メッセージまたはトラッキングエリア更新要求メッセージを受信するステップと、
前記タイマーを実行中である場合には、前記第1の識別情報に基づいて前記第2の位置管理装置を選択して、前記アタッチ要求メッセージまたは前記トラッキングエリア更新要求メッセージを選択した第2の位置管理装置に送信するするステップと、
前記タイマーを実行していない場合には、前記第1の位置管理装置を選択して、前記アタッチ要求メッセージまたは前記トラッキングエリア更新要求メッセージを前記第1の位置管理装置に送信するステップと、
を有することを特徴とする基地局装置の制御方法。 - 前記第1の識別情報は、前記第2のコアネットワークに対応づけられたコアネットワークタイプである、
ことを特徴とする請求項14または15に記載の基地局装置の制御方法。 - 前記第1の識別情報は、前記第2のコアネットワークに含まれる位置管理装置のグループ識別情報である、
ことを特徴とする請求項14または15に記載の基地局装置の制御方法。 - 前記コンテキスト解放メッセージの受信に基づいて、RRCコネクション解放要求メッセージを前記端末装置に送信するステップと、
前記RRCコネクション解放要求メッセージには、前記第2のコアネットワークへ接続することを指示または要求する第2の識別情報を少なくとも含めるステップと、
を有することを特徴とする請求項14から17の何れか一項に記載の基地局装置の制御方法。 - 端末装置の制御方法であって、
少なくとも第1の識別情報とアタッチが必要であることを示す情報を含むデタッチ要求メッセージを第1のコアネットワークに含まれる第1の位置管理装置から受信するステップと、
前記第1の識別情報は、再度アタッチを指示または要求する識別情報であり、
デタッチメッセージの受信に基づいて、少なくとも第2の識別情報を含めてアタッチ要求メッセージを基地局装置に送信してアタッチ手続きを開始するステップと、
前記第2の識別情報は、第2のコアネットワークへ接続することを指示または要求する識別情報であり、
前記アタッチ手続きの完了に伴い、前記第2のコアネットワークに含まれるゲートウェイ装置との間にPDN(Packet Data Network)コネクションを確立するステップと、
を有することを特徴とする端末装置の制御方法。 - 端末装置の制御方法であって、
少なくとも第1の識別情報を含むページングメッセージを第1のコアネットワークに含まれる第1の位置管理装置から受信するステップと、
前記第1の識別情報は、第2のコアネットワークへ接続することを指示または要求する識別情報であり、
前記ページングメッセージの受信に基づいて、サービス要求メッセージを前記第1の位置管理装置に送信するステップと、
前記サービス要求メッセージの応答であり、少なくともデタッチした状態を示す識別情報を含むサービスリジェクトメッセージを第1の位置管理装置から受信するステップと、
前記サービスリジェクトメッセージの受信に基づいて、少なくとも第2の識別情報を含めてアタッチ要求メッセージを基地局装置に送信してアタッチ手続きを開始するステップと、
前記第2の識別情報は、前記第2のコアネットワークへ接続することを指示または要求する識別情報であり、前記アタッチ手続きの完了に伴い、前記第2のコアネットワークに含まれるゲートウェイ装置との間にPDN(Packet Data Network)コネクションを確立するステップと、
を有することを特徴とする端末装置の制御方法。 - 前記第1の識別情報及び/又は前記第2の識別情報は、第2のコアネットワークに対応づけられたコアネットワークタイプである、
ことを特徴とする請求項19又は20に記載の端末装置の制御方法。 - 前記第1の識別情報及び/又は前記第2の識別情報は、第2のコアネットワークに含まれる位置管理装置のグループ識別情報である、
ことを特徴とする請求項19又は20に記載の端末装置の制御方法。 - 第1のコアネットワークに含まれる位置管理装置の制御方法であって、
少なくとも第1の識別情報を含むコンテキスト解放メッセージまたはルート再設定要求メッセージを基地局装置に送信するステップと、
前記第1の識別情報は、第2のコアネットワークへ接続することを指示または要求する識別情報であり、
前記コンテキスト解放メッセージまたは前記ルート再設定要求メッセージの応答メッセージを前記基地局装置から受信するステップと、
を有することを特徴とする位置管理装置の制御方法。 - 前記コンテキスト解放メッセージまたは前記ルート再設定要求メッセージを前記基地局装置に送信するために、少なくとも前記第1の識別情報を含むデタッチ要求メッセージまたはページングメッセージを端末装置に送信するステップ、
を有することを特徴とする請求項23に記載の位置管理装置の制御方法。 - 前記第1の識別情報は、前記第2のコアネットワークに対応づけられたコアネットワークタイプである、
ことを特徴とする請求項23または24に記載の位置管理装置の制御方法。 - 前記第1の識別情報は、前記第2のコアネットワークに含まれる位置管理装置のグループ識別情報である、
ことを特徴とする請求項23または24に記載の位置管理装置の制御方法。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2016552863A JP6630675B2 (ja) | 2014-10-06 | 2015-08-28 | Ue、基地局装置、ueの通信制御方法及び基地局の通信制御方法 |
US15/517,145 US10231176B2 (en) | 2014-10-06 | 2015-08-28 | Base station device, terminal device, location management device, and control method |
US16/279,463 US11770761B2 (en) | 2014-10-06 | 2019-02-19 | Base station device, terminal device, location management device, and control method |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2014-205334 | 2014-10-06 | ||
JP2014205334 | 2014-10-06 |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/517,145 A-371-Of-International US10231176B2 (en) | 2014-10-06 | 2015-08-28 | Base station device, terminal device, location management device, and control method |
US16/279,463 Continuation US11770761B2 (en) | 2014-10-06 | 2019-02-19 | Base station device, terminal device, location management device, and control method |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016056321A1 true WO2016056321A1 (ja) | 2016-04-14 |
Family
ID=55652945
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2015/074483 WO2016056321A1 (ja) | 2014-10-06 | 2015-08-28 | 基地局装置、端末装置、位置管理装置および制御方法 |
Country Status (3)
Country | Link |
---|---|
US (2) | US10231176B2 (ja) |
JP (2) | JP6630675B2 (ja) |
WO (1) | WO2016056321A1 (ja) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2018008239A1 (ja) * | 2016-07-08 | 2018-01-11 | 株式会社Nttドコモ | 無線通信システム |
CN108781402A (zh) * | 2016-04-20 | 2018-11-09 | 华为技术有限公司 | 专用核心网迁移处理方法、设备和系统 |
CN109309947A (zh) * | 2017-07-26 | 2019-02-05 | 维沃移动通信有限公司 | 指示终端接入核心网、接入核心网的方法、基站及终端 |
JP2019519180A (ja) * | 2016-06-27 | 2019-07-04 | 華為技術有限公司Huawei Technologies Co.,Ltd. | ネットワーク・エッジ・コンピューティングを使って仮想化ネットワーク機能を展開するための方法、装置およびシステム |
JP2021513231A (ja) * | 2017-12-18 | 2021-05-20 | オッポ広東移動通信有限公司Guangdong Oppo Mobile Telecommunications Corp., Ltd. | ネットワークのリダイレクト方法、端末、アクセスネットワークデバイス及び移動管理デバイス |
CN114375023A (zh) * | 2021-12-28 | 2022-04-19 | 天翼物联科技有限公司 | 终端附着upf的处理方法、系统、装置和存储介质 |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10863382B2 (en) * | 2015-03-12 | 2020-12-08 | Nec Corporation | Methods and systems for balancing load among communication control apparatuses |
CN106332222A (zh) * | 2015-07-02 | 2017-01-11 | 北京三星通信技术研究有限公司 | 一种网络选择的方法和基站 |
EP3799479B1 (en) | 2015-09-18 | 2023-06-21 | Huawei Technologies Co., Ltd. | Selection of a dedicated core network based on a service type |
JP2018538744A (ja) * | 2015-11-19 | 2018-12-27 | エスケー テレコム カンパニー リミテッドSk Telecom Co., Ltd. | 移動通信システムにてコアネットワークを選択する方法及び装置 |
CN108476459A (zh) * | 2016-01-18 | 2018-08-31 | 华为技术有限公司 | 一种拥塞控制方法及装置 |
US10257078B2 (en) | 2016-04-01 | 2019-04-09 | Qualcomm Incorporated | Interworking with legacy radio access technologies for connectivity to next generation core network |
CN109076328B (zh) * | 2016-05-10 | 2021-07-16 | 华为技术有限公司 | 移动性管理方法和装置 |
KR20170128043A (ko) * | 2016-05-13 | 2017-11-22 | 삼성전자주식회사 | 무선 이동통신 시스템에서 자원 이용 방법 및 장치 |
CN107770847B (zh) * | 2016-08-22 | 2020-11-27 | 华为技术有限公司 | 网络接入方法、接入设备和终端设备 |
US10064048B1 (en) * | 2018-01-05 | 2018-08-28 | Hong Kong Applied Science and Technology Research Institute Company Limited | Acquiring permanent identifier of user equipment by gateway in mobile communication system |
Family Cites Families (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8831606B2 (en) * | 2007-07-18 | 2014-09-09 | Zte Corporation | Mobile terminal registration method in a radio network |
CN101610504B (zh) * | 2008-06-18 | 2012-08-08 | 上海华为技术有限公司 | 接入、获取用户设备上下文及用户设备标识的方法和装置 |
MY156860A (en) * | 2011-09-30 | 2016-04-05 | Nec Corp | Communication System, Method, and Apparatus |
EP2873257A4 (en) * | 2012-07-10 | 2016-03-09 | Ericsson Telefon Ab L M | REDUCE A SIGNALING LOAD BY CHANGING THE POSITION OF TERMINALS |
JP6196103B2 (ja) * | 2013-09-13 | 2017-09-13 | 株式会社Nttドコモ | 移動通信システム、ネットワークノード及び移動通信方法 |
KR101903928B1 (ko) * | 2013-09-27 | 2018-10-02 | 닛본 덴끼 가부시끼가이샤 | 통신 시스템, 기지국, 통신 방법, 및 프로그램을 저장한 비일시적 컴퓨터 판독가능 매체 |
JP6420337B2 (ja) * | 2013-11-01 | 2018-11-07 | 華為技術有限公司Huawei Technologies Co.,Ltd. | ネットワーク選択方法およびコアネットワーク装置 |
WO2015167722A1 (en) * | 2014-04-28 | 2015-11-05 | Intel IP Corporation | Communication via dedicated network nodes |
US9398500B2 (en) * | 2014-05-08 | 2016-07-19 | Intel IP Corporation | Systems, methods, and devices for cell selection based on prioritized nodes |
KR102321203B1 (ko) * | 2014-05-08 | 2021-11-04 | 인터디지탈 패튼 홀딩스, 인크 | Ue를 전용 코어 네트워크 노드에 리디렉트하기 위한 방법들 및 이동성 관리 엔티티(mme) |
CN105142128B (zh) * | 2014-06-05 | 2020-01-14 | 中兴通讯股份有限公司 | 专用网络选择方法及装置 |
WO2016002692A1 (ja) * | 2014-07-01 | 2016-01-07 | シャープ株式会社 | 基地局装置、第1の位置管理装置、端末装置、通信制御方法、および通信システム |
US9674749B2 (en) * | 2014-08-14 | 2017-06-06 | Samsung Electronics Co., Ltd. | Method and apparatus for selecting dedicated core network |
US10375564B2 (en) * | 2015-01-14 | 2019-08-06 | Lg Electronics Inc. | Method for updating area in wireless communication system, and device therefor |
EP3286981A1 (en) * | 2015-03-18 | 2018-02-28 | Nec Corporation | Communication system |
-
2015
- 2015-08-28 US US15/517,145 patent/US10231176B2/en not_active Expired - Fee Related
- 2015-08-28 WO PCT/JP2015/074483 patent/WO2016056321A1/ja active Application Filing
- 2015-08-28 JP JP2016552863A patent/JP6630675B2/ja active Active
-
2019
- 2019-02-19 US US16/279,463 patent/US11770761B2/en active Active
- 2019-12-09 JP JP2019222433A patent/JP2020053993A/ja active Pending
Non-Patent Citations (2)
Title |
---|
"3GPP TS 23.401 V13.0.0", TECHNICAL SPECIFICATION GROUP SERVICES AND SYSTEM ASPECTS;GENERAL PACKET RADIO SERVICE (GPRS) ENHANCEMENTS FOR EVOLVED UNIVERSAL TERRESTRIAL RADIO ACCESS NETWORK (E-UTRAN) ACCESS (RELEASE 13), September 2014 (2014-09-01), pages 30 - 31, 140-142 * |
3RD GENERATION PARTNERSHIP PROJECT;: "Technical Specification Group Services and System Aspects;Architecture Enhancements for Dedicated Core Networks;Stage 2(Release 13", 3GPP TR 23.707 V0.2.0, July 2014 (2014-07-01), pages 8 - 10 , 14- 16, 18-20 * |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108781402A (zh) * | 2016-04-20 | 2018-11-09 | 华为技术有限公司 | 专用核心网迁移处理方法、设备和系统 |
EP3448089A4 (en) * | 2016-04-20 | 2019-02-27 | Huawei Technologies Co., Ltd. | METHOD FOR PROCESSING THE MIGRATION OF A DEDICATED CORE NETWORK, EQUIPMENT AND SYSTEM |
JP2019519180A (ja) * | 2016-06-27 | 2019-07-04 | 華為技術有限公司Huawei Technologies Co.,Ltd. | ネットワーク・エッジ・コンピューティングを使って仮想化ネットワーク機能を展開するための方法、装置およびシステム |
US11036536B2 (en) | 2016-06-27 | 2021-06-15 | Huawei Technologies Co., Ltd. | Method, apparatus, and system for deploying virtualized network function using network edge computing |
WO2018008239A1 (ja) * | 2016-07-08 | 2018-01-11 | 株式会社Nttドコモ | 無線通信システム |
CN109309947A (zh) * | 2017-07-26 | 2019-02-05 | 维沃移动通信有限公司 | 指示终端接入核心网、接入核心网的方法、基站及终端 |
CN109309947B (zh) * | 2017-07-26 | 2021-04-27 | 维沃移动通信有限公司 | 指示终端接入核心网、接入核心网的方法、基站及终端 |
JP2021513231A (ja) * | 2017-12-18 | 2021-05-20 | オッポ広東移動通信有限公司Guangdong Oppo Mobile Telecommunications Corp., Ltd. | ネットワークのリダイレクト方法、端末、アクセスネットワークデバイス及び移動管理デバイス |
US11576097B2 (en) | 2017-12-18 | 2023-02-07 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Method and terminal for redirecting network |
CN114375023A (zh) * | 2021-12-28 | 2022-04-19 | 天翼物联科技有限公司 | 终端附着upf的处理方法、系统、装置和存储介质 |
CN114375023B (zh) * | 2021-12-28 | 2024-03-12 | 天翼物联科技有限公司 | 终端附着upf的处理方法、系统、装置和存储介质 |
Also Published As
Publication number | Publication date |
---|---|
US20190182761A1 (en) | 2019-06-13 |
JP2020053993A (ja) | 2020-04-02 |
US11770761B2 (en) | 2023-09-26 |
US20170311245A1 (en) | 2017-10-26 |
JPWO2016056321A1 (ja) | 2017-07-20 |
JP6630675B2 (ja) | 2020-01-15 |
US10231176B2 (en) | 2019-03-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP6630675B2 (ja) | Ue、基地局装置、ueの通信制御方法及び基地局の通信制御方法 | |
JP6750003B2 (ja) | Ue及びueの通信方法 | |
US11026208B2 (en) | Base station device, first location management device, terminal device, communication control method, and communication system | |
KR102367342B1 (ko) | 단말 장치, 기지국 장치, MME(Mobility Management Entity) 및 통신 제어 방법 | |
US20170318613A1 (en) | Base station device, position management device, terminal device, and control method | |
US11284312B2 (en) | User equipment and communication control method performed by user equipment | |
JP2020113807A (ja) | ユーザ装置 | |
US11259242B2 (en) | User equipment | |
US20160353498A1 (en) | Communication control method, position management device, base station device, terminal device, and communication system | |
US11284320B2 (en) | User equipment | |
JPWO2016163420A1 (ja) | 端末装置、mme及びpgw | |
WO2014054610A1 (ja) | 移動通信システム、第1の基地局装置、移動局装置及び移動通信システムの通信方法 | |
CN113056902A (zh) | 用户装置、控制装置以及通信控制方法 | |
WO2014054644A1 (ja) | 移動通信システム、第2の基地局装置、移動局装置及び移動通信システムの通信方法 | |
JPWO2016163414A1 (ja) | 端末装置、TWAG、ePDG及びPGW | |
JPWO2016163411A1 (ja) | 端末装置、pgw及びtwag | |
US20220369220A1 (en) | User equipment (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: 15849241 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2016552863 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15517145 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 15849241 Country of ref document: EP Kind code of ref document: A1 |