WO2014041805A1 - Système et procédé de communications mobile, dispositif de passerelle et station de base - Google Patents

Système et procédé de communications mobile, dispositif de passerelle et station de base Download PDF

Info

Publication number
WO2014041805A1
WO2014041805A1 PCT/JP2013/005397 JP2013005397W WO2014041805A1 WO 2014041805 A1 WO2014041805 A1 WO 2014041805A1 JP 2013005397 W JP2013005397 W JP 2013005397W WO 2014041805 A1 WO2014041805 A1 WO 2014041805A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
bearer
transmits
gateway device
transmitted
Prior art date
Application number
PCT/JP2013/005397
Other languages
English (en)
Japanese (ja)
Inventor
創 前佛
田村　利之
Original Assignee
日本電気株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 日本電気株式会社 filed Critical 日本電気株式会社
Priority to EP13837842.7A priority Critical patent/EP2897392A4/fr
Priority to US14/426,615 priority patent/US20150237458A1/en
Priority to KR1020157005702A priority patent/KR101654491B1/ko
Priority to JP2014535381A priority patent/JP5900629B2/ja
Priority to CN201380046603.9A priority patent/CN104604266A/zh
Priority to IN1108DEN2015 priority patent/IN2015DN01108A/en
Publication of WO2014041805A1 publication Critical patent/WO2014041805A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0215—Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/24—Interfaces between hierarchically similar devices between backbone network devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
    • 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
    • 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/16—Gateway arrangements

Definitions

  • the present invention relates to a mobile communication system, a data communication method, a gateway device, and a base station, and more particularly to a mobile communication system accommodating an MTC device and a data communication method in the mobile communication system.
  • the GTP (GPRS Tunneling Protocol) or PMIP (Proxy Mobile IP) protocol is applied to the current mobile phone system network defined by 3GPP (3rd Generation Partnership Project) standardization organizations. These protocols provide a user with a transmission path by securing resources necessary for realizing communication requested by the user. Necessary resources need to be prepared according to the number of users and the number of connections required from each user. These protocols are composed of a control signal (Control Plane or C-Plane) for performing communication control and a user data signal (User Plane or U-Plane) for transmitting user data. Also, a plurality of transmission paths (GTP tunnel in the case of GTP, IP tunnel in the case of PMIP) used for user data signal transmission can be secured according to a user request.
  • GTP tunnel in the case of GTP
  • MTC Machine Type Communication
  • MTC device As another feature of a device used for MTC (hereinafter referred to as an MTC device), it is possible to avoid communication during a busy time when a mobile phone system is frequently used, and to realize communication in a relatively free night. Taking advantage of such features, it is assumed that mobile phone operators accommodate MTC devices several hundred times larger than ordinary mobile terminals in a mobile phone system.
  • the node device in the mobile phone system secures a user data transmission path for the MTC.
  • This user data transmission path reservation is intended to secure resources necessary for the user data transmission path for the MTC device by the node device in the mobile phone system.
  • Non-Patent Document 1 discloses a procedure for securing resources necessary for a user data transmission path in a network defined by 3GPP.
  • An object of the present invention is to provide a mobile communication system, a data communication method, a gateway device, and a base station that can reduce resource load in a mobile phone system in order to solve such a problem.
  • a mobile communication system includes a first gateway device that transmits user data to and from a base station, and a second gateway device that transmits the user data to and from an external network.
  • the first gateway device and the second gateway device transmit autonomously from the terminal device via the base station between the first gateway device and the second gateway device.
  • the small amount of data to be transmitted is transmitted using communication resources for transmitting control signals instead of communication resources for transmitting user data.
  • a data communication method includes a first gateway device that transmits user data to and from a base station, and a second gateway device that transmits the user data to and from an external network; A small amount of data autonomously transmitted from the terminal device via the base station between the first gateway device and the second gateway device, and user data Transmission is performed using communication resources for transmitting control signals instead of communication resources for transmission.
  • a mobile communication system a data communication method, a gateway device, and a base station that can reduce resource load in a mobile phone system.
  • FIG. 1 is a configuration diagram of a mobile communication system according to a first embodiment.
  • 1 is a configuration diagram of a mobile communication system according to a first embodiment.
  • 1 is a configuration diagram of a mobile communication system according to a first embodiment.
  • FIG. 3 is a configuration diagram of a GTP-C message according to the first exemplary embodiment. It is a figure explaining the flow of the ATTACH process concerning Embodiment 1.
  • FIG. It is a figure explaining the flow of the process at the time of TAU execution concerning Embodiment 1.
  • FIG. It is a figure explaining the flow of a process in the case of transmitting small amount data from UE concerning Embodiment 1.
  • FIG. FIG. 6 is a diagram for explaining a flow of a handover process according to the first embodiment.
  • FIG. 6 is a diagram for explaining a flow of a handover process according to the first embodiment. It is a figure explaining the flow of a process at the time of receiving small amount data in PGW concerning Embodiment 1.
  • FIG. It is a figure explaining the flow of a process in the case of transmitting small amount data from UE concerning Embodiment 1.
  • FIG. It is a figure explaining the flow of a process in the case of transmitting the large sized data concerning Embodiment 1.
  • FIG. It is a figure explaining the flow of a process in the case of transmitting the large sized data concerning Embodiment 1.
  • FIG. It is a figure explaining the flow of a process in the case of deleting the exclusive bearer concerning Embodiment 1.
  • FIG. 4 is a configuration diagram of a mobile communication system according to a third embodiment.
  • FIG. 4 is a configuration diagram of a mobile communication system according to a third embodiment.
  • FIG. 4 is a configuration diagram of a mobile communication system according to a third embodiment.
  • FIG. 4 is a configuration diagram of a mobile communication system according to a third embodiment.
  • FIG. 12 is a diagram for explaining the flow of ATTACH processing according to the third embodiment. It is a figure explaining the flow of a process in the case of transmitting small amount data from UE concerning Embodiment 3.
  • FIG. FIG. 10 is a diagram for explaining a flow of processing when executing RAU according to the third embodiment; It is a figure explaining the flow of a process when RNC and SGSN concerning Embodiment 3 are changed. It is a figure explaining the flow of a process when RNC and SGSN concerning Embodiment 3 are changed. It is a figure explaining the flow of a process when RNC and SGSN concerning Embodiment 3 are changed. It is a figure explaining the flow of a process at the time of receiving small amount data in GGSN concerning Embodiment 3.
  • FIG. It is a figure explaining the flow of a process in the case of transmitting small amount data from UE concerning Embodiment 3.
  • FIG. It is a figure explaining the flow of a process in the case of transmitting / receiving the large data concerning Embodiment 3.
  • FIG. It is a figure explaining the flow of a process in the case of transmitting / receiving the large data concerning Embodiment 3.
  • FIG. It is a figure explaining the flow of a process in the case of deleting the dedicated bearer concerning Embodiment 3.
  • FIG. It is a figure explaining the flow of a process in the case of deleting the dedicated bearer concerning Embodiment 3.
  • FIG. It is a figure explaining the flow of the ATTACH process concerning Embodiment 4.
  • FIG. 10 is a diagram for explaining the flow of handover processing according to the fourth embodiment;
  • FIG. 10 is a diagram for explaining the flow of handover processing according to the fourth embodiment;
  • It is a figure explaining the flow of a process at the time of receiving small amount data in GGSN concerning Embodiment 4.
  • FIG. It is a figure explaining the flow of a process in the case of transmitting small amount data from UE concerning Embodiment 4.
  • FIG. 1 It is a figure explaining the flow of a process in the case of transmitting / receiving the large data concerning Embodiment 4.
  • FIG. It is a figure explaining the flow of a process in the case of transmitting / receiving the large data concerning Embodiment 4.
  • FIG. It is a figure explaining the flow of a process in the case of deleting the dedicated bearer concerning Embodiment 4.
  • FIG. It is a figure explaining the flow of a process in the case of deleting the dedicated bearer concerning Embodiment 4.
  • FIG. 1 It is a figure explaining the flow of a process in the case of deleting the dedicated bearer concerning Embodiment 4.
  • FIG. 1 shows an example in which LTE (Long Term Evolution) defined in 3GPP is used for an access network.
  • the mobile communication system shown in this figure has UE (User Equipment) 10, eNodeB (enhanced Node B) 20, MME (Mobility Management Entity) 30, SGW (Serving Gateway) 40 and PGW (Packet Data Network Gateway) 50. ing.
  • UE User Equipment
  • eNodeB enhanced Node B
  • MME Mobility Management Entity
  • SGW Serving Gateway
  • PGW Packet Data Network Gateway
  • the UE 10 is a communication device or mobile station that performs wireless communication, and may be, for example, a mobile phone or a smartphone terminal. Further, the UE 10 may be an MTC device (machine type terminal device).
  • the eNodeB 20 is a base station that performs radio communication with a mobile station. UE10 and eNodeB20 perform radio
  • the SGW 40 is used as a data relay device that transmits and receives user data between the eNodeB 20 and the PGW 50.
  • the user data is packet data including voice data transmitted from the UE 10.
  • the PGW 50 is used as a gateway device that transmits and receives user data to and from an external network.
  • the external network is a network different from the network having the eNodeB 20, the MME 30, the SGW 40, and the PGW 50.
  • the external network is, for example, a network managed by a provider different from the provider that manages the eNodeB 20, the MME 30, the SGW 40, and the PGW 50.
  • the external network is not limited to the above, and may be the same network as the network having the eNodeB 20, the MME 30, the SGW 40, and the PGW 50 when the mobile phone operators are the same.
  • the MME 30 is a device that performs call control processing.
  • the MME 30 designates the SGW that is the destination of the user data transmitted from the eNodeB 20 and notifies the designated SGW to the eNodeB 20.
  • the MME 30 transmits and receives control signals to and from the eNodeB 20, and also transmits and receives control signals to and from the SGW 40.
  • Control signals between the UE 10 and the eNodeB 20 are transmitted and received using a protocol defined as RRC (Radio Resource Control). Furthermore, the user data in UE10 and eNodeB20 are transmitted / received using Traffic channel.
  • RRC Radio Resource Control
  • User data between the eNodeB 20 and the SGW 40 and user data between the SGW 40 and the PGW 50 are transmitted and received using a protocol defined as GTP-U.
  • Control signals between the eNodeB 20 and the MME 30 are transmitted and received using a protocol defined as S1AP (S1 Application Protocol).
  • S1AP S1 Application Protocol
  • a control signal between the MME 30 and the SGW 40 and a control signal between the SGW 40 and the PGW 50 are transmitted and received using a protocol defined as GTP-C.
  • the small amount of data is, for example, data transmitted from the MTC device. Specific examples include measured values of sensors and meters, and sales of vending machines. Furthermore, the small amount of data may be user data that is autonomously transmitted and received between communication devices without a user operation. Further, the small amount of data is defined as SmallSData in 3GPP (3GPP TS 22.368 V11.5.0 "Service requirements for Machine-Type Communications (MTC)", clause 7.2.5, 2012-06)
  • the communication device is, for example, a vending machine or a sensor terminal.
  • MTC Machine Type Communication
  • the communication resource is, for example, a parameter set for transmitting / receiving user data or a control signal, a memory necessary for transmitting / receiving user data or a control signal on a memory or a communication path, and the like.
  • FIG. 2 shows that a small amount of data is transmitted and received between the SGW 40 and the PGW 50 using a protocol defined as GTP-C.
  • the SGW 40 transmits a small amount of data with the UE 10 transmitted from the eNodeB 20 via GTP-U to the PGW 50 via GTP-C.
  • the PGW 50 transmits the small amount of data to the SGW 40 via GTP-C.
  • GTP-C a protocol defined as GTP-C.
  • FIG. 3 shows an example in which a small amount of data transmitted / received using the GTP-U is transmitted between the eNodeB 20 and the SGW 40 using a protocol for transmitting / receiving a control signal.
  • the eNodeB 20 transmits the small amount of data transmitted via the Traffic channel to the MME 30 via the S1AP.
  • the MME 30 transmits a small amount of data transmitted from the eNodeB 20 to the SGW 40 via GTP-C.
  • the SGW 40 transmits the small amount of data to the MME 30 via GTP-C.
  • the MME 30 transmits the received small amount of data to the eNodeB 20 via the S1AP. Since the SGW 40 and the PGW 50 are the same as those in FIG.
  • a GTP-C message transmitted via GTP-C has a GTP-C message header and IE (Information Element) AC. Further, the GTP-C message defines UP-PDU (User Plane-Protocol Date Unit) IE in order to transmit a small amount of data. Similarly to the GTP-C message, the UP-PDU IE is defined for the S1AP message used between the eNodeB 20 and the MME 30.
  • UP-PDU User Plane-Protocol Date Unit
  • user data is transmitted and received at the eNodeB 20 by transmitting and receiving a small amount of data between the SGW 40 and the PGW 50 and also between the eNodeB 20 and the SGW 40 using the S1AP and GTP-C used for transmitting the control signal. Therefore, it is not necessary to secure communication resources for use, and the resource load can be reduced.
  • the processing operations of the UE 10 and the eNodeB 20 are the same as those of the UE 10 and the eNodeB 20 of FIG. Therefore, it is not necessary to mount a new function in the UE 10 and the eNodeB 20 in order to realize the present invention.
  • the processing operation of the UE 10 is the same as that of the UE 10 of FIG. Therefore, the UE 10 does not need to be equipped with a new function in order to realize the present invention.
  • the new function is, for example, a function of receiving a small amount of data transmitted via a user data bearer and transmitting the received small amount of data via a control signal bearer.
  • ATTACH UE location registration
  • the UE 10 transmits an ATTACH signal to the MME 30 (S1).
  • an authentication operation and security setting of the UE 10 are performed between the UE 10 and the HSS (Home Subscriber Server) (S2).
  • the MME 30 transmits an Update Location request signal to the HSS (S3).
  • the HSS transmits an Update Location Ack signal to the MME 30.
  • the Update-Location-Ack signal includes pseudo-U / Size-attribution set for each APN.
  • the pseudo-U / Size-attribution may be set in the IMSI unit or the IMEISV unit in addition to the APN unit.
  • the HSS manages pseudo-U / Size attribution as subscriber data associated with the UE 10. Therefore, the HSS can include pseudo-U / Size / attribution in the Update Location Ack signal that is a response signal to the Update Location request signal transmitted from the UE 10.
  • the pseudo-U bearer is a GTP-U bearer that is set in a pseudo or virtual manner.
  • the bearer indicates a communication path between devices.
  • the bearer may be a communication resource reserved for setting a communication path between devices. Since the pseudo-U bearer is a bearer that is set in a pseudo or virtual manner, communication resources are not secured, or a minimum necessary communication resource is secured. That is, when the UE 10 executes the ATTACH process, a communication resource securing process is usually executed to set up a GTP-U bearer.
  • the processing sequence between the devices is not changed, and wasteful communication is performed. It is possible to prevent resources from being reserved. That is, when a small amount of data is transmitted using a GTP-C bearer, a process for setting a pseudo-U bearer is performed instead of executing a process for setting a GTP-U bearer. In this manner, the communication device can be accommodated in the mobile communication system without allocating communication resources for setting the GTP-U bearer to the communication device that transmits a small amount of data.
  • pseudo-U / Size attribution also defines information on the size defined as a small amount of data. Data that exceeds the defined size is not treated as small data. That is, data less than the defined size is treated as a small amount of data.
  • the MME 30 Upon receiving the pseudo-U / Size attribution, the MME 30 transmits a Create Session request signal including a PU (pseudo-U) flag to the SGW 40. Furthermore, the SGW 40 transmits a Create Session request signal including PU (pseudo-U) flag to the PGW 50 (S5).
  • the PU flag is a parameter for notifying that a pseudo-U bearer is set instead of a normal GTP-U bearer between the SGW 40 and the PGW 50. Further, the PU flag may be a parameter for notifying that a pseudo-U bearer is set instead of a normal GTP-U bearer between the eNodeB 20 and the SGW 40.
  • the PGW 50 transmits a Create Session response signal including PU status1 to the SGW 40. Further, the SGW 40 transmits a Create Session response signal including PU status1 to the MME 30 (S6).
  • PU status1 is a parameter indicating that a pseudo-U bearer is set between the SGW 40 and the PGW 50.
  • a Create Session response signal is transmitted from the PGW 50 to the SGW 40, and further from the SGW 40 to the MME 30, and the PU status1 is held in the SGW 40, whereby a pseudo-U bearer (hereinafter referred to as Pseudo-U treatment (1) between the SGW 40 and the PGW 50. )) Is completed (S7).
  • the MME 30 transmits an Initial Context Setup Request / Attach Accept signal including the PU flag to the eNodeB 20 (S8).
  • the MME 30 notifies the eNodeB 20 and the SGW 40 that a pseudo-U bearer is set instead of the GTP-U bearer.
  • the eNodeB 20 transmits an RRC Connection Reconfiguration signal to the UE 10 (S9).
  • the UE 10 transmits an RRC Connection Reconfiguration Complete signal to the eNodeB 20 (S10).
  • the eNodeB 20 transmits an Initial Context Setup Response signal including the PU status 2 to the MME 30 (S11).
  • PU status2 is a parameter indicating that a pseudo-U bearer is set between the eNodeB 20 and the SGW 40.
  • Pseudo-U treatment (2) the setting of the pseudo-U bearer (hereinafter referred to as Pseudo-U treatment (2)) is completed between the eNodeB 20 and the SGW 40 (S12).
  • the MME 30 transmits a Modify bearer request signal including PU flag and PUSGstatus2 to the SGW 40 (S13). Thereby, MME30 notifies the state of Pseudo-U treatment (2) to SGW40.
  • the SGW 40 transmits a Modify bearer response signal to the MME 30 (S14).
  • the SGW 40 holds PU status1 and PU status2. Therefore, the SGW 40 can determine to which bearer the received small amount of data is set and transmitted. For example, the SGW 40 is in a state where it holds a PU status2 indicating that a pseudo-U bearer is set with the eNodeB 20. At this time, when receiving a small amount of data from the PGW 50, the SGW 40 transmits the small amount of data to the MME 30 via the GTP-C bearer. For example, when the SGW 40 does not hold the PU status2, the SGW 40 transmits a small amount of data received from the PGW 50 to the eNodeB 20 via the GTP-U bearer. The case where the SGW 40 does not hold the PU status2 occurs, for example, when the eNodeB 20 and the SGW 40 do not have a function of setting a pseudo-U bearer between the eNodeB 20 and the SGW 40.
  • Tracking Area is location information of the UE 10 managed on the mobile communication network, for example, on the core network.
  • the Tracking area (TA) may be an area composed of a plurality of cells.
  • the TAU is a process executed when the TA where the UE 10 is located is changed.
  • the UE 10 transmits a TAU request signal to a new MME 30 (New MME) that manages the UE 10 whose TA has been changed (S21).
  • the New MME transmits a Context Request signal to the MME 30 (Old MME) that has been managing the UE 10 before the TA is changed (S22).
  • the Old MME transmits a Context Response signal to the New MME (S23).
  • the Context Response signal includes PU flag.
  • the Old MME notifies the New MME that the pseudo-U bearer is set instead of GTP-U for the UE10.
  • an authentication operation and security setting of the UE 10 are performed between the UE 10 and the HSS (Home Subscriber Server) (S24).
  • the New MME transmits a Context Request Ack signal to the Old MME (S25).
  • the New MME transmits a Create Session ⁇ request signal including the PU flag to the SGW 40 (New SGW) newly allocated to transmit a small amount of data transmitted from the UE 10 when the TA is changed (S26). ).
  • the PGW 50 transmits a Modify bearer response signal including PU status1 to the New SGW (S28).
  • the New SGW transmits a Create Session ⁇ response signal including the PU status 1 to the New MME (S29). Accordingly, Pseudo-U treatment (1) is set between New N SGW and PGW 50 (S30).
  • the New MME transmits an Update Location request signal to the HSS (S31).
  • the HSS transmits an Update Location Ack signal to the New MME.
  • the Update Location Ack signal includes pseudo-U / Size attribution set for each APN (S32).
  • the pseudo-U / Size-attribution may be set in the IMSI unit or the IMEISV unit in addition to the APN unit.
  • the New MME transmits a TAU accept signal to the UE 10 (S33).
  • the UE 10 transmits a PDN Connectivity Request (APN) signal to the MME 30 (S41).
  • the MME 30 transmits an Initial Context Setup Request signal including the PU flag to the eNodeB 20 (S42). Since the processing in steps S43 to S48 is the same as that in steps S9 to S14 in FIG. 5, detailed description thereof is omitted.
  • the handover source eNodeB 20 (Old eNB) transmits a Handover required signal to the MME 30 (Old MME) that manages the Old eNB (S51).
  • the Old MME transmits a Forward relocation request signal to the MME 30 (New MME) that manages the handover target eNodeB 20 (New eNB) (S52).
  • the Forward / relocation / request signal includes PU / flag.
  • the New MME transmits a Create Session request signal to the New SGW connected to the New eNB (S53).
  • the Create Session request signal includes PU flag.
  • the New SGW transmits a Create Session response signal to the New MME (S54).
  • the New MME transmits a Handover request signal including the PU flag to the New eNB (S55).
  • the New eNB transmits a Handover request ack signal including PU status2 to the New MME (S56).
  • Pseudo-U treatment (2) is set between NewNeNB and New SGW (S57).
  • the New MME transmits a Forward relocation response signal to the Old MME (S58).
  • the Old MME transmits a Handover command signal to the Old eNB (S59).
  • the Old eNB transmits a Handover command signal to the UE 10 (S60).
  • the UE 10 transmits a Handover confirm signal to the New eNB (S61).
  • the New eNB transmits a Handover Notify signal to the New MME (S62).
  • the New MME transmits a Forward relocation complete Notification signal to the Old MME (S63).
  • the Old MME transmits a Forward relocation complete Ack signal to the New MME (S64).
  • the New MME transmits a Modify bearer request signal to the New SGW (S65).
  • the Modify bearer request signal includes PU flag and PU status2.
  • the New SGW transmits a Modify bearer request signal including the PU flag to the PGW 50 (S66).
  • the PGW 50 transmits a Modify bearer response signal including PU status1 to the New SGW (S67).
  • the New SGW transmits a ModifyModbearer response signal including PU status1 to the New MME (S68).
  • Pseudo-U treatment (1) is set between New SGW and PGW50 (S69).
  • the Pseudo-U treatment (1) is set between the SGW 40 and the PGW 50 (S71).
  • the PGW 50 receives a small amount of data destined for the UE 10 associated with the Pseudo-U treatment (1)
  • the PGW 50 transmits the received small amount of data to the SGW 40 via the GTP-C (S72).
  • the SGW 40 transmits a Downlink Data Notification signal to notify the MME 30 that a small amount of data has been received (S73).
  • This Downlink Data Notification signal may contain a small amount of data.
  • the MME 30 transmits a Page signal to the eNodeB 20 (S74), and the eNodeB 20 transmits a Page signal to the UE 10 (S75).
  • the PGW 50 may determine whether the size of the data exceeds the size defined as the small amount data in order to determine whether the received data is the small amount data.
  • FIG. 11 is also used as a process executed by the UE 10 that has received the Page signal in FIG.
  • the UE 10 transmits a Service request signal to the MME 30 (S76).
  • the authentication operation and security setting of the UE 10 are performed between the UE 10 and the HSS (Home Subscriber Server) (S77).
  • the MME 30 transmits an S1-AP: Initial Context Setup Request signal including the PU flag to the eNodeB 20 (S78).
  • This S1-AP Initial Context Setup Request signal may include a small amount of data.
  • the eNodeB 20 sets a radio bearer with the UE 10 (S79). The eNodeB 20 may transmit the small amount of data received by the S1-AP: Initial Context Setup Request signal to the UE 10 using a set radio bearer.
  • the eNodeB 20 transmits the S1-AP: Initial Context Setup Complete signal including the PU status 2 to the MME 30 (S80). Thereby, Pseudo-U treatment (2) is set between eNodeB20 and SGW40 (S81).
  • the MME 30 transmits a Modify bearer request signal including the PU flag and PU status2 (S82).
  • the SGW 40 transmits a Modify bearer response signal to the MME 30 (S83).
  • FIG. 1 a case where large data larger than the data size (or data amount) defined as the small amount data is transmitted / received in an environment where small amount data is transmitted / received using GTP-C will be described using FIG.
  • the temperature sensor when a temperature sensor is used as a communication device used for MTC, the temperature sensor periodically notifies temperature information to a server device or the like. The temperature information in this case is handled as a small amount of data.
  • the temperature sensor software when the temperature sensor software is requested to be updated, the temperature sensor may transmit data having a larger amount of data than the small amount of data (hereinafter referred to as large data).
  • large data is data that exceeds the data size defined in pseudo-U / Size attribution.
  • GTP-C bearer When GTP-C bearer is configured to transmit a small amount of data between the SGW 40 and the PGW 50, when large data arriving at the UE 10 arrives at the PGW 50, the PGW 50 newly establishes a large data with the SGW 40.
  • the dedicated bearer may be a GTP-U bearer, for example. Therefore, the PGW 50 transmits a Create Bearer Request signal to the SGW 40. Further, the SGW 40 transmits a Create Bearer Request signal to the MME 30 (S91). Next, the MME 30 transmits a Bearer Setup Request signal to the eNodeB 20 (S92). Next, the eNodeB 20 transmits a Bearer Setup Response signal to the MME 30 (S93). Next, the MME 30 transmits a Create Bearer Response signal to the SGW 40. Further, the SGW 40 transmits a Create Bearer Response signal to the PGW 50 (S94).
  • a dedicated bearer for transmitting large data is set between the SGW 40 and the PGW 50 by transmitting the Create Bearer Request / Response signal, and the eNodeB 20 is transmitted / received by transmitting and receiving the Bearer Request Response / Response signal. And a dedicated bearer is set between SGW40.
  • the PGW 50 is set to the pseudo- that is already set between the SGW 40 and the PGW 50.
  • the U bearer may be changed to a normal GTP-U bearer or a dedicated bearer.
  • Update Bearer Request / Response signal is used instead of Create Bearer Request / Response signal in steps S91 and S94 of FIG.
  • a BearerBModify Request / Response signal is used instead of the Bearer Setup Request / Response in steps S92 and S93 of FIG.
  • Bearer Modify Request / Response signal is transmitted only when Pseudo-U treatment (2) is set between the eNodeB 20 and the SGW 40.
  • S1-AP is set between eNodeB 20 and MME 30 to transmit a small amount of data
  • GTP-C is set between MME 30 and PGW 50
  • eNodeB 20 and PGW 50 are used to transmit large data from UE 10.
  • a dedicated bearer for newly transmitting large data is set between
  • the eNodeB 20 transmits a Bearer Resource Command command signal to the MME 30 (S111).
  • the MME 30 transmits a Bearer Resource Command signal to the SGW 40, and the SGW 40 further transmits a Bearer Resource Command signal to the PGW 50 (S112).
  • the PGW 50 transmits a Create Bearer Request signal to the SGW 40, and the SGW 40 further transmits a Create Bearer Request signal to the MME 30 (S113).
  • the MME 30 transmits a Bearer Setup Request signal to the eNodeB 20 (S114).
  • the eNodeB 20 transmits a Bearer Setup Response signal to the MME 30 (S115).
  • the MME 30 transmits a Create Bearer Response signal to the SGW 40 (S116).
  • a dedicated bearer for transmitting large data is set between the SGW 40 and the PGW 50 by transmitting a Create Bearer Request / Response signal between the MME 30 and the PGW 50, and the Bearer is set between the MME 30 and the eNodeB 20.
  • a dedicated bearer is also set between the eNodeB 20 and the SGW 40 by transmitting a Setup Request / Response signal.
  • the UE 10 to the SGW 40 are connected to the GTP-U.
  • Large data is transmitted through the bearer.
  • a Bearer Resource Command signal is transmitted from the SGW 40 to the PGW 50.
  • a Create Bearer Request / Response signal is transmitted between the PGW 50 and the MME 30.
  • a dedicated bearer used for transmitting large data between the SGW 40 and the PGW 50 is set. In this case, the Bearer Setup Request / Response signal in FIG. 13 is not transmitted.
  • the eNodeB 20 receives large data from the UE 10.
  • the pseudo-U bearer already set between the eNodeB 20 and the PGW 50 may be changed to a normal GTP-U bearer or a dedicated bearer.
  • a Modify Bearer Request signal is used instead of the Create Bearer Request / Response signal in steps S113 and S116 of FIG.
  • a BearerBModify Request / Response signal is used instead of the Bearer Setup Request / Response in steps S114 and S115 of FIG.
  • Bearer Modify Request / Response signal is transmitted only when Pseudo-U treatment (2) is set between the eNodeB 20 and the SGW 40.
  • the UE 10 to the SGW 40 are connected to the GTP-U.
  • Large data is transmitted using a bearer.
  • a Bearer Resource Command signal is transmitted from the SGW 40 to the PGW 50.
  • a Modify Bearer Request / Response signal is transmitted between the PGW 50 and the MME 30.
  • the Pseudo-U bearer already set between the SGW 40 and the PGW 50 can be changed to a dedicated bearer or GTP-U bearer used for transmitting large data.
  • the BearerBModify Request / Response signal in FIG. 13 is not transmitted.
  • the dedicated bearer is deleted when transmission of large data is completed between the eNodeB 20 and the PGW 50.
  • the dedicated bearer may be deleted when the eNodeB 20 or the PGW 50 detects that large data is not transmitted for a certain period of time.
  • the PGW 50 transmits a Delete Bearer Request signal to the SGW 40, and further, the SGW 40 transmits a Delete Bearer Request signal to the MME 30 (S131).
  • the MME 30 transmits a Deactivate Bearer Request signal to the eNodeB 20 (S132).
  • the eNodeB 20 transmits a Deactivate Bearer Response signal to the MME 30 (S133).
  • the MME 30 transmits a Delete Bearer Response signal to the SGW 40, and further, the SGW 40 transmits a Delete Bearer Response signal to the PGW 50 (S134).
  • the dedicated bearer set between the eNodeB 20 and the PGW 50 can be deleted.
  • the flow of processing in the case where the eNodeB 20 deletes the dedicated bearer when the eNodeB 20 detects that the transmission of large data is not performed will be described with reference to FIG.
  • the eNodeB 20 transmits a BearerBResource Command signal to the MME 30 (S141).
  • the MME 30 transmits a Delete Bearer Command signal to the SGW 40, and further, the SGW 40 transmits a Delete Bearer Command signal to the PGW 50 (S142).
  • the PGW 50 transmits a Delete Bearer Request signal to the SGW 40, and the SGW 40 further transmits a Delete Bearer Request signal to the MME 30 (S143).
  • the MME 30 transmits a Deactivate Bearer Request signal to the eNodeB 20 (S144).
  • the eNodeB 20 transmits a Deactivate Bearer Response signal to the MME 30 (S145).
  • the MME 30 transmits a Delete Bearer Response signal to the SGW 40, and the SGW 40 further transmits a Delete Bearer Response signal to the PGW 50 (S146).
  • a large amount of data is transmitted in the SGW 40. It may be detected that it is not broken.
  • a Delete Bearer Command signal is transmitted from the SGW 40 to the PGW 50.
  • a Delete Bearer Request / Response signal is transmitted between the PGW 50 and the MME 30.
  • the dedicated bearer used in order to transmit the large data set between SGW40 and PGW50 can be deleted.
  • the Deactivate Bearer Request / Response signal in FIG. 15 is not transmitted.
  • a pseudo-U bearer that does not need to secure communication resources can be set between the eNodeB 20 and the PGW 50.
  • a GTP-U bearer for transmitting a small amount of data
  • using communication resources used for transmitting control signals such as GTP-C and S1-AP A small amount of data can be transmitted.
  • PMIP when PMIP is used between the SGW 40 and the PGW 50, a PMIP bearer is used instead of the GTP-C bearer between the SGW 40 and the PGW 50 in FIG.
  • the PMIP message transmitted via PMIP uses a PMIP message header instead of the GTP-C message header in FIG. 4, and has IEs A to C as in FIG. Further, UP-PDUPDIE is defined in the PMIP message in order to transmit a small amount of data.
  • Steps S151 to S154 are the same as steps S1 to S4 in FIG.
  • the MME 30 upon receiving the Update / Location / Ack signal, the MME 30 transmits a Create / Session / request signal including the PU / flag to the SGW 40 (S155).
  • the SGW 40 transmits a PBU (Proxy Binding Update) signal to the PGW 50 (S156).
  • the PBU signal includes PU flag.
  • the PGW 50 transmits a PBA (Proxy Binding Ack) signal (S157).
  • the PBA signal includes PU status1.
  • the SGW 40 transmits a Create Session response signal to the MME 30 (S158).
  • the Create Session response signal includes PU status1.
  • Pseudo-U treatment (1) is set between SGW40 and PGW50 (S159). Steps S160 to S166 in FIG. 17 are the same as steps S8 to S14 in FIG.
  • Steps S171 to S176 are the same as steps S21 to S26 in FIG.
  • the New SGW that has received the Create Session request signal in step S176 transmits a PBU signal including the PU flag to the PGW 50 (S177).
  • the PGW 50 transmits a PBA signal including PU status1 to the New SGW (S178).
  • Steps S179 to S183 are the same as steps S29 to S33 in FIG.
  • Steps S191 to S195 are the same as steps S61 to S65 in FIG.
  • the NewModSGW that has received the Modify bearer request signal transmits a PBU signal including the PU flag to the PGW 50 (S196).
  • the PGW 50 transmits a PBA signal including PU status1 to the New SGW (S197).
  • Steps S198 and S199 are the same as steps S68 and S69 in FIG.
  • communication is performed between the eNodeB 20 and the PGW 50 even when the transfer method defined as PMIP is used between the SGW 40 and the PGW 50. It is possible to set a pseudo-U bearer that does not require resource reservation. As a result, a small amount of data can be transmitted by using communication resources used for transmitting a control signal such as PMIP, using the same processing flow as when a GTP-U bearer is used for transmitting a small amount of data. Can do.
  • FIG. 20 shows an example in which GPRS defined as the second generation or the third generation defined in 3GPP is used for the core network.
  • SGSN45 and GGSN55 are contained in the apparatus which comprises GPRS.
  • the RNC 25 is used for the access network or RAN (Radio Area Network), and the UE 10 is connected to the RNC 25.
  • RAN Radio Area Network
  • the RNC 25 is a device that aggregates base stations, and communicates with UEs (mobile stations) via the base stations. For example, the RNC 25 specifies the SGSN 45 that is the transmission destination for transmitting the user data transmitted from the UE 10, and transmits the user data to the specified SGSN 45.
  • SGSN 45 is used as a data relay device that transmits and receives user data between RNC 25 and GGSN 55.
  • the user data is packet data including voice data transmitted from the UE 10.
  • the GGSN 55 is used as a gateway device that transmits and receives user data to and from an external network.
  • the external network is a network different from the network having the RNC 25, the SGSN 45, and the GGSN 55.
  • the external network may be, for example, a network managed by a provider different from the provider that manages the RNC 25, the SGSN 45, and the GGSN 55.
  • Control signals between the UE 10 and the RNC 25 are transmitted and received using a protocol defined as RRC. Further, user data in the UE 10 and the RNC 25 is transmitted and received using Traffic channel.
  • User data between the RNC 25 and the SGSN 45 and user data between the SGSN 45 and the GGSN 55 are transmitted and received using a protocol defined as GTP-U.
  • Control signals between the RNC 25 and the SGSN 45 are transmitted and received using a protocol defined as RANAP.
  • Control signals between the SGSN 45 and the GGSN 55 are transmitted and received using a protocol defined as GTP-C.
  • FIG. 21 shows that a small amount of data is transmitted and received between the SGSN 45 and the GGSN 55 using a protocol defined as GTP-C.
  • the SGSN 45 transmits a small amount of data transmitted from the RNC 25 via GTP-U to the GGSN 55 via GTP-C.
  • the GGSN 55 transmits the small amount of data to the SGSN 45 via GTP-C.
  • FIG. 22 shows an example in which a small amount of data transmitted / received using GTP-U is transmitted between the RNC 25 and SGSN 45 using a protocol for transmitting / receiving a control signal.
  • the RNC 25 transmits the small amount of data transmitted via the Traffic channel to the SGSN 45 via the RANAP.
  • the SGSN 45 receives a small amount of data destined for the UE 10 from the GGSN 55, the SGSN 45 transmits the small amount of data to the RNC 25 via the RANAP.
  • SGSN45 and GGSN55 since it is the same as that of FIG. 21, detailed description is abbreviate
  • a RANAP message transmitted via RANAP has a RANAP message header and IEs A to C. Furthermore, UP-PDUPDIE is defined in the RANAP message in order to transmit a small amount of data.
  • the processing operations of the UE 10 and the RNC 25 are the same as those of the UE 10 and the RNC 25 of FIG. Therefore, the UE 10 and the RNC 25 do not need to be equipped with a new function in order to realize the present invention.
  • the processing operation of the UE 10 is the same as that of the UE 10 of FIG. Therefore, the UE 10 does not need to be equipped with a new function in order to realize the present invention.
  • the UE 10 transmits an ATTACH signal to the SGSN 45 (S201).
  • an authentication operation and security setting of the UE 10 are performed between the UE 10 and the HSS (Home Subscriber Server) (S202).
  • the SGSN 45 transmits an Update Location request signal to the HSS (S203).
  • the HSS transmits an Insert subscriber data signal to the SGSN 45 (S204).
  • the Insert subscriber data signal includes pseudo-U / Size attribution set for each APN.
  • the pseudo-U / Size-attribution may be set in the IMSI unit or the IMEISV unit in addition to the APN unit.
  • the SGSN 45 transmits an Insert subscriber data Ack signal to the HSS (S205).
  • the HSS transmits an Update Location ACK signal to the SGSN 45.
  • the SGSN 45 acquires and manages pseudo-U attribution information set in units of APN in this way.
  • the SGSN 45 transmits an ATTACH accept signal to the UE 10 (S207).
  • the PDP Context is a communication resource used for transmitting user data between the SGSN 45 and the GGSN 55. Further, in this figure, an example in which a small amount of data is transmitted as user data will be described.
  • the UE 10 transmits an Activate PDP Context Request (APN) signal to the SGSN 45 (S211).
  • the SGSN 45 transmits a Create PDP Context Request signal including the PU flag to the GGSN 55 (S212).
  • the GGSN 55 transmits a Create PDP Context Response signal including PU status1 to the SGSN 45 (S213).
  • Pseudo-U treatment (1) is set between SGSN45 and GGSN55 (S214).
  • the SGSN 45 transmits a RAB assignment request signal including the PU flag to the RNC 25 (S215).
  • the RNC 25 sets a radio bearer (radio bearer) with the UE 10 (S216).
  • the RNC 25 transmits a RAB assignment-Response signal including PU status 2 to the SGSN 45 (S217).
  • Pseudo-U treatment (2) (S218) is set between RNC 25 and SGSN 45.
  • the SGSN 45 transmits an Activate PDP Context Accept signal to the UE 10 (S219).
  • Routing Area is location information of the UE 10 managed on the GPRS network.
  • the RA may be an area composed of a plurality of cells.
  • the RAU is a process executed when the RA where the UE 10 is located is changed.
  • the UE 10 transmits a RAU signal to the SGSN (hereinafter, New SGSN) that manages the RA after the change (S221).
  • the New SGSN transmits an SGSN Context request signal to the SGSN (hereinafter referred to as Old SGSN) that manages the RA before the change (S222).
  • Old SGSN transmits an SGSN Context response signal to New SGSN (S223).
  • the SGSN Context response signal includes pseudo-U / Size attribution associated with the UE10.
  • an authentication operation and security setting of the UE 10 are performed between the UE 10 and the HSS (Home Subscriber Server) (S224).
  • the New SGSN transmits an SGSN Context Ack signal to the Old SGSN (S225).
  • the New SGSN transmits an Update PDP Context Request signal to the GGSN 55 in order to set a pseudo-U bearer with the GGSN 55 (S226).
  • the Update PDP Context Request signal includes PU flag.
  • the GGSN 55 transmits an Update PDP Context Response signal including PU status1 to the New SGSN (S227).
  • Pseudo-U treatment (1) is set between New SGSN and GGSN 55 (S228).
  • step S229 to step S232 are the same as step S203 to step S206 in FIG. 24, detailed description thereof will be omitted.
  • the New SGSN that has received the Update Location Ack signal in step S232 transmits an RAU accept signal to the UE 10 (S233).
  • the RNC before change (hereinafter referred to as Old RNC) transmits a Relocation Required signal to the SGSN before change (hereinafter referred to as Old SGSN) (S241).
  • the Old SGSN transmits a Forward Relocation Request signal including the PU flag to the changed SGSN (hereinafter, New SGSN) (S242).
  • the New SGSN transmits a Relocation Request signal including the PUNflag to the NewSRNC (S243).
  • the New RNC transmits a Relocation Request Acknowledge signal including PU status 2 to the New SGSN (S244).
  • Pseudo-U treatment (2) is set between New RNC and New SGSN (S245).
  • the New SGSN transmits a Forward Relocation Response signal to the Old SGSN (S246).
  • the Old SGSN transmits a Relocation command signal to the Old RNC (S247).
  • the Old RNC transmits an RRC message signal to the UE 10 (S248).
  • the Old RNC transmits a Forward SRNS Context signal to the Old SGSN (S249).
  • Old SGSN transmits a Forward SRNS Context signal to New SGSN (S250).
  • the New SGSN transmits a Forward SRNS Context Ack signal to the Old SGSN (S251), and further transmits a Forward SRNS Context signal to the New RNC (S252).
  • the New RNC transmits a Relocation detect signal to the New SGSN (S254).
  • the UE 10 transmits an RRC message signal to the New RNC (S255).
  • the New RNC transmits a Relocation complete signal to the New SGSN (S256).
  • the New SGSN transmits a Forward relocation complete signal to the Old SGSN (S257).
  • Old SGSN transmits a Forward relocation complete Ack signal to New SGSN (S258).
  • the New SGSN transmits an Update PDP Context request signal including the PU flag to the GGSN 55 (S ⁇ b> 259).
  • the GGSN 55 transmits an Update PDP Context Response signal including PU status1 to the New SGSN (S260).
  • Pseudo-U treatment (1) is set between New SGSN and GGSN 55 (S261).
  • the Old SGSN transmits an Iu release command signal to the Old RNC in order to release communication resources secured with the Old RNC (S262).
  • the Old RNC transmits an Iu release command complete signal to the Old SGSN (S263).
  • Pseudo-U treatment (1) is set between the SGSN 45 and the GGSN 55 (S271).
  • the GGSN 55 receives a small amount of data destined for the UE 10 associated with the Pseudo-U treatment (1)
  • the GGSN 55 transmits the received small amount of data to the SGSN 45 via the GTP-C (S272).
  • the SGSN 45 transmits a Page signal to the RNC 25 (S273)
  • the RNC 25 transmits a Page signal to the UE 10 (S274).
  • the UE 10 transmits a Service request signal to the SGSN 45 (S275).
  • the SGSN 45 transmits an RAB assignment Request signal including the PU flag to the RNC 25 (S276).
  • This RAB ⁇ ⁇ ⁇ assignment ⁇ ⁇ Request signal may include a small amount of data.
  • the RNC 25 sets a radio bearer with the UE 10 (S277).
  • the RNC 25 may transmit a small amount of data received by the RAB assignment Request signal to the UE 10 using a set radio bearer.
  • the RNC 25 transmits a RAB assignment-Response signal including the PU assignment status 2 to the SGSN 45 (S278).
  • Pseudo-U treatment (2) is set between the RNC 25 and the SGSN 45 (S279).
  • GTP-C When GTP-C is configured to transmit a small amount of data between the SGSN 45 and the GGSN 55, when large data arriving at the UE 10 arrives at the GGSN 55, the GGSN 55 newly transmits large data to the SGSN 45.
  • the dedicated bearer may be referred to as Secondary PDP Context when the pseudo bearer is Primary PDP Context.
  • the GGSN 55 transmits an Initiate PDP Context Activation Request signal to the SGSN 45 in order to set a dedicated bearer (S281).
  • the SGSN 45 transmits a RAB assignment Request signal to the RNC 25 (S282).
  • the RNC 25 transmits a RAB assignment Response signal to the SGSN 45 (S283).
  • the SGSN 45 transmits a Create PDP context Request signal to the GGSN 55 (S284).
  • the GGSN 55 transmits a Create PDP context Response signal to the SGSN 45 (S285).
  • the SGSN 45 transmits an Initiate PDP Context Activation Response signal to the GGSN 55 (S286).
  • a dedicated bearer for transmitting large data is set between the SGSN 45 and the GGSN 55, and by sending a RAB assignmentRequest / Response signal, A dedicated bearer is also set between the RNC 25 and the SGSN 45.
  • the GGSN 55 can transmit the received large data to the SGSN 45 using the dedicated bearer, and the SGSN 45 can further transmit to the RNC 25.
  • the GGSN 55 is set to the pseudo-
  • the U bearer may be changed to a normal GTP-U bearer or a dedicated bearer.
  • an UpdateInPDP Context Request / Response signal is used instead of the Initiate PDP Context Activation Request signal in steps S281 and S286 of FIG. Further, in this case, the processing of step S284 and step S285 in FIG. 31 is omitted.
  • the RAB assignment Request / Response signal is transmitted only when Pseudo-U treatment (2) is set between the RNC 25 and the SGSN 45.
  • the RNC 25 transmits a RAB assignment request signal to the SGSN 45 (S291).
  • the SGSN 45 transmits a RAB assignment ⁇ Request signal to the RNC 25 (S292).
  • the RNC 25 transmits a RAB assignment Response signal to the SGSN 45 (S293).
  • the SGSN 45 transmits a Create PDP Context Request signal to the GGSN 55 (S294).
  • the GGSN 55 transmits a Create PDP Context Response signal to the SGSN 45 (S295).
  • a dedicated bearer for transmitting large data is set between the SGSN 45 and the GGSN 55, and by sending a RAB assignmentRequest / Response signal, A dedicated bearer is also set between the RNC 25 and the SGSN 45.
  • the RNC 25 can transmit the received large data to the SGSN 45 using the dedicated bearer, and the SGSN 45 can further transmit to the GGSN 55.
  • a small amount of data is transmitted between the SGSN 45 and the GGSN 55 using a GTP-C bearer and is transmitted between the SGSN 45 and the RNC 25 using a GTP-U bearer
  • the UE 10 to the SGSN 45 are connected to the GTP-U.
  • Large data is transmitted using a bearer.
  • a Create PDP Context Request / Response signal is transmitted between the SGSN 45 and the GGSN 55.
  • a dedicated bearer is set between SGSN45 and GGSN55. In this case, the RAB assignment request / response signal in FIG. 32 is not transmitted.
  • the RNC 25 receives a large amount of data from the UE 10.
  • the pseudo-U bearer already set between the RNC 25 and the GGSN 55 may be changed to a normal GTP-U bearer or a dedicated bearer.
  • RAB modify Request / Response signal is used instead of RAB assignment Request signal in step S291 in FIG.
  • Update PDP Context Request / Response signal is used instead of Create PDP Context Request / Response signal in steps S294 and S295 of FIG.
  • the pseudo-U bearer already set between the RNC 25 and the GGSN 55 can be changed to a normal GTP-U bearer or a dedicated bearer.
  • the dedicated bearer is deleted when transmission of large data between the RNC 25 and the GGSN 55 is completed.
  • the dedicated bearer may be deleted when the RNC 25 or the GGSN 55 detects that large data is not transmitted for a certain period of time.
  • the GGSN 55 when the GGSN 55 detects that large data is not transmitted for a certain period of time, the GGSN 55 transmits a Delete PDP Context Request signal to the SGSN 45 (S301).
  • the RNC 25 transmits a RAB assignment ⁇ Request signal to the RNC 25 in order to delete the dedicated bearer set between the RNC 25 and the SGSN 45 (S302).
  • the RNC 25 transmits a RAB assignment response signal to the SGSN 45 (S303).
  • the SGSN 45 transmits a Delete PDP Context Response signal to the GGSN 55 (S304). Thereby, the dedicated bearer set between RNC25 and GGSN55 can be deleted.
  • the GTP-U bearer or the dedicated bearer is changed to a pseudo-U bearer when the large data transmission ends.
  • the flow of processing when returning to step will be described. Specifically, an Update PDP Context Request / Response signal is used instead of the Delete PDP Context Request / Response signal in steps S301 and S304 in FIG. Using these signals, processing for returning the GTP-U bearer or the dedicated bearer to the pseudo-U bearer is executed.
  • the SGSN 45 transmits a RAB assignment request signal to the RNC 25 (S312).
  • the RNC 25 transmits a RAB assignment Response signal to the SGSN 45 (S313).
  • the SGSN 45 transmits a Delete PDP Context Request signal to the GGSN 55 (S314).
  • the GGSN 55 transmits a Delete PDP Context Response signal to the SGSN 45 (S315).
  • the dedicated bearer for transmitting large data between the SGSN 45 and the GGSN 55 is deleted, and by sending the RAB assignment Request / Response signal, the RNC 25 And the dedicated bearer between the SGSN 45 is deleted.
  • a RAB modify Request signal is used instead of the RAB Release33Request signal in step S311 in FIG.
  • Update PDP Context Request / Response signal is used instead of Delete PDP Context Request / Response signal in steps S314 and S315 of FIG. Using these signals, processing for returning the GTP-U bearer or the dedicated bearer to the pseudo-U bearer is executed.
  • a dedicated bearer between the SGSN 45 and the GGSN 55 can be deleted by transmitting a Delete PDP Context Request / Response signal between the SGSN 45 and the GGSN 55.
  • the RAB Release Request signal and RAB assignment Request / Response signal in FIG. 34 are not transmitted.
  • a pseudo-U bearer that does not need to secure communication resources can be set between the RNC 25 and the GGSN 55.
  • a small amount of data can be obtained by using communication resources used for transmitting control signals such as GTP-C and RANAP, using the same processing flow as in the case of using a GTP-U bearer for the transmission of a small amount of data. Can be transmitted.
  • the network described in the fourth embodiment includes the RNC 25 used as 3G access in the access network, and the SGW 40 and PGW 50 used as EPC in the core network. Further, an SGSN 45 is arranged between the access network and the core network.
  • the RNC 25 is connected to the UE 10 that transmits and receives a small amount of data. In the following description, description will be made on the assumption of such a network configuration.
  • Steps S321 to S327 in FIG. 35 are the same as steps S1 to S7 in FIG.
  • SGSN 45 is used instead of the MME 30 of FIG.
  • steps S328 to S331 in FIG. 35 are the same as steps S215 to S218 in FIG.
  • the SGSN 45 transmits a Modify bearer request signal to the SGW 40 (S332).
  • the Modify bearer request signal includes PU flag and PU status2.
  • the SGW 40 transmits a Modify bearer response signal to the SGSN 45 (S333).
  • the SGSN 45 transmits an ATTACH accept signal to the UE 10 (S334).
  • Pseudo-U treatment (2) in FIG. 35 may be set between RNC 25, SGSN 45, and SGW 40, or may be set between RNC 25 and SGSN 45 without going through SGSN 45. The same applies to the following description.
  • Steps S341 to S345 are the same as steps S221 to S225 in FIG. 26, and thus detailed description thereof is omitted.
  • Steps S346 to S352 are the same as steps S26 to S32 in FIG.
  • SGSN is used instead of MME in FIG.
  • step S352 the New SGSN that has received the Update Location Ack signal transmits the RAU accept signal to the UE 10 (S353).
  • Steps S361 to S365 in FIG. 37 are the same as steps S275 to S279 in FIG. Also, step S366 and step S367 in FIG. 37 are the same as step S332 and step S333 in FIG.
  • Steps S391 to S395 in FIG. 40 are the same as steps S71 to S75 in FIG.
  • FIG. 41 is also used as a process executed by UE 10 that has received the Page signal in FIG.
  • the UE 10 transmits a Service request signal to the SGSN 45 (S401).
  • an authentication operation and security setting of the UE 10 are performed between the UE 10 and the HSS (Home Subscriber Server) (S402).
  • the SGSN 45 transmits a RAB assignment Request signal including the PU flag to the RNC 25 (S403).
  • the RNC 25 sets a radio bearer with the UE 10 (S404).
  • the RNC 25 transmits a RAB assignment-Response signal including the PU assignment status 2 to the SGSN 45 (S405).
  • Pseudo-U treatment (2) is set between RNC25 and SGW40 (S406).
  • the PGW 50 When GTP-C is configured to transmit a small amount of data between the SGW 40 and the PGW 50, when large data arrives at the PGW 50, the PGW 50 is dedicated to newly transmitting large data to the SGW 40. Set up a bearer. Therefore, the PGW 50 transmits a Create Bearer Request signal to the SGW 40. Further, the SGW 40 transmits a Create Bearer Request signal to the SGSN 45 (S411). Next, the SGSN 45 transmits a RAB assignment Request signal to the RNC 25 (S412). Next, the RNC 25 transmits a RAB assignment Response signal to the SGSN 45 (S413). Next, the SGSN 45 transmits a Create Bearer Response signal to the SGW 40. Further, the SGW 40 transmits a Create Bearer Response signal to the PGW 50 (S414).
  • a dedicated bearer for transmitting large data is set between the SGW 40 and the PGW 50 by transmitting / receiving the Create Bearer Request / Response signal, and by transmitting / receiving the RAB assignment Request / Response signal, the RNC 25
  • dedicated bearers are set between SGSN 45 and SGSN 45 and SGW 40.
  • a dedicated bearer may be set between the RNC 25 and the SGW 40.
  • the RAB assignment Request / Response signal in steps S412 and S413 in FIG. 42 is transmitted only when Pseudo-U treatment (2) is set between the RNC 25 and the SGSN 45.
  • the RNC 25 transmits an RAB assignment request signal to the SGSN 45 (S421).
  • the SGSN 45 transmits a Bearer Resource Command signal to the SGW 40, and further the SGW 40 transmits a Bearer Resource Command signal to the PGW 50 (S422).
  • the PGW 50 transmits a Create Bearer Request signal to the SGW 40, and the SGW 40 further transmits a Create Bearer Request signal to the SGSN 45 (S423).
  • the SGSN 45 transmits a RAB assignment request signal to the RNC 25 (S424).
  • the RNC 25 transmits a RAB assignment Response signal to the SGSN 45 (S425).
  • the SGSN 45 transmits a Create Bearer Response signal to the SGW 40, and the SGW 40 further transmits a Create Bearer Response signal to the PGW 50 (S426).
  • a dedicated bearer for transmitting large data is set between the SGW 40 and the PGW 50 by transmitting the Create Bearer Request / Response signal, and the RNC 25 is transmitted by transmitting the Bearer Setup Request / Response signal.
  • dedicated bearers are set between SGSN 45 and SGSN 45 and SGW 40.
  • a dedicated bearer may be set between the RNC 25 and the SGW 40 by transmitting a Bearer Setup Request / Response signal.
  • the RNC 25 can transmit the received large data to the SGW 40 using the dedicated bearer, to the SGW 40 via the SGSN 45, and further to the SGW 40.
  • a Bearer Resource Command signal is transmitted from the SGSN 45 to the PGW 50.
  • a Create Bearer Request / Response signal is transmitted between the PGW 50 and the SGSN 45.
  • a dedicated bearer is set between SGSN45 and PGW50. In this case, the RAB assignment request / response signal in FIG. 43 is not transmitted.
  • GTP-C and RANAP are set to transmit a small amount of data between the RNC 25 and the PGW 50
  • the RNC 25 receives large data from the UE 10
  • the pseudo-U bearer may be changed to a normal GTP-U bearer or a dedicated bearer.
  • a Modify Bearer Request / Response signal is used instead of the Create Bearer Request / Response signal in steps S423 and S426 of FIG.
  • the UE 10 to the SGW 40 are connected to the GTP-U.
  • Large data is transmitted using a bearer.
  • the pseudo-U bearer already set between the SGW 40 and the PGW 50 may be changed to a normal GTP-U or a dedicated bearer.
  • a Bearer Resource Command signal is transmitted from the SGW 40 to the PGW 50.
  • a Modify Bearer Request / Response signal is transmitted between the PGW 50 and the MME 30. In this case, the RAB assignment request / Response signal in FIG. 43 is not transmitted.
  • the dedicated bearer is deleted when transmission of large data between the RNC 25 and the PGW 50 is completed.
  • the dedicated bearer may be deleted when the RNC 25 or the PGW 50 detects that large data is not transmitted for a certain period of time.
  • the PGW 50 transmits a Delete Bearer Request signal to the SGW 40, and further, the SGW 40 transmits a Delete Bearer Request signal to the SGSN 45 (S431).
  • the SGSN 45 transmits a RAB ⁇ ⁇ assignment Request signal to the RNC 25 in order to delete the dedicated bearer set between the RNC 25, SGSN 45 and SGW 40 or between the RNC 25 and SGW 40 (S432).
  • the RNC 25 transmits a RAB assignment response signal to the SGSN 45 (S433).
  • the SGSN 45 transmits a Delete Bearer Response signal to the SGW 40, and further, the SGW 40 transmits a Delete Bearer Response signal to the PGW 50 (S434).
  • the dedicated bearer set between the RNC 25 and the PGW 50 can be deleted.
  • the GTP-U bearer or the dedicated bearer is changed to a pseudo-U bearer when the large data transmission ends.
  • the flow of processing to return to will be described. Specifically, an Update Bearer Request / Response signal is used instead of the Delete Bearer Request / Response signal in steps S431 and S434 in FIG. In this way, the process of returning the GTP-U bearer or the dedicated bearer to the pseudo-U bearer is executed.
  • the SGSN 45 transmits a Delete Bearer Command signal to the SGW 40, and further, the SGW 40 transmits a Delete Bearer Command signal to the PGW 50 (S442).
  • the PGW 50 transmits a Delete Bearer Request signal to the SGW 40, and the SGW 40 further transmits a Delete Bearer Request signal to the SGSN 45 (S443).
  • the SGSN 45 transmits a RAB assignment Request signal to the RNC 25 (S444).
  • the RNC 25 transmits a RAB assignment Response signal to the SGSN 45 (S445).
  • the SGSN 45 transmits a Delete Bearer Response signal to the SGW 40, and the SGW 40 further transmits a Delete Bearer Response signal to the PGW 50 (S446).
  • the dedicated bearer for transmitting large data between the SGW 40 and the PGW 50 is deleted, and by sending a Deactivate Bearer Request / Response signal, the RNC 25, The dedicated bearer between the SGSN 45 and the SGW 40 or the RNC 25 and the SGW 40 is deleted.
  • a large amount of data is transmitted in the SGSN 45. It may be detected that it is not broken.
  • a Delete Bearer ⁇ ⁇ Command signal is transmitted from the SGSN 45 to the PGW 50 in order to delete the dedicated bearer.
  • a Delete Bearer Request / Response signal is transmitted between the PGW 50 and the SGSN 45. In this case, the Deactivate Bearer Request / Response signal in FIG. 45 is not transmitted.
  • a pseudo-U bearer that does not require securing communication resources can be set between the RNC 25 and the PGW 50.

Landscapes

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

Abstract

L'invention concerne un système de communications mobile et procédé de communications de données permettant de réduire la charge de ressources dans un système de téléphone mobile. Le système de communications mobile comprend une passerelle de service (SGW) (40) pour transférer des données utilisateur à destination/ en provenance d'un nœud évolué B (eNodeB) (20), et une passerelle de réseau de données par paquets (PGW) (50) pour transférer des données utilisateur à destination/en provenance d'un réseau externe. La SGW (40) et la PGW (50) sont configurées de telle sorte que de petits volumes de données envoyés et reçus, de manière autonome, à partir/en provenance d'un dispositif de terminal via le eNodeB (20) sont transférés entre la SGW (40) et la PGW (50) par utilisation d'une ressource de communication pour transférer les signaux de commande plutôt que d'une ressource de communication pour transférer les données utilisateur.
PCT/JP2013/005397 2012-09-12 2013-09-12 Système et procédé de communications mobile, dispositif de passerelle et station de base WO2014041805A1 (fr)

Priority Applications (6)

Application Number Priority Date Filing Date Title
EP13837842.7A EP2897392A4 (fr) 2012-09-12 2013-09-12 Système et procédé de communications mobile, dispositif de passerelle et station de base
US14/426,615 US20150237458A1 (en) 2012-09-12 2013-09-12 Mobile communication system, data communication method, gateway device and base station
KR1020157005702A KR101654491B1 (ko) 2012-09-12 2013-09-12 이동 통신 시스템, 데이터 통신 방법, 게이트웨이 장치 및 기지국
JP2014535381A JP5900629B2 (ja) 2012-09-12 2013-09-12 移動通信システム、データ通信方法、ゲートウェイ装置及び基地局
CN201380046603.9A CN104604266A (zh) 2012-09-12 2013-09-12 移动通信系统、数据通信方法、网关设备和基站
IN1108DEN2015 IN2015DN01108A (fr) 2012-09-12 2013-09-12

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2012200731 2012-09-12
JP2012-200731 2012-09-12

Publications (1)

Publication Number Publication Date
WO2014041805A1 true WO2014041805A1 (fr) 2014-03-20

Family

ID=50277946

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2013/005397 WO2014041805A1 (fr) 2012-09-12 2013-09-12 Système et procédé de communications mobile, dispositif de passerelle et station de base

Country Status (7)

Country Link
US (1) US20150237458A1 (fr)
EP (1) EP2897392A4 (fr)
JP (1) JP5900629B2 (fr)
KR (1) KR101654491B1 (fr)
CN (1) CN104604266A (fr)
IN (1) IN2015DN01108A (fr)
WO (1) WO2014041805A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018061920A1 (fr) * 2016-09-30 2018-04-05 株式会社Ｎｔｔドコモ Procédé de commande de communication et système de communication
JP2019511161A (ja) * 2016-02-17 2019-04-18 日本電気株式会社 データ伝送のための制御プレーンおよびユーザプレーンの選択
JP2019146270A (ja) * 2015-07-24 2019-08-29 日本電気株式会社 Ｕｅ、ｍｍｅ、ｕｅの通信方法、及びｍｍｅの通信方法

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3308557B1 (fr) * 2015-06-11 2023-06-07 Intel Corporation Architecture de réseau de l'internet des objets cellulaire

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010117761A1 (fr) * 2009-03-31 2010-10-14 Interdigital Patent Holdings, Inc. Procédé et appareil permettant d'offrir un service sans commutation de paquets dans un réseau cible de technologie d'accès radio
WO2011132103A1 (fr) * 2010-04-21 2011-10-27 Telefonaktiebolaget L M Ericsson (Publ) Réduction de bande passante de dispositif mtc
WO2011138238A1 (fr) * 2010-05-03 2011-11-10 Alcatel Lucent Gestion du fonctionnement d'un dispositif de communication de type machine dans un système de communication mobile
WO2011141834A1 (fr) * 2010-05-10 2011-11-17 Telefonaktiebolaget L M Ericsson (Publ) Réduction du surdébit de protocole dans des procédures d'accès de paquets à bloc unique
WO2012050360A2 (fr) * 2010-10-12 2012-04-19 Samsung Electronics Co., Ltd. Procédé et système de transmission d'unités de données par paquets dans des dispositifs de communication du type machine sur une interface réseau dans un réseau d'évolution à long terme

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101931898B (zh) * 2009-06-26 2014-03-05 华为技术有限公司 用户面数据的传输方法、装置及系统
EP2941026B1 (fr) * 2010-03-23 2017-12-13 Interdigital Patent Holdings, Inc. Procédé pour la communication d'un dispositif de communication de type machine et unité de transmission/réception sans fil correspondante
CN102238520B (zh) * 2010-04-26 2014-12-31 中兴通讯股份有限公司 一种小数据包传输的方法和系统
CN102457871B (zh) * 2010-10-26 2014-06-11 电信科学技术研究院 一种网络资源节省方法和系统
US20120254890A1 (en) * 2011-04-01 2012-10-04 Renesas Mobile Corporation Small Data Transmission For Detached Mobile Devices
US8879667B2 (en) * 2011-07-01 2014-11-04 Intel Corporation Layer shifting in open loop multiple-input, multiple-output communications
CN102316521B (zh) * 2011-09-15 2014-04-16 电信科学技术研究院 数据传输方法、系统和设备
CN102340754B (zh) * 2011-09-23 2014-07-23 电信科学技术研究院 数据发送和接收方法及设备
KR101589393B1 (ko) * 2011-10-03 2016-01-27 인텔 코포레이션 장치 간(ｄ２ｄ) 통신 메커니즘
CN106507332B (zh) * 2011-11-04 2020-01-10 华为技术有限公司 一种数据传输方法、移动性管理实体和移动终端
US9241351B2 (en) * 2011-11-04 2016-01-19 Intel Corporation Techniques and configurations for triggering a plurality of wireless devices
KR102058954B1 (ko) * 2012-02-06 2019-12-26 삼성전자 주식회사 무선 통신 시스템에서 small data를 효율적으로 전송하는 방법 및 장치
US20130265937A1 (en) * 2012-04-09 2013-10-10 Puneet Jain Machine type communication (mtc) via non-access stratum layer
US9363835B2 (en) * 2013-05-14 2016-06-07 Telefonaktiebolaget Lm Ericsson (Publ) Methods and nodes for improved network signaling

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010117761A1 (fr) * 2009-03-31 2010-10-14 Interdigital Patent Holdings, Inc. Procédé et appareil permettant d'offrir un service sans commutation de paquets dans un réseau cible de technologie d'accès radio
WO2011132103A1 (fr) * 2010-04-21 2011-10-27 Telefonaktiebolaget L M Ericsson (Publ) Réduction de bande passante de dispositif mtc
WO2011138238A1 (fr) * 2010-05-03 2011-11-10 Alcatel Lucent Gestion du fonctionnement d'un dispositif de communication de type machine dans un système de communication mobile
WO2011141834A1 (fr) * 2010-05-10 2011-11-17 Telefonaktiebolaget L M Ericsson (Publ) Réduction du surdébit de protocole dans des procédures d'accès de paquets à bloc unique
WO2012050360A2 (fr) * 2010-10-12 2012-04-19 Samsung Electronics Co., Ltd. Procédé et système de transmission d'unités de données par paquets dans des dispositifs de communication du type machine sur une interface réseau dans un réseau d'évolution à long terme

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"GPRS enhancements for E-UTRAN access (Release 11", 3GPP TS 23.401 V11.1.0, March 2012 (2012-03-01)
3RD GENERATION PARTNERSHIP PROJECT: "Service requirements for Machine-Type Communications (MTC)", 3GPP TS 22.368 V11.5.0, June 2012 (2012-06-01)
KDDI, KT CORP. ET AL.: "MTC Small Data Transmissions", 3GPP TSG-SA WG1 #55, S1-112412, 12 August 2011 (2011-08-12), XP050547892 *
See also references of EP2897392A4

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2019146270A (ja) * 2015-07-24 2019-08-29 日本電気株式会社 Ｕｅ、ｍｍｅ、ｕｅの通信方法、及びｍｍｅの通信方法
US11272337B2 (en) 2015-07-24 2022-03-08 Nec Corporation Mobile communication system, MME, terminals and method for communication
US11445345B2 (en) 2015-07-24 2022-09-13 Nec Corporation Mobile communication system, MME, terminals and method for communication
JP2019511161A (ja) * 2016-02-17 2019-04-18 日本電気株式会社 データ伝送のための制御プレーンおよびユーザプレーンの選択
US10616936B2 (en) 2016-02-17 2020-04-07 Nec Corporation Method for (re)selection of control plane and user plane data transmission
US10945300B2 (en) 2016-02-17 2021-03-09 Nec Corporation Method for (re)selection of control plane and user plane data transmission
US12028912B2 (en) 2016-02-17 2024-07-02 Nec Corporation Method for (re)selection of control plane and user plane data transmission
WO2018061920A1 (fr) * 2016-09-30 2018-04-05 株式会社Ｎｔｔドコモ Procédé de commande de communication et système de communication
JPWO2018061920A1 (ja) * 2016-09-30 2019-07-25 株式会社Ｎｔｔドコモ 通信制御方法および通信システム
US10687385B2 (en) 2016-09-30 2020-06-16 Ntt Docomo, Inc. Communication control method and communication system

Also Published As

Publication number Publication date
CN104604266A (zh) 2015-05-06
JP5900629B2 (ja) 2016-04-06
IN2015DN01108A (fr) 2015-06-26
EP2897392A1 (fr) 2015-07-22
KR20150040345A (ko) 2015-04-14
JPWO2014041805A1 (ja) 2016-08-12
US20150237458A1 (en) 2015-08-20
KR101654491B1 (ko) 2016-09-05
EP2897392A4 (fr) 2016-03-09

Similar Documents

Publication Publication Date Title
US10219143B2 (en) Data transmission method, mobility management entity, and mobile terminal
KR101519547B1 (ko) 사용자 장비의 위치 정보를 갱신하기 위한 방법 및 장치
KR102250738B1 (ko) Epc에서의 원활한 ue 이전
EP3167657B1 (fr) Procédé et dispositif de transfert intercellulaire entre des noeuds menb dans un système à petites cellules
US20190357106A1 (en) Data transmission supporting method and apparatus
CN102223691B (zh) 移动通信系统中的切换方法
CN111866851B (zh) 无线通信系统中基于局部区域管理分组数据连接的方法和装置
EP2683211A1 (fr) Support de transmission de données par paquets dans un réseau mobile
EP2259657B1 (fr) Procédé pour indiquer la gestion de support de la passerelle de desserte
KR102200821B1 (ko) 작은 셀 아키텍처에서 로컬 브레이크아웃을 지원하기 위한 방법, 시스템 및 장치
US20160227439A1 (en) Method and device for setting up local breakout bearers
CN102868994A (zh) 一种支持用户设备ue移动性的方法
WO2012094957A1 (fr) Procédé et système pour effecteur une gestion de mobilité sur un terminal mtc
CN103686932A (zh) 一种保证本地ip接入业务正确建立的方法
CN102740404A (zh) 一种保证本地ip接入业务正确建立的方法
US20150237495A1 (en) Method and system for differentiating between subscribers
JP5900629B2 (ja) 移動通信システム、データ通信方法、ゲートウェイ装置及び基地局
CN102469619B (zh) 一种移动通信系统及其服务网关重定位的方法
CN103428888B (zh) 一种直通隧道建立方法及系统
CN104053200A (zh) Ue在umts系统和lte系统之间切换的方法及设备
CN101610462B (zh) 一种数据报文发送方法、装置及通信系统
CN102300194B (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: 13837842

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2014535381

Country of ref document: JP

Kind code of ref document: A

REEP Request for entry into the european phase

Ref document number: 2013837842

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2013837842

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 20157005702

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 14426615

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE