WO2011029395A1

WO2011029395A1 - Terminal control method and apparatus

Info

Publication number: WO2011029395A1
Application number: PCT/CN2010/076745
Authority: WO
Inventors: 郭小龙; 周进怡
Original assignee: 华为技术有限公司
Priority date: 2009-09-09
Filing date: 2010-09-09
Publication date: 2011-03-17
Also published as: CN102026156B; CN102026156A

Abstract

A terminal control method and apparatus are provided in the embodiments of the present invention, and the method includes that: Machine Type Communications (MTC) feature information of a terminal is saved, the MTC feature information contains at least one MTC attribute and a parameter value corresponding to the attribute, and the MTC feature information is used to control the terminal; and the MTC feature information of the terminal is transferred to a network node. The method and apparatus in the embodiments of the present invention provide a transfer method for MTC feature information and a terminal control method under the scenario of Machine to Machine (M2M) communications. The use of the method, through the transfer of MTC feature information of a terminal between network elements, enables the terminal and a network side to implement synchronization of the MTC feature information, and enables the network side to implement effective management to the terminal according to the MTC feature information and save network resources.

Description

The present invention claims the priority of the Chinese application filed on September 09, 2009, the application number is 200910171174. 3, the invention name is "a terminal control method and device", all of which The content is incorporated herein by reference. Technical field

The present invention relates to the field of communications technologies, and in particular, to a terminal control method and apparatus.

BACKGROUND In a mobile communication network based on H2H (Human to Human), a network assumes a managed terminal device, such as a user equipment (User Equipment, UE) and a mobile terminal (Mob i Station, MS). Both are user-oriented (ie: users who use these UEs or MSs are human). From the perspective of network management, these terminal devices have many similarities. For example: UE/MS has mobility, such as: a person carrying a UE/MS to move, a UE or an MS may attach to the network at any time, for example: the user can boot at any time, and the UE or the MS can send or receive a large number of consecutive Data such as: voice stream, user talking via UE or MS, and so on.

However, in a mobile communication network based on M (Machine to Machine), the terminal devices managed by the network are not necessarily human-oriented, but may be various types of equipment, such as: vending machines, Water meter or electricity meter, home gateway, etc. Compared with UE/MS in traditional mobile communication networks, these machines are very different, for example: For vending machines, there is usually no large amount of continuous voice data; for water meters or meters, it may only be at a specific time, Or send data in response to a network query; for a home gateway, there is usually no movement.

In the M2M field, "MTC" (Machine Type Communicat ions) is machine-oriented communication; "MTC terminal" is a UE capable of MTC communication; "MTC server" is a network entity capable of providing MTC service.

Since the MTC terminal is different from the user-oriented UE or MS, it may cause a network. The huge difference in management. Not conducive to the optimization of network resources. SUMMARY OF THE INVENTION In one aspect, an embodiment of the present invention provides a method for controlling a terminal, where the method includes: acquiring machine type communication MTC feature information of a terminal, where the MTC feature information includes at least one MTC attribute and a parameter corresponding to the attribute. And the MTC feature information is used to control the terminal; and the terminal is controlled according to the MTC feature information.

In an aspect, the embodiment of the present invention further provides a core network node, where the core network node includes: a storage unit, configured to store MTC feature information of the terminal, where the MTC feature information includes at least one MTC attribute and corresponding to the attribute a parameter value, the MTC feature information is used to control the terminal; and a sending unit, configured to transmit, to the network node, MTC feature information of the terminal, so that the network node is configured according to the MTC feature information. The terminal controls.

In an aspect, the embodiment of the present invention further provides a terminal, where the terminal includes: a storage unit, configured to store MTC feature information of the terminal, where the MTC feature information includes at least one MTC attribute and a parameter corresponding to the attribute The MTC feature information is used to control the terminal; the sending unit is configured to send the stored MTC feature information to a core network node and/or an access network node, so that the core network node and And/or the access network node controls the terminal according to the MTC feature information.

In an aspect, the embodiment of the present invention further provides an access network node, where the access network node includes: an acquiring unit, configured to acquire MTC feature information of the terminal from a core network node or a terminal or another access network node, where The MTC feature information includes: at least one MTC attribute and a parameter value corresponding to the attribute; the MTC feature information is used to control the terminal; and the sending unit is configured to send the acquired MTC feature information of the terminal to The terminal and/or other access network nodes.

In one aspect, an embodiment of the present invention further provides a mobility management entity, where the mobility management entity includes:

Means for acquiring machine type communication MTC feature information of the terminal, the MTC feature information And including at least one MTC attribute and a parameter value corresponding to the attribute, the MTC feature information is used to control the terminal; and a unit for controlling the terminal according to the MTC feature information.

The method of the embodiment can implement the MTC feature information synchronization between the MTC terminal and the network side by transmitting the MTC feature information of the MTC terminal between the network elements, and enable the network side to implement effective management of the MTC terminal according to the MTC feature information. Save network resources. BRIEF DESCRIPTION OF DRAWINGS FIG. 1 is a schematic diagram of the principle of Embodiment 1 of the present invention;

Figure la is an overall flowchart of a terminal control method according to Embodiment 1 of the present invention.

2 is a schematic diagram of a message delivery process according to Embodiment 1 of the present invention;

3 is a schematic diagram of a first specific implementation method according to Embodiment 2 of the present invention;

4 is a schematic diagram of a second specific implementation method according to Embodiment 2 of the present invention;

FIG. 5 is a schematic diagram of a third specific implementation method according to Embodiment 2 of the present invention; FIG.

6 is a schematic diagram of a first specific implementation method according to Embodiment 3 of the present invention;

7 is a schematic diagram of a second specific implementation method of Embodiment 3 of the present invention;

8 is a schematic diagram of a first specific implementation method according to Embodiment 4 of the present invention;

9 is a schematic diagram of a second specific implementation method according to Embodiment 4 of the present invention;

FIG. 10 is a schematic diagram of a first specific implementation method according to Embodiment 5 of the present invention; FIG.

11 is a schematic diagram of a second specific implementation method according to Embodiment 5 of the present invention;

12 is a schematic diagram of a third specific implementation method according to Embodiment 5 of the present invention;

13 is a schematic diagram of a fourth specific implementation method according to Embodiment 5 of the present invention;

14 is a schematic diagram of a first specific implementation method according to Embodiment 6 of the present invention;

15 is a schematic diagram of a second specific implementation method according to Embodiment 6 of the present invention;

16 is a flowchart 1 of MTC gateway and network interaction MTC feature information in Embodiment 7 of the present invention; FIG. 17 is a flowchart 2 of MTC gateway and network interaction MTC feature information in Embodiment 7 of the present invention; 18 is a schematic diagram of a first specific implementation method according to Embodiment 7 of the present invention;

Figure 19 is a schematic diagram of a system according to Embodiment 8 of the present invention;

20 is a functional block diagram of a core network node according to Embodiment 8 of the present invention;

21 is a functional block diagram of a terminal according to Embodiment 8 of the present invention;

Figure 22 is a functional block diagram of an access network node according to Embodiment 8 of the present invention; Figure 23 is a functional block diagram of an access gateway according to Embodiment 8 of the present invention. detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is a partial embodiment of the invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

The embodiment of the present invention specifically defines and describes the MTC feature information, and provides a comprehensive method for transmitting MTC feature information, so that the core network node can effectively manage the MTC terminal based on the obtained MTC feature information, thereby saving network resources; The terminal can also set its own capabilities according to the MTC feature information to match the control and management of the core network. The following are examples of several MTC features: Mobility characteristics: It embodies the characteristics of whether the MTC terminal will move, and the frequency, extent and mode of movement. Mobility features may be further divided into: no mobility features (still), low mobility features, high mobility features, and so on. For different mobility characteristics, the network can be managed differently, such as: no mobility management (eg: for stationary MTC terminals), limited mobility management (eg: no roaming related functions), different Frequency mobility management (eg, for devices with low mobility characteristics, reducing the frequency of mobility management processes) and more.

Time-controlled features: Reflect the time-based behavioral characteristics of MTC terminals. For example: data transmission at a specific time, access at a specific time, paging at a specific time, and the like. The network can be managed differently for different time-controlled features, such as: Time for data transmission for MTC terminals Control features, the network can more rationally allocate resources; for the time-controlled nature of MTC terminal paging, the network can avoid unnecessary paging, MTC terminals can also avoid unnecessary paging channel monitoring and so on.

Data transmission characteristics: It embodies the characteristics of MTC terminals in terms of data transmission volume, data transmission direction, and data transmission mode. For example, according to the amount of data transmission can be divided into: high data transmission equipment (such as: multimedia data transmission voice), low data transmission equipment (such as: only a small amount of key information transmission); according to the data transmission direction can be divided into: two-way data transmission equipment It can only receive data devices and only transmit data devices. It can be divided into: according to different data transmission modes: signaling transmission equipment, single bearer transmission equipment, multi-bearer transmission equipment, and so on. Obviously, the network uses different processing methods for MTC terminals with different data transmission characteristics, which can achieve resource optimization purposes, such as: for only data devices that can be sent, the network will not send data to them; for low data transmission devices, networks The data can be carried in the signaling message without establishing a dedicated bearer or the like.

The MTC feature information of the embodiment of the present invention generally includes two parts, the first part is an MTC attribute, and the second part is a parameter value included in the MTC attribute. The following are some examples of attributes and parameter values. The parentheses are the attribute names, and the parentheses are the parameter values. Optionally, the attribute name may be other names. As long as the meanings of the representatives are the same, they belong to the protection scope of the number of claims; the included parameters may use only part rather than all of them in practical applications.

Attribute <1>, area restriction, region (area list, no limitation), indicates whether the MTC terminal can only move within a limited area, "area list" indicates that the MTC terminal can only move within a limited area, and the value is the terminal. Restricted area. For example, {cell 1, cell2, cell3} means that the MTC terminal can only move in the cell1, cell2 and cell3 areas; {TA1, TA2} means that the MTC terminal can only move in the TA1 and TA2 areas, if the MTC terminal has the Areas that may result in failure to be serviced, etc. "No limitation" indicates that the MTC terminal has no zone restrictions. The possible optimization of the attribute is that the TA list allocated to the MTC terminal is smaller than the restricted area, or when paging, paging is performed in the intersection of the TA list and the restricted area, thus reducing the paging overhead. It may even include a ranked area list parameter, indicating a list of regions, such as {cell 1, cell2, eel 13} Indicates that the MTC terminal enters eel 11 after entering eel 11, and then enters cell3, and does not directly enter cell3 or other areas from celll. The method can be used to enable the network to optimize the paging of the MTC terminal according to the area restriction information, such as paging the MTC terminal only in a specific area, such as paging in an area list or an area in the sequence area list; The sequence area list of the UE is {cell 1, cell 2, cell 3}. If the UE initiates access in the eel 12, the network may only page the {cell 2, cell 3} area in the subsequent paging because the MTC terminal It is impossible to return to eel 11.

Attribute <2>, speed (high, middle, low, stationary), indicating the moving speed of the MTC terminal, whether it is "high speed" or "medium speed" or "low speed" or "still, so, so high speed" Medium speed "need to define a certain speed range, such as "high speed" of more than 100km / h, "medium speed" of "30km / h - 100km / h", etc. According to different speeds, the network can assign different TA lists, For example, a high-speed MTC terminal allocates a larger TA list, and a low-speed allocation of a smaller TA list can achieve an overhead balance between TAU and paging. For a stationary MTC terminal, there may be more optimizations. It is the specific speed as a parameter.

Attribute <3>, call origination (CP specific (time), UP specific (time)), any time), indicating whether the MTC terminal is allowed to initiate access (similar to the calling party), no means not allowing MTC The terminal initiates the access. The "predefined time" indicates that the access is only allowed to be initiated at the specified time, such as between 1:00-2:00 every day, or at a certain moment, such as 1:00 on the 2,09.8.20 day. It may also continue to be classified as a signaling to initiate access at a specified time, such as a call or service request at a certain time or a certain time period; or may be classified as a user plane or control plane to initiate access at a specified time, such as a certain time or The time period initiates access to an APN or P匪 connection. "Any time" means that the MTC terminal is allowed to access the network at any time. With this method, optimization can be made as follows: If the M0 attribute (ie, the value) of the MTC terminal is "no", that is, the MTC terminal does not support the initiative to initiate the access, the MTC terminal may have no random access procedure and other access procedures. Program, cylinder terminal.

Attribute <4>, call termination MT (no, predefined time (CP specific (time), UP specific (time)), any time), and the only difference between the above is that the MT indicates the MTC terminal. The end of the network; that is, the network initiates the service to the MTC terminal (paging the MTC terminal, similar to the called party). With this method, optimization can be made as follows: If the MT attribute of the MTC terminal is "no", that is, the MTC terminal can only initiate M0, and the network cannot page the MTC terminal, the MTC terminal can not perform the periodic location update process, and the network also The MRT (Mobile Reachable Timer) timer is not set for the MTC terminal. If the MT attribute of the MTC terminal is "predefined time", the MTC terminal can turn off the receiver outside of the predetermined time (because no paging occurs) to achieve the purpose of power saving.

Attribute <5>, access delay tolerance (yes, no, tolerance time) , indicates whether the MTC terminal is not sensitive to the delay at the time of access. Yes means that the MTC terminal is delay-insensitive when accessing, that is, the service of the MTC terminal is not urgent, and it does not matter if it is accessed again after a period of time. No indicates that the MTC terminal is delay-sensitive when accessing, that is, it needs to be accessed as soon as possible when there is a service. Tolerance t ime means that it can be accessed only for a period of time; if tolerance time = 1 hour, it means that the MTC terminal can delay the successful access at any time within one hour when there is service. Thus, if the MTC terminal delay is not sensitive, then if the network is congested, the MTC terminal can delay access and avoid further network congestion.

Attribute <6>, Termination delay tolerance (yes, no, tolerance time), similar to attribute 5, indicates whether the MTC terminal is insensitive to delay. If the MTC terminal is insensitive to the termination delay (that is, the attribute value of the Termination Delay Tolerance is "yes"), when the downlink page arrives, the network can postpone the paging (such as the current network load is high) to make reasonable resources. Scheduling.

Attribute <7>, whether circuit-switched CS (yes, no) is supported, whether CS (Circuit Switched) is supported, yes means support, no means no support (ie PS only, packet switching). If the MTC terminal does not support CS, then all CS-related processes (such as CSFB) can be simply not implemented.

Attribute <8>, data rate (no limitation, lOk/s, lk/s ...), indicates the data rate, no limit or lkbps-lOkbps range, or other values. According to the data rate of the MTC, if the rate is less than a certain threshold, the data transmission and reception of the MTC terminal and the network can be controlled. The face is made without establishing a user plane connection.

Attribute <9>, based on Group Based (no, group id (same location, same user same feature)), indicates whether it belongs to a group member, no indicates that the MTC terminal does not belong to any group, and "group id" indicates an MTC terminal. The group belonging to the "group id" identifier, "same location" indicates the group formed by the group because it is in the same area; the same user indicates the group formed by the same user; "same feature" indicates that the group has the same characteristics. The group formed. According to the group's attributes, the network can perform group accounting (rather than separate billing) and many other optimizations.

Attribute <10>, whether to support high reliability High Availability (no, yes), indicates whether the MTC terminal is connected with high reliability, no means no, yes means high reliability. If the MTC terminal requires high reliability, the network needs to maintain the connection of the MTC terminal and cannot easily release the connection.

Attribute <11>, whether to support the exception check requirement Theft/Vandalism Vulnerable (no, yes), indicates whether the MTC terminal has the requirement for abnormality detection such as anti-theft/destruction, no means no such requirement, yes means there is demand, so if the terminal If it is stolen or misused, the network will check it. If it is confirmed stolen/abuse, the network may conduct prevention and control work, such as deleting the contract of the MTC terminal.

Through the description of the above attributes, an example of the optimization of an MTC and network is as follows: Table 1 shows the attributes of an MTC terminal (such as the electronic monitoring system of the road):

Table 1

Theft/Vandalism Vulnerable Yes

Other property?

The table indicates that the restricted area of the MTC terminal is a fixed area; it is stationary; the access cannot be initiated, and the request can only be initiated by the network to the MTC terminal, and the MTC terminal cannot actively access the network; The Acces s delay tolerance parameter is meaningless. When the network initiates a request to the MTC, the request can be deferred. The MTC terminal can only use the PS service and no CS service; the data rate does not exceed lkbps; the MTC terminal belongs to a group, and the group is based on Group formed by the same user; no reliability requirement; if the MTC terminal is abnormal (stolen, etc.), the network can detect and avoid further loss.

Of course, the above attributes may have other variants in practice, such as Acces s delay tolerance, yes means that the access delay is not sensitive; in reality, acces s delay urgency ( yes, no ) may be used, and yes represents access delay sensitivity. No means that the access delay is not sensitive, and the meaning of yes and no with acces s delay to lerance is exactly the opposite; the other actual value of Group based may be only yes and no, yes means that the MTC terminal is group based. , and no refinement is how to form a group or a group id, the group id may be notified by other forms of the network (such as the contract of the MTC terminal); MT may only have parameters (no, predef ined t ime, any t ime), predef ined T ime indicates the scheduled time of any access, and so on. Such modifications are still within the scope of the claims.

Table 2 shows examples of values corresponding to different types of services. Service 1 is a vehicle management system; Business 2 is a vending machine; Business 3 is a health inspection system (implanted into the human body); Business 4 is a gas meter reading device; Service 5 is a fire report device.

Table 2

M2M service class M2M service M2M service M2M service M2M service M2M service properties class 1 class 2 class 3 class 4 class 5 limited region No limitation Cell list TA list Cell list Cell list

Speed high low middle stationary stationary

MO Any time no Any time Predefined time Any time

(3:00 AM every day)

MT Any time Any time no no Any time Access delay no yes no yes No tolerance

Determination yes yes no yes No delay tolerance

CS no no no no no

Data rate 10 kbps 1 kbps 1kbps 1kbps 1kbps

Group Based No Yes No Yes No

High Availability no No Yes Yes Yes

Theft/Vandalism yes yes No Yes Yes Vulnerable

Other property? No No No Yes Yes If the value of a set of attributes is defined as a "service category, then, then only the value of this service category needs to be carried, and the MTC feature is easily obtained. For example, definition 1, 2 , 3, 4, 5, these five values, as the value of service c las s, then the MTC terminal carries service c las s = 1 , which represents the value of a specific set of attributes, which will greatly simplify the parameters. Carry.

In short, regardless of whether the MTC terminal carries many attributes and values, or carries a simplified value, it acts as the MTC feature information of the MTC terminal and communicates with the network, so that the network knows the characteristics of the MTC terminal or its service characteristics. Some attributes may be at the MTC terminal level, and some attributes are at the service level, such as a gas meter reading device, which may simultaneously initiate two services, service c las s=4 and service clas s = 5 as shown in Table 2, and The network may also modify the value of these attributes to notify the MTC terminal, or the MTC terminal does not carry any information to the network, and the MTC feature is directly determined by the network. The MTC feature information transfer of the case will be described in detail below in conjunction with a specific embodiment.

The embodiment of the present invention is described by taking a 3GPP LTE network as an example. Of course, the method is also applicable to other systems, such as UMTS networks, WiMAX networks, etc. If the system is a UMTS network, simply change the following solid E to SGSN, S-GW or P-GW to GGSN, and eNB to RNC. That is, the S1 interface message can be changed to "Iu interface message". The use of other implementation systems is also within the scope of the invention.

Example 1

This embodiment provides a method for controlling a terminal. FIG. 1 is a schematic diagram of the principle of the embodiment. One In an aspect, the network can acquire/save MTC feature information related to the MTC terminal according to the characteristics of the MTC terminal, and the MTC feature information can be directly or indirectly from the MTC terminal; on the other hand, the MTC terminal can effectively accept the network. Management, also need to obtain / save the MTC feature information provided by the network. In order to implement effective management based on MTC feature information, it is necessary to maintain coordination of MTC feature information on the network and the MTC terminal.

Figure la is an overall flowchart of a method for controlling a terminal according to the embodiment, as shown in Figure la: The method includes:

Step S101: The MTC feature information of the storage terminal, where the MTC feature information includes at least one MTC attribute and a parameter value corresponding to the attribute; the MTC feature information is used to control the terminal;

Optionally, the MTC feature information of the storage terminal includes: storing MTC feature information of the terminal at the core network node; and/or storing MTC feature information of the terminal in the terminal.

Optionally, the MTC feature information of the storage terminal includes: establishing an index according to a service category of the terminal, and storing an MTC feature information set of each service category corresponding to each index value.

Optionally, the MTC feature information of this embodiment includes at least one of the following attributes:

Attribute 1 : area limitation, the area is limited to the area range in which the terminal moves; Attribute 2: moving speed, the moving speed indicates the moving speed of the terminal; Attribute 3: mobile originating, the mobile originating indication indicates whether to allow And the access delay sensitivity indicates Whether the terminal is sensitive to access delay; attribute 6: termination delay sensitivity, the termination delay sensitivity indicates whether the terminal is sensitive to the termination delay; attribute 7: whether circuit switching is supported; attribute 8: data rate, The data rate represents a rate of data transmitted and received by the terminal; attribute 9: based on a group, the group-based indicates whether the terminal belongs to a group member; attribute 10: whether connection high reliability is supported, the connection high reliability representation The terminal needs to maintain the connection between the terminal and the network; Property 11: Whether to support the abnormality checking requirement.

Optionally, the parameter value of the area restriction attribute includes: a restricted area list; The controlling the terminal includes: the tracking area list allocated to the terminal is smaller than the restricted area list; or paging the terminal in an intersection of the tracking area list and the restricted area list; or according to the restricted area The order of the list determines the mobile area of the terminal, and the terminal is paged within the determined area.

Optionally, the parameter value of the moving speed attribute includes: a speed range; the controlling the terminal includes: assigning a tracking area list to the terminal according to the speed range.

Optionally, the parameter value of the mobility initiation attribute includes: supporting or not supporting call initiation, where the parameter value further includes: a call initiation time, a supported call initiation signaling, and a call originating access network. One or more parameters in the type; the controlling the terminal includes: performing corresponding control on the random access procedure of the terminal according to the call initiation parameter value.

Optionally, the parameter value of the mobile termination attribute includes: supporting or not supporting call termination, and further including a call termination time when supporting call termination; the controlling the terminal includes: when the call termination is not supported, The terminal performs paging; or controls the terminal not to perform a periodic location update process; or does not set a mobile reachable timer MRT for the terminal; when the call termination is supported, the terminal is controlled to be outside the call termination time The time to turn off the receiver.

Optionally, the parameter value of the access delay sensitivity attribute includes: an access allowed delay; the controlling the terminal includes: controlling, according to the access allowed delay, the terminal according to a network Load conditions are accessed.

Optionally, the parameter value of the termination delay sensitivity attribute includes: a termination allowed delay; the controlling the terminal includes: performing paging control on the terminal according to the termination allowable time and a network load condition.

Optionally, whether the parameter value of the circuit switched attribute is supported comprises: supporting or not supporting circuit switching; and the controlling the terminal comprises: when the circuit switching is not supported, the control terminal cancels the process related to the circuit switching.

Optionally, the parameter value of the data rate attribute includes: a data rate range; the controlling the terminal includes: controlling the terminal and the network when the data rate is less than a set threshold The control plane is used for data transmission and reception; otherwise, the user plane is used for data transmission and reception.

Optionally, the group attribute-based parameter value includes: a group identifier; the controlling the terminal includes: the network performing group charging on the terminal according to the group information.

Optionally, whether the parameter value supporting the connection high reliability attribute comprises: supporting or not supporting high reliability; and the controlling the terminal comprises: when supporting high reliability, the network maintains the connection of the terminal.

Optionally, the parameter value of the abnormality check requirement attribute is: whether the abnormality check is supported or not supported; when the abnormality check is supported, the terminal abnormality is judged and processed according to the abnormality check requirement information.

Step S102: Transfer the MTC feature information of the terminal to the network node.

Optionally, the transmitting the MTC feature information of the terminal to the network node further includes: performing an index according to the service category of the terminal, and searching for the MTC feature information set of the corresponding service category according to the index, and transmitting the information to the network node The set of MTC feature information of the corresponding service category.

Optionally, the transmitting, by the network node, the MTC feature information of the terminal includes at least one of the following delivery modes:

Transmitting the MTC feature information of the terminal between the core network nodes, such as between the solid E and the HSS;

Transmitting, by the HSS, the MTC feature information of the terminal to the terminal by the core network node;

Transmitting the MTC feature information of the terminal to the access network node by the core network node, for example, by the HSS to the base station;

Transmitting MTC feature information of the terminal between access network nodes, such as between different base stations;

Transmitting, by the terminal, the MTC feature information of the terminal to the core network node and/or the access network node, for example, by the terminal to the solid E and/or the base station;

Passing the MTC feature information of the terminal through the access gateway at the terminal and the core network node or Forwarding between access network nodes, such as by the core network node or the access network node, is transmitted to the terminal through the access gateway.

Optionally, the transmitting, by the core network node, the MTC feature information of the terminal to the terminal includes: adding or deleting an MTC attribute in the MTC feature information, and transmitting the MTC feature information after the added or deleted Giving the terminal; and/or assigning a parameter corresponding to the MTC attribute in the MTC feature information, and transmitting the assigned MTC feature information to the terminal.

FIG. 2 is a schematic diagram of a terminal control method according to an embodiment of the present invention. as shown in picture 2:

Step 201: The MTC terminal reports the MTC feature information to the network, including the attribute and the parameter corresponding to the attribute. The transmission of the MTC feature information may be combined in one message or separately, that is, different parameters may be used. Different messages, different processes, etc. to convey these two aspects of information.

Step 202: After receiving the MTC feature information, the network combines: 1) the MTC feature information supported by the network, and 2) the subscription/configuration associated with the MTC terminal to adjust and set the received MTC feature information.

Step 203: The network sends the MTC feature information after the subscription and configuration processing to the MTC terminal. Through the above three steps, the MTC feature information can be coordinated between the network and the MTC terminal, so that the network can effectively manage the MTC terminal based on the MTC feature information. It should be noted that these three steps involve a complete negotiation process, and in certain cases, not all three steps are necessary, sometimes only step 1, or only steps 1, 2, or only Steps 2, 3, or only step 3 can be used to synchronize the MTC feature information between the MTC terminal and the network. The transfer of MTC feature information in detail will be explained in the subsequent embodiments.

Example 2:

The embodiment provides an MTC feature information transmission method, in which the MTC feature information of the MTC terminal is stored on the network side, and the UE indirectly transmits the MTC feature information to the network. The technical solution includes the following steps: The MTC feature information is saved on the network side (for example: in the HSS (Home Subscr iber Server). EIR (Equipment Ident i ty Reg is ter) _3⁄4 The MME (in the network entity such as the Mobility Management Entity) and the MTC server (the MTC server), the UE provides the identifier information or the type information or the index information to the network by using the message, and the identifier information or the type information or the index information may include: Identification (IMSI), device identification (IMEI), machine model, machine capability (or part) or agreed index number, etc.; network side from the network that stores MTC feature information according to the identification information or type information or index information provided by the UE The corresponding MTC feature information is obtained in the node.

FIG. 3 is a schematic diagram of the first specific implementation method of the second embodiment. In the scenario of FIG. 3, the MTC feature information is stored in the network node EIR, and the MME can query and obtain the corresponding MTC feature information according to IMEI or IMEISV (International Mobile Equipment Identity Software Vers ion).

Step 301: The UE carries device identification information (such as: IMEI, IMEISV or a part thereof) in the message sent to the solid E;

Step 302: The MME sends a query request message to the EIR according to the received device identification information (such as: IMEI, IMEISV or a part thereof);

Step 303: The EIR performs an inquiry according to the device identification information (such as: IMEI, IMEISV, or a part thereof), and returns the corresponding MTC feature information to the solid E.

Through the above steps, the network node (such as: 丽 E) can indirectly obtain the MTC feature information corresponding to the MTC terminal (eg, UE).

FIG. 4 is a schematic diagram of a second specific implementation method of Embodiment 2. In the scenario of FIG. 4, the MTC feature information is stored in the solid E in a manner that the contracted index is used as a key. The index represents a service class (Service Class), and the index according to the contract can be obtained in the solid E. MTC feature information.

As shown in FIG. 4: Step 401: The UE carries an index, such as a service class id or a specific attribute and a value, and may also be an APN information, that is, a service information, and a solid E saves the APN and the service. Corresponding relationship of the information, so as to know what kind of feature information the UE should have, and the E is able to obtain the MTC feature information corresponding to the index according to the index. The method of FIG. 4 is also a method for causing a network node (eg, solid E) to indirectly obtain MTC feature information corresponding to an MTC terminal (eg, UE). In this case, the MTC feature may be at the MTC terminal level, such as the MTC feature that the group of terminals has in common; or the service level, such as the MTC feature that the specific service MTC terminal has; or even the bearer level. , such as for the MTC feature that bears the MTC terminal.

FIG. 5 is a schematic diagram of a third specific implementation method of the second embodiment. In the scenario of FIG. 5, the MTC feature information is stored in the contract database HSS, and the corresponding MTC feature information can be queried according to IMSI and/or IMEI and/or IMEISV and/or APN and/or service c las s id. As shown in Figure 5:

Step 501: The UE carries the identifier information (such as IMSI.IMEI.IMEIVV, APN or service class id or a combination thereof) in the message sent to the MME.

Step 502: The solid E sends a query request message to the HSS according to the received identification information (such as: IMSI, IMEI, IMEISV, APN or service c las s id, or a combination thereof);

Step 503: The HSS performs an inquiry according to the received identification information, and returns the corresponding MTC feature information to the solid E.

Through the above steps, the network node (eg, solid E) can indirectly obtain the MTC feature information corresponding to the MTC terminal (eg, UE).

The method of Figure 3 - Figure 5 is a brief description of Embodiment 2, in fact, in addition to using a special process (Figure 3 - Figure 5), it can also be combined with existing processes, such as: At tach process, TAU process , service request process, P匪 connection process, and so on.

Example 3:

The embodiment provides a method for transmitting MTC feature information, in which the MTC feature information is stored in an MTC terminal (for example, a UE), and the UE directly provides MTC feature information to the network through a message, which may be through 1) a newly defined message, 2) The newly defined parameters, 3) use specific fields in the existing parameters, etc.; the network side receives and saves the corresponding MTC feature information. Similarly, in addition to using a dedicated process, it can be combined with existing processes, such as: At tach process, TAU flow Process, service request process, P匪 connection process, and so on.

FIG. 6 is a schematic diagram of the first specific implementation method of Embodiment 3. As shown in FIG. 6: Step 601: The UE carries the MTC feature information (all or part of the feature information, terminal level or service level) in the attach request (AUACH Reques t) message in the attaching process (AUach) to the network. Or bearer level feature information).

FIG. 7 is a schematic diagram of a second specific implementation method of Embodiment 3. In the scenario of FIG. 7, the UE may transmit the MTC feature information to the eNB through a response message during the network-initiated capability query process, and further transmit it to the eNB through the eNB. In this flow, the MTC feature information can be delivered as part of the UE capability information. As shown in Figure 5:

Step 702: The eNB sends a capability query request (UE Capabiyi Query) to the UE; Step 703: The UE feeds back a capability information response (UE Cap IPTV) to the eNB to transmit the MTC feature information to the eNB.

Step 704: The eNB further transmits the MTC feature information to the UE through the UE CAPABILITY INFO INDICATION message, where the MTC feature information may be delivered as part of the UE capability information.

Example 4:

The fourth embodiment provides a method for transmitting MTC feature information. In many cases, the network needs to transmit the MTC feature information to the UE. For example, after the network receives the MTC feature information sent by the UE, the network adjusts the MTC feature information. In order to maintain the consistency of the network and the terminal information, the adjusted MTC feature needs to be transmitted to the UE; or the network assigns the MTC feature provided by the UE; or when the network initiates the service, directly transmits the relevant MTC feature information to the UE. UE and so on. The method for the network to transmit the MTC feature information to the UE includes: 1) the network is delivered to the UE through the NAS message; 2) the network delivers the message to the UE through the RAN. FIG. 8 is a schematic diagram of a first specific implementation method of Embodiment 4. In the scenario of FIG. 8, after obtaining the MTC feature information, the core network node (eg, MME) may transmit the MTC feature information to the MTC terminal (eg, UE) through the NAS message. The following takes the case of the network initiated service as an example, as shown in Figure 8: Step 801: The solid E receives the message initiated by the service, where the corresponding MTC feature information is carried. The information may be received directly from the MTC server, or the MTC server may be forwarded through the P-GW or the S-GW. E, it may also be that the solid E is obtained from the HSS or itself; the following is similar and will not be described again.

Step 802: The solid E initiates a service to the related UE, and carries the corresponding MTC feature information in the NAS message.

FIG. 9 is a schematic diagram of a second specific implementation method of Embodiment 4. In the scenario of Figure 9, after obtaining the MTC feature information, the core network node (such as: solid E) can also transmit the MTC feature information to the MTC terminal (such as UE) through the RAN. The following is an example of a network-initiated service, as shown in Figure 9:

Step 901: The solid E receives the service initiated message, where the corresponding MTC feature information is carried. Step 902: The solid E transmits the MTC feature information to the RAN (eg, eNB) through the S1 interface message. Step 903: The RAN is in the same UE. In the RRC message of the interaction, the corresponding MTC feature information is delivered to the UE.

Similarly, the technical solution can be combined with existing processes, such as: At tach process, TAU process, service request process, PDN connection process, etc., in addition to using a dedicated process (as above).

Example 5:

The embodiment 5 provides an MTC feature information transmission method. Sometimes, the access network RAN needs to obtain MTC feature information. The method for the RAN to obtain the MTC feature information includes: 1) being sent from a core network (eg, solid E); 2) uploading from an MTC terminal (eg, UE); 3) obtaining from other access network nodes (eg, other eNBs) ). Corresponding to the following three embodiments.

FIG. 10 is a schematic diagram of a first specific implementation method of Embodiment 5. In the scenario of FIG. 10, after obtaining and storing the MTC feature information, the core network (eg, MME) may use the interface message (such as an S1 interface message) between the core network and the access network to perform the MTC feature required by the RAN. The message is passed to the RAN. This process may be triggered by certain events, such as: Receiving a service initiation message from the MTC server. As shown in Figure 10: Step 1001: The solid E receives the service initiated message, where the corresponding MTC feature information is carried; or the feature information is from another entity or itself.

Step 1002: The solid E sends the MTC feature message required by the RAN to the RAN through an interface message (such as an S1 interface message) between the core network and the access network.

FIG. 11 is a schematic diagram of a second specific implementation method of Embodiment 5. In the scenario of FIG. 11, the same process can be combined with the existing process. For example, in the TAU process, after receiving the TAU request message, the MME transmits the MTC feature information to the eNB in the initial context setup request, the MTC feature. It can also be used as part of the capability information. As shown in Figure 11:

Step 1101: The MME acquires a TAU Reques t message sent by the UE.

Step 110 ² : The MME transmits the MTC feature information to the eNB in an initial context establishment request (INITIAL CONTEXT SETUP REQUEST), and the MTC feature may also be part of the capability information.

Step 1103: The eNB sends an initial context setup response (INITIAL CONTEXT SETUP RESPONSE) to the UE.

FIG. 12 is a schematic diagram of a third specific implementation method of Embodiment 5. In the scenario of FIG. 12, the RAN may obtain corresponding MTC feature information directly from the MTC terminal (ie, UE) side. In the process of initiating the establishment of the RRC connection, the UE may transmit the MTC feature information to the RAN through an RRC connection setup request message or a setup complete message or other message. As shown in Figure 12:

Step 1201: The UE initiates an RRC Connection Establishment Request (RRC Connection Reques t) message to the RAN, and carries the corresponding MTC feature information in the message.

Step 1202: The RAN sends an RRC Connection Setup (RRC Connection Setup) message to the UE. Step 1203: The UE sends an RRC Connection Setup Complete message to the RAN, and may also carry the corresponding MTC feature in the message. information.

FIG. 13 is a schematic diagram of a fourth specific implementation method of Embodiment 5. In the scenario of FIG. 13, in the access network RAN, one eNB may obtain corresponding MTC feature information from other eNBs. For example, in the X2 handover process, the source eNB may carry the MTC feature information in the message that sends the handover request to the target eNB. Step 1301: The source eNB sends a handover request (HANDOVER REQUEST) message to the target eNB, where the message may carry the MTC feature information.

Step 1302: The target eNB sends a HANDOVER REQUEST ACKNOWLEDGE message to the source eNB.

Step 1303: The source eNB sends a handover command (HANDOVER COMMAND) to the UE.

Example 6:

The sixth embodiment provides an MTC feature information transmission method, which is: transmitting MTC feature information in a core network. After the core network node (such as the solid E) obtains the MTC feature information of the UE, if the UE moves to enter the new core network node, the new core network node may acquire the MTC feature information of the UE from the old core network node. . Of course, the new core network node may also obtain the MTC feature information of the UE from the HSS or the UE or the AN node. For details, refer to the description of the foregoing technical solution, and details are not described herein again. The focus here is on MTC feature information transfer between core network nodes:

FIG. 14 is a schematic diagram of the first specific implementation method of Embodiment 6. In the scenario of FIG. 14, source E obtains corresponding MTC feature information from the context response message sent by the target solid E. As shown in Figure 14:

Step 1401: The source solid E sends a context request (Context Reques t) message to the target solid E; Step 1402: The target MME sends a context response (Context Response) message to the source MME, and carries the MTC feature information in the message;

Step 1403: The source solid E sends a context acknowledgment (Context Acknowledge) message to the target solid E.

FIG. 15 is a schematic diagram of a second specific implementation method of Embodiment 6. In the scenario of FIG. 15, after acquiring the MTC feature information of the UE, the core network node may also send the information to the user plane node, such as the S-GW/P-GW or the GGSN. It is possible to send all the features of the MTC, or only part of the MTC feature information, such as only the Group Based group id (same loca ti on, same user, same feature), that is, the composition type of the group, so that the user plane node can Information system: group billing or other operations, can be sent through new messages or use existing messages (such as at tach process The create session request message, or the create session response in the dedicated bearer setup process, adds a parameter to send. The user plane node can also pass this information (such as S-GW to P-GW). As shown in Figure 15:

Step 1501: The MME sends a Create Session Request message to the S-GW, where the message carries the MTC feature information, which may be all MTC feature information, or part of the MTC feature information.

Step 1502: The S-GW sends a Create Session Request message to the P-GW, where the message carries the MTC feature information. Of course, the S-GW may not transmit the MTC feature information to the P-GW.

Step 1503: The P-GW sends a Create Session Response message to the S-GW. (It is also possible that the MTC feature information is transmitted from the P-GW to the S-GW, for example, the P-GW acquires the MTC feature from the MTC Server. Information, then passed to S-GW)

Step 1504: The S-GW sends a Create Session Response message to the solid E. (It is also possible that the MTC feature information is transmitted from the S-GW to the MME)

Example 7

The seventh embodiment provides an MTC feature information transmission method, and the method relates to processing the MTC feature information by the MTC gateway. In many cases, multiple MTC terminals can access the network through an MTC gateway. There are multiple solutions for the transmission of MTC feature information. It is also possible to have multiple MTC terminals integrated together. In this case, the integrated device can be regarded as an MTC gateway, so that the same solution as above can be used. The only difference is that the MTC terminal is actually the same as the MTC gateway. Is in the same network entity.

FIG. 16 is a flowchart 1 of MTC gateway and network interaction MTC feature information according to Embodiment 7 of the present invention. In one case, as shown in FIG. 16, the MTC gateway can perform MTC feature information interaction with the network, that is, the interaction does not depend on the MTC terminal under the MTC gateway. The MTC gateway may also carry the MTC feature information in the process of performing MTC message interaction with the MTC terminal, but the MTC feature information specific to these MTC terminals is invisible to the network. So in this case, the network treats the MTC gateway as if it were a UE. The same, the treatment plan is the same as before. As shown in FIG. 16, step 1601 is independent of step 1602, and there is no clear relationship between the two.

FIG. 17 is a second flowchart of MTC feature information of an MTC gateway interacting with a network in Embodiment 7 of the present invention. In another case, as shown in Figure 17, the MTC gateway interacts with the MTC feature information of the network. The MTC gateway is actually an intermediary between the MTC terminal and the network. The MTC gateway will transmit the received feature information of the MTC terminal to the network, and return the MTC feature information negotiated with the network to the MTC terminal. Therefore, in this case, the network treats the MTC terminal under the MTC gateway as if it were a UE, and the processing scheme is the same as before.

FIG. 18 is a schematic diagram of the first specific implementation method of Embodiment 7. In the scenario of Figure 18, the MTC gateway has negotiated with the network and saved related MTC feature information. The feature information can be: MTC feature of the MTC gateway itself, common MTC feature of all MTC terminals under the MTC gateway, The MTC feature allowed by the MTC gateway; the MTC terminal has its own specific MTC feature. During the MTC feature negotiation with the MTC gateway, the MTC gateway can determine and coordinate the difference of the MTC feature between the MTC terminal and the MTC gateway/network. This can be redundant by negotiating the MTC feature information with the network.

Step 1801: The MTC feature information is exchanged between the MTC gateway and the network (refer to Embodiment 2-4). The MTC feature information may be: MTC feature of the MTC gateway itself, and common MTC of all MTC terminals under the MTC gateway. The characteristics, the MTC features allowed by the MTC gateway, and the negotiated MTC feature information are stored in the MTC gateway and the network;

Step 1802: When an MTC terminal joins the MTC gateway, the message carries the MTC feature information specific to the MTC terminal, and the MTC gateway compares the received MTC feature information with the saved MTC feature information to determine whether There are differences, or conflicts occur;

Step 1803: If the MTC feature information is different from or conflicts with the MTC feature information stored in the MTC gateway, the feature information of the MTC gateway needs to be changed, thereby triggering the MTC gateway to perform MTC feature information interaction with the network. Realizing the update of MTC feature information on the network and the MTC gateway; Step 1804: After completing the update of the MTC feature information, the MTC gateway sends the negotiated MTC feature information related to the MTC terminal to the MTC terminal.

The method of the embodiment can implement the MTC feature information synchronization between the MTC terminal and the network side by transmitting the MTC feature information of the MTC terminal between the network elements, and enable the network side to implement effective management of the MTC terminal according to the MTC feature information. Save network resources. It should be noted that the method of the embodiment of the present invention is equally applicable to the UMTS system.

Example 8

The embodiment provides a terminal control system, which implements MTC feature information transmission of the terminal, so that the core network node can effectively manage the MTC terminal based on the obtained MTC feature information, and save network resources; the terminal according to the MTC feature Information can also set its own capabilities to match the control and management of the core network. Figure 19 is a schematic diagram of the system of the present embodiment. As shown in FIG. 19, the system includes: a terminal 190, an access network node 191, and a core network node 192. Optionally, the system further includes an access gateway 193. One side of the access gateway is connected to multiple terminals 190, and the other side is connected to the access network node 191. The MTC feature information of the terminal 190 may be stored in the core network node 192 or the terminal 190, or simultaneously stored in the core network node 191 or the terminal 190, and the information stored by the MTC feature information is implemented between the terminal 190 and the core network 191. Synchronization, corresponding control and management of the terminal according to the feature information. The specific transmission process of the MTC feature information and the control management method for the terminal according to the MTC feature information are described in detail in Embodiment 1-7, and are not repeated here.

Optionally, the system in this embodiment also supports the access network node to obtain the MTC feature information of the terminal 190 from the other access network node 191 or the core network node 192 or the terminal 190. Optionally, the system in this embodiment also supports The access gateway 193 implements the delivery of the terminal MTC feature information instead of the plurality of terminals 190.

FIG. 20 is a functional block diagram of a core network node according to an embodiment of the present invention. The core network node can be an HSS or EIR or a solid E or MTC server. As shown in FIG. 20, the core network node 192 of this embodiment includes: a storage unit 201, configured to store MTC feature information of the terminal, where the MTC feature information includes at least one MTC attribute and a parameter value corresponding to the attribute, where MTC feature information is used for the terminal For the control, refer to the related description of the foregoing method embodiment. The sending unit 202 is configured to transmit the MTC feature information of the terminal to the network node. Optionally, the core network node further includes: an obtaining unit 203, configured to acquire The MTC feature information of the terminal sends the MTC feature information to the storage unit 201.

Optionally, the storage unit 201 includes: a first storage unit, configured to separately store corresponding MTC feature information for each terminal according to an identifier of each terminal; and/or a second storage unit, configured to be used according to the terminal The service category is indexed, and the MTC feature information set is stored for each service category.

Optionally, the sending unit 202 includes one or any combination of the following: a first sending unit, configured to send MTC feature information of the terminal to another core network node; and a second sending unit, configured to access the network The node sends the MTC feature information of the terminal, and the third sending unit is configured to send the MTC feature information of the terminal to the terminal.

Optionally, the first sending unit is further configured to: after modifying the MTC feature information, send the information to the corresponding terminal, where the modifying includes adding or deleting the MTC attribute in the MTC feature information, and Modify the parameter values of the attribute.

Optionally, the acquiring unit 203 includes: a first acquiring unit, configured to acquire MTC feature information of the terminal from another core network node; or a second acquiring unit, configured to acquire an MTC feature of the terminal from the terminal information.

FIG. 21 is a functional block diagram of a terminal according to the embodiment. As shown in FIG. 21, the terminal 190 includes: a storage unit 211, configured to store MTC feature information of the terminal, where the MTC feature information includes at least one MTC. The attribute and the parameter value corresponding to the attribute; the MTC feature information is used to control the terminal. For details, refer to the related description of the foregoing method embodiment, and details are not described herein; the sending unit 212 is configured to store the The MTC feature information is sent to a core network node and/or an access network node. Optionally, the terminal further includes: an obtaining unit 213, configured to acquire MTC feature information of the terminal from the core network node, and send the MTC feature information to the storage unit 210.

Optionally, the storage unit 210 is configured to: establish an index according to a service category of the terminal, and store an MTC feature information set for each service category; the sending unit 211, configured to send the index value To the core network node and / or access network node.

FIG. 22 is a functional block diagram of an access network node according to the embodiment. As shown in FIG. 11, the access network node 191 includes: an obtaining unit 221, configured to use a core network node or a terminal or other access network node. Acquiring the MTC feature information of the terminal, where the MTC feature information includes: at least one MTC attribute and a parameter value corresponding to the attribute; the MTC feature information is used to control the terminal; and the sending unit 222 is configured to acquire The MTC feature information of the terminal is sent to the terminal and/or other access network nodes. As an example, the access network node may be a base station eNB, with specific reference to the foregoing description of the method embodiments.

FIG. 23 is a functional block diagram of an access gateway according to the embodiment. As shown in FIG. 23, the access gateway 193 includes: a receiving unit 231, configured to receive MTC feature information stored by the terminal, where the MTC feature information includes The MTC feature information is used to control the terminal, and the MTC feature information is used to control the terminal. For details, refer to the description of the foregoing method embodiment, and details are not described herein; And transmitting the MTC feature information stored by the terminal to the core network node.

Optionally, the receiving unit 231 is configured to receive MTC feature information stored by the terminal, where the MTC feature information includes: at least one MTC attribute and a parameter value corresponding to the attribute, where the MTC feature information is used for The terminal performs control; the sending unit 232 is configured to send the MTC feature information stored by the terminal to the access network node.

Optionally, the receiving unit 231 is configured to receive MTC feature information stored by the terminal, where the MTC feature information includes: at least one MTC attribute and a parameter value corresponding to the attribute, where the MTC feature information is used for The terminal performs control; the sending unit 232 is configured to send the MTC feature information stored by the terminal to the core network node and the access network node.

Optionally, the receiving unit 231 is configured to receive MTC feature information that is stored by the core network node, where the MTC feature information includes: at least one MTC attribute and a parameter value corresponding to the attribute, where the MTC feature information is used. And controlling, by the sending unit, the sending unit 232, configured to send the MTC feature information stored by the core network node to the corresponding terminal. The system in this embodiment can implement the MTC feature information synchronization between the MTC terminal and the network side by transmitting the MTC feature information of the MTC terminal between the network elements, and enable the network side to implement effective management of the MTC terminal according to the MTC feature information. Save network resources. It should be noted that the method of the embodiment of the present invention is also applicable to the UMTS system.

A person skilled in the art can understand that all or part of the process of implementing the above embodiment method can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium. The program, when executed, may include the flow of an embodiment of the methods as described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), or a Random Acces s Memory (RAM).

The above embodiments are only used to explain the technical solutions of the embodiments of the present invention, and are not limited thereto; although the embodiments of the present invention are described in detail with reference to the foregoing embodiments, those skilled in the art should understand that The technical solutions described in the embodiments are modified, or the equivalents of the technical features are replaced by the equivalents. The modifications and substitutions of the embodiments do not depart from the spirit and scope of the technical solutions of the embodiments of the embodiments of the present invention.

Claims

Claim

A method for controlling a terminal, the method comprising:

Acquiring the machine type communication MTC feature information of the terminal, the MTC feature information includes at least one MTC attribute and a parameter value corresponding to the attribute, where the MTC feature information is used to control the terminal;

The terminal is controlled according to the MTC feature information.

2. The method according to claim 1, wherein the obtaining the MTC feature information of the terminal comprises:

From the home contract server HSS or device identification register EIR or mobile management entity Solid E or machine type communication MTC server or terminal obtains MTC feature information of the terminal.

The method according to claim 1, wherein the method further comprises:

The HSS or EIR or the MME or the MTC server is indexed according to the service category of the terminal, and each index value corresponding to the index stores a set of MTC feature information corresponding to the service category;

The acquiring the MTC feature information of the terminal includes:

And searching, according to the index, a set of MTC feature information corresponding to the service category, and acquiring a set of MTC feature information of the corresponding service category.

The method according to claim 1, wherein the method further comprises: adding or deleting the MTC attribute in the MTC feature information, and transmitting the MTC feature information after adding or deleting the MTC attribute To the terminal; and/or

The parameter corresponding to the MTC attribute in the MTC feature information is assigned, and the MTC feature information assigned to the parameter corresponding to the MTC attribute is transmitted to the terminal.

The method according to any one of claims 1 to 4, wherein the MTC feature information comprises at least one of the following attributes:

Attribute 1 : area limitation, the area is limited to the area range in which the terminal moves; Attribute 2: moving speed, the moving speed indicates the moving speed of the terminal; Attribute 3: mobile originating, the mobile originating indication indicates whether to allow The terminal initiates access; attribute 4: mobile termination, the mobile termination indicates off Initiating the service to the terminal on the network side; Attribute 5: Access delay sensitivity, the access delay sensitivity indicates whether the terminal is sensitive to access delay; Attribute 6: End delay sensitivity, The termination delay sensitivity indicates whether the terminal is sensitive to termination delay; attribute 7: whether circuit switching is supported; attribute 8: data rate, the data rate indicates a rate of data transmitted and received by the terminal; and attribute 9: based on The group-based group indicates whether the terminal belongs to a group member; attribute 10: whether the connection is highly reliable, the high reliability of the connection indicates that the terminal needs to maintain the connection between the terminal and the network; Abnormal check requirements.

6. A method according to any one of claims 1 to 5, characterized in that

The MTC feature information includes an area restriction attribute, where the area restriction attribute is an area range in which the terminal moves;

The parameter values of the area restriction attribute include: a list of restricted areas;

The controlling the terminal according to the MTC feature information includes:

The list of tracking areas allocated for the terminal is smaller than the list of restricted areas; or

Placing the terminal in the intersection of the restricted area list and the tracking area list assigned to the terminal; or

The mobile area of the terminal is determined according to the order of the restricted area list, and the terminal is paged in the determined area.

7. A method according to any one of claims 1 to 6, characterized in that

The MTC feature information includes a moving speed attribute, and the moving speed attribute indicates a moving speed of the terminal;

The parameter values of the moving speed attribute include: a speed range;

The controlling the terminal according to the MTC feature information includes:

A tracking area list is allocated to the terminal according to the speed range.

8. A method according to any one of claims 1 to 7, characterized in that

The MTC feature information includes a mobility initiation attribute, where the mobile initiation attribute indicates whether the terminal is allowed to initiate an access; The parameter values of the mobility initiation attribute include: support or no support for call initiation, and the parameter value further includes: one of a call initiation time, a supported call initiation signaling, and a network type of call origination access when the call is initiated. Or multiple parameters;

The controlling the terminal according to the MTC feature information includes:

Performing corresponding control on the random access procedure of the terminal according to the call initiation parameter value.

9. A method according to any one of claims 1 to 8, characterized in that

The MTC feature information includes a mobile termination attribute, where the mobile termination attribute indicates that the network side initiates a service to the terminal;

The parameter values of the mobile termination attribute include: support or no support for call termination, and call termination time when supporting call termination;

The controlling the terminal according to the MTC feature information includes:

When the call termination is not supported, the terminal is not paged; or the terminal is not controlled to perform a periodic location update process; or the mobile reachable timer MRT is not set to the terminal;

When the call termination is supported, the terminal is controlled to turn off the receiver at a time other than the call termination time.

10. A method according to any one of claims 1 to 9, characterized in that

The MTC feature information includes an access delay sensitivity attribute, and the access delay sensitivity attribute indicates whether the terminal is sensitive to an access delay;

The parameter values of the access delay sensitivity attribute include: an access allowed delay;

The controlling the terminal according to the MTC feature information includes:

And controlling, according to the access allowed delay, the terminal to perform access according to a load condition of the network.

11. A method according to any one of claims 1 to 10, characterized in that

The MTC feature information includes a termination delay sensitivity attribute, and the termination delay sensitivity attribute indicates whether the terminal is sensitive to the termination delay;

The parameter values of the termination delay sensitivity attribute include: a termination allowed delay;

The controlling the terminal according to the MTC feature information includes:

Paging control is performed on the terminal according to the termination allowable delay and the network load condition.

The method according to any one of claims 1 to 11, wherein the MTC feature information includes whether to support circuit switching attributes;

Whether the parameter value of the circuit switching attribute is supported includes: supporting or not supporting circuit switching; and controlling the terminal according to the MTC feature information, including:

When circuit switching is not supported, the control terminal cancels the process associated with circuit switching.

13. A method according to any one of claims 1 to 12, characterized in that

The MTC feature information includes a data rate attribute, and the data rate attribute indicates a rate of data transmitted and received with respect to the terminal;

The parameter values of the data rate attribute include: a data rate range;

The controlling the terminal according to the MTC feature information includes:

When the data rate is less than the set threshold, the terminal and the network are controlled to use the control plane to perform data transmission and reception; otherwise, the user plane is used for data transmission and reception.

14. A method according to any one of claims 1 to 13, characterized in that

The MTC feature information includes a group attribute, and the group attribute indicates whether the terminal belongs to a group member;

The parameter values based on the group attribute include: a group identifier;

The controlling the terminal according to the MTC feature information includes:

Group charging is performed on terminals belonging to the same group according to the group identifier.

15. A method according to any one of claims 1 to 14, characterized in that

The MTC feature information includes whether the connection high reliability attribute is supported, and whether the connection high reliability attribute indicates that the terminal needs to maintain the connection between the terminal and the network;

Whether the parameter value of the connection to the high reliability attribute is supported includes: supporting or not supporting high reliability; and controlling the terminal according to the MTC feature information, including:

When high reliability is supported, the network maintains the connection of the terminal.

16. A method according to any one of claims 1 to 15, characterized in that

The MTC feature information includes whether an exception check requirement attribute is supported; Whether the parameter value of the abnormality check requirement attribute is supported includes: supporting or not supporting the abnormality check; and controlling the terminal according to the MTC feature information, including:

When the abnormality check is supported, the abnormality check requirement information is received, and the abnormality of the terminal is judged and processed according to the abnormality check demand information.

17. A core network node, wherein the core network node comprises:

a storage unit, configured to store MTC feature information of the terminal, where the MTC feature information includes at least one MTC attribute and a parameter value corresponding to the attribute, where the MTC feature information is used to control the terminal;

And a sending unit, configured to transmit the MTC feature information of the terminal to the network node, so that the network node controls the terminal according to the MTC feature information.

The core network node according to claim 17, wherein the storage unit comprises: a first storage unit, configured to store corresponding MTC feature information for the terminal according to an identifier of each terminal; and / or

And a second storage unit, configured to establish an index according to a service category of the terminal, and store, according to each index value of the index, a set of MTC feature information corresponding to the service category.

19. The core network node of claim 17 wherein:

The sending unit is further configured to: after modifying the MTC feature information, send the message to the corresponding terminal, where the modifying includes adding or deleting the MTC attribute in the MTC feature information, and parameters of the attribute The value is modified.

The core network node according to claim 17, wherein the core network node further includes:

And an acquiring unit, configured to acquire MTC feature information of the terminal, and send the MTC feature information to the storage unit.

The core network node according to any one of claims 18 to 20, wherein the core network node is a home subscription server HSS or a device identification register EIR or a mobility management entity solid E or a machine type communication MTC. server.

22. A terminal, wherein the terminal comprises:

a storage unit, configured to store MTC feature information of the terminal, where the MTC feature information includes at least one MTC attribute and a parameter value corresponding to the attribute; the MTC feature information is used to control the terminal;

a sending unit, configured to send the stored MTC feature information to a core network node and/or an access network node, so that the core network node and/or the access network node access the terminal according to the MTC feature information Take control.

23. The terminal of claim 22, wherein:

The storage unit is configured to: establish an index according to a service category of the terminal, and store, according to each index value of the index, a set of MTC feature information corresponding to the service category;

The sending unit is configured to send the index value to a core network node and/or an access network node.

24. A mobility management entity, wherein the mobility management entity comprises:

And a unit for acquiring machine type communication MTC feature information of the terminal, the MTC feature information includes at least one MTC attribute and a parameter value corresponding to the attribute, where the MTC feature information is used to control the terminal;

A unit for controlling the terminal according to the MTC feature information.

The mobility management entity according to claim 24, wherein the mobility management entity further comprises:

a unit for indexing the service category of the terminal;

Means for storing a set of MTC feature information corresponding to a service class for each index value corresponding to the index;

And the unit for acquiring the MTC feature information of the machine type of the terminal is specifically configured to search the set of the MTC feature information of the corresponding service category according to the index, and obtain the set of the MTC feature information of the corresponding service category.

The mobility management entity according to claim 25, wherein the mobility management entity further comprises: Adding or deleting the MTC attribute in the MTC feature information, and transmitting the MTC feature information after adding or deleting the MTC attribute to the unit of the terminal; and/or

The parameter corresponding to the MTC attribute in the MTC feature information is assigned, and the MTC feature information assigned to the parameter corresponding to the MTC attribute is transmitted to the unit of the terminal.

27. The mobility management entity of claim 24, wherein

The unit for controlling the terminal according to the MTC feature information, specifically, the tracking area list allocated for the terminal is smaller than the restricted area list; or

28. The mobility management entity of claim 24, wherein

The parameter values of the moving speed attribute include: a speed range;

The unit for controlling the terminal according to the MTC feature information is specifically configured to allocate a tracking area list to the terminal according to the speed range.

29. The mobility management entity of claim 24, wherein

The MTC feature information includes a mobile origination attribute, where the mobile origination attribute indicates whether the terminal is allowed to initiate an access;

The parameter values of the mobility initiation attribute include: support or no support for call initiation, and the parameter value further includes: one of a call initiation time, a supported call initiation signaling, and a network type of call origination access when the call is initiated. Or multiple parameters; The unit for controlling the terminal according to the MTC feature information is specifically configured to perform corresponding control on a random access procedure of the terminal according to the call initiation parameter value.

30. The mobility management entity of claim 24, wherein

The unit for controlling the terminal according to the MTC feature information is specifically configured to: when the call termination is not supported, not paging the terminal; or controlling the terminal not to perform a periodic location update process; Or not setting the mobile reachable timer MRT to the terminal;

31. The mobility management entity of claim 24, wherein

The unit for controlling the terminal according to the MTC feature information is specifically configured to control, according to the access allowed delay, the terminal to access according to a load condition of the network.

32. The mobility management entity of claim 24, wherein

The MTC feature information includes whether circuit switching attributes are supported;

Whether the parameter value of the circuit switching attribute is supported includes: supporting or not supporting circuit switching; the unit for controlling the terminal according to the MTC feature information is specifically used to control the terminal when circuit switching is not supported Cancel the process related to circuit switching.

The mobility management entity according to claim 24, wherein the MTC feature information includes a data rate attribute, the data rate attribute indicates a rate of data transmitted and received by the terminal, and a parameter value of the data rate attribute. Includes: Data rate range;

The unit for controlling the terminal according to the MTC feature information is specifically used when When the data rate is less than the set threshold, the terminal and the network are controlled to use the control plane to perform data transmission and reception; otherwise, the user plane is used for data transmission and reception.

The mobility management entity according to claim 24, wherein the MTC feature information comprises a group attribute, and the group attribute indicates whether the terminal belongs to a group member;

The parameter values based on the group attribute include: a group identifier;

The unit for controlling the terminal according to the MTC feature information is specifically configured to perform group charging on terminals belonging to the same group according to the group identifier.

The mobility management entity according to claim 24, wherein the MTC feature information includes whether to support a connection high reliability attribute, and whether the connection high reliability attribute indicates that the terminal needs to maintain the terminal and Network connection;

Whether the parameter value of the connection high reliability attribute is supported includes: supporting or not supporting high reliability; the unit for controlling the terminal according to the MTC feature information is specifically used when supporting high reliability , the network maintains the connection of the terminal.

36. The mobility management entity according to claim 24, wherein the MTC feature information includes whether an exception check requirement attribute is supported;

The parameter value of whether the abnormality check requirement attribute is supported includes: supporting or not supporting the abnormality check; the unit for controlling the terminal according to the MTC feature information is specifically used to receive an abnormality when the abnormality check is supported. The demand information is checked, and the abnormality of the terminal is judged and processed according to the abnormality check requirement information.