CN108810867A - System, core network node, terminal, radio access network node and method - Google Patents

System, core network node, terminal, radio access network node and method Download PDF

Info

Publication number
CN108810867A
CN108810867A CN201810397978.4A CN201810397978A CN108810867A CN 108810867 A CN108810867 A CN 108810867A CN 201810397978 A CN201810397978 A CN 201810397978A CN 108810867 A CN108810867 A CN 108810867A
Authority
CN
China
Prior art keywords
mme
sgsn
terminal
customization
request
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN201810397978.4A
Other languages
Chinese (zh)
Inventor
前佛创
田村利之
岩井孝法
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NEC Corp
Original Assignee
NEC Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by NEC Corp filed Critical NEC Corp
Publication of CN108810867A publication Critical patent/CN108810867A/en
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/16—Communication-related supplementary services, e.g. call-transfer or call-hold
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0092—Indication of how the channel is divided
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • 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
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/06—Registration at serving network Location Register, VLR or user mobility server
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Databases & Information Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The present invention relates to system, core network node, terminal, radio access network node and methods.The system comprises：Core network node；Terminal；Radio access network node, wherein the core network node is configured as：Information corresponding with the usage type of the terminal is sent to the radio access network node；The terminal is configured as：TAU/RAU requests are sent to the radio access network node；The radio access network node is configured as：After receiving the TAU/RAU requests, core network node is selected based on described information.

Description

System, core network node, terminal, radio access network node and method
The application be the applying date be September in 2012 28, entitled " communication system, method and apparatus ", application number For：201280048275.1 Chinese invention patent application divisional application.
Technical field
(citation of related applications)
The present invention is based on and require that the Japanese patent application No.2011-217384's submitted for 30th in September in 2011 is excellent The equity first weighed, the entire disclosure are incorporated herein by being quoted to it.
The present invention relates to communication system, method and apparatus.
Background technology
In the core network of mobile communication system, in order to provide various services, core net to various terminals (movement station) It is necessary to be provided with each required function of service for all nodes in network.It is many in Large-scale Mobile communication network etc. Node is arranged within the core network.When each location register, terminal is connected to the section in core network in a distributed way Point.
Therefore, all nodes in core network need necessary function (the service offer work(for having for each servicing Can).Even when a part of node in core network does not have the essential service for each service provision function, all can not Ensure the service continuity of terminal.
For example, patent document 1 disclose it is a kind of for based on the type of the service utilized by movement station come optimize grouping The arrangement of forward-path, wherein when movement station utilizes the service from external network, carrying out limitation to packet forwarding path makes It obtains stream of packets and specific cluster retransmission unit is passed through based on external network.When the clothes provided by mobile communications network are utilized in movement station When business, packet forwarding path is not limited.
[patent document 1]
Japanese Laid-Open Patent Publication No.2003-338832A
Invention content
Some analyses of the prior art are described below.
As described above, because each node in core network has the whole services for providing function, need each Node has high functionality and high-performance.Therefore, each core network node becomes expensive.
For example, because relatively small number purpose mobile terminal (delivers simultaneously with MBMS (multicast broadcast multimedia service) services Service) it is compatible, so providing MBMS service without too many chance, MBMS service is marked by 3GPP (third generation partner program) Standardization and the carrying service for realizing broadcast-type delivering.However, in order to provide services to the MBMS user of peanut, communication fortune Seeking quotient, it is necessary to make all nodes in core network equipped with MBMS functions.Otherwise, common carrier can not be to peanut MBMS user provides service.
If whether can need to select the node in core network using MBMS service based on mobile terminal, communicate Operator can install the relatively small number purpose costliness core network node compatible with MBMS and not compatible with MBMS in combination Many cheap core network nodes.In this manner, it is possible to generally more effectively reduce equipment cost (the first of the present inventor Knowledge).
In addition, the 3GPP machine communications (MTC being widely used in recent years：Machine-type communication) equipment (M2M equipment) exists Mobility characteristic, requirement communication quality etc. be significantly different from the normal terminal for call (hand-held be whole End), mobile telephone terminal and smart phone etc..It is well known that, there are various types of machine communication services, such as Long-range in the remote management of inventory and the charging of automatic vending machine, sensing system supervise, vehicle monitoring and intelligent grid.
In core network node, for example, the node of MTC compatibilities is customized to be suitable for accommodating to exchange more than normal node More control signals and less user data terminal (MTC device) (though for example, the node of these MTC compatibilities be customized to so that The performance of the user plane of exchanging user data is so reduced for cost reduction, but control the control plane of signal system Performance is enhanced).Therefore, unless common carrier makes all core network nodes are equipped with to have successfully connected to MTC device With the necessary ability and function of handheld terminal, otherwise common carrier both MTC device and handheld terminal can not be carried For service.This is suitable for MBMS service.
If MTC device and handheld terminal may be coupled to core network node appropriate respectively, communication is allowed to transport Battalion quotient arrange the relatively inexpensive core network node for being used for handheld terminal and in combination for the relatively inexpensive of MTC device Core network node (the second knowledge of the present inventor).
It is each compatible with handheld terminal and MTC device relatively expensive with installation if situation is such Core network node compare, can more effectively reduce the equipment cost (the third knowledge of the present inventor) of whole system.
Therefore, the present invention has been carried out to solve the above problems, and the purpose of the present invention is to provide one kind to be used for More effectively in the system, method and the equipment that generally reduce equipment cost and cost of implementation and reduce of system.
The present invention to solve the above problems usually has following configuration (but not limited to).
According to an aspect of the invention, there is provided a kind of includes the communication system of the core network for mobile communication system System, wherein core network include multiple nodes, and each node is used as the ambulant node for management terminal, and multiple nodes close It is different from each other in the service function that node provides the terminal with, and
It is wherein based on subscriber information and end message, according to the service characteristic utilized by terminal or according to the class of terminal Type, selection will be connected to the node of terminal in multiple nodes, and terminal is connected to selected node.It additionally provides A kind of mobile communication system, including：
Terminal (UE (user equipment) or MS (movement station)), the terminal support work(associated with MTC (machine-type communication) Energy；
Base station；And
Specific MME (mobility management entity) or SGSN (service GPRS (General Packet Radio Service) supporting node),
Wherein, the terminal of function associated with MTC is supported to be configured to provide instruction RRC (radio resources to base station Control) connection request include the function information, and
Wherein, the instruction information that base station is configured to be provided using the terminal by support function will support the function Terminal is directed to specific MME or SGSN, or the specific MME or SGSN of selection.
According to another aspect of the present invention, a kind of communication means is provided, including：
By for multiple inserting knots of terminal, in mobile communication system core network, which is used as managing end The ambulant node at end, and it is supplied to the service function of terminal and different from each other about node；
Based on subscriber information and end message, according to the characteristic serviced used in terminal or according to the type of terminal To select the node that be connected to terminal in the multiple node；And
Terminal is connected to selected node.
A kind of communication means for mobile communication system is additionally provided, mobile communication system includes at least support and MTC The terminal (UE (user equipment) or MS (movement station)), base station and specific MME (mobility of (machine-type communication) relevant function Management entity) or SGSN (service GPRS (General Packet Radio Service) supporting node), this method includes：
It includes the function to support that the terminal of the function provides instruction RRC (radio resource control) connection request to base station Information, and
Base station using the instruction information provided by terminal will support the terminal of the function be directed to specific MME or SGSN, or the specific MME or SGSN of selection.
According to another aspect of the present invention, a kind of node apparatus is provided, which performs control to based on subscriber Information and end message are by another mobile management section of the type compatibility with the service characteristic and terminal that are utilized by terminal Point device is selected as the ambulant mobile management node apparatus for management terminal, terminal is connected to selected another One mobile management node apparatus.
A kind of base station in mobile communication system is additionally provided, mobile communication system includes at least terminal, and ((user sets UE It is standby) or MS (movement station)) and specific MME (mobility management entity) or SGSN ((general packet radio takes service GPRS Business) supporting node), which supports and MTC (machine-type communication) relevant function, and wherein base station includes：
It is configured to from supporting that the terminal of the function receives instruction RRC (radio resource control) connection request include the function Information unit；And
It is configured to using by supporting the instruction information that the terminal of the function is provided that the terminal of the function will be supported to guide To the unit of specific MME or SGSN or the specific MME or SGSN of selection.
A kind of terminal in mobile communication system is additionally provided, mobile communication system includes at least：Base station and specific MME (mobility management entity) or SGSN (service GPRS (General Packet Radio Service) supporting node), and terminal be support with The terminal (UE (user equipment) or MS (movement station)) of MTC (machine-type communication) relevant function, which includes：
It is configured to provide the list that instruction RRC (radio resource control) connection request includes the information of the function to base station Member；And
It is arranged so that base station will support the terminal of the function to be directed to spy using the instruction information provided by terminal Determine the unit of MME or SGSN or the specific MME or SGSN of selection.
In accordance with the invention it is possible to be dropped come cost of implementation by more effectively reducing the equipment cost of entire core network system It is low.
Description of the drawings
Fig. 1 is the figure for the system configuration for illustrating the first exemplary embodiment according to the present invention.
Fig. 2 is the figure for the system configuration for illustrating the second exemplary embodiment according to the present invention.
Fig. 3 is the figure for illustrating the first exemplary sequence according to the present invention.
Fig. 4 is the figure for illustrating the second exemplary sequence according to the present invention.
Fig. 5 is the figure for illustrating the exemplary sequence of third according to the present invention.
Fig. 6 is the figure for illustrating the exemplary sequence of third according to the present invention.
Fig. 7 is the figure for illustrating the 4th exemplary sequence according to the present invention.
Fig. 8 is the figure for illustrating the 5th exemplary sequence according to the present invention.
Fig. 9 is the figure for illustrating the 5th exemplary sequence according to the present invention.
Figure 10 is the figure for illustrating the 6th exemplary sequence according to the present invention.
Figure 11 is the figure for illustrating the 7th exemplary sequence according to the present invention.
Figure 12 is the figure for illustrating the 8th exemplary sequence according to the present invention.
Figure 13 is the figure for illustrating the 8th exemplary sequence according to the present invention.
Figure 14 is the figure for illustrating the 9th exemplary sequence according to the present invention.
Figure 15 is the figure for illustrating the tenth exemplary sequence according to the present invention.
Figure 16 is the figure for illustrating the tenth exemplary sequence according to the present invention.
Specific implementation mode
First, by the summary with reference to figure 1 and Fig. 2 description present invention.According to the present invention, core network, which is included in, puies forward terminal Multiple nodes (121/122 in 22/22 or Fig. 2 in Fig. 1) different from each other in terms of the service function of confession.Based on subscriber information And end message, it selects to be connected to terminal from multiple nodes according to the type of the service characteristic or terminal that are utilized by terminal Node.Terminal (101 in 1 or Fig. 2 in Fig. 1) is connected to selected node.That is, within the core network, in combination The node (122 in 22 or Fig. 2 in Fig. 1) that there are predetermined special services to provide function is installed and is provided without special services The node (121 in 21 or Fig. 2 in Fig. 1) of function.
Therefore, according to the present invention, pass through and two types are installed, that is, optimization has the node and not that special services provide function Node with special services offer function is arranged as the node for being connectable to terminal with all nodes in core network The ability for being useful for all services is compared with the case where function, can further decrease the cost of whole system.
According to the present invention, in communication of mobile terminal network, terminal can be according to such as service characteristic or terminal type Condition is connected to particular core network node.
<Pattern 1>
General MME (mobility management entity) is from UE, (user equipment is also known as user equipment, terminal or movement Stand) when receiving attached request, determine whether UE has the type using special services based on subscriber information and end message. When UE is the type, MME is reselected into request signal (mobile management in order to which UE is connected to customization MME, general MME Entity reselects request signal) it is transferred to e nodes B (the node B of evolution：Base station apparatus).
It is connected to customization MME by the way that attached request is re-transmitted to customization MME, UE by e nodes B.
<Pattern 2>
General MME changes request signal when receiving attached request from UE, by MME, and (mobility management entity change is asked Seek signal) it is transferred to customization MME, in order to which UE is connected to customization MME.By continuing attached process by customizing MME, UE is connected It is connected to customization MME.
<Pattern 3>
General MME from UE when receiving attached request, to UE transmission to which are added the attached of the identifier of customization MME Refusal, in order to which UE is connected to customization MME.By transmitting UE again to the attached identifier for asking to be added to customization MME Attached request, UE are connected to customization MME.
<Pattern 4>
UE is to e nodes B transmission to which are added the connectivity request messages for asking the connection to customization MME (specific MME) RRC (radio resource control) connection request (radio resource connects request).When utilize established RRC connections from UE to When MME transmission attaches request, e nodes selection customization MME is so that UE is connected to customization MME.
<Pattern 5>
When the general MME with the session established with UE executes what the S1 established between e nodes B and general MME was connect When discharging (S1 releases), in next selection of MME, general MME instruction e nodes B selection customizations MME.Hereafter, when UE transmits position When setting management region update request (TA (tracing area) update request), e nodes B selections customization MME so that UE be connected to it is fixed MME processed.
<Pattern 6>
When receiving attached request from UE, general SGSN (service GPRS (general packet radio service) supporting nodes：? It is described as in claim " Serving GPRS Support Node ") made to determine whether UE has based on subscriber information and end message With the type of special services.If UE is the type, SGSN is customized in order to which UE to be connected to, general SGSN selects SGSN again It selects request signal and is transferred to RNC (radio network controller).UE is set to connect by the way that attached request is transferred to customization SGSN, RNC To customization SGSN.
<Mode 7>
When receiving attached request from UE, SGSN change request signals are transferred to customization SGSN by general SGSN, so as to SGSN is customized in UE to be connected to.Continue attached process by customizing SGSN, UE is connected to customization SGSN.
<Pattern 8>
When receiving attached request from UE, general SGSN is transmitted to UE to which are added the attached of the identifier of customization SGSN Even refuse, in order to which UE is connected to customization SGSN.The identifier of customization SGSN is added to attachment request by transmitting again Attached request, UE be connected to customization SGSN.
<Pattern 9>
UE is transmitted to RNC to the connection request (RRC which are added request to the connectivity request message of the connection of customization SGSN Connection request).When transmitting attached request to SGSN from the UE of the RRC connections with foundation, RRC connection request has been received RNC selection customization SGSN so that UE be connected to customization SGSN.
<Pattern 10>
When the general SGSN of the session with UE with foundation executes Iu releases, in next selection of SGSN, generally SGSN instructs RNC selection customizations SGSN.Hereafter, when (RA (Routing Area) updates are asked for UE transmission location management regions update request Ask) when, RNC selections customization SGSN is so that UE is connected to customization SGSN.
As described in pattern 1 to 10 above, according to the present invention, the characteristic of the service used based on terminal is selected It selects core network and is connected to terminal.In this way, within the core network, node with specific service provision function and Node without such function is arranged in which can be combined.That is, by optimizing specific node to have specific service to carry For function and by configuring other nodes for not having such special services and providing function, node can be distinguished. As a result, it is possible to reduce the equipment cost in whole system.Exemplary embodiment and specific example are described below with reference to attached drawing.
<Exemplary embodiment 1>
Fig. 1 illustrates exemplary embodiment of the present invention 1.As exemplary embodiment 1, will be described with EPC (evolution Block core) configuration.In the configuration, UE transmission attaches request and UE is connected to customization MME.
In Fig. 1, UE 1 (user equipment) is the terminal that service is received from customization MME.For example, UE 1 can be above-mentioned The terminal etc. of MTC device, MBMS compatibilities.The normal mobile station using normal service in UE 1, such as mobile telephone terminal or In the case of person's smart phone (the incompatible terminal with the special services of such as MTC or MBMS), UE 1 is connected to generally MME.In addition, as being described below, when in response to come from normal mobile station (for example, from such as MTC or MBMS The incompatible terminal of special services) attached request and select customization MME when, execute reselecting for MME, and UE 1 is weighed Newly it is connected to general MME.
E nodes B 11 is the base station apparatus in LTE (long term evolution).
MME 21 and MME 22 is the mobile management device introduced in EPC.It is that UE 1 needs to connect to customize MME 22 The customization MM2 arrived, and general MME (21) is the MME other than such customization MME.It, can although not limited MME 22 is for example customized to configure, (M2M is set as the terminal customization MME for servicing and being compatible with for machine communication (MTC) It is standby) (for example, C plane treatment network-controls are reinforced).Alternatively, customization MME 22 may be configured to the MME of MBMS compatibilities.
HSS (home subscriber servers) 31 is the database for storing subscriber information.
S-GW (gateway) 41 and P-GW (grouped data network gateway) 51 is the device for handling user plane.
Service network 61 is external network.
In Fig. 1, e nodes B corresponds to the device in radio access network (RAN), and MME, S-GW, P-GW etc. are corresponding Device in core network (CN).
Next, the above exemplary embodiments 1 will be described based on several examples.The different control described in each example Scheme processed.Example 1 to 5 corresponds respectively to above-mentioned pattern 1 to 5.
<Example 1>
Fig. 3 is the sequence chart for illustrating the operation according to example 1.
In figure 3,
UE corresponds to the UE 1 in Fig. 1,
E nodes B corresponds to the e nodes B 11 in Fig. 1,
General MME " corresponds to the general MME 21 in Fig. 1,
The customization MME 22 that MME corresponds in Fig. 1 is customized,
The S-GW 41 that GW corresponds in Fig. 1 is serviced,
PDN GW correspond to the P-GW 51 in Fig. 1, and
HSS corresponds to the HSS 31 in Fig. 1.
" PCRF " is "Policy and Charging Rules Function.In addition, (world is mobile by EIR (equipment identity register) storages IMEI Equipment identities) etc., and it is connected to MME via S13 interfaces.
In figure 3, for example, " 1. attached request " indicates that the transmission of the attached request of node B is sequence 1 from UE to e.In order to The reference numeral 1 (reference numeral with component) of UE in the reference numeral of the sequence and Fig. 1 is distinguished, the sequence number 1 It will be expressed as " attached request (1) " with bracket in the following description.Other sequences number also indicates in an identical manner.This Outside, it will also be indicated in an identical manner with the sequence number in subsequent sequence figure in Fig. 4.Fig. 3 is based on 3GPP TS23.401 In Fig. 5 .3.2.1-1：Attached process, and sequence number is according to the figure.The details of each sequence is in 3GPP TS23.401 5.3.2 it is described in.Hereinafter, the sequence of operation will be described with reference to figure 1 and Fig. 3.
As illustrated in figure 3, when UE 1 transmits attached request (1), first, e nodes B 11 receives attached request (1).Next, e nodes B 11 relays attached request (2) to MME.
At this sequence, it is to ask (2) to be forwarded to general MME 21 also by attached that e nodes B 11, which can not be uniquely determined, It is to be forwarded to customization MME 22.The case where attached request (2) is forwarded to general MME 21 accordingly, there exist e nodes B 11.
After receiving attached request (2), general MME 21 obtains end message via identity request/response from UE 1 (ME identity) (4,5b).
Note that ME identity checks request (5b) is transferred to EIR by general MME 21, and EIR is by ME identity checks responses It is (not shown) to return to general MME.In addition, coordinating with HSS 31, general MME 21 executes certification and obtains subscriber profiles. That is, in this case, general MME 21 executes certification and obtains subscriber profiles.
For general MME 21 in the acquisition of end message and subscriber profiles, determination is that UE 1 is connected to general MME 21 also It is attached to customization MME 22.
When general MME 21 determines that UE 1 needs to be connected to general MME 21, general MME 21 continues normally attached Process.
When general MME 21 determines that the needs of UE 1 are connected to customization MME 22, general MME 21 is by MME selection signals (MME reselects order) (S1AP (S1 applications) signal newly introduced in the present example embodiment) is sent to e nodes B 11, With reselecting for command M ME.
In this sequence, general MME 21 sets the identifier of customization MME 22 in MME reselects command signal (for example, GUMMEI (the unique MME identity in the whole world)).That is, before the establishment of carrying within the core network, general MME 21 will be weighed New selection request is transferred to e node B, includes for selecting the necessary information of new MME (GUMMEI) reselecting request. MME is equipped with whether determining UE is the function of reselecting object.
When e nodes B 11, which receives MME, reselects command signal, according to the identifier set in the signal, e sections The selection customization MME 22 of point B 11, and attached request (2) is forwarded to customization MME 22.Because customizing MME 22 to need to attach NAS (Non-Access Stratum) parameter (being used in the certification between UE and MME) of request, so to transmit this again attached by e nodes B 11 Even ask.E nodes B 11 needs the function of being equipped with the such NAS message of storage.
Because new MME (=customization MME 22) can not determine old MME (=general MME), new MME can not Take over the context of (take over) from old MME (=general MME).Therefore, new MME (=customization MME：MME 22) It also needs to execute certification and obtains subscriber profiles.
After receiving attached request signal, customization MME 22 obtains end message via identity request/response.This Outside, customization MME 22 and HSS 31 coordinates to execute certification and obtain subscriber profiles.That is, customization MME 32 execute with by general The identical processing of processing performed by MME 21.
After obtaining end message and subscriber profiles, the customization determinations of MME 22 are that UE 1 is connected to general MME 21 also It is attached to customization MME 22.
In this case, because customization MME 22 has been selected later by reselecting for e nodes B 11, institute Continue normally to attach process to customize MME 22 and reselect command signal without transmission MME.That is, following sequence is held Row：
From customization MME 22 to HSS 31 more new position request (8) transmission,
From HSS 31 to customization MME 22 update position response (11) transmission,
From customization MME 22 to S-GW 41 establishment session request (12) transmission,
The transmission of 51 establishment session request (13) from S-GW 41 to P-GW,
IP-CAN session establishments/the modification (14) initiated by the PCEF of P-GW 51,
The transmission of 41 establishment session request (15) from P-GW 51 to S-GW,
The transmission (if not switching (HO)) of 41 the first down link data from P-GW 51 to S-GW,
From S-GW 41 to customization MME 22 establishment conversational response (16) transmission,
The transmission of receiving (17) is asked/attached from the initial context setting of customization MME 22 to e nodes B 11,
The transmission of (18) is reconfigured from the RRC connections of e nodes B 11 to UE 1,
From UE 11 to e, the RRC connections of node B 11 reconfigure the transmission of completion (19),
The transmission of (20) is responded from e nodes B 11 to the initial context setting of customization MME 22,
The direct transmission (21) of node B from UE 1 to e,
From e nodes B 11 to customization MME 22 attached completion (22) transmission,
The transmission of the first uplink data of 41 and P-GW 51 from UE 1 to S-GW,
The transmission of (23) is asked from the modification carrying of customization MME 22 to S-GW 41,
The transmission of modification carrying request (23a) from S-GW 41 to PDN,
The transmission of 41 modification carrying response (23b) from PDN to S-GW,
From S-GW 41 to the transmission of the modification carrying response (24) of customization MME 22, and
From the transmission of the first down link data of P-GW 51 and S-GW 41 to UE 1.
In addition, general MME 21 and customization MME 22 are equipped with and determine which MME needs the function of being connected to UE 1.It should Determination is carried out based on the information transmitted from UE 1.The information can be：
- IMSE (International Mobile Subscriber identity),
- IMEI (International Mobile Equipment Identity)：(terminal identity)),
- UE network capabilities,
- MS network capabilities,
Movement station classification designator (classmark) 2,
Movement station classification designator 3,
Device attribute,
By the new parameter of the attached request signal added in future, or
The identifier of a part for these parameters is (for example, the PLMN (public-land mobile network)-for including in IMSI id)。
Alternatively, above-mentioned determination can be carried out based on the information transmitted from HSS 31.Information can be：
Feature list,
- APN (access point name),
By the new parameter of the update position response/insertion subscriber data request signal added in future, or
The identifier of a part for these parameters.
Any one of information of these projects or combination can be used for above-mentioned determination.
In addition, in this example, even if when attached from requiring connect to the UE 1 of general MME 21 to customization MME 22 and forwarding Even request signal, customization MME 22 also can ask e nodes B 11 to select general MME 21 in a similar way.For example, if UE 1 is normal mobile station (for example, normal mobile station incompatible with the special service of such as MTC or MBMS) and if UE 1 is firstly connected to customization MME 22, then general MME 21 is selected and provided service from general MME 21.
As described above, in the present example embodiment, MME instruction e nodes B executes reselecting for MME.In response to referring to It enables, e nodes B executes reselecting and continuing attached process for MME.In this way, UE can be attached to appropriate MME。
<Example 2>
As example 2, another example of EPC (block core of evolution) will be described with.In this illustration, UE is transmitted Attached request and UE are connected to customization MME.In example 2, system identical with the system configuration in example 1 will be used to match It sets.
Fig. 4 is the sequence chart for illustrating the operation according to example 2.Fig. 4 is based on Fig. 5 .3.2.1-1 in 3GPP TS23.401： Attached process, and sequence number is according to the figure.The details of each sequence is described in 3GPP TS23.401 5.3.2.? Hereinafter, the operation will be described with reference to figure 1 and Fig. 4.
When UE 1 transmits attached request (1), e nodes B 11 receives attached request (1).Next, e nodes B 11 will be attached Even request (2) is relayed to MME.At the sequence, it is to ask (2) to be forwarded to one by attached that e nodes B 11, which can not be uniquely determined, As MME 21 be still forwarded to customization MME 22.Accordingly, there exist e nodes B 11 to be forwarded to general MME 21 by attached request (2) The case where.
After receiving attached request (2), general MME 21 obtains end message via identity request/response (5b) (ME identity).In addition, in phase with HSS 31, general MME 21 executes certification and obtains subscriber profiles.That is, in such case Under, at least general MME 21 executes certification and obtains subscriber profiles.
After getting end message and subscriber profiles, the determinations of general MME 21 are that UE 1 is connected to general MME 21 Also it is attached to customization MME 22.If general MME 21 determines that UE 1 needs to be connected to general MME 21, general MME 21 continue normally attached process.
If general MME 21 determines that the needs of UE 1 are connected to customization MME 22, for the change of command M ME, generally MME is changed request signal (MME changes request) (GTP (GPRS Tunnel Protocol) signal newly introduced in this example) by MME 21 It is transferred to customization MME 22.
In this sequence, general MME 21 is set by terminal in MME changes request signal (MME changes request) The contextual information that certification and the acquisition of subscriber profiles are generated.
Customization MME 22 is maintained at MME change requests and believes when receiving MME changes request signal (MME changes request) The contextual information set is set in number and MME is changed into response signal (the GTP signals newly introduced in this example) is transferred to General MME 21.
Then, more new position request (8) is transferred to HSS 31 to notify the change of MME to HSS 31 by customization MME 22.
For the MME changed to the notices of HSS 31, customization MME 32 transmits more new position request.Subsequently attached process is by fixed MME 22 processed is executed.
It is effective in the Security Context Information received from general MME 21, customization MME 22 can be omitted Execute reauthentication (re-authentication).
Then, customization MME 22 continues attached process, and e nodes B 11 receives initial context from customization MME 22 and sets Set request/attached receiving) (17).
Initial context setting request/attached receive (17) are the attached requests (2) to being received by general MME 21 Response.E nodes B 11 needs to include the function from response is received different from another MME of general MME 21.
Then, customization MME 22 continues normally to attach process.
General MME 21 and customization MME 22, which is equipped with, determines which MME needs the function of being connected to UE 1, such as example 1 The case where.
In addition, in this example, even if attached from needing the UE 1 for being connected to general MME 21 to forward to customization MME 22 Even when request signal, customization MME 22 can ask general MME 21 for the change of MME in a similar way.For example, In the case that UE 1 is normal mobile station (for example, normal mobile station incompatible with the special service of such as MTC or MBMS), when When being connected to customization MME 22, MME is just changed request signal (MME changes request) and is transferred to UE 1 by customization MME 22 General MME 21.In this way, general MME 21 is selected, and service is provided from general MME 21.
As described above, in this example, general MME instructs customization MME about the change of MME.It is fixed in response to the instruction MME processed receives to change and continue attached process.In this way, UE can be attached to MME appropriate.
<Example 3>
As example 3, another example of EPC will be described with.In this illustration, the attached request of UE transmission, and UE It is connected to customization MME.In example 3, system configuration identical with the system configuration in example 1 will be used.
Fig. 5 and Fig. 6 is the sequence chart for illustrating the operation according to example 3.Fig. 5 and Fig. 6 is based on the figure in 3GPP TS23.401 5.3.2.1-1：Attached process, and sequence number is according to the figure.Each sequence described in 3GPP TS23.401 5.3.2 Details.Hereinafter, it will describe to operate with reference to figure 1, Fig. 5 and Fig. 6.
When UE 1 transmits attached request (1), first, e nodes B 11 receives attached request (1).Next, e nodes B Attached request (2) is forwarded to MME by 11.However, it is to ask (2) to be forwarded to one by attached that e nodes B 11, which can not be uniquely determined, As MME 21 be still forwarded to customization MME 22.Accordingly, there exist e nodes B 11 to be forwarded to general MME 21 by attached request (2) The case where.
After receiving attached request (2), general MME 21 obtains end message via identity request/response (5b) (ME identity).In addition, in phase with HSS 31, general MME 21 executes certification and obtains subscriber profiles.
For general MME 21 in the acquisition of end message and subscriber profiles, determination is that UE 1 is connected to general MME 21 also It is attached to customization MME 22.If UE 1 will be connected to general MME 21, general MME 21 continues normally to attach Journey.
If the needs of UE 1 are connected to customization MME 22, as the replacement for continuing attached process, general MME 21 will Attached refuse information is transferred to UE 1.That is, initial context setting request/attached refusal (17) is transferred to e by general MME 21 Node B 11.
In the sequence, the settings in attached refusal signal of general MME 21 re-attach (re-Attach) for instructing Parameter (the new parameter introduced in this example) and include GUMMEI (whole world unique MME identifiers) (whole world GUTI Unique temporary identity (identifier)) parameter (the new parameter introduced in this example) so that e nodes B 11 is again attached in execution Customization MME 22 can be selected when even.GUTI parameters are formed by GUMMEI and M-TMSI (Temporary Mobile Station identity).MMEI is by MCC (Mobile Country Code MCC), MNC (Mobile Network Code) and MME identifiers are formed.Although these parameters are newly to introduce in this example Parameter, but because e nodes B 11 be transparent, e nodes B 11 is unaffected.
When receiving attached refusal signal from e nodes B 11, as shown in Figure 6, UE 1 is according to for instructing attached The set parameter re-attached will wherein set GUTI's (attached by GUTI) in refusal signal and GUTI parameters Attached request (1) is transferred to e nodes B 11.E nodes B 11 determines MME appropriate according to the GUMMEI being included in GUTI, And attached request (2) is forwarded to customization MME 22.
UE 1 is equipped with the GUTI received in attached refusal signal and re-attaches (the attached request in Fig. 6 when transmitting (1)) function of the GUTI specified in attached refusal is used when.MME, which is equipped with, determines whether the UE reselects object Function.
Then, customization MME 22 continues normally to attach process.Although setting GUTI in attached request, customize MME 22 does not keep contextual information.
Therefore, when receiving attached request signal, customization MME 22 obtains terminal via identity request/response (4) Information.In addition, customization MME 22 and HSS 31 executes certification and obtains subscriber profiles in phase.
In addition, general MME 21 and customization MME 22 are equipped with and determine which MME needs the function of being connected to UE 1, Such as the case where example 1.
In addition, in this example, in addition it is attached from needing the UE 1 for being connected to general MME 21 to forward to customization MME 22 Even request signal, customization MME 22 can also promote UE 1 to reselect MME in an identical manner.That is, being normal in UE 1 In the case of movement station (for example, normal mobile station incompatible with the special service of such as MTC or MBMS), once when 1 quilts of UE When being connected to customization MME 22, MME 22 is just by attached refusal signal transmission to UE 1 for customization, and UE 1 is promoted to reselect General MME 21.In this way, because the transmission of UE 1 re-attaches request signal, general MME 21 is selected, and from General MME 21 provides service.
As described above, in this example, general MME instructions UE executes reselecting for MME.In response to the instruction, UE refers to MME is customized, and continues attached process.In this way, UE can be attached to MME appropriate.
<Example 4>
As example 4, another example of EPC will be described with.In this illustration, the attached request of UE transmission, and UE It is connected to customization MME.In example 4, system configuration identical with the system configuration in example 1 will be used.Fig. 7 is diagram root According to the sequence chart of the operation of example 4.Fig. 7 is based on Fig. 5 .3.2.1-1 in 3GPP TS23.401：Attached process, and sequence is compiled Number according to the figure.The details of each sequence is described in 3GPP TS23.401 5.3.2.It hereinafter, will be with reference to figure 1 and figure 7 describe to operate.
In order to ask (1) to be transferred to MME by attached, UE 1 establishes RRC with e nodes B 11 first and connect.In order to establish RRC Connection, first, UE 1 is by RRC connection request signal transmission to e nodes B 11.
In this sequence, the settings of UE 1 instruction UE 1 needs the parameter (user identity, the foundation that are connected to customization MME 22 The mark of the new value or a part for new parameter (value or parameter that newly introduce in this example) or such parameter of reason It accords with (for example, the PLMN-id for including in IMSI)).
The new parameter (establishing the new value of reason or new parameter) of RRC connection request is implemented so that UE 1 can Notify UE 1 that can be connected to customization MME to e nodes B 11 by using RRC connection request.
For e nodes B 11 when receiving RRC connection request signal, the storage instruction needs of UE 1 are connected to customization MME 22 Information, and continue follow-up RRC connection procedures.
After establishing rrc connection, when UE 1 transmits attached request (1), e nodes B 11 receives attached request (1).? In the sequence, attached request (2) is forwarded to by e nodes B 11 since the information stored when receiving RRC connection request (1) Customize MME 22.
After receiving attached request (2), customization MME22 continues normally attached process.
In addition, UE 1 assemble oriented e nodes B 11 instruct general MME 21 and customization which of MME 22 need by It is connected to the function of UE 1.Because UE can not store the information about all MME in core network, instruction MME types, The information of service type etc. is used to give the instruction of e nodes B 11, instead of the identifier that can select unique MME by it.
In addition, e nodes B 11, which is equipped with, determines which MME needs the function of being connected to UE 1.
As described above, user identity in RRC connection request message, the new value for establishing reason or new parameter and this One in the identifier of a part for the parameter of sample or combination are for passing through selections of the e nodes B 11 to MME.
As described above, in this example, UE instructs e nodes B to select MME.In response to the instruction, the specified customizations of e nodes B MME, and continue attached process.In this way, UE can be attached to MME appropriate.
<Example 5>
As example 5, another example of EPC will be described with.In this illustration, when executing tracking area update, UE and customization MME are connected.In example 5, system configuration identical with the system configuration in example 1 will be used.
Fig. 8 and Fig. 9 is the sequence chart for illustrating the operation according to example 5.Fig. 8 is based on the figure in 3GPP TS23.401 5.3.5-1：(see the 3GPP TS23.401 5.3.5) of S1Release Peocedure (S1 release procedures).Fig. 9 is based on figure 5.3.3.1-1：(service GW changes Tracking Area Update procedure with Serving GW change Tracking area update program) (see 3GPP TS23.401 5.3.3).It will be (and one in Fig. 3 with reference to figure 1, Fig. 8 and Fig. 9 Point) operation described.
When UE 1 transmits attached request (see 1 in Fig. 3), first, e nodes B 11 receives attached request.E nodes B 11 Attached request is relayed to MME (see 2 in Fig. 3).
E nodes B 11, which can not be uniquely determined, to be forwarded to general MME 21 by attached request or is forwarded to customization MME 22.The case where attached request is forwarded to general MME 21 accordingly, there exist e nodes B 11.
When receiving attached request, general MME 21 via identity request/response (see in Fig. 34,5b) obtain end Client information (ME identity).In addition, general MME 21 and HSS 31 executes certification and obtains subscriber profiles in phase.
For general MME 21 in the acquisition of end message and subscriber profiles, determination is that UE 1 is connected to general MME 21 also It is attached to customization MME 22.Then, continue normally attached process.If UE1 will be connected to general MME 21, handle It completes at this moment.
If UE 1 needs be connected to customization MME 22, general MME 21 execute S1 release so that UE 1 execute with Track area update (TA updates), as shown in Figure 8.S1 UE contexts release commands (4) are transferred to e nodes B by general MME 21 11。
General MME 21 is come by using the MME identifiers (for example, GUMMEI) in S1 UE contexts release commands (4) It provides about e nodes B in the instruction for establishing the MME for needing selection when S1 is connect with MME next time.For example, specifying for bearing The S1 releases of the activation of lotus balance TAU, which are performed, to be new by the parameter of the GUMMEI of next MME of e nodes B selections Parameter.Even after S1 releases are completed, although e nodes B11 is keeping the session information for UE 1, e nodes B 11 continue the information for keeping MME identifiers as the selection for next MME.
After S1 releases are performed, next, UE 1 transmits TAU requests (2), as illustrated in Fig. 9.First, e is saved Point B 11 receives TAU requests (2) from UE 1 and TAU requests (3) is forwarded to MME.Such as in the state that S1 discharges completion, e Node B 11 executes reselecting and establishing S1 connections for MME.E nodes B 11 according to by old MME (=general MME) in S1 When release indicated GUMMEI come select customization MME.E nodes B 11 is equipped with the work(for keeping next GUMMEI per UE Energy.
When selecting MME, e nodes B 11 believes according in the S1 UE context release commands received from general MME 21 The MME identifiers of indicated GUMMEI select customization MME 22 in number.Because GUTI (GUMMEI) instructions on NAS are old MME (=general MME), so m context can be obtained.
After receiving TAU requests (3), customization MME22 continues normal TA renewal processes.Customizing MME 22 will be upper and lower Text request (4) is transferred to general MME 21 and receives context response (5).
In the case where repositioning S-GW, customization MME 22 will include that the context of instruction for changing S-GW confirms (7) it is transferred to general MME.When customization MME 22 selects new S-GW 41 (new service GW), customization MME 22 will create meeting Words request (8) is transferred to new S-GW 41.
New S-GW 41 (new service GW) will change carrying request (9) transmission in response to the establishment session request (8) To P-GW 51.After receiving the response for carrying request (9) to modification from P-GW 51, new S-GW will create conversational response (11) customization MME 22 is returned to.
Customization MME 22 will update position (12) and be transferred to HSS 31.
General MME 21 deletes MM contexts when receiving canceling position (13) from HSS 31, and by canceling position Confirm that (14) are transferred to HSS 31.HSS 31 will update location confirmation (17) in response to update position (12) and be transferred to customization MME 22。
General MME 21 will delete session request (18) and be transferred to old S-GW 41 (old service GW), and old S- GW 41 (old service GW) will be transferred to general MME 21 to the response (19) for deleting session request (18).
TAU receiving (20) is transferred to UE 01 by customization MME 22.
Receive in (20) if GUTI is included in TAU, TAU is completed (21) back to customization MME 22 by UE 1.UE This TAU is completed (21) by 1 to be used as receiving received signal TAU the confirmation of (20).
General MME 21 and customization MME 22, which is equipped with, determines which MME needs the function of being connected to UE 1.This Function is identical as the function in example 1.
In this example, in the same manner as described above, when e nodes B 11 is from the UE for needing to be connected to general MME 21 1 from normal mobile station (the incompatible normal mobile station with the special service of such as MTC or MBMS) (for example, receive TA updates When request, service is provided by selecting general MME, UE 1 to be connected to general MME 21, and from general MME 21.
In this example, the sequence having been based in Fig. 9 performs TA renewal processes.However, being characterized in e in this example Node B 11 selects MME.Therefore, this example can also be by for example (such as servicing for re-establishing other processes of S1 connections Request) it realizes.
As described above, according to this example, general MME instruction e nodes B executes reselecting for MME.In response to the instruction, e Node B specifies customization MME when selecting next MME, and continues the process.In this manner, UE be connectable to it is appropriate MME。
<Exemplary embodiment 2>
As exemplary embodiment 2, the configuration of UMTS (Universal Mobile Telecommunications System) will be described with.In this configuration In, the attached request of UE transmission, and UE is connected to customization SGSN.The system that Fig. 2 illustrates accoding to exemplary embodiment 2 is matched It sets.
UE 101 is the terminal that service is received from customization SGSN.For example, UE 101 can be that above-mentioned MTC device or MBMS are simultaneous Hold terminal.UE 101 be such as mobile telephone terminal or smart phone using normal service normal mobile station (with such as The incompatible terminal of the special services of MTC or MBMS) in the case of, UE 101 is connected to general SGSN.In addition, as below By description, when in response to coming from normal mobile station (for example, from the end incompatible with the special services of such as MTC or MBMS End) attached request and select customization SGSN when, execute reselecting for SGSN.As a result, UE 1 is connected to general SGSN.
Node B 111 and RNC (radio network controller) 171 is for being wirelessly electrically accessed suitable for UMTS system Equipment.
General SGSN 121 and customization SGSN 122 are each overlay areas and use in umts Equipment.According to connection mode, general SGSN 121 and customization SGSN 122 handle user plane.If it is flat that SGSN does not handle user Face then sets user plane between S-GW and RNC.
HLR (home location register) 131 is the database for storing subscriber information.
(gateway GPRS (general packet radio service) supporting nodes of GGSN 141：It is described as " net in the claims Close GPRS Support Node ") it is attached to the gateway device of external network.Service network 161 is external network (Data packet network Network).
In fig. 2, node B 111 and RNC 171 is the equipment in radio access network RAN.SGSN, GGSN etc. are core Equipment in heart net.
Next, exemplary embodiment 2 will be described based on several examples.The different controlling party described in each example Method.Following example 6 corresponds respectively to above-mentioned pattern 6 to 10 to 10.
<Example 6>
Figure 10 is to illustrate the sequence chart according to the operation of example 6 and be based on 3GPP TS 23.0606.5 Figure 22.
In Fig. 10,
" MS (movement station) " corresponds to the UE 101 in Fig. 2,
" RAN (Radio Access Network) " corresponds to NodeB 111 and RNC 171 in Fig. 2,
" general MME " corresponds to the general SGSN 121 in Fig. 2,
" customization SGSN " corresponds to the customization SGSN 122 in Fig. 2,
" GGSN " corresponds to the GGSN 141 in Fig. 2, and
" HLR " corresponds to the HLR 131 in Fig. 2.
The VLR/VLR (Visitor Location Register) of MSC (mobile switching centre) is the position for CS services in addition to HLR Set register.EIR (device identifier register) stores the identifier of effective mobile device.
It will describe to operate with reference to figure 2 and Figure 10.Hereinafter, the UE 101 in Fig. 2 will act as the MS in Figure 10.
When UE 101 (MS) transmits attached request (1), first, node B 111 receives attached request (1), and will be attached Even request (1) is forwarded to RNC 171.Attached request (1) is forwarded to SGSN by RNC 171.However, RNC 171 can not be uniquely Determination is that attached request is forwarded to general SGSN 121 or is forwarded to customization SGSN 122.Accordingly, there exist RNC 171 will be attached The case where even request is forwarded to general SGSN 121.
After receiving attached request, general SGSN 121 believes via identity request/response (3,4) to obtain terminal Breath.In addition, general SGSN 121 and HLR 131 executes certification and obtains subscriber profiles in phase.That is, in this case, General SGSN 121 executes certification and obtains subscriber profiles.
For general SGSN 121 in the acquisition of end message and subscriber profiles, determination is that UE101 is connected to general SGSN 121 are also attached to customization SGSN 122.In the case where UE 101 needs to be connected to general SGSN 121, general SGSN 121 continue normally attached process.
In the case where the needs of UE 101 are connected to 122 SGSN of customization, to instruct reselecting for SGSN, generally SGSN is reselected order (the RANAP signals newly introduced in this example) and is transferred to RNC 171 by SGSN 121.In the sequence In, general SGSN 121 reselects command signal (for example, RAI (Tracking Area Identifier symbol) or NRI (Internet resources in SGSN Identifier)) in setting identification customization SGSN 122 identifier.That is, general SGSN 121 to RNC 171 transmit including with Request is reselected in the SGSN of the necessary information (RAI) of selection customization SGSN 122.It is reselected being executed in single pond In the case of, it can only use NRI.SGSN is equipped with whether determining UE 101 is the function of reselecting object.
When RNC 171, which receives SGSN, reselects command signal, the identifier set by the signal, The selections of RNC 171 customization SGSN 122 and the attached request (1) of forwarding.Because customizing the NAS that SGSN 122 needs attached request (Non-Access Stratum) parameter, so the attached request of the transmission of RNC 171.RNC 171 is equipped with the function of the such NAS message of storage.
Because new SGSN (=customization SGSN) can not determine old SGSN (=general SGSN), new SGSN can not Take over context.Therefore, new SGSN is also needed to execute certification and is obtained subscriber profiles.Receive attached request (2) it Afterwards, customization SGSN 122 obtains end message via identity request/response.In addition, customization SGSN 122 and HLR 131 coordinates Ground executes certification and obtains subscriber profiles.That is, customization SGSN 122 execute with by identical performed by general SGSN 121 Processing.
SGSN 122 is customized in the acquisition of end message and subscriber profiles, determination is that UE 101 is connected to general SGSN 121 are also attached to customization SGSN (022).In this case, because being had been selected after being reselected by RNC 171 Customization SGSN 122, so customization SGSN 122 continues normally attach process, reselecting order without transmission SGSN believes Number.
In addition, general SGSN 121 and customization SGSN 122 are equipped with and determine which SGSN needs to be connected to UE 101 Function.The determination is carried out based on the information transmitted from UE 101.The information can be：
- IMSE (International Mobile Subscriber identity),
- IMEI,
- UE network capabilities,
- MS network capabilities,
Movement station classification designator 2,
Movement station classification designator 3,
Device attribute,
By the new parameter of the attached request signal added in future, or
The identifier (for example, the PLMN-id for including in IMSI) of a part for these parameters.
Alternatively, above-mentioned determination can be carried out based on the information transmitted from HLR 131.The information can be：
Feature list,
- APN,
By the new parameter of the update position response/insertion subscriber data request signal added in future, or
The identifier of a part for these parameters.
Any one of information of these projects or combination can be used for above-mentioned determination.
In addition, in this example, even if from needing to be connected to the UE 101 of general SGSN 121 to customization SGSN 122 When forwarding attaches request signal, customization SGSN 122 can ask RNC 171 to execute reselecting for SGSN in the same way. If UE 101 be normal mobile station (for example, normal mobile station incompatible with the special service of such as MTC or MBMS) and If UE 101 is firstly connected to customization, SGSN 122, general MME 121 ask the choosing again of the execution of RNC 171 SGSN It selects.As a result, general SGSN 121 is selected, and service is provided from general SGSN 121.
As described above, in this example, SGSN instructions RNC executes reselecting for SGSN.In response to the instruction, RNC is held Row SGSN's reselects, and continues attached process.In this way, UE can be attached to SGSN appropriate.
<Example 7>
As example 7, another example of UMTS will be described with.In this illustration, the attached request of UE transmission, and UE It is connected to customization SGSN.In example 7, system configuration identical with the system configuration in example 6 will be used.Figure 11 is diagram According to the sequence chart of the operation of example 7.Hereinafter, it will describe to operate with reference to figure 2 and Figure 11.
When UE 101 transmits attached request (1), first, node B 111 receives attached request (1).Next, node B Attached request is forwarded to RNC 171 by 111, and attached request is forwarded to SGSN by RNC 171.However, RNC 171 can not be only The determination of one ground is that attached request is forwarded to general SGSN 121 or is forwarded to customization SGSN 122.Accordingly, there exist RNC 171 The case where attached request is forwarded to general SGSN 121.
General SGSN 121 obtains end message when receiving attached request via identity request/response.In addition, Coordinate with HLR 131, general SGSN 121 executes certification and obtains subscriber profiles.That is, in this case, at least generally SGSN 121 executes certification and obtains subscriber profiles.
For general SGSN 121 in the acquisition of end message and subscriber profiles, determination is that UE 101 is connected to general SGSN 121 are also attached to customization SGSN 122.If general SGSN 121 determines that UE 101 needs to be connected to general SGSN 121 When, then general SGSN 121 continues normally to attach process.
In the case where the needs of UE 101 are connected to 122 SGSN of customization, in order to instruct the change of SGSN, general SGSN SGSN is changed request (the GTP signals newly introduced in the present example embodiment) by 121 is transferred to customization SGSN 122.
In the sequence, the settings in SGSN changes request signal of general SGSN 121 are simple by the certification of movement station and subscriber The contextual information that the acquisition of shelves is generated.That is, when general SGSN 121 is for change (SGSN changes) the request customization of SGSN When SGSN 122, general SGSN 121 notifies context to new SGSN (customization SGSN 122).SGSN, which is equipped with, determines the UE Whether 101 be the function of reselecting object.
Customization SGSN 122 is maintained at set in SGSN change request signals when receiving SGSN change request signals Contextual information, and by SGSN change response signal (the GTP signals newly introduced in the present example embodiment) be transferred to General SGSN 121.
Then, customization SGSN 122 will update position signal (8) and be transferred to HLR 131 with to the notices of HLR 131 SGSN Change.
When the Security Context Information transmitted from general SGSN 121 is effective, customization SGSN 122, which can be omitted, to be held Row reauthentication.
Then, customization SGSN 122 continues attached process, and RNC 171 is received to attach and received letter from customization SGSN 122 Number (9).Then, continue normally attached process.
General SGSN 121 and customization SGSN 122, which is equipped with, determines which SGSN needs the work(for being connected to UE 101 Can, such as the case where example 6.
In this example, even if it is attached from needing to be connected to the UE 101 of general SGSN 121 to customization SGSN 122 and forwarding Even when request signal, general SGSN 121 is asked in the change that customization SGSN 122 can be directed to SGSN in an identical manner.? In the case that UE 101 is normal mobile station (for example, terminal incompatible with the special service of such as MTC or MBMS), and such as Fruit UE 101 is connected to customization SGSN 122, then customizes SGSN 122 and select general SGSN 122, and from general SGSN 121 provide service.
As described above, in this example, general SGSN instructs the change of SGSN to customization SGSN.It is fixed in response to the instruction SGSN processed receives to change and continue attached process.In this way, UE can be attached to SGSN appropriate.
<Example 8>
As example 8, another example of UMTS will be described with.In this illustration, the attached request of UE transmission, and UE It is connected to customization SGSN.In example 8, the identical configuration with example 6 will be used.Figure 12 and Figure 13 is diagram according to example The sequence chart of 8 operation.Hereinafter, it will describe to operate with reference to figure 2, Figure 12 and Figure 13.
When UE 101 (MS) transmits attached request (1), first, node B 111 receives attached request (1).Next, section Attached request is forwarded to RNC 171 by point B 111, and attached request is forwarded to SGSN by RNC 171.However, 171 nothings of RNC Method, which is uniquely determined, to be forwarded to general SGSN 121 by attached request or is forwarded to customization SGSN 122.Accordingly, there exist RNC 171 by it is attached request be forwarded to general SGSN 121 the case where.
After receiving attached request (1), general SGSN 121 believes via identity request/response (3) to obtain terminal Breath.In addition, in phase with HLR 131, general SGSN 121 executes certification and obtains subscriber profiles.
For general SGSN 121 in the acquisition of end message and subscriber profiles, determination is that UE 101 is connected to general SGSN 121 are also attached to customization SGSN 122.In the case where UE 101 requires connect to general SGSN 121, general SGSN 121 Continue normally attached process.
In the case where the needs of UE 101 are connected to 122 SGSN of customization, as the replacement for continuing attached process, generally Attached refusal signal (9) is transferred to UE 101 by SGSN 121.
In this case, general SGSN 121 in attached refusal signal setting for instruct the parameter re-attached with RAI (Routing Area identity) parameter (parameter newly introduced in the present example embodiment) so that RNC 171 can executed again Selection customization SGSN 122 when attached.Although these parameters are the parameters newly introduced in this example, because RNC 171 is Transparent, so RNC 171 is unaffected.
UE 101 needs be equipped with via it is attached refusal come receive RAI and when transmission again again attach when use attaching The function of specified RAI in refusal.SGSN, which is equipped with, determines whether this UE 101 is the function of reselecting object.
UE 101 is when receiving attached refusal signal (9), according to set in attached refusal signal (9) for instructing The parameter re-attached and RAI parameters (passing through re-attaching for P-TMSI (grouping Temporary Mobile Subscriber identifier)) will wherein The attached request signal (1) for being set with RAI is transferred to RNC 171, as shown in Figure 13.It is appropriate that RNC 171 is determined according to RAI SGSN, and by it is attached request be forwarded to customization SGSN 122.
Then, customization SGSN 122 continues normally to attach process.
Although setting RAI in attached request, customization SGSN 122 does not keep contextual information.Therefore, it is receiving When to attached request signal (1), customization SGSN 122 obtains end message via identity request/response.In addition, customization SGSN 122 execute certification and obtain subscriber profiles in phase with HLR 131.
General SGSN 121 and customization SGSN 122, which is equipped with, determines which SGSN needs the work(for being connected to UE 101 Can, such as the case where example 6.
In this example, even if it is attached from needing to be connected to the UE 101 of general SGSN 121 to 122 turns of SGSN of customization Request signal is sent out, customization SGSN 122 also can ask UE 101 for reselecting for SGSN in the same way.If UE 101 is normal mobile station (for example, terminal incompatible with the special service of such as MTC or MBMS) and if UE 101 When being connected to customization SGSN 122, then SGSN 122 is customized by attached refusal signal transmission to UE 101 and asks UE 101 Select general SGSN 121.In this way, because the transmission of UE 101 re-attaches request (attached request) signal, generally SGSN 121 is selected, and provides service from general SGSN 121.
As described above, in this example, general SGSN instructions UE executes reselecting for SGSN.In response to the instruction, UE It is specified to customize SGSN and continue attached process.In this way, UE can be attached to SGSN appropriate.
<Example 9>
As example 9, another example of UMTS will be described with.In this illustration, the attached request of UE transmission and UE It is connected to customization SGSN.In example 6, identical system configuration will be used with example 6.Figure 14 is diagram according to example 9 Operation sequence chart.Hereinafter, it will describe to operate with reference to figure 2 and Figure 14.
In order to which attached request is transferred to SGSN, first, UE 101 establishes RRC with RNC 171 and connect.In order to establish RRC Connection, first, UE 101 is by RRC connection request signal transmission to RNC 171.
In this signal, the setting instructions of UE 101 UE 101 needs the parameter (user for being connected to customization SGSN 122 Identity, establish reason one of new value or new parameter (value or parameter that newly introduce in this example) or such parameter The identifier (for example, the PLMN-id for including in IMSI) divided).
When receiving RRC connection request signal, the storage instruction needs of UE 101 of RNC 171 are connected to customization SGSN 122 information and continue follow-up RRC connection procedures.
After establishing rrc connection, the attached request (1) of the transmission of UE 101 and the attached request (1) of the receptions of node B 111. Next, attached request is forwarded to RNC 171 by node B 111.
Attached request is forwarded to SGSN by RNC 171.It is deposited according to when RNC 171 has received RRC connection request signal Attached request signal is forwarded to customization SGSN 122 by the information of storage, RNC 171.
After receiving attached request signal, customization SGSN 122 continues normally to attach process.
Which of general SGSN 121 and customization SGSN 122 is instructed to need in addition, UE 101 is equipped with oriented RNC 171 Function to be attached to UE 101.UE 101 can not store the information about all SGSN in core network, so conduct It is capable of the replacement of selected identifier by its unique SGSN, the information of instruction SGSN types, service type etc. is for giving The instruction of RNC 171.
RNC 171, which is equipped with, determines which SGSN needs the function of being connected to UE 101.For this determination, as above It is described, using user identity, establish reason new value or new parameter (value or parameter that newly introduce in this example) and One in the identifier of a part for such parameter or combination.
As described above, in this example, UE 101 instructs RNC 171 to select SGSN.In response to the instruction, RNC 171 refers to It customizes SGSN and continues attached process.In this way, UE 101 can be attached to SGSN appropriate.
<Example 10>
As example 10, another example of UMTS will be described with.In this illustration, when RA update be performed UE and SGSN is customized to be connected.In example 10, the identical system configuration with example 6 will be used.Figure 15 and Figure 16 is diagram basis The sequence chart of the operation of example 10.Hereinafter, the part with reference to figure 2, Figure 15, Figure 16 and Figure 10 is described to operate.
When UE 101 transmits attached request (see 1 in Figure 10), first, node B 111 receives attached request.Node B Attached request is forwarded to RNC 171 by 111, and attached request is forwarded to SGSN by RNC 171.RNC 171 can not be unique Ground determination is that attached request is forwarded to general SGSN 121 or is forwarded to customization SGSN 12.Accordingly, there exist RNC 171 will The case where attached request is forwarded to general SGSN 121.
When receiving attached request, general SGSN 121 is obtained via identity request/response (see 3,5 in Figure 10) End message.In addition, general SGSN 121 and HLR 131 executes certification and obtains subscriber profiles in phase.
For general SGSN 121 in the acquisition of end message and subscriber profiles, determination is that UE 101 is connected to general SGSN 121 are also attached to customization SGSN 122.In the case where UE 101 requires connect to general SGSN 121, general SGSN 121 Continue normally attached process.
In the case where the needs of UE 101 are connected to 122 SGSN of customization, general SGSN 121 executes Iu and discharges (Iu Release) so that UE 101 executes RA (Routing Area) and updates, as shown in Figure 15.
Iu release command signals (4 in Figure 15) are transferred to RNC 171 by general SGSN 121.General SGSN 121 passes through Using the SGSN identifiers (for example, RAI or NRI) in Iu release command signals come provide about by RNC next time with SGSN Establish the instruction of the SGSN selected when Iu connections.In the case of signal pond, NRI can be used.
Even if after Iu releases are completed, although RNC 171 is keeping the session information for UE 101, RNC 171 continue the information for keeping SGSN identifiers as the selection for next SGSN.
After Iu releases are performed (after IU release completions (6) are transferred to general SGSN 121 by RNC 171), connect Get off, as illustrated in Figure 16, UE 101 transmits RAU requests (RA updates request) (2).
First, node B 111 receives RAU requests (2), and RAU requests (3) are forwarded to RNC 171 by node B 111.
Next, RAU requests are forwarded to SGSN by RNC 171.Because Iu releases (c) have been performed for, RNC 171 execute the selection of SGSN and establish Iu connections.
In the selection of SGSN, RNC 171 is according to the institute in the Iu release command signals received from general SGSN 121 Specified SGSN identifiers come select customization SGSN 122.RNC is held according to by old SGSN (=general SGSN) in Iu releases When row indicated RAI (or NRI) come select customization SGSN.RNC is equipped with the function of keeping next RAI per UE.
After receiving RAU requests, customization SGSN 122 continues normal RA renewal processes.Because of the P- on NAS TMSI (RAI) indicates the general SGSN as old SGSN, so customization SGSN 122 obtains context.
General SGSN 121 and customization SGSN 122, which is equipped with, determines which SGSN needs the work(for being connected to UE 101 Energy.This function is identical as the function in example 6.
In this example, in identical means described above, when RNC 17 is general from needing to be connected to The UE 101 of SGSN 21 is (for example, from normal mobile station (with the special service of such as MTC or MBMS incompatible normal movement Stand)) when receiving RA update requests, by selecting general SGSN, UE 101 to be connected to general SGSN 121 and from general SGSN 121 provides service.
In addition, in this example, RA renewal processes have been based on sequentially executed in Figure 16.However, in this example It is characterized in that RNC 171 selects SGSN.Therefore, this example can also by for example for re-establishing other programs of Iu connections it is (all Such as PDP context activation) it realizes.
As described above, according to this example, general SGSN instructions RCN executes reselecting for SGSN.In response to this Instruction, RNC specifies customization SGSN in the selection next time of SGSN, and continues other processes.In this way, UE can be by It is connected to SGSN appropriate.
Hereinafter, the difference by description among above-mentioned example.
<Mobile network>
Example 1-5 be, for example, based on LTE (long term evolution) (Radio Access Network be E-UTRAN (general land of evolution without Line access) and core network be EPC).Example 6-10 is, for example, that (Radio Access Network is based on 3G (third generation) UTRAN (universal terrestrial access network) and core network is GPSR).
<Embodiment method>
A) example 1 and 6：Attached process (being retried in RAN (Radio Access Network)))
B) example 2 and 7：Attached process (interconnection in core network (CN))
C) example 3 and 7：It is retried by terminal
B) example 4 and 8：Selection in core network (CN)
E) example 5 and 10：The update (RAU/TAU) in location management region
<The range (element to be modified is needed for embodiment) of influence>
A) example 1 and 6：RAN (Radio Access Network) and CN (core network)
B) example 2 and 7：CN(RAN)
C) example 3 and 8：Terminal and CN
D) example 4 and 9：Terminal and RAN
E) example 5 and 10：RAN and CN
<The advantageous effects etc. provided by embodiment>
A) example 1 and 6：Although no function needs to be added to terminal, function needs to be added to RAN.
B) example 2 and 7：There is no function to need to be added to terminal, and in some cases, no function needs are added It is added to RAN.In addition, among example, minimum semaphore is requirement.
C) example 3 and 8：There is no function to need to be added to RAN, and function can be easily added terminal and CN.However, attached refusal needs the time.
D) example 4 and 9：Although no function needs to be added to CN, needs more multi-functional than other examples are added It is added to RAN.In addition, RAN needs to store and manage the CN lists for selecting CN.Before accessing HLR/HSS, for selecting CN Information be limited.
E) example 5 and 10：There is no function to need to be added to terminal.CN's reselects in the change by contraction etc. It is possible after attached.
<The wherein selected situation of core network node>
Hereinafter, description wherein core network node is based on the above exemplary embodiments and example is selected several Situation.
MTC (machine-type communication) equipment (M2M equipment) is connected to customization CN nodes (for the section of MTC device optimization Point).
Customization CN nodes are connected to using the user of MBMS (MBMS is compatible with CN nodes).
In another case, service is only provided by customizing CN nodes so that new service is activated on small-scale.
<The case where using LTE>
Particular UE is connected to the node of wherein MME and SGW arrangements.Although not particularly restricted, for example, in the presence of wherein The case where low volume data business is sent to UE via SMS (short message service).In this case, if MME and SGW cloth It sets, then can more easily realize the embodiment of SMS conversion process.
In addition, depending on terminal type (for example, CSFB (CS fallings) terminals and VoLTE terminals), MME is exchanged.Work as CS (circuit switching) service during LTE connections by CSFB when transmission or reception (CS fallings) be by radio switch to 3G (or Function 2G).VoLTE (LTE voices) is the function of providing voice (it is provided via CS) on LTE and service. CSFB terminals need and MSC intercommunications.VoLTE terminals need and IMS (IP multimedia subsystem) intercommunication.When CSFB is performed, The MSC (mobile switching centre) attached in advance is caused the MME of choice arrangement.
The disclosure of above patent document is incorporated herein by being quoted to it.It exemplary embodiment and exemplary repaiies Changing and adjusting in the range of generic disclosure content (including claim) of the present invention is possible and is based on the present invention Basic fundamental design.Various disclosed elements (including element in each in claim, example, attached drawing etc.) Various combinations and selection are possible in the scope of the claims of the present invention.That is, the present invention includes can certainly The various change made according to the generic disclosure content including claim and technical concept by those skilled in the art and Modification.
The above exemplary embodiments and it is exemplary can at least partly be described following complementary annotations, but not limited to this.
(complementary annotations 1)
A kind of includes the communication system of the core network for mobile communication system, wherein the core network includes more A node, each node are used as the ambulant node of management terminal, and the multiple node provides terminal about the node Service function and it is different from each other, and
Wherein, it is based on subscriber information and end message, according to the service characteristic or terminal utilized by the terminal Type selects the node to be attached to the terminal in the multiple node, and the terminal be connected to it is selected The node selected.
(complementary annotations 2)
According to the communication system described in complementary annotations 1, wherein received from the attached of the terminal via base station apparatus When even asking, mobility management entity is reselected request signal and is transferred to the base station by first movement management entity node Device, in order to which the terminal is connected to the second mobility management entity node, the second mobility management entity node The service different from the service provided by the first movement management entity node is provided, and
Wherein, attached request is transferred to the second mobility management entity node by the base station apparatus, will be described Terminal is connected to the second mobility management entity node.
(complementary annotations 3)
According to the communication system described in complementary annotations 1, wherein receiving attached ask from the terminal via base station apparatus When asking, mobility management entity change request signal is transferred to the second mobile management reality by first movement management entity node Body node, in order to which the terminal is connected to the second mobility management entity node, second mobile management is real Body node provides the service different from the service provided by the first movement management entity node, and
Wherein, the second mobility management entity node continuing with the attached request attached process, by institute It states terminal and is connected to the second mobility management entity node.
(complementary annotations 4)
According to the communication system described in complementary annotations 1, wherein receiving attached ask from the terminal via base station apparatus When asking, first movement management entity node is added to the mark of the second mobility management entity node to the terminal transmission The attached refusal of symbol, in order to which the terminal is connected to the second mobility management entity node, the mobile management Entity node provides the service different from the service provided by the first movement management entity node, and
Wherein, the identifier of the second mobility management entity node is added to attached request by the terminal, and Again the attached request is transmitted to be connected to the second mobility management entity node.
(complementary annotations 5)
According to the communication system described in complementary annotations 1, wherein the terminal transmits RRC connection request to base station apparatus, right The RRC connection request is added to connectivity request message of the request to the second mobility management entity node, second movement Property management entity node the service different from the service provided by first movement management entity node is provided, and
Wherein, have from foundation to mobility pipe in the transmission for receiving the RRC connection request when the base station apparatus When the attached request that the terminal of the RRC connections of reason entity receives, the base station apparatus selects the second mobility pipe Entity node is managed so that the terminal is connected to the second mobility management entity node.
(complementary annotations 6)
According to the communication system described in complementary annotations 1, wherein when the first movement pipe for establishing the session for having the terminal It is described when reason entity node discharges the connection established between the base station apparatus and the first movement management entity node Base station apparatus is in the mobility management entity carried out by the base station apparatus described in first movement management entity node instruction Select the second mobility management entity node select next time in, the second mobility management entity node provide with by described What first movement management entity node was provided services different services, and
Wherein, when the request of location management area update is transferred to the base station apparatus by the terminal, the base Station arrangement selects the second mobility management entity node the terminal is connected to second mobility management entity Node.
(complementary annotations 7)
According to the communication system described in complementary annotations 1, wherein first service GPRS (General Packet Radio Service) is supported Node is when receiving the attached request from the terminal via radio network controller, by Serving GPRS Support Node weight New selection request signal is transferred to the radio network controller, in order to which the terminal is connected to second service GPRS branch It serves as a diplomatic envoy a little, the second service GPRS Support Node is provided with the service that is provided by the first service GPRS Support Node not Same service, and
Wherein, attached request is re-transmitted to the second service GPRS branch and served as a diplomatic envoy by the radio network controller The terminal is connected to the second service GPRS Support Node by point.
(complementary annotations 8)
According to the communication system described in complementary annotations 1, wherein first service GPRS (General Packet Radio Service) is supported Node (SGSN) from the terminal via no network of wires controller when receiving attached request, by Serving GPRS Support Node Change request signal and be transferred to second service GPRS Support Node, in order to which the terminal is connected to the second service GPRS Supporting node, the service that the second service GPRS Support Node is provided and provided by the first service GPRS Support Node Different services, and
Wherein, second GPRS Support Node continuing with the attached request attached process, by the terminal It is connected to the second service GPRS Support Node.
(complementary annotations 9)
According to the communication system described in complementary annotations 1, wherein first service GPRS (general packet radio service) Zhi Chijie Point (SGSN) is attached to the terminal transmission when receiving the attached request from the terminal via radio network controller Refusal, the second service GPRS Support Node is connected to by the terminal, and second service is added to the attached refusal The identifier of GPRS Support Node, the second service GPRS Support Node provide and by the first service GPRS Support Nodes What is provided services different services, and
Wherein, the identifier of the second service GPRS Support Node is added to attached request by the terminal, and again The attached request is newly transmitted to be connected to the second service GPRS Support Node.
(complementary annotations 10)
According to the communication system described in complementary annotations 1, wherein the terminal asks RRC (radio resource control) connections It asks and is transferred to radio network controller, company of the request to second service GPRS Support Node is added to the RRC connection request The connectivity request message connect, the second service GPRS Support Node provide and by first service GPRS (general packet radios Service) the different service of service that is provided of supporting node, and
Wherein, have to clothes when the radio network controller transmits foundation when receiving the RRC connection request Be engaged in GPRS Support Node RRC connections the terminal attached request when, the radio network controller selects described the Two Serving GPRS Support Nodes by the terminal to be connected to second GPRS Support Node.
(complementary annotations 11)
According to the communication system described in complementary annotations 1, wherein when foundation has the first service with the session of the terminal The release of GPRS (General Packet Radio Service) supporting node is propped up in the first service GPRS (General Packet Radio Service) Serve as a diplomatic envoy the connection a little established between the radio network controller when, described in first service GPRS Support Node instruction Radio network controller selects in the selection next time of the Serving GPRS Support Node carried out by the radio network controller Second service GPRS Support Node, the second service GPRS Support Node provide and by the first service GPRS Support Nodes What is provided services different services, and
Wherein, when the request of location management area update is transferred to the radio network controller by the terminal, The radio network controller selects the second service GPRS Support Node so that the terminal is connected to second clothes Business GPRS Support Node.
(complementary annotations 12)
A kind of communication means, including：
By for multiple inserting knots of the terminal, in mobile communication system core network, the node is used as management The ambulant node of terminal, and it is different from each other to the service function that terminal is provided about the node；
Based on subscriber information and end message, according to the characteristic or the terminal serviced used in the terminal Type selects the node to be attached to terminal in the multiple node；And
The terminal is connected to selected node.
(complementary annotations 13)
According to the communication means described in complementary annotations 12, including：
First movement management entity node, will when receiving the attached request from the terminal via base station apparatus Mobility management entity reselects request signal and is transferred to the base station apparatus, in order to which the terminal is connected to the second shifting Mobility management entity node, the second mobility management entity node provide and by the first movement management entity nodes What is provided services different services；And
Attached request is transferred to the second mobility management entity node by the base station apparatus, and the terminal is connected It is connected to the second mobility management entity node.
(complementary annotations 14)
According to the communication means described in complementary annotations 12, including：
First movement management entity node, will when receiving the attached request from the terminal via base station apparatus Mobility management entity changes request signal and is transferred to the second mobility management entity node, in order to which the terminal to be connected to The second mobility management entity node, the second mobility management entity node provide and by the first movement pipes What reason entity node was provided services different services；And
The second mobility management entity node continuing with the attached request attached process, by the terminal It is connected to the second mobility management entity node.
(complementary annotations 15)
According to the communication means described in complementary annotations 12, including：
First movement management entity node when receiving the attached request from the terminal via base station apparatus, to The terminal transmission is added to the attached refusal of the identifier of the second mobility management entity node, in order to by the terminal It is connected to the second mobility management entity node, the second mobility management entity node offer is moved with by described first What mobility management entity node was provided services different services；And
The identifier of the second mobility management entity node is added to attached request by the terminal, and is passed again The defeated attached request is to be connected to the second mobility management entity node.
(complementary annotations 16)
According to the communication means described in complementary annotations 12, including：
The terminal transmits RRC (radio resource control) connection request to base station apparatus, adds to the RRC connection request Connectivity request message of the request to the second mobility management entity node, the second mobility management entity node has been added to provide The service different from the service provided by first movement management entity node；And
Have to mobile management from foundation when the base station apparatus transmits after receiving the RRC connection request When the attached request of the terminal of the RRC connections of entity, the base station apparatus selects the second mobility management entity section Point by the terminal to be connected to the second mobility management entity node.
(complementary annotations 17)
According to the communication means described in complementary annotations 12, including：
When establish have with the first movement management entity node of the session of the terminal release the base station apparatus with When the connection established between the first movement management entity node, described in the first movement management entity node instruction Base station apparatus selects the second mobile management real in the selection next time for the mobility management entity that the base station apparatus carries out Body node, the clothes that the second mobility management entity node is provided and provided by the first movement management entity node It is engaged in different services；And
When the request of location management area update is transferred to the base station apparatus by the terminal, the base station apparatus The second mobility management entity node is selected so that the terminal is connected to the second mobility management entity node.
(complementary annotations 18)
According to the communication means described in complementary annotations 12, including：
First service GPRS (General Packet Radio Service) supporting node (SGSN) is via radio network controller When receiving the attached request from the terminal, Serving GPRS Support Node is reselected into request signal and is transferred to the nothing Line electric network controller, in order to which the terminal is connected to second service GPRS Support Node, the second service GPRS branch It serves as a diplomatic envoy and a service different from the service provided by the first service GPRS Support Node is provided；And
Attached request is transferred to the second service GPRS Support Node by the radio network controller, will be described Terminal is connected to the second service GPRS Support Node.
(complementary annotations 19)
According to the communication means described in complementary annotations 12, including：
First service GPRS (General Packet Radio Service) supporting node (SGSN) is via no network of wires controller When receiving attached request from the terminal, Serving GPRS Support Node change request signal is transferred to second service GPRS branch It serves as a diplomatic envoy a little, in order to which the terminal is connected to the second service GPRS Support Node, the second service GPRS branch is served as a diplomatic envoy Point provides the service different from the service provided by the first service GPRS Support Node；And
Second GPRS Support Node continues attached process, and the terminal is connected to the second service GPRS branch It serves as a diplomatic envoy a little.
(complementary annotations 20)
According to the communication means described in complementary annotations 12, including：
First service GPRS (general packet radio service) supporting node (SGSN) is received via radio network controller To when attached request from the terminal, to the attached refusal of the terminal transmission, the terminal is connected to described second Serving GPRS Support Node, to the attached identifier for refusing to be added to second service GPRS Support Node, second clothes Business GPRS Support Node provides the service different from the service provided by the first service GPRS Support Node；And
The identifier of the second service GPRS Support Node is added to attached request by the terminal, and is transmitted again The attached request is to be connected to the second service GPRS Support Node.
(complementary annotations 21)
According to the communication means described in complementary annotations 12, including：
RRC (radio resource control) connection request is transferred to radio network controller by the terminal, is connected to the RRC Connect the connectivity request message that request is added to connection of the request to second service GPRS Support Node, the second service GPRS branch It serves as a diplomatic envoy and a service different from the service provided by first service GPRS (General Packet Radio Service) supporting node is provided； And
Have to service from foundation when the radio network controller is transmitted when receiving the RRC connection request When the attached request of the terminal of the RRC connections of GPRS Support Node, the radio network controller selection described second Serving GPRS Support Node by the terminal to be connected to second GPRS Support Node.
(complementary annotations 22)
According to the communication means described in complementary annotations 12, including：
It is released with the first service GPRS of the session of the terminal (General Packet Radio Service) supporting node when establishing to have It is placed between first service GPRS (General Packet Radio Service) supporting nodes and the radio network controller and builds When vertical connection, the first service GPRS Support Node instructs the radio network controller by the wireless network control Second service GPRS Support Node, the second service are selected in the selection next time for the Serving GPRS Support Node that device carries out GPRS Support Node provides the service different from the service provided by the first service GPRS Support Node；And
When the request of location management area update is transferred to the radio network controller by the terminal, the nothing Line electric network controller selects the second service GPRS Support Node the terminal is connected to the second service GPRS Supporting node.
(complementary annotations 23)
A kind of node apparatus, the node apparatus are performed control to based on subscriber information and end message, will with by described Another mobile management node apparatus of the type compatibility of service characteristic or the terminal that terminal is utilized is selected as pipe The terminal is connected to selected another mobile management node and filled by the ambulant mobile management node apparatus for managing terminal It sets.
(complementary annotations 24)
According to the node apparatus described in complementary annotations 23, wherein the node apparatus is nothing in mobile communication system Line is electrically accessed the node apparatus on network or core network.
(complementary annotations 25)
A kind of communication system, including：
The general end of ambulant core network node as management terminal being used for other than predetermined particular terminal The general MME (mobility management entity) at end or general SGSN (Serving GPRS Support Node)；And
It includes that predetermined special services are supplied to the spy to customize MME or customization SGSN, the customization MME or customization SGSN Determine the function of terminal, or be customized to it is compatible with the particular terminal of predefined type,
Wherein, the general MME, the general SGSN or described particular terminals select the customization MME or described customizations The node that SGSN is connected to as the particular terminal.
Reference numerals list
1 UE
11 e nodes B
21 general MME
22 customization MME
31 HSS
41 S-GW (service GW)
51 P-GW(PDN GW)
61 service networks
101 UE(MS)
111 node B
121 general SGSN
122 customization SGSN
131 HLR
141 GGSN
161 service networks
171 RNC

Claims (9)

1. a kind of system, including：
Core network node；
Terminal；
Radio access network node, wherein
The core network node is configured as：
Information corresponding with the usage type of the terminal is sent to the radio access network node；
The terminal is configured as：
TAU/RAU requests are sent to the radio access network node；
The radio access network node is configured as：
After receiving the TAU/RAU requests, core network node is selected based on described information.
2. a kind of core network node, the core network node is configured as：
Information corresponding with the usage type of terminal is sent to radio access network node, so as to the radio access network Network node selects core network node during the TAU/RAU processes of the terminal based on described information.
3. a kind of terminal, the terminal is configured as：
TAU/RAU requests are sent to radio access network node, so that the radio access network node is in the terminal TAU/RAU processes during core network node selected based on information corresponding with the usage type of the terminal.
4. a kind of radio access network node, the radio access network node is configured as：
Core network node is selected based on information corresponding with the usage type of terminal.
5. a kind of radio access network node, the radio access network node is configured as：
During the TAU/RAU processes of terminal, core net is selected based on information corresponding with the usage type of the terminal Network node.
6. a kind of method, including：
Information corresponding with the usage type of terminal is sent to radio access network node, so as to the radio access network Network node selects core network node during the TAU/RAU processes of the terminal based on described information.
7. a kind of method, including：
TAU/RAU requests are sent to radio access network node, so that the radio access network node is in terminal Core network node is selected based on information corresponding with the usage type of the terminal during TAU/RAU processes.
8. a kind of method, including：
Core network node is selected based on information corresponding with the usage type of terminal.
9. a kind of method, including：
During the TAU/RAU processes of terminal, core net is selected based on information corresponding with the usage type of the terminal Network node.
CN201810397978.4A 2011-09-30 2012-09-28 System, core network node, terminal, radio access network node and method Pending CN108810867A (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
JP2011-217384 2011-09-30
JP2011217384 2011-09-30
CN201280048275.1A CN103858517A (en) 2011-09-30 2012-09-28 Communication system, method and apparatus

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
CN201280048275.1A Division CN103858517A (en) 2011-09-30 2012-09-28 Communication system, method and apparatus

Publications (1)

Publication Number Publication Date
CN108810867A true CN108810867A (en) 2018-11-13

Family

ID=47995845

Family Applications (5)

Application Number Title Priority Date Filing Date
CN201510751790.1A Active CN105392153B (en) 2011-09-30 2012-09-28 Communication system, method and apparatus
CN201810397978.4A Pending CN108810867A (en) 2011-09-30 2012-09-28 System, core network node, terminal, radio access network node and method
CN201280048275.1A Pending CN103858517A (en) 2011-09-30 2012-09-28 Communication system, method and apparatus
CN201810397425.9A Pending CN108924813A (en) 2011-09-30 2012-09-28 System, terminal, core network node, radio access network node and method
CN201610010213.1A Active CN105554789B (en) 2011-09-30 2012-09-28 Communication system, method and apparatus

Family Applications Before (1)

Application Number Title Priority Date Filing Date
CN201510751790.1A Active CN105392153B (en) 2011-09-30 2012-09-28 Communication system, method and apparatus

Family Applications After (3)

Application Number Title Priority Date Filing Date
CN201280048275.1A Pending CN103858517A (en) 2011-09-30 2012-09-28 Communication system, method and apparatus
CN201810397425.9A Pending CN108924813A (en) 2011-09-30 2012-09-28 System, terminal, core network node, radio access network node and method
CN201610010213.1A Active CN105554789B (en) 2011-09-30 2012-09-28 Communication system, method and apparatus

Country Status (11)

Country Link
US (5) US9572134B2 (en)
EP (4) EP3324671A1 (en)
JP (7) JP5500320B2 (en)
CN (5) CN105392153B (en)
BR (3) BR122016000399B1 (en)
ES (1) ES2694175T3 (en)
MX (1) MX2014003394A (en)
MY (4) MY185434A (en)
PH (3) PH12015502533B1 (en)
WO (1) WO2013047822A1 (en)
ZA (2) ZA201401963B (en)

Families Citing this family (59)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105392153B (en) * 2011-09-30 2018-05-11 日本电气株式会社 Communication system, method and apparatus
JP5923393B2 (en) * 2012-06-15 2016-05-24 株式会社Ｎｔｔドコモ Mobile communication network distribution system and mobile communication network distribution method
WO2014169950A1 (en) * 2013-04-16 2014-10-23 Nokia Solutions And Networks Oy Mobility management entity (mme) triggered detach and re-attach to a specific target mme
UA116025C2 (en) * 2013-07-04 2018-01-25 Нек Корпорейшн SYSTEM, METHOD AND DEVICE OF COMMUNICATION
JP2015043522A (en) * 2013-08-26 2015-03-05 株式会社日立製作所 Gateway devices, packet distribution control method, and radio communication system
JP6196103B2 (en) 2013-09-13 2017-09-13 株式会社Ｎｔｔドコモ Mobile communication system, network node, and mobile communication method
KR102143446B1 (en) * 2013-09-27 2020-08-11 에스케이텔레콤 주식회사 Authentication apparatus in wireless communication system, method thereof and computer recordable medium storing the method
BR112016006125B1 (en) * 2013-09-27 2023-04-11 Nec Corporation SYSTEM, METHOD, TERMINAL, RADIO ACCESS NETWORK NODE, CORE NETWORK NODE
JP6340076B2 (en) * 2013-10-29 2018-06-06 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． Mobility management method, apparatus and system
EP3065465B1 (en) 2013-11-01 2018-01-10 Huawei Technologies Co., Ltd. Network selection method and core network device
EP3095273B1 (en) 2014-01-15 2018-08-08 Nokia Solutions and Networks Oy Overlay implementation of ims centralized service network system with selection of serving network entity within a pool
CN111510980B (en) 2014-05-08 2022-06-03 交互数字专利控股公司 Method for redirecting UE to special core network node and wireless transmitting and receiving unit
US10299298B2 (en) * 2014-05-16 2019-05-21 Lg Electronics Inc. Packet data network connection process in wireless communication system, and apparatus for same
WO2015182141A1 (en) * 2014-05-30 2015-12-03 Nec Corporation Apparatus, system and method for dedicated core network
US10104603B2 (en) 2014-05-30 2018-10-16 Nec Corporation Apparatus, system and method for dedicated core network
JP6386102B2 (en) * 2014-06-17 2018-09-05 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． MME reselection method and MME
EP3163944B1 (en) 2014-06-24 2019-10-09 Nec Corporation A mobility management node, mobile terminal, methods therefor and a computer program for performing a mme relocation procedure
JP6460102B2 (en) * 2014-06-24 2019-01-30 日本電気株式会社 Control node and network node and methods performed by them
WO2016000189A1 (en) * 2014-06-30 2016-01-07 华为技术有限公司 Network element selection entity and user equipment registration method
US10231176B2 (en) * 2014-10-06 2019-03-12 Sharp Kabushiki Kaisha Base station device, terminal device, location management device, and control method
US9832719B2 (en) * 2014-10-17 2017-11-28 Qualcomm Incorporated Selection of a serving node in a wireless communication system
JP6520044B2 (en) * 2014-10-24 2019-05-29 日本電気株式会社 Wireless terminal, network device, and methods thereof
EP3223561B1 (en) 2014-11-21 2019-10-16 NEC Corporation Offloading traffic of an mtc device
EP3223563A4 (en) * 2014-11-21 2018-10-17 NEC Corporation Communication device, communication method, communication system, and storage medium
EP3223562A4 (en) * 2014-11-21 2018-06-27 NEC Corporation Communication device, communication method, communication system, and storage medium
JP2016122887A (en) * 2014-12-24 2016-07-07 富士通株式会社 Radio base station, radio device, radio communication system and radio communication control method
WO2016148197A1 (en) * 2015-03-17 2016-09-22 日本電気株式会社 Communication system, device, and method, and program
CN106304246A (en) * 2015-05-11 2017-01-04 中兴通讯股份有限公司 A kind of cut-in method and corresponding access node, terminal and communication network
US10524171B2 (en) * 2015-06-16 2019-12-31 Qualcomm Incorporated Reselection between regular and dedicated core networks
KR20180039090A (en) * 2015-08-07 2018-04-17 샤프 가부시키가이샤 A terminal device, a base station device, a communication control method of a terminal device, and a communication control method of a base station device
US9730056B2 (en) * 2015-08-14 2017-08-08 Telefonaktiebolaget Lm Ericsson (Publ) System, method, and apparatus for facilitating selection of a serving node
CN107925876B (en) * 2015-08-14 2021-07-30 瑞典爱立信有限公司 Node and method for handling mobility procedures of a wireless device
US9516572B1 (en) 2015-10-01 2016-12-06 Sprint Communications Company L.P. Server control of user equipment having a current access point name (APN) data set
US9930517B2 (en) * 2015-10-30 2018-03-27 Acer Incorporated Apparatuses and methods for handling change of user equipment (UE) usage type
CN108464036B (en) 2015-11-06 2023-03-17 交互数字专利控股公司 Method, core network entity and wireless transmit/receive unit (WTRU) using enhanced dedicated core network (DNC) selection
CN112188596A (en) * 2015-11-10 2021-01-05 华为技术有限公司 Method for selecting service network, network equipment and management equipment
JP2019004197A (en) * 2015-11-10 2019-01-10 シャープ株式会社 Terminal device, c-sgn, and communication control method
JP2019009480A (en) * 2015-11-10 2019-01-17 シャープ株式会社 Terminal device, c-sgn, and communication control method
JP2019009481A (en) * 2015-11-10 2019-01-17 シャープ株式会社 Terminal device, c-sgn, and communication control method
EP4021032A1 (en) 2015-11-19 2022-06-29 SK Telecom Co., Ltd. Method and apparatus for selecting core network in mobile communication system
CN108476546B (en) 2015-12-29 2021-11-09 Lg 电子株式会社 Method and apparatus for establishing bearer for transmission of user data
MX2018008538A (en) 2016-01-14 2018-11-29 Ericsson Telefon Ab L M Customization approach for cooperating nodes.
WO2017121481A1 (en) * 2016-01-14 2017-07-20 Telefonaktiebolaget Lm Ericsson (Publ) Method and nodes for performing a tracking area update (tau) / routing area update (rau) procedure in a stateless architecture
JP2019050435A (en) * 2016-01-19 2019-03-28 シャープ株式会社 Terminal device, c-sgn, and communication control method
US10440556B2 (en) * 2016-02-11 2019-10-08 Lg Electronics Inc. Method for updating location of terminal in wireless communication system and apparatus for supporting same
JP6611173B2 (en) * 2016-02-22 2019-11-27 日本電気株式会社 Gateway device, communication method, and program
JP6632025B2 (en) * 2016-02-22 2020-01-15 日本電気株式会社 Communication system, communication method, and program
JP6944007B2 (en) * 2016-02-29 2021-10-06 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． Methods, devices, and wireless communication systems to determine control plane nodes
WO2017147751A1 (en) * 2016-02-29 2017-09-08 华为技术有限公司 Method, apparatus and wireless communication system for determining control plane node
JP2019096918A (en) * 2016-04-05 2019-06-20 シャープ株式会社 Terminal, base station device, mme (mobility management entity) and communication control method
EP3448089A1 (en) * 2016-04-20 2019-02-27 Huawei Technologies Co., Ltd. Method of processing dedicated core network migration, equipment, and system
FR3050898B1 (en) * 2016-04-27 2018-05-25 Airbus Ds Slc METHOD FOR ATTACHING USER EQUIPMENT TO A BASE STATION OF A TELECOMMUNICATIONS SYSTEM
WO2018008922A2 (en) * 2016-07-04 2018-01-11 엘지전자 주식회사 Method for supporting nas signaling by base station in wireless communication system and apparatus therefor
DK3306887T3 (en) * 2016-10-10 2021-01-04 Ntt Docomo Inc PROCEDURE FOR ESTABLISHING A CONNECTION OF A MOBILE TERMINAL TO A MOBILE RADIO COMMUNICATION NETWORK AND COMMUNICATION NETWORK DEVICE
US10021557B1 (en) 2017-08-18 2018-07-10 Verizon Patent And Licensing Inc. Universal GUTI for simplified device onboarding
US9998896B1 (en) * 2017-08-18 2018-06-12 Verizon Patent And Licensing Inc. Dedicated APN access using default network access key for profile download
JP6609678B2 (en) * 2018-08-08 2019-11-20 華為技術有限公司 MME reselection method and MME
US11419174B2 (en) * 2019-02-26 2022-08-16 Mediatek Inc. Connection recovery method for recovering a connection between a communications apparatus and a data network and the associated communications apparatus
WO2020255490A1 (en) * 2019-06-19 2020-12-24 日本電気株式会社 Core network device, communication control method, nontransitory computer-readable medium, and wireless communication system

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101222439A (en) * 2008-01-28 2008-07-16 华为技术有限公司 User load distribution method, device and system of core network
CN101400084A (en) * 2007-09-30 2009-04-01 北京三星通信技术研究有限公司 Method for changing service core network node of UE
CN101500281A (en) * 2008-01-30 2009-08-05 华为技术有限公司 Method for messaging in routing non-access layer
CN101534500A (en) * 2008-03-10 2009-09-16 华为技术有限公司 Addressing method, network element equipment and network system
US20110238844A1 (en) * 2010-03-29 2011-09-29 Vodafone Holding Gmbh Connection Management for M2M Device in A Mobile Communication Network

Family Cites Families (34)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4000906B2 (en) 2002-05-22 2007-10-31 日本電気株式会社 Packet transfer route optimization method, packet transfer apparatus, and program
US7305251B2 (en) * 2003-10-07 2007-12-04 Motorola Inc. Method for selecting a core network
EP1720364A4 (en) 2004-02-23 2011-02-09 Nec Corp Mobile subscriber network and resource management method
EP2456276B1 (en) * 2005-04-26 2014-06-25 Vodafone Group PLC Telecommunications Networks
US8090392B2 (en) 2005-08-05 2012-01-03 Interdigital Technology Corporation Method and system for reporting a short message capability via an IP multimedia subsystem
WO2007058024A1 (en) 2005-11-16 2007-05-24 Nec Corporation Mobile communication system, core network, radio network system, and method for selecting network for containing the system
CN100479600C (en) * 2006-07-19 2009-04-15 华为技术有限公司 Method for selecting core network by network resource identification code
US20070254667A1 (en) * 2006-04-28 2007-11-01 Joanna Jokinen Inter-MME handover in evolved communication systems
CN100584093C (en) 2006-08-15 2010-01-20 华为技术有限公司 A method and system transferring user device in mobile communication system
JP4848890B2 (en) * 2006-08-23 2011-12-28 日本電気株式会社 Mobile communication system and method, and base station used therefor
CN101094512A (en) * 2006-09-07 2007-12-26 中兴通讯股份有限公司 Method for establishing user's context and load bearing context in multicast service
CN101573997B (en) * 2006-12-29 2013-05-29 艾利森电话股份有限公司 Automatic distribution of server and gateway information for pool configuration
CN101272614B (en) * 2007-03-20 2010-12-08 华为技术有限公司 Method, system and device for selecting network equipment
CN101355793B (en) 2007-07-27 2011-08-31 华为技术有限公司 Method and apparatus for recognizing user equipment as well as method for transferring and distributing temporary mark
EP2048910A1 (en) * 2007-10-10 2009-04-15 France Telecom Radio access technology selection in telecommunications system
US9247420B2 (en) * 2007-12-12 2016-01-26 Lg Electronics Inc. Method of managing user equipment capabilities
EP2079253A1 (en) * 2008-01-09 2009-07-15 Panasonic Corporation Non-3GPP to 3GPP network handover optimizations
EP2353337B1 (en) * 2008-11-17 2018-10-03 Cisco Technology, Inc. Dynamic load balancing in a communication network
WO2011038359A2 (en) * 2009-09-26 2011-03-31 Cisco Technology, Inc. Providing services at a communication network edge
US9560140B2 (en) * 2009-09-29 2017-01-31 Qualcomm Incorporated Signaling identification of machine to machine devices and services
JP5187909B2 (en) * 2009-10-05 2013-04-24 株式会社エヌ・ティ・ティ・ドコモ Mobile communication method and relay node
CN102056265A (en) * 2009-11-10 2011-05-11 中兴通讯股份有限公司 Method, mobility management unit and gateway unit for limiting access and communication of machine type communication (MTC) equipment
US9307390B2 (en) 2010-01-08 2016-04-05 Gemalto Sa Group based mobility optimization method and device in machine-type communication
CN102123477B (en) * 2010-01-08 2015-06-10 中兴通讯股份有限公司 Access realization method and device of M2M (Machine to Machine) core network
EP2517501A4 (en) * 2010-02-03 2013-03-06 Huawei Tech Co Ltd System and method for managing an access network re-selection
KR101609580B1 (en) 2010-02-10 2016-04-07 삼성전자주식회사 Wireless communication system and method for establishing connection between user equipment and mobility management entity
KR101835042B1 (en) 2010-03-23 2018-03-08 인터디지탈 패튼 홀딩스, 인크 Apparatus and method for efficient signaling for machine type communication
EP2577887A4 (en) * 2010-05-26 2016-11-16 Lg Electronics Inc Nas-based signaling protocol for overload protection of random access in massive machine type communication
US20120238208A1 (en) 2011-03-17 2012-09-20 Maik Bienas Mobile radio communication devices and servers
US8565100B2 (en) * 2011-03-23 2013-10-22 Renesas Mobile Corporation Method and apparatus for facilitating machine-type communication
US20120254890A1 (en) * 2011-04-01 2012-10-04 Renesas Mobile Corporation Small Data Transmission For Detached Mobile Devices
US20120252481A1 (en) * 2011-04-01 2012-10-04 Cisco Technology, Inc. Machine to machine communication in a communication network
KR101836562B1 (en) * 2011-08-30 2018-03-08 텔레호낙티에볼라게트 엘엠 에릭슨(피유비엘) Methods of and nodes for selecting a target core network for handing over a voice session of a terminal
CN105392153B (en) * 2011-09-30 2018-05-11 日本电气株式会社 Communication system, method and apparatus

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101400084A (en) * 2007-09-30 2009-04-01 北京三星通信技术研究有限公司 Method for changing service core network node of UE
CN101222439A (en) * 2008-01-28 2008-07-16 华为技术有限公司 User load distribution method, device and system of core network
CN101500281A (en) * 2008-01-30 2009-08-05 华为技术有限公司 Method for messaging in routing non-access layer
CN101534500A (en) * 2008-03-10 2009-09-16 华为技术有限公司 Addressing method, network element equipment and network system
US20110238844A1 (en) * 2010-03-29 2011-09-29 Vodafone Holding Gmbh Connection Management for M2M Device in A Mobile Communication Network

Also Published As

Publication number Publication date
CN105392153B (en) 2018-05-11
US20160128051A1 (en) 2016-05-05
MY166216A (en) 2018-06-22
CN103858517A (en) 2014-06-11
JP6308280B2 (en) 2018-04-11
BR122015028043A2 (en) 2018-03-20
US20170250789A1 (en) 2017-08-31
EP2763496A4 (en) 2015-05-06
ES2694175T3 (en) 2018-12-18
MX2014003394A (en) 2014-07-09
US20170251103A1 (en) 2017-08-31
MY166211A (en) 2018-06-22
PH12015502533A1 (en) 2016-12-05
BR122016000399A2 (en) 2018-03-20
EP2763496B1 (en) 2018-08-01
US9572134B2 (en) 2017-02-14
JP2016054554A (en) 2016-04-14
EP3026952A1 (en) 2016-06-01
JP5862829B2 (en) 2016-02-16
PH12018502260A1 (en) 2019-06-24
JP2016007052A (en) 2016-01-14
JP6308279B2 (en) 2018-04-11
US20140211728A1 (en) 2014-07-31
ZA201505059B (en) 2016-12-21
BR122015028043B1 (en) 2019-05-07
JP2017005766A (en) 2017-01-05
WO2013047822A1 (en) 2013-04-04
US9706530B2 (en) 2017-07-11
MY185434A (en) 2021-05-19
US20160066231A1 (en) 2016-03-03
JP5500320B2 (en) 2014-05-21
ZA201401963B (en) 2016-01-27
JP2017060171A (en) 2017-03-23
JPWO2013047822A1 (en) 2015-03-30
EP3001719A1 (en) 2016-03-30
CN108924813A (en) 2018-11-30
PH12016500039B1 (en) 2016-04-11
PH12015502533B1 (en) 2016-12-05
CN105392153A (en) 2016-03-09
BR112014007308A2 (en) 2017-04-04
JP5804114B2 (en) 2015-11-04
MY156860A (en) 2016-04-05
CN105554789B (en) 2019-03-15
US9686774B2 (en) 2017-06-20
JP2018137765A (en) 2018-08-30
EP3324671A1 (en) 2018-05-23
CN105554789A (en) 2016-05-04
PH12016500039A1 (en) 2016-04-11
BR122016000399B1 (en) 2019-05-07
BR112014007308B1 (en) 2019-04-09
JP2014132785A (en) 2014-07-17
EP2763496A1 (en) 2014-08-06

Similar Documents

Publication Publication Date Title
CN105554789B (en) Communication system, method and apparatus
RU2669792C1 (en) Communication system, method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
WD01 Invention patent application deemed withdrawn after publication
WD01 Invention patent application deemed withdrawn after publication

Application publication date: 20181113