WO2017201677A1 - 数据传输的方法及装置 - Google Patents

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

Info

Publication number
WO2017201677A1
WO2017201677A1 PCT/CN2016/083198 CN2016083198W WO2017201677A1 WO 2017201677 A1 WO2017201677 A1 WO 2017201677A1 CN 2016083198 W CN2016083198 W CN 2016083198W WO 2017201677 A1 WO2017201677 A1 WO 2017201677A1
Authority
WO
WIPO (PCT)
Prior art keywords
service data
preset
qos
transmitted
granularity
Prior art date
Application number
PCT/CN2016/083198
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 EP16902667.1A priority Critical patent/EP3447978B1/en
Priority to BR112018073970A priority patent/BR112018073970A2/pt
Priority to CN201680086064.5A priority patent/CN109155762B/zh
Priority to PCT/CN2016/083198 priority patent/WO2017201677A1/zh
Publication of WO2017201677A1 publication Critical patent/WO2017201677A1/zh
Priority to US16/198,720 priority patent/US10721754B2/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/0268Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/50Allocation or scheduling criteria for wireless resources
    • H04W72/54Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/543Allocation or scheduling criteria for wireless resources based on quality criteria based on requested quality, e.g. QoS
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/16Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/12Wireless traffic scheduling
    • H04W72/1263Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/50Allocation or scheduling criteria for wireless resources
    • H04W72/56Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H04W72/569Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information

Definitions

  • the present invention relates to wireless communication technologies, and in particular, to a data transmission method and apparatus.
  • Qos Quality of Service
  • Qos Quality of Service
  • the terminal uses an uplink (UL) traffic flow template (TFT) to transport a user service data flow (Service Data Flow, SDF) is bound to an Evolved Packet System (EPS) bearer, and multiple SDFs can be complexed by including multiple uplink packet filters in the UL TFT.
  • UL uplink
  • EPS Evolved Packet System
  • P-GW Packet Data Network Gateway
  • DL downlink
  • the requirements of the QoS are ensured by the attributes of the EPS bearer.
  • the Mobility Management Entity (MME) of the core network provides the evolved radio access bearer to the radio network side (Evolved Radio).
  • the Access Bearer (E-RAB) Qos requirement parameter specifically the E-RAB Qos requirement parameter may include a Qos Classification Identifier (QCI), where different QCIs identify different Qos requirements.
  • QCI Qos Classification Identifier
  • the QoS requirements of multiple SDFs multiplexed to the same EPS bearer are the same, and the same level of QoS processing is used.
  • the Qos requirements of different services are not the same, and there is no way to meet the different Qos requirements of different services by using existing technologies.
  • the embodiment of the invention provides a method and a device for data transmission, which are used to solve the problem that different QoS requirements of different services are not met in the prior art.
  • a first aspect of the present invention provides a data transmission method, including:
  • the network element of the radio access network acquires preset granularity service data
  • the radio access network element performs the QoS requirement classification on the preset granularity service data, and determines the Qos requirement parameter corresponding to the classification of the preset granularity service data according to the QoS requirement parameter corresponding to the preset granularity service data.
  • the network element of the radio access network transmits the preset granularity service data according to the classification of the preset granularity service data.
  • the radio access network element obtains the Qos requirement parameter corresponding to the preset granularity service data, including:
  • the radio access network element obtains the Qos requirement parameter corresponding to the preset granularity service data according to the attribute information of the preset granularity service data and the preset QoS mapping relationship.
  • the attribute information of the preset granularity service data includes any one of the following or any combination thereof: preset feature information, preset identifier, and preset channel identifier.
  • the preset QoS mapping relationship is: mapping relationship between preset feature information and Qos requirement parameters;
  • the radio access network element obtains, by the radio access network element, the Qos requirement parameter corresponding to the preset granularity service data according to the attribute information of the preset granularity service data and the preset QoS mapping relationship, including:
  • the network element of the radio access network identifies characteristic information in the preset granularity service data
  • the radio access network element obtains the Qos requirement parameter corresponding to the preset granularity service data according to the characteristic information in the preset granularity service data and the mapping relationship between the preset feature information and the QoS requirement parameter.
  • the feature information includes one or any combination of the following: a port number of the protocol layer, a feature word, an association feature, and a data popularity; wherein the association feature refers to a plurality of feature words that are jointly identified.
  • the preset QoS mapping relationship is: a mapping relationship between the preset QoS identifier and the QoS requirement parameter;
  • the radio access network element obtains, by the radio access network element, the Qos requirement parameter corresponding to the preset granularity service data according to the attribute information of the preset granularity service data and the preset QoS mapping relationship, including:
  • the network element of the radio access network acquires the Qos identifier in the preset granularity service data according to a preset rule
  • the radio access network element obtains the Qos requirement parameter corresponding to the preset granularity service data according to the mapping between the Qos identifier in the preset granularity service data and the preset QoS identifier and the QoS requirement parameter.
  • the network element of the radio access network acquires the Qos identifier in the preset granularity service data according to a preset rule, including:
  • the network element of the radio access network acquires the Qos identifier in the data packet header of the preset granularity service data according to a preset rule.
  • the preset QoS mapping relationship is: mapping relationship between the preset channel identifier and the QoS requirement parameter;
  • the radio access network element obtains, by the radio access network element, the Qos requirement parameter corresponding to the preset granularity service data according to the attribute information of the preset granularity service data and the preset QoS mapping relationship, including:
  • the radio access network element determines a channel for receiving the preset granularity service data
  • the radio access network element obtains the Qos requirement parameter corresponding to the preset granularity service data according to the channel that receives the preset granularity service data and the mapping relationship between the preset channel identifier and the QoS requirement parameter.
  • the QoS requirement parameter includes at least one of the following or any combination thereof: a stream aggregation maximum bit rate AMBR, a radio bearer AMBR, a terminal AMBR, a priority, a time delay, a packet loss rate, a handover characteristic, a time-varying characteristic, Assign retention priority ARP.
  • the method before the acquiring, by the radio access network element, the QoS requirement parameter corresponding to the preset granularity service data, the method further includes:
  • the network element of the radio access network acquires Qos enhanced attribute information; correspondingly,
  • the radio access network element performs QoS enhancement attribute information according to the preset granularity service data, And the preset QoS mapping relationship, and the QoS requirement parameter corresponding to the preset granularity service data is obtained.
  • the QoS enhanced attribute information includes any one of the following or any combination thereof: a time varying attribute, a classification attribute, and a granularity attribute;
  • the time-varying attribute is used to identify whether the state of the service data in the service process changes with time, and whether the QoS requirement parameter changes with the state of the service data;
  • the classification attribute is used to identify whether the service data is classified according to the Qos requirement parameter;
  • the granularity attribute is used to identify the processing granularity of Qos.
  • the preset QoS mapping relationship includes: a mapping relationship between a state of the service data and a Qos requirement parameter;
  • the radio access network network element obtains, by the radio access network network element, the Qos requirement parameter corresponding to the preset granularity service data according to the QoS enhanced attribute information of the preset granularity service data, and the preset QoS mapping relationship, including:
  • the network element of the radio access network acquires the current service status of the preset granularity service data, including:
  • the network element of the radio access network determines the current service status of the preset granularity service data according to the service status change notification.
  • the radio access network element transmits the preset granularity service data according to the classification of the preset granularity service data, including:
  • the radio access network network element uses the Qos requirement parameter corresponding to the classification of the preset granularity service data as a scheduling input of the medium access control MAC layer, and transmits the preset granularity service data by using a MAC layer scheduling.
  • the method before the transmitting, by the radio access network element, the preset granularity service data according to the classification of the preset granularity service data, the method further includes:
  • the radio access network element generates a plurality of sub-radio bearers, and each sub-radio bearer corresponds to different Qos demand parameters;
  • the radio access network element selects the corresponding sub-radio bearer to transmit the preset granularity service data according to the QoS requirement parameter corresponding to the classification of the preset granularity service data and the mapping relationship between the sub-radio bearer and the QoS requirement parameter. .
  • the radio access network element transmits the preset granularity service data according to the classification of the preset granularity service data, including:
  • the radio access network element selects a processing template used by each protocol layer according to a Qos requirement parameter corresponding to the classification of the preset granularity service data, where different Qos requirement parameters corresponding to the processing template are different;
  • the radio access network element transmits the preset granularity service data according to a processing template used by each protocol layer.
  • the method further includes:
  • the network element of the radio access network acquires the preset QoS mapping relationship.
  • the method further includes:
  • the network element of the radio access network sends the preset QoS mapping relationship to the terminal.
  • a second aspect of the embodiments of the present invention provides a data transmission method, including:
  • the terminal acquires the preset granularity uplink service data to be transmitted
  • the terminal transmits the preset granularity uplink service data to be transmitted according to the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted.
  • the terminal acquires the Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted, including:
  • the terminal acquires a Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted according to the preset granularity uplink service data to be transmitted and the preset QoS mapping relationship.
  • the preset QoS mapping relationship is: a mapping relationship between the preset feature information and the Qos requirement parameter;
  • the terminal obtains the Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted according to the preset granularity of the uplink service data to be transmitted, and the preset QoS mapping relationship, including:
  • the terminal identifies the feature information of the preset granularity uplink service data to be transmitted;
  • the terminal according to the feature information of the preset granularity uplink service data to be transmitted, and the The mapping relationship between the preset feature information and the QoS requirement parameter is used to obtain the Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted.
  • the feature information includes one or any combination of the following: a port number of the protocol layer, a feature word, an association feature, and a data popularity; wherein the association feature refers to a plurality of feature words that are jointly identified.
  • the preset QoS mapping relationship is: a mapping relationship between a preset QoS identifier and a Qos requirement parameter;
  • the terminal obtains, by the terminal, the Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted, according to the preset granularity uplink service data to be transmitted, and the preset QoS mapping relationship, including:
  • the terminal And obtaining, by the terminal, the Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted, according to the mapping between the Qos identifier in the preset granularity uplink service data and the preset QoS identifier and the QoS requirement parameter. .
  • the QoS requirement parameter includes at least one of the following or any combination thereof: a stream aggregation maximum bit rate AMBR, a radio bearer AMBR, a terminal AMBR, a priority, a time delay, a packet loss rate, a handover characteristic, a time-varying characteristic, Assign retention priority ARP.
  • the terminal before the acquiring, by the terminal, the QoS requirement parameter corresponding to the preset granularity uplink service data, the terminal further includes:
  • the Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted including:
  • the terminal obtains, by the terminal, the Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted, according to the QoS enhanced attribute information corresponding to the preset granularity uplink service data to be transmitted, and the preset QoS mapping relationship.
  • the QoS enhanced attribute information includes any one of the following or any combination thereof: a time varying attribute, a classification attribute, and a granularity attribute;
  • the time-varying attribute is used to identify whether the state of the service data in the service process changes with time, and whether the Qos requirement parameter changes according to the state of the service data;
  • the classification attribute is used to identify the industry Whether the service data is classified according to the Qos requirement parameter;
  • the granularity attribute is used to identify the processing granularity of the Qos.
  • the terminal transmits the preset granularity uplink service data to be transmitted according to the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted, including:
  • the terminal adjusts a scheduling policy of the logical channel corresponding to the preset granularity uplink service data to be transmitted according to the QoS requirement parameter of the preset granularity uplink service data to be transmitted, and uses the adjusted logical channel to transmit to the RAN network element.
  • the preset granularity uplink service data to be transmitted is not limited to the QoS requirement parameter of the preset granularity uplink service data to be transmitted.
  • the terminal transmits the preset granularity uplink service data to be transmitted according to the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted, including:
  • the terminal maps the preset granularity uplink service data to be transmitted to the corresponding one according to the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted, and the mapping relationship between the preset QoS requirement parameter and the sub RB.
  • the sub-radio bearers are transmitted on the RB.
  • the terminal sends the preset granularity uplink service data to be transmitted according to the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted, and the mapping relationship between the preset QoS requirement parameter and the sub RB.
  • the transmission further includes:
  • the terminal receives a mapping relationship between the preset QoS requirement parameter and the sub RB sent by the RAN network element.
  • the terminal transmits the preset granularity uplink service data to be transmitted according to the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted, including:
  • the terminal uses the preset processing template corresponding to each protocol layer to transmit the preset granularity uplink service data to be transmitted, where different Qos requirement parameters corresponding to the preset processing template are different.
  • a third aspect of the embodiments of the present invention provides a data transmission method, including:
  • the core network control function entity CN CP generates a QoS QoS mapping relationship, where the QoS mapping relationship is used to indicate a mapping relationship between the preset granularity service data and the QoS requirement parameter;
  • the CN CP sends the QoS mapping relationship to the radio access network element.
  • the method further includes:
  • the CN CP sends the QoS mapping relationship to the terminal.
  • the QoS mapping relationship includes: mapping relationship between service data feature information and Qos requirement parameters.
  • the feature information includes one or any combination of the following: a port number of the protocol layer, a feature word, an association feature, and a data popularity; wherein the association feature refers to multiple features of the joint identification. Sign word.
  • the QoS mapping relationship includes: a mapping relationship between a Qos identifier and a Qos requirement parameter in the service data.
  • the preset QoS mapping relationship is: a mapping relationship between the preset channel identifier and the QoS requirement parameter.
  • the method further includes:
  • the CN CP sends at least one set of Qos requirement parameters to the core network user plane functional entity.
  • a fourth aspect of the embodiments of the present invention provides an apparatus for data transmission, including:
  • An obtaining module configured to acquire preset granularity service data
  • a determining module configured to obtain a Qos demand parameter corresponding to the preset granularity service data; classify the preset granularity service data into a Qos requirement, and determine the pre-determination according to the Qos requirement parameter corresponding to the preset granularity service data Setting a Qos requirement parameter corresponding to the classification of the granularity service data;
  • a transmission module configured to transmit the preset granularity service data according to the classification of the preset granularity service data.
  • the determining module is configured to obtain a Qos requirement parameter corresponding to the preset granularity service data according to the attribute information of the preset granularity service data and the preset QoS mapping relationship.
  • the attribute information of the preset granularity service data includes any one of the following or any combination thereof: preset feature information, preset identifier, and preset channel identifier.
  • the preset QoS mapping relationship is: mapping relationship between preset feature information and Qos requirements;
  • the determining module is specifically configured to identify the characteristic information in the preset granularity service data, and obtain the foregoing according to the characteristic information in the preset granularity service data and the mapping relationship between the preset feature information and the QoS requirement parameter.
  • the Qos requirement parameter corresponding to the preset granularity service data.
  • the feature information includes one or any combination of the following: a port number of the protocol layer, a feature word, an association feature, and a data popularity; wherein the association feature refers to a plurality of feature words that are jointly identified.
  • the preset QoS mapping relationship is: a mapping relationship between the preset QoS identifier and the QoS requirement parameter;
  • the determining module is specifically configured to acquire, in the preset granularity service data, according to a preset rule. And the Qos requirement parameter corresponding to the preset granularity service data is obtained according to the mapping between the Qos identifier in the preset granularity service data and the preset QoS identifier and the QoS requirement parameter.
  • the determining module is configured to obtain the Qos identifier in the preset granularity service data according to the preset rule, where the QoS identifier is obtained in the data packet header of the preset granularity service data according to the preset rule.
  • the preset QoS mapping relationship is: mapping relationship between the preset channel identifier and the QoS requirement parameter;
  • the determining module is specifically configured to determine a channel for receiving the preset granularity service data, and acquiring, according to the channel for receiving the preset granularity service data, and a mapping relationship between a preset channel identifier and a QoS requirement parameter, The Qos requirement parameter corresponding to the preset granularity service data.
  • the QoS requirement includes at least one of the following or any combination thereof: a flow aggregation maximum bit rate AMBR, a radio bearer AMBR, a terminal AMBR, a priority, a time delay, a packet loss rate, a handover characteristic, a time-varying characteristic, Assign retention priority ARP.
  • the device further includes:
  • a receiving module configured to receive and obtain QoS enhanced attribute information
  • the determining module is configured to obtain a Qos requirement parameter corresponding to the preset granularity service data according to the QoS enhanced attribute information of the preset granularity service data and the preset QoS mapping relationship.
  • the QoS enhanced attribute information includes any one of the following or any combination thereof: a time varying attribute, a classification attribute, and a granularity attribute;
  • the time-varying attribute is used to identify whether the state of the service data in the service process changes with time, and whether the QoS requirement parameter changes with the state of the service data;
  • the classification attribute is used to identify whether the service data is classified according to the Qos requirement parameter;
  • the granularity attribute is used to identify the processing granularity of Qos.
  • the preset QoS mapping relationship includes: a mapping relationship between a state of the service data and a Qos requirement parameter;
  • the determining module is specifically configured to obtain a current service state of the preset granularity service data, and determine, according to a current service state of the preset granularity service data, and a mapping relationship between a state of the service data and a Qos requirement parameter.
  • the Qos requirement parameter corresponding to the current service status of the preset granularity service data.
  • the receiving module is further configured to receive a service status change notification sent by the application layer server.
  • the determining module is further configured to determine a current service state of the preset granularity service data according to the service state change notification.
  • the transmission module is specifically configured to use the QoS requirement parameter corresponding to the classification of the preset granularity service data as a scheduling input of the medium access control MAC layer, and transmit the preset granularity service data by using a MAC layer scheduling.
  • the device further includes:
  • a generating module configured to generate multiple sub-radio bearers, where each sub-radio bearer corresponds to different Qos demand parameters; correspondingly,
  • the transmission module is configured to: according to the QoS requirement parameter corresponding to the classification of the preset granularity service data, and the mapping relationship between the sub-radio bearer and the QoS requirement parameter, select the corresponding sub-radio bearer to transmit the preset granularity service data. .
  • the transmitting module is specifically configured to select, according to the QoS requirement parameter corresponding to the classification of the preset granularity service data, a processing template used by each protocol layer, where different Qos requirements of the processing template are corresponding.
  • the parameters are different; the preset granularity service data is transmitted according to the processing template used by each protocol layer.
  • the acquiring module is further configured to acquire the preset QoS mapping relationship.
  • the transmitting module is further configured to send the preset QoS mapping relationship to the terminal.
  • a fifth aspect of the embodiments of the present invention provides an apparatus for data transmission, including:
  • the obtaining module is configured to obtain the preset granularity uplink service data to be transmitted;
  • a determining module configured to acquire a Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted;
  • the transmission module is configured to transmit the preset granularity uplink service data to be transmitted according to the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted.
  • the determining module is configured to obtain a Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted according to the preset granularity uplink service data to be transmitted and the preset QoS mapping relationship.
  • the preset QoS mapping relationship is: mapping relationship between preset feature information and Qos requirement parameters;
  • the determining module is specifically configured to identify feature information of the preset granularity uplink service data to be transmitted; and according to the feature information of the preset granularity uplink service data to be transmitted, and the preset feature information and the Qos requirement parameter.
  • the mapping relationship is obtained, and the Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted is obtained.
  • the feature information includes one or any combination of the following: a port number of the protocol layer, a feature word, an association feature, and a data popularity; wherein the association feature refers to a plurality of feature words that are jointly identified.
  • the preset QoS mapping relationship is: a mapping relationship between a preset QoS identifier and a Qos requirement parameter;
  • the determining module is configured to obtain a Qos identifier in the preset granularity uplink service data to be transmitted, and the Qos identifier in the uplink service data of the preset granularity to be transmitted, and the preset Qos identifier and the Qos requirement.
  • the mapping relationship between the parameters is obtained, and the Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted is obtained.
  • the QoS requirement includes at least one of the following or any combination thereof: a flow aggregation maximum bit rate AMBR, a radio bearer AMBR, a terminal AMBR, a priority, a time delay, a packet loss rate, a handover characteristic, a time-varying characteristic, Assign retention priority ARP.
  • the device further includes: a first receiving module, configured to receive Qos enhanced attribute information sent by the core network control function entity or the RAN network element;
  • the determining module is configured to obtain a Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted according to the QoS enhanced attribute information corresponding to the preset granularity uplink service data to be transmitted, and the preset QoS mapping relationship.
  • the QoS enhanced attribute information includes any one of the following or any combination thereof: a time varying attribute, a classification attribute, and a granularity attribute;
  • the time-varying attribute is used to identify whether the state of the service data in the service process changes with time, and whether the QoS requirement parameter changes with the state of the service data;
  • the classification attribute is used to identify whether the service data is classified according to the Qos requirement parameter;
  • the granularity attribute is used to identify the processing granularity of Qos.
  • the transmitting module is configured to adjust a scheduling policy of the logical channel corresponding to the preset granularity uplink service data to be transmitted according to the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted, and adopt the adjustment
  • the subsequent logical channel transmits the preset granularity uplink service data to be transmitted to the RAN network element.
  • the transmitting module is configured to: according to the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted, and the mapping relationship between the preset QoS requirement parameter and the sub-RB, the to-be-transmitted pre-transmission
  • the granularity uplink service data is mapped to the corresponding sub-radio bearer RB for transmission.
  • the device further includes: a second receiving module, configured to receive a mapping relationship between the preset QoS requirement and the sub-RB sent by the RAN network element.
  • the transmitting module is configured to perform QoS processing on the preset granularity uplink service data to be transmitted by using a preset processing template corresponding to each protocol layer, and uplink the processed preset granularity to be transmitted.
  • the service data is sent to the RAN network element.
  • a sixth aspect of the embodiments of the present invention provides an apparatus for data transmission, including:
  • a generating module configured to generate a QoS mapping relationship, where the QoS mapping relationship is used to indicate a mapping relationship between the preset granularity service data and the QoS requirement parameter;
  • a sending module configured to send the QoS mapping relationship to the radio access network element.
  • the sending module is further configured to send the QoS mapping relationship to the radio access network element.
  • the QoS mapping relationship includes: mapping relationship between service data feature information and Qos requirements.
  • the service data feature information includes one or any combination of the following: a port number of the protocol layer, a feature word, an association feature, and a data popularity; wherein the association feature refers to multiple feature words jointly identified. .
  • the QoS mapping relationship includes: a mapping relationship between a Qos identifier and a Qos requirement parameter in the service data.
  • the preset QoS mapping relationship is: a mapping relationship between the preset channel identifier and the QoS requirement parameter.
  • the sending module is further configured to send at least one set of Qos requirement parameters to the core network user plane function entity.
  • a seventh aspect of the embodiments of the present invention provides an apparatus for data transmission, including: a memory, a processor, a receiver, and a transmitter. Wherein: the memory, the processor, the receiver, and the transmitter are connected by a bus.
  • a processor configured to acquire a preset granularity service data, obtain a Qos requirement parameter corresponding to the preset granularity service data, and classify the preset granularity service data into a Qos requirement, and according to the
  • the QoS requirement parameter corresponding to the preset granularity service data is determined by the QoS requirement parameter corresponding to the preset granularity service data; and the preset granularity service data is transmitted according to the classification of the preset granularity service data.
  • the processor is configured to obtain a Qos requirement parameter corresponding to the preset granularity service data according to the attribute information of the preset granularity service data and the preset QoS mapping relationship.
  • the attribute information of the preset granularity service data includes any one of the following or any combination thereof: preset feature information, preset identifier, and preset channel identifier.
  • the preset QoS mapping relationship is: mapping relationship between preset feature information and Qos requirements;
  • the processor is specifically configured to identify the characteristic information in the preset granularity service data, and obtain the preset granularity according to the characteristic information in the preset granularity service data and the mapping relationship between the preset feature information and the QoS requirement parameter.
  • the Qos requirement parameter corresponding to the business data.
  • the feature information includes one or any combination of the following: a port number of the protocol layer, a feature word, an association feature, and a data popularity; wherein the association feature refers to a plurality of feature words that are jointly identified.
  • the preset QoS mapping relationship is: a mapping relationship between the preset QoS identifier and the QoS requirement parameter;
  • the processor is configured to obtain a Qos identifier in the preset granularity service data according to a preset rule, and a mapping relationship between the Qos identifier in the preset granularity service data and the preset Qos identifier and the Qos requirement parameter. Obtaining a Qos requirement parameter corresponding to the preset granularity service data.
  • the processor is configured to obtain the Qos identifier in the preset granularity service data according to the preset rule, where the QoS identifier is obtained in the data packet header of the preset granularity service data according to the preset rule.
  • the preset QoS mapping relationship is: a mapping relationship between the preset channel identifier and the QoS requirement parameter; the processor is specifically configured to determine a channel that receives the preset granularity service data; The channel of the preset granularity service data, and the mapping relationship between the preset channel identifier and the QoS requirement parameter, and obtains the Qos requirement parameter corresponding to the preset granularity service data.
  • the QoS requirement includes at least one of the following or any combination thereof: a flow aggregation maximum bit rate AMBR, a radio bearer AMBR, a terminal AMBR, a priority, a time delay, a packet loss rate, Switching characteristics, time-varying characteristics, and assigning retention priority ARP.
  • the receiver is configured to receive and obtain QoS enhanced attribute information
  • the processor is specifically configured to obtain a Qos requirement parameter corresponding to the preset granularity service data according to the QoS enhanced attribute information of the preset granularity service data and the preset QoS mapping relationship.
  • the QoS enhanced attribute information includes any one of the following or any combination thereof: a time varying attribute, a classification attribute, and a granularity attribute;
  • the time-varying attribute is used to identify whether the state of the service data in the service process changes with time, and whether the QoS requirement parameter changes with the state of the service data;
  • the classification attribute is used to identify whether the service data is classified according to the Qos requirement parameter;
  • the granularity attribute is used to identify the processing granularity of Qos.
  • the preset QoS mapping relationship includes: a mapping relationship between a state of the service data and a Qos requirement parameter;
  • the processor is specifically configured to obtain a current service state of the preset granularity service data, and determine, according to a current service state of the preset granularity service data, and a mapping relationship between a state of the service data and a Qos requirement parameter, The Qos requirement parameter corresponding to the current service status of the granularity service data.
  • the receiver is further configured to receive a service status change notification sent by the application layer server
  • the processor is further configured to determine, according to the service status change notification, a current service status of the preset granularity service data.
  • the processor is configured to use the QoS requirement parameter corresponding to the classification of the preset granularity service data as a scheduling input of the medium access control MAC layer, and transmit the preset granularity service data by using a MAC layer scheduling.
  • the processor is further configured to generate multiple sub-radio bearers, where each sub-radio bearer corresponds to different Qos requirement parameters. And selecting a corresponding sub-radio bearer to transmit the preset granularity service data according to the QoS requirement parameter corresponding to the classification of the preset granularity service data and the mapping relationship between the sub-radio bearer and the QoS requirement parameter.
  • the processor is configured to: according to the Qos requirement parameter corresponding to the classification of the preset granularity service data, select a processing template used by each protocol layer, where different Qos requirement parameters corresponding to the processing template are different. And transmitting, according to the processing template used by each protocol layer, the preset granularity service data.
  • the processor is further configured to acquire the preset QoS mapping relationship.
  • the transmitter is configured to send the preset QoS mapping relationship to the terminal.
  • An eighth aspect of the embodiments of the present invention provides an apparatus for data transmission, including: a memory, a processor, a receiver, and a transmitter. among them:
  • the memory, processor, receiver, and transmitter are connected by a bus.
  • the processor is configured to obtain the preset granularity uplink service data to be transmitted, obtain the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted, and transmit according to the Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted.
  • the preset granularity uplink service data to be transmitted is configured to obtain the preset granularity uplink service data to be transmitted.
  • the processor is configured to obtain the Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted according to the preset granularity uplink service data to be transmitted and the preset QoS mapping relationship.
  • the preset QoS mapping relationship is: a mapping relationship between the preset feature information and the QoS requirement parameter; the processor is specifically configured to identify the feature information of the preset granularity uplink service data to be transmitted; The feature information of the preset granularity uplink service data is forwarded, and the mapping relationship between the preset feature information and the QoS requirement parameter is obtained, and the Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted is obtained.
  • the feature information includes one or any combination of the following: a port number of the protocol layer, a feature word, an association feature, and a data popularity; wherein the association feature refers to a plurality of feature words that are jointly identified.
  • the preset QoS mapping relationship is: a mapping relationship between the preset QoS identifier and the QoS requirement parameter; the processor is configured to obtain the Qos identifier in the preset granularity uplink service data to be transmitted; And the QoS requirement parameter of the preset granularity uplink service data to be transmitted is obtained by the QoS identifier of the preset granularity uplink service data to be transmitted and the mapping relationship between the preset QoS identifier and the QoS requirement parameter.
  • the QoS requirement parameter includes at least one of the following or any combination thereof: a stream aggregation maximum bit rate AMBR, a radio bearer AMBR, a terminal AMBR, a priority, a time delay, a packet loss rate, a handover characteristic, a time-varying characteristic, Assign retention priority ARP.
  • the receiver is configured to receive the QoS enhanced attribute information sent by the core network control function entity or the RAN network element, where the processor is configured to: according to the Qos enhanced attribute information corresponding to the preset granularity uplink service data to be transmitted, And the preset QoS mapping relationship, and the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted is obtained.
  • the QoS enhanced attribute information includes any one of the following or any combination thereof: a time varying attribute, a classification attribute, and a granularity attribute;
  • the time-varying attribute is used to identify whether the state of the service data in the service process changes with time, and whether the QoS requirement parameter changes with the state of the service data;
  • the classification attribute is used to identify whether the service data is classified according to the Qos requirement parameter;
  • the granularity attribute is used to identify the processing granularity of Qos.
  • the processor adjusts a scheduling policy of the logical channel corresponding to the preset granularity uplink service data to be transmitted according to the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted, and adopts the adjusted logical channel direction.
  • the RAN network element transmits the preset granularity uplink service data to be transmitted.
  • the processor is configured to: according to the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted, and the mapping relationship between the preset QoS requirement parameter and the sub RB, the preset granularity to be transmitted.
  • the uplink service data is mapped to the corresponding sub-radio bearer RB for transmission.
  • the receiver is configured to receive a mapping relationship between the preset QoS requirement sent by the RAN network element and the sub RB.
  • the processor is configured to perform QoS processing on the preset granularity uplink service data to be transmitted by using a preset processing template corresponding to each protocol layer, and process the processed preset granularity uplink service data to be transmitted. Send to the RAN network element.
  • a ninth aspect of the embodiments of the present invention provides an apparatus for data transmission, including: a memory, a processor, a receiver, and a transmitter. among them:
  • the memory, processor, receiver, and transmitter are connected by a bus.
  • a processor configured to generate a QoS mapping relationship, where the QoS mapping relationship is used to indicate a mapping relationship between the preset granularity service data and the QoS requirement parameter;
  • a transmitter configured to send the QoS mapping relationship to the radio access network element.
  • the transmitter is further configured to send the QoS mapping relationship to the radio access network element.
  • the QoS mapping relationship includes: mapping relationship between service data feature information and Qos requirements.
  • the feature information includes one or any combination of the following: a port number of the protocol layer, a feature word, an association feature, and a data popularity; wherein the association feature refers to a plurality of feature words that are jointly identified.
  • the QoS mapping relationship includes: a mapping relationship between a Qos identifier and a Qos requirement parameter in the service data.
  • the preset QoS mapping relationship is: a mapping relationship between the preset channel identifier and the QoS requirement parameter.
  • the transmitter is further configured to send at least one set of Qos requirement parameters to the core network user plane function entity.
  • the RAN network element obtains the preset granularity service data, and further the RAN network element obtains the QoS requirement parameter of the preset granularity service data, and performs Qos on the preset granularity service data. Determining the requirements, determining the QoS requirement parameters corresponding to the classification of the preset granularity service data, and then the RAN network element transmits the preset granularity service data according to the classification of the preset granularity service data, so that the RAN network element can learn different presets. After the preset QoS service data is received, the preset QoS service data is respectively transmitted according to the classification of the preset granularity service data to meet the Qos of different preset granularity service data. demand.
  • FIG. 1 is a schematic diagram of an application scenario of a data transmission method provided by the present invention.
  • Embodiment 1 of a method for data transmission provided by the present invention
  • Embodiment 3 is a schematic flowchart of Embodiment 2 of a method for data transmission provided by the present invention
  • Embodiment 4 is a schematic flowchart of Embodiment 3 of a method for data transmission provided by the present invention.
  • FIG. 5 is a schematic diagram of a processing scenario of a data transmission method provided by the present invention.
  • FIG. 6 is a schematic diagram of another processing scenario of a method for data transmission provided by the present invention.
  • FIG. 7 is a schematic diagram of another processing scenario of a method for data transmission provided by the present invention.
  • FIG. 8 is a schematic diagram of another processing scenario of a method for data transmission provided by the present invention.
  • FIG. 9 is a schematic flowchart diagram of Embodiment 4 of a method for data transmission according to the present invention.
  • FIG. 10 is a schematic structural diagram of Embodiment 1 of a device for data transmission according to the present invention.
  • FIG. 11 is a schematic structural diagram of Embodiment 2 of a device for data transmission according to the present invention.
  • Embodiment 3 of a device for data transmission according to the present invention.
  • FIG. 13 is a schematic structural diagram of Embodiment 4 of a device for data transmission according to the present invention.
  • Embodiment 5 of a device for data transmission according to the present invention.
  • Embodiment 6 is a schematic structural diagram of Embodiment 6 of a device for data transmission according to the present invention.
  • Embodiment 7 of a device for data transmission according to the present invention.
  • FIG. 17 is a schematic structural diagram of Embodiment 1 of a radio access network element according to the present invention.
  • FIG. 18 is a schematic structural diagram of Embodiment 1 of a terminal provided by the present invention.
  • FIG. 19 is a schematic structural diagram of Embodiment 1 of a core network element provided by the present invention.
  • the terminal in the embodiment of the present invention may be a wireless terminal or a wired terminal, and the wireless terminal may be a device that provides voice and/or other service data connectivity to the user, a handheld device with wireless connection function, or is connected to the wireless device. Other processing devices for the modem.
  • the wireless terminal can communicate with one or more core networks via a Radio Access Network (RAN), which can be a mobile terminal, such as a mobile phone (or "cellular" phone) and a mobile terminal.
  • RAN Radio Access Network
  • the computer for example, can be a portable, pocket, handheld, computer built-in or in-vehicle mobile device that exchanges language and/or data with the wireless access network.
  • the wireless terminal may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, and a remote terminal.
  • the access terminal, the user terminal (User Terminal), the user agent (User Agent), and the user device (User Device or User Equipment) are not limited herein.
  • FIG. 1 is a schematic diagram of an application scenario of a data transmission method according to the present invention.
  • the method is applied to a communication system, and the communication system may be a LTE system, or may be a next-generation communication system in the future, and is not limited herein.
  • the system may include: a Core Network (CN), a Radio Access Network (RAN), and a terminal.
  • CN Core Network
  • RAN Radio Access Network
  • the network element of the core network may include a core network control plane (CN CP) and a core network user plane (CN UP).
  • CN CP core network control plane
  • CN UP core network user plane
  • the RAN may further include a RAN controller in addition to the RAN network element. It can be determined according to the specific situation, not every scene needs RAN controller.
  • the core network may include: a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), and a Serving Gateway. , referred to as S-GW) and other network elements.
  • MME Mobility Management Entity
  • P-GW Packet Data Network Gateway
  • S-GW Serving Gateway
  • the CN CP can also communicate with the application layer server.
  • system to which the embodiments of the present invention are applied may also include some auxiliary entities, such as HSS, OAM, PCRF, and the like.
  • the CN CP is responsible for the functions of session management, mobility management, QoS control, and contract information management of the terminal;
  • CN UP is responsible for functions such as service data forwarding
  • the RAN controller is responsible for the control of the RAN, and may specifically include: resource allocation, mobility management, and the like;
  • the RAN network element may be a base station, and has functions of service establishment and mobility, and service data scheduling;
  • the terminal has functions of transmitting, receiving, and measuring data.
  • the RAN network element includes, but is not limited to, a base station and/or a terminal.
  • the network element of the core network notifies the network element of the radio access network of different QoS requirements of different services, that is, the radio access network element can obtain a finer-grained Qos requirement, and performs Qos for different service data. Processed to better meet the actual Qos needs of different businesses.
  • the RAN network element obtains the preset granularity service data, performs QoS classification according to the QoS requirement parameter of the preset granularity service data, and transmits the preset granularity service data according to the QoS classification of the preset granularity service data.
  • FIG. 2 is a schematic flowchart of Embodiment 1 of a data transmission method according to the present invention. As shown in FIG. 2, the method includes:
  • the CN UP receives the service data sent by the application layer server.
  • the CN UP divides the service data into at least one preset granularity service data according to a preset granularity.
  • the preset granularity of the CN UP partition may be: flow, and/or RB. This preset granularity can be pre-configured to CN UP. However, the preset granularity may also be an Evolved Radio Access Bearer (E-RAB), a session, or the like.
  • E-RAB Evolved Radio Access Bearer
  • the Qos requirements of the preset granularity service data are different, and may refer to different Qos requirements of the same E-RAB, the same bear, the same flow, the same type, or the same session data and other data.
  • the WeChat red envelope service is different from the Qos requirements of other services.
  • the business data of a very important person (VIP) user is different from the Qos requirement of other business data.
  • VIP very important person
  • the CN UP sends the preset granularity service data to the RAN network element.
  • the RAN network element receives the preset granularity service data sent by the CN UP.
  • the CN UP may send the service data to the RAN network element, and the RAN network element divides the service data into the preset granularity service data, which is not limited herein.
  • the RAN network element acquires a Qos requirement parameter corresponding to the preset granularity service data.
  • the RAN network element obtains the Qos requirement parameter corresponding to the preset granularity service data according to the attribute information corresponding to the preset granularity service data and the preset preset QoS mapping relationship.
  • the attribute information may include one or any combination of the following: preset feature information, preset identifier, and preset channel identifier.
  • the preset QoS mapping relationship may be notified to the RAN network element by the CN CP, and after receiving the preset granularity service data, the RAN may obtain different preset granularities according to different preset granularity service data and preset QoS mapping relationship. Different Qos demand parameters corresponding to the business data.
  • the Qos requirement parameter includes at least one of the following or any combination thereof: flow aggregation Maximum bit rate (AMBR), radio bearer (RB-AMBR), terminal AMBR, priority, delay characteristics, packet loss characteristics, handover characteristics, time-varying characteristics, and Allocation and Retention Priority (ARP).
  • AMBR flow aggregation Maximum bit rate
  • RB-AMBR radio bearer
  • ARP Allocation and Retention Priority
  • Each set of QoS requirements reflects different QoS requirements.
  • the specific QoS requirements are: different flow-AMBR, different RB-AMBR, different AMBRs, different priorities, different delays, different rate of packet loss rate, and allocation.
  • the handover performance refers to one or more of the requirements of the service for the handover performance, such as the requirement of handover delay, the requirement of packet loss rate, and the requirement of sesssion continuity.
  • the handover here may specifically refer to handover of the terminal between cells.
  • the RAN network element performs Qos processing on the preset granularity service data according to the QoS requirement parameter of the preset granularity service data.
  • the RAN network element performs the QoS processing on the preset granularity service data according to the QoS requirement parameter of the preset granularity service data, where the RAN network element performs the Qos requirement classification on the preset granularity service data, and according to The QoS requirement parameter corresponding to the preset granularity service data is used to determine the QoS requirement parameter corresponding to the classification of the preset granularity service data; and the RAN network element transmits the preset granularity service data according to the classification of the preset granularity service data.
  • the CN UP may add a classification label to each preset granularity service data, or use different channels to send different classified preset granularity service data, that is, the service data of the same QoS requirement is sent by the same channel, so as to facilitate the RAN.
  • the network element classifies the above-mentioned preset granularity service data into Qos requirements.
  • the QoS element After the RAN network element obtains different QoS parameters corresponding to different service data, the QoS element can be differentiated according to the Qos requirement parameters of different service data to meet different Qos requirements of different services.
  • the RAN network element obtains the preset granularity service data, and further the RAN network element obtains the QoS requirement parameter of the preset granularity service data, and performs the Qos requirement classification on the preset granularity service data, and determines the preset granularity service data.
  • the QoS requirement parameter corresponding to the classification and the RAN network element transmits the preset granularity service data according to the classification of the preset granularity service data, so that the RAN network element can obtain different QoS requirement parameters corresponding to different preset granularity service data.
  • the preset granularity service data is respectively transmitted according to the classification of the preset granularity service data to meet the Qos requirement of the service data of different preset granularities.
  • the CN UP sends the preset granularity service data to the RAN network element, where the CN UP may be separately sent according to different QoS requirement parameters corresponding to the preset granularity service data.
  • the CN CP can send multiple sets of Qos demand parameters to the CN UP.
  • the CNUP may determine the Qos requirement parameter corresponding to the preset granularity service data according to the multiple sets of Qos requirement parameters and the mapping relationship between the Qos requirement parameters and the data features.
  • the CN UP may combine some other information of each data packet, such as an Internet Protocol (IP) address, a destination IP address, a source port address, a destination port address, etc., to determine the Qos requirement of each data packet. .
  • IP Internet Protocol
  • the CN UP adds different Qos identifiers to the preset granularity service data corresponding to the different QoS requirement parameters, so that the RAN network element can determine the Qos requirement parameter corresponding to the preset granularity service data according to the QoS identifier.
  • the QoS requirement parameter represented by each QoS identifier needs to be notified to the RAN side network element first.
  • the CN CP may notify the CN UP and the RAN network element of the correspondence between the QoS identifier and the preset granularity (flow, and/or RB).
  • the CN UP identifies the "flow, and/or RB" to which each data packet belongs. If at least one data packet belongs to the same flow or the same RB, or both belong to the same flow and belong to the same RB, CN UP will At least one packet is tagged with the same QoS.
  • the CN UP sends the preset granularity service data corresponding to the different QoS requirement parameters to the RAN network element by using a plurality of different channels, where each channel corresponds to a set of Qos requirement parameters, that is, the Qos can be used.
  • the preset granularity service data with the same requirement parameter is sent in one channel, and the RAN network element can determine the Qos requirement parameter corresponding to the preset granularity service data according to the channel that receives the preset granularity service data.
  • the QoS requirement parameter represented by each channel identifier needs to be notified to the RAN side network element first.
  • the CN CP may notify the CN UP and the RAN network element of the correspondence between the channel identifier and the preset granularity (flow, and/or RB).
  • the CN UP identifies the channel corresponding to each data packet. Specifically, if at least one data packet belongs to the same flow or the same RB, or belongs to the same flow and belongs to the same RB, the CN UP will use the at least one data packet.
  • the RAN network element is sent through the same channel.
  • the CN CP sends a mapping relationship between the QoS requirement parameter and the filtering template parameter to the RAN network element in advance, so that the RAN network element establishes corresponding filtering according to the mapping relationship between the QoS requirement parameter and the filtering template parameter. template.
  • the RAN network element filters each received data packet into a queue corresponding to different QoS requirement parameters, that is, the RAN network element puts each data packet received into the queue corresponding to the classified category.
  • the RAN network element including the RAN data processing entity on the base station side, also includes the terminal, and the terminals described herein include various types such as an ordinary terminal, a low-capability terminal, and a super power-saving terminal.
  • the CN CP may notify the CN UP and the RAN network element of the correspondence between the used filter template parameters and the preset granularity (flow, and/or RB).
  • the CN CP may send the QoS requirement parameter to the CN UP at the beginning of the service.
  • the QoS requirement parameter in the subsequent service process is no longer changed, and is applicable to a service with little fluctuation in data volume and no change in QoS, but not
  • the CN CP sends the Qos demand parameter to the CN UP at the beginning of the service, and periodically sends the updated QoS demand parameter to the CN UP, which is suitable for the regular fluctuation of the data volume and the regular change of the QoS demand; or
  • the CN CP sends the Qos demand parameter to the CN UP at the beginning of the service, and then sends the updated Qos demand parameter to the CN UP according to actual needs, triggering the CN UP to change the Qos demand parameter, which is applicable to the fluctuation of the data volume, and the QoS demand changes irregularly.
  • the CN CP may also send the foregoing Qos requirement parameter to the RAN network element in a similar manner as described above.
  • the CN CP may also send the above Qos demand parameter to the terminal in a similar manner as described above.
  • the CN CP can send the Qos requirement parameters to different network elements at different times, and is not limited herein.
  • the Qos demand parameter may include any one of the following or any combination thereof: flow aggregation maximum bit rate (AMBR), radio bearer (RB-AMBR), terminal AMBR, priority, time delay, packet loss rate, handover characteristics Time-varying characteristics, allocation retention priority ARP.
  • AMBR flow aggregation maximum bit rate
  • RB-AMBR radio bearer
  • terminal AMBR priority
  • priority time delay
  • packet loss rate packet loss rate
  • handover characteristics Time-varying characteristics
  • allocation retention priority ARP allocation retention priority
  • the flow AMBR can be understood as: the overall maximum bit rate of some flows, that is, one or more flows as a whole, and the sum of the bit rates of these flows cannot be greater than a certain maximum threshold, if the Qos requirement parameter This parameter is included, and a "flow collection” is also required. This "flow collection" includes one or more flows.
  • RB-AMBR is: the overall maximum bit rate of some RBs, that is, one or more RBs are considered as a whole, and the sum of the bit rates of these RBs cannot be greater than a certain maximum threshold, if the Qos requirement parameter includes this A parameter, which also needs to indicate an "RB set", which includes one or more RBs.
  • the CN CP may generate multiple sets of Qos requirement parameters according to the service characteristic parameters.
  • the service characteristic parameter may include any one of the following or any combination thereof: QoS information based on registration information, QoS information based on local operators, QoS information based on network fragmentation, QoS information based on application services, and the like.
  • the service characteristic parameter may be sent by the application server to the CN CP; or the service subscriber parameter may be configured in advance by the Home Subscriber Server (HSS); or the operation administration and maintenance (Operation Administration and Maintenance (OAM for short) configures the service feature parameters for the CN CP in advance.
  • HSS Home Subscriber Server
  • OAM Opera administration and maintenance
  • the CN CP may generate multiple sets of Qos requirement parameters according to the service characteristic parameter and adopt a Radio Resource Management (RRM) algorithm, which is not limited herein.
  • RRM Radio Resource Management
  • the method further includes: the CN CP generates the preset QoS mapping relationship, and sends the preset QoS mapping relationship to the radio access network element.
  • the CN CP can also directly send the preset QoS mapping relationship to the terminal.
  • the CN CP may perform the foregoing preset Qos through a process such as a nitial Context Setup, an E-RAB Setup, and an E-RAB Modify.
  • the mapping relationship is notified to the RAN network element, and/or the terminal.
  • the core network element may send the preset QoS mapping relationship to the RAN network element during the service establishment or the service modification process.
  • the core network element sends the preset QoS mapping relationship to the RAN network element in any process related to the terminal/service.
  • the RAN network element may also forward the preset QoS mapping relationship to the terminal, that is, the RAN network element may also send the preset QoS mapping relationship to the terminal, and after receiving the service data, the terminal performs corresponding Qos. deal with.
  • the foregoing preset QoS mapping relationship may be in various forms.
  • the method for the RAN network element to obtain the Qos requirement parameter corresponding to the preset granularity service data is also different.
  • the preset QoS mapping relationship is: a mapping relationship between preset feature information and a Qos requirement parameter.
  • preset feature information is used to describe features of the business data.
  • the CN CP may obtain application layer information of different service data, or may obtain application layer information of different service data by interacting with the application server, and obtain different Qos requirement parameters of different service data, for example, acquiring the same Bearer, the same
  • the different Qos requirements of the flow, the same type, or different service data in the same session, and the corresponding Qos requirement parameters are different, and then the mapping relationship between the preset feature information and the Qos requirement parameter is generated.
  • the CN CP After obtaining the application layer information of different service data, the CN CP can obtain the Qos requirement parameter of the different service data according to the preset rule, and can also negotiate with the application server to obtain the Qos requirement parameter of the different service data.
  • the core network element reads the application layer data information of the WeChat service, and obtains different Qos requirement parameters corresponding to different service data, such as WeChat voice, WeChat text, and WeChat red packet, according to preset rules.
  • the preset rule may include a mapping relationship between different service data and different QoS requirements.
  • the core network element may negotiate with the WeChat server to preset the Qos requirements of different service data in the WeChat service, such as different QoS requirements of different service data such as WeChat voice, WeChat text, and WeChat red envelope.
  • the RAN network element obtains according to the attribute information corresponding to the preset granularity service data and a preset preset QoS mapping relationship.
  • the QoS requirement parameter corresponding to the preset granularity service data may include:
  • the RAN network element identifies feature information in the preset granularity service data.
  • the RAN network element obtains a Qos requirement parameter corresponding to the preset granularity service data according to the feature information in the preset granularity service data and the mapping relationship between the preset feature information and the QoS requirement parameter.
  • the RAN network element after receiving the preset granularity service data, the RAN network element first identifies the feature information, and then obtains the Qos requirement parameter corresponding to the service data according to the mapping relationship between the preset feature information and the QoS requirement parameter.
  • mapping relationship may be specifically stipulated by a protocol, and is not limited herein.
  • the foregoing feature information may include: one or any combination of the following: an IP address, a port number, a feature word, an association feature, and a data behavior of the protocol layer.
  • the port number of the protocol layer may be a special port number in the Transmission Control Protocol (TCP), which is not limited herein, and may be a port number of another protocol layer.
  • TCP Transmission Control Protocol
  • the feature word may be a message feature word of the HyperText Transfer Protocol (HTTP), such as “GET”, “POST”, “HTTP/1.1”, “HOST” and the like, and is not limited herein.
  • HTTP HyperText Transfer Protocol
  • An association feature refers to the joint recognition of multiple feature words.
  • Data prevalence is the behavior identification of the data stream. For example, it includes one or any combination of the following: the range of the port in the packet, the packet length statistics (the packet length sequence, the packet length set, and the packet length). Range, average packet length, summation of round message length, etc.), frequency of message transmission, proportion of message transmission and reception, and degree of dispersion of destination address.
  • the preset QoS mapping relationship is: a mapping relationship between the preset QoS identifier and the QoS requirement parameter.
  • the RAN network element obtains the foregoing according to the attribute information corresponding to the preset granularity service data and a preset preset QoS mapping relationship.
  • the Qos requirement parameter corresponding to the preset granularity service data may include:
  • the RAN network element obtains the Qos identifier in the preset granularity service data according to a preset rule.
  • the QoS identifier may be carried in a protocol layer header of the preset granularity service data packet, where the preset granularity service data packet carries the foregoing preset granularity service data.
  • the preset rule may include a location indication of the Qos identifier, that is, which bit is specifically indicated as the Qos identifier.
  • the RAN network element obtains the Qos identifier in the preset granularity service data according to the preset rule, and the RAN network element obtains the Qos identifier in the data packet header of the preset granularity service data according to the preset rule.
  • the RAN network element obtains the Qos identifier in the data packet header of the preset granularity service data according to the preset rule.
  • a TCP header is reserved for 6 bits, a GTPU header extension space, a DSCP field in IP, and the like as a QoS flag.
  • different values of the DSCP domain correspond to different QoS requirement parameters, for example, 00000001 identifies a set of QoS requirement parameters, and 00000011 identifies another set of QoS requirement parameters, which is not limited herein, and may be flexibly performed according to Qos specific processing granularity or Qos requirements. set up.
  • the RAN network element is configured according to the Qos identifier in the preset granularity service data, and presets.
  • the mapping between the Qos identifier and the QoS requirement parameter is used to obtain the Qos requirement parameter corresponding to the preset granularity service data.
  • the CN CP may preset multiple sets of sub-Qos demand parameters, and each set of Qos requirement parameters may include one or any combination of the following: flow AMBR, RB-AMBR, terminal AMBR, priority, delay characteristics, packet loss characteristics, Switching characteristics, time-varying characteristics, ARP, etc. are not limited herein.
  • the RAN network element After receiving the preset granularity service data packet carrying the preset granularity service data, the RAN network element obtains the Qos identifier, and then obtains the Qos corresponding to the preset granularity service data according to the mapping relationship between the preset QoS identifier and the QoS requirement parameter.
  • the demand parameter so that the QoS requirement of the above preset granularity business data can be further known.
  • the foregoing QoS mapping relationship is: mapping relationship between the preset channel identifier and the QoS requirement parameter.
  • the CN UP uses different channels to send preset granularity service data of different QoS requirements. That is, the preset granularity service data corresponding to the same set of QoS requirements can be sent by the same channel.
  • the foregoing RAN network element obtains the QoS requirement parameter corresponding to the preset granularity service data according to the attribute information corresponding to the preset granularity service data, and the preset preset QoS mapping relationship, and may include: the RAN network element determines to receive the foregoing The channel of the preset granularity service data is obtained according to the channel that receives the preset granularity service data, and the mapping relationship between the preset channel identifier and the QoS requirement parameter, and obtains the Qos requirement parameter corresponding to the preset granularity service data.
  • the RAN network element before the RAN network element obtains the QoS requirement parameter corresponding to the preset granularity service data, the RAN network element further receives the QoS enhanced attribute information sent by the core network element.
  • the RAN network element obtains the QoS requirement parameter corresponding to the preset granularity service data, and the RAN network element obtains the preset granularity according to the QoS enhanced attribute information of the preset granularity service data and the preset QoS mapping relationship.
  • the Qos requirement parameter corresponding to the business data corresponds to the QoS requirement parameter corresponding to the business data.
  • the foregoing Qos enhanced attribute information includes any one of the following or any combination thereof: a time varying attribute, a classification attribute, and a granularity attribute.
  • time-varying attribute is used to identify whether the state of the service data in the service process changes with time, and whether the QoS requirement parameter changes with the state of the service data.
  • the change in the Qos demand parameter may be a change in the content of the Qos demand parameter, and/or a change in the value of a particular parameter.
  • video services will have different Qos requirements in different time dimensions, such as in the prelude, drama
  • the QoS requirements of the content, advertisement, and subtitles sections may be different, and the QoS requirements of the location packets at different times when dragging the video are also different, and the RAN may consider different processing methods; for example, the video service data packet belongs to the advertisement part, Use Qos processing different from the scenario content packet.
  • Voice calls may require Qos to remain stable throughout the call, ie Qos requirements do not change with the state of the business data.
  • Different parts of the same service data may also have different requirements for QoS, and the service data needs to be classified according to the Qos demand parameter. Even the same time period of the same business may correspond to different Qos demand parameters.
  • the preset field may be extended in the preset granularity service data as the classification information identifier to specifically identify the classification information of different parts in the service data.
  • the application layer may indicate the classification information identifier in the service data to the RAN network element.
  • the Qos requirements can be different.
  • the granularity of Qos processing can also be different. For example, it can be processed according to the granularity of "per bearer", or according to the granularity of "flow”. Processing, or, can also be handled according to the "package" granularity, but not limited to this.
  • the RAN network element obtains the preset granularity according to the type of the preset granularity service data, other parameters that identify the nature of the service data, and the preset QoS mapping relationship.
  • the RAN network element may select a filtering template of different granularity according to the processing granularity specifically indicated by the granularity attribute. For example, if the granularity of the traffic is used to process the preset granularity service data, the preset granularity service data is filtered by using a “flow” granularity filtering template to obtain different flows.
  • the CN UP can send coarser-grained service data to the RAN network element, and perform finer-grained partitioning at the RAN network element.
  • the CN CP sends multiple sets of filtering templates of different granularities to the RAN network element and the terminal.
  • the RAN network element may determine, according to the specific content of the QoS enhanced attribute information, whether to obtain the Qos requirement parameter corresponding to the preset granularity service data according to the preset granularity service data and the preset QoS mapping relationship.
  • the foregoing QoS enhanced attribute information includes a time-varying attribute, and the time-varying attribute identifies that the service data has time-varying, that is, the state of the service data changes in time in the business process, and the QoS requirement changes according to the state of the service data, then Obtaining a Qos requirement parameter corresponding to the preset granularity service data according to the preset granularity service data and the preset QoS mapping relationship.
  • the QoS enhancement attribute does not include a time-varying attribute, or includes a time-varying attribute, but the time-varying attribute identifies that the service data does not have time-varying, then the QoS requirement parameter corresponding to the preset granularity service data is not required to be obtained, for example,
  • the coarse-grained Qos processing is performed according to the prior art, and is not limited herein.
  • the foregoing Qos enhanced attribute information includes a classification attribute, and the classification attribute identifies that the service data needs to be classified by the QoS requirement, and then the foregoing preset granularity service is obtained according to the preset granularity service data and the preset QoS mapping relationship.
  • the Qos requirement parameter corresponding to the data if the QoS attribute does not include the categorization attribute or the categorization attribute, but the categorization attribute identifies the service data, the QoS requirement parameter corresponding to the preset granularity service data does not need to be obtained, for example, according to the Qos requirement parameter.
  • the prior art performs coarse-grained Qos processing, which is not limited herein.
  • the foregoing Qos enhanced attribute information includes a granularity attribute
  • the granularity attribute identification processing granularity is “per bearer” or “flow”
  • the Qos requirement parameter corresponding to the preset granularity service data.
  • the foregoing Qos enhanced attribute information includes a granularity attribute
  • the granularity attribute identification processing granularity is “packet”, indicating that the processing granularity itself is small, it is not necessary to obtain the foregoing according to the preset granularity service data and the preset QoS mapping relationship.
  • the Qos requirement parameter corresponding to the preset granularity service data If the Qos enhancement attribute does not include the above-mentioned granularity attribute, the Qos requirement parameter corresponding to the preset granularity service data may not be obtained, and the coarse-grained Qos processing may be performed according to the prior art, which is not limited herein.
  • the CN CP may also be configured according to the foregoing Qos enhanced attribute information.
  • the Qos requirement parameter that is, the QoS requirement of the preset granularity service data is satisfied according to the QoS enhancement attribute of the preset granularity service data.
  • the business status is time-varying, and different business status requires different QoS processing to ensure business needs.
  • the preset QoS mapping relationship includes: a mapping relationship between the status of the service data and the QoS requirement parameter.
  • the CN CP may negotiate with the application layer server to determine multiple sets of Qos demand parameters, for example, generate multiple sets of Qos demand parameters according to service demand changes, user subscription information, and core network policies. Each set of Qos demand parameters corresponds to different business states.
  • the CN CP can acquire the characteristics of the time-varying attribute, and then configure the mapping relationship between the state of the service data and the Qos requirement parameter.
  • the RAN network element obtains the QoS requirement parameter corresponding to the preset granularity service data, where the RAN network element obtains the current service status of the preset granularity service data; and the RAN network element is configured according to the current preset granularity service data.
  • the RAN network element can monitor the service status of the preset granularity service data in real time, and determine the current service of the preset granularity service data according to the mapping relationship between the status of the service data and the QoS requirement parameter when the preset granularity service state is changed.
  • the Qos requirement parameter corresponding to the status For example, the RAN network element can identify the change of the service status according to the feature information of the service data, but is not limited thereto.
  • the application layer server may also indicate that the service status changes to the underlying layer (the CN CP, the RAN network element, and the lower protocol layer of the application layer in the terminal, such as the network side), and the Qos requirement parameter needs to be changed.
  • the underlying layer the CN CP, the RAN network element, and the lower protocol layer of the application layer in the terminal, such as the network side
  • the RAN network element may further receive the service state change notification message sent by the application layer server, before the RAN network element obtains the QoS requirement parameter corresponding to the preset granularity service data according to the preset granularity service data and the preset QoS mapping relationship.
  • the service state change notification message may carry the current service state, and after receiving the service state change notification message, the RAN network element determines the current service state of the preset granularity service data according to the service state change notification message, and according to the state of the service data.
  • the QoS requirement parameter corresponding to the current service state of the preset granularity service data is obtained by the mapping relationship with the QoS requirement parameter; or the service state change notification message may be directly carried With the Qos requirement parameter indicated by the application layer, the RAN network element can directly determine the Qos requirement parameter after the change of the preset granularity service data according to the service state change notification message.
  • the features embodying the time varying attribute may include: a repeated data packet, a location of the data packet in a slice, time period information of the video service, and the like.
  • the duplicate data packet can be detected by the sequence number of the protocol, and if it is determined to be a duplicate data packet, the Qos information such as the transmission reliability and/or priority of the duplicate data packet is provided. For example, for a Transmission Control Protocol (TCP) retransmission packet, a higher priority can be implemented in the RLC layer processing, thereby implementing cross-layer optimization.
  • TCP Transmission Control Protocol
  • the feature of identifying the location of the packet in the slice is provided.
  • the foregoing may be performed according to the foregoing.
  • the mapping relationship between the status of the service data and the Qos demand parameter determines the corresponding Qos demand parameter.
  • the data packet in the front part of the slice can be relatively increased in priority, so as to improve the smoothness of the video playback and improve the user. Experience.
  • the QoS requirement parameter corresponding to different classification parts of the preset granularity service data is obtained by using a preset mechanism, so as to further perform QoS processing.
  • the preset QoS mapping relationship may include: mapping relationship between the classification information identifier and the QoS requirement parameter.
  • the RAN network element obtains the QoS requirement parameter corresponding to the preset granularity service data, where the RAN network element obtains the classification information identifier of the preset granularity service data, and the RAN network element identifies the classification information according to the preset granularity service data, and The mapping relationship between the classification information identifier and the QoS requirement parameter is obtained, and the Qos requirement parameter corresponding to each classification part in the preset granularity service data is obtained.
  • the CN CP may also send multiple sets of Qos requirement parameters to the RAN network element and the terminal during the service establishment or modification process, and the multiple sets of different granularity filtering templates and multiple The set of Qos demand parameters correspond one by one.
  • the preset QoS mapping relationship may include: a mapping relationship between the filtering template and the QoS requirement parameter, where the RAN network element obtains the Qos requirement parameter corresponding to the preset granularity service data, which may be:
  • the RAN network element divides the preset granularity service data into service data corresponding to the granularity of the at least one filtering template according to the selected filtering template, and according to the filtering template and the Qos requirement parameter.
  • the mapping relationship is obtained by acquiring the Qos requirement parameter corresponding to the service data corresponding to the granularity of the at least one filtering template.
  • the Qos enhanced attribute information sent by the CN CP to the RAN network element includes a time-varying attribute, and the time-varying attribute indicates the status of the service data in the service process.
  • the CN CP may resend the QoS enhanced attribute information to the RAN network element, where the QoS enhanced attribute information still includes a time-varying attribute, but the current time-varying attribute indicates that the status of the service data in the service process does not change with time, and the QoS requirement Does not change with the state of business data.
  • Instant variable properties change from time to time to timeless. It is also possible that the CN CP sends the QoS enhanced attribute information to the RAN network element after a period of time, and the QoS enhanced attribute information does not include the time varying attribute.
  • classification attributes and granularity attributes can be dynamically changed. Then the subsequent Qos demand acquisition and Qos processing will change dynamically.
  • FIG. 5 is a schematic diagram of a processing scenario of a data transmission method provided by the present invention.
  • a RAN network element can uniformly process functions of different multiple protocol layers. Specifically, multiple protocol layers may be from top to bottom.
  • the method includes a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a MAC layer, and a physical (PHY) layer.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access
  • PHY physical
  • the RAN network element needs to perform differentiated processing according to different QoS requirements of different preset granularity service data.
  • the RAN network element transmits the preset granularity service data according to the classification of the preset granularity service data, which may be:
  • the RAN network element uses the Qos requirement parameter corresponding to the classification of the preset granularity service data as the scheduling input of the MAC layer, and performs Qos processing on the preset granularity service data by using the MAC layer scheduling.
  • different service data may be processed at different priorities in the MAC layer, that is, different priority scheduling is performed, or scheduling is performed in consideration of different transmission rates to meet different Qos requirements of service data.
  • the above-mentioned flow AMBR, RB-AMBR, terminal AMBR, delay characteristics, packet loss characteristics, handover characteristics, time-varying characteristics, ARP, etc. may be considered for scheduling.
  • the QoS processing may be performed in the following two manners.
  • the Qos requirement parameter corresponding to a preset granularity service data only relates to the priority and the transmission rate, and the scheduling of the MAC layer can be completely satisfied.
  • the QoS requirement parameter corresponding to the preset granularity service data can be used as the MAC layer.
  • the way to schedule input is to perform Qos processing.
  • the following two schemes may be adopted to satisfy other QoS requirements. Partial Qos processing is completed using only the scheduling of the MAC. Of course, in this case, the following two schemes can also be used for Qos processing.
  • the QoS processing of the subsequent terminal can also be performed by referring to the combination manner, which is not limited herein.
  • the RAN network element generates a plurality of sub-radio bearers (radio bearers, RB for short), respectively, before performing QoS processing on the preset granularity service data according to the QoS requirement parameter corresponding to the preset granularity service data.
  • RB corresponds to different Qos demand parameters.
  • the RAN network element may dynamically generate multiple sub-RBs.
  • the RAN may generate multiple sub-RBs according to the preset QoS mapping relationship sent by the CN CP.
  • the RAN may generate multiple sub-RBs corresponding to different feature information according to the mapping relationship between the preset feature information and the QoS requirement, or generate multiple sub-RBs corresponding to different QoS identifiers according to the mapping relationship between the preset QoS identifier and the QoS requirement parameter.
  • Etc There is no limit here.
  • the CN CP sends multiple sets of Qos requirement parameters to the RAN network element, and the RAN network element directly generates multiple sub-RBs according to the multiple sets of Qos requirement parameters, so that each sub-RB corresponds to a set of Qos requirements. parameter.
  • the RAN network element After the RAN network element generates the plurality of sub-RBs, the RAN network element transmits the preset granularity service data according to the classification of the preset granularity service data, and may be: the QoS requirement parameter corresponding to the RAN network element according to the classification of the preset granularity service data, and the sub-RB The mapping relationship with the QoS requirement parameter is selected, and the corresponding sub-RB is selected to transmit the foregoing preset granularity service data.
  • mapping relationship between the foregoing sub-RBs and the Qos requirement parameters different identifiers may be used to represent different Qos requirement parameters, for example, QCI is used to identify different Qos requirement parameters. Number, there is no limit here.
  • different sub-RBs may be configured in different cell groups.
  • some sub-RBs may be configured in a primary cell group (MCG).
  • MCG primary cell group
  • the other sub-RBs are configured in a second cell group (Secondary Cell Group, SCG for short).
  • the sub-RBs with higher Qos requirement parameters may be configured in a cell group with low cell load and good channel quality.
  • the Qos requirement of the first Qos requirement parameter is higher than the second Qos requirement parameter, the cell load of the MCG is lower than the SCG, and/or the channel quality is higher than the SCG, then the sub-RB corresponding to the first Qos requirement parameter is configured in the MCG. .
  • the foregoing sub-RBs may switch between different cells according to corresponding Qos demand parameters.
  • the RAN network element may offload the service data transmitted on the sub-RB, that is, the service data transmitted on the sub-RB is offloaded to multiple cells for transmission. To increase data transfer rate and bandwidth.
  • FIG. 6 is a schematic diagram of another processing scenario of the data transmission method provided by the present invention.
  • the RAN network element generates multiple sub-RBs, which may be performed at the RLC layer below the PDCP layer, that is, A plurality of sub-RBs are generated in the RLC layer, and each sub-RB corresponds to a different Qos attribute.
  • each sub-RB corresponds to one RLC entity
  • FIG. 6 takes two sub-RBs as an example, and is respectively recorded as an RLC entity 1 and an RLC entity 2.
  • each sub-RB may correspond to two RLC entities, where the two RLC entities respectively correspond to uplink services and downlink services of the same sub-RB; or two RLC entities respectively correspond to different flows in the same sub-RB, each of which Flow corresponds to a more elaborate QoS attribute.
  • the RAN network element divides the data into multiple streams, with one stream as the initial transmission service data and the other stream as the weight. For example, the service data is transmitted.
  • the Qos requirements of the two streams are different. Specifically, due to the window mechanism used in TCP, TCP expects the underlying layer to deliver data packets to the receiving TCP entity in order, otherwise it may trigger fast retransmission and congestion window. Halve, reducing link throughput. However, for TCP retransmission packets, the sooner the delivery is required, the better, that is, the received service data packet will be delivered to the receiving TCP entity. It is not required to submit in order.
  • the RAN network element processes the multiple flows through the same PDCP entity and hands them to different RLC entities for processing, that is, one RLC entity processes the initial transmission service data, and another RLC entity processes the retransmission service data.
  • the two RLC entities may also process the retransmission service data, that is, one of the RLC entities processes both the initial transmission service data and the retransmission service data, and is not limited herein.
  • the PDCP entity only allocates a PDCP sequence (SN) to a packet of the initial service data, and does not allocate a PDCP sequence to the packet of the retransmission service data.
  • the RLC entity that processes the initial service data is transmitted in the order of the PDCP sequence.
  • the retransmission service data is preferentially processed, that is, the scheduler first arranges retransmission of the service data, and if there is remaining transmission space, then arranges the initial transmission service data transmission.
  • the terminal switches, that is, switches to another cell
  • the cached data is returned to the PDCP entity, and the PDCP entity is The transmission is performed again in the new cell.
  • the PDCP sequence is uniformly allocated to the initial transmission service data and the retransmission service data.
  • the packets for retransmitting the service data are directly transmitted and are not delivered in order.
  • some sequence numbers are assigned to the packets that retransmit the service data.
  • the PDCP entity acts as the receiver, it needs to remember which data packets are self-processed by the RLC entity that retransmits the service data, and which packets are from the processing of the initial service data. RLC entity.
  • the RLC entity 1 processes the initial After the service data is transmitted, the RLC entity 2 processes the retransmission service data.
  • the PDCP entity and the upper layer transmit the 5 packets of 1, 2, 3, 4, and 5, when the PDCP entity receives the 7th packet, it needs to determine that It is not passing the No. 7 packet upwards. If the No. 6 packet is the initial transmission service packet, then it needs to wait for the No. 6 packet. If the No. 6 packet is a retransmission service data packet, the No. 7 packet is immediately transmitted upward.
  • the No. 6 packet is a packet for initial transmission of service data or a packet for retransmitting service data, and then the PDCP entity caches the No. 7 packet, and then passes the No. 7 packet after the No. 6 packet.
  • FIG. 7 is a schematic diagram of another processing scenario of the data transmission method provided by the present invention.
  • some preset granularity service data may share one RLC entity.
  • the RLC entity needs to add a PDCP label to the data packet header to identify which PDCP entity the data packet comes from, so that the RLC entity of the receiving side can receive the service.
  • the data packet can be sent to the corresponding receiver PDCP entity according to the PDCP label of the data packet.
  • the RAN network element divides the data into multiple streams, with one stream as the initial transmission service data and the other stream as the weight.
  • the traffic data is used as an example.
  • Each of the initial traffic data flows uses an independent PDCP entity and an RLC entity, and two or more retransmission service data flows share one RLC entity.
  • the RLC is shared by two retransmission service data flows.
  • Entity 3 is an example. After receiving the retransmission service data packet sent by each PDCP entity, the RLC entity 3 adds a PDCP label to the retransmission service data packet header to identify which PDCP entity the data packet comes from.
  • FIG. 8 is a schematic diagram of another processing scenario of the data transmission method provided by the present invention. As shown in FIG. 8 , in the same cell, the RAN network element generates multiple sub-RBs, which may also be directly performed at the PDCP layer.
  • the QoS requirements of the two service data are different. Specifically, because the window mechanism is used in TCP, TCP expects the bottom layer to deliver the data packet in order, otherwise it may trigger fast retransmission. At the same time, the congestion window is halved, which reduces the link throughput. However, for TCP retransmission packets, the sooner the delivery is required, the better the data packet will be delivered upwards. It can be seen that the priority of the retransmission service data is higher than the priority of the initial transmission service data.
  • the initial transmission service data and the retransmission service data respectively adopt separate PDCP entities and RLC entities.
  • the TB transmission refers to the MAC layer taking data from the RLC layer, and organizing the acquired data into a TB and transmitting it to the physical layer.
  • the MAC entity preferentially transmits the retransmission service data packet using the short TTI subframe.
  • the retransmission service data packet is not fragmented and only cascaded in the RLC entity to avoid retransmission of a certain segment of the service data packet waiting for the RLC entity to be reorganized. It should be noted that since it is not segmented, it is connected.
  • the receiving RLC entity does not need to use a plurality of RLC Protocol Data Units (PDUs) to assemble an RLC Service Data Unit (SDU). Therefore, the RLC sequence does not need to be allocated in this manner. or,
  • the retransmission service data packet is both cascaded and segmented in the sender RLC entity, but the RLC entity does not receive an RLC SDU every time it receives an RLC PDU, and if it is formed into an RLC SDU, it is sent to the RLC SDU.
  • PDCP entity If the RLC entity finds that a segment of the RLC PDU cannot be assembled into an RLC SDU, the RLC SDU that can be spelled out is first sent to the PDCP entity, and the RLC PDU continues to wait in the RLC queue until the next RLC PDU arrives. Try again to pack the RLC SDU. This can shorten the waiting time of the data segmentation RLC SDU in the receiver buffer.
  • this process in order to allow the receiving RLC entity to recognize the order of the RLC PDUs to assemble an RLC SDU using multiple RLC PDUs, this can shorten the waiting time of the data segment in the cache.
  • This method requires an RLC sequence number to be assigned to each RLC PDU.
  • the RLC entity If it is recognized that the data packets in the buffer belong to the same TCP acknowledgement character (Acknowledgement, ACK for short) of the same retransmission service data stream, the RLC entity only transmits the last ACK.
  • TCP transmits the data packet number. The initial packet number is monotonically increasing, and the retransmission packet number is unchanged. Therefore, the packet number of the retransmitted packet is definitely ahead of the packet number of the packet currently being transmitted.
  • each sub-RB may correspond to one PDCP entity and one RLC entity (or two), and the MAC layer performs priority scheduling on data in the logical channel corresponding to the sub-RB. And multiplexing/demultiplexing processing.
  • each sub-RB may be configured with different protocol layer parameters, logical channel parameters, and the like.
  • the PDCP layer parameter may include at least one of the following or any combination thereof: a discard timer, a header compression, a reordering timer, a serial number (SN) length, and the like.
  • the RLC parameters may include at least one of the following or any combination thereof: an uplink and downlink RLC mode, a polling retransmission timer, a t-Status Prohibit timer, a Poll Investigation (PDU), and a Poll byte. (Byte), maximum number of retransmissions, reordering timer, SN length, etc.
  • the logical channel parameters may include at least one of the following or any combination thereof: priority Priority, prioritised BitRate, bucket size Duration, logical channel group, etc.
  • the RAN network element may release the sub-RB: optionally, after the service data of the RAN network element is released on the first sub-RB, the first sub-RB is released.
  • a sub-RB may refer to any sub-RB; or, after receiving the service data release notification sent by the CN CP, the RAN network element releases the service data and releases the sub-RB.
  • the CN CP may specifically instruct the RAN to release the first sub-RB.
  • the service data, and the release of the first sub-RB, the first sub-RB may refer to any sub-RB; or the RAN network element monitors that the sub-RB corresponding to the first Qos requirement parameter does not receive the service data within the preset time period. And releasing the sub-RB corresponding to the first Qos requirement parameter, where the first Qos requirement parameter may refer to any set of Qos requirement parameters.
  • the first Qos requirement parameter may refer to any set of Qos requirement parameters.
  • the RAN network element transmits the preset granularity service data according to the classification of the preset granularity service data, which may include: the RAN network element selects the protocol layer used according to the QoS requirement parameter corresponding to the classification of the preset granularity service data.
  • the template is processed, wherein the processing template includes corresponding QoS requirement parameters. Further, the RAN network element transmits the preset granularity service data according to the processing template used by each protocol layer.
  • the different protocol layers of the same RB may preset the corresponding processing template.
  • the mapping relationship between the protocol layer and the processing template may be dynamically changed, and is not always fixed.
  • Each processing template corresponds to a different Qos requirement parameter.
  • the processing template may be selected by each protocol layer, or the processing template may be uniformly selected by a preset module in the RAN network element:
  • the RAN network element translates and modifies the Qos requirement parameters corresponding to the preset granularity service data at each protocol layer, and notifies the next protocol layer, and each protocol layer selects itself according to the obtained QoS requirement parameters.
  • the PDCP layer may select a PDCP layer processing template corresponding to the Qos requirement parameter corresponding to the preset granularity service data, and provide information about the Qos requirement parameter to the next layer of the RLC layer, so that the RLC layer selects a processing template suitable for itself.
  • the RAN network element selects a corresponding processing template for each protocol layer according to the Qos requirement parameter corresponding to the preset granularity service data, that is, uniformly selects a processing template of each protocol layer.
  • the processing template entity of each protocol layer is configured with a unique identifier (id), and the protocol layer entity at the receiving end Receive, resume, and post up based on id.
  • the RLC entity receives the service data packet delivered by the lower layer, and selects a processing template of the specific RLC layer according to the processing module id for processing.
  • the MAC layer Based on the processing of the PDCP layer and the RLC layer, the MAC layer performs optimal scheduling of service data, for example, scheduling with different priorities, and is not limited herein.
  • the foregoing embodiment is only exemplified by the LTE L2 protocol stack, and can be applied to other protocol stack configurations, such as no RLC layer, or part of the RLC layer function is migrated to the MAC or PDCP layer, and similar to the RAN network element, the terminal is also based on Different Qos requirements for business data, and more granular processing of Qos for business data.
  • FIG. 9 is a schematic flowchart of Embodiment 4 of a method for data transmission according to the present invention. As shown in FIG. 8, the method includes:
  • S901 The terminal acquires preset preset granularity uplink service data to be transmitted.
  • the terminal may map, according to the slice where the uplink service data is located, which data streams can be transmitted in the slice, and then determine which packets are transmitted according to the Qos requirement.
  • S902 The terminal acquires a Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted.
  • the terminal acquires the Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted according to the preset granularity uplink service data to be transmitted and the preset QoS mapping relationship.
  • the terminal may receive the CN CP or the preset QoS mapping relationship sent by the RAN network element, which is not limited herein.
  • the preset QoS mapping relationship is generally generated by the CN CP. If the RAN network element sends the preset QoS mapping relationship to the terminal, the RAN network element may first receive the preset QoS mapping relationship sent by the CN CP, and then the RAN network element. Forwarding the preset QoS mapping relationship to the terminal.
  • the core network element may send the preset QoS mapping relationship to the terminal by using a Non-Access Stratum (NAS) message. If the RAN network element forwards the preset QoS mapping relationship to the terminal, the RAN network element may send the preset QoS mapping relationship to the terminal by using an access stratum (AS) message.
  • NAS Non-Access Stratum
  • AS access stratum
  • the QoS requirement parameter can refer to the foregoing embodiment, and details are not described herein again.
  • the terminal transmits the preset granularity uplink service data to be transmitted according to the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted.
  • the preset granularity may be: flow, and/or RB. Specifically can be terminated by CN CP The terminal indicates the preset granularity, which can also be pre-configured, and is not limited herein.
  • the RAN network element forwards the received preset granularity uplink service data to be transmitted to the CN UP.
  • the terminal acquires the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted, and transmits the preset granularity uplink service data according to the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted. Perform different data processing on the preset granularity uplink service data corresponding to the different QoS requirement parameters to meet the Qos requirements of the uplink data of different preset granularities.
  • the terminal after obtaining the Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted, the terminal obtains multiple TCP ACKs in the cache according to the preset granularity uplink service data to be transmitted and the preset QoS mapping relationship. , delete the previous one, and only keep the last ACK.
  • the terminal When uploading data, if the TB space is found to be free, the above-mentioned "deleted TCP ACK" is transmitted. If there is no space in the TB space, it will not be transmitted.
  • the Qos threshold can be configured on the network.
  • BSR Buffer state report
  • the size of the retransmitted packet is indicated in the BSR.
  • the foregoing preset QoS mapping relationship may have multiple forms.
  • the method for the terminal to obtain the service data Qos requirement is also different.
  • the preset QoS mapping relationship is: a mapping relationship between preset feature information and a Qos requirement parameter.
  • the terminal obtains the QoS requirement parameter corresponding to the preset granularity of the uplink service data to be transmitted according to the preset granularity of the uplink service data to be transmitted, and the preset QoS mapping relationship, where the terminal may identify that the terminal needs to transmit the preset granularity uplink. And determining, according to the feature information of the preset granularity uplink service data to be transmitted, and the mapping relationship between the preset feature information and the QoS requirement parameter, determining the uplink service data corresponding to the preset granularity to be transmitted. Qos demand parameters.
  • the terminal After the terminal obtains the mapping relationship between the preset feature information and the QoS requirement parameter, the terminal identifies the feature information of the uplink data of the preset granularity. After identifying the feature information of the preset granularity uplink service data to be transmitted, the terminal determines the Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted according to the mapping relationship between the preset feature information and the QoS requirement parameter.
  • the foregoing feature information may include: one or any combination of the following: a port number of the protocol layer, a feature word, an association feature, and a data popularity.
  • the preset QoS mapping relationship is: a mapping relationship between the preset QoS identifier and the QoS requirement parameter.
  • the terminal obtains the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted according to the preset granularity of the uplink service data to be transmitted, and the preset QoS mapping relationship, where the terminal obtains the preset granularity to be transmitted.
  • the Qos identifier in the service data and the terminal obtains the Qos requirement corresponding to the preset granularity uplink service data to be transmitted according to the QoS identifier of the preset granularity of the uplink service data to be transmitted and the mapping relationship between the preset QoS identifier and the QoS requirement parameter. parameter.
  • the terminal may receive the identifier configuration information of the service data sent by the application layer server, and determine the Qos identifier of the preset granularity uplink service data to be transmitted according to the identifier configuration information of the service data.
  • the Qos identifier can be carried in the protocol layer header of the service data packet, and is not limited herein.
  • the terminal determines the QoS requirement of the preset granularity uplink service data to be transmitted according to the QoS identifier of the preset granularity of the uplink service data to be transmitted and the mapping relationship between the preset QoS identifier and the QoS requirement parameter.
  • the terminal may further receive the foregoing QoS enhanced attribute information sent by the RAN network element or the CN CP.
  • the foregoing Qos enhanced attribute information includes any one of the following or any combination thereof: a time varying attribute, a classification attribute, and a granularity attribute.
  • a time varying attribute e.g., a time varying attribute
  • a classification attribute e.g., a classification attribute
  • a granularity attribute e.g., a granularity attribute
  • the terminal may determine, according to the specific content of the QoS enhanced attribute information, whether to perform the foregoing preset granularity uplink service data to be transmitted according to the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted. Qos processing.
  • the foregoing QoS enhanced attribute information includes a time-varying attribute, and the time-varying attribute identifies that the service data has time-varying, that is, the state of the service data in the business process changes with time, and the Qos requirement
  • the terminal obtains the Qos demand parameter corresponding to the preset granularity uplink service data to be transmitted, according to the status of the service data, and the terminal, according to the preset granularity of the uplink service data and the preset QoS mapping relationship.
  • the foregoing Qos enhanced attribute information includes a classification attribute, and the classification attribute identifies that the service data needs to be classified by the QoS requirement, and the terminal acquires the foregoing according to the preset granularity uplink service data to be transmitted and the preset QoS mapping relationship.
  • the terminal when the foregoing Qos enhanced attribute information includes a granularity attribute, and the granularity attribute identification processing granularity is “per bearer” or “flow”, the terminal performs uplink service data according to the preset granularity to be transmitted, and preset QoS mapping relationship. And obtaining the Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted.
  • the CN CP may also configure different Qos requirement parameters according to the foregoing Qos enhanced attribute information.
  • the preset QoS mapping relationship includes: a mapping relationship between the status of the service data and the QoS requirement parameter.
  • the terminal obtains the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted according to the foregoing preset granularity uplink service data to be transmitted, and the preset QoS mapping relationship, where the terminal obtains the preset granularity uplink service data to be transmitted.
  • the current service status of the terminal is determined by the terminal according to the mapping relationship between the status of the service data and the QoS requirement parameter, and the QoS requirement parameter corresponding to the current service status of the preset granularity uplink service data to be transmitted.
  • the application layer server can indicate to the terminal that the service status has changed.
  • the terminal may obtain different QoS requirement parameters corresponding to different classification parts of the preset granularity uplink service data to be transmitted according to the preset mechanism, so as to further perform QoS processing.
  • the preset QoS mapping relationship may include: mapping relationship between the classification information identifier and the QoS requirement parameter.
  • the terminal obtains the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted according to the foregoing preset granularity uplink service data to be transmitted, and the preset QoS mapping relationship, where the terminal obtains the preset granularity uplink service data to be transmitted.
  • the classification information identifier is obtained according to the mapping relationship between the classification information identifier and the QoS requirement parameter, and each of the preset granularity uplink service data to be transmitted is obtained.
  • the Qos requirement parameters corresponding to the classification part.
  • the preset QoS mapping relationship may include: a mapping relationship between the filtering template and the QoS requirement parameter.
  • the terminal obtains the Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted according to the foregoing preset granularity uplink service data to be transmitted, and the preset QoS mapping relationship, where the terminal may: preset the preset according to the selected filtering template.
  • the granularity service data is divided into service data corresponding to the granularity of the at least one filtering template, and the QoS requirement parameter corresponding to the service data corresponding to the granularity of the at least one filtering template is obtained according to the mapping relationship between the filtering template and the QoS requirement parameter.
  • the terminal performs differentiated QoS processing on different uplink service data, and may have multiple methods.
  • the following examples may include the following types. These solutions may be used according to specific processing requirements, or may be used independently. .
  • the terminal transmits the uplink service data of the preset granularity to be transmitted according to the QoS requirement parameter corresponding to the uplink service data of the preset granularity to be transmitted, where the terminal may be: the Qos requirement parameter corresponding to the uplink service data of the preset granularity to be transmitted by the terminal. And adjusting the scheduling policy of the logical channel corresponding to the preset granularity uplink service data to be transmitted, and transmitting the preset granularity uplink service data to be transmitted by using the adjusted logical channel. Specifically, it may be transmitted to the RAN network element.
  • the terminal may be determined that one of the logical channels performs scheduling policy adjustment, such as increasing priority, increasing transmission rate, etc., and is not limited herein.
  • the adjustment may be implemented according to the Qos requirement parameter corresponding to the uplink service data of the preset granularity to be transmitted.
  • the terminal needs to send a modification indication message to the RAN network element, for example, by modifying the indication message to indicate that the logical channel needs a higher priority LCG BSR, or indicating that the logical channel needs a higher transmission rate, etc.
  • a modification indication message for example, by modifying the indication message to indicate that the logical channel needs a higher priority LCG BSR, or indicating that the logical channel needs a higher transmission rate, etc.
  • the QoS requirement indication corresponding to the uplink service data of the preset granularity to be transmitted may be used.
  • the RAN network element After receiving the modification indication message, the RAN network element knows that the QoS requirement of the LCG has changed, and may perform the configuration of the logical channel, for example, adding or deleting a logical channel, or modifying a logical channel configuration parameter, etc., which is not specifically limited herein.
  • the terminal transmits the uplink service data of the preset granularity to be transmitted according to the QoS requirement parameter corresponding to the uplink service data of the preset granularity to be transmitted, where the terminal may be: the Qos requirement parameter corresponding to the uplink service data of the preset granularity to be transmitted by the terminal. And mapping the preset QoS request uplink data to the corresponding sub-RB for transmission. That is, the uplink service data is specifically mapped to the corresponding sub-RB and transmitted to the RAN network element.
  • the sub-RBs are in one-to-one correspondence with the above logical channels.
  • the terminal can receive the mapping relationship between the Qos requirement parameter sent by the RAN network element and the sub-RB.
  • the RAN network element may configure a mapping relationship between different QoS requirement parameters and the sub-RBs for the terminal, and send the mapping relationship to the terminal.
  • the terminal After the terminal obtains the uplink service data of the preset granularity to be transmitted according to the preset granularity, the terminal maps the uplink service data to be transmitted to the corresponding sub-RB according to the QoS requirement parameter corresponding to the uplink service data of the preset granularity to be transmitted. Transfer.
  • the terminal may also map multiple preset preset granularity uplink service data with the same or similar QoS requirement parameters to the same sub-RB for transmission.
  • the similar Qos demand parameter may be a Qos demand parameter whose difference between the Qos demand parameter values is within a preset range.
  • the mapping relationship between the preset Qos requirement parameter and the sub-RB may be: a mapping relationship between the preset type of the Qos requirement parameter and the sub-RB, that is, the RAN network element may classify the Qos requirement parameter, and configure the preset. And determining, by the terminal, the type of the Qos demand parameter of the preset granularity uplink service data to be transmitted according to the QoS requirement parameter of the preset granularity uplink service data to be transmitted, and according to the preset Mapping the QoS requirements of the QoS to the sub-RBs, and mapping the uplink service data to be transmitted to the corresponding sub-RBs for transmission.
  • a QoS Classification Identifier may be used to identify a preset type of QoS requirement parameter, that is, a preset granularity uplink service data corresponding to a certain type or a certain type of QCI is mapped to the same sub-RB. .
  • the terminal may send a service data classification message to the RAN network element, where the service data classification message includes one or any combination of the following: a Qos requirement parameter of the preset granularity uplink service data to be transmitted, and the foregoing to be transmitted.
  • the service data classification message includes one or any combination of the following: a Qos requirement parameter of the preset granularity uplink service data to be transmitted, and the foregoing to be transmitted.
  • the RAN network element After receiving the service data classification message, the RAN network element establishes a new sub-RB, and configures a mapping relationship between the new sub-RB and the Qos requirement parameter, and then sends the mapping relationship between the new sub-RB and the Qos requirement parameter to the terminal. Therefore, the terminal maps the preset granularity uplink service data to be transmitted to the corresponding sub RB.
  • the “information information of the setup sub-RB” may be not carried in the foregoing service data classification message, and a sub-RB establishment request message is specifically sent to the RAN network element. Then, after receiving the foregoing service data classification message and the sub-RB establishment request message, the RAN network element establishes a new sub-RB, and configures a mapping relationship between the new sub-RB and the Qos requirement parameter, and then the new sub-RB and Qos requirements. The mapping relationship of the parameters is sent to the terminal.
  • the terminal may request the RAN network element to release the sub-RB corresponding to the first Qos requirement parameter, when the sub-RB corresponding to the first QoS requirement parameter has no data transmission in the preset time period, where
  • the first Qos demand parameter can refer to any set of Qos demand parameters.
  • the terminal requests the RAN network element to release the first sub-RB, and the first sub-RB may refer to any sub-RB.
  • the terminal may notify the RAN network element to release the sub-RB through control plane signaling, for example, by using an RRC message or by using a medium access control control element (MAC CE) to notify the RAN network element to release.
  • control plane signaling for example, by using an RRC message or by using a medium access control control element (MAC CE) to notify the RAN network element to release.
  • MAC CE medium access control control element
  • the terminal may also notify the AN network element to release the sub-RB through the user plane.
  • the end marker may be carried in the user plane data packet to indicate that the RAN network element releases the sub-RB and the service data on the sub-RB.
  • the configuration of the sub-RBs has two modes, one is static configuration, that is, the RAN side performs configuration, and the RAN learns the Qos requirement parameter of each preset granularity service data through the CN CP, and refers to the sub-reference parameter.
  • the QoS requirement parameter of all preset granularity service data included in the RB is parameterized for the sub-RB.
  • the QoS requirement parameter of the categorized sub-flow can be obtained by combining the packet header mapping information reported by the terminal with the QoS parameter of the categorized data stream notified by the CN CP.
  • the dynamic configuration is that the terminal dynamically generates the QoS requirement parameter of the preset granularity service data according to the mapping relationship between the preset granularity service data and the sub-RB.
  • Dynamically configured rules can be generated and notified to the terminal by the network side.
  • the update may be performed on the basis of the initial configuration of the sub-RB parameters on the network side.
  • the parameter configuration of the PBR of the sub-RB may be the sum of the GBRs of all the sub-flows of the classified data.
  • the network side can be configured with uniform PBR generation rules (for example, The PBR can be generated according to the QCI calculation, and the terminal calculates the PBR of each preset granularity service data, and the parameter configuration of the PBR of the sub-RB can be the sum of the PBRs of all the preset granularity service data.
  • uniform PBR generation rules for example, The PBR can be generated according to the QCI calculation, and the terminal calculates the PBR of each preset granularity service data, and the parameter configuration of the PBR of the sub-RB can be the sum of the PBRs of all the preset granularity service data.
  • the terminal performs data processing procedures of one or more of encryption, segmentation, reassembly, scheduling, and multiplexing based on the parameter configuration of the uplink sub-RB.
  • the terminal transmits the uplink service data of the preset granularity to be transmitted according to the QoS requirement parameter corresponding to the uplink service data of the preset granularity to be transmitted, where the terminal transmits the preset to be transmitted by using a preset processing template corresponding to each protocol layer.
  • Set granular upstream service data may be sent to the RAN network element.
  • the processing template corresponding to different protocol layers is configured according to the subscription information of the terminal or the different Qos requirement parameter information, and the protocol layer may correspond to at least one processing template.
  • the protocol layer may correspond to at least one processing template. For example, configuring at least one processing template corresponding to the PDCP layer (each processing template corresponds to one PDCP entity), and/or configuring at least one processing template corresponding to the RLC layer (each processing template corresponds to one RLC entity), and is not limited herein. .
  • the terminal receives the correspondence between the preset processing template sent by the RAN network element and each protocol layer, where each processing template can be distinguished by different template identifiers.
  • the content of each processing template may be pre-configured in the terminal, or may be dynamically notified by the RAN network element, which is not limited herein.
  • the processing template establishment request may be sent to the RAN network element to request the RAN network element to reconfigure the processing template corresponding to each protocol layer, and the RAN network element may establish a new processing template according to the processing template establishment request, for example, establish a new PDCP entity, that is, PDCP.
  • the terminal may also send a processing template deletion request to the RAN network element, where the processing template deletion request may carry the identifier of the processing template to be deleted, to request the RAN network element to delete one or more to-be-delete processing templates that are currently configured.
  • the terminal may further include: a reason parameter for requesting deletion, and the like in the processing template deletion request.
  • the terminal may request the RAN network element to delete the unused processing template in the preset time period, which is not limited herein.
  • the data packet header of the service data carries the identifier of the PDCP entity and the identifier of the RLC entity.
  • the terminal may release some service data sub-flows. For example, the terminal may detect that the RAN releases the classified data sub-flow when the time when a certain classified data sub-flow has no data packet exceeds a preset time period. .
  • the RAN may be notified by means of control plane signaling, and the RAN message is notified by the RRC message or the MAC CE to release the classified data substream.
  • the RAN may also be notified by the user plane, and the end face indicator is carried in the user plane data packet to notify the RAN of the termination of the offload data substream.
  • FIG. 10 is a schematic structural diagram of Embodiment 1 of a device for data transmission according to the present invention.
  • the device may be integrated into a RAN network element or a RAN controller.
  • the device includes: an obtaining module 110, a determining module 111, and Transmission module 112, wherein:
  • the obtaining module 110 is configured to obtain preset granularity service data.
  • the determining module 111 is configured to obtain the Qos requirement parameter corresponding to the preset granularity service data, perform the Qos requirement classification on the preset granularity service data, and determine the Qos requirement parameter according to the preset granularity service data.
  • the Qos requirement parameter corresponding to the classification of the preset granularity service data is obtained from the preset granularity service data.
  • the transmission module 112 is configured to transmit the preset granularity service data according to the classification of the preset granularity service data.
  • the RAN network element obtains the preset granularity service data, and further the RAN network element obtains the QoS requirement parameter of the preset granularity service data, and performs the Qos requirement classification on the preset granularity service data, and determines the preset granularity service data.
  • the QoS requirement parameter corresponding to the classification and the RAN network element transmits the preset granularity service data according to the classification of the preset granularity service data, so that the RAN network element can obtain different QoS requirement parameters corresponding to different preset granularity service data.
  • the preset granularity service data is respectively transmitted according to the classification of the preset granularity service data, so as to meet the Qos requirement of the service data of different preset granularities.
  • the determining module 111 is configured to obtain the Qos requirement parameter corresponding to the preset granularity service data according to the attribute information of the preset granularity service data and the preset QoS mapping relationship. number.
  • the attribute information of the preset granularity service data includes any one of the following or any combination thereof: preset feature information, preset identifier, and preset channel identifier.
  • the preset QoS mapping relationship is: a mapping relationship between the preset feature information and the QoS requirement; the determining module 111 is specifically configured to identify the characteristic information in the preset granularity service data; The characteristic information in the granularity service data, and the mapping relationship between the preset feature information and the QoS requirement parameter are obtained, and the Qos requirement parameter corresponding to the preset granularity service data is obtained.
  • the feature information includes one or any combination of the following: a port number of the protocol layer, a feature word, an association feature, and a data popularity; wherein the association feature refers to a plurality of feature words that are jointly identified.
  • the preset QoS mapping relationship is: a mapping relationship between the preset QoS identifier and the QoS requirement parameter
  • the determining module 111 is configured to obtain the QoS identifier in the preset granularity service data according to the preset rule.
  • the QoS requirement parameter corresponding to the preset granularity service data is obtained according to the QoS identifier of the preset granularity service data and the mapping relationship between the preset QoS identifier and the QoS requirement parameter.
  • the determining module 111 is configured to obtain the Qos identifier in the preset granularity service data according to the preset rule, and specifically: obtain the Qos identifier in the data packet header of the preset granularity service data according to the preset rule.
  • the preset QoS mapping relationship is: a mapping relationship between the preset channel identifier and the QoS requirement parameter; the determining module 111 is specifically configured to determine a channel that receives the preset granularity service data; The channel of the preset granularity service data, and the mapping relationship between the preset channel identifier and the QoS requirement parameter, and the Qos requirement parameter corresponding to the preset granularity service data is obtained.
  • the QoS requirement parameter includes at least one of the following or any combination thereof: a flow aggregation maximum bit rate AMBR, a radio bearer AMBR, a terminal AMBR, a priority, a time delay, a packet loss rate, a handover characteristic, and a time-varying characteristic. , assign retention priority ARP.
  • FIG. 11 is a schematic structural diagram of Embodiment 2 of a data transmission apparatus according to the present invention. As shown in FIG. 11, the apparatus further includes: a receiving module 113, configured to receive and obtain Qos enhanced attribute information.
  • the determining module 111 is configured to obtain the Qos requirement parameter corresponding to the preset granularity service data according to the QoS enhanced attribute information of the preset granularity service data and the preset QoS mapping relationship. number.
  • the QoS enhanced attribute information includes any one of the following or any combination thereof: a time varying attribute, a classification attribute, and a granularity attribute;
  • the time-varying attribute is used to identify whether the state of the service data in the service process changes with time, and whether the QoS requirement parameter changes with the state of the service data;
  • the classification attribute is used to identify whether the service data is classified according to the Qos requirement parameter;
  • the granularity attribute is used to identify the processing granularity of Qos.
  • the preset QoS mapping relationship includes: a mapping relationship between a state of the service data and a Qos requirement parameter;
  • the determining module 111 is configured to obtain a current service status of the preset granularity service data, and determine, according to a current service status of the preset granularity service data, and a mapping relationship between the status of the service data and a Qos requirement parameter.
  • the Qos requirement parameter corresponding to the current service state of the preset granularity service data.
  • the receiving module 113 is further configured to determine, according to the service state change notification, a current service state of the preset granularity service data.
  • the transmission module 112 is specifically configured to use the QoS requirement parameter corresponding to the classification of the preset granularity service data as a scheduling input of the medium access control MAC layer, and transmit the preset granularity service data by using a MAC layer scheduling.
  • FIG. 12 is a schematic structural diagram of Embodiment 3 of a device for data transmission according to the present invention. As shown in FIG. 12, on the basis of FIG. 10, the device further includes: a generating module 114, configured to generate multiple sub-radio bearers, each sub- The radio bearers correspond to different Qos demand parameters.
  • a generating module 114 configured to generate multiple sub-radio bearers, each sub- The radio bearers correspond to different Qos demand parameters.
  • the transmission module 112 is configured to select the corresponding sub-radio bearer to transmit the preset granularity service data according to the QoS requirement parameter corresponding to the classification of the preset granularity service data and the mapping relationship between the sub-radio bearer and the QoS requirement parameter.
  • the transmission module 112 is configured to select, according to the QoS requirement parameter corresponding to the classification of the preset granularity service data, a processing template used by each protocol layer, where different Qos requirement parameters corresponding to the processing template are selected. Differently: transmitting the preset granularity service data according to a processing template used by each protocol layer.
  • the obtaining module 110 is further configured to acquire the preset QoS mapping relationship.
  • the transmitting module 112 is further configured to send the preset QoS mapping relationship to the terminal.
  • FIG. 13 is a schematic structural diagram of Embodiment 4 of a device for data transmission according to the present invention, where the device can be To be integrated in the terminal, the device includes: an obtaining module 131, a determining module 132, and a transmitting module 133, where:
  • the obtaining module 131 is configured to obtain the preset granularity uplink service data to be transmitted.
  • the determining module 132 is configured to obtain a Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted.
  • the transmitting module 133 is configured to transmit the preset granularity uplink service data to be transmitted according to the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted.
  • the determining module 132 is configured to obtain the Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted according to the preset granularity uplink service data to be transmitted and the preset QoS mapping relationship.
  • the preset QoS mapping relationship is: a mapping relationship between the preset feature information and the QoS requirement parameter; the determining module 132 is specifically configured to identify the feature information of the preset granularity uplink service data to be transmitted; The feature information of the preset granularity uplink service data to be transmitted, and the mapping relationship between the preset feature information and the QoS requirement parameter, obtain the Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted.
  • the feature information includes one or any combination of the following: a port number of the protocol layer, a feature word, an association feature, and a data popularity; wherein the association feature refers to a plurality of feature words that are jointly identified.
  • the preset QoS mapping relationship is: a mapping relationship between a preset QoS identifier and a Qos requirement parameter;
  • the determining module 132 is configured to obtain the Qos identifier in the preset granularity uplink service data to be transmitted, and the Qos identifier in the uplink service data of the preset granularity to be transmitted, and the preset Qos identifier and the Qos requirement parameter.
  • the mapping relationship is obtained, and the Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted is obtained.
  • the QoS requirement includes at least one of the following or any combination thereof: a flow aggregation maximum bit rate AMBR, a radio bearer AMBR, a terminal AMBR, a priority, a time delay, a packet loss rate, a handover characteristic, a time-varying characteristic, Assign retention priority ARP.
  • FIG. 14 is a schematic structural diagram of Embodiment 5 of a device for data transmission according to the present invention.
  • the device may further include: a first receiving module 134, configured to receive a core network control function entity or a RAN network element. Qos enhances attribute information.
  • the determining module 132 is configured to obtain the Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted according to the QoS enhanced attribute information corresponding to the preset granularity uplink service data to be transmitted, and the preset QoS mapping relationship.
  • the QoS enhanced attribute information includes any one of the following or any combination thereof: a time varying attribute, a classification attribute, and a granularity attribute;
  • the time-varying attribute is used to identify whether the state of the service data in the service process changes with time, and whether the QoS requirement parameter changes with the state of the service data;
  • the classification attribute is used to identify whether the service data is classified according to the Qos requirement parameter;
  • the granularity attribute is used to identify the processing granularity of Qos.
  • the transmission module 133 is configured to adjust a scheduling policy of the logical channel corresponding to the preset granularity uplink service data to be transmitted according to the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted, and adopt the adjusted The logical channel transmits the preset granularity uplink service data to be transmitted to the RAN network element.
  • the transmitting module 133 is configured to: according to the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted, and the mapping relationship between the preset QoS requirement parameter and the sub RB, the preset to be transmitted The granular uplink service data is mapped to the corresponding sub-radio bearer RB for transmission.
  • FIG. 15 is a schematic structural diagram of Embodiment 6 of a device for data transmission according to the present invention.
  • the device may further include: a second receiving module 135, configured to receive the pre-sent sent by the RAN network element. Set the mapping relationship between Qos requirements and sub-RBs.
  • the transmitting module 133 is configured to perform QoS processing on the preset granularity uplink service data to be transmitted by using a preset processing template corresponding to each protocol layer, and send the processed preset granularity uplink service data to be sent to the RAN. Network element.
  • FIG. 16 is a schematic structural diagram of Embodiment 7 of a data transmission apparatus according to the present invention.
  • the apparatus may be integrated into a core network element.
  • the apparatus includes: a generating module 161 and a sending module 162, where:
  • the generating module 161 is configured to generate a QoS mapping relationship, where the QoS mapping relationship is used to indicate a mapping relationship between the preset granularity service data and the QoS requirement parameter.
  • the sending module 162 sends the QoS mapping relationship to the radio access network element.
  • the sending module 162 is further configured to send the QoS mapping relationship to the radio access network element.
  • the QoS mapping relationship includes: mapping between service data feature information and Qos requirements. relationship.
  • the service data feature information includes one or any combination of the following: a port number of the protocol layer, a feature word, an association feature, and a data popularity; wherein the association feature refers to a plurality of feature words jointly identified.
  • the QoS mapping relationship includes: the QoS mapping relationship includes: a mapping relationship between a Qos identifier and a Qos requirement parameter in the service data.
  • the QoS mapping relationship includes: mapping a preset channel identifier to a QoS requirement parameter.
  • the sending module 162 is further configured to send at least one set of Qos requirement parameters to the core network user plane function entity.
  • FIG. 17 is a schematic structural diagram of Embodiment 1 of a radio access network element according to the present invention.
  • the RAN network element includes: a memory 171, a processor 172, a receiver 173, and a transmitter 174.
  • the memory 171, the processor 172, the receiver 173, and the transmitter 174 are connected by a bus 175.
  • Memory 171 is used to store instructions, and processor 172 is used to invoke instructions in memory 171 to perform the aforementioned method embodiments. specifically:
  • the processor 172 is configured to obtain the preset granularity service data, obtain the QoS requirement parameter corresponding to the preset granularity service data, and perform the QoS requirement classification on the preset granularity service data, and corresponding to the preset granularity service data.
  • the QoS requirement parameter determines the QoS requirement parameter corresponding to the classification of the preset granularity service data, and transmits the preset granularity service data according to the classification of the preset granularity service data.
  • the processor 172 is configured to obtain a Qos requirement parameter corresponding to the preset granularity service data according to the attribute information of the preset granularity service data and the preset QoS mapping relationship.
  • the attribute information of the preset granularity service data includes any one of the following or any combination thereof: preset feature information, preset identifier, and preset channel identifier.
  • the preset QoS mapping relationship is: mapping relationship between preset feature information and Qos requirements;
  • the processor 172 is specifically configured to identify the characteristic information in the preset granularity service data, and according to the characteristic information in the preset granularity service data, and the preset feature information and the Qos requirement parameter. The mapping relationship is obtained, and the Qos requirement parameter corresponding to the preset granularity service data is obtained.
  • the feature information includes one or any combination of the following: a port number of the protocol layer, a feature word, an association feature, and a data popularity; wherein the association feature refers to a plurality of feature words that are jointly identified.
  • the preset QoS mapping relationship is: a mapping relationship between the preset QoS identifier and the QoS requirement parameter;
  • the processor 172 is configured to acquire a Qos identifier in the preset granularity service data according to a preset rule, and map the Qos identifier in the preset granularity service data and the preset Qos identifier and the Qos requirement parameter. The relationship is obtained by acquiring a Qos requirement parameter corresponding to the preset granularity service data.
  • the processor 172 is configured to obtain the Qos identifier in the preset granularity service data according to the preset rule, where the QoS identifier is obtained in the data packet header of the preset granularity service data according to the preset rule.
  • the preset QoS mapping relationship is: a mapping relationship between the preset channel identifier and the QoS requirement parameter; the processor 172 is specifically configured to determine a channel that receives the preset granularity service data; according to the receiving station The channel of the preset granularity service data, and the mapping relationship between the preset channel identifier and the QoS requirement parameter, and the Qos requirement parameter corresponding to the preset granularity service data is obtained.
  • the QoS requirement includes at least one of the following or any combination thereof: a flow aggregation maximum bit rate AMBR, a radio bearer AMBR, a terminal AMBR, a priority, a time delay, a packet loss rate, a handover characteristic, a time-varying characteristic, Assign retention priority ARP.
  • the receiver 173 is configured to receive and obtain Qos enhanced attribute information.
  • the processor 172 is specifically configured to obtain a Qos requirement parameter corresponding to the preset granularity service data according to the QoS enhanced attribute information of the preset granularity service data and the preset QoS mapping relationship.
  • the QoS enhanced attribute information includes any one of the following or any combination thereof: a time varying attribute, a classification attribute, and a granularity attribute;
  • the time-varying attribute is used to identify whether the state of the service data in the service process changes with time, and whether the QoS requirement parameter changes with the state of the service data;
  • the classification attribute is used to identify whether the service data is classified according to the Qos requirement parameter;
  • the granularity attribute is used to identify the processing granularity of Qos.
  • the preset QoS mapping relationship includes: a mapping relationship between a state of the service data and a Qos requirement parameter; and the processor 172, specifically Determining the current service status of the preset granularity service data; determining the preset granularity service data according to the current service status of the preset granularity service data, and the mapping relationship between the status of the service data and the QoS requirement parameter.
  • the current Qos demand parameter corresponding to the current business status.
  • the receiver 173 is further configured to receive a service status change notification sent by the application layer server, where the processor 172 is further configured to determine, according to the service status change notification, a current service status of the preset granularity service data.
  • the processor 172 is configured to use the QoS requirement parameter corresponding to the classification of the preset granularity service data as a scheduling input of the medium access control MAC layer, and transmit the preset granularity service data by using a MAC layer scheduling.
  • the processor 172 is further configured to generate multiple sub-radio bearers, where each sub-radio bearer corresponds to a different Qos requirement parameter. And selecting a corresponding sub-radio bearer to transmit the preset granularity service data according to the QoS requirement parameter corresponding to the classification of the preset granularity service data and the mapping relationship between the sub-radio bearer and the QoS requirement parameter.
  • the processor 172 is configured to select, according to the QoS requirement parameter corresponding to the classification of the preset granularity service data, a processing template used by each protocol layer, where different Qos requirement parameters corresponding to the processing template are selected. Differently: transmitting the preset granularity service data according to a processing template used by each protocol layer.
  • the processor 172 is further configured to acquire the preset QoS mapping relationship.
  • the transmitter 174 is configured to send the preset QoS mapping relationship to the terminal.
  • FIG. 18 is a schematic structural diagram of Embodiment 1 of a terminal provided by the present invention. As shown in FIG. 18, the terminal includes: a memory 181, a processor 182, a receiver 183, and a transmitter 184.
  • the memory 181, the processor 182, the receiver 183, and the transmitter 184 are connected by a bus 185.
  • Memory 181 is used to store instructions, and processor 182 is used to invoke instructions in memory 181 to perform the aforementioned method embodiments. specifically:
  • the processor 182 is configured to obtain the preset granularity uplink service data to be transmitted, obtain the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted, and the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted, Transmitting the preset granularity uplink service data to be transmitted.
  • the processor 182 is configured to obtain the preset service granularity uplink service data pair to be transmitted according to the preset granularity uplink service data to be transmitted and the preset QoS mapping relationship.
  • the Qos demand parameters should be.
  • the preset QoS mapping relationship is: a mapping relationship between the preset feature information and the QoS requirement parameter; the processor 182 is specifically configured to identify the feature information of the preset granularity uplink service data to be transmitted; The feature information of the preset granularity uplink service data to be transmitted, and the mapping relationship between the preset feature information and the QoS requirement parameter, obtain the Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted.
  • the feature information includes one or any combination of the following: a port number of the protocol layer, a feature word, an association feature, and a data popularity; wherein the association feature refers to a plurality of feature words that are jointly identified.
  • the preset QoS mapping relationship is: a mapping relationship between the preset QoS identifier and the QoS requirement parameter; the processor 182 is configured to obtain the Qos identifier in the preset granularity uplink service data to be transmitted; And the QoS requirement parameter of the preset granularity uplink service data to be transmitted is obtained by the mapping between the Qos identifier in the preset granularity uplink service data and the mapping relationship between the preset QoS identifier and the QoS requirement parameter.
  • the QoS requirement parameter includes at least one of the following or any combination thereof: a stream aggregation maximum bit rate AMBR, a radio bearer AMBR, a terminal AMBR, a priority, a time delay, a packet loss rate, a handover characteristic, a time-varying characteristic, Assign retention priority ARP.
  • the receiver 183 is configured to receive the QoS enhanced attribute information sent by the core network control function entity or the RAN network element, where the processor 182 is configured to: according to the QoS enhanced attribute corresponding to the preset granularity uplink service data to be transmitted.
  • the information and the preset QoS mapping relationship are used to obtain the Qos requirement parameter corresponding to the preset granularity uplink service data to be transmitted.
  • the QoS enhanced attribute information includes any one of the following or any combination thereof: a time varying attribute, a classification attribute, and a granularity attribute;
  • the time-varying attribute is used to identify whether the state of the service data in the service process changes with time, and whether the QoS requirement parameter changes with the state of the service data;
  • the classification attribute is used to identify whether the service data is classified according to the Qos requirement parameter;
  • the granularity attribute is used to identify the processing granularity of Qos.
  • the processor 182 according to the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted, adjusts a scheduling policy of the logical channel corresponding to the preset granularity uplink service data to be transmitted, and adopts the adjusted logical channel. Transmitting the preset granularity uplink service data to be transmitted to the RAN network element.
  • the processor 182 is configured to: according to the QoS requirement parameter corresponding to the preset granularity uplink service data to be transmitted, and the mapping relationship between the preset QoS requirement parameter and the sub RB, the preset to be transmitted The granular uplink service data is mapped to the corresponding sub-radio bearer RB for transmission.
  • the receiver 183 is configured to receive a mapping relationship between the preset QoS requirement sent by the RAN network element and the sub RB.
  • the processor 182 is configured to perform QoS processing on the preset granularity uplink service data to be transmitted by using a preset processing template corresponding to each protocol layer, and process the processed preset granularity uplink service to be transmitted.
  • the data is sent to the RAN network element.
  • FIG. 19 is a schematic structural diagram of Embodiment 1 of a core network element provided by the present invention.
  • the terminal includes: a memory 191, a processor 192, a receiver 193, and a transmitter 194.
  • the memory 191, the processor 192, the receiver 193, and the transmitter 194 are connected by a bus 195.
  • Memory 191 is used to store instructions, and processor 192 is used to invoke instructions in memory 191 to perform the aforementioned method embodiments. specifically:
  • the processor 192 is configured to generate a QoS mapping relationship, where the QoS mapping relationship is used to indicate a mapping relationship between the preset granularity service data and the QoS requirement parameter.
  • the transmitter 194 is configured to send the QoS mapping relationship to the radio access network element.
  • the sender 194 is further configured to send the QoS mapping relationship to the radio access network element.
  • the QoS mapping relationship includes: mapping relationship between service data feature information and Qos requirements.
  • the feature information includes one or any combination of the following: a port number of the protocol layer, a feature word, an association feature, and a data popularity; wherein the association feature refers to a plurality of feature words that are jointly identified.
  • the QoS mapping relationship includes: a mapping relationship between a Qos identifier and a Qos requirement parameter in the service data.
  • the preset QoS mapping relationship is: a mapping relationship between the preset channel identifier and the QoS requirement parameter.
  • the sender 194 is further configured to send at least one set of Qos requirement parameters to the core network user plane function entity.
  • the foregoing device is used to perform the foregoing method embodiments, and the implementation principle and technical effects are similar. For details, refer to the foregoing method embodiments.
  • the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed.
  • the foregoing steps include the steps of the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Abstract

本发明实施例提供一种数据传输的方法及装置,该方法包括:终端获取待传输预设粒度上行业务数据;终端获取所述待传输预设粒度上行业务数据对应的Qos需求参数;终端根据所述待传输预设粒度上行业务数据对应的Qos需求参数,传输所述待传输预设粒度上行业务数据。实现了对不同Qos需求参数对应的待传输预设粒度上行业务数据进行不同的数据处理,以满足不同预设粒度上行业务数据的Qos需求。

Description

数据传输的方法及装置 技术领域
本发明涉及无线通信技术,尤其涉及一种数据传输的方法及装置。
背景技术
服务质量(Quality of Service,简称Qos)是一种网络能够利用各种基础技术,为指定的网络通信提供更好服务的能力,是网络的一种安全机制,用来解决网络延迟和阻塞等问题。
长期演进(Long Term Evolution,简称LTE)系统中,在上行传输过程中,终端使用上行(uplink,简称UL)业务流模板(Traffic Flow Template,简称TFT)将一个用户服务数据流(Service Data Flow,简称SDF)与一个演进的分组系统(Evolved Packet System,简称EPS)承载(bearer)绑定在一起,并通过在UL TFT中包含多个上行包过滤(uplink packet filter),可以将多个SDF复用到相同的EPS bearer上;在下行传输过程中,核心网中的分组数据网网关(Packet Data Network Gateway,简称P-GW)使用下行(downlink,简称DL)TFT将一个SDF与一个EPS bearer绑定在一起,并通过在DL TFT中包含多个下行包过滤(downlink packet filter),可以将多个SDF复用到相同的EPS bearer上。
现有的LET系统中,通过EPS bearer的属性来保证Qos的需求,具体地,由核心网的移动管理实体(Mobility Management Entity,简称MME)向无线网络侧提供演进的无线接入承载(Evolved Radio Access Bearer,简称E-RAB)Qos需求参数,具体地E-RAB Qos需求参数可以包括Qos分类标识(Qos Classification Identifier,简称QCI),其中,不同的QCI标识不同的Qos需求。另外,在无线网络侧会认为复用到相同EPS bearer的多个SDF的Qos需求相同,并采用相同级别的Qos处理。但是,实际上不同业务的Qos需求并不相同,采用现有技术没有办法满足不同业务的不同Qos需求。
发明内容
本发明实施例提供一种数据传输的方法及装置,用于解决现有技术中没有办法满足不同业务的不同Qos需求。
本发明第一方面提供一种数据传输的方法,包括:
无线接入网网元获取预设粒度业务数据;
所述无线接入网网元获取所述预设粒度业务数据对应的Qos需求参数;
所述无线接入网网元将所述预设粒度业务数据进行Qos需求分类,并根据所述预设粒度业务数据对应的Qos需求参数确定所述预设粒度业务数据所属分类对应的Qos需求参数;
所述无线接入网网元根据所述预设粒度业务数据所属分类传输所述预设粒度业务数据。
可选地,所述无线接入网网元获取所述预设粒度业务数据对应的Qos需求参数,包括:
所述无线接入网网元根据所述预设粒度业务数据的属性信息、以及预设服务质量Qos映射关系,获取所述预设粒度业务数据对应的Qos需求参数。
可选地,所述预设粒度业务数据的属性信息包括下述任一项或其任意组合:预设特征信息、预设标识、预设通道标识。
可选地,所述预设Qos映射关系为:预设特征信息与Qos需求参数的映射关系;
所述无线接入网网元根据所述预设粒度业务数据的属性信息、以及预设服务质量Qos映射关系,获取所述预设粒度业务数据对应的Qos需求参数,包括:
所述无线接入网网元识别所述预设粒度业务数据中的特性信息;
所述无线接入网网元根据所述预设粒度业务数据中的特性信息、以及预设特征信息与Qos需求参数的映射关系,获取所述预设粒度业务数据对应的Qos需求参数。
进一步地,所述特征信息包括下述一项或其任意组合:协议层的端口号、特征字、关联特征、数据流行为;其中,所述关联特征指联合识别的多个特征字。
可选地,所述预设服务质量Qos映射关系为:预设Qos标识与Qos需求参数的映射关系;
所述无线接入网网元根据所述预设粒度业务数据的属性信息、以及预设服务质量Qos映射关系,获取所述预设粒度业务数据对应的Qos需求参数,包括:
所述无线接入网网元根据预设规则获取所述预设粒度业务数据中的Qos标识;
所述无线接入网网元根据所述预设粒度业务数据中的Qos标识、以及所述预设Qos标识与Qos需求参数的映射关系,获取所述预设粒度业务数据对应的Qos需求参数。
进一步地,所述无线接入网网元根据预设规则获取所述预设粒度业务数据中的Qos标识,包括:
所述无线接入网网元根据预设规则,在所述预设粒度业务数据的数据包头中获取Qos标识。
可选地,所述预设服务质量Qos映射关系为:预设通道标识与Qos需求参数的映射关系;
所述无线接入网网元根据所述预设粒度业务数据的属性信息、以及预设服务质量Qos映射关系,获取所述预设粒度业务数据对应的Qos需求参数,包括:
所述无线接入网网元确定接收所述预设粒度业务数据的通道;
所述无线接入网网元根据所述接收所述预设粒度业务数据的通道、以及预设通道标识与Qos需求参数的映射关系,获取所述预设粒度业务数据对应的Qos需求参数。
进一步地,所述Qos需求参数包括下述至少一项或其任意组合:流聚合最大比特速率AMBR、无线承载AMBR、终端AMBR、优先级、时间延迟、丢包率、切换特性、时变特性、分配保留优先级ARP。
可选地,所述无线接入网网元获取所述预设粒度业务数据对应的Qos需求参数之前,还包括:
所述无线接入网网元获取Qos增强属性信息;相应地,
所述无线接入网网元获取所述预设粒度业务数据对应的Qos需求参数,包括:
所述无线接入网网元根据所述预设粒度业务数据的Qos增强属性信息、 以及预设Qos映射关系,获取所述预设粒度业务数据对应的Qos需求参数。
可选地,所述Qos增强属性信息包括下述任一项或其任意组合:时变属性、分类属性、粒度属性;
其中,所述时变属性用于标识业务过程中业务数据的状态是否随时间变化、且Qos需求参数是否随业务数据的状态变化;所述分类属性用于标识业务数据是否根据Qos需求参数分类;所述粒度属性用于标识Qos的处理粒度。
可选地,所述Qos增强属性信息包括时变属性时,所述预设Qos映射关系包括:业务数据的状态与Qos需求参数的映射关系;
所述无线接入网网元根据所述预设粒度业务数据的Qos增强属性信息、以及预设Qos映射关系,获取所述预设粒度业务数据对应的Qos需求参数,包括:
所述无线接入网网元获取所述预设粒度业务数据的当前业务状态;
所述无线接入网网元根据所述预设粒度业务数据的当前业务状态、以及所述业务数据的状态与Qos需求参数的映射关系,确定所述预设粒度业务数据的当前业务状态对应的Qos需求参数。
可选地,所述无线接入网网元获取所述预设粒度业务数据的当前业务状态,包括:
所述无线接入网网元接收应用层服务器发送的业务状态变化通知;
所述无线接入网网元根据所述业务状态变化通知,确定所述预设粒度业务数据的当前业务状态。
可选地,所述无线接入网网元根据所述预设粒度业务数据所属分类传输所述预设粒度业务数据,包括:
所述无线接入网网元将所述预设粒度业务数据所属分类对应的Qos需求参数作为介质访问控制MAC层的调度输入,通过MAC层调度传输所述预设粒度业务数据。
可选地,所述无线接入网网元根据所述预设粒度业务数据所属分类传输所述预设粒度业务数据之前,还包括:
所述无线接入网网元生成多个子无线承载,每个子无线承载对应不同的Qos需求参数;
所述无线接入网网元根据所述预设粒度业务数据所属分类传输所述预设 粒度业务数据,包括:
所述无线接入网网元根据所述预设粒度业务数据所属分类对应的Qos需求参数、以及子无线承载与Qos需求参数的映射关系,选择对应的子无线承载传输所述预设粒度业务数据。
可选地,所述无线接入网网元根据所述预设粒度业务数据所属分类传输所述预设粒度业务数据,包括:
所述无线接入网网元根据所述预设粒度业务数据所属分类对应的Qos需求参数,选择各协议层所采用的处理模板,其中,不同的所述处理模板对应的Qos需求参数不同;
所述无线接入网网元根据所述各协议层所采用的处理模板传输所述预设粒度业务数据。
进一步地,所述方法还包括:
所述无线接入网网元获取所述预设Qos映射关系。
进一步地,所述方法还包括:
所述无线接入网网元向终端发送所述预设Qos映射关系。
本发明实施例第二方面提供一种数据传输的方法,包括:
终端获取待传输预设粒度上行业务数据;
所述终端获取所述待传输预设粒度上行业务数据对应的Qos需求参数;
所述终端根据所述待传输预设粒度上行业务数据对应的Qos需求参数,传输所述待传输预设粒度上行业务数据。
可选地,所述终端获取所述待传输预设粒度上行业务数据对应的Qos需求参数,包括:
所述终端根据所述待传输预设粒度上行业务数据、以及预设服务质量Qos映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
进一步地,所述预设服务质量Qos映射关系为:预设特征信息与Qos需求参数的映射关系;
所述终端根据待传输预设粒度上行业务数据、以及预设Qos映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数,包括:
所述终端识别所述待传输预设粒度上行业务数据的特征信息;
所述终端根据所述待传输预设粒度上行业务数据的特征信息、以及所述 预设特征信息与Qos需求参数的映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
可选地,所述特征信息包括下述一项或其任意组合:协议层的端口号、特征字、关联特征、数据流行为;其中,所述关联特征指联合识别的多个特征字。
可选地,所述预设Qos映射关系为:预设Qos标识与Qos需求参数的映射关系;
所述终端根据所述待传输预设粒度上行业务数据、以及预设服务质量Qos映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数,包括:
所述终端获取所述待传输预设粒度上行业务数据中的Qos标识;
所述终端根据所述待传输预设粒度上行业务数据中的Qos标识、以及所述预设Qos标识与Qos需求参数的映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
进一步地,所述Qos需求参数包括下述至少一项或其任意组合:流聚合最大比特速率AMBR、无线承载AMBR、终端AMBR、优先级、时间延迟、丢包率、切换特性、时变特性、分配保留优先级ARP。
可选地,所述终端获取所述待传输预设粒度上行业务数据对应的Qos需求参数之前,还包括:
所述终端接收核心网控制功能实体或RAN网元发送的Qos增强属性信息;相应地,
所述终端获取所述待传输预设粒度上行业务数据对应的Qos需求参数,包括:
所述终端根据所述待传输预设粒度上行业务数据对应的Qos增强属性信息、以及预设Qos映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
进一步地,所述Qos增强属性信息包括下述任一项或其任意组合:时变属性、分类属性、粒度属性;
其中,所述时变属性用于标识业务过程中业务数据的状态是否随时间变化、且Qos需求参数是否随业务数据的状态变化;所述分类属性用于标识业 务数据是否根据Qos需求参数分类;所述粒度属性用于标识Qos的处理粒度。
可选地,所述终端根据所述待传输预设粒度上行业务数据对应的Qos需求参数,传输所述待传输预设粒度上行业务数据,包括:
所述终端根据所述待传输预设粒度上行业务数据对应的Qos需求参数,调整所述待传输预设粒度上行业务数据对应的逻辑信道的调度策略,采用调整后的逻辑信道向RAN网元传输所述待传输预设粒度上行业务数据。
可选地,所述终端根据所述待传输预设粒度上行业务数据对应的Qos需求参数,传输所述待传输预设粒度上行业务数据,包括:
所述终端根据所述待传输预设粒度上行业务数据对应的Qos需求参数、以及预设Qos需求参数与子RB之间的映射关系,将所述待传输预设粒度上行业务数据映射到对应的子无线承载RB上传输。
可选地,所述终端根据所述待传输预设粒度上行业务数据对应的Qos需求参数、以及预设Qos需求参数与子RB之间的映射关系,将所述待传输预设粒度上行业务数据映射到对应的子无线承载RB上传输之前,还包括:
所述终端接收所述RAN网元发送的所述预设Qos需求参数与子RB之间的映射关系。
可选地,所述终端根据所述待传输预设粒度上行业务数据对应的Qos需求参数,传输所述待传输预设粒度上行业务数据,包括:
终端采用各协议层对应的预设处理模板传输所述待传输预设粒度上行业务数据,其中,不同所述预设处理模板对应的Qos需求参数不同。
本发明实施例第三方面提供一种数据传输的方法,包括:
核心网控制功能实体CN CP生成服务质量Qos映射关系,所述Qos映射关系用于表示预设粒度业务数据与Qos需求参数的映射关系;
所述CN CP将所述Qos映射关系发送给无线接入网网元。
可选地,所述方法还包括:
所述CN CP向终端发送所述Qos映射关系。
可选地,所述Qos映射关系包括:业务数据特征信息与Qos需求参数的映射关系。
可选地,所述特征信息包括下述一项或其任意组合:协议层的端口号、特征字、关联特征、数据流行为;其中,所述关联特征指联合识别的多个特 征字。
可选地,所述Qos映射关系包括:业务数据中Qos标识与Qos需求参数的映射关系。
可选地,所述预设服务质量Qos映射关系为:预设通道标识与Qos需求参数的映射关系。
进一步地,所述方法还包括:
所述CN CP向核心网用户面功能实体发送至少一套Qos需求参数。
本发明实施例第四方面提供一种数据传输的装置,包括:
获取模块,用于获取预设粒度业务数据;
确定模块,用于获取所述预设粒度业务数据对应的Qos需求参数;将所述预设粒度业务数据进行Qos需求分类,并根据所述预设粒度业务数据对应的Qos需求参数确定所述预设粒度业务数据所属分类对应的Qos需求参数;
传输模块,用于根据所述预设粒度业务数据所属分类传输所述预设粒度业务数据。
可选地,所述确定模块,具体用于根据所述预设粒度业务数据的属性信息、以及预设服务质量Qos映射关系,获取所述预设粒度业务数据对应的Qos需求参数。
其中,所述预设粒度业务数据的属性信息包括下述任一项或其任意组合:预设特征信息、预设标识、预设通道标识。
可选地,所述预设服务质量Qos映射关系为:预设特征信息与Qos需求的映射关系;
所述确定模块,具体用于识别所述预设粒度业务数据中的特性信息;根据所述预设粒度业务数据中的特性信息、以及预设特征信息与Qos需求参数的映射关系,获取所述预设粒度业务数据对应的Qos需求参数。
可选地,所述特征信息包括下述一项或其任意组合:协议层的端口号、特征字、关联特征、数据流行为;其中,所述关联特征指联合识别的多个特征字。
可选地,所述预设服务质量Qos映射关系为:预设Qos标识与Qos需求参数的映射关系;
所述确定模块,具体用于根据预设规则获取所述预设粒度业务数据中的 Qos标识;根据所述预设粒度业务数据中的Qos标识、以及所述预设Qos标识与Qos需求参数的映射关系,获取所述预设粒度业务数据对应的Qos需求参数。
可选地,所述确定模块用于根据预设规则获取所述预设粒度业务数据中的Qos标识,具体为:根据预设规则,在所述预设粒度业务数据的数据包头中获取Qos标识。
可选地,所述预设服务质量Qos映射关系为:预设通道标识与Qos需求参数的映射关系;
所述确定模块,具体用于确定接收所述预设粒度业务数据的通道;根据所述接收所述预设粒度业务数据的通道、以及预设通道标识与Qos需求参数的映射关系,获取所述预设粒度业务数据对应的Qos需求参数。
可选地,所述Qos需求包括下述至少一项或其任意组合:流聚合最大比特速率AMBR、无线承载AMBR、终端AMBR、优先级、时间延迟、丢包率、切换特性、时变特性、分配保留优先级ARP。
可选地,所述装置还包括:
接收模块,用于接收获取Qos增强属性信息;
所述确定模块,具体用于根据所述预设粒度业务数据的Qos增强属性信息、以及预设Qos映射关系,获取所述预设粒度业务数据对应的Qos需求参数。
可选地,所述Qos增强属性信息包括下述任一项或其任意组合:时变属性、分类属性、粒度属性;
其中,所述时变属性用于标识业务过程中业务数据的状态是否随时间变化、且Qos需求参数是否随业务数据的状态变化;所述分类属性用于标识业务数据是否根据Qos需求参数分类;所述粒度属性用于标识Qos的处理粒度。
可选地,所述Qos增强属性信息包括时变属性时,所述预设Qos映射关系包括:业务数据的状态与Qos需求参数的映射关系;
所述确定模块,具体用于获取所述预设粒度业务数据的当前业务状态;根据所述预设粒度业务数据的当前业务状态、以及所述业务数据的状态与Qos需求参数的映射关系,确定所述预设粒度业务数据的当前业务状态对应的Qos需求参数。
可选地,所述接收模块,还用于接收应用层服务器发送的业务状态变化通知;
所述确定模块,还用于根据所述业务状态变化通知,确定所述预设粒度业务数据的当前业务状态。
可选地,所述传输模块,具体用于将所述预设粒度业务数据所属分类对应的Qos需求参数作为介质访问控制MAC层的调度输入,通过MAC层调度传输所述预设粒度业务数据。
进一步地,所述装置还包括:
生成模块,用于生成多个子无线承载,每个子无线承载对应不同的Qos需求参数;相应地,
所述传输模块,具体用于根据所述预设粒度业务数据所属分类对应的Qos需求参数、以及子无线承载与Qos需求参数的映射关系,选择对应的子无线承载传输所述预设粒度业务数据。
可选地,所述传输模块,具体用于根据所述预设粒度业务数据所属分类对应的Qos需求参数,选择各协议层所采用的处理模板,其中,不同的所述处理模板对应的Qos需求参数不同;根据所述各协议层所采用的处理模板传输所述预设粒度业务数据。
可选地,所述获取模块,还用于获取所述预设Qos映射关系。
可选地,所述传输模块,还用于向终端发送所述预设Qos映射关系。
本发明实施例第五方面提供一种数据传输的装置,包括:
获取模块,用于获取待传输预设粒度上行业务数据;
确定模块,用于获取所述待传输预设粒度上行业务数据对应的Qos需求参数;
传输模块,用于根据所述待传输预设粒度上行业务数据对应的Qos需求参数,传输所述待传输预设粒度上行业务数据。
可选地,所述确定模块,具体用于根据所述待传输预设粒度上行业务数据、以及预设服务质量Qos映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
可选地,所述预设服务质量Qos映射关系为:预设特征信息与Qos需求参数的映射关系;
所述确定模块,具体用于识别所述待传输预设粒度上行业务数据的特征信息;根据所述待传输预设粒度上行业务数据的特征信息、以及所述预设特征信息与Qos需求参数的映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
可选地,所述特征信息包括下述一项或其任意组合:协议层的端口号、特征字、关联特征、数据流行为;其中,所述关联特征指联合识别的多个特征字。
可选地,所述预设Qos映射关系为:预设Qos标识与Qos需求参数的映射关系;
所述确定模块,具体用于获取所述待传输预设粒度上行业务数据中的Qos标识;根据所述待传输预设粒度上行业务数据中的Qos标识、以及所述预设Qos标识与Qos需求参数的映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
可选地,所述Qos需求包括下述至少一项或其任意组合:流聚合最大比特速率AMBR、无线承载AMBR、终端AMBR、优先级、时间延迟、丢包率、切换特性、时变特性、分配保留优先级ARP。
可选地,所述装置还包括:第一接收模块,用于接收核心网控制功能实体或RAN网元发送的Qos增强属性信息;相应地,
所述确定模块,具体用于根据所述待传输预设粒度上行业务数据对应的Qos增强属性信息、以及预设Qos映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
可选地,所述Qos增强属性信息包括下述任一项或其任意组合:时变属性、分类属性、粒度属性;
其中,所述时变属性用于标识业务过程中业务数据的状态是否随时间变化、且Qos需求参数是否随业务数据的状态变化;所述分类属性用于标识业务数据是否根据Qos需求参数分类;所述粒度属性用于标识Qos的处理粒度。
可选地,所述传输模块,具体用于根据所述待传输预设粒度上行业务数据对应的Qos需求参数,调整所述待传输预设粒度上行业务数据对应的逻辑信道的调度策略,采用调整后的逻辑信道向RAN网元传输所述待传输预设粒度上行业务数据。
可选地,所述传输模块,具体用于根据所述待传输预设粒度上行业务数据对应的Qos需求参数、以及预设Qos需求参数与子RB之间的映射关系,将所述待传输预设粒度上行业务数据映射到对应的子无线承载RB上传输。
进一步地,所述装置还包括:第二接收模块,用于接收所述RAN网元发送的所述预设Qos需求与子RB之间的映射关系。
可选地,所述传输模块,具体用于采用各协议层对应的预设处理模板对所述待传输预设粒度上行业务数据进行Qos处理,并将处理后的所述待传输预设粒度上行业务数据发送给RAN网元。
本发明实施例第六方面提供一种数据传输的装置,包括:
生成模块,用于生成服务质量Qos映射关系,所述Qos映射关系用于表示预设粒度业务数据与Qos需求参数的映射关系;
发送模块,用于将所述Qos映射关系发送给无线接入网网元。
可选地,所述发送模块,还用于将所述Qos映射关系发送给无线接入网网元。
可选地,所述Qos映射关系包括:业务数据特征信息与Qos需求的映射关系。
可选地,所述业务数据特征信息包括下述一项或其任意组合:协议层的端口号、特征字、关联特征、数据流行为;其中,所述关联特征指联合识别的多个特征字。
可选地,所述Qos映射关系包括:业务数据中Qos标识与Qos需求参数的映射关系。
可选地,所述预设服务质量Qos映射关系为:预设通道标识与Qos需求参数的映射关系。
可选地,所述发送模块,还用于向核心网用户面功能实体发送至少一套Qos需求参数。
本发明实施例第七方面提供一种数据传输的装置,包括:存储器、处理器、接收器以及发送器。其中:存储器、处理器、接收器以及发送器通过总线连接。
处理器,用于获取预设粒度业务数据;获取所述预设粒度业务数据对应的Qos需求参数;将所述预设粒度业务数据进行Qos需求分类,并根据所述 预设粒度业务数据对应的Qos需求参数确定所述预设粒度业务数据所属分类对应的Qos需求参数;根据所述预设粒度业务数据所属分类传输所述预设粒度业务数据。
可选地,处理器,具体用于根据所述预设粒度业务数据的属性信息、以及预设服务质量Qos映射关系,获取所述预设粒度业务数据对应的Qos需求参数。
其中,所述预设粒度业务数据的属性信息包括下述任一项或其任意组合:预设特征信息、预设标识、预设通道标识。
可选地,所述预设服务质量Qos映射关系为:预设特征信息与Qos需求的映射关系;
处理器具体用于识别所述预设粒度业务数据中的特性信息;根据所述预设粒度业务数据中的特性信息、以及预设特征信息与Qos需求参数的映射关系,获取所述预设粒度业务数据对应的Qos需求参数。
其中,所述特征信息包括下述一项或其任意组合:协议层的端口号、特征字、关联特征、数据流行为;其中,所述关联特征指联合识别的多个特征字。
可选地,所述预设服务质量Qos映射关系为:预设Qos标识与Qos需求参数的映射关系;
处理器,具体用于根据预设规则获取所述预设粒度业务数据中的Qos标识;根据所述预设粒度业务数据中的Qos标识、以及所述预设Qos标识与Qos需求参数的映射关系,获取所述预设粒度业务数据对应的Qos需求参数。
可选地,处理器用于根据预设规则获取所述预设粒度业务数据中的Qos标识,具体为:根据预设规则,在所述预设粒度业务数据的数据包头中获取Qos标识。
可选地,所述预设服务质量Qos映射关系为:预设通道标识与Qos需求参数的映射关系;处理器具体用于确定接收所述预设粒度业务数据的通道;根据所述接收所述预设粒度业务数据的通道、以及预设通道标识与Qos需求参数的映射关系,获取所述预设粒度业务数据对应的Qos需求参数。
可选地,所述Qos需求包括下述至少一项或其任意组合:流聚合最大比特速率AMBR、无线承载AMBR、终端AMBR、优先级、时间延迟、丢包率、 切换特性、时变特性、分配保留优先级ARP。
可选地,所述接收器,用于接收获取Qos增强属性信息;
所述处理器具体用于根据所述预设粒度业务数据的Qos增强属性信息、以及预设Qos映射关系,获取所述预设粒度业务数据对应的Qos需求参数。
可选地,所述Qos增强属性信息包括下述任一项或其任意组合:时变属性、分类属性、粒度属性;
其中,所述时变属性用于标识业务过程中业务数据的状态是否随时间变化、且Qos需求参数是否随业务数据的状态变化;所述分类属性用于标识业务数据是否根据Qos需求参数分类;所述粒度属性用于标识Qos的处理粒度。
可选地,所述Qos增强属性信息包括时变属性时,所述预设Qos映射关系包括:业务数据的状态与Qos需求参数的映射关系;
处理器,具体用于获取所述预设粒度业务数据的当前业务状态;根据所述预设粒度业务数据的当前业务状态、以及所述业务数据的状态与Qos需求参数的映射关系,确定所述预设粒度业务数据的当前业务状态对应的Qos需求参数。
可选地,接收器还用于接收应用层服务器发送的业务状态变化通知;处理器,还用于根据所述业务状态变化通知,确定所述预设粒度业务数据的当前业务状态。
可选地,处理器,具体用于将所述预设粒度业务数据所属分类对应的Qos需求参数作为介质访问控制MAC层的调度输入,通过MAC层调度传输所述预设粒度业务数据。
可选地,处理器,还用于生成多个子无线承载,每个子无线承载对应不同的Qos需求参数。且根据所述预设粒度业务数据所属分类对应的Qos需求参数、以及子无线承载与Qos需求参数的映射关系,选择对应的子无线承载传输所述预设粒度业务数据。
可选地,处理器,具体用于根据所述预设粒度业务数据所属分类对应的Qos需求参数,选择各协议层所采用的处理模板,其中,不同的所述处理模板对应的Qos需求参数不同;根据所述各协议层所采用的处理模板传输所述预设粒度业务数据。
可选地,处理器,还用于获取所述预设Qos映射关系。
可选地,发送器,用于向终端发送所述预设Qos映射关系。
本发明实施例第八方面提供一种数据传输的装置,包括:存储器、处理器、接收器以及发送器。其中:
存储器、处理器、接收器以及发送器通过总线连接。
处理器,用于获取待传输预设粒度上行业务数据;获取所述待传输预设粒度上行业务数据对应的Qos需求参数;根据所述待传输预设粒度上行业务数据对应的Qos需求参数,传输所述待传输预设粒度上行业务数据。
可选地,处理器,具体用于根据所述待传输预设粒度上行业务数据、以及预设服务质量Qos映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
可选地,所述预设服务质量Qos映射关系为:预设特征信息与Qos需求参数的映射关系;处理器,具体用于识别所述待传输预设粒度上行业务数据的特征信息;根据所述待传输预设粒度上行业务数据的特征信息、以及所述预设特征信息与Qos需求参数的映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
可选地,所述特征信息包括下述一项或其任意组合:协议层的端口号、特征字、关联特征、数据流行为;其中,所述关联特征指联合识别的多个特征字。
可选地,所述预设Qos映射关系为:预设Qos标识与Qos需求参数的映射关系;处理器,具体用于获取所述待传输预设粒度上行业务数据中的Qos标识;根据所述待传输预设粒度上行业务数据中的Qos标识、以及所述预设Qos标识与Qos需求参数的映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
进一步地,所述Qos需求参数包括下述至少一项或其任意组合:流聚合最大比特速率AMBR、无线承载AMBR、终端AMBR、优先级、时间延迟、丢包率、切换特性、时变特性、分配保留优先级ARP。
可选地,接收器,用于接收核心网控制功能实体或RAN网元发送的Qos增强属性信息;处理器,具体用于根据所述待传输预设粒度上行业务数据对应的Qos增强属性信息、以及预设Qos映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
可选地,所述Qos增强属性信息包括下述任一项或其任意组合:时变属性、分类属性、粒度属性;
其中,所述时变属性用于标识业务过程中业务数据的状态是否随时间变化、且Qos需求参数是否随业务数据的状态变化;所述分类属性用于标识业务数据是否根据Qos需求参数分类;所述粒度属性用于标识Qos的处理粒度。
可选地,处理器,根据所述待传输预设粒度上行业务数据对应的Qos需求参数,调整所述待传输预设粒度上行业务数据对应的逻辑信道的调度策略,采用调整后的逻辑信道向RAN网元传输所述待传输预设粒度上行业务数据。
可选地,处理器,具体用于根据所述待传输预设粒度上行业务数据对应的Qos需求参数、以及预设Qos需求参数与子RB之间的映射关系,将所述待传输预设粒度上行业务数据映射到对应的子无线承载RB上传输。
可选地,接收器,用于接收所述RAN网元发送的所述预设Qos需求与子RB之间的映射关系。
可选地,处理器,具体用于采用各协议层对应的预设处理模板对所述待传输预设粒度上行业务数据进行Qos处理,并将处理后的所述待传输预设粒度上行业务数据发送给RAN网元。
本发明实施例第九方面提供一种数据传输的装置,包括:存储器、处理器、接收器以及发送器。其中:
存储器、处理器、接收器以及发送器通过总线连接。
处理器,用于生成服务质量Qos映射关系,所述Qos映射关系用于表示预设粒度业务数据与Qos需求参数的映射关系;
发送器,用于将所述Qos映射关系发送给无线接入网网元。
可选地,发送器,还用于将所述Qos映射关系发送给无线接入网网元。
可选地,所述Qos映射关系包括:业务数据特征信息与Qos需求的映射关系。
可选地,所述特征信息包括下述一项或其任意组合:协议层的端口号、特征字、关联特征、数据流行为;其中,所述关联特征指联合识别的多个特征字。
可选地,所述Qos映射关系包括:业务数据中Qos标识与Qos需求参数的映射关系。
可选地,所述预设服务质量Qos映射关系为:预设通道标识与Qos需求参数的映射关系。
可选地,发送器,还用于向核心网用户面功能实体发送至少一套Qos需求参数。
本发明实施例提供的数据传输的方法及装置中,RAN网元获取预设粒度业务数据,进一步地RAN网元获取上述预设粒度业务数据的Qos需求参数,并对预设粒度业务数据进行Qos需求分类、确定预设粒度业务数据所属分类对应的Qos需求参数,进而RAN网元根据所述预设粒度业务数据所属分类传输所述预设粒度业务数据,实现了RAN网元可以获知不同预设粒度业务数据对应的不同Qos需求参数,在收到预设粒度业务数据后,根据所述预设粒度业务数据所属分类分别传输所述预设粒度业务数据,以满足不同预设粒度业务数据的Qos需求。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案,下面将对实施例或现有技术描述中所需要使用的附图作一简单地介绍,显而易见地,下面描述中的附图是本发明的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动性的前提下,还可以根据这些附图获得其他的附图。
图1为本发明提供的数据传输的方法应用场景示意图;
图2为本发明提供的数据传输的方法实施例一的流程示意图;
图3为本发明提供的数据传输的方法实施例二的流程示意图;
图4为本发明提供的数据传输的方法实施例三的流程示意图;
图5为本发明提供的数据传输的方法的处理场景示意图;
图6为本发明提供的数据传输的方法的另一处理场景示意图;
图7为本发明提供的数据传输的方法的另一处理场景示意图;
图8为本发明提供的数据传输的方法的另一处理场景示意图;
图9为本发明提供的数据传输的方法实施例四的流程示意图;
图10为本发明提供的数据传输的装置实施例一的结构示意图;
图11为本发明提供的数据传输的装置实施例二的结构示意图;
图12为本发明提供的数据传输的装置实施例三的结构示意图;
图13为本发明提供的数据传输的装置实施例四的结构示意图;
图14为本发明提供的数据传输的装置实施例五的结构示意图;
图15为本发明提供的数据传输的装置实施例六的结构示意图;
图16为本发明提供的数据传输的装置实施例七的结构示意图;
图17为本发明提供的无线接入网网元实施例一的结构示意图;
图18为本发明提供的终端实施例一的结构示意图;
图19为本发明提供的核心网网元实施例一的结构示意图。
具体实施方式
本发明实施例中的终端,可以是无线终端也可以是有线终端,无线终端可以是指向用户提供语音和/或其他业务数据连通性的设备,具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备。无线终端可以经无线接入网(Radio Access Network,简称RAN)与一个或多个核心网进行通信,无线终端可以是移动终端,如移动电话(或称为“蜂窝”电话)和具有移动终端的计算机,例如,可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置,它们与无线接入网交换语言和/或数据。例如,个人通信业务(Personal Communication Service,简称PCS)电话、无绳电话、会话发起协议(Session Initiation Protocol,简称SIP)话机、无线本地环路(Wireless Local Loop,简称WLL)站、个人数字助理(Personal Digital Assistant,简称PDA)等设备。无线终端也可以称为系统、订户单元(Subscriber Unit)、订户站(Subscriber Station),移动站(Mobile Station)、移动台(Mobile)、远程站(Remote Station)、远程终端(Remote Terminal)、接入终端(Access Terminal)、用户终端(User Terminal)、用户代理(User Agent)、用户设备(User Device or User Equipment),在此不作限定。
图1为本发明提供的数据传输的方法应用场景示意图,该方法应用于通信系统中,该通信系统可以是LET系统,也可以是未来的下一代通信系统等,在此不作限制。如图1所示,该系统可以包括:核心网(Core Network,简称CN)、无线接入网(Radio access network,简称RAN)以及终端。
其中,核心网的网元可以包括核心网控制面功能实体(core network control plane,简称CN CP)和核心网用户面功能实体(core network user plane,简称CN UP)。
可选地,参见图1,RAN除了包括RAN网元,还可以包括RAN控制器(controller)。可以根据具体情况进行确定,不是每个场景都需要RAN controller。
如果图1所示通信系统是LTE系统,那么核心网可以包括:移动管理实体(Mobility Management Entity,简称MME)、分组数据网网关(Packet Data Network Gateway,简称P-GW)、服务网关(Serving Gateway,简称S-GW)等网元。
需要说明的是,CN CP还可以与应用层服务器通信连接。
另外,本发明实施例所应用的系统还可以包括一些辅助实体,例如:HSS、OAM、PCRF等。
上述这些实体逻辑是都是独立的,物理部署上可以都是独立的,也可以部分实体部署在同一物理位置,在此不作限制。
参见图1,本发明实施例涉及到的网元中:
CN CP负责终端的会话管理、移动性管理、Qos控制、签约信息管理等功能;
CN UP负责业务数据转发等功能;
RAN控制器负责RAN的控制,具体可以包括:资源分配、移动性管理等;
RAN网元,例如可以是基站,具备业务建立和移动性功能、以及业务数据调度等功能;
终端,具备数据的发送、接收、测量等功能。
本发明实施例中,RAN网元包括但不限于基站和/或终端。
随着通信需求的多样化发展,不同业务的实际Qos需求并不相同,尤其是时频和互联网业务的不断发展,对Qos的需求也更加细化和动态。
本发明实施例中,通过核心网网元向无线接入网网元通知不同业务的不同Qos需求,即无线接入网网元可以获得更细粒度的Qos需求,并针对不同的业务数据进行Qos处理,以更好地满足不同业务的实际Qos需求。
具体地,RAN网元获取预设粒度业务数据,并按照预设粒度业务数据的Qos需求参数进行Qos分类,按照预设粒度业务数据的Qos分类传输该预设粒度业务数据。
图2为本发明提供的数据传输的方法实施例一的流程示意图,如图2所示,该方法包括:
S201、CN UP接收应用层服务器发送的业务数据。
S202、CN UP按照预设粒度将业务数据划分为至少一个预设粒度业务数据。
CN UP划分的预设粒度可以是:flow,和/或,RB。这个预设粒度可以是预先配置给CN UP的。但并不以此为限,预设粒度还可以是无线接入承载(Evolved Radio Access Bearer,简称E-RAB)、会话(session)等。
预设粒度业务数据的Qos需求不同,可以是指与同一E-RAB、同一bear,同flow、同一类型、或者同一session的数据与其他数据不同的Qos需求。
例如同一类型的微信业务中,微信红包业务与其他业务的Qos需求不同。同一应用业务中,贵宾(very important person,简称VIP)用户的业务数据与其他业务数据的Qos需求不同。在此不作限制,可以根据具体实现场景进行划分。
S203、CN UP向RAN网元发送预设粒度业务数据。
S204、RAN网元接收CN UP发送的预设粒度业务数据。
可选地,也可以是CN UP向RAN网元发送业务数据,由RAN网元将业务数据划分为预设粒度业务数据,在此不作限制。
S205、RAN网元获取上述预设粒度业务数据对应的Qos需求参数。
可选地,RAN网元根据上述预设粒度业务数据对应的属性信息、以及预设预设Qos映射关系,获取上述预设粒度业务数据对应的Qos需求参数。
属性信息可以包括下述一种或任意组合:预设特征信息、预设标识、预设通道标识。
该预设Qos映射关系可以由CN CP通知给RAN网元,进而RAN收到预设粒度业务数据后,就可以根据不同的预设粒度业务数据、以及预设Qos映射关系,获取不同预设粒度业务数据对应的不同Qos需求参数。
可选地,Qos需求参数包括下述至少一项或其任意组合:流(flow)聚合 最大比特速率(AMBR)、无线承载(RB-AMBR)、终端AMBR、优先级、延迟特性、丢包特性、切换特性、时变特性、分配保留优先级(Allocation and Retention Priority,简称ARP)。
每套Qos需求参数体现出不同的Qos需求,具体可能表现为:flow-AMBR不同、RB-AMBR不同、终端AMBR不同、优先级的不同、延迟的不同、丢包率的不同速率的不同、分配保留优先级(Allocation and Retention Priority,简称ARP)的不同、切换性能不同等,在此不作限制。即每套Qos需求参数可能是所包含Qos需求参数内容不同,和/或,具体某个参数值不同。
其中所述切换性能,是指业务对切换性能的需求,例如切换时延的需求、丢包率的需求、sesssion连续性的需求等其中一项或多项。这里的切换具体可以指终端在小区间的切换。
S206、RAN网元根据上述预设粒度业务数据的Qos需求参数,对该预设粒度业务数据进行Qos处理。
具体实现过程中,RAN网元根据上述预设粒度业务数据的Qos需求参数,对该预设粒度业务数据进行Qos处理可以是:RAN网元将上述预设粒度业务数据进行Qos需求分类,并根据上述预设粒度业务数据对应的Qos需求参数确定预设粒度业务数据所属分类对应的Qos需求参数;进而RAN网元根据所述预设粒度业务数据所属分类传输所述预设粒度业务数据。
其中,CN UP可以给每个预设粒度业务数据加上分类标签,或者,采用不同的通道发送不同分类的预设粒度业务数据,即同样Qos需求的业务数据采用同一个通道发送,以便于RAN网元将上述预设粒度业务数据进行Qos需求分类。
RAN网元获取到不同业务数据对应的不同Qos需求参数之后,就可以具体根据不同业务数据的Qos需求参数,对不同业务数据进行区分处理,以满足不同业务的不同Qos需求。
本实施例中,RAN网元获取预设粒度业务数据,进一步地RAN网元获取上述预设粒度业务数据的Qos需求参数,并对预设粒度业务数据进行Qos需求分类、确定预设粒度业务数据所属分类对应的Qos需求参数,进而RAN网元根据所述预设粒度业务数据所属分类传输所述预设粒度业务数据,实现了RAN网元可以获知不同预设粒度业务数据对应的不同Qos需求参数,在 收到预设粒度业务数据后,根据所述预设粒度业务数据所属分类分别传输所述预设粒度业务数据,以满足不同预设粒度业务数据的Qos需求。
可选地,CN UP向RAN网元发送预设粒度业务数据,可以是CN UP按照预设粒度业务数据对应的不同Qos需求参数分别发送。
CN CP可以向CN UP发送多套Qos需求参数。可选地,具体可以是CN UP根据多套Qos需求参数、以及Qos需求参数与数据特征的映射关系等,确定预设粒度业务数据对应的Qos需求参数。具体地,CN UP可以结合每个数据包的一些其他信息,例如源互联网协议(Internet Protocol,简称IP)地址,目的IP地址,源端口地址,目标端口地址等,确定每个数据包的Qos需求。
一种方式中,CN UP将不同Qos需求参数对应的预设粒度业务数据加上不同的Qos标识,以便于RAN网元根据Qos标识可以确定预设粒度业务数据对应的Qos需求参数。这种情况下,每个Qos标识所代表的Qos需求参数需要先通知RAN侧网元。
S201之前,CN CP可以将Qos标识与预设粒度(flow,和/或,RB)的对应关系通知CN UP、以及RAN网元。
CN UP识别每个数据包所属的“flow,和/或,RB”,如果至少一个数据包属于同一个流或同一个RB,或者既属于同一个流也属于同一个RB,CN UP就将这至少一个数据包加上相同的Qos标识。
或者,另一种方式中,CN UP采用多个不同的通道分别向RAN网元发送不同Qos需求参数对应的预设粒度业务数据,其中,每个通道对应一套Qos需求参数,即可以将Qos需求参数相同的预设粒度业务数据在一个通道发送,RAN网元根据接收上述预设粒度业务数据的通道可以确定出预设粒度业务数据对应的Qos需求参数。这种情况下,每个通道标识所代表的Qos需求参数需要先通知RAN侧网元。
S201之前,CN CP可以将通道标识与预设粒度(flow,和/或,RB)的对应关系通知CN UP、以及RAN网元。
CN UP识别每个数据包所对应的通道,具体地,如果至少一个数据包属于同一个流或同一个RB,或者既属于同一个流也属于同一个RB,CN UP就将这至少一个数据包通过相同的通道发送给RAN网元。
或者,可选地,CN CP预先向RAN网元发送Qos需求参数与过滤模板参数之间的映射关系,以使RAN网元根据Qos需求参数与过滤模板参数之间的映射关系,建立相应的过滤模板。RAN网元将收到的每一个数据包过滤到不同Qos需求参数对应的队列中去,即RAN网元将收到的每一个数据包放到所属分类对应的队列中去。
需要说明的是,这里所说的RAN网元,包括基站侧的RAN数据处理实体,也包括终端,这里所述的终端,包括普通终端、低能力终端、超级省电终端等各种类型。
S201之前,CN CP可以将所使用的过滤模板参数与预设粒度(flow,和/或,RB)的对应关系通知CN UP、以及RAN网元。
具体地,CN CP可以在业务开始时向CN UP发送Qos需求参数,这种方式后续业务过程中Qos需求参数不再改变,适用于数据量波动很小、QoS无变化的业务,但不以此为限;或者,CN CP在业务开始时向CN UP发送Qos需求参数,并周期性地向CN UP发送更新的Qos需求参数,适用于数据量定期波动,QoS需求变化比较有规律的业务;或者,CN CP在业务开始时向CN UP发送Qos需求参数,后续根据实际需要向CN UP发送更新的Qos需求参数,触发CN UP改变Qos需求参数,适用于数据量波动,QoS需求变化没有规律,无法预期QoS需求变化的业务。
CN CP也可以采用上述类似的方式将上述Qos需求参数发送给RAN网元。
CN CP还可以采用上述类似的方式将上述Qos需求参数发送给终端。
当然,CN CP可以在不同时间向不同网元发送Qos需求参数,在此不作限制。
Qos需求参数可以包括下述任一种或其任意组合:流(flow)聚合最大比特速率(AMBR)、无线承载(RB-AMBR)、终端AMBR、优先级、时间延迟、丢包率、切换特性、时变特性、分配保留优先级ARP。
其中:flow AMBR可以理解为:某一些flow的整体最大比特速率,也就是说,将一个或多个flow看作一个整体,这些flow的比特速率之和不能大于某个最大门限,如果Qos需求参数中包括这一个参数,同时还需要指示一个“flow集合”,这个“flow集合”包括一个或多个flow。
RB-AMBR为:某一些RB的整体最大比特速率,也就是说,将一个或多个RB看作一个整体,这些RB的比特速率之和不能大于某个最大门限,如果Qos需求参数中包括这一个参数,同时还需要指示一个“RB集合”,这个“RB集合”包括一个或多个RB。
具体地,CN CP可以根据业务特性参数生成多套Qos需求参数。这里业务特性参数可以包括下述任一种或其任意组合:基于注册信息的QoS信息,基于本地运营商的QoS信息,基于网络分片的QoS信息,基于应用服务的QoS信息等。
可选地,可以由应用服务器向CN CP发送业务特性参数;或者,由归属签约用户服务器(Home Subscriber Server,简称HSS)预先为CN CP配置业务特性参数;或者,由操作管理维护(Operation Administration and Maintenance,简称OAM)预先为CN CP配置业务特性参数。当然并不以此为限,也可以由其他网元向CN CP发送业务特性参数、或者预先为CN CP配置业务特性参数。
可选地,CN CP可以根据业务特性参数、采用无线资源管理(Radio Resource Management,简称RRM)算法生成多套Qos需求参数,在此不作限制。
在上述实施例的基础上,该方法还包括:CN CP生成上述预设Qos映射关系,并将该预设Qos映射关系发送给无线接入网网元。CN CP还可以将上述预设Qos映射关系也直接发送给终端。
具体实现过程中,CN CP可以通过初始上下文建立(nitial Context Setup)、演进无线接入承载建立(E-RAB Setup)、演进无线接入承载修改(E-RAB Modify)等过程将上述预设Qos映射关系通知给RAN网元,和/或,终端。
可选地,核心网网元可以在业务建立或者业务修改过程中,向RAN网元发送上述预设Qos映射关系。
可选地,也可以在任一和终端/业务相关的过程中,核心网网元向RAN网元发送上述预设Qos映射关系。
当然,也可以由RAN网元向终端转发上述预设Qos映射关系,即可选地,RAN网元还可以将上述预设Qos映射关系发送到终端,终端接收到业务数据后,进行相应地Qos处理。
上述预设Qos映射关系可以有多种形式,针对不同的预设Qos映射关系,RAN网元获取预设粒度业务数据对应的Qos需求参数的方法也不同。
一种实施方式中,上述预设Qos映射关系为:预设特征信息与Qos需求参数的映射关系。一般地,预设特征信息用于描述业务数据的特征。
可选地,CN CP可以获取不同业务数据的应用层信息,或者还可以通过与应用服务器交互获取不同业务数据的应用层信息,进而获取不同业务数据的不同Qos需求参数,例如获取同一Bearer、同flow、同一类型、或者同一session中不同业务数据的不同Qos需求,对应的Qos需求参数不同,进而生成预设特征信息与Qos需求参数的映射关系。
其中,CN CP获取不同业务数据的应用层信息之后,可以根据预设规则获取不同业务数据的Qos需求参数,也可以与应用服务器协商获取不同业务数据的Qos需求参数。
例如,核心网网元读取微信业务的应用层数据信息,根据预设规则获取例如微信语音、微信文字、微信红包等不同业务数据对应的不同Qos需求参数。其中预设规则可以包括不同业务数据与不同Qos需求的映射关系等。
或者,核心网网元可与微信的服务器进行协商,预设微信业务中的不同业务数据的Qos需求,像微信语音、微信文字、微信红包等不同业务数据的不同Qos需求。
图3为本发明提供的数据传输的方法实施例二的流程示意图,如图3所示,上述RAN网元根据上述预设粒度业务数据对应的属性信息、以及预设预设Qos映射关系,获取上述预设粒度业务数据对应的Qos需求参数,可以包括:
S301、RAN网元识别上述预设粒度业务数据中的特征信息。
S302、RAN网元根据该预设粒度业务数据中的特征信息、以及预设特征信息与Qos需求参数的映射关系,获取上述预设粒度业务数据对应的Qos需求参数。
具体地,RAN网元收到预设粒度业务数据后,先识别特征信息,进而就可以根据预设特征信息与Qos需求参数的映射关系,得到该业务数据对应的Qos需求参数。
上述映射关系可以具体通过协议进行规定,在此不作限制。
可选地,上述特征信息可以包括:下述一项或其任意组合:协议层的IP地址、端口号、特征字、关联特征、数据流行为。
协议层的端口号,可以是传输控制协议(Transmission Control Protocol,简称TCP)中的某些特殊端口号,在此不作限定,也可以是其他协议层的端口号。
特征字可以是超文本传输协议(HyperText Transfer Protocol,简称HTTP)的报文特征字,例如“GET”、“POST”、“HTTP/1.1”、“HOST”等关键字,在此不作限制。
关联特征是指多个特征字的联合识别。
数据流行为是对数据流进行的行为识别,例如包括下述行为中的一项或任意组合:报文中端口的范围、报文长度统计(报文长度序列、报文长度集合、报文长度范围、报文长度平均值、轮次报文长度求和等)、报文发送频度、报文收发比例以及目的地址的分散程度。
又一实施方式中,上述预设Qos映射关系为:预设Qos标识与Qos需求参数的映射关系。
图4为本发明提供的数据传输的方法实施例三的流程示意图,如图4所示,RAN网元根据上述预设粒度业务数据对应的属性信息、以及预设预设Qos映射关系,获取上述预设粒度业务数据对应的Qos需求参数,可以包括:
S401、RAN网元根据预设规则获取上述预设粒度业务数据中的Qos标识。
可选地,Qos标识可以携带在预设粒度业务数据包的协议层头部,其中预设粒度业务数据包中携带上述预设粒度业务数据。预设规则可以包括Qos标识的位置指示,即具体指示哪个比特位作为Qos标识。
即RAN网元根据预设规则获取上述预设粒度业务数据中的Qos标识,可以是:RAN网元根据预设规则,在上述预设粒度业务数据的数据包头中获取Qos标识。当然不以此为限。
例如,采用TCP头保留6位、GTPU头扩展空间、IP中的DSCP域等来作为Qos标识。可选地,DSCP域的不同值对应不同的Qos需求参数,例如00000001标识一套Qos需求参数、00000011标识另一套Qos需求参数,在此不作限制,可以根据Qos具体处理粒度或者Qos需求灵活进行设定。
S402、RAN网元根据上述预设粒度业务数据中的Qos标识、以及预设 Qos标识与Qos需求参数的映射关系,获取上述预设粒度业务数据对应的Qos需求参数。
具体地,CN CP可以预设多套子Qos需求参数,每套Qos需求参数都可以包括下述一项或任意组合:流AMBR、RB-AMBR、终端AMBR、优先级、延迟特性、丢包特性、切换特性、时变特性、ARP等,在此不作限制。
RAN网元收到携带预设粒度业务数据的预设粒度业务数据包后,获取Qos标识,进而就可以根据预设Qos标识与Qos需求参数的映射关系,得到该预设粒度业务数据对应的Qos需求参数,从而就可以进一步知道上述预设粒度业务数据的Qos需求。
可选地,上述Qos映射关系为:预设通道标识与Qos需求参数的映射关系。CN UP采用不同的通道发送不同Qos需求的预设粒度业务数据,即同一套Qos需求参数对应的预设粒度业务数据可以采用同一个通道发送。
类似的,上述RAN网元根据上述预设粒度业务数据对应的属性信息、以及预设预设Qos映射关系,获取上述预设粒度业务数据对应的Qos需求参数,可以包括:RAN网元确定接收上述预设粒度业务数据的通道,根据该接收上述预设粒度业务数据的通道、以及预设通道标识与Qos需求参数的映射关系,获取上述预设粒度业务数据对应的Qos需求参数。
进一步地,另一种实施方式中,RAN网元获取上述预设粒度业务数据对应的Qos需求参数之前,RAN网元还接收核心网网元发送的Qos增强属性信息。
相应地,RAN网元获取上述预设粒度业务数据对应的Qos需求参数,可以是:RAN网元根据上述预设粒度业务数据的Qos增强属性信息、以及预设Qos映射关系,获取上述预设粒度业务数据对应的Qos需求参数。
可选地,上述Qos增强属性信息包括下述任一项或其任意组合:时变属性、分类属性、粒度属性。
需要说明的是,(1)时变属性用于标识业务过程中业务数据的状态是否随时间变化、且Qos需求参数是否随业务数据的状态变化。
Qos需求参数的变化可以是Qos需求参数内容的变化,和/或,具体某个参数值的变化。
例如:视频业务在不同时间维度上会有不同Qos需求,例如在前奏、剧 情内容、广告、字幕部分的Qos需求可以是不同的,以及拖动视频时不同时刻位置包的Qos需求也不同,RAN可以考虑不同的处理方式;例如该视频业务数据包属于广告部分,则可采用与剧情内容数据包不同的Qos处理。而语音通话则可能要求在整个通话过程中Qos一直保持稳定,即Qos需求不随业务数据的状态变化。
(2)上述分类属性用于标识业务数据是否根据Qos需求参数分类。
同一业务数据的不同部分也可能对Qos的需求不同,需要对业务数据根据Qos需求参数进行分类。即使是同一业务的同一时段,也可能对应不同的Qos需求参数。
对于需要对业务数据根据Qos需求参数进行分类,可以在预设粒度业务数据中扩展预设字段作为分类信息标识,以具体标识业务数据中不同部分的分类信息。具体可以由应用层向RAN网元指示业务数据中的分类信息标识。
例如对于一个视频业务,考虑视频的不同帧,像视频初始阶段:动态部分先高优先级传输,背景部分优先级略低,后续多个背景帧进行联合实现高清晰度。
(3)上述粒度属性用于标识Qos的处理粒度。
对于不同的业务,其Qos需求可以不同,相应地,Qos处理的粒度也可以不同,例如可以按照“每片(per)bearer”的粒度来处理,或者,按照“流(flow)”的粒度来处理,或者,还可以按照“包(packet)”的粒度来处理,但并不以此为限。
RAN网元收到的Qos增强属性信息中包括粒度属性时,上述RAN网元根据上述预设粒度业务数据的类型及其它标识业务数据性质的参数、以及预设Qos映射关系,获取上述预设粒度业务数据对应的Qos需求参数之前,RAN网元可以根据粒度属性所具体指示的处理粒度选择不同粒度的过滤模板。例如,采用“流”的粒度来处理预设粒度业务数据,那么通过“流”粒度的过滤模板将上述预设粒度业务数据进行过滤,得到不同的flow。
这种方式中,CN UP可以向RAN网元发送较粗粒度的业务数据,在RAN网元处再进行更细粒度的划分。
可选地,在业务建立或修改过程中,CN CP向RAN网元、以及终端发送多套不同粒度的过滤模板。
RAN网元可以根据上述Qos增强属性信息的具体内容,决定是否根据上述预设粒度业务数据、以及预设Qos映射关系,获取上述预设粒度业务数据对应的Qos需求参数。
也就是说,并不一定所有的业务都要按照前述方法细粒度的确定Qos需求参数,可以根据具体地属性来确定是否有必要这样做,即在满足一定条件的情况下按照前述方法来获取业务数据对应的Qos需求参数。
可选地,在上述Qos增强属性信息包括时变属性,且时变属性标识该业务数据具有时变性,即业务过程中业务数据的状态随时间变化、且Qos需求随业务数据的状态变化,那么就根据上述预设粒度业务数据、以及预设Qos映射关系,获取上述预设粒度业务数据对应的Qos需求参数。相反,如果Qos增强属性不包含时变属性,或者包含时变属性、但时变属性标识该业务数据不具有时变性,那么就不需要获取上述预设粒度业务数据对应的Qos需求参数,例如可以按照现有技术进行粗粒度的Qos处理,在此不作限制。
可选地,在上述Qos增强属性信息包括分类属性,且分类属性标识上述业务数据需要进行Qos需求分类,那么就根据上述预设粒度业务数据、以及预设Qos映射关系,获取上述预设粒度业务数据对应的Qos需求参数。相反,如果Qos增强属性不包含分类属性,或者包含分类属性、但分类属性标识上述业务数据不需要进行Qos需求分类,那么就不需要获取上述预设粒度业务数据对应的Qos需求参数,例如可以按照现有技术进行粗粒度的Qos处理,在此不作限制。
可选地,在上述Qos增强属性信息包括粒度属性,且粒度属性标识处理粒度为“per bearer”或者“flow”时,就根据根据上述预设粒度业务数据、以及预设Qos映射关系,获取上述预设粒度业务数据对应的Qos需求参数。如果上述上述Qos增强属性信息包括粒度属性,且粒度属性标识处理粒度为“packet”时,表明处理粒度本身就较小,则无需根据上述预设粒度业务数据、以及预设Qos映射关系,获取上述预设粒度业务数据对应的Qos需求参数。如果Qos增强属性不包含上述粒度属性,也可以不获取预设粒度业务数据对应的Qos需求参数,进而可以按照现有技术进行粗粒度的Qos处理,在此不作限制。
可选地,也可以CN CP也可以根据上述Qos增强属性信息配置不同的 Qos需求参数,即根据预设粒度业务数据的Qos增强属性来满足预设粒度业务数据的Qos需求。
业务状态是时变的,不同的业务状态需要不同的Qos处理来保证业务需求。
进一步地,Qos增强属性信息包括时变属性时,预设Qos映射关系包括:业务数据的状态与Qos需求参数的映射关系。具体地,CN CP可以和应用层服务器协商确定多套Qos需求参数,例如:根据业务的需求变化和用户签约信息、核心网策略等信息生成多套Qos需求参数。每一套Qos需求参数对应着不同的业务状态。
对于时变属性,CN CP可以获取体现时变属性的特征,进而配置业务数据的状态与Qos需求参数的映射关系。
可选地,RAN网元获取上述预设粒度业务数据对应的Qos需求参数,可以是:RAN网元获取上述预设粒度业务数据的当前业务状态;RAN网元根据上述预设粒度业务数据的当前业务状态、以及上述业务数据的状态与Qos需求参数的映射关系,获取上述预设粒度业务数据的当前业务状态对应的Qos需求参数。
具体地,RAN网元可以实时监测上述预设粒度业务数据的业务状态,在预设粒度业务状态变换时,根据业务数据的状态与Qos需求参数的映射关系,确定预设粒度业务数据的当前业务状态对应的Qos需求参数。例如,RAN网元可以根据业务数据的特征信息来识别业务状态发生变化,但不以此为限。
可选地,也可以由应用层服务器向底层(CN CP、RAN网元、终端中的应用层的下层协议层,如网络侧)指示业务状态发生了变化,需要更改Qos需求参数。
即RAN网元根据上述预设粒度业务数据、以及预设Qos映射关系,获取上述预设粒度业务数据对应的Qos需求参数之前,RAN网元还可以接收应用层服务器发送的业务状态变换通知消息。业务状态变换通知消息中可以携带当前业务状态,那么RAN网元在收到业务状态变换通知消息后,根据业务状态变换通知消息确定预设粒度业务数据的当前业务状态,并根据上述业务数据的状态与Qos需求参数的映射关系,获取上述预设粒度业务数据的当前业务状态对应的Qos需求参数;或者,业务状态变换通知消息中可以直接携 带应用层指示的Qos需求参数,那么RAN网元可以直接根据业务状态变换通知消息确定预设粒度业务数据变更后的Qos需求参数。
举例说明,体现时变属性的特征可以包括:重复的数据包、数据包在分片(slice)中的位置、视频业务的时段信息等。具体地,可以通过协议的序号来检测重复的数据包,若判断是重复的数据包,则提供重复数据包的传输可靠性和/或优先级等Qos信息。例如,对于传输控制协议(Transmission Control Protocol,简称TCP)重传包,可以在RLC层处理时体现较高的优先级,从而实现跨层优化。
对于多个终端的视频业务,提供识别数据包(packet)在slice中位置的特征,例如:RAN网元收到业务数据包后,检测到位置在slice中前部的数据包,则可以根据上述业务数据的状态与Qos需求参数的映射关系,确定对应的Qos需求参数,一般对于位置在slice中前部的数据包可以相对提高发送的优先级等处理,以提高视频播放的流畅度、提高用户体验。
如果RAN网元收到的Qos增强属性信息中包括分类属性,则需要采用预设机制获取上述预设粒度业务数据不同分类部分对应的不同Qos需求参数,以便进一步进行Qos处理。
可选地,预设Qos映射关系可以包括:分类信息标识与Qos需求参数的映射关系。
RAN网元获取上述预设粒度业务数据对应的Qos需求参数,可以是:RAN网元获取上述预设粒度业务数据的分类信息标识;RAN网元根据上述预设粒度业务数据的分类信息标识、以及分类信息标识与Qos需求参数的映射关系,获取上述预设粒度业务数据中各分类部分分别对应的Qos需求参数。
进一步地,如果上述Qos增强属性信息中包括粒度属性,在业务建立或修改过程中,CN CP还可以向RAN网元、以及终端发送多套Qos需求参数,上述多套不同粒度的过滤模板和多套Qos需求参数一一对应。
相应地,预设Qos映射关系可以包括:过滤模板和Qos需求参数的映射关系,上述RAN网元获取上述预设粒度业务数据对应的Qos需求参数,可以是:
上述RAN网元根据所选择的过滤模板将上述预设粒度业务数据划分为至少一个过滤模板对应粒度的业务数据,并根据过滤模板和Qos需求参数的 映射关系,获取上述至少一个过滤模板对应粒度的业务数据分别对应的Qos需求参数。
需要说明的是,上述Qos增强属性都是可以动态变化的,例如一开始CN CP向RAN网元发送的Qos增强属性信息中包含时变属性,该时变属性指示业务过程中业务数据的状态随时间变化、且Qos需求随业务数据的状态变化。一段时间后,CN CP可以向RAN网元再发送Qos增强属性信息,该Qos增强属性信息依然包含时变属性,但是当前的时变属性指示业务过程中业务数据的状态不随时间变化、且Qos需求不随业务数据的状态变化。即时变属性由时变改变为非时变。也可能一段时间后CN CP向RAN网元再发送Qos增强属性信息,该Qos增强属性信息中不包含时变属性。
类似地,上述分类属性、粒度属性都可以动态变化。那么后续的Qos需求获取、以及Qos处理都会动态地发生变化。
当然,并不以上述举例为限。
图5为本发明提供的数据传输的方法的处理场景示意图,如图5所示,RAN网元可以将不同的多个协议层的功能统一处理,具体地,多个协议层从上到下可以包括:分组数据汇聚协议(Packet Data Convergence Protocol,简称PDCP)层、无线链路层控制协议(Radio Link Control,简称RLC)层、MAC层、以及物理(PHY)层。
在上述实施例的基础上,RAN网元需要根据不同预设粒度业务数据的不同Qos需求,进行区分处理。
RAN网元有多种方法可以进行区分处理,以下述几种方法举例说明,下述这几种方案可以根据具体需要结合使用,也可以独立使用,在此不作限制:
1、RAN网元根据上述预设粒度业务数据所属分类传输该预设粒度业务数据,可以是:
RAN网元将上述预设粒度业务数据所属分类对应的Qos需求参数作为MAC层的调度输入,通过MAC层调度对上述预设粒度业务数据进行Qos处理。
具体地,不同的业务数据,在MAC层可以考虑不同的优先级处理,即进行不同的优先级调度,或者,考虑不同的传输速率进行调度等,以满足业务数据的不同Qos需求。
当然不以此为限,还可以考虑上述流AMBR、RB-AMBR、终端AMBR、延迟特性、丢包特性、切换特性、时变特性、ARP等进行区别调度。
可选地,如果有些业务数据的Qos需求通过MAC层的调度还不能完全满足,那么可以结合以下两种方式进行Qos处理。
例如,某个预设粒度业务数据对应的Qos需求参数只涉及优先级、传输速率,那么通过MAC层的调度可以完全满足,就可以采用上述将预设粒度业务数据对应的Qos需求参数作为MAC层的调度输入的方式来进行Qos处理。
如果某个预设粒度业务数据的Qos需求还涉及切换特性、时变特性等,MAC调度在某些场景下可能不能很好的满足,那么可以采用下述的两种方案满足其他的Qos需求,仅采用MAC的调度完成部分Qos处理。当然,这种情况也可以直接选用下述的两种方案进行Qos处理。
后续终端的Qos处理也可以参照这种结合方式进行,在此不作限定。
2、RAN网元根据上述预设粒度业务数据对应的Qos需求参数,对上述预设粒度业务数据进行Qos处理之前,RAN网元生成多个子无线承载(radio bearer,简称RB),其中,每个子RB对应不同的Qos需求参数。
可选地,一种实施方法中,RAN网元可以动态生成多个子RB。具体地,RAN可以根据CN CP发送的预设Qos映射关系生成多个子RB。例如,RAN可以根据预设特征信息与Qos需求的映射关系,生成不同特征信息对应的多个子RB;或者,根据预设Qos标识与Qos需求参数的映射关系,生成不同Qos标识对应的多个子RB等,在此不作限制。
可选地,另一种实施方法中,CN CP向RAN网元发送多套Qos需求参数,RAN网元直接根据这多套Qos需求参数生成多个子RB,以使每个子RB对应一套Qos需求参数。
RAN网元生成多个子RB后,根据上述预设粒度业务数据所属分类传输该预设粒度业务数据,可以是:RAN网元根据上述预设粒度业务数据所属分类对应的Qos需求参数、以及子RB与Qos需求参数的映射关系,选择对应的子RB传输上述预设粒度业务数据。
需要说明的是,上述子RB与Qos需求参数的映射关系中,可以用不同的标识来表示不同的Qos需求参数,例如选用QCI来标识不同的Qos需求参 数,在此不作限制。
可选地,在上述实施例的基础上,还可以将不同的子RB配置在不同的小区(cell)组,例如可以将某些子RB配置在主小区组(Master Cell Group,简称MCG),将另一些子RB配置在第二小区组(Secondary Cell Group,简称SCG),并不以此为限。
具体实现过程中,可以将所对应Qos需求参数要求较高的子RB配置在小区负荷低、信道质量好的小区组中。
例如第一Qos需求参数的Qos要求高于第二Qos需求参数,MCG的小区负荷低于SCG、和/或、信道质量高于SCG,那么将第一Qos需求参数对应的子RB配置在MCG中。
进一步地,上述子RB可以根据对应的Qos需求参数,在不同的小区间切换。
可选地,如果某个子RB的数据吞吐量大于预设预置,RAN网元可以将该子RB上传输的业务数据分流,即将该子RB上传输的业务数据分流到多个小区进行传输,以提高数据传输速率和带宽。
图6为本发明提供的数据传输的方法的另一处理场景示意图,如图6所示,在同一小区内,上述RAN网元生成多个子RB,可以是在PDCP层以下的RLC层进行,即在RLC层生成多个子RB,每个子RB对应不同的Qos属性。
如图6所示,每个子RB对应一个RLC实体,图6以2个子RB为例,分别记为RLC实体1和RLC实体2。可选地,也可以每个子RB对应两个RLC实体,这两个RLC实体分别对应同一子RB的上行业务和下行业务;也可以两个RLC实体分别对应同一子RB内不同的flow,每个flow对应一个更加精细的QoS属性。
假设RAN网元的处理粒度为“流”,RAN网元接收到核心网用户面实体发送的数据后,会将数据分为多个流,以一个流为初传业务数据、另一个流为重传业务数据为例,这两个流的Qos需求不同,具体地,由于TCP中使用窗口机制,TCP期望底层按序向接收方TCP实体递交数据包,否则可能会触发快速重传,同时拥塞窗口减半,使链路吞吐量降低。但是对于TCP重传包,则要求越早递交越好,即收到业务数据包就会向接收方的TCP实体递交, 不要求按序递交。
实现过程中,RAN网元将多个流经过同一个PDCP实体处理后,交给不同的RLC实体处理,即一个RLC实体处理初传业务数据、另一个RLC实体处理重传业务数据。可选地,为了更好地获得分级增益,也可以两个RLC实体都处理重传业务数据,即其中一个RLC实体既处理初传业务数据、也处理重传业务数据,在此不作限制。
一种方式中,PDCP实体只对初传业务数据的包分配PDCP序列(SN),不对重传业务数据的包分配PDCP序列。处理初传业务数据的RLC实体收到初传业务数据的包后,会按照PDCP序列的顺序传递。在调度过程中,重传业务数据优先处理,也就是说:调度器先安排重传业务数据,如果还有剩余传输空间,再安排初传业务数据传输。需要说明的是,数据传递过程中,终端发生了切换,即切换到其他小区,那么处理重传业务数据的RLC实体中如果还有缓存数据,则将这些缓存数据返回PDCP实体,由PDCP实体在新的小区中再执行发送。
另一种方式中,对初传业务数据和重传业务数据统一分配PDCP序列,但是RLC作为接收方时,对于重传业务数据的包还是直接进行传递,不作按序传递。但是由于统一分配PDCP序列,有些序号分给了重传业务数据的包,PDCP实体作为接收方时需要记住哪些数据包自处理重传业务数据的RLC实体,哪些包来自处理初传业务数据的RLC实体。假设1-7这7个序号,1、2、4、5、7分配给了初传业务数据的5个包,3和6分配给了重传业务数据的2个包,RLC实体1处理初传业务数据,RLC实体2处理重传业务数据,当PDCP实体以及向上层传递了1、2、3、4、5这5个包后,当PDCP实体再收到7号包时,需要确定是不是向上传递7号包,如果6号包是初传业务数据包,那么需要等待6号包,如果6号包是重传业务数据包,则立即向上传递7号包。需要说明的是,如果收到7号包后发生了切换,即终端切换到新的小区,RLC实体会重置,即RLC实体中的缓存会被清空,这样RLC实体就没法准确告知PDCP实体6号包是初传业务数据的包还是重传业务数据的包,那么PDCP实体就将7号包缓存,等到6号包之后再传递7号包。
图7为本发明提供的数据传输的方法的另一处理场景示意图,如图7所示,在图6的基础上,一些预设粒度业务数据可以共用一个RLC实体,这种 情况下,RLC实体作为发送方收到PDCP实体传递的数据包后,需要在数据包头上增加PDCP标签,用于标识数据包来自于哪一个PDCP实体,以便于接收方的RLC实体作为收到业务数据包时,才能把根据数据包的PDCP标签将数据包发送给对应的接收方PDCP实体。
假设RAN网元的处理粒度为“流”,RAN网元接收到核心网用户面实体发送的数据后,会将数据分为多个流,以一个流为初传业务数据、另一个流为重传业务数据为例,每个初传业务数据流使用独立的PDCP实体和RLC实体,两个或多个重传业务数据流共用一个RLC实体,本例中以2个重传业务数据流共用RLC实体3为例。RLC实体3收到每个PDCP实体发送的重传业务数据包后,在重传业务数据包头中添加PDCP标签,用以标识数据包来自哪一个PDCP实体。
图8为本发明提供的数据传输的方法的另一处理场景示意图,如图8所示,在同一小区内,上述RAN网元生成多个子RB,也可以直接在PDCP层进行。
以初传业务数据和重传业务数据为例,这两种业务数据的Qos需求不同,具体地,由于TCP中使用窗口机制,TCP期望底层按序向上递交数据包,否则可能会触发快速重传,同时拥塞窗口减半,使链路吞吐量降低。但是对于TCP重传包,则要求越早递交越好,即收到业务数据包就会向上递交。可见重传业务数据的优先级高于初传业务数据的优先级。
参加图8,初传业务数据和重传业务数据分别采用单独的PDCP实体和RLC实体。
对于重传业务数据包,可以有如下一种方式或任意组合来保证降低传输时延:
1)MAC实体一旦收到重传业务数据包,在组织传输块(transport block,简称TB)传输时,会优先取重传业务数据包。
其中,TB传输是指MAC层从RLC层取数据,并将获取的数据组织成TB放到物理层去传输。
2)MAC实体优先使用短TTI的子帧传输重传业务数据包。
3)重传业务数据包在RLC实体不分段、只级联,以避免重传业务数据包的某个分段在RLC实体等待被重组。需要说明的是,由于不分段,所以接 收方RLC实体不需要利用多个RLC协议数据单元(Protocol Data Unit,简称PDU)拼装出一个RLC服务数据单元(Service Data Unit,简称SDU),因而这种方式不需要分配RLC序列。或者,
重传业务数据包在发送方RLC实体既做级联、也做分段,但是在接收方RLC实体没每收到一个RLC PDU,就会尝试拼成RLC SDU,如果拼成RLC SDU就发送给PDCP实体。如果RLC实体发现RLC PDU中某个分段不能拼成RLC SDU,就先把能拼出来的RLC SDU送交PDCP实体,而RLC PDU则继续在RLC队列中等待,等到下一个RLC PDU到来后,再尝试拼半装RLC SDU。这样可以缩短数据分段RLC SDU在接收端缓存中的等待时间。这个过程中,为了让接收方的RLC实体能识别RLC PDU的顺序,以便利用多个RLC PDU拼装出一个RLC SDU,所以这样可以缩短数据分段在缓存中的等待时间。这种方式需要每个RLC PDU分配一个RLC序列号。
4)如果识别出缓存中的数据包属于同一个重传业务数据流的多个TCP确认字符(Acknowledgement,简称ACK),RLC实体只传输最后一个ACK。
如果RLC实体有两个重传业务数据包,先传输距离初传时间最长的重传业务数据包;或者,将两个重传业务数据包中的数据与当前数据比较,先传输字节间隔较大的重传业务数据包;或者,将两个重传业务数据包与当前数据包比较,先传输包数量间隔较大的重传业务数据包,需要说明的是,TCP将数据包编号传输,初传数据包号是单调递增的,重传数据包号不变,所以与当前正在进行初传的数据包的包号相比,重传数据包的包号肯定排在前面。
需要说明的是,图6-图8仅为示例,实现时,每个子RB可以对应一PDCP实体、一个RLC实体(或两个),MAC层对子RB对应逻辑信道中的数据进行优先级调度和复用/解复用处理。
RAN网元生成多个子RB后,可以给每个子RB配置不同的协议层参数、逻辑信道参数等。具体地,PDCP层参数可以包括下述至少一项或其任意组合:丢弃定时器(discard Timer)、头压缩、重排序定时器、序列号(Serial Number,简称SN)长度等。RLC参数可以包括下述至少一项或其任意组合:上下行RLC模式、轮询(Poll)的重传定时器、状态限制(t-Status Prohibit)定时器、Poll调查(PDU)、Poll字节(Byte)、最大重传次数、重排序定时器、SN长度等。逻辑信道参数可以包括下述至少一项或其任意组合:优先 级(priority)、名义速率(prioritised BitRate)、桶大小(bucket Size Duration)、归属逻辑信道组(logical Channel Group)等。
在上述实施例的基础上,为了节约资源,RAN网元可以对子RB进行释放:可选地,RAN网元在第一子RB上的业务数据都释放后,释放该第一子RB,第一子RB可以指任一子RB;或者,RAN网元接收CN CP发送的业务数据释放通知后,释放业务数据,并释放子RB,具体地,CN CP可以具体指示RAN释放第一子RB上的业务数据,以及释放第一子RB,第一子RB可以指任一子RB;或者,RAN网元监测到第一Qos需求参数对应的子RB在预设时间段内未接收到业务数据时,释放该第一Qos需求参数对应的子RB,其中第一Qos需求参数可以指任一套Qos需求参数。当然,并不以这几种方案为限。
3、RAN网元根据上述预设粒度业务数据所属分类传输该预设粒度业务数据,可以包括:RAN网元根据上述预设粒度业务数据所属分类对应的Qos需求参数,选择各协议层所采用的处理模板,其中处理模板包括对应的Qos需求参数。进而,RAN网元根据上述各协议层所采用的处理模板传输该预设粒度业务数据。
具体地,这种实现方式中,同一RB的不同协议层可以预设好对应的处理模板,当然,协议层与处理模板的映射关系可以动态变化,并不一直固定。每个处理模板对应不同的Qos需求参数。
可以由各协议层自己选择处理模板,也可以由RAN网元中一个预设模块统一选择处理模板:
(1)RAN网元将上述预设粒度业务数据对应的Qos需求参数在每一协议层进行翻译和修正,并通知到下一协议层,由各协议层根据获得的Qos需求参数自行进行选择。
例如,PDCP层可以选择预设粒度业务数据对应的Qos需求参数所对应的PDCP层处理模板,并向下一层RLC层提供Qos需求参数的相关信息,以便于RLC层选择适合自己的处理模板。
(2)RAN网元根据上述预设粒度业务数据对应的Qos需求参数为每一协议层选择对应的处理模板,即统一选择好各协议层的处理模板。
每个协议层的处理模板实体配置唯一标识(id),在接收端协议层实体 根据id来接收、恢复和向上投递。例如RLC实体收到下层投递来的业务数据包,根据处理模块id来选择具体的RLC层的处理模板进行处理。
可以在PDCP层、RLC层的处理基础上,由MAC层进行业务数据的优化调度,例如进行不同优先级的调度等,在此不作限制。
上述实施例只是以LTE的L2协议栈进行举例,可以适用于其他协议栈形态,比如没有RLC层,或RLC层部分功能迁移到MAC或PDCP层等,与RAN网元类似的,终端也会根据业务数据的不同Qos需求,更细粒度的对业务数据进行Qos处理。
图9为本发明提供的数据传输的方法实施例四的流程示意图,如图8所示,该方法包括:
S901、终端获取待传输预设粒度上行业务数据。
可选地,终端收到上行业务数据后,可以根据上行业务数据所在的分片(slice)映射出那些数据流可以在slice传输,再根据Qos需求确定传哪些包。
S902、终端获取上述待传输预设粒度上行业务数据对应的Qos需求参数。
可选地,终端根据上述待传输预设粒度上行业务数据、以及预设Qos映射关系,获取上述待传输预设粒度上行业务数据对应的Qos需求参数。
可选地,终端可以接收CN CP,或者,RAN网元发送的预设Qos映射关系,在此不作限制。
上述预设Qos映射关系一般由CN CP生成,如果是由RAN网元向终端发送上述预设Qos映射关系,可以是RAN网元先接收CN CP发送的预设Qos映射关系,再由RAN网元向终端转发上述预设Qos映射关系。
如果CN CP将上述预设Qos映射关系直接发送给终端,可以是核心网网元通过非接入层(Non-Access Stratum,简称NAS)消息来向终端发送上述预设Qos映射关系。如果是由RAN网元向终端转发上述预设Qos映射关系,则可以是RAN网元通过接入层(Access Stratum,简称AS)消息向终端发送上述预设Qos映射关系。
具体地,Qos需求参数可以参照前述实施例,在此不再赘述。
S903、终端根据上述待传输预设粒度上行业务数据对应的Qos需求参数,传输上述待传输预设粒度上行业务数据。
可选地,预设粒度可以是:flow,和/或,RB。具体可以由CN CP向终 端指示预设粒度,也可以预先配置好,在此不作限制。
S904、RAN网元将接收到的上述待传输预设粒度上行业务数据转发给CN UP。
本实施例中,终端获取上述待传输预设粒度上行业务数据对应的Qos需求参数,并根据上述待传输预设粒度上行业务数据对应的Qos需求参数传输待传输预设粒度上行业务数据,实现了对不同Qos需求参数对应的待传输预设粒度上行业务数据进行不同的数据处理,以满足不同预设粒度上行业务数据的Qos需求。
可选地,终端根据上述待传输预设粒度上行业务数据、以及预设Qos映射关系,获取上述待传输预设粒度上行业务数据对应的Qos需求参数之后,如果识别出缓存中有多个TCP ACK,则删掉前面的,只保留最后一个ACK。上传数据时,如果发现TB空间有空余,就传上述“删掉的TCP ACK”,如果TB空间没有空余,就不传了。
网络侧可以配置Qos门限,终端上报缓存状态报告(Buffer state report,简称BSR)时,可以指出高于Qos门限的数据包的大小。
例如,在BSR中指出重传数据包的大小。
进一步地,与前述RAN网元侧实施例类似地,上述预设Qos映射关系可以有多种形式,针对不同的预设Qos映射关系,终端获取业务数据Qos需求的方法也不同。
一种实施方式中,上述预设Qos映射关系为:预设特征信息与Qos需求参数的映射关系。
终端根据待传输预设粒度上行业务数据、以及预设服务质量Qos映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数,可以为:终端识别所述待传输预设粒度上行业务数据的特征信息;并根据所述待传输预设粒度上行业务数据的特征信息、以及所述预设特征信息与Qos需求参数的映射关系,确定所述待传输预设粒度上行业务数据对应的Qos需求参数。即终端获取到预设特征信息与Qos需求参数的映射关系后,会对待传输预设粒度上行业务数据的特征信息进行识别。识别到待传输预设粒度上行业务数据的特征信息后,终端会根据预设特征信息与Qos需求参数的映射关系,确定上述待传输预设粒度上行业务数据对应的Qos需求参数。
可选地,上述特征信息可以包括:下述一项或其任意组合:协议层的端口号、特征字、关联特征、数据流行为。这些特征信息的具体解释可以参见前述实施例,在此不再赘述。
又一种实施例中,上述预设Qos映射关系为:预设Qos标识与Qos需求参数的映射关系。
终端根据待传输预设粒度上行业务数据、以及预设服务质量Qos映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数,可以是:终端获取所述待传输预设粒度上行业务数据中的Qos标识,进而终端根据待传输预设粒度上行业务数据中的Qos标识、以及预设Qos标识与Qos需求参数的映射关系,获取上述待传输预设粒度上行业务数据对应的Qos需求参数。
可选地,终端可以接收应用层服务器发送的业务数据的标识配置信息,根据业务数据的标识配置信息确定待传输预设粒度上行业务数据的Qos标识。
Qos标识可以携带在业务数据包的协议层头部,在此不作限制。
进而终端会根据待传输预设粒度上行业务数据中的Qos标识、以及预设Qos标识与Qos需求参数的映射关系,确定上述待传输预设粒度上行业务数据的Qos需求。
可选地,终端还可以接收RAN网元或者CN CP发送的上述Qos增强属性信息。
可选地,上述Qos增强属性信息包括下述任一项或其任意组合:时变属性、分类属性、粒度属性。这些属性的具体解释可以参照前述实施例,在此不在赘述。
与前述RAN侧网元类似的,终端可以根据上述Qos增强属性信息的具体内容,决定是否根据上述待传输预设粒度上行业务数据对应的Qos需求参数,对上述待传输预设粒度上行业务数据进行Qos处理。
也就是说,并不一定所有的业务都要按照前述方法细粒度的确定Qos需求参数,可以根据具体地属性来确定是否有必要这样做,即在满足一定条件的情况下按照前述方法来获取业务数据对应的Qos需求参数。
可选地,在上述Qos增强属性信息包括时变属性,且时变属性标识该业务数据具有时变性,即业务过程中业务数据的状态随时间变化、且Qos需求 随业务数据的状态变化,那么终端就根据上述待传输预设粒度上行业务数据、以及预设Qos映射关系,获取上述待传输预设粒度上行业务数据对应的Qos需求参数。
可选地,在上述Qos增强属性信息包括分类属性,且分类属性标识上述业务数据需要进行Qos需求分类,那么终端就根据上述待传输预设粒度上行业务数据、以及预设Qos映射关系,获取上述待传输预设粒度上行业务数据对应的Qos需求参数。
可选地,在上述Qos增强属性信息包括粒度属性,且粒度属性标识处理粒度为“per bearer”或者“flow”时,终端就根据上述待传输预设粒度上行业务数据、以及预设Qos映射关系,获取上述待传输预设粒度上行业务数据对应的Qos需求参数。
可选地,也可以CN CP也可以根据上述Qos增强属性信息配置不同的Qos需求参数。
Qos增强属性信息包括时变属性时,预设Qos映射关系包括:业务数据的状态与Qos需求参数的映射关系。终端就根据上述待传输预设粒度上行业务数据、以及预设Qos映射关系,获取上述待传输预设粒度上行业务数据对应的Qos需求参数,可以为:终端获取上述待传输预设粒度上行业务数据的当前业务状态;终端根据上述业务数据的状态与Qos需求参数的映射关系,确定上述待传输预设粒度上行业务数据的当前业务状态对应的Qos需求参数。
可以由应用层服务器向终端指示业务状态发生了变化。
如果Qos增强属性信息中包括分类属性,则终端可以根据预设机制获取上述待传输预设粒度上行业务数据不同分类部分对应的不同Qos需求参数,以便进一步进行Qos处理。
可选地,预设Qos映射关系可以包括:分类信息标识与Qos需求参数的映射关系。
终端就根据上述待传输预设粒度上行业务数据、以及预设Qos映射关系,获取上述待传输预设粒度上行业务数据对应的Qos需求参数,可以为:终端获取上述待传输预设粒度上行业务数据的分类信息标识,再根据分类信息标识与Qos需求参数的映射关系,获取上述待传输预设粒度上行业务数据中各 分类部分分别对应的Qos需求参数。
进一步地,如果上述Qos增强属性信息中包括粒度属性,预设Qos映射关系可以包括:过滤模板和Qos需求参数的映射关系。
终端就根据上述待传输预设粒度上行业务数据、以及预设Qos映射关系,获取上述待传输预设粒度上行业务数据对应的Qos需求参数,可以为:终端根据所选择的过滤模板将上述预设粒度业务数据划分为至少一个过滤模板对应粒度的业务数据,并根据过滤模板和Qos需求参数的映射关系,获取上述至少一个过滤模板对应粒度的业务数据分别对应的Qos需求参数。
需要说明的是,上述Qos增强属性都是可以动态变化的。
关于上述Qos增强属性信息对应的实施例均可以参照前述RAN网元侧实施例,在此不再赘述。
进一步地,终端对不同上行业务数据进行区分化Qos处理,可以有多种方法,举例说明可以包括以下几种,这几种方案可以根据具体处理需求结合使用,也可以独立使用,在此不作限制。
1、上述终端根据上述待传输预设粒度上行业务数据对应的Qos需求参数,传输上述待传输预设粒度上行业务数据,可以是:终端根据上述待传输预设粒度上行业务数据对应的Qos需求参数,调整该待传输预设粒度上行业务数据对应的逻辑信道的调度策略,采用调整后的逻辑信道发送上述待传输预设粒度上行业务数据。具体地,可以是传输给RAN网元。
具体实现过程中,如果终端本来有多个逻辑信道组(Logic channel group,简称LCG),那么可以确定其中一个逻辑信道进行调度策略的调整,例如提高优先级、提高传输速率等,在此不作限制,根据上述待传输预设粒度上行业务数据对应的Qos需求参数实现调整即可。
如果终端开始只有一个LCG,那么终端需要向RAN网元发送修改指示消息,例如通过修改指示消息指示该逻辑信道需要更高优先级的LCG的BSR,或者指示该逻辑信道需要更高的传输速率等,在此不作限制,根据上述待传输预设粒度上行业务数据对应的Qos需求指示即可。RAN网元收到修改指示消息后,知道LCG的Qos需求发生了变化,可以重新进行逻辑信道的配置,例如增加或删除逻辑信道,或者修改逻辑信道配置参数等,在此不作具体限定。
2、上述终端根据上述待传输预设粒度上行业务数据对应的Qos需求参数,传输上述待传输预设粒度上行业务数据,可以是:终端根据上述待传输预设粒度上行业务数据对应的Qos需求参数、以及预设Qos需求参数与子RB之间的映射关系,将上述待传输预设粒度上行业务数据映射到对应的子RB上进行传输。即具体将上行业务数据映射到对应的子RB上传输给RAN网元。
子RB与上述逻辑信道一一对应。
在此之前,终端可以接收RAN网元发送的Qos需求参数与子RB之间的映射关系。具体地,RAN网元可以为终端配置不同Qos需求参数与子RB之间的映射关系,并发送给终端。
终端按照预设粒度获取不同的待传输预设粒度上行业务数据后,根据不同待传输预设粒度上行业务数据对应的Qos需求参数,将待传输预设粒度上行业务数据映射到对应的子RB上进行传输。
可选地,终端也可以将具有相同或相似Qos需求参数的多个待传输预设粒度上行业务数据映射到同一子RB中进行传输。相似Qos需求参数可以是Qos需求参数值的差值在预设范围内的Qos需求参数。
具体实现时,预设Qos需求参数与子RB之间的映射关系可以为:预设类型的Qos需求参数与子RB的映射关系,即RAN网元可以将Qos需求参数进行分类,并配置预设类型的Qos需求参数与子RB的映射关系,进而终端根据上述待传输预设粒度上行业务数据的Qos需求参数确定该待传输预设粒度上行业务数据的Qos需求参数所属的类型,并根据预设类型的Qos需求参数与子RB的映射关系,将上述待传输预设粒度上行业务数据映射到对应的子RB上进行传输。
例如,可以采用服务质量分类标识(QoS Classification Identifier,简称QCI)来标识预设类型的Qos需求参数,即将某一类或某几类QCI对应的待传输预设粒度上行业务数据映射到同一子RB。
具体实现过程中,如果终端获取到待传输预设粒度上行业务数据后,发现预设Qos需求参数与子RB之间的映射关系中没有待传输预设粒度上行业务数据的Qos需求参数所对应的子RB,那么终端可以向RAN网元发送业务数据分类消息,其中,该业务数据分类消息包括下述一项或任意组合:上述待传输预设粒度上行业务数据的Qos需求参数、上述待传输预设粒度上行业 务数据的数据流标识、建立子RB的指示信息。RAN网元收到该业务数据分类消息后,建立一个新的子RB,并配置该新的子RB与Qos需求参数的映射关系,进而将新的子RB与Qos需求参数的映射关系发送给终端,以便于终端将上述待传输预设粒度上行业务数据映射到对应的子RB。
可选地,可以不在上述业务数据分类消息中携带“建立子RB的指示信息”,而专门向RAN网元再发送一个子RB建立请求消息。那么RAN网元在收到上述业务数据分类消息和子RB建立请求消息后,建立一个新的子RB,并配置该新的子RB与Qos需求参数的映射关系,进而将新的子RB与Qos需求参数的映射关系发送给终端。
在上述实施例的基础上,终端可以在监测到第一Qos需求参数对应的子RB在预设时间段内没有数据传输时,请求RAN网元释放该第一Qos需求参数对应的子RB,其中第一Qos需求参数可以指任一套Qos需求参数。或者,终端在第一子RB上的业务数据都释放后,请求RAN网元释放该第一子RB,第一子RB可以指任一子RB。
可选地,终端可以通过控制面信令通知RAN网元释放子RB,例如通过RRC消息或者通过媒体接入层控制信息(Medium Access Control control element,简称MAC CE)的信元通知RAN网元释放子RB。
可选地,终端还可以通过用户面通知AN网元释放子RB,例如可以在用户面数据包中携带一个结束标记(end marker)指示RAN网元释放子RB以及子RB上的业务数据。
进一步地,对于上行业务数据,子RB的配置有两种方式,一种是静态配置,即RAN侧进行配置,RAN通过CN CP得知每个预设粒度业务数据的Qos需求参数,参考该子RB包含的所有预设粒度业务数据的Qos需求参数对该子RB进行参数配置。特殊的,分类子流的Qos需求参数,可以是通过终端上报的数据包头映射信息和CN CP通知的分类数据流Qos需求参数结合得到。
一种是动态配置,终端根据预设粒度业务数据和子RB的映射关系,动态生成预设粒度业务数据的Qos需求参数。动态配置的规则可由网络侧生成并通知到终端。例如,可以在网络侧初始配置子RB参数的基础上进行更新,例如对于GBR业务,子RB的PBR的参数配置可以是其包含的所有分类数据子流的GBR之和。对于non PBR业务,网络侧可以配置统一的PBR生成规则(例如, 可以根据QCI计算生成PBR),终端计算出每个预设粒度业务数据的PBR,则子RB的PBR的参数配置可以是其包含的所有预设粒度业务数据的PBR之和。
终端基于上行子RB的参数配置进行加密、分段、重组、调度和复用等其中一项或多项的数据处理程序。
3、上述终端根据上述待传输预设粒度上行业务数据对应的Qos需求参数,传输上述待传输预设粒度上行业务数据,可以是:终端采用各协议层对应的预设处理模板传输上述待传输预设粒度上行业务数据。具体可以是发送给RAN网元。
其中,不同的处理模板对应不同的Qos需求参数,RAN可以预先根据终端的签约信息、或者不同的Qos需求参数信息配置不同协议层对应的处理模板,当然,每个协议层可以对应至少一个处理模板,例如配置PDCP层对应的至少一个处理模板(每个处理模板对应一个PDCP实体),和/或,配置RLC层对应的至少一个处理模板(每个处理模板对应一个RLC实体),在此不作限制。
在此之前,终端接收RAN网元发送的预设处理模板和各协议层的对应关系,其中,每个处理模板可以由不同的模板标识进行区分。具体地每个处理模板的内容可以预先配置在终端中,也可以由RAN网元动态进行通知,在此不作限制。
当然,如果终端获取上述待传输预设粒度上行业务数据的Qos需求后,发现当前协议层的处理模板所对应的Qos需求参数与上述待传输预设粒度上行业务数据的Qos需求并不匹配,终端可以向RAN网元发送处理模板建立请求,以请求RAN网元重新配置各协议层对应的处理模板,RAN网元可以根据处理模板建立请求建立新的处理模板,例如建立新的PDCP实体,即PDCP层对应的新的处理模板;和/或,建立新的RLC实体,即RLC层对应的新的处理模板。RAN建立完成后会重新通知终端,以便于终端采用各协议层对应的预设处理模板对上述待传输预设粒度上行业务数据进行Qos处理。
终端还可以向RAN网元发送处理模板删除请求,该处理模板删除请求中可以携带待删除处理模板的标识,以请求RAN网元将当前配置好的一个或多个待删除处理模板删除。可选地,终端还可以在上述处理模板删除请求中携带:请求删除的原因参数等。
例如:终端可以请求RAN网元删除预设时间段内未使用的处理模板,在此不作限制。
其中,业务数据的数据包头中携带PDCP实体的标识和或RLC实体的标识。
在上述实施例的基础上,终端可以释放某些业务数据子流,例如终端检测在某一分类数据子流没有数据包的时间超过预设时间段,则终端可以通知RAN释放该分类数据子流。可以通过控制面信令的方式通知RAN,通过RRC消息或者MAC CE的信元通知RAN释放该分类数据子流。还可以通过用户面的方式通知RAN,在用户面数据包中携带一个end marker的指示信息来通知RAN该分流数据子流的终止。
图10为本发明提供的数据传输的装置实施例一的结构示意图,该装置可以集成于RAN网元或RAN控制器中,如图10所示,该装置包括:获取模块110、确定模块111和传输模块112,其中:
获取模块110,用于获取预设粒度业务数据。
确定模块111,用于获取所述预设粒度业务数据对应的Qos需求参数;将所述预设粒度业务数据进行Qos需求分类,并根据所述预设粒度业务数据对应的Qos需求参数确定所述预设粒度业务数据所属分类对应的Qos需求参数。
传输模块112,用于根据所述预设粒度业务数据所属分类传输所述预设粒度业务数据。
本实施例中,RAN网元获取预设粒度业务数据,进一步地RAN网元获取上述预设粒度业务数据的Qos需求参数,并对预设粒度业务数据进行Qos需求分类、确定预设粒度业务数据所属分类对应的Qos需求参数,进而RAN网元根据所述预设粒度业务数据所属分类传输所述预设粒度业务数据,实现了RAN网元可以获知不同预设粒度业务数据对应的不同Qos需求参数,在收到预设粒度业务数据后,根据所述预设粒度业务数据所属分类分别传输所述预设粒度业务数据,以满足不同预设粒度业务数据的Qos需求。
确定模块111,具体用于根据所述预设粒度业务数据的属性信息、以及预设服务质量Qos映射关系,获取所述预设粒度业务数据对应的Qos需求参 数。
其中,所述预设粒度业务数据的属性信息包括下述任一项或其任意组合:预设特征信息、预设标识、预设通道标识。
可选地,所述预设服务质量Qos映射关系为:预设特征信息与Qos需求的映射关系;确定模块111,具体用于识别所述预设粒度业务数据中的特性信息;根据所述预设粒度业务数据中的特性信息、以及预设特征信息与Qos需求参数的映射关系,获取所述预设粒度业务数据对应的Qos需求参数。
可选地,所述特征信息包括下述一项或其任意组合:协议层的端口号、特征字、关联特征、数据流行为;其中,所述关联特征指联合识别的多个特征字。
可选地,所述预设服务质量Qos映射关系为:预设Qos标识与Qos需求参数的映射关系;确定模块111,具体用于根据预设规则获取所述预设粒度业务数据中的Qos标识;根据所述预设粒度业务数据中的Qos标识、以及所述预设Qos标识与Qos需求参数的映射关系,获取所述预设粒度业务数据对应的Qos需求参数。
确定模块111用于根据预设规则获取所述预设粒度业务数据中的Qos标识,具体为:根据预设规则,在所述预设粒度业务数据的数据包头中获取Qos标识。
可选地,所述预设服务质量Qos映射关系为:预设通道标识与Qos需求参数的映射关系;确定模块111,具体用于确定接收所述预设粒度业务数据的通道;根据所述接收所述预设粒度业务数据的通道、以及预设通道标识与Qos需求参数的映射关系,获取所述预设粒度业务数据对应的Qos需求参数。
可选地,所述Qos需求参数包括下述至少一项或其任意组合:流聚合最大比特速率AMBR、无线承载AMBR、终端AMBR、优先级、时间延迟、丢包率、切换特性、时变特性、分配保留优先级ARP。
图11为本发明提供的数据传输的装置实施例二的结构示意图,如图11所示,在图10的基础上,该装置还包括:接收模块113,用于接收获取Qos增强属性信息。
确定模块111,具体用于根据所述预设粒度业务数据的Qos增强属性信息、以及预设Qos映射关系,获取所述预设粒度业务数据对应的Qos需求参 数。
可选地,所述Qos增强属性信息包括下述任一项或其任意组合:时变属性、分类属性、粒度属性;
其中,所述时变属性用于标识业务过程中业务数据的状态是否随时间变化、且Qos需求参数是否随业务数据的状态变化;所述分类属性用于标识业务数据是否根据Qos需求参数分类;所述粒度属性用于标识Qos的处理粒度。
可选地,所述Qos增强属性信息包括时变属性时,所述预设Qos映射关系包括:业务数据的状态与Qos需求参数的映射关系;
确定模块111,具体用于获取所述预设粒度业务数据的当前业务状态;根据所述预设粒度业务数据的当前业务状态、以及所述业务数据的状态与Qos需求参数的映射关系,确定所述预设粒度业务数据的当前业务状态对应的Qos需求参数。
可选地,接收模块113,还用于根据所述业务状态变化通知,确定所述预设粒度业务数据的当前业务状态。
传输模块112,具体用于将所述预设粒度业务数据所属分类对应的Qos需求参数作为介质访问控制MAC层的调度输入,通过MAC层调度传输所述预设粒度业务数据。
图12为本发明提供的数据传输的装置实施例三的结构示意图,如图12所示,在图10的基础上,该装置还包括:生成模块114,用于生成多个子无线承载,每个子无线承载对应不同的Qos需求参数。
传输模块112,具体用于根据所述预设粒度业务数据所属分类对应的Qos需求参数、以及子无线承载与Qos需求参数的映射关系,选择对应的子无线承载传输所述预设粒度业务数据。
可选地,传输模块112,具体用于根据所述预设粒度业务数据所属分类对应的Qos需求参数,选择各协议层所采用的处理模板,其中,不同的所述处理模板对应的Qos需求参数不同;根据所述各协议层所采用的处理模板传输所述预设粒度业务数据。
可选地,获取模块110,还用于获取所述预设Qos映射关系。
可选地,传输模块112,还用于向终端发送所述预设Qos映射关系。
图13为本发明提供的数据传输的装置实施例四的结构示意图,该装置可 以集成于终端中,该装置包括:获取模块131、确定模块132和传输模块133,其中:
获取模块131,用于获取待传输预设粒度上行业务数据。
确定模块132,用于获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
传输模块133,用于根据所述待传输预设粒度上行业务数据对应的Qos需求参数,传输所述待传输预设粒度上行业务数据。
可选地,确定模块132,具体用于根据所述待传输预设粒度上行业务数据、以及预设服务质量Qos映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
可选地,所述预设服务质量Qos映射关系为:预设特征信息与Qos需求参数的映射关系;确定模块132,具体用于识别所述待传输预设粒度上行业务数据的特征信息;根据所述待传输预设粒度上行业务数据的特征信息、以及所述预设特征信息与Qos需求参数的映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
可选地,所述特征信息包括下述一项或其任意组合:协议层的端口号、特征字、关联特征、数据流行为;其中,所述关联特征指联合识别的多个特征字。
可选地,所述预设Qos映射关系为:预设Qos标识与Qos需求参数的映射关系;
确定模块132,具体用于获取所述待传输预设粒度上行业务数据中的Qos标识;根据所述待传输预设粒度上行业务数据中的Qos标识、以及所述预设Qos标识与Qos需求参数的映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
可选地,所述Qos需求包括下述至少一项或其任意组合:流聚合最大比特速率AMBR、无线承载AMBR、终端AMBR、优先级、时间延迟、丢包率、切换特性、时变特性、分配保留优先级ARP。
图14为本发明提供的数据传输的装置实施例五的结构示意图,在图13的基础上,该装置还可以包括:第一接收模块134,用于接收核心网控制功能实体或RAN网元发送的Qos增强属性信息。
确定模块132,具体用于根据所述待传输预设粒度上行业务数据对应的Qos增强属性信息、以及预设Qos映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
可选地,所述Qos增强属性信息包括下述任一项或其任意组合:时变属性、分类属性、粒度属性;
其中,所述时变属性用于标识业务过程中业务数据的状态是否随时间变化、且Qos需求参数是否随业务数据的状态变化;所述分类属性用于标识业务数据是否根据Qos需求参数分类;所述粒度属性用于标识Qos的处理粒度。
可选地,传输模块133,具体用于根据所述待传输预设粒度上行业务数据对应的Qos需求参数,调整所述待传输预设粒度上行业务数据对应的逻辑信道的调度策略,采用调整后的逻辑信道向RAN网元传输所述待传输预设粒度上行业务数据。
可选地,传输模块133,具体用于根据所述待传输预设粒度上行业务数据对应的Qos需求参数、以及预设Qos需求参数与子RB之间的映射关系,将所述待传输预设粒度上行业务数据映射到对应的子无线承载RB上传输。
图15为本发明提供的数据传输的装置实施例六的结构示意图,在图13的基础上,该装置还可以包括:第二接收模块135,用于接收所述RAN网元发送的所述预设Qos需求与子RB之间的映射关系。
传输模块133,具体用于采用各协议层对应的预设处理模板对所述待传输预设粒度上行业务数据进行Qos处理,并将处理后的所述待传输预设粒度上行业务数据发送给RAN网元。
图16为本发明提供的数据传输的装置实施例七的结构示意图,该装置可以集成于核心网网元,如图16所示,该装置包括:生成模块161和发送模块162,其中:
生成模块161,用于生成服务质量Qos映射关系,所述Qos映射关系用于表示预设粒度业务数据与Qos需求参数的映射关系。
发送模块162,将所述Qos映射关系发送给无线接入网网元。
可选地,发送模块162还用于将所述Qos映射关系发送给无线接入网网元。
可选地,所述Qos映射关系包括:业务数据特征信息与Qos需求的映射 关系。
所述业务数据特征信息包括下述一项或其任意组合:协议层的端口号、特征字、关联特征、数据流行为;其中,所述关联特征指联合识别的多个特征字。
可选地,所述Qos映射关系包括:所述Qos映射关系包括:业务数据中Qos标识与Qos需求参数的映射关系。
可选地,所述Qos映射关系包括:预设通道标识与Qos需求参数的映射关系。
可选地,发送模块162,还用于向核心网用户面功能实体发送至少一套Qos需求参数。
上述装置用于执行前述方法实施例,其实现原理和技术效果类似。
图17为本发明提供的无线接入网网元实施例一的结构示意图,如图16所示,该RAN网元包括:存储器171、处理器172、接收器173以及发送器174。
存储器171、处理器172、接收器173、发送器174通过总线175连接。
存储器171用于存储指令,处理器172用于调用存储器171中的指令执行前述方法实施例。具体地:
处理器172,用于获取预设粒度业务数据;获取所述预设粒度业务数据对应的Qos需求参数;将所述预设粒度业务数据进行Qos需求分类,并根据所述预设粒度业务数据对应的Qos需求参数确定所述预设粒度业务数据所属分类对应的Qos需求参数;根据所述预设粒度业务数据所属分类传输所述预设粒度业务数据。
处理器172,具体用于根据所述预设粒度业务数据的属性信息、以及预设服务质量Qos映射关系,获取所述预设粒度业务数据对应的Qos需求参数。
其中,所述预设粒度业务数据的属性信息包括下述任一项或其任意组合:预设特征信息、预设标识、预设通道标识。
可选地,所述预设服务质量Qos映射关系为:预设特征信息与Qos需求的映射关系;
处理器172,具体用于识别所述预设粒度业务数据中的特性信息;根据所述预设粒度业务数据中的特性信息、以及预设特征信息与Qos需求参数的 映射关系,获取所述预设粒度业务数据对应的Qos需求参数。
其中,所述特征信息包括下述一项或其任意组合:协议层的端口号、特征字、关联特征、数据流行为;其中,所述关联特征指联合识别的多个特征字。
可选地,所述预设服务质量Qos映射关系为:预设Qos标识与Qos需求参数的映射关系;
处理器172,具体用于根据预设规则获取所述预设粒度业务数据中的Qos标识;根据所述预设粒度业务数据中的Qos标识、以及所述预设Qos标识与Qos需求参数的映射关系,获取所述预设粒度业务数据对应的Qos需求参数。
可选地,处理器172,用于根据预设规则获取所述预设粒度业务数据中的Qos标识,具体为:根据预设规则,在所述预设粒度业务数据的数据包头中获取Qos标识。
可选地,所述预设服务质量Qos映射关系为:预设通道标识与Qos需求参数的映射关系;处理器172具体用于确定接收所述预设粒度业务数据的通道;根据所述接收所述预设粒度业务数据的通道、以及预设通道标识与Qos需求参数的映射关系,获取所述预设粒度业务数据对应的Qos需求参数。
可选地,所述Qos需求包括下述至少一项或其任意组合:流聚合最大比特速率AMBR、无线承载AMBR、终端AMBR、优先级、时间延迟、丢包率、切换特性、时变特性、分配保留优先级ARP。
可选地,所述接收器173,用于接收获取Qos增强属性信息;
所述处理器172具体用于根据所述预设粒度业务数据的Qos增强属性信息、以及预设Qos映射关系,获取所述预设粒度业务数据对应的Qos需求参数。
可选地,所述Qos增强属性信息包括下述任一项或其任意组合:时变属性、分类属性、粒度属性;
其中,所述时变属性用于标识业务过程中业务数据的状态是否随时间变化、且Qos需求参数是否随业务数据的状态变化;所述分类属性用于标识业务数据是否根据Qos需求参数分类;所述粒度属性用于标识Qos的处理粒度。
可选地,所述Qos增强属性信息包括时变属性时,所述预设Qos映射关系包括:业务数据的状态与Qos需求参数的映射关系;处理器172,具体用 于获取所述预设粒度业务数据的当前业务状态;根据所述预设粒度业务数据的当前业务状态、以及所述业务数据的状态与Qos需求参数的映射关系,确定所述预设粒度业务数据的当前业务状态对应的Qos需求参数。
可选地,接收器173还用于接收应用层服务器发送的业务状态变化通知;处理器172,还用于根据所述业务状态变化通知,确定所述预设粒度业务数据的当前业务状态。
可选地,处理器172,具体用于将所述预设粒度业务数据所属分类对应的Qos需求参数作为介质访问控制MAC层的调度输入,通过MAC层调度传输所述预设粒度业务数据。
可选地,处理器172,还用于生成多个子无线承载,每个子无线承载对应不同的Qos需求参数。且根据所述预设粒度业务数据所属分类对应的Qos需求参数、以及子无线承载与Qos需求参数的映射关系,选择对应的子无线承载传输所述预设粒度业务数据。
可选地,处理器172,具体用于根据所述预设粒度业务数据所属分类对应的Qos需求参数,选择各协议层所采用的处理模板,其中,不同的所述处理模板对应的Qos需求参数不同;根据所述各协议层所采用的处理模板传输所述预设粒度业务数据。
可选地,处理器172,还用于获取所述预设Qos映射关系。
可选地,发送器174,用于向终端发送所述预设Qos映射关系。
图18为本发明提供的终端实施例一的结构示意图,如图18所示,该终端包括:存储器181、处理器182、接收器183以及发送器184。
存储器181、处理器182、接收器183、发送器184通过总线185连接。
存储器181用于存储指令,处理器182用于调用存储器181中的指令执行前述方法实施例。具体地:
处理器182,用于获取待传输预设粒度上行业务数据;获取所述待传输预设粒度上行业务数据对应的Qos需求参数;根据所述待传输预设粒度上行业务数据对应的Qos需求参数,传输所述待传输预设粒度上行业务数据。
可选地,处理器182,具体用于根据所述待传输预设粒度上行业务数据、以及预设服务质量Qos映射关系,获取所述待传输预设粒度上行业务数据对 应的Qos需求参数。
可选地,所述预设服务质量Qos映射关系为:预设特征信息与Qos需求参数的映射关系;处理器182,具体用于识别所述待传输预设粒度上行业务数据的特征信息;根据所述待传输预设粒度上行业务数据的特征信息、以及所述预设特征信息与Qos需求参数的映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
可选地,所述特征信息包括下述一项或其任意组合:协议层的端口号、特征字、关联特征、数据流行为;其中,所述关联特征指联合识别的多个特征字。
可选地,所述预设Qos映射关系为:预设Qos标识与Qos需求参数的映射关系;处理器182,具体用于获取所述待传输预设粒度上行业务数据中的Qos标识;根据所述待传输预设粒度上行业务数据中的Qos标识、以及所述预设Qos标识与Qos需求参数的映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
进一步地,所述Qos需求参数包括下述至少一项或其任意组合:流聚合最大比特速率AMBR、无线承载AMBR、终端AMBR、优先级、时间延迟、丢包率、切换特性、时变特性、分配保留优先级ARP。
可选地,接收器183,用于接收核心网控制功能实体或RAN网元发送的Qos增强属性信息;处理器182,具体用于根据所述待传输预设粒度上行业务数据对应的Qos增强属性信息、以及预设Qos映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
可选地,所述Qos增强属性信息包括下述任一项或其任意组合:时变属性、分类属性、粒度属性;
其中,所述时变属性用于标识业务过程中业务数据的状态是否随时间变化、且Qos需求参数是否随业务数据的状态变化;所述分类属性用于标识业务数据是否根据Qos需求参数分类;所述粒度属性用于标识Qos的处理粒度。
可选地,处理器182,根据所述待传输预设粒度上行业务数据对应的Qos需求参数,调整所述待传输预设粒度上行业务数据对应的逻辑信道的调度策略,采用调整后的逻辑信道向RAN网元传输所述待传输预设粒度上行业务数据。
可选地,处理器182,具体用于根据所述待传输预设粒度上行业务数据对应的Qos需求参数、以及预设Qos需求参数与子RB之间的映射关系,将所述待传输预设粒度上行业务数据映射到对应的子无线承载RB上传输。
可选地,接收器183,用于接收所述RAN网元发送的所述预设Qos需求与子RB之间的映射关系。
可选地,处理器182,具体用于采用各协议层对应的预设处理模板对所述待传输预设粒度上行业务数据进行Qos处理,并将处理后的所述待传输预设粒度上行业务数据发送给RAN网元。
图19为本发明提供的核心网网元实施例一的结构示意图,如图19所示,该终端包括:存储器191、处理器192、接收器193以及发送器194。
存储器191、处理器192、接收器193、发送器194通过总线195连接。
存储器191用于存储指令,处理器192用于调用存储器191中的指令执行前述方法实施例。具体地:
处理器192,用于生成服务质量Qos映射关系,所述Qos映射关系用于表示预设粒度业务数据与Qos需求参数的映射关系。
发送器194,用于将所述Qos映射关系发送给无线接入网网元。
可选地,发送器194,还用于将所述Qos映射关系发送给无线接入网网元。
可选地,所述Qos映射关系包括:业务数据特征信息与Qos需求的映射关系。
可选地,所述特征信息包括下述一项或其任意组合:协议层的端口号、特征字、关联特征、数据流行为;其中,所述关联特征指联合识别的多个特征字。
可选地,所述Qos映射关系包括:业务数据中Qos标识与Qos需求参数的映射关系。
可选地,所述预设服务质量Qos映射关系为:预设通道标识与Qos需求参数的映射关系。
可选地,发送器194,还用于向核心网用户面功能实体发送至少一套Qos需求参数。
上述装置用于执行前述方法实施例,其实现原理和技术效果类似,详细内容可以参照前述方法实施例。
本领域普通技术人员可以理解:实现上述方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成,前述的程序可以存储于一计算机可读取存储介质中,该程序在执行时,执行包括上述方法实施例的步骤;而前述的存储介质包括:ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
最后应说明的是:以上各实施例仅用以说明本发明的技术方案,而非对其限制;尽管参照前述各实施例对本发明进行了详细的说明,本领域的普通技术人员应当理解:其依然可以对前述各实施例所记载的技术方案进行修改,或者对其中部分或者全部技术特征进行等同替换;而这些修改或者替换,并不使相应技术方案的本质脱离本发明各实施例技术方案的范围。

Claims (24)

  1. 一种数据传输的方法,其特征在于,包括:
    终端获取待传输预设粒度上行业务数据;
    所述终端获取所述待传输预设粒度上行业务数据对应的Qos需求参数;
    所述终端根据所述待传输预设粒度上行业务数据对应的Qos需求参数,传输所述待传输预设粒度上行业务数据。
  2. 根据权利要求1所述的方法,其特征在于,所述终端获取所述待传输预设粒度上行业务数据对应的Qos需求参数,包括:
    所述终端根据所述待传输预设粒度上行业务数据、以及预设服务质量Qos映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
  3. 根据权利要求2所述的方法,其特征在于,所述预设服务质量Qos映射关系为:预设特征信息与Qos需求参数的映射关系;
    所述终端根据待传输预设粒度上行业务数据、以及预设Qos映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数,包括:
    所述终端识别所述待传输预设粒度上行业务数据的特征信息;
    所述终端根据所述待传输预设粒度上行业务数据的特征信息、以及所述预设特征信息与Qos需求参数的映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
  4. 根据权利要求3所述的方法,其特征在于,所述特征信息包括下述一项或其任意组合:协议层的端口号、特征字、关联特征、数据流行为;其中,所述关联特征指联合识别的多个特征字。
  5. 根据权利要求2所述的方法,其特征在于,所述预设Qos映射关系为:预设Qos标识与Qos需求参数的映射关系;
    所述终端根据所述待传输预设粒度上行业务数据、以及预设服务质量Qos映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数,包括:
    所述终端获取所述待传输预设粒度上行业务数据中的Qos标识;
    所述终端根据所述待传输预设粒度上行业务数据中的Qos标识、以及所述预设Qos标识与Qos需求参数的映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
  6. 根据权利要求1-5任一项所述的方法,其特征在于,所述Qos需求参数包括下述至少一项或其任意组合:流聚合最大比特速率AMBR、无线承载AMBR、终端AMBR、优先级、时间延迟、丢包率、切换特性、时变特性、分配保留优先级ARP。
  7. 根据权利要求2所述的方法,其特征在于,所述终端获取所述待传输预设粒度上行业务数据对应的Qos需求参数之前,还包括:
    所述终端接收核心网控制功能实体或RAN网元发送的Qos增强属性信息;相应地,
    所述终端获取所述待传输预设粒度上行业务数据对应的Qos需求参数,包括:
    所述终端根据所述待传输预设粒度上行业务数据对应的Qos增强属性信息、以及预设Qos映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
  8. 根据权利要求7所述的方法,其特征在于,所述Qos增强属性信息包括下述任一项或其任意组合:时变属性、分类属性、粒度属性;
    其中,所述时变属性用于标识业务过程中业务数据的状态是否随时间变化、且Qos需求参数是否随业务数据的状态变化;所述分类属性用于标识业务数据是否根据Qos需求参数分类;所述粒度属性用于标识Qos的处理粒度。
  9. 根据权利要求2所述的方法,其特征在于,所述终端根据所述待传输预设粒度上行业务数据对应的Qos需求参数,传输所述待传输预设粒度上行业务数据,包括:
    所述终端根据所述待传输预设粒度上行业务数据对应的Qos需求参数,调整所述待传输预设粒度上行业务数据对应的逻辑信道的调度策略,采用调整后的逻辑信道向RAN网元传输所述待传输预设粒度上行业务数据。
  10. 根据权利要求2所述的方法,其特征在于,所述终端根据所述待传输预设粒度上行业务数据对应的Qos需求参数,传输所述待传输预设粒度上行业务数据,包括:
    所述终端根据所述待传输预设粒度上行业务数据对应的Qos需求参数、以及预设Qos需求参数与子RB之间的映射关系,将所述待传输预设粒度上行业务数据映射到对应的子无线承载RB上传输。
  11. 根据权利要求10所述的方法,其特征在于,所述终端根据所述待传输预设粒度上行业务数据对应的Qos需求参数、以及预设Qos需求参数与子RB之间的映射关系,将所述待传输预设粒度上行业务数据映射到对应的子无线承载RB上传输之前,还包括:
    所述终端接收所述RAN网元发送的所述预设Qos需求参数与子RB之间的映射关系。
  12. 根据权利要求2所述的方法,其特征在于,所述终端根据所述待传输预设粒度上行业务数据对应的Qos需求参数,传输所述待传输预设粒度上行业务数据,包括:
    终端采用各协议层对应的预设处理模板传输所述待传输预设粒度上行业务数据,其中,不同所述预设处理模板对应的Qos需求参数不同。
  13. 一种数据传输的装置,其特征在于,包括:
    获取模块,用于获取待传输预设粒度上行业务数据;
    确定模块,用于获取所述待传输预设粒度上行业务数据对应的Qos需求参数;
    传输模块,用于根据所述待传输预设粒度上行业务数据对应的Qos需求参数,传输所述待传输预设粒度上行业务数据。
  14. 根据权利要求13所述的装置,其特征在于,所述确定模块,具体用于根据所述待传输预设粒度上行业务数据、以及预设服务质量Qos映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
  15. 根据权利要求14所述的装置,其特征在于,所述预设服务质量Qos映射关系为:预设特征信息与Qos需求参数的映射关系;
    所述确定模块,具体用于识别所述待传输预设粒度上行业务数据的特征信息;根据所述待传输预设粒度上行业务数据的特征信息、以及所述预设特征信息与Qos需求参数的映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
  16. 根据权利要求14所述的装置,其特征在于,所述特征信息包括下述一项或其任意组合:协议层的端口号、特征字、关联特征、数据流行为;其中,所述关联特征指联合识别的多个特征字。
  17. 根据权利要求14所述的装置,其特征在于,所述预设Qos映射关系 为:预设Qos标识与Qos需求参数的映射关系;
    所述确定模块,具体用于获取所述待传输预设粒度上行业务数据中的Qos标识;根据所述待传输预设粒度上行业务数据中的Qos标识、以及所述预设Qos标识与Qos需求参数的映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
  18. 根据权利要求13-17任一项所述的装置,其特征在于,所述Qos需求参数包括下述至少一项或其任意组合:流聚合最大比特速率AMBR、无线承载AMBR、终端AMBR、优先级、时间延迟、丢包率、切换特性、时变特性、分配保留优先级ARP。
  19. 根据权利要求14所述的装置,其特征在于,所述装置还包括:第一接收模块,用于接收核心网控制功能实体或RAN网元发送的Qos增强属性信息;相应地,
    所述确定模块,具体用于根据所述待传输预设粒度上行业务数据对应的Qos增强属性信息、以及预设Qos映射关系,获取所述待传输预设粒度上行业务数据对应的Qos需求参数。
  20. 根据权利要求19所述的装置,其特征在于,所述Qos增强属性信息包括下述任一项或其任意组合:时变属性、分类属性、粒度属性;
    其中,所述时变属性用于标识业务过程中业务数据的状态是否随时间变化、且Qos需求参数是否随业务数据的状态变化;所述分类属性用于标识业务数据是否根据Qos需求参数分类;所述粒度属性用于标识Qos的处理粒度。
  21. 根据权利要求14所述的装置,其特征在于,所述传输模块,具体用于根据所述待传输预设粒度上行业务数据对应的Qos需求参数,调整所述待传输预设粒度上行业务数据对应的逻辑信道的调度策略,采用调整后的逻辑信道向RAN网元传输所述待传输预设粒度上行业务数据。
  22. 根据权利要求14所述的装置,其特征在于,所述传输模块,具体用于根据所述待传输预设粒度上行业务数据对应的Qos需求参数、以及预设Qos需求参数与子RB之间的映射关系,将所述待传输预设粒度上行业务数据映射到对应的子无线承载RB上传输。
  23. 根据权利要求14所述的装置,其特征在于,所述装置还包括:第二接收模块,用于接收所述RAN网元发送的所述预设Qos需求与子RB之间的 映射关系。
  24. 根据权利要求14所述的装置,其特征在于,所述传输模块,具体用于采用各协议层对应的预设处理模板对所述待传输预设粒度上行业务数据进行Qos处理,并将处理后的所述待传输预设粒度上行业务数据发送给RAN网元。
PCT/CN2016/083198 2016-05-24 2016-05-24 数据传输的方法及装置 WO2017201677A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP16902667.1A EP3447978B1 (en) 2016-05-24 2016-05-24 Data transmission method and device
BR112018073970A BR112018073970A2 (pt) 2016-05-24 2016-05-24 método e aparelho de transmissão de dados
CN201680086064.5A CN109155762B (zh) 2016-05-24 2016-05-24 数据传输的方法及装置
PCT/CN2016/083198 WO2017201677A1 (zh) 2016-05-24 2016-05-24 数据传输的方法及装置
US16/198,720 US10721754B2 (en) 2016-05-24 2018-11-21 Data transmission method and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/083198 WO2017201677A1 (zh) 2016-05-24 2016-05-24 数据传输的方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/198,720 Continuation US10721754B2 (en) 2016-05-24 2018-11-21 Data transmission method and apparatus

Publications (1)

Publication Number Publication Date
WO2017201677A1 true WO2017201677A1 (zh) 2017-11-30

Family

ID=60411033

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/083198 WO2017201677A1 (zh) 2016-05-24 2016-05-24 数据传输的方法及装置

Country Status (5)

Country Link
US (1) US10721754B2 (zh)
EP (1) EP3447978B1 (zh)
CN (1) CN109155762B (zh)
BR (1) BR112018073970A2 (zh)
WO (1) WO2017201677A1 (zh)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108984254A (zh) * 2018-07-03 2018-12-11 深圳市必发达科技有限公司 一种基于即时通讯工具的信息处理方法
CN110858987A (zh) * 2018-08-24 2020-03-03 中兴通讯股份有限公司 一种数据传输方法、装置、设备及计算机可读介质
CN112449434A (zh) * 2019-08-28 2021-03-05 中国移动通信有限公司研究院 一种信息传输方法、装置和计算机可读存储介质
WO2021212438A1 (zh) * 2020-04-23 2021-10-28 深圳市大疆创新科技有限公司 数据传输方法、装置、系统、终端设备和存储介质
WO2022257967A1 (zh) * 2021-06-10 2022-12-15 维沃移动通信有限公司 传输处理方法、装置、接入网节点及核心网节点
WO2023010254A1 (zh) * 2021-08-02 2023-02-09 Oppo广东移动通信有限公司 数据传输方法、装置、设备及存储介质
WO2023125096A1 (zh) * 2021-12-31 2023-07-06 中兴通讯股份有限公司 参数配置方法、通信设备和存储介质

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10524181B2 (en) * 2016-08-03 2019-12-31 Samsung Electronics Co., Ltd. Method for cell reselection in idle mode for next generation mobile communication systems
KR102322381B1 (ko) * 2018-02-14 2021-11-10 주식회사 케이티 릴레이 노드에서 rrc 메시지를 처리하는 방법 및 그 장치
CN111510949B (zh) * 2019-01-30 2023-05-05 中国移动通信有限公司研究院 一种数据传输方法、装置和存储介质
US20210392033A1 (en) * 2020-06-15 2021-12-16 Plantronics, Inc. Systems and Methods for Managing Failed Packet Transmissions using a Smart Retransmission Scheme with Hierarchical Packet Analysis
CN112449384B (zh) * 2019-08-31 2022-05-24 华为技术有限公司 数据处理方法、装置和系统
US20230261817A1 (en) * 2019-10-16 2023-08-17 Telefonaktiebolaget Lm Ericsson (Publ) Multiplexed transmission of data packages towards a terminal device
CN113677005A (zh) * 2020-05-14 2021-11-19 华为技术有限公司 一种通信方法及装置
CN115225498A (zh) * 2021-03-29 2022-10-21 中国移动通信集团广东有限公司 一种局数据配置方法及装置
CN117641465A (zh) * 2022-08-10 2024-03-01 华为技术有限公司 一种通信方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102638852A (zh) * 2011-02-12 2012-08-15 电信科学技术研究院 一种基于服务质量的调度方法、设备及系统
US20130007234A1 (en) * 2011-06-29 2013-01-03 International Business Machines Corporation Dynamically modifying quality of service levels for resources in a networked computing environment
CN103595764A (zh) * 2013-10-17 2014-02-19 航天恒星科技有限公司 一种超大规模VSAT系统的多业务QoS保障系统及其实现方法

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008021182A2 (en) * 2006-08-09 2008-02-21 Interdigital Technology Corporation Method and apparatus for providing differentiated quality of service for packets in a particular flow
CN101128040A (zh) * 2006-08-18 2008-02-20 华为技术有限公司 无线通信网络及其业务控制方法
EP2745477B1 (en) * 2011-08-18 2016-04-27 VID SCALE, Inc. Methods and systems for packet differentiation
TW201442527A (zh) * 2013-01-11 2014-11-01 Interdigital Patent Holdings 使用者平面壅塞管理
EP2944062B1 (en) * 2013-01-11 2019-10-30 Interdigital Patent Holdings, Inc. System and method for adaptive modulation

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102638852A (zh) * 2011-02-12 2012-08-15 电信科学技术研究院 一种基于服务质量的调度方法、设备及系统
US20130007234A1 (en) * 2011-06-29 2013-01-03 International Business Machines Corporation Dynamically modifying quality of service levels for resources in a networked computing environment
CN103595764A (zh) * 2013-10-17 2014-02-19 航天恒星科技有限公司 一种超大规模VSAT系统的多业务QoS保障系统及其实现方法

Non-Patent Citations (1)

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

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108984254A (zh) * 2018-07-03 2018-12-11 深圳市必发达科技有限公司 一种基于即时通讯工具的信息处理方法
CN110858987A (zh) * 2018-08-24 2020-03-03 中兴通讯股份有限公司 一种数据传输方法、装置、设备及计算机可读介质
CN110858987B (zh) * 2018-08-24 2022-09-30 中兴通讯股份有限公司 一种数据传输方法、装置、设备及计算机可读介质
CN112449434A (zh) * 2019-08-28 2021-03-05 中国移动通信有限公司研究院 一种信息传输方法、装置和计算机可读存储介质
WO2021212438A1 (zh) * 2020-04-23 2021-10-28 深圳市大疆创新科技有限公司 数据传输方法、装置、系统、终端设备和存储介质
WO2022257967A1 (zh) * 2021-06-10 2022-12-15 维沃移动通信有限公司 传输处理方法、装置、接入网节点及核心网节点
WO2023010254A1 (zh) * 2021-08-02 2023-02-09 Oppo广东移动通信有限公司 数据传输方法、装置、设备及存储介质
WO2023125096A1 (zh) * 2021-12-31 2023-07-06 中兴通讯股份有限公司 参数配置方法、通信设备和存储介质

Also Published As

Publication number Publication date
BR112018073970A2 (pt) 2019-03-06
EP3447978B1 (en) 2021-07-28
CN109155762A (zh) 2019-01-04
EP3447978A1 (en) 2019-02-27
US20190090257A1 (en) 2019-03-21
CN109155762B (zh) 2021-08-20
EP3447978A4 (en) 2019-03-20
US10721754B2 (en) 2020-07-21

Similar Documents

Publication Publication Date Title
US10721754B2 (en) Data transmission method and apparatus
US11240724B2 (en) Method and device for handover
CN109565703B (zh) 用于管理无线通信网络中的数据通信的方法和设备
US9432873B2 (en) Differentiation of traffic flows for uplink transmission
AU2018215661A1 (en) Multi-technology aggregation architecture for long term evolution communications systems
WO2013010462A1 (zh) 保证上行服务质量的方法、基站及用户设备
KR20140017662A (ko) 모바일 송수신기, 기지국 송수신기, 데이터 서버, 그리고 관련 장치, 방법 및 컴퓨터 프로그램
WO2018103675A1 (zh) 数据流重映射方法及装置和用户设备、ran设备
WO2018059518A1 (zh) 一种数据传输方法、装置和系统
US20230116578A1 (en) Data transmission method and apparatus
US20220303825A1 (en) Data transmission method and apparatus
WO2019101054A1 (zh) 聚合速率控制方法、设备以及系统
EP4216603A1 (en) Data processing method, device, readable storage medium, and program product
WO2018082431A1 (zh) 无线通信方法、用户设备接入网设备、和核心网设备
WO2016161594A1 (zh) 一种数据传输的方法及装置
US11647419B2 (en) Adjusting window size based on quality of experience
WO2022012361A1 (zh) 一种通信方法及装置
CN116746264A (zh) 一种通信方法及装置
WO2023185608A1 (zh) 一种数据传输的方法及通信装置
WO2023184552A1 (zh) 一种数据传输方法及装置、通信设备
WO2023184545A1 (zh) 一种数据传输方法及装置、通信设备
WO2023185402A1 (zh) 通信方法及装置
WO2024032211A1 (zh) 一种拥塞控制方法以及装置

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112018073970

Country of ref document: BR

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

Ref document number: 16902667

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2016902667

Country of ref document: EP

Effective date: 20181123

ENP Entry into the national phase

Ref document number: 112018073970

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20181122