WO2018171386A1 - 一种QoS处理方法和装置 - Google Patents

一种QoS处理方法和装置 Download PDF

Info

Publication number
WO2018171386A1
WO2018171386A1 PCT/CN2018/077260 CN2018077260W WO2018171386A1 WO 2018171386 A1 WO2018171386 A1 WO 2018171386A1 CN 2018077260 W CN2018077260 W CN 2018077260W WO 2018171386 A1 WO2018171386 A1 WO 2018171386A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
target base
qos
message
flows
Prior art date
Application number
PCT/CN2018/077260
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/496,944 priority Critical patent/US11190984B2/en
Priority to EP18771369.8A priority patent/EP3606171A4/en
Publication of WO2018171386A1 publication Critical patent/WO2018171386A1/zh

Links

Images

Classifications

    • 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
    • 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/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H04W28/22—Negotiating communication rate
    • 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
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H04W36/023—Buffering or recovering information during reselection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a QoS (Quality of Service) processing method and apparatus in a handover scenario or a PDU (Protocol Data Unit) session setup scenario.
  • QoS Quality of Service
  • PDU Protocol Data Unit
  • the target base station determines whether it can accept all bearers of the UE (User Equipment) according to its load and radio conditions. If the UE cannot receive all the bearers, it will notify the bearer that the original base station cannot accept in the handover response message, and the source base station side needs to deactivate the bearer, which may cause some services to be unsupported.
  • UE User Equipment
  • the embodiments of the present disclosure provide a QoS processing method and apparatus, which avoids the problem that the target base station is directly deactivated when the QoS parameters of one or more flows of the UE cannot be met.
  • a QoS processing method comprising:
  • the target base station sends a first message to the source base station, where the first message includes: first information for notifying the source base station that the target base station cannot meet the QoS requirement of the one or more flows of the UE, and for the one or more The second information of the QoS parameters that the target base station can accept is recommended by the flow.
  • the method further includes:
  • the target base station sends a second message to the core network, where the second message includes third information for notifying the core network that the target base station cannot meet the QoS requirements of one or more flows of the UE.
  • the second message further includes fourth information about the QoS parameters that the target base station can accept for the one or more flows.
  • the method further includes:
  • the target base station receives the updated QoS parameters of the one or more flows sent by the core network.
  • a QoS processing method is further provided, where the method includes:
  • the source base station receives the first message sent by the target base station, and acquires first information in the first message that is used to notify the source base station that the target base station cannot meet the QoS requirements of one or more flows of the UE;
  • the source base station sends a third message to the core network, where the third message includes fifth information used to notify the core network that the target base station cannot meet the QoS requirements of one or more flows of the UE;
  • the first message further includes second information about a QoS parameter that the target base station can accept for the one or more flows.
  • the third message further includes sixth information about the QoS parameters that the target base station can accept for the one or more flows.
  • the method further includes:
  • the source base station selects an appropriate target base station to re-initiate the handover process according to the updated QoS parameters of the one or more flows.
  • a QoS processing method is further provided, where the method includes:
  • the target base station sends a fourth message to the core network, where the fourth message includes seventh information for notifying the core network that the target base station cannot meet the QoS requirements of one or more flows of the UE.
  • the fourth message further includes eighth information about a QoS parameter that the target base station can accept for the one or more flows.
  • the method further includes:
  • the target base station receives the updated QoS parameters of the one or more flows sent by the core network.
  • the method further includes:
  • the target base station receives the handover request message sent by the source base station through the core network.
  • a QoS processing method is further provided, where the method includes:
  • the core network receives a fourth message sent by the target base station, where the fourth message includes seventh information for notifying the core network that the target base station cannot meet the QoS requirements of one or more flows of the UE.
  • the fourth message further includes eighth information about a QoS parameter that the target base station can accept for the one or more flows.
  • the method further includes:
  • the core network receives a handover response message sent by the target base station.
  • the method further includes:
  • the core network sends a fifth message to the source base station, where the fifth message includes ninth information indicating a QoS parameter of the updated one or more flows.
  • a QoS processing apparatus is further provided, which is applied to a target base station, where the apparatus includes:
  • a first notification module configured to send a first message to the source base station, where the first message includes: first information for notifying the source base station that the target base station cannot meet the QoS requirement of the one or more flows of the UE Determining, by the one or more flows, the second information of the QoS parameters that the target base station can accept.
  • the device further includes:
  • the second notification module is configured to send a second message to the core network, where the second message includes third information for notifying the core network that the target base station cannot meet the QoS requirements of the one or more flows of the UE.
  • the second message further includes fourth information about the QoS parameters that the target base station can accept for the one or more flows.
  • the device further includes:
  • a first receiving module configured to receive an updated QoS parameter of the one or more flows sent by the core network.
  • a QoS processing apparatus is further provided, which is applied to a source base station, where the apparatus includes:
  • a second receiving module configured to receive a first message sent by the target base station, and obtain first information in the first message that is used to notify the source base station that the target base station cannot meet the QoS requirement of one or more flows of the UE;
  • a third notification module configured to send a third message to the core network, where the third message includes second information used to notify the core network that the target base station cannot meet the QoS requirements of one or more flows of the UE;
  • the first message further includes second information about a QoS parameter that the target base station can accept for the one or more flows.
  • the third message further includes sixth information about the QoS parameters that the target base station can accept for the one or more flows.
  • the device further includes:
  • a third receiving module configured to receive an updated QoS parameter of the one or more flows sent by the core network
  • a switching module configured to select a suitable target base station to re-initiate the handover process according to the updated QoS parameters of the one or more flows.
  • a QoS processing apparatus is further provided, which is applied to a target base station, where the apparatus includes:
  • the fourth notification module is configured to send a fourth message to the core network, where the fourth message includes seventh information for notifying the core network that the target base station cannot meet the QoS requirements of one or more flows of the UE.
  • the fourth message further includes eighth information about a QoS parameter that the target base station can accept for the one or more flows.
  • the device further includes:
  • a fourth receiving module configured to receive an updated QoS parameter of the one or more flows sent by the core network.
  • the device further includes:
  • the fifth receiving module is configured to receive, by using the core network, a handover request message sent by the source base station.
  • An eighth aspect of the present disclosure further provides a QoS processing apparatus, which is applied to a core network, where the apparatus includes:
  • a sixth receiving module configured to receive a fourth message sent by the target base station, where the fourth message includes seventh information for notifying the core network that the target base station cannot meet the QoS requirement of one or more flows of the UE.
  • the fourth message further includes eighth information about a QoS parameter that the target base station can accept for the one or more flows.
  • the device further includes:
  • a first sending module configured to send, to the target base station, the updated QoS parameters of the one or more flows
  • the seventh receiving module is configured to receive a handover response message sent by the target base station.
  • the device further includes:
  • the second sending module is configured to send a fifth message to the source base station, where the fifth message carries ninth information indicating a QoS parameter of the updated one or more flows.
  • a ninth aspect according to an embodiment of the present disclosure further provides a base station including a memory, a processor, and a computer program stored on the memory and operable on the processor, the processor executing the computer program as described above The steps in the QoS processing method.
  • a core network side device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor executing the computer
  • the steps in the QoS processing method as described above are implemented at the time of the program.
  • a computer readable storage medium having stored thereon a computer program (instruction), the program (instruction) being executed by a processor to implement the QoS processing method as described above The steps in .
  • One of the foregoing technical solutions has the following advantages or advantages: providing a processing flow when the target base station cannot meet the QoS requirement, for example, by using the target that is carried in the first message for the one or more flows.
  • the QoS parameters that the base station can receive so that the target base station can notify the source base station of the QoS parameters that the source base station can receive when notifying the source base station that it cannot satisfy the QoS requirements of one or more flows of the UE, thereby avoiding direct deactivation of the source base station in the related art.
  • FIG. 1 is a schematic structural diagram of a bearer model in a related LTE system
  • FIG. 2 is a schematic diagram of a related LTE architecture
  • FIG. 3 is a schematic diagram of an architecture of a 5G system
  • FIG. 4 is a schematic diagram of a 5G network architecture
  • FIG. 5 is a flowchart of a QoS processing method in an embodiment of the present disclosure
  • FIG. 6 is a flowchart of a QoS processing method in another embodiment of the present disclosure.
  • FIG. 7 is a flowchart of a QoS processing method in an embodiment of the present disclosure.
  • FIG. 8 is a flowchart of a QoS processing method in another embodiment of the present disclosure.
  • FIG. 9 is a flowchart of a QoS processing method in an embodiment of the present disclosure.
  • FIG. 10 is a flowchart of a QoS processing method in another embodiment of the present disclosure.
  • FIG. 11 is a flowchart of a QoS processing method in an embodiment of the present disclosure.
  • FIG. 13 is a flowchart of the Xn handover process in an embodiment of the present disclosure, after the handover, notifying the core network RAN (Radio Access Network) that the QoS requirements of certain flows cannot be met;
  • RAN Radio Access Network
  • FIG. 14 is a flowchart of an Xn handover procedure in an embodiment of the present disclosure, before the handover, notifying the core network RAN side that the QoS requirements of some flows cannot be met;
  • Figure 15 is a flowchart of an NG handover procedure in an embodiment of the present disclosure.
  • FIG. 16 is a structural diagram of a QoS processing apparatus in an embodiment of the present disclosure.
  • FIG. 17 is a structural diagram of a QoS processing apparatus in another embodiment of the present disclosure.
  • FIG. 18 is a structural diagram of a QoS processing apparatus in still another embodiment of the present disclosure.
  • FIG. 19 is a structural diagram of a QoS processing apparatus in still another embodiment of the present disclosure.
  • 20 is a structural diagram of a target base station in an embodiment of the present disclosure.
  • 21 is a structural diagram of a source base station in an embodiment of the present disclosure.
  • FIG. 22 is a structural diagram of a target base station in another embodiment of the present disclosure.
  • FIG. 23 is a structural diagram of a core network side device in an embodiment of the present disclosure.
  • the core network is responsible for generating the QoS parameters of the E-RAB (Evolved Radio Access Bearer), and the air interface RB (Radio Bearer) and the E-RAB are one-to-one mapping relationship. Therefore, the QoS parameters of the air interface RB directly adopt the E-RAB QoS parameters generated by the core network.
  • E-RAB Evolved Radio Access Bearer
  • RB Radio Bearer
  • the embodiments of the present disclosure can be used in different network deployment structures.
  • two network deployment structures that may be adopted for future mobile communication are first introduced.
  • Deployment structure 1 base station + terminal
  • a typical LTE architecture is shown. There are multiple cells in the eNB (base station), and the UE and the cell perform air interface data transmission and reception in the connected state.
  • Deployment structure 2 The network side nodes are 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 unit, and one central unit controls a plurality of distributed units deployed in a certain area, and these distributed units Specifically, the air interface is transmitted to the terminal through a Transmission Reception Point (TRP).
  • TRP Transmission Reception Point
  • One or more transmission points can simultaneously serve the terminal for data transmission.
  • Embodiments of the present disclosure are applicable to the above two RAN architectures.
  • the 5G network architecture is shown in Figure 4.
  • the three logical entities in the network architecture are CN-C (core network control plane functional entity) located on the core network, and CN-U (core network user plane functional entity); gNB (Next Generation Base Station) and eLTE eNB (Base Station for Evolved LTE) of the access network.
  • CN-C and gNB establish an NG-C interface for control plane signaling transmission;
  • CN-U and gNB establish NG-U for user plane data transmission.
  • the Xn interface is established between the wireless access networks g-NB, and the Xn interface supports both control planes (such as Xn-C) and user plane functions (such as Xn-U).
  • a control plane connection with a UE granularity may be established on the NG-C (where the control plane connection corresponding to each UE may be identified by using an NG-AP ID), and a PDU session (PDU session) is established on the NG-U.
  • User plane connection or user plane tunnel
  • one UE can only maintain one NG-C connection with CN-C at the same time, but can simultaneously establish multiple PDUs with CN-U on NG-U interface
  • a Session (PDU Session) is a granular user plane connection (or user plane tunnel).
  • the 5G core network has no bearer concept.
  • the QoS parameters sent by the core network CN-C to the gNB are configured with the flow granularity.
  • the access network gNB still performs QoS management with RB (Radio Bearer) granularity, the access network needs to generate RB-level QoS parameters for the interaction process between the gNB and the UE and the gNB and other radio access entities. .
  • RB Radio Bearer
  • Step 501 The target base station sends a first message to the source base station, where the first message includes: first information for notifying the source base station that the QoS requirement of the one or more flows of the terminal (UE) cannot be met, and further includes: The second information of the QoS parameters that the target base station is capable of accepting by the one or more flows.
  • the target base station notifies the source base station in the handover response message that the target base station cannot satisfy the flow list of the QoS requirements, and may also carry the QoS parameters recommended for the flows.
  • the source base station can determine the target base station that meets the QoS requirements with reference to the QoS parameters recommended for these flows.
  • the QoS parameter that can be accepted by the target base station for the one or more flow recommendations carried in the first message is such that the target base station notifies the source base station that it cannot satisfy one or more flows of the UE.
  • the source base station can be notified of the QoS parameters that the source base station can receive, and the source base station in the related art can directly deactivate the bearer that the target base station cannot accept, and the target base station cannot support the corresponding service.
  • the specific process includes:
  • Step 601 The target base station sends a first message to the source base station, where the first message includes: first information for notifying the source base station that the QoS requirement of the one or more flows of the terminal (UE) cannot be satisfied, and is used for indicating
  • the second information of the QoS parameters that the target base station is capable of accepting for the one or more flow recommendations further includes.
  • the target base station notifies the source base station in the handover response message that the target base station cannot satisfy the QoS requirement flow list, and may also carry the QoS parameters recommended for the flow.
  • Step 602 The target base station sends a second message to the core network, where the second message includes third information used to notify the core network that the target base station cannot meet the QoS requirements of one or more flows of the UE.
  • the target base station may notify the core network RAN side that the QoS requirement of the certain or some flows cannot be met.
  • the second message further includes fourth information about the QoS parameters that the target base station can accept for the one or more flows.
  • the method further includes:
  • Step 603 The target base station receives the QoS parameters of the updated one or more flows sent by the core network.
  • the core network can update the QoS parameters of one or more flows based on QoS parameters that the target base station can receive for the one or more flow recommendations carried in the second message.
  • a processing flow when the target base station cannot satisfy the QoS requirement is provided. And the QoS parameter that can be received by the target base station for the one or more flow recommendations carried in the first message, so that the target base station can notify the source base station that it cannot meet the QoS requirements of one or more flows of the UE, At the same time, the source base station is notified of the QoS parameters that can be received by the source base station, so that the source base station in the related art directly deactivates the bearer that the target base station cannot accept, and the target base station cannot support the corresponding service.
  • FIG. 7 a flow of a QoS processing method in an embodiment is shown, and the specific steps are as follows:
  • Step 701 The source base station receives the first message sent by the target base station, and acquires first information in the first message that indicates that the target base station cannot meet the QoS requirement of the one or more flows of the UE.
  • the first message further includes second information for indicating a QoS parameter that the target base station can accept for the one or more flow recommendations.
  • the target base station notifies the source base station in the handover response message that the target base station cannot satisfy the QoS requirement flow list, and may also carry the QoS parameters recommended for the flow.
  • Step 702 The source base station sends a third message to the core network, where the third message includes a fifth information, configured to notify the core network that the target base station cannot meet the QoS requirement of the one or more flows of the UE.
  • the third message further includes sixth information for indicating a QoS parameter that the target base station can accept for the one or more flow recommendations.
  • a processing flow when the target base station cannot satisfy the QoS requirement is provided. And the QoS parameter that can be received by the target base station for the one or more flow recommendations carried in the first message, so that the target base station can notify the source base station that it cannot meet the QoS requirements of one or more flows of the UE, At the same time, the source base station is notified of the QoS parameters that can be received by the source base station, so that the source base station in the related art directly deactivates the bearer that the target base station cannot accept, and the target base station cannot support the corresponding service.
  • FIG. 8 a flow of a QoS processing method in another embodiment is shown, and the specific steps are as follows:
  • Step 801 The source base station receives the first message, and obtains first information in the first message that indicates that the target base station cannot meet the QoS requirement of the one or more flows of the UE.
  • the first message further includes Second information of QoS parameters that the target base station can receive for the one or more flow recommendations.
  • the target base station notifies the source base station in the handover response message that the target base station cannot satisfy the QoS requirement flow list, and may also carry the QoS parameters recommended for the flow.
  • Step 802 The source base station sends a third message to the core network, where the third message includes fifth information used to notify the core network that the target base station cannot meet the QoS requirements of one or more flows of the UE.
  • the third message further includes sixth information for indicating a QoS parameter that the target base station can accept for the one or more flow recommendations.
  • Step 803 The source base station receives the QoS parameter of the updated one or more flows sent by the core network.
  • Step 804 The source base station selects an appropriate target base station to re-initiate the handover process according to the updated QoS parameters of the one or more flows.
  • a processing flow when the target base station cannot satisfy the QoS requirement is provided. And the QoS parameter that can be received by the target base station for the one or more flow recommendations carried in the first message, so that the target base station can notify the source base station that it cannot meet the QoS requirements of one or more flows of the UE, At the same time, the source base station is notified of the QoS parameters that can be received by the source base station, so that the source base station in the related art directly deactivates the bearer that the target base station cannot accept, and the target base station cannot support the corresponding service.
  • the source base station may further select a suitable target base station to re-initiate the handover process according to the updated QoS parameters of the one or more flows, improve the entire handover process, and ensure that the QoS requirements of one or more flows of the UE can be The target base station accepts.
  • FIG. 9 a flow of a QoS processing method in an embodiment is shown. The specific steps are as follows:
  • Step 901 The target base station sends a fourth message to the core network, where the fourth message includes seventh information used to notify the core network that the target base station cannot meet the QoS requirements of one or more flows of the UE.
  • the fourth message further includes eighth information about a QoS parameter that the target base station can accept for the one or more flows.
  • the target base station receives the QoS parameters of the updated one or more flows sent by the core network.
  • the target base station may send a handover response to the core network, and then the core network carries the updated QoS parameter in the handover response to the source base station, and then Then, the source base station sends a handover command to the UE, and the UE accesses the target cell.
  • the flow of the QoS processing shown in FIG. 9 may be applicable to a handover scenario, and may also be applied to a PDU session establishment process.
  • the target base station may also be referred to as the serving base station of the UE. If the serving base station of the UE cannot meet the QoS requirements of one or more flows of the PDU session, the serving base station of the UE may also notify by a message. The core network cannot meet the QoS requirements of one or more flows of the UE.
  • Step 1001 The target base station receives, by using the core network, a handover request message sent by the source base station.
  • Step 1002 The target base station sends a fourth message to the core network, where the fourth message includes seventh information for notifying the core network that the target base station cannot meet the QoS requirements of one or more flows of the UE.
  • the fourth message further includes eighth information about a QoS parameter that the target base station can accept for the one or more flows.
  • Step 1003 The target base station receives the updated QoS parameters of the one or more flows sent by the core network.
  • a processing flow when the target base station cannot satisfy the QoS requirement is provided.
  • the QoS parameters that can be received, and the target base station can also receive the updated QoS parameters of the one or more flows sent by the core network, so as to prevent the source base station from directly deactivating the bearer that the target base station cannot accept, thereby causing the target base station Unable to support the corresponding business.
  • the source base station may further select a suitable target base station to re-initiate the handover process according to the updated QoS parameters of the one or more flows, improve the entire handover process, and ensure that the QoS requirements of one or more flows of the UE can be The target base station accepts.
  • FIG. 11 a flow of a QoS processing method in an embodiment is shown. The specific steps are as follows:
  • Step 1101 The core network receives the fourth message sent by the target base station, and acquires seventh information in the fourth message that is used to notify the core network that the target base station cannot meet the QoS requirement of one or more flows of the UE.
  • the fourth message further includes eighth information about the QoS parameters that the target base station can accept for the one or more flows.
  • a processing flow when the target base station cannot satisfy the QoS requirement is provided.
  • QoS parameters that can be accepted are provided.
  • Step 1201 The core network receives the fourth message sent by the target base station, and acquires seventh information in the fourth message that is used to notify the core network that the target base station cannot meet the QoS requirement of one or more flows of the UE.
  • the fourth message further includes eighth information about the QoS parameters that the target base station can accept for the one or more flows.
  • Step 1202 The core network sends the QoS parameter of the updated one or more flows to the target base station.
  • Step 1203 The core network receives a handover response message sent by the target base station.
  • Step 1204 The core network sends a fifth message to the source base station, where the fifth message carries the updated QoS parameters of the one or more flows.
  • the source base station may send a handover command to the UE, and the UE accesses the target cell.
  • the processes shown in FIG. 11 and FIG. 12 can be applied to the NG handover process. That is, in the NG handover process, the target base station notifies the core network that the QoS parameter requirements of one or more flows cannot be satisfied, and further, the recommended QoS parameters may also be provided.
  • a processing flow when the target base station cannot satisfy the QoS requirement is provided.
  • QoS parameters that can be accepted are provided.
  • the source base station may give an indication to the source base station, and at the same time, the target base station may also carry the flow.
  • the recommended QoS parameters the source base station can refer to the information to determine the final target cell.
  • the target base station After the handover is completed, the target base station notifies the core network that the QoS requirements of some flows of the UE cannot be met. At the same time, the recommended QoS parameters of the stream may also be carried.
  • the core network updates the QoS parameters of the flow according to the information and sends the QoS parameters to the target base station.
  • the Xn handover process notifies the RAN side of the core network that the QoS requirements of some flows cannot be met after the handover.
  • the Xn handover process notifies the RAN side of the core network that the QoS requirements of some flows cannot be met after the handover.
  • Step 1301 The source base station (Source node) sends a handover request message (Handover Request) to a plurality of target base stations (Target cell 1 and Target cell 2).
  • Step 1302 The target base station performs admission control according to the QoS parameter of the flow, and returns successfully received flow information and a flow that cannot satisfy the QoS requirement in the handover request response message (Handover request ACK1 and Handover request ACK2) (only applicable to notification control ( Notification Control) The information of the stream, and the information of the stream that failed to accept.
  • Handover request ACK1 and Handover request ACK2 only applicable to notification control ( Notification Control)
  • Notification Control Notification Control
  • the QoS parameter that can be accepted by the local base station can be carried in the response message.
  • Step 1303 The source base station selects a last target cell according to the received response message (Select the proper target cell), and sends a handover cancel message (Handover cancel) to the other target cells.
  • Step 1304 The source base station sends a handover command (Handover command) to the UE, and the UE accesses the target cell (UE access to the target cell).
  • a handover command (Handover command)
  • Step 1305 The target base station indicates that the QoS requirement of some flows cannot be met in the path switch message to the core network, and the core network may update the QoS parameters and notify the target base station in a path switch ACK message.
  • the target base station may also give an indication to the source base station, and the target base station may also carry the After receiving the indication, the source base station notifies the core network, and then the core network sends the updated QoS parameters of the stream to the source base station.
  • the source base station selects the target cell according to the information provided by the target base station, and initiates a handover process to the target base station.
  • the Xn handover process notifies the core network RAN side that the QoS requirements of some flows cannot be met before the handover, and the specific process can be seen in FIG. 14 .
  • Step 1401 The source base station (source node) sends a handover request message (Handover Request) to a plurality of target base stations (Target cell 1 and Target cell 2).
  • Handover Request a handover request message
  • Step 1402 The target base station performs admission control according to the QoS parameter of the flow, and returns the successfully received flow information and the flow that cannot satisfy the QoS requirement (only applicable to the flow of the notification control feature) in the handover request response message (Handover request ACK). Information, as well as information about the flow of failures.
  • the response message may carry the indication and the recommended QoS parameters that the base station can accept.
  • Step 1403 The source base station sends an indication to the core network that the RAN side cannot meet the QoS requirement.
  • Step 1404 The QoS parameter of the core network update UE is sent to the base station (CN update the QoS parameter).
  • Step 1405 The source base station selects a suitable target cell to initiate a handover process, and the handover request message carries the updated QoS parameter.
  • Step 1406 The source base station sends a handover command to the UE, and the UE accesses the target cell.
  • Step 1407 The process in which the target base station initiates a path switch to the core network.
  • the target base station if it receives the handover request from the core network, it determines that it cannot satisfy the QoS requirements of certain flows of the UE according to its own load and the like, and gives an indication to the core network. At the same time, the target base station may also carry its own recommended QoS parameters for the flow, and the core network may adjust the QoS parameters of the flow and simultaneously send the QoS parameters to the source base station and the target base station.
  • the source eNB carries the updated QoS parameters in the handover command sent to the UE. For the specific process, refer to FIG. 15.
  • Step 1501 The source base station sends a handover request (Handover Request) message to the target base station by using the CN.
  • Step 1502 The target base station notifies the CN that the QoS parameters of some flows require that the RAN side cannot be satisfied.
  • Step 1503 The core network sends the updated QoS parameter to the target base station.
  • Step 1504 The target base station sends a handover request ACK message to the core network.
  • Step 1505 The core network carries the updated QoS parameter in the handover response message to the source base station.
  • Step 1506 The source base station sends a handover command to the UE, and the UE accesses the target cell.
  • a QoS processing apparatus is also provided in the embodiment of the present disclosure. Since the principle of solving the problem is similar to the QoS processing method in FIG. 5 and FIG. 6 of the embodiment of the present disclosure, the implementation of the apparatus may refer to the method. The implementation, the repetition is no longer described.
  • the apparatus 1600 is applied to a target base station, and the apparatus 1600 includes:
  • the first notification module 1601 is configured to notify, by using the first message, that the source base station cannot meet the QoS requirement of the one or more flows of the UE, where the first message further includes the target recommended for the one or more flows The QoS parameters that the base station can accept.
  • the device 1600 further includes:
  • the second notification module 1602 is configured to notify the core network by the second message that the QoS requirement of the one or more flows of the UE cannot be met.
  • the second message further includes a QoS parameter that can be accepted by the target base station for the one or more flow recommendations.
  • the device 1600 further includes:
  • the first receiving module 1603 is configured to receive the updated QoS parameters of the one or more flows sent by the core network.
  • a QoS processing apparatus is also provided in the embodiment of the present disclosure. Since the principle of solving the problem is similar to the QoS processing method in FIG. 7 and FIG. 8 of the embodiment of the present disclosure, the implementation of the apparatus may refer to the method. The implementation, the repetition is no longer described.
  • the apparatus 1700 is applied to a source base station, and the apparatus 1700 includes:
  • the second receiving module 1701 is configured to learn, by using the first message, that the target base station cannot meet the QoS requirement of one or more flows of the UE;
  • a third notification module 1702 configured to notify, by using a third message, that the target base station in the core network cannot meet the QoS requirement of one or more flows of the UE;
  • the first message further includes a QoS parameter that can be accepted by the target base station for the one or more flow recommendations.
  • the third message further includes a QoS parameter that can be accepted by the target base station for the one or more flow recommendations.
  • the device 1700 further includes:
  • the third receiving module 1703 is configured to receive, by the core network, the updated QoS parameters of the one or more flows.
  • the switching module 1704 is configured to select a suitable target base station to re-initiate the handover process according to the updated QoS parameters of the one or more flows.
  • a QoS processing apparatus is also provided in the embodiment of the present disclosure. Since the principle of solving the problem is similar to the QoS processing method in FIG. 9 and FIG. 10 of the embodiment of the present disclosure, the implementation of the apparatus may refer to the method. The implementation, the repetition is no longer described.
  • the apparatus 1800 is applied to a target base station, including:
  • the fourth notification module 1801 is configured to notify, by using the fourth message, that the core network cannot meet the QoS requirement of one or more flows of the UE.
  • the fourth message further includes a QoS parameter that can be accepted by the target base station for the one or more flow recommendations.
  • the device 1800 further includes:
  • the fourth receiving module 1802 is configured to receive the updated QoS parameters of the one or more flows sent by the core network.
  • the device 1800 further includes:
  • the fifth receiving module 1803 is configured to receive, by using a core network, a handover request message sent by the source base station.
  • a QoS processing apparatus is also provided in the embodiment of the present disclosure. Since the principle of solving the problem is similar to the QoS processing method in FIG. 11 and FIG. 12 of the embodiment of the present disclosure, the implementation of the apparatus may refer to the method. The implementation, the repetition is no longer described.
  • the QoS processing apparatus 1900 is applied to a core network, including:
  • the sixth receiving module 1901 is configured to receive a fourth message sent by the target base station, and use the fourth message to learn that the target base station cannot meet the QoS requirement of one or more flows of the UE.
  • the fourth message further includes a QoS parameter that can be accepted by the target base station for the one or more flow recommendations.
  • the device further includes:
  • a first sending module 1902 configured to send, to the target base station, the updated QoS parameters of the one or more flows
  • the seventh receiving module 1903 is configured to receive a handover response message sent by the target base station.
  • the device further includes:
  • the second sending module 1904 is configured to send a fifth message to the source base station, where the fifth message carries the updated QoS parameter of the one or more flows.
  • an embodiment of the present disclosure provides a target base station, including:
  • the first processor 2004 is configured to read a program in the first memory 2005 and perform the following process:
  • the first transceiver 2001 is configured to receive and transmit data under the control of the first processor 2004.
  • the bus architecture (represented by the first bus 2000) can include any number of interconnected buses and bridges, the first bus 2000 will include one or more processors and firsts represented by the first processor 2004.
  • the various circuits of the memory represented by memory 2005 are linked together.
  • the first bus 2000 can also link various other circuits such as peripherals, voltage regulators, and power management circuits.
  • the first bus interface 2003 provides an interface between the first bus 2000 and the first transceiver 2001.
  • the first transceiver 2001 can be an element or a plurality of elements, such as a plurality of receivers and transmitters, providing means for communicating with various other devices on a transmission medium.
  • the data processed by the first processor 2004 is transmitted over the wireless medium by the first transceiver 2001 and the first antenna 2002. Further, the first antenna 2002 also receives data and transmits the data to the first process via the first transceiver 2001. 2004.
  • the first processor 2004 is responsible for managing the first bus 2000 and the usual processing, and can also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the first memory 2005 can be used to store data used by the first processor 2004 when performing operations.
  • the first processor 2004 may be a CPU, an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a CPLD (Complex Programmable Logic Device). Logic device).
  • the target base station sends a second message to the core network, where the second message includes third information for notifying the core network that the target base station cannot meet the QoS requirements of one or more flows of the UE.
  • the second message further includes fourth information about the QoS parameters that the target base station can accept for the one or more flows.
  • the first processor 2004 is further configured to receive the updated QoS parameters of the one or more flows sent by the core network.
  • an embodiment of the present disclosure provides a source base station, including:
  • the second processor 2104 is configured to read the program in the second memory 2105 and perform the following process:
  • Receiving a first message sent by the target base station and acquiring, in the first message, first information for notifying the source base station that the target base station cannot meet the QoS requirement of the one or more flows of the UE; sending the third message to the core network
  • the third message includes fifth information for informing the core network that the target base station cannot meet the QoS requirement of the one or more flows of the UE, where the first message further includes the one or more The second information of the QoS parameters that the target base station can accept.
  • the second transceiver 2101 is configured to receive and transmit data under the control of the second processor 2104.
  • the bus architecture (represented by the second bus 2100) can include any number of interconnected buses and bridges, and the second bus 2100 will include one or more processors and seconds represented by the second processor 2104.
  • the various circuits of the memory represented by memory 2105 are linked together.
  • the second bus 2100 can also link various other circuits such as peripherals, voltage regulators, and power management circuits.
  • the second bus interface 2103 provides an interface between the second bus 2100 and the second transceiver 2101.
  • the second transceiver 2101 can be an element or a plurality of elements, such as a plurality of receivers and transmitters, providing means for communicating with various other devices on a transmission medium.
  • the data processed by the second processor 2104 is transmitted over the wireless medium by the second transceiver 2101 and the second antenna 2102. Further, the second antenna 2102 also receives the data and transmits the data to the second processing via the second transceiver 2101. 2104.
  • the second processor 2104 is responsible for managing the second bus 2100 and the usual processing, and can also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the second memory 2105 can be used to store data used by the second processor 2104 in performing operations.
  • the second processor 2104 may be a CPU, an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a CPLD (Complex Programmable Logic Device). Logic device).
  • the third message further includes sixth information about the QoS parameters that the target base station can accept for the one or more flows.
  • the second processor 2104 is further configured to receive, by the core network, an updated QoS parameter of the one or more flows, according to the QoS parameter of the updated one or more flows, Select the appropriate target base station to re-initiate the handover process.
  • an embodiment of the present disclosure provides a target base station, including:
  • the third processor 2204 is configured to read the program in the third memory 2205 and perform the following process:
  • the fourth message including seventh information for notifying the core network that the target base station cannot satisfy the QoS requirement of one or more flows of the UE.
  • the third transceiver 2201 is configured to receive and transmit data under the control of the third processor 2204.
  • the bus architecture (represented by the third bus 2200) can include any number of interconnected buses and bridges, and the third bus 2200 will include one or more processors and thirds represented by the third processor 2204.
  • the various circuits of the memory represented by memory 2205 are linked together.
  • the third bus 2200 can also link various other circuits such as peripherals, voltage regulators, and power management circuits.
  • the third bus interface 2203 provides an interface between the third bus 2200 and the third transceiver 2201.
  • the third transceiver 2201 can be an element or a plurality of elements, such as a plurality of receivers and transmitters, providing means for communicating with various other devices on a transmission medium.
  • the data processed by the third processor 2204 is transmitted over the wireless medium through the third transceiver 2201 and the third antenna 2202. Further, the third antenna 2202 also receives the data and transmits the data to the third processing via the third transceiver 2201. 2204.
  • the third processor 2204 is responsible for managing the third bus 2200 and the usual processing, and can also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the third memory 2205 can be used to store data used by the third processor 2204 when performing operations.
  • the third processor 2204 may be a CPU, an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a CPLD (Complex Programmable Logic Device). Logic device).
  • the fourth message further includes eighth information about a QoS parameter that the target base station can accept for the one or more flows.
  • the third processor 2204 is further configured to receive the updated QoS parameters of the one or more flows sent by the core network.
  • the third processor 2204 is further configured to receive, by using a core network, a handover request message sent by the source base station.
  • an embodiment of the present disclosure provides a core network side device, including:
  • the fourth processor 2304 is configured to read the program in the fourth memory 2305 and perform the following process:
  • the target base station Receiving a fourth message sent by the target base station, where the fourth message includes seventh information for notifying the core network side device that the target base station cannot meet the QoS requirement of one or more flows of the UE.
  • the bus architecture (represented by the fourth bus 2300) may include any number of interconnected buses and bridges, and the fourth bus 2300 will include one or more processors and fourths represented by the fourth processor 2304.
  • the various circuits of the memory represented by memory 2305 are linked together.
  • the fourth bus 2300 can also link various other circuits such as peripherals, voltage regulators, and power management circuits.
  • the fourth bus interface 2303 provides an interface between the fourth bus 2300 and the fourth transceiver 2301.
  • the fourth transceiver 2301 can be an element or a plurality of elements, such as a plurality of receivers and transmitters, providing means for communicating with various other devices on a transmission medium.
  • the data processed by the fourth processor 2304 is transmitted over the wireless medium through the fourth transceiver 2301 and the fourth antenna 2302. Further, the fourth antenna 2302 also receives the data and transmits the data to the fourth processing via the fourth transceiver 2301. 2304.
  • the fourth processor 2304 is responsible for managing the fourth bus 2300 and the usual processing, and can also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the fourth memory 2305 can be used to store data used by the third processor 2204 when performing operations.
  • the fourth processor 2304 may be a CPU, an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a CPLD (Complex Programmable Logic Device). Logic device).
  • the fourth message further includes eighth information about a QoS parameter that the target base station can accept for the one or more flows.
  • the fourth processor 2304 is further configured to send the updated QoS parameter of the one or more flows to the target base station, and receive a handover response message sent by the target base station.
  • the fourth processor 2304 is further configured to send, to the source base station, a fifth message, where the fifth message includes ninth information indicating a QoS parameter of the updated one or more flows.
  • the embodiment of the present disclosure further provides a computer readable storage medium having stored thereon a computer program (instruction), which is implemented by the processor, as shown in FIG. 5, FIG. 6, FIG. 7, FIG. 8, and FIG. 9.
  • a computer program instruction
  • FIG. 10 The steps in the QoS processing method shown in FIG. 10, FIG. 11, or FIG.
  • system and “network” are used interchangeably herein.
  • B corresponding to A means that B is associated with A, and B can be determined from A.
  • determining B from A does not mean that B is only determined based on A, and that B can also be determined based on A and/or other information.
  • the disclosed method and apparatus may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • each functional unit in various embodiments of the present disclosure may be integrated into one processing unit, or each unit may be physically included separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.
  • the above-described integrated unit implemented in the form of a software functional unit can be stored in a computer readable storage medium.
  • the above software functional unit is stored in a storage medium and includes a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network side device, etc.) to perform part of the steps of the transceiving method of the various embodiments of the present disclosure.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

Landscapes

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

Abstract

本公开实施例提供了一种QoS处理方法和装置，所述方法包括：目标基站向源基站发送第一消息，所述第一消息至少包括：用于通知源基站该目标基站不能满足UE的一个或多个流的QoS要求的第一信息和针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第二信息。

Description

一种QoS处理方法和装置
相关申请的交叉引用
本申请主张在2017年3月24日在中国提交的中国专利申请No.201710182683.0的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，尤其涉及一种切换场景下或者PDU(Protocol Data Unit，协议数据单元)会话(session)建立场景下的QoS(Quality of Service，服务质量)处理方法和装置。
背景技术
相关的LTE(Long Term Evolution，长期演进)系统在切换过程中，目标基站根据自身的负荷(load)以及无线情况判断是否可以接纳UE(User Equipment，终端)所有的承载。如果UE不能接纳所有的承载，会在切换响应消息中通知原基站不能接纳的承载，源基站侧需要去激活该承载，这样导致某些业务不能支持。
如果在5G采用相同的机制，也会导致某些流(flow)在切换过程中被去激活。
发明内容
鉴于上述技术问题，本公开实施例提供一种QoS处理方法和装置，避免目标基站在不能满足UE的一个或多个流的QoS参数时该一个或多个流会被直接去激活的问题。
依据本公开的实施例的一个方面，提供了一种服务质量QoS处理方法，所述方法包括：
目标基站向源基站发送第一消息，所述第一消息至少包括：用于通知源基站该目标基站不能满足UE的一个或多个流的QoS要求的第一信息和针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第二信息。
可选地，所述方法还包括：
所述目标基站向核心网发送第二消息，该第二消息包括用于通知核心网该目标基站不能满足所述UE的一个或多个流的QoS要求的第三信息。
可选地，所述第二消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第四信息。
可选地，所述方法还包括：
所述目标基站接收所述核心网发送的更新后的所述一个或多个流的QoS参数。
依据本公开实施例的第二个方面，还提供了一种QoS处理方法，所述方法包括：
源基站接收目标基站发送的第一消息，并获取所述第一消息中用于通知该源基站该目标基站不能满足UE的一个或多个流的QoS要求的第一信息；
所述源基站向核心网发送第三消息，该第三消息包括用于通知核心网所述目标基站不能满足所述UE的一个或多个流的QoS要求的第五信息；
其中，所述第一消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第二信息。
可选地，所述第三消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第六信息。
可选地，所述方法还包括：
所述源基站接收所述核心网发送的更新后的所述一个或多个流的QoS参数；
所述源基站根据所述更新后的所述一个或多个流的QoS参数，选择合适的目标基站重新发起切换过程。
依据本公开实施例的第三个方面，还提供了一种QoS处理方法，所述方法包括：
目标基站向核心网发送第四消息，该第四消息包括用于通知核心网该目标基站不能满足UE的一个或多个流的QoS需求的第七信息。
可选地，所述第四消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第八信息。
可选地，所述方法还包括：
所述目标基站接收核心网发送的更新后的所述一个或多个流的QoS参数。
可选地，所述方法还包括：
所述目标基站通过核心网接收所述源基站发送的切换请求消息。
依据本公开实施例的第四个方面，还提供了一种QoS处理方法，所述方法包括：
核心网接收目标基站发送的第四消息，该第四消息包括用于通知该核心网该目标基站不能满足UE的一个或多个流的QoS需求的第七信息。
可选地，所述第四消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第八信息。
可选地，所述方法还包括：
所述核心网向所述目标基站发送更新后的所述一个或多个流的QoS参数；
所述核心网接收所述目标基站发送的切换响应消息。
可选地，所述方法还包括：
所述核心网向所述源基站发送第五消息，所述第五消息中包括用于表示更新后的所述一个或多个流的QoS参数的第九信息。
依据本公开实施例的第五个方面，还提供了一种QoS处理装置，应用于目标基站，所述装置包括：
第一通知模块，用于向源基站发送第一消息，所述第一消息至少包括：用于通知源基站该目标基站不能满足UE的一个或多个流的QoS要求的第一信息和针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第二信息。
可选地，所述装置还包括：
第二通知模块，用于向核心网发送第二消息，该第二消息包括用于通知核心网该目标基站不能满足所述UE的一个或多个流的QoS要求的第三信息。
可选地，所述第二消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第四信息。
可选地，所述装置还包括：
第一接收模块，用于接收所述核心网发送的更新后的所述一个或多个流的QoS参数。
依据本公开实施例的第六个方面，还提供了一种QoS处理装置，应用于源基站，所述装置包括：
第二接收模块，用于接收目标基站发送的第一消息，并获取所述第一消息中用于通知该源基站该目标基站不能满足UE的一个或多个流的QoS要求的第一信息；
第三通知模块，用于向核心网发送第三消息，该第三消息中包括用于通知核心网所述目标基站不能满足所述UE的一个或多个流的QoS要求的第二信息；
其中，所述第一消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第二信息。
可选地，所述第三消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第六信息。
可选地，所述装置还包括：
第三接收模块，用于接收所述核心网发送的更新后的所述一个或多个流的QoS参数；
切换模块，用于根据所述更新后的所述一个或多个流的QoS参数，选择合适的目标基站重新发起切换过程。
依据本公开实施例的第七个方面，还提供了一种QoS处理装置，应用于目标基站，所述装置包括：
第四通知模块，用于向核心网发送第四消息，该第四消息中包括用于通知核心网该目标基站不能满足UE的一个或多个流的QoS需求的第七信息。
可选地，所述第四消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第八信息。
可选地，所述装置还包括：
第四接收模块，用于接收核心网发送的更新后的所述一个或多个流的QoS参数。
可选地，所述装置还包括：
第五接收模块，用于通过核心网接收所述源基站发送的切换请求消息。
依据本公开实施例的第八个方面还提供了一种QoS处理装置，应用于核心网，所述装置包括：
第六接收模块，用于接收目标基站发送的第四消息，该第四消息中包括用于通知该核心网该目标基站不能满足UE的一个或多个流的QoS需求的第七信息。
可选地，所述第四消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第八信息。
可选地，所述装置还包括：
第一发送模块，用于向所述目标基站发送更新后的所述一个或多个流的QoS参数；
第七接收模块，用于接收所述目标基站发送的切换响应消息。
可选地，所述装置还包括：
第二发送模块，用于向所述源基站发送第五消息，所述第五消息中携带有用于表示更新后的所述一个或多个流的QoS参数的第九信息。
依据本公开实施例的第九个方面还提供了一种基站，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如上所述QoS处理方法中的步骤。
依据本公开实施例的第十个方面，还提供了一种核心网侧设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如上所述QoS处理方法中的步骤。
依据本公开实施例的第十一个方面，还提供了一种计算机可读存储介质，其上存储有计算机程序(指令)，该程序(指令)被处理器执行时实现如上所述QoS处理方法中的步骤。
上述技术方案中的一个技术方案具有如下优点或有益效果：提供了在目标基站不能满足QoS需求时的处理流程，例如通过第一消息中携带的针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数，使得目标基站在通知源基站其不能满足UE的一个或多个流的QoS要求时，能同时通知源基 站其能够接纳的QoS参数，避免相关技术中源基站直接去激活目标基站不能接纳的承载，进而导致目标基站无法支持相应的业务的问题。
附图说明
为了更清楚地说明本公开实施例的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开中记载的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。以下附图并未刻意按实际尺寸等比例缩放绘制，重点在于示出本公开的主旨。
图1为相关的LTE系统中承载模型的结构示意图；
图2为相关的LTE架构示意图；
图3为5G系统的一种架构示意图；
图4为5G网络架构示意图；
图5为本公开的一个实施例中的QoS处理方法的流程图；
图6为本公开的另一个实施例中的QoS处理方法的流程图；
图7为本公开的一个实施例中的QoS处理方法的流程图；
图8为本公开的另一个实施例中的QoS处理方法的流程图；
图9为本公开的一个实施例中的QoS处理方法的流程图；
图10为本公开的另一个实施例中QoS处理方法的流程图；
图11为本公开的一个实施例中的QoS处理方法的流程图；
图12为本公开的另一个实施例中的QoS处理方法的流程图；
图13为本公开的一个实施例中的Xn切换过程，切换后通知核心网RAN(Radio Access Network，无线接入网)侧不能满足某些流的QoS要求的流程图；
图14为本公开的一个实施例中的Xn切换过程，切换前通知核心网RAN侧不能满足某些流的QoS要求的流程图；
图15为本公开的一个实施例中的NG切换过程中的流程图；
图16为本公开的一个实施例中的QoS处理装置的结构图；
图17为本公开的另一个实施例中的QoS处理装置的结构图；
图18为本公开的又一个实施例中的QoS处理装置的结构图；
图19为本公开的又一个实施例中的QoS处理装置的结构图；
图20为本公开的一个实施例中的目标基站的结构图；
图21为本公开的一个实施例中的源基站的结构图；
图22为本公开的另一个实施例中的目标基站的结构图；
图23为本公开的一个实施例中的核心网侧设备的结构图。
具体实施方式
下面将参照附图更详细地描述本公开的示例性实施例。虽然附图中显示了本公开的示例性实施例，然而应当理解，可以以各种形式实现本公开而不应被这里阐述的实施例所限制。相反，提供这些实施例是为了能够更透彻地理解本公开，并且能够将本公开的范围完整的传达给本领域的技术人员。
(1)相关的LTE系统中承载模型
参见图1，图中示出了相关的LTE系统中承载模型的结构。相关的LTE系统中核心网负责生成E-RAB(Evolved Radio Access Bearer，演进的无线接入承载)的QoS参数，由于空口RB(Radio Bearer，无线承载)与E-RAB是一一映射的关系，因此空口RB的QoS参数直接采用核心网生成的E-RAB QoS参数。
(2)RAN侧架构
本公开实施例可以用于不同的网络部署结构，为了描述方便，先介绍两种未来移动通信可能采用的网络部署结构。
部署结构一：基站+终端
参见图2，图中示出了典型的LTE架构。eNB(基站)下有多个小区(cell)，连接态下UE与小区进行空口数据收发。
部署结构二：网络侧节点分为中央单元(CU，Central Unit)和分布式单元(DU，Distributed Unit)，用户侧节点为终端
参见图3，图中示出了未来移动通信5G可能采用的一种架构，网络侧节点包括中央单元和分布式单元，一个中央单元控制一定区域内部署的多个分布式单元，这些分布式单元具体通过传输点(Transmission Reception Point，TRP)与终端进行空口传输。一个或多个传输点可以同时为终端服务，进行 数据传输。
本公开实施例适用于上述两种RAN架构。
5G网络架构如图4所示，网络架构中包括三个逻辑实体分别是位于核心网的CN-C(核心网控制面功能实体)，和CN-U(核心网用户面功能实体)；以及位于接入网的gNB(下一代基站)和eLTE eNB(演进LTE的基站)。其中CN-C与gNB建立NG-C接口用于控制面信令的传输；CN-U与gNB建立NG-U用于用户面数据传输。无线接入网g-NB之间建立Xn接口，Xn接口同时支持控制面(例如Xn-C)和用户面功能(例如Xn-U)。
其中NG-C上可建立以UE为粒度的控制面连接(其中每个UE对应的控制面连接可使用NG-AP ID进行标识)，在NG-U上建立以PDU session(PDU会话)为粒度的用户面连接(或者称为用户面隧道)，一个UE仅能同时保持一个与CN-C之间的NG-C连接，但是可以同时建立多个与CN-U在NG-U接口上的PDU Session(PDU会话)为粒度的用户面连接(或者称为用户面隧道)。在无线接入网可以有一个或多个gNB同时为UE提供服务。
未来5G核心网没有承载(Bearer)的概念，核心网CN-C下发给gNB的QoS参数是以流为粒度配置的。另一方面由于接入网gNB仍然以RB(无线承载)为粒度进行QoS管理，因此接入网需要生成RB级别的QoS参数用于gNB与UE以及gNB与其他无线接入实体之间的交互过程。
包括参见图5，图中示出了一个实施例中的QoS处理方法，具体步骤如下：
步骤501、目标基站向源基站发送第一消息，所述第一消息至少包括：用于通知源基站其不能满足终端(UE)的一个或多个流的QoS要求的第一信息和还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第二信息。
例如，在Xn切换过程中，目标基站在切换响应消息中通知源基站该目标基站不能满足QoS需求的流列表(flow list)，并且还可以携带针对这些流推荐的QoS参数。源基站可以参考针对这些流推荐的QoS参数决定符合该QoS要求的目标基站。
在本实施例中，通过第一消息中携带的针对所述一个或多个流推荐的所 述目标基站能够接纳的QoS参数，使得目标基站在通知源基站其不能满足UE的一个或多个流的QoS要求时，能同时通知源基站其能够接纳的QoS参数，避免相关技术中源基站直接去激活目标基站不能接纳的承载，进而导致目标基站无法支持相应的业务。
参见图6，图中示出了另一个实施例中的QoS处理方法，具体流程，所述方法包括：
步骤601、目标基站向源基站发送第一消息，所述第一消息至少包括：用于通知源基站其不能满足终端(UE)的一个或多个流的QoS要求的第一信息和用于表示针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第二信息还包括。
例如，在Xn切换过程中，目标基站在切换响应消息中通知源基站该目标基站不能满足QoS需求的流列表，并且还可以携带针对这些流推荐的QoS参数。
步骤602、目标基站向核心网发送第二消息，该第二消息包括用于通知核心网该目标基站不能满足所述UE的一个或多个流的QoS要求的第三信息。
例如，在源基站基于步骤601中的第一消息选择合适的目标小区，切换完成后，目标基站可以通知核心网RAN侧不能满足某个或某些流的QoS需求。
可选地，所述第二消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第四信息。
继续参见图6，可选地，该方法还包括：
步骤603、目标基站接收所述核心网发送的更新后的一个或多个流的QoS参数。
上述核心网能够基于第二消息中携带的针对一个或多个流推荐的目标基站能够接纳的QoS参数对一个或多个流的QoS参数进行更新。
在本实施例中提供了在目标基站不能满足QoS需求时的处理流程。通过第一消息中携带的针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数，使得目标基站在通知源基站其不能满足UE的一个或多个流的QoS要求时，能同时通知源基站其能够接纳的QoS参数，避免相关技术中源基站 直接去激活目标基站不能接纳的承载，进而导致目标基站无法支持相应的业务。
需要说明的是，图5和图6所示的流程可以适用于切换场景，当然也并不限于此。
参见图7，图中示出了一个实施例中的QoS处理方法的流程，具体步骤如下：
步骤701、源基站接收目标基站发送的第一消息，并获取第一消息中的用于表示目标基站不能满足UE的一个或多个流的QoS要求的第一信息；
其中，第一消息中还包括用于表示针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第二信息。
例如，在Xn切换过程中，目标基站在切换响应消息中通知源基站该目标基站不能满足QoS需求的流列表，并且还可以携带针对这些流推荐的QoS参数。
步骤702、源基站向核心网发送第三消息，该第三消息包括用于通知核心网所述目标基站不能满足所述UE的一个或多个流的QoS要求的第五信息还包括。
在本实施例中，可选地，所述第三消息中还包括用于表示针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第六信息。
在本实施例中提供了在目标基站不能满足QoS需求时的处理流程。通过第一消息中携带的针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数，使得目标基站在通知源基站其不能满足UE的一个或多个流的QoS要求时，能同时通知源基站其能够接纳的QoS参数，避免相关技术中源基站直接去激活目标基站不能接纳的承载，进而导致目标基站无法支持相应的业务。
参见图8，图中示出了另一个实施例中的QoS处理方法的流程，具体步骤如下：
步骤801、源基站接收第一消息，并获取该第一消息中用于表示目标基站不能满足UE的一个或多个流的QoS要求的第一信息；其中，第一消息中还包括用于表示针对所述一个或多个流推荐的目标基站能够接纳的QoS参数 的第二信息。
例如，在Xn切换过程中，目标基站在切换响应消息中通知源基站该目标基站不能满足QoS需求的流列表，并且还可以携带针对这些流推荐的QoS参数。
步骤802、源基站向核心网发送第三消息，该第三消息包括用于通知核心网所述目标基站不能满足所述UE的一个或多个流的QoS要求的第五信息。在本实施例中，可选地，所述第三消息中还包括用于表示针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第六信息。
步骤803、源基站接收核心网发送的更新后的一个或多个流的QoS参数；
步骤804、源基站根据更新后的一个或多个流的QoS参数，选择合适的目标基站重新发起切换过程。
在本实施例中提供了在目标基站不能满足QoS需求时的处理流程。通过第一消息中携带的针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数，使得目标基站在通知源基站其不能满足UE的一个或多个流的QoS要求时，能同时通知源基站其能够接纳的QoS参数，避免相关技术中源基站直接去激活目标基站不能接纳的承载，进而导致目标基站无法支持相应的业务。
进一步地，源基站还可以根据更新后的一个或多个流的QoS参数，选择合适的目标基站重新发起切换过程，完善了整个切换的流程，确保UE的一个或多个流的QoS要求能够被目标基站接纳。
需要说明的是，图5和图6所示的流程可以适用于切换场景，当然也并不限于此。
参见图9，图中示出了一个实施例中的QoS处理方法的流程，具体步骤如下：
步骤901、目标基站向核心网发送第四消息，该第四消息包括用于通知核心网该目标基站不能满足UE的一个或多个流的QoS需求的第七信息。
在本实施例中，可选地，所述第四消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第八信息。
可选地，在步骤901之后，目标基站接收核心网发送的更新后的一个或 多个流的QoS参数。
可选地，目标基站接收到更新后的一个或多个流的QoS参数之后，目标基站可以向核心网发送切换响应，然后核心网在给源基站的切换响应中携带更新后的QoS参数，再然后，源基站给UE发送切换命令，UE接入到目标小区。
需要说明的是，图9所示的QoS处理的流程可以适用于切换场景，也可以适用于PDU会话建立过程。
在PDU会话建立过程的场景中，上述目标基站也可以称为UE的服务基站，如果UE的服务基站不能满足PDU会话下一个或多个流的QoS要求，UE的服务基站也可以通过一条消息通知核心网其不能满足UE的一个或多个流的QoS要求。
参见图10，图中示出了另一个实施例中QoS处理方法的流程，具体步骤如下：
步骤1001、目标基站通过核心网接收所述源基站发送的切换请求消息。
步骤1002、目标基站向核心网发送第四消息，该第四消息包括用于通知核心网该目标基站不能满足UE的一个或多个流的QoS需求的第七信息。
在本实施例中，可选地，所述第四消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第八信息。
步骤1003、目标基站接收核心网发送的更新后的所述一个或多个流的QoS参数。
在本实施例中提供了在目标基站不能满足QoS需求时的处理流程。通过第四消息中携带的针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数，使得目标基站在不能满足UE的一个或多个流的QoS要求时，能通知核心网其能够接纳的QoS参数，以及目标基站还可以接收核心网发送的更新后的所述一个或多个流的QoS参数，避免相关技术中源基站直接去激活目标基站不能接纳的承载，进而导致目标基站无法支持相应的业务。
进一步地，源基站还可以根据更新后的一个或多个流的QoS参数，选择合适的目标基站重新发起切换过程，完善了整个切换的流程，确保UE的一个或多个流的QoS要求能够被目标基站接纳。
参见图11，图中示出了一个实施例中的QoS处理方法的流程，具体步骤如下：
步骤1101、核心网接收目标基站发送的第四消息，获取该第四消息中的用于通知核心网该目标基站不能满足UE的一个或多个流的QoS需求的第七信息。
在本实施例中，可选地，第四消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第八信息。
在本实施例中提供了在目标基站不能满足QoS需求时的处理流程。通过第四消息中携带的针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数，使得目标基站在不能满足UE的一个或多个流的QoS要求时，能通知核心网其能够接纳的QoS参数。
参见图12，图中示出了另一个实施例中的QoS处理方法的流程，具体步骤如下：
步骤1201、核心网接收目标基站发送的第四消息，并获取该第四消息中用于通知核心网该目标基站不能满足UE的一个或多个流的QoS需求的第七信息。
在本实施例中，可选地，第四消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第八信息。
步骤1202、核心网向目标基站发送更新后的一个或多个流的QoS参数。
步骤1203、核心网接收目标基站发送的切换响应消息。
步骤1204、核心网向源基站发送第五消息，所述第五消息中携带更新后的所述一个或多个流的QoS参数。
源基站接收到更新后的所述一个或多个流的QoS参数之后，源基站可以UE发送切换命令，UE接入到目标小区。
需要说明的是，图11和图12所示的流程可以适用于NG切换过程。即，在NG切换过程中，目标基站通知核心网一个或多个流的QoS参数要求不能满足，进一步地，还可以提供推荐的QoS参数。
在本实施例中提供了在目标基站不能满足QoS需求时的处理流程。通过第四消息中携带的针对所述一个或多个流推荐的所述目标基站能够接纳的 QoS参数，使得目标基站在不能满足UE的一个或多个流的QoS要求时，能通知核心网其能够接纳的QoS参数。
在一些实施例中，在Xn切换过程中，如果目标基站根据自身的负荷等情况判断自己不能满足UE的某些流的QoS要求，给源基站一个指示，同时，目标基站也可以携带该流的推荐的QoS参数，源基站可以参考该信息决定最后的目标小区。切换完成后，目标基站通知核心网该UE的某些流的QoS需求不能得到满足。同时，也可以携带推荐的该流的QoS参数。核心网根据该信息更新该流的QoS参数并下发给目标基站。
具体地，Xn切换过程，切换后通知核心网RAN侧不能满足某些流的QoS要求，具体流程可参见图13。
步骤1301、源基站(源节点(Source node))向多个目标基站(目标小区(Target cell)1和目标小区(Target cell)2)发送切换请求消息(切换请求(Handover request))。
步骤1302、目标基站根据流的QoS参数进行接纳控制，并在切换请求响应消息(Handover request ACK1和Handover request ACK2)中返回成功接纳的流信息和不能满足QoS需求的流(只适用于通知控制(Notification Control)特性的流)的信息，以及接纳失败的流的信息。
对于可以进行通知控制的流，如果目标基站不能满足该流的QoS需求，可以在响应消息中携带指示以及推荐的本基站(Target cell1或Target cell2)可以接纳的QoS参数。
步骤1303、源基站根据收到的响应消息选择最后的目标小区(选择适当的目标小区(Select the proper target cell))，给其他目标小区发送切换取消消息(切换取消(Handover cancel))。
步骤1304、源基站给UE发送切换命令(Handover command)，UE接入到目标小区(UE access to the target cell)。
步骤1305、目标基站在给核心网的路径切换(path switch)消息中指示不能满足某些流的QoS需求，核心网可以更新QoS参数并在路径切换回复(path switch ACK)消息中通知目标基站。
在一些实施例中，Xn切换过程中，如果目标基站根据自身的load等情况 判断自己不能满足UE某些流的QoS要求，给源基站一个指示，同时，目标基站也可以携带自己可以接纳的该流的QoS参数，源基站收到该指示后，通知核心网，然后核心网将更新后的该流的QoS参数发给源基站。源基站根据目标基站提供信息选择目标小区，重新向目标基站发起切换过程。
具体地，Xn切换过程，切换前通知核心网RAN侧不能满足某些流的QoS要求，具体流程可参见图14。
步骤1401、源基站(源节点(Source node))向多个目标基站(目标小区(Target cell)1和目标小区(Target cell)2)发送切换请求消息(切换请求(Handover request))。
步骤1402、目标基站根据流的QoS参数进行接纳控制，并在切换请求响应消息(Handover request ACK)中返回成功接纳的流信息和不能满足QoS需求的流(只适用于通知控制特性的流)的信息，以及接纳失败的流的信息。对于可以进行通知控制的流，如果目标基站不能满足该流的QoS需求，可以在响应消息中携带指示以及推荐的本基站可以接纳的QoS参数。
步骤1403、源基站给核心网发送RAN侧不能满足QoS需求的指示。
步骤1404、核心网更新UE的QoS参数发送给基站(CN更新QoS参数(CN update the QoS parameter))。
步骤1405、源基站选择合适的目标小区发起切换过程，切换请求消息中携带更新后的QoS参数。
步骤1406、源基站给UE发送切换命令，UE接入到目标小区
步骤1407、目标基站向核心网发起路径切换的过程。
在一些实施例中，NG切换过程中，如果目标基站在收到来自核心网的切换请求后，根据自身的负荷等情况判断自己不能满足UE的某些流的QoS要求，给核心网一个指示，同时，目标基站也可以携带自己对于该流推荐的QoS参数，核心网可以调整该流的QoS参数并同时发给源基站和目标基站。源基站在发给UE的切换命令中携带更新后的QoS参数，具体流程可参见图15。
步骤1501、源基站通过CN向目标基站发送切换请求(Handover request)消息。
步骤1502、目标基站通知CN某些流的QoS参数要求RAN侧不能满足。
步骤1503、核心网把更新后的QoS参数发送给目标基站。
步骤1504、目标基站发送切换请求回复(handover request ACK)消息给核心网。
步骤1505、核心网在给源基站的切换响应消息中携带更新后的QoS参数。
步骤1506、源基站给UE发送切换命令，UE接入到目标小区。
基于同一发明构思，本公开实施例中还提供了一种QoS处理装置，由于该装置解决问题的原理与本公开实施例图5、图6中QoS处理方法相似，因此该装置的实施可以参见方法的实施，重复之处不再敷述。
参见图16，图中示出了一个实施例中的QoS处理装置，该装置1600应用于目标基站，装置1600包括：
第一通知模块1601，用于通过第一消息通知源基站其不能满足UE的一个或多个流的QoS要求，其中，第一消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数。
在本实施例中，可选地，所述装置1600还包括：
第二通知模块1602，用于通过第二消息通知核心网其不能满足所述UE的一个或多个流的QoS要求。
在本实施例中，可选地，所述第二消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数。
在本实施例中，可选地，所述装置1600还包括：
第一接收模块1603，用于接收所述核心网发送的更新后的所述一个或多个流的QoS参数。
基于同一发明构思，本公开实施例中还提供了一种QoS处理装置，由于该装置解决问题的原理与本公开实施例图7、图8中QoS处理方法相似，因此该装置的实施可以参见方法的实施，重复之处不再敷述。
参见图17，图中示出了另一个实施例中的QoS处理装置，该装置1700应用于源基站，装置1700包括：
第二接收模块1701，用于通过第一消息获知目标基站不能满足UE的一个或多个流的QoS要求；
第三通知模块1702，用于通过第三消息通知核心网所述目标基站不能满 足所述UE的一个或多个流的QoS要求；
其中，所述第一消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数。
在本实施例中，可选地，所述第三消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数。
在本实施例中，可选地，所述装置1700还包括：
第三接收模块1703，用于接收所述核心网发送的更新后的所述一个或多个流的QoS参数；
切换模块1704，用于根据所述更新后的所述一个或多个流的QoS参数，选择合适的目标基站重新发起切换过程。
基于同一发明构思，本公开实施例中还提供了一种QoS处理装置，由于该装置解决问题的原理与本公开实施例图9、图10中QoS处理方法相似，因此该装置的实施可以参见方法的实施，重复之处不再敷述。
参见图18，图中示出了又一个实施例中的QoS处理装置，该装置1800应用于目标基站，包括：
第四通知模块1801，用于通过第四消息通知核心网其不能满足UE的一个或多个流的QoS需求。
在本实施例中，可选地，所述第四消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数。
在本实施例中，可选地，所述装置1800还包括：
第四接收模块1802，用于接收核心网发送的更新后的所述一个或多个流的QoS参数。
在本实施例中，可选地，所述装置1800还包括：
第五接收模块1803，用于通过核心网接收所述源基站发送的切换请求消息。
基于同一发明构思，本公开实施例中还提供了一种QoS处理装置，由于该装置解决问题的原理与本公开实施例图11、图12中QoS处理方法相似，因此该装置的实施可以参见方法的实施，重复之处不再敷述。
参见图19，图中示出了又一个实施例中的QoS处理装置，QoS处理装置 1900应用于核心网，包括：
第六接收模块1901，用于接收目标基站发送的第四消息，通过所述第四消息获知所述目标基站不能满足UE的一个或多个流的QoS需求。
在本实施例中，可选地，所述第四消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数。
在本实施例中，可选地，所述装置还包括：
第一发送模块1902，用于向所述目标基站发送更新后的所述一个或多个流的QoS参数；
第七接收模块1903，用于接收所述目标基站发送的切换响应消息。
在本实施例中，可选地，所述装置还包括：
第二发送模块1904，用于向所述源基站发送第五消息，所述第五消息中携带更新后的所述一个或多个流的QoS参数。
参见图20，本公开实施例提供了一种目标基站，包括：
第一处理器2004，用于读取第一存储器2005中的程序，执行下列过程：
向源基站发送第一消息，所述第一消息至少包括：用于通知源基站该目标基站不能满足UE的一个或多个流的QoS要求的第一信息和针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第二信息。
第一收发机2001，用于在第一处理器2004的控制下接收和发送数据。
在图20中，总线架构(用第一总线2000来代表)可以包括任意数量的互联的总线和桥，第一总线2000将包括由第一处理器2004代表的一个或多个处理器和第一存储器2005代表的存储器的各种电路链接在一起。第一总线2000还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起。第一总线接口2003在第一总线2000和第一收发机2001之间提供接口。第一收发机2001可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经第一处理器2004处理的数据通过第一收发机2001和第一天线2002在无线介质上进行传输，进一步，第一天线2002还接收数据并将数据经由第一收发机2001传送给第一处理器2004。
第一处理器2004负责管理第一总线2000和通常的处理，还可以提供各 种功能，包括定时，外围接口，电压调节、电源管理以及其他控制功能。而第一存储器2005可以被用于存储第一处理器2004在执行操作时所使用的数据。具体的，第一处理器2004可以是CPU、ASIC(Application Specific Integrated Circuit，专用集成电路)、FPGA(Field－Programmable Gate Array，现场可编程门阵列)，或CPLD(Complex Programmable Logic Device，复杂可编程逻辑器件)。
所述目标基站向核心网发送第二消息，该第二消息包括用于通知核心网该目标基站不能满足所述UE的一个或多个流的QoS要求的第三信息。
可选地，所述第二消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第四信息。
可选地，第一处理器2004还用于接收所述核心网发送的更新后的所述一个或多个流的QoS参数。
参见图21，本公开实施例提供了一种源基站，包括：
第二处理器2104，用于读取第二存储器2105中的程序，执行下列过程：
接收目标基站发送的第一消息，并获取所述第一消息中用于通知该源基站该目标基站不能满足UE的一个或多个流的QoS要求的第一信息；向核心网发送第三消息，该第三消息包括用于通知核心网所述目标基站不能满足所述UE的一个或多个流的QoS要求的第五信息；其中，所述第一消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第二信息。
第二收发机2101，用于在第二处理器2104的控制下接收和发送数据。
在图21中，总线架构(用第二总线2100来代表)可以包括任意数量的互联的总线和桥，第二总线2100将包括由第二处理器2104代表的一个或多个处理器和第二存储器2105代表的存储器的各种电路链接在一起。第二总线2100还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起。第二总线接口2103在第二总线2100和第二收发机2101之间提供接口。第二收发机2101可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经第二处理器2104处理的数据通过第二收发机2101和第二天线2102在无线介质上 进行传输，进一步，第二天线2102还接收数据并将数据经由第二收发机2101传送给第二处理器2104。
第二处理器2104负责管理第二总线2100和通常的处理，还可以提供各种功能，包括定时，外围接口，电压调节、电源管理以及其他控制功能。而第二存储器2105可以被用于存储第二处理器2104在执行操作时所使用的数据。具体的，第二处理器2104可以是CPU、ASIC(Application Specific Integrated Circuit，专用集成电路)、FPGA(Field－Programmable Gate Array，现场可编程门阵列)，或CPLD(Complex Programmable Logic Device，复杂可编程逻辑器件)。
可选地，所述第三消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第六信息。
可选地，第二处理器2104还用于接收所述核心网发送的更新后的所述一个或多个流的QoS参数；根据所述更新后的所述一个或多个流的QoS参数，选择合适的目标基站重新发起切换过程。
参见图22，本公开实施例提供了一种目标基站，包括：
第三处理器2204，用于读取第三存储器2205中的程序，执行下列过程：
向核心网发送第四消息，该第四消息包括用于通知核心网该目标基站不能满足UE的一个或多个流的QoS需求的第七信息。
第三收发机2201，用于在第三处理器2204的控制下接收和发送数据。
在图22中，总线架构(用第三总线2200来代表)可以包括任意数量的互联的总线和桥，第三总线2200将包括由第三处理器2204代表的一个或多个处理器和第三存储器2205代表的存储器的各种电路链接在一起。第三总线2200还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起。第三总线接口2203在第三总线2200和第三收发机2201之间提供接口。第三收发机2201可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经第三处理器2204处理的数据通过第三收发机2201和第三天线2202在无线介质上进行传输，进一步，第三天线2202还接收数据并将数据经由第三收发机2201传送给第三处理器2204。
第三处理器2204负责管理第三总线2200和通常的处理，还可以提供各种功能，包括定时，外围接口，电压调节、电源管理以及其他控制功能。而第三存储器2205可以被用于存储第三处理器2204在执行操作时所使用的数据。具体的，第三处理器2204可以是CPU、ASIC(Application Specific Integrated Circuit，专用集成电路)、FPGA(Field－Programmable Gate Array，现场可编程门阵列)，或CPLD(Complex Programmable Logic Device，复杂可编程逻辑器件)。
可选地，所述第四消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第八信息。
可选地，第三处理器2204还用于接收核心网发送的更新后的所述一个或多个流的QoS参数。
可选地，第三处理器2204还用于通过核心网接收所述源基站发送的切换请求消息。
参见图23，本公开实施例提供了一种核心网侧设备，包括：
第四处理器2304，用于读取第四存储器2305中的程序，执行下列过程：
接收目标基站发送的第四消息，该第四消息包括用于通知该核心网侧设备该目标基站不能满足UE的一个或多个流的QoS需求的第七信息。
在图23中，总线架构(用第四总线2300来代表)可以包括任意数量的互联的总线和桥，第四总线2300将包括由第四处理器2304代表的一个或多个处理器和第四存储器2305代表的存储器的各种电路链接在一起。第四总线2300还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起。第四总线接口2303在第四总线2300和第四收发机2301之间提供接口。第四收发机2301可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经第四处理器2304处理的数据通过第四收发机2301和第四天线2302在无线介质上进行传输，进一步，第四天线2302还接收数据并将数据经由第四收发机2301传送给第四处理器2304。
第四处理器2304负责管理第四总线2300和通常的处理，还可以提供各种功能，包括定时，外围接口，电压调节、电源管理以及其他控制功能。而 第四存储器2305可以被用于存储第三处理器2204在执行操作时所使用的数据。具体的，第四处理器2304可以是CPU、ASIC(Application Specific Integrated Circuit，专用集成电路)、FPGA(Field－Programmable Gate Array，现场可编程门阵列)，或CPLD(Complex Programmable Logic Device，复杂可编程逻辑器件)。
可选地，所述第四消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第八信息。
可选地，第四处理器2304还用于向所述目标基站发送更新后的所述一个或多个流的QoS参数；接收所述目标基站发送的切换响应消息。
可选地，第四处理器2304还用于向所述源基站发送第五消息，所述第五消息中包括用于表示更新后的所述一个或多个流的QoS参数的第九信息。
本公开实施例还提供了一种计算机可读存储介质，其上存储有计算机程序(指令)，该程序(指令)被处理器执行时实现如图5、图6、图7、图8、图9、图10、图11或图12中所示的QoS处理方法中的步骤。
应理解，说明书通篇中提到的“一个实施例”或“一实施例”意味着与实施例有关的特定特征、结构或特性包括在本公开的至少一个实施例中。因此，在整个说明书各处出现的“在一个实施例中”或“在一实施例中”未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。
在本公开的各种实施例中，应理解，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本公开实施例的实施过程构成任何限定。
另外，本文中术语“系统”和“网络”在本文中常可互换使用。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
在本申请所提供的实施例中，应理解，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确 定B，还可以根据A和/或其它信息确定B。
在本申请所提供的几个实施例中，应该理解到，所揭露方法和装置，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
另外，在本公开各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理包括，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
上述以软件功能单元的形式实现的集成的单元，可以存储在一个计算机可读取存储介质中。上述软件功能单元存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络侧设备等)执行本公开各个实施例所述收发方法的部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述的是本公开的优选实施方式，应当指出对于本技术领域的普通人员来说，在不脱离本公开所述的原理前提下还可以做出若干改进和润饰，这些改进和润饰也在本公开的保护范围内。

Claims (33)

  1. 一种服务质量(Quality of Service，QoS)处理方法，包括：
    目标基站向源基站发送第一消息，所述第一消息至少包括：用于通知源基站该目标基站不能满足终端的一个或多个流的QoS要求的第一信息和针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第二信息。
  2. 根据权利要求1所述的方法，还包括：
    所述目标基站向核心网发送第二消息，该第二消息包括用于通知核心网该目标基站不能满足所述终端的一个或多个流的QoS要求的第三信息。
  3. 根据权利要求2所述的方法，其中，所述第二消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第四信息。
  4. 根据权利要求3所述的方法，还包括：
    所述目标基站接收所述核心网发送的更新后的所述一个或多个流的QoS参数。
  5. 一种QoS处理方法，包括：
    源基站接收目标基站发送的第一消息，并获取所述第一消息中用于通知该源基站该目标基站不能满足终端的一个或多个流的QoS要求的第一信息；
    所述源基站向核心网发送第三消息，该第三消息包括用于通知核心网所述目标基站不能满足所述终端的一个或多个流的QoS要求的第五信息；
    其中，所述第一消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第二信息。
  6. 根据权利要求5所述的方法，其中，所述第三消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第六信息。
  7. 根据权利要求5所述的方法，还包括：
    所述源基站接收所述核心网发送的更新后的所述一个或多个流的QoS参数；
    所述源基站根据所述更新后的所述一个或多个流的QoS参数，选择合适的目标基站重新发起切换过程。
  8. 一种QoS处理方法，包括：
    目标基站向核心网发送第四消息，该第四消息包括用于通知核心网该目标基站不能满足终端的一个或多个流的QoS需求的第七信息。
  9. 根据权利要求8所述的方法，其中，所述第四消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第八信息。
  10. 根据权利要求9所述的方法，还包括：
    所述目标基站接收核心网发送的更新后的所述一个或多个流的QoS参数。
  11. 根据权利要求8所述的方法，还包括：
    所述目标基站通过核心网接收源基站发送的切换请求消息。
  12. 一种QoS处理方法，包括：
    核心网接收目标基站发送的第四消息，该第四消息包括用于通知该核心网该目标基站不能满足终端的一个或多个流的QoS需求的第七信息。
  13. 根据权利要求12所述的方法，其中，所述第四消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第八信息。
  14. 根据权利要求13所述的方法，还包括：
    所述核心网向所述目标基站发送更新后的所述一个或多个流的QoS参数；
    所述核心网接收所述目标基站发送的切换响应消息。
  15. 根据权利要求14所述的方法，还包括：
    所述核心网向源基站发送第五消息，所述第五消息中包括用于表示更新后的所述一个或多个流的QoS参数的第九信息。
  16. 一种QoS处理装置，应用于目标基站，其中，所述装置包括：
    第一通知模块，用于向源基站发送第一消息，所述第一消息至少包括：用于通知源基站该目标基站不能满足终端的一个或多个流的QoS要求的第一信息和针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第二信息。
  17. 根据权利要求16所述的装置，还包括：
    第二通知模块，用于向核心网发送第二消息，该第二消息包括用于通知核心网该目标基站不能满足所述终端的一个或多个流的QoS要求的第三信 息。
  18. 根据权利要求17所述的装置，其中，所述第二消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第四信息。
  19. 根据权利要求18所述的装置，还包括：
    第一接收模块，用于接收所述核心网发送的更新后的所述一个或多个流的QoS参数。
  20. 一种QoS处理装置，应用于源基站，其中，所述装置包括：
    第二接收模块，用于接收目标基站发送的第一消息，并获取所述第一消息中用于通知该源基站该目标基站不能满足终端的一个或多个流的QoS要求的第一信息；
    第三通知模块，用于向核心网发送第三消息，该第三消息中包括用于通知核心网所述目标基站不能满足所述终端的一个或多个流的QoS要求的第二信息；
    其中，所述第一消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第二信息。
  21. 根据权利要求20所述的装置，其中，所述第三消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第六信息。
  22. 根据权利要求20所述的装置，还包括：
    第三接收模块，用于接收所述核心网发送的更新后的所述一个或多个流的QoS参数；
    切换模块，用于根据所述更新后的所述一个或多个流的QoS参数，选择合适的目标基站重新发起切换过程。
  23. 一种QoS处理装置，应用于目标基站，其中，所述装置包括：
    第四通知模块，用于向核心网发送第四消息，该第四消息中包括用于通知核心网该目标基站不能满足终端的一个或多个流的QoS需求的第七信息。
  24. 根据权利要求23所述的装置，其中，所述第四消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第八信息。
  25. 根据权利要求24所述的装置，还包括：
    第四接收模块，用于接收核心网发送的更新后的所述一个或多个流的 QoS参数。
  26. 根据权利要求23所述的装置，还包括：
    第五接收模块，用于通过核心网接收源基站发送的切换请求消息。
  27. 一种QoS处理装置，应用于核心网，其中，所述装置包括：
    第六接收模块，用于接收目标基站发送的第四消息，该第四消息中包括用于通知该核心网该目标基站不能满足终端的一个或多个流的QoS需求的第七信息。
  28. 根据权利要求27所述的装置，其中，所述第四消息中还包括针对所述一个或多个流推荐的所述目标基站能够接纳的QoS参数的第八信息。
  29. 根据权利要求28所述的装置，还包括：
    第一发送模块，用于向所述目标基站发送更新后的所述一个或多个流的QoS参数；
    第七接收模块，用于接收所述目标基站发送的切换响应消息。
  30. 根据权利要求29所述的装置，还包括：
    第二发送模块，用于向源基站发送第五消息，所述第五消息中携带有用于表示更新后的所述一个或多个流的QoS参数的第九信息。
  31. 一种基站，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其中，所述处理器执行所述计算机程序时实现如权利要求1～4任一项所述QoS处理方法中的步骤，或者实现如权利要求5～7任一项所述QoS处理方法中的步骤，或者实现如权利要求8～11任一项所述QoS处理方法中的步骤。
  32. 一种核心网侧设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其中，所述处理器执行所述计算机程序时实现如权利要求12～15任一项所述QoS处理方法中的步骤。
  33. 一种计算机可读存储介质，其上存储有计算机程序，其中，该计算机程序被处理器执行时实现权利要求1～4任一项所述QoS处理方法中的步骤，或者实现如权利要求5～7任一项所述QoS处理方法中的步骤，或者实现如权利要求8～11任一项所述QoS处理方法中的步骤，或者实现如权利要求12～15任一项所述QoS处理方法中的步骤。
PCT/CN2018/077260 2017-03-24 2018-02-26 一种QoS处理方法和装置 WO2018171386A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US16/496,944 US11190984B2 (en) 2017-03-24 2018-02-26 Quality of service processing method and device
EP18771369.8A EP3606171A4 (en) 2017-03-24 2018-02-26 QOS PROCESSING METHOD AND DEVICE

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710182683.0 2017-03-24
CN201710182683.0A CN108632909B (zh) 2017-03-24 2017-03-24 一种QoS处理方法和装置

Publications (1)

Publication Number Publication Date
WO2018171386A1 true WO2018171386A1 (zh) 2018-09-27

Family

ID=63584992

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/077260 WO2018171386A1 (zh) 2017-03-24 2018-02-26 一种QoS处理方法和装置

Country Status (4)

Country Link
US (1) US11190984B2 (zh)
EP (1) EP3606171A4 (zh)
CN (1) CN108632909B (zh)
WO (1) WO2018171386A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020045896A1 (en) * 2018-08-27 2020-03-05 Lg Electronics Inc. Method and apparatus for enhancing handover procedure for supporting conditional handover in wireless communication system
EP3973721B1 (en) * 2019-06-17 2023-12-20 Huawei Technologies Co., Ltd. Potential qos change notification methods and nodes for assisting application adjustment

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1951035A (zh) * 2004-05-07 2007-04-18 三星电子株式会社 在宽带无线接入通信系统中执行快速移交的系统和方法
CN107734563A (zh) * 2016-08-12 2018-02-23 电信科学技术研究院 切换场景下的QoS参数处理的方法及设备

Family Cites Families (46)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005025092A1 (en) * 2003-09-04 2005-03-17 Samsung Electronics Co., Ltd. System and method for selecting a serving base station according to a drop of a mobile subscriber station in a broadband wireless access communication system
KR101084113B1 (ko) * 2004-03-05 2011-11-17 엘지전자 주식회사 이동통신의 핸드오버에 적용되는 서비스 정보 전달 방법
US7233583B2 (en) * 2004-06-28 2007-06-19 Nokia Corporation Method and apparatus providing context transfer for inter-BS and inter-PCF handoffs in a wireless communication system
DE602004029017D1 (de) * 2004-07-02 2010-10-21 Alcatel Lucent Mechanismus für das Weiterreichen für mobile IP-Protokolle
US7369856B2 (en) * 2004-11-24 2008-05-06 Intel Corporation Method and system to support fast hand-over of mobile subscriber stations in broadband wireless networks
US8090369B2 (en) * 2007-05-01 2012-01-03 Qualcomm Incorporated User equipment capability handling in long-term evolution systems
KR20090023050A (ko) * 2007-08-29 2009-03-04 삼성전자주식회사 광대역 통신시스템에서 부하균등을 위한 방법 및 장치
KR101422007B1 (ko) * 2007-09-18 2014-07-23 엘지전자 주식회사 광대역 무선 접속 시스템에서 대역 핸드오버를 수행하는방법 및 이를 지원하는 이동 단말
GB2454204A (en) * 2007-10-31 2009-05-06 Nec Corp Core network selecting security algorithms for use between a base station and a user device
CN101472304B (zh) * 2007-12-24 2010-05-12 华为技术有限公司 一种ms的切换方法、系统和装置
KR101572882B1 (ko) * 2008-01-25 2015-11-30 엘지전자 주식회사 핸드오버 지연시간 감소 기법
RU2479947C2 (ru) * 2008-04-04 2013-04-20 Нокиа Сименс Нетуоркс Ой Время действия для хэндовера мобильных станций
US20100041387A1 (en) * 2008-08-15 2010-02-18 Amit Khetawat Method and Apparatus for Inter Home Node B Cell Update Handling
WO2010031441A1 (en) * 2008-09-19 2010-03-25 Nokia Siemens Networks Oy Network apparatus and method for transmitting a message to a target network apparatus in the wimax system
US20100091739A1 (en) * 2008-10-14 2010-04-15 Qualcomm Incorporated Methods and systems for pre-allocating a cqi channel during handoff
CN101827451B (zh) * 2009-03-03 2012-12-12 华为技术有限公司 中继节点的入网方法及装置
CN101873620B (zh) * 2009-04-22 2015-01-28 中兴通讯股份有限公司 小区间的重选参数和切换参数匹配的判断方法及装置
CN101990221A (zh) * 2009-08-07 2011-03-23 中兴通讯股份有限公司 一种传输小区切换信息的方法及基站
CN106028405A (zh) * 2010-01-13 2016-10-12 中兴通讯股份有限公司 一种实现小区重选参数协商的方法及基站
CN101778431B (zh) * 2010-02-02 2015-08-12 中兴通讯股份有限公司 一种基站系统中用户接入的接纳控制方法和装置
CN102111805B (zh) * 2010-06-18 2016-12-28 电信科学技术研究院 多载波系统的测量配置和上报方法及设备
EP2659709A1 (en) * 2010-12-28 2013-11-06 Nokia Siemens Networks Oy Relay node configuration in preparation for handover
CN103718604A (zh) * 2011-06-21 2014-04-09 诺基亚公司 提供优化的切换预备和执行操作的方法、装置和计算机程序产品
CN103379660B (zh) * 2012-04-28 2017-04-26 华为技术有限公司 自组织网络功能选择的方法、装置和系统
CN109905904B (zh) * 2012-06-29 2022-05-03 北京三星通信技术研究有限公司 一种接入控制方法
CN102833802B (zh) * 2012-08-15 2015-09-23 电信科学技术研究院 一种数据转发方法及设备
GB2506913B (en) * 2012-10-12 2015-06-17 Broadcom Corp Apparatus and method for use in a communication network
CN103916917B (zh) * 2013-01-06 2018-08-07 电信科学技术研究院 一种承载分离场景下进行切换的方法、设备及系统
KR101812046B1 (ko) * 2013-04-03 2017-12-29 후아웨이 테크놀러지 컴퍼니 리미티드 Ｕｅ 성능을 획득하는 방법, 단말, 및 기지국
AU2014250095B2 (en) * 2013-04-05 2016-06-16 Telefonaktiebolaget L M Ericsson (Publ) Handover request indicating split of a radio bearer between cells
US9578647B2 (en) * 2013-08-29 2017-02-21 Telefonaktiebolaget Lm Ericsson (Publ) 3GPP bearer-based QoS model support on WiFi
KR20150048611A (ko) * 2013-10-28 2015-05-07 삼성전자주식회사 이동성에 강인한 그룹 통신을 위한 방법 및 장치
CN105472659B (zh) * 2014-08-07 2019-02-22 中国电信股份有限公司 节点间无线资源分配方法和系统
CN104486793A (zh) * 2014-08-26 2015-04-01 上海华为技术有限公司 一种数据传输方法及基站
CN113411850B (zh) * 2015-01-16 2023-08-01 北京三星通信技术研究有限公司 切换方法和设备
WO2016171716A1 (en) * 2015-04-24 2016-10-27 Nokia Solutions And Networks Oy Flexible quality of service for inter-base station handovers within wireless network
CN107734562B (zh) * 2016-08-11 2020-04-03 华为技术有限公司 一种业务传输控制方法、相关设备及通信系统
CN111417137B (zh) * 2016-08-15 2021-05-04 华为技术有限公司 一种网络切片配置方法及装置
CN111885642B (zh) * 2016-11-02 2022-06-10 中兴通讯股份有限公司 切换方法及装置
WO2018132047A1 (en) * 2017-01-11 2018-07-19 Telefonaktiebolaget Lm Ericsson (Publ) A radio access node, a core network node, an information database and methods of operating the same in different radio access technologies
CN108347751B (zh) * 2017-01-25 2021-08-03 华为技术有限公司 通信方法和通信装置
CN108366391B (zh) * 2017-01-26 2023-08-25 中兴通讯股份有限公司 一种通信方法、网络设备及系统
CN108989242B (zh) * 2017-02-03 2020-01-03 华为技术有限公司 一种改变数据无线承载映射的QoS流处理方法和设备
US10986516B2 (en) * 2017-03-10 2021-04-20 Huawei Technologies Co., Ltd. System and method of network policy optimization
US10568007B2 (en) * 2017-03-22 2020-02-18 Comcast Cable Communications, Llc Handover random access
US11218933B2 (en) * 2018-09-14 2022-01-04 Qualcomm Incorporated Systems and methods for deferred 5G location of a mobile device using a combined AMF and LMF based location solution

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1951035A (zh) * 2004-05-07 2007-04-18 三星电子株式会社 在宽带无线接入通信系统中执行快速移交的系统和方法
CN107734563A (zh) * 2016-08-12 2018-02-23 电信科学技术研究院 切换场景下的QoS参数处理的方法及设备

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Study on New Radio Access Technology; Radio Access Archi- tecture and Interface (Relaease 14", 3GPP TR 38.801, no. V1.0.0, 8 December 2016 (2016-12-08), XP051229946 *
HUAWEI: "Flow based QoS during Handover", 3GPP TSG-RAN WG3 NR AD-HOC, R3-170253, 12 January 2017 (2017-01-12), XP051204448 *
NOKIA: "QoS Modification during Intra-radio Access Handover in LTE ACTIVE", 3GPP TSG-RAN WG3#51, R3-060249, 9 February 2006 (2006-02-09), XP050159196 *
See also references of EP3606171A4 *

Also Published As

Publication number Publication date
EP3606171A1 (en) 2020-02-05
CN108632909B (zh) 2019-08-23
EP3606171A4 (en) 2020-02-05
CN108632909A (zh) 2018-10-09
US20200107229A1 (en) 2020-04-02
US11190984B2 (en) 2021-11-30

Similar Documents

Publication Publication Date Title
WO2018171398A1 (zh) QoS处理方法和设备
JP6950140B2 (ja) 設定方法および装置、並びにシステム
EP3624530A1 (en) Information processing method and related apparatus
CN107734563B (zh) 切换场景下的QoS参数处理的方法及设备
WO2019056970A1 (zh) 通信方法及装置
US20220015011A1 (en) Communications Method And Apparatus
WO2019129197A1 (zh) 一种通信方法，设备及其系统
WO2018018621A1 (zh) 建立辅连接的方法和装置
WO2019062621A1 (zh) 一种进行重复传输的方法和设备
US20190239281A1 (en) Session management method and session management network element
EP3920585B1 (en) Communication system handover method, network device, apparatus and medium
US11558919B2 (en) Communication method, access network device and terminal device
WO2018171386A1 (zh) 一种QoS处理方法和装置
US20210144630A1 (en) Base station and data transmission method thereof for mobile communication system
WO2021056703A1 (zh) 信息更新方法、设备及系统
JP7340941B2 (ja) 通信装置、制御方法、及びプログラム
WO2021208813A1 (zh) 一种通信方法及通信装置
WO2022154718A1 (en) Systems and methods for ue context retrieval and data forwarding to support small data transmission
CN111083699A (zh) 一种密钥生成方法、装置、第一网络实体及基站设备
JP2021504993A (ja) 情報送信方法及び装置、並びにネットワークデバイス
WO2022036635A1 (zh) 一种通信方法及装置
WO2023273824A1 (zh) 切换方法、装置、网络设备及中继终端
US20230262837A1 (en) Communication Method and Related Apparatus Thereof
US20180270886A1 (en) Link setup method and device

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2018771369

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2018771369

Country of ref document: EP

Effective date: 20191024