WO2018107490A1

WO2018107490A1 - Method and device for controlling data transmission rate on non-gbr bearer

Info

Publication number: WO2018107490A1
Application number: PCT/CN2016/110476
Authority: WO
Inventors: 朱强华
Original assignee: 华为技术有限公司
Priority date: 2016-12-16
Filing date: 2016-12-16
Publication date: 2018-06-21

Abstract

Embodiments of the present invention provide a method and a device for controlling a data transmission rate on a non-GRB bearer to at least resolve an issue in the prior art, in which an AMBR of a data transmission between UE and a DN is not controllable when multiple UP-GWs are selected for the DN to which the UE requests access. The method comprises: a CP function entity receiving an identifier of a target DN, wherein the identifier is transmitted by the UE and indicates a DN to which the UE requests access; the CP function entity selecting serving UP-GWs for the UE according to the identifier of the target DN, and acquiring respective normalized weightings of the serving UP-GWs; the CP function entity acquiring an AMBR of a data transmission between the UE and the target DN according to the identifier of the target DN; the CP function entity determines, according to the normalized weighting of a first UP-GW and the AMBR of the data transmission between the UE and the target DN, an AMBR of a data transmission on a non-GBR bearer between the UE and the first UP-GW, wherein the first UP-GW is any one of the serving UP-GWs; and the CP function entity sending the AMBR of the data transmission on the non-GBR bearer between the UP and the first UP-GW to the first UP-GW and the UE. The present application is applicable to the field of wireless communications.

Description

Method and device for controlling data transmission rate on non-GBR bearer

Technical field

The present application relates to the field of wireless communications, and in particular, to a method and apparatus for controlling a data transmission rate on a non-Guranteed Bit Rate (non-GBR) bearer.

Background technique

In order to meet the challenges of wireless broadband technology and maintain the leading edge of the 3rd Generation Partnership Project (3GPP) network, the 3GPP standards group developed the next generation Next Generation System network architecture at the end of 2016. It is called the 5rd Generation (5G) network architecture. As shown in FIG. 1 , the 5G network architecture is composed of a user equipment (UE), a radio access network (RAN) access point, a core network, and a data network (DN). The core network is divided into a user plane (UP) function and a control plane (CP) function. The UP function is implemented by the UP-Gateway (UP-GW), and the CP function is implemented by the CP function entity. In order to meet the extreme needs of various scenarios, the 5G network is allowed to select multiple UP-GWs for one DN requested by the UE to serve as a connection point between the mobile network and the DN, and provide a data forwarding service for the UE. For example, in FIG. 1, UP-GW1 can be used to satisfy traditional Internet services, and UP-GW2 can be used to satisfy low-latency services.

However, as shown in FIG. 1, when there are multiple UP-GWs, it means that the UE has multiple paths to reach the same data network, and the rate of common data on the non-GBR bearers of the multiple paths cannot exceed the access of the UE. Aggregate Maximum Bit Rate (AMBR) of data transmission between the UE and the DN when a DN is used. However, the rate of data transmission on the non-GBR bearer of UP-GW1 or UP-GW2 can only control the path of each path cannot exceed the AMBR, and cannot interfere with the rate of data transmission on the non-GBR bearer of other paths, thereby causing the UE to The AMBR for data transmission between DNs is not controllable.

Summary of the invention

The embodiment of the present application provides a method and a device for controlling a data transmission rate on a non-GBR bearer, so as to at least solve the problem in the prior art when multiple UP-GWs are selected for a DN requested by the UE for access, between the UE and the DN. The uncontrolled problem of AMBR for data transmission.

To achieve the above objective, the embodiment of the present application provides the following technical solutions:

In a first aspect, a method for controlling a data transmission rate on a non-guaranteed bit rate non-GBR bearer is provided, the method comprising: the control plane CP function entity receiving an identifier of a target data network DN sent by the user equipment UE, the identifier of the target DN a DN for instructing the UE to request access; the CP function entity selects a serving user plane gateway UP-GW for the UE according to the identifier of the target DN, and obtains a normalized weight of the service UP-GW; the CP functional entity Acquiring, according to the identifier of the target DN, an aggregate maximum bit rate AMBR of data transmission between the UE and the target DN; the CP function entity is based on a normalized weight of the first UP-GW and data between the UE and the target DN Transmitting an AMBR, determining an AMBR for data transmission on a non-GBR bearer between the UE and the first UP-GW, the first UP-GW being any one of the serving UP-GWs; the CP functional entity The AMBR of the data transmission on the non-GBR bearer between the UE and the first UP-GW is sent to the first UP-GW and the UE. Based on the control method of the data transmission rate on the non-GBR bearer provided by the embodiment of the present application, when multiple UP-GWs are selected for one DN requested by the UE, on the one hand, not only the data between the UE and the DN can be controlled. The transmitted AMBR may also control the AMBR of the data transmission on the non-GBR bearer between the UE and each of the plurality of UP-GWs, so that different paths between the UE and one DN may be satisfied. Business needs. On the other hand, since the current network architecture and network element deployment are not changed, there is no uncontrollable factor or additional burden for the mobile network, and the transmission path length is not increased due to technical reasons, affecting some low times. The performance of the extended service has no effect on other traditional gateway technologies and security mechanisms.

In a possible design, the CP function entity obtains the normalized weight of the service UP-GW, including: the CP function entity acquires the weight of the service UP-GW; and the CP function entity according to the service UP-GW The weights are normalized for each UP-GW in the service UP-GW, and the normalized weights of the service UP-GW are obtained. In this way, the CP functional entity can obtain the normalized weight of the serving UP-GW.

In a possible design, the CP functional entity obtains the weight of the service UP-GW, The method includes: the CP function entity acquires a weight of the service UP-GW preconfigured in the CP function entity. That is, the weight of the serving UP-GW may be statically configured in the CP functional entity. This method is simpler and more convenient.

In a possible design, the CP function entity receives the network parameter sent by the first UP-GW; and determines the weight of the first UP-GW according to the network parameter of the first UP-GW. That is, the CP function entity can serve the network parameters reported by each UP-GW in the UP-GW, and dynamically obtain the weight of each UP-GW. The network parameter may specifically include: a historical average rate of data transmission on the non-GBR bearer between the UE and each UP-GW, a location of each UP-GW, a load of each UP-GW, and each UP-GW The service attributes and the like of the connected data network are not specifically limited in this embodiment of the present application. Since the above-mentioned dynamically acquiring the weight of each UP-GW takes into account the current network parameters of each UP-GW, it is possible to make the AM function allocated by the CP function entity for each UP-GW in the serving UP-GW more in line with each The actual situation of the UP-GW, that is to say, the result of the allocation is more precise, so that the control of the AMBR for data transmission on the non-GBR bearer between the UE and each UP-GW is also more accurate.

In a possible design, the method further includes: the CP function entity acquiring subscription data of the UE, where the subscription data includes data transmission on a non-GBR bearer between the UE and the first UP-GW. An additional AMBR; the CP functional entity determines a non-GBR bearer between the UE and the first UP-GW according to a normalized weight of the first UP-GW and an AMBR of data transmission between the UE and the target DN The AMBR of the data transmission includes: the CP function entity determines, according to the normalized weight of the first UP-GW and the AMBR of the data transmission between the UE and the target DN, the UE and the first UP-GW The intermediate non-GBR carries the intermediate AMBR of the data transmission; the CP functional entity mediates the intermediate AMBR of the data transmission on the non-GBR bearer between the UE and the first UP-GW, and the UE and the The additional AMBRs of the data transmission on the non-GBR bearer between the first UP-GW are added to obtain an AMBR for data transmission on the non-GBR bearer between the UE and the first UP-GW. That is, in the embodiment of the present application, the additional AMBR is also used for data transmission on the non-GBR bearer between the UE and the first UP-GW, for example, it is assumed that the first UP-GW is located at the edge of the network, close to the user, specifically for the mobile user. Providing high-definition video, in order to ensure the user's smooth experience, there is no cardon when watching the video, and each user can be assigned an additional AMBR of 50 Mbps to ensure that the UP-GW transmits data from the UE and the target DN in the future. Obtained in AMBR How many other rate quotas are available? If the user is downloading files through the UP-GW, the 50 Mbps additional AMBR can meet the basic HD video rate requirements, avoiding the occurrence of a stuck condition due to insufficient allocated rate quotas.

In a possible design, the CP function entity selects a service UP-GW for the UE according to the identifier of the target DN, and the method includes: the CP function entity queries the identifier of the pre-configured DN and the identifier of the DN according to the identifier of the target DN. Corresponding all the corresponding mappings of the UP-GWs, and obtaining the identifiers of all the UP-GWs corresponding to the identifiers of the target DNs; and further, the CP functional entities are determined by the identifiers of all the UP-GWs corresponding to the identifiers of the target DNs based on the preset policies. The UP-GW is selected for the UE in the UP-GW. The preset policy can be based, for example, on current business needs. In this way, the CP functional entity can select the serving UP-GW for the UE according to the identifier of the target DN.

In a possible design, the CP function entity acquires the AMBR of the data transmission between the UE and the target DN according to the identifier of the target DN, including: the CP function entity queries the pre-configured DN according to the identifier of the target DN. The correspondence between the AMBR and the data transmission between the UE and the DN is identified, and an AMBR for data transmission between the UE and the target DN is obtained. In this way, the CP function entity acquires the AMBR of data transmission between the UE and the target DN according to the identifier of the target DN.

In a possible design, the method further includes: the CP function entity receives a service request of the UE; the CP function entity selects a second UP-GW for the UE according to the service request of the UE and the identifier of the target DN. The CP function entity acquires a normalized weight of the second UP-GW; the CP function entity determines, according to the normalized weight of the second UP-GW and the AMBR of data transmission between the UE and the target DN, The non-GBR between the UE and the second UP-GW carries an AMBR for data transmission; the CP function entity sends the AMBR of the data transmission on the non-GBR bearer between the UE and the second UP-GW to The second UP-GW and the UE. That is, the control method of the data transmission rate on the non-GBR bearer provided by the embodiment of the present application is convenient to expand, and a UP-GW is newly selected, and the AMBR of the data transmission on the non-GBR between the UE and the UP-GW can be easily performed.

In a possible design, the method further includes: the CP function entity updating a normalized weight of the first UP-GW, and obtaining an updated normalized weight of the first UP-GW; The CP function entity updates the AMBR of the data transmission on the non-GBR bearer between the UE and the first UP-GW according to the updated normalized weight and the AMBR of the data transmission between the UE and the target DN. Obtaining an updated AMBR; the CP function entity sends the updated AMBR to the first UP-GW and the UE. That is, in the embodiment of the present application, the AMBR of the data transmission on the normalized weight of the first UP-GW and the non-GBR bearer between the UE and the first UP-GW is opposite to the original UP-GW. In the case where the value when the UP-GW is served is changed, the normalized weight of the first UP-GW and the AMBR of the data transmission on the non-GBR bearer between the UE and the first UP-GW may also be updated.

In a possible design, the method further includes: the CP function entity acquiring subscription data of the UE, where the subscription data includes data transmission on a non-GBR bearer between the UE and the second UP-GW. Adding an AMBR; the CP function entity determines a non-GBR between the UE and the second UP-GW according to a normalized weight of the second UP-GW and an AMBR of data transmission between the UE and the target DN The AMBR carrying the data transmission includes: determining, by the CP function entity, the UE and the second UP-GW according to the normalized weight of the second UP-GW and the AMBR of data transmission between the UE and the target DN The intermediate AMBR of the data transmission between the non-GBR bearers; the intermediate AMBR of the data transmission on the non-GBR bearer between the UE and the second UP-GW, and the UE in the The additional AMBRs of the data transmission on the non-GBR bearer between the second UP-GWs are added to obtain an AMBR for data transmission on the non-GBR bearer between the UE and the second UP-GW. That is, in the embodiment of the present application, the additional AMBR is also used for data transmission on the non-GBR bearer between the UE and the second UP-GW, for example, it is assumed that the second UP-GW is located at the edge of the network, close to the user, specifically for the mobile user. Providing high-definition video, in order to ensure the user's smooth experience, there is no cardon when watching the video, and each user can be assigned an additional AMBR of 50 Mbps to ensure that the UP-GW transmits data from the UE and the target DN in the future. How many other rate quotas are obtained in the AMBR. If the user is downloading files through the UP-GW, the additional AMBR of 50 Mbps can meet the requirements of the basic HD video rate, thereby avoiding the occurrence of a stuck condition due to insufficient rate quota allocation. .

In a second aspect, a control plane CP function entity is provided. The CP function entity includes: a receiving module, an obtaining module, a determining module, a selecting module, and a sending module. The receiving module is configured to receive a target data network DN sent by the user equipment UE. Identification of the target DN a DN indicating that the UE requests access; the selecting module is configured to select a serving user plane gateway UP-GW according to the identifier of the target DN received by the receiving module; the acquiring module is configured to acquire the selected module The normalization weight of the service UP-GW; the obtaining module is further configured to acquire, according to the identifier of the target DN received by the receiving module, an aggregate maximum bit rate AMBR of data transmission between the UE and the target DN; the determining module Determining a non-guaranteed bit between the UE and the first UP-GW according to the normalized weight of the first UP-GW acquired by the acquiring module and the AMBR of data transmission between the UE and the target DN The non-GBR carries the AMBR of the data transmission, and the first UP-GW is any one of the serving UP-GWs; the sending module is configured to use the UE determined by the determining module and the first UP-GW The AMBR of the non-GBR bearer on the data transmission is sent to the first UP-GW and the UE.

In a possible design, the obtaining module obtains the normalized weight of the service UP-GW selected by the selecting module, including: obtaining the weight of the service UP-GW selected by the selecting module; according to the service UP-GW The weights are normalized for each UP-GW in the service UP-GW, and the normalized weights of the service UP-GW are obtained.

In a possible design, the obtaining module obtains the weight of the service UP-GW selected by the selection module, including: acquiring a weight of the service UP-GW selected by the selection module pre-configured in the CP function entity; or Receiving, by the network parameter sent by the first UP-GW, determining a weight of the first UP-GW according to the network parameter of the first UP-GW.

In a possible design, the acquiring module is further configured to acquire subscription data of the UE, where the subscription data includes an additional AMBR for data transmission on a non-GBR bearer between the UE and the first UP-GW. The determining module determines the non- between the UE and the first UP-GW according to the normalized weight of the first UP-GW acquired by the obtaining module and the AMBR of the data transmission between the UE and the target DN. The GBR carries the AMBR of the data transmission, and includes: determining, according to the normalized weight of the first UP-GW acquired by the acquiring module, and the AMBR of the data transmission between the UE and the target DN, determining the UE and the first UP - an intermediate AMBR for data transmission on a non-GBR bearer between GWs; an intermediate AMBR for data transmission on a non-GBR bearer between the UE and the first UP-GW, and the UE and the An additional AMBR of the data transmission on the non-GBR bearer between the UP-GWs is obtained, and an AMBR for data transmission on the non-GBR bearer between the UE and the first UP-GW is obtained.

In a possible design, the selecting module selects a service UP-GW for the UE according to the identifier of the target DN, and includes: querying, according to the identifier of the target DN, all the UPs corresponding to the identifier of the DN and the identifier of the DN. - the identifier of the GW, the identifier of all the UP-GWs corresponding to the identifier of the target DN is obtained; and the UE is selected from the UP-GW determined by the identifiers of all the UP-GWs corresponding to the identifier of the target DN based on the preset policy. Service UP-GW. The preset policy can be based, for example, on current business needs.

In a possible design, the acquiring module acquires the AMBR of the data transmission between the UE and the target DN according to the identifier of the target DN, and includes: querying the identifier of the pre-configured DN and the UE according to the identifier of the target DN. The correspondence between the AMBRs of the data transmission between the DNs is obtained by the AMBR of the data transmission between the UE and the target DN.

In a possible design, the receiving module is further configured to receive a service request of the UE, where the selecting module is further configured to: according to the service request of the UE and the identifier of the target DN received by the receiving module, the UE Selecting a second UP-GW; the obtaining module is further configured to obtain a normalized weight of the second UP-GW selected by the selecting module; the determining module is further configured to use the second UP- obtained by the acquiring module Determining the normalized weight of the GW and the AMBR of the data transmission between the UE and the target DN, determining an AMBR for data transmission on the non-GBR bearer between the UE and the second UP-GW; the sending module is further used And transmitting, by the determining module, the AMBR of the data transmission on the non-GBR bearer between the UE and the second UP-GW to the second UP-GW and the UE.

In a possible design, the CP functional entity further includes an update module, and the update module is configured to update a normalized weight of the first UP-GW to obtain an updated normalization of the first UP-GW. The update module is further configured to update the non-GBR bearer between the UE and the first UP-GW according to the updated normalized weight and the AMBR of the data transmission between the UE and the target DN. The AMBR of the data transmission is obtained, and the updated AMBR is obtained. The sending module is further configured to send the updated AMBR that is updated by the update module to the first UP-GW and the UE.

In a possible design, the acquiring module is further configured to acquire subscription data of the UE, where the subscription data includes an additional AMBR for data transmission on a non-GBR bearer between the UE and the second UP-GW. The determining module acquires the second UP-GW according to the acquiring module Determining the AMBR of the data transmission between the UE and the target DN, and determining the AMBR of the data transmission on the non-GBR bearer between the UE and the second UP-GW, including: obtaining according to the acquiring module Determining the normalized weight of the second UP-GW and the AMBR of data transmission between the UE and the target DN, determining an intermediate AMBR for data transmission on the non-GBR bearer between the UE and the second UP-GW Transmitting the intermediate AMBR of the data transmission on the non-GBR bearer between the UE and the second UP-GW, and transmitting the data on the non-GBR bearer between the UE and the second UP-GW The additional AMBR is added to obtain an AMBR for data transmission on the non-GBR bearer between the UE and the second UP-GW.

A third aspect provides a control plane CP functional entity, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor is connected to the memory through the bus, when the CP functional entity In operation, the processor executes the computer-executed instructions stored in the memory to cause the CP functional entity to perform a control method of the data transmission rate on the non-guaranteed bit rate non-GBR bearer according to any of the above first aspects.

In a fourth aspect, an embodiment of the present application provides a computer storage medium for storing computer software instructions used by the control plane CP functional entity, and includes a program designed to execute the foregoing aspect as a control plane CP functional entity.

In a fifth aspect, the embodiment of the present application provides a computer program, where the computer program includes instructions, when the computer program is executed by a computer, to enable the computer to perform the non-guaranteed bit rate non-GBR of any one of the foregoing first aspects. The flow in the control method that carries the data transmission rate.

In addition, the technical effects brought by the design mode of any one of the second aspect to the fifth aspect can be referred to the technical effects brought by different design modes in the first aspect, and details are not described herein again.

These and other aspects of the present application will be more readily apparent from the following description of the embodiments.

In summary, based on the method for controlling the data transmission rate on the non-GBR bearer and the CP function entity provided by the embodiment of the present application, when multiple UP-GWs are selected for one DN requested by the UE, on the one hand, not only the The AMBR for data transmission between the UE and the DN may also control the AMBR of the data transmission on the non-GBR bearer between the UE and each of the plurality of UP-GWs, thereby satisfying the UE and a DN. Not on different paths Same business needs. On the other hand, since the current network architecture and network element deployment are not changed, there is no uncontrollable factor or additional burden for the mobile network, and the transmission path length is not increased due to technical reasons, affecting some low times. The performance of the extended service has no effect on other traditional gateway technologies and security mechanisms.

DRAWINGS

FIG. 1 is a schematic diagram of an existing 5G network architecture;

2 is a schematic structural diagram of a computer device according to an embodiment of the present application;

FIG. 3 is a schematic flowchart of a method for controlling a data transmission rate on a non-GBR bearer according to an embodiment of the present disclosure;

4 is a schematic flowchart of a method for controlling data transmission rate on another non-GBR bearer according to an embodiment of the present disclosure;

FIG. 5 is a schematic flowchart of a method for controlling data transmission rate on a non-GBR bearer according to an embodiment of the present disclosure;

FIG. 6 is a schematic flowchart of a method for controlling data transmission rate on a non-GBR bearer according to an embodiment of the present disclosure;

FIG. 7 is a schematic structural diagram of a CP functional entity according to an embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. In the description of the present application, the meaning of "a plurality" is two or more unless otherwise stated.

As shown in Figure 1, it is an existing 5G network architecture. The RAN access point communicates with the UE through a next generation network (NG)1, communicates with the CP functional entity of the 5G core network through the NG2, and communicates with the UP-GW of the 5G core network through the NG3. The CP functional entity of the 5G core network communicates with the UP-GW of the 5G core network through NG4. The UP-GW of the 5G core network communicates with the DN through NG6. The following briefly describes the various components of the 5G network structure as follows:

UE: is the entry point for mobile users to interact with the network, providing basic computing power and storage. Ability to store, display business windows to users, and accept user input. In addition, the UE in the 5G network architecture adopts next-generation air interface technology to establish signal connection and data connection with the RAN, thereby transmitting control signals and service data to the core network.

RAN access point: Similar to the base station in the traditional network, it is deployed at a certain location to provide network access functions for authorized users in a specific area, and can use different quality transmission tunnels according to user level and service requirements. The RAN access point can manage its own resources and provide access services for the UE as needed, thereby completing the forwarding of control signals and user data between the UE and the core network.

Core network: responsible for maintaining the subscription data of the mobile network, managing the network elements of the mobile network, and providing functions such as session management, mobility management, policy management, and security authentication for the UE. When the UE is attached, the UE is provided with network access authentication; when the UE has a service request, the network resource is allocated to the UE; when the UE moves, the network resource is updated for the UE; when the UE is idle, the UE is provided with a fast recovery mechanism; When the UE is detached, the network resource is released for the UE; when the UE has the service data, the data routing function is provided for the UE, such as forwarding the uplink data to the DN; or receiving the downlink data of the UE from the DN, and forwarding the data to the RAN access point. Thereby sent to the UE.

As mentioned above, the core network is divided into UP function and CP function. Among them, the UP function is mainly responsible for the transmission of service data, such as packet data packet forwarding, quality of service (QoS) control, accounting information statistics, etc. The CP function is mainly responsible for mobile network management, such as sending data packet forwarding. Policies, QoS control strategies, etc. Generally, the UP function is implemented by the UP-GW, and the CP function is implemented by the CP function entity, and the CP function entity may specifically include a mobility management entity, a session management entity, and the like, which is not specifically limited in this embodiment of the present application.

DN: A data network that provides services for users. The general client is located at the UE and the server is located at the DN. The DN can be a private network, such as a local area network, or an external network that is not controlled by the operator, such as the Internet, or a proprietary network deployed by the operator, for example, to configure an Internet Protocol (IP) multimedia network. A network deployed by the system (IP Multimedia Core Network Subsystem, IMS) service.

Although not shown, the above 5G network architecture may also include a database entity for supporting a primary user database of an IMS network entity that processes or invokes the session. It includes user profiles, performs user authentication and authorization, and provides information about user physics. The location information is similar to the global system for mobile communication (GSM) home location register. The functions provided by the database entity include the IP multimedia function, or the home location register (HLR) function required for the packet switched (PS) domain, and/or the HLR required for the call service (CS) domain. Features. The information that the database entity can process includes one or more of the following information: user identification, numbering and address information; user security information, ie network access control information for authentication and authorization; user positioning information, ie database entity support User registration, storage location information; user list information, etc. In the embodiment of the present application, the database entity is mainly used to provide subscription data related to the new UP-GW, such as an additional AMBR value of the new UP-GW, when the UE selects a new UP-GW.

Of course, the above 5G network architecture may also include other modules or network entities, such as a Policy and Charging Rules Function (PCRF) entity, a Policy and Charging Control (PCC) entity, or The policy control entity and the like are not specifically limited in this embodiment of the present application.

It should be noted that the UE involved in the present application may include various handheld devices with wireless communication functions, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to the wireless modem, and various forms of UEs. Mobile station (MS), terminal, terminal equipment, soft terminal, and the like. For convenience of description, in the present application, the devices mentioned above are collectively referred to as user equipments or UEs.

It should be noted that the foregoing DN, RAN access point, database entity, CP functional entity, and UP-GW are only one name, and the name itself does not limit the device. For example, the RAN access point may also be replaced by a Next Generation Access Network (AN) access point; the database entity may also be replaced by a Home Subscriber Server (HSS) or a user subscription. a User Subscription Database (USD) or a Subscriber Repository (SR); the CP functional entity may also be replaced with a CP function or a CP, and the UP-GW may also be replaced with an UP-GW entity. The DN may also be replaced with an access point name (APN) in the second generation (2G), the third generation (3rd generation, 3G) or the third generation (3rd generation, 5G), etc. Etc., hereby make a unified explanation, the details are not described below.

In addition, any one of the above-mentioned 5G network architectures, such as a CP functional entity or an UP-GW, may be implemented by one physical device or multiple physical devices; The functional nodes or network elements, such as the CP functional entity and the UP-GW, may be implemented by different physical devices, or may be implemented by the same physical device, which is not specifically limited in this embodiment. That is, it can be understood that any one of the above-mentioned 5G network architectures, such as a CP function entity or an UP-GW, may be a logical function module in the physical device, or may be a plurality of entities. A logical function module of the device is not specifically limited in this embodiment of the present application.

As shown in FIG. 2, the CP functional entity in the 5G network architecture shown in FIG. 1 can be implemented by the computer device (or system) in FIG. 2.

FIG. 2 is a schematic diagram of a computer device according to an embodiment of the present application. The computer device 200 includes at least one processor 201, a communication bus 202, a memory 203, and at least one communication interface 204.

The processor 201 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more programs for controlling the execution of the program of the present application. integrated circuit.

Communication bus 202 can include a path for communicating information between the components described above.

The communication interface 204 uses a device such as any transceiver for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), etc. .

The memory 203 can be a Read-Only Memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type that can store information and instructions. The dynamic storage device can also be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this. Save The memory can exist independently and be connected to the processor via a bus. The memory can also be integrated with the processor.

The memory 203 is used to store application code for executing the solution of the present application, and is controlled by the processor 201 for execution. The processor 201 is configured to execute application code stored in the memory 203 to implement UP functional entity selection of non-3GPP access.

In a particular implementation, as an embodiment, processor 201 may include one or more CPUs, such as CPU0 and CPU1 in FIG.

In a particular implementation, as an embodiment, computer device 200 can include multiple processors, such as processor 201 and processor 208 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.

In a particular implementation, as an embodiment, computer device 200 may also include an output device 205 and an input device 206. Output device 205 is in communication with processor 201 and can display information in a variety of ways. For example, the output device 205 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait. Input device 206 is in communication with processor 201 and can accept user input in a variety of ways. For example, input device 206 can be a mouse, keyboard, touch screen device or sensing device, and the like.

The computer device 200 described above can be a general purpose computer device or a special purpose computer device. In a specific implementation, the computer device 200 can be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet, a wireless terminal device, a communication device, an embedded device, or have FIG. A device of similar structure. The embodiment of the present application does not limit the type of computer device 200.

As shown in FIG. 3, a schematic flowchart of a method for controlling a data transmission rate on a non-GBR bearer according to an embodiment of the present application includes the following steps:

S301: The CP function entity receives the identifier of the target DN sent by the UE, where the identifier of the target DN is used to indicate the DN that the UE requests to access.

Specifically, the identifier of the target DN may be carried by the attached message sent by the UE to the CP function entity, or may be carried by other messages, which is not specifically limited in this embodiment of the present application.

S302. The CP function entity selects a service UP-GW for the UE according to the identifier of the target DN.

Specifically, the CP function entity may select one UP-GW or multiple UP-GWs for the UE as the service UP-GW of the UE, which is not specifically limited in this embodiment of the present application.

Specifically, the CP function entity selects the service UP-GW for the UE according to the identifier of the target DN, and specifically includes: the CP function entity queries the pre-configured DN identifier and all the UPs corresponding to the identifier of the DN according to the identifier of the target DN. The identifier of the GW is obtained by the GW, and the identifiers of all the UP-GWs corresponding to the identifiers of the target DNs are obtained. Further, the CP function entity may be determined from the UP-GWs determined by the identifiers of all the UP-GWs corresponding to the identifiers of the target DNs based on the preset policies. Select the service UP-GW for the UE. The preset policy can be based, for example, on current business needs.

Illustratively, if the current service requirement is a traditional Internet service and a low-latency service, and the UP-GW determined by the identity of all UP-GWs corresponding to the identifier of the target DN, the UP-GW1 can be used to satisfy the traditional Internet service. The UP-GW2 can be used to meet the low-latency service, and the CP function entity can select the UP-GW1 and the UP-GW2 as the service UP-GW of the UE for the UE. For details, refer to step S402 in the embodiment shown in FIG.

S303. The CP function entity acquires a normalized weight of the service UP-GW.

Exemplarily, as shown in FIG. 4, since the CP function entity takes the UE as selecting the UP-GW1 and the UP-GW2 as the serving UP-GW of the UE, the CP functional entity acquires the normalization of the service UP-GW. The weight is actually that the CP functional entity acquires the normalized weight of UP-GW1 and the normalized weight of UP-GW2 (step S403).

S304. The CP functional entity acquires an AMBR for data transmission between the UE and the target DN according to the identifier of the target DN.

Wherein, the AMBR of the data transmission between the UE and the target DN defines the total bit rate that all non-GBR bearers associated with the target DN are allowed to use, as in FIG. 1, all non-GBR bearers associated with the DN include the UE and Non-GBR bearer between UP-GW1 and non-GBR bearer between UE and UP-GW2.

It should be noted that the AMBR for data transmission between the UE and the target DN in step S304 may specifically refer to the APN-AMBR defined in the existing protocol. APN-AMBR defines the total bit rate that all non-GBR bearers associated with a particular APN are allowed to use.

In addition, it should be noted that, in the embodiment of the present application, the total bit rate of all non-GBR bearers allowed to be used actually refers to the total bit rate of data transmission on all non-GBR bearers, which is uniformly described herein, and details are not described herein again.

S305. The CP function entity determines, according to the normalized weight of the first UP-GW and the AMBR of the data transmission between the UE and the target DN, the AMBR of the data transmission on the non-GBR bearer between the UE and the first UP-GW. The first UP-GW is any one of the serving UP-GWs.

It should be noted that, in this embodiment of the present application, the serving UP-GW may include one or more UP-GWs. When the serving UP-GW includes only one UP-GW, the first UP-GW is the serving UP-GW; when the serving UP-GW includes multiple UP-GWs, the first UP-GW is in the serving UP-GW. anyone.

As shown in FIG. 4, the CP function entity selects two serving UP-GWs, UP-GW1 and UP-GW2 for the UE. Then, the first UP-GW may be any one of UP-GW1 and UP-GW2.

S306. The CP function entity sends the AMBR of the data transmission on the non-GBR bearer between the UE and the first UP-GW to the first UP-GW.

Specifically, reference may be made to step S406a or S406b in the embodiment shown in FIG.

S307. The CP function entity sends an AMBR that transmits data on the non-GBR bearer between the UE and the first UP-GW to the UE.

Specifically, reference may be made to step S407a or S407b in the embodiment shown in FIG.

In the embodiment shown in FIG. 3, the order of execution of steps S302 and S304 is not limited, and the order of execution of steps S306 and S307 is not limited. For example, step S306 may be performed first, and then step S307 may be performed; step S307 may be performed first, and then step S306 may be performed; obviously, steps S306 and S307 may also be performed simultaneously.

The method for controlling the data transmission rate on the non-GBR bearer provided by the embodiment of the present application, when selecting multiple UP-GWs for one DN requested by the UE, on the one hand, not only The AMBR that controls the data transmission between the UE and the DN may also control the AMBR of the data transmission on the non-GBR bearer between the UE and each of the plurality of UP-GWs, so that the UE and the UE can be satisfied. Different business needs on different paths between one DN. On the other hand, since the current network architecture and network element deployment are not changed, there is no uncontrollable factor or additional burden for the mobile network, and the transmission path length is not increased due to technical reasons, affecting some low times. The performance of the extended service has no effect on other traditional gateway technologies and security mechanisms.

Optionally, the CP function entity obtains the normalized weight of the service UP-GW in step S303, and specifically includes:

S3031: The CP functional entity acquires the weight of the service UP-GW;

S3032: The CP functional entity normalizes each UP-GW in the service UP-GW according to the weight of the serving UP-GW, and obtains a normalized weight of the service UP-GW.

Illustratively, the normalized weight of each UP-GW in the service UP-GW can be calculated based on equation (1):

Where α(n) represents the weight of the nth UP-GW in the serving UP-GW, and ω(n) represents the normalized weight of the nth UP-GW in the serving UP-GW,

Indicates the sum of the weights of all UP-GWs in the serving UP-GW, and N is the number of UP-GWs in the serving UP-GW.

It should be noted that the weight of the service UP-GW acquired by the CP function entity may be a normalized weight, or may not be a normalized weight, which is not specifically limited in this embodiment of the present application.

For example, FIG. 4 illustrates an example in which the CP function entity selects UP-GW1 and UP-GW2 as the UE's service UP-GW for the UE. Wherein, if the weight of UP-GW1 is 0.2 and the weight of UP-GW2 is 0.3, it is obtained based on formula (1), the normalized weight ω(1) of UP-GW1 is 0.4, and the normalization of UP-GW2 The weight ω(2) is 0.6. Alternatively, if the weight of UP-GW1 is 2 and the weight of UP-GW2 is 3, it is available based on formula (1), and the normalized weight of UP-GW1 is ω(1). At 0.4, the normalized weight ω(2) of UP-GW2 is 0.6.

Optionally, in a possible implementation manner of the step S3031, the CP function entity obtains the weight of the serving UP-GW, and the CP function entity acquires the weight of the pre-configured service UP-GW in the CP function entity.

That is, the weight of the serving UP-GW may be statically configured in the CP functional entity. This method is simpler and more convenient.

For example, as shown in FIG. 4, the CP function entity selects UP-GW1 and UP-GW2 as the service UP-GW of the UE as an example. Therefore, the CP function entity acquires the weight of the pre-configured service UP-GW in the CP function entity. In fact, the CP functional entity acquires the weight of the pre-configured UP-GW1 and the weight of the UP-GW2 in the CP functional entity.

Optionally, in another possible implementation manner of step S3031, the CP function entity obtains the weight of the serving UP-GW, including:

The CP function entity receives the network parameter sent by the first UP-GW;

The CP function entity determines the weight of the first UP-GW according to the network parameter of the first UP-GW, where the first UP-GW is any one of the service UP-GWs.

For example, the CP function entity can dynamically obtain the weight of each UP-GW according to the network parameters reported by each UP-GW in the serving UP-GW.

The network parameter may specifically include: a historical average rate of data transmission on the non-GBR bearer between the UE and each UP-GW, a location of each UP-GW, a load of each UP-GW, and each UP One or more of the service attributes of the data network to which the GW is connected, and the embodiment of the present application does not specifically limit this.

Specifically, according to the network parameters reported by each UP-GW in the serving UP-GW, the weight of each UP-GW can be calculated based on formula (2):

Where α(n) represents the weight of the nth UP-GW in the serving UP-GW; Avg_AMBRn represents the historical average rate of data transmission on the non-GBR bearer between the UE and the nth UP-GW; Serv _rate represents the current The usage rate of the quota allocated for this UE, for example, 30M is allocated, but 5M is actually used, which means that the allocation is much, Serv _rate = 1/6; GW _level indicates the location parameter of the nth UP-GW; GW _Load represents the _{load of} the nth UP-GW. For example, the UP-GW serves up to 500 UEs. Now that 400 has been accessed, the load is 400/500. Serv _latency indicates the delay parameter of the service.

It can be seen from the formula (2) that the lower the position where the UP-GW is located, that is, the closer to the mobile user, the greater the weight value; or the service attribute of the data network connected by the UP-GW is the low-latency service, the weight value The larger the historical average rate of data transmission on the non-GBR bearer between the UE and the UP-GW, that is, the stronger the performance, the larger the weight value; or the less the load of the UP-GW, the weight The bigger the value, etc.

It should be noted that, the method for dynamically acquiring the weight of each UP-GW in the service UP-GW may be obtained one or more times according to the foregoing network parameter after the UE selects the service UP-GW, and this embodiment of the present application No specific limitation.

Since the above-mentioned dynamically acquiring the weight of each UP-GW takes into account the current network parameters of each UP-GW, it is possible to make the AM function allocated by the CP function entity for each UP-GW in the serving UP-GW more in line with each The actual situation of the UP-GW, that is to say, the result of the allocation is more precise, so that the control of the AMBR for data transmission on the non-GBR bearer between the UE and each UP-GW is also more accurate.

For example, FIG. 4 is an example in which the CP function entity selects UP-GW1 and UP-GW2 as the UE's service UP-GW for the UE, and the first UP-GW in the above solution is any one of the service UP-GWs. Therefore, for UP-GW1, the CP function entity receives the network parameter sent by the first UP-GW; determines the weight of the first UP-GW according to the network parameter of the first UP-GW, and actually the CP function entity receives the UP-GW1. The transmitted network parameters; the weight of the UP-GW1 is determined according to the network parameters of the UP-GW1. For the UP-GW2, the CP function entity receives the network parameter sent by the first UP-GW; determines the weight of the first UP-GW according to the network parameter of the first UP-GW, and actually the CP function entity receives the UP-GW2 transmission. Network parameters; determine the weight of UP-GW2 according to the network parameters of UP-GW2. Wherein, according to the network parameters of the UP-GW1, the weight of the UP-GW1 is determined; and, according to the UP-GW2 For the network parameter, the method for determining the weight of the UP-GW2 can be referred to the formula (2), and details are not described herein again.

Optionally, in the foregoing step S304, the CP function entity acquires the AMBR of the data transmission between the UE and the target DN according to the identifier of the target DN, and specifically includes:

The CP function entity searches for the correspondence between the identifier of the pre-configured DN and the AMBR of the data transmission between the UE and the DN according to the identifier of the target DN, and obtains the AMBR for data transmission between the UE and the target DN.

Of course, the CP function entity may obtain the AMBR of the data transmission between the UE and the target DN in other manners according to the identifier of the target DN, which is not specifically limited in this embodiment.

Optionally, in step S305, the product of the normalized weight of the serving UP-GW and the AMBR of the data transmission between the UE and the target DN may be used as the data transmission on the non-GBR bearer between the UE and the serving UP-GW. AMBR.

For the convenience of the description, the embodiment of the present application can record the AMBR of the data transmission between the UE and the target DN as AMBR0, and record the AMBR of the data transmission on the non-GBR bearer between the UE and the UP-GW1 as the AMBR1, and the UE The AMBR of the data transmission on the non-GBR bearer between the UP and the GW2 is referred to as AMBR2, and is collectively described herein, and will not be described below.

Exemplarily, the AMBR of the data transmission on the non-GBR bearer between the UE and each of the UP-GWs in the serving UP-GW may be calculated based on the formula (3):

AMBRn=ω(n)×AMBR0, formula (3)

Where ω(n) represents the normalized weight of the nth UP-GW in the serving UP-GW; AMBRn represents the data transmission on the non-GBR bearer between the UE and the nth UP-GW in the serving UP-GW AMBR.

For example, if AMBR0 is 100 Mbit/s, UP-GW1 has a normalized weight ω(1) of 0.4, and UP-GW2 has a normalized weight ω(2) of 0.6, based on formula (3), AMBR1 is 40 Mbit/s, AMBR2 is 60 Mbit/s.

Optionally, after step S307 of the embodiment shown in FIG. 3, the foregoing method may further include steps S308-S309.

S308. After configuring the AMBR for data transmission on the non-GBR bearer between the UE and the first UP-GW, the UE sends a Direct Transfer message to the RAN access point, where the RAN access point receives the direct transmission message. .

The direct transmission message includes a session management response (Session Management Response) message.

S309. The RAN access point sends a session management response message to the CP function entity, and the CP function entity receives the session management response message, so that the CP function entity learns that the UE completes the AMBR update.

Optionally, in an implementation scenario of the foregoing embodiment, the foregoing method may further include:

The CP function entity acquires subscription data of the UE, and the subscription data includes an additional AMBR for data transmission on the non-GBR bearer between the UE and the first UP-GW.

Furthermore, in step S305, the CP function entity determines the data transmission on the non-GBR bearer between the UE and the first UP-GW according to the normalized weight of the first UP-GW and the AMBR of the data transmission between the UE and the target DN. The AMBR can specifically include:

The CP function entity determines an intermediate AMBR for data transmission on the non-GBR bearer between the UE and the first UP-GW according to the normalized weight of the first UP-GW and the AMBR of the data transmission between the UE and the target DN;

The CP functional entity adds the intermediate AMBR of the data transmission on the non-GBR bearer between the UE and the first UP-GW, and the additional AMBR of the data transmission on the non-GBR bearer between the UE and the first UP-GW Obtaining an AMBR for data transmission on a non-GBR bearer between the UE and the first UP-GW.

The additional AMBR is also used for the transmission of data on the non-GBR bearer between the UE and the first UP-GW. For example, if the first UP-GW is located at the edge of the network and is close to the user, the HD video is specifically provided for the mobile user. To ensure the user's smooth experience, there is no sticking when watching the video, and each user can be assigned an additional AMBR of 50 Mbps, thereby ensuring how much the UP-GW obtains in the AMBR of data transmission between the UE and the target DN in the future. Rate quota. If the user is downloading files through the UP-GW, the 50 Mbps additional AMBR can meet the basic HD video rate requirements, avoiding the allocation rate. Insufficient amount leads to the occurrence of the Caton situation.

It should be noted that the processor 201 in the computer device 200 shown in FIG. 2 can call the application code stored in the memory 203 to perform the action or the step of the CP function entity in the embodiment shown in FIG. There are no restrictions on this.

As shown in FIG. 4, a schematic flowchart of a method for controlling a data transmission rate on a non-GBR bearer provided by an embodiment of the present application, selects UP-GW1 and UP-GW2 as the service UP of the UE by using the CP functional entity for the UE. The GW is described as an example. The method specifically includes the following steps.

S401. The CP function entity receives an identifier of a target DN sent by the UE.

S402. The CP functional entity selects UP-GW1 and UP-GW2 as the serving UP-GW of the UE according to the identifier of the target DN.

S403. The CP function entity acquires the normalized weight of the UP-GW1 and the normalized weight of the UP-GW2.

In step S403, the normalized weights of UP-GW1 and UP-GW2 can be obtained through the implementation provided in step S303, and details are not described herein.

S404. The CP functional entity acquires AMBR0 according to the identifier of the target DN.

The embodiment of the present application can record the AMBR of the data transmission between the UE and the target DN as AMBR0, and record the AMBR of the data transmission on the non-GBR bearer between the UE and the UP-GW1 as AMBR1, and between the UE and the UP-GW2. The non-GBR carries the AMBR2 on the data transmission.

S405a. The CP functional entity determines AMBR1 according to the normalized weights of AMBR0 and UP-GW1.

S405b. The CP functional entity determines AMBR2 according to the normalized weights of AMBR0 and UP-GW2.

Specifically, the foregoing steps S405a and S405b may be specifically implemented as follows:

The CP function entity acquires subscription data of the UE, where the subscription data includes an additional AMBR for data transmission on the non-GBR bearer between the UE and the UP-GW1, and the UE and the UE The non-GBR between UP-GW2 carries an additional AMBR for data transmission.

For convenience of description, the embodiment of the present application may record the additional AMBR for data transmission on the non-GBR bearer between the UE and the UP-GW1 as AMBR1-1; on the non-GBR bearer between the UE and the UP-GW2 The additional AMBR for data transmission is referred to as AMBR2-1, which is hereby uniformly described, and will not be described below.

The CP functional entity adds the intermediate AMBR1-2 and AMBR1-1 of the data transmission on the non-GBR bearer between the UE and the UP-GW1 to obtain the AMBR1; and will be on the non-GBR bearer between the UE and the UP-GW2. The intermediate AMBR2-2 and AMBR2-1 of the data transmission are added to obtain AMBR2.

AMBR2 = AMBR2-2+AMBR2-1.

For example, if AMBR1-1=10 Mbit/s, AMBR1-2 is 40 Mbit/s, AMBR1=50 Mbit/s; if AMBR2-1=0 Mbit/s, AMBR2-2 is 60 Mbit/s, then AMBR2=60 Mbit/s.

It should be noted that, in the calculation manner of the AMBR1-2 and the AMBR2-2 in the embodiment of the present application, reference may be made to the above formula (3), and details are not described herein again.

In addition, the use of additional AMBR guarantees the special needs of special users and avoids the occurrence of traffic jams due to insufficient rate quotas allocated.

S406a, the CP functional entity sends AMBR1 to UP-GW1.

S406b, the CP functional entity sends AMBR2 to UP-GW2.

For example, the CP function entity may carry the identifier of the UE and the AMBR1 in a tunnel setup message sent to the UP-GW1, and may carry the UE in a tunnel setup message sent to the UP-GW2. The identifier and the AMBR2 are not specifically limited in this embodiment of the present application.

The S407a, the CP functional entity sends the AMBR1 to the UE.

S407b. The CP functional entity sends the AMBR2 to the UE.

It should be noted that, in the embodiment shown in FIG. 4, the CP function entity may send the AMBR1 and the AMBR2 to the UE at the same time, that is, the AMBR1 and the AMBR2 are carried in the same message. It is sent to the UE; the AMBR1 and the AMBR2 may be separately sent to the UE, which is not specifically limited in this embodiment of the present application.

For example, the CP function entity may carry the AMBR1 and the AMBR2 in a Session Management Request message sent to the RAN access point, and the Radio Resource Control (RRC) sent by the RAN access point to the UE In the configuration message, the AMBR1 and the AMBR2 are notified to the UE, which is not specifically limited in this embodiment of the present application.

It should be noted that there is no necessary execution sequence between steps S405a and S405b in the embodiment shown in FIG. 4, and there is no necessary execution sequence between steps S406, S406b, S407a and S407b, and between steps S402 and S404. There is no necessary execution sequence; for example, step S405a may be performed first, and then step S405b may be performed; step S405b may be performed first, and then step S405a may be performed; and steps S405a and S405b may be performed simultaneously, which is performed by the embodiment of the present application. No specific limitation.

Optionally, after steps S407a and S407b of the embodiment shown in FIG. 4, the following steps may be further included:

S408. After configuring the AMBR1 and the AMBR2, the UE sends a direct transmission message to the RAN access point, and the RAN access point receives the direct transmission message. The direct transmission message includes a session management response message.

S409. The RAN access point sends a session management response message to the CP function entity, where the CP function entity receives the session management response message, so that the CP function entity learns that the UE completes the AMBR update.

The processor 201 in the computer device 200 shown in FIG. 2 can call the application code stored in the memory 203 to perform the action of the CP function entity in the embodiment shown in FIG. 4, which is not limited in this embodiment.

FIG. 5 is a schematic flowchart of a method for controlling a data transmission rate on another non-GBR bearer according to an embodiment of the present application, where the CP function entity selects a service UP-GW in the embodiment shown in FIG. The CP function entity is based on the new service request, and the new UP-GW is added as the service UP-GW as an example, including the following steps:

S501. The CP function entity receives a service request of the UE.

The service request of the UE is used to request a new service. For example, in the embodiment shown in FIG. 3, if the service UP-GW selected by the CP function entity for the UE cannot provide the video service, and the user needs the video service, the UE may apply to the CP. The functional entity sends a service request, and the service request of the UE is used to request a video service.

S502. The CP function entity selects a second UP-GW for the UE according to the service request of the UE and the identifier of the target DN.

The identifier of the target DN is the identifier of the target DN received in step S301 in the embodiment shown in FIG. 3, and details are not described herein.

In step S502, the second UP-GW may be selected for the UE by using the implementation provided in step S302, and details are not described herein.

Exemplarily, after the UE selects UP-GW1 and UP-GW2 as the serving UP-GW of the UE, FIG. 4 selects UP-GW3 as the second UP- based on the service request of the UE and the identifier of the target DN. GW. Specifically, reference may be made to step S602 in the embodiment shown in FIG. 6.

Optionally, the embodiment of the present application may also select a second UP-GW for the UE based on the offload requirement and the identifier of the target DN, which is not specifically limited in this embodiment of the present application.

S503. The CP functional entity acquires a normalized weight of the second UP-GW.

In step S503, the normalized weight of the second UP-GW can be obtained through the implementation provided in step S303, and details are not described herein.

Specifically, reference may be made to step S603 in the embodiment shown in FIG. 6.

S504: The CP function entity updates the normalized weight of the first UP-GW, and obtains the updated normalized weight of the first UP-GW.

In step S504, the normalized weight of the first UP-GW may be updated by the implementation provided in step S303, and details are not described herein.

Specifically, reference may be made to step S604a or S604b in the embodiment shown in FIG. 6.

S505. The CP functional entity is determined according to the normalized weight of the second UP-GW and the AMBR0. An AMBR for data transmission on a non-GBR bearer between the UE and the second UP-GW.

In step S505, the AMBR of the data transmission on the non-GBR bearer between the UE and the second UP-GW may be determined by the implementation provided in step S305, and details are not described herein.

Specifically, reference may be made to step S605 in the embodiment shown in FIG. 6.

For the convenience of the description, the AMBR of the data transmission on the non-GBR bearer between the UE and the UP-GW3 can be referred to as the AMBR3 in the embodiment of the present application.

S506. The CP function entity updates the AMBR of the data transmission on the non-GBR bearer between the UE and the first UP-GW according to the updated normalized weight and AMBR0, and obtains the updated AMBR.

In step S506, the AMBR of the data transmission on the non-GBR bearer between the UE and the first UP-GW may be updated by the implementation provided in step S305, and details are not described herein.

Specifically, reference may be made to step S606a or S606b in the embodiment shown in FIG. 6.

For details of the AMBR0 in the step S505 and the step S506, refer to the related description in the embodiment shown in FIG.

S507. The CP function entity sends the AMBR of the data transmission on the non-GBR bearer between the UE and the second UP-GW to the second UP-GW.

Specifically, reference may be made to step S607 in the embodiment shown in FIG. 6.

S508. The CP function entity sends the updated AMBR to the first UP-GW.

Specifically, reference may be made to step S608a or S608b in the embodiment shown in FIG. 6.

S509: The CP function entity sends the AMBR of the data transmission on the non-GBR bearer between the UE and the second UP-GW to the UE.

Specifically, reference may be made to step S609 in the embodiment shown in FIG. 6.

For example, the CP function entity may carry the identifier of the UE and the AMBR3 in the tunnel setup message sent to the UP-GW3, which is not specifically limited in this embodiment of the present application.

S510. The CP function entity sends the updated AMBR to the UE.

Specifically, reference may be made to step S610a or S610b in the embodiment shown in FIG. 6.

In the embodiment shown in FIG. 5, steps S504, S506, and S508 are optional steps for determining that the normalized weight of the first UP-GW is relative to when the second UP-GW is not added as the serving UP-GW. Whether the value changes, when the change occurs, the normalized weight of the first UP-GW is updated, thereby updating the AMBR of the data transmission on the non-GBR bearer between the UE and the first UP-GW.

In the embodiment shown in FIG. 5, the order of execution of steps S503 and S504 is not limited, and the order of execution of steps S505 and S506 is not limited, and the order of execution of steps S507, S508, S509, and S510 is not limited. For example, step S503 may be performed first, and then step S504 may be performed; step S504 may be performed first, and then step S503 may be performed; obviously, steps S503 and S504 may also be performed simultaneously.

Based on the control method of the data transmission rate on the non-GBR bearer provided by the embodiment of the present application, when multiple UP-GWs are selected for one DN requested by the UE, on the one hand, not only the data between the UE and the DN can be controlled. The transmitted AMBR may also control the AMBR of the data transmission on the non-GBR bearer between the UE and each of the plurality of UP-GWs, so that different paths between the UE and one DN may be satisfied. Business needs. On the other hand, since the current network architecture and network element deployment are not changed, there is no uncontrollable factor or additional burden for the mobile network, and the transmission path length is not increased due to technical reasons, affecting some low times. The performance of the extended service has no effect on other traditional gateway technologies and security mechanisms. On the other hand, this method is convenient to expand. A new UP-GW is selected, which can easily be used on the non-GBR bearer between the UE and the UP-GW. AMBR for data transmission.

Optionally, after step S510 of the embodiment shown in FIG. 5, the following steps may be further included:

S511. After the UE configures the AMBR for data transmission on the non-GBR bearer between the UE and the second UP-GW, the UE sends a direct transmission message to the RAN access point, and the RAN access point receives the direct transmission message. The direct transmission message includes a session management response message.

S512. The RAN access point sends a session management response message to the CP function entity, where the CP function entity receives the session management response message, so that the CP function entity learns that the UE is completed. AMBR update.

The CP function entity acquires subscription data of the UE, and the subscription data includes an additional AMBR for data transmission on the non-GBR bearer between the UE and the second UP-GW.

In the step S505, the CP function entity determines the AMBR of the data transmission on the non-GBR bearer between the UE and the second UP-GW according to the normalized weight of the second UP-GW and the AMBR0, which may specifically include:

The CP function entity determines an intermediate AMBR for data transmission on the non-GBR bearer between the UE and the second UP-GW according to the normalized weight of the second UP-GW and the AMBR of the data transmission between the UE and the target DN;

The CP functional entity adds the intermediate AMBR of the data transmission on the non-GBR bearer between the UE and the second UP-GW, and the additional AMBR of the data transmission on the non-GBR bearer between the UE and the second UP-GW Obtaining an AMBR for data transmission on a non-GBR bearer between the UE and the second UP-GW.

The additional AMBR is also used for the transmission of data on the non-GBR bearer between the UE and the second UP-GW. For example, if the second UP-GW is located at the edge of the network and is close to the user, the HD video is specifically provided for the mobile user. To ensure the user's smooth experience, there is no sticking when watching the video, and each user can be assigned an additional AMBR of 50 Mbps, thereby ensuring how much the UP-GW obtains in the AMBR of data transmission between the UE and the target DN in the future. Rate quota. If the user is downloading files through the UP-GW, the 50 Mbps additional AMBR can meet the requirements of the basic HD video rate, avoiding the occurrence of a stuck condition due to insufficient allocated rate quota.

FIG. 6 is a schematic flowchart of a method for controlling a data transmission rate on a non-GBR bearer according to an embodiment of the present application. The CP function entity selects UP-GW1 and UP-GW2 as UEs in FIG. After serving the UP-GW, select UP-GW3 as the UE for the UE. The second UP-GW is described as an example. The method specifically includes the following steps:

S601. The CP function entity receives a service request of the UE.

S602. The CP function entity selects the UP-GW3 as the second UP-GW for the UE according to the service request of the UE and the identifier of the target DN.

S603. The CP functional entity acquires a normalized weight of the UP-GW3.

In step S603, the normalized weight of the UP-GW 3 can be obtained through the implementation provided in step S303, and details are not described herein.

S604a, the CP functional entity updates the normalized weight of the UP-GW1, and obtains the updated normalized weight of the UP-GW1.

In step S604a, the normalized weight of the UP-GW1 can be updated by the implementation provided in step S303, and details are not described herein again.

S604b, the CP function entity updates the normalized weight of the UP-GW2, and obtains the updated normalized weight of the UP-GW2.

In step S604b, the normalized weight of UP-GW2 can be updated by the implementation provided in step S303, and details are not described herein.

It should be noted that, since FIG. 6 is that the CP function entity in FIG. 4 selects UP-GW1 and UP-GW2 as the service UP-GW for the UE, based on the new service request, the newly added UP-GW3 is the service UP-GW. For example, when determining the normalized weight of the UP-GW 3 (step S603), updating the normalized weight of the UP-GW 1 (step S604a), and updating the normalized weight of the UP-GW 2 (step S604b), The service UP-GW of the corresponding UE includes: UP-GW1, UP-GW2, and UP-GW3. That is, when the normalized weight of the UP-GW is calculated based on the formula (1), N=3.

For example, if UP-GW3 is added as the second UP-GW, the weight of UP-GW1 is 0.2, the weight of UP-GW2 is 0.3, and the weight of UP-GW3 is 0.5, which is available based on formula (1), UP- The normalized weight ω(1) of GW1 is 0.2, the normalized weight ω(2) of UP-GW2 is 0.3, and the normalized weight ω(3) of UP-GW3 is 0.5. Alternatively, if the weight of UP-GW1 is 2, the weight of UP-GW2 is 3, and the weight of UP-GW3 is 5, it is available based on formula (1), and the normalized weight ω(1) of UP-GW1 is 0.2. , UP-GW2's normalized weight ω(2) is 0.3, UP-GW3 The normalized weight ω(3) is 0.5.

S605. The CP functional entity determines AMBR3 according to the normalized weight of the UP-GW3 and the AMBR0.

In step S605, the AMBR3 may be determined by the implementation provided in step S305, and details are not described herein.

For example, if AMBR0 is 100 Mbit/s and UP-GW3 has a normalized weight ω(3) of 0.3, it is available based on equation (3), and AMBR3 is 30 Mbit/s.

Alternatively, optionally, step S605 can be implemented as follows:

The CP function entity acquires subscription data of the UE, and the subscription data includes an additional AMBR for data transmission on the non-GBR bearer between the UE and the UP-GW3.

For convenience of description, the embodiment of the present application can record the additional AMBR of data transmission on the non-GBR bearer between the UE and the UP-GW3 as AMBR3-1, and will be on the non-GBR bearer between the UE and the UP-GW3. The intermediate AMBR of the data transmission is referred to as AMBR3-2, which is uniformly described herein, and will not be described below.

The CP functional entity adds AMBR3-2 and AMBR1-1 to obtain AMBR1. That is, AMBR3 = AMBR3-2+AMBR3-1.

For example, if AMBR3-1=10 Mbit/s and AMBR3-2 is 30 Mbit/s, AMBR3=40 Mbit/s.

For the calculation method of the AMBR 3-2 in the embodiment of the present application, reference may be made to the above formula (3), and details are not described herein again.

S606a, the CP functional entity updates AMBR1 according to the updated normalized weight and AMBR0, and obtains the updated AMBR1.

In step S606a, the AMBR1 may be updated by the implementation provided in step S305, and details are not described herein.

For example, if AMBR0 is 100 Mbit/s, UP-GW1's updated normalized weight ω(1) If it is 0.3, it is obtained based on formula (3), and the updated AMBR1 is 30 Mbit/s.

S606b, the CP functional entity updates AMBR2 according to the updated normalized weight and AMBR0, and obtains the updated AMBR2.

In step S606b, AMBR2 may be updated by the implementation provided in step S305, and details are not described herein.

For example, if AMBR0 is 100 Mbit/s and UP-GW2's updated normalized weight ω(2) is 0.4, it is available based on equation (3), and the updated AMBR2 is 40 Mbit/s.

For details of the AMBR0 in the steps S605, S606a, and S606b, refer to the related description in the embodiment shown in FIG.

S607. The CP functional entity sends the AMBR3 to the UP-GW3.

For example, the CP function entity may carry the identifier of the UE and the AMBR 34 in the tunnel setup message sent to the UP-GW 3, which is not specifically limited in this embodiment of the present application.

The S608a and the CP function entity send the updated AMBR1 to the UP-GW1.

For example, the CP function entity may carry the identifier of the UE and the updated AMBR1 in the Tunnel Updata message sent to the UP-GW1, which is not specifically limited in this embodiment of the present application.

The S608b and the CP functional entity send the updated AMBR2 to the UP-GW2.

For example, the CP function entity may carry the identifier of the UE and the updated AMBR2 in the Tunnel Updata message sent to the UP-GW2, which is not specifically limited in this embodiment of the present application.

S609. The CP functional entity sends the AMBR3 to the UE.

For example, the CP function entity may carry the AMBR3 in the session management request message sent to the RAN access point, and the RAN access point notifies the UE to the UE in the RRC configuration message sent to the UE. This is not specifically limited.

The S610a, the CP functional entity sends the updated AMBR1 to the UE.

The S610b and the CP function entity send the updated AMBR2 to the UE.

It should be noted that, in the embodiment shown in FIG. 6, the CP function entity may send the updated AMBR1 and the updated AMBR2 to the UE at the same time, that is, the updated AMBR1 and the updated AMBR2 are carried in the same message. For the UE, the updated AMBR1 and the updated AMBR2 may be separately sent to the UE, which is not specifically limited in this embodiment of the present application.

For example, the CP function entity may carry the updated AMBR1 and the updated AMBR2 in the session management request message sent to the RAN access point, and the RAN access point is updated in the RRC configuration message sent to the UE. The AMBR1 and the updated AMBR2 are notified to the UE, which is not specifically limited in this embodiment of the present application.

In the embodiment shown in FIG. 6, steps S604a, S604b, S606a, S606b, S608a, and S608b are optional steps for determining that the normalized weights of UP-GW1 and UP-GW2 are not added to UP-GW3. Whether the value as the second UP-GW changes, when the change occurs, the normalized weights of UP-GW1 and UP-GW2 are updated, thereby updating the non-GBR bearer between the UE and UP-GW1 and UP-GW2. AMBR on data transmission.

In the embodiment shown in FIG. 6, the order of execution of steps S603, S604a, and S604b is not limited, and the order of execution of steps S605, S606a, and S606b is not limited, and steps S607, S608a, S608b, S609, S610a, and S610b are omitted. The order of execution is not limited. For example, any one of steps S603, S604a, and S604b may be performed first, then any one of the remaining two steps may be performed, and finally the remaining one step is performed; obviously, steps S603, S604a, and S604b may also be performed simultaneously. The application examples are not specifically limited thereto.

Optionally, after step S609 of the embodiment shown in FIG. 6, the following steps may be further included:

S611. After configuring the AMBR3, the UE sends a direct transmission message to the RAN access point, and the RAN access point receives the direct transmission message. The direct transmission message includes a session management response message.

S612. The RAN access point sends a session management response message to the CP function entity, and the CP function entity receives the session management response message, so that the CP function entity learns that the UE completes the AMBR update.

Wherein, the processor 201 in the computer device 200 shown in FIG. 2 can call the memory. The application code stored in 203 is used to perform the action of the CP function entity in the embodiment shown in FIG. 6, which is not limited in this embodiment.

The solution provided by the embodiment of the present application is mainly introduced from the perspective of interaction between the network elements. It can be understood that, in order to implement the above functions, the above-mentioned CP functional entity includes hardware structures and/or software modules corresponding to each function. Those skilled in the art will readily appreciate that the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.

The embodiment of the present application may divide the function module of the CP function entity according to the foregoing method example. For example, each function module may be divided according to each function, or two or more functions may be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.

For example, in the case of dividing each functional module by corresponding functions, FIG. 7 shows a possible structural diagram of the CP functional entity 70 involved in the above embodiment. As shown in FIG. 7, the CP functional entity 70 may include a receiving module 701, a selecting module 702, an obtaining module 703, a determining module 704, and a sending module 705.

Optionally, the CP functional entity 70 further includes an update module 706.

The receiving module 701 is configured to support the CP function entity 70 to perform step S301 in FIG. 3, step S401 in FIG. 4, step S501 in FIG. 5, and step S601 in FIG.

The selection module 702 is configured to support the CP function entity 70 to perform step S302 in FIG. 3, step S402 in FIG. 4, step S502 in FIG. 5, and step S602 in FIG.

The acquisition module 703 is configured to support the CP function entity 70 to perform steps S303 and S304 in FIG. 3, steps S403 and S404 in FIG. 4, step S503 in FIG. 5, and step S603 in FIG.

The determination module 704 is configured to support the CP function entity 70 to perform step S305 in FIG. 3, steps S405a and S405b in FIG. 4, step S505 in FIG. 5, and step S605 in FIG.

The sending module 705 is configured to support the CP function entity 70 to perform steps S306 and S307 in FIG. 3, steps S406a, S406b, S407a, and S407b in FIG. 4, steps S507-S510 in FIG. 5, and step S607 in FIG. S608a, S608b, S609, S610a, and S610b.

The update module 706 is configured to support the CP function entity 70 to perform steps S504 and S506 in FIG. 5, steps S604a, S604b, S606a, and S606b in FIG.

All the related content of the steps involved in the foregoing method embodiments may be referred to the functional descriptions of the corresponding functional modules, and details are not described herein again.

The CP function entity provided by the embodiment of the present application can be used to perform the foregoing method for controlling the data transmission rate on the non-GBR bearer. Therefore, the technical solution can be obtained by referring to the foregoing method embodiment. .

The embodiment of the present application further provides a computer storage medium for storing computer software instructions used by the CP functional entity, which includes a program designed to execute the foregoing method embodiments. By executing the stored program, a control method of the data transmission rate on the non-GBR bearer can be realized.

The embodiment of the present application further provides a computer program, which includes instructions, when the computer program is executed by a computer, to enable the computer to execute the flow of the foregoing method embodiment.

The computer storage medium and the computer program provided by the embodiments of the present application can be used to perform the foregoing method for controlling the data transmission rate on the non-GBR bearer. Therefore, the technical effects of the present invention can be obtained by referring to the foregoing method embodiments. No longer.

Although the present application has been described herein in connection with the various embodiments, those skilled in the art can Other variations of the disclosed embodiments are achieved. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit may implement the recited in the claims Several features. Certain measures are recited in mutually different dependent claims, but this does not mean that the measures are not combined to produce a good effect.

Those skilled in the art will appreciate that embodiments of the present application can be provided as a method, apparatus (device), or computer program product. Thus, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware. Moreover, the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code. The computer program is stored/distributed in a suitable medium, provided with other hardware or as part of the hardware, or in other distributed forms, such as over the Internet or other wired or wireless telecommunication systems.

The present application is described with reference to flowchart illustrations and/or block diagrams of the methods, apparatus, and computer program products of the embodiments of the present application. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

While the present invention has been described in connection with the specific embodiments and embodiments thereof, various modifications and combinations can be made without departing from the spirit and scope of the application. Corresponding The specification and drawings are merely illustrative of the invention, and are intended to be It will be apparent to those skilled in the art that various modifications and changes can be made in the present application without departing from the spirit and scope of the application. Thus, it is intended that the present invention cover the modifications and variations of the present invention.

Claims

A method for controlling a data transmission rate on a non-guaranteed bit rate non-GBR bearer, the method comprising:

The control plane CP function entity receives the identifier of the target data network DN sent by the user equipment UE, and the identifier of the target DN is used to indicate the DN that the UE requests to access;

The CP function entity selects a serving user plane gateway UP-GW for the UE according to the identifier of the target DN, and acquires a normalized weight of the service UP-GW;

The CP function entity acquires an aggregate maximum bit rate AMBR of data transmission between the UE and the target DN according to the identifier of the target DN;

Determining, by the CP functional entity, a non- between the UE and the first UP-GW according to a normalized weight of the first UP-GW and an AMBR of data transmission between the UE and the target DN The GBR carries an AMBR for data transmission, and the first UP-GW is any one of the serving UP-GWs;

The CP function entity sends an AMBR that transmits data on the non-GBR bearer between the UE and the first UP-GW to the first UP-GW and the UE.
The method according to claim 1, wherein the CP function entity acquires the normalized weight of the service UP-GW, including:

The CP function entity acquires a weight of the service UP-GW;

The CP function entity normalizes each UP-GW in the service UP-GW according to the weight of the service UP-GW, and obtains a normalized weight of the service UP-GW.
The method according to claim 2, wherein the CP function entity acquires the weight of the service UP-GW, including:

Obtaining, by the CP function entity, a weight of the service UP-GW preconfigured in the CP function entity; or

The CP function entity receives the network parameter sent by the first UP-GW, and determines the weight of the first UP-GW according to the network parameter of the first UP-GW.
The method according to any one of claims 1 to 3, wherein the method further comprises:

The CP function entity acquires the subscription data of the UE, where the subscription data includes an additional AMBR for data transmission on the non-GBR bearer between the UE and the first UP-GW;

Determining, by the CP functional entity, a non- between the UE and the first UP-GW according to a normalized weight of the first UP-GW and an AMBR of data transmission between the UE and the target DN The AMBR for data transmission on the GBR, including:

Determining, between the UE and the first UP-GW, the CP function entity according to the normalized weight of the first UP-GW and the AMBR of data transmission between the UE and the target DN The intermediate AMBR of the data transmission on the non-GBR bearer;

The intermediate function AMBR of the CP function entity transmitting the data on the non-GBR bearer between the UE and the first UP-GW, and the intermediate UE and the first UP-GW The additional AMBRs of the data transmission on the non-GBR bearer are added to obtain an AMBR for data transmission on the non-GBR bearer between the UE and the first UP-GW.
The method according to any one of claims 1 to 4, wherein the method further comprises:

Receiving, by the CP functional entity, a service request of the UE;

The CP function entity selects a second UP-GW for the UE according to the service request of the UE and the identifier of the target DN;

The CP function entity acquires a normalized weight of the second UP-GW;

Determining, between the UE and the second UP-GW, the CP function entity according to the normalized weight of the second UP-GW and the AMBR of data transmission between the UE and the target DN The non-GBR carries the AMBR for data transmission;

The CP function entity sends an AMBR for data transmission on the non-GBR bearer between the UE and the second UP-GW to the second UP-GW and the UE.
The method of claim 5, wherein the method further comprises:

Updating, by the CP function entity, a normalized weight of the first UP-GW, to obtain an updated normalized weight of the first UP-GW;

Updating, by the CP functional entity, a non-GBR between the UE and the first UP-GW according to the updated normalized weight and an AMBR of data transmission between the UE and the target DN Carrying the AMBR of the data transmission, and obtaining the updated AMBR;

The CP function entity sends the updated AMBR to the first UP-GW and the UE.
The method according to claim 5 or 6, wherein the method further comprises:

The CP function entity acquires the subscription data of the UE, where the subscription data includes an additional AMBR for data transmission on the non-GBR bearer between the UE and the second UP-GW;

Determining, between the UE and the second UP-GW, the CP function entity according to the normalized weight of the second UP-GW and the AMBR of data transmission between the UE and the target DN The non-GBR carries the AMBR for data transmission, including:

Determining, between the UE and the second UP-GW, the CP function entity according to the normalized weight of the second UP-GW and the AMBR of data transmission between the UE and the target DN The intermediate AMBR of the data transmission on the non-GBR bearer;

The intermediate function AMBR of the CP function entity transmitting data on the non-GBR bearer between the UE and the second UP-GW, and the said UE and the second UP-GW The additional AMBRs of the data transmission on the non-GBR bearer are added to obtain an AMBR for data transmission on the non-GBR bearer between the UE and the second UP-GW.
A control plane CP functional entity, wherein the CP functional entity comprises: a receiving module, an obtaining module, a determining module, a selecting module, and a sending module;

The receiving module is configured to receive an identifier of a target data network DN sent by the user equipment UE, where the identifier of the target DN is used to indicate a DN that the UE requests to access;

The selecting module is configured to select a serving user plane gateway UP-GW for the UE according to the identifier of the target DN received by the receiving module;

The obtaining module is configured to obtain a normalized weight of the service UP-GW selected by the selection module;

The acquiring module is further configured to acquire, according to the identifier of the target DN received by the receiving module, an aggregate maximum bit rate AMBR of data transmission between the UE and the target DN;

The determining module is configured to determine, according to the normalized weight of the first UP-GW acquired by the acquiring module, and the AMBR of data transmission between the UE and the target DN, to determine the UE and the first The non-guaranteed bit rate between the UP-GWs carries the AMBR of the data transmission on the non-GBR, and the first UP-GW is any one of the serving UP-GWs;

The sending module is configured to send, to the first UP-GW and the UE, an AMBR that transmits data on a non-GBR bearer between the UE and the first UP-GW determined by the determining module .
The CP functional entity according to claim 8, wherein the acquisition module Obtaining a normalized weight of the service UP-GW selected by the selection module, including:

Obtaining a weight of the service UP-GW selected by the selection module;

Each UP-GW in the service UP-GW is separately normalized according to the weight of the serving UP-GW, and the normalized weight of the service UP-GW is obtained.
The CP function entity according to claim 9, wherein the obtaining module obtains the weight of the service UP-GW selected by the selection module, including:

Obtaining a weight of the service UP-GW selected by the selection module pre-configured in the CP functional entity; or

Receiving, by the first UP-GW, a network parameter, and determining, according to the network parameter of the first UP-GW, a weight of the first UP-GW.
A CP functional entity according to any one of claims 8 to 10, characterized in that

The acquiring module is further configured to acquire the subscription data of the UE, where the subscription data includes an additional AMBR for data transmission on the non-GBR bearer between the UE and the first UP-GW;

Determining, by the determining module, that the UE and the first UP-GW are determined according to a normalized weight of the first UP-GW acquired by the acquiring module and an AMBR of data transmission between the UE and the target DN The non-GBR carries the AMBR on the data transmission, including:

Determining non between the UE and the first UP-GW according to the normalized weight of the first UP-GW acquired by the acquiring module and the AMBR of data transmission between the UE and the target DN - the intermediate AMBR of the data transmission on the GBR bearer;

An intermediate AMBR that transmits data on the non-GBR bearer between the UE and the first UP-GW, and the non-GBR between the UE and the first UP-GW The additional AMBRs carrying the data transmissions are added to obtain an AMBR for data transmission on the non-GBR bearer between the UE and the first UP-GW.
A CP functional entity according to any one of claims 8-11, characterized in that

The receiving module is further configured to receive a service request of the UE;

The selecting module is further configured to select a second UP-GW for the UE according to the service request of the UE and the identifier of the target DN received by the receiving module;

The obtaining module is further configured to obtain a normalized weight of the second UP-GW selected by the selecting module;

The determining module is further configured to determine, according to the normalized weight of the second UP-GW acquired by the acquiring module, and the AMBR of data transmission between the UE and the target DN, to determine the UE and the An AMBR for data transmission on a non-GBR bearer between the second UP-GW;

The sending module is further configured to send, to the second UP-GW, the AMBR that transmits data on the non-GBR bearer between the UE and the second UP-GW determined by the determining module UE.
The CP functional entity according to claim 12, wherein the CP functional entity further comprises an update module;

The update module is configured to update a normalized weight of the first UP-GW, and obtain an updated normalized weight of the first UP-GW;

The update module is further configured to update, between the UE and the first UP-GW, according to the updated normalized weight and an AMBR of data transmission between the UE and the target DN. The non-GBR carries the AMBR of the data transmission, and obtains the updated AMBR;

The sending module is further configured to send the updated AMBR that is updated by the update module to the first UP-GW and the UE.
A CP functional entity according to claim 12 or 13, characterized in that

The acquiring module is further configured to acquire the subscription data of the UE, where the subscription data includes an additional AMBR for data transmission on the non-GBR bearer between the UE and the second UP-GW;

Determining, by the determining module, the UE and the second UP according to the normalized weight of the second UP-GW acquired by the acquiring module and the AMBR of data transmission between the UE and the target DN - AMBR on the non-GBR bearer for data transmission, including:

Determining between the UE and the second UP-GW according to the normalized weight of the second UP-GW acquired by the acquiring module and the AMBR of data transmission between the UE and the target DN The non-GBR bears the intermediate AMBR on the data transmission;

An intermediate AMBR that transmits data on the non-GBR bearer between the UE and the second UP-GW, and the non-GBR between the UE and the second UP-GW The additional AMBRs carrying the data transmissions are added to obtain an AMBR for data transmission on the non-GBR bearer between the UE and the second UP-GW.
A control plane CP functional entity, comprising: a processor, a memory, Bus and communication interface;

The memory is configured to store a computer execution instruction, the processor is connected to the memory through the bus, and when the CP function entity is running, the processor executes the computer execution instruction stored in the memory to And a method of controlling the data transmission rate on the non-guaranteed bit rate non-GBR bearer according to any one of claims 1-7.