WO2017132971A1 - 一种组呼业务处理方法及系统、核心网设备 - Google Patents

一种组呼业务处理方法及系统、核心网设备 Download PDF

Info

Publication number
WO2017132971A1
WO2017132971A1 PCT/CN2016/073587 CN2016073587W WO2017132971A1 WO 2017132971 A1 WO2017132971 A1 WO 2017132971A1 CN 2016073587 W CN2016073587 W CN 2016073587W WO 2017132971 A1 WO2017132971 A1 WO 2017132971A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
group
core network
network device
bearer network
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.)
Ceased
Application number
PCT/CN2016/073587
Other languages
English (en)
French (fr)
Inventor
陈钢
尧俊峰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hytera Communications Corp Ltd
Original Assignee
Hytera Communications Corp Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Hytera Communications Corp Ltd filed Critical Hytera Communications Corp Ltd
Priority to PCT/CN2016/073587 priority Critical patent/WO2017132971A1/zh
Publication of WO2017132971A1 publication Critical patent/WO2017132971A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a group call service processing method and system, and a core network device.
  • high-speed data service is one of the fastest-developing cluster services, especially high-speed data services represented by video services, and high-speed data services to the transmission bearer network between the cluster core network and the base station.
  • the pressure is getting bigger and bigger.
  • the method for transmitting data through the transmission bearer network between the cluster core network and the base station is a unicast (point-to-point) transmission mode.
  • the core network replicates the data from the data source and copies one copy for each base station participating in the group call.
  • the group call of the cluster includes the terminal A of the base station 1, the terminal B of the base station 2, and the base station 3.
  • the terminal C has three users, and the core network copies 3 pieces of data for the three base stations participating in the group call.
  • each data is transmitted to each base station participating in the group call through the bearer network, and the base station transmits the data to the terminal. .
  • the total traffic transmitted by the bearer network is the sum of the traffic of all the data of the base station participating in the group call, so that the designed bearer traffic of the bearer network is large, and a large amount of redundant traffic exists during use, which reduces the bearer.
  • the transmission efficiency of the network, in addition, the core network also needs to copy multiple copies of the data, increasing the load on the core network and reducing the capacity and performance of the cluster service.
  • the purpose of the application is to provide a group call service processing method and system, and a core network device, which implements point-to-multipoint multicast transmission with a preset multicast distribution tree, thereby improving the capacity and performance of the cluster service.
  • a group call service processing method based on a trunking communication system is provided.
  • the core network device receives the group call downlink data packet from the data source;
  • the core network device sends the group call downlink data packet to the bearer network, where the bearer network is pre-configured with a multicast distribution tree, where the multicast distribution tree uses the core network device as a multicast source and participates in the multicast group.
  • the base station is a leaf node.
  • the method for setting a multicast distribution tree in advance includes:
  • the core network device When the terminal registers with the core network device for the first time in the multicast group, the core network device triggers the establishment of the multicast distribution tree in the bearer network.
  • the establishment of the multicast distribution tree triggered by the core network device in the bearer network includes:
  • the core network device allocates a bearer network multicast IP address to the multicast group
  • the core network device sends the bearer network multicast IP address to the participating base stations in the multicast group, and triggers the participating base station in the multicast group to send a request for joining the multicast network to the bearer network, and the request for joining the multicast is used for triggering.
  • the bearer network establishes a multicast distribution tree in which the core network device is a multicast source and the participating base stations in the multicast group are leaf nodes.
  • the method further includes: after receiving the terminal deregistration request message, the core network device determines whether the registered terminal is still in the multicast group where the debit terminal is located, and if not, releases the bearer network group of the multicast group where the debit terminal is located.
  • the IP address is broadcasted, and the participating base station in the multicast group is triggered to send an exit multicast message to the bearer network, and the exit multicast message is used to trigger the bearer network to delete the participating base station of the multicast group from the multicast distribution tree.
  • a core network device including:
  • a data receiving unit configured to: after the group call is established, the core network device receives the group call downlink data packet from the data source;
  • a data sending unit configured to send the group call downlink data packet to the bearer network, where the bearer network is pre-configured with a multicast distribution tree, where the multicast distribution tree uses the core network device as a multicast source and a multicast group.
  • the participating base stations are leaf nodes.
  • it also includes:
  • the triggering unit is configured to trigger the establishment of the multicast distribution tree in the bearer network when the terminal registers with the core network device for the first time in the multicast group.
  • the trigger unit includes:
  • a multicast address allocation unit configured to allocate a bearer network multicast IP address to the multicast group
  • a first requesting unit configured to send the bearer network multicast to a participating base station in the multicast group
  • An IP address and the participating base station in the multicast group sends a request to join the multicast network to the bearer network.
  • the request to join the multicast is used to trigger the bearer network to establish the core network device as the multicast source and the participating base station in the multicast group.
  • it also includes:
  • the determining unit after receiving the terminal logout request message, determining whether there is still a registered terminal in the multicast group where the debit terminal is located;
  • the multicast address release unit is configured to release the multicast IP address of the bearer network of the multicast group where the terminal is located when the terminal that does not exist in the group where the terminal is located is deleted;
  • a second requesting unit configured to trigger the participating base station in the multicast group to send an exit multicast message to the bearer network, and the exiting the multicast message is used to trigger the bearer network to delete the participating base station of the multicast group from the multicast distribution tree.
  • a group call service processing system including any of the core network devices, and a bearer network and a participating base station.
  • a core network device comprising a memory and a processor, the memory for storing program code and transmitting the program code to the processor;
  • the processor is configured to execute the group communication service processing method based on the cluster communication system according to the instruction in the program code.
  • the core network device After the initiating terminal initiates a group call request to the core network device, the core network device receives the group call downlink data packet from the data source, and sends the group call downlink data packet to the bearer network, and the core network device is preset in the bearer network.
  • the participating base station is a multicast distribution tree of the leaf node, so that the downlink data packet will be transmitted from the core network device to each participating base station along the multicast distribution tree, and the participating base station sends the terminal to the participating group call, thereby, the core
  • the network device only needs to send one data, which realizes the point-to-multipoint multicast transmission mode from the core network device to the group call terminal, reduces the load of the core network, and the redundant traffic of the bearer network, and reduces the transmission.
  • the delay increases the capacity and performance of the cluster service as a whole.
  • FIG. 1 is a flowchart of a group call service processing method according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a method for establishing a multicast distribution tree preset in a group call service processing method according to an embodiment of the present invention
  • FIG. 3 is a flowchart of a method for deleting a multicast distribution tree in a group call service processing method according to an embodiment of the present invention
  • FIG. 4 is a signaling flowchart of a method for processing a group call service of an LTE cluster system according to an embodiment of the present invention
  • FIG. 5 is a schematic diagram of an IP packet protocol stack in an LTE cluster system group call service processing method according to an embodiment of the present invention
  • FIG. 6 is a signaling flowchart of a method for deleting a multicast distribution tree in a method for processing a group call service of an LTE cluster system according to an embodiment of the present invention
  • FIG. 7 is a schematic structural diagram of a core network device according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram showing the hardware structure of a core network device according to an embodiment of the present invention.
  • FIG. 1 is a flowchart showing a group call service processing method based on a trunking communication system according to an embodiment of the present invention.
  • the method is based on a trunking communication system, and a multicast distribution tree is pre-configured in the bearer network.
  • the multicast distribution tree uses a core network device as a multicast source and a participating base station in a multicast group as a leaf node.
  • the group call service processing method in the embodiment of the present invention is applied to a trunking communication system, for example, PDT (Professional Digital Trunking) communication system, LTE (Long Term Evolution) communication system
  • the bearer network is a data transmission network in a trunking communication system
  • the trunking communication system includes a core network, a bearer network, and a base station, and different
  • the core network integrates different core network devices.
  • the core network includes eMME (enhanced Home Management Entity), TCF (Trunking Control Function), eHSS ( Enhanced Home Subscriber Server, Enhanced Home Subscriber Server, XGW (X Gateway, Cluster Gateway) and TMF (Trunking Media Function).
  • the core network device may be a switch, and the switch implements the functions of the above five network elements.
  • the bearer network is a physical transport network between the core network and the base station.
  • the bearer network pre-sets a multicast distribution tree in which the core network device is the multicast source and the participating base stations in the group are the leaf nodes, so that after the group call is established, the downlink data packet will be along
  • the multicast distribution tree is transmitted by the core network device to each participating base station, and is sent by the participating base station to the terminal participating in the group call, so that the core network device only needs to send one data, and the point from the core network device to the group call terminal is realized.
  • the multi-point multicast transmission mode reduces the load on the core network equipment and the redundant traffic of the bearer network, and reduces the transmission delay, thereby improving the capacity and performance of the cluster service as a whole.
  • the bearer network multicast IP address of the multicast group where the terminal is located is preset in the core network device and the participating base station, and the multicast distribution tree may be preset in the bearer network, and the bearer network is The multicast IP address is set in the core network device and the participating base station. In this way, the bearer network multicast IP address is set in the core network and the base station side in advance, and the bearer network can use the multicast IP address to implement multicast of the downlink data packet.
  • each terminal in the multicast group performs a registration request before performing the clustering service.
  • the core network device when the terminal first registers with the core network device in the multicast group, the core network device The establishment of the multicast distribution tree is triggered in the bearer network.
  • the core network device can trigger the establishment of the multicast distribution tree after receiving the terminal registration completion message in the multicast group for the first time.
  • the terminal After the core network receives the registration completion message, the terminal is registered under a certain base station. For convenience of description and differentiation, the terminal is recorded as a registered terminal, and the base station registered by the terminal is recorded as a participating base station, and at this time, the multicast distribution is triggered.
  • the tree is set to ensure that the multicast distribution tree can be effectively set up before the group call request. In a specific embodiment, referring to FIG. 2, the following steps may be adopted. Set the multicast distribution tree in advance.
  • step S101 the core network device allocates a bearer network multicast IP address to the multicast group.
  • step S102 the core network device sends the bearer network multicast IP address to the participating base stations in the multicast group, and triggers the participating base station in the multicast group to send a request for joining the multicast to the bearer network, and joins the multicast.
  • the request is used to trigger the bearer network to establish a multicast distribution tree in which the core network device is a multicast source and the participating base stations in the multicast group are leaf nodes.
  • the core network device determines whether the multicast group in which the registered terminal is located has been assigned a multicast IP address of the bearer network, and if not, assigns a multicast IP address of the bearer network to the multicast group. And sending the multicast IP address of the bearer network of the multicast group to the participating base stations in the multicast group where the registered terminal is not joined, and triggering the participating base station that does not join the multicast to send the request for joining the multicast network to the bearer network.
  • a terminal in a multicast group is a contracting member in a multicast group.
  • the participating base station is a base station registered by a terminal in the multicast group.
  • it can be a signing member of a multicast group.
  • It can also be a contracting member of multiple multicast groups, that is, a certain terminal can be in different multicast groups respectively.
  • UE1 is a contracting member of group 1 and group 2, respectively.
  • the terminal includes UE1 and UE3, and the group 2 includes the UE1 and the UE4.
  • the multicast group where the UE1 is located is the group 1 and the group 2.
  • the terminal after a terminal sends a registration completion message to the core network device, the terminal is a registered terminal, the registration terminal is registered under the participating base station, and the participating base station transmits data to the base station, and then the core network device first determines Whether the multicast group in which the terminal is located has been assigned a multicast IP address of the bearer network. If not, the multicast group address of the bearer network is allocated to the multicast group where the registered terminal is located. For the registered terminals that belong to different multicast groups. The bearer network multicast IP address is allocated to each multicast group to which the registered terminal belongs, and then the core network device sends the bearer network multicast IP address to the participating base stations in each multicast group.
  • the participating base stations have base stations that have not joined the multicast group, the participating base stations that have not joined the multicast are sent to the bearer network to send an invitation to join the multicast.
  • the base station that does not join the multicast can be sent to the multicast station to be added to the multicast.
  • the base station may send a packet requesting to join the multicast to the upper-level router in the bearer network by using the group member management protocol, and indicate to the upper-level router in the bearer network to listen to the multicast IP address, and multicast.
  • the group member management protocol may be, for example, the IGMPv3 protocol.
  • the bearer network may establish a multicast distribution tree in which the core network device is a multicast source and the participating base station is a leaf node, and the multicast routing protocol may be, for example, PIM-SMM protocol.
  • the establishment of the multicast distribution tree is triggered by the registration completion message of the registered terminal, and after the terminal is registered, the corresponding multicast distribution is established for the participating base stations in all the groups in which the registered terminal is located.
  • the tree needs to be registered before the terminal performs the cluster service. Therefore, before the group call is initiated, the participating base stations of all the registered terminals establish a multicast distribution tree in the bearer network.
  • the method for performing group call service processing includes:
  • step S01 after the group call is established, the core network device receives the group call downlink data packet from the data source.
  • the terminal initiates a group call service request to the core network device.
  • the terminal that initiates the group call request is recorded as the initiating terminal, and the initiating terminal may be any signing member in the multicast group.
  • the network device After receiving the group call request from the initiating terminal, the network device confirms the group call request, and establishes a group call with the group.
  • the core network device After the group call is established, the core network device first receives the group call downlink data packet from the data source, and the data The data transmission between the source and the core network device is a point-to-point transmission.
  • step S02 the core network device sends the group call downlink data packet to the bearer network, and the downlink data packet is transmitted to the participating base station along the multicast distribution tree.
  • the multicast distribution tree is pre-configured in the bearer network.
  • the multicast source of the multicast distribution tree is the core network device, and the leaf node is the participating base station. After the core network device sends the group call downlink data packet to the bearer network, the bearer is carried. The network will be transmitted along the multicast distribution tree to the participating base stations, and the participating base stations will send them to the corresponding terminals, thereby implementing a point-to-multipoint multicast transmission mode from the core network device to the terminal.
  • the bearer network multicast IP address is preset in the core network device and the participating base station, and the core network device carries the group bearer downlink IP packet to the bearer network and carries the bearer network multicast IP address of the group. In this way, the bearer network uses the multicast IP address to implement multicast.
  • the multicast does not immediately exit the multicast.
  • the participating base station continues to listen to the data of the group.
  • the multicast distribution tree in the bearer network remains. After all the terminals in the group are deregistered, the base station exits the multicast.
  • the bearer network is triggered to delete the participating base stations of the multicast group in the multicast distribution tree.
  • step S201 after receiving the terminal deregistration request message, the core network device determines whether there is still a registered terminal in the multicast group where the debit terminal is located, and if not, releases the group where the debit terminal is located.
  • the multicast IP address of the bearer network of the broadcast group, and the participating base stations in the multicast group are sent to the bearer network to send out the multicast request, and the exit multicast message is used to trigger the bearer network to join the participating base stations of the group from the multicast distribution tree. delete.
  • the step of exiting the multicast is triggered by all the terminals in the multicast group completing the logout.
  • the core network device receives the terminal logout request message, that is, the terminal is in any multicast group to which the terminal belongs.
  • the CCP withdraws from the cluster service, and the terminal sends a logout request to the core network device.
  • the terminal is recorded as a logout terminal, and then the core network device determines whether there is still a registration in the multicast group where the logout terminal is located. The terminal does not exit the multicast if there is a registered terminal.
  • the bearer network group of the group in which the terminal is located is released.
  • the IP address is broadcasted, and the participating base station is notified to quit the multicast, and the participating base station in the multicast group is sent to the bearer network to send an exit multicast request.
  • the base station that sends the multicast request may be sent to the base station that does not exit the multicast.
  • the bearer network After receiving the multicast request, the bearer network deletes the participating base station of the multicast group from the multicast distribution tree. Specifically, after receiving the request for exiting the multicast from the participating base station, the bearer network may delete the participating base station that sends the exit multicast request from the multicast distribution tree by using a multicast routing protocol, where the multicast routing protocol may be, for example, PIM. - SMM protocol, in this way, the multicast distribution tree of the multicast group is deleted.
  • the multicast routing protocol may be, for example, PIM. - SMM protocol
  • the core network of the LTE trunking communication system includes an eMME (Enhanced Home Management Entity), a TCF (Trunking Control Function), and an eHSS (enhanced Home Subscriber Server).
  • the five network elements are the enhanced home subscriber server, the xGW (X Gateway, the cluster gateway), and the TMF (Trunking Media Function).
  • the multicast distribution tree is preset in the bearer network.
  • the step of pre-setting the multicast distribution tree in the bearer network includes:
  • the terminal UE completes the cluster registration process and sends a registration completion message to the eMME, to notify the eMME terminal that the registration is completed.
  • the eMME determines whether the bearer network multicast IP address of the multicast group where the UE is located has been allocated.
  • the eMME sends a bearer network multicast IP address allocation request to the xGW, and the sent request carries the multicast group identifier.
  • the xGW After receiving the multicast IP address allocation request of the bearer network, the xGW allocates a bearer network multicast IP address to the multicast group.
  • the xGW returns a bearer network multicast IP address allocation response message to the eMME, where the message carries the bearer network multicast IP address.
  • the eMME checks whether the participating base stations in the multicast group join the multicast, and if not, sends a message for establishing a multicast request to the participating base stations, where the message carries the bearer network multicast IP address and the group identifier.
  • the participating base station returns a response to establish a multicast request to the eMME.
  • the participating base station After receiving the message for establishing the multicast request, the participating base station sends the join multicast message through the IGMP protocol, indicates to the upper-layer router in the bearer network, listens to the multicast of the multicast IP address, and returns a multicast request to the eMME. the response to.
  • the bearer network uses the PIM-SSM protocol to establish a multicast distribution tree with the xGW as the multicast source and the participating base station as the leaf node.
  • the multicast distribution tree of all participating base stations of the multicast group is pre-established.
  • any terminal initiates a group call, and the core network device establishes a group call with the multicast group where the originating terminal is located.
  • the core network device receives the group call downlink data packet from the data source, where the downlink data packet is unicast data. Then, the core network device sends the group call downlink data packet to the bearer network, and the downlink number The packet is transmitted to the participating base station along the multicast distribution tree. At this time, the downlink data packet is multicast data, and the data packet is transmitted to each participating base station according to the multicast distribution tree, and finally transmitted to the terminal through the base station.
  • the group call data packet protocol stack, the gateway xGW of the core network, and the IP packets on both sides of the base station use the bearer network multicast IP address in the core network device.
  • the multicast IP address of the bearer network is carried, and the bearer network uses the multicast IP address of the bearer network to implement multicast.
  • the outermost IP header of the downlink data packet is used. The address is set to the bearer network multicast IP address, and then the group call downlink data packet is sent to the bearer network as the source of the multicast distribution.
  • the core network device does not trigger the base station to exit the multicast, and the base station continues to listen to the group of data, and the corresponding multicast distribution tree in the bearer network still exists.
  • the TCF after receiving the group call release request, notifies the eMME to end the group call, and the eMME sends a group call release indication to the terminal, and the group call ends, but the base station does not trigger the base station to exit the multicast, and the base station continues to monitor.
  • the data of the group, the corresponding multicast distribution tree in the bearer network still exists.
  • the base station Only when there is no terminal with the group under the base station, the base station exits the multicast and sends the exit multicast message to the bearer network.
  • the terminal sends a logout request to the eMME to notify the eMME to exit the cluster service.
  • the eMME sends a message requesting cancellation to the TCF.
  • the eMME returns a message accepting the logout request to the terminal.
  • the eMME checks whether there is a registered terminal in the multicast group, and if not, sends a request for releasing the multicast IP address of the bearer network of the multicast group to the xGW, where the request carries the group identifier.
  • the xGW returns a release request response to the eMME.
  • the eMME sends an exit multicast group request to the base station.
  • the base station After receiving the exit multicast request, the base station sends an exit multicast message through the IGMP protocol, and indicates to the upper-level router in the bearer network that the base station in the multicast group wants to exit the multicast group.
  • the bearer network updates the multicast distribution tree of the bearer network, and deletes the subscription base station of the terminal in the multicast group from the multicast distribution tree. In this way, after all the terminals in the multicast group are not registered, the base station that is contracted with the terminal exits the multicast.
  • the core network device is a switch (MSC, Mobile).
  • the switch determines whether the multicast group in which the registered terminal is located has allocated the bearer network multicast IP address.
  • the bearer network assigns a multicast IP address of the bearer network to the multicast group, and send the multicast IP address of the bearer network of the multicast group to the participating base stations in the group where the registered terminal is located, and trigger the non-joining multicast.
  • the participating base station sends a request for joining the multicast to the bearer network.
  • the bearer network After receiving the request for joining the multicast, the bearer network establishes a multicast distribution tree in which the switch is the multicast source and the participating base station is the leaf node.
  • the switch determines whether there is still a registered terminal in the multicast group where the terminal is located. If not, the bearer network of the multicast group where the terminal is located is released. The multicast IP address is triggered, and the participating base stations in the multicast group are sent to the bearer network to send out the multicast message. After receiving the exit multicast message, the bearer network deletes the participating base station of the multicast group from the multicast distribution tree. .
  • the present invention further provides a core network device, as shown in FIG. 7, including:
  • the data receiving unit 710 is configured to: after establishing the group call, the core network device receives the group call downlink data packet from the data source;
  • the data packet sending unit 720 is configured to send the group call downlink data packet to the bearer network, where the bearer network is pre-configured with a multicast distribution tree, where the multicast distribution tree uses the core network device as a multicast source and a multicast group.
  • the participating base stations are leaf nodes.
  • the triggering unit 730 is configured to trigger establishment of the multicast distribution tree in the bearer network when the terminal registers with the core network device for the first time in the multicast group.
  • the trigger unit 730 includes:
  • the multicast address allocating unit 7301 is configured to allocate a bearer network multicast IP address to the multicast group.
  • the first requesting unit 7302 is configured to send the bearer network multicast IP address to the participating base stations in the multicast group, and trigger the participating base station in the multicast group to send a request for joining the multicast network to the bearer network.
  • the request to join the multicast is used to trigger the bearer network to establish a multicast distribution tree in which the core network device is the multicast source and the participating base stations in the multicast group are the leaf nodes.
  • the determining unit after receiving the terminal logout request message, determining whether there is still a registered terminal in the multicast group where the debit terminal is located;
  • the multicast address release unit is configured to release the multicast IP address of the bearer network of the multicast group where the terminal is located when the terminal that does not exist in the group where the terminal is located is deleted;
  • the second requesting unit is configured to trigger the participating base station in the multicast to send an exit multicast message to the bearer network, and the exiting multicast message is used to trigger the bearer network to delete the participating base station of the group from the multicast distribution tree.
  • the present invention also provides a corresponding group call service processing system, including the above core network device, and a bearer network and a base station.
  • the core network device includes a data receiving unit, and after the group call is established, the core network device receives the group call downlink data packet from the data source, and the data sending unit is configured to use the group call downlink data packet.
  • the packet is sent to the bearer network.
  • the bearer network is pre-configured with a multicast distribution tree.
  • the multicast distribution tree uses the core network device as the multicast source and the participating base stations in the multicast group as the leaf nodes.
  • the core network device further includes a triggering unit, configured to trigger establishment of the multicast distribution tree in the bearer network when the terminal first registers with the core network device in the multicast group.
  • the trigger unit includes:
  • a multicast address allocation unit configured to allocate a bearer network multicast IP address to the multicast group
  • the first requesting unit is configured to send the bearer network multicast IP address to the participating base stations in the multicast group, and trigger the participating base station in the multicast group to send a request for joining the multicast to the bearer network, and join the multicast
  • the request is used to trigger the bearer network to establish a multicast distribution tree in which the core network device is a multicast source and the participating base stations in the multicast group are leaf nodes.
  • the core network device further includes: a determining unit, configured to: after receiving the terminal logout request message, determine whether there is still a registered terminal in the multicast group where the debit terminal is located; and the multicast address release unit is configured to cancel the group where the terminal is located When there is no registered terminal, the multicast IP address of the bearer network of the multicast group where the terminal is located is released; the second request unit is configured to trigger the parameter in the multicast. And the base station sends an exit multicast message to the bearer network, and the exit multicast message is used to trigger the bearer network to delete the participating base stations of the group from the multicast distribution tree.
  • a multicast distribution tree in which the core network device is the source and the participating base station is the leaf node is pre-established in the bearer network.
  • the bearer network is further configured to: after receiving the information for establishing the multicast distribution tree, establish a multicast distribution tree with the core network device as the source and the participating base station as the leaf node.
  • the bearer network is further configured to delete the participating base stations in the multicast group from the multicast distribution tree after receiving the exit multicast message.
  • the processing system is based on a LTE cluster system, and the core network device includes network elements through eMME, xGW, and the like. In other embodiments, the processing system is based on a PDT trunking communication system and the core network device is a switch.
  • the present invention also provides a core network device 800, including a memory 802 and a processor 801 for storing program code 805 and transmitting the program code 805 to the processor. 801;
  • the processor 801 is configured to perform the following steps according to the instructions in the program code 805:
  • the group call downlink data packet from the data source is received;
  • the group call downlink data packet is sent to the bearer network, and the bearer network is pre-configured with a multicast distribution tree.
  • the multicast distribution tree uses the core network device as the multicast source and the participating base stations in the multicast group as the leaf node.
  • the following steps are performed: when the terminal registers with the core network device for the first time in the multicast group, the establishment of the multicast distribution tree in the bearer network is triggered.
  • the triggering establishment of the multicast distribution tree in the bearer network includes:
  • the multicast group in which the terminal is located is still stored. If the registered terminal does not exist, the multicast IP address of the bearer network of the multicast group where the terminal is located is released, and the participating base station in the multicast is triggered to send the exit multicast message to the bearer network, and the multicast message is used for exiting the multicast message.
  • the trigger bearer network deletes the participating base stations of the group from the multicast distribution tree.
  • the processor 801 is connected to the memory 802 through a bus 803.
  • the core network device 800 has a communication interface 804.
  • the bus 803 may be an industry standard architecture (Industry Standard Architecture, referred to as ISA) bus or Peripheral Component (PCI) bus or Extended Industry Standard Architecture (EISA) bus.
  • ISA Industry Standard Architecture
  • PCI Peripheral Component
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into one or more of an address bus, a data bus, and a control bus. For ease of representation, only one thick line is shown in the figure, but it does not mean that there is only one bus or one type of bus.
  • the memory 802 is configured to store executable program code, the program code including computer operating instructions.
  • the memory 802 can include a high speed RAM (Ramdom Access Memory) memory.
  • the memory 802 may further include a non-volatile memory.
  • the memory 802 can include a disk storage.
  • the processor 801 may be a central processing unit (CPU), or the processor 801 may be an application specific integrated circuit (ASIC), or the processor 801 may Is one or more integrated circuits that are configured to implement embodiments of the present invention.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • the core network device in the embodiment of the present invention may be, for example, a core network element, a switch, or the like.
  • the invention may be described in the general context of computer-executable instructions executed by a computer, such as a program module.
  • program modules include routines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular abstract data types.
  • the invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are connected through a communication network.
  • program modules can be located in both local and remote computer storage media including storage devices.
  • the device embodiment since it basically corresponds to the method embodiment, reference may be made to the partial description of the method embodiment.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located One Places, or they can be distributed to multiple network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without any creative effort.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种基于集群通信系统的组呼业务处理方法，该方法包括：建立组呼后，核心网设备接收来自数据源的组呼下行数据包；所述核心网设备将组呼下行数据包发送至承载网，所述承载网中预先设置有组播分发树，所述组播分发树以核心网设备为组播源、组播组中的参与基站为叶子节点。该方法中，核心网设备只需发送一份数据，便实现了由核心网设备至组呼终端的点到多点的组播传输方式，减少了核心网设备的负荷，以及承载网的冗余流量，同时减少了传输时延，从整体上提高了集群业务的容量和性能。

Description

一种组呼业务处理方法及系统、核心网设备 技术领域
本发明涉及通信技术领域，特别是涉及一种组呼业务处理方法及系统、核心网设备。
背景技术
在目前的集群通信系统中，高速数据业务是发展最为快速的集群业务之一，尤其是以视频业务为代表的高速数据业务，而高速数据业务给集群核心网与基站之间的传输承载网带来的压力也越来越大。
在现有技术中，集群核心网与基站间通过传输承载网传输数据的方式为单播(点到点)传输方式，具体的，参考图1所示，在向核心网发送组呼请求之后，核心网将来自数据源的数据进行复制，为每个参与组呼的基站复制一份，在该图示中，集群的组呼包含了基站1的终端A、基站2的终端B和基站3下的终端C共三个用户，则，核心网为参与组呼的三个基站复制3份数据，进而，通过承载网将每份数据传送至参与组呼的各个基站，基站再将数据传输给终端。
然而，在这种传输方式中，承载网传输的总流量为参与组呼的基站所有数据的流量的总和，使得承载网的设计承载流量较大，使用时存在大量的冗余流量，降低了承载网的传输效率，此外，核心网还需要将数据进行多份复制，增加了核心网的负荷，降低了集群业务的容量和性能。
发明内容
本申请的目的是提供一种组呼业务处理方法及系统、核心网设备，以预先设定的组播分发树实现点到多点的组播传输，提高集群业务的容量和性能。
在本申请第一方面，提供了一种基于集群通信系统的组呼业务处理方法，
包括：
建立组呼后，核心网设备接收来自数据源的组呼下行数据包；
所述核心网设备将组呼下行数据包发送至承载网，所述承载网中预先设置有组播分发树，所述组播分发树以核心网设备为组播源、组播组中的参与基站为叶子节点。
可选的，预先设置组播分发树的方法包括：
当组播组中首次有终端向核心网设备注册时，由核心网设备触发组播分发树在承载网中的建立。
可选的，由核心网设备触发组播分发树在承载网中的建立包括：
核心网设备为所述组播组分配承载网组播IP地址；
核心网设备向所述组播组中的参与基站发送所述承载网组播IP地址，并触发组播组中的参与基站向承载网发送加入组播的请求，加入组播的请求用于触发承载网建立起以核心网设备为组播源、组播组中的参与基站为叶子节点的组播分发树。
可选的，还包括：核心网设备接收到终端注销请求消息后，判断注销终端所在的组播组中是否还存在注册的终端，若不存在，则释放注销终端所在组播组的承载网组播IP地址，并触发所述组播组中的参与基站向承载网发送退出组播消息，退出组播消息用于触发承载网将该组播组的参与基站从组播分发树中删除。
在本申请第二方面，提出了一种核心网设备，包括：
数据接收单元，用于建立组呼后，核心网设备接收来自数据源的组呼下行数据包；
数据发送单元，用于将组呼下行数据包发送至承载网，所述承载网中预先设置有组播分发树，所述组播分发树以核心网设备为组播源、组播组中的参与基站为叶子节点。
可选的，还包括：
触发单元，用于当组播组中首次有终端向核心网设备注册时，触发组播分发树在承载网中的建立。
可选的，触发单元包括：
组播地址分配单元，用于为所述组播组分配承载网组播IP地址；
第一请求单元，用于向所述组播组中的参与基站发送所述承载网组播 IP地址，并触发组播组中的参与基站向承载网发送加入组播的请求，加入组播的请求用于触发承载网建立起以核心网设备为组播源、组播组中的参与基站为叶子节点的组播分发树。
可选的，还包括：
判断单元，用于接收到终端注销请求消息后，判断注销终端所在的组播组中是否还存在注册的终端；
组播地址释放单元，用于注销终端所在组中不存在注册的终端时，释放注销终端所在组播组的承载网组播IP地址；
第二请求单元，用于触发所述组播组中的参与基站向承载网发送退出组播消息，退出组播消息用于触发承载网将该组播组的参与基站从组播分发树中删除。
在本申请第三方面，提出了一种组呼业务处理系统，包括上述任一的核心网设备，以及承载网和参与基站。
在本申请的第四方面，提出了一种核心网设备，包括存储器和处理器，所述存储器用于存储程序代码，并将所述程序代码传输给所述处理器；
所述处理器用于根据所述程序代码中的指令，执行上述任一的基于集群通信系统的组呼业务处理方法。
与现有技术相比，本申请提供的技术方案具有以下有益效果：
在发起终端向核心网设备发起组呼请求之后，核心网设备接收来自数据源的组呼下行数据包，将该组呼下行数据包发送至承载网，而承载网中预先设置有以核心网设备为源头、参与基站为叶子节点的组播分发树，这样，下行数据包将沿着组播分发树由核心网设备传送至各参与基站，由参与基站发送至参与组呼的终端，从而，核心网设备只需发送一份数据，便实现了由核心网设备至组呼终端的点到多点的组播传输方式，减少了核心网的负荷，以及承载网的冗余流量，同时减少了传输时延，从整体上提高了集群业务的容量和性能。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面 描述中的附图仅仅是本发明的实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据提供的附图获得其他的附图。
图1示出了根据本发明实施例的组呼业务处理方法的流程图；
图2示出了根据本发明实施例的组呼业务处理方法中预先设定的组播分发树的建立方法的流程图；
图3示出了根据本发明实施例的组呼业务处理方法中组播分发树删除方法的流程图；
图4示出了根据本发明实施例的LTE集群系统组呼业务处理方法的信令流程图；
图5示出了根据本发明实施例的LTE集群系统组呼业务处理方法中IP包协议栈的示意图；
图6示出了根据本发明实施例的LTE集群系统组呼业务处理方法中组播分发树删除方法的信令流程图；
图7示出了根据本发明实施例的核心网设备的结构示意图；
图8示出了根据本发明实施例的核心网设备的硬件结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本发明方案，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
参考图1所示，图1示出了根据本发明实施例的基于集群通信系统的组呼业务处理方法的流程图。该方法基于集群通信系统，承载网中预先设置有组播分发树，所述组播分发树以核心网设备为组播源、组播组中的参与基站为叶子节点。
在本发明实施例的组呼业务处理方法，应用于集群通信系统，例如 PDT(Professional Digital Trunking，专业数字集群)通信系统、LTE(Long Term Evolution，长期演进)通信系统，承载网为集群通信系统中的数据传输网络，集群通信系统包括核心网、承载网和基站，不同的集群通信系统中，核心网集成不同的核心网设备，如LTE中，核心网包括eMME(enhanced Home Management Entity，增强型移动管理实体)、TCF(Trunking Control Function，集群控制功能模块)、eHSS(enhanced Home Subscriber Server，增强型归属用户服务器)、xGW(X Gateway，集群网关)和TMF(Trunking Media Function，集群媒体功能模块)这五个网元。PDT集群系统中，核心网设备具体可以是交换机，由交换机实现上述五种网元的功能。
承载网为核心网到基站之间的物理传输网络。在终端发起组呼请求之前，承载网中预先设置以核心网设备为组播源、组中的参与基站为叶子节点的组播分发树，这样，在建立组呼之后，下行数据包将沿着组播分发树由核心网设备传送至各参与基站，由参与基站发送至参与组呼的终端，从而，核心网设备只需发送一份数据，便实现了由核心网设备至组呼终端的点到多点的组播传输方式，减少了核心网设备的负荷，以及承载网的冗余流量，同时减少了传输时延，从整体上提高了集群业务的容量和性能。
此外，在本发明的实施例中，终端所在组播组的承载网组播IP地址预先设置在核心网设备和参与基站中，可以在承载网中预先设置组播分发树的同时，将承载网组播IP地址设置在核心网设备和参与基站中，这样，预先在核心网和基站侧都设置了承载网组播IP地址，承载网可以使用该组播IP地址实现下行数据包的组播。
对于集群通信系统，组播组中的每个终端在进行集群业务之前，都会进行注册请求，在本发明实施例中，当组播组中首次有终端向核心网设备注册时，由核心网设备触发组播分发树在承载网中的建立，具体的，可以在核心网设备首次收到组播组中终端注册完成消息后，来触发组播分发树的建立。在核心网收到注册完成消息之后，该终端登记在某个基站下，为了便于描述和区分，此终端记做已注册终端，此终端登记的基站记做参与基站，此时，触发组播分发树的设置，确保在组呼请求之前能够有效地设置好组播分发树。在具体的实施例中，参考图2所示，可以采用如下步骤 预先设置组播分发树。
在步骤S101，核心网设备为所述组播组分配承载网组播IP地址。
在步骤S102，核心网设备向所述组播组中的参与基站发送所述承载网组播IP地址，并触发组播组中的参与基站向承载网发送加入组播的请求，加入组播的请求用于触发承载网建立起以核心网设备为组播源、组播组中的参与基站为叶子节点的组播分发树。
具体的，核心网设备接收到终端的注册完成消息后，判断已注册终端所在的组播组是否已分配承载网组播IP地址，若没有，则为该组播组分配承载网组播IP地址，并向已注册终端所在的组播组中未加入组播的参与基站发送该组播组的承载网组播IP地址，并触发未加入组播的参与基站向承载网发送加入组播的请求。
在集群通信系统中，组播组中的终端即组播组内的签约成员，参与基站是组播组中的终端所登记的基站，对于同一个终端，可以是某个组播组的签约成员，也可以是多个组播组的签约成员，也就是说，某终端可以分别在不同的组播组中，例如，在一个实施例中，UE1分别为组1和组2的签约成员，组1中包含终端UE1-UE3，组2中包含终端UE1和UE4，UE1所在的组播组为组1和组2。
在本实施例中，在一个终端向核心网设备发送注册完成消息之后，该终端为已注册终端，该注册终端登记在参与基站下，由参与基站向其传送数据，而后，核心网设备先判断该终端所在的组播组是否已经分配承载网组播IP地址，若没有，则为该已注册终端所在的组播组分配承载网组播IP地址，对于分属于不同组播组的已注册终端，则为该已注册终端所属的每个组播组都分配承载网组播IP地址，之后，核心网设备将承载网组播IP地址发送到每个组播组中的参与基站。若这些参与基站中存在尚未加入其组播组的基站，则触发未加入组播的参与基站向承载网发送加入组播的邀请，触发时可以向未加入组播的基站发送要求其加入组播的请求，基站接收到该请求之后，可以使用组成员管理协议向承载网中的上级路由器发送请求加入组播的报文，向承载网中的上级路由器表明要监听该组播IP地址，组播组成员管理协议例如可以为IGMPv3协议。
承载网在接收到来自参与基站的加入组播的请求之后，可以通过组播路由协议建立起核心网设备为组播源、参与基站为叶子节点的组播分发树，组播路由协议例如可以为PIM-SMM协议。
在该方法中，以已注册终端的注册完成消息触发组播分发树的建立，在该终端注册完毕之后，为该已注册终端所在的所有组中的参与基站都建立起了相应的组播分发树，由于终端在进行集群业务之前都需要注册，这样，在发起组呼之前，为所有的注册的终端的参与基站都在承载网中建立起了组播分发树。基于该组播分发树，进行组呼业务处理的方法包括：
步骤S01，建立组呼后，核心网设备接收来自数据源的组呼下行数据包。
在本发明的实施例中终端为向核心网设备发起组呼业务请求，为了便于描述该发起组呼请求的终端记做发起终端，发起终端可以为组播组中的任意签约成员，该在核心网设备接收到发起终端的组呼请求之后，核心网设备确认此次组呼请求，与该组建立组呼，建立组呼之后，核心网设备首先接收来自数据源的组呼下行数据包，数据源与核心网设备之间的数据传输为点对点的传输。
在步骤S02，核心网设备将组呼下行数据包发送至承载网，下行数据包沿组播分发树传送至参与基站。
由于在承载网中预先设置有组播分发树，组播分发树的组播源为核心网设备，叶子节点为参与基站，在核心网设备将组呼下行数据包发送至承载网后，在承载网中将沿组播分发树传送至参与基站，由参与基站发送至相应的终端，从而实现核心网设备到终端的点到多的组播传输方式。
在本发明的实施例中，在核心网设备以及参与基站中预先设置了承载网组播IP地址，核心网设备将组呼下行数据包发送至承载网时携带该组的承载网组播IP地址，这样，承载网使用该组播IP地址实现组播。
在组呼结束后，并不马上退出组播，参与基站继续监听该组的数据，承载网中的组播分发树仍然保留，直到组中的所有终端都注销注册之后，基站退出组播，并触发承载网删除组播分发树中该组播组的参与基站。
参考图3所示，具体的，在步骤S201，核心网设备接收到终端注销请求消息后，判断注销终端所在的组播组中是否还存在注册的终端，若不存在，则释放注销终端所在组播组的承载网组播IP地址，并触发该组播组中的参与基站向承载网发送退出组播请求，退出组播消息用于触发承载网将该组的参与基站从组播分发树中删除。
在本发明实施例中，通过组播组中所有终端完成注销来触发退出组播的步骤，当核心网设备收到终端注销请求消息后，也就是说，该终端在其任何所属的组播组中将退出集群业务，终端向核心网设备发送注销请求，为了方便描述和与其他终端区别，该终端记做注销终端，而后，核心网设备判断该注销终端所在的组播组中是否还存在注册的终端，如果存在注册的终端，则不进行退出组播，若组播组中不存在注册的终端，即该组播组中的所有终端都已注销，则释放注销终端所在组的承载网组播IP地址，并通知参与基站退出组播，触发该组播组中的参与基站向承载网发送退出组播请求，触发时可以向未退出组播的基站发送要求其退出组播的请求，可以通过使用组成员管理协议向承载网中的上级路由器发送退出组播的报文，向承载网中的上级路由器表明要退出该组播IP地址，组播组成员管理协议例如可以为IGMPv3协议。
承载网接收到退出组播请求后，将该组播组的参与基站从组播分发树中删除。具体的，承载网在接收到来自参与基站的退出组播的请求之后，可以通过组播路由协议将发送退出组播请求的参与基站从组播分发树中删除，组播路由协议例如可以为PIM-SMM协议，这样，就将该组播组的组播分发树删除了。
以上对本发明实施例的基于集群通信系统的组呼业务处理方法进行了详细的描述，为了更好的理解本发明实施例的技术方案，以下将对基于LTE宽带集群通信系统的组呼业务处理方法的具体实施例进行详细的描述。
参考图4所示，在LTE集群通信系统的核心网包括eMME(enhanced Home Management Entity，增强型移动管理实体)、TCF(Trunking Control Function，集群控制功能模块)、eHSS(enhanced Home Subscriber Server， 增强型归属用户服务器)、xGW(X Gateway，集群网关)和TMF(Trunking Media Function，集群媒体功能模块)这五个网元。
在终端进行组呼之前，在承载网中预先设置有组播分发树，具体的，在该实施例中，在承载网中预先设置组播分发树的步骤包括：
S301，终端UE完成集群注册过程向eMME发送注册完成的消息，通知eMME终端注册完毕。
S302，eMME判断该UE的所在组播组的承载网组播IP地址是否已经分配。
S303，若没有分配，eMME向xGW发送承载网组播IP地址分配请求，发送的请求中携带组播组标识。
S304，xGW接收到承载网组播IP地址分配请求后，为该组播组分配承载网组播IP地址。
S305，xGW向eMME返回承载网组播IP地址分配应答消息，消息中携带承载网组播IP地址。
S306，eMME检查组播组中的参与基站是否加入组播，若没有，向这些参与基站发送建立组播请求的消息，消息中携带承载网组播IP地址和组标识。
S307，参与基站向eMME返回建立组播请求的应答。
S308，参与基站收到建立组播请求的消息后，通过IGMP协议发送加入组播消息，向承载网中的上级路由器表明要监听该组播IP地址的组播，并向eMME返回建立组播请求的响应。
S309，承载网使用PIM-SSM协议建立起以xGW为组播源、参与基站为叶子节点的组播分发树。
当组播组中的所有终端都完成注册之后，该组播组的所有参与基站的组播分发树就预先建立好了。
之后，S401，任意的终端发起组呼，核心网设备与发起终端所在的组播组建立组呼。
S402，核心网设备接收来自数据源的组呼下行数据包，该下行数据包为单播数据；而后，核心网设备将组呼下行数据包发送至承载网，下行数 据包沿组播分发树传送至参与基站，此时下行数据包为组播数据，数据包根据组播分发树传送到各个参与基站，通过基站最后传输到终端。
参考图5所示，为本实施例的LTE集群通信系统下的组呼数据包协议栈，核心网的网关xGW和基站两侧的IP包都使用了承载网组播IP地址，在核心网设备将组呼下行数据包发送至承载网时携带承载网组播IP地址，承载网使用该承载网组播IP地址实现组播，该具体的实施例中，下行数据包的最外层IP头目的地址设置为承载网组播IP地址，然后，作为组播分发的源头把该组呼下行数据包发送至承载网。
S403，在组呼结束后，核心网设备并不触发基站退出组播，基站继续监听该组数据，承载网中相应的组播分发树仍然存在。
具体的，TCF收到组呼释放请求之后，通知eMME结束此次组呼，eMME向终端发送组呼释放指示，则此次组呼结束，但此时并不触发基站退出组播，基站继续监听该组数据，承载网中相应的组播分发树仍然存在。
只有当基站下没有与该组签约的终端时，基站才退出组播并发送退出组播消息给承载网。
参考图6所示，具体的，S501，终端向eMME发送注销请求，通知eMME退出集群业务。
S501，eMME发送请求注销的消息给TCF。
S502，eMME返回接受注销请求的消息给终端。
S503，eMME检查组播组中是否还存在注册的终端，若没有，向xGW发送释放该组播组的承载网组播IP地址的请求，请求中携带组标识。
S504，xGW接收到释放请求后，释放该组播组的承载网组播IP地址。
S505，xGW向eMME返回释放请求应答。
S506，eMME向基站发送退出组播组请求。
S507，基站向收到退出组播请求后，通过IGMP协议发送退出组播消息，向承载网中的上级路由器表明组播组中的基站要退出该组播组。
S508，承载网接收到退出组播消息后，更新承载网的组播分发树，将该组播组中终端的签约基站从组播分发树中删除。这样，在组播组中所有的终端都没有在注册之后，与终端签约的基站退出组播。
以上为LTE集群通信系统的组呼业务处理方法的实施例，该处理方法还可以应用于其他的集群通信系统，如PDT集群通信系统，对于PDT集群通信系统，核心网设备为交换机(MSC,Mobile Switch Center)，在该具体的实施例中，在预先设置组播分发树的过程中，交换机接收到终端的注册完成消息后，判断已注册终端所在的组播组是否已分配承载网组播IP地址，若没有，则为该组播组分配承载网组播IP地址，并向已注册终端所在的组中的参与基站发送该组播组的承载网组播IP地址，并触发未加入组播的参与基站向承载网发送加入组播的请求；承载网接收到加入组播的请求后，建立以交换机为组播源、参与基站为叶子节点的组播分发树。
在组播分发树的删除过程中，交换机接收到终端注销请求消息后，判断注销终端所在的组播组中是否还存在注册的终端，若不存在，则释放注销终端所在组播组的承载网组播IP地址，并触发该组播组中的参与基站向承载网发送退出组播消息；承载网接收到退出组播消息后，将该组播组的参与基站从组播分发树中删除。。
以上对本发明的基于集群通信系统的组呼业务处理方法及实施例进行了详细的描述，此外，本发明还提供了，一种核心网设备，参考图7所示，包括：
数据接收单元710，用于建立组呼后，核心网设备接收来自数据源的组呼下行数据包；
数据包发送单元720，用于将组呼下行数据包发送至承载网，所述承载网中预先设置有组播分发树，所述组播分发树以核心网设备为组播源、组播组中的参与基站为叶子节点。
进一步地，还包括：
触发单元730，用于当组播组中首次有终端向核心网设备注册时，触发组播分发树在承载网中的建立。
进一步地，触发单元730包括：
组播地址分配单元7301，用于为所述组播组分配承载网组播IP地址；
第一请求单元7302，用于向所述组播组中的参与基站发送所述承载网组播IP地址，并触发组播组中的参与基站向承载网发送加入组播的请求， 加入组播的请求用于触发承载网建立起以核心网设备为组播源、组播组中的参与基站为叶子节点的组播分发树。
进一步地，还包括：
判断单元，用于接收到终端注销请求消息后，判断注销终端所在的组播组中是否还存在注册的终端；
组播地址释放单元，用于注销终端所在组中不存在注册的终端时，释放注销终端所在组播组的承载网组播IP地址；
第二请求单元，用于触发所述组播中的参与基站向承载网发送退出组播消息，退出组播消息用于触发承载网将该组的参与基站从组播分发树中删除。
此外，本发明还提供了相应的组呼业务处理系统，包括上述的核心网设备，以及承载网和基站。
在该组呼业务处理系统中，核心网设备包括数据接收单元，用于建立组呼后，核心网设备接收来自数据源的组呼下行数据包；数据发送单元，用于将组呼下行数据包发送至承载网，所述承载网中预先设置有组播分发树，所述组播分发树以核心网设备为组播源、组播组中的参与基站为叶子节点。
进一步地，核心网设备还包括触发单元，用于当组播组中首次有终端向核心网设备注册时，触发组播分发树在承载网中的建立。
进一步地，触发单元包括：
组播地址分配单元，用于为所述组播组分配承载网组播IP地址；
第一请求单元，用于向所述组播组中的参与基站发送所述承载网组播IP地址，并触发组播组中的参与基站向承载网发送加入组播的请求，加入组播的请求用于触发承载网建立起以核心网设备为组播源、组播组中的参与基站为叶子节点的组播分发树。
进一步地，核心网设备还包括：判断单元，用于接收到终端注销请求消息后，判断注销终端所在的组播组中是否还存在注册的终端；组播地址释放单元，用于注销终端所在组中不存在注册的终端时，释放注销终端所在组播组的承载网组播IP地址；第二请求单元，用于触发所述组播中的参 与基站向承载网发送退出组播消息，退出组播消息用于触发承载网将该组的参与基站从组播分发树中删除。
在该组呼业务处理系统中，承载网中预先建立有以核心网设备为源头、参与基站为叶子节点的组播分发树。
进一步地，承载网还用于在接收到建立组播分发树的信息后，建立起以核心网设备为源头、参与基站为叶子节点的组播分发树。
进一步地，承载网还用于在接收到退出组播消息之后，将组播组中的参与基站从组播分发树中删除。
在一些实施例中，所述处理系统基于LET集群系统，核心网设备包括通过eMME、xGW等网元。在另一些实施例中，所述处理系统基于PDT集群通信系统，核心网设备为交换机。
此外，参考图8所示，本发明还提供了核心网设备800，包括存储器802和处理器801，所述存储器802用于存储程序代码805，并将所述程序代码805传输给所述处理器801；
所述处理器801用于根据所述程序代码805中的指令，执行以下步骤：
建立组呼后，接收来自数据源的组呼下行数据包；
将组呼下行数据包发送至承载网，所述承载网中预先设置有组播分发树，所述组播分发树以核心网设备为组播源、组播组中的参与基站为叶子节点。
进一步地，还执行以下步骤：当组播组中首次有终端向核心网设备注册时，触发组播分发树在承载网中的建立。
进一步地，触发组播分发树在承载网中的建立包括：
为所述组播组分配承载网组播IP地址；
向所述组播组中的参与基站发送所述承载网组播IP地址，并触发组播组中的参与基站向承载网发送加入组播的请求，加入组播的请求用于触发承载网建立起以核心网设备为组播源、组播组中的参与基站为叶子节点的组播分发树。
进一步地，还执行以下步骤：
接收到终端注销请求消息后，判断注销终端所在的组播组中是否还存 在注册的终端，若不存在，则释放注销终端所在组播组的承载网组播IP地址，并触发所述组播中的参与基站向承载网发送退出组播消息，退出组播消息用于触发承载网将该组的参与基站从组播分发树中删除。
在本发明实施例中，所述处理器801与所述存储器802通过总线803连接，所述核心网设备800具有通信接口804，所述总线803可以是工业标准体系结构(Industry Standard Architecture，简称为ISA)总线或外部设备互连(Peripheral Component，简称为PCI)总线或扩展工业标准体系结构(Extended Industry Standard Architecture，简称为EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线中的一种或多种。为便于表示，图中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
所述存储器802用于存储可执行程序代码，该程序代码包括计算机操作指令。所述存储器802可以包含高速RAM(Ramdom Access Memory)存储器。可选地，所述存储器802还可以还包括非易失性存储器(non-volatile memory)。例如所述存储器802可以包括磁盘存储器。
所述处理器801可以是一个中央处理器(Central Processing Unit，简称为CPU)，或者所述处理器801可以是特定集成电路(Application Specific Integrated Circuit，简称为ASIC)，或者所述处理器801可以是被配置成实施本发明实施例的一个或多个集成电路。
本发明实施例的核心网设备例如可以是核心网网元、交换机等设备。
本发明可以在由计算机执行的计算机可执行指令的一般上下文中描述，例如程序模块。一般地，程序模块包括执行特定任务或实现特定抽象数据类型的例程、程序、对象、组件、数据结构等等。也可以在分布式计算环境中实践本发明，在这些分布式计算环境中，由通过通信网络而被连接的远程处理设备来执行任务。在分布式计算环境中，程序模块可以位于包括存储设备在内的本地和远程计算机存储介质中。
对于设备实施例而言，由于其基本对应于方法实施例，所以相关之处参见方法实施例的部分说明即可。以上所描述的设备实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一 个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
以上所述仅是本发明的具体实施方式，应当指出，对于本技术领域的普通技术人员来说，在不脱离本发明原理的前提下，还可以做出若干改进和润饰，这些改进和润饰也应视为本发明的保护范围。

Claims (10)

  1. 一种基于集群通信系统的组呼业务处理方法，其特征在于，包括：
    建立组呼后，核心网设备接收来自数据源的组呼下行数据包；
    所述核心网设备将组呼下行数据包发送至承载网，所述承载网中预先设置有组播分发树，所述组播分发树以核心网设备为组播源、组播组中的参与基站为叶子节点。
  2. 根据权利要求1所述的方法，其特征在于，预先设置组播分发树的方法包括：
    当组播组中首次有终端向核心网设备注册时，由核心网设备触发组播分发树在承载网中的建立。
  3. 根据权利要求2所述的方法，其特征在于，由核心网设备触发组播分发树在承载网中的建立包括：
    核心网设备为所述组播组分配承载网组播IP地址；
    核心网设备向所述组播组中的参与基站发送所述承载网组播IP地址，并触发组播组中的参与基站向承载网发送加入组播的请求，加入组播的请求用于触发承载网建立起以核心网设备为组播源、组播组中的参与基站为叶子节点的组播分发树。
  4. 根据权利要求1-3中任一项所述的方法，其特征在于，还包括：
    核心网设备接收到终端注销请求消息后，判断注销终端所在的组播组中是否还存在注册的终端，若不存在，则释放注销终端所在组播组的承载网组播IP地址，并触发所述组播组中的参与基站向承载网发送退出组播消息，退出组播消息用于触发承载网将该组播组的参与基站从组播分发树中删除。
  5. 一种核心网设备，其特征在于，包括：
    数据接收单元，用于建立组呼后，核心网设备接收来自数据源的组呼下行数据包；
    数据发送单元，用于将组呼下行数据包发送至承载网，所述承载网中预先设置有组播分发树，所述组播分发树以核心网设备为组播源、组播组中的参与基站为叶子节点。
  6. 根据权利要求5所述的设备，其特征在于，还包括：
    触发单元，用于当组播组中首次有终端向核心网设备注册时，触发组播分发树在承载网中的建立。
  7. 根据权利要求6所述的设备，其特征在于，触发单元包括：
    组播地址分配单元，用于为所述组播组分配承载网组播IP地址；
    第一请求单元，用于向所述组播组中的参与基站发送所述承载网组播IP地址，并触发组播组中的参与基站向承载网发送加入组播的请求，加入组播的请求用于触发承载网建立起以核心网设备为组播源、组播组中的参与基站为叶子节点的组播分发树。
  8. 根据权利要求5-7中任一项所述的设备，其特征在于，还包括：
    判断单元，用于接收到终端注销请求消息后，判断注销终端所在的组播组中是否还存在注册的终端；
    组播地址释放单元，用于注销终端所在组中不存在注册的终端时，释放注销终端所在组播组的承载网组播IP地址；
    第二请求单元，用于触发所述组播组中的参与基站向承载网发送退出组播消息，退出组播消息用于触发承载网将该组播组的参与基站从组播分发树中删除。
  9. 一种组呼业务处理系统，其特征在于，包括如权利要求5-8中任一项所述的核心网设备，以及承载网和基站。
  10. 一种核心网设备，其特征在于，包括存储器和处理器，所述存储器用于存储程序代码，并将所述程序代码传输给所述处理器；
    所述处理器用于根据所述程序代码中的指令，执行如权利要求1-4中任一项所述的基于集群通信系统的组呼业务处理方法。
PCT/CN2016/073587 2016-02-05 2016-02-05 一种组呼业务处理方法及系统、核心网设备 Ceased WO2017132971A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/073587 WO2017132971A1 (zh) 2016-02-05 2016-02-05 一种组呼业务处理方法及系统、核心网设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/073587 WO2017132971A1 (zh) 2016-02-05 2016-02-05 一种组呼业务处理方法及系统、核心网设备

Publications (1)

Publication Number Publication Date
WO2017132971A1 true WO2017132971A1 (zh) 2017-08-10

Family

ID=59500417

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/073587 Ceased WO2017132971A1 (zh) 2016-02-05 2016-02-05 一种组呼业务处理方法及系统、核心网设备

Country Status (1)

Country Link
WO (1) WO2017132971A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109089333A (zh) * 2018-10-10 2018-12-25 北京中兴高达通信技术有限公司 一种数字集群系统组派接实现方法
CN110958621A (zh) * 2018-09-27 2020-04-03 普天信息技术有限公司 宽带集群通信系统中多集团访问配置方法和装置
CN112449395A (zh) * 2019-08-28 2021-03-05 中国联合网络通信集团有限公司 一种数据传输方法、核心网设备和amf
CN119232681A (zh) * 2023-06-29 2024-12-31 华为技术有限公司 一种数据处理方法、交换节点及相关系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010091533A1 (zh) * 2009-02-12 2010-08-19 上海贝尔股份有限公司 在固定网络中传送移动组播业务的方法和装置
CN102857873A (zh) * 2011-06-30 2013-01-02 中兴通讯股份有限公司 基于td-lte的宽带数字集群系统及其数据传输方法
CN102883273A (zh) * 2011-07-12 2013-01-16 普天信息技术研究院有限公司 一种实现组呼通信的方法
CN104254054A (zh) * 2013-06-25 2014-12-31 电信科学技术研究院 一种集群通信方法及装置和系统
CN105635987A (zh) * 2016-02-05 2016-06-01 海能达通信股份有限公司 一种组呼业务处理方法及系统、核心网设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010091533A1 (zh) * 2009-02-12 2010-08-19 上海贝尔股份有限公司 在固定网络中传送移动组播业务的方法和装置
CN102857873A (zh) * 2011-06-30 2013-01-02 中兴通讯股份有限公司 基于td-lte的宽带数字集群系统及其数据传输方法
CN102883273A (zh) * 2011-07-12 2013-01-16 普天信息技术研究院有限公司 一种实现组呼通信的方法
CN104254054A (zh) * 2013-06-25 2014-12-31 电信科学技术研究院 一种集群通信方法及装置和系统
CN105635987A (zh) * 2016-02-05 2016-06-01 海能达通信股份有限公司 一种组呼业务处理方法及系统、核心网设备

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110958621A (zh) * 2018-09-27 2020-04-03 普天信息技术有限公司 宽带集群通信系统中多集团访问配置方法和装置
CN109089333A (zh) * 2018-10-10 2018-12-25 北京中兴高达通信技术有限公司 一种数字集群系统组派接实现方法
CN109089333B (zh) * 2018-10-10 2021-11-05 北京中兴高达通信技术有限公司 一种数字集群系统组派接实现方法
CN112449395A (zh) * 2019-08-28 2021-03-05 中国联合网络通信集团有限公司 一种数据传输方法、核心网设备和amf
CN112449395B (zh) * 2019-08-28 2022-09-02 中国联合网络通信集团有限公司 一种数据传输方法、核心网设备和amf
CN119232681A (zh) * 2023-06-29 2024-12-31 华为技术有限公司 一种数据处理方法、交换节点及相关系统

Similar Documents

Publication Publication Date Title
US11700509B2 (en) Communication system, communication method, and apparatus thereof
CN111526552B (zh) Ue执行的方法及ue、以及smf实体执行的方法及smf实体
US10542415B2 (en) Data transmission method for edge multimedia broadcast/multicast service (MBMS) service and related device
US7724743B2 (en) System and method for distributing VoIP data packets in group communications amoung wireless telecommunication devices
CN110351670B (zh) 集群通信系统、集群服务器、通信装置以及介质
US10397012B2 (en) Evolved multimedia broadcast/multicast service (EMBMS) system and EMBMS system management method
CN104284298B (zh) 一种群组通信中的资源控制方法及组通信服务器
US20220417907A1 (en) Communication method and apparatus for multicast broadcast service, medium, and electronic device
CN106488409B (zh) 一种单播发送广播多播数据的方法、装置及系统
CN104254054A (zh) 一种集群通信方法及装置和系统
US11337040B2 (en) Broadcast bearer management method and device thereof
CN111556539A (zh) Ue执行的方法及ue、以及smf实体执行的方法及smf实体
JP2023509071A (ja) マルチキャストサービスセッション操作の方法、装置及び通信機器
CN106411750B (zh) 数据分发方法及系统
CN116420347A (zh) 用于时间敏感网络中的组播服务支持的方法和装置
WO2017132971A1 (zh) 一种组呼业务处理方法及系统、核心网设备
CN105635987B (zh) 一种组呼业务处理方法及系统、核心网设备
JP7724948B2 (ja) 通信トンネル管理方法、装置、およびシステム
CN101247541B (zh) 移动通信网络多媒体组播业务的实现方法
CN105764034A (zh) 组呼下行数据包传输方法和系统及设备
WO2017132972A1 (zh) 组呼下行数据包传输方法和系统及设备
WO2021197469A1 (zh) 传输通道变更方法、接入网设备及核心网设备
EP4154469A1 (en) Apparatus, methods, and computer programs for multicast session management in 5g networks
HK40027908A (zh) Ue执行的方法及ue、以及smf实体执行的方法及smf实体
HK40027905A (zh) Ue执行的方法及ue、以及smf实体执行的方法及smf实体

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16888796

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16888796

Country of ref document: EP

Kind code of ref document: A1