WO2021037115A1

WO2021037115A1 - Wireless network resource management method, network system, and related product

Info

Publication number: WO2021037115A1
Application number: PCT/CN2020/111618
Authority: WO
Inventors: 郭�东; 赵文军
Original assignee: 华为技术有限公司
Priority date: 2019-08-30
Filing date: 2020-08-27
Publication date: 2021-03-04
Also published as: CN112449375B; CN112449375A

Abstract

Embodiments of the present invention disclose a wireless network resource management method, a network system, and a related product. The method comprises: an access device receiving data sent to a first terminal device, and obtaining the service type of the data; and obtaining a shared bearer corresponding to the service type, the shared bearer being a bearer established for a second terminal device, and being used to transmit data of the service type. QoS control of the service type may be implemented, and unified QoS control is performed on data of the same service type transmitted by multiple different terminal devices, which helps to save air interface resources, and the total occupation of the air interface resources may be conveniently controlled by the service type.

Description

Wireless network resource management method, network system and related products

This application claims the priority of a Chinese patent application filed with the State Intellectual Property Office of China, the application number is 201910813868.6, and the invention title is "Wireless Network Resource Management Method, Network System and Related Products" on August 30, 2019, and its entire content Incorporated in this application by reference.

Technical field

The present invention relates to the field of communication technology, in particular to a method for managing wireless network resources, a network system and related products.

Background technique

The Third Generation Partnership Project (3GPP) organization defined in the TS23.401 protocol that the data between the user equipment (UE) and the Internet server is in the fourth generation (4G) network The realization of the transmission. The Internet server is a server of a service provider, so it is also called a service provider (service provider, SP) server, or simply a service server or server.

In a 4G network, the network equipment responsible for data transmission between the UE and the Internet server includes a base station (eNodeB), a serving gateway (SGW), and a packet data network (PDN) gateway (PDN GW, PGW). After the UE is connected to the 4G network, an end-to-end default bearer (default bearer) is established between the UE, eNodeB, SGW, and PGW. In order to ensure the quality of service (QoS) of various applications of the UE, when the UE uses various applications, a dedicated bearer can be created to transmit data between the UE application and the server.

3GPP defines QoS information and flow information for proprietary bearers. Among them, the QoS information specifies the transmission quality that the dedicated bearer needs to ensure end-to-end, including: packet delay, packet error loss rate, bit rate, etc.; flow information It is used to specify which application communication data between the UE and the Internet server uses the dedicated bearer for transmission. In addition, the flow information also includes a packet filter. The information in the packet filter includes the Internet protocol (IP) address, subnet mask, protocol number, port range, and UE side port range of the Internet server. ; Among them, the protocol number includes transmission control protocol (transmission control protocol, TCP), user datagram protocol (user datagram protocol, UDP), etc.

After one or more dedicated bearers are established, when the UE or PGW transmits data to the other party, the information in the IP header of the data to be transmitted is matched with the packet filter information of all dedicated bearers. If a certain packet is matched Filter, then put the IP packet on the corresponding dedicated bearer for transmission; if no packet filter is matched, then put the IP packet on the default bearer for transmission. Since the dedicated bearer defines QoS, the transmission of service data on the dedicated bearer will obtain a better service experience than the transmission on the default bearer.

In order to ensure the QoS of the dedicated bearer, it is necessary to reserve air interface resources for the dedicated bearer. The current wireless network resource management method is: when the data flow of the corresponding dedicated bearer does not exceed the guaranteed bit rate (GBR) of the dedicated bearer, All IP packets are allowed to be forwarded. All IP packets are discarded when the maximum bit rate (MBR) is exceeded. When the GBR is not exceeded, the network is congested to determine whether to discard the IP packets.

However, the above methods of wireless network resource management need to reserve more air interface resources for each dedicated bearer, which leads to waste of air interface resources.

Summary of the invention

The technical problem to be solved by the embodiment of the present invention is to provide a wireless network resource management method and related products, which are used to control the service quality of the business and save air interface resources.

In the first aspect, an embodiment of the present invention provides a method for managing wireless network resources, including:

The access device receives data (or called a data message) sent to the first terminal device, and obtains the service type of the data;

Obtaining a shared bearer corresponding to the service type, where the shared bearer is a bearer established for the second terminal device and used to transmit data of the service type;

The data is sent using the shared bearer.

The aforementioned access device may be a base station or an access point (AP), and the base station may be an eNodeB or a NodeB. The foregoing first terminal device may be a terminal device, and the data sent to the first terminal device may be service data sent by the server to the first terminal device. The service type is the attribute of the data, for example: video data service, instant message service, etc. A shared bearer is a bearer named for a purpose. The access device is allocated with air interface resources, bit rate resources, and QoS control resources for the shared bearer. For the first terminal device and the second terminal device, the bearer with the access device is a dedicated bearer.

This embodiment can implement QoS control for service types, and perform unified QoS control on multiple different terminal devices transmitting data of the same service type, which is beneficial to save air interface resources, and can conveniently control the overall occupation of air interface resources by this service type. the amount.

In an optional implementation manner, the obtaining the shared bearer corresponding to the service type includes:

After confirming that the service type belongs to the shared type, the shared bearer is searched for.

As an example of obtaining a shared bearer, this embodiment can quickly determine whether the service type has a shared bearer and which one is the shared bearer.

In an optional implementation manner, before the obtaining the shared bearer corresponding to the service type, the method further includes: receiving, by the access device, service quality information sent by a gateway device, in the service quality information Contains information used to establish the shared bearer for the second terminal device;

Establishing the shared bearer according to the service quality information.

This embodiment provides an implementation manner for establishing a shared bearer. The gateway device initiates the establishment of the shared bearer and specifies QoS information. For the gateway device, the QoS information of a certain service type can be configured locally in the gateway device or specified by other devices. The gateway device may be a PGW, an evolution of the PGW, or a physical device jointly deployed by the PGW and the SGW. The QoS of the shared bearer can be set conveniently on the serving gateway or other devices.

In an optional implementation manner, that the access device receives the service quality information sent by the gateway device, and the service quality information including the information used to establish the shared bearer for the second terminal device includes:

The access device receives the bearer creation request or the bearer update request sent by the gateway device, the bearer context is carried in the bearer creation request or the bearer update request, and the bearer shared quality of service information element is included in the bearer context, and The bearer shared service quality information element includes information used to establish the shared bearer for the second terminal device.

This embodiment provides a specific example in which the gateway device sends the quality of service information to the access device. This implementation method does not need to increase the signaling overhead.

In an optional implementation manner, the inclusion of a bearer shared quality of service information element in the bearer context includes:

The bearer shared quality of service information element is carried in the extended information element of the general packet radio service tunneling protocol control (GTP-C) information element.

This embodiment provides a specific means for carrying shared QoS information elements in the bearer context, which can conveniently carry shared QoS information elements.

In an optional implementation manner, before the access device receives the data sent to the first terminal device, the method further includes:

After receiving the information for establishing the shared bearer for the first terminal device, and after confirming that the maximum number of shared bearers allowed by the shared bearer is not exceeded, count the number of shared bearers that have been used by the shared bearer, and use Establishing the dedicated bearer of the first terminal device by the air interface resources of the shared bearer;

Or, if it is confirmed that the maximum number of bearers allowed by the shared bearer is exceeded, the establishment of a dedicated bearer for the first terminal device is refused.

In this embodiment, after the shared bearer is established, the service quality of the user equipment using the shared bearer can still be guaranteed even when the service type of the shared bearer is overloaded.

In an optional implementation manner, after the shared bearer is established, the method further includes:

After receiving the instruction to delete the dedicated bearer sent by the gateway device, it is confirmed that the number of shared bearers of the shared bearer is greater than 1, then the dedicated bearer between the devices corresponding to the instruction is deleted, and the number of shared bearers is counted ；

Or, if it is confirmed that the number of shared bearers is equal to 1, the shared bearers are deleted.

In this embodiment, the shared bearer can be conveniently managed, the deletion of the shared bearer can be controlled, the service of the terminal device using the shared bearer can be ensured, and the resources of the shared bearer can be released in time. In this embodiment, after receiving the instruction to delete the dedicated bearer, the number of shared bearers of the shared bearer can be reduced by 1, and then it is confirmed whether the number of shared bearers is equal to 0, and if it is not equal to 0, the number of shared bearers corresponding to the instruction can be deleted. Dedicated bearer between devices; or, after receiving the instruction to delete the dedicated bearer, the number of shared bearers of the shared bearer can be reduced by 1, and then confirm whether the number of shared bearers is greater than 0. If so, delete the instruction Dedicated bearer between corresponding devices. These two implementation methods are equivalent to the execution of deleting dedicated bearers when the number of shared bearers is determined to be greater than 1, which is equivalent to counting the number of shared bearers.

In the second aspect, an embodiment of the present invention also provides a method for managing wireless network resources, including:

After receiving the service access initiated by the first terminal device or the second terminal device, the gateway device determines the service type corresponding to the service access;

After confirming that the service type belongs to the shared service type, the gateway device sends service quality information to the access device, and the service quality information includes information used to establish the service for the first terminal device or the second terminal device. Share the information carried.

In an optional implementation manner, the sending quality of service information to the access device, and including information used to establish a shared bearer for the first terminal device or the second terminal device in the quality of service information includes :

Send a bearer creation request or a bearer update request to the access device, the bearer context is carried in the bearer creation request or the bearer update request, and the bearer shared service quality information element is included in the bearer context. The quality information element includes information used to establish the shared bearer for the first terminal device.

In a third aspect, an embodiment of the present invention also provides an access device, including: a data receiving unit, configured to receive data sent to a first terminal device, and obtain a service type of the data;

A bearer obtaining unit, configured to obtain a shared bearer corresponding to the service type, where the shared bearer is a bearer established for the second terminal device and used to transmit data of the service type;

The sending unit is configured to send the data using the shared bearer.

In an optional implementation manner, the bearer obtaining unit is configured to search for the shared bearer after confirming that the service type belongs to the shared type.

In an optional implementation manner, the access device further includes:

The information receiving unit is configured to receive the service quality information sent by the gateway device before the bearer obtaining unit obtains the shared bearer corresponding to the service type, and the service quality information includes information for establishing a service for the second terminal device. The shared bearer information;

The first bearer establishment unit is configured to establish the shared bearer according to the service quality information.

In an optional implementation manner, the information receiving unit is configured to receive a bearer creation request or a bearer update request sent by the gateway device, and the bearer context is carried in the bearer creation request or the bearer update request. Contains a bearer shared quality of service information element, and the bearer shared quality of service information element includes information used to establish the shared bearer for the second terminal device.

In an optional implementation manner, the access device further includes:

The counting unit is configured to confirm that the shared bearer is not exceeded after receiving the information for establishing the shared bearer for the first terminal device before the data receiving unit receives the data sent to the first terminal device After the maximum number of shared bearers allowed, count the number of shared bearers that have been used by the shared bearers;

A second bearer establishment unit, configured to use air interface resources of the shared bearer to establish a dedicated bearer for the first terminal device after confirming that the maximum number of shared bearers allowed by the shared bearer has not been exceeded;

Alternatively, the second bearer establishment unit is configured to confirm that the maximum number of bearers allowed by the shared bearer is exceeded, and then refuse to establish a dedicated bearer for the first terminal device.

In an optional implementation manner, the access device further includes:

A counting confirmation unit, configured to confirm that the number of shared bearers of the shared bearer is greater than 1 after receiving an instruction to delete the dedicated bearer sent by the gateway device after the shared bearer is established;

A bearer control unit, configured to confirm that the number of shared bearers of the shared bearer is greater than one at the counting confirmation unit, and then delete the dedicated bearer between the devices corresponding to the indication;

A count update unit, configured to count the number of shared bearers;

Alternatively, the bearer control unit is configured to confirm that the number of shared bearers is equal to 1, and then delete the shared bearers.

In a fourth aspect, an embodiment of the present invention also provides a gateway device, including:

The type determining unit is configured to determine the service type corresponding to the service access after receiving the service access initiated by the first terminal device or the second terminal device;

The information sending unit is configured to send service quality information to the access device after confirming that the service type belongs to the shared service type, and the service quality information includes information for the first terminal device or the second terminal The equipment establishes shared bearer information.

In an optional implementation manner, the information sending unit is configured to send a bearer creation request or a bearer update request to the access device, and the bearer context is carried in the bearer creation request or the bearer update request. The bearer context includes a bearer shared quality of service information element, and the bearer shared quality of service information element includes information used to establish the shared bearer for the first terminal device.

In the fifth aspect, an embodiment of the present invention also provides a network system, including:

The access device and the gateway device; the access device is used to perform any of the method procedures described in the first aspect of the embodiments of the present invention; the gateway device is used to perform any of the second aspect of the embodiments of the present invention The method flow described in one item.

In the sixth aspect, the embodiments of the present invention also provide a network device. The network device may be any one of a mobile management device, a gateway device, a policy control function device, a session management device, and a user plane function device, including: processing The processor, the memory, and the transceiver; the processor, the memory, and the transceiver are connected in a communicative manner;

Program code is stored in the memory;

The processor is configured to read the program code and cooperate with the transceiver to implement the functions of the method implemented by the mobile management device in the embodiment of the present invention.

In a seventh aspect, an embodiment of the present invention also provides a computer-readable storage medium, in which program code is stored, and the program code includes program instructions that, when executed by a processor, cause the The processor cooperates with the transceiver to implement the function of any method in the embodiments of the present invention.

In an eighth aspect, the embodiments of the present invention also provide a computer program product. The above-mentioned computer program product includes program instructions. When the above-mentioned program instructions are executed by the above-mentioned processor, the processor cooperates with the transceiver to implement the The function of any method implemented by any one of the mobile management device, the gateway device, the policy control function device, the session management device, and the user plane function device.

In the technical solutions provided by all the above aspects, the specific means to include the bearer shared quality of service information element in the bearer context may include:

The bearer shared quality of service information element is carried in the extended information element of the general radio packet service tunnel control plane protocol GTP-C information element.

In the technical solutions provided by all the above aspects, the bearer sharing service quality information element carries: the identity of whether the bearer is shared, the identity of the service type, the maximum number of shared bearers allowed, the maximum allowed uplink rate, the maximum allowed downlink rate, Guaranteed maximum uplink rate and guaranteed maximum downlink rate.

Description of the drawings

In order to more clearly describe the technical solutions in the embodiments of the present invention or the background art, the following will describe the drawings that need to be used in the embodiments of the present invention or the background art.

Figure 1 is a system structure diagram of an embodiment of the present invention;

Figure 2 is a network architecture diagram of a network according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of the relationship between QoS according to an embodiment of the present invention;

4A is a schematic flowchart of a method according to an embodiment of the present invention;

4B is a schematic flowchart of a method according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of the structure of an optional cell according to an embodiment of the present invention;

FIG. 6 is a schematic flowchart of a method according to an embodiment of the present invention;

Figure 7 is a schematic diagram of the system structure of an embodiment of the present invention;

FIG. 8 is a schematic flowchart of a method according to an embodiment of the present invention;

FIG. 9 is a schematic structural diagram of an access device according to an embodiment of the present invention;

FIG. 10 is a schematic structural diagram of a gateway device according to an embodiment of the present invention;

FIG. 11 is a schematic diagram of the structure of a network device according to an embodiment of the present invention;

Figure 12 is a schematic structural diagram of an access device according to an embodiment of the present invention.

detailed description

The embodiments of the present invention will be described below in conjunction with the drawings in the embodiments of the present invention.

As shown in Figure 1, it is a schematic diagram of the system structure of the embodiment of the present invention. Figure 1 includes UE, base station, gateway device and server; the gateway device includes SGW and PGW, and the SGW and PGW can be deployed on the same device. Can be deployed separately. The server is an SP server that provides business services on the Internet side.

As shown in Figure 2, it is a schematic diagram of a unicast evolved packet system (evolved packet system, EPS) bearer between the UE and the PGW. The ESP bearer is a dedicated bearer.

The functions of each part of the EPS bearer are as follows:

In the UE, the uplink traffic flow template (UL TFT) aggregates and maps the traffic flow to the EPS bearer in the uplink direction;

In the PGW, the downlink traffic flow template (DL TFT) aggregates and maps the traffic flow to the EPS bearer in the downlink direction;

The radio bearer transmits EPS bearer packets between the UE and the eNodeB. If there is a radio bearer, there is a one-to-one mapping between the EPS bearer and the radio bearer;

S1 bearer transmits EPS bearer between eNodeB and SGW;

S5/S8 bearer transmits EPS bearer between SGW and PGW;

The UE stores the mapping between the filter of the uplink and the radio bearer to create a mapping between the UL service flow aggregation and the radio bearer in the uplink;

The PGW stores the mapping between the filter of the downlink and the S5/S8 bearer to create a mapping between DL service flow aggregation and the S5/S8 bearer in the downlink;

The eNodeB stores the one-to-one mapping between the radio bearer and the S1 bearer to create the mapping between the radio bearer and the S1 bearer in the uplink and downlink;

The SGW stores a one-to-one mapping between S1 bearers and S5/S8 bearers to create a mapping between S1 bearers and S5/S8 bearers in the uplink and downlink;

In addition, the evolved radio access bearer (E-RAB) is the bearer of the evolved universal terrestrial radio access network (E-UTRAN), which refers to the S1 bearer and the corresponding radio Concatenation of bearers; used to transmit data between the UE and the core network (CN). E-RAB is the name used by radio access bearer (RAB) in LTE, and the establishment process of the two can refer to each other.

The PGW routes the downlink packets to different EPS bearers based on the downlink filter in the TFT allocated to the EPS bearer in the PDN connection. When receiving the downlink data, the PGW searches for the downlink filter, and the downlink data is transmitted to the SGW on the EPS bearer associated with the TFT of the matching downlink filter. If no matching filter is found, the downlink data packet will be sent through the EPS bearer without any downlink filter assigned. If a downlink filter has been allocated for all EPS bearers, the PGW will discard the downlink data. In addition, since data is transmitted in the form of packets in the network, the downlink filter referred to in this embodiment is also called a packet filter, or simply a filter.

The dedicated bearer is divided into a guaranteed bit rate (GBR) bearer and a non-guaranteed bit rate (non-GBR) bearer, as shown in Figure 3.

The QoS parameters carried by GBR include GBR and maximum bit rate (MBR) parameters, where GBR is the rate that the dedicated bearer is expected to provide, and MBR is the upper limit of the rate that the bearer can provide. The QoS parameters of non-GBR bearers include the aggregate maximum bit rate (AMBR) parameter, which is the upper limit of the rate of a set of data streams; multiple evolved packet system (EPS) bearers can share one AMBR carried by non-GBR. Among them, the bit rate management performed based on the access point name (APN) is to limit the sum of the rates that can be used by all non-GBR bearers created by a UE under an APN. The bit rate management performed by the UE is to limit the sum of the rates that can be used by all non-GBR bearers of the UE, and the sum of the rates cannot be greater than the aforementioned AMBR.

In addition, Figure 3 also shows that the service access entity (SAE) bears QoS, including QoS class identifier (QCI) and allocation and retention priority (ARP), where QCI Including dedicated bearer, packet loss rate (loss) and delay (delay).

As shown in FIG. 4A, it is a schematic diagram of the method flow of the embodiment of the present invention. In this example, two UEs are included. The SGW and the PGW are deployed in the gateway device, and the access device is the base station, which specifically includes:

401: The gateway device obtains the service type of UE1, determines whether the service type belongs to the service type using the shared bearer, and if so, obtains the QoS information corresponding to the service type.

The way for the gateway device to obtain the service type of UE1 may be that after UE1 initiates access to the service server, the base station obtains it through service awareness (SA) technology.

In this step, the wireless network service provider can pre-set which service types belong to the service types that use shared bearers; the gateway device specifically refers to the PGW; the above QoS information is the same as the UE2 using the same service type, so it is also called To share QoS information.

In addition, if the service type does not belong to the service type using the shared bearer, the procedure for establishing a radio bearer specified in 3GPP or other procedures for establishing a radio bearer can be used, which is not limited in this embodiment.

402: The gateway device sends the aforementioned QoS information to the base station, and specifies in the aforementioned QoS information that the QoS information is used to establish a shared bearer, the service type corresponding to the shared bearer, and other parameters required for establishing a radio bearer.

More specifically, the extended GTP-C cell contains optional cells for carrying Shared QoS, as shown in Table 1:

Table 1

信元Letter yuan	属性Attributes	简要说明brief introduction
shared QoSshared QoS	OO	扩展的共享QoS信元，用于提供QoS共享信息.The extended shared QoS cell is used to provide QoS shared information.

The optional cell structure of the GTP-C cell is shown in Figure 5. The specific translation of each field in Figure 5 is as follows:

Bit: bits;

Type = xx (decimal): type = xx (decimal);

Length=N: length=n;

Standby: apare; instance: instance;

Whether to share the flag: SF (shared flag);

Shared serviceID: shared serviceID;

The maximum value of shared bears: maximum of shared bears;

The maximum bit rate of the uplink: totally maximum bit rate for uplink;

The maximum bit rate of the downlink: totally maximum bit rate for downlink;

Guaranteed uplink bit rate: totally guaranteed bit rate for uplink;

Guaranteed uplink bit rate: totally guaranteed bit rate for downlink;

These octets only exist when they exist: these octet(s) is/are present only if.

A more specific description is shown in Table 2 below:

Table 2

403: After receiving the above QoS information, the base station determines to establish a dedicated bearer for UE1. The dedicated bearer is a shared bearer and obtains the service type; determines that the shared bearer has not been established, and sends relevant information to UE1 to establish the shared bearer.

In this step, the base station allocates air interface resources to UE1 according to the QoS information. For UE1, the base station establishes a dedicated bearer for it. The UE can also return relevant information to the network according to the 3GPP protocol, which will not be repeated in this embodiment. So far, the establishment of the radio bearer of UE1 is completed. In addition, the count of the number of dedicated bearers sharing the shared bearer is 1, that is, the number of shared bearers is 1.

404 and 405 refer to the preceding 401 and 402, and will not be repeated here.

406: After receiving the above QoS information sent by the gateway device, the base station determines to establish a dedicated bearer for UE1. The dedicated bearer is a shared bearer, obtains the service type identifier in it, and determines that the shared bearer has been established, and then determines whether the number of shared bearers is The maximum number of shared bearers has been reached, that is, whether the number of shared bearers has reached the value specified by Maximum of shared bears. If not, you can send relevant information to UE2 to establish a dedicated bearer for UE2, otherwise refuse to establish a dedicated bearer for UE2. If a dedicated bearer is established for the UE2, the dedicated bearer uses the resources of the already established shared bearer, and the number of shared bearers is increased by one.

After the shared bearer is established, the data sent by UE1 and UE2 to the base station is sent using the dedicated bearer for UE1 and UE2; before the base station sends data to UE1 or UE2, the service type is first judged as the shared service type, and the corresponding shared bearer is found. Then use the shared bearer to send data to UE1 or UE2.

The shared bearer deletion process can be performed after UE1 establishes the shared bearer above. If only the dedicated bearer of UE1 in the shared bearer uses the shared bearer, UE1 is the last shared bearer deletion in the shared bearer; the subsequent embodiments are based on The UE2 is taken as an example for deleting the last shared type bearer, as shown in FIG. 4B.

407: The gateway device sends an instruction to delete the shared bearer to the base station.

The indication of deleting the shared bearer will carry the identifier of the aforementioned shared bearer and the information of deleting the bearer of UE1.

408: After the base station obtains the identity of the shared bearer from the above indication of deleting the shared bearer, the number of shared bearers using the shared bearer is reduced by 1, and it is confirmed whether the number of shared bearers is 0. If not, it means that there are other dedicated bearers using the shared bearer. Shared bearer; at this time, the bit rate resources and QoS control resources of the shared bearer do not need to be released.

In the example of this embodiment, since UE1 is not the last shared type bearer, the number of shared bearers will be greater than zero at this time.

The base station may send a bearer deletion instruction to UE1, and then UE1 returns related information about the bearer deletion to the network side.

409: The gateway device sends an instruction to delete the shared bearer to the base station.

The indication of deleting the shared bearer will carry the identifier of the aforementioned shared bearer and the information of deleting the bearer of UE2.

410: After the base station obtains the identity of the shared bearer from the above indication of deleting the shared bearer, the number of shared bearers using the shared bearer is reduced by 1, and it is confirmed whether the number of shared bearers is 0. If so, it means that no other dedicated bearers use the shared bearer. Bearer; at this time, the bit rate resources and QoS control resources of the shared bearer can be released.

Then the base station can send a bearer deletion instruction to UE2, and UE2 returns related information about the bearer deletion to the network side.

After the above 409 and 410, sending the delete bearer indication to UE1 or UE2 and UE1 or UE2 returning to the network side the related information of deleting the bearer can follow the 3GPP related agreement on the deletion of the dedicated bearer of the UE, which is not limited in the embodiment of the present invention , I won’t repeat it here.

In the following embodiments, the establishment and deletion of an evolved radio access bearer (E-RAB) in long term evolution (LTE) is taken as an example for description.

As shown in Figure 6, the process of establishing a shared bearer includes:

601: UE1 initiates service access to the SP server.

Specifically: the UE initiates a service message, and performs IP data message transmission with the SP server. IP data packets will pass through network equipment including eNodeB, SGW, and PGW.

602: PGW performs SA identification and maps out service type and QoS information.

Specifically: PGW recognizes the type of service accessed by UE1 through the service awareness function, and decides whether to create a corresponding shared bearer according to the corresponding service type. For a certain service type, whether to create a shared bearer, and the parameters of the corresponding shared bearer, either the policy and charging rules function (PCRF) issued to the PGW, or the local configuration configured on the PGW The embodiment does not limit this.

If the current service type does not need to create a shared bearer, there is no subsequent process in this embodiment, and will not be repeated here.

If the current service type belongs to the service type for which a shared bearer needs to be created, the QoS information of the corresponding shared bearer is mapped out, and the shared ID of the shared bearer is mapped.

603: The PGW sends a bearer creation request message (create bearer request) to the mobile management entity (mobile management entity, MME) through the SGW. The bearer creation request message includes the international mobile subscriber identity (IMSI) and payload type In addition to information such as the payload type identifier (PTI) and the linked evolved packet system bearer identity (LBI), it also includes the QoS information of the shared bearer. The PGW sends an E-RAB setting request to the eNodeB through the MME.

For the QoS information carried in the above bearer creation request message, reference may be made to the description of the GTP extended cell in the preceding text, which will not be repeated here.

604: The MME allocates an EPS bearer identifier and sends a bearer setup request to the base station. The bearer setup request carries the EPS bearer identifier, shared QoS information, session management request (session management request), S1-TEID, etc. The above S1 is the port number, and TEDI is the tunnel endpoint identifier. The above-mentioned S1-TEID is used to identify the S1 bearer, and the above-mentioned EPS bearer identifier is used to identify the EPS bearer.

605: The base station extracts the shared QoS information in the above bearer establishment request, judges whether there is a shared QoS control resource according to the shared ID, if not, allocates the bit rate resource, maps the shared bearer QoS to wireless QoS, and records the shared bearer The number of shared bearers = 1.

606: The base station sends an RRC connection reconfiguration (RRC connection reconfiguration) request to UE1.

The RRC connection reconfiguration request carries the radio bearer QoS, session management request, and EPS radio bearer identity (radio bearer identity)

607: UE1 sends an RRC connection re-configuration complete (RRC connection re-configuration complete) message to the base station to confirm the activation of the radio bearer.

608: The base station sends a bearer setup response (bearer setup response) message to the MME to confirm the activation of the radio bearer. The above-mentioned EPS bearer identifier and the above-mentioned S1-TEID are included in the bearer establishment response message.

609: UE1 establishes a session management response message containing the above-mentioned ESP bearer identifier, and sends the session management response message to the base station.

610: After receiving the above session management response message, the base station sends an uplink non-access stratum (NAS) transmission message to the MME. The uplink NAS transmission message can be used as a session management response message.

611: After receiving the bearer establishment response message in 608 and the session management response message in 609, the MME sends a bearer creation response to the PGW to confirm that the bearer is activated to the SGW. The bearer creation response carries the above-mentioned EPS bearer identifier and the above-mentioned S1-TEID.

The above 601-611 is the first creation of a shared bearer (UE1)

612-615 refer to the previous 601-604 and will not be repeated here.

616: The base station obtains the shared QoS information, judges that the shared QoS control resource already exists according to the shared ID, no longer allocates the bit rate resource and the shared QoS control resource, the number of shared bearers is +1, and the previously established shared QoS control can be reused Resources.

617-622 refer to 605-611 in the previous article and will not repeat it here.

The above 612-622 are non-first-time creation of shared bearers (UE2).

After multiple UEs use the shared bearer with the aforementioned shared ID, and multiple UEs access the service of the service type corresponding to the shared bearer, the base station will use the bit rate of the shared bearer for all dedicated bearers of these service types to uniformly perform QoS control.

In the embodiment of the present invention, the same type of services of different users can be aggregated at the base station to perform QoS control, and therefore, the air interface resources can be managed and controlled reasonably and effectively. More specifically: For the same type of service, such as video service, the creation of a shared GBR dedicated bearer can be triggered. By reserving a certain amount of air interface resources, in the case of overload, it can still guarantee the basic viewing of certain users, and at the same time pass MBR controls the overall resource occupation of the air interface bit rate. For services with high instantaneous bit rate requirements (such as grabbing red envelopes), a shared GBR dedicated bearer can be created to meet service requirements, while avoiding the problem of multiple users simultaneously using and occupying too much air interface resources.

As shown in FIG. 7, it is a schematic diagram of UE1, UE2, and UE3 accessing the same service type, and the service type is a shared service type. The service data accessed by UE1-UE3 are respectively identified by the numbers 1-3 in the square. The SP server sends the service data respectively sent to UE1-UE3 to the PGW, which forwards the PGW to the base station, and the base station uses the shared bearer to send it to UE1-UE3 For UE1-UE3, it does not know the existence of shared bearers. For UE1-UE3, dedicated bearers are used for service access.

Referring to Figure 6, in the network architecture shown in Figure 7, the PGW in the PGW is used to sense service types and trigger the establishment of a shared bearer, so that the same service types of different users can be associated with the same shared bearer; the base station pairs according to the PGW. The shared bearer setting is to establish dedicated bearers for multiple UEs. The dedicated bearers share the resources of the shared bearer, including bit rate resources and QoS control resources; these shared bearer resources form a shared resource group for these dedicated bearers; multiple users also The air interface resources of the shared bearer are shared.

As shown in Figure 8, the deletion process of the shared bearer includes:

①. Delete the bearer of the non-last shared bearer type (UE1):

801: The PGW detects that the UE1 no longer accesses the corresponding service, and the PGW sends a delete bearer request message to the MME through the SGW.

The above-mentioned delete bearer request message may carry information such as PTI, EPS bearer identifier, and delete reason.

802: MME sends a Deactivate Bearer Request to the base station

The EPS bearer identifier is carried in the deactivation bearer request. More specifically, the MME constructs a NAS deactivate EPS bearer context request message (NASdeactivate EPS bearer contextrequest), the NAS deactivate EPS bearer context request message includes the EPS bearer identifier, and carries the NAS deactivate EPS bearer context request message in the deactivate EPS bearer context request message. Activate the bearer request message.

803: The base station checks the bearer to be deleted according to the EPS bearer identifier, and finds that the bearer is a shared QoS bearer, then the number of shared bearers of the QoS bearer is reduced by one. After updating the number of shared bearers, the result is not 0, indicating that there are still bearers using the shared QoS resources of the shared bearers corresponding to the bearer, so the bit rate and shared QoS resources are not released.

804: The base station sends an RRC connection reconfiguration (RRC connection reconfiguration) message to UE1.

The RRC connection reconfiguration message includes the EPS bearer identification release and the NAS deactivation EPS bearer context request message.

805: UE1 replies to the base station with an RRC connection reconfiguration complete (RRC connection reconfiguration complete) message.

806: The base station sends a Deactivate Bearer Response (Deactivate Bearer Response) message to the MME to confirm the deactivation of the bearer. The EPS bearer identifier is carried in the deactivation bearer response message.

807: UE1 constructs a deactivate EPS bearer context accept message. The deactivate EPS bearer context accept message includes the EPS bearer identifier, and the UE sends a direct transfer message to the base station. The direct transmission message carries the above-mentioned deactivated EPS bearer context acceptance message.

808: The base station sends the above-mentioned deactivated EPS bearer context accept message to the MME.

809: The MME deletes the bearer context related to the deactivated EPS bearer, and sends a Delete Bearer Response (Delete Bearer Response) message to the PGW through the SGW to confirm the deactivation of the bearer.

②. Delete the last shared bearer type (UE2)

Steps 810-811 can refer to 801-802, which will not be repeated here.

812. The base station checks the bearer to be deleted according to the EPS bearer identifier, and finds that the bearer is a shared QoS bearer, then the number of shared bearers of the QoS bearer is reduced by one. After updating the number of shared bearers, the result is 0, indicating that no bearer is using the shared QoS resource of the shared bearer corresponding to the bearer, and the shared QoS resource and its corresponding bit rate resource can be released.

Steps 813-818 can refer to 804-809, which will not be repeated here.

An embodiment of the present invention also provides an access device, as shown in FIG. 9, including: a data receiving unit 901, configured to receive data sent to a first terminal device, and obtain a service type of the data;

The bearer obtaining unit 902 is configured to obtain a shared bearer corresponding to the service type, where the shared bearer is a bearer established for the second terminal device and used to transmit data of the service type;

The sending unit 903 is configured to send the data using the shared bearer.

In an optional implementation manner, the bearer obtaining unit 902 is configured to search for the shared bearer after confirming that the service type belongs to the shared type.

For the specific description of this embodiment, please refer to the method embodiment provided above, especially the specific content of Figure 4A, Figure 4B and Figure 6. You can also refer to Figure 6 to Figure 8 and related text descriptions together, which will not be repeated here. .

In an optional implementation manner, the access device further includes:

The information receiving unit 904 is configured to receive the service quality information sent by the gateway device before the bearer obtaining unit 902 obtains the shared bearer corresponding to the service type, and the service quality information includes information for serving the second terminal The equipment establishes the information of the shared bearer;

The first bearer establishment unit 905 is configured to establish the shared bearer according to the service quality information.

In an optional implementation manner, the information receiving unit 904 is configured to receive a bearer creation request or a bearer update request sent by the gateway device, and the bearer context is carried in the bearer creation request or the bearer update request, and the bearer The context includes a bearer shared quality of service information element, and the bearer shared quality of service information element includes information used to establish the shared bearer for the second terminal device.

In an optional implementation manner, the access device further includes:

The counting unit 906 is configured to, before the data receiving unit 901 receives the data sent by the first terminal device, after receiving the information used to establish the shared bearer for the first terminal device, confirm that the shared bearer is not exceeded. After the maximum number of shared bearers allowed by the bearer is carried, count the number of shared bearers that have been used by the shared bearer;

The second bearer establishment unit 907 is configured to use the air interface resources of the shared bearer to establish a dedicated bearer of the first terminal device after confirming that the maximum number of shared bearers allowed by the shared bearer is not exceeded;

Alternatively, the second bearer establishing unit 907 is configured to confirm that the maximum number of bearers allowed by the shared bearer is exceeded, and then refuse to establish a dedicated bearer for the first terminal device.

In an optional implementation manner, the access device further includes:

The counting confirmation unit 908 is configured to confirm that the number of shared bearers of the shared bearer is greater than 1 after receiving an instruction to delete the dedicated bearer sent by the gateway device after the shared bearer is established;

The bearer control unit 909 is configured to confirm that the number of shared bearers of the shared bearer is greater than one in the count confirmation unit 908, and then delete the dedicated bearer between the devices corresponding to the indication;

A count update unit 910, configured to count the number of shared bearers;

Alternatively, the bearer control unit 909 is configured to confirm that the number of shared bearers is equal to 1, and then delete the shared bearers.

In this embodiment, the functions of the data receiving unit 901, the sending unit 903, and the information receiving unit 904 can be performed by the antenna of the base station and its related control module, corresponding to the function of the transceiver of the network device in the subsequent embodiments. Other units may be implemented by hardware with data processing functions in the base station, and may correspond to the functions of the processor of the network device in the subsequent embodiments.

The embodiment of the present invention also provides a gateway device, as shown in FIG. 10, including:

The type determining unit 1001 is configured to determine the service type corresponding to the service access after receiving the service access initiated by the first terminal device or the second terminal device;

The information sending unit 1002 is configured to send service quality information to the access device after confirming that the service type belongs to the shared service type, and the service quality information includes information used to provide information for the first terminal device or the second terminal device or the second terminal device. The terminal equipment establishes the shared bearer information.

In an optional implementation manner, the information sending unit 1002 is configured to send a bearer creation request or a bearer update request to the access device, and the bearer context is carried in the bearer creation request or the bearer update request, and the bearer context is carried in the bearer creation request or the bearer update request. The bearer context includes a bearer shared quality of service information element, and the bearer shared quality of service information element includes information used to establish the shared bearer for the first terminal device.

The embodiment of the present invention also provides a network device, which may be any one of a mobile management device, a gateway device, a policy control function device, a session management device, and a user plane function device.

As shown in FIG. 11, the network device includes: a processor 1101, a memory 1102, and a transceiver 1103; the processor 1101, the memory 1102, and the transceiver 1103 are connected in a communicative manner;

Program codes are stored in the memory 1102;

More specifically, the processor 1101 can correspond to the functions of units other than the data receiving unit 901, the sending unit 903, and the information receiving unit 904 in the structure shown in FIGS. 9 and 10. The specific execution process is not detailed in this embodiment. Narrated. The transceiver 1103 may correspond to the functions of the data receiving unit 901, the sending unit 903, the information receiving unit 904, and the information sending unit 1002 in the structures shown in FIGS. 9 and 10. The specific execution process is not described in detail in this embodiment.

The network device is a gateway device, and the transceiver 1103 is configured to send service quality information to the access device after confirming that the service type belongs to the shared service type. The service quality information includes information for the first terminal device Or the second terminal device establishes shared bearer information; the processor 1101 is configured to determine the service type corresponding to the service access after receiving the service access initiated by the first terminal device or the second terminal device.

The memory 1102 includes but is not limited to random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or Portable read-only memory (compact disc read-only memory, CD-ROM), the memory 1102 is used for related instructions and data. The transceiver 1103 is used to receive and send data and messages.

The processor 1101 may be one or more central processing units (CPUs). When the processor 1101 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

FIG. 12 shows a schematic diagram of a possible structure of the access device involved in the above embodiment, especially the base station. The base station may be the base station in Figure 1, Figure 4A, Figure 4B, Figure 6, Figure 7, and the base station in Figure 8, and the eNodeB in Figure 2.

The base station shown includes a transceiver 1201 and a controller/processor 1202. The transceiver 1201 may be used to support the sending and receiving of information between the base station and the UE in the foregoing embodiment, and to support radio communication between the UE and other UEs. The controller/processor 1202 may be used to perform various functions for communicating with UEs or other network devices. In the uplink, the uplink signal from the UE is received via an antenna, mediated by the transceiver 1201, and further processed by the controller/processor 1202 to restore the service data and signaling information sent by the UE. On the downlink, service data and signaling messages are processed by the controller/processor 1202, and mediated by the transceiver 1201 to generate a downlink signal, which is transmitted to the UE via an antenna. The controller/processor 1202 is also used to execute the wireless network resource management method as described in the above embodiments, establish a shared bearer for the UE, use the shared bearer to transmit data for the UE, and manage the dedicated bearer sharing the shared bearer, including Delete and add dedicated bearers in the shared bearer, and delete the shared bearer itself. The controller/processor 1202 specifically executes the steps of 403 and 406 in FIG. 4A, 408 and 410 in FIG. 4B, 605 and 616 in FIG. 6, and 803 and 812 in FIG. The base station may also include a memory 1203, which may be used to store program codes and data of the base station. The base station may also include a communication unit 1204 for supporting the base station to communicate with other network entities. For example, it is used to support communication between the base station and other communication network entities shown in FIG. 4A, FIG. 4B, FIG. 6 or FIG. 8, such as UE, MME, and gateway equipment.

It can be understood that FIG. 7 only shows a simplified design of the base station. In practical applications, the base station may include any number of transmitters, receivers, processors, controllers, memories, communication units, etc., and all base stations that can implement the present invention fall within the protection scope of the present invention.

The embodiment of the present invention also provides a computer-readable storage medium, the storage medium stores program code, the program code includes program instructions, and when executed by a processor, the program instructions cause the processor to communicate with the transceiver The device cooperates to realize the function of any method in the embodiment of the present invention. For details, please refer to the method flow in the preceding text, which will not be described in detail here.

The embodiment of the present invention also provides a computer program product. The above-mentioned computer program product includes program instructions. When the above-mentioned program instructions are executed by the above-mentioned processor, the processor and the transceiver cooperate to implement any item provided in the embodiments of the present invention. For the function of the method, please refer to the method flow in the previous article for details, which will not be detailed here.

A person of ordinary skill in the art can understand that all or part of the process in the above-mentioned embodiment method can be realized. The process can be completed by a computer program instructing relevant hardware. The program can be stored in a computer readable storage medium. , May include the processes of the foregoing method embodiments. The aforementioned storage media include: ROM or random storage RAM, magnetic disks or optical disks and other media that can store program codes.

Claims

A method for managing wireless network resources, which is characterized in that it includes:

The access device receives the data sent to the first terminal device, and obtains the service type of the data;

Obtaining, by the access device, a shared bearer corresponding to the service type, where the shared bearer is a bearer established for a second terminal device and used to transmit data of the service type;

The access device uses the shared bearer to send the data.
The method according to claim 1, characterized in that, before said obtaining the shared bearer corresponding to the service type, the method further comprises:

Receiving, by the access device, service quality information sent by a gateway device, the service quality information includes information used to establish the shared bearer for the second terminal device;

Establishing the shared bearer according to the service quality information.
The method according to claim 2, wherein the access device receives the service quality information sent by the gateway device, and the service quality information includes information for establishing the shared bearer for the second terminal device include:

The access device receives the bearer creation request or the bearer update request sent by the gateway device, the bearer context is carried in the bearer creation request or the bearer update request, and the bearer shared quality of service information element is included in the bearer context, and The bearer shared service quality information element includes information used to establish the shared bearer for the second terminal device.
The method according to claim 3, wherein the including a bearer shared quality of service information element in the bearer context comprises:

The bearer shared quality of service information element is carried in the extended information element of the general radio packet service tunnel control plane protocol GTP-C information element.
The method according to claim 4, wherein the bearer sharing quality of service information element carries: an identifier of whether the bearer is shared, an identifier of the service type, a maximum number of shared bearers allowed, a maximum allowed uplink rate, The maximum allowed downlink rate, the guaranteed maximum uplink rate, and the guaranteed maximum downlink rate.
The method according to any one of claims 1-5, wherein before the access device receives the data sent by the first terminal device, the method further comprises:

After receiving the information for establishing the shared bearer for the first terminal device, and after confirming that the maximum number of shared bearers allowed by the shared bearer is not exceeded, count the number of shared bearers that have been used by the shared bearer, and use Establishing the dedicated bearer of the first terminal device by the air interface resources of the shared bearer;

Or, if it is confirmed that the maximum number of bearers allowed by the shared bearer is exceeded, the establishment of a dedicated bearer for the first terminal device is refused.
The method according to any one of claims 1-5, wherein after the shared bearer is established, the method further comprises:

After receiving the instruction to delete the dedicated bearer sent by the gateway device, it is confirmed that the number of shared bearers of the shared bearer is greater than 1, then the dedicated bearer between the devices corresponding to the instruction is deleted, and the number of shared bearers is counted ；

Or, if it is confirmed that the number of shared bearers is equal to 1, the shared bearers are deleted.
A method for managing wireless network resources, which is characterized in that it includes:

After receiving the service access initiated by the first terminal device or the second terminal device, the gateway device determines the service type corresponding to the service access;

The gateway device confirms that the service type belongs to the shared service type, and sends service quality information to the access device, where the service quality information includes a method for establishing a shared bearer for the first terminal device or the second terminal device Information.
8. The method according to claim 8, wherein the sending quality of service information to the access device includes a method for establishing a shared bearer for the first terminal device or the second terminal device. The information includes:

Send a bearer creation request or a bearer update request to the access device, the bearer context is carried in the bearer creation request or the bearer update request, and the bearer shared service quality information element is included in the bearer context. The quality information element includes information used to establish the shared bearer for the first terminal device.
The method according to claim 9, wherein the including the bearer shared quality of service information element in the bearer context comprises:

The bearer shared quality of service information element is carried in the extended information element of the general radio packet service tunnel control plane protocol GTP-C information element.
The method according to claim 10, wherein the bearer sharing quality of service information element carries: an identifier of whether the bearer is shared, an identifier of the service type, a maximum number of shared bearers allowed, a maximum allowed uplink rate, The maximum allowed downlink rate, the guaranteed maximum uplink rate, and the guaranteed maximum downlink rate.
A network device, comprising: a processor, a memory, and a transceiver; the processor, the memory, and the transceiver are connected in a communicative manner; and it is characterized in that:

Program code is stored in the memory;

The processor is configured to read the program code and cooperate with the transceiver to implement the function of the method of any one of claims 1 to 11.
A computer-readable storage medium, characterized in that:

A program code is stored in the storage medium, and the program code includes program instructions that, when executed by a processor, cause the processor to cooperate with the transceiver to implement the function of any one of the methods of claims 1 to 11.