CN110740425B - Method and system for distinguishing cluster service bearer by core network - Google Patents
Method and system for distinguishing cluster service bearer by core network Download PDFInfo
- Publication number
- CN110740425B CN110740425B CN201810803717.8A CN201810803717A CN110740425B CN 110740425 B CN110740425 B CN 110740425B CN 201810803717 A CN201810803717 A CN 201810803717A CN 110740425 B CN110740425 B CN 110740425B
- Authority
- CN
- China
- Prior art keywords
- service
- core network
- bearing
- cluster
- service type
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
- H04W4/10—Push-to-Talk [PTT] or Push-On-Call services
Abstract
The invention relates to a method and a system for distinguishing cluster service load by a core network, which comprises the following steps: a first core network receives a call service request sent by a terminal and sends a message for applying for bearing resources to a second core network; the message carrying the resource carries identification information for identifying the service type requested by the terminal; the second core network judges the service type of the terminal call according to the message of applying for bearing resources; if the service type of the terminal call is a first service type, the second core network starts a first service type bearing resource allocation process according to a first preset strategy; and if the service type of the terminal call is a second service type, the second core network starts a second service type bearing resource allocation process according to a second preset strategy. The implementation of the invention solves the problem that the core network can not distinguish cluster bearing from non-cluster bearing, realizes the priority scheduling of the cluster service, avoids the occupation of non-cluster service resources and improves the effect and quality of the terminal cluster service under roaming.
Description
Technical Field
The present invention relates to the field of broadband trunking, and more particularly, to a method and system for a core network to distinguish trunking service bearers.
Background
In a roaming scenario, a trunking terminal roams from a home location to a visited location, and when the trunking terminal is doing trunking services (point-to-point single call service and group call calling service) or non-trunking services (PS), a V-SGW (roaming location-serving gateway) of the visited location needs to send a message to inform a home location H-PGW (home location-PDN gateway) to allocate bearer resources for the services.
The bearers can be classified into cluster bearers and non-cluster bearers according to the transmitted traffic. Initiating the establishment or modification of the network side bearer by the H-PGW, if the QoS (Quality of Service) of the existing bearer meets the QoS application, the H-PGW can reuse the bearer to initiate the bearer modification process, and superimpose a bearer TFT (Traffic Flow Template) on the existing bearer; and if the QoS of the existing bearer can not meet the QoS application, the H-PGW initiates a bearer establishment flow. The QoS parameters of the bearer include QCI (QoS Class Identifier)/GBR (Guaranteed Bit Rate)/MBR (Maximum Bit Rate).
Since trunking traffic is usually prioritized over PS traffic and trunking bearers are distinguished from PS bearers, but currently PGW (PDN Gateway) does not distinguish trunking bearers from non-trunking bearers (PS), either existing PS bearers may be used to carry trunking traffic or existing trunking bearers may be used to carry non-trunking traffic, and a mismatch between traffic and bearers may result in poor trunking traffic quality.
Therefore, since the existing core network PGW cannot distinguish between a trunking bearer and a non-trunking bearer (PS), trunking services may not be scheduled and resource occupied preferentially. If the non-cluster service resource application is carried out: if the QoS of the existing cluster bearer can meet the QoS application, the PGW is caused to use the existing cluster bearer to bear the PS service, and the resources are occupied; or, when the cluster service resource application is carried out: if the QoS of the existing PS bearer can meet the QoS application, the PGW is caused to use the existing PS bearer to bear the trunking service, and the trunking service cannot be scheduled preferentially, so that the service quality is influenced.
Disclosure of Invention
The technical problem to be solved by the present invention is to provide a method and a system for a core network to distinguish a cluster service bearer, aiming at the above-mentioned defects in the prior art.
The technical scheme adopted by the invention for solving the technical problems is as follows: a method for constructing a core network differentiated cluster service bearer comprises the following steps:
a first core network receives a call service request sent by a terminal and sends a message for applying for bearing resources to a second core network; the message of the bearing resource carries identification information for identifying the service type requested by the terminal;
the second core network judges the service type of the terminal call according to the message of applying for bearing resources;
if the service type of the terminal call is a first service type, the second core network starts a first service type bearing resource allocation process according to a first preset strategy;
and if the service type of the terminal call is a second service type, the second core network starts a second service type bearing resource allocation process according to a second preset strategy.
Preferably, the identification information is identified by setting a flag bit in an idle field of the message applying for bearing resources;
the second core network determining the service type of the terminal call according to the message applying for bearing resources includes:
the second core network judges whether the flag bit meets a first preset condition according to the message of applying for bearing the resource, if so, the service type of the terminal call is a first service type; and if not, the service type of the terminal call is a second service type.
Preferably, the identification information is identified by a value of a service quality level identifier in the message requesting for bearer resources;
the second core network determining the service type of the terminal call according to the message applying for bearing resources includes:
the second core network judges whether the value of the service quality grade identification meets a second preset condition according to the message of applying for bearing resources, if so, the service type of the terminal call is a second service type; if not, the service type of the terminal call is the first service type.
Preferably, the first service type is a trunking service type, and the second service type is a non-trunking service type.
Preferably, the first core network is a broadband trunking core network of a roaming place where the terminal is located, and the second core network is a broadband trunking core network of a home place where the terminal is located.
Preferably, the first core network includes a cluster control function module, an enhanced mobility management unit, and a service gateway;
the first core network receiving a call service request sent by a terminal and sending a message for applying for bearing resources to a second core network comprises:
the enhanced mobile management unit receives a call service request sent by the terminal and sends a call service message to the cluster control function module;
the cluster control function module establishes a call service according to the call service message;
the enhanced mobile management unit determines the service type of the terminal according to the call service request, and sets the identification information and determines the bearing resource required to be applied according to the service type;
the enhanced mobile management unit sets the identification information and then sends the message of applying for bearing resources to the service gateway;
and the service gateway receives the message for applying for bearing the resources and sends the message for applying for bearing the resources to the second core network.
Preferably, the first and second electrodes are formed of a metal,
if the identification information is the identification information identified by setting a flag bit in an idle field of the message applying for bearing the resources;
the second core network determining the service type of the terminal call according to the message applying for bearing resources includes:
the second core network judges whether the flag bit meets a first preset condition according to the message of applying for bearing the resource, if so, the service type of the terminal call is a first service type;
if the identification information is the identification information identified by the service quality grade identification in the bearing resource message;
the second core network determining the service type of the terminal call according to the message applying for bearing resources includes:
and the second core network judges whether the value of the service quality grade identification meets a second preset condition according to the message of applying for bearing resources, if so, the service type of the terminal call is a second service type.
Preferably, the starting the first service type bearer resource allocation procedure according to the first preset policy includes:
if the existing cluster bearing meets the service quality requirement of the applied bearing resource, triggering and modifying the cluster bearing process;
if the existing cluster bearing does not meet the service quality requirement of the applied bearing resource, triggering a newly-built cluster bearing process;
and directly triggering the newly-built cluster bearing process no matter whether the existing cluster bearing meets the service quality requirement of the applied bearing resource or not.
Preferably, the starting the second service type bearer resource allocation procedure according to the second preset policy includes:
if the existing non-cluster bearing meets the service quality requirement of the applied bearing resource, triggering and modifying the non-cluster bearing process;
and if the existing non-cluster bearing does not meet the service quality requirement of the applied bearing resource, triggering a new non-cluster bearing process.
Preferably, the method further comprises:
and judging whether the existing cluster bearing or non-cluster bearing meets the service quality requirement of the applied bearing resource or not according to the value of the service quality grade identification carried in the message for applying for bearing the resource.
The invention also provides a system for distinguishing the cluster service bearer by the core network, which comprises a terminal, a first core network and a second core network;
the terminal is used for sending a call service request to the first core network;
the first core network is used for receiving a call service request sent by a terminal and sending a message for applying for bearing resources to a second core network; the message of the bearing resource carries identification information for identifying the service type requested by the terminal;
the second core network judges the service type of the terminal call according to the message of applying for bearing resources;
if the service type of the terminal call is a first service type, the second core network starts a first service type bearing resource allocation process according to a first preset strategy;
and if the service type of the terminal call is a second service type, the second core network starts a second service type bearing resource allocation process according to a second preset strategy.
The method and the system for distinguishing the cluster service bearer by the core network have the following beneficial effects that: the implementation of the invention solves the problem that the core network can not distinguish cluster bearing from non-cluster bearing, realizes the priority scheduling of the cluster service, avoids the occupation of non-cluster service resources and improves the effect and quality of the terminal cluster service under roaming.
Drawings
The invention will be further described with reference to the accompanying drawings and examples, in which:
fig. 1 is a flowchart of a method for differentiating a cluster service bearer by a core network according to the present invention;
FIG. 2 is a diagram of a first embodiment of the present invention for identifying a service type by setting a flag bit in an idle field;
FIG. 3 is a diagram of a second embodiment of the present invention for identifying a service type by using a value of a quality of service class identifier;
FIG. 4 is a schematic diagram of a cluster service process of a method for differentiating cluster service bearers by a core network according to the present invention;
FIG. 5 is a schematic diagram of a non-trunking service processing method for differentiating trunking service bearers by a core network according to the present invention;
fig. 6 is a flow chart of new single call service end-to-end of a method for differentiating cluster service bearer by a core network according to the present invention.
Detailed Description
For a more clear understanding of the technical features, objects and effects of the present invention, embodiments of the present invention will now be described in detail with reference to the accompanying drawings.
As shown in fig. 1, the present invention provides a method for a core network to distinguish a trunking service bearer, where the method is applicable to a roaming scenario, where a trunking terminal roams from a home location to a visited location, and a trunking service or a non-trunking service is initiated by the trunking terminal.
Specifically, the method for distinguishing the cluster service bearer by the core network includes the following steps:
step S11, the first core network receives the call service request sent by the terminal and sends the message of applying for bearing resources to the second core network; the message carrying the resource carries identification information for identifying the service type requested by the terminal.
In the embodiment of the present invention, the first service type is a trunking service type, wherein the trunking service type may be a point-to-point single call service or a group call calling service.
The second service type is a non-trunking service type, i.e. a PS service.
Specifically, when the terminal roams to a visited place and needs to perform a trunking service or a non-trunking service, the terminal needs to send a call service request to the first core network, and the first core network obtains a service type initiated by the terminal according to the call service request sent by the terminal.
Optionally, the first core network includes a cluster control function module (V-TCF), an enhanced mobile management unit (V-eMME), and a serving gateway (V-SGW).
Step S11 includes:
step S111, the enhanced mobile management unit receives the call service request sent by the terminal and sends a call service message to the cluster control function module.
And step S112, the cluster control function module establishes a call service according to the call service message.
Specifically, after receiving the call service message sent by the enhanced mobile management unit, the trunking control function module establishes a corresponding call service flow according to a call initiated by the terminal, thereby implementing control over operations executed by the enhanced mobile management unit and the service gateway.
Step S113, the enhanced mobile management unit determines the service type of the terminal according to the call service request, and sets the identification information and determines the bearer resource required to be applied according to the service type.
After the enhanced mobile management unit determines the service type of the call of the terminal according to the call service request sent by the terminal, namely, identification information for identifying the service type of the terminal call is set between the S5/S8 interfaces of the service gateway of the first core network and the PDN gateway of the second core network. The bearer resource required to be applied includes a QCI value, a GBR (Guaranteed Bit Rate), an MBR (Maximum Bit Rate), and the like.
Specifically, the setting of the identification information for identifying the service type of the terminal call may be implemented in the following two ways:
the first mode is as follows: the identification information is set by setting a flag bit in a Spare field (Spare) of a message applying for bearer resources.
As shown in fig. 2, the service type of the terminating call is identified by using a Spare field (Spare) in the Flow QoS cell (type 81). The service type can be identified by the flag bits 0 and 1. For example, if the flag bit is 0, it indicates that the service type is non-trunking service, and if the flag bit is 1, it indicates that the service type is trunking service. That is, when the Spare field is 0, it indicates that the service type of the terminal call is non-trunking service; when the Spare field is 1, it indicates that the service type of the terminal call is the trunking service.
In the second mode, the identification information is set by applying for the value of the service quality level identification in the message carrying the resource.
As shown in fig. 3, the traffic type of the terminal call is identified by the value of the quality of service class identifier (QCI) in the Flow QoS cell (type 81). In particular, cluster traffic may be represented using a special QCI value. Generally, the value range of the QCI is 1 to 255, and when the value of the QCI is 1 to 9, the QCI is used for indicating that the service type is non-trunking service, so that trunking service can adopt values within 1 to 255 except 1 to 9. For example, in one embodiment of the invention, the cluster services may be represented by 65, 66, 69, 70. When the value of QCI is any one value of 1-9, the service type of the terminal call is indicated to be non-trunking service; when the value of the QCI is any one of 65, 66, 69 and 70, the service type of the terminal call is indicated as the group service.
Step S114, the enhanced mobile management unit sets the identification information and then sends a message for applying for bearing resources to the service gateway.
Specifically, after the setting of the identification information is completed in step S113, the enhanced mobility management unit sends a message for applying for bearer resources to the serving gateway, where the message for applying for bearer resources carries the set identification information, and further, the message for applying for bearer resources also includes bearer resources required by the terminal, such as a QCI value, a GBR (Guaranteed Bit Rate), an MBR (Maximum Bit Rate), and the like.
Step S115, the service gateway receives the message of applying for the bearer resource, and sends the message of applying for the bearer resource to the second core network.
Step S12, the second core network determines the service type of the terminal call according to the message of applying for bearing resources.
In the embodiment of the present invention, the determination of the service type of the terminal call according to the message for applying for the bearer resource may be performed by a PDN gateway in the second core network, or may be performed by another network element in the second core network.
Taking the PDN gateway as an example, specifically, after receiving the message for applying for bearer resources sent by the serving gateway of the first core network, the PDN gateway of the second core network determines the service type of the terminal call according to the identification information carried in the message for applying for bearer resources.
In this embodiment of the present invention, when the identification information carried in the message applying for bearer resource is set in the first manner, that is, by setting a flag bit in an idle field of the message applying for bearer resource, step S12 includes the following steps:
step S121, the second core network determines whether the flag bit satisfies a first preset condition according to the message of applying for bearing the resource, if so, the service type of the terminal call is a first service type, and if not, the service type of the terminal call is a second service type.
In this embodiment of the present invention, when the identification information carried in the message for applying for bearer resource is set in the first manner, that is, the identification information is set by using the value of the qos class identifier in the bearer resource message, step S12 includes the following steps:
step S122, the second core network determines whether the value of the qos class identifier satisfies a second preset condition according to the message for applying for the bearer resource, if so, the service type of the terminal call is the second service type, and if not, the service type of the terminal call is the first service type.
Specifically, the first preset condition is that the flag bit is 1. Therefore, when the flag bit is 1, the first preset condition is met, and at this time, the service type of the terminal call can be judged to be the first service type (trunking service); when the flag bit is 0, the first preset condition is not satisfied, and at this time, the service type of the terminal call can be determined to be a second service type (non-trunking service).
The second preset condition is that the QCI value is any one of 1-9. Therefore, when the QCI value is any one of values 1 to 9, the second preset condition is satisfied, and at this time, the service type of the terminal call can be determined to be the second service type (non-trunking service); when the QCI value is any one of 65, 66, 69 and 70, the second preset condition is not satisfied, and the service type of the terminal call can be determined to be the first service type (group service).
Step S13, if the service type of the terminal call is the first service type, the second core network starts a bearer resource allocation procedure of the first service type according to a first preset policy.
In the embodiment of the present invention, if the service type of the terminal call is the first service type, starting the first service type bearer resource allocation procedure according to the first preset policy may be performed by the PDN gateway in the second core network, or may be performed by another network element in the second core network.
Optionally, in this embodiment of the present invention, the first preset policy may include:
and 3, directly triggering a newly-built cluster bearing flow no matter whether the existing cluster bearing meets the requirement of the quality of service (QoS) of the applied bearing resource or not.
Specifically, step S13 includes the following steps:
step S131, if the existing cluster bearer meets the service quality requirement of the requested bearer resource, the cluster bearer flow is triggered to be modified.
The qos requirement of the applied bearer resource may be determined by the QCI, MBR, and GBR included in the message of the applied bearer resource.
As shown in fig. 4, taking the PDN gateway as an example, specifically, if the service type of the terminal call is the first service type (trunking service), the PDN gateway of the second core network detects whether an existing trunking bearer can meet the qos requirement of the requested bearer resource, that is, the PDN gateway of the second core network detects whether a QCI, an MBR, and a GBR in the existing trunking bearer meet the QCI, the MBR, and the GBR in the message requesting for the bearer resource, and if so, indicates that the existing trunking bearer meets the qos requirement of the requested bearer resource, and triggers modification of the trunking bearer flow according to a policy used by the PDN gateway of the second core.
Wherein, the cluster bearing flow modifying process comprises the following steps: and triggering bearer modification by the PDN gateway of the second core network, superposing a bearer TFT (Traffic Flow Template) to the existing trunking bearer, and sending a modified trunking bearer message to the service gateway of the first core network, wherein the service gateway of the first core network returns a response of modifying the trunking bearer message to the PDN gateway of the second core network after receiving the modified trunking bearer message sent by the PDN gateway of the second core network.
Step S132, if the existing cluster bearer does not meet the service quality requirement of the requested bearer resource, triggering a new cluster bearer flow.
As shown in fig. 4, if the PDN gateway of the second core network detects whether the QCI, MBR, and GBR in the existing trunking bearer satisfy the QCI, MBR, and GBR in the message of applying for bearer resources, if not, it indicates that the existing trunking bearer does not satisfy the qos requirement of the applied bearer resources, and then according to the policy used by the second core gateway, a new trunking bearer flow is triggered.
Wherein, the new cluster bearing process is as follows: and the PDN gateway of the second core network triggers the newly-built cluster bearer and sends a newly-built cluster bearer message to the service gateway of the first core network, and the service gateway of the first core network returns a response of the newly-built cluster bearer message to the PDN gateway of the second core network after receiving the newly-built cluster bearer message sent by the PDN gateway of the second core network.
Step S133, directly triggering the newly-built cluster bearer flow regardless of whether the existing cluster bearer meets the quality of service requirement of the requested bearer resource.
Step S14, if the service type of the terminal call is the second service type, the second core network starts the second service type bearer resource allocation procedure according to the second preset policy.
In the embodiment of the present invention, if the service type of the terminal call is the second service type, starting the second service type bearer resource allocation procedure according to the second preset policy may be performed by the PDN gateway in the second core network, or may be performed by another network element in the second core network.
Optionally, the second preset policy may include:
and 4, if the existing non-cluster bearer meets the service quality requirement of the applied bearer resource, triggering and modifying the non-cluster bearer flow.
And 5, if the existing non-cluster bearer does not meet the service quality requirement of the applied bearer resource, triggering to establish a new non-cluster bearer flow.
Specifically, step S14 includes the following steps:
step S141, if the existing non-cluster bearer meets the quality of service requirement of the requested bearer resource, triggering to modify the non-cluster bearer flow.
As shown in fig. 5, taking the PDN gateway as an example, specifically, if the service type of the terminal call is the second service type (non-trunking service), the PDN gateway of the second core network detects whether an existing non-trunking bearer can meet the qos requirement of the requested bearer resource, that is, the PDN gateway of the second core network detects whether a QCI, a MBR, and a GBR in the existing non-trunking bearer meet the qos requirement of the requested bearer resource message, and if so, indicates that the existing non-trunking bearer meets the qos requirement of the requested bearer resource, and triggers a bearer modification procedure according to a policy used by the second core gateway.
Wherein, the non-cluster bearing flow is modified as follows: and triggering and modifying the non-trunking bearer by the PDN gateway of the second core network, superposing a bearer TFT (Traffic Flow Template) to the existing non-trunking bearer, and sending a message for modifying the non-trunking bearer to the service gateway of the first core network, wherein after receiving the message for modifying the non-trunking bearer sent by the PDN gateway of the second core network, the service gateway of the first core network returns a response for modifying the non-trunking bearer to the PDN gateway of the second core network.
Step S142, if the existing non-cluster bearer does not meet the quality of service requirement of the requested bearer resource, triggering a new non-cluster bearer flow.
As shown in fig. 5, if the PDN gateway of the second core network detects whether the QCI, MBR, and GBR in the existing non-trunking bearer satisfy the QCI, MBR, and GBR in the bearer resource application message, if not, it indicates that the existing non-trunking bearer does not satisfy the qos requirement of the requested bearer resource, and then according to the policy used by the second core gateway, a new non-trunking bearer flow is triggered.
The newly-built non-cluster bearing process comprises the following steps: and the PDN gateway of the second core network triggers the new non-trunking bearer and sends a new non-trunking bearer message to the service gateway of the first core network, and the service gateway of the first core network returns a response of the new non-trunking bearer message to the PDN gateway of the second core network after receiving the new non-trunking bearer message sent by the PDN gateway of the second core network.
The method comprises the steps that identification information for identifying the service type of a terminal call is carried in a message of applying for bearing resources sent to a PDN gateway of a second core network by a service gateway of a first core network, so that the PDN gateway of the second core network can distinguish the service type of the terminal call through the identification information to distinguish whether the bearing resources required by the terminal are cluster bearing or non-cluster bearing, and if the identification information is identified as the cluster service, the PDN gateway of the second core network determines to newly establish or modify the cluster bearing according to a first preset strategy; and if the identification information is identified as the non-trunking service, the PDN gateway of the second core network determines to newly build or modify the non-trunking bearer according to a second preset strategy. The scheme effectively solves the problem that a core network PDN Gateway (PGW) can not distinguish cluster bearing from non-cluster bearing, realizes the priority scheduling of the cluster service, avoids the occupation of non-cluster service resources and improves the quality of the effect of the terminal cluster service under roaming.
The invention also provides a system for distinguishing the cluster service bearer by the core network, and the system for distinguishing the cluster service bearer by the core network can be used for realizing the method for distinguishing the cluster service bearer by the core network. The terminal comprises a terminal, a first core network and a second core network.
Specifically, the terminal is configured to send a call service request to the first core network. Here, the terminal includes a calling terminal and a called terminal.
The first core network is used for receiving a call service request sent by the terminal and sending a message for applying for bearing resources to the second core network; the message carrying the resource carries identification information for identifying the service type requested by the terminal.
The second core network is used for judging the service type of the terminal call according to the message of applying for bearing the resource; if the service type of the terminal call is a first service type, the second core network starts a first service type bearing resource allocation process according to a first preset strategy; and if the service type of the terminal call is a second service type, the second core network starts a second service type bearing resource allocation process according to a second preset strategy.
The first core network is a broadband trunking core network of a roaming place where the terminal is located, that is, the terminal roams to a broadband trunking core network of a visited place. The second core network is a broadband cluster core network of the home location processed by the terminal. The first service type is a trunking service type, wherein the trunking service type may be a point-to-point single call service or a group call calling service.
The second service type is a non-trunking service type, i.e. a PS service.
The technical solution of the present invention is explained below with a specific example.
The cluster full duplex single call flow is taken as an example for explanation, as shown in fig. 6.
Description of the preconditions:
1. UE1 is end user 1, which roams to visited place 1, whose visited place Serving Gateway (SGW) is V-SGW1, whose home PDN Gateway (PGW) is H-PGW 1;
2. UE2 is end user 2, which roams to visited place 2, whose visited place SGW is V-SGW2, and whose home location PGW is H-PGW 2;
3. UE1 and UE2 are conducting non-trunking traffic, and QCI in quality of service QoS of PS bearers on UE1 and UE2 are both 1, that is, QCI is 1;
4. the H-PGW uses policy 2, that is, if the existing cluster bearer does not meet the QoS requirement, the policy of the newly-built cluster bearer flow may be triggered to perform cluster resource allocation.
As shown in FIG. 6, the overall process steps 1-28 initiate a clustered full duplex single call process for UE2 for UE 1. Therein, bearer resource allocation flows for UE1 and UE2 are represented within rectangular boxes.
The description is made with respect to bearer resource allocation of UE 2:
step10) and V-eMME2 apply for the trunking service to allocate the trunking bearer resource QoS (QCI ═ 1), and after receiving the call service request sent by UE2, notify the V-SGW through the bearer resource application message (the message is not shown in the figure), and notify the H-PGW2 through the bearer resource application message by V-SGW2 to allocate the trunking bearer resource.
The H-PGW2 determines whether the existing PS bearer can satisfy the application requirement according to the QoS (QCI ═ 1) in the bearer resource application message. The QCI value in the QoS of the existing PS bearer is also 1, so that the requirement of the QoS (QCI ═ 1) to be applied can be satisfied. However, no cluster bearer can satisfy the QoS (QCI ═ 1) of the applied bearer resource, so the H-PGW2 initiates a modification procedure of the newly-built cluster bearer, and sends a message of the newly-built cluster bearer to the V-SGW 2.
The H-PGW2 uses policy 2, and although the existing PS Bearer QoS (QCI ═ 1) can satisfy the applied QoS (QCI ═ 1), no cluster Bearer can satisfy the QoS (QCI ═ 1) of the applied resource, so the H-PGW2 initiates a modification procedure of newly establishing the cluster Bearer, and sends a Create Bearer Request message to the V-SGW 2.
Step13), bearer resource allocation of UE 1: similar to the bearer resource allocation of the UE 2.
The above embodiments are merely illustrative of the technical ideas and features of the present invention, and are intended to enable those skilled in the art to understand the contents of the present invention and implement the present invention, and not to limit the scope of the present invention. All equivalent changes and modifications made within the scope of the claims of the present invention should be covered by the claims of the present invention.
It will be understood that modifications and variations can be made by persons skilled in the art in light of the above teachings and all such modifications and variations are intended to be included within the scope of the invention as defined in the appended claims.
Claims (6)
1. A method for distinguishing cluster service bearer by a core network is characterized by comprising the following steps:
a first core network receives a call service request sent by a terminal and sends a message for applying for bearing resources to a second core network; the message of the bearing resource carries identification information for identifying the service type requested by the terminal; the first core network is a broadband cluster core network of a roaming place where the terminal is located, and the second core network is a broadband cluster core network of a home place where the terminal is located;
the second core network judges the service type of the terminal call according to the message of applying for bearing resources;
if the service type of the terminal call is a first service type, the second core network starts a first service type bearing resource allocation process according to a first preset strategy; the first service type is a cluster service type; the starting of the first service type bearer resource allocation process according to the first preset strategy comprises the following steps: if the existing cluster bearing meets the service quality requirement of the applied bearing resource, triggering and modifying the cluster bearing process; if the existing cluster bearing does not meet the service quality requirement of the applied bearing resource, triggering a newly-built cluster bearing process;
if the service type of the terminal call is a second service type, the second core network starts a second service type bearing resource allocation process according to a second preset strategy; the second service type is a non-cluster service type; the starting of the second service type bearer resource allocation process according to the second preset strategy comprises: if the existing non-cluster bearing meets the service quality requirement of the applied bearing resource, triggering and modifying the non-cluster bearing process; and if the existing non-cluster bearing does not meet the service quality requirement of the applied bearing resource, triggering a new non-cluster bearing process.
2. The method for differentiating the cluster service bearer by the core network according to claim 1, wherein the identification information is identified by setting a flag bit in an idle field of the message for applying for bearer resources;
the second core network determining the service type of the terminal call according to the message applying for bearing resources includes:
the second core network judges whether the flag bit meets a first preset condition according to the message of applying for bearing the resource, if so, the service type of the terminal call is a first service type; and if not, the service type of the terminal call is a second service type.
3. The method for differentiating the cluster service bearer of the core network as claimed in claim 1, wherein the identification information is identified by a value of a quality of service class identifier in the message of applying for bearer resources;
the second core network determining the service type of the terminal call according to the message applying for bearing resources includes:
the second core network judges whether the value of the service quality grade identification meets a second preset condition according to the message of applying for bearing resources, if so, the service type of the terminal call is a second service type; if not, the service type of the terminal call is the first service type.
4. The method for differentiating cluster service bearers by core network according to claim 1, wherein the first core network includes a cluster control function module, an enhanced mobility management unit and a serving gateway;
the first core network receiving a call service request sent by a terminal and sending a message for applying for bearing resources to a second core network comprises:
the enhanced mobile management unit receives a call service request sent by the terminal and sends a call service message to the cluster control function module;
the cluster control function module establishes a call service according to the call service message;
the enhanced mobile management unit determines the service type of the terminal according to the call service request, and sets the identification information and determines the bearing resource required to be applied according to the service type;
the enhanced mobile management unit sets the identification information and then sends the message of applying for bearing resources to the service gateway;
and the service gateway receives the message for applying for bearing the resources and sends the message for applying for bearing the resources to the second core network.
5. The method for differentiating the cluster service bearer of the core network according to claim 1, wherein the method further comprises:
and judging whether the existing cluster bearing or non-cluster bearing meets the service quality requirement of the applied bearing resource or not according to the value of the service quality grade identification carried in the message for applying for bearing the resource.
6. A system for distinguishing cluster service bearing by a core network is characterized by comprising a terminal, a first core network and a second core network;
the terminal is used for sending a call service request to the first core network;
the first core network is used for receiving a call service request sent by a terminal and sending a message for applying for bearing resources to a second core network; the message of the bearing resource carries identification information for identifying the service type requested by the terminal; the first core network is a broadband cluster core network of a roaming place where the terminal is located, and the second core network is a broadband cluster core network of a home place where the terminal is located;
the second core network judges the service type of the terminal call according to the message of applying for bearing resources;
if the service type of the terminal call is a first service type, the second core network starts a first service type bearing resource allocation process according to a first preset strategy; the first service type is a cluster service type; the starting of the first service type bearer resource allocation process according to the first preset strategy comprises the following steps: if the existing cluster bearing meets the service quality requirement of the applied bearing resource, triggering and modifying the cluster bearing process; if the existing cluster bearing does not meet the service quality requirement of the applied bearing resource, triggering a newly-built cluster bearing process;
if the service type of the terminal call is a second service type, the second core network starts a second service type bearing resource allocation process according to a second preset strategy; the second service type is a non-cluster service type; the starting of the second service type bearer resource allocation process according to the second preset strategy comprises: if the existing non-cluster bearing meets the service quality requirement of the applied bearing resource, triggering and modifying the non-cluster bearing process; and if the existing non-cluster bearing does not meet the service quality requirement of the applied bearing resource, triggering a new non-cluster bearing process.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810803717.8A CN110740425B (en) | 2018-07-20 | 2018-07-20 | Method and system for distinguishing cluster service bearer by core network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810803717.8A CN110740425B (en) | 2018-07-20 | 2018-07-20 | Method and system for distinguishing cluster service bearer by core network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110740425A CN110740425A (en) | 2020-01-31 |
| CN110740425B true CN110740425B (en) | 2021-11-02 |
Family
ID=69235740
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810803717.8A Active CN110740425B (en) | 2018-07-20 | 2018-07-20 | Method and system for distinguishing cluster service bearer by core network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110740425B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114650557B (en) * | 2020-12-18 | 2023-03-21 | 成都鼎桥通信技术有限公司 | Allopatric disaster-tolerant distributed roaming network architecture, communication method and storage medium |
| CN117440358A (en) * | 2022-07-14 | 2024-01-23 | 维沃移动通信有限公司 | Communication processing method, device, communication equipment and readable storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103037316A (en) * | 2012-12-17 | 2013-04-10 | 海能达通信股份有限公司 | Method, device and system for preferential gaining of speaking right of group-calling same-level users |
| CN103581839A (en) * | 2012-07-19 | 2014-02-12 | 中兴通讯股份有限公司 | Broadband trunking service realizing method and broadband trunking service realizing system |
| CN104244196A (en) * | 2013-06-14 | 2014-12-24 | 中国普天信息产业股份有限公司 | Service building method in cluster system |
| CN104254055A (en) * | 2013-06-27 | 2014-12-31 | 电信科学技术研究院 | Emergency calling method, device and system |
| CN104995932A (en) * | 2013-09-26 | 2015-10-21 | 华为技术有限公司 | Method and device for allocating wireless resources |
| CN105323720A (en) * | 2014-06-30 | 2016-02-10 | 中兴通讯股份有限公司 | Trunking communication business processing method, trunking core network equipment, and user equipment |
| CN106162573A (en) * | 2016-09-14 | 2016-11-23 | 海能达通信股份有限公司 | A kind of cluster multi call processing method, relevant device and system |
| CN107566994A (en) * | 2016-07-01 | 2018-01-09 | 中兴通讯股份有限公司 | Group region method of adjustment and system, cluster application server and trunking user terminal |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105594289B (en) * | 2013-09-30 | 2020-04-28 | 诺基亚技术有限公司 | Group communication |
-
2018
- 2018-07-20 CN CN201810803717.8A patent/CN110740425B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103581839A (en) * | 2012-07-19 | 2014-02-12 | 中兴通讯股份有限公司 | Broadband trunking service realizing method and broadband trunking service realizing system |
| CN103037316A (en) * | 2012-12-17 | 2013-04-10 | 海能达通信股份有限公司 | Method, device and system for preferential gaining of speaking right of group-calling same-level users |
| CN104244196A (en) * | 2013-06-14 | 2014-12-24 | 中国普天信息产业股份有限公司 | Service building method in cluster system |
| CN104254055A (en) * | 2013-06-27 | 2014-12-31 | 电信科学技术研究院 | Emergency calling method, device and system |
| CN104995932A (en) * | 2013-09-26 | 2015-10-21 | 华为技术有限公司 | Method and device for allocating wireless resources |
| CN105323720A (en) * | 2014-06-30 | 2016-02-10 | 中兴通讯股份有限公司 | Trunking communication business processing method, trunking core network equipment, and user equipment |
| CN107566994A (en) * | 2016-07-01 | 2018-01-09 | 中兴通讯股份有限公司 | Group region method of adjustment and system, cluster application server and trunking user terminal |
| CN106162573A (en) * | 2016-09-14 | 2016-11-23 | 海能达通信股份有限公司 | A kind of cluster multi call processing method, relevant device and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110740425A (en) | 2020-01-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3454601B1 (en) | Method and apparatus for controlling quality of service | |
| KR101278516B1 (en) | Paging method, core network device, wireless access network device, and gateway device | |
| KR102148341B1 (en) | Method and device for setting priority of data transmission | |
| US9655156B2 (en) | Bearer establishment method, base station, packet data gateway, and computer system | |
| KR20200024363A (en) | Devices and methods of operating and controlling data flow | |
| CN110741701B (en) | Method and base station for acquiring data radio bearer identifier | |
| EP2481239B1 (en) | Method and Apparatus for handling an evolved Allocation and Retention Priority | |
| CN108141867B (en) | Method for improved priority handling of data stream transmissions in a communication system | |
| CN110691382B (en) | Wireless resource allocation method and network element equipment | |
| WO2018006773A1 (en) | Information and data transmission method and device, access network, and system | |
| US9125106B1 (en) | Management of quality of service policy changes in a communication network based on whether the policy change is an upgrade or a downgrade | |
| CN107911849B (en) | Access preemption method in admission control judgment of LTE (Long term evolution) system | |
| US9980152B2 (en) | Method of indication of available radio resources | |
| CN106488519B (en) | Voice call method and terminal | |
| CN110740425B (en) | Method and system for distinguishing cluster service bearer by core network | |
| EP2632093B1 (en) | Packet switched domain service processing method and device | |
| CN103813298A (en) | Backhaul network bearer management method and device | |
| CN109451539B (en) | Service quality improving method and device | |
| WO2017148243A1 (en) | Control method and system for data transmission, and data transmission method and device | |
| CN110392019B (en) | Method and system for establishing special load bearing of cluster audio and video service | |
| EP2763485B1 (en) | Scheduling method in a mobile telecommunication system | |
| CN114423031A (en) | Mapping method for 5G service quality flow and data radio bearer | |
| CN113630778A (en) | Dynamic control method and terminal for QoS (quality of service) flow | |
| CN111294980B (en) | Method and device for establishing radio bearer | |
| WO2020223861A1 (en) | User equipment strategy configuration method and apparatus, user equipment, base station, and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |