WO2017092587A1 - 一种数据传输方法及*** - Google Patents

一种数据传输方法及*** Download PDF

Info

Publication number
WO2017092587A1
WO2017092587A1 PCT/CN2016/106816 CN2016106816W WO2017092587A1 WO 2017092587 A1 WO2017092587 A1 WO 2017092587A1 CN 2016106816 W CN2016106816 W CN 2016106816W WO 2017092587 A1 WO2017092587 A1 WO 2017092587A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
bearer
data
terminal
base station
Prior art date
Application number
PCT/CN2016/106816
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 EP16869897.5A priority Critical patent/EP3364671B1/en
Publication of WO2017092587A1 publication Critical patent/WO2017092587A1/zh
Priority to US15/991,691 priority patent/US10667305B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/54—Store-and-forward switching systems 
    • H04L12/56—Packet switching systems
    • H04L12/5601—Transfer mode dependent, e.g. ATM
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/23—Manipulation of direct-mode connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/54—Store-and-forward switching systems 
    • H04L12/56—Packet switching systems
    • H04L12/5601—Transfer mode dependent, e.g. ATM
    • H04L2012/5638—Services, e.g. multimedia, GOS, QOS
    • H04L2012/5665—Interaction of ATM with other protocols
    • H04L2012/5667—IP over ATM

Definitions

  • the present patent application relates to wireless communication, and more particularly to a data transmission method and system.
  • the next generation mobile communication system will support Machine to Machine (M2M) or Machine Type Communication (MTC). According to forecasts, by 2020, the number of MTC devices connected to the network will reach 500 to 100 billion, which will far exceed the current number of connections.
  • M2M Machine to Machine
  • MTC Machine Type Communication
  • the number of MTC devices is large, and if a large number of MTC devices access the network to compete for network resources, it will bring a new burden to the existing network. There is currently no suitable solution for data transmission of these MTC devices.
  • the present patent application provides a data transmission method and system, which are applicable to an MTC device.
  • the patent application provides a data transmission method.
  • the transmission method one or more first bearers are pre-established between the first network device and the base station, and one or more second bearers are pre-established between the first network device and the second network device.
  • the method includes the following steps: The first network device receives data transmitted by the base station through a first bearer. The data is sent by the terminal to the base station through the air interface resource, and is used for receiving The first bearer of the data corresponds to the first service attribute of the data. The first network device sends data to the second network device through a second bearer, and the second bearer for transmitting data corresponds to the second service attribute of the data.
  • first bearers pre-established between the first network device and the base station there is one pre-established one or more second bearers between the first network device and the second network device, and the data sent by the terminal to the base station It can be sent directly on the first and second bearers. This avoids the signaling process required for the establishment and deletion of bearers and the resulting delay. This effectively improves the efficiency of network business processing.
  • the first bearer corresponds to the service attribute of the data
  • the second bearer corresponds to the second service attribute of the data.
  • the first bearer and the second bearer do not need to correspond to each terminal.
  • the limited application of the present patent application can solve the problem of a large number of terminal data transmission, avoiding the bearer signaling process of a large number of terminals and the resulting delay. This effectively improves the efficiency of network business processing.
  • the first bearer is established when the base station or the first network device is initialized.
  • the second bearer is established when the base station or the first network device is initialized.
  • the first and second bearers are established, and the terminal can directly use the established first bearer and the second bearer when attaching, thereby further improving the network service processing efficiency.
  • the second network device is a server, and the second bearer is established when the server is initialized.
  • the network can support the business capability of OTT (over the top), especially It provides a vertical business capability when the network supports network slicing in the future.
  • the first service attribute is an attribute of the air interface resource, and is used to receive the first bearer and the data of the data.
  • the attributes of the air interface resources used correspond.
  • the data processing process can be simplified by selecting the corresponding first bearer by the attribute of the air interface resource used by the data.
  • the first service attribute is a first quality of service characteristic
  • the first bearer and data for receiving data are received.
  • the first quality of service feature corresponds.
  • the data processing process can be simplified by selecting the corresponding first bearer by the first quality of service characteristic of the data.
  • the second service attribute is a second quality of service feature
  • the method further includes: the first network device passes The second quality of service characteristic of the data determines a second bearer for transmitting data.
  • the data processing process can be simplified by selecting the corresponding second bearer by the second quality of service characteristic of the data.
  • the data received by the first bearer carries the first identifier of the terminal, and the first network device is configured according to the terminal
  • the correspondence between the first identifier and the IP address of the terminal acquires the IP address of the terminal; the first network device carries the IP address of the terminal in the data sent to the second network device.
  • the first identifier enables the base station and the first network device to accurately distinguish each terminal within its management domain. This provides the possibility of not carrying an IP address when performing data transmission on the first bearer and the air interface.
  • the number of bits of the first identifier is less than the number of bits of the IP address. In this way, the terminal can be identified only by the first identifier on the air interface and the first bearer, and the air interface overhead is reduced.
  • the method further includes: the first network device sends a security request to the base station after detecting the suspect terminal by using the data; the first network device Receive the security response sent by the base station.
  • the first network device includes a first network device user plane and a first network device control plane, where the first network device is specifically The first network device user plane.
  • the processing of the data is only operated by the user, which can further simplify the network processing and improve the network processing efficiency.
  • the present application provides a first network device, where one or more first bearers are pre-established between the first network device and the base station; and the first network device and the second network device are pre-established.
  • the first network device includes a first receiver and a first transmitter.
  • the first receiver receives the data sent by the base station by using a first bearer, where the data is sent by the terminal to the base station through the air interface resource, and the first bearer for receiving the data corresponds to the first service attribute of the data.
  • the first transmitter transmits data to the second network device through a second bearer, and the second bearer for transmitting data corresponds to the second service attribute of the data.
  • the first bearer and the second bearer are established when the first network device is initialized.
  • the first service attribute is an attribute of the air interface resource, and is used to receive the first bearer of the data and the data used by the data.
  • the attributes of the air interface resource correspond.
  • the first service attribute is a first quality of service characteristic
  • the first bearer and the data are used to receive data.
  • a service quality characteristic corresponds.
  • the second service attribute is a second quality of service characteristic
  • the first network device further includes the first processor The first processor determines a second bearer for transmitting data by a second quality of service characteristic of the data.
  • the data received by the first bearer carries the first identifier of the terminal; the first processor is further configured according to the terminal The corresponding relationship between the first identifier and the IP address of the terminal acquires the IP address of the terminal, and the data sent by the first sender to the second network device carries the IP address of the terminal.
  • the number of bits of the first identifier is less than the number of bits of the IP address.
  • the first processor is further configured to detect the suspect terminal; the first transmitter is further configured to detect, by the first processor After the suspect terminal sends a security request to the base station, the first receiver is further configured to receive the security response sent by the base station.
  • the patent application provides a data transmission method, where a first network device exists between a base station and a base station.
  • One or more first bearers pre-established.
  • the method includes the following steps: the base station receives the data sent by the terminal from the air interface resource; the base station sends the data to the first network device by using a first bearer, where the first bearer for sending the data is related to the first service attribute of the data. correspond.
  • the first bearer is established when the base station or the first network device is initialized.
  • the first service attribute is an attribute of the air interface resource
  • the method further includes: the attribute of the air interface resource of the data passing by the base station Select the corresponding first bearer.
  • the first service attribute is a first quality of service feature
  • the method further includes: the first service of the base station by using the data The quality characteristic selects the corresponding first carrier.
  • the method further includes: receiving, by the base station, a security request sent by the first network device, where the security request carries the suspect terminal The base station performs security processing on the suspect terminal; the base station sends a security response to the first network device, and the security response carries the identity of the terminal that has performed security processing.
  • the present patent application provides a base station, where one or more first bearers are pre-established between the first network device and the base station.
  • the base station includes a second receiver and a second transmitter.
  • the second receiver receives the data sent by the terminal from the air interface resource; the second transmitter sends the data to the first network device by using a first bearer, and the first bearer for sending the data is related to the first service attribute of the data. correspond.
  • the first bearer is established when the base station or the first network device is initialized.
  • the first service attribute is an attribute of an air interface resource
  • the base station further includes a second processor, configured to pass data The attribute of the air interface resource selects the corresponding first bearer.
  • the first service attribute is a first quality of service feature
  • the base station further includes a second processor, configured to pass The first quality of service characteristic of the data selects the corresponding first bearer.
  • the second receiver further receives a security request sent by the first network device, where the security request carries the identity identifier of the suspect terminal;
  • the second processor performs security processing on the suspect terminal;
  • the second transmitter sends a security response to the first network device, and the security response carries the identity of the terminal that has performed security processing.
  • the present patent application provides a data transmission method, where a pre-established one or more first bearers exist between a first network device and a base station, and a pre-established relationship exists between the first network device and the second network device.
  • One or more second carriers includes the following steps: the first network device receives data transmitted by the second network device through a second bearer. A second bearer for receiving the data corresponds to a second service attribute of the data. The first network device sends data to the base station through a first bearer, and the first bearer for transmitting data corresponds to the first service attribute of the data.
  • the first bearer is established when the base station or the first network device is initialized.
  • the second bearer is established when the base station or the first network device is initialized.
  • the second network device is a server
  • the second bearer is established when the server is initialized.
  • the first service attribute is an attribute of an air interface resource
  • the first network device passes the air interface resource of the data The attribute determines the first bearer used to send the data.
  • the first service attribute is a first quality of service characteristic
  • the first network device passes the first of the data
  • the quality of service feature determines the first bearer used to send the data.
  • the second service attribute is a second quality of service characteristic, configured to receive the first bearer and data of the data The second quality of service feature corresponds.
  • the data received by the second bearer carries an IP address of the terminal
  • the first network device is configured according to the IP address of the terminal.
  • the first identifier of the terminal is obtained by the correspondence between the address and the first identifier of the terminal; the first network device carries the first identifier of the terminal in the data sent to the second network device.
  • the number of bits of the first identifier is less than the number of bits of the IP address.
  • the present application provides a first network device, where one or more first bearers are pre-established between the first network device and the base station, and the first network device and the second network device are pre-established.
  • the first network device includes a first receiver and a first transmitter.
  • the first receiver receives data transmitted by the second network device through a second bearer.
  • a second bearer for receiving the data corresponds to a second service attribute of the data.
  • the first transmitter sends data to the base station through a first bearer, and the first bearer for transmitting data corresponds to the first service attribute of the data.
  • the first bearer and the second bearer are established when the first network device is initialized.
  • the first service attribute is an attribute of the air interface resource
  • the first network device further includes a first processor, where The processor determines a first bearer for transmitting data by using an attribute of the air interface resource of the data.
  • the first service attribute is a first quality of service feature
  • the first network device further includes a first processor
  • a processor determines a first bearer for transmitting data by a first quality of service characteristic of the data.
  • the second service attribute is a second service quality characteristic, and is used to receive the first bearer and data of the data.
  • the second quality of service feature corresponds.
  • the data received by the second bearer carries an IP address of the terminal
  • the second processor is configured according to the IP address of the terminal and the terminal.
  • the first identifier of the terminal is obtained by the correspondence between the identifiers; the second identifier carries the first identifier of the terminal in the data sent to the second network device.
  • the number of bits of the first identifier is less than the number of bits of the IP address.
  • the present application provides a data transmission method, where a pre-established one or more first bearers exist between a first network device and a base station.
  • the method includes the following steps: a base station receives data transmitted by a first network device through a first bearer.
  • the first bearer for receiving the data corresponds to the first service attribute of the data.
  • the base station sends data to the terminal through the air interface resource.
  • the first bearer is established when the base station or the first network device is initialized.
  • the first service attribute is an attribute of the air interface resource, and is used for receiving the first bearer of the data and the air interface resource of the data.
  • the attributes correspond.
  • the first service attribute is a first quality of service characteristic
  • the first bearer and the data are used to receive data.
  • a service quality characteristic corresponds.
  • the present application provides a base station, where one or more first bearers are pre-established between the first network device and the base station.
  • the base station includes a second receiver and a second transmitter.
  • the second receiver receives data transmitted by the first network device through a first bearer.
  • the first bearer for receiving the data corresponds to the first service attribute of the data.
  • the second transmitter transmits data to the terminal through the air interface resource.
  • the first bearer is established when the base station is initialized.
  • the first service attribute is an attribute of the air interface resource, and is used to receive the first bearer of the data and the air interface resource of the data.
  • the attributes correspond.
  • the first service attribute is a first quality of service characteristic
  • the first bearer and the data are used to receive data.
  • a service quality characteristic corresponds.
  • the present application provides a method for establishing a bearer, including: when the first network device is initialized, the first network device sends a first bearer setup request to the base station, where the first bearer setup request carries: the first network Identification information of the device and the first bearer information that is requested to be created; the first network device receives the first bearer setup response sent by the base station, where the first bearer setup response carries: the first bearer information allocated by the base station; The network device sends a second bearer setup request, where the second bearer setup request carries: the identifier information of the first network device and the second bearer information that is requested to be created; the first network device receives the second bearer setup response sent by the second network device; The second bearer setup response carries: the identifier information of the second bearer and the created second bearer information.
  • the method further includes: the first network device sends a second bearer modification request to the second network device, where the second bearer modification request carries: the second bearer bandwidth that is requested to be modified.
  • the first network device receives the second bearer modification response sent by the second network device, and the second bearer modification response carries: the bandwidth allocated by the modified second bearer.
  • the method further includes: the first network device sends the first bearer setup complete information to the base station, where the first bearer setup complete information carries: the established first bearer identifier information, the first network device identifier information, and the identifier of the base station information.
  • the first network device includes a first network device user plane and a first network device control plane, where The network device is specifically the first network device control plane, and the method further includes: the first network device control sends a first bearer setup request to the first network device user plane, where the first bearer setup request carries: the identifier of the base station and the base station allocated The first bearer information, the first network device control plane receives the first bearer setup response sent by the user plane of the first network device, where the first bearer setup response carries: the identifier of the user plane of the first network device, the identifier of the base station, and the first The first bearer information that is allocated by the user plane of the network device; the first network device controls to send the first bearer setup complete message to the user plane of the first network device, where the first bearer setup complete message carries: the identifier of the base station and the first Carry information.
  • the method further includes: the first network device control sends a second bearer setup request, the second bearer, to the user plane of the first network device
  • the setup request carries: a first network device control plane identifier and a first network device user plane identifier; the first network device control plane receives a second bearer setup response sent by the first network device user plane, and the second bearer setup response carries: An identifier of the user plane of the first network device and the second bearer information allocated by the user plane of the first network device; the first network device controls to send a second bearer setup complete message to the user plane of the first network device, where the second bearer setup response carries : Establishing the completed second bearer information.
  • the present patent application proposes a first network device, comprising: a processor and a memory coupled to each other, wherein the memory stores an instruction, and the processor executes the instruction to complete the method for establishing the bearer of the ninth aspect.
  • the present application provides a method for establishing a bearer, including: receiving, by a base station, a first bearer setup request sent by a first network device, where the first bearer setup request carries: identifier information and a request of the first network device The first bearer information is sent by the base station, and the first bearer setup response carries the first bearer information allocated by the base station.
  • the method further includes: receiving, by the base station, the first bearer setup complete information sent by the first network device, where the first bearer setup complete information carries: the created first bearer Logo.
  • the present patent application provides a base station, comprising: a processor and a memory coupled to each other, wherein the memory stores an instruction, and the processor executes the instruction to complete the method for establishing the bearer of the eleventh aspect.
  • the present application provides a method for establishing a bearer, including: when a base station is initialized, the first network device receives a first bearer setup request sent by the base station, where the first bearer setup request carries: identifier information of the base station And the first bearer information that is requested to be created; the first network device sends a first bearer setup response to the base station, where the first bearer setup response carries: the created first bearer information.
  • the method further includes: the first network device sends a second bearer setup request to the gateway, where the second bearer setup request carries: identifier information of the first network device, request to create The second bearer information is received by the first network device.
  • the second bearer setup response carries the identifier information of the second bearer and the created second bearer information.
  • the method further includes: the first network device sends a second bearer modification request to the gateway, where the second bearer modification request carries: the requested bandwidth; the first network device receives the gateway The second bearer modification response is sent: the second bearer modification response carries: the identifier information of the second bearer, and the bandwidth allocated by the modified second bearer.
  • the present patent application proposes a first network device, including a processor and a memory coupled to each other, wherein the memory stores an instruction, and the processor executes the instruction to complete the method for establishing the bearer of the thirteenth aspect.
  • the present patent application proposes a method for establishing a bearer.
  • the base station When the base station is initialized, the base station sends a first bearer setup request to the first network device, where the first bearer setup request carries: the identifier information of the base station, and the request is created.
  • the first bearer information is received by the first network device, where the first bearer setup response carries: the first bearer information allocated by the first network device.
  • the method further includes: receiving, by the base station, the first bearer setup complete information sent by the first network device, where the first bearer setup complete information carries: the created first bearer Logo.
  • the present patent application proposes a base station comprising a processor and a memory coupled to each other, wherein the memory stores an instruction, and the processor executes the instruction to complete the method for establishing the bearer of the fifteenth aspect.
  • the present application provides a method for a terminal to attach to a network, including: receiving, by the base station, an attach request sent by the terminal; the base station sending an attach request to the first network device, so that the first network device allocates the terminal for the terminal.
  • An identifier is received by the base station, and the base station sends an attach response sent by the first network device; the base station sends an attach response to the terminal; and the attach response carries: the first identifier of the terminal.
  • the attach response further includes: an IP address of the terminal, where the first identifier of the terminal has a corresponding relationship with the IP address of the terminal.
  • the number of bits of the first identifier of the terminal is less than the number of bits of the IP address of the terminal.
  • the patent application proposes a base station comprising a processor and a memory coupled to each other, wherein the memory stores an instruction, and the processor executes the instruction to complete the attaching method of the seventeenth aspect.
  • the present application provides a method for a terminal to be attached to a network, where the first network device receives an attach request sent by a base station, and the attach request is sent by the terminal to the base station; An identifier is sent by the first network device to the base station, so that the base station sends an attach response to the terminal; the attach response carries: the first identifier of the terminal.
  • the attaching response further includes: the first network device acquires the IP address of the terminal from the gateway, and the attach response further carries: the IP address of the terminal, and the first identifier of the terminal The IP address of the terminal has a corresponding relationship.
  • the method further includes: the first network device establishing a correspondence between the first identifier of the terminal and the IP address.
  • the present patent application proposes a first network device comprising a processor and a memory coupled to each other, wherein the memory stores instructions, and the processor executes the instructions to complete the attaching method of the nineteenth aspect.
  • the present application provides a method for a terminal to attach to a network, including: the terminal sends an attach request to the base station; the terminal receives the attach response sent by the base station, and the attach response carries: the first identifier of the terminal.
  • the first identifier is allocated by the first network device and has a corresponding relationship with the IP address of the terminal.
  • the present patent application proposes a terminal comprising a processor and a memory coupled to each other, wherein the memory stores an instruction, and the processor executes the instruction to complete the attaching method of the twenty-first aspect.
  • the first bearer and the second bearer used in data transmission are pre-established, which remain reserved for the next transmission after data transmission, which is not deleted as the single data transmission ends.
  • the first bearer and the second bearer need only be established once.
  • the first bearer and the second bearer are established according to service attributes, regardless of the number of terminals.
  • the number of the first bearer and the second bearer are each smaller than the number of terminals under the jurisdiction of the base station.
  • FIG. 1 is a schematic diagram of an architecture of a network system in accordance with an embodiment of the present patent application.
  • FIG. 2 is a schematic diagram of an architecture of a network system in accordance with another embodiment of the present patent application.
  • FIG. 3 is a schematic diagram of a machine type data uplink transmission method according to an embodiment of the present patent application.
  • FIG. 4 is a schematic diagram of a machine type data downlink transmission method according to another embodiment of the present patent application. Figure.
  • FIG. 5 is a schematic diagram of a data transmission method under the first network device integration architecture according to another embodiment of the present patent application.
  • FIG. 6 is a schematic diagram of a data transmission method under a first network device separation architecture according to another embodiment of the present patent application.
  • FIG. 7 is a schematic diagram of interaction of a method for establishing a bearer in a case where the first network device is initialized under the centralized architecture of the first network device.
  • FIG. 8 is a schematic diagram of interaction of a method for establishing a bearer in a case where the first network device is initialized in a separate architecture of the first network device.
  • FIG. 9 is a schematic diagram of interaction of a method for establishing a bearer in a case where a base station is initialized under a centralized architecture of a first network device.
  • FIG. 10 is a schematic diagram of interaction of a method for establishing a bearer in a case where a base station is initialized under a split architecture of a first network device.
  • 11-12 are flow diagrams of two different embodiments in which a terminal is attached to a network under the architecture of the first network device integration.
  • 13-15 are flow diagrams of three different embodiments in which a terminal is attached to a network under a separate architecture of the first network device.
  • Figure 16 is a schematic illustration of a machine type data transfer system in accordance with one embodiment of the present patent application.
  • FIG 17 is a schematic illustration of a machine type data transmission system in accordance with another embodiment of the present patent application. Figure.
  • first and the like are used to distinguish similar objects, and “first” is merely an object of a certain class or class, and is not necessarily used to describe a specific order or order. It is to be understood that the terms so used are interchangeable as appropriate, and are merely illustrative of the manner in which the objects of the same attributes are described in the embodiments of the present application. "One” or “one” does not exclude multiple cases.
  • the terminals involved in the present patent application may include various handheld devices having wireless communication functions, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to wireless modems, and various forms of user equipment (User Equipment, Referred to as UE), mobile station (MS), terminal equipment (Terminal Equipment) and so on.
  • UE User Equipment
  • MS mobile station
  • Terminal Equipment Terminal Equipment
  • the above mentioned devices are collectively referred to as a terminal or a UE.
  • a base station (BS) referred to in this patent application is a device deployed in a radio access network to provide a wireless communication function for a UE.
  • the base station may include various forms of macro base stations, micro base stations, relay stations, access points, and the like.
  • the name of a device having a base station function may be different.
  • an evolved Node B evolved Node B: eNB or eNodeB
  • Node B In the 3G network, it is called Node B and so on.
  • the above-mentioned devices for providing wireless communication functions to the UE are collectively referred to as a base station or a BS.
  • the gateway may include a Serving Gateway (S-GW) or a Packet Data Network Gate (P-GW) or other network node having a gateway function.
  • S-GW Serving Gateway
  • P-GW Packet Data Network Gate
  • An unauthorized transfer can be understood as any one of the following meanings, or multiple meanings, or a combination of some of the various technical meanings or other similar meanings:
  • the unlicensed transmission may refer to: in a public land mobile network (PLMN) network, the first network device or the cloud/Centralized Radio Access Network (CRAN) scenario is not required.
  • the wireless controller can dynamically implement the method of uplink data transmission of the terminal. Dynamic scheduling refers to the transmission resource after the transmission time interval (TTI) of the current receiving signaling time is assigned to each uplink transmission of the UE by the network.
  • TTI transmission time interval
  • the transmission time interval refers to the minimum transmission time of one uplink transmission. Time unit, such as 1ms.
  • the unlicensed transmission may include: according to the characteristics of the transmission data, such as the transmission delay or the reliability requirement, on the specified time-frequency resource, the code resource and the pilot resource supported by the time-frequency resource are used. Modulation coding scheme, feedback class, diversity mode, etc. for data transmission to reduce network signaling and/or reduce transmission Delay.
  • the unlicensed transmission may be: the first network device pre-allocates and informs the terminal device of multiple transmission resources; when the terminal device has an uplink data transmission requirement, select at least one transmission resource from the plurality of transmission resources pre-allocated by the first network device, and use The selected transmission resource sends the uplink data; the first network device detects the uplink data sent by the terminal device on the transmission resource in the pre-assigned multiple transmission resources.
  • the detection may be blind detection, or may be performed according to one of the control domains in the uplink data, or may be detected in other manners.
  • the unlicensed transmission may be: the first network device pre-allocates and informs the terminal device of multiple transmission resources, so that when the terminal device has an uplink data transmission requirement, at least one transmission resource is selected from multiple transmission resources pre-allocated by the first network device. , using the selected transmission resource to send uplink data.
  • the unlicensed transmission may be: acquiring information of a plurality of pre-assigned transmission resources, selecting at least one transmission resource from the plurality of transmission resources when there is an uplink data transmission requirement, and transmitting the uplink data by using the selected transmission resource.
  • the method of obtaining can be obtained from the first network device.
  • the unlicensed transmission may be a method for implementing uplink data transmission of the terminal device without dynamic scheduling of the first network device, where the dynamic scheduling may refer to that the first network device uses signaling for each uplink data transmission of the terminal device.
  • implementing uplink data transmission of the terminal device may be understood as allowing data of two or more terminal devices to perform uplink data transmission on the same time-frequency resource.
  • the transmission resource may be a transmission resource in a transmission time unit after the time when the UE receives the signaling.
  • a transmission time unit may refer to a minimum time unit for one transmission, such as a TTI (Transmission Time Interval), the value may be 1 ms, or may be a preset transmission time unit.
  • the unlicensed transmission may mean that the terminal device performs uplink data transmission without requiring authorization of the first network device.
  • the authorization may be performed by the terminal device sending an uplink scheduling request to the first network device. After receiving the scheduling request, the first network device sends an uplink grant to the terminal device, where the uplink grant indicates the uplink transmission resource allocated to the terminal device.
  • the unlicensed transmission may refer to: a contention transmission mode, which may specifically mean that multiple terminals simultaneously perform uplink data transmission on the same time-frequency resources allocated in advance without the base station performing authorization.
  • the blind detection can be understood as the detection of data that may arrive without predicting whether or not data has arrived.
  • the blind detection can also be understood as detection without explicit signaling indication.
  • the air interface resource refers to a resource used by the terminal to perform transmission on an air interface.
  • the first network device is a network side communication device that performs data transmission with a base station.
  • the first network device also processes the data.
  • the transmission resource may include, but is not limited to, a combination of one or more of the following resources:
  • time domain resources such as radio frames, subframes, symbols, etc.
  • - frequency domain resources such as subcarriers, resource blocks, etc.
  • - airspace resources such as transmit antennas, beams, etc.
  • SCMA Sparse Code Multiple Access
  • LDS Low Density Signature
  • the above transmission resources may be transmitted according to a control mechanism including, but not limited to, the following:
  • uplink power control such as uplink transmit power upper limit control, etc.
  • Modulation coding mode setting such as transmission block size, code rate, modulation order setting, etc.
  • the first network device refers to a communication device that receives data of an unlicensed transmission from a base station or sent to a base station, and processes the data of the unauthorized transmission
  • a Contention Transmission Unit (CTU)
  • a CTU may refer to a transmission resource combining time, frequency, and code domain, or may refer to a transmission resource combining time, frequency, and pilot, or may refer to a transmission resource combining time, frequency, code domain, and pilot.
  • the access area of the CTU may refer to a time-frequency area for unlicensed transmission, and may further refer to a time-frequency area corresponding to the CTU.
  • the network entity names in all embodiments of this patent may be extended to names having the same or similar functions.
  • each step is labeled. However, this does not mean that the steps need to be performed sequentially in the order of the labels. Those skilled in the art can adjust the sequence of each step without paying creative labor.
  • a patent application with the patent application number PCT/CN2014/073084 and the patent application name "System and Method for Uplink Grant-free Transmission Scheme” provides a technical solution for uplink unlicensed transmission.
  • a radio resource is divided into a contention transmission unit (CTU) of various sizes, and a terminal device is mapped to a certain CTU.
  • Each CTU is assigned a set of codes, and the assigned code may be Code Division Multiple Access (Code Division Multiple Access,
  • the CDMA) code may also be a Sparse Code Multiple Access (SCMA) or a Low Density Signature (LDS) or a signature.
  • Each code corresponds to a set of pilots.
  • the terminal may select one code and one pilot in the pilot group corresponding to the code for uplink transmission.
  • PCT/CN2014/073084 is also understood to be a part of the content of the embodiment of the present patent application, and is not described again.
  • PCT/CN2014/073084 is mainly for air interface transmission, and it does not mention how the network side should handle it. This patent application can solve the processing on the network side and improve the efficiency of network service processing.
  • the Mobility Management Entity sends an Initial Context Setup Request to the eNB (enhanced NodeB) to establish the bearer of the base station to the S-GW and the air interface.
  • the number of terminals accessing a base station may be 300,000 or more.
  • the frequency and data packets of some MTC terminals may be small. Since the transmission frequency is small, the MTC terminal enters the idle state after performing one transmission. At the next transmission, it needs to be transmitted through the random access procedure. Due to the existence of a large number of terminals, the system will generate a large number of random access procedures, which greatly consumes system resources, especially occupying a large amount of signaling resources, which may cause other normal large data volume transmission services to be affected.
  • the delay requirements are relatively high, such as the Internet of Vehicles business. If the transmission is performed through the traditional scheduling request process, it will cause a large delay and cannot meet the service requirements.
  • FIG. 1 is a schematic diagram of an architecture of a network system in accordance with an embodiment of the present patent application.
  • the network system includes a first network device 104, a gateway (GateWay, GW for short) 106, a network controller (NC) 108, and a plurality of base stations (Evolved Node B, eNB for short) 102.
  • Each base station 102 governs a large number of terminals under it.
  • the first network device 104 is a centralized architecture that can be responsible for both the processing of the control plane and the processing of the user plane, such as data transmission.
  • the first network device 104 can be connected to a plurality of base stations 102 to serve terminals under the plurality of base stations 102.
  • the first network device 104 can also be coupled to the network controller 108, which can obtain terminal information, such as policy control information, from the network controller.
  • the network controller 108 may include a mobility management entity (MME), a Policy Charging and Rule Function (PCRF), or a Home Subscriber Server (HSS).
  • MME mobility management entity
  • PCRF Policy Charging and Rule Function
  • HSS Home Subscriber Server
  • the first network device 104 can also be coupled to the gateway 106.
  • the first network device has an ID that uniquely identifies its identity, which may be the IP address of the first network device.
  • the network of the embodiment of the present patent application may refer to a Public Land Mobile Network (PLMN) or a Device to Device (D2D) network.
  • PLMN Public Land Mobile Network
  • D2D Device to Device
  • FIG. 1 is only a simplified schematic diagram of an example, and other first network devices may also be included in the network, which are not shown in FIG. 1.
  • the first network device 104 can be a physical entity or a functional entity. When it is a functional entity, it can be physically deployed with a network controller or S_GW or other network device.
  • first bearers pre-established between the first network device and the base station.
  • second bearers pre-established between the first network device and the second network device.
  • the network adopts an architecture separated by a Control Plane/User Plane (C/U).
  • the control plane is centrally controlled, and the user plane completes data forwarding.
  • the network system includes a first network device, a gateway 106, a network controller 108, and a plurality of base stations 102.
  • the first network device is a split architecture that includes a first network device control plane 104a and a first network device user plane 104c.
  • the first network device control plane 104a and the first network device user plane 104c may each be connected to a plurality of base stations.
  • a first network device control plane may be connected to the first network device user plane, and different first network device user planes may support multiple services, or may respectively support different service categories.
  • a first network device user plane (User Plane) supports low-latency, high-reliability services
  • a first network device user plane supports delay-tolerable reliable transmission services.
  • FIG. 3 is a schematic diagram of a data transmission method for performing uplink data transmission according to an embodiment of the present patent application.
  • 4 is a schematic diagram of a data transmission method for performing data transmission according to another embodiment of the present patent application.
  • the uplink data transmission and the downlink data transmission may be performed separately or simultaneously.
  • the first network device may refer to the first network device in the centralized architecture of the first network device or the first network device user plane in the separate architecture of the first network device.
  • the application scenario of the transmission method includes: one or more first bearers pre-established between the first network device and the base station, and one or more second bearers pre-established between the first network device and the second network device .
  • the transmission method includes the following steps:
  • the terminal sends data to the base station by using the air interface resource, and the base station receives the data sent by the terminal from the air interface resource.
  • the base station sends data to the first network device by using a first bearer, where the first network device receives data sent by the base station.
  • the first network device sends data to the second network device by using a second bearer.
  • the first bearer and the second bearer are pre-established and are not released after a single data transfer is completed.
  • the first bearer and the second bearer remain reserved for the next data transmission after the end of a single data transmission.
  • the first bearer and the second bearer do not need to continuously create and delete bearers as the state of the terminal changes or the end of a single data transmission.
  • the first bearer and the second bearer need only be established once. This avoids the signaling process required for the establishment and deletion of bearers and the resulting delay. This effectively improves the efficiency of network business processing.
  • the first bearer is pre-established according to the first service attribute.
  • the second bearer is pre-established according to the second service attribute.
  • the number of first bearers has nothing to do with the number of terminals.
  • the number of second bearers is also irrelevant to the number of base stations.
  • the number of first bearers and second bearers is determined by the traffic attributes of the data to be transmitted.
  • First bearer and first The number of two bearers does not need to correspond to each terminal.
  • the patent application uses a limited bearer to solve the problem of a large number of terminal data transmissions, avoiding the bearer signaling process of a large number of terminals and the resulting delay. This effectively improves the efficiency of network business processing.
  • the transmitting method may further include the step 304: determining the first bearer.
  • the transmission method may further include the step 305 of determining the second bearer.
  • the first service attribute may correspond to an attribute of the air interface resource.
  • Data using the same type of air interface resource can be placed on the first bearer for data transmission.
  • data for the same type of service category is scheduled to the same air interface resource.
  • data of the same type of service can be placed on the same first bearer for data transmission.
  • the base station determines that the first bearer corresponding to the air interface resource used by the data performs data transmission.
  • the first bearer corresponds to the air interface resource used by the data.
  • the first service attribute may also be the first quality of service feature.
  • Data having the same first quality of service characteristic of the same class can be placed on the first bearer for data transmission.
  • the base station determines a first bearer corresponding to a first quality of service characteristic (QoS) of data transmitted by the terminal.
  • the first bearer corresponds to a first quality of service characteristic of the data.
  • the second service attribute may be a second quality of service feature, and data with the same type of second quality of service feature may be placed on the second bearer for data transmission.
  • the second quality of service characteristic may be the same as or different from the first quality of service characteristic.
  • a plurality of different, adjacent levels of first quality of service characteristics may be combined into one level of second quality of service characteristics.
  • the data transmitted on the first bearer carries the first identifier of the terminal.
  • the first identifier enables the base station and the first network device to accurately distinguish each terminal within its management domain. There may be orthogonality or quasi-orthogonality or low correlation between the first identifiers of the respective terminals.
  • the base station can learn the first network device corresponding to the data it receives, and send the data to the first network device.
  • the first network device can also know the base station corresponding to the data it receives.
  • the data transmitted on the second bearer carries the IP address of the terminal.
  • the first identifier of the terminal has a corresponding relationship with the IP address of the terminal.
  • the IP address of the terminal may be assigned by the gateway when the terminal is attached.
  • the first network device can search for and obtain the IP address of the terminal by using the first identifier of the terminal. This provides the possibility of not carrying an IP address when performing data transmission on the first bearer and the air interface.
  • the transmitting method may further include: Step 306: Acquire an IP address of the terminal according to the first identifier of the terminal.
  • the number of bits of the first identifier of the terminal is less than the number of bits of the IP address.
  • the terminal can be identified only by the first identifier allocated for the terminal, and the air interface overhead is reduced.
  • the first identifier of the terminal may be that the terminal is allocated by the first network device when attached.
  • the IP address of the terminal may be assigned by the gateway when the terminal is attached. The specific identification method of the first identifier and IP address of the terminal will be further described in detail below.
  • the entire data transmission can be performed according to the data control policy of the terminal.
  • the first network device may acquire terminal information, such as policy control information, from the network controller, in order to complete authentication, encryption, and QoS control of the terminal.
  • the second network device may be a gateway.
  • the second network device can also be a server, such as an application server.
  • various application services can be provided to the user through the Internet, so that the network can support the OTT (over the top) service capability, and particularly provides a vertical service capability when the network supports network slicing in the future.
  • the transmission method includes the following steps:
  • the second network device sends data to the first network device by using a second bearer.
  • the first network device receives data sent by the second network device.
  • the first network device sends data to the base station by using a first bearer.
  • the base station receives data transmitted by the first network device.
  • the base station sends data to the terminal by using an air interface resource.
  • the transmitting method may further include the step 404 of determining the second bearer.
  • the transmission method may further include the step 405 of determining the first bearer.
  • QoS quality of service characteristic of the data transmitted by the second network device
  • the second bearer corresponds to a second quality of service characteristic of the data.
  • the first network device can determine a first bearer corresponding to a first quality of service characteristic (QoS) of data transmitted by the second network device.
  • the first bearer corresponds to a first quality of service characteristic of the data.
  • the first network device can also determine a first bearer corresponding to an attribute of an air interface resource used by data transmitted by the second network device.
  • the first bearer corresponds to an attribute of the air interface resource of the data.
  • the data transmitted on the first bearer carries the first identifier of the terminal.
  • the data transmitted on the second bearer carries the IP address of the terminal.
  • the transmission method may further include the step 406: the first network device acquires the first identifier of the terminal according to the IP address of the terminal.
  • FIG. 5 is a schematic diagram of a data transmission method under the first network device integration architecture according to another embodiment of the present patent application.
  • the communication method can perform security control to prevent some malicious terminals from continuously sending messages, which causes the system to block.
  • the data transmission method includes the following steps:
  • the first network device receives data of the terminal forwarded by the base station. For detailed procedures of this step, refer to 301-302 above.
  • the first network device performs detection of the suspect terminal.
  • a suspect terminal is a terminal that maliciously attacks a system. For example, terminals that transmit frequently, have security problems, and have encrypted data problems.
  • the first network device can detect the suspect terminal using a detection algorithm.
  • the first network device When detecting the suspect terminal, the first network device sends a security request to the base station, where the security request carries: the identity identifier of the suspect terminal.
  • the identity identifier may be a permanent identity of the terminal, such as an international mobile subscriber identity (IMSI) or a mobile access code (mobile access code). Code, referred to as MAC address.
  • IMSI international mobile subscriber identity
  • MAC address Mobile access code
  • the base station receives the security request.
  • the base station performs security processing on the data of the suspect terminal.
  • the security processing may specifically include: blocking the data of the suspect terminal or re-authenticating the suspect terminal in the air interface.
  • the base station sends a security response to the first network device.
  • the security response carries: the identity of the terminal that has been securely processed.
  • FIG. 6 is a schematic diagram of a data transmission method under a first network device separation architecture according to another embodiment of the present patent application. This communication method can perform security control. As shown in FIG. 6, the data transmission method includes the following steps:
  • the first network device user plane receives data of the terminal forwarded by the base station. For detailed procedures of this step, refer to 301-302 above.
  • execution body is the first network device user plane instead of the first network device.
  • the first network device user When detecting the suspect terminal, the first network device user sends a security request to the first network device control plane, so that the first network device control plane and the base station take security measures.
  • the security request can carry: the identifier of the suspect terminal.
  • the first network device control plane receives the security request, and sends a security request to the base station.
  • the base station receives the security request.
  • the base station performs security processing on the data of the suspect terminal.
  • the security processing may specifically include: blocking the data of the suspect terminal or re-authenticating the suspect terminal in the air interface.
  • the base station sends a security response to the first network device control plane.
  • the security response carries: the identity of the terminal that has been securely processed.
  • the first network device controls to send a security response to the user plane of the first network device, where the first network device user plane receives the security response.
  • the security response carries: the identity of the terminal that has been securely processed.
  • the bearer establishment is mainly established in advance between the first network device and the base station and the first network device and the second network device.
  • the establishment of the bearer may be at the time of initialization of the first network device or at the time of initialization of the base station.
  • FIG. 7 is a schematic diagram of interaction of a method for establishing a bearer when the first network device is initialized under the centralized architecture of the first network device. As shown in FIG. 7, a method for establishing a bearer includes the following steps:
  • the first network device When the first network device is initialized, the first network device is configured with all base station information under its jurisdiction. The first network device sends a first bearer setup request to the base station under its jurisdiction.
  • the first bearer setup request may carry: an ID of the first network device, an IP address, and first bearer information that is requested to be created.
  • the first bearer information corresponds to the first service attribute, and may include: a QoS level, a requested bandwidth, and a port number.
  • the base station receives the first bearer setup request, prepares the first bearer resource, and sends a first bearer setup response to the first network device.
  • the first bearer setup response may carry: an ID of the base station, an IP address, and the created first bearer information.
  • the first bearer information created includes: a QoS level, an allocated bandwidth, and a first bearer ID.
  • the first network device receives the first bearer setup response sent by the base station, and sends the first bearer setup complete information to the base station.
  • the first bearer setup completion information may carry: a first bearer setup completion indication. This step is mainly used to confirm that the base station receives the first bearer setup response of the first network device. This step is optional.
  • the first network device sends a second bearer setup request to the second network device.
  • the second network device can be a gateway.
  • the second network device can also be a server, such as an application server.
  • the second bearer setup request may carry: identifier information of the first network device and second bearer information that is requested to be created.
  • the second bearer information may include: a QoS level, a requested bandwidth.
  • the second bearer information corresponds to the second service attribute.
  • the second network device receives the second bearer setup request, completes the bearer resource allocation, and sends a second bearer setup response to the first network device.
  • the first network device receives a second bearer setup response sent by the second network device.
  • the second bearer setup response may carry: an ID of the second network device, an IP address, an ID of the first network device, an IP address, and the created second bearer information.
  • the created second bearer information includes: a QoS level, an allocated bandwidth, and a second bearer ID.
  • the first bearer and the second bearer are set up when the first network device is initialized.
  • the bearer is not required to wait until the data is transmitted or when the terminal is attached.
  • the access delay and transmission scheduling delay during data transmission are avoided. This effectively improves the efficiency of network business processing.
  • first bearers and second bearers can be created simultaneously as needed.
  • the first bearer is established according to the first service attribute
  • the second bearer is established according to the second service attribute.
  • the bearers can be separately established for different types of services. In this way, only one first bearer can be established for the same type of service of different terminals.
  • a first bearer can be used for data transmission of the same type of service of different terminals.
  • the first service attribute may specifically be the first QoS of the service that the terminal needs to perform.
  • the first service attribute may also be an attribute of an air interface resource used by the terminal service. The difference between the two is that the granularity of the base station processing the terminal service is different.
  • the bearer is established according to the QoS of the service, and the base station needs to establish a bearer according to a type of QoS class. And according to A bearer resource is used to establish a bearer, and a bearer is established for a type of air interface resource according to the air interface resource configured by the base station. It should be noted that even if the bearer is established according to the QoS level, it may be that several different QoS levels are merged into one bearer to reduce the number of bearers.
  • the second service attribute may be the second QoS of the service.
  • the services from the base stations may be re-merged, and the services with the same first QoS attribute are placed on the same second bearer for transmission, or the services of multiple different first QoS attributes may be placed.
  • the same second bearer is transmitted.
  • the number of first bearers and second bearers is determined by the traffic attributes of the data to be transmitted.
  • the number of first bearers has nothing to do with the number of terminals.
  • the number of second bearers is also irrelevant to the number of base stations.
  • the number of the first bearer and the second bearer are each smaller than the number of terminals under the jurisdiction of the base station.
  • the number of the first bearer and the second bearer does not need to correspond to each terminal, and the problem of a large number of terminal data transmission can be solved by using a limited bearer, and the bearer signaling process and the resulting delay can be avoided.
  • the first bearer and the second bearer are reserved for establishment for data transmission. It is no longer necessary to establish a bearer during data transmission, and the first bearer and the second bearer are not deleted after the end of a single data transmission.
  • the first bearer and the second bearer need only be established once.
  • the first bearer and the second bearer do not need to continuously create and delete bearers as the state of the terminal changes.
  • the first network device may also choose to send a multicast message to all base stations under its jurisdiction.
  • the first network device then receives the message returned by each base station.
  • the first network device establishes a second bearer to the second network device according to the bandwidth requirement of each base station.
  • the first bearer and the second bearer are two independent bearers.
  • the number of first bearers may be one or more. when When the number of first bearers is one, all unlicensed services under the jurisdiction of the base station are transmitted on the unique first bearer. When the number of the first bearers is multiple, the corresponding first bearer may be selected for data transmission according to requirements.
  • the number of second bearers may also be one or more.
  • the number of second bearers is one, the unlicensed services of all base stations under the jurisdiction of the first network device are transmitted on the unique second bearer.
  • the number of the second bearers is multiple, the corresponding first bearer may be selected for data transmission according to requirements.
  • the number of bearers is determined according to the service attributes, and has no relationship with the number of terminals and base stations. In this embodiment, there is no need to establish a bearer for each of the unauthorized terminals.
  • the number of bearers does not need to correspond to the number of terminals, and the number of bearers is very limited. The number of bearers that need to be established will be greatly reduced relative to the prior art. This effectively improves the efficiency of network business processing.
  • FIG. 8 is a schematic diagram of interaction of a method for establishing a bearer in a case where the first network device is initialized in a separate architecture of the first network device.
  • the main difference between the method for establishing the bearer shown in FIG. 8 and the method for establishing the bearer shown in FIG. 7 is that the bearer setup request is specifically initiated by the first network device control plane in FIG. 8, and the first network device control plane is added. Interaction with the user plane of the first network device. Specifically, the method includes the following steps:
  • the first network device controls to send a first bearer setup request to the base station.
  • the first bearer setup request may carry: an ID of the control plane of the first network device, an IP address, and first bearer information that is requested to be created.
  • the first bearer information requested to be created may include: a QoS level and a requested bandwidth.
  • the base station receives the first bearer setup request, prepares resources for the first bearer, and sends a first bearer setup response to the first network device control plane.
  • the first bearer setup response may carry: the ID of the base station, the IP address, and the base station The first bearer information assigned.
  • the first bearer information allocated by the base station may include: a QoS level, an allocated bandwidth, and a first bearer ID.
  • the first network device control plane receives the first bearer setup response sent by the base station, and selects a first network device user plane controlled by the first network device according to the service attribute, and sends a first bearer setup request to the first network device user plane.
  • the first bearer setup request may carry: an ID of the base station, an IP address, and first bearer information allocated by the base station.
  • the first network device user After receiving the first bearer setup request, the first network device user sends a first bearer setup response to the first network device control plane.
  • the first bearer setup response may carry: an ID of the user plane of the first network device, an IP address, an ID of the base station, an IP address, and first bearer information allocated by the user plane of the first network device.
  • the allocated first bearer information may include: a QoS level, an allocated bandwidth, and a first bearer ID.
  • the first bearer establishes completion information.
  • the first bearer setup complete information may carry: a first bearer setup completion indication, an ID of the user plane of the first network device, an IP address, an ID of the base station, an IP address, and first bearer information that is established.
  • the first bearer information that is established may include: a QoS level, an allocated bandwidth, and a first bearer ID. This step is mainly used to notify the first network device user plane and the first bearer information that the base station creates.
  • the first network device controls to send a second bearer setup request to the first network device user plane.
  • the first network device control plane can simultaneously establish a second bearer for the first network device user plane under its jurisdiction.
  • the QoS of each second bearer may be determined according to the QoS and control policy of the first bearer.
  • the second bearer setup request may carry: The ID of the control plane of the network device, the IP address, the ID of the target user plane of the first network device, and the IP address.
  • the first network device user After receiving the second bearer setup request, the first network device user sends a second bearer setup response to the first network device control plane.
  • the second bearer setup response may carry: an ID of the first network device user plane, an IP address, an ID of the first network device control plane, an IP address, and second bearer information allocated by the first network device user plane.
  • the allocated second bearer information includes: a QoS level, an allocated bandwidth, and a second bearer ID.
  • the first network device control plane After receiving the second bearer setup response from the user plane of the first network device, the first network device control plane sends a second bearer setup request to the second network device to establish a second bearer for each first network device user plane.
  • the second bearer setup request may carry: an ID of the control plane of the first network device, an IP address, an ID of each user plane of the first network device, an IP address, and second bearer information allocated by each user plane of the first network device.
  • the allocated second bearer information may include: a QoS level, an allocated bandwidth, and a second bearer ID.
  • the second network device receives the second bearer setup request, and after completing the bearer resource allocation, returns a second bearer setup response corresponding to each user plane of the first network device to the first network device control plane.
  • the second bearer setup response may carry: an ID of the second network device, an IP address, an ID of each user plane of the first network device, an IP address, and a second bearer allocated by the second network device to each user plane of the first network device. information.
  • the allocated second bearer information may include: a QoS level, an allocated bandwidth, and a second bearer ID.
  • the first network device controls to send the second bearer setup complete information to the second network device (811) and the first network device user plane (812).
  • the second bearer setup complete information may carry: an ID of the second network device, an IP address, an ID of the user plane of the first network device, an IP address, and second bearer information for which the creation is completed.
  • Second The bearer information includes: a QoS level, an allocated bandwidth, and a second bearer ID. This step is mainly used to notify the first network device user plane and the second network device to complete the second bearer information.
  • FIG. 9 is a schematic diagram of interaction of a method for establishing a bearer in a case where a base station is initialized under a centralized architecture of a first network device. As shown in FIG. 9, a method for establishing a bearer includes the following steps:
  • the base station sends a first bearer setup request to the first network device.
  • the first bearer setup request may carry: an ID of the base station, an IP address, and first bearer information (including: QoS level, requested bandwidth) that is requested to be created.
  • the first bearer setup request may also carry: resource information allocated by the base station for different CTUs, including the frequency of the air interface, the air interface bandwidth, the modulation and coding scheme, and the service attributes corresponding to each CTU.
  • a service attribute can refer to a QoS level of a service.
  • the first network device receives the first bearer setup request, prepares the first bearer resource, and sends a first bearer setup response to the base station.
  • the first bearer setup response may carry: an ID of the first network device, an IP address, and the created first bearer information.
  • the created first bearer information may include: a QoS level, an allocated bandwidth, and a first bearer ID.
  • the base station receives the first bearer setup response sent by the first network device, and sends the first bearer setup complete information to the first network device, where the first bearer setup complete information may carry: the first bearer setup complete indication.
  • This step is mainly used to confirm that the first network device receives the first bearer setup response of the base station. This step is optional.
  • steps 904 and 905 can be performed.
  • the bandwidth allocated by the base station for the unlicensed service is larger or smaller, the first network device and the second network device may be caused. of The bandwidth is insufficient or redundant. In this case, the transmission bandwidth between the first network device and the second network device needs to be modified, and steps 906 and 907 are performed. If the bandwidth between the first network device and the second network device is sufficient, no steps need to be taken.
  • the first network device sends a second bearer setup request to the second network device, where the second bearer setup request may carry: an ID of the first network device, an IP address, and second bearer information that is requested to be created.
  • the second bearer information requested to be created may include: a QoS level and a requested bandwidth.
  • the second network device receives the second bearer setup request, completes the bearer resource allocation, and sends a second bearer setup response to the first network device.
  • the first network device receives a second bearer setup response sent by the second network device.
  • the second bearer setup response may carry: an ID of the second network device, an IP address, and identifier information of the first network device and the created second bearer information.
  • the created second bearer information includes: a QoS level, an allocated bandwidth, and a second bearer ID.
  • the first network device sends a second bearer modification request to the second network device, where the second bearer modification request may carry: a bandwidth requested to be modified.
  • the second network device receives the second bearer modification request, completes modification of the bearer resource, and sends a second bearer modification response to the first network device.
  • the first network device receives the second bearer modification response sent by the second network device.
  • the second bearer modification response may carry: the identifier information of the second bearer and the bandwidth allocated by the modified second bearer.
  • the second bearer between the server and the first network device may be established at the time of server initialization.
  • the establishment process can refer to the above description.
  • FIG. 10 is a schematic diagram of interaction of a method for establishing a bearer in a case where a base station is initialized under a split architecture of a first network device.
  • the main difference between the method for establishing the bearer shown in FIG. 10 and the method for establishing the bearer shown in FIG. 9 is that, in FIG. 10, the base station specifically initiates a bearer setup request to the first network device control plane, and adds the first network device.
  • the base station sends a first bearer setup request to the first network device control plane.
  • the first bearer setup request may carry: an ID of the base station, an IP address, and first bearer information that is requested to be created.
  • the first bearer information created by the request includes: a QoS level, and a requested bandwidth.
  • the first bearer setup request may also carry: resource information allocated by the base station for different CTUs, including the frequency of the air interface, the air interface bandwidth, the modulation and coding scheme, and the service attributes corresponding to each CTU.
  • a service attribute can refer to a QoS level of a service.
  • the first network device control sends a first bearer setup request to the first network device user plane, and notifies the first network device user plane to prepare to bear the resource.
  • the first bearer setup request sent to the user plane of the first network device may carry: an ID of the base station, an IP address, and first bearer information that is requested to be created.
  • the first bearer information created by the request includes: a QoS level, and a requested bandwidth.
  • the requested bandwidth refers to the bandwidth of the bearer between the base station and the user plane of the first network device.
  • the first network device user plane receives the first bearer setup request, and sends a first bearer setup response to the first network device control plane.
  • the first network device user plane returns the bearer establishment result to the first network device control plane.
  • the first bearer setup response may carry: an ID of the user plane of the first network device, an IP address, and first bearer information allocated by the user plane of the first network device.
  • the first bearer information includes: a QoS level, an allocated bandwidth, and The first bearer ID.
  • the first network device control plane receives the first bearer setup response, and sends a first bearer setup response to the base station.
  • the base station receives the first bearer setup response sent by the control plane of the first network device, and sends the first bearer setup complete information to the control plane of the first network device.
  • the first bearer setup complete information may carry: the user plane of the first network device The ID, the IP address, and the first bearer information created for the user plane of the first network device.
  • the first bearer information includes: a QoS level, an allocated bandwidth, and a first bearer ID.
  • the first network device controls to send a first bearer setup complete message to the first network device user plane.
  • the message may carry: an ID of the user plane of the first network device, an IP address, and first bearer information created for the user plane of the first network device.
  • the first bearer information may include: a QoS level, an allocated bandwidth, and a first bearer ID.
  • steps 1007-1012 may be performed.
  • the bandwidth allocated by the base station for the unlicensed service is larger or smaller.
  • the first network device control plane and the second may be caused.
  • the bandwidth between the network devices is insufficient or redundant.
  • the transmission bandwidth between the control plane of the first network device and the second network device needs to be modified, and steps 1013 and 1014 are performed. If the bandwidth between the first network device control plane and the second network device is sufficient, no steps need to be taken.
  • the first network device control sends a second bearer setup request to the first network device user plane, and notifies the first network device user plane to prepare to bear the resource.
  • the second bearer setup request sent to the first network device user plane may carry: an ID of the first network device control plane, an IP address, a base station ID, an IP address, and a request resource. Assignment instructions.
  • the unauthorized user plane can simultaneously establish the second bearer.
  • the QoS of each second bearer may be determined according to the QoS and control policy of the first bearer of the requesting base station.
  • the second bearer setup response is sent to the first network device control plane.
  • the first network device user plane returns the prepared bearer resource information to the first network device control plane.
  • the first network device user sends a second bearer setup response to the first network device control plane.
  • the second bearer setup response may carry: an ID, an IP address, and an allocated first bearer information of the user plane of the first network device.
  • the first bearer information includes: a QoS level, an allocated bandwidth, and a first bearer ID.
  • the first network device control sends a second bearer setup request to the second network device, and the bearer may be established for the unauthorized user plane.
  • the second bearer setup request may carry: an ID of the control plane of the first network device, an IP address, and second bearer information that is requested to be created.
  • the bearer information may include: a QoS level and a requested bandwidth.
  • the second network device receives the second bearer setup request, completes the bearer resource allocation, and sends a second bearer setup response to the first network device control plane.
  • the first network device control plane receives the second bearer setup response sent by the second network device.
  • the second bearer setup response may carry: an ID of the second network device, an IP address, identifier information of the control plane of the first network device, and second bearer information allocated by the second network device.
  • the second bearer information may include: a QoS level, an allocated bandwidth, and a second bearer ID.
  • the first network device controls to send a bearer setup complete message to the second network device.
  • the message may carry: an ID of the second network device, an IP address, an ID of the first network device user plane, an IP address, and a created second bearer ID.
  • the first network device control sends a second bearer setup complete message to the second network device (1011) and the first network device user plane (1012), respectively.
  • the second bearer setup complete message may carry: a first network device control plane ID, an IP address, an ID of the first network device user plane, an IP address, and a second bearer information that is established.
  • the second bearer information may include: a QoS level, an allocated bandwidth, and a second bearer ID.
  • the first network device control sends a second bearer modification request to the second network device, where the second bearer modification request may carry: a bandwidth requested to be modified.
  • the first network device control plane receives the second bearer modification response sent by the second network device (1014) and the first network device user plane (1015), and the second bearer modification response may carry: the identifier of the second bearer The information and the bandwidth allocated by the modified second bearer.
  • the interaction between the first network device and the second network device or the first network device control plane and the second network device may be relayed by the network controller.
  • the solution of the patent application can be compatible with the existing network system.
  • the UE is assigned a Cell Radio Network Temporary Identifier (C-RNTI) for air interface transmission to identify the connected state.
  • C-RNTI Cell Radio Network Temporary Identifier
  • the acquisition of the IP address of the UE is performed by the P-GW after the default bearer is established. Due to the existence of a large number of MTC terminals in the future, if an independent bearer is established for each terminal, the gateway may not be able to manage such a large amount of bearer contexts. The establishment of a large number of bearers is technically very challenging. How to assign an address to an MTC terminal is a problem.
  • the present patent application proposes that the first network device allocates the terminal in the process of terminal attachment.
  • the IP address of the terminal is assigned by the gateway to enable communication with the network.
  • the number of bits of the first identifier is less than the number of bits of the IP address.
  • the use of the first identifier to identify the terminal between the air interface and the base station and the first network device can reduce the air interface overhead. After the first network device receives the data of the air interface, the first identifier is restored to an IP address for transmission on the network.
  • the first network device allocates a unique ID, and obtains the terminal IP address by using a pre-established bearer between the first network device and the gateway.
  • the access only needs to be done once, and the user subscription information can be obtained, and the first identifier of the user is obtained, which provides a control basis for subsequent data transmission.
  • the first identifier allocated by the first network device to the terminal is used to uniquely identify a terminal within the first network device, by which the first network device can associate and manage terminal related data.
  • FIG. 11 is a schematic diagram of a method of attaching a terminal in accordance with an embodiment of the present patent application. As shown in FIG. 11, it includes the following steps:
  • the random access procedure may be a normal random access procedure or a random access procedure performed on an unlicensed resource.
  • the terminal sends an attach request (Attach Request) message to the base station by using the air interface resource.
  • the message can carry: the IMSI of the terminal, the MAC address, the attachment type, and the encryption option.
  • the base station receives the attach request, and does not parse the attach request.
  • the base station directly sends an attach request to the first network device by using the first bearer.
  • the attachment request may be added: base station ID or IP address information.
  • the first network device receives the attach request and parses the attach request.
  • the first network device sends an authentication request to the network controller.
  • the message name can also be a secure message or an attach request.
  • the message may carry: information about the base station where the terminal is currently located, identification information of the first network device, authentication information of the terminal, security information, and control policy.
  • the network controller After receiving the attach request, the network controller sends an attach response to the first network device.
  • the message name can also be a security response or an authentication response.
  • the attach response can carry: control policy, authentication encryption parameters, and possible gateway information.
  • the selected gateway information for the case where there may be multiple gateways.
  • the first network device receives an attach response from the network controller, and the first network device allocates the first identifier to the terminal.
  • the first network device sends an IP allocation request to the corresponding gateway.
  • the IP allocation request may carry: a permanent ID of the terminal.
  • the permanent ID can include an IMSI and a MAC address.
  • the gateway receives the IP allocation request, allocates an IP address to the terminal, and sends an IP allocation response to the first network device.
  • the allocation response may carry: the IP address of the gateway, the permanent ID of the terminal, the IP address assigned to the terminal, the ID or IP address of the base station to which the terminal belongs.
  • the first network device may establish a correspondence between the first identifier and the IP address in the first network device, where the correspondence includes uplink and downlink mapping.
  • the uplink mapping refers to that the data received from the base station is differentiated by the first identifier allocated by the first network device, and needs to be restored to a normal IP address.
  • the downlink mapping refers to data sent from the gateway to the first network device, and the first network device converts the IP address into the first identifier for transmission between the base station and the terminal in the air interface.
  • the first network device sends to the base station Send an attachment response.
  • the attach response may carry: a first network device ID or an IP address, a first identifier assigned by the first network device to the terminal, an IP address assigned by the gateway to the terminal, and an authentication encryption parameter.
  • the base station After receiving the attach response, the base station sends an attach response to the terminal.
  • the attach response sent to the terminal may carry: a first identifier assigned by the first network device to the terminal, an IP address assigned by the gateway to the terminal, and an authentication encryption parameter.
  • the first identity assigned by the first network device to the terminal may have orthogonality, such as a Zadoff-Chu (ZC) sequence. This can facilitate the base station to detect the terminal by using the first identifier.
  • ZC Zadoff-Chu
  • the length of the first identifier should be as short as possible to reduce the complexity of base station detection. However, the too short sequence reduces the number of supported terminals, so the first identifier assigned by the first network device should be a reasonable length.
  • the terminal can be classified into a static terminal, a slow mobile terminal, and a fast mobile terminal. Slow and fast are determined according to actual needs. If the moving speed is less than 5km/h, it is slow. If the moving speed is greater than or equal to 5km/h, it is fast.
  • a set of first identifiers can be pre-assigned for each type of terminal. When a first identifier is specifically allocated to a terminal, a first identifier selected from a group of first identifiers corresponding to attributes of the terminal may be allocated to the terminal. The first identifier for a static terminal or slow moving can be reused in different ranges. Fast mobile terminals need to be unique over a wider range.
  • FIG. 12 is a schematic illustration of a method of attachment by a terminal in accordance with another embodiment of the present patent application.
  • the main difference between FIG. 12 and FIG. 11 is that the base station directly sends an attach request to the network controller. As shown in FIG. 12, it includes the following steps:
  • the base station receives the attach request, parses the attach request, and parses the attach request to the network controller after parsing the attach request.
  • the attach request may carry: base station ID or IP address information, the IMSI of the terminal, the MAC address and the attachment type, and the encryption option.
  • the network controller After receiving the attach request, the network controller sends an IP allocation request to the gateway.
  • the IP allocation request may carry: a permanent ID of the terminal.
  • the permanent ID can include an IMSI, a MAC address.
  • the gateway receives the IP allocation request, allocates an IP address to the terminal, and sends an IP allocation response to the network controller.
  • the allocation response may carry: the IP address of the gateway, the permanent ID of the terminal, and the IP address assigned to the terminal.
  • the network controller After receiving the IP allocation response, the network controller sends an attach request to the control plane of the first network device, where the attach request may carry: a base station ID or an IP address, an IMSI of the terminal, a MAC address, an attachment type, an encryption option, and a terminal. IP address.
  • the first network device After receiving the attach request, the first network device allocates the first identifier to the terminal.
  • the first network device may also establish a correspondence between the first identifier and the IP address, where the correspondence includes uplink and downlink mapping.
  • the uplink mapping means that the data received from the base station is differentiated by the first identifier, and needs to be restored to a normal IP address.
  • the downlink mapping refers to data sent from the gateway to the user plane of the first network device, and the first network device converts the IP address into the first identifier for transmission between the base station and the terminal in the air interface.
  • the first network device After receiving the attach response, the first network device sends an attach response to the network controller.
  • the attach response may carry: a first identifier assigned by the first network device to the terminal and an IP address allocated by the gateway for the terminal site.
  • the network controller sends an attach response to the base station.
  • the attach response may carry: a first network device ID or an IP address, a first identifier assigned by the first network device to the terminal, an IP address assigned by the gateway to the terminal, and an authentication encryption parameter.
  • the process of attaching the terminal in the network is basically similar to the process under the architecture integrated by the first network device.
  • the first network device is divided into a control plane and a user plane, the control plane is used for terminal control information and policies, and the user plane is used for data transmission.
  • the terminal When the terminal is initially attached, it interacts with the control plane. Since the bearer is established between the user plane and the gateway, the allocation of the first identifier needs to be implemented by the first network device user plane. At the same time, the terminal's control information needs to be inserted into the control plane.
  • FIG. 13-15 are flow diagrams of three different embodiments in which a terminal is attached to a network under a separate architecture of the first network device.
  • the first identity of the terminal is assigned by the first network device user plane.
  • the base station parses the message and sends the message to the first network device control plane.
  • the base station does not parse the message, and directly sends it to the user plane of the first network device, and is parsed by the user of the first network device. If it is a control message, it is sent to the control plane of the first network device. Otherwise do forwarding processing.
  • the base station parses the message, and after parsing the attached message, sends the attached message to the network controller.
  • a method for attaching a terminal device in a network includes the following steps:
  • 1301 is the same as 1101.
  • 1302 is the same as 1102.
  • the base station receives the attach request, parses the attach request, and parses the attach request to the first network device control plane.
  • the attach request may carry: a base station ID or an IP address, an IMSI of the terminal, a MAC address, an attachment type, and an encryption option.
  • the first network device control plane receives the attach request and sends an authentication request to the network controller.
  • the message name can also be a secure message or an attach request.
  • the authentication request may carry: the current base station information of the terminal, the ID or IP address of the control plane of the first network device, the authentication information of the terminal, the security information, and the control policy.
  • the IP allocation request may carry: a permanent ID of the terminal.
  • the permanent ID can include an IMSI, a MAC address.
  • the gateway sends an IP allocation response to the first network device control plane.
  • the allocation response may carry: the IP address of the gateway, the permanent ID of the terminal, the IP address assigned to the terminal, the ID or IP address of the base station to which the terminal belongs, and the ID or IP address of the control plane of the first network device.
  • the first network device control plane selects a first network device user plane controlled by the first network device, and sends an attach request to the unauthorized user plane.
  • the attach request may carry: the IMSI of the terminal Or the MAC address, the IP address assigned by the gateway, the authentication encryption parameter, the control policy, and the ID or IP address of the base station where it is located.
  • the first network device user plane After receiving the attach request, the first network device user plane allocates a first identifier to the terminal.
  • the first network device user plane may also establish a correspondence between the first identifier and the IP address.
  • the first network device user sends an attach response to the first network device control plane.
  • the attach response may carry: the IMSI or MAC address of the terminal and the ID assigned to it, and the base station ID or IP address where it is located.
  • the first network device control plane sends an attach response to the base station after receiving the attach response of the user plane of the first network device.
  • the attach response may carry: a first identifier assigned by the user plane of the first network device to the terminal, and an IP address and an authentication encryption parameter allocated by the gateway for the terminal.
  • a method for attaching a terminal device in a network includes the following steps:
  • 1402 is the same as 1302.
  • the base station receives the attach request, does not parse the attach request, and directly sends the attach request to the first network device user plane for parsing.
  • the attach request may carry the ID or IP address of the user plane of the first network device, the IMSI of the terminal, the MAC address, the attachment type, and the encryption option.
  • the attach request may carry: a base station ID or an IP address, an IMSI of the terminal, a MAC address, and an attachment type. And encryption options.
  • the first network device control plane receives the attach request, and sends an attach request to the network controller, where the message name may also be a security message or an authentication request.
  • the attach request may carry: the current base station information of the terminal, the ID or IP address of the control plane of the first network device, the authentication information of the terminal, the security information, and the control policy.
  • a method for attaching a terminal device to a network includes the following steps:
  • 1502 is the same as 1302.
  • the base station receives the attach request, parses the attach request, and parses the attach request to the network controller.
  • the attach request may carry: a base station ID or an IP address, an IMSI of the terminal, a MAC address, Attachment type and encryption options.
  • the network controller After receiving the IP allocation response, the network controller sends an attach request to the control plane of the first network device, where the attach request may carry: a base station ID or an IP address, an IMSI of the terminal, a MAC address, an attachment type, an encryption option, and a gateway.
  • the IP address assigned to the terminal may carry: a base station ID or an IP address, an IMSI of the terminal, a MAC address, an attachment type, an encryption option, and a gateway.
  • the first network device control plane selects a first network device user plane controlled by the first network device, and sends an attach request to the unauthorized user plane.
  • This attach request is the same as the attach request in 1308.
  • the first network device control plane After receiving the attach response, the first network device control plane sends an attach response to the network controller.
  • the attach response may carry: a first identifier assigned by the user plane of the first network device to the terminal, and an IP address assigned by the gateway to the terminal.
  • the attach request may be transmitted on the bearer.
  • the present patent application also provides a machine type data transmission system including a first network.
  • Device 104 base station 102, and second network device 106.
  • the first network device in Figure 16 is an integrated architecture.
  • the above data transmission system can handle uplink and/or downlink data transmission.
  • the first network device 104 includes a first receiver 114a and a first transmitter 114b.
  • the first network device 104 can also include a first processor 114c.
  • the base station 102 includes a second receiver 112a and a second transmitter 112b.
  • the base station 102 can also include a second processor 112c.
  • the second network device 116 includes a third receiver 116a and a third transmitter 116b.
  • the second network device 116 can also include a third processor 116c.
  • the second receiver 112a receives data transmitted by the terminal from the air interface resource.
  • the second transmitter 112b transmits the data to the first receiver 114a of the first network device 104 via the pre-established first bearer 161.
  • the second processor 112c may select the first bearer 161 according to the first service attribute of the data.
  • the first service attribute is an attribute of the air interface resource.
  • the second transmitter 112b transmits data through the first bearer 161 corresponding to the attribute of the air interface resource used by the data.
  • the first receiver 114a receives data through the first bearer 161.
  • the first service attribute is a first quality of service feature.
  • the second transmitter 112b transmits data through the first bearer 161 corresponding to the first quality of service characteristic of the data.
  • the first receiver 114a receives data through the first bearer 161.
  • the first processor 114c may select the second bearer 162 according to the second service attribute of the data.
  • the second service attribute may be a second quality of service feature.
  • the first transmitter 114b transmits data to the second network device via the second bearer 162 corresponding to the second quality of service characteristic of the data.
  • the data received by the first receiver 114a through the first bearer 161 may carry the first identifier of the terminal.
  • the data transmitted by the first transmitter 114b through the second bearer 162 may carry the IP address of the terminal.
  • the first identifier of the terminal has a corresponding relationship with the IP address of the terminal.
  • the first processor 114c may acquire the IP address of the terminal through the first identifier of the terminal.
  • the data transmission system of this embodiment can also provide security control.
  • the first processor 114c also detects the suspect terminal according to the data, and notifies the first transmitter 114b after detecting the suspect terminal.
  • the specific method of detection can refer to some detection algorithms for malicious users.
  • the first transmitter 114b may send a security request to the second receiver 112a of the base station 102 via the first bearer 161.
  • the second receiver 112a notifies the second processor 112c after receiving the security request.
  • the second processor 112c of the base station 102 performs security processing on the suspect terminal.
  • the security processing may specifically include: blocking the data of the suspect terminal or re-authenticating the suspect terminal in the air interface.
  • the second processor 112c notifies the second transmitter 112b.
  • the second transmitter 112b transmits a security response to the first receiver 114a via the first bearer 161.
  • the first receiver 114a receives the security response.
  • the first receiver 114a also receives data transmitted by the third transmitter 116b from the pre-established second bearer 162. This data needs to be sent to a terminal in the system.
  • the third processor 116c may be based on the second service genus of the data.
  • the second bearer 162 is selected.
  • the second service attribute may be a second quality of service characteristic.
  • the first transmitter 114b transmits data to the second receiver 112a of the base station 102 via the pre-established first bearer 161.
  • the first processor 114c may select the first bearer 161 according to the first service attribute of the data.
  • the first service attribute is a first quality of service feature.
  • the first transmitter 114b transmits data through the first bearer 161 corresponding to the first quality of service characteristic of the data.
  • the second receiver 112a receives data through the first bearer 161.
  • the second processor 112c may select an appropriate air interface resource to transmit the data to the base station.
  • the first network device in FIG. 17 is a separate architecture.
  • the first network device 104 includes a first network device user plane 104c and a first network device control plane 104a.
  • the split architecture and the integrated architecture are basically similar.
  • the first receiver 114a, the first transmitter 114b, and the first processor 114c are specifically located within the first network device user plane 104c.
  • the first network device control plane 104a includes a fourth receiver 124a, a fourth transmitter 124b, and a fourth processor 124c.
  • the first transmitter 114b sends a security request to the fourth receiver 124a of the first network device control plane 104a after the first processor 114c detects the suspect terminal.
  • the fourth transmitter 124b sends a security request to the second receiver 112a.
  • the second receiver 112a receives the security request.
  • the second processor 112c takes security measures.
  • the second transmitter 112a also sends a security response to the fourth receiver 124a of the first network device control plane 104a.
  • the fourth receiver 124a receives the security Fully responding, sending a security response to the first receiver 114a.
  • system and “network” are used interchangeably herein.
  • the term “and/or” in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and / or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations.
  • the character "/" in this article generally indicates that the contextual object is an "or" relationship.
  • B corresponding to A means that B is associated with A, and B can be determined according to A.
  • determining B from A does not mean that B is only determined based on A, and that B can also be determined based on A and/or other information.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, or an electrical, mechanical or other form of connection.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present patent application.
  • each functional unit in each embodiment of the present patent application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • a portion of the solution that contributes intrinsically or to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for causing a A computer device (which may be a personal computer, a server, or a first network device, etc.) performs all or part of the steps of the methods described in various embodiments of the present patent application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a computer.
  • computer readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage media or other magnetic storage device, or can be used for carrying or storing in the form of an instruction or data structure.
  • connection may suitably be a computer readable medium.
  • the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair cable, digital terminating line (DSL), or wireless technologies such as infrared, radio, and microwave
  • coaxial cable , fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, wireless, and microwave
  • disks and discs include compact discs (CDs), laser discs, compact discs, digital versatile discs (DVDs), Floppy disks and Blu-ray discs, in which disks are usually magnetically replicated, while disks use lasers to optically replicate data. Combinations of the above should also be included within the scope of the computer readable media.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本专利申请公开了一种数据传输方法及***，第一网络设备与基站之间存在预先建立的一个或多个第一承载，第一网络设备与第二网络设备之间存在预先建立的一个或多个第二承载。该传输方法包括如下步骤：第一网络设备通过一个第一承载接收基站发送的数据。该数据是终端通过空口资源向基站发送的，用于接收该数据的第一承载与该数据的第一业务属性相对应。第一网络设备通过一个第二承载向第二网络设备发送数据，用于发送数据的第二承载与数据的第二业务属性相对应。

Description

一种数据传输方法及***
本申请要求于2015年11月30日提交中国专利局、申请号为201510859746.2、发明名称为“一种数据传输方法及***”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本专利申请涉及无线通信，更为具体地，涉及一种数据传输方法及***。
背景技术
下一代移动通信***将支持机器对机器(Machine to Machine，简称为“M2M”)或者称为机器类型通信(Machine Type Communication，简称“MTC”)。根据预测，到2020年，连接在网络上的MTC设备将会达到500到1000亿，这将远超现在的连接数量。
在M2M应用中，MTC设备的数量庞大，大量MTC设备如果接入网络竞争网络资源，会给现有网络带来新的负担。目前尚未有合适这些MTC设备进行数据传输的方案。
发明内容
有鉴于此，本专利申请提供了一种数据传输方法及***，适用于MTC设备。
第一方面，本专利申请提供了一种数据传输方法。该传输方法中，第一网络设备与基站之间存在预先建立的一个或多个第一承载，第一网络设备与第二网络设备之间存在预先建立的一个或多个第二承载。该方法包括如下步骤：第一网络设备通过一个第一承载接收基站发送的数据。该数据是终端通过空口资源向基站发送的，用于接收 该数据的第一承载与该数据的第一业务属性相对应。第一网络设备通过一个第二承载向第二网络设备发送数据，用于发送数据的第二承载与数据的第二业务属性相对应。
由于第一网络设备与基站之间存在预先建立的一个或多个第一承载，第一网络设备与第二网络设备之间存在预先建立的一个或多个第二承载，终端发给基站的数据可以直接在第一、二承载上发送。这避免了承载的建立、删除所需的信令过程以及由此产生的时延。这有效地提高了网络业务处理效率。
第一承载与数据的业务属性相对应，第二承载与数据的第二业务属性相对应。第一承载和第二承载无需与每个终端对应，本专利申请使用有限的承载可以解决大量终端数据传输的问题，避免大量终端的承载信令过程以及由此产生的时延。这有效地提高了网络业务处理效率。
在第一方面的第一种可能的实现方式中，该第一承载是该基站或该第一网络设备初始化时建立的。
结合第一方面或第一方面的第一种可能的实现方式，在第二种可能的实现方式中，该第二承载是该基站或该第一网络设备初始化时建立的。
在初始化时，建立第一、二承载，终端在附着时也可以直接使用已建立的第一承载和第二承载,进一步提高网络业务处理效率。
结合第一方面或第一方面的第一种可能的实现方式，在第三种可能的实现方式中，该第二网络设备是服务器，该第二承载是该服务器初始化时建立的。这样可以通过互联网向用户提供各种应用服务，使得网络能够支持OTT(over the top)的业务能力，尤 其在未来网络支持网络切片时，提供了一种垂直业务能力。
结合第一方面或第一方面的第一至三种可能的实现方式，在第四种可能的实现方式中，第一业务属性为空口资源的属性，用于接收数据的第一承载与数据所使用的空口资源的属性相对应。通过数据所使用的空口资源的属性选择相应的第一承载，可以简化数据处理过程。
结合第一方面或第一方面的第一至三种可能的实现方式，在第五种可能的实现方式中，第一业务属性为第一服务质量特性，用于接收数据的第一承载与数据的第一服务质量特性相对应。通过数据的第一服务质量特性选择相应的第一承载，可以简化数据处理过程。
结合第一方面或第一方面的第一至五种可能的实现方式，在第六种可能的实现方式中，第二业务属性为第二服务质量特性，该方法还包括：第一网络设备通过数据的第二服务质量特性确定用于发送数据的第二承载。通过数据的第二服务质量特性选择相应的第二承载，可以简化数据处理过程。
结合第一方面或第一方面的第一至六种可能的实现方式，在第七种可能的实现方式中，通过第一承载接收的数据携带终端的第一标识，第一网络设备根据终端的第一标识与终端的IP地址之间的对应关系获取终端的IP地址；第一网络设备在向第二网络设备发送的数据中携带终端的IP地址。该第一标识使得基站和第一网络设备在其管理域内可以准确区别各个终端。这为在第一承载和空口进行数据传输时不携带IP地址提供了可能。
结合第一方面的第七种可能的实现方式，在第八种可能的实现方式中，第一标识的位数小于IP地址的位数。这样在空口和第一承载上可以仅用第一标识对终端进行识别，降低空口开销。
结合第一方面的第一至八种可能的实现方式，在第九种可能的实现方式中，该方法还包括第一网络设备通过数据检测到嫌疑终端后向基站发送安全请求；第一网络设备接收基站发送的安全响应。采用这种安全机制，可以避免某些恶意终端不断发送消息，导致***阻塞。
结合第一方面的第一至八种可能的实现方式，在第十种可能的实现方式中，第一网络设备包括第一网络设备用户面和第一网络设备控制面，第一网络设备具体为第一网络设备用户面。通过用户面与控制面分离的架构，对数据的处理仅由用户面操作，可以进一步简化网络处理，提高网络处理效率。
第二方面，本专利申请提供了一种第一网络设备，第一网络设备与基站之间存在预先建立的一个或多个第一承载；第一网络设备与第二网络设备之间存在预先建立的一个或多个第二承载。第一网络设备包括第一接收器和第一发送器。第一接收器通过一个第一承载接收基站发送的数据，数据是终端通过空口资源向基站发送的，用于接收数据的第一承载与数据的第一业务属性相对应。第一发送器通过一个第二承载向第二网络设备发送数据，用于发送数据的第二承载与数据的第二业务属性相对应。
在第二方面的第一种可能的实现方式中，第一承载和第二承载是第一网络设备初始化时建立的。
结合第二方面与第二方面的第一种可能的实现方式，在第二种可能的实现方式中，第一业务属性为空口资源的属性，用于接收数据的第一承载与数据所使用的空口资源的属性相对应。
结合第二方面与第二方面的第一种可能的实现方式，在第三种可能的实现方式中，第一业务属性为第一服务质量特性，用于接收数据的第一承载与数据的第一服务质量特性相对应。
结合第二方面与第二方面的第一至三种可能的实现方式，在第四种可能的实现方式中，第二业务属性为第二服务质量特性，第一网络设备还包括第一处理器，第一处理器通过数据的第二服务质量特性确定用于发送数据的第二承载。
结合第二方面与第二方面的第一至四种可能的实现方式，在第五种可能的实现方式中，通过第一承载接收的数据携带终端的第一标识；第一处理器还根据终端的第一标识与终端的IP地址之间的对应关系获取终端的IP地址，第一发送器向第二网络设备发送的数据中携带终端的IP地址。
结合第二方面的第五可能的实现方式，在第六种可能的实现方式中，第一标识的位数小于IP地址的位数。
结合第二方面的第五或六种可能的实现方式，在第七种可能的实现方式中，第一处理器还用于检测嫌疑终端；第一发送器还用于在第一处理器检测到嫌疑终端后向基站发送安全请求，第一接收器还用于接收基站发送的安全响应。
第三方面，本专利申请提供了一种数据传输方法，第一网络设备与基站之间存在 预先建立的一个或多个第一承载。该方法包括如下步骤：基站从空口资源上接收终端发送的数据；基站通过一个第一承载向第一网络设备发送该数据，用于发送该数据的第一承载与该数据的第一业务属性相对应。
在第三方面的第一种可能的实现方式中，该第一承载是该基站或该第一网络设备初始化时建立的。
结合第三方面或第三方面的第一种可能的实现方式，在第二种可能的实现方式中，第一业务属性为空口资源的属性，该方法还包括：基站通过数据的空口资源的属性选择相应的第一承载。
结合第三方面或第三方面的第一种可能的实现方式，在第三种可能的实现方式中，第一业务属性为第一服务质量特性，该方法还包括：基站通过数据的第一服务质量特性选择相应的第一承载。
结合第三方面或第三方面的第一至三种可能的实现方式，在第四种可能的实现方式中，该方法还包括：基站接收第一网络设备发送的安全请求，安全请求携带嫌疑终端的身份标识；基站对嫌疑终端进行安全处理；基站向第一网络设备发送安全响应，安全响应携带已进行安全处理的终端的身份标识。
第四方面，本专利申请提供了一种基站，第一网络设备与基站之间存在预先建立的一个或多个第一承载。该基站包括第二接收器和第二发送器。第二接收器从空口资源上接收终端发送的数据；第二发送器通过一个第一承载向第一网络设备发送该数据，用于发送该数据的第一承载与该数据的第一业务属性相对应。
在第四方面的第一种可能的实现方式中，该第一承载是该基站或该第一网络设备初始化时建立的。
结合第四方面或第四方面的第一种可能的实现方式，在第二种可能的实现方式中，第一业务属性为空口资源的属性，该基站还包括第二处理器，用于通过数据的空口资源的属性选择相应的第一承载。
结合第四方面或第四方面的第一种可能的实现方式，在第三种可能的实现方式中，第一业务属性为第一服务质量特性，该基站还包括第二处理器，用于通过数据的第一服务质量特性选择相应的第一承载。
结合第四方面的第二、三种可能的实现方式，在第四种可能的实现方式中，第二接收器还接收第一网络设备发送的安全请求，安全请求携带嫌疑终端的身份标识；第二处理器对嫌疑终端进行安全处理；第二发送器向第一网络设备发送安全响应，安全响应携带已进行安全处理的终端的身份标识。
第五方面，本专利申请提供了一种数据传输方法，第一网络设备与基站之间存在预先建立的一个或多个第一承载，第一网络设备与第二网络设备之间存在预先建立的一个或多个第二承载。该方法包括如下步骤：第一网络设备通过一个第二承载接收第二网络设备发送的数据。用于接收该数据的第二承载与该数据的第二业务属性相对应。第一网络设备通过一个第一承载向基站发送数据，用于发送数据的第一承载与数据的第一业务属性相对应。
在第五方面的第一种可能的实现方式中，该第一承载是该基站或该第一网络设备初始化时建立的。
结合第五方面或第五方面的第一种可能的实现方式，在第二种可能的实现方式中，该第二承载是该基站或该第一网络设备初始化时建立的。
结合第五方面或第五方面的第一种可能的实现方式，在第三种可能的实现方式中，该第二网络设备是服务器，该第二承载是该服务器初始化时建立的。
结合第五方面或第五方面的第一至三种可能的实现方式，在第四种可能的实现方式中，第一业务属性为空口资源的属性，该第一网络设备通过数据的空口资源的属性确定用于发送数据的第一承载。
结合第五方面或第五方面的第一至三种可能的实现方式，在第五种可能的实现方式中，第一业务属性为第一服务质量特性，该第一网络设备通过数据的第一服务质量特性确定用于发送数据的第一承载。
结合第五方面或第一方面的第一至五种可能的实现方式，在第六种可能的实现方式中，第二业务属性为第二服务质量特性，用于接收数据的第一承载与数据的第二服务质量特性相对应。
结合第五方面或第五方面的第一至六种可能的实现方式，在第七种可能的实现方式中，通过第二承载接收的数据携带终端的IP地址，第一网络设备根据终端的IP地址与终端的第一标识之间的对应关系获取终端的第一标识；第一网络设备在向第二网络设备发送的数据中携带终端的第一标识。第一标识的位数小于IP地址的位数。
第六方面，本专利申请提供了一种第一网络设备，第一网络设备与基站之间存在预先建立的一个或多个第一承载，第一网络设备与第二网络设备之间存在预先建立的一个或多个第二承载。第一网络设备包括第一接收器和第一发送器。第一接收器通过一个第二承载接收第二网络设备发送的数据。用于接收该数据的第二承载与该数据的第二业务属性相对应。第一发送器通过一个第一承载向基站发送数据，用于发送数据的第一承载与数据的第一业务属性相对应。
在第六方面的第一种可能的实现方式中，第一承载和第二承载是第一网络设备初始化时建立的。
结合第六方面与第六方面的第一种可能的实现方式，在第三种可能的实现方式中，第一业务属性为空口资源的属性，第一网络设备还包括第一处理器，第一处理器通过数据的空口资源的属性确定用于发送数据的第一承载。
结合第六方面与第六方面的第一种可能的实现方式，在第四种可能的实现方式中，第一业务属性为第一服务质量特性，第一网络设备还包括第一处理器，第一处理器通过数据的第一服务质量特性确定用于发送数据的第一承载。
结合第六方面与第六方面的第一至四种可能的实现方式，在第五种可能的实现方式中，第二业务属性为第二服务质量特性，用于接收数据的第一承载与数据的第二服务质量特性相对应。
结合第六方面的第三至四种可能的实现方式，在第六种可能的实现方式中，通过第二承载接收的数据携带终端的IP地址，第二处理器根据终端的IP地址与终端的第 一标识之间的对应关系获取终端的第一标识；第二发送器在向第二网络设备发送的数据中携带终端的第一标识。第一标识的位数小于IP地址的位数。
第七方面，本专利申请提供了一种数据传输方法，第一网络设备与基站之间存在预先建立的一个或多个第一承载。该方法包括如下步骤：基站通过一个第一承载接收第一网络设备发送的数据。用于接收该数据的第一承载与该数据的第一业务属性相对应。基站通过空口资源向终端发送数据。
在第七方面的第一种可能的实现方式中，该第一承载是该基站或该第一网络设备初始化时建立的。
结合第七方面或第七方面的第一种可能的实现方式，在第二种可能的实现方式中，第一业务属性为空口资源的属性，用于接收数据的第一承载与数据的空口资源的属性相对应。
结合第七方面或第七方面的第一种可能的实现方式，在第三种可能的实现方式中，第一业务属性为第一服务质量特性，用于接收数据的第一承载与数据的第一服务质量特性相对应。
第八方面，本专利申请提供了一种基站，第一网络设备与基站之间存在预先建立的一个或多个第一承载。基站包括第二接收器和第二发送器。第二接收器通过一个第一承载接收第一网络设备发送的数据。用于接收该数据的第一承载与该数据的第一业务属性相对应。第二发送器通过通过空口资源向终端发送数据。
在第八方面的第一种可能的实现方式中，第一承载是基站初始化时建立的。
结合第八方面或第八方面的第一种可能的实现方式，在第二种可能的实现方式中，第一业务属性为空口资源的属性，用于接收数据的第一承载与数据的空口资源的属性相对应。
结合第八方面或第八方面的第一种可能的实现方式，在第三种可能的实现方式中，第一业务属性为第一服务质量特性，用于接收数据的第一承载与数据的第一服务质量特性相对应。
第九方面，本专利申请提出了一种承载的建立方法，包括：在第一网络设备初始化时，第一网络设备向基站发送第一承载建立请求，第一承载建立请求中携带：第一网络设备的标识信息和请求创建的第一承载信息；第一网络设备接收基站发送的第一承载建立响应，第一承载建立响应中携带：基站分配的第一承载信息；第一网络设备向第二网络设备发送第二承载建立请求，第二承载建立请求中携带：第一网络设备的标识信息和请求创建的第二承载信息；第一网络设备接收第二网络设备发送的第二承载建立响应；第二承载建立响应中携带：第二承载的标识信息和创建的第二承载信息。
在第九方面的第一种可能的实现方式中，该方法还包括：第一网络设备向第二网络设备发送第二承载修改请求，第二承载修改请求中携带：请求修改的第二承载带宽；第一网络设备接收第二网络设备发送的第二承载修改响应；第二承载修改响应中携带：修改后的第二承载所分配的带宽。
结合第九方面或第九方面的第一种可能的实现方式，在第二种可能的实现方式 中，该方法还包括：第一网络设备向基站发送第一承载建立完成信息，第一承载建立完成信息中携带：建立完成的第一承载的标识信息、第一网络设备标识信息和基站的标识信息。
结合第九方面或第九方面的第一至二种可能的实现方式，在第三种可能的实现方式中，第一网络设备包括第一网络设备用户面和第一网络设备控制面，第一网络设备具体为第一网络设备控制面，该方法还包括：第一网络设备控制面向第一网络设备用户面发送第一承载建立请求，第一承载建立请求中携带：基站的标识和基站所分配的第一承载信息，第一网络设备控制面接收第一网络设备用户面发送的第一承载建立响应，第一承载建立响应中携带：第一网络设备用户面的标识、基站的标识和第一网络设备用户面所分配的第一承载信息；第一网络设备控制面向第一网络设备用户面发送第一承载建立完成消息，第一承载建立完成消息中携带：基站的标识和建立完成的第一承载信息。
结合第九方面的第三种可能的实现方式，在第四种可能的实现方式中，该方法还包括：第一网络设备控制面向第一网络设备用户面发送第二承载建立请求，第二承载建立请求中携带：第一网络设备控制面标识和第一网络设备用户面标识；第一网络设备控制面接收第一网络设备用户面发送的第二承载建立响应，第二承载建立响应中携带：第一网络设备用户面的标识和第一网络设备用户面所分配的第二承载信息；第一网络设备控制面向第一网络设备用户面发送第二承载建立完成消息，第二承载建立响应中携带：建立完成的第二承载信息。
第十方面，本专利申请提出了一种第一网络设备，包括：相互耦合的处理器和存储器，存储器中存有指令，处理器执行该指令以完成第九方面的承载的建立方法。
第十一方面，本专利申请提出了一种承载的建立方法，包括：基站接收第一网络设备发送的第一承载建立请求，第一承载建立请求中携带：第一网络设备的标识信息、请求创建的第一承载信息；基站向第一网络设备发送第一承载建立响应，第一承载建立响应中携带：基站分配的第一承载信息。
在第十一方面的第一种可能的实现方式中，该方法还包括：基站接收第一网络设备发送的第一承载建立完成信息，第一承载建立完成信息中携带：创建的第一承载的标识。
第十二方面，本专利申请提出了一种基站，包括：相互耦合的处理器和存储器，存储器中存有指令，处理器执行该指令以完成第十一方面的承载的建立方法。
第十三方面，本专利申请提出了一种承载的建立方法，包括：在基站初始化时，第一网络设备接收基站发送的第一承载建立请求，第一承载建立请求中携带：基站的标识信息、请求创建的第一承载信息；第一网络设备向基站发送第一承载建立响应，第一承载建立响应中携带：创建的第一承载信息。
在第十三方面的第一种可能的实现方式中，方法还包括：第一网络设备向网关发送第二承载建立请求，第二承载建立请求中携带：第一网络设备的标识信息、请求创建的第二承载信息；第一网络设备接收网关发送的第二承载建立响应；第二承载建立响应中携带：第二承载的标识信息、创建的第二承载信息。
在第十三方面的第一种可能的实现方式中，方法还包括：第一网络设备向网关发送第二承载修改请求，第二承载修改请求中携带：请求的带宽；第一网络设备接收网关发送的第二承载修改响应；第二承载修改响应中携带：第二承载的标识信息、修改后的第二承载所分配的带宽。
第十四方面，本专利申请提出了一种第一网络设备，包括相互耦合的处理器和存储器，存储器中存有指令，处理器执行该指令以完成第十三方面的承载的建立方法。
第十五方面，本专利申请提出了一种承载的建立方法，在基站初始化时，基站向第一网络设备发送第一承载建立请求，第一承载建立请求中携带：基站的标识信息、请求创建的第一承载信息；基站接收第一网络设备发送的第一承载建立响应，第一承载建立响应中携带：第一网络设备分配的第一承载信息。
在第十五方面的第一种可能的实现方式中，该方法还包括：基站接收第一网络设备发送的第一承载建立完成信息，第一承载建立完成信息中携带：创建的第一承载的标识。
第十六方面，本专利申请提出了一种基站，包括相互耦合的处理器和存储器，存储器中存有指令，处理器执行该指令以完成第十五方面的承载的建立方法。
第十七方面，本专利申请提出了一种终端在网络中附着的方法，包括：基站接收终端发送的附着请求；基站向第一网络设备发送附着请求，以使第一网络设备为终端分配第一标识；基站接收第一网络设备发送的附着响应；基站向终端发送附着响应；附着响应中携带：终端的第一标识。
在第十七方面的第一种可能的实现方式中，附着响应中还携带：终端的IP地址，终端的第一标识与终端的IP地址具有对应关系。终端第一标识的位数小于终端的IP地址的位数。
第十八方面，本专利申请提出了一种基站，包括相互耦合的处理器和存储器，存储器中存有指令，处理器执行该指令以完成第十七方面的附着方法。
第十九方面，本专利申请提出了一种终端在网络中附着的方法，包括：第一网络设备接收基站发送的附着请求，附着请求是终端向基站发送的；第一网络设备为终端分配第一标识；第一网络设备向基站发送附着响应，以使基站向终端发送附着响应；附着响应中携带：终端的第一标识。
在第十九方面的第一种可能的实现方式中，附着响应中还携带：第一网络设备从网关获取终端的IP地址，附着响应中还携带：终端的IP地址，终端的第一标识与终端的IP地址具有对应关系。
结合第十九方面的第一种可能的实现方式中，在第二种可能的实现方式中，该方法还包括：第一网络设备建立终端的第一标识与IP地址的对应关系。
第二十方面，本专利申请提出了一种第一网络设备，包括相互耦合的处理器和存储器，存储器中存有指令，处理器执行该指令以完成第十九方面的附着方法。
第二十一方面，本专利申请提出了一种终端在网络中附着的方法，包括：终端向基站发送附着请求；终端接收基站发送的附着响应，附着响应中携带：终端的第一标识。
在第二十一方面的第一种可能的实现方式中，第一标识是第一网络设备分配的并与终端的IP地址有对应关系。
第二十二方面，本专利申请提出了一种终端，包括相互耦合的处理器和存储器，存储器中存有指令，处理器执行该指令以完成第二十一方面的附着方法。
本专利申请中，数据传输中使用的第一承载和第二承载是预先建立的，其在数据传输后继续保留以供下次传输，其不会随着单次数据传输的结束而删除。第一承载和第二承载仅需建立一次即可。第一承载和第二承载是根据业务属性建立的，与终端的数量无关。第一承载和第二承载的数量分别都小于基站所管辖的终端的数量。使用有限的承载可以解决大量终端数据传输的问题，避免承载信令过程以及由此产生的时延。这有效地提高了网络业务处理效率。
附图说明
为了更清楚地说明本专利申请实施例的技术方案，下面将对本专利申请实施例中所需要使用的附图作简单地介绍，显而易见地，下面所描述的附图仅仅是本专利申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获取其他的附图。
图1是根据本专利申请一个实施例的网络***的架构的示意图。
图2是根据本专利申请另一个实施例的网络***的架构的示意图。
图3是根据本专利申请一个实施例，一种机器类型的数据上行传输方法的示意图。
图4是根据本专利申请另一个实施例，一种机器类型的数据下行传输方法的示意 图。
图5是根据本专利申请另一个实施例，在第一网络设备集成架构下，一种数据传输方法的示意图。
图6是根据本专利申请另一个实施例，在第一网络设备分离架构下，一种数据传输方法的示意图。
图7是在第一网络设备集中式架构下，第一网络设备初始化的情况下，一种建立承载的方法的交互示意图。
图8是在第一网络设备分离式架构下，第一网络设备初始化的情况下，一种建立承载的方法的交互示意图。
图9是在第一网络设备集中式架构下，基站初始化的情况下，一种建立承载的方法的交互示意图。
图10是在第一网络设备分离式架构下，基站初始化的情况下，一种建立承载的方法的交互示意图。
图11-12是在第一网络设备集成的架构下，终端在网络中附着的两个不同实施例的流程示意图。
图13-15是在第一网络设备分离的架构下，终端在网络中附着的三个不同实施例的流程示意图。
图16是是根据本专利申请一个实施例，一种机器类型的数据传输***的示意图。
图17是是根据本专利申请另一个实施例，一种机器类型的数据传输***的示意 图。
具体实施方式
下面将结合本专利申请实施例中的附图，对本专利申请实施例中的技术方案进行清楚地描述，显然，所描述的实施例是本专利申请的一部分实施例，而不是全部实施例。基于本专利申请中的实施例，本领域普通技术人员在没有做出创造性劳动的前提下所获取的所有其他实施例，都应属于本专利申请保护的范围。
本专利申请中，术语“第一”等是用于区别类似的对象，“第一”只是特指了某一个或某一类的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，这仅仅是描述本专利申请的实施例中对相同属性的对象在描述时所采用的区分方式。“一”或“一个”不排除多个的情况。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，以便包含一系列单元的过程、方法、***、产品或设备不必限于那些单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它单元。
本专利申请所涉及到的终端可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的用户设备(User Equipment，简称UE)，移动台(Mobile station，简称MS)，终端设备(Terminal Equipment)等等。为方便描述，本专利申请中，上面提到的设备统称为终端或UE。
本专利申请所涉及到的基站(Base Station，简称BS)是一种部署在无线接入网中用以为UE提供无线通信功能的装置。所述基站可以包括各种形式的宏基站，微基站，中继站，接入点等等。在采用不同的无线接入技术的***中，具备基站功能的设备的名称可能会有所不同，例如在LTE网络中，称为演进的节点B(evolved NodeB简称：eNB或者eNodeB)，在第三代3G网络中，称为节点B(Node B)等等。为方便描述，本专利申请中，上述为UE提供无线通信功能的装置统称为基站或BS。
本专利申请中网关可以包括业务网关(Serving Gateway，简称S-GW)或分组数据网关(Packet Data Network GateWay，简称P-GW)或其他具有网关功能的网络节点。
免授权传输可以理解为如下含义的任一一种含义，或，多种含义，或者多种含义中的部分技术特征的组合或其他类似的含义：
免授权传输可以指：在公用陆地移动网(Public Land Mobile Network，简称PLMN)网络中，不需要第一网络设备或者云/集成无线接入网(Cloud/Centralized Radio Access Network，简称CRAN)场景下的无线控制器动态调度即可实现终端数据上行传输的方法。动态调度是指网络为UE的每次上行传输通过信令指配当前接收信令时刻的以后传输时间间隔(Transmission Time Interval，简称TTI)以后的传输资源，传输时间间隔是指一次上行传输的最小时间单元，如1ms。
免授权传输可以指：终端根据传输数据的特点的不同，如传输时延或可靠性的要求，在指定的时频资源上，采用该时频资源所能支持的包括码资源、导频资源、调制编码方案、反馈类别、分集方式等进行数据传输的方式以减少网络信令和/或减小传输 时延。
免授权传输可以指：第一网络设备预先分配并告知终端设备多个传输资源；终端设备有上行数据传输需求时，从第一网络设备预先分配的多个传输资源中选择至少一个传输资源，使用所选择的传输资源发送上行数据；第一网络设备在所述预先分配的多个传输资源中的传输资源上检测终端设备发送的上行数据。所述检测可以是盲检测，也可能根据所述上行数据中某一个控制域进行检测，或者是其他方式进行检测。
免授权传输可以指：第一网络设备预先分配并告知终端设备多个传输资源，以使终端设备有上行数据传输需求时，从第一网络设备预先分配的多个传输资源中选择至少一个传输资源，使用所选择的传输资源发送上行数据。
免授权传输可以指：获取预先分配的多个传输资源的信息，在有上行数据传输需求时，从所述多个传输资源中选择至少一个传输资源，使用所选择的传输资源发送上行数据。获取的方式可以从第一网络设备获取。
免授权传输可以指：不需要第一网络设备动态调度即可实现终端设备的上行数据传输的方法，所述动态调度可以是指第一网络设备为终端设备的每次上行数据传输通过信令来指示传输资源的一种调度方式。可选地，实现终端设备的上行数据传输可以理解为允许两个或两个以上终端设备的数据在相同的时频资源上进行上行数据传输。可选地，所述传输资源可以是UE接收所述的信令的时刻以后的传输时间单位的传输资源。一个传输时间单位可以是指一次传输的最小时间单元，比如TTI(Transmission Time Interval)，数值可以为1ms，或者可以是预先设定的传输时间单元。
免授权传输可以指：终端设备在不需要第一网络设备授权的情况下进行上行数据传输。所述授权可以指终端设备发送上行调度请求给第一网络设备，第一网络设备接收调度请求后，向终端设备发送上行授权，其中所述上行授权指示分配给终端设备的上行传输资源。
免授权传输可以指：一种竞争传输方式，具体地可以指多个终端在预先分配的相同的时频资源上同时进行上行数据传输，而无需基站进行授权。
所述盲检测可以理解为在不预知是否有数据到达的情况下，对可能到达的数据进行的检测。所述盲检测也可以理解为没有显式的信令指示下的检测。
所述空口资源是指用于终端进行空口上传输的资源。
所述第一网络设备是与基站进行数据传输的网络侧的通信设备。所述第一网络设备还对所述数据进行处理。
所述传输资源可以包括但不限于如下资源的一种或多种的组合：
-时域资源，如无线帧、子帧、符号等；
-频域资源，如子载波、资源块等；
-空域资源，如发送天线、波束等；
-码域资源，如稀疏码多址接入(Sparse Code Multiple Access，简称为“SCMA”)码本、低密度签名(Low Density Signature，简称为“LDS”)序列、CDMA码等；
-上行导频资源。
如上的传输资源可以根据包括但不限于如下的控制机制进行的传输：
-上行功率控制，如上行发送功率上限控制等
-调制编码方式设置，如传输块大小、码率、调制阶数设置等；
-重传机制，如HARQ机制等。
所述第一网络设备是指接收来自基站或发送给基站的免授权传输的数据，并对所述免授权传输的数据进行处理的通信设备，竞争传输单元(Contention Transmission Unit，简称为“CTU”)可以为免授权传输的基本传输资源。CTU可以指时间、频率、码域相结合的传输资源，或者，可以指时间、频率、导频相结合的传输资源，或者，可以指时间、频率、码域、导频相结合的传输资源。
CTU的接入区域可以指用于免授权传输的时频区域，进一步可以指CTU对应的时频区域。
本专利所有实施例中的网络实体名称可以扩展为具有相同或类似功能的名称。
本专利申请中，关于方法的介绍中，对各个步骤进行了标号。但这不代表各个步骤需要按照标号的顺序先后执行。本领域技术人员可以在不付出创造性劳动的前提下，对各个步骤的先后顺序进行调整。
专利申请号为PCT/CN2014/073084、专利申请名称为“System and Method for Uplink Grant-free Transmission Scheme”的专利申请给出了一种上行免授权传输的技术方案。在该专利申请中，将无线资源划分为各种不同大小的竞争传输单元(Contention Transmission Unit，简称CTU)，终端设备被映射到某个CTU。每个CTU被分配一组码，所分配的码可以是码分多址接入(Code Division Multiple Access， 简称CDMA)码，也可以是稀疏码多址接入(Sparse Code Multiple Access，简称SCMA)或低密度签名(Low Density Signature，简称LDS)或签名(signature)等。每一个码对应一组导频。终端可以选择一个码以及与该码对应的导频组中的一个导频进行上行传输。
PCT/CN2014/073084的专利申请内容也可以理解为通过引用作为本专利申请实施例内容的一部分，不再赘述。PCT/CN2014/073084主要针对空口传输，其并没有提到网络侧应该如何处理。本专利申请可以解决网络侧的处理并提高网络业务处理效率。
在LTE***中，为保持UE永久在线，会为每个UE建立一条从P-GW到S-GW的默认承载。当UE请求业务传输时，移动管理实体(Mobility Management Entity，简称MME)会向eNB(enhanced NodeB)发送初始上下文建立请求(Initial context Setup Request)以建立基站到S-GW以及空口的承载。
由于未来MTC业务数量巨大，接入到一个基站的终端数可能在30万或更多。某些MTC终端传输数据的频度以及数据包可能很小。由于传输频度小，MTC终端进行一次传输后，即会进入空闲态。下次传输的时候，就需要通过随机接入过程进行传输。由于大量终端的存在，将导致***会产生大量的随机接入过程，极大消耗了***资源，尤其是占用了大量的信令资源，可能会导致其他正常的大数据量传输业务受到影响。
而对某些MTC类业务，对时延要求比较高，比如车联网业务。如果通过传统的调度请求过程来进行传输，会造成很大的时延而不能满足业务要求。
当未来网络***中的UE数目极大增加时，为每个UE建立默认承载将极大消耗系 统资源，甚至导致P-GW上的上下文(context)资源不够。此外，每次UE进行传输时，都需要为该UE建立空口以及基站到S-GW的承载，这将极大地消耗***信令资源，增加***负荷。
认识到这些问题后，提出了本专利申请的一种数据传输方法和***。
接下来首先介绍本专利申请实施例的架构。图1是根据本专利申请一个实施例的网络***的架构的示意图。如图1所示，网络***包括第一网络设备104、网关(GateWay，简称GW)106、网络控制器(Network Controller，简称NC)108、多个基站(Evolved Node B，简称eNB)102。每个基站102管辖其下的大量终端。
在本实施例中，第一网络设备104是集中式架构，其既可以负责控制面的处理也负责用户面的处理，如数据传输。
第一网络设备104可以和多个基站102相连，服务于该多个基站102下的终端。第一网络设备104还可以和网络控制器108相连，第一网络设备可以从网络控制器获取终端信息，如策略控制信息。网络控制器108可以包括移动管理实体(mobility management entity，简称MME)、策略和计费规则功能(Policy Charging and Rule Function，简称PCRF)或归属终端服务器(Home Subscriber Server，简称HSS)。
第一网络设备104还可以和网关106相连。第一网络设备具有唯一的标识其身份的ID，该ID可以是第一网络设备的IP地址。
本专利申请实施例的网络可以是指公共陆地移动网络(Public Land Mobile Network，简称为“PLMN”)或者设备对设备(Device to Device，简称为“D2D”)网 络或者M2M网络或者其他网络，图1只是举例的简化示意图，网络中还可以包括其他第一网络设备，图1中未予以示出。
第一网络设备104可以是一个物理实体，也可以说一个功能实体。当其是功能实体时，其在物理上可以跟网络控制器或S_GW或其他网络设备部署在一起。
第一网络设备与基站之间存在预先建立的一个或多个第一承载。第一网络设备与第二网络设备之间存在预先建立的一个或多个第二承载。
图2是根据本专利申请另一个实施例的网络***的架构的示意图。在本实施例中，网络采用控制面/用户面(Control plane/User Plane，简称“C/U”)分离的架构。控制面集中进行控制，用户面完成数据转发。如图2所示，网络***包括第一网络设备、网关106、网络控制器108、多个基站102。第一网络设备是分离式架构，其包含第一网络设备控制面104a和第一网络设备用户面104c。
第一网络设备控制面104a和第一网络设备用户面104c分别可以和多个基站相连。在第一网络设备分离式架构下，一个第一网络设备控制面可以和第一网络设备用户面相连，不同的第一网络设备用户面可以支持多种业务，也可以分别支持不同的业务类别，比如一个第一网络设备用户面(User Plane)支持低延迟、高可靠业务，一个第一网络设备用户面支持延迟可容忍的可靠传输业务。
请参考图3、4，图3是根据本专利申请一个实施例，进行上行数据传输的一种数据传输方法的示意图。图4是根据本专利申请另一个实施例，进行数据传输的一种数据传输方法的示意图。上行数据传输和下行数据传输可以分别进行，也可以同时进行。 在关于图3和图4的描述中，第一网络设备可以指代第一网络设备集中式架构下的第一网络设备或者是第一网络设备分离式架构下的第一网络设备用户面。
如图3所示，一种数据传输方法。该传输方法的应用场景包括：第一网络设备与基站之间存在预先建立的一个或多个第一承载，第一网络设备与第二网络设备之间存在预先建立的一个或多个第二承载。
该传输方法包括如下步骤：
301、终端通过空口资源向基站发送数据，基站从空口资源上接收该终端发送的数据。
302、基站通过一个第一承载向第一网络设备发送数据，第一网络设备接收基站发送的数据。
303、第一网络设备通过一个第二承载向第二网络设备发送数据。
第一承载和第二承载是预先建立的，并且在单次数据传输结束后不会释放。第一承载和第二承载在单次数据传输结束后继续保留以供下次数据传输使用。第一承载和第二承载不会随着终端状态的改变或者单次数据传输结束而需要不断的进行承载的创建和删除。第一承载和第二承载仅需建立一次即可。这避免了承载的建立、删除所需的信令过程以及由此产生的时延。这有效地提高了网络业务处理效率。
第一承载是根据第一业务属性预先建立的。第二承载是根据第二业务属性预先建立的。第一承载的数量与终端的数量没有关系。第二承载的数量与基站的数量也没有关系。第一承载和第二承载的数量是由需传输数据的业务属性决定的。第一承载和第 二承载的数量无需与每个终端对应，本专利申请使用有限的承载可以解决大量终端数据传输的问题，避免大量终端的承载信令过程以及由此产生的时延。这有效地提高了网络业务处理效率。
可选地，该传输方法还可以包括步骤304、确定第一承载。该传输方法还可以包括步骤305、确定第二承载。
第一业务属性可以与空口资源的属性相对应。可以将使用同一类空口资源的数据放在第一承载上进行数据传输。例如，对于同一类业务类别的数据会调度到相同的空口资源上。这样就可以将同一类业务的数据放在同一个第一承载上进行数据传输。当基站与第一网络设备之间的第一承载有多条时，在304中，基站确定与数据所使用的空口资源相对应的第一承载进行数据传输。在302中，第一承载与数据所使用的空口资源相对应。
可选地，第一业务属性还可以为第一服务质量特性。可以将具有同一类第一服务质量特性的数据放在第一承载上进行数据传输。当基站与第一网络设备之间的第一承载有多条时，在304中，基站确定与终端发送的数据的第一服务质量特性(QoS)相对应的第一承载。在302中，第一承载与数据的第一服务质量特性相对应。
可选地，第二业务属性可以为第二服务质量特性，可以将具有同一类第二服务质量特性的数据放在第二承载上进行数据传输。第二服务质量特性与第一服务质量特性的等级可以相同也可以不同。可以将多个不同、相邻等级的第一服务质量特性合并成一个等级的第二服务质量特性。当第二网络设备与第一网络设备之间的第二承载有多 条时，在305中，第一网络设备确定与终端发送的数据的第二服务质量特性(QoS)相对应的第二承载。在302中，第二承载与数据的第二服务质量特性相对应。
关于第一承载和第二承载，下文将做进一步详细介绍。
可选地，在第一承载上传输的数据携带终端的第一标识。该第一标识使得基站和第一网络设备在其管理域内可以准确区别各个终端。各个终端的第一标识之间可以具有正交性或准正交性或低相关性。通过第一标识，基站可以了解到其所接收的数据所对应的第一网络设备，并将数据发送给第一网络设备。第一网络设备也可以了解到其所接收的数据所对应的基站。
可选地，在第二承载上传输的数据携带终端的IP地址。终端的第一标识与终端的IP地址具有对应关系。终端的IP地址可以是终端在附着时由网关分配的。第一网络设备可以通过该对应关系，由终端的第一标识查找、获取终端的IP地址。这为在第一承载和空口进行数据传输时不携带IP地址提供了可能。可选地，该传输方法还可以包括步骤306、根据终端的第一标识获取终端的IP地址。
可选地，终端的第一标识的位数小于IP地址的位数。在空口和第一承载上可以仅用为终端分配的第一标识对终端进行识别，降低空口开销。
可选地，终端的第一标识可以是终端在附着时由第一网络设备分配的。终端的IP地址可以是终端在附着时由网关分配的。关于终端的第一标识和IP地址的具体分配方法，下文将做进一步详细介绍。
可选地，整个数据传输可以根据终端的数据控制策略进行。在上行数据传输时， 第一网络设备可以从网络控制器获取终端信息，如策略控制信息，以便完成对终端的鉴权、加密以及QoS控制等。
可选地，该第二网络设备可以是网关。该第二网络设备也可以是服务器，例如：应用服务器。第二网络设备是服务器时，可以通过互联网向用户提供各种应用服务，使得网络能够支持OTT(over the top)的业务能力，尤其在未来网络支持网络切片时，提供了一种垂直业务能力。
如图4所示，一种数据传输方法，第一网络设备与基站之间存在预先建立的一个或多个第一承载；第一网络设备与第二网络设备之间存在预先建立的一个或多个第二承载。
该传输方法包括如下步骤：
401、第二网络设备通过一个第二承载向第一网络设备发送数据。第一网络设备接收第二网络设备发送的数据。
402、第一网络设备通过一个第一承载向基站发送数据。基站接收第一网络设备发送的数据。
403、基站通过空口资源向终端发送数据。
关于第一、二承载可以参考上面的介绍。
可选地，该传输方法还可以包括步骤404、确定第二承载。该传输方法还可以包括步骤405、确定第一承载。关于确定的具体方法也可以参考上面的介绍。主要区别在于：在404中由第二网络设备确定与第二网络设备发送的数据的第二服务质量特性 (QoS)相对应的第二承载。在401中，第二承载与数据的第二服务质量特性相对应。在405中，第一网络设备可以确定与第二网络设备发送的数据的第一服务质量特性(QoS)相对应的第一承载。在402中，第一承载与数据的第一服务质量特性相对应。在405中，第一网络设备还可确定与第二网络设备发送的数据使用的空口资源的属性相对应的第一承载。在402中，第一承载与数据的空口资源的属性相对应。
可选地，在第一承载上传输的数据携带终端的第一标识。在第二承载上传输的数据携带终端的IP地址。具体可以参考前面的介绍。该传输方法还可以包括步骤406、第一网络设备根据终端的IP地址获取终端的第一标识。
图5是根据本专利申请另一个实施例，在第一网络设备集成架构下，一种数据传输方法的示意图。该通信方法可以进行安全控制，避免某些恶意终端不断发送消息，导致***阻塞。如图5所示，该一种数据传输方法包括如下步骤：
501、第一网络设备接收基站转发的终端的数据。此步骤的详细过程可以参考上文中301-302。
502、第一网络设备进行嫌疑终端的检测。嫌疑终端是指恶意攻击***的终端。如，频繁传输、存在安全问题、存在加密数据问题的终端。第一网络设备可以使用检测算法对嫌疑终端进行检测。
503、在检测到嫌疑终端时，第一网络设备向基站发送安全请求，安全请求携带：嫌疑终端的身份标识。该身份标识可以是终端的永久标识，如，国际移动用户识别码(international mobile subscriber identity，IMSI)或移动接入码(mobile access  code，简称MAC)地址。
504、基站接收安全请求。基站对嫌疑终端的数据进行安全处理。安全处理具体可包括：对该嫌疑终端的数据进行阻塞或者在空口对嫌疑终端进行重新鉴权。
505、基站向第一网络设备发送安全响应。安全响应携带：已进行安全处理的终端的身份标识。
图6是根据本专利申请另一个实施例，在第一网络设备分离架构下，一种数据传输方法的示意图。该通信方法可以进行安全控制。如图6所示，该数据传输方法包括如下步骤：
601、第一网络设备用户面接收基站转发的终端的数据。此步骤的详细过程可以参考上文中301-302。
602、与502基本相同，但是执行主体为第一网络设备用户面而不是第一网络设备。
603、在检测到嫌疑终端时，第一网络设备用户面向第一网络设备控制面发送安全请求，以使第一网络设备控制面和基站采取安全措施。安全请求中可携带：嫌疑终端的标识。
604、第一网络设备控制面接收安全请求，向基站发送安全请求。
605、基站接收安全请求。基站对嫌疑终端的数据进行安全处理。安全处理具体可包括：对该嫌疑终端的数据进行阻塞或者在空口对嫌疑终端进行重新鉴权。
606、基站向第一网络设备控制面发送安全响应。安全响应携带：已进行安全处理的终端的标识。
607、第一网络设备控制面向第一网络设备用户面发送安全响应，第一网络设备用户面接收该安全响应。安全响应携带：已进行安全处理的终端的标识。
通过上述安全控制，可以阻止恶意终端，避免***阻塞，保障了***的传输速度和效率。
接下来介绍本专利申请的承载建立方法。承载建立主要是在第一网络设备和基站以及第一网络设备和第二网络设备之间预先分别建立。承载的建立可以是在第一网络设备初始化的时候，或者在基站初始化的时候。
图7是在第一网络设备集中式架构下，第一网络设备初始化时，一种建立承载的方法的交互示意图。如图7所示，一种承载的建立方法，包括如下步骤：
701、当第一网络设备初始化的时候，第一网络设备会被配置所有其所管辖的基站信息。第一网络设备向其管辖的基站发送第一承载建立请求。第一承载建立请求中可以携带：第一网络设备的ID、IP地址和请求创建的第一承载信息。第一承载信息与第一业务属性相对应，可以包括：QoS级别、请求的带宽和端口号。
702、基站接收第一承载建立请求，准备第一承载资源，向第一网络设备发送第一承载建立响应。第一承载建立响应中可以携带：基站的ID、IP地址和创建的第一承载信息。所创建的第一承载信息包括：QoS级别、分配的带宽和第一承载ID。
703、第一网络设备接收基站发送的第一承载建立响应，向基站发送第一承载建立完成信息。第一承载建立完成信息中可以携带：第一承载建立完成指示。此步骤主要用于证实基站接收到第一网络设备的第一承载建立响应。此步骤是可选的。
704、第一网络设备向第二网络设备发送第二承载建立请求。该第二网络设备可以为网关。该第二网络设备还可以为服务器，例如：应用服务器。第二承载建立请求中可以携带：第一网络设备的标识信息和请求创建的第二承载信息。第二承载信息可以包括：QoS级别、请求的带宽。第二承载信息与第二业务属性相对应。
705、第二网络设备接收第二承载建立请求，完成承载资源分配，向第一网络设备发送第二承载建立响应。第一网络设备接收第二网络设备发送的第二承载建立响应。第二承载建立响应中可以携带：第二网络设备的ID、IP地址、第一网络设备的ID、IP地址和创建的第二承载信息。创建的第二承载信息包括：QoS级别、分配的带宽和第二承载ID。
第一承载和第二承载在第一网络设备初始化时就开始建立。无需等到数据传输时或终端附着时才建立承载。避免了数据传输时的接入时延和传输调度时延。这有效地提高了网络业务处理效率。
根据需要，可以同时创建多个第一承载和第二承载。第一承载是根据第一业务属性建立的，第二承载是根据第二业务属性建立的。可以分别为不同类别的业务分别建立承载。这样就可以为不同终端的同一类业务只建立一个第一承载。一个第一承载就可以供不同终端的同一类业务进行数据传输。
第一业务属性具体可以为终端需进行的业务的第一QoS。第一业务属性也可以为终端业务所使用的空口资源的属性。两者的不同点在于基站对终端业务处理的粒度不同。根据业务的QoS建立授权承载，则基站需要根据一类QoS级别建立承载。而根据 所使用的空口资源建立承载，则是根据基站所配置的空口资源，为一类空口资源建立一个承载。需要说明的是，即使是根据QoS级别来建立承载，也可能是把几个不同的QoS级别归并到一个承载，以减小承载数量。
第二业务属性可以为业务的第二QoS。建立第二承载时可以对来自各基站的业务进行再次合并，将具有相同第一QoS属性的业务放在同一个第二承载进行传输，也可能是将多个不同第一QoS属性的业务放在同一个第二承载进行传输。
第一承载和第二承载的数量是由需传输数据的业务属性决定的。第一承载的数量与终端的数量没有关系。第二承载的数量与基站的数量也没有关系。第一承载和第二承载的数量分别都小于基站所管辖的终端的数量。第一承载和第二承载的数量无需与每个终端对应，使用有限的承载可以解决大量终端数据传输的问题，可以避免承载信令过程以及由此产生的时延。
第一承载和第二承载在建立后一直保留，以供数据传输使用。数据传输时不再需要建立承载，并且在单次数据传输结束后也不删除第一承载和第二承载。第一承载和第二承载仅需建立一次即可。第一承载和第二承载不会随着终端状态的改变而需要不断的进行承载的创建和删除。
在一种方案下，在步骤701中，第一网络设备也可以选择发送一个组播消息给所有其管辖的基站。然后第一网络设备会接收各基站返回的消息。在收到各基站返回的消息后，第一网络设备会根据各基站的带宽需求，建立到第二网络设备的第二承载。
第一承载和第二承载是两段独立的承载。第一承载的数量可以是一个或多个。当 第一承载的数量是一个时，基站管辖的所有免授权业务都在该唯一的第一承载上传输。当第一承载的数量是多个时，可以根据需要选择相应的第一承载进行数据传输。
第二承载的数量也可以是一个或多个。当第二承载的数量是一个时，第一网络设备所管辖的所有基站的免授权业务都在该唯一的第二承载上传输。当第二承载的数量是多个时，可以根据需要选择相应的第一承载进行数据传输。
承载数量是依据业务属性决定的，和终端及基站数量没有关系。在本实施例中，无需为每个免授权终端建立承载。承载的数量与终端数量不需一一对应，承载的数量是非常有限的。相对于现有技术，所需建立的承载的数量将极大地减少。这有效地提高了网络业务处理效率。
图8是在第一网络设备分离式架构下，第一网络设备初始化的情况下，一种建立承载的方法的交互示意图。图8所示的承载的建立方法与图7所示的承载的建立方法的主要区别在于：在图8中具体由第一网络设备控制面发起承载建立请求、并且增加了第一网络设备控制面和第一网络设备用户面之间的交互。具体地，该方法包括如下步骤：
801、第一网络设备控制面向基站发送第一承载建立请求。第一承载建立请求中可以携带：第一网络设备控制面的ID、IP地址和请求创建的第一承载信息。请求创建的第一承载信息可以包括：QoS级别和请求的带宽。
802、基站接收第一承载建立请求，为第一承载准备资源，向第一网络设备控制面发送第一承载建立响应。第一承载建立响应中可以携带：基站的ID、IP地址和基站所 分配的第一承载信息。基站所分配的第一承载信息可以包括：QoS级别、分配的带宽和第一承载ID。
803、第一网络设备控制面接收基站发送的第一承载建立响应，可以根据业务属性选择其所控制的一个第一网络设备用户面，向该第一网络设备用户面发送第一承载建立请求。第一承载建立请求中可以携带：基站的ID、IP地址和基站所分配的第一承载信息。
804、第一网络设备用户面接收第一承载建立请求后，第一网络设备用户面向第一网络设备控制面发送第一承载建立响应。第一承载建立响应中可以携带：第一网络设备用户面的ID、IP地址、基站的ID、IP地址和第一网络设备用户面所分配的第一承载信息。所分配的第一承载信息可以包括：QoS级别、分配的带宽和第一承载ID。
805和806、第一网络设备控制面收到第一网络设备用户面发送的第一承载建立响应后，第一网络设备控制面分别向基站(805)和第一网络设备用户面(806)发送第一承载建立完成信息。第一承载建立完成信息中可以携带：第一承载建立完成指示，第一网络设备用户面的ID、IP地址、基站的ID、IP地址和建立完成的第一承载信息。建立完成的第一承载信息可以包括：QoS级别、分配的带宽和第一承载ID。此步骤主要用于通知第一网络设备用户面和基站创建完成的第一承载信息。
807、第一网络设备控制面向第一网络设备用户面发送第二承载建立请求。第一网络设备控制面可同时为其所管辖的第一网络设备用户面建立第二承载。各个第二承载的QoS可依据第一承载的QoS及控制策略确定。第二承载建立请求中可以携带：第 一网络设备控制面的ID、IP地址、目标第一网络设备用户面的ID、IP地址。
808、第一网络设备用户面接收第二承载建立请求后，第一网络设备用户面向第一网络设备控制面发送第二承载建立响应。第二承载建立响应中可以携带：第一网络设备用户面的ID、IP地址、第一网络设备控制面的ID、IP地址和第一网络设备用户面所分配的第二承载信息。所分配的第二承载信息包括：QoS级别、分配的带宽、第二承载ID。
809、第一网络设备控制面接收来自第一网络设备用户面的第二承载建立响应后，向第二网络设备发送第二承载建立请求，以分别为各第一网络设备用户面建立第二承载，第二承载建立请求中可以携带：第一网络设备控制面的ID、IP地址、各第一网络设备用户面的ID、IP地址和各第一网络设备用户面所分配的第二承载信息。所分配的第二承载信息可以包括：QoS级别、分配的带宽和第二承载ID。
810、第二网络设备接收第二承载建立请求，完成承载资源分配后，向第一网络设备控制面返回各第一网络设备用户面所对应的第二承载建立响应。该第二承载建立响应中可以携带：第二网络设备的ID、IP地址、各个第一网络设备用户面的ID、IP地址及第二网络设备为各个第一网络设备用户面分配的第二承载信息。所分配的第二承载信息可以包括：QoS级别、分配的带宽和第二承载ID。
811、812、第一网络设备控制面向第二网络设备(811)和第一网络设备用户面(812)发送第二承载建立完成信息。第二承载建立完成信息中可以携带：第二网络设备的ID、IP地址、第一网络设备用户面的ID、IP地址及为其创建完成的第二承载信息。第二 承载信息包括：QoS级别、分配的带宽、第二承载ID。此步骤主要用于通知第一网络设备用户面和第二网络设备创建完成的第二承载信息。
图9是在第一网络设备集中式架构下，基站初始化的情况下，一种建立承载的方法的交互示意图。如图9所示，一种承载的建立方法，包括如下步骤：
901、当基站初始化的时候，基站向第一网络设备发送第一承载建立请求。第一承载建立请求中可以携带：基站的ID、IP地址和请求创建的第一承载信息(包括：QoS级别、请求的带宽)。第一承载建立请求还可携带：基站分别为不同CTU分配的资源信息，包括空口的频率、空口带宽、调制编码方案以及各CTU所对应的业务属性。业务属性可以指业务的QoS级别。
902、第一网络设备接收第一承载建立请求，准备第一承载资源，向基站发送第一承载建立响应。第一承载建立响应中可以携带：第一网络设备的的ID、IP地址、创建的第一承载信息。所创建的第一承载信息可以包括：QoS级别、分配的带宽和第一承载ID。
903、基站接收第一网络设备发送的第一承载建立响应，向第一网络设备发送第一承载建立完成信息，第一承载建立完成信息中可以携带：第一承载建立完成指示。此步骤主要用于证实第一网络设备接收到基站的第一承载建立响应。此步骤是可选的。
在第一网络设备和第二网络设备之间没有第二承载的情形下，可以进行步骤904和905。在第一网络设备和第二网络设备之间已经有第二承载的情形下，如果基站为免授权业务分配的带宽较大或较小，可能会导致第一网络设备和第二网络设备之间的 带宽不足或多余，此时就需要修改第一网络设备和第二网络设备之间的传输带宽，进行步骤906和907。如果第一网络设备和第二网络设备之间的带宽足够，则无需进行任何步骤。
904、第一网络设备向第二网络设备发送第二承载建立请求，第二承载建立请求中可以携带：第一网络设备的ID、IP地址和请求创建的第二承载信息。请求创建的第二承载信息可以包括：QoS级别和请求的带宽。
905、第二网络设备接收第二承载建立请求，完成承载资源分配，向第一网络设备发送第二承载建立响应。第一网络设备接收第二网络设备发送的第二承载建立响应。第二承载建立响应中可以携带：第二网络设备的ID、IP地址和第一网络设备的标识信息和创建的第二承载信息。创建的第二承载信息包括：QoS级别、分配的带宽和第二承载ID。
906、第一网络设备向第二网络设备发送第二承载修改请求，第二承载修改请求中可以携带：请求修改的带宽。
907、第二网络设备接收第二承载修改请求，完成承载资源的修改，向第一网络设备发送第二承载修改响应。第一网络设备接收第二网络设备发送的第二承载修改响应。第二承载修改响应中可以携带：第二承载的标识信息和修改后的第二承载所分配的带宽。
当第二网络设备为服务器时，可以在服务器初始化时建立服务器与第一网络设备之间的第二承载。其建立流程可以参考上面的描述。
图10是在第一网络设备分离式架构下，基站初始化的情况下，一种建立承载的方法的交互示意图。图10所示的承载的建立方法与图9所示的承载的建立方法的主要区别在于：在图10中具体由基站向第一网络设备控制面发起承载建立请求、并且增加了第一网络设备控制面和第一网络设备用户面之间的交互。具体地，该方法包括如下步骤：
1001、与901类似。当基站初始化的时候，基站向第一网络设备控制面发送第一承载建立请求。第一承载建立请求中可以携带：基站的ID、IP地址和请求创建的第一承载信息。该请求创建的第一承载信息包括：QoS级别、请求的带宽。第一承载建立请求还可携带：基站分别为不同CTU分配的资源信息，包括空口的频率、空口带宽、调制编码方案以及各CTU所对应的业务属性。业务属性可以指业务的QoS级别。
1002、第一网络设备控制面向第一网络设备用户面发送第一承载建立请求，通知第一网络设备用户面准备承载资源。向第一网络设备用户面发送的第一承载建立请求中可以携带：基站的ID、IP地址和请求创建的第一承载信息。该请求创建的第一承载信息包括：QoS级别、请求的带宽。请求的带宽是指基站与第一网络设备用户面之间的承载的带宽。
1003、第一网络设备用户面接收第一承载建立请求，向第一网络设备控制面发送第一承载建立响应。第一网络设备用户面返回承载建立结果给第一网络设备控制面。第一承载建立响应中可以携带：第一网络设备用户面的的ID、IP地址、第一网络设备用户面分配的第一承载信息。该第一承载信息包括：QoS级别、分配的带宽和 第一承载ID。
1004、第一网络设备控制面接收第一承载建立响应，向基站发送第一承载建立响应。
1005、基站接收第一网络设备控制面发送的第一承载建立响应，向第一网络设备控制面发送第一承载建立完成信息，第一承载建立完成信息中可以携带：第一网络设备用户面的ID、IP地址、为第一网络设备用户面创建的第一承载信息。该第一承载信息包括：QoS级别、分配的带宽和第一承载ID。
1006、第一网络设备控制面向第一网络设备用户面发送第一承载建立完成消息。消息中可以携带：第一网络设备用户面的ID、IP地址、为第一网络设备用户面创建的第一承载信息。该第一承载信息可以包括：QoS级别、分配的带宽、第一承载ID。
在第一网络设备控制面和第二网络设备之间没有第二承载的情形下，可以进行步骤1007-1012。在第一网络设备控制面和第二网络设备之间已经有第二承载的情形下，如果基站为免授权业务分配的带宽较大或较小，可能会导致第一网络设备控制面和第二网络设备之间的带宽不足或多余，此时就需要修改第一网络设备控制面和第二网络设备之间的传输带宽，进行步骤1013和1014。如果第一网络设备控制面和第二网络设备之间的带宽足够，则无需进行任何步骤。
1007、第一网络设备控制面向第一网络设备用户面发送第二承载建立请求，通知第一网络设备用户面准备承载资源。向第一网络设备用户面发送的第二承载建立请求中可以携带：第一网络设备控制面的ID、IP地址、基站的ID、IP地址和请求资源 分配指示。
1008、免授权用户面收到第二承载建立请求后，可同时建立第二承载。各第二承载的QoS可依据请求基站的第一承载的QoS及控制策略确定。免授权用户面完成承载资源准备后，向第一网络设备控制面发送第二承载建立响应。第一网络设备用户面返回准备的承载资源信息给第一网络设备控制面。第一网络设备用户向第一网络设备控制面发送第二承载建立响应。第二承载建立响应中可以携带：第一网络设备用户面的的ID、IP地址和分配的第一承载信息。该第一承载信息包括：QoS级别、分配的带宽和第一承载ID。
1009、第一网络设备控制面向第二网络设备发送第二承载建立请求，可同时为免授权用户面建立承载。第二承载建立请求中可以携带：第一网络设备控制面的ID、IP地址和请求创建的第二承载信息。该承载信息可以包括：QoS级别和请求的带宽。
1010、第二网络设备接收第二承载建立请求，完成承载资源分配，向第一网络设备控制面发送第二承载建立响应。第一网络设备控制面接收第二网络设备发送的第二承载建立响应。第二承载建立响应中可以携带：第二网络设备的ID、IP地址、第一网络设备控制面的标识信息和第二网络设备分配的第二承载信息。第二承载信息可以包括：QoS级别、分配的带宽和第二承载ID。
1011、第一网络设备控制面向第二网络设备发送承载建立完成消息。消息中可以携带：第二网络设备的ID、IP地址、第一网络设备用户面的ID、IP地址和创建的第二承载ID。
1011、1012、第一网络设备控制面向第二网络设备(1011)和第一网络设备用户面(1012)分别发送第二承载建立完成消息。第二承载建立完成消息中可以携带：第一网络设备控制面ID、IP地址、第一网络设备用户面的ID、IP地址、及建立完成的第二承载信息。该第二承载信息可以包括：QoS级别、分配的带宽和第二承载ID。
1013、第一网络设备控制面向第二网络设备发送第二承载修改请求，第二承载修改请求中可以携带：请求修改的带宽。
1014、1015第一网络设备控制面接收第二网络设备(1014)和第一网络设备用户面(1015)分别发送的第二承载修改响应；第二承载修改响应中可以携带：第二承载的标识信息和修改后的第二承载所分配的带宽。
在图7-10中，关于第二承载的建立和修改，第一网络设备与第二网络设备或第一网络设备控制面与第二网络设备之间的交互，可以通过网络控制器中转。通过网络控制器中转，使得本专利申请的方案可以兼容现有的网络***。
在LTE***中，UE在完成随机接入后，会被分配一个小区无线网络临时标识(Cell Radio Network Temporary Identifier，简称C-RNTI)用于空口传输，识别连接态。而UE的IP地址的获取是在默认承载建立完成之后，由P-GW完成IP地址分配。由于未来的MTC终端的大量存在，如果为每个终端建立独立的承载，则可能导致网关无法管理如此海量的承载context，大量承载的建立在技术上存在极大挑战，在没有核心网承载时，如何为MTC终端分配地址就是一个问题。
针对此，本专利申请提出了在终端附着的过程中，由第一网络设备分配终端的第 一标识，以供终端在空口进行数据传输，用以唯一标识该终端和降低空口开销。由网关分配终端的IP地址，以实现与网络进行通信。第一标识的位数小于IP地址的位数。在空口和基站与第一网络设备间使用该第一标识对终端进行识别，可以降低空口开销。当第一网络设备接收到空口的数据后，会将第一标识恢复成IP地址以在网络上进行传输。
当终端第一次接入网络时，通过第一网络设备分配唯一的ID，并用第一网络设备和网关之间的预先建立的承载获取终端IP地址。接入仅需做一次，可以获取用户签约信息，并获取用户第一标识符，为后续数据传输提供控制依据。
第一网络设备为终端分配的第一标识用于在第一网络设备范围内唯一识别一个终端，通过该第一标识，第一网络设备可以关联和管理终端相关的数据。
图11是根据本专利申请的一个实施例，终端进行附着的方法的示意图。如图11所示，其包括如下步骤：
1101、终端和基站之间进行随机接入过程(Random Access Channel，RACH)。该随机接入过程可以是通常的随机接入过程，也可以是在免授权资源上进行的随机接入过程。
1102、终端通过空口资源向基站发送附着请求(Attach Request)消息。消息中可以携带：终端的IMSI、MAC地址、附着类型和加密选项等。
1103、基站收到附着请求，不对附着请求进行解析。基站直接通过第一承载向第一网络设备发送附着请求。附着请求中可以增加：基站ID或IP地址信息。
1104、第一网络设备收到附着请求，对附着请求进行解析。第一网络设备向网络控制器发送鉴权请求。该消息名称也可以是安全消息或附着请求。消息中可以携带：终端当前所在基站信息、第一网络设备的标识信息、终端的鉴权信息和安全信息和控制策略。
1105、网络控制器收到附着请求后，向第一网络设备发送附着响应。该消息名称也可以是安全响应或鉴权响应。附着响应中可以携带：控制策略，鉴权加密参数以及可能的网关信息。对可能存在多个网关的情况下，所选择的网关信息。
1106、第一网络设备从网络控制器收到附着响应，第一网络设备为终端分配第一标识。
1107、第一网络设备向对应的网关发送IP分配请求。IP分配请求中可以携带：终端的永久ID。该永久ID可以包括IMSI和MAC地址。
1108、网关收到IP分配请求，为终端分配一个IP地址，并发送IP分配响应给第一网络设备。分配响应中可以携带：网关的IP地址、终端的永久ID、为终端分配的IP地址、终端所属的基站的ID或IP地址。
1109、第一网络设备收到IP分配响应后，可以在第一网络设备中建立第一标识和IP地址间的对应关系，该对应关系包括上行和下行映射。上行映射是指从基站接收到终端的数据是以第一网络设备分配的第一标识进行区分的，需要将其恢复成正常的IP地址。下行映射是指从网关发送给第一网络设备的数据，第一网络设备会将IP地址转换成第一标识，以供基站和终端之间在空口进行传输。第一网络设备向基站发 送附着响应。附着响应中可以携带：第一网络设备ID或IP地址、第一网络设备为终端分配的第一标识、网关为终端分配的IP地址以及鉴权加密参数。
1110、基站收到附着响应后，向终端发送附着响应。向终端发送的附着响应中可以携带：第一网络设备为终端分配的第一标识、网关为终端分配的IP地址、鉴权加密参数。
第一网络设备为终端分配的第一标识可具有正交性，如Zadoff-Chu(ZC)序列。这可以方便基站使用该第一标识对终端进行检测。
第一标识的长度应尽量短以降低基站检测的复杂度。但是过短的序列使得支持的终端数减少，因此，第一网络设备分配的第一标识应该是一个合理的长度。
此外，为保证能为每个终端分配到第一标识，可以将终端区分为静态终端、慢速移动终端、快速移动终端。慢速和快速根据实际需要确定。如移动速度小于5km/h即为慢速。如移动速度大于等于5km/h即为快速。为每一类终端可以预先分配一组第一标识。在具体为某个终端分配第一标识时，可以从终端所属性对应的一组第一标识中选择一个第一标识分配给该终端。对静态终端或慢速移动的第一标识，可以在不同范围内重用。对快速移动终端需在更大范围内保持唯一。
图12是根据本专利申请的另一个实施例，终端进行附着的方法的示意图。图12与图11的主要区别在于：基站直接向网络控制器发送附着请求。如图12所示，其包括如下步骤：
1201、与1101相同。
1202、与1102相同.
1203、基站收到附着请求，对附着请求进行解析，解析到附着请求后，将该附着请求发送给网络控制器。附着请求中可以携带：基站ID或IP地址信息、终端的IMSI、MAC地址和附着类型和加密选项。
1204、网络控制器收到附着请求后，向网关发送IP分配请求。IP分配请求中可以携带：终端的永久ID。该永久ID可以包括IMSI、MAC地址。
1205、网关收到IP分配请求，为终端分配一个IP地址，并发送IP分配响应给网络控制器。分配响应中可以携带：网关的IP地址、终端的永久ID和为终端分配的IP地址。
1206、网络控制器收到IP分配响应后，向第一网络设备控制面发送附着请求，该附着请求中可以携带：基站ID或IP地址、终端的IMSI、MAC地址、附着类型、加密选项和终端的IP地址。
1207、第一网络设备收到附着请求后，为终端分配第一标识。第一网络设备还可建立第一标识和IP地址间的对应关系，该对应关系包括上行和下行映射。上行映射是指从基站接收到终端的数据是以第一标识进行区分的，需要将其恢复成正常的IP地址。下行映射是指从网关发送给第一网络设备用户面的数据，第一网络设备会将IP地址转换成第一标识，以供基站和终端之间在空口进行传输。
1208、第一网络设备收到附着响应后，向网络控制器发送附着响应。该附着响应中可以携带：第一网络设备为终端分配的第一标识以及网关为终端分配的IP地 址。
1209、网络控制器向基站发送附着响应。附着响应中可以携带：第一网络设备ID或IP地址、第一网络设备为终端分配的第一标识、网关为终端分配的IP地址以及鉴权加密参数。
1210、与1110相同。
在第一网络设备分离的架构下，终端在网络中附着的流程和在第一网络设备集成的架构下的流程基本类似。不同的是由于第一网络设备被分成了控制面和用户面，控制面用于终端控制信息及策略，用户面则用于数据传输。终端初始附着时，与控制面进行交互。由于承载是在用户面与网关之间建立的，因此，第一标识的分配需要通过第一网络设备用户面来实现。同时，终端的控制信息需要***到控制面。
图13-15是在第一网络设备分离的架构下，终端在网络中附着的三个不同实施例的流程示意图。在图13-15所示实施例中，终端的第一标识是由第一网络设备用户面分配的。在图13所示实施例中，基站解析消息并将消息发送给第一网络设备控制面。在图14所示实施例中，基站对消息不做解析，直接发送给第一网络设备用户面，由第一网络设备用户面解析，如果是控制消息，则发送给第一网络设备控制面处理，否则做转发处理。在图15中，基站解析消息，解析出附着消息后，将附着消息发送给网络控制器。
如图13所示，根据本专利申请的另一个实施例，终端设备在网络中附着的方法，包括如下步骤：
1301、与1101相同。
1302、与1102相同。
1303、基站收到附着请求，对附着请求进行解析，解析到附着请求后，将该附着请求发送给第一网络设备控制面。附着请求中可以携带：基站ID或IP地址、终端的IMSI、MAC地址、附着类型和加密选项。
1304、与1104类似，第一网络设备控制面收到附着请求，向网络控制器发送鉴权请求。该消息名称也可以是安全消息或附着请求。鉴权请求中可以携带：终端当前所在基站信息、第一网络设备控制面的ID或IP地址、终端的鉴权信息和安全信息和控制策略。
1305、与1105类似，区别在于：在1305中，是向第一网络设备控制面发送附着响应。
1306、与1107类似，区别在于：在1306中，是第一网络设备控制面向对应的网关发送IP分配请求。IP分配请求中可以携带：终端的永久ID。该永久ID可以包括IMSI、MAC地址。
1307、与1108类似，区别在于：在1307中，网关向第一网络设备控制面发送IP分配响应。分配响应中可以携带：网关的IP地址、终端的永久ID、为终端分配的IP地址、终端所属的基站的ID或IP地址和第一网络设备控制面的ID或IP地址。
1308、第一网络设备控制面收到IP分配响应后，选择其所控制的一个第一网络设备用户面，向免授权用户面发送附着请求。该附着请求中可以携带：终端的IMSI 或MAC地址、网关分配的IP地址、鉴权加密参数、控制策略和所在基站的ID或IP地址等。
1309、第一网络设备用户面收到附着请求后为为终端分配第一标识。第一网络设备用户面还可建立第一标识和IP地址间的对应关系。
1310、第一网络设备用户面向第一网络设备控制面发送附着响应。该附着响应中可以携带：终端的IMSI或MAC地址及为其分配的ID，和所在基站ID或IP地址。
1311、第一网络设备控制面收到第一网络设备用户面的附着响应后，向基站发送附着响应。该附着响应中可以携带：第一网络设备用户面为终端分配的第一标识以及网关为终端分配的IP地址和鉴权加密参数。
1312、与1110相同。
如图14所示，根据本专利申请的另一个实施例，终端设备在网络中附着的方法，包括如下步骤：
1401、与1301相同。
1402、与1302相同。
1403、基站收到附着请求，不对附着请求进行解析，直接将该附着请求发送给第一网络设备用户面进行解析。该附着请求中可以携带第一网络设备用户面的ID或IP地址、终端的IMSI、MAC地址、附着类型和加密选项。
1404、第一网络设备解析到附着请求后，将该附着请求发送给第一网络设备控制面。附着请求中可以携带：基站ID或IP地址、终端的IMSI、MAC地址、附着类型 和加密选项。
1405、与1304类似，第一网络设备控制面收到附着请求，向网络控制器发送附着请求，该消息名称也可以是安全消息或鉴权请求。附着请求中可以携带：终端当前所在基站信息、第一网络设备控制面的ID或IP地址、终端的鉴权信息和安全信息和控制策略。
1406、与1305相同。
1407、与1306相同。
1408、与1307相同。
1409、与1308相同。
1410、与1309相同。
1411、与1310相同。
1412、与1311相同。
1413、与1312相同。
如图15所示，根据本专利申请的另一个实施例，终端设备在网络中附着的方法，包括如下步骤：
1501、与1301相同。
1502、与1302相同。
1503、基站收到附着请求，对附着请求进行解析，解析后，将该附着请求发送给网络控制器。附着请求中可以携带：基站ID或IP地址、终端的IMSI、MAC地址、 附着类型和加密选项。
1504、与1204相同。
1505、与1205相同。
1506、网络控制器收到IP分配响应后，向第一网络设备控制面发送附着请求，该附着请求中可以携带：基站ID或IP地址、终端的IMSI、MAC地址、附着类型、加密选项、网关为终端分配的IP地址。
1507、第一网络设备控制面收到附着请求后，选择其所控制的一个第一网络设备用户面，向该免授权用户面发送附着请求。该附着请求与1308中的附着请求相同。
1508、与1309相同。
1509、与1310相同。
1510、第一网络设备控制面收到附着响应后，向网络控制器发送附着响应。该附着响应中可以携带：第一网络设备用户面为终端分配的第一标识以及网关为终端分配的IP地址。
1511、与1209相同。
1512、与1210相同。
上述附着过程中，如果基站不对附着请求进行解析，则该附着请求可以在承载上进行传输。
如图16所示，本专利申请还提供了一种机器类型的数据传输***，包括第一网络 设备104、基站102和第二网络设备106。图16中的第一网络设备是集成式架构。上述数据传输***可以处理上行和/或下行数据传输。
第一网络设备104包括第一接收器114a和第一发送器114b。第一网络设备104还可以包括第一处理器114c。基站102包括第二接收器112a和第二发送器112b。基站102还可以包括第二处理器112c。第二网络设备116包括第三接收器116a和第三发送器116b。第二网络设备116还可以包括第三处理器116c。
第二接收器112a从空口资源上接收终端发送的数据。第二发送器112b通过预先建立的第一承载161向第一网络设备104的第一接收器114a发送该数据。当基站102与第一网络设备104之间预先建立的第一承载161有多条时，第二处理器112c可以根据数据的第一业务属性选择第一承载161。
可选地，第一业务属性为空口资源的属性。第二发送器112b通过与数据所使用的空口资源的属性相对应的第一承载161发送数据。第一接收器114a通过该第一承载161接收数据。
可选地，第一业务属性为第一服务质量特性。第二发送器112b通过与数据的第一服务质量特性相对应的第一承载161发送数据。第一接收器114a通过该第一承载161接收数据。
可选地，第一处理器114c可以根据数据的第二业务属性选择第二承载162。第二业务属性可以为第二服务质量特性。第一发送器114b通过与数据的第二服务质量特性相对应的第二承载162向第二网络设备发送数据。
第一接收器114a通过第一承载161接收的数据可以携带终端的第一标识。第一发送器114b通过第二承载162发送的数据可以携带终端的IP地址。终端的第一标识与终端的IP地址具有对应关系。第一处理器114c可以通过终端的第一标识获取终端的IP地址。
关于第一、二业务属性和第一、二承载和第一标识及其他相关联的技术内容，可以参考前文的介绍。
本实施例的数据传输***还可以提供安全控制。具体介绍如下：第一处理器114c还根据数据检测嫌疑终端、并在检测到嫌疑终端后通知第一发送器114b。检测的具体方法可以参考一些对恶意用户的检测算法。第一发送器114b可以通过第一承载161向基站102的第二接收器112a发送安全请求。
第二接收器112a接收安全请求后通知第二处理器112c。基站102的第二处理器112c对嫌疑终端进行安全处理。安全处理具体可包括：对该嫌疑终端的数据进行阻塞或者在空口对嫌疑终端进行重新鉴权。安全处理完后，第二处理器112c会通知第二发送器112b。
第二发送器112b通过第一承载161向第一接收器114a发送安全响应。第一接收器114a接收该安全响应。
第一接收器114a还从预先建立的第二承载162上接收第三发送器116b发送的数据。该数据需要发送给***中某个终端的。当第二网络设备116与第一网络设备104之间预先建立的第二承载162有多条时，第三处理器116c可以根据数据的第二业务属 性选择第二承载162。该第二业务属性可以为第二服务质量特性。
第一发送器114b通过预先建立的第一承载161向基站102的第二接收器112a发送数据。当预先建立的第一承载161有多条时，第一处理器114c可以根据数据的第一业务属性选择第一承载161。可选地，第一业务属性为第一服务质量特性。第一发送器114b通过与数据的第一服务质量特性相对应的第一承载161发送数据。第二接收器112a通过该第一承载161接收数据。
第二接收器112a接收数据后，第二处理器112c可以选择适当的空口资源将数据发送给基站。
如图17所示，本专利申请还提供了另一种机器类型的数据传输***。与图16不同，图17中的第一网络设备是分离式架构。第一网络设备104包括第一网络设备用户面104c和第一网络设备控制面104a。对于基本的数据传输，分离式架构和集成式架构基本类似。在分离式架构下，第一接收器114a、第一发送器114b和第一处理器114c具体是位于第一网络设备用户面104c内。第一网络设备控制面104a包括第四接收器124a、第四发送器124b和第四处理器124c。
关于安全控制，本实施例与图16所示的实施例不同。在本实施例中，第一发送器114b在第一处理器114c检测到嫌疑终端后向第一网络设备控制面104a的第四接收器124a发送安全请求。第四发送器124b会向第二接收器112a发送安全请求。第二接收器112a接收该安全请求。第二处理器112c会采取安全措施。第二发送器112a还向第一网络设备控制面104a的第四接收器124a发送安全响应。第四接收器124a接收该安 全响应、向第一接收器114a发送安全响应。
应理解，以上某一实施例中的技术特征和描述，为了使专利申请文件简洁清楚，可以理解适用于其他实施例，比如方法实施例的技术特征可以适用于装置实施例或其他方法实施例，在其他实施例就不再一一赘述。
本专利申请中，方法步骤虽然进行了编号，但这只是为了叙述方便，并不代表方法的各步骤一定要按照该编号进行。本领域技术人员可以对方法的各个步骤的顺序做合理的调整。
另外，本文中术语“***”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本专利申请实施例中，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能， 但是这种实现不应认为超出本专利申请的范围。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本专利申请所提供的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口、装置或单元的间接耦合或通信连接，也可以是电的，机械的或其它的形式连接。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本专利申请实施例方案的目的。
另外，在本专利申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本专利申请的技术 方案本质上或者说对现有技术做出贡献的部分，或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者第一网络设备等)执行本专利申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本专利申请可以用硬件实现，或固件实现，或它们的组合方式来实现。当使用软件实现时，可以将上述功能存储在计算机可读介质中或作为计算机可读介质上的指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是计算机能够存取的任何可用介质。以此为例但不限于：计算机可读介质可以包括RAM、ROM、EEPROM、CD-ROM或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。此外。任何连接可以适当的成为计算机可读介质。例如，如果软件是使用同轴电缆、光纤光缆、双绞线、数字终端线(DSL)或者诸如红外线、无线电和微波之类的无线技术从网站、服务器或者其他远程源传输的，那么同轴电缆、光纤光缆、双绞线、DSL或者诸如红外线、无线和微波之类的无线技术包括在所属介质的定影中。如本专利申请所使用的，盘(Disk)和碟(disc)包括压缩光碟(CD)、激光碟、光碟、数字通用光碟(DVD)、 软盘和蓝光光碟，其中盘通常磁性的复制数据，而碟则用激光来光学的复制数据。上面的组合也应当包括在计算机可读介质的保护范围之内。
以上所述，仅为本专利申请的具体实施方式，但本专利申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本专利申请揭露的技术范围内，可轻易想到各种等效的修改或替换，这些修改或替换都应涵盖在本专利申请的保护范围之内。因此，本专利申请的保护范围应以权利要求的保护范围为准。
总之，以上所述仅为本专利申请技术方案的较佳实施例而已，并非用于限定本专利申请的保护范围。凡在本专利申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本专利申请的保护范围之内。

Claims (16)

  1. 一种数据传输方法，其特征在于：
    第一网络设备与基站之间存在预先建立的一个或多个第一承载；所述第一网络设备与第二网络设备之间存在预先建立的一个或多个第二承载；
    所述方法包括如下步骤：
    所述第一网络设备通过一个第一承载接收基站发送的数据，所述数据是终端通过空口资源向所述基站发送的，所述用于接收所述数据的第一承载与所述数据的第一业务属性相对应；
    所述第一网络设备通过一个第二承载向第二网络设备发送所述数据，所述用于发送所述数据的第二承载与所述数据的第二业务属性相对应。
  2. 如权利要求1所述的方法，其特征在于：
    所述第一承载是所述基站或所述第一网络设备初始化时建立的。
  3. 如权利要求1或2所述的方法，其特征在于：
    所述第二承载是所述基站或所述第一网络设备初始化时建立的。
  4. 如权利要求1或2所述的方法，其特征在于：
    所述第二网络设备是服务器，所述第二承载是所述服务器初始化时建立的。
  5. 如权利要求1-4任一所述的方法，其特征在于：
    所述第一业务属性为空口资源的属性，所述用于接收所述数据的第一承载与所述数据所使用的所述空口资源的属性相对应。
  6. 如权利要求1-4任一所述的方法，其特征在于：
    所述第一业务属性为第一服务质量特性，所述用于接收所述数据的第一承载与所述数据的第一服务质量特性相对应。
  7. 如权利要求1-6任一所述的方法，其特征在于：
    所述第二业务属性为第二服务质量特性，所述方法还包括：所述第一网络设备通过所述数据的第二服务质量特性确定所述用于发送所述数据的第二承载。
  8. 如权利要求1-7任一所述的方法，其特征在于：
    所述通过第一承载接收的所述数据携带所述终端的第一标识；所述第一网络设备根据所述终端的第一标识与所述终端的IP地址之间的对应关系获取所述终端的IP地址；所述第一网络设备在向所述第二网络设备发送的所述数据中携带所述终端的IP地址。
  9. 如权利要求7所述的方法，其特征在于：
    所述第一标识的位数小于所述IP地址的位数。
  10. 一种第一网络设备，其特征在于：
    第一网络设备与基站之间存在预先建立的一个或多个第一承载；所述第一网络设备与第二网络设备之间存在预先建立的一个或多个第二承载；
    所述第一网络设备包括第一接收器和第一发送器；
    所述第一接收器通过一个第一承载接收基站发送的数据，所述数据是终端通过空口资源向所述基站发送的，所述用于接收所述数据的第一承载与所述数据的第一业务 属性相对应；
    所述第一发送器通过一个第二承载向第二网络设备发送所述数据，所述用于发送所述数据的第二承载与所述数据的第二业务属性相对应。
  11. 如权利要求10所述的第一网络设备，其特征在于：
    所述第一承载和第二承载是所述第一网络设备初始化时建立的。
  12. 如权利要求10或11所述的第一网络设备，其特征在于：
    所述第一业务属性为空口资源的属性，所述用于接收所述数据的第一承载与所述数据所使用的所述空口资源的属性相对应。
  13. 如权利要求10或11所述的第一网络设备，其特征在于：
    所述第一业务属性为第一服务质量特性，所述用于接收所述数据的第一承载与所述数据的第一服务质量特性相对应。
  14. 如权利要求10-13任一所述的第一网络设备，其特征在于：
    所述第二业务属性为第二服务质量特性，所述第一网络设备还包括第一处理器，所述第一处理器通过所述数据的第二服务质量特性确定所述用于发送所述数据的第二承载。
  15. 如权利要求14所述的第一网络设备，其特征在于：
    所述通过第一承载接收的所述数据携带所述终端的第一标识；所述第一处理器还根据所述终端的第一标识与所述终端的IP地址之间的对应关系获取所述终端的IP地址，所述第一发送器向所述第二网络设备发送的所述数据中携带所述终端的IP地址。
  16. 如权利要求15所述的第一网络设备，其特征在于：
    所述第一标识的位数小于所述IP地址的位数。
PCT/CN2016/106816 2015-11-30 2016-11-22 一种数据传输方法及*** WO2017092587A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP16869897.5A EP3364671B1 (en) 2015-11-30 2016-11-22 Method and device for data transmission
US15/991,691 US10667305B2 (en) 2015-11-30 2018-05-29 Data transmission method and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510859746.2A CN106817669B (zh) 2015-11-30 2015-11-30 一种数据传输方法及***
CN201510859746.2 2015-11-30

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/991,691 Continuation US10667305B2 (en) 2015-11-30 2018-05-29 Data transmission method and system

Publications (1)

Publication Number Publication Date
WO2017092587A1 true WO2017092587A1 (zh) 2017-06-08

Family

ID=58796279

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/106816 WO2017092587A1 (zh) 2015-11-30 2016-11-22 一种数据传输方法及***

Country Status (4)

Country Link
US (1) US10667305B2 (zh)
EP (1) EP3364671B1 (zh)
CN (1) CN106817669B (zh)
WO (1) WO2017092587A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3370466A4 (en) * 2016-02-05 2019-07-10 Guangdong Oppo Mobile Telecommunications Corp., Ltd. COMMUNICATION METHOD, DEVICE EQUIPMENT AND NETWORK EQUIPMENT
CN107295585B (zh) 2016-04-13 2021-05-18 华为技术有限公司 一种数据传输方法、网络设备、终端设备及基站
CN109842910A (zh) * 2017-11-28 2019-06-04 ***通信有限公司研究院 一种网络切片的处理方法及接入网网元
CN113079539B (zh) * 2020-01-03 2023-07-18 大唐移动通信设备有限公司 一种信息传输方法、终端及网络设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102076028A (zh) * 2009-11-23 2011-05-25 中兴通讯股份有限公司 公用承载建立的方法、数据传输方法和核心网络侧设备
CN102149214A (zh) * 2010-02-05 2011-08-10 中兴通讯股份有限公司 一种通信***中的数据传输方法和***
US20130201924A1 (en) * 2012-02-07 2013-08-08 Qualcomm Incorporated Data radio bearer (drb) enhancements for small data transmissions apparatus, systems, and methods
CN103563440A (zh) * 2011-03-18 2014-02-05 知识风险控股81有限责任公司 移动通信网络和方法
WO2014135126A1 (en) * 2013-03-08 2014-09-12 Huawei Technologies Co., Ltd. System and method for uplink grant-free transmission scheme

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015036055A1 (en) * 2013-09-16 2015-03-19 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for providing user equipment (ue) connectivity
US9603186B2 (en) * 2014-05-08 2017-03-21 Intel IP Corporation Mobility management entity, user equipment and methods for machine type communication

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102076028A (zh) * 2009-11-23 2011-05-25 中兴通讯股份有限公司 公用承载建立的方法、数据传输方法和核心网络侧设备
CN102149214A (zh) * 2010-02-05 2011-08-10 中兴通讯股份有限公司 一种通信***中的数据传输方法和***
CN103563440A (zh) * 2011-03-18 2014-02-05 知识风险控股81有限责任公司 移动通信网络和方法
US20130201924A1 (en) * 2012-02-07 2013-08-08 Qualcomm Incorporated Data radio bearer (drb) enhancements for small data transmissions apparatus, systems, and methods
WO2014135126A1 (en) * 2013-03-08 2014-09-12 Huawei Technologies Co., Ltd. System and method for uplink grant-free transmission scheme

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3364671A4

Also Published As

Publication number Publication date
CN106817669B (zh) 2021-05-04
EP3364671A1 (en) 2018-08-22
US20180279393A1 (en) 2018-09-27
CN106817669A (zh) 2017-06-09
EP3364671A4 (en) 2018-09-12
EP3364671B1 (en) 2020-10-28
US10667305B2 (en) 2020-05-26

Similar Documents

Publication Publication Date Title
US10187909B2 (en) Method for indicating a ciphering indication for a sidelink radio bearer in a D2D communication system and device therefor
EP3131352B1 (en) Method for performing a logical channel prioritization in a d2d communication system and device therefor
US10219293B2 (en) Method for avoiding transmitting MAC PDU having padding only in a D2D communication system and device therefor
CN107211430B (zh) 在d2d通信***中选择用于d2d ue的副链路授权的方法及其装置
KR101828725B1 (ko) 서비스 요청 절차 수행 방법 및 사용자 장치
JP6392880B2 (ja) Ｄ２ｄ通信システムにおけるアイディーの衝突を解決する方法及びその装置
RU2636753C1 (ru) Способ конфигурирования mac pdu для системы связи d2d и устройство для его осуществления
US10028294B2 (en) Method for notifying for D2D communication system and device therefor
KR20150079643A (ko) Ims 기반 서비스 연결 방법
WO2016205988A1 (zh) 数据传输的功率控制方法和装置
US10455443B2 (en) Method for transmitting a priority list reporting in a D2D communication system and device therefor
US10623532B2 (en) Method for indicating a priority for relay data in a D2D communication system and device therefor
US10667305B2 (en) Data transmission method and system
US10575335B2 (en) Method for contention resolution in a random access procedure in a D2D communication system and device therefor
US20180213384A1 (en) Method for requesting emergency service by roaming ue and method for processing same
EP3562235B1 (en) Service data transmission method and communication node
US10129079B2 (en) Telecommunications system and method
WO2019096393A1 (en) A client device, an access network device, a method and a computer program for establishing a data radio bearer

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: 16869897

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2016869897

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE