WO2018032991A1 - 一种数据处理方法及装置 - Google Patents

一种数据处理方法及装置 Download PDF

Info

Publication number
WO2018032991A1
WO2018032991A1 PCT/CN2017/096215 CN2017096215W WO2018032991A1 WO 2018032991 A1 WO2018032991 A1 WO 2018032991A1 CN 2017096215 W CN2017096215 W CN 2017096215W WO 2018032991 A1 WO2018032991 A1 WO 2018032991A1
Authority
WO
WIPO (PCT)
Prior art keywords
data packet
network device
access network
flow
mapping relationship
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2017/096215
Other languages
English (en)
French (fr)
Inventor
黄曲芳
戴明增
韩立锋
曾清海
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=61197384&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=WO2018032991(A1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Priority to EP22199519.4A priority Critical patent/EP4184999B1/en
Priority to EP17840966.0A priority patent/EP3493582B1/en
Priority to EP26150124.1A priority patent/EP4716179A3/en
Priority to EP20167012.2A priority patent/EP3745767B1/en
Priority to BR112019003025-5A priority patent/BR112019003025B1/pt
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP25190092.4A priority patent/EP4661368A3/en
Publication of WO2018032991A1 publication Critical patent/WO2018032991A1/zh
Priority to US16/277,368 priority patent/US10880773B2/en
Anticipated expiration legal-status Critical
Priority to US17/111,165 priority patent/US11997529B2/en
Priority to US18/636,903 priority patent/US20240365161A1/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/50—Queue scheduling
    • H04L47/62—Queue scheduling characterised by scheduling criteria
    • H04L47/6215—Individual queue per QOS, rate or priority
    • 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
    • H04W28/0263—Traffic management, e.g. flow control or congestion control per individual bearer or channel involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • 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
    • 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/0268—Traffic 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]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • 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
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]

Definitions

  • the present application relates to the field of mobile communications technologies, and in particular, to a data processing method and apparatus.
  • LTE Long Term Evolution
  • data transmission is based on RB (Radio Bearer).
  • the LTE system divides data according to QoS (Quality of Service) requirements of various applications.
  • DRBs Data Radio Bearers
  • the PGW Public Data Network GateWay
  • TFT Traffic Flow Template
  • the internal data is implemented in the terminal. Filter to map packets to individual bearers.
  • RAN Radio Access Network
  • Different air interface processing parameters are configured for different RBs to implement different treatments for data of each RB.
  • the data in each DRB is processed on the same side of the radio access network device.
  • the data of different DRBs are different on the radio access network device side.
  • the 5G the fifth generation mobile communication network
  • it is required to implement finer QoS processing on the service data, and the concept of "flow" is introduced, that is, the RB can be
  • the packet is divided into packets of multiple flows.
  • the embodiment of the present invention provides a data processing method and apparatus, which are used to implement a flow direction to which a receiver instructs a flow to which each data packet belongs, thereby implementing processing of the data packet according to a flow level, thereby improving processing efficiency of the data packet.
  • an embodiment of the present application provides a data processing method, including:
  • the first device determines a flow to which the data packet belongs
  • the first device determines a flow identifier according to the flow to which the data packet belongs, and sends the data packet including the flow identifier to the second device.
  • the first device after determining the flow identifier of the data packet, the first device sends the flow identifier to the second access network device by using the data packet, thereby indicating the The stream to which the packet belongs.
  • the second device can be caused to process the data packet according to the flow level, and further, the performance of the end-to-end QoS can be improved.
  • the determining, by the first device, the flow identifier according to the flow to which the data packet belongs includes:
  • the first device allocates the flow identifier to the data packet according to a flow to which the data packet belongs;
  • the first device determines, from the flow identifier list sent by the third device, a flow identifier corresponding to the flow to which the data packet belongs.
  • the first device directly allocates a flow identifier to the data packet, or the first device determines the flow identifier for the data packet according to the flow identifier list sent by the third device, so that the flow identifier of the data packet can be quickly determined, and the determined data is improved.
  • the efficiency of the packet flow identification is improved.
  • the flow identifier is located in a packet header of the data packet.
  • the flow identifier is located in a data packet sequence number field of the data packet, and occupies K bits in the data packet sequence number field, where K is a positive integer.
  • the K-bit carrying stream identifier in the sequence number field of the data packet is directly used, and the structure of the existing data packet can be changed without changing the structure of the existing data packet.
  • the method further includes:
  • the first device groups all data packets belonging to the same flow as a group, and separately allocates a data packet serial number for each group of data packets;
  • the method further includes:
  • the first device performs a header compression and encryption operation on the data packet according to a bit other than a bit occupied by the flow identifier in a data packet sequence number field of the data packet.
  • the first device separately allocates a data packet sequence number for each group of data packets, so that when the data packet is subjected to header compression and encryption operations, according to the data packet sequence number field of the data packet,
  • the bits other than the bits occupied by the stream identifier perform header compression and encryption operations on the data packet, and may carry the stream identifier in the data packet, and avoid modification of the header compression and encryption algorithm, and can
  • the technology is compatible.
  • an embodiment of the present application provides a data processing apparatus, including:
  • a processing unit configured to determine a flow to which the data packet belongs; and determine a flow identifier according to the flow to which the data packet belongs;
  • transceiver unit configured to send the data packet including the flow identifier to the second access network device.
  • an embodiment of the present application provides a data processing apparatus, including:
  • a processor configured to determine a flow to which the data packet belongs; and determine a flow identifier according to the flow to which the data packet belongs;
  • a transceiver configured to send, to the second access network device, the data packet that includes the flow identifier.
  • an embodiment of the present application provides a data processing method, including:
  • the first device determines to end the data packet, where the end data packet is sent by the first device by using the first RB.
  • First class last packet
  • the first device sends the end indication information and the end data packet to the second device, where the end indication information is used to indicate that the data packet that the first device sends by using the first RB that belongs to the first flow has been Sent.
  • the first device when the RB of the first flow mapping is changed, the first device indicates, by the sending end indication information, the last data of the first flow that is sent by the first device by using the first RB by using the first RB. Packets, thereby ensuring that the second device processes each packet in the order of the packets, avoiding packet out of order.
  • the method further includes:
  • the first device sends all data packets that are not sent and belong to the first stream by using the second RB.
  • the first device can accurately determine the data packet transmitted by the changed RB when the RB of the first flow mapping changes, and avoid the disorder of the data packet.
  • the first device determines that the radio bearer RB that is mapped with the first stream is changed from the first RB to the second RB, and includes:
  • the first device receives the remapping instruction sent by the third device, and determines, according to the remapping instruction, that the RB that is mapped with the first flow is changed from the first radio bearer RB to the second RB.
  • the first device determines to end the data packet, including:
  • the sending, by the first device, the end indication information and the ending data packet to the second device including:
  • the first device After the first device sends the end data packet to the second device, the first device sends the end indication information to the second device.
  • the first device may send the end indication information through the end data packet, or may separately send the end indication information, thereby improving the flexibility of the end indication information transmission and improving the efficiency.
  • the method further includes:
  • an embodiment of the present application provides a data processing apparatus, including:
  • a processing unit configured to determine, after the radio bearer RB of the first stream mapping is changed from the first RB to the second RB, to end the data packet, where the end data packet is sent by the first device by using the first RB First class last packet;
  • a transceiver unit configured to send the end indication information and the end data packet to the second device, where the end indication information is used to indicate that the data packet that belongs to the first stream that is sent by the first device by using the first RB is already Sent.
  • an embodiment of the present application provides a data processing apparatus, including:
  • a processor configured to determine, after the radio bearer RB of the first stream mapping is changed from the first RB to the second RB, to end the data packet, where the end data packet is sent by the first device by using the first RB First class last packet;
  • a transceiver configured to send the end indication information and the end data packet to the second device, where the end indication information is used to indicate that the data packet that the first device sends by using the first RB that belongs to the first flow has been Sent.
  • the embodiment of the present application provides a data processing method, including:
  • the second device receives the end indication information sent by the first device, where the end indication information is sent after the first device sends the last data packet belonging to the first flow by using the first radio bearer RB; And indicating that the data packet that belongs to the first stream that is sent by the first device by using the first RB has been sent;
  • the second device processes the data packet that is received by the second RB and belongs to the first stream.
  • the second device may determine, according to the end indication information, the last data packet that belongs to the first flow that is sent by the first device to the second device by using the first RB. It can ensure that the second device processes each data packet in the order of the data packets to avoid data packet disorder.
  • an embodiment of the present application provides a data processing apparatus, including:
  • a transceiver unit configured to receive end indication information sent by the first device, where the end indication information is sent after the first device sends the last data packet belonging to the first flow by using the first radio bearer RB; The information is used to indicate that the data packet that belongs to the first flow that is sent by the first device by using the first RB has been sent;
  • a processing unit configured to process, by the second RB, a data packet that belongs to the first flow.
  • the embodiment of the present application provides a data processing apparatus, including:
  • a transceiver configured to receive end indication information sent by the first device, where the end indication information is sent after the first device sends the last data packet belonging to the first flow by using the first radio bearer RB; The information is used to indicate that the data packet that belongs to the first flow that is sent by the first device by using the first RB has been sent;
  • a processor configured to process, by the second RB, a data packet that belongs to the first stream.
  • the embodiment of the present application provides a data processing method, where the method includes:
  • the first access network device sends a first message to the second access network device, where the first message is used to request to switch the terminal to the second access network device;
  • the first access network device receives a first response message that is returned by the second access network device and includes a first mapping relationship; the first mapping relationship is the terminal that is determined by the second access network device.
  • the first device forwards the data packet of each stream of the terminal to the second access network device according to the first mapping relationship sent by the second device, thereby implementing the terminal at the terminal.
  • the mapping relationship between the flow and the RB is changed during the handover.
  • the first message includes a second mapping relationship, where the second mapping relationship is a mapping relationship between each flow and an RB used by the terminal in a network where the first access network device is located. .
  • the second device may be configured to determine, by the first device, a mapping relationship between each flow and the RB used in the network where the first access network device is located, Thereby, the second device can be caused to send data to the first device according to the second mapping relationship.
  • the first response message further includes a third mapping relationship, where the third mapping relationship is a mapping relationship between the flow and the RB determined by the second access network device for each flow in the terminal, or The mapping between the flow and the RB determined by the core network device corresponding to the second access network device for each flow in the terminal.
  • the third mapping relationship is a mapping relationship between the flow and the RB determined by the second access network device for each flow in the terminal, or The mapping between the flow and the RB determined by the core network device corresponding to the second access network device for each flow in the terminal.
  • it also includes:
  • the first access network device sends a handover command to the terminal, and is used to indicate that the terminal accesses the second access network device; the handover command includes the third mapping relationship.
  • the TEID of the mapping in the first mapping relationship is different.
  • the first device sends the data packet of each RB of the terminal to the second access network device through a tunnel, so as to implement sending the data packet to the second device according to the RB level.
  • the second mapping relationship is different from the third mapping relationship
  • the method further includes:
  • the first access network device deletes a data packet sequence number in a data packet of each stream of the terminal.
  • the TEID of each flow mapping in the first mapping relationship is different.
  • the first device sends the data packet of each stream of the terminal to the second access network device through a tunnel, so as to send the data packet to the second device according to the flow level.
  • the embodiment of the present application provides a data processing apparatus, including:
  • a transceiver unit configured to send a first message to the second access network device, to request to switch the terminal to the second access network device, and receive the first mapping relationship that is returned by the second access network device a first response message;
  • the first mapping relationship is a mapping relationship between each stream in the terminal and a tunnel endpoint identifier TEID;
  • a processing unit configured to forward, according to the first mapping relationship, a data packet of each stream of the terminal to the second access network device.
  • the embodiment of the present application provides a data processing apparatus, including:
  • a transceiver configured to send a first message to the second access network device, to request to switch the terminal to the second access network device, and receive the first mapping relationship that is returned by the second access network device a first response message;
  • the first mapping relationship is a mapping relationship between each stream in the terminal and a tunnel endpoint identifier TEID;
  • a processor configured to forward, according to the first mapping relationship, a data packet of each flow of the terminal to the second access network device.
  • the embodiment of the present application provides a data processing method, where the method includes:
  • the first response message that includes the first mapping relationship to the first access network device, and receiving the foregoing that the first access network device forwards according to the first mapping relationship a data packet of each stream of the terminal;
  • the first mapping relationship is a mapping relationship between each of the terminals and the TEID determined by the second access network device.
  • the first message includes a second mapping relationship, where the second mapping relationship is a mapping relationship between each flow and an RB used by the terminal in a network where the first access network device is located. .
  • the first response message includes a third mapping relationship, where the third mapping relationship is a mapping relationship between the RB and the RB determined by the second access network device for each of the terminals.
  • the core network device corresponding to the second access network device is a mapping relationship between the flow and the RB determined by each flow in the terminal.
  • the second access network device after the second access network device receives the data packet of each flow of the terminal that is forwarded by the first access network device according to the first mapping relationship, the second access network device further includes:
  • the target stream is any one of the second mapping relationships; the target data packet is any one of the target flows.
  • the second access network device determines, by using the RB, that the target data packet is sent, including:
  • the second access network device determines that the target data packet is not correctly received by the receiver of the target data packet And the data packet after the target data packet is correctly received by the receiver of the target data packet, and the target data packet is sent in the first RB; or
  • the second access network device determines that the target data packet is not correctly received by the receiver of the target data packet and the data packet subsequent to the target data packet is not correctly received by the receiver of the target data packet, Sending the target data packet in the second RB; or
  • the second access network device determines that the target data packet is not correctly received by the receiver of the target data packet, sending the target data packet in the second RB;
  • the target data packet is sent in the first RB.
  • the TEID of the mapping in the first mapping relationship is different.
  • the embodiment of the present application provides a data processing apparatus, including:
  • a transceiver unit configured to receive a first message sent by the first access network device, to request to switch the terminal to the second access network device, and return a first mapping relationship to the first access network device a first response message, and receiving a data packet of each flow of the terminal that is forwarded by the first access network device according to the first mapping relationship; the first mapping relationship is the second access network device Determining a mapping relationship between each stream and the TEID in the terminal.
  • the embodiment of the present application provides a data processing apparatus, including:
  • a transceiver configured to receive a first message sent by the first access network device, to request to switch the terminal to the second access network device, and return a first mapping relationship to the first access network device a first response message, and receiving a data packet of each flow of the terminal that is forwarded by the first access network device according to the first mapping relationship; the first mapping relationship is the second access network device Determining a mapping relationship between each stream and the TEID in the terminal.
  • the embodiment of the present application provides a data processing method, where the method includes:
  • the TEID of each RB mapping in the first mapping relationship is the same;
  • the TEID of each RB mapping in the first mapping relationship is different.
  • the embodiment of the present application provides a data processing apparatus, including:
  • a transceiver unit configured to send a first message to the first core network device, to request to switch the terminal from the first access network device to the second access network device, and receive the returned by the first core network device a first response message of the first mapping relationship;
  • the first mapping relationship is a mapping relationship between each RB and the TEID determined by the second access network device for the terminal;
  • a processing unit configured to forward, according to the first mapping relationship, a data packet of each RB of the terminal to the second access network device.
  • the embodiment of the present application provides a data processing apparatus, including:
  • a transceiver configured to send a first message to the first core network device, to request to switch the terminal from the first access network device to the second access network device, and receive the first core network device to return a first response message of the first mapping relationship;
  • the first mapping relationship is a mapping relationship between each RB and the TEID determined by the second access network device for the terminal;
  • a processor configured to forward, according to the first mapping relationship, a data packet of each RB of the terminal to the second access network device.
  • the embodiment of the present application provides a data processing method, where the method includes:
  • the second core network device determines a second mapping relationship, where the second mapping relationship is a mapping relationship between each RB and the flow used by the terminal in the network where the first access network device is located; the second mapping relationship Determining, by the TFT template used by each RB of the terminal in the network where the first core network device is located, and the TFT template used by the network in which the second core network device is located;
  • the second core network device sends a third message including the second mapping relationship to the second access network device, for requesting to switch the terminal from the first access network device to the second access network device.
  • the method further includes:
  • the second core network device receives a response message that is returned by the second access network device and includes a first mapping relationship; the first mapping relationship is that each of the second access network devices determines for the terminal Mapping between RB and TEID.
  • the embodiment of the present application provides a data processing apparatus, including:
  • a processing unit configured to determine a second mapping relationship, where the second mapping relationship is a mapping relationship between each RB and a flow used by the terminal in the network where the first access network device is located; the second mapping relationship Determining, by the TFT template used by each RB of the terminal in the network where the first core network device is located, and the TFT template used by the network in which the second core network device is located;
  • transceiver unit configured to send, to the second access network device, a third message that includes the second mapping relationship, to request to switch the terminal from the first access network device to the second access network device.
  • the embodiment of the present application provides a data processing apparatus, including:
  • a processor configured to determine a second mapping relationship, where the second mapping relationship is a mapping relationship between each RB and a flow used by the terminal in the network where the first access network device is located; the second mapping relationship Determining, by the TFT template used by each RB of the terminal in the network where the first core network device is located, and the TFT template used by the network in which the second core network device is located;
  • a transceiver configured to send, to the second access network device, a third message that includes the second mapping relationship, to request to switch the terminal from the first access network device to the second access network device.
  • the embodiment of the present application provides a data processing method, where the method includes:
  • the mapping relationship is a mapping relationship between each RB and the flow used by the terminal in the network where the first access network device is located;
  • a response message including a first mapping relationship to the second core network device where the first mapping relationship is that each RB determined by the second access network device for the terminal Mapping relationship with TEID.
  • the second access network device enables the second core network device to determine each RB and TEID of the terminal by returning a response message including the first mapping relationship to the second core network device. Reflect Shooting relationship.
  • the response message further includes mapping relationship mapping indication information, where the mapping relationship mapping indication information is used to indicate that the terminal determined by the second access network device is in the second access network device
  • mapping relationship mapping indication information is used to indicate that the terminal determined by the second access network device is in the second access network device
  • the mapping relationship between each RB and the stream used in the network is the same as the second mapping relationship.
  • the response message further includes a sequence indication message, where the first access network device is configured to carry the first connection in a data packet that forwards the terminal to the second access network device.
  • the serial number of the packet assigned by the incoming device is configured to carry the first connection in a data packet that forwards the terminal to the second access network device.
  • the third message further includes a TFT template used by each RB of the terminal in a network where the second core network device is located.
  • the TEID of each RB mapping in the first mapping relationship is the same;
  • the method further includes:
  • the second access network device filters data packets of each RB of the terminal into each stream according to a TFT template used by each RB of the terminal in a network where the second core network device is located. data pack.
  • the second access network device filters, according to the TFT template used by each RB of the terminal in the network where the second core network device is located, the data packet of each RB of the terminal to Before each stream's data packet, it also includes:
  • the second access network device filters data packets of each RB of the terminal into each stream according to a TFT template used by each RB of the terminal in a network where the second core network device is located. After the packet, it also includes:
  • the second access network device determines an RB to which the data packet of each flow belongs
  • the second access network device For the data packets in each RB, the second access network device performs data aggregation processing on the data packets of each RB by using the data packet sequence allocated by the first access network in each data packet.
  • the embodiment of the present application provides a data processing apparatus, including:
  • a transceiver unit configured to receive a third message that is sent by the second core network device and includes a second mapping relationship, configured to request to switch the terminal from the first access network device to the second access network device, where the second The mapping relationship is a mapping relationship between the RB and the flow used by the terminal in the network where the first access network device is located, and a response message including the first mapping relationship is returned to the second core network device;
  • the first mapping relationship is a mapping relationship between each RB and the TEID determined by the second access network device for the terminal.
  • the embodiment of the present application provides a data processing apparatus, including:
  • a transceiver configured to receive a third message that is sent by the second core network device and includes a second mapping relationship, configured to request to switch the terminal from the first access network device to the second access network device, where the second The mapping relationship is a mapping relationship between the RB and the flow used by the terminal in the network where the first access network device is located, and a response message including the first mapping relationship is returned to the second core network device;
  • the first mapping relationship is a mapping relationship between each RB and the TEID determined by the second access network device for the terminal.
  • the embodiment of the present application provides a data processing method, where the method includes:
  • the access network device allocates the uplink resource to the terminal
  • the illustrated access network device sends first indication information to the terminal, where the first indication information is used to indicate that the data is in The transmission success rate of the correctly transmitted on the uplink resource.
  • the access network device allocates the uplink resource to the terminal, and indicates the transmission success rate of the data correctly transmitted on the uplink resource, so that the terminal can be in the uplink resource according to the data.
  • the transmission success rate of the correctly transmitted transmission determines the data transmitted on the uplink resource, thereby improving the transmission success rate of the higher priority data.
  • the first indication information is a specific value of a transmission success rate
  • the first indication information is an index value, and the index value corresponds to a specific value of a transmission success rate.
  • the embodiment of the present application provides a data processing apparatus, including:
  • a processing unit configured to allocate the uplink resource to the terminal
  • the transceiver unit is configured to send the first indication information to the terminal, where the first indication information is used to indicate a transmission success rate of data correctly transmitted on the uplink resource.
  • the embodiment of the present application provides a data processing apparatus, including:
  • a processor configured to allocate the uplink resource to the terminal
  • the transceiver is configured to send first indication information to the terminal, where the first indication information is used to indicate a transmission success rate of data correctly transmitted on the uplink resource.
  • the embodiment of the present application provides a data processing method, where the method includes:
  • the terminal determines the uplink resource allocated by the access network device for the terminal, and receives the first indication information sent by the access network device, where the first indication information is used to indicate that the data is correctly transmitted on the uplink resource. Success rate;
  • the data transmitted by the terminal on the uplink resource according to the first indication information is transmitted.
  • the terminal may enable the terminal to determine, according to the transmission success rate of the data correctly transmitted on the uplink resource, the transmission on the uplink resource. Data, thereby increasing the transmission success rate of higher priority data.
  • the data that is transmitted by the terminal on the uplink resource according to the first indication information includes:
  • the terminal determines that the transmission success rate indicated by the first indication information is greater than the first threshold, transmitting, by the uplink resource, data corresponding to the service whose priority is greater than the first preset priority; or
  • the terminal determines that the transmission success rate indicated by the first indication information is less than the second threshold, the terminal transmits data corresponding to the service whose priority is lower than the second preset priority on the uplink resource.
  • the first indication information is a specific value of a transmission success rate
  • the first indication information is an index value, and the index value corresponds to a specific value of a transmission success rate.
  • the embodiment of the present application provides a data processing apparatus, including:
  • a processing unit configured to determine an uplink resource allocated by the access network device for the terminal, and receive first indication information sent by the access network device, where the first indication information is used to indicate that the data is on the uplink resource The transmission success rate of the correct transmission;
  • a transceiver unit configured to transmit data on the uplink resource according to the first indication information.
  • the embodiment of the present application provides a data processing apparatus, including:
  • a processor configured to determine an uplink resource allocated by the access network device for the terminal, and receive first indication information sent by the access network device, where the first indication information is used to indicate that the data is on the uplink resource The transmission success rate of the correct transmission;
  • a transceiver configured to transmit data on the uplink resource according to the first indication information.
  • FIG. 1 is a schematic flowchart of a data processing method according to an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a data processing method according to an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a data processing method according to an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a data processing method according to an embodiment of the present application.
  • 5(a) to 5(c) are schematic flowcharts of a data processing method according to an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of a data processing method according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a data switching process according to an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of a data processing method according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a data switching process according to an embodiment of the present application.
  • FIG. 10 is a schematic flowchart of a data processing method according to an embodiment of the present application.
  • FIG. 11 is a schematic diagram of a data switching process according to an embodiment of the present application.
  • FIG. 12 is a schematic flowchart of a data processing method according to an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application.
  • FIG. 15 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application.
  • FIG. 16 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application.
  • FIG. 17 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application.
  • FIG. 18 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application.
  • FIG. 19 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application.
  • FIG. 20 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application.
  • FIG. 21 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application.
  • FIG. 22 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application.
  • FIG. 23 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application.
  • FIG. 24 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application.
  • FIG. 25 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application.
  • FIG. 26 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application.
  • FIG. 27 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application.
  • FIG. 28 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application.
  • FIG. 29 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application.
  • FIG. 30 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application.
  • FIG. 31 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application.
  • FIG. 32 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present disclosure.
  • each RB in the radio access network device corresponds to a PDCP (Packet Data Convergence Protocol) entity and an RLC (Radio Link Control) entity.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • the radio access network device places each data packet in the PDCP corresponding to the RB to which each data packet belongs.
  • the entity performs processing such as assigning a PDCP SN (Sequence Number), header compression, encryption, and addition of a PDCP header, and then transmitting the data packet in the order of the PDCP SN through the RLC entity to which each data packet belongs.
  • the radio access network device After receiving the data packet, the radio access network device sequentially transfers the data packet from the RLC entity to the PDCP entity according to the PDCP SN of each data packet to perform PDCP header, decryption, decompression, and the like.
  • the radio access network equipment can only implement the processing of data packets according to the RB, and how to process the data packets according to each stream, there is no good solution.
  • the terminal may be a wireless terminal, such as a mobile phone, a computer, a tablet, a personal digital assistant (PDA), a mobile Internet device (MID), and a wearable device.
  • a wireless terminal such as a mobile phone, a computer, a tablet, a personal digital assistant (PDA), a mobile Internet device (MID), and a wearable device.
  • PDA personal digital assistant
  • MID mobile Internet device
  • wearable device a wireless terminal
  • IP Internet Protocol
  • IP Internet Protocol
  • UE user equipment
  • FIG. 1 a schematic flowchart of a data processing method provided by an embodiment of the present application.
  • the method includes:
  • Step 101 The first device determines a flow to which the data packet belongs.
  • Step 102 The first device determines a flow identifier according to the flow to which the data packet belongs, and sends the data packet including the flow identifier to the second device.
  • the first device may be an access network device, or may be a device such as a terminal.
  • the first device may determine the flow to which the data packet belongs according to the actual situation. For example, the first device may determine the flow to which the data packet belongs according to the service type, the destination address, the port, and the like corresponding to the data packet. limited.
  • the second device may be an access network device, or may be a device such as a terminal.
  • the manner in which the first device determines the flow identifier according to the flow to which the data packet belongs may be the following two types:
  • the first device may allocate the flow identifier to the data packet according to the flow to which the data packet belongs. It should be noted that, in this scenario, the first device may use the flow identifier that is allocated for each flow in advance, and then, according to the flow to which the data packet belongs, the flow identifier that is allocated in advance for each flow and the data packet. A flow identifier corresponding to the associated stream is allocated to the data packet. After the first device allocates the flow identifier for each flow, the flow identifier of each flow may also be sent to the second device by using RRC (Radio Resource Control) signaling. Of course, the first device may also send the flow identifier of each flow to a device such as a terminal or a core network device.
  • RRC Radio Resource Control
  • the first device determines, from the flow identifier list sent by the third device, a flow identifier corresponding to the flow to which the data packet belongs.
  • the third device may be the same device as the second device, or may be a different device.
  • the third device may also be a core network device or a terminal device connected to the first device, which is not limited in this embodiment of the present application.
  • the third device may send the flow identifier list to the first device by using RRC signaling or PDCP layer signaling.
  • the first device may aggregate the determined data packet to the convergence protocol corresponding to the RB of each data packet.
  • the data packet in each aggregation protocol entity is then assigned a packet sequence number, a header compression, an encryption, a protocol header, and the like.
  • the aggregation protocol entity may refer to a PDCP entity, or an entity having a similar function to the PDCP entity;
  • the data packet sequence number may refer to a PDCP SN, or may be a sequence having a similar function to the PDCP SN; It refers to the PDCP header, and may also refer to a packet header having a similar function to the PDCP header. limited.
  • the first device when the first device allocates the data packet sequence number for the data packet, the first device may uniformly allocate the data packet sequence number to all the data packets to which the multiple flows of the same RB belong, that is, when the data packet serial number is allocated. , does not distinguish which stream the packet belongs to. This is compatible with existing protocols and avoids major changes to existing protocols.
  • all the data packets belonging to the same flow may be grouped as a group, and the data packet serial number is separately allocated for each group of data packets, that is, When assigning a packet sequence number, you need to distinguish which stream the packet belongs to.
  • flow1 to flow3 are mapped to the same RB, and the first device receives five data packets in time order, respectively, data packet 1 to data packet 5, wherein data packet 1 and data packet 4 belong to flow1, and data packet 3 And packet 5 belongs to flow2, and packet 2 belongs to flow3.
  • the sequence number of the data packet allocated by the first device to the data packet 1 to the data packet 5 may be 1, 1, 1, 2, and 2.
  • the first device needs to perform a header compression and encryption operation on the data packet according to the data packet sequence number field of the data packet.
  • a bit other than the bit occupied by the stream identifier performs a header compression and encryption operation on the data packet.
  • the first device may first set the value of the bit occupied by the flow identifier to 1 or 0, and then perform header compression and encryption on the data packet. operating.
  • the first packet compression, encryption, and the like may be performed separately for each data packet, and the processing is unified only when the PDCP header is finally added. In this way, the packet sequence numbers used for header compression and encryption are contiguous and compatible with the prior art.
  • the flow identifier may be carried in the data packet and sent to the second device.
  • the first device places the flow identifier in a packet header of the data packet, so as to send the flow identifier to the second device by using the data packet.
  • a field may be added to the packet header of the data packet as the flow identifier field, or the existing field in the packet header of the data packet may be redefined as the flow identifier field.
  • a reserved field in a data packet can be redefined as a flow identification field, such as redefining a reserved field in a PDCP header in a data packet as a flow identification field.
  • the first device carries the flow identifier by using K bits in the sequence number field of the data packet, where K is a positive integer.
  • K is a positive integer.
  • the value of K can be determined according to actual conditions, and is not limited herein.
  • the stream identifier is now located in the packet sequence number field of the data packet and occupies K bits in the packet sequence number field.
  • the packet sequence number is PDCP SN.
  • the first device may carry the flow identifier through the first K bits in the PDCP SN field.
  • the above method is to add explicit bits in the data packet to identify each stream, thereby indicating the flow to which each data packet belongs, in addition to implicitly indicating the flow to which each data packet belongs. For example, it may be previously agreed between the first device and the second device, the terminal, and the core network device that the flow to which each data packet belongs may be indicated according to the data packet sequence number of the data packet. For example, when the data packet sequence number of the data packet is odd, it indicates that the data packet is from stream 0, and when the packet sequence number of the packet is even, it indicates that the data packet is from stream 1.
  • the prior agreement between the first device and the second device, the terminal, and the core network device may be agreed by using RRC signaling; or may be agreed by using PDCP layer control signaling.
  • the first device after determining the flow identifier of the data packet, the first device sends the flow identifier to the second device by using the data packet, thereby indicating to the second device that the data packet belongs to Stream.
  • the method can enable the second device to process the data packet according to the flow level. Further, the performance of the end-to-end QoS can be improved.
  • FIG. 2 is a schematic flowchart diagram of a data processing method provided by an embodiment of the present application.
  • the PDCP, the RLC, and the MAC are taken as an example for description, but the solution described in the embodiment of the present application is not limited to these layers.
  • the first device after receiving the data packets of flow 0 (flow 0) and flow 1 (flow 1), the first device determines to map the two flows to the same RB transmission, and determines a flow identifier for each data packet.
  • the flow identifier assigned to stream 0 (flow 0) by the first device is 0, and the flow identifier assigned to stream 1 (flow 1) is 1.
  • the flow identifier assigned by the first device for each flow may be located in the PDCP header of the data packet, or may occupy K bits in the PDCP SN field. The number of bits occupied by the flow identifier can be determined according to the number of flows.
  • the PDCP entity of the first device also needs to uniformly allocate the PDCP SN for the data packets of the two flows. Specifically, two packets from flow 0 have a PDCP SN of 24 and 25, and two packets from flow 1 have a PDCP SN of 26 and 27. If the number of flows aggregated in the same RB is more than two, this practice still applies. Then, the first device separately performs header compression, encryption, and PDCP header processing on each data packet, and then delivers the data packet to the RLC entity, and then the MAC entity forwards to the PHY entity, and then sends the data packet to the second device.
  • the PDCP entity of the second device After the second device receives the data packet sent by the first device, the PDCP entity of the second device performs operations such as de-PDCP header, decryption, and header decoding, and finally identifies each data packet according to the flow identifier assigned by the first device.
  • the PDCP entity can perform encryption and header compression/decompression operations on the respective sub-entities of different flows.
  • the SN used by each sub-entity is discontinuous; another implementation manner Yes: In the PDCP entity, the same set of sub-entities are used to implement encryption and header compression/de-head compression operations.
  • the PDCP SN used by each sub-entity is continuous.
  • FIG. 2 is a schematic flowchart of a data processing method according to an embodiment of the present application.
  • the PDCP entity of the first device may also separately allocate PDCP SN, increase flow identifier, header compression, encryption, and the like to the data packets of the two streams, and perform unified processing only in the step of adding the PDCP header at the end.
  • the biggest benefit of this is that the PDCP SN used for header compression and encryption is contiguous, the same as the prior art, so the changes to the header compression and encryption algorithms are relatively small.
  • the PDCP entity of the second device uniformly performs the PDCP header processing, and then identifies the flow to which each data packet belongs according to the flow identifier allocated by the first device. Finally, each stream packet is decrypted, decompressed, and the like.
  • the PDCP entity internally implements encryption, header compression/decompression header operations on the same set of sub-entities for different streams.
  • the RB of the flow map may change as the air interface wireless conditions change, or the QoS of the service changes, or the user subscription information changes.
  • the buffer corresponding to the source RB of the sender may still have some data packets of the stream that have not been transmitted yet, or the sender has not transmitted, but the sender does not determine whether the receiver correctly receives the packet.
  • the first device may be a terminal or an access network device; the second device may be a terminal or an access network device.
  • the method includes:
  • Step 401 After the RB of the first stream mapping is changed from the first RB to the second RB, the first device determines to end the data packet, where the ending data packet is sent by the first device by using the first RB. The last of the first stream data pack.
  • Step 402 The first device sends the end indication information and the end data packet to the second device, where the end indication information is used to indicate that the first device sends the first RB that belongs to the first flow.
  • the packet has been sent.
  • Step 403 The second device receives the end indication information sent by the first device, where the end indication information is sent after the first device sends the last data packet belonging to the first flow by using the first RB.
  • the indication information is used to indicate that the data packet that belongs to the first flow that is sent by the first device by using the first RB has been sent.
  • Step 404 The second device processes the data packet that belongs to the first stream that is received by the second RB.
  • the first device may receive the remapping instruction sent by the third device, and determine, according to the remapping instruction, that the RB that is mapped with the first stream is changed from the first RB to the second RB.
  • the remapping command includes a mapping relationship between the changed first stream and the second RB.
  • the remapping command may further include a mapping relationship between the first stream and the first RB before the change.
  • the third device may be a device such as a core network device or a terminal connected to the first device, and the third device may be the same device as the second device, which is not limited in this embodiment.
  • the cache corresponding to the first RB may still have unsent data packets belonging to the first flow, and has been sent but not determined to be received. Whether the party correctly received the packet.
  • the first device may send, by the second RB, all data packets that are not sent and belong to the first stream.
  • the first device may still send all the data packets that are not sent and belong to the first stream by using the first RB, in this case, the end indication information is sent by the RB before the RB change of the first flow mapping. That is, the first device sends the end indication information through the first RB.
  • the first device sends all the unsent data packets that belong to the first stream through the second RB, before sending the data packets, the first device needs to re-send all the unsent and belongs to the first stream.
  • the packet is re-allocated to store the packet sequence number, encryption, header compression, and so on.
  • the packet sequence number needs to be re-allocated to obtain a continuous packet sequence number.
  • the "discontinuous packet sequence number" appears here because the packet sequence of the data packet in the first RB is originally continuous, and after the first device determines that the RB of the first stream mapping is changed, the first RB is not When the data packet that is sent and belongs to the first stream is sent by the second RB, the data packet sequence of the data packet in the first RB is scrambled, and the data packet sequence of the data packet in the first RB is vacant, and the vacant data is vacant.
  • the packet sequence number is a packet sequence number of a packet that is not transmitted in the first RB and belongs to the first stream.
  • the first device may first determine the end data packet from the first, and then send the end indication information and the end data packet to the second device. Specifically, if the first device sends all the data packets that are not sent and belong to the first flow, the first device may send all the data that is sent by using the first RB to the first flow.
  • the last data packet in the to-be-acknowledged data packet is determined as the end data packet, and the to-be-confirmed data packet is a data packet that has been transmitted but has not been determined whether the receiver correctly received.
  • the first device may send all the packets that belong to the first flow that are sent by using the first RB.
  • the acknowledgment packet and the last packet in the unsent packet are determined to be the end packet.
  • the first device can also determine any one data packet as the end data packet.
  • the description herein is only an example.
  • the first device may carry the end indication information in the end data packet, or may separately send the end indication information and the end data packet.
  • the first device sends an end data packet including the end indication information to the second device.
  • the end indication information can be located anywhere in the end packet, for example, the end indication information can be located in the packet header of the end packet.
  • the first device after the first device sends the end data packet to the second device, the first device sends the end indication information to the second device. It should be noted that, in this implementation manner, after the first device sends the end data packet to the second device, before sending the end indication information to the second device, the first device needs to receive the An acknowledgment message returned by the second device, and after determining, according to the acknowledgment message, that the end data packet and the data packets belonging to the first stream and before the end data packet are correctly received by the second device, Sending the end indication information to the second device.
  • the first device may generate a control packet including the end indication information, and send the control packet to the second device by using the first RB or the second RB, thereby implementing sending an end indication to the second device. information.
  • the second device may determine that the data packet belonging to the first stream sent by the first device by using the first RB has been sent.
  • the two devices may determine when the data packets belonging to the first stream received from the second RB are submitted to the previous protocol layer for processing, such as the PDCP layer.
  • the data packet in the method of the foregoing process may be an uplink data packet or a downlink data packet, which is not limited in this embodiment of the present application.
  • the last data packet that belongs to the first flow that is sent by the first device by using the first RB is indicated by the sending end indication information, thereby It can ensure that the second device processes each data packet in the order of the data packets to avoid packet out of order.
  • FIG. 5(a) and FIG. 5(b) a schematic flowchart of a data processing method according to an embodiment of the present application is provided.
  • FIG. 5(a) and FIG. 5(b) PDCP and RLC are taken as an example, but the solution described in the embodiment of the present application is not limited to these layers.
  • the original 5 flows are mapped to two RBs: stream 0 (flow 0), stream 1 (flow 1), stream 2 (flow 2) map to RB A, stream 3 (flow 3), stream 4 (flow 4) maps to RB B.
  • the receiver After receiving the data packet of each flow, the receiver forwards the data packet mapped to the flow of the same RB through the same PDCP entity, performs header compression, encryption, and adds the PDCP header, and then forwards the data packet to the RLC entity.
  • flow2 is mapped to RB B, and the mapping relationship between other flows and RBs is unchanged.
  • the two data packets belonging to flow2 received by the first device are still in the RLC buffer of RB A, and the PDCP SNs of the two data packets are 22 and 25, respectively.
  • These two data packets may be unsent packets, or may be packets that have been sent but have not been determined to be correctly received by the receiver.
  • the packet of PDCP SN of RB B in FIG. 5(b) is 67. Since the order of the packets received by the sender from the upper layer of the sender is 22, 25, 67, the receivers are also submitted to the upper layer of the receiver in the same order.
  • the sender After flow2 is mapped to RB B, the sender generates a control packet containing the end indication information after sending the data packet of the PDCP SN of flow2 to 25, and sends the control packet to the receiver on the air interface. The purpose is to indicate to the receiver that the last packet belonging to flow2 sent by the sender through the RAA is a packet with a PDCP SN of 25.
  • FIG. 5(c) is a schematic flowchart of a data processing method according to an embodiment of the present application.
  • the sender will re-process the "data packets 24, 25 that have not been transmitted in the air interface" belonging to flow2, and then transfer them to the RB B mapped after the change of flow2.
  • the PDCP entity mentioned here is reprocessed, including reassigning the PDCP SN, re-encrypting, re-compressing, and so on.
  • the sender can send the end indication information in advance, that is, after the last packet transmission from flow 2 in RB A is completed, the end indication information is sent.
  • the receiver can determine the time to submit the packet belonging to flow2 to the upper layer.
  • the sender except for the re-processing of the "packets 24, 25 that have not been transmitted on the air interface", if the PDCP SN of other data packets is affected, it needs to be re-processed, such as the packet belonging to flow 0 in Figure 5(a). 23. Packet 24 belonging to flow 1 needs to be reassigned PDCP SN, re-encrypted, and re-compressed.
  • the data packets received by the access network device in the system on the wired interface enter the access network device according to the RB, and are sent by the RB when the air interface sends the data packet.
  • the type of access network device of this type is hereinafter referred to as RB-RB type; and the NR (New Radio) system is based on flow transmission, and the access network device in the system is received on the wired interface.
  • the data packet is sent to the access network device according to the flow. When the data packet is sent by the air interface, it is sent by the RB in the air interface.
  • the type of the access network device of this type is simply referred to as the flow-RB type.
  • the sender determines a tunnel for the same RB or flow data packet, and sends the same RB or flow data packet through the determined tunnel.
  • the tunnel generally uses the tunnel endpoint identifier (Tunnel). Endpoint Identifier, TEID) is identified.
  • the source access network device currently accessed by the terminal and the target access network device to be switched may have different combinations. All possible combinations may be as shown in Table 1. It should be noted that the scenario shown in Table 1 may be a scenario in which the LTE system and the NR system of the access network device exist in the network, and may be other scenarios, which is not limited in this application.
  • the terminal is switched in the LTE system, which is a prior art.
  • the access network devices in different systems use different granularity in packet processing (the LTE system is based on the RB level, and the NR system is based on the flow level).
  • the terminal performs the handover, how does the source access network device and the target access network device convert the RB-level data packet into the stream-level data packet or convert the flow-level data packet into the RB-level data packet. There is currently no good solution.
  • FIG. 6 a schematic flowchart of a data processing method according to an embodiment of the present application is provided.
  • the method includes:
  • Step 601 The first access network device sends a first message to the second access network device, where it is requested to switch the terminal to the second access network device.
  • Step 602 The second access network device receives the first message sent by the first access network device, and is configured to request to switch the terminal to the second access network device.
  • Step 603 The first access network device receives a first response message that is returned by the second access network device and includes a first mapping relationship, where the first mapping relationship is each flow and tunnel end point in the terminal. Identifies the mapping relationship of TEIDs.
  • the first mapping relationship may be determined by the second access network device or the core network device that is in the same network as the second access network device, and may be determined according to actual conditions, and details are not described herein.
  • Step 604 The first access network device forwards the data packet of each flow of the terminal to the second access network device according to the first mapping relationship.
  • Step 605 The second access network device returns a first response message including the first mapping relationship to the first access network device, and receives the first access network device to forward according to the first mapping relationship.
  • the data packet of each stream of the terminal is a first response message including the first mapping relationship to the first access network device, and receives the first access network device to forward according to the first mapping relationship.
  • the first access network device may receive the measurement report sent by the terminal. It should be noted that the terminal is a terminal that accesses the first access network device.
  • the first access network device After receiving the measurement report, the first access network device performs a handover decision according to the handover algorithm. After determining that the handover needs to be performed, step 601 is performed.
  • the first message sent by the first access network device may further include at least one of the following:
  • the second mapping relationship is a mapping relationship between each flow and an RB used by the terminal in a network where the first access network device is located;
  • the fourth mapping relationship is a mapping relationship between each flow and a TEID used by the terminal in a network where the first access network device is located;
  • At least one flow AMBR (Aggregate Maximum Bit Rate) value corresponding to each flow.
  • the multiple flows may correspond to the same flow AMBR, that is, one set of flows may correspond to one flow AMBR.
  • the first response message may further include a third mapping relationship, where the third mapping relationship is a mapping relationship between the flow and the RB determined by the second access network device for each flow in the terminal. Or the mapping relationship between the flow and the RB determined by the core network device corresponding to the second access network device for each flow in the terminal. Similar to the first mapping relationship, the third mapping relationship also includes an independent TEID allocated for the uplink data and the downlink data.
  • the second mapping relationship and the third mapping relationship may be the same or different, and may be determined according to actual conditions, and details are not described herein again.
  • the first access network device forwards, according to the first mapping relationship, a data packet of each stream of the terminal to the Before the second access network device, it is also possible to delete the data packet sequence number in the data packet of each stream of the terminal. For example, delete the PDCP SN in the packet for each stream.
  • the first access network device may send the data packet of each flow to the second access network device through a tunnel.
  • the first access network device may also send the data packet of each RB of the terminal to the second access network device through a tunnel.
  • the TEID mapped by each RB mapped flow is the same.
  • the first access network device establishes a tunnel according to the first mapping relationship. Therefore, the TEIDs of the same flow mappings in the first mapping relationship are the same, that is, in the first mapping relationship.
  • the mapped TEIDs are the same and are mapped in the third mapping relationship.
  • the different RBs have different TEIDs mapped in the first mapping relationship.
  • the first access network device may send the two parts of the data packet of the terminal to the second access network device, and part of the data packet that has been sent to the terminal through the air interface but has not determined whether the terminal is correctly received.
  • a packet a part of a packet that has not been sent to the terminal through an air interface.
  • the first access network device may further send a handover command to the terminal, where the terminal is configured to access the second access network device, where the handover command includes the third mapping relationship.
  • step 605 after the second access network device receives the data packet of each flow of the terminal, if the second mapping relationship is determined according to the second mapping relationship and the third mapping relationship, The first RB of the target flow map is changed to the second RB, and after receiving the target data packet of the target flow, determining an RB used to send the target data packet; wherein the target flow is the second Mapping any one of the flows; the target data packet is any one of the target flows.
  • the mapping relationship between the flow and the RB determined by the second access network device may be the same as the mapping relationship between the flow and the RB used by the terminal in the network where the first access network device is located, or Different, if the same, the second access network device processes the data packet of the terminal according to the mapping relationship between the original flow and the RB, and details are not described herein again.
  • the second connection There are four ways for the network access device to determine the RB used to send the target data packet, which is described in detail below:
  • the second access network device determines that the target data packet is not correctly received by the receiver of the target data packet and the data packet after the target data packet is used by the target data When the receiver of the packet receives correctly, the target data packet is transmitted in the first RB.
  • the second access network device determines that the target data packet is not correctly received by the receiver of the target data packet and the data packet after the target data packet is not the target When the receiver of the data packet receives correctly, the target data packet is transmitted in the second RB.
  • the second access network device determines that the target data packet is not correctly received by the receiver of the target data packet, sending the target data packet in the second RB. .
  • the target data packet is sent in the first RB.
  • the second access network device belongs to the data packet of the flow for the flow without replacing the RB. If the previous data packet is moved to the new RB transmission, the data packet serial number of the current data packet is changed, and the encryption is performed again. After processing, it is sent in the air interface.
  • the second access network device for the data packets received from the gateway, maps the data packets of each flow to the corresponding RB according to the new flow and RB mapping relationship, and then sends the data packet in the air interface, and details are not described herein.
  • the second access network device may determine, according to the PDCP status report sent by the terminal or the first access network device, the receiving status of each data packet.
  • the second access network device may further determine the receiving status of each data packet by other means, and details are not described herein again.
  • the second mapping relationship and the third mapping relationship are exchanged between the first access network device and the second access network device before the handover, so that when the terminal performs handover, the source is implemented.
  • the RB level data packet is converted into a stream level data packet or the stream level data packet is converted into an RB level data packet.
  • FIG. 7 is a schematic diagram of a data switching process provided by an embodiment of the present application.
  • FIG. 7 corresponds to the comparison scenario 2 in Table 1, that is, the first access network device processes the data packet according to the flow-RB manner, and the second access network device processes the data packet according to the flow-RB manner.
  • Step 701 The terminal reports the measurement report to the first access network device.
  • the specific content of the measurement report can be referred to the description in the existing standard, which is not limited by the embodiment of the present application.
  • Step 702 The first access network device determines to trigger the handover process according to the received measurement report, and sends a first message to the second access network device.
  • the following information may be included in the first message:
  • mapping relationship a second mapping relationship; a fourth mapping relationship; at least one stream AMBR value corresponding to each stream.
  • Step 703 The second access network device returns a first response message including the first mapping relationship to the first access network device.
  • the first response message may further include a third mapping relationship, where the third mapping relationship may be the same as the second mapping relationship, or may be different, and may be determined according to actual conditions.
  • Step 704 The first access network device sends a handover command to the terminal.
  • the switching command includes the third mapping relationship.
  • Step 705 The first access network device sends the data packet of the terminal to the second access network device.
  • the first access network device may send the data packet of each stream of the terminal to the second access network device through a tunnel.
  • the second access network device knows which stream the data packet belongs to according to the tunnel in which the data packet is received.
  • Step 706 The second access network device performs path switching.
  • the second access network device may further notify the gateway and the core network session management network element, and send subsequent data packets related to the terminal to the second access network device.
  • Step 707 The terminal accesses the second access network device.
  • the method includes:
  • Step 801 The first access network device sends a first message to the first core network device, where the first message is used to request to switch the terminal from the first access network device to the second access network device.
  • Step 802 The first access network device receives a first response message that is returned by the first core network device and includes a first mapping relationship, where the first mapping relationship is that the second access network device is The mapping relationship between each flow determined by the terminal and the TEID;
  • Step 803 The first access network device forwards, according to the first mapping relationship, a data packet of each flow of the terminal to the second access network device.
  • FIG. 9 is a schematic diagram of a data switching process provided by an embodiment of the present application.
  • FIG. 9 corresponds to the comparison scenario 3 in Table 1, that is, the first access network device processes the data packet according to the flow-RB manner, and the second access network device processes the data packet according to the RB-RB manner.
  • Step 901 The terminal reports the measurement report to the first access network device.
  • the specific content of the measurement report can be referred to the description in the existing standard, which is not limited by the embodiment of the present application.
  • the terminal has 4 flows, which are flow 0, flow 1, flow 2, and flow 3.
  • Step 902 The first access network device determines to trigger the handover process according to the received measurement report, and sends a first message to the first core network device, for requesting to switch the terminal to the second access network device.
  • the first access network device determines to establish a tunnel for each flow, and the first access network device allocates one TEID for each uplink data and downlink data of each flow, so the first message may include the terminal in the first
  • the mapping relationship between the uplink and downlink data and the TEID of each stream used in the network where the access network device is located for example, flow 0 mapping TEID 0, flow 1 mapping TEID 1, flow 2 mapping TEID 2, flow 3 mapping TEID 3 .
  • the first core network device is a device in the network where the first access network device is connected to the first access network.
  • the first message may further include a mapping relationship between each flow and the RB used by the terminal in the network where the first access network device is located.
  • Step 903 After receiving the first message sent by the first access network device, the first core network device sends a second message to the second core network device, requesting to switch the terminal to the second access network. device.
  • the second message may include a fourth mapping relationship, where the fourth mapping relationship is a mapping relationship between each stream and the TEID used by the terminal in the network where the first access network device is located.
  • the fourth mapping relationship may be: flow 0 mapping TEID 0, flow 1 mapping TEID 1, flow 2 mapping TEID 2, and flow 3 mapping TEID 3.
  • the second message may also include one or more sets of TFT filter template parameters and corresponding QoS categories used by the first core network device.
  • a set of TFT filter template parameters includes: a source IP address, Source port number, destination IP address, destination port number, protocol type.
  • Step 904 After receiving the second message sent by the first core network device, the second core network device sends a third message to the second access network device, requesting to switch the terminal to the second access network. device.
  • the second core network device may also determine, according to each of the flows of the terminal, the RBs mapped in the network where the second access network device is located, that is, the third mapping relationship, for example: The second core network device determines two RBs, which are RB A and RB B respectively, and the third mapping relationship determined by the second core network device is: flow 0 and flow 1 map RB A, flow 2 and flow 3 map RB B.
  • the third message may include the following mapping relationship: flow 0 mapping TEID 0, flow 1 mapping TEID 1, flow 2 mapping TEID 2, flow 3 mapping TEID 3; flow 0 and flow 1 mapping RB A, flow 2 and flow 3 Map RB B.
  • Step 905 The second access network device sends a third response message to the second core network device.
  • the second access network device After receiving the third message, the second access network device determines to receive the data packet sent by the first access network device according to a TEID of each flow, and determines the network where the second access network is located in the terminal.
  • the first mapping relationship may be: flow 0 mapping TEID 0', flow 1 mapping TEID 1', flow 2 mapping TEID 2', and flow 3 mapping TEID 3'.
  • the second access network device sends the foregoing mapping relationship to the first access network device by using a third response message.
  • Step 906 The second core network device sends a second response message to the first core network device.
  • the first mapping relationship and the third mapping relationship may be included in the second response message.
  • Step 907 The first core network device sends a first response message to the first access network device.
  • the first mapping message and the third mapping relationship may be included in the first response message.
  • Step 908 The first access network device sends a handover command to the terminal.
  • a third mapping relationship may be included in the handover command.
  • the first access network device sends the data packet of each stream of the terminal through a tunnel according to the first mapping relationship. To the second access network device. In this way, the second access network device knows which stream the data packet belongs to according to the tunnel in which the data packet is received.
  • the second access network device may also require the first access network device to "establish a tunnel according to each RB.”
  • the second access network device may determine the same TEID for the flow that is mapped to the same RB, that is, the first mapping relationship determined by the second access network device may be: flow 0 mapping TEID 0 ', flow 1 maps TEID 0', flow 2 maps TEID 1', and flow 3 maps TEID 1'.
  • the second access network device sends the foregoing mapping relationship to the first access network device by using the third response message.
  • the terminal determines, according to the PDCP status report generated by the second access network device, to which RB the data packet is transmitted. Specifically, for the data packet that is embodied as “hole” in the PDCP status report, the terminal sends the data packet of the hole through the RB before the RB change of the flow mapping; for the data packet that is not reflected as “hole” in the PDCP status report, the terminal The RBs that have been changed by the RB of the stream map send these packets that are not reflected as "holes". If the terminal does not receive the PDCP status report, all the data packets are transmitted in the RB after the RB change of the flow map.
  • the first access network device transmits the data packet to the second access network device through the tunnel according to the third mapping relationship.
  • the third mapping relationship is: flow 0 and flow 3 map to RB A, flow 1 and flow 2 are mapped to RB B.
  • the first access network device forwards the data packets of flow 0 and flow 3 to the tunnel corresponding to the RB A according to the third mapping relationship, and forwards the data packets of flow 1 and flow 2 to the tunnel corresponding to the RB B.
  • the first access network device does not send the packet sequence number of each data packet, and after the data packet arrives at the second access network device, the second access network device reallocates data for each data packet.
  • Package serial number is used to allocate packet sequence number of each data packet.
  • the method includes:
  • Step 1001 The first access network device sends a first message to the first core network device, where the first message is used to request to switch the terminal from the first access network device to the second access network device.
  • Step 1002 The first access network device receives a first response message that is returned by the first core network device and includes a first mapping relationship, where the first mapping relationship is that the second access network device is The mapping relationship between each RB and the TEID determined by the terminal;
  • Step 1003 The first access network device forwards a data packet of each RB of the terminal to the second access network device according to the first mapping relationship.
  • the first access network device may receive the measurement report sent by the terminal.
  • the first access network device After receiving the measurement report, the first access network device performs a handover decision according to the handover algorithm. After determining that the handover needs to be performed, step 1001 is performed.
  • the first message sent by the first access network device may further include at least one of the following:
  • the fourth mapping relationship is a mapping relationship between each RB and the TEID used by the terminal in the network where the first access network device is located.
  • the first core network device After receiving the first message, the first core network device sends a second message to the second core network device.
  • the second message may include the following content:
  • a fourth mapping relationship a TFT (Traffic Flow Template) template used by each RB of the terminal in the network where the first core network device is located.
  • the second message may also include one or more sets of TFT filter template parameters and corresponding QoS categories used by the first core network device.
  • a set of TFT filter template parameters includes: a source IP address, Source port number, destination IP address, destination port number, protocol type.
  • the second core network device may use, according to the TFT template used by the network where the first core network device is located, and each RB of the terminal according to each RB of the terminal.
  • the TFT template used by the network where the second core network device is located determines a second mapping relationship; the second mapping relationship is each flow and RB used by the terminal in the network where the first access network device is located. Mapping relationship.
  • the second core network device then sends a third message including the second mapping relationship to the second access network device for requesting to switch the terminal from the first access network device to the second access network device.
  • the third message may further include a TFT template used by each RB of the terminal in a network where the second core network device is located.
  • the second access network device After receiving the third message that is sent by the second core network device and includes the second mapping relationship, the second access network device returns, to the second core network device, a third response message that includes the first mapping relationship; the first mapping The relationship is a mapping relationship between each RB and the TEID determined by the second access network device for the terminal.
  • the TEID of each RB mapping in the first mapping relationship is the same; or the TEID of each RB mapping in the first mapping relationship is different.
  • the third response message further includes mapping relationship mapping indication information, where the mapping relationship mapping indication information is used to indicate that the terminal determined by the second access network device is in the second access network.
  • mapping relationship mapping indication information is used to indicate that the terminal determined by the second access network device is in the second access network.
  • the mapping relationship between each RB and the stream used in the network in which the device is located is the same as the second mapping relationship.
  • the third response message may further include a sequence indication message, where the first access network device is configured to carry the first packet in the data packet that forwards the terminal to the second access network device.
  • the sequence number of the packet assigned by an access network device can refer to the PDCP SN.
  • the second core network device After receiving the third response message that is returned by the second access network device and including the first mapping relationship, the second core network device sends a second response message to the first core network device.
  • the second response message includes a first mapping relationship.
  • step 1002 after receiving the first response message, the first access network device sends a handover command to the terminal to instruct the terminal to access the second access network device.
  • step 1003 when the first access network device forwards the data packet of each RB of the terminal to the second access network device, the data packet sequence number of each data packet may also be sent to the second The access network device may, of course, not transmit the sequence number of the data packet of each data packet, and is determined according to actual conditions.
  • the data packets sent by the first access network device to the second access network device may be divided into two types of data packets, and one type of data packet has been sent to the terminal through the air interface but has not been determined yet. Whether the terminal correctly receives the data packet; one type of data packet is a data packet that has not been sent to the terminal through the air interface.
  • FIG. 11 is a schematic diagram of a data switching process provided by an embodiment of the present application.
  • FIG. 11 corresponds to the comparison scenario 4 in Table 1, that is, the first access network device processes the data packet according to the RB-RB manner, and the second access network device processes the data packet according to the flow-RB manner.
  • Step 1101 The terminal reports the measurement report to the first access network device.
  • the specific content of the measurement report can be referred to the description in the existing standard, which is not limited by the embodiment of the present application.
  • the terminal has 4 flows, which are flow 0, flow 1, flow 2, and flow 3.
  • Flow 0 and flow 1 are mapped to RB A; flow 2 and flow 3 are mapped to RB B.
  • Step 1102 The first access network device determines to trigger the handover process according to the received measurement report, and sends a first message to the first core network device, for requesting to switch the terminal to the second access network device.
  • the first access network device determines that a tunnel is established for each RB.
  • the first access network device allocates one TEID to each RB. Therefore, the first message may include a fourth mapping relationship, that is, the terminal is in the first The mapping relationship between each RB and TEID used in the network where the access network device is located. For example, RB A maps TEID 0 and RB B maps TEID1.
  • Step 1103 After receiving the first message sent by the first access network device, the first core network device sends a second message to the second core network device, requesting to switch the terminal to the second access network. device.
  • the second message may include a mapping relationship between each RB and the TEID used by the terminal in the network where the first access network device is located, and a network where each RB of the terminal is located in the first core network device.
  • Step 1104 The second core network device determines a second mapping relationship.
  • the second core network device may be configured according to a TFT template used by each RB of the terminal in a network where the first core network device is located, and a network where each RB of the terminal is located in the second core network device.
  • the TFT template used determines the second mapping relationship, that is, the flow 0 and the flow 1 are mapped to the RB A; the flow 2 and the flow 3 are mapped to the RB B.
  • Step 1105 The second core network device sends a third message to the second access network device, requesting to switch the terminal to The second access network device.
  • the second mapping relationship and the fourth mapping relationship may be included in the third message.
  • Step 1106 The second access network device sends a third response message to the second core network device.
  • the second access network device After receiving the third message, the second access network device determines to receive the data packet sent by the first access network device according to the manner in which each RB maps one TEID, and determines the TEID mapped by each RB on the side of the RB.
  • the first mapping relationship may be: RB A mapping TEID 0', RB B mapping TEID 1'.
  • the second access network device sends the foregoing mapping relationship to the first access network device by using a third response message.
  • Step 1107 The second core network device sends a second response message to the first core network device.
  • the first mapping relationship may be included in the second response message.
  • Step 1108 The first core network device sends a first response message to the first access network device.
  • the first mapping relationship may be included in the first response message.
  • Step 1109 The first access network device sends a handover command to the terminal.
  • the first access network device sends the data packet of each RB of the terminal to the second access network device through a tunnel according to the first mapping relationship.
  • the second access network device knows which stream the data packet belongs to according to the tunnel in which the data packet is received.
  • the second access network device may determine, according to the second mapping relationship, whether the mapping between the flow and the RB used by the terminal in the network where the second access network device is located is The flow used by the terminal in the network where the first access network device is located is the same as the RB mapping relationship. If the same, the second access network device carries the mapping relationship mapping indication information in the third response message sent in step 1106.
  • the mapping relationship mapping indication information is used to indicate that the mapping relationship between each RB and the flow used by the terminal in the network where the second access network device is located is determined by the second access network device.
  • the second mapping relationship is the same.
  • the third access message sent by the second access network device in step 1106 carries a sequence indication message, which is used to indicate that the first access network device forwards the terminal to the second access network device.
  • the data packet carries the sequence number of the data packet allocated by the first access network device; thereby requesting the first access network device to carry the data packet sequence number of each data packet when performing data packet forwarding, so that the entire handover
  • the packet processing of the process is exactly the same as the internal handover of LTE.
  • the first access network device may map the same TEID to all RBs, that is, all RB data packets are forwarded to the second access network device via one tunnel.
  • the second access network device uses the TFT template used by the RB of the terminal in the network where the second core network device is located to filter the received data packet into multiple The stream is then transmitted in the network in which the second core network device is located.
  • the first access network device may map the same TEID to all RBs, that is, all RB data packets are forwarded to the second access network device via one tunnel.
  • the second access network device carries the sequence indication message in the third response message sent in step 1106, so as to request the first access network device to carry the data packet sequence number of each data packet when performing data packet forwarding, After the second access network device receives the data packet, the second access network device deletes the data packet sequence number allocated by the first access network in the data packet of each RB of the terminal.
  • the second access network device determines an RB to which the data packet of each of the flows belongs; then for the data packets in each RB, the second access network device uses the first of each data packet
  • the data packet sequence allocated by the access network performs data aggregation processing on the data packets of each RB.
  • the second access network device may use the TFT template used by the RB of the terminal in the network where the second core network device is located to filter the received data packet into multiple flows, and then Determining the number of each stream using each TFT of the terminal in the TFT template used by the network in which the first core network device is located According to the RB to which the packet belongs, data aggregation processing, such as PDCP processing, is performed according to the packet sequence number allocated by each packet of the first access network device, and is transmitted in the air interface.
  • data aggregation processing such as PDCP processing
  • the access network device allocates uplink resources to the terminal, it allocates physical resources and specifies the MCS value used by the terminal. Once these two parameters are determined, the probability of success of the terminal transmitting the uplink data is determined. Generally, the transmission success probability is 90. %.
  • the MAC layer of the terminal multiplexes the data of each RB, which is equivalent to the transmission success probability provided by the MAC layer for each RB. Based on this idea, when the MAC entity multiplexes data from each RB, only the relative priorities of the RBs can be considered, regardless of the reliability of the underlying transmission resources.
  • the transmission success probability of correctly transmitting data on the uplink resource allocated for the terminal may be determined, and the transmission success probability is notified to the terminal. Thereby improving resource utilization.
  • FIG. 12 is a schematic flowchart of a data processing method provided by an embodiment of the present application.
  • the method includes:
  • Step 1201 The access network device allocates the uplink resource to the terminal.
  • Step 1202 The access network device sends first indication information to the terminal, where the first indication information is used to indicate a transmission success rate of data correctly transmitted on the uplink resource.
  • Step 1203 The terminal determines an uplink resource allocated by the access network device for the terminal, and receives first indication information sent by the access network device.
  • Step 1204 The terminal transmits data on the uplink resource according to the first indication information.
  • the access network device may allocate an uplink resource to the terminal after receiving the resource request sent by the terminal.
  • the resource request sent by the terminal may be a Scheduling Request (SR), or may be a message for requesting an uplink resource, such as a Buffer Status Reports (BSR), which is not limited in this embodiment of the present application.
  • SR Scheduling Request
  • BSR Buffer Status Reports
  • the access network device may also allocate uplink resources to the terminal in other situations, and details are not described herein again.
  • step 1202 as described above, once the uplink resource allocated by the access network device and the MCS value used by the specified terminal are determined, the probability of success of the terminal transmitting the uplink data on the uplink resource is determined.
  • the access network device determines the transmission success rate of the data to be correctly transmitted on the uplink resource, which is not limited in this embodiment of the present application.
  • the first indication information may be a specific value of a transmission success rate.
  • the first indication information may also be an index value, where the index value corresponds to a specific value of a transmission success rate.
  • the access network device may send a comparison table to the terminal through dedicated signaling in advance, and the comparison table includes multiple index values, and each index value corresponds to one transmission success probability.
  • the index value may be indicated.
  • the tables used by the terminals in the same cell may be different or the same.
  • the access network device sends a comparison table to the terminal by using broadcast signaling, where the comparison table includes multiple index values, and each index value corresponds to one transmission success probability.
  • the index value may be indicated.
  • a comparison table may be specified by the protocol, and the comparison table includes a plurality of index values, and each index value corresponds to a transmission success probability.
  • the access network device may also determine the RB configuration information when the RB is configured for the terminal.
  • the configuration information indicates to the terminal that the data packet in the configured RB can only use the resource whose transmission success probability is greater than a preset threshold. Transfer. In this way, the terminal can determine the resources used to transmit the data packets in each RB according to the configuration information of each RB.
  • the access network device may send the first indication information and the uplink resource allocation indication information that is generated by the terminal in the same message, and may also be sent separately, which is not limited in this embodiment of the present application.
  • the uplink resource allocation indication information is used to indicate to the terminal an uplink resource allocated to the terminal.
  • the terminal determines how the terminal allocates the uplink resource to the access network device.
  • the embodiment of the present application is not limited.
  • step 1204 when the MAC entity of the terminal generates the uplink data transmission block, the transmission success rate indicated by the first indication information is taken into consideration. For example, if the terminal finds that the success probability of the uplink resource obtained by the terminal is relatively high, the priority is sent. If the terminal finds that the success probability of the uplink resource obtained by the terminal is relatively low, the data of the service with low priority and long delay budget is sent.
  • the terminal if it is determined that the transmission success rate indicated by the first indication information is greater than the first threshold, transmits, on the uplink resource, data corresponding to the service whose priority is greater than the first preset priority; If the terminal determines that the transmission success rate indicated by the first indication information is less than the second threshold, the terminal transmits data corresponding to the service whose priority is lower than the second preset priority on the uplink resource.
  • the first threshold and the second threshold may be determined according to actual conditions, which is not limited by the embodiment of the present application.
  • the foregoing solution can be used not only for the scenario where the access network device dynamically allocates resources, but also for the scenario of semi-statically allocating resources.
  • the access network device pre-allocates a set of radio resources, which respectively correspond to different transmission success probabilities.
  • the terminal uses a specific radio resource to transmit data, it first determines the transmission success probability corresponding to the radio resource, and then correspondingly according to the radio resource corresponding to the radio resource. The probability of successful transmission determines which RB's data can be transmitted using this wireless resource.
  • each network element such as a terminal, a base station, etc.
  • each network element includes hardware structures and/or software modules corresponding to each function.
  • the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • the embodiment of the present application further provides a data processing apparatus, which may perform the method flow described in FIG. 1 and may implement the first device implemented in the method flow described in FIG. 2 to FIG. Features.
  • FIG. 13 a schematic structural diagram of a data processing apparatus according to an embodiment of the present application is provided.
  • the apparatus includes:
  • the processing unit 1301 is configured to determine a flow to which the data packet belongs, and determine a flow identifier according to the flow to which the data packet belongs;
  • the transceiver unit 1302 is configured to send the data packet including the flow identifier to the second access network device.
  • the processing unit 1301 is specifically configured to:
  • a flow identifier corresponding to the flow to which the data packet belongs is determined from a flow identifier list sent by the third device.
  • FIG. 1 For other contents of the apparatus described in FIG. 13, reference may be made to FIG. 1 and the description related to FIG. 1, and details are not described herein again.
  • the embodiment of the present application further provides a data processing apparatus, which can perform the method flow described in FIG. 4 and can perform the functions implemented by the first device in the method flow described in FIG. 5.
  • FIG. 14 a schematic structural diagram of a data processing apparatus is provided in an embodiment of the present application.
  • the apparatus includes:
  • the processing unit 1401 is configured to determine, after the radio bearer RB of the first stream mapping is changed from the first RB to the second RB, to end the data packet, where the end data packet is sent by the first device by using the first RB The last packet of the first stream;
  • the transceiver unit 1402 is configured to send the end indication information and the end data packet to the second device, where the end indication information is used to indicate that the first device sends the data packet that belongs to the first stream by using the first RB. Has been sent.
  • FIG. 4 For other contents of the apparatus described in FIG. 14, reference may be made to FIG. 4 and the description related to FIG. 4, and details are not described herein again.
  • the embodiment of the present application further provides a data processing apparatus, which can perform the method flow described in FIG. 4 and can perform the functions implemented by the second device in the method flow described in FIG. 5.
  • FIG. 15 a schematic structural diagram of a data processing apparatus is provided in an embodiment of the present application.
  • the apparatus includes:
  • the transceiver unit 1501 is configured to receive end indication information sent by the first device, where the end indication information is sent after the first device sends the last data packet belonging to the first flow by using the first radio bearer RB;
  • the indication information is used to indicate that the data packet that belongs to the first flow that is sent by the first device by using the first RB has been sent;
  • the processing unit 1502 is configured to process the data packet that belongs to the first stream that is received by the second RB.
  • FIG. 4 For other contents of the apparatus described in FIG. 15, reference may be made to FIG. 4 and the description related to FIG. 4, and details are not described herein again.
  • the embodiment of the present application further provides a data processing apparatus, which may perform the method flow described in FIG. 6 and may implement the first access network device implemented in the method flow described in FIG. Features.
  • FIG. 16 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application.
  • the apparatus includes:
  • the transceiver unit 1601 is configured to send a first message to the second access network device, to request to switch the terminal to the second access network device, and receive the first mapping relationship that is returned by the second access network device a first response message; the first mapping relationship is a mapping relationship between each stream in the terminal and a tunnel endpoint identifier TEID;
  • the processing unit 1602 is configured to forward, according to the first mapping relationship, a data packet of each flow of the terminal to the second access network device.
  • the embodiment of the present application further provides a data processing apparatus, which may perform the method flow described in FIG. 6 and may implement the second access network device implemented in the method flow described in FIG. Features.
  • FIG. 17 a schematic structural diagram of a data processing apparatus is provided in an embodiment of the present application.
  • the apparatus includes:
  • the transceiver unit 1701 is configured to receive a first message sent by the first access network device, to request to switch the terminal to the second access network device, and return a first mapping relationship to the first access network device. a first response message, and receiving a data packet of each flow of the terminal that is forwarded by the first access network device according to the first mapping relationship; the first mapping relationship is the second access network The mapping relationship between each stream and the TEID in the terminal determined by the device.
  • the embodiment of the present application further provides a data processing apparatus, which may perform the method flow described in FIG. 10, and may implement the first access network device implemented in the method flow described in FIG. Features.
  • FIG. 18 a schematic structural diagram of a data processing apparatus is provided in an embodiment of the present application.
  • the apparatus includes:
  • the transceiver unit 1801 is configured to send a first message to the first core network device, to request to switch the terminal from the first access network device to the second access network device, and receive the returned by the first core network device.
  • a first response message including a first mapping relationship; the first mapping relationship is a mapping relationship between each RB and a TEID determined by the second access network device for the terminal;
  • the processing unit 1802 is configured to forward, according to the first mapping relationship, a data packet of each RB of the terminal to the second access network device.
  • FIG. 10 For other contents of the apparatus described in FIG. 18, reference may be made to FIG. 10 and the description related to FIG. 10, and details are not described herein again.
  • FIG. 19 a schematic structural diagram of a data processing apparatus is provided in an embodiment of the present application.
  • the apparatus includes:
  • the processing unit 1901 is configured to determine a second mapping relationship, where the second mapping relationship is a mapping relationship between each RB and a stream used by the terminal in the network where the first access network device is located; the second mapping The relationship is determined by a TFT template used by each RB of the terminal in a network in which the first core network device is located and a TFT template used by each RB of the terminal in a network in which the second core network device is located ;
  • the transceiver unit 1902 is configured to send, to the second access network device, a third message that includes the second mapping relationship, to request to switch the terminal from the first access network device to the second access network device.
  • FIG. 10 For other contents of the apparatus described in FIG. 19, reference may be made to FIG. 10 and the description related to FIG. 10, and details are not described herein again.
  • FIG. 20 a schematic structural diagram of a data processing apparatus is provided in an embodiment of the present application.
  • the apparatus includes:
  • the transceiver unit 2001 is configured to receive a third message that is sent by the second core network device and includes a second mapping relationship, and is configured to request to switch the terminal from the first access network device to the second access network device, where the The second mapping relationship is a mapping relationship between the RB and the flow used by the terminal in the network where the first access network device is located; and a response message including the first mapping relationship is returned to the second core network device;
  • the first mapping relationship is a mapping relationship between each RB and the TEID determined by the second access network device for the terminal.
  • FIG. 10 For other contents of the apparatus described in FIG. 20, reference may be made to FIG. 10 and the description related to FIG. 10, and details are not described herein again.
  • FIG. 21 a schematic structural diagram of a data processing apparatus is provided in an embodiment of the present application.
  • the apparatus includes:
  • the processing unit 2101 is configured to allocate the uplink resource to the terminal.
  • the transceiver unit 2102 is configured to send first indication information to the terminal, where the first indication information is used to indicate a transmission success rate of data correctly transmitted on the uplink resource.
  • FIG. 12 For other contents of the apparatus described in FIG. 21, reference may be made to FIG. 12 and the description related to FIG. 12, and details are not described herein again.
  • FIG. 22 a schematic structural diagram of a data processing apparatus is provided in an embodiment of the present application.
  • the apparatus includes:
  • the processing unit 2201 is configured to determine, by the access network device, the uplink resource that is allocated by the access network device, and receive the first indication information that is sent by the access network device, where the first indication information is used to indicate that the data is in the uplink resource.
  • the transmission success rate of the correct transmission is configured to determine, by the access network device, the uplink resource that is allocated by the access network device, and receive the first indication information that is sent by the access network device, where the first indication information is used to indicate that the data is in the uplink resource.
  • the transceiver unit 2202 is configured to transmit data on the uplink resource according to the first indication information.
  • FIG. 12 For other contents of the apparatus described in FIG. 22, reference may be made to FIG. 12 and the description related to FIG. 12, and details are not described herein again.
  • the embodiment of the present application further provides a data processing apparatus, which may perform the method flow described in FIG. 1 and may implement the first device implemented in the method flow described in FIG. 2 to FIG. Features.
  • FIG. 23 a schematic structural diagram of a data processing apparatus is provided in an embodiment of the present application.
  • the apparatus includes:
  • the processor 2301 is configured to determine a flow to which the data packet belongs, and determine a flow identifier according to the flow to which the data packet belongs;
  • the transceiver 2302 is configured to send the data packet including the flow identifier to the second access network device.
  • FIG. 1 For other contents of the apparatus described in FIG. 23, reference may be made to FIG. 1 and the description related to FIG. 1, and details are not described herein again.
  • the embodiment of the present application further provides a data processing apparatus, which can perform the method flow described in FIG. 4 and can perform the functions implemented by the first device in the method flow described in FIG. 5.
  • FIG. 24 a schematic structural diagram of a data processing apparatus is provided in an embodiment of the present application.
  • the apparatus includes:
  • the processor 2401 is configured to determine, after the radio bearer RB of the first stream mapping is changed from the first RB to the second RB, to end the data packet, where the end data packet is sent by the first device by using the first RB.
  • the transceiver 2402 is configured to send the end indication information and the end data packet to the second device, where the end indication information is used to indicate that the first device sends the data packet that belongs to the first flow by using the first RB. Has been sent.
  • the embodiment of the present application further provides a data processing apparatus, which can perform the method flow described in FIG. 4 and can perform the functions implemented by the first device in the method flow described in FIG. 5.
  • FIG. 25 a schematic structural diagram of a data processing apparatus is provided in an embodiment of the present application.
  • the apparatus includes:
  • the transceiver 2501 is configured to receive end indication information sent by the first device, where the end indication information is sent after the first device sends the last data packet belonging to the first flow by using the first radio bearer RB;
  • the indication information is used to indicate that the data packet that belongs to the first flow that is sent by the first device by using the first RB has been sent;
  • the processor 2502 is configured to process the data packet that is received by the second RB and belongs to the first stream.
  • the embodiment of the present application further provides a data processing apparatus, which can be implemented in FIG.
  • FIG. 26 is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application.
  • the apparatus includes:
  • the transceiver 2601 is configured to send a first message to the second access network device, to request to switch the terminal to the second access network device, and receive the first mapping relationship that is returned by the second access network device a first response message; the first mapping relationship is a mapping relationship between each stream in the terminal and a tunnel endpoint identifier TEID;
  • the processor 2602 is configured to forward, according to the first mapping relationship, a data packet of each stream of the terminal to the second access network device.
  • the embodiment of the present application further provides a data processing apparatus, which may perform the method flow described in FIG. 6 and may implement the second access network device implemented in the method flow described in FIG. Features.
  • FIG. 27 a schematic structural diagram of a data processing apparatus is provided in an embodiment of the present application.
  • the apparatus includes a transceiver 2701, a processor 2702.
  • the transceiver 2701 is configured to receive a first message sent by the first access network device, to request to switch the terminal to the second access network device, and return a first mapping relationship to the first access network device. a first response message, and receiving a data packet of each flow of the terminal that is forwarded by the first access network device according to the first mapping relationship; the first mapping relationship is the second access network The mapping relationship between each stream and the TEID in the terminal determined by the device.
  • the embodiment of the present application further provides a data processing apparatus, which may perform the method flow described in FIG. 10, and may implement the first access network device implemented in the method flow described in FIG. Features.
  • FIG. 18 a schematic structural diagram of a data processing apparatus is provided in an embodiment of the present application.
  • the apparatus includes:
  • the transceiver 2801 is configured to send a first message to the first core network device, to request to switch the terminal from the first access network device to the second access network device, and receive the first core network device to return a first response message including a first mapping relationship;
  • the first mapping relationship is a mapping relationship between each RB and a TEID determined by the second access network device for the terminal;
  • the processor 2802 is configured to forward, according to the first mapping relationship, a data packet of each RB of the terminal to the second access network device.
  • FIG. 10 For other contents of the apparatus described in FIG. 28, reference may be made to FIG. 10 and the description related to FIG. 10, and details are not described herein again.
  • FIG. 29 a schematic structural diagram of a data processing apparatus is provided in an embodiment of the present application.
  • the apparatus includes:
  • the processor 2901 is configured to determine a second mapping relationship, where the second mapping relationship is a mapping relationship between each RB and a flow used by the terminal in the network where the first access network device is located; the second mapping The relationship is determined by a TFT template used by each RB of the terminal in a network in which the first core network device is located and a TFT template used by each RB of the terminal in a network in which the second core network device is located ;
  • the transceiver 2902 is configured to send, to the second access network device, a third message that includes the second mapping relationship, to request to switch the terminal from the first access network device to the second access network device.
  • FIG. 10 For other contents of the apparatus described in FIG. 29, reference may be made to FIG. 10 and the description related to FIG. 10, and details are not described herein again.
  • FIG. 30 a schematic structural diagram of a data processing apparatus is provided in an embodiment of the present application.
  • the apparatus includes a transceiver 3001 and a processor 3002.
  • the transceiver 3001 is configured to receive, by the second core network device, a third message that includes a second mapping relationship, and is configured to request to switch the terminal from the first access network device to the second access network device, where
  • the second mapping relationship is a mapping relationship between the RB and the flow used by the terminal in the network where the first access network device is located; and a response message including the first mapping relationship is returned to the second core network device;
  • the first mapping relationship is a mapping relationship between each RB and the TEID determined by the second access network device for the terminal.
  • FIG. 10 For other contents of the apparatus described in FIG. 30, reference may be made to FIG. 10 and the description related to FIG. 10, and details are not described herein again.
  • FIG. 31 a schematic structural diagram of a data processing apparatus is provided in an embodiment of the present application.
  • the apparatus includes:
  • the processor 3101 is configured to allocate the uplink resource to the terminal.
  • the transceiver 3102 is configured to send first indication information to the terminal, where the first indication information is used to indicate a transmission success rate of data correctly transmitted on the uplink resource.
  • FIG. 12 For other contents of the apparatus described in FIG. 31, reference may be made to FIG. 12 and the description related to FIG. 12, and details are not described herein again.
  • FIG. 32 a schematic structural diagram of a data processing apparatus is provided in an embodiment of the present application.
  • the apparatus includes:
  • the processor 3201 is configured to determine, by the access network device, the uplink resource allocated by the access network device, and receive the first indication information that is sent by the access network device, where the first indication information is used to indicate that the data is in the uplink resource.
  • the transmission success rate of the correct transmission is configured to determine, by the access network device, the uplink resource allocated by the access network device, and receive the first indication information that is sent by the access network device, where the first indication information is used to indicate that the data is in the uplink resource.
  • the transceiver 3202 is configured to transmit data on the uplink resource according to the first indication information.
  • FIG. 12 For other contents of the apparatus described in FIG. 32, reference may be made to FIG. 12 and the description related to FIG. 12, and details are not described herein again.
  • the transceiver can be a wired transceiver, a wireless transceiver, or a combination thereof.
  • the wired transceiver can be, for example, an Ethernet interface.
  • the Ethernet interface can be an optical interface, an electrical interface, or a combination thereof.
  • the wireless transceiver can be, for example, a wireless local area network transceiver, a cellular network transceiver, or a combination thereof.
  • the processor may be a central processing unit (English: central processing unit, abbreviated: CPU), a network processor (English: network processor, abbreviated: NP) or a combination of CPU and NP.
  • the processor may further include a hardware chip.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (abbreviated as PLD), or a combination thereof.
  • the above PLD can be a complex programmable logic device (English: complex programmable logic device, abbreviation: CPLD), field-programmable gate array (English: field-programmable gate array, abbreviation: FPGA), general array logic (English: generic array Logic, abbreviation: GAL) or any combination thereof.
  • the memory may include a volatile memory (English: volatile memory), such as random access memory (English: random-access memory, abbreviation: RAM); the memory may also include non-volatile memory (English: non-volatile memory).
  • read-only memory English: read-only memory, abbreviation: ROM
  • flash memory English: flash memory
  • hard disk English: hard disk drive, abbreviation: HDD
  • solid state drive English: solid-state drive, Abbreviation: SSD
  • the memory can also include the above A combination of types of memory.
  • the bus interface may also be included in FIG. 23 to FIG. 32.
  • the bus interface may include any number of interconnected buses and bridges, and specifically, various circuits of the memory represented by one or more processors and memories represented by the processor. Linked together.
  • the bus interface 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.
  • the bus interface provides an interface.
  • the transceiver provides means for communicating with various other devices on a transmission medium.
  • the processor is responsible for managing the bus architecture and the usual processing, and the memory can store the data that the processor uses when performing operations.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种数据处理方法及装置，包括：第一设备确定数据包所属的流；所述第一设备根据所述数据包所属的流确定流标识，并向第二设备发送包括所述流标识的所述数据包。

Description

一种数据处理方法及装置
本申请要求在2016年8月15日提交中国国家知识产权局、申请号为201610673593.7、发明名称为“一种数据处理方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及移动通信技术领域，尤其涉及一种数据处理方法及装置。
背景技术
现在的LTE(Long Term Evolution，长期演进系统)中，数据的传输是基于RB(Radio Bearer，无线承载)的，LTE系统按照各种应用的QoS(Quality of Service，服务质量)需求，将数据划分成一个或多个DRB(Data Radio Bearer，数据无线承载)。具体地，对下行数据，PGW(Public Data Network GateWay，公用数据网网关)通过TFT(Traffic Flow Template，业务流模板)将数据过滤，把数据包映射到各个承载；对上行数据，终端内部实现数据过滤，将数据包映射到各个承载。从RAN(Radio Access Network，无线接入网)的角度，只能看到一个或多个RB，通过对不同RB配置不同的空口处理参数，实现对各个RB的数据的区别对待。每个DRB内部的数据在无线接入网设备侧都按相同的待遇处理，不同DRB的数据，在无线接入网设备侧的待遇不同。
在正在讨论的5G(the fifth generation,第五代移动通信网络)中，要求对业务数据实施更加精细的QoS处理，也就引入了“流(flow)”的概念，即可以将一个RB中的数据包划分为多个flow的数据包。目前，如何实现将数据包按照flow级别处理，还没有一种解决方案。
发明内容
本申请实施例提供一种数据处理方法及装置，用以实现发送方向接收方指示每个数据包所属的流，从而实现将数据包按照flow级别处理，从而提高数据包的处理效率。
第一方面，本申请实施例提供一种数据处理方法，包括：
第一设备确定数据包所属的流；
所述第一设备根据所述数据包所属的流确定流标识，并向第二设备发送包括所述流标识的所述数据包。
根据本申请实施例提供的方法，第一设备在确定出数据包的流标识后，并通过所述数据包向第二接入网设备发送所述流标识，从而向第二设备指示出所述数据包所属的流。根据该方法，可以使得第二设备按照流级别对数据包进行处理，进一步的，可以改善端对端的QoS的性能。
可选的，所述第一设备根据所述数据包所属的流确定流标识，包括：
所述第一设备根据所述数据包所属的流为所述数据包分配所述流标识；或者
所述第一设备从第三设备发送的流标识列表中确定与所述数据包所属的流对应的流标识。
根据上述方法，第一设备直接为数据包分配流标识，或者第一设备根据第三设备发送的流标识列表为数据包确定流标识，从而可以实现快速的确定数据包的流标识，提高确定数据包流标识的效率。
可选的，所述流标识位于所述数据包的包头。
可选的，所述流标识位于所述数据包的数据包序列号字段中，并占据所述数据包序列号字段中的K个比特位，K为正整数。
根据上述方法，直接采用数据包序列号字段中的K个比特位承载流标识，可以不改变现有数据包的结构，达到区分每个数据包所属的流的目的。
可选的，所述第一设备接收数据包之后，还包括：
所述第一设备将属于同一个流的所有数据包作为一组，并分别为每一组数据包独立分配数据包序列号；
所述第一设备将所述流标识通过所述数据包发送给第二设备之前，还包括：
所述第一设备根据所述数据包的数据包序列号字段中除了所述流标识所占据的比特位之外的比特位对所述数据包进行头压缩和加密操作。
根据上述方法，第一设备将分别为每一组数据包独立分配数据包序列号，从而在对所述数据包进行头压缩和加密操作时，根据所述数据包的数据包序列号字段中除了所述流标识所占据的比特位之外的比特位对所述数据包进行头压缩和加密操作，可以在数据包中携带流标识的同时，避免对头压缩和加密算法进行改动，能够与现有技术相兼容。
第二方面，本申请实施例提供一种数据处理装置，包括：
处理单元，用于确定数据包所属的流；根据所述数据包所属的流确定流标识；
收发单元，用于向第二接入网设备发送包括所述流标识的所述数据包。
第三方面，本申请实施例提供一种数据处理装置，包括：
处理器，用于确定数据包所属的流；根据所述数据包所属的流确定流标识；
收发机，用于向第二接入网设备发送包括所述流标识的所述数据包。
第四方面，本申请实施例提供一种数据处理方法，包括：
当第一流映射的无线承载RB由第一RB更改为第二RB后，第一设备确定结束数据包，所述结束数据包为所述第一设备通过所述第一RB发送的属于所述第一流的最后一个数据包；
所述第一设备向第二设备发送结束指示信息以及所述结束数据包；所述结束指示信息用于指示所述第一设备通过所述第一RB发送的属于所述第一流的数据包已经发送完毕。
根据本申请实施例提供的方法，在第一流映射的RB改变时，第一设备通过发送结束指示信息向第二设备指示出第一设备通过第一RB发送的属于所述第一流的最后一个数据包，从而能够保证第二设备按照数据包的顺序处理每个数据包，避免数据包乱序。
可选的，所述第一设备确定结束数据包之后，还包括：
所述第一设备将所有未发送的且属于所述第一流的数据包通过所述第二RB发送。
根据上述方法，第一设备可以实现在第一流映射的RB改变时，准确的确定通过改变后的RB传输的数据包，避免数据包出现乱序。
可选的，第一设备确定与第一流映射的无线承载RB由第一RB更改为第二RB，包括：
所述第一设备接收第三设备发送的重映射指令，并根据重映射指令确定与第一流映射的RB由第一无线承载RB更改为第二RB。
可选的，所述第一设备确定结束数据包，包括：
所述第一设备将通过所述第一RB发送的所有属于所述第一流的待确认数据包中的最后一个数据包确定为所述结束数据包，所述待确认数据包为已经发送但未确定接收方是否正确接收到的数据包。
根据上述方法，通过将所有属于所述第一流的待确认数据包中的最后一个数据包确定为结束数据包，从而能够准确的确定结束数据包。
可选的，所述第一设备向第二设备发送结束指示信息以及所述结束数据包，包括：
所述第一设备向所述第二设备发送包括所述结束指示信息的结束数据包；或者
所述第一设备在向所述第二设备发送所述结束数据包之后，向所述第二设备发送所述结束指示信息。
根据上述方法，第一设备既可以将结束指示信息通过结束数据包发送，也可以单独发送结束指示信息，从而提高结束指示信息发送的灵活性，提高效率。
可选的，所述第一设备在向所述第二设备发送所述结束数据包之后，向所述第二设备发送所述结束指示信息之前，还包括：
所述第一设备接收所述第二设备返回的确认消息，并根据所述确认消息确定所述结束数据包以及属于所述第一流的且位于所述结束数据包之前的数据包均被所述第二设备正确接收。
第五方面，本申请实施例提供一种数据处理装置，包括：
处理单元，用于当第一流映射的无线承载RB由第一RB更改为第二RB后，确定结束数据包，所述结束数据包为第一设备通过所述第一RB发送的属于所述第一流的最后一个数据包；
收发单元，用于向第二设备发送结束指示信息以及所述结束数据包；所述结束指示信息用于指示所述第一设备通过所述第一RB发送的属于所述第一流的数据包已经发送完毕。
第六方面，本申请实施例提供一种数据处理装置，包括：
处理器，用于当第一流映射的无线承载RB由第一RB更改为第二RB后，确定结束数据包，所述结束数据包为第一设备通过所述第一RB发送的属于所述第一流的最后一个数据包；
收发机，用于向第二设备发送结束指示信息以及所述结束数据包；所述结束指示信息用于指示所述第一设备通过所述第一RB发送的属于所述第一流的数据包已经发送完毕。
第七方面，本申请实施例提供一种数据处理方法，包括：
第二设备接收第一设备发送的结束指示信息；所述结束指示信息为所述第一设备经由第一无线承载RB发送完属于第一流的最后一个数据包后发送的；所述结束指示信息用于指示所述第一设备通过所述第一RB发送的属于所述第一流的数据包已经发送完毕；
所述第二设备处理通过所述第二RB接收到的属于所述第一流的数据包。
根据本申请实施例提供的方法，第二设备接收到结束指示信息之后，可以根据结束指示信息确定第一设备通过第一RB向第二设备发送的属于第一流的最后一个数据包，从 而能够保证第二设备按照数据包的顺序处理每个数据包，避免数据包乱序。
第八方面，本申请实施例提供一种数据处理装置，包括：
收发单元，用于接收第一设备发送的结束指示信息；所述结束指示信息为所述第一设备经由第一无线承载RB发送完属于第一流的最后一个数据包后发送的；所述结束指示信息用于指示所述第一设备通过所述第一RB发送的属于所述第一流的数据包已经发送完毕；
处理单元，用于处理通过所述第二RB接收到的属于所述第一流的数据包。
第九方面，本申请实施例提供一种数据处理装置，包括：
收发机，用于接收第一设备发送的结束指示信息；所述结束指示信息为所述第一设备经由第一无线承载RB发送完属于第一流的最后一个数据包后发送的；所述结束指示信息用于指示所述第一设备通过所述第一RB发送的属于所述第一流的数据包已经发送完毕；
处理器，用于处理通过所述第二RB接收到的属于所述第一流的数据包。
第十方面，本申请实施例提供一种数据处理方法，该方法包括：
第一接入网设备向第二接入网设备发送第一消息，所述第一消息用于请求将终端切换到所述第二接入网设备；
所述第一接入网设备接收所述第二接入网设备返回的包括第一映射关系的第一响应消息；所述第一映射关系为所述第二接入网设备确定的所述终端中每个流与隧道端点标识TEID的映射关系；
所述第一接入网设备根据所述第一映射关系将所述终端的每个流的数据包转发给所述第二接入网设备。
根据本申请实施例提供的方法，第一设备根据第二设备发送的第一映射关系将所述终端的每个流的数据包转发给所述第二接入网设备，从而实现了在终端进行切换时，实现在切换中更改流与RB的映射关系。
可选的，所述第一消息中包括第二映射关系；所述第二映射关系为所述终端在所述第一接入网设备所处的网络中使用的每个流与RB的映射关系。
根据上述方法，通过向第二设备发送第二映射关系，可以使得第二设备确定第一设备确定在所述第一接入网设备所处的网络中使用的每个流与RB的映射关系，从而能够使得第二设备根据第二映射关系向第一设备发送数据。
可选的，所述第一响应消息中还包括第三映射关系；所述第三映射关系为所述第二接入网设备为所述终端中每个流确定的流与RB的映射关系或者为所述第二接入网设备对应的核心网设备为所述终端中每个流确定的流与RB的映射关系。
可选的，还包括：
所述第一接入网设备向所述终端发送切换命令，用于指示所述终端接入所述第二接入网设备；所述切换命令中包括所述第三映射关系。
可选的，在所述第三映射关系中映射的RB相同的流，在所述第一映射关系中映射的TEID相同，且在所述第三映射关系中映射的RB不同的流，在所述第一映射关系中映射的TEID不同。
根据上述方法，第一设备将所述终端的每个RB的数据包通过一个隧道发送给第二接入网设备，从而实现按照RB级别向第二设备发送数据包。
可选的，所述第二映射关系与所述第三映射关系不同；
所述第一接入网设备根据所述第一映射关系将所述终端的每个流的数据包转发给所述第二接入网设备之前，还包括：
所述第一接入网设备将所述终端的每个流的数据包中的数据包序列号删除。
可选的，所述第一映射关系中每个流映射的TEID不同。
根据上述方法，第一设备将所述终端的每个流的数据包通过一个隧道发送给第二接入网设备，从而实现按照流级别向第二设备发送数据包。
第十一方面，本申请实施例提供一种数据处理装置，包括：
收发单元，用于向第二接入网设备发送第一消息，用于请求将终端切换到所述第二接入网设备；接收所述第二接入网设备返回的包括第一映射关系的第一响应消息；所述所述第一映射关系为所述终端中每个流与隧道端点标识TEID的映射关系；
处理单元，用于根据所述第一映射关系将所述终端的每个流的数据包转发给所述第二接入网设备。
第十二方面，本申请实施例提供一种数据处理装置，包括：
收发机，用于向第二接入网设备发送第一消息，用于请求将终端切换到所述第二接入网设备；接收所述第二接入网设备返回的包括第一映射关系的第一响应消息；所述所述第一映射关系为所述终端中每个流与隧道端点标识TEID的映射关系；
处理器，用于根据所述第一映射关系将所述终端的每个流的数据包转发给所述第二接入网设备。
第十三方面，本申请实施例提供一种数据处理方法，该方法包括：
第二接入网设备接收第一接入网设备发送的第一消息，用于请求将终端切换到所述第二接入网设备；
所述第二接入网设备向所述第一接入网设备返回包括第一映射关系的第一响应消息，并接收所述第一接入网设备根据所述第一映射关系转发的所述终端的每个流的数据包；所述第一映射关系为所述第二接入网设备确定的所述终端中每个流与TEID的映射关系。
可选的，所述第一消息中包括第二映射关系；所述第二映射关系为所述终端在所述第一接入网设备所处的网络中使用的每个流与RB的映射关系。
可选的，所述第一响应消息中包括第三映射关系；所述第三映射关系为所述第二接入网设备为所述终端中每个流确定的与RB的映射关系或者为所述第二接入网设备对应的核心网设备为所述终端中每个流确定的流与RB的映射关系。
可选的，所述第二接入网设备接收所述第一接入网设备根据所述第一映射关系转发的所述终端的每个流的数据包之后，还包括：
所述第二接入网设备根据所述第二映射关系以及所述第三映射关系确定所述第二映射关系中的目标流映射的第一RB更改为第二RB，则在接收到所述目标流的目标数据包之后，确定发送所述目标数据包所使用的RB；
其中，所述目标流为所述第二映射关系中的任意一个流；所述目标数据包为所述目标流中的任意一个数据包。
可选的，所述第二接入网设备确定发送所述目标数据包所使用的RB，包括：
所述第二接入网设备若确定所述目标数据包未被所述目标数据包的接收方正确接收 且所述目标数据包之后的数据包被所述目标数据包的接收方正确接收，则在所述第一RB中发送所述目标数据包；或者
所述第二接入网设备若确定所述目标数据包未被所述目标数据包的接收方正确接收且所述目标数据包之后的数据包未被所述目标数据包的接收方正确接收，则在所述第二RB中发送所述目标数据包；或者
所述第二接入网设备若确定所述目标数据包未被所述目标数据包的接收方正确接收，则在所述第二RB中发送所述目标数据包；或者
所述第二接入网设备若无法确定所述目标数据包的接收状态，则在所述第一RB中发送所述目标数据包。
可选的，在所述第三映射关系中映射的RB相同的流，在所述第一映射关系中映射的TEID相同，且在所述第三映射关系中映射的RB不同的流，在所述第一映射关系中映射的TEID不同。
第十四方面，本申请实施例提供一种数据处理装置，包括：
收发单元，用于接收第一接入网设备发送的第一消息，用于请求将终端切换到所述第二接入网设备；向所述第一接入网设备返回包括第一映射关系的第一响应消息，并接收所述第一接入网设备根据所述第一映射关系转发的所述终端的每个流的数据包；所述第一映射关系为所述第二接入网设备确定的所述终端中每个流与TEID的映射关系。
第十五方面，本申请实施例提供一种数据处理装置，包括：
收发机，用于接收第一接入网设备发送的第一消息，用于请求将终端切换到所述第二接入网设备；向所述第一接入网设备返回包括第一映射关系的第一响应消息，并接收所述第一接入网设备根据所述第一映射关系转发的所述终端的每个流的数据包；所述第一映射关系为所述第二接入网设备确定的所述终端中每个流与TEID的映射关系。
第十六方面，本申请实施例提供一种数据处理方法，该方法包括：
第一接入网设备向第一核心网设备发送第一消息，用于请求将终端从所述第一接入网设备切换到第二接入网设备；
所述第一接入网设备接收所述第一核心网设备返回的包括第一映射关系的第一响应消息；所述第一映射关系为所述第二接入网设备为所述终端确定的每个RB与TEID的映射关系；
所述第一接入网设备根据所述第一映射关系将所述终端的每个RB的数据包转发给所述第二接入网设备。
可选的，所述第一映射关系中每个RB映射的TEID相同；或者
所述第一映射关系中每个RB映射的TEID不同。
第十七方面，本申请实施例提供一种数据处理装置，包括：
收发单元，用于向第一核心网设备发送第一消息，用于请求将终端从所述第一接入网设备切换到第二接入网设备；接收所述第一核心网设备返回的包括第一映射关系的第一响应消息；所述第一映射关系为所述第二接入网设备为所述终端确定的每个RB与TEID的映射关系；
处理单元，用于根据所述第一映射关系将所述终端的每个RB的数据包转发给所述第二接入网设备。
第十八方面，本申请实施例提供一种数据处理装置，包括：
收发机，用于向第一核心网设备发送第一消息，用于请求将终端从所述第一接入网设备切换到第二接入网设备；接收所述第一核心网设备返回的包括第一映射关系的第一响应消息；所述第一映射关系为所述第二接入网设备为所述终端确定的每个RB与TEID的映射关系；
处理器，用于根据所述第一映射关系将所述终端的每个RB的数据包转发给所述第二接入网设备。
第十九方面，本申请实施例提供一种数据处理方法，该方法包括：
第二核心网设备确定第二映射关系，所述第二映射关系为终端在所述第一接入网设备所处的网络中使用的每个RB与流的映射关系；所述第二映射关系由所述终端的每个RB在第一核心网设备所处的网络所使用的TFT模板以及所述终端的每个RB在所述第二核心网设备所处的网络所使用的TFT模板确定；
所述第二核心网设备向第二接入网设备发送包括所述第二映射关系的第三消息，用于请求将终端从第一接入网设备切换到第二接入网设备。
可选的，所述第二核心网设备向第二接入网设备发送包括所述第二映射关系的第三消息之后，还包括：
所述第二核心网设备接收所述第二接入网设备返回的包括第一映射关系的响应消息；所述第一映射关系为所述第二接入网设备为所述终端确定的每个RB与TEID的映射关系。
第二十方面，本申请实施例提供一种数据处理装置，包括：
处理单元，用于确定第二映射关系，所述第二映射关系为终端在所述第一接入网设备所处的网络中使用的每个RB与流的映射关系；所述第二映射关系由所述终端的每个RB在第一核心网设备所处的网络所使用的TFT模板以及所述终端的每个RB在所述第二核心网设备所处的网络所使用的TFT模板确定；
收发单元，用于向第二接入网设备发送包括所述第二映射关系的第三消息，用于请求将终端从第一接入网设备切换到第二接入网设备。
第二十一方面，本申请实施例提供一种数据处理装置，包括：
处理器，用于确定第二映射关系，所述第二映射关系为终端在所述第一接入网设备所处的网络中使用的每个RB与流的映射关系；所述第二映射关系由所述终端的每个RB在第一核心网设备所处的网络所使用的TFT模板以及所述终端的每个RB在所述第二核心网设备所处的网络所使用的TFT模板确定；
收发机，用于向第二接入网设备发送包括所述第二映射关系的第三消息，用于请求将终端从第一接入网设备切换到第二接入网设备。
第二十二方面，本申请实施例提供一种数据处理方法，该方法包括：
第二接入网设备接收第二核心网设备发送的包括第二映射关系的第三消息，用于请求将终端从第一接入网设备切换到所述第二接入网设备，所述第二映射关系为所述终端在所述第一接入网设备所处的网络中使用的每个RB与流的映射关系；
所述第二接入网设备向所述第二核心网设备返回包括第一映射关系的响应消息；所述第一映射关系为所述第二接入网设备为所述终端确定的每个RB与TEID的映射关系。
根据本申请实施例提供的方法，第二接入网设备通过向第二核心网设备返回包括第一映射关系的响应消息，使得第二核心网设备能够确定所述终端的每个RB与TEID的映 射关系。
可选的，所述响应消息中还包括映射关系映射指示信息；所述映射关系映射指示信息用于指示所述第二接入网设备确定的所述终端在所述第二接入网设备所处的网络中使用的每个RB与流的映射关系与所述第二映射关系相同。
可选的，所述响应消息中还包括序列指示消息，用于指示所述第一接入网设备在向所述第二接入网设备转发所述终端的数据包中携带所述第一接入网设备分配的数据包序列号。
可选的，所述第三消息中还包括所述终端的每个RB在所述第二核心网设备所处的网络所使用的TFT模板。
可选的，所述第一映射关系中每个RB映射的TEID相同；
所述第二接入网设备向所述第二核心网设备返回包括第一映射关系的响应消息之后，还包括：
所述第二接入网设备接收所述第一接入网设备转发的所述终端的每个RB的数据包；
所述第二接入网设备根据所述终端的每个RB在所述第二核心网设备所处的网络所使用的TFT模板将所述终端的每个RB的数据包过滤为每个流的数据包。
可选的，所述第二接入网设备根据所述终端的每个RB在所述第二核心网设备所处的网络所使用的TFT模板将所述终端的每个RB的数据包过滤为每个流的数据包之前，还包括：
所述第二接入网设备将所述终端的每个RB的数据包中所述第一接入网分配的数据包序列号删除；
所述第二接入网设备根据所述终端的每个RB在所述第二核心网设备所处的网络所使用的TFT模板将所述终端的每个RB的数据包过滤为每个流的数据包之后，还包括：
所述第二接入网设备确定所述每个流的数据包所属的RB；
针对每个RB中的数据包，所述第二接入网设备使用每个数据包中所述第一接入网分配的数据包序列对每个RB的数据包进行数据汇聚处理。
第二十三方面，本申请实施例提供一种数据处理装置，包括：
收发单元，用于接收第二核心网设备发送的包括第二映射关系的第三消息，用于请求将终端从第一接入网设备切换到所述第二接入网设备，所述第二映射关系为所述终端在所述第一接入网设备所处的网络中使用的每个RB与流的映射关系；向所述第二核心网设备返回包括第一映射关系的响应消息；所述第一映射关系为所述第二接入网设备为所述终端确定的每个RB与TEID的映射关系。
第二十四方面，本申请实施例提供一种数据处理装置，包括：
收发机，用于接收第二核心网设备发送的包括第二映射关系的第三消息，用于请求将终端从第一接入网设备切换到所述第二接入网设备，所述第二映射关系为所述终端在所述第一接入网设备所处的网络中使用的每个RB与流的映射关系；向所述第二核心网设备返回包括第一映射关系的响应消息；所述第一映射关系为所述第二接入网设备为所述终端确定的每个RB与TEID的映射关系。
第二十五方面，本申请实施例提供一种数据处理方法，该方法包括：
接入网设备为终端分配所述上行资源；
所示接入网设备向所述终端发送第一指示信息，所述第一指示信息用于指示数据在 所述上行资源上正确传输的传输成功率。
根据本申请实施例提供的方法，接入网设备向终端分配上行资源的同时，向终端指示出数据在所述上行资源上正确传输的传输成功率，从而使得终端能够根据数据在所述上行资源上正确传输的传输成功率确定在所述上行资源上传输的数据，从而提高优先级较高的数据的传输成功率。
可选的，所述第一指示信息为传输成功率的具体数值；或者
所述第一指示信息为索引值，所述索引值对应一个传输成功率的具体数值。
第二十六方面，本申请实施例提供一种数据处理装置，包括：
处理单元，用于为终端分配所述上行资源；
收发单元，用于向所述终端发送第一指示信息，所述第一指示信息用于指示数据在所述上行资源上正确传输的传输成功率。
第二十七方面，本申请实施例提供一种数据处理装置，包括：
处理器，用于为终端分配所述上行资源；
收发机，用于向所述终端发送第一指示信息，所述第一指示信息用于指示数据在所述上行资源上正确传输的传输成功率。
第二十八方面，本申请实施例提供一种数据处理方法，该方法包括：
终端确定接入网设备为所述终端分配的上行资源，并接收所述接入网设备发送的第一指示信息，所述第一指示信息用于指示数据在所述上行资源上正确传输的传输成功率；
所述终端根据所述第一指示信息在所述上行资源上传输的数据。
根据本申请实施例提供的方法，终端接收接入网设备发送的第一指示信息后，可以使得终端能够根据数据在所述上行资源上正确传输的传输成功率确定在所述上行资源上传输的数据，从而提高优先级较高的数据的传输成功率。
可选的，所述终端根据所述第一指示信息在所述上行资源上传输的数据，包括：
所述终端若确定所述第一指示信息所指示的传输成功率大于第一阈值，则在所述上行资源上传输优先级大于第一预设优先级的业务所对应的数据；或者
所述终端若确定所述第一指示信息所指示的传输成功率小于第二阈值，则在所述上行资源上传输优先级小于第二预设优先级的业务所对应的数据。
可选的，所述第一指示信息为传输成功率的具体数值；或者
所述第一指示信息为索引值，所述索引值对应一个传输成功率的具体数值。
第二十九方面，本申请实施例提供一种数据处理装置，包括：
处理单元，用于确定接入网设备为所述终端分配的上行资源，并接收所述接入网设备发送的第一指示信息，所述第一指示信息用于指示数据在所述上行资源上正确传输的传输成功率；
收发单元，用于根据所述第一指示信息在所述上行资源上传输的数据。
第三十方面，本申请实施例提供一种数据处理装置，包括：
处理器，用于确定接入网设备为所述终端分配的上行资源，并接收所述接入网设备发送的第一指示信息，所述第一指示信息用于指示数据在所述上行资源上正确传输的传输成功率；
收发机，用于根据所述第一指示信息在所述上行资源上传输的数据。
附图说明
图1为本申请实施例提供的一种数据处理方法流程示意图；
图2为本申请实施例提供的一种数据处理方法流程示意图；
图3为本申请实施例提供的一种数据处理方法流程示意图；
图4为本申请实施例提供的一种数据处理方法流程示意图；
图5(a)至图5(c)为本申请实施例提供的一种数据处理方法流程示意图；
图6为本申请实施例提供的一种数据处理方法流程示意图；
图7为本申请实施例提供的一种数据切换流程示意图；
图8为本申请实施例提供的一种数据处理方法流程示意图；
图9为本申请实施例提供的一种数据切换流程示意图；
图10为本申请实施例提供的一种数据处理方法流程示意图；
图11为本申请实施例提供的一种数据切换流程示意图；
图12为本申请实施例提供的一种数据处理方法流程示意图；
图13为本申请实施例提供的一种数据处理装置结构示意图；
图14为本申请实施例提供的一种数据处理装置结构示意图；
图15为本申请实施例提供的一种数据处理装置结构示意图；
图16为本申请实施例提供的一种数据处理装置结构示意图；
图17为本申请实施例提供的一种数据处理装置结构示意图；
图18为本申请实施例提供的一种数据处理装置结构示意图；
图19为本申请实施例提供的一种数据处理装置结构示意图；
图20为本申请实施例提供的一种数据处理装置结构示意图；
图21为本申请实施例提供的一种数据处理装置结构示意图；
图22为本申请实施例提供的一种数据处理装置结构示意图；
图23为本申请实施例提供的一种数据处理装置结构示意图；
图24为本申请实施例提供的一种数据处理装置结构示意图；
图25为本申请实施例提供的一种数据处理装置结构示意图；
图26为本申请实施例提供的一种数据处理装置结构示意图；
图27为本申请实施例提供的一种数据处理装置结构示意图；
图28为本申请实施例提供的一种数据处理装置结构示意图；
图29为本申请实施例提供的一种数据处理装置结构示意图；
图30为本申请实施例提供的一种数据处理装置结构示意图；
图31为本申请实施例提供的一种数据处理装置结构示意图；
图32为本申请实施例提供的一种数据处理装置结构示意图。
具体实施方式
现有技术中，无线接入网设备内部每个RB对应一个PDCP(Packet Data Convergence Protocol，分组数据汇聚协议)实体、一个RLC(Radio Link Control，无线链路层控制)实体。无线接入网设备在发送数据包时，将每个数据包放在每个数据包所属的RB所对应的PDCP 实体进行分配PDCP SN(Sequence Number，序列号)、头压缩、加密、加PDCP头等处理，然后通过每个数据包所属的RLC实体按照PDCP SN的顺序将数据包发送出去。相应的，无线接入网设备接收到数据包之后，按照每个数据包的PDCP SN，依次将数据包从RLC实体转至PDCP实体进行去PDCP头、解密、解头压缩等处理。
目前，无线接入网设备只能实现按照RB处理数据包，如何按照每个流处理数据包，还没有很好的解决方案。
本申请实施例中，终端可以是可以为无线终端，例如可以为移动电话、计算机、平板电脑、个人数码助理(personal digital assistant，PDA)、移动互联网设备(mobile Internet device，MID)、可穿戴设备、互联网协议(Internet Protocol，IP)电话、网络打印机和电子书阅读器(e-book reader)或任何其它类型的能在无线环境中工作的用户设备(user equipment，UE)等。
基于上述描述，如图1所示，为本申请实施例提供的一种数据处理方法流程示意图。
参见图1，该方法包括：
步骤101：第一设备确定数据包所属的流；
步骤102：所述第一设备根据所述数据包所属的流确定流标识，并向第二设备发送包括所述流标识的所述数据包。
步骤101中，第一设备可以是接入网设备，也可以是指终端等设备，本申请实施例对此并不限定。
第一设备可以根据实际情况确定数据包所属的流，例如，第一设备可以根据所述数据包对应的业务类型、目的地址、端口等确定数据包所属的流，本申请实施例对此并不限定。
步骤102中，第二设备可以是接入网设备，也可以是指终端等设备，本申请实施例对此并不限定。
第一设备根据所述数据包所属的流确定流标识的方式可以有以下两种：
一种可能的实现方式中，第一设备可以根据所述数据包所属的流为所述数据包分配所述流标识。需要说明的是，该场景下，第一设备可以根据预先为每个流分配的流标识，然后根据所述数据包所属的流，将预先为每个流分配的流标识中与所述数据包所属的流所对应的流标识分配给所述数据包。第一设备为每个流分配了流标识之后，还可以通过RRC(Radio Resource Control，无线资源控制)信令将每个流的流标识发送给第二设备。当然，第一设备还可以将每个流的流标识发送给终端或者核心网设备等设备。
另一种可能的实现方式中，所述第一设备从第三设备发送的流标识列表中确定与所述数据包所属的流对应的流标识。其中第三设备可以与第二设备为同一个设备，也可以为不同的设备。第三设备还可以为与第一设备连接的核心网设备或者终端等设备，本申请实施例对此并不限定。
第三设备可以通过RRC信令或者PDCP层信令向第一设备发送流标识列表。
第一设备确定数据包所属的流的流标识之后，将所述数据包发送给第二设备之前，所述第一设备可以将确定的数据包汇聚到每个数据包的RB所对应的汇聚协议实体中，然后对每个汇聚协议实体中的数据包进行分配数据包序列号、头压缩、加密、加协议头等处理。其中，汇聚协议实体可以是指PDCP实体，也可以是指与PDCP实体具有类似功能的实体；数据包序列号可以是指PDCP SN，也可以是指与PDCP SN具有类似功能的序列；协议头可以是指PDCP头，也可以是指与PDCP头具有类似功能的包头，本申请实施例对此并不 限定。
本申请实施例中，第一设备在为数据包分配数据包序列号时，可以为映射到同一RB的多个流所属的所有数据包统一分配数据包序列号，即在分配数据包序列号时，不区分数据包属于哪个流。这样可以和现有协议相兼容，避免对现有协议做较大的改动。
可选的，第一设备在为数据包分配数据包序列号时，还可以将属于同一个流的所有数据包作为一组，并分别为每一组数据包独立分配数据包序列号，即在分配数据包序列号时，需要区分数据包属于哪个流。
举例来说，flow1至flow3映射到同一RB，第一设备按照时间顺序分别接收到5个数据包，分别为数据包1至数据包5，其中数据包1以及数据包4属于flow1，数据包3以及数据包5属于flow2，数据包2属于flow3。此时，第一设备分别为数据包1至数据包5分配的数据包序列号可以为1、1、1、2、2。
在分别为每一组数据包独立分配数据包序列号的实现方式下，第一设备在对所述数据包进行头压缩和加密操作时，需要根据所述数据包的数据包序列号字段中除了所述流标识所占据的比特位之外的比特位对所述数据包进行头压缩和加密操作。
举例来说，第一设备在对所述数据包进行头压缩和加密操作之前，可以先将流标识所占据的比特位的值均作为1或0，然后对所述数据包进行头压缩和加密操作。除此之外，第一设备在对所述数据包进行头压缩和加密操作时，也可以对每个流的数据包单独进行头压缩、加密等操作，只在最后加PDCP头时统一处理。这样处理时，头压缩和加密使用的数据包序列号是连续的，可以与现有技术兼容。
本申请实施例中，第一设备确定所述数据包的流标识之后，可以将所述流标识携带在所述数据包中发送给第二设备。一种可能的实现方式中，所述第一设备将所述流标识放置在所述数据包的包头中，从而实现将所述流标识通过所述数据包发送给第二设备。本申请实施例中，可以在数据包的包头中新增一个字段作为流标识字段，也可以将数据包的包头中已有的字段重定义为流标识字段。举例来说，可以将数据包中的保留字段重定义为流标识字段，例如将数据包中PDCP头中的保留字段重定义为流标识字段。
另一种可能的实现方式中，第一设备通过数据包序列号字段中的K个比特位承载流标识，K为正整数。K的取值可以根据实际情况确定，在此并不限定。
此时流标识位于所述数据包的数据包序列号字段中，并占据所述数据包序列号字段中的K个比特位。
举例来说，数据包序列号为PDCP SN。此时，第一设备可以通过PDCP SN字段中的前K个比特位承载流标识。
上述做法是在数据包中增加显式的比特来标识每个流，从而指示出每个数据包所属的流，除此之外，也可以采用隐式方式指示每个数据包所属的流。例如，可以通过第一设备与第二设备、终端、核心网设备之间事先约定：可以根据数据包的数据包序列号来指示每个数据包所属的流。举例来说，当数据包的数据包序列号为奇数，表示该数据包来自流0，当据包的数据包序列号为偶数，表示该数据包来自流1。可选的，第一设备与第二设备、终端、核心网设备之间的事先约定可以通过RRC信令进行约定；也可以通过PDCP层控制信令进行约定。
根据本申请实施例提供的方法，第一设备在确定出数据包的流标识后，并通过所述数据包向第二设备发送所述流标识，从而向第二设备指示出所述数据包所属的流。根据该方 法，可以使得第二设备按照流级别对数据包进行处理，进一步的，可以改善端对端的QoS的性能。
下面结合具体的实施例详细描述图1的过程。
如图2所示，为本申请实施例提供的一种数据处理方法流程示意图。
图2中，以PDCP、RLC、MAC为例进行说明，但是本申请实施例所述的方案不限于这几层。图2中，第一设备收到流0(flow 0)和流1(flow1)的数据包后，确定将这两个flow映射到同一个RB传输，就分别为每个数据包确定flow标识。图2中第一设备为流0(flow 0)分配的flow标识为0，为流1(flow 1)分配的flow标识为1。第一设备为每个flow分配的flow标识可以位于数据包的PDCP头，也可以占据PDCP SN字段中的K个比特位。flow标识所占据的比特位的数量可以根据flow数量确定。
第一设备的PDCP实体还需要为两个flow的数据包统一分配PDCP SN。具体的，来自flow 0的两个数据包，为其分配的PDCP SN为24、25，来自flow 1的两个数据包，为其分配的PDCP SN为26、27。如果同一RB内汇聚的flow数量多于2个，这种做法仍然适用。之后，第一设备分别对每个数据包进行头压缩、加密、加PDCP头等处理，然后将数据包递交至RLC实体，再由MAC实体转至PHY实体后，由PHY实体发送至第二设备。第二设备接收到第一设备发送的数据包后，第二设备的PDCP实体分别进行去PDCP头、解密、解头压缩等操作，最后根据第一设备分配的flow标识，识别出每个数据包所属的flow，从而将收到的数据包分成各个flow，向上层递交。这种实现方式，PDCP实体内部可以对不同流用各自的子实体实现加密、头压缩/解头压缩操作，这种实现方式下，各个子实体所使用的SN是不连续的；另一种实现方式是：PDCP实体内部对不同流用同一套的子实体实现加密、头压缩/解头压缩操作，这种实现方式下，各子实体所使用的PDCP SN是连续的。
结合图2，如图3所示，为本申请实施例提供的一种数据处理方法流程示意图。图3中，第一设备的PDCP实体也可以对两个流的数据包单独进行分配PDCP SN、增加流标识、头压缩、加密等处理，只在最后加PDCP头这一步统一处理。这样做的最大好处在于头压缩和加密使用的PDCP SN是连续的，与现有技术相同，所以对头压缩和加密算法的改动比较小。相应的，第二设备接收到第一设备发送的数据包后，第二设备的PDCP实体统一进行去PDCP头处理，然后根据第一设备分配的流标识，识别出每个数据包所属的流，最后分别对每个流的数据包进行解密、解头压缩等处理。这种实现方式下，PDCP实体内部对不同流用同一套的子实体实现加密、头压缩/解头压缩操作。
随着空口无线条件的变化，或者业务的QoS变化，或者用户签约信息变化，流映射的RB可能会改变。在流映射的RB由源RB改变为目标RB时，发送方的源RB对应的缓存中可能还存在该流的一些还没有传输的数据包，或者已经传输但发送方未确定接收方是否正确接收到的数据包，对于这些数据包该如何处理，目前还没有一种有效的解决方案。
基于上述描述，如图4所示，为本申请实施例提供的一种数据处理方法流程示意图。图4所示的流程中，第一设备可以为终端，也可以为接入网设备；第二设备可以为终端，也可以为接入网设备。
参见图4，该方法包括：
步骤401：当第一流映射的RB由第一RB更改为第二RB后，第一设备确定结束数据包，所述结束数据包为所述第一设备通过所述第一RB发送的属于所述第一流的最后一个 数据包。
步骤402：所述第一设备向第二设备发送结束指示信息以及所述结束数据包；所述结束指示信息用于指示所述第一设备通过所述第一RB发送的属于所述第一流的数据包已经发送完毕。
步骤403：第二设备接收第一设备发送的结束指示信息；所述结束指示信息为所述第一设备经由第一RB发送完属于所述第一流的最后一个数据包后发送的；所述结束指示信息用于指示所述第一设备通过所述第一RB发送的属于所述第一流的数据包已经发送完毕。
步骤404：所述第二设备处理通过所述第二RB接收到的属于所述第一流的数据包。
步骤401中，第一设备可以接收第三设备发送的重映射指令，并根据重映射指令确定与第一流映射的RB由第一RB更改为第二RB。所述重映射指令中包括更改后的第一流与第二RB的映射关系，当然所述重映射指令中还可以包括更改前的第一流与第一RB的映射关系。其中，第三设备可以是指与第一设备连接的核心网设备或者终端等设备，第三设备还可以与第二设备为相同的设备，本申请实施例对此并不限定。
第一设备确定与第一流映射的RB由第一RB更改为第二RB后，第一RB对应的缓存中可能还存在未发送的属于所述第一流的数据包，以及已经发送但未确定接收方是否正确接收到的数据包。
对于未发送的属于所述第一流的数据包，第一设备可以将所有未发送的且属于所述第一流的数据包通过所述第二RB发送。或者，第一设备可以仍然将所有未发送的且属于所述第一流的数据包通过所述第一RB发送，在该情况下，结束指示信息是通过第一流映射的RB更改之前的RB发送的，即第一设备通过第一RB发送结束指示信息。
若第一设备将所有未发送的且属于所述第一流的数据包通过所述第二RB发送，在发送这些数据包之前，第一设备需要重新为所有未发送的且属于所述第一流的数据包重新进行分配数据包序列号、加密、头压缩等操作。相应的，通过第一RB发送的数据包中，若出现不连续的数据包序列号，则需要重新分配数据包序列号，以便获得连续的数据包序列号。其中，这里出现“不连续的数据包序列号”，是因为第一RB中数据包的数据包序列原来是连续的，当第一设备确定第一流映射的RB更改之后，将第一RB中未发送的且属于所述第一流的数据包通过第二RB发送时，导致第一RB中数据包的数据包序列被打乱，第一RB中的数据包的数据包序列出现空缺，空缺的数据包序列号就是第一RB中未发送的且属于所述第一流的数据包的数据包序列号。
对于已经发送但未确定接收方是否正确接收到的数据包，第一设备可以先从中确定出结束数据包，然后将结束指示信息以及结束数据包发送给第二设备。具体的，第一设备若将所有未发送的且属于所述第一流的数据包通过所述第二RB发送，此时第一设备可以将通过所述第一RB发送的所有属于所述第一流的待确认数据包中的最后一个数据包确定为所述结束数据包，所述待确认数据包为已经发送但未确定接收方是否正确接收到的数据包。第一设备若仍然将所有未发送的且属于所述第一流的数据包通过所述第一RB发送，此时第一设备可以将通过所述第一RB发送的所有属于所述第一流的待确认数据包以及未发送的数据包中的最后一个数据包确定为所述结束数据包。
需要说明的是，如何确定结束数据包，属于第一设备的内部实现，也就是说，第一设备也可以将任何一个数据包确定为结束数据包。此处的描述仅是举例。
步骤402中，第一设备可以将结束指示信息携带在结束数据包中发送，也可以分别发送结束指示信息和结束数据包。
具体的，一种可能的实现方式中，第一设备向所述第二设备发送包括所述结束指示信息的结束数据包。在该实现方式中，结束指示信息可以位于所述结束数据包的任何位置，例如，结束指示信息可以位于所述结束数据包的数据包头。
另一种可能的实现方式中，所述第一设备在向所述第二设备发送所述结束数据包之后，向所述第二设备发送所述结束指示信息。需要说明的是，在该实现方式中，所述第一设备在向所述第二设备发送所述结束数据包之后，向所述第二设备发送所述结束指示信息之前，需要先接收所述第二设备返回的确认消息，并在根据所述确认消息确定所述结束数据包以及属于所述第一流的且位于所述结束数据包之前的数据包均被所述第二设备正确接收之后，向第二设备发送所述结束指示信息。在该实现方式中，第一设备可以生成一个包括所述结束指示信息的控制包，并通过第一RB或者第二RB向第二设备发送所述控制包，从而实现向第二设备发送结束指示信息。
在步骤403中，第二设备在接收到结束指示信息之后，在步骤404中，第二设备可以确定第一设备通过第一RB发送的属于所述第一流的数据包已经发送完毕，此时第二设备可以确定何时将从第二RB接收到的属于所述第一流的数据包递交到上一协议层进行处理，例如PDCP层。
需要说明的是，上述流程的方法中的数据包可以是指上行数据包，也可以是指下行数据包，本申请实施例对此并不限定。
根据本申请实施例提供的方法，在第一流映射的RB改变时，通过发送结束指示信息向第二设备指示出第一设备通过第一RB发送的属于所述第一流的最后一个数据包，从而能够保证第二设备按照数据包的顺序处理每个数据包，避免数据包乱序。
下面结合具体的实施例详细描述图4的过程。
如图5(a)以及图5(b)所示，为本申请实施例提供的一种数据处理方法流程示意图。
图5(a)以及图5(b)中，以PDCP、RLC为例进行说明，但是本申请实施例所述的方案不限于这几层。图5(a)中，原来5个flow映射到两个RB：流0(flow 0)、流1(flow1)、流2(flow 2)映射到RB A，流3(flow 3)、流4(flow 4)映射到RB B。接收方接收到每个flow的数据包后，将映射到同一RB的flow的数据包通过同一PDCP实体进行头压缩、加密、加PDCP头等处理，然后将数据包转至RLC实体。重配置以后，flow2改为映射到RB B，其他flow和RB的映射关系不变。此时，第一设备接收到的属于flow2的两个数据包仍然在RB A的RLC buffer中，这两个数据包的PDCP SN分别为22和25。这两个数据包可以为未发送的数据包，也可以为已经发送但未确定接收方是否正确接收到的数据包。
flow2改为映射到RB B以后，PDCP SN分别为22和25的数据包依然通过RB A传输，但是它们后续的属于flow 2数据包，需要通过RB B传输。具体的，如图5(b)所示，图5(b)中RB B中PDCP SN为67的数据包。因为发送方从发送方的上层接收到的数据包的顺序是22、25、67，所以在接收方也要按照相同的顺序递交给接收方的上层。为此，flow2改为映射到RB B后，发送方在发完flow2的PDCP SN为25的数据包之后，生成一个包含结束指示信息的控制包，并将所述控制包在空口发送给接收方，其目的是向接收方指示出发送方通过RAA发送的属于flow2的最后一个数据包为PDCP SN为25的数据包。
本申请实施例中，flow映射的RB更改以后，第一设备还可以将已经接收但未传输的属于该flow数据包通过更改后的RB传输。具体的，结合图5(a)以及图5(b)，如图5(c)所示，为本申请实施例提供的一种数据处理方法流程示意图。图5(c)中，发送方将属于flow2的“还未在空口传输的数据包24、25”，经PDCP实体重新处理后，放到flow2更改后映射的RB B中传输。这里所说的PDCP实体重新处理，包括重新分配PDCP SN，重新加密、重新头压缩等。如果这样做，发送方就可以提前发送结束指示信息，即在RB A中最后一个来自flow 2的数据包发送完成后，发送结束指示信息。接收方收到结束指示信息后，就可以确定向上层递交属于flow2的数据包的时间了。对于发送方，除了对“还未在空口传输的包24、25”重新处理外，其它数据包的PDCP SN如果受到影响，都需要重新处理，比如图5(a)中属于flow 0的数据包23，属于flow 1的数据包24，都需要重新分配PDCP SN、重新加密、重新头压缩。
由于现有的LTE系统是基于bear(承载)传输的，该系统中的接入网设备在有线接口接收到的数据包按RB进入接入网设备的，在空口发送数据包时是按RB发送的，下面将该类型的接入网设备的类型简称为RB-RB型；而NR(New Radio，新空口)系统是基于flow传输的，该系统中的接入网设备在有线接口接收到的数据包是按flow进入接入网设备的，在空口发送数据包时是按RB在空口发送的，下面将该类型的接入网设备的类型简称为flow-RB型。需要说明的是，数据包在空口传输时，发送方会为同一RB或flow的数据包确定一个隧道，并将同一RB或flow的数据包通过确定的隧道发送，隧道一般采用隧道端点标识(Tunnel Endpoint Identifier,TEID)进行标识。
终端在切换时，终端当前接入的源接入网设备与将要切换的目标接入网设备可能有多种不同的组合，所有可能的组合可以如表1所示。需要说明的是，表1所示的场景可以为网络中同时存在LTE系统和NR系统的接入网设备的场景，当然也可以为其他场景，本申请对此并不限定。
Figure PCTCN2017096215-appb-000001
表1
场景一中，终端就是在LTE系统的内部进行切换，属于现有技术，本申请实施例对此不再赘述。结合前面的描述，在场景二、三、四中，由于不同系统中的接入网设备，对数据包处理时所采用的粒度不同(LTE系统中是基于RB级别，NR系统中是基于flow级别)，终端在进行切换时，源接入网设备与目标接入网设备之间如何实现将RB级别的数据包转换为流级别的数据包或者将流级别的数据包转换为RB级别的数据包，目前还没有一种好的解决方案。
基于上述描述，如图6所示，为本申请实施例提供的一种数据处理方法流程示意图。
参见图6，该方法包括：
步骤601：第一接入网设备向第二接入网设备发送第一消息，用于请求将终端切换到所述第二接入网设备。
步骤602：第二接入网设备接收第一接入网设备发送的第一消息，用于请求将终端切换到所述第二接入网设备。
步骤603：所述第一接入网设备接收所述第二接入网设备返回的包括第一映射关系的第一响应消息，所述第一映射关系为所述终端中每个流与隧道端点标识TEID的映射关系。
需要说明的是，第一映射关系可以为第二接入网设备或者与第二接入网设备处于同一网络的核心网设备确定的，具体可以根据实际情况确定，在此不再赘述。
步骤604：所述第一接入网设备根据所述第一映射关系将所述终端的每个流的数据包转发给所述第二接入网设备。
步骤605：所述第二接入网设备向所述第一接入网设备返回包括第一映射关系的第一响应消息，并接收所述第一接入网设备根据所述第一映射关系转发的所述终端的每个流的数据包。
步骤601之前，第一接入网设备可能会接收到终端发送的测量报告。需要说明的是，所述终端为接入第一接入网设备的终端。
第一接入网设备接收到所述测量报告之后，根据切换算法进行切换判决。当确定需要执行切换之后，执行步骤601。
步骤601中，第一接入网设备发送的第一消息中还可以包括以下至少一项：
第二映射关系；所述第二映射关系为所述终端在所述第一接入网设备所处的网络中使用的每个流与RB的映射关系；
第四映射关系；所述第四映射关系为所述终端在第一接入网设备所处的网络中使用的每个流与TEID的映射关系；
每个流对应的至少一个flow AMBR(Aggregate Maximum Bit Rate，最大聚合速率)值。其中，多个流可以对应同一个flow AMBR，即一组流可以对应一个flow AMBR。
步骤603中，所述第一响应消息中还可以包括第三映射关系；所述第三映射关系为所述第二接入网设备为所述终端中每个流确定的流与RB的映射关系或者为所述第二接入网设备对应的核心网设备为所述终端中每个流确定的流与RB的映射关系。与第一映射关系类似，第三映射关系也包括为上行数据和下行数据分配的、独立的TEID。
需要说明的是，本申请实施例中，第二映射关系与第三映射关系可以相同，也可以不同，具体可以根据实际情况确定，在此不再赘述。可选的，若所述第二映射关系与所述第三映射关系不同；所述第一接入网设备根据所述第一映射关系将所述终端的每个流的数据包转发给所述第二接入网设备之前，还可能将所述终端的每个流的数据包中的数据包序列号删除。例如，将每个流的数据包中的PDCP SN删除。
步骤604中，若所述第一映射关系中每个流映射的TEID不同，则第一接入网设备可以将每个流的数据包通过一个隧道(tunnel)发送给第二接入网设备。
第一接入网设备也可以将所述终端的每个RB的数据包通过一个隧道发送给第二接入网设备，此时每个RB映射的流所映射的TEID相同。需要说明的是，第一接入网设备是根据第一映射关系建立隧道的，因此此时，第一映射关系中映射的RB相同的流映射的TEID相同，即在所述第一映射关系中映射的TEID相同，且在所述第三映射关系中映射的 RB不同的流，在所述第一映射关系中映射的TEID不同。
需要说明的是，第一接入网设备可以将所述终端的两部分数据包发送给第二接入网设备，一部分是已经通过空口发送给终端但是还没有确定所述终端是否正确收到的数据包；一部分是还没有通过空口发送给终端的数据包。
可选的，所述第一接入网设备还可以向所述终端发送切换命令，用于指示所述终端接入所述第二接入网设备；所述切换命令中包括所述第三映射关系。
步骤605中，所述第二接入网设备接收到所述终端的每个流的数据包之后，若根据所述第二映射关系以及所述第三映射关系确定所述第二映射关系中的目标流映射的第一RB更改为第二RB，则在接收到所述目标流的目标数据包之后，确定发送所述目标数据包所使用的RB；其中，所述目标流为所述第二映射关系中的任意一个流；所述目标数据包为所述目标流中的任意一个数据包。
上述流程中，第二接入网设备所确定的流与RB的映射关系与所述终端在第一接入网设备所处的网络中使用的每个流与RB的映射关系可能相同，也可能不同，如果相同，第二接入网设备就按照原来的流与RB的映射关系对终端的数据包进行处理，在此不再赘述。
如果第二接入网设备所确定的流与RB的映射关系与所述终端在第一接入网设备所处的网络中使用的每个流与RB的映射关系不相同，所述第二接入网设备确定发送所述目标数据包所使用的RB的方式有四种，下面详细描述：
一种可能的实现方式中，所述第二接入网设备若确定所述目标数据包未被所述目标数据包的接收方正确接收且所述目标数据包之后的数据包被所述目标数据包的接收方正确接收，则在所述第一RB中发送所述目标数据包。
一种可能的实现方式中，所述第二接入网设备若确定所述目标数据包未被所述目标数据包的接收方正确接收且所述目标数据包之后的数据包未被所述目标数据包的接收方正确接收，则在所述第二RB中发送所述目标数据包。
一种可能的实现方式中，所述第二接入网设备若确定所述目标数据包未被所述目标数据包的接收方正确接收，则在所述第二RB中发送所述目标数据包。
一种可能的实现方式中，所述第二接入网设备若无法确定所述目标数据包的接收状态，则在所述第一RB中发送所述目标数据包。
第二接入网设备对于没有更换RB的流，属于该流的数据包，如果前面有的数据包被挪到新的RB传输了，就更改当前数据包的数据包序列号，重新做加密等处理后，在空口发送。
第二接入网设备对于从网关接收到的数据包，按照新的流与RB映射关系，将每个流的数据包映射到相应的RB，然后在空口发送，在此不再赘述。
本申请实施例中，第二接入网设备可以根据终端或第一接入网设备发送的PDCP状态报告确定每个数据包的接收状态。当然，以上只是示例，第二接入网设备还可以通过其他方式确定每个数据包的接收状态，在此不再赘述。
根据本申请实施例提供的方法，通过在切换之前，由第一接入网设备与第二接入网设备之间交换第二映射关系以及第三映射关系，从而实现终端在进行切换时，源接入网设备与目标接入网设备之间实现将RB级别的数据包转换为流级别的数据包或者将流级别的数据包转换为RB级别的数据包。
下面通过具体的实施例详细描述图6的过程。
如图7所示，为本申请实施例提供的一种数据切换流程示意图。
图7对应表1中对比场景二，即第一接入网设备按照flow-RB的方式处理数据包，第二接入网设备按照flow-RB的方式处理数据包。
步骤701：终端向第一接入网设备上报测量报告。
测量报告的具体内容可以参考现有标准中的描述，本申请实施例对此并不限定。
步骤702：第一接入网设备根据接收到的测量报告决定触发切换流程，并向第二接入网设备发送第一消息。
可选的，第一消息中可以包括以下信息：
第二映射关系；第四映射关系；每个流对应的至少一个流AMBR值。
需要说明的是，第一消息中也可以不包括以上信息，具体根据实际情况确定。
步骤703：第二接入网设备向所述第一接入网设备返回包括第一映射关系的第一响应消息。
所述第一响应消息中还可以包括第三映射关系；所述第三映射关系与第二映射关系可以相同，也可以不同，具体可以根据实际情况确定。
步骤704：第一接入网设备向终端发送切换命令。
所述切换命令中包含可以包括所述第三映射关系。
步骤705：第一接入网设备向第二接入网设备发送所述终端的数据包。
具体的，第一接入网设备可以将终端的每个流的数据包通过一个隧道发送给第二接入网设备。这样，第二接入网设备根据收到数据包所在的隧道，就知道该数据包属于哪个流。
步骤706：第二接入网设备进行路径切换。
第二接入网设备还可以通知网关以及核心网会话管理网元，将后续和终端相关的数据包发送到第二接入网设备
步骤707：终端接入第二接入网设备。
基于上述描述，针对表1中的场景三，如图8所示，为本申请实施例提供的一种数据处理方法流程示意图。
参见图8，该方法包括：
步骤801：第一接入网设备向第一核心网设备发送第一消息，所述第一消息用于请求将终端从所述第一接入网设备切换到第二接入网设备；
步骤802：所述第一接入网设备接收所述第一核心网设备返回的包括第一映射关系的第一响应消息；所述第一映射关系为所述第二接入网设备为所述终端确定的每个流与TEID的映射关系；
步骤803：所述第一接入网设备根据所述第一映射关系将所述终端的每个流的数据包转发给所述第二接入网设备。
下面通过详细的实施例描述图8所示的过程。
如图9所示，为本申请实施例提供的一种数据切换流程示意图。
图9对应表1中对比场景三，即第一接入网设备按照flow-RB的方式处理数据包，第二接入网设备按照RB-RB的方式处理数据包。
步骤901：终端向第一接入网设备上报测量报告。
测量报告的具体内容可以参考现有标准中的描述，本申请实施例对此并不限定。
终端共有4个flow，分别为flow 0、flow 1、flow 2、flow 3。
步骤902：第一接入网设备根据接收到的测量报告决定触发切换流程，向第一核心网设备发送第一消息，用于请求将终端切换到第二接入网设备。
第一接入网设备确定为每个流建立一条隧道，此时第一接入网设备为每个flow的上行数据和下行数据各分配一个TEID，因此第一消息中可以包括所述终端在第一接入网设备所处的网络中使用的每个流的上下行数据与TEID的映射关系，例如，flow 0映射TEID 0、flow 1映射TEID 1、flow 2映射TEID 2、flow 3映射TEID 3。
第一核心网设备为第一接入网设备所处的网络中与所述第一接入网对接的设备。
可选的，第一消息中还可以包括所述终端在第一接入网设备所处的网络中使用的每个流与RB的映射关系。
步骤903：第一核心网设备接收到所述第一接入网设备发送的第一消息后，向第二核心网设备发送第二消息，用于请求将终端切换到所述第二接入网设备。
第二消息中可以包括第四映射关系，所述第四映射关系为所述终端在第一接入网设备所处的网络中使用的每个流与TEID的映射关系。结合前面的描述，此时，第四映射关系可以为：flow 0映射TEID 0、flow 1映射TEID 1、flow 2映射TEID 2、flow 3映射TEID 3。
除此之外，第二消息也可以只包含第一核心网设备所使用的一套或多套TFT过滤模板参数以及对应的QoS类别，具体地，一套TFT过滤模板参数包括：源IP地址、源端口号、目标IP地址、目标端口号、协议类型。第二核心网设备收到TFT模板后，确定自己为该UE所提供的RB数量、flow数量，以及flow到RB的映射关系。
步骤904：第二核心网设备接收到所述第一核心网设备发送的第二消息后，向第二接入网设备发送第三消息，用于请求将终端切换到所述第二接入网设备。
第二核心网设备接收到所述第二消息的同时，还可以为终端的每个流确定在第二接入网设备所处的网络中所映射的RB，即第三映射关系，例如：第二核心网设备确定了两个RB，分别为RB A与RB B，第二核心网设备确定的第三映射关系为：flow 0与flow 1映射RB A、flow 2与flow 3映射RB B。
此时，第三消息中可以包括以下映射关系：flow 0映射TEID 0、flow 1映射TEID 1、flow 2映射TEID 2、flow 3映射TEID 3；flow 0与flow 1映射RB A、flow 2与flow 3映射RB B。
步骤905：第二接入网设备向第二核心网设备发送第三响应消息。
第二接入网设备收到第三消息后，确定按照每个流映射一个TEID的方式接收从第一接入网设备发送的数据包，同时确定终端中在第二接入网所处的网络中使用的流与TEID的映射关系，即第一映射关系。此处，第一映射关系可以为：flow 0映射TEID 0’、flow 1映射TEID 1’、flow 2映射TEID 2’、flow 3映射TEID 3’。
第二接入网设备将上述映射关系通过第三响应消息发送给第一接入网设备。
步骤906：第二核心网设备向第一核心网设备发送第二响应消息。
第二响应消息中可以包括第一映射关系以及第三映射关系。
步骤907：第一核心网设备向第一接入网设备发送第一响应消息。
第一响应消息中可以包括第一映射关系以及第三映射关系。
步骤908：第一接入网设备向终端发送切换命令。
切换命令中可以包括第三映射关系。
最后，第一接入网设备根据第一映射关系将终端的每个流的数据包通过一个隧道发送 给第二接入网设备。这样，第二接入网设备根据收到数据包所在的隧道，就知道该数据包属于哪个流。
图9所示的流程中，第二接入网设备也可以要求第一接入网设备“按照每个RB来建立隧道”。此时，在步骤905中，第二接入网设备可以为映射到同一个RB的流确定相同的TEID，即第二接入网设备确定出的第一映射关系可以为：flow 0映射TEID 0’、flow 1映射TEID 0’、flow 2映射TEID 1’、flow 3映射TEID 1’。随后，第二接入网设备将上述映射关系通过第三响应消息发送给第一接入网设备。
图9所示的场景三中，第二接入网设备对数据包的处理又可以细分为如表2所示的四种情况：
Figure PCTCN2017096215-appb-000002
表2
下面对表2中的四种情况进行详细说明：
- 情况1：第二接入网设备从各个隧道接收数据包后，根据所述第二接入网设备对应的核心网设备为所述终端中每个流确定的流与RB的映射关系，将收到的数据包汇聚到相应的RB中。该情况下，数据包的处理与现有的LTE内部的切换流程的数据包处理完全相同，在此不再赘述。
- 情况2：第二接入网设备从各个隧道接收数据包后，根据所述第二接入网设备对应的核心网设备为所述终端中每个流确定的流与RB的映射关系，将收到的数据汇聚到相应的RB中，然后按照上面描述的四种可能的实现方式中的至少一种处理数据包。
可选的，对于发生了流映射的RB发生改变的那些流，对于终端而言，终端按照第二接入网设备生成的PDCP状态报告确定数据包向哪个RB传输。具体的，对于PDCP状态报告内体现为“空洞”的数据包，终端通过流映射的RB更改前的RB发送空洞的数据包；对于PDCP状态报告内未能体现为“空洞”的数据包，终端通过流映射的RB更改后的RB发送这些未能体现为“空洞”的数据包。终端如果没收到PDCP状态报告，则把所有数据包都放在flow映射的RB更改后的RB中传输。
- 情况3：从第一接入网设备的角度看，需要将来自多个流的数据包汇聚到一个隧道中，并向第二接入网设备转发。由于第二映射关系以及所述第三映射关系相同，所以从第二接入网设备的角度看，将来自各个隧道的数据包，放到对应的RB中传输就可以了。具体的数据包的处理与LTE内部的切换流程的数据包处理完全相同，在此不再赘述。
- 情况4：第一接入网设备根据第三映射关系，将数据包通过隧道传到第二接入网设备。比如，在第二映射关系中，flow 0和flow 1原本映射到RB A，flow 2和flow 3原本映射到RB B，到了第二接入网设备侧，第三映射关系为：flow 0和flow 3映射到RB A,flow 1和flow 2映射到RB B。第一接入网设备按照第三映射关系，将flow 0和flow 3的数据包放到RB A对应的隧道中转发，将flow 1和flow 2的数据包放到RB B对应的隧道中转发。数据包转发过程中，第一接入网设备并不发送每个数据包的数据包序列号，数据包到达第二接入网设备后，第二接入网设备为每个数据包重新分配数据包序列号。
基于上述描述，针对表1中的场景四，如图10所示，为本申请实施例提供的一种数据处理方法流程示意图。
参见图10，该方法包括：
步骤1001：第一接入网设备向第一核心网设备发送第一消息，所述第一消息用于请求将终端从所述第一接入网设备切换到第二接入网设备；
步骤1002：所述第一接入网设备接收所述第一核心网设备返回的包括第一映射关系的第一响应消息；所述第一映射关系为所述第二接入网设备为所述终端确定的每个RB与TEID的映射关系；
步骤1003：所述第一接入网设备根据所述第一映射关系将所述终端的每个RB的数据包转发给所述第二接入网设备。
步骤1001之前，第一接入网设备可能会接收到终端发送的测量报告。
第一接入网设备接收到所述测量报告之后，根据切换算法进行切换判决。当确定需要执行切换之后，执行步骤1001。
步骤1001中，第一接入网设备发送的第一消息中还可以包括以下至少一项：
第四映射关系；所述第四映射关系为所述终端在第一接入网设备所处的网络中使用的每个RB与TEID的映射关系。
第一核心网设备接收到第一消息之后，向第二核心网设备发送第二消息。所述第二消息中可以包括以下内容：
第四映射关系；所述终端的每个RB在第一核心网设备所处的网络所使用的TFT(Traffic Flow Template，数据流模板)模板。除此之外，第二消息也可以只包含第一核心网设备所使用的一套或多套TFT过滤模板参数以及对应的QoS类别，具体地，一套TFT过滤模板参数包括：源IP地址、源端口号、目标IP地址、目标端口号、协议类型。第二核心网设备收到TFT模板后，确定自己为该终端所提供的RB数量、flow数量，以及flow到RB的映射关系。
第二核心网设备接收到所述第二消息之后，可以根据所述终端的每个RB在第一核心网设备所处的网络所使用的TFT模板以及所述终端的每个RB在所述第二核心网设备所处的网络所使用的TFT模板确定第二映射关系；所述第二映射关系为所述终端在所述第一接入网设备所处的网络中使用的每个流与RB的映射关系。
所述第二核心网设备随后向第二接入网设备发送包括所述第二映射关系的第三消息，用于请求将终端从第一接入网设备切换到第二接入网设备。所述第三消息中还可以包括所述终端的每个RB在所述第二核心网设备所处的网络所使用的TFT模板。
第二接入网设备接收第二核心网设备发送的包括第二映射关系的第三消息之后，向所述第二核心网设备返回包括第一映射关系的第三响应消息；所述第一映射关系为所述第二接入网设备为所述终端确定的每个RB与TEID的映射关系。
其中，所述第一映射关系中每个RB映射的TEID相同；或者，所述第一映射关系中每个RB映射的TEID不同。
可选的，所述第三响应消息中还包括映射关系映射指示信息；所述映射关系映射指示信息用于指示所述第二接入网设备确定的所述终端在所述第二接入网设备所处的网络中使用的每个RB与流的映射关系与所述第二映射关系相同。
进一步的，所述第三响应消息中还可以包括序列指示消息，用于指示所述第一接入网设备在向所述第二接入网设备转发所述终端的数据包中携带所述第一接入网设备分配的数据包序列号。数据包序列号可以是指PDCP SN。
所述第二核心网设备接收所述第二接入网设备返回的包括第一映射关系的第三响应消息之后，向第一核心网设备发送第二响应消息。所述第二响应消息中包括第一映射关系。
步骤1002中，第一接入网设备接收到第一响应消息之后，向所述终端发送切换命令，用于指示所述终端接入所述第二接入网设备。
步骤1003中，第一接入网设备将所述终端的每个RB的数据包转发给所述第二接入网设备时，可以将每个数据包的数据包序列号同时也发送给第二接入网设备，当然，也可以不发送每个数据包的数据包序列号，具体根据实际情况确定。
需要说明的是，第一接入网设备发送给第二接入网设备的数据包，可以分为两种类型的数据包，一种类型的数据包是已经通过空口发送给终端但是还没有确定所述终端是否正确收到的数据包；一种类型的数据包是还没有通过空口发送给终端的数据包。
下面通过详细的实施例描述图10的过程。
如图11所示，为本申请实施例提供的一种数据切换流程示意图。
图11对应表1中对比场景四，即第一接入网设备按照RB-RB的方式处理数据包，第二接入网设备按照flow-RB的方式处理数据包。
步骤1101：终端向第一接入网设备上报测量报告。
测量报告的具体内容可以参考现有标准中的描述，本申请实施例对此并不限定。
例如，终端共有4个flow，分别为flow 0、flow 1、flow 2、flow 3。其中，flow 0、flow1映射到RB A；flow 2、flow 3映射到RB B。
步骤1102：第一接入网设备根据接收到的测量报告决定触发切换流程，向第一核心网设备发送第一消息，用于请求将终端切换到第二接入网设备。
第一接入网设备确定为每个RB建立一条隧道，此时第一接入网设备为每个RB分配一个TEID，因此第一消息中可以包括第四映射关系，即所述终端在第一接入网设备所处的网络中使用的每个RB与TEID的映射关系，例如，RB A映射TEID 0、RB B映射TEID1。
步骤1103：第一核心网设备接收到所述第一接入网设备发送的第一消息后，向第二核心网设备发送第二消息，用于请求将终端切换到所述第二接入网设备。
第二消息中可以包括所述终端在第一接入网设备所处的网络中使用的每个RB与TEID的映射关系，以及所述终端的每个RB在第一核心网设备所处的网络所使用的TFT模板。
步骤1104：第二核心网设备确定第二映射关系。
第二核心网设备可以根据所述终端的每个RB在第一核心网设备所处的网络所使用的TFT模板以及所述终端的每个RB在所述第二核心网设备所处的网络所使用的TFT模板确定第二映射关系，即确定出flow 0、flow 1映射到RB A；flow 2、flow 3映射到RB B。
步骤1105：第二核心网设备向第二接入网设备发送第三消息，用于请求将终端切换到 所述第二接入网设备。
第三消息中可以包括第二映射关系以及第四映射关系。
步骤1106：第二接入网设备向第二核心网设备发送第三响应消息。
第二接入网设备收到第三消息后，确定按照每个RB映射一个TEID的方式接收从第一接入网设备发送的数据包，同时确定自己这一侧每个RB映射的TEID，即第一映射关系。第一映射关系可以为：RB A映射TEID 0’、RB B映射TEID 1’。
第二接入网设备将上述映射关系通过第三响应消息发送给第一接入网设备。
步骤1107：第二核心网设备向第一核心网设备发送第二响应消息。
第二响应消息中可以包括第一映射关系。
步骤1108：第一核心网设备向第一接入网设备发送第一响应消息。
第一响应消息中可以包括第一映射关系。
步骤1109：第一接入网设备向终端发送切换命令。
最后，第一接入网设备根据第一映射关系将终端的每个RB的数据包通过一个隧道发送给第二接入网设备。这样，第二接入网设备根据收到数据包所在的隧道，就知道该数据包属于哪个流。
图10所示的流程中，第二接入网设备收到第三消息后，可以根据第二映射关系确定终端在第二接入网设备所处的网络所使用的流与RB映射关系是否与终端在第一接入网设备所处的网络所使用的流与RB映射关系相同，如果相同，则第二接入网设备在步骤1106中发送的第三响应消息中携带映射关系映射指示信息；其中，所述映射关系映射指示信息用于指示所述第二接入网设备确定的所述终端在所述第二接入网设备所处的网络中使用的每个RB与流的映射关系与所述第二映射关系相同。
同时，第二接入网设备在步骤1106中发送的第三响应消息中携带序列指示消息，用于指示所述第一接入网设备在向所述第二接入网设备转发所述终端的数据包中携带所述第一接入网设备分配的数据包序列号；从而请求第一接入网设备在进行数据包转发时将每个数据包的数据包序列号捎带上，这样，整个切换流程的数据包处理过程就与LTE内部的切换完全相同。
可选的，图11所述的流程中，第一接入网设备可以为所有RB映射相同的TEID，即所有RB的数据包都经由一条隧道转发到第二接入网设备。第二接入网设备收到转发的数据包后，使用所述终端的每个RB在所述第二核心网设备所处的网络所使用的TFT模板，将接收到的数据包过滤成多个流，再在第二核心网设备所处的网络中传输。
可选的，图11所述的流程中，第一接入网设备可以为所有RB映射相同的TEID，即所有RB的数据包都经由一条隧道转发到第二接入网设备。第二接入网设备在步骤1106中发送的第三响应消息中携带序列指示消息，从而请求第一接入网设备在进行数据包转发时将每个数据包的数据包序列号捎带上，第二接入网设备收到数据包后，所述第二接入网设备将所述终端的每个RB的数据包中所述第一接入网分配的数据包序列号删除。然后所述第二接入网设备确定所述每个流的数据包所属的RB；然后针对每个RB中的数据包，所述第二接入网设备使用每个数据包中所述第一接入网分配的数据包序列对每个RB的数据包进行数据汇聚处理。具体的，第二接入网设备可以使用所述终端的每个RB在所述第二核心网设备所处的网络所使用的TFT模板，将接收到的数据包过滤成多个流，然后再使用所述终端的每个RB在所述第一核心网设备所处的网络所使用的TFT模板，确定每个流的数 据包所属的RB，再按第一接入网设备未每个数据包分配的数据包序列号做数据汇聚处理，例如PDCP处理，并在空口传输。
接入网设备为终端分配上行资源时，会分配物理资源，并规定终端使用的MCS值，这两个参数一旦确定，终端传输上行数据的一次成功概率也就确定了，通常传输成功概率是90％。而终端的MAC层对各个RB的数据进行复用，相当于MAC层对各个RB提供的传输成功概率也是相同的。基于这个思想，MAC实体对来自各个RB的数据进行复用时，可以只考虑各个RB的相对优先级，不考虑底层传输资源的可靠程度。
5G系统中，为了实现更加精细化的传输，接入网设备为终端分配上行资源时，可以确定在为终端分配的上行资源上正确传输数据的传输成功概率，并将传输成功概率通知给终端，从而提高资源利用率。
基于上述描述，如图12所示，为本申请实施例提供的一种数据处理方法流程示意图。
参见图12，该方法包括：
步骤1201：接入网设备为终端分配所述上行资源；
步骤1202：接入网设备向所述终端发送第一指示信息，所述第一指示信息用于指示数据在所述上行资源上正确传输的传输成功率。
步骤1203：终端确定接入网设备为所述终端分配的上行资源，并接收所述接入网设备发送的第一指示信息；
步骤1204：所述终端根据所述第一指示信息在所述上行资源上传输数据。
步骤1201中，接入网设备可能在接收到终端发送的资源请求后，为终端分配上行资源。终端发送的资源请求可以为调度请求(Schedule Request，SR)，也可以为缓冲区状态报告(Buffer Status Reports，BSR)等用于请求上行资源的消息，本申请实施例对此并不限定。当然，接入网设备也可以在其他情况下为终端分配上行资源，在此不再赘述。
步骤1202中，如前所述，接入网设备为终端分配的上行资源和规定终端使用的MCS值一旦确定，终端在所述上行资源上传输上行数据的一次成功概率也就确定了。对此，接入网设备如何确定数据在所述上行资源上正确传输的传输成功率，本申请实施例对此并不限定。
本申请实施例中，所述第一指示信息可以为传输成功率的具体数值。
所述第一指示信息还可以为索引值，所述索引值对应一个传输成功率的具体数值。在该方式下，一种可能的实现方式中，可以事先由接入网设备通过专用信令向终端发送一个对照表格，对照表格中包括多个索引值，每个索引值对应一个传输成功概率。接入网设备分配上行传输资源时，指示索引值即可。同一小区内各个终端所使用的表格可以各不相同，也可以相同，本申请实施例对此并不限定。
一种可能的实现方式中，接入网设备通过广播信令向终端发送一个对照表格，对照表格中包括多个索引值，每个索引值对应一个传输成功概率。接入网设备分配上行传输资源时，指示索引值即可。
一种可能的实现方式中，可以由协议规定一个对照表格，对照表格中包括多个索引值，每个索引值对应一个传输成功概率。
可选的，接入网设备也可以在为终端配置RB时，确定RB的配置信息，此时配置信息向终端指示所配置的RB中的数据包只能用传输成功概率大于预设阈值的资源进行传输。这样，终端可以根据每个RB的配置信息确定传输每个RB中的数据包所使用的资源。
需要说明的是，接入网设备可以将第一指示信息与向终端发生的上行资源分配指示信息放在同一条消息中发送，也可以分别发送，本申请实施例对此并不限定。其中，上行资源分配指示信息用于向终端指示为所述终端分配的上行资源。
步骤1203中，终端如何确定接入网设备为其分配的上行资源，本申请实施例并不限定。
最后在步骤1204中，终端的MAC实体生成上行数据传输块时，将第一指示信息指示的传输成功率考虑在内，比如，终端发现自己得到的上行资源对应的成功概率比较高，就发送优先级高、时延预算少的业务的数据，如果终端发现自己得到的上行资源对应的成功概率比较低，就发送优先级低、时延预算多的业务的数据。
举例来说，所述终端若确定所述第一指示信息所指示的传输成功率大于第一阈值，则在所述上行资源上传输优先级大于第一预设优先级的业务所对应的数据；所述终端若确定所述第一指示信息所指示的传输成功率小于第二阈值，则在所述上行资源上传输优先级小于第二预设优先级的业务所对应的数据。其中，第一阈值以及第二阈值可以根据实际情况确定，本申请实施例对此并不限定。
需要说明的是，以上方案不仅可用于接入网设备动态分配资源的场景，还可以用于半静态分配资源的场景。比如：接入网设备预先分配一些无线资源的集合，分别对应不同的传输成功概率，终端使用一个具体的无线资源传输数据时，先确定该无线资源对应的传输成功概率，再根据该无线资源对应的传输成功概率确定哪些RB的数据可以利用这个无线资源传输。
上述本发明提供的实施例中，分别从各个网元本身、以及从各个网元之间交互的角度对本发明实施例提供的数据处理方法进行了介绍。可以理解的是，各个网元，例如终端、基站等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本发明能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
基于相同的技术构思，本申请实施例还提供一种数据处理装置，该装置可执行图1所述的方法流程，以及可以执行图2至图3所述的方法流程中第一设备所实现的功能。
如图13所示，为本申请实施例提供一种数据处理装置结构示意图。
参见图13，该装置包括：
处理单元1301，用于确定数据包所属的流；根据所述数据包所属的流确定流标识；
收发单元1302，用于向第二接入网设备发送包括所述流标识的所述数据包。
所述处理单元1301具体用于：
根据所述数据包所属的流为所述数据包分配所述流标识；或者
从第三设备发送的流标识列表中确定与所述数据包所属的流对应的流标识。
关于图13所述的装置的其它内容，可以参考图1以及与图1有关的描述，在此不再赘述。
基于相同的技术构思，本申请实施例还提供一种数据处理装置，该装置可执行图4所述的方法流程，以及可以执行图5所述的方法流程中第一设备所实现的功能。
如图14所示，为本申请实施例提供一种数据处理装置结构示意图。
参见图14，该装置包括：
处理单元1401，用于当第一流映射的无线承载RB由第一RB更改为第二RB后，确定结束数据包，所述结束数据包为第一设备通过所述第一RB发送的属于所述第一流的最后一个数据包；
收发单元1402，用于向第二设备发送结束指示信息以及所述结束数据包；所述结束指示信息用于指示所述第一设备通过所述第一RB发送的属于所述第一流的数据包已经发送完毕。
关于图14所述的装置的其它内容，可以参考图4以及与图4有关的描述，在此不再赘述。
基于相同的技术构思，本申请实施例还提供一种数据处理装置，该装置可执行图4所述的方法流程，以及可以执行图5所述的方法流程中第二设备所实现的功能。
如图15所示，为本申请实施例提供一种数据处理装置结构示意图。
参见图15，该装置包括：
收发单元1501，用于接收第一设备发送的结束指示信息；所述结束指示信息为所述第一设备经由第一无线承载RB发送完属于第一流的最后一个数据包后发送的；所述结束指示信息用于指示所述第一设备通过所述第一RB发送的属于所述第一流的数据包已经发送完毕；
处理单元1502，用于处理通过所述第二RB接收到的属于所述第一流的数据包。
关于图15所述的装置的其它内容，可以参考图4以及与图4有关的描述，在此不再赘述。
基于相同的技术构思，本申请实施例还提供一种数据处理装置，该装置可执行图6所述的方法流程，以及可以执行图7所述的方法流程中第一接入网设备所实现的功能。
如图16所示，为本申请实施例提供一种数据处理装置结构示意图。
参见图16，该装置包括：
收发单元1601，用于向第二接入网设备发送第一消息，用于请求将终端切换到所述第二接入网设备；接收所述第二接入网设备返回的包括第一映射关系的第一响应消息；所述所述第一映射关系为所述终端中每个流与隧道端点标识TEID的映射关系；
处理单元1602，用于根据所述第一映射关系将所述终端的每个流的数据包转发给所述第二接入网设备。
关于图16所述的装置的其它内容，可以参考图6以及与图6有关的描述，在此不再赘述。
基于相同的技术构思，本申请实施例还提供一种数据处理装置，该装置可执行图6所述的方法流程，以及可以执行图7所述的方法流程中第二接入网设备所实现的功能。
如图17所示，为本申请实施例提供一种数据处理装置结构示意图。
参见图17，该装置包括：
收发单元1701，用于接收第一接入网设备发送的第一消息，用于请求将终端切换到所述第二接入网设备；向所述第一接入网设备返回包括第一映射关系的第一响应消息，并接收所述第一接入网设备根据所述第一映射关系转发的所述终端的每个流的数据包；所述第一映射关系为所述第二接入网设备确定的所述终端中每个流与TEID的映射关系。
关于图17所述的装置的其它内容，可以参考图6以及与图6有关的描述，在此不再赘述。
基于相同的技术构思，本申请实施例还提供一种数据处理装置，该装置可执行图10所述的方法流程，以及可以执行图11所述的方法流程中第一接入网设备所实现的功能。
如图18所示，为本申请实施例提供一种数据处理装置结构示意图。
参见图18，该装置包括：
收发单元1801，用于向第一核心网设备发送第一消息，用于请求将终端从所述第一接入网设备切换到第二接入网设备；接收所述第一核心网设备返回的包括第一映射关系的第一响应消息；所述第一映射关系为所述第二接入网设备为所述终端确定的每个RB与TEID的映射关系；
处理单元1802，用于根据所述第一映射关系将所述终端的每个RB的数据包转发给所述第二接入网设备。
关于图18所述的装置的其它内容，可以参考图10以及与图10有关的描述，在此不再赘述。
如图19所示，为本申请实施例提供一种数据处理装置结构示意图。
参见图19，该装置包括：
处理单元1901，用于确定第二映射关系，所述第二映射关系为终端在所述第一接入网设备所处的网络中使用的每个RB与流的映射关系；所述第二映射关系由所述终端的每个RB在第一核心网设备所处的网络所使用的TFT模板以及所述终端的每个RB在所述第二核心网设备所处的网络所使用的TFT模板确定；
收发单元1902，用于向第二接入网设备发送包括所述第二映射关系的第三消息，用于请求将终端从第一接入网设备切换到第二接入网设备。
关于图19所述的装置的其它内容，可以参考图10以及与图10有关的描述，在此不再赘述。
如图20所示，为本申请实施例提供一种数据处理装置结构示意图。
参见图20，该装置包括：
收发单元2001，用于接收第二核心网设备发送的包括第二映射关系的第三消息，用于请求将终端从第一接入网设备切换到所述第二接入网设备，所述第二映射关系为所述终端在所述第一接入网设备所处的网络中使用的每个RB与流的映射关系；向所述第二核心网设备返回包括第一映射关系的响应消息；所述第一映射关系为所述第二接入网设备为所述终端确定的每个RB与TEID的映射关系。
关于图20所述的装置的其它内容，可以参考图10以及与图10有关的描述，在此不再赘述。
如图21所示，为本申请实施例提供一种数据处理装置结构示意图。
参见图21，该装置包括：
处理单元2101，用于为终端分配所述上行资源；
收发单元2102，用于向所述终端发送第一指示信息，所述第一指示信息用于指示数据在所述上行资源上正确传输的传输成功率。
关于图21所述的装置的其它内容，可以参考图12以及与图12有关的描述，在此不再赘述。
如图22所示，为本申请实施例提供一种数据处理装置结构示意图。
参见图22，该装置包括：
处理单元2201，用于确定接入网设备为所述终端分配的上行资源，并接收所述接入网设备发送的第一指示信息，所述第一指示信息用于指示数据在所述上行资源上正确传输的传输成功率；
收发单元2202，用于根据所述第一指示信息在所述上行资源上传输的数据。
关于图22所述的装置的其它内容，可以参考图12以及与图12有关的描述，在此不再赘述。
基于相同的技术构思，本申请实施例还提供一种数据处理装置，该装置可执行图1所述的方法流程，以及可以执行图2至图3所述的方法流程中第一设备所实现的功能。
如图23所示，为本申请实施例提供一种数据处理装置结构示意图。
参见图23，该装置包括：
处理器2301，用于确定数据包所属的流；根据所述数据包所属的流确定流标识；
收发机2302，用于向第二接入网设备发送包括所述流标识的所述数据包。
关于图23所述的装置的其它内容，可以参考图1以及与图1有关的描述，在此不再赘述。
基于相同的技术构思，本申请实施例还提供一种数据处理装置，该装置可执行图4所述的方法流程，以及可以执行图5所述的方法流程中第一设备所实现的功能。
如图24所示，为本申请实施例提供一种数据处理装置结构示意图。
参见图24，该装置包括：
处理器2401，用于当第一流映射的无线承载RB由第一RB更改为第二RB后，确定结束数据包，所述结束数据包为第一设备通过所述第一RB发送的属于所述第一流的最后一个数据包；
收发机2402，用于向第二设备发送结束指示信息以及所述结束数据包；所述结束指示信息用于指示所述第一设备通过所述第一RB发送的属于所述第一流的数据包已经发送完毕。
关于图24所述的装置的其它内容，可以参考图4以及与图4有关的描述，在此不再赘述。
基于相同的技术构思，本申请实施例还提供一种数据处理装置，该装置可执行图4所述的方法流程，以及可以执行图5所述的方法流程中第一设备所实现的功能。
如图25所示，为本申请实施例提供一种数据处理装置结构示意图。
参见图25，该装置包括：
收发机2501，用于接收第一设备发送的结束指示信息；所述结束指示信息为所述第一设备经由第一无线承载RB发送完属于第一流的最后一个数据包后发送的；所述结束指示信息用于指示所述第一设备通过所述第一RB发送的属于所述第一流的数据包已经发送完毕；
处理器2502，用于处理通过所述第二RB接收到的属于所述第一流的数据包。
关于图25所述的装置的其它内容，可以参考图4以及与图4有关的描述，在此不再赘述。
基于相同的技术构思，本申请实施例还提供一种数据处理装置，该装置可执行图6所 述的方法流程，以及可以执行图7所述的方法流程中第一接入设备所实现的功能。
如图26所示，为本申请实施例提供一种数据处理装置结构示意图。
参见图26，该装置包括：
收发机2601，用于向第二接入网设备发送第一消息，用于请求将终端切换到所述第二接入网设备；接收所述第二接入网设备返回的包括第一映射关系的第一响应消息；所述所述第一映射关系为所述终端中每个流与隧道端点标识TEID的映射关系；
处理器2602，用于根据所述第一映射关系将所述终端的每个流的数据包转发给所述第二接入网设备。
关于图26所述的装置的其它内容，可以参考图6以及与图6有关的描述，在此不再赘述。
基于相同的技术构思，本申请实施例还提供一种数据处理装置，该装置可执行图6所述的方法流程，以及可以执行图7所述的方法流程中第二接入网设备所实现的功能。
如图27所示，为本申请实施例提供一种数据处理装置结构示意图。
参见图27，该装置包括：收发机2701，处理器2702。
收发机2701，用于接收第一接入网设备发送的第一消息，用于请求将终端切换到所述第二接入网设备；向所述第一接入网设备返回包括第一映射关系的第一响应消息，并接收所述第一接入网设备根据所述第一映射关系转发的所述终端的每个流的数据包；所述第一映射关系为所述第二接入网设备确定的所述终端中每个流与TEID的映射关系。
关于图27所述的装置的其它内容，可以参考图6以及与图6有关的描述，在此不再赘述。
基于相同的技术构思，本申请实施例还提供一种数据处理装置，该装置可执行图10所述的方法流程，以及可以执行图11所述的方法流程中第一接入网设备所实现的功能。
如图18所示，为本申请实施例提供一种数据处理装置结构示意图。
参见图28，该装置包括：
收发机2801，用于向第一核心网设备发送第一消息，用于请求将终端从所述第一接入网设备切换到第二接入网设备；接收所述第一核心网设备返回的包括第一映射关系的第一响应消息；所述第一映射关系为所述第二接入网设备为所述终端确定的每个RB与TEID的映射关系；
处理器2802，用于根据所述第一映射关系将所述终端的每个RB的数据包转发给所述第二接入网设备。
关于图28所述的装置的其它内容，可以参考图10以及与图10有关的描述，在此不再赘述。
如图29所示，为本申请实施例提供一种数据处理装置结构示意图。
参见图29，该装置包括：
处理器2901，用于确定第二映射关系，所述第二映射关系为终端在所述第一接入网设备所处的网络中使用的每个RB与流的映射关系；所述第二映射关系由所述终端的每个RB在第一核心网设备所处的网络所使用的TFT模板以及所述终端的每个RB在所述第二核心网设备所处的网络所使用的TFT模板确定；
收发机2902，用于向第二接入网设备发送包括所述第二映射关系的第三消息，用于请求将终端从第一接入网设备切换到第二接入网设备。
关于图29所述的装置的其它内容，可以参考图10以及与图10有关的描述，在此不再赘述。
如图30所示，为本申请实施例提供一种数据处理装置结构示意图。
参见图30，该装置包括：收发机3001，处理器3002。
收发机3001，用于接收第二核心网设备发送的包括第二映射关系的第三消息，用于请求将终端从第一接入网设备切换到所述第二接入网设备，所述第二映射关系为所述终端在所述第一接入网设备所处的网络中使用的每个RB与流的映射关系；向所述第二核心网设备返回包括第一映射关系的响应消息；所述第一映射关系为所述第二接入网设备为所述终端确定的每个RB与TEID的映射关系。
关于图30所述的装置的其它内容，可以参考图10以及与图10有关的描述，在此不再赘述。
如图31所示，为本申请实施例提供一种数据处理装置结构示意图。
参见图31，该装置包括：
处理器3101，用于为终端分配所述上行资源；
收发机3102，用于向所述终端发送第一指示信息，所述第一指示信息用于指示数据在所述上行资源上正确传输的传输成功率。
关于图31所述的装置的其它内容，可以参考图12以及与图12有关的描述，在此不再赘述。
如图32所示，为本申请实施例提供一种数据处理装置结构示意图。
参见图32，该装置包括：
处理器3201，用于确定接入网设备为所述终端分配的上行资源，并接收所述接入网设备发送的第一指示信息，所述第一指示信息用于指示数据在所述上行资源上正确传输的传输成功率；
收发机3202，用于根据所述第一指示信息在所述上行资源上传输的数据。
关于图32所述的装置的其它内容，可以参考图12以及与图12有关的描述，在此不再赘述。
图23至图32中，收发信机可以是有线收发信机，无线收发信机或其组合。有线收发信机例如可以为以太网接口。以太网接口可以是光接口，电接口或其组合。无线收发信机例如可以为无线局域网收发信机，蜂窝网络收发信机或其组合。处理器可以是中央处理器(英文：central processing unit，缩写：CPU)，网络处理器(英文：network processor，缩写：NP)或者CPU和NP的组合。处理器还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(英文：application-specific integrated circuit，缩写：ASIC)，可编程逻辑器件(英文：programmable logic device，缩写：PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(英文：complex programmable logic device，缩写：CPLD)，现场可编程逻辑门阵列(英文：field-programmable gate array，缩写：FPGA)，通用阵列逻辑(英文：generic array logic,缩写：GAL)或其任意组合。存储器可以包括易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)；存储器也可以包括非易失性存储器(英文：non-volatile memory)，例如只读存储器(英文：read-only memory，缩写：ROM)，快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)；存储器还可以包括上述 种类的存储器的组合。
可选的，图23至图32中还可以包括总线接口，总线接口可以包括任意数量的互联的总线和桥，具体由处理器代表的一个或多个处理器和存储器代表的存储器的各种电路链接在一起。总线接口还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发信机提供用于在传输介质上与各种其他设备通信的单元。处理器负责管理总线架构和通常的处理，存储器可以存储处理器在执行操作时所使用的数据。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本申请范围的所有变更和修改。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (27)

  1. 一种数据处理方法，其特征在于，该方法包括：
    第一设备确定数据包所属的流；
    所述第一设备根据所述数据包所属的流确定流标识，并向第二设备发送包括所述流标识的所述数据包。
  2. 根据权利要求1所述的方法，其特征在于，所述第一设备根据所述数据包所属的流确定流标识，包括：
    所述第一设备根据所述数据包所属的流为所述数据包分配所述流标识；或者
    所述第一设备从第三设备发送的流标识列表中确定与所述数据包所属的流对应的流标识。
  3. 根据权利要求1或2所述的方法，其特征在于，所述流标识位于所述数据包的包头。
  4. 根据权利要求1或2所述的方法，其特征在于，所述流标识位于所述数据包的数据包序列号字段中，并占据所述数据包序列号字段中的K个比特位，K为正整数。
  5. 根据权利要求4所述的方法，其特征在于，所述第一设备接收数据包之后，还包括：
    所述第一设备将属于同一个流的所有数据包作为一组，并分别为每一组数据包独立分配数据包序列号；
    所述第一设备将所述流标识通过所述数据包发送给第二设备之前，还包括：
    所述第一设备根据所述数据包的数据包序列号字段中除了所述流标识所占据的比特位之外的比特位对所述数据包进行头压缩和加密操作。
  6. 一种数据处理方法，其特征在于，包括：
    当第一流映射的无线承载RB由第一RB更改为第二RB后，第一设备确定结束数据包，所述结束数据包为所述第一设备通过所述第一RB发送的属于所述第一流的最后一个数据包；
    所述第一设备向第二设备发送结束指示信息以及所述结束数据包；所述结束指示信息用于指示所述第一设备通过所述第一RB发送的属于所述第一流的数据包已经发送完毕。
  7. 根据权利要求6所述的方法，其特征在于，所述第一设备确定结束数据包之后，还包括：
    所述第一设备将所有未发送的且属于所述第一流的数据包通过所述第二RB发送。
  8. 根据权利要求6或7所述的方法，其特征在于，第一设备确定与第一流映射的无线承载RB由第一RB更改为第二RB，包括：
    所述第一设备接收第三设备发送的重映射指令，并根据重映射指令确定与第一流映射的RB由第一无线承载RB更改为第二RB。
  9. 根据权利要求1所述的方法，其特征在于，所述第一设备向第二设备发送结束指示信息以及所述结束数据包，包括：
    所述第一设备向所述第二设备发送包括所述结束指示信息的结束数据包；或者
    所述第一设备在向所述第二设备发送所述结束数据包之后，向所述第二设备发送所述结束指示信息。
  10. 一种数据处理方法，其特征在于，包括：
    第二设备接收第一设备发送的结束指示信息；所述结束指示信息为所述第一设备经由第一无线承载RB发送完属于第一流的最后一个数据包后发送的；所述结束指示信息用于指示所述第一设备通过所述第一RB发送的属于所述第一流的数据包已经发送完毕；
    所述第二设备处理通过所述第二RB接收到的属于所述第一流的数据包。
  11. 一种数据处理方法，其特征在于，该方法包括：
    第一接入网设备向第二接入网设备发送第一消息，所述第一消息用于请求将终端切换到所述第二接入网设备；
    所述第一接入网设备接收所述第二接入网设备返回的包括第一映射关系的第一响应消息；所述第一映射关系为所述终端中每个流与隧道端点标识TEID的映射关系；
    所述第一接入网设备根据所述第一映射关系将所述终端的每个流的数据包转发给所述第二接入网设备。
  12. 根据权利要求11所述的方法，其特征在于，所述第一消息中包括第二映射关系；所述第二映射关系为所述终端在所述第一接入网设备所处的网络中使用的每个流与RB的映射关系。
  13. 根据权利要求11或12所述的方法，其特征在于，所述第一响应消息中还包括第三映射关系；所述第三映射关系为所述第二接入网设备为所述终端中每个流确定的流与RB的映射关系或者为所述第二接入网设备对应的核心网设备为所述终端中每个流确定的流与RB的映射关系。
  14. 一种数据处理方法，其特征在于，该方法包括：
    第二接入网设备接收第一接入网设备发送的第一消息，用于请求将终端切换到所述第二接入网设备；
    所述第二接入网设备向所述第一接入网设备返回包括第一映射关系的第一响应消息，并接收所述第一接入网设备根据所述第一映射关系转发的所述终端的每个流的数据包；所述第一映射关系为所述终端中每个流与隧道端点标识TEID的映射关系。
  15. 根据权利要求14所述的方法，其特征在于，所述第一消息中包括第二映射关系；所述第二映射关系为所述终端在所述第一接入网设备所处的网络中使用的每个流与RB的映射关系。
  16. 根据权利要求15所述的方法，其特征在于，所述第一响应消息中包括第三映射关系；所述第三映射关系为所述第二接入网设备为所述终端中每个流确定的与RB的映射关系或者为所述第二接入网设备对应的核心网设备为所述终端中每个流确定的流与RB的映射关系。
  17. 根据权利要求16所述的方法，其特征在于，所述第二接入网设备接收所述第一接入网设备根据所述第一映射关系转发的所述终端的每个流的数据包之后，还包括：
    所述第二接入网设备根据所述第二映射关系以及所述第三映射关系确定所述第二映射关系中的目标流映射的第一RB更改为第二RB，则在接收到所述目标流的目标数据包之后，确定发送所述目标数据包所使用的RB；
    其中，所述目标流为所述第二映射关系中的任意一个流；所述目标数据包为所述目标流中的任意一个数据包。
  18. 根据权利要求17所述的方法，其特征在于，所述第二接入网设备确定发送所述 目标数据包所使用的RB，包括：
    所述第二接入网设备若确定所述目标数据包未被所述目标数据包的接收方正确接收且所述目标数据包之后的数据包被所述目标数据包的接收方正确接收，则在所述第一RB中发送所述目标数据包；或者
    所述第二接入网设备若确定所述目标数据包未被所述目标数据包的接收方正确接收且所述目标数据包之后的数据包未被所述目标数据包的接收方正确接收，则在所述第二RB中发送所述目标数据包；或者
    所述第二接入网设备若确定所述目标数据包未被所述目标数据包的接收方正确接收，则在所述第二RB中发送所述目标数据包；或者
    所述第二接入网设备若无法确定所述目标数据包的接收状态，则在所述第一RB中发送所述目标数据包。
  19. 一种数据处理装置，其特征在于，包括：
    处理单元，用于确定数据包所属的流；根据所述数据包所属的流确定流标识；
    收发单元，用于向第二接入网设备发送包括所述流标识的所述数据包。
  20. 根据权利要求19所述的装置，其特征在于，所述处理单元具体用于：
    根据所述数据包所属的流为所述数据包分配所述流标识；或者
    从第三设备发送的流标识列表中确定与所述数据包所属的流对应的流标识。
  21. 根据权利要求19或20所述的装置，其特征在于，所述流标识位于所述数据包的数据包序列号字段中，并占据所述数据包序列号字段中的K个比特位，K为正整数。
  22. 一种数据处理装置，其特征在于，包括：
    处理单元，用于当第一流映射的无线承载RB由第一RB更改为第二RB后，确定结束数据包，所述结束数据包为第一设备通过所述第一RB发送的属于所述第一流的最后一个数据包；
    收发单元，用于向第二设备发送结束指示信息以及所述结束数据包；所述结束指示信息用于指示所述第一设备通过所述第一RB发送的属于所述第一流的数据包已经发送完毕。
  23. 根据权利要求22所述的装置，其特征在于，所述处理单元具体用于：
    接收第三设备发送的重映射指令，并根据重映射指令确定与第一流映射的RB由第一无线承载RB更改为第二RB。
  24. 根据权利要求22所述的装置，其特征在于，所述收发单元具体用于：
    向所述第二设备发送包括所述结束指示信息的结束数据包；或者
    在向所述第二设备发送所述结束数据包之后，向所述第二设备发送所述结束指示信息。
  25. 一种数据处理装置，其特征在于，包括：
    收发单元，用于接收第一设备发送的结束指示信息；所述结束指示信息为所述第一设备经由第一无线承载RB发送完属于第一流的最后一个数据包后发送的；所述结束指示信息用于指示所述第一设备通过所述第一RB发送的属于所述第一流的数据包已经发送完毕；
    处理单元，用于处理通过所述第二RB接收到的属于所述第一流的数据包。
  26. 一种数据处理装置，其特征在于，该装置包括：
    收发单元，用于向第二接入网设备发送第一消息，用于请求将终端切换到所述第二接入网设备；接收所述第二接入网设备返回的包括第一映射关系的第一响应消息；所述所述第一映射关系为所述终端中每个流与隧道端点标识TEID的映射关系；
    处理单元，用于根据所述第一映射关系将所述终端的每个流的数据包转发给所述第二接入网设备。
  27. 一种数据处理装置，其特征在于，该装置包括：
    收发单元，用于接收第一接入网设备发送的第一消息，用于请求将终端切换到所述第二接入网设备；向所述第一接入网设备返回包括第一映射关系的第一响应消息，并接收所述第一接入网设备根据所述第一映射关系转发的所述终端的每个流的数据包；所述第一映射关系为所述第二接入网设备确定的所述终端中每个流与TEID的映射关系。
PCT/CN2017/096215 2016-08-15 2017-08-07 一种数据处理方法及装置 Ceased WO2018032991A1 (zh)

Priority Applications (9)

Application Number Priority Date Filing Date Title
EP25190092.4A EP4661368A3 (en) 2016-08-15 2017-08-07 Data processing method and apparatus
EP17840966.0A EP3493582B1 (en) 2016-08-15 2017-08-07 Methods and apparatus for remapping a flow to a radio bearer
EP26150124.1A EP4716179A3 (en) 2016-08-15 2017-08-07 Data processing method and apparatus
EP20167012.2A EP3745767B1 (en) 2016-08-15 2017-08-07 Data processing method and apparatus
BR112019003025-5A BR112019003025B1 (pt) 2016-08-15 2017-08-07 Método e aparelho de processamento de dados
EP22199519.4A EP4184999B1 (en) 2016-08-15 2017-08-07 Data processing method and apparatus
US16/277,368 US10880773B2 (en) 2016-08-15 2019-02-15 Wireless communication method and apparatus
US17/111,165 US11997529B2 (en) 2016-08-15 2020-12-03 Wireless communication method and apparatus
US18/636,903 US20240365161A1 (en) 2016-08-15 2024-04-16 Wireless Communication Method and Apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610673593.7A CN107770807B (zh) 2016-08-15 2016-08-15 一种数据处理方法及装置
CN201610673593.7 2016-08-15

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/277,368 Continuation US10880773B2 (en) 2016-08-15 2019-02-15 Wireless communication method and apparatus

Publications (1)

Publication Number Publication Date
WO2018032991A1 true WO2018032991A1 (zh) 2018-02-22

Family

ID=61197384

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/096215 Ceased WO2018032991A1 (zh) 2016-08-15 2017-08-07 一种数据处理方法及装置

Country Status (6)

Country Link
US (3) US10880773B2 (zh)
EP (5) EP4184999B1 (zh)
CN (2) CN107770807B (zh)
BR (1) BR112019003025B1 (zh)
ES (2) ES2934613T3 (zh)
WO (1) WO2018032991A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3720033A4 (en) * 2018-06-15 2021-03-31 Guangdong Oppo Mobile Telecommunications Corp., Ltd. METHOD OF SENDING DATA IN A SEQUENCE, NETWORK DEVICE AND TERMINAL DEVICE

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4391706B1 (en) 2016-09-29 2025-06-04 Nokia Technologies Oy Radio bearer switching in radio access
CN109041119B9 (zh) * 2017-06-08 2020-07-03 维沃移动通信有限公司 一种数据传输方法、相关设备及系统
EP3804396A4 (en) * 2018-06-01 2022-03-02 Telefonaktiebolaget LM Ericsson (publ) Method for bundling sampling data for wireless transmission
US10756795B2 (en) 2018-12-18 2020-08-25 XCOM Labs, Inc. User equipment with cellular link and peer-to-peer link
US11063645B2 (en) * 2018-12-18 2021-07-13 XCOM Labs, Inc. Methods of wirelessly communicating with a group of devices
US11330649B2 (en) 2019-01-25 2022-05-10 XCOM Labs, Inc. Methods and systems of multi-link peer-to-peer communications
CN110536263A (zh) * 2019-07-11 2019-12-03 中兴通讯股份有限公司 一种数据传输方法、装置、第一通信节点及第二通信节点
US12089098B2 (en) * 2019-08-14 2024-09-10 Nokia Technologies Oy Feedback on network-assisted fallback to contention-based random access
CN116325900B (zh) * 2020-10-22 2026-01-06 华为技术有限公司 一种通信方法及装置
US12107744B2 (en) * 2022-05-12 2024-10-01 Mellanox Technologies, Ltd. Cycle-based per-flow packet drop counting
CN121531407A (zh) * 2026-01-15 2026-02-13 荣耀终端股份有限公司 通信方法、装置、系统及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101754373A (zh) * 2009-12-28 2010-06-23 华为技术有限公司 操作指示方法、服务网关和核心网络系统
CN102892143A (zh) * 2011-07-20 2013-01-23 华为技术有限公司 数据分流的方法以及用户设备
CN103945470A (zh) * 2013-01-18 2014-07-23 华为技术有限公司 切换方法、源通信节点和目标通信节点

Family Cites Families (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7609718B2 (en) * 2002-05-15 2009-10-27 Broadcom Corporation Packet data service over hyper transport link(s)
KR20050101006A (ko) * 2004-04-16 2005-10-20 삼성전자주식회사 멀티캐스트 멀티미디어 방송 서비스를 지원하는 이동통신시스템에서 제어 정보를 효율적으로 전송하는 방법
ES2526199T3 (es) 2006-08-18 2015-01-08 Telefonaktiebolaget Lm Ericsson (Publ) Correlación que implica cambio inter sistema entre diferentes tipos de portadores radio
MX2011008282A (es) * 2009-02-13 2011-08-24 Panasonic Corp Dispositivo de comunicacion y metodo de comunicacion.
US8320827B2 (en) * 2009-06-17 2012-11-27 Interdigital Patent Holdings, Inc. Method and apparatus for performing handover with a relay node
CN103118401B (zh) * 2009-06-19 2015-09-30 华为技术有限公司 业务承载映射方法及通信设备
CN104797007B (zh) * 2010-08-12 2018-05-11 华为技术有限公司 一种通信系统
EP2557870B1 (en) * 2011-08-10 2020-07-08 Alcatel Lucent Configuring transmissions
CN103517356B (zh) * 2012-06-28 2017-04-05 电信科学技术研究院 一种进行切换的方法、系统和设备
US9900793B2 (en) * 2013-01-11 2018-02-20 Lg Electronics Inc. Method and apparatus for transmitting information in wireless communication system
US9497682B2 (en) * 2013-06-07 2016-11-15 Intel Corporation Central processing unit and methods for supporting coordinated multipoint transmission in an LTE network
WO2015026055A1 (ko) 2013-08-23 2015-02-26 엘지전자 주식회사 다중의 rat들에 동시에 접속된 단말의 링크 실패를 관리하는 방법 및 이를 수행하는 장치
US9350550B2 (en) * 2013-09-10 2016-05-24 M2M And Iot Technologies, Llc Power management and security for wireless modules in “machine-to-machine” communications
EP3063896A2 (en) * 2013-10-30 2016-09-07 Interdigital Patent Holdings, Inc. Carrier aggregation configuration in wireless systems
CN105917722B (zh) * 2014-01-22 2019-12-13 瑞典爱立信有限公司 无线通信网络中扩展信令的方法和装置
US9713044B2 (en) 2014-01-30 2017-07-18 Sharp Kabushiki Kaisha Systems and methods for dual-connectivity operation
US9544942B2 (en) * 2014-02-18 2017-01-10 Qualcomm Incorporated DCH to non-DCH state switching of user equipment in UMTS
US9794266B2 (en) * 2014-09-05 2017-10-17 Qualcomm Incorporated Using multiple credentials for access and traffic differentiation
EP3958613B1 (en) * 2014-11-12 2025-05-14 Huawei Technologies Co., Ltd. Method and device for controlling binding of data flow to bearer
CN104363598B (zh) * 2014-11-25 2018-03-23 电信科学技术研究院 一种drb映射方法及装置
CN106031277B (zh) * 2015-01-29 2018-11-30 华为技术有限公司 无线承载重配置方法、建立方法、用户设备和基站
WO2016130057A1 (en) * 2015-02-10 2016-08-18 Telefonaktiebolaget Lm Ericsson (Publ) Systems and methods for facilitating the transition of a wireless communication device (wcd) from a cell_fach state to a cell_dch state
US10461908B2 (en) * 2015-11-11 2019-10-29 Qualcomm Incorporated Techniques for providing channels in low latency LTE wireless communications
CN106993313A (zh) * 2016-01-21 2017-07-28 中兴通讯股份有限公司 一种实现承载切换的方法及终端和基站
US10959240B2 (en) * 2016-04-15 2021-03-23 Qualcomm Incorporated Providing quality-of-service in wireless communications
US11122643B2 (en) * 2016-04-27 2021-09-14 Apple Inc. LWIP enhancements for reliable DRB switching
CN107645791A (zh) * 2016-07-22 2018-01-30 电信科学技术研究院 一种传输数据流的无线承载处理方法及装置
TWI710277B (zh) * 2016-07-26 2020-11-11 財團法人工業技術研究院 基於使用者設備輔助回饋來控制可配置的承載的基站、使用者設備及方法
US10911977B2 (en) * 2016-08-01 2021-02-02 Samsung Electronics Co., Ltd. Method and apparatus for managing data communication in wireless communication network
WO2018030982A1 (en) * 2016-08-08 2018-02-15 Nokia Technologies Oy End marker handling for mobility between 5g and lte
CN110463254B (zh) * 2017-03-22 2022-11-22 Lg电子株式会社 用于在无线通信系统中基于服务质量(QoS)框架发送UL分组的方法及其设备
US11071025B2 (en) * 2018-06-29 2021-07-20 FG Innovation Company Limited Cell handover with minimum mobility interruption

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101754373A (zh) * 2009-12-28 2010-06-23 华为技术有限公司 操作指示方法、服务网关和核心网络系统
CN102892143A (zh) * 2011-07-20 2013-01-23 华为技术有限公司 数据分流的方法以及用户设备
CN103945470A (zh) * 2013-01-18 2014-07-23 华为技术有限公司 切换方法、源通信节点和目标通信节点

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "QoS Framework for NR", 3GPP TSG-RAN WG2 MEETING #96 R2-168657, 13 November 2016 (2016-11-13), XP051178213 *
HUAWEI ET AL.: "Considerations on 5G RAN QoS Framework", 3GPP TSG-RAN2 MEETING #94 R2-164267, 14 May 2016 (2016-05-14), XP051095206 *
See also references of EP3493582A4 *
ZTE ET AL.: "Further Discussion on the New UP Protocol Layer for QoS", 3GPP TSG-RAN WG2 MEETING #97 R2-1701119, 12 February 2017 (2017-02-12), XP051211831 *
ZTE: "Discussion on the QoS Control in the NextGen RAN", 3GPP TSG-RAN WG2 MEETING #93BIS R2-162622, 1 April 2016 (2016-04-01), XP051082187 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3720033A4 (en) * 2018-06-15 2021-03-31 Guangdong Oppo Mobile Telecommunications Corp., Ltd. METHOD OF SENDING DATA IN A SEQUENCE, NETWORK DEVICE AND TERMINAL DEVICE
US11018832B2 (en) 2018-06-15 2021-05-25 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method for submitting data in sequence, network device and terminal device
US11689334B2 (en) 2018-06-15 2023-06-27 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method for submitting data in sequence, network device and terminal device

Also Published As

Publication number Publication date
US10880773B2 (en) 2020-12-29
EP4661368A2 (en) 2025-12-10
EP4716179A2 (en) 2026-03-25
EP3745767A1 (en) 2020-12-02
EP3493582A1 (en) 2019-06-05
EP4184999B1 (en) 2025-10-08
US20210153064A1 (en) 2021-05-20
CN107770807A (zh) 2018-03-06
BR112019003025A2 (pt) 2019-05-14
CN107770807B (zh) 2024-03-15
US20190182703A1 (en) 2019-06-13
EP3493582B1 (en) 2020-04-08
EP4716179A3 (en) 2026-04-01
EP4661368A3 (en) 2026-02-18
ES2934613T3 (es) 2023-02-23
EP3493582A4 (en) 2019-06-19
EP3745767B1 (en) 2022-10-05
EP4184999A1 (en) 2023-05-24
US11997529B2 (en) 2024-05-28
US20240365161A1 (en) 2024-10-31
EP4184999C0 (en) 2025-10-08
CN110493823A (zh) 2019-11-22
CN110493823B (zh) 2020-09-04
BR112019003025B1 (pt) 2021-12-21
ES3048758T3 (en) 2025-12-11

Similar Documents

Publication Publication Date Title
US11997529B2 (en) Wireless communication method and apparatus
US10779195B2 (en) Information transmission method and apparatus
US20250081025A1 (en) Method for obtaining data radio bearer identifier and base station
WO2019029643A1 (zh) 通信方法、基站、终端设备和系统
CN108337633B (zh) 数据分流配置方法、基站系统和用户终端
CN107040942A (zh) 业务流传输方法、装置及系统
CN108156633A (zh) 数据流重映射方法及装置和用户设备、ran设备
CN107005893A (zh) 服务质量的控制方法、设备及系统
CN111107581A (zh) Pdcp复制功能的确定、指示方法及装置、基站、终端
WO2024037423A1 (zh) 一种带宽控制的方法和装置
WO2019214524A1 (zh) 一种进行资源分配的方法和装置
WO2019214553A1 (zh) 一种进行资源分配的方法和装置
CN104780577B (zh) 一种数据资源在小区间进行切换传输的方法和设备
JP7285905B2 (ja) データ無線ベアラ識別子を取得するための方法および基地局
WO2018227444A1 (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: 17840966

Country of ref document: EP

Kind code of ref document: A1

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

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 2017840966

Country of ref document: EP

Effective date: 20190226

ENP Entry into the national phase

Ref document number: 112019003025

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20190214