KR20130049632A - Server and method for device triggering using short message service - Google Patents

Abstract

PURPOSE: A server for triggering a device using a dynamic MSISDN(Mobile Subscriber ISDN Number) and a method thereof are provided to trigger the device by effectively using MSISDN resources. CONSTITUTION: When a terminal registers a location, a dynamic MSISDN is assigned to the terminal(S302). A trigger request message including an external identifier of the terminal is received from an MTC(Machine Type Communication) server. The external identifier is mapped to the dynamic MSISDN. A short text message including a triggering request is transmitted to a short text message server through the dynamic MSISDN(S303). When the terminal releases location registration, the terminal releases the assigned dynamic MSISDN(S304). [Reference numerals] (AA) Start; (BB) End; (S301) Ensure DIMSI and DMSISDN areas; (S302) Assign DMSISDN when a terminal registers a location; (S303) Trigger the terminal; (S304) Release the DMSISDN when the terminal releases location registration

Description

Server and method for device triggering using short message service

The present invention relates to device triggers in a communication network for mechanical communication.

Machine Type Communication (MTC) is a form of data communication that represents a machine or machine to machine communication in which one or more entities do not or require minimal human interaction. An MTC device user terminal (or MTC device) 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. .

Many MTC application services provided through MTC communication rarely transmit data at long time intervals. In the case of such an application service, 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. However, in another way, 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. As in the latter case, 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.

It may be considered to use an existing short message service (SMS) as a message transmitted to the terminal for the MTC device triggering.

As an identifier of a device used for routing of a terminal message service in a network providing a short message service, a mobile subscriber ISDN number (MSISDN) or an international mobile subscriber identity (IMSI) may be considered. When using MSISDN, MSISDN resources may run out when multiple devices use the network. When using IMSI, there is a need for changes in the interface and nodes for short message services.

An object of the present invention is to provide a server and a method capable of device triggering using the MSISDN resources efficiently.

The present invention provides a server and a method for device triggering through a short message using an MSISDN dynamically allocated to a terminal.

According to the present invention described above, device triggering can be performed efficiently using MSISDN resources.

1 illustrates the structure of a communication network in which embodiments of the invention are implemented.
2 illustrates an example of a method for transmitting a terminal triggering request using SMS.
3 illustrates a terminal triggering method in a wireless network according to an embodiment of the present invention.
4 is a flowchart illustrating the detailed steps of step S302 of FIG. 3.
FIG. 5 is a flowchart illustrating detailed steps of step S303 of FIG. 3.
FIG. 6 is a flowchart illustrating detailed steps of step S304 of FIG. 3.

Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary drawings. In adding reference numerals to the components of each drawing, it should be noted that the same reference numerals are used to refer to the same components as much as possible even if displayed on different drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.

This specification will be described based on machine type communication (MTC). 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.

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 (or MTC device) 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. .

Many MTC application services provided through MTC have a feature of rarely transmitting data at long time intervals. In the case of such an application service, 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. However, in another way, 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. As in the latter case, 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.

1 illustrates the structure of a communication network in which embodiments of the invention are implemented.

Referring to FIG. 1, the plurality of MTC terminals 102 may communicate with one or more MTC servers 104 through the wireless network 110.

The MTC terminal 102 or the MTC device is a user equipment (eg, an electric meter equipped with a mobile communication module) that performs communication between devices with the MTC server 104 through the wireless network 110 of the mobile communication operator. , Gas meters, vending machines, etc.).

The MTC server 104 is a server that controls the terminal 102 and collects data of the terminal 102 by communicating with the MTC terminal 102 through the wireless network 110 of the mobile communication operator.

The MTC user may use a service provided by the MTC server 104 through an application server (not shown) in communication with the MTC server 104.

The wireless network 110 includes a Serving GPRS Support Node / Mobile Switching Center (SGSN / MSC) 112, a Home Location Register / Home Subscriber Server (HLR / HSS) 114, and a Short Message Service-Gateway Mobile Switching (SMS-GMSC). Center 116, Short Message Service-Service Center (SMS-SC) 118, Machine Type Communication InterWorking Function (MTC IWF) 120, and the like.

SGSN / MSC 112 is a switch that performs a packet switching function for a mobile terminal.

The HLR / HSS 114 is an entity that stores user subscription related information (user identifier, user profile, etc.).

The SMS-GMSC 116 is a switch functioning as a gateway for short message delivery from the SMS-SC 118 to the mobile operator's wireless network. It performs the function of inquiring the routing information (information of the serving SGSN or MSC) carrying the short message from the HLR / HSS 114 for the mobile terminated SMS transmission. In actual implementation, it may be implemented integrated into the SMS-SC 118.

The SMS-SC 118 relays, stores and forwards short messages between short message entities (SMEs) (for example, user terminals) capable of transmitting and receiving short messages. to be.

In order to facilitate device triggering by a plurality of MTC servers 104 in a wireless network of a mobile carrier that must accommodate a large number of MTC terminals 102, a trigger request is received by receiving a trigger request of the MTC server 104. MTC server authentication of the transmitting MTC server 104, trigger request authorization, charging, trigger delivery mechanism selection, device identifier mapping, etc. MTC IWF 120 may be required to perform the MTC device triggering control function.

The MTC IWF 120 may be implemented as a function of a standalone entity or some function of other wireless network equipment. The MTC server 102 may transmit a trigger request to the MTC IWF 120 by resolving an IP address of the MTC IWF 120 performing a device triggering control function for a specific MTC terminal 102.

In a typical SMS, a short message sent from a short message entity (SME) is received by the SMS-SC 118, and the SMS-SC 118 transmits a short message to the SMS-GMSC 116. The SMS-GMSC 116 queries the HLR / HSS 114 for the necessary routing information to deliver the short message. When querying the routing information, the mobile subscriber ISDN number (MSISDN) may be used as an identifier of the terminal. The SMS-GMSC 116 inquiring the routing information transmits the short message to the corresponding SGSN / MSC 112, and the SGSN / MSC 112 transmits the short message to the terminal 102 and confirms it. SGSN / MSC 112 reports the short message delivery success message to SMS-GMSC 116. Previously, SMS transmission failed due to network detach of the terminal, and thus the terminal access indication is set in the HLR / HSS 114, so that the user terminal network attaches and the short message transmission succeeds. If so, the SMS-GMSC 116 updates the information of the HLR / HSS 114. The SMS-GMSC 116 reports the success of the short message delivery to the SMS-SC 118.

On the other hand, when the short message transmission from the SGSN / MSC 112 to the terminal 102 fails, the SMS-GMSC 116 reports the transmission failure to the SMS-SC 118, and the SMS-SC 118 in advance The short message retransmission is performed according to the set retransmission method.

This SMS transmission method may be used for terminal trigger. 2 illustrates an example of a method for transmitting a terminal triggering request using SMS.

The MTC server 104 functions as an SME and transmits a trigger request short message to the SMS-SC 118 (direct model) (S201). Alternatively, the MTC server 104 delivers a trigger request message to the MTC IWF 120, and the MTC IWF 120 functions as an SME to deliver a trigger request short message to the SMS-SC 118 (indirect model) ( S201 '). The SMS-SC 118 transmits a short message to the SMS-GMSC 116 (S202). The SMS-GMSC 116 queries the routing information needed to deliver the short message via the HLR / HSS 114, that is, the information of the SGSN or MSC 112 serving the terminal 102 to receive the short message ( S203). Based on the routing information, the SMS-GMSC 116 transmits a short message to the SGSN / MSC 112 (S204). SGSN / MSC 112 transmits and confirms a short message to the terminal 102 (S205). SGSN / MSC 112 reports the short message delivery success to SMS-GMSC 116 (S206). In the state that the mobile station Not Reachable Flag is set to the terminal 102 is not accessible to the HLR / HSS 114 due to the previous SMS failure due to the network detach of the terminal 102 (network detach), etc. If the SMS mobile incoming procedure is executed after the terminal 102 has network attached, the SMS-GMSC 116 updates the information of the HLR / HSS 114 (S207). If the SMS reception of the terminal 102 has not failed before, step S207 may be omitted. The SMS-GMSC 116 reports the success of the short message delivery to the SMS-SC 118 (S208). The SMS-SC 118 directly reports the success of the short message delivery to the MTC server 104 (S209), or reports the success of the short message delivery to the MTC server 104 through the MTC IWF 120 (S209 '). Then, the data communication between the terminal 102 and the MTC server 104 is started (S210).

The SMS-GMSC 116 receives a process failure (for example, deregistration of the network of the terminal 102, etc.) from an entity (terminal 102, SGSN / MSC 112, HLR / HSS 114, etc.) of the mobile incoming process. ), The SMS-GMSC 116 reports the message transmission failure to the SMS-SC 118, and the SMS-SC 118 may perform the retransmission according to a preset retransmission method.

The short message may include address information (eg, an IP address) of the MTC server 104 for data communication with the MTC server 104, and the terminal 102 may include an indication of a trigger request. When receiving the MTC server 104 is set in advance to communicate with. As the outgoing telephone number of the SMS, the MSISDN assigned by the MTC server 104 may be used, and the MSISDN of the terminal 102 to be triggered may be used as the incoming telephone number.

The MTC IWF 120 may request triggering of the terminal 102 by mapping the external identifier of the terminal 102 with the MSISDN. The external identifier is a globally unique value and is an identifier used between the MTC server 104 and the MTC IWF 120, and the Mobile Station International ISDN Number (MSISDN), Fully Qualified Domain Name (FQDN), and Network Access Identifier (NAI). ), A SIP Session Initiation Protocol Uniform Resource Identifier (URI), an Internet Protocol (IP) address, and the like. When the external identifier is not the MSISDN, the triggering of the terminal 102 may be requested using the MSISDN mapped to the external identifier.

The MSISDN mapping method is a method of reusing an existing network function, which has an advantage that there is no significant effect on the system design. However, as the number of MTC terminals increases in the long term, it is necessary to allocate MSISDN, which is a fixed identifier, to many MTC terminals, which may cause a shortage of MSISDN resources.

Alternatively, the MTC IWF 120 may request triggering of the terminal 102 by mapping an external identifier of the terminal 102 to an internal identifier (for example, an International Mobile Subscriber Identity (IMSI)) in the network. The SMS-GMSC 116 requests the routing information query for the external identifier directly from the HLR / HSS 114 and then performs MTC terminal triggering based on IMSI without MSISDN.

The IMSI mapping method has the advantage of solving the MSISDN resource shortage. However, there is a disadvantage in that the structure of an existing network using MSISDN needs to be changed. In other words, the MTC terminal triggering method using SMS is implemented to operate only when the MSISDN telephone number is the called number. Therefore, when using the IMSI, the SMS interface and the node need to be changed.

3 illustrates a terminal triggering method in a wireless network according to an embodiment of the present invention.

Referring to FIG. 3, a preliminary work step of securing areas of dynamic IMSI (DIMSI) and dynamic MSISDN is performed (S301).

In the present specification, DIMSI is IMSI used for mapping of DMSISDN. The DIMSI may be granted to the MTC terminal, for example. DMSISDN is an MSISDN that is dynamically allocated and managed at MTC IWF 120. When the terminal 102 registers a location, the terminal 102 may be assigned a DMSISDN, and when the terminal 102 releases the location, the DMSISDN assigned to the terminal 102 may be released.

IMSI is stored in UICC and used to represent user information. IMSI can consist of 15 decimal digits, and the 15 digits can be classified into 3 digits Mobile Country Code (MCC), 2 or 3 digits Mobile Network Code (MCC), and Mobile Subscriber Identification Number (MSIN). Can be. One MCC is assigned to a country. The MNC is used in conjunction with the MCC to identify the country's MNO. MSIN is a value for identifying a user. The prefix of the MSIN may be determined by the MNO's policy, such as to distinguish the user's attributes (eg, prepaid subscriber, postpaid subscriber) or to identify HLRs that accept subscriber information.

Specific resources among IMSI resources may be allocated for DIMSI. For example, a particular MNC may be reserved for DIMSI resources, or certain values of MSIN may be reserved for DIMSI resources. For example, when MNC = 99 is reserved for the DIMSI resource, the IMSI of 45099XXXXXXXXXX (450 is MCC, 99 is MNC, and XXXXXXXXXX is MSIN) is DIMSI.

MSISDN means the number used by the actual user. The MSISDN may include a Country Code (CC) assigned to each country, a National Destination Code (NDC) for identifying a carrier, and a serial number (SN) which is a serial number belonging to each carrier.

Specific resources among the MSISDN resources may be allocated for the DMSISDN. For example, certain NDCs may be reserved for DMSISDN resources, or certain values of SN may be reserved for DMSISDN resources. For example, when NDC = 99 is reserved for DMSISDN resources, MSISDN with 8299XXXXXXXX (82 is CC, 99 is NDC, XXXXXXXX is SN) is DMSISDN.

In the DIMSI and DMSISDN area secure step (S301), the allocated DIMSI and DMSISDN resource information is registered in the HLR / HSS 114 and the MTC IWF 120. To this end, the HLR / HSS 114 may include a storage unit for storing DIMSI resource information, and the MTC IWF 120 may include a storage unit for storing DIMSI and DMSISDN resource information. Subsequently, in the mapping step of the DIMSI and the external identifier through subscription, the MTC IWF 120 performs one-to-one mapping between the external identifier and the DIMSI through the subscription with the MTC server 104. To this end, the MTC IWF 120 may manage a dynamic table (Dtable) as a table including DIMSI, external identifier, and DMSISDN information. Dtable may include information as shown in Table 1 below.

[Table 1]

In Table 1, the external identifier is a globally unique value, and may be composed of a domain identifier and a local identifier. DMSISDN may be allocated to a network registered terminal and may not be allocated to a terminal not registered.

In addition, the MTC IWF 120 may store information on the unassigned DMSISDN.

Referring back to FIG. 3, when the terminal 102 registers a location, a DMSISDN is assigned to the terminal 102 (S302).

4 is a flowchart illustrating the detailed steps of step S302 of FIG. 3.

Referring to FIG. 4, the terminal 102 performs network registration (location registration) with the SGSN / MME 112 (S401), and the SGSN / MME 112 transmits the corresponding information to the HLR / HSS 114. (S402). The HLR / HSS 114 performs IMSI location registration (S403). When the HLR / HSS 114 has the DIMSI resource information in advance and confirms that the IMSI of the terminal 102 is the DIMSI, the HLR / HSS 114 requests the MTC IWF 120 to allocate the DMSISDN ( S404). The MTC IWF 120 reconfirms that the IMSI of the terminal 102 is a DIMSI through the Dtable inquiry, allocates the remaining DMSISDN which is not used among the DMSISDN resources, and updates the Dtable with the changed information according to the DMSISDN allocation (S405). .

An example of the Dtable update in step S405 is shown in Table 2 below.

[Table 2]

In Table 2, MTC IWF 120 receives the DIMSI information of the terminal 102 from the HLR / HSS 114. The MTC IWF 120 knows in advance the external identifier mapped to the DIMSI of the terminal 120. The MTC IWF allocates one of the remaining DMSISDNs to the terminal 102 having registered the location, and the corresponding DMSISDN information in the Dtable is changed to the DMSISDN assigned in the <blank>.

The MTC IWF 120 transmits DMSISDN allocation information to the HLR / HSS 114 (S406), and the HLR / HSS 114 updates the profile information of the UE 102 by allocating DMSISDN to the UE profile corresponding to the DIMSI. (S407).

When the process of FIG. 4 is completed, the MTC IWF 120 knows the MSISDN (DMSISDN) mapped to the external identifier of the terminal 102, and the HLR / HSS 114 is connected to the MSISDN (DMSISDN) of the terminal 102. I know the IMSI that is mapped (DIMSI).

Referring to FIG. 3 again, terminal triggering is performed by a request from the MTC server 104 (S303).

FIG. 5 is a flowchart illustrating detailed steps of step S303 of FIG. 3.

Referring to FIG. 5, the MTC server 104 transmits a trigger request message including external identifier information of the terminal 102 to the MTC IWF 120 (S501). The MTC IWF 120 maps the DMSISDN assigned to the external identifier using the Dtable (S502), and functions as an SME to transmit an SMS triggering request using the MSISDN (DMSISDN) to the SMS-SC 118 (S503). The SMS-SC 118 transmits an SMS triggering request using the MSISDN (DMSISDN) to the SMS-GMSC 116 (S504). The SMS-GMSC 116 uses the MSISDN (DMSISDN) to provide the triggering message to the HLR / HSS 114 for routing information (IMSI of the terminal 102, serving SGSN / MSC serving the terminal 102). 112), and so on (S505). The HLR / HSS 112 is in a state of knowing the DIMSI mapped to the DMSISDN by the step S302 described above. The SMS-GMSC 116 transmits a triggering message to the serving SGSN / MSC 112 (S506). The SGSN / MSC 112 transmits a triggering message to the terminal 102 and checks whether the message is delivered successfully (S507). SGSN / MSC 112 reports the success of triggering message delivery to SMS-GMSC 116 (S508), SMS-GMSC 116 reports the success of triggering message delivery to SMS-SCSC 118 (S509), The SMS-SC 118 reports the triggering message delivery success to the MTC IWF 120 (S510), and the MTC IWF 120 reports the success of the triggering message delivery to the MTC server 104 (S511). In addition, the terminal 102 initiates data communication with the MTC server 104 (S512).

On the other hand, when the terminal 102 is in a network de-registration state, or the like, when the DMSISDN is not assigned to the external identifier of the terminal 102, the MTC IWF 120 determines the external identifier and the DMSISDN of the terminal 102. After the step S502 of mapping, a message indicating that the terminal 102 is inaccessible (triggering failure message) (for example, MTC Not Reachable Flag) may be reported to the MTC server 104, and steps S503 to S512 may be omitted. have. When the valid time is set in the triggering request message from the MTC server 104 and the terminal 102 is in the network deregistration state, the MTC IWF 120 receives a DMSISDN assignment request signal from the HLR / HSS 114 within the valid time. 4, the steps S502 to S512 of FIG. 5 may be performed after the steps S405 to S407 of FIG. 4 are performed.

Referring back to Figure 3, when the terminal releases the location registration DMSISDN termination procedure is carried out (S304). In FIG. 3, the terminal triggering is performed once between the step S302 in which the terminal registers the location of the DMSISDN and the step S304 in which the terminal cancels the location registration of the DMSISDN. It is also possible that the step S303 is repeated a plurality of times between steps S302 and S304.

FIG. 6 is a flowchart illustrating detailed steps of step S304 of FIG. 3.

Referring to FIG. 6, the terminal 102 performs a location registration cancellation procedure with the SGSN / MSC 112 (S601), and the SGSN / MSC 112 transmits the corresponding information to the HLR / HSS 114 (S602). ). The HLR / HSS 114 performs termination of IMSI location registration (S603). When the HLR / HSS 114 has the DIMSI resource information in advance and confirms that the IMSI of the terminal 102 is the DIMSI, the HLR / HSS 114 requests the MTC IWF 120 to terminate the DMSISDN ( S604). The MTC IWF 120 reconfirms that the IMSI of the terminal 102 is a DIMSI through a Dtable inquiry, cancels a corresponding DMSISDN, and updates the Dtable with information changed according to the DMSISDN termination (S605).

An example of the Dtable update in step S605 is shown in Table 3 below.

[Table 3]

In Table 3, MTC IWF 120 receives the DIMSI information of the terminal 102 from the HLR / HSS 114. The MTC IWF 120 knows in advance the external identifier mapped to the DIMSI of the terminal 120. The MTC IWF revokes the DMSISDN assigned to the terminal 102, and the corresponding DMSISDN information in the Dtable is changed to <blank> in the assigned DMSISDN. The revoked DMSISDN may then be used for another terminal 102 that has registered a location.

The MTC IWF 120 transmits DMSISDN termination information to the HLR / HSS 114 (S506), and the HLR / HSS 114 updates the profile information of the terminal 102 by deleting the DMSISDN in the terminal profile corresponding to the DIMSI. (S607).

According to the above-described embodiment, when the MTC server triggers the MTC terminal triggering using the SMS through the wireless network of the mobile communication provider, it may provide a method capable of triggering the MTC terminal by dynamically allocating an MSISDN number. By dynamically allocating and managing MSISDN resources to external identifiers, the MTC IWF can reduce MSISDN shortages and trigger MTC terminal triggers without major changes to the existing network structure (using MSISDN for SMS routing). .

In particular, in case of not always on MTC terminal registered on the network (or infrequently access MTC device), MSISDN resources are allocated only to terminals registered in the network. It can be used efficiently.

The above-described embodiment is composed of the terminal 102, MTC server 104 and the wireless network 110, the wireless network 110 is SGSN / MSC 112, HLR / HSS 114, SMS-GMSC (116) ), SMS-SC 118 and MTC IWF 120 has been described by way of example, the present invention is not limited to the system consisting of the above-described entity, it is composed of entities having the same or similar functions Applicable to the system.

The above description is merely illustrative of the technical idea of the present invention, and those skilled in the art to which the present invention pertains may make various modifications and changes without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be construed according to the following claims, and all technical ideas falling within the scope of the same shall be construed as falling within the scope of the present invention.

Claims (1)

Assigning a dynamic Mobile Subscriber ISDN Number (MSISDN) to the terminal when the terminal registers a location;
Receiving a trigger request message including an external identifier of the terminal from a machine type communication (MTC) server;
Mapping the external identifier to the dynamic MSISDN and sending a short message including a trigger request to the short message server using the dynamic MSISDN; And
And terminating the dynamic MSISDN assigned to the terminal when the terminal cancels the location registration.

Images