WO2017004805A1

WO2017004805A1 - Method and device for data transmission

Info

Publication number: WO2017004805A1
Application number: PCT/CN2015/083545
Authority: WO
Inventors: 黄正磊; 张万强
Original assignee: 华为技术有限公司
Priority date: 2015-07-08
Filing date: 2015-07-08
Publication date: 2017-01-12
Also published as: CN107005838A; CN107005838B

Abstract

Embodiments of the present invention provide a method and device for data transmission, and the method comprises: when the downlink data of a user equipment transmitted by a data transmission end is unreachable, a mobility management entity transmits a first instruction message to a service gateway for instructing the service gateway to cache the downlink data; the mobility management entity determines that a second instruction message needs to be transmitted to the data transmission end; and the mobility management entity transmits the second instruction message to the data transmission end, so that the data transmission end transmits the downlink data of the user equipment according to the second instruction message. With the embodiments of the present invention, the data transmission end can flexibly transmit downlink data according to the second instruction message, and unnecessary data transmission is avoided and the network efficiency is improved.

Description

Method and device for data transmission

Technical field

The present invention relates to the field of communications and, more particularly, to a method and apparatus for data transmission.

Background technique

In order to support the evolution of the wireless side (such as LTE), the 3rd Generation Partnership Project ("3GPP") began to study the system architecture evolution (System Architecture Evolution, referred to as "the network side" in December 2004. SAE"). LTE and SAE together constitute an Evolved Packet System ("EPS"). The EPS network architecture adopts an end-to-end Internet Protocol (IP) networking and a flat network structure, and fully considers compatibility with existing 2G/3G networks.

In the EPS network architecture, the main network functional entities are:

1) Evolved Universal Terrestrial Radio Access Network (EUTRAN): a network composed of multiple eNodeBs for implementing wireless physical layer functions, resource scheduling functions, and radio resource management functions. , wireless access control functions and mobility management functions. The eNodeB is connected to the serving gateway (Serving Gateway, referred to as "S-GW") through the user plane interface S1-U for transmitting user data; the eNodeB is connected to the MME through the control plane interface S1-MME, and adopts the S1-AP protocol. Realize functions such as radio access bearer control.

2) Mobility Management Entity (MME): It is mainly responsible for all control plane functions of user session management, including non-access stratum (Non Access Stratum, referred to as "NAS") signaling and security. Management of the tracking area, PDN Gateway (P-GW), and S-GW selection.

3) S-GW: mainly responsible for data transmission, forwarding, and routing switching of user equipment (User, Equipment, referred to as "UE"), and as a local mobility anchor point when the UE switches between eNodeBs, for each The UE has only one S-GW serving it at a time.

4) P-GW: as an anchor point for the packet data network (Packet Data Network, referred to as "PDN") connection, responsible for the Internet Protocol (Internet Protocol, "IP") address allocation of the UE, and data packet filtering of the UE. , rate control, generation of billing information, and so on.

In the EPS network architecture, the EPS connection management of the UE (EPS Connection Management, The state referred to as "ECM" for short includes: ECM-IDLE (ie, idle state) and ECM-CONNECTED (ie, connected state), which reflects the signaling connection characteristics of the UE.

In the idle state (ECM-IDLE), there is no NAS signaling connection between the UE and the network, for example, does not include a Radio Resource Control (RRC) connection and an S1-MME connection; State (ECM-CONNECTED), there is a NAS signaling connection between the UE and the network, including RRC connection and S1-MME connection.

If there is no data transmission for a long time, that is, when there is no NAS signaling connection between the UE and the network, the UE enters an idle state. In the idle state, the UE mainly listens to the call channel and the broadcast channel. If the UE wants to listen to the user data channel, it must switch from the idle state to the connected state. For example, if the UE is in an idle state, when the EPS network receives the downlink data packet or signaling of the UE, the EPS network initiates a network side trigger service request process, in which the MME is in the tracking area where the current UE is located. Initiating paging, the UE will switch to the connected state in response to the MME's paging, and then listen to the user data channel to receive data or signaling. The network side triggers the service request process as follows:

Step 1: After the S-GW receives the downlink data packet of the UE, the S-GW sends a downlink data notification message to the MME.

Step 2: After receiving the downlink data notification message, the MME searches for the corresponding UE context, and returns an acknowledgement message to the S-GW.

Step 3: The MME sends a paging to all the eNodeBs in the tracking area where the UE is located, and the paging message sent to the eNodeB carries the UE identity (IMSI or P-TMSI, etc.) of the UE, paging priority, and the like;

Step 4: The eNodeB pages the UE according to the received paging message.

Step 5: The UE responds to the paging, initiates a service request procedure, establishes a user plane, and starts preparing to receive downlink data.

In order to reduce the power consumption of the user equipment, the user equipment can enable the power save mode (PSM). The user equipment requests an active time (Active Time) from the network side. Each time the user equipment changes from the connected state to the idle state, the user equipment starts a timer (the time value of the timer is the active time). When the timer expires, the user equipment enters the power saving mode from the idle state. In the power saving mode, the user equipment no longer listens to the paging message on the network side, that is, the user equipment does not respond to the paging on the network side.

Discontinuous Reception (DRX) is a kind of saving UE. The mode of operation of electricity consumption. If the UE adopts DRX, the UE only turns on the receiver to enter the activation period for a certain period of time to receive downlink data and signaling, and turns off the receiver to enter the sleep period at other time periods, and stops receiving downlink data and signaling.

DRX includes two types: idle state DRX (referred to as "I-DRX") and connected state DRX (referred to as "C-DRX"). The idle state DRX, as the name implies, is when the UE is in the idle (IDLE) state. Discontinuous reception (DRX), connected state DRX is the discontinuous reception (DRX) in which the UE is in the connected state.

The DRX cycle is called the DRX cycle, and one DRX cycle is divided into an active phase and a dormant phase. The DRX cycle is further divided into a long cycle and a short cycle, wherein the long cycle sleep period is longer, and the short cycle sleep period is shorter, and the long period and the short period activation period are the same. In addition, the long period is an integer multiple of the short period.

When the user equipment (UE) in the idle state has downlink data arriving, the network initiates paging to the UE. However, the temporary interruption of the wireless signal or the power saving function such as the PSM and the long-cycle DRX enabled by the UE will cause the UE to fail to respond to the paging of the network. The service application continuously retransmits data, thereby increasing the load and paging overhead of the core network element.

To avoid this problem, the MME may instruct the S-GW to buffer the downlink data of the delay tolerant service, and then send the buffered data to the UE when the UE is reachable. The MME may provide the S-GW with the buffer time T and/or the number of cached packets N, where the cache time T is related to the power saving mechanism adopted by the UE and the delay requirement of the application, and the N may be based on the subscription data (user priority, packet loss) Rate, etc.) to determine. The S-GW determines the number M of data packets that can be buffered based on the N provided by the MME and its own configuration. The S-GW buffers the downlink data of the UE according to the MME indication. When the timer T times out or the number of received data packets exceeds M, the S-GW may discard the buffered data packet.

When the timer T times out or the number of received packets exceeds M, the S-GW will discard the buffered packets. At this time, the data sending end, such as an application server (AS) or a service capability server (SCS), does not know whether the UE is reachable, and still continues to retransmit or send new downlink data packets. Since the S-GW does not buffer the received downlink data packet, the downlink data transmission or retransmission of the data transmitting end is unnecessary, thereby increasing the load of the core network node and causing waste of network resources.

Summary of the invention

Embodiments of the present invention provide a data transmission method and device, which can flexibly transmit downlink data, avoid unnecessary data transmission, and improve network efficiency.

The first aspect provides a data transmission method, including: when the downlink data of the user equipment sent by the data sending end is unreachable, the mobility management entity sends a first indication message to the serving gateway, where the first indication message is used. Instructing the service gateway to buffer the downlink data;

The mobility management entity determines that a second indication message needs to be sent to the data sender;

The mobility management entity sends the second indication message to the data sending end, so that the data sending end sends the downlink data of the user equipment according to the second indication message.

With reference to the first aspect, in a first possible implementation manner, the first indication message carries indication information indicating that the serving gateway caches the downlink data, where the indication information includes a duration and/or a number of data packets,

The second indication message carries the indication information.

In combination with the first aspect or the first possible implementation manner, in the second possible implementation manner, when the downlink data of the user equipment sent by the mobility management entity at the data sending end is unreachable, the first information is sent to the serving gateway. Before indicating the message, the method further includes:

The mobility management entity obtains a first request message sent by the data sending end, where the first request message is used to request the network to feed back the second indication message when the downlink data of the user equipment is unreachable, and the first request message carries the The address information of the data sender and the identifier of the user equipment,

The mobility management entity determines that the second indication message needs to be sent to the data sending end, including:

And if the mobility management entity determines that the identifier of the user equipment is the same as the identifier of the user equipment carried in the first request message, the mobility management entity determines that the second indication message needs to be sent to the data sending end.

With reference to the first aspect, any one of the first to the second possible implementation manners, in a third possible implementation manner, the mobility management entity sends the data to the data sending end Before the second indication information, the method further includes:

The mobility management entity generates the second indication message.

With reference to the first aspect, any one of the first to the second possible implementation manners, in a fourth possible implementation, the first indication message is further used to indicate that the serving gateway generates the first Two indication messages,

Before the mobility management entity sends the second indication information to the data sending end, the method further includes:

The mobility management entity receives the second indication message sent by the serving gateway.

With reference to the first aspect or the first possible implementation manner, in a fifth possible implementation manner, the mobility management entity determines that the second indication message needs to be sent to the data sending end, including:

If the mobility management entity determines that the identifier of the user equipment is the same as the identifier of the user equipment, the mobility management entity determines that the second indication message needs to be sent to the data sending end, where the preset The feedback identifier list includes an identifier of the user equipment that needs to feed back the second indication message.

In conjunction with the fifth possible implementation, in a sixth possible implementation, the first indication message is further used to indicate that the serving gateway sends the address information of the data sending end to the mobility management entity, where the mobility management is performed. Before the entity sends the second indication information to the data sending end, the method further includes:

Receiving, by the mobility management entity, address information of the data sending end sent by the serving gateway;

The mobility management entity generates the second indication message, where the second indication message carries address information of the data sending end.

In conjunction with the fifth possible implementation, in a seventh possible implementation, the first indication message is further used to indicate that the serving gateway generates the second indication message,

Before the mobility management entity sends the second indication message to the data sending end, the method further includes:

With reference to the first aspect, the possible implementation manner of any one of the first to the seventh possible implementation manners, in the eighth possible implementation manner, the method further includes:

The mobility management entity receives an acknowledgment message sent by the data sending end, where the acknowledgment message is used to indicate that the data sending end has received the second indication message.

A second aspect provides a data transmission method, including: acquiring, by a data sending end, a second indication message, where the second indication message is generated after the serving gateway receives the first indication message, where the first indication message is used by The downlink data of the user equipment that indicates that the service gateway buffers downlink data unreachable;

The data sending end sends the downlink data of the user equipment according to the second indication message.

With reference to the second aspect, in a first possible implementation manner, the first indication message carries indication information indicating that the serving gateway caches the downlink data, where the indication information includes a duration and/or a number of data packets,

The second indication message carries the indication information.

among them,

When the indication information includes the duration, the data sending end sends the downlink data of the user equipment according to the second indication message, including:

The data sending end determines, according to the second indication message, downlink data that is sent by the user equipment in the duration,

When the indication information includes the number of the data packets, the data sending end sends the downlink data of the user equipment according to the second indication message, including:

The data sending end sends the downlink data of the user equipment according to the second indication message, and the number of data packets of the downlink data of the user equipment sent by the data sending end is less than or equal to the number of the data packets.

When the indication information includes the duration and the number of the data packets, the data sending end sends the downlink data of the user equipment according to the second indication message, including:

The data sending end determines, according to the second indication message, that the downlink data of the user equipment is sent in the duration, and the number of data packets of the downlink data of the user equipment that is sent by the data sending end is less than or equal to the duration of the data. The number of packets.

With reference to the first possible implementation manner of the second aspect, in a second possible implementation manner, when the indication information includes the duration, or the indication information includes the duration and the number of the data packets, the method further include:

The data sending end determines, according to the second indication message, that the downlink data of the user equipment is not sent at a time other than the duration.

With reference to the second aspect, any one of the first to the second possible implementation manners of the second aspect, in a third possible implementation, the second indication message is obtained at the data sending end Previously, it also included:

The data sending end sends a first request message, where the first request message is used to request the network to feed back the second indication message when the downlink data of the user equipment is unreachable, where the first request message carries the address information of the data sending end and the The identifier of the user device.

With reference to the second aspect, the possible implementation manner of any one of the first to the third possible implementation manners of the second aspect, in the fourth possible implementation manner, the method further includes:

The data sending end sends an acknowledgment message to the mobility management entity, where the acknowledgment message is used to indicate that the data sending end has received the second indication message.

In a third aspect, a data transmission method is provided, including: a service gateway receiving a mobility tube a first indication message sent by the physical entity, where the first indication message is used to indicate that the serving gateway caches downlink data of the user equipment that is not reachable by the data sending end, and generates a second indication message;

The service gateway obtains address information of the data sending end;

The serving gateway generates and sends a second indication message according to the indication of the first indication message and the address information of the data sending end, so that the data sending end sends the downlink data of the user equipment according to the second indication message.

With reference to the third aspect, in a first possible implementation, the first indication message carries indication information indicating that the serving gateway caches the downlink data, where the indication information includes a duration and/or a number of data packets.

The second indication message carries the indication information.

With reference to the third aspect, or the first possible implementation manner of the third aspect, in a second possible implementation manner, the first indication message carries the address information of the data sending end,

The service gateway obtains the address information of the data sending end, including:

The serving gateway acquires address information of the data sending end according to the first indication message.

With reference to the third aspect, or the first possible implementation manner of the third aspect, in a third possible implementation manner, the first indication message is further used to indicate that the serving gateway obtains address information of the data sending end,

The serving gateway performs detection of the downlink data according to the indication of the first indication message, and acquires address information of the data sending end.

A fourth aspect provides a data transmission method, including: receiving, by a serving gateway, a first indication message sent by a mobility management entity, where the first indication message is used to indicate that the downlink data sent by the serving gateway cache data sending end is unreachable Downlink data of the user equipment, and obtaining address information of the data sending end;

The serving gateway performs detection of the downlink data according to the indication of the first indication message, and acquires address information of the data sending end;

The service gateway sends the address information of the data sending end to the mobility management entity, so that the mobility management entity generates and sends a second indication message to the data sending end according to the address information of the data sending end, so that the data sending end And sending downlink data of the user equipment according to the second indication message.

With reference to the fourth aspect, in a first possible implementation manner, the first indication message carries indication information indicating that the serving gateway caches the downlink data, where the indication information includes a duration and/or a number of data packets,

The second indication message carries the indication information.

In a fifth aspect, a mobility management entity is provided, including:

a first determining unit, configured to send a first indication message to the serving gateway when the downlink data of the user equipment sent by the data sending end is unreachable, where the first indication message is used to indicate that the serving gateway caches the downlink data;

a second determining unit, configured to determine that the second indication message needs to be sent to the data sending end;

And a sending unit, configured to send the second indication message to the data sending end, so that the data sending end sends the downlink data of the user equipment according to the second indication message.

With reference to the fifth aspect, in a first possible implementation manner, the first indication message carries indication information indicating that the serving gateway caches the downlink data, where the indication information includes a duration and/or a number of data packets,

The second indication message carries the indication information.

With reference to the fifth aspect or the first possible implementation manner of the fifth aspect, in a second possible implementation manner, the method further includes:

An acquiring unit, configured to acquire, after the first determining unit sends the first indication message to the serving gateway, the first request message sent by the data sending end, where the first determining unit sends the first indication message to the serving gateway The request message is used to request the network to feed back the second indication message when the user equipment is unreachable, and the first request message carries the address information of the data sending end and the identifier of the user equipment.

And determining, by the second determining unit, that the identifier of the user equipment is the same as the identifier of the user equipment carried in the first request message, determining that the second indication message needs to be sent to the data sending end.

With reference to the fifth aspect, the first possible implementation manner of the first to the second possible implementation manners of the fifth aspect, in the third possible implementation manner, the method further includes:

The first generating unit is configured to generate the second indication message before the sending unit sends the second indication message to the data sending end.

With reference to the fifth aspect, any one of the first to the second possible implementation manners of the fifth aspect, in a fourth possible implementation, the first indication message is further used to indicate the The service gateway generates the second indication message, where the mobility management entity further includes:

The receiving unit is configured to receive the second indication message sent by the serving gateway before the sending unit sends the downlink data sending second indication message to the data sending end.

With reference to the fifth aspect or the first possible implementation manner of the fifth aspect, in the fifth possible implementation manner, the first determining unit determines that the preset feedback identifier list has the same identifier as the user equipment And determining, the second indication message needs to be sent to the data sending end, where the preset feedback identifier list includes an identifier of the user equipment that needs to feed back the second indication message.

With reference to the fifth possible implementation manner of the fifth aspect, in a sixth possible implementation, the first indication message is further used to indicate that the serving gateway sends the address information of the data sending end to the mobility management entity, where The mobility management entity also includes:

a first receiving unit, configured to receive address information of the data sending end sent by the serving gateway before the sending unit sends the downlink data sending indication information to the data sending end;

The second generating unit is configured to generate the second indication message, where the second indication message carries the address information of the data sending end, before the sending unit sends the downlink data sending indication information to the data sending end.

With the fifth possible implementation of the fifth aspect, in a seventh possible implementation, the first indication message is further used to indicate that the serving gateway generates the second indication message, where the mobility management entity further includes:

The second receiving unit is configured to receive the second indication message sent by the serving gateway before the sending unit sends the second indication message to the data sending end.

With reference to the fifth aspect, the first possible implementation manner of the first to the seventh possible implementation manners of the fifth aspect, in the eighth possible implementation manner, the method further includes:

The third receiving unit is configured to receive an acknowledgment message sent by the data sending end, where the acknowledgment message is used to indicate that the data sending end has received the second indication message.

In a sixth aspect, a data sending end is provided, including:

An acquiring unit, configured to obtain a second indication message, where the second indication message is generated after the serving gateway receives the first indication message, where the first indication message is used to indicate that the serving gateway caches the user equipment that the downlink data is unreachable Downstream data;

The first sending unit is configured to send downlink data of the user equipment according to the second indication message.

With reference to the sixth aspect, in a first possible implementation manner, the second indication message carries indication information that the serving gateway caches the downlink data, where the indication information includes duration and/or number of data packets. Project,

among them,

When the indication information includes the duration, the first sending unit determines, according to the second indication message, that the downlink data of the user equipment is sent within the duration,

When the indication information includes the number of the data packets, the first sending unit sends the downlink data of the user equipment according to the second indication message, and the number of data packets of the downlink data of the user equipment sent by the data sending end is less than or equal to The number of packets,

When the indication information includes the duration and the number of the data packets, the first sending unit determines, according to the second indication message, downlink data that is sent by the user equipment in the duration, and the data sending end is in the duration The number of data packets of downlink data sent by the user equipment is less than or equal to the number of data packets.

With reference to the first possible implementation manner of the sixth aspect, in a second possible implementation manner, when the indication information includes the duration, or the indication information includes the duration and the number of the data packets, the data is sent The terminal also includes:

And a determining unit, configured to determine, according to the second indication message, that downlink data of the user equipment is not sent at a time other than the duration.

With reference to the sixth aspect, the possible implementation manner of any one of the first to the second possible implementation manners of the sixth aspect, in a third possible implementation manner, the method further includes:

a second sending unit, configured to send a first request message, where the first request message is used to request the network to feed back the second indication message when the downlink data of the user equipment is unreachable, before the acquiring unit acquires the second indication message, where The first request message carries the address information of the data sending end and the identifier of the user equipment.

With reference to the sixth aspect, any one of the first to the third possible implementation manners of the sixth aspect, in a fourth possible implementation manner, the method further includes:

And a third sending unit, configured to send a downlink data sending confirmation message to the mobility management entity, where the confirming message is used to indicate that the data sending end has received the second indication message.

In a seventh aspect, a service gateway is provided, including:

a receiving unit, configured to receive a first indication message sent by the mobility management entity, where the first indication message is used to indicate that the serving gateway caches downlink data of the user equipment that is not reachable by the data sending end, and generates a second indication. Message

An obtaining unit, configured to obtain address information of the data sending end;

And a sending unit, configured to generate and send a second indication message according to the indication of the first indication message and the address information of the data sending end, so that the data sending end sends the downlink data of the user equipment according to the second indication message.

With reference to the seventh aspect, in a first possible implementation manner, the first indication message carries indication information indicating that the serving gateway caches the downlink data, where the indication information includes a duration and/or a number of data packets,

The second indication message carries the indication information.

With reference to the seventh aspect, or the first possible implementation manner of the seventh aspect, in a second possible implementation manner, the first indication message carries the address information of the data sending end,

The obtaining unit acquires address information of the data sending end according to the first indication message.

With reference to the seventh aspect, or the first possible implementation manner of the seventh aspect, in a third possible implementation, the first indication message is further used to indicate that the serving gateway obtains address information of the data sending end,

The acquiring unit performs detection of the downlink data according to the indication of the first indication message, and acquires address information of the data sending end.

In an eighth aspect, a service gateway is provided, including:

a receiving unit, configured to receive a first indication message sent by the mobility management entity, where the first indication message is used to indicate that the serving gateway caches downlink data of the user equipment that is not reachable by the data sending end, and obtains the data sending Address information of the terminal;

An acquiring unit, configured to perform detection of the downlink data according to the indication of the first indication message, and obtain address information of the data sending end;

a sending unit, configured to send the address information of the data sending end to the mobility management entity, so that the mobility management entity generates and sends the second indication message to the data sending end according to the address information of the data sending end, so that the The data sending end sends the downlink data of the user equipment according to the second indication message.

With reference to the eighth aspect, in a first possible implementation manner, the first indication message carries indication information indicating that the serving gateway caches the downlink data, where the indication information includes a duration and/or a number of data packets,

The second indication message carries the indication information.

Based on the foregoing technical solution, when the downlink data of the user equipment sent by the data sending end is unreachable, the mobility management entity sends a first indication message to the serving gateway, indicating the service. The traffic gateway buffers the downlink data; and the mobility management entity sends the second indication message to the data sending end, so that the data sending end sends the downlink data of the user equipment according to the second indication message, for example, the user equipment is sent for a certain duration. Downstream data, the downlink data of the user equipment is not transmitted at times other than the duration. Thereby, the downlink data can be flexibly transmitted, unnecessary data transmission is avoided, and network efficiency is improved.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings to be used in the embodiments of the present invention will be briefly described below. It is obvious that the drawings described below are only some embodiments of the present invention, Those skilled in the art can also obtain other drawings based on these drawings without paying any creative work.

FIG. 1 is a schematic diagram of a communication network scenario applicable to an embodiment of the present invention.

2 is a schematic flow chart of a communication method in accordance with one embodiment of the present invention.

3 is a schematic flow chart of a method of data transmission according to an embodiment of the present invention.

FIG. 4 is a schematic flowchart of a method of data transmission according to another embodiment of the present invention.

FIG. 5 is a schematic flowchart of a method of data transmission according to another embodiment of the present invention.

FIG. 6 is a schematic flowchart of a method of data transmission according to another embodiment of the present invention.

FIG. 7 is a schematic flowchart of a method of data transmission according to another embodiment of the present invention.

FIG. 8 is a schematic flowchart of a method of data transmission according to another embodiment of the present invention.

FIG. 9 is a schematic flowchart of a method of data transmission according to another embodiment of the present invention.

FIG. 10 is a schematic flowchart of a method of data transmission according to another embodiment of the present invention.

11 is a schematic block diagram of a mobility management entity in accordance with one embodiment of the present invention.

Figure 12 is a schematic block diagram of a data transmitting end in accordance with one embodiment of the present invention.

Figure 13 is a schematic block diagram of a service gateway in accordance with one embodiment of the present invention.

FIG. 14 is a schematic block diagram of a service gateway according to another embodiment of the present invention.

15 is a schematic block diagram of a mobility management entity in accordance with another embodiment of the present invention.

FIG. 16 is a schematic block diagram of a data transmitting end according to another embodiment of the present invention.

17 is a schematic block diagram of a service gateway in accordance with another embodiment of the present invention.

18 is a schematic block diagram of a service gateway in accordance with another embodiment of the present invention.

detailed description

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

It should be understood that the technical solution of the present invention can be applied to an Evolved Packet System ("EPS"), and can also be applied to other various communication systems, for example, Global System of Mobile communication (referred to as: "GSM") system, Code Division Multiple Access ("CDMA") system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (General) Packet Radio Service (referred to as "GPRS"), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE time division duplex (Time) Division Duplex (referred to as "TDD"), Universal Mobile Telecommunication System ("UMTS").

It should also be understood that in the embodiment of the present invention, a user equipment (User Equipment, referred to as "UE") may also be referred to as a terminal, a mobile terminal (Mobile Terminal), a mobile station (Mobile Station, abbreviated as "MS"), and the like. . The user equipment UE can communicate with one or more core networks via a Radio Access Network (Radio Access Network, hereinafter referred to as "RAN"). Specifically, for example, the user equipment UE may be a mobile phone (or "cellular" phone), a computer with a mobile terminal, and may also be a portable, pocket, handheld, computer built-in or vehicle-mounted mobile device, which The radio access network RAN exchanges languages and/or data. In addition, the user equipment UE may also be an MTC device such as a sensor. In addition, in the embodiment of the present invention, the mobile device UE may also be a mobile relay device, such as an access point (AP).

It should also be understood that, in the embodiment of the present invention, the radio access network RAN node may specifically be a base station, and the base station may be an evolved base station (Evolutional Node B, referred to as “eNB or e-NodeB”) in LTE. It may be a base station in GSM (Base Transceiver Station, abbreviated as "BTS"), and may also be a base station (NodeB, abbreviated as "NB") in WCDMA. The embodiment of the present invention is not limited, but for convenience of description, the following The embodiment will be described by taking an eNB as an example.

FIG. 1 is a schematic diagram of a communication network scenario applicable to an embodiment of the present invention. The logical architecture of the mobile communication network shown in FIG. 1 includes: user equipment 110, access network 120, and mobile management network element. 130. Service gateway 140, data gateway 150, and message data network 160. The user equipment 110 is connected to the access network 120 through a local wireless network or a limited network. The mobility management network element 130 is responsible for location management, connection management, security authentication, gateway selection, and the like of the user equipment 110. The service gateway 140 is local to the user equipment 110. The access gateway is responsible for access technology related connection management and data forwarding, and the data gateway 150 is a gateway for the user equipment to access the external message data network 160.

The logical architecture diagram corresponds to the actual network, and may be an Evolved Packet System (EPS) network. The access network may be a UTRAN (Universal Terrestrial Radio Access Network) or a GERAN (GSM EDGE Radio Access). Network, GSM/EDGE radio access network) or E-UTRAN (Evolved Universal Terrestrial Radio Access Network), the mobility management network element may be Mobility Management Entity (MME) or GPRS. The Serving GPRS Support Node (SGSN), the serving gateway may be a Serving Gateway (S-GW), and the data gateway may be a Packet Data Network Gateway (PDN-GW).

The network element device mainly involved in the embodiment of the present invention is described by way of example:

The mobility management entity MME: supports functions related to "downlink data transmission indication" processing, including request, generation and feedback of "downlink data transmission indication" message, and related local configuration policies.

Serving gateway S-GW: can support the functions related to the "downlink data transmission indication" process, including the generation and feedback of the "downlink data transmission indication" message, and provide the MME with information about the downlink data packet (such as source/destination IP address, etc.) ), and related local configuration strategies.

It should be noted that in order to enhance the network's ability to support new services such as Machine-To-Machine (M2M), 3GPP is conducting an Architecture Enhancements for Service Exposure (AESE) research project. A new network entity is defined in AESE: Service Capability Exposure Function (SCEF), which provides multiple service capabilities through one or more standard Application Programming Interfaces (APIs). The network can interact with external business applications to obtain information such as the communication mode of the user equipment (UE), such as data size, location, and mobility mode. The external service application can also obtain information about the connection property, reachability, and network status of the UE from the network through the API.

The following describes the network to the third-party application server (Application Server, AS) in conjunction with Figure 2. Knowing the process of UE connection attributes, how AESE provides multiple service capabilities through SCEF. Specifically, the process shown in FIG. 2 includes:

201, the P-GW finds that the UE establishes a new PDN connection;

202. The P-GW reports a PDN connection setup message to the SCEF, where the message includes the UE identifier, the APN, and the UE IP address.

203. The SCEF saves the received information and returns an acknowledgement message to the P-GW.

204. The AS sends a message request to the SCEF to notify the UE of the connection attribute, where the message includes the UE identifier and the IP packet filter information related to the specific service.

205. The SCEF authorizes the UE connection attribute request message of the AS.

206: The SCEF checks whether the PDN connection establishment indication information of the UE is received from the P-GW, and the IP address of the UE matches the IP filter information received from the AS. If the instructions have been received, proceed with the subsequent information flow;

207. The SCEF sends a UE connection attribute request message to the P-GW, where the message includes the UE identifier and the UE IP address information.

208. The P-GW returns, to the SCEF, PDN connection information related to the UE IP address, such as an IP-CAN type, a RAT type, an APN-AMBR, and the like. The SCEF generates a corresponding UE connection attribute according to the received PDN connection information.

209. The SCEF notifies the third-party AS of the UE connection attribute information.

It should be understood that the mobility management entity in the embodiment of the present invention may be an MME or an SGSN; the serving gateway may be an S-GW or an SGSN; the user equipment may be an MS or a UE; and the data sending end may be It is a third-party AS, and may be a Service Capability Server (SCS). The embodiment of the present invention does not limit this.

It should also be understood that the first indication message in the embodiment of the present invention may also be referred to as a downlink data notification acknowledgement DDNA message, and the second indication message may also be referred to as a downlink data transmission indication message, and the first request message may be a downlink data transmission indication request. The message is not limited by this embodiment of the present invention.

In the following, the mobility management entity is the MME, the serving gateway is the S-GW, and the user equipment is the UE first indication message, which is the downlink data notification confirmation DDNA message, and the second indication message is the downlink data transmission indication message, and the first request message is the downlink data. The instruction request message is sent for example, but the embodiment of the present invention is not limited thereto.

It should be noted that the names of the first indication message, the second indication message, and the first request message in the embodiment of the present invention may all be messages of other names, as long as the corresponding functions of the messages can be implemented. That is, the embodiment of the invention is not limited thereto.

3 is a schematic flow chart of a method of data transmission according to an embodiment of the present invention. The method shown in FIG. 3 can be performed by a mobility management entity. Specifically, the method shown in FIG. 3 includes:

310. The mobility management entity sends a first indication message to the serving gateway when the downlink data of the user equipment sent by the data sending end is unreachable, where the first indication message is used to instruct the serving gateway to buffer the downlink data.

For example, when it is determined that the UE enables the power saving function such as PSM or long-period DRX, or the wireless signal is interrupted, the MME determines that the downlink data of the UE is unreachable.

320. The mobility management entity determines that the second indication message needs to be sent to the data sending end.

330. The mobility management entity sends a second indication message to the data sending end, so that the data sending end sends the downlink data of the user equipment according to the second indication message.

It should be understood that the MME sending a downlink data transmission indication message to the server may be that the MME sends a downlink data transmission indication message to the server via the SCEF.

For example, after receiving the downlink data, the data gateway P-GW forwards the downlink data to the S-GW, and the S-GW receives the downlink data, and sends a Downlink Data Notification (DDN) message to the MME. The DDN message carries the UE identifier. The MME detects that the UE is temporarily unreachable (for example, the UE enables PSM or eDRX) and decides to buffer the downlink data. The MME sends a Downlink Data Notification Acknowledgment (DDNA) message to the serving gateway S-GW, where the DDNA message is used to indicate that the S-GW buffers the downlink data; for example, the downlink data is buffered for the duration, and the MME determines according to the identifier of the UE. The downlink data transmission indication message needs to be sent to the server. The downlink data transmission indication message may include the duration information. The S-GW determines the number of cached data packets M according to the MME indication, the cache usage, the local configuration policy, and the like, and starts the timer T cache. Downstream data. When the timer T times out or the number of received packets exceeds M, the S-GW will no longer cache the packets. The MME sends a downlink data transmission indication message to the server, and the server determines, according to the downlink data transmission indication message, the downlink data of the user equipment UE to be transmitted for the duration, and does not send the downlink data of the UE at a time other than the duration.

Therefore, in the embodiment of the present invention, when the downlink data of the user equipment sent by the data sending end is unreachable, the mobility management entity sends a first indication message to the serving gateway, indicating that the serving gateway buffers the downlink data; and the mobility management entity sends the data to the data. Sending, by the terminal, the second indication message, so that the data sending end sends the downlink data of the user equipment according to the second indication message, for example, sending the downlink data of the user equipment for a certain duration, and does not send the time except for the duration. User equipment Downstream data. Thereby, the downlink data can be flexibly transmitted, unnecessary data transmission is avoided, and network efficiency is improved.

Optionally, according to the embodiment of the present invention, the first indication message carries indication information indicating that the serving gateway buffers downlink data, where the indication information includes a duration and/or a number of data packets.

The second indication message carries indication information.

It should be understood that the number of cached data packets refers to the maximum number of data packets that the S-GW configured by the MME for the S-GW can cache.

It should be noted that, in the embodiment of the present invention, whether the second indication message is fed back based on the request of the server (AS/SCS) may be determined, or the second indication message may be determined based on the local configuration information of the MME. And, the second indication message may be generated by the MME or may be generated by the S-GW. The following describes each of these cases in detail.

In one case, when the embodiment of the present invention is to feed back the second indication message based on the AS/SCS request, before 310, the method further includes:

The mobility management entity obtains the first request message sent by the data sending end, where the first request message is used to request the network to feed back the second indication message when the downlink data of the user equipment is unreachable, and the first request message carries the address information and the user of the data sending end. Identification of the device,

It should be understood that the address information of the sending end may be the IP or the location geographic information, and the identifier of the user equipment may be the ID, the IP, the IMEI code, and the like of the user equipment, and the embodiment of the present invention is not limited thereto.

For example, the AS/SCS sends a downlink data transmission indication request message to the SCEF, requesting the network to feed back the indication information when the UE is unreachable. The request message carries the IP address of the AS/SCS, the UE identifier, and the validity period of the request. The validity period of the request message may be valid only for the current downlink data transmission of the UE, or may be valid for all downlink data transmissions of the UE within a certain period of time. The SCEF forwards the AS/SCS request message to the MME. The MME saves the request message after receiving it, and deletes the message after the request message expires.

If the mobility management entity determines that the identifier of the user equipment is the same as the identifier of the user equipment carried in the first request message, the mobility management entity determines that the second indication message needs to be sent to the data sending end.

Further, when the second indication message is generated by the MME, before 330, the method further includes:

The mobility management entity generates a second indication message.

For example, the MME detects that the UE is temporarily unreachable (such as the PSM and eDRX enabled by the UE). Set the cached downlink data. The MME sends a Downstream Data Notification (DDNA) message to the S-GW, indicating that the S-GW needs to buffer the downlink data and the buffer duration T, optionally including the number N of buffered packets. The MEE determines whether the downlink data transmission indication information needs to be fed back according to the UE identifier. If the UE identifier in the DDN message is the same as the UE identifier in the AS/SCS request message, the MME generates a downlink data transmission indication message, and sends the downlink data transmission indication message to the AS/SCS via the SCEF. .

Alternatively, when the second indication message is generated by the S-GW, the first indication message is further used to instruct the serving gateway to generate the second indication message, wherein before 330, the method further includes:

For example, when the MME detects that the UE is temporarily unreachable (such as the PSM and eDRX enabled by the UE), it determines to buffer the downlink data. At the same time, the MEE determines that the downlink data transmission indication message needs to be fed back according to the UE identifier. The MME sends a Downstream Data Notification (DDNA) message to the S-GW, indicating that the S-GW needs to buffer the downlink data, and the buffer duration T, and the number of buffered packets N (optional). At the same time, the MME informs the S-GW that it needs to feed back the downlink data transmission indication message and provide the IP address of the AS/SCS. The S-GW determines the number of cached data packets M according to the MME indication, the cache usage, the local configuration policy, and the like, and generates a downlink data transmission indication message to be sent to the MME. The S-GW starts the timer T to buffer the downlink data. When the timer T times out or the number of received data packets exceeds M, the S-GW will not cache the data packet. The MME forwards the downlink data transmission indication message and sends it to the AS/SCS via the SCEF.

In another case, when the embodiment of the present invention determines whether to send the downlink data transmission indication message based on the local configuration information of the MME, that is, in this case, the MME needs to pre-configure the downlink data transmission indication message to be fed back. A list (pre-set feedback identifier list), the list includes the UE identifier, that is, all downlink data of the UE in the list needs to provide a feedback message when the UE is unreachable.

Optionally, in 320, if the mobility management entity determines that the identifier of the user equipment is the same as the identifier of the user equipment, the mobility management entity determines that the second indication message needs to be sent to the data sending end, where The preset feedback identifier list includes an identifier of the user equipment that needs to feed back the second indication message.

Further, when the second indication message is generated by the MME, the first indication message is further used to indicate that the serving gateway sends the address information of the data sending end to the mobility management entity. Before 330, the method further includes:

The mobility management entity receives the address information of the data sending end sent by the serving gateway;

The mobility management entity generates a second indication message, where the second indication message carries address information of the data sending end.

For example, the MME detects that the UE is temporarily unreachable (for example, the UE enables PSM or eDRX) and decides to buffer the downlink data. The MEE queries the locally configured list according to the UE identifier, and determines whether a downlink data transmission indication message needs to be fed back. If feedback is needed, the MME also needs to request the S-GW to provide the IP address of the AS/SCS. That is, the MME sends a Downstream Data Notification (DDNA) message to the S-GW, indicating that the S-GW needs to buffer the downlink data and the buffer duration T, and optionally also includes the number N of buffered packets. At the same time, the MME also requests the S-GW to provide the IP address of the AS/SCS. The S-GW starts the data packet detection function according to the MME indication, acquires the IP address of the AS/SCS corresponding to the downlink data packet, and feeds back to the MME. The MME generates a downlink data transmission indication message according to the AS/SCS IP address provided by the S-GW, and sends the downlink data transmission indication message to the AS/SCS via the SCEF.

Alternatively, when the second indication message is generated by the S-GW, the first indication message is further used to instruct the serving gateway to generate the second indication message. Before 330, the method further includes: the mobility management entity receiving the service gateway to send The second indication message.

For example, the MME detects that the UE is temporarily unreachable (such as the PSM and eDRX enabled by the UE), and determines to buffer the downlink data. The MEE queries the local configuration list according to the UE identifier, and determines whether the downlink data transmission indication message needs to be fed back. The MME sends a Downstream Data Notification (DDNA) message to the S-GW, indicating that the S-GW needs to buffer the downlink data and the buffer duration T, optionally including the number N of buffered packets. At the same time, the MME informs the S-GW that the downlink data transmission indication message needs to be fed back, and the S-GW determines the number M of cached packets according to the MME indication, the cache usage, the local configuration policy, and the like. The S-GW starts the data packet detection function according to the MME indication, acquires the IP address of the AS/SCS corresponding to the downlink data packet, and generates a downlink data transmission indication message to be sent to the MME. The MME forwards the downlink data transmission indication message and sends it to the AS/SCS via the SCEF.

Optionally, the embodiment of the present invention further includes: the mobility management entity receives the acknowledgement message sent by the data sending end, and the acknowledgement message is used to indicate that the data sending end has received the second indication message.

It should be understood that the acknowledgment message in the embodiment of the present invention may also be referred to as an acknowledgment message or a acknowledgment indication message, etc., which is not limited by the embodiment of the present invention.

For example, the MME sends a downlink data transmission indication message to the AS through the SCEF. After receiving the downlink data transmission indication message, the AS sends a downlink data transmission indication acknowledgement message to the MME (via SCEF), and the MME learns the AS according to the downlink data transmission indication acknowledgement message. The downlink data transmission indication message has been correctly sent, so that the downlink data transmission indication message does not need to be retransmitted (retransmitted), and the network is improved. Network efficiency.

In the above, the method for data transmission of the embodiment of the present invention is described from the mobility management entity side in conjunction with FIG. 3, and the data transmission method of the embodiment of the present invention is described below from the data transmitting end side with reference to FIG.

FIG. 4 is a schematic flowchart of a method of data transmission according to another embodiment of the present invention. The method of FIG. 5 can be performed by a data transmitting end. Specifically, the method shown in FIG. 5 includes:

410. The data sending end acquires a second indication message, where the second indication message is generated after the serving gateway receives the first indication message, where the first indication message is used to indicate that the serving gateway buffers downlink data of the user equipment that is unreachable in downlink data. ;

Specifically, the second indication message may be generated by the mobility management entity, or may be generated by the service gateway, which is not limited by the embodiment of the present invention.

420. The data sending end sends the downlink data of the user equipment according to the second indication message.

For example, after receiving the downlink data, the data gateway P-GW forwards the downlink data to the S-GW, and the S-GW receives the downlink data, and sends a downlink data notification (DDN) message to the MME. The DDN message carries the UE identifier. The MME detects that the UE is temporarily unreachable (for example, the UE enables PSM or eDRX) and decides to buffer the downlink data. The MME sends a downlink data notification acknowledgement DDNA message to the serving gateway S-GW, where the DDNA message is used to indicate that the S-GW buffers the downlink data, for example, buffering the downlink data for a duration, for example, buffering the downlink data for a duration; and the MME is configured according to the UE. The identifier determines that the downlink data sending indication message needs to be sent to the data sending end, and the downlink data sending indication message includes the duration information. The S-GW determines the number of cached data packets M according to the MME indication, the cache usage, the local configuration policy, and the like. Start timer T to buffer downstream data. When the timer T times out or the number of received packets exceeds M, the S-GW will no longer cache the packets. The MME sends a downlink data sending indication message to the data sending end, and the data sending end determines, according to the downlink data sending indication message, the downlink data of the UE to be sent in the duration, and does not send the downlink data of the UE at a time other than the duration.

Therefore, the embodiment of the present invention may obtain the second indication message on the data sending end, where the second indication message is generated after the serving gateway receives the first indication message, where the first indication message is used to indicate that the serving gateway buffers the downlink data unreachable. The downlink data of the user equipment is sent by the data sending end according to the second indication message. For example, the downlink data of the user equipment is sent for a certain duration, and the downlink data of the user equipment is not sent at a time other than the duration. Thereby, the downlink data can be flexibly transmitted, unnecessary data transmission is avoided, and network efficiency is improved.

Optionally, as another embodiment, the first indication message carries the indication service gateway buffer downlink number According to the indication information, the indication information includes the duration and/or the number of data packets.

The second indication message carries indication information.

among them,

When the indication information includes the duration, in 420, the data sending end determines, according to the second indication message, that the downlink data of the user equipment is sent in the duration,

When the indication information includes the number of data packets, in 420, the data sending end sends the downlink data of the user equipment according to the second indication message, and the number of data packets of the downlink data of the user equipment sent by the data sending end is less than or equal to the number of data packets. ,

When the indication information includes the duration and the number of data packets, in 420, the data sending end determines, according to the second sending indication message, the downlink data that is sent by the user equipment for the duration, and the user equipment that is sent by the data sending end during the duration The number of packets of downlink data is less than or equal to the number of packets.

Further, as another embodiment, when the indication information includes duration information, or the indication information includes a duration and a number of data packets, the method further includes:

The data transmitting end determines, according to the second indication message, that the downlink data of the user equipment is not transmitted at a time other than the duration.

Optionally, as another embodiment, before 410, the method further includes:

The data sending end sends a first request message, where the first request message is used to request the network to feed back the second indication message when the downlink data of the user equipment is unreachable, and the first request message carries the address information of the data sending end and the identifier of the user equipment.

For example, the data sending end (for example, the AS or the SCS) sends a downlink data sending indication request message to the SCEF, requesting the network to feed back the indication information when the UE is unreachable. The request message carries the IP address of the AS/SCS, the UE identifier, and the validity period of the request. The validity period of the request message may be valid only for the current downlink data transmission of the UE, or may be valid for all downlink data transmissions of the UE within a certain period of time. The SCEF forwards the AS/SCS request message to the MME. The MME saves the request message after receiving it, and deletes the message after the request message expires.

Optionally, the method of the embodiment of the present invention further includes:

The data sending end sends an acknowledgement message to the mobility management entity, where the acknowledgement message is used to indicate that the data sender has received the second indication message.

For example, the MME (via the SCEF) sends a downlink data transmission indication message to the data transmitting end, and after receiving the downlink data transmission indication message, the data transmitting end sends the downlink to the MME (via SCEF). The data transmission indication confirmation message is obtained by the MME according to the downlink data transmission indication acknowledgement message, and the data transmission end has received the correct downlink data transmission indication message, so that the downlink data transmission indication message does not need to be retransmitted (retransmitted), thereby improving network efficiency.

In the above, the method for data transmission of the embodiment of the present invention is described from the mobility management entity side in conjunction with FIG. 3, and the data transmission method of the embodiment of the present invention is described from the data transmitting end side in conjunction with FIG. The method of data transmission in the embodiment of the present invention is described from the serving gateway side in conjunction with FIG. 5 and FIG. 6.

FIG. 5 is a schematic flowchart of a method of data transmission according to another embodiment of the present invention. The method of FIG. 5 can be performed by a service gateway. Specifically, the method shown in FIG. 5 includes:

510. The serving gateway receives the first indication message sent by the mobility management entity, where the first indication message is used to indicate that the serving gateway caches downlink data of the user equipment that is not reachable by the data sending end, and generates a second indication message.

520. The service gateway obtains address information of the data sending end.

530. The serving gateway generates and sends a second indication message according to the indication of the first indication message and the address information of the data sending end, so that the data sending end sends the downlink data of the user equipment according to the second indication message.

For example, after receiving the downlink data, the data gateway P-GW forwards the downlink data to the S-GW, and the S-GW receives the downlink data, and sends a downlink data notification (DDN) message to the MME. The DDN message carries the UE identifier. The MME detects that the UE is temporarily unreachable (for example, the UE enables PSM or eDRX) and decides to buffer the downlink data. The MME sends a downlink data notification acknowledgement DDNA message to the serving gateway S-GW, where the DDNA message is used to indicate that the S-GW buffers the downlink data for a duration and generates a downlink data transmission indication message, for example, buffering the downlink data for a duration; The identifier of the UE determines that the downlink data sending indication message needs to be sent to the data sending end, and the downlink data sending indication message includes the duration information. The S-GW determines the number M of cached data packets according to the MME indication, the cache usage, the local configuration policy, and the like. And start the timer T to buffer the downlink data. When the timer T times out or the number of received packets exceeds M, the S-GW will no longer cache the packets. The S-GW obtains the IP address information of the data sending end; the S-GW obtains the IP address information of the data sending end, and the S-GW generates and sends a downlink data sending indication message to the MME according to the indication according to the DDNA message and the IP address information of the data sending end, and the downlink The data sending indication message includes the duration information, and the MME forwards the downlink data sending indication message to the data sending end, and the data sending end downlink data sending indication message determines that the downlink data of the user equipment is sent in the duration, except for the duration. The downlink data of the UE is not transmitted at the time.

Therefore, in the embodiment of the present invention, when the downlink data of the user equipment sent by the data sending end is unreachable, the serving gateway receives the mobility management entity to send a first indication message, indicating that the downlink data sent by the serving gateway caches the data sending end is unreachable. The downlink data of the user equipment is generated, and the second indication message is generated, and the service gateway acquires the address information of the data sending end. The serving gateway generates and sends a second indication message according to the indication of the first indication message and the address information of the data sending end, so as to facilitate the data sending end. Sending downlink data of the user equipment according to the second indication message, for example, sending downlink data of the user equipment for a duration, and not transmitting downlink data of the UE at a time other than the duration. Thereby, the downlink data can be flexibly transmitted, unnecessary data transmission is avoided, and network efficiency is improved.

Optionally, the first indication message carries indication information indicating that the serving gateway buffers downlink data, where the indication information includes a duration and/or a number of data packets.

The second indication message carries indication information.

It should be noted that, in the embodiment of the present invention, the AS/SCS request may be used to determine whether to feed back the downlink data transmission indication message, or may be based on the local configuration information of the MME to determine whether to feed back the downlink data transmission indication message. Moreover, the downlink data transmission indication message may be generated by the MME or may be generated by the S-GW. The following describes each of these cases in detail.

In one case, when the embodiment of the present invention performs the feedback downlink data transmission indication message based on the AS/SCS request, the first indication message optionally carries the address information of the data sending end, where, in 520, the serving gateway is configured according to the An indication message acquires address information of the data transmitting end.

For example, the AS/SCS sends a downlink data transmission indication request message to the SCEF, requesting the network to feed back the indication information when the UE is unreachable. The request message carries the IP address of the AS/SCS, the UE identifier, and the validity period of the request. The validity period of the request message may be valid only for the current downlink data transmission of the UE, or may be valid for all downlink data transmissions of the UE within a certain period of time. The SCEF forwards the AS/SCS request message to the MME. The MME saves the request message after receiving it, and deletes the message after the request message expires. When the MME detects that the UE is temporarily unreachable (such as the PSM and eDRX enabled by the UE), it determines to buffer the downlink data. At the same time, the MEE determines that the downlink data transmission indication message needs to be fed back according to the UE identifier. The MME sends a Downstream Data Notification (DDNA) message to the S-GW, indicating that the S-GW needs to buffer the downlink data, and the buffer duration T, and the number of buffered packets N (optional). At the same time, the MME informs the S-GW that it needs to feed back the downlink data transmission indication message and provide the IP address of the AS/SCS. The S-GW determines the number of cached data packets M according to the MME indication, the cache usage, the local configuration policy, and the like, and generates a downlink data transmission indication message to be sent to the MME. The MME forwards the downlink data transmission indication message and sends it to the SCEF via the SCEF. AS/SCS.

In another case, when the embodiment of the present invention determines whether to feed back the downlink data sending indication message based on the local configuration information of the MME, that is, in this case, the MME needs to feed back the downlink data sending indication message. A list (pre-set feedback identifier list), the list includes the UE identifier, that is, all downlink data of the UE in the list needs to provide a feedback message when the UE is unreachable.

Optionally, the first indication message is further used to instruct the serving gateway to obtain address information of the data sending end,

The service gateway performs downlink data detection according to the indication of the first indication message, and acquires address information of the data sending end.

FIG. 6 is a schematic flowchart of a method of data transmission according to another embodiment of the present invention. The method of FIG. 6 can be performed by a service gateway. Specifically, the method shown in FIG. 6 includes:

610. The serving gateway receives the first indication message sent by the mobility management entity, where the first indication message is used to indicate that the serving gateway caches the downlink data of the user equipment that is not reachable by the downlink data sent by the data sending end, and obtains the address information of the data sending end.

620. The serving gateway performs downlink data detection according to the indication of the first indication message, and obtains address information of the data sending end.

630. The service gateway sends the address information of the data sending end to the mobility management entity, so that the mobility management entity generates and sends a second indication message to the data sending end according to the address information of the data sending end, so that the data sending end according to the second indication message Send downlink data of the user equipment.

For example, the MME detects that the UE is temporarily unreachable (for example, the UE enables PSM or eDRX) and decides to buffer the downlink data. The MEE queries the locally configured list according to the UE identifier, and determines whether a downlink data transmission indication message needs to be fed back. If feedback is needed, the MME also needs to request the S-GW to provide the IP address of the AS/SCS. That is, the MME sends a Downstream Data Notification (DDNA) message to the S-GW, indicating that the S-GW needs to buffer the downlink data and the buffer duration T, and optionally also includes the number N of buffered packets. At the same time, the MME also requests the S-GW to provide the IP address of the AS/SCS. The S-GW starts the data packet detection function according to the MME indication, acquires the IP address of the AS/SCS corresponding to the downlink data packet, and feeds back to the MME. The S-GW starts the timer T to buffer the downlink data. When the timer T times out or the number of received data packets exceeds M, the S-GW will not cache the data packet. The MME generates a downlink data transmission indication message according to the IP address of the AS/SCS provided by the S-GW, and sends the downlink data transmission indication message to the AS/SCS via the SCEF. The AS/SCS determines to send in the duration according to the downlink data sending indication message. The downlink data of the user equipment UE does not transmit downlink data of the UE at a time other than the duration.

Therefore, the embodiment of the present invention receives the first indication message sent by the mobility management entity by using the serving gateway, where the first indication message is used to indicate that the serving gateway caches the downlink data of the user equipment that is not reachable by the data sending end, and obtains the data. Address information of the sending end; detecting downlink data according to the indication of the first indication message, acquiring address information of the data sending end; sending address information of the data sending end to the mobility management entity, so that the mobility management entity generates the address information according to the data sending end And sending a second indication message to the data sending end, so that the data sending end sends the downlink data of the user equipment according to the second indication message, for example, sending the downlink data of the user equipment for a duration, not at any time other than the duration. Send the downlink data. Thereby, the downlink data can be flexibly transmitted, unnecessary data transmission is avoided, and network efficiency is improved.

The second indication message carries indication information.

The method for data transmission according to the embodiment of the present invention is described from the side of the mobility management entity in conjunction with FIG. 3, and the method for data transmission according to the embodiment of the present invention is described from the data transmitting end side in conjunction with FIG. 4, in conjunction with FIG. 5 and FIG. The service gateway side describes a method of data transmission in an embodiment of the present invention. The method of data transmission in the embodiment of the present invention will be described in detail below with reference to specific examples of FIGS. 7 to 10.

FIG. 7 is a schematic flowchart of a method of data transmission according to another embodiment of the present invention. The embodiment of Figure 7 describes that the downlink data transmission indication message is generated by the MME and decides whether to feed back the message based on the AS/SCS request.

Specifically, the method shown in FIG. 7 includes:

701. The AS/SCS sends a downlink data sending indication request message to the SCEF, and requests the network to feed back the indication information when the UE is unreachable. The request message carries the IP address of the AS/SCS, the UE identifier, and the validity period of the request. The validity period of the request message may be valid only for the current downlink data transmission of the UE, or may be valid for all downlink data transmissions of the UE within a certain period of time.

702. The SCEF forwards the AS/SCS request message to the MME. The MME saves the request message after receiving it, and deletes the message after the request message expires.

703. When the user equipment is in an idle state, the P-GW receives the downlink data and forwards the data to the S-GW.

704. The S-GW receives the downlink data, and sends a downlink data notification DDN message to the MME. The message carries the UE identifier.

705. The MME detects that the UE is temporarily unreachable (such as the PSM and eDRX enabled by the UE), and determines to buffer the downlink data.

706. The MME sends a downlink data notification acknowledgement DDNA message to the S-GW, indicating that the S-GW needs to buffer the downlink data and the buffer duration T, and optionally further includes the number of cached packets N.

707. The MME sends a downlink data sending indication message to the AS.

Specifically, the MEE determines whether the downlink data transmission indication information needs to be fed back according to the UE identifier. If the UE identifier in the DDN message is the same as the UE identifier in the AS/SCS request message, the MME generates a downlink data transmission indication message, and sends the downlink data transmission indication message to the SCEF. AS/SCS.

The downlink data sending indication message generated by the MME includes a buffer duration T, and optionally further includes a number N of cached packets determined by the MME.

708. The AS/SCS optionally sends a downlink data transmission indication acknowledgement message to the network.

709. The S-GW determines the number of cached packets M according to the MME indication, the usage of the cache, the local configuration policy, and the like, and starts the timer T to buffer the downlink data. When the timer T times out or the number of received packets exceeds M, the S-GW will discard the buffered packets.

Therefore, in the embodiment of the present invention, a request message is sent to the network through the AS/SCS, and the downlink data transmission indication message is requested to be fed back when the UE is unreachable. The MME generates a downlink data transmission indication message based on the AS/SCS request, and feeds back information such as the buffer duration T and the number of cached packets N decided by the MME to the AS/SCS. The AS/SCS can decide when to stop the transmission or retransmission of downlink data packets according to the indication of the network, thereby avoiding unnecessary data packet transmission and improving the efficiency of using network resources.

FIG. 8 is a schematic flowchart of a method of data transmission according to another embodiment of the present invention. The embodiment of Figure 8 describes that the downlink data transmission indication message is generated by the S-GW and decides whether to feed back the message based on the AS/SCS request.

Specifically, the method shown in FIG. 8 includes:

801. The AS/SCS sends a downlink data sending indication request message to the SCEF, and requests the network to feed back the indication information when the UE is unreachable. The request message carries the IP address of the AS/SCS, the UE identifier, and the validity period of the request. The validity period of the request message may be valid only for the current downlink data transmission of the UE, or may be valid for all downlink data transmissions of the UE within a certain period of time.

802. The SCEF forwards the AS/SCS request message to the MME. The MME saves the request message after receiving it, and deletes the message after the request message expires.

The specific downlink data processing flow is as follows:

803. When the user equipment is in an idle state, the P-GW receives the downlink data and forwards the data to the S-GW.

804. The S-GW receives the downlink data, and sends a downlink data notification (DDN) message to the MME. The message carries the UE identifier.

805. The MME detects that the UE is temporarily unreachable (such as the PSM and eDRX enabled by the UE), and determines to buffer the downlink data. At the same time, the MEE determines whether the downlink data transmission indication message needs to be fed back according to the UE identifier. If the UE identifier in the DDN message is the same as the UE identifier in the AS/SCS request message, the MEE needs to provide a feedback message.

806. The MME sends a Downstream Data Notification (DDNA) message to the S-GW, indicating that the S-GW needs to buffer the downlink data, and the buffer duration T and the number of cache packets N (optional). At the same time, the MME informs the S-GW that it needs to feed back the downlink data transmission indication message and provide the IP address of the AS/SCS.

807. The S-GW sends a downlink data sending indication message to the MME.

Specifically, the S-GW determines the number of cached data packets M according to the MME indication, the usage of the cache, the local configuration policy, and the like, and generates a downlink data transmission indication message to be sent to the MME.

The downlink data sending indication information generated by the S-GW may include a buffer duration T and a number N of cached packets determined by the S-GW.

808, 807, the MME sends a downlink data sending indication message to the AS.

Specifically, the MME forwards the downlink data transmission indication message and sends it to the AS/SCS via the SCEF.

809. The AS/SCS optionally sends a downlink data transmission indication acknowledgement message to the network.

810. The S-GW starts a timer T to buffer downlink data. When the timer T times out or the number of received packets exceeds M, the S-GW will discard the buffered packets.

Therefore, the embodiment of the present invention sends a request message to the network through the AS/SCS, requesting feedback of the downlink data transmission indication information when the UE is unreachable. The S-GW generates a downlink data transmission indication message based on the AS/SCS request, and feeds back information such as the buffer duration T and the number of cached packets M determined by the S-GW to the AS/SCS. The AS/SCS can decide when to stop the transmission or retransmission of downlink data packets according to the indication of the network, thereby avoiding unnecessary data packet transmission and improving the efficiency of using network resources.

FIG. 9 is a schematic flowchart of a method of data transmission according to another embodiment of the present invention. FIG. 9 Embodiment This embodiment describes that a downlink data transmission indication message is generated by an MME, and determines whether to feed back the message based on local configuration information of the MME. A list of the feedback downlink data transmission indication message is configured in the MME, and the list includes the UE identifier, that is, all downlink data of the UE in the list needs to provide a feedback message when the UE is unreachable.

Specifically, the method shown in FIG. 9 includes:

901: When the user equipment is in an idle state, the P-GW receives downlink data and forwards the data to the S-GW.

902. The S-GW receives the downlink data, and sends a downlink data notification (DDN) message to the MME. The message carries the UE identifier.

903. The MME detects that the UE is temporarily unreachable (such as the PSM and eDRX enabled by the UE), and determines to buffer the downlink data. The MEE queries the local configuration list according to the UE identifier, and determines whether the downlink data transmission indication message needs to be fed back. If feedback is needed, the MME also needs to request the S-GW to provide the IP address of the AS/SCS.

904. The MME sends a Downstream Data Notification (DDNA) message to the S-GW, indicating that the S-GW needs to buffer the downlink data and the buffer duration T, and optionally further includes the number N of buffered packets. At the same time, the MME also requests the S-GW to provide the IP address of the AS/SCS.

905. The S-GW sends an IP address of the AS/SCS to the MME.

Specifically, the S-GW starts the data packet detection function according to the MME indication, acquires the IP address of the AS/SCS corresponding to the downlink data packet, and feeds back to the MME.

906. The MME sends a downlink data sending indication message to the AS.

Specifically, the MME generates a downlink data transmission indication message according to the AS/SCS IP address provided by the S-GW, and sends the downlink data transmission indication message to the AS/SCS via the SCEF.

907. The AS/SCS optionally sends a downlink data transmission indication acknowledgement message to the network.

908. The S-GW determines the number of cached packets M according to the MME indication, the usage of the cache, the local configuration policy, and the like, and starts the timer T to buffer the downlink data. When the timer T times out or the number of received packets exceeds M, the S-GW will discard the buffered packets.

Therefore, the MME determines whether to forward the downlink data sending indication message when the UE is unreachable based on the local configuration information, and generates a downlink data sending indication message by the MME, and feeds back the buffer duration T and the number of buffered packets to the AS/SCS. And other information. The AS/SCS can decide when to stop the transmission or retransmission of downlink data packets according to the indication of the network, thereby avoiding unnecessary data packet transmission and improving the efficiency of using network resources.

FIG. 10 is a schematic flowchart of a method of data transmission according to another embodiment of the present invention. FIG. 8 Embodiment This embodiment describes that a downlink data transmission indication message is generated by an S-GW, and determines whether to feed back the message based on local configuration information of the MME. A list of the feedback downlink data transmission indication message is pre-configured in the MME, where the UE identifier is included in the list, that is, the UE in the list All downlink data needs to provide feedback messages when the UE is unreachable.

Specifically, the method shown in FIG. 10 includes:

1001: When the user equipment is in an idle state, the P-GW receives the downlink data and forwards the data to the S-GW.

1002. The S-GW receives the downlink data, and sends a downlink data notification (DDN) message to the MME. The message carries the UE identifier.

1003. The MME detects that the UE is temporarily unreachable (such as the PSM and eDRX enabled by the UE), and determines to buffer the downlink data. The MEE queries the local configuration list according to the UE identifier, and determines whether the downlink data transmission indication message needs to be fed back.

1004. The MME sends a Downstream Data Notification (DDNA) message to the S-GW, indicating that the S-GW needs to buffer the downlink data and the buffer duration T, and optionally includes the number of cached packets N. At the same time, the MME informs the S-GW that it needs to feed back the downlink data transmission indication message.

1005. The S-GW sends a downlink data sending indication message to the MME.

Specifically, the S-GW determines the number M of cached packets according to the MME indication, the cache usage, the local configuration policy, and the like. The S-GW starts the data packet detection function according to the MME indication, acquires the IP address of the AS/SCS corresponding to the downlink data packet, and generates a downlink data transmission indication message to be sent to the MME.

The downlink data sending indication information generated by the S-GW includes a buffer duration T and a number N of cached packets determined by the S-GW.

1006. The MME sends a downlink data sending indication message to the AS.

1007. The AS/SCS optionally sends a downlink data transmission indication acknowledgement message to the network.

1008. The S-GW starts a timer T to buffer downlink data. When the timer T times out or the number of received packets exceeds M, the S-GW will discard the buffered packets.

Therefore, the MME determines whether to forward the downlink data sending indication message when the UE is unreachable based on the local configuration information, and generates a downlink data sending indication message by the S-GW, and feeds back the buffer duration T and the cache data to the AS/SCS. The number of packets N and other information. The AS/SCS can decide when to stop the transmission or retransmission of downlink data packets according to the indication of the network, thereby avoiding unnecessary data packet transmission and improving the efficiency of using network resources.

In the above, the data transmission method of the embodiment of the present invention is described in detail with reference to FIG. 1 to FIG. 10, and the apparatus for data transmission according to the embodiment of the present invention is described below with reference to FIG. 11 to FIG.

It should be understood that the mobility management entity shown in FIG. 11 corresponds to the method embodiment of FIG. 3, and the processes related to the mobility management entity in the implementation of FIG. 3 can be implemented. The specific functions of the mobility management entity 1100 shown in FIG. Referring to the respective processes performed by the mobility management entity in FIG. 3, in order to avoid repetition, the detailed description is appropriately omitted herein.

The mobility management entity 1100 shown in FIG. 11 includes a first determining unit 1110, a second determining unit 1120, and a transmitting unit 1130.

Specifically, the first determining unit 1110 is configured to send a first indication message to the serving gateway when the downlink data of the user equipment sent by the data sending end is unreachable, where the first indication message is used to instruct the serving gateway to buffer the downlink data.

The second determining unit 1120 is configured to determine that the second indication message needs to be sent to the data sending end;

The sending unit 1130 is configured to send a second indication message to the data sending end, so that the data sending end sends the downlink data of the user equipment according to the second indication message.

Therefore, in the embodiment of the present invention, when the downlink data of the user equipment sent by the data sending end is unreachable, the mobility management entity sends a first indication message to the serving gateway, indicating that the serving gateway buffers the downlink data; and the mobility management entity sends the data to the data. Sending, by the terminal, the second indication message, so that the data sending end sends the downlink data of the user equipment according to the second indication message, for example, sending the downlink data of the user equipment for a certain duration, and does not send the time except for the duration. Downstream data of the user equipment. Thereby, the downlink data can be flexibly transmitted, unnecessary data transmission is avoided, and network efficiency is improved.

Optionally, as another embodiment, the first indication message carries indication information indicating that the serving gateway buffers downlink data, where the indication information includes a duration and/or a number of data packets.

The second indication message carries indication information.

Optionally, as another embodiment, the mobility management entity 1100 further includes:

An acquiring unit, configured to acquire, by the first determining unit, a first request message sent by the data sending end, before sending the first indication message to the serving gateway, when the downlink data of the user equipment sent by the data sending end is determined to be unreachable, first The request message is used to request the network to feed back the second indication message when the downlink data of the user equipment is unreachable, where the first request message carries the address information of the data sending end and the identifier of the user equipment.

The second determining unit 1120 determines that the second indication message needs to be sent to the data sending end, if the identifier of the user equipment is the same as the identifier of the user equipment carried in the first request message.

The first generating unit is configured to generate a second indication message before the sending unit sends the second indication message to the data sending end.

Optionally, as another embodiment, the first indication message is further used to indicate that the serving gateway generates the second indication message, and the mobility management entity 1100 further includes:

The receiving unit is configured to receive the second indication message sent by the serving gateway before the sending unit sends the downlink data to send the second indication message to the data sending end.

Optionally, as another embodiment, if the first determining unit 1110 determines that the identifier of the user equipment is the same as the identifier of the user equipment, the first determining unit 1110 determines that the second indication message needs to be sent to the data sending end, where The set of feedback identifiers includes an identifier of the user equipment that needs to feed back the second indication message.

Optionally, as another embodiment, the first indication message is further used to indicate that the serving gateway sends the address information of the data sending end to the mobility management entity, where the mobility management entity further includes:

The first receiving unit is configured to receive, after the sending unit sends the downlink data sending indication information to the data sending end, the address information of the data sending end sent by the serving gateway;

The second generating unit is configured to generate a second indication message, where the second indication message carries the address information of the data sending end, before the sending unit sends the downlink data sending indication information to the data sending end.

The third receiving unit is configured to receive an acknowledgement message sent by the data sending end, where the acknowledgement message is used to indicate that the data sending end has received the second indication message.

It should be understood that the data transmitting end shown in FIG. 12 corresponds to the method embodiment of FIG. 4, and the processes involved in the data transmitting end in the implementation of FIG. 4 can be implemented. The specific functions of the data sending end 1200 shown in FIG. 12 can be referred to FIG. The detailed processes performed by the data transmitting end are omitted as appropriate to avoid duplication.

The data transmitting end 1200 shown in FIG. 12 includes an obtaining unit 1210 and a first transmitting unit 1220.

Specifically, the obtaining unit 1210 is configured to acquire a second indication message, where the second indication message is in the service After receiving the first indication message, the first indication message is used to indicate that the serving gateway buffers downlink data of the user equipment whose downlink data is unreachable;

The first sending unit 1220 is configured to send downlink data of the user equipment according to the second indication message.

Optionally, as another embodiment,

The second indication message carries indication information that the serving gateway buffers downlink data, where the indication information includes a duration and/or a number of data packets.

among them,

When the indication information includes the duration, the first sending unit 1220 determines, according to the second indication message, that the downlink data of the user equipment is sent in the duration,

When the indication information includes the number of data packets, the first sending unit 1220 sends the downlink data of the user equipment according to the second indication message, and the number of data packets of the downlink data of the user equipment sent by the data sending end is less than or equal to the number of data packets.

When the indication information includes the duration and the number of data packets, the first sending unit 1220 determines, according to the second indication message, the downlink data that is sent by the user equipment for the duration, and the downlink data of the user equipment that is sent by the data sending end during the duration. The number of packets is less than or equal to the number of packets.

Optionally, as another embodiment, when the indication information includes the duration, or the indication information includes the duration and the number of data packets, the data sending end 1200 further includes:

And a determining unit, configured to determine, according to the second indication message, that the downlink data of the user equipment is not sent at a time other than the duration.

Optionally, as another embodiment, the data sending end 1200 further includes:

a second sending unit, configured to send a first request message, where the first request message is used to request the network to feed back a second indication message when the downlink data of the user equipment is unreachable, the first request is sent by the acquiring unit 1210 The message carries the address information of the data sending end and the identifier of the user equipment.

Optionally, as another embodiment, the data sending end 1200 further includes:

And a third sending unit, configured to send a downlink data sending confirmation message to the mobility management entity, where the confirmation message is used to indicate that the data sending end has received the second indication message.

It should be understood that the server shown in FIG. 13 corresponds to the method embodiment of FIG. 5, and the processes related to the serving gateway in the implementation of FIG. 5 can be implemented. The specific functions of the serving gateway 1300 shown in FIG. 13 can be referred to the serving gateway in FIG. The detailed processes are omitted as appropriate to avoid repetition.

The service gateway 1300 shown in FIG. 13 includes a receiving unit 1310, an obtaining unit 1320, and a transmitting unit 1330.

Specifically, the receiving unit is configured to receive a first indication message that is sent by the mobility management entity, where the first indication message is used to indicate that the serving gateway caches downlink data of the user equipment that is not reachable by the data sending end, and generates a second indication. Message

The obtaining unit 1320 is configured to obtain address information of the data sending end.

The sending unit 1330 is configured to generate and send a second indication message according to the indication of the first indication message and the address information of the data sending end, so that the data sending end sends the downlink data of the user equipment according to the second indication message.

The second indication message carries indication information.

Optionally, as another embodiment, the first indication message carries address information of the data sending end,

The obtaining unit 1320 acquires address information of the data sending end according to the first indication message.

Optionally, as another embodiment, the first indication message is further used to instruct the serving gateway to obtain data. Address information of the sender,

The obtaining unit 1320 performs downlink data detection according to the indication of the first indication message, and acquires address information of the data sending end.

It should be understood that the server shown in FIG. 14 corresponds to the method embodiment of FIG. 6, and the processes related to the service gateway in the implementation of FIG. 6 can be implemented. The specific functions of the service gateway 1800 shown in FIG. 14 can be referred to the service gateway in FIG. The detailed processes are omitted as appropriate to avoid repetition.

The service gateway 1400 shown in FIG. 14 includes a receiving unit 1410, an obtaining unit 1420, and a transmitting unit 1430.

Specifically, the receiving unit 1410 is configured to receive a first indication message that is sent by the mobility management entity, where the first indication message is used to indicate that the serving gateway caches downlink data of the user equipment that is not reachable by the data sending end, and obtains data transmission. Address information of the terminal;

The obtaining unit 1420 is configured to perform downlink data detection according to the indication of the first indication message, and obtain address information of the data sending end;

The sending unit 1430 is configured to send the address information of the data sending end to the mobility management entity, so that the mobility management entity generates and sends a second indication message to the data sending end according to the address information of the data sending end, so that the data sending end according to the second indication The message sends the downlink data of the user equipment.

Therefore, the embodiment of the present invention receives the first indication message sent by the mobility management entity by using the serving gateway, where the first indication message is used to indicate that the serving gateway caches the downlink data of the user equipment that is not reachable by the data sending end, and obtains the data. Address information of the sending end; detecting downlink data according to the indication of the first indication message, acquiring address information of the data sending end; sending address information of the data sending end to the mobility management entity, so that the mobility management entity generates the address information according to the data sending end And sending a second indication message to the data sending end, so that the data sending end sends the downlink data of the user equipment according to the second indication message, for example, sending the downlink data of the user equipment for a duration, not at any time other than the duration. Send the downlink data. Thereby, the downlink data can be flexibly transmitted, unnecessary data transmission is avoided, and network efficiency is improved. Optionally, as another embodiment, the first indication message carries indication information indicating that the serving gateway buffers downlink data, where the indication information includes a duration and/or a number of data packets.

The second indication message carries indication information.

15 is a schematic block diagram of a mobility management entity in accordance with another embodiment of the present invention. The mobility management entity 1500 shown in FIG. 15 includes a processor 1510, a memory 1520, a bus system 1530, and a transceiver 1540.

It should be understood that the receiving end device 1500 shown in FIG. 15 corresponds to the mobility management entity shown in FIG. 11, and can implement various processes related to the mobility management entity in the method embodiment shown in FIG. For the specific functions of the sex management entity 1500, reference may be made to the various processes performed by the mobility management entity in FIG. 3. To avoid repetition, the detailed description is omitted as appropriate herein.

Specifically, the processor 1510 is configured to use the bus system 1530 to call the code stored in the memory 1520, and send a first indication message to the serving gateway when the downlink data of the user equipment sent by the data sending end is unreachable, where the first indication message is used. And instructing the service gateway to buffer the downlink data; and determining that the second indication message needs to be sent to the data sending end, the transceiver 1540 sending the second indication message to the data sending end, so that the data sending end sends the downlink data of the user equipment according to the second indication message. .

The method disclosed in the foregoing embodiments of the present invention may be applied to the processor 1510 or implemented by the processor 1510. The processor 1510 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 1510 or an instruction in a form of software. The processor 1510 may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a Field Programmable Gate Array (FPGA), or the like. Programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present invention may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software module can be located in random access memory (RAM), flash memory, only Read-Only Memory (ROM), programmable read-only memory or electrically erasable programmable memory, registers, etc., are well-known storage media in the field. The storage medium is located in the memory 1520. The processor 1510 reads the information in the memory 1520 and completes the steps of the foregoing method in combination with hardware. The bus system 1530 may include a power bus, a control bus, and a status signal bus in addition to the data bus. Wait. However, for clarity of description, various buses are labeled as bus system 1530 in the figure.

The second indication message carries indication information.

Optionally, as another embodiment, the processor 1510 is further configured to: before the downlink data of the user equipment sent by the data sending end is unreachable, send the first request sent by the data sending end before sending the first indication message to the serving gateway. The first request message is used to request the network to feed back the second indication message when the user equipment is unreachable, where the first request message carries the address information of the data sending end and the identifier of the user equipment.

If the identifier of the user equipment is the same as the identifier of the user equipment carried in the first request message, the processor 1510 determines that the second indication message needs to be sent to the data sending end.

Optionally, as another embodiment, the processor 1510 is further configured to generate a second indication message before the transceiver 1540 sends the second indication message to the data sending end.

Optionally, in another embodiment, the first indication message is further used to indicate that the serving gateway generates the second indication message, and the transceiver 1540 is further configured to receive, before the sending unit sends the downlink data to send the second indication message to the data sending end. The second indication message sent by the serving gateway.

Optionally, as another embodiment, if the processor 1510 determines that the identifier that is the same as the identifier of the user equipment exists in the preset feedback identifier list, determining that the second indication message needs to be sent to the data sending end, where the preset The identifier identifier list includes an identifier of the user equipment that needs to feed back the second indication message.

Optionally, as another embodiment, the first indication message is further used to instruct the serving gateway to send the address information of the data sending end to the mobility management entity, before the transceiver 1540 sends the downlink data sending indication information to the data sending end, the transceiver 1540 is further configured to receive address information of a data sending end sent by the serving gateway;

The processor 1510 is further configured to generate a second indication message, where the second indication message carries address information of the data sending end.

Optionally, the first indication message is used to instruct the serving gateway to generate the second indication message, and the transceiver 1540 is further configured to receive the second indication message sent by the serving gateway before the sending unit sends the second indication message. .

Optionally, as another embodiment, the transceiver 1540 is further configured to receive an acknowledgment message sent by the data sending end, where the acknowledgment message is used to indicate that the data sending end has received the second indication message.

FIG. 16 is a schematic block diagram of a data transmitting end according to another embodiment of the present invention. The data transmitting end shown in FIG. 16 includes a processor 1610, a memory 1620, a bus system 1630, and a transceiver 1640.

It should be understood that the data transmitting end 1600 shown in FIG. 16 corresponds to the data transmitting end shown in FIG. 12, and the processes related to the data transmitting end in the implementation of FIG. 4 can be implemented. The specific function of the data sending end 1600 shown in FIG. 16 can be Referring to the respective processes performed by the data transmitting end in FIG. 4, in order to avoid repetition, the detailed description is appropriately omitted herein.

Specifically, the processor 1610 is configured to use the bus system 1630 to call the code stored in the memory 1620 to obtain a second indication message, where the second indication message is generated after the serving gateway receives the first indication message, and the first indication message is generated. And the transceiver 16 is configured to send the downlink data of the user equipment according to the second indication message.

The method disclosed in the foregoing embodiments of the present invention may be applied to the processor 1610 or implemented by the processor 1610. Processor 1610 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1610 or an instruction in the form of software. The processor 1610 may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a Field Programmable Gate Array (FPGA), or the like. Programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out. The general purpose processor may be a microprocessor or the processor may be any conventional Processor and so on. The steps of the method disclosed in the embodiments of the present invention may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software module can be located in a random access memory (RAM), a flash memory, a read-only memory (ROM), a programmable read only memory or an electrically erasable programmable memory, a register, etc. In the storage medium. The storage medium is located in the memory 1620. The processor 1610 reads the information in the memory 1620 and completes the steps of the foregoing method in combination with hardware. The bus system 1630 may include a power bus, a control bus, and a status signal bus in addition to the data bus. Wait. However, for clarity of description, various buses are labeled as bus system 1630 in the figure.

Optionally, as another embodiment, the second indication message carries the indication information that the serving gateway buffers the downlink data, where the indication information includes a duration and/or a number of data packets, where

When the indication information includes the duration, the transceiver 1640 determines, according to the second indication message, the downlink data of the user equipment to be sent within the duration,

When the indication information includes the number of data packets, the transceiver 1640 sends the downlink data of the user equipment according to the second indication message, and the number of data packets of the downlink data of the user equipment sent by the data sending end is less than or equal to the number of data packets.

When the indication information includes the duration and the number of data packets, the transceiver 1640 determines, according to the second indication message, downlink data that is sent by the user equipment for the duration, and data of the downlink data of the user equipment that is sent by the data sending end for the duration. The number of packets is less than or equal to the number of packets.

Optionally, as another embodiment, when the indication information includes a duration, or the indication information includes a duration and a number of data packets, the transceiver 1640 is further configured to determine, according to the second indication message, that time other than the duration is not Send downlink data of the user equipment.

Optionally, as another embodiment, the transceiver 1640 is further configured to: before acquiring the second indication message, send a first request message, where the first request message is used to request the network to feed back the second indication message when the user equipment is unreachable, The first request message carries the address information of the data sending end and the identifier of the user equipment.

Optionally, as another embodiment, the transceiver 1640 is further configured to send a downlink data sending acknowledgement message to the mobility management entity, where the acknowledgement message is used to indicate that the data sender has received the second indication message.

17 is a schematic block diagram of a service gateway in accordance with another embodiment of the present invention. The service gateway shown in FIG. 17 includes a processor 1710, a memory 1720, a bus system 1730, and a transceiver 1740.

It should be understood that the service gateway 1700 shown in FIG. 17 corresponds to the service gateway shown in FIG. 13 and can implement various processes related to the service gateway in the implementation of FIG. 5. The specific function of the service gateway 1700 shown in FIG. 17 can be referred to FIG. In the process of completion by the service gateway, in order to avoid duplication, the detailed description is omitted here as appropriate.

Specifically, the processor 1710 is configured to receive, by using the bus system 1730, the code stored in the memory 1720, and receive the first indication message sent by the mobility management entity, where the first indication message is used to instruct the serving gateway to buffer the downlink data sent by the data sending end. The downlink data of the unreachable user equipment is generated, and the second indication message is generated, and the address information of the data sending end is obtained. The transceiver 1740 is configured to generate and send the second indication message according to the indication of the first indication message and the address information of the data sending end. The data sending end sends the downlink data of the user equipment according to the second indication message.

The method disclosed in the above embodiments of the present invention may be applied to the processor 1710 or implemented by the processor 1710. The processor 1710 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1710 or an instruction in a form of software. The processor 1710 may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a Field Programmable Gate Array (FPGA), or the like. Programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present invention may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software module can be located in a random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory or electrically erasable Program memory, registers, etc. are well-established in the storage medium of the art. The storage medium is located in the memory 1720. The processor 1710 reads the information in the memory 1720 and completes the steps of the foregoing method in combination with hardware. The bus system 1730 may include a power bus, a control bus, and a status signal bus in addition to the data bus. Wait. However, for clarity of description, various buses are labeled as bus system 1730 in the figure.

The second indication message carries indication information.

The transceiver 1740 obtains address information of the data sending end according to the first indication message.

Optionally, as another embodiment, the first indication message is further used to instruct the serving gateway to obtain address information of the data sending end,

The processor 1710 performs downlink data detection according to the indication of the first indication message, and acquires address information of the data sending end.

18 is a schematic block diagram of a service gateway in accordance with another embodiment of the present invention. The service gateway shown in FIG. 18 includes a processor 1810, a memory 1820, a bus system 1830, and a transceiver 1840.

It should be understood that the service gateway 1800 shown in FIG. 18 corresponds to the service gateway shown in FIG. 14 and can implement various processes related to the service gateway in the implementation of FIG. 6. The specific function of the service gateway 1800 shown in FIG. 18 can be referred to FIG. In the process of completion by the service gateway, in order to avoid duplication, the detailed description is omitted here as appropriate.

Specifically, the transceiver 1840 is configured to receive the first indication message sent by the mobility management entity, where the first indication message is used to indicate that the serving gateway caches the downlink data of the user equipment that is not reachable by the downlink data sent by the data sending end, and obtains the data sending. Address information of the terminal; the processor 1810 is configured to invoke the code stored in the memory 1820 through the bus system 1830, perform downlink data detection according to the indication of the first indication message, and obtain address information of the data sending end; the transceiver 1840 sends the address to the mobility management entity. Sending the address information of the data sending end, so that the mobility management entity generates and sends a second indication message to the data sending end according to the address information of the data sending end, so that the data sending end sends the downlink data of the user equipment according to the second indication message.

Therefore, the embodiment of the present invention receives the first indication message sent by the mobility management entity by using the serving gateway, where the first indication message is used to indicate that the serving gateway caches the downlink data of the user equipment that is not reachable by the data sending end, and obtains the data. Address information of the sender; according to the first indication The indication of the information is used to detect the downlink data, obtain the address information of the data sending end, and send the address information of the data sending end to the mobility management entity, so that the mobility management entity generates and sends a second indication to the data sending end according to the address information of the data sending end. The message is sent to the data sending end to send the downlink data of the user equipment according to the second indication message, for example, the downlink data of the user equipment is sent for a duration, and the downlink data is not sent at a time other than the duration. Thereby, the downlink data can be flexibly transmitted, unnecessary data transmission is avoided, and network efficiency is improved. The method disclosed in the above embodiments of the present invention may be applied to the processor 1810 or implemented by the processor 1810. The processor 1810 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1810 or an instruction in a form of software. The processor 1810 may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like. Programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present invention may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor. The software module can be located in a random access memory (RAM), a flash memory, a read-only memory (ROM), a programmable read only memory or an electrically erasable programmable memory, a register, etc. In the storage medium. The storage medium is located in the memory 1820. The processor 1810 reads the information in the memory 1820 and completes the steps of the foregoing method in combination with hardware. The bus system 1830 may include a power bus, a control bus, and a status signal bus in addition to the data bus. Wait. However, for clarity of description, various buses are labeled as bus system 1830 in the figure.

The second indication message carries indication information.

It is to be understood that the phrase "one embodiment" or "an embodiment" or "an" Thus, "in one embodiment" or "in an embodiment" or "an" In addition, these particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that in various embodiments of the invention, the above The size of the sequence numbers of the processes does not imply a sequence of executions, and the order of execution of the processes is determined by its function and intrinsic logic, and should not be construed as limiting the implementation of the embodiments of the present invention.

Additionally, the terms "system" and "network" are used interchangeably herein. The term "and/or" in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and / or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations. In addition, the character "/" in this article generally indicates that the contextual object is an "or" relationship.

It should be understood that in the embodiment of the present invention, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B from A does not mean that B is only determined based on A, and that B can also be determined based on A and/or other information.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both, for clarity of hardware and software. Interchangeability, the composition and steps of the various examples have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

A person skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, or an electrical, mechanical or other form of connection.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present invention.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented in hardware, firmware implementation, or a combination thereof. When implemented in software, the functions described above may be stored in or transmitted as one or more instructions or code on a computer readable medium. Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A storage medium may be any available media that can be accessed by a computer. By way of example and not limitation, computer readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage media or other magnetic storage device, or can be used for carrying or storing in the form of an instruction or data structure. The desired program code and any other medium that can be accessed by the computer. Also. Any connection may suitably be a computer readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable , fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, wireless, and microwave are included in the fixing of the associated media. As used in the present invention, a disk and a disc include a compact disc (CD), a laser disc, a compact disc, a digital versatile disc (DVD), a floppy disk, and a Blu-ray disc, wherein the disc is usually magnetically copied, and the disc is The laser is used to optically replicate the data. Combinations of the above should also be included within the scope of the computer readable media.

In summary, the above description is only a preferred embodiment of the technical solution of the present invention, and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

A method for data transmission, comprising:

When the downlink data of the user equipment sent by the data sending end is unreachable, the mobility management entity sends a first indication message to the serving gateway, where the first indication message is used to instruct the serving gateway to buffer the downlink data.

The mobility management entity determines that a second indication message needs to be sent to the data sending end;

The mobility management entity sends the second indication message to the data sending end, so that the data sending end sends the downlink data of the user equipment according to the second indication message.
The method of claim 1 wherein

The first indication message carries indication information indicating that the serving gateway caches the downlink data, where the indication information includes a duration and/or a number of data packets.

The second indication message carries the indication information.
Method according to claim 1 or 2, characterized in that

And before the sending, by the mobility management entity, the downlink data of the user equipment that is sent by the data sending end is unreachable to the serving gateway, the method further includes:

The mobility management entity acquires a first request message sent by the data sending end, where the first request message is used to request the network to feed back the second indication message when the downlink data of the user equipment is unreachable, The first request message carries the address information of the data sending end and the identifier of the user equipment,

The mobility management entity determines that the second indication message needs to be sent to the data sending end, including:

If the mobility management entity determines that the identifier of the user equipment is the same as the identifier of the user equipment carried in the first request message, the mobility management entity determines that the second needs to be sent to the data sending end. Indicate the message.
The method according to any one of claims 1 to 3, further comprising: before the mobility management entity sends the second indication information to the data sending end, further comprising:

The mobility management entity generates the second indication message.
The method according to any one of claims 1 to 3, wherein the first indication message is further used to instruct the service gateway to generate the second indication message,

Before the mobility management entity sends the second indication information to the data sending end, the method further includes:

The mobility management entity receives the second indication message sent by the serving gateway.
Method according to claim 1 or 2, characterized in that

The mobility management entity determines that the second indication message needs to be sent to the data sending end, including:

If the mobility management entity determines that the identifier of the user equipment is the same as the identifier of the user equipment, the mobility management entity determines that the second indication message needs to be sent to the data sending end. The preset feedback identifier list includes an identifier of the user equipment that needs to feed back the second indication message.
The method of claim 6 wherein:

The first indication message is further configured to instruct the serving gateway to send the address information of the data sending end to the mobility management entity, where the mobility management entity sends the second indication information to the data sending end. Previously, the method further includes:

Receiving, by the mobility management entity, address information of the data sending end sent by the serving gateway;

The mobility management entity generates the second indication message, where the second indication message carries address information of the data sending end.
The method of claim 6 wherein:

The first indication message is further configured to instruct the service gateway to generate the second indication message,

Before the mobility management entity sends the second indication message to the data sending end, the method further includes:

The mobility management entity receives the second indication message sent by the serving gateway.
The method according to any one of claims 1 to 8, further comprising:

The mobility management entity receives an acknowledgment message sent by the data sending end, where the acknowledgment message is used to indicate that the data sending end has received the second indication message.
A method for data transmission, comprising:

The data sending end is configured to obtain a second indication message, where the second indication message is generated after the serving gateway receives the first indication message, where the first indication message is used to indicate that the serving gateway caches users whose downlink data is unreachable. Downlink data of the device;

The data sending end sends the downlink data of the user equipment according to the second indication message.
The method of claim 10 wherein:

The first indication message carries an indication message indicating that the serving gateway caches the downlink data Information, the indication information includes duration and/or number of data packets,

The second indication message carries the indication information,

among them,

When the indication information includes the duration, the data sending end sends the downlink data of the user equipment according to the second indication message, including:

The data sending end determines, according to the second indication message, that the downlink data of the user equipment is sent in the duration,

When the indication information includes the number of the data packets, the data sending end sends the downlink data of the user equipment according to the second indication message, including:

The data sending end sends the downlink data of the user equipment according to the second indication message, and the number of data packets of the downlink data of the user equipment sent by the data sending end is less than or equal to the number of the data packets.

When the indication information includes the duration and the number of data packets, the data sending end sends the downlink data of the user equipment according to the second indication message, including:

The data sending end determines, according to the second indication message, downlink data that is sent by the user equipment in the duration, and downlink data of the user equipment that is sent by the data sending end in the duration The number of packets is less than or equal to the number of packets.
The method of claim 11 wherein

When the indication information includes the duration, or the indication information includes the duration and the number of data packets, the method further includes:

And the data sending end determines, according to the second indication message, that the downlink data of the user equipment is not sent at a time other than the duration.
A method according to any one of claims 10 to 12, wherein

Before the data sending end obtains the second indication message, the method further includes:

The data sending end sends a first request message, where the first request message is used to request the network to feed back the second indication message when the downlink data of the user equipment is unreachable, where the first request message carries the data The address information of the sender and the identifier of the user equipment.
The method according to any one of claims 10 to 13, further comprising:

The data sending end sends an acknowledgement message to the mobility management entity, where the acknowledgement message is used to indicate that the data sending end has received the second indication message.
A method for data transmission, comprising:

The serving gateway receives the first indication message sent by the mobility management entity, where the first indication message is used to indicate that the serving gateway caches downlink data of the user equipment that is not reachable by the data sending end, and generates a second indication message. ;

The service gateway acquires address information of the data sending end;

The serving gateway generates and sends a second indication message according to the indication of the first indication message and the address information of the data sending end, so that the data sending end sends the downlink of the user equipment according to the second indication message. data.
The method of claim 15 wherein:

The first indication message carries indication information indicating that the serving gateway caches the downlink data, where the indication information includes a duration and/or a number of data packets.

The second indication message carries the indication information.
The method according to claim 15 or 16, wherein the first indication message carries address information of the data sending end,

The service gateway obtains the address information of the data sending end, and includes:

The serving gateway acquires address information of the data sending end according to the first indication message.
The method according to claim 15 or 16, wherein the first indication message is further used to instruct the service gateway to acquire address information of the data sending end,

The service gateway obtains the address information of the data sending end, and includes:

The serving gateway performs the detection of the downlink data according to the indication of the first indication message, and acquires address information of the data sending end.
A method for data transmission, comprising:

The serving gateway receives the first indication message sent by the mobility management entity, where the first indication message is used to indicate that the serving gateway caches downlink data of the user equipment that is not reachable by the data sending end, and acquires the data sending. Address information of the terminal;

The serving gateway performs detection of the downlink data according to the indication of the first indication message, and acquires address information of the data sending end;

The service gateway sends the address information of the data sending end to the mobility management entity, so that the mobility management entity generates and sends a second indication message to the data sending end according to the address information of the data sending end. The data sending end sends the downlink data of the user equipment according to the second indication message.
The method of claim 19 wherein:

The first indication message carries indication information indicating that the serving gateway caches the downlink data, where the indication information includes a duration and/or a number of data packets.

The second indication message carries the indication information.
A mobility management entity, comprising:

a first determining unit, configured to send a first indication message to the serving gateway when the downlink data of the user equipment sent by the data sending end is unreachable, where the first indication message is used to instruct the serving gateway to buffer the downlink data;

a second determining unit, configured to determine that a second indication message needs to be sent to the data sending end;

And a sending unit, configured to send the second indication message to the data sending end, so that the data sending end sends the downlink data of the user equipment according to the second indication message.
The method of claim 21 wherein

The first indication message carries indication information indicating that the serving gateway caches the downlink data, where the indication information includes a duration and/or a number of data packets.

The second indication message carries the indication information.
The mobility management entity according to claim 21 or 22, further comprising:

An acquiring unit, configured to acquire, by the first determining unit, the first request message sent by the data sending end, before sending the first indication message to the serving gateway, when the downlink data of the user equipment sent by the data sending end is unreachable, The first request message is used to request the network to feed back the second indication message when the downlink data of the user equipment is unreachable, where the first request message carries the address information of the data sending end and the identifier of the user equipment.

And determining, by the second determining unit, that the identifier of the user equipment is the same as the identifier of the user equipment carried in the first request message, determining that the second indication message needs to be sent to the data sending end.
The mobility management entity according to any one of claims 21 to 23, further comprising:

The first generating unit is configured to generate the second indication message before the sending unit sends the second indication message to the data sending end.
The mobility management entity according to any one of claims 21 to 23, wherein the first indication message is further used to instruct the service gateway to generate the second indication message, the mobility management entity Also includes:

The receiving unit is configured to receive the second indication message sent by the serving gateway before the sending unit sends the second indication message to the data sending end.
A mobility management entity according to claim 21 or 22, characterized in that

If the first determining unit determines that the identifier of the user equipment is the same as the identifier of the user equipment, the second determining unit needs to send the second indication message to the data sending end, where the preset The feedback identifier list includes an identifier of the user equipment that needs to feed back the second indication message.
The mobility management entity of claim 26, wherein

The first indication message is further configured to: the service gateway sends the address information of the data sending end to the mobility management entity, where the mobility management entity further includes:

a first receiving unit, configured to receive address information of the data sending end sent by the serving gateway before the sending unit sends the second indication message to the data sending end;

The second generating unit is configured to generate the second indication message, where the second indication message carries the address information of the data sending end, before the sending unit sends the second indication message to the data sending end.
The mobility management entity according to claim 26, wherein the first indication message is further configured to instruct the service gateway to generate the second indication message, and the mobility management entity further includes:

The second receiving unit is configured to receive the second indication message sent by the serving gateway before the sending unit sends the second indication message to the data sending end.
The mobility management entity according to any one of claims 21 to 28, further comprising:

The third receiving unit is configured to receive an acknowledgement message sent by the data sending end, where the acknowledgement message is used to indicate that the data sending end has received the second indication message.
A data transmitting end, comprising:

An acquiring unit, configured to obtain a second indication message, where the second indication message is generated after the serving gateway receives the first indication message, where the first indication message is used to indicate that the serving gateway caches downlink data unreachable Downlink data of the user equipment;

The first sending unit is configured to send downlink data of the user equipment according to the second indication message.
A data transmitting end according to claim 30, characterized in that

The second indication message carries indication information that the serving gateway buffers the downlink data, where the indication information includes a duration and/or a number of data packets.

among them,

When the indication information includes the duration, the first sending unit determines, according to the second indication message, that the downlink data of the user equipment is sent in the duration,

When the indication information includes the number of the data packets, the first sending unit sends the downlink data of the user equipment according to the second indication message, and the data of the downlink data of the user equipment sent by the data sending end The number of packets is less than or equal to the number of packets,

When the indication information includes the duration and the number of data packets, the first sending unit determines, according to the second indication message, that downlink data of the user equipment is sent in the duration, and in the persistent The number of data packets of the downlink data of the user equipment sent by the data sending end is less than or equal to the number of the data packets.
The data transmitting end according to claim 31, wherein

When the indication information includes the duration, or the indication information includes the duration and the number of data packets, the data sending end further includes:

And a determining unit, configured to determine, according to the second indication message, that the downlink data of the user equipment is not sent at a time other than the duration.
The data transmitting end according to any one of claims 30 to 32, further comprising:

a second sending unit, configured to send a first request message, where the first request message is used to request the network to feed back the first data when the downlink data of the user equipment is unreachable before the acquiring unit acquires the second indication message The second indication message carries the address information of the data sending end and the identifier of the user equipment.
The data transmitting end according to any one of claims 30 to 33, further comprising:

And a third sending unit, configured to send an acknowledgement message to the mobility management entity, where the acknowledgement message is used to indicate that the data sending end has received the second indication message.
A service gateway, comprising:

a receiving unit, configured to receive a first indication message sent by the mobility management entity, where the first indication message is used to indicate that the serving gateway caches downlink data of the user equipment that is not reachable by the data sending end, and generates the first Two indication messages;

An obtaining unit, configured to acquire address information of the data sending end;

a sending unit, configured to generate and send a second indication message according to the indication of the first indication message and the address information of the data sending end, so that the data sending end sends the user equipment according to the second indication message Downstream data.
A service gateway according to claim 35, wherein

The first indication message carries indication information indicating that the serving gateway caches the downlink data, where the indication information includes a duration and/or a number of data packets.

The second indication message carries the indication information.
The service gateway according to claim 35 or claim 36, wherein the first indication message carries address information of the data sending end,

The acquiring unit acquires address information of the data sending end according to the first indication message.
The service gateway according to claim 35 or claim 36, wherein the first indication message is further configured to instruct the service gateway to acquire address information of the data sending end,

The acquiring unit performs detection of the downlink data according to the indication of the first indication message, and acquires address information of the data sending end.
A service gateway, comprising:

a receiving unit, configured to receive a first indication message sent by the mobility management entity, where the first indication message is used to indicate that the serving gateway caches downlink data of the user equipment that is not reachable by the data sending end, and obtains the Address information of the data sender;

An acquiring unit, configured to perform detection of the downlink data according to the indication of the first indication message, and acquire address information of the data sending end;

a sending unit, configured to send address information of the data sending end to the mobility management entity, so that the mobility management entity generates and sends the second information to the data sending end according to the address information of the data sending end And indicating the message, so that the data sending end sends the downlink data of the user equipment according to the second indication message.
A service gateway according to claim 39, wherein

The first indication message carries indication information indicating that the serving gateway caches the downlink data, where the indication information includes a duration and/or a number of data packets.

The second indication message carries the indication information.