WO2012152221A1

WO2012152221A1 - Service communication method, device, and system

Info

Publication number: WO2012152221A1
Application number: PCT/CN2012/075270
Authority: WO
Inventors: 郭小龙
Original assignee: 华为技术有限公司
Priority date: 2011-05-11
Filing date: 2012-05-10
Publication date: 2012-11-15
Also published as: CN102780999A; CN102780999B

Abstract

Disclosed are a service communication method, device, and system. When a server needs to communicate with a UE, a trigger request is transmitted through the server to the target UE to trigger the temporary IP allocation for the UE, the temporary bearing between the UE and the server, or the establishment of other data connections, thereby enabling temporary communication between the server and the UE. During most of the period when the server and the UE are not in communication, the UE does not have a dedicated IP address, bearing, or other data connections, thereby effectively conserving network cost.

Description

The present invention relates to the field of communications technologies, and in particular, to a service communication method, apparatus, and system. Background technique

At present, M2M (Machine to Machine) communication has been widely used in machine-to-machine wireless communication. Broadly speaking, M2M's main application mode is machine-to-machine, machine-to-mobile (such as user remote monitoring:) and mobile Phone to machine (such as user remote control:).

Initially, it is expected that the terminal used for human-to-human communication may only account for a fraction of the entire terminal market, and a larger number of communications is the M2M communication service. In fact, the number of machines is currently at least four times the number of humans, so M2M has huge market potential. At the same time, because M2M is a combination of wireless communication and information technology, it can be used for two-way communication, such as collecting information, setting parameters and sending commands over long distances. Therefore, M2M technology can have different application schemes, such as security monitoring, vending machines, cargo tracking. Wait.

From the perspective of device characteristics, M2M and our traditional H2H (Human to Human) communication methods differ in the following ways: 1) The main purpose of the information transmitted between M2M terminals is to achieve some automatic Control function, no human intervention is required; 2) The number of potential terminals participating in M2M communication is very large, and the interaction traffic of each terminal may be very small, and the interaction may be sudden; 3) The functions implemented by the M2M terminal are relatively More specific, only need to complete certain information transmission interactions; 4), some M2M terminals may be relatively fixed, or rarely moved; 5), M2M terminal behavior in a specific application is consistent, for example, In the electronic meter reading service, all terminals upload data to a specific server at a specific time.

H2H MTC (Machine Type Communications) application The architecture mainly includes MTC Device (MTC device), MTC Server (MTC server), network part (access network element, core network element, HSS and other logical functions), and MTC server stores MTC device or group related Data or information to provide MTC services or related information, such as a meter reading and processing server. MTC equipment also includes some automatic communication facilities in daily life such as vending machines, gas meter readers, hydroelectric meters, and the like. The communication network between the MTC server and the MTC device is mainly a 3GPP network (such as GSM or UMTS or SAE system).

The current MTC device or user equipment (UE) is identified by IMSI (International Mobile Subscriber Identity), TMSI (Temporary Mobile Subscriber Identity), and MSISDN (Mobile Subscriber Integrated Service Digital Network Number). Integrated Services Digital Network Number). The IMSI and the MSISDN are both network record user equipment identifiers, which are recorded in the HSS and core network nodes (MSC/SGSN of 2G/3G, MME of SAE/LTE), and TMSI is a temporarily assigned identifier, which is also recorded in the core network node. in. TMSI is the general term for temporary identification. Specifically, it is called TMSI in the 2G/3G CS domain, P-TMSI in the 2G/3G PS domain, and GUTI (Global Unique Temporary Identity) in the SAE/LTE system. ). IMSI is an internal identifier of a user equipment in the network. It is used to uniquely index a user equipment and has certain confidentiality. The MSISDN is mainly used in the CS domain and is an externally visible identifier. Other users can call the user equipment to establish a call by dialing the number. This number can also be used for short message (SMS, short message service) communication. Inside the network, MSISDN is mainly used for the No. 7 signaling route to find the HSS where the user equipment is located, so as to find the core network node where the user equipment is located.

For the PS domain, if the user equipment wants to implement communication, whether it is active communication or passive communication, it must first allocate IP and establish a bearer before communicating with the peer node. If the peer node wants to communicate with the user equipment, it must also know the IP address of the user equipment to send IP data to the IP address of the user equipment. After the IP data arrives at the network, the bearer is established to send data to the peer. If the user equipment is in an idle state, after the data arrives at the S-GW or the SGSN, there is no lower data bearer. The network paging user equipment is triggered, and the user equipment responds to establish a RAB (Radio Access Bearer), and establishes a lower bearer that reaches the user equipment, so that the bearer of the entire network can be opened, so that the MTC is enabled. The server can send data to the user device.

The user equipment generally takes the PS data service. Many of the M2M services are triggered by the downlink service. For example, the water meter company triggers the water meter to report the current reading. This random trigger requires the MTC Device to be reachable at any time. According to the data service type, the trigger mode of the user equipment may be triggered by a short message or triggered by IP data.

However, if the MTC Device is required to be MSISDN through the short message triggering, the number of M2M terminals is large, and may reach several times the current number of UEs in the future. If an MSISDN is allocated to each MTC Device, the number of MSISDNs may be consumed quickly, and then the number of bits of the MSISDN has to be upgraded, and the number of bits of the MSISDN upgrade is not only time-consuming and labor-intensive, but also causes operator overhead. greatly increase.

If the IP data is triggered, it is necessary to assign an IP address to the MTC Device and establish a bearer before the communication. First, the number of IP addresses is limited. In an IPv4 scenario, assigning an IP to each MTC Device in advance will consume a large number of IP addresses. Of course, using IPv6 or a private address can alleviate the problem of insufficient IP address space. . Secondly, the MTC Device pre-establishes a bearer and occupies a large amount of resources on the network. For example, an MME, S-GW, and P-GW of an SAE system can generally establish one million bearers, assuming that there are 10 million MTC Devices in the Beijing area. , electric meter, car, etc.), and each MTC Device establishes two bearers when the boot is attached, then the Beijing area only needs 20 MME/S-GW/P-GW for the MTC Device, but these MTC Devices It is not time to communicate with the same time. For example, each MTC Device will only communicate for 10 minutes, and up to 500,000 MTC Devices will communicate within the same time period. That is to say, in fact, the MTC Device does not communicate at all times, and does not concentrate on initiating communication. Normally, only one MME/S-GW/P-GW is required to meet the communication requirements, but the network has to I don’t know when I can initiate the communication and keep the IP and bearer of the MTC Device, and I have to buy it. Many devices cause a waste of network resources. Moreover, the established bearer will continuously update the bearer as the MTC Device moves, and also causes a large amount of signaling overhead. Summary of the invention

The embodiments of the present invention provide a method, a device, and a system for communicating services to solve the problem that existing user equipments need to have a fixed bearer or IP to implement trigger communication and waste network resources.

A service communication method includes: a service management center receiving a trigger request sent by a server, where the trigger request carries a user equipment identifier; the service management center determines a core network node currently registered by the user equipment corresponding to the user equipment identifier; The service management center sends an IP address allocation request of the user equipment to the core network node, where the IP address allocation request is used to trigger the core network node to page the user equipment according to the user equipment identifier and is also used to The user equipment establishes a bearer and obtains an IP address after accessing the network; the service management center sends a message carrying the IP address of the user equipment to the server; and establishing the bearer according to the bearer established by the user equipment and the IP address. Communication between the server and the user equipment.

The embodiment of the present invention provides a service communication device, including a receiving unit, configured to receive a triggering request sent by a server, where the triggering request carries a user equipment identifier, and a positioning unit, configured to determine a user equipment corresponding to the user equipment identifier. a currently registered core network node; a requesting unit, configured to send an IP address allocation request of the user equipment to the core network node, where the IP address allocation request is used to trigger the core network node to perform paging according to the user equipment identifier The user equipment is further configured to: after the user equipment accesses the network, establish a bearer and obtain an IP address; the sending unit is configured to send, to the server, a message that carries the IP address of the user equipment; and a processing unit, configured to: The bearer established by the user equipment and the IP address establish communication between the server and the user equipment.

The embodiment of the present invention provides a service communication system, including a server, a core network node, and a service management center. Before the server communicates with the user equipment, the server manages the service. The center sends a trigger request of the user equipment, where the trigger request carries the user equipment identifier; the service management center determines a core network node registered by the user equipment corresponding to the user equipment identifier, and sends the core network node to the core network node. The IP address allocation request of the user equipment; the core network node pages the user equipment according to the user equipment identifier; after the user equipment accesses the network, the IP address allocation request triggers the user equipment to establish a bearer and Acquiring an IP address; the core network node responds to the server by the service management center with a message carrying the user equipment IP address information; the server is configured according to the bearer and IP address information established by the user equipment The user equipment establishes communication.

The embodiment of the present invention provides a service communication method, which is used to trigger a temporary communication between a target user equipment and a server, where the service management center receives a trigger request of the server, where the trigger request carries the user equipment identifier and data; The management center determines a core network node that is currently registered by the user equipment corresponding to the user equipment identifier; the service management center sends a request for triggering the user equipment to the core network node, so that the core network node is configured according to the The user equipment identifies the user equipment and, after the user equipment accesses the network, causes the core network node to send data in the trigger request to the user equipment; the service management center receives the user equipment a response message, the response message is sent by the core network node to the service management center; the service management center sends a response message of the user equipment to the server, to complete communication between the server and the user equipment. .

A service communication device according to an embodiment of the present invention includes a first receiving unit, configured to receive a trigger request of a server, where the trigger request carries a user equipment identifier and data, and a positioning unit, configured to determine, corresponding to the user equipment identifier a requesting unit, configured to send a request for triggering the user equipment to the core network node, so that the core network node pages the user equipment according to the user equipment identifier and After the user equipment accesses the network, the core network node sends the data in the trigger request to the user equipment; the second receiving unit is configured to receive a response message of the user equipment, where the response message is Sending, by the core network node, the service management center; A response message from the user equipment is sent to the server to complete communication between the server and the user equipment.

The service communication system provided by the embodiment of the present invention includes a server, a core network node, and a service management center. Before the server communicates with the user equipment, the server sends a trigger request of the user equipment to the service management center, where the trigger request carries the user. a device identifier and data; the service management center determines, by the user equipment identifier, a core network node that is registered by the user equipment, and pages the user equipment corresponding to the user equipment identifier by using the core network node; After the access, the core network node sends the data in the trigger request to the user equipment; the user equipment sends a response message to the service management center through a core network node; the service management center sends the response The message is returned to the server.

The embodiment of the present invention provides a service communication method, which is used to trigger communication between a target user equipment and a server, where the service management center receives a trigger request of the server, and the trigger request carries the user equipment identifier and data; the service management center determines a core network node currently registered by the user equipment corresponding to the user equipment identifier; the service management center sends a setup bearer request to the core network node, where the establishing a bearer request causes the core network node to page After the user equipment is accessed, the user equipment is requested to establish a bearer from the user equipment to the service management center; the service management center binds the bearer established by the user equipment to the user equipment identifier and along the bearer direction. The user equipment sends the data in the trigger request; the service management center receives a message that the user equipment responds along the bearer and sends the response message to the server to complete the server and the user equipment. Communication.

An embodiment of the present invention provides a service communication device, including a first receiving unit, configured to receive a trigger request of a server, where the trigger request carries a user equipment identifier and data, and a positioning unit, configured to determine, corresponding to the user equipment identifier a core network node currently registered by the user equipment; a requesting unit, configured to send a setup bearer request to the core network node, where the establishing a bearer request causes the core network node to request the user equipment to establish after the user equipment accesses a bearer from the user equipment to the service management center; a second receiving unit, configured to receive the user The device sends a response message along the bearer and sends the response message to the server to complete communication between the server and the user equipment.

The embodiment of the present invention provides a service communication system, including a server, a core network node, and a service management center. Before the server communicates with the user equipment, the server sends a trigger request of the user equipment to the service management center, where the trigger request is sent. Carrying the user equipment identifier and the data; the service management center determines the core network node registered by the user equipment by using the user equipment identifier; the service management center sends a setup bearer request to the core network node, so that the core After the user equipment accesses the network, the network node requests the user equipment to establish a bearer from the user equipment to the service management center; the user equipment establishes the bearer according to the request of the core network node; The service management center binds the bearer to the user equipment identifier and sends the data in the trigger request to the user equipment along the bearer; the service management center receives the user equipment response along the bearer. The message is sent to the server.

The service communication method, device, and system of the foregoing embodiment may trigger a temporary IP allocation of the user equipment and a temporary bearer between the user equipment and the server by sending a trigger request to the target user equipment through the server when the server needs to communicate with the user equipment. Or the establishment of other data connections to implement temporary communication between the server and the user equipment, and the user equipment does not have a dedicated IP address, bearer or other data connection for most of the time when the server and the user equipment do not communicate, thereby effectively saving network overhead. . DRAWINGS

FIG. 1 is a flowchart of a service communication method according to Embodiment 1 of the present invention.

FIG. 2 is a schematic flowchart diagram of a service communication method according to Embodiment 1 of the present invention.

FIG. 3 is a schematic flowchart of external identifier conversion of a user equipment according to Embodiment 1 of the present invention. FIG. 4 is a schematic flowchart of determining a core network node registered by a user equipment according to Embodiment 1 of the present invention. FIG. 5 is a schematic diagram of a supplementary flow of a service communication method according to Embodiment 1 of the present invention.

FIG. 6 is a schematic diagram of a service communication apparatus according to Embodiment 2 of the present invention.

FIG. 7 is a schematic diagram showing a service communication system according to Embodiments 3, 6, and 9 of the present invention.

FIG. 8 is a flowchart of a service communication method according to Embodiment 4 of the present invention.

FIG. 9 is a schematic flowchart diagram of a service communication method according to Embodiment 4 of the present invention.

Figure 10 is a flow chart showing the process of determining the core network node registered by the user equipment and paging the user equipment corresponding to the user equipment identifier through the core network node in the fourth embodiment of the present invention.

FIG. 11 is a schematic diagram of a service communication apparatus according to Embodiment 5 of the present invention.

FIG. 12 is a flowchart of a service communication method according to Embodiment 7 of the present invention.

FIG. 13 is a schematic flowchart diagram of a service communication method according to Embodiment 7 of the present invention.

FIG. 14 is a schematic flowchart of determining a core network node registered by a user equipment and paging the user equipment corresponding to the user equipment identifier by using the core network node according to Embodiment 7 of the present invention.

FIG. 15 is a schematic diagram of a service communication apparatus according to Embodiment 8 of the present invention. The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. example. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention are within the scope of the present invention.

Embodiment 1

The first embodiment of the present invention provides a service communication method for identifying and triggering a communication connection between a terminal device and a server in M2M communication. In this embodiment, the terminal device such as the user equipment is a complex terminal, and has multiple services, and different services have different QoS requirements. The user equipment and the peer end, such as the communication between the user equipment and the server, must use an IP protocol stack. The user equipment in this embodiment does not register the IP address information of the IP with the server in advance. As shown in FIG. 1 and FIG. 2, in the embodiment that the user equipment does not have a proprietary IP address and a bearer, the service communication method includes the following steps:

Step 101: The service management center receives a trigger request sent by the server, where the trigger request carries a user equipment identifier.

Step 102: The service management center determines, by using the user equipment identifier, a core network node currently registered by the user equipment corresponding to the user equipment identifier;

Step 103: The service management center sends an IP address allocation request of the user equipment to the core network node, where the IP address allocation request is used to trigger the core network node to page the user equipment according to the user equipment identifier. And the user equipment is used to establish a bearer and obtain an IP address after accessing the network;

Step 104: The service management center sends a message carrying the IP address of the user equipment to the server.

Step 105: Establish communication between the server and the user equipment according to the bearer and the IP address established by the user equipment.

In the foregoing step 101, the user equipment identifier carried in the trigger request may be an internal identifier or an external identifier. If it is an external identifier, it needs to be converted into an internal identifier for identification within the network. The conversion is mainly performed by an IMF (identity mapping function), and the IMF has an interface with the service management center or an IMF merged with the service management center. Inside, as shown in FIG. 3, the following external identity conversion is also included before step 102:

Step 201a: The service management center acquires a corresponding APN (Access Point Name) information according to the address information of the server;

Step 202a: Find a corresponding IMF according to the APN information.

Step 203: Query the IMF to query the internal identifier corresponding to the external identifier of the user equipment. Step 204: The IMF returns the internal identifier of the user equipment to the service management center.

If the user equipment identifier carried by the trigger request is an internal identifier, then the IMF and the service The server has an interface or an IMF merged in the server, and the request message of step 101 directly carries the internal identifier of the user equipment, because the server may query the IMF for the internal corresponding to the external identifier of the server before sending the trigger request. The identifier, the IMF returns an internal identifier of the user equipment to the server, and the server directly initiates a trigger request by using an internal identifier.

As shown in FIG. 4, in the foregoing step 102, the core network node may be an MME (Mobility Management Entity) or an SGSN (Serving GPRS Support Node), and the service management center passes through the office. The action of the user equipment identifier determining the core network node currently registered by the user equipment corresponding to the user equipment identifier includes the following steps:

Step 201b: If the service management center already knows the address information of the user equipment corresponding to the user equipment identifier, directly determine, by using the address information, the core network node that is currently registered by the user equipment;

Step 202b: If the service management center does not know the address information of the user equipment, first query the address information of the user equipment corresponding to the user equipment identifier to the HSS (Home Subscriber Server), by using the The address information determines a core network node that is currently registered by the user equipment.

In the foregoing step 202b, the address information of the user equipment is the registered core network node identifier, so the core network node where the user equipment is located can be found by using the address information of the user equipment.

The service management center in the foregoing step 103 sends an IP address allocation request of the user equipment to the core network node, where the IP address allocation request carries APN information corresponding to the server, so that the user equipment follows A PDN (Packet Data Network) connection to the service management center and a bearer of the APN are established.

In the foregoing step 103, if the core network node fails to page the user equipment according to the user equipment identifier, the subsequent step becomes that the core network node directly sends an uplink message that fails to be sent to the service management center, and then passes the service. The management center notifies the user equipment that the trigger failed, The failure of the middle trigger is that the user equipment is not paged due to network congestion or abnormality, which causes the trigger to end abnormally. Therefore, the implementation of the embodiment of the present invention needs to be established under the condition that the network is normal.

After the user equipment accesses the network, the core network node sends the APN information corresponding to the server to the user equipment, and the user equipment is redirected to the core network. The node initiates the establishment of a bearer to the APN corresponding to the server, where the bearer is a PDN or PDP between the user equipment and the service management center in this embodiment.

(Packet Data Protocol) The data link may be a P-GW (PDN-GW, Packet Data Network Gateway) corresponding to the server APN in other embodiments.

The IP address of the user equipment is directly assigned by the AAA Server (Authentication, Authorization, Accounting, Authentication and Authorization) or the P-GW to the user in the process of establishing the bearer. In practical applications, no matter who is nominally assigned to the user equipment, it can be considered as being assigned by the AAA Server and the core network node can know the address to which the user equipment is assigned. The AAA Server logical entity is a RADIUS (Remote Authentication Dial In User Service) server or a DHCP server, configured to allocate an IP address to the user equipment, and record the correspondence between the IP address and the internal identifier of the user equipment. And may be merged into the service management center or the P-GW, and merged to become the service management center or the P-GW to allocate an address to the user equipment.

In the foregoing step 104, if the user equipment is assigned a private IP address, that is, the user equipment and the server are not in an address space domain, NAT (Network Address Translation) address translation is required. The service management center not only returns the private IP address of the user equipment to the server, but also returns information such as an external address and a port number of the NAT entity to implement the server and the user equipment by using NAT. Communication between internal and external networks.

In the above step 105, after receiving the IP address of the user equipment, the server may transmit data to the user equipment according to the IP address, where the user equipment is based on the data source and The information required to respond to the server is carried, so that the triggering and information interaction with the specified user equipment is completed without the server knowing the IP address of the user equipment in advance.

As shown in FIG. 5, after the foregoing step 104, the service communication method of the embodiment further includes: Step 106: After the user equipment completes information interaction with the server, the service management center receives the user equipment release Notification of IP address;

Step 107: The service management center notifies the server to delete the correspondence between the IP address and the user equipment.

In the foregoing step 107, the user equipment releases the IP address and cancels the bearer of the user equipment to the service management center to save the IP address and the network overhead.

The notification of releasing the IP address is sent by the core network node to the service management center, and the service management center notifies the server.

The above method for triggering and identifying a user equipment, the user equipment may not have a dedicated IP address and bearer, and only when the user equipment or the server sends data to the opposite end, the trigger is performed, and the server and the server are implemented by reallocating the IP and establishing the bearer. The information exchange of the user equipment effectively saves the IP address space and network overhead in most of the time when the server and the user equipment do not communicate.

In addition, most nodes of the network only need to save the internal identifier of the user equipment without having to save its external identifier. The external identifier is only saved by the corresponding server and IMF entity. The format of the external identifier can be FQDN, URI, or even MSISDN. Different servers can have different formats. For the same user device, different servers can set different external identifiers or formats, and different entities only need to save the necessary Information can be saved without saving unnecessary information, thus saving storage space.

Embodiment 2

As shown in FIG. 6, the second embodiment of the present invention provides a service communication apparatus corresponding to the service communication method of the first embodiment, which is used to trigger communication between the user equipment and the server.

The device includes:

a receiving unit, configured to receive a trigger request sent by the server, where the trigger request carries a user Equipment Identity;

a positioning unit, configured to determine a core network node currently registered by the user equipment corresponding to the user equipment identifier;

a requesting unit, configured to send an IP address allocation request of the user equipment to the core network node, where the IP address allocation request is used to trigger the core network node to page the user equipment to access the network according to the user equipment identifier and And the user equipment is used to establish a bearer and obtain an IP address after accessing the network;

a sending unit, configured to send, to the server, a message that carries the IP address of the user equipment, and a processing unit, configured to establish, according to the bearer and the IP address established by the user equipment, communication between the server and the user equipment .

The user equipment identifier carried in the triggering request is an internal identifier or an external identifier. If the user equipment identifier carried by the triggering request is an external identifier, the receiving module converts the external identifier into an internal identifier.

The device further includes:

An obtaining module, configured to obtain, after the user equipment completes information interaction with the server, a notification that the user equipment releases an IP address;

Notifying the server to notify the server to delete the corresponding relationship between the IP address and the user equipment.

As shown in FIG. 7, a third embodiment of the present invention provides a service communication system, including a server 20, a core network node 40, and a service management center 30. Before the server 20 communicates with the user equipment 10, the server 20 sends a trigger request of the user equipment 10 to the service management center 30, where the trigger request carries the user equipment identifier; the service management center 30 determines by using the user equipment identifier. And the core network node 40 of the user equipment 10 corresponding to the user equipment identifier, and sending an IP address allocation request of the user equipment 10 to the core network node 40; the core network node 40 according to the user equipment identifier Paging the user equipment 10; after the user equipment 10 is accessed, Assigning an address to the user equipment 10 and establishing a bearer according to the address allocation request; the core network node 40 responds to the server 20 by the service management center 30 with a message carrying the IP address information of the user equipment 10; The server 20 establishes communication with the user equipment 10 according to the IP address information of the user equipment 10 and the established bearer.

The user equipment identifier carried in the trigger request may be internally identified or externally identified. If it is an external identifier, it needs to be converted into an internal identifier for identification within the network. The service communication system of this embodiment further includes an IMF 50, and the conversion is mainly performed by the IMF 50.

The service management center 30, by using the user equipment identifier, finds the core network node 40 where the user equipment 10 corresponding to the user equipment identifier is located, and must first know the address information of the user equipment 10.

Specifically, the service communication system service communication system of this embodiment further includes an HSS 60. If the service management center 30 already knows the address information of the user equipment 10 corresponding to the user equipment identifier, the address information is directly found through the address information. The core network node 40 corresponding to the user equipment 10; if the service management center 30 does not know the address information of the user equipment 10, the HSS 60 needs to first query the HSS 60 for the address of the core network node where the user equipment 10 is located corresponding to the user equipment identifier. Information, the address information of the user equipment 10 is an identifier of a core network node registered by the user equipment.

The IP address allocation request carries the APN information corresponding to the server 20, so that the user equipment 10 establishes a service management corresponding to the APN according to the APN information corresponding to the server 20 carried in the address allocation request. The carrying of the center 30.

The service communication system further includes an AAA server 70, and the AAA server 70 is configured to allocate an IP address to the user equipment 10, and record a correspondence between the IP address and the internal identifier of the user equipment 10.

After receiving the IP address of the user equipment 10, the server 20 of the service communication system in this embodiment can transmit data to the user equipment 10 according to the IP address, and the user equipment 10 responds according to the data source and the bearer response. The information required by the server 20, so that the triggering and information exchange with the specified user equipment is completed without the server 20 knowing the IP address of the user equipment 10 in advance. Mutual.

Embodiment 4

Embodiment 4 of the present invention provides a service communication method for identifying and triggering a communication connection between a terminal device and a server in M2M communication. In this embodiment, the terminal device such as the user equipment is a simple terminal, and has a single service, and the user equipment and the opposite end, such as a server, can perform fixed format communication, for example, a specific format between the user equipment and the server through a short message. The data interacts.

As shown in Figures 8 and 9, the service communication method includes the following steps:

Step 301: The service management center receives a trigger request of the server, where the trigger request carries a user equipment identifier and a data trigger request trigger request.

Step 302: The service management center determines a core network node currently registered by the user equipment corresponding to the user equipment identifier.

Step 303: The service management center sends a request for triggering the user equipment to the core network node, so that the core network node pages the user equipment according to the user equipment identifier and accesses the user equipment. After the network, the core network node sends a data trigger request in the trigger request to the user equipment;

Step 304: The service management center receives a response message of the user equipment, where the response message is sent by the core network node to the service management center;

Step 305: The service management center sends a response message of the user equipment to the server, to complete communication between the server and the user equipment.

In the foregoing step 301, the identifier of the user equipment may be an internal identifier or an external identifier. If it is an external identifier, it needs to be converted into an internal identifier for identification within the network. The specific conversion process is to first obtain the corresponding APN information according to the server address information; and then find the corresponding IMF according to the APN information; and then query the corresponding IMF. The internal identifier corresponding to the external identifier is returned to the service management center by the IMF after the conversion is completed; if it is the internal identifier, the service management center directly uses the conversion without using the conversion. As shown in FIG. 10, in the foregoing steps 302 and 303, the core network node may be an MME (Mobility Management Entity) or an SGSN (Serving GPRS Support Node), the service management center. The action of determining, by the user equipment identifier, the core network node where the user equipment is located, and triggering the core network node to page the user equipment corresponding to the user equipment identifier includes the following steps:

Step 401: Determine a core network node that is registered by the user equipment.

Step 402: Send the trigger request to the core network node.

Step 403: The core network node pages the user equipment according to the user equipment identifier in the trigger request.

In the above step 401, if the service management center already knows the address information of the user equipment corresponding to the user equipment identifier, directly find the core network node corresponding to the user equipment by using the address information; To know the address information of the user equipment, the HSS needs to first query the address information of the user equipment corresponding to the user equipment identifier.

If the paging of the user equipment fails in step 403, the subsequent step becomes that the core network node directly sends an uplink message that fails to be sent to the service management center, and then the service management center notifies the user equipment that the trigger fails, and the trigger fails. The user equipment is not paged due to network congestion or abnormality.

In the foregoing step 304, the user equipment sends the response data to the core network node, and then the core network node sends the response message of the user equipment to the service management center. The response message includes the user equipment identifier of the user equipment and the response data, that is, after receiving the response data of the user equipment, the core network node adds the user equipment identifier corresponding to the user equipment and returns the information to the service management center, and The user equipment identifier is an internal identifier.

The server may establish a signaling connection communication with the service management center, so that the service management center and the server are connection-oriented signaling communication, and may also establish a signaling-free connection communication, so that the service management center and the server are There is no signaling communication between.

When there is no signaling connection between the server and the service management center, the foregoing In step 305, the response message carries the user equipment identifier and the response data, and the format of the response data is consistent with the data format in the triggering request, and the user equipment identifier is also consistent with the user equipment identifier in the triggering. Both are external identifiers or both internal identifiers. Therefore, before the service management center returns the response message to the server, the service management center receives the user equipment identifier and the user equipment in the trigger request included in the response message from the core network node. If the identifiers are inconsistent, the service management center converts the user equipment identifier in the response message by using a corresponding IMF; if the service management center receives the response data included in the response message from the core network node, the format of the response data is The data format in the trigger request sent by the server is inconsistent, and the service management center converts the response data into a data format in the trigger request, so that the server and the user equipment perform the data message in a specific format. Simple information interaction.

When the server and the service management center are connected to each other, the service management center may not carry any identifier in the message of the response server, but the user equipment that obtains the response according to the signaling connection information by the server. Identification information.

The method for triggering and identifying the user equipment may be used to find and trigger the user equipment to respond to the data carried in the trigger request by using the user equipment identifier to implement the information of the server and the user equipment only when the user equipment or the server sends data to the peer end. Interaction, and most of the time when the server and the user equipment do not communicate, the user equipment may not have a dedicated IP address and bearer, thereby effectively saving network overhead.

Embodiment 5

As shown in FIG. 11, a fifth embodiment of the present invention provides a service communication device corresponding to the service communication method of the fourth embodiment, which is used to trigger communication between the user equipment and the server.

The device includes:

a first receiving unit, configured to receive a trigger request of the server, where the trigger request carries a user equipment identifier and data;

a positioning unit, configured to determine that the user equipment corresponding to the user equipment identifier is currently registered Core network node;

a requesting unit, configured to send, to the core network node, a request for triggering the user equipment, so that the core network node pages the user equipment according to the user equipment identifier, and after the user equipment accesses the network, Transmitting, by the core network node, data in the trigger request to the user equipment;

a second receiving unit, configured to receive a response message of the user equipment, where the response message is sent by the core network node to the service management center;

And a sending unit, configured to send a response message of the user equipment to the server, to complete communication between the server and the user equipment.

Embodiment 6

As shown in FIG. 7, a fourth embodiment of the present invention provides a system for service communication, including a server 20, a core network node 40, and a service management center 30.

Before the server 20 communicates with the user equipment 10, the server 20 sends a trigger request of the user equipment 10 to the service management center 30, where the trigger request carries the user equipment identifier and data; the service management center 30 passes the user equipment. Identifying the core network node 40 where the user equipment 10 is located, and paging the user equipment 10 corresponding to the user equipment identifier by the core network node 40; after the user equipment 10 is accessed, the core network node 40 The user equipment 10 sends the data in the trigger request; the user equipment 10 sends a response message to the service management center 30 through the core network node 40; the service management center 30 returns the response message to the Server 20.

The service communication system of this embodiment further includes an IMF 50,

The user equipment identifier carried in the foregoing trigger request may be an internal identifier or an external identifier. If it is an external identifier, it needs to be converted into an internal identifier for intra-network identification. The specific conversion process is to first obtain the corresponding APN information according to the address information of the server 20; then find the corresponding IMF 50 according to the APN information; and then query the corresponding IMF 50. The internal identifier corresponding to the external identifier is returned to the service management center by the IMF 50 after the conversion is completed. 30; If it is an internal identifier, the business management center 30 is used directly without conversion.

Specifically, the service communication system of this embodiment further includes an HSS. If the service management center 30 already knows the address information of the user equipment 10 corresponding to the user equipment identifier, the triggering request sent by the server further carries the location of the user equipment. Information, the core network node 40 corresponding to the user equipment 10 is directly found by the address information; if the service management center 30 does not know the address information of the user equipment 10, the HSS 60 needs to first query the user equipment. The address information of the corresponding user equipment 10 is identified.

The user equipment 10 sends a response message to the service management center 30 through the core network node 40. The user equipment 10 first sends response data to the core network node 40, and then the core network node 40 sends the response data to the service management center. 30 returns the response message. In this embodiment, the server and the service management center have no signaling connection communication, and the response message includes the user equipment identifier of the user equipment 10 and the response data, that is, the service management center 30 receives After the response data to the user equipment 10 is added, the user equipment identifier corresponding to the user equipment 10 is added and returned to the service management center 30. In other embodiments, the server and the service management center may be connection-oriented signaling communications, and the response message includes response data of the user equipment 10, where the service management center responds to the response message of the server. The identifier does not carry any identifier, but the server obtains the identification information of the responding user equipment according to the signaling connection information.

In summary, the foregoing service management center 30 responds whether the message carries the identifier of the user equipment 10, depending on whether the service management center establishes a signaling connection with the specific user equipment, for example, when the server sends a trigger request to the service management center, a specific user is established. The signaling connection of the device, when the service management center returns a message, the message replied on the signaling connection may not carry any user equipment identifier, but is corresponding to the user equipment through the signaling connection. Otherwise, in the case that the service management center and the server do not establish a signaling connection of a specific user equipment, in the service The user equipment ID is required to be carried in the message returned by the management center. Whether the internal identifier of the user equipment or the external identifier is carried, depends on whether the identifier carried by the server in the trigger message is an internal identifier or an external identifier. If the user equipment identifier in the trigger request is an external identifier, the service management center 30 is required. The foregoing description is also applicable to other embodiments by using the corresponding IMF 50. The foregoing description is also applicable to other embodiments. For the convenience of description, in other embodiments, the service management center and the server do not establish a signaling connection of a specific user equipment and trigger. The request carries the external representation as an example, and the various situations are not described again. If the service management center 30 receives the response data from the core network node 40 and the format of the response data is inconsistent with the data format in the trigger request sent by the server 20, the service management center 30 will respond the data. The conversion is in accordance with the data format in the trigger request, so that the server 20 and the user device 10 perform simple information interaction through a data message of a specific format.

The device 20 is configured to trigger and identify the user equipment, and only when the user equipment 10 or the server 20 sends data to the opposite end, the user equipment 10 identifies and triggers the user equipment 10 to respond to the data carried in the trigger request, so that the server 20 is implemented. The information exchanges with the user equipment 10, and during most of the time when the server 20 and the user equipment 10 are not in communication, the user equipment 10 may not have a dedicated IP address and bearer, thereby effectively saving network overhead.

Example 7

Embodiment 5 of the present invention provides a service communication method for identifying and triggering a communication connection between a terminal device and a server in M2M communication. In this embodiment, the terminal device such as the user equipment is a simple terminal, and has a single service. The user equipment and the peer end, for example, when the user equipment and the server need to communicate, then trigger the request and temporarily set up the bearer to implement the user equipment and Information exchange between servers.

As shown in FIG. 12 and FIG. 13 , the service communication method in this embodiment includes the following steps: Step 601: A service management center receives a trigger request of a server, where the trigger request carries a user equipment identifier and data.

Step 602: The service management center determines a user equipment corresponding to the user equipment identifier The currently registered core network node;

Step 603: The service management center sends a setup bearer request to the core network node, where the establishing a bearer request causes the core network node to request the user equipment to establish the user equipment after paging the user equipment access Bearer to the service management center;

Step 604: The service management center binds the bearer established by the user equipment to the user equipment identifier, and sends the data in the trigger request to the user equipment along the bearer. Step 605: The service management center receives the message that the user equipment responds along the bearer and sends the response message to the server to complete communication between the server and the user equipment.

In the foregoing step 601, the identifier of the user equipment may be an internal identifier or an external identifier. If it is an external identifier, it needs to be converted into an internal identifier for identification within the network. The specific conversion process is to first obtain the corresponding APN information according to the server address information; and then find the corresponding IMF according to the APN information; and then query the corresponding IMF. The internal identifier corresponding to the external identifier is returned to the service management center by the IMF after the conversion is completed; if it is the internal identifier, the service management center directly uses the conversion without using the conversion.

As shown in FIG. 14, the service management center in the foregoing steps 602 and 603 determines, by using the user equipment identifier, a core network node that is registered by the current user equipment, and pages the user equipment identifier through the core network node. The actions of the corresponding user equipment include:

Step 701: Determine a core network node that is registered by the user equipment.

Step 702: Send the user equipment identifier and the APN information of the service management center to the core network node.

Step 703: The core network node pages the user equipment according to the user equipment identifier. In the foregoing step 701, if the service management center already knows the address information of the user equipment, directly find the core network node corresponding to the user equipment by using the address information; if the service management center does not know the address information of the user equipment Then, the HSS 60 needs to first query the address information of the user equipment corresponding to the user equipment identifier. The core network node may be an MME (Mobility Management Entity) or an SGSN (Serving GPRS Support Node). In the foregoing step 702, the server is communicated to the core network node in the service management center. When the request and the user equipment identifier of the triggering object are triggered, the service management center simultaneously sends its APN information to the core network node.

If the paging of the user equipment fails in step 703, the subsequent step becomes that the core network node directly responds to the service management center to send an uplink message that fails to be sent, and then the service management center notifies the user equipment that the trigger fails, and the trigger fails. The user equipment is not paged due to network congestion or abnormality.

In the above step 603, the service management center sends the user equipment identifier and the APN information of the service management center to the core network node, and the core network node sends the APN information to the user equipment. Establishing a bearer request carries the APN information of the service management center.

In the foregoing step 603, the user equipment establishes a bearer of the service management center corresponding to the APN information according to the APN information of the service management center in the request of the core network node, and does not need to allocate the user equipment IP address.

In the above step 604, after the service management center binds the bearer to the user equipment identifier and sends the data in the trigger request to the user equipment along the bearer, the user equipment The bearer sends the response data of the user equipment to the service management center, and the service management center returns the response data and the user equipment identifier to the server, thereby completing the triggering of the server by the server. Information exchange.

The method for triggering and identifying the user equipment may be that the user equipment finds and triggers the user equipment to establish a temporary bearer only when the user equipment or the server sends data to the peer end, and the server and the user equipment are along the temporary bearer. Temporary information interaction can be performed, and in the majority of the time when the server and the user equipment do not communicate, the user equipment can have no dedicated IP address and bearer, thereby effectively saving network overhead. Example eight

As shown in FIG. 15, a ninth embodiment of the present invention provides a service communication apparatus corresponding to the service communication method of the seventh embodiment, which is used to trigger communication between the user equipment and the server.

The device includes:

a requesting unit, configured to send a setup bearer request to the core network node, where the establishing a bearer request, after the user equipment accesses, requesting the user equipment to establish the user equipment to the service management center Bearer

And a second receiving unit, configured to receive a message that the user equipment responds along the bearer, and send the response message to the server, to complete communication between the server and the user equipment.

After the positioning unit determines the core network node that is currently registered by the user equipment corresponding to the user equipment identifier, the user equipment identifier and the APN information of the service management center are sent to the core network node, where The core network node carries the APN information of the service management center in the setup bearer request to the user equipment, and the user equipment establishes the bearer of the service management center corresponding to the APN information according to the APN information of the service management center.

Example nine

As shown in FIG. 6, the ninth embodiment of the present invention provides a service communication system, including a server 20, a core network node 40, and a service management center 30.

Before the server 20 communicates with the user equipment 10, the server 20 sends a trigger request of the user equipment 10 to the service management center 30, where the trigger request carries the user equipment identifier and data; the service management center 30 passes the user equipment. The identifier determines the core network node 40 registered by the user equipment 10; the service management center 30 sends a setup bearer request to the core network node 40, so that the core network node 40 requests after paging the user equipment 10 to access User equipment 10, the bearer of the user equipment 10 to the service management center 30 is established; and the user equipment 10 corresponding to the user equipment identifier is paged by the core network node 40; the user equipment 10 is according to the core network The request of the node 40 establishes the bearer; the service management center 30 binds the bearer to the user equipment identifier and sends the data in the trigger request to the user equipment 10 along the bearer; The management center 30 receives the message that the user equipment 10 responds along the bearer and sends the response message to the server 20.

The service communication system of the embodiment of the present invention further includes an IMF 50.

The user equipment identifier carried in the trigger request may be an internal identifier or an external identifier. If it is an external identifier, it needs to be converted into an internal identifier for intra-network identification. The specific conversion process is to first obtain the corresponding APN information according to the address information of the server 20; then find the corresponding IMF 50 according to the APN information; and then query the corresponding IMF 50. The internal identifier corresponding to the external identifier is returned to the service management center 30 after the IMF 50 completes the conversion; if it is the internal identifier, the service management center 30 is directly used without conversion.

The service management center 30 finds the core network node 40 registered by the user equipment 10 corresponding to the user equipment identifier by using the user equipment identifier, and must first know the address information of the user equipment 10.

The service communication system in this embodiment further includes an HSS 60. Specifically, if the service management center 30 already knows the address information of the user equipment 10 corresponding to the user equipment identifier, the user equipment is directly found by using the address information. 10 corresponding core network node 40; if the service management center 30 does not know the address information of the user equipment 10, the HSS 60 needs to first query the address information of the user equipment 10 corresponding to the user equipment identifier.

After the corresponding core network node 40 is found, the service management center 30 transmits the APN information corresponding to the triggering request of the server 20 and the user equipment identifier of the triggering object to the core network node 40. The core network node 40 is described. The setup bearer request sent by the core network node 40 to the user equipment 10 carries the APN information of the service management center 30. After the user equipment 10 binds the bearer to the user equipment identifier in the service management center 30 and sends the data in the trigger request to the user equipment 10 along the bearer, the user equipment 10 may follow the bearer along the bearer. The response data of the user equipment 10 is sent to the service management center 30, and the service management center 30 returns the response data and the user equipment identifier to the server 20, thereby completing the server 20 to the designated user equipment 10. The trigger interacts with the information.

The device for triggering and identifying the user equipment may find and trigger the user equipment 10 to establish a temporary bearer by using the user equipment identifier only when the user equipment 10 or the server 20 is to send data to the opposite end. The server 20 and the user equipment 10 The interim temporary bearer can perform temporary information exchange, and in the majority of the time when the server 20 and the user equipment 10 are not in communication, the user equipment 10 can have no dedicated IP address and bearer in time, thereby effectively saving network overhead.

The foregoing embodiment of the present invention mainly relates to a single triggering of a user equipment, and in other embodiments, a group triggering may be performed. At this time, the triggering request will carry multiple user equipment address information instead of the identifier of the user equipment, indicating that the server All the user equipments corresponding to the address information are triggered, and the data is directly sent by the service management center in the form of cell broadcast or multicast broadcast, or may be converted into multiple single triggers according to the binding relationship of the APNs. The bearer of the user equipment belonging to the APN sends data, or the data is sent after the bearer is established.

In addition, regardless of whether the user equipment is a simple terminal or a complex terminal, since the user equipment has only one communication peer in the server within one APN. Then, when the user equipment wants to send data, or attaches, the user equipment can be directly established to the P-GW, and then the P-GW goes to the service management center and the tunnel to the service management center to the server, and the user equipment or the server can follow the tunnel. Send or respond to the data to the peer.

The user equipment in the foregoing embodiment of the present invention may be an MTC Device in M2M communication, the server may be an MTC Server in M2M communication, and the service management center may be an M2M Service Management Center (MSMC, M2M Service Management). Centre), or a logical entity such as a Proxy.

In addition, the description of the present invention is described by taking an SAE/LTE network as an example. In actual implementation, Use other networks (such as 2G/3G or WiMAX/3GPP2 networks). In this case, the network implementation entity is different. For example, when using 2G/3G network, MME will be replaced by SGSN as core network entity, HSS will be Instead of HLR (Home Location Register), P-GW will be replaced by GGSN (Gateway GPRS Support Node).

In the M2M communication application, since the server does not communicate with the user equipment most of the time, other embodiments of the present invention can be similar to the first embodiment, and after the communication between the server and the user equipment is completed, the communication is released. The IP of the user equipment or the bearer between the user equipment and the server is released, thereby effectively saving network resource overhead.

The communication system provided by the embodiment of the present invention is described in detail above, and the principles and implementation manners of the present invention are described in the following. The description of the above embodiments is only used to help understand the method and core idea of the present invention. At the same time, the content of the present invention is not limited by the scope of the present invention.

Claims

Rights request

A service communication method, characterized in that: the method comprises:

The service management center receives a trigger request sent by the server, where the trigger request carries the user equipment identifier;

Determining, by the service management center, a core network node currently registered by the user equipment corresponding to the user equipment identifier;

The service management center sends an IP address allocation request of the user equipment to the core network node, where the IP address allocation request is used to trigger the core network node to page the user equipment according to the user equipment identifier and is also used to After the user equipment accesses the network, the bearer is established and the IP address is obtained; the service management center sends a message carrying the IP address of the user equipment to the server;

Establishing communication between the server and the user equipment according to the bearer and the IP address established by the user equipment.

The method according to claim 1, wherein the user equipment identifier carried in the trigger request is an internal identifier or an external identifier, and if the user equipment identifier carried in the trigger request is an external identifier, Before determining, by the service management center, the core network node currently registered by the user equipment corresponding to the user equipment identifier, the method further includes: converting the external identifier into an internal identifier.

3. The method according to claim 2, wherein the converting the external identifier to an internal identifier comprises:

The service management center acquires an APN (Access Point Name) information corresponding to the server according to the address information of the server;

Determining a corresponding IMF (identity mapping function) according to the APN information;

And querying, by the IMF, an internal identifier corresponding to the external identifier of the user equipment;

The service management center receives the internal identifier sent by the IMF.

The method according to claim 1, wherein the determining, by the service management center, the core network node currently registered by the user equipment corresponding to the user equipment identifier comprises: the service management center according to The address information of the user equipment corresponding to the user equipment identifier determines a core network node that is currently registered by the user equipment.

The method according to claim 1 or 4, wherein the service management center queries the HSS (Home Subscriber Server) for the address information of the user equipment corresponding to the user equipment identifier, and then passes the The address information determines a core network node that is currently registered by the user equipment.

The method according to claim 1, wherein the IP address allocation request carries APN information corresponding to the server, and after the user equipment accesses the network, the core network node uses the server The corresponding APN information is sent to the user equipment, and the bearer of the user equipment to the APN corresponding to the server is established.

The method according to claim 6, wherein the bearer is a PDN (Packet Data Network) or a PDP of the user equipment to the service management center.

(Packet Data Protocol) connection.

The method according to claim 6, wherein the bearer is a PDN or a PDP of the P-GW (Packet Data Network Gateway) corresponding to the APN of the server. connection.

The method according to claim 6 or 7, wherein in the process of establishing the bearer, an AAA server (Authentication, Authorization, Accounting, Authentication and Authorization Accounting Server) is used to assign an IP address to the user equipment. .

The method according to any one of claims 1, 2, 3, 4, 6 and 7, wherein the core network node is an MME (Mobility Management Entity) or an SGSN (Serving GPRS Support) Node, service GPRS support node).

The method according to any one of claims 1, 2, 3, 4, 6 and 7, wherein, after the communication between the server and the user equipment is completed, the method further includes: The service management center receives the notification that the user equipment releases the IP address; the service management center notifies the server to delete the correspondence between the IP address and the user equipment.

The method according to claim 11, wherein the notification that the user equipment releases the IP address is first notified by the user equipment to the core network node, and then sent by the core network node to the service. control center.

13. A service communication device, the device comprising:

a receiving unit, configured to receive a trigger request sent by the server, where the trigger request carries a user equipment identifier;

a requesting unit, configured to send an IP address allocation request of the user equipment to the core network node, where the IP address allocation request is used to trigger the core network node to page the user equipment according to the user equipment identifier and also used to After the user equipment accesses the network, the bearer is set up and obtains an IP address; the sending unit is configured to send, to the server, a message that carries the IP address of the user equipment, and the processing unit is configured to use, according to the bearer established by the user equipment, The IP address establishes communication between the server and the user equipment.

The device according to claim 13, wherein the receiving unit receives the user equipment identifier carried in the trigger request sent by the server as an internal identifier or an external identifier, if the user equipment identifier carried by the trigger request For external identification, the receiving module converts the external identifier into an internal identifier.

The device according to claim 13, further comprising:

Notifying the server, the server is notified to delete the corresponding address of the IP address and the user equipment

A service communication system, comprising: a server, a core network node, and a service management center, wherein the server sends a trigger request of the user equipment to the service management center before the server communicates with the user equipment, where the trigger Requesting to carry the user equipment identifier; the service management center determines a core network node that is registered by the user equipment corresponding to the user equipment identifier, and sends an IP address allocation request of the user equipment to the core network node; The network node pages the user equipment to access the network according to the user equipment identifier; the IP address allocation request triggers the user equipment to establish a bearer and acquires an IP address; the core network node sends the The server responds with a message carrying the user equipment IP address information; the server establishes communication with the user equipment according to the bearer and IP address information established by the user equipment.

The system according to claim 16, wherein the user equipment identifier carried in the trigger request sent by the server to the service management center is an internal identifier or an external identifier.

The system according to claim 17, wherein the user equipment identifier carried in the trigger request is an external identifier, the device further includes an IMF, and the IMF corresponds to the APN information of the server, Converting the user equipment external identifier into a corresponding internal identifier and returning to the service management center.

The system according to claim 16, wherein the service management center determines a core network node currently registered by the user equipment by using address information of the user equipment corresponding to the user equipment identifier.

The system according to claim 19, further comprising an HSS, configured to provide the service management center with address information of a core network node where the user equipment corresponding to the user equipment identifier is located.

The system according to claim 16, wherein the IP address allocation request carries APN information corresponding to the server, and after the user equipment accesses the network, the core network node uses the server Corresponding APN information is sent to the user equipment and the use is established. The bearer of the user equipment to the APN corresponding to the server

The system according to claim 16, wherein the bearer is a PDN or PDP connection of the user equipment to the service management center.

The system according to claim 16 or 22, further comprising an AAA server, configured to allocate an IP address to the user equipment in the process of establishing the bearer.

A service communication method, configured to trigger communication between a user equipment and a server, wherein the method includes:

The service management center receives a trigger request of the server, where the trigger request carries the user equipment identifier and the data;

Sending, by the service management center, a request for triggering the user equipment to the core network node, so that the core network node pages the user equipment according to the user equipment identifier, and after the user equipment accesses the network, Transmitting, by the core network node, data in the trigger request to the user equipment;

Receiving, by the service management center, a response message of the user equipment, where the response message is sent by the core network node to the service management center;

The service management center sends a response message of the user equipment to the server to complete communication between the server and the user equipment.

The method according to claim 24, wherein the user equipment identifier carried in the trigger request is an internal identifier or an external identifier, and if the user equipment identifier carried in the trigger request is an external identifier, The business management center is converted to an internal identifier by the IMF where the server is located.

The method according to claim 24, wherein the service management center and the server are non-signaling connection communications, and the step of the service management center receiving the response message of the user equipment includes: Receiving, by the core network node, data that is sent by the user equipment;

The core network node sends a response message to the service management center, where the response message includes data that is responded to by the user equipment and the user equipment identifier.

The method according to claim 24, wherein the service management center and the server are connection-oriented signaling communications, and the step of the service management center receiving the response message of the user equipment includes:

Receiving, by the core network node, data that is sent by the user equipment;

The core network node sends a response message to the service management center, where the response message includes data that is responded to by the user equipment.

The method according to claim 27, wherein the server acquires the identification information of the responding user equipment according to the signaling connection information.

The method according to any one of claims 24 to 28, wherein the core network node is an MME or an SGSN.

30. A service communication device, configured to trigger communication between a user equipment and a server, and the method includes:

a sending unit, configured to send a response message of the user equipment to the server, to complete The communication between the server and the user equipment.

31. A service communication system, comprising: a server, a core network node, and a service management center, wherein, before the server communicates with the user equipment, the server sends a trigger request of the user equipment to the service management center, where the trigger Requesting to carry the user equipment identifier and the data; the service management center determines, by the user equipment identifier, the core network node that is registered by the user equipment, and pages the user equipment corresponding to the user equipment identifier by using the core network node; After the user equipment is accessed, the core network node sends the data in the trigger request to the user equipment; the user equipment sends a response message to the service management center through a core network node; The response message is returned to the server.

The system according to claim 31, wherein the service management center and the server are non-signaling connection communications, and the user equipment sends a response message to the service management center through the core network node. The core network node first receives the data that the user equipment responds to; the core network node sends a response message to the service management center, where the response message includes the data that the user equipment responds to and the User device ID.

The system according to claim 31, wherein the service management center and the server are connection-oriented signaling communications, and the user equipment sends a response message to the service management center through the core network node. In the process, the core network node first receives the data that the user equipment responds to; the core network node sends a response message to the service management center, where the response message includes data that is responded by the user equipment.

The method according to claim 33, wherein the server acquires the identification information of the responding user equipment according to the signaling connection information.

35. A service communication method, the method comprising:

Determining, by the service management center, a core network node currently registered by the user equipment corresponding to the user equipment identifier; The service management center sends a setup bearer request to the core network node, where the establishment of the bearer request causes the core network node to request the user equipment to establish the user equipment to the service after paging the user equipment access Bearer of the management center;

The service management center binds the bearer established by the user equipment to the user equipment identifier, and sends the data in the trigger request to the user equipment along the bearer;

The service management center receives a message that the user equipment responds along the bearer and sends the response message to the server to complete communication between the server and the user equipment.

The method according to claim 35, wherein the establishing a bearer request sent by the core network node includes the user equipment identifier and APN information of the service management center.

The method according to claim 36, wherein the service management center sends a request for establishing a bearer request to the core network node, where the core network node carries the request for establishing a bearer to the user equipment. There is APN information of the service management center.

The method according to claim 37, wherein the user equipment establishes a bearer to the service management center corresponding to the APN information according to the APN information of the service management center.

The method according to any one of claims 35 to 38, wherein the core network node is an MME or an SGSN.

40. A service communication device, configured to trigger communication between a user equipment and a server, and the method includes:

a requesting unit, configured to send a setup bearer request to the core network node, where the establishing a bearer request, after the user equipment accesses, requesting the user equipment to establish the user equipment to the service management center Bearer And a second receiving unit, configured to receive a message that the user equipment responds along the bearer, and send the response message to the server, to complete communication between the server and the user equipment.

The device according to claim 40, wherein after the positioning unit determines a core network node currently registered by the user equipment corresponding to the user equipment identifier, the user equipment identifier and the service are The APN information of the management center is sent to the core network node, and the core network node carries the APN information of the service management center in the request for establishing a bearer to the user equipment, where the user equipment is based on the APN of the service management center. The information is established to the bearer of the service management center corresponding to the APN information.

42. A service communication system, comprising: a server, a core network node, and a service management center, wherein the server sends a trigger request of the user equipment to the service management center before the server communicates with the user equipment, where The triggering request carries the user equipment identifier and the data; the service management center determines the core network node that is registered by the user equipment by using the user equipment identifier; the service management center sends a setup bearer request to the core network node, so that After the user equipment accesses the network, the core network node requests the user equipment to establish a bearer from the user equipment to the service management center; the user equipment establishes the bearer according to the request of the core network node. The service management center binds the bearer to the user equipment identifier and sends the data in the trigger request to the user equipment along the bearer; the service management center receives the user equipment along the Carrying a response message and sending the response message to the server

The system according to claim 42, wherein the request for the service management center to send the bearer to the core network node includes the user equipment identifier and the APN information of the service management center.

The system according to claim 43, wherein the core network node carries the APN information of the service management center in the setup bearer request to the user equipment.

The system according to claim 44, wherein the user equipment establishes an APN corresponding to the APN information according to the APN information of the service management center in the setup bearer request.