Nothing Special   »   [go: up one dir, main page]

WO2018028295A1 - 切换场景下的QoS参数处理的方法及设备 - Google Patents

切换场景下的QoS参数处理的方法及设备 Download PDF

Info

Publication number
WO2018028295A1
WO2018028295A1 PCT/CN2017/087901 CN2017087901W WO2018028295A1 WO 2018028295 A1 WO2018028295 A1 WO 2018028295A1 CN 2017087901 W CN2017087901 W CN 2017087901W WO 2018028295 A1 WO2018028295 A1 WO 2018028295A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
target base
pdu flow
qos parameter
handover request
Prior art date
Application number
PCT/CN2017/087901
Other languages
English (en)
French (fr)
Inventor
汪颖
焦斌
Original Assignee
电信科学技术研究院
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 电信科学技术研究院 filed Critical 电信科学技术研究院
Priority to US16/323,767 priority Critical patent/US10959133B2/en
Priority to EP17838427.7A priority patent/EP3477991B1/en
Priority to KR1020197007268A priority patent/KR102210296B1/ko
Priority to JP2019506666A priority patent/JP6743281B2/ja
Publication of WO2018028295A1 publication Critical patent/WO2018028295A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H04W36/0044—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information of quality context information
    • 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]
    • 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/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0064—Transmission or use of information for re-establishing the radio link of control information between different access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/26—Reselection being triggered by specific parameters by agreed or negotiated communication parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
    • H04W36/1443—Reselecting a network or an air interface over a different radio air interface technology between licensed networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H04W36/302—Reselection being triggered by specific parameters by measured or perceived connection quality data due to low signal strength
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/543—Allocation or scheduling criteria for wireless resources based on quality criteria based on requested quality, e.g. QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a method and a device for processing QoS (Quality of Service) parameters in a handover scenario.
  • QoS Quality of Service
  • a bearer model in an LTE (Long Term Evolution) system in the related art is shown.
  • a core network control plane function entity is responsible for generating an E-RAB (Evolved Radio Access Bearer).
  • the QoS parameter of the evolved radio access bearer is a one-to-one mapping relationship between the air interface RB (Radio Bearer) and the E-RAB. Therefore, the QoS parameters of the air interface RB are directly generated by the core network control plane function entity.
  • E-RAB QoS parameters are directly generated by the core network control plane function entity.
  • the heterogeneous access technology in the mobile communication network leads to the need to support multiple tunneling protocols in the core network control plane functional entity to support mobility and guarantee QoS, such as GTP (GPRS (General Packet Radio Service) Tunneling Protocol). , GPRS tunneling protocol), PMIP (Proxy Mobile Internet Protocol), etc.
  • GTP GPRS (General Packet Radio Service) Tunneling Protocol
  • PMIP Proxy Mobile Internet Protocol
  • the 5G network that separates control and forwarding supports numerous tunneling protocols, which will lead to complex control logic and signaling interactions, thus affecting system performance. Therefore, 5G networks can consider QoS support enhancements on the general forwarding plane, such as simplifying the forwarding protocol. Optimize the QoS scheduling policy and enhance the packet forwarding capability of the forwarding plane.
  • connection management mechanism in the future 5G network needs to consider the connection access compatible with the EPS (Evolved Packet System).
  • the connection management may still need to provide interoperability management functions to handle the LTE network.
  • the tunnel manages the message and completes the tunnel management process.
  • the 5G core network control plane functional entity has no bearer concept, core network control.
  • the QoS parameters sent by the surface function entity CN-C to the NG-NB are configured with a flow granularity.
  • the access network NG-NB still performs QoS management with RB granularity, the access network needs to generate RB-level QoS parameters for use between the NG-NB and the UE and between the NG-NB and other wireless access entities. Interaction process.
  • the embodiments of the present disclosure provide a method and an apparatus for processing QoS parameters in a handover scenario, and a process for resolving QoS in a handover scenario.
  • a method for processing QoS parameters in a handover scenario comprising:
  • the source base station sends a handover request message to the target base station, where the handover request message includes: a QoS parameter based on a Protocol Data Unit (PDU) flow and/or an RB-based QoS parameter;
  • PDU Protocol Data Unit
  • the PDU flow based QoS parameter or the RB based QoS parameter is used by the target base station for admission control.
  • the handover request message further includes: a mapping relationship of RBs of the PDU flow generated by the source base station.
  • the method further includes:
  • the source base station receives the handover response message sent by the target base station, where the handover response message includes: information about the PDU flow that the target base station accepts successfully or fails or information about the RB.
  • a method for processing QoS parameters in a handover scenario comprising:
  • the target base station receives a handover request message sent by the source base station, where the handover request message includes: a QoS parameter based on the PDU flow and/or an RB-based QoS parameter;
  • the target base station performs admission control according to the PDU flow based QoS parameter or the RB based QoS parameter.
  • the method further includes:
  • the target base station generates, according to the QoS parameter based on the PDU flow, a convergence mapping relationship between the PDU flow of the target base station and the RB, and a configuration parameter of the corresponding RB.
  • the handover request message further includes: a mapping relationship of RBs of the PDU flow generated by the source base station;
  • the method further includes:
  • the target base station generates a convergence mapping relationship between the PDU flow of the target base station and the RB according to the mapping relationship of the RBs of the PDU flow generated by the source base station, and configuration parameters of the corresponding RB.
  • the method further includes:
  • the target base station sends a handover request response message to the source base station, where the handover request response message includes: information about the successfully or failed PDU flow or information of the RB.
  • the method further includes:
  • the target base station receives a transmission path update confirmation message sent by the core network control plane function entity.
  • a method for processing QoS parameters in a handover scenario includes:
  • the core network control plane function entity sends a handover request message to the target base station, where the handover request message includes: a QoS parameter based on the PDU flow and/or an RB-based QoS parameter;
  • the PDU flow based QoS parameter or the RB based QoS parameter is used by the target base station for admission control.
  • the method further includes:
  • the core network control plane function entity receives a handover request acknowledgement message sent by the target base station, where the handover request acknowledgement message includes information of a PDU flow or RB that the target base station accepts successfully or fails;
  • the core network control plane function entity sends a handover command to the source base station.
  • a method for processing QoS parameters in a handover scenario includes:
  • the target base station receives a handover request message sent by the core network control plane function entity, where the handover is requested
  • the request message includes: QoS parameters based on PDU flow and/or RB-based QoS parameters;
  • the target base station performs admission control according to the QoS parameter of the PDU flow or the QoS parameter based on the RB.
  • the method further includes:
  • the target base station generates, according to the QoS parameter based on the PDU flow, a convergence mapping relationship between the PDU flow of the target base station and the RB, and a configuration parameter of the corresponding RB.
  • the handover request message further includes: a mapping relationship of RBs of the PDU flow generated by the source base station;
  • the method further includes:
  • the target base station generates a convergence mapping relationship between the PDU flow of the target base station and the RB according to the mapping relationship of the RBs of the PDU flow generated by the source base station, and configuration parameters of the corresponding RB.
  • the method further includes:
  • the target base station sends a handover confirmation message to the core network control plane function entity, where the handover request acknowledgement message includes: information about the PDU flow or RB that the target base station accepts successfully or fails.
  • a source base station including:
  • a first sending module configured to send a handover request message to the target base station, where the handover request message includes: a QoS parameter based on the PDU flow and/or an RB-based QoS parameter;
  • the PDU flow based QoS parameter or the RB based QoS parameter is used by the target base station for admission control.
  • the handover request message further includes: a mapping relationship of RBs of the PDU flow generated by the source base station.
  • the source base station further includes:
  • the first receiving module is configured to receive a handover response message sent by the target base station, where the handover response message includes: information about a PDU flow or an RB that the target base station accepts successfully or fails.
  • a target base station is further provided, where the target base station includes:
  • a second receiving module configured to receive a handover request message sent by the source base station, where the handover request message includes: a QoS parameter based on the PDU flow and/or an RB-based QoS parameter;
  • the first admission control module is configured to perform admission control according to the PDU flow based QoS parameter or the RB based QoS parameter.
  • the target base station further includes:
  • a first generating module configured to generate, according to the PDU flow-based QoS parameter, a convergence mapping relationship between the PDU flow of the target base station and the RB, and a configuration parameter of the corresponding RB.
  • the handover request message further includes: a mapping relationship of RBs of the PDU flow generated by the source base station;
  • the target base station further includes:
  • a second generating module configured to generate, according to a mapping relationship of the RBs of the PDU flow generated by the source base station, a convergence mapping relationship between the PDU flow of the target base station and the RB, and a configuration parameter of the corresponding RB.
  • the target base station further includes:
  • the second sending module is configured to send a handover request response message to the source base station, where the handover request response message includes: information about the PDU flow or RB that the target base station accepts successfully or fails.
  • the target base station further includes:
  • a sixth sending module configured to send a transmission path update message to the core network control plane function entity, and carry the information of the received PDU flow;
  • the fifth receiving module is configured to receive a transmission path update confirmation message sent by the core network control plane function entity.
  • a core network control plane functional entity including:
  • a third sending module configured to send a handover request message to the target base station, where the handover request message includes: a QoS parameter based on the PDU flow and/or an RB-based QoS parameter;
  • the PDU flow based QoS parameter or the RB based QoS parameter is used by the target base station for admission control.
  • the core network control plane functional entity further includes:
  • a third receiving module configured to receive a handover request acknowledgement message sent by the target base station, where the handover request acknowledgement message includes information about PDU flow successfully received or failed by the target base station, or information about an RB;
  • the fourth sending module is configured to send a handover command to the source base station.
  • a target base station including:
  • a fourth receiving module configured to receive a handover request message sent by a core network control plane function entity, where the handover request message includes: a PDU flow based QoS parameter and/or an RB based QoS parameter;
  • a second admission control module configured to perform admission control according to the QoS parameter of the PDU flow or the QoS parameter based on the RB.
  • the target base station further includes:
  • a third generating module configured to generate, according to the PDU flow-based QoS parameter, a convergence mapping relationship between the PDU flow of the target base station and the RB, and a configuration parameter of the corresponding RB.
  • the handover request message further includes: a mapping relationship of RBs of the PDU flow generated by the source base station;
  • the target base station further includes:
  • a fourth generation module configured to generate, according to a mapping relationship of RBs of the PDU flow generated by the source base station, a convergence mapping relationship between the PDU flow of the target base station and the RB, and a configuration parameter of the corresponding RB.
  • the target base station further includes:
  • a fifth sending module configured to send a handover confirmation message to the core network control plane function entity, where the handover request acknowledgement message includes: information that the target base station accepts a successful or failed PDU flow or RB.
  • a source base station comprising: a processor, a memory, and a transceiver, wherein:
  • the processor is configured to read a program in the memory and perform the following process:
  • a handover request message to a target base station, where the handover request message includes: a QoS parameter based on a PDU flow and/or an RB-based QoS parameter;
  • the PDU flow-based QoS parameter or the RB-based QoS parameter is used for admission control by the target base station
  • the transceiver is configured to receive and transmit data
  • the memory is capable of storing data used by the processor when performing operations.
  • a target base station comprising: a processor, a memory, and a transceiver, wherein:
  • the processor is configured to read a program in the memory and perform the following process:
  • a handover request message sent by a source base station, where the handover request message includes: a QoS parameter based on a PDU flow and/or an RB-based QoS parameter;
  • the transceiver is configured to receive and transmit data
  • the memory is capable of storing data used by the processor when performing operations.
  • a core network control plane functional entity including: a processor, a memory, and a transceiver, where:
  • the processor is configured to read a program in the memory and perform the following process:
  • a handover request message to a target base station, where the handover request message includes: a QoS parameter based on a PDU flow and/or an RB-based QoS parameter;
  • the PDU flow-based QoS parameter or the RB-based QoS parameter is used for admission control by the target base station
  • the transceiver is configured to receive and transmit data
  • the memory is capable of storing data used by the processor when performing operations.
  • a target base station comprising: a processor, a memory, and a transceiver, wherein:
  • the processor is configured to read a program in the memory and perform the following process:
  • a handover request message sent by a core network control plane function entity, where the handover request message includes: a PDU flow based QoS parameter and/or an RB based QoS parameter;
  • the transceiver is configured to receive and transmit data
  • the memory is capable of storing data used by the processor when performing operations.
  • the source base station may carry the PDU flow-based QoS parameter and/or the RB-based QoS parameter to the target base station in the handover request message, and the target base station performs admission control according to the QoS parameter of the PDU flow or the RB-based QoS parameter, and
  • the PDU flow information or the RB information that is successfully and/or failed is returned in the handover request response, and the target eNB may aggregate the PDU flows with the same QoS requirements according to the received PDU flow information, and generate a convergence mapping relationship between the PDU flow and the RB.
  • the configuration parameters of the corresponding RB the target base station sends the received PDU flow information to the core network, and implements QoS processing in the handover scenario.
  • FIG. 1 is a schematic diagram of a bearer model in an LTE system in the related art
  • FIG. 2 is a schematic diagram of a typical LTE architecture
  • 3 is a schematic diagram of an architecture of future mobile communications
  • FIG. 4 is a schematic diagram of a 5G network architecture
  • FIG. 5 is a flowchart of a method for processing QoS parameters in a handover scenario in some embodiments of the present disclosure
  • FIG. 6 is another flowchart of a method for processing QoS parameters in a handover scenario in some embodiments of the present disclosure
  • FIG. 7 is still another flowchart of a method for processing QoS parameters in a handover scenario in some embodiments of the present disclosure
  • FIG. 8 is still another flowchart of a method for processing QoS parameters in a handover scenario in some embodiments of the present disclosure
  • FIG. 9 is a schematic diagram of a QoS processing flow based on PDU flow admission in some embodiments of the present disclosure.
  • FIG. 10 is a schematic diagram of a QoS processing flow based on RB admission in some embodiments of the present disclosure
  • FIG. 11 is another schematic diagram of a QoS processing flow based on PDU flow admission in some embodiments of the present disclosure
  • FIG. 12 is another schematic diagram of a QoS processing flow based on RB admission in some embodiments of the present disclosure
  • Figure 13 is a schematic illustration of a source base station in some embodiments of the present disclosure.
  • Figure 14 is a schematic diagram of a target base station in some embodiments of the present disclosure.
  • 15 is a schematic diagram of a core network control plane functional entity in some embodiments of the present disclosure.
  • 16 is another schematic diagram of a target base station in some embodiments of the present disclosure.
  • embodiments of the present disclosure may be implemented as a system, apparatus, device, method, or computer program product.
  • embodiments of the present disclosure may be embodied in the form of full hardware, complete software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.
  • the embodiments of the present disclosure can be applied to different network deployment structures.
  • two network deployment structures that may be adopted for future mobile communication are first introduced.
  • Deployment structure 1 base station and terminal
  • a typical LTE architecture is shown.
  • eNB evolved Node B
  • UE terminal
  • the cell in the connected state perform air interface data transmission and reception.
  • the deployment structure 2 is a network side node and a user side node, wherein the network side node is divided into a central unit (CU, Central Unit) and a distributed unit (DU, distributed unit), and the user side node is a terminal.
  • CU Central Unit
  • DU distributed unit
  • the network side node includes a central unit and a distributed node, and one central unit controls a plurality of distributed units deployed in a certain area, and the plurality of distributed units pass the TRP ( Transmission Reception Point, sending and receiving point) Port transmission, one or more TRPs can serve the terminal at the same time for data transmission.
  • TRP Transmission Reception Point, sending and receiving point
  • the present disclosure is applicable to the above two RAN (Radio Access Network) architectures.
  • the following is a unified description.
  • the network side wireless signaling and data transceiver nodes are collectively referred to as base stations (NG-NBs), whether they are eNBs in the deployment structure 1 or CU/DUs in the deployment structure 2 (the specific transmission and reception points are TRPs).
  • the network architecture includes three logical entities: CN-C (Core Network-Control, core network control plane function entity control plane function entity) located on the core network control plane functional entity. ), and CN-U (Core Network-User, core network control plane functional entity user plane functional entity); and NG-NB (Next Generation-Node B, Next Generation Base Station) and eLTE eNB (Evolved LTE) located in the access network Base station).
  • CN-C and NG-NB establish S1*-C interface for control plane signaling transmission
  • CN-U and NG-NB establish S1*-U for user plane data transmission.
  • An X2* interface is established between the NG-NBs of the radio access network, and the X2* connector supports both control planes (such as X2*-C) and user plane functions (such as X2*-U).
  • a control plane connection with a granularity of the UE may be established on the S1*-C (where the control plane connection corresponding to each UE may be identified by using an S1*-AP ID), and a PDU session (PDU session) is established on the S1*-U.
  • a PDU session PDU session
  • the PDU session on the U interface is a granular user plane connection (or user plane tunnel).
  • the radio access network may have one or more NG-NBs simultaneously serving the UE.
  • FIG. 5 a method for processing QoS parameters in a handover scenario is illustrated. The specific steps are as follows:
  • Step 501 The source base station sends a handover request message to the target base station, where the handover request message includes: a QoS parameter based on the PDU flow and/or an RB-based QoS parameter;
  • the PDU flow based QoS parameter or the RB based QoS parameter is used by the target base station for admission control.
  • the source base station and the target base station may correspond to two different eNBs in FIG. 2, or the source base station and the target base station may correspond to two different TRPs in FIG.
  • the handover request message further includes: a mapping relationship of RBs of the PDU flow generated by the source base station.
  • the method further includes:
  • the source base station receives the handover response message sent by the target base station, where the handover response message includes: information about the PDU flow or RB that the target base station accepts successfully or fails.
  • the source base station may carry the PDU flow-based QoS parameter and/or the RB-based QoS parameter to the target base station in the handover request message, and the target base station is based on the QoS parameter of the PDU flow or based on
  • the QoS parameters of the RB are subjected to the admission control, and the successful and/or failed PDU flow information or RB information is returned in the handover request response, and the target base station may aggregate the PDU flows with the same QoS requirements according to the received PDU flow information, and The aggregation mapping relationship between the PDU flow and the RB is generated, and the configuration parameters of the corresponding RB are sent, and the target base station sends the received PDU flow information to the core network.
  • the source base station may also carry the mapping relationship between the PDU flow generated by the source base station and the RB in the handover request message, and the target base station may refer to the mapping relationship to generate a mapping relationship between the PDU flow and the RB, and corresponding Configuration parameters.
  • FIG. 6 a method for processing QoS parameters in a handover scenario is illustrated. The specific steps are as follows:
  • Step 601 The target base station receives a handover request message sent by the source base station, where the handover request message includes: a QoS parameter based on the PDU flow and/or an RB-based QoS parameter;
  • Step 602 The target base station performs admission control according to the PDU flow based QoS parameter or the RB based QoS parameter.
  • the method further includes:
  • the target base station generates, according to the QoS parameter based on the PDU flow, a convergence mapping relationship between the PDU flow of the target base station and the RB, and a configuration parameter of the corresponding RB.
  • the handover request message further includes: a mapping relationship of RBs of the PDU flow generated by the source base station;
  • the method further includes:
  • the target base station generates a convergence mapping relationship between the PDU flow of the target base station and the RB according to the mapping relationship of the RBs of the PDU flow generated by the source base station, and configuration parameters of the corresponding RB.
  • the method further includes:
  • the message includes: the target base station accepts information of a successful or failed PDU flow or RB.
  • the method further includes:
  • the target base station receives a transmission path update confirmation message sent by the core network control plane function entity.
  • the source base station may carry the PDU flow-based QoS parameter and/or the RB-based QoS parameter to the target base station in the handover request message, and the target base station is based on the QoS parameter of the PDU flow or based on
  • the QoS parameters of the RB are subjected to the admission control, and the successful and/or failed PDU flow information or RB information is returned in the handover request response, and the target base station may aggregate the PDU flows with the same QoS requirements according to the received PDU flow information, and The aggregation mapping relationship between the PDU flow and the RB is generated, and the configuration parameters of the corresponding RB are sent, and the target base station sends the received PDU flow information to the core network.
  • the source base station may also carry the mapping relationship between the PDU flow generated by the source base station and the RB in the handover request message, and the target base station may refer to the mapping relationship to generate a mapping relationship between the PDU flow and the RB, and corresponding Configuration parameters.
  • FIG. 7 a method for processing QoS parameters in a handover scenario is illustrated. The specific steps are as follows:
  • Step 701 The core network control plane function entity sends a handover request message to the target base station, where the handover request message includes: a QoS parameter based on the PDU flow and/or an RB-based QoS parameter;
  • the PDU flow based QoS parameter or the RB based QoS parameter is used by the target base station for admission control.
  • the method further includes:
  • the core network control plane function entity receives a handover request acknowledgement message sent by the target base station, where the handover request acknowledgement message includes information of a PDU flow or RB that the target base station accepts successfully or fails;
  • the core network control plane function entity sends a handover command to the source base station.
  • the source base station sends a handover preparation request message to the core network control plane function entity (for example, 5G CN-C), and the handover preparation message may carry the PDU generated by the source base station.
  • the flow-to-RB mapping relationship to the target base station (target NG-NB) and the RB-based QoS parameter, the mapping relationship and the QoS parameters of the RB are transparent to the core network, and the core network control plane functional entity is transparently transmitted to the target base station.
  • the core network control plane function entity sends a handover request message to the target base station, where the handover request message carries the QoS parameter based on the PDU flow, and the information transmitted by the source base station to the target base station, and the target base station according to the QoS parameter based on the PDU flow or
  • the RB-based QoS parameters are subjected to admission control, and the successful and failed PDU flow information is returned to the core network control plane functional entity in the handover request acknowledgement message, and the failed RB information is sent to the target NG-NB (the information is transparent to the core network) .
  • the target eNB aggregates the PDU flows with the same QoS requirements, and generates a convergence mapping scheme of the PDU flow to the RB, and configuration parameters of the corresponding RB. If the source base station carries the mapping relationship between the PDU flow and the RB, the target base station can refer to the information to generate its own PDU flow to RB aggregation mapping scheme and corresponding configuration parameters.
  • the core network control plane function entity sends a handover command to the source base station, and may carry the PDU flow information that the target side fails to receive.
  • FIG. 8 a method for processing QoS parameters in a handover scenario is illustrated. The specific steps are as follows:
  • Step 801 The target base station receives a handover request message sent by a core network control plane function entity, where the handover request message includes: a QoS flow based QoS parameter and/or an RB-based QoS parameter;
  • Step 802 The target base station performs admission control according to the QoS parameter of the PDU flow or the QoS parameter based on the RB.
  • the method further includes:
  • the target base station generates, according to the QoS parameter based on the PDU flow, a convergence mapping relationship between the PDU flow of the target base station and the RB, and a configuration parameter of the corresponding RB.
  • the handover request message further includes: a mapping relationship of RBs of the PDU flow generated by the source base station.
  • the method further includes:
  • the target base station generates a convergence mapping relationship between the PDU flow of the target base station and the RB according to the mapping relationship of the RBs of the PDU flow generated by the source base station, and configuration parameters of the corresponding RB.
  • the method further includes:
  • the target base station sends a handover confirmation message to the core network control plane function entity, where the handover request acknowledgement message includes: information about the PDU flow or RB that the target base station accepts successfully or fails.
  • the source base station sends a handover preparation request message to the core network control plane function entity (for example, 5G CN-C), and the handover preparation message may carry the mapping of the PDU flow generated by the source base station to the RB.
  • the relationship to the target base station (target NG-NB) and the RB-based QoS parameters, the mapping relationship and the QoS parameters of the RB are transparent to the core network, and the core network control plane functional entity is transparently transmitted to the target base station.
  • the core network control plane function entity sends a handover request message to the target base station, where the handover request message carries the QoS parameter based on the PDU flow, and the information transmitted by the source base station to the target base station, and the target base station according to the QoS parameter based on the PDU flow or
  • the RB-based QoS parameters are subjected to admission control, and the successful and failed PDU flow information is returned to the core network control plane functional entity in the handover request acknowledgement message, and the failed RB information is sent to the target NG-NB (the information is transparent to the core network) .
  • the target eNB aggregates the PDU flows with the same QoS requirements, and generates a convergence mapping scheme of the PDU flow to the RB, and configuration parameters of the corresponding RB. If the source base station carries the mapping relationship between the PDU flow and the RB, the target base station can refer to the information to generate its own PDU flow to RB aggregation mapping scheme and corresponding configuration parameters.
  • the core network control plane function entity sends a handover command to the source base station, and may carry the PDU flow information that the target side fails to receive.
  • FIG. 9 a QoS processing flow based on PDU flow admission is shown.
  • a direct interface exists between the NG-NB and the NG-NB. The specific steps are as follows:
  • Step 901 The source NG-NB sends a handover request message to the target NG-NB, where the message carries the QoS parameter based on the PDU flow, and may also carry the mapping relationship between the PDU flow generated by the source base station and the RB.
  • Step 902 The target NG-NB performs admission control according to the QoS parameter of the flow, and returns the success and failure flow information in the handover request response message.
  • the target NG-NB aggregates flows with consistent QoS requirements, and generates a convergence mapping scheme of PDU flow to RBs and configuration parameters of corresponding RBs. If the source NG-NB carries the mapping relationship between the PDU flow and the RB, the target NG-NB can refer to the information to generate its own PDU flow to RB aggregation mapping scheme and corresponding configuration parameters.
  • Step 903 The target NG-NB sends a transmission path update message to the 5G CN-C, and carries the flow information that is successfully received.
  • Step 904 The 5G CN-C returns a transmission path update confirmation message to the target NG-NB, and may carry the flow information confirming the update.
  • FIG. 10 a QoS processing flow based on RB admission is shown.
  • a direct interface exists between the NG-NB and the NG-NB. The specific steps are as follows:
  • Step 1001 The source NG-NB sends a handover request message to the target NG-NB, where the message carries the RB-based QoS parameter, and the QoS parameter of the PDU flow may also carry the mapping relationship between the PDU flow generated by the source base station and the RB.
  • Step 1002 The target NG-NB performs admission control according to the QoS parameter of the RB, and returns successful and failed RB information in the handover request response message.
  • the target NG-NB aggregates the flows with the same QoS requirements according to the received flow QoS information, and generates a convergence mapping scheme of the PDU flow to the RB, and configuration parameters of the corresponding RB. If the source NG-NB carries the mapping relationship between the PDU flow and the RB, the target NG-NB can also refer to the information to generate its own PDU flow to RB aggregation mapping scheme and corresponding configuration parameters.
  • Step 1003 The target NG-NB sends a transmission path update message to the 5G CN-C, and carries the received flow information.
  • Step 1004 The 5G CN-C returns a transmission path update confirmation message to the target NG-NB, and may carry the flow information confirming the update.
  • FIG. 11 a QoS processing flow based on PDU flow admission is shown.
  • the NG-NB there is no direct interface between the NG-NB and the NG-NB.
  • the specific steps are as follows:
  • Step 1101 The source NG-NB sends a handover preparation request message to the 5G CN-C, where the message may carry the mapping relationship between the PDU flow and the RB generated by the source base station to the target NG-NB, the information is transparent to the core network, and the core network is transparently transmitted. Give the target NG-NB.
  • Step 1102 The 5G CN-C sends a handover request message to the target NG-NB, where the message carries the QoS parameter based on the PDU flow and the information transparently transmitted by the source NG-NB to the target NG-NB.
  • Step 1103 The target NG-NB performs admission control according to the QoS parameter of the flow, and switches.
  • the request confirmation message returns the success and failure flow information to the 5G CN-C.
  • the target NG-NB aggregates flows with consistent QoS requirements, and generates a convergence mapping scheme of PDU flow to RBs and configuration parameters of corresponding RBs. If the source base station carries the mapping relationship between the PDU flow and the RB, the target base station can refer to the information to generate its own PDU flow to RB aggregation mapping scheme and corresponding configuration parameters.
  • Step 1104 The 5G CN-C sends a handover command to the source NG-NB, and the message may carry the flow information of the destination side failure.
  • the QoS processing flow based on RB admission is shown.
  • the specific steps are as follows:
  • Step 1201 The source NG-NB sends a handover preparation request message to the 5G CN-C, where the message carries the RB-based QoS parameter, and may also carry the mapping relationship between the PDU flow and the RB generated by the source base station to the target NG-NB.
  • the core network is transparent, and the core network is transparently transmitted to the target NG-NB.
  • Step 1202 The 5G CN-C sends a handover request message to the target NG-NB, where the message carries the QoS parameter of the PDU flow and the information transparently transmitted by the source NG-NB to the target NG-NB.
  • Step 1203 The target NG-NB performs admission control according to the QoS parameter of the RB, and returns a flow parameter of the successful and failed admission to the 5G CN-C in the handover request response message, and the failed RB information is sent to the target NG-NB (this information Transparent to the core network).
  • the target NG-NB aggregates the flows with the same QoS requirements according to the received flow QoS information, and generates a convergence mapping scheme of the PDU flow to the RB, and configuration parameters of the corresponding RB. If the source NG-NB carries the mapping relationship between the PDU flow and the RB, the target NG-NB can also refer to the information to generate its own PDU flow to RB aggregation mapping scheme and corresponding configuration parameters.
  • Step 1204 The 5G CN-C sends a handover command to the source NG-NB, and the message may carry the failed RB information transparently transmitted by the target NG-NB to the source NG-NB.
  • a source base station is illustrated, the source base station including:
  • the first sending module 1301 is configured to send a handover request message to the target base station, where the handover request message includes: a QoS parameter based on the PDU flow and/or an RB-based QoS parameter;
  • the PDU flow based QoS parameter or the RB based QoS parameter is used for the The target base station performs admission control.
  • the handover request message further includes: a mapping relationship of RBs of the PDU flow generated by the source base station.
  • the source base station further includes:
  • the first receiving module is configured to receive a handover response message sent by the target base station, where the handover response message includes: information about a PDU flow or an RB that the target base station accepts successfully or fails.
  • the source base station may carry the PDU flow-based QoS parameter and/or the RB-based QoS parameter to the target base station in the handover request message, and the target base station is based on the QoS parameter of the PDU flow or based on
  • the QoS parameters of the RB are subjected to the admission control, and the successful and/or failed PDU flow information or RB information is returned in the handover request response, and the target base station may aggregate the PDU flows with the same QoS requirements according to the received PDU flow information, and The aggregation mapping relationship between the PDU flow and the RB is generated, and the configuration parameters of the corresponding RB are sent, and the target base station sends the received PDU flow information to the core network.
  • the source base station may also carry the mapping relationship between the PDU flow generated by the source base station and the RB in the handover request message, and the target base station may refer to the mapping relationship to generate a mapping relationship between the PDU flow and the RB, and corresponding Configuration parameters.
  • a target base station is illustrated, the target base station 1400 comprising:
  • the second receiving module 1401 is configured to receive a handover request message sent by the source base station, where the handover request message includes: a QoS parameter based on the PDU flow and/or an RB-based QoS parameter;
  • the first admission control module 1402 is configured to perform admission control according to the PDU flow based QoS parameter or the RB based QoS parameter.
  • the target base station further includes:
  • a first generating module configured to generate, according to the PDU flow-based QoS parameter, a convergence mapping relationship between the PDU flow of the target base station and the RB, and a configuration parameter of the corresponding RB.
  • the handover request message further includes: a mapping relationship of RBs of the PDU flow generated by the source base station;
  • the target base station further includes:
  • a second generating module configured to generate, according to a mapping relationship of the RBs of the PDU flow generated by the source base station, a convergence mapping relationship between the PDU flow of the target base station and the RB, and a configuration parameter of the corresponding RB.
  • the target base station further includes:
  • the second sending module is configured to send a handover request response message to the source base station, where the handover request response message includes: information about the PDU flow or RB that the target base station accepts successfully or fails.
  • the source base station may carry the PDU flow-based QoS parameter and/or the RB-based QoS parameter to the target base station in the handover request message, and the target base station is based on the QoS parameter of the PDU flow or based on
  • the QoS parameters of the RB are subjected to the admission control, and the successful and/or failed PDU flow information or RB information is returned in the handover request response, and the target base station may aggregate the PDU flows with the same QoS requirements according to the received PDU flow information, and The aggregation mapping relationship between the PDU flow and the RB is generated, and the configuration parameters of the corresponding RB are sent, and the target base station sends the received PDU flow information to the core network.
  • the source base station may also carry the mapping relationship between the PDU flow generated by the source base station and the RB in the handover request message, and the target base station may refer to the mapping relationship to generate a mapping relationship between the PDU flow and the RB, and corresponding Configuration parameters.
  • the core network control plane functional entity 1500 includes:
  • the third sending module 1501 is configured to send a handover request message to the target base station, where the handover request message includes: a QoS parameter based on the PDU flow and/or an RB-based QoS parameter;
  • the PDU flow based QoS parameter or the RB based QoS parameter is used by the target base station for admission control.
  • the core network control plane functional entity further includes:
  • a third receiving module configured to receive a handover request acknowledgement message sent by the target base station, where the handover request acknowledgement message includes information about a PDU flow or RB that the target base station accepts successfully or fails;
  • the fourth sending module is configured to send a handover command to the source base station.
  • the source base station sends a handover preparation request message to the core network control plane function entity (for example, 5G CN-C), and the handover preparation message may carry the PDU generated by the source base station.
  • the flow-to-RB mapping relationship to the target base station (target NG-NB) and the RB-based QoS parameter, the mapping relationship and the QoS parameters of the RB are transparent to the core network, and the core network control plane functional entity is transparently transmitted to the target base station.
  • the core network control plane function entity sends a handover request message to the target base station, where the handover request message carries the QoS parameter based on the PDU flow, and the information transmitted by the source base station to the target base station, and the target base station according to the QoS parameter based on the PDU flow or
  • the RB-based QoS parameters are subjected to admission control, and the successful and failed PDU flow information is returned to the core network control plane functional entity in the handover request acknowledgement message, and the failed RB information is sent to the target NG-NB (the information is transparent to the core network) .
  • the target eNB aggregates the PDU flows with the same QoS requirements, and generates a convergence mapping scheme of the PDU flow to the RB, and configuration parameters of the corresponding RB. If the source base station carries the mapping relationship between the PDU flow and the RB, the target base station can refer to the information to generate its own PDU flow to RB aggregation mapping scheme and corresponding configuration parameters.
  • the core network control plane function entity sends a handover command to the source base station, and may carry the PDU flow information that the target side fails to receive.
  • a target base station is illustrated, the target base station 1600 comprising:
  • the fourth receiving module 1601 is configured to receive a handover request message sent by a core network control plane function entity, where the handover request message includes: a PDU flow based QoS parameter and/or an RB based QoS parameter;
  • the second admission control module 1602 is configured to perform admission control according to the QoS parameter of the PDU flow or the RB-based QoS parameter.
  • the target base station further includes:
  • a third generating module configured to generate, according to the PDU flow-based QoS parameter, a convergence mapping relationship between the PDU flow of the target base station and the RB, and a configuration parameter of the corresponding RB.
  • the handover request message further includes: a mapping relationship of RBs of the PDU flow generated by the source base station.
  • the target base station further includes:
  • a fourth generation module configured to generate, according to a mapping relationship of RBs of the PDU flow generated by the source base station, a convergence mapping relationship between the PDU flow of the target base station and the RB, and a configuration parameter of the corresponding RB.
  • the target base station further includes:
  • a fifth sending module configured to send a handover confirmation message to the core network control plane function entity, where the handover request acknowledgement message includes: information that the target base station accepts a successful or failed PDU flow or RB.
  • the target base station further includes:
  • a sixth sending module configured to send a transmission path update message to the core network control plane function entity, and carry the information of the received PDU flow;
  • the fifth receiving module is configured to receive a transmission path update confirmation message sent by the core network control plane function entity.
  • the source base station sends a handover preparation request message to the core network control plane function entity (for example, 5G CN-C), and the handover preparation message may carry the mapping of the PDU flow generated by the source base station to the RB.
  • the relationship to the target base station (target NG-NB) and the RB-based QoS parameters, the mapping relationship and the QoS parameters of the RB are transparent to the core network, and the core network control plane functional entity is transparently transmitted to the target base station.
  • the core network control plane function entity sends a handover request message to the target base station, where the handover request message carries the QoS parameter based on the PDU flow, and the information transmitted by the source base station to the target base station, and the target base station according to the QoS parameter based on the PDU flow or
  • the RB-based QoS parameters are subjected to admission control, and the successful and failed PDU flow information is returned to the core network control plane functional entity in the handover request acknowledgement message, and the failed RB information is sent to the target NG-NB (the information is transparent to the core network) .
  • the target eNB aggregates the PDU flows with the same QoS requirements, and generates a convergence mapping scheme of the PDU flow to the RB, and configuration parameters of the corresponding RB. If the source base station carries the mapping relationship between the PDU flow and the RB, the target base station can refer to the information to generate its own PDU flow to RB aggregation mapping scheme and corresponding configuration parameters.
  • the core network control plane function entity sends a handover command to the source base station, and may carry the PDU flow information that the target side fails to receive.
  • system and “network” are used interchangeably herein.
  • B corresponding to A means that B is associated with A, and B can be determined from A.
  • determining B from A does not mean that B is only determined based on A, and that B can also be determined based on A and/or other information.
  • the disclosed method and apparatus may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may be physically included separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.
  • the above-described integrated unit implemented in the form of a software functional unit can be stored in a computer readable storage medium.
  • the above software functional unit is stored in a storage medium and includes a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network side device, etc.) to perform part of the steps of the transceiving method of the various embodiments of the present disclosure.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, and the program code can be stored. Medium.

Landscapes

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

Abstract

本公开文本实施例提供了一种切换场景下的QoS参数处理的方法及设备，在切换过程中，源基站可以在切换请求消息中携带基于PDU flow的QoS参数和/或基于RB的QoS参数给目标基站，由目标基站根据该PDU flow的QoS参数或者基于RB的QoS参数进行接纳控制，并且在切换请求响应中返回成功和/或失败的PDU flow信息或RB信息，目标基站可以根据接收到的PDU flow信息，将QoS要求一致的PDU flow进行汇聚，并生成PDU flow到RB的汇聚映射关系，以及相应的RB的配置参数，目标基站向核心网发送接纳的PDU flow信息，实现在切换场景下的QoS处理。

Description

切换场景下的QoS参数处理的方法及设备
相关申请的交叉引用
本申请主张在2016年8月12日在中国提交的中国专利申请No.201610663580.1的优先权，其全部内容通过引用包含于此。
技术领域
本公开文本涉及通信技术领域，尤其涉及一种切换场景下的QoS(Quality of Service，服务质量)参数处理的方法及设备。
背景技术
参见图1，图中示出了相关技术中的LTE(Long Term Evolution，长期演进)系统中承载模型，相关技术中的LTE系统中核心网控制面功能实体负责生成E-RAB(Evolved Radio Access Bearer，演进的无线接入承载)的QoS参数，由于空口RB(Radio Bearer，无线承载)与E-RAB是一一映射的关系，因此空口的RB的QoS参数直接采用核心网控制面功能实体生成的E-RAB QoS参数。
移动通信网络中的异构接入技术导致了核心网控制面功能实体中需要支持多种隧道协议来支持移动性和保障QoS，例如GTP(GPRS(General Packet Radio Service，通用分组无线服务)Tunneling Protocol，GPRS隧道协议)，PMIP(Proxy Mobile Internet Protocol，代理移动互联网协议)等。而在控制和转发分离的5G网络支持众多的隧道协议将导致复杂的控制逻辑和信令交互，从而影响系统的性能，因此，5G网络可考虑通用转发平面上QoS支持增强，比如简化转发协议，优化QoS调度策略，增强转发平面的数据包转发能力等。由于LTE网络的长期存在，未来5G网络中连接管理机制还需考虑兼容EPS(Evolved Packet System，演进的分组系统)的连接接入，连接管理可能仍需提供互操作管理功能来处理LTE网络中的隧道管理消息，并完成隧道管理过程。
未来5G核心网控制面功能实体没有承载(Bearer)的概念，核心网控制 面功能实体CN-C下发给NG-NB的QoS参数是以流(flow)为粒度配置的。另一方面由于接入网NG-NB仍然以RB为粒度进行QoS管理，因此接入网需要生成RB级别的QoS参数用于NG-NB与UE以及NG-NB与其他无线接入实体之间的交互过程。
现在尚处于5G初级研究阶段，目前公开的资料中并没有提出切换过程中基于新的QoS机制的处理方案。
发明内容
鉴于上述技术问题，本公开文本实施例提供一种切换场景下的QoS参数处理的方法及设备，解决切换场景下的QoS的处理。
依据本公开文本实施例的第一个方面，提供了一种切换场景下的QoS参数处理的方法，所述方法包括：
源基站向目标基站发送切换请求消息，所述切换请求消息包括：基于协议数据单元(Protocol Data Unit，PDU)flow的QoS参数和/或基于RB的QoS参数；
其中，所述基于PDU flow的QoS参数或基于RB的QoS参数用于所述目标基站进行接纳控制。
可选地，所述切换请求消息还包括：所述源基站生成的PDU flow的RB的映射关系。
可选地，所述方法还包括：
所述源基站接收所述目标基站发送的切换响应消息，所述切换响应消息包括：所述目标基站接纳成功或失败的PDU flow的信息或RB的信息。
依据本公开文本实施例的第二个方面，提供了一种切换场景下的QoS参数处理的方法，所述方法包括：
目标基站接收源基站发送的切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
所述目标基站根据所述基于PDU flow的QoS参数或者基于RB的QoS参数进行接纳控制。
可选地，所述方法还包括：
所述目标基站根据基于PDU flow的QoS参数，生成所述目标基站的PDU flow到RB的汇聚映射关系，以及相应RB的配置参数。
可选地，所述切换请求消息还包括：所述源基站生成的PDU flow的RB的映射关系；
所述方法还包括：
所述目标基站根据所述源基站生成的PDU flow的RB的映射关系，生成所述目标基站的PDU flow到RB的汇聚映射关系，以及相应RB的配置参数。
可选地，所述方法还包括：
所述目标基站向所述源基站发送切换请求响应消息，所述切换请求响应消息包括：所述目标基站接纳成功或失败的PDU flow的信息或RB的信息。
可选地，所述方法还包括：
所述目标基站向核心网控制面功能实体发送传输路径更新消息，携带接纳后的PDU flow的信息；
所述目标基站接收所述核心网控制面功能实体发送的传输路径更新确认消息。
依据本公开文本实施例的第三个方面，提供了一种切换场景下的QoS参数处理的方法，所述方法包括：
核心网控制面功能实体向目标基站发送切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
其中，所述基于PDU flow的QoS参数或基于RB的QoS参数用于所述目标基站进行接纳控制。
可选地，所述方法还包括：
所述核心网控制面功能实体接收所述目标基站发送的切换请求确认消息，所述切换请求确认消息包括所述目标基站接纳成功或失败的PDU flow或RB的信息；
所述核心网控制面功能实体向源基站发送切换命令。
依据本公开文本实施例的第四个方面，还提供了一种切换场景下的QoS参数处理的方法，所述方法包括：
目标基站接收核心网控制面功能实体发送的切换请求消息，所述切换请 求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
所述目标基站根据所述PDU flow的QoS参数或基于RB的QoS参数进行接纳控制。
可选地，所述方法还包括：
所述目标基站根据基于PDU flow的QoS参数，生成所述目标基站的PDU flow到RB的汇聚映射关系，以及相应RB的配置参数。
可选地，所述切换请求消息还包括：源基站生成的PDU flow的RB的映射关系；
所述方法还包括：
所述目标基站根据所述源基站生成的PDU flow的RB的映射关系，生成所述目标基站的PDU flow到RB的汇聚映射关系，以及相应RB的配置参数。
可选地，所述方法还包括：
所述目标基站向所述核心网控制面功能实体发送切换确认消息，所述切换请求确认消息包括：所述目标基站接纳成功或失败的PDU flow或RB的信息。
依据本公开文本实施例的第五个方面，还提供了一种源基站，包括：
第一发送模块，用于向目标基站发送切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
其中，所述基于PDU flow的QoS参数或基于RB的QoS参数用于所述目标基站进行接纳控制。
可选地，所述切换请求消息还包括：所述源基站生成的PDU flow的RB的映射关系。
可选地，所述源基站还包括：
第一接收模块，用于接收所述目标基站发送的切换响应消息，所述切换响应消息包括：所述目标基站接纳成功或失败的PDU flow或RB的信息。
依据本公开文本实施例的第六个方面，还提供了一种目标基站，所述目标基站包括：
第二接收模块，用于接收源基站发送的切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
第一接纳控制模块，用于根据所述基于PDU flow的QoS参数或者基于RB的QoS参数进行接纳控制。
可选地，所述目标基站还包括：
第一生成模块，用于根据基于PDU flow的QoS参数，生成所述目标基站的PDU flow到RB的汇聚映射关系，以及相应RB的配置参数。
可选地，所述切换请求消息还包括：所述源基站生成的PDU flow的RB的映射关系；
所述目标基站还包括：
第二生成模块，用于根据所述源基站生成的PDU flow的RB的映射关系，生成所述目标基站的PDU flow到RB的汇聚映射关系，以及相应RB的配置参数。
可选地，所述目标基站还包括：
第二发送模块，用于向所述源基站发送切换请求响应消息，所述切换请求响应消息包括：所述目标基站接纳成功或失败的PDU flow或RB的信息。
可选地，所述目标基站还包括：
第六发送模块，用于向核心网控制面功能实体发送传输路径更新消息，携带接纳后的PDU flow的信息；
第五接收模块，用于接收所述核心网控制面功能实体发送的传输路径更新确认消息。
依据本公开文本实施例的第七个方面，还提供了一种核心网控制面功能实体，包括：
第三发送模块，用于向目标基站发送切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
其中，所述基于PDU flow的QoS参数或基于RB的QoS参数用于所述目标基站进行接纳控制。
可选地，所述核心网控制面功能实体还包括：
第三接收模块，用于接收所述目标基站发送的切换请求确认消息，所述切换请求确认消息包括所述目标基站接纳成功或失败的PDU flow的信息或RB的信息；
第四发送模块，用于向源基站发送切换命令。
依据本公开文本实施例的第八个方面，还提供了一种目标基站，包括：
第四接收模块，用于接收核心网控制面功能实体发送的切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
第二接纳控制模块，用于根据所述PDU flow的QoS参数或基于RB的QoS参数进行接纳控制。
可选地，所述目标基站还包括：
第三生成模块，用于根据基于PDU flow的QoS参数，生成所述目标基站的PDU flow到RB的汇聚映射关系，以及相应RB的配置参数。
可选地，所述切换请求消息还包括：源基站生成的PDU flow的RB的映射关系；
所述目标基站还包括：
第四生成模块，用于根据所述源基站生成的PDU flow的RB的映射关系，生成所述目标基站的PDU flow到RB的汇聚映射关系，以及相应RB的配置参数。
可选地，所述目标基站还包括：
第五发送模块，用于向所述核心网控制面功能实体发送切换确认消息，所述切换请求确认消息包括：所述目标基站接纳成功或失败的PDU flow或RB的信息。
依据本公开文本实施例的第九个方面，还提供了一种源基站，包括：处理器、存储器和收发机，其中：
所述处理器，用于读取存储器中的程序，执行下列过程：
通过所述收发机向目标基站发送切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
其中，所述基于PDU flow的QoS参数或基于RB的QoS参数用于所述目标基站进行接纳控制，
所述收发机用于接收和发送数据，
所述存储器能够存储所述处理器在执行操作时所使用的数据。
依据本公开文本实施例的第十个方面，还提供了一种目标基站，包括：处理器、存储器和收发机，其中：
所述处理器，用于读取存储器中的程序，执行下列过程：
通过所述收发机接收源基站发送的切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
根据所述基于PDU flow的QoS参数或者基于RB的QoS参数进行接纳控制，
所述收发机用于接收和发送数据，
所述存储器能够存储所述处理器在执行操作时所使用的数据。
依据本公开文本实施例的第十一个方面，还提供了一种核心网控制面功能实体，包括：处理器、存储器和收发机，其中：
所述处理器，用于读取存储器中的程序，执行下列过程：
通过所述收发机向目标基站发送切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
其中，所述基于PDU flow的QoS参数或基于RB的QoS参数用于所述目标基站进行接纳控制，
所述收发机用于接收和发送数据，
所述存储器能够存储所述处理器在执行操作时所使用的数据。
依据本公开文本实施例的第十二个方面，还提供了一种目标基站，包括：处理器、存储器和收发机，其中：
所述处理器，用于读取存储器中的程序，执行下列过程：
通过所述收发机接收核心网控制面功能实体发送的切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
根据所述PDU flow的QoS参数或基于RB的QoS参数进行接纳控制，
所述收发机用于接收和发送数据，
所述存储器能够存储所述处理器在执行操作时所使用的数据。
上述技术方案中的一个技术方案具有如下优点或有益效果：在切换过程 中，源基站可以在切换请求消息中携带基于PDU flow的QoS参数和/或基于RB的QoS参数给目标基站，由目标基站根据该PDU flow的QoS参数或者基于RB的QoS参数进行接纳控制，并且在切换请求响应中返回成功和/或失败的PDU flow信息或RB信息，目标基站可以根据接收到的PDU flow信息，将QoS要求一致的PDU flow进行汇聚，并生成PDU flow到RB的汇聚映射关系，以及相应的RB的配置参数，目标基站向核心网发送接纳的PDU flow信息，实现在切换场景下的QoS处理。
附图说明
为了更清楚地说明本公开文本实施例的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请中记载的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。以下附图并未刻意按实际尺寸等比例缩放绘制，重点在于示出本申请的主旨。
图1为相关技术中的LTE系统中承载模型的示意图；
图2为典型的LTE架构的示意图；
图3为未来移动通信的架构的示意图；
图4为5G网络架构的示意图；
图5为本公开文本一些实施例中切换场景下的QoS参数处理的方法的流程图；
图6为本公开文本一些实施例中切换场景下的QoS参数处理的方法的另一流程图；
图7为本公开文本一些实施例中切换场景下的QoS参数处理的方法的又一流程图；
图8为本公开文本一些实施例中切换场景下的QoS参数处理的方法的又一流程图；
图9为本公开文本一些实施例中基于PDU flow接纳的QoS处理流程的示意图；
图10为本公开文本一些实施例中基于RB接纳的QoS处理流程的示意图；
图11为本公开文本一些实施例中基于PDU flow接纳的QoS处理流程的另一示意图；
图12为本公开文本一些实施例中基于RB接纳的QoS处理流程的另一示意图；
图13为本公开文本一些实施例中源基站的示意图；
图14为本公开文本一些实施例中目标基站的示意图；
图15为本公开文本一些实施例中核心网控制面功能实体的示意图；
图16为本公开文本一些实施例中目标基站的另一示意图。
具体实施方式
下面将参照附图更详细地描述本公开的示例性实施例。虽然附图中显示了本公开的示例性实施例，然而应当理解，可以以各种形式实现本公开而不应被这里阐述的实施例所限制。相反，提供这些实施例是为了能够更透彻地理解本公开，并且能够将本公开的范围完整的传达给本领域的技术人员。
本领域技术人员知道，本公开文本的实施方式可以实现为一种系统、装置、设备、方法或计算机程序产品。因此，本公开文本的实施例可以具体实现为以下形式：完全的硬件、完全的软件(包括固件、驻留软件、微代码等)，或者硬件和软件结合的形式。
本公开文本的实施方式可以用于不同的网络部署结构，为了描述方便，先介绍两种未来移动通信可能采用的网络部署结构。
部署结构一：基站和终端
参见图2，图中示出了典型的LTE架构。eNB(Evolved Node B，演进型基站)下有多个小区(cell)，连接态下终端(UE)与小区进行空口数据收发。
部署结构二：网络侧节点和用户侧节点，其中，网络侧节点分为中央单元(CU，Central Unit)和分布式单元(DU，Distributed Unit)，用户侧节点为终端。
参见图3，图中示出了未来移动通信的架构，网络侧节点包括中央单元和分布式节点，一个中央单元控制一定区域内部署的多个分布式单元，该多个分布式单元通过TRP(Transmission Reception Point，收发点)与终端进行空 口传输，一个或多个TRP可以同时为终端服务，进行数据传输。
本公开文本适用于上述两种RAN(Radio Access Network，无线接入网)架构。后续为统一描述，网络侧无线信令和数据收发节点不管是部署结构一中的eNB或部署结构二中的CU/DU(具体收发点为TRP)，都统称为基站(NG-NB)。
参见图4，图中示出了5G网络架构，网络架构中包括三个逻辑实体分别是位于核心网控制面功能实体的CN-C(Core Network-Control，核心网控制面功能实体控制面功能实体)，和CN-U(Core Network-User，核心网控制面功能实体用户面功能实体)；以及位于接入网的NG-NB(Next Generation-Node B，下一代基站)和eLTE eNB(演进LTE的基站)。其中CN-C与NG-NB建立S1*-C接口用于控制面信令的传输；CN-U与NG-NB建立S1*-U用于用户面数据传输。无线接入网NG-NB之间建立X2*接口，X2*接头同时支持控制面(例如X2*-C)和用户面功能(例如X2*-U)。
其中S1*-C上可建立以UE为粒度的控制面连接(其中每个UE对应的控制面连接可使用S1*-AP ID进行标识)，在S1*-U上建立以PDU会话(PDU session)为粒度的用户面连接(或者称为用户面隧道)，一个UE仅能同时保持一个与CN-C之间的S1*-C连接，但是可以同时建立多个与CN-U在S1*-U接口上的PDU会话为粒度的用户面连接(或者称为用户面隧道)。在无线接入网可以有一个或多个NG-NB同时为UE提供服务。
在本公开文本一些实施例中，参见图5，图中示出了一种切换场景下的QoS参数处理的方法，具体步骤如下：
步骤501、源基站向目标基站发送切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
其中，所述基于PDU flow的QoS参数或基于RB的QoS参数用于所述目标基站进行接纳控制。
在本实施例中，源基站和目标基站可以对应于图2中两个不同的eNB，或者源基站和目标基站可以对应于图3中两个不同的TRP。
在本实施例中，可选地，所述切换请求消息还包括：所述源基站生成的PDU flow的RB的映射关系。
在本实施例中，可选地，所述方法还包括：
所述源基站接收所述目标基站发送的切换响应消息，所述切换响应消息包括：所述目标基站接纳成功或失败的PDU flow或RB的信息。
在本实施例中，在切换过程中，源基站可以在切换请求消息中携带基于PDU flow的QoS参数和/或基于RB的QoS参数给目标基站，由目标基站根据该PDU flow的QoS参数或者基于RB的QoS参数进行接纳控制，并且在切换请求响应中返回成功和/或失败的PDU flow信息或RB信息，目标基站可以根据接收到的PDU flow信息，将QoS要求一致的PDU flow进行汇聚，并生成PDU flow到RB的汇聚映射关系，以及相应的RB的配置参数，目标基站向核心网发送接纳的PDU flow信息。
需要说明的是，源基站也可以在切换请求消息中，携带源基站生成的PDU flow到RB的映射关系，目标基站可以参考该映射关系，生成自己的PDU flow到RB的映射关系，以及相应的配置参数。
在本公开文本一些实施例中，参见图6，图中示出了一种切换场景下的QoS参数处理的方法，具体步骤如下：
步骤601、目标基站接收源基站发送的切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
步骤602、目标基站根据所述基于PDU flow的QoS参数或者基于RB的QoS参数进行接纳控制。
在本实施例中，可选地，所述方法还包括：
所述目标基站根据基于PDU flow的QoS参数，生成所述目标基站的PDU flow到RB的汇聚映射关系，以及相应RB的配置参数。
在本实施例中，可选地，所述切换请求消息还包括：所述源基站生成的PDU flow的RB的映射关系；
所述方法还包括：
所述目标基站根据所述源基站生成的PDU flow的RB的映射关系，生成所述目标基站的PDU flow到RB的汇聚映射关系，以及相应RB的配置参数。
在本实施例中，可选地，所述方法还包括：
所述目标基站向所述源基站发送切换请求响应消息，所述切换请求响应 消息包括：所述目标基站接纳成功或失败的PDU flow或RB的信息。
在本实施例中，可选地，所述方法还包括：
所述目标基站向核心网控制面功能实体发送传输路径更新消息，携带接纳后的PDU flow的信息；
所述目标基站接收所述核心网控制面功能实体发送的传输路径更新确认消息。
在本实施例中，在切换过程中，源基站可以在切换请求消息中携带基于PDU flow的QoS参数和/或基于RB的QoS参数给目标基站，由目标基站根据该PDU flow的QoS参数或者基于RB的QoS参数进行接纳控制，并且在切换请求响应中返回成功和/或失败的PDU flow信息或RB信息，目标基站可以根据接收到的PDU flow信息，将QoS要求一致的PDU flow进行汇聚，并生成PDU flow到RB的汇聚映射关系，以及相应的RB的配置参数，目标基站向核心网发送接纳的PDU flow信息。
需要说明的是，源基站也可以在切换请求消息中，携带源基站生成的PDU flow到RB的映射关系，目标基站可以参考该映射关系，生成自己的PDU flow到RB的映射关系，以及相应的配置参数。
在本公开文本一些实施例中，参见图7，图中示出了一种切换场景下的QoS参数处理的方法，具体步骤如下：
步骤701、核心网控制面功能实体向目标基站发送切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
其中，所述基于PDU flow的QoS参数或基于RB的QoS参数用于所述目标基站进行接纳控制。
在本实施例中，可选地，所述方法还包括：
所述核心网控制面功能实体接收所述目标基站发送的切换请求确认消息，所述切换请求确认消息包括所述目标基站接纳成功或失败的PDU flow或RB的信息；
所述核心网控制面功能实体向源基站发送切换命令。
在本实施例中，源基站(源NG-NB)向核心网控制面功能实体(例如5G CN-C)发送切换准备请求消息，该切换准备消息可以携带源基站生成的PDU  flow到RB的映射关系给目标基站(目标NG-NB)，以及基于RB的QoS参数，该映射关系和RB的QoS参数对核心网透明，核心网控制面功能实体透传给目标基站。然后，核心网控制面功能实体向目标基站发送切换请求消息，该切换请求消息中携带基于PDU flow的QoS参数，以及源基站透传给目标基站的信息，目标基站根据基于PDU flow的QoS参数或者基于RB的QoS参数进行接纳控制，并在切换请求确认消息中向核心网控制面功能实体返回成功和失败的PDU flow信息，以及失败的RB信息给目标NG-NB(该信息对核心网透明)。目标基站将QoS要求一致的PDU flow进行汇聚，并生成PDU flow到RB的汇聚映射方案，以及相应RB的配置参数。如果源基站携带了PDU flow到RB的映射关系，目标基站可以参考该信息生成自己的PDU flow到RB的汇聚映射方案，及相应的配置参数。核心网控制面功能实体向源基站发送切换命令，可以携带目标侧接纳失败的PDU flow信息。
在本公开文本一些实施例中，参见图8，图中示出了一种切换场景下的QoS参数处理的方法，具体步骤如下：
步骤801、目标基站接收核心网控制面功能实体发送的切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
步骤802、目标基站根据所述PDU flow的QoS参数或基于RB的QoS参数进行接纳控制。
在本实施例中，可选地，所述方法还包括：
所述目标基站根据基于PDU flow的QoS参数，生成所述目标基站的PDU flow到RB的汇聚映射关系，以及相应RB的配置参数。
在本实施例中，可选地，
所述切换请求消息还包括：所述源基站生成的PDU flow的RB的映射关系。
所述方法还包括：
所述目标基站根据所述源基站生成的PDU flow的RB的映射关系，生成所述目标基站的PDU flow到RB的汇聚映射关系，以及相应RB的配置参数。
在本实施例中，可选地，所述方法还包括：
所述目标基站向所述核心网控制面功能实体发送切换确认消息，所述切换请求确认消息包括：所述目标基站接纳成功或失败的PDU flow或RB的信息。
在本实施例中，源基站(源NG-NB)向核心网控制面功能实体(例如5G CN-C)发送切换准备请求消息，该切换准备消息可以携带源基站生成的PDU flow到RB的映射关系给目标基站(目标NG-NB)，以及基于RB的QoS参数，该映射关系和RB的QoS参数对核心网透明，核心网控制面功能实体透传给目标基站。然后，核心网控制面功能实体向目标基站发送切换请求消息，该切换请求消息中携带基于PDU flow的QoS参数，以及源基站透传给目标基站的信息，目标基站根据基于PDU flow的QoS参数或者基于RB的QoS参数进行接纳控制，并在切换请求确认消息中向核心网控制面功能实体返回成功和失败的PDU flow信息，以及失败的RB信息给目标NG-NB(该信息对核心网透明)。目标基站将QoS要求一致的PDU flow进行汇聚，并生成PDU flow到RB的汇聚映射方案，以及相应RB的配置参数。如果源基站携带了PDU flow到RB的映射关系，目标基站可以参考该信息生成自己的PDU flow到RB的汇聚映射方案，及相应的配置参数。核心网控制面功能实体向源基站发送切换命令，可以携带目标侧接纳失败的PDU flow信息。
在本公开文本一些实施例中，参见图9，图中示出了基于PDU flow接纳的QoS处理流程，在本实施例中，NG-NB和NG-NB之间存在直接接口，具体步骤如下：
步骤901：源NG-NB向目标NG-NB发送切换请求消息，消息中携带基于PDU flow的QoS参数，也可以携带源基站生成的PDU flow到RB的映射关系。
步骤902：目标NG-NB根据flow的QoS参数进行接纳控制，并在切换请求响应消息中返回成功和失败的flow信息。目标NG-NB将QoS要求一致的flow进行汇聚，并生成PDU flow到RB的汇聚映射方案，以及相应RB的配置参数。如果源NG-NB携带了PDU flow到RB的映射关系，目标NG-NB可以参考该信息生成自己的PDU flow到RB的汇聚映射方案及相应的配置参数。
步骤903：目标NG-NB向5G CN-C发送传输路径更新消息，携带接纳成功的flow信息。
步骤904：5G CN-C向目标NG-NB返回传输路径更新确认消息，可以携带确认更新的flow信息。
在本公开文本一些实施例中，参见图10，图中示出了基于RB接纳的QoS处理流程，在本实施例中，NG-NB和NG-NB之间存在直接接口，具体步骤如下：
步骤1001：源NG-NB向目标NG-NB发送切换请求消息，消息中携带基于RB的QoS参数，PDU flow的QoS参数，也可以携带源基站生成的PDU flow到RB的映射关系。
步骤1002：目标NG-NB根据RB的QoS参数进行接纳控制，并在切换请求响应消息中返回成功和失败的RB信息。目标NG-NB根据接收到的flowQoS信息，将QoS要求一致的flow进行汇聚，并生成PDU flow到RB的汇聚映射方案，以及相应RB的配置参数。如果源NG-NB携带了PDU flow到RB的映射关系，目标NG-NB也可以参考该信息生成自己的PDU flow到RB的汇聚映射方案，及相应的配置参数。
步骤1003：目标NG-NB向5G CN-C发送传输路径更新消息，携带接纳后的flow信息。
步骤1004：5G CN-C向目标NG-NB返回传输路径更新确认消息，可以携带确认更新的flow信息。
在本公开文本一些实施例中，参见图11，图中示出了基于PDU flow接纳的QoS处理流程，在本实施例中，NG-NB和NG-NB之间没有直接接口，具体步骤如下：
步骤1101：源NG-NB向5G CN-C发送切换准备请求消息，消息中可以携带源基站生成的PDU flow到RB的映射关系给目标NG-NB，该信息对核心网透明，核心网透传给目标NG-NB。
步骤1102：5G CN-C向目标NG-NB发送切换请求消息，消息中携带基于PDU flow的QoS参数，以及源NG-NB透传给目标NG-NB的信息。
步骤1103：目标NG-NB根据flow的QoS参数进行接纳控制，并在切换 请求确认消息中给5G CN-C返回成功和失败的flow信息。目标NG-NB将QoS要求一致的flow进行汇聚，并生成PDU flow到RB的汇聚映射方案，以及相应RB的配置参数。如果源基站携带了PDU flow到RB的映射关系，目标基站可以参考该信息生成自己的PDU flow到RB的汇聚映射方案，及相应的配置参数。
步骤1104：5G CN-C向源NG-NB发送切换命令，消息可以携带目标侧接纳失败的flow信息。
在本公开文本一些实施例中，参见图12，图中示出了基于RB接纳的QoS处理流程，在本实施例中，NG-NB和NG-NB之间没有直接接口，具体步骤如下：
步骤1201：源NG-NB向5G CN-C发送切换准备请求消息，消息中携带基于RB的QoS参数，也可以携带源基站生成的PDU flow到RB的映射关系给目标NG-NB，这些信息对核心网透明，核心网透传给目标NG-NB。
步骤1202：5G CN-C向目标NG-NB发送切换请求消息，消息中携带PDU flow的QoS参数，以及源NG-NB透传给目标NG-NB的信息。
步骤1203：目标NG-NB根据RB的QoS参数进行接纳控制，并在切换请求响应消息中给5G CN-C返回接纳成功和失败的flow参数，以及失败的RB信息给目标NG-NB(该信息对核心网透明)。目标NG-NB根据接收到的flow QoS信息，将QoS要求一致的flow进行汇聚，并生成PDU flow到RB的汇聚映射方案，以及相应RB的配置参数。如果源NG-NB携带了PDU flow到RB的映射关系，目标NG-NB也可以参考该信息生成自己的PDU flow到RB的汇聚映射方案，及相应的配置参数。
步骤1204：5G CN-C向源NG-NB发送切换命令，消息可以携带目标NG-NB给源NG-NB透明传输的失败RB信息。
在本公开文本一些实施例中，参见图13，图中示出了一种源基站，该源基站包括：
第一发送模块1301，用于向目标基站发送切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
其中，所述基于PDU flow的QoS参数或基于RB的QoS参数用于所述 目标基站进行接纳控制。
在本实施例中，可选地，所述切换请求消息还包括：所述源基站生成的PDU flow的RB的映射关系。
在本实施例中，可选地，所述源基站还包括：
第一接收模块，用于接收所述目标基站发送的切换响应消息，所述切换响应消息包括：所述目标基站接纳成功或失败的PDU flow或RB的信息。
在本实施例中，在切换过程中，源基站可以在切换请求消息中携带基于PDU flow的QoS参数和/或基于RB的QoS参数给目标基站，由目标基站根据该PDU flow的QoS参数或者基于RB的QoS参数进行接纳控制，并且在切换请求响应中返回成功和/或失败的PDU flow信息或RB信息，目标基站可以根据接收到的PDU flow信息，将QoS要求一致的PDU flow进行汇聚，并生成PDU flow到RB的汇聚映射关系，以及相应的RB的配置参数，目标基站向核心网发送接纳的PDU flow信息。
需要说明的是，源基站也可以在切换请求消息中，携带源基站生成的PDU flow到RB的映射关系，目标基站可以参考该映射关系，生成自己的PDU flow到RB的映射关系，以及相应的配置参数。
在本公开文本一些实施例中，参见图14，图中示出了一种目标基站，所述目标基站1400包括：
第二接收模块1401，用于接收源基站发送的切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
第一接纳控制模块1402，用于根据所述基于PDU flow的QoS参数或者基于RB的QoS参数进行接纳控制。
在本实施例中，可选地，所述目标基站还包括：
第一生成模块，用于根据基于PDU flow的QoS参数，生成所述目标基站的PDU flow到RB的汇聚映射关系，以及相应RB的配置参数。
在本实施例中，可选地，
所述切换请求消息还包括：所述源基站生成的PDU flow的RB的映射关系；
所述目标基站还包括：
第二生成模块，用于根据所述源基站生成的PDU flow的RB的映射关系，生成所述目标基站的PDU flow到RB的汇聚映射关系，以及相应RB的配置参数。
在本实施例中，可选地，所述目标基站还包括：
第二发送模块，用于向所述源基站发送切换请求响应消息，所述切换请求响应消息包括：所述目标基站接纳成功或失败的PDU flow或RB的信息。
在本实施例中，在切换过程中，源基站可以在切换请求消息中携带基于PDU flow的QoS参数和/或基于RB的QoS参数给目标基站，由目标基站根据该PDU flow的QoS参数或者基于RB的QoS参数进行接纳控制，并且在切换请求响应中返回成功和/或失败的PDU flow信息或RB信息，目标基站可以根据接收到的PDU flow信息，将QoS要求一致的PDU flow进行汇聚，并生成PDU flow到RB的汇聚映射关系，以及相应的RB的配置参数，目标基站向核心网发送接纳的PDU flow信息。
需要说明的是，源基站也可以在切换请求消息中，携带源基站生成的PDU flow到RB的映射关系，目标基站可以参考该映射关系，生成自己的PDU flow到RB的映射关系，以及相应的配置参数。
在本公开文本一些实施例中，参见图15，图中示出了一种核心网控制面功能实体，核心网控制面功能实体1500包括：
第三发送模块1501，用于向目标基站发送切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
其中，所述基于PDU flow的QoS参数或基于RB的QoS参数用于所述目标基站进行接纳控制。
在本实施例中，可选地，所述核心网控制面功能实体还包括：
第三接收模块，用于接收所述目标基站发送的切换请求确认消息，所述切换请求确认消息包括所述目标基站接纳成功或失败的PDU flow或RB的信息；
第四发送模块，用于向源基站发送切换命令。
在本实施例中，源基站(源NG-NB)向核心网控制面功能实体(例如5G CN-C)发送切换准备请求消息，该切换准备消息可以携带源基站生成的PDU  flow到RB的映射关系给目标基站(目标NG-NB)，以及基于RB的QoS参数，该映射关系和RB的QoS参数对核心网透明，核心网控制面功能实体透传给目标基站。然后，核心网控制面功能实体向目标基站发送切换请求消息，该切换请求消息中携带基于PDU flow的QoS参数，以及源基站透传给目标基站的信息，目标基站根据基于PDU flow的QoS参数或者基于RB的QoS参数进行接纳控制，并在切换请求确认消息中向核心网控制面功能实体返回成功和失败的PDU flow信息，以及失败的RB信息给目标NG-NB(该信息对核心网透明)。目标基站将QoS要求一致的PDU flow进行汇聚，并生成PDU flow到RB的汇聚映射方案，以及相应RB的配置参数。如果源基站携带了PDU flow到RB的映射关系，目标基站可以参考该信息生成自己的PDU flow到RB的汇聚映射方案，及相应的配置参数。核心网控制面功能实体向源基站发送切换命令，可以携带目标侧接纳失败的PDU flow信息。
在本公开文本一些实施例中，参见图16，图中示出了一种目标基站，该目标基站1600包括：
第四接收模块1601，用于接收核心网控制面功能实体发送的切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
第二接纳控制模块1602，用于根据所述PDU flow的QoS参数或基于RB的QoS参数进行接纳控制。
在本实施例中，可选地，所述目标基站还包括：
第三生成模块，用于根据基于PDU flow的QoS参数，生成所述目标基站的PDU flow到RB的汇聚映射关系，以及相应RB的配置参数。
在本实施例中，可选地，
所述切换请求消息还包括：所述源基站生成的PDU flow的RB的映射关系。
所述目标基站还包括：
第四生成模块，用于根据所述源基站生成的PDU flow的RB的映射关系，生成所述目标基站的PDU flow到RB的汇聚映射关系，以及相应RB的配置参数。
在本实施例中，可选地，所述目标基站还包括：
第五发送模块，用于向所述核心网控制面功能实体发送切换确认消息，所述切换请求确认消息包括：所述目标基站接纳成功或失败的PDU flow或RB的信息。
在本实施例中，可选地，所述目标基站还包括：
第六发送模块，用于向核心网控制面功能实体发送传输路径更新消息，携带接纳后的PDU flow的信息；
第五接收模块，用于接收所述核心网控制面功能实体发送的传输路径更新确认消息。
在本实施例中，源基站(源NG-NB)向核心网控制面功能实体(例如5G CN-C)发送切换准备请求消息，该切换准备消息可以携带源基站生成的PDU flow到RB的映射关系给目标基站(目标NG-NB)，以及基于RB的QoS参数，该映射关系和RB的QoS参数对核心网透明，核心网控制面功能实体透传给目标基站。然后，核心网控制面功能实体向目标基站发送切换请求消息，该切换请求消息中携带基于PDU flow的QoS参数，以及源基站透传给目标基站的信息，目标基站根据基于PDU flow的QoS参数或者基于RB的QoS参数进行接纳控制，并在切换请求确认消息中向核心网控制面功能实体返回成功和失败的PDU flow信息，以及失败的RB信息给目标NG-NB(该信息对核心网透明)。目标基站将QoS要求一致的PDU flow进行汇聚，并生成PDU flow到RB的汇聚映射方案，以及相应RB的配置参数。如果源基站携带了PDU flow到RB的映射关系，目标基站可以参考该信息生成自己的PDU flow到RB的汇聚映射方案，及相应的配置参数。核心网控制面功能实体向源基站发送切换命令，可以携带目标侧接纳失败的PDU flow信息。
应理解，说明书通篇中提到的“一个实施例”或“一实施例”意味着与实施例有关的特定特征、结构或特性包括在本公开文本的至少一个实施例中。因此，在整个说明书各处出现的“在一个实施例中”或“在一实施例中”未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。
在本公开文本的各种实施例中，应理解，上述各过程的序号的大小并不 意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本公开文本实施例的实施过程构成任何限定。
另外，本文中术语“系统”和“网络”在本文中常可互换使用。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
在本申请所提供的实施例中，应理解，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
在本申请所提供的几个实施例中，应该理解到，所揭露方法和装置，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
另外，在本公开文本各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理包括，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
上述以软件功能单元的形式实现的集成的单元，可以存储在一个计算机可读取存储介质中。上述软件功能单元存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络侧设备等)执行本公开文本各个实施例所述收发方法的部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述的是本公开文本的可选实施方式，应当指出对于本技术领域的 普通人员来说，在不脱离本公开文本所述的原理前提下还可以做出若干改进和润饰，这些改进和润饰也在本公开文本的保护范围内。

Claims (32)

  1. 一种切换场景下的服务质量(Quality of Service，QoS)参数处理的方法，包括：
    源基站向目标基站发送切换请求消息，所述切换请求消息包括：基于协议数据单元(Protocol Data Unit，PDU)流(flow)的QoS参数和/或基于无线承载(Radio Bearer，RB)的QoS参数；
    其中，所述基于PDU flow的QoS参数或基于RB的QoS参数用于所述目标基站进行接纳控制。
  2. 根据权利要求1所述的方法，其中，所述切换请求消息还包括：所述源基站生成的PDU flow的RB的映射关系。
  3. 根据权利要求1所述的方法，还包括：
    所述源基站接收所述目标基站发送的切换响应消息，所述切换响应消息包括：所述目标基站接纳成功或失败的PDU flow的信息或RB的信息。
  4. 一种切换场景下的QoS参数处理的方法，包括：
    目标基站接收源基站发送的切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
    所述目标基站根据所述基于PDU flow的QoS参数或者基于RB的QoS参数进行接纳控制。
  5. 根据权利要求4所述的方法，还包括：
    所述目标基站根据基于PDU flow的QoS参数，生成所述目标基站的PDU flow到RB的汇聚映射关系，以及相应RB的配置参数。
  6. 根据权利要求4所述的方法，其中，
    所述切换请求消息还包括：所述源基站生成的PDU flow的RB的映射关系；
    所述方法还包括：
    所述目标基站根据所述源基站生成的PDU flow的RB的映射关系，生成所述目标基站的PDU flow到RB的汇聚映射关系，以及相应RB的配置参数。
  7. 根据权利要求4所述的方法，还包括：
    所述目标基站向所述源基站发送切换请求响应消息，所述切换请求响应消息包括：所述目标基站接纳成功或失败的PDU flow的信息或RB的信息。
  8. 根据权利要求4所述的方法，还包括：
    所述目标基站向核心网控制面功能实体发送传输路径更新消息，携带接纳后的PDU flow的信息；
    所述目标基站接收所述核心网控制面功能实体发送的传输路径更新确认消息。
  9. 一种切换场景下的QoS参数处理的方法，包括：
    核心网控制面功能实体向目标基站发送切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
    其中，所述基于PDU flow的QoS参数或基于RB的QoS参数用于所述目标基站进行接纳控制。
  10. 根据权利要求9所述的方法，还包括：
    所述核心网控制面功能实体接收所述目标基站发送的切换请求确认消息，所述切换请求确认消息包括所述目标基站接纳成功或失败的PDU flow或RB的信息；
    所述核心网控制面功能实体向源基站发送切换命令。
  11. 一种切换场景下的QoS参数处理的方法，包括：
    目标基站接收核心网控制面功能实体发送的切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
    所述目标基站根据所述PDU flow的QoS参数或基于RB的QoS参数进行接纳控制。
  12. 根据权利要求11所述的方法，还包括：
    所述目标基站根据基于PDU flow的QoS参数，生成所述目标基站的PDU flow到RB的汇聚映射关系，以及相应RB的配置参数。
  13. 根据权利要求11所述的方法，其中，
    所述切换请求消息还包括：源基站生成的PDU flow的RB的映射关系；
    所述方法还包括：
    所述目标基站根据所述源基站生成的PDU flow的RB的映射关系，生成 所述目标基站的PDU flow到RB的汇聚映射关系，以及相应RB的配置参数。
  14. 根据权利要求11所述的方法，还包括：
    所述目标基站向所述核心网控制面功能实体发送切换确认消息，所述切换请求确认消息包括：所述目标基站接纳成功或失败的PDU flow或RB的信息。
  15. 一种源基站，包括：
    第一发送模块，用于向目标基站发送切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
    其中，所述基于PDU flow的QoS参数或基于RB的QoS参数用于所述目标基站进行接纳控制。
  16. 根据权利要求15所述的源基站，其中，所述切换请求消息还包括：所述源基站生成的PDU flow的RB的映射关系。
  17. 根据权利要求15所述的源基站，其中，所述源基站还包括：
    第一接收模块，用于接收所述目标基站发送的切换响应消息，所述切换响应消息包括：所述目标基站接纳成功或失败的PDU flow或RB的信息。
  18. 一种目标基站，包括：
    第二接收模块，用于接收源基站发送的切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
    第一接纳控制模块，用于根据所述基于PDU flow的QoS参数或者基于RB的QoS参数进行接纳控制。
  19. 根据权利要求18所述的目标基站，还包括：
    第一生成模块，用于根据基于PDU flow的QoS参数，生成所述目标基站的PDU flow到RB的汇聚映射关系，以及相应RB的配置参数。
  20. 根据权利要求18所述的目标基站，其中，
    所述切换请求消息还包括：所述源基站生成的PDU flow的RB的映射关系；
    所述目标基站还包括：
    第二生成模块，用于根据所述源基站生成的PDU flow的RB的映射关系，生成所述目标基站的PDU flow到RB的汇聚映射关系，以及相应RB的配置 参数。
  21. 根据权利要求18所述的目标基站，还包括：
    第二发送模块，用于向所述源基站发送切换请求响应消息，所述切换请求响应消息包括：所述目标基站接纳成功或失败的PDU flow或RB的信息。
  22. 根据权利要求18所述的目标基站，还包括：
    第六发送模块，用于向核心网控制面功能实体发送传输路径更新消息，携带接纳后的PDU flow的信息；
    第五接收模块，用于接收所述核心网控制面功能实体发送的传输路径更新确认消息。
  23. 一种核心网控制面功能实体，包括：
    第三发送模块，用于向目标基站发送切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
    其中，所述基于PDU flow的QoS参数或基于RB的QoS参数用于所述目标基站进行接纳控制。
  24. 根据权利要求23所述的核心网控制面功能实体，还包括：
    第三接收模块，用于接收所述目标基站发送的切换请求确认消息，所述切换请求确认消息包括所述目标基站接纳成功或失败的PDU flow的信息或RB的信息；
    第四发送模块，用于向源基站发送切换命令。
  25. 一种目标基站，包括：
    第四接收模块，用于接收核心网控制面功能实体发送的切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
    第二接纳控制模块，用于根据所述PDU flow的QoS参数或基于RB的QoS参数进行接纳控制。
  26. 根据权利要求25所述的目标基站，还包括：
    第三生成模块，用于根据基于PDU flow的QoS参数，生成所述目标基站的PDU flow到RB的汇聚映射关系，以及相应RB的配置参数。
  27. 根据权利要求25所述的目标基站，其中，
    所述切换请求消息还包括：源基站生成的PDU flow的RB的映射关系；
    所述目标基站还包括：
    第四生成模块，用于根据所述源基站生成的PDU flow的RB的映射关系，生成所述目标基站的PDU flow到RB的汇聚映射关系，以及相应RB的配置参数。
  28. 根据权利要求25所述的目标基站，其中，所述目标基站还包括：
    第五发送模块，用于向所述核心网控制面功能实体发送切换确认消息，所述切换请求确认消息包括：所述目标基站接纳成功或失败的PDU flow或RB的信息。
  29. 一种源基站，包括：处理器、存储器和收发机，其中：
    所述处理器，用于读取存储器中的程序，执行下列过程：
    通过所述收发机向目标基站发送切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
    其中，所述基于PDU flow的QoS参数或基于RB的QoS参数用于所述目标基站进行接纳控制，
    所述收发机用于接收和发送数据，
    所述存储器能够存储所述处理器在执行操作时所使用的数据。
  30. 一种目标基站，包括：处理器、存储器和收发机，其中：
    所述处理器，用于读取存储器中的程序，执行下列过程：
    通过所述收发机接收源基站发送的切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
    根据所述基于PDU flow的QoS参数或者基于RB的QoS参数进行接纳控制，
    所述收发机用于接收和发送数据，
    所述存储器能够存储所述处理器在执行操作时所使用的数据。
  31. 一种核心网控制面功能实体，包括：处理器、存储器和收发机，其中：
    所述处理器，用于读取存储器中的程序，执行下列过程：
    通过所述收发机向目标基站发送切换请求消息，所述切换请求消息 包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
    其中，所述基于PDU flow的QoS参数或基于RB的QoS参数用于所述目标基站进行接纳控制，
    所述收发机用于接收和发送数据，
    所述存储器能够存储所述处理器在执行操作时所使用的数据。
  32. 一种目标基站，包括：处理器、存储器和收发机，其中：
    所述处理器，用于读取存储器中的程序，执行下列过程：
    通过所述收发机接收核心网控制面功能实体发送的切换请求消息，所述切换请求消息包括：基于PDU flow的QoS参数和/或基于RB的QoS参数；
    根据所述PDU flow的QoS参数或基于RB的QoS参数进行接纳控制，
    所述收发机用于接收和发送数据，
    所述存储器能够存储所述处理器在执行操作时所使用的数据。
PCT/CN2017/087901 2016-08-12 2017-06-12 切换场景下的QoS参数处理的方法及设备 WO2018028295A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
US16/323,767 US10959133B2 (en) 2016-08-12 2017-06-12 Method and device for processing quality of service parameter in handover scenario
EP17838427.7A EP3477991B1 (en) 2016-08-12 2017-06-12 Method and device for processing quality of service parameter in handover scenario
KR1020197007268A KR102210296B1 (ko) 2016-08-12 2017-06-12 핸드오버 시나리오에서의 QoS 파라미터 처리 방법 및 기기
JP2019506666A JP6743281B2 (ja) 2016-08-12 2017-06-12 切替シナリオでのＱｏＳパラメータ処理方法および機器

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610663580.1A CN107734563B (zh) 2016-08-12 2016-08-12 切换场景下的QoS参数处理的方法及设备
CN201610663580.1 2016-08-12

Publications (1)

Publication Number Publication Date
WO2018028295A1 true WO2018028295A1 (zh) 2018-02-15

Family

ID=61162661

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/087901 WO2018028295A1 (zh) 2016-08-12 2017-06-12 切换场景下的QoS参数处理的方法及设备

Country Status (6)

Country Link
US (1) US10959133B2 (zh)
EP (1) EP3477991B1 (zh)
JP (1) JP6743281B2 (zh)
KR (1) KR102210296B1 (zh)
CN (1) CN107734563B (zh)
WO (1) WO2018028295A1 (zh)

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108024294B (zh) * 2016-11-02 2020-08-07 中兴通讯股份有限公司 切换方法及装置
SG11201811794YA (en) * 2017-01-05 2019-01-30 Lg Electronics Inc Method and device for transmitting rule for qos flow to drb mapping
CN108632909B (zh) * 2017-03-24 2019-08-23 电信科学技术研究院 一种QoS处理方法和装置
CN108632910B (zh) * 2017-03-24 2019-07-02 电信科学技术研究院 一种QoS处理方法和设备
CN108811153A (zh) * 2017-05-05 2018-11-13 华为技术有限公司 通信方法、集中式单元、分布式单元、基站及终端设备
CN110290569A (zh) * 2018-03-19 2019-09-27 中兴通讯股份有限公司 参数配置方法、装置、网元、基站及存储介质
US10911979B2 (en) * 2018-04-09 2021-02-02 Mediatek Inc. AT commands for 5G session management
CN112970284B (zh) * 2018-09-29 2023-02-21 中兴通讯股份有限公司 使用多个分组数据单元会话的超可靠通信
CN111093233B (zh) * 2018-10-24 2022-09-06 中国移动通信有限公司研究院 一种切换控制方法、装置及基站
CN111263416A (zh) 2018-12-03 2020-06-09 北京三星通信技术研究有限公司 切换的方法和设备
CN113852999A (zh) * 2020-06-28 2021-12-28 中兴通讯股份有限公司 资源管理方法及网络设备
US11445410B2 (en) 2021-01-21 2022-09-13 Sprint Communications Company L.P. Wireless communication service delivery responsive to user equipment (UE) handovers
EP4064757A1 (en) * 2021-03-22 2022-09-28 Robert Bosch GmbH Handover-service preparation via pre-announcement
CN114867071B (zh) * 2022-03-25 2024-10-29 成都中科微信息技术研究院有限公司 一种QoS流与DRB聚合关系建立方法、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102316540A (zh) * 2010-07-08 2012-01-11 中兴通讯股份有限公司 一种切换时的接入控制方法及系统
CN102948215A (zh) * 2010-06-21 2013-02-27 高通股份有限公司 无线通信系统中在无线接入技术间切换期间进行qos 上下文转换的方法和装置
WO2015160329A1 (en) * 2014-04-15 2015-10-22 Nokia Solutions And Networks Oy Interworking with bearer-based system
WO2016003113A1 (ko) * 2014-06-30 2016-01-07 삼성전자 주식회사 무선 통신 시스템에서 서비스 연속성을 제어하는 방법 및 장치

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1909521A1 (en) * 2006-10-02 2008-04-09 Matsushita Electric Industrial Co., Ltd. Method for supporting quality of service over a connection lifetime
EP2553963B1 (en) * 2010-04-02 2020-07-22 InterDigital Patent Holdings, Inc. Method and apparatus for supporting communication via a relay node
US8908636B2 (en) * 2010-06-21 2014-12-09 Qualcomm Incorporated Method and apparatus for QoS context transfer during inter radio access technology handover in a wireless communication system
US9807426B2 (en) 2011-07-01 2017-10-31 Qualcomm Incorporated Applying non-square transforms to video data
KR20140080192A (ko) * 2012-12-20 2014-06-30 주식회사 팬택 이종 네트워크 무선 통신 시스템에서 베어러 확장 제어 방법 및 그 장치
CN104105148A (zh) * 2013-04-07 2014-10-15 电信科学技术研究院 一种小区切换方法及设备
US9420503B2 (en) * 2014-01-21 2016-08-16 Cisco Technology, Inc. System and method for seamless mobility in a network environment
JP6426648B2 (ja) 2016-04-12 2018-11-21 株式会社Ｎｔｔドコモ 動画像予測復号方法及び動画像予測復号装置
CN108781396B (zh) 2016-08-10 2021-04-13 日本电气株式会社 无线电接入网络节点、无线电终端、核心网络节点及其方法
EP3958615A1 (en) 2016-08-10 2022-02-23 NEC Corporation Radio access network node, radio terminal, core network node, and method therefor

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102948215A (zh) * 2010-06-21 2013-02-27 高通股份有限公司 无线通信系统中在无线接入技术间切换期间进行qos 上下文转换的方法和装置
CN102316540A (zh) * 2010-07-08 2012-01-11 中兴通讯股份有限公司 一种切换时的接入控制方法及系统
WO2015160329A1 (en) * 2014-04-15 2015-10-22 Nokia Solutions And Networks Oy Interworking with bearer-based system
WO2016003113A1 (ko) * 2014-06-30 2016-01-07 삼성전자 주식회사 무선 통신 시스템에서 서비스 연속성을 제어하는 방법 및 장치

Also Published As

Publication number Publication date
US20190215735A1 (en) 2019-07-11
EP3477991A4 (en) 2019-05-01
JP6743281B2 (ja) 2020-08-19
KR20190039245A (ko) 2019-04-10
US10959133B2 (en) 2021-03-23
EP3477991B1 (en) 2020-08-12
JP2019525629A (ja) 2019-09-05
EP3477991A1 (en) 2019-05-01
CN107734563B (zh) 2020-02-07
KR102210296B1 (ko) 2021-01-29
CN107734563A (zh) 2018-02-23

Similar Documents

Publication Publication Date Title
WO2018028295A1 (zh) 切换场景下的QoS参数处理的方法及设备
EP3032871B1 (en) Data transmission method, device and system
WO2019184651A1 (zh) 一种通信方法及装置
WO2018171398A1 (zh) QoS处理方法和设备
WO2020001562A1 (zh) 一种通信方法及装置
US11356294B2 (en) Packet processing method and device
WO2019242749A1 (zh) 一种切换方法及装置
WO2018018621A1 (zh) 建立辅连接的方法和装置
WO2022206775A1 (zh) 一种多播广播业务的传输切换方法及装置
EP4221005A1 (en) Multipath transmission method and communication apparatus
WO2019024032A1 (zh) 数据传输方法、相关设备及通信系统
WO2018082576A1 (zh) 一种适应灵活部署场景的网络架构
WO2021097858A1 (zh) 一种通信方法及装置
WO2015188357A1 (zh) 一种控制承载切换的设备和控制方法
WO2021135650A1 (zh) 通信方法及装置
WO2020103871A1 (zh) 一种数据通信方法及装置
WO2019213922A1 (zh) 中继网络中节点间转发数据的方法和网络节点
WO2022156439A1 (zh) 信息传输方法、装置、基站及介质
EP4117338A1 (en) Data transmission method and apparatus
WO2019137169A1 (zh) 数据传输方法、装置、设备及计算机可读存储介质
WO2021208813A1 (zh) 一种通信方法及通信装置
WO2018098762A1 (zh) 信息传输方法、基站和终端设备
WO2023124822A1 (zh) 一种通信协作方法及装置
WO2022218099A1 (zh) 组播通信方法及通信装置
TWI679870B (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: 17838427

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019506666

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017838427

Country of ref document: EP

Effective date: 20190125

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20197007268

Country of ref document: KR

Kind code of ref document: A