WO2017056349A1 - Système de communication mobile, dispositif de gestion de mobilité, procédé de communication, terminal de communication mobile, et support non transitoire lisible par ordinateur - Google Patents

Système de communication mobile, dispositif de gestion de mobilité, procédé de communication, terminal de communication mobile, et support non transitoire lisible par ordinateur Download PDF

Info

Publication number
WO2017056349A1
WO2017056349A1 PCT/JP2016/002983 JP2016002983W WO2017056349A1 WO 2017056349 A1 WO2017056349 A1 WO 2017056349A1 JP 2016002983 W JP2016002983 W JP 2016002983W WO 2017056349 A1 WO2017056349 A1 WO 2017056349A1
Authority
WO
WIPO (PCT)
Prior art keywords
pgw
mobile communication
management device
mobility management
message
Prior art date
Application number
PCT/JP2016/002983
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 KR1020177036218A priority Critical patent/KR102028271B1/ko
Priority to RU2016146737A priority patent/RU2652453C1/ru
Publication of WO2017056349A1 publication Critical patent/WO2017056349A1/fr

Links

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/12—Reselecting a serving backbone network switching or routing node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/02—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration by periodical registration
    • 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/04—Registration at HLR or HSS [Home Subscriber Server]

Definitions

  • the present invention relates to a mobile communication system, a mobility management device, a communication method, and a program, and more particularly to a mobile communication system, a mobility management device, a communication method, and a program that execute a handover process.
  • 3GPP 3rd Generation Generation Partnership Project
  • a communication area 3GPP communication area in which a wireless communication method specified in 3GPP is used and a communication area (Non-3GPP communication area) in which a wireless communication method not specified in 3GPP is used
  • 3GPP communication area 3GPP communication area
  • Non-3GPP communication area a communication area in which a wireless communication method not specified in 3GPP is used
  • a UE which is a mobile communication terminal connects to a visited network (EPC: EvolvedvolvePacket Core) using a 3GPP radio access technology, and a gateway (for example, PGW: Packet Data Network Gateway).
  • EPC EvolvedvolvePacket Core
  • PGW Packet Data Network Gateway
  • the PGW is a gateway for transmitting (transmitting / receiving) user data related to the UE between the visited network and the external network, and establishes PDN Connection used for communication with the UE.
  • PDN Connection is composed of one or a plurality of communication bearers.
  • PDN Connection is established for each service provided to the UE.
  • the service is associated with an APN (Access Point Name) such as IMS (IP Multimedia Subsystem) or Internet connection.
  • APN Access Point Name
  • IMS IP Multimedia Subsystem
  • an MME Mobility Management Entity transmits a PGW ID that is PGW identification information to an HSS (Home Subscriber Server) that manages subscriber information about the UE.
  • the PGW ID is identification information of the PGW that has established a PDN connection used for communication with the UE.
  • the MME is a node device that performs setting of PDN Connection, mobility management regarding UE, communication control, and the like.
  • the HSS is a server device that performs management for associating PGW IDs in units of PDN connections, management of subscriber information of UEs, and the like.
  • the procedure for the MME to transmit the PGW ID to the HSS is described in Non-Patent Document 1 describing the ATTACH procedure.
  • the UE connects to the IP access device using the Non-3GPP radio access technology.
  • the IP access device makes an inquiry to the AAA (AuthenticationPGAuthorization Accounting) server for the PGW ⁇ ⁇ ⁇ ⁇ ID of the PGW that has established a PDN Connection with the UE so that the UE can continuously receive services from the external network.
  • the AAA server executes communication authentication and the like in the Non-3GPP communication area.
  • the AAA server is linked to the HSS, and can acquire the PGW ID managed in the HSS.
  • the AAA server notifies the IP access device of the PGW ID acquired from the HSS.
  • the IP access device can select a PGW that has established a PDN connection for the UE using the PGW ID acquired from the AAA server. Further, the IP access device establishes a communication path or communication bearer between the UE and the PGW. In this way, the UE can continue to receive services from the external network via the same PGW even at the movement destination. That is, handover from the 3GPP communication area to the Non-3GPP communication area is realized by using the PGW as an anchor point.
  • the MME When the MME receives a Reset notification from the HSS, the MME manages Location Information Confirmed in HSS (LICH) in the UE as Not Confirmed.
  • LICH Location Information Confirmed in HSS
  • the state in which LICH is set to Not Confirmed indicates that the HSS has resumed and does not hold the PGW ID of the PGW that established the PDN Connection used for communication with the UE.
  • the UE transmits a TAU request message to the MME in order to periodically execute TAU (Tracking Area Update) as providing location information.
  • TAU Track Area Update
  • the MME transmits an ULR (Update Location Request) message to the HSS in order to update the TA (Tracking Area) of the UE.
  • the MME transmits an ULR message in which an Active APN (Access Point Name) AVP (Attribute Value Pair) including a PGW ID of the PGW used for communication with the UE is set to the HSS.
  • an Active APN Access Point Name
  • AVP At this time, the MME transmits an ULR message in which an Active APN (Access Point Name) AVP (Attribute Value Pair) including a PGW ID of the PGW used for communication with the UE is set to the HSS.
  • the MME establishes the PDN Connection used for communication with the UE even when the MME receives any message other than the TAU Request message from the UE.
  • a ULR message in which an Active APN (Access Point Name) AVP (Attribute Value Pair) including the PGW ID of the PGW may be transmitted to the HSS.
  • the HSS can hold the PGW ID deleted by the resumption in association with the UE again by receiving the ULR message in which the Active APN AVP is set. Thereby, even after restarting, HSS can hold
  • the recovery procedure after restart of HSS in Non-Patent Document 2 is based on the premise that the UE executes TAU in an area that does not involve MME change. Specifically, the UE transmits a TAU Request message to the MME that manages LICH as Not Confirmed. When the LICH of the UE that has transmitted the TAU Request message is Not Confirmed, the MME sends the ULR message in which the Active APN AVP including the PGW ID of the PGW used for communication with the UE is set to HSS. Send to.
  • the HSS transmits a Reset notification to each MME.
  • each MME manages the LICH of the UE to Not Confirmed for the UE currently managed by the MME.
  • the UE transmits a TAU-Request message to the new changed MME.
  • the changed MME does not manage the LICH of the UE that has transmitted the TAUTARequest message as Not Confirmed.
  • the changed MME does not transmit the PGW ID of the PGW establishing the PDN Connection used for communication with the UE to the HSS.
  • the changed MME can acquire the information of the PGW ID from the MME before the change. Therefore, the MME after the change can be connected to the same PGW as the PGW to which the UE was connected before moving, using the acquired PGW ID.
  • the HSS does not hold the PGW ID of the PGW that has established the PDN Connection used for communication with the UE.
  • the AAA server cannot obtain the PGW ID from the HSS. Therefore, the IP access device in the Non-3GPP communication area cannot detect the PGW that serves as an anchor point. As a result, there arises a problem that the UE cannot be handed over from the 3GPP communication area to the Non-3GPP communication area.
  • An object of the present invention is to provide a mobile communication system, a mobility management device, and a communication method that allow a UE to normally perform a handover from a 3GPP communication area to a non-3GPP communication area even after resumption of HSS in the above situation. And providing a program.
  • the mobile communication system includes a PGW that establishes a PDN connection used for communication with a mobile communication terminal, an HSS that holds a PGW ID that is an identifier of the PGW, and the movement of the mobile communication terminal
  • a mobility management device that performs management.
  • the mobility management device receives the TrackingTrackArea Update message transmitted from the mobile communication terminal, the mobility management device sets the PGW ⁇ ID regardless of the holding state of the PGW ID in the HSS.
  • the set Update Location Request message is transmitted to the HSS.
  • the mobility management device Upon receiving the Tracking ⁇ Area Update message transmitted from the mobile communication terminal, the mobility management device according to the second aspect of the present invention holds the PGW ID of the PGW that established the PDN Connection used for communication with the mobile communication terminal. Regardless of the holding state of the PGW ID in the HSS, the communication section transmits an Update Location Request message in which the PGW ID is set to the HSS.
  • the communication method when receiving the Tracking Area Update message transmitted from the mobile communication terminal, holds the PGW ID of the PGW that has established the PDN Connection used for communication with the mobile communication terminal. Regardless of the holding state of the PGW ID, the Update Location Request message in which the PGW ID is set is transmitted to the HSS.
  • the program according to the fourth aspect of the present invention receives the Tracking Area Update message transmitted from the mobile communication terminal, the program in the HSS that holds the PGW ID of the PGW that established the PDN Connection used for communication with the mobile communication terminal Regardless of the holding state of the PGW ID, the computer is caused to transmit an Update Location Request message in which the PGW ID is set to the HSS.
  • the UE can normally hand over from the 3GPP communication area to the Non-3GPP communication area, a mobile management device, a communication method, and A program can be provided.
  • FIG. 1 is a configuration diagram of a mobile communication system according to a first embodiment.
  • FIG. 3 is a configuration diagram of a mobile communication system according to a second embodiment. It is a block diagram of MME concerning Embodiment 2.
  • FIG. It is a block diagram of UE concerning Embodiment 2.
  • FIG. It is a figure which shows the flow of the TAU process concerning Embodiment 2.
  • FIG. It is a figure which shows the flow of the TAU process concerning Embodiment 2.
  • FIG. It is a figure which shows the Update * Location * Request message concerning Embodiment 2.
  • FIG. 10 is a diagram showing a flow of a handover process according to the second embodiment.
  • FIG. 3 is a configuration diagram of a mobile communication system according to a second embodiment.
  • FIG. 10 is a diagram showing a flow of handover processing according to the fifth embodiment. It is a figure which shows the flow of the authentication process performed among the AAA server concerning Embodiment 5, HSS, and MME.
  • the mobile communication system of FIG. 1 includes a mobile communication terminal 10, a PGW 11, an HSS 12, and a mobility management device 100.
  • the communication system of FIG. 1 is configured using node devices mainly defined in 3GPP.
  • the mobile communication terminal 10 may be a mobile phone terminal, a smart phone terminal, a tablet terminal, or the like.
  • the mobile communication terminal 10 may be an M2M (Machine to Machine) terminal, an MTC (Machine Type to Communication) terminal, or the like.
  • the mobile communication terminal 10 may be a computer device that operates when a processor executes a program stored in a memory.
  • the mobile communication terminal 10 is assumed to be a terminal that can communicate in the 3GPP communication area and the Non-3GPP communication area.
  • the PGW 11, the HSS 12, and the mobility management device 100 are node devices whose functions and operations are defined in 3GPP.
  • the PGW 11, the HSS 12, and the mobility management device 100 may be computer devices that operate when a processor executes a program stored in a memory.
  • the PGW 11 establishes a PDN Connection used for communication with the mobile communication terminal 10.
  • the PDN Connection is established between the mobile communication terminal 10 and the PGW 11 via an eNB (evolved Node B) (not shown) or an RNC (Radio Network Controller) (not shown).
  • eNB and RNC are devices whose functions and operations are defined in 3GPP.
  • the eNB is a base station that supports LTE (Long Term Evolution) as a radio communication method.
  • the RNC is a node device that supports a wireless communication system called 2G (second generation mobile phone) or 3G (third generation mobile phone).
  • the PGW 11 is assigned a PGW ID that is an identifier uniquely identified in the communication system.
  • the communication system may be, for example, EPS (Evolved Packet System).
  • the HSS 12 holds the PGW ID of the PGW that has established the PDN Connection used for communication with the mobile communication terminal 10.
  • the mobility management device 100 performs mobility management related to the mobile communication terminal 10.
  • the movement management may be, for example, managing position information that changes as the mobile communication terminal 10 moves.
  • the mobility management device 100 may be an MME or SGSN (Serving GPRS Support Node).
  • the mobile communication terminal 10 periodically transmits a TAU request message to the mobility management device 100. Specifically, the mobile communication terminal 10 transmits a TAU Request message to the mobility management apparatus 100 via the eNB.
  • Tracking area is composed of one or more cells. Tracking Area is information managed by the mobility management apparatus 100, for example. In other words, the mobility management device 100 manages Tracking Area as the location information of the mobile communication terminal 10. In addition, when the mobile management device 100 calls the mobile communication terminal 10, the mobile management device 100 executes Paging for all mobile communication terminals located in Tracking Area associated with the mobile communication terminal 10.
  • the mobile management device 100 When the mobile management device 100 receives the TAU Request message transmitted from the mobile communication terminal 10, it transmits a ULR message in which the PGW ID is set to the HSS 12 regardless of the holding state of the PGW ID in the HSS 12.
  • the mobility management device 100 transmits a ULR message to the HSS 12 in order to update the location information of the mobile communication terminal 10 managed in the HSS 12.
  • the HSS 12 usually acquires the PGW ID of the PGW 11 that has established the PDN connection that is used for communication with the mobile communication terminal 10 during the ATTACH processing of the mobile communication terminal 10. Further, the HSS 12 holds the mobile communication terminal 10 and the PGW ID of the PGW 11 in association with each other. However, the HSS 12 deletes all the PGW IDs that it holds when it resumes due to the occurrence of a failure. Therefore, the HSS 12 may not hold the PGW ID of the PGW 11 associated with the mobile communication terminal 10.
  • the mobility management device 100 transmits a ULR message in which the PGW ID of the PGW 11 is set regardless of whether or not the HSS 12 holds the PGW ID of the PGW 11 associated with the mobile communication terminal 10.
  • the HSS 12 receives the ULR message, the HSS 12 already holds the PGW ID of the PGW 11, and if there is no change from the received PGW ID, the HSS 12 does not perform the process of updating the PGW ID of the PGW 11 associated with the mobile communication terminal 10. May be.
  • the already held PGW ID is different from the PGW ID set in the ULR message, it is overwritten and saved.
  • the HSS 12 When the HSS 12 receives the ULR message, if it does not hold the PGW ID of the PGW 11, the HSS 12 holds the PGW ID set in the ULR message in association with the mobile communication terminal 10.
  • the mobility management apparatus 100 transmits the ULR message in which the PGW ID is set to the HSS 12 regardless of whether or not the LICH is managed as Not Confirmed for the mobile communication terminal 10 that has transmitted the TAU Request message.
  • the mobility management device 100 determines whether or not the HSS 12 holds the PGW ID of the PGW 11 that has established the PDN connection that is used for communication with the mobile communication terminal 10 that has transmitted the TAU Request message. Regardless, the ULR message in which the PGW ID is set is transmitted to the HSS 12. In other words, the mobility management device 100 transmits the ULR message in which the PGW ID is set to the HSS 12 regardless of whether or not the LICH is managed as Not Confirmed for the mobile communication terminal 10 that has transmitted the TAU Request message.
  • the HSS 12 acquires the PGW ⁇ ⁇ ID of the PGW 11 that has established the PDN Connection used for communication with the mobile communication terminal 10 even when the mobile communication terminal 10 moves with the change of the MME after the restart. be able to. Therefore, even when the MME that has transmitted the TAUTARequest message before the HSS 12 resumes and the MME that has transmitted the TAU Request message after the HSS 12 resumes, the mobile communication terminal 10 performs the handover process of the mobile communication terminal 10. Can be executed normally. Furthermore, even when the mobile communication terminal 10 moves from the 3GPP communication area to the Non-3GPP communication area, the handover process of the mobile communication terminal 10 can be executed normally.
  • the HSS 12 can update the PGW ID of the PGW 11 that has established the PDN Connection used for communication with the mobile communication terminal 10 at the timing when the mobile communication terminal 10 transmits the TAU Request message. Therefore, even if the mobile communication terminal 10 moves with the change of the MME in the 3GPP communication area after the mobile device restarts, and the mobile communication terminal 10 moves to the Non-3GPP communication area, The PGW ID relating to the mobile communication terminal 10 can be transmitted to the AAA server. Therefore, even in the Non-3GPP communication area, since the PGW ID of the PGW 11 serving as the anchor point can be specified, the handover process for the mobile communication terminal 10 can be executed normally. Further, the HSS 12 in FIG. 1 may be referred to as a subscriber information management device.
  • Embodiment 2 The mobile communication system of FIG. 2 has PGW11, HSS12, MME13, MME14, UE20, AAA server 31, IP access device 32, eNB40, eNB41, SGW50, SGW60, and PCRF70. Since the PGW 11 and the HSS 12 are the same as those in FIG. In FIG. 2, the MME 13 is used as the mobility management device 100.
  • the UE 20 corresponds to the mobile communication terminal 10 of FIG.
  • UE 20 is used as a general term for mobile communication terminals in 3GPP.
  • the AAA server 31 is a device that performs authentication of the UE 20 in the Non-3GPP communication area. Further, the AAA server 31 is linked to the HSS 12 and receives from the HSS 12 the PGW ID of the PGW 11 that has established the PDN connection that is used for communication with the UE 20.
  • the IP access device 32 is a device that communicates with the UE 20 in the Non-3GPP communication area.
  • the IP access device 32 may be, for example, an access point in a wireless LAN, or may be a device that performs mobile communication with the UE 20 using a communication method different from the communication method defined in 3GPP.
  • the IP access device 32 may be a Trusted non-3GPP Access network, ePDG (Evolved Packet Data Gateway), or TWAN (Trusted WLAN Access Network) described in Non-Patent Document 3.
  • the IP access device 32 may be a WT (WirelessWireLAN Termination).
  • the IP access device 32 acquires the PGW ID associated with the UE 20 from the AAA server 31.
  • the IP access device 32 accesses the PGW 11 using the acquired PGW ID.
  • the IP access device 32 can relay communication between the PGW 11 serving as an anchor point and the UE 20.
  • ENB40 and eNB41 communicate with UE20 using LTE as a radio system. Moreover, SGW50 relays communication between eNB40 and PGW11, and SGW60 relays communication between eNB41 and PGW11.
  • the PCRF 70 is a node device that manages a QoS policy or the like related to the UE 20.
  • FIG. 2 shows that the UE 20 moves from the Tracking Area managed by the MME 13 to the Tracking Area managed by the MME 14 and further moves to the Non-3GPP communication area.
  • the solid line in FIG. 2 indicates that control information or C-Plane information is transmitted or received.
  • a broken line in FIG. 2 indicates that user data or U-Plane information is transmitted or received.
  • the arrow shown between UE20 of FIG. 2 shows that UE20 is moving.
  • the UE 20 moves from the Tracking Area managed by the MME 13 to the Tracking Area managed by the MME 14 and then moves to the Non-3GPP communication area. Mainly explained.
  • the MME 13 includes a communication unit (the communication unit may be referred to as a transmission and reception unit) 15 and a control unit 16.
  • the communication unit 15 and the control unit 16 may be software or a module that operates when a processor executes a program stored in a memory.
  • the communication unit 15 and the control unit 16 may be hardware such as a circuit or a chip.
  • the communication unit 15 communicates with the eNB 40, the HSS 12, and the MME 14. Further, the communication unit 15 communicates with the UE 20 via the eNB 40.
  • the control unit 16 generates a message to be transmitted to the eNB 40, the MME 14, and the HSS 12 via the communication unit 15, and further analyzes a message received from the eNB 40, the MME 14, and the HSS 12.
  • the control unit 16 transmits a Notify Request message in which the PGW PG ID of the PGW 11 used for communication with the UE 20 is set to the HSS 12 via the communication unit 15. Further, when the control unit 16 receives the TAU request message transmitted from the UE 20 via the eNB 40, the control unit 16 sends the communication unit 15 the ULR message in which the PGW ID of the PGW 11 that has established the PDN connection used for communication with the UE 20 is set. To the HSS 12.
  • control unit 16 manages the LICH related to the UE 20 as Not Confirmed.
  • the UE 20 includes a 3GPP communication unit 21 and a Non-3GPP communication unit 22.
  • the 3GPP communication unit 21 and the Non-3GPP communication unit 22 may be software or a module that operates when a processor executes a program stored in a memory.
  • the 3GPP communication unit 21 and the Non-3GPP communication unit 22 may be hardware such as a circuit or a chip.
  • the 3GPP communication unit 21 performs radio communication with the eNB 40.
  • the 3GPP communication unit 21 performs radio communication with the eNB 40 using LTE as a radio communication method.
  • the 3GPP communication unit 21 transmits an ATTACH Request message to the eNB 40 when the UE 20 transitions from the power OFF state to the ON state. Further, the 3GPP communication unit 21 periodically transmits a TAU request message for transmitting the location information of the UE 20 to the eNB 40.
  • the 3GPP communication unit 21 transmits a TAU Request message to the eNB 40 when moving with a change of the MME.
  • the Non-3GPP communication unit 22 performs wireless communication with the IP access device 32.
  • the Non-3GPP communication unit 22 may perform wireless LAN communication with the IP access device 32 or may communicate with the IP access device 32 using other communication methods.
  • FIGS. 5 and 6 refer to FIG. 5.3.3.1-1 in 3GPP TS 23.401 V13.1.0 (2014-12). 5 and 6, it is assumed that the HSS 12 has restarted (S1) and the HSS 12 has transmitted a Reset notification to the MME 13 and the MME 14 (S2 and S3).
  • the UE 20 determines to start the TAU process (S11). For example, the UE 20 starts the TAU process when it moves to a position that involves a change in MME or when it detects a periodic timing for starting the TAU process.
  • FIG. 5 the flow of the TAU process when the UE 20 moves to a position with an MME change will be described.
  • the UE 20 transmits a TAU request message to the MME 14 via the eNB 41 (S12 and S13).
  • the MME 14 is an MME (new MME) that manages the UE 20 after movement. Further, the MME (old MME) that has managed the UE 20 before moving is assumed to be MME13.
  • the MME 14 transmits a Context Request message to the MME 13 that has managed the UE 20 before moving in order to request transmission of subscriber information and the like regarding the UE 20 (S14).
  • the MME 13 transmits a Context Response message in which subscriber information including the PGW ID related to the UE 20 is set to the MME 14 (S15).
  • the authentication process regarding UE20 is performed between UE20 and MME14, and also between MME14 and HSS12 (S16).
  • the MME 14 transmits a Context Acknowledge message to the MME 13 in order to instruct to change the gateway device accommodating the UE 20 from the SGW (ServingServGateway) 50 to the SGW 60 as the UE 20 moves (S17). .
  • the MME 14 transmits a Create Session Request message to instruct the SGW 60 to generate a communication bearer with the PGW 11 (S18).
  • the SGW 60 transmits a Modify Bearer Request message to the PGW 11 in order to request generation of a communication bearer (S19).
  • the PGW 11 transmits a Modify Bearer Response message to the SGW 60 as a response to the Modify Bearer Request message (S20).
  • the SGW 60 transmits a Create Session Response message to the MME 14 as a response to the Create Session Request message in step S18 (S21). In this way, the UE 20 establishes a PDN Connection with the PGW 11 via the SGW 60.
  • FIG. 7 shows an Update Location Request message in which Active APN AVP is set.
  • FIG. 7 refers to 3GPP TS 29.272 V13.2.0 (2015-06) Table 5.2.1.1.1 / 1.
  • the MME 14 sets the ActiveUEAPN AVP including the PGW ⁇ ⁇ ⁇ ⁇ ID of the PGW 11 that has established the PDN Connection used for communication with the UE 20 in the Update Location Request message. To do.
  • the MME 14 sets Active APN AVP including the PGW ID in the Update Location Request message regardless of whether or not the PGW ID needs to be reset in the HSS12 when the HSS 12 is restarted or reset. Further, the MME 14 acquires the information of the PGW ID from the MME 13 through the Context Response message. Therefore, the MME 14 can connect to the same PGW as the PGW to which the UE was connected before the movement using the acquired PGW ⁇ ID, and can normally perform the handover even after the HSS is resumed.
  • FIG. 8 refers to FIG. 8.2.2-1 in Non-Patent Document 3.
  • a communication bearer is set between SGW 60 and PGW 11 using PMIPv6 or GTP tunnel (S31).
  • the UE 20 detects the IP access device 32 (S32).
  • an authentication process is executed between the UE 20 and the IP access device 32 (S33).
  • the authentication regarding UE20 is performed also in a network (S34).
  • the AAA server 31 inquires the HSS 12, acquires the PGW ID of the PGW 11 that has established the PDN connection used for communication with the UE 20, and transmits the PGW ID to the AAA proxy 71.
  • AAA Proxy 71 is used as a proxy server of the AAA server 31.
  • the UE 20 executes L3 Attach Trigger processing with the IP access device 32 (S35). Thereby, for example, the UE 20 transmits information on the APN used at the time of communication in the 3GPP communication area to the IP access device 32.
  • Gateway Control Session Establishment Protocol is executed between the IP access device 32 and the vPCRF (Policy and Charging Rules) Function 72, and further between the vPCRF 72 and the hPCRF 73 (S36).
  • the PCRF is a node device that manages a QoS policy or the like related to the UE 20.
  • the vPCRF 72 executes policy control related to the UE 20 in the roaming destination network when the UE 20 roams.
  • the hPCRF 73 executes policy control related to the UE 20 in the home network of the UE 20.
  • step S36 the hPCRF 73 transmits the QoS policy information regarding the UE 20 to the vPCRF 72. Further, the vPCRF 72 transmits (transfers) QoS policy information and the like related to the UE 20 to the IP access device 32.
  • the IP access device 32 transmits Proxy Binding Update to the PGW 11 using the PGW ID of the PGW 11 received in Step S34 (S37).
  • Proxy Binding Update the PGW 11 associates the PDN Connection used for communication with the UE 20 in the 3GPP communication area and the communication bearer or communication connection in the Non-3GPP communication area, and executes the handover process of the UE 20.
  • the HSS 12 establishes a PDN Connection used for communication with the UE 20 every time the UE 20 executes the TAU process. You can get PGW ID.
  • the MME 14 sends the PGW ID of the PGW11 that establishes the PDN Connection used for communication with the UE20 to the HSS 12 every time the TAU process of the UE20 is performed. To do.
  • HSS12 establishes PDN Connection used for communication with UE20 from MME14 which performs movement management about UE20 after movement.
  • the PGW ID of the PGW 11 being received can be received (S22).
  • the AAA server 31 can acquire the PGW ID related to the UE 20 from the HSS 12 even after the HSS 12 is restarted. Therefore, the UE 20 can access the same PGW before and after the movement.
  • a normal handover can be performed from the 3GPP communication area to the Non-3GPP communication area. As a result, the UE can continue to receive services from the external network via the same PGW even at the movement destination.
  • the MME is mainly used as the mobility management apparatus 100.
  • SGSN 110 and SGSN 111 may be used instead of the MME.
  • the MME 13 in FIG. 2 is replaced with the SGSN 110
  • the MME 14 is replaced with the SGSN 111.
  • eNB 40 and eNB 41 in FIG. 2 are replaced with RNC 130 and RNC 131.
  • the HSS 12 in FIG. 2 is replaced with the HLR 120.
  • the UE 20 executes a RAU (Routing Area Update) process instead of the TAU process, and transmits a RAU Request to the SGSN 111 via the RNC 131.
  • RAU Radio Access Area Update
  • the HSS 12 has restarted and a Reset notification is transmitted to the MME 13. Further, the MME 13 manages the LICH in the UE 20 as Not Confirmed by receiving the Reset notification.
  • the UE 20 moves from a position managed by the MME 13 to a position managed by the MME 14. In such a situation, the UE 20 executes the TAU process after step S11 in FIG.
  • Steps S11 to S14 are the same as in the second embodiment.
  • step S14 when the MME 13 specifies that the TAU process related to the UE 20 is being executed, in step S15, the MME 13 transmits a Context Response message that sets that the LICH is managed as Not Confirmed to the MME 14.
  • FIG. 10 shows that MME / SGSN UE EPS PDN Connections indicating that there is data set for each PDN Connection is set in the Context Response message.
  • IE Information Element
  • Type of MME / SGSN UE UE EPS PDN Connections indicates PDN Connection.
  • LICH is added to Indication Flags of the Context Response message.
  • the IE ⁇ Type of Indication Flags indicates Indication.
  • FIG. 11 refers to 3GPP TS29.274 V13.2.0 (2015-06) Figure 8.12-1.
  • FIG. 11 shows that a flag related to LICH is set in Bit 5 of Octet 9. For example, when 1 is set in Bit 5 of Octet 9, it indicates that the Active APN needs to be set in the Update Location Request message when the MME 14 sends an Update Location Request message to the HSS 12. . That is, when 1 is set in Bit 5 of Octet 9, it indicates that LICH is Not Confirmed.
  • FIG. 12 refers to 3GPP TS29.274 V13.2.0 (2015-06) Table 7.3.6-2.
  • FIG. 12 shows that a Context identifier indicating the identification information of PDN Connection is added.
  • Context Identifier is information used to identify PDN Connection, and is used when transmitting Active-APN AVP described later. Therefore, the MME 13 sets a Context Identifier in the Context Response message with a flag indicating that the LICH related to the UE 20 is Not Confirmed.
  • the MME 13 transmits a Context Response message including the PGW ID of the PGW 11 to the MME 14.
  • the information about the PGW ID is transferred from the MME 13 to the MME 14 using the MME / SGSN, UE, EPS, PDN, Connections, and IE, but the information about the PGW ID may be transferred using a dedicated IE.
  • step S22 the MME 14 transmits the ULR message in which the Active-APN AVP including the PGW ID of the PGW 11 that has established the PDN Connection used for communication with the UE 20 is set to the HSS 12 because the LICH related to the UE 20 is Not Confirmed.
  • step S15 when the MME 14 receives a Context Response message in which 1 is set in Bit 5 of Octet 9 in the area indicating Indication, the MME 14 sets the Context Identifier set in the Context Response message in Step S15 to Active-APN AVP. Set to.
  • step S22 the MME 14 transmits to the HSS 12 an ULR message in which an Active-APNAPAVP including the PGW ID of the PGW 11 that has established the PDN Connection used for communication with the UE 20 is set.
  • the MME 14 that has managed the UE 20 after movement can grasp the LICH management state related to the UE 20 by the Context Response message transmitted from the MME 13 that has managed the UE 20 before movement. it can. That is, even if the MME that manages the UE 20 changes from the MME 13 to the MME 14 due to the movement of the UE 20, the management state of the LICH can be taken over to the MME 14. Therefore, the HSS 12 can acquire the PGW ID of the PGW 11 that has established the PDN connection used for communication with the UE 20 by receiving the ULR message from the MME 14.
  • the AAA server 31 establishes a PDN Connection used for communication with the UE 20 from the resumed HSS 12.
  • the PGW ID of the PGW 11 can be acquired. Therefore, the UE 20 can normally hand over from the 3GPP communication area to the Non-3GPP communication area.
  • the HSS 12 has restarted and a Reset notification is transmitted to the MME 13. Also, the MME 13 manages the LICH in the UE 20 as Not Confirmed by receiving the Reset notification.
  • the UE 20 moves from a position managed by the MME 13 to a position managed by the MME 14. In such a situation, the UE 20 executes the TAU process after step S11 in FIG.
  • ARD Access-Restriction-Data
  • Table 7.7.731 / 1 stipulates that the HSS 12 holds Access-Restriction-Data (ARD) indicating the access network to which the use of the UE 20 is restricted.
  • the ARD is defined by associating an area where the ARD is set and the restriction content. For example, when 1 is set in Bit 5 of the area indicating ARD, it indicates that the UE 20 is not permitted to perform handover to the Non-3GPP communication area. In addition, when 0 is set in each Bit in the area indicating ARD, it indicates that the use of the access network associated with each Bit is not restricted.
  • the HSS 12 transmits information related to the ARD to the MME 13. For example, in periodic TAU processing of the UE 20, the HSS 12 sets information related to ARD in an Update Location Answer message that is a response message of the Update Location Request message, and transmits the information to the MME 13.
  • step S14 of FIG. 5 when the MME 13 specifies that the TAU process related to the UE 20 is being executed, the MME 13 confirms whether 0 is set in the Bit 5 of the area indicating the ARD of the UE 20.
  • the fact that 0 is set in Bit 5 of the area indicating ARD indicates that the UE 20 is permitted to perform handover to the Non-3GPP communication area.
  • the MME 13 When the MME 13 specifies that the TAU process related to the UE 20 is being executed, the MME 13 transmits instruction information to the MME 14 when confirming that Bit 5 of the area indicating the ARD of the UE 20 is set to 0. Specifically, the MME 13 sends information instructing to transmit to the HSS 12 an ULR message in which an Active-APN including the PGW ID of the PGW 11 that has established the PDN connection used for communication with the UE 20 is set in the Context Response message. The Context Response message is sent to the MME 14. Bit 5 in the area indicating ARD is a flag indicating the state of HTN3AA (Handover To Non 3GPP- Access Not Allowed). It should be noted that this state may be defined by something other than ARD, and the MME 13 may notify the MME 14 by setting this in a Context Response message.
  • the MME 14 When the MME 14 obtains information instructing to transmit the ULR message including the Active-APN AVP to the HSS 12 in Step S15, the MME 14 transmits the ULR message in which the Active-APN including the PGW ID is set to the HSS 12 in Step S22. .
  • the MME 13 establishes a PDN Connection used for communication with the UE 20 when the Bit 5 of the area indicating the ARD of the UE 20 is set to 0 and the LICH is managed as Not Confirmed.
  • Information indicating that the ULR message in which the Active-APN including the ID is set is transmitted to the HSS 12 may be set in the Context Response message. Then, the MME 13 may transmit the Context Response message to the MME 14.
  • the MME 13 can transmit the instruction information regarding the content of the ULR message to the MME 14 that manages the UE 20 after movement, using the restriction content indicated in the ARD. That is, the MME 13 can instruct the MME 14 to set the PGW ID of the PGW 11 for which the UE 20 has set the communication bearer in the ULR message.
  • the MME 14 sets the Active-APN in the ULR message only when the UE 20 is permitted to perform handover to the Non-3GPP communication area. Thereby, when the processing in the fourth embodiment is executed, the information amount of the ULR message can be reduced as compared with the first and second embodiments in which the Active-APN is always set in the ULR message.
  • SGSN 110 and 111 may be used instead of MME 13 and 14, RNC 130 and RNC 131 may be used instead of eNB 40 and eNB 41, and HLR 120 is used instead of HSS 12. May be.
  • the UE 20 executes the RAU process instead of the TAU process, and transmits the RAU request to the SGSN 111 via the RNC 131.
  • FIG. 14 refers to FIG. 8.2.2-1 in Non-Patent Document 3.
  • a communication bearer is set between SGW 60 and PGW 11 using PMIPv6 or GTP tunnel (S31).
  • the UE 20 detects the IP access device 32 (S32).
  • an authentication process is executed between the UE 20 and the IP access device 32 (S33).
  • the authentication regarding UE20 is performed also in a network (S34).
  • the HSS 12 / AAA server 31 needs to transmit the PGW ID of the PGW 11 that has established the PDN Connection used for communication with the UE 20 to the AAA Proxy 71, but the HSS 12 restarts so that the HSS 12 May have been deleted from the HSS 12 for the PGW 11 of the PGW 11 that has established the PDN Connection used for communication with the UE 20.
  • the HSS 12 makes an inquiry to the MME 14 that is the destination of the UE 20, thereby acquiring the PGW ID of the PGW 11 that has established the PDN connection used for communication with the UE 20, and then transmits the PGW ID to the AAA proxy 71.
  • AAA Proxy 71 is used as a proxy server of AAA server 31.
  • the AAA server 31, the HSS 12, and the PGW ID of the PGW 11 that has established the PDN connection that the HSS 12 uses for communication with the UE 20 due to the restart of the HSS 12 using FIG. 15 are deleted from the HSS 12. Details of the authentication process performed between the MMEs 14 will be described.
  • the HSS 12 sends a RESET message to the related MME (S42).
  • the MME 14 that has received the RESET message lists all the subscribers accommodated in the HSS 12 to which the RESET message has been sent, sets it as a RESET ANSWER message, and transmits the RESET ANSWER message to the HSS 12 (S43).
  • the subscriber list set here may be composed of IMSI (International Mobile Subscriber Identity) or another User Identity.
  • the HSS 12 can manage the association between the subscriber and the MME that the subscriber moves to after the RESET process by holding the subscriber list in units of MME. This association enables an inquiry operation from the HSS 12 to the MME 14, which will be described below. However, the association may be used for other operations such as SMS reception, network-initiated subscriber location search, service provision from the MTC server, and the like. I do not care.
  • the HSS 12 receives the STa Access Authentication and Authorization request message from the AAA server 31 (S45).
  • STa Access Authentication andIMSAuthorization Request message a parameter equivalent to IMSI is set as User Identity.
  • the HSS 12 does not hold the PGW ID for the User Identity, the HSS 12 further transmits a Status request message to the MME.
  • This message includes subscriber information corresponding to IMSI and an information element indicating that information on the PGW ID of the PGW 11 that has established the PDN connection used for communication with the UE 20 is requested.
  • the Status request message may be a RESET REQUEST message or another message.
  • the MME 14 sets information on the PGW ID of the PGW 11 that has established the PDN Connection used for communication with the UE 20, and transmits a Status answer message to the HSS 12 (S47). Further, the Status ⁇ ⁇ ⁇ ⁇ ⁇ ⁇ answer message may be a RESET ANSWER message or another message.
  • the HSS 12 transmits to the AAA server 31 a Trusted non-3GPP Access Authentication and Authorization Answer message in which information on the PGW ID of the PGW 11 that has established the PDN Connection used for communication with the UE 20 is set (S48).
  • step S34 From here, it returns to FIG. 14 and continues and demonstrates after step S34.
  • the AAA proxy 71 transmits the PGW ID received from the HSS 12 / AAA server 31 to the IP access device 32.
  • the UE 20 executes L3 Attach Trigger processing with the IP access device 32 (S35). Thereby, for example, the UE 20 transmits information on the APN used at the time of communication in the 3GPP communication area to the IP access device 32.
  • Gateway Control Session Establishment Protocol is executed between the IP access device 32 and the vPCRF (Policy and Charging Rules) Function 72, and further between the vPCRF 72 and the hPCRF 73 (S36).
  • the PCRF is a node device that manages a QoS policy or the like related to the UE 20.
  • the vPCRF 72 executes policy control related to the UE 20 in the roaming destination network when the UE 20 roams.
  • the hPCRF 73 executes policy control related to the UE 20 in the home network of the UE 20.
  • step S36 the hPCRF 73 transmits the QoS policy information regarding the UE 20 to the vPCRF 72. Further, the vPCRF 72 transmits (transfers) QoS policy information and the like related to the UE 20 to the IP access device 32.
  • the IP access device 32 transmits Proxy Binding Update to the PGW 11 using the PGW ID of the PGW 11 received in Step S34 (S37).
  • Proxy Binding Update the PGW 11 associates the PDN Connection used for communication with the UE 20 in the 3GPP communication area and the communication bearer or communication connection in the Non-3GPP communication area, and executes the handover process of the UE 20.
  • the HSS 12 makes an inquiry to the MME 14 that is the destination of the UE 20 using the authentication processing request from the AAA server 31 as a trigger. I can do things. As a result, the HSS 12 can acquire the PGW ID of the PGW 11 that has established the PDN connection used for communication with the UE 20.
  • HSS12 establishes PDN Connection used for communication with UE20 from MME14 which performs movement management about UE20 after movement.
  • the PGW ID of the PGW 11 being received can be received.
  • the AAA server 31 can acquire the PGW ID related to the UE 20 from the HSS 12 even after the HSS 12 is restarted. Therefore, the UE 20 can access the same PGW before and after the movement.
  • a normal handover can be performed from the 3GPP communication area to the Non-3GPP communication area. As a result, the UE can continue to receive services from the external network via the same PGW even at the movement destination.
  • the UE 20 does not communicate with the MME and the UE 20 moves from the 3GPP communication area to the Non-3GPP communication area.
  • the AAA server 31 can acquire the PGW ID of the PGW 11 that has established the PDN connection used for communication with the UE 20, and has the same effect.
  • the MME is mainly used as the mobility management apparatus 100.
  • SGSN 110 and SGSN 111 may be used instead of the MME.
  • the MME 13 in FIG. 2 is replaced with the SGSN 110
  • the MME 14 is replaced with the SGSN 111.
  • eNB 40 and eNB 41 in FIG. 2 are replaced with RNC 130 and RNC 131.
  • the HSS 12 in FIG. 2 is replaced with the HLR 120.
  • the UE 20 executes a RAU (Routing Area Update) process instead of the TAU process, and transmits a RAU Request to the SGSN 111 via the RNC.
  • RAU Radio Access Area Update
  • the present invention has been described as a hardware configuration, but the present invention is not limited to this.
  • the present invention can also realize the processing in each node device constituting the mobile communication system by causing a CPU (Central Processing Unit) to execute a computer program.
  • a CPU Central Processing Unit
  • Non-transitory computer readable media include various types of tangible storage media (tangible storage medium).
  • Examples of non-transitory computer-readable media include magnetic recording media (eg flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (eg magneto-optical discs), CD-ROMs (Read Only Memory), CD-Rs, CD-R / W, semiconductor memory (for example, mask ROM, PROM (Programmable ROM), EPROM (Erasable ROM), flash ROM, RAM (Random Access Memory)) are included.
  • 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.
  • a PGW for establishing a PDN connection used for communication with a mobile communication terminal;
  • An HSS holding a PGW ID which is an identifier of the PGW;
  • a mobility management device for performing mobility management of the mobile communication terminal, The mobility management device When receiving the Tracking Area Update message transmitted from the mobile communication terminal, the mobile communication system transmits an Update Location Request message in which the PGW ID is set to the HSS regardless of the holding state of the PGW ID in the HSS.
  • the first mobility management device includes: Sending a Context Response message in which registration information about the mobile communication terminal is set to the second mobility management device;
  • the second mobility management device is The mobile communication system according to appendix 1, wherein when the information indicating that the HSS has been resumed is set in the registration information, an Update Location Request message in which the PGW ID is set is transmitted to the HSS.
  • the first mobility management device includes: Instructing the second mobility management device to send an Update Location Request message in which the PGW ID is set to the HSS based on at least one of Access-Restriction-Data and information indicating that the HSS has been resumed
  • the mobile communication system according to attachment 1 wherein a Context Response message in which instruction information is set is transmitted.
  • the first mobility management device includes: A Context Response message in which a Context Identifier that is an identifier of the PDN Connection is set is transmitted to the second mobility management device;
  • the second mobility management device is The mobile communication system according to Supplementary Note 2 or 3, wherein the Update Location Request message in which an Active APN AVP including the Context Identifier and the PGW ID is set is transmitted to the HSS.
  • Appendix 5 When the Tracking Area Update message transmitted from the mobile communication terminal is received, the PGW is held regardless of the holding state of the PGW ID in the HSS that holds the PGW ID of the PGW that has established the PDN Connection used for communication with the mobile communication terminal.
  • a mobility management device comprising: a communication unit that transmits an Update Location Request message in which an ID is set to the HSS.
  • the communication unit is When receiving a Context Response message in which registration information related to the mobile communication terminal transmitted from the first mobility management device is set, and information indicating that the HSS has been resumed is set in the registration information, the PGW The mobility management device according to appendix 5, wherein an Update Location Request message in which an ID is set is transmitted to the HSS.
  • the communication unit is A Context Response message in which a Context Identifier that is an identifier of the PDN Connection is set is received from the first mobility management device, and the Update Location Request message in which an Active APN AVP including the Context Identifier and the PGW ID is set is sent to the HSS.
  • the mobility management device according to appendix 6, wherein (Appendix 8)
  • the communication unit is The mobility management device according to appendix 5, wherein a Context Response message in which registration information related to the mobile communication terminal including information indicating that the HSS has been resumed is transmitted to the second mobility management device.
  • the communication unit is Instructing the second mobility management device to send an Update Location Request message in which the PGW ID is set to the HSS based on at least one of Access-Restriction-Data and information indicating that the HSS has been resumed
  • the mobility management device according to appendix 5, wherein a Context Response message in which instruction information to be set is transmitted.
  • the communication unit is The mobility management device according to appendix 8 or 9, wherein a Context Response message in which a Context Identifier that is an identifier of the PDN Connection is set is transmitted to the second mobility management device.

Landscapes

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

Abstract

L'objectif de la présente invention est de fournir un système de communication mobile permettant à un terminal de communication mobile d'effectuer un transfert de façon classique depuis une zone de communication 3 GPP vers une zone de communication Non-3 GPP, même après le redémarrage d'un dispositif de gestion d'informations d'abonné. Un système de communication mobile selon la présente invention comprend : une passerelle PGW qui établit une connexion PDN qui est utilisée en communication avec un terminal de communication mobile ; un dispositif de gestion d'informations d'abonné qui conserve un identifiant (ID) de PGW qui est un identifiant de la PGW ; et un dispositif de gestion de mobilité qui effectue la gestion de mobilité du terminal de communication mobile. Lors de la réception d'un message de mise à jour de zone de localisation ou d'un message de mise à jour de zone d'acheminement qui sont transmis depuis le terminal de communication mobile, le dispositif de gestion de mobilité transmet au dispositif de gestion d'informations d'abonné un message avec lequel la PGW ID est ajustée.
PCT/JP2016/002983 2015-09-30 2016-06-21 Système de communication mobile, dispositif de gestion de mobilité, procédé de communication, terminal de communication mobile, et support non transitoire lisible par ordinateur WO2017056349A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
KR1020177036218A KR102028271B1 (ko) 2015-09-30 2016-06-21 이동 통신 시스템, 이동 관리 장치, 통신 방법, 이동 통신 단말, 및 비-일시적 컴퓨터 판독가능 매체
RU2016146737A RU2652453C1 (ru) 2015-09-30 2016-06-21 Система мобильной связи, устройство управления мобильностью, способ связи, терминал мобильной связи и не-временный считываемый компьютером носитель

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2015193034A JP6025232B1 (ja) 2015-09-30 2015-09-30 移動通信システム、ｍｍｅ、通信方法、及びプログラム
JP2015-193034 2015-09-30

Publications (1)

Publication Number Publication Date
WO2017056349A1 true WO2017056349A1 (fr) 2017-04-06

Family

ID=57326579

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2016/002983 WO2017056349A1 (fr) 2015-09-30 2016-06-21 Système de communication mobile, dispositif de gestion de mobilité, procédé de communication, terminal de communication mobile, et support non transitoire lisible par ordinateur

Country Status (6)

Country Link
JP (1) JP6025232B1 (fr)
KR (1) KR102028271B1 (fr)
AR (2) AR106170A1 (fr)
JO (1) JO3802B1 (fr)
RU (2) RU2652453C1 (fr)
WO (1) WO2017056349A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
RU2728538C1 (ru) * 2017-04-27 2020-07-30 ЭлДжи ЭЛЕКТРОНИКС ИНК. Способ для выполнения связанной с регистрацией amf процедуры посредством udm в системе беспроводной связи и устройство для этого

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108924959B (zh) * 2017-04-26 2020-11-27 华为技术有限公司 无线通信的方法、amf和ran

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101370001B (zh) * 2007-08-15 2011-01-05 华为技术有限公司 一种信息传递方法
WO2012148210A2 (fr) * 2011-04-29 2012-11-01 Lg Electronics Inc. Procédé pour le traitement de données associées à la gestion de session et à la gestion de mobilité
KR101573156B1 (ko) * 2011-08-12 2015-12-01 엘지전자 주식회사 무선 통신 시스템에서 아이들 모드 시그널링 감소에 관련된 데이터를 처리하는 방법

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "PGW Identity Notification in TAU procedure", 3GPP TSG-SA WG2#103, S2-141621 , 3GPP, 23 May 2014 (2014-05-23), XP050804983 *
NEC: "An Issue on HSS failure recover procedure", 3GPP TSG-CT WG4#71, C4-151950, 3GPP, 20 November 2015 (2015-11-20), XP051039137 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
RU2728538C1 (ru) * 2017-04-27 2020-07-30 ЭлДжи ЭЛЕКТРОНИКС ИНК. Способ для выполнения связанной с регистрацией amf процедуры посредством udm в системе беспроводной связи и устройство для этого
US10798556B2 (en) 2017-04-27 2020-10-06 Lg Electronics Inc. Method for performing a procedure related to AMF registration by UDM in wireless communication system and apparatus for same
US11096037B2 (en) 2017-04-27 2021-08-17 Lg Electronics Inc. Method for performing a procedure related to AMF registration by UDM in wireless communication system and apparatus for same
US11700524B2 (en) 2017-04-27 2023-07-11 Lg Electronics Inc. Method for performing a procedure related to AMF registration by UDM in wireless communication system and apparatus for same

Also Published As

Publication number Publication date
AR120619A2 (es) 2022-03-02
KR102028271B1 (ko) 2019-10-02
RU2018111698A3 (fr) 2019-02-27
RU2691856C2 (ru) 2019-06-18
JP6025232B1 (ja) 2016-11-16
JP2017069760A (ja) 2017-04-06
RU2652453C1 (ru) 2018-04-26
JO3802B1 (ar) 2021-01-31
KR20180008694A (ko) 2018-01-24
RU2018111698A (ru) 2019-02-27
AR106170A1 (es) 2017-12-20

Similar Documents

Publication Publication Date Title
US10070288B2 (en) Method for dynamically switching mobile network, subscription manager, and user equipment
JP4938131B2 (ja) パケットスイッチングドメインにおける端末の位置登録方法及び装置
US8855045B2 (en) Method and system for controlling establishment of local IP access
JP6568231B2 (ja) ユーザー・プレーンベアラの確立を制御する方法及び装置
JP5800025B2 (ja) 移動通信ネットワークシステム、通信制御方法およびそのプログラム
EP3799519A1 (fr) Méthode et appareils pour la transfert sans coupure entre réseaux 3gpp et non-3gpp
US11064541B2 (en) Terminal apparatus, mobility management entity (MME), and communication control method
WO2015062098A1 (fr) Procédé de sélection de réseau et dispositif de réseau central
JP2010539758A (ja) Ｌｔｅシステムにおいて、ユーザ静的ｉｐアドレスのアドレッシングをサポートする方法、システムおよび装置
WO2009117879A1 (fr) Procédé pour indiquer la gestion de support de la passerelle de desserte
WO2014166089A1 (fr) Procédé et dispositif de régulation de l'encombrement
US9602958B2 (en) Communication of information between devices in communication networks
US20220345997A1 (en) User equipment and core network apparatus
EP2790457A1 (fr) Procédé et dispositif pour la gestion d'une connexion d'accès à un réseau local
WO2017028637A1 (fr) Procédé et dispositif de traitement destinés à la récupération de passerelle
JP6025232B1 (ja) 移動通信システム、ｍｍｅ、通信方法、及びプログラム
CN102014452B (zh) 一种本地ip访问连接实现移动性的方法和系统
US11343754B2 (en) Terminal apparatus, mobility management entity (MME), and communication control method
JP6601876B2 (ja) コアネットワークノード、及び方法
JP2021057924A (ja) ゲートウェイ装置、及び制御方法
WO2014086208A1 (fr) Procédé, appareil et mme pour traiter un service de réseau à commutation de circuits
US20240163784A1 (en) User equipment (ue) and communication control method performed by ue
EP4322690A1 (fr) Équipement utilisateur (ue) et procédé de commande de communication exécuté par l'ue
WO2016112774A1 (fr) Procédé de mise à jour de position et unité de gestion de mobilité
WO2014180405A1 (fr) Procédé de téléavertissement et centre de commutation mobile

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2016146737

Country of ref document: RU

Kind code of ref document: A

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16850536

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20177036218

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16850536

Country of ref document: EP

Kind code of ref document: A1