KR102510056B1 - Gateway apparatus and paging method thereof - Google Patents

Abstract

The present invention relates to a gateway device and a paging method thereof. The disclosed paging method of the gateway device includes checking the state of a bearer for communication with the IoT terminal when a service event for the IoT terminal occurs, and information on a default bearer previously set for the IoT terminal when the bearer is released. and processing paging for the IoT terminal according to the acquired default bearer information. According to this embodiment of the present invention, the gateway device does not set a dedicated bearer for the IoT service and processes paging for the IoT terminal using information on a default bearer set at the beginning of the service. As such, according to the present invention, a network entity of a general network constructed for a general mobile communication service, such as an LTE network, can be changed into a structure suitable for providing an IoT service targeting an IoT terminal. Therefore, there is an advantage of providing efficiency in terms of cost compared to the case of building a dedicated IoT network using a separate communication protocol.

Description

Gateway device and its paging method {GATEWAY APPARATUS AND PAGING METHOD THEREOF}

The present invention relates to a gateway device and a paging method thereof, and more particularly, to a gateway device supporting an IoT service for an Internet of Things (IoT) terminal and a paging method for the IoT service.

As is well known, interest in and utilization of communication services between objects in addition to general mobile communication services between people are increasing. Such communication services between objects are variously called IoT, machine to machine communication (M2M), machine type communication (MTC), smart device communication, or machine oriented communication. Hereinafter, it will be collectively referred to as an IoT service.

Communication networks for providing IoT services to IoT terminals include general networks such as LTE (Long Term Evolution) networks that provide general mobile communication services, IoT dedicated networks using separate communication protocols, and hybrid networks that use both general and dedicated networks. IoT networks can be used.

Here, the network entities constituting the general network and the hybrid IoT network have a structure suitable for providing a large-capacity data service while supporting the mobility of a general mobile communication terminal. Representative examples include location and state management of mobile communication terminals and tunneling protocols for supporting handover. These functions may be necessary for a stable mobile communication service.

However, in the case of an IoT terminal, it can be located only at a fixed point according to its purpose of use, and such a mobility-free IoT terminal does not require a complicated handover mechanism. Even if the location is slightly changed in a home or factory, handover is not required if the location does not deviate from the service area provided by the base station initially registered.

Therefore, when an IoT service is provided using network entities constituting a general network and a hybrid IoT network as they are, there is a problem in that resources such as network entities are wasted.

Of course, as an alternative, it is possible to build a dedicated IoT network using a separate communication protocol to accommodate IoT terminals, but it is more cost-effective to accommodate IoT terminals by using a general network such as an LTE network for which an infrastructure has already been built. It is self-evident that high

Republic of Korea Patent Publication No. 10-2016-0021032, published on February 24, 2016.

According to an embodiment of the present invention, a gateway device having a structure suitable for providing an IoT service targeting an IoT terminal and a method of paging the IoT terminal for the IoT service by the gateway device are provided.

The problem to be solved by the present invention is not limited to those mentioned above, and another problem to be solved that is not mentioned will be clearly understood by those skilled in the art from the description below.

A paging method of a gateway device according to an aspect of the present invention includes checking a state of a bearer for communication with an IoT terminal when a service event for the IoT terminal occurs, and if the bearer is released, the IoT terminal It may include acquiring information of a default bearer that has been previously set for , and processing paging for the IoT terminal according to the obtained information of the default bearer.

A gateway device according to another aspect of the present invention includes a transmission and reception unit for transmitting and receiving signals to and from an IoT terminal through a wireless access network, and a control unit for controlling the transmission and reception unit to process paging for the IoT terminal, wherein the control unit, When a service event for the IoT terminal occurs, a state of a bearer for communication with the IoT terminal is checked, and when the bearer is in a released state, information on a default bearer previously set for the IoT terminal is acquired, and the acquisition Paging for the IoT terminal may be processed by controlling the transmission/reception unit according to the default bearer information.

According to an embodiment of the present invention, the gateway device processes paging for the IoT terminal using information on a default bearer set at the beginning of the service without setting a dedicated bearer for the IoT service.

As such, according to the present invention, a network entity of a general network constructed for a general mobile communication service, such as an LTE network, can be changed into a structure suitable for providing an IoT service targeting an IoT terminal.

Therefore, there is an effect of providing efficiency in terms of cost compared to the case of building a dedicated IoT network using a separate communication protocol.

1 is a block diagram of an IoT service system including a gateway device and a control entity according to an embodiment of the present invention.
2 is a detailed configuration diagram of a gateway device according to an embodiment of the present invention.
3 is a flowchart illustrating a process of setting a default bearer in an IoT service system including a gateway device and a control entity according to an embodiment of the present invention.
4 and 5 are flowcharts illustrating a process of processing paging for an IoT terminal in a gateway device according to an embodiment of the present invention.

Advantages and features of the present invention, and methods of achieving them, will become clear with reference to the detailed description of the following embodiments taken in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in various different forms, and only these embodiments make the disclosure of the present invention complete, and common knowledge in the art to which the present invention belongs. It is provided to completely inform the person who has the scope of the invention, and the present invention is only defined by the scope of the claims.

In describing the embodiments of the present invention, if it is determined that a detailed description of a known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description will be omitted. In addition, terms to be described later are terms defined in consideration of functions in the embodiment of the present invention, which may vary according to the intention or custom of a user or operator. Therefore, the definition should be made based on the contents throughout this specification.

Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings.

1 is a block diagram of an IoT service system including a gateway device and a control entity according to an embodiment of the present invention.

As shown therein, the IoT service system 100 according to an embodiment of the present invention includes the IoT terminal 110, the eNB 120, the control entity 130, the HSS 140, and the gateway device 150.

The IoT terminal 110 is located at a fixed point of a cell among a plurality of cells existing in the service area of the eNB 120 and receives the IoT service. For example, the IoT terminal 110 may be an IoT module of various home appliances for home automation.

The eNB 120 performs a role of a base station that guarantees mobility by communicating with a mobile communication terminal (not shown) existing within its service area. In addition, it serves as a base station for providing IoT services to the IoT terminal 110. The eNB 120 controls radio resources such as radio bearer control, radio admission control, connection mobility control, and dynamic resource allocation to mobile communication terminals. A radio resource management function may be performed.

The control entity 130 is a network entity that builds a service network for providing IoT services to the IoT terminal 110, and when an IP (Internet Protocol) address assignment for the IoT terminal 110 is requested, the IoT terminal 110 A default bearer is established between the control entity 130 and the gateway device 150 so that the IP address allocated by the gateway device 150 is transmitted to the IoT terminal 110. In addition, the control entity 130 may store the information of the configured default bearer so that it can be used in a paging procedure later. For example, the control entity 130 may restrict and implement some functions of a Mobility Management Entity (MME) for constructing an LTE network.

HSS (Home Subscriber Server) 140 is a network node including a database including subscriber information for the IoT terminal 110, provides subscriber information to the control entity 130, and IoT terminal The location of (110) can be registered and managed. For example, when establishing an LTE network, the HSS 140 may play a role of storing and managing subscriber information of a mobile communication terminal receiving LTE service.

When setting a default bearer with the IoT terminal 110 is requested, the gateway device 150 establishes a default bearer between the IoT terminal 110, the control entity 130, and the gateway device 150. The IoT terminal 110 ) by assigning an IP address to the IoT terminal 110 to use the Internet 10. In addition, the gateway device 150 may store information on the configured default bearer so that it can be used in a later paging procedure. In addition, when a service event for the IoT terminal 110 occurs, the state of a bearer for communication with the IoT terminal 110 is checked, and if the bearer is in a released state, information on a preset default bearer is obtained, and the obtained Paging for the IoT terminal 110 is processed according to the default bearer information. At this time, the previously set default bearer information may use default bearer information stored during the process of allocating an IP address to the IoT terminal 110 or query the control entity 130 and receive the response. If the default bearer is not released, a signal may be delivered through the corresponding default bearer. For example, the gateway device 150 may be implemented by integrating a Serving Gateway (SGW) and a Packet Data Network Gateway (PGW) constructing an LTE network, but limiting some of their functions.

2 is a detailed configuration diagram of a gateway device 150 according to an embodiment of the present invention.

As shown therein, the gateway device 150 according to an embodiment includes a storage unit 151, a transmission/reception unit 152, and a control unit 153.

Referring to FIGS. 1 and 2 , the storage unit 151 stores default bearer information set during the process of allocating an IP address for the IoT terminal 110 . For example, the storage unit 151 may be implemented as a non-volatile memory device such as electrically erasable programmable read-only memory (EEPROM), and may store information about the eNB 120 through which a default bearer tunnel passes.

The transmitting/receiving unit 152 transmits/receives a signal to/from the IoT terminal 110 through a wireless access network under the control of the controller 153. For example, the transceiver 152 may be implemented as an LTE communication module.

The controller 153 controls the transceiver 152 to process paging for the IoT terminal 110 . When a service event for the IoT terminal 110 occurs, the control unit 153 checks the state of a bearer for communication with the IoT terminal 110, and if the bearer is released, a preset setting for the IoT terminal 110 occurs. Information on the default bearer that has been used is obtained, and paging for the IoT terminal 110 is processed by controlling the transmission/reception unit 152 according to the obtained information on the default bearer. Here, the control unit 153 may query the network entity 130 for information on the default bearer established during the process of allocating the IP address to the IoT terminal 110 and receive a response thereof. Alternatively, the control unit 153 sets the default bearer during the process of allocating the IP address for the IoT terminal 110, and then stores the default bearer information in the storage unit 151, and the bearer with the IoT terminal 110 is released. In this state, paging for the IoT terminal 110 may be processed by checking default bearer information stored in the storage unit 151 . If the default bearer is not released, the control unit 153 may control the transmission/reception unit 152 to transmit a signal through the corresponding default bearer. For example, the controller 153 may be implemented with a processor such as a central processing unit (CPU).

3 is a flowchart illustrating a process of setting a default bearer in an IoT service system including a gateway device and a control entity according to an embodiment of the present invention.

1 to 3, the IoT terminal 110 is located at a fixed point of any one cell among a plurality of cells existing in the service area of the eNB 120, and wirelessly accesses the eNB 120 to obtain an IP address. Assignment is requested (S201).

Then, the eNB 120 requests the control entity 130 to allocate an IP address for the IoT terminal 110 (S203), and the control entity 130 sends subscriber information of the IoT terminal 110 to the HSS 140. It is requested and delivered (S205).

Subsequently, the control entity 130 requests the gateway device 150 to set up a bearer for an initial service based on the subscriber information of the IoT terminal 110 transmitted from the HSS 140 (S207).

Here, the gateway device 150 allocates an IP address to the IoT terminal 110 using a preset IP address allocation table, and then sends a response signal to the bearer setup request to the control entity 130 (S209 and S211).

Thereafter, a default bearer setup procedure for the IoT service is performed between the IoT terminal 110, the eNB 120, the control entity 130, and the gateway device 150. At this time, the IP address allocated in step S209 is the IoT terminal. It is delivered to (110) (S213).

Then, the control entity 130 registers the location of the IoT terminal 110 in the HSS 140, and the location information on the IoT terminal 110 is updated in the HSS 140 (S215).

Then, the control entity 130 may store the information of the default bearer established in step S211 so that it can be used in a paging procedure thereafter (step S217).

In addition, the gateway device 150 may also store the default bearer information established in step S211 so that it can be used in a paging procedure later. For example, identification information about the eNB 120 used for the default bearer tunnel may be stored under the control of the controller 153 (S219).

Here, the IoT service system 100 can be designed and built so that only one of steps S217 and S219 is selectively performed, and the IoT service system 100 can be designed and built so that both steps S217 and S219 are performed. there is.

4 and 5 are flowcharts for explaining a process of processing paging for an IoT terminal in a gateway device according to an embodiment of the present invention, FIG. 4 is a case in which step S217 of FIG. 3 is performed, and FIG. This is the case in which step S219 of FIG. 3 is performed.

1 to 4, the control unit 153 of the gateway device 150 checks the state of the bearer for communication with the IoT terminal 110 when a service event occurs for the IoT terminal 110 (S301 ).

Here, the control unit 153 checks whether the default bearer, which was previously set at the beginning of the service, is maintained by the transceiver 152 or released (S303), and if it is maintained, the IoT terminal 110 through the corresponding default bearer. ) and transmits a signal to (S305).

However, if the previously set default bearer is released, the control unit 153 controls the transceiver 152 to provide the control entity 130 with information on the default bearer set during the process of allocating the IP address for the IoT terminal 110. Inquiry is made and the response is received (S307).

Then, the control unit 153 of the gateway device 150 queries the control entity 130 and processes paging for the IoT terminal 110 according to the obtained default bearer information. For example, paging is processed through the IoT terminal 110 by selecting the eNB 120 based on path information included in the default bearer information (S309).

Thereafter, the IoT service for the IoT terminal 110 is provided, which is in the service area provided by the eNB 120 initially registered even if the IoT terminal 110, which does not require mobility, slightly changes location in a home or factory. If it does not deviate, since handover is not required, IoT service can be provided through the eNB 120 used in the IP address allocation process (S311).

1, 2, 3, and 5, when a default bearer with the IoT terminal 110 is established during the process of allocating an IP address to the IoT terminal 110, the control unit 153 of the gateway device 150 The set default bearer information is stored in the storage unit 151. For example, identification information about the eNB 120 used for the default bearer tunnel may be stored in the storage 151 (S401).

Subsequently, when a service event for the IoT terminal 110 occurs, the control unit 153 checks the state of a bearer for communication with the IoT terminal 110 (S403).

Here, the control unit 153 checks whether the default bearer, which was preset at the beginning of the service, is maintained by the transceiver 152 or released (S405), and if it is maintained, the IoT terminal 110 through the corresponding default bearer. ) to transmit the signal (S407).

However, if the preset default bearer is released, the control unit 153 checks the default bearer information stored in the storage unit 151 in step S401 (S409).

Then, the control unit 153 of the gateway device 150 processes paging for the IoT terminal 110 according to the default bearer information checked in the storage unit 151 . For example, paging is processed through the IoT terminal 110 by selecting the eNB 120 based on path information included in the default bearer information (S411).

Thereafter, the IoT service for the IoT terminal 110 is provided, which is in the service area provided by the eNB 120 initially registered even if the IoT terminal 110, which does not require mobility, slightly changes location in a home or factory. If it does not deviate, since handover is not required, IoT service can be provided through the eNB 120 used in the IP address allocation process (S413).

As described so far, according to an embodiment of the present invention, the gateway device 150 does not set a dedicated bearer for the IoT service, but processes paging for the IoT terminal using information on a default bearer set at the beginning of the service.

Combinations of each block of the block diagrams and each step of the flowcharts attached hereto may be performed by computer program instructions. Since these computer program instructions may be loaded into a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed by the processor of the computer or other programmable data processing equipment are each block of the block diagram or flowchart. In each step, means to perform the functions described are created. These computer program instructions may also be stored in a computer usable or computer readable memory that can be directed to a computer or other programmable data processing equipment to implement functionality in a particular way, such that the computer usable or computer readable memory It is also possible for the instructions stored in to produce an article of manufacture containing instruction means for performing the function described in each block of the block diagram or each step of the flow chart. The computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operational steps are performed on the computer or other programmable data processing equipment to create a computer-executed process to generate computer or other programmable data processing equipment. It is also possible that the instructions performing the processing equipment provide steps for executing the functions described in each block of the block diagram and each step of the flowchart.

Additionally, each block or each step may represent a module, segment or portion of code that includes one or more executable instructions for executing specified logical function(s). It should also be noted that in some alternative embodiments it is possible for the functions recited in blocks or steps to occur out of order. For example, two blocks or steps shown in succession may in fact be performed substantially concurrently, or the blocks or steps may sometimes be performed in reverse order depending on their function.

The above description is merely an example of the technical idea of the present invention, and various modifications and variations can be made to those skilled in the art without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are not intended to limit the technical idea of the present invention, but to explain, and the scope of the technical idea of the present invention is not limited by these embodiments. The protection scope of the present invention should be construed according to the claims below, and all technical ideas within the scope equivalent thereto should be construed as being included in the scope of the present invention.

According to an embodiment of the present invention, since a network entity of a general network constructed for a general mobile communication service, such as an LTE network, can be changed to a structure suitable for providing an IoT service targeting an IoT terminal, a separate Compared to the case of building a dedicated IoT network using a communication protocol, it provides efficiency in terms of cost.

This present invention can be used when building an IoT communication network for providing IoT services to IoT terminals.

100: IoT service system 110: IoT terminal
120: eNB 130: control entity
140: HSS 150: gateway device
151: storage unit 152: transmission and reception unit
153: control unit

Claims (6)

When a service event for an Internet of Things (IoT) terminal occurs, checking a state of a bearer for communication with the IoT terminal;
If the bearer is in a released state, obtaining information on a default bearer that is previously set for the IoT terminal and then released;
Processing paging for the IoT terminal according to the released default bearer information
The gateway device's paging method.
According to claim 1,
The step of obtaining information of the default bearer,
Inquiring a network entity about information on the default bearer established during the IP (Internet Protocol) address allocation process for the IoT terminal and receiving a response thereof
The gateway device's paging method.
According to claim 1,
Further comprising: storing information of the default bearer after setting the default bearer during an IP (Internet Protocol) address allocation process for the IoT terminal;
The step of obtaining the information of the default bearer that has been previously established,
Checking the stored default bearer information
The gateway device's paging method.
A transmitting and receiving unit for transmitting and receiving signals to and from IoT (Internet of Things) terminals through a wireless access network;
A control unit controlling the transceiver to process paging for the IoT terminal,
The control unit,
When a service event for the IoT terminal occurs, check the state of a bearer for communication with the IoT terminal,
If the bearer is in a released state, it is previously set for the IoT terminal and then released. Acquiring information of a default bearer;
Controlling the transceiver according to the information of the released default bearer to process paging for the IoT terminal
gateway device.
According to claim 4,
The control unit,
Inquiring a network entity for information on the default bearer established during the IP (Internet Protocol) address assignment process for the IoT terminal and receiving a response
gateway device.
According to claim 4,
a storage unit for storing information of the default bearer;
The control unit,
After setting the default bearer during an IP (Internet Protocol) address assignment process for the IoT terminal, the default bearer information is stored in the storage unit;
When the bearer with the IoT terminal is released, checking the default bearer information stored in the storage unit to process the paging
gateway device.

Images