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

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

Info

Publication number
WO2018001297A1
WO2018001297A1 PCT/CN2017/090746 CN2017090746W WO2018001297A1 WO 2018001297 A1 WO2018001297 A1 WO 2018001297A1 CN 2017090746 W CN2017090746 W CN 2017090746W WO 2018001297 A1 WO2018001297 A1 WO 2018001297A1
Authority
WO
WIPO (PCT)
Prior art keywords
user plane
bearer type
configuration
bearer
plane configuration
Prior art date
Application number
PCT/CN2017/090746
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 US16/313,818 priority Critical patent/US20190159021A1/en
Priority to EP17819294.4A priority patent/EP3480989B1/en
Publication of WO2018001297A1 publication Critical patent/WO2018001297A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for data transmission.
  • SRB Signaling Radio Bearer
  • Data Radio Bearer Data Radio Bearer
  • the high-level control information is transmitted through the SRB on the air interface; the data information is transmitted through the DRB in the air interface.
  • the network needs to configure the parameters corresponding to the bearer for each SRB/DRB through the RRC Connection Reconfiguration.
  • the main configuration parameters related to SRB include:
  • srb-Identity identifier corresponding to the SRB, such as the SRB number.
  • Rlc-Config RLC layer configuration corresponding to the SRB
  • logicalChannelConfig Indicates the logical channel configuration of the SRB.
  • the main configuration parameters related to DRB include:
  • eps-BearerIdentity ID of the EPS bearer corresponding to the DRB, such as the EPS bearer number.
  • drb-Identity DRB identifier corresponding to the DRB, such as the DRB number.
  • pdcp-Config PDCP layer configuration corresponding to the DRB
  • rlc-Config RLC layer configuration corresponding to the DRB
  • logicalChannelIdentity the logical channel identifier corresponding to the DRB
  • logicalChannelConfig The logical channel configuration corresponding to the DRB.
  • eMBB enhanced Mobile Broadband
  • Ultra-dense networking is a trend in the development of mobile communication systems in the future.
  • some protocol functions need to be processed centrally.
  • a two-layer structure of a centralized processing node and a distributed processing node is formed, and the distributed processing node is also called a TRP (Transmission Reception Point).
  • TRP Transmission Reception Point
  • the centralized processing node according to different functions, it can be further divided into a control plane of the centralized processing node and a user plane of the centralized processing node.
  • an embodiment of the present disclosure provides a data transmission method and apparatus for ensuring that a future mobile communication system can perform data transmission management more effectively and reduce system signaling overhead.
  • a data transmission method including:
  • the terminal determines a correspondence between the bearer type and the user plane configuration
  • the terminal performs data transmission according to the determined user plane configuration.
  • the user plane configuration includes a user plane function configuration and/or a user plane parameter configuration.
  • the user plane configuration corresponding to the bearer type is a configuration of a user plane basic function and/or a parameter, or the user plane configuration corresponding to the bearer type is a configuration set of user plane basic functions and/or parameters.
  • the user plane configuration includes a manner in which the user plane function divides functions between the centralized processing node and the distributed processing node.
  • determining a correspondence between the bearer type and the user plane configuration including:
  • the terminal determines a correspondence between the bearer type of the bearer and the user plane configuration according to the service type and/or the network deployment corresponding to the bearer.
  • the terminal determines a correspondence between the bearer type and the user plane configuration, including:
  • the terminal determines the correspondence between the bearer type and the user plane configuration by using the pre-configuration information.
  • the terminal determines the correspondence between the bearer type and the user plane configuration by using the pre-configuration information, including:
  • the terminal determines, from the pre-configuration information, a correspondence between a bearer type and a user plane configuration corresponding to the terminal capability.
  • the terminal determines a correspondence between the bearer type and the user plane configuration, including:
  • the terminal obtains the correspondence between the bearer type and the user plane configuration by means of network notification.
  • the terminal obtains a correspondence between the bearer type and the user plane configuration by using a network notification manner, including:
  • the terminal reports the terminal capability
  • the terminal obtains the correspondence between the bearer type and the user plane configuration corresponding to the terminal capability by means of the network notification.
  • the user plane configuration corresponding to the bearer type includes one or more of the following: header compression, encryption, integrity protection, segmentation, concatenation, ARQ, HARQ, multiplexing, Qos parameters, scheduling mode, and modulation. Mode, encoding method and multiple access method.
  • a method for data transmission comprising:
  • the network side device determines a correspondence between the bearer type and the user plane configuration.
  • the network side device configuration bears a corresponding bearer type
  • the network side device sends the bearer type indication information, where the bearer type indication information carries the bearer type identifier;
  • the network side device according to the bearer type identifier and the pair of bearer type and user plane configuration The relationship of the user plane corresponding to the bearer should be determined;
  • the network side device performs data transmission according to the determined user plane configuration.
  • the user plane configuration includes a user plane function configuration and/or a user plane parameter configuration.
  • the user plane configuration corresponding to the bearer type is a configuration of a user plane basic function and/or a parameter, or the user plane configuration corresponding to the bearer type is a configuration set of user plane basic functions and/or parameters.
  • the user plane configuration includes a manner in which the user plane function divides functions between the centralized processing node and the distributed processing node.
  • the network side device determines a correspondence between the bearer type and the user plane configuration, including:
  • the network side device determines the correspondence between the bearer type and the user plane configuration by using the pre-configuration information.
  • the method further includes:
  • the network side device notifies the terminal of the correspondence between the bearer type and the user plane configuration by means of network notification.
  • the network side device notifies the terminal of the correspondence between the bearer type and the user plane configuration by using a network notification manner, including:
  • the network side device acquires the terminal capability reported by the terminal;
  • the network side device notifies the terminal of the correspondence between the bearer type and the user plane configuration corresponding to the terminal capability by means of the network notification.
  • the user plane configuration corresponding to the bearer type includes one or more of the following: header compression, encryption, integrity protection, segmentation, concatenation, ARQ, HARQ, multiplexing, Qos parameters, scheduling mode, and modulation. Mode, encoding method and multiple access method.
  • an apparatus for data transmission including:
  • a first determining module configured to determine a correspondence between a bearer type and a user plane configuration
  • a receiving module configured to receive the bearer type indication information indicated by the network side, where the bearer type indication information carries the bearer type identifier;
  • a second determining module configured to determine, according to the bearer type identifier indication carried in the bearer type indication information, and the correspondence between the bearer type indication and the user plane configuration, the user plane configuration corresponding to the bearer to be established;
  • a transmission module for performing data transmission according to the determined user plane configuration.
  • the user plane configuration includes a user plane function configuration and/or a user plane parameter configuration.
  • the user plane configuration corresponding to the bearer type is a configuration of a user plane basic function and/or a parameter, or the user plane configuration corresponding to the bearer type is a configuration set of user plane basic functions and/or parameters.
  • the user plane configuration includes a manner in which the user plane function divides functions between the centralized processing node and the distributed processing node.
  • the first determining unit is further configured to: determine, according to the service type and/or network deployment corresponding to the bearer, a correspondence between a bearer type of the bearer and a user plane configuration.
  • the first determining unit is further configured to: determine, by using the pre-configuration information, a correspondence between the bearer type and the user plane configuration.
  • the first determining unit is further configured to: determine, from the pre-configuration information, a correspondence between a bearer type and a user plane configuration corresponding to the terminal capability.
  • the first determining unit is further configured to: obtain a correspondence between the bearer type and the user plane configuration by means of network notification.
  • the first determining unit is further configured to: report the terminal capability; and obtain, by using a network notification, a correspondence between the bearer type and the user plane configuration corresponding to the terminal capability.
  • the user plane configuration corresponding to the bearer type includes one or more of the following: header compression, encryption, integrity protection, segmentation, concatenation, ARQ, HARQ, multiplexing, Qos parameters, scheduling mode, and modulation. Mode, encoding method and multiple access method.
  • an apparatus for data transmission comprising:
  • a third determining module configured to determine a correspondence between a bearer type and a user plane configuration
  • a configuration module configured to configure a bearer type corresponding to the bearer
  • a sending module configured to send bearer type indication information, where the bearer type indication information carries the bearer type identifier
  • a fourth determining module configured to determine, according to the bearer type identifier and the corresponding relationship between the bearer type and the user plane configuration, a user plane configuration corresponding to the bearer;
  • a transmission module for performing data transmission according to the determined user plane configuration.
  • the user plane configuration includes a user plane function configuration and/or a user plane parameter configuration.
  • the user plane configuration corresponding to the bearer type is a configuration of a user plane basic function and/or a parameter, or the user plane configuration corresponding to the bearer type is a configuration set of user plane basic functions and/or parameters.
  • the user plane configuration includes a manner in which the user plane function divides functions between the centralized processing node and the distributed processing node.
  • the third determining module is further configured to: determine, by using the pre-configuration information, a correspondence between the bearer type and the user plane configuration.
  • the device further includes:
  • the notification module is configured to notify the terminal of the correspondence between the bearer type and the user plane configuration by means of network notification.
  • the notification module is further configured to: acquire the terminal capability reported by the terminal, and notify the terminal of the correspondence between the bearer type and the user plane configuration corresponding to the terminal capability by using a network notification manner.
  • the user plane configuration corresponding to the bearer type includes one or more of the following: header compression, encryption, integrity protection, segmentation, concatenation, ARQ, HARQ, multiplexing, Qos parameters, scheduling mode, and modulation. Mode, encoding method and multiple access method.
  • a terminal comprising: a processor, a memory, and a transceiver, wherein
  • the memory is configured to store an instruction used by the processor when performing an operation
  • the processor is configured to determine a correspondence between a bearer type and a user plane configuration
  • the transceiver is configured to receive the bearer type indication information indicated by the network side, where the bearer type indication information carries the bearer type identifier;
  • the processor is further configured to determine, according to the bearer type identifier carried in the bearer type indication information, and the corresponding relationship between the bearer type and the user plane configuration, the user plane configuration corresponding to the bearer;
  • a network side device including: a processor, a memory, and a transceiver.
  • the memory is configured to store an instruction used by the processor when performing an operation
  • the processor is configured to determine a correspondence between a bearer type and a user plane configuration
  • the transceiver is configured to send bearer type indication information, where the bearer type indication information carries a bearer type identifier;
  • the processor is further configured to determine, according to the bearer type identifier and the corresponding relationship between the bearer type and the user plane configuration, a user plane configuration corresponding to the bearer;
  • the transceiver is further configured to perform data transmission according to the determined user plane configuration.
  • the network and the terminal perform user plane data transmission based on the user plane function corresponding to the bearer type, thereby ensuring that the mobile communication system can perform data transmission management more effectively and reduce the bearer.
  • the configured signaling overhead can better support network slicing.
  • FIG. 1 is a schematic diagram of a network architecture of a future mobile communication system
  • FIG. 2 is a schematic diagram of user plane protocol layer separation between a centralized processing node and a distributed processing node in the related art
  • FIG. 3 is a flowchart of a method for data transmission in an embodiment of the present disclosure
  • FIG. 5 is a schematic diagram of a pre-configured bearer type and a corresponding user plane configuration thereof according to an embodiment of the present disclosure
  • FIG. 6 is a schematic diagram of a bearer type and a corresponding user plane configuration correspondence sent by a broadcast manner according to an embodiment of the present disclosure
  • FIG. 7 is a schematic diagram of a bearer type and a corresponding user plane configuration corresponding relationship sent by using a dedicated signaling manner according to an embodiment of the present disclosure
  • FIG. 8 is a block diagram of an apparatus for data transmission in an embodiment of the present disclosure.
  • FIG. 9 is a block diagram of an apparatus for data transmission in an embodiment of the present disclosure.
  • FIG. 10 is a block diagram of an apparatus for data transmission in an embodiment of the present disclosure.
  • Figure 11 is a block diagram of an apparatus for data transmission in an embodiment of the present disclosure.
  • embodiments of the present disclosure may be implemented as a system, apparatus, device, method, or computer program product.
  • embodiments of the present disclosure may be embodied in the form of full hardware, complete software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.
  • FIG. 1 shows a schematic diagram of a network architecture of a future mobile communication system.
  • the user plane function may be divided between the centralized processing node and the distributed processing node.
  • Option 1-Option 5 there are five user plane protocol layer separation schemes (Option 1-Option 5), see figure 2.
  • Step 301 the terminal determines the correspondence between the bearer type and the user plane configuration, and then proceeds to step 302;
  • the user plane configuration may include: a user plane function configuration and/or a user plane parameter configuration, and is not limited thereto.
  • the foregoing user plane configuration may include a manner in which the user plane function divides functions between the centralized processing node and the distributed processing node, and is not limited thereto.
  • the bearer type may correspond to a service type, such as eMBB, mMTC, URLLC, and the like.
  • the user plane configuration corresponding to the bearer type is a configuration of the basic functions and/or parameters of the user plane, or the user plane configuration corresponding to the bearer type is a configuration set of basic functions and/or parameters of the user plane, and is not limited thereto.
  • the network side can change the configuration based on the above bearer type through the delta (variable) configuration.
  • the URLLC service As an example. Because of its high reliability and low latency, the data packets are generally small. Therefore, the corresponding bearer user plane function cannot support functions such as ARQ (automatic retransmission request) and segmentation, and user plane parameters, such as TTI (Transmission Time Interval), should select a relatively short TTI.
  • ARQ automatic retransmission request
  • TTI Transmission Time Interval
  • the user plane configuration corresponding to the bearer type includes one or more of the following: header compression, encryption, integrity protection, segmentation, concatenation, ARQ (Automatic RepeatreQuest, automatic request reply), HARQ (Hybrid Automatic Repeat reQuest) Transmission request), multiplexing, Qos (Quality of Service) parameters, scheduling mode, modulation mode, coding mode, and multiple access mode.
  • header compression encryption, integrity protection, segmentation, concatenation, ARQ (Automatic RepeatreQuest, automatic request reply), HARQ (Hybrid Automatic Repeat reQuest) Transmission request), multiplexing, Qos (Quality of Service) parameters, scheduling mode, modulation mode, coding mode, and multiple access mode.
  • the terminal determines the user plane configuration corresponding to the bearer type, factors such as the corresponding service type and network deployment may be considered.
  • the terminal can determine the correspondence between the bearer type and the user plane configuration in the following three manners:
  • the correspondence between the user plane configurations corresponding to each bearer type is stipulated in the protocol.
  • Option 2 The network notifies the mapping between the bearer type and the user plane configuration by broadcast.
  • the user plane configuration corresponding to the bearer type is determined by the network, and then notified to the terminal by broadcast.
  • a new channel and a new RNTI may be defined for the broadcast, or a periodic broadcast may be performed using a specific resource and a specific channel.
  • Option 3 The network notifies the mapping between the bearer type and the user plane configuration through dedicated signaling.
  • the network After the terminal establishes an RRC connection with the network, the network notifies the terminal of the correspondence between the bearer type and the user plane configuration by using a dedicated signaling manner.
  • the terminal capability only supports N types of bearer types, the terminal only needs to know the user plane configuration corresponding to the N types of bearer types through pre-configuration or network notification.
  • the network side may select one bearer type configuration from the bearer type corresponding to the service type indication information to the terminal according to the terminal service type indication information.
  • the network may notify the user plane configuration corresponding to the bearer type when the bearer of a bearer type of the terminal is about to be established.
  • the bearer type and the user plane configuration correspondence need only be notified once.
  • the bearer and the network slice may be mapped, and the bearer identification information is replaced with the network slice identifier information.
  • the mapping between the bearer and the user plane configuration is replaced by the correspondence between the network switch and the user plane configuration.
  • Step 302 The terminal receives the bearer type indication information indicated by the network side, and carries the bearer type identifier carried in the bearer type indication information, and then proceeds to step 303.
  • the network side may be referred to as a network side control plane processing unit, and is of course not limited thereto.
  • the network side sends the bearer type indication information to the terminal.
  • Step 303 The terminal determines the user plane configuration corresponding to the bearer according to the bearer type identifier carried in the bearer type indication information, and the corresponding relationship between the bearer type and the user plane configuration, and then proceeds to step 304.
  • the bearer type identifier may also be referred to as a bearer type corresponding number, and is of course not limited thereto.
  • Step 304 The terminal performs data transmission according to the determined user plane configuration.
  • the terminal does not need to perform header compression when transmitting the uplink data corresponding to the bearer.
  • the base station does not need to perform decompression when receiving the data, and the processing manners of other user plane configurations are similar, and will not be described here.
  • the network and the terminal perform user plane data transmission based on the user plane function corresponding to the bearer type. It ensures that the future mobile communication system can perform data transmission management more effectively, reduce the signaling overhead of the bearer configuration, and better support network slicing.
  • Step 401 the network side device determines the correspondence between the bearer type and the user plane configuration, and then proceeds to step 402;
  • the network side device determines the correspondence between the bearer type and the user plane configuration by using the pre-configuration information, for example, the user plane configuration corresponding to each bearer type is agreed in the protocol.
  • the network side device may be a network side control plane processing unit.
  • the corresponding processing unit is a centralized processing unit.
  • the user plane configuration may include: a user plane function configuration and/or a user plane parameter configuration, and is not limited thereto.
  • the foregoing user plane configuration may include a manner in which the user plane function divides functions between the centralized processing node and the distributed processing node, and is not limited thereto.
  • the bearer type N corresponds to a certain division manner of the user plane function in FIG. 2 between the centralized processing node and the distributed processing node, such as option2.
  • the other type of bearer M corresponds to the way in which the different household functions are divided between the centralized processing node and the distributed processing node.
  • the bearer type may correspond to a service type, such as eMBB, mMTC, URLLC, and the like.
  • the user plane configuration corresponding to the bearer type is a configuration of the basic functions and/or parameters of the user plane, or the user plane configuration corresponding to the bearer type is a configuration set of basic functions and/or parameters, and is not limited thereto.
  • the network can change the configuration based on the above bearer type through the delta (variable) configuration. Take the URLLC service as an example. Because of its high reliability and low latency, the data packets are generally small.
  • the corresponding bearer user plane function cannot support functions such as ARQ (automatic retransmission request) and segmentation, and user plane parameters, such as TTI (Transmission Time Interval), should select a relatively short TTI.
  • ARQ automatic retransmission request
  • TTI Transmission Time Interval
  • the user plane configuration corresponding to the bearer type includes one or more of the following: header compression, encryption, integrity protection, segmentation, concatenation, ARQ (Automatic RepeatreQuest, automatic request reply), HARQ (Hybrid Automatic Repeat reQuest) Transmission request), multiplexing, QoS parameters, scheduling mode, modulation mode, coding mode, and multiple access mode.
  • the network side device may notify the terminal of the correspondence between the bearer type and the user plane configuration by using the network notification manner, and notify the network.
  • the manner of the broadcast notification may be the manner of the broadcast notification or the manner of the dedicated signaling, for example, the user plane configuration corresponding to the bearer type is determined by the network, and then notified to the terminal by broadcast.
  • a new channel and a new RNTI Radio Network Temporary Identity
  • the network notifies the terminal of the correspondence between the bearer type and the user plane configuration by means of dedicated signaling.
  • the terminal capability only supports N types of bearer types, the terminal only needs to know the user plane configuration corresponding to the N types of bearer types through pre-configuration or network notification.
  • the network side may select one bearer type configuration from the bearer type corresponding to the service type indication information to the terminal according to the terminal service type indication information.
  • the network may notify the user plane configuration corresponding to the bearer type when the bearer of a bearer type of the terminal is about to be established.
  • the bearer type and the user plane configuration correspondence need only be notified once.
  • the bearer and the network slice may be mapped, and the bearer identification information is replaced with the network slice identifier information.
  • the mapping between the bearer and the user plane configuration is replaced by the correspondence between the network switch and the user plane configuration.
  • Step 402 the network side device configuration bearer corresponding bearer type, and then proceeds to step 403;
  • the network side device may select one bearer type configuration from the bearer type corresponding to the service type indication information to the terminal according to the terminal service type indication information.
  • Step 403 the network side device sends the bearer type indication information, the bearer type indication information carries the bearer type identifier, and then proceeds to step 404;
  • the bearer type identifier may also be referred to as a bearer type corresponding number, and is of course not limited thereto.
  • Step 404 The network side device determines the user plane configuration corresponding to the bearer according to the bearer type identifier and the corresponding relationship between the bearer type and the user plane configuration, and then proceeds to step 405.
  • Step 405 The network side device performs data transmission according to the determined user plane configuration.
  • the base station does not need to perform header compression when delivering the downlink data corresponding to the bearer.
  • the terminal does not need to receive the data. Line decompression, other user plane configuration is handled similarly, and will not be described here.
  • the network and the terminal perform user plane data transmission based on the user plane function corresponding to the bearer type. It ensures that the future mobile communication system can perform data transmission management more effectively, reduce the signaling overhead of the bearer configuration, and better support network slicing.
  • Step 501 Determine a bearer type and a corresponding user plane configuration.
  • the network and the terminal respectively determine the bearer type and the user plane configuration corresponding to the bearer type according to the pre-configuration information.
  • the pre-configuration information may be a default configuration agreed in the protocol, or may be configuration information pre-configured in the base station and the terminal.
  • the user plane configuration corresponding to the bearer type includes user plane function configuration and/or user plane parameter configuration.
  • the user plane configuration corresponding to the bearer type is a configuration of basic functions and/or parameters of the user plane, or the user plane configuration corresponding to the bearer type is a configuration set of basic functions and/or parameters, and then the network can be configured by delta (incremental) Change the configuration based on it;
  • the corresponding bearer user plane function cannot support functions such as ARQ (automatic retransmission request) and segmentation, and user plane parameters, such as TTI (Transmission Time Interval), should select a relatively short TTI.
  • ARQ automatic retransmission request
  • TTI Transmission Time Interval
  • the bearer corresponding user plane function can be considered to not support segmentation and concatenation, so that the delay caused by the scheduling interaction between the RLC and the MAC can be avoided.
  • the terminal only needs to know the user plane configuration corresponding to the N types of bearers in a pre-configured manner.
  • Step 502 bearer establishment indication message
  • the network determines whether the terminal needs to establish an uplink and/or downlink bearer. If it needs to be established, send a bearer setup indication message to the terminal, for example, RRC Connection can be used.
  • RRC Connection can be used.
  • Reconfiguration message RRC Connection Reconfiguration Message
  • the bearer setup indication message needs to carry the bearer type indication information, such as the number corresponding to the bearer type. It can also carry the bearer ID and some configuration information unique to the bearer.
  • the bearer setup indication message may be signaling of each protocol layer, such as RRC (Radio Resource Control) signaling, MAC (Media Intervention Control Layer) signaling, or physical layer signaling.
  • RRC Radio Resource Control
  • MAC Media Intervention Control Layer
  • Step 503 Determine a user plane configuration corresponding to the bearer to be established.
  • the terminal can determine the user plane configuration information corresponding to the bearer to be established, according to the bearer type indication information obtained in step 502 and the corresponding relationship between the bearer type and the user plane configuration determined in step 501.
  • Step 504 Perform data transmission corresponding to the bearer.
  • Data transmission is performed between the terminal and the network according to the user plane configuration determined in step 503.
  • the base station does not need to perform header compression when delivering the downlink data corresponding to the bearer.
  • the terminal does not need to decompress the data.
  • the network and the terminal perform user plane data transmission based on the user plane function corresponding to the bearer type. It ensures that the future mobile communication system can perform data transmission management more effectively, reduce the signaling overhead of the bearer configuration, and better support network slicing.
  • the schematic diagram of the bearer type and its corresponding user plane configuration correspondence is sent by broadcast.
  • the specific steps are as follows:
  • Step 601 Determine a bearer type and a corresponding user plane configuration thereof.
  • the network determines the bearer type and the user plane configuration corresponding to the bearer type.
  • the user plane configuration corresponding to the bearer type includes user plane function configuration and/or user plane parameter configuration.
  • the user plane configuration corresponding to the bearer type is a configuration of basic functions and/or parameters of the user plane, or the user plane configuration corresponding to the bearer type is a configuration set of basic functions and/or parameters, and then the network can be configured on the basis of delta. Change configuration;
  • TTI should choose a shorter TTI.
  • the bearer corresponding user plane function can be considered to not support segmentation and concatenation, so that the delay caused by the scheduling interaction between the RLC and the MAC can be avoided.
  • Step 602 bearer type and corresponding user plane configuration indication information
  • the user plane configuration corresponding to the bearer type is determined by the network, and then notified to the terminal by broadcast.
  • a new channel and a new RNTI may be defined for the broadcast, or a periodic broadcast may be performed using a specific resource and a specific channel.
  • Step 603 bearer establishment indication message
  • the network determines whether the terminal needs to establish an uplink and/or downlink bearer. If the establishment is required, the bearer setup indication message is sent to the terminal in a broadcast manner, and the bearer setup indication message needs to carry the bearer type indication information, such as the number corresponding to the bearer type. It can also carry the bearer ID and some configuration information unique to the bearer.
  • the bearer setup indication message may be signaling of each protocol layer, such as RRC signaling, MAC signaling, or physical layer signaling.
  • RRC Radio Resource Control
  • MAC User Data Management
  • physical layer Physical Layer
  • the protocol layer may change, and is no longer called RRC/MAC/physical layer, so it can be directly changed to the protocol layer signaling corresponding to the future mobile communication system.
  • Step 604 Determine a user plane configuration corresponding to the bearer to be established.
  • the terminal can determine the user plane configuration information corresponding to the bearer to be established, according to the bearer type indication information obtained in step 602 and the relationship between the bearer type and the user plane configuration determined in step 1.
  • Step 605 Perform data transmission corresponding to the bearer
  • Data transmission is performed between the terminal and the base station according to the user plane configuration determined in step 603.
  • the base station does not need to perform header compression when delivering the downlink data corresponding to the bearer.
  • the terminal does not need to decompress the data.
  • the network and the terminal perform user plane data transmission based on the user plane function corresponding to the bearer type. It ensures that the future mobile communication system can perform data transmission management more effectively, reduce the signaling overhead of the bearer configuration, and better support network slicing.
  • FIG. 7 a schematic flowchart of a bearer type and a corresponding user plane configuration correspondence relationship sent by using a dedicated signaling manner is shown, and the specific steps are as follows:
  • Step 701 Determine a bearer type and a corresponding user plane configuration.
  • the network determines the bearer type and the user plane configuration corresponding to the bearer type.
  • the user plane configuration corresponding to the bearer includes a user plane function configuration and/or a user plane parameter configuration.
  • the user plane configuration corresponding to the bearer type is a configuration of basic functions and/or parameters of the user plane, or the user plane configuration corresponding to the bearer type is a configuration set of basic functions and/or parameters, and then the network can be configured on the basis of delta. Change the configuration.
  • the URLLC service Take the URLLC service as an example. Because of its high reliability and low latency, the data packets are generally small. Therefore, the corresponding bearer user plane function cannot support functions such as ARQ and segmentation, and user plane parameters, such as TTI, should select a relatively short TTI.
  • the bearer corresponding user plane function can be considered to not support segmentation and concatenation, so that the delay caused by the scheduling interaction between the RLC and the MAC can be avoided.
  • Step 702 bearer type and corresponding user plane configuration indication information
  • the network configures the bearer type and the corresponding user plane configuration indication information to the terminal by using dedicated signaling.
  • the network only needs to notify the N types of bearer and user plane configuration correspondence supported by the terminal capability.
  • the mapping between the bearer type and the user plane configuration may be that the network notifies the terminal after the terminal establishes the RRC connection; or the network notifies the terminal of the type bearer and the user plane configuration relationship before the terminal has the corresponding type bearer to be established.
  • the bearer type and the corresponding user plane configuration indication information and the bearer setup indication message may use the same message or different messages.
  • Step 703 bearer establishment indication message
  • the network determines whether the terminal needs to establish an uplink and/or downlink bearer. If the establishment is required, the bearer setup indication message is sent to the terminal in a broadcast manner, and the bearer setup indication message needs to carry the bearer type indication information, such as the number corresponding to the bearer type. It can also carry the bearer ID and some configuration information unique to the bearer.
  • the bearer setup indication message may be signaling of each protocol layer, such as RRC signaling, MAC signaling. Or physical layer signaling.
  • RRC signaling such as RRC signaling, MAC signaling.
  • MAC signaling such as MAC signaling
  • physical layer signaling such as physical MAC/media interface
  • Step 704 Determine a user plane configuration corresponding to the bearer to be established.
  • the terminal can determine the user plane configuration information corresponding to the bearer to be established, according to the bearer type indication information acquired in step 702 and the relationship between the bearer type and the user plane configuration determined in step 701.
  • Step 705 Perform data transmission corresponding to the bearer
  • Data transmission is performed between the terminal and the base station according to the user plane configuration determined in step 703.
  • the base station does not need to perform header compression when delivering the downlink data corresponding to the bearer.
  • the terminal does not need to decompress the data.
  • the network and the terminal perform user plane data transmission based on the user plane function corresponding to the bearer type. It ensures that the future mobile communication system can perform data transmission management more effectively, reduce the signaling overhead of the bearer configuration, and better support network slicing.
  • an apparatus 800 for data transmission comprising:
  • a first determining module 801 configured to determine a correspondence between a bearer type and a user plane configuration
  • the receiving module 802 is configured to receive the bearer type indication information indicated by the network side, where the bearer type indication information carries the bearer type identifier;
  • the second determining module 803 is configured to determine, according to the bearer type identifier indication carried in the bearer type indication information, and the correspondence between the bearer type indication and the user plane configuration, the user plane configuration corresponding to the bearer to be established;
  • the transmission module 804 is configured to perform data transmission according to the determined user plane configuration.
  • the user plane configuration includes a user plane function configuration and/or a user plane parameter configuration.
  • the user plane configuration corresponding to the bearer type is a configuration of a user plane basic function and/or a parameter
  • the user plane configuration corresponding to the bearer type is a configuration set of user plane basic functions and/or parameters.
  • the configuration set of basic functions and/or parameters may be any one or more of the following: header compression, encryption, integrity protection, segmentation, concatenation, ARQ, HARQ, multiplexing, Qos parameters, scheduling mode, modulation mode , coding method and multiple access method.
  • the user plane configuration includes a manner in which the user plane function divides functions between the centralized processing node and the distributed processing node.
  • the first determining unit is further configured to: according to the service type corresponding to the bearer / or network deployment, determining the correspondence between the bearer type of the bearer and the user plane configuration.
  • the first determining unit is further configured to: determine, by using the pre-configuration information, a correspondence between the bearer type and the user plane configuration.
  • the first determining unit is further configured to: determine, from the pre-configuration information, a correspondence between a bearer type and a user plane configuration corresponding to the terminal capability.
  • the first determining unit is further configured to: obtain a correspondence between the bearer type and the user plane configuration by means of network notification.
  • the first determining unit is further configured to: report the terminal capability; and obtain, by using a network notification, a correspondence between the bearer type and the user plane configuration corresponding to the terminal capability.
  • the user plane configuration corresponding to the bearer type includes one or more of the following: header compression, encryption, integrity protection, segmentation, concatenation, ARQ, HARQ, multiplexing, Qos parameters, scheduling mode, and modulation. Mode, encoding method and multiple access method.
  • the network and the terminal perform user plane data transmission based on the user plane function corresponding to the bearer type. It ensures that the future mobile communication system can perform data transmission management more effectively, reduce the signaling overhead of the bearer configuration, and better support network slicing.
  • a device 900 for data transmission comprising:
  • the third determining module 901 is configured to determine a correspondence between the bearer type and the user plane configuration.
  • the configuration module 902 is configured to configure a bearer type corresponding to the bearer.
  • the sending module 903 is configured to send the bearer type indication information, where the bearer type indication information carries the bearer type identifier;
  • the fourth determining module 904 is configured to determine, according to the bearer type identifier and the corresponding relationship between the bearer type and the user plane configuration, a user plane configuration corresponding to the bearer;
  • the transmission module 905 is configured to perform data transmission according to the determined user plane configuration.
  • the user plane configuration includes a user plane function configuration and/or a user plane parameter configuration.
  • the user plane configuration corresponding to the bearer type is a configuration of a user plane basic function and/or a parameter
  • the user plane configuration corresponding to the bearer type is a configuration set of user plane basic functions and/or parameters.
  • the configuration set of basic functions and/or parameters may be any one or more of the following: header compression, encryption, integrity protection, segmentation, concatenation, ARQ, HARQ, multiplexing, Qos parameters, scheduling mode, modulation mode , coding method and multiple access method.
  • the user plane configuration includes a manner in which the user plane function divides functions between the centralized processing node and the distributed processing node.
  • the third determining module is further configured to: determine, by using the pre-configuration information, a correspondence between the bearer type and the user plane configuration.
  • the device further includes:
  • the notification module is configured to notify the terminal of the correspondence between the bearer type and the user plane configuration by means of network notification.
  • the notification module is further configured to: acquire the terminal capability reported by the terminal, and notify the terminal of the correspondence between the bearer type and the user plane configuration corresponding to the terminal capability by using a network notification manner.
  • the user plane configuration corresponding to the bearer type includes one or more of the following: header compression, encryption, integrity protection, segmentation, concatenation, ARQ, HARQ, multiplexing, Qos parameters, scheduling mode, and modulation. Mode, encoding method and multiple access method.
  • a terminal including:
  • the processor 1004 is configured to read a program in the memory 1105 and perform the following process:
  • Determining a correspondence between the bearer type and the user plane configuration Determining a correspondence between the bearer type and the user plane configuration; receiving the bearer type indication information indicated by the network side, the bearer type identifier carried in the bearer type indication information; and the bearer type identifier and the bearer type carried in the bearer type indication information
  • Corresponding relationship with the user plane configuration determines the user plane configuration corresponding to the bearer; and performs data transmission according to the determined user plane configuration;
  • the transceiver 1001 is configured to receive and transmit data under the control of the processor 1004.
  • bus 1000 may include any number of interconnected buses and bridges, and bus 1000 will include one or more processors represented by processor 1004 and memory represented by memory 1105. The various circuits are linked together. The bus 1000 can also link various other circuits, such as peripherals, voltage regulators, and power management circuits, as is known in the art, and therefore, will not be further described herein.
  • Bus interface 1003 provides an interface between bus 1000 and transceiver 1001.
  • the transceiver 1001 can be an element or a plurality of elements, such as a plurality of receivers and transmitters, providing means for communicating with various other devices on a transmission medium.
  • Data processed by processor 1004 is transmitted over wireless medium via antenna 802. Further, antenna 802 also receives data and transmits the data to processor 1004.
  • the processor 1004 is responsible for managing the bus 1000 and the usual processing, and can also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the first memory 1105 can be used to store data used by the processor 1004 in performing operations.
  • the processor 1004 may be a CPU, an ASIC, an FPGA, or a CPLD.
  • the above uplink contention resources available in the area are: all access devices in an area are reserved as resources for uplink contention transmission.
  • the area is at least an area where the terminal identifier of the active connection state (for example, the Inactive UE ID) is valid, or may be a larger area.
  • the processor 1004 is further configured to determine, according to the service type and/or network deployment corresponding to the bearer, a correspondence between a bearer type of the bearer and a user plane configuration.
  • the processor 1004 is further configured to determine, by using the pre-configuration information, a correspondence between the bearer type and the user plane configuration.
  • the processor 1004 is further configured to determine, from the pre-configuration information, a correspondence between a bearer type and a user plane configuration corresponding to the terminal capability.
  • the processor 1004 is further configured to obtain, by using a network notification, a correspondence between a bearer type and a user plane configuration.
  • the network and the terminal perform user plane data transmission based on the user plane function corresponding to the bearer type. It ensures that the future mobile communication system can perform data transmission management more effectively, reduce the signaling overhead of the bearer configuration, and better support network slicing.
  • a network side device including:
  • the processor 1104 is configured to read a program in the memory 1105 and perform the following process:
  • Determining the corresponding relationship between the bearer type and the user plane configuration Determining the corresponding relationship between the bearer type and the user plane configuration; configuring the bearer type corresponding to the bearer; transmitting the bearer type indication information, where the bearer type indication information carries the bearer type identifier; according to the bearer type, the bearer type, and the user plane configuration
  • the corresponding relationship determines the user plane configuration corresponding to the bearer; data transmission is performed according to the determined user plane configuration.
  • the transceiver 1101 is configured to receive and transmit data under the control of the processor 1104.
  • bus 1100 can include any number of interconnected buses and bridges, and bus 1100 will include one or more processors represented by processor 1104 and memory represented by memory 1105. The various circuits are linked together. The bus 1100 can also link various other circuits such as peripherals, voltage regulators, and power management circuits. They are well known in the art and, therefore, will not be further described herein.
  • Bus interface 1103 provides an interface between bus 1100 and transceiver 1101. The transceiver 1101 can be an element or a plurality of elements, such as a plurality of receivers and transmitters, providing means for communicating with various other devices on a transmission medium. Data processed by processor 1104 is transmitted over wireless medium via antenna 1102. Further, antenna 1102 also receives data and transmits the data to processor 1104.
  • the processor 1104 is responsible for managing the bus 1100 and the usual processing, and can also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the memory 1105 can be used to store data used by the processor 1104 in performing operations.
  • the processor 1104 can be a CPU, an ASIC, an FPGA, or a CPLD.
  • the above user plane configuration includes a user plane function configuration and/or a user plane parameter configuration, and is of course not limited thereto.
  • the user plane configuration corresponding to the bearer type is a configuration of the basic functions and/or parameters of the user plane, or the configuration of the basic plane function and/or parameter corresponding to the user plane configuration is not limited to this.
  • the processor 1104 is further configured to determine, by using the pre-configuration information, a correspondence between the bearer type and the user plane configuration.
  • the user plane configuration corresponding to the bearer type includes one or more of the following: header compression, encryption, integrity protection, segmentation, concatenation, ARQ, HARQ, multiplexing, Qos parameters, scheduling mode, modulation mode, coding mode, and Multiple access method.
  • the network and the terminal perform user plane data transmission based on the user plane function corresponding to the bearer type. It ensures that the future mobile communication system can perform data transmission management more effectively, reduce the signaling overhead of the bearer configuration, and better support network slicing.
  • system and “network” are used interchangeably herein.
  • B corresponding to A means that B is associated with A, and B can be determined from A.
  • determining B from A does not mean that B is only determined based on A, and that B can also be determined based on A and/or other information.
  • the disclosed method and apparatus may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • each functional unit in various embodiments of the present disclosure may be integrated into one processing unit, or each unit may be physically included separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.
  • the above-described integrated unit implemented in the form of a software functional unit can be stored in a computer readable storage medium.
  • the above software functional unit is stored in a storage medium and includes a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network side device, etc.) to perform part of the steps of the transceiving method of the various embodiments of the present disclosure.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, and the program code can be stored. Medium.

Abstract

本公开实施例提供了一种数据传输的方法及装置，该方法包括：终端确定承载类型和用户面配置的对应关系；所述终端接收网络侧指示的承载类型指示信息，所述承载类型指示信息中携带的承载类型标识；所述终端根据所述承载类型指示信息中携带的承载类型标识以及承载类型和用户面配置的对应关系确定承载对应的用户面配置；所述终端根据确定的用户面配置进行数据传输。

Description

数据传输的方法及装置
相关申请的交叉引用
本申请主张于2016年6月30日提交中国专利局、申请号为201610512740.2的优先权，其全部内容据此通过引用并入本申请。
技术领域
本公开涉及通信技术领域，尤其涉及一种数据传输的方法及装置。
背景技术
LTE(Long Term Evolution，长期演进)系统中，空口承载类型只有两类：SRB(Signaling Radio Bearer，信令承载)和DRB(Data Radio Bearer，数据无线承载)。
高层控制信息在空口通过SRB传输；数据信息在空口通过DRB来传输。为了保证网络和终端对于SRB/DRB配置理解的一致性，网络需要通过RRC重配过程(RRC Connection Reconfiguration)针对每个SRB/DRB配置该承载对应的参数。
SRB相关主要配置参数包括：
srb-Identity：SRB对应的标识，比如SRB编号；
Rlc-Config：SRB对应的RLC层配置；
logicalChannelConfig：指示SRB的逻辑信道配置。
DRB相关主要配置参数包括：
eps-BearerIdentity：DRB对应的EPS承载标识，比如EPS承载编号
drb-Identity：DRB对应的DRB标识，比如DRB编号；
pdcp-Config：DRB对应的PDCP层配置；
rlc-Config：DRB对应的RLC层配置；
logicalChannelIdentity：DRB对应的逻辑信道标识；
logicalChannelConfig：DRB对应的逻辑信道配置。
2)未来移动通信系统设计思路
未来移动通信系统主要有三类业务：
eMBB(enhanced Mobile Broadband，增强型宽带通信)
mMTC(massive Machine Type Communications，大量机器类型通信)
URLLC(Ultra-Reliable and Low Latency Communications，高可靠低时延通信)
超密集组网是未来移动通信系统发展的一个趋势，在超密集组网情况下，为了实现对大量分布式处理节点的统一控制面管理，需要将部分协议功能进行集中式处理。这样就形成了集中处理节点和分布式处理节点的双层结构，分布式处理节点也称为TRP(Transmission Reception Point，发送接收节点)。对于集中处理节点，根据功能不同，又可以进一步划分为集中处理节点的控制面和集中处理节点的用户面。
对于未来的移动通信系统，其支持多种业务，并且采用集中处理节点和分布式处理节点的双层结构。在这种情况下如何进行有效的数据传输管理，以降低系统信令开销需要考虑。
发明内容
鉴于上述技术问题，本公开实施例提供一种数据传输的方法及装置，用于保证未来移动通信系统可以更有效的进行数据传输管理，降低系统信令开销。
依据本公开实施例的一个方面，提供了一种数据传输的方法，包括：
终端确定承载类型和用户面配置的对应关系；
所述终端接收网络侧指示的承载类型指示信息，所述承载类型指示信息中携带的承载类型标识；
所述终端根据所述承载类型指示信息中携带的承载类型标识以及承载类型和用户面配置的对应关系确定承载对应的用户面配置；
所述终端根据确定的用户面配置进行数据传输。
可选地，所述用户面配置包括用户面功能配置和/或用户面参数配置。
可选地，所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置，或者所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置集合。
可选地，所述用户面配置包括用户面功能在集中处理节点和分布式处理节点之间功能划分的方式。
可选地，确定承载类型和用户面配置的对应关系，包括：
所述终端根据所述承载对应的业务类型和/或网络部署，确定所述承载的承载类型和用户面配置的对应关系。
可选地，所述终端确定承载类型和用户面配置的对应关系，包括：
所述终端通过预配置信息确定承载类型和用户面配置的对应关系。
可选地，所述终端通过预配置信息确定承载类型和用户面配置的对应关系，包括：
所述终端从所述预配置信息中确定与终端能力对应的承载类型和用户面配置的对应关系。
可选地，所述终端确定承载类型和用户面配置的对应关系，包括：
所述终端通过网络通知的方式获取承载类型和用户面配置的对应关系。
可选地，所述终端通过网络通知的方式获取承载类型和用户面配置的对应关系，包括：
所述终端上报终端能力；
所述终端通过网络通知的方式获取与所述终端能力对应的承载类型和用户面配置的对应关系。
可选地，所述承载类型对应的用户面配置包括以下一项或多项：头压缩、加密、完整性保护、分段、串接、ARQ、HARQ、复用、Qos参数、调度方式、调制方式、编码方式和多址方式。
依据本公开实施例的另一个方面，还提供了一种数据传输的方法，所述方法包括：
网络侧设备确定承载类型和用户面配置的对应关系；
所述网络侧设备配置承载对应的承载类型；
所述网络侧设备发送承载类型指示信息，所述承载类型指示信息中携带所述承载类型标识；
所述网络侧设备根据所述承载类型标识以及承载类型和用户面配置的对 应关系确定承载对应的用户面配置；
所述网络侧设备根据确定的用户面配置进行数据传输。
可选地，所述用户面配置包括用户面功能配置和/或用户面参数配置。
可选地，所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置，或者所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置集合。
可选地，所述用户面配置包括用户面功能在集中处理节点和分布式处理节点之间功能划分的方式。
可选地，所述网络侧设备确定承载类型和用户面配置的对应关系，包括：
所述网络侧设备通过预配置信息确定承载类型和用户面配置的对应关系。
可选地，所述方法还包括：
网络侧设备通过网络通知的方式通知终端所述承载类型和用户面配置的对应关系。
可选地，网络侧设备通过网络通知的方式通知终端所述承载类型和用户面配置的对应关系，包括：
所述网络侧设备获取所述终端上报的终端能力；
所述网络侧设备通过网络通知的方式向所述终端通知与所述终端能力对应的承载类型和用户面配置的对应关系。
可选地，所述承载类型对应的用户面配置包括以下一项或多项：头压缩、加密、完整性保护、分段、串接、ARQ、HARQ、复用、Qos参数、调度方式、调制方式、编码方式和多址方式。
依据本公开实施例的第三个方面，还提供了一种数据传输的装置，包括：
第一确定模块，用于确定承载类型和用户面配置的对应关系；
接收模块，用于接收网络侧指示的承载类型指示信息，所述承载类型指示信息中携带的承载类型标识；
第二确定模块，用于根据所述承载类型指示信息中携带的承载类型标识指示以及承载类型指示和用户面配置的对应关系确定要建立的该承载对应的用户面配置；
传输模块，用于根据确定的用户面配置进行数据传输。
可选地，所述用户面配置包括用户面功能配置和/或用户面参数配置。
可选地，所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置，或者所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置集合。
可选地，所述用户面配置包括用户面功能在集中处理节点和分布式处理节点之间功能划分的方式。
可选地，所述第一确定单元进一步用于：根据所述承载对应的业务类型和/或网络部署，确定所述承载的承载类型和用户面配置的对应关系。
可选地，所述第一确定单元进一步用于：通过预配置信息确定承载类型和用户面配置的对应关系。
可选地，所述第一确定单元进一步用于：从所述预配置信息中确定与终端能力对应的承载类型和用户面配置的对应关系。
可选地，所述第一确定单元进一步用于：通过网络通知的方式获取承载类型和用户面配置的对应关系。
可选地，所述第一确定单元进一步用于：上报终端能力；通过网络通知的方式获取与所述终端能力对应的承载类型和用户面配置的对应关系。
可选地，所述承载类型对应的用户面配置包括以下一项或多项：头压缩、加密、完整性保护、分段、串接、ARQ、HARQ、复用、Qos参数、调度方式、调制方式、编码方式和多址方式。
依据本公开实施例的第四个方面，还提供了一种数据传输的装置，所述装置包括：
第三确定模块，用于确定承载类型和用户面配置的对应关系；
配置模块，用于配置承载对应的承载类型；
发送模块，用于发送承载类型指示信息，所述承载类型指示信息中携带所述承载类型标识；
第四确定模块，用于根据所述承载类型标识以及承载类型和用户面配置的对应关系确定承载对应的用户面配置；
传输模块，用于根据确定的用户面配置进行数据传输。
可选地，所述用户面配置包括用户面功能配置和/或用户面参数配置。
可选地，所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置，或者所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置集合。
可选地，所述用户面配置包括用户面功能在集中处理节点和分布式处理节点之间功能划分的方式。
可选地，所述第三确定模块进一步用于：通过预配置信息确定承载类型和用户面配置的对应关系。
可选地，所述装置还包括：
通知模块，用于通过网络通知的方式通知终端所述承载类型和用户面配置的对应关系。
可选地，所述通知模块进一步用于：获取所述终端上报的终端能力；通过网络通知的方式向所述终端通知与所述终端能力对应的承载类型和用户面配置的对应关系。
可选地，所述承载类型对应的用户面配置包括以下一项或多项：头压缩、加密、完整性保护、分段、串接、ARQ、HARQ、复用、Qos参数、调度方式、调制方式、编码方式和多址方式。
依据本公开实施例的第五个方面，还提供了一种终端，包括：处理器、存储器和收发机，其中
所述存储器，用于存储所述处理器在执行操作时所使用的指令；
所述处理器，用于确定承载类型和用户面配置的对应关系；
所述收发机，用于接收网络侧指示的承载类型指示信息，所述承载类型指示信息中携带承载类型标识；
所述处理器，还用于根据所述承载类型指示信息中携带的承载类型标识以及承载类型和用户面配置的对应关系确定承载对应的用户面配置；
依据本公开实施例的第六个方面，还提供了一种网络侧设备，包括：处理器、存储器和收发机，
所述存储器，用于存储所述处理器在执行操作时所使用的指令；
所述处理器，用于确定承载类型和用户面配置的对应关系；
所述收发机，用于发送承载类型指示信息，所述承载类型指示信息中携带承载类型标识；
所述处理器，还用于根据所述承载类型标识以及承载类型和用户面配置的对应关系确定承载对应的用户面配置；
所述收发机，还用于根据确定的用户面配置进行数据传输。
上述技术方案中的一个技术方案具有如下优点或有益效果：网络和终端基于承载类型对应的用户面功能进行用户面数据传输，从而可以保证未来移动通信系统可以更有效的进行数据传输管理，降低承载配置的信令开销，可以更好的支持网络切片。
附图说明
图1为未来移动通信系统的网络架构示意图；
图2为相关技术中的集中处理节点和分布式处理节点之间用户面协议层分离示意图；
图3为本公开实施例中数据传输的方法的流程图；
图4为本公开实施例中数据传输的方法的流程图；
图5为本公开实施例中预配置承载类型及其对应的用户面配置的示意图；
图6为本公开实施例中承载类型及其对应的用户面配置对应关系通过广播方式发送的示意图；
图7为本公开实施例中承载类型及其对应的用户面配置对应关系通过专用信令方式发送的示意图；
图8为本公开实施例中数据传输的装置的框图；
图9为本公开实施例中数据传输的装置的框图；
图10为本公开实施例中数据传输的装置的框图；
图11为本公开实施例中数据传输的装置的框图。
具体实施方式
下面将参照附图更详细地描述本公开的示例性实施例。虽然附图中显示了 本公开的示例性实施例，然而应当理解，可以以各种形式实现本公开而不应被这里阐述的实施例所限制。相反，提供这些实施例是为了能够更透彻地理解本公开，并且能够将本公开的范围完整的传达给本领域的技术人员。
本领域技术人员知道，本公开的实施方式可以实现为一种系统、装置、设备、方法或计算机程序产品。因此，本公开的实施例可以具体实现为以下形式：完全的硬件、完全的软件(包括固件、驻留软件、微代码等)，或者硬件和软件结合的形式。
图1示出了，未来移动通信系统的网络架构示意图。在相关技术中，对于用户面处理，可能会在集中处理节点和分布式处理节点之间对用户面功能进行划分，目前，用户面协议层分离方案有五种(Option 1-Option 5)，参见图2。
根据本公开的实施方式，提出了一种数据传输的方法及装置。
参见图3，图中示出了一种数据传输的方法，具体步骤如下：
步骤301、终端确定承载类型和用户面配置的对应关系，然后进入步骤302；
针对功能配置和/或参数配置，上述用户面配置可以包括：用户面功能配置和/或用户面参数配置，当然也并不限于此。
当然，针对功能划分方式，上述用户面配置可以包括用户面功能在集中处理节点和分布式处理节点之间功能划分的方式，当然也并不限于此。
在本实施例中，承载类型可以对应于业务类型，例如eMBB、mMTC、URLLC等。上述所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置，或者承载类型对应的用户面配置是用户面基本功能和/或参数的配置集合，当然也并不限于此。
需要说明的是，网络侧可以通过delta(变量)配置在上述承载类型基础上变更配置。以URLLC业务为例，由于其要求高可靠、低时延，且数据包一般都比较小。因此其对应的承载用户面功能不能支持ARQ(自动重传请求)、分段等功能，用户面参数，比如TTI(Transmission Time Interval，传输时间间隔)要选择比较短的TTI。以用户面协议栈分离方案Option3为例(见图2)，由于集中处理节点和分布式处理节点之间是非理想链路，会有一定时延，因此如果该承载对应的是URLLC业务，那么该承载对应的用户面功能可以考虑不支持分段、串接，这样就可以避免RLC和MAC之间调度交互导致的时延。
上述承载类型对应的用户面配置包括以下一项或多项：头压缩、加密、完整性保护、分段、串接、ARQ(AutomaticRepeatreQuest，自动请求回复)、HARQ(Hybrid Automatic Repeat reQuest，混合自动重传请求)、复用、Qos(Quality of Service，服务质量)参数、调度方式、调制方式、编码方式和多址方式等。需要说明的是，上述例举的用户配置包括的一项或多项可以是用户面基本功能和/或参数的配置集合，当然也并不限于上述举例。
在本实施例中，终端确定承载类型对应的用户面配置时可以考虑承载对应的业务类型、网络部署等因素。
在本实施例中，终端可采用以下三种方式确定承载类型和用户面配置的对应关系：
可选方式一：预配置
例如：在协议中约定每个承载类型对应的用户面配置的对应关系。
可选方式二：网络通过广播方式通知承载类型和用户面配置的对应关系
例如：由网络确定承载类型对应的用户面配置，然后通过广播方式通知给终端。具体的，可以为该广播定义新的信道和新的RNTI(无线网络临时标识)，也可以是使用特定资源和特定信道进行周期性广播。
可选方式三：网络通过专用信令方式通知承载类型和用户面配置的对应关系
例如：终端和网络建立RRC连接后，由网络通过专用信令方式将方式通知承载类型和用户面配置的对应关系给终端。
需要说明的是，上述提及的承载类型和用户面配置通知方式可以基于终端能力做优化。具体如下：
如果终端能力仅支持N种承载类型，则终端只需要通过预配置或者网络通知方式获知这N种承载类型对应的用户面配置即可；
终端能力上报时需要携带支持的承载类型指示信息或者业务类型指示信息。网络侧可以根据终端业务类型指示信息，从该业务类型指示信息对应的承载类型中选择一个承载类型配置给终端。
同样需要说明的是，上述提及的承载类型和用户面配置通知方式可以基于终端实际使用的承载类型做优化。具体如下：
如果通过广播或者专用信令方式通知承载类型和用户面配置通知方式，那么网络可以在终端某个承载类型的承载即将建立时通知该承载类型对应的用户面配置。可选地，对于同一类型的承载，该承载类型和用户面配置对应关系只需要通知一次。
需要说明的是，如果未来接入网引入网络切片概念，那么还可以将承载和网络切片做映射，将承载标识信息替换为网络切片标识信息。承载和用户面配置对应关系替换为网络切换和用户面配置的对应关系。
步骤302、终端接收网络侧指示的承载类型指示信息，承载类型指示信息中携带的承载类型标识，然后进入步骤303；
上述网络侧可以是指网络侧控制面处理单元，当然也并不限于此。可选地，网络侧在根据需要建立的承载配置与该承载对应的承载类型之后，网络侧向终端发送承载类型指示信息。
步骤303、终端根据承载类型指示信息中携带的承载类型标识以及承载类型和用户面配置的对应关系确定承载对应的用户面配置，然后进入步骤304；
上述承载类型标识也可称为承载类型对应的编号，当然也并不限于此。
步骤304、终端根据确定的用户面配置进行数据传输。
以上行为例，如果该承载对应的用户面功能不包含头压缩，那么终端在发送该承载对应的上行数据时不需要进行头压缩。基站接收到该数据也不需要进行解压缩，其他用户面配置的处理方式与此类似，在此不再敷述。
在本实施例中，网络和终端基于承载类型对应的用户面功能进行用户面数据传输。保证未来移动通信系统可以更有效的进行数据传输管理，降低承载配置的信令开销，可以更好的支持网络切片。
参见图4，图中示出了一种数据传输的方法，具体步骤如下：
步骤401、网络侧设备确定承载类型和用户面配置的对应关系，然后进入步骤402；
可选地，网络侧设备通过预配置信息确定承载类型和用户面配置的对应关系，例如在协议中约定每个承载类型对应的用户面配置。
上述网络侧设备可以是网络侧控制面处理单元，比如对于图2中的网络架构，对应的是集中处理单元。
针对功能配置和/或参数配置，上述用户面配置可以包括：用户面功能配置和/或用户面参数配置，当然也并不限于此。
当然，针对功能划分方式，上述用户面配置可以包括用户面功能在集中处理节点和分布式处理节点之间功能划分的方式，当然也并不限于此。
比如承载类型N，对应图2用户面功能在集中处理节点和分布式处理节点之间的划分的某种划分方式，比如option2。而另一种承载类型M，则对应不同的户面功能在集中处理节点和分布式处理节点之间的划分方式。
在本实施例中，承载类型可以对应于业务类型，例如eMBB、mMTC、URLLC等。上述承载类型对应的用户面配置是用户面基本功能和/或参数的配置，或者承载类型对应的用户面配置是基本功能和/或参数的配置集合，当然也并不限于此。需要说明的是，网络可以通过delta(变量)配置在上述承载类型基础上变更配置。以URLLC业务为例，由于其要求高可靠、低时延，且数据包一般都比较小。因此其对应的承载用户面功能不能支持ARQ(自动重传请求)、分段等功能，用户面参数，比如TTI(Transmission Time Interval，传输时间间隔)要选择比较短的TTI。以用户面协议栈分离方案Option3为例(见图2)，由于集中处理节点和分布式处理节点之间是非理想链路，会有一定时延，因此如果该承载对应的是URLLC业务，那么该承载对应的用户面功能可以考虑不支持分段、串接，这样就可以避免RLC和MAC之间调度交互导致的时延。
上述承载类型对应的用户面配置包括以下一项或多项：头压缩、加密、完整性保护、分段、串接、ARQ(AutomaticRepeatreQuest，自动请求回复)、HARQ(Hybrid Automatic Repeat reQuest，混合自动重传请求)、复用、QoS参数、调度方式、调制方式、编码方式和多址方式等。
若终端需要采用网络通知的方式获取承载类型和用户面配置的对应关系，在上述步骤401之后，网络侧设备可以通过网络通知的方式通知终端所述承载类型和用户面配置的对应关系，网络通知的方式可以是广播通知的方式或者专用信令通知的方式，例如：由网络确定承载类型对应的用户面配置，然后通过广播方式通知给终端。具体的，可以为该广播定义新的信道和新的RNTI(无线网络临时标识)，也可以是使用特定资源和特定信道进行周期性广播。又例 如：终端和网络建立RRC连接后，由网络通过专用信令方式将方式通知承载类型和用户面配置的对应关系给终端。
需要说明的是，上述提及的承载类型和用户面配置通知方式可以基于终端能力做优化。具体如下：
如果终端能力仅支持N种承载类型，则终端只需要通过预配置或者网络通知方式获知这N种承载类型对应的用户面配置即可；
终端能力上报时需要携带支持的承载类型指示信息或者业务类型指示信息。网络侧可以根据终端业务类型指示信息，从该业务类型指示信息对应的承载类型中选择一个承载类型配置给终端。
同样需要说明的是，上述提及的承载类型和用户面配置通知方式可以基于终端实际使用的承载类型做优化。具体如下：
如果通过广播或者专用信令方式通知承载类型和用户面配置通知方式，那么网络可以在终端某个承载类型的承载即将建立时通知该承载类型对应的用户面配置。可选地，对于同一类型的承载，该承载类型和用户面配置对应关系只需要通知一次。
需要说明的是，如果未来接入网引入网络切片概念，那么还可以将承载和网络切片做映射，将承载标识信息替换为网络切片标识信息。承载和用户面配置对应关系替换为网络切换和用户面配置的对应关系。
步骤402、网络侧设备配置承载对应的承载类型，然后进入步骤403；
可选地，网络侧设备可以根据终端业务类型指示信息，从该业务类型指示信息对应的承载类型中选择一个承载类型配置给终端。
步骤403、所述网络侧设备发送承载类型指示信息，所述承载类型指示信息中携带所述承载类型标识，然后进入步骤404；
上述承载类型标识也可称为承载类型对应的编号，当然也并不限于此。
步骤404、网络侧设备根据所述承载类型标识以及承载类型和用户面配置的对应关系确定承载对应的用户面配置，然后进入步骤405；
步骤405、网络侧设备根据确定的用户面配置进行数据传输。
以下行为例，如果该承载对应的用户面功能不包含头压缩，那么基站在下发该承载对应的下行数据时不需要进行头压缩。终端接收到该数据也不需要进 行解压缩，其他用户面配置的处理方式与此类似，在此不再敷述。
在本实施例中，网络和终端基于承载类型对应的用户面功能进行用户面数据传输。保证未来移动通信系统可以更有效的进行数据传输管理，降低承载配置的信令开销，可以更好的支持网络切片。
示例性地，参见图5，图中示出了预配置承载类型及其对应的用户面配置的流程，具体步骤如下：
步骤501、确定承载类型及其对应的用户面配置；
网络和终端分别根据预配置信息确定承载类型和该承载类型对应的用户面配置。预配置信息可以是在协议中约定的默认配置，也可以是预配置在基站和终端中的配置信息。
承载类型对应的用户面配置包括用户面功能配置和/或用户面参数配置。确定承载类型对应的用户面配置时需要考虑承载对应的业务类型、网络部署等因素。
所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置，或者承载类型对应的用户面配置是基本功能和/或参数的配置集合，然后网络可以通过delta(增量)配置在其基础上变更配置；
以URLLC业务为例，由于其要求高可靠、低时延，且数据包一般都比较小。因此其对应的承载用户面功能不能支持ARQ(自动重传请求)、分段等功能，用户面参数，比如TTI(Transmission Time Interval，传输时间间隔)要选择比较短的TTI。
以用户面协议栈分离方案Option3为例(见图2)，由于集中处理节点和分布式处理节点之间是非理想链路，会有一定时延，因此如果该承载对应的是URLLC业务，那么该承载对应的用户面功能可以考虑不支持分段、串接，这样就可以避免RLC和MAC之间调度交互导致的时延。
作为优化，如果终端能力仅支持N种承载类型，则终端只需要通过预配置方式获知这N种承载类型对应的用户面配置即可。
步骤502：承载建立指示消息；
终端接入网络后，由网络确定终端是否需要建立上行和/或下行承载。如果需要建立，则向终端发送承载建立指示消息，比如可以使用RRC Connection  Reconfiguration消息(RRC连接重配消息)。承载建立指示消息中需要携带承载类型指示信息，比如承载类型对应的编号。还可以携带承载ID以及该承载特有的一些配置信息。
承载建立指示消息可以是各个协议层的信令，比如RRC(Radio Resource Control，无线资源控制协议)信令、MAC(媒体介入控制层)信令或者物理层信令。当然未来移动通信系统，协议层可能变化，不再叫RRC/MAC/物理层，那么直接改成未来移动通信系统对应的协议层信令即可。
步骤503：确定要建立的承载对应的用户面配置；
终端根据步骤502中获取的承载类型指示信息以及步骤501中确定的承载类型和用户面配置的对应关系，就可以确定要建立的承载对应的用户面配置信息。
步骤504：进行承载对应的数据传输；
终端和网络之间根据步骤503确定的用户面配置进行数据传输。以下行为例，如果该承载对应的用户面功能不包含头压缩，那么基站在下发该承载对应的下行数据时不需要进行头压缩。终端接收到该数据也不需要进行解压缩。
在本实施例中，网络和终端基于承载类型对应的用户面功能进行用户面数据传输。保证未来移动通信系统可以更有效的进行数据传输管理，降低承载配置的信令开销，可以更好的支持网络切片。
示例性地，参见图6，图中示出了承载类型及其对应的用户面配置对应关系通过广播方式发送的示意图，具体步骤如下：
步骤601：确定承载类型及其对应的用户面配置；
网络确定承载类型和该承载类型对应的用户面配置。承载类型对应的用户面配置包括用户面功能配置和/或用户面参数配置。确定承载类型对应的用户面配置时需要考虑承载对应的业务类型、网络部署等因素。
所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置，或者承载类型对应的用户面配置是基本功能和/或参数的配置集合，然后网络可以通过delta配置在其基础上变更配置；
以URLLC业务为例，由于其要求高可靠、低时延，且数据包一般都比较小。因此其对应的承载用户面功能不能支持ARQ、分段等功能，用户面参数， 比如TTI要选择比较短的TTI。
以用户面协议栈分离方案Option3为例(见图2)，由于集中处理节点和分布式处理节点之间是非理想链路，会有一定时延，因此如果该承载对应的是URLLC业务，那么该承载对应的用户面功能可以考虑不支持分段、串接，这样就可以避免RLC和MAC之间调度交互导致的时延。
步骤602：承载类型和对应的用户面配置指示信息
即由网络确定承载类型对应的用户面配置，然后通过广播方式通知给终端。具体的，可以为该广播定义新的信道和新的RNTI(无线网络临时标识)，也可以是使用特定资源和特定信道进行周期性广播。
步骤603：承载建立指示消息；
终端接入网络后，由网络确定终端是否需要建立上行和/或下行承载。如果需要建立，则向终端以广播方式发送承载建立指示消息，承载建立指示消息中需要携带承载类型指示信息，比如承载类型对应的编号。还可以携带承载ID以及该承载特有的一些配置信息。
承载建立指示消息可以是各个协议层的信令，比如RRC信令、MAC信令或者物理层信令。当然未来移动通信系统，协议层可能变化，不再叫RRC/MAC/物理层，那么直接改成未来移动通信系统对应的协议层信令即可。
步骤604：确定要建立的承载对应的用户面配置；
终端根据步骤602中获取的承载类型指示信息以及步骤1中确定的承载类型和用户面配置的关系，就可以确定要建立的承载对应的用户面配置信息。
步骤605：进行承载对应的数据传输
终端和基站之间根据步骤603确定的用户面配置进行数据传输。以下行为例，如果该承载对应的用户面功能不包含头压缩，那么基站在下发该承载对应的下行数据时不需要进行头压缩。终端接收到该数据也不需要进行解压缩。
在本实施例中，网络和终端基于承载类型对应的用户面功能进行用户面数据传输。保证未来移动通信系统可以更有效的进行数据传输管理，降低承载配置的信令开销，可以更好的支持网络切片。
示例性地，参见图7，图中示出了承载类型及其对应的用户面配置对应关系通过专用信令方式发送的流程示意图，具体步骤如下：
步骤701：确定承载类型及其对应的用户面配置；
网络确定承载类型和该承载类型对应的用户面配置。承载对应的用户面配置包括用户面功能配置和/或用户面参数配置。确定承载类型对应的用户面配置时需要考虑承载对应的业务类型、网络部署等因素。
所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置，或者承载类型对应的用户面配置是基本功能和/或参数的配置集合，然后网络可以通过delta配置在其基础上变更配置。
以URLLC业务为例，由于其要求高可靠、低时延，且数据包一般都比较小。因此其对应的承载用户面功能不能支持ARQ、分段等功能，用户面参数，比如TTI要选择比较短的TTI。
以用户面协议栈分离方案Option3为例(见图2)，由于集中处理节点和分布式处理节点之间是非理想链路，会有一定时延，因此如果该承载对应的是URLLC业务，那么该承载对应的用户面功能可以考虑不支持分段、串接，这样就可以避免RLC和MAC之间调度交互导致的时延。
步骤702：承载类型和对应的用户面配置指示信息；
即终端和网络建立RRC连接后，由网络通过专用信令将承载类型和对应的用户面配置指示信息配置给终端。
作为优化，如果终端能力仅支持N种承载类型，则网络只需要通知终端能力支持的N种承载和用户面配置对应关系即可。
该承载类型和和用户面配置对应关系可以是终端建立RRC连接后网络即通知终端；也可以是终端有对应类型承载要建立之前，网络再将该类型承载和用户面配置关系通知给终端。对于后者，承载类型和对应的用户面配置指示信息和承载建立指示消息可以使用同一条消息或者不同消息。
步骤703：承载建立指示消息；
终端接入网络后，由网络确定终端是否需要建立上行和/或下行承载。如果需要建立，则向终端以广播方式发送承载建立指示消息，承载建立指示消息中需要携带承载类型指示信息，比如承载类型对应的编号。还可以携带承载ID以及该承载特有的一些配置信息。
承载建立指示消息可以是各个协议层的信令，比如RRC信令、MAC信令 或者物理层信令。当然未来移动通信系统，协议层可能变化，不再叫RRC/MAC/物理层，那么直接改成未来移动通信系统对应的协议层信令即可。
步骤704：确定要建立的承载对应的用户面配置；
终端根据步骤702中获取的承载类型指示信息以及步骤701中确定的承载类型和用户面配置的关系，就可以确定要建立的承载对应的用户面配置信息。
步骤705：进行承载对应的数据传输
终端和基站之间根据步骤703确定的用户面配置进行数据传输。以下行为例，如果该承载对应的用户面功能不包含头压缩，那么基站在下发该承载对应的下行数据时不需要进行头压缩。终端接收到该数据也不需要进行解压缩。
在本实施例中，网络和终端基于承载类型对应的用户面功能进行用户面数据传输。保证未来移动通信系统可以更有效的进行数据传输管理，降低承载配置的信令开销，可以更好的支持网络切片。
参见图8，图中示出了一种数据传输的装置800，包括：
第一确定模块801，用于确定承载类型和用户面配置的对应关系；
接收模块802，用于接收网络侧指示的承载类型指示信息，所述承载类型指示信息中携带的承载类型标识；
第二确定模块803，用于根据所述承载类型指示信息中携带的承载类型标识指示以及承载类型指示和用户面配置的对应关系确定要建立的该承载对应的用户面配置；
传输模块804，用于根据确定的用户面配置进行数据传输。
可选地，所述用户面配置包括用户面功能配置和/或用户面参数配置。
可选地，所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置，或者所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置集合。例如基本功能和/或参数的配置集合可以是以下任意一种或多种：头压缩、加密、完整性保护、分段、串接、ARQ、HARQ、复用、Qos参数、调度方式、调制方式、编码方式和多址方式。
可选地，所述用户面配置包括用户面功能在集中处理节点和分布式处理节点之间功能划分的方式。
可选地，所述第一确定单元进一步用于：根据所述承载对应的业务类型和 /或网络部署，确定所述承载的承载类型和用户面配置的对应关系。
可选地，所述第一确定单元进一步用于：通过预配置信息确定承载类型和用户面配置的对应关系。
可选地，所述第一确定单元进一步用于：从所述预配置信息中确定与终端能力对应的承载类型和用户面配置的对应关系。
可选地，所述第一确定单元进一步用于：通过网络通知的方式获取承载类型和用户面配置的对应关系。
可选地，所述第一确定单元进一步用于：上报终端能力；通过网络通知的方式获取与所述终端能力对应的承载类型和用户面配置的对应关系。
可选地，所述承载类型对应的用户面配置包括以下一项或多项：头压缩、加密、完整性保护、分段、串接、ARQ、HARQ、复用、Qos参数、调度方式、调制方式、编码方式和多址方式。
在本实施例中，网络和终端基于承载类型对应的用户面功能进行用户面数据传输。保证未来移动通信系统可以更有效的进行数据传输管理，降低承载配置的信令开销，可以更好的支持网络切片。
参见图9，图中示出了一种数据传输的装置900，包括：
第三确定模块901，用于确定承载类型和用户面配置的对应关系；
配置模块902，用于配置承载对应的承载类型；
发送模块903，用于发送承载类型指示信息，所述承载类型指示信息中携带所述承载类型标识；
第四确定模块904，用于根据所述承载类型标识以及承载类型和用户面配置的对应关系确定承载对应的用户面配置；
传输模块905，用于根据确定的用户面配置进行数据传输。
可选地，所述用户面配置包括用户面功能配置和/或用户面参数配置。
可选地，所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置，或者所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置集合。例如基本功能和/或参数的配置集合可以是以下任意一种或多种：头压缩、加密、完整性保护、分段、串接、ARQ、HARQ、复用、Qos参数、调度方式、调制方式、编码方式和多址方式。
可选地，所述用户面配置包括用户面功能在集中处理节点和分布式处理节点之间功能划分的方式。
可选地，所述第三确定模块进一步用于：通过预配置信息确定承载类型和用户面配置的对应关系。
可选地，所述装置还包括：
通知模块，用于通过网络通知的方式通知终端所述承载类型和用户面配置的对应关系。
可选地，所述通知模块进一步用于：获取所述终端上报的终端能力；通过网络通知的方式向所述终端通知与所述终端能力对应的承载类型和用户面配置的对应关系。
可选地，所述承载类型对应的用户面配置包括以下一项或多项：头压缩、加密、完整性保护、分段、串接、ARQ、HARQ、复用、Qos参数、调度方式、调制方式、编码方式和多址方式。
参见图10，图中示出了一种终端，包括：
处理器1004，用于读取存储器1105中的程序，执行下列过程：
确定承载类型和用户面配置的对应关系；接收网络侧指示的承载类型指示信息，所述承载类型指示信息中携带的承载类型标识；根据所述承载类型指示信息中携带的承载类型标识以及承载类型和用户面配置的对应关系确定承载对应的用户面配置；根据确定的用户面配置进行数据传输；
收发机1001，用于在处理器1004的控制下接收和发送数据。
在图10中，总线架构(用总线1000来代表)，总线1000可以包括任意数量的互联的总线和桥，总线1000将包括由处理器1004代表的一个或多个处理器和存储器1105代表的存储器的各种电路链接在一起。总线1000还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口1003在总线1000和收发机1001之间提供接口。收发机1001可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经处理器1004处理的数据通过天线802在无线介质上进行传输，进一步，天线802还接收数据并将数据传送给处理器1004。
处理器1004负责管理总线1000和通常的处理，还可以提供各种功能，包括定时，外围接口，电压调节、电源管理以及其他控制功能。而第一存储器1105可以被用于存储处理器1004在执行操作时所使用的数据。
可选的，处理器1004可以是CPU、ASIC、FPGA或CPLD。
上述在区域内可用的上行竞争资源是指：一个区域内的所有接入设备都预留作为上行竞争传输的资源。该区域至少是活跃连接态的终端标识(例如Inactive UE ID)有效的区域，也可以是个更大的区域。
可选地，处理器1004，还用于根据所述承载对应的业务类型和/或网络部署，确定所述承载的承载类型和用户面配置的对应关系。
可选地，处理器1004，还用于通过预配置信息确定承载类型和用户面配置的对应关系。
可选地，处理器1004，还用于从所述预配置信息中确定与终端能力对应的承载类型和用户面配置的对应关系。
可选地，处理器1004，还用于通过网络通知的方式获取承载类型和用户面配置的对应关系。
在本实施例中，网络和终端基于承载类型对应的用户面功能进行用户面数据传输。保证未来移动通信系统可以更有效的进行数据传输管理，降低承载配置的信令开销，可以更好的支持网络切片。
参见图11，图中示出了一种网络侧设备，包括：
处理器1104，用于读取存储器1105中的程序，执行下列过程：
确定承载类型和用户面配置的对应关系；配置承载对应的承载类型；发送承载类型指示信息，所述承载类型指示信息中携带所述承载类型标识；根据所述承载类型以及承载类型和用户面配置的对应关系确定承载对应的用户面配置；根据确定的用户面配置进行数据传输。
收发机1101，用于在处理器1104的控制下接收和发送数据。
在图11中，总线架构(用总线1100来代表)，总线1100可以包括任意数量的互联的总线和桥，总线1100将包括由处理器1104代表的一个或多个处理器和存储器1105代表的存储器的各种电路链接在一起。总线1100还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些 都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口1103在总线1100和收发机1101之间提供接口。收发机1101可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经处理器1104处理的数据通过天线1102在无线介质上进行传输，进一步，天线1102还接收数据并将数据传送给处理器1104。
处理器1104负责管理总线1100和通常的处理，还可以提供各种功能，包括定时，外围接口，电压调节、电源管理以及其他控制功能。而存储器1105可以被用于存储处理器1104在执行操作时所使用的数据。
可选的，处理器1104可以是CPU、ASIC、FPGA或CPLD。
上述用户面配置包括用户面功能配置和/或用户面参数配置，当然也并不限于此。
所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置，或者上述承载类型对应用户面配置的是基本功能和/或参数的配置集合，当然也并不限于此。
可选地，处理器1104，还用于通过预配置信息确定承载类型和用户面配置的对应关系。
上述承载类型对应的用户面配置包括以下一项或多项：头压缩、加密、完整性保护、分段、串接、ARQ、HARQ、复用、Qos参数、调度方式、调制方式、编码方式和多址方式。
在本实施例中，网络和终端基于承载类型对应的用户面功能进行用户面数据传输。保证未来移动通信系统可以更有效的进行数据传输管理，降低承载配置的信令开销，可以更好的支持网络切片。
应理解，说明书通篇中提到的“一个实施例”或“一实施例”意味着与实施例有关的特定特征、结构或特性包括在本公开的至少一个实施例中。因此，在整个说明书各处出现的“在一个实施例中”或“在一实施例中”未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。
在本公开的各种实施例中，应理解，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本 公开实施例的实施过程构成任何限定。
另外，本文中术语“系统”和“网络”在本文中常可互换使用。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
在本申请所提供的实施例中，应理解，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
在本申请所提供的几个实施例中，应该理解到，所揭露方法和装置，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理包括，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
上述以软件功能单元的形式实现的集成的单元，可以存储在一个计算机可读取存储介质中。上述软件功能单元存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络侧设备等)执行本公开各个实施例所述收发方法的部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述的是本公开的优选实施方式，应当指出对于本技术领域的普通人员来说，在不脱离本公开所述的原理前提下还可以做出若干改进和润饰，这些 改进和润饰也在本公开的保护范围内。

Claims (32)

  1. 一种数据传输的方法，包括：
    终端确定承载类型和用户面配置的对应关系；
    所述终端接收网络侧指示的承载类型指示信息，所述承载类型指示信息中携带承载类型标识；
    所述终端根据所述承载类型指示信息中携带的承载类型标识以及承载类型和用户面配置的对应关系确定承载对应的用户面配置；
    所述终端根据确定的用户面配置进行数据传输。
  2. 根据权利要求1所述的方法，其中，所述用户面配置包括用户面功能配置和/或用户面参数配置；或者
    所述用户面配置包括用户面功能在集中处理节点和分布式处理节点之间功能划分的方式。
  3. 根据权利要求1所述的方法，其中，所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置，或者所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置集合。
  4. 根据权利要求1所述的方法，其中，所述终端确定承载类型和用户面配置的对应关系，包括：
    所述终端根据所述承载对应的业务类型和/或网络部署，确定所述承载的承载类型和用户面配置的对应关系。
  5. 根据权利要求1所述的方法，其中，所述终端确定承载类型和用户面配置的对应关系，包括：
    所述终端通过预配置信息确定承载类型和用户面配置的对应关系；或者
    所述终端通过网络通知的方式获取承载类型和用户面配置的对应关系。
  6. 根据权利要求5所述的方法，其中，所述终端通过预配置信息确定承载类型和用户面配置的对应关系，包括：
    所述终端从所述预配置信息中确定与终端能力对应的承载类型和用户面配置的对应关系。
  7. 根据权利要求5所述的方法，其中，所述终端通过网络通知的方式获 取承载类型和用户面配置的对应关系，包括：
    所述终端上报终端能力；
    所述终端通过网络通知的方式获取与所述终端能力对应的承载类型和用户面配置的对应关系。
  8. 根据权利要求1所述的方法，其中，所述承载类型对应的用户面配置包括以下一项或多项：头压缩、加密、完整性保护、分段、串接、ARQ、HARQ、复用、Qos参数、调度方式、调制方式、编码方式和多址方式。
  9. 一种数据传输的方法，所述方法包括：
    网络侧设备确定承载类型和用户面配置的对应关系；
    所述网络侧设备配置承载对应的承载类型；
    所述网络侧设备发送承载类型指示信息，所述承载类型指示信息中携带承载类型标识；
    所述网络侧设备根据所述承载类型标识以及承载类型和用户面配置的对应关系确定承载对应的用户面配置；
    所述网络侧设备根据确定的用户面配置进行数据传输。
  10. 根据权利要求9所述的方法，其中，所述用户面配置包括用户面功能配置和/或用户面参数配置；或者
    所述用户面配置包括用户面功能在集中处理节点和分布式处理节点之间功能划分的方式。
  11. 根据权利要求9所述的方法，其中，所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置，或者所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置集合。
  12. 根据权利要求9所述的方法，其中，所述网络侧设备确定承载类型和用户面配置的对应关系，包括：
    所述网络侧设备通过预配置信息确定承载类型和用户面配置的对应关系。
  13. 根据权利要求9所述的方法，其中，所述方法还包括：
    所述网络侧设备通过网络通知的方式通知终端所述承载类型和用户面配置的对应关系。
  14. 根据权利要求13所述的方法，其中，所述网络侧设备通过网络通知 的方式通知终端所述承载类型和用户面配置的对应关系，包括：
    所述网络侧设备获取所述终端上报的终端能力；
    所述网络侧设备通过网络通知的方式向所述终端通知与所述终端能力对应的承载类型和用户面配置的对应关系。
  15. 根据权利要求9所述的方法，其中，所述承载类型对应的用户面配置包括以下一项或多项：头压缩、加密、完整性保护、分段、串接、ARQ、HARQ、复用、Qos参数、调度方式、调制方式、编码方式和多址方式。
  16. 一种数据传输的装置，包括：
    第一确定模块，用于确定承载类型和用户面配置的对应关系；
    接收模块，用于接收网络侧指示的承载类型指示信息，所述承载类型指示信息中携带承载类型标识；
    第二确定模块，用于根据所述承载类型指示信息中携带的承载类型标识指示以及承载类型指示和用户面配置的对应关系确定要建立的该承载对应的用户面配置；
    传输模块，用于根据确定的用户面配置进行数据传输。
  17. 根据权利要求16所述的装置，其中，所述用户面配置包括用户面功能配置和/或用户面参数配置；或者
    所述用户面配置包括用户面功能在集中处理节点和分布式处理节点之间功能划分的方式。
  18. 根据权利要求16所述的装置，其中，所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置，或者所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置集合。
  19. 根据权利要求16所述的装置，其中，所述第一确定单元进一步用于：根据所述承载对应的业务类型和/或网络部署，确定所述承载的承载类型和用户面配置的对应关系。
  20. 根据权利要求16所述的装置，其中，所述第一确定单元进一步用于：通过预配置信息确定承载类型和用户面配置的对应关系，或者通过网络通知的方式获取承载类型和用户面配置的对应关系。
  21. 根据权利要求20所述的装置，其中，所述第一确定单元进一步用于： 从所述预配置信息中确定与终端能力对应的承载类型和用户面配置的对应关系。
  22. 根据权利要求20所述的装置，其中，所述第一确定单元进一步用于：上报终端能力；通过网络通知的方式获取与所述终端能力对应的承载类型和用户面配置的对应关系。
  23. 根据权利要求16所述的装置，其中，所述承载类型对应的用户面配置包括以下一项或多项：头压缩、加密、完整性保护、分段、串接、ARQ、HARQ、复用、Qos参数、调度方式、调制方式、编码方式和多址方式。
  24. 一种数据传输的装置，所述装置包括：
    第三确定模块，用于确定承载类型和用户面配置的对应关系；
    配置模块，用于配置承载对应的承载类型；
    发送模块，用于发送承载类型指示信息，所述承载类型指示信息中携带承载类型标识；
    第四确定模块，用于根据所述承载类型标识以及承载类型和用户面配置的对应关系确定承载对应的用户面配置；
    传输模块，用于根据确定的用户面配置进行数据传输。
  25. 根据权利要求24所述的装置，其中，所述用户面配置包括用户面功能配置和/或用户面参数配置；或者
    所述用户面配置包括用户面功能在集中处理节点和分布式处理节点之间功能划分的方式。
  26. 根据权利要求24所述的装置，其中，所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置，或者所述承载类型对应的用户面配置是用户面基本功能和/或参数的配置集合。
  27. 根据权利要求24所述的装置，其中，所述第三确定模块进一步用于：通过预配置信息确定承载类型和用户面配置的对应关系。
  28. 根据权利要求24所述的装置，其中，所述装置还包括：
    通知模块，用于通过网络通知的方式通知终端所述承载类型和用户面配置的对应关系。
  29. 根据权利要求28所述的装置，其中，所述通知模块进一步用于：获 取所述终端上报的终端能力；通过网络通知的方式向所述终端通知与所述终端能力对应的承载类型和用户面配置的对应关系。
  30. 根据权利要求24所述的装置，其中，所述承载类型对应的用户面配置包括以下一项或多项：头压缩、加密、完整性保护、分段、串接、ARQ、HARQ、复用、Qos参数、调度方式、调制方式、编码方式和多址方式。
  31. 一种终端，所述终端包括处理器、存储器和收发机，
    所述存储器，用于存储所述处理器在执行操作时所使用的指令；
    所述处理器，用于确定承载类型和用户面配置的对应关系；
    所述收发机，用于接收网络侧指示的承载类型指示信息，所述承载类型指示信息中携带承载类型标识；
    所述处理器，还用于根据所述承载类型指示信息中携带的承载类型标识以及承载类型和用户面配置的对应关系确定承载对应的用户面配置；
    所述收发机，还用于根据确定的用户面配置进行数据传输。
  32. 一种网络侧设备，所述网络侧设备包括处理器、存储器和收发机，
    所述存储器，用于存储所述处理器在执行操作时所使用的指令；
    所述处理器，用于确定承载类型和用户面配置的对应关系；
    所述收发机，用于发送承载类型指示信息，所述承载类型指示信息中携带承载类型标识；
    所述处理器，还用于根据所述承载类型标识以及承载类型和用户面配置的对应关系确定承载对应的用户面配置；
    所述收发机，还用于根据确定的用户面配置进行数据传输。
PCT/CN2017/090746 2016-06-30 2017-06-29 数据传输的方法及装置 WO2018001297A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US16/313,818 US20190159021A1 (en) 2016-06-30 2017-06-29 Method and device for data transmission
EP17819294.4A EP3480989B1 (en) 2016-06-30 2017-06-29 Method and device for data transmission

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610512740.2 2016-06-30
CN201610512740.2A CN107579807B (zh) 2016-06-30 2016-06-30 数据传输的方法及装置

Publications (1)

Publication Number Publication Date
WO2018001297A1 true WO2018001297A1 (zh) 2018-01-04

Family

ID=60785968

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/090746 WO2018001297A1 (zh) 2016-06-30 2017-06-29 数据传输的方法及装置

Country Status (4)

Country Link
US (1) US20190159021A1 (zh)
EP (1) EP3480989B1 (zh)
CN (1) CN107579807B (zh)
WO (1) WO2018001297A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020034552A1 (en) 2018-12-28 2020-02-20 Zte Corporation Configuration of user plane functions for wireless systems
KR102663548B1 (ko) * 2018-12-28 2024-05-03 지티이 코포레이션 무선 시스템들을 위한 사용자 평면 기능들의 구성

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110324867A (zh) * 2018-03-31 2019-10-11 华为技术有限公司 一种通信方法及装置
JP7262941B2 (ja) * 2018-08-06 2023-04-24 シャープ株式会社 端末装置、基地局装置、および方法
US11706670B2 (en) * 2018-08-06 2023-07-18 Google Llc Transferring a radio bearer configuration
CN112153632B (zh) * 2019-06-27 2022-12-13 华为技术有限公司 一种能力上报的方法及通信装置
CN111343657B (zh) * 2020-03-09 2023-02-24 中国联合网络通信集团有限公司 移动性管理方法、装置、终端设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101931898A (zh) * 2009-06-26 2010-12-29 华为技术有限公司 用户面数据的传输方法、装置及系统
CN102685816A (zh) * 2011-03-09 2012-09-19 中兴通讯股份有限公司 一种用户面配置参数的处理方法及装置
US9049588B2 (en) * 2013-02-28 2015-06-02 Blackberry Limited Communicating data in a predefined transmission mode
US20150319795A1 (en) * 2012-11-01 2015-11-05 Ntt Docomo, Inc. Radio communication system and control method
US20160174281A1 (en) * 2013-08-02 2016-06-16 Alcatel-Lucent Method and apparatus for establishing radio bearer

Family Cites Families (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8917630B2 (en) * 2006-10-11 2014-12-23 Lg Electronics Inc. Managing contextual information for wireless communications
CN101005411B (zh) * 2006-12-29 2010-05-19 华为技术有限公司 电路型数据业务自动化测试系统、装置及方法
ATE547875T1 (de) * 2007-07-27 2012-03-15 Research In Motion Ltd Informationsaustausch in drahtlosen servern
CN101163043B (zh) * 2007-11-08 2010-06-02 华为技术有限公司 一种网络管理功能配置方法以及网络管理功能配置系统
CN101527836B (zh) * 2009-04-07 2011-10-26 中兴通讯股份有限公司 传输持续业务复用配置信息的终端、系统及方法
CN101674606A (zh) * 2009-09-25 2010-03-17 华为技术有限公司 数据传输方法及装置
EP2507964A1 (en) * 2009-11-30 2012-10-10 Nokia Siemens Networks Oy Method and network device establishing a binding between a plurality of separate sessions in a network
CN102082684B (zh) * 2009-12-01 2013-04-24 华为技术有限公司 业务配置转换方法、装置及系统
CN102547610B (zh) * 2010-12-31 2016-03-30 华为技术有限公司 消息处理方法、设备及系统
CN102083006B (zh) * 2011-01-17 2014-06-04 大唐移动通信设备有限公司 一种数据传输方法、装置及系统
CN103052045B (zh) * 2011-10-17 2019-03-12 中兴通讯股份有限公司 一种消息类型的指示方法、系统及装置
CN103874151B (zh) * 2012-12-17 2018-04-27 电信科学技术研究院 分层组网时的承载转移方法和设备
CN103974422A (zh) * 2013-02-05 2014-08-06 电信科学技术研究院 一种通信处理方法及装置
CN104488314B (zh) * 2013-06-09 2019-02-26 华为技术有限公司 无线通信方法、用户设备及网络节点
EP3078236A1 (en) * 2013-12-06 2016-10-12 Interdigital Patent Holdings, Inc. Layered connectivity in wireless systems
WO2015113212A1 (zh) * 2014-01-28 2015-08-06 华为技术有限公司 无线承载配置方法、基站及系统
CN104270725B (zh) * 2014-09-24 2018-04-10 中兴通讯股份有限公司 指示信息的确定、处理以及请求消息的处理方法及装置
US10517011B2 (en) * 2014-11-13 2019-12-24 Telefonaktiebolaget Lm Ericsson (Publ) Automated measurement and analysis of end-to-end performance of VoLTE service
US11825352B2 (en) * 2015-11-30 2023-11-21 Apple Inc. Mobile-terminated packet transmission
US20190320417A1 (en) * 2015-12-10 2019-10-17 Nokia Solutions And Networks Oy Method, system and apparatus
WO2017120770A1 (zh) * 2016-01-12 2017-07-20 华为技术有限公司 建立承载的方法、装置及系统
WO2017166031A1 (zh) * 2016-03-28 2017-10-05 华为技术有限公司 区分接入网的方法、装置及计算机可读存储介质
CA3025961C (en) * 2016-05-30 2023-09-26 Huawei Technologies Co., Ltd. Wireless communication method and device

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101931898A (zh) * 2009-06-26 2010-12-29 华为技术有限公司 用户面数据的传输方法、装置及系统
CN102685816A (zh) * 2011-03-09 2012-09-19 中兴通讯股份有限公司 一种用户面配置参数的处理方法及装置
US20150319795A1 (en) * 2012-11-01 2015-11-05 Ntt Docomo, Inc. Radio communication system and control method
US9049588B2 (en) * 2013-02-28 2015-06-02 Blackberry Limited Communicating data in a predefined transmission mode
US20160174281A1 (en) * 2013-08-02 2016-06-16 Alcatel-Lucent Method and apparatus for establishing radio bearer

Non-Patent Citations (1)

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

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020034552A1 (en) 2018-12-28 2020-02-20 Zte Corporation Configuration of user plane functions for wireless systems
EP3903522A4 (en) * 2018-12-28 2022-01-12 ZTE Corporation CONFIGURING USER PLANE FEATURES FOR WIRELESS SYSTEMS
US11882476B2 (en) 2018-12-28 2024-01-23 Zte Corporation Configuration of user plane functions for wireless systems
KR102663548B1 (ko) * 2018-12-28 2024-05-03 지티이 코포레이션 무선 시스템들을 위한 사용자 평면 기능들의 구성

Also Published As

Publication number Publication date
CN107579807A (zh) 2018-01-12
US20190159021A1 (en) 2019-05-23
EP3480989A4 (en) 2019-05-22
EP3480989B1 (en) 2020-12-09
CN107579807B (zh) 2020-11-27
EP3480989A1 (en) 2019-05-08

Similar Documents

Publication Publication Date Title
WO2018001297A1 (zh) 数据传输的方法及装置
WO2019056970A1 (zh) 通信方法及装置
WO2017193945A1 (zh) 一种上行数据传输的方法及设备
WO2020030051A1 (zh) 一种资源配置方法及装置
CN107370573B (zh) 一种下行数据传输的方法及设备
JP6961711B2 (ja) ページング方法及びページング装置
US11265903B2 (en) Uplink transmission method and apparatus
WO2016141793A1 (zh) 一种空口协议栈的配置方法、数据传输方法及设备
WO2013152743A1 (zh) 传输信号的方法和装置
TW201804857A (zh) 建立輔連接的方法和裝置
US11259362B2 (en) Method for repeatedly transmitting data and device
WO2019165882A1 (zh) 一种切片信息的获取方法和中继装置
WO2019062746A1 (zh) 通信方法、装置和系统
WO2020063441A1 (zh) 重复传输方法、终端和网络侧设备
EP4192082A1 (en) Communication method, apparatus and system
US20200008250A1 (en) Wireless Connection Establishment Method And Apparatus
EP4152795A1 (en) Configuration method and device in sidelink relay architecture
WO2019029405A1 (zh) 通信方法与设备
WO2019029463A1 (zh) 一种接收控制信息、发送控制信息的方法及设备
TW202126085A (zh) 使用者設備、排程節點、用於使用者設備之方法及用於排程節點之方法
EP3534662B1 (en) Bearer configuration method and related product
JP6140292B2 (ja) ネットワーク装置及びユーザ端末
WO2020221261A1 (zh) 一种通信方法及装置
WO2019228459A1 (zh) 通信方法、装置及存储介质
WO2017070947A1 (zh) 协同调度方法、装置及系统

Legal Events

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

Ref document number: 17819294

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017819294

Country of ref document: EP

Effective date: 20190130