WO2015096270A1 - 一种保持业务连续性的方法及设备 - Google Patents

一种保持业务连续性的方法及设备 Download PDF

Info

Publication number
WO2015096270A1
WO2015096270A1 PCT/CN2014/071599 CN2014071599W WO2015096270A1 WO 2015096270 A1 WO2015096270 A1 WO 2015096270A1 CN 2014071599 W CN2014071599 W CN 2014071599W WO 2015096270 A1 WO2015096270 A1 WO 2015096270A1
Authority
WO
WIPO (PCT)
Prior art keywords
mbms service
scheduling
service
stop
user equipment
Prior art date
Application number
PCT/CN2014/071599
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 KR1020167020051A priority Critical patent/KR101815409B1/ko
Priority to JP2016543116A priority patent/JP6480459B2/ja
Priority to EP14873191.2A priority patent/EP3076690B1/en
Priority to EP17205709.3A priority patent/EP3373613B1/en
Priority to CN201480071365.1A priority patent/CN105850161B/zh
Publication of WO2015096270A1 publication Critical patent/WO2015096270A1/zh
Priority to US15/194,116 priority patent/US10206224B2/en
Priority to US16/227,176 priority patent/US10694540B2/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/20Control channels or signalling for resource management
    • H04W72/23Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/12Wireless traffic scheduling
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/30Connection release
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/40Connection management for selective distribution or broadcast
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W84/00Network topologies
    • H04W84/02Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04Large scale networks; Deep hierarchical networks
    • H04W84/042Public Land Mobile systems, e.g. cellular systems

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and device for maintaining business continuity. Background technique
  • a multimedia broadcast multicast service is a technology that simultaneously transmits the same service to multiple user equipments (UEs, User Equipments) by using a broadcast channel.
  • UEs user equipments
  • a group of UEs receiving the same service use the same downlink configuration to perform services. Receive, do not have to establish their own link for each UE.
  • the Multimedia Broadcast Multicast Service Single Frequency Network is a transmission method for synchronous transmission in multiple cells at the same frequency at the same time. This transmission mode can effectively save frequency resources and improve spectrum utilization. Rate, and increase coverage.
  • Multicast/Multicast Coordination Entity is a logical entity that can configure multiple MBSFN areas for MBSFN transmission and allocate all evolved base stations (eNBs, Evolved Node Bs) in the MBSFN area. Radio resources for MBSFN transmission.
  • eNBs evolved base stations
  • Evolved Node Bs evolved Node Bs
  • the MCE informs the UEs that receive the service statistics in a statistical manner. When the number of UEs receiving the service is less than a certain number, the MCE may determine to disable the MBSFN transmission of the service.
  • the specific implementation process is as follows: The MCE determines to close the MBSFN transmission of a service.
  • the configuration of the eNB is updated by the MBMS scheduling information, and the service information is not carried in the new configuration; the eNB notifies the UE to update the service configuration, and the service information is not carried in the new service configuration; after receiving the updated service configuration, the UE receives the updated service configuration. If the service is not in the new configuration information, the service is considered to be stopped. If the UE wants to continue to receive the service, the unicast service needs to be triggered to continue to receive the MBMS service through the unicast service.
  • the UE needs to detect that the MBSFN transmission is closed, and then continue to receive the MBMS service by establishing a unicast bearer. It is not until the unicast bearer is established that the MBMS service can continue to be accepted. Since the unicast bearer setup takes a period of time, during which the UE receives the service, it experiences an interruption. Summary of the invention
  • the technical problem to be solved by the present application is that after the MCE determines to stop scheduling a service, the UE that needs to continue to receive the service needs to establish a unicast bearer, and how to reduce the service interruption time caused by the unicast bearer establishment process.
  • the present application provides a method and a device for maintaining service continuity, which can effectively reduce the service interruption time of the UE receiving the service after the MCE stops scheduling a service.
  • the present application provides a method for maintaining service continuity, including: receiving, by a base station, a first notification of a MBMS service stop scheduling of a multimedia broadcast multicast service sent by a multi-cell/multicast cooperative entity, where the MBMS service stops scheduling first
  • the notification is that the multi-cell/multicast cooperative entity determines a notification that is sent to the base station when the MBMS service is closed; the base station sends an MBMS service stop scheduling information to the user equipment according to the first notification that the MBMS service stops scheduling;
  • the base station continues to schedule the MBMS service until the predetermined condition is met and then stops scheduling the MBMS service.
  • the MBMS service stop scheduling first notification carries a delay stop indication, to indicate that the base station delays scheduling to stop the MBMS service.
  • the predetermined condition is one of the following conditions: receiving a multi-cell/multicast collaboration entity
  • the sent MBMS service stops scheduling the second notification, the MBMS service stop scheduling second notification indicates that the base station stops scheduling the MBMS service; or after receiving the first notification that the MBMS service stops scheduling, the MBMS service stops scheduling is reached.
  • a time point of the notification indication or a first predetermined time after receiving the first notification that the MBMS service stops scheduling; or after receiving the first notification that the MBMS service stops scheduling, reaching a second predetermined time point.
  • the MBMS service stop scheduling first notification includes the delay stop time length information or a predetermined stop time stamp information .
  • the MBMS service stop scheduling, the first notification, indicating the MBMS service The scheduling is stopped when the predetermined condition is met.
  • the base station uses the configuration information that does not carry the MBMS service in the point-to-multipoint control channel message as the MBMS service stop scheduling information that is sent to the user equipment.
  • the base station notifies the user equipment of the service stop scheduling information, or sends a delay stop indication to Informing the user equipment that the MBMS service is scheduled to be stopped.
  • the MBMS service stop scheduling information carries an upcoming stop indication, to notify The user equipment will stop scheduling the MBMS service, and the user equipment will continue to receive the MBMS service until receiving the MBMS service stop scheduling notification.
  • the base station is configured by using a point-to-multipoint control channel, a paging control channel, and an MBMS transmission channel. Any one of the scheduling information transmits the delay stop indication.
  • the application provides a method for maintaining service continuity, the method includes: receiving, by a user equipment, MBMS service stop scheduling information from a base station, determining that the base station is about to stop scheduling the MBMS service; and the user equipment continues to monitor The scheduling information of the MBMS service; receiving the MBMS service according to the scheduling information of the MBMS service.
  • the receiving the MBMS service is stopped.
  • the step of the user equipment receiving the MBMS service stop scheduling information from the base station includes: the user The device receives the point-to-multipoint control channel message, and determines that the base station is about to stop scheduling the MBMS service according to the configuration information that does not carry the MBMS service in the message.
  • the MBMS service stop scheduling information carries an indication that the MBMS service is about to stop, and is used to indicate that the user equipment is about to stop scheduling, and the user equipment is configured according to The delay stop indication continues to monitor the scheduling information of the MBMS service until the MBMS service stop scheduling notification is received.
  • the user equipment receives an MBMS service delay stop indication from the base station, or after the user equipment receives the service stop scheduling information, and stops the indication according to the MBMS service delay. And continuing to monitor scheduling information of the MBMS service.
  • a fifth possible implementation manner of the second aspect by using a point-to-multipoint control channel, a paging control channel, and an MBMS transmission channel scheduling information Any of the types of receiving the delay stop.
  • the method further includes: determining, by the user equipment, that the MBMS service belongs to stop scheduling, And if the user equipment needs to continue to receive the MBMS service after the base station stops scheduling the MBMS service, triggering establishment of the unicast bearer, and stopping the point corresponding to the MBMS service after the unicast bearer is established.
  • the point service channel receives the MBMS service
  • the process of establishing the triggered unicast bearer includes: the access layer of the user equipment of the user equipment sends an indication that the MBMS service cannot continue to be received to the upper layer of the user equipment, where the user equipment is sent to the application server Sending an indication that the MBMS service cannot continue to be received, the application server sends a trigger request for establishing a thin bearer to the user equipment, and the user equipment of the user triggers the establishment of the unicast bearer according to the trigger request.
  • the application provides a method for maintaining service continuity, the method comprising: determining, by a multi-cell/multicast cooperative entity, an MBMS service that needs to be closed; sending an MBMS service stop scheduling notification to a base station, where the MBMS service stops scheduling Notifying the base station that the MBMS service meets a predetermined condition, stopping scheduling, and instructing the base station to continue to schedule the MBMS service.
  • the MBMS service stop scheduling notification includes the time length information of the scheduled scheduled time or the scheduled stop timestamp information or the indication information of stopping the MBMS service And indicating that the base station continues to schedule the MBMS service for a predetermined time.
  • the step of determining, by the multi-cell/multicast cooperative entity, the MBMS service that needs to be closed includes: The multi-cell/multicast cooperative entity notifies the base station to count the user equipment that receives the MBMS service; determines the number of user equipments of the MBMS service according to the statistical response of the base station, and the number of user equipments that receive the MBMS service When less than the predetermined threshold, Determining that the MBMS service needs to be shut down or the multi-cell/multicast cooperative entity receives the request information that is sent by the application server to close the MBMS service.
  • the step of: sending the MBMS service stop scheduling notification to the base station includes: The configuration information of the base station is updated by the MBMS scheduling information, and the updated configuration information does not carry the configuration information of the MBMS service that needs to be closed, as the MBMS service stop scheduling notification sent to the base station.
  • the method for maintaining service continuity includes: receiving, by a group communication server, information that is received by a user equipment and receiving a group service by using a multimedia broadcast multicast service MBSFN; and the group communication server is from a multi-cell Receiving, by the multicast cooperative entity, the MBSFN transmission stop notification for receiving the group service, the group communication server determining that the MBSFN transmission is about to stop according to the MBSFN transmission stop; and the group communication server notifying the user equipment A unicast bearer is set up, so that the user equipment continues to receive the group service by using the unicast bearer after the MBSFN for receiving the group service stops.
  • the MBSFN transmission stop notification includes service information that stops scheduling, and the service information includes at least one of the MBSFN area information and an identifier of an MBMS.
  • the service information includes at least one of the MBSFN area information and an identifier of an MBMS.
  • the method further includes: after the user equipment establishes a unicast bearer, The group communication server notifies the multi-cell/multicast cooperative entity to stop the MBSFN transmission.
  • the application provides a method for maintaining service continuity, the method comprising: determining, by a multi-cell/multicast cooperative entity, an MBSFN transmission that needs to be stopped; notifying the group communication server that the MBSFN transmission is stopped, so that the group The communication server notifies the user equipment to establish a unicast bearer, so that the user equipment continues to receive the group service by replacing the MBSFN by the unicast bearer after the MBSFN transmission is stopped.
  • the step that the multi-cell/multicast cooperative entity determines that the MBSFN transmission needs to be stopped includes: the multi-cell/multicast cooperative entity notifying the base station of the statistics Receiving the user equipment of the MBMS service; determining, according to the statistical response of the base station, the number of user equipments of the MBMS service, and receiving the MBMS service in the When the number of user equipments is less than a predetermined threshold, it is determined that the MBSFN transmission mode of the MBMS service needs to be stopped.
  • the MBSFN transmission is about to stop to notify the service information that includes the stop scheduling, where the service information includes At least one of the MBSFN area information and the identifier of the MBMS.
  • the application provides a method for maintaining service continuity, where the method includes: the user equipment reports information of receiving a group service through a multimedia broadcast multicast service single frequency network MBSFN to a group communication server;
  • the unicast bearer establishes a notification, establishes a unicast bearer, and continues to listen to the scheduling information that carries the group service.
  • the information about the group service includes: at least one of the MBSFN area information and an identifier of the MBMS.
  • the method further includes: the user equipment registering with the group communication server.
  • the method further includes: completing the unicast bearer setup Afterwards, the user equipment stops listening to scheduling information that carries the group service.
  • a base station includes a receiving module and a scheduling module, where: the receiving module is configured to receive a first notification that the MBMS service stops scheduling of the multimedia broadcast multicast service sent by the multi-cell/multicast cooperative entity, The MBMS service stop scheduling first notification is that the multi-cell/multicast cooperative entity determines a notification sent to the base station when the MBMS service is closed; the scheduling module is configured to receive the MBMS in the receiving module After the service stops scheduling the first notification, the MBMS service stop scheduling information is sent to the user equipment, and the MBMS service is continued to be scheduled until the predetermined condition is met, and then the MBMS service is stopped.
  • the MBMS service stop scheduling first notification carries a delay stop indication, to indicate that the base station delays scheduling the MBMS service.
  • the scheduling module stops scheduling the MBMS service when one of the following conditions is met: the receiving module receives a second notification that the MBMS service stops scheduling sent by the multi-cell/multicast cooperative entity, where the MBMS service stops. Dispatching the second notification to indicate that the base station stops scheduling the MBMS service stop scheduling; or the time point after the receiving module receives the first notification of stopping the scheduling of the MBMS service, reaching the first notification indication that the MBMS service stops scheduling; The receiving module receives the first predetermined time after receiving the first notification that the MBMS service stops scheduling.
  • the MBMS service stop scheduling first notification includes the delay stop time length information or a predetermined stop timestamp information .
  • the MBMS service stop scheduling, the first notification, indicating the MBMS The scheduling is stopped when the service meets the predetermined conditions.
  • the scheduling module is configured by using a point-to-multipoint control channel message
  • the configuration information of the MBMS service is not carried as the MBMS service stop scheduling information sent to the user equipment.
  • the scheduling module sends a delay stop indication at the same time as or after the user equipment is notified to stop the scheduling information of the service In order to inform the user equipment that the MBMS service is scheduled to be stopped.
  • the MBMS service stop scheduling information carrying the MBMS service is about to stop An indication to inform the user equipment that the MBMS service will be scheduled to be stopped.
  • the scheduling module by using a point-to-multipoint control channel, a paging control channel, and an MBMS transmission Any one of the channel scheduling information transmits the delay stop indication.
  • a user equipment includes a first receiving module, a listening module, and a second receiving module, where: the first receiving module is configured to receive MBMS service stop scheduling information from a base station, and determine the The MBMS service is about to stop; the listening module is used to continue The scheduling information of the MBMS service is continuously monitored; the second receiving module is configured to receive the MBMS service according to the scheduling information of the MBMS service that is monitored by the monitoring module.
  • the second receiving module stops receiving the MBMS service. .
  • the first receiving module is configured to receive a point-to-multipoint control channel message, according to the The configuration information that does not carry the MBMS service in the message determines that the base station is about to stop scheduling the MBMS service.
  • the MBMS service stop scheduling information carries an indication that the MBMS service is about to stop scheduling, and is used to indicate that the MBMS service of the user equipment is about to stop scheduling
  • the monitoring module is configured to continue to monitor the scheduling information of the MBMS service according to the MBMS service to stop scheduling indication, until the MBMS service stop notification information is received.
  • the first receiving module is configured to receive an MBMS service delay stop indication from the base station, or after receiving the service stop scheduling information, where the monitoring module is And configured to continue to monitor scheduling information of the MBMS service according to the MBMS service delay stop indication.
  • the first receiving module by using a point-to-multipoint control channel, a paging control channel, Any one of the MBMS transmission channel scheduling information receives the delay stop indication.
  • the user equipment further includes a unicast establishing module, where the unicast establishing module is configured to stop scheduling in the base station After the MBMS service continues to receive the MBMS service, triggering the establishment of the unicast bearer; after the unicast bearer is established, the second receiving module stops the point-to-multipoint traffic channel corresponding to the MBMS service and receives the MBMS. business.
  • a multi-cell/multicast cooperation entity includes a determining module and a scheduling module, where: the determining module is configured to determine an MBMS service that needs to be closed; And when the determining module determines that the MBMS service needs to be shut down, sending an MBMS service stop scheduling notification to the base station, where the MBMS service stops scheduling notification The scheduling stops when the MBMS service of the base station meets a predetermined condition, and the scheduling module instructs the base station to continue scheduling the MBMS service.
  • the MBMS service stop scheduling notification includes the time length information of the scheduled scheduled time or the scheduled stop timestamp information or an indication that the MBMS service is to be stopped.
  • Information to indicate that the base station continues to schedule the MBMS service for a predetermined time.
  • the determining module is configured to notify a user that receives the MBMS service by notifying the base station
  • the device determines the number of user equipments of the MBMS service according to the statistics of the base station, and determines that the MBSFN transmission mode of the MBMS service needs to be closed when the number of user equipments that receive the MBMS service is less than a predetermined threshold.
  • the scheduling module by using the MBMS scheduling information, to update the configuration information of the base station
  • the updated configuration information does not carry the configuration information of the MBMS service that needs to be closed, as the MBMS service stop scheduling notification sent to the base station.
  • a base station includes a processor, a receiver, a transmitter, and a memory, where the processor is coupled to the receiver, the transmitter, and the memory, where: the processor is configured to control receiving Receiving a first notification of the MBMS service stop scheduling of the multimedia broadcast multicast service sent by the multi-cell/multicast cooperative entity, where the first notification of the MBMS service stop scheduling is when the multi-cell/multicast cooperative entity determines to close the MBMS service Sending, to the base station, a notification, after receiving the first notification that the MBMS service stops scheduling, controlling the sender to send MBMS service stop scheduling information to the user equipment, where the processor continues to schedule the MBMS service until a predetermined condition is met Stop scheduling the MBMS service; the memory is used to store the MBMS data.
  • a user equipment in an eleventh aspect, includes a processor, a receiver, and a memory, where the processor is coupled to the receiver and the memory, where: the processor is configured to control the The receiver receives the MBMS service stop scheduling information from the base station, determines that the base station stops scheduling the MBMS service when the predetermined condition is met, continues to monitor the scheduling information of the MBMS service, and controls the receiver to monitor according to the processor.
  • the MBMS Scheduling information of the service receiving the MBMS service
  • the memory is configured to store the MBMS service data.
  • a multi-cell/multicast cooperation entity includes a processor, a transmitter, and a memory, where the processor is coupled to the transmitter and the memory, respectively, where:
  • the processor is configured to determine an MBMS service that needs to be shut down, and control the sender to send an MBMS service stop scheduling notification to the base station, where the MBMS service stop scheduling notification informs the base station that the MBMS service meets a predetermined condition, and stops scheduling,
  • the processor instructs the base station to continue to schedule the MBMS service;
  • the memory is configured to store the MBMS service data.
  • a group communication server includes a first receiving module, a second receiving module, and a notification module, where: the first receiving module is configured to receive a multimedia broadcast group reported by the user equipment.
  • the broadcast service single frequency network MBSFN receives the information of the group service;
  • the second receiving module is configured to receive, by the multi-cell/multicast cooperation entity, the MBSFN transmission stop notification for receiving the group service;
  • the notification module is used by Notifying the user equipment to establish a unicast bearer, so that the user equipment continues to receive the group service by using the unicast bearer after the MBSFN for receiving the group service stops.
  • the MBSFN transmission stop notification includes service information that stops scheduling, where the service information includes at least the MBSFN information and an identifier of an MBMS One.
  • the notification module is further configured to establish a unicast bearer on the user equipment Thereafter, the multi-cell/multicast cooperative entity is notified to stop the MBSFN transmission.
  • a multi-cell/multicast cooperation entity includes a determining module and a notification module, where: the determining module is configured to determine an MBSFN transmission that needs to be stopped; The module is configured to notify the group communication server that the MBSFN transmission is stopped after the determining module determines that the MBSFN transmission needs to be stopped, so that the group communication server notifies the user equipment to establish a unicast bearer, so that the user equipment After the MBSFN transmission is stopped, the group service is continuously received by the unicast bearer instead of the MBSFN.
  • the determining module by notifying a base station, to the user equipment that receives the MBMS service, determining, according to the statistical response of the base station, the MBMS service The number of user equipments at which the MBMS is received When the number of user equipments of the service is less than a predetermined threshold, it is determined that the MBSFN transmission mode of the MBMS service needs to be stopped.
  • the MBSFN transmission stop notification includes the service information that stops scheduling, the service The information includes at least one of the MBSFN information and an identifier of the MBMS.
  • a user equipment includes a reporting module and a unicast bearer establishing module, where: the reporting module is configured to report the MBSFN receiving group to the group communication server through the multimedia broadcast multicast service single frequency network The information of the service; the unicast bearer establishing module is configured to establish a unicast bearer according to the MBSFN transmission stop notification of the group communication server, and continue to listen to the bearer while continuing to receive the group service after the MBSFN transmission is stopped. Scheduling information of the group of services.
  • the information of the group service includes at least one of the MBSFN information and an identifier of the MBMS.
  • the reporting module is further configured to register with the group communication server.
  • the unicast bearer establishing module is After the unicast bearer is established, the scheduling information that carries the group service is stopped.
  • a group communication server includes a processor, a receiver, and a memory, wherein the processor is coupled to the receiver and the memory, respectively, wherein: the processor is used to control Receiving, by the user equipment, the information of the group service received by the multimedia broadcast multicast service single frequency network MBSFN, and controlling the receiver to receive the information for receiving the group service from the multi-cell/multicast cooperation entity
  • the MBSFN transmission stop notification notifying the user equipment to establish a unicast bearer, so that the user equipment continues to receive the group service by using the unicast bearer after the MBSFN for receiving the group service stops;
  • a memory is used to store the set of business data.
  • a multi-cell/multicast cooperation entity includes a processor, a transmitter, and a memory, where the processor is coupled to the transmitter and the storage, respectively.
  • the processor is configured to determine an MBSFN transmission that needs to be stopped, and control the sender to send a notification to the group communication server to notify the group communication server that the MBSFN transmission is stopped, so that the group communication server notifies the
  • the user equipment establishes a unicast bearer, so that the user equipment continues to receive the group service by replacing the MBSFN by using the unicast bearer after the MBSFN transmission stops; the memory is used to store data.
  • a user equipment including a processor, a receiver, and a memory, where the processor is coupled to the receiver and the memory, where: the processor is configured to communicate to a group
  • the server reports the information of the group service through the multimedia broadcast multicast service single frequency network MBSFN, and controls the receiver to receive the notification of the group communication server, according to the MBSFN transmission stop notification of the group communication server, after the MBSFN transmission stops
  • the group service needs to continue to be received, the unicast bearer is established, and the scheduling information that carries the group service is continuously monitored; the memory is used to store data.
  • the base station receives the MBMS service stop scheduling notification sent by the MCE, and the base station sends a notification to the user equipment MBMS service stop scheduling information, and continues to schedule the MBMS service.
  • the MCE determines to stop the scheduling of an MBMS service, and the user equipment that needs to continue to receive the MBMS service can continue to receive the service in the process of establishing the unicast bearer, thereby effectively reducing the scheduling of the service, and the user equipment needs to continue receiving.
  • This service establishes a service interruption time in the process of unicast bearer, giving the user a better experience.
  • FIG. 1 is a flowchart of a method for maintaining service continuity according to an embodiment of the present invention.
  • FIG. 2 is a flowchart of a method for maintaining service continuity according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of an embodiment of the present invention.
  • FIG. 4 is a flow chart of a method for maintaining business continuity according to an embodiment of the present invention.
  • FIG. 5 is a diagram of five types of business continuity maintained by an embodiment of the present invention.
  • FIG. 6 is a flowchart of a method for maintaining service continuity according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a base station according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a user equipment according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a multi-cell/multicast cooperative entity according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of two base stations according to an embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of two types of user equipment according to an embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram of a two-type multi-cell/multicast cooperative entity according to an embodiment of the present invention.
  • FIG. 14 is a schematic structural diagram of a group communication server according to an embodiment of the present invention;
  • FIG. 14 is a schematic diagram of a third embodiment of the present invention.
  • a schematic diagram 15 of a multi-cell/multicast cooperative entity is provided in the embodiment of the present invention: a schematic structural diagram of three types of user equipments;
  • FIG. 16 is a schematic structural diagram of a two-group communication server according to an embodiment of the present invention
  • FIG. 17 is a schematic structural diagram of four multi-cell/multicast cooperation entities according to an embodiment of the present invention. Schematic diagram of the structure of the user equipment
  • FIG. 1 is a flowchart of a first method for maintaining service continuity according to an embodiment of the present invention. This embodiment is described in terms of a base station.
  • the method for maintaining service continuity in this embodiment includes:
  • the base station receives the first notification that the MBMS service stops scheduling sent by the multi-cell/multicast cooperative entity;
  • the multi-cell/multicast coordination entity first triggers the base station (eNB, Evolved Node B) to collect the user equipment that receives an MBMS service, and the eNB statistically determines the number of user equipments of the MBMS service, and receives the When the user equipment of the MBMS service is less than the predetermined threshold, the MCE determines to stop the scheduling of the MBMS service.
  • the MCE informs the eNB to stop scheduling the MBMS service that receives the user equipment less than the predetermined threshold, such as stopping the scheduling of the service 1.
  • the eNB receives the first notification that the MBMS service sent by the MCE stops scheduling.
  • the MBMS service stop scheduling first notification is a notification sent by the MCE to the base station when the MBMS service is closed.
  • the MBMS service stop scheduling first notification may be used to stop the scheduling when a certain MBMS service meets the predetermined condition. This predetermined condition may be after a certain time, or a fixed time point or a re-scheduled MBMS service stop scheduling, and the like. Of course, it can be other specified conditions.
  • the MBMS service stop scheduling first notification may further carry a delay stop indication, to indicate that the eNB delays scheduling the MBMS service.
  • the MBMS service stop scheduling first notification may further include delay stop time length information or stop time stamp information, and is used to specify that the eNB stops scheduling the MBMS service after delaying the specified time.
  • the MCE decides to stop the scheduling of the service 1, and then sends a service 1 to the eNB to stop scheduling the first notification, where the notification may be used to indicate that the service 1 is about to stop scheduling, or the first notification may carry a delay stop indication to indicate that the eNB delays scheduling.
  • Service 1 The eNB stops scheduling the service after stopping the scheduling of the service for a period of time according to the MBMS service delay stop indication. And may further specify a delay stop time, to indicate a stop scheduling time relative to the relative time of receiving the first notification of stopping the scheduling, such as 10 minutes, 5 minutes, two modification periods or other time information, or may be Specify timestamp information, such as specific timestamp information such as 12:30, 12:40.
  • the optional MBMS service stop scheduling first notification is carried by the MBMS scheduling information message.
  • the MBMS scheduling information does not carry the configuration information of the MBMS service, it indicates that the scheduling of the MBMS service is to be stopped.
  • the base station sends the MBMS service stop scheduling information to the user equipment according to the MBMS service stop scheduling first notification.
  • the eNB After receiving the first notification that the MBMS service of the MCE stops scheduling, the eNB sends the MBMS service stop scheduling information to the user equipment.
  • the eNB may use the configuration information that does not carry the MBMS service in the point-to-multipoint control channel message as the MBMS service stop scheduling information that is sent to the user equipment.
  • the MBMS service stop scheduling information may carry the MBMS service, and the scheduling indication is stopped, to notify the user that the device is about to stop scheduling the MBMS service.
  • the MBMS service stop notification is sent to the user equipment to notify the user equipment that the MBMS service is stopped.
  • a delay stop indication is sent to notify the user equipment to delay scheduling the MBMS at the same time as or after the eNB notifies the user equipment service stop scheduling information. After the scheduling is stopped when the MBMS service meets the predetermined condition, the scheduling of the MBMS service is stopped.
  • the MBMS service delay stop indication or the MBMS service upcoming stop scheduling indication may be adjusted by using a point-to-multipoint control channel, a paging control channel, and an MBMS transmission channel. Any one of the degree information is sent to the user equipment.
  • the delay stop indication may be sent by a counting request message carried on the point-to-multipoint control channel channel, for example by counting Adding a delay stop indication to the request or the MBMS service is about to stop the scheduling indication; if the delay stop indication is sent by the MBMS transmission channel scheduling information, the MBMS service channel stop position indication (MTCH stop ) field in the MBMS transmission channel scheduling information message may be A special value indicates a delay stop indication or the MBMS service is about to stop scheduling instructions.
  • MTCH stop MBMS service channel stop position indication
  • S103 The base station continues to schedule the MBMS service until the predetermined condition is met, and then stops scheduling the MBMS service.
  • the eNB continues to schedule the MBMS service. Specifically, the eNB continues to indicate the sending position of the MBMS in the MBMS transport channel scheduling information (MSI), so that the user equipment that needs to continue to receive the MBMS service triggers the establishment of the unicast bearer. During the unicast bearer process, there is no interruption or interruption of the MBMS service.
  • MSI transport channel scheduling information
  • the eNB may stop scheduling the MBMS service when one of the following conditions is met: receiving the second notification of the MBMS service stop scheduling sent by the MCE, the MBMS service stop scheduling second notification indicating that the MBMS service stops scheduling; or receiving the MBMS After the first notification of the service stop scheduling, the time point of the first notification indication that the MBMS service stops scheduling is reached; or the first predetermined time is passed after receiving the first notification that the MBMS service stops scheduling; or after receiving the first notification that the service stops scheduling , reaching the second predetermined time point.
  • the MCE sends a first notification that the MBMS service stops scheduling, notifies that a certain service is about to stop scheduling, and then, after a predetermined time, the MCE sends a second notification that the MBMS service stops scheduling.
  • the notification directly instructs the eNB to stop scheduling the MBMS service.
  • the MCE directly carries the delay stop indication in the first notification of the MBMS service stop scheduling, and stops the scheduling time point as a predefined time point, for example, after receiving the first notification that the MBMS service stops scheduling, the next next The start time of the modification period is stopped, or the delay may be further indicated in the first notification to indicate the specific delay time.
  • the eNB receives the first notification that the MBMS service of the MCE stops scheduling, and stops scheduling the service after a delay. Or stopping the scheduling of the MBMS service at a point in time when the first notification indication is further reached.
  • the MBMS service sent by the MCE stops scheduling the first notification, but Notifying a certain MBMS service to stop scheduling (that is, the first notification is a normal MBMS service stop scheduling notification), after receiving the notification, the eNB continues to schedule the MBMS for a first predetermined time, and the first predetermined time may be a system advance. Set time.
  • the user equipment After receiving the scheduling information of the MBMS service of the eNB, the user equipment determines that an MBMS service is about to stop, but continues to monitor the MSI for a period of time. If the user equipment needs to continue to receive the MBMS service, the establishment of the unicast bearer may be triggered. After the unicast bearer is established, the point-to-multipoint traffic channel (MTCH) corresponding to the MBMS service is stopped.
  • MTCH point-to-multipoint traffic channel
  • the process of establishing the triggered unicast bearer includes: the access layer of the user equipment of the user equipment sends an indication that the MBMS service cannot continue to be received, and the high layer of the user equipment sends an indication that the MBMS service cannot continue to be received,
  • the application server sends a trigger request for establishing a thin bearer to the user equipment, and the user equipment of the user triggers the establishment of the unicast bearer according to the trigger request.
  • the eNB receives the MBMS service stop scheduling notification sent by the MCE, and the eNB sends the MBMS service stop scheduling information to the user equipment, and continues to schedule the MBMS service.
  • the MCE determines to stop the scheduling of an MBMS service, and the user equipment that needs to continue to receive the MBMS service can continue to receive the service in the process of establishing the unicast bearer, thereby effectively reducing the scheduling of the service, and the user equipment needs to continue receiving.
  • This service establishes a service interruption time in the process of unicast bearer, giving the user a better experience.
  • FIG. 2 is a flowchart of a method for maintaining service continuity according to an embodiment of the present invention. This embodiment is described in terms of user equipment.
  • the method for maintaining service continuity in this embodiment includes :
  • the user equipment receives the MBMS service stop scheduling information from the base station, and determines that the base station is about to stop scheduling the MBMS service.
  • the MCE determines to stop the scheduling of a certain MBMS service, it sends a stop scheduling notification to the eNB, and the eNB notifies the user equipment to stop scheduling the MBMS service related information, and informs the user equipment that the MBMS service will be stopped. .
  • the user equipment After receiving the information that the MBMS service of the eNB stops scheduling, the user equipment determines that the MBMS service is about to stop scheduling.
  • the user equipment can determine that the MBMS service is about to stop scheduling according to the configuration information that does not carry an MBMS service in the message by receiving the point-to-multipoint control channel message. Or the point-to-multipoint control channel message still carries the configuration information of a certain MBMS service, but judges according to the upcoming stop indication carried in the MBMS service stop scheduling information.
  • the MBMS service is about to stop scheduling.
  • S202 The user equipment continues to monitor scheduling information of the MBMS service.
  • the scheduling information of the MBMS service may be MBMS transmission channel scheduling information (MSI), and the MBMS service indicated by the user equipment MSI.
  • MSI MBMS transmission channel scheduling information
  • the sending location continues to receive the MBMS service.
  • the MBMS service stop scheduling information carries the MBMS service to stop scheduling indication, and is used to indicate that the MBMS service of the user equipment is about to stop scheduling, and the user equipment continues to monitor the MBMS service according to the MBMS service is about to stop the scheduling indication. The scheduling information until the MBMS service stop notification is received.
  • the user equipment receives the MBMS service delay stop indication from the eNB at the same time or after receiving the MBMS service stop scheduling information, and continues to monitor the scheduling information of the MBMS service according to the MBMS service delay stop indication.
  • the user equipment may receive the MBMS service delay stop indication or the MBMS service to stop scheduling indication by using any one of a point-to-multipoint control channel, a paging control channel, and MBMS transmission channel scheduling information.
  • the MBMS service delay stop indication is received through the point-to-multipoint control channel channel or the MBMS service is about to stop the scheduling indication, it may be received by a counting request message carried on the point-to-multipoint control channel channel, for example, by Carrying an MBMS service delay stop indication in the counting request or the MBMS service is about to stop the scheduling indication;
  • the MBMS service delay stop indication is received through the MBMS transmission channel scheduling information
  • the MBMS service channel stop position indication in the MBMS transmission channel scheduling information message may be A special value of the (MTCH stop ) field is used to receive an MBMS service delay stop indication or the MBMS service is about to stop scheduling instructions.
  • S203 Receive the MBMS service according to the scheduling information of the MBMS service.
  • the user equipment receives the MBMS service according to the scheduling information of the MBMS service.
  • the scheduling information of the MBMS service is MBMS transmission channel scheduling information (MSI), and the scheduling information of the MBMS service includes receiving the MBMS service according to the scheduling position of the MBMS service indicated in the MSI.
  • MSI MBMS transmission channel scheduling information
  • the establishment of the unicast bearer is triggered.
  • the user equipment continues to monitor the scheduling information of the MBMS service.
  • the point-to-multipoint traffic channel corresponding to the MBMS service is stopped, and the MBMS service is continuously received through the unicast bearer.
  • the process of establishing the triggered unicast bearer includes: the access layer of the user equipment of the user equipment sends an indication that the MBMS service cannot continue to be received, and the high layer of the user equipment sends an indication that the MBMS service cannot continue to be received,
  • the application server sends a trigger request for establishing a thin bearer to the user equipment, and the user equipment of the user triggers the establishment of the unicast bearer according to the trigger request.
  • FIG. 3 is a flowchart of a third method for maintaining service continuity according to an embodiment of the present invention. This embodiment is described from the perspective of an MCE.
  • the method for maintaining service continuity in this embodiment includes:
  • S301 The multi-cell/multicast cooperative entity determines an MBMS service that needs to be closed
  • the MCE first triggers the eNB to count the user equipment that receives the MBMS service.
  • the eNB counts the number of user equipments that determine the MBMS service.
  • the MCE determines to stop the MBSFN transmission of the MBMS service. the way.
  • the MCE receives the notification that the MBMS service is stopped by the group communication server, and determines to stop the MBSFN transmission mode of the MBMS service according to the notification that the MBMS service is stopped.
  • S302 Send an MBMS service stop scheduling notification to the base station, where the MBMS service stop scheduling notification informs the base station that the MBMS service meets the predetermined condition, stops scheduling, and instructs the base station to continue to schedule the MBMS service;
  • the MCE sends an MBMS service stop scheduling notification to the eNB, and the MBMS service stop scheduling notification informs the base station that the MBMS service stops the scheduling when the predetermined condition is met, and instructs the eNB to continue to schedule the MBMS service.
  • This predetermined condition may be a predetermined time or a predetermined time point, and may of course be other conditions.
  • the MCE can update the configuration information of the eNB by using the MBMS scheduling information, and the updated configuration information no longer carries the configuration information of the MBMS service to be closed, as the MBMS service stop scheduling notification sent to the eNB.
  • the MCE informs the eNB to stop scheduling the MBMS service that receives the user equipment less than the predetermined threshold, such as stopping the scheduling of the service 1.
  • the MBMS service stop scheduling notification may further carry a delay stop indication to indicate the eNB extension
  • the MBMS service is scheduled to be stopped late.
  • the MBMS service stop scheduling notification may further include delay stop time length information or stop time stamp information, and is used to specify that the eNB stops scheduling the MBMS service after delaying the specified time.
  • the MCE decides to stop scheduling the service 1, it sends a service to the eNB. 1 Stops the scheduling notification, and the notification can be used to indicate that the service 1 is about to stop scheduling. Further, the notification may further carry a delay stop indication to indicate that the eNB delays scheduling the service 1 , and the eNB stops scheduling the service after stopping the scheduling of the service according to the MBMS service stop scheduling indication. And may further specify a delay stop time, to indicate a stop scheduling time relative to the relative time of receiving the first notification of stopping the scheduling, such as 10 minutes, 5 minutes, two modification periods or other time information, or may be Specify timestamp information, such as specific timestamp information such as 12:30 and 12:40.
  • the MCE may also send a delay stop indication at the same time as or after sending the MBMS service stop scheduling notification to instruct the eNB to delay scheduling the MBMS service.
  • the MCE first sends a service 1 to the eNB to stop scheduling the first notification, the first notification indicates that the service 1 is about to stop scheduling, and then sends a service 1 to stop scheduling the second notification, the second notification directly indicating the eNB immediately Stop scheduling business 1.
  • the optional MBMS service stop scheduling first notification is carried by the MBMS scheduling information message, and when the MBMS scheduling information does not carry the MBMS service, it indicates that the scheduling of the MBMS service is to be stopped.
  • FIG. 4 is a flowchart of a method for maintaining service continuity according to an embodiment of the present invention. This embodiment is described in terms of a group communication server, and the method for maintaining service continuity in this embodiment. Includes:
  • the group communication server receives the information that is received by the user equipment and receives the group service through the MBSFN.
  • the data in the MBSFN area group service is carried on the MBMS service, and the group communication server is used to manage the user equipment in the group.
  • the user equipment Before receiving the group service data, the user equipment needs to register with the group communication server.
  • the group communication server can report the information that the group service is receiving the group service through the MBSFN mode.
  • the information of the group service includes the MBSFN area identifier of the group service and the cell identifier of the group service. At least one Kind.
  • the group communication server receives, from the multi-cell/multicast cooperation entity, the MBSFN transmission stop notification for receiving the group service.
  • the MCE decides to stop the scheduling of a certain MBMS service, and then the MCE informs the eNB to notify the group communication server before stopping the scheduling of the MBMS service.
  • the MCE can send business information that it is about to stop to the group communication server, such as the MBSFN area identifier, the MBMS server identifier, and the like.
  • the group communication server receives a MBSFN transmission from the MCE to stop notification.
  • the group communication server notifies the user equipment to establish a unicast bearer, so that the user equipment continues to receive the group service by using the unicast bearer after the MBSFN for receiving the group service stops.
  • the group communication server After receiving the MBSFN transmission stop notification, the group communication server notifies the user equipment to establish a unicast bearer, so that after the MBSFN for receiving the group service stops, the MBSFN continues to receive the group service by the unicast bearer.
  • the unicast bearer may be established only by the user equipment that needs to continue to receive the service of the group.
  • the user equipment that needs to continue to receive the service of the group triggers the establishment of a unicast bearer to continue receiving the group of services on the unicast bearer after the MBSFN transmission is stopped.
  • the group communication server After the user equipment establishes a unicast bearer, the group communication server notifies the MCE to stop the MBSFN transmission.
  • the access layer of the user equipment determines that an MBMS service is about to stop, and sends an indication to the upper layer of the user equipment, where the user equipment high layer reports the MBMS service to the group communication server.
  • the corresponding group service cannot continue to receive the MBSFN mode.
  • the group communication server triggers the user equipment to establish a unicast bearer to continue receiving the group. business.
  • the unicast bearer is a dedicated radio bearer for transmitting MBMS services between the user equipment and the base station.
  • the user equipment is required to establish a connection with the eNB before the group service server reports that the group service corresponding to the MBMS service cannot continue to be received in the MBSFN mode.
  • the user equipment receives the network congestion.
  • the eNB's MBMS service stops scheduling information, it can perform a random backoff to prevent multiple user equipments from simultaneously triggering the unicast connection establishment process.
  • the user equipment generates a random factor, and a The predetermined threshold is compared, and the delay of triggering the unicast process is determined according to the comparison result. For example, if the predetermined random factor is 0.5 and the user-generated random number is 0.6, 0.6>0.5, the user delays 10 ms to trigger the connection establishment.
  • the group communication server of the user equipment in the management group is notified before notifying the eNB.
  • the group communication server notifies the user equipment to establish a unicast bearer, and then notifies the MCE to stop the MBSFN transmission after the user equipment establishes the unicast bearer.
  • the user equipment that needs to continue to receive the group service transmitted through the MBSFN first establishes a unicast bearer according to the notification of the group communication server, thereby avoiding interruption of the group service and giving the user a better Use experience.
  • FIG. 5 is a flowchart of a method for maintaining service continuity according to an embodiment of the present invention. This embodiment is described by using an MCE.
  • the method for maintaining service continuity in this embodiment includes:
  • S501 The multi-cell/multicast cooperative entity determines the MBSFN transmission that needs to be stopped;
  • the MCE first triggers the eNB to collect the user equipment of the MBMS service, and determines the number of the user equipment of the MBMS service according to the eNB statistical response. When the user equipment that receives the MBMS service is less than the predetermined threshold, determine that the MBSFN needs to stop the MBMS service. transfer method.
  • S502 notify the group communication server that the MBSFN transmission is stopped
  • the MCE When the MCE decides to stop the MBSFN transmission of a certain MBMS service, the MCE notifies the eNB to notify the group communication server before stopping the scheduling of the MBMS service.
  • the MCE can report the business information that it is about to stop to the group communication server, such as the MBSFN area identifier and the MBMS server identifier.
  • the group communication server is notified to the user equipment to establish a unicast bearer, so that after the user equipment stops MBSFN transmission, the unicast bearer replaces the MBSFN to continue receiving the group service.
  • the notification group communication server After the MBSFN transmission is about to stop, the notification group communication server sends MBMS service stop scheduling information to the eNB after a predetermined period of time, so that the eNB stops scheduling the MBMS service.
  • the group communication server is configured to manage the user equipment in the group. After receiving the MBSFN transmission stop notification, the user equipment can be notified to establish a unicast bearer, so that after the MBSFN transmission of the receiving group service is stopped, the unicast bearer can continue to be transmitted. Receive group business.
  • FIG. 6 is a flowchart of a sixth method for maintaining service continuity according to an embodiment of the present invention. This embodiment is described in terms of user equipment.
  • the method for maintaining service continuity in this embodiment includes :
  • the user equipment reports the information of the group service through the MBSFN to the group communication server.
  • the data of the MBSFN area group service is carried on the MBMS service
  • the group communication server is used to manage the user equipment in the group
  • the user equipment is in the receiving group. Before the business data, you need to register with the group communication server.
  • the user equipment can receive the information of the group service through the MBSFN mode on the group communication server.
  • the information of the group service includes the MBSFN area indication of the group service and the cell identifier in the group service. At least one.
  • S602 Establish a unicast bearer according to the unicast bearer setup notification of the group communication server, and continue to monitor the scheduling information that carries the service of the group;
  • the MCE decides to stop the scheduling of a certain MBMS service, and then the MCE informs the eNB to notify the group communication server before stopping the scheduling of the MBMS service.
  • the MCE can send business information that it is about to stop to the group communication server, such as the MBSFN area identifier, the MBMS server identifier, and the like.
  • the group communication server receives a MBSFN transmission from the MCE to stop notification.
  • the group communication server After receiving the MBSFN transmission stop notification, the group communication server notifies the user equipment to establish a unicast bearer, so as to continue receiving the group service through the unicast bearer.
  • the group communication server notifies the user equipment to establish a unicast bearer, so as to continue receiving the group service through the unicast bearer.
  • the group communication server notifies the user equipment to establish a unicast bearer, so as to continue receiving the group service through the unicast bearer.
  • the group communication server After receiving the MBSFN transmission stop notification, the group communication server notifies the user equipment to establish a unicast bearer, so as to continue receiving the group service through the unicast bearer.
  • the user equipment that needs to continue to receive the service of the group triggers the establishment of a unicast bearer to continue receiving the group of services on the unicast bearer after the MBSFN transmission is stopped.
  • the group communication server After the user equipment establishes a unicast bearer, the group communication server notifies the MCE to stop the MBSFN transmission.
  • the user equipment During the establishment of the unicast bearer, the user equipment continues to listen to the scheduling information of the group of services. After the unicast bearer is established, the user equipment stops listening to the scheduling information of the bearer group service, and continues to receive the group service through the unicast bearer.
  • FIG. 7 is a schematic structural diagram of a first type of base station according to an embodiment of the present invention.
  • the base station 100 in this embodiment includes a receiving module 11 and a scheduling module 12, where:
  • the receiving module 11 is configured to receive a first notification that the MBMS service stops scheduling sent by the MCE;
  • the MCE first triggers the eNB to count the user equipment that receives the MBMS service.
  • the eNB counts the number of user equipments that determine the MBMS service.
  • the MCE determines to stop the scheduling of the MBMS service.
  • the MCE informs the eNB to stop scheduling the MBMS service that receives the user equipment less than the predetermined threshold, such as stopping the scheduling of the service 1.
  • the eNB receives the first notification that the MBMS service sent by the MCE stops scheduling through the receiving module 11.
  • the MBMS service stop scheduling first notification is a notification sent by the MCE to the base station when the MBMS service is closed, and the MBMS service stop scheduling first notification may be used to stop the scheduling when an MBMS service meets a predetermined condition.
  • This predetermined condition may be after a certain time, or a fixed time point, and the like. Of course, it can be other specified conditions.
  • the MBMS service stop scheduling first notification may further carry a delay stop indication to indicate that the eNB delays scheduling the MBMS service.
  • the MBMS service stop scheduling first notification may further include delaying stop time length information or stopping timestamp information, for specifying that the eNB stops scheduling the MBMS service after delaying the specified time.
  • the MCE decides to stop the scheduling of the service 1, and then sends a service 1 to the eNB to stop scheduling the first notification, where the notification may be used to indicate that the service 1 is about to stop scheduling or the first notification may carry a delay stop indication, to instruct the eNB to delay the scheduling service. 1 .
  • the eNB stops scheduling the service after stopping the scheduling of the service for a period of time according to the MBMS service delay stop indication. And may further specify a delay stop time, to indicate a stop scheduling time relative to the relative time of receiving the first notification of stopping the scheduling, such as 10 minutes, 5 minutes, two modification periods or other time information, or may be Specify timestamp information, such as specific timestamp information such as 12:30, 12:40.
  • the optional MBMS service stop scheduling first notification is carried by the MBMS scheduling information message.
  • the MBMS scheduling information does not carry the configuration information of the MBMS service, it indicates that the scheduling of the MBMS service is to be stopped.
  • the scheduling module 12 is configured to send the MBMS service stop scheduling information to the user equipment after receiving the first notification that the MBMS service stops scheduling, and continue to schedule the MBMS service until the predetermined condition is met, and then stop scheduling the MBMS service.
  • the eNB After receiving the first notification that the MBMS service of the MCE stops scheduling, the eNB sends the MBMS service stop scheduling information to the user equipment by using the scheduling module 12.
  • the scheduling module 12 may use the configuration information that does not carry a certain MBMS service in the point-to-multipoint control channel message as a certain MBMS service stop scheduling information sent to the user equipment.
  • the MBMS service stop scheduling information may carry a delay stop indication to notify the user equipment that the MBMS service is scheduled to be stopped.
  • the scheduling module 12 notifies the user equipment that the scheduling information is stopped or after, and also sends a delay stop indication to notify the user equipment that the MBMS is delayed to be scheduled.
  • the MBMS service stop scheduling information may carry the MBMS service, that is, the scheduling indication is stopped, to notify the user equipment that the MBMS service is about to be stopped.
  • the MBMS service delay stop indication or the MBMS service upcoming stop scheduling indication may be sent to the user equipment by using any one of a point-to-multipoint control channel, a paging control channel, and MBMS transmission channel scheduling information. Specifically, if the MBMS service delay stop indication is sent through the point-to-multipoint control channel channel, it may be sent by a counting request message carried on the point-to-multipoint control channel channel, for example, by adding an MBMS service delay in the counting request. If the MBMS service delay stop indication is sent by the MBMS transport channel scheduling information, the MBMS service delay stop indication may be indicated by a special value of the MBMS Traffic Channel Stop Location Indication (MTCH stop) field in the MBMS Transport Channel Scheduling Information message.
  • MTCH stop Traffic Channel Stop Location Indication
  • the eNB continues to schedule the MBMS service through the scheduling module 12, so that the user equipment that needs to continue to receive the MBMS service triggers the establishment of a unicast bearer, and the MBMS service does not interrupt or the interruption time is reduced during the unicast bearer process.
  • the scheduling module 12 stops scheduling the MBMS service when the one of the foregoing conditions is met: the receiving module 11 receives the second notification of the MBMS service stop scheduling that occurs in the MCE, and the MBMS service stops scheduling the second notification to indicate that the MBMS service stops scheduling; or After receiving the first notification that the MBMS service stops scheduling, the receiving module 11 reaches the time point of the MBMS service stop scheduling first notification indication; or the receiving module 11 passes the first predetermined time after receiving the MBMS service stop scheduling first notification; Or after receiving the first notification that the service stops scheduling, the second predetermined time point is reached.
  • the MCE may send a first notification that the MBMS service stops scheduling, notifying that a certain service is about to stop scheduling, and then, after a predetermined time, the MCE sends the MBMS service to stop.
  • a second notification is scheduled, the notification directly instructing the eNB to stop scheduling the MBMS service.
  • the MCE may also directly carry the delay stop indication in the first notification of the MBMS service stop scheduling, and stop the scheduling time point as a predefined time point, for example, after receiving the first notification of stopping the scheduling of the MBMS service, starting from the next modification period.
  • the start time is stopped, or the delay may be further indicated in the first notification to indicate a specific delay time.
  • the eNB receives the first notification that the MBMS service of the MCE stops scheduling, and stops scheduling the service after a delay. Or stop scheduling the MBMS service at a point in time when the first notification indication is reached.
  • the first notification of the MBMS service that the MCE can send stops scheduling, only to notify a certain MBMS service to stop scheduling (that is, the first notification is an ordinary MBMS service stop scheduling notification), and after receiving the notification, the eNB continues to schedule itself.
  • the MBMS first predetermined time the first predetermined time may be a preset time of the system.
  • the user equipment After receiving the scheduling information of the MBMS service of the eNB, the user equipment determines that an MBMS service is about to stop, but continues to monitor the MSI for a period of time. If the user equipment needs to continue to receive the MBMS service, the establishment of the unicast bearer may be triggered, and after the unicast bearer is established, the point-to-multipoint traffic channel (MTCH) corresponding to the MBMS service is stopped.
  • MTCH point-to-multipoint traffic channel
  • the base station provided in this embodiment can implement the steps in the embodiment shown in FIG. 1.
  • the division of each functional module of the base station in this embodiment is only schematic. Under the premise that the purpose of the present invention can be achieved, the function module of the base station
  • the division is not limited to the above, and may be any other possible way of implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not implemented.
  • FIG. 8 is a schematic structural diagram of a first type of user equipment according to an embodiment of the present invention.
  • the user equipment 110 of this embodiment includes a first receiving module 21, a listening module 22, and a second receiving module 23, where:
  • the first receiving module 21 is configured to receive MBMS service stop scheduling information from the base station, and determine that the base station is about to stop scheduling the MBMS service;
  • the eNB When the MCE determines that the scheduling of a certain MBMS service is to be stopped, the eNB sends a stop scheduling notification to the eNB, and the eNB notifies the user equipment to stop scheduling the MBMS service related information, and informs the user equipment that the MBMS service is about to stop being scheduled. That is, the base station stops scheduling the MBMS service when the predetermined condition is met.
  • This predetermined condition may be a predetermined time or a predetermined time point or a stop scheduling notification, etc., and of course other conditions.
  • the user equipment After receiving the information about the stop scheduling of the MBMS service of the eNB by the first receiving module 21, the user equipment determines that the MBMS service is about to stop scheduling.
  • the first receiving module 21 may determine that the MBMS service is about to stop scheduling according to the configuration information that does not carry a certain MBMS service in the message by receiving the point-to-multipoint control channel message. Or the point-to-multipoint control channel message still carries the configuration information of a certain MBMS service, but determines that the MBMS service is about to stop scheduling according to the imminent stop indication carried in the MBMS service stop scheduling information.
  • the monitoring module 22 is configured to continue to monitor the scheduling information of the MBMS service after the first receiving module 21 determines that the MBMS service stops scheduling after satisfying the predetermined condition;
  • the scheduling information of the MBMS service may be MBMS transport channel scheduling information (MSI), and the user equipment MSI.
  • MSI MBMS transport channel scheduling information
  • the indicated transmission location of the MBMS service continues to receive the MBMS service.
  • the MBMS service stop scheduling information carries a delay stop indication, which is used to indicate that the MBMS service delays the scheduling of the user equipment, and the monitoring module 22 continues to monitor the scheduling information of the MBMS service according to the delay stop indication.
  • the MBMS service stop scheduling information carries an MBMS service to stop scheduling indication, and is used to indicate that the MBMS is about to stop scheduling
  • the listening module is configured to determine, according to the MBMS service, that the base station is about to stop scheduling, determining that the base station is about to stop Stop scheduling the MBMS service.
  • the first receiving module 21 receives the MBMS service delay stop indication from the eNB, and the listening module 22 continues to monitor the scheduling information of the MBMS service according to the MBMS service delay stop indication.
  • the first receiving module 21 may receive the MBMS service delay stop indication or the MBMS service upcoming stop scheduling indication by using any one of a point-to-multipoint control channel, a paging control channel, and MBMS transmission channel scheduling information. Specifically, if the MBMS service delay stop indication is received through the point-to-multipoint control channel channel, it may be received by a counting request message carried on the point-to-multipoint control channel channel, for example, by carrying the MBMS service delay in the counting request. If the MBMS service delay stop indication is received through the MBMS transport channel scheduling information, the MBMS service delay stop indication may be received through a special value of the MBMS Traffic Channel Stop Location Indication (MTCH stop) field in the MBMS Transport Channel Scheduling Information message.
  • the second receiving module 23 is configured to receive the MBMS service according to the scheduling information of the MBMS service monitored by the monitoring module 22.
  • the second receiving module 23 receives the MBMS service according to the scheduling information of the MBMS service monitored by the monitoring module 22.
  • the scheduling information of the MBMS service is MBMS transmission channel scheduling information (MSI), and the scheduling information according to the MBMS service includes receiving the MBMS service according to the scheduling location of the MBMS service indicated in the MSI.
  • MSI MBMS transmission channel scheduling information
  • the establishment of the unicast bearer is triggered.
  • the intercepting module 22 continues to monitor the scheduling information of the MBMS service.
  • the second receiving module 23 stops receiving the point-to-multipoint traffic channel corresponding to the MBMS service, and continues to receive the MBMS service through the unicast bearer.
  • the second receiving module 23 stops receiving the MBMS service.
  • the user equipment further includes a unicast establishing module, where the unicast establishing module is configured to trigger the establishment of the unicast bearer after the user equipment determines that the base station is about to stop scheduling the MBMS service;
  • the second receiving module stops the point-to-multipoint traffic channel corresponding to the MBMS service to receive the MBMS service.
  • the user equipment in this embodiment can implement the steps of the embodiment shown in FIG. 2.
  • the division of each functional module of the user equipment in this embodiment is only schematic, and the user equipment can be implemented on the premise that the purpose of the present invention can be achieved.
  • the division of the functional modules is not limited to the above, and may be any other possible way of implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not implemented.
  • FIG. 9 is a schematic structural diagram of a first multi-cell/multicast cooperative entity according to an embodiment of the present invention.
  • the multi-cell/multicast cooperative entity 120 of this embodiment includes a determining module 31 and a scheduling module 32, where :
  • the determining module 31 is configured to determine an MBMS service that needs to be closed;
  • the MCE first triggers the eNB to count the user equipment that receives the MBMS service, and the eNB counts the number of the user equipments that determine the MBMS service.
  • the MCE determines, by the determining module 31, that the MBMS is stopped. MBSFN transmission mode of service.
  • the scheduling module 32 is configured to: when the determining module 31 determines that the MBMS service needs to be shut down, send the MBMS service stop scheduling notification to the base station, where the MBMS service stop scheduling notification informs the base station that the MBMS service meets a predetermined condition, stops scheduling, and instructs the base station to continue scheduling MBMS business.
  • the MCE After the determining module 31 determines that the MBMS service needs to be shut down, the MCE sends an MBMS service stop scheduling notification to the eNB through the scheduling module 32, and the MBMS service stop scheduling notification informs the base station that the MBMS service stops the scheduling when the predetermined condition is met, and instructs the eNB to continue to schedule the MBMS service stop scheduling notification.
  • MBMS business After the determining module 31 determines that the MBMS service needs to be shut down, the MCE sends an MBMS service stop scheduling notification to the eNB through the scheduling module 32, and the MBMS service stop scheduling notification informs the base station that the MBMS service stops the scheduling when the predetermined condition is met, and instructs the eNB to continue to schedule the MBMS service stop scheduling notification.
  • MBMS business After the determining module 31 determines that the MBMS service needs to be shut down, the MCE sends an MBMS service stop scheduling notification to the eNB through the scheduling module 32, and the MBMS
  • the scheduling module 32 may update the configuration information of the eNB by using the MBMS scheduling information, and the updated configuration information no longer carries the configuration information of the MBMS service to be closed, as the MBMS service stop scheduling notification sent to the eNB.
  • the scheduling module 32 notifies the eNB to stop scheduling the MBMS service that receives the user equipment less than the predetermined threshold, such as stopping the scheduling of the service 1.
  • the MBMS service stop scheduling notification may also carry a delay stop indication to instruct the eNB to delay scheduling the MBMS service. Further, the MBMS service stop scheduling notification may further include delay stop time length information or stop time stamp information, and is used to specify that the eNB stops scheduling the MBMS service after delaying the specified time.
  • the scheduling module 32 sends a service 1 stop scheduling notification to the eNB, and the notification can be used to indicate that the service 1 is about to stop scheduling.
  • the notification may further carry a delay stop indication to indicate that the eNB delays scheduling the service 1 , and the eNB stops scheduling the service after stopping the scheduling of the service for a period of time according to the MBMS service delay stop indication.
  • a delay stop time to indicate a stop scheduling time relative to the relative time of receiving the first notification of stopping the scheduling, such as 10 minutes, 5 minutes, two modification periods or other time information, or may be Specify timestamp information, such as specific timestamp information such as 12:30, 12:40.
  • the scheduling module 32 may also send a delay stop indication at the same time as or after transmitting the MBMS service stop scheduling notification to instruct the eNB to delay scheduling the MBMS service.
  • the MCE sends a service 1 to the eNB to stop scheduling the first notification by the scheduling module 32.
  • the first notification indicates that the service 1 is about to stop scheduling, and then sends a service 1 to stop scheduling the second notification, the second notification. Directly instructing the eNB to immediately stop scheduling service 1.
  • the optional MBMS service stop scheduling first notification is carried by the MBMS scheduling information message, and when the MBMS scheduling information does not carry the MBMS service, it indicates that the scheduling of the MBMS service is to be stopped.
  • the multi-cell/multicast cooperative entity in this embodiment can implement the steps of the embodiment shown in FIG. 3.
  • the division of each functional module of the multi-cell/multicast collaboration entity is only schematic,
  • the division of the multi-cell/multicast cooperative entity function module is not limited to the above manner, and may be any other possible implementation manner. For example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not implemented.
  • FIG. 10 is a schematic structural diagram of a second base station according to an embodiment of the present invention.
  • the base station 130 of this embodiment includes a processor 41, a memory 42, a receiver 43, a transmitter 44, and a bus system 45, where:
  • the processor 41 controls the operation of the base station 130, which may also be referred to as a CPU (Central Processing Unit).
  • Processor 41 may be an integrated circuit chip with signal processing capabilities.
  • the processor 41 can also be a general-purpose processor, a digital signal processing (DSP), an application specific integrated circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other Programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • the general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the memory 42 can include read only memory and random access memory and provides instructions and data to the processor 41.
  • a portion of memory 42 may also include non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • the various components of the base station 130 are coupled together by a bus system 45, which may include, in addition to the data bus, a power bus, a control bus, a status signal bus, and the like.
  • the bus system may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus.
  • the bus may be one or more physical lines, and when it is a plurality of physical lines, it may be divided into an address bus, a data bus, a control bus, and the like.
  • the processor 41, The memory 42 and the receiver 43 and the transmitter 44 can also be directly connected via a communication line.
  • various buses are labeled as bus system 45 in the figure.
  • Memory 42 stores the following elements, executable modules or data structures, or subsets thereof, or their extended sets:
  • Operation instructions Includes various operation instructions for implementing various operations.
  • Operating System Includes a variety of system programs for implementing a variety of basic services and handling hardware-based tasks.
  • the processor 41 performs the following operations by calling an operation instruction stored in the memory 42 (the operation instruction can be stored in the operating system):
  • the processor 41 is configured to control the receiver 43 to receive the MBMS service stop scheduling first notification sent by the MCE, and after receiving the MBMS service stop scheduling first notification, the MBMS service stops scheduling, the first notification is when the MCE determines to close the MBMS service to the base station.
  • the notification sent, the control transmitter 44 sends the MBMS service stop scheduling information to the user equipment, and the processor 41 continues to schedule the MBMS service until the predetermined condition is met and then stops scheduling the MBMS service.
  • the memory 42 is used to store the MBMS data.
  • the MCE first triggers the eNB to count the user equipment that receives the MBMS service.
  • the eNB counts the number of user equipments that determine the MBMS service.
  • the MCE determines to stop the scheduling of the MBMS service.
  • the MCE informs the eNB to stop scheduling the MBMS service that receives the user equipment less than the predetermined threshold, such as stopping the scheduling of the service 1.
  • the processor 41 controls the receiver 43 to receive the first notification that the MBMS service sent by the MCE stops scheduling.
  • the MBMS service stop scheduling first notification may be used to indicate that an MBMS service stops scheduling when it satisfies a predetermined condition.
  • This predetermined condition may be after a certain time, or a fixed time point, and the like. Of course, it can be other specified conditions.
  • the MBMS service stop scheduling first notification may further carry a delay stop indication to indicate that the eNB delays scheduling the MBMS service.
  • the MBMS service stop scheduling first notification may further include delaying stop time length information or stopping timestamp information, for specifying that the eNB stops scheduling the MBMS service after delaying the specified time.
  • the MCE decides to stop scheduling the service 1
  • the service 1 is sent to the eNB to stop scheduling the first notification
  • the notification may be used to indicate that the service 1 is about to stop scheduling
  • the first notification may be Carrying a delay stop indication to instruct the eNB to delay the scheduling of the service 1
  • the eNB stops scheduling the service after stopping the scheduling of the service for a period of time according to the MBMS service delay stop indication.
  • a delay stop time to indicate a stop scheduling time relative to the relative time of receiving the first notification of stopping the scheduling, such as 10 minutes, 5 minutes, two modification periods or other time information, or may be Specify timestamp information, such as specific timestamp information such as 12:30, 12:40.
  • the optional MBMS service stop scheduling first notification is carried by the MBMS scheduling information message.
  • the MBMS scheduling information does not carry the configuration information of the MBMS service, it indicates that the scheduling of the MBMS service is to be stopped.
  • the processor 41 controls the receiver 43 to receive the first notification of the MBMS service stop scheduling of the MCE, and further controls the transmitter 44 to send a certain MBMS service stop scheduling information to the user equipment.
  • the processor 41 can control the transmitter 44 to use the configuration information of the MBMS service in the point-to-multipoint control channel message as a certain MBMS service stop scheduling information sent to the user equipment.
  • the MBMS service stop scheduling information may carry a delay stop indication to notify the user equipment that the MBMS service is scheduled to be stopped.
  • the processor 41 controls the transmitter 44 to notify the user equipment that the scheduling information is stopped or after, and also sends a delay stop indication to notify the user that the device may delay scheduling the MBMSo.
  • the MBMS service delay stop indication may be sent to the user equipment by using any one of a point-to-multipoint control channel, a paging control channel, and MBMS transmission channel scheduling information. Specifically, if the MBMS service delay stop indication is sent through the point-to-multipoint control channel channel, it may be sent by a counting request message carried on the point-to-multipoint control channel channel, for example, by adding an MBMS service delay in the counting request. If the MBMS service delay stop indication is sent by the MBMS transport channel scheduling information, the MBMS service delay stop indication may be indicated by a special value of the MBMS Traffic Channel Stop Location Indication (MTCH stop) field in the MBMS Transport Channel Scheduling Information message.
  • MTCH stop Traffic Channel Stop Location Indication
  • the processor 41 continues to schedule the MBMS service, so that the user equipment that needs to continue to receive the MBMS service triggers the establishment of a unicast bearer, and the MBMS service does not The interruption or interruption time is reduced.
  • the processor 41 stops scheduling the MBMS service when one of the following conditions is met: when the receiver 43 receives the second notification of the MBMS service stop scheduling that occurs in the MCE, the MBMS service stops scheduling the second notification to indicate that the MBMS service stops scheduling; Or the time point after the receiver 43 receives the first notification that the MBMS service stops scheduling, and reaches the first notification indication that the MBMS service stops scheduling; or the receiver 41 passes the first predetermined time after receiving the first notification that the MBMS service stops scheduling. After reaching the first notification that the service stops scheduling, the second predetermined time point is reached.
  • the user equipment After receiving the scheduling information of the MBMS service of the eNB, the user equipment determines that an MBMS service is about to stop, but continues to monitor the MSI for a period of time. If the user equipment needs to continue to receive the MBMS service, the establishment of the unicast bearer may be triggered. After the unicast bearer is established, the point-to-multipoint traffic channel corresponding to the MBMS service is stopped.
  • each step of the above method may be completed by an integrated logic circuit of hardware in the processor 41 or an instruction in the form of software.
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware decoding processor, or may be performed by a combination of hardware and software modules in a decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 42, and the processor 41 reads the information in the memory 42 and combines the hardware to perform the steps of the above method.
  • FIG. 11 is a schematic structural diagram of a second user equipment according to an embodiment of the present invention.
  • the user equipment 140 of this embodiment includes a processor 51, a memory 52, a receiver 53, and a bus system 54, wherein:
  • the processor 51 controls the operation of the user equipment 140, which may also be referred to as a CPU (Central Processing Unit).
  • Processor 51 may be an integrated circuit chip with signal processing capabilities.
  • the processor 51 can also be a general-purpose processor, a digital signal processing (DSP), an application specific integrated circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other Programmable logic device, discrete gate or transistor logic, discrete hardware Component.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • Memory 52 can include read only memory and random access memory and provides instructions and data to processor 51. A portion of memory 52 may also include non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • the various components of the user equipment 140 are coupled together by a bus system 55, which may include, in addition to the data bus, a power bus, a control bus, a status signal bus, and the like.
  • the bus system may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus.
  • the bus may be one or more physical lines, and when it is a plurality of physical lines, it may be divided into an address bus, a data bus, a control bus, and the like.
  • processor 51, memory 52, and receiver 53 may also be directly connected by a communication line.
  • various buses are labeled as bus system 54 in the figure.
  • Memory 52 stores the following elements, executable modules or data structures, or subsets thereof, or their extended sets:
  • Operation instructions Includes various operation instructions for implementing various operations.
  • Operating System Includes a variety of system programs for implementing a variety of basic services and handling hardware-based tasks.
  • the processor 51 performs the following operations by calling an operation instruction stored in the memory 52 (the operation instruction can be stored in the operating system):
  • the processor 51 is configured to control the receiver 53 to receive the MBMS service stop scheduling information from the base station, determine that the base station stops scheduling the MBMS service when the predetermined condition is met, and continues to monitor the scheduling information of the MBMS service, and controls the receiver 53 according to the processor 51.
  • the scheduled scheduling information of the MBMS service is received, and the MBMS service is received.
  • the memory 52 is used to store the MBMS service data.
  • the eNB When the MCE determines that the scheduling of a certain MBMS service is to be stopped, the eNB sends a stop scheduling notification to the eNB, and the eNB notifies the user equipment to stop scheduling the MBMS service related information, and informs the user equipment that the MBMS service is stopped when the predetermined condition is met again.
  • This predetermined condition may be a predetermined time or a predetermined time point or the like, and of course other conditions may be employed.
  • the processor 51 controls the receiver 53 to receive the information about the MBMS service stop scheduling of the eNB, and determines that the MBMS service is about to stop scheduling.
  • the receiver 53 can receive the point-to-multipoint control channel message, and the processor 51 determines that the MBMS service is about to stop scheduling according to the configuration information that does not carry a certain MBMS service in the message. Or the point-to-multipoint control channel message still carries the configuration information of a certain MBMS service, but determines that the MBMS service is about to stop scheduling according to the imminent stop indication carried in the MBMS service stop scheduling information.
  • the scheduling information of the MBMS service may be MBMS transmission channel scheduling information (MSI), and the sending location of the MBMS service indicated by the user equipment MSI continues to receive the MBMS service.
  • MSI MBMS transmission channel scheduling information
  • the MBMS service stop scheduling information carries a delay stop indication, which is used to indicate that the MBMS service delays the scheduling of the user equipment, and the processor 51 continues to monitor the scheduling information of the MBMS service according to the delay stop indication.
  • the receiver 53 receives the MBMS service delay stop indication from the eNB at the same time as or after receiving the MBMS service stop scheduling information, and the processor 51 continues to monitor the scheduling information of the MBMS service according to the MBMS service delay stop indication.
  • the receiver 53 may receive the MBMS service delay stop indication by using any one of a point-to-multipoint control channel, a paging control channel, and MBMS transmission channel scheduling information. Specifically, if the MBMS service delay stop indication is received through the point-to-multipoint control channel channel, it may be received by a counting request message carried on the point-to-multipoint control channel channel, for example, by stopping the MBMS service delay stop indication in the counting request. If the MBMS service delay stop indication is received through the MBMS transport channel scheduling information, the MBMS service delay stop indication may be received through a special value of the MBMS Traffic Channel Stop Location Indication (MTCH stop) field in the MBMS Transport Channel Scheduling Information message.
  • MTCH stop Traffic Channel Stop Location Indication
  • the processor 51 further controls the receiver 53 to receive the MBMS service according to the scheduling information of the MBMS service monitored by the processor 51.
  • the scheduling information of the MBMS service is MBMS transport channel scheduling information (MSI), and the scheduling information of the MBMS service includes receiving the MBMS service according to the scheduling location of the MBMS service indicated in the MSI.
  • MSI MBMS transport channel scheduling information
  • the processor 51 triggers the establishment of the unicast bearer. During the unicast bearer setup process, the processor 51 continues to monitor the MBMS service. Scheduling information. After the unicast bearer is established, the processor 51 controls the receiver 53 to stop receiving the point-to-multipoint traffic channel corresponding to the MBMS service, and continues to receive the MBMS service through the unicast bearer.
  • the control receiver 53 stops the reception of the MBMS service.
  • the method disclosed in the foregoing embodiments of the present invention may be applied to the processor 51 or implemented by the processor 61.
  • each step of the above method may be completed by an integrated logic circuit of hardware in the processor 51 or an instruction in the form of software.
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware decoding processor, or may be performed by a combination of hardware and software modules in a decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 52, and the processor 51 reads the information in the memory 52 and combines the hardware to perform the steps of the above method.
  • FIG. 12 is a schematic structural diagram of a second multi-cell/multicast cooperation entity according to an embodiment of the present invention.
  • the multi-cell/multicast cooperation entity 150 of this embodiment includes a processor 61, a memory 62, and a transmitter. 63 and bus system 64, wherein:
  • the processor 61 controls the operation of the multi-cell/multicast cooperative entity (MCE) 150, which may also be referred to as a CPU (Central Processing Unit).
  • MCE multi-cell/multicast cooperative entity
  • Processor 61 may be an integrated circuit chip with signal processing capabilities.
  • the processor 61 can also be a general-purpose processor, a digital signal processing (DSP), an application specific integrated circuit (ASIC), a Field-Programmable Gate Array (FPGA), or the like. Programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • Memory 62 can include read only memory and random access memory and provides instructions and data to processor 61. A portion of memory 62 may also include non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • the various components of the MCE 150 are coupled together by a bus system 64, which may include, in addition to the data bus, a power bus, a control bus, a status signal bus, and the like.
  • the bus system may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus.
  • the bus may be one or more physical lines, and when it is a plurality of physical lines, it may be divided into an address bus, a data bus, a control bus, and the like.
  • the processor 61, the memory 62, and the transmitter 63 may also be directly connected through a communication line.
  • various buses are labeled as bus system 64 in the figure.
  • Memory 62 stores the following elements, executable modules or data structures, or subsets thereof, or their extended sets:
  • Operation instructions Includes various operation instructions for implementing various operations.
  • Operating System Includes a variety of system programs for implementing a variety of basic services and handling hardware-based tasks.
  • the processor 61 performs the following operations by calling an operation instruction stored in the memory 62 (the operation instruction can be stored in the operating system):
  • the processor 61 is configured to determine the MBMS service to be shut down, and the control transmitter 63 sends an MBMS service stop scheduling notification to the base station.
  • the MBMS service stop scheduling notification informs the base station that the MBMS service stops the scheduling when the predetermined condition is met, and the processor 61 instructs the base station to continue scheduling.
  • the MBMS service is configured to determine the MBMS service to be shut down, and the control transmitter 63 sends an MBMS service stop scheduling notification to the base station.
  • the MBMS service stop scheduling notification informs the base station that the MBMS service stops the scheduling when the predetermined condition is met, and the processor 61 instructs the base station to continue scheduling.
  • the MBMS service is configured to determine the MBMS service to be shut down, and the control transmitter 63 sends an MBMS service stop scheduling notification to the base station.
  • the MBMS service stop scheduling notification informs the base station that the MBMS service stops the scheduling when the predetermined condition is met, and the processor 61 instructs
  • the memory 62 is used to store the MBMS service data.
  • the MCE first triggers the eNB to collect the user equipment of the MBMS service by using the processor 61.
  • the eNB statistically determines the number of user equipments of the MBMS service.
  • the MCE processor 61 determines. Stop the MBSFN transmission mode of the MBMS service.
  • the control transmitter 63 sends the MBMS service stop scheduling notification to the base station, and the processor 61 instructs the base station to continue scheduling the MBMS service.
  • the processor 61 can update the configuration information of the eNB by using the MBMS scheduling information, and the updated configuration information does not carry the configuration information of the MBMS service that needs to be closed, as the MBMS service stop scheduling notification sent to the eNB.
  • the processor 61 controls the transmitter 63 to inform the eNB to stop scheduling the MBMS service that receives the user equipment less than a predetermined threshold, such as stopping the scheduling of the service 1.
  • the MBMS service stop scheduling notification may further carry a delay stop indication to indicate the eNB extension
  • the MBMS service is scheduled to be stopped late.
  • the MBMS service stop scheduling notification may further include delay stop time length information or stop time stamp information, and is used to specify that the eNB stops scheduling the MBMS service after delaying the specified time.
  • the processor 61 controls the transmitter 63 to send a service 1 stop scheduling notification to the eNB, where the notification may be used to indicate that the service 1 is about to stop scheduling, and the eNB continues to schedule according to the MBMS service delay stop indication.
  • the service stops scheduling the service after a period of time.
  • the notification may also carry a delay stop indication to instruct the eNB to delay scheduling the service 1 .
  • a delay stop time to indicate a stop scheduling time relative to the relative time of receiving the first notification of stopping the scheduling, such as 10 minutes, 5 minutes, two modification periods or other time information, or may be Specify timestamp information, such as specific timestamp information such as 12:30, 12:40.
  • the processor 61 can control the transmitter 63 to send a delay stop indication at the same time as or after the MBMS service stop scheduling notification is sent, to instruct the eNB to delay scheduling the MBMS service.
  • the processor 61 controls the transmitter 63 to first send a service 1 to the eNB to stop scheduling the first notification, the first notification indicates that the service 1 is about to stop scheduling, and then the control transmitter 63 sends a service 1 to stop scheduling the second.
  • the second notification directly indicates that the eNB stops scheduling the service 1 immediately.
  • the optional MBMS service stop scheduling first notification is carried by the MBMS scheduling information message, and when the MBMS scheduling information does not carry the MBMS service, it indicates that the scheduling of the MBMS service is to be stopped.
  • the method disclosed in the foregoing embodiments of the present invention may be applied to the processor 61 or implemented by the processor 61.
  • each step of the above method may be completed by an integrated logic circuit of hardware in the processor 61 or an instruction in a form of software.
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or executed.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software modules can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 62, and the processor 61 reads the information in the memory 62 and combines the hardware to perform the steps of the above method.
  • the eNB receives the MBMS service stop scheduling notification sent by the MCE, and the eNB sends the MBMS service stop scheduling information to the user equipment, and continues to schedule the MBMS service.
  • the MCE determines to stop the scheduling of an MBMS service, and the user equipment that needs to continue to receive the MBMS service can continue to receive the service in the process of establishing the unicast bearer, thereby effectively reducing the scheduling of the service, and the user equipment needs to continue receiving.
  • This service establishes a service interruption time in the process of unicast bearer, giving the user a better experience.
  • FIG. 13 is a schematic structural diagram of a first group communication server according to an embodiment of the present invention.
  • the group communication server 160 of the embodiment includes a first receiving module 71, a second receiving module 72, and a notification module 73. :
  • the first receiving module 71 is configured to receive information that is received by the user equipment and receives the group service through the MBSFN.
  • the data in the MBSFN area group service is carried on the MBMS service, and the group communication server is used to manage the user equipment in the group.
  • the user equipment Before receiving the group service data, the user equipment needs to register with the group communication server.
  • the user equipment can report the information that the group service is receiving the group service through the MBSFN mode.
  • the information of the group service includes the MBSFN area identifier of the group service and the cell identifier of the group service. At least one of them.
  • the group communication server receives the information of the MBSFN receiving group service reported by the user equipment through the first receiving module 71.
  • the second receiving module 72 is configured to receive, from the MCE, the MBSFN transmission stop notification for receiving the group service.
  • the MCE decides to stop the scheduling of a certain MBMS service, and then the MCE informs the eNB to notify the group communication server before stopping the scheduling of the MBMS service.
  • the MCE can send business information that it is about to stop to the group communication server, such as the MBSFN area identifier, the MBMS server identifier, and the like.
  • the group communication server receives a certain MBSFN transmission stop notification from the MCE through the second receiving module 72.
  • the notification module 73 is configured to notify the user equipment to establish a unicast bearer, so that the user equipment continues to receive the group service through the unicast bearer after the MBSFN for receiving the group service stops.
  • the notification module 73 After the second receiving module 72 of the group communication server receives the notification that the MBSFN transmission is about to stop, the notification module 73 notifies the user equipment to establish a unicast bearer, so that the MBSFN is replaced by the unicast bearer after the MBSFN for receiving the group service is stopped. Continue to receive this group of services.
  • the notification module 73 can only notify the user equipment that needs to continue to receive the group of services to establish a unicast bearer.
  • the user equipment that needs to continue to receive the service of the group triggers the establishment of a unicast bearer to continue receiving the group of services on the unicast bearer after the MBSFN transmission is stopped.
  • the group communication server After the user equipment establishes a unicast bearer, the group communication server notifies the MCE to stop the MBSFN transmission.
  • the access layer of the user equipment determines that an MBMS service is about to stop, and sends an indication to the upper layer of the user equipment, where the user equipment high layer reports the MBMS service to the group communication server.
  • the corresponding group service cannot continue to receive the MBSFN mode.
  • the group communication server triggers the user equipment to establish a unicast bearer to continue receiving the group. business.
  • the unicast bearer is a dedicated radio bearer for transmitting MBMS services between the user equipment and the base station.
  • the user equipment is required to establish a connection with the eNB before the group service server reports that the group service corresponding to the MBMS service cannot continue to be received in the MBSFN mode.
  • the user equipment receives the network congestion.
  • the MBMS service of the eNB stops the scheduling information, it can perform a random backoff to prevent multiple user equipments from simultaneously triggering the unicast connection establishment process.
  • the user equipment generates a random factor, compares with a predetermined threshold, and determines to trigger the unicast according to the comparison result. The delay of the process. For example, if the predetermined random factor is 0.5 and the user-generated random number is 0.6, 0.6>0.5, the user delays 10ms to trigger the connection establishment.
  • the group communication server provided in this embodiment can implement various steps in the embodiment shown in FIG. 4.
  • the division of each functional module of the group communication server in this embodiment is only schematic, and on the premise that the purpose of the present invention can be achieved,
  • the division of the group communication server function modules is not limited to the above manner, and may be any other possible manner. For example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not implemented.
  • FIG. 14 is a third multi-cell/multicast collaboration provided by an embodiment of the present invention.
  • Schematic diagram of the structure of the body, the multi-cell/multicast cooperation entity 170 of this embodiment includes a determining module 81 and a notification module 82, where:
  • the determination module 81 is used to determine the MBSFN transmission that needs to be stopped.
  • the determining module 81 determines the number of user equipments of the MBMS service according to the statistical response of the base station by notifying the base station to the user equipment that receives the MBMS service. When the number of user equipments receiving the MBMS service is less than the predetermined threshold, it is determined that the MBMS needs to be stopped. MBSFN transmission mode of service.
  • the notification module 82 is configured to notify the group communication server that the MBSFN transmission is stopped after the determining module 81 determines that a certain MBSFN transmission needs to be stopped.
  • the MCE When the MCE decides to stop the MBSFN transmission of a certain MBMS service, the MCE notifies the eNB to notify the group communication server through the notification module 82 before notifying the eNB to stop scheduling the MBMS service.
  • the MCE can report the service information that it is about to stop to the group communication server, such as the MBSFN area identifier and the MBMS server identifier.
  • the group communication server is notified to the user equipment to establish a unicast bearer, so that after the user equipment stops MBSFN transmission, the unicast bearer replaces the MBSFN to continue receiving the group service.
  • the notification group communication server After the MBSFN transmission is about to stop, the notification group communication server sends MBMS service stop scheduling information to the eNB after a predetermined period of time, so that the eNB stops scheduling the MBMS service.
  • the group communication server is configured to manage the user equipment in the group. After receiving the MBSFN transmission stop notification, the user equipment can be notified to establish a unicast bearer, so that after the MBSFN transmission of the receiving group service is stopped, the unicast bearer can continue to be transmitted. Receive group business.
  • the multi-cell/multicast cooperation entity provided in this embodiment can implement the steps in the embodiment shown in FIG. 5.
  • the division of each functional module of the multi-cell/multicast collaboration entity in this embodiment is only schematic,
  • the division of the multi-cell/multicast cooperative entity function module is not limited to the above manner, and may be any other possible implementation manner. For example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not implemented.
  • FIG. 15 is a schematic structural diagram of a third user equipment according to an embodiment of the present invention.
  • the user equipment 180 in this embodiment includes a reporting module 91 and a unicast bearer establishing module 92, where:
  • the reporting module 91 is configured to report information of receiving group services through the MBSFN to the group communication server.
  • the data in the MBSFN area group service is carried on the MBMS service, and the group communication server is used to manage the user equipment in the group.
  • the reporting module 91 is also used to register with the group communication server in advance.
  • the reporting unit 91 can report the information that the group service is receiving the group service through the MBSFN mode.
  • the information of the group service includes the MBSFN area identifier of the group service and the cell identifier of the group service. At least one of them.
  • the unicast bearer establishing module 92 is configured to establish a unicast bearer according to the unicast bearer establishment notification of the group communication server, and continue to monitor the scheduling information that carries the group of services.
  • the MCE decides to stop the scheduling of a certain MBMS service, and then the MCE informs the eNB to notify the group communication server before stopping the scheduling of the MBMS service.
  • the MCE can send business information that it is about to stop to the group communication server, such as the MBSFN area identifier, the MBMS server identifier, and the like.
  • the group communication server receives a MBSFN transmission from the MCE to stop notification.
  • the group communication server After receiving the MBSFN transmission stop notification, the group communication server notifies the user equipment to establish a unicast bearer, so as to continue receiving the group service through the unicast bearer.
  • the group communication server notifies the user equipment to establish a unicast bearer, so as to continue receiving the group service through the unicast bearer.
  • the group communication server notifies the user equipment to establish a unicast bearer, so as to continue receiving the group service through the unicast bearer.
  • the group communication server After receiving the MBSFN transmission stop notification, the group communication server notifies the user equipment to establish a unicast bearer, so as to continue receiving the group service through the unicast bearer.
  • the unicast bearer establishing module 92 triggers the establishment of the unicast bearer according to the notification of the group communication server, and continues to receive the group of services on the unicast bearer after the MBSFN transmission stops.
  • the group communication server notifies the MCE to stop the MBSFN transmission.
  • the user equipment During the establishment of the unicast bearer, the user equipment continues to listen to the scheduling information of the group of services. After the unicast bearer is established, the user equipment stops listening to the scheduling information of the bearer group service, and continues to receive the group service through the unicast bearer.
  • the user equipment provided in this embodiment can implement various steps in the embodiment shown in FIG. 6.
  • the division of each functional module of the user equipment in this embodiment is only schematic, and the user equipment can be implemented on the premise that the purpose of the present invention can be achieved.
  • the division of the functional modules is not limited to the above, and may be any other possible way of implementation. For example, multiple units or components can be combined or integrated into Another system, or some features can be ignored, or not executed.
  • FIG. 16 is a schematic structural diagram of a second group communication server according to an embodiment of the present invention.
  • the group communication server 190 includes a processor 191, a receiver 193, a memory 192, and a bus system 194, where:
  • the processor 191 controls the operation of the group communication server 190, which may also be referred to as a CPU (Central Processing Unit).
  • the processor 191 may be an integrated circuit chip with signal processing capabilities.
  • the processor 191 can also be a general-purpose processor, a digital signal processing (DSP), an application specific integrated circuit (ASIC), a Field-Programmable Gate Array (FPGA), or the like. Programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • Memory 192 can include read only memory and random access memory and provides instructions and data to processor 191. A portion of memory 192 may also include non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • the various components of the group communication server 190 are coupled together by a bus system 194, which may include, in addition to the data bus, a power bus, a control bus, and a status signal bus.
  • the bus system may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus.
  • the bus may be one or more physical lines, and may be divided into an address bus, a data bus, a control bus, etc. when it is a plurality of physical lines.
  • the processor 191, the memory 192, and the receiver 193 may also be directly connected through a communication line.
  • various buses are labeled as bus system 194 in the figure.
  • Memory 192 stores the following elements, executable modules or data structures, or a subset thereof, or their extended set:
  • Operation instructions Includes various operation instructions for implementing various operations.
  • Operating System Includes a variety of system programs for implementing a variety of basic services and handling hardware-based tasks.
  • the processor 191 calls the operation instruction stored in the memory 192 (the The operation instructions can be stored in the operating system), and the following operations are performed:
  • the processor 191 is configured to control the receiver 193 to receive the information of the group service received by the user equipment through the MBSFN, and control the receiver 193 to receive a certain MBSFN transmission stop notification from the MCE, and notify the user equipment to establish a unicast bearer, so that the user equipment passes the single The broadcast bearer continues to receive group services.
  • Memory 192 is used to store group service data.
  • the data in the MBSFN area group service is carried on the MBMS service, and the group communication server is used to manage the user equipment in the group.
  • the user equipment Before receiving the group service data, the user equipment needs to register with the group communication server.
  • the user equipment can report the information that the group service is receiving the group service through the MBSFN mode.
  • the information of the group service includes the MBSFN area identifier of the group service and the cell identifier of the group service. At least one of them.
  • the group communication server receives the information of the MBSFN receiving group service reported by the user equipment through the first receiving module 71.
  • the MCE decides to stop the scheduling of a certain MBMS service, and then the MCE informs the eNB to notify the group communication server before stopping the scheduling of the MBMS service.
  • the MCE can report the service information that it is about to stop to the group communication server, such as the MBSFN area identifier and the MBMS server identifier.
  • the group communication server processor 191 controls the receiver 193 to receive a MBSFN transmission from the MCE to stop notification. After the receiver 193 receives a certain MBSFN transmission imminent stop notification, the processor 191 notifies the user equipment to establish a unicast bearer to continue receiving the group of services through the unicast bearer. As a preference, the processor 191 can only notify the user equipment that needs to continue to receive the group of services to establish a unicast bearer.
  • the user equipment that needs to continue to receive the service of the group triggers the establishment of a unicast bearer to continue receiving the group of services on the unicast bearer after the MBSFN transmission is stopped.
  • the group communication server After the user equipment establishes a unicast bearer, the group communication server notifies the MCE to stop the MBSFN transmission.
  • the access layer of the user equipment determines that an MBMS service is about to stop, and sends an indication to the upper layer of the user equipment, where the user equipment high layer reports the MBMS service to the group communication server.
  • the corresponding group service cannot continue to receive in the MBSFN mode.
  • the group communication server triggers the user equipment to establish a unicast bearer to continue to receive the request. Receive the group business.
  • the unicast bearer is one for transmission between the user equipment and the base station.
  • the user equipment is required to establish a connection with the eNB before the group service server reports that the group service corresponding to the MBMS service cannot continue to be received in the MBSFN mode.
  • the user equipment receives the network congestion.
  • the MBMS service of the eNB stops the scheduling information, it can perform a random backoff to prevent multiple user equipments from simultaneously triggering the unicast connection establishment process.
  • the user equipment generates a random factor, compares with a predetermined threshold, and determines to trigger the unicast according to the comparison result. The delay of the process. For example, if the predetermined random factor is 0.5 and the user-generated random number is 0.6, 0.6>0.5, the user delays 10ms to trigger the connection establishment.
  • each step of the above method may be completed by an integrated logic circuit of the hardware in the processor 191 or an instruction in the form of software.
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software modules can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 192, and the processor 191 reads the information in the memory 192 and combines the hardware to complete the steps of the above method.
  • FIG. 17 is a schematic structural diagram of a fourth multi-cell/multicast cooperation entity according to an embodiment of the present invention.
  • the multi-cell/multicast cooperation entity 200 of this embodiment includes a processor 201, a memory 202, and a transmitter 203. And a bus system 204, wherein:
  • the processor 201 controls the operation of the multi-cell/multicast cooperative entity 200, which may also be referred to as a CPU (Central Processing Unit).
  • Processor 201 may be an integrated circuit chip with signal processing capabilities.
  • the processor 201 can also be a general-purpose processor, a digital signal processing (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a Field-Programmable Gate Array (FPGA). Programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 202 can include a read only memory and a random access memory, and is directed to the processor 201 Provide instructions and data.
  • a portion of memory 202 may also include non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • the various components of the multi-cell/multicast cooperative entity 200 are coupled together by a bus system 204, which may include, in addition to the data bus, a power bus, a control bus, a status signal bus, and the like.
  • the bus system may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus.
  • the bus may be one or more physical lines, and may be divided into an address bus, a data bus, a control bus, etc. when it is a plurality of physical lines.
  • the processor 201, the memory 202, and the transmitter 203 may also be directly connected through a communication line.
  • various buses are labeled as bus system 204 in the figure.
  • Memory 202 stores the following elements, executable modules or data structures, or a subset thereof, or their extended set:
  • Operation instructions Includes various operation instructions for implementing various operations.
  • Operating System Includes a variety of system programs for implementing a variety of basic services and handling hardware-based tasks.
  • the processor 201 performs the following operations by calling an operation instruction stored in the memory 202 (the operation instruction can be stored in the operating system):
  • the processor 201 is configured to determine an MBMS service that needs to be closed, and the control transmitter 203 sends an MBMS service stop scheduling notification to the base station, where the MBMS service stop scheduling notification indicates that an MBMS service is about to stop scheduling, and the processor 201 instructs the base station to continue to schedule the MBMS service. ;
  • the memory 202 is used to store MBMS service data.
  • the processor 201 determines the number of user equipments of the MBMS service according to the statistical response of the base station by notifying the base station of the user equipment that receives the MBMS service, and determines that the MBMS needs to be stopped when the number of the user equipments that receive the MBMS service is less than a predetermined threshold.
  • the MBSFN transmission method of the service is notifying the base station of the user equipment that receives the MBMS service, and determines that the MBMS needs to be stopped when the number of the user equipments that receive the MBMS service is less than a predetermined threshold.
  • the processor 201 controls the transmitter 203 to notify the group communication server first.
  • the sender 203 can report the service information that is about to stop, such as the MBSFN area identifier, the MBMS server identifier, and the like, to the group communication server.
  • the user equipment establishes a unicast bearer, so that after the user equipment stops the MBSFN transmission, the unicast bearer replaces the MBSFN to continue receiving the group service.
  • the notification group communication server After the MBSFN transmission is about to stop, the notification group communication server sends MBMS service stop scheduling information to the eNB after a predetermined period of time, so that the eNB stops scheduling the MBMS service.
  • the group communication server is configured to manage the user equipment in the group. After receiving the MBSFN transmission stop notification, the user equipment can be notified to establish a unicast bearer, so that after the MBSFN transmission of the receiving group service is stopped, the unicast bearer can continue to be transmitted. Receive group business.
  • the method disclosed in the foregoing embodiments of the present invention may be applied to the processor 201 or implemented by the processor 201.
  • each step of the above method may be completed by an integrated logic circuit of hardware in the processor 201 or an instruction in a form of software.
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software modules can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 202, and the processor 201 reads the information in the memory 202 and combines the hardware to perform the steps of the above method.
  • FIG. 18 is a schematic structural diagram of a fourth user equipment according to an embodiment of the present invention.
  • the user equipment 210 of this embodiment includes a processor 211, a memory 212, a receiver 213, and a bus system 204, where:
  • the processor 211 controls the operation of the user equipment 210, which may also be referred to as a CPU (Central Processing Unit).
  • Processor 211 may be an integrated circuit chip with signal processing capabilities.
  • the processor 211 can also be a general-purpose processor, a digital signal processing (DSP), an application specific integrated circuit (ASIC), a Field-Programmable Gate Array (FPGA), or the like. Programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • Memory 212 can include read only memory and random access memory and provides instructions and data to processor 211. A portion of the memory 212 may also include non-volatile random access storage (NVRAM).
  • NVRAM non-volatile random access storage
  • the various components of user equipment 210 are coupled together by a bus system 214, which may include, in addition to the data bus, a power bus, a control bus, a status signal bus, and the like.
  • the bus system may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus.
  • the bus may be one or more physical lines, and when it is a plurality of physical lines, it may be divided into an address bus, a data bus, a control bus, and the like.
  • the processor 211, the memory 212, and the receiver 213 may also be directly connected through a communication line.
  • various buses are labeled as bus system 214 in the figure.
  • Memory 212 stores the following elements, executable modules or data structures, or a subset thereof, or their extended set:
  • Operation instructions Includes various operation instructions for implementing various operations.
  • Operating System Includes a variety of system programs for implementing a variety of basic services and handling hardware-based tasks.
  • the processor 211 performs the following operations by calling an operation instruction stored in the memory 212 (the operation instruction can be stored in the operating system):
  • the processor 211 is configured to report the information of the group service through the MBSFN to the group communication server, and control the receiver 213 to receive the notification of the group communication server, and establish a unicast bearer when the group service needs to continue to be received according to the notification of the group communication server. At the same time, the scheduling information carrying the service of the group is continuously monitored.
  • Memory 212 is used to store data.
  • the data in the MBSFN area group service is carried on the MBMS service, and the group communication server is used to manage the user equipment in the group.
  • the user equipment Before receiving the group service data, the user equipment needs to register with the group communication server.
  • the processor 211 reports to the group communication server that the information of the group service is being received by the MBSFN mode, and the information of the group service includes the MBSFN area identifier of the group service and the cell identifier of the group service. At least one.
  • the MCE decides to stop the scheduling of a certain MBMS service, and then the MCE notifies the eNB to notify the group communication server before stopping the scheduling of the MBMS service.
  • MCE can be sent to the group communication server ⁇ Business information that you are about to stop, such as MBSFN area labeling, MBMS server ID, etc.
  • the group communication server receives a MBSFN transmission from the MCE to stop notification.
  • the group communication server After receiving the MBSFN transmission stop notification, the group communication server notifies the user equipment to establish a unicast bearer, so as to continue receiving the group service through the unicast bearer.
  • the group communication server notifies the user equipment to establish a unicast bearer, so as to continue receiving the group service through the unicast bearer.
  • the group communication server notifies the user equipment to establish a unicast bearer, so as to continue receiving the group service through the unicast bearer.
  • the group communication server After receiving the MBSFN transmission stop notification, the group communication server notifies the user equipment to establish a unicast bearer, so as to continue receiving the group service through the unicast bearer.
  • the processor 211 triggers the establishment of the unicast bearer according to the notification of the group communication server, and continues to receive the group of services on the unicast bearer after the MBSFN transmission is stopped.
  • the group communication server After the user equipment establishes a unicast bearer, the group communication server notifies the MCE to stop the MBSFN transmission.
  • the processor 211 continues to monitor the scheduling information that carries the service. After the unicast bearer is established, the processor 211 stops listening to the scheduling information of the bearer group service, and continues to receive the group service by using the unicast bearer. .
  • the method disclosed in the foregoing embodiment of the present invention may be applied to the processor 211 or implemented by the processor 211.
  • each step of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 211 or an instruction in a form of software.
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software modules can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 212, and the processor 211 reads the information in the memory 212 and combines the hardware to perform the steps of the above method.
  • the MCE decides to stop a certain MBSFN transmission that needs to be stopped, it notifies the eNB before notifying the eNB.
  • the group communication server of the user equipment in the management group the group communication server notifies the user equipment to establish a unicast bearer, and then notifies the MCE to stop the MBSFN transmission after the user equipment establishes the unicast bearer.
  • the present invention is to solve the problem that the MCE needs to continue to receive the unicast bearer after the MCE determines to stop scheduling the service, and how to reduce the service interruption time caused by the unicast bearer establishment process. .
  • the sent MBMS service stops scheduling notification, and the base station sends a notification to the user equipment that the MBMS service stops scheduling information, and continues to schedule the MBMS service.
  • the MCE determines to stop the scheduling of an MBMS service, and the user equipment that needs to continue to receive the MBMS service can continue to receive the service in the process of establishing the unicast bearer, thereby effectively reducing the scheduling of the service, and the user equipment needs to continue receiving.
  • This service establishes a service interruption time in the process of unicast bearer, giving the user a better experience.
  • the embodiment of the present invention provides a method and a device for maintaining service continuity.
  • the MCE decides to stop an MBSFN transmission that needs to be stopped, the MCE notifies the group communication server of the user equipment in the management group before notifying the eNB.
  • the group communication server notifies the user equipment to establish a unicast bearer, and then notifies the MCE to stop the MBSFN transmission after the user equipment establishes the unicast bearer.
  • the user equipment that needs to continue to receive the group service transmitted through the MBSFN first establishes a unicast bearer according to the notification of the group communication server, thereby avoiding interruption of the group service and giving the user a better Use experience.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the modules or units is only a logical function division.
  • there may be another division manner for example, multiple units or components may be used. Combined or can be integrated into another system, or some features can be ignored, or not executed.
  • the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical, mechanical or otherwise.
  • the components displayed as units may or may not be physical units, i.e., may be located in one place, or may be distributed over multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated in In a unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • the instructions include a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a multi-cell/multicast collaboration entity, etc.) or a processor to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes:
  • U disk removable hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM), disk or optical disk, and other media that can store program code.
  • ROM read-only memory
  • RAM random access memory

Landscapes

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

Abstract

本发明公开了一种保持业务连续性的方法及设备。其中,保持业务连续性的方法包括:基站接收MCE发送的MBMS业务停止调度第一通知;基站发送通知用户设备MBMS业务停止调度信息,继续调度MBMS业务。通过这样的方式,能够有效减少因MCE停止调度某业务后而导致UE接收该业务出现的业务中断时间。

Description

一种保持业务连续性的方法及 i殳备 技术领域
本发明涉及通信领域, 特别涉及一种保持业务连续性的方法及设备。 背景技术
多媒体广播组播业务( MBMS , Multimedia Broadcast Multicast Service ) 是利用广播信道同时向多个用户设备 ( UE , User Equipment )发送相同业务 的技术,接收同一业务的一组 UE使用相同的下行配置来进行业务接收, 不 必为每个 UE建立自己的链路。
多媒体广播组播业务单频网 ( MBSFN , Multimedia Broadcast Multicast Service Single Frequency Network )是在同一时间以相同频率在多个小区进 行同步传输的传输方式, 使用该传输方式可以有效节约频率资源, 提高频 谱利用率, 并提高覆盖率。
多小区 /多播协作实体( MCE, Multicast Coordination Entity )是一种逻 辑实体,可以配置多个用于进行 MBSFN传输的 MBSFN区域,并为 MBSFN 区域的所有演进型基站 (eNB , Evolved Node B ) 分配无线资源以进行 MBSFN传输。
MCE通过统计的方式通知对接收业务的 UE进行统计, 在接收业务的 UE少于一定数量时, MCE可能会确定关闭该业务的 MBSFN传输,具体实 现过程如下: MCE决定关闭某业务的 MBSFN传输,在通过 MBMS调度信 息更新 eNB的配置, 在新的配置中不再携带该业务信息; eNB通知 UE更 新业务配置, 新的业务配置中不再携带该业务信息; UE收到更新后的业务 配置后, 发现该业务不在新的配置信息中, 则认为该业务停止; 如果 UE 希望继续接收该业务, 需要再触发单播业务建立, 通过单播业务继续接收 该 MBMS业务。
由此可知, 如果 MCE关闭一个 MBMS业务的 MBSFN传输, 则 UE 需要检测到该业务 MBSFN传输关闭后,通过建立单播承载继续接收 MBMS 业务。 直到单播承载建立完毕才能继续接受 MBMS业务。 由于单播承载建 立需要一段时间, 在这段时间内 UE接收该业务会经历一段中断。 发明内容
本申请主要解决的技术问题是 MCE确定停止调度某业务后,需要继续 接收该业务的 UE需要建立单播承载,如何减少在单播承载建立过程中引发 的业务中断时间。
有鉴于此, 本申请提出一种保持业务连续性的方法及设备, 能够有效 减少因 MCE停止调度某业务后而导致 UE接收该业务的业务中断时间。
第一方面, 本申请提供一种保持业务连续性的方法, 包括: 基站接收 多小区 /多播协作实体发送的多媒体广播组播业务 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业务的调度信息; 根据所述 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 业务停止调度通知包括所述继续调度预定时间的时间长度信息或者预定停 止时间戳信息或者停止 MBMS业务的指示信息, 以指示所述基站继续调度 所述 MBMS业务预定时间。
结合第三方面或第三方面的第一种可能的实现方式, 在第三方面的第 二种可能的实现方式中: 所述多小区 /多播协作实体确定需要关闭的 MBMS 业务的步骤包括: 所述多小区 /多播协作实体通知所述基站统计接收所述 MBMS业务的用户设备; 根据基站统计响应确定所述 MBMS业务的用户设 备的数量, 在所述接收所述 MBMS业务的用户设备数量少于预定门限时, 确定需要关闭所述 MBMS业务或者所述多小区 /多播协作实体收到应用服务 器发送的关闭所述 MBMS业务的请求信息。
结合第三方面或第三方面的第一至第二种任一可能的实现方式, 在第 三方面的第三种可能的实现方式中: 所述向基站发送 MBMS业务停止调度 通知的步骤包括: 通过 MBMS调度信息更新基站的配置信息, 更新后的所 述配置信息不再携带所述需要关闭的 MBMS业务的配置信息, 以作为向基 站发送的所述 MBMS业务停止调度通知。
第四方面, 本申请保持业务连续性的方法, 所述方法包括: 组通讯服 务器接收用户设备上报的通过多媒体广播组播业务单频网 MBSFN接收组业 务的信息; 所述组通讯服务器从多小区 /多播协作实体接收用于接收所述组 业务的所述 MBSFN传输停止通知 ,所述组通讯服务器根据述 MBSFN传输停 止通确定所述 MBSFN传输即将停止; 所述组通讯服务器通知所述用户设备 建立单播承载,以便所述用户设备在用于接收组业务的所述 MBSFN停止后, 通过所述单播承载继续接收所述组业务。
结合第四方面, 在第四方面的第一种可能的实现方式中: 所述 MBSFN 传输停止通知包含停止调度的业务信息, 所述业务信息包括所述 MBSFN区 域信息以及 MBMS的标识中的至少一种。
结合第四方面或第四方面的第一种可能的实现方式, 在第四方面的第 二种可能的实现方式中: 所述方法还包括: 在所述用户设备建立单播承载 后, 所述组通讯服务器通知所述多小区 /多播协作实体停止所述 MBSFN传 输。
第五方面, 本申请提供一种保持业务连续性的方法, 所述方法包括: 多小区 /多播协作实体确定需要停止的 MBSFN传输;通知组通讯服务器所述 MBSFN传输停止,以使所述组通讯服务器通知所述用户设备建立单播承载, 以便所述用户设备在所述 MBSFN传输停止后, 通过所述单播承载代替所述 MBSFN继续接收所述组业务。
结合第五方面, 在第五方面的第一种可能的实现方式中: 所述多小区 / 多播协作实体确定需要停止的 MBSFN传输的步骤包括:所述多小区 /多播协 作实体通知基站统计接收所述 MBMS业务的用户设备; 根据所述基站统计 响应确定所述 MBMS业务的用户设备的数量, 在所述接收所述 MBMS业务 的用户设备数量少于预定门限时, 确定需要停止所述 MBMS业务的 MBSFN 传输方式。
结合第五方面或第五方面的第一种可能的实现方式, 在第五方面的第 二种可能的实现方式中: 所述 MBSFN传输即将停止通知包含停止调度的业 务信息, 所述业务信息包括所述 MBSFN区域信息以及 MBMS的标识中的至 少一种。
第六方面, 本申请提供一种保持业务连续性的方法, 所述方法包括: 用户设备向组通讯服务器上报通过多媒体广播组播业务单频网 MBSFN接收 组业务的信息; 根据所述组通讯服务器的单播承载建立通知, 建立单播承 载, 同时继续监听承载所述组业务的调度信息。
结合第六方面, 在第六方面的第一种可能的实现方式中: 所述组业务 的信息包括: 所述 MBSFN区域信息以及 MBMS的标识中的至少一种。
结合第六方面或第六方面的第一种可能的实现方式, 在第六方面的第 二种可能的实现方式中: 所述用户设备向组通讯服务器上报通过 MBSFN接 收组业务的信息的步骤之前, 还包括: 所述用户设备向所述组通讯服务器 进行注册。
结合第六方面或第六方面的第一种至第二种任一可能的实现方式, 在 第六方面的第三种可能的实现方式中: 所述方法还包括: 所述单播承载建 立完成后, 所述用户设备停止监听承载所述组业务的调度信息。
第七方面, 提供一种基站, 所述基站包括接收模块和调度模块, 其中: 所述接收模块用于接收多小区 /多播协作实体发送的多媒体广播组播业务 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业务的调度信息, 接收所述 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业务的用户设备, 根据基站统计响应确定所述 MBMS业务的用户 设备的数量, 在所述接收所述 MBMS业务的用户设备数量少于预定门限时, 确定需要关闭所述 MBMS业务的 MBSFN传输方式。
结合第九方面或第九方面的第一种至第二种任一可能的实现方式, 在 第九方面的第三种可能的实现方式中: 所述调度模块通过 MBMS调度信息 更新基站的配置信息, 更新后的所述配置信息不再携带所述需要关闭的 MBMS业务的配置信息, 以作为向基站发送的所述 MBMS业务停止调度通 知。
第十方面, 提供一种基站, 所述基站包括处理器、 接收器、 发送器和 存储器, 所述处理器分别耦接所述接收器、 发送器以及存储器, 其中: 所 述处理器用于控制接收器接收多小区 /多播协作实体发送的多媒体广播组播 业务 MBMS业务停止调度第一通知, 所述 MBMS业务停止调度第一通知是 所述多小区 /多播协作实体确定关闭所述 MBMS业务时向所述基站发送的通 知, 在接收所述 MBMS业务停止调度第一通知后, 控制所述发送器向用户 设备发送 MBMS业务停止调度信息, 所述处理器继续调度所述 MBMS业务 直到满足预定条件再停止调度所述 MBMS业务; 所述存储器用于存储所述 MBMS数据。
第十一方面, 提供一种用户设备, 所述用户设备包括处理器、 接收器 以及存储器, 所述处理器分别耦接所述接收器和所述存储器, 其中: 所述 处理器用于控制所述接收器从基站接收 MBMS业务停止调度信息, 确定所 述基站在满足预定条件时停止调度所述 MBMS业务, 继续监听所述 MBMS 业务的调度信息, 并控制所述接收器根据所述处理器监听到的所述 MBMS 业务的调度信息, 接收所述 MBMS业务; 所述存储器用于存储所述 MBMS 业务数据。
第十二方面, 提供一种多小区 /多播协作实体, 所述多小区 /多播协作实 体包括处理器、 发送器和存储器, 所述处理器分别耦接所述发送器和存储 器, 其中: 所述处理器用于确定需要关闭的 MBMS业务, 控制所述发送器 向基站发送 MBMS业务停止调度通知, 所述 MBMS业务停止调度通知告知 所述基站所述 MBMS业务满足预定条件时停止调度, 所述处理器指示所述 基站继续调度所述 MBMS业务; 所述存储器用于存储所述 MBMS业务数据。
第十三方面, 提供一种组通讯服务器, 所述组通讯服务器包括第一接 收模块、 第二接收模块以及通知模块, 其中: 所述第一接收模块用于接收 用户设备上报的通过多媒体广播组播业务单频网 MBSFN接收组业务的信 息; 所述第二接收模块用于从多小区 /多播协作实体接收用于接收所述组业 务的所述 MBSFN传输停止通知; 所述通知模块用于通知所述用户设备建立 单播承载,以便所述用户设备在用于接收所述组业务的所述 MBSFN停止后, 通过所述单播承载继续接收所述组业务。
结合第十三方面, 在第十三方面的第一种可能的实现方式中: 所述 MBSFN传输停止通知包含停止调度的业务信息, 所述业务信息包括所述 MBSFN信息以及 MBMS的标识中的至少一种。
结合第十三方面或第十三方面的第一种可能的实现方式, 在第十三方 面的第二种可能的实现方式中: 所述通知模块还用于在所述用户设备建立 单播承载后, 通知所述多小区 /多播协作实体停止所述 MBSFN传输。
第十四方面, 提供一种多小区 /多播协作实体, 所述多小区 /多播协作实 体包括确定模块和通知模块, 其中: 所述确定模块用于确定需要停止的 MBSFN传输; 所述通知模块用于在所述确定模块确定需要停止的所述 MBSFN传输后,通知组通讯服务器所述 MBSFN传输停止, 以使所述组通讯 服务器通知所述用户设备建立单播承载, 以便所述用户设备在所述 MBSFN 传输停止后, 通过所述单播承载代替所述 MBSFN继续接收所述组业务。
结合第十四方面, 在第十四方面的第一种可能的实现方式中: 所述确 定模块通过通知基站统计接收所述 MBMS业务的用户设备, 根据所述基站 统计响应确定所述 MBMS业务的用户设备的数量, 在所述接收所述 MBMS 业务的用户设备数量少于预定门限时, 确定需要停止所述 MBMS业务的 MBSFN传输方式。
结合第十四方面或第十四方面的第一种可能的实现方式, 在第十四方 面的第二种可能的实现方式中: 所述 MBSFN传输停止通知包含停止调度的 业务信息, 所述业务信息包括所述 MBSFN信息以及 MBMS的标识中的至少 一种。
第十五方面, 提供一种用户设备, 所述用户设备包括上报模块和单播 承载建立模块, 其中: 所述上报模块用于向组通讯服务器上报通过多媒体 广播组播业务单频网 MBSFN接收组业务的信息; 所述单播承载建立模块用 于根据组通讯服务器的所述 MBSFN传输停止通知,在所述 MBSFN传输停止 后需要继续接收所述组业务时, 建立单播承载, 同时继续监听承载所述组 业务的调度信息。
结合第十五方面, 在第十五方面的第一种可能的实现方式中: 所述组 业务的信息包括所述 MBSFN信息以及 MBMS的标识中的至少一种。
结合第十五方面或第十五方面的第一种可能的实现方式, 在第十五方 面的第二种可能的实现方式中: 所述上报模块还用于向所述组通讯服务器 进行注册。
结合第十五方面或第十五方面的第一种至第二种任一可能的实现方 式, 在第十五方面的第三种可能的实现方式中: 所述单播承载建立模块在 所述单播承载建立完成后, 停止监听承载所述组业务的调度信息。
第十六方面, 提供一种组通讯服务器, 所述组通讯服务器包括处理器、 接收器和存储器, 所述处理器分别耦接所述接收器和所述存储器, 其中: 所述处理器用于控制所述接收器接收用户设备上报的通过多媒体广播组播 业务单频网 MBSFN接收组业务的信息,并控制所述接收器从多小区 /多播协 作实体接收用于接收所述组业务的所述 MBSFN传输停止通知, 通知所述用 户设备建立单播承载, 以便所述用户设备在用于接收所述组业务的所述 MBSFN停止后, 通过所述单播承载继续接收所述组业务; 所述存储器用于 存储所述组业务数据。
第十七方面, 提供一种多小区 /多播协作实体, 所述多小区 /多播协作实 体包括处理器、 发送器和存储器, 所述处理器分别耦接所述发送器和存储 器, 其中: 所述处理器用于确定需要停止的 MBSFN传输, 控制所述发送器 向组通讯服务器发送通知,以通知所述组通讯服务器所述 MBSFN传输停止, 以使所述组通讯服务器通知所述用户设备建立单播承载, 以便所述用户设 备在所述 MBSFN传输停止后,通过所述单播承载代替所述 MBSFN继续接收 所述组业务; 所述存储器用于存储数据。
第十八方面, 提供一种用户设备, 所述用户设备包括处理器、 接收器 和存储器, 所述处理器分别耦接所述接收器和所述存储器, 其中: 所述处 理器用于向组通讯服务器上报通过多媒体广播组播业务单频网 MBSFN接收 组业务的信息, 并控制接收器接收组通讯服务器的通知, 根据所述组通讯 服务器的所述 MBSFN传输停止通知,在所述 MBSFN传输停止后需要继续接 收所述组业务时, 建立单播承载, 同时继续监听承载所述组业务的调度信 息; 所述存储器用于存储数据。
相对于现有技术, 本申请的有益效果: 上述技术方案, 基站接收 MCE 发送的 MBMS业务停止调度通知, 基站发送通知用户设备 MBMS业务停 止调度信息, 继续调度该 MBMS业务。 通过这样的方式, 使得 MCE确定 停止某 MBMS业务调度, 而需要继续接收该 MBMS业务的用户设备在建 立单播承载过程中也能继续接收该业务, 有效减少因业务停止调度, 用户 设备需要继续接收该业务而建立单播承载的过程中业务中断时间, 给用户 更好的使用体验。 附图说明
图 1是本发明实施例提供的 :一种保持业务连续性的方法的流程图 图 2是本发明实施例提供的 <二种保持业务连续性的方法的流程图 图 3是本发明实施例提供的 <三种保持业务连续性的方法的流程图 图 4是本发明实施例提供的 :四种保持业务连续性的方法的流程图 图 5是本发明实施例提供的 <五种保持业务连续性的方法的流程图 图 6是本发明实施例提供的 <六种保持业务连续性的方法的流程图 图 7是本发明实施例提供的 :一种基站的结构示意图;
图 8是本发明实施例提供的 :一种用户设备的结构示意图;
图 9是本发明实施例提供的 :一种多小区 /多播协作实体的结构示意图 图 10是本发明实施例提供的 :二种基站的结构示意图;
图 11是本发明实施例提供的 :二种用户设备的结构示意图;
图 12是本发明实施例提供的 %二种多小区 /多播协作实体的结构示意 图 13是本发明实施例提供的 -一种组通讯服务器的结构示意图; 图 14是本发明实施例提供的 三种多小区 /多播协作实体的结构示意 图 15是本发明实施例提供的 :三种用户设备的结构示意图;
图 16是本发明实施例提供的 :二种组通讯服务器的结构示意图; 图 17是本发明实施例提供的 四种多小区 /多播协作实体的结构示意 图 18是本发明实施例提供的第四种用户设备的结构示意图 具体实肺式
请参阅图 1 ,图 1是本发明实施例提供的第一种保持业务连续性的方法 的流程图, 本实施例以基站的角度来进行描述, 本实施例的保持业务连续 性的方法包括:
S101 :基站接收多小区 /多播协作实体发送的 MBMS业务停止调度第一 通知;
多小区 /多播协作实体( MCE, Multicast Coordination Entity )首先触发 基站( eNB, Evolved Node B )统计接收某个 MBMS业务的用户设备, eNB 统计响应确定该 MBMS业务的用户设备的数量, 在接收该 MBMS业务的 用户设备少于预定门限时, MCE确定停止该 MBMS业务的调度。 MCE通 知 eNB停止对接收用户设备少于预定门限的 MBMS业务的调度,比如停止 对业务 1的调度。
eNB接收 MCE发送的 MBMS业务停止调度第一通知。该 MBMS业务 停止调度第一通知是 MCE确定关闭该 MBMS业务时向基站发送的通知, 该 MBMS业务停止调度第一通知可以用于指示某个 MBMS业务满足预定 条件时停止调度。 这个预定条件, 可以是一定的时间后、 或固定的时间点 或者是再次收到 MBMS业务停止调度等等。当然也可以是其他的指定条件。 可选的, 该 MBMS业务停止调度第一通知还可以携带延迟停止指示, 以指示 eNB延迟停止调度该 MBMS业务。 更进一步地, MBMS业务停止 调度第一通知还可以包括延迟停止时间长度信息或者停止时间戳信息, 用 于指定 eNB延迟指定时间后停止调度该 MBMS业务。
比如 MCE决定停止对业务 1的调度, 则向 eNB发送业务 1停止调度 第一通知, 该通知可以用于指示业务 1 即将停止调度, 或者第一通知可以 携带延迟停止指示,以指示 eNB延迟停止调度业务 1 , eNB根据所述 MBMS 业务延迟停止指示继续调度所述业务一段时间后停止对所述业务的调度。 并可以进一步指定延迟停止的时间, 用以指示停止调度时间相对于收到所 述停止调度第一通知的相对时间, 如 10分钟、 5分钟、 两个修改周期或者 别的时间信息, 也可以是指定时间戳信息, 如 12点 30分、 12点 40分这样 的具体时间戳信息。
可选的所述 MBMS业务停止调度第一通知通过 MBMS调度信息消息 携带, 当所述 MBMS调度信息不再携带所述 MBMS业务的配置信息时, 表示要停止所述 MBMS业务的调度。
S102:基站根据 MBMS业务停止调度第一通知向用户设备发送 MBMS 业务停止调度信息;
eNB在接收到 MCE的 MBMS业务停止调度第一通知后, eNB向用户 设备发送所述 MBMS业务停止调度信息。
其中, eNB可以通过点到多点控制信道消息中不携带所述 MBMS业务 的配置信息作为向用户设备发送的所述 MBMS业务停止调度信息。
可选的, 所述 MBMS业务停止调度信息可以携带所述 MBMS业务即 将停止调度指示, 以告知用户设备即将停止调度该 MBMS 业务。 在所述 MBMS业务满足预定条件时停止调度后,向用户设备发送所述 MBMS业务 停止通知, 以告知用户设备所述 MBMS业务停止。
可选的, 在 eNB通知用户设备业务停止调度信息的同时或之后, 还发 送延迟停止指示, 以告知用户设备会延迟停止调度所述 MBMS。 在所述 MBMS业务满足预定条件时停止调度后, 停止调度 MBMS业务停止。
其中, 上述 MBMS业务延迟停止指示或者所述 MBMS业务即将停止 调度指示可以通过点到多点控制信道、 寻呼控制信道、 MBMS传输信道调 度信息中的任何一种发送给用户设备。 具体而言, 如果通过点到多点控制 信道信道发送延迟停止指示或者所述 MBMS业务即将停止调度指示, 可以 在通过承载在点到多点控制信道信道上的计数请求消息发送, 例如通过在 计数请求中增加延迟停止指示或者所述 MBMS业务即将停止调度指示; 如 果通过 MBMS传输信道调度信息发送延迟停止指示, 可以通过 MBMS传 输信道调度信息消息中的 MBMS业务信道停止位置指示 (MTCH stop ) 字 段的特殊值来表示延迟停止指示或者所述 MBMS业务即将停止调度指示。
S103 : 基站继续调度该 MBMS 业务直到满足预定条件再停止调度该 MBMS业务;
eNB继续调度所述 MBMS业务, 具体的, eNB在 MBMS传输信道调 度信息中 (MSI )继续指示所述 MBMS的发送位置, 以使得需要继续接收 所述 MBMS 业务的用户设备触发建立单播承载, 在单播承载过程中该 MBMS业务的不会发生中断或中断时间减少。
其中, eNB可以在满足以下条件之一时, 停止调度该 MBMS业务: 收 到 MCE发送的 MBMS业务停止调度第二通知,该 MBMS业务停止调度第 二通知指示该 MBMS业务停止调度; 或收到该 MBMS业务停止调度第一 通知之后, 达到该 MBMS业务停止调度第一通知指示的时间点; 或收到该 MBMS业务停止调度第一通知之后经过第一预定时间; 或收到业务停止调 度第一通知之后, 达到第二预定时间点。
具体地解释上述三种情况, 第一种情况是 MCE发送 MBMS业务停止 调度第一通知, 通知某个业务即将停止调度, 然后经过预定时间后, MCE 再发送该 MBMS业务停止调度第二通知,该通知直接指示 eNB停止调度该 MBMS业务。
另一种情况是, MCE直接在 MBMS业务停止调度第一通知中携带延 迟停止指示,并且停止调度时间点为预定义的时间点,比如收到所述 MBMS 业务停止调度第一通知之后下下个修改周期的起始时间停止, 或者可以一 进一步第一通知中携带的延迟停止指示具体的延迟时间, eNB接收到 MCE 的该 MBMS业务停止调度第一通知, 延迟一段时间停止调度该业务。 或者 进一步达到该第一通知指示的时间点就停止调度该 MBMS业务。
还有一种情况是, MCE发送的 MBMS业务停止调度第一通知, 只是 通知某个 MBMS业务停止调度 (即该第一通知就是普通的 MBMS业务停 止调度通知), eNB在接收到该通知后, 自行继续调度该 MBMS第一预定 时间, 该第一预定时间可以是系统预先设定的时间。
用户设备在接收到 eNB 的 MBMS 业务停止调度信息后, 确定某个 MBMS业务即将停止, 但是会继续监听一段时间的 MSI。 如果用户设备需 要继续接收该 MBMS业务, 则可以触发单播承载的建立, 在单播承载建立 后,停止接收该 MBMS业务对应的点到多点业务信道 ( MTCH )。 所述触发 单播承载的建立过程包括: 所属用户设备的接入层向所述用户设备高层发 送 MBMS业务不能继续接收的指示, 所述用户设备高层向应用服务器发送 MBMS业务不能继续接收的指示, 所属应用服务器向用户设备发送单薄承 载建立的触发请求, 所属用户设备根据所述触发请求触发单播承载的建立。
上述保持业务连续性的方法实施例, eNB接收 MCE发送的 MBMS业 务停止调度通知, eNB发送向用户设备发送 MBMS业务停止调度信息, 继 续调度该 MBMS业务。 通过这样的方式, 使得 MCE确定停止某 MBMS业 务调度, 而需要继续接收该 MBMS业务的用户设备在建立单播承载过程中 也能继续接收该业务, 有效减少因业务停止调度, 用户设备需要继续接收 该业务而建立单播承载的过程中业务中断时间, 给用户更好的使用体验。
请参阅图 2 ,图 2是本发明实施例提供的第二种保持业务连续性的方法 的流程图, 本实施例以用户设备的角度来进行描述, 本实施例的保持业务 连续性的方法包括:
S201 : 用户设备从基站接收 MBMS业务停止调度信息, 确定基站即将 停止调度该 MBMS业务;
MCE确定要停止某个 MBMS业务的调度时, 向 eNB发送停止调度通 知, eNB通知用户设备停止调度的 MBMS业务相关信息, 告知用户设备即 将停止调度该 MBMS业务。。
用户设备在接收到 eNB 的 MBMS 业务停止调度的信息后, 确定该 MBMS业务即将停止调度。 其中, 用户设备可以通过接收点到多点控制信 道消息, 才艮据该消息中不携带某个 MBMS 业务的配置信息确定该 MBMS 业务即将停止调度。 或者点到多点控制信道消息仍然携带某个 MBMS业务 的配置信息, 但根据 MBMS业务停止调度信息携带的即将停止指示判断该 MBMS业务即将停止调度。
S202: 用户设备继续监听该 MBMS业务的调度信息;
用户设备在接收到 MBMS 业务停止调度信息后, 继续监听该 MBMS 业务的调度信息, 所述 MBMS业务的调度信息具体可以是 MBMS传输信道 调度信息 (MSI ) , 用户设备 MSI中指示的所述 MBMS业务的发送位置继 续接收所述 MBMS业务。
可选的, MBMS业务停止调度信息中携带所述 MBMS业务即将停止调 度指示, 用于指示用户设备所述 MBMS业务即将停止调度, 用户设备根据 所述 MBMS业务即将停止调度指示, 继续监听该 MBMS业务的调度信息, 直到收到 MBMS业务停止通知。
可选的,用户设备接收 MBMS业务停止调度信息的同时或之后,从 eNB 接收该 MBMS业务延迟停止指示, 根据该 MBMS业务延迟停止指示, 继 续监听该 MBMS业务的调度信息。
其中, 用户设备可以通过点到多点控制信道、 寻呼控制信道、 MBMS 传输信道调度信息中的任何一种接收上述 MBMS业务延迟停止指示或者所 述 MBMS业务即将停止调度指示。 具体而言, 如果通过点到多点控制信道 信道接收 MBMS业务延迟停止指示或者所述 MBMS业务即将停止调度指 示, 可以在通过承载在点到多点控制信道信道上的计数请求消息接收, 例 如通过在计数请求中携带 MBMS业务延迟停止指示或者所述 MBMS业务 即将停止调度指示; 如果通过 MBMS传输信道调度信息接收 MBMS业务 延迟停止指示, 可以通过 MBMS传输信道调度信息消息中的 MBMS业务 信道停止位置指示 (MTCH stop )字段的特殊值来接收 MBMS业务延迟停 止指示或者所述 MBMS业务即将停止调度指示。
S203 : 根据该 MBMS业务的调度信息, 接收该 MBMS业务; 用户设备根据该 MBMS业务的调度信息, 接收该 MBMS业务。 具体 的所述 MBMS业务的调度信息为 MBMS 传输信道调度信息( MSI ), 根据 该 MBMS业务的调度信息包括, 根据 MSI中指示的所述 MBMS业务的调 度位置, 接收所述 MBMS业务。
如果用户设备需要继续接收该 MBMS业务, 触发单播承载的建立, 在 单播承载建立过程中, 用户设备继续监听该 MBMS业务的调度信息。 在单 播承载建立完成后, 停止接收该 MBMS业务对应的点到多点业务信道, 通 过单播承载继续接收该 MBMS业务。 所述触发单播承载的建立过程包括: 所属用户设备的接入层向所述用户设备高层发送 MBMS业务不能继续接收 的指示, 所述用户设备高层向应用服务器发送 MBMS业务不能继续接收的 指示, 所属应用服务器向用户设备发送单薄承载建立的触发请求, 所属用 户设备根据所述触发请求触发单播承载的建立
当然, 如果 MBMS业务的调度信息中不再包含该 MBMS业务配置信 息, 则停止该 MBMS业务的接收。 或者收到所述接收 MBMS业务停止调 度信息之后经过第一预定时间后停止该 MBMS业务的接收。 请参阅图 3 , 图 3是本发明实施例提供的第三种保持业务连续性的方法的流程图, 本实 施例从 MCE的角度来进行描述, 本实施例的保持业务连续性的方法包括:
S301 : 多小区 /多播协作实体确定需要关闭的 MBMS业务;
MCE首先触发 eNB统计接收某个 MBMS业务的用户设备, eNB统计 响应确定该 MBMS业务的用户设备的数量, 在接收该 MBMS业务的用户 设备少于预定门限时, MCE确定停止该 MBMS业务的 MBSFN传输方式。
或者 MCE接收组通讯服务器发送的 MBMS业务停止的通知, 根据所 述 MBMS业务停止的通知确定停止该 MBMS业务的 MBSFN传输方式。
S302: 向基站发送 MBMS业务停止调度通知, 该 MBMS业务停止调 度通知告知基站该 MBMS业务满足预定条件时停止调度, 指示基站继续调 度该 MBMS业务;
MCE向 eNB发送 MBMS业务停止调度通知,该 MBMS业务停止调度 通知告知基站该 MBMS业务满足预定条件时停止调度,指示 eNB继续调度 该 MBMS业务。 这个预定条件可以是预定时间或者预定时间点, 当然也可 以是别的条件。
其中, MCE可以通过 MBMS调度信息更新 eNB的配置信息, 更新后 的配置信息中不再携带需要关闭的 MBMS业务的配置信息, 以作为向 eNB 发送的 MBMS业务停止调度通知。
MCE通知 eNB停止对接收用户设备少于预定门限的 MBMS业务的调 度, 比如停止对业务 1的调度。
该 MBMS业务停止调度通知还可以携带延迟停止指示,以指示 eNB延 迟停止调度该 MBMS业务。 更进一步地, MBMS业务停止调度通知还可以 包括延迟停止时间长度信息或者停止时间戳信息, 用于指定 eNB延迟指定 时间后停止调度该 MBMS业务。
比如 MCE决定停止对业务 1的调度, 则向 eNB发送业务 1停止调度 通知, 该通知可以用于指示业务 1 即将停止调度。 更进一步的, 该通知还 可以携带延迟停止指示, 以指示 eNB延迟停止调度业务 1 , eNB根据所述 MBMS业务停止调度指示继续调度所述业务一段时间后停止对所述业务的 调度。 并可以进一步指定延迟停止的时间, 用以指示停止调度时间相对于 收到所述停止调度第一通知的相对时间, 如 10分钟、 5分钟、 两个修改周 期或者别的时间信息, 也可以是指定时间戳信息, 如 12点 30分、 12点 40 分这样的具体时间戳信息。
当然, MCE也可以在发送 MBMS业务停止调度通知的同时或之后, 再发送一个延迟停止指示, 以指示 eNB延迟停止调度该 MBMS业务。
另一种方式是, MCE先向 eNB发送一个业务 1停止调度第一通知, 该 第一通知指示业务 1 即将停止调度, 然后发送一个业务 1停止调度第二通 知, 该第二通知直接指示 eNB马上停止调度业务 1。
可选的所述 MBMS业务停止调度第一通知通过 MBMS调度信息消息 携带, 当所述 MBMS调度信息不再携带所述 MBMS业务时表示要停止所 述 MBMS业务的调度。
请参阅图 4,图 4是本发明实施例提供的第四种保持业务连续性的方法 的流程图, 本实施例以组通讯服务器的角度来进行描述, 本实施例的保持 业务连续性的方法包括:
S401 :组通讯服务器接收用户设备上报的通过 MBSFN接收组业务的信 息;
组通讯中, 在 MBSFN区域组业务的数据承载在 MBMS业务上, 组通 讯服务器用来管理组内用户设备, 用户设备接收组业务数据之前, 需要先 向组通讯服务器进行注册。
用户设备如果通过 MBSFN方式接收组通讯服务器进行通讯,可以向组 通讯服务器上报自己正在通过 MBSFN方式接收组业务的信息,这个组业务 的信息包括组业务的 MBSFN区域标示、组业务所在的小区标示中的至少一 种。
S402: 组通讯服务器从多小区 /多播协作实体接收用于接收组业务的该 MBSFN传输停止通知;
MCE决定停止某个 MBMS业务的调度, 则 MCE通知 eNB停止对该 MBMS业务调度之前, 先通知组通讯服务器。 MCE可以向组通信服务器上 艮自己即将停止的业务信息, 比如 MBSFN区域标示、 MBMS服务器标识 等。
组通讯服务器从 MCE接收某个 MBSFN传输即将停止通知。
S403 : 组通讯服务器通知用户设备建立单播承载, 以便用户设备在用 于接收组业务的 MBSFN停止后, 通过单播承载继续接收该组业务;
组通讯服务器接收到某个 MBSFN传输即将停止通知后,通知用户设备 建立单播承载, 以便在用于接收组业务的 MBSFN停止后,通过单播承载替 代 MBSFN继续接收该组业务。作为一种优选,可以只通知需要继续接收该 组业务的用户设备建立单播承载。
需要继续接收该组业务的用户设备, 根据组通讯服务器的通知, 触发 建立单播承载, 以在该 MBSFN传输停止后,在单播承载上继续接收该组业 务。 在用户设备建立单播承载后, 组通讯服务器通知 MCE停止该 MBSFN 传输。
具体的, 如果用户设备通过该 MBMS业务接收组通讯数据, 则用户设 备的接入层确定某个 MBMS业务即将停止, 向用户设备高层发送指示, 所 述用户设备高层向组通讯服务器上报该 MBMS业务对应的组业务无法继续 采用 MBSFN方式接收,组通讯服务器收到该请求后,如果判断该组业务需 要继续发送给所述用户设备, 则触发所述用户设备建立单播承载以继续接 收所述组业务。 其中所述单播承载为用户设备和基站之间的一个用于传输 MBMS业务的专用无线 载。
其中用户设备高层向组通讯服务器上报该 MBMS业务对应的组业务无 法继续采用 MBSFN方式接收之前, 需要和 eNB建立连接, 为了避免艮多 用户设备同时发起连接建立过程造成网络拥塞, 用户设备在接收到 eNB的 MBMS业务停止调度信息后可以执行一个随即退避, 避免多个用户设备同 时触发单播连接建立过程, 具体的, 用户设备生成一个随机因子, 和一个 预定门限比较, 根据比较结果决定触发单播立过程的延迟。 比如预定随机 因子为 0.5 , 用户生成随机数为 0.6, 0.6>0.5,则用户延迟 10ms触发连接建 立。
通过本实施例的详细描述, 可以理解, 本实施例中保持业务连续性的 方法, MCE决定停止某个需要停止的 MBSFN传输时, 在通知 eNB之前, 先通知管理组内用户设备的组通讯服务器, 组通讯服务器通知用户设备建 立单播承载,在用户设备建立单播承载后再通知 MCE停止该 MBSFN传输。 通过这样的方式, MCE决定停止某个 MBSFN传输时, 需要继续接收通过 该 MBSFN传输的组业务的用户设备根据组通讯服务器的通知先建立单播 承载, 避免该组业务中断, 给用户更好的使用体验。
请参阅图 5 ,图 5是本发明实施例提供的第五种保持业务连续性的方法 的流程图, 本实施例以 MCE的角度来进行描述, 本实施例的保持业务连续 性的方法包括:
S501 : 多小区 /多播协作实体确定需要停止的 MBSFN传输;
MCE首先触发 eNB统计接收某个 MBMS业务的用户设备, 根据 eNB 统计响应确定该 MBMS业务的用户设备的数量, 在接收该 MBMS业务的 用户设备少于预定门限时, 确定需要停止该 MBMS业务的 MBSFN传输方 式。
S502: 通知组通讯服务器该 MBSFN传输停止;
MCE决定停止某个 MBMS业务的 MBSFN传输时, 则 MCE通知 eNB 停止对该 MBMS业务调度之前, 先通知组通讯服务器。 MCE可以向组通 信服务器上报自己即将停止的业务信息, 比如 MBSFN 区域标示、 MBMS 服务器标识等。 以使组通讯服务器通知用户设备建立单播承载, 以便用户 设备再 MBSFN传输停止后, 通过单播承载代替 MBSFN继续接收组业务。
通知组通讯服务器该 MBSFN传输即将停止之后, 经过预定一段时间 后, 向 eNB发送 MBMS业务停止调度信息, 以便 eNB停止对所述 MBMS 业务的调度。
组通讯服务器用于管理其组内用户设备,其在接收到 MBSFN传输即将 停止通知后, 可以通知用户设备建立单播承载, 以便在接收组业务的 MBSFN传输停止后, 也能继续通过单播承载接收组业务。 请参阅图 6,图 6是本发明实施例提供的第六种保持业务连续性的方法 的流程图, 本实施例以用户设备的角度来进行描述, 本实施例的保持业务 连续性的方法包括:
S601 : 用户设备向组通讯服务器上报通过 MBSFN接收组业务的信息; 组通讯中, 在 MBSFN区域组业务的数据承载在 MBMS业务上, 组通 讯服务器用来管理组内用户设备, 用户设备在接收组业务数据之前, 需要 先向组通讯服务器进行注册。
用户设备如果通过 MBSFN方式接收组业务,可以向组通讯服务器上 4艮 自己正在通过 MBSFN方式接收组业务的信息,这个组业务的信息包括组业 务的 MBSFN区域标示、 组业务所在的小区标示中的至少一种。
S602: 根据组通讯服务器的单播承载建立通知, 建立单播承载, 同时 继续监听承载该组业务的调度信息;
MCE决定停止某个 MBMS业务的调度, 则 MCE通知 eNB停止对该 MBMS业务调度之前, 先通知组通讯服务器。 MCE可以向组通信服务器上 艮自己即将停止的业务信息, 比如 MBSFN区域标示、 MBMS服务器标识 等。
组通讯服务器从 MCE接收某个 MBSFN传输即将停止通知。
组通讯服务器接收到某个 MBSFN传输即将停止通知后,通知用户设备 建立单播承载, 以便通过单播承载继续接收该组业务。 作为一种优选, 可 以只通知需要继续接收该组业务的用户设备建立单播承载。
需要继续接收该组业务的用户设备, 根据组通讯服务器的通知, 触发 建立单播承载, 以在该 MBSFN传输停止后,在单播承载上继续接收该组业 务。 在用户设备建立单播承载后, 组通讯服务器通知 MCE停止该 MBSFN 传输。
在建立单播承载过程中, 用户设备继续监听承载该组业务的调度信息, 在单播承载建立完成后, 用户设备停止监听承载组业务的调度信息, 通过 单播承载来继续接收组业务。
请参阅图 7, 图 7是本发明实施例提供的第一种基站的结构示意图, 本 实施例的基站 100包括接收模块 11和调度模块 12, 其中:
接收模块 11用于接收 MCE发送的 MBMS业务停止调度第一通知; MCE首先触发 eNB统计接收某个 MBMS业务的用户设备, eNB统计响应 确定该 MBMS业务的用户设备的数量, 在接收该 MBMS业务的用户设备少 于预定门限时, MCE确定停止该 MBMS业务的调度。 MCE通知 eNB停止对 接收用户设备少于预定门限的 MBMS业务的调度, 比如停止对业务 1的调 度。
eNB通过接收模块 11接收 MCE发送的 MBMS业务停止调度第一通知。 该 MBMS业务停止调度第一通知是 MCE确定关闭该 MBMS业务时向基站 发送的通知, 该 MBMS 业务停止调度第一通知可以用于指示某个 MBMS 业务满足预定条件时停止调度。 这个预定条件, 可以是一定的时间后、 或 固定的时间点等等。 当然也可以是其他的指定条件。
可选的, 该 MBMS业务停止调度第一通知还可以携带延迟停止指示, 以指示 eNB延迟停止调度该 MBMS业务。 更进一步地, MBMS业务停止 调度第一通知还可以包括延迟停止时间长度信息或者停止时间戳信息, 用 于指定 eNB延迟指定时间后停止调度该 MBMS业务。
比如 MCE决定停止对业务 1的调度, 则向 eNB发送业务 1停止调度第一 通知, 该通知可以用于指示业务 1即将停止调度或者第一通知可以携带延迟 停止指示, 以指示 eNB延迟停止调度业务 1 , eNB根据所述 MBMS业务延迟 停止指示继续调度所述业务一段时间后停止对所述业务的调度。 并可以进 一步指定延迟停止的时间, 用以指示停止调度时间相对于收到所述停止调 度第一通知的相对时间, 如 10分钟、 5分钟、 两个修改周期或者别的时间信 息, 也可以是指定时间戳信息, 如 12点 30分、 12点 40分这样的具体时间戳 信息。
可选的所述 MBMS业务停止调度第一通知通过 MBMS调度信息消息携 带, 当所述 MBMS调度信息不再携带所述 MBMS业务的配置信息时, 表示 要停止所述 MBMS业务的调度。
调度模块 12用于在接收模块 11接收到 MBMS业务停止调度第一通知 后, 向用户设备发送该 MBMS 业务停止调度信息, 并继续调度该 MBMS 业务直到满足预定条件再停止调度该 MBMS业务。
eNB在接收到 MCE的 MBMS业务停止调度第一通知后, 通过调度模 块 12向用户设备发送所述 MBMS业务停止调度信息。 其中, 调度模块 12 可以通过点到多点控制信道消息中不携带某个 MBMS业务的配置信息作为向用户设备发送的某个 MBMS业务停止调度信 息。
可选的, 所述 MBMS业务停止调度信息可以携带延迟停止指示, 以告 知用户设备会延迟停止调度该 MBMS业务。
可选的, 调度模块 12通知用户设备业务停止调度信息的同时或之后, 还发送延迟停止指示, 以告知用户设备会延迟停止调度该 MBMS。
可选的, 所述 MBMS业务停止调度信息可以携带所述 MBMS业务即 将停止调度指示, 以告知所述用户设备即将停止调度所述 MBMS业务。
其中, 上述 MBMS业务延迟停止指示或者所述 MBMS业务即将停止 调度指示可以通过点到多点控制信道、 寻呼控制信道、 MBMS传输信道调 度信息中的任何一种发送给用户设备。 具体而言, 如果通过点到多点控制 信道信道发送 MBMS业务延迟停止指示, 可以在通过承载在点到多点控制 信道信道上的计数请求消息发送, 例如通过在计数请求中增加 MBMS业务 延迟停止指示; 如果通过 MBMS传输信道调度信息发送 MBMS业务延迟 停止指示, 可以通过 MBMS传输信道调度信息消息中的 MBMS业务信道 停止位置指示 (MTCH stop )字段的特殊值来表示 MBMS业务延迟停止指 示。
eNB通过调度模块 12继续调度该 MBMS业务, 以使得需要继续接收 该 MBMS业务的用户设备触发建立单播承载,在单播承载过程中该 MBMS 业务的不会发生中断或中断时间减少。
其中, 调度模块 12在满足以上条件之一时, 停止调度该 MBMS业务: 接收模块 11接收到 MCE发生的 MBMS业务停止调度第二通知,该 MBMS 业务停止调度第二通知指示该 MBMS业务停止调度; 或接收模块 11收到 该 MBMS业务停止调度第一通知之后, 达到该 MBMS业务停止调度第一 通知指示的时间点; 或接收模块 11收到该 MBMS业务停止调度第一通知 之后经过第一预定时间; 或收到业务停止调度第一通知之后, 达到第二预 定时间点。
也就是说, MCE可以发送 MBMS业务停止调度第一通知, 通知某个 业务即将停止调度, 然后经过预定时间后, MCE再发送该 MBMS业务停 止调度第二通知, 该通知直接指示 eNB停止调度该 MBMS业务。
MCE也可以直接在 MBMS业务停止调度第一通知中携带延迟停止指 示, 并且停止调度时间点为预定义的时间点, 比如收到所述 MBMS业务停 止调度第一通知之后下下个修改周期的起始时间停止, 或者可以一进一步 第一通知中携带的延迟停止指示具体的延迟时间, eNB接收到 MCE 的该 MBMS业务停止调度第一通知, 延迟一段时间停止调度该业务。 或者进一 步达到该第一通知指示的时间点就停止调度该 MBMS业务。
还有就是 MCE可以发送的 MBMS业务停止调度第一通知, 只是通知 某个 MBMS业务停止调度 (即该第一通知就是普通的 MBMS业务停止调 度通知 ) , eNB在接收到该通知后, 自行继续调度该 MBMS第一预定时间, 该第一预定时间可以是系统预先设定的时间。
用户设备在接收到 eNB 的 MBMS 业务停止调度信息后, 确定某个 MBMS业务即将停止, 但是会继续监听一段时间的 MSI。 如果用户设备需 要继续接收该 MBMS业务, 则可以触发单播承载的建立, 在单播承载建立 后, 停止接收该 MBMS业务对应的点到多点业务信道 ( MTCH )。
本实施例提供的基站, 能够实现图 1 所示实施例中的各个步骤, 本实 施例中基站的各个功能模块的划分只是示意性的, 在能够实现本发明目的 的前提下, 基站功能模块的划分并不限于以上方式, 可以是其他任何可能 实现的方式。 例如多个单元或组件可以结合或者可以集成到另一个系统, 或一些特征可以忽略, 或不执行。
请参阅图 8,图 8是本发明实施例提供的第一种用户设备的结构示意图, 本实施例的用户设备 110包括第一接收模块 21、监听模块 22以及第二接收 模块 23 , 其中:
第一接收模块 21用于从基站接收 MBMS业务停止调度信息, 确定基站 即将停止调度该 MBMS业务;
MCE确定要停止某个 MBMS业务的调度时, 向 eNB发送停止调度通知, eNB通知用户设备停止调度的 MBMS业务相关信息,告知用户设备即将停止 调度该 MBMS业务。 即基站在满足预定条件时会停止调度该 MBMS业务。 这个预定条件可以是预定时间或预定时间点或再次收到停止调度通知等 等, 当然也可以是其他条件。 用户设备通过第一接收模块 21接收到 eNB的 MBMS业务停止调度的信 息后, 确定该 MBMS业务即将停止调度。 其中, 第一接收模块 21可以通过 接收点到多点控制信道消息, 根据该消息中不携带某个 MBMS业务的配置 信息确定该 MBMS业务即将停止调度。 或者点到多点控制信道消息仍然携 带某个 MBMS业务的配置信息, 但根据 MBMS业务停止调度信息携带的即 将停止指示判断该 MBMS业务即将停止调度。
监听模块 22用于在第一接收模块 21确定该 MBMS业务在满足预定条件 时停止调度后, 继续监听该 MBMS业务的调度信息;
监听模块 22在第一接收模块 21接收到 MBMS业务停止调度信息后, 继 续监听该 MBMS业务的调度信息, 所述 MBMS业务的调度信息具体可以是 MBMS传输信道调度信息 (MSI ) , 用户设备 MSI中指示的所述 MBMS业务 的发送位置继续接收所述 MBMS业务。
可选的, MBMS业务停止调度信息中携带延迟停止指示, 用于指示用 户设备该 MBMS业务延迟停止调度, 监听模块 22根据该延迟停止指示, 继续监听该 MBMS业务的调度信息。
可选的, 所述 MBMS业务停止调度信息携带 MBMS业务即将停止调 度指示, 用于指示用户设备所述 MBMS即将停止调度, 所述监听模块用于 根据 MBMS 业务即将停止调度指示, 确定所述基站即将停止调度所述 MBMS业务。
可选的, 第一接收模块 21接收 MBMS业务停止调度信息的同时或之 后, 从 eNB接收该 MBMS业务延迟停止指示, 监听模块 22根据该 MBMS 业务延迟停止指示, 继续监听该 MBMS业务的调度信息。
其中, 第一接收模块 21可以通过点到多点控制信道、 寻呼控制信道、 MBMS传输信道调度信息中的任何一种接收上述 MBMS业务延迟停止指示 或者 MBMS业务即将停止调度指示。 具体而言, 如果通过点到多点控制信 道信道接收 MBMS业务延迟停止指示, 可以在通过承载在点到多点控制信 道信道上的计数请求消息接收, 例如通过在计数请求中携带 MBMS业务延 迟停止指示; 如果通过 MBMS传输信道调度信息接收 MBMS业务延迟停止 指示, 可以通过 MBMS传输信道调度信息消息中的 MBMS业务信道停止位 置指示 (MTCH stop )字段的特殊值来接收 MBMS业务延迟停止指示。 第二接收模块 23用于根据监听模块 22监听到的该 MBMS业务的调度 信息, 接收该 MBMS业务。
第二接收模块 23根据监听模块 22监听到的该 MBMS业务的调度信息, 接收该 MBMS业务。具体的所述 MBMS业务的调度信息为 MBMS 传输信 道调度信息 (MSI ), 根据该 MBMS业务的调度信息包括, 根据 MSI中指 示的所述 MBMS业务的调度位置, 接收所述 MBMS业务。
如果用户设备需要继续接收该 MBMS业务, 触发单播承载的建立, 在 单播承载建立过程中, 监听模块 22继续监听该 MBMS业务的调度信息。 在单播承载建立完成后, 第二接收模块 23停止接收该 MBMS业务对应的 点到多点业务信道, 通过单播承载继续接收该 MBMS业务。
当然, 如果 MBMB业务的调度信息中不再包含该 MBMS业务配置信 息, 则第二接收模块 23停止该 MBMS业务的接收。
所述用户设备还包括单播建立模块, 所述单播建立模块用于在所述用 户设备确定所述基站即将停止调度所述 MBMS业务之后, 触发单播承载的 建立;
所述第二接收模块在所述单播承载建立完成后, 停止所述 MBMS业务 对应的点到多点业务信道接收所述 MBMS业务。
本实施例所述的用户设备, 能够实现图 2所示实施例的各个步骤, 本 实施例中用户设备的各个功能模块的划分只是示意性的, 在能够实现本发 明目的的前提下, 用户设备功能模块的划分并不限于以上方式, 可以是其 他任何可能实现的方式。 例如多个单元或组件可以结合或者可以集成到另 一个系统, 或一些特征可以忽略, 或不执行。
请参阅图 9 , 图 9是本发明实施例提供的第一种多小区 /多播协作实体 的结构示意图,本实施例的多小区 /多播协作实体 120包括确定模块 31和调 度模块 32 , 其中:
确定模块 31用于确定需要关闭的 MBMS业务;
MCE首先触发 eNB统计接收某个 MBMS业务的用户设备, eNB统计响应 确定该 MBMS业务的用户设备的数量, 在接收该 MBMS业务的用户设备少 于预定门限时, MCE通过确定模块 31确定停止该 MBMS业务的 MBSFN传输 方式。 调度模块 32用于在确定模块 31确定需要关闭该 MBMS业务时, 向基 站发送该 MBMS业务停止调度通知, 该 MBMS业务停止调度通知告知基 站该 MBMS 业务满足预定条件时停止调度, 指示基站继续调度该 MBMS 业务。
在确定模块 31确定需要关闭某个 MBMS业务后, MCE通过调度模块 32向 eNB发送 MBMS业务停止调度通知, 该 MBMS业务停止调度通知告 知基站该 MBMS 业务满足预定条件时停止调度, 指示 eNB 继续调度该 MBMS业务。
其中, 调度模块 32可以通过 MBMS调度信息更新 eNB的配置信息, 更新后的配置信息中不再携带需要关闭的 MBMS业务的配置信息, 以作为 向 eNB发送的 MBMS业务停止调度通知。
调度模块 32通知 eNB停止对接收用户设备少于预定门限的 MBMS业 务的调度, 比如停止对业务 1的调度。
该 MBMS业务停止调度通知还可以携带延迟停止指示,以指示 eNB延 迟停止调度该 MBMS业务。 更进一步地, MBMS业务停止调度通知还可以 包括延迟停止时间长度信息或者停止时间戳信息, 用于指定 eNB延迟指定 时间后停止调度该 MBMS业务。
比如 MCE决定停止对业务 1的调度, 则通过调度模块 32向 eNB发送 业务 1停止调度通知, 该通知可以用于指示业务 1 即将停止调度。 更进一 步的, 该通知还可以携带延迟停止指示, 以指示 eNB延迟停止调度业务 1 , eNB根据所述 MBMS业务延迟停止指示继续调度所述业务一段时间后停止 对所述业务的调度。 并可以进一步指定延迟停止的时间, 用以指示停止调 度时间相对于收到所述停止调度第一通知的相对时间, 如 10分钟、 5分钟、 两个修改周期或者别的时间信息, 也可以是指定时间戳信息, 如 12 点 30 分、 12点 40分这样的具体时间戳信息。
当然, 调度模块 32也可以在发送 MBMS业务停止调度通知的同时或 之后,再发送一个延迟停止指示,以指示 eNB延迟停止调度该 MBMS业务。
另一种方式是, MCE通过调度模块 32先向 eNB发送一个业务 1停止 调度第一通知, 该第一通知指示业务 1即将停止调度, 然后发送一个业务 1 停止调度第二通知, 该第二通知直接指示 eNB马上停止调度业务 1。 可选的所述 MBMS业务停止调度第一通知通过 MBMS调度信息消息 携带, 当所述 MBMS调度信息不再携带所述 MBMS业务时表示要停止所 述 MBMS业务的调度。
本实施例所述的多小区 /多播协作实体, 能够实现图 3所示实施例的各 个步骤, 本实施例中多小区 /多播协作实体的各个功能模块的划分只是示意 性的, 在能够实现本发明目的的前提下, 多小区 /多播协作实体功能模块的 划分并不限于以上方式, 可以是其他任何可能实现的方式。 例如多个单元 或组件可以结合或者可以集成到另一个系统, 或一些特征可以忽略, 或不 执行。
请参阅图 10, 图 10是本发明实施例提供的第二种基站的结构示意图, 本实施例的基站 130包括处理器 41、 存储器 42、 接收器 43、 发送器 44以 及总线系统 45 , 其中:
处理器 41控制基站 130的操作, 处理器 41还可以称为 CPU ( Central Processing Unit, 中央处理单元)。 处理器 41可能是一种集成电路芯片, 具 有信号的处理能力。处理器 41还可以是通用处理器、数字信号处理器( DSP, Digital Signal Processing ). 专用集成电路 ( ASIC, Application Specific Integrated Circuit )、 现场可编程门阵列 ( FPGA, Field - Programmable Gate Array )或者其他可编程逻辑器件、 分立门或者晶体管逻辑器件、 分立硬件 组件。 通用处理器可以是微处理器或者该处理器也可以是任何常规的处理 器等。
存储器 42可以包括只读存储器和随机存取存储器, 并向处理器 41提 供指令和数据。 存储器 42的一部分还可以包括非易失性随机存取存储器 ( NVRAM )。
基站 130的各个组件通过总线系统 45耦合在一起, 其中总线系统 45 除包括数据总线之外, 还可以包括电源总线、 控制总线和状态信号总线等。 该总线系统可以是 ISA ( Industry Standard Architecture , 工业标准体系结构) 总线、 PCI ( Peripheral Component Interconnect, 夕卜部设备互连 )总线或 EISA ( Extended Industry Standard Architecture ,扩展工业标准体系结构)总线等。 所述总线可以是一条或多条物理线路, 当是多条物理线路时可以分为地址 总线、 数据总线、 控制总线等。 在本发明的其它一些实施例中, 处理器 41、 存储器 42以及接收器 43、 发送器 44也可以通过通信线路直接连接。 但是 为了清楚说明起见, 在图中将各种总线都标为总线系统 45。
存储器 42存储了如下的元素, 可执行模块或者数据结构, 或者它们的 子集, 或者它们的扩展集:
操作指令: 包括各种操作指令, 用于实现各种操作。
操作系统: 包括各种系统程序, 用于实现各种基础业务以及处理基于 硬件的任务。
在本发明实施例中,处理器 41通过调用存储器 42存储的操作指令(该 操作指令可存储在操作系统中), 执行如下操作:
处理器 41用于控制接收器 43接收 MCE发送的 MBMS业务停止调度第一 通知, 在接收 MBMS业务停止调度第一通知后, MBMS业务停止调度第一 通知是 MCE确定关闭所述 MBMS业务时向基站发送的通知, 控制发送器 44 向用户设备发送 MBMS业务停止调度信息, 处理器 41继续调度该 MBMS业 务直到满足预定条件再停止调度该 MBMS业务。
存储器 42用于存储该 MBMS数据。
MCE首先触发 eNB统计接收某个 MBMS业务的用户设备, eNB统计 响应确定该 MBMS业务的用户设备的数量, 在接收该 MBMS业务的用户 设备少于预定门限时, MCE确定停止该 MBMS业务的调度。 MCE通知 eNB 停止对接收用户设备少于预定门限的 MBMS业务的调度, 比如停止对业务 1的调度。
处理器 41控制接收器 43接收 MCE发送的 MBMS业务停止调度第一 通知。 该 MBMS业务停止调度第一通知可以用于指示某个 MBMS业务满 足预定条件时停止调度。 这个预定条件, 可以是一定的时间后、 或固定的 时间点等等。 当然也可以是其他的指定条件。
可选的, 该 MBMS业务停止调度第一通知还可以携带延迟停止指示, 以指示 eNB延迟停止调度该 MBMS业务。 更进一步地, MBMS业务停止 调度第一通知还可以包括延迟停止时间长度信息或者停止时间戳信息, 用 于指定 eNB延迟指定时间后停止调度该 MBMS业务。
比如 MCE决定停止对业务 1的调度, 则向 eNB发送业务 1停止调度 第一通知, 该通知可以用于指示业务 1 即将停止调度, 或者第一通知可以 携带延迟停止指示,以指示 eNB延迟停止调度业务 1 , eNB根据所述 MBMS 业务延迟停止指示继续调度所述业务一段时间后停止对所述业务的调度。 并可以进一步指定延迟停止的时间, 用以指示停止调度时间相对于收到所 述停止调度第一通知的相对时间, 如 10分钟、 5分钟、 两个修改周期或者 别的时间信息, 也可以是指定时间戳信息, 如 12点 30分、 12点 40分这样 的具体时间戳信息。
可选的所述 MBMS业务停止调度第一通知通过 MBMS调度信息消息 携带, 当所述 MBMS调度信息不再携带所述 MBMS业务的配置信息时, 表示要停止所述 MBMS业务的调度。
处理器 41控制接收器 43接收到 MCE的 MBMS业务停止调度第一通 知后, 进一步控制发送器 44向用户设备发送某个 MBMS业务停止调度信 息。
其中, 处理器 41可以控制发送器 44通过点到多点控制信道消息中不 携带 MBMS业务的配置信息作为向用户设备发送的某个 MBMS业务停止 调度信息。
可选的, 所述 MBMS业务停止调度信息可以携带延迟停止指示, 以告 知用户设备会延迟停止调度该 MBMS业务。
可选的, 处理器 41控制发送器 44通知用户设备业务停止调度信息的 同时或之后, 还发送延迟停止指示, 以告知用户设备会延迟停止调度所述 MBMSo
其中, 上述 MBMS业务延迟停止指示可以通过点到多点控制信道、 寻 呼控制信道、 MBMS传输信道调度信息中的任何一种发送给用户设备。 具 体而言, 如果通过点到多点控制信道信道发送 MBMS业务延迟停止指示, 可以在通过承载在点到多点控制信道信道上的计数请求消息发送, 例如通 过在计数请求中增加 MBMS业务延迟停止指示; 如果通过 MBMS传输信 道调度信息发送 MBMS业务延迟停止指示, 可以通过 MBMS传输信道调 度信息消息中的 MBMS业务信道停止位置指示 (MTCH stop )字段的特殊 值来表示 MBMS业务延迟停止指示。
处理器 41继续调度该 MBMS业务, 以使得需要继续接收该 MBMS业 务的用户设备触发建立单播承载, 在单播承载过程中该 MBMS业务的不会 发生中断或中断时间减少。
其中, 处理器 41在满足以下条件之一时, 停止调度该 MBMS业务: 当接收器 43接收到 MCE发生的 MBMS业务停止调度第二通知,该 MBMS 业务停止调度第二通知指示该 MBMS业务停止调度; 或接收器 43收到该 MBMS业务停止调度第一通知之后,达到该 MBMS业务停止调度第一通知 指示的时间点; 或接收器 41收到该 MBMS业务停止调度第一通知之后经 过第一预定时间; 或收到业务停止调度第一通知之后, 达到第二预定时间 点。
用户设备在接收到 eNB 的 MBMS 业务停止调度信息后, 确定某个 MBMS业务即将停止, 但是会继续监听一段时间的 MSI。 如果用户设备需 要继续接收该 MBMS业务, 则可以触发单播承载的建立, 在单播承载建立 后, 停止接收该 MBMS业务对应的点到多点业务信道。
上述本发明实施例揭示的方法可以应用于处理器 41中, 或者由处理器 41实现。在实现过程中, 上述方法的各步骤可以通过处理器 41中的硬件的 集成逻辑电路或者软件形式的指令完成。 可以实现或者执行本发明实施例 中的公开的各方法、 步骤及逻辑框图。 结合本发明实施例所公开的方法的 步骤可以直接体现为硬件译码处理器执行完成, 或者用译码处理器中的硬 件及软件模块组合执行完成。 软件模块可以位于随机存储器, 闪存、 只读 存储器, 可编程只读存储器或者电可擦写可编程存储器、 寄存器等本领域 成熟的存储介质中。 该存储介质位于存储器 42 , 处理器 41读取存储器 42 中的信息, 结合其硬件完成上述方法的步骤。
请参阅图 11 , 图 11是本发明实施例提供的第二种用户设备的结构示意 图, 本实施例的用户设备 140包括处理器 51、 存储器 52、 接收器 53以及 总线系统 54, 其中:
处理器 51控制用户设备 140的操作,处理器 51还可以称为 CPU( Central Processing Unit, 中央处理单元)。 处理器 51可能是一种集成电路芯片, 具 有信号的处理能力。处理器 51还可以是通用处理器、数字信号处理器(DSP, Digital Signal Processing ). 专用集成电路 ( ASIC, Application Specific Integrated Circuit )、 现场可编程门阵列 ( FPGA, Field - Programmable Gate Array )或者其他可编程逻辑器件、 分立门或者晶体管逻辑器件、 分立硬件 组件。 通用处理器可以是微处理器或者该处理器也可以是任何常规的处理 器等。
存储器 52可以包括只读存储器和随机存取存储器, 并向处理器 51提 供指令和数据。 存储器 52的一部分还可以包括非易失性随机存取存储器 ( NVRAM )。
用户设备 140的各个组件通过总线系统 55耦合在一起, 其中总线系统 55除包括数据总线之外, 还可以包括电源总线、 控制总线和状态信号总线 等。 该总线系统可以是 ISA ( Industry Standard Architecture, 工业标准体系 结构)总线、 PCI ( Peripheral Component Interconnect, 夕卜部设备互连)总线 或 EISA ( Extended Industry Standard Architecture , 扩展工业标准体系结构) 总线等。 所述总线可以是一条或多条物理线路, 当是多条物理线路时可以 分为地址总线、 数据总线、 控制总线等。 在本发明的其它一些实施例中, 处理器 51、 存储器 52以及接收器 53也可以通过通信线路直接连接。 但是 为了清楚说明起见, 在图中将各种总线都标为总线系统 54。
存储器 52存储了如下的元素, 可执行模块或者数据结构, 或者它们的 子集, 或者它们的扩展集:
操作指令: 包括各种操作指令, 用于实现各种操作。
操作系统: 包括各种系统程序, 用于实现各种基础业务以及处理基于 硬件的任务。
在本发明实施例中,处理器 51通过调用存储器 52存储的操作指令(该 操作指令可存储在操作系统中), 执行如下操作:
处理器 51用于控制接收器 53从基站接收 MBMS业务停止调度信息, 确 定基站在满足预定条件时停止调度该 MBMS业务, 并继续监听该 MBMS业 务的调度信息, 并控制接收器 53根据处理器 51监听到的该 MBMS业务的调 度信息, 接收该 MBMS业务。
存储器 52用于存储该 MBMS业务数据。
MCE确定要停止某个 MBMS业务的调度时, 向 eNB发送停止调度通知, eNB通知用户设备停止调度的 MBMS业务相关信息,告知用户设备再满足预 定条件时会停止调度该 MBMS业务。 这个预定条件可以是预定时间或预定 时间点等等, 当然也可以是其他条件。 处理器 51控制接收器 53接收到 eNB的 MBMS业务停止调度的信息后, 确定该 MBMS业务即将停止调度。 其中, 接收器 53可以通过接收点到多 点控制信道消息, 处理器 51才艮据该消息中不携带某个 MBMS业务的配置 信息确定该 MBMS业务即将停止调度。 或者点到多点控制信道消息仍然携 带某个 MBMS业务的配置信息, 但根据 MBMS业务停止调度信息携带的 即将停止指示判断该 MBMS业务即将停止调度。
在接收器 53接收到 MBMS业务停止调度通知后, 处理器 51继续监听 该 MBMS业务的调度信息。,所述 MBMS业务的调度信息具体可以是 MBMS 传输信道调度信息 (MSI ) , 用户设备 MSI中指示的所述 MBMS业务的发 送位置继续接收所述 MBMS业务
可选的, MBMS业务停止调度信息中携带延迟停止指示, 用于指示用 户设备该 MBMS业务延迟停止调度, 处理器 51根据该延迟停止指示, 继 续监听该 MBMS业务的调度信息。
可选的, 接收器 53接收 MBMS业务停止调度信息的同时或之后, 从 eNB接收该 MBMS业务延迟停止指示, 处理器 51根据该 MBMS业务延迟 停止指示, 继续监听该 MBMS业务的调度信息。
其中, 接收器 53可以通过点到多点控制信道、 寻呼控制信道、 MBMS 传输信道调度信息中的任何一种接收上述 MBMS业务延迟停止指示。 具体 而言, 如果通过点到多点控制信道信道接收 MBMS业务延迟停止指示, 可 以在通过承载在点到多点控制信道信道上的计数请求消息接收, 例如通过 在计数请求中 MBMS业务延迟停止指示; 如果通过 MBMS传输信道调度 信息接收 MBMS业务延迟停止指示, 可以通过 MBMS传输信道调度信息 消息中的 MBMS业务信道停止位置指示 (MTCH stop )字段的特殊值来接 收 MBMS业务延迟停止指示。
处理器 51进一步控制接收器 53根据处理器 51监听到的该 MBMS业 务的调度信息, 接收该 MBMS业务。 具体的所述 MBMS业务的调度信息 为 MBMS 传输信道调度信息( MSI ),根据该 MBMS业务的调度信息包括, 根据 MSI中指示的所述 MBMS业务的调度位置, 接收所述 MBMS业务。
如果用户设备需要继续接收该 MBMS业务, 通过处理器 51触发单播 承载的建立, 在单播承载建立过程中, 处理器 51继续监听该 MBMS业务 的调度信息。 在单播承载建立完成后, 处理器 51控制接收器 53停止接收 该 MBMS业务对应的点到多点业务信道,通过单播承载继续接收该 MBMS 业务。
当然, 如果 MBMB业务的调度信息中不再包含该 MBMS业务信息, 则控制接收器 53停止该 MBMS业务的接收。
上述本发明实施例揭示的方法可以应用于处理器 51中, 或者由处理器 61实现。在实现过程中, 上述方法的各步骤可以通过处理器 51中的硬件的 集成逻辑电路或者软件形式的指令完成。 可以实现或者执行本发明实施例 中的公开的各方法、 步骤及逻辑框图。 结合本发明实施例所公开的方法的 步骤可以直接体现为硬件译码处理器执行完成, 或者用译码处理器中的硬 件及软件模块组合执行完成。 软件模块可以位于随机存储器, 闪存、 只读 存储器, 可编程只读存储器或者电可擦写可编程存储器、 寄存器等本领域 成熟的存储介质中。 该存储介质位于存储器 52 , 处理器 51读取存储器 52 中的信息, 结合其硬件完成上述方法的步骤。
请参阅图 12 , 图 12是本发明实施例提供的第二种多小区 /多播协作实 体的结构示意图, 本实施例的多小区 /多播协作实体 150包括处理器 61、 存 储器 62、 发送器 63以及总线系统 64, 其中:
处理器 61控制多小区 /多播协作实体(MCE ) 150的操作, 处理器 61 还可以称为 CPU ( Central Processing Unit, 中央处理单元)。 处理器 61可能 是一种集成电路芯片, 具有信号的处理能力。 处理器 61还可以是通用处理 器、数字信号处理器( DSP, Digital Signal Processing )、专用集成电路( ASIC, Application Specific Integrated Circuit )、 现场可编程门阵列 ( FPGA, Field - Programmable Gate Array )或者其他可编程逻辑器件、 分立门或者晶体管逻 辑器件、 分立硬件组件。 通用处理器可以是微处理器或者该处理器也可以 是任何常规的处理器等。
存储器 62可以包括只读存储器和随机存取存储器, 并向处理器 61提 供指令和数据。 存储器 62的一部分还可以包括非易失性随机存取存储器 ( NVRAM )。
MCE 150的各个组件通过总线系统 64耦合在一起, 其中总线系统 64 除包括数据总线之外, 还可以包括电源总线、 控制总线和状态信号总线等。 该总线系统可以是 ISA ( Industry Standard Architecture , 工业标准体系结构) 总线、 PCI ( Peripheral Component Interconnect, 夕卜部设备互连 )总线或 EISA ( Extended Industry Standard Architecture ,扩展工业标准体系结构)总线等。 所述总线可以是一条或多条物理线路, 当是多条物理线路时可以分为地址 总线、 数据总线、 控制总线等。 在本发明的其它一些实施例中, 处理器 61、 存储器 62以及发送器 63也可以通过通信线路直接连接。 但是为了清楚说 明起见, 在图中将各种总线都标为总线系统 64。
存储器 62存储了如下的元素, 可执行模块或者数据结构, 或者它们的 子集, 或者它们的扩展集:
操作指令: 包括各种操作指令, 用于实现各种操作。
操作系统: 包括各种系统程序, 用于实现各种基础业务以及处理基于 硬件的任务。
在本发明实施例中,处理器 61通过调用存储器 62存储的操作指令(该 操作指令可存储在操作系统中), 执行如下操作:
处理器 61用于确定需要关闭的 MBMS业务, 控制发送器 63向基站发送 MBMS业务停止调度通知, 该 MBMS业务停止调度通知告知基站该 MBMS 业务满足预定条件时停止调度, 处理器 61指示基站继续调度该 MBMS业务。
存储器 62用于存储该 MBMS业务数据。
MCE首先通过处理器 61触发 eNB统计接收某个 MBMS业务的用户设 备, eNB统计响应确定该 MBMS业务的用户设备的数量,在接收该 MBMS 业务的用户设备少于预定门限时, MCE处理器 61确定停止该 MBMS业务 的 MBSFN传输方式。
处理器 61确定需要关闭该 MBMS业务时, 控制发送器 63向基站发送 该 MBMS业务停止调度通知,处理器 61指示基站继续调度该 MBMS业务。
其中, 处理器 61可以通过 MBMS调度信息更新 eNB的配置信息, 更 新后的配置信息中不再携带需要关闭的 MBMS业务的配置信息, 以作为向 eNB发送的 MBMS业务停止调度通知。
处理器 61控制发送器 63通知 eNB停止对接收用户设备少于预定门限 的 MBMS业务的调度, 比如停止对业务 1的调度。
该 MBMS业务停止调度通知还可以携带延迟停止指示,以指示 eNB延 迟停止调度该 MBMS业务。 更进一步地, MBMS业务停止调度通知还可以 包括延迟停止时间长度信息或者停止时间戳信息, 用于指定 eNB延迟指定 时间后停止调度该 MBMS业务。
比如 MCE决定停止对业务 1的调度,则处理器 61控制发送器 63向 eNB 发送业务 1停止调度通知,该通知可以用于指示业务 1即将停止调度, eNB 根据所述 MBMS业务延迟停止指示继续调度所述业务一段时间后停止对所 述业务的调度。更进一步的,该通知还可以携带延迟停止指示, 以指示 eNB 延迟停止调度业务 1。 并可以进一步指定延迟停止的时间, 用以指示停止调 度时间相对于收到所述停止调度第一通知的相对时间, 如 10分钟、 5分钟、 两个修改周期或者别的时间信息, 也可以是指定时间戳信息, 如 12 点 30 分、 12点 40分这样的具体时间戳信息。
当然, 处理器 61可以控制发送器 63在发送 MBMS业务停止调度通知 的同时或之后,再控制发送器 63发送一个延迟停止指示, 以指示 eNB延迟 停止调度该 MBMS业务。
另一种方式是, 处理器 61控制发送器 63先向 eNB发送一个业务 1停 止调度第一通知, 该第一通知指示业务 1 即将停止调度, 然后控制发送器 63发送一个业务 1停止调度第二通知, 该第二通知直接指示 eNB马上停止 调度业务 1。
可选的所述 MBMS业务停止调度第一通知通过 MBMS调度信息消息 携带, 当所述 MBMS调度信息不再携带所述 MBMS业务时表示要停止所 述 MBMS业务的调度。
上述本发明实施例揭示的方法可以应用于处理器 61中, 或者由处理器 61实现。在实现过程中, 上述方法的各步骤可以通过处理器 61中的硬件的 集成逻辑电路或者软件形式的指令完成。 可以实现或者执行本发明实施例 中的公开的各方法、 步骤及逻辑框图。 结合本发明实施例所公开的方法的 步骤可以直接体现为硬件译码处理器执行完成, 或者用译码处理器中的硬 件及软件模块组合执行完成。 软件模块可以位于随机存储器, 闪存、 只读 存储器, 可编程只读存储器或者电可擦写可编程存储器、 寄存器等本领域 成熟的存储介质中。 该存储介质位于存储器 62 , 处理器 61读取存储器 62 中的信息, 结合其硬件完成上述方法的步骤。 上述基站、 用户设备、 多小区 /多播协作实体的实施例, eNB接收 MCE 发送的 MBMS业务停止调度通知, eNB发送通知用户设备 MBMS业务停 止调度信息, 继续调度该 MBMS业务。 通过这样的方式, 使得 MCE确定 停止某 MBMS业务调度, 而需要继续接收该 MBMS业务的用户设备在建 立单播承载过程中也能继续接收该业务, 有效减少因业务停止调度, 用户 设备需要继续接收该业务而建立单播承载的过程中业务中断时间, 给用户 更好的使用体验。
请参阅图 13 ,图 13是本发明实施例提供的第一种组通讯服务器的结构 示意图, 本实施例的组通讯服务器 160包括第一接收模块 71、 第二接收模 块 72以及通知模块 73 , 其中:
第一接收模块 71用于接收用户设备上报的通过 MBSFN接收组业务的信 息。
组通讯中, 在 MBSFN区域组业务的数据承载在 MBMS业务上, 组通讯 服务器用来管理组内用户设备, 用户设备接收组业务数据之前, 需要先向 组通讯服务器进行注册。
用户设备如果通过 MBSFN方式接收组通讯服务器进行通讯, 可以向组 通讯服务器上报自己正在通过 MBSFN方式接收组业务的信息, 这个组业务 的信息包括组业务的 MBSFN区域标示、 组业务所在的小区标示中的至少一 种。 组通讯服务器通过第一接收模块 71接收用户设备上报的通过 MBSFN接 收组业务的信息。
第二接收模块 72用于从 MCE接收用于接收组业务的该 MBSFN传输停 止通知。
MCE决定停止某个 MBMS业务的调度, 则 MCE通知 eNB停止对该 MBMS业务调度之前, 先通知组通讯服务器。 MCE可以向组通信服务器上 艮自己即将停止的业务信息, 比如 MBSFN区域标示、 MBMS服务器标识 等。
组通讯服务器通过第二接收模块 72从 MCE接收某个 MBSFN传输停止 通知。
通知模块 73用于通知用户设备建立单播承载, 以便用户设备在用于接 收组业务的 MBSFN停止后, 通过单播承载继续接收组业务。 组通讯服务器的第二接收模块 72接收到某个 MBSFN传输即将停止通 知后, 通过通知模块 73通知用户设备建立单播承载, 以便在用于接收组业 务的 MBSFN停止后,通过单播承载替代 MBSFN继续接收该组业务。作为 一种优选, 通知模块 73可以只通知需要继续接收该组业务的用户设备建立 单播承载。
需要继续接收该组业务的用户设备, 根据组通讯服务器的通知, 触发 建立单播承载, 以在该 MBSFN传输停止后,在单播承载上继续接收该组业 务。 在用户设备建立单播承载后, 组通讯服务器通知 MCE停止该 MBSFN 传输。
具体的, 如果用户设备通过该 MBMS业务接收组通讯数据, 则用户设 备的接入层确定某个 MBMS业务即将停止, 向用户设备高层发送指示, 所 述用户设备高层向组通讯服务器上报该 MBMS业务对应的组业务无法继续 采用 MBSFN方式接收,组通讯服务器收到该请求后,如果判断该组业务需 要继续发送给所述用户设备, 则触发所述用户设备建立单播承载以继续接 收所述组业务。 其中所述单播承载为用户设备和基站之间的一个用于传输 MBMS业务的专用无线 载。
其中用户设备高层向组通讯服务器上报该 MBMS业务对应的组业务无 法继续采用 MBSFN方式接收之前, 需要和 eNB建立连接, 为了避免艮多 用户设备同时发起连接建立过程造成网络拥塞, 用户设备在接收到 eNB的 MBMS业务停止调度信息后可以执行一个随即退避, 避免多个用户设备同 时触发单播连接建立过程, 具体的, 用户设备生成一个随机因子, 和一个 预定门限比较, 根据比较结果决定触发单播立过程的延迟。 比如预定随机 因子为 0.5 , 用户生成随机数为 0.6, 0.6>0.5,则用户延迟 10ms触发连接建 立。
本实施例提供的组通讯服务器, 能够实现图 4所示实施例中的各个步 骤, 本实施例中组通讯服务器的各个功能模块的划分只是示意性的, 在能 够实现本发明目的的前提下, 组通讯服务器功能模块的划分并不限于以上 方式, 可以是其他任何可能实现的方式。 例如多个单元或组件可以结合或 者可以集成到另一个系统, 或一些特征可以忽略, 或不执行。
请参阅图 14, 图 14是本发明实施例提供的第三种多小区 /多播协作实 体的结构示意图, 本实施例的多小区 /多播协作实体 170 包括确定模块 81 和通知模块 82, 其中:
确定模块 81用于确定需要停止的 MBSFN传输。
确定模块 81通过通知基站统计接收某个 MBMS业务的用户设备, 根据 基站统计响应确定该 MBMS业务的用户设备的数量, 在接收该 MBMS业务 的用户设备数量少于预定门限时, 确定需要停止该 MBMS业务的 MBSFN传 输方式。
通知模块 82用于在确定模块 81确定需要停止的某个 MBSFN传输后, 通知组通讯服务器该 MBSFN传输停止。
MCE决定停止某个 MBMS业务的 MBSFN传输时, 则 MCE通知 eNB 停止对该 MBMS业务调度之前, 通过通知模块 82先通知组通讯服务器。 MCE可以向组通信服务器上报自己即将停止的业务信息, 比如 MBSFN区 域标示、 MBMS服务器标识等。 以使组通讯服务器通知用户设备建立单播 承载, 以便用户设备再 MBSFN传输停止后,通过单播承载代替 MBSFN继 续接收组业务。
通知组通讯服务器该 MBSFN传输即将停止之后, 经过预定一段时间 后, 向 eNB发送 MBMS业务停止调度信息, 以便 eNB停止对所述 MBMS 业务的调度。
组通讯服务器用于管理其组内用户设备,其在接收到 MBSFN传输即将 停止通知后, 可以通知用户设备建立单播承载, 以便在接收组业务的 MBSFN传输停止后, 也能继续通过单播承载接收组业务。
本实施例提供的多小区 /多播协作实体, 能够实现图 5所示实施例中的 各个步骤, 本实施例中多小区 /多播协作实体的各个功能模块的划分只是示 意性的, 在能够实现本发明目的的前提下, 多小区 /多播协作实体功能模块 的划分并不限于以上方式, 可以是其他任何可能实现的方式。 例如多个单 元或组件可以结合或者可以集成到另一个系统, 或一些特征可以忽略, 或 不执行。
请参阅图 15 ,图 15是本发明实施例提供的第三种用户设备的结构示意 图, 本实施例的用户设备 180包括上报模块 91和单播承载建立模块 92, 其 中: 上报模块 91用于向组通讯服务器上报通过 MBSFN接收组业务的信息。 组通讯中, 在 MBSFN区域组业务的数据承载在 MBMS业务上, 组通讯 服务器用来管理组内用户设备, 用户设备在接收组业务数据之前, 需要先 向组通讯服务器进行注册。 因此, 上报模块 91还用于预先向组通讯服务器 进行注册。
用户设备如果通过 MBSFN方式接收组业务, 可以通过上报模块 91向组 通讯服务器上报自己正在通过 MBSFN方式接收组业务的信息, 这个组业务 的信息包括组业务的 MBSFN区域标示、 组业务所在的小区标示中的至少一 种。
单播承载建立模块 92用于根据组通讯服务器的单播承载建立通知, 建 立单播承载, 同时继续监听承载该组业务的调度信息。
MCE决定停止某个 MBMS业务的调度, 则 MCE通知 eNB停止对该 MBMS业务调度之前, 先通知组通讯服务器。 MCE可以向组通信服务器上 艮自己即将停止的业务信息, 比如 MBSFN区域标示、 MBMS服务器标识 等。
组通讯服务器从 MCE接收某个 MBSFN传输即将停止通知。
组通讯服务器接收到某个 MBSFN传输即将停止通知后,通知用户设备 建立单播承载, 以便通过单播承载继续接收该组业务。 作为一种优选, 可 以只通知需要继续接收该组业务的用户设备建立单播承载。
需要继续接收该组业务的用户设备, 其单播承载建立模块 92根据组通 讯服务器的通知, 触发建立单播承载, 以在该 MBSFN传输停止后, 在单播 承载上继续接收该组业务。 在用户设备建立单播承载后, 组通讯服务器通 知 MCE停止该 MBSFN传输。
在建立单播承载过程中, 用户设备继续监听承载该组业务的调度信息, 在单播承载建立完成后, 用户设备停止监听承载组业务的调度信息, 通过 单播承载来继续接收组业务。
本实施例提供的用户设备, 能够实现图 6所示实施例中的各个步骤, 本实施例中用户设备的各个功能模块的划分只是示意性的, 在能够实现本 发明目的的前提下, 用户设备功能模块的划分并不限于以上方式, 可以是 其他任何可能实现的方式。 例如多个单元或组件可以结合或者可以集成到 另一个系统, 或一些特征可以忽略, 或不执行。
请参阅图 16, 图 16是本发明实施例提供的第二种组通讯服务器的结构 示意图, 本实施例中组通讯服务器 190包括处理器 191、 接收器 193、 存储器 192以及总线系统 194, 其中:
处理器 191控制组通讯服务器 190的操作,处理器 191还可以称为 CPU ( Central Processing Unit, 中央处理单元 )。 处理器 191可能是一种集成电 路芯片, 具有信号的处理能力。 处理器 191还可以是通用处理器、 数字信 号处理器( DSP, Digital Signal Processing )、专用集成电路( ASIC, Application Specific Integrated Circuit )、现场可编程门阵列( FPGA, Field - Programmable Gate Array )或者其他可编程逻辑器件、 分立门或者晶体管逻辑器件、 分立 硬件组件。 通用处理器可以是微处理器或者该处理器也可以是任何常规的 处理器等。
存储器 192可以包括只读存储器和随机存取存储器, 并向处理器 191 提供指令和数据。 存储器 192的一部分还可以包括非易失性随机存取存储 器( NVRAM )。
组通讯服务器 190的各个组件通过总线系统 194耦合在一起, 其中总 线系统 194除包括数据总线之外, 还可以包括电源总线、 控制总线和状态 信号总线等。 该总线系统可以是 ISA ( Industry Standard Architecture, 工业 标准体系结构)总线、 PCI ( Peripheral Component Interconnect, 夕卜部设备互 连 )总线或 EISA ( Extended Industry Standard Architecture , 扩展工业标准体 系结构) 总线等。 所述总线可以是一条或多条物理线路, 当是多条物理线 路时可以分为地址总线、 数据总线、 控制总线等。 在本发明的其它一些实 施例中, 处理器 191、存储器 192以及接收器 193也可以通过通信线路直接 连接。 但是为了清楚说明起见, 在图中将各种总线都标为总线系统 194。
存储器 192存储了如下的元素, 可执行模块或者数据结构, 或者它们 的子集, 或者它们的扩展集:
操作指令: 包括各种操作指令, 用于实现各种操作。
操作系统: 包括各种系统程序, 用于实现各种基础业务以及处理基于 硬件的任务。
在本发明实施例中,处理器 191通过调用存储器 192存储的操作指令(该 操作指令可存储在操作系统中) , 执行如下操作:
处理器 191用于控制接收器 193接收用户设备上报的通过 MBSFN接收组 业务的信息, 并控制接收器 193从 MCE接收某个 MBSFN传输停止通知, 通 知用户设备建立单播承载, 以便用户设备通过单播承载继续接收组业务。
存储器 192用于存储组业务数据。
组通讯中, 在 MBSFN区域组业务的数据承载在 MBMS业务上, 组通讯 服务器用来管理组内用户设备, 用户设备接收组业务数据之前, 需要先向 组通讯服务器进行注册。
用户设备如果通过 MBSFN方式接收组通讯服务器进行通讯, 可以向组 通讯服务器上报自己正在通过 MBSFN方式接收组业务的信息, 这个组业务 的信息包括组业务的 MBSFN区域标示、 组业务所在的小区标示中的至少一 种。 组通讯服务器通过第一接收模块 71接收用户设备上报的通过 MBSFN接 收组业务的信息。
MCE决定停止某个 MBMS业务的调度, 则 MCE通知 eNB停止对该 MBMS业务调度之前, 先通知组通讯服务器。 MCE可以向组通信服务器上 报自己即将停止的业务信息, 比如 MBSFN区域标示、 MBMS服务器标识等。
组通讯服务器处理器 191控制接收器 193从 MCE接收某个 MBSFN传输 即将停止通知。在接收器 193接收到某个 MBSFN传输即将停止通知后,处理 器 191通知用户设备建立单播承载, 以便通过单播承载继续接收该组业务。 作为一种优选, 处理器 191可以只通知需要继续接收该组业务的用户设备建 立单播承载。
需要继续接收该组业务的用户设备, 根据组通讯服务器的通知, 触发 建立单播承载, 以在该 MBSFN传输停止后, 在单播承载上继续接收该组业 务。 在用户设备建立单播承载后, 组通讯服务器通知 MCE停止该 MBSFN传 输。
具体的, 如果用户设备通过该 MBMS业务接收组通讯数据, 则用户设 备的接入层确定某个 MBMS业务即将停止, 向用户设备高层发送指示, 所 述用户设备高层向组通讯服务器上报该 MBMS业务对应的组业务无法继续 采用 MBSFN方式接收,组通讯服务器收到该请求后,如果判断该组业务需 要继续发送给所述用户设备, 则触发所述用户设备建立单播承载以继续接 收所述组业务。 其中所述单播承载为用户设备和基站之间的一个用于传输
MBMS业务的专用无线 载。
其中用户设备高层向组通讯服务器上报该 MBMS业务对应的组业务无 法继续采用 MBSFN方式接收之前, 需要和 eNB建立连接, 为了避免艮多用 户设备同时发起连接建立过程造成网络拥塞, 用户设备在接收到 eNB的 MBMS业务停止调度信息后可以执行一个随即退避, 避免多个用户设备同 时触发单播连接建立过程, 具体的, 用户设备生成一个随机因子, 和一个 预定门限比较, 根据比较结果决定触发单播立过程的延迟。 比如预定随机 因子为 0.5 , 用户生成随机数为 0.6, 0.6>0.5,则用户延迟 10ms触发连接建立。
上述本发明实施例揭示的方法可以应用于处理器 191 中, 或者由处理 器 191 实现。 在实现过程中, 上述方法的各步骤可以通过处理器 191 中的 硬件的集成逻辑电路或者软件形式的指令完成。 可以实现或者执行本发明 实施例中的公开的各方法、 步骤及逻辑框图。 结合本发明实施例所公开的 方法的步骤可以直接体现为硬件译码处理器执行完成, 或者用译码处理器 中的硬件及软件模块组合执行完成。 软件模块可以位于随机存储器, 闪存、 只读存储器, 可编程只读存储器或者电可擦写可编程存储器、 寄存器等本 领域成熟的存储介质中。 该存储介质位于存储器 192, 处理器 191读取存储 器 192中的信息, 结合其硬件完成上述方法的步骤。
请参阅图 17 , 图 17是本发明实施例提供的第四种多小区 /多播协作实 体的结构示意图, 本实施例的多小区 /多播协作实体 200包括处理器 201存 储器 202、 发送器 203以及总线系统 204 , 其中:
处理器 201控制多小区 /多播协作实体 200的操作, 处理器 201还可以 称为 CPU ( Central Processing Unit, 中央处理单元 )。 处理器 201可能是一 种集成电路芯片, 具有信号的处理能力。 处理器 201还可以是通用处理器、 数字信号处理器 ( DSP, Digital Signal Processing )、 专用集成电路( ASIC, Application Specific Integrated Circuit )、 现场可编程门阵列 ( FPGA, Field - Programmable Gate Array )或者其他可编程逻辑器件、 分立门或者晶体管逻 辑器件、 分立硬件组件。 通用处理器可以是微处理器或者该处理器也可以 是任何常规的处理器等。
存储器 202可以包括只读存储器和随机存取存储器, 并向处理器 201 提供指令和数据。 存储器 202的一部分还可以包括非易失性随机存取存储 器( NVRAM )。
多小区 /多播协作实体 200的各个组件通过总线系统 204耦合在一起, 其中总线系统 204除包括数据总线之外, 还可以包括电源总线、 控制总线 和状态信号总线等。 该总线系统可以是 ISA ( Industry Standard Architecture, 工业标准体系结构)总线、 PCI ( Peripheral Component Interconnect, 外部设 备互连 )总线或 EISA ( Extended Industry Standard Architecture , 扩展工业标 准体系结构)总线等。 所述总线可以是一条或多条物理线路, 当是多条物 理线路时可以分为地址总线、 数据总线、 控制总线等。 在本发明的其它一 些实施例中, 处理器 201、存储器 202以及发送器 203也可以通过通信线路 直接连接。但是为了清楚说明起见,在图中将各种总线都标为总线系统 204。
存储器 202存储了如下的元素, 可执行模块或者数据结构, 或者它们 的子集, 或者它们的扩展集:
操作指令: 包括各种操作指令, 用于实现各种操作。
操作系统: 包括各种系统程序, 用于实现各种基础业务以及处理基于 硬件的任务。
在本发明实施例中, 处理器 201通过调用存储器 202存储的操作指令 (该操作指令可存储在操作系统中), 执行如下操作:
处理器 201用于确定需要关闭的 MBMS业务, 控制发送器 203向基站发 送 MBMS业务停止调度通知, 该 MBMS业务停止调度通知指示某个 MBMS 业务即将停止调度, 处理器 201指示基站继续调度该 MBMS业务;
存储器 202用于存储 MBMS业务数据。
处理器 201通过通知基站统计接收某个 MBMS业务的用户设备, 根据 基站统计响应确定该 MBMS业务的用户设备的数量, 在接收该 MBMS业 务的用户设备数量少于预定门限时,确定需要停止该 MBMS业务的 MBSFN 传输方式。
MCE决定停止某个 MBMS业务的 MBSFN传输时, 则 MCE通知 eNB 停止对该 MBMS业务调度之前, 处理器 201控制发送器 203先通知组通讯 服务器。 发送器 203 可以向组通信服务器上报自己即将停止的业务信息, 比如 MBSFN区域标示、 MBMS服务器标识等。 以使组通讯服务器通知用 户设备建立单播承载, 以便用户设备再 MBSFN传输停止后,通过单播承载 代替 MBSFN继续接收组业务。
通知组通讯服务器该 MBSFN传输即将停止之后, 经过预定一段时间 后, 向 eNB发送 MBMS业务停止调度信息, 以便 eNB停止对所述 MBMS 业务的调度。
组通讯服务器用于管理其组内用户设备,其在接收到 MBSFN传输即将 停止通知后, 可以通知用户设备建立单播承载, 以便在接收组业务的 MBSFN传输停止后, 也能继续通过单播承载接收组业务。
上述本发明实施例揭示的方法可以应用于处理器 201 中, 或者由处理 器 201 实现。 在实现过程中, 上述方法的各步骤可以通过处理器 201 中的 硬件的集成逻辑电路或者软件形式的指令完成。 可以实现或者执行本发明 实施例中的公开的各方法、 步骤及逻辑框图。 结合本发明实施例所公开的 方法的步骤可以直接体现为硬件译码处理器执行完成, 或者用译码处理器 中的硬件及软件模块组合执行完成。 软件模块可以位于随机存储器, 闪存、 只读存储器, 可编程只读存储器或者电可擦写可编程存储器、 寄存器等本 领域成熟的存储介质中。 该存储介质位于存储器 202, 处理器 201读取存储 器 202中的信息, 结合其硬件完成上述方法的步骤。
请参阅图 18 ,图 18是本发明实施例提供的第四种用户设备的结构示意 图, 本实施例的用户设备 210包括处理器 211、 存储器 212、 接收器 213以 及总线系统 204, 其中:
处理器 211控制用户设备 210的操作, 处理器 211还可以称为 CPU ( Central Processing Unit, 中央处理单元 )。 处理器 211可能是一种集成电 路芯片, 具有信号的处理能力。 处理器 211还可以是通用处理器、 数字信 号处理器( DSP, Digital Signal Processing )、专用集成电路( ASIC, Application Specific Integrated Circuit )、现场可编程门阵列( FPGA, Field - Programmable Gate Array )或者其他可编程逻辑器件、 分立门或者晶体管逻辑器件、 分立 硬件组件。 通用处理器可以是微处理器或者该处理器也可以是任何常规的 处理器等。
存储器 212可以包括只读存储器和随机存取存储器, 并向处理器 211 提供指令和数据。 存储器 212的一部分还可以包括非易失性随机存取存储 器( NVRAM )。
用户设备 210的各个组件通过总线系统 214耦合在一起, 其中总线系 统 214除包括数据总线之外, 还可以包括电源总线、 控制总线和状态信号 总线等。 该总线系统可以是 ISA ( Industry Standard Architecture , 工业标准 体系结构)总线、 PCI ( Peripheral Component Interconnect, 夕卜部设备互连 ) 总线或 EISA ( Extended Industry Standard Architecture ,扩展工业标准体系结 构)总线等。 所述总线可以是一条或多条物理线路, 当是多条物理线路时 可以分为地址总线、 数据总线、 控制总线等。 在本发明的其它一些实施例 中,处理器 211、存储器 212以及接收器 213也可以通过通信线路直接连接。 但是为了清楚说明起见, 在图中将各种总线都标为总线系统 214。
存储器 212存储了如下的元素, 可执行模块或者数据结构, 或者它们 的子集, 或者它们的扩展集:
操作指令: 包括各种操作指令, 用于实现各种操作。
操作系统: 包括各种系统程序, 用于实现各种基础业务以及处理基于 硬件的任务。
在本发明实施例中, 处理器 211通过调用存储器 212存储的操作指令 (该操作指令可存储在操作系统中), 执行如下操作:
处理器 211用于向组通讯服务器上报通过 MBSFN接收组业务的信息,并 控制接收器 213接收组通讯服务器的通知, 根据组通讯服务器的通知, 在需 要继续接收组业务时, 建立单播承载, 同时继续监听承载该组业务的调度 信息。
存储器 212用于存储数据。
组通讯中, 在 MBSFN区域组业务的数据承载在 MBMS业务上, 组通 讯服务器用来管理组内用户设备, 用户设备在接收组业务数据之前, 需要 先向组通讯服务器进行注册。
用户设备如果通过 MBSFN方式接收组业务,处理器 211向组通讯服务 器上报自己正在通过 MBSFN方式接收组业务的信息,这个组业务的信息包 括组业务的 MBSFN区域标示、 组业务所在的小区标示中的至少一种。
MCE决定停止某个 MBMS业务的调度, 则 MCE通知 eNB停止对该 MBMS业务调度之前, 先通知组通讯服务器。 MCE可以向组通信服务器上 艮自己即将停止的业务信息, 比如 MBSFN区域标示、 MBMS服务器标识 等。
组通讯服务器从 MCE接收某个 MBSFN传输即将停止通知。
组通讯服务器接收到某个 MBSFN传输即将停止通知后,通知用户设备 建立单播承载, 以便通过单播承载继续接收该组业务。 作为一种优选, 可 以只通知需要继续接收该组业务的用户设备建立单播承载。
需要继续接收该组业务的用户设备, 处理器 211 根据组通讯服务器的 通知, 触发建立单播承载, 以在该 MBSFN传输停止后, 在单播承载上继续 接收该组业务。 在用户设备建立单播承载后, 组通讯服务器通知 MCE停止 该 MBSFN传输。
在建立单播承载过程中, 处理器 211 继续监听承载该组业务的调度信 息, 在单播承载建立完成后, 处理器 211停止监听承载组业务的调度信息, 通过单播承载来继续接收组业务。
上述本发明实施例揭示的方法可以应用于处理器 211 中, 或者由处理 器 211 实现。 在实现过程中, 上述方法的各步骤可以通过处理器 211 中的 硬件的集成逻辑电路或者软件形式的指令完成。 可以实现或者执行本发明 实施例中的公开的各方法、 步骤及逻辑框图。 结合本发明实施例所公开的 方法的步骤可以直接体现为硬件译码处理器执行完成, 或者用译码处理器 中的硬件及软件模块组合执行完成。 软件模块可以位于随机存储器, 闪存、 只读存储器, 可编程只读存储器或者电可擦写可编程存储器、 寄存器等本 领域成熟的存储介质中。 该存储介质位于存储器 212, 处理器 211读取存储 器 212中的信息, 结合其硬件完成上述方法的步骤。
通过上述组通讯服务器、 用户设备以及多小区 /多播协作实体实施例的 详细描述, 可以理解, 本发明实施例中, MCE 决定停止某个需要停止的 MBSFN传输时, 在通知 eNB之前, 先通知管理组内用户设备的组通讯服 务器, 组通讯服务器通知用户设备建立单播承载, 在用户设备建立单播承 载后再通知 MCE停止该 MBSFN传输。 通过这样的方式, MCE决定停止 某个 MBSFN传输时,需要继续接收通过该 MBSFN传输的组业务的用户设 备根据组通讯服务器的通知先建立单播承载, 避免该组业务中断, 给用户 更好的使用体验。 通过上述实施例的阐述, 可以理解, 本发明旨在解决 MCE确定停止调 度某业务后, 需要继续接收该业务的 UE需要建立单播承载,如何减少在单 播承载建立过程中引发的业务中断时间。 送的 MBMS业务停止调度通知, 基站发送通知用户设备 MBMS业务停止 调度信息, 继续调度该 MBMS业务。 通过这样的方式, 使得 MCE确定停 止某 MBMS业务调度, 而需要继续接收该 MBMS业务的用户设备在建立 单播承载过程中也能继续接收该业务, 有效减少因业务停止调度, 用户设 备需要继续接收该业务而建立单播承载的过程中业务中断时间, 给用户更 好的使用体验。
另一方面, 本发明实施例提供的还有一种保持业务连续性的方法和设 备, MCE决定停止某个需要停止的 MBSFN传输时, 在通知 eNB之前, 先 通知管理组内用户设备的组通讯服务器, 组通讯服务器通知用户设备建立 单播承载, 在用户设备建立单播承载后再通知 MCE停止该 MBSFN传输。 通过这样的方式, MCE决定停止某个 MBSFN传输时, 需要继续接收通过 该 MBSFN传输的组业务的用户设备根据组通讯服务器的通知先建立单播 承载, 避免该组业务中断, 给用户更好的使用体验。
在本申请所提供的几个实施例中, 应该理解到, 所揭露的系统, 装置 和方法, 可以通过其它的方式实现。 例如, 以上所描述的装置实施例仅仅 是示意性的, 例如, 所述模块或单元的划分, 仅仅为一种逻辑功能划分, 实际实现时可以有另外的划分方式, 例如多个单元或组件可以结合或者可 以集成到另一个系统, 或一些特征可以忽略, 或不执行。 另一点, 所显示 或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口, 装 置或单元的间接耦合或通信连接, 可以是电性, 机械或其它的形式。 作为单元显示的部件可以是或者也可以不是物理单元, 即可以位于一个地 方, 或者也可以分布到多个网络单元上。 可以根据实际的需要选择其中的 部分或者全部单元来实现本实施例方案的目的。
另外, 在本申请各个实施例中的各功能单元可以集成在一个处理单元 中, 也可以是各个单元单独物理存在, 也可以两个或两个以上单元集成在 一个单元中。 上述集成的单元既可以采用硬件的形式实现, 也可以采用软 件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销 售或使用时, 可以存储在一个计算机可读取存储介质中。 基于这样的理解, 本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方 案的全部或部分可以以软件产品的形式体现出来, 该计算机软件产品存储 在一个存储介质中, 包括若干指令用以使得一台计算机设备(可以是个人 计算机, 服务器, 或者多小区 /多播协作实体等)或处理器 (processor )执 行本申请各个实施例所述方法的全部或部分步骤。 而前述的存储介质包括:
U盘、 移动硬盘、 只读存储器(ROM, Read-Only Memory ), 随机存取存储 器(RAM, Random Access Memory ),磁碟或者光盘等各种可以存储程序代 码的介质。
以上所述仅为本申请的实施例, 并非因此限制本申请的专利范围, 凡 是利用本申请说明书及附图内容所作的等效结构或等效流程变换, 或直接 或间接运用在其他相关的技术领域, 均同理包括在本申请的专利保护范围 内。

Claims

权利要求
1.一种保持业务连续性的方法, 其特征在于, 所述方法包括: 基站接收多小区 /多播协作实体发送的多媒体广播组播业务 MBMS业务 停止调度第一通知, 所述 MBMS业务停止调度第一通知是所述多小区 /多播 协作实体确定关闭所述 MBMS业务时向所述基站发送的通知;
所述基站根据所述 MBMS业务停止调度第一通知向用户设备发送 MBMS业务停止调度信息;
所述基站继续调度所述 MBMS业务直到满足预定条件再停止调度所述 MBMS业务。
2.根据权利要求 1所述的方法, 其特征在于, 所述 MBMS业务停止调度 第一通知携带延迟停止指示, 以指示所述基站延迟停止调度所述 MBMS业 务。
3.根据权利要求 2所述的方法, 其特征在于, 所述预定条件是下列条件 之一:
收到多小区 /多播协作实体发送的 MBMS业务停止调度第二通知, 所述 MBMS业务停止调度第二通知指示基站停止调度所述 MBMS业务; 或
收到所述 MBMS业务停止调度第一通知之后, 达到所述 MBMS业务停 止调度第一通知指示的时间点; 或
收到所述 MBMS业务停止调度第一通知之后经过第一预定时间; 或 收到所述 MBMS业务停止调度第一通知之后, 达到第二预定时间点。
4.根据权利要求 2所述的方法, 其特征在于, 所述 MBMS业务停止调度 第一通知包括所述延迟停止时间长度信息或者预定停止时间戳信息。
5.根据权利要求 1-4任一项所述的方法, 其特征在于, 所述 MBMS业务 停止调度第一通知指示所述 MBMS业务满足预定条件时停止调度。
6.根据权利要求 1-5任一项所述的方法, 其特征在于, 所述基站通过点 到多点控制信道消息中不携带所述 MBMS业务的配置信息作为向用户设备 发送的所述 MBMS业务停止调度信息。
7.根据权利要求 6所述的方法, 其特征在于, 所述基站通知用户设备所 述业务停止调度信息的同时或之后, 发送延迟停止指示, 以告知所述用户 设备会延迟停止调度所述 MBMS业务。
8.根据权利要求 1-5任一项所述的方法, 其特征在于, 所述 MBMS业务 停止调度信息携带 MBMS业务即将停止调度指示, 以告知所述用户设备即 将停止调度所述 MBMS业务。
9.根据权利要求 7或 8所述的方法, 其特征在于, 所述基站通过点到多点 控制信道、 寻呼控制信道、 MBMS传输信道调度信息中的任何一种发送所 述延迟停止指示或者 MBMS业务即将停止调度指示。
10.—种保持业务连续性的方法, 其特征在于, 所述方法包括: 用户设备从基站接收 MBMS业务停止调度信息, 确定所述基站即将停 止调度所述 MBMS业务;
所述用户设备继续监听所述 MBMS业务的调度信息;
根据所述 MBMS业务的调度信息, 接收所述 MBMS业务。
11.根据权利要求 10所述的方法, 其特征在于,
如果所述 MBMS业务的调度信息中不再包含所述 MBMS业务配置信 息, 则停止接收所述 MBMS业务。
12.根据权利要求 10或 11所述的方法, 其特征在于, 所述用户设备从基 站接收 MBMS业务停止调度信息的步骤包括: 所述用户设备接收点到多点 控制信道消息, 根据所述消息中不携带所述 MBMS业务的配置信息确定所 述基站即将停止调度所述 MBMS业务。
13.根据权利要求 10所述的方法, 其特征在于, 所述 MBMS业务停止调 度信息携带 MBMS业务即将停止调度指示, 用于指示用户设备所述 MBMS 即将停止调度, 所述用户设备根据 MBMS业务即将停止调度指示, 确定所 述基站即将停止调度所述 MBMS业务。
14.根据权利要求 10所述的方法, 其特征在于, 所述用户设备接收业务 停止调度信息的同时或之后, 从基站接收 MBMS业务延迟停止指示, 根据 所述 MBMS业务延迟停止指示, 确定所述基站即将停止调度所述 MBMS业 务。
15.根据权利要求 13或 14所述的方法, 其特征在于, 通过点到多点控制 信道、 寻呼控制信道、 MBMS传输信道调度信息中的任何一种接收所述延 迟停止或者 MBMS业务即将停止调度指示。
16.根据权利要求 10所述的方法, 其特征在于, 所述方法还包括: 确定 所述基站即将停止调度所述 MBMS业务之后, 触发单播承载的建立, 在所 述单播承载建立完成后, 停止所述 MBMS业务对应的点到多点业务信道接 收所述 MBMS业务。
17.—种保持业务连续性的方法, 其特征在于, 所述方法包括: 多小区 /多播协作实体确定需要关闭的 MBMS业务;
向基站发送 MBMS业务停止调度通知, 所述 MBMS业务停止调度通知 告知所述基站所述 MBMS业务满足预定条件时停止调度, 指示所述基站继 续调度所述 MBMS业务。
18.根据权利要求 17所述的方法, 其特征在于, 所述 MBMS业务停止调 度通知包括所述继续调度预定时间的时间长度信息或者预定停止时间戳信 息或者停止 MBMS业务的指示信息, 以指示所述基站继续调度所述 MBMS 业务预定时间。
19.根据权利要求 17或 18所述的方法, 其特征在于, 所述多小区 /多播协 作实体确定需要关闭的 MBMS业务的步骤包括:
所述多小区 /多播协作实体通知所述基站统计接收所述 MBMS业务的用 户设备;
根据基站统计响应确定所述 MBMS业务的用户设备的数量, 在所述接 收所述 MBMS业务的用户设备数量少于预定门限时, 确定需要关闭所述 MBMS业务。
20.根据权利要求 17-19任一项所述的方法, 其特征在于, 所述向基站发 送 MBMS业务停止调度通知的步骤包括:
通过 MBMS调度信息更新基站的配置信息, 更新后的所述配置信息不 再携带所述需要关闭的 MBMS业务的配置信息, 以作为向基站发送的所述 MBMS业务停止调度通知。
21.—种保持业务连续性的方法, 其特征在于, 所述方法包括: 组通讯服务器接收用户设备上报的通过多媒体广播组播业务单频网 MBSFN接收组业务的信息;
所述组通讯服务器从多小区 /多播协作实体接收用于接收所述组业务的 所述 MBSFN传输停止通知; 所述组通讯服务器通知所述用户设备建立单播承载, 以便所述用户设 备在用于接收组业务的所述 MBSFN停止后, 通过所述单播承载继续接收所 述组业务。
22.根据权利要求 21所述的方法, 其特征在于, 所述 MBSFN传输停止通 知包含停止调度的业务信息, 所述业务信息包括所述 MBSFN区域信息以及 MBMS的标识中的至少一种。
23.根据权利要求 21或 22所述的方法, 其特征在于, 所述方法还包括: 在所述用户设备建立单播承载后, 所述组通讯服务器通知所述多小区 / 多播协作实体停止所述 MBSFN传输。
24.—种保持业务连续性的方法, 其特征在于, 所述方法包括: 多小区 /多播协作实体确定需要停止的 MBSFN传输;
通知组通讯服务器所述 MBSFN传输即将停止, 以使所述组通讯服务器 通知所述用户设备建立单播承载, 以便所述用户设备在所述 MBSFN传输停 止后, 通过所述单播承载代替所述 MBSFN继续接收所述组业务。
25.根据权利要求 24所述的方法, 其特征在于, 所述多小区 /多播协作实 体确定需要停止的 MBSFN传输的步骤包括:
所述多小区 /多播协作实体通知基站统计接收所述 MBMS业务的用户设 备;
根据所述基站统计响应确定所述 MBMS业务的用户设备的数量, 在所 述接收所述 MBMS业务的用户设备数量少于预定门限时, 确定需要停止所 述 MBMS业务的 MBSFN传输方式。
26.根据权利要求 24或 25所述的方法, 其特征在于, 所述 MBSFN传输即 将停止通知包含停止调度的业务信息, 所述业务信息包括所述 MBSFN区域 信息以及 MBMS的标识中的至少一种。
27.—种保持业务连续性的方法, 其特征在于, 所述方法包括: 用户设备向组通讯服务器上报通过多媒体广播组播业务单频网 MBSFN 接收组业务的信息;
根据所述组通讯服务器的单播承载建立通知, 建立单播承载, 同时继 续监听承载所述组业务的调度信息。
28.根据权利要求 27所述的方法, 其特征在于, 所述组业务的信息包括: 所述 MBSFN区域信息以及 MBMS的标识中的至少一种。
29.根据权利要求 27或 28所述的方法, 其特征在于, 所述用户设备向组 通讯服务器上报通过 MBSFN接收组业务的信息的步骤之前, 还包括:
所述用户设备向所述组通讯服务器进行注册。
30.根据权利要求 27-29任一项所述的方法, 其特征在于, 所述方法还包 括:
所述单播承载建立完成后, 所述用户设备停止监听承载所述组业务的 调度信息。
31.—种基站, 其特征在于, 所述基站包括接收模块和调度模块, 其中: 所述接收模块用于接收多小区 /多播协作实体发送的多媒体广播组播业 务 MBMS业务停止调度第一通知, 所述 MBMS业务停止调度第一通知是所 述多小区 /多播协作实体确定关闭所述 MBMS业务时向所述基站发送的通 知;
所述调度模块用于在所述接收模块接收到所述 MBMS业务停止调度第 一通知后, 向用户设备发送 MBMS业务停止调度信息, 并继续调度所述 MBMS业务直到满足预定条件再停止调度所述 MBMS业务。
32.根据权利要求 31所述的基站, 其特征在于, 所述 MBMS业务停止调 度第一通知携带延迟停止指示, 以指示所述基站延迟停止调度所述 MBMS 业务。
33.根据权利要求 32所述的基站, 其特征在于, 所述调度模块在满足下 列条件之一时, 停止调度所述 MBMS业务:
所述接收模块收到多小区 /多播协作实体发送的 MBMS业务停止调度第 二通知, 所述 MBMS业务停止调度第二通知指示基站停止调度所述 MBMS 业务停止调度; 或
所述接收模块收到所述 MBMS业务停止调度第一通知之后, 达到所述 MBMS业务停止调度第一通知指示的时间点; 或
所述接收模块收到所述 MBMS业务停止调度第一通知之后经过第一预 定时间。
34.根据权利要求 32所述的基站, 其特征在于, 所述 MBMS业务停止调 度第一通知包括所述延迟停止时间长度信息或者预定停止时间戳信息。
35.根据权利要求 31-34任一项所述的基站, 其特征在于, 所述 MBMS业 务停止调度第一通知指示所述 MBMS业务满足预定条件时停止调度。
36.根据权利要求 31-35任一项所述的基站, 其特征在于, 所述调度模块 通过点到多点控制信道消息中不携带所述 MBMS业务的配置信息作为向用 户设备发送的所述 MBMS业务停止调度信息。
37.根据权利要求 36所述的基站, 其特征在于, 所述调度模块在通知用 户设备所述业务停止调度信息的同时或之后, 发送延迟停止指示, 以告知 所述用户设备会延迟停止调度所述 MBMS业务。
38.根据权利要求 31-35任一项所述的基站, 其特征在于, 所述 MBMS业 务停止调度信息携带所述 MBMS业务即将停止调度指示, 以告知所述用户 设备即将停止调度所述 MBMS业务。
39.根据权利要求 37或 38所述的基站, 其特征在于, 所述调度模块通过 点到多点控制信道、 寻呼控制信道、 MBMS传输信道调度信息中的任何一 种发送所述延迟停止指示或者所述 MBMS业务即将停止调度指示。
40.—种用户设备, 其特征在于, 所述用户设备包括第一接收模块、 监 听模块以及第二接收模块, 其中:
所述第一接收模块用于从基站接收 MBMS业务停止调度信息, 确定所 述基站即将停止调度所述 MBMS业务;
所述监听模块用于在所述第一接收模块确定所述基站在满足预定条件 时停止调度所述 MBMS业务后, 继续监听所述 MBMS业务的调度信息; 所述第二接收模块用于根据所述监听模块监听到的所述 MBMS业务的 调度信息, 接收所述 MBMS业务。
41.根据权利要求 40所述的用户设备, 其特征在于, 如果所述 MBMS业 务的调度信息中不再包含所述 MBMS业务配置信息, 所述第二接收模块停 止接收所述 MBMS业务。
42.根据权利要求 40或 41所述的用户设备, 其特征在于, 所述第一接收 模块用于接收点到多点控制信道消息, 根据所述消息中不携带所述 MBMS 业务的配置信息确定所述基站即将停止调度所述 MBMS业务。
43.根据权利要求 40所述的用户设备, 其特征在于, 所述 MBMS业务停 止调度信息携带 MBMS业务即将停止调度指示, 用于指示用户设备所述 MBMS即将停止调度, 所述监听模块用于根据 MBMS业务即将停止调度指 示, 确定所述基站即将停止调度所述 MBMS业务。
44.根据权利要求 40所述的用户设备, 所述第一接收模块用于接收业务 停止调度信息的同时或之后, 从基站接收 MBMS业务延迟停止指示, 所述 监听模块用于根据所述 MBMS业务延迟停止指示, 确定所述基站即将停止 调度所述 MBMS业务。
45.根据权利要求 43或 44所述的用户设备, 其特征在于, 所述第一接收 模块通过点到多点控制信道、 寻呼控制信道、 MBMS传输信道调度信息中 的任何一种接收所述延迟停止指示或者 MBMS业务即将停止调度指示。
46.根据权利要求 40所述的用户设备, 其特征在于, 所述用户设备还包 括单播建立模块, 所述单播建立模块用于在所述用户设备确定所述基站即 将停止调度所述 MBMS业务之后, 触发单播承载的建立;
所述第二接收模块在所述单播承载建立完成后, 停止所述 MBMS业务 对应的点到多点业务信道接收所述 MBMS业务。
47.—种多小区 /多播协作实体,其特征在于,所述多小区 /多播协作实体 包括确定模块和调度模块, 其中:
所述确定模块用于确定需要关闭的 MBMS业务;
所述调度模块用于在所述确定模块确定需要关闭所述 MBMS业务时, 向基站发送 MBMS业务停止调度通知, 所述 MBMS业务停止调度通知告知 所述基站所述 MBMS业务满足预定条件时停止调度, 所述调度模块指示所 述基站继续调度所述 MBMS业务。
48.根据权利要求 47所述的多小区 /多播协作实体, 其特征在于, 所述 MBMS业务停止调度通知包括所述继续调度预定时间的时间长度信息或者 预定停止时间戳信息或者即将停止 MBMS业务的指示信息, 以指示所述基 站继续调度所述 MBMS业务预定时间。
49.根据权利要求 47或 48所述的多小区 /多播协作实体, 其特征在于, 所 述确定模块用于通过通知所述基站统计接收所述 MBMS业务的用户设备, 根据基站统计响应确定所述 MBMS业务的用户设备的数量, 在所述接收所 述 MBMS业务的用户设备数量少于预定门限时, 确定需要关闭所述 MBMS 业务的 MBSFN传输方式。
50.根据权利要求 47-49任一项所述的多小区 /多播协作实体, 其特征在 于, 所述调度模块通过 MBMS调度信息更新基站的配置信息, 更新后的所 述配置信息不再携带所述需要关闭的 MBMS业务的配置信息, 以作为向基 站发送的所述 MBMS业务停止调度通知。
51.—种基站, 其特征在于, 所述基站包括处理器、 接收器、 发送器和 存储器, 所述处理器分别耦接所述接收器、 发送器以及存储器, 其中: 所述处理器用于控制接收器接收多小区 /多播协作实体发送的多媒体广 播组播业务 MBMS业务停止调度第一通知, 所述 MBMS业务停止调度第一 通知是所述多小区 /多播协作实体确定关闭所述 MBMS业务时向所述基站发 送的通知, 在接收所述 MBMS业务停止调度第一通知后, 控制所述发送器 向用户设备发送 MBMS业务停止调度信息, 所述处理器继续调度所述 MBMS业务直到满足预定条件再停止调度所述 MBMS业务;
所述存储器用于存储所述 MBMS数据。
52.—种用户设备, 其特征在于, 所述用户设备包括处理器、 接收器以 及存储器, 所述处理器分别耦接所述接收器和所述存储器, 其中:
所述处理器用于控制所述接收器从基站接收 MBMS业务停止调度信 息, 确定所述基站在满足预定条件时停止调度所述 MBMS业务, 继续监听 所述 MBMS业务的调度信息, 并控制所述接收器根据所述处理器监听到的 所述 MBMS业务的调度信息, 接收所述 MBMS业务;
所述存储器用于存储所述 MBMS业务数据。
53.—种多小区 /多播协作实体,其特征在于,所述多小区 /多播协作实体 包括处理器、 发送器和存储器, 所述处理器分别耦接所述发送器和存储器, 其中:
所述处理器用于确定需要关闭的 MBMS业务, 控制所述发送器向基站 发送 MBMS业务停止调度通知, 所述 MBMS业务停止调度通知告知所述基 站所述 MBMS业务满足预定条件时停止调度, 所述处理器指示所述基站继 续调度所述 MBMS业务;
所述存储器用于存储所述 MBMS业务数据。
54.—种组通讯服务器, 其特征在于, 所述组通讯服务器包括第一接收 模块、 第二接收模块以及通知模块, 其中: 所述第一接收模块用于接收用户设备上报的通过多媒体广播组播业务 单频网 MBSFN接收组业务的信息;
所述第二接收模块用于从多小区 /多播协作实体接收用于接收所述组业 务的所述 MBSFN传输停止通知;
所述通知模块用于通知所述用户设备建立单播承载, 以便所述用户设 备在用于接收所述组业务的所述 MBSFN停止后, 通过所述单播承载继续接 收所述组业务。
55.根据权利要求 54所述的组通讯服务器, 其特征在于, 所述 MBSFN传 输停止通知包含停止调度的业务信息, 所述业务信息包括所述 MBSFN信息 以及 MBMS的标识中的至少一种。
56.根据权利要求 54或 55所述的组通讯服务器, 其特征在于, 所述通知 模块还用于在所述用户设备建立单播承载后, 通知所述多小区 /多播协作实 体停止所述 MBSFN传输。
57.—种多小区 /多播协作实体,其特征在于,所述多小区 /多播协作实体 包括确定模块和通知模块, 其中:
所述确定模块用于确定需要停止的 MBSFN传输;
所述通知模块用于在所述确定模块确定需要停止的所述 MBSFN传输 后, 通知组通讯服务器所述 MBSFN传输即将停止, 以使所述组通讯服务器 通知所述用户设备建立单播承载, 以便所述用户设备在所述 MBSFN传输停 止后, 通过所述单播承载代替所述 MBSFN继续接收所述组业务。
58.根据权利要求 57所述的多小区 /多播协作实体, 其特征在于, 所述确 定模块通过通知基站统计接收所述 MBMS业务的用户设备, 根据所述基站 统计响应确定所述 MBMS业务的用户设备的数量, 在所述接收所述 MBMS 业务的用户设备数量少于预定门限时, 确定需要停止所述 MBMS业务的 MBSFN传输方式。
59.根据权利要求 57或 58所述的多小区 /多播协作实体, 其特征在于, 所 述 MBSFN传输停止通知包含停止调度的业务信息, 所述业务信息包括所述 MBSFN信息以及 MBMS的标识中的至少一种。
60.—种用户设备, 其特征在于, 所述用户设备包括上报模块和单播承 载建立模块, 其中: 所述上报模块用于向组通讯服务器上报通过多媒体广播组播业务单频 网 MBSFN接收组业务的信息;
所述单播承载建立模块用于根据组通讯服务器的单播承载建立通知, 建立单播承载, 同时继续监听承载所述组业务的调度信息。
61.根据权利要求 60所述的用户设备, 其特征在于, 所述组业务的信息 包括所述 MBSFN信息以及 MBMS的标识中的至少一种。
62.根据权利要求 60或 61所述的用户设备, 其特征在于, 所述上报模块 还用于向所述组通讯服务器进行注册。
63.根据权利要求 60-62任一项所述的用户设备, 其特征在于, 所述单播 承载建立模块在所述单播承载建立完成后, 停止监听承载所述组业务的调 度信息。
64.—种组通讯服务器, 其特征在于, 所述组通讯服务器包括处理器、 接收器和存储器, 所述处理器分别耦接所述接收器和所述存储器, 其中: 所述处理器用于控制所述接收器接收用户设备上报的通过多媒体广播 组播业务单频网 MBSFN接收组业务的信息, 并控制所述接收器从多小区 / 多播协作实体接收用于接收所述组业务的所述 MBSFN传输停止通知, 通知 所述用户设备建立单播承载, 以便所述用户设备在用于接收所述组业务的 所述 MBSFN停止后, 通过所述单播承载继续接收所述组业务;
所述存储器用于存储所述组业务数据。
65.—种多小区 /多播协作实体,其特征在于,所述多小区 /多播协作实体 包括处理器、 发送器和存储器, 所述处理器分别耦接所述发送器和存储器, 其中:
所述处理器用于确定需要停止的 MBSFN传输, 控制所述发送器向组通 讯服务器发送通知, 以通知所述组通讯服务器所述 MBSFN传输即将停止, 以使所述组通讯服务器通知所述用户设备建立单播承载, 以便所述用户设 备在所述 MBSFN传输停止后,通过所述单播承载代替所述 MBSFN继续接收 所述组业务;
所述存储器用于存储数据。
66.—种用户设备, 其特征在于, 所述用户设备包括处理器、 接收器和 存储器, 所述处理器分别耦接所述接收器和所述存储器, 其中: 所述处理器用于向组通讯服务器上报通过多媒体广播组播业务单频网
MBSFN接收组业务的信息, 并控制接收器接收组通讯服务器的通知, 根据 所述组通讯服务器的单播承载建立通知, 建立单播承载, 同时继续监听承 载所述组业务的调度信息;
所述存储器用于存储数据。
PCT/CN2014/071599 2013-12-27 2014-01-27 一种保持业务连续性的方法及设备 WO2015096270A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
KR1020167020051A KR101815409B1 (ko) 2013-12-27 2014-01-27 서비스 계속성을 유지하기 위한 방법 및 장치
JP2016543116A JP6480459B2 (ja) 2013-12-27 2014-01-27 サービス継続性を維持する方法およびデバイス
EP14873191.2A EP3076690B1 (en) 2013-12-27 2014-01-27 Method and device for keeping service continuity
EP17205709.3A EP3373613B1 (en) 2013-12-27 2014-01-27 Method and device for maintaining service continuity
CN201480071365.1A CN105850161B (zh) 2013-12-27 2014-01-27 一种保持业务连续性的方法及设备
US15/194,116 US10206224B2 (en) 2013-12-27 2016-06-27 Method and device for maintaining service continuity
US16/227,176 US10694540B2 (en) 2013-12-27 2018-12-20 Method and device for maintaining service continuity

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
PCT/CN2013/090767 WO2015096160A1 (zh) 2013-12-27 2013-12-27 一种保持业务连续性的方法及设备
CNPCT/CN2013/090767 2013-12-27

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/194,116 Continuation US10206224B2 (en) 2013-12-27 2016-06-27 Method and device for maintaining service continuity

Publications (1)

Publication Number Publication Date
WO2015096270A1 true WO2015096270A1 (zh) 2015-07-02

Family

ID=53477418

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2013/090767 WO2015096160A1 (zh) 2013-12-27 2013-12-27 一种保持业务连续性的方法及设备
PCT/CN2014/071599 WO2015096270A1 (zh) 2013-12-27 2014-01-27 一种保持业务连续性的方法及设备

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/090767 WO2015096160A1 (zh) 2013-12-27 2013-12-27 一种保持业务连续性的方法及设备

Country Status (6)

Country Link
US (2) US10206224B2 (zh)
EP (2) EP3373613B1 (zh)
JP (2) JP6480459B2 (zh)
KR (1) KR101815409B1 (zh)
CN (2) CN105850161B (zh)
WO (2) WO2015096160A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017066952A1 (en) 2015-10-22 2017-04-27 Telefonaktiebolaget Lm Ericsson (Publ) Mbms switching improvement

Families Citing this family (41)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104954994A (zh) * 2014-03-26 2015-09-30 电信科学技术研究院 一种组通信业务中断处理方法及处理装置
CN104955065A (zh) * 2014-03-31 2015-09-30 北京三星通信技术研究有限公司 进行用户统计的方法、暂停数据传输的方法和装置
CN105635984B (zh) * 2014-11-07 2020-06-09 中兴通讯股份有限公司 指示信息处理方法及装置
US9949236B2 (en) * 2014-12-12 2018-04-17 Qualcomm Incorporated Traffic advertisement in neighbor aware network (NAN) data path
US10820314B2 (en) 2014-12-12 2020-10-27 Qualcomm Incorporated Traffic advertisement in neighbor aware network (NAN) data path
US10827484B2 (en) 2014-12-12 2020-11-03 Qualcomm Incorporated Traffic advertisement in neighbor aware network (NAN) data path
EP4109985B1 (en) * 2015-04-07 2024-04-17 Nokia Solutions and Networks Oy Network location reporting for broadcast bearer management
EP3409035B1 (en) * 2016-01-28 2021-03-17 Nokia Solutions and Networks Oy Dynamic switching of streaming service between broadcast and unicast delivery
WO2018066905A1 (ko) * 2016-10-07 2018-04-12 엘지전자 주식회사 V2x 통신을 수행하는 방법 및 장치
CN112073205B (zh) * 2016-11-01 2024-05-14 瑞典爱立信有限公司 服务中断报告
JP7272093B2 (ja) * 2019-04-25 2023-05-12 株式会社三洋物産 遊技機
JP7307320B2 (ja) * 2019-04-25 2023-07-12 株式会社三洋物産 遊技機
JP7272094B2 (ja) * 2019-04-25 2023-05-12 株式会社三洋物産 遊技機
JP7272095B2 (ja) * 2019-04-25 2023-05-12 株式会社三洋物産 遊技機
JP7275914B2 (ja) * 2019-06-27 2023-05-18 株式会社三洋物産 遊技機
JP7275909B2 (ja) * 2019-06-27 2023-05-18 株式会社三洋物産 遊技機
JP7275908B2 (ja) * 2019-06-27 2023-05-18 株式会社三洋物産 遊技機
JP7275912B2 (ja) * 2019-06-27 2023-05-18 株式会社三洋物産 遊技機
JP7275911B2 (ja) * 2019-06-27 2023-05-18 株式会社三洋物産 遊技機
JP7275915B2 (ja) * 2019-06-27 2023-05-18 株式会社三洋物産 遊技機
JP7275916B2 (ja) * 2019-06-27 2023-05-18 株式会社三洋物産 遊技機
JP7275910B2 (ja) * 2019-06-27 2023-05-18 株式会社三洋物産 遊技機
JP7275913B2 (ja) * 2019-06-27 2023-05-18 株式会社三洋物産 遊技機
JP7302372B2 (ja) * 2019-08-22 2023-07-04 株式会社三洋物産 遊技機
JP7302373B2 (ja) * 2019-08-22 2023-07-04 株式会社三洋物産 遊技機
JP7307330B2 (ja) * 2019-08-22 2023-07-12 株式会社三洋物産 遊技機
JP7302375B2 (ja) * 2019-08-22 2023-07-04 株式会社三洋物産 遊技機
JP7302376B2 (ja) * 2019-08-22 2023-07-04 株式会社三洋物産 遊技機
JP7302377B2 (ja) * 2019-08-22 2023-07-04 株式会社三洋物産 遊技機
JP7302378B2 (ja) * 2019-08-22 2023-07-04 株式会社三洋物産 遊技機
JP7302374B2 (ja) * 2019-08-22 2023-07-04 株式会社三洋物産 遊技機
JP7302379B2 (ja) * 2019-08-23 2023-07-04 株式会社三洋物産 遊技機
JP7307331B2 (ja) * 2019-08-23 2023-07-12 株式会社三洋物産 遊技機
JP7342586B2 (ja) * 2019-10-03 2023-09-12 株式会社三洋物産 遊技機
JP7342588B2 (ja) * 2019-10-03 2023-09-12 株式会社三洋物産 遊技機
JP7342587B2 (ja) * 2019-10-03 2023-09-12 株式会社三洋物産 遊技機
JP7342584B2 (ja) * 2019-10-03 2023-09-12 株式会社三洋物産 遊技機
JP7342589B2 (ja) * 2019-10-03 2023-09-12 株式会社三洋物産 遊技機
JP7342585B2 (ja) * 2019-10-03 2023-09-12 株式会社三洋物産 遊技機
TWI704819B (zh) * 2019-10-05 2020-09-11 財團法人工業技術研究院 維持傳輸服務連續性的方法及服務中心
CN115396825B (zh) * 2020-04-15 2024-04-23 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102651852A (zh) * 2011-02-28 2012-08-29 中兴通讯股份有限公司 一种多媒体广播多播业务连续接收的方法和装置
CN103026642A (zh) * 2010-07-26 2013-04-03 韩国电子通信研究院 用于使用上行链路传送控制信号的系统
CN103202040A (zh) * 2010-11-08 2013-07-10 日本电气株式会社 经由单播或广播/多播提供mbms服务的通信系统

Family Cites Families (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI321918B (en) * 2002-08-07 2010-03-11 Interdigital Tech Corp Channel switching for support of multlmedia broadcast and multicast services
CN1266898C (zh) * 2004-03-29 2006-07-26 华为技术有限公司 一种实现多媒体广播/组播服务业务激活的方法
EP2161862A1 (en) * 2007-06-19 2010-03-10 Panasonic Corporation Radio transmission method, radio reception method, radio transmission/reception method, radio transmission device, radio reception device, radio transmission/reception system, base station device, and communication terminal device
US8600291B2 (en) * 2009-02-12 2013-12-03 Qualcomm Incorporated Multiple service management
CN101877823B (zh) * 2009-04-28 2012-09-26 电信科学技术研究院 一种多播广播业务的调度方法及装置
US8477702B2 (en) * 2009-04-28 2013-07-02 Electronics And Telecommunications Research Institute Scheduling apparatus and method for multicast broadcast service
IN2012DN01791A (zh) * 2009-10-05 2015-06-05 Ericsson Telefon Ab L M
BR112012020138B1 (pt) * 2010-02-12 2021-02-02 Alcatel Lucent método para processamento de atualização de sessão de serviço mbms de serviço de transmissão/multidifusão de multimidia em uma rede de acesso por rádio ran
CN102264032B (zh) * 2010-05-26 2016-02-10 中兴通讯股份有限公司 多媒体广播组播业务控制信息的发送方法及装置
CN102291679B (zh) * 2010-06-18 2013-09-25 电信科学技术研究院 一种mbms承载释放通知的方法和设备
EP2568725B1 (en) * 2010-06-29 2016-01-13 ZTE Corporation Method and system for realizing user equipment to transmit counting response in multimedia broadcast multicast service
CN102387471B (zh) * 2010-08-31 2016-06-15 中兴通讯股份有限公司 一种mbms业务控制方法及系统
CN102026101B (zh) * 2011-01-14 2013-02-20 大唐移动通信设备有限公司 网络部署中继节点的场景下的mbms业务实现方法和设备
CN102651846B (zh) * 2011-02-24 2016-12-07 中兴通讯股份有限公司 Mbms业务发送方式切换的方法和系统
CN102695129B (zh) * 2011-03-21 2018-01-02 中兴通讯股份有限公司 确定挂起mbms业务重新恢复的方法及装置、用户设备
CN102724636B (zh) * 2011-03-30 2017-02-01 中兴通讯股份有限公司 一种mbms业务处理方法和系统
CN102740234B (zh) * 2011-04-12 2017-11-07 中兴通讯股份有限公司 一种mbms挂起方法、系统及mce
CN102769827A (zh) * 2011-05-02 2012-11-07 上海贝尔股份有限公司 发起mbms业务接收状态报告的方法和设备
CN102790948B (zh) 2011-05-17 2017-04-05 中兴通讯股份有限公司 一种指示mbms业务中断的方法、装置及用户设备
CN103124397B (zh) * 2011-11-18 2017-11-24 中兴通讯股份有限公司 保持集群业务连续性的处理方法及装置
US9820259B2 (en) 2012-05-04 2017-11-14 Qualcomm Incorporated Smooth transition between multimedia broadcast multicast service (MBMS) and unicast service by demand
US9674251B2 (en) 2013-06-17 2017-06-06 Qualcomm Incorporated Mediating content delivery via one or more services
US20160249183A1 (en) * 2013-10-23 2016-08-25 Lg Electronics Inc. Method of selectively transmitting mbms service level information in wireless communication system and apparatus therefor
JP6918613B2 (ja) 2017-07-20 2021-08-11 フリー工業株式会社 壁面構造および壁面の構築方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103026642A (zh) * 2010-07-26 2013-04-03 韩国电子通信研究院 用于使用上行链路传送控制信号的系统
CN103202040A (zh) * 2010-11-08 2013-07-10 日本电气株式会社 经由单播或广播/多播提供mbms服务的通信系统
CN102651852A (zh) * 2011-02-28 2012-08-29 中兴通讯股份有限公司 一种多媒体广播多播业务连续接收的方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3076690A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017066952A1 (en) 2015-10-22 2017-04-27 Telefonaktiebolaget Lm Ericsson (Publ) Mbms switching improvement
EP3366053A4 (en) * 2015-10-22 2019-05-22 Telefonaktiebolaget LM Ericsson (PUBL) MBMS SWITCHING IMPROVEMENT

Also Published As

Publication number Publication date
CN110392348A (zh) 2019-10-29
CN105850161B (zh) 2019-07-19
JP2017507524A (ja) 2017-03-16
EP3076690A1 (en) 2016-10-05
CN105850161A (zh) 2016-08-10
KR20160102281A (ko) 2016-08-29
KR101815409B1 (ko) 2018-01-04
WO2015096160A1 (zh) 2015-07-02
US10694540B2 (en) 2020-06-23
US20190124679A1 (en) 2019-04-25
CN110392348B (zh) 2021-11-19
JP2019083572A (ja) 2019-05-30
US20160309522A1 (en) 2016-10-20
EP3373613A1 (en) 2018-09-12
EP3373613B1 (en) 2020-04-15
EP3076690A4 (en) 2016-11-30
US10206224B2 (en) 2019-02-12
EP3076690B1 (en) 2018-03-14
JP6480459B2 (ja) 2019-03-13
JP6643510B2 (ja) 2020-02-12

Similar Documents

Publication Publication Date Title
WO2015096270A1 (zh) 一种保持业务连续性的方法及设备
EP2568725B1 (en) Method and system for realizing user equipment to transmit counting response in multimedia broadcast multicast service
JP5789287B2 (ja) 無線通信システムにおけるマルチメディアブロードキャスト・マルチキャストサービスのためのマルチセル協調
EP2659706B1 (en) Methods and apparatus for managing resource utilization in a long term evolution communication system
JP2007536785A (ja) 無線通信システムにおける1対多サービスに関する制御情報通知の送受信方法
WO2011018037A1 (zh) 一种配置mbms控制信息的方法、设备和系统
WO2009100668A1 (zh) 一种触发资源配置的方法、装置及系统
WO2012092819A1 (zh) Mbms业务的同步计数方法和设备
WO2014201695A1 (zh) eMBMS管理方法、多媒体广播组播业务协调实体和基站
CN104301931A (zh) 拥塞/过载的控制方法,系统,装置和基站
WO2016161655A1 (zh) 一种多播业务传输装置及方法
CN103200533A (zh) 一种集群短消息业务的实现方法
EP3217723B1 (en) Multimedia broadcast multicast communication method, device and system
WO2022205570A1 (zh) 无线通信方法、终端设备和网络设备
WO2016026137A1 (zh) Mbms中群组业务数据的传输方法、基站和用户设备
CN114173375A (zh) 一种流量控制方法及装置
US11140656B2 (en) Paging in a group communications system
WO2015013925A1 (zh) 一种控制服务质量的方法及装置
CN113347576B (zh) 一种mbms辅助信息的上报方法、装置及存储介质
CN102802123A (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: 14873191

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2016543116

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2014873191

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2014873191

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 20167020051

Country of ref document: KR

Kind code of ref document: A