阅读说明：本技术 组呼方法和集群服务器 (Group calling method and cluster server ) 是由 范珂 刘棣 魏婷婷 于 2020-05-20 设计创作，主要内容包括：本发明实施例提供组呼方法和群管理服务器,以实现CF寻址。该组呼方法基于集群服务器,集群服务器包括PF实体和GSM功能实体,GMS功能实体上维护有群组标识GID与业务控制功能CF业务标识之间的映射关系。该方法包括：PF实体接收加入请求(携带目标GID)；若本地未保存与目标GID相匹配的映射关系,PF实体根据目标GID向GMS获取相应的CF配置信息；CF配置信息至少包含CF业务标识；PF实体在本地保存目标GID与获取到的CF业务标识之间的映射关系,从而完成了CF寻址。(The embodiment of the invention provides a group calling method and a group management server 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 a mapping relation between a group identifier GID and a service control function CF service identifier is maintained on the GMS functional entity. The method comprises the following steps: the PF entity receives a joining request (carrying a target GID); if the mapping relation matched with the target GID is not locally stored, 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; the PF entity locally saves the mapping relation between the target GID and the obtained CF service identification, thereby completing CF addressing.)

1. A group call 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 (GSM) function entity, and the GMS function entity maintains a mapping relation between a Group Identifier (GID) and a service Control Function (CF) service identifier;

the method comprises the following steps:

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

if the mapping relation matched with the target GID is not locally stored, 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 obtained CF service identifier.

2. The method of claim 1, further comprising:

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

3. The method of claim 2, further comprising:

the PF entity receives a subscription notification message of the GSM; 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 the PF entity locally saves the mapping relation between the target GID and the new CF service identifier.

4. A method according to any of claims 1-3, wherein the mapping maintained on the GMS functional entity is configured by a GMS operations management maintenance entity.

5. The method of claim 4, further comprising:

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

and the PF entity delivers the group call request to a 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 program stored in the memory and calls other equipment to execute the following steps:

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

if the mapping relation matched with the target GID is not stored locally, corresponding CF configuration information is acquired from a group management service GMS functional entity according to the target GID; the GMS functional entity is used for: maintaining a mapping relation between the group identifier GID and the CF service identifier;

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 obtained CF service identifier.

7. The cluster server of claim 6, wherein the processor, by executing the program stored in the memory and invoking the other device, further performs the steps of:

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

8. The cluster server of claim 7,

the processor executes the program stored in the memory and calls other equipment, and further executes the following steps:

receiving a subscription notification message of the GSM; 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.

9. A cluster server comprising at least a processor and a memory; the processor executes the program stored in the memory and calls other equipment to execute the following steps:

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

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

10. The cluster server of claim 9, wherein the processor, by executing the program stored in the memory and invoking the other device, further performs the steps of:

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 identity.

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 (transmission Critical system) is a whole set of trunking communication system established by 3GPP on top of LTE to solve public security. MCPTT (Session Critical Push To talk) is used as an important component of the MCS system and provides voice trunking communication service.

MCPTT can provide group call function (group call), and the existing MCPTT standard has two requirements for group call implementation:

1. the group call service of a certain group is uniformly implemented on a specific CF (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 calling PF (critical function) entity, and the PF entity addresses a CF entity corresponding to a called group of the group call (i.e., searches for a corresponding CF entity), and hands the group call request to the found CF entity for processing.

But the 3GPP standard does not specify how the PF entity addresses the CF entity 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 purpose, the embodiments of the present invention provide the following technical solutions:

a group call method is based on a cluster server, the cluster server comprises a user management function (PF) entity and a group management service (GSM) function entity, and the GMS function entity maintains a mapping relation between a Group Identifier (GID) and a service Control Function (CF) service identifier;

the method comprises the following steps:

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

if the mapping relation matched with the target GID is not locally stored, 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 obtained CF service identifier.

Optionally, the method further includes: the PF entity subscribes the CF configuration information of the target GID to the GSM so that the GSM informs the PF entity when the CF configuration information of the target GID is changed.

Optionally, the method further includes: the PF entity receives a subscription notification message of the GSM; 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 the PF entity locally saves the mapping relation between the target GID and the new CF service identifier.

Optionally, the mapping relationship maintained on the GMS functional entity is configured by a GMS operation management maintenance entity.

Optionally, the method further includes: the PF entity receives a group call request; the group call request carries the target GID; and the PF entity delivers the group call request to a 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 program stored in the memory and calls other equipment to execute the following steps: receiving a join request; the join request carries a target GID; if the mapping relation matched with the target GID is not stored locally, corresponding CF configuration information is acquired from a group management service GMS functional entity according to the target GID; the GMS functional entity is used for: maintaining a mapping relation between the group identifier GID and the CF service identifier; 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 obtained CF service identifier.

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

Optionally, the processor executes the program stored in the memory and calls other devices, and further executes the following steps: receiving a subscription notification message of the GSM; 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 program stored in the memory and calls other equipment to execute the following steps:

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

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

Optionally, the processor executes the program stored in the memory and calls other devices, and further executes the following steps: 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 identity.

It can be seen that, in the embodiment of the present invention, the GMS functional entity maintains the relationship between the GID and the CF service identifier, and when the PF entity receives the join request carrying the target GID, and the PF obtains the corresponding CF service identifier from the GMS and stores the mapping relationship between the target GID and the CF service identifier without locally storing the corresponding mapping relationship, thereby completing the 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 structure of a PF entity provided in an embodiment of the present invention;

fig. 4 is an exemplary structure of a GMS provided in 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 structure of a PF entity provided by an embodiment of the present invention;

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

fig. 9 is another exemplary flow of a 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 reference and clarity, the terms, abbreviations or abbreviations used hereinafter are summarized as follows:

PF: a partitionationfunction, user management function;

CF: control Function, service control Function;

GMS: a group management server;

GID: GroupId, group identification, a unique identifier used to identify a group;

affiliation request: a request for joining;

3 GPP: 3rd Generation Partnership Project third Generation Partnership Project;

MCPTT: mission Critical Push To Talk, key task Push To Talk;

UE: user Equipment, a User terminal;

OAM: operation Administration and Maintenance;

subscribe Request: a subscription request;

server: a server, an entity;

PSI: public Service Identity, which is actually a URI, can be routed to the corresponding CF.

The group call function may serve the public safety domain, e.g., a patrol traffic police may establish a group, and a calling subscriber in the group may establish a group call to a subscriber belonging to the group.

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

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

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

The PF entity and the CF entity are both function modules defined by 3GPP standards, 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 talk right management of the group calling.

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

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

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

TABLE 1

It should be noted that "N" in table 1 above indicates that the configuration item has no effect, and "Y" indicates that the configuration item has an effect, i.e., the ControllingFunction PSI has no effect on MCPTTUE and is useful for MCPTTServer.

Fig. 3 shows 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, including the maintenance unit 3 and the query unit 4. The maintaining unit 3 is configured to maintain a mapping relationship between the GID and the CF service identifier.

The function of each unit will be further described later in this document in connection with a paging method.

Fig. 5 shows an exemplary flow of the group calling method, including:

s1: the PF entity receives a join request.

The join request is sent by a UE belonging to a certain group. The GID is carried in the join request and may be referred to as a target GID.

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

S2: and if the mapping relation matched with the target GID is not locally stored, 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., the CF configuration information).

The CF configuration information includes a CF service identifier, and the CF service identifier is used to characterize the CF entity.

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

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

Because each group call needs to find the corresponding CF service identifier according to the GID, the PF entity can save the mapping relation locally for searching conveniently. In case of not being locally detected, the corresponding CF configuration information may be acquired to the GMS functional entity.

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

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

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

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

s4: the PF entity subscribes to the GSM for CF configuration information of the target GID.

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

In one example, please refer to fig. 7, the PF entity may further include a subscription unit 5 to execute the above step S4.

Fig. 8 shows the interaction between the PF entity and GSM when the CF configuration information is changed, which may include the following steps:

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

The subscription notification message may specifically include the latest CF configuration information (e.g., a 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 a subscription notification message.

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

S803: the PF locally saves 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.

Therefore, after subscription, when the CF configuration changes, the GSM notifies the PF entity, and the real-time performance of the local configuration relationship of the PF entity is ensured.

It should be noted that, conventionally, the mapping relationship between the GID and the CF service identifier is pre-deployed on the PF entity (instead of GSM). For example, if there are 10 PFs, 10 groups, and 10 CFs in a networking, according to a common practice, 10 CFs corresponding to group IDs need to be configured on each PF. Therefore, the larger the number of groups, the more content needs to be configured on each PF. Although this implementation can meet the basic requirements of addressing, it is complex in configuration and costly to maintain. Once the group service migration needs to be modified, the mapping relationships on all PF entities need to be modified.

In the embodiment of the invention, after the mapping relationship between the GID and the CF service identifier is centrally managed on the GMS, 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 relationship between the GID and the CF service identifier does not need to be separately configured and maintained on each PF entity, so that the configuration complexity and the maintenance cost are greatly reduced.

In addition, the PF entity locally stores the mapping relationship between the target GID and the obtained CF service identifier, so that CF addressing can be conveniently and rapidly carried out. Through subscription, when the CF configuration changes, the GSM informs the PF entity, and the real-time performance of the local configuration relationship of the PF entity is ensured.

Referring to fig. 9 (the bold italic step in fig. 9 is an additional step), the group call method will be described in detail below by taking the target GID as GID1 as an example, which may include the following steps:

s901: the UE initiates an affinity request to request entry into the group GID 1.

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

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

S902: after receiving the affinity Request, the PF entity initiates a Group server PSI Request (Group server PSI Request) to the GMS according to the GID1 to acquire CF configuration information corresponding to the GID 1.

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

S903: the GMS returns a Group ServerPSI Response.

The Group ServerPSI Response carries CF configuration information corresponding to GID 1.

S904: the PF records the mapping relationship of the GID1 and the CF service identifier locally.

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

S905: the PF initiates a Group ServerPSI Subscribe Request to the GMS according to the GID1, and subscribes Group information.

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

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

Step S906 may be executed by the aforementioned maintenance unit 3, or a subscription unit may be added to the GSM to execute step S906.

S907: the UE (or called client) sends a Group Call Request to initiate a GID1 Group Call.

The group call request carries a target GID, namely GID 1.

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 a 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 CF 1.

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

S909: when the CF configuration to which the GID1 belongs is changed, the GSM sends a subscription notification message (Group server psi Notify Request) to the PF entity.

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

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

S910: after receiving the subscription notification message, the PF entity records the mapping relationship of the GID1 to the new CF (CF2) locally.

Step S910 is similar to step S803 described above, and is not described herein again.

S911: after successful processing, the PF entity returns a Group ServerPSI Notify Response to the GMS.

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

S912: the UE sends a Group Call Request, and initiates the GID1 Group Call again.

Step S912 is similar to step S907, and is not described herein.

S913: and the PF entity forwards the group call request to a 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 the GID1 belongs is changed from CF1 to CF2, the PF entity GMS forwards the group call request to CF 2.

Step S913 is similar to step S908, and is not described herein.

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

Fig. 10 shows a schematic diagram of a possible structure of the cluster server (PF entity or GSM entity) in the foregoing embodiment, which includes: a bus, a processor 101, a memory 102, a communication interface 103, an input device 104, and an output device 105. The processor 101, the memory 102, the communication interface 103, the input device 104, and the output device 105 are connected to each other by a bus. Wherein:

a bus may include a path that transfers 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 (NP), a microprocessor, etc., or an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program according to the present invention. But also a Digital Signal Processor (DSP), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components.

The memory 102 stores programs or scripts for executing the technical solution 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 as text (e.g., ASCII) and are interpreted or compiled only when called.

The input device 104 may include means for receiving data and information input by a user, such as a keyboard, mouse, camera, voice input device, 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 any means for using a transceiver or the like to communicate 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, by executing the program stored in the memory and invoking other devices, may perform the following steps:

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

if the mapping relation matched with the target GID is not stored locally, corresponding CF configuration information is acquired from a group management service GMS functional entity according to the target GID; the GMS functional entity is used for: maintaining a mapping relation between the group identifier GID and the CF service identifier;

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 obtained CF service identifier.

For details, please refer to the foregoing description, which is 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 calling other devices:

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

For details, please refer to the foregoing description, which is not repeated herein.

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 calling other devices:

receiving a subscription notification message of the GSM; 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.

For details, please refer to the foregoing description, which is not repeated herein.

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

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

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

For details, please refer to the foregoing description, which is not repeated herein.

In other embodiments of the present invention, the processor in the GSM entity may further perform 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 identity.

For details, please refer to the foregoing description, which is not repeated herein.

The functions of the units shown in fig. 3, 4, and 7 can be realized by the processor 101 executing a program stored in the memory 102 and calling another device.

Those of skill would further appreciate that the various illustrative components and model steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order 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 implementation. A skilled artisan may use different PFs for each particular application to implement the described functionality, but such implementation should not be considered 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. A software module may reside 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.