WO2016063449A1 - 制御装置及びその方法 - Google Patents
制御装置及びその方法 Download PDFInfo
- Publication number
- WO2016063449A1 WO2016063449A1 PCT/JP2015/004404 JP2015004404W WO2016063449A1 WO 2016063449 A1 WO2016063449 A1 WO 2016063449A1 JP 2015004404 W JP2015004404 W JP 2015004404W WO 2016063449 A1 WO2016063449 A1 WO 2016063449A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- core network
- network entity
- mme
- wireless terminal
- control device
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims description 59
- 230000011664 signaling Effects 0.000 claims abstract description 24
- 238000004891 communication Methods 0.000 claims description 30
- 230000004044 response Effects 0.000 claims description 14
- 230000005540 biological transmission Effects 0.000 abstract description 5
- 238000010586 diagram Methods 0.000 description 9
- 238000010295 mobile communication Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 5
- 238000012508 change request Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 235000008694 Humulus lupulus Nutrition 0.000 description 3
- 238000005352 clarification Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- 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
- H04W36/125—Reselecting a serving backbone network switching or routing node involving different types of service backbones
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/24—Reselection being triggered by specific parameters
- H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
- H04W36/304—Reselection being triggered by specific parameters by measured or perceived connection quality data due to measured or perceived resources with higher communication quality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
- H04W40/04—Communication route or path selection, e.g. power-based or shortest path routing based on wireless node resources
-
- 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
- H04W8/065—Registration at serving network Location Register, VLR or user mobility server involving selection of the user mobility server
Definitions
- the present disclosure relates to a mobile communication network, and more particularly to mobility management of a wireless terminal.
- a base station receives an attach request from a wireless terminal, determines whether the wireless terminal is a stationary device (stationary device), and the wireless terminal is stationary.
- the local component is at least one of the functions of remote mobility management management entity (MME), remote serving gateway (S-GW), or remote packet data network (PDN) gateway (P-GW).
- MME remote mobility management management entity
- S-GW remote serving gateway
- PDN remote packet data network gateway
- a remote MME, a remote S-GW, and a remote P-GW are devices located in an evolved “packet” core “(EPC)” network.
- the attach request includes an indication indicating whether or not the wireless terminal is a stationary device, and whether the base station (eNB) is a device where the wireless terminal is stationary based on the display Determine whether or not.
- a home subscriber server (HSS) in an EPC network determines whether the wireless terminal is a stationary device based on subscriber information of the wireless terminal.
- the base station (eNB) sends an attach request to the HSS via the MME device, receives a response from the HSS via the MME device, and determines whether the wireless terminal is a stationary device from the HSS. Determine based on the response.
- the base station (eNB) uses a local component (for example, a local MME component) when the wireless terminal is a stationary device, and the wireless terminal When it is a mobile device, it uses a remote MME, a remote S-GW, and a remote P-GW.
- Patent Document 1 determines whether a wireless terminal is a stationary device in the base station (eNB) or HSS, and associates the wireless terminal with the base station when the wireless terminal is a stationary device. It is described that a connection of the wireless terminal is established using a specified local component (for example, a local MME component).
- a specified local component for example, a local MME component
- the amount of mobility of a wireless terminal may not be sufficient as a criterion for core network entity selection in some cases. For example, even if the wireless terminal is a mobile device, if the communication frequency of the wireless terminal is high or the delay tolerance level of the wireless terminal is low (that is, the wireless terminal allows delay) If not, it may be more appropriate to use a local component in the radio access network for the wireless terminal than a remote device in the core network.
- One of the objectives that embodiments disclosed herein are to achieve is associated with multiple core network entities (eg, MME devices in the core network and radio access networks (eg, base stations)).
- An apparatus, method, and program that contribute to determining which of local MME components) to use for a wireless terminal using one or more criteria (indicators, parameters) different from the mobility of the wireless terminal Is to provide. It should be noted that this objective is only one of several objectives that the embodiments disclosed herein intend to achieve. Other objects or problems and novel features will become apparent from the description of the present specification or the accompanying drawings.
- the control device includes a memory and a processor coupled to the memory.
- the processor is configured to increase a path cost or a management range with the wireless terminal based on at least one of a delay tolerance level of the wireless terminal, a frequency of control signaling of the wireless terminal, and a communication interval of the wireless terminal. It operates to select a target core network entity to provide a mobility management service or a data transfer service for mobility management of the wireless terminal from among a plurality of different candidate core network entities.
- the method includes: a path cost to the wireless terminal based on at least one of a delay tolerance level of the wireless terminal, a frequency of control signaling of the wireless terminal, and a communication interval of the wireless terminal. Or selecting a target core network entity to provide a mobility management service or a data transfer service for the wireless terminal from among a plurality of candidate core network entities having different management ranges.
- the program includes a group of instructions (software code) for causing the computer to perform the method according to the second aspect described above when read by the computer.
- the above aspects contribute to determining which of a plurality of core network entities to use for a wireless terminal using one or more criteria (indicators, parameters) different from the mobility of the wireless terminal.
- An apparatus, a method, and a program can be provided.
- FIG. 1 shows a configuration example of a public land mobile network (PLMN) 100 according to the present embodiment.
- the PLMN 100 provides a communication service such as voice communication and / or packet data communication to a wireless terminal (User Equipment (UE)) 111.
- the PLMN 100 includes a radio access network (Evolved Universal Terrestrial Radio Access Network (E-UTRAN)) 110 and a core network (Evolved Packet Core (EPC)) 120.
- the E-UTRAN 110 includes a base station (eNB) 112 that performs radio communication with the UE 111.
- the EPC 120 includes a mobility management entity (MME) device 121, a home subscriber server (HSS) 122, a serving gateway (S-GW) 123, and a PDN gateway (P-GW) 124.
- MME mobility management entity
- HSS home subscriber server
- S-GW serving gateway
- P-GW PDN gateway
- FIG. 1 shows only one eNB 112, one S-GW 123, and one P-GW 124 for simplification.
- the PLMN 100 may include a plurality of eNBs 112, a plurality of S-GWs 123, and a plurality of P-GWs 124.
- One MME device 121 and one HSS 122 may communicate with a plurality of eNBs, a plurality of S-GWs, and a plurality of P-GWs.
- the PLMN 100 may further include a plurality of MME devices 121 and a plurality of HSSs 122.
- the MME and HSS 122 are nodes or entities of the control plane arranged in EPC 120.
- the MME can perform mobility management and bearer management of a plurality of UEs (UEs) including the UE 111.
- Mobility management is used to keep track of the UE's current location (keep track) and includes maintaining a mobility management context (MM context) for the UE.
- the bearer management controls the establishment of an EPS bearer for the UE to communicate with the external network (Packet Data Network (PDN)) 130 via the E-UTRAN 110 and the EPC 120, and bearer management context (ie, EPS EPS bearer context) related to the UE. ).
- the HSS 122 manages subscriber information of UEs including the UE 111.
- the S-GW 123 and the P-GW 124 are user plane packet transfer nodes arranged in the EPC 120 and transfer user data (that is, Internet Protocol (IP) packets).
- the S-GW 123 is a gateway to the E-UTRAN 110, and is connected to the eNB 112 via the S1-U interface.
- the P-GW 124 is a gateway with the PDN 130 and is connected to the PDN 130 via the SGi interface.
- the PDN 130 may be an external network such as the Internet, or may be a network for an IP service (e.g., IP Multimedia Subsystem (IMS) service) provided by an operator who manages the EPC 120.
- IP IP Multimedia Subsystem
- the MME component 141 is associated with the eNB 112 and is arranged away from the MME device 121 in the EPC 120.
- the MME component 141 may be disposed integrally with the eNB 112.
- the MME component 141 may be arranged at the same geographical location as the eNB 112 or at the same cell site.
- the MME component 141 can perform at least a part of a plurality of functions related to mobility management and bearer management that the MME device 121 has.
- the MME component 141 may perform tracking of the UE 111, for example. In other words, the MME component 141 may perform a location update procedure (Tracking Area Update (TAU) procedure) regarding the UE 111.
- TAU Track Area Update
- the MME component 141 may establish an EPS bearer for the UE 111.
- the MME component 141 may perform a bearer establishment procedure (Service Request procedure) related to the UE 111.
- the MME component 141 may perform paging of the UE 111.
- the MME component 142 is associated with the S-GW 123 and is arranged away from the MME device 121 in the EPC 120.
- the MME component 142 may be disposed integrally with the S-GW 123.
- the MME component 142 may be located at the same geographical location as the S-GW 123 or at the same cell site, for example. Similar to the MME component 141, the MME component 142 can perform at least a part of a plurality of functions related to mobility management and bearer management that the MME device 121 has.
- the MME component 141 is arranged away from the MME device 121, and the path cost between the UE 111 and the MME component 141 is different from that between the UE 111 and the MME device 121.
- the MME component 141 is further arranged away from the MME component 142, and the path cost to the UE 111 is different from that of the MME component 142.
- the path cost is a cost required for a control message (for example, a data packet) to reach the MME component 141 from the UE 111 (or vice versa), and can be defined using various metrics.
- the route cost depends on, for example, the processing time of the processing device such as eNB existing between the UE 111 and the MME component 141, the processing time of the packet transfer device such as the router and the switch, and the bandwidth of the line between them. .
- the route cost may be defined using the number of hops (the number of relay nodes) until reaching the MME component 141 from the UE 111, for example. A large number of hops means a high route cost.
- the route cost may be defined using, for example, a delay time until reaching the MME component 141 from the UE 111 or Round Trip Time (RTT). A large delay time or RTT means a high path cost.
- the path cost may be defined using multiple metrics, such as the number of hops and delay time. The route cost is sometimes called distance.
- the MME component 141 associated with the eNB 112, the MME component 142 associated with the S-GW 123, and the MME device 121 in the EPC 120 may be distinguished from each other depending on the difference in management range.
- the MME component 141 is used for mobility management of UEs located in one or several cells managed by the eNB 112, and therefore its management range is relatively narrow.
- the MME component 142 is used for mobility management of UEs located in multiple cells managed by multiple eNBs 112 connected to the S-GW 123, and thus its management range is relatively moderate. is there.
- the MME device 121 is used for mobility management of UEs located in a number of cells managed by multiple S-GWs 123 and a number of eNBs 112, and thus its management scope is that of MME components 141 and 142. Wide compared to.
- An MME component arranged in association with a network node such as eNB 112 and S-GW 123 is assigned an IP address different from the IP address of the network node in order to distinguish the MME component from the network node with which the MME component is associated. May be. Instead, the MME component and the network node with which it is associated use a common IP address, and the network node with which the MME component is associated with a different Transmission Control Protocol (TCP) port number or User Datagram Protocol (UDP) may be distinguished by port number.
- TCP Transmission Control Protocol
- UDP User Datagram Protocol
- the control device 151 executes selection of the MME that performs the mobility management of the UE 111.
- the control device 151 may be arranged in the UE 111 as shown in FIG.
- the control device 151 may be arranged in the EPC 120, for example, the MME device 121.
- the control device 151 may be arranged in the E-UTRAN 110, for example, the eNB 112.
- the control device 151 includes a control node (eg, Software-Defined Network (SDN) controller, Network Function Virtualization (NFV) controller, Operations Support System (OSS), or Element Management) arranged outside the PLMN 100. System (EMS)).
- SDN Software-Defined Network
- NFV Network Function Virtualization
- OSS Operations Support System
- Element Management arranged outside the PLMN 100. System (EMS)).
- FIG. 2 is a flowchart showing an example (process 200) of the MME selection process performed by the control device 151.
- the control device 151 determines the path cost (or management) with the UE 111 based on at least one of the delay tolerance level of the UE 111, the frequency of control signaling of the UE 111, and the communication interval of the UE 111.
- a target MME for which mobility management of the UE 111 is to be performed is selected from among a plurality of candidate MMEs having different (ranges of ranges).
- the controller 151 may communicate with the E-UTRAN 110 and EPC 120 entities to detect multiple candidate MMEs.
- the control device 151 may receive a list of candidate MMEs from the serving MME (for example, the MME device 121) or the eNB 112 that is currently performing mobility management of the UE 111.
- the plurality of candidate MMEs include, for example, the MME component 141 associated with the eNB 112 and the MME device 121 in the EPC 120.
- the plurality of candidate MMEs may further include an MME component 142 associated with the S-GW 123.
- the MME component 141 associated with the eNB 112 generally has a lower path cost and a smaller management range than the MME device 121 and the MME component 142 arranged in the EPC 120.
- the control device 151 triggers a control procedure for transferring the mobility management of the UE 111 from the serving MME to the target MME based on the MME selection in the block 501.
- the controller 151 may send an MME change request message to the target MME or the serving MME.
- the target MME or the serving MME may start the MME change procedure itself.
- the MME selection by the control device 151 may be performed as follows, for example.
- the control device 151 has a relatively lower path cost (or a narrower management range) than the MME device 121 when the delay tolerance level of the UE 111 is lower than the threshold (that is, the UE 111 does not allow delay).
- the MME may be selected as the target MME.
- the MME component 141 associated with the E-UTRAN 110 for example, the eNB 112 may be selected as the target MME. Thereby, the delay time required for the control signaling process can be suppressed.
- the UE 111 has a relatively lower path cost than the serving MME when the response time of the serving MME (eg, the MME device 121) (eg, Round Trip Time (RTT)) exceeds a threshold (or You may select MME (for example, MME component 141) with a narrow management range as a target MME.
- the threshold value used here may be determined based on the delay tolerance level of the UE 111, and a smaller threshold value may be used as the delay tolerance level of the UE 111 is smaller.
- the control device 151 may select an MME having a lower path cost (or a narrower management range) than the MME device 121 as the target MME.
- the MME component 141 associated with the E-UTRAN 110 eg, eNB 112
- the load of the control plane for example, a communication apparatus and a communication line
- the control plane for example, a communication apparatus and a communication line
- the control device 151 has an MME whose path cost is relatively smaller (or whose management range is narrower) than that of the MME device 121 when the communication interval of the UE 111 falls below the threshold (that is, the communication interval of the UE 111 is short). May be selected as the target MME, for example, the MME component 141 associated with the E-UTRAN 110 (for example, eNB 112) may be selected as the target MME. Thereby, the load of the control plane (for example, a communication apparatus and a communication line) resulting from frequent occurrence of signaling between the E-UTRAN 110 and the EPC 120 can be suppressed.
- the control plane for example, a communication apparatus and a communication line
- the control device 151 may perform MME selection in consideration of the load on the network node. For example, when the load of the MME device 121 exceeds a threshold value, the control device 151 may select an MME having a relatively lower load than the MME device 121 as the target MME. Instead, the control device 151 refers to the load status of a plurality of MMEs (for example, the MME device 121, the MME component 141, and the MME component 142), and distributes the mobility management load among the plurality of MMEs. As such, the target MME may be selected. A plurality of examples of MME selection based on the different parameters described above may be used in appropriate combination.
- the controller 151 uses parameters used for MME selection (eg, network node response time (eg, RTT), network node load, path cost (eg, hop count, The delay time or distance)) may be measured by itself.
- the control device 151 may measure time from transmission of a control message to reception of a response message.
- the control device 151 may use Internet Control Message Protocol (ICMP) ping or traceroute to measure response time (RTT) or route cost.
- ICMP Internet Control Message Protocol
- the control device 151 may receive parameter values used for MME selection measured in the UE 111 or one or more network nodes in the E-UTRAN 110 or the EPC 120 from the UE 111 or these network nodes.
- the control device 151 may receive the parameter value from a control node (e.g., SDN controller, NFV controller, OSS, or EMS) arranged outside the PLMN 100.
- a control node e.g., SDN controller, NFV controller, OSS, or
- the control device 151 is based on at least one of the delay tolerance level of the UE 111, the frequency of control signaling of the UE 111, and the communication interval of the UE 111.
- the target MME to perform the mobility management of the UE 111 is selected from among a plurality of candidate MMEs having different path costs (or wide management ranges) with the UE 111. Therefore, the control apparatus 151 can select MME which should perform the mobility management of UE111 using the 1 or several reference
- control device 151 may consider the mobility of the UE 111 for MME selection in combination with the delay tolerance level of the UE 111, the frequency of control signaling, or the communication interval. In some implementations, the control device 151 may select an MME having a lower path cost (or a narrower management range) than the MME device 121 as the target MME when the mobility of the UE 111 is lower than the threshold. For example, the MME component 141 associated with the E-UTRAN 110 (eg, eNB 112) may be selected as the target MME. Selecting the MME component 141 associated with the E-UTRAN 110 when the mobility of the UE 111 is large may cause frequent changes of the MME and increase control signaling.
- MME component 141 associated with the E-UTRAN 110 eg, eNB 112
- the mobility of the UE 111 when the mobility of the UE 111 is small, it can be expected that the increase in signaling cost due to frequent changes in the MME is small. Therefore, by selecting the MME component 141 associated with the E-UTRAN 110 when the mobility of the UE 111 is small, an increase in signaling cost due to frequent changes in the MME is suppressed, and the delay time required for control signaling processing is reduced. Can be suppressed.
- the magnitude of the mobility of the UE 111 may be evaluated using, for example, an average cell stay time of the UE 111, a frequency of handover, or an average occurrence interval of handover.
- FIG. 3 is a sequence diagram showing an example (processing 300) of the MME changing procedure according to the present embodiment.
- the control device 151 is arranged in the UE 111.
- the UE 111 transmits an attach request message (Attach request message) to the MME device 121.
- the MME selection in block 301 may be performed by the MME selection function of the eNB 112 that has received the attach request.
- the MME device 121 as the serving MME transmits an attach approval message (Attach Accept message) to the UE 111.
- the attach approval message includes an MME selection policy.
- the MME selection policy may be transmitted using a Non-Access stratum (NAS) message (for example, a TAU Accept message) different from the attach approval message.
- NAS Non-Access stratum
- the MME selection policy may be transmitted from the serving MME (MME device 121) to the UE 111 in a procedure different from the attach procedure (blocks 301 and 302), for example, a TAU procedure.
- the UE 111 may receive the MME selection policy from the HSS 122 or the eNB 112.
- the UE 111 may receive the MME selection policy on the user plane from the control server in the PDN 130 via the PLMN 100.
- a mobility management procedure eg, TAU procedure, Service request procedure, and paging
- the MME selection policy indicates one or more parameters to be considered for MME selection.
- the one or more parameters to be considered for MME selection may include parameters related to at least one of a delay tolerance level of the UE 111, a frequency of control signaling of the UE 111, and a communication interval of the UE 111.
- Parameters to be considered for MME selection may include load information of network nodes (e.g., eNB 112, MME device 121, HSS 122, and S-GW 123). Additionally or alternatively, the selection policy may specify a selection algorithm.
- the selection policy includes (a) a parameter to be considered, (b) a threshold, (c) an identifier of an MME (eg, MME component 141) to be selected when the threshold is exceeded, and (d ) An identifier of the MME (for example, the MME device 121 or the MME component 142) selected when the threshold value is below may be indicated. Additionally or alternatively, the MME selection policy may indicate the timing or period at which MME selection should be performed.
- the UE 111 selects a target MME from among a plurality of candidate MMEs having different path costs (or a wide management range) with the UE 111 based on the MME selection policy.
- the MME component 141 associated with the eNB 112 is selected as the target MME.
- UE111 transmits a MME change request message to MME component 141 (target MME).
- the MME component 141 in response to receiving the MME change request message, the MME component 141 initiates a control procedure for transferring the mobility management of the UE 111 from the MME device 121 (serving MME) to the MME component 141 (target MME). .
- the MME component 141 sends an MME change response message to the UE 111.
- a mobility management procedure is performed between the UE 111 and the MME component 141 (target MME, ie new serving MME).
- the control procedure for transferring mobility management of UE 111 transfers mobility management from old MME to new MME in the TAU procedure performed when UE 111 detects that it has entered a new tracking area (TA). It may be the same as the procedure to do.
- FIG. 4 is a sequence diagram showing a specific example (process 400) of the control procedure (block 307).
- the MME component 141 target MME
- the MME device 121 sends a Context Request message to the MME device 121 (serving MME).
- the MME device 121 sends a Context Response message including the UE 111 context (MM context and EPS bearer context) to the MME component 141.
- the MME component 141 communicates with the HSS 122 and UE 111 (not shown) for UE 111 authentication and security setup. If UE 111 authentication and security are already enabled, block 403 may be omitted. In block 404, the MME component 141 transmits a Context Acknowledge message to the MME device 121.
- the MME component 141 transmits a Modify Bearer Request message to the S-GW 123 to inform the address of the new MME (that is, the MME component 141).
- the Modify Bearer Request message indicates the new MME that manages the EPS bearer of the UE 111, that is, the IP address of the MME component 141 and the MME14TEID.
- the S-GW 123 sends a Modify Bearer Response message to the MME component 141.
- Blocks 407 to 410 are performed to notify the HSS 122 of the MME change. Note that the change of the MME can be notified to the HSS 122 in a normal TAU procedure performed after the MME relocation procedure (400) is completed. Therefore, the processing in blocks 407 to 410 may be omitted.
- the MME component 141 sends an Update Location Request message to the HSS 122.
- the Update Location Request message indicates the identifier of the MME component 141.
- the HSS 122 sends a CancelCanLocation message to the MME device 121 to inform that the context (MM context and EPS bearer context) related to the UE 111 can be deleted.
- the MME device 121 deletes the context related to the UE 111 as necessary. Then, the MME device 121 transmits a Cancel Location Ack message to the HSS 122. In block 410, the HSS 122 acknowledges the Update Location Request by sending an Update Location Ack message to the MME component 141.
- MME selection can be performed in the UE 111. Therefore, it is possible to easily perform MME selection according to the state (for example, delay tolerance level, mobility characteristics, signaling frequency, or communication interval) of the UE 111 that dynamically changes.
- the UE 111 operates to receive an MME selection policy from the network (for example, the MME device 121). Therefore, the MME selection policy can be determined in the network, and the MME selection policy can be set in the UE 111 according to the network status (for example, the load of MME, whether congestion has occurred).
- the network status for example, the load of MME, whether congestion has occurred.
- FIG. 5 is a sequence diagram showing an example (process 500) of the MME changing procedure according to the present embodiment.
- the control device 151 is arranged in the MME device 121.
- the attach approval message (Attach Accept message) in block 502 may not include the MME selection policy.
- the MME device 121 control device 151) as the serving MME determines the UE 111 based on at least one of the delay tolerance level of the UE 111, the frequency of control signaling of the UE 111, and the communication interval of the UE 111.
- a target MME for which mobility management of the UE 111 is to be performed is selected from among a plurality of candidate MMEs having different path costs (or wide management ranges).
- the MME component 141 associated with the eNB 112 is selected as the target MME.
- the MME device 121 starts a control procedure for transferring the mobility management of the UE 111 from the MME device 121 (serving MME) to the MME component 141 (target MME).
- a mobility management procedure is performed between the UE 111 and the MME component 141 (target MME, that is, a new serving MME).
- the control procedure (block 505) for transferring the mobility management of the UE 111 is similar to the procedure for transmitting the UE context from the source MME to the target MME using the Forward Relocation Request message in the case of S1-based handover. Also good.
- FIG. 6 is a sequence diagram showing a specific example (process 600) of the control procedure (block 505).
- the MME device 121 (serving MME) transmits the context (MM (context and EPS bearer context) of the UE 111 to the MME component 141 (target MME).
- the MME component 141 target MME
- the GPRS Tunelling Protocol for the Control Plane (GTP-C) message transmitted at the S10 interface between the MMEs can be used.
- the Forward Relocation Request message or A modified version may be used.
- the Forward Relocation Request message in block 601 may include an information element indicating that the message is transmitted for Context Relocation instead of S1-based handover.
- the MME component 141 stores the context of the UE 111 received from the MME device 121 in its own memory or storage (not shown).
- the MME component 141 requests the S-GW 123 to update the EPS bearer context of the UE 111 held in the S-GW 123 (block 603).
- the processing in blocks 602 and 603 is similar to the processing in blocks 405 and 406 in FIG.
- the MME component 141 notifies the MME device 121 that it has accepted the handover of mobility management and bearer management of the UE 111.
- the GTP-C message transmitted in the S10 interface between the MMEs can be used for the transmission of this notification, and the Forward Relocation Response message or a modified version thereof is used as shown in FIG. Also good.
- Blocks 605 to 608 are performed to notify the HSS 122 of the MME change.
- the processing in blocks 605 to 608 is the same as the processing in blocks 407 to 410 in FIG.
- ⁇ Fourth Embodiment> examples of MME selection have been described.
- the technical idea described in the first to third embodiments is based on the selection of a user plane core network entity (eg, S-GW, P-GW, or both) that provides data transfer services for the UE 111. Can be applied.
- a user plane core network entity eg, S-GW, P-GW, or both
- the control device 151 performs selection of a user plane core network entity.
- FIG. 7 shows a configuration example of a public land mobile communication network (Public Land Mobile Network (PLMN)) 100 according to the present embodiment.
- the PLMN 100 includes an S-GW component 143 and a P-GW component 144 that are arranged in association with the eNB 112.
- the control device 751 executes selection of S-GW and / or P-GW that provides the data transfer service to the UE 111 or both.
- the control device 751 may be arranged in the UE 111 as shown in FIG.
- the control device 751 may be located in the EPC 120, for example in the MME device 121.
- the control device 751 may be arranged in the E-UTRAN 110, for example, the eNB 112.
- the control device 751 may be arranged in a control node (e.g., SDN controller, NFV controller, OSS, or EMS) arranged outside the PLMN 100.
- a control node e.g., SDN controller, NFV controller, OSS, or EMS
- FIG. 8 is a flowchart showing an example (processing 800) of user plane core network entity selection processing performed by the control device 751.
- the controller 751 determines the path cost (or management) between the UE 111 and the UE 111 based on at least one of the delay tolerance level of the UE 111, the frequency of control signaling of the UE 111, and the communication interval of the UE 111.
- a target core network entity for which mobility management of the UE 111 is to be performed is selected from among a plurality of candidate core network entities having different range widths.
- Controller 751 may communicate with E-UTRAN 110 and EPC 120 entities to detect multiple candidate core network entities.
- the control device 151 may receive a list of candidate core network entities from the serving MME (for example, the MME device 121) or the eNB 112 that is currently managing the mobility of the UE 111.
- the plurality of candidate core network entities include, for example, an S-GW component 143 associated with the eNB 112 and an S-GW 123 in the EPC 120.
- the plurality of candidate core network entities may include a P-GW component 144 associated with the eNB 112 and a P-GW 124 within the EPC 120.
- the S-GW component 143 and the P-GW component 144 associated with the eNB 112 generally have a lower path cost and a smaller management range than the S-GW 123 and the P-GW 124 arranged in the EPC 120, respectively.
- a specific example of the user plane core network / entity selection by the control device 751 is the same as the specific example of the MME selection by the control device 151 described in the first embodiment, and a description thereof will be omitted here.
- the controller 751 triggers a control procedure for transferring the data transfer service for the UE 111 to the target core network entity based on the core network entity selection in block 801.
- the controller 751 may send a change request message to a serving MME (eg, MME 121).
- the serving MME may initiate itself a procedure to change the user plane core network entity.
- a user plane core network entity that is to perform the data transfer service of the UE 111 based on one or more criteria (indicators, parameters) different from the mobility of the UE 111.
- FIG. 9 shows a configuration example of the control device 151.
- the control device 751 may also have the same configuration as in FIG.
- the control device 151 includes a network interface 1511, a processor 1512, and a memory 1513.
- the network interface 1511 is used to communicate with a network node or device (e.g., UE 111, eNB 112, MME device 121, HSS 122, and S-GW 123).
- the network interface 1511 may include, for example, a network interface card (NIC) compliant with IEEE 802.3 series.
- NIC network interface card
- the processor 1512 reads out and executes software (computer program) from the memory 1513, thereby performing the processing of the control device 151 related to the processing 200, 300, or 500 described in the above-described embodiment.
- the processor 1512 may be, for example, a microprocessor, a Micro Processing Unit (MPU), or a Central Processing Unit (CPU).
- the processor 1512 may include a plurality of processors.
- the memory 1513 is configured by a combination of a volatile memory and a nonvolatile memory.
- the volatile memory is, for example, Static Random Access Memory (SRAM), Dynamic RAM (DRAM), or a combination thereof.
- the nonvolatile memory is, for example, a mask Read Only Memory (MROM), Programmable ROM (PROM), flash memory, hard disk drive, or a combination thereof.
- the memory 1513 may include a storage arranged away from the processor 1512. In this case, the processor 1512 may access the memory 1513 via the network interface 1511 or an I / O interface not shown.
- the memory 1513 is used to store a software module group including the MME selection module 1514.
- the MME selection module 1514 includes a group of instructions and data for executing the processing of the control device 151 related to the processing 200, 300, or 500 described in the above embodiment.
- the processor 1512 can perform the processing of the control device 151 described in the above-described embodiment by reading a software module group including the MME selection module 1514 from the memory 1513 and executing the software module group.
- each of the processors included in the control device 151 and the control device 751 includes a group of instructions for causing a computer to execute the algorithm described with reference to the drawings. Alternatively, a plurality of programs are executed. The program can be stored and supplied to a computer using various types of non-transitory computer readable media. Non-transitory computer readable media include various types of tangible storage media (tangible storage medium).
- non-transitory computer-readable media are magnetic recording media (eg flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (eg magneto-optical discs), Compact Disc Read Only Memory (CD-ROM), CD-ROM R, CD-R / W, semiconductor memory (for example, mask ROM, Programmable ROM (PROM), Erasable PROM (EPROM), flash ROM, Random Access Memory (RAM)).
- the program may also be supplied to the computer by various types of temporary computer-readable media. Examples of transitory computer readable media include electrical signals, optical signals, and electromagnetic waves.
- the temporary computer-readable medium can supply the program to the computer via a wired communication path such as an electric wire and an optical fiber, or a wireless communication path.
- At least one of the MME device 121, the MME component 141, and the MME component 142 is an MME (virtualized MME) virtualized using a server virtualization technology and a network virtualization technology. Good.
- at least one of the S-GW 123, the P-GW 124, the S-GW component 143, and the P-GW component 144 is an S-virtualized using a server virtualization technology and a network virtualization technology.
- GW (or P-GW) may be used.
- the virtualized MME, S-GW, and P-GW may be realized as a virtual machine set in a server pool or a virtual router set in a physical switch group.
- UMTS Universal Mobile Telecommunications System
- HRPD High Rate Packet Data
- GSM Global System for Mobile Communications
- GPRS General packet radio service
- Evolved Universal Terrestrial Radio Access Network E-UTRAN
- UE User Equipment
- eNB eNodeB
- EPC Evolved Packet Core
- MME Mobility Management Entity
- HSS Home Subscriber Server
- S-GW Serving Gateway
- P-GW Packet Data Network Gateway
- PDN Packet Data Network
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
図1は、本実施形態に係る公衆地上移動通信ネットワーク(Public Land Mobile Network (PLMN))100の構成例を示している。PLMN100は、通信サービス、例えば音声通信若しくはパケットデータ通信又はこれら両方を無線端末(User Equipment (UE))111に提供する。PLMN100は、無線アクセスネットワーク(Evolved Universal Terrestrial Radio Access Network (E-UTRAN))110及びコアネットワーク(Evolved Packet Core(EPC))120を含む。E-UTRAN110は、UE111と無線通信する基地局(eNB)112を含む。EPC120は、Mobility Management Entity(MME)装置121、Home Subscriber Server(HSS)122、Serving Gateway(S-GW)123、及びPDN Gateway(P-GW)124を含む。
本実施形態では、第1の実施形態で説明されたMME変更手順の具体例が説明される。本実施形態に係る移動通信ネットワークの構成例は、第1の実施形態に関して説明された図1と同様とすればよい。図3は、本実施形態に係るMME変更手順の一例(処理300)を示すシーケンス図である。図3の例では、制御装置151がUE111に配置されている。
本実施形態では、第1の実施形態で説明されたMME変更手順の具体例が説明される。本実施形態に係る移動通信ネットワークの構成例は、第1の実施形態に関して説明された図1と同様とすればよい。図5は、本実施形態に係るMME変更手順の一例(処理500)を示すシーケンス図である。図5の例では、制御装置151がMME装置121に配置されている。
第1~第3の実施形態では、MME選択の例について説明した。第1~第3の実施形態で説明された技術思想は、UE111のためにデータ転送サービスを提供するユーザープレーンのコアネットワーク・エンティティ(例えば、S-GW、P-GW又はこれら両方)の選択に応用することができる。本実施形態では、ユーザープレーンのコアネットワーク・エンティティの選択を制御装置151が行う例について説明する。
上述の複数の実施形態は、各々独立に実施されてもよいし、適宜組み合わせて実施されてもよい。
111 User Equipment (UE)
112 eNodeB (eNB)
120 Evolved Packet Core (EPC)
121 Mobility Management Entity (MME) 装置
122 Home Subscriber Server (HSS)
123 Serving Gateway (S-GW)
124 Packet Data Network Gateway (P-GW)
130 Packet Data Network (PDN)
141 MMEコンポーネント
142 MMEコンポーネント
143 S-GWコンポーネント
144 P-GWコンポーネント
143 S-GWコンポーネント
144 P-GWコンポーネント
151 制御装置
751 制御装置
1512 プロセッサ
1513 メモリ
Claims (19)
- メモリと、
前記メモリに結合されたプロセッサと、
を備え、
前記プロセッサは、無線端末の遅延耐性レベル、前記無線端末の制御シグナリングの頻度、及び前記無線端末の通信間隔のうち少なくとも1つに基づいて、前記無線端末との間の経路コスト又は管理範囲の広さが異なる複数の候補コアネットワーク・エンティティの中から前記無線端末のためにモビリティ管理サービス又はデータ転送サービスを提供するべきターゲット・コアネットワーク・エンティティを選択するよう動作する、
制御装置。 - 前記複数の候補コアネットワーク・エンティティは、コアネットワークノードに関連付けて配置された第1のコアネットワーク・エンティティと、無線アクセスネットワークノードに関連付けて配置されており且つ前記第1のコアネットワーク・エンティティよりも前記無線端末との間の経路コストが小さい第2のコアネットワーク・エンティティを含む、
請求項1に記載の制御装置。 - 前記プロセッサは、前記遅延耐性レベルが第1のレベルであるときに前記第1のコアネットワーク・エンティティを前記ターゲット・コアネットワーク・エンティティとして選択し、前記遅延耐性レベルが前記第1のレベルよりもネットワーク遅延を許容しないことを示す第2のレベルであるときに前記第2のコアネットワーク・エンティティを前記ターゲット・コアネットワーク・エンティティとして選択する、
請求項2に記載の制御装置。 - 前記プロセッサは、前記無線端末と前記第1のコアネットワーク・エンティティの間の通信に関する遅延時間又は応答時間が前記遅延耐性レベルに基づく閾値を超える場合に、前記第2のコアネットワーク・エンティティを前記ターゲット・コアネットワーク・エンティティとして選択する、
請求項2に記載の制御装置。 - 前記プロセッサは、前記制御シグナリングの頻度が第1の値であるときに前記第1のコアネットワーク・エンティティを前記ターゲット・コアネットワーク・エンティティとして選択し、前記制御シグナリングの頻度が前記第1の値よりも大きい第2の値であるときに前記第2のコアネットワーク・エンティティを前記ターゲット・コアネットワーク・エンティティとして選択する、
請求項2に記載の制御装置。 - 前記プロセッサは、前記通信間隔が第1の値であるときに前記第1のコアネットワーク・エンティティを前記ターゲット・コアネットワーク・エンティティとして選択し、前記通信間隔が前記第1の値よりも短いことを示す第2の値であるときに前記第2のコアネットワーク・エンティティを前記ターゲット・コアネットワーク・エンティティとして選択する、
請求項2に記載の制御装置。 - 前記コアネットワーク・エンティティは、モビリティ管理サービスを提供するmobility management entity(MME)である、
請求項1~6のいずれか1項に記載の制御装置。 - 前記コアネットワーク・エンティティは、データ転送サービスを提供するServing Gateway(S-GW)又はPacket Data Network Gateway(P-GW)である、
請求項1~6のいずれか1項に記載の制御装置。 - 前記制御装置は、前記無線端末に配置される、
請求項1~8のいずれか1項に記載の制御装置。 - 前記制御装置は、コアネットワークに配置される、
請求項1~8のいずれか1項に記載の制御装置。 - 無線端末の遅延耐性レベル、前記無線端末の制御シグナリングの頻度、及び前記無線端末の通信間隔のうち少なくとも1つに基づいて、前記無線端末との間の経路コスト又は管理範囲の広さが異なる複数の候補コアネットワーク・エンティティの中から前記無線端末のためにモビリティ管理サービス又はデータ転送サービスを提供するべきターゲット・コアネットワーク・エンティティを選択することを備える、
コアネットワーク・エンティティの選択方法。 - 前記複数の候補コアネットワーク・エンティティは、コアネットワークノードに関連付けて配置された第1のコアネットワーク・エンティティと、無線アクセスネットワークノードに関連付けて配置されており且つ前記第1のコアネットワーク・エンティティよりも前記無線端末との間の経路コストが小さい第2のコアネットワーク・エンティティを含む、
請求項11に記載の方法。 - 前記選択することは、前記遅延耐性レベルが第1のレベルであるときに前記第1のコアネットワーク・エンティティを前記ターゲット・コアネットワーク・エンティティとして選択し、前記遅延耐性レベルが前記第1のレベルよりもネットワーク遅延を許容しないことを示す第2のレベルであるとき前記第2のコアネットワーク・エンティティを前記ターゲット・コアネットワーク・エンティティとして選択することを含む、
請求項12に記載の方法。 - 前記選択することは、前記無線端末と前記第1のコアネットワーク・エンティティの間の通信に関する遅延時間又は応答時間が前記遅延耐性レベルに基づく閾値を超える場合に、前記第2のコアネットワーク・エンティティを前記ターゲット・コアネットワーク・エンティティとして選択することを含む、
請求項12に記載の方法。 - 前記選択することは、前記制御シグナリングの頻度が第1の値であるときに前記第1のコアネットワーク・エンティティを前記ターゲット・コアネットワーク・エンティティとして選択し、前記制御シグナリングの頻度が前記第1の値よりも大きい第2の値であるときに前記第2のコアネットワーク・エンティティを前記ターゲット・コアネットワーク・エンティティとして選択することを含む、
請求項12に記載の方法。 - 前記選択することは、前記通信間隔が第1の値であるときに前記第1のコアネットワーク・エンティティを前記ターゲット・コアネットワーク・エンティティとして選択し、前記通信間隔が前記第1の値よりも短いことを示す第2の値であるときに前記第2のコアネットワーク・エンティティを前記ターゲット・コアネットワーク・エンティティとして選択することを含む、
請求項12に記載の方法。 - 前記コアネットワーク・エンティティは、モビリティ管理サービスを提供するmobility management entity(MME)である、
請求項11~16のいずれか1項に記載の方法。 - 前記コアネットワーク・エンティティは、データ転送サービスを提供するServing Gateway(S-GW)又はPacket Data Network Gateway(P-GW)である、
請求項11~16のいずれか1項に記載の方法。 - 請求項11~18のいずれか1項に記載の方法をコンピュータに行わせるためのプログラムを格納した非一時的なコンピュータ可読媒体。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP15852097.3A EP3211939A4 (en) | 2014-10-24 | 2015-08-31 | Control device and method therefor |
US15/519,389 US10085191B2 (en) | 2014-10-24 | 2015-08-31 | Control device and method therefor |
JP2016555055A JP6561995B2 (ja) | 2014-10-24 | 2015-08-31 | 制御装置及びその方法 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2014-217630 | 2014-10-24 | ||
JP2014217630 | 2014-10-24 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016063449A1 true WO2016063449A1 (ja) | 2016-04-28 |
Family
ID=55760512
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2015/004404 WO2016063449A1 (ja) | 2014-10-24 | 2015-08-31 | 制御装置及びその方法 |
Country Status (4)
Country | Link |
---|---|
US (1) | US10085191B2 (ja) |
EP (1) | EP3211939A4 (ja) |
JP (1) | JP6561995B2 (ja) |
WO (1) | WO2016063449A1 (ja) |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10805217B2 (en) * | 2015-11-10 | 2020-10-13 | At&T Intellectual Property I, L.P. | Control plane device selection for broadcast session exchange |
US11245633B2 (en) * | 2016-08-18 | 2022-02-08 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and wireless device for handling transmission of data |
US11533777B2 (en) | 2018-06-29 | 2022-12-20 | At&T Intellectual Property I, L.P. | Cell site architecture that supports 5G and legacy protocols |
US10728826B2 (en) * | 2018-07-02 | 2020-07-28 | At&T Intellectual Property I, L.P. | Cell site routing based on latency |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2010086014A1 (en) * | 2009-01-27 | 2010-08-05 | Nokia Siemens Networks Oy | Method and device for data processing in an access point supporting local breakout |
JP2013533711A (ja) * | 2010-08-09 | 2013-08-22 | エヌイーシー ヨーロッパ リミテッド | クラスタ化フェムトセルネットワークでローカルモビリティ管理を行う装置および方法 |
US20140169269A1 (en) * | 2012-12-19 | 2014-06-19 | Cisco Technology, Inc. | SYSTEMS, METHODS AND MEDIA FOR MOBILE MANAGEMENT ENTITY (MME) SELECTION BY EVOLVED NODE B (eNodeB) |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4161782B2 (ja) | 2002-04-18 | 2008-10-08 | 松下電器産業株式会社 | モバイルノードおよび移動通信方法 |
EP2424322A3 (en) * | 2005-04-26 | 2012-06-13 | Vodafone Group PLC | Telecommunications networks |
US7701857B2 (en) * | 2006-06-07 | 2010-04-20 | Genband Inc. | Method, system, and computer-readable medium for resource-based route selection |
CN101272614B (zh) * | 2007-03-20 | 2010-12-08 | 华为技术有限公司 | 一种选择网络设备的方法和系统及装置 |
US9025522B2 (en) | 2012-05-11 | 2015-05-05 | Verizon Patent And Licensing Inc. | Providing network connectivity based on device mobility |
KR101769257B1 (ko) * | 2013-06-21 | 2017-08-17 | 후아웨이 테크놀러지 컴퍼니 리미티드 | 이동성 관리 엔티티를 선택하기 위한 방법, 장치, 및 시스템 |
-
2015
- 2015-08-31 JP JP2016555055A patent/JP6561995B2/ja active Active
- 2015-08-31 EP EP15852097.3A patent/EP3211939A4/en not_active Withdrawn
- 2015-08-31 WO PCT/JP2015/004404 patent/WO2016063449A1/ja active Application Filing
- 2015-08-31 US US15/519,389 patent/US10085191B2/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2010086014A1 (en) * | 2009-01-27 | 2010-08-05 | Nokia Siemens Networks Oy | Method and device for data processing in an access point supporting local breakout |
JP2013533711A (ja) * | 2010-08-09 | 2013-08-22 | エヌイーシー ヨーロッパ リミテッド | クラスタ化フェムトセルネットワークでローカルモビリティ管理を行う装置および方法 |
US20140169269A1 (en) * | 2012-12-19 | 2014-06-19 | Cisco Technology, Inc. | SYSTEMS, METHODS AND MEDIA FOR MOBILE MANAGEMENT ENTITY (MME) SELECTION BY EVOLVED NODE B (eNodeB) |
Also Published As
Publication number | Publication date |
---|---|
JP6561995B2 (ja) | 2019-08-21 |
US10085191B2 (en) | 2018-09-25 |
EP3211939A1 (en) | 2017-08-30 |
JPWO2016063449A1 (ja) | 2017-08-10 |
EP3211939A4 (en) | 2018-06-27 |
US20170245187A1 (en) | 2017-08-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11122413B2 (en) | Method and apparatus for efficiently transmitting small amounts of data in wireless communication systems | |
JP5406220B2 (ja) | ユーザ装備の位置情報を更新するための方法 | |
US10051512B2 (en) | Method and apparatus for controlling traffic in wireless communication system | |
US9986496B2 (en) | Method in a network node of a wireless communications network | |
JP6520044B2 (ja) | 無線端末、ネットワーク装置、及びこれらの方法 | |
US9480045B2 (en) | Networks and methods for paging message control | |
EP3461071A1 (en) | Communication control method, and related network element | |
WO2016035230A1 (ja) | モビリティ管理及びベアラ管理を移転するための方法及び装置 | |
JP2011514068A5 (ja) | ||
KR20150066562A (ko) | 무선 액세스 네트워크 장치, 코어 네트워크 장치, 이동 단말, 이들의 방법, 및 컴퓨터 판독가능 매체 | |
US11937168B2 (en) | Method and apparatus for session management | |
JP6561995B2 (ja) | 制御装置及びその方法 | |
US20170150395A1 (en) | Mobility management of user equipment | |
US20190045410A1 (en) | Packet data network gateway handoff | |
US20180124087A1 (en) | Method, apparatus, and system for detecting terminal device anomaly | |
KR20160002150A (ko) | 무선 통신 시스템에서 서비스 연속성을 제어하는 방법 및 장치 | |
CN112312585B (zh) | 对用户设备进行接入控制的方法,网络系统及相关设备 | |
US10009870B2 (en) | Method for reporting location information of user equipment, and apparatus | |
WO2012095057A2 (zh) | 拥塞控制方法及设备、系统 | |
JP2021520686A (ja) | ユーザプレーンパスについての障害の検出とハンドリングの改善 | |
KR20140134998A (ko) | 통신 시스템에서 음성 서비스 성능 향상을 위한 방법 및 장치 | |
US10327274B2 (en) | Mobile device anchoring and connectivity across multiple mobile network technologies | |
JP6383659B2 (ja) | PMIPv6MAGの復旧 | |
WO2017166291A1 (zh) | 一种通信方法、终端、基站和移动性管理设备 | |
WO2019140560A1 (zh) | 一种切换方法及装置、计算机存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 15852097 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2016555055 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15519389 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REEP | Request for entry into the european phase |
Ref document number: 2015852097 Country of ref document: EP |