WO2013065996A1 - Serveur et procédé pour terminal de communication de type machine - Google Patents

Serveur et procédé pour terminal de communication de type machine Download PDF

Info

Publication number
WO2013065996A1
WO2013065996A1 PCT/KR2012/008797 KR2012008797W WO2013065996A1 WO 2013065996 A1 WO2013065996 A1 WO 2013065996A1 KR 2012008797 W KR2012008797 W KR 2012008797W WO 2013065996 A1 WO2013065996 A1 WO 2013065996A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
trigger
mtc
server
information
Prior art date
Application number
PCT/KR2012/008797
Other languages
English (en)
Korean (ko)
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
Priority claimed from KR1020110117281A external-priority patent/KR20130049130A/ko
Application filed by 주식회사 케이티 filed Critical 주식회사 케이티
Publication of WO2013065996A1 publication Critical patent/WO2013065996A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/02—Inter-networking arrangements

Definitions

  • a machine type communication (MTC) server requests triggering for a machine type communication terminal through a wireless network of a mobile communication operator, and the terminal receiving the trigger request initiates communication with the machine type communication server. Terminal triggering.
  • MTC machine type communication
  • Machine Type Communication is a form of data communication that represents M2M (machine to machine) communication, where one or more entities do not or require minimal human interaction.
  • An MTC device user terminal such as an electric meter, gas meter, or vending machine equipped with a mobile communication module may control an MTC device and collect data through a wireless network of a mobile carrier (for example, a service). It can communicate with Capability Server or MTC application server.
  • the MTC user may periodically allow the MTC device to start data communication through the wireless network of the mobile communication provider to transmit data to the MTC server.
  • the MTC device initiates data communication through the mobile operator's wireless network at the request of the MTC server for control and management of the MTC device, collection of data on demand, and the like. You can also communicate with the MTC server.
  • the MTC device transmits a trigger request of the MTC server through the wireless network of the mobile communication operator, and the MTC device receiving the trigger request initiates data communication through the wireless network of the mobile communication operator to communicate with the MTC server. This is called triggering.
  • Machine type communication-interworking function may be used to relay or convert device triggering requests generated from a plurality of MTC servers in a wireless network of a mobile carrier that must accommodate a large number of MTC devices.
  • the MTC-IWF may be implemented as a separate entity's equipment or as part of other wireless network equipment.
  • the MTC-IWF can relay or convert signal information for operating a specific function of the mobile operator's wireless network through a reference point with the MTC server, and MTC server authentication, authorization of control messages, identifier mapping, etc. Can be done.
  • an MTC-IWF or an MTC server receiving a failure result continuously generates a unnecessary network load by repeatedly repeating a trigger delivery request. It aims to prevent.
  • the external server communication unit for receiving a trigger request of the terminal from the external server;
  • a management server communication unit for querying a management server for managing subscriber information with a network internal identifier of the terminal and information of a relay server relaying a trigger message to the terminal;
  • a relay server communication unit which transmits a trigger request of the terminal to the relay server, and when the triggering of the terminal fails, the relay server communication unit retransmits the trigger request within a valid time included in the trigger request. It provides a network connection server.
  • an external identifier of a terminal is received from a manganese access server that receives a trigger request of the terminal from an external server and transmits the trigger request to the terminal, and transmits an internal identifier of the terminal to the network between the network and the terminal.
  • a network connection server communication unit transmitting information of a relay server relaying a trigger message;
  • a trigger information storage unit for storing an internal identifier mapped to an external identifier of the terminal and information of a relay server relaying the terminal;
  • a trigger state storage unit for storing information indicating that there is a trigger request message waiting for retransmission in the network connection server when the triggering of the terminal fails.
  • a trigger transmission request message to a terminal is received from a network connection server receiving a trigger request of a terminal from an external server and delivered to the terminal, and a trigger transmission confirmation or failure message is sent to the network connection server.
  • a network connection server communication unit for transmitting;
  • a terminal communication unit transmitting the trigger delivery request message to the terminal and receiving the trigger delivery confirmation message from the terminal;
  • a trigger state storage unit for storing information indicating that there is a trigger request message waiting for retransmission in the network connection server when the trigger transfer request message transmission fails to the terminal.
  • Another embodiment of the present invention is a terminal trigger request delivery method executed in a network connection server that receives a trigger request of a terminal from an external server and delivers the trigger request to the terminal, the network internal identifier of the terminal to a management server managing subscriber information.
  • an external identifier of a terminal is received from a manganese access server that receives a trigger request of the terminal from an external server and transmits the trigger request to the terminal, and transmits an internal identifier of the terminal to the network between the network and the terminal. Transmitting information of a relay server relaying a trigger message; And storing information indicating that there is a trigger request message waiting for retransmission in the network connection server if the triggering of the terminal fails.
  • the step of delivering a trigger transfer request message from the network connection server to the terminal Receiving a trigger delivery confirmation message from the terminal; And storing information indicating that there is a trigger request message waiting for retransmission in the network connection server when the trigger transmission request message transmission fails to the terminal. to provide.
  • the MTC-IWF or the MTC server receiving the failure result continuously repeats the trigger delivery request to avoid unnecessary network load. Generation can be prevented.
  • 1 illustrates an example of a network system for an MTC.
  • FIG. 2 illustrates an MTC device triggering method according to an embodiment.
  • FIG. 3 illustrates a trigger failure procedure due to failure of HLR / HSS information extraction according to an embodiment.
  • FIG. 4 illustrates a trigger failure procedure due to an SGSN / MME error according to an embodiment.
  • FIG 5 illustrates a trigger failure procedure due to an error on a wireless path, according to an embodiment.
  • FIG. 6 illustrates a triggerable notification procedure according to an embodiment.
  • FIG. 7 illustrates a device triggering procedure when a terminal becomes accessible according to an embodiment.
  • FIG. 8 is a block diagram illustrating a configuration of an MTC-IWF according to an embodiment.
  • FIG. 9 is a block diagram illustrating a configuration of an HLR / HSS according to an embodiment.
  • FIG. 10 is a block diagram illustrating a configuration of an SGSN / MME according to an embodiment.
  • MTC machine type communication
  • MTC may be variously called as M2M communication (Machine to Machine Communication), Internet of Things (IoT), Smart Device Communication, Machine Oriented Communication, and the like.
  • M2M communication Machine to Machine Communication
  • IoT Internet of Things
  • Smart Device Communication Smart Device Communication
  • Machine Oriented Communication and the like.
  • MTC is a form of data communication that represents a machine or machine-to-machine communication where one or more entities do not or require minimal human interaction.
  • An MTC device user terminal such as an electric meter, gas meter, or vending machine equipped with a mobile communication module may communicate with an MTC server that controls the MTC device and collects data through a wireless network of a mobile communication operator. .
  • MTC application services provided through MTC have a feature of rarely transmitting data at long time intervals.
  • the MTC user may periodically allow the MTC device to start data communication through the wireless network of the mobile communication provider to transmit data to the MTC server.
  • the MTC device initiates data communication through the mobile operator's wireless network at the request of the MTC server for control and management of the MTC device, collection of data on demand, and the like. You can also communicate with the MTC server.
  • the MTC device transmits a trigger request of the MTC server through the wireless network of the mobile communication operator, and the MTC device receiving the trigger request initiates data communication through the wireless network of the mobile communication operator to communicate with the MTC server. This is called triggering.
  • FIG. 1 illustrates an example of a network system for an MTC.
  • the example shown in FIG. 1 is a structure under consideration in the 3rd Generation Partnership Project (3GPP), but the present invention is not limited to the system shown in FIG.
  • 3GPP 3rd Generation Partnership Project
  • an MTC user 110 who wants to use a user equipment (UE) 120 may access an M2M application 130.
  • the terminal 120 is an MTC device.
  • the terminal 120 may be expressed in various terms such as a user terminal, an MTC terminal, an MTC device, an MTC user terminal, and an MTC device terminal.
  • the M2M application 130 may communicate with the M2M application 122 of the terminal 120 at the level of the application program.
  • the M2M application 130 may be operated by a service provider (SP).
  • SP service provider
  • the M2M application 130 may communicate with the terminal 120 through a network.
  • the M2M application 130 may be directly connected to the network to communicate with the terminal 120 (Direct Model).
  • the M2M application 130 may be connected to the network through the MTC server 140 to communicate with the terminal 120 (Indirect Model).
  • the MTC server 140 may be operated by a service provider or operated by a mobile network operator (MNO).
  • MNO mobile network operator
  • the wireless network operated by the mobile network operator includes a Radio Access Network (RAN) 150 and a Core Network (CN).
  • the core network includes a Home Location Register / Home Subscriber Server (HLR / HSS) 162, a Serving GPRS Support Node / Mobility Management Entity (164), and an SMS-SC / IP-SM-.
  • HLR / HSS Home Location Register / Home Subscriber Server
  • 164 Serving GPRS Support Node / Mobility Management Entity
  • SMS-SC IP-SM-.
  • Short Message Service-Service Center / IP-Short Message-GateWay 166
  • Machine Type Communication-Interworking Function MTC-IWF
  • Charging Data Function / Charging Gateway Function (CDF / CGF) (170)
  • GGSN / PGW / ePDG Gateway GPRS Support Node / Packet Data Network GateWay / enhanced Packet Data Gateway
  • the HLR / HSS 162 is an entity that stores user subscription related information (user identifier, user profile, etc.).
  • the SGSN is a switch that performs a packet switching function for a mobile terminal.
  • the MME is an entity on a control plane for supporting mobility management function in an Evolved Packet System (EPS).
  • EPS Evolved Packet System
  • the SMS-SC / IP-GW-GW 166 is an entity that relays, stores and forwards a short message between an entity capable of transmitting and receiving a short message (for example, a user terminal). .
  • the MTC-IWF 168 provides a reference point (MTCsp) for communicating with the MTC server 140, and, at the request of the MTC server 140, specifies a wireless network (Public Land Mobile Network, PLMN) of the mobile communication service provider. It is an entity that relays or converts signaling, MTC server authentication, authorization of control message, identifier mapping, etc. to operate a function.
  • MTCsp reference point
  • PLMN Public Land Mobile Network
  • the CDF is an entity that receives a charging event from an external entity (eg, MTC-IWF 168) and generates a charging data record (CDR) using information of the charging event. CDRs generated in the CDF are transferred to CGF. CGF acts as a gateway between the core network and the charging platform.
  • an external entity eg, MTC-IWF 168
  • CDRs generated in the CDF are transferred to CGF.
  • CGF acts as a gateway between the core network and the charging platform.
  • the GGSN / PGW / ePDG 172 receives the packet from the external network and forwards the received packet to the SGSN / MME 164, or receives the packet from the SGSN / MME 164 and forwards the received packet to the external network. It is an object.
  • the MTC user 110 allows the terminal 120 to periodically communicate with the MTC server 140 via the network. Can be set.
  • the MTC user 110 may use the terminal 120 based on a request of the MTC server 140 at any time. It may trigger to communicate with the MTC server 140 via this wireless network.
  • the network transmits the trigger request of the MTC server 140 to the terminal 120, and the terminal 120 receiving the trigger request initiates data communication through the network to communicate with the MTC server 140 is called MTC device triggering. Can be called
  • a specific function of a mobile operator wireless network may be received by receiving a trigger request of the MTC server 140.
  • Relaying or translating signaling information for activating the MTC server 140, MTC server authentication, trigger request authorization, charging, MTC-IWF 168 may be required to perform device triggering control functions such as trigger delivery mechanism selection and terminal identifier mapping.
  • MTC-IWF 168 may be implemented as a separate entity or as part of other wireless network equipment.
  • the MTC server 140 may transmit a trigger request to the MTC-IWF 170 by resolving an IP address of the MTC-IWF 170 that performs a device triggering control function for a specific terminal.
  • the MTC-IWF 168 may select a trigger delivery mechanism by a trigger request of the MTC server 140.
  • Trigger delivery mechanisms include using the Short Message Service (SMS), using the paging channel, using the broadcast channel, using the Cell Broadcast Service (CBS), and using the Non Access Stratum (NAS) protocol. There may be.
  • SMS Short Message Service
  • CBS Cell Broadcast Service
  • NAS Non Access Stratum
  • the MTC-IWF 68 may transmit a device trigger message to the terminal 120 through the SGSN / MME 164 serving the terminal 120 to be triggered.
  • FIG. 2 illustrates an MTC device triggering method according to an embodiment.
  • the MTC server 140 transmits a trigger request including the external identifier and the valid time of the terminal 120 to the MTC-IWF 168 (S201).
  • the external identifier is an identifier for identifying the terminal 120 from outside the 3GPP system, and includes a mobile station international ISDN number (MSISDN), a fully qualified domain name (FQDN), a network access identifier (NAI), and a session initiation protocol uniform resource identifier (SIP URI). ), An Internet Protocol (IP) address, and the like.
  • the valid time may be time information for storing the trigger request in the network when the trigger request is not delivered to the terminal 120.
  • the MTC-IWF 168 authorizes a trigger request, and is required for International Mobile Subscriber Identity (IMSI) information and other triggers mapped to an external identifier of the terminal 120 through the HLR / HSS 162.
  • Information for example, SGSN / MME 164 information serving a terminal 120 to be triggered
  • the IMSI may be used as an identifier of the terminal 120 in the mobile carrier's network.
  • the present invention is not limited thereto, and an identifier other than IMSI that can be used as an identifier of the terminal 120 in the network of the mobile communication operator may be applied.
  • the MTC-IWF 168 requests the trigger message delivery to the serving SGSN / MME 164 of the terminal 120 inquired by the HLR / HSS 162 (S203).
  • the SGSN / MME 164 receiving the trigger delivery request transmits a trigger message to the terminal 120 (S204).
  • the terminal 120 transmits a confirmation message for trigger message transmission to the MTC server 140 through the SGSN / MME 164 and the MTC-IWF 168 (S205).
  • the terminal 120 may activate a PDP / PDN (Packet Data Protocol / Public Data Network) connection through the GGSN / PGW 172 (S206).
  • PDP Packet Data Protocol / Public Data Network
  • the terminal 120 communicates with the MTC server 140 (S207).
  • the SGSN / MME 164 may include trigger delivery information in the non-access stratum (NAS) signaling message and transmit the trigger delivery information to the terminal 120. That is, when the terminal 120 transmits a Routing Area Update / Tracking Area Update (RAU / TAU) request message, the SGSN / MME 164 includes trigger delivery information in the RAU / TAU acceptance message to the terminal 120. I can deliver it. When the terminal 120 transmits an attach request message, the SGSN / MME 164 may include the trigger delivery information in the registration acceptance message and transmit the trigger delivery information to the terminal 120. When there is an ongoing signaling between the terminal 120 and the SGSN / MME 164, the SGSN / MME 164 transmits trigger transmission information through a specific NAS message (eg, a Downlink Generic NAS Transport message). 120).
  • a specific NAS message eg, a Downlink Generic NAS Transport message
  • the SGSN / MME 164 may deliver trigger delivery information to the terminal 120 through a paging request.
  • the SGSN / MME 164 may identify a specific paging request. Trigger delivery information may be transmitted to the terminal 120 through a NAS message (eg, a Downlink Generic NAS Transport message).
  • the SGSN / MME 164 may use a NAS message in an improved format or in a generic format for small amount of data transmission between the SGSN / MME and the terminal.
  • FIG. 3 illustrates a trigger failure procedure due to failure of HLR / HSS information extraction according to an embodiment.
  • the MTC server 140 transmits a trigger request message to the MTC-IWF 168 through an MTCsp reference point (S301).
  • the MTC server 140 may know in advance by configuring an IP address for one or more MTC-IWF 168 to forward a trigger request message for a specific terminal 120, or may be configured of one or more MTC-IWF 168 in advance.
  • An IP address for the MTC-IWF 168 may be resolved through a Domain Name System (DNS) (not shown) based on the domain name.
  • DNS Domain Name System
  • the mobile communication service provider can distinguish the MTC-IWF 168 to be processed according to the attributes of the terminal 120 (for example, application, user terminal, user terminal group, mobility support, fixed installation, trigger frequency, etc.).
  • the domain name may be allocated and included in the external identifier (for example, ⁇ terminal identifier inside the mobile operator> @ ⁇ mobile carrier domain name including the MTC-IWF identifier>).
  • the mobile communication service provider may use MSISDN as external identifier information of the terminal 120 or include a domain name that does not include the MTC-IWF identifier.
  • MSISDN external identifier information of the terminal 120
  • the IP address for the MTC-IWF 168 may be resolved in a round robin manner.
  • the IP address for the MTC-IWF 168 may be resolved by specifying the domain name of the mobile communication provider used basically and the domain name of the mobile communication provider used as a backup for the terminal 120.
  • the trigger request message may include all or part of the information shown in Table 1 below.
  • Terminal identifier Information for identifying the MTC device user terminal may use MSISDN, Fully Qualified Domain Name (FQDN), Network Access Identifier (NAI), SIP URI, IP address, etc.
  • MTC Server Identifier Information for identifying an MTC server capable of requesting device triggering through a mobile carrier's wireless network, such as an MSISDN, a fully qualified domain name (FQDN), a network access identifier (NAI), a SIP URI, IP address can be used and can be used for device triggering and billing.
  • Trigger application ID Information for identifying an application to be operated in the MTC device user terminal by a trigger request of the MTC server
  • Priority It may be necessary to indicate whether the mobile service provider's wireless network (eg SMS-SC, etc.) is overloaded in the overload state (eg triggering device in case of many trigger requests to be processed compared to the network capacity).
  • Priority and Urgency Indications Displaying Status Report Requests Information indicating whether to request a report on the trigger request message processing status by the MTC server.
  • Trigger reference number Information used to correlate trigger requests and trigger responses
  • Old trigger reference number Used to delete the previous trigger request message from the network when the MTC server attempts to resend the trigger request message to the same terminal that has not been answered with the trigger reference number of the previously requested but not yet responded trigger request message.
  • the MTC-IWF 168 detects the trigger signaling load coming from the MTC server 140 and receives from the SGSN / MME 164 the number or rate of trigger request messages from a specific MTC server, the total number or rate of trigger request messages.
  • Overload control messages e.g., a message notifying SGSN / MME to start overloading to limit sending a message to SGSN / MME
  • a specific trigger request message to control overloading according to settings by the network administrator, etc.
  • processing of the entire trigger request message can be stopped.
  • the MTC-IWF 168 may resume processing of the interrupted trigger request message.
  • the MTC-IWF 168 fails to transmit the trigger message to the terminal 120 until the valid time transmitted by being included in the trigger request message of the MTC server 140 due to the overload ends, the MTC-IWF 168 ) May report the trigger failure to the MTC server 140, including the detailed reason code for the trigger failure (eg, failure due to overload, failure due to valid timeout).
  • the MTC-IWF 168 may not report the trigger result.
  • the MTC-IWF 168 may extend the valid time by the time that is interrupted when the trigger request message processing is stopped due to the overload. If MTC-IWF 168 extends the validity time due to overload, MTC-IWF 168 may report that the trigger is being stopped due to overload and may indicate that the valid time is being extended. have. The MTC-IWF 168 may report that the overload is released to the MTC server 140 when the overload is released. In this case, the remaining valid time of the trigger request message interrupted by the overload may be displayed.
  • the MTC-IWF 168 receiving the trigger request message from the MTC server 140 performs authorization of the MTC server and authorization of whether the MTC server has a right to request triggering from a specific terminal. Can be.
  • MTC server 140 identifier information that may request MTC-IWF 168 terminal triggering may be pre-configured in the MTC-IWF 168.
  • the MTC server 140 identifier information, which may request the MTC-IWF 168 to trigger on a specific terminal, is preconfigured in the HLR / HSS 162 and the MTC-IWF 168 may be configured in the HLR / HSS 162. You can inquire.
  • an identifier of the terminal 120 allowing the MTC-IWF 168 to trigger the terminal and the triggering of the terminal 120 is allowed.
  • An identifier information table including an identifier of the MTC server 140 may be preconfigured in the MTC-IWF 168.
  • the above-described identifier information table may be configured in advance in the HLR / HSS 162 and the MTC-IWF 168 may query the HLR / HSS 162.
  • the MTC-IWF 168 fails to authenticate the MTC server or the authorization of the trigger, if the external identifier information of the terminal included in the trigger request message is not an MSISDN, the MTC-IWF 168 cannot process the trigger request.
  • the MTC-IWF 168 may not be able to process the MTC-IWF 168 because it is not a trigger request for a terminal subscribed to the wireless network of the mobile communication operator operating the MTC-IWF 168.
  • the trigger failure may be reported to the server 140 including a detailed reason code (eg, authentication failure, authorization failure, terminal specific failure, etc.) for the trigger failure.
  • the MTC-IWF 168 may not report a trigger failure when the trigger request message of the MTC server 140 does not include a report request indication.
  • the MTC-IWF 168 inquires information necessary for terminal triggering through the HLR / HSS 162 (S302).
  • the MTC-IWF 168 may request the inquiry including the external identifier information of the terminal 120 included in the trigger request message of the MTC server 140 to inquire information necessary for the trigger.
  • the MTC-IWF 168 may request an inquiry including a timestamp when the trigger request message reaches the MTC-IWF 168.
  • the HLR / HSS 162 may include external identifier information of the terminal 120 included in the information inquiry request message from the MTC-IWF 168, time information of reaching the MTC-IWF 168, and an identifier of the MTC server 140. Information and the like may be used to check whether the information inquiry request message is received in duplicate, and if the message reception is checked as duplicate, it may be discarded.
  • the HLR / HSS 162 may store IMSI information mapped to the external identifier information of the terminal 120 and other information necessary for triggering, and MTC may transmit all the information necessary for triggering according to an inquiry request of the MTC-IWF 168. May be provided to the IWF 168.
  • the MTC-IWF 168 may make a trigger information request to the HLR / HSS 162
  • the MTC-IWF 168 may make a request including an indication of necessary information content in addition to the external identifier information of the terminal 120, and the HLR / HSS 162 may be requested. May extract and respond to necessary information included in the request of the MTC-IWF 168.
  • the HLR / HSS 162 provides attribute information indicating that the terminal 120 is an MTC device for MTC terminal triggering, connection priority information of the terminal 120, and attribute information about whether the terminal 120 has a fixed location.
  • the fixed location information may be additionally managed.
  • the HLR / HSS 162 indicates that there is a trigger request message waiting for trigger delivery within a network entity that provides a trigger message store and forward function if the trigger message delivery fails (eg, message waiting indication) can be stored.
  • Network entities that provide storage and forwarding functions may be implemented within MTC-IWF 168, or functions implemented within MTC-IWF 168, or entities separate from MTC-IWF 168 (e.g., SMS-SC, MTC).
  • the information indicating that there is a wait trigger request message stored by the HLR / HSS 162 may include identifier information of the terminal 120 that fails to deliver the trigger request message, a network entity or a MTC-IWF 168 that provides a storage and forwarding function. It may include at least one of the address information, the information indicating the detailed cause (for example, the UE not reachable (Not Reachable)) failed to deliver the trigger request message, the valid time.
  • the HLR / HSS 162 indicates that there is a trigger request message waiting for trigger delivery in a network entity that fails to deliver the trigger message and provides a storage and forwarding function. ) May not be saved.
  • the terminal 120 does not have a paging response by the SGSN / MME 164, when the terminal 120 is network deregistered (GPRS detach, IMSI detach), or SGSN / serviced by the HLR / HSS 162
  • the HLR / HSS 162 sends a detailed reason code that fails to deliver the trigger request message to the network connection of the MTC terminal. You can set it to Disabled (eg MTC Device Not Reachable) and save it.
  • the HLR / HSS 162 If the information cannot be extracted because the HLR / HSS 162 does not store / manage the external identifier information of the terminal 120 included in the inquiry request message of the MTC-IWF 168, the HLR / HSS 162 is the MSISDN. If the HLR / HSS 162 fails to extract the information, for example, if it is unable to process any external identifier information other than HLR / HSS 162, the HLR / HSS 162 will provide a separate failure notification with a failure code for the detailed cause of the failure. The message may be delivered to the MTC-IWF 168 (S303).
  • the terminal 120 when the terminal 120 does not respond to paging by the SGSN / MME 164, when the terminal 120 is deregistered from the network, the SGSN / MME 164 information serviced by the HLR / HSS 162 is provided. If the terminal 120 is unable to access the network due to the reason that the terminal 120 is not able to access the network, and the HLR / HSS 162 fails to extract information, the HLR / HSS 162 includes a failure code for a detailed failure cause. A separate failure notification message may be delivered to the MTC-IWF 168.
  • the MTC-IWF 168 may generate charging information and transmit the charging information to the CDF / CGF 170 even when the trigger fails.
  • the generated charging information may include external identifier information of the MTC terminal 120, IMSI information mapped to external identifier information of the MTC terminal 120, identifier information of the MTC server 140, a trigger result, and the like.
  • the failure notification message may be delivered through the inquiry response message of the MTC-IWF 168 in step S302 described above, and step S303 may be omitted.
  • the MTC-IWF 168 receiving the failure notification message transmits a failure report including the failure code to the MTC server 140 (S304).
  • the MTC-IWF 168 may deliver a failure report when a failure notification message is received, or may deliver a failure report at the end of a trigger request validity time. If the failure report is not delivered until the trigger request validity time expires, the success report can be delivered without passing the previous failure report if the trigger message is successfully delivered through the trigger retransmission before the trigger request validity time expires. If the trigger request message of the MTC server 140 does not include a report request indication, the MTC-IWF 168 may not report the trigger result to the MTC server 140, and step S304 may be omitted.
  • the terminal 120 when the terminal 120 does not respond to paging by the SGSN / MME 164, when the terminal 120 is deregistered from the network, the SGSN / MME 164 that the HLR / HSS 162 is serving. If the HLR / HSS 162 fails to extract the information because the terminal 120 is in a network inaccessible state due to no information), the MTC-IWF 168 periodically Trigger message delivery may be retransmitted and information retrieval may be repeated to HLR / HSS 162 for this purpose.
  • the network entity providing the storage and forwarding function may notify that the terminal 120 is reachable from the SGSM / MME 164 and / or the HLR / HSS 162 before the trigger request validity time expires. It may receive a message, and if so, it may retransmit trigger message delivery to a network entity that provides storage and delivery functionality.
  • the connectable notification message may include at least one of a terminal identifier (eg, IMSI), information indicating that the terminal is accessible (eg, UE-Reachable, UE-present), and routing information including a serving core node identifier. May contain information.
  • the network object providing the storage and forwarding function has a trigger wait message through the MTC-IWF 168. It may receive a registration message and a notification message for accessibility of the terminal.
  • the information indicating that there is a wait trigger request message stored by the HLR / HSS 162 may include address information of the MTC-IWF 168, not address information of a network object providing a storage and forwarding function. If the MTC-IWF 168 receives the terminal accessible notification message, the network entity providing the storage and delivery function may be triggered to retransmit the trigger message delivery through the MTC-IWF 168.
  • the network entity providing the storage and forwarding function may be registered to the terminal and may be connected to the terminal. May receive a notification message.
  • the information indicating that there is a wait trigger request message stored by the HLR / HSS 162 may include address information of the network object providing the storage and forwarding function, and the network object providing the storage and forwarding function.
  • the network entity providing the storage and forwarding function may be triggered to retransmit the trigger message delivery.
  • the trigger message forwarding retransmission by the network entity providing the storage and forwarding function may be provided through the MTC-IWF 168, or the self forwarding function of the network entity providing the storage and forwarding function (for example, SMS). -SC 166) may be used.
  • the MTC-IWF 168 may resend trigger message delivery by setting a rule (eg, entered by an operator) during the trigger request validity time.
  • a rule eg, entered by an operator
  • the MTC-IWF 168 may forward the trigger request message to the SMS-SC 166.
  • the MTC-IWF 168 may serve as a Short Message Entity (SME) capable of transmitting and receiving a short message with the SMS-SC 168. If the trigger delivery fails and the MTC-IWF 168 forwards the trigger request message to the SMS-SC 166, the MTC-IWF 168 may forward the trigger request message, including some or all of the information in Table 1. Can be.
  • SME Short Message Entity
  • the MTC-IWF 168 may map the valid time information received from the MTC server 140 to the TP-Validity-Period information transmitted to the SMS-SC 166 to transmit the information to the SMS-SC 166.
  • the SMS-SC 166 may use the valid time information for SMS transmission.
  • the MTC-IWF 168 may set a value other than the valid time information received from the MTC server 140 (for example, a value determined as the valid time value according to an operator's policy).
  • the TP-Validity-Period information transmitted to 166 may be mapped and transmitted to the SMS-SC 166, and the SMS-SC 166 may use valid time information for SMS transmission.
  • the SMS-SC 166 When the SMS-SC 166 causes retransmission, the information indicating that there is a waiting trigger request message stored by the HLR / HSS 162 described above is not the address information of the MTC-IWF 168 but the SMS-SC. 166 may include address information. To this end, the MTC-IWF 168 may request an information update from the HLR / HSS 162 and receive a confirmation thereof.
  • a network entity providing the above-described storage and forwarding function is triggered to the terminal 120 by the trigger request message.
  • To retransmit the MTC-IWF 168 may forward the trigger request message to a network entity that provides storage and forwarding functionality.
  • the MTC-IWF 168 is a network entity that provides storage and forwarding functions including some or all of the information in Table 1 (eg, validity time, trigger reference number, etc.) included in the trigger request message of the MTC server. I can deliver it.
  • a network entity providing a storage and forwarding function may retransmit trigger message delivery.
  • FIG. 4 illustrates a trigger failure procedure due to an SGSN / MME error according to an embodiment.
  • Steps S401 and S402 of FIG. 4 are the same as steps S301 and S302 of FIG. 3, and a detailed description thereof will be omitted.
  • step S402 is a case where information inquiry about the HLR / HSS 162 of the MTC-IWF 168 is successful.
  • the MTC-IWF 168 may receive information of the SGSN / MME 164 serving the terminal 120 from the HLR / HSS 162.
  • the MTC-IWF 168 requests the trigger message delivery to the SGSN / MME 164 node provided from the HLR / HSS 162 using the IMSI information of the terminal 120 as a destination address ( S403).
  • the trigger message transfer request message delivered by the MTC-IWF 168 to the SGSN / MME 164 may use an SMS transmission protocol or an internet protocol such as HTTP, SIP, or Diameter.
  • the trigger message delivery request message to the SGSN / MME 164 may include some or all of the information in Table 1.
  • the MTC-IWF 168 first sends a message containing priority information to the SGSN / MME 164 so that the SGSN / MME 164 preferentially processes a trigger forwarding request with a high trigger priority.
  • the terminal 120 may set up a PDP / PDN connection having a high access priority.
  • the MTC-IWF 168 sends a message to the SGSN / MME 164 that includes valid time information, such that the valid time expires if the SGSN / MME 164 fails to deliver the trigger request message. It may attempt to retransmit to the terminal 120 without delivering a failure report until.
  • the valid time information delivered from the MTC-IWF 168 to the SGSN / MME 164 may be valid time information delivered by the MTC server 140 to the MTC-IWF 168, or the valid time delivered by the MTC server 140. It may be a value determined as a value of valid time other than information (for example, according to an operator's policy or the like).
  • the MTC-IWF 168 may send a message to the SGSN / MME 164 that includes a timestamp when the trigger request message reached the MTC-IWF 168.
  • the SGSN / MME 164 requests a trigger using external identifier information of the terminal 120 included in the trigger message delivery request message, time information of reaching the MTC-IWF 168, identifier information of the MTC server 140, and the like. It is possible to check whether the message is received in duplicate, and if the trigger request message is checked to be received in duplicate, it can be discarded.
  • the MTC-IWF 168 transmits a trigger message to the previous serving SGSN / MME 164.
  • the previous serving SGSN / MME 164 may not be able to process the trigger message delivery request.
  • the previous serving SGSN / MME 164 reports to the MTC-IWF 168 a trigger delivery failure including a failure code for the detailed failure cause (S404).
  • SGSN / MME 164 sends a failure report to MTC-IWF 168 when it determines that trigger delivery has failed, or MTC-IWF 168 at the end of the validity time received from MTC-IWF 168. You can send a failure report. If the network entity that receives the failure report and provides the storage and forwarding function before the expiration time included in the trigger request message of the MTC server 140 is a separate entity from the MTC-IWF 168, the MTC- IWF 168 may forward the trigger request message to a network entity that provides storage and forwarding functionality.
  • the MTC-IWF 168 fails to deliver a trigger message to the HLR / HSS 162 and waits for a trigger delivery to a network entity that provides storage and delivery functionality.
  • a request is made to store information indicating that there is a trigger request message (S405).
  • the information indicating that there is a wait trigger request message indicates the identifier information of the terminal 120 that failed to deliver the trigger request message, the address information of the network entity or the MTC-IWF 168 providing the storage and forwarding function, and the detailed cause of failure.
  • the information may include at least one of validity time.
  • the identifier information of the terminal 120 may be external identifier information or IMSI information of the terminal 120.
  • the HLR / HSS 162 transmits a confirmation message for storing the trigger delivery state to the MTC-IWF 168 (S406).
  • the HLR / HSS 162 may not send an acknowledgment message for storing the trigger delivery status to the MTC-IWF 168, and step S406 may be omitted.
  • the MTC-IWF 168 receiving the failure notification message transmits a failure report including the failure code to the MTC server 140 (S407).
  • the MTC-IWF 168 may deliver a failure report when a failure notification message is received, or may deliver a failure report at the end of a trigger request validity time. If the failure report is not delivered until the trigger request validity time expires, the success report can be delivered without passing the previous failure report if the trigger message is successfully delivered through the trigger retransmission before the trigger request validity time expires. If the trigger request message of the MTC server 140 does not include a report request indication, the MTC-IWF 168 may not report the trigger result to the MTC server 140, and step S407 may be omitted.
  • the terminal 120 when the terminal 120 does not respond to paging by the SGSN / MME 164, when the terminal 120 is deregistered from the network, the SGSN / MME 164 that the HLR / HSS 162 is serving. If the HLR / HSS 162 fails to extract the information because the terminal 120 is in a network inaccessible state due to no information), the MTC-IWF 168 periodically Trigger message delivery may be retransmitted and information retrieval may be repeated to HLR / HSS 162 for this purpose.
  • the network entity providing the storage and forwarding function receives a notification message indicating that the terminal 120 is reachable from the SGSM / MME 164 or the HLR / HSS 162 before the trigger request validity time expires.
  • the network entity providing the storage and forwarding function may retransmit the triggered message forwarding if received.
  • the MTC-IWF 168 may resend trigger message delivery by setting a rule (eg, entered by an operator) during the trigger request validity time.
  • a rule eg, entered by an operator
  • the MTC-IWF 168 may send the SMS-SC 166 to the SMS-SC 166 to resend the trigger request message to the terminal 120.
  • the trigger request message may be forwarded to the SC 166.
  • the MTC-IWF 168 may serve as a Short Message Entity (SME) capable of transmitting and receiving a short message with the SMS-SC 168. If the trigger delivery fails and the MTC-IWF 168 forwards the trigger request message to the SMS-SC 166, the MTC-IWF 168 may forward the trigger request message, including some or all of the information in Table 1. Can be.
  • SME Short Message Entity
  • the MTC-IWF 168 may map the valid time information received from the MTC server 140 to the TP-Validity-Period information transmitted to the SMS-SC 166 to transmit the information to the SMS-SC 166.
  • the SMS-SC 166 may use the valid time information for SMS transmission.
  • the MTC-IWF 168 may set a value other than the valid time information received from the MTC server 140 (for example, a value determined as the valid time value according to an operator's policy).
  • the TP-Validity-Period information transmitted to 166 may be mapped and transmitted to the SMS-SC 166, and the SMS-SC 166 may use valid time information for SMS transmission.
  • the SMS-SC 166 When the SMS-SC 166 causes retransmission, the information indicating that there is a waiting trigger request message stored by the HLR / HSS 162 described above is not the address information of the MTC-IWF 168 but the SMS-SC. 166 may include address information. To this end, the MTC-IWF 168 may request an information update from the HLR / HSS 162 and receive a confirmation thereof.
  • a network entity providing a storage and forwarding function to the terminal 120 triggers a request message.
  • To retransmit the MTC-IWF 168 may forward the trigger request message to a network entity that provides storage and forwarding functionality.
  • the MTC-IWF 168 may transfer some (eg, validity time) or all of the information in Table 1 included in the trigger request message of the MTC server to a network entity providing a storage and forwarding function.
  • the MTC-IWF 168 may further convey information about the cause of the failure.
  • the network entity providing the storage and forwarding function receives the terminal accessible notification message from the MTC-IWF 168 or the HLR / HSS 162
  • the network entity providing the storage and forwarding function can resend the trigger message forwarding. have.
  • FIG 5 illustrates a trigger failure procedure due to an error on a wireless path, according to an embodiment.
  • Steps S501 to S503 of FIG. 5 are the same as steps S401 to S403 of FIG. 4, and a detailed description thereof will be omitted.
  • the SGSN / MME 164 transmits a trigger message to the terminal 120 (S504). However, when the terminal 120 is out of the wireless coverage area or the like, the SGSN / MME 164 transmits a trigger message to the terminal 120 or the terminal 120 transmits an acknowledgment message about the trigger message delivery. An error on the wireless path can cause the trigger message to fail.
  • the SGSN / MME 164 has a trigger request message waiting for trigger delivery to a network entity that provides a storage and forwarding function when the trigger message delivery fails, so that the UE can notify the trigger retransmission when the terminal is reachable.
  • the display information can be stored to make it available.
  • the indication information for notifying the trigger retransmission when the terminal is reachable because the network entity that provides the storage and forwarding function has a trigger request message waiting for the trigger forwarding is included in the validity time included in the trigger request.
  • MTC-IWF 168 that is set by SGSN / MME 164 that failed trigger message delivery before it was terminated, or received a trigger delivery failure report from SGSN / MME 164, to HLR / HSS 162. Through the HLR / HSS 162 according to the step S506 of requesting to store information indicating that there is a trigger request message waiting for trigger delivery to a network entity that fails to deliver the trigger message and provides a storage and forwarding function. Can be set
  • the SGSN / MME 164 fails to deliver a trigger message due to an error on the radio path, the SGSN / MME 164 reports to the MTC-IWF 168 a trigger delivery failure that includes a failure code for the detailed cause of the failure. (S505). If the network entity that receives the failure report and provides the storage and forwarding function before the expiration time included in the trigger request message of the MTC server 140 is a separate entity from the MTC-IWF 168, the MTC- IWF 168 may forward the trigger request message to a network entity that provides storage and forwarding functionality.
  • the MTC-IWF 168 fails to deliver the trigger message to the HLR / HSS 162 and waits for trigger delivery to a network entity that provides storage and delivery functionality.
  • Request to store information indicating that there is a trigger request message to the HLR / HSS 162 (S506).
  • the information indicating that the MTC-IWF 168 transmitted to the HLR / HSS 162 has a trigger request message waiting for the trigger forwarding may include identifier information, storage, and forwarding function of the terminal 120 that failed to forward the trigger request.
  • the identifier information of the terminal 120 may be external identifier information or IMSI information of the terminal 120.
  • the HLR / HSS 162 transmits a confirmation message for storing the trigger delivery state to the MTC-IWF 168 (S507).
  • the HLR / HSS 162 may not send an acknowledgment message for storing the trigger delivery status to the MTC-IWF 168, and step S507 may be omitted.
  • MTC-IWF 168 receiving the failure notification message transmits a failure report including the failure code to the MTC server 140 (S508).
  • the MTC-IWF 168 may deliver a failure report when a failure notification message is received, or may deliver a failure report at the end of a trigger request validity time. If the failure report is not delivered until the trigger request validity time expires, the success report can be delivered without passing the previous failure report if the trigger message is successfully delivered through the trigger retransmission before the trigger request validity time expires. If the trigger request message of the MTC server 140 does not include a report request indication, the MTC-IWF 168 may not report the trigger result to the MTC server 140, and step S508 may be omitted.
  • the terminal 120 when the terminal 120 does not respond to paging by the SGSN / MME 164, when the terminal 120 is deregistered from the network, the SGSN / MME 164 that the HLR / HSS 162 is serving. If the HLR / HSS 162 fails to extract the information because the terminal 120 is in a network inaccessible state due to no information), the MTC-IWF 168 periodically Trigger message delivery may be retransmitted and information retrieval may be repeated to HLR / HSS 162 for this purpose.
  • the network entity providing the storage and forwarding function receives a notification message indicating that the terminal 120 is reachable from the SGSM / MME 164 or the HLR / HSS 162 before the trigger request validity time expires.
  • the network entity providing the storage and forwarding function may retransmit the triggered message forwarding if received.
  • the MTC-IWF 168 may resend trigger message delivery by setting a rule (eg, entered by an operator) during the trigger request validity time.
  • a rule eg, entered by an operator
  • the MTC-IWF 168 sends the SMS-SC 166 to the SMS-SC 166 to cause the SMS-SC 166 to resend the trigger request message to the terminal 120. You can pass a trigger request message.
  • the MTC-IWF 168 may serve as a Short Message Entity (SME) capable of transmitting and receiving a short message with the SMS-SC 168. If the trigger delivery fails and the MTC-IWF 168 forwards the trigger request message to the SMS-SC 166, the MTC-IWF 168 may forward the trigger request message, including some or all of the information in Table 1. Can be.
  • SME Short Message Entity
  • the MTC-IWF 168 may map the valid time information received from the MTC server 140 to the TP-Validity-Period information transmitted to the SMS-SC 166 to transmit the information to the SMS-SC 166.
  • the SMS-SC 166 may use the valid time information for SMS transmission.
  • the MTC-IWF 168 may set a value other than the valid time information received from the MTC server 140 (for example, a value determined as the valid time value according to an operator's policy).
  • the TP-Validity-Period information transmitted to 166 may be mapped and transmitted to the SMS-SC 166, and the SMS-SC 166 may use valid time information for SMS transmission.
  • the SMS-SC 166 When the SMS-SC 166 causes retransmission, the information indicating that there is a waiting trigger request message stored by the HLR / HSS 162 described above is not the address information of the MTC-IWF 168 but the SMS-SC. 166 may include address information. To this end, the MTC-IWF 168 may request an information update from the HLR / HSS 162 and receive a confirmation thereof.
  • the network entity providing the storage and forwarding function resends the trigger request message to the terminal 120.
  • the MTC-IWF 168 may forward the trigger request message to a network entity that provides storage and forwarding functionality.
  • the MTC-IWF 168 may deliver some or all of the information in Table 1 included in the trigger request message of the MTC server 140 to the network entity providing the storage and forwarding function.
  • the MTC-IWF 168 may further convey information about the cause of the failure.
  • the network entity providing the storage and forwarding function receives the terminal accessible notification message from the MTC-IWF 168 or the HLR / HSS 162
  • the network entity providing the storage and forwarding function can resend the trigger message forwarding. have.
  • FIG. 6 illustrates a triggerable notification procedure according to an embodiment.
  • the MTC-IWF 168 fails to deliver the trigger message to the HLR / HSS 162 to provide a storage and delivery function.
  • Information is sent to the network entity indicating that there is a trigger request message waiting for trigger delivery, and the HLR / HSS 162 may store this information.
  • the information indicating that there is a wait trigger request message stored by the HLR / HSS 162 may include identifier information of the terminal 120 that fails to deliver the trigger message, and information about the network entity or the MTC-IWF 168 that provides storage and forwarding functions. It may include at least one of an address, information indicating a detailed cause of failure of the trigger message delivery, and a valid time.
  • the terminal 120 does not respond to paging by the SGSN / MME 164, the terminal 120 is deregistered from the network, or does not have the information of the serving SGSN / MME 164 in the HLR / HSS.
  • the failure detail reason code stored by the HLR / HSS 162 may be set to be unable to connect to the network of the terminal.
  • the indication information for notifying the trigger retransmission when the terminal is accessible due to the wait trigger request message may be stored in the SGSN / MME 164.
  • the SGSN / MME 164 transmits a trigger preparation notification message to the HLR / HSS 162 informing that the trigger message delivery to the terminal 120 is ready (S602).
  • the triggerable notification message may include at least one of a terminal identifier (eg, IMSI), information indicating that the terminal is accessible (eg, UE-Reachable, UE-present), and routing information including a serving core node identifier. It may include.
  • the SGSN / MME 164 may delete the indication information for allowing the UE to notify the retransmission of the trigger when there is a wait trigger request message in the network entity providing the storage and forwarding function.
  • the HLR / HSS 162 transmits a notification message to the MTC-IWF 168 informing that the terminal 120 has become accessible (S603). At this time, the HLR / HSS 162 may delete information indicating that there is a wait trigger request message in the network entity providing the storage and forwarding function.
  • the SGSN / MME 164 may not store information indicating that there is a wait trigger request message in the MTC-IWF 168.
  • the trigger request transmission may fail during the inquiry process of the HLR / HSS 162, and in this case, the SGSN / MME 164 may not know whether the trigger request transmission has failed.
  • the connection state between the SGSN / MME 164 and the terminal 120 in FIG. 6 that failed while attempting to transmit a trigger request to the terminal 120 in FIG. 4 and FIG. 5 is failed.
  • the SGSN / MME 164 may be different from each other, and in this case, the SGSN / MME 164 that detects an accessible state of the terminal 120 may not know whether a trigger request transmission has failed. Alternatively, by setting, the SGSN / MME 164 may not store information indicating that there is a wait trigger request message in the MTC-IWF 168.
  • the HLR / HSS 162 when the HLR / HSS 162 detects that the terminal 120 has entered the network connection state using only the network connection state information of the terminal 120 collected, the HLR / HSS 162 determines that the terminal 120 A notification message for notifying that the connection is available may be transmitted to the MTC-IWF 168. At this time, the HLR / HSS 162 may delete information indicating that there is a wait trigger request message in the MTC-IWF 168.
  • the MTC-IWF 168 that has received a notification message indicating that the UE is in an accessible state from the HLR / HSS 162 may execute triggering again.
  • 7 illustrates a device triggering procedure when a terminal becomes accessible according to an embodiment.
  • Steps S701 and S702 in FIG. 7 are the same as steps S502 and S503 in FIG. 5, and detailed descriptions are omitted.
  • the information retrieval step may be omitted.
  • the SGSN / MME 164 transmits a trigger message to the terminal 120 (S703), and the terminal 120 that has received the trigger message transmits an acknowledgment message for the trigger message transmission to the SGSN / MME 164 and the MTC-IWF ( 168 and transmits to MTC server 704 (S704).
  • the SGSN / MME 164 may delete information indicating that there is a wait trigger request message in the MTC-IWF 168. That is, the SGSN / MME 164 deletes information indicating that there is a wait trigger request message in the MTC-IWF 168, as described with reference to FIG. 120 may be executed when it detects that the network connection is possible, or when SGSN / MME 164 receives an acknowledgment message for trigger message delivery from terminal 120, as described in connection with FIG. It may be.
  • the MTC-IWF 168 having received a trigger delivery success report, triggers the HLR / HSS 162 to delete information indicating that there is a trigger request message waiting for a trigger delivery stored in the HLR / HSS 162.
  • the delivery status update request message is transmitted (S705).
  • the HLR / HSS 162 deletes information indicating that there is a wait trigger request message, and sends a trigger forwarding status update confirmation message to the MTC-IWF 168 that deleted information indicating that there is a wait trigger request message. (S706).
  • steps S705 and S706 may be omitted.
  • the HLR / HSS 162 may not transmit a confirmation message for the trigger delivery status update request to the MTC-IWF 168, and step S706 may be omitted.
  • the terminal 120 activates the PDP / PDN connection if necessary (S706).
  • the terminal 120 communicates with the MTC server 140.
  • the MTC server sends a trigger message forwarding request to the MTC IWF through the MTCsp reference point and receives a response to the trigger message forwarding request. Can be sent by IWF.
  • the MTC server may request the MTC IWF to delete the previous trigger request message, modify the previous trigger request message (for example, change the priority), query the trigger delivery status of the previous trigger request message, and the like through the trigger command request message.
  • the MTC IWF will not be able to forward the trigger message to the MTC IWF with confirmation details about the previous trigger request message received through the MTC server's trigger command request message (for example, MTC device not reachable). Can be answered.
  • MTC IWF can obtain the necessary information by requesting the HLR / HSS to look up information to check the trigger delivery status of the previous trigger request message through the trigger command request message of the MTC server.
  • the trigger command request message may include all or part of the information shown in Table 1 above.
  • the trigger command request message can be distinguished by different message type indication parameter values from the trigger request message.
  • the MTC server may include a trigger reference number (eg, old trigger reference number) of the trigger request message previously transmitted in the trigger request message.
  • a trigger reference number eg, old trigger reference number
  • the old trigger request message stored because the valid time has not expired can be deleted.
  • FIG. 8 is a block diagram illustrating a configuration of an MTC-IWF according to an embodiment.
  • the MTC-IWF transmits and receives a message with an MTC server communication unit 810 for transmitting and receiving a message with an MTC server, an HLR / HSS communication unit 820 for transmitting and receiving a message with an HLR / HSS, and an SGSN / MME.
  • SGSN / MME communication unit 830 a trigger information storage unit 840 for storing information included in the trigger request message received from the MTC server, a trigger message storage unit 850 for storing a trigger request message waiting for transmission , And a control unit 860.
  • the MTC server communication unit 810 may receive a trigger request message from the MTC server.
  • the trigger request message may include a message type indication, a valid time, a terminal identifier, an MTC server identifier, an application ID, a trigger priority, a status report request indication, and application specific information as shown in Table 1.
  • the MTC server communication unit 810 may transmit a trigger delivery confirmation message when the trigger request message delivery is successful, and may transmit a trigger failure report when the trigger request message delivery fails.
  • the HLR / HSS communication unit 820 may transmit a message requesting inquiry of the IMSI information mapped to the external identifier of the terminal and the serving SGSN / MME information of the terminal to the HLR / HSS, and the IMSI information of the terminal and the terminal from the HLR / HSS.
  • a response message including Serving SGSN / MME Information may be received. If the inquiry fails in the HLR / HSS, the HLR / HSS communication unit 820 may receive a failure notification message including the failure cause information from the HLR / HSS.
  • the HLR / HSS communication unit 820 stores a trigger request message waiting for transmission to the HLR / HSS.
  • a trigger delivery status message may be sent to indicate the status.
  • the HLR / HSS communication unit 820 may receive a notification signal indicating that the terminal is network accessible from the HLR / HSS.
  • the HLR / HSS communication unit 820 requests to delete the information indicating that the trigger request message is waiting for transmission to the HLR / HSS.
  • the trigger delivery status update message may be transmitted.
  • the SGSN / MME communication unit 830 may transmit a trigger delivery request message to the SGSN / MME. If the triggering is successful, the SGSN / MME communication unit 830 may receive a trigger delivery confirmation message from the SGSN / MME, and if the triggering fails, the SGSN / MME communication unit 830 receives a trigger delivery failure message from the SGSN / MME. can do.
  • the trigger information storage unit 840 may store trigger related information included in a trigger request message received from the MTC server.
  • the information included in the trigger request message is a valid time which is information about a time for storing the trigger request when the trigger request fails, an identifier of the terminal, an MTC server identifier, an application ID for identifying an application to be operated in the terminal, and priority of triggering. It may include a priority for indicating whether or not to process, a status report request indication indicating whether to report the processing status to the trigger request message, and application specific information that may be used by an application of the terminal.
  • the trigger message storage unit 850 When the trigger message storage unit 850 receives a failure notification message from the HLR / HSS through the HLR / HSS communication unit 820 because the trigger fails due to the information extraction failure in the HLR / HSS, due to an error in the SGSN / MME Failed trigger from SGSN / MME via SGSN / MME communication unit 830, or failure from SGSN / MME via SGSN / MME communication unit 830 due to a failure in the radio path due to failure of the trigger. If a notification message is received, the failed trigger message is stored.
  • the trigger message stored in the trigger message storage unit 850 may be stored within a valid time stored in the trigger information storage unit 840. When the trigger succeeds by retransmitting the trigger message within the valid time, or when the valid time has elapsed, the trigger message stored in the trigger message storage unit 850 may be deleted.
  • the control unit 860 When the control unit 860 receives the trigger request message through the MTC server communication unit 810, the control unit 860 stores the trigger information in the trigger information storage unit 840 and related information about the trigger (IMSI of the terminal, information of the serving SGSN / MME). Through the HLR / HSS communication unit 820 can query information to the HLR / HSS. The controller 860 may transmit a trigger request message to the SGSN / MME through the SGSN / MME communication unit 830. When the message for confirming the trigger delivery is received from the SGSN / MME through the SGSN / MME communication unit 830, the controller 860 may transmit the trigger delivery confirmation message to the MTC server through the MTC server communication unit 810.
  • the control unit 860 triggers a trigger message that failed to be delivered. Stored in the message storage unit 850.
  • the control unit 860 When a signal indicating that the terminal is connected to the network within the valid time stored in the trigger information storage unit 840 is received from the HLR / HSS through the HLR / HSS transmitter 820, the control unit 860 stores the trigger message storage unit 850. You can try triggering again using the trigger message stored in). Alternatively, the controller 860 may retry triggering using the trigger message stored in the trigger message storage unit 850 periodically within the valid time. If the terminal triggers again and succeeds, the control unit 860 forwards the trigger requesting to delete information indicating that the trigger request message is waiting for transmission to the HLR / HSS through the HLR / HSS communication unit 820. Status update message can be sent.
  • the controller 860 may delete the trigger message stored in the trigger message storage 850.
  • the controller 860 may generate charging information.
  • the charging information may be generated not only when the trigger succeeds but also when the trigger fails.
  • the generated charging information may be delivered to the CDF / CGF (170).
  • the generated charging information may include external identifier information of the MTC terminal 120, IMSI information mapped to external identifier information of the MTC terminal 120, identifier information of the MTC server 140, a trigger result, and the like.
  • FIG. 9 is a block diagram illustrating a configuration of an HLR / HSS according to an embodiment.
  • the HLR / HSS triggers an MTC-IWF communication unit 910 for transmitting and receiving a message with the MTC-IWF, a trigger information storage unit 920 for storing information necessary for triggering the terminal, and an MTC-IWF.
  • the MTC-IWF communication unit 910 may receive an information inquiry request for the trigger of the terminal from the MTC-IWF, and may transmit information necessary for the trigger to the terminal to the MTC-IWF.
  • the MTC-IWF communication unit 910 may transmit a failure notification message including a failure code for a detailed failure cause when the MTC-IWF fails to inquire information necessary for triggering the terminal.
  • the MTC-IWF communication unit 910 may receive trigger delivery status information from the MTC-IWF when the trigger fails due to an error of the SGSN / MME or an error on the radio path.
  • the MTC-IWF communication unit 910 When the MTC-IWF communication unit 910 receives a message from the SGSN / MME that it has detected that the terminal is in a network accessible state, the MTC-IWF communication unit 910 may transmit a notification message for notifying that the terminal is in a network accessible state to the MTC-IWF. If the trigger forwarding status information indicating that the triggering of the terminal has failed previously is received from the MTC-IWF, and the triggering of the terminal succeeds thereafter, the MTC-IWF communication unit 910 may receive a trigger forwarding status update request message from the MTC-IWF. Can be.
  • the trigger information storage unit 920 may store IMSI information mapped to an external identifier of the terminal and serving SGSN / MME information serving the terminal as information necessary for triggering the terminal.
  • the trigger information storage unit 920 may be configured to display the attribute information indicating that the terminal is an MTC device, access priority information of the terminal, attribute information for distinguishing whether the terminal has a fixed location, and fixing when the terminal has a fixed location. Additional location information can be stored.
  • the trigger state storage unit 930 stores information indicating that there is a trigger request message waiting for trigger delivery in the MTC-IWF when the trigger delivery to the terminal fails.
  • the information indicating that there is a wait trigger request message in the MTC-IWF may include identifier information of the UE that fails to deliver the trigger request message, address information of the MTC-IWF, and a detailed reason code that fails to deliver the trigger request message. If the trigger delivery to the terminal fails due to the information retrieval failure in the HLR / HSS, information indicating that there is a wait trigger request message in the MTC-IWF is generated by the HLR / HSS and stored in the trigger state storage unit 930. Can be.
  • the standby trigger in the MTC-IWF Information indicating that there is a request message may be received from the MTC-IWF through the MTC-IWF communication unit 910 and stored in the trigger state storage unit 930.
  • a trigger forwarding status update request message for removing information indicating that there is a wait trigger request message in the MTC-IWF is received from the MTC-IWF through the MTC-IWF communication unit 910
  • the trigger state information stored in the trigger state storage unit 930 may be deleted.
  • the control unit 940 extracts information necessary for the trigger from the trigger information storage unit 920, and this is MTC-IWF.
  • the communication unit 910 may transmit the MTC-IWF.
  • the controller 940 may transmit a failure notification message including the detailed reason code to the MTC-IWF through the MTC-IWF communication unit 910.
  • the controller 940 may store information indicating that there is a trigger request message waiting for trigger transmission in the MTC-IWF in the trigger state storage unit 930.
  • the controller 940 When the trigger delivery to the terminal fails due to the information inquiry failure in the HLR / HSS, the controller 940 generates information indicating that there is a wait trigger request message in the MTC-IWF and stores the information in the trigger state storage unit 930. Can be. If trigger delivery to the terminal fails for a cause other than HLR / HSS, for example, if trigger delivery to the terminal fails due to an SGSN / MME error or due to an error on the radio path, the controller 940 may control the MTC.
  • the IWF communication unit 910 may store information indicating that there is a wait trigger request message in the MTC-IWF received from the MTC-IWF in the trigger state storage unit 930.
  • the control unit 940 When receiving a message from the SGSN / MME that the terminal has detected that the network can be connected, the control unit 940 notifies the MTC-IWF to the MTC-IWF through the MTC-IWF communication unit 910 for notifying that the terminal is network accessible. You can send a message. Subsequently, when the trigger request message by the MTC-IWF is delivered to the terminal and the terminal triggering is successful, the MTC-IWF requests to update the trigger delivery status to remove information indicating that there is a wait trigger request message in the MTC-IWF.
  • Message may be transmitted, and the controller 940 has a standby trigger request message in the MTC-IWF stored in the trigger state storage unit 930 based on the trigger delivery state update request message received through the MTC-IWF communication unit 910. You can delete the information that displays.
  • FIG. 10 is a block diagram illustrating a configuration of an SGSN / MME according to an embodiment.
  • SGSN / MME MTC-IWF communication unit 1010 for transmitting and receiving messages with the MTC-IWF
  • the terminal communication unit 1020 for transmitting and receiving messages with the terminal, waiting for the trigger transmission in the MTC-IWF
  • the trigger state storage unit 1030 and the control unit 1040 for storing information indicating that there is a trigger request message are stored.
  • the MTC-IWF communication unit 1010 may receive a trigger transfer request message from the MTC-IWF. If the triggering is successful, the MTC-IWF communication unit 1010 may transmit a trigger delivery confirmation message to the MTC-IWF. If the trigger delivery request message is due to an SGSN / MME error or a failure on the radio path, the MTC-IWF communication unit 1010 may transmit a trigger delivery failure message with the detailed reason code to the MTC-IWF.
  • the terminal communication unit 1020 may transmit a trigger request message to the terminal. In addition, the terminal communication unit 1020 may receive a trigger confirmation message from the terminal. In addition, the terminal communication unit 1020 may detect a network connection state of the terminal by network registration, routing area update, PDP / PDN connection setting, and the like of the terminal.
  • the trigger state storage unit 1030 may store information indicating that there is a trigger request message waiting for trigger delivery in the MTC-IWF when the trigger delivery to the terminal fails.
  • the information indicating that there is a wait trigger request message stored in the trigger state storage unit 1030 may be deleted later when the network connection state of the terminal is detected.
  • the controller 1040 may transmit a trigger delivery request message received from the MTC-IWF through the MTC-IWF communication unit 1010 to the terminal through the terminal communication unit 1020.
  • the controller 1040 may transmit a trigger delivery confirmation message received from the terminal through the terminal communication unit 1020 to the MTC-IWF through the MTC-IWF communication unit 1010. If the triggering of the terminal fails due to an SGSN / MME error or an error on the radio path, the controller 1040 may transmit a trigger transmission failure message to the MTC-IWF through the MTC-IWF communication unit 1010. In this case, the controller 1040 may store information indicating that there is a trigger request message waiting for trigger delivery in the MTC-IWF in the trigger state storage unit 1030.
  • the controller 1040 detects the network connection state of the terminal through the terminal communication unit 1020, and if the terminal is the same as the terminal information of the information stored in the trigger state storage unit 1030, the trigger preparation notification signal HLR The information indicating that there is a trigger request message waiting for the trigger transmission in the MTC-IWF stored in the trigger state storage unit 1030 may be deleted.

Landscapes

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

Abstract

La présente invention concerne une technologie de déclenchement de terminal selon laquelle un serveur de communication de type machine (MTC) demande à un terminal MTC d'effectuer un déclenchement par l'intermédiaire d'un réseau sans fil d'une porteuse de communications mobiles, et le terminal qui a reçu la demande de déclenchement lance une communication avec le serveur MTC.
PCT/KR2012/008797 2011-11-03 2012-10-25 Serveur et procédé pour terminal de communication de type machine WO2013065996A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
KR20110113760 2011-11-03
KR10-2011-0113760 2011-11-03
KR10-2011-0117281 2011-11-11
KR1020110117281A KR20130049130A (ko) 2011-11-03 2011-11-11 기계 형태 통신 단말의 트리거링을 위한 서버 및 방법

Publications (1)

Publication Number Publication Date
WO2013065996A1 true WO2013065996A1 (fr) 2013-05-10

Family

ID=48192299

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2012/008797 WO2013065996A1 (fr) 2011-11-03 2012-10-25 Serveur et procédé pour terminal de communication de type machine

Country Status (1)

Country Link
WO (1) WO2013065996A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105794310A (zh) * 2014-01-06 2016-07-20 英特尔Ip公司 在互通功能节点和短消息服务节点之间通信以用于设备触发替换/撤销的技术
TWI708513B (zh) * 2015-07-12 2020-10-21 美商高通公司 網路安全架構
CN113038395A (zh) * 2014-07-03 2021-06-25 康维达无线有限责任公司 用于支持多种传输机制的网络的应用数据传递服务

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20110081750A (ko) * 2010-01-08 2011-07-14 엘지전자 주식회사 이동통신 시스템에서의 ｍｔｃ 장치의 모니터링 방법

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20110081750A (ko) * 2010-01-08 2011-07-14 엘지전자 주식회사 이동통신 시스템에서의 ｍｔｃ 장치의 모니터링 방법

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
KT: "MTC device trigger considering time controlled feature", 3GPP SA WG2 MEETING #86, 15 July 2011 (2011-07-15) *
PANASONIC: "Device triggering for multiple MTC device", 3GPP SA WG2 MEETING #85, 20 May 2011 (2011-05-20), pages 2 - 112502 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105794310A (zh) * 2014-01-06 2016-07-20 英特尔Ip公司 在互通功能节点和短消息服务节点之间通信以用于设备触发替换/撤销的技术
EP3092869A4 (fr) * 2014-01-06 2017-05-31 Intel IP Corporation Techniques destinées à la communication entre des n uds de fonction d'interfonctionnement et de service d'envoi de messages courts pour le remplacement/rappel d'un déclencheur de dispositif
CN113038395A (zh) * 2014-07-03 2021-06-25 康维达无线有限责任公司 用于支持多种传输机制的网络的应用数据传递服务
TWI708513B (zh) * 2015-07-12 2020-10-21 美商高通公司 網路安全架構
US11329969B2 (en) 2015-07-12 2022-05-10 Qualcomm Incorporated Network security architecture

Similar Documents

Publication Publication Date Title
WO2013055063A1 (fr) Serveur de message court, procédé de déclenchement de terminal de serveur associé, serveur de distribution de requête de déclenchement, procédé de distribution de requête de déclenchement de serveur associé
WO2013141599A1 (fr) Procédé et appareil de déclenchement de groupe mtc dans un système de communication sans fil
WO2017026760A1 (fr) Terminal et son procédé de communication
WO2018143774A1 (fr) Procédé de gestion d'enregistrement pour un terminal accédant à un réseau 5g au moyen d'un accès non 3 gpp
WO2011021875A2 (fr) Serveur pour plan de commande au niveau d'un réseau de communication mobile et procédé de commande de service d'accès ip local
WO2011099769A2 (fr) Système de communication sans fil et procédé de connexion entre un équipement utilisateur et une entité de gestion de mobilité
WO2012138107A2 (fr) Messagerie sur un réseau
WO2014027740A1 (fr) Procédé et appareil pour une messagerie basée sur des groupes dans un réseau de communication mobile
WO2012111952A2 (fr) Procédé de transmission et de réception d'informations de mise à jour de paramètre dans un système de communication sans fil, et dispositif l'utilisant
JP6406814B2 (ja) 通信システム、サービス制御装置、ｍｔｃユーザ装置、ゲートウェイ装置及び通信方法
WO2015174702A1 (fr) Procédé et appareil pour une émission et une réception de signal de hss/mme dans un système de communication sans fil
WO2012081882A2 (fr) Procédé et appareil pour la transmission fiable d'une diffusion multiple vers un groupe au moyen d'une technique de radiodiffusion cellulaire dans un système de communication mobile
WO2012153971A2 (fr) Procédé et appareil d'envoi de données de multidiffusion à des dispositifs m2m dans un système d'accès sans fil
WO2012074337A2 (fr) Appareil et procédé d'envoi/réception de trafic de diffusion groupée dans un système d'accès sans fil prenant en charge une communication de machine à machine
EP3566509A1 (fr) Procédé de gestion d'enregistrement pour un terminal accédant à un réseau 5g au moyen d'un accès non 3 gpp
JP5904206B2 (ja) 通信システム、通信方法及び通信プログラム
WO2012020958A2 (fr) Procédé et appareil de fourniture de services sur un terminal d'un système de communication mobile
JP2010088055A (ja) 通信システム、移動機、端末管理装置および通信方法
WO2013065996A1 (fr) Serveur et procédé pour terminal de communication de type machine
WO2013165168A1 (fr) Procédé et dispositif pour surveiller un équipement d'utilisateur dans un réseau de communication mobile
AU2016310558B2 (en) Method and device for lawful interception for proximity services
WO2015026109A1 (fr) Procédé et dispositif destinés à annuler le déclenchement d'un dispositif dans un système de communication sans fil
WO2010090470A2 (fr) Système et procédé de fourniture de service de pousser de message dans un système de communication sans fil
WO2013051898A2 (fr) Serveur de transfert de demande de déclenchement, procédé de transfert d'une demande de déclenchement d'un serveur, réseau de communication et procédé de déclenchement de terminal dans un réseau de communication
WO2017003255A1 (fr) Procédé de sélection de réseau et station de base

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

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

Country of ref document: EP

Kind code of ref document: A1