CN113709680B

CN113709680B - Group calling method and cluster server

Info

Publication number: CN113709680B
Application number: CN202010430453.3A
Authority: CN
Inventors: 范珂; 刘棣; 魏婷婷
Original assignee: Hytera Communications Corp Ltd
Current assignee: Hytera Communications Corp Ltd
Priority date: 2020-05-20
Filing date: 2020-05-20
Publication date: 2023-10-24
Anticipated expiration: 2040-05-20
Also published as: CN113709680A

Abstract

The embodiment of the invention provides a group calling method and a group management server so as to realize CF addressing. The group calling method is based on a cluster server, the cluster server comprises a PF entity and a GSM functional entity, and the GMS functional entity maintains a mapping relation between a group identification GID and a service identification of a service control function CF. The method comprises the following steps: the PF entity receives the join request (carrying the target GID); if the mapping relation matched with the target GID is not stored locally, the PF entity acquires corresponding CF configuration information from the GMS according to the target GID; the CF configuration information at least comprises CF service identification; the PF entity locally stores the mapping relation between the target GID and the acquired CF service identifier, thereby completing CF addressing.

Description

Group calling method and cluster server

Technical Field

The present invention relates to the field of communications, and in particular, to a group call method and a cluster server.

Background

MCS (Mission Critical System) is a complete set of trunked communication systems established by 3GPP over LTE to address public safety. MCPTT (Mission Critical Push To Talk) as an important component of the MCS system, provides voice trunked communication services.

MCPTT may provide a group call function (group call), and the existing MCPTT standard has the following two requirements for group call:

1. the group call service of a certain group is uniformly implemented on a specific CF (Controlling Function, service control function) entity, and the CF entity is responsible for call control and talk right management of the group call.

2. When a user initiates a group call, please refer to fig. 1, the group call request first reaches a caller PF (particulate matter function) entity, the PF entity addresses (i.e. searches for a corresponding CF entity) the CF entity corresponding to the group to be called, and the group call request is submitted to the found CF entity for processing.

The 3GPP standard does not specify the problem of how the PF entity addresses CF entities in the MCPTT group call.

Disclosure of Invention

In view of this, embodiments of the present invention provide a group call method and a group management server to implement CF addressing.

In order to achieve the above object, the embodiment of the present invention provides the following technical solutions:

the group calling method is based on a cluster server, wherein the cluster server comprises a user management function PF entity and a group management service GMS function entity, and the GMS function entity maintains a mapping relation between a group identification GID and a service identification of a service control function CF;

the method comprises the following steps:

the PF entity receives the joining request; the joining request carries a target GID;

if the mapping relation matched with the target GID is not stored locally, the PF entity acquires corresponding CF configuration information from the GMS according to the target GID; the CF configuration information at least comprises a CF service identifier;

and the PF entity locally stores the mapping relation between the target GID and the acquired CF service identifier.

Optionally, the method further comprises: the PF entity subscribes CF configuration information of the target GID to the GMS so that the PF entity is notified when the CF configuration information of the target GID is changed.

Optionally, the method further comprises: the PF entity receives a subscription notification message of the GMS; the subscription notification message includes the latest CF configuration information corresponding to the target GID; the latest CF configuration information comprises a new CF service identifier; the PF entity locally stores the mapping relation between the target GID and the new CF service identifier.

Optionally, the mapping relation maintained on the GMS functional entity is configured by an OAM operation management maintenance entity.

Optionally, the method further comprises: the PF entity receives a group call request; the group call request carries the target GID; and the PF entity transmits the group call request to the corresponding CF entity for processing according to the mapping relation between the locally stored target GID and the CF service identifier.

A cluster server comprising at least a processor and a memory; the processor executes the following steps by executing the program stored in the memory and calling other devices: receiving a joining request; the joining request carries a target GID; if the mapping relation matched with the target GID is not stored locally, acquiring corresponding CF configuration information from a Group Management Service (GMS) functional entity according to the target GID; the GMS functional entity is configured to: maintaining a mapping relation between the group identification GID and the CF service identification; receiving CF configuration information returned by the GMS; the CF configuration information at least comprises a CF service identifier; and locally storing the mapping relation between the target GID and the acquired CF service identifier.

Optionally, the processor further executes the following steps by executing the program stored in the memory and calling other devices: and subscribing the CF configuration information of the target GID to the GMS so as to enable the GMS to inform the PF entity when the CF configuration information of the target GID is changed.

Optionally, the processor further executes the following steps by executing the program stored in the memory and calling other devices: receiving a subscription notification message of the GMS; the subscription notification message includes the latest CF configuration information corresponding to the target GID; the latest CF configuration information comprises a new CF service identifier; and locally storing the mapping relation between the target GID and the new CF service identifier.

A cluster server comprising at least a processor and a memory; the processor executes the following steps by executing the program stored in the memory and calling other devices:

maintaining a mapping relation between the group identification GID and the service identification of the service control function CF;

returning corresponding CF configuration information according to the target GID provided by the PF entity; the CF configuration information at least comprises CF service identification.

Optionally, the processor further executes the following steps by executing the program stored in the memory and calling other devices: when the CF configuration information of the target GID is changed, a subscription notification message is sent to the PF entity; the subscription notification message includes the latest CF configuration information corresponding to the target GID; the latest CF configuration information includes a new CF service identification.

It can be seen that, in the embodiment of the present invention, the relation between the GID and the CF service identifier is maintained by the GMS functional entity, and when the PF entity receives the join request carrying the target GID, and the corresponding mapping relation is not stored locally, the PF obtains the corresponding CF service identifier from the GMS, and stores the mapping relation between the target GID and the CF service identifier, thereby completing CF addressing.

Drawings

Fig. 1 is a group call flow in the existing MCPTT standard;

fig. 2 is an exemplary structure of a group call system according to an embodiment of the present invention;

FIG. 3 is an exemplary architecture of a PF entity provided in accordance with an embodiment of the present invention;

fig. 4 is an exemplary structure of GMS provided by an embodiment of the present invention;

fig. 5 is an exemplary flow of a group call method according to an embodiment of the present invention;

fig. 6 is another exemplary flow of a group call method according to an embodiment of the present invention;

FIG. 7 is another exemplary architecture of a PF entity provided in accordance with an embodiment of the present invention;

fig. 8 is an exemplary interaction flow between a PF entity and GMS when CF configuration information is changed according to an embodiment of the present invention;

fig. 9 is a flowchart of another exemplary group call method according to an embodiment of the present invention;

fig. 10 is an exemplary hardware structure of a cluster server according to an embodiment of the present invention.

Detailed Description

For purposes of reference and clarity, technical terms, abbreviations or abbreviations used hereinafter are summarized as follows:

PF (: a partitioing function, user management function;

CF: controlling Function, traffic control function;

GMS: a group management server;

GID: groupId, group identification, a unique identifier for identifying a group;

affiationrequest: a join request;

3GPP:3rd Generation Partnership Project third generation partnership project;

MCPTT: mission Critical Push To Talk, mission critical push-to-talk;

UE: user Equipment, user terminal;

OAM: operation Administration and Maintenance, operation management maintenance;

subscribe Request: a subscription request;

server: a server, an entity;

PSI: public Service Identity, public service identity, actually a URI, may be routed to the corresponding CF.

The group call function may serve public safety areas, for example, patrol traffic polices may establish a group, and a caller within the group may establish a group call to subscribers belonging to the group.

When a user initiates a group call, a calling PF entity is required to address CF entities corresponding to a group to be called.

The embodiment of the invention provides a group calling method and a cluster server (PF entity and GMS entity) so as to improve the data processing speed of group calling while realizing CF entity addressing.

Fig. 2 shows an exemplary structure of a group call system in which PF and GMS entities are located, and in the group call system, a plurality of PF entities and a plurality of CF entities are included.

The PF entity and the CF entity are both functional modules defined by the 3GPP standard, wherein the PF entity is used for user access control, and the CF entity is used for service control. The group calling service of a certain group is uniformly realized on a specific CF entity, and the CF entity is responsible for the call control and the speaking right management of the group calling.

Besides PF entity and CF entity, the group call system also includes GMS and GM OAM. GMS is also a functional module defined by the 3GPP standard for group information management. The invention expands the mapping relation between GID and CF service mark (or expands CF PSI configuration information) on GMS, which can be configured by GMS OAM. Both the GMS entity and the PF entity belong to a cluster server.

Based on the mapping relation, the core of the invention is as follows: after a User (UE) sends a join request to its home group, the PF obtains group information from the GMS according to the GID in the join request (which may be referred to as a target GID), where the group information includes CF configuration information (e.g., CF service identifier). After the acquisition is successful, the PF stores the mapping relation between the target GID and the CF service identifier locally.

The CF service identity is PSI. Table 1 below shows one exemplary format of CF PSI configuration information.

TABLE 1

It should be noted that "N" in table 1 above indicates that this configuration item is not active, and "Y" indicates that this configuration item is active, that is, controllingfunction psi is not active on MCPTTUE, and is useful on MCPTTServer.

FIG. 3 illustrates an exemplary structure of a PF entity: a communication unit 1 and an addressing unit 2;

fig. 4 shows an exemplary structure of the GMS, comprising a maintenance unit 3 and a query unit 4. The maintenance unit 3 is configured to maintain a mapping relationship between the GID and the CF service identifier.

The functionality of each unit will be further described herein in connection with the paging method.

Fig. 5 illustrates an exemplary flow of the group call method described above, including:

s1: the PF entity receives the join request.

The above-mentioned join request is transmitted by UEs belonging to a certain group. The GID is carried in the join request and may be referred to as the target GID.

In one example, step S1 may be performed by the aforementioned communication unit 1.

S2: if the mapping relation matched with the target GID is not stored locally, the PF entity acquires corresponding CF configuration information from the GMS according to the target GID.

Specifically, the PF entity may obtain corresponding CF configuration information from the GMS through the CSC-3 interface.

Step S2 may be performed by the addressing unit 2 as described above.

On the GMS side, the query unit 4 may query the corresponding CF configuration information from the maintenance unit according to the target GID provided by the PF entity, and return the query result (i.e., CF configuration information).

The CF configuration information includes a CF service identifier, and the CF service identifier is used for characterizing the CF entity.

S3: the PF entity locally stores the mapping relation between the target GID and the acquired CF service identifier.

In one example, step S3 may be performed by the addressing unit 2 described previously.

Because each group call needs to find the corresponding CF service identifier according to the GID, the PF entity stores the mapping relationship locally, which is convenient for searching. And under the condition that the local information is not found, acquiring corresponding CF configuration information from the GMS functional entity.

It should be noted that, for the case where the mapping relationship between the target GID and the CF service identifier is already stored locally, if the PF entity receives the join request of the UE for the target GID, steps S2-S3 may not be executed any more, or, considering the possibility of migrating the group service CF, steps S2-S3 may be executed again after receiving the join request of the UE each time.

Of course, in addition to executing steps S2-S3 each time a join request is accepted, there are the following processing methods:

referring to fig. 6, after the step S3, the method may further include the following steps:

s4: the PF entity subscribes to the CF configuration information of the target GID from the GMS.

After subscription, the GMS notifies the PF entity when CF configuration information of the target GID is changed.

In one example, referring to fig. 7, the pf entity may further include a subscription unit 5 to perform step S4 described above.

Fig. 8 shows interactions between PF entity and GMS when CF configuration information is changed, which may include the steps of:

s801: when the CF configuration information of the target GID is changed, the GMS transmits a subscription notification message to the PF entity.

The subscription notification message may specifically include the latest CF configuration information (e.g., new CF service identifier) corresponding to the target GID.

In one example, step S801 may be performed by the aforementioned maintenance unit 3.

S802: the PF entity receives the subscription notification message.

In one example, step S802 may be performed by the aforementioned communication unit 1.

S803: the PF locally stores the mapping relation between the target GID and the new CF service identification.

In one example, step S803 may be performed by the aforementioned addressing unit 2.

After subscription, when the CF configuration changes, the GMS notifies the PF entity, so as to ensure the real-time performance of the configuration relationship of the PF entity.

It should be noted that it is conventional practice to pre-deploy the mapping relationship between GID and CF service identifier on the PF entity (instead of GMS). For example, if 10 PFs, 10 groups and 10 CFs are networked, then 10 CFs corresponding to group IDs need to be configured on each PF according to the normal practice. Thus, the greater the number of groups, the more content that needs to be configured on each PF. This implementation, while meeting the basic requirements of addressing, is complex to configure and costly to maintain. Once the group service migration needs to be modified, the mapping relationship on all PF entities needs to be modified.

In the embodiment of the invention, after the mapping relation between the GID and the CF service identifier is managed on the GMS in a centralized way, the subscription is combined, once the group service migration needs to be modified, only the configuration on the GMS needs to be modified, and the mapping relation between the GID and the CF service identifier does not need to be configured and maintained on each PF entity independently, so that the configuration complexity and the maintenance cost are greatly reduced.

In addition, the PF entity locally stores the mapping relation between the target GID and the acquired CF service identifier, so that CF addressing can be conveniently and quickly performed. Through subscription, when the CF configuration changes, the GMS informs the PF entity, and the real-time performance of the local configuration relation of the PF entity is ensured.

The group call method will be described in detail below taking the target GID as GID1 as an example (please refer to fig. 9 (the step of bold italics in fig. 9 is a new step), which may include the following steps:

s901: the UE initiates Affiliation request (join request) to request to join the group GID1.

Since the PF entity is responsible for user access control, affiliation request is sent to the PF entity.

S901 is similar to S1 described above, and will not be described here.

S902: after receiving Affiliation request, the PF entity initiates Group ServerPSI Request (group server PSI request) to the GMS according to GID1 to acquire CF configuration information corresponding to GID1.

Step S902 is similar to step S2 described above, and will not be described here.

S903: the GMS returns a Group ServerPSI Response response.

Group ServerPSI Response response carries CF configuration information corresponding to GID1.

S904: the PF records the mapping relation between GID1 and CF service identification locally.

Step S904 is similar to step S3 described above, and will not be described here.

S905: the PF initiates Group ServerPSI Subscribe Request the subscription group information to the GMS according to GID1.

Step S905 is similar to step S4 described above, and will not be described here.

S906: the GMS returns a Group ServerPSI Subscribe Response response indicating acceptance of the subscription request.

Step S906 may be performed by the aforementioned maintenance unit 3, or the GMS may add a subscription unit, to perform step S906.

S907: the UE (or client) sends Group Call Request (group call request) to initiate GID1 group call.

The group call request carries the target GID, i.e., GID1.

In one example, the group call request may be received by the aforementioned communication unit 1.

S908: and the PF entity forwards the group call request to the corresponding CF entity for processing according to the mapping relation between the locally stored target GID and the CF service identifier.

For example, assuming GID1 corresponds to CF1, the PF forwards the group call request to CF1.

In one example, step S908 may be performed by the addressing unit 2 described previously.

S909: when the CF configuration to which the GID1 belongs changes, the GMS sends a subscription notification message to the PF entity (Group ServerPSI Notify Request).

Step S909 is similar to step S801 described above, and will not be described here.

Assuming that the CF to which GID1 belongs is changed from CF1 to CF2, GMS will push the change information to all PF entities that have successfully subscribed through Group ServerPSI Notify Request.

S910: after receiving the subscription notification message, the PF entity records the mapping relation from GID1 to new CF (CF 2) locally.

Step S910 is similar to step S803 described above, and will not be described here.

S911: after the processing is successful, the PF entity returns a Group ServerPSINotify Response response to the GMS.

In one example, step S911 may be performed by the aforementioned addressing unit 2.

S912: the UE sends Group Call Request (group call request) to initiate GID1 group call again.

Step S912 is similar to step S907 described above, and will not be described here.

S913: and the PF entity forwards the group call request to the corresponding CF entity for processing according to the mapping relation between the locally stored target GID and the CF service identifier.

Assuming that the CF to which GID1 belongs is changed from CF1 to CF2, the PF entity GMS forwards the group call request to CF2.

Step S913 is similar to step S908 described above, and will not be described here.

The added PF entity of the embodiment obtains the flow of the GMS group information and the PF entity subscribes the flow of the group information to the GMS; the 3GPP standard can be subsequently pushed in considering implementation technology (extension of CSC-3 interface) as stage 3.

Fig. 10 shows a schematic diagram of a possible architecture of the cluster server (PF entity or GMS entity) in the above embodiment, including: a bus, a processor 101, a memory 102, a communication interface 103, an input device 104, and an output device 105. The processor 101, memory 102, communication interface 103, input device 104, and output device 105 are interconnected by a bus. Wherein:

a bus may comprise a path that communicates information between components of a computer system.

The processor 101 may be a general-purpose processor, such as a general-purpose Central Processing Unit (CPU), a network processor (Network Processor, NP), a microprocessor, etc., or may be an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present invention. But may also be a Digital Signal Processor (DSP), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components.

The memory 102 stores programs or scripts for implementing the technical scheme of the present invention, and may also store an operating system and other key services. In particular, the program may include program code including computer-operating instructions. Scripts are typically saved in text (e.g., ASCII) and interpreted or compiled only when called.

The input device 104 may include means for receiving data and information entered by a user, such as a keyboard, mouse, camera, voice input means, touch screen, etc.

The output device 105 may include means, such as a display screen, speakers, etc., that allow information to be output to a user.

The communication interface 103 may include devices using any transceiver or the like for communicating with other devices or communication networks, such as ethernet, radio Access Network (RAN), wireless Local Area Network (WLAN), etc.

The processor in the PF entity may perform the following steps by executing the program stored in the memory and invoking other devices:

receiving a joining request; the joining request carries a target GID;

if the mapping relation matched with the target GID is not stored locally, acquiring corresponding CF configuration information from a Group Management Service (GMS) functional entity according to the target GID; the GMS functional entity is configured to: maintaining a mapping relation between the group identification GID and the CF service identification;

receiving CF configuration information returned by the GMS; the CF configuration information at least comprises a CF service identifier;

and locally storing the mapping relation between the target GID and the acquired CF service identifier.

Specific details are set forth in the foregoing description and are not repeated herein.

In other embodiments of the present invention, the processor 101 may further execute the following steps by executing the program stored in the memory 102 and invoking other devices:

and subscribing the CF configuration information of the target GID to the GMS so as to enable the GMS to inform the PF entity when the CF configuration information of the target GID is changed.

In other embodiments of the present invention, the processor in the PF entity may further execute the following steps by executing the program stored in the memory and invoking other devices:

receiving a subscription notification message of the GMS; the subscription notification message includes the latest CF configuration information corresponding to the target GID; the latest CF configuration information comprises a new CF service identifier;

and locally storing the mapping relation between the target GID and the new CF service identifier.

The processor in the GMS entity may perform the following steps by executing the program stored in the memory and invoking other devices:

In other embodiments of the present invention, the processor in the GMS entity may further perform the following steps by executing a program stored in the memory and invoking other devices:

when the CF configuration information of the target GID is changed, a subscription notification message is sent to the PF entity; the subscription notification message includes the latest CF configuration information corresponding to the target GID; the latest CF configuration information includes a new CF service identification.

The functions of the respective units shown in fig. 3, 4, and 7 can be realized by the processor 101 executing the programs stored in the memory 102 and calling other devices.

Those of skill would further appreciate that the elements and model steps of the examples described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the elements and steps of the examples have been described generally in terms of functionality in the foregoing description to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Those skilled in the art may use different PFs for each particular application to implement the described functionality, but such implementation should not be considered to be beyond the scope of the present invention.

The steps of a PF or model described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software modules may be disposed in Random Access Memory (RAM), memory, read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, WD-ROM, or any other form of storage medium known in the art.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. The group calling method is characterized in that based on a cluster server, the cluster server comprises a user management function PF entity and a group management service GMS function entity, and the GMS function entity maintains a mapping relation between a group identification GID and a service identification of a service control function CF;

the method comprises the following steps:

2. The method as recited in claim 1, further comprising:

the PF entity subscribes CF configuration information of the target GID to the GMS so that the PF entity is notified when the CF configuration information of the target GID is changed.

3. The method as recited in claim 2, further comprising:

the PF entity receives a subscription notification message of the GMS; the subscription notification message includes the latest CF configuration information corresponding to the target GID; the latest CF configuration information comprises a new CF service identifier;

the PF entity locally stores the mapping relation between the target GID and the new CF service identifier.

4. A method according to any of claims 1-3, characterized in that the mapping relation maintained at the GMS functional entity is configured by an OAM operation management maintenance entity.

5. The method as recited in claim 4, further comprising:

the PF entity receives a group call request; the group call request carries the target GID;

and the PF entity transmits the group call request to the corresponding CF entity for processing according to the mapping relation between the locally stored target GID and the CF service identifier.

6. A cluster server comprising at least a processor and a memory; the processor executes the following steps by executing the program stored in the memory and calling other devices:

receiving a joining request; the joining request carries a target GID;

7. The cluster server of claim 6, wherein the processor further performs the steps of:

and subscribing the CF configuration information of the target GID to the GMS so as to enable the GMS to notify a PF entity when the CF configuration information of the target GID is changed.

8. The cluster server of claim 7, wherein,

the processor further executes the following steps by executing the program stored in the memory and calling other devices:

9. A cluster server comprising at least a processor and a memory; the processor executes the following steps by executing the program stored in the memory and calling other devices:

10. The cluster server of claim 9, wherein the processor further performs the steps of: