WO2019104960A1 - Mbms服务区域的管理方法及系统 - Google Patents

Mbms服务区域的管理方法及系统 Download PDF

Info

Publication number
WO2019104960A1
WO2019104960A1 PCT/CN2018/088005 CN2018088005W WO2019104960A1 WO 2019104960 A1 WO2019104960 A1 WO 2019104960A1 CN 2018088005 W CN2018088005 W CN 2018088005W WO 2019104960 A1 WO2019104960 A1 WO 2019104960A1
Authority
WO
WIPO (PCT)
Prior art keywords
communication network
network element
service
identifier
area
Prior art date
Application number
PCT/CN2018/088005
Other languages
English (en)
French (fr)
Inventor
王玮
周衡
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP18884339.5A priority Critical patent/EP3720155A4/en
Priority to KR1020207004249A priority patent/KR102277535B1/ko
Publication of WO2019104960A1 publication Critical patent/WO2019104960A1/zh

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/02—Services making use of location information
    • H04W4/021—Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast

Definitions

  • the present disclosure relates to the field of communications technologies, for example, to a method and system for managing a Multimedia Broadcast Multicast Service (MBMS) service area.
  • MBMS Multimedia Broadcast Multicast Service
  • LTE Long Term Evolution
  • eMBMS enhanced Multimedia Broadcast Multicast Service
  • OFDM Orthogonal Frequency Division Multiplexing
  • a point-to-multipoint broadcast channel is provided, which is suitable for a terminal having a video function to receive a digital audio or video service in a broadcast or multicast form through a Physical Multicasts Channel (PMCH).
  • PMCH Physical Multicasts Channel
  • eMBMS Advanced Mobile Broadband
  • 3GPP Third Generation Partnership Project
  • MCPTT Mission-critical push-to-talk
  • eMBMS technology will play an important role in the field of public safety clusters, providing cluster services to meet business needs for scenarios such as public security, fire protection, railways, and emergency relief.
  • the service coverage of the eMBMS is based on the MBMS service area multicast single frequency network area (MBSFN Area, MA).
  • MMSFN Area MMS service area multicast single frequency network area
  • a service can only be carried out in one or more corresponding MAs, that is, in the corresponding physical space.
  • the eMBMS supports a flexible MA configuration.
  • the coverage of the MA can be large or small, and can be adjusted freely through the background.
  • the configuration of the MA is always static or semi-static, which makes it impossible to adapt to the requirements of certain usage scenarios.
  • the embodiment of the present application provides a method and a system for managing an MBMS service area, which can implement an MBMS service area that is dynamically adjusted based on a physical location change of a service initiating terminal.
  • An embodiment of the present application provides a method for managing an MBMS service area, including:
  • the first communication network element receives the first session establishment request that carries the exclusive MBMS identifier, and the first communication network element determines, according to the received location notification message or the first region determination message, whether the first communication network element is in the Within the service area of the exclusive MBSM indicated by the exclusive MBMS logo;
  • the dedicated MBMS identifier is used to indicate that the dedicated MBMS of the service area is dynamically adjusted based on the physical location change of the service initiating terminal; the location notification message is used to indicate that the service initiating terminal is currently in the first communication network element. Coverage.
  • An embodiment of the present application provides a method for managing an MBMS service area, including:
  • the second communication network element receives the second session establishment request that carries the dedicated MBMS identifier, where the dedicated MBMS identifier is used to indicate that the dedicated MBMS of the service area is dynamically adjusted based on the physical location change of the service initiation terminal;
  • the second communication network element sends a first session establishment request carrying the dedicated MBMS identifier to the first communication network element.
  • An embodiment of the present application provides a method for managing an MBMS service area, including:
  • the second communication network element monitors the first communication network element where the service originating terminal of the dedicated MBMS is located when detecting the dedicated MBMS of the service area based on the physical location change of the service initiating terminal;
  • the second communication network element When the second communication network element receives the session establishment request carrying the dedicated MBMS identity, or the first communication network element where the service initiation terminal is located is switched, the second communication network element initiates the terminal to the service.
  • the first communication network element currently located sends a location notification message;
  • the dedicated MBMS identifier is used to indicate the dedicated MBMS, and the location notification message is used to indicate that the service initiation terminal is currently in the coverage of the first communication network element.
  • An embodiment of the present application provides a method for managing an MBMS service area, including:
  • the service originating terminal applies for a data link
  • the service initiating terminal sends the data carrying the dedicated service identifier by using the data link, where the dedicated service identifier is used to indicate that the dedicated MBMS of the service area is dynamically adjusted based on the physical location change of the service initiating terminal, and the exclusive MBMS There is a correspondence between the service identifier and the dedicated MBMS identifier.
  • An embodiment of the present application provides a method for managing an MBMS service area, including:
  • the service server receives the data carrying the dedicated service identifier, where the dedicated service identifier is used to indicate that the dedicated MBMS of the service area is dynamically adjusted based on the physical location change of the service initiating terminal;
  • the service server determines, according to the dedicated service identifier, a dedicated MBMS identifier corresponding to the dedicated service identifier, and triggers a session establishment process.
  • the embodiment of the present application provides a management system for an MBMS service area, including: a first communication network element and a second communication network element; the first communication network element is connected to the second communication network element;
  • the second communication network element is configured to send, to the first communication network element, a first session establishment request that carries a dedicated MBMS identifier
  • the first communication network element is configured to receive the first session establishment request, and determine, according to the received location notification message or the first region determination message, whether the first communication network element is in the exclusive indication indicated by the exclusive MBMS identifier.
  • the dedicated MBMS identifier is used to indicate that the dedicated MBMS of the service area is dynamically adjusted based on the physical location change of the service initiating terminal; the location notification message is used to indicate that the service initiating terminal is currently in the coverage of the first communication network element.
  • An embodiment of the present application provides a communication network element, including: a memory and a processor, where the memory is configured to store a management program of an MBMS service area, and the management program is implemented by the processor to implement the management method provided above.
  • An embodiment of the present application provides a terminal, including: a memory and a processor, where the memory is configured to store a management program of an MBMS service area, and the management program is implemented by the processor to implement the foregoing management applied to any one of the terminals. method.
  • An embodiment of the present application provides a service server, including: a memory and a processor, where the memory is configured to store a management program of an MBMS service area, and the management program is implemented by the processor to implement the foregoing application to the service server. Management method.
  • the embodiment of the present application further provides a computer readable medium storing a management program of an MBMS service area, where the management program is executed by a processor to implement the management method described in any one of the above.
  • the physical location of the service initiation terminal is monitored by identifying the service type, and the first communication network element (for example, the base station) adaptively dynamically adjusts the MBMS. Service Area.
  • the embodiment of the present application compensates for the limitation that the current eMBMS service cannot be adapted to a specific usage scenario, and is applicable to various scenarios in the public security field based on MCPTT, such as railway scheduling, disaster warning, video surveillance, and the like.
  • the embodiment of the present application facilitates flexible deployment of the eMBMS, and allows the wireless resource to quickly switch between the multicast service and the non-multicast service, that is, meet the resource usage requirements of the burst hotspot, and avoid resource waste.
  • the self-organized dynamic service area adjustment mode of the first communication network element is also generally applicable to other application scenarios.
  • FIG. 1 is a schematic diagram of a management system of an MBMS service area according to an embodiment of the present application
  • FIG. 2 is a diagram showing an example of a management system of an MBMS service area according to an embodiment of the present application
  • FIG. 3 is a flowchart of a method for managing an MBMS service area according to an embodiment of the present application
  • FIG. 4 is a flowchart of another MBMS service area management method according to an embodiment of the present application.
  • FIG. 5 is a flowchart of another MBMS service area management method according to an embodiment of the present application.
  • FIG. 6 is a flowchart of another MBMS service area management method according to an embodiment of the present application.
  • FIG. 7 is a flowchart of another MBMS service area management method according to an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of a registration phase according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a service flow initiation phase according to an embodiment of the present application.
  • FIG. 10 is a schematic diagram of processing in a dynamic area generation phase according to an embodiment of the present application.
  • FIG. 11 is a diagram showing an example of dynamic adjustment of a service area according to an embodiment of the present application.
  • FIG. 12 is another exemplary diagram of dynamic adjustment of a service area according to an embodiment of the present application.
  • FIG. 13 is a schematic diagram of an apparatus for managing an MBMS service area according to an embodiment of the present application.
  • FIG. 14 is a schematic diagram of another MBMS service area management apparatus according to an embodiment of the present application.
  • FIG. 15 is a schematic diagram of another MBMS service area management apparatus according to an embodiment of the present application.
  • 16 is a schematic diagram of another MBMS service area management apparatus according to an embodiment of the present application.
  • FIG. 17 is a schematic diagram of another MBMS service area management apparatus according to an embodiment of the present application.
  • FIG. 18 is a schematic diagram of a first communication network element according to an embodiment of the present application.
  • FIG. 19 is a schematic diagram of a second communication network element according to an embodiment of the present application.
  • FIG. 20 is a schematic diagram of a third communication network element according to an embodiment of the present application.
  • FIG. 21 is a schematic diagram of a terminal according to an embodiment of the present application.
  • FIG. 22 is a schematic diagram of a service server according to an embodiment of the present application.
  • a certain service needs to access all related users within a certain range around the service initiator after the service is initiated. Moreover, as the physical location of the service initiator changes continuously, the coverage area of the service needs to be continuously adjusted, so that users newly entering the service coverage area join the cluster, and users who are far away from the service coverage area automatically exit.
  • the embodiment of the present invention provides a method and a system for managing an MBMS service area.
  • the first communication network element for example, a base station
  • the first communication network element automatically adjusts the service coverage to form a dynamic MBMS service area (MBMS area) that is adjusted according to the physical location change of the service initiation terminal.
  • MBMS area dynamic MBMS service area
  • FIG. 1 is a schematic diagram of a management system of an MBMS service area according to an embodiment of the present application.
  • the management system of the MBMS service area provided by the embodiment includes: a first communication network element 11 and a second communication network element 12; wherein the first communication network element 11 is connected to the second communication network element.
  • the second communication network element 12 is configured to send a first session establishment request carrying a dedicated MBMS identifier (MBMS ID) to the first communication network element 11.
  • MBMS ID dedicated MBMS identifier
  • the first communication network element 11 is configured to receive the first session establishment request, and determine, according to the received location notification message or the first region decision message, whether it is in the service area of the dedicated MBMS indicated by the exclusive MBMS identifier.
  • the dedicated MBMS identifier is used to indicate a dedicated MBMS that dynamically adjusts the service area based on the physical location change of the service initiating terminal.
  • the location notification message is used to indicate that the service initiating terminal is currently in the coverage of the first communication network element 11.
  • the difference between the dedicated MBMS and the normal MBMS is that the MBMS service area corresponding to the dedicated MBMS is limited by the physical location of the service originating terminal, and is dynamically changed.
  • the first area decision message may be used to indicate the interval between the first communication network element adjacent to the first communication network element 11 and the service area center of the dedicated MBMS.
  • the second communication network element 12 may be configured to send a first session establishment request to the first communication network element 11 after receiving the second session establishment request carrying the dedicated MBMS identity.
  • the management system provided in this embodiment may further include: a third communication network element 13, and the third communication network element 13 is respectively connected to the first communication network element 11 and the second communication network. Yuan 12.
  • the third communication network element 13 can be configured to detect the dedicated MBMS, and then monitor the first communication network element where the service originating terminal of the dedicated MBMS is located.
  • the third communication network element 13 may be further configured to: according to the received third session establishment request carrying the dedicated MBMS identifier, or according to the handover of the first communication network element where the service initiation terminal is located, to the service initiation terminal currently located.
  • the first communication network element e.g., the first communication network element 11 transmits a location notification message.
  • the system in this embodiment may further include: a service initiating terminal (User Equipment, UE) 10 configured to send data carrying a dedicated service identifier through a link.
  • UE User Equipment
  • the dedicated service identifier is used to indicate the exclusive MBMS identifier, and the corresponding service identifier has a corresponding relationship with the dedicated MBMS identifier.
  • the system in this embodiment may further include: a service server 14 configured to receive data carrying a dedicated service identifier, and determine, according to the dedicated service identifier, a corresponding to the dedicated service identifier.
  • a service server 14 configured to receive data carrying a dedicated service identifier, and determine, according to the dedicated service identifier, a corresponding to the dedicated service identifier.
  • a dedicated MBMS logo that triggers the session establishment process.
  • the first communication network element 11 may include a base station (eNodeB), and the second communication network element 12 may include a Multi-cell/Multicast Coordination Entity (MCE), and the third communication network
  • the element 13 may include a Mobility Management Entity (MME).
  • MME Mobility Management Entity
  • FIG. 2 is a schematic diagram of a management system of an MBMS service area according to an embodiment of the present application.
  • the first communication network element is an eNodeB
  • the second communication network element is an MCE
  • the third communication network element is an MME
  • the service server is a cluster service server (for example, an MCPTT server).
  • the management system provided in this example may include: a UE 20, an eNodeB 21, an MCE 22, an MME 23, a cluster service server 24, a Broadcast/Multicast Service Center (BM-SC) 25, and MBMS Gateway (MBMS Gate Way, MBMS-GW) 26.
  • BM-SC 25 and MBMS-GW 26 are participants in the process of initiating multicast services.
  • the UE 20 is configured to carry a dedicated service identity at the service initiation phase, ie as a service origination terminal.
  • the cluster service server 24 is configured to identify whether the currently initiated service is in a dedicated MBMS service and identify related information of the service originating terminal.
  • the MCE 22 is configured to configure a dedicated MBMS identifier corresponding to the dedicated service identifier, and uniformly manages channel resources corresponding to the dedicated service identifier, and supports configuring the range of the dynamic MBMS service area by using the background parameter.
  • the MME 23 is configured to monitor the physical location of the service originating terminal and transmit the location change information of the service originating terminal to the eNodeB 21.
  • the plurality of eNodeBs 21 to which the MCE 22 and the MME 23 belong are respectively configured to determine whether the eNodeB is located within the dynamic range of the MBMS service area, and guide the radio resource management policy.
  • the process of dynamically adjusting the MBMS service area based on the physical location of the service originating terminal may include the following three phases: a registration phase, a business process initiation phase, and a dynamic region generation phase.
  • a registration phase a registration phase
  • a business process initiation phase a business process initiation phase
  • a dynamic region generation phase a phase that is generated by the process of dynamically adjusting the MBMS service area.
  • the registration phase can include the following process.
  • the MCE reports the exclusive MBMS ID to the MME to identify the dedicated MBMS.
  • the difference between the dedicated MBMS and other common MBMSs is that the MBMS Area corresponding to the dedicated MBMS is restricted by the location of the service originating terminal and dynamically changes; the dedicated MBMS ID can establish a chain between the MCE and the MME.
  • the MME is carried to the MME, or it can be carried to the MME through an independent message.
  • the MCE reserves an independent multicast resource for the dedicated MBMS, and the multicast resource may include at least one multicast subframe. In an embodiment, the MCEs schedule these multicast resources when the dedicated MBMS is initiated.
  • the MCE sends a dedicated MBMS ID and a dynamic area range identifier to the eNodeB.
  • the dynamic zone range identifier may be configured by the background to indicate the scope of the service area of the dedicated MBMS.
  • the dynamic area range identifier may indicate the maximum interval of the service area boundary of the dedicated MBMS relative to the center of the service area.
  • the dedicated MBMS ID and the dynamic area range identifier may be carried in the response message that the eNodeB establishes a link connection to the MCE, or may be actively sent to the eNodeB through a dedicated configuration message.
  • the dedicated MBMS ID corresponding to the exclusive MBMS and the routing information supporting the dedicated MBMS ID are set on the cluster service server.
  • the business process initiation phase can include the following first steps to fifth steps.
  • the first step is to initiate a dedicated cluster business.
  • the UE initiates a dedicated cluster service, and writes the dedicated service identifier into the user plane data packet, which is used to indicate the service type to the cluster service server.
  • the UE uses a dedicated QoS Class Identifier (QCI) to apply for a bearer link.
  • QCI QoS Class Identifier
  • the proprietary QCI can be an extended QCI that is independent of the standard protocol and is dedicated to the above-mentioned proprietary cluster services.
  • the second step business type identification and initiation.
  • the cluster service server determines that the service initiated by the UE is in the dynamic adjustment of the service area based on the location change of the service originating terminal, that is, the dedicated MBMS ID, that is, the corresponding service of the exclusive MBMS ID.
  • the cluster service server sends the user plane data, the exclusive MBMS ID, and the routing information that supports the dedicated MBMS ID to the BM-SC, triggering the eMBMS session establishment process.
  • the third step is to monitor the location of the service originating terminal.
  • the MME monitors the physical identity of the eNodeB (for example, an Internet Protocol (IP) address) and its changes, and tracks and records in which coverage of the eNodeB the service initiating terminal is currently located.
  • IP Internet Protocol
  • the MME notifies the eNodeB of the location change information of the service originating terminal.
  • the BM-SC performs a standard session establishment process.
  • the MME receives a session establishment request (corresponding to the third session establishment request) carrying the exclusive MBMS ID from the MBMS-GW
  • the MME monitors the location according to the location of the service originating terminal. And sending a location notification message to the eNodeB where the current service initiating terminal is located, to notify the eNodeB that the wireless connection is being provided for the service initiating terminal.
  • the MME sends a location notification message to the eNodeB that is providing the radio access to the service initiating terminal, according to the change of the location monitoring record, until the service bearer of the service initiating terminal is removed.
  • the fifth step the multicast service chooses to execute.
  • the MME continues to perform the standard session establishment process. After the eNodeB receives the session connection request (corresponding to the first session connection request) from the MCE carrying the exclusive MBMS ID, and the corresponding scheduling information, the eNodeB first needs to confirm whether it is in the Exclusive MBMS within the dynamic service area.
  • the eNodeB when an eNodeB determines that the eNodeB is not in the dynamic service area, the eNodeB saves the relevant configuration information delivered by the MCE, and schedules its corresponding radio resource according to the mode of the non-multicast subframe; when an eNodeB decides When the eNodeB is in the dynamic service area, the subsequent standard session establishment process is performed, that is, the service notification and related configuration parameters are sent, and the multicast protocol Internet Protocol (IP) is officially added to perform the corresponding radio resource location. Multicast business.
  • IP Internet Protocol
  • the dynamic region generation phase may include the following steps 1 through 4.
  • the eNodeB After receiving the dynamic area range identifier from the MCE, the eNodeB starts to determine the parameter in the local maintenance area, and the area decision parameter is used to determine whether the eNodeB is in the dynamic service area; the area decision parameter includes the following three elements: dynamic area range ID, center position offset ID, and serial number.
  • the dynamic area range identifier is received from the MCE and stored directly locally.
  • the center position offset identifier is maintained by the eNodeB itself, and the initialization value is the same as the dynamic area range identifier.
  • the serial number is maintained by the eNodeB and the initialization value is all 0s.
  • a dynamic area generation process is triggered.
  • the eNodeB adds 1 to the locally saved sequence number, sets the locally saved center position offset flag to 0, and adds the locally saved center position offset flag to the updated sequence number.
  • a regional decision message (corresponding to the second region decision message described above) is formed. The zone decision message is sent to all contiguous eNodeBs of the eNodeB through the X2 or S1 interface, and proceeds to the fourth step.
  • the third step when an eNodeB receives the area decision message (corresponding to the first area decision message), if the sequence number carried in the received area decision message is the same as the value of the serial number saved locally by the eNodeB, Then, the received regional decision message is directly ignored, and the process is terminated. If the sequence number carried in the received regional decision message is different from the value of the serial number saved locally by the eNodeB, the received regional decision message is carried. The serial number and center position offset are identified to the local.
  • the process proceeds to the fourth step; if the received regional determination message carries the central location offset identifier and the local If the value of the saved dynamic area range identifier is different, the locally updated center position offset identifier is incremented by 1 and together with the updated sequence number to form an area decision message (corresponding to the second area decision message described above), and then The zone decision message is sent to all contiguous eNodeBs of the eNodeB through the X2 or S1 interface, and proceeds to the fourth step.
  • the eNodeB compares the updated locally saved center location offset identifier with the dynamic area range identifier. If the center location offset identifier is smaller than the dynamic area range identifier, the eNodeB determines that the eNodeB is in the dynamic service area, if the center location is biased If the move identifier is greater than or equal to the dynamic area range identifier, then the eNodeB is determined not to be in the dynamic service area.
  • the physical location of the service initiation terminal is monitored by identifying the service type, and the eNodeB adaptively dynamically adjusts the service area of the eMBMS.
  • the eNodeB adaptively dynamically adjusts the service area of the eMBMS.
  • the present embodiment facilitates the flexible deployment of the eMBMS, and allows the wireless resources to quickly switch between the multicast service and the non-multicast service, that is, meet the resource usage requirements of the burst hotspot, and avoid resource waste.
  • the eNodeB self-organizing dynamic area adjustment mode is also generally applicable to other application scenarios.
  • FIG. 3 is a flowchart of a method for managing an MBMS service area according to an embodiment of the present application. As shown in FIG. 3, the method for managing an MBMS service area provided by this embodiment includes the following steps S11-S12.
  • the first communication network element receives the first session establishment request carrying the dedicated MBMS identity.
  • the first communication network element determines whether it is in the service area of the dedicated MBMS indicated by the exclusive MBMS identifier according to the received location notification message or the first region decision message of the first communication network element.
  • the dedicated MBMS identifier is used to indicate that the dedicated MBMS of the service area is dynamically adjusted based on the physical location change of the service originating terminal.
  • the location notification message is used to indicate that the service originating terminal is currently within the coverage of the first communication network element.
  • the first region decision message may be used to indicate an interval between the first communication network element adjacent to the first communication network element and the service area center of the dedicated MBMS.
  • step S12 may include:
  • the first communication network element updates the locally saved area decision parameter according to the received location notification message, and determines whether it is in the service area of the exclusive MBMS according to the updated area decision parameter; or, the first communication network element receives the The first area decision message, the locally saved area decision parameter is updated, and the self-determined area decision parameter is used to determine whether it is in the service area of the exclusive MBMS, where the first area decision message carries the adjacent first communication network element.
  • the area decision parameter of the first communication network element is used to determine whether it is in the service area of the exclusive MBMS.
  • the region decision parameter may include at least: a dynamic region range identifier and a center location offset identifier.
  • the dynamic area range identifier is used to indicate the range of the service area of the dedicated MBMS, for example, the maximum interval of the service area boundary of the dedicated MBMS relative to the center of the service area may be indicated.
  • the central location offset identifier is used to indicate the spacing between the first communication network element and the service area center of the dedicated MBMS.
  • the first communication network element determines whether it is in the service area of the dedicated MBMS according to the updated area decision parameter, and may include: if the central location offset identifier saved locally by the first communication network element is smaller than dynamic The area-wide identifier determines that it is in the service area of the exclusive MBMS. If the central location offset identifier stored locally by the first communication network element is greater than or equal to the dynamic area range identifier, it is determined that it is not in the service area of the exclusive MBMS.
  • the first communication network element updates the locally saved area decision parameter according to the received location notification message, and may include: if the first communication network element receives the location notification message, the locally saved central location The offset flag is set to 0. Thus, it indicates that the first communication network element is at the center of the service area of the exclusive MBMS.
  • the first communication network element updates the locally saved area decision parameter according to the received first area decision message, which may include:
  • the locally saved center position offset identifier is updated to the first communication that is carried by the first communication network element carried in the received first area decision message.
  • the center position offset identifier in the area decision parameter of the network element.
  • the difference between the central location offset identifier carried in the first region decision message and the central location offset identifier locally saved by the adjacent first communication network element is 1.
  • the first communication network element can indicate the interval between itself and the service area center of the dedicated MBMS to the other adjacent first communication network element by using the first area decision message.
  • the method in this embodiment may further include:
  • the first communication network element broadcasts a second area decision message to the first communication network element that is adjacent to itself.
  • the central location offset identifier carried by the second regional decision message is equal to the central location offset identifier locally saved by the first communication network element plus one.
  • the method in this embodiment may further include:
  • the first communication network element broadcasts a second area determination message to the first communication network element that is adjacent to the first communication network element, where the central location offset identifier carried by the second area determination message is equal to the central location offset identifier locally saved by the first communication network element. plus 1.
  • the region decision parameter may further include: a serial number.
  • the method in this embodiment may further include:
  • the first communication network element adds the locally saved sequence number to 1 according to the received location communication message; or the first communication network element determines, according to the received first region decision message, the first regional decision message
  • the sequence number in the area decision parameter of the first communication network element that is adjacent to the first communication network element is equal to the sequence number in the local decision parameter stored in the local communication network element, and the first communication network element discards the received first area decision message.
  • the first communication network element may determine, by using the sequence number carried in the received first region decision message, whether the regional decision parameter carried in the received first region decision message is available, that is, whether to perform dynamic The adjustment process of the service area.
  • this application is not limited thereto. In other implementations, other elements may be set in the region decision parameters to implement the above functions.
  • the method in this embodiment may further include:
  • the first communication network element receives the exclusive MBMS identifier and the dynamic area range identifier; wherein the dynamic area range identifier is used to indicate the range of the service area of the exclusive MBMS.
  • the first communication network element receives the exclusive MBMS identifier and the dynamic area range identifier sent by the second communication network element in the registration phase, and then, in the service flow initiation phase, can identify whether the first session establishment request is Carry the exclusive MBMS logo.
  • the first communication network element may include an eNodeB.
  • this application is not limited thereto.
  • the first communication network element determines the dynamic service area in a self-organizing manner, and can be applied to a specific usage scenario and other application scenarios that the eMBMS service cannot be adapted.
  • FIG. 4 is a flowchart of a method for managing another MBMS service area according to an embodiment of the present application. As shown in FIG. 4, the method for managing an MBMS service area provided by this embodiment includes the following S21-S22.
  • the second communication network element receives the second session establishment request carrying the dedicated MBMS identity.
  • the dedicated MBMS identifier is used to indicate that the dedicated MBMS of the service area is dynamically adjusted based on the physical location change of the service originating terminal.
  • the second communication network element sends a first session establishment request carrying the exclusive MBMS identifier to the first communication network element.
  • the method of the embodiment may further include:
  • the second communication network element is configured with a dedicated MBMS identifier and a dynamic area range identifier, and reserves an independent multicast resource for the dedicated MBMS indicated by the dedicated MBMS identifier; wherein the dynamic area range identifier is used to indicate the range of the service area of the exclusive MBMS;
  • the second communication network element sends a dedicated MBMS identifier and a dynamic area range identifier to the first communication network element; the second communication network element sends a dedicated MBMS identifier to the third communication network element.
  • the second communication network element may be configured with a dedicated MBMS identifier and a dynamic area range identifier corresponding to the dedicated MBMS, and the dedicated MBMS identifier and the dynamic area range identifier are sent to the first communication network element, and the exclusive MBMS identifier is used. Send to the third communication network element.
  • the second communication network element sends the exclusive MBMS identifier and the dynamic area range identifier to the first communication network element, which may include:
  • the second communication network element sends the dedicated MBMS identifier and the dynamic area range identifier to the first communication network element by using the configuration message; or the second communication network element establishes a request response message by using the link connection for the first communication network element.
  • a communication network element sends a dedicated MBMS identity and a dynamic zone range identifier.
  • the second communication network element sends the exclusive MBMS identifier to the third communication network element, which may include:
  • the second communication network element sends a dedicated MBMS identifier to the third communication network element through a separate message; or the second communication network element sends a dedicated MBMS identifier to the third communication network element through the link connection establishment message.
  • the first communication network element may include an eNodeB
  • the second communication network element may include an MCE
  • the third communication network element may include an MME.
  • this application is not limited thereto.
  • FIG. 5 is a flowchart of a method for managing another MBMS service area according to an embodiment of the present application. As shown in FIG. 5, the method for managing an MBMS service area provided by this embodiment includes the following S31-S32.
  • the third communication network element monitors the first communication network element where the service originating terminal of the dedicated MBMS is located when detecting the dedicated MBMS that dynamically adjusts the service area based on the physical location change of the service initiating terminal.
  • the third communication network element when the third communication network element receives the third session establishment request that carries the dedicated MBMS identity, or the first communication network element where the service initiation terminal is located is switched, the third communication network element sends the current service to the service initiation terminal.
  • the first communication network element where the location is sent sends a location notification message.
  • the dedicated MBMS identifier is used to indicate the exclusive MBMS, and the location notification message is used to indicate that the service originating terminal is currently in the coverage of the first communication network element.
  • the third communication network element detecting the exclusive MBMS may include:
  • the third communication network element detects that the quality of service level identifier (QCI) of a data link is in the dedicated QCI, it confirms that the service carried by the data link is in the exclusive MBMS.
  • QCI quality of service level identifier
  • the method of this embodiment may further include: the third communication network element receives the exclusive MBMS identity.
  • the third communication network element receives the exclusive MBMS identifier configured by the second communication network element from the second communication network element.
  • the first communication network element may include an eNodeB
  • the second communication network element may include an MCE
  • the third communication network element may include an MME.
  • this application is not limited thereto.
  • the third communication network element keeps track of the eNodeB where the service initiating terminal is located, and may send a location notification message to the eNodeB where the service initiating terminal is currently located, to inform the eNodeB that the eNodeB is currently providing radio access to the service initiating terminal.
  • FIG. 6 is a flowchart of a method for managing another MBMS service area according to an embodiment of the present application. As shown in FIG. 6, the method for managing an MBMS service area provided by this embodiment includes the following S41-S42.
  • the service originating terminal applies for a data link.
  • the service initiating terminal sends the data carrying the dedicated service identifier through the data link.
  • the dedicated service identifier is used to indicate that the dedicated MBMS of the service area is dynamically adjusted based on the physical location change of the service initiating terminal, and the corresponding service identifier has a corresponding relationship with the dedicated MBMS identifier.
  • S41 may include: the service originating terminal adopts a dedicated QCI application data link.
  • the exclusive QCI can be an extended QCI that is independent of the standard protocol.
  • the terminal when the terminal initiates the dedicated MBMS service, the terminal carries the dedicated service identifier, which is used to indicate the service type to the service server, so that the service server performs the processing corresponding to the service type.
  • FIG. 7 is a flowchart of a method for managing another MBMS service area according to an embodiment of the present application. As shown in FIG. 7, the method for managing an MBMS service area provided by this embodiment includes the following S51-S52.
  • the service server receives data carrying a dedicated service identifier.
  • the dedicated service identifier is used to indicate that the dedicated MBMS of the service area is dynamically adjusted based on the physical location change of the service originating terminal.
  • the service server determines a dedicated MBMS identifier corresponding to the dedicated service identifier according to the dedicated service identifier, and triggers a session establishment process.
  • triggering the session establishment process may include:
  • the service server sends a session establishment request to the broadcast multicast service center (BM-SC), where the session establishment request carries the received data, the dedicated MBMS identifier, and the routing information corresponding to the dedicated MBMS identifier.
  • BM-SC broadcast multicast service center
  • This embodiment illustrates the implementation process of the registration phase.
  • the second communication network element (MCE in this example) sends the relevant identity to the first communication network element (eNodeB in this example) and the third communication network element (MME in this example) for service initiation Instant identification and tracking.
  • the registration phase of this embodiment includes the following processes S101-S106.
  • the MCE sets a dedicated MBMS ID, and the exclusive MBMS ID corresponds to a dedicated MBMS, and the service area of the dedicated MBMS dynamically changes based on the physical location of the service initiating terminal.
  • the MCE sets a dynamic area range identifier, where the dynamic area range identifier indicates a range of the service area of the exclusive MBMS.
  • the eNodeB that provides the wireless access to the service initiating terminal is the center of the dynamic service area
  • the dynamic area range identifier may indicate the maximum interval (in units of cells) of the service area boundary of the dedicated MBMS with respect to the center of the service area.
  • the MCE sets a radio resource related to the exclusive MBMS ID.
  • the radio resource may include one or more subframes that are fixed in position.
  • the radio resources are relatively independent of the radio resources of other multicast services, and are scheduled when the service corresponding to the dedicated MBMS ID is initiated. Will be occupied by other multicast services.
  • the MCE reports the exclusive MBMS ID to the MME, where the MME determines whether the service has been initiated, and whether the subsequent location notification process is performed.
  • the MCE sends the dedicated MBMS ID and the dynamic area range identifier to the eNodeB, and is used by the eNodeB to determine whether the initiated multicast service is in the eMBMS service that needs to generate the dynamic service area, and whether it is within the dynamic service area.
  • the cluster service server sets a dedicated MBMS ID and routing information supporting the dedicated MBMS ID.
  • the BM-SC is instructed to provide a correct route for the user plane data stream.
  • S104 may be performed after S103
  • S105 may be performed after S103
  • S106 may be performed before S101 or simultaneously with S101.
  • the service process initiation phase includes an uplink service that the service initiating terminal sends the user plane data stream to the cluster server, and the downlink broadcast service that the cluster server distributes the user plane data stream by using the eMBMS multicast technology.
  • the overall service initiation process may include uplink and downlink services, which are implemented on the basis of the Long Term Evolution (LTE) standard service flow, and introduce mechanisms such as service identification, location detection, location notification, and regional decision.
  • LTE Long Term Evolution
  • the execution process of this embodiment is as follows S201-S216.
  • the terminal initiates a dedicated cluster service, and writes the dedicated service identifier into the user plane data packet.
  • the pre-negotiated dedicated QCI is used to distinguish it from the ordinary dedicated service bearer.
  • the MME when the MME detects that a certain bearer link QCI is in a dedicated QCI, and confirms that the service corresponding to the link bearer is in the dynamic area eMBMS service based on the service originating terminal location, the MME is started to monitor the MME;
  • the physical identifier (such as the IP address) of the bearer eNodeB and its changes are tracked and recorded in real time to monitor which eNodeB coverage the service originating terminal is currently in.
  • the cluster service server determines that the service is in the eMBMS service based on the location of the service originating terminal, that is, the corresponding service of the exclusive MBMS ID, according to the dedicated service identifier reported by the terminal.
  • the cluster service server searches for the routing information corresponding to the dedicated MBMS ID, and sends the received user plane data stream, routing information, and the dedicated MBMS ID to the BM-SC to trigger the eMBMS session establishment process.
  • the BM-SC sends a session establishment request to the corresponding MBMS-GW according to the routing information.
  • This process belongs to the standard eMBMS session establishment procedure, except that the dedicated MBMS ID is carried.
  • the MBMS-GW transmits a session establishment response message to the BM-SC.
  • the MBMS-GW sends a session establishment request (corresponding to the third session establishment request) to the corresponding MME according to the routing information.
  • This process belongs to a standard eMBMS session establishment procedure, except that the exclusive MBMS ID is carried.
  • the MME when the MME receives the session establishment request that carries the exclusive MBMS ID from the MBMS-GW, the MME sends a location notification message to the eNodeB where the current service originating terminal is located, according to the location monitoring record of the service originating terminal, for notifying the MME.
  • the eNodeB is providing radio access to the service initiating terminal; when the service initiating terminal is handed over, the MME may send a location notification message to the new eNodeB that is providing the radio access according to the change of the location monitoring record until the service initiating terminal The business bearers are removed.
  • the MME sends a session establishment request (corresponding to the foregoing second session establishment request) to the corresponding MCE according to the routing information.
  • This process belongs to a standard eMBMS session establishment procedure, except that the dedicated MBMS ID is carried.
  • the MCE sends a session establishment response message to the MME.
  • the MME transmits a session establishment response message to the MBMS-GW.
  • the MCE when the MCE receives the session establishment request (corresponding to the second session establishment request described above) that carries the exclusive MBMS ID from the MME, it determines that the service type is the eMBMS service based on the location of the service originating terminal, and is reserved.
  • the scheduling information is configured on the dedicated multicast resource, and the session establishment request (corresponding to the first session establishment request described above) and the scheduling information are sent to the corresponding eNodeB; the process is similar to the standard MCE processing flow, except that the resource scheduling is specific to the dedicated Multicast subframes instead of all multicast subframes.
  • the eNodeB sends a session establishment response message.
  • the eNodeB transmits a scheduling information response message.
  • the eNodeB After the eNodeB receives the session connection request (corresponding to the first session establishment request described above) carrying the exclusive MBMS ID from the MCE, and the corresponding scheduling information, the eNodeB first needs to confirm whether it is in the dynamic service area.
  • the eNodeB When an eNodeB decides that it is not in the dynamic service area, the eNodeB only saves the relevant configuration information delivered by the MCE, and schedules its corresponding radio resource according to the mode of the non-multicast subframe; when an eNodeB decides that it is in dynamic When the service area is in the range, the subsequent standard session establishment process is performed, that is, the MBMS Control Channel (MCCH) notification and the related MBSFN configuration parameters are delivered, and the multicast group IP is officially added to perform the corresponding radio resource location. Multicast business.
  • MCCH MBMS Control Channel
  • This embodiment describes a process of confirming whether the eNodeB is in a dynamic service area after receiving a location notification message sent by the MME or an area decision message sent by another eNodeB.
  • each eNodeB saves a region decision parameter, and the region decision parameter includes the following three elements: a dynamic region range identifier, a center location offset identifier, and a sequence number.
  • the dynamic area range identifier is received from the MCE and stored directly in the local area.
  • the central location offset identifier is maintained by the eNodeB.
  • the initialization value is the same as the dynamic area range identifier.
  • the serial number is maintained by the eNodeB and the initialization value is all 0s.
  • the process of this embodiment includes the following S301-S308.
  • the eNodeB determines whether a location notification message from the MME is received; if yes, executes S302, otherwise, executes S305.
  • the eNodeB increments the locally saved sequence number by one and sets the locally saved center position offset flag to zero.
  • the eNodeB adds 1 to the locally saved central location offset identifier, and together with the updated sequence number, forms an area decision message (corresponding to the second region decision message described above), and then, through the X2 or S1 interface, The area decision message is sent to all contiguous eNodeBs of the eNodeB; thereafter, S304 is performed.
  • the eNodeB compares the central location offset identifier with the dynamic area range identifier; if the central location offset identifier is smaller than the dynamic area range identifier, it determines that it is in the dynamic service area, and starts the service; if the central location offset identifier If it is greater than or equal to the dynamic area range identifier, it is determined that it is not in the dynamic service area and the service is stopped.
  • the eNodeB determines whether to receive an area decision message from the eNodeB that is adjacent to itself (corresponding to the first area decision message described above); if yes, execute S306, otherwise the eNodeB determines that it is not in the service area of the dedicated service. , stop the business.
  • the eNodeB determines whether the sequence number carried in the received area decision message is the same as the value of the locally saved sequence number; if they are the same, the received area decision message is directly ignored, and the process ends; otherwise, S307 is performed.
  • the eNodeB saves the sequence number and the central location offset identifier carried in the received area decision message to the local. In this step, the eNodeB updates the locally saved sequence number and the central location offset identifier to the sequence number and the central location offset identifier carried in the received regional decision message.
  • the eNodeB determines whether the central location offset identifier carried in the received region determination message is the same as the value of the locally saved dynamic region range identifier; if the same, the process proceeds to S304; otherwise, the S303 is performed, that is, the center location is biased. After the offset flag is incremented by 1, it forms an area decision message (corresponding to the above-mentioned second area decision message) together with the sequence number, and then transmits the area decision message to all the adjacent eNodeBs of the eNodeB through the X2 or S1 interface.
  • This embodiment illustrates the execution process of each eNodeB generating a dynamic service area for the first time in an initial state.
  • each eNodeB saves a region decision parameter, and the region decision parameter includes the following three elements: a dynamic region range identifier, a center location offset identifier, and a sequence number.
  • the dynamic area range identifier is received from the MCE and stored locally.
  • the initial value is 3.
  • the center position offset identifier is maintained by the eNodeB.
  • the initialization value is the same as the dynamic area range identifier.
  • the serial number is determined by the eNodeB. Self-maintained, the initialization value is all 0. That is, in this embodiment, the initial region decision parameter of each eNodeB is (3, 30000).
  • the coverage of the eNodeB is simplified to linear coverage. This application is not limited thereto. This embodiment is also applicable to the eNodeB mesh overlay.
  • the implementation process of this embodiment is as follows from the first step to the fourteenth step.
  • an eNodeB receives a location notification message from the MME, confirming that it is in the center of the dynamic eMBMS area, and the eNodeB is hereinafter referred to as a central eNodeB.
  • the central eNodeB sets the central location offset identifier of the local record to 0, adds the sequence number of the local record to 1, and saves it locally; that is, the local eNodeB updates the locally determined region decision parameter to be (3, 0, 0001).
  • the central eNodeB constructs a regional decision message, and the result of the construction is (1,0001), and the regional decision message is broadcasted to all neighboring eNodeBs of the central eNodeB through the S1 or X2 link.
  • the central eNodeB determines that the center location offset identifier (where the value is 0) is smaller than the dynamic area range identifier (where the value is 3) and is in the dynamic service area.
  • the central eNodeB is named as the central node.
  • the eNodeB that receives the regional decision message from the central node determines that the sequence number carried by the received regional decision message is inconsistent with the locally saved sequence number, and saves the received sequence number and the central location offset identifier, and locally updates.
  • the subsequent regional decision parameter is (3,1,0001).
  • the eNodeB that receives the regional decision message from the central node determines that the updated central location offset identifier (where the value is 1) is not equal to the dynamic region range identifier (where the value is 3), and the regional decision is constructed.
  • the message, the result of the construction is (2,0001), and the constructed region decision message is broadcast to all neighboring eNodeBs of the eNodeB through the S1 or X2 link.
  • the eNodeB that receives the regional decision message from the central node determines that the updated central location offset identifier (where the value is 1) is smaller than the dynamic region range identifier (where the value is 3), that is, in the dynamic service area.
  • the eNodeB that receives the regional decision message from the central node is named as a primary node.
  • the central node receives the regional decision message from the first-level node, and determines that the sequence number carried in the received regional decision message is the same as the locally saved sequence number, and is not processed, and the received regional decision message is discarded.
  • the eNodeB that receives the regional decision message from the first-level node determines that the sequence number carried in the received regional decision message is inconsistent with the locally saved sequence number, and saves the sequence number carried in the received regional decision message.
  • the center position offset identifier, and the locally updated region decision parameter is (3, 20001).
  • Step 10 The eNodeB that receives the regional decision message from the primary node determines that the updated central location offset identifier is not equal to the dynamic regional scope identifier, and then constructs a regional decision message, and the construction result is (3,0001).
  • the eNodeB to the regional decision message from the primary node broadcasts the constructed regional decision message to all of the neighboring eNodeBs of the eNodeB over the S1 or X2 link.
  • the eNodeB decision that receives the regional decision message from the first-level node is updated, and the central location offset identifier (where the value is 2) is smaller than the dynamic region range identifier (where the value is 3), that is, the dynamic The service area; in this embodiment, the eNodeB that receives the area decision message from the primary node is named as a secondary node.
  • the first-level node receives the regional decision message from the secondary node, and determines that the sequence number carried in the received regional decision message is the same as the locally saved sequence number, and is not processed, and the received regional decision message is discarded.
  • the eNodeB that receives the regional decision message from the secondary node determines that the sequence number carried in the received regional decision message is inconsistent with the locally saved sequence number, and saves the sequence number carried in the received regional decision message.
  • the center position offset identifier, the local updated region decision parameter is (3, 30001).
  • the updated central location offset identifier of the eNodeB that receives the regional decision message from the secondary node is equal to the dynamic regional range identifier, and the regional determination message is no longer broadcasted to the neighboring eNodeB, and the updated center is determined.
  • the location offset identifier (where the value is 3) is equal to the dynamic zone range identifier (where the value is 3), ie it is not in the dynamic service area.
  • This embodiment describes an execution process of generating a dynamic service area after each eNodeB performs a handover on the service originating terminal. After receiving the location notification message, the eNodeB gradually confirms and finally determines the boundary of the dynamic service area, the new eNodeB is included in the dynamic service area, and the old eNodeB exits the dynamic service area.
  • each eNodeB saves the area decision parameter, and the area decision parameter includes the following three elements: a dynamic area range identifier, a center position offset identifier, and a sequence number; wherein the dynamic area range identifier is received from the MCE, directly It is saved locally.
  • the initial value is 3.
  • the center position offset identifier is maintained by the eNodeB.
  • the initialization value is the same as the dynamic area range identifier.
  • the serial number is maintained by the eNodeB and the initialization value is all 0s.
  • the coverage of the eNodeB is simplified to linear coverage. This application is not limited thereto. This embodiment is also applicable to the eNodeB mesh overlay.
  • the implementation process of this embodiment is as follows from the first step to the fourteenth step.
  • the original primary node receives the location notification message from the MME, and confirms that it is in the center of the dynamic eMBMS region; the eNodeB is hereinafter referred to as the central eNodeB.
  • the central eNodeB sets the central location offset identifier of the local record to 0, adds the sequence number of the local record to 1, and saves it locally; that is, the local eNodeB updates the locally determined region decision parameter to be (3, 0, Xxx2).
  • the central eNodeB constructs a regional decision message, and the result of the construction is (1, xxx2), and the regional decision message is broadcasted to all neighboring eNodeBs of the central eNodeB through the S1 or X2 link.
  • the central eNodeB determines that the center eNodeB is located in the dynamic service area.
  • the central eNodeB is named as the central node. .
  • the eNodeB that receives the regional decision message from the central node determines that the sequence number carried by the received regional decision message is inconsistent with the locally saved sequence number, and saves the received sequence number and the central location offset identifier, and locally updates.
  • the subsequent regional decision parameters are (3, 1, xxx2).
  • the eNodeB that receives the regional decision message from the central node determines that the updated central location offset identifier (where the value is 1) is not equal to the dynamic region range identifier (where the value is 3), and the regional decision is constructed.
  • the message, the result of the construction is (2, xxx2), and the constructed region decision message is broadcast to all neighboring eNodeBs of the eNodeB through the S1 or X2 link.
  • the eNodeB that receives the regional decision message from the central node determines that the updated central location offset identifier (where the value is 1) is smaller than the dynamic region range identifier (where the value is 3), that is, in the dynamic service area.
  • the eNodeB that receives the regional decision message from the central node is named as a primary node; as shown in FIG. 12, after the handover occurs, one original central node and one original secondary node are updated to one level. node.
  • the central node receives the regional decision message from the first-level node, and determines that the sequence number carried in the received regional decision message is the same as the locally saved sequence number, and is not processed, and the received regional decision message is discarded.
  • the eNodeB that receives the regional decision message from the first-level node determines that the sequence number carried in the received regional decision message is inconsistent with the locally saved sequence number, and saves the received sequence number and the central location offset identifier.
  • the local decision parameter after local update is (3, 2, xxx2).
  • the eNodeB decision to receive the regional decision message from the first-level node is updated, and the central location offset identifier (where the value is 2) is not equal to the dynamic region range identifier (where the value is 3), and the construction region is
  • the decision message is constructed with (3, xxx2) and the constructed region decision message is broadcast to all neighboring eNodeBs of the eNodeB through the S1 or X2 link.
  • the eNodeB decision that receives the regional decision message from the first-level node is updated, and the central location offset identifier (where the value is 2) is smaller than the dynamic region range identifier (where the value is 3), that is, the dynamic
  • the eNodeB that receives the regional decision message from the primary node is named as a secondary node; as shown in FIG. 12, after the handover occurs, an original primary node is updated to a secondary node; A node that is not in the dynamic service area joins the dynamic service area as a secondary node.
  • the first-level node receives the regional decision message from the secondary node, and determines that the sequence number carried in the received regional decision message is the same as the locally saved sequence number, and is not processed, and the received regional decision message is discarded.
  • the eNodeB that receives the regional decision message from the secondary node determines that the sequence number carried in the received regional decision message is inconsistent with the locally saved sequence number, and saves the received serial number and the central location offset identifier.
  • the local decision parameter of the local update is (3, 3, xxx2).
  • the updated central location offset identifier of the eNodeB that receives the regional decision message from the secondary node is equal to the dynamic regional range identifier, and the regional determination message is no longer broadcasted to the neighboring eNodeB, and the updated center is determined.
  • the position offset identifier (where the value is 3) is equal to the dynamic area range identifier (where the value is 3), that is, it is not in the dynamic service area; as shown in Figure 12, after the switchover occurs, an original secondary node exits the dynamic Service Area.
  • FIG. 13 is a schematic diagram of an apparatus for managing an MBMS service area according to an embodiment of the present application.
  • the management apparatus of the MBMS service area provided in this embodiment is applied to a first communication network element (for example, an eNodeB), and includes: a first receiving module 101 and a first processing module 102.
  • a first communication network element for example, an eNodeB
  • the first receiving module 101 is configured to receive a first session establishment request that carries a dedicated MBMS identifier, where the dedicated MBMS identifier is used to indicate that the dedicated MBMS of the service area is dynamically adjusted based on the physical location change of the service initiating terminal.
  • the first processing module 102 is configured to determine, according to the received location notification message or the first region decision message, whether the first communication network element is located in a service area of the dedicated MBMS.
  • the location notification message is used to indicate that the service initiation terminal is currently in the coverage of the first communication network element.
  • the first processing module 102 may be configured to determine, according to the received location notification message or the first region determination message, whether the first communication network element is in the service area of the dedicated MBMS: Receiving the location notification message, updating the locally saved region decision parameter, and determining, according to the updated region decision parameter, whether the first communication network element is in the service area of the exclusive MBMS; or
  • the first area decision message carries the first communication network The region decision parameter of the first communication network element adjacent to the element.
  • the area decision parameter may include at least: a dynamic area range identifier and a center position offset identifier; wherein the dynamic area range identifier is used to indicate a range of the service area of the exclusive MBMS; the center position offset identifier is used to indicate The interval between the first communication network element and the service area center of the dedicated MBMS.
  • the first processing module 102 may be configured to determine, according to the updated region decision parameter, whether the first communication network element is in the service area of the dedicated MBMS: if the first communication network element is local If the saved central location offset identifier is smaller than the dynamic area range identifier, the first communication network element is determined to be in the service area of the dedicated MBMS; if the central location offset identifier locally saved by the first communication network element is greater than or equal to the dynamic area range identifier And determining that the first communication network element is not in the service area of the dedicated MBMS.
  • the management apparatus may further include: a first sending module.
  • the first sending module is configured to broadcast a second area determination message to the first communication network element adjacent to the first communication network element according to the received location notification message.
  • the first sending module is configured to: according to the received first area decision message, confirm that the central location offset identifier carried by the first region determination message is not equal to the locally saved dynamic area range identifier, and then the first communication to the neighboring The network element broadcasts the second regional decision message.
  • the central location offset identifier carried by the second regional decision message is equal to the central location offset identifier locally saved by the first communication network element where the location is located.
  • FIG. 14 is a schematic diagram of another apparatus for managing an MBMS service area according to an embodiment of the present application.
  • the management apparatus of the MBMS service area provided in this embodiment is applied to a second communication network element (for example, an MCE), and includes: a second receiving module 201 and a second sending module 202.
  • a second communication network element for example, an MCE
  • the second receiving module 201 is configured to receive a second session establishment request that carries a dedicated MBMS identifier, where the dedicated MBMS identifier is used to indicate that the dedicated MBMS of the service area is dynamically adjusted based on the physical location change of the service initiating terminal;
  • the second sending module 202 is configured to send a first session establishment request carrying the dedicated MBMS identifier to the first communication network element.
  • the management apparatus may further include: a configuration module.
  • the configuration module is configured to configure a dedicated MBMS identifier and a dynamic area range identifier, and reserve an independent multicast resource for the dedicated MBMS indicated by the dedicated MBMS identifier; wherein the dynamic area range identifier is used to indicate the range of the service area of the exclusive MBMS;
  • the second sending module 202 is further configured to send a dedicated MBMS identifier and a dynamic area range identifier to the first communication network element, and send a dedicated MBMS identifier to the third communication network element.
  • FIG. 15 is a schematic diagram of an apparatus for managing an MBMS service area according to an embodiment of the present application.
  • the management apparatus of the MBMS service area provided in this embodiment is applied to a third communication network element (for example, an MME), and includes: a monitoring module 301 and a second sending module 302.
  • a third communication network element for example, an MME
  • the monitoring module 301 is configured to monitor the first communication network element where the service originating terminal of the dedicated MBMS is located when detecting the dedicated MBMS that dynamically adjusts the service area based on the physical location change of the service initiating terminal.
  • the second sending module 302 is configured to: according to the received third session establishment request that carries the dedicated MBMS identifier, or the first communication that the service originating terminal is currently located according to the handover of the first communication network element where the service originating terminal is located The network element sends a location notification message.
  • the dedicated MBMS identifier is used to indicate the exclusive MBMS, and the location notification message is used to indicate that the service originating terminal is currently in the coverage of the first communication network element.
  • the management apparatus provided in this embodiment may further include: a third receiving module.
  • the third receiving module is configured to receive the exclusive MBMS identifier.
  • FIG. 16 is a schematic diagram of an apparatus for managing an MBMS service area according to an embodiment of the present application.
  • the management apparatus of the MBMS service area provided in this embodiment is applied to the service originating terminal, and includes: a second processing module 401 and a fourth sending module 402.
  • the second processing module 401 is configured to apply for a data link
  • the fourth sending module 402 is configured to send data carrying the dedicated service identifier through the data link, where the dedicated service identifier is used to indicate that the dedicated MBMS of the service area is dynamically adjusted based on the physical location change of the service initiating terminal, and the dedicated service identifier is There is a correspondence between the exclusive MBMS identifiers.
  • the second processing module 401 can be configured to apply for a data link by employing a proprietary QCI application data link.
  • FIG. 17 is a schematic diagram of an apparatus for managing an MBMS service area according to an embodiment of the present application.
  • the management apparatus of the MBMS service area provided in this embodiment is applied to a service server (for example, an MCPTT server), and includes: a fourth receiving module 501 and a third processing module 502.
  • the fourth receiving module 501 is configured to receive data carrying a dedicated service identifier, where the dedicated service identifier is used to indicate that the dedicated MBMS of the service area is dynamically adjusted based on the physical location change of the service initiating terminal.
  • the third processing module 502 is configured to determine, according to the dedicated service identifier, a dedicated MBMS identifier corresponding to the dedicated service identifier, and trigger a session establishment process.
  • the third processing module 502 can trigger the session establishment process by the third processing module 502 to send a fourth session establishment request to the BM-SC, where the fourth session establishment request carries the received data, The routing information corresponding to the exclusive MBMS identifier and the exclusive MBMS identifier.
  • FIG. 18 is a schematic diagram of a first communication network element according to an embodiment of the present application.
  • the first communication network element 1000 eg, eNodeB
  • the first communication network element 1000 includes: a first memory 1001 and a first processor 1002, where the first memory 1001 is configured to store a management program of the MBMS service area;
  • the management program is executed by the first processor 1002, the management method of the first communication network element side provided by the foregoing embodiment is implemented.
  • the first processor 1002 may include, but is not limited to, a processing device such as a Micro Controller Unit (MCU) or a Field Programmable Gate Array (FPGA).
  • the first memory 1001 may be configured as a software program and a module for storing application software, such as program instructions or modules corresponding to the management method in the embodiment, and the first processor 1002 runs the software program and the module stored in the first memory 1001. Thus, various functional applications and data processing are performed, such as implementing the management method provided by the embodiment.
  • the first memory 1001 can include a high speed random access memory, and can also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory.
  • the first memory 1001 can include memory remotely located relative to the first processor 1002, which can be connected to the first communication network element 1000 via a network.
  • networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • the first communication network element 1000 can also include a first communication unit 1003; the first communication unit 1003 can receive or transmit data via a network.
  • the first communication unit 1003 can be a Radio Frequency (RF) module for communicating with the Internet wirelessly.
  • RF Radio Frequency
  • FIG. 19 is a schematic diagram of a second communication network element according to an embodiment of the present application.
  • the second communication network element 2000 eg, MCE
  • the second communication network element 2000 includes: a second memory 2001 and a second processor 2002, where the second memory 2001 is configured to store a management program of the MBMS service area;
  • the management program is executed by the second processor 2002, the management method of the second communication network element side provided by the foregoing embodiment is implemented.
  • the second communication network element 2000 can also include a second communication unit 2003.
  • FIG. 20 is a schematic diagram of a third communication network element according to an embodiment of the present application.
  • the third communication network element 3000 (for example, MME) provided in this embodiment includes: a third memory 3001 and a third processor 3002, where the third memory 3001 is configured to store a management program of the MBMS service area; When the management program is executed by the third processor 3002, the management method of the third communication network element side provided by the foregoing embodiment is implemented.
  • the third communication network element 3000 may further include a third communication unit 3003.
  • FIG. 21 is a schematic diagram of a terminal according to an embodiment of the present application.
  • the terminal 4000 provided in this embodiment includes: a memory 4001 and a processor 4002.
  • the memory 4001 is configured to store a management program of an MBMS service area.
  • the management program is executed by the processor 4002, the foregoing embodiment is implemented. Terminal side management method.
  • the terminal 4000 may further include a fourth communication unit 4003.
  • FIG. 22 is a schematic diagram of a service server according to an embodiment of the present application.
  • the service server 5000 provided in this embodiment includes: a memory 5001 and a processor 5002.
  • the memory 5001 is configured as a management program for storing an MBMS service area.
  • the management program is executed by the processor 5002, the foregoing embodiment is implemented.
  • the service server 5000 can also include a communication unit 5003.
  • the embodiment of the present application further provides a computer readable storage medium, where a management program of an MBMS service area is stored, and when the management program is executed by the processor, the management method provided by any one of the embodiments corresponding to FIG. 3 to FIG. 7 is implemented. step.
  • computer storage medium includes volatile and nonvolatile, implemented in any method or technology for storing information, such as computer readable instructions, data structures, program modules or other data. Sex, removable and non-removable media.
  • Computer storage media include, but are not limited to, Random Access Memory (RAM), Read-Only Memory (ROM), and Electrically Erasable Programmable Read Only Memory (EEPROM). , flash memory or other memory technology, Compact Disc Read-Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical disc storage, magnetic box, magnetic tape, disk storage or other magnetic storage A device, or any other medium that can be used to store desired information and that can be accessed by a computer.
  • communication media typically includes computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and can include any information delivery media. .
  • the MBMS service area management method and system provided by the present disclosure can implement an MBMS service area that is dynamically adjusted based on a physical location change of a service originating terminal.

Landscapes

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

Abstract

公开了一种MBMS服务区域的管理方法，包括：第一通信网元接收携带专属MBMS标识的第一会话建立请求，根据接收到的位置通知消息或者第一区域判决消息后，确定所述第一通信网元是否处于专属MBMS标识指示的专属MBMS的服务区域内；其中，专属MBMS标识用于指示基于业务发起终端的物理位置变化动态调整服务区域的专属MBMS；位置通知消息用于指示业务发起终端当前处于该第一通信网元的覆盖范围内。

Description

MBMS服务区域的管理方法及系统 技术领域
本公开涉及通信技术领域，例如涉及一种多媒体广播多播业务(Multimedia Broadcast Multicast Service，MBMS)服务区域的管理方法及系统。
背景技术
第四代移动通信长期演进(Long Term Evolution，LTE)系统中引入增强的多媒体广播多播业务(enhanced Multimedia Broadcast Multicast Service，eMBMS)，在基于正交频分复用(Orthogonal Frequency Division Multiplexing，OFDM)调制方式的前提下，提供了一种点对多点的广播信道，适用于具有视频功能的终端通过物理多播信道(Physical Multicasts Channel，PMCH)接收广播或组播形式的数字音频或视频业务。
随着无线通信技术的发展，eMBMS技术的应用需求逐渐向公共安全技术、集群通信、物联网、车联网等领域不断延伸，点对多点的广播信道业务模式受到重视。其中，第三代合作伙伴计划(Third Generation Partnership Project，3GPP)基于公共安全技术领域提出的关键任务一键通(Mission-critical push-to-talk，MCPTT)架构，更是明确使用eMBMS作为无线侧的技术方案。可以预见，在不远将来，eMBMS技术将在公共安全集群领域扮演重要的角色，给例如公安、消防、铁路、应急救灾等场景提供满足业务需求的集群服务。
在目前的协议中，eMBMS的业务覆盖范围是根据MBMS服务区域多播组播单频网络区域(MBSFN Area，MA)开展的。某项业务只能在其对应的一个或者多个MA内开展，即在对应的物理空间内开展。目前eMBMS支持较为灵活的MA配置，MA的覆盖范围可大可小，也可以通过后台自由调整，但是MA的配置方式始终是静态或者半静态的，导致无法适应某些使用场景的需求。
发明内容
本申请实施例提供一种MBMS服务区域的管理方法及系统，能够实现基于业务发起终端的物理位置变化而动态调整的MBMS服务区域。
本申请实施例提供一种MBMS服务区域的管理方法，包括：
第一通信网元接收携带专属MBMS标识的第一会话建立请求，所述第一通信网元根据接收到的位置通知消息或者第一区域判决消息，确定所述第一通信网元是否处于所述专属MBMS标识指示的专属MBSM的服务区域内；
其中，所述专属MBMS标识用于指示基于业务发起终端的物理位置变化而动态调整服务区域的专属MBMS；所述位置通知消息用于指示所述业务发起终端当前处于所述第一通信网元的覆盖范围内。
本申请实施例提供一种MBMS服务区域的管理方法，包括：
第二通信网元接收携带专属MBMS标识的第二会话建立请求；其中，所述专属MBMS标识用于指示基于业务发起终端的物理位置变化动态调整服务区域的专属MBMS；
所述第二通信网元向第一通信网元发送携带所述专属MBMS标识的第一会话建立请求。
本申请实施例提供一种MBMS服务区域的管理方法，包括：
第二通信网元在检测到基于业务发起终端的物理位置变化动态调整服务区域的专属MBMS时，监测所述专属MBMS的业务发起终端所在的第一通信网元；
在所述第二通信网元接收到携带专属MBMS标识的会话建立请求，或者，所述业务发起终端所在的第一通信网元发生切换时，所述第二通信网元向所述业务发起终端当前所在的第一通信网元发送位置通知消息；
其中，所述专属MBMS标识用于指示所述专属MBMS，所述位置通知消息用于指示所述业务发起终端当前处于所述第一通信网元的覆盖范围内。
本申请实施例提供一种MBMS服务区域的管理方法，包括：
业务发起终端申请数据链路；
所述业务发起终端通过所述数据链路发送携带专属业务标识的数据；其中，所述专属业务标识用于指示基于所述业务发起终端的物理位置变化动态调整服务区域的专属MBMS，所述专属业务标识与专属MBMS标识之间存在对应关系。
本申请实施例提供一种MBMS服务区域的管理方法，包括：
业务服务器接收携带专属业务标识的数据；其中，所述专属业务标识用于指示基于业务发起终端的物理位置变化动态调整服务区域的专属MBMS；
所述业务服务器根据所述专属业务标识，确定与所述专属业务标识对应的专属MBMS标识，触发会话建立流程。
本申请实施例提供一种MBMS服务区域的管理系统，包括：第一通信网元以及第二通信网元；所述第一通信网元连接所述第二通信网元；
其中，所述第二通信网元设置为向所述第一通信网元发送携带专属MBMS标识的第一会话建立请求；
所述第一通信网元设置为接收所述第一会话建立请求，根据接收到的位置通知消息或者第一区域判决消息，确定所述第一通信网元是否处于所述专属MBMS标识指示的专属MBMS的服务区域内；
其中，所述专属MBMS标识用于指示基于业务发起终端的物理位置变化动态调整服务区域的专属MBMS；所述位置通知消息用于指示所述业务发起终端当前处于所述第一通信网元的覆盖范围内。
本申请实施例提供一种通信网元，包括：存储器以及处理器，所述存储器设置为存储MBMS服务区域的管理程序，所述管理程序被所述处理器执行时实现上述提供的管理方法。
本申请实施例提供一种终端，包括：存储器以及处理器，所述存储器设置为存储MBMS服务区域的管理程序，所述管理程序被所述处理器执行时实现上述应用于终端任一项的管理方法。
本申请实施例提供一种业务服务器，包括：存储器以及处理器，所述存储器设置为存储MBMS服务区域的管理程序，所述管理程序被所述处理器执行时实现上述应用于业务服务器任一项的管理方法。
本申请实施例还提供一种计算机可读介质，存储有MBMS服务区域的管理程序，该管理程序被处理器执行时实现上述任一项所述的管理方法。
本申请实施例中，在保持了当前协议的多播业务发起流程的基础上，通过识别业务类型，监测业务发起终端的物理位置，由第一通信网元(比如，基站)自适应动态调整MBMS服务区域。本申请实施例在使用前景上，弥补了当前eMBMS业务无法适配特定使用场景的局限，适用于基于MCPTT的公共安全领域各类场景，例如铁路调度、灾难预警、视频监控等。而且，本申请实施例便于eMBMS的灵活部署，允许无线资源迅速地在多播业务与非多播业务之间快速转换，即满足突发热点的资源使用要求，又避免资源浪费。另外，第一通信网元自组织的动态服务区域调整模式，也普遍适用于其他应用场景。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图说明
图1为本申请实施例提供的MBMS服务区域的管理系统的示意图；
图2为本申请实施例提供的MBMS服务区域的管理系统的示例图；
图3为本申请实施例提供的一种MBMS服务区域的管理方法的流程图；
图4为本申请实施例提供的另一种MBMS服务区域的管理方法的流程图；
图5为本申请实施例提供的另一种MBMS服务区域的管理方法的流程图；
图6为本申请实施例提供的另一种MBMS服务区域的管理方法的流程图；
图7为本申请实施例提供的另一种MBMS服务区域的管理方法的流程图；
图8为本申请实施例的注册阶段的流程示意图；
图9为本申请实施例的业务流程发起阶段的示意图；
图10为本申请实施例的动态区域生成阶段的处理示意图；
图11为本申请实施例的服务区域动态调整的一种示例图；
图12为本申请实施例的服务区域动态调整的另一示例图；
图13为本申请实施例的一种MBMS服务区域的管理装置的示意图；
图14为本申请实施例的另一种MBMS服务区域的管理装置的示意图；
图15为本申请实施例的另一种MBMS服务区域的管理装置的示意图；
图16为本申请实施例的另一种MBMS服务区域的管理装置的示意图；
图17为本申请实施例的另一种MBMS服务区域的管理装置的示意图；
图18为本申请实施例提供的第一通信网元的示意图；
图19为本申请实施例提供的第二通信网元的示意图；
图20为本申请实施例提供的第三通信网元的示意图；
图21为本申请实施例提供的终端的示意图；
图22为本申请实施例提供的业务服务器的示意图。
具体实施方式
对于某些使用场景，例如铁路系统的集群应急通信，某项业务需要在业务发起之后，将业务发起者周围一定范围内的相关用户全部接入该业务。而且，随着业务发起者自身物理位置的不断变化，业务的覆盖区域需要不断调整，使得新进入业务覆盖区域的用户加入集群，远离业务覆盖区域的用户自动退出。
本申请实施例提供一种MBMS服务区域的管理方法及系统，通过对业务发起终端的数据链路的识别，实时跟踪并通知业务发起终端所在的第一通信网元 (比如，基站)。由第一通信网元自动调整业务覆盖范围，形成一种随着业务发起终端的物理位置变化而调整的动态MBMS服务区域(MBMS area)。
图1为本申请实施例提供的MBMS服务区域的管理系统的示意图。如图1所示，本实施例提供的MBMS服务区域的管理系统，包括：第一通信网元11以及第二通信网元12；其中，第一通信网元11连接第二通信网元。
其中，第二通信网元12，设置为向第一通信网元11发送携带专属MBMS标识(MBMS ID)的第一会话建立请求。
第一通信网元11，设置为接收第一会话建立请求，根据接收到的位置通知消息或者第一区域判决消息，确定自身是否处于专属MBMS标识指示的专属MBMS的服务区域内。
其中，专属MBMS标识用于指示基于业务发起终端的物理位置变化动态调整服务区域的专属MBMS；位置通知消息用于指示业务发起终端当前处于第一通信网元11的覆盖范围内。
本实施例中，专属MBMS与普通MBMS的区别在于：专属MBMS对应的MBMS服务区域受限于业务发起终端的物理位置，而且是动态变化的。
本实施例中，第一区域判决消息可以用于指示该第一通信网元11邻接的第一通信网元与专属MBMS的服务区域中心的间隔。
在示例性实施方式中，第二通信网元12，可以用于在接收到携带专属MBMS标识的第二会话建立请求后，向第一通信网元11发送第一会话建立请求。
在示例性实施方式中，如图1所示，本实施例提供的管理系统还可以包括：第三通信网元13，第三通信网元13分别连接第一通信网元11和第二通信网元12。
第三通信网元13，可以设置为检测到专属MBMS，则监测该专属MBMS的业务发起终端所在的第一通信网元。
第三通信网元13，还可以设置为根据接收到的携带专属MBMS标识的第三会话建立请求，或者，根据该业务发起终端所在的第一通信网元的切换，向该业务发起终端当前所在的第一通信网元(比如，第一通信网元11)发送位置通知消息。
在示例性实施方式中，如图1所示，本实施例的系统还可以包括：业务发起终端(User Equipment，UE)10，设置为通过链路发送携带专属业务标识的数据。在一实施例中，专属业务标识用于指示专属MBMS标识，且专属业务标识 与专属MBMS标识之间存在对应关系。
在一实施例中，如图1所示，本实施例的系统还可以包括：业务服务器14，设置为接收携带专属业务标识的数据，根据该专属业务标识，确定与所述专属业务标识对应的专属MBMS标识，触发会话建立流程。
在示例性实施方式中，第一通信网元11可以包括基站(eNodeB)，第二通信网元12可以包括多小区多播协调实体(Multi-cell/Multicast Coordination Entity，MCE)，第三通信网元13可以包括移动管理实体(Mobility Management Entity，MME)。本申请对此并不限定。
图2为本申请实施例提供的MBMS服务区域的管理系统的示例图。在本示例中，以第一通信网元为eNodeB，第二通信网元为MCE，第三通信网元为MME，业务服务器为集群业务服务器(例如，MCPTT服务器)为例进行说明。
如图2所示，本示例提供的管理系统可以包括：UE 20、eNodeB 21、MCE 22、MME 23、集群业务服务器24、广播组播业务中心(Broadcast/Multicast Service Center，BM-SC)25和MBMS网关(MBMS Gate Way，MBMS-GW)26。其中，BM-SC 25和MBMS-GW 26是在多播业务发起过程中的参与者。
在本示例中，UE 20设置为在业务发起阶段携带专属业务标识，即作为业务发起终端。集群业务服务器24设置为识别当前发起的业务是否处于专属MBMS业务，并识别业务发起终端的相关信息。MCE 22设置为配置专属业务标识所对应的专属MBMS标识，并统一管理专属业务标识对应的信道资源，支持通过后台参数配置动态MBMS服务区域的范围。MME 23设置为监控业务发起终端的物理位置，并将业务发起终端的位置变化信息传递给eNodeB 21。在MCE 22与MME 23所属的多个eNodeB 21，分别设置为判断本eNodeB是否位于MBMS服务区域的动态范围之内，并指导无线资源管理策略。
在本示例中，基于业务发起终端的物理位置而动态调整MBMS服务区域的过程可以包括以下三个阶段：注册阶段、业务流程发起阶段以及动态区域生成阶段。下面基于本示例的管理系统对上述三个阶段分别进行说明。
本示例中，注册阶段可以包括以下过程。
MCE向MME上报专属MBMS ID，用于标识专属MBMS。在一实施例中，专属MBMS与其他普通MBMS的区别在于：专属MBMS对应的MBMS Area(服务区域)是受限于业务发起终端的位置并且动态变化的；专属MBMS ID可以在MCE与MME建立链路连接时携带给MME，或者，也可以通过独立的消 息专门携带给MME。
MCE给专属MBMS预留独立的多播资源，多播资源可以包括至少一个多播子帧。在一实施例中，MCE在专属MBMS发起时，针对这些多播资源进行调度。
MCE向eNodeB下发专属MBMS ID和动态区域范围标识。在一实施例中，动态区域范围标识可由后台配置，用于标明专属MBMS的服务区域的范围。比如，动态区域范围标识可以指示专属MBMS的服务区域边界相对于服务区域中心的最大间隔。专属MBMS ID和动态区域范围标识可以在eNodeB向MCE建立链路连接的响应(response)消息中携带，或者，也可以通过专门的配置消息主动向eNodeB下发。
集群业务服务器上设置专属MBMS所对应的专属MBMS ID以及支持专属MBMS ID的路由信息。
本示例中，业务流程发起阶段可以包括以下第一步至第五步。
第一步、发起专属集群业务。
本步骤中，UE发起专属集群业务，将专属业务标识写入用户面数据包，用于向集群业务服务器表明业务类型。在一实施例中，UE在发起业务时，使用一种专属服务质量等级标识符(QoS Class Identifier，QCI)申请承载链路。专属QCI可以是一种独立于标准协议之外的扩展QCI，专用于上述专属集群业务。
第二步、业务类型识别与发起。
集群业务服务器依据UE上报的专属业务标识，确定UE发起的业务处于基于业务发起终端的位置变化动态调整服务区域的专属MBMS，即专属MBMS ID的对应业务。集群业务服务器将业务发起终端发送的用户面数据、专属MBMS ID以及支持专属MBMS ID的路由信息，一同下发至BM-SC，触发eMBMS会话建立流程。
第三步、业务发起终端的位置监测。
在MME检测到某一数据链路的QCI处于专属QCI时，确认该数据链路承载需要进行监测。MME监测承载端eNodeB的物理标识(比如，网络协议(Internet Protocol，IP)地址)以及其变化情况，实时追踪并记录业务发起终端当前处于哪一个eNodeB的覆盖范围内。
第四步、MME向eNodeB通知业务发起终端的位置变化信息。
BM-SC执行标准的会话建立流程，当MME接收到来自MBMS-GW的携带 专属MBMS ID的会话建立请求(对应于上述的第三会话建立请求)时，MME依据对业务发起终端的位置监测记录，向当前业务发起终端所在的eNodeB发送位置通知消息，用于告知该eNodeB正在为业务发起终端提供无线接入。当业务发起终端发生越区切换时，MME根据位置监测记录的变化情况，向新的正在给业务发起终端提供无线接入的eNodeB发送位置通知消息，直至业务发起终端的业务承载拆除。
第五步、多播业务选择执行。
MME继续执行标准的会话建立流程，当eNodeB收到来自MCE的携带专属MBMS ID的会话连接请求(对应于上述的第一会话连接请求)，以及对应的调度信息之后，eNodeB要先确认自身是否处于专属MBMS的动态服务区域内。
在一实施例中，当一个eNodeB判决本eNodeB不处于动态服务区域内时，该eNodeB保存MCE下发的相关配置信息，按照非多播子帧的模式调度其对应的无线资源；当一个eNodeB判决本eNodeB处于动态服务区域内时，执行后续的标准会话建立流程，即下发业务通知和相关配置参数，并正式加入多播组互联网协议(Internet Protocol，IP)，在对应的无线资源位置上执行多播业务。
本示例中，动态区域生成阶段可以包括以下步骤一至步骤四。
第一步、eNodeB收到来自MCE的动态区域范围标识后，开始在本地维护区域判决参数，区域判决参数用于判决eNodeB是否处于动态服务区域内；区域判决参数包含以下三个元素：动态区域范围标识、中心位置偏移标识、以及序列号。
在一实施例中，动态区域范围标识接收自MCE，直接保存在本地。中心位置偏移标识由eNodeB自行维护，初始化数值与动态区域范围标识相同。序列号，由eNodeB自行维护，初始化数值为全0。
第二步、当某一个eNodeB收到MME发送的位置通知消息时，触发一次动态区域生成流程。在一实施例中，该eNodeB将本地保存的序列号加1，将本地保存的中心位置偏移标识置0；并且将本地保存的中心位置偏移标识加1后与更新后的序列号一起，组成区域判决消息(对应于上述的第二区域判决消息)。通过X2或者S1接口，将区域判决消息发送至该eNodeB的所有邻接的eNodeB，并进入第四步。
第三步、当某一个eNodeB收到区域判决消息(对应于上述的第一区域判决消息)时，若接收到的区域判决消息中携带的序列号与该eNodeB本地保存的序 列号的数值相同，则直接忽略接收到的区域判决消息，并结束流程；若接收到的区域判决消息中携带的序列号与该eNodeB本地保存的序列号的数值不相同，则保存接收到的区域判决消息中携带的序列号和中心位置偏移标识至本地。
若接收到的区域判决消息中携带的中心位置偏移标识与本地保存的动态区域范围标识的数值相同，则进入第四步；若接收到的区域判决消息中携带的中心位置偏移标识与本地保存的动态区域范围标识的数值不同，则将本地更新后的中心位置偏移标识加1并与更新后的序列号一起，组成区域判决消息(对应于上述的第二区域判决消息)，然后，通过X2或者S1接口，将区域判决消息发送至该eNodeB的所有邻接的eNodeB，并进入第四步。
第四步、eNodeB比较更新后的本地保存的中心位置偏移标识与动态区域范围标识，若中心位置偏移标识小于动态区域范围标识，则该eNodeB判决本eNodeB处于动态服务区域，若中心位置偏移标识大于或等于动态区域范围标识，则判决本eNodeB不处于动态服务区域。
本实施例在保持了目前协议的多播业务发起流程的基础上，通过识别业务类型，监测业务发起终端的物理位置，由eNodeB自适应动态调整eMBMS的服务区域。在使用前景上，弥补了当前eMBMS业务无法适配特定使用场景的局限，适用于基于MCPTT的公共安全领域各类场景，例如铁路调度、灾难预警、视频监控等。而且，本实施例便于eMBMS的灵活部署，允许无线资源迅速在多播业务与非多播业务之间快速转换，即满足突发热点的资源使用要求，又避免资源浪费。另外，eNodeB自组织的动态区域调整模式，也普遍适用于其他应用场景。
图3为本申请实施例提供的一种MBMS服务区域的管理方法的流程图。如图3所示，本实施例提供的MBMS服务区域的管理方法，包括以下步骤S11-S12。
在S11中，第一通信网元接收携带专属MBMS标识的第一会话建立请求。
在S12中，第一通信网元根据接收到的位置通知消息或者第一通信网元的第一区域判决消息，确定自身是否处于专属MBMS标识指示的专属MBMS的服务区域内。
在一实施例中，专属MBMS标识用于指示基于业务发起终端的物理位置变化而动态调整服务区域的专属MBMS。位置通知消息用于指示业务发起终端当前处于该第一通信网元的覆盖范围内。
在一实施例中，第一区域判决消息可以用于指示该第一通信网元邻接的第 一通信网元与专属MBMS的服务区域中心的间隔。
在示例性实施方式中，步骤S12可以包括：
第一通信网元根据接收到的位置通知消息，更新本地保存的区域判决参数，根据更新后的区域判决参数，确定自身是否处于专属MBMS的服务区域内；或者，第一通信网元根据接收到的第一区域判决消息，更新本地保存的区域判决参数，根据更新后的区域判决参数，确定自身是否处于专属MBMS的服务区域内，其中，第一区域判决消息携带该第一通信网元邻接的第一通信网元的区域判决参数。
在示例性实施方式中，区域判决参数至少可以包括：动态区域范围标识和中心位置偏移标识。其中，动态区域范围标识用于指示专属MBMS的服务区域的范围，比如，可以指示专属MBMS的服务区域边界相对于服务区域中心的最大间隔。中心位置偏移标识用于指示第一通信网元与专属MBMS的服务区域中心之间的间隔。
在示例性实施方式中，第一通信网元根据更新后的区域判决参数，确定自身是否处于专属MBMS的服务区域内，可以包括：若第一通信网元本地保存的中心位置偏移标识小于动态区域范围标识，则确定自身处于专属MBMS的服务区域内；若第一通信网元本地保存的中心位置偏移标识大于或等于动态区域范围标识，则确定自身不处于专属MBMS的服务区域内。
在示例性实施方式中，第一通信网元根据接收到的位置通知消息，更新本地保存的区域判决参数，可以包括：若第一通信网元接收到位置通知消息，则将本地保存的中心位置偏移标识置0。如此，表明此时该第一通信网元处于专属MBMS的服务区域中心。
第一通信网元根据接收到的第一区域判决消息，更新本地保存的区域判决参数，可以包括：
若第一通信网元接收到第一区域判决消息，则将本地保存的中心位置偏移标识更新为接收到的第一区域判决消息中携带的所述第一通信网元临接的第一通信网元的区域判决参数中的中心位置偏移标识。其中，第一区域判决消息中携带的中心位置偏移标识与该邻接的第一通信网元本地保存的中心位置偏移标识之间的差值为1。换言之，第一通信网元通过第一区域判决消息可以向邻接的其他第一通信网元指示自身与专属MBMS的服务区域中心之间的间隔。
在示例性实施方式中，第一通信网元接收到位置通知消息后，本实施例的 方法还可以包括：
第一通信网元向自身邻接的第一通信网元广播第二区域判决消息。其中，第二区域判决消息携带的中心位置偏移标识等于该第一通信网元本地保存的中心位置偏移标识加1。
在示例性实施方式中，第一通信网元接收到第一区域判决消息后，本实施例的方法还可以包括：
若第一区域判决消息携带的所述第一通信网元临接的第一通信网元的区域判决参数内的中心位置偏移标识不等于第一通信网元本地保存的动态区域范围标识，则第一通信网元向自身邻接的第一通信网元广播第二区域判决消息，其中，第二区域判决消息携带的中心位置偏移标识等于该第一通信网元本地保存的中心位置偏移标识加1。
在示例性实施方式中，区域判决参数还可以包括：序列号。
其中，第一通信网元接收到位置通知消息或者第一区域判决消息后，本实施例的方法还可以包括：
第一通信网元根据接收到的位置通信消息，将本地保存的序列号加1；或者，第一通信网元根据接收到的第一区域判决消息，若确定第一区域判决消息携带的所述第一通信网元临接的第一通信网元的区域判决参数内的序列号等于自身本地保存的区域判决参数内的序列号，则第一通信网元丢弃接收到的第一区域判决消息。
本示例性实施方式中，第一通信网元可以通过接收到的第一区域判决消息携带的序列号，判断接收到的第一区域判决消息携带的区域判决参数是否可以使用，即确定是否进行动态服务区域的调整过程。然而，本申请对此并不限定。在其他实现方式中，可以在区域判决参数中设置其他元素实现上述功能。
在示例性实施方式中，在S11之前，本实施例的方法还可以包括：
第一通信网元接收专属MBMS标识以及动态区域范围标识；其中，动态区域范围标识用于指示专属MBMS的服务区域的范围。
在本实施方式中，第一通信网元在注册阶段会接收第二通信网元下发的专属MBMS标识以及动态区域范围标识，然后，在业务流程发起阶段，可以识别出第一会话建立请求是否携带专属MBMS标识。
在示例性实施方式中，第一通信网元可以包括eNodeB。然而，本申请对此并不限定。
本实施例中，第一通信网元通过自组织方式确定动态服务区域，可以适用于eMBMS业务无法适配的特定使用场景以及其他应用场景。
图4为本申请实施例提供的另一MBMS服务区域的管理方法的流程图。如图4所示，本实施例提供的MBMS服务区域的管理方法，包括如下S21-S22。
在S21中，第二通信网元接收携带专属MBMS标识的第二会话建立请求。
在一实施例中，专属MBMS标识用于指示基于业务发起终端的物理位置变化动态调整服务区域的专属MBMS。
在S22中，第二通信网元向第一通信网元发送携带专属MBMS标识的第一会话建立请求。
在示例性实施方式中，在S21之前，本实施例的方法还可以包括：
第二通信网元配置专属MBMS标识以及动态区域范围标识，并给专属MBMS标识所指示的专属MBMS预留独立的多播资源；其中，动态区域范围标识用于指示专属MBMS的服务区域的范围；第二通信网元向第一通信网元发送专属MBMS标识以及动态区域范围标识；第二通信网元向第三通信网元发送专属MBMS标识。
其中，第二通信网元可以在注册阶段，配置专属MBMS所对应的专属MBMS标识以及动态区域范围标识，并将专属MBMS标识和动态区域范围标识下发给第一通信网元，将专属MBMS标识发送给第三通信网元。
在示例性实施方式中，第二通信网元向第一通信网元发送专属MBMS标识以及动态区域范围标识，可以包括：
第二通信网元通过配置消息向第一通信网元发送专属MBMS标识以及动态区域范围标识；或者，第二通信网元通过针对第一通信网元的链路连接建立请求的响应消息，向第一通信网元发送专属MBMS标识以及动态区域范围标识。
在示例性实施方式中，第二通信网元向第三通信网元发送专属MBMS标识，可以包括：
第二通信网元通过单独的消息向第三通信网元发送专属MBMS标识；或者，第二通信网元通过链路连接建立消息向第三通信网元发送专属MBMS标识。
在示例性实施方式中，第一通信网元可以包括eNodeB，第二通信网元可以包括MCE，第三通信网元可以包括MME。然而，本申请对此并不限定。
图5为本申请实施例提供的另一MBMS服务区域的管理方法的流程图。如图5所示，本实施例提供的MBMS服务区域的管理方法，包括如下S31-S32。
在S31中，第三通信网元在检测到基于业务发起终端的物理位置变化动态调整服务区域的专属MBMS时，监测该专属MBMS的业务发起终端所在的第一通信网元。
在S32中，在第三通信网元接收到携带专属MBMS标识的第三会话建立请求，或者，业务发起终端所在的第一通信网元发生切换时，则第三通信网元向业务发起终端当前所在的第一通信网元发送位置通知消息。
其中，专属MBMS标识用于指示专属MBMS，位置通知消息用于指示业务发起终端当前处于该第一通信网元的覆盖范围内。
在示例性实施方式中，第三通信网元检测专属MBMS可以包括：
第三通信网元在检测到一个数据链路的服务质量等级标识符(QCI)处于专属QCI时，确认该数据链路所承载的业务处于专属MBMS。
在示例性实施方式中，在S31之前，本实施例的方法还可以包括：第三通信网元接收专属MBMS标识。
其中，在注册阶段，第三通信网元从第二通信网元接收第二通信网元配置的专属MBMS标识。
在示例性实施方式中，第一通信网元可以包括eNodeB，第二通信网元可以包括MCE，第三通信网元可以包括MME。然而，本申请对此并不限定。
本实施例中，第三通信网元实时跟踪业务发起终端所在的eNodeB，而且可以向业务发起终端当前所在的eNodeB发送位置通知消息，告知该eNodeB当前正在给业务发起终端提供无线接入。
图6为本申请实施例提供的另一MBMS服务区域的管理方法的流程图。如图6所示，本实施例提供的MBMS服务区域的管理方法，包括如下S41-S42。
在S41中，业务发起终端申请数据链路。
在S42中，业务发起终端通过数据链路发送携带专属业务标识的数据。
在一实施例中，专属业务标识用于指示基于业务发起终端的物理位置变化动态调整服务区域的专属MBMS，且专属业务标识与专属MBMS标识之间存在对应关系。
在示例性实施方式中，S41可以包括：业务发起终端采用专属QCI申请数据链路。其中，专属QCI可以是一种独立于标准协议之外的扩展QCI。
本实施例中，终端在发起专属MBMS业务时，携带专属业务标识，用于向业务服务器表明业务类型，以便于业务服务器执行该业务类型对应的处理。
图7为本申请实施例提供的另一MBMS服务区域的管理方法的流程图。如图7所示，本实施例提供的MBMS服务区域的管理方法，包括如下S51-S52。
在S51中，业务服务器接收携带专属业务标识的数据。
在一实施例中，专属业务标识用于指示基于业务发起终端的物理位置变化动态调整服务区域的专属MBMS。
在S52中，业务服务器根据专属业务标识，确定与所述专属业务标识对应的专属MBMS标识，触发会话建立流程。
在示例性实施方式中，在S52中，触发会话建立流程可以包括：
业务服务器向广播组播业务中心(BM-SC)发送会话建立请求，其中，会话建立请求携带接收到的数据、专属MBMS标识、以及专属MBMS标识对应的路由信息。
下面通过多个实施例对本申请的方案进行说明。其中，下面的实施例基于图2所示的系统进行说明。
实施例一
本实施例说明了注册阶段的实施过程。在注册阶段，第二通信网元(本示例中为MCE)将相关标识发送至第一通信网元(本示例中为eNodeB)和第三通信网元(本示例中为MME)，以便业务发起时的即时识别与追踪。
如图8所示，本实施例的注册阶段包括以下流程S101-S106。
在S101中，MCE设置专属MBMS ID，专属MBMS ID对应专属MBMS，该专属MBMS的服务区域基于业务发起终端的物理位置而动态变化。
在S102中，MCE设置动态区域范围标识，该动态区域范围标识指示专属MBMS的服务区域的范围。
在一实施例中，给业务发起终端提供无线接入的eNodeB作为动态服务区域的中心，动态区域范围标识可以指示专属MBMS的服务区域边界相对于服务区域中心的最大间隔(以小区为单位)。
在S103中，MCE设置专属MBMS ID相关的无线资源。
在一实施例中，无线资源可以包括位置固定的一个或者多个子帧，这些无线资源相对独立于其他多播业务的无线资源，当对应于专属MBMS ID的业务发起时，才调度这些资源，不会被其他多播业务占用。
在S104中，MCE向MME上报专属MBMS ID，用于MME判断业务是否已经发起，是否执行后续的位置通知流程。
在S105中，MCE向eNodeB发送专属MBMS ID和动态区域范围标识，分别用于eNodeB判断发起的多播业务是否处于需要生成动态服务区域的eMBMS业务，以及判断自身是否处于动态服务区域之内。
在S106中，集群业务服务器上设置专属MBMS ID以及支持专属MBMS ID的路由信息，用于eMBMS业务发起时，指导BM-SC为用户面数据流提供正确的路由。
本申请对于上述步骤的执行顺序并不限定。比如，S104可以在S103之后执行，S105可以在S103之后执行，S106可以在S101之前或与S101同时执行。
实施例二
本实施例说明了业务流程发起阶段的实施过程。其中，业务流程发起阶段包含业务发起终端将用户面数据流发送至集群服务器的上行业务，也包含集群服务器通过eMBMS多播技术将用户面数据流分发的下行广播业务。
整体的业务发起流程可以包含上、下行业务，都是在长期演进技术(Long Term Evolution，LTE)标准业务流程基础上，引入业务识别、位置检测、位置通知、以及区域判决等机制后实现的。
如图9所示，本实施例的执行过程如下S201-S216。
在S201中，终端(UE)发起专属集群业务，将专属业务标识写入用户面数据包，在申请建立专用承载时，使用预先协商好的专属QCI，以区别于普通的专用业务承载。
在S202中，当MME检测到某一承载链路QCI处于专属QCI时，确认该链路承载所对应的业务处于基于业务发起终端位置的动态区域eMBMS业务时，开始对该承载进行监测；MME监测承载端eNodeB的物理标识(比如，IP地址)以及其变化情况，实时追踪并记录，用于监测业务发起终端当前处于哪一个eNodeB的覆盖范围。
在S203中，集群业务服务器(比如，MCPTT Server)依据终端上报的专属业务标识，判断该业务处于基于业务发起终端位置的eMBMS业务，即专属MBMS ID的对应业务。
在S204中，集群业务服务器查找专属MBMS ID对应的路由信息，将接收的用户面数据流、路由信息以及专属MBMS ID一同下发至BM-SC，触发eMBMS会话建立流程。
在S205中，BM-SC依据路由信息，向对应的MBMS-GW发送会话建立请 求，本流程属于标准的eMBMS会话建立流程，不同在于携带专属MBMS ID。
在S206中，MBMS-GW向BM-SC发送会话建立响应消息。
在S207中，MBMS-GW依据路由信息，向对应的MME发送会话建立请求(对应于上述第三会话建立请求)，本流程属于标准的eMBMS会话建立流程，不同在于携带专属MBMS ID。
在S208中，MME接收到来自MBMS-GW的携带专属MBMS ID的会话建立请求时，MME依据对业务发起终端的位置监测记录，向当前业务发起终端所在的eNodeB发送位置通知消息，用于告知该eNodeB正在为业务发起终端提供无线接入；当业务发起终端发生越区切换时，MME可以根据位置监测记录的变化情况，向新的正在提供无线接入的eNodeB发送位置通知消息，直至业务发起终端的业务承载拆除。
在S209中，MME依据路由信息，向对应的MCE发送会话建立请求(对应上述的第二会话建立请求)，本流程属于标准的eMBMS会话建立流程，不同在于携带专属MBMS ID。
在S210中，MCE向MME发送会话建立响应消息。
在S211中，MME向MBMS-GW发送会话建立响应消息。
在S212和S214中，MCE接收到来自MME的携带专属MBMS ID的会话建立请求(对应于上述的第二会话建立请求)时，判断业务类型为基于业务发起终端位置的eMBMS业务，在预留的专属多播资源上配置调度信息，向对应的eNodeB发送会话建立请求(对应于上述的第一会话建立请求)和调度信息；上述过程与标准的MCE处理流程类似，不同在于资源调度要针对专属的多播子帧而不是全体多播子帧。
在S213中，eNodeB发送会话建立响应消息。
在S215中，eNodeB发送调度信息响应消息。
在S216中，当eNodeB收到来自MCE的携带专属MBMS ID的会话连接请求(对应于上述的第一会话建立请求)，以及对应的调度信息之后，eNodeB先要确认自身是否处于动态服务区域。
其中，当一个eNodeB判决自身不处于动态服务区域内时，该eNodeB仅仅是保存MCE下发的相关配置信息，按照非多播子帧的模式调度其对应的无线资源；当一个eNodeB判决自身处于动态服务区域范围内时，执行后续的标准会话建立流程，即下发MBMS控制信道(MBMS Control Channel，MCCH)通知和 相关MBSFN配置参数，并正式加入多播组IP，在对应的无线资源位置上执行多播业务。
实施例三
本实施例说明eNodeB接收到MME发送的位置通知消息或者其他eNodeB发送的区域判决消息之后，确认是否处于动态的服务区域的过程。
本实施例中，每个eNodeB均保存区域判决参数，区域判决参数包含以下三个元素：动态区域范围标识、中心位置偏移标识、以及序列号。其中，动态区域范围标识，接收自MCE，直接保存在本地；中心位置偏移标识，由eNodeB自行维护，初始化数值与动态区域范围标识相同；序列号，由eNodeB自行维护，初始化数值为全0。
如图10所示，本实施例的过程包括如下S301-S308。
在S301中，eNodeB判断是否收到来自MME的位置通知消息；若收到，则执行S302，否则，执行S305。
在S302中，eNodeB将本地保存的序列号加1，并将本地保存的中心位置偏移标识置0。
在S303中，eNodeB将本地保存的中心位置偏移标识加1，与更新后的序列号一起，组成区域判决消息(对应于上述的第二区域判决消息)，然后，通过X2或者S1接口，将区域判决消息发送至该eNodeB的所有邻接的eNodeB；之后，执行S304。
在S304中，该eNodeB将中心位置偏移标识与动态区域范围标识进行比较；若中心位置偏移标识小于动态区域范围标识，则判决自身处于动态服务区域内，开启业务；若中心位置偏移标识大于或等于动态区域范围标识，则判决自身不处于动态服务区域内，停发业务。
在S305中，eNodeB判断是否收到来自自身邻接的eNodeB的区域判决消息(对应于上述的第一区域判决消息)；若收到，则执行S306，否则该eNodeB确定自己不处于专属业务的服务区域，停发业务。
在S306中，该eNodeB判断接收到的区域判决消息中携带的序列号与本地保存的序列号的数值是否相同；若相同，则直接忽略接收到的区域判决消息，结束流程；否则，执行S307。
在S307中，该eNodeB保存接收到的区域判决消息中携带的序列号和中心位置偏移标识至本地。本步骤中，该eNodeB将本地保存的序列号和中心位置偏 移标识更新为接收到的区域判决消息中携带的序列号和中心位置偏移标识。
在S308中，该eNodeB判断接收到的区域判决消息中携带的中心位置偏移标识与本地保存的动态区域范围标识的数值是否相同；若相同，则执行S304，否则，执行S303，即将中心位置偏移标识加1后与序列号一起组成区域判决消息(对应于上述的第二区域判决消息)，然后通过X2或者S1接口，将区域判决消息发送至该eNodeB的所有邻接的eNodeB。
实施例四
本实施例说明了每个eNodeB在初始状态下首次生成动态服务区域的执行过程。
本实施例中，每个eNodeB均保存区域判决参数，区域判决参数包含以下三个元素：动态区域范围标识、中心位置偏移标识、以及序列号。其中，动态区域范围标识，接收自MCE，直接保存在本地，本示例中，初始值为3；中心位置偏移标识，由eNodeB自行维护，初始化数值与动态区域范围标识相同；序列号，由eNodeB自行维护，初始化数值为全0。即，本实施例中，每个eNodeB的初始区域判决参数为(3，3，0000)。
本实施例中为了演示方便，将eNodeB的覆盖简化为线型覆盖。本申请对此并不限定。本实施例针对eNodeB网状覆盖同样适用。
如图11所示，本实施例的实施过程如下第一步至第十四步。
第一步、某个eNodeB收到来自MME的位置通知消息，确认自己处于动态eMBMS区域的中心，以下将该eNodeB称为中心eNodeB。
第二步、中心eNodeB将本地记录的中心位置偏移标识置0，将本地记录的序列号加1，并在本地保存；即中心eNodeB更新后在本地存储的区域判决参数为(3，0，0001)。
第三步、中心eNodeB构建区域判决消息，构建结果为(1，0001)，将区域判决消息通过S1或者X2链路，广播至中心eNodeB的所有邻接eNodeB。
第四步、中心eNodeB判决中心位置偏移标识(此处值为0)小于动态区域范围标识(此处值为3)，处于动态服务区域；本实施例中，将中心eNodeB命名为中心节点。
第五步、收到来自中心节点的区域判决消息的eNodeB，判决接收到的区域判决消息携带的序列号与本地保存的序列号不一致，保存收到的序列号和中心位置偏移标识，本地更新后的区域判决参数为(3，1，0001)。
第六步、上述收到来自中心节点的区域判决消息的eNodeB判决更新后的中心位置偏移标识(此处值为1)不等于动态区域范围标识(此处值为3)，则构建区域判决消息，构建结果为(2，0001)，并将构建的区域判决消息通过S1或者X2链路，广播至该eNodeB的所有邻接eNodeB。
第七步、上述收到来自中心节点的区域判决消息的eNodeB判决更新后的中心位置偏移标识(此处值为1)小于动态区域范围标识(此处值为3)，即处于动态服务区域；本实施例中，将上述收到来自中心节点的区域判决消息的eNodeB命名为一级节点。
第八步、中心节点收到来自一级节点的区域判决消息，判决接收到的区域判决消息中携带的序列号与本地保存的序列号相同，不作处理，丢弃接收到的区域判决消息。
第九步、收到来自一级节点的区域判决消息的eNodeB，判决接收到的区域判决消息中携带的序列号与本地保存的序列号不一致，保存收到的区域判决消息中携带的序列号和中心位置偏移标识，本地更新后的区域判决参数为(3，2，0001)。
第十步、上述收到来自一级节点的区域判决消息的eNodeB判决更新后的中心位置偏移标识不等于动态区域范围标识，则构建区域判决消息，构建结果为(3，0001)，上述收到来自一级节点的区域判决消息的eNodeB将构建的区域判决消息通过S1或者X2链路，广播至该eNodeB的所有邻接eNodeB。
第十一步、上述收到来自一级节点的区域判决消息的eNodeB判决更新后的中心位置偏移标识(此处值为2)小于动态区域范围标识(此处值为3)，即处于动态服务区域；本实施例中，将上述收到来自一级节点的区域判决消息的eNodeB命名为二级节点。
第十二步、一级节点收到来自二级节点的区域判决消息，判决接收到的区域判决消息中携带的序列号与本地保存的序列号相同，不作处理，丢弃接收到的区域判决消息。
第十三步、收到来自二级节点的区域判决消息的eNodeB，判决接收到的区域判决消息中携带的序列号与本地保存的序列号不一致，保存收到的区域判决消息中携带的序列号和中心位置偏移标识，本地更新后的区域判决参数为(3，3，0001)。
第十四步、上述收到来自二级节点的区域判决消息的eNodeB判决更新后的 中心位置偏移标识等于动态区域范围标识，不再向邻接eNodeB广播发送区域判决消息，并判决更新后的中心位置偏移标识(此处值为3)等于动态区域范围标识(此处值为3)，即不处于动态服务区域。
至此，如图11所示，动态服务区域的范围可以确认。
实施例五
本实施例说明了各个eNodeB在业务发起终端发生越区切换之后，生成动态服务区域的执行过程。其中，eNodeB在接收到位置通知消息之后，逐步确认并最终确定动态服务区域的边界，新的eNodeB纳入动态服务区域，旧的eNodeB退出动态服务区域。
本实施例中，每个eNodeB均保存区域判决参数，区域判决参数包含以下三个元素：动态区域范围标识、中心位置偏移标识、以及序列号；其中，动态区域范围标识，接收自MCE，直接保存在本地，本示例中，初始值为3；中心位置偏移标识，由eNodeB自行维护，初始化数值与动态区域范围标识相同；序列号，由eNodeB自行维护，初始化数值为全0。
本实施例中为了演示方便，将eNodeB的覆盖简化为线型覆盖。本申请对此并不限定。本实施例针对eNodeB网状覆盖同样适用。
如图12所示，本实施例的实施过程如下第一步至第十四步。
第一步、在业务发起终端发生越区切换后，某个原先的一级节点，收到来自MME的位置通知消息，确认自己处于动态eMBMS区域的中心；以下将该eNodeB称为中心eNodeB。
第二步、中心eNodeB将本地记录的中心位置偏移标识置0，将本地记录的序列号加1，并在本地保存；即中心eNodeB更新后在本地存储的区域判决参数为(3，0，xxx2)。
第三步、中心eNodeB构建区域判决消息，构建结果为(1，xxx2)，将区域判决消息通过S1或者X2链路，广播至中心eNodeB的所有邻接eNodeB。
第四步、中心eNodeB判决中心位置偏移标识(此处值为0)小于动态区域范围标识(此处值为3)，即处于动态服务区域；本实施例中，将中心eNodeB命名为中心节点。
第五步、收到来自中心节点的区域判决消息的eNodeB，判决接收到的区域判决消息携带的序列号与本地保存的序列号不一致，保存收到的序列号和中心位置偏移标识，本地更新后的区域判决参数为(3，1，xxx2)。
第六步、上述收到来自中心节点的区域判决消息的eNodeB判决更新后的中心位置偏移标识(此处值为1)不等于动态区域范围标识(此处值为3)，则构建区域判决消息，构建结果为(2，xxx2)，并将构建的区域判决消息通过S 1或者X2链路，广播至该eNodeB的所有邻接eNodeB。
第七步、上述收到来自中心节点的区域判决消息的eNodeB判决更新后的中心位置偏移标识(此处值为1)小于动态区域范围标识(此处值为3)，即处于动态服务区域；本实施例中，将上述收到来自中心节点的区域判决消息的eNodeB命名为一级节点；在图12中可见，切换发生后，一个原中心节点和一个原二级节点，更新为一级节点。
第八步、中心节点收到来自一级节点的区域判决消息，判决接收到的区域判决消息中携带的序列号与本地保存的序列号相同，不作处理，丢弃接收到的区域判决消息。
第九步、收到来自一级节点的区域判决消息的eNodeB，判决接收到的区域判决消息中携带的序列号与本地保存的序列号不一致，保存收到的序列号和中心位置偏移标识，本地更新后的区域判决参数为(3，2，xxx2)。
第十步、上述收到来自一级节点的区域判决消息的eNodeB判决更新后的中心位置偏移标识(此处值为2)不等于动态区域范围标识(此处值为3)，则构建区域判决消息，构建结果为(3，xxx2)，并将构建的区域判决消息通过S1或者X2链路，广播至该eNodeB的所有邻接eNodeB。
第十一步、上述收到来自一级节点的区域判决消息的eNodeB判决更新后的中心位置偏移标识(此处值为2)小于动态区域范围标识(此处值为3)，即处于动态服务区域；本实施例中，将上述收到来自一级节点的区域判决消息的eNodeB命名为二级节点；在图12中可见，切换发生后，一个原一级节点，更新为二级节点；一个原不处于动态服务区域的节点作为二级节点，加入了动态服务区域。
第十二步、一级节点收到来自二级节点的区域判决消息，判决接收到的区域判决消息中携带的序列号与本地保存的序列号相同，不作处理，丢弃接收到的区域判决消息。
第十三步、收到来自二级节点的区域判决消息的eNodeB，判决接收到的区域判决消息中携带的序列号与本地保存的序列号不一致，保存收到的序列号和中心位置偏移标识，本地更新后的区域判决参数为(3，3，xxx2)。
第十四步、上述收到来自二级节点的区域判决消息的eNodeB判决更新后的中心位置偏移标识等于动态区域范围标识，不再向邻接eNodeB广播发送区域判决消息，并判决更新后的中心位置偏移标识(此处值为3)等于动态区域范围标识(此处值为3)，即不处于动态服务区域；在图12中可见，切换发生后，一个原二级节点，退出了动态服务区域。
至此，如图12所示，动态服务区域的范围可以确认。
图13为本申请实施例提供的一种MBMS服务区域的管理装置的示意图。如图13所示，本实施例提供的MBMS服务区域的管理装置，应用于第一通信网元(比如，eNodeB)，包括：第一接收模块101和第一处理模块102。
第一接收模块101，设置为接收携带专属MBMS标识的第一会话建立请求；其中，专属MBMS标识用于指示基于业务发起终端的物理位置变化动态调整服务区域的专属MBMS。
第一处理模块102，设置为根据接收到的位置通知消息或者第一区域判决消息，确定所在的第一通信网元是否处于专属MBMS的服务区域内。
其中，位置通知消息用于指示业务发起终端当前处于该第一通信网元的覆盖范围内。
在示例性实施方式中，第一处理模块102可以设置为通过以下方式根据接收到的位置通知消息或者第一区域判决消息，确定所在的第一通信网元是否处于专属MBMS的服务区域内：根据接收到的位置通知消息，更新本地保存的区域判决参数，根据更新后的区域判决参数，确定所在的第一通信网元是否处于专属MBMS的服务区域内；或者，
根据接收到的第一区域判决消息，更新本地保存的区域判决参数，根据更新后的区域判决参数，确定自身是否处于专属MBMS的服务区域内；其中，第一区域判决消息携带该第一通信网元邻接的第一通信网元的区域判决参数。
在示例性实施方式中，区域判决参数至少可以包括：动态区域范围标识和中心位置偏移标识；其中，动态区域范围标识用于指示专属MBMS的服务区域的范围；中心位置偏移标识用于指示第一通信网元与专属MBMS的服务区域中心之间的间隔。
在示例性实施方式中，第一处理模块102可以设置为通过以下方式根据更新后的区域判决参数，确定所在的第一通信网元是否处于专属MBMS的服务区域内：若第一通信网元本地保存的中心位置偏移标识小于动态区域范围标识， 则确定该第一通信网元处于专属MBMS的服务区域内；若第一通信网元本地保存的中心位置偏移标识大于或等于动态区域范围标识，则确定该第一通信网元不处于专属MBMS的服务区域内。
在示例性实施方式中，本实施例提供的管理装置还可以包括：第一发送模块。
第一发送模块，设置为根据接收到的位置通知消息，向所在的第一通信网元邻接的第一通信网元广播第二区域判决消息。
或者，第一发送模块，设置为根据接收到的第一区域判决消息，确认第一区域判决消息携带的中心位置偏移标识不等于本地保存的动态区域范围标识，则向该邻接的第一通信网元广播第二区域判决消息。
其中，第二区域判决消息携带的中心位置偏移标识等于该所在的第一通信网元本地保存的中心位置偏移标识加1。
关于本实施例提供的管理装置的相关描述可以参照图3对应的方法实施例的说明，故于此不再赘述。
图14为本申请实施例提供的另一种MBMS服务区域的管理装置的示意图。如图14所示，本实施例提供的MBMS服务区域的管理装置，应用于第二通信网元(比如，MCE)，包括：第二接收模块201和第二发送模块202。
第二接收模块201，设置为接收携带专属MBMS标识的第二会话建立请求；其中，专属MBMS标识用于指示基于业务发起终端的物理位置变化动态调整服务区域的专属MBMS；
第二发送模块202，设置为向第一通信网元发送携带专属MBMS标识的第一会话建立请求。
在示例性实施方式中，本实施例提供的管理装置还可以包括：配置模块。
配置模块，设置为配置专属MBMS标识以及动态区域范围标识，并给专属MBMS标识所指示的专属MBMS预留独立的多播资源；其中，动态区域范围标识用于指示专属MBMS的服务区域的范围；
第二发送模块202，还设置为向第一通信网元发送专属MBMS标识以及动态区域范围标识；向第三通信网元发送专属MBMS标识。
关于本实施例提供的管理装置的相关描述可以参照图4对应的方法实施例的说明，故于此不再赘述。
图15为本申请实施例提供的MBMS服务区域的管理装置的示意图。如图 15所示，本实施例提供的MBMS服务区域的管理装置，应用于第三通信网元(比如，MME)，包括：监测模块301和第二发送模块302。
监测模块301，设置为在检测到基于业务发起终端的物理位置变化动态调整服务区域的专属MBMS时，监测该专属MBMS的业务发起终端所在的第一通信网元。
第二发送模块302，设置为根据接收到的携带专属MBMS标识的第三会话建立请求，或者，根据业务发起终端所在的第一通信网元的切换时，向业务发起终端当前所在的第一通信网元发送位置通知消息。
其中，专属MBMS标识用于指示专属MBMS，位置通知消息用于指示业务发起终端当前处于该第一通信网元的覆盖范围内。
在示例性实施方式中，本实施例提供的管理装置还可以包括：第三接收模块。
第三接收模块，设置为接收专属MBMS标识。
关于本实施例提供的管理装置的相关描述可以参照图5对应的方法实施例的说明，故于此不再赘述。
图16为本申请实施例提供的MBMS服务区域的管理装置的示意图。如图16所示，本实施例提供的MBMS服务区域的管理装置，应用于业务发起终端，包括：第二处理模块401和第四发送模块402。
第二处理模块401，设置为申请数据链路；
第四发送模块402，设置为通过该数据链路发送携带专属业务标识的数据；其中，专属业务标识用于指示基于业务发起终端的物理位置变化动态调整服务区域的专属MBMS，且专属业务标识与专属MBMS标识之间存在对应关系。
在示例性实施方式中，第二处理模块401可以设置为通过以下方式申请数据链路：采用专属QCI申请数据链路。
关于本实施例提供的管理装置的相关描述可以参照图6对应的方法实施例的说明，故于此不再赘述。
图17为本申请实施例提供的MBMS服务区域的管理装置的示意图。如图17所示，本实施例提供的MBMS服务区域的管理装置，应用于业务服务器(比如，MCPTT服务器)，包括：第四接收模块501和第三处理模块502。
第四接收模块501，设置为接收携带专属业务标识的数据；其中，专属业务标识用于指示基于业务发起终端的物理位置变化动态调整服务区域的专属 MBMS。
第三处理模块502，设置为根据专属业务标识，确定与所述专属业务标识对应的专属MBMS标识，触发会话建立流程。
在示例性实施方式中，第三处理模块502可以第三处理模块502通过以下方式触发会话建立流程：向BM-SC发送第四会话建立请求，其中，第四会话建立请求携带接收到的数据、专属MBMS标识、专属MBMS标识对应的路由信息。
关于本实施例提供的管理装置的相关描述可以参照图7对应的方法实施例的说明，故于此不再赘述。
图18为本申请实施例提供的第一通信网元的示意图。如图18所示，本实施例提供的第一通信网元1000(比如，eNodeB)，包括：第一存储器1001以及第一处理器1002，第一存储器1001设置为存储MBMS服务区域的管理程序；该管理程序被第一处理器1002执行时实现上述实施例提供的第一通信网元侧的管理方法。
其中，第一处理器1002可以包括但不限于微处理器(Microcontroller Unit，MCU)或可编程逻辑器件(Field Programmable Gate Array，FPGA)等的处理装置。第一存储器1001可设置为存储应用软件的软件程序以及模块，如本实施例中的管理方法对应的程序指令或模块，第一处理器1002通过运行存储在第一存储器1001内的软件程序以及模块，从而执行各种功能应用以及数据处理，比如实现本实施例提供的管理方法。第一存储器1001可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些示例中，第一存储器1001可包括相对于第一处理器1002远程设置的存储器，这些远程存储器可以通过网络连接至第一通信网元1000。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
示例性地，第一通信网元1000还可以包括第一通信单元1003；第一通信单元1003可以经由一个网络接收或者发送数据。在一个实例中，第一通信单元1003可以为射频(Radio Frequency，RF)模块，其用于通过无线方式与互联网进行通信。
图19为本申请实施例提供的第二通信网元的示意图。如图19所示，本实施例提供的第二通信网元2000(比如，MCE)，包括：第二存储器2001以及第 二处理器2002，第二存储器2001设置为存储MBMS服务区域的管理程序；该管理程序被第二处理器2002执行时实现上述实施例提供的第二通信网元侧的管理方法。
示例性地，第二通信网元2000还可以包括第二通信单元2003。
关于本实施例提供的第二存储器、第二处理器以及第二通信单元的说明可以参照上述第一存储器、第一处理器以及第一通信单元的说明，故于此不再赘述。
图20为本申请实施例提供的第三通信网元的示意图。如图20所示，本实施例提供的第三通信网元3000(比如，MME)，包括：第三存储器3001以及第三处理器3002，第三存储器3001设置为存储MBMS服务区域的管理程序；该管理程序被第三处理器3002执行时实现上述实施例提供的第三通信网元侧的管理方法。
示例性地，第三通信网元3000还可以包括第三通信单元3003。
关于本实施例提供的第三存储器、第三处理器以及第三通信单元的说明可以参照上述第一存储器、第一处理器以及第一通信单元的说明，故于此不再赘述。
图21为本申请实施例提供的终端的示意图。如图21所示，本实施例提供的终端4000，包括：存储器4001以及处理器4002，存储器4001设置为存储MBMS服务区域的管理程序；该管理程序被处理器4002执行时实现上述实施例提供的终端侧的管理方法。
示例性地，终端4000还可以包括第四通信单元4003。
关于本实施例提供的存储器、处理器以及通信单元的说明可以参照上述第一存储器、第一处理器以及第一通信单元的说明，故于此不再赘述。
图22为本申请实施例提供的业务服务器的示意图。如图22所示，本实施例提供的业务服务器5000，包括：存储器5001以及处理器5002，存储器5001设置为存储MBMS服务区域的管理程序；该管理程序被处理器5002执行时实现上述实施例提供的业务服务器侧的管理方法的步骤。
示例性地，业务服务器5000还可以包括通信单元5003。
关于本实施例提供的存储器、处理器以及通信单元的说明可以参照上述第一存储器、第一处理器以及第一通信单元的说明，故于此不再赘述。
此外，本申请实施例还提供一种计算机可读存储介质，存储有MBMS服务 区域的管理程序，该管理程序被处理器执行时实现图3至图7对应的任一实施例提供的管理方法的步骤。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块或单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块或单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些组件或所有组件可以被实施为由处理器，如数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于随机存取存储器(Random Access Memory，RAM)、只读存储器(Read-Only Memory，ROM)、电可擦除可编程只读存储器(Electrically Erasable Programmable Read Only Memory，EEPROM)、闪存或其他存储器技术、只读光盘(Compact Disc Read-Only Memory，CD-ROM)、数字多功能盘(Digital Versatile Disc，DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
工业实用性
本公开提供的一种MBMS服务区域的管理方法及系统，能够实现基于业务发起终端的物理位置变化而动态调整的MBMS服务区域。

Claims (33)

  1. 一种多媒体广播多播业务服务区域的管理方法，包括：
    第一通信网元接收携带专属多媒体广播多播业务标识的第一会话建立请求，所述第一通信网元根据接收到的位置通知消息或者第一区域判决消息，确定所述第一通信网元是否处于所述专属多媒体广播多播业务标识指示的专属多媒体广播多播业务的服务区域内；
    其中，所述专属多媒体广播多播业务标识用于指示基于业务发起终端的物理位置变化而动态调整服务区域的专属多媒体广播多播业务；所述位置通知消息用于指示所述业务发起终端当前处于所述第一通信网元的覆盖范围内。
  2. 根据权利要求1所述的方法，其中，所述第一通信网元根据接收到的位置通知消息或者第一区域判决消息，确定所述第一通信网元是否处于所述专属多媒体广播多播业务标识指示的专属多媒体广播多播业务的服务区域内，包括：
    所述第一通信网元根据接收到的位置通知消息，更新本地保存的区域判决参数，根据更新后的区域判决参数，确定所述第一通信网元是否处于所述专属多媒体广播多播业务的服务区域内；或者，
    所述第一通信网元根据接收到的第一区域判决消息，更新本地保存的区域判决参数，根据更新后的区域判决参数，确定所述第一通信网元是否处于所述专属多媒体广播多播业务的服务区域内；其中，所述第一区域判决消息携带所述第一通信网元邻接的第一通信网元的区域判决参数。
  3. 根据权利要求2所述的方法，其中，所述区域判决参数包括：动态区域范围标识和中心位置偏移标识；
    其中，所述动态区域范围标识用于指示所述专属多媒体多播广播业务的服务区域的范围；所述中心位置偏移标识用于指示所述第一通信网元与所述专属多媒体广播多播业务的服务区域中心之间的间隔。
  4. 根据权利要求3所述的方法，其中，所述根据更新后的区域判决参数，确定所述第一通信网元是否处于所述专属多媒体广播多播业务的服务区域内，包括：
    若所述第一通信网元本地保存的中心位置偏移标识小于所述动态区域范围标识，则确定所述第一通信网元处于所述专属多媒体广播多播业务的服务区域内；若所述第一通信网元本地保存的中心位置偏移标识大于或等于所述动态区域范围标识，则确定所述第一通信网元不处于所述专属多媒体广播多播业务的服务区域内。
  5. 根据权利要求3或4所述的方法，其中，所述第一通信网元根据接收到的位置通知消息，更新本地保存的区域判决参数，包括：若所述第一通信网元接收到所述位置通知消息，则所述第一通信网元将本地保存的中心位置偏移标识置0；
    所述第一通信网元根据接收到的第一区域判决消息，更新本地保存的区域判决参数，包括：若所述第一通信网元接收到所述第一区域判决消息，则所述第一通信网元将本地保存的中心位置偏移标识更新为所述第一区域判决消息中携带的所述第一通信网元邻接的第一通信网元的区域判决参数中的中心位置偏移标识，其中，所述第一区域判决消息中携带的中心位置偏移标识与所述邻接的第一通信网元本地保存的中心位置偏移标识之间的差值为1。
  6. 根据权利要求3、4或5所述的方法，其中，所述第一通信网元接收到位置通知消息后，所述方法还包括：
    所述第一通信网元向所述邻接的第一通信网元广播第二区域判决消息，其中，所述第二区域判决消息携带的中心位置偏移标识等于所述第一通信网元本地保存的中心位置偏移标识加1。
  7. 根据权利要求3、4或5所述的方法，其中，所述第一通信网元接收到第一区域判决消息后，所述方法还包括：
    若所述第一区域判决消息携带所述第一通信网元邻接的第一通信网元的区域判决参数中的中心位置偏移标识不等于所述第一通信网元本地保存的动态区域范围标识，则所述第一通信网元向所述邻接的第一通信网元广播第二区域判决消息，其中，所述第二区域判决消息携带的中心位置偏移标识等于所述第一通信网元本地保存的中心位置偏移标识加1。
  8. 根据权利要求3-7中任一项所述的方法，其中，所述区域判决参数还包括：序列号；
    所述第一通信网元接收到位置通知消息或者第一区域判决消息之后，所述方法还包括：
    所述第一通信网元根据接收到的位置通知消息，将本地保存的序列号加1；或者，
    所述第一通信网元根据接收到的第一区域判决消息，若确定所述第一区域判决消息携带的所述第一通信网元邻接的第一通信网元的区域判决参数中的序列号等于所述第一通信网元本地保存的区域判决参数内的序列号，则所述第一 通信网元丢弃接收到的所述第一区域判决消息。
  9. 根据权利要求1或2所述的方法，其中，所述第一通信网元接收携带专属多媒体广播多播业务标识的第一会话建立请求之前，所述方法还包括：
    所述第一通信网元接收专属多媒体广播多播业务标识以及动态区域范围标识；其中，所述动态区域范围标识用于指示所述专属多媒体多播广播业务的服务区域的范围。
  10. 根据权利要求1所述的方法，其中，所述第一通信网元包括基站。
  11. 一种多媒体广播多播业务服务区域的管理方法，包括：
    第二通信网元接收携带专属多媒体广播多播业务标识的第二会话建立请求；其中，所述专属多媒体广播多播业务标识用于指示基于业务发起终端的物理位置变化动态调整服务区域的专属多媒体广播多播业务；
    所述第二通信网元向第一通信网元发送携带所述专属多媒体广播多播业务标识的第一会话建立请求。
  12. 根据权利要求11所述的方法，其中，所述第二通信网元接收携带专属多媒体广播多播业务标识的第二会话建立请求之前，所述方法还包括：
    所述第二通信网元配置专属多媒体广播多播业务标识以及动态区域范围标识，并给所述专属多媒体广播多播业务标识所指示的专属多媒体广播多播业务预留独立的多播资源；其中，所述动态区域范围标识用于指示所述专属多媒体多播广播业务的服务区域的范围；
    所述第二通信网元向所述第一通信网元发送所述专属多媒体广播多播业务标识以及动态区域范围标识；
    所述第二通信网元向第三通信网元发送所述专属多媒体广播多播业务标识。
  13. 根据权利要求12所述的方法，其中，所述第二通信网元向所述第一通信网元发送所述专属多媒体广播多播业务标识以及动态区域范围标识，包括：
    所述第二通信网元通过配置消息向所述第一通信网元发送所述专属多媒体广播多播业务标识以及动态区域范围标识；或者，
    所述第二通信网元通过针对所述第一通信网元的链路连接建立请求的响应消息，向所述第一通信网元发送所述专属多媒体广播多播业务标识以及动态区域范围标识。
  14. 根据权利要求12所述的方法，其中，所述第二通信网元向所述第三通信网元发送所述专属多媒体广播多播业务标识，包括：
    所述第二通信网元通过单独的消息向所述第三通信网元发送所述专属多媒体广播多播业务标识；或者，
    所述第二通信网元通过链路连接建立消息向所述第三通信网元发送所述专属多媒体广播多播业务标识。
  15. 根据权利要求12、13或14所述的方法，其中，所述第一通信网元包括基站，所述第二通信网元包括多小区多播协调实体，所述第三通信网元包括移动管理实体。
  16. 一种多媒体广播多播业务服务区域的管理方法，包括：
    第二通信网元在检测到基于业务发起终端的物理位置变化动态调整服务区域的专属多媒体广播多播业务时，监测所述专属多媒体广播多播业务的业务发起终端所在的第一通信网元；
    在所述第二通信网元接收到携带专属多媒体广播多播业务标识的会话建立请求，或者，所述业务发起终端所在的第一通信网元发生切换时，所述第二通信网元向所述业务发起终端当前所在的第一通信网元发送位置通知消息；
    其中，所述专属多媒体广播多播业务标识用于指示所述专属多媒体广播多播业务，所述位置通知消息用于指示所述业务发起终端当前处于所述第一通信网元的覆盖范围内。
  17. 根据权利要求16所述的方法，其中，所述第二通信网元检测所述专属多媒体广播多播业务包括：
    所述第二通信网元在检测到一个数据链路的服务质量等级标识符处于专属服务质量等级标识符时，确认所述数据链路所承载的业务处于所述专属多媒体广播多播业务。
  18. 根据权利要求16或17所述的方法，其中，所述第二通信网元监测所述专属多媒体广播多播业务的业务发起终端所在的第一通信网元之前，所述方法还包括：
    所述第二通信网元接收专属多媒体广播多播业务标识。
  19. 根据权利要求16、17或18所述的方法，其中，所述第一通信网元包括基站，所述第二通信网元包括移动管理实体。
  20. 一种多媒体广播多播业务服务区域的管理方法，包括：
    业务发起终端申请数据链路；
    所述业务发起终端通过所述数据链路发送携带专属业务标识的数据；其中， 所述专属业务标识用于指示基于所述业务发起终端的物理位置变化动态调整服务区域的专属多媒体广播多播业务，所述专属业务标识与专属多媒体广播多播业务标识之间存在对应关系。
  21. 根据权利要求20所述的方法，其中，所述业务发起终端申请数据链路，包括：所述业务发起终端采用专属服务质量等级标识符申请数据链路。
  22. 一种多媒体广播多播业务服务区域的管理方法，包括：
    业务服务器接收携带专属业务标识的数据；其中，所述专属业务标识用于指示基于业务发起终端的物理位置变化动态调整服务区域的专属多媒体广播多播业务；
    所述业务服务器根据所述专属业务标识，确定与所述专属业务标识对应的专属多媒体广播多播业务标识，触发会话建立流程。
  23. 根据权利要求22所述的方法，其中，所述触发会话建立流程包括：
    所述业务服务器向广播组播业务中心发送会话建立请求，其中，所述会话建立请求携带所述数据、所述专属多媒体广播多播业务标识、以及所述专属多媒体广播多播业务标识对应的路由信息。
  24. 一种多媒体广播多播业务服务区域的管理系统，包括：第一通信网元以及第二通信网元；所述第一通信网元连接所述第二通信网元；
    其中，所述第二通信网元设置为向所述第一通信网元发送携带专属多媒体广播多播业务标识的第一会话建立请求；
    所述第一通信网元设置为接收所述第一会话建立请求，根据接收到的位置通知消息或者第一区域判决消息，确定所述第一通信网元是否处于所述专属多媒体广播多播业务标识指示的专属多媒体广播多播业务的服务区域内；
    其中，所述专属多媒体广播多播业务标识用于指示基于业务发起终端的物理位置变化动态调整服务区域的专属多媒体广播多播业务；所述位置通知消息用于指示所述业务发起终端当前处于所述第一通信网元的覆盖范围内。
  25. 根据权利要求24所述的系统，其中，所述第二通信网元，设置为在接收到携带所述专属多媒体广播多播业务标识的第二会话建立请求后，向所述第一通信网元发送所述第一会话建立请求。
  26. 根据权利要求24或25所述的系统，其中，所述系统还包括：第三通信网元，所述第三通信网元分别连接所述第一通信网元和所述第二通信网元；
    所述第三通信网元，设置为在检测到所述专属多媒体广播多播业务时，监 测所述专属多媒体广播多播业务的业务发起终端所在的第一通信网元；
    所述第三通信网元，设置为根据接收到的携带所述专属多媒体广播多播业务标识的第三会话建立请求，或者，根据所述业务发起终端所在的第一通信网元的切换，向所述业务发起终端当前所在的第一通信网元发送所述位置通知消息。
  27. 根据权利要求24、25或26所述的系统，其中，所述系统还包括：业务发起终端，设置为通过数据链路发送携带专属业务标识的数据，其中，所述专属业务标识用于指示所述专属多媒体广播多播业务，且所述专属业务标识与所述专属多媒体广播多播业务标识之间存在对应关系。
  28. 根据权利要求27所述的系统，其中，所述系统还包括：业务服务器，设置为接收携带所述专属业务标识的数据，根据所述专属业务标识，确定与所述专属业务标识对应的专属多媒体广播多播业务标识，触发会话建立流程。
  29. 根据权利要求26、27或28所述的系统，其中，所述第一通信网元包括基站，所述第二通信网元包括多小区多播协调实体，所述第三通信网元包括移动管理实体。
  30. 一种通信网元，包括：存储器以及处理器，所述存储器设置为存储多媒体广播多播业务服务区域的管理程序，所述管理程序被所述处理器执行时实现如权利要求1至19中任一项所述的管理方法。
  31. 一种终端，包括：存储器以及处理器，所述存储器设置为存储多媒体广播多播业务服务区域的管理程序，所述管理程序被所述处理器执行时实现如权利要求20至21中任一项所述的管理方法。
  32. 一种业务服务器，包括：存储器以及处理器，所述存储器设置为存储多媒体广播多播业务服务区域的管理程序，所述管理程序被所述处理器执行时实现如权利要求22至23中任一项所述的管理方法。
  33. 一种计算机可读介质，存储有多媒体广播多播业务服务区域的管理程序，所述管理程序被处理器执行时实现如权利要求1至23中任一项所述的管理方法。
PCT/CN2018/088005 2017-11-30 2018-05-23 Mbms服务区域的管理方法及系统 WO2019104960A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP18884339.5A EP3720155A4 (en) 2017-11-30 2018-05-23 PROCEDURE AND SYSTEM FOR ADMINISTERING AN MBMS SERVICE AREA
KR1020207004249A KR102277535B1 (ko) 2017-11-30 2018-05-23 Mbms 서비스 영역의 관리 방법 및 시스템

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711242542.X 2017-11-30
CN201711242542.XA CN107770727B (zh) 2017-11-30 2017-11-30 一种mbms服务区域的管理方法及系统

Publications (1)

Publication Number Publication Date
WO2019104960A1 true WO2019104960A1 (zh) 2019-06-06

Family

ID=61277091

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/088005 WO2019104960A1 (zh) 2017-11-30 2018-05-23 Mbms服务区域的管理方法及系统

Country Status (4)

Country Link
EP (1) EP3720155A4 (zh)
KR (1) KR102277535B1 (zh)
CN (1) CN107770727B (zh)
WO (1) WO2019104960A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113395675A (zh) * 2021-06-02 2021-09-14 联合汽车电子有限公司 数据处理方法、车辆控制系统及可读存储介质

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107770727B (zh) * 2017-11-30 2020-04-03 中兴通讯股份有限公司 一种mbms服务区域的管理方法及系统
CN110602628B (zh) * 2018-05-23 2021-04-20 华为技术有限公司 车联网中终端加入多播组的方法、网关和服务器
WO2020035129A1 (en) * 2018-08-13 2020-02-20 Huawei Technologies Co., Ltd. Providing multicast/broadcast services in 5g networks
CN113891255B (zh) * 2018-11-27 2023-04-11 华为技术有限公司 一种通信方法、装置及系统
CN114600472B (zh) * 2019-10-30 2023-04-28 华为技术有限公司 通信方法及装置
CN115150751A (zh) * 2021-03-30 2022-10-04 维沃移动通信有限公司 业务数据处理方法、装置及设备
CN113891326B (zh) * 2021-10-15 2023-06-06 中国联合网络通信集团有限公司 一种业务传输方法、装置及存储介质
WO2024147714A1 (en) * 2023-01-07 2024-07-11 Samsung Electronics Co., Ltd. Handling migration status information in mission critical network

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100189027A1 (en) * 2007-06-19 2010-07-29 Panasonic Corporation Radio transmission method, radio reception method, radio transmission-reception method, radio transmission apparatus, radio reception apparatus, radio transmission-reception system, base station apparatus, and communication terminal
CN102395110A (zh) * 2006-01-24 2012-03-28 北京三星通信技术研究有限公司 Lte系统中支持mbms业务传输的方法
CN102740234A (zh) * 2011-04-12 2012-10-17 中兴通讯股份有限公司 一种mbms挂起方法、系统及mce
CN107770727A (zh) * 2017-11-30 2018-03-06 中兴通讯股份有限公司 一种mbms服务区域的管理方法及系统

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100689390B1 (ko) * 2003-10-02 2007-03-02 삼성전자주식회사 멀티미디어 방송/멀티캐스트 서비스의 서비스 유효성 정보를 송수신하는 방법
EP2131603B1 (en) * 2007-03-23 2015-09-02 Panasonic Intellectual Property Corporation of America Radio communication base station device and radio communication method
CN102088660B (zh) * 2009-12-04 2014-08-20 华为技术有限公司 一种实现多媒体广播多播动态区域管理的方法、装置
CN103347250B (zh) * 2013-07-18 2016-03-23 重庆邮电大学 一种动态调整多媒体广播单频网区域的方法
CN105376718B (zh) * 2014-08-25 2020-03-31 中兴通讯股份有限公司 Lte集群通信的方法、用户设备及第一网元设备
WO2016041135A1 (zh) * 2014-09-15 2016-03-24 华为技术有限公司 增强型广播组播业务的处理网元及其广播的方法
WO2017163695A1 (ja) * 2016-03-23 2017-09-28 日本電気株式会社 コアノード、加入者情報管理装置、通信システム、通信方法、及び、コンピュータ可読媒体
CN113556691B (zh) * 2016-04-01 2022-12-02 北京三星通信技术研究有限公司 一种发送v2x消息的方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102395110A (zh) * 2006-01-24 2012-03-28 北京三星通信技术研究有限公司 Lte系统中支持mbms业务传输的方法
US20100189027A1 (en) * 2007-06-19 2010-07-29 Panasonic Corporation Radio transmission method, radio reception method, radio transmission-reception method, radio transmission apparatus, radio reception apparatus, radio transmission-reception system, base station apparatus, and communication terminal
CN102740234A (zh) * 2011-04-12 2012-10-17 中兴通讯股份有限公司 一种mbms挂起方法、系统及mce
CN107770727A (zh) * 2017-11-30 2018-03-06 中兴通讯股份有限公司 一种mbms服务区域的管理方法及系统

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "GCSE Counting using MooD Consumption Report", SA WG2 MEETING #109, S 2-151572, 29 May 2015 (2015-05-29), XP050976879 *
See also references of EP3720155A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113395675A (zh) * 2021-06-02 2021-09-14 联合汽车电子有限公司 数据处理方法、车辆控制系统及可读存储介质
CN113395675B (zh) * 2021-06-02 2023-07-04 联合汽车电子有限公司 数据处理方法、车辆控制系统及可读存储介质

Also Published As

Publication number Publication date
CN107770727B (zh) 2020-04-03
KR20200022038A (ko) 2020-03-02
CN107770727A (zh) 2018-03-06
KR102277535B1 (ko) 2021-07-14
EP3720155A4 (en) 2021-08-25
EP3720155A1 (en) 2020-10-07

Similar Documents

Publication Publication Date Title
WO2019104960A1 (zh) Mbms服务区域的管理方法及系统
US10687179B2 (en) Service continuity for group communication over LTE eMBMS
US10993086B2 (en) Method, system, and apparatus for transmitting group communication service data
US10462719B2 (en) Method, device and system for supporting transmission of a group service
US20200329347A1 (en) Multicast/broadcast service to radio access networks with core networks
KR102689205B1 (ko) 브로드캐스트/멀티캐스트 서비스 관리 방법, 장치, 전자 설비, 저장 매체
US20170111934A1 (en) Method for obtaining ue counting result, method and apparatus for suspending data transmission
Liebhart et al. LTE for public safety
CN115348619A (zh) 组播业务的处理方法、装置、相关设备及存储介质
KR20170113755A (ko) 무선통신시스템에서 그룹통신 및 멀티캐스트 서비스를 위한 서비스 연속성 제공 방법 및 장치
US9294294B2 (en) Method and arrangement for efficient group communication
CN102291679A (zh) 一种mbms承载释放通知的方法和设备
CN115551082A (zh) 一种多播业务的通信方法、装置及系统
Nguyen et al. LTE Broadcast for Public Safety
CN115996435A (zh) 一种通信方法、装置及设备

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: 18884339

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20207004249

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018884339

Country of ref document: EP

Effective date: 20200630