KR20110122643A - Method for controlling network overload in machine type communication in mobile communications system and appatarus thereof - Google Patents

Method for controlling network overload in machine type communication in mobile communications system and appatarus thereof Download PDF

Info

Publication number
KR20110122643A
KR20110122643A KR1020110042291A KR20110042291A KR20110122643A KR 20110122643 A KR20110122643 A KR 20110122643A KR 1020110042291 A KR1020110042291 A KR 1020110042291A KR 20110042291 A KR20110042291 A KR 20110042291A KR 20110122643 A KR20110122643 A KR 20110122643A
Authority
KR
South Korea
Prior art keywords
terminal
mtc
network
information
functions
Prior art date
Application number
KR1020110042291A
Other languages
Korean (ko)
Other versions
KR101782650B1 (en
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 to US33089210P priority Critical
Priority to US61/330,892 priority
Application filed by 엘지전자 주식회사 filed Critical 엘지전자 주식회사
Priority claimed from US13/696,039 external-priority patent/US8942175B2/en
Publication of KR20110122643A publication Critical patent/KR20110122643A/en
Application granted granted Critical
Publication of KR101782650B1 publication Critical patent/KR101782650B1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/04Arrangements for maintaining operational condition
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02Terminal devices

Abstract

The present invention relates to a method for controlling an overload of a network that may occur due to a service request of a terminal in a mobile communication system of machine type communication (MTC).
The present invention controls the network overload by requesting the network to activate a specific MTC function based on the information on the change of the MTC functions without making unnecessary MTC functions (eg, attach request). It is also an efficient use of network resources.

Description

TECHNICAL FOR CONTROLLING NETWORK OVERLOAD IN MACHINE TYPE COMMUNICATION IN MOBILE COMMUNICATIONS SYSTEM AND APPATARUS THEREOF

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a mobile communication system, and in particular, to control an overload (or overload) of a network by MTC data communication in a machine type communication (MTC) service of a mobile communication system.

The 3GPP, which enacts the technical specifications of 3G mobile communication systems, plans to optimize and improve the performance of 3GPP technologies from the end of 2004 in order to respond to various forums and new technologies related to 4G mobile communication. (Long Term Evolution / Evolved Packet Core) technology began research. EPC, centered on 3GPP SA WG2, is a study on network technology aimed at determining the network structure and supporting mobility between heterogeneous networks in parallel with 3GPP TSG RAN LTE work. Is one of. This is a work to develop a 3GPP system to support a variety of radio access technologies based on IP, and has been aimed at an optimized packet-based system that minimizes transmission delay with improved data transmission capability.

Hereinafter, technical terms used in the description of the present invention will be described.

-MTC function is a function to support communication between MTC devices or between MTC device and MTC server, which means that communication is performed without human intervention unlike existing human-to-person connection. For example, MTC applications include vending machines and servers, point-of-service devices and servers, and communications between electricity and water meters and servers. The device is called an MTC device. Here, MTC is also called the name of Machine to Machine or IoT.

A tracking area (TA) indicates an area where an E-UTRAN provides a service and includes one or more E-UTRAN cells.

-A routing area (RA) indicates an area where GERAN / UTRAN provides a service and includes one or more GERAN / UTRAN cells.

The Tracking Area Identity (TAI) list indicates a list of each TA identifier (that is, a tracking area identity (TAI)) that identifies the tracking areas that the terminal may enter without performing a tracking area update procedure ( A list of TAIs that identify the tracking areas that the UE can enter without performing a tracking area updating procedure.The TAIs in a TAI list assigned by an MME to a UE pertain to the same MME area). For a detailed description of the TAI list, use the information outlined in standard document 3GPP TS 24.301 v9.1.0.

Mobility Management Entity Area (MME area): The MME area refers to the area of the network served by the MME. The MME area consists of one or more tracking areas (TA). In addition, all cells served by one base station (i.e., eNodeB) are included in one MME region (The mobility management entity (MME) area is the part of the network served by an MME.An MME area consists of one or Several Tracking Areas.All cells served by an eNodeB are included in an MME Area.) Detailed descriptions of MME areas are incorporated in the standard document 3GPP TS 23.002 v9.2.0.

-UMTS: Universal Mobile Telecommunication System, which means 3G network.

-EPS: Evolved Packet System is a generic name for Evolved Packet Core, LTE, and various access networks and terminals. In addition, EPS is a network in which UMTS is evolved.

-NodeB: It is installed in the outdoors as a base station of UMTS network and the coverage is macro cell size

eNodeB: It is installed outdoors as a base station of the EPS network, and the service coverage is a macro cell size.

UE: means UE, user equipment.

IMSI: International Mobile Subscriber Identity, which is the unique identifier of an internationally assigned user in a mobile network.

SIM card: Subscriber Identity Module that contains user subscriber information such as IMSI.

-UICC: Universal Integrated Circuit Card, used the same as SIM card.

-MTC: Machine Type Communication means communication between devices without human intervention.

-MTC device: A terminal that performs a specific purpose having a communication function through a core network, for example, a vending machine, a meter reader, and the like.

MTC server: A server on a network that manages MTC devices and sends and receives data. It can be outside the core network.

-MTC application: The actual application using the MTC device and the MTC server, for example, remote meter reading, quantity movement tracking.

MTC Feature: Some features are required according to the function or feature of the network to support MTC applications, that is, the purpose of each application. Examples include MTC monitoring (needed for remote meter reading in case of equipment loss) and low mobility (less movement in vending machines).

-RAN: Radio Access Network is a generic term for 3GPP wireless access such as RNC, NodeB, eNodeB.

HLR (Home Location Register) / HSS (Home Subscriber Server): Database (DB) representing subscriber information in 3GPP network.

-RANAP, which stands for Radio Access Network Application Part, means the interface between the RAN and the node (MME / SGSN / MSC) in charge of controlling the core network.

The cell camping (or camping on) state refers to a state in which the terminal selects a cell after completing a cell selection procedure or a cell selection / reselection process. The detailed description thereof uses the contents disclosed in the standard document 3GPP TS 36.304 v9.1.0.

ISR (Idle mode Signaling Reduction) increases efficiency of network resources by reducing signaling for location registration when the UE moves between different access networks such as E-UTRAN network and UTRAN / GERAN. Giving is a service.

IMS Centralized Services (ICS) are stable to IMS regardless of the access network to which the terminal is attached (i.e., attached to the CS domain as well as the IP-CAN) Provide consistent services. For a detailed description of the ICS, use the information set forth in the standard document 3GPP TS 23.292 v9.4.0.

IMS (IP Multimedia Subsystem) refers to a system that provides a multimedia service based on IP.

-Attach (attach) refers to the connection of the terminal with the network node, which means that the attachment that occurs in the handover (handover) in a broad sense.

In the above, this invention is demonstrated with reference to the described technical term.

1 is a conceptual diagram illustrating a 3GPP service model for MTC support.

In GSM / UMTS / EPS of 3GPP standard for MTC support, communication is defined through PS network, but the present invention describes a method applicable to CS network. do. In the current technical specification, the definition of the network structure is proposed to use an existing bearer of 3GPP. Meanwhile, a method of using a short message service (SMS) for data exchange between an MTC device and an MTC server has been proposed as one of alternative solutions. It is proposed to use SMS in consideration of the small amount of digital data such as meter information or product information due to the nature of MTC application, and the SMS method based on the existing SMS method and IMS can be supported. Do. In FIG. 1, MTCsms is a data exchange interface through an existing SMS scheme, and MTCi is a data exchange interface for 3GPP bearer service and IMS.

Hereinafter, overload control in the MTC service will be described.

Examples of cases where an overload occurs in the MTC include: An incorrect function of the MTC server or the MTC application; When an external event occurs that causes a large number of MTC devices to connect; This is the case where a specific program is repeatedly operated at a specific time. In these cases, it is very difficult to implement an MTC application in conjunction with a core network (or core network). This is because core network nodes (SGSN / MME / PGW, etc.) are easily damaged by data that is concentrated and concentrated.

Thus, the method for controlling the overload occurring in conventional core network nodes is as follows:

1) A network node can deny a particular connection. The criterion of restriction to deny the connection is possible according to APN or MTC group. Alternatively, the MTC device may connect to the network node only at a predetermined time. However, if the network node transmits a retry delay time (back off time) to the MTC device to the MTC device in the congested state, the network node sends information to the MTC device so that the MTC device does not connect during the period. Can provide;

2) Before the MTC device uses it at a specific time, there is a method of performing a location update process of the cell to which the MTC device belongs, that is, the TAU / RAU. However, this is intended to register the correct position before use because it is not used for a long time. In this case, since it is off for a long time, it is necessary to update the location information at the time of connection, which is not a solution to the fundamental problem;

3) Randomizes a connection start time at which the MTC device connects to the network node within a specific predetermined time. This is to prevent traffic from gathering at a specific time. This method may trigger on an MTC server or an MTC device.

On the other hand, the situation of the network is changed during the overload occurs in the MTC, MTC devices may be rejected even if the attachment request to the network, the unnecessary network resources may be lost. Hereinafter, an example of network overload caused by the network rejecting the attach procedure of the MTC device and the attach request of the MTC device will be described.

In the mobile communication system supporting the conventional MTC service, the attach procedure of the MTC device is as follows: 1) The MTC device (terminal) registers subscriber information with the MTC server. That is, a user of the MTC device may set and change an activation or deactivation state of each MTC feature through, for example, web based registration. The result of enabling / disabling each MTC feature is stored in the core network; 2) When the terminal attaches to the network (or the core network node), the network checks the subscriber information. That is, at the time when the MTC device attaches to the network, the core network node (for example, the MME) brings the subscriber information by interaction with the subscription registration server (for example, the HSS) and the corresponding terminal (ie, MTC device) determine whether to accept in the network; 3) On the other hand, if the network cannot support an attach request (eg, activation request of a specific MTC function) of the terminal according to the situation of the network such as an operator policy or the like, Decide to reject the attachment.

In the above-described prior art, each MTC function of the MTC device is stored in the core network, and may not activate a specific MTC function according to the situation of the core network, or may support another MTC function according to the capability of the network. It happens that you can't. That is, even though the terminal (MTC device) does not recognize and transmits the attach request to the network at a preset time or event occurrence, the network rejects the request of the terminal, thereby causing a technical problem that unnecessary resources are lost.

This technical problem is because a change in service support of MTC functions occurs at the network end.

Accordingly, the present invention generates and transmits information on changes of MTC functions in a network to the terminal, so that the terminal does not make unnecessary requests for MTC functions (eg, attach requests), and is applied to the changes of the MTC functions. By requesting activation of a specific MTC function to the network based on the information, we propose a method of controlling network overload and efficiently using network resources.

In order to achieve the above object, a network overload control method in a mobile communication system according to the present invention,

Receiving and storing, by the terminal, information related to network overload control from a network node;

Analyzing, by the terminal, the information related to the stored network overload control and determining whether to reject or allow a service request to the network node;

And when the network node determines to allow the service request in the determining step, transmitting, by the terminal, a message requesting the service to the network node.

Preferably, the information related to the network overload control

Characterized in that it includes information indicating the activation state of the machine type communication (MTC) functions associated with the terminal.

Preferably, the information related to the network overload control

An activation list of MTC functions that the network node can support for the terminal;

The network deactivating list of MTC functions for the terminal;

A list of MTC functions that the terminal may activate or should activate or a list of MTC functions that the terminal may deactivate or require;

An incompatibility set among MTC functions for the terminal;

A parameter value of a corresponding MTC function to avoid incompatible setup among MTC functions for the terminal;

Information of a form in which MTC functions and on / off flags are combined among MTC functions for the terminal;

If there is information previously transmitted to the terminal by the network node, updated information of the information; It is characterized by including at least one of.

Preferably, the message requesting the service

Information on MTC functions that the terminal wants to activate;

Information on MTC functions in an activated state currently stored by the terminal;

Information on a capability of a device currently supported by the terminal and / or corresponding MTC functions;

And at least one of information on user preferences for MTC functions of the terminal.

In addition, in order to achieve the above object, a network overload control method in a mobile communication system according to the present invention,

Receiving a message requesting a service from a terminal by a network node;

Receiving, by the network node, information on machine type communication (MTC) functions of the terminal from a subscriber registration server;

In consideration of the information on the MTC functions of the terminal received by the network node, the situation of the network, and an operator policy,

Determining whether to reject or allow the service request of the terminal;

In response to the determination, the network node may include transmitting information related to network overload control to the terminal together with an allowance message or a rejection message for the service request.

Preferably, the network node

In consideration of the received information on the MTC functions of the terminal, the situation of the network, and the operator policy,

The method may further include generating information related to the network overload control.

Preferably, the method may further include updating information related to the network overload control generated by the network node to the subscriber information server.

Preferably, the information related to the network overload control

The information related to the network overload control

An activation list of MTC functions that the network node can support for the terminal;

The network deactivating list of MTC functions for the terminal;

A list of MTC functions that the terminal may activate or should activate or a list of MTC functions that the terminal may deactivate or require;

An incompatibility set among MTC functions for the terminal;

A parameter value of a corresponding MTC function to avoid incompatible setup among MTC functions for the terminal;

Information of a form in which MTC functions and on / off flags are combined among MTC functions for the terminal;

If there is information previously transmitted to the terminal by the network node, updated information of the information; It is characterized by including at least one of.

Preferably, the message requesting the service

Information on MTC functions that the terminal wants to activate;

Information on MTC functions in an activated state currently stored by the terminal;

Information on a capability of a device currently supported by the terminal and / or corresponding MTC functions;

And at least one of information on user preferences for MTC functions of the terminal.

Preferably, the terminal is an MTC device capable of supporting an MTC service,

The network node may be a mobility management entity (MME), a serving GPRS support node (SGSN), or a mobile telephone switching (MSC).

In addition, in order to achieve the above object, the mobile communication terminal according to the present invention,

Make a service request to a network node,

A transceiver for receiving status information of MTC functions from the network node, cause information on rejection of the service request, and information on currently active MTC functions of a network;

A storage unit which stores state information of MTC functions received from the network node, cause information on rejection of the service request, and information on currently active MTC functions of the network;

And a controller for controlling a network overload by determining whether to make a service request to the network so that a network overload does not occur in consideration of the received information.

According to the present invention, in a mobile communication system supporting an MTC service, the terminal requests an unnecessary MTC function from the network based on change information (or active / deactivated list of MTC functions) of MTC functions generated in the network. By preventing the overload of the network, it is also possible to improve the quality of MTC service and the efficiency of network resource utilization.

In addition, the present invention is based on the activation (activation) of the MTC functions registered when the terminal (that is, the MTC device) and the network status (that is, the status of the home network and the visited network), operator policy, etc. By not allowing the terminal to make unnecessary service requests, it is possible to effectively manage the overload of the network in the MTC environment.

In addition, the present invention prevents waste of wired / wireless network resources in an MTC environment of a 3GPP GSM / UMTS / EPS system. In particular, in an MTC environment in which many MTC devices attempt to communicate at the same time as compared to the existing communication, waste of resources due to unnecessary service requests of the terminal can be eliminated.

In addition, the present invention can improve the quality of service that a user feels by flexibly activating MTC functions in the MTC device.

1 is a conceptual diagram illustrating a 3GPP service model for MTC support.
2 is a signal flowchart illustrating a method for controlling network overload in an MTC service of a mobile communication system according to a first embodiment of the present invention.
3 is a signal flow diagram illustrating a method for controlling network overload in an MTC service of a mobile communication system according to a second embodiment of the present invention.
4 is a schematic diagram of a terminal and a network node according to an embodiment of the present invention.

The present invention is applied to a mobile communication system using machine type communication (MTC). However, the present invention is not limited thereto, and may be applied to next generation mobile communication and other wired / wireless communication to which the technical spirit of the present invention can be applied.

As the inventive concept allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail in the written description. However, this is not intended to limit the present invention to specific embodiments, it should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention.

Terms including ordinal numbers such as first and second may be used to describe various components, but the components are not limited by the terms. The terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component. The term and / or includes any item of a plurality of related listed items or a plurality of related listed yields.

When an element is referred to as being "connected" or "connected" to another element, it may be directly connected or connected to the other element, but other elements may be present in between. On the other hand, when a component is said to be "directly connected" or "directly connected" to another component, it should be understood that there is no other component in between.

The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting of the invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, the terms "comprise" or "have" are intended to indicate that there is a feature, number, step, operation, component, part, or combination thereof described on the specification, and one or more other features. It is to be understood that the present disclosure does not exclude the possibility of the presence or the addition of numbers, steps, operations, components, components, or a combination thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art. Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art and shall not be construed in ideal or excessively formal meanings unless expressly defined in this application. Do not.

The terminal according to the present invention refers to all devices capable of performing the technical features of the present invention. That is, a mobile communication terminal (for example, a pacemaker, a vending machine, a power meter, an air pollution meter, etc.) capable of performing an MTC service function according to the present invention is a user equipment (UE), and other human-oriented devices. (E.g. mermaids, cell phones, cell phones, DMB phones, game phones, camera phones, smartphones, etc.), and other notebooks, desktop computers, laptop computers, palmtop computers, PDAs (personal digital assistant), white goods, etc., is a comprehensive meaning.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Reference will now be made in detail to the preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to the like elements throughout. The description will be omitted.

In a 3GPP mobile communication system supporting the MTC function, data communication involving an MTC device that does not involve human operation is operated in a preset state. When such data communication is driven at a specific time, data communication (or Congestion may occur due to traffic congestion, and other forms of communication (eg, human-human) may be interrupted.

That is, the present invention focuses on the problem of falling into a congestion / overload state of data communication in a mobile communication system supporting the MTC service. The present invention proposes the function and operation of the network according to the present invention, which can solve the congestion occurring in connection with MTC data communication. Thus, the present invention provides a method for preventing congestion of data communication in advance; On the other hand, when a congestion state of data communication occurs, by appropriately distributing data communication, it is possible to efficiently use radio resources or resources of the core network.

The present invention is conceived to efficiently use network resources by preventing network overload that may occur because a terminal (ie, MTC device) does not know the network situation in relation to the MTC service.

The basic concept of the present invention is to: 1) register each function of the MTC device with the MTC server; 2) when a change in the registered MTC functions of the MTC device occurs, the core network sends information (or list) updated with the change in the MTC functions to the terminal; 3) On the basis of the received information, the terminal transmits a request for the MTC function to the network, so that the terminal does not send an MTC service request that cannot be supported by the network.

Hereinafter, examples of specific situations to which embodiments of the present invention will be applied will be described. An embodiment of the present invention is: 1) when the terminal roams; 2) the network operator changes the network settings for the MTC function; 3) the network's capability has changed and it is difficult to support certain MTC functions; 4) An incompatible set occurs when the network cannot support MTC functions. Hereinafter, each situation to which the embodiment of the present invention is applied will be described.

1) When the terminal roams, the terminal does not know the network situation

When a terminal roams from a home network to a visited network, it may be impossible to know what MTC features are currently supported in the network. That is, for example, in a network of an MTC environment that mainly provides electronic health care (e-health care) services, a user or terminal using the electronic health care (e-health care) service may use various MTCs. Assume that you are using the following features: "Small data transmission"; "Frequent data transmission"; "Infrequent mobile terminated"; "Priority alarm" and so on.

Assume that the terminal has moved from the home network to the visited network. By the way, it is assumed that the mobile visited network is not a network of MTC environments optimized for electronic health care services, but is currently capable of providing "small data transmission" and other MTC functions such as: "Low Mobility"; "Time Control"; "Time Tolerant"; "Group Based Charging"; "PS Only"; MTC features such as "Small Data Transmission".

In this case, if the terminal (or MTC user) can know the situation of the MTC functions supported by the visited network, e-health care limited to only "small data transmission" currently supported by the visited network. If you want to continue using the service (for example, you can't use emergency alarms, but you can currently send your body measurements and receive appropriate feedback), or you can't receive full electronic health care services. Or the like, and make an appropriate service request to the network. Meanwhile, the determination of the terminal (or MTC user) may be determined directly through a user interface or may be determined by using a pre-configured value.

If the terminal can know the support status of the MTC functions of the visited network that is camping on, for example, the terminal uses a priority alarm feature that is not supported by the visited network. By not sending a request to the network, waste of network resources can be avoided.

2 ) Network operators MTC  When the network setting for the function is changed, the terminal does not know such a network situation

It is assumed that the network currently being served by the terminal provides the following MTC functions: "Small Data Transmission"; "Frequent data transmission"; "Infrequent mobile terminated"; MTC functions such as "Priority alarm".

As part of the network overload and network management policy, an operator wants to temporarily disable (deactivated) some MTC functions at a certain point in time. For example, if you disable MTC functions such as "Frequent data transmission" or "small data transmission" due to network overload at a certain point in time, in this network situation, the network may use MTC such as "frequent data transmission service" for MTC service. When the function is requested from the terminal, the request is rejected.

That is, when the terminal first connects to the network, the terminal knows and operates only the contents of the MTC function that is said to be supported by the network, and thus the network at a specific time (or when an event occurs) occurs when the MTC function of "frequent data transmission" occurs. Send a service request to. However, since the MTC function of the "frequent data transmission" is disabled in the network, the service request is rejected. In this case, as a result, the terminal wastes network resources by requesting MTC service for the deactivated MTC function (that is, "frequent data transmission").

3 A) the ability of the network has changed MTC  When the network cannot support the function, the terminal does not know such a network situation

Currently, it is assumed that the terminal is provided with a "Small data transmission feature" among MTC functions from the network. In this case, the network provides a "small data transmission" using an SMS scheme, and the current network is disconnected from an SMS server providing an MTC service or a resource for providing an SMS service. There is a situation that it is difficult to support the MTC function of the "small data transmission" due to lack of (resource). At this time, when the terminal first accesses the network, the terminal does not know the changed situation of the current network capability (that is, the network does not support the MTC function of "small data transmission"), and the terminal "small data transmission" to the network. If the service request (service request) to the network for the terminal will be rejected (reject) for the request from the network. Therefore, this situation results in waste of resources between the terminal and the network.

4 ) Network MTC  Incompatible settings among the functions ( incompatible set In the case where) occurs, the terminal does not know such a network situation

It is assumed that the terminal has registered the following MTC functions in the network, and that the MTC functions are currently all supported by the network: that is, "Low Mobility"; "Time Control"; "Time Tolerant"; "Group Based Charging"; "PS Only"; "Small Data Transmission"; "Frequent data transmission"; "Infrequent mobile terminated"; MTC functions such as "Priority alarm".

In this case, an incompatible set may occur that is difficult to use together among the MTC functions from a network point of view. That is, for example, while the MTC function of "time control", which has a characteristic of transmitting data only for a predetermined time period, is set to transmit data only for one or two minutes of the day in a corresponding network, The MTC function of "frequent data transmission" that can transmit data frequently assumes that data transmission is enabled every hour. Under these assumptions, the two MTC functions, "time control" and "frequent data transmission", are currently available on the network but can be referred to as incompatible set MTC features that cannot use both MTC functions at the same time. Can be. Such incompatible MTC functions may be affected by the terminal support capability, network support capability, subscriber information, or MTC service to be served. In addition, when the service requests to the network in a situation where the terminal does not know such an incompatible MTC function, the network will reject the service request based on preset information or an operator policy. Rejection of the request of the service by such a network eventually leads to waste of network resources. In other words, if the terminal is aware of the incompatible MTC function of the current network, the terminal is less likely to send unnecessary service requests to the network, such as service requests that are likely to be rejected.

As described above, as in the case of 1) to 4) above, if the terminal does not know the network condition correctly, the service request of the terminal must be rejected or is likely to be rejected. A service request can be attempted to the network. This, in turn, increases the load on the network associated with the MTC server and wastes network resources.

Accordingly, the present invention proposes a method of preventing waste of network resources by receiving a changed information of an MTC function according to a change in the situation of a network and not requesting a certain service to be rejected based on the changed information.

In an embodiment of the present invention, the terminal and / or the network (eg, the core network node) updates and generates changes of the MTC functions. In addition, the present invention is based on the activation (activation) of the MTC functions registered when the terminal (that is, the MTC device) and the network status (that is, the status of the home network and the visited network), operator policy, etc. In other words, the terminal does not make unnecessary service requests. As a result, the present invention can effectively manage the overload of the network in the MTC environment.

According to an embodiment of the present invention, the subject may be divided into an operation of a terminal and an operation of a network node: first, operations performed to prevent an unnecessary service request of the terminal from the terminal's point of view; Secondly, these operations are performed by the network node in order to prevent unnecessary service requests from the terminal.

First, operations performed by the UE in order to prevent unnecessary service requests to the network are as follows:

(1) The terminal checks the activated / deactivated state of each of the current MTC functions. In this case, the basis for confirming the active / inactive state set in each of the MTC functions may be various. For example, ① a terminal stores a terminal (13 in FIG. 4) as a result of a reject or accept (ie, information included in S10 of FIG. 2) obtained by making a service request to a previous network node. In the MTC functions, the active / inactive state of the MTC functions; Alternatively, when the terminal receives the allow message or the reject message from the network node for the service request of each MTC feature, it may be inferred by receiving a direct cause or other information directly or indirectly from the network node. . That is, you may explicitly receive an activation list of MTC functions, or you may receive an inactivation list of MTC functions; Or ③ For example, the terminal may receive information on the stored MTC functions using a method such as OMA DM / DT from a server storing information on MTC functions set for each MTC device. have.

On the other hand, the activated MTC function is set, for example, when the terminal registers and subscribes to an MTC server, and refers to an MTC function activated when a specific time or event occurs. That is, the activation state of a specific MTC function refers to a state that is willing to receive a service or a state that can provide a service. On the other hand, even if the terminal is subscribed to the MTC system (or specifically MTC server, for example), if the specific MTC function is inactive by the operator policy of the network or because of the state of the other network, the terminal Currently cannot be serviced for the disabled MTC function.

(2) The terminal determines whether to send a service request for a specific MTC function to the network node.

More specifically, the terminal (for example, a control unit (or processing unit) that is one component of the terminal) determines (determines whether the capability related to the MTC function is supported by the terminal based on the above-described information). Determine whether the corresponding MTC function is activated according to the current subscription information. As such, based on confirming the activation of the MTC function according to the capability determination and the current subscription information, since the terminal determines whether to send a service request to the network node, it may not make a certain service request that will be rejected from the terminal's point of view. have.

(3) Meanwhile, when the terminal sends a service request to the network node, the terminal may include at least one or more of the following information on the MTC functions of the terminal and transmit the same to the network node:

MTC functions that the terminal wants to activate;

MTC functions in an activated state currently stored in the storage of the terminal;

The capability of the device currently supported by the terminal and / or corresponding MTC functions;

Preset or dynamically selected user preferences (e.g. preference information such as wanting to preferentially select a particular MTC function).

(4) The terminal sends a service request for a specific MTC function to the network node, and after receiving an allow message or reject message from the network for the request, store the related message. As such, the stored information may be used when the terminal determines whether to make a service request to the network node.

Second, operations performed to prevent an unnecessary service request of a terminal from the network's point of view are as follows:

(1) The network node receives a service request from a terminal (ie, an MTC device).

(2) When receiving a service request from the terminal, the network node determines whether to activate each MTC function in consideration of network conditions. In this case, the information that the network node considers when determining the activation of the MTC functions is as follows: information that the terminal includes in the service request to the network as described above; Information capable of knowing network status; Subscriber information; The decision is made based on a provider policy (for example, pre-configuration information, or information on a provider policy by request / response method if necessary such as PCRF interaction).

(3) The network node informs the terminal of the result indicating the activation status of the MTC functions (for example, a list of the activation status of the MTC functions): That is, the network node sends the result to the allow message or the reject message. Or include; Alternatively, for example, the network node may send the result to the terminal using a method such as an OMA DM / DT from a server storing information on MTC functions set for each MTC device.

On the other hand, the form of the result indicating the activation status (activation status) of the MTC functions that the network node sends to the terminal may be implemented in various ways:

Ie a " list of MTC Activated feature "

Or "a list of MTC deactivated features" of the network;

A list of MTC functions that the terminal can activate (or have to) and / or a list of MTC functions that the terminal can deactivate (or have to);

-Parameter values of the corresponding MTC function that can avoid incompatibility sets and / or incompatible settings;

Information in the form of "each MTC function + on / off flag"; or

If there was previously information, it is updated information.

As described above, in order to reduce the network overload and increase the efficiency of network resources, the present invention, the terminal and the network node performs the corresponding operations, respectively. That is, the UE does not send only a service request to the network node unconditionally, but rather a service request to the network in consideration of the capability of the terminal itself and the situation of the currently activated MTC functions transmitted by the network node. Because it does not, the service request is likely to be rejected in the network. Therefore, in terms of network resources, since the terminal does not make a service request having a high probability of being rejected in the network based on the above information, the efficiency of network resources can be improved and network overload can be prevented.

Hereinafter, an embodiment of the present invention will be described in more detail with reference to FIGS. 2 and 4.

2 is a signal flowchart illustrating a method for controlling network overload in an MTC service of a mobile communication system according to a first embodiment of the present invention.

3 is a signal flow diagram illustrating a method for controlling network overload in an MTC service of a mobile communication system according to a second embodiment of the present invention.

4 is a schematic diagram of a terminal and a network node according to an embodiment of the present invention.

2 and 3 illustrate a procedure in which a terminal makes a attach request to a network node.

2 and 3 are merely examples showing a method of controlling network overload using an attach procedure, and further, using a message of a location registration procedure such as TAU / RAU. The network overload according to the present invention may be controlled, and the terminal may apply the method for controlling network overload of the present invention to another service request procedure after attaching to the network. . In addition, in the network overload control method according to the present invention, a specific service request procedure such as SMS may be used. In this case, an MTC related parameter may be added.

The difference between the embodiment of FIG. 2 and the embodiment of FIG. 3 is that the embodiment of FIG. 2 determines whether the terminal sends the attach request message to the network, and includes a list of activated MTC functions in the attach request message. . However, the embodiment of FIG. 3 will be described in detail below in comparison with the embodiment of FIG. 2.

Hereinafter, the signaling related to the present invention will be described with reference to FIG. 4.

1. The terminal (UE, MTC device) 10, more specifically, the control unit 13 of the terminal determines whether to send an attach request (attach request) to the network node (MME) (30). At this time, the control unit 12 of the terminal 10 determines whether to send a attach request in consideration of the information stored in the storage unit (13). When the control unit 12 determines whether to send the attach request, information read from the storage unit 130 considers as follows: That is, the result of the attach requests previously sent to the network by the terminal 10. And subscription information and the capability of the terminal 10 to support the MTC function.

When the control unit 12 of the terminal 10 determines the attach request, it transmits the attach request message to the network node 30 via the base station (eNodeB) 20 through the transceiver unit 11 (S1 and S2).

The control unit 12 of the terminal 10 may include information for controlling network overload in the attach request message, for example, information of activated MTC functions known to the terminal itself, and the MTC functions to be activated. Information, such as device capability to provide other MTC functions, and so forth.

MTC functions for which the terminal 10 wishes to request activation;

-MTC functions in the activated state currently stored in the storage unit 13 of the terminal 10;

Device capabilities currently supported by the terminal 10 and / or corresponding MTC functions;

A preset or dynamically selected user preference (or terminal preference, user / UE preference) (eg preference information that the terminal wants to preferentially select a particular MTC function); At least one of may be included in the attachment message.

2. The subscription information is brought to the network node 30 through an interaction between the HSS 70 and the network node (MME) 30 (that is, the MME is a kind of network control node) (S3 or S4). In this case, the operation may be an authentication process S3 or a location update process S4 in FIG. 2. However, for convenience of description of the present invention, the subscription information is obtained by the network node 30 from the HSS 70 through the S4 process.

The subscription information of the S4 process may include information of an MTC service subscribed to by the terminal, information of an MTC function, information of an currently activated MTC function, information of an MTC function that is deactivated, or the like. have.

On the other hand, the control unit 32 of the network node 30: ① information on the network overload control received from the terminal through the process S1 and S2 (for example, the MTC functions activated in the terminal, the terminal is activated Preferred MTC functions); ② the subscriber information obtained through the S4 process; In addition, network information collected by the network node 30 (for example, information received from a third network node (not shown)); ④ Consider the operator policy received from the pre-configuration or PCRF to determine the MTC functions to be finally activated (or MTC functions to be deactivated), and to deactivate (or deactivate) the MTC functions to be activated. MTC functions).

If the network node 30 accepts (accepts) the attachment requested by the terminal 10, the network node 30 sends an attach accept message to the terminal 10 through the base station 20. (S10 and S11). At this time, the network node 30, in order to prevent the terminal from overloading the network due to unnecessary service request in the future, the MTC functions to be activated (or deactivated) determined and generated by the control unit 31 of the network node 30 The transceiver 31 of the network node 30 may send a list of MTC functions) to the MTC terminal 10. In addition, the network node 30 includes information indicating the status of the current MTC features (MTC features' status), " cause " information indicating the reason for granting or rejecting the reason for the service request of the terminal 10; In addition, the network node 30 may send information to the terminal 10 including information indicating a possible MTC activated set. This information that the network node 30 sends to the terminal 10 is used later when the terminal 10 determines whether to make a service request to the network node 30. That is, the control unit 12 of the terminal 10 determines the service request to the network node 30 based on the information received through the steps S10 and S11, so that the terminal 10 sends the service request to the network node 30. In this case, it is possible to deny unnecessary operations from the standpoint of the terminal 10, and the network node 30 from preventing the overload of the network.

3. Meanwhile, the network node 30 may also send a rejection message to the attachment request of the terminal 10. In more detail, as follows. That is, during the procedure of performing the service request (eg, the attach request) of the terminal 10, the network node 30 determines reject at any particular stage in consideration of the network situation and subscriber information. If so, a reject message may be sent to the terminal 10 instead of the attachment message to the terminal 10. In this case, the network node 30 may send information indicating the state of the currently activated MTC function together with a specific "cause" (ie, information indicating a reason for rejection). In addition, when the network node 30 sends a rejection message due to a situation in which it is difficult to provide a specific incompatible MTC function, the network node 30 provides the terminal 10 with more detailed information such as a list of incompatible MTC functions, thereby providing a terminal ( 10) Do not unnecessarily repeat service requests that are guaranteed to be rejected. Therefore, the terminal 10 may send a service request to the network node 30 in which an incompatible MTC feature set does not occur in a future service request.

On the other hand, the form of the result indicating the activation status (activation status) of the MTC functions that the network node 30 sends to the terminal 10 with the permission message or rejection message, can be implemented in various ways as described above:

Ie a " list of MTC Activated feature "

Or "a list of MTC deactivated features" of the network;

A list of MTC functions that the terminal can activate (or have to) and / or a list of MTC functions that the terminal can deactivate (or have to);

-Parameter values of the corresponding MTC function that can avoid incompatibility sets and / or incompatible settings;

Information in the form of "each MTC function + on / off flag"; or

If there was previously information, it is updated information.

On the other hand, the information sent by the network node 30 to the terminal may be transmitted to the terminal 10 through another path (for example, OMA DM / DT) without a permit message or a reject message. For example, the network node 30 updates the activation status of the MTC function on the HSS 70 or the server (for example, the MTC server) storing the subscriber information (S19), and then a specific time point. Alternatively, the terminal 10 may provide information related to the MTC function (ie, information for controlling network overload) to the terminal 10 through another path such as OMA DM / DT after the set event occurs.

Compared to the embodiment of FIG. 2, in the second embodiment of FIG. 3, the terminal 10 transmits information for network overload control (eg, activated MTC functions through an attachment message). MTC features), the terminal does not include the preferred MTC features (preferred MTC features) (S31 and S32).

Accordingly, in the second embodiment of FIG. 3, the terminal 10 controls information for controlling network overload transmitted by the network node 30 (eg, “cause”, MTC features' status, or possible MTC activated). set, etc.) (S40 and S41), it is possible to determine whether to make a service request to the network node 30 in consideration of the received information. Since the operation and function of each signaling of the second embodiment of FIG. 3 are the same as the corresponding operation of the first embodiment of FIG. 2, a detailed description of the second embodiment of FIG. 3 will be described with reference to the first embodiment of FIG. 2. Use it.

On the other hand, the method according to the invention described so far may be implemented in software, hardware, or a combination thereof. For example, the method according to the present invention may be stored in a storage medium (eg, mobile terminal internal memory, flash memory, hard disk, etc.) and may be stored in a processor (eg, mobile terminal internal microprocessor). It may be implemented as codes or instructions in a software program that can be executed by.

In the above, the present invention has been described with reference to the embodiments shown in the drawings, but this is merely exemplary, and those skilled in the art may realize various modifications and other equivalent embodiments therefrom. I will understand. Therefore, the true technical protection scope of the present invention will be defined by the technical spirit of the appended claims.

Claims (11)

  1. Receiving and storing, by the terminal, information related to network overload control from a network node;
    Analyzing, by the terminal, the information related to the stored network overload control and determining whether to reject or allow a service request to the network node;
    When the network node determines that the network node permits a service request, transmitting, by the terminal, a message requesting a service to the network node; network overload control in a mobile communication system Way.
  2. The method of claim 1, wherein the information related to the network overload control is
    Network overload control method in a mobile communication system, characterized in that it comprises information indicating the activation state of the machine type communication (MTC) functions associated with the terminal.
  3. The method of claim 2, wherein the information related to the network overload control is
    An activation list of MTC functions that the network node can support for the terminal;
    The network deactivating list of MTC functions for the terminal;
    A list of MTC functions that the terminal may activate or should activate or a list of MTC functions that the terminal may deactivate or require;
    An incompatibility set among MTC functions for the terminal;
    A parameter value of a corresponding MTC function to avoid incompatible setup among MTC functions for the terminal;
    Information of a form in which MTC functions and on / off flags are combined among MTC functions for the terminal;
    If there is information previously transmitted to the terminal by the network node, updated information of the information; medium
    Network overload control method in a mobile communication system comprising at least one.
  4. The method of claim 1, wherein the message requesting the service is
    Information on MTC functions that the terminal wants to activate;
    Information on MTC functions in an activated state currently stored by the terminal;
    Information on a capability of a device currently supported by the terminal and / or corresponding MTC functions;
    Of the information on the user preferences for the MTC functions of the terminal
    Network overload control method in a mobile communication system comprising at least one.
  5. Receiving a message requesting a service from a terminal by a network node;
    Receiving, by the network node, information on machine type communication (MTC) functions of the terminal from a subscriber registration server;
    In consideration of the information on the MTC functions of the terminal received by the network node, the situation of the network, and an operator policy,
    Determining whether to reject or allow the service request of the terminal;
    In response to the determination, the network node transmits information related to network overload control to the terminal along with an allowance message or a rejection message for the service request. Load control method.
  6. 6. The method of claim 5, wherein the network node is
    In consideration of the received information on the MTC functions of the terminal, the situation of the network, and the operator policy,
    And generating information related to the network overload control.
  7. The method of claim 6,
    And updating the information related to the network overload control generated by the network node in the subscriber information server.
  8. The method of claim 5, wherein the information related to the network overload control
    The information related to the network overload control
    An activation list of MTC functions that the network node can support for the terminal;
    The network deactivating list of MTC functions for the terminal;
    A list of MTC functions that the terminal may activate or should activate or a list of MTC functions that the terminal may deactivate or require;
    An incompatibility set among MTC functions for the terminal;
    A parameter value of a corresponding MTC function to avoid incompatible setup among MTC functions for the terminal;
    Information of a form in which MTC functions and on / off flags are combined among MTC functions for the terminal;
    If there is information previously transmitted to the terminal by the network node, updated information of the information; medium
    Network overload control method in a mobile communication system comprising at least one.
  9. The method of claim 5, wherein the message requesting the service
    Information on MTC functions that the terminal wants to activate;
    Information on MTC functions in an activated state currently stored by the terminal;
    Information on a capability of a device currently supported by the terminal and / or corresponding MTC functions;
    Of the information on the user preferences for the MTC functions of the terminal
    Network overload control method in a mobile communication system comprising at least one.
  10. The method of claim 5, wherein the terminal
    MTC device that can support MTC service,
    The network node may be a mobility management entity (MME), a serving GPRS support node (SGSN), or a mobile telephone switching (MSC).
  11. Make a service request to a network node,
    A transceiver for receiving from the network node status information of MTC functions, cause information for rejection of the service request, and information on currently active MTC functions of the network;
    A storage unit which stores state information of MTC functions received from the network node, cause information on rejection of the service request, and information on currently active MTC functions of the network;
    And a controller configured to control a network overload by determining whether to make a service request to the network so that a network overload does not occur in consideration of the received information.
KR1020110042291A 2010-05-04 2011-05-04 Method for controlling network overload in machine type communication in mobile communications system and appatarus thereof KR101782650B1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US33089210P true 2010-05-04 2010-05-04
US61/330,892 2010-05-04

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US13/696,039 US8942175B2 (en) 2010-05-04 2011-05-04 Method for controlling MTC service network overload in mobile communication system and device thereof
PCT/KR2011/003349 WO2011139098A2 (en) 2010-05-04 2011-05-04 Method for controlling mtc service network overload in mobile communication system and device thereof

Publications (2)

Publication Number Publication Date
KR20110122643A true KR20110122643A (en) 2011-11-10
KR101782650B1 KR101782650B1 (en) 2017-09-27

Family

ID=45393155

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020110042291A KR101782650B1 (en) 2010-05-04 2011-05-04 Method for controlling network overload in machine type communication in mobile communications system and appatarus thereof

Country Status (1)

Country Link
KR (1) KR101782650B1 (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013070051A1 (en) * 2011-11-13 2013-05-16 엘지전자 주식회사 Method and device for triggering machine-type communication mtc in wireless communication system
WO2013081412A1 (en) * 2011-11-30 2013-06-06 엘지전자 주식회사 Method and device for supporting mtc trigger of serving node in wireless communication system
WO2013165168A1 (en) * 2012-05-02 2013-11-07 주식회사 케이티 Method and device for monitoring user equipment in mobile communication network
KR20130123291A (en) * 2012-05-02 2013-11-12 주식회사 케이티 User equipment monitoring method and apparatus in mobile network
WO2014054876A1 (en) * 2012-10-01 2014-04-10 엘지전자 주식회사 Method and device for device trigger/small data exchange/collection in wireless communication system
KR101580058B1 (en) * 2014-10-13 2015-12-24 한국과학기술원 Method and systema for reducing network load in internet of things

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20090045039A (en) 2007-10-30 2009-05-07 엘지전자 주식회사 Method of reselecting a cell based on priorities

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013070051A1 (en) * 2011-11-13 2013-05-16 엘지전자 주식회사 Method and device for triggering machine-type communication mtc in wireless communication system
US9392396B2 (en) 2011-11-13 2016-07-12 Lg Electronics Inc. Method and device for triggering machine-type communication MTC in wireless communication system
WO2013081412A1 (en) * 2011-11-30 2013-06-06 엘지전자 주식회사 Method and device for supporting mtc trigger of serving node in wireless communication system
US9775021B2 (en) 2011-11-30 2017-09-26 Lg Electronics Inc. Method and device for supporting MTC trigger of serving node in wireless communication system
KR20130123291A (en) * 2012-05-02 2013-11-12 주식회사 케이티 User equipment monitoring method and apparatus in mobile network
WO2013165168A1 (en) * 2012-05-02 2013-11-07 주식회사 케이티 Method and device for monitoring user equipment in mobile communication network
WO2014054876A1 (en) * 2012-10-01 2014-04-10 엘지전자 주식회사 Method and device for device trigger/small data exchange/collection in wireless communication system
US9554234B2 (en) 2012-10-01 2017-01-24 Lg Electronics Inc. Method and device for device trigger/small data exchange/collection in wireless communication system
KR101580058B1 (en) * 2014-10-13 2015-12-24 한국과학기술원 Method and systema for reducing network load in internet of things

Also Published As

Publication number Publication date
KR101782650B1 (en) 2017-09-27

Similar Documents

Publication Publication Date Title
CN105103621B (en) Method and apparatus for applicating category to be arranged on a user device during network congestion
US20130044596A1 (en) Method and System for Controlling Access of Machine Type Communications Devices
CA2765572C (en) Server for control plane at mobile communication network and method for controlling local ip access service
US9743447B2 (en) Control method and device based on multiple priorities in wireless communication system
CN102448112B (en) Process the method based on the congestion control of APN and communication device thereof
US9264975B2 (en) Post access policing in a mobile communication network
US9300480B2 (en) Method for monitoring machine type communication device in mobile communication system
US9078119B2 (en) Method and system for acquiring information of machine type communication user equipment
TWI455621B (en) Service networks and methods for handling machine type communicaion (mtc) device triggering
KR101973462B1 (en) Method for performing detach procedure and terminal thereof
JP2013509737A (en) Communication system and apparatus for status-dependent mobile services
CN102223729B (en) Control machine type communication device and access the method and system of network
JP5308459B2 (en) Telecommunications network and time-based network access method
WO2014097517A1 (en) Radio communication system, radio access network node, communication device, and core network node
US20150296440A1 (en) Hierarchical Access Network Discovery and Selection Function and Offload Wi-Fi Network
KR101824987B1 (en) Method for efficiently transmitting downlink small data of machine type communication in mobile communications system
EP2472790A1 (en) Method, mobile management unit and gateway for restricting mtc device to access and communicate
KR20130090831A (en) Method and apparatus for operating dormant mode of device
US8626206B2 (en) Paging mechanisms for mobile stations with multiple subscriptions
EP2830367A1 (en) Terminal power-saving method and terminal power-saving device, and network-side power-saving device
CN105554789A (en) Communication system, method, and apparatus
WO2009094916A1 (en) A control method, system, and device for circuit domain fallback
JP2017529020A (en) Service capability server / EPC coordination for power saving mode and paging
EP2693776B1 (en) System and method for controlling advanced triggering operations in a telecommunication network
KR101144463B1 (en) Method for performing offline indication of machine type communication device in mobile communications system

Legal Events

Date Code Title Description
E902 Notification of reason for refusal
E701 Decision to grant or registration of patent right
GRNT Written decision to grant