WO2012116536A1 - 一种多媒体广播多播业务连续接收的方法和装置 - Google Patents
一种多媒体广播多播业务连续接收的方法和装置 Download PDFInfo
- Publication number
- WO2012116536A1 WO2012116536A1 PCT/CN2011/077573 CN2011077573W WO2012116536A1 WO 2012116536 A1 WO2012116536 A1 WO 2012116536A1 CN 2011077573 W CN2011077573 W CN 2011077573W WO 2012116536 A1 WO2012116536 A1 WO 2012116536A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service
- unicast
- mbms service
- mbms
- access
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
- H04L65/611—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for multicast or broadcast
Definitions
- the present invention relates to multimedia communication technologies, and in particular, to a method and apparatus for continuously receiving multimedia broadcast multicast services. Background technique
- the 3rd Generation Partnership Project 3rd Generation Partnership Project proposes Multimedia Broadcast Multicast Service (MBMS), which is a data source to multiple
- MBMS Multimedia Broadcast Multicast Service
- the technology for transmitting data by the target mobile terminal realizes the sharing of resources of the network (including the core network and the access network), and improves the utilization of network resources (especially air interface resources).
- the MBMS service defined by 3GPP can not only realize plain text low-rate message class multicast and broadcast, but also realize high-speed multimedia service broadcast and multicast, and provide a variety of rich video, audio and multimedia services, which undoubtedly conforms to the future.
- the trend of mobile data development provides a better business prospect for the development of 3G.
- MBMS technology has been introduced in Release 9 (R9, Release 9) LTE systems and has been enhanced in Release 10 (R10, ReleaselO).
- the control signaling of the MBMS service is transmitted separately from the user data, which is called the control plane (CP, respectively).
- Control Plane and User Plane (UP, User Plane).
- the control plane controls the transmission of user plane data by controlling the start, update, and end of the service, and implements basic MBMS service transmission.
- the MBMS service is sent in the MBMS Single Frequency Network (MBSFN) area of a fixed size (which can be initially configured by the operator but cannot be dynamically changed).
- MMSFN MBMS Single Frequency Network
- an MBMS Counting mechanism is introduced. The specific implementation of this mechanism is as follows:
- Multi-cell/multicast Coordination Entity decides to initiate the MBMS service Counting process. The decision can be triggered according to the rules defined by the MCE, or by the operator through OAM (Operation Administration and Maintenance).
- the MCE sends an MBMS Service Counting Request message to the evolved NodeB (eNB, evolved NodeB) through the M2 interface.
- the message is a class 1 message
- the class 1 message is a message 0 with feedback
- the eNB After receiving the MBMS Service Counting Request message, the eNB sends an MBMS Service Counting Request message on the MBMS Control Channel (MCCH, MBMS Control Channel) of the corresponding MBSFN area.
- MCCH MBMS Control Channel
- the user equipment After receiving the MBMS Service Counting Request message from the eNB, the user equipment (UE, User Equipment) detects whether the temporary mobile group identity (TMGI, Temporary Mobile Group Identity) of the MBMS service that it is receiving is included, if it contains The TMGI of the MBMS service that is being received by itself is fed back to the eNB with its corresponding index number (index ) according to the order in which the TMGI appears in the MBMS Service Counting Request message.
- TMGI Temporary Mobile Group Identity
- the eNB collects the feedback result of all the UEs in the cell, and after the MBMS Counting process on the MCCH ends (generally, one MCCH modification period), the result is sent to the MCE through the MBMS Service Counting Results Report message on the M2 interface. . 6.
- the MCE decides whether to activate/deactivate the service according to the result of counting the MBMS service, that is, the number of UEs that are receiving the service or/and interested in the service.
- the UE receiving the MBMS service may be in one of two states, one is a RRC (Radio Resources Control) connection state (referred to as a connected state), and the other is an RRC idle state (referred to as an idle state).
- RRC Radio Resources Control
- the UE is in the connected state.
- the UE in the idle state does not establish an RRC connection with the network side, and the UE in the connected state establishes an RRC connection with the network side.
- the current Counting mechanism only counts the receiving state of the MBMS service in the RRC connected state, and does not consider the receiving state of most UEs in the RRC idle state, which may cause some misjudgment problems. For example, when a certain UE is in an idle state at a certain moment and is receiving or interested in receiving an MBMS service, but since only the connected UE is counted, the result of the statistics is that the service is not activated or deactivated. In this case, the reception of a large number of UEs in the idle state that are receiving or interested in the MBMS service will be interrupted and the MBMS service cannot be continued to be received. In addition, even if only a small number of UEs cause service interruption due to inactivity or deactivation of the service, it will be unable to continue to receive services, thereby greatly reducing the user experience, which is undesired by operators.
- the RMS version of the MBMS technology uses the semi-static MBSFN mode to transmit the MBMS service.
- the size of the transmission area is unchanged after the initial configuration of the carrier.
- the UE can only receive the MBMS service in the fixed MBSFN area.
- the MBMS service may also be preempted by the higher priority service to transmit the resource, thereby stopping the service transmission; or the UE leaving the effective area of the MBMS service will also stop the MBMS service from being sent. All of the above will cause the UE to continue to receive MBMS services, thereby reducing the user experience. Summary of the invention
- the main object of the present invention is to provide a method and apparatus for continuously receiving a multimedia broadcast multicast service, which ensures that the receiving state of a user who is receiving an MBMS service is not interrupted, and improves the user's service experience.
- the invention provides a method for continuous reception of an MBMS service, the method comprising:
- the UE After detecting that the MBMS service being received is stopped, the UE initiates the access of the unicast service corresponding to the MBMS service according to the correspondence between the MBMS service and the unicast service, and continues to receive the unicast by using the unicast service.
- MBMS business After detecting that the MBMS service being received is stopped, the UE initiates the access of the unicast service corresponding to the MBMS service according to the correspondence between the MBMS service and the unicast service, and continues to receive the unicast by using the unicast service.
- the detecting that the MBMS service being received is stopped is: the UE does not detect the configuration information of the MBMS service being received in the corresponding MCCH;
- the UE cannot read the resource location and channel information of the MCCH corresponding to the MBMS service being received on the broadcast control channel (BCCH, Broadcast Control Channel); or the UE cannot find the control information of the MBSFN.
- the unicast service corresponding to the MBMS service is initiated according to the corresponding relationship between the MBMS service and the unicast service, and the following is: reading the MBMS user service description (USD, User Service Description) Obtaining the access information of the corresponding unicast of the MBMS service, and sending a scheduling and access request to the network according to the obtained access information of the corresponding unicast of the MBMS service, requesting access to the MBMS service content The same unicast business.
- USD User Service Description
- the method further includes: the UE determining to continue receiving the stopped MBMS service by using the unicast.
- the UE determines to continue to receive the stopped MBMS service by using the unicast: the UE sends a request to the application layer to continue receiving the stopped MBMS service by using the unicast, and determines, by the application layer, that the handover to the unicast continues to receive the MBMS business;
- the UE determines, according to the policy decision set by itself, that the handover to the unicast continues to receive the MBMS service;
- the UE determines, when receiving the message that the user continues to receive the service by using the unicast, to switch to the unicast to continue receiving the MBMS service;
- the UE determines that the stopped MBMS service is not normally ended, it is determined that the handover to the unicast continues to receive the MBMS service.
- the method further includes: after receiving the instruction that the MBMS service sent by the network is switched to the unicast, the UE starts to initiate the access of the unicast service corresponding to the MBMS service in advance.
- the present invention provides a device for continuously receiving a multimedia broadcast multicast service, the device comprising: a detecting module, an access module, and a unicast receiving module;
- a detecting module configured to notify the access module after detecting that the MBMS service being received is stopped
- An access module configured to initiate, according to the correspondence between the MBMS service and the unicast service, the unicast service that has a corresponding relationship with the MBMS service;
- the unicast receiving module is configured to continue to receive the MBMS service by using the unicast after the access module accesses the unicast service.
- the detecting module is specifically configured to detect, in the corresponding MCCH, configuration information of the MBMS service that is being received, to learn that the MBMS service that is being received is stopped, or that the receiving of the MBMS service is not received on the BCCH.
- the resource location and channel information of the MCCH corresponding to the MBMS service, and it is learned that the MBMS service being received is stopped;
- the MBMS service is not found in the MBSFN control information.
- the MBMS service being received stops transmitting.
- the device further includes: a switching instruction module, configured to notify the access module after receiving the instruction that the MBMS service sent by the network is switched to the unicast.
- the access module is specifically configured to read the MBMS USD, obtain the access information of the corresponding unicast of the MBMS service, and access the network according to the obtained unicast access information of the MBMS service. Sending a scheduling and access request, requesting access to the same unicast service as the MBMS service content, and notifying the unicast receiving module after the access and scheduling request is successful.
- the present invention provides a method and apparatus for continuously receiving a multimedia broadcast multicast service. After detecting that the MBMS service being received is stopped, the UE initiates the MBMS service according to the correspondence between the MBMS service and the unicast service. The access of the unicast service with the corresponding relationship continues to receive the MBMS service through unicast; in this way, it can ensure that the receiving state of the user who is receiving the MBMS service is not interrupted, and the user's service experience is improved.
- FIG. 1 is a schematic flow chart of a method for implementing continuous reception of a multimedia broadcast multicast service according to the present invention
- FIG. 2 is a schematic structural diagram of an apparatus for implementing continuous reception of a multimedia broadcast multicast service according to the present invention
- FIG. 3 is a schematic flowchart of a method for continuously receiving a multimedia broadcast multicast service according to an embodiment of the present invention
- FIG. 4 is a schematic flowchart diagram of a method for implementing continuous reception of a multimedia broadcast multicast service according to Embodiment 2 of the present invention. detailed description
- the basic idea of the present invention is: after detecting that the MBMS service being received is stopped, the UE initiates access of the unicast service corresponding to the MBMS service according to the correspondence between the MBMS service and the unicast service, The MBMS service continues to be received through unicast.
- the present invention implements a method for continuously receiving multimedia broadcast multicast services. As shown in FIG. 1, the method includes the following steps:
- Step 101 The UE detects that the MBMS service being received is stopped.
- the MBMS service is stopped.
- the network performs statistics on the service, it is found that the UE that is receiving the service or the number of UEs interested in the service is small, and the network deactivates or does not activate the service, resulting in
- the MBMS service is stopped from being sent by the MBSFN mode; or because the UE moves out of the MBSFN area where the MBMS service is being received or the effective transmission area of the MBMS service, the UE cannot continue to receive the service, and the service passively stops transmitting; or The service is preempted by other higher-priority services, causing the service to stop, etc.; of course, for other network side to stop the MBMS service being sent or other non-UE reasons, the UE cannot continue to receive the MBMS through MBSFN.
- the case of the service may also be included in the range in which the MBMS service being received in this step is stopped;
- the UE can detect that the MBMS service being received is stopped in the following manner: 1.
- the UE does not detect the configuration information of the MBMS service being received in the corresponding MCCH, and the corresponding MCCH refers to the configuration of the MBMS service that the UE is receiving.
- the information is transmitted on the MCCH; or the UE cannot read the resource location and channel information of the MCCH corresponding to the MBMS service being received on the BCCH, and the channel information may be one or more of the following information: MCCH corresponding Scheduling information, MCCH modification period, repetition period, frequency offset and subframe configuration, modulation and coding scheme (MCS, Modulation and Coding Scheme) corresponding to subframe configuration, subframe position of MCCH change notification, physical downlink control channel bit Mapping between (PDCCH bit, Physical Downlink Control Channel bit) and MCCH
- MCS Modulation and Coding Scheme
- the UE sends RRC signaling, layer 1 (L1, Layer 1) signaling or MAC layer signaling according to the network, and learns that the MBMS service being received stops transmitting.
- layer 1 L1, Layer 1
- MAC layer MAC layer
- the step further includes: after receiving the instruction that the MBMS service sent by the network is switched to the unicast, the UE starts to initiate the access of the unicast service corresponding to the MBMS service, that is, directly performing step 104, thereby reducing the service.
- Interrupt delay after receiving the instruction that the MBMS service sent by the network is switched to the unicast, the UE starts to initiate the access of the unicast service corresponding to the MBMS service, that is, directly performing step 104, thereby reducing the service.
- the access of the unicast service that is associated with the MBMS service is initiated in advance, and the UE may not wait until it detects that the MBMS service is stopped after receiving the instruction to switch the MBMS service sent by the network to the unicast.
- the process of accessing the unicast service corresponding to the MBMS service is initiated.
- Step 102 The UE initiates a determination whether to continue receiving the stopped MBMS service by unicast. If the determination result is yes, step 104 is performed; otherwise, step 103 is performed;
- the UE may send a request to the application layer to continue receiving the stopped MBMS service by using the unicast, and the application layer determines whether to switch to the unicast to continue receiving the service according to the setting of the unicast. If the determination result is yes, step 104 is performed; otherwise, , performing step 103;
- the UE may also determine whether to switch to unicast to continue receiving the service according to its pre-set policy. If the determination result is yes, go to step 104; otherwise, go to step 103;
- the UE may also report the user to the user, and the user decides whether to continue to receive the service through unicast.
- step 104 is performed; otherwise, step 103 is performed;
- the UE determines whether the stopped MBMS service is a normal end, if not normally, step 104 is performed; otherwise, step 103 is performed;
- the normal termination of the stopped MBMS service means that the current session of the MBMS service has been completely transmitted, and the network stops the transmission by performing an MBMS session end process;
- the determining whether the stopped MBMS service ends normally may be determined by whether to receive the end identifier of the MBMS service; or by using the RRC signaling sent by the network, such as the MBMS Session sto procedure; or by the application layer and the user.
- the unicast continuation of the unicast service is performed by the unicast peer-to-peer method, and the unicast service is the same as the MBMS service.
- the correspondence between the unicast service and the MBMS service being received can be obtained by querying MBMS USD;
- MBMS USD contains all the information that the UE accesses the service through unicast and MBSFN, such as Unicast Resource Identifier (URI), MBGI TMGI and IP multicast address, etc., which is convenient. Know the mapping relationship between unicast services and corresponding MBMS services.
- URI Unicast Resource Identifier
- MBGI TMGI IP multicast address
- this step is optional, that is, the step may not be performed in an actual application, and correspondingly, in the case where the step is not performed, the step 103 is not performed, and the step 104 is directly executed.
- Step 103 The UE stops receiving the MBMS service, releases related resources, and the process ends. Specifically, the UE ends the receiving of the MBMS service, and releases the related resources occupied by the MBMS service, and the process ends.
- Step 104 The UE acquires a correspondence between the MBMS service and the unicast service, and prepares to access the unicast service.
- the UE reads the MBMS USD, obtains the corresponding unicast access information of the MBMS service, and prepares to access the unicast service;
- the corresponding unicast access information refers to related information required for unicast service access in the MBMS USD, which is the same as the MBMS service content, such as unicast access URI, service or session ID, and the like.
- Information required for access In fact, as long as the UE starts to receive the MBMS service, it has MBMS USD, which contains all the information needed to access the multicast and unicast services, so as to obtain the corresponding unicast access URI and the corresponding session description protocol (SDP, a link of the Session Description Protocol and other corresponding unicast access information; the UE can learn related information for accessing the same unicast service as the MBMS service content, thereby accessing the unicast service .
- SDP session description protocol
- Step 105 The UE sends a scheduling and access request according to the correspondence between the MBMS service and the unicast service, and requests the network to send the MBMS service by using unicast.
- the UE sends a scheduling and access request to the network according to the obtained unicast access information of the MBMS service, and requests to access the same unicast service as the MBMS service content;
- the UE may apply for an uplink resource through a scheduling request (SR, Schedule Request), and send a scheduling and access request through a Buffer State Report (BSR), or may be performed by other methods, such as a physical uplink control channel (PUCCH, Physical).
- SR scheduling request
- BSR Buffer State Report
- PUCCH physical uplink control channel
- the Uplink Control Channel sends a scheduling and access request, requesting the network to send traffic through unicast.
- Step 106 Determine whether the scheduling and access request is successful, if successful, perform step 107; otherwise, perform step 108;
- the determining whether the scheduling and the access request are successful may be determined by using the feedback of the scheduling and the access request, or by monitoring whether the PDCCH has the downlink resource allocated for the UE, or by using the PDCCH or/and the MAC. Indicated by, or RRC signaling;
- a scheduling and access request timer may be set. After the scheduling and the access request are successfully determined, the timer is reset. When the timer expires, the scheduling and access request are considered to be unsuccessful, thus avoiding the UE. Multiple scheduling and access requests.
- Step 107 The UE receives the related scheduling and access information of the unicast service corresponding to the MBMS service, accesses the unicast service, and implements continuous reception of the MBMS service, and the process ends.
- the UE receives the corresponding corresponding to the MBMS service.
- the related scheduling and access information of the unicast service according to the indication of the related scheduling and access information, receive the unicast service on the corresponding downlink resource, and continue to receive the MBMS corresponding service through unicast, thereby implementing the MBMS service.
- the related scheduling and access information refers to the time-frequency resources, configuration information, and other UE access unicast services allocated by the network for the unicast service corresponding to the MBMS service.
- Required information such as session id, service id, etc.
- Step 108 The UE interrupts the access to the unicast service, ends the MBMS service reception, and the process ends. Specifically, the UE interrupts access to the unicast service, releases all related resources, and ends the MBMS service reception; all related resources refer to resources related to the UE receiving the MBMS service and resources related to the unicast service corresponding to the UE receiving the MBMS service.
- the step further includes: the UE sends a service scheduling and an access failure indication to the application layer or the user, indicating that the application layer or the user service access fails; or the UE sends a failure reason or a subsequent operation indication to the application layer or the user, for example, “interval time” After trying again, wait.
- the present invention further provides a device for continuously receiving a multimedia broadcast multicast service.
- the device includes: a detecting module 21, an access module 22, and a unicast receiving module 23;
- the detecting module 21 is configured to notify the access module 22 after detecting that the MBMS service being received is stopped;
- the access module 22 is configured to initiate, according to the correspondence between the MBMS service and the unicast service, access of a unicast service corresponding to the MBMS service;
- the unicast receiving module 23 is configured to: after the access module 22 accesses the unicast service, continue to receive the MBMS service by using unicast;
- the detecting module 21 is specifically configured to detect, in the corresponding MCCH, configuration information of the MBMS service that is being received, and learn that the MBMS service that is being received is stopped; or, the MBMS service corresponding to the MBMS service that is being received cannot be read on the BCCH.
- MCCH resource location and letter The information of the MBMS service that is being received is stopped; or the MBMS service that is being received is stopped by other means in the prior art, for example, the service ID of the MBMS service being received cannot be found in the related control information of the MBSFN.
- the method further includes: a switching instruction module 24, configured to notify the access module 22 after receiving an instruction to switch the MBMS service sent by the network to unicast;
- the access module 22 is specifically configured to: after receiving the notification of the detecting module 21, determine to continue to receive the stopped MBMS service by using the unicast, and initiate and perform according to the correspondence between the MBMS service and the unicast service.
- the MBMS service has a corresponding unicast service access;
- the access module 21 is configured to read the MBMS USD, obtain the access information of the corresponding unicast of the MBMS service, and send the scheduling and the network according to the obtained unicast access information of the MBMS service.
- the access request requesting access to the same unicast service as the MBMS service content, and after the access and scheduling request is successful, notifying the unicast receiving module 23;
- the access module 22 is further configured to: after the access and scheduling request fails, interrupt the access to the unicast service, release all related resources, and end the MBMS service reception; all related resources refer to resources related to the UE receiving the MBMS service and And receiving, by the UE, resources related to the unicast service corresponding to the MBMS service;
- the device further includes a reporting module 25, configured to send a service scheduling and access failure indication to the application layer or the user, prompting the application layer or the user service access to fail; or sending the failure reason or subsequent operation indication to the application layer or the user, such as " Try again after a period of time, etc.
- a reporting module 25 configured to send a service scheduling and access failure indication to the application layer or the user, prompting the application layer or the user service access to fail; or sending the failure reason or subsequent operation indication to the application layer or the user, such as " Try again after a period of time, etc.
- Embodiment 1 This embodiment is a method for implementing continuous reception of an MBMS service after the MBMS service that is being sent is stopped. As shown in FIG. 3, the method includes:
- Step 201 The UE detects that the MBMS service being received is stopped.
- the UE refers to a UE that is capable of receiving an MBMS service.
- the specific process of this step refer to step 101.
- Step 202 The UE determines whether the stopped MBMS service is a normal end, if it is normal, step 204 is performed; otherwise, step 203 is performed;
- Step 203 End the reception of the MBMS service, and the process ends.
- Step 204 The UE reads MBMS USD, and obtains access information of the corresponding unicast service of the MBMS service.
- Step 205 The UE sends a scheduling and access request to the network according to the obtained access information of the corresponding unicast service of the MBMS service, and requests the network to send the MBMS service by using unicast.
- the access information of the service refers to the related information required for the unicast service access of the MBMS service, such as the access URI, SDP, etc. of the MBMS service corresponding to the unicast service;
- the step of the access and the access request carrying the corresponding unicast service of the MBMS service further includes: the network preparing the unicast service for the UE according to the resource scheduling and the access policy, and allocating the time-frequency resource and the configuration information, The UE is notified of the allocated time-frequency resources and configuration information.
- Step 206 Determine whether the scheduling and access request is successful, if successful, perform step 208; otherwise, perform step 207;
- the determining whether the scheduling and the unicast access request are successful may be based on one or more of downlink information sent by the network, such as scheduling and access request response, PDCCH indication, MAC signaling, or RRC signaling. to make sure;
- This step can also set a scheduling and access request timer, in the scheduling and access request After the success is successful, the timer is reset. When the timer expires, the scheduling and access request are considered to be unsuccessful, thus avoiding multiple scheduling and access requests of the UE.
- Step 207 The UE interrupts the access to the unicast service, and ends the MBMS service, and the process ends.
- the method further includes: after the UE accesses the unicast service, releasing the original MBMS service receiving state, and the service-related context information, and receiving the service only through unicast; or saving the original MBMS service.
- Information such as MBMS USD, TMGI or multicast IP address, etc., is convenient for the network to deactivate the service activation or/and the UE that moves out of the MBSFN area to enter the MBSFN area again after switching to the MBSFN reception mode.
- the UE determines that the MBMS service is abnormally terminated, and then reads the corresponding information of the MBMS service corresponding to the unicast service in the MBMS USD, and accesses the information.
- the unicast enables the continuous reception of the MBMS service, so that after the MBMS service is deactivated or the UE moves out of the MBSFN area, the user who is receiving the MBMS service can continuously receive the MBMS service, thereby improving the continuity of the MBMS service reception. Increased user satisfaction.
- the application layer or the user participates in deciding whether to continue receiving the MBMS service through unicast, thereby implementing a method for continuously receiving the MBMS service.
- the method includes The following steps:
- Step 301 The UE detects that the MBMS service being received is stopped.
- Step 302 The UE sends a service interruption indication to the application layer or the user, and the service interruption indication indicates whether the service is continuously received through the unicast.
- the service interruption indication may be a special indicator or bit sent to the application layer, or a predefined indicator bit, and the user may Received an inquiry similar to "Whether to continue receiving services through unicast", indicating whether the user continues to receive services through unicast;
- the step may be directly processed according to an application layer or a preset policy of the user, for example, the preset policy is “continue to receive without receiving unicast after the MBMS service is interrupted”, or “when receiving. After the MBMS service is abnormally interrupted, it continues to receive by unicast; etc.
- the preset policy is “continue to receive without receiving unicast after the MBMS service is interrupted”, or “when receiving. After the MBMS service is abnormally interrupted, it continues to receive by unicast; etc.
- the preset policy is “continue to receive without receiving unicast after the MBMS service is interrupted”, or “when receiving. After the MBMS service is abnormally interrupted, it continues to receive by unicast; etc.
- the preset policy is “continue to receive without receiving unicast after the MBMS service is interrupted”, or “when receiving. After the MBMS service is abnormally interrupted, it continues to receive by unicast; etc.
- there are other similar preset policies depending on the user's settings.
- Step 303 Determine whether the application layer or the user indicates to continue receiving services through unicast. If the determination result is yes, go to step 305; otherwise, go to step 304;
- Step 304 The UE ends the MBMS service reception, and the process ends.
- the UE releases the resources and service contexts occupied by the MBMS service, and ends the MBMS service reception, and the process ends.
- Step 305 The UE reads MBMS USD, and obtains access information of the corresponding unicast service of the MBMS service.
- the UE reads the USD of the MBMS service, obtains the access URI of the unicast service corresponding to the MBMS service, and other required information, such as the SDP related to the unicast service. Links, etc.
- Step 306 The UE sends a scheduling and access request, and requests the network to send the service by using unicast. Specifically, the UE sends the scheduling request and the unicast access request to the network by using the access information of the corresponding unicast service of the MBMS service obtained from the MBMS, and requests to access the unicast service corresponding to the MBMS service.
- Step 307 Determine whether the scheduling and access request is successful, if the scheduling and access request is successful, go to step 308; otherwise, go to step 309;
- whether the scheduling and access request is successful may be determined according to one or more of downlink information sent by the network, such as scheduling and access request response, PDCCH indication, MAC signaling, or RRC signaling.
- Step 308 The UE receives the related scheduling and access information of the unicast service corresponding to the MBMS service, accesses the unicast service, and implements continuous reception of the MBMS service by using unicast, and the process ends;
- Step 309 The UE interrupts the access to the unicast service, and informs the user that the unicast access fails, ends the MBMS service reception, and the process ends.
- the UE after receiving the indication that the scheduling and the access request of the network is unsuccessful, the UE interrupts the unicast resource scheduling and the access request, releases the resources related thereto, and ends the receiving of the MBMS service;
- the indication that the scheduling and access request of the network is unsuccessful may be from a scheduling and access request response, or the network may notify the UE by using dedicated signaling or other signaling; or may also set a timer to determine in the scheduling and access request. After successful, the timer is reset, and when the timer expires, the scheduling and access request are considered to have failed.
- the UE may also release the receiving state of the MBMS service, and the context information related to the MBMS service, and receive the service only by using unicast; and may also save the information of the MBMS service.
- MBMS USD, TMGI or multicast IP address, etc. it is convenient to switch to MBSFN receiving mode later.
- the embodiment is directed to the case that the MBMS service that the user is receiving is stopped. In the manner of user participation, the MBMS service is continuously received through unicast, thereby ensuring the continuity of the MBMS service reception and improving the experience of the user receiving the service.
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本发明公开了一种多媒体广播多播(MBMS)业务连续接收的方法,用户设备(UE)在检测到正在接收的MBMS业务被停止后,根据所述MBMS业务与单播业务的对应关系,发起与所述MBMS业务有对应关系的单播业务的接入,通过单播继续接收所述MBMS业务;本发明同时还公开了一种多媒体广播多播业务连续接收的装置,通过本发明的方案,能够确保正在接收MBMS业务的用户的接收状态不会中断,提高用户的业务体验。
Description
一种多媒体广播多播业务连续接收的方法和装置 技术领域
本发明涉及多媒体通信技术, 尤其涉及一种多媒体广播多播业务连续 接收的方法和装置。 背景技术
随着 Internet的迅猛发展和大屏幕多功能移动终端的普及, 出现了大量 移动数据多媒体业务和各种高带宽多媒体业务, 如视频会议、 电视广播、 视频点播、 广告、 网上教育、 互动游戏等, 这一方面满足了移动用户多业 务的需求, 同时也为移动运营商带来了新的业务增长点。 这些移动数据多 媒体业务要求多个用户能够同时接收相同数据, 与一般的数据业务相比, 具有数据量大、 持续时间长、 时延敏感等特点。
为了有效地利用移动网络资源, 第三代合作伙伴计划 (3GPP , 3rd Generation Partnership Project ) 提出了多媒体广播多播业务 ( MBMS , Multimedia Broadcast Multicast Service ),该业务是一种从一个数据源向多个 目标移动终端传送数据的技术, 实现了网络(包括核心网和接入网) 资源 的共享, 提高了网络资源 (尤其是空中接口资源)的利用率。 3GPP定义的 MBMS业务不仅能够实现纯文本低速率的消息类组播和广播, 而且还能够 实现高速多媒体业务的广播和组播, 提供多种丰富的视频、 音频和多媒体 业务, 这无疑顺应了未来移动数据发展的趋势, 为 3G的发展提供了更好的 业务前景。
目前, 在版本 9 ( R9, Release 9 ) 的 LTE***中引入了 MBMS技术, 并在版本 10 ( R10, ReleaselO ) 中进行了加强。 在最初引进的 MBMS技术 中, MBMS业务的控制信令与用户数据分开传输, 分别称为控制面 (CP,
Control Plane )和用户面 (UP, User Plane )。 控制面通过控制业务的开始、 更新和结束, 来控制用户面数据的发送, 实现基本的 MBMS业务的发送。 MBMS 业务在固定大小 (可以由运营商初期配置, 但不可动态变化) 的 MBMS单频网 (MBSFN, MBMS Single Frequency Network ) 区域中发送。 在 R10版本中, 为了提高 MBMS***的资源利用率, 方便运营商管理, 引 入了 MBMS计数(Counting )机制。 该机制的具体实现方式如下:
1、多小区 /多播协作实体( MCE, Multi-cell/multicast Coordination Entity ) 决定发起 MBMS业务 Counting过程。 该决定可以根据 MCE预定义的规则 触发,也可以由运营商通过操作管理和维护( OAM, Operation Administration and Maintenance )发起。
2、 MCE通过 M2接口向演进型 NodeB ( eNB , evolved NodeB )发送 MBMS Service Counting Request message。 其中, 该 message为一个 class 1 message, 所述 class 1 message即带反馈的 message 0
3、 eNB接收到 MBMS Service Counting Request message后 , 在相应 MBSFN区域的 MBMS控制信道(MCCH, MBMS Control Channel )上发 送 MBMS Service Counting Request message。
4、用户设备( UE, User Equipment )在接收到来自 eNB的 MBMS Service Counting Request message之后, 检测其中是否包含自己正在接收的 MBMS 业务的临时移动群标识( TMGI, Temporary Mobile Group Identity ), 如果其 中包含自己正在接收的 MBMS 业务的 TMGI , 则根据 MBMS Service Counting Request message中该 TMGI出现的顺序, 向 eNB反馈其相应的索 引号 ( index )。
5、 eNB收集所属小区的所有 UE的反馈结果, 在 MCCH上的 MBMS Counting过程结束后 (一般为 1个 MCCH修改周期),将结果通过 M2接口 上的 MBMS Service Counting Results Report message上才艮给 MCE。
6、 MCE根据对 MBMS业务 Counting的结果, 即正在接收该业务或 / 和对该业务感兴趣的 UE的数目, 来决定是否激活 /去激活该业务。
接收 MBMS业务的 UE可以处于两种状态之一, 一种为无线资源控制 ( RRC, Radio Resources Control )连接态(简称为连接态), 另一种为 RRC 空闲态 (简称为空闲态)。 根据 UE是否正在接收单播业务, 可以判断正在 接收 MBMS业务的 UE是处于连接态还是处于空闲态。 当 UE在接收单播 业务时, UE处于连接态。 处于空闲态的 UE没有与网络侧建立 RRC连接, 处于连接态的 UE则与网络侧建立了 RRC连接。
但是, 目前的 Counting机制仅统计处于 RRC连接态 UE对 MBMS业 务的接收状态, 而没有考虑大部分处于 RRC空闲态的 UE的接收状态, 这 将会造成一些误判问题。 例如, 当某一时刻, 大部分 UE处于空闲态且正在 接收或感兴趣接收某 MBMS业务, 但是由于只统计连接态 UE, 因此统计 的结果是未激活或去激活该业务。 在这种情况下, 大量正在接收或感兴趣 该 MBMS 业务的处于空闲态的 UE 的接收将被中断, 无法继续接收该 MBMS业务。 此外, 即使只有少量的 UE因为业务的未激活或去激活而导 致业务中断, 也将导致其无法继续接收业务, 从而使得用户的体验大大地 降低, 而这是运营商所不愿看到的。
此外, R10版本的 MBMS技术采用半静态的 MBSFN方式发送 MBMS 业务, 其发送区域大小经过运营商初次配置后, 大小将保持不变, UE只能 在这个固定的 MBSFN区域内接收 MBMS业务。 当 UE因为移动或其他原 因,离开该 MBSFN区域内后,将不能继续接收业务,从而造成业务的中断。 除此之外, MBMS业务也可能被优先级更高的业务抢占发送资源, 从而停 止业务发送; 或者 UE 离开该 MBMS业务的有效区域, 也将造成 MBMS 业务的停止发送。 上面这些情况都将造成 UE无法继续接收 MBMS业务, 从而降低用户体验。
发明内容
有鉴于此, 本发明的主要目的在于提供一种多媒体广播多播业务连续 接收的方法和装置,确保正在接收 MBMS业务的用户的接收状态不会中断, 提高用户的业务体验。
为达到上述目的, 本发明的技术方案是这样实现的:
本发明提供的一种 MBMS业务连续接收的方法, 该方法包括:
UE在检测到正在接收的 MBMS业务被停止后,根据所述 MBMS业务 与单播业务的对应关系, 发起与所述 MBMS业务有对应关系的单播业务的 接入, 通过单播继续接收所述 MBMS业务。
上述方案中, 所述检测到正在接收的 MBMS业务被停止为: 所述 UE 在相应的 MCCH中检测不到正在接收的 MBMS业务的配置信息;
或者,所述 UE无法在广播控制信道( BCCH, Broadcast Control Channel ) 上读取到正在接收的 MBMS业务对应的 MCCH的资源位置和信道信息; 或者, 所述 UE在 MBSFN的控制信息中查找不到正在接收的 MBMS 业务的服务标识( Service ID )、 或会话标识( Session ID )、 或业务的 TMGI; 或者,所述 UE根据网络发送的 RRC信令、层 1信令或媒体接入( MAC , Media Access Control )层信令, 获知正在接收的 MBMS业务停止发送。
上述方案中, 所述根据所述 MBMS业务与单播业务的对应关系, 发起 与所述 MBMS业务有对应关系的单播业务的接入, 为: 读取 MBMS用户 业务描述(USD, User Service Description ), 获取所述 MBMS业务的相应 单播的接入信息, 根据获取的所述 MBMS业务的相应单播的接入信息, 向 网络发送调度和接入请求, 请求接入与所述 MBMS业务内容相同的单播业 务。
上述方案中, 所述 UE在检测到正在接收的 MBMS业务被停止后, 该 方法进一步包括: UE判定通过单播继续接收被停止的 MBMS业务。
上述方案中,所述 UE判定通过单播继续接收被停止的 MBMS业务为: UE向应用层发送通过单播继续接收被停止的 MBMS业务的请示, 通过应 用层确定切换到单播继续接收所述 MBMS业务;
或, UE根据自身预先设置的策略判断确定切换到单播继续接收所述 MBMS业务;
或, UE在收到用户决定通过单播继续接收该业务的消息时, 确定切换 到单播继续接收所述 MBMS业务;
或, UE判断被停止的 MBMS业务不是正常结束时, 确定切换到单播 继续接收所述 MBMS业务。
上述方案中, 该方法进一步包括: UE接收到网络发送的 MBMS业务 切换到单播的指令后, 提前开始发起与所述 MBMS业务有对应关系的单播 业务的接入。
本发明提供的一种多媒体广播多播业务连续接收的装置 , 该装置包括: 检测模块、 接入模块、 单播接收模块; 其中,
检测模块, 用于在检测到正在接收的 MBMS业务被停止后, 通知接入 模块;
接入模块, 用于根据所述 MBMS业务与单播业务的对应关系, 发起与 所述 MBMS业务有对应关系的单播业务的接入;
单播接收模块, 用于接入模块接入所述单播业务后, 通过单播继续接 收所述 MBMS业务。
上述方案中, 所述检测模块, 具体用于在相应的 MCCH中检测不到正 在接收的 MBMS业务的配置信息, 获知正在接收的 MBMS业务被停止; 或者, 无法在 BCCH上读取到正在接收的 MBMS业务对应的 MCCH 的资源位置和信道信息, 获知正在接收的 MBMS业务被停止;
或者, 在 MBSFN 的控制信息中查找不到正在接收的 MBMS 业务的
Service ID, 或 Session ID、 后业务的 TMGI, 获知正在接收的 MBMS业务 被停止;
或者, 根据网络发送的 RRC信令、 层 1信令或 MAC层信令, 获知正 在接收的 MBMS业务停止发送。
上述方案中, 该装置进一步包括: 切换指令模块, 用于接收到网络发 送的 MBMS业务切换到单播的指令后, 通知接入模块。
上述方案中, 所述接入模块, 具体用于读取 MBMS USD, 获取所述 MBMS业务的相应单播的接入信息,根据获取的所述 MBMS业务的相应单 播的接入信息, 向网络发送调度和接入请求, 请求接入与所述 MBMS业务 内容相同的单播业务, 当接入和调度请求成功后, 通知单播接收模块。
本发明提供了一种多媒体广播多播业务连续接收的方法和装置 , UE在 检测到正在接收的 MBMS业务被停止后, 根据所述 MBMS业务与单播业 务的对应关系, 发起与所述 MBMS业务有对应关系的单播业务的接入, 通 过单播继续接收所述 MBMS业务; 如此, 能够确保正在接收 MBMS业务 的用户的接收状态不会中断, 提高用户的业务体验。 附图说明
图 1 为本发明实现一种多媒体广播多播业务连续接收的方法的流程示 意图;
图 2为本发明实现一种多媒体广播多播业务连续接收的装置的结构示 意图;
图 3 为本发明实施例一实现多媒体广播多播业务连续接收的方法的流 程示意图;
图 4为本发明实施例二实现多媒体广播多播业务连续接收的方法的流 程示意图。
具体实施方式
本发明的基本思想是: UE在检测到正在接收的 MBMS业务被停止后, 根据所述 MBMS业务与单播业务的对应关系, 发起与所述 MBMS业务有 对应关系的单播业务的接入, 通过单播继续接收所述 MBMS业务。
下面通过附图及具体实施例对本发明做进一步的详细说明。
本发明实现一种多媒体广播多播业务连续接收的方法, 如图 1 所示, 该方法包括以下几个步驟:
步驟 101 : UE检测到正在接收的 MBMS业务被停止;
本步驟中, 所述 MBMS业务被停止是指网络对该业务进行统计之后, 发现正在接收该业务的 UE或对该业务感兴趣的 UE数目较少, 网络将该业 务去激活或未激活, 导致该 MBMS业务被停止通过 MBSFN方式发送; 或 由于 UE移出正在接收的 MBMS业务所在的 MBSFN区域或者该 MBMS业 务的有效发送区域,导致 UE无法继续接收该业务,该业务被动的停止发送; 或由于该业务被其他优先级更高的业务抢占发送资源, 导致该业务发送停 止等; 当然, 对于其他网络侧中止正在发送的 MBMS业务或其他非 UE原 因造成的、 UE无法通过 MBSFN的方式继续接收该 MBMS业务的情况, 也可以包含在本步驟的正在接收的 MBMS业务被停止的范围内;
UE可以通过以下方式检测到正在接收的 MBMS业务被停止: 一、 UE在相应的 MCCH中检测不到正在接收的 MBMS业务的配置信 息, 所述相应的 MCCH是指 UE正在接收的 MBMS业务的配置信息在该 MCCH上传输; 或者, UE无法在 BCCH上读取到正在接收的 MBMS业务 对应的 MCCH的资源位置和信道信息, 所述信道信息可以是下面一种或一 种以上的信息: MCCH对应调度信息、 MCCH修改周期、 重复周期、 频率 偏移量和子帧配置、子帧配置对应的调制和编码格式(MCS, Modulation and Coding Scheme ), MCCH 更改通知的子帧位置、 物理下行控制信道比特
( PDCCH bit, Physical Downlink Control Channel bit )与 MCCH之间的映
MBSFN的相关控制信息中查找不到正在接收的 MBMS业务的 Service ID、 或 Session ID、 或业务的 TMGI等。
二、 UE根据网络发送 RRC信令、 层 1 ( L1 , Layer 1 )信令或 MAC层 信令, 获知正在接收的 MBMS业务停止发送。
本步驟进一步包括: UE接收到网络发送的 MBMS业务切换到单播的 指令后, 提前开始发起与所述 MBMS业务有对应关系的单播业务的接入, 即直接执行步驟 104, 这样可以降低业务中断时延;
所述提前开始发起与 MBMS业务有对应关系的单播业务的接入, 是指 UE可以在收到网络发送的 MBMS业务切换到单播的指令后, 不必等到检 测到所述 MBMS业务被停止就开始发起与 MBMS业务有对应关系的单播 业务的接入过程。
步驟 102: UE发起是否通过单播继续接收被停止的 MBMS业务的判断, 如果判断结果为是, 则执行步驟 104; 否则, 执行步驟 103;
具体的, UE可以向应用层发送通过单播继续接收被停止的 MBMS业 务的请示, 应用层根据自身设置判断是否切换到单播继续接收该业务, 如 果判断结果为是, 则执行步驟 104; 否则, 执行步驟 103;
UE 也可以根据自身预先设置的策略判断是否切换到单播继续接收该 业务, 如果判断结果为是, 则执行步驟 104; 否则, 执行步驟 103;
UE还可以上报用户, 由用户决定是否通过单播继续接收该业务, 在收 到用户决定通过单播继续接收该业务的消息时, 执行步驟 104; 否则, 执行 步驟 103;
或者, UE判断被停止的 MBMS业务是否为正常结束, 如果不是正常 结束, 则执行步驟 104; 否则, 执行步驟 103;
所述被停止的 MBMS业务正常结束是指该 MBMS业务的当前 session 已经全部发送完毕, 由网络执行 MBMS会话结束过程而停止发送;
所述判断被停止的 MBMS 业务是否正常结束, 可以通过是否收到 MBMS业务的结束标识来判定;或者通过网络发送的 RRC信令,如 MBMS Session sto 过程进行判定; 或者通过应用层和用户判定。
所述通过单播继续接收业务是指对于停止后的 MBMS业务, UE无法 继续采用 MBSFN的方式接收该业务,则可以切换到单播点对点的方式接收 与该 MBMS 业务内容相同的单播业务, 该单播业务与正在接收的 MBMS 业务之间的对应关系, 可以通过查询 MBMS USD获得;
实际上, MBMS USD中包含 UE通过单播和 MBSFN方式接入该业务 的所有信息, 如单播统一资源标识符( URI , Uniform Resource Identifier )、 MBMS的 TMGI和 IP多播地址等,可以方便的知道单播业务与相应 MBMS 业务之间的映射关系。
在本实施例中, 本步驟为可选的, 即在实际应用中可以不执行本步驟, 相应的,在不执行本步驟的情况下,步驟 103也不执行,直接执行步驟 104。
步驟 103: UE停止接收 MBMS业务, 释放相关资源, 流程结束。 具体的, UE结束对该 MBMS业务的接收, 释放接收该 MBMS业务所 占用的相关资源, 该过程结束。
步驟 104: UE获取所述 MBMS业务与单播业务的对应关系, 准备接入 单播业务;
具体的 , UE读取 MBMS USD, 获取所述 MBMS业务的相应单播的接 入信息, 准备接入单播业务;
所述相应单播的接入信息, 是指 MBMS USD中, 与所述 MBMS业务 内容相同的单播业务接入所需要的相关信息, 如单播接入的 URI、 业务或 session ID等单播接入所需要的信息;
实际上, 只要 UE开始接收 MBMS业务, 就拥有 MBMS USD, 其中包 含接入多播和单播业务所需要的所有信息,从而获取相应的单播接入的 URI 和到相应会话描述协议(SDP, Session Description Protocol ) 的链接以及其 他所述相应的单播接入信息; UE 通过这些信息, 可以得知用于接入与 MBMS业务内容相同的单播业务的相关信息, 从而接入该单播业务。
步驟 105: UE根据所述 MBMS业务与单播业务的对应关系,发送调度 和接入请求, 请求网络通过单播发送所述 MBMS业务;
具体的, UE根据获取的所述 MBMS业务的相应单播的接入信息, 向 网络发送调度和接入请求, 请求接入与所述 MBMS业务内容相同的单播业 务;
这里, UE可以通过调度请求(SR, Schedule Request ) 申请上行资源, 通过緩存状态报告(BSR, Buffer State Report )发送调度和接入请求, 也可 以通过其他方式, 如物理上行控制信道(PUCCH, Physical Uplink Control Channel )等发送调度和接入请求, 请求网络通过单播发送业务。
步驟 106: 判断调度和接入请求是否成功,如果成功, 则执行步驟 107; 否则, 执行步驟 108;
本步驟中, 所述判断调度和接入请求是否成功, 可以通过调度和接入 请求的反馈来判断;或者通过监测 PDCCH是否有为 UE分配的下行资源来 确定; 或者通过 PDCCH或 /和 MAC上的指示、 或 RRC信令来确定;
本步驟还可以设置一个调度和接入请求定时器, 在调度和接入请求确 定成功后, 复位所述定时器, 当定时器超时后, 认为调度和接入请求失败, 这样, 避免了 UE的多次调度和接入请求。
步驟 107: UE接收所述 MBMS业务对应的单播业务的相关调度和接入 信息, 接入所述单播业务, 实现 MBMS业务的连续接收, 流程结束;
具体的, 当接入和调度请求成功后, UE接收所述 MBMS业务对应的
单播业务的相关调度和接入信息, 根据所述相关调度和接入信息的指示, 在相应的下行资源上接收所述单播业务, 实现通过单播继续接收 MBMS相 应业务, 从而实现 MBMS业务的连续接收, 流程结束; 所述相关调度和接 入信息是指网络为 UE接入所述 MBMS业务对应的单播业务所分配的时频 资源、 配置信息、 以及其他 UE接入单播业务所必需的信息, 如 session id, service id等。
步驟 108: UE中断接入单播业务, 结束 MBMS业务接收, 流程结束。 具体的, UE中断接入单播业务, 释放所有相关资源, 结束 MBMS业 务接收; 所有相关资源是指与 UE接收 MBMS业务相关的资源以及与 UE 接收该 MBMS业务对应单播业务相关的资源。
本步驟进一步包括: UE 向应用层或用户发送业务调度和接入失败指 示,提示应用层或用户业务接入失败; 或 UE向应用层或用户发送失败原因 或者后续操作指示, 如 "间隔一段时间后再次尝试" 等。
为了实现上述方法, 本发明还提供一种多媒体广播多播业务连续接收 的装置, 如图 2所示, 该装置包括: 检测模块 21、 接入模块 22、 单播接收 模块 23; 其中,
检测模块 21 , 用于在检测到正在接收的 MBMS业务被停止后, 通知接 入模块 22;
接入模块 22, 用于根据所述 MBMS业务与单播业务的对应关系,发起 与所述 MBMS业务有对应关系的单播业务的接入;
单播接收模块 23 , 用于接入模块 22接入所述单播业务后, 通过单播继 续接收所述 MBMS业务;
所述检测模块 21 , 具体用于在相应的 MCCH 中检测不到正在接收的 MBMS业务的配置信息, 获知正在接收的 MBMS业务被停止; 或者, 无法 在 BCCH上读取到正在接收的 MBMS业务对应的 MCCH的资源位置和信
道信息, 获知正在接收的 MBMS业务被停止; 或者, 通过现有技术中的其 他方式获知正在接收的 MBMS业务被停止, 如在 MBSFN的相关控制信息 中查找不到正在接收的 MBMS业务的 Service ID、 或 Session ID、 或业务的 TMGI等, 获知正在接收的 MBMS业务被停止; 或者, 根据网络发送 RRC 信令、 层 1信令或 MAC层信令, 获知正在接收的 MBMS业务停止发送; 该装置进一步包括: 切换指令模块 24, 用于接收到网络发送的 MBMS 业务切换到单播的指令后, 通知接入模块 22;
所述接入模块 22, 具体用于在收到检测模块 21的通知后, 判定通过单 播继续接收被停止的 MBMS业务后, 根据所述 MBMS业务与单播业务的 对应关系, 发起与所述 MBMS业务有对应关系的单播业务的接入;
所述接入模块 21 , 具体用于读取 MBMS USD, 获取所述 MBMS业务 的相应单播的接入信息, 根据获取的所述 MBMS业务的相应单播的接入信 息, 向网络发送调度和接入请求, 请求接入与所述 MBMS业务内容相同的 单播业务, 当接入和调度请求成功后, 通知单播接收模块 23;
所述接入模块 22, 进一步用于在接入和调度请求失败后, 中断接入单 播业务, 释放所有相关资源, 结束 MBMS业务接收; 所有相关资源是指与 UE接收 MBMS业务相关的资源以及与 UE接收该 MBMS业务对应单播业 务相关的资源;
该装置进一步包括上报模块 25, 用于向应用层或用户发送业务调度和 接入失败指示, 提示应用层或用户业务接入失败; 或向应用层或用户发送 失败原因或者后续操作指示, 如 "间隔一段时间后再次尝试" 等;
所述接入模块 22, 进一步还用于在接入和调度请求失败后, 通知上报 模块 25。 实施例一
本实施例是针对正在发送的 MBMS业务被停止后实现 MBMS业务连 续接收的方法, 如图 3所示, 该方法包括:
步驟 201: UE检测到正在接收的 MBMS业务被停止;
这里, 所述 UE指有能力接收 MBMS业务的 UE; 本步驟具体过程参 见步驟 101。
步驟 202: UE判断被停止的 MBMS业务是否为正常结束,如果为正常 结束, 则执行步驟 204; 否则, 执行步驟 203;
步驟 203: 结束该 MBMS业务的接收, 流程结束;
步驟 204: UE读取 MBMS USD, 获取所述 MBMS业务的相应单播业 务的接入信息;
步驟 205: UE根据获得的所述 MBMS业务的相应单播业务的接入信息, 向网络发送调度和接入请求, 请求网络通过单播发送所述 MBMS业务; 本步驟中,所述相应单播业务的接入信息是指 UE获取的与所述 MBMS 业务内容相同的单播业务接入所需要的相关信息, 如所述 MBMS业务对应 单播业务的接入 URI、 SDP等;
所述调度和接入请求携带所述 MBMS 业务的相应单播业务的接入信 本步驟进一步包括: 网络根据资源调度和接入策略, 为 UE准备单播业 务, 分配时频资源和配置信息, 并将分配的时频资源和配置信息通知 UE。
步驟 206: 判断调度和接入请求是否成功,如果成功, 则执行步驟 208; 否则, 执行步驟 207;
本步驟中, 所述判断调度和单播接入请求是否成功, 可以根据网络发 送的下行信息, 如调度和接入请求响应、 PDCCH指示、 MAC信令或 RRC 信令等中的一个或几个来确定;
本步驟还可以设置一个调度和接入请求定时器, 在调度和接入请求确
定成功后, 复位所述定时器, 当定时器超时后, 认为调度和接入请求失败, 这样, 避免了 UE的多次调度和接入请求。
步驟 207: UE中断接入单播业务, 结束 MBMS业务接收, 流程结束; 步驟 208: UE接收所述 MBMS业务对应的单播业务的相关调度和接入 信息, 接入所述单播业务, 实现通过单播对所述 MBMS业务的连续接收。
进一步的, 上述方法还包括: UE接入所述单播业务后, 释放原有的 MBMS业务的接收状态, 以及业务相关的上下文信息, 只通过单播接收业 务; 或者, 保存原有 MBMS业务的信息, 如 MBMS USD, TMGI或多播 IP 地址等, 为以后网络将去激活业务激活或 /和移出 MBSFN区域的 UE再次 进入所述 MBSFN区域后切换到 MBSFN接收方式提供方便。
可以看出, 本实施例针对正在发送的 MBMS业务被停止的情况, 通过 UE判断该 MBMS业务为非正常结束,然后读取 MBMS USD中所述 MBMS 业务对应单播业务的相应信息, 通过接入单播实现所述 MBMS业务的连续 接收, 从而保证了 MBMS业务去激活或 UE移出所述 MBSFN区域之后, 正在接收该 MBMS业务的用户可以连续接收该 MBMS业务,提高了 MBMS 业务接收的连续性, 增强了用户满意度。
实施例二
本实施例是针对正在接收的 MBMS业务被停止后, 由应用层或用户参 与决定是否通过单播继续接收所述 MBMS业务, 从而实现 MBMS业务连 续接收的方法, 如图 4所示, 该方法包括以下几个步驟:
步驟 301: UE检测到正在接收的 MBMS业务被停止;
步驟 302: UE向应用层或用户发送业务中断指示, 通过所述业务中断 指示询问是否通过单播继续接收业务;
本步驟中, 所述业务中断指示可以是向应用层发送的一个特殊的指示 符或比特, 或者一个预先定义好的指示位, 通过应用层的翻译, 用户可以
收到类似 "是否通过单播继续接收业务" 的询问, 请示用户是否通过单播 继续接收业务;
进一步的, 本步驟也可以直接根据应用层或用户预设的策略进行处理, 如预设的策略为"当正在接收的 MBMS业务中断后,不通过单播继续接收"、 或 "当正在接收的 MBMS业务非正常中断后, 通过单播继续接收" 等; 当 然, 也可以有其他类似的预先设定策略, 取决于用户的设定。
步驟 303: 判断应用层或用户是否指示通过单播继续接收业务, 如果判 断结果为是, 则执行步驟 305; 否则, 执行步驟 304;
具体的, 可以根据来自应用层或用户的指示, 判断是否通过单播继续 单播继续接收业务。
步驟 304: UE结束 MBMS业务接收, 流程结束。
具体的, 当来自应用层或用户的指示为 "不通过单播继续接收业务"; 或者应用层或用户预设的策略为 "MBMS业务中断后, 不通过单播继续接 收业务"; 或者其他类似的 "不通过单播继续接收业务" 的策略时, UE释 放所述 MBMS业务占用的资源和业务上下文, 结束所述 MBMS业务接收, 流程结束。
步驟 305: UE读取 MBMS USD, 获取所述 MBMS业务的相应单播业 务的接入信息;
具体的, 当应用层或用户的指示为 "通过单播继续接收业务"; 或者应 用层或用户预设的策略为 "MBMS业务中断后, 通过单播继续接收业务"; 或者其他类似的 "通过单播继续接收业务" 的策略时, UE读取所述 MBMS 业务的 USD, 获取该 MBMS业务对应单播业务的接入 URI, 以及其他一些 需要的信息, 如与该单播业务相关的 SDP的链接等。
步驟 306: UE发送调度和接入请求, 请求网络通过单播发送业务;
具体的, UE利用从 MBMS USD中获取的所述 MBMS业务的相应单播 业务的接入信息, 向网络发送调度请求和单播接入请求, 请求接入 MBMS 业务对应的单播业务。
步驟 307: 判断调度和接入请求是否成功, 如果调度和接入请求成功, 则执行步驟 308; 否则, 执行步驟 309;
具体的, 可以根据网络发送的下行信息, 如调度和接入请求响应、 PDCCH指示、 MAC信令或 RRC信令等中的一个或多个, 确定调度和接入 请求是否成功。
步驟 308: UE接收所述 MBMS业务对应的单播业务的相关调度和接入 信息, 接入所述单播业务, 实现通过单播对所述 MBMS业务的连续接收, 流程结束;
步驟 309: UE 中断接入单播业务, 并告知用户单播接入失败, 结束 MBMS业务接收, 流程结束;
具体的, 当 UE收到网络的调度和接入请求不成功的指示后, UE中断 单播的资源调度和接入请求, 释放与其有关的资源, 结束该 MBMS业务的 接收;
所述网络的调度和接入请求不成功的指示可以来自调度和接入请求响 应,也可以网络通过专用信令或其他信令通知 UE;或者还可以设置定时器, 在调度和接入请求确定成功后, 复位所述定时器, 当定时器超时则认为调 度和接入请求失败。
本实施例中, 在执行步驟 308之后, UE还可以释放所述 MBMS业务 的接收状态, 以及所述 MBMS业务相关的上下文信息, 只通过单播接收业 务; 也可以保存所述 MBMS业务的信息,如 MBMS USD, TMGI或多播 IP 地址等, 为以后切换到 MBSFN接收方式提供方便。
可以看出本实施例针对用户正在接收的 MBMS业务被停止的情况, 通
过用户参与的方式, 实现了通过单播继续接收所述 MBMS业务, 从而保证 了 MBMS业务接收的连续性, 提高了用户接收业务的体验。
以上所述, 仅为本发明的较佳实施例而已, 并非用于限定本发明的保 护范围。
Claims
1、 一种多媒体广播多播(MBMS )业务连续接收的方法, 其特征在于, 该方法包括:
用户设备(UE )在检测到正在接收的 MBMS业务被停止后, 根据所述 MBMS业务与单播业务的对应关系,发起与所述 MBMS业务有对应关系的 单播业务的接入, 通过单播继续接收所述 MBMS业务。
2、 根据权利要求 1所述的方法, 其特征在于, 所述检测到正在接收的 MBMS业务被停止为: 所述 UE在相应的 MBMS控制信道 ( MCCH ) 中检 测不到正在接收的 MBMS业务的配置信息;
或者, 所述 UE无法在广播控制信道(BCCH )上读取到正在接收的 MBMS业务对应的 MCCH的资源位置和信道信息;
或者, 所述 UE在 MBMS单频网( MBSFN )的控制信息中查找不到正 在接收的 MBMS业务的服务标识( Service ID )、 或会话标识( Session ID )、 或业务的临时移动群标识( TMGI );
或者,所述 UE根据网络发送的 RRC信令、层 1信令或媒体接入( MAC ) 层信令, 获知正在接收的 MBMS业务停止发送。
3、 根据权利要求 1 所述的方法, 其特征在于, 所述根据所述 MBMS 业务与单播业务的对应关系, 发起与所述 MBMS业务有对应关系的单播业 务的接入, 为: 读取 MBMS用户业务描述( USD ), 获取所述 MBMS业务 的相应单播的接入信息, 根据获取的所述 MBMS业务的相应单播的接入信 息, 向网络发送调度和接入请求, 请求接入与所述 MBMS业务内容相同的 单播业务。
4、 根据权利要求 1所述的方法, 其特征在于, 所述 UE在检测到正在 接收的 MBMS业务被停止后, 该方法进一步包括: UE判定通过单播继续 接收被停止的 MBMS业务。
5、 根据权利要求 4所述的方法, 其特征在于, 所述 UE判定通过单播 继续接收被停止的 MBMS业务为: UE向应用层发送通过单播继续接收被 停止的 MBMS 业务的请示, 通过应用层确定切换到单播继续接收所述 MBMS业务;
或, UE根据自身预先设置的策略判断确定切换到单播继续接收所述 MBMS业务;
或, UE在收到用户决定通过单播继续接收该业务的消息时, 确定切换 到单播继续接收所述 MBMS业务;
或, UE判断被停止的 MBMS业务不是正常结束时, 确定切换到单播 继续接收所述 MBMS业务。
6、 根据权利要求 1所述的方法, 其特征在于, 该方法进一步包括: UE 接收到网络发送的 MBMS业务切换到单播的指令后, 提前开始发起与所述 MBMS业务有对应关系的单播业务的接入。
7、 一种多媒体广播多播业务连续接收的装置, 其特征在于, 该装置包 括: 检测模块、 接入模块、 单播接收模块; 其中,
检测模块, 用于在检测到正在接收的 MBMS业务被停止后, 通知接入 模块;
接入模块, 用于根据所述 MBMS业务与单播业务的对应关系, 发起与 所述 MBMS业务有对应关系的单播业务的接入;
单播接收模块, 用于接入模块接入所述单播业务后, 通过单播继续接 收所述 MBMS业务。
8、 根据权利要求 7所述的装置, 其特征在于, 所述检测模块, 具体用 于在相应的 MCCH中检测不到正在接收的 MBMS业务的配置信息, 获知 正在接收的 MBMS业务被停止;
或者, 无法在 BCCH上读取到正在接收的 MBMS业务对应的 MCCH 的资源位置和信道信息, 获知正在接收的 MBMS业务被停止; 或者, 在 MBSFN 的控制信息中查找不到正在接收的 MBMS 业务的 Service ID, 或 Session ID、 后业务的 TMGI, 获知正在接收的 MBMS业务 被停止;
或者, 根据网络发送的 RRC信令、 层 1信令或 MAC层信令, 获知正 在接收的 MBMS业务停止发送。
9、 根据权利要求 7所述的装置, 其特征在于, 该装置进一步包括: 切 换指令模块, 用于接收到网络发送的 MBMS业务切换到单播的指令后, 通 知接入模块。
10、 根据权利要求 7所述的装置, 其特征在于, 所述接入模块, 具体 用于读取 MBMS USD, 获取所述 MBMS业务的相应单播的接入信息, 根 据获取的所述 MBMS业务的相应单播的接入信息, 向网络发送调度和接入 请求, 请求接入与所述 MBMS业务内容相同的单播业务, 当接入和调度请 求成功后, 通知单播接收模块。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201110048585.0 | 2011-02-28 | ||
CN2011100485850A CN102651852A (zh) | 2011-02-28 | 2011-02-28 | 一种多媒体广播多播业务连续接收的方法和装置 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012116536A1 true WO2012116536A1 (zh) | 2012-09-07 |
Family
ID=46693729
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2011/077573 WO2012116536A1 (zh) | 2011-02-28 | 2011-07-25 | 一种多媒体广播多播业务连续接收的方法和装置 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN102651852A (zh) |
WO (1) | WO2012116536A1 (zh) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114501340A (zh) * | 2020-10-23 | 2022-05-13 | ***通信有限公司研究院 | Mbs接收方法、发送方法、装置、终端及基站 |
CN114513756A (zh) * | 2020-10-23 | 2022-05-17 | 大唐移动通信设备有限公司 | 一种多播广播业务数据接收、指示方法、终端及网络设备 |
CN115086882A (zh) * | 2021-03-16 | 2022-09-20 | 维沃移动通信有限公司 | 传输方法、装置、设备及可读存储介质 |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2854427B1 (en) * | 2012-06-29 | 2018-08-01 | Huawei Technologies Co., Ltd. | Session processing method and device |
US9473906B2 (en) * | 2013-03-22 | 2016-10-18 | Mediatek Inc. | Idle mode reception for group communication over LTE eMBMS |
KR102033986B1 (ko) * | 2013-09-13 | 2019-10-21 | 후아웨이 테크놀러지 컴퍼니 리미티드 | 스트리밍 미디어를 전송하기 위한 방법과 시스템, 사용자 장비, 및 서버 |
CN104602197B (zh) * | 2013-10-30 | 2018-11-02 | 电信科学技术研究院 | 一种进行通信的方法、***和设备 |
CN104754522B (zh) * | 2013-12-25 | 2018-05-29 | 电信科学技术研究院 | 一种保持组通信业务连续性的方法、装置和*** |
CN104754519B (zh) * | 2013-12-25 | 2018-11-27 | 电信科学技术研究院 | 一种组通信业务的处理方法、用户设备和网络侧设备 |
WO2015096160A1 (zh) | 2013-12-27 | 2015-07-02 | 华为技术有限公司 | 一种保持业务连续性的方法及设备 |
WO2016070380A1 (en) * | 2014-11-06 | 2016-05-12 | Qualcomm Incorporated | Embms session suspend/stop notification |
CN110337068B (zh) * | 2014-11-13 | 2021-12-14 | 华为技术有限公司 | 多媒体广播组播的通信方法、装置和*** |
CN104918204A (zh) * | 2015-03-17 | 2015-09-16 | 华中科技大学 | 一种lte中的单播多播转换控制方法 |
WO2022028546A1 (en) * | 2020-08-06 | 2022-02-10 | FG Innovation Company Limited | Method of broadcast or multicast service and related device |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101043252A (zh) * | 2006-04-23 | 2007-09-26 | 华为技术有限公司 | 一种基于mbms机制的ims业务的传输方法及*** |
CN101567768A (zh) * | 2008-04-25 | 2009-10-28 | 展讯通信(上海)有限公司 | 一种mbms手机电视流式修复的方法、***和移动终端装置 |
WO2009140994A1 (en) * | 2008-05-19 | 2009-11-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Switching between delivery methods in an iptv communication network |
US20100023828A1 (en) * | 2008-07-28 | 2010-01-28 | At&T Corp. | IP Multicast with IP Unicast/Multicast Error Correction |
US20100235702A1 (en) * | 2009-03-12 | 2010-09-16 | Jiro Tanimoto | Transmitter, file distribution system, file distribution control method and file distribution control program in system |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101568158B (zh) * | 2008-04-24 | 2011-07-20 | 华为技术有限公司 | 一种用户设备小区切换的方法、***及装置 |
-
2011
- 2011-02-28 CN CN2011100485850A patent/CN102651852A/zh active Pending
- 2011-07-25 WO PCT/CN2011/077573 patent/WO2012116536A1/zh active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101043252A (zh) * | 2006-04-23 | 2007-09-26 | 华为技术有限公司 | 一种基于mbms机制的ims业务的传输方法及*** |
CN101567768A (zh) * | 2008-04-25 | 2009-10-28 | 展讯通信(上海)有限公司 | 一种mbms手机电视流式修复的方法、***和移动终端装置 |
WO2009140994A1 (en) * | 2008-05-19 | 2009-11-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Switching between delivery methods in an iptv communication network |
US20100023828A1 (en) * | 2008-07-28 | 2010-01-28 | At&T Corp. | IP Multicast with IP Unicast/Multicast Error Correction |
US20100235702A1 (en) * | 2009-03-12 | 2010-09-16 | Jiro Tanimoto | Transmitter, file distribution system, file distribution control method and file distribution control program in system |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114501340A (zh) * | 2020-10-23 | 2022-05-13 | ***通信有限公司研究院 | Mbs接收方法、发送方法、装置、终端及基站 |
CN114513756A (zh) * | 2020-10-23 | 2022-05-17 | 大唐移动通信设备有限公司 | 一种多播广播业务数据接收、指示方法、终端及网络设备 |
CN114513756B (zh) * | 2020-10-23 | 2023-04-04 | 大唐移动通信设备有限公司 | 一种多播广播业务数据接收、指示方法、终端及网络设备 |
CN115086882A (zh) * | 2021-03-16 | 2022-09-20 | 维沃移动通信有限公司 | 传输方法、装置、设备及可读存储介质 |
CN115086882B (zh) * | 2021-03-16 | 2024-03-19 | 维沃移动通信有限公司 | 传输方法、装置、设备及可读存储介质 |
Also Published As
Publication number | Publication date |
---|---|
CN102651852A (zh) | 2012-08-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2012116536A1 (zh) | 一种多媒体广播多播业务连续接收的方法和装置 | |
AU2017200065B2 (en) | Method and device for receiving a multimedia broadcast multicast service in a mobile communication system | |
US9491644B2 (en) | Method and device for determining resumption of suspended multimedia broadcast multicast service, and user equipment | |
US10045395B2 (en) | Base station, processor, and user terminal for setting a configuration to the user terminal for discontinuously monitoring a physical downlink control channel (PDCCH) on which a control signal is transmitted by the base station | |
US9237498B2 (en) | Method, user equipment and system for realizing service continuity of multimedia broadcast and multicast service | |
WO2017028582A1 (zh) | Sc-mcch发送方法、sc-ptm接收方法及其装置 | |
JP5844879B2 (ja) | Mbmsサービス送信方式の切替方法、装置及びユーザー装置 | |
WO2012155408A1 (zh) | 一种指示mbms业务中断的方法、装置及用户设备 | |
TWI414190B (zh) | 改善群播控制通道監聽機制的方法及通訊裝置 | |
CN103024680B (zh) | 半静态调度激活方法及基于半静态调度的集群通信*** | |
WO2012019461A1 (zh) | 多媒体广播多播业务中统计用户设备信息的方法和*** | |
WO2013096032A4 (en) | Method and apparatus for processing group event notifications and providing group policy in a communication system | |
US20160150590A1 (en) | Method and system for indicating a multicast session to user equipment (ue) in an idle mode | |
WO2009024073A1 (fr) | Procédé et système de rétroaction multiutilisateur, procédé de transmission en liaison descendante, station de base et dispositif utilisateur | |
WO2013170693A1 (zh) | Mbms的处理方法及装置、接收方法、装置及*** | |
WO2008043298A1 (fr) | Procédé et station de base pour terminal mobile dans un système de diffusion multidestination | |
WO2012041146A1 (zh) | 多媒体广播组播业务计数方法及*** | |
WO2012113312A1 (zh) | Mbms业务发送方式切换的方法和*** | |
CN105578440B (zh) | Lte***中的即时通讯业务心跳包的传输方法及装置 | |
WO2012113199A1 (zh) | 一种网元获取用户设备的接收状况信息的方法及*** | |
EP1898659A2 (en) | Method of reporting MBMS service information for user equipment in a wireless communications system and related apparatus | |
WO2012130007A1 (zh) | 一种mbms业务处理方法和*** | |
WO2012113342A1 (zh) | 实现mbms业务连续性的上报方法和用户设备 | |
WO2007022719A1 (fr) | Procede et equipement utilisateur de transmission de messages a partir d'equipement utilisateur vers le reseau | |
WO2012122772A1 (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: 11859876 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 11859876 Country of ref document: EP Kind code of ref document: A1 |