CN110022581B - Method, device, network unit and terminal for supporting network bearer control - Google Patents

Method, device, network unit and terminal for supporting network bearer control Download PDF

Info

Publication number
CN110022581B
CN110022581B CN201810024065.8A CN201810024065A CN110022581B CN 110022581 B CN110022581 B CN 110022581B CN 201810024065 A CN201810024065 A CN 201810024065A CN 110022581 B CN110022581 B CN 110022581B
Authority
CN
China
Prior art keywords
bearer
priority
information
network
bearers
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201810024065.8A
Other languages
Chinese (zh)
Other versions
CN110022581A (en
Inventor
柯小婉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Priority to CN201810024065.8A priority Critical patent/CN110022581B/en
Publication of CN110022581A publication Critical patent/CN110022581A/en
Application granted granted Critical
Publication of CN110022581B publication Critical patent/CN110022581B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/16Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/24Reselection being triggered by specific parameters
    • H04W36/26Reselection being triggered by specific parameters by agreed or negotiated communication parameters
    • H04W36/28Reselection being triggered by specific parameters by agreed or negotiated communication parameters involving a plurality of connections, e.g. multi-call or multi-bearer connections
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0011Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0055Transmission or use of information for re-establishing the radio link
    • H04W36/0066Transmission or use of information for re-establishing the radio link of control information between different types of networks in order to establish a new radio link in the target network

Landscapes

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

Abstract

The invention provides a method, a device, a network unit and a terminal for supporting network bearer control, and belongs to the technical field of communication. The method for supporting network bearer control is applied to a first network unit and comprises the following steps: acquiring carried information; determining the priority information of the bearer according to the acquired bearer information; the priority information is used for bearer control, and the bearer control comprises at least one of the following: selecting an activated bearer, selecting a bearer requesting activation, selecting a switched bearer, whether an activated bearer is requested, whether a switched bearer, selecting a released bearer, whether the bearers are released. The technical scheme of the invention supports the interoperation between the extended bearer network and the non-extended bearer network, and better meets the increasing business demands.

Description

Method, device, network unit and terminal for supporting network bearer control
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method, an apparatus, a network unit, and a terminal for supporting network bearer control.
Background
Currently, the maximum number of bearers (EPS beacons) supported for UEs (User Equipment) in 3G and 4G networks is 8. As traffic increases, the number of bearers for the UE is increasingly in demand. The number of bearers supported in 5G is very large, more than 8. In order to support the interoperability of a 4G network with a 5G network, the number of bearers supported in the 4G network needs to be extended.
At present, it is not clear how to support interoperability between extended bearer networks and non-extended bearer networks.
Disclosure of Invention
The invention aims to provide a method, a device, a network unit and a terminal for supporting network bearer control, which support the interoperability between an extended bearer network and a non-extended bearer network, and better meet the increasing service demands.
In order to solve the technical problems, the embodiment of the invention provides the following technical scheme:
in a first aspect, an embodiment of the present invention provides a method for supporting network bearer control, which is applied to a first network element, and includes:
acquiring carried information;
and determining the priority information of the bearer according to the acquired bearer information.
In a second aspect, an embodiment of the present invention provides a method for supporting network bearer control, which is applied to a second network element or a terminal, and includes:
Acquiring priority information of a bearer;
carrying out bearing control according to the priority information, wherein the bearing control comprises at least one of the following: selecting an activated bearer, selecting a bearer requesting activation, selecting a switched bearer, whether the bearer is activated, whether the bearer is requested to be activated, whether the bearer is switched, selecting a released bearer, and whether the bearer is released.
In a third aspect, an embodiment of the present invention provides an apparatus for supporting network bearer control, which is applied to a first network element, and includes:
the first acquisition module is used for acquiring the carried information;
and the first processing module is used for determining the priority information of the bearer according to the acquired bearer information.
In a fourth aspect, an embodiment of the present invention provides an apparatus for supporting network bearer control, which is applied to a second network element or a terminal, and includes:
the second acquisition module is used for acquiring the priority information of the bearing;
the second processing module is configured to perform bearer control according to the priority information, where the bearer control includes at least one of the following: selecting an activated bearer, selecting a bearer requesting activation, selecting a switched bearer, whether the bearer is activated, whether the bearer is requested to be activated, whether the bearer is switched, selecting a released bearer, and whether the bearer is released.
In a fifth aspect, an embodiment of the present invention provides a first network element, including: a memory, a processor and a computer program stored on the memory and executable on the processor, which when executed by the processor performs the steps of a method for supporting network bearer control as described above.
In a sixth aspect, an embodiment of the present invention provides a second network element, including: a memory, a processor and a computer program stored on the memory and executable on the processor, which when executed by the processor performs the steps of a method for supporting network bearer control as described above.
In a seventh aspect, an embodiment of the present invention provides a terminal, including: a memory, a processor and a computer program stored on the memory and executable on the processor, which when executed by the processor performs the steps of a method for supporting network bearer control as described above.
In an eighth aspect, an embodiment of the present invention provides a computer readable storage medium, wherein the computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the method as described above.
The embodiment of the invention has the following beneficial effects:
in the above scheme, the first network unit acquires the information of the bearer, and determines the priority information of the bearer according to the acquired information of the bearer, where the priority information is used for bearer control. And the second network unit or the terminal acquires the priority information of the bearer and carries out control according to the priority information. By the technical scheme of the invention, the interoperability between the extended bearer network and the non-extended bearer network can be supported, and the increasingly-increased service demands can be better met.
Drawings
Fig. 1 is a flowchart of a method for supporting network bearer control applied to a first network element according to an embodiment of the present invention;
fig. 2 is a flow chart of a method for supporting network bearer control applied to a second network element or a terminal according to an embodiment of the present invention;
fig. 3 to fig. 7 are signaling interaction diagrams of a method for supporting network bearer control according to an embodiment of the present invention;
fig. 8 is a block diagram of an apparatus for supporting network bearer control applied to a first network element according to an embodiment of the present invention;
fig. 9 is a block diagram of an apparatus for supporting network bearer control applied to a second network element or a terminal according to an embodiment of the present invention;
fig. 10 is a block diagram of a first network element or a second network element according to an embodiment of the present invention;
Fig. 11 is a block diagram of a terminal according to an embodiment of the present invention.
Detailed Description
In a network that does not support extended bearers (such as a 3G network or an existing 4G network), the legal value of the EPS Bearer ID (non-extended Bearer identification) is any one of 5 to 15, that is, 11 total values, and the maximum number of bearers that can be established is 8.
However, the prior art has the following problems:
problem 1: when the UE needs to access to a target network that does not support the extension bearer, for the bearer to which the extension bearer identifier is allocated, since the extension bearer identifier cannot be identified by the network that does not support the extension bearer, handover or activation cannot be performed. For bearers assigned non-extended bearer identities, the bearer identities are identifiable by networks that do not support the extended bearer. But 11 non-extended bearers are identified, if all handovers or all activations are performed, they will be considered as errors by the target network not supporting the extended bearers.
Problem 2: when the UE is in a connected state, the source radio access network node needs to switch the UE to a network (such as 3G) that does not support an extended bearer, and needs to prepare Source To Target Container (source to target container) content, which contains 8 bearers at most. When the bearer identification of the existing bearer of the UE contains non-extended bearer identifications and the number of non-extended bearer identifications exceeds 8, the source radio access network node also lacks information to determine which bearer to select for handover.
Problem 3: in a network supporting extended bearers (such as a 4G network), when the bearer identities of the existing bearers of the UE contain non-extended bearer identities and the number of non-extended bearer identities exceeds 8. The subsequent UE enters an idle state and moves to a network that does not support extended bearers (e.g., a 3G network), and when the UE requests to activate a bearer, the UE also lacks information to determine which bearer to select for activation.
In 5G networks, to support interoperability to 4G, bearer identification also needs to be allocated. Similar problems are faced since the UE may continue to switch to the 3G network or to a 4G network that does not support extended bearers after switching from 5G to the 4G network. If the high priority service established in 5G is allocated with the extended bearer identification, after switching to the 4G network, the subsequent switching to the 3G network is also impossible.
In the present invention, the core network element may comprise at least one of: core network equipment, core network nodes, core network functions, core network elements, mobility management entities (Mobility Management Entity, MME), access mobility management functions (Access Management Function, AMF), session management functions (Session Management Function, SMF), user plane functions (User Plane Function, UPF), serving gateways (GW, SGW), PDN gateways (PDN GateWay), policy control functions (Policy Control Function, PCF), policy and charging rules function elements (Policy and Charging Rules Function, PCRF), serving GPRS support nodes (Serving GPRS Support Node, SGSN), gateWay GPRS support nodes (Gateway GPRS Support Node, GGSN) radio access network equipment, and,
In the present invention, the radio access network element may include at least one of: a radio Access network device, a radio Access network node, a radio Access network function, a radio Access network Unit, a 3GPP radio Access network, a Non-3GPP radio Access network, a Centralized Unit (CU), a Distributed Unit (DU), a base station, eNB, gNB, RNC, nodeB, a Non-3GPP interworking function (Non-3GPP InterWorking Function,N3IWF), an Access control (Access Controller, AC) node, an Access Point (AP) device, or a wireless local area network (Wireless Local Area Networks, WLAN) node.
The base station may be a base station (BTS, base Transceiver Station) in GSM or CDMA, a base station (NodeB) in WCDMA, or an evolved base station (eNB or e-NodeB, evolutional Node B) and a 5G base station (gNB) in LTE, and the present invention is not limited thereto, but for convenience of description, the following embodiments will be described by taking the gNB as an example.
In the present invention, the non-extended bearer identifier may refer to a legal value of an existing bearer identifier before extension, for example: any one of values 5 to 15. The extended bearer identification may refer to a legal value of the extended bearer identification. Such as any of 1 to 4 or greater than 15, for a total of 11 values.
In the present invention, the network that does not support the extension bearer may be a network element that supports the existing non-extension bearer identification but does not support the non-extension bearer identification. Such as a 3G network (e.g., UTRAN), an un-upgraded 4G network (EUTRAN, EPC, etc.).
In the present invention, the network supporting the extended bearer can support both the existing non-extended bearer identification and the network element of the non-extended bearer identification.
The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The embodiment of the invention provides a method for supporting network bearing control, which is applied to a first network unit, as shown in fig. 1, and comprises the following steps:
step 101: acquiring carried information;
step 102: and determining the priority information of the bearer according to the acquired bearer information.
The priority information may be used for bearer control, which may include at least one of: selecting an activated bearer, selecting a bearer requesting activation, selecting a switched bearer, whether an activated bearer is requested, whether a switched bearer, selecting a released bearer, whether the bearers are released.
In one embodiment, the bearers selected from the bearers selected for activation, the bearers selected for request activation, the bearers selected for handover and the bearers selected for release may refer to the bearers selected according to the priority information from the existing several bearers of the terminal. In another embodiment, whether to activate the bearer, whether to request activation of the bearer, whether to switch the bearer, and whether to release the bearer in the bearers may be an operation of the bearer corresponding to the priority information.
In this embodiment, the first network element may perform bearer control according to the determined priority information (the bearer control is described above and is not described herein again). Or, the first network element may send the determined priority information of the bearer to the second network element or the terminal, so that the second network element or the terminal performs the bearer control (the bearer control is described above and is not described herein). By the technical scheme of the invention, the interoperability between the extended bearer network and the non-extended bearer network can be supported, and the increasingly-increased service demands can be better met. Increasing business demands.
Further, before the step of determining the priority information of the bearer, the method may obtain the information of the bearer by at least one of:
Receiving a bearer identification allocation request of the bearer;
receiving the establishment request of the bearing;
receiving a Packet Data Network (PDN) connection establishment request about the bearer;
a packet data unit, PDU, session establishment request is received for the bearer.
Further, the carried information may include at least one of: qoS information for a bearer, qoS flow information for a bearer map, PDU session information for a bearer map, traffic information for a bearer, identification type information for a bearer, policies for an operator.
The QoS information carried may include at least one of: carrying QCI, qoS parameter of GBR load, ARP of load;
the information of the QoS flows carrying the mapping may include at least one of: the identification of the QoS flow, the QoS profile (context) of the bearer mapping QoS flow, the 5QI of the bearer mapping QoS flow, the ARP of the bearer mapping QoS flow;
the information of the PDU session carrying the mapping may include at least one of: identification of the bearer mapping PDU session, slice identification information of the bearer mapping session (e.g., S-nsai);
the carried service information comprises at least one of the following: multimedia priority service, high priority access.
The identification type information of the bearer may include at least one of: whether the load is an extended load identification or not and whether the load is a non-extended load identification or not;
the carried identification information comprises at least one of the following: extended bearer identification, non-extended bearer identification.
In one embodiment, the priority information of the bearer is ARP of the bearer or ARP of the QoS flow mapped by the bearer. When a bearer maps multiple QoS flows, the ARP with the highest priority is selected as the ARP of the bearer.
In one embodiment, the identity type of the bearer can be known as an extended or non-extended bearer identity through the identity of the bearer. In another embodiment, whether the bearer identification type is extended or non-extended bearer identification can be known from the bearer identification type information.
Further, the step of determining the priority information of the bearer may specifically include at least one of: when the identification type information of the bearer is a non-extension bearer identification, determining priority information of the bearer; when the identity type information of the bearer is an extended bearer identity, priority information of the bearer may not be determined. It will be appreciated that the extension bearer identity cannot be identified by networks that do not support the extension bearer. In one embodiment, the bearer that is validated for the extension bearer identification cannot be transferred directly to the target network that does not support the extension bearer. These bearers may not need priority information of the bearers. In contrast, the non-extension bearer identification is identifiable by networks that do not support extension bearers. But the maximum number of non-extended bearer identities (e.g., M) is greater than the maximum number of bearers (e.g., N) that can be established in an extended bearer network that is not supported. When the number of bearers with non-extended bearer identities of the terminal is greater than N, priority information of one bearer is required to decide which bearer can be transferred to the target network that does not support the extended bearer.
Further, the priority information is used for carrying out bearer control according to the priority information when the terminal moves into a target network which does not support the extension bearer, and the bearer control comprises at least one of the following steps: selecting an activated bearer, selecting a bearer requesting activation, selecting a switched bearer, whether an activated bearer is requested, whether a switched bearer, selecting a released bearer, whether the bearers are released.
Further, the bearer may comprise one of: a default bearer for a packet data gateway (PDN) connection, a dedicated bearer for a PDN connection, an Evolved Packet System (EPS) bearer, a Packet Data Protocol (PDP) context, a bearer for a Protocol Data Unit (PDU) session map, a Data Radio Bearer (DRB), a logical channel.
Further, the priority information may be used to perform the bearer control according to the priority information block when the terminal moves into a target network that does not support the extended bearer.
Wherein the terminal moving into the target network which does not support the extension bearer may include the terminal switching to the target network which does not support the extension bearer or accessing the target network which does not support the extension bearer at the terminal. In one embodiment, the terminal is switched to a target network that does not support the extended bearer, and the network may select the switched bearer according to the priority information of the bearer. In another embodiment, the terminal in idle state accesses to the target network which does not support the extended bearer, and the terminal can select the bearer which is requested to be activated according to the priority and information of the bearer. The network may also select an active bearer based on the priority information of the bearer. In another embodiment, when the terminal accesses to the target network that does not support the extended bearer, if the network receives the downlink data notification of the bearer, it may also determine whether to activate the bearer according to the priority information of the bearer.
Further, when the terminal moves into the target network that does not support the extension bearer, the step of performing bearer control according to the priority information may include at least one of the following:
when a terminal needs to be switched to a target network which does not support the expanded load, and the load quantity of the terminal exceeds the maximum load quantity supported by the target network, preferentially selecting a high-priority load for switching according to the priority information of the load;
when a terminal needs to be switched to a target network which does not support an extended bearer, and the number of bearers with non-extended bearer identification of the terminal exceeds the maximum number of bearers supported by the target network, preferentially selecting a bearer with high priority for switching according to the priority information of the bearer;
when a terminal accesses a target network which does not support the expanded load, and the load quantity of the terminal exceeds the maximum load quantity supported by the target network, preferentially selecting a high-priority load for activation according to the priority information of the load;
when a terminal accesses a target network which does not support an extended bearer, and the number of bearers with non-extended bearer identifiers of the terminal exceeds the maximum number of bearers supported by the target network, preferentially selecting a bearer with high priority for activation according to the priority information of the bearer;
When a terminal accesses a target network which does not support the expanded load, and the number of the load requested to be activated by the terminal exceeds the maximum load supported by the target network, preferentially selecting the load with high priority to activate according to the priority information of the load;
when a terminal accesses a target network which does not support an extended bearer, and the terminal has a non-extended bearer identification, and the number of bearers requested to be activated exceeds the maximum number of bearers supported by the target network, the high-priority bearers are preferentially selected to be activated according to the priority information of the bearers;
when a terminal accesses a target network which does not support the expanded load, and the number of the load which the terminal needs to activate exceeds the maximum load supported by the target network, preferentially selecting the load with high priority to request activation according to the priority information of the load;
when a terminal accesses a target network which does not support an extended bearer, and the terminal has a non-extended bearer identification, and the number of bearers required to be activated exceeds the maximum number of bearers supported by the target network, the high-priority bearers are preferentially selected for activation according to the priority information of the bearers;
when a terminal accesses a target network which does not support an extended bearer, and the number of bearers of the terminal or the number of bearers with non-extended bearer identifiers of the terminal exceeds the maximum number of bearers supported by the target network, selecting a low-priority bearer to release or keep inactive according to the priority information of the bearer;
When a terminal accesses a target network which does not support an extended bearer, and the number of bearers which are requested to be activated by the terminal or the number of bearers which are requested to be activated by the terminal and have non-extended bearer identifiers exceeds the maximum number of bearers supported by the target network, selecting a low-priority bearer to release or keep inactive according to the priority information of the bearers;
when the terminal accesses a target network which does not support the extended bearer, and the number of bearers which the terminal needs to activate or the number of bearers which the terminal needs to activate and has the non-extended bearer identification exceeds the maximum number of bearers supported by the target network, the low-priority bearers are selected to be released or kept inactive according to the priority information of the bearers.
Further, in one embodiment, bearers that are not selected for handover, activation, or request activation may be released or remain inactive.
Further, in one embodiment, the priority selection of the bearer with the high priority according to the priority information of the bearer may refer to selecting the bearer with the highest priority or priorities according to the priority of the bearer. The priority selection of the low priority bearer according to the priority information of the bearer may refer to selecting the bearer with the lowest priority or priorities according to the priority of the bearer. In another embodiment, the priority selection of the bearer with the high priority according to the priority information of the bearer may refer to the selection of the bearer with the priority indication.
For example, in a handover related scenario, the priority selection of a high priority bearer according to the priority information of the bearer may be the selection of a bearer with a priority indication and/or with a priority activation indication.
For example, in a scenario related to requesting activation of a bearer, the priority selection of a high priority bearer according to the priority information of the bearer may be the selection of a bearer with a priority indication and/or with a priority request activation indication. Related scenarios where an active bearer is requested, such as a terminal accessing a network (e.g., a 3G network) that does not support an extended bearer, initiate a routing area update request to activate the bearer.
For example, in a scenario related to activating a bearer, preferentially selecting a bearer with a high priority according to the priority information of the bearer may select a bearer with a priority indication and/or with a priority activation indication. And receiving downlink data notification of the bearer in a relevant scenario of activating the bearer.
Further, after the step of determining the priority information of the bearer, the method may further include at least one of:
transmitting the priority information of the bearer to at least one of the following: UE, second network element;
transmitting the carried information to at least one of the following: UE, second network element.
In one embodiment, the first network element determines the priority information and sends the priority information to the second network element, and the second network element directly performs bearer control according to the obtained priority information. In another embodiment, the first network element may send the bearer information to the second network element, and the second network element determines the priority information of the bearer according to the bearer information, and then performs bearer control.
Further, the first network element may comprise at least one of: a first radio access network element, a first core network element.
Optionally, the core network element may comprise at least one of: core network equipment, core network nodes, core network functions, core network elements, AMF, SMF, UPF, PCF, MME, SGW, PGW, PCRF, SGSN, GGSN.
Optionally, the radio access network element may comprise at least one of: radio access network equipment, radio access network nodes, radio access network function units, 3GPP radio access networks, non-3 GPP radio access networks, CU, DU, base station, eNB, gNB, RNC, nodeB, N3IWF, AC, AP, WLAN.
Further, the second network element comprises at least one of: a second radio access network element, a second core network element. The radio access network elements are specifically described above and will not be described in detail herein. The core network elements are as described above and will not be described in detail here.
The embodiment of the invention also provides a method for supporting network bearer control, which is applied to a second network unit or terminal, as shown in fig. 2, and comprises the following steps:
step 201: acquiring priority information of a bearer;
step 202: carrying out bearer control according to the priority information, wherein the bearer control can comprise at least one of the following: selecting an activated bearer, selecting a bearer requesting activation, selecting a switched bearer, whether an activated bearer is requested, whether a switched bearer, selecting a released bearer, whether the bearers are released.
In one embodiment, the bearers selected from the bearers selected for activation, the bearers selected for request activation, the bearers selected for handover and the bearers selected for release may refer to the bearers selected according to the priority information from the existing several bearers of the terminal. In another embodiment, whether to activate the bearer, whether to request activation of the bearer, whether to switch the bearer, and whether to release the bearer in the bearers may be an operation of the bearer corresponding to the priority information.
In this embodiment, the second network element or the terminal obtains the priority information of the bearer, and may perform bearer control according to the priority information (the bearer control is described above and is not described herein again). By the technical scheme of the invention, the interoperability between the extended bearer network and the non-extended bearer network can be supported, and the increasingly-increased service demands can be better met.
Further, the priority information may include at least one of: priority indication, priority handover indication, priority request activation indication, priority level. In one embodiment, the priority indication may be further divided into: priority switch indication, priority request activation indication, priority activation indication, so as to be applied to different bearer control scenes, such as a switch scene, a bearer activation scene, and a request activation bearer scene.
Further, the step of performing bearer control according to the priority information may include at least one of:
selecting a bearer with a priority activation instruction or a priority instruction to activate;
selecting a bearer with a priority activation request instruction or a priority instruction to perform request activation;
selecting a bearer with a priority switch instruction or a priority instruction to switch;
and selecting the bearer with high priority to activate, request activation or switch according to the priority level.
And selecting the bearer with the highest priority or priorities according to the priority level to activate, request activation or handover.
Further, the step of acquiring the priority information of the bearer may include one of the following:
And acquiring the priority information of the bearer by receiving the priority information of the bearer sent by the first network unit.
And determining the priority information of the bearer by acquiring the information of the bearer.
Further, the carried information may include at least one of: qoS information for a bearer, qoS flow information for a bearer map, PDU session information for a bearer map, traffic information for a bearer, identification type information for a bearer, policies for an operator.
The QoS information carried may include at least one of: carrying QCI, qoS parameter of GBR load, ARP of load;
the information of the QoS flows carrying the mapping may include at least one of: the identification of the QoS flow, the QoS profile (context) of the bearer mapping QoS flow, the 5QI of the bearer mapping QoS flow, the ARP of the bearer mapping QoS flow;
the information of the PDU session carrying the mapping may include at least one of: identification of the bearer mapping PDU session, slice identification information of the bearer mapping session (e.g., S-nsai);
the carried service information comprises at least one of the following: multimedia priority service, high priority access.
The identification type information of the bearer may include at least one of: whether the load is an extended load identification or not and whether the load is a non-extended load identification or not;
The carried identification information comprises at least one of the following: extended bearer identification, non-extended bearer identification.
In one embodiment, the priority information of the bearer is ARP of the bearer or ARP of the QoS flow mapped by the bearer. When a bearer maps multiple QoS flows, the ARP with the highest priority is selected as the ARP of the bearer.
Further, the step of performing bearer control according to the priority information may include: and when the terminal moves into a target network which does not support the extension bearing, carrying out bearing control according to the priority information.
Further, when the terminal moves into the target network that does not support the extension bearer, the step of performing bearer control according to the priority information may include at least one of:
when a terminal needs to be switched to a target network which does not support the expanded load, and the load quantity of the terminal exceeds the maximum load quantity supported by the target network, preferentially selecting a high-priority load for switching according to the priority information of the load;
when a terminal needs to be switched to a target network which does not support an extended bearer, and the number of bearers with non-extended bearer identification of the terminal exceeds the maximum number of bearers supported by the target network, preferentially selecting a bearer with high priority for switching according to the priority information of the bearer;
When a terminal accesses a target network which does not support the expanded load, and the load quantity of the terminal exceeds the maximum load quantity supported by the target network, preferentially selecting a high-priority load for activation according to the priority information of the load;
when a terminal accesses a target network which does not support an extended bearer, and the number of bearers with non-extended bearer identifiers of the terminal exceeds the maximum number of bearers supported by the target network, preferentially selecting a bearer with high priority for activation according to the priority information of the bearer;
when a terminal accesses a target network which does not support the expanded load, and the number of the load requested to be activated by the terminal exceeds the maximum load supported by the target network, preferentially selecting the load with high priority to activate according to the priority information of the load;
when a terminal accesses a target network which does not support an extended bearer, and the terminal has a non-extended bearer identification, and the number of bearers requested to be activated exceeds the maximum number of bearers supported by the target network, the high-priority bearers are preferentially selected to be activated according to the priority information of the bearers;
when a terminal accesses a target network which does not support the expanded load, and the number of the load which the terminal needs to activate exceeds the maximum load supported by the target network, preferentially selecting the load with high priority to request activation according to the priority information of the load;
When a terminal accesses a target network which does not support an extended bearer, and the terminal has a non-extended bearer identification, and the number of bearers required to be activated exceeds the maximum number of bearers supported by the target network, the high-priority bearers are preferentially selected for activation according to the priority information of the bearers;
when a terminal accesses a target network which does not support an extended bearer, and the number of bearers of the terminal or the number of bearers with non-extended bearer identifiers of the terminal exceeds the maximum number of bearers supported by the target network, selecting a low-priority bearer to release or keep inactive according to the priority information of the bearer;
when a terminal accesses a target network which does not support an extended bearer, and the number of bearers which are requested to be activated by the terminal or the number of bearers which are requested to be activated by the terminal and have non-extended bearer identifiers exceeds the maximum number of bearers supported by the target network, selecting a low-priority bearer to release or keep inactive according to the priority information of the bearers;
when the terminal accesses a target network which does not support the extended bearer, and the number of bearers which the terminal needs to activate or the number of bearers which the terminal needs to activate and has the non-extended bearer identification exceeds the maximum number of bearers supported by the target network, the low-priority bearers are selected to be released or kept inactive according to the priority information of the bearers.
Further, in one embodiment, the priority selection of the bearer with the high priority according to the priority information of the bearer may refer to selecting the bearer with the highest priority or priorities according to the priority of the bearer. The priority of the low priority bearer is selected according to the priority information of the bearer, namely, the bearer with the lowest priority or a plurality of priorities can be selected according to the priority of the bearer;
in another embodiment, the priority selection of the bearer with the high priority according to the priority information of the bearer may refer to the selection of the bearer with the priority indication.
For example, in a handover related scenario, the priority selection of a high priority bearer according to the priority information of the bearer may be the selection of a bearer with a priority indication and/or with a priority activation indication.
For example, in a scenario related to requesting activation of a bearer, the priority selection of a high priority bearer according to the priority information of the bearer may be the selection of a bearer with a priority indication and/or with a priority request activation indication. Related scenarios where an active bearer is requested, such as a terminal accessing a network (e.g., a 3G network) that does not support an extended bearer, initiate a routing area update request to activate the bearer.
For example, in a scenario related to activating a bearer, preferentially selecting a bearer with a high priority according to the priority information of the bearer may select a bearer with a priority indication and/or with a priority activation indication. And receiving downlink data notification of the bearer in a relevant scenario of activating the bearer.
Further, the first network element may comprise at least one of: a first radio access network element, a first core network element.
Optionally, the core network element may comprise at least one of: core network equipment, core network nodes, core network functions, core network elements, AMF, SMF, UPF, PCF, MME, SGW, PGW, PCRF, SGSN, GGSN.
Optionally, the radio access network element may comprise at least one of: radio access network equipment, radio access network nodes, radio access network function units, 3GPP radio access networks, non-3 GPP radio access networks, CU, DU, base station, eNB, gNB, RNC, nodeB, N3IWF, AC, AP, WLAN.
Further, the second network element comprises at least one of: a second radio access network element, a second core network element. The radio access network elements are specifically described above and will not be described in detail herein. The core network elements are as described above and will not be described in detail here.
The method for supporting network bearer control according to the present invention will be described in detail with reference to the accompanying drawings and specific embodiments:
detailed description of the preferred embodiments
In this embodiment, when the PDN connection is established, the core network element (e.g., MME, AMF) confirms the priority information of the bearer for the default bearer of the PDN connection.
Specifically, as shown in fig. 3, the method for supporting network bearer control in this embodiment includes the following steps:
step 1, a core network element (e.g. MME) receives a PDN connection establishment request message.
Step 2, the MME distributes priority information for default bearer of PDN connection.
The priority information is described in steps 101 and 102, and will not be described in detail here. The priority information may be used for bearer control, where the bearer control is described in step 101 and step 102, and is not described herein. For example, can be used for one of the following: the method is used for deciding the priority of the activated bearer when the UE accesses the network which does not support the extended bearer, and deciding the priority of the switched bearer when the wireless access network switches the UE to the target network which does not support the extended bearer.
In one embodiment, only bearers assigned with non-extended bearer identities need to acknowledge the priority information. And 3, the SGW sends a session creation request message to the PGW. The message may indicate priority information of the bearer.
Based on the received information, the PGW may perform at least one of:
and deciding an activated bearing according to the priority information.
And 4, the PGW sends a session creation response message to the SGW. The message may indicate priority information of the bearer.
Based on the received information, the PGW may perform at least one of:
and deciding an activated bearing according to the priority information.
Step 5, the SGW sends a create session response message to the MME.
Step 6, the mme sends a bearer establishment request message to the RAN node, the message may indicate at least one of: priority information of the created bearer, NAS packet.
The NAS packet may contain a NAS message such as a create session response message or a bearer context creation message, and the NAS message may indicate at least one of the following: priority information of the created bearer.
The MME may send the priority of sending the bearer to the UE in at least two ways.
The RAN may be informed by an S1 message, which in turn informs the UE AS layer by an RRC message. The UE AS layer may inform higher layers of the received bearer priority information.
The MME may also send the priority information of the bearer to the UE through NAS messages.
Based on the received information, the RAN node may perform at least one of:
Storing the bearing context, including the bearing priority information;
and when the UE is switched to a target network which does not support the extension bearing, determining the priority of the switched bearing. If there are 11 bearers with non-extended bearer identities, 8 bearers at most need to be selected for handover according to the bearer priority information.
Step 7, the ran node sends an RRC message to the UE, which may indicate at least one of: priority information of the created bearer, NAS packet.
Based on the received information, the UE may perform at least one of:
storing the bearing context, including the bearing priority information;
the priority of activating the bearer is decided when the UE accesses an extended bearer network. If there are 11 bearers with non-extended bearer identities, a maximum of 8 bearers need to be selected for activation according to the bearer priority information. Through the above PDN connection establishment procedure, priority information of default bearers of the PDN connection is stored as bearer contexts in the PGW, SGW, MME, radio access network, UE, respectively. Within a network supporting an extended bearer, a subsequent network may update the priority information of the bearer.
And 8, the UE transmits an RRC message to the RAN node.
Step 9, the RAN node sends a bearer establishment response message to the MME.
Step 10, MME and SGW modify the bearer.
Second embodiment
In this embodiment, when the dedicated bearer is established, the core network element (e.g., MME, AMF) confirms the bearer priority information for the dedicated bearer.
Specifically, as shown in fig. 4, the method for supporting network bearer control in this embodiment includes the following steps:
step 1, the pgw sends a create bearer request message to the SGW.
Step 2, the SGW sends a create bearer request message to the MME.
Step 3, the MME confirms the bearer priority information for the created bearer.
The priority information is described in step 101 and step 102, and will not be described in detail here. The priority information may be used for bearer control, where the bearer control is described in step 101 and step 102, and is not described herein. For example, the priority may be for one of: the method is used for deciding the priority of the activated bearer when the UE accesses the network which does not support the extended bearer, and deciding the priority of the switched bearer when the wireless access network switches the UE to the target network which does not support the extended bearer.
In one embodiment, only bearers assigned non-extended bearer identities need to acknowledge the priority information.
The MME sends a bearer establishment request message to the RAN node.
The message may indicate at least one of: priority information of the created bearer, NAS packet.
The NAS packet may contain a NAS message such as a create session response message or a bearer context creation message, and the NAS message may indicate at least one of the following: priority information of the created bearer.
The MME may send the priority of sending the bearer to the UE in at least two ways.
The RAN node may be informed by an S1 message, which in turn informs the UE AS layer by an RRC message. The UE AS layer may inform higher layers of the received bearer priority information.
The MME may also send the priority information of the bearer to the UE through NAS messages.
Based on the received information, the RAN node may perform at least one of:
storing the bearing context, including the bearing priority information;
and when the UE is switched to a target network which does not support the extension bearing, determining the priority of the switched bearing. If there are 11 bearers with non-extended bearer identities, 8 bearers at most need to be selected for handover according to the bearer priority information.
Step 4, the radio access network sends an RRC message (e.g., an RRC reconfiguration request message) to the UE. The message may indicate at least one of: priority information of the created bearer, NAS packet.
Based on the received information, the UE may perform at least one of:
Storing the bearing context, including the bearing priority information;
the priority of activating the bearer is decided when the UE accesses an extended bearer network. If there are 11 bearers with non-extended bearer identities, a maximum of 8 bearers need to be selected for activation according to the bearer priority information. In step 5, the ue returns an RRC message (e.g., an RRC reconfiguration response message) to the radio access network.
Step 6, the wireless access network sends a bearer establishment response message to the MME.
Step 7, the ue transmits an uplink transmission message to the RAN node.
Step 8, the RAN node sends an uplink transmission message to the MME.
In step 9, the mme returns a create bearer response message to the SGW. The message may indicate priority information of the bearer.
Based on the received information, the PGW may perform at least one of:
and deciding an activated bearing according to the priority information.
Step 10, the sgw sends a create bearer response message to the PGW. The message may indicate default bearer priority information.
The message may indicate priority information of the bearer.
Based on the received information, the PGW may perform at least one of:
and deciding an activated bearing according to the priority information.
Detailed description of the preferred embodiments
In this embodiment, when establishing a PDU session or adding a QoS flow, the SMF determines a mapped bearer, and a core network element (e.g., MME, AMF) confirms priority information for the mapped bearer.
Specifically, as shown in fig. 5, the method for supporting network bearer control in this embodiment includes the following steps:
step 1, the UE sends PDU session establishment request message to AMF.
Step 2, the AMF sends a create session context request message to the AMF.
Step 3, the smf returns a create session context response message to the AMF.
Step 4, the smf maps the bearer (e.g. EPS bearer) for the PDU session, and requests the AMF to allocate a bearer identifier (e.g. EBI) for the mapped bearer. The SMF sends an EBI allocation request message to the AMF.
The AMF acknowledges the priority information for the requested bearer. The priority information is described in step 101, and will not be described herein. The priority information may be used for bearer control, where the bearer control is described in step 101 and is not described herein. For example, the priority may be for one of: the method is used for deciding the priority of the activated bearer when the UE accesses the network which does not support the extended bearer, and deciding the priority of the switched bearer when the wireless access network switches the UE to the target network which does not support the extended bearer. In one embodiment, only bearers assigned non-extended bearer identities need to acknowledge the priority information. Step 5, the amf sends an EBI allocation response message to the SMF. At least one of the following may be indicated in the message: the PDU session maps the priority information of the bearer.
Step 6, the smf sends an N1N2 messaging message to the AMF. At least one of the following may be indicated in the message: n1 session container, N2 session message.
The N1 session container or N2 session message contains at least one of: the PDU session maps the priority information of the bearer.
Step 7, AMF sends PDU session resource establishment request message to RAN node. At least one of the following may be indicated in the message: the PDU session maps the carried priority information and NAS data packet.
The NAS packet may contain a NAS message such as a create session response message or a modify session message, which may indicate at least one of the following: the PDU session maps the priority information of the bearer.
The AMF may send priority information of the PDU session map bearer to the UE in at least two ways.
The RAN node may be informed by an S1 message, which in turn informs the UE AS layer by an RRC message. The UE AS layer may inform higher layers of the priority information of the received PDU session map bearer.
The MME may also send priority information of the PDU session map bearer to the UE through NAS messages.
Based on the received information, the RAN node may perform at least one of:
storing the bearing context, including the bearing priority information;
And when the UE is switched to a target network which does not support the extension bearing, determining the priority of the switched bearing. If there are 11 bearers with non-extended bearer identities, 8 bearers at most need to be selected for handover according to the bearer priority information.
In step 8, the radio access network sends an RRC message (e.g., an RRC reconfiguration request message) to the UE. The message may indicate at least one of: the PDU session maps the carried priority information and NAS data packet.
Based on the received information, the UE may perform at least one of:
storing the bearing context, including the bearing priority information;
the priority of activating the bearer is decided when the UE accesses an extended bearer network. If there are 11 bearers with non-extended bearer identities, a maximum of 8 bearers need to be selected for activation according to the bearer priority information.
In step 9, the ue returns an RRC message (e.g., an RRC reconfiguration response message) to the radio access network.
Step 10, the radio access network unit returns a PDU session resource establishment response message to the AMF.
In step 11, the amf sends an update session context request message to the SMF.
In step 12, the smf sends a session modification request message to the UPF. The message may indicate at least one of: the identity of the bearer to which the PDU session maps comprises a first bearer identity and/or a second bearer identity.
Based on the received information, the UPF may perform at least one of:
and storing the priority information of the mapping bearer.
And deciding an activated bearing according to the priority information. For example, when the UE accesses a network that does not support an extended bearer, the UPF needs to decide an activated bearer according to the priority level information.
Step 13, the upf sends a session modification response message to the SMF.
In step 14, the smf sends an update session context bearer response message to the AMF.
Detailed description of the preferred embodiments
In this embodiment, when the UE switches from a network supporting an extended bearer (e.g. 4G) to a network not supporting an extended bearer (e.g. 3G network), the source radio access network node determines the bearer that can be switched according to the priority information of the bearer.
Specifically, as shown in fig. 6, the method for supporting network bearer control in this embodiment includes the following steps:
step 1,4G the radio access network element (also called LTE, UTRAN, etc.) receives the measurement report reported by the UE. A handover event occurs.
Step 2,4G the radio access network element discovers that the target network is a network that does not support an extended bearer (e.g., a 3G network), alternatively the 4G radio access network element simply switches bearers with an identification of the non-extended bearer, including but not limited to at least one of:
When the terminal is switched to a target network which does not support the expanded bearer, the 4G wireless access network unit decides bearer control according to the priority information of the bearer, such as selecting the switched bearer. The bearer control is described in step 202, and will not be described in detail here. If there are 11 bearers with non-extended bearer identities, 8 bearers at most need to be selected for handover according to the bearer priority information.
The 4G radio access network element sends a handover required message to the MME. The message contains the EPS bearing context of the selected bearing.
And a network bearing control step 3, wherein the MME sends a redirection request message to the target SGSN (Serving GPRS Support Node, GPRS service support node), and the redirection request message at least comprises EPS bearing context.
And step 4, the target SGSN sends a session creation context request message to the target SGW, wherein the session creation context request message at least comprises an EPS bearing context.
And step 5, the target SGW sends a session creation context request message to the PGW, wherein the session creation context request message at least comprises an EPS bearing context.
And step 6, the PGW sends a session creation context response message to the target SGW.
And 7, the target SGW sends a session creation context response message to the target SGSN.
And 8, the target SGSN sends a repositioning request message to the target RAN node, wherein the repositioning request message at least comprises EPS bearing context.
And step 9, the target RAN node sends a relocation request confirmation message to the target SGSN.
And step 10, the target SGSN establishes an indirect data forwarding channel with the target SGW.
Step 11, the target SGSN sends a redirection response message to the MME.
Step 12, the MME and the source SGW confirm a data forwarding address.
Step 13, the MME sends a handover command to the source RAN node.
Step 14, the source RAN node sends RRC reconfiguration request message to the UE;
step 15, the UE sends an RRC reconfiguration response message or a hand-in UTRAN message to the target RAN node.
And step 16, the target RAN node sends a redirection completion notification to the target SGSN.
Step 17, the target SGSN forwards a redirection completion notification to the MME.
Step 18, the target SGSN sends a bearer modification request message to the target SGW.
Step 19, the target SGW sends a bearer modification request message to the PGW.
And step 20, the PGW sends a bearer modification response message to the target SGW.
Step 21, the target SGW sends a modify bearer response message to the target SGSN.
Example five
Specifically, as shown in fig. 7, in this embodiment, the method for supporting network bearer control includes the following steps:
step 1, the ue moves into the 3G network and sends a location update request message (e.g., a routing area update request message) to the SGSN. And when the UE accesses the bearer activated according to the priority indication of the bearer. The UE decides bearer control, such as selecting a bearer for which activation is requested, according to the priority information of the bearer. The bearer control is described in step 202, and will not be described in detail here. If there are 11 bearers with non-extended bearer identities, a maximum of 8 bearers need to be selected for activation according to the bearer priority information.
The UE sends a location update request message (e.g., a routing area update request) message to the target SGSN via the RAN node, where the message may indicate that an activated bearer is requested.
Step 2, the target SGSN sends an acquisition context message to the MME and/or SGSN;
and step 3, the SGSN sends a PDP context update request message to the PGW/GGSN.
The PGW determines bearer control, such as selecting an activated bearer, according to the priority information of the bearer. The bearer control is described in step 202, and will not be described in detail here.
Step 3, the PGW/GGSN sends a PDP context update response message to the SGSN;
and step 4, the SGSN sends a position update response message to the UE.
And 5, the SGSN sends a position update response message to the UE.
The embodiment of the invention also provides a device for supporting network bearer control, which is applied to the first network unit, as shown in fig. 8, and comprises:
a first obtaining module 31, configured to obtain information of a bearer;
a first processing module 32, configured to determine priority information of the bearer according to the acquired bearer information;
the priority information may be used for bearer control including at least one of: selecting an activated bearer, selecting a bearer requesting activation, selecting a switched bearer, whether an activated bearer is requested, whether a switched bearer, selecting a released bearer, whether the bearers are released.
In this embodiment, the first network element may perform bearer control according to the determined priority information (the bearer control is described above and is not described herein again). Or, the first network element may send the determined priority information of the bearer to the second network element or the terminal, so that the second network element or the terminal performs the bearer control (the bearer control is described above and is not described herein). By the technical scheme of the invention, the interoperability between the extended bearer network and the non-extended bearer network can be supported, and the increasingly-increased service demands can be better met. Increasing business demands
Further, the priority information includes at least one of: priority indication, priority handover indication, priority request activation indication, priority level.
Further, the bearer comprises one of: default bearers for PDN connections, dedicated bearers for PDN connections, EPS bearers, PDP contexts, bearers for PDU session mapping, DRBs, logical channels.
Further, the apparatus further comprises:
a transmission module operable to perform at least one of:
the priority information of the bearer may be sent to at least one of: UE, second network element;
the carried information may be sent to at least one of: UE, second network element.
Further, the second network element comprises at least one of: a second radio access network element, a second core network element. The radio access network element is as described in the step of fig. 1, and will not be described here again. The core network elements are as described in the steps of fig. 1, and are not described here again.
Further, the first acquisition module is specifically configured to perform at least one of:
receiving a bearer identification allocation request of the bearer;
receiving the establishment request of the bearing;
Receiving a Packet Data Network (PDN) connection establishment request about the bearer;
a packet data unit, PDU, session establishment request is received for the bearer.
Further, the carried information may include at least one of: qoS information for a bearer, qoS flow information for a bearer map, PDU session information for a bearer map, traffic information for a bearer, identification type information for a bearer, policies for an operator.
The QoS information carried may include at least one of: carrying QCI, qoS parameter of GBR load, ARP of load;
the information of the QoS flows carrying the mapping may include at least one of: the identification of the QoS flow, the QoS profile (context) of the bearer mapping QoS flow, the 5QI of the bearer mapping QoS flow, the ARP of the bearer mapping QoS flow;
the information of the PDU session carrying the mapping may include at least one of: identification of the bearer mapping PDU session, slice identification information of the bearer mapping session (e.g., S-nsai);
the carried service information comprises at least one of the following: multimedia priority service, high priority access.
The identification type information of the bearer may include at least one of: whether the load is an extended load identification or not and whether the load is a non-extended load identification or not;
The carried identification information comprises at least one of the following: extended bearer identification, non-extended bearer identification.
In one embodiment, the priority information of the bearer is ARP of the bearer or ARP of the QoS flow mapped by the bearer. When a bearer maps multiple QoS flows, the ARP with the highest priority is selected as the ARP of the bearer.
Further, the first processing module is specifically configured to determine priority information of the bearer when the identifier type information of the bearer is a non-extended bearer identifier.
Further, the priority information is used for carrying out bearer control according to the priority information when the terminal moves into a target network which does not support the extension bearer, and the bearer control can comprise at least one of the following: selecting an activated bearer, selecting a bearer requesting activation, selecting a switched bearer, whether an activated bearer is requested, whether a switched bearer, selecting a released bearer, whether the bearers are released.
Further, the first network element comprises at least one of: a first radio access network element, a first core network element. The radio access network element is as described in the step of fig. 1, and will not be described here again. The core network elements are as described in the steps of fig. 1, and are not described here again.
And the first processing module is used for carrying out the bearing control according to the priority information when the terminal moves into a target network which does not support the extension bearing.
The first processing module may be specifically configured to perform at least one of:
when a terminal needs to be switched to a target network which does not support the expanded load, and the load quantity of the terminal exceeds the maximum load quantity supported by the target network, preferentially selecting a high-priority load for switching according to the priority information of the load;
when a terminal needs to be switched to a target network which does not support an extended bearer, and the number of bearers with non-extended bearer identification of the terminal exceeds the maximum number of bearers supported by the target network, preferentially selecting a bearer with high priority for switching according to the priority information of the bearer;
when a terminal accesses a target network which does not support the expanded load, and the load quantity of the terminal exceeds the maximum load quantity supported by the target network, preferentially selecting a high-priority load for activation according to the priority information of the load;
when a terminal accesses a target network which does not support an extended bearer, and the number of bearers with non-extended bearer identifiers of the terminal exceeds the maximum number of bearers supported by the target network, preferentially selecting a bearer with high priority for activation according to the priority information of the bearer;
When a terminal accesses a target network which does not support the expanded load, and the number of the load requested to be activated by the terminal exceeds the maximum load supported by the target network, preferentially selecting the load with high priority to activate according to the priority information of the load;
when a terminal accesses a target network which does not support an extended bearer, and the terminal has a non-extended bearer identification, and the number of bearers requested to be activated exceeds the maximum number of bearers supported by the target network, the high-priority bearers are preferentially selected to be activated according to the priority information of the bearers;
when a terminal accesses a target network which does not support the expanded load, and the number of the load which the terminal needs to activate exceeds the maximum load supported by the target network, preferentially selecting the load with high priority to request activation according to the priority information of the load;
when a terminal accesses a target network which does not support an extended bearer, and the terminal has a non-extended bearer identification, and the number of bearers required to be activated exceeds the maximum number of bearers supported by the target network, the high-priority bearers are preferentially selected for activation according to the priority information of the bearers;
when a terminal accesses a target network which does not support an extended bearer, and the number of bearers of the terminal or the number of bearers with non-extended bearer identifiers of the terminal exceeds the maximum number of bearers supported by the target network, selecting a low-priority bearer to release or keep inactive according to the priority information of the bearer;
When a terminal accesses a target network which does not support an extended bearer, and the number of bearers which are requested to be activated by the terminal or the number of bearers which are requested to be activated by the terminal and have non-extended bearer identifiers exceeds the maximum number of bearers supported by the target network, selecting a low-priority bearer to release or keep inactive according to the priority information of the bearers;
when the terminal accesses a target network which does not support the extended bearer, and the number of bearers which the terminal needs to activate or the number of bearers which the terminal needs to activate and has the non-extended bearer identification exceeds the maximum number of bearers supported by the target network, the low-priority bearers are selected to be released or kept inactive according to the priority information of the bearers.
The embodiment of the invention also provides a device for supporting network bearer control, which is applied to a second network unit or terminal, as shown in fig. 9, and comprises:
a second obtaining module 41, configured to obtain priority information of a bearer;
a second processing module 42, configured to perform bearer control according to the priority information, where the bearer control includes at least one of the following: selecting an activated bearer, selecting a bearer requesting activation, selecting a switched bearer, whether an activated bearer is requested, whether a switched bearer, selecting a released bearer, whether the bearers are released.
In this embodiment, the second network element or the terminal obtains the priority information of the bearer, and may perform bearer control according to the priority information (the bearer control is described above and is not described herein again). By the technical scheme of the invention, the interoperability between the extended bearer network and the non-extended bearer network can be supported, and the increasingly-increased service demands can be better met.
The bearer comprises one of: default bearers for PDN connections, dedicated bearers for PDN connections, EPS bearers, PDP contexts, bearers for PDU session mapping, DRBs, logical channels.
Further, the priority information includes at least one of: priority indication, priority handover indication, priority request activation indication, priority level.
Further, the second processing module is specifically configured to perform at least one of:
selecting a bearer with a priority activation instruction or a priority instruction to activate;
selecting a bearer with a priority activation request instruction or a priority instruction to perform request activation;
selecting a bearer with a priority switch instruction or a priority instruction to switch;
selecting a bearer with high priority to activate, request activation or switch according to the priority level;
And selecting the bearer with the highest priority or priorities according to the priority level to activate, request activation or handover.
Further, the second acquisition module may be specifically configured to perform one of:
and acquiring the priority information of the bearer by receiving the priority information of the bearer sent by the first network unit.
And determining the priority information of the bearer by acquiring the information of the bearer.
Further, the carried information may include at least one of: qoS information for a bearer, qoS flow information for a bearer map, PDU session information for a bearer map, traffic information for a bearer, identification type information for a bearer, policies for an operator.
The QoS information carried may include at least one of: carrying QCI, qoS parameter of GBR load, ARP of load;
the information of the QoS flows carrying the mapping may include at least one of: the identification of the QoS flow, the QoS profile (context) of the bearer mapping QoS flow, the 5QI of the bearer mapping QoS flow, the ARP of the bearer mapping QoS flow;
the information of the PDU session carrying the mapping may include at least one of: identification of the bearer mapping PDU session, slice identification information of the bearer mapping session (e.g., S-nsai);
The carried service information comprises at least one of the following: multimedia priority service, high priority access.
The identification type information of the bearer may include at least one of: whether the load is an extended load identification or not and whether the load is a non-extended load identification or not;
the carried identification information comprises at least one of the following: extended bearer identification, non-extended bearer identification.
In one embodiment, the priority information of the bearer is ARP of the bearer or ARP of the QoS flow mapped by the bearer. When a bearer maps multiple QoS flows, the ARP with the highest priority is selected as the ARP of the bearer.
Further, the second processing module may be specifically configured to perform bearer control according to the priority information when the terminal moves into a target network that does not support the extended bearer. The bearer control may include at least one of: selecting an activated bearer, selecting a bearer requesting activation, selecting a switched bearer, whether an activated bearer is requested, whether a switched bearer, selecting a released bearer, whether the bearers are released.
Further, the second processing module may be specifically configured to perform at least one of:
when a terminal needs to be switched to a target network which does not support the expanded load, and the load quantity of the terminal exceeds the maximum load quantity supported by the target network, preferentially selecting a high-priority load for switching according to the priority information of the load;
When a terminal needs to be switched to a target network which does not support an extended bearer, and the number of bearers with non-extended bearer identification of the terminal exceeds the maximum number of bearers supported by the target network, preferentially selecting a bearer with high priority for switching according to the priority information of the bearer;
when a terminal accesses a target network which does not support the expanded load, and the load quantity of the terminal exceeds the maximum load quantity supported by the target network, preferentially selecting a high-priority load for activation according to the priority information of the load;
when a terminal accesses a target network which does not support an extended bearer, and the number of bearers with non-extended bearer identifiers of the terminal exceeds the maximum number of bearers supported by the target network, preferentially selecting a bearer with high priority for activation according to the priority information of the bearer;
when a terminal accesses a target network which does not support the expanded load, and the number of the load requested to be activated by the terminal exceeds the maximum load supported by the target network, preferentially selecting the load with high priority to activate according to the priority information of the load;
when a terminal accesses a target network which does not support an extended bearer, and the terminal has a non-extended bearer identification, and the number of bearers requested to be activated exceeds the maximum number of bearers supported by the target network, the high-priority bearers are preferentially selected to be activated according to the priority information of the bearers;
When a terminal accesses a target network which does not support the expanded load, and the number of the load which the terminal needs to activate exceeds the maximum load supported by the target network, preferentially selecting the load with high priority to request activation according to the priority information of the load;
when a terminal accesses a target network which does not support an extended bearer, and the terminal has a non-extended bearer identification, and the number of bearers required to be activated exceeds the maximum number of bearers supported by the target network, the high-priority bearers are preferentially selected for activation according to the priority information of the bearers;
when a terminal accesses a target network which does not support an extended bearer, and the number of bearers of the terminal or the number of bearers with non-extended bearer identifiers of the terminal exceeds the maximum number of bearers supported by the target network, selecting a low-priority bearer to release or keep inactive according to the priority information of the bearer;
when a terminal accesses a target network which does not support an extended bearer, and the number of bearers which are requested to be activated by the terminal or the number of bearers which are requested to be activated by the terminal and have non-extended bearer identifiers exceeds the maximum number of bearers supported by the target network, selecting a low-priority bearer to release or keep inactive according to the priority information of the bearers;
When the terminal accesses a target network which does not support the extended bearer, and the number of bearers which the terminal needs to activate or the number of bearers which the terminal needs to activate and has the non-extended bearer identification exceeds the maximum number of bearers supported by the target network, the low-priority bearers are selected to be released or kept inactive according to the priority information of the bearers.
Further, in one embodiment, the priority selection of the bearer with the high priority according to the priority information of the bearer may refer to selecting the bearer with the highest priority or priorities according to the priority of the bearer. The priority of the low priority bearer is selected according to the priority information of the bearer, namely, the bearer with the lowest priority or a plurality of priorities can be selected according to the priority of the bearer;
in another embodiment, the priority selection of the bearer with the high priority according to the priority information of the bearer may refer to the selection of the bearer with the priority indication.
For example, in a handover related scenario, the priority selection of a high priority bearer according to the priority information of the bearer may be the selection of a bearer with a priority indication and/or with a priority activation indication.
For example, in a scenario related to requesting activation of a bearer, the priority selection of a high priority bearer according to the priority information of the bearer may be the selection of a bearer with a priority indication and/or with a priority request activation indication. Related scenarios where an active bearer is requested, such as a terminal accessing a network (e.g., a 3G network) that does not support an extended bearer, initiate a routing area update request to activate the bearer.
For example, in a scenario related to activating a bearer, preferentially selecting a bearer with a high priority according to the priority information of the bearer may select a bearer with a priority indication and/or with a priority activation indication. And receiving downlink data notification of the bearer in a relevant scenario of activating the bearer.
Further, the second network element comprises at least one of: a second radio access network element, a second core network element. The radio access network element is as described in the step of fig. 1, and will not be described here again. The core network elements are as described in the steps of fig. 1, and are not described here again.
The embodiment of the invention also provides a first network unit, which comprises: a memory, a processor and a computer program stored on the memory and executable on the processor, which when executed by the processor performs the steps of a method for supporting network bearer control as described above.
The embodiment of the invention also provides a second network unit, which comprises: a memory, a processor and a computer program stored on the memory and executable on the processor, which when executed by the processor performs the steps of a method for supporting network bearer control as described above.
Referring to fig. 10, fig. 10 is a block diagram of a first network element or a second network element applied in the embodiment of the present invention, which can implement details of the method for supporting network bearer control in the foregoing embodiment and achieve the same effects. As shown in fig. 10, the first network element or the second network element 500 includes: a processor 501, a transceiver 502, a memory 503, a user interface 504, and a bus interface, wherein:
in an embodiment of the present invention, the first network unit 500 further includes: a computer program stored on the memory 503 and executable on the processor 501, which when executed by the processor 501 performs the steps of: acquiring carried information;
determining the priority information of the bearer according to the acquired bearer information;
the priority information is used for deciding at least one of the following: selecting an activated bearer, selecting a bearer requesting activation, selecting a switched bearer, whether an activated bearer is requested, whether a switched bearer, selecting a released bearer, whether the bearers are released.
In fig. 10, a bus architecture may comprise any number of interconnecting buses and bridges, with various circuits of the one or more processors, represented in particular by processor 501, and the memory, represented in particular by memory 503. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 502 may be a number of elements, i.e. comprising a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium. The user interface 504 may also be an interface capable of interfacing with an inscribed desired device for a different user device, including but not limited to a keypad, display, speaker, microphone, joystick, etc.
The processor 501 is responsible for managing the bus architecture and general processing, and the memory 503 may store data used by the processor 501 in performing operations.
In an embodiment of the present invention, the second network unit 500 further includes: a computer program stored on the memory 503 and executable on the processor 501, which when executed by the processor 501 performs the steps of: acquiring priority information of a bearer;
carrying out bearing control according to the priority information, wherein the bearing control comprises at least one of the following: selecting an activated bearer, selecting a bearer requesting activation, selecting a switched bearer, whether the bearer is activated, whether the bearer is requested to be activated, whether the bearer is switched, selecting a released bearer, and whether the bearer is released.
In fig. 10, a bus architecture may comprise any number of interconnecting buses and bridges, with various circuits of the one or more processors, represented in particular by processor 501, and the memory, represented in particular by memory 503. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 502 may be a number of elements, i.e. comprising a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium. The user interface 504 may also be an interface capable of interfacing with an inscribed desired device for a different user device, including but not limited to a keypad, display, speaker, microphone, joystick, etc.
The processor 501 is responsible for managing the bus architecture and general processing, and the memory 503 may store data used by the processor 501 in performing operations.
The embodiment of the invention also provides a terminal, which comprises: a memory, a processor and a computer program stored on the memory and executable on the processor, which when executed by the processor performs the steps of a method for supporting network bearer control as described above.
Referring to fig. 11, fig. 11 is a block diagram of a terminal to which the embodiment of the present invention is applied, which can implement details of the method for supporting network bearer control in the above embodiment and achieve the same effects. As shown in fig. 11, the terminal 600 includes: processor 604, antenna 601, radio frequency device 602, baseband device 603, memory 605, network interface 606, and bus interface, wherein:
in an embodiment of the present invention, the terminal 600 further includes: a computer program stored on the memory 605 and executable on the processor 604, which when executed by the processor 604 performs the steps of: acquiring priority information of a bearer; carrying out bearing control according to the priority information, wherein the bearing control comprises at least one of the following: selecting an activated bearer, selecting a bearer requesting activation, selecting a switched bearer, whether the bearer is activated, whether the bearer is requested to be activated, whether the bearer is switched, selecting a released bearer, and whether the bearer is released.
In fig. 11, a bus architecture may be comprised of any number of interconnected buses and bridges, and in particular, one or more processors represented by the processor 604 and various circuits of the memory, represented by the memory 605. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The network interface 606 may also be an interface capable of interfacing with an internal connection requiring device, including but not limited to a keypad, display, speaker, microphone, joystick, etc.
The processor 604 is responsible for managing the bus architecture and general processing, and the memory 605 may store data used by the processor 604 in performing operations.
Embodiments of the present invention also provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of a method for supporting network bearer control as described above.
It is to be understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For a hardware implementation, the processing units may be implemented within one or more application specific integrated circuits (Application Specific Integrated Circuits, ASIC), digital signal processors (Digital Signal Processing, DSP), digital signal processing devices (DSP devices, DSPD), programmable logic devices (Programmable Logic Device, PLD), field programmable gate arrays (Field-Programmable Gate Array, FPGA), general purpose processors, controllers, microcontrollers, microprocessors, other electronic units configured to perform the functions described herein, or a combination thereof.
For a software implementation, the techniques described herein may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The software codes may be stored in a memory and executed by a processor. The memory may be implemented within the processor or external to the processor.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described by differences from other embodiments, and identical and similar parts between the embodiments are all enough to be referred to each other.
It will be apparent to those skilled in the art that embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the invention may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
Embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal device, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiment and all such alterations and modifications as fall within the scope of the embodiments of the invention.
It is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or terminal device comprising the element.
While the foregoing is directed to the preferred embodiments of the present invention, it will be appreciated by those skilled in the art that various modifications and changes can be made without departing from the principles of the present invention, and such modifications and changes are intended to be within the scope of the present invention.

Claims (32)

1. A method for supporting network bearer control, comprising:
the method comprises the steps that a first core network CN network element obtains carried information;
the first CN network element determines the priority information of the bearer according to the acquired bearer information;
the first CN network element sends the carried priority information to a terminal and/or a second network element;
the priority information is used for carrying out bearing control according to the priority information when the terminal moves into a target network which does not support the extension bearing, and the bearing control comprises at least one of the following steps: selecting an activated bearer, selecting a bearer requesting activation, whether a bearer is activated, whether a bearer requesting activation is activated.
2. The method for supporting network bearer control according to claim 1, wherein,
the priority information includes at least one of: priority indication, priority request activation indication, priority level.
3. The method of supporting network bearer control according to claim 1, wherein the bearer comprises one of: default bearers for packet data gateway PDN connections, dedicated bearers for PDN connections, evolved packet system EPS bearers, packet data protocol PDP contexts, bearers for protocol data unit PDU session mapping, data radio bearers DRBs, logical channels.
4. The method for supporting network bearer control according to claim 1, wherein prior to said step of determining the priority information of the bearer, said method obtains the information of the bearer by at least one of:
receiving a bearer identification allocation request of the bearer;
receiving the establishment request of the bearing;
receiving a Packet Data Network (PDN) connection establishment request about the bearer;
a packet data unit, PDU, session establishment request is received for the bearer.
5. The method of supporting network bearer control according to claim 1, wherein the information of the bearer comprises at least one of: the QoS information of the bearer, the QoS flow information of the bearer map, the PDU session information of the bearer map, the service information of the bearer, the identification type information of the bearer, and the policy of the operator.
6. The method for supporting network bearer control according to claim 5, wherein,
the QoS information carried includes at least one of: the QOS class mark QCI is carried, and the QoS parameter carried by the bit rate GBR and the address resolution protocol ARP carried are ensured;
the information of the QoS flows carrying the mapping includes at least one of: the identification of the QoS flow, the QoS context profile of the bearer mapping QoS flow, the 5QI of the bearer mapping QoS flow and the ARP of the bearer mapping QoS flow;
The information of the PDU session carrying the mapping includes at least one of: identification of the bearer mapping PDU session and slice identification information of the bearer mapping session;
the carried service information comprises at least one of the following: multimedia priority service and high priority access;
the identification type information of the bearer comprises at least one of the following: whether the load is an extended load identification or not and whether the load is a non-extended load identification or not;
the carried identification information comprises at least one of the following: extended bearer identification, non-extended bearer identification.
7. The method for supporting network bearer control according to claim 6, wherein said step of determining the priority information of the bearer specifically comprises:
and when the identification type information of the bearer is a non-extension bearer identification, determining the priority information of the bearer.
8. The method for supporting network bearer control according to claim 1, wherein after the step of determining the priority information of the bearer according to the information of the acquired bearer, the method comprises:
and when the terminal moves into a target network which does not support the extension bearing, carrying out bearing control according to the priority information.
9. The method for supporting network bearer control according to claim 8, wherein said step of performing said bearer control according to said priority information when the terminal moves into a target network that does not support an extended bearer comprises at least one of:
When a terminal accesses a target network which does not support the expanded load, and the load quantity of the terminal exceeds the maximum load quantity supported by the target network, preferentially selecting a high-priority load for activation according to the priority information of the load;
when a terminal accesses a target network which does not support an extended bearer, and the number of bearers with non-extended bearer identifiers of the terminal exceeds the maximum number of bearers supported by the target network, preferentially selecting a bearer with high priority for activation according to the priority information of the bearer;
when a terminal accesses a target network which does not support the expanded load, and the number of the load requested to be activated by the terminal exceeds the maximum load supported by the target network, preferentially selecting the load with high priority to activate according to the priority information of the load;
when a terminal accesses a target network which does not support an extended bearer, and the terminal has a non-extended bearer identification, and the number of bearers requested to be activated exceeds the maximum number of bearers supported by the target network, the high-priority bearers are preferentially selected to be activated according to the priority information of the bearers;
when a terminal accesses a target network which does not support the expanded load, and the number of the load which the terminal needs to activate exceeds the maximum load supported by the target network, preferentially selecting the load with high priority to request activation according to the priority information of the load;
When a terminal accesses a target network which does not support an extended bearer, and the terminal has a non-extended bearer identification, and the number of bearers required to be activated exceeds the maximum number of bearers supported by the target network, the high-priority bearers are preferentially selected for activation according to the priority information of the bearers;
when a terminal accesses a target network which does not support an extended bearer, and the number of bearers of the terminal or the number of bearers with non-extended bearer identifiers of the terminal exceeds the maximum number of bearers supported by the target network, selecting a low-priority bearer according to the priority information of the bearer to keep inactive;
when a terminal accesses a target network which does not support an extended bearer, and the number of bearers which are requested to be activated by the terminal or the number of bearers which are requested to be activated by the terminal and have non-extended bearer identification exceeds the maximum number of bearers supported by the target network, selecting a low-priority bearer according to the priority information of the bearers to keep inactive;
when the terminal accesses a target network which does not support the extended bearer, and the number of bearers which the terminal needs to activate or the number of bearers which the terminal needs to activate and has the non-extended bearer identification exceeds the maximum number of bearers supported by the target network, the low-priority bearer is selected according to the priority information of the bearers to keep inactive.
10. A method for supporting network bearer control, comprising:
the method comprises the steps that a second network unit or a terminal obtains priority information of a bearer, wherein the priority information is used for carrying out bearer control according to the priority information when the terminal moves into a target network which does not support extension bearer; the second network unit or the terminal performs bearer control according to the priority information, where the bearer control includes at least one of the following: selecting an activated bearer, selecting a bearer requesting activation, whether the bearer is activated, and whether the bearer requesting activation is activated;
wherein the second network element comprises: a radio access network RAN network element, a second CN network element.
11. The method for supporting network bearer control according to claim 10, wherein,
the priority information includes at least one of: priority indication, priority request activation indication, priority level.
12. The method for supporting network bearer control according to claim 10, wherein,
the bearer comprises one of: default bearers for packet data gateway PDN connections, dedicated bearers for PDN connections, evolved packet system EPS bearers, packet data protocol PDP contexts, bearers for protocol data unit PDU session mapping, data radio bearers DRBs, logical channels.
13. The method for supporting network bearer control according to claim 11, wherein said step of bearer control according to said priority information comprises at least one of:
selecting a bearer with a priority activation instruction or a priority instruction to activate;
selecting a bearer with a priority activation request instruction or a priority instruction to perform request activation;
selecting a bearer with high priority to activate and request activation according to the priority level;
and selecting the bearer with the highest priority or priorities to activate according to the priority level, and requesting activation.
14. The method for supporting network bearer control according to claim 10, wherein said step of acquiring bearer priority information comprises one of:
acquiring the priority information of the bearer by receiving the priority information of the bearer sent by the first network element;
and determining the priority information of the bearer by acquiring the information of the bearer.
15. The method of supporting network bearer control according to claim 14, wherein the information of the bearer comprises at least one of: the QoS information of the bearer, the QoS flow information of the bearer map, the PDU session information of the bearer map, the service information of the bearer, the identification type information of the bearer, and the policy of the operator.
16. The method of supporting network bearer control according to claim 15, wherein the QoS information of the bearer comprises at least one of: the QOS class mark QCI is carried, and the QoS parameter carried by the bit rate GBR and the address resolution protocol ARP carried are ensured;
the information of the QoS flows carrying the mapping includes at least one of: the identification of the QoS flow, the QoS context profile of the bearer mapping QoS flow, the 5QI of the bearer mapping QoS flow and the ARP of the bearer mapping QoS flow;
the information of the PDU session carrying the mapping includes at least one of: identification of the bearer mapping PDU session and slice identification information of the bearer mapping session;
the carried service information comprises at least one of the following: multimedia priority service and high priority access;
the identification type information of the bearer comprises at least one of the following: whether the load is an extended load identification or not and whether the load is a non-extended load identification or not;
the carried identification information comprises at least one of the following: extended bearer identification, non-extended bearer identification.
17. The method for supporting network bearer control according to claim 10, wherein said step of bearer control according to said priority information comprises:
and when the terminal moves into a target network which does not support the extension bearing, carrying out bearing control according to the priority information.
18. The method for supporting network bearer control according to claim 17, wherein said step of performing bearer control according to said priority information when the terminal moves into a target network that does not support an extended bearer comprises at least one of:
when a terminal accesses a target network which does not support the expanded load, and the load quantity of the terminal exceeds the maximum load quantity supported by the target network, the RAN network unit preferentially selects a high-priority load for activation according to the priority information of the load;
when a terminal accesses a target network which does not support an extended bearer, and the number of bearers with non-extended bearer identifiers of the terminal exceeds the maximum number of bearers supported by the target network, the RAN network unit preferentially selects a bearer with high priority to activate according to the priority information of the bearer;
when a terminal accesses a target network which does not support an extended bearer, and the number of bearers requested to be activated by the terminal exceeds the maximum number of bearers supported by the target network, the RAN network unit preferentially selects a high-priority bearer to be activated according to the priority information of the bearer;
when a terminal accesses a target network which does not support an extended bearer, wherein the terminal has a non-extended bearer identification, the number of bearers requested to be activated exceeds the maximum number of bearers supported by the target network, and the RAN network unit preferentially selects a high-priority bearer to be activated according to the priority information of the bearers;
When a terminal accesses a target network which does not support the expanded load, and the number of the load which needs to be activated by the terminal exceeds the maximum load supported by the target network, the terminal preferentially selects the load with high priority to request activation according to the priority information of the load;
when a terminal accesses a target network which does not support an extended bearer, wherein the terminal has a non-extended bearer identification, the number of bearers required to be activated exceeds the maximum number of bearers supported by the target network, and the RAN network unit preferentially selects a high-priority bearer to be activated according to the priority information of the bearers;
when a terminal accesses a target network which does not support an extended bearer, and the number of bearers of the terminal or the number of bearers with non-extended bearer identifiers of the terminal exceeds the maximum number of bearers supported by the target network, the terminal or the second CN network unit selects a bearer with low priority according to priority information of the bearer and keeps inactive;
when a terminal accesses a target network which does not support an extended bearer, and the number of bearers requested to be activated by the terminal or the number of bearers requested to be activated by the terminal and having non-extended bearer identification exceeds the maximum number of bearers supported by the target network, the terminal or the second CN network unit selects a low-priority bearer according to the priority information of the bearer to keep inactive;
When a terminal accesses a target network which does not support an extended bearer, and the number of bearers which the terminal needs to activate or the number of bearers which the terminal needs to activate and has a non-extended bearer identification exceeds the maximum number of bearers supported by the target network, the terminal or the second CN network unit selects a bearer with low priority according to the priority information of the bearer and keeps inactive.
19. The method for supporting network bearer control according to claim 18, wherein said preferentially selecting a high priority bearer according to the priority information of the bearer comprises at least one of:
the priority selection of the high priority bearer according to the priority information of the bearer means that the bearer with the highest priority or a plurality of priorities is selected according to the priority of the bearer;
the priority selection of the low priority bearer according to the priority information of the bearer means that the bearer with the lowest priority or a plurality of priorities is selected according to the priority of the bearer;
the priority selection of the high priority bearer according to the priority information of the bearer means that the bearer with the priority indication is selected;
in the related scenario of requesting to activate the bearer, the priority selection of the bearer with high priority according to the priority information of the bearer refers to selecting the bearer with priority indication and/or with priority request activation indication;
In a related scenario of activating bearers, preferentially selecting a high priority bearer according to the priority information of the bearer refers to selecting a bearer with a priority indication and/or with a priority activation indication.
20. An apparatus for supporting network bearer control, comprising:
the first acquisition module is used for acquiring the carried information by the first CN network element;
the first processing module is used for determining the priority information of the bearer according to the acquired bearer information by the first CN network element;
a sending module, configured to send the carried priority information to a terminal and/or a second network element by using the first CN network element;
the priority information is used for carrying out bearing control according to the priority information when the terminal moves into a target network which does not support the extension bearing, and the bearing control comprises at least one of the following steps: selecting an activated bearer, selecting a bearer requesting activation, whether a bearer is activated, whether a bearer requesting activation is activated.
21. The apparatus for supporting network bearer control according to claim 20, wherein,
the priority information includes at least one of: priority indication, priority request activation indication, priority level.
22. The apparatus for supporting network bearer control according to claim 20, wherein the first acquisition module is specifically configured to perform at least one of:
receiving a bearer identification allocation request of the bearer;
receiving the establishment request of the bearing;
receiving a Packet Data Network (PDN) connection establishment request about the bearer;
a packet data unit, PDU, session establishment request is received for the bearer.
23. The apparatus for supporting network bearer control according to claim 20, wherein said first processing module is configured to perform said bearer control according to said priority information when a terminal moves into a target network that does not support an extended bearer.
24. An apparatus for supporting network bearer control, comprising:
the second acquisition module is used for acquiring the priority information of the bearer by a second network unit or a terminal, wherein the priority information is used for carrying out bearer control according to the priority information when the terminal moves into a target network which does not support the extension bearer;
the second processing module is configured to perform bearer control by the second network element or the terminal according to the priority information, where the bearer control includes at least one of the following: selecting an activated bearer, selecting a bearer requesting activation, whether the bearer is activated, and whether the bearer requesting activation is activated;
Wherein the second network element comprises: RAN network element, second CN network element.
25. The apparatus for supporting network bearer control according to claim 24, wherein,
the priority information includes at least one of: priority indication, priority request activation indication, priority level.
26. The apparatus for supporting network bearer control according to claim 25, wherein the second processing module is specifically configured to perform at least one of:
selecting a bearer with a priority activation instruction or a priority instruction to activate;
selecting a bearer with a priority activation request instruction or a priority instruction to perform request activation;
selecting a bearer with high priority to activate and request activation according to the priority level;
and selecting the bearer with the highest priority or priorities to activate according to the priority level, and requesting activation.
27. The apparatus for supporting network bearer control according to claim 24, wherein the second acquisition module is specifically configured to perform one of:
acquiring the priority information of the bearer by receiving the priority information of the bearer sent by the first network element;
And determining the priority information of the bearer by acquiring the information of the bearer.
28. The apparatus for supporting network bearer control according to claim 24, wherein the second processing module is specifically configured to perform bearer control according to the priority information when the terminal moves into the target network that does not support the extension bearer.
29. A first CN network element, comprising: memory, a processor and a computer program stored on the memory and executable on the processor, which when executed by the processor performs the steps of the method of supporting network bearer control as claimed in any one of claims 1 to 9.
30. A second network element, comprising: memory, a processor and a computer program stored on the memory and executable on the processor, which when executed by the processor performs the steps of the method of supporting network bearer control as claimed in any one of claims 10 to 19.
31. A terminal, comprising: memory, a processor and a computer program stored on the memory and executable on the processor, which when executed by the processor performs the steps of the method of supporting network bearer control as claimed in any one of claims 10 to 19.
32. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the method of supporting network bearer control according to any of claims 1 to 9 or the steps of the method of supporting network bearer control according to any of claims 10 to 19.
CN201810024065.8A 2018-01-10 2018-01-10 Method, device, network unit and terminal for supporting network bearer control Active CN110022581B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810024065.8A CN110022581B (en) 2018-01-10 2018-01-10 Method, device, network unit and terminal for supporting network bearer control

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810024065.8A CN110022581B (en) 2018-01-10 2018-01-10 Method, device, network unit and terminal for supporting network bearer control

Publications (2)

Publication Number Publication Date
CN110022581A CN110022581A (en) 2019-07-16
CN110022581B true CN110022581B (en) 2023-07-14

Family

ID=67188147

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810024065.8A Active CN110022581B (en) 2018-01-10 2018-01-10 Method, device, network unit and terminal for supporting network bearer control

Country Status (1)

Country Link
CN (1) CN110022581B (en)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11277791B2 (en) 2019-10-16 2022-03-15 Samsung Electronics Co., Ltd. Method for user equipment initiated network slice registration and traffic forwarding in telecommunication networks
WO2021091285A1 (en) * 2019-11-06 2021-05-14 Samsung Electronics Co., Ltd. Method and apparatus for controlling network slice in wireless communication system
CN112788682B (en) * 2019-11-08 2022-08-19 华为技术有限公司 Communication method and device thereof
CN112788584B (en) * 2019-11-08 2022-07-29 华为技术有限公司 Communication method and device
CN113132970B (en) * 2019-12-31 2022-11-29 大唐移动通信设备有限公司 Method and device for notifying combined service priority
CN117459993B (en) * 2023-12-22 2024-03-15 深圳国人无线通信有限公司 Method and device for determining service priority in dedicated service channel

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103327547A (en) * 2007-09-28 2013-09-25 株式会社Ntt都科摩 Radio communication system and radio communication method

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101299825B (en) * 2007-04-30 2012-07-25 华为技术有限公司 Method, system and apparatus for implementing multicast load-bearing resource control
US8861535B2 (en) * 2010-05-21 2014-10-14 Cisco Technology, Inc. Multi-tiered paging support using paging priority
JP2011182443A (en) * 2011-04-21 2011-09-15 Ntt Docomo Inc Wireless communication system, and wireless communication method
US9538450B2 (en) * 2012-08-03 2017-01-03 Futurewei Technologies, Inc. System and method for mobile relay packet gateway relocation for path optimization
US20140105125A1 (en) * 2012-10-16 2014-04-17 Qualcomm Incorporated Criteria for ue-initiated bearer deactivation when maximum number of active bearers has been reached
KR102232787B1 (en) * 2014-06-30 2021-03-26 삼성전자 주식회사 Method and apparatus for controlling service continuity in mobile communication systems
US9591516B2 (en) * 2014-12-23 2017-03-07 Motorola Solutions, Inc. Method and apparatus for managing bearers in a wireless communication system

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103327547A (en) * 2007-09-28 2013-09-25 株式会社Ntt都科摩 Radio communication system and radio communication method

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
CATT, China Mobile, CATR, China Unicom, China Telecom, Huawei, ZTE, OPPO, vivo.S2-175877 "Discussion on EPS bearer ID allocation".3GPP tsg_sa\WG2_Arch.2017,(TSGS2_122BIS_Sophia_Antipolis),全文. *
CDMA网络接入EPC的关键技术分析;关琳;谢沛荣;;电信科学(05);全文 *
Ericsson.S2-173322 "EPS bearer ID allocation in 5GS".3GPP tsg_sa\WG2_Arch.2017,(TSGS2_121_Hangzhou),全文. *
LTE高话务量场景的优化策略及保障方案研究;答嘉曦;;移动通信(08);全文 *
ZTE.S2-082245 "23.401 CR0229: Bearer Update Indication in Create Bearer Request message".3GPP tsg_sa\WG2_Arch.2008,(TSGS2_64_Jeju),全文. *

Also Published As

Publication number Publication date
CN110022581A (en) 2019-07-16

Similar Documents

Publication Publication Date Title
JP7279773B2 (en) Wireless terminal and method
CN110022581B (en) Method, device, network unit and terminal for supporting network bearer control
CN108419270B (en) Service distribution realization method and device
EP3669591B1 (en) Network entity, user equipment and method for the control and use of network slices
EP3562207B1 (en) Data transmission method, network device and terminal device
US11129054B2 (en) Methods, systems and devices for supporting local breakout in small cell architecture
JPWO2018128020A1 (en) Base station, radio terminal and methods thereof
JP6152398B2 (en) Method for updating network detection and selection information and traffic routing information
JP7290193B2 (en) Wireless terminal and method in wireless terminal
CN110636475B (en) Data processing method and device
EP3860089A1 (en) Network service control method and communication device
KR102232787B1 (en) Method and apparatus for controlling service continuity in mobile communication systems
WO2019242724A1 (en) Communication method, and paging method, device and system
TWI539841B (en) Mobile communication devices, access networks, and methods for steering data traffic
CN110719613B (en) Method and device for establishing voice service
JP2015527783A (en) Congestion state reporting method and access network device
CN111510977B (en) Mobility management method and device
CN111757357B (en) Redirection method, network and terminal equipment, communication system and readable storage medium
JP2022043218A (en) Communication method, secondary network node and terminal
WO2012059118A1 (en) Improved quality of service control
JP7111812B2 (en) Random access method, device and storage medium for communication device
US9706476B2 (en) Method for obtaining radio access network information and radio access network controller
US20210266730A1 (en) Method for indicating terminal capability, method for obtaining terminal capability, method for indicating capability identifier, method for obtaining capability identifier, and communications device
CN111278048B (en) Capability indication method and device
CN114071605A (en) Switching method, device and system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant