WO2017113390A1 - 数据传输的方法和装置 - Google Patents

数据传输的方法和装置 Download PDF

Info

Publication number
WO2017113390A1
WO2017113390A1 PCT/CN2015/100311 CN2015100311W WO2017113390A1 WO 2017113390 A1 WO2017113390 A1 WO 2017113390A1 CN 2015100311 W CN2015100311 W CN 2015100311W WO 2017113390 A1 WO2017113390 A1 WO 2017113390A1
Authority
WO
WIPO (PCT)
Prior art keywords
data transmission
data packet
transmission parameter
network device
core network
Prior art date
Application number
PCT/CN2015/100311
Other languages
English (en)
French (fr)
Inventor
刘清顺
黄正磊
张万强
吕黎明
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2015/100311 priority Critical patent/WO2017113390A1/zh
Publication of WO2017113390A1 publication Critical patent/WO2017113390A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information

Definitions

  • the present invention relates to the field of communications, and in particular, to a method, device, and system for data transmission.
  • M2M Machine to Machine
  • SDT Small Data Transmission
  • terminals such as water meters, electricity meters, and sensors mainly transmit meter reading data or monitoring data with a small amount of data through a network, and the data amount of data packets transmitted at one time is usually only tens to hundreds of bytes.
  • the current communication system is designed for transmitting large amounts of data.
  • LTE Long Term Evolution
  • the process is to establish bearers of the air interface and the S1 interface, and needs to download Radio Resource Control (RRC) security context information into an evolved Node B (eNodeB or eNB).
  • RRC Radio Resource Control
  • eNodeB evolved Node B
  • the overhead of establishing bearers and subsequent operations is very wasteful before transmitting small data.
  • the embodiment of the invention provides a method, a device and a system for data transmission, so as to solve the problem that the bearer needs to be built before the data is transmitted.
  • an embodiment of the present invention provides a data transmission method, including: acquiring, by a core network device, a data transmission parameter, where the data transmission parameter includes part or all of information included in an IP protocol IP header; and assigning an identifier to the data transmission parameter. And an identifier for identifying the data transmission parameter; and transmitting the data transmission parameter and the identifier to the terminal.
  • the IP header may include a User Data Packet Protocol UDP header. Therefore, the core network device can avoid the waste of overhead due to the establishment of the bearer before the data is transmitted by acquiring the data transmission parameter and assigning the identifier, and transmitting the data transmission parameter and the identifier to the terminal.
  • the core network device can obtain data transmission parameters according to the indication of the terminal. For example, before the core network device obtains the data transmission parameter, the terminal may send a data transmission indication to the core network device, where the data transmission indication is used to indicate a data packet including the data transmission parameter or server information or service information related to the data packet; The core network device receives the data transmission indication sent by the terminal, and acquires the data transmission parameter according to the data transmission indication.
  • the core network device can obtain data transmission in one of the following ways: parameter.
  • the first mode the core network device obtains the locally configured data transmission parameter, where the locally configured data transmission parameter may include the server address and the port information. This static configuration has small changes to existing signaling, simple implementation, and good compatibility.
  • the second mode the core network device obtains the data transmission parameter by using the context information of the terminal. For example, the core network device obtains the context information of the terminal from the core network device attached to the terminal, and the context information of the terminal includes the data transmission parameter.
  • the third mode the core network device obtains the data transmission parameter through the subscription data of the terminal. For example, the core network device acquires the subscription data of the terminal from the HSS, and the subscription data of the terminal includes the data transmission parameter.
  • the second and third modes have smaller modifications to the existing signaling, and the implementation manner is simple, and the local configuration of the core network device does not need to be changed.
  • the fourth mode the core network device receives the data transmission parameter sent by the terminal. For example, the core network device receives the control signaling or the uplink data packet sent by the terminal, where the control signaling or the uplink data packet includes the data transmission parameter. In this way, the core network device can obtain data transmission parameters more flexibly, and the content of the obtained data transmission parameters is more comprehensive.
  • the fifth mode the core network device receives the data transmission parameter sent by the PCRF entity, and the core network device receives the data transmission parameter sent by the PCRF entity during the session establishment process.
  • the sixth mode the core network device receives the data transmission parameter sent by the server, for example, the core network device receives the data transmission parameter sent by the server through the open service interface, and for example, the core network device receives the downlink data packet sent by the server, and the downlink data packet Contains data transfer parameters.
  • the core network device can obtain data transmission parameters more flexibly, and the content of the data transmission parameters has better scalability.
  • the core network device can also obtain data transmission parameters by other means.
  • the core network device After the core network device sends the data transmission parameter and the identifier to the terminal, the first data packet sent by the terminal is received, the first data packet carries the identifier, and the data transmission parameter is determined according to the identifier; The data packet is processed. For example, the core network device adds an IP header and removes the identifier in the first data packet according to the data transmission parameter to generate the second data packet or convert the first data packet into the second data packet, for example, the core.
  • the network device adds an IP header corresponding to the data transmission parameter in the first data packet and removes the identifier to generate the second data packet or convert the first data packet into the second data packet, and, for example, the core network device according to the first data packet Generating a second data packet or converting the first data packet into a second data packet, wherein the second data packet includes an IP header and does not include an identifier. Further, the core network device may also send the second data packet to the M2M service platform or the AS. In this design, on the one hand, the first data packet transmitted between the terminal and the core network device does not carry an IP header, that is, a non-IP data packet is transmitted between the terminal and the core network device, thereby reducing the first data packet.
  • the core network device can recover the IP header according to the data transmission identifier, generate the second data packet, or convert the first data packet into the first data packet.
  • Two data packets that is, generating IP data packets or converting non-IP data packets into IP data packets, so as to be suitable for transmission between the core network device and the M2M service platform or AS.
  • the third data packet sent by the M2M service platform or the AS is also received, and the third data packet carries the data transmission parameter; and the data transmission parameter is determined according to the data transmission parameter. Identifying; then processing the third data packet, for example, the core network device removes the IP header of the third data packet and adds an identifier in the third data packet to generate a fourth data packet or convert the third data packet into a fourth data packet.
  • the data packet for example, the core network device generates a fourth data packet according to the third data packet or converts the third data packet into a fourth data packet, wherein the fourth data packet includes the identifier and does not include the IP header.
  • the core network device may further send the fourth data packet to the terminal.
  • the core network device can remove the IP header, generate the fourth data packet, or convert the third data packet into the fourth data packet, that is, generate a non-IP data packet or generate an IP packet.
  • the data packet is converted into a non-IP data packet to send the non-IP data packet to the terminal, thereby reducing the overhead of data transmission between the core network device and the terminal, and improving the transmission efficiency.
  • the embodiment of the present invention provides another method for data transmission, including: determining, according to a correspondence between an identifier and a data transmission parameter included in the first data packet, a data transmission parameter identified by the identifier, the data transmission parameter. Include some or all of the information contained in the Internet Protocol IP header, wherein the IP header may include a User Datagram Protocol UDP header; and processing the first data packet, for example, adding an IP header to the first data packet according to the data transmission parameter And deleting the identifier to generate the second data packet or converting the first data packet into the second data packet, and, for example, adding an IP header corresponding to the data transmission parameter in the first data packet and removing the identifier to generate the second data packet Or converting the first data packet into the second data packet, and, for example, generating the second data packet according to the first data packet or converting the first data packet into the second data packet, where the second data packet includes the IP header and does not Contains the logo.
  • the method in this aspect may not include the above part, but includes the following other parts.
  • the method of the present aspect may also include the above part and the other part.
  • the following another part includes: determining, according to the third data packet, the IP header and the corresponding relationship, wherein the correspondence is a correspondence between the identifier and the data transmission parameter, where the data transmission parameter includes information included in the IP header.
  • the third data packet for example, removing the IP header of the third data packet and adding an identifier in the third data packet to generate a fourth data packet or converting the third data packet into a fourth data packet
  • the data packet for example, generates a fourth data packet according to the third data packet or converts the third data packet into a fourth data packet, wherein the fourth data packet includes the identifier and does not include the IP header.
  • the IP header of the data packet can be removed or added according to the data transmission parameter and the identifier, so that the data packet is reduced in the transmission of the data packet and the transmission efficiency is improved when the data packet is suitable for transmission.
  • the second data packet may also be sent to the M2M platform or the AS; or, after the fourth data packet is obtained, the fourth data packet may also be sent to the terminal.
  • the method in this design is applicable to the core network device, so that the core network device can send IP data packets suitable for transmission to the M2M or AS, or enable the core network device to be able to the terminal device. Sending non-IP packets that do not carry IP headers can reduce transmission overhead and improve transmission efficiency.
  • the second data packet may be processed by a higher layer; or after the fourth data packet is obtained, the fourth data packet may also be sent to the core network device.
  • the method in this design is applicable to the terminal, so that the terminal can perform high-level processing on the obtained IP data packet, or enable the terminal to send a non-IP data packet that does not carry the IP header to the core network device, thereby reducing the transmission overhead. Improve transmission efficiency.
  • an embodiment of the present invention provides a core network device, where the core network device has a function of implementing a behavior of a core network device in the foregoing method design.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the core network device includes a processor and a network interface, the processor being configured to support the core network device to perform a corresponding function in the foregoing method, the network interface for supporting the core network device
  • the communication with the terminal transmits the information or instructions involved in the above method to the terminal.
  • the processor is configured to obtain a data transmission parameter, where the data transmission parameter includes part or all of information included in an Internet Protocol IP header, wherein the IP header may include a User Datagram Protocol UDP header; and is configured to assign an identifier to the data transmission parameter, and identify It is used to identify data transmission parameters; it is also used to send data transmission parameters and identifiers to the terminal through a network interface.
  • the core network device can also include a memory for coupling with the processor that retains the necessary program instructions and data for the core network device.
  • an embodiment of the present invention provides a terminal, where the terminal has a function of implementing terminal behavior in the design of the foregoing method.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the terminal includes a receiver and a processor configured to support the terminal to perform a corresponding function in the above method, the receiver being configured to support the terminal to receive the above method Information or instructions sent by the core network device involved.
  • the receiver is configured to receive data transmission parameters and identifiers sent by the core network device, where the data transmission parameters include some or all of the information included in the Internet Protocol IP header, where the IP header may include a User Datagram Protocol UDP header, and the identifier is used. And identifying the data transmission parameter; the processor is configured to process the data packet according to the data transmission parameter and the identifier.
  • the terminal may further include a transmitter configured to support the terminal transmitting the information or instructions involved in the method to the core network device.
  • the terminal can also include a memory coupled to the processor that retains program instructions and data necessary for the terminal.
  • an embodiment of the present invention provides a communication system, where the system includes the core network device and the terminal in the foregoing aspect.
  • an embodiment of the present invention provides a computer storage medium for storing Computer software instructions for use with the core network device, including programs designed to perform the above aspects.
  • an embodiment of the present invention provides a computer storage medium for storing computer software instructions for use in the terminal, including a program designed to perform the above aspects.
  • the core network device can avoid the data in the terminal and the core network before transmitting the data by acquiring the data transmission parameter and assigning the identifier, and transmitting the data transmission parameter and the identifier to the terminal.
  • the burden is created by establishing bearers.
  • the core network device and the terminal can process the data packet based on the foregoing data transmission parameter and the identifier, so that the data packet transmitted between the core network device and the terminal does not carry the IP header, thereby reducing transmission between the core network device and the terminal.
  • the overhead of data increases the efficiency of data transmission.
  • FIG. 1 is a schematic diagram of a possible system network for implementing the present invention
  • FIG. 2 is a schematic diagram of another possible system network for implementing the present invention.
  • FIG. 3 is a schematic diagram of still another possible system network for implementing the present invention.
  • FIG. 4 is a schematic flowchart of a method for data transmission according to an embodiment of the present invention.
  • 5a and 5b are schematic diagrams of communication of a method for negotiating data transmission parameters and identifiers according to an embodiment of the present invention
  • FIG. 6a and FIG. 6b are schematic diagrams of communication of another method for negotiating data transmission parameters and identifiers according to an embodiment of the present invention
  • FIG. 7a and FIG. 7b are schematic diagrams of communication of a method for negotiating data transmission parameters and identifiers according to an embodiment of the present invention
  • 8a and 8b are schematic diagrams of communication of a method for negotiating data transmission parameters and identifiers according to an embodiment of the present invention
  • 9a and 9b are schematic diagrams of communication of a method for negotiating data transmission parameters and identifiers according to an embodiment of the present invention
  • FIG. 10a and FIG. 10b are schematic diagrams of communication of a method for negotiating data transmission parameters and identifiers according to an embodiment of the present invention
  • FIG. 11 is a schematic diagram of communication according to a method for data transmission based on data transmission parameters and identifiers according to an embodiment of the present invention
  • FIG. 12 is another data transmission based on data transmission parameters and identifiers according to an embodiment of the present invention. Communication diagram of the method of transmission;
  • FIG. 13 is a schematic diagram of communication according to another method for data transmission based on data transmission parameters and identifiers according to an embodiment of the present disclosure
  • FIG. 14 is a schematic diagram of communication according to another method for data transmission based on data transmission parameters and identifiers according to an embodiment of the present invention.
  • FIG. 15 is a schematic structural diagram of a core network device according to an embodiment of the present disclosure.
  • FIG. 16 is a schematic structural diagram of a terminal according to an embodiment of the present invention.
  • the network architecture and the service scenario described in the embodiments of the present invention are used to more clearly illustrate the technical solutions of the embodiments of the present invention, and do not constitute a limitation of the technical solutions provided by the embodiments of the present invention.
  • the technical solutions provided by the embodiments of the present invention are equally applicable to similar technical problems.
  • EPS Evolved Packet System
  • UE User Equipment
  • IP Internet Protocol
  • FIG. 1 After accessing the access network, the UE passes a General Packet Radio System (GPRS) Service Support Node (SGSN) or a Mobility Management Entity (MME). Access to the Serving Gateway (SGW), and then access to the Packet Data Network Gateway (PDN-GW or PGW) and the carrier IP service network.
  • GPRS General Packet Radio System
  • MME Mobility Management Entity
  • SGW Serving Gateway
  • PGW Packet Data Network Gateway
  • PGW Packet Data Network Gateway
  • CIoT refers to the Internet of Things-based Internet of Things.
  • 3GPP 3rd Generation Partnership Project
  • IoT devices with low data rates study how to support efficient transmission of frequent and infrequent small data packets, support terminal power consumption optimization, support paging optimization in coverage enhanced scenarios, and simplify mobility management and session management signaling. .
  • the CIoT Serving Gateway Node is a newly introduced logical entity for supporting functions related to the CIoT application scenario, for example, supporting some necessary mobility management processes and supporting effective
  • the small data transmission process supports the security process necessary for efficient transmission of small data, supports short message transmission based on Packet Switched (PS) domain, supports paging optimization to achieve coverage enhancement, and supports S8 interface for roaming scenarios.
  • PS Packet Switched
  • the network architecture shown in Figure 2 also includes: CIoT UE, supporting CIoT Technology terminal; CIoT BS, base station (BS) supporting CIoT technology; LTE eMTC UE, terminal supporting evolved machine type communication (eMTC) technology in LTE system; LTE eMTC eNB, support The eNB of the eMTC technology in the LTE system; the Home Subscriber Server (HSS) is configured to store the subscription information of the IP Multimedia Subsystem (IMS) user in the home network, and provide a management interface, which is operated by The service and the end user customize and modify the subscription data; the application server (AS) is used to provide the service application for the terminal.
  • IMS IP Multimedia Subsystem
  • AS application server
  • the CIoT UE and the CIoT BS communicate with each other through the CIoT-Uu interface, and the LTE eMTC UE and the LTC eMTC eNB communicate with each other through the LTE-Uu (eMTC) interface.
  • eMTC LTE-Uu
  • FIG. 3 is a schematic diagram of a network architecture of a CIoT in a roaming scenario according to an embodiment of the present invention.
  • the C-SGN communicates with the PGW through the S8 interface
  • the PGW communicates with the AS through the SGi interface.
  • the other content is similar to the network architecture shown in FIG. 2, and may be described in detail in FIG. 2, and details are not described herein again.
  • the technical solution of the embodiment of the present invention can be applied to a mobile originated (MO) data transmission process, and can also be applied to a mobile terminated (MT) data transmission process.
  • the data can be transmitted between the terminal and the core network through a Non-Access Stratum (NAS) message, so that no data plane path needs to be established between the terminal and the core network, which reduces overhead.
  • NAS Non-Access Stratum
  • the solution of the embodiment of the present invention will propose a way to improve this situation in the subsequent introduction.
  • One embodiment of the present invention provides a method of data transmission, and a terminal, core network device and system based on the method.
  • the terminal and the core network device perform a data transmission parameter and an identifier negotiation process.
  • the core network device acquires a data transmission parameter, allocates an identifier for the data transmission parameter, and sends the data transmission parameter and the identifier to the terminal.
  • the solution of the embodiment of the present invention can avoid waste of overhead caused by establishing a bearer before transmitting data.
  • the terminal and the core network device may process the corresponding data packet according to the data transmission parameter and the identifier during the transmission process of the data packet, so that the data packet does not carry the IP header when transmitting between the terminal and the core network, so It can reduce the overhead of data packets and improve the efficiency of data transmission.
  • the core network device in the network architecture shown in FIG. 1, may be an MME. Or PGW; in the network architecture shown in FIG. 2, the core network device may be a C-SGN; in the network architecture shown in FIG. 3, the core network device may be a C-SGN or a PGW.
  • the core network device obtains data transmission parameters, and the data transmission parameters include some or all of the information included in the IP header, where the IP header may include a User Datagram Protocol (UDP) header.
  • the core network device can obtain data transmission parameters according to the indication of the terminal. For example, before the core network device obtains the data transmission parameter, the terminal may send a data transmission indication to the core network device, where the data transmission indication is used to indicate a data packet including the data transmission parameter or server information or service information related to the data packet; The core network device receives the data transmission indication sent by the terminal, and acquires the data transmission parameter according to the data transmission indication.
  • UDP User Datagram Protocol
  • the core network device obtains locally configured data transmission parameters.
  • the data transmission parameter is statically configured in the core network device, and the data transmission parameter may include a server address and port information, and the like, for example, including a server IP address, a protocol type, and a destination port.
  • the core network device obtains data transmission parameters through static configuration. The existing signaling changes are small, the implementation is simple, and the compatibility is good.
  • the core network device obtains context information of the terminal, where the context information includes data transmission parameters.
  • the data transmission parameters may include a server IP address, a protocol type, and a destination port.
  • the core network device obtains the context information of the terminal from the core network device to which the terminal is attached. This method has less modification to the existing signaling, is simple to implement, and does not need to change the local configuration of the core network device.
  • the core network device obtains subscription data of the terminal, and the subscription data includes data transmission parameters.
  • the data transmission parameters may include a server IP address, a protocol type, and a destination port.
  • the core network device can obtain the subscription data of the terminal from the HSS. This method has less modification to the existing signaling, is simple to implement, and does not need to change the local configuration of the core network device. Further, if the terminal is the first time accessing the network or the core network device cannot obtain the context information of the terminal from the previously attached core network device, the core network device can ensure that the data transmission parameter is obtained by acquiring the subscription data of the terminal.
  • the core network device receives data transmission parameters transmitted by the terminal.
  • the data transmission parameters may include the IP address and port of the terminal, the protocol type, and the IP address and port of the server.
  • the core network device may receive control signaling or an uplink data packet sent by the terminal, where the control signaling or the uplink data packet includes data transmission parameters. Therefore, when the terminal supports sending data transmission parameters to the base station, the core network device can obtain data transmission parameters more flexibly, and the content of the acquired data transmission parameters is more comprehensive.
  • the core network device receives a data transmission parameter sent by a Policy and Charging Rules Function (PCRF) entity.
  • data transmission Parameters can include server IP address, protocol type, and destination port.
  • the core network device can receive data transmission parameters sent by the PCRF entity during session establishment. Therefore, when the PCRF entity is deployed in the applied network architecture, the core network device can obtain data transmission parameters more flexibly, and the content of the data transmission parameter has better scalability.
  • PCRF Policy and Charging Rules Function
  • the core network device receives data transmission parameters sent by the server, where the server may be an M2M service platform or an Application Server (AS).
  • the data transmission parameters may include a server IP address, a protocol type, and a destination port.
  • the core network device can receive the data transmission parameter sent by the server through the open service interface; for example, the core network device can receive the downlink data packet sent by the server, and downlink.
  • the data transfer parameters are included in the packet. Therefore, the core network device can obtain data transmission parameters more flexibly, and the content of the data transmission parameters has better scalability.
  • the core network device assigns an identifier to the data transmission parameter, and the identifier is used to identify the data transmission parameter. For different data transmission parameters, the core network device allocates different identifiers, that is, the data transmission parameters and the identifiers have a unique correspondence relationship.
  • the core network device sends data transmission parameters and identities to the terminal.
  • the terminal receives data transmission parameters and identifiers sent by the core network device.
  • the method described in the foregoing sections 401 to 404 is a negotiation process
  • the negotiation process is a process in which the terminal and the core network device negotiate data transmission parameters and identifiers.
  • the terminal and the core network device may complete the negotiation process in the process of the connection initiated by the terminal or the Tracking Area Update (TAU).
  • TAU Tracking Area Update
  • the transmission process is a process in which the terminal and the core network device transmit the data packet based on the data transmission parameter and the identifier.
  • the method of the embodiment of the present invention may also include only the transmission process. That is to say, in the specific implementation of the embodiment of the present invention, only the negotiation process or the transmission process may be performed, and the negotiation process and the transmission process may also be performed. The above transmission process will be described below from the core network device and the terminal respectively.
  • the core network device can perform one of the following examples.
  • the operation of the core network device can also be implemented in other ways:
  • the core network device receives the first data packet, and the first data packet includes an identifier.
  • the core network device may receive the first data packet sent by the terminal after transmitting the data transmission parameter and the identifier to the terminal. Then, the core network device determines the data transmission parameter according to the identifier; or the core network device determines the data transmission parameter identified by the identifier according to the correspondence between the identifier and the data transmission parameter, where the data transmission parameter includes some or all of the information included in the IP header.
  • the core network device then processes the first data packet. For example, the core network device adds an IP header to the first data packet according to the data transmission parameter and removes the identifier to generate a second data packet or convert the first data packet into a second data packet.
  • the core network device adds an IP header corresponding to the data transmission parameter in the first data packet and removes the identifier, Generating a second data packet or converting the first data packet into a second data packet; for example, the core network device generates a second data packet according to the first data packet or converts the first data packet into a second data packet, where The second packet contains an IP header and does not contain an identifier. Further, the core network device may also send the second data packet to the M2M service platform or the AS.
  • the first data packet transmitted between the terminal and the core network device does not carry an IP header, that is, a non-IP data packet is transmitted between the terminal and the core network device, so that the header of the first data packet can be reduced.
  • the core network device can recover the IP header according to the data transmission identifier, generate the second data packet, or convert the first data packet into the second data packet.
  • the core network device after the core network device sends the data transmission parameter and the data transmission identifier to the terminal, the third data packet sent by the M2M service platform or the AS is also received, where the third data packet carries the data transmission parameter, where the data transmission parameter includes the IP. Some or all of the information contained in the header. The core network device then determines the identity based on the data transmission parameters.
  • the core network device processes the third data packet, for example, the core network device removes the IP header of the third data packet and adds an identifier in the third data packet to generate a fourth data packet or convert the third data packet into The fourth data packet; for example, the core network device generates the fourth data packet according to the third data packet or converts the third data packet into the fourth data packet, where the fourth data packet includes the identifier and does not include the IP header. Further, the core network device may further send the fourth data packet to the terminal. In this example, after receiving the third data packet, the core network device can remove the IP header, generate the fourth data packet, or convert the third data packet into the fourth data packet, that is, generate a non-IP data packet or generate IP data. The packet is converted into a non-IP data packet to send the non-IP data packet to the terminal, thereby reducing the overhead of data transmission between the core network device and the terminal, and improving the transmission efficiency.
  • the core network device may determine the identifier according to the IP header and the corresponding relationship included in the third data packet, where the correspondence relationship is a correspondence between the identifier and the data transmission parameter, where the data transmission parameter includes an IP header included Part or all of the information; then the core network device processes the third data packet.
  • the core network device may send the fourth data packet to the terminal. Similar to the above example, the core network device achieves similar effects by the way in this example, thereby improving the efficiency of transmission.
  • the terminal can perform one of the following examples.
  • the operation of the terminal can also be implemented in other ways:
  • the terminal receives the fifth data packet, where the fifth data packet includes an identifier, for example, the terminal receives the fifth data packet sent by the core network device; then, the terminal determines the data transmission parameter according to the identifier, or the terminal may also The correspondence of the data transmission parameters determines the data transmission parameters identified by the identifier, the data transmission parameters including some or all of the information contained in the IP header.
  • the terminal processes the fifth data packet, for example, the terminal adds an IP header in the fifth data packet according to the data transmission parameter and removes the identifier to generate the sixth data packet or convert the fifth data packet into the sixth data packet; for example, The terminal adds an IP header corresponding to the data transmission parameter in the fifth data packet and removes the identifier to generate the sixth data packet or convert the fifth data packet into the sixth data packet; for example, the terminal generates the first data packet according to the fifth data packet.
  • the sixth data packet or the fifth data packet is converted into the sixth data packet, wherein the sixth data packet includes an IP header and does not include an identifier. Further, the terminal can perform high-level processing on the sixth data packet.
  • the terminal after receiving the fifth data packet, that is, the non-IP data packet with small overhead, the terminal can recover the IP header according to the data transmission parameter, generate the sixth data packet, or convert the fifth data packet into the sixth data packet.
  • a data packet that is, an IP data packet is generated or a non-IP data packet is converted into an IP data packet, so that the terminal is suitable for high-level processing.
  • the terminal may determine the identifier according to the data transmission parameter included in the seventh data packet, or the terminal may determine the identifier according to the IP header and the corresponding relationship included in the seventh data packet, where the seventh data packet may be the terminal.
  • the correspondence relationship is the correspondence between the identifier and the data transmission parameter, and the data transmission parameter includes some or all of the information included in the IP header.
  • the terminal then processes the seventh data packet, for example, the terminal removes the IP header of the seventh data packet and adds an identifier in the seventh data packet to generate the eighth data packet or convert the seventh data packet into the eighth data packet; For another example, the terminal generates the eighth data packet according to the seventh data packet or converts the seventh data packet into the eighth data packet, where the eighth data packet includes the identifier and does not include the IP header. Further, the terminal may further send the eighth data packet to the core network device.
  • the terminal can remove the IP header of the seventh data packet, that is, remove the IP header of the IP data packet, generate the eighth data packet, or convert the seventh data packet into the eighth data packet, that is, generate a non-IP data packet or
  • the IP data packet is converted into a non-IP data packet, so that the non-IP data packet is transmitted between the terminal and the core network device, that is, the head overhead of the transmitted data packet can be reduced, and the data transmission between the terminal and the core network device is improved. effectiveness.
  • the embodiments of the present invention will be further described based on the network architecture shown in FIG. 1 , in which the terminal is the UE and the core network device is the MME or the PGW.
  • FIGS 5a - 10b will show various implementations of the negotiation process for data transmission parameters and identification.
  • FIG. 5a and FIG. 5b are schematic diagrams of communication of a method for negotiating data transmission parameters and identifiers according to an embodiment of the present invention.
  • the core network device acquires data transmission parameters by static configuration.
  • the core network device is an MME; in the method shown in FIG. 5b, the core network device is a PGW.
  • MME mobile phone
  • PGW packet gateway
  • the UE sends an attach request message to the MME, where the attach request message carries a data transmission indication, where the data transmission indication is used to indicate a data packet containing the data transmission parameter or server information or service information related to the data packet.
  • the MME After receiving the attach request sent by the UE, the MME acquires a locally configured data transmission parameter corresponding to the data packet according to the data transmission indication.
  • Locally configured data transfer parameters can be packaged Includes server IP address, protocol type, and destination port.
  • the MME sends a create session request message to the PGW, and the create session request message carries the data transmission parameter.
  • the PGW after receiving the create session request message sent by the MME, the PGW saves the data transmission parameters. Therefore, when the PGW receives the downlink data packet, it may identify, according to the data transmission parameter, whether the downlink data packet is the foregoing data packet, so as to send the data packet to the MME.
  • the PGW sends a create session response message to the MME.
  • the MME After receiving the create session response message sent by the PGW, the MME allocates an identifier for the data transmission parameter, where the identifier is used to identify the data transmission parameter.
  • the MME sends an attach accept message to the UE, and the attach accept message carries the data transmission parameter and the identifier.
  • the UE receives the attach accept message sent by the MME, so that the data packet can be transmitted based on the data transmission parameter and the identifier in a subsequent transmission process.
  • the method shown in FIG. 5b is similar to the method shown in FIG. 5a.
  • the core network device is a PGW
  • the PGW acquires the locally configured data transmission parameter according to the data transmission indication, and transmits the data transmission parameter.
  • the parameter assigns an identity and then sends the data transmission parameters and identity to the UE.
  • FIG. 6a and FIG. 6b are schematic diagrams of communication of another method for negotiating data transmission parameters and identifiers according to an embodiment of the present invention.
  • the core network device obtains data transmission parameters by requesting context information of the UE from a core network device attached to the UE, where the core network device to which the UE is previously attached is the source MME or the source SGSN. .
  • the core network device is the target MME; in the method shown in FIG. 6b, the core network device is the PGW.
  • FIG. 6a the core network device is the target MME; in the method shown in FIG. 6b, the core network device is the PGW. The following is an example of FIG. 6a.
  • the 601 part and the 604-608 part are respectively similar to the 501 part and the 503-507 part of the method shown in FIG. 5a, wherein the function of the MME in the method shown in FIG. 5a is implemented by the target MME in the method shown in FIG. 6a, and the other The content is not described in detail.
  • the target MME after receiving the attach request sent by the UE, the target MME sends a context request message to the source MME or the source SGSN according to the data transmission indication to request the context information of the UE.
  • the source MME or the source SGSN after receiving the Context Request message sent by the target MME, the source MME or the source SGSN sends a context response message including the context information of the UE to the target MME, where the context information of the UE carries the data transmission parameter.
  • the target MME receives the context response message sent by the source MME or the source SGSN.
  • the method shown in Figure 6b is similar to the method shown in Figure 6a, except that the method shown in Figure 6b
  • the core network device is a PGW, and the PGW receives the data transmission parameter sent by the target MME, and assigns an identifier to the data transmission parameter, and then sends the data transmission parameter and the identifier to the target MME, and then the target MME sends the data transmission parameter and the identifier.
  • the PGW can also only send the identifier to the target MME.
  • the PGW sends the data transmission parameter and the identifier together to the target MME, which can simplify the operation of the target MME and reduce the risk that the target MME matches the data transmission parameter and the identifier.
  • the target MME can simplify the operation of the target MME and reduce the risk that the target MME matches the data transmission parameter and the identifier.
  • FIG. 7a and FIG. 7b are schematic diagrams of communication of a method for negotiating data transmission parameters and identifiers according to an embodiment of the present invention.
  • the core network device acquires data transmission parameters by acquiring subscription data of the UE from the HSS.
  • the core network device is an MME; in the method shown in FIG. 7b, the core network device is a PGW. The following description will be made by taking FIG. 7a as an example.
  • the 701 part and the 703-707 parts are similar to the 501 part and the 503-507 part of the method shown in FIG. 5a, respectively, and are not described herein.
  • the MME and the HSS perform the process of acquiring the subscription data, and the MME obtains the subscription data of the UE from the HSS, and the subscription data of the UE carries the data transmission parameter.
  • the method shown in FIG. 7b is similar to the method shown in FIG. 7a.
  • the core network device is a PGW
  • the PGW receives the data transmission parameter sent by the MME, and assigns an identifier to the data transmission parameter.
  • the data transmission parameter and the identifier are sent to the MME, or only the identifier is sent to the MME, and then the MME sends the data transmission parameter and the identifier to the UE.
  • the core network device is a PGW
  • the PGW receives the data transmission parameter sent by the MME, and assigns an identifier to the data transmission parameter.
  • the data transmission parameter and the identifier are sent to the MME, or only the identifier is sent to the MME, and then the MME sends the data transmission parameter and the identifier to the UE.
  • FIG. 8a and FIG. 8b are schematic diagrams of communication of a method for negotiating data transmission parameters and identifiers according to an embodiment of the present invention.
  • the core network device receives data transmission parameters transmitted by the terminal.
  • the core network device is an MME; in the method shown in FIG. 8b, the core network device is a PGW.
  • MME mobile phone
  • PGW packet gateway
  • the portions 804 to 807 are similar to the portions 503 to 507 in the method shown in FIG. 5a, and are not described herein.
  • an attach procedure is performed between the UE and the MME, and the UE is attached to the EPS system.
  • the UE registers with the M2M service platform or AS through the application layer message, and acquires data transmission parameters from the M2M service platform or the AS.
  • the UE sends a TAU request message to the MME, where the TAU request message carries data transmission parameters.
  • the MME receives the TAU request message sent by the UE.
  • the MME sends a TAU accept message to the UE, where the TAU receive message carries the data transmission parameter and the identifier.
  • the UE receives the TAU accept message sent by the MME, so that the data packet can be transmitted based on the data transmission parameter and the identifier in a subsequent transmission process.
  • the method shown in FIG. 8b is similar to the method shown in FIG. 8a.
  • the core network device is a PGW
  • the PGW receives the data transmission parameter sent by the MME, and assigns an identifier to the data transmission parameter.
  • the data transmission parameter and the identifier are sent to the MME, or only the identifier is sent to the MME, and then the MME sends the data transmission parameter and the identifier to the UE.
  • the core network device is a PGW
  • the PGW receives the data transmission parameter sent by the MME, and assigns an identifier to the data transmission parameter.
  • the data transmission parameter and the identifier are sent to the MME, or only the identifier is sent to the MME, and then the MME sends the data transmission parameter and the identifier to the UE.
  • FIG. 9a and FIG. 9b are schematic diagrams of communication of a method for negotiating data transmission parameters and identifiers according to an embodiment of the present invention.
  • the core network device receives data transmission parameters transmitted by the PCRF entity during session establishment.
  • the core network device is an MME; in the method shown in FIG. 9b, the core network device is a PGW.
  • the core network device is a PGW. The following description will be made by taking FIG. 9a as an example.
  • the 901 part, the 906 part and the 907 part are similar to the 501 part, the 506 part and the 507 part of the method shown in Fig. 5a, respectively, and are not described herein.
  • the MME after receiving the attach request message sent by the UE, the MME sends a create session request message to the PGW, where the create session request message carries the data transmission indication.
  • the PGW after receiving the create session request message sent by the MME, the PGW sends a gateway control session establishment message to the PCRF entity for requesting data transmission parameters.
  • the PCRF entity after receiving the gateway control session establishment message sent by the PGW, the PCRF entity sends a gateway control session establishment confirmation message to the PGW, and the gateway control session establishment confirmation message carries the data transmission parameter.
  • the PGW after receiving the gateway control session establishment confirmation message sent by the PCRF entity, the PGW sends a create session response message to the MME, where the session response message carries the data transmission parameter.
  • the MME receives the create session response message sent by the PGW.
  • the method shown in FIG. 9b is similar to the method shown in FIG. 9a.
  • the core network device is a PGW
  • the PGW assigns an identifier to the data transmission parameter.
  • the data transmission parameter and the identifier are sent to the MME, or only the identifier is sent to the MME, and then the MME sends the data transmission parameter and the identifier to the UE.
  • the core network device is a PGW
  • the PGW assigns an identifier to the data transmission parameter.
  • the data transmission parameter and the identifier are sent to the MME, or only the identifier is sent to the MME, and then the MME sends the data transmission parameter and the identifier to the UE.
  • FIG. 10a and FIG. 10b are schematic diagrams of communication of a method for negotiating data transmission parameters and identifiers according to an embodiment of the present invention.
  • the core network device receives the data transmission parameters sent by the M2M service platform or the AS.
  • the core network device is an MME; in the method shown in FIG. 10b, the core network device is a PGW.
  • FIG. 10a the core network device is an MME; in the method shown in FIG. 10b, the core network device is a PGW.
  • the 1001 part and the 1004 ⁇ 1008 parts are similar to the 501 part and the 503-507 part of the method shown in FIG. 5a, respectively, and are not described herein.
  • the MME After receiving the attach request message sent by the UE, the MME obtains the address of the M2M service platform or the AS according to the access point name (APN) provided by the UE, and then passes the Service Capability Exposure Function (Service Capability Exposure Function, The SCEF) entity's service open interface sends a request message to the M2M service platform or AS for requesting data transmission parameters.
  • API access point name
  • the SCEF Service Capability Exposure Function
  • the M2M service platform or the AS after receiving the request message sent by the MME, the M2M service platform or the AS sends a response message to the MME through the SCEF entity, where the response message carries the data transmission parameter.
  • the MME receives the response message sent by the M2M service platform or the AS.
  • the method shown in FIG. 10b is similar to the method shown in FIG. 10a.
  • the core network device is a PGW
  • the PGW assigns an identifier to the data transmission parameter, and then The data transmission parameter and the identifier are sent to the MME, or only the identifier is sent to the MME, and then the MME sends the data transmission parameter and the identifier to the UE.
  • the core network device is a PGW
  • the PGW assigns an identifier to the data transmission parameter, and then The data transmission parameter and the identifier are sent to the MME, or only the identifier is sent to the MME, and then the MME sends the data transmission parameter and the identifier to the UE.
  • Figures 11-14 will illustrate various implementations of a transmission process based on data transmission parameters and identification.
  • FIG. 11 is a schematic diagram of communication of a method for data transmission based on data transmission parameters and identifiers according to an embodiment of the present invention.
  • the core network device is an MME.
  • the data transmission parameter and the identifier negotiation process are performed between the UE and the MME.
  • the UE and the MME locally store data transmission parameters and identifiers.
  • the data packet to be sent by the UE is an IP data packet
  • the IP header of the IP data packet carries the data transmission parameter
  • the UDP payload is the application layer data that the UE needs to send to the M2M service platform or the AS. If the data transmission parameter carried by the IP header of the to-be-transmitted data packet is the same as the data transmission parameter saved by the UE, the UE determines that the UDP payload carried in the data packet to be sent is small data.
  • the UE removes the IP header in the IP data packet to be sent to generate or convert into a small data packet, and carries the identifier and the EPS bearer identifier in the small data packet, and then encapsulates the small data packet into the NAS message.
  • the EPS bearer identifier is used by the MME to determine the SGW/PGW to which the small data packet should be sent.
  • an RRC connection setup procedure is performed between the UE and the eNB, and the UE sends a NAS message to the eNB in the RRC connection setup process.
  • the eNB after receiving the NAS message sent by the UE, the eNB sends an initial UE message to the MME, where the initial UE message carries the NAS message.
  • the MME After receiving the initial UE message sent by the eNB, the MME extracts the small data packet in the NAS message, removes the identifier and the EPS bearer identifier in the small data packet, and determines the corresponding data transmission parameter according to the identifier, according to the data transmission parameter. Add IP headers for small packets, convert small packets into IP packets, and then encapsulate IP packets into GPRS tunneling protocol (GPRS Tunneling) Protocol, GTP) packet.
  • GPRS Tunneling GPRS Tunneling Protocol
  • the MME obtains the IP address of the SGW according to the EPS bearer identifier, and sends a GTP data packet to the SGW.
  • the SGW after receiving the GTP data packet sent by the MME, the SGW sends a GTP data packet to the PGW.
  • the PGW decapsulates the GTP data packet into an IP data packet.
  • the PGW sends an IP data packet to the M2M service platform or the AS.
  • the M2M service platform or the AS receives the IP data packet sent by the PGW.
  • part 1101 is optional.
  • the information may be obtained from the 1102 part. The method shown in Fig. 11 is started.
  • FIG. 12 is a schematic diagram of communication of another method for data transmission based on data transmission parameters and identifiers according to an embodiment of the present invention.
  • the core network device is a PGW.
  • the sections 1201 to 1205 are similar to the sections 1101 to 1105 in the method shown in FIG. 11, respectively.
  • the UE and the PGW both locally store data transmission parameters and identifiers, and other contents are not described herein. .
  • the MME After receiving the initial UE message sent by the eNB, the MME extracts the small data packet in the NAS message, and encapsulates the small data packet into a GTP data packet, where the small data packet carries the UDP payload, the identifier, and the EPS bearer identifier. .
  • the MME obtains the IP address of the SGW according to the EPS bearer identifier, and sends a GTP data packet to the SGW.
  • the SGW after receiving the GTP data packet sent by the MME, the SGW sends a GTP data packet to the PGW.
  • the PGW decapsulates the GTP data packet into a small data packet, removes the identifier and the EPS bearer identifier in the small data packet, and determines the corresponding data transmission parameter according to the identifier, according to the data.
  • the transmission parameters add IP headers for small packets and convert small packets to IP packets.
  • the PGW sends an IP packet to the M2M service platform or AS.
  • the 1201 portion is similar to the above 1101 portion and is also optional.
  • FIG. 13 is a schematic diagram of communication according to another method for data transmission based on data transmission parameters and identifiers according to an embodiment of the present invention.
  • the core network device is an MME.
  • the data transmission parameter and the identifier negotiation process are performed between the UE and the MME.
  • the UE and the MME locally store data transmission parameters and identifiers.
  • the M2M service platform or AS sends an IP data packet to the PGW, and the IP header of the IP data packet carries the data transmission parameter.
  • the PGW determines that the IP data packet is transmitted as small data according to the data transmission parameter.
  • the PGW encapsulates the IP data packet into a GTP data packet, and carries a small data indication in the GTP data packet, and the small data indication is used to indicate that the transmission of the IP data packet carried in the GTP data packet is a small data transmission.
  • the PGW sends a GTP packet to the SGW.
  • the SGW determines that the transmission of the IP data packet is a small data transmission according to the small data indication.
  • the SGW sends a GTP data packet to the MME through a Downlink Data Notification (DDN) message.
  • DDN Downlink Data Notification
  • the MME sends a paging message to the eNB, and the paging message carries a small data indication.
  • the eNB after receiving the paging message sent by the MME, the eNB sends a paging message to the UE, where the paging message carries a small data indication.
  • the UE after receiving the paging message sent by the eNB, the UE sends a service request to the MME.
  • the MME after receiving the service request sent by the UE, the MME sends a DDN confirmation message to the SGW.
  • the MME decapsulates the GTP data packet into an IP data packet, removes the IP header of the IP data packet, and carries the corresponding identifier and the EPS bearer identifier in the IP data packet according to the data transmission parameter, thereby converting the IP data packet into Small packets and encapsulate small packets in NAS messages.
  • the MME sends a NAS message to the eNB.
  • the eNB after receiving the NAS message sent by the MME, the eNB sends a NAS message to the UE.
  • the UE extracts a small data packet from the NAS message, removes the identifier and the EPS bearer identifier, determines a corresponding data transmission parameter according to the identifier, and adds an IP header to the small data packet according to the data transmission parameter, thereby converting the small data packet IP packets are submitted to the high-level application protocol.
  • part 1301 is similar to the above part 1101 and is also optional.
  • FIG. 14 is a schematic diagram of communication according to another method for data transmission based on data transmission parameters and identifiers according to an embodiment of the present invention.
  • the core network device is a PGW.
  • the 1401 ⁇ 1403 part and the 1413 ⁇ 1415 part are similar to the 1301 ⁇ 1303 part and the 1313 ⁇ 1315 part in the method shown in FIG. 13, respectively, wherein in the 1401 part, after the UE and the PGW complete the negotiation process, the UE and the PGW are locally saved. Data transmission parameters and identification, other content will not be described.
  • the PGW removes the IP header of the IP packet, based on the number of data transmission parameters in the IP.
  • the IP data packet is converted into a small data packet, and then the small data packet is encapsulated into a GTP data packet, and the small data indication is carried in the GTP data packet, and the small data indication is used to indicate the GTP data packet.
  • the transmission of the data packets carried in is a small data transmission.
  • the PGW sends a GTP packet to the SGW.
  • the SGW determines that the transmission of the IP data packet is a small data transmission according to the small data indication.
  • the SGW sends a Downlink Data Notification (DDN) message to the MME, where the DDN message carries the GTP data packet.
  • DDN Downlink Data Notification
  • the MME sends a paging message to the eNB, and the paging message carries a small data indication.
  • the eNB After receiving the paging message sent by the MME, the eNB sends a paging message to the UE, where the paging message carries a small data indication.
  • the UE after receiving the paging message sent by the eNB, the UE sends a service request to the MME.
  • the MME after receiving the service request sent by the UE, the MME sends a DDN confirmation message to the SGW.
  • the MME decapsulates the GTP data packet into a small data packet, and carries the EPS bearer identifier in the small data packet, and then encapsulates the small data packet in the NAS message.
  • the 1401 portion is similar to the above 1101 portion and is also optional.
  • the core network device that implements some of the above methods may also be an SGSN, for example, the MME or the target in the methods shown in FIG. 5a, 6a, 7a, 8a, 9a, 10a, 11 and 13 above.
  • the function of the MME can be done by the SGSN.
  • FIG. 5a through 14 can also be implemented in the network architecture illustrated in Figures 2 and 3.
  • the functions of the MME or the target MME in the methods shown in FIG. 5a, 6a, 7a, 8a, 9a, 10a, 11 and 13 are as shown in FIG. 2.
  • the functions of the PGW in the methods shown in Figures 5b, 6b, 7b, 8b, 9b, 10b, 12 and 14 are implemented by the C-SGN in Figure 2.
  • FIG. 5a to FIG. 14 is applied to the network architecture shown in FIG.
  • the functions of the MME or the target MME in the methods shown in FIG. 5a, 6a, 7a, 8a, 9a, 10a, 11 and 13 are as shown in FIG. 3.
  • the functions of the PGW in the methods shown in Figures 5b, 6b, 7b, 8b, 9b, 10b, 12 and 14 are implemented by the PGW in Figure 3.
  • the terminal involved in the embodiments of the present invention may include various handheld devices, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to the wireless demodulator, and each of the wireless communication functions.
  • MS mobile station
  • M2M device M2M device
  • TE Terminal Device
  • each network element such as a terminal, a core network device, etc.
  • each network element includes hardware structures and/or software modules corresponding to each function.
  • the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. Those skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • FIG. 15 is a schematic diagram showing a possible structure of a core network device involved in the above embodiment.
  • the core network device may be an MME or a PGW in the network architecture shown in FIG. 2, or may be a C-SGN in the network architecture shown in FIG. 2, or may be a C-SGN in the network architecture shown in FIG. PGW.
  • the core network device includes a memory 1501, a controller/processor 1502, and a network interface 1503.
  • the controller/processor 1502 is used to control and manage the actions of the core network device.
  • controller/processor 1502 is configured to support core network devices to perform processes 401-403 in FIG. 4, processes 502, 503, 506, and 507 in FIG. 5a, processes 530, 540, and 550 in FIG. 5b, FIG. 6a Processes 602, 604, 607, and 608, processes 650 and 660 in Figure 6b, processes 702, 703, 706, and 707 in Figure 7a, processes 740 and 750 in Figure 7b, processes 801, 802 in Figure 8a 804, 807, and 808, processes 810, 820, 850, and 860 in FIG.
  • the memory 1501 is for storing program codes and data for the core network device.
  • Network interface 1503 is used to support communication of core network devices with other network entities, such as communications with the terminals shown in FIG. 16, and for example, with various network entities shown in FIG. 1, FIG. 2, or FIG.
  • FIG. 16 is a schematic diagram showing a possible structure of a terminal involved in the above embodiment.
  • the terminal includes a transmitter 1601, a receiver 1602, a controller/processor 1603, a memory 1604, and a modem processor 1605.
  • the transmitter 1601 adjusts (e.g., analog conversion, filtering, amplifying, upconverting, etc.) the output samples and generates an uplink signal that is transmitted via an antenna to the eNB in the above embodiment for transmission to the core network device.
  • the antenna receives the downlink signal transmitted by the core network device through the eNB in the above embodiment.
  • Receiver 1602 conditions (eg, filters, amplifies, downconverts, digitizes, etc.) the signals received from the antenna and provides input samples.
  • encoder 1606 receives the traffic data and signaling messages to be transmitted on the uplink and processes (e.g., formats, codes, and interleaves) the traffic data and signaling messages.
  • Modulator 1607 further The encoded service data and signaling messages are processed (eg, symbol mapped and modulated) and output samples are provided.
  • Demodulator 1609 processes (e.g., demodulates) the input samples and provides symbol estimates.
  • the decoder 1608 processes (e.g., deinterleaves and decodes) the symbol estimate and provides decoded data and signaling messages that are sent to the UE.
  • Encoder 1606, modulator 1607, decoder 1608, and demodulator 1609 may be implemented by a composite modem processor 1605. These units are processed according to the radio access technologies employed by the radio access network (e.g., LTE systems, CIoT systems, and access technologies of other evolved systems).
  • the controller/processor 1603 controls and manages the actions of the terminal for performing the processing performed by the terminal in the above embodiment. For example, other processes for controlling the processing of the data packet by the terminal in accordance with the data transmission parameters and identification and/or the described scheme of the present invention.
  • the controller/processor 1103 is configured to support the terminal to perform the process 404 of FIG. 4, the process 501 of FIG. 5a, the process 510 of FIG. 5b, the process 601 of FIG. 6a, the process 610 of FIG. 6b, and the figure.
  • the memory 1604 is used to store program codes and data for the terminal.
  • the controller/processor for performing the functions of the above-mentioned core network device or terminal of the present invention may be a central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), and a dedicated integration.
  • CPU central processing unit
  • DSP digital signal processor
  • ASIC Application-Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the steps of a method or algorithm described in connection with the present disclosure may be implemented in a hardware, or may be implemented by a processor executing software instructions.
  • the software instructions may be composed of corresponding software modules, which may be stored in a random access memory (RAM), a flash memory, a read only memory (ROM), an erasable programmable read only memory ( Erasable Programmable ROM (EPROM), electrically erasable programmable read only memory (EEPROM), registers, hard disk, removable hard disk, compact disk read only (CD-ROM) or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in the terminal.
  • the processor and the storage medium can also exist as discrete components in the terminal.
  • the functions described herein can be implemented in hardware, software, firmware, or any combination thereof.
  • the functions may be stored in a computer readable medium 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 general purpose or special purpose computer.

Abstract

本发明涉及通信领域，尤其涉及一种数据传输的方法和装置。在一种数据传输的方法中，核心网设备获取数据传输参数，数据传输参数包含互联网协议IP头包含的信息中的部分或全部；核心网设备为数据传输参数分配标识，标识用于标识该数据传输参数；核心网设备向终端发送数据传输参数和标识。通过本发明提供的方案，可以避免在传输数据前因建立承载而造成开销浪费。

Description

数据传输的方法和装置 技术领域
本发明涉及通信领域，尤其涉及一种数据传输的方法及装置和系统。
背景技术
在移动通信系统中，一些机器对机器(Machine to Machine，M2M)应用在网络中传输的数据包仅携带很小的数据量，这就涉及到小数据传输(Small Data Transmission，SDT)。例如，水表、电表、传感器等终端主要通过网络发送数据量很小的抄表数据或监测数据，一次传输的数据包携带的数据量通常只有几十到几百个字节。而目前的通信系统是针对传输数据量较大的数据所设计的。例如，在现有的长期演进(Long Term Evolution，LTE)系统中，当空闲态的终端有数据需要传输时，即使所需要传输的数据是小数据，终端也需要在发送数据之前先发起业务请求过程来建立空口和S1接口的承载，并且需要下载无线资源控制(Radio Resource Control，RRC)安全上下文信息到演进节点B(evolved NodeB，eNodeB或eNB)中。然而，对于小数据传输而言，在传输小数据之前，这样建立承载和后续操作所带来的开销是非常浪费的。
发明内容
本发明实施例提供一种数据传输的方法，装置和系统，以解决传输数据前需建立承载造成开销浪费的问题。
一方面，本发明实施例提供了一种数据传输的方法，包括：核心网设备获取数据传输参数，数据传输参数包含互联网协议IP头包含的信息中的部分或全部；并为数据传输参数分配标识，标识用于标识所述数据传输参数；以及向终端发送数据传输参数和标识。其中，IP头可以包括用户数据包协议UDP头。从而核心网设备通过获取数据传输参数并分配标识，以及将数据传输参数和标识发送给终端，能够避免在传输数据前因建立承载而造成开销浪费。
在一种可能的设计中，核心网设备可以根据终端的指示获取数据传输参数。例如，在核心网设备获取数据传输参数之前，终端可以向核心网设备发送数据传输指示，数据传输指示用于指示包含数据传输参数的数据包或者与该数据包相关的服务器信息或业务信息；对应的，核心网设备接收终端发送的数据传输指示，并根据数据传输指示获取数据传输参数。
在一种可能的设计中，核心网设备可以通过以下方式之一获取数据传输 参数。第一种方式：核心网设备获取本地配置的数据传输参数，其中，本地配置的数据传输参数可以包括服务器地址和端口信息。这种静态配置的方式对现有的信令改动较小，实现方式简单，具有较好的兼容性。第二种方式：核心网设备通过终端的上下文信息获取数据传输参数，例如，核心网设备从终端之前附着的核心网设备获取终端的上下文信息，该终端的上下文信息中包含数据传输参数。第三种方式：核心网设备通过终端的签约数据获取数据传输参数，例如，核心网设备从HSS获取终端的签约数据，该终端的签约数据中包含数据传输参数。第二种和第三种方式对现有的信令改动也较小，实现方式简单，且不需要对核心网设备的本地配置进行改变。第四种方式：核心网设备接收终端发送的数据传输参数，例如，核心网设备接收终端发送的控制信令或上行数据包，该控制信令或上行数据包中包含数据传输参数。这种方式中，核心网设备可以更为灵活地获取数据传输参数，且所获取的数据传输参数的内容更加全面。第五种方式：核心网设备接收策略与计费规则功能PCRF实体发送的数据传输参数，例如，核心网设备接收PCRF实体在会话建立过程中发送的数据传输参数。第六种方式：核心网设备接收服务器发送的数据传输参数，例如，核心网设备接收服务器通过开放业务接口发送的数据传输参数，又例如，核心网设备接收服务器发送的下行数据包，下行数据包中包含数据传输参数。第五种和第六种方式中，核心网设备可以更为灵活地获取数据传输参数，且数据传输参数的内容具有较好的扩展性。当然，核心网设备还可以通过其他方式获取数据传输参数。
在一种可能的设计中，核心网设备向终端发送数据传输参数和标识之后，还接收终端发送的第一数据包，第一数据包携带标识；以及根据标识确定数据传输参数；然后对第一数据包进行处理，例如，核心网设备根据数据传输参数在第一数据包中添加IP头并去除标识，以生成第二数据包或将第一数据包转换成第二数据包，又例如，核心网设备在第一数据包中添加数据传输参数对应的IP头并去除标识，以生成第二数据包或将第一数据包转换为第二数据包，又例如，核心网设备根据第一数据包生成第二数据包或将第一数据包转换为第二数据包，其中，第二数据包包含IP头且不包含标识。进一步的，核心网设备还可以向M2M业务平台或AS发送第二数据包。在这种设计中，一方面，终端与核心网设备之间传输的第一数据包不携带IP头，即终端与核心网设备之间传输的是非IP数据包，从而能够减少第一数据包的头开销，提高数据传输的效率；另一方面，核心网设备接收到携带标识的第一数据包后，能够根据数据传输标识恢复IP头，生成第二数据包或者将第一数据包转换为第二数据包，即生成IP数据包或将非IP数据包转换为IP数据包，从而适于在核心网设备与M2M业务平台或AS之间传输。
在一种可能的设计中，核心网设备向终端发送数据传输参数和标识之后，还接收M2M业务平台或AS发送的第三数据包，第三数据包携带数据传输参数；以及根据数据传输参数确定标识；然后对第三数据包进行处理，例如，核心网设备去除第三数据包的IP头并在第三数据包中添加标识，以生成第四数据包或将第三数据包转换为第四数据包，又例如，核心网设备根据第三数据包生成第四数据包或将第三数据包转换为第四数据包，其中，第四数据包包含标识且不包含IP头。进一步地，核心网设备还可以向终端发送第四数据包。在这种设计中，核心网设备在接收到第三数据包后，能够去除IP头，生成第四数据包或将第三数据包转换为第四数据包，即生成非IP数据包或将IP数据包转换为非IP数据包，以向终端发送该非IP数据包，因此能够减少核心网设备与终端之间数据传输的开销，提高传输的效率。
另一方面，本发明实施例提供了另一种数据传输的方法，包括：根据第一数据包包含的标识与数据传输参数的对应关系，确定标识所标识的数据传输参数，所述数据传输参数包含互联网协议IP头包含的信息中的部分或全部，其中IP头可以包括用户数据报协议UDP头；以及对第一数据包进行处理，例如，根据数据传输参数在第一数据包中添加IP头并去除标识，以生成第二数据包或将第一数据包转换成第二数据包，又例如，在第一数据包中添加数据传输参数对应的IP头并去除标识，以生成第二数据包或将第一数据包转换为第二数据包，又例如，根据第一数据包生成第二数据包或将第一数据包转换为第二数据包，其中，第二数据包包含IP头且不包含标识。在一种可能的实现方式中，本方面中的方法可以不包括上述部分，而是包括以下另一部分，当然，本方面的方法也可以既包含上述部分，也包含以下另一部分。以下另一部分包括：根据第三数据包中包含IP头和对应关系确定标识，其中，所述对应关系为所述标识和数据传输参数的对应关系，所述数据传输参数包含IP头包含的信息中的部分或全部；以及对第三数据包进行处理，例如，去除第三数据包的IP头并在第三数据包中添加标识，以生成第四数据包或将第三数据包转换为第四数据包，又例如，根据第三数据包生成第四数据包或将第三数据包转换为第四数据包，其中，第四数据包包含标识且不包含IP头。通过本方面的方法，能够根据数据传输参数和标识去除或添加数据包的IP头，从而使得数据包在适于传输的情况下，降低了传输该数据包的开销，提高了传输效率。
在一种可能的设计中，在得到第二数据包之后，还可以向M2M平台或AS发送第二数据包；或者，在得到第四数据包之后，还可以向终端发送第四数据包。例如，这种设计中的方法适用于核心网设备，使得核心网设备能够向M2M或AS发送适于传输的IP数据包，或者使得核心网设备能够向终端 发送不携带IP头的非IP数据包，从而能够降低传输的开销，提高传输效率。
在另一种可能的设计中，在得到第二数据包之后，还可以对第二数据包进行高层处理；或者，在得到第四数据包之后，还可以向核心网设备发送第四数据包。例如，这种设计中的方法适用于终端，使得终端能够对得到的IP数据包进行高层处理，或者使得终端能够向核心网设备发送不携带IP头的非IP数据包，从而能够降低传输的开销，提高传输效率。
又一方面，本发明实施例提供了一种核心网设备，该核心网设备具有实现上述方法设计中核心网设备行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，核心网设备的结构中包括处理器和网络接口，所述处理器被配置为支持核心网设备执行上述方法中相应的功能，所述网络接口用于支持核心网设备与终端之间的通信，向终端发送上述方法中所涉及的信息或者指令。例如，处理器用于获取数据传输参数，数据传输参数包含互联网协议IP头包含的信息中的部分或全部，其中IP头可以包括用户数据报协议UDP头；以及用于为数据传输参数分配标识，标识用于标识数据传输参数；还用于通过网络接口向终端发送数据传输参数和标识。所述核心网设备还可以包括存储器，所述存储器用于与处理器耦合，其保存核心网设备必要的程序指令和数据。
又一方面，本发明实施例提供了一种终端，该终端具有实现上述方法设计中终端行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相应对应的模块。
在一种可能的设计中，终端的结构中包括接收器和处理器，所述处理器被配置为支持终端执行上述方法中相应的功能，所述接收器被配置为支持终端接收上述方法中所涉及的核心网设备发送的信息或者指令。例如，所述接收器用于接收核心网设备发送的数据传输参数和标识，数据传输参数包括互联网协议IP头包含的信息中的部分或全部，其中IP头可以包括用户数据报协议UDP头，标识用于标识所述数据传输参数；所述处理器用于根据数据传输参数和标识对数据包处理。所述终端还可以包括发射器，所述发射器被配置为支持终端向核心网设备发送上述方法中所涉及的信息或者指令。所述终端还可以包括存储器，所述存储器与所述处理器耦合，其保存终端必要的程序指令和数据。
又一方面，本发明实施例提供了一种通信系统，该系统包括上述方面所述的核心网设备和终端。
再一方面，本发明实施例提供了一种计算机存储介质，用于储存为上 述核心网设备所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
再一方面，本发明实施例提供了一种计算机存储介质，用于储存为上述终端所用的计算机软件指令，其包含用于执行上述方面所设计的程序。
相较于现有技术，本发明提供的方案中，核心网设备通过获取数据传输参数并分配标识，以及将数据传输参数和标识发送给终端，能够避免在传输数据前由于在终端与核心网络之间建立承载而造成开销浪费。进一步的，核心网设备和终端能够基于上述数据传输参数和标识对数据包进行处理，使得核心网设备与终端之间所传输的数据包不携带IP头，从而减少核心网设备与终端之间传输数据的开销，提高数据传输的效率。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作一简单地介绍，显而易见地，下面描述中的附图是本发明的一些实施例，对于本领域普通技术人员来说，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为实现本发明的一种可能的系统网络示意图；
图2为实现本发明的另一种可能的系统网络示意图；
图3为实现本发明的又一种可能的系统网络示意图；
图4为本发明实施例提供的一种数据传输的方法的流程示意图；
图5a和图5b为本发明实施例提供的一种协商数据传输参数和标识的方法的通信示意图；
图6a和图6b为本发明实施例提供的另一种协商数据传输参数和标识的方法的通信示意图；
图7a和图7b为本发明实施例提供的又一种协商数据传输参数和标识的方法的通信示意图；
图8a和图8b为本发明实施例提供的又一种协商数据传输参数和标识的方法的通信示意图；
图9a和图9b为本发明实施例提供的又一种协商数据传输参数和标识的方法的通信示意图；
图10a和图10b为本发明实施例提供的又一种协商数据传输参数和标识的方法的通信示意图；
图11为本发明实施例提供的一种基于数据传输参数和标识的数据传输的方法的通信示意图；
图12为本发明实施例提供的另一种基于数据传输参数和标识的数据传 输的方法的通信示意图；
图13为本发明实施例提供的又一种基于数据传输参数和标识的数据传输的方法的通信示意图；
图14为本发明实施例提供的又一种基于数据传输参数和标识的数据传输的方法的通信示意图；
图15为本发明实施例提供的一种核心网设备的结构示意图；
图16为本发明实施例提供的一种终端的结构示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行描述。
本发明实施例描述的网络架构以及业务场景是为了更加清楚的说明本发明实施例的技术方案，并不构成对于本发明实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本发明实施例提供的技术方案对于类似的技术问题，同样适用。
图1为本发明实施例提供的一种演进分组系统(Evolved Packet System，EPS)网络架构的示意图，其主要包括(User Equipment，UE)，接入网络，核心网络以及运营商互联网协议(Internet Protocol，IP)业务网络。如图1所示，UE接入接入网后，通过通用分组无线系统(General Packet Radio System，GPRS)业务支撑节点(Serving GPRS Support Node，SGSN)或移动性管理实体(Mobility Management Entity，MME)接入到服务网关(Serving Gateway，SGW)，然后接入到分组数据网络网关(Packet Data Network Gateway，PDN-GW或PGW)及运营商IP业务网络。
图2为本发明实施例提供的一种非漫游场景的蜂窝物联网(Cellular Internet of Things，CIoT)的网络架构的示意图。CIoT是指基于蜂窝网络的物联网，目前，第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)正在开展基于CIoT的项目研究，通过对蜂窝网络架构增强以支持超低复杂度、功率受限、低数据速率的物联网设备，研究如何支持频繁和不频繁的小数据包的有效传输，支持终端功率消耗优化，支持覆盖增强场景下的寻呼优化，并简化移动性管理和会话管理信令。图2中，CIoT服务网关节点(CIoT Serving Gateway Node，C-SGN)为新引入的逻辑实体，用于支持与CIoT应用场景相关的功能，例如，支持部分必需的移动性管理流程，支持有效的小数据传输过程，支持有效传输小数据所必需的安全过程，支持基于分组交换(Packet Switched，PS)域的短消息传输，支持寻呼优化以实现覆盖增强，支持漫游场景的S8接口等。图2所示网络架构中还包括：CIoT UE，支持CIoT 技术的终端；CIoT BS，支持CIoT技术的基站(Base Station，BS)；LTE eMTC UE，支持LTE系统中的演进的机器类通信(evolved Machine Type Communication，eMTC)技术的终端；LTE eMTC eNB，支持LTE系统中的eMTC技术的eNB；归属用户服务器(Home Subscriber Server，HSS)，用于在归属网络中保存IP多媒体子系统(IP Multimedia Subsystem，IMS)用户的签约信息，同时提供管理接口，由运营商及终端用户对签约数据进行定制和修改；应用服务器(Application Server，AS)，用于为终端提供业务应用。其中，CIoT UE和CIoT BS之间通过CIoT-Uu接口相互通信，LTE eMTC UE与LTC eMTC eNB之间通过LTE-Uu(eMTC)接口相互通信。需要说明的是，图2所示的网络架构中，PGW与C-SGN合设为单个C-SGN，在实际应用中，PGW与C-SGN也可以分开部署，二者之间通过S5接口进行通信。
图3为本发明实施例提供的一种漫游场景的CIoT的网络架构的示意图。如图3所示，C-SGN通过S8接口与PGW相互通信，而PGW通过SGi接口与AS相互通信。其他内容与图2所示的网络架构相似，可以参考图2中详细描述，在此不再赘述。
本发明实施例的技术方案可以应用于移动发起(Mobile Originated，MO)的数据传输过程，也可以应用于移动终止(Mobile Terminated，MT)的数据传输过程。其中，终端与核心网络之间可以通过非接入层(Non-Access Stratum，NAS)消息进行数据传输，从而终端与核心网之间不需要建立数据面路径，减少了开销。
然而，对于小数据传输而言，通过NAS消息传输包含小数据的数据包时，该数据包的IP头的大小相比小数据的大小较大。传输一次该数据包所带来的信令开销远远超过所传输的小数据，因此传输效率比较低。对此，本发明实施例的方案会在后续介绍中提出改善这种情况的途径。
下面将基于上面所述的本发明涉及的共性方面，对本发明实施例进一步详细说明。
本发明的一个实施例提供一种数据传输的方法，和基于这个方法的终端，核心网设备和系统。所述终端和核心网设备进行数据传输参数和标识的协商过程，例如，核心网设备获取数据传输参数，为数据传输参数分配标识，并将数据传输参数和标识发送给终端。通过上述协商过程，本发明实施例的方案可以避免在传输数据前因建立承载造成开销浪费。进一步的终端和核心网设备可以在数据包的传输过程中，根据数据传输参数和标识对相应的数据包进行处理，以使得数据包在终端与核心网之间进行传输时不携带IP头，因此能够减少数据包的头开销，提高数据传输的效率。
本发明实施例中，在图1所示的网络架构中，核心网设备可以是MME 或PGW；在图2所示的网络架构中，核心网设备可以是C-SGN；在图3所示的网络架构中，核心网设备可以是C-SGN或PGW。
下面结合附图4，对本发明实施例提供的方案进行说明。
在401部分，核心网设备获取数据传输参数，数据传输参数包含IP头包含的信息中的部分或全部，其中IP头可以包括数据报协议(User Datagram Protocol，UDP)头。核心网设备可以根据终端的指示获取数据传输参数。例如，在核心网设备获取数据传输参数之前，终端可以向核心网设备发送数据传输指示，数据传输指示用于指示包含数据传输参数的数据包或者与该数据包相关的服务器信息或业务信息；对应的，核心网设备接收终端发送的数据传输指示，并根据数据传输指示获取数据传输参数。
在一个示例中，核心网设备获取本地配置的数据传输参数。在核心网设备获取数据传输参数之前，数据传输参数静态配置在核心网设备中，数据传输参数可以包括服务器地址和端口信息等，例如包括服务器IP地址、协议类型和目的端口。核心网设备通过静态配置的方式获取数据传输参数，对现有的信令改动较小，实现方式简单，具有较好的兼容性。
在另一个示例中，核心网设备获取终端的上下文信息，该上下文信息中包含数据传输参数。该数据传输参数可以包括服务器IP地址、协议类型和目的端口。例如，核心网设备从终端之前附着的核心网设备获取终端的上下文信息，这种方式对现有的信令改动较小，实现方式简单，且不需要对核心网设备的本地配置进行改变。
在又一个示例中，核心网设备获取终端的签约数据，签约数据中包含数据传输参数。该数据传输参数可以包括服务器IP地址、协议类型和目的端口。例如，核心网设备可以从HSS获取终端的签约数据，这种方式对现有的信令改动较小，实现方式简单，且不需要对核心网设备的本地配置进行改变。进一步地，若终端是初次接入网络或者核心网设备无法从之前附着的核心网设备获取终端的上下文信息，核心网设备可以通过获取终端的签约数据确保获取数据传输参数。
在又一个示例中，核心网设备接收终端发送的数据传输参数。数据传输参数可以包括终端的IP地址和端口、协议类型以及服务器的IP地址和端口。例如，核心网设备可以接收终端发送的控制信令或上行数据包，该控制信令或上行数据包中包含数据传输参数。因此，当终端支持向基站发送数据传输参数时，核心网设备可以更为灵活地获取数据传输参数，且所获取的数据传输参数的内容更加全面。
在又一个示例中，核心网设备接收策略与计费规则功能(Policy and Charging Rules Function，简称PCRF)实体发送的数据传输参数。数据传输 参数可以包括服务器IP地址、协议类型和目的端口。例如，核心网设备可以接收PCRF实体在会话建立过程中发送的数据传输参数。因此，当所应用的网络架构中部署有PCRF实体时，核心网设备可以更为灵活地获取数据传输参数，且数据传输参数的内容具有较好的扩展性。
在又一个示例中，核心网设备接收服务器发送的数据传输参数，其中，服务器可以是M2M业务平台或应用服务器(Application Server，AS)。数据传输参数可以包括服务器IP地址、协议类型和目的端口。例如，当核心网设备与服务器之间通过开放业务接口进行交互时，核心网设备可以接收服务器通过开放业务接口发送的数据传输参数；又例如，核心网设备可以接收服务器发送的下行数据包，下行数据包中包含数据传输参数。因此，核心网设备可以更为灵活地获取数据传输参数，且数据传输参数的内容具有较好的扩展性。
在402部分，核心网设备为数据传输参数分配标识，标识用于标识该数据传输参数。对于不同的数据传输参数，核心网设备分配不同的标识，即数据传输参数与标识之间具有唯一对应关系。
在403部分，核心网设备向终端发送数据传输参数和标识。
在404部分，终端接收核心网设备发送的数据传输参数和标识。
上述401～404部分所述的方法为协商过程，协商过程是终端和核心网设备对数据传输参数和标识进行协商的过程。其中，终端和核心网设备可以在终端发起的附着过程或跟踪区更新(Tracking Area Update，TAU)过程中完成协商过程。在执行完该协商过程后，还可以执行下面的传输过程，传输过程是终端和核心网设备基于数据传输参数和标识对数据包进行传输的过程。或者，本发明实施例的方法也可以仅包括传输过程。也就是说，在本发明实施例的具体实现中，可以仅执行协商过程或传输过程，也可以执行协商过程和传输过程。下面分别从核心网设备和终端对上述传输过程进行说明。
在传输过程中，核心网设备可以执行如下述示例之一，当然，核心网设备的操作也可以通过其他方式实现：
在一个示例中，核心网设备接收第一数据包，第一数据包中包含标识，例如，核心网设备可以在向终端发送数据传输参数和标识之后接收终端发送的第一数据包。然后核心网设备根据标识确定数据传输参数；或者核心网设备根据标识与数据传输参数的对应关系确定标识所标识的数据传输参数，该数据传输参数包含IP头包含的信息中的部分或全部。然后核心网设备对第一数据包进行处理，例如，核心网设备根据数据传输参数在第一数据包中添加IP头并去除标识，以生成第二数据包或将第一数据包转换成第二数据包；又例如，核心网设备在第一数据包中添加数据传输参数对应的IP头并去除标识， 以生成第二数据包或将第一数据包转换为第二数据包；又例如，核心网设备根据第一数据包生成第二数据包或将第一数据包转换为第二数据包，其中，第二数据包包含IP头且不包含标识。进一步的，核心网设备还可以向M2M业务平台或AS发送第二数据包。在这个示例中，一方面，终端与核心网设备之间传输的第一数据包不携带IP头，即终端与核心网设备之间传输的是非IP数据包，从而能够减少第一数据包的头开销，提高数据传输的效率；另一方面，核心网设备接收到携带标识的第一数据包后，能够根据数据传输标识恢复IP头，生成第二数据包或者将第一数据包转换为第二数据包，即生成IP数据包或将非IP数据包转换为IP数据包，从而适于在核心网设备与M2M业务平台或AS之间传输。
在另一个示例中，核心网设备向终端发送数据传输参数和数据传输标识之后，还接收M2M业务平台或AS发送的第三数据包，第三数据包携带数据传输参数，该数据传输参数包含IP头包含的信息中的部分或全部。然后核心网设备根据数据传输参数确定标识。然后，核心网设备对第三数据包进行处理，例如，核心网设备去除第三数据包的IP头并在第三数据包中添加标识，以生成第四数据包或将第三数据包转换为第四数据包；又例如，核心网设备根据第三数据包生成第四数据包或将第三数据包转换为第四数据包，其中，第四数据包包含标识且不包含IP头。进一步的，核心网设备还可以向终端发送第四数据包。在这个示例中，核心网设备在接收到第三数据包后，能够去除IP头，生成第四数据包或将第三数据包转换为第四数据包，即生成非IP数据包或将IP数据包转换为非IP数据包，以向终端发送该非IP数据包，因此能够减少核心网设备与终端之间数据传输的开销，提高传输的效率。
在又一个示例中，核心网设备可以根据第三数据包中包含的IP头和对应关系确定标识，其中，该对应关系为标识和数据传输参数的对应关系，该数据传输参数包含IP头包含的信息中的部分或全部；然后核心网设备对第三数据包进行处理，处理的具体实现方式可以参见上面一个示例中核心网设备对第三数据包的各种处理方式，此处不作赘述。进一步的，核心网设备可以向终端发送第四数据包。与上面一个示例类似，核心网设备通过本示例中的方式也达到类似的效果，从而提高传输的效率。
在传输过程中，终端可以执行如下述示例之一，当然，终端的操作也可以通过其他方式实现：
在一个示例中，终端接收第五数据包，第五数据包包含标识，例如，终端接收核心网设备发送的第五数据包；然后，终端根据标识确定数据传输参数，或者终端也可以根据标识与数据传输参数的对应关系确定标识所标识的数据传输参数，该数据传输参数包含IP头包含的信息中的部分或全部。然后 终端对第五数据包进行处理，例如，终端根据数据传输参数在第五数据包中添加IP头并去除标识，以生成第六数据包或将第五数据包转换成第六数据包；又例如，终端在第五数据包中添加数据传输参数对应的IP头并去除标识，以生成第六数据包或将第五数据包转换为第六数据包；又例如，终端根据第五数据包生成第六数据包或将第五数据包转换为第六数据包，其中，第六数据包包含IP头且不包含标识。进一步的，终端可以对第六数据包进行高层处理。在这个示例中，终端在接收第五数据包，即接收头开销较小的非IP数据包后，能够根据数据传输参数恢复IP头，生成第六数据包或将第五数据包转换为第六数据包，即生成IP数据包或将非IP数据包转换为IP数据包，从而适于终端进行高层处理。
在另一个示例中，终端可以根据第七数据包包含的数据传输参数确定标识，或者，终端可以根据第七数据包中包含的IP头和对应关系确定标识，其中，第七数据包可以为终端待发送的数据包，对应关系为标识与数据传输参数的对应关系，数据传输参数包含IP头包含的信息中的部分或全部。然后终端对第七数据包进行处理，例如，终端去除第七数据包的IP头并在第七数据包中添加标识，以生成第八数据包或将第七数据包转换为第八数据包；又例如，终端根据第七数据包生成第八数据包或将第七数据包转换为第八数据包，其中，第八数据包包含标识且不包含IP头。进一步的，终端还可以向核心网设备发送第八数据包。在这个示例中，终端能够去除第七数据包的IP头，即去除IP数据包的IP头，生成第八数据包或将第七数据包转换为第八数据包，即生成非IP数据包或将IP数据包转换为非IP数据包，从而使得终端与核心网设备之间所传输的是非IP数据包，即能够减少所传输数据包的头开销，提高终端与核心网设备之间数据传输的效率。
下面将结合更多的附图，基于图1所示的网络架构，以终端为UE，核心网设备为MME或PGW为例，对本发明的实施例做进一步说明。
图5a～图10b将示出数据传输参数和标识的协商过程的各种实现方式。
图5a和图5b为本发明实施例提供的一种协商数据传输参数和标识的方法的通信示意图。在图5a和图5b所示的方法中，核心网设备通过静态配置的方式获取数据传输参数。图5a所示的方法中，核心网设备为MME；图5b所示的方法中，核心网设备为PGW。下面以图5a为例进行说明。
在501部分，UE向MME发送附着请求(attach request)消息，附着请求消息中携带数据传输指示，数据传输指示用于指示包含数据传输参数的数据包或者与该数据包相关的服务器信息或业务信息。
在502部分，MME接收UE发送的附着请求后，根据数据传输指示获取与数据包对应的本地配置的数据传输参数。本地配置的数据传输参数可以包 括服务器IP地址、协议类型和目的端口。
在503部分，MME向PGW发送创建会话请求(create session request)消息，创建会话请求消息中携带数据传输参数。
在504部分，PGW接收MME发送的创建会话请求消息后，保存数据传输参数。从而当PGW接收到下行数据包时，可以根据数据传输参数识别该下行数据包是否为上述数据包，以便将该数据包发送给MME。
在505部分，PGW向MME发送创建会话响应(create session response)消息。
在506部分，MME接收PGW发送的创建会话响应消息后，为该数据传输参数分配标识，标识用于标识该数据传输参数。
在507部分，MME向UE发送附着接受(attach accept)消息，附着接受消息中携带数据传输参数和标识。对应的，UE接收MME发送的附着接受消息，从而能够在后续的传输过程中基于数据传输参数和标识对上述数据包进行传输。
图5b所示的方法与图5a所示的方法相似，区别在于，图5b所示的方法中，核心网设备为PGW，PGW根据数据传输指示获取本地配置的数据传输参数，并为该数据传输参数分配标识，然后将数据传输参数和标识发送给UE。其它内容可以参见图5a中的详细描述，在此不再赘述。
图6a和图6b为本发明实施例提供的另一种协商数据传输参数和标识的方法的通信示意图。在图6a和图6b所示的方法中，核心网设备通过从UE之前附着的核心网设备请求UE的上下文信息来获取数据传输参数，其中，UE之前附着的核心网设备为源MME或源SGSN。图6a所示的方法中，核心网设备为目标MME；图6b所示的方法中，核心网设备为PGW。下面以图6a为例进行说明。
601部分以及604～608部分分别与图5a所示方法中的501部分以及503～507部分相似，其中，图5a所述方法中的MME的功能由图6a所示方法中的目标MME实现，其它内容不作赘述。
在602部分，目标MME接收UE发送的附着请求后，根据数据传输指示向源MME或源SGSN发送上下文请求(context request)消息，以请求UE的上下文信息。
在603部分，源MME或源SGSN接收目标MME发送的上下文请求消息后，向目标MME发送包含UE的上下文信息的上下文响应(context response)消息，其中，UE的上下文信息中携带数据传输参数。对应的，目标MME接收源MME或源SGSN发送的上下文响应消息。
图6b所示的方法与图6a所示的方法相似，区别在于，图6b所示的方法 中，核心网设备为PGW，PGW接收目标MME发送的数据传输参数，并为该数据传输参数分配标识，然后将数据传输参数和标识发送给目标MME后，目标MME再将数据传输参数和标识发送给UE。可以理解的是，由于目标在630部分中已获得数据传输参数，PGW也可以只向目标MME发送标识。其中，PGW将数据传输参数和标识一起发送给目标MME，能够简化目标MME的操作，降低目标MME将数据传输参数和标识匹配错误的风险。其它内容可以参见图6a中的详细描述，在此不再赘述。
图7a和图7b为本发明实施例提供的又一种协商数据传输参数和标识的方法的通信示意图。在图7a和图7b所示的方法中，核心网设备通过从HSS获取UE的签约数据来获取数据传输参数。图7a所示的方法中，核心网设备为MME；图7b所示的方法中，核心网设备为PGW。下面以图7a为例进行说明。
701部分以及703～707部分分别与图5a所示方法中的501部分以及503～507部分相似，此处不作赘述。
在702部分，MME与HSS之间进行签约数据的获取过程，MME从HSS中获取到UE的签约数据，UE的签约数据中携带数据传输参数。
图7b所示的方法与图7a所示的方法相似，区别在于，图7b所示的方法中，核心网设备为PGW，PGW接收MME发送的数据传输参数，并为该数据传输参数分配标识，然后将数据传输参数和标识发送给MME，或者仅将标识发送给MME，然后MME将数据传输参数和标识发送给UE。其它内容可以参见图7a中的详细描述，在此不再赘述。
图8a和图8b为本发明实施例提供的又一种协商数据传输参数和标识的方法的通信示意图。在图8a和图8b所示的方法中，核心网设备接收终端发送的数据传输参数。图8a所示的方法中，核心网设备为MME；图8b所示的方法中，核心网设备为PGW。下面以图8a为例进行说明。
804～807部分分别与图5a所示方法中的503～507部分相似，此处不作赘述。
在801部分，UE与MME之间进行附着过程，UE附着到EPS系统。
在802部分，UE通过应用层消息注册到M2M业务平台或AS，从M2M业务平台或AS获取数据传输参数。
在803部分，UE向MME发送TAU请求消息，TAU请求消息中携带数据传输参数。对应的，MME接收UE发送的TAU请求消息。
在808部分，MME向UE发送TAU接受消息，TAU接收消息中携带数据传输参数和标识。对应的，UE接收MME发送的TAU接受消息，从而能够在后续的传输过程中基于数据传输参数和标识对数据包进行传输。
图8b所示的方法与图8a所示的方法相似，区别在于，图8b所示的方法中，核心网设备为PGW，PGW接收MME发送的数据传输参数，并为该数据传输参数分配标识，然后将数据传输参数和标识发送给MME，或者仅将标识发送给MME，然后MME将数据传输参数和标识发送给UE。其它内容可以参见图8a中的详细描述，在此不再赘述。
图9a和图9b为本发明实施例提供的又一种协商数据传输参数和标识的方法的通信示意图。在图9a和图9b所示的方法中，核心网设备接收PCRF实体在会话建立过程中发送的数据传输参数。图9a所示的方法中，核心网设备为MME；图9b所示的方法中，核心网设备为PGW。下面以图9a为例进行说明。
901部分，906部分和907部分分别与图5a所示方法中的501部分，506部分和507部分相似，此处不作赘述。
在902部分，MME接收UE发送的附着请求消息后，向PGW发送创建会话请求消息，创建会话请求消息中携带数据传输指示。
在903部分，PGW接收MME发送的创建会话请求消息后，向PCRF实体发送网关控制会话建立(gateway control session establishment)消息，用于请求数据传输参数。
在904部分，PCRF实体接收PGW发送的网关控制会话建立消息后，向PGW发送网关控制会话建立确认消息，网关控制会话建立确认消息中携带数据传输参数。
在905部分，PGW接收PCRF实体发送的网关控制会话建立确认消息后，向MME发送创建会话响应消息，创建会话响应消息中携带数据传输参数。对应的，MME接收PGW发送的创建会话响应消息。
图9b所示的方法与图9a所示的方法相似，区别在于，图9b所示的方法中，核心网设备为PGW，PGW接收PCRF实体发送的数据传输参数后，为数据传输参数分配标识，然后将数据传输参数和标识发送给MME，或者仅将标识发送给MME，然后MME将数据传输参数和标识发送给UE。其它内容可以参见图9a中的详细描述，在此不再赘述。
图10a和图10b为本发明实施例提供的又一种协商数据传输参数和标识的方法的通信示意图。在图10a和图10b所示的方法中，核心网设备接收M2M业务平台或AS发送的数据传输参数。图10a所示的方法中，核心网设备为MME；图10b所示的方法中，核心网设备为PGW。下面以图10a为例进行说明。
1001部分以及1004～1008部分分别与图5a所示方法中的501部分以及503～507部分相似，此处不作赘述。
在1002部分，MME接收UE发送的附着请求消息后，根据UE提供的接入点名称(Access Point Name，APN)得到M2M业务平台或AS的地址，然后通过业务能力开放功能(Service Capability Exposure Function，SCEF)实体的业务开放接口向M2M业务平台或AS发送请求消息，用于请求数据传输参数。
在1003部分，M2M业务平台或AS接收MME发送的请求消息后，通过SCEF实体向MME发送响应消息，响应消息中携带数据传输参数。对应的，MME接收M2M业务平台或AS发送的响应消息。
图10b所示的方法与图10a所示的方法相似，区别在于，图10b所示的方法中，核心网设备为PGW，PGW接收MME发送的数据传输参数后，为数据传输参数分配标识，然后将数据传输参数和标识发送给MME，或者仅将标识发送给MME，然后MME将数据传输参数和标识发送给UE。其它内容可以参见图10a中的详细描述，在此不再赘述。
图11～14将示出基于数据传输参数和标识的传输过程的各种实现方式。
图11为本发明实施例提供的一种基于数据传输参数和标识的数据传输的方法的通信示意图。图11所述的方法中，核心网设备为MME。
在1101部分，UE与MME之间进行数据传输参数和标识的协商过程，具体实现方式可以参见图5a～10b所示的方法，此处不再赘述。完成协商过程后，UE与MME都本地保存有数据传输参数和标识。
在1102部分，UE待发送的数据包为IP数据包，该IP数据包的IP头携带数据传输参数，UDP净荷为UE需要发送给M2M业务平台或AS的应用层数据。如果待发送数据包的IP头携带的数据传输参数和UE已保存的数据传输参数相同，则UE判定待发送的数据包中携带的UDP净荷为小数据。
在1103部分，UE去除待发送的IP数据包中的IP头，以生成或转换为小数据包，并在小数据包中携带标识和EPS承载标识，然后将小数据包封装到NAS消息中，其中，EPS承载标识用于MME判断该小数据包应发往的SGW/PGW。
在1104部分，UE与eNB之间进行RRC连接建立过程，UE在RRC连接建立过程中将NAS消息发送给eNB。
在1105部分，eNB接收UE发送的NAS消息后，向MME发送初始UE消息，初始UE消息中携带该NAS消息。
在1106部分，MME接收eNB发送的初始UE消息后，提取NAS消息中的小数据包，去除小数据包中的标识和EPS承载标识，并根据标识确定对应的数据传输参数后，根据数据传输参数为小数据包添加IP头，使得小数据包转换为IP数据包，然后将IP数据包封装为GPRS隧道协议(GPRS Tunneling  Protocol，GTP)数据包。
在1107部分，MME根据EPS承载标识获取SGW的IP地址，向SGW发送GTP数据包。
在1108部分，SGW接收MME发送的GTP数据包后，向PGW发送GTP数据包。
在1109部分，PGW接收SGW发送的GTP数据包后，将GTP数据包解封装为IP数据包。
在1110部分，PGW向M2M业务平台或AS发送IP数据包，对应的，M2M业务平台或AS接收PGW发送的IP数据包。
需要说明的是，1101部分是可选的，例如，当UE与MME之前已协商过数据传输参数和标识，或者UE与MME通过其他方法都已保存过数据传输参数和标识时，可从1102部分开始执行图11所示的方法。
图12为本发明实施例提供的另一种基于数据传输参数和标识的数据传输的方法的通信示意图。图12所述的方法中，核心网设备为PGW。
1201～1205部分分别与图11所示方法中的1101～1105部分相似，其中，在1201部分，UE和PGW完成协商过程后，UE和PGW都本地保存有数据传输参数和标识，其他内容不作赘述。
在1206部分，MME接收eNB发送的初始UE消息后，提取NAS消息中的小数据包，并将小数据包封装为GTP数据包，其中，小数据包中携带UDP净荷、标识和EPS承载标识。
在1207部分，MME根据EPS承载标识获取SGW的IP地址，向SGW发送GTP数据包。
在1208部分，SGW接收MME发送的GTP数据包后，向PGW发送GTP数据包。
在1209部分，PGW接收SGW发送的GTP数据包后，将GTP数据包解封装为小数据包，去除小数据包中的标识和EPS承载标识，并根据标识确定对应的数据传输参数后，根据数据传输参数为小数据包添加IP头，将小数据包转换为IP数据包。
在1210部分，PGW向M2M业务平台或AS发送IP数据包。
需要说明的是，1201部分与上述1101部分类似，也是可选的。
图13为本发明实施例提供的又一种基于数据传输参数和标识的数据传输的方法的通信示意图。图13所述的方法中，核心网设备为MME。
在1301部分，UE与MME之间进行数据传输参数和标识的协商过程，具体实现方式可以参见图5a～10b所示的方法，此处不再赘述。完成协商过程后，UE与MME都本地保存有数据传输参数和标识。
在1302部分，M2M业务平台或AS向PGW发送IP数据包，IP数据包的IP头携带数据传输参数。
在1303部分，PGW接收M2M业务平台或AS发送的IP数据包后，根据数据传输参数判定IP数据包传输的为小数据。
在1304部分，PGW将IP数据包封装为GTP数据包，并在GTP数据包中携带小数据指示，小数据指示用于指示GTP数据包中携带的IP数据包的传输为小数据传输。
在1305部分，PGW向SGW发送GTP数据包。
在1306部分，SGW接收PGW发送的GTP数据包后，根据小数据指示判定为IP数据包的传输为小数据传输。
在1307部分，SGW通过下行数据通知(Downlink Data Notification，DDN)消息向MME发送GTP数据包。
在1308部分，由于UE和MME之间没有信令连接，MME向eNB发送寻呼消息，寻呼消息中携带小数据指示。
在1309部分，eNB接收MME发送的寻呼消息后，向UE发送寻呼消息，寻呼消息中携带小数据指示。
在1310部分，UE接收eNB发送的寻呼消息后，向MME发送业务请求。
在1311部分，MME接收UE发送的业务请求后，向SGW发送DDN确认消息。
在1312部分，MME将GTP数据包解封装为IP数据包，去除IP数据包的IP头，并根据数据传输参数在IP数据包中携带对应的标识和EPS承载标识，从而将IP数据包转换为小数据包，并将小数据包封装在NAS消息中。
在1313部分，MME向eNB发送NAS消息。
在1314部分，eNB接收MME发送的NAS消息后，向UE发送NAS消息。
在1315部分，UE从NAS消息中提取小数据包，去除标识和EPS承载标识，根据标识确定对应的数据传输参数，并根据数据传输参数在小数据包中添加IP头，从而将小数据包转换为IP数据包并提交给高层应用协议。
需要说明的是，1301部分与上述1101部分类似，也是可选的。
图14为本发明实施例提供的又一种基于数据传输参数和标识的数据传输的方法的通信示意图。图14所述的方法中，核心网设备为PGW。
1401～1403部分和1413～1415部分分别与图13所示方法中的1301～1303部分和1313～1315部分相似，其中，在1401部分，UE和PGW完成协商过程后，UE和PGW都本地保存有数据传输参数和标识，其他内容不作赘述。
在1404部分，PGW去除IP数据包的IP头，根据数据传输参数在IP数 据包中携带对应的标识，从而将IP数据包转换为小数据包，然后将小数据包封装成GTP数据包，并在GTP数据包中携带小数据指示，小数据指示用于指示GTP数据包中携带的数据包的传输为小数据传输。
在1405部分，PGW向SGW发送GTP数据包。
在1406部分，SGW接收PGW发送的GTP数据包后，根据小数据指示判定为IP数据包的传输为小数据传输。
在1407部分，SGW向MME发送下行数据通知(Downlink Data Notification，DDN)消息，DDN消息中携带GTP数据包。
在1408部分，由于UE和MME之间没有信令连接，MME向eNB发送寻呼消息，寻呼消息中携带小数据指示。
在1409部分，eNB接收MME发送的寻呼消息后，向UE发送寻呼消息，寻呼消息中携带小数据指示。
在1410部分，UE接收eNB发送的寻呼消息后，向MME发送业务请求。
在1411部分，MME接收UE发送的业务请求后，向SGW发送DDN确认消息。
在1412部分，MME将GTP数据包解封装为小数据包，并在小数据包中携带EPS承载标识，然后将小数据包封装在NAS消息中。
需要说明的是，1401部分与上述1101部分类似，也是可选的。
当应用图1所示的网络架构时，实现上述部分方法的核心网设备也可以为SGSN，例如，上述图5a、6a、7a、8a、9a、10a、11和13所示方法中MME或目标MME的功能可以由SGSN完成。
应当理解的是，图5a至图14所示的方法也可以在图2和图3所示的网络架构中实施。当图5a至图14所示的方法应用于图2所示的网络架构时，图5a、6a、7a、8a、9a、10a、11和13所示方法中MME或目标MME的功能由图2中的C-SGN实现，图5b、6b、7b、8b、9b、10b、12和14所示方法中PGW的功能由图2中的C-SGN实现。当图5a至图14所示的方法应用于图3所示的网络架构时，图5a、6a、7a、8a、9a、10a、11和13所示方法中MME或目标MME的功能由图3中的C-SGN实现，图5b、6b、7b、8b、9b、10b、12和14所示方法中PGW的功能由图3中的PGW实现。
可以理解的是，本发明实施例所涉及到的终端可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备、或连接到无线解调器的其他处理设备，以及各种形式的UE，移动台(Mobile Station，MS)，M2M设备(M2M device)，终端设备(Terminal Device，TE)等。为方便描述，本发明实施例中，上面提到的设备统称为终端。
上述主要从各个网元之间交互的角度对本发明实施例提供的方案进行了 介绍。可以理解的是，各个网元，例如终端，核心网设备等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本发明中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。本领域技术人员可以对每个特定的应用来使用不同的方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
图15示出了上述实施例中所涉及的核心网设备的一种可能的结构示意图。核心网设备可以是图2所示的网络架构中的MME或PGW，也可以是图2所示的网络架构中的C-SGN，还可以是图3所示的网络架构中的C-SGN或PGW。
核心网设备包括存储器1501、控制器/处理器1502和网络接口1503。控制器/处理器1502用于对核心网设备的动作进行控制管理。例如，控制器/处理器1502用于支持核心网设备执行图4中的过程401～403，图5a中的过程502、503、506和507，图5b中的过程530、540和550，图6a中的过程602、604、607和608，图6b中的过程650和660，图7a中的过程702、703、706和707，图7b中的过程740和750，图8a中的过程801、802、804、807和808，图8b中的过程810、820、850和860，图9a中的过程902、906和907，图9b中的过程930、950和960，图10a中的过程1002、1004、1007和1008，图10b中的过程1050和1060，图11中的过程1101、1106和1107，图12中的过程1201、1209和1210，图13中的过程1301、1308、1311、1312和1313，图14中的过程1401、1403、1404和1405。存储器1501用于存储用于核心网设备的程序代码和数据。网络接口1503用于支持核心网设备与其他网络实体的通信，例如与图16所示的终端的通信，又例如与图1、图2或图3中示出的各个网络实体之间的通信。
图16示出了上述实施例中所涉及的终端的一种可能的结构示意图。如图16所示，终端包括发射器1601，接收器1602，控制器/处理器1603，存储器1604和调制解调处理器1605。
发射器1601调节(例如，模拟转换、滤波、放大和上变频等)输出采样并生成上行链路信号，该上行链路信号经由天线发射给上述实施例中的eNB，从而发送给核心网设备。在下行链路上，天线接收上述实施例中核心网设备通过eNB发送的下行链路信号。接收器1602调节(例如，滤波、放大、下变频以及数字化等)从天线接收的信号并提供输入采样。在调制解调处理器1605中，编码器1606接收要在上行链路上发送的业务数据和信令消息，并对业务数据和信令消息进行处理(例如，格式化、编码和交织)。调制器1607进一步 处理(例如，符号映射和调制)编码后的业务数据和信令消息并提供输出采样。解调器1609处理(例如，解调)该输入采样并提供符号估计。解码器1608处理(例如，解交织和解码)该符号估计并提供发送给UE的已解码的数据和信令消息。编码器1606、调制器1607、解码器1608和解调器1609可以由合成的调制解调处理器1605来实现。这些单元根据无线接入网采用的无线接入技术(例如，LTE系统，CIoT系统及其他演进系统的接入技术)来进行处理。
控制器/处理器1603对终端的动作进行控制管理，用于执行上述实施例中由终端进行的处理。例如用于控制终端根据数据传输参数和标识对数据包处理和/或本发明所描述的方案的其他过程。作为示例，控制器/处理器1103用于支持终端执行图4中的过程404，图5a中的过程501，图5b中的过程510，图6a中的过程601，图6b中的过程610，图7a中的过程701，图7b中的过程710，图8a中的过程801～803，图8b中的过程810～830，图9a中的过程901，图9b中的过程910，图10a中的过程1001，图10b中的过程1010，图11中的过程1101～1104，图12中的过程1201～1204，图13中的过程1301、1310和1315，以及图14中的过程1401、1410和1415。存储器1604用于存储用于终端的程序代码和数据。
用于执行本发明上述核心网设备或终端的功能的控制器/处理器可以是中央处理器(Central Processing Unit，CPU)，通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application-Specific Integrated Circuit，ASIC)，现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。
结合本发明公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read Only Memory，ROM)、可擦除可编程只读存储器(Erasable Programmable ROM，EPROM)、电可擦可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于终端中。当然，处理器和存储介质也可以作为分立组件存在于终端中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本发明的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明的具体实施方式而已，并不用于限定本发明的保护范围，凡在本发明的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明的保护范围之内。

Claims (23)

  1. 一种数据传输的方法，其特征在于，包括：
    核心网设备获取数据传输参数，所述数据传输参数包含互联网协议IP头包含的信息中的部分或全部；
    所述核心网设备为所述数据传输参数分配标识，所述标识用于标识所述数据传输参数；以及
    所述核心网设备向终端发送所述数据传输参数和所述标识。
  2. 根据权利要求1所述的方法，其特征在于，所述核心网设备获取所述数据传输参数，包括如下情形之一：
    所述核心网设备获取本地配置的所述数据传输参数；
    所述核心网设备获取所述终端的上下文信息，所述上下文信息中包含所述数据传输参数；
    所述核心网设备获取所述终端的签约数据，所述签约数据中包含所述数据传输参数；
    所述核心网设备接收所述终端发送的所述数据传输参数；
    所述核心网设备接收策略与计费规则功能PCRF实体发送的所述数据传输参数；
    所述核心网设备接收机器对机器M2M业务平台或应用服务器AS发送的所述数据传输参数。
  3. 根据权利要求1或2所述的方法，其特征在于，所述核心网设备向终端发送所述数据传输参数和所述标识之后，所述方法还包括：
    所述核心网设备接收所述终端发送的第一数据包，所述第一数据包携带所述标识；
    所述核心网设备根据所述标识确定所述数据传输参数；
    所述核心网设备根据所述数据传输参数在所述第一数据包中添加IP头并去除所述标识，以生成第二数据包；
    所述核心网设备向M2M业务平台或AS发送所述第二数据包。
  4. 根据权利要求1所述的方法，其特征在于，所述核心网设备向终端发送所述数据传输参数和所述标识之后，所述方法还包括：
    所述核心网设备接收M2M业务平台或AS发送的第三数据包，所述第三数据包携带所述数据传输参数；
    所述核心网设备根据所述数据传输参数确定所述标识；
    所述核心网设备去除所述第三数据包的IP头并在所述第三数据包中携带所述标识，以生成第四数据包；
    所述核心网设备向所述终端发送所述第四数据包。
  5. 根据权利要求1或2所述的方法，其特征在于，所述核心网设备获取所述数据传输参数之前，所述方法还包括：
    所述核心网设备接收所述终端发送的数据传输指示，所述数据传输指示用于指示包含所述数据传输参数的数据包或者与所述数据包相关的服务器信息或业务信息；
    所述核心网设备获取所述数据传输参数，包括：
    所述核心网设备根据所述数据传输指示获取所述数据传输参数。
  6. 一种数据传输的方法，其特征在于，包括：
    根据第一数据包中包含的标识与数据传输参数的对应关系，确定所述标识所标识的所述数据传输参数，所述数据传输参数包含互联网协议IP头包含的信息中的部分或全部；以及
    根据所述数据传输参数在所述第一数据包中添加所述IP头并去除所述标识，以生成第二数据包。
  7. 根据权利要求6所述的方法，其特征在于，还包括：
    根据第三数据包中包含的IP头和对应关系确定标识，其中，所述对应关系为所述标识和数据传输参数的对应关系，所述数据传输参数包含IP头包含的信息中的部分或全部；以及
    去除所述第三数据包的IP头并在所述第三数据包中携带所述标识，以生成第四数据包。
  8. 根据权利要求6或7所述的方法，其特征在于，还包括：
    对所述第二数据包进行高层处理；或者，
    向机器对机器M2M业务平台或应用服务器AS发送所述第二数据包。
  9. 根据权利要求7所述的方法，其特征在于，还包括：
    向终端发送所述第四数据包；或者
    向核心网设备发送所述第四数据包。
  10. 一种核心网设备，其特征在于，包括：处理器和网络接口，
    所述处理器用于获取数据传输参数，所述数据传输参数包含互联网协议IP头包含的信息中的部分或全部；以及用于为所述数据传输参数分配标识，所述标识用于标识所述数据传输参数；还用于通过所述网络接口向终端发送所述数据传输参数和所述标识。
  11. 根据权利要求10所述的核心网设备，其特征在于，
    所述处理器具体用于获取本地配置的所述数据传输参数；或者
    所述处理器具体用于通过所述网络接口获取所述终端的上下文信息，所述上下文信息中包含所述数据传输参数；或者
    所述处理器具体用于通过所述网络接口获取所述终端的签约数据，所 述签约数据中包含所述数据传输参数；或者
    所述处理器具体用于通过所述网络接口接收所述终端发送的所述数据传输参数；或者
    所述处理器具体用于通过所述网络接口接收策略与计费规则功能PCRF实体发送的所述数据传输参数；或者
    所述处理器具体用于通过所述网络接口接收机器对机器M2M业务平台或应用服务器AS发送的所述数据传输参数。
  12. 根据权利要求10或11所述的核心网设备，其特征在于，所述处理器还用于在通过所述网络接口向所述终端发送所述数据传输参数和所述标识之后，通过所述网络接口接收所述终端发送的第一数据包，所述第一数据包携带所述标识；以及用于根据所述标识确定所述数据传输参数；以及用于根据所述数据传输参数在所述第一数据包中添加IP头，以生成第二数据包；以及用于通过所述网络接口向M2M业务平台或AS发送所述第二数据包。
  13. 根据权利要求10所述的核心网设备，其特征在于，所述处理器还用于在通过所述网络接口向所述终端发送所述数据传输参数和所述标识之后，通过所述网络接口接收M2M业务平台或AS发送的第三数据包，所述第三数据包携带所述数据传输参数；以及用于根据所述数据传输参数确定所述标识；以及去除所述第三数据包的所述IP头并在所述第三数据包中携带所述标识，以生成第四数据包；以及用于通过所述网络接口向所述终端发送所述第四数据包。
  14. 根据权利要求10或11所述的核心网设备，其特征在于，所述处理器还用于在获取所述数据传输参数之前，通过所述网络接口接收所述终端发送的数据传输指示，所述数据传输指示用于指示包含所述数据传输参数的数据包或者与所述数据包相关的服务器信息或业务信息；以及具体用于根据所述数据传输指示获取所述数据传输参数。
  15. 一种核心网设备，其特征在于，包括：
    处理器，用于根据第一数据包包含的标识与数据传输参数的对应关系，确定所述标识所标识的所述数据传输参数，所述数据传输参数包含互联网协议IP头包含的信息中的部分或全部；以及用于根据所述数据传输参数在所述第一数据包中添加所述IP头，以生成第二数据包。
  16. 根据权利要求15所述的核心网设备，其特征在于，所述处理器还用于根据第三数据包中包含的IP头和对应关系确定标识，其中，所述对应关系为所述标识和数据传输参数的对应关系，所述数据传输参数包含IP头包含的信息中的部分或全部；以及用于去除所述第三数据包的所述IP 头并所述第三数据包中添加所述标识，以生成第四数据包。
  17. 根据权利要求15或16所述的核心网设备，其特征在于，还包括网络接口，所述处理器还用于通过所述网络接口向机器对机器M2M业务平台或应用服务器AS发送所述第二数据包。
  18. 根据权利要求15所述的核心网设备，其特征在于，还包括网络接口，所述处理器还用于通过所述网络接口向终端发送所述第四数据包。
  19. 一种终端，特征在于，包括：
    处理器，用于根据第一数据包包含的标识与数据传输参数的对应关系，确定所述标识所标识的所述数据传输参数，所述数据传输参数包含互联网协议IP头包含的信息中的部分或全部；以及用于根据所述数据传输参数在所述第一数据包中添加所述IP头，以生成第二数据包。
  20. 根据权利要求19所述的终端，其特征在于，所述处理器还用于根据第三数据包中包含的IP头和对应关系确定标识，其中，所述对应关系为所述标识和数据传输参数的对应关系，所述数据传输参数包含IP头包含的信息中的部分或全部；以及用于去除所述第三数据包的所述IP头并所述第三数据包中添加所述标识，以生成第四数据包。
  21. 根据权利要求19或20所述的终端，其特征在于，所述处理器还用于对所述第二数据包进行高层处理。
  22. 根据权利要求20所述的终端，其特征在于，还包括：
    发射器，用于向核心网设备发送所述第四数据包。
  23. 一种通信系统，其特征在于，包括如权利要求10至18中任一项所述的核心网设备和如权利要求19至22中任一项所述的终端。
PCT/CN2015/100311 2015-12-31 2015-12-31 数据传输的方法和装置 WO2017113390A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/100311 WO2017113390A1 (zh) 2015-12-31 2015-12-31 数据传输的方法和装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/100311 WO2017113390A1 (zh) 2015-12-31 2015-12-31 数据传输的方法和装置

Publications (1)

Publication Number Publication Date
WO2017113390A1 true WO2017113390A1 (zh) 2017-07-06

Family

ID=59224288

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/100311 WO2017113390A1 (zh) 2015-12-31 2015-12-31 数据传输的方法和装置

Country Status (1)

Country Link
WO (1) WO2017113390A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113766569A (zh) * 2021-09-09 2021-12-07 阿里巴巴达摩院(杭州)科技有限公司 数据传输方法、设备、系统及存储介质
WO2023030386A1 (zh) * 2021-09-03 2023-03-09 华为技术有限公司 一种数据传输方法、电子设备和装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102986257A (zh) * 2010-07-13 2013-03-20 高通股份有限公司 用于提供统一的机器到机器寻址的方法和装置
CN103179085A (zh) * 2011-12-20 2013-06-26 华为技术有限公司 网际协议头置换映射关系的获取方法及网络节点

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102986257A (zh) * 2010-07-13 2013-03-20 高通股份有限公司 用于提供统一的机器到机器寻址的方法和装置
CN103179085A (zh) * 2011-12-20 2013-06-26 华为技术有限公司 网际协议头置换映射关系的获取方法及网络节点

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023030386A1 (zh) * 2021-09-03 2023-03-09 华为技术有限公司 一种数据传输方法、电子设备和装置
CN113766569A (zh) * 2021-09-09 2021-12-07 阿里巴巴达摩院(杭州)科技有限公司 数据传输方法、设备、系统及存储介质
CN113766569B (zh) * 2021-09-09 2024-03-15 阿里巴巴达摩院(杭州)科技有限公司 数据传输方法、设备、系统及存储介质

Similar Documents

Publication Publication Date Title
JP6588144B2 (ja) マルチトランスポート機構をサポートするネットワークのためのアプリケーションデータ配信サービス
US9942926B2 (en) System, method and computer readable medium for bearer activation in a core network for wireless devices
KR101576014B1 (ko) 시그널링 라디오 베어러를 통한 짧은 패킷 데이터 메시지들의 전송
EP2768251B1 (en) Data transmission method, mobility management entity and mobile terminal
US10993272B2 (en) Efficient delivery method and apparatuses for infrequent small data
KR101645109B1 (ko) 무선 통신 네트워크 내의 스몰 데이터 기술 및 구성
WO2021000827A1 (zh) 数据传输链路建立方法、装置以及计算机可读存储介质
CN107925914B (zh) 分组数据网络上的非ip数据的通信
US9992109B2 (en) Data transmission method, apparatus and system
WO2017031700A1 (zh) 一种数据包的压缩参数确定方法及相关设备
WO2017113390A1 (zh) 数据传输的方法和装置
US11388588B2 (en) Optimized small data transmission over uplink
WO2019136695A1 (zh) 一种数据传输方法及装置、计算机存储介质
US20200154357A1 (en) Communication method and device
CN111567015B (zh) 一种数据传输方法及装置、计算机存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15912014

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15912014

Country of ref document: EP

Kind code of ref document: A1