WO2020073199A1 - Procédés et appareils de déclenchement de dispositif - Google Patents

Procédés et appareils de déclenchement de dispositif Download PDF

Info

Publication number
WO2020073199A1
WO2020073199A1 PCT/CN2018/109503 CN2018109503W WO2020073199A1 WO 2020073199 A1 WO2020073199 A1 WO 2020073199A1 CN 2018109503 W CN2018109503 W CN 2018109503W WO 2020073199 A1 WO2020073199 A1 WO 2020073199A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
request
gateway node
management node
node
Prior art date
Application number
PCT/CN2018/109503
Other languages
English (en)
Inventor
Qiong SONG
Hui GU
Xiaoming Li
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to PCT/CN2018/109503 priority Critical patent/WO2020073199A1/fr
Publication of WO2020073199A1 publication Critical patent/WO2020073199A1/fr

Links

Images

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4588—Network directories; Name-to-address mapping containing mobile subscriber information, e.g. home subscriber server [HSS]
    • 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/08—Mobility data transfer
    • H04W8/12—Mobility data transfer between location registers or mobility servers

Definitions

  • Embodiments of the disclosure generally relate to wireless communication, and, more particularly, to methods and apparatuses for device triggering.
  • CIoT Cellular internet of things
  • 3GPP 3rd generation partnership project
  • UE user equipment
  • EPS evolved packet system
  • PDN packet data network
  • the UE may send an Attach Request message including an EPS session management (ESM) Dummy Message instead of a PDN Connection Request message.
  • EMM EPS session management
  • the mobility management entity (MME) supports EMM-REGISTERED without PDN connection, the establishment of a default EPS bearer context during the attach procedure is optional.
  • the UE and MME have no active EPS bearer contexts associated to the UE. Also the serving gateway (SGW) and PDN gateway (PGW) have no default EPS bearer context because no session was created.
  • SGW serving gateway
  • PGW PDN gateway
  • One of the objects of the disclosure is to provide an improved solution for device triggering.
  • a method implemented at a packet gateway node comprises receiving, from a server, downlink traffic destined to a terminal device that has no packet data connection with the packet gateway node.
  • the method further comprises performing a triggering procedure via at least a subscriber management node such that a mobility management node corresponding to the terminal device can be triggered to establish the packet data connection.
  • the performing the triggering procedure via at least the subscriber management node comprises sending, to the subscriber management node, a first request for obtaining information related to the terminal device.
  • the performing the triggering procedure via at least the subscriber management node further comprises receiving, from the subscriber management node, the information related to the terminal device.
  • the information related to the terminal device is reachability status of the terminal device.
  • the information related to the terminal device is an identifier (ID) of the mobility management node corresponding to the terminal device.
  • the performing the triggering procedure via at least the subscriber management node further comprises sending, to a serving gateway node, a second request for triggering establishment of the packet data connection.
  • the second request includes the ID of the mobility management node and an internet protocol (IP) address of the packet gateway node.
  • IP internet protocol
  • the first request is a Send Routing Information Request message and the information related to the terminal device is received in a Send Routing Information Response message.
  • the second request is a PGW Downlink Triggering Notification message.
  • a method implemented at a subscriber management node comprises receiving, from a packet gateway node, a first request for obtaining information related to a terminal device.
  • the method further comprises obtaining the information related to the terminal device.
  • the method further comprises sending the information related to the terminal device to the packet gateway node.
  • the information related to the terminal device is reachability status of the terminal device.
  • the obtaining the information related to the terminal device comprises sending, to a mobility management node, a second request for triggering establishment of a packet data connection between the terminal device and the packet gateway node.
  • the obtaining the information related to the terminal device further comprises receiving, from the mobility management node, the reachability status of the terminal device.
  • the second request includes an IP address of the packet gateway node.
  • the information related to the terminal device is an ID of a mobility management node corresponding to the terminal device.
  • the obtaining the information related to the terminal device comprises determining the ID of the mobility management node corresponding to the terminal device.
  • the first request is a Send Routing Information Request message and the information related to the terminal device is sent in a Send Routing Information Response message.
  • the second request is an Insert Subscriber Data Request message having a Downlink Data Request bit set to indicate that there is downlink traffic from the packet gateway node.
  • the reachability status of the terminal device is received in an Insert Subscriber Data Answer message.
  • a method implemented at a mobility management node comprises receiving, from a subscriber management node or a serving gateway node, a request for triggering establishment of a packet data connection between a terminal device and a packet gateway node.
  • the method further comprises performing a connection establishment procedure based on the request such that the packet data connection is established.
  • the request includes an IP address of the packet gateway node.
  • the method further comprises sending, to the subscriber management node, reachability status of the terminal device.
  • the request is an Insert Subscriber Data Request message having a Downlink Data Request bit set to indicate that there is downlink traffic from the packet gateway node, or the request is a PGW Downlink Triggering Notification message.
  • the request is an Insert Subscriber Data Request message having a Downlink Data Request bit set to indicate that there is downlink traffic from the packet gateway node.
  • the reachability status of the terminal device is sent in an Insert Subscriber Data Answer message.
  • a method implemented at a serving gateway node comprises receiving, from a packet gateway node, a first request for triggering establishment of a packet data connection between a terminal device and the packet gateway node.
  • the method further comprises sending, to a mobility management node, a second request for triggering establishment of the packet data connection, based on the first request.
  • the first request includes an ID of a mobility management node corresponding to the terminal device and an IP address of the packet gateway node.
  • the second request includes the IP address of the packet gateway node.
  • each of the first and second requests is a PGW Downlink Triggering Notification message.
  • a packet gateway node comprises at least one processor and at least one memory.
  • the at least one memory contains instructions executable by the at least one processor, whereby the packet gateway node is operative to receive, from a server, downlink traffic destined to a terminal device that has no packet data connection with the packet gateway node.
  • the packet gateway node is further operative to perform a triggering procedure via at least a subscriber management node such that a mobility management node corresponding to the terminal device can be triggered to establish the packet data connection.
  • the packet gateway node is operative to perform the method according to the above aspect.
  • a subscriber management node comprises at least one processor and at least one memory.
  • the at least one memory contains instructions executable by the at least one processor, whereby the subscriber management node is operative to receive, from a packet gateway node, a first request for obtaining information related to a terminal device.
  • the subscriber management node is further operative to obtain the information related to the terminal device.
  • the subscriber management node is further operative to send the information related to the terminal device to the packet gateway node.
  • the subscriber management node is operative to perform the method according to the above aspect.
  • a mobility management node comprises at least one processor and at least one memory.
  • the at least one memory contains instructions executable by the at least one processor, whereby the mobility management node is operative to receive, from a subscriber management node or a serving gateway node, a request for triggering establishment of a packet data connection between a terminal device and a packet gateway node.
  • the mobility management node is further operative to perform a connection establishment procedure based on the request such that the packet data connection is established.
  • the mobility management node is operative to perform the method according to the above aspect.
  • a serving gateway node comprises at least one processor and at least one memory.
  • the at least one memory contains instructions executable by the at least one processor, whereby the serving gateway node is operative to receive, from a packet gateway node, a first request for triggering establishment of a packet data connection between a terminal device and the packet gateway node.
  • the serving gateway node is further operative to send, to a mobility management node, a second request for triggering establishment of the packet data connection, based on the first request.
  • the serving gateway node is operative to perform the method according to the above aspect.
  • the computer program product comprises instructions which when executed by at least one processor, cause the at least one processor to perform the method according to the above aspect.
  • the computer readable storage medium comprises instructions which when executed by at least one processor, cause the at least one processor to perform the method according to the above aspect.
  • a packet gateway node comprises a reception module for receiving, from a server, downlink traffic destined to a terminal device that has no packet data connection with the packet gateway node.
  • the packet gateway node further comprises a triggering module for performing a triggering procedure via at least a subscriber management node such that a mobility management node corresponding to the terminal device can be triggered to establish the packet data connection.
  • a subscriber management node comprises a reception module for receiving, from a packet gateway node, a first request for obtaining information related to a terminal device.
  • the subscriber management node further comprises an obtaining module for obtaining the information related to the terminal device.
  • the subscriber management node further comprises a sending module for sending the information related to the terminal device to the packet gateway node.
  • a mobility management node comprises a reception module for receiving, from a subscriber management node or a serving gateway node, a request for triggering establishment of a packet data connection between a terminal device and a packet gateway node.
  • the mobility management node further comprises a connection establishment module for performing a connection establishment procedure based on the request such that the packet data connection is established.
  • a serving gateway node comprises a reception module for receiving, from a packet gateway node, a first request for triggering establishment of a packet data connection between a terminal device and the packet gateway node.
  • the serving gateway node further comprises a sending module for sending, to a mobility management node, a second request for triggering establishment of the packet data connection, based on the first request.
  • device triggering can be achieved through the cooperation between a packet gateway node and a subscriber management node such that a simplified procedure can be provided for device triggering.
  • FIG. 1 is a diagram showing an exemplary wireless communication system into which an embodiment of the disclosure is applicable;
  • FIG. 2 is a flowchart illustrating a method implemented at a packet gateway node according to an embodiment of the disclosure
  • FIG. 3 is a flowchart for explaining the method of FIG. 2;
  • FIG. 4 is a flowchart for explaining the method of FIG. 2;
  • FIG. 5 is a flowchart illustrating a method implemented at a subscriber management node according to an embodiment of the disclosure
  • FIG. 6 is a flowchart for explaining the method of FIG. 5;
  • FIG. 7 is a flowchart illustrating a method implemented at a mobility management node according to an embodiment of the disclosure
  • FIG. 8 is a flowchart illustrating a method implemented at a serving gateway node according to an embodiment of the disclosure
  • FIG. 9 is a flowchart illustrating an exemplary process according to an embodiment of the disclosure.
  • FIG. 10 is a flowchart illustrating another exemplary process according to an embodiment of the disclosure.
  • FIG. 11 is a block diagram showing an apparatus suitable for use in practicing some embodiments of the disclosure.
  • FIG. 12 is a block diagram showing a packet gateway node according to an embodiment of the disclosure.
  • FIG. 13 is a block diagram showing a subscriber management node according to an embodiment of the disclosure.
  • FIG. 14 is a block diagram showing a mobility management node according to an embodiment of the disclosure.
  • FIG. 15 is a block diagram showing a serving gateway node according to an embodiment of the disclosure.
  • the device triggering procedure when the device triggering procedure is performed, it is required to get subscription information about whether the UE is allowed to be triggered by a specific SCS/AS. But there is no interface between PGW and HSS to support the device triggering procedure based on the current architecture. When the UE is attached without PDN connection, the PGW has no UE information to trigger device triggering delivery procedure.
  • the PGW cannot trigger the service request procedure when downlink signaling or data is received from the SCS/AS because there is no default bearer associated with the UE and the PGW, and the PGW has no information about which MME and SGW serve the UE.
  • the SMS-SC and SCEF are not mandatory network elements for the operator, especially for the specific enterprise network. In the shared network, some small operators could deploy their own PGW and share the SGW and MME with other operators but without the SMS-SC or SCEF.
  • the solution proposed in 3GPP TS 23.682 for device triggering procedure is over Tsp interface.
  • the only way is using the device triggering function and the device triggers are delivered via mobile terminated (MT) -SMS.
  • MT mobile terminated
  • This will introduce extra transmission delay, more power consumption and chipset complexity which is not efficient for IoT devices (e.g. remote control, software upgrade, etc. ) such as smart meters which need low power consumption and low cost.
  • SCEF performs device triggering towards UE to establish a PDN connection of type Non-IP to the default access point name (APN) by using T4 SMS device triggering to a pre-defined SMS Application Port ID.
  • APN access point name
  • This is mainly for Non-IP PDN connection over T6a interface and also has a big dependency with SMS over T4 support.
  • IP multimedia subsystem simply referred to as IMS IP multimedia subsystem simply referred to as IMS
  • OPEX operating expense
  • CAEX capital expenditure
  • some of the IoT application servers use IP address to identify narrow band (NB) -IoT device. So they want PGW to save the related context of UE, including IP address even after PDN is deactivated, and want the same PGW to be selected for the later PDN activation. Then the PGW needs to trigger this PDN activation once there is any downlink IoT service. But the PGW does not know which SGW and MME serve this UE when the UE is attached without PDN. The PGW needs to require the related information which is not defined in 3GPP 23.682.
  • the present disclosure proposes improved solutions for device triggering.
  • the solutions will be described in detail with reference to FIGs. 1-15.
  • FIG. 1 is a diagram showing an exemplary wireless communication system into which an embodiment of the disclosure is applicable.
  • the wireless communication system comprises a user equipment (UE) 102, a radio access network (RAN) 104, a serving general packet radio service (GPRS) support node (SGSN) 106, a mobility management entity (MME) 108, a serving gateway (SGW) 110, a gateway GPRS support node (GGSN) /packet data network (PDN) gateway (PGW) 112, a service capability exposure function (SCEF) 114, a service capability server (SCS) 116, an application server (AS) 118 and a home subscriber server (HSS) 120.
  • UE user equipment
  • RAN radio access network
  • GPRS general packet radio service
  • MME mobility management entity
  • SGW serving gateway
  • GGSN gateway GPRS support node
  • PDN packetet data network gateway
  • SCEF service capability exposure function
  • SCS service capability server
  • AS application server
  • HSS home
  • the UE 102 can communicate through a radio access communication link with the RAN 104.
  • the UE may also be referred to as, for example, terminal device, access terminal, mobile station, mobile unit, subscriber station, or the like. It may refer to any end device that can access a wireless communication network and receive services therefrom.
  • the UE may include a portable computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and playback appliance, a mobile phone, a cellular phone, a smart phone, a tablet, a wearable device, a personal digital assistant (PDA) , or the like.
  • PDA personal digital assistant
  • a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network equipment.
  • the UE may be a machine-to-machine (M2M) device, which may, in a 3GPP context, be referred to as a machine-type communication (MTC) device.
  • M2M machine-to-machine
  • MTC machine-type communication
  • machines or devices may include sensors, metering devices such as power meters, industrial machineries, bikes, vehicles, or home or personal appliances, e.g. refrigerators, televisions, personal wearables such as watches, and so on.
  • the RAN 104 may include, for example, a universal mobile telecommunications system (UMTS) terrestrial RAN (UTRAN) , a global system for mobile communication (GSM) enhanced data rate for GSM evolution (EDGE) RAN (GERAN) , and/or an evolved universal terrestrial RAN (E-UTRAN) .
  • UMTS universal mobile telecommunications system
  • UTRAN universal mobile telecommunications system
  • GSM global system for mobile communication
  • EDGE enhanced data rate for GSM evolution
  • GERAN global system for mobile communication
  • E-UTRAN can each include radio network controller (RNC) nodes to control communications through radio base stations providing radio access communication links to UEs that are within their respective communication service cells.
  • the E-UTRAN can include radio base station nodes (eNodeBs or eNBs) that can provide the combined functionality of the RNC nodes and base stations of the UTRAN and the GERAN.
  • eNodeBs or eNBs radio base station nodes
  • the SGSN 106 is a core network node in the UMTS and has a user-plane function and a control-plane function.
  • the user-plane function of the SGSN 106 can transfer user data packets of the UE 102 between the RAN 104 and the GGSN/PGW 112.
  • the control-plane function of the SGSN 106 can carry out mobility management of the UE 102, bearer management and the like.
  • the MME 108 is a core network node in evolved packet system (EPS) and can carry out the mobility management of the UE 102, the bearer management, and the like.
  • the SGW 110 is a packet transfer node in the core network of the EPS.
  • the SGW 110 can transfer user data packets of the UE 102 between the RAN 104 and the GGSN/PGW 112.
  • the GGSN is a core network node in the UMTS.
  • the PGW is a core network node in the EPS.
  • the GGSN/PGW 112 means either the GGSN or the PGW or both.
  • the GGSN/PGW 112 is a user-plane packet transfer node in the core network and can transfer user data packets of the UE 102.
  • the GGSN/PGW 112 can serve as a gateway to an external PDN and provide the UE 102 with the connectivity to the external PDN.
  • the SCEF 114 can securely expose the services and capabilities provided by 3GPP networks by providing access to the services and capabilities through homogenous network application programming interfaces (APIs) defined by open mobile alliance (OMA) , GSM alliance (GSMA) and possibly other standardization bodies.
  • the SCS 116 can make open service access (OSA) standard interfaces accessible by application and provide an abstraction of network protocol for application developers. As a gateway between applications and the network, the SCS 120 can accomplish mapping of OSA interfaces onto network protocols and vice versa.
  • the AS 118 may be a type of server designed to install, operate and host applications and associated services for users.
  • the HSS 120 is a control-plane node in the core network of 3GPP public land mobile network (PLMN) and can manage subscriber information of the UE 102.
  • PLMN public land mobile network
  • the wireless communication system may further comprise a mobile switching center (MSC) 122, a short message service (SMS) -service center (SC) /gateway mobile switching center (GMSC) /interworking MSC (IWMSC) 124, a short message entity (SME) 126, an IP-short message (SM) -gateway (GW) 128, a machine-type communication (MTC) -interworking function (IWF) 130, a charge data function (CDF) /charge gateway function (CGF) 132 and an MTC-authentication, authorization and accounting (AAA) 134.
  • MSC mobile switching center
  • SMS short message service
  • GMSC gateway mobile switching center
  • IWMSC interworking MSC
  • SME short message entity
  • SME IP-short message
  • GW IP-short message
  • MTC machine-type communication
  • IWF charge data function
  • CGF charge gateway function
  • AAA MTC-authentication, authorization and accounting
  • the MME 108, the SGW 110, the PGW 112 and the HSS 120 are merely exemplary examples of the components in the wireless communication system and may be replaced by components with similar functionalities.
  • the MME may be replaced by an access and mobility management function (AMF)
  • the SGW and the PGW may be replaced by a user plane function (UPF)
  • the HSS may be replaced by a unified data management (UDM) .
  • 5G fifth generation
  • CN fifth generation
  • AMF access and mobility management function
  • UPF user plane function
  • UDM unified data management
  • FIG. 2 is a flowchart illustrating a method implemented at a packet gateway node according to an embodiment of the disclosure.
  • the packet gateway node may take the form of a PGW, a UPF, or any other entity having similar functionality.
  • the packet gateway node receives, from a server, downlink traffic destined to a terminal device that has no packet data connection with the packet gateway node.
  • the server may be an SCS or an AS.
  • the downlink traffic may comprise data or signaling.
  • the downlink traffic may be received in a message including a first ID of the terminal device.
  • the first ID may be an external ID or a mobile subscriber international integrated services digital network (ISDN) number (MSISDN) .
  • ISDN mobile subscriber international integrated services digital network
  • the packet data connection may be a PDN connection or a protocol data unit (PDU) session.
  • the terminal device may be registered into the network without PDN connection (e.g. the terminal device is in the state of EMM-REGISTERED without PDN connection) , or the PDN connection of the terminal device may be released because it is in idle state for a long time. If the packet gateway node finds that it has no bearer context associated with the terminal device, it may determine to trigger the packet data connection.
  • the packet gateway node performs a triggering procedure via at least a subscriber management node such that a mobility management node corresponding to the terminal device can be triggered to establish the packet data connection.
  • the subscriber management node may take the form of an HSS, a UDM, or any other entity having similar functionality.
  • the mobility management node may take the form of an MME, an AMF, or any other entity having similar functionality.
  • the mobility management node corresponding to the terminal device may refer to the mobility management node serving the terminal device or having a coverage area within which the terminal device is located.
  • block 204 may be implemented as blocks 306 and 310 of FIG. 3.
  • the trigger procedure is performed via the subscriber management node, which will be described later with respect to blocks 504-1 and 504-2 of FIG. 5.
  • the packet gateway node sends, to the subscriber management node, a first request for obtaining information related to the terminal device.
  • the first request may be sent through an interface between the packet gateway node and the subscriber management node.
  • the interface may be a new introduced interface called Gh interface. This interface may be implemented based on various authentication, authorization and accounting (AAA) protocols such as Diameter protocol.
  • AAA authentication, authorization and accounting
  • the information related to the terminal device may comprise information which may facilitate or be helpful for the triggering procedure or downlink traffic delivery procedure towards the terminal device.
  • the information related to the terminal device is reachability status of the terminal device.
  • the first request may include a second ID of the terminal device and an IP address of the packet gateway node.
  • the second ID may be determined by the packet gateway node by mapping the first ID to the second ID.
  • the second ID may be an international mobile subscriber identification number (IMSI) .
  • the first request may be a Send Routing Information Request message.
  • the packet gateway node receives, from the subscriber management node, the information related to the terminal device. That is, the reachability status of the terminal device is received in the first option.
  • the information may indicate that the terminal device is reachable or temporarily unreachable. In the latter case, the information may optionally indicate the duration time after which the terminal device can be reached.
  • the information may be received in a Send Routing Information Response message.
  • block 204 may be implemented as blocks 408-412 of FIG. 4.
  • the triggering procedure is performed via the subscriber management node and a serving gateway node.
  • the packet gateway node sends, to the subscriber management node, a first request for obtaining information related to the terminal device.
  • the information related to the terminal device is an ID of the mobility management node corresponding to the terminal device.
  • the first request may include the second ID of the terminal device and the IP address of the packet gateway node.
  • the first request may be a Send Routing Information Request message.
  • the packet gateway node receives, from the subscriber management node, the information related to the terminal device. That is, the ID of the mobility management node is received in the second option.
  • the ID of the mobility management node may be received in a Send Routing Information Response message.
  • the packet gateway node sends, to a serving gateway node, a second request for triggering establishment of the packet data connection.
  • the serving gateway node may take the form of an SGW, a UPF, or any other entity having similar functionality.
  • the serving gateway node may be a default serving gateway node locally configured in the packet gateway node.
  • the second request may include the second ID of the terminal device, the IP address of the packet gateway node, and the ID of the mobility management node received from the subscriber management node.
  • the second request may be a PGW Downlink Triggering Notification message. In this way, based on the ID of the mobility management node, the serving gateway node may request the corresponding mobility management node to establish the packet data connection.
  • a new interface is introduced between the packet gateway node and the subscriber management node.
  • FIG. 5 is a flowchart illustrating a method implemented at a subscriber management node according to an embodiment of the disclosure.
  • the subscriber management node may take the form of an HSS, a UDM, or any other entity having similar functionality.
  • the subscriber management node receives, from a packet gateway node, a first request for obtaining information related to a terminal device.
  • Block 502 may correspond to block 306 in the first option or block 408 in the second option and its details are omitted here.
  • the subscriber management node obtains the information related to the terminal device.
  • block 504 may be implemented as blocks 504-1 and 504-2 shown in FIG. 6.
  • the subscriber management node sends, to a mobility management node, a second request for triggering establishment of a packet data connection between the terminal device and the packet gateway node.
  • the mobility management node may take the form of an MME, an AMF, or any other entity having similar functionality. For example, through location update from the terminal device, the subscriber management node can know which mobility management node is serving the terminal device or has a coverage area within which the terminal device is located. Thus, the second request can be sent to such serving mobility management node.
  • the second request may include the second ID of the terminal device and the IP address of the packet gateway node.
  • the second request may be an Insert Subscriber Data Request message having a Downlink Data Request bit set to indicate that there is downlink traffic from the packet gateway node.
  • the subscriber management node receives, from the mobility management node, the reachability status of the terminal device.
  • the reachability status of the terminal device may be received in an Insert Subscriber Data Answer message.
  • block 504 may be implemented as block 504-3 shown in FIG. 6.
  • the subscriber management node determines the ID of the mobility management node corresponding to the terminal device. As mentioned above, the subscriber management node can know which mobility management node is serving the terminal device. Thus, the ID of such serving mobility management node can be determined.
  • the subscriber management node sends the information related to the terminal device to the packet gateway node. Block 506 corresponds to block 310 or 410 and its details are omitted here.
  • FIG. 7 is a flowchart illustrating a method implemented at a mobility management node according to an embodiment of the disclosure.
  • the mobility management node receives, from a subscriber management node or a serving gateway node, a request for triggering establishment of a packet data connection between a terminal device and a packet gateway node.
  • the request may include the second ID of the terminal device and the IP address of the packet gateway node.
  • the request is received from the subscriber management node.
  • the request may be an Insert Subscriber Data Request message having a Downlink Data Request bit set to indicate that there is downlink traffic from the packet gateway node.
  • the request is received from the serving gateway node.
  • the request may be a PGW Downlink Triggering Notification message.
  • the mobility management node performs a connection establishment procedure based on the request such that the packet data connection is established. Since the request includes the IP address of the packet gateway node, the mobility management node can establish the packet data connection with the packet gateway node identified by the IP address.
  • the connection establishment procedure may be implemented as blocks 907-914 of FIG. 9 or blocks 1009-1016 of FIG. 10, which will be described later.
  • the method may further comprise sending, to the subscriber management node, reachability status of the terminal device.
  • FIG. 8 is a flowchart illustrating a method implemented at a serving gateway node according to an embodiment of the disclosure. This method corresponds to the second option described above.
  • the serving gateway node receives, from a packet gateway node, a first request for triggering establishment of a packet data connection between a terminal device and the packet gateway node.
  • the first request may include an ID of a mobility management node corresponding to the terminal device and an IP address of the packet gateway node.
  • the first request may be a PGW Downlink Triggering Notification message.
  • the serving gateway node sends, to a mobility management node, a second request for triggering establishment of the packet data connection, based on the first request.
  • the mobility management node may be identified by the ID received from the packet gateway node.
  • the second request may include the IP address of the packet gateway node which is received at block 802. In this way, the mobility management node can establish the packet data connection with the packet gateway node identified by the IP address.
  • the second request may be a PGW Downlink Triggering Notification message.
  • FIG. 9 is a flowchart illustrating an exemplary process according to an embodiment of the disclosure.
  • the server is an SCS/AS
  • the packet gateway node is a PGW
  • the subscriber management node is an HSS
  • the mobility management node is an MME.
  • This solution corresponds to the above first option and is based on HSS triggered paging procedure.
  • the SCS/AS determines the need to trigger a UE. If the SCS/AS has no contact details for a PGW, it may determine the IP address (es) (and optionally port (s) ) of the PGW by performing a domain name system (DNS) query using the External Identifier or using a locally configured PGW identifier.
  • DNS domain name system
  • the SCS/AS sends the data or signaling to the PGW in a message including the External Identifier or MSISDN to identify the UE.
  • the SCS/AS may identify a UE with an External Identifier or an MSISDN and the PGW may resolve (or map) the External Identifier or the MSISDN to an IMSI.
  • the PGW may buffer the downlink data packet and start the device triggering procedure.
  • the PGW sends to the HSS a Send Routing Information Request message including the PGW IP address, to request the UE status, when no PDN connectivity is established for this UE.
  • a new message “Send Routing Information Request” is introduced between the PGW and the HSS. This message is sent through a new introduced Gh interface.
  • the PGW may check if the SCS/AS is authorized to trigger the UE.
  • the HSS sends an Insert Subscriber Data Request message to the MME to retrieve information about the UE status.
  • the “Downlink Data Request” bit in the message is set to indicate to the MME that there is downlink data from the PGW.
  • the message also includes the PGW IP address. In this way, when the UE is attached without PDN, the PGW can trigger the network triggered service request procedure through the HSS.
  • the MME may save the received PGW IP address.
  • the MME sends an Insert Subscriber Data Answer message to the HSS. If the UE is in EPS connection management (ECM) -CONNECTED state or ECM-IDLE state in which paging can be performed, then the MME accepts the “Downlink Data Request” . If the MME is aware of the UE being temporarily unreachable or if the MME knows that the UE is not reachable while using power saving functions, then the Insert Subscriber Data Answer message returned by the MME has the cause “temporarily unreachable” and optionally includes the duration time after which the UE can be reached. Thus, new information elements (IEs) are introduced in the Insert Subscriber Data Request and Insert Subscriber Data Answer messages.
  • the HSS sends a Send Routing Information Response message to the PGW. Thus, a new message “Send Routing Information Response” is introduced between the PGW and the HSS. This message is sent through the new Gh interface.
  • the MME sends a paging request message to the UE.
  • the UE sends to the MME a service request message as the paging response.
  • the MME creates a session to the corresponding PGW identified by the PGW IP address. Specifically, the MME sends a Create Session Request message to the PGW and the PGW replies with a Create Session Response message.
  • the MME sends an S1-AP Initial Context Setup Request message to the eNB. Note that if control plane CIoT EPS optimization applies to the PDN connection, an S1-AP Downlink non-access stratum (NAS) transport message may be used.
  • NAS Downlink non-access stratum
  • the eNB sends an S1-AP Initial Context Setup Complete message to the MME.
  • the UE sends an Activate Default EPS Bearer Context Accept message to the MME.
  • the MME sends a Modify Bearer Request message to the PGW and the PGW acknowledges by sending Modify Bearer Response to the MME.
  • the PGW sends its buffered downlink data packets to the UE. In this way, the service triggered by the SCS/AS can be served when non-IP/IP over SGi and even attachment without PDN connection between the UE and the PGW are used.
  • FIG. 10 is a flowchart illustrating another exemplary process according to an embodiment of the disclosure.
  • the server is an SCS/AS
  • the packet gateway node is a PGW
  • the subscriber management node is an HSS
  • the serving gateway node is an SGW
  • the mobility management node is an MME.
  • Blocks 1001-1002 are the same as blocks 901-902 and their details are omitted here.
  • the PGW sends a Send Routing Information Request message to the HSS, to identify which MME is serving the UE when no PDN connectivity is established.
  • the MME identifier where the UE is located can be obtained from the HSS.
  • the PGW may check if the SCS/AS is authorized to trigger the UE.
  • the HSS sends to the PGW a Send Routing Information response message including the MME identifier for the requested UE.
  • the PGW sends, to the local configured default SGW, a PGW Downlink Triggering Notification message including the IMSI, the MME identifier and the PGW IP address for control plane.
  • the PGW may know by local configuration whether the selected SGW is connected with the MME which is indicated by the MME identifier from the HSS. Since the default SGW is preconfigured by the operator, this solution depends on the network deployment.
  • the SGW sends, to the MME identified by the MME identifier, a PGW Downlink Triggering Notification message including the PGW IP address.
  • the MME responds to the SGW with a PGW Downlink Triggering Acknowledge message. Since it is the serving MME for the UE, the related information indicated by the PGW may be saved.
  • the SGW sends a PGW Downlink Triggering Acknowledge message to the PGW.
  • the MME starts paging if the UE is in ECM-IDLE state. Note that if the MME restarts, then the MME may do IMSI paging to force the UE to reattach or do normal paging if there is any UE context replication in MME pool, which is all up to implementation. If the MME is aware of the UE being temporarily unreachable, or if the MME knows that the UE is not reachable while using power saving functions, then the MME may send to the PGW a PGW Downlink Triggering Acknowledge message which includes the cause “temporarily unreachable” and optionally includes the duration time after which the UE can be reached.
  • Blocks 1010-1016 are the same as blocks 908-914 and their details are omitted here. It should be noted that two blocks shown in succession in the figures may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
  • SMS-based architecture proposed in 3GPP TS 23.682
  • PGW/GGSN when PGW/GGSN receives downlink data, first of all the PGW/GGSN should inform the SGSN. Secondly the SGSN should inform SMS-SC through Gd. Thirdly the SMS-SC should inform the MME through SGd to wake up the UE.
  • the three steps based on the current architecture can be skipped since the PGW can inform the MME through the SGW directly. Without the transmission time on Gd and SGd interfaces and handling time in the SMS-SC, the latency can be lower.
  • SMS has more data to send and will occupy more bandwidth in Uu interface. It increases the failure rate especially in the extended coverage.
  • FIG. 11 is a block diagram showing an apparatus suitable for use in practicing some embodiments of the disclosure.
  • the apparatus 1100 may include a processor 1110, a memory 1120 that stores a program, and a communication interface 1130 for communicating data with other external devices through wired and/or wireless communication.
  • the program includes program instructions that, when executed by the processor 1110, enable the apparatus 1100 to operate in accordance with the embodiments of the present disclosure, as discussed above. That is, the embodiments of the present disclosure may be implemented at least in part by computer software executable by the processor 1110, or by hardware, or by a combination of software and hardware.
  • the memory 1120 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memories, magnetic memory devices and systems, optical memory devices and systems, fixed memories and removable memories.
  • the processor 1110 may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multi-core processor architectures, as non-limiting examples.
  • FIG. 12 is a block diagram showing a packet gateway node according to an embodiment of the disclosure.
  • the packet gateway node 1200 comprises a reception module 1202 and a triggering module 1204.
  • the reception module 1202 may be configured to receive, from a server, downlink traffic destined to a terminal device that has no packet data connection with the packet gateway node, as described above with respect to block 202.
  • the triggering module 1204 may be configured to perform a triggering procedure via at least a subscriber management node such that a mobility management node corresponding to the terminal device can be triggered to establish the packet data connection, as described above with respect to block 204.
  • FIG. 13 is a block diagram showing a subscriber management node according to an embodiment of the disclosure.
  • the subscriber management node 1300 comprises a reception module 1302, an obtaining module 1304 and a sending module 1306.
  • the reception module 1302 may be configured to receive, from a packet gateway node, a first request for obtaining information related to a terminal device, as described above with respect to block 502.
  • the obtaining module 1304 may be configured to obtain the information related to the terminal device, as described above with respect to block 504.
  • the sending module 1306 may be configured to send the information related to the terminal device to the packet gateway node, as described above with respect to block 506.
  • FIG. 14 is a block diagram showing a mobility management node according to an embodiment of the disclosure.
  • the mobility management node 1400 comprises a reception module 1402 and a connection establishment module 1404.
  • the reception module 1402 may be configured to receive, from a subscriber management node or a serving gateway node, a request for triggering establishment of a packet data connection between a terminal device and a packet gateway node, as described above with respect to block 702.
  • the connection establishment module 1404 may be configured to perform a connection establishment procedure based on the request such that the packet data connection is established, as described above with respect to block 704.
  • FIG. 15 is a block diagram showing a serving gateway node according to an embodiment of the disclosure.
  • the serving gateway node comprises a reception module 1502 and a sending module 1504.
  • the reception module 1502 may be configured to receive, from a packet gateway node, a first request for triggering establishment of a packet data connection between a terminal device and the packet gateway node, as described above with respect to block 802.
  • the sending module 1504 may be configured to send, to a mobility management node, a second request for triggering establishment of the packet data connection, based on the first request, as described above with respect to block 804.
  • the modules described above may be implemented by hardware, or software, or a combination of both.
  • the various exemplary embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto.
  • firmware or software which may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto.
  • While various aspects of the exemplary embodiments of this disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • the exemplary embodiments of the disclosure may be practiced in various components such as integrated circuit chips and modules. It should thus be appreciated that the exemplary embodiments of this disclosure may be realized in an apparatus that is embodied as an integrated circuit, where the integrated circuit may comprise circuitry (as well as possibly firmware) for embodying at least one or more of a data processor, a digital signal processor, baseband circuitry and radio frequency circuitry that are configurable so as to operate in accordance with the exemplary embodiments of this disclosure.
  • exemplary embodiments of the disclosure may be embodied in computer-executable instructions, such as in one or more program modules, executed by one or more computers or other devices.
  • program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types when executed by a processor in a computer or other device.
  • the computer executable instructions may be stored on a computer readable medium such as a hard disk, optical disk, removable storage media, solid state memory, RAM, etc.
  • the function of the program modules may be combined or distributed as desired in various embodiments.
  • the function may be embodied in whole or in part in firmware or hardware equivalents such as integrated circuits, field programmable gate arrays (FPGA) , and the like.
  • FPGA field programmable gate arrays

Landscapes

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

Abstract

L'invention concerne des procédés et des appareils de déclenchement de dispositif. Selon un mode de réalisation, un nœud de passerelle de paquets reçoit, en provenance d'un serveur, un trafic de liaison descendante destiné à un dispositif terminal qui ne dispose d'aucune connexion de données par paquets avec le nœud de passerelle de paquets. Le nœud de passerelle de paquets réalise une procédure de déclenchement par l'intermédiaire d'au moins un nœud de gestion d'abonné de telle sorte qu'un nœud de gestion de mobilité correspondant au dispositif terminal peut être déclenché pour établir la connexion de données par paquets.
PCT/CN2018/109503 2018-10-09 2018-10-09 Procédés et appareils de déclenchement de dispositif WO2020073199A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/109503 WO2020073199A1 (fr) 2018-10-09 2018-10-09 Procédés et appareils de déclenchement de dispositif

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/109503 WO2020073199A1 (fr) 2018-10-09 2018-10-09 Procédés et appareils de déclenchement de dispositif

Publications (1)

Publication Number Publication Date
WO2020073199A1 true WO2020073199A1 (fr) 2020-04-16

Family

ID=70164450

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/109503 WO2020073199A1 (fr) 2018-10-09 2018-10-09 Procédés et appareils de déclenchement de dispositif

Country Status (1)

Country Link
WO (1) WO2020073199A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140219248A1 (en) * 2011-07-11 2014-08-07 Interdigital Patent Holdings, Inc. Systems and Methods for Establishing and Maintaining Multiple Cellular Connections and/or Interfaces
US20160286385A1 (en) * 2015-03-25 2016-09-29 Lg Electronics Inc. Method and apparatus for monitoring user equipment reachability in wireless communication system
US20170048112A1 (en) * 2015-08-14 2017-02-16 Telefonaktiebolaget L M Ericsson (Publ) Systems and methods for establishing a packet data network connection for a wireless communication device
CN106982473A (zh) * 2016-01-19 2017-07-25 中兴通讯股份有限公司 传输通道的建立方法、移动性管理实体、网元设备及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140219248A1 (en) * 2011-07-11 2014-08-07 Interdigital Patent Holdings, Inc. Systems and Methods for Establishing and Maintaining Multiple Cellular Connections and/or Interfaces
US20160286385A1 (en) * 2015-03-25 2016-09-29 Lg Electronics Inc. Method and apparatus for monitoring user equipment reachability in wireless communication system
US20170048112A1 (en) * 2015-08-14 2017-02-16 Telefonaktiebolaget L M Ericsson (Publ) Systems and methods for establishing a packet data network connection for a wireless communication device
CN106982473A (zh) * 2016-01-19 2017-07-25 中兴通讯股份有限公司 传输通道的建立方法、移动性管理实体、网元设备及系统

Similar Documents

Publication Publication Date Title
US10244502B2 (en) Identifiers and triggers for capillary devices
US10419964B2 (en) Method and apparatus for machine-to-machine communication registration
JP5767394B2 (ja) マシンタイプ通信デバイスをトリガして同期させるための方法および装置
JP6015868B2 (ja) 通信デバイス、基地局及び通信装置並びにそれらの通信制御方法
US9609632B2 (en) Method and device for managing RAN resources in wireless communication system
US11706321B2 (en) System and method for using T8 API to deliver data over an IP path
US10660067B2 (en) Systems and methods for efficient signaling of IoT devices in a wireless telecommunications network
US20240121591A1 (en) Methods and apparatuses for event monitoring
WO2020103662A1 (fr) Procédé et appareil de surveillance d'événement
WO2020168673A1 (fr) Procédés et appareils d'établissement de connexion
WO2021165856A1 (fr) Support partiel d'informations de réseau d'accès
US10057871B2 (en) Data transmission method and base station
WO2020073199A1 (fr) Procédés et appareils de déclenchement de dispositif
US11522962B2 (en) Methods and apparatuses for IP and non-IP data communication using a unified interface
US11323841B2 (en) Methods and apparatuses for exposure of presence reporting area functionality
WO2020155177A1 (fr) Procédés et appareils permettant de surveiller un service d'événement pour un groupe de dispositifs terminaux
US20230328628A1 (en) System and method for using t8 api to deliver data over an ip path
US11451996B2 (en) Methods and apparatuses for PLMN rate control
WO2021000915A1 (fr) Procédés et appareils de distribution de données non ip

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: 18936660

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18936660

Country of ref document: EP

Kind code of ref document: A1