(divisional application of invention application No. 201010170193.7 filed 5/2010)
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
FIG. 1 is a network architecture diagram of SAE applicable to the embodiment of the present invention, as shown in FIG. 1, a Mobility Management Entity (MME) 11 is located in a core network and is responsible for Mobility Management, and functions of the MME include bearer control of the core network; a Serving Gateway (SGW) 12 is responsible for User Equipment (User Equipment, UE) User plane data transmission, forwarding, route switching, and the like; a Packet Data Network (PDN) Gateway (PGW) 13 is mainly responsible for connecting to a PDN Network, allocating an IP address to a user, and the like; a Policy and charging rules Function (Policy and charging rules Function, PCRF)14 is responsible for generating Policy and charging rules information for bearer establishment according to the subscription information of the user, the IP-Connectivity Access Network (IP-CAN) type, the IP-CAN capability, and other information. Since SAE is an all-IP network, PGW13 is responsible for allocating a network-wide routable public network IP address, which may be an IPv4 address, to a terminal device attached to the network; in addition, the public network IP address in the embodiment of the present invention may specifically be a network-wide routable IP address allocated by a gateway device in the Internet (Internet) to a terminal device attached to the Internet (Internet), and the private network IP address in the embodiment of the present invention may specifically be an IP address used for identifying a terminal device in a local area network and being unable to perform routing on the Internet (Internet).
Fig. 2 is a schematic flow chart of an embodiment of a data transmission method of the present invention, and as shown in fig. 2, the embodiment of the present invention includes the following steps:
step 201, after the terminal device is attached to the network, the terminal device sends a private network IP address of the terminal device and an IP address of the gateway device to the network side server, wherein the IP address of the gateway device is obtained by the terminal device through the attachment acceptance message, and the gateway device is a gateway device in the network to which the terminal device is attached;
step 202, the terminal device receives data information transmitted by the network side server according to the private network IP address and the IP address of the gateway device.
In the data transmission method provided by the embodiment of the invention, the terminal device sends the private network IP address of the terminal device and the IP address of the gateway device to the network side server, so that the network side server transmits data information to the terminal device according to the private network IP address of the terminal device and the IP address of the gateway device, and the gateway device is not required to distribute the public network IP address of the terminal device to the terminal device, thereby reducing the influence on the existing public network IP address when the terminal device and the network side server transmit data.
Further, on the basis of the embodiment shown in fig. 2, the terminal device may receive an attach accept message sent by the MME after the MME determines that the terminal device is a machine type communication device, where the attach accept message includes an IP address of the gateway device; further, the MME determines that the terminal device is an MTC device according to the subscription information from the home subscriber server.
Further, on the basis of the embodiment shown in fig. 2, step 202 may specifically be: when a network side server needs to transmit data information to the terminal equipment, the terminal equipment receives the data information which is sent to the gateway equipment by the network side server according to the IP address of the gateway equipment and forwarded to the terminal equipment by the gateway equipment according to the private network IP address.
Further, on the basis of the embodiment shown in fig. 2, if the terminal device further sends an instruction for transmitting data information in a tunnel manner to the network side server, the network side server communicates with the gateway device according to the instruction, and then the gateway device transmits the data information to the terminal device; specifically, the tunnel mode may be, for example: an IP nesting IP (IP in IP) mode, a User data packet Tunnel (UDP Tunnel) mode, and the like.
Further, in the embodiment shown in fig. 2, the gateway device may specifically be a PGW in the network, and may also be an NAT gateway existing in the network.
Fig. 3 is a schematic flow chart of a data transmission method according to another embodiment of the present invention, and as shown in fig. 3, the embodiment of the present invention includes the following steps:
301, a machine type communication server acquires a private network IP address of a terminal device and an IP address of a gateway device, wherein the gateway device is a gateway device in a network attached to the terminal device;
and step 302, the machine type communication server transmits data information to the terminal equipment according to the private network IP address and the IP address of the gateway equipment.
According to the data transmission method provided by the embodiment of the invention, the machine type communication server transmits the data information to the terminal equipment according to the private network IP address of the terminal equipment and the IP address of the gateway equipment, and the gateway equipment is not required to distribute the public network IP address of the terminal equipment to the terminal equipment, so that the influence on the existing public network IP address when the terminal equipment and the network side server transmit data is reduced.
Further, on the basis of the above-mentioned embodiment shown in fig. 3, step 301 may include the following processes by:
the machine type communication server receives the private network IP address of the terminal equipment and the IP address of the gateway equipment, which are sent by the terminal equipment; or,
the machine type communication server sends a request message to a machine type communication gateway or a domain name server, and the request message is used for requesting to acquire the private network IP address of the terminal equipment and the IP address of the gateway equipment;
and the machine type communication server receives the private network IP address of the terminal equipment and the IP address of the gateway equipment returned by the machine type communication gateway equipment or the domain name server according to the request message.
Further, on the basis of the embodiment shown in fig. 3, the method further includes: if the machine type communication server further obtains an instruction from the terminal device to transmit the data information in a tunnel manner, step 302 may specifically be: and the network side server communicates with the gateway equipment through a tunnel according to the private network IP address and the IP of the gateway equipment, and the gateway equipment further transmits the data information with the terminal equipment according to the private network IP address.
Further, in the embodiment shown in fig. 3, the gateway device may specifically be a PGW in the network, and may also be an NAT gateway existing in the network.
Fig. 4 is a flowchart illustrating an address obtaining method according to an embodiment of the present invention, and as shown in fig. 4, a terminal device in the embodiment of the present invention may specifically be an MTC device; the embodiment of the invention comprises the following steps:
step 401, an address acquisition server receives a private network IP address of a terminal device sent by the terminal device;
step 402, the address acquisition server sends a request containing a private network IP address to the gateway device according to the request sent by the MTC server, so that the gateway device distributes a public network IP address and a port number to the terminal device according to the request containing the private network IP address; the gateway equipment is the gateway equipment in the network attached to the terminal equipment;
and step 403, the address acquisition server sends the acquired public network IP address and port number to the machine type communication server, so that the machine type communication server transmits data information to the terminal device according to the public network IP address.
According to the address acquisition method provided by the embodiment of the invention, the address acquisition server acquires the public network IP address and the port number of the terminal equipment from the gateway equipment according to the request of acquiring the public network IP address of the terminal equipment from the machine type communication server, so that the machine type communication server can dynamically acquire the public network IP address of the terminal equipment, and the influence on the existing public network IP address when the terminal equipment and the machine type communication server transmit data is reduced.
Further, on the basis of the above-mentioned embodiment shown in fig. 4, step 402 may include the following processes:
the address acquisition server receives a request containing a Fully Qualified Domain Name (FQDN) of the MTC equipment from a machine type communication server, and is used for requesting to acquire a public network IP address and a port number of the terminal equipment;
the address acquisition server inquires the full-name domain name of the terminal equipment so as to acquire the IP address of the gateway equipment, and sends a request containing the private network IP address to the gateway equipment according to the IP address of the gateway equipment, so that the gateway equipment allocates the public network IP address and the port number of the terminal equipment to the terminal equipment according to the private network IP address.
Further, in the embodiment shown in fig. 4, the gateway device may specifically be a PGW in a network, and may also be an NAT gateway existing in the network; the location acquisition server may specifically be an MTC gateway/DNS.
In order to more clearly describe the technical solution of the embodiment of the present invention, the embodiment of the present invention is described in detail below with reference to fig. 5 to 7.
Fig. 5 is a signaling flow chart applicable to the embodiment of the present invention, and as shown in fig. 5, in the embodiment, an example is taken to illustrate that a terminal device is specifically an MTC device, a gateway device is specifically a PGW/NAT, and a network side server is specifically an MTC server; the embodiment of the invention comprises the following steps:
step 501, the MTC device initiates an attach request message to the MME, where the attach request message may specifically be an SAE network attach request message;
step 502, the MME authenticates the attach request message, and the specific authentication process may refer to a related protocol in the prior art, which is not described herein again;
step 503, the MME initiates a location update request message to a Home Subscriber Server (HSS) or an Authentication, Authorization, and Accounting (AAA) Server;
step 504, the HSS/AAA returns a location update response message to the MME, where the location update response message includes subscription information of the MTC device, where the subscription information includes an MTC attribute supported by the MTC device, and may also include a Full Qualified Domain Name (FQDN) of the MTC device, where the MTC attribute specifically may include at least one or any combination of small data volume, low mobility, and regularity of time control when the MTC device communicates, but the MTC attribute is not limited to the above-mentioned list, and as long as the characteristic that the MTC device itself has to be distinguished from other terminal devices is the MTC attribute described in this embodiment;
step 505, the MME initiates a default bearer (default bearer) establishment request to the PGW;
step 506, after receiving the default bearer request, the PGW establishes default bearer (default bearer) context information; optionally, if there is a separate NAT gateway in the network, the PGW may further obtain an IP address of the NAT gateway; the PGW returns a response for establishing the default bearer to the MME, wherein the response for establishing the default bearer comprises the private network IP address of the terminal equipment and the IP address of the PGW, and further, if an independent NAT gateway exists in the network, the PGW can also carry the IP address of the NAT gateway in the response for establishing the default bearer;
step 507, the MME determines that the terminal Device is an MTC Device (Device) according to the subscription information returned by the HSS and the response message returned by the PGW;
for example: the MME can judge that the terminal equipment is the MTC equipment according to the description that the subscription information returned by the HSS contains the MTC characteristics, and/or judge that the terminal equipment is the MTC equipment according to the FQDN of the terminal contained in the subscription information returned by the HSS;
step 508, the MME sends an Attach Accept (Attach Accept) message to the terminal device, where the Attach Accept message includes the IP address of the gateway device; further, if the network has the NAT gateway, the IP address of the NAT gateway may also be included;
specifically, the bearer context request may be carried by expanding an Evolved Session Management (ESM) message container Information Element (message container Information Element) of an Attach Accept (Attach Accept) message, where the message container Information Element (message container Information Element) activates a default Evolved Packet System (activated Evolved Packet System), and the specific expansion manner may be: an information element is added on the basis of a message body of a context request carried by an existing activated default evolution data packet system, wherein the information element can be specifically a PGW/NAT address (PGW/NAT address), the type of the information element is specifically a PGW/NAT IP address (address), and the information element is optional and has the length of 6-14 bytes.
Step 509, the MTC Device sends a first data packet containing the FQDN, private network IP address and PGW IP address of the MTC Device (Device) to the MTC Server (Server); optionally, the first data packet may further include an indication that the terminal device instructs the MTC server to transmit data information to the terminal device in a Tunnel (Tunnel) manner (e.g., UDP Tunnel, IP in IP), and specifically, the first data packet includes a message body with a special format, for example: the message body with the special format may be a message body with a fixed beginning of an IP Address Update field (IP Address Update) at the beginning of the message body to inform an MTC Server (Server) that the purpose of the first packet is to Update Address information; in addition, the MTC Server (Server) stores the first data packet after receiving the first data packet sent by the MTC Device (Device).
Step 510, when the MTC server needs to transmit data information with the MTC equipment, the MTC server transmits the data information according to the IP address of the PGW/NAT and the PGW/NAT;
specifically, when the MTC Server (Server) needs to transmit data information to the MTC Device (Device), the MTC Server (Server) may transmit the data information to the PGW through a Tunnel (Tunnel), for example: if the data information is transmitted by a User Datagram Protocol (UDP), the tunnel mode may specifically be: the external IP address of the UDP data packet is the IP address of the PGW or the NAT, and the internal IP address of the UDP data packet is the private network IP address of the MTC Device; the above description is only an example and should not be construed as limiting the embodiments of the present invention.
Step 511, the PGW/NAT transmits the data information with the terminal according to the IP address of the private network;
for example: corresponding to the example of step 510, after receiving the UDP packet sent by the MTC server, the PGW/NAT extracts the private network IP address of the UDP packet, and transmits the data information to the MTC Device (Device) according to the private network IP address in the normal procedure.
According to the data transmission method provided by the embodiment of the invention, the terminal equipment sends the first data packet after being attached to the network, and the first data packet comprises the private network IP address of the terminal equipment and the IP address of the PGW/NAT, so that the MTC server can transmit data information to the terminal equipment according to the private network IP address of the terminal equipment and the IP address of the PGW/NAT, and the influence on the existing public network IP address when the terminal equipment and the MTC server transmit the data information is reduced because the PGW is not required to distribute the public network IP address of the terminal equipment to the terminal equipment; further, if the network has the NAT gateway, the NAT gateway is not required to establish an IP address mapping table for the MTC Device (Device), so that the function of the NAT gateway is simplified, the MTC Device (Device) does not need to maintain the public network IP address and port number obtained from the NAT gateway, and the waste of network resources and the consumption of battery power of the MTC Device (Device) are avoided.
Fig. 6 is another signaling flowchart applicable to the embodiment of the present invention, as shown in fig. 6, the embodiment of the present invention further includes: the terminal device is specifically an MTC device, the gateway device is specifically a PGW/NAT, and the network side server comprises an MTC gateway/DNS and an MTC server for exemplary explanation; the embodiment of the invention comprises the following steps:
the embodiment of the invention comprises the following steps:
step 601, the MTC device initiates an attach request message to the MME, where the attach request message may specifically be an EPS network attach request message.
Step 602, the MME authenticates the attach request message, and the specific authentication process may refer to a related protocol in the prior art, which is not described herein again;
step 603, the MME initiates a location update request message to HSS or AAA;
step 604, the HSS/AAA returns a location update response message to the MME, where the location update response message includes subscription information of the MTC device, where the subscription information includes an MTC attribute supported by the MTC device, and may also include an FQDN of the MTC device, where the MTC attribute may specifically include at least one or any combination of small data volume, low mobility, and regularity of time control when the MTC device communicates, but the MTC attribute is not limited to the above list, and as long as the MTC device itself has a characteristic different from other terminal devices, the characteristic is the MTC attribute described in this embodiment;
step 605, the MME initiates a default bearer (default bearer) establishment request to the PGW/NAT;
step 606, after receiving the default bearer request, the PGW/NAT establishes default bearer (default bearer) context information; optionally, if there is a separate NAT gateway in the network, the PGW may further obtain an IP address of the NAT gateway; the PGW returns a response for establishing the default bearer to the MME, wherein the response for establishing the default bearer comprises the private network IP address of the terminal equipment and the IP address of the PGW, and further, if an independent NAT gateway exists in the network, the PGW can also carry the IP address of the NAT gateway in the response for establishing the default bearer;
step 607, the MME determines that the terminal Device is an MTC Device (Device) according to the subscription information returned by the HSS/AAA and the response message returned by the PGW/NAT;
for example: the MME can judge that the terminal equipment is the MTC equipment according to the description that the subscription information returned by the HSS contains the MTC characteristics, and/or judge that the terminal equipment is the MTC equipment according to the FQDN of the terminal contained in the subscription information returned by the HSS;
step 608, the MME sends an Attach Accept (Attach Accept) message to the terminal device, where the Attach Accept message includes the IP address of the PGW; further, if the network has the NAT gateway, the IP address of the NAT gateway may also be included;
specifically, the bearer context request may be carried by expanding an Evolved Session Management (ESM) message container Information Element (message container Information Element) of an Attach Accept (Attach Accept) message, where the message container Information Element (message container Information Element) activates a default Evolved Packet System (activated Evolved Packet System), and the specific expansion manner may be: an information element is added on the basis of a message body of a context request carried by an existing activated default evolution data packet system, wherein the information element can be specifically a PGW/NAT address (PGW/NAT address), the type of the information element is specifically a PGW/NAT IP address (address), and the information element is optional and has the length of 6-14 bytes.
Step 609, the MTC Device sends a first data packet to an MTC Gateway/domain name server (MTC Gateway/DNS), where the first data packet includes the FQDN, the private network IP address, and the IP address of the PGW/NAT of the MTC Device (Device); an MTC Gateway/domain name server (MTC Gateway/DNS) stores the FQDN, the private network IP address and the IP address of the PGW which are contained in the first data packet; further, the first data packet may be a DNS update message; in addition, if a NAT gateway exists in the network, the first packet may further include an IP address of the NAT gateway.
Step 610, when the MTC Server (Server) needs to transmit data information to the MTC Device (Device), the MTC Server (Server) sends a first request message to an MTC gateway/domain name Server (mtcgaveway/DNS), where the first request message includes the FQDN of the MTC Device (Device);
step 611, the MTC Gateway/domain name server (MTC Gateway/DNS) returns a first response message to the MTC server, where the first response message includes a private network IP address of the MTC Device (Device) and an IP address of the PGW, and if there is a NAT Gateway in the network, the first response message may also include the IP address of the NAT Gateway.
Step 612, when the MTC Server (Server) transmits data information to the MTC Device (Device), the MTC Server (Server) sends the data information to the PGW/NAT through a tunnel mode (UDP tunnel), where the data information may specifically be a UDP packet, and the tunnel mode may specifically be: the external IP address of the UDP packet is the IP address of the PGW or NAT, and the internal IP address of the UDP packet is the private network IP address of the MTC Device.
Step 613, after receiving the data information, the PGW or the NAT extracts a PDU packet inside the UDP packet, and sends the data information to the MTC Device (Device) according to a normal flow.
The step 612 and the step 611 are only an exemplary description, and are all implementation manners described in the embodiment of the present invention as long as the MTC server sends the data information to the PGW/NAT through the IP address of the PGW/NAT and the PGW/NAT forwards the data information to the MTC device according to the private network IP address of the MTC device.
According to the data transmission method provided by the embodiment of the invention, the terminal equipment sends the first data packet after being attached to the network, and the first data packet comprises the IP address of the gateway equipment attached to the private network IP address of the terminal equipment, so that the MTC server transmits data information to the terminal equipment according to the private network IP address of the terminal equipment and the IP address of the gateway equipment attached to the terminal equipment; moreover, the NAT does not need to establish an IP address mapping table for the MTCD device, thereby simplifying the NAT gateway function; in addition, the MTC Device does not need to maintain the public network IP address and the public network port number obtained from the NAT, and the waste of network resources and the consumption of the battery capacity of the MTC Device are avoided.
Fig. 7 is a further signaling flow chart applicable to the embodiment of the present invention, as shown in fig. 7, the embodiment of the present invention further includes: the terminal device is specifically an MTC device, the gateway device is specifically a PGW/NAT, and the network side server comprises an MTC gateway/DNS and an MTC server for exemplary explanation; the embodiment of the invention comprises the following steps:
step 701, the MTC device initiates an attach request message to the MME, where the attach request message may specifically be an EPS network attach request message.
Step 702, the MME authenticates the attach request message, and the specific authentication process may refer to the related protocol in the prior art, which is not described herein again;
step 703, the MME initiates a location update request message to HSS or AAA;
step 704, the HSS/AAA returns a location update response message to the MME, where the location update response message includes subscription information of the MTC device, where the subscription information includes an MTC attribute supported by the MTC device, and may also include an FQDN of the MTC device, where the MTC attribute may specifically include at least one or any combination of small data volume, low mobility, and regularity of time control when the MTC device communicates, but the MTC attribute is not limited to the above list, and as long as the MTC device itself has a characteristic different from other terminal devices, the characteristic is the MTC attribute described in this embodiment;
step 705, the MME initiates a default bearer (default bearer) establishment request to the PGW;
step 706, after receiving the default bearer request, the PGW establishes default bearer (default bearer) context information; optionally, if there is a separate NAT gateway in the network, the PGW may further obtain an IP address of the NAT gateway; the PGW returns a response for establishing the default bearer to the MME, wherein the response for establishing the default bearer comprises the private network IP address of the terminal equipment and the IP address of the PGW, and further, if an independent NAT gateway exists in the network, the PGW can also carry the IP address of the NAT gateway in the response for establishing the default bearer;
step 707, the MME determines that the terminal Device is an MTC Device (Device) according to the subscription information returned by the HSS/AAA and the response message returned by the PGW;
for example: the MME can judge that the terminal equipment is the MTC equipment according to the description that the subscription information returned by the HSS contains the MTC characteristics, and/or judge that the terminal equipment is the MTC equipment according to the FQDN of the terminal contained in the subscription information returned by the HSS;
step 708, the MME sends an Attach Accept (Attach Accept) message to the MTC device, where the Attach Accept message includes the IP address of the gateway device; further, if there is a NAT gateway in the network, the network may also include an IP address of the NAT;
specifically, the bearer context request (bearer context request) of the default Evolved Packet System (activated default Evolved Packet System) may be activated to be carried by expanding an Evolved Session Management (ESM) message container Information Element (message container Information Element) of an Attach Accept (Attach Accept) message, where the specific expansion manner may be: an information element is added on the basis of a message body of a context request carried by an existing activated default evolution data packet system, wherein the information element can be specifically a PGW/NAT address (PGW/NAT address), the type of the information element is specifically a PGW/NAT IP address (address), and the information element is optional and has the length of 6-14 bytes.
Step 709, the MTC Device sends an update message to the MTC gateway/DNS, where the update message includes the FQDN, private network IP address and PGW IP address of the MTC Device (Device); further, the update message may be a DNS update message; in addition, if a NAT gateway exists in the network, the update message may further include an IP address of the NAT gateway.
Step 710, when the MTC Server (Server) needs to transmit data information to the MTC Device (Device), the MTC Server (Server) sends a request message to the MTC gateway/DNS, where the request message includes FQDN, which is used to request to acquire a public network IP address of the MTC Device (Device);
step 711, the MTC gateway/DNS searches for an IP address of a PGW or NAT attached to the MTC Device (Device) according to the FQDN, and sends a dynamic request message to the PGW or NAT, where the dynamic request message is used to request a public network IP address of the MTC Device (Device), and the dynamic request message includes a private network IP address of the MTC Device (Device);
step 712, the PGW finds the MTC Device (Device) according to the private network IP address of the MTC Device (Device), dynamically allocates a corresponding public network IP address and port number to the MTC Device (Device), and sends the public network IP address and port number of the MTC Device to the MTC gateway/DNS;
step 713, the MTC gateway/DNS returns the public network IP address and port number of the MTC Device (Device) to the MTC Server (Server);
step 714, the MTC Server (Server) sends data information to the public network IP address of the MTC Device (Device), and routes the data information to the PGW or the NAT gateway according to the public network IP address of the MTC Device;
and 715, after receiving the data information, the PGW/NAT maps the public network IP address and the port number of the MTC Device (Device) into a private network IP address and a port number according to a normal NAT process, and sends the data information to the MTC Device according to the private network IP address.
According to the data transmission method provided by the embodiment of the invention, after the server acquires the private network IP address of the terminal equipment and the IP address of the PGW or NAT, the public network IP address of the MTC equipment is dynamically acquired from the SGW/PGW according to the private network IP address of the terminal equipment and the IP address of the PGW or NAT, and the MTC equipment does not fixedly occupy the public network IP address allocated by the gateway equipment any more, but is dynamically allocated by the gateway equipment when data transmission is required, so that the influence on the existing public network IP address when the terminal equipment and the server transmit data is reduced.
Fig. 8 is a schematic structural diagram of an embodiment of a terminal device of the present invention, and as shown in fig. 8, the terminal device in the embodiment of the present invention may specifically be an MTC device, and the embodiment of the present invention may implement the method flow in the embodiment shown in fig. 2 and the signaling flow in the embodiment shown in fig. 5; the embodiment comprises the following steps: a transmitting module 81 and a receiving module 82;
the sending module 81 sends a private network internet protocol IP address of the terminal device and an IP address of a gateway device to a network side server after the terminal device is attached to a network, wherein the IP address of the gateway device is obtained by the terminal device through an attachment acceptance message, and the gateway device is a gateway device in the network to which the terminal device is attached; the receiving module 82 receives data information transmitted by the network side server according to the private network IP address and the IP address of the gateway device.
In the terminal device provided in the embodiment of the present invention, since the receiving module 82 sends the private network IP address of the terminal device and the IP address of the gateway device to the network-side server, the network-side server transmits data information to the terminal device according to the private network IP address of the terminal device and the IP address of the gateway device, and since the gateway device is no longer required to allocate the public network IP address of the terminal device to the terminal device, the influence on the existing public network IP address when the terminal device and the network-side server transmit data is reduced.
Further, on the basis of the embodiment shown in fig. 8, the receiving module 82 is further configured to receive, by the terminal device, the attach accept message sent by the mobility management entity after the mobility management entity determines that the terminal device is a machine type communication device.
Further, on the basis of the embodiment shown in fig. 8, the sending module 81 is further configured to send an instruction for transmitting the data information in a tunnel manner to the network side server, so that the network side server communicates with the gateway device in a tunnel manner according to the private network IP address and the IP address of the gateway device, and the gateway device transmits the data information according to the private network IP address and the terminal device.
Fig. 9 is a schematic structural diagram of an embodiment of a machine type communication server according to the present invention, where the embodiment of the present invention can implement the method flow shown in fig. 3 and the signaling flow shown in fig. 5 to 7; as shown in fig. 9, the present embodiment includes: an acquisition module 91 and a transmission module 92;
the obtaining module 91 obtains a private network IP address of a terminal device and an IP address of the gateway device, where the gateway device is a gateway device in a network to which the terminal device is attached; the transmission module 92 transmits data information to the terminal device according to the private network IP address and the IP address of the gateway device.
In the machine type communication server provided by the embodiment of the invention, the transmission module 92 transmits the data information to the terminal device according to the private network IP address of the terminal device and the IP address of the gateway device, and the gateway device is not required to allocate the public network IP address of the terminal device to the terminal device, so that the influence on the existing public network IP address when the terminal device and the network side server transmit data is reduced.
Further, on the basis of the embodiment shown in fig. 9, the obtaining module 91 may further include: the first receiving unit, and/or the first sending unit and the second receiving unit; the first receiving unit receives a private network IP address of the terminal equipment and an IP address of the gateway equipment, which are sent by the terminal equipment; the first sending unit sends a request message to a machine type communication gateway or a domain name server, and the request message is used for requesting to acquire the private network IP address of the terminal equipment and the IP address of the gateway equipment; and the second receiving unit receives the private network IP address of the machine type communication gateway equipment or the domain name server and returns the private network IP address of the terminal equipment and the IP address of the gateway equipment according to the request message.
Further, on the basis of the embodiment shown in fig. 9, the obtaining module 91 is further configured to obtain an instruction from the terminal device to transmit the data information in a tunnel manner, and the transmitting module 92 is specifically configured to: when the obtaining module 91 obtains the instruction from the terminal device to transmit the data information in the tunnel manner, the gateway device communicates with the gateway device in the tunnel manner according to the private network IP address and the IP address of the gateway device, and then the gateway device transmits the data information with the terminal device according to the private network IP address.
Fig. 10 is a schematic structural diagram of an address obtaining server according to an embodiment of the present invention, where the address obtaining server in the embodiment of the present invention may specifically be an MTC gateway device or a DNS, and the embodiment of the present invention may implement the method flow in the embodiment shown in fig. 4 and the signaling flow in the embodiment shown in fig. 7; as shown in fig. 10, the present embodiment includes: the device comprises a receiving module 101, an obtaining module 102 and a sending module 103;
the receiving module 101 receives a private network IP address of a terminal device from the terminal device; the obtaining module 102 sends a request including the private network IP address to a gateway device according to a request sent by an MTC server, so that the gateway device allocates a public network IP address and a port number to the terminal device according to the request including the private network IP address, where the gateway device is a gateway device in a network to which the terminal device is attached; the sending module 103 sends the public network IP address and the port number acquired from the gateway device to the machine type communication server, so that the machine type communication server transmits data information to the terminal device according to the public network IP address and the port number.
In the address obtaining server provided in the embodiment of the present invention, since the obtaining module 102 obtains the public network IP address and the port number of the terminal device from the gateway device according to the request from the machine type communication server for obtaining the public network IP address of the terminal device, the machine type communication server dynamically obtains the public network IP address of the terminal device, and the influence on the existing public network IP address when the terminal device and the machine type communication server transmit data is reduced.
Further, on the basis of the embodiment shown in fig. 10, the obtaining module 102 may further include: the device comprises a first receiving unit, a query unit and a second receiving unit; the first receiving unit is used for receiving a request containing the FQDN from a machine type communication server by the address acquisition server and requesting to acquire a public network IP address and a port number of the terminal equipment; the query unit queries the full-name domain name of the terminal device so as to acquire the IP address of the gateway device, and sends a request containing the private network IP address to the gateway device according to the IP address of the gateway device, so that the gateway device allocates the public network IP address and the port number of the terminal device to the terminal device according to the private network IP address; and the second receiving unit receives the public network IP address and the port number sent by the gateway equipment.
Fig. 11 is a schematic structural diagram of an embodiment of a data transmission system according to the present invention, where the system in the embodiment of the present invention can implement the method flows shown in fig. 2 to fig. 4 and the signaling flow shown in fig. 5; as shown in fig. 11, the present embodiment includes: a network side server 111 and a gateway device 112;
the network side server 111 acquires a private network IP address of the terminal device and an IP address of the gateway device after the terminal device is attached to the network, and performs data information transmission with the gateway device 112 according to the IP address of the gateway device 112, where the IP address of the gateway device 112 is acquired by the terminal device through an attachment acceptance message, and the gateway device 112 is a gateway device in the network to which the terminal device is attached; and the gateway device 112 transmits the data information with the terminal device according to the private network IP address.
In the data transmission system provided in the embodiment of the present invention, since the network-side server 111 acquires the private network IP address of the terminal device and the IP address of the gateway device after the terminal device is attached to the network, the network-side server 111 transmits data information to the terminal device according to the private network IP address of the terminal device and the IP address of the gateway device 112, and since the gateway device 112 is no longer required to allocate the public network IP address of the terminal device to the terminal device, the influence on the existing public network IP address when the terminal device and the network-side server 111 transmit data information is reduced.
Further, on the basis of the embodiment shown in fig. 11, the network-side server 111 is further configured to obtain an instruction sent by the terminal device to transmit the data information in a tunnel manner, and communicate with the gateway device 112 in a tunnel manner according to the IP of the gateway device 112, so that the gateway device 112 transmits the data information with the terminal device according to the private network IP address.
Further, on the basis of the embodiment shown in fig. 11, the network side server may be a machine type communication server, or the network side server may further include a machine type communication server, a machine type communication gateway, or a domain name server; fig. 12 is a schematic structural diagram of a data transmission system according to another embodiment of the present invention, where the system in this embodiment of the present invention can implement the method flows of the embodiments shown in fig. 2 to fig. 4 and the signaling flow of the embodiment shown in fig. 6; in the embodiment, a network side server specifically includes an MTC server and an MTC GW/DNS is taken as an example for explanation; as shown in fig. 12, the present embodiment includes: gateway device 121, MTC server 122, MTC GW/DNS123, MME124, HSS 125;
the HSS125 is configured to provide subscription information of the terminal device for the MME124, and the MME124 determines that the terminal device is a machine type communication device according to the subscription information of the terminal device; after the MME124 determines that the terminal device is a machine type communication device, the MME124 sends an attach accept message to the terminal device, where the attach accept message includes an IP address of the gateway device 121; further, MME124 may carry the IP address of gateway device 121 in the accept message by field expanding the attach accept message.
After the terminal equipment is attached to the network, the MTC GW/DNS123 receives the private network IP address of the terminal equipment and the IP address of the gateway equipment 121 sent by the terminal equipment, and provides the private network IP address of the terminal equipment and the IP address of the gateway equipment 121 for the MTC server 122 when the MTC server 122 needs to transmit data information to the terminal equipment; the gateway device 121 is a gateway device in a network to which the terminal device is attached.
In the data transmission system provided in the embodiment of the present invention, since the terminal device sends the private network IP address of the terminal device and the IP address of the gateway device 121 to the MTC server 122, the MTC server 122 transmits data information to the terminal device according to the private network IP address of the terminal device and the IP address of the gateway device 121, and since the gateway device 121 is no longer required to allocate the public network IP address of the terminal device to the terminal device, the influence on the existing public network IP address when the terminal device and the MTC server 122 transmit data is reduced.
Further, on the basis of the embodiment shown in fig. 12, the MTC GW/DNS123 is further configured to obtain an indication that the data information is transmitted in a tunnel manner, where the indication is sent by the terminal device, and when the MTC server 122 needs to transmit the data information to the terminal device, the MTC server 122 obtains a private network IP address of the terminal device and an IP address of the gateway device 121 from the MTC GW/DNS123, so that the MTC server 122 communicates with the gateway device 121 in a tunnel manner according to the IP address of the gateway device 121, and then the gateway device 121 transmits the data information with the terminal device according to the private network IP address.
Fig. 13 is a schematic structural diagram of a further embodiment of the data transmission system of the present invention, where the system in the embodiment of the present invention may implement the method flows in the embodiments shown in fig. 2 to fig. 4 and the signaling flow in the embodiment shown in fig. 7, and the location obtaining server in the embodiment of the present invention may specifically be the location obtaining server in the embodiment shown in fig. 10, and the location obtaining server may specifically implement a function of MTC GW/DNS; as shown in fig. 13, the present embodiment includes: gateway device 131, MTC server 132, location acquisition server 133;
after the terminal device is attached to the network, the location obtaining server 133 receives a private network IP address sent by the terminal device, and sends a second request containing the private network IP address to the gateway device 131 according to the first request sent by the MTC server 132, so that the gateway device 131 allocates a public network IP address and a port number to the terminal device according to the second request;
the location obtaining server 133 sends the public network IP address and the port number obtained from the gateway device 131 to the MTC server 132, and the MTC server 132 performs data information transmission with the terminal device according to the public network IP address and the port number.
In the data transmission system provided in the embodiment of the present invention, since the location obtaining server 133 obtains the public network IP address and the port number of the terminal device from the gateway device 131 according to the request from the MTC server 132 for obtaining the public network IP address of the terminal device, the MTC server 132 dynamically obtains the public network IP address of the terminal device when data transmission is required, and the influence on the existing public network IP address when the terminal device and the MTC server 132 transmit data is reduced.
Further, on the basis of the embodiment shown in fig. 13, as shown in fig. 13, the data transmission system may further include: MME134, HSS 135; the HSS135 is configured to provide subscription information of the terminal device for the MME134, so that the MME134 determines that the terminal device is a machine type communication device according to the subscription information of the terminal device; after the MME134 determines that the terminal device is a machine type communication device, the MME134 sends an attach accept message to the terminal device, where the attach accept message includes an IP address of the gateway device 131; specifically, MME134 carries the IP address of gateway device 131 in the accept message by field-expanding the attach accept message.
It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, devices, modules and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
Those of ordinary skill in the art will understand that: all or part of the steps for implementing the embodiments can be implemented by hardware related to program instructions, and the program can be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.