CN103581892A - Purpose MTC server determining method, device and system - Google Patents
Purpose MTC server determining method, device and system Download PDFInfo
- Publication number
- CN103581892A CN103581892A CN201210277414.XA CN201210277414A CN103581892A CN 103581892 A CN103581892 A CN 103581892A CN 201210277414 A CN201210277414 A CN 201210277414A CN 103581892 A CN103581892 A CN 103581892A
- Authority
- CN
- China
- Prior art keywords
- mtc server
- mtc
- identification
- address
- identification information
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 61
- 238000004891 communication Methods 0.000 claims abstract description 20
- 230000005540 biological transmission Effects 0.000 claims description 10
- 238000010586 diagram Methods 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000005457 optimization Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000003780 insertion Methods 0.000 description 1
- 230000037431 insertion Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses an MTC server determining method, device and system. The MTC server determining method, device and system are used for simply and effectively determining purpose MTC servers which receive data messages when an MTC-IWF entity is connected with multiple MTC servers. The method includes the steps that a network side device receives the data messages of UE, and the data messages include identification information used for determining purpose machine-type communication MTC servers; the network side device inquires the correspondence relationships of the identity information and identification and addresses of the MTC servers and determines the identification or the addresses of the MTC servers corresponding to the identification information included in the data messages. The invention discloses an uplink data sending method and device meanwhile.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method, a device, and a system for determining a destination-Type Communication (MTC) server.
Background
In a Machine Type Communication (MTC) project of the R11 stage, the 3GPP has conducted a study on an optimization scheme of a small data transmission characteristic. The small data is a data message with the size defined in the protocol 22.368v11.4.0 being below 1 kbyte or about 1 kbyte.
Currently, small data transmission optimization schemes can be roughly divided into two categories:
the first category is Short Message (SMS) based optimization schemes;
the second type is that a small data message is transmitted to a Mobility Management Entity (MME) by expanding a non-access stratum (NAS) message, and then the MME transmits the small data message to an MTC server (server).
In the second method, a Mobility Management Entity (MME) may transmit a small data packet to an MTC Server through two paths, where one path is that the MME goes to the MTC Server through a packet data network gateway (PDN GW, PGW), and the other path is that the MME goes to the MTC Server through an Interworking Function (IWF) entity.
The transmission path from MME to MTC Server through MTC-IWF entity mainly has the following two specific schemes:
in a first method, as shown in fig. 1, during an attachment process of a User Equipment (UE), an MME downloads subscription data of a user from a Home Subscriber Server (HSS), where the subscription data includes address information of a machine type communication interworking function (MTC-IWF) entity. Assuming that the MTC-IWF is not configured on the user side, the HSS needs to provide the address of a Generic MTC-IWF entity. After receiving a Non-Access Stratum (NAS) message carrying a small data message sent by UE, the MME acquires the small data message and forwards the small data message to an MTC-IWF entity based on address information acquired from HSS.
The address of the MTC-IWF entity may be configured in the HSS in several ways: providing each UE with a Fully Qualified Domain Name (FQDN) or an Internet Protocol (IP) address of the MTC-IWF entity in subscription data; or, providing an FQDN or an IP address of an MTC-IWF entity for each MTC Access Point Name (APN) in the subscription data; alternatively, the FQDN or IP address of the generic MTC-IWF entity is provided in the HSS.
In a second method, as shown in fig. 2, a User Equipment (UE) carries an MTC-AP PDU (Machine type communication Application-Packet Data Unit, Protocol Data Unit, MTC Application-Packet Data Unit, or Protocol Data Unit; Data Unit referring to MTC communication Application layer) in an Uplink Generic NAS Transport (Uplink _ Generic _ NAS _ Transport) message to send to an MME/SGSN, where the MTC-AP PDU includes an MTC header and MTC Data, and in the MTC header, the UE includes an internal identifier and a receive (receiver) field, the internal identifier is used to identify an identity of a UE sender, for example, an International Mobile Subscriber Identifier (IMSI) may be used as the internal identifier, and an MTC server identifier (MTC server id) is stored in the receiver field.
After receiving the Uplink _ Generic _ NAS _ Transport message, the MME/SGSN determines a proper MTC-IWF entity and then sends the MTC-AP PDU to the MTC-IWF entity through an MTCx interface, wherein the MTCx is an interface between the MME/SGSN and the MTC-IWF entity.
The MME/SGSN determines a proper MTC-IWF entity according to a local configuration or roaming agreement (roaming aggregation) or subscription data of the UE.
And the MTC-IWF entity analyzes the received MTC-AP PDU, obtains the MTCServer ID from the receiver domain and sends the MTC data to the corresponding MTC Server through the MTCSp interface. And, the MTC-IWF converts the internal identifier in the MTC header into an External identifier (External ID) of the UE, from which the service layer can identify the UE. The external Identifier of the UE is composed of a local Identifier (localdientifier) and a Domain Identifier (Domain ID), and the Domain Identifier represents a Domain (Domain) controlled by a Mobile Network Operator (MNO), and can be used to find the MTC-IWF entity. The local identity is assigned by the MNO and is unique within domain.
The UE herein refers to an intelligent terminal device or a general terminal device for MTC communication.
In summary, the first method does not discuss how the MTC-IWF entity determines the MTC Server receiving small data when the MTC-IWF entity is connected to a plurality of MTC servers; in the second method, the UE needs to know the MTC Server ID, and according to the method, the application layer of the UE is informed of the MTC Server ID provided by the application layer, but the method does not specifically describe how the application layer knows the MTC Server ID. Generally, the MTC Server ID may be obtained when the UE leaves the factory, but when the MTC Server communicating with the UE changes, the UE needs to be notified of the changed MTC Server ID, which may bring a large operation and maintenance workload and reduce flexibility of MTC service development.
Disclosure of Invention
The invention provides a method, equipment and a system for determining a target MTC server, which are used for simply and effectively determining the target MTC server for receiving data messages when an MTC-IWF entity is connected with a plurality of MTC servers.
The embodiment of the invention provides the following specific technical scheme:
a target MTC server determination method comprises the following steps:
network side equipment receives a data message of User Equipment (UE), wherein the data message contains identification information for determining a target Machine Type Communication (MTC) server;
and the network side equipment inquires the corresponding relation between the identification information and the identification or address of the MTC server and determines the identification or address of the MTC server corresponding to the identification information contained in the data message.
An uplink data transmission method includes:
user Equipment (UE) carries identification information for determining a target Machine Type Communication (MTC) server in a data message to be sent;
and the UE sends the data message to a network side.
A network-side device, comprising:
a receiving unit, configured to receive a data packet of a user equipment UE, where the data packet includes identification information for determining a target machine type communication MTC server;
and the determining unit is used for inquiring the corresponding relation between the identification information and the identification or address of the MTC server and determining the identification or address of the MTC server corresponding to the identification information contained in the data message.
A user equipment, comprising:
a message determining unit, configured to carry, in a data message to be sent, identification information for determining a target machine type communication MTC server;
and the sending unit is used for sending the data message to a network side.
A destination MTC server determination system, comprising:
the system comprises User Equipment (UE) and network side equipment, wherein the UE is used for sending a data message to the network side equipment, and the data message contains identification information for determining a target Machine Type Communication (MTC) server;
and the network side equipment is used for receiving the data message, inquiring the corresponding relation between the identification information and the identification or address of the MTC server, and determining the identification or address of the MTC server corresponding to the identification information contained in the data message.
Based on the technical scheme, in the embodiment of the invention, the identification information for determining the target MTC server is carried in the data message of the UE, and after the network side equipment receives the data message, the identification or address of the MTC server corresponding to the identification information contained in the data message is determined by inquiring the corresponding relation between the preset identification information and the identification or address of the MTC server, so that the target MTC server of the data message sent by the UE can be simply and effectively determined, and compared with the existing scheme, the resource overhead is effectively reduced.
Drawings
Fig. 1 is a flow chart of a first method for determining a transmission path in the prior art;
FIG. 2 is a flow chart of a second prior art delivery path method;
FIG. 3 is a flowchart of a method for determining a destination MTC server in an embodiment of the invention;
fig. 4 is a flowchart of an uplink small data transmission method in an embodiment of the present invention;
FIG. 5 is a schematic flow chart of a method according to a first embodiment of the present invention;
FIG. 6 is a schematic flow chart of a method according to a second embodiment of the present invention;
FIG. 7 is a schematic flow chart of a method according to a third embodiment of the present invention;
FIG. 8 is a schematic flow chart of a method according to a fourth embodiment of the present invention;
FIG. 9 is a schematic flow chart of a method according to a fifth embodiment of the present invention;
fig. 10 is a schematic structural diagram of a network-side device in an embodiment of the present invention;
fig. 11 is a schematic structural diagram of a ue in an embodiment of the present invention;
fig. 12 is a schematic diagram of a system for determining MTC server according to an embodiment of the invention.
Detailed Description
In order to simply and effectively determine a target MTC server for receiving a small data message when an MTC-IWF entity is connected with a plurality of MTC servers, and compared with the existing scheme, reduce resources occupied by the target MTC server and reduce overhead, the embodiment of the invention provides a method, equipment and a system for determining the target MTC server.
The following embodiments are given for the special case of small data packets, and can also be used for other data packets whose actual size is larger than the size of the small data packet. With the popularization of intelligent terminals, many applications on the intelligent terminals can also send the data messages related to the embodiment of the invention.
In the following embodiments, only a small data packet is taken as an example, but the present invention is not limited to the small data packet, and for other data packets, the method provided in the following embodiments may also be adopted, and the same technical effect can be achieved.
In practical applications, the MTC Server may be disposed in one physical device, or may be disposed in two separate physical devices, where when the MTC Server is disposed in the two separate physical devices, the two physical devices respectively correspond to an application Server and a Service Capability Server (SCS Server for short).
In this embodiment, when the target MTC server of the small data packet is determined, and the MTC server is set in one physical device, the target MTC server is the physical device; when the MTC server is disposed in two separate physical devices, the target MTC server is referred to as an SCS server, i.e., the identifier or address of the MTC server is determined as the identifier or address of the SCS server.
The server in the following embodiments is only an MTC server or an SCS server, but the present invention is not limited to the MTC server or the SCS server, and other servers may also use the method provided in the following embodiments and achieve the same technical effects.
Preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings.
As shown in fig. 3, in the embodiment of the present invention, a method for determining a destination MTC server is provided, which includes the following specific processes:
step 301: the network side equipment receives a small data message of the UE, wherein the small data message contains identification information used for determining a target MTC server.
The identification information for determining the destination MTC server includes, but is not limited to, any one of the following:
an external identity of the UE; a domain identity among external identities of the UE; a Port Number (Port Number for short) is a Number for distinguishing different upper layer applications; application identification (ApplicationID).
Preferably, the identification information for determining the destination MTC server is an external identification (ExternalID) of the UE or a Domain identification (Domain ID) among the external identifications of the UE.
The Port Number and the Application ID are used to identify and distinguish specific upper layer applications, and in this embodiment, may be used to determine a destination MTC server.
Step 302: and the network side equipment inquires the corresponding relation between the identification information and the identification or address of the MTC server and determines the identification or address of the MTC server corresponding to the identification information contained in the small data message.
Specifically, the network side device queries the correspondence between the identification information and the MTC server identification or address, and the following three specific implementations are provided:
the network side equipment inquires the corresponding relation between the identification information contained in the subscription data of the UE and the MTC server identification or address;
or,
the method comprises the steps that network side equipment inquires the corresponding relation between preset identification information in a Domain Name Server (DNS) and an MTC Server identification or address;
or,
and the network side equipment inquires the corresponding relation between the locally preset identification information and the MTC server identification or address.
The network side equipment queries the subscription data of the UE, where the network side equipment may send the identification information included in the small data message to the HSS, and the HSS queries a correspondence between the identification information included in the subscription data of the UE stored locally and an MTC server identifier or address; after the network side device obtains the subscription data of the UE from the HSS, the network side device may locally query the correspondence between the identifier information included in the subscription data of the UE and the MTC server identifier or address.
The network side equipment queries the corresponding relationship between the preset identification information in the DNS and the MTC server identification or address, where the network side equipment may send the identification information contained in the small data message to the DNS, and the DNS queries the corresponding relationship between the local preset identification information and the MTC server identification or address; or after the network side device obtains the corresponding relationship between the identification information and the MTC server identification or address from the DNS, the network side device may locally query the corresponding relationship.
In this embodiment, the network side device includes but is not limited to: any one of MME, serving General Packet Radio System (GPRS) support node (SGSN), MTC-IWF entity.
After the network side equipment determines the identifier or the address of the MTC server corresponding to the identifier information contained in the small data message, the network side equipment sends the small data message to the corresponding MTC server according to the determined identifier or address of the MTC server.
Specifically, if the network side device is an MME or SGSN, after the MME or SGSN determines the identifier or address of the MTC server corresponding to the identifier information included in the small data packet, there are two processing manners:
the MME or the SGSN directly sends the small data message to the corresponding MTC server according to the determined identification or address of the MTC server; or,
and the MME or the SGSN sends the determined identification or address of the MTC server to the MTC-IWF entity, and the MTC-IWF entity sends the small data message to the corresponding MTC server according to the determined identification or address of the MTC server.
Based on the same inventive concept, as shown in fig. 4, an embodiment of the present invention further provides an uplink small data sending method, which specifically includes the following steps:
step 401: the UE carries identification information for determining a target MTC server in a small data message to be sent.
The identification information for determining the destination MTC server includes, but is not limited to, any one of the following:
an external identity of the UE; a domain identity among external identities of the UE; a Port Number; application identification (Application ID).
Preferably, the identification information for determining the destination MTC server is an external identity of the UE or a domain identity in the external identity of the UE.
Step 402: and the UE sends the small data message to the network side.
After receiving the small data message of the UE, the network side device queries a correspondence between the identification information and an identification or address of the MTC server, and determines the identification or address of the MTC server corresponding to the identification information contained in the small data message.
In this embodiment, for specific implementation of the network side device, reference may be made to specific implementation of the network side device in the above-mentioned target MTC server determination method, and repeated details are not repeated.
The uplink small data transmission method and the method for determining the destination MTC server provided by the present invention are specifically described below by five specific embodiments.
When the identification information for determining the destination MTC server is any one of the above listed information, the method can be used in the following embodiments, and the implementation process is the same.
In the following embodiments, the correspondence between the identification information and the identification of the MTC server is taken as an example for explanation, and the application of the correspondence between the identification information and the IP address of the MTC server in the following embodiments is the same, except that the identification of the MTC server is determined instead of the IP address of the MTC server.
In the following embodiments one to four, the identification information for determining the target MTC server is an external identifier of the UE as an example.
In a first specific embodiment, as shown in fig. 5, in this specific embodiment, a specific process of transmitting a small data packet to a destination MTC server is as follows:
step 501: the UE sends a small data message to the MME through a non-access stratum (NAS) layer message, wherein the small data message comprises small data and an External ID of the UE.
Step 502: and the MME forwards the small data message to the MTC-IWF entity.
Step 503: and the MTC-IWF acquires the External ID from the small data message, sends the External ID to the HSS, and determines the MTC server identifier corresponding to the External ID contained in the small data message by the HSS according to the corresponding relation between the External ID contained in the subscription data of the UE and the MTC server identifier.
Step 504: and the HSS returns the determined MTC server identification to the MTC-IWF entity.
Step 505: and the MTC-IWF entity forwards the small data message to the MTC server corresponding to the determined MTC server identifier.
In a second specific embodiment, as shown in fig. 6, in this specific embodiment, a specific process of transmitting a small data packet to a destination MTC server is as follows:
step 601: and the UE sends a small data message to the MME through the NAS message, wherein the small data message comprises the small data and an External ID of the UE.
Step 602: the MME inquires subscription data of the UE, determines an MTC server identifier corresponding to an ExternalID contained in the small data message according to a corresponding relation between the ExternalID contained in the subscription data and the MTC server identifier, and sends the small data message and the determined MTC server identifier to the MTC-IWF entity.
Step 603: and the MTC-IWF entity forwards the small data message to the MTC server corresponding to the determined MTC server identifier.
The subscription Data of the UE obtained by the MME may be subscription Data that includes a correspondence between an External ID and an MTC server identifier in an Insertion Subscription Data (ISD) process of the HSS, and is sent to the MME.
In a third specific embodiment, as shown in fig. 7, in the specific embodiment, a specific process of transmitting a small data packet to a destination MTC server is as follows:
step 701: the UE sends a small data message to the MME through the NAS message, and the small data message comprises small data and an External ID of the UE.
Step 702: and the MME inquires the subscription data of the UE, determines an MTC server identifier corresponding to the ExternalID contained in the small data message according to the corresponding relation between the ExternalID contained in the subscription data and the MTC server identifier, and forwards the small data message to the MTC server corresponding to the determined MTC server identifier.
The subscription data of the UE obtained by the MME may be the subscription data that the HSS includes the correspondence between the ExternalID and the MTC server identifier in the ISD procedure and is sent to the MME.
In a fourth specific embodiment, as shown in fig. 8, a specific process of transmitting a small data packet to a destination MTC server is as follows:
step 801: the UE sends a small data message to the MME through the NAS message, and the small data message comprises small data and an External ID of the UE.
Step 802: and the MME sends the small data message to the MTC-IWF entity.
Step 803: the MTC-IWF entity acquires an External ID contained in the small data message and sends the External ID contained in the small data message to a DNS (domain name system) for DNS query; and the DNS determines the identifier of the MTC server corresponding to the External ID contained in the small data message according to the corresponding relation between the stored External ID and the identifier of the MTC server.
Step 804: and the DNS returns the determined identification of the MTC server to the MTC-IWF entity.
Step 805: and the MTC-IWF entity forwards the small data message to the MTC server corresponding to the determined MTC server identifier.
In a fifth embodiment, as shown in fig. 9, an example of determining that the identification information of the destination MTC server is an Application ID is described, in this embodiment, a specific process of transmitting a small data packet to the destination MTC server is as follows:
step 901: the UE sends a small data message to the MME through the NAS message, wherein the small data message comprises small data and Application IDs for distinguishing different upper-layer MTC applications, and the Application IDs can be indicated to a lower layer by an Application layer of the UE or can be added to the data message by the lower layer such as a non-access layer.
Step 902: and the MME sends the small data message to the MTC-IWF entity.
Step 903: and the MTC-IWF entity obtains the Application ID from the small data message and carries out DNS query, namely the Application ID is sent to the DNS, and the DNS determines the identification of the MTC server corresponding to the Application ID contained in the small data message according to the stored corresponding relation between the Application ID and the identification of the MTC server.
Step 904: and the DNS returns the determined identification of the MTC server to the MTC-IWF entity.
In step 903-.
Step 905: and the MTC-IWF entity sends the small data message to the MTC server corresponding to the determined identification of the MTC server.
Based on the same inventive concept, as shown in fig. 10, the embodiment of the present invention further provides a network side device, and for specific implementation thereof, reference may be made to the description of the network side device in the method for determining the target MTC server, repeated details are not repeated, and the network side device mainly includes the following units:
a receiving unit 1001, configured to receive a small data packet of a UE, where the small data packet includes identification information for determining a target MTC server;
the determining unit 1002 is configured to query a correspondence between the identification information and an identification or address of the MTC server, and determine the identification or address of the MTC server corresponding to the identification information contained in the small data message.
Wherein the determining unit is specifically configured to:
inquiring the corresponding relation between identification information contained in the subscription data of the UE and an MTC server identification or address; or inquiring the corresponding relation between the preset identification information in the domain name service DNS and the MTC server identification or address; or inquiring the corresponding relation between the identification information locally preset by the network side equipment and the MTC server identification or address.
Specifically, the network side device may be a mobility management entity MME, SGSN or MTC-IWF entity.
In a specific implementation, the network-side device further includes: a sending unit 1003, configured to send the small data message to a corresponding MTC server according to the determined identifier or address of the MTC server.
In another specific implementation, the network-side device further includes: a sending unit 1003, configured to send the determined identifier or address of the MTC server to the MTC-IWF entity, where the MTC-IWF entity sends the small data message to the corresponding MTC server according to the determined identifier or address of the MTC server.
Based on the same inventive concept, as shown in fig. 11, an embodiment of the present invention further provides a user equipment, where specific implementation of the user equipment may refer to specific implementation of the UE in the uplink small data transmission method, and repeated parts are not described again, and the user equipment mainly includes the following units:
a message determining unit 1101, configured to carry, in a small data message to be sent, identification information for determining a destination MTC server;
a sending unit 1102, configured to send the small data packet to a network side.
Based on the same inventive concept, as shown in fig. 12, an embodiment of the present invention further provides a target MTC server determination system, and specific implementation of the system may refer to specific implementation of the above uplink small data transmission method and method for determining a target MTC server, and repeated details are not repeated, where the system mainly includes a UE1201 and a network side device 1202, where,
the UE1201 is configured to send a small data packet to a network side, where the small data packet includes identification information for determining a destination MTC server;
the network side device 1202 is configured to receive the small data packet, query a corresponding relationship between the identification information and an identification or address of the MTC server, and determine the identification or address of the MTC server corresponding to the identification information included in the small data packet.
Based on the technical scheme, in the embodiment of the invention, the identification information for determining the target MTC server is carried in the data message of the UE, and after the network side equipment receives the data message, the identification or address of the MTC server corresponding to the identification information contained in the data message is determined by inquiring the corresponding relation between the preset identification information and the identification or address of the MTC server, so that the target MTC server of the data message sent by the UE can be simply and effectively determined, and compared with the existing scheme, the resource overhead is effectively reduced.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (15)
1. A target MTC server determination method is characterized by comprising the following steps:
network side equipment receives a data message of User Equipment (UE), wherein the data message contains identification information for determining a target Machine Type Communication (MTC) server;
and the network side equipment inquires the corresponding relation between the identification information and the identification or address of the MTC server and determines the identification or address of the MTC server corresponding to the identification information contained in the data message.
2. The method of claim 1, wherein the identification information includes, but is not limited to, any of:
an external identity of the UE;
a domain identity among external identities of the UE;
port Number is Port Number;
the Application identifies the Application ID.
3. The method according to claim 2, wherein the network side device querying the correspondence between the identification information and the MTC server identification or address specifically includes:
the network side equipment inquires the corresponding relation between the identification information contained in the subscription data of the UE and the MTC server identification or address;
or,
the method comprises the steps that network side equipment inquires the corresponding relation between preset identification information in a Domain Name Service (DNS) and an MTC server identification or address;
or,
and the network side equipment inquires the corresponding relation between the locally preset identification information and the MTC server identification or address.
4. The method of claim 3, wherein the network-side device is a Mobility Management Entity (MME), a serving general packet radio system support node (SGSN), or a machine type communication interworking function (MTC-IWF) entity.
5. The method of claim 4, wherein if the network side device is an MME or an SGSN, after the network side device determines an identifier or an address of an MTC server corresponding to the identifier information included in the data packet, the method further comprises:
and the MME or the SGSN sends the determined identification or address of the MTC server to the MTC-IWF entity, and the MTC-IWF entity sends the data message to the corresponding MTC server according to the determined identification or address of the MTC server.
6. The method according to claim 4, wherein after the network side device determines the identifier or the address of the MTC server corresponding to the identifier information contained in the data packet, the method further includes:
and the network side equipment sends the data message to the corresponding MTC server according to the determined identification or address of the MTC server.
7. An uplink data transmission method, comprising:
user Equipment (UE) carries identification information for determining a target Machine Type Communication (MTC) server in a data message to be sent;
and the UE sends the data message to a network side.
8. The method of claim 7, wherein the identification information includes, but is not limited to, any of:
an external identity of the UE;
a domain identity among external identities of the UE;
port Number is Port Number;
the Application identifies the Application ID.
9. A network-side device, comprising:
a receiving unit, configured to receive a data packet of a user equipment UE, where the data packet includes identification information for determining a target machine type communication MTC server;
and the determining unit is used for inquiring the corresponding relation between the identification information and the identification or address of the MTC server and determining the identification or address of the MTC server corresponding to the identification information contained in the data message.
10. The network-side device of claim 9, wherein the determining unit is specifically configured to:
inquiring the corresponding relation between identification information contained in the subscription data of the UE and an MTC server identification or address;
or,
inquiring the corresponding relation between the preset identification information in the domain name service DNS and the MTC server identification or address;
or,
and inquiring the corresponding relation between the identification information locally preset by the network side equipment and the MTC server identification or address.
11. The network-side device of claim 10, wherein the network-side device is a Mobility Management Entity (MME), an SGSN, or a machine type communication interworking function (MTC-IWF) entity.
12. The network-side device of claim 11, further comprising: and the sending unit is used for sending the data message to the corresponding MTC server according to the determined identification or address of the MTC server.
13. The network-side device of claim 11, further comprising: and the sending unit is used for sending the determined identification or address of the MTC server to the MTC-IWF entity, and the MTC-IWF entity sends the data message to the corresponding MTC server according to the determined identification or address of the MTC server.
14. A user device, comprising:
a message determining unit, configured to carry, in a data message to be sent, identification information for determining a target machine type communication MTC server;
and the sending unit is used for sending the data message to a network side.
15. A destination MTC server determination system, comprising:
the system comprises User Equipment (UE) and a network side, wherein the UE is used for sending a data message to the network side, and the data message contains identification information for determining a target Machine Type Communication (MTC) server;
and the network side equipment is used for receiving the data message, inquiring the corresponding relation between the identification information and the identification or address of the MTC server, and determining the identification or address of the MTC server corresponding to the identification information contained in the data message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210277414.XA CN103581892A (en) | 2012-08-06 | 2012-08-06 | Purpose MTC server determining method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210277414.XA CN103581892A (en) | 2012-08-06 | 2012-08-06 | Purpose MTC server determining method, device and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN103581892A true CN103581892A (en) | 2014-02-12 |
Family
ID=50052618
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210277414.XA Pending CN103581892A (en) | 2012-08-06 | 2012-08-06 | Purpose MTC server determining method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103581892A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017162073A1 (en) * | 2016-03-25 | 2017-09-28 | 阿里巴巴集团控股有限公司 | Data duplication elimination method and device |
| WO2018049690A1 (en) * | 2016-09-19 | 2018-03-22 | 华为技术有限公司 | Packet transmission method, apparatus and system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102202270A (en) * | 2010-03-24 | 2011-09-28 | 中兴通讯股份有限公司 | Machine type communication (MTC)-based message transmission method and interworking functional entity |
| CN102238520A (en) * | 2010-04-26 | 2011-11-09 | 中兴通讯股份有限公司 | Method and system for transmitting small data packets |
| WO2011141834A1 (en) * | 2010-05-10 | 2011-11-17 | Telefonaktiebolaget L M Ericsson (Publ) | Reducing protocol overhead in single-block packet access procedures |
| CN102413457A (en) * | 2010-09-20 | 2012-04-11 | 中兴通讯股份有限公司 | Uplink data message sending method and device |
-
2012
- 2012-08-06 CN CN201210277414.XA patent/CN103581892A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102202270A (en) * | 2010-03-24 | 2011-09-28 | 中兴通讯股份有限公司 | Machine type communication (MTC)-based message transmission method and interworking functional entity |
| CN102238520A (en) * | 2010-04-26 | 2011-11-09 | 中兴通讯股份有限公司 | Method and system for transmitting small data packets |
| WO2011141834A1 (en) * | 2010-05-10 | 2011-11-17 | Telefonaktiebolaget L M Ericsson (Publ) | Reducing protocol overhead in single-block packet access procedures |
| CN102413457A (en) * | 2010-09-20 | 2012-04-11 | 中兴通讯股份有限公司 | Uplink data message sending method and device |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017162073A1 (en) * | 2016-03-25 | 2017-09-28 | 阿里巴巴集团控股有限公司 | Data duplication elimination method and device |
| CN107229660A (en) * | 2016-03-25 | 2017-10-03 | 阿里巴巴集团控股有限公司 | A kind of method and apparatus of data deduplication |
| WO2018049690A1 (en) * | 2016-09-19 | 2018-03-22 | 华为技术有限公司 | Packet transmission method, apparatus and system |
| CN109196895A (en) * | 2016-09-19 | 2019-01-11 | 华为技术有限公司 | A kind of message transmitting method, apparatus and system |
| CN109196895B (en) * | 2016-09-19 | 2020-07-21 | 华为技术有限公司 | Message transmission method, device and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN115460686B (en) | Base station, access and mobility management functional entity and method thereof | |
| CN109997334B (en) | Session management with relaying and charging for indirect connectivity of internet of things applications in 3GPP networks | |
| CN109863789B (en) | Method and apparatus for connecting terminal to network based on applicable network information in mobile communication system | |
| FI127414B (en) | Apparatus and method to efficiently send device trigger messages | |
| US9107025B2 (en) | Node and method for communications handling | |
| CN106576217B (en) | Application data delivery service for networks supporting multiple transport mechanisms | |
| CN112637947B (en) | Base station, access and mobility management functional entity and method thereof | |
| US11388580B2 (en) | Method for transferring signaling messages of terminal between network functions | |
| CN102413453B (en) | A kind of shared method and system of MTC device Subscriber Number | |
| CN103731902A (en) | Method and device for inquiring direct connection communication target terminal information | |
| CN102547658B (en) | Method and device for transmitting data | |
| WO2014005551A1 (en) | Ue configuration method, network side device and system for proximity awareness | |
| EP2884779B1 (en) | Message processing method in coexistence of multiple external identifiers of terminal and network side device | |
| US20160157045A1 (en) | Method and apparatus for sending or forwarding information | |
| CN113491148A (en) | Method and apparatus for supporting event monitoring | |
| CN102158828B (en) | Short message processing method and equipment | |
| CN103581892A (en) | Purpose MTC server determining method, device and system | |
| CN102625277B (en) | Data sending method, apparatus, terminal and system thereof | |
| CN102348176B (en) | Short message sending method and device | |
| CN105210401A (en) | ProSe information transmission method, terminals, and communications device | |
| CN103546884B (en) | Machine type communication system, and method and devices for transmitting data of machine type communication system | |
| KR20180062728A (en) | Method and apparatus for transmitting group messages based on nb-iot | |
| KR20130139160A (en) | An apparatus and method for delivering messages to a plurality of devices in mobile communication networks |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20140212 |