WO2013113268A1 - 一种mbms接收和能力传输方法及其装置 - Google Patents

一种mbms接收和能力传输方法及其装置 Download PDF

Info

Publication number
WO2013113268A1
WO2013113268A1 PCT/CN2013/071031 CN2013071031W WO2013113268A1 WO 2013113268 A1 WO2013113268 A1 WO 2013113268A1 CN 2013071031 W CN2013071031 W CN 2013071031W WO 2013113268 A1 WO2013113268 A1 WO 2013113268A1
Authority
WO
WIPO (PCT)
Prior art keywords
mbms
terminal
information
service
mbms service
Prior art date
Application number
PCT/CN2013/071031
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 EP13743636.6A priority Critical patent/EP2811764B1/en
Priority to KR1020147024176A priority patent/KR101636788B1/ko
Priority to US14/375,462 priority patent/US9826417B2/en
Publication of WO2013113268A1 publication Critical patent/WO2013113268A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/02Arrangements for optimising operational condition
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/10Scheduling measurement reports ; Arrangements for measurement reports
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/16Arrangements for providing special services to substations
    • H04L12/18Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/58Message adaptation for wireless communication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60Network streaming of media packets
    • H04L65/75Media network packet handling
    • H04L65/765Media network packet handling intermediate
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/442Monitoring of processes or resources, e.g. detecting the failure of a recording device, monitoring the downstream bandwidth, the number of times a movie has been viewed, the storage space available from the internal hard disk
    • H04N21/44209Monitoring of downstream path of the transmission network originating from a server, e.g. bandwidth variations of a wireless network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/637Control signals issued by the client directed to the server or network components
    • H04N21/6371Control signals issued by the client directed to the server or network components directed to network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/64Addressing
    • H04N21/6405Multicasting
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/647Control signaling between network components and server or clients; Network processes for video distribution between server and clients, e.g. controlling the quality of the video stream, by dropping packets, protecting content from unauthorised alteration within the network, monitoring of network load, bridging between two different networks, e.g. between IP and wireless
    • H04N21/64723Monitoring of network processes or resources, e.g. monitoring of network load
    • H04N21/64738Monitoring network characteristics, e.g. bandwidth, congestion level
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • 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
    • H04W76/00Connection management
    • H04W76/40Connection management for selective distribution or broadcast
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/22Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24Transfer of terminal data

Definitions

  • the present invention relates to the field of wireless communications, and in particular, to an MBMS receiving and capability transmission method and apparatus therefor. Background technique
  • MBMS Multimedia Broadcast Multicast Service
  • LTE Long Term Evolution
  • the MBMS service is supported on the frequency layer shared by the MBMS and the unicast service.
  • the cell on the frequency layer is an MBMS/unicast hybrid cell.
  • the frequency layer capable of providing the MBMS service is the MBMS frequency layer.
  • the MBMS service uses the MBSFN (Multicast Broadcast Single Frequency Network) transmission method.
  • MBSFN Multicast Broadcast Single Frequency Network
  • the so-called MBSFN refers to simultaneous transmission in multiple cells at the same frequency at the same time (that is, cells in the same MBSFN area are all of the same frequency).
  • Using this transmission method can save frequency resources and improve spectrum utilization. It requires multiple cells to send identical content simultaneously.
  • the UE (User Equipment, Terminal) receiver can treat multiple MBSFN cells as one large cell. Therefore, the UE will not only be subject to inter-cell interference transmitted by neighboring cells, but will also benefit from the superposition of signals from multiple MBSFN cells.
  • advanced UE receiver technology is used, the time difference of multipath propagation can be solved, thereby eliminating intra-cell interference.
  • the diversity effect brought by the multi-cell co-frequency transmission can also solve problems such as blind zone coverage, enhance the reliability of reception, and improve coverage.
  • MBMSN domain MBMS Step transmission Supports multi-cell MBMS transmission consolidation
  • MBSFN synchronization area can be semi-statically configured
  • ⁇ port through O&M (Operation and Management) system.
  • Fig. 1 shows the relationship between the MBMS service area and the MBSFN synchronization area and the like.
  • the MBMS service area is distinguished by one or more service identifiers, and each identifier is mapped to one or more cells.
  • the MBSFN area is composed of a group of cells in the synchronization area, and these cells perform synchronous MBSFN transmission, and the MBSFN area is planned according to the operator's policy.
  • the MBSFN area reserved cell also belongs to the synchronization area, and the cell does not perform MBSFN transmission.
  • LTE Rd-11 multiple frequency layers are allowed to provide MBMS services at the same time, but in the same geographical location, a service can usually only be sent through one MBMS frequency layer.
  • the business continuity of MBMS is guaranteed only in one MBSFN area, that is, continuity is guaranteed only in one frequency layer.
  • Business continuity between different frequencies or business continuity of multiple frequencies is temporarily not considered.
  • the UE In order to ensure the continuity of the service, the UE needs to report the status of the latest MBMS service reception or interest to the network, and the network should ensure the continuity of the reception of the MBMS service when the network is switched.
  • the UE reports a MBMS frequency point that is currently interested or being received, and the frequency point is a non-serving frequency point.
  • the UE may directly receive the MBMS service in the current configuration, but the receiving capability is better.
  • the UE cannot directly receive the MBMS in the current configuration, and the network side needs to reconfigure the serving cell before receiving.
  • the embodiment of the present invention provides an MBMS receiving and capability transmission method and a device thereof, which are used to solve the problem that the content of the existing MBMS service information is not comprehensive enough, thereby ensuring the MBMS reception continuity of the terminal.
  • MBMS service receiving and capability information reporting method provided by the embodiment of the present invention, Includes:
  • the terminal sends the MBMS information that the terminal is interested in or receiving, and the receiving capability information of the terminal to the corresponding MBMS service to the network device.
  • the network device performs corresponding processing according to the received MBMS information and the receiving capability information of the corresponding MBMS service by the terminal.
  • a sending module configured to send, to the network device, MBMS information that is interested or received by the terminal, and information about the receiving capability of the terminal to the corresponding MBMS service.
  • a receiving module configured to receive MBMS information that is sent by the terminal or is being received by the terminal, and receiving capability information of the terminal for the corresponding MBMS service;
  • a processing module configured to perform corresponding processing according to the received MBMS information and the terminal receiving capability information of the corresponding MBMS service.
  • the network device can process the MBMS service receiving capability of the terminal to ensure the continuity of the MBMS service reception of the terminal by reporting the receiving capability information of the MBMS service of the terminal to the network device.
  • FIG. 1 is a schematic diagram showing the relationship between an MBMS service area and an MBSFN synchronization area in the prior art
  • FIG. 2 is a schematic flowchart of a UE side in an MBMS receiving and capability reporting process according to Embodiment 1 of the present invention
  • FIG. 3 is a schematic flowchart of an eNB side in an MBMS receiving and capability reporting process according to Embodiment 1 of the present invention
  • FIG. 4 is a schematic flowchart of a UE side in an MBMS receiving and capability reporting process according to Embodiment 2 of the present invention
  • 5 is a schematic flowchart of an eNB side in an MBMS receiving and capability reporting process according to Embodiment 2 of the present invention
  • FIG. 6 is a schematic flowchart of a UE side in an MBMS receiving and capability reporting process according to Embodiment 3 of the present invention.
  • FIG. 7 is a schematic flowchart of an eNB side in an MBMS receiving and capability reporting process according to Embodiment 3 of the present invention.
  • FIG. 8 is a schematic structural diagram of a terminal device according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a network device according to an embodiment of the present invention. detailed description
  • the MBMS service related information reporting mechanism of the UE is improved.
  • the UE reports the MBMS information that it receives or is interested in to the network side, and informs whether the MBMS service or frequency point of interest is within the receiving capability range of the UE, if the frequency corresponding to the MBMS service that the UE is interested in. If the point is located outside the receiving capability of the current configuration, the network may reconfigure the serving cell of the UE according to the load situation and the algorithm to ensure the continuity of the MBMS service reception of the user.
  • the MBMS service receiving and capability reporting methods provided by the embodiments of the present invention mainly include:
  • Manner 1 The UE reports the receiving capability information by binding the MBMS frequency/service information that is of interest or received to the receiving capability.
  • the terminal reports the MBMS frequency point + optional indication information.
  • the length of the optional indication information is lbit. If the lbit indication information is carried, it indicates that the UE is interested in the MBMS frequency point but has no capability to receive in the current configuration; if the lbit indication information is not carried, it indicates that the UE can directly receive or receive the MBMS of the frequency point in the current configuration.
  • the MBMS frequency point on the terminal or other identification information corresponding to the MBMS service indicates that the UE can be straight in the current configuration.
  • the MBMS service is received, and the other identifier information indicates that the UE cannot receive the corresponding MBMS service under the current configuration.
  • the other identification information may be a service ID or a service area ID or a cell identifier carrying the service.
  • the MBMS service receiving capability refers to whether the UE can receive the MBMS service on the corresponding MBMS frequency reported by the UE in the current configuration, that is, the MBMS frequency corresponding to the MBMS service that the UE is interested in or receiving. Point, whether it is within the receiving capability range of the current configuration of the UE.
  • the MBMS service receiving capability information can be sent to the network side in display mode or implicit mode.
  • Manner 2 The UE reports the receiving capability of the MBMS service separately.
  • a specific implementation is as follows: The UE reports the MBMS service receiving capability through an independent process or a network triggered process.
  • the MBMS service receiving capability is for a cell, and the UE may indicate one or a combination of the following content in the reported MBMS service receiving capability information:
  • the UE can only receive MBMS services on the Pcdl (primary carrier);
  • the UE may receive the MBMS service on any serving cell; iii.
  • the UE may receive the MBMS service within the aggregate capability;
  • the UE may receive MBMS services on any carrier (eg separate MBMS receivers);
  • the UE can simultaneously receive MBMS services and the like on multiple carriers.
  • This embodiment uses the LTE system as an example to describe the flow of the MBMS receiving and capability information reported by the UE through the MBMS frequency point + lbit optional indication, and the corresponding processing procedure on the network side.
  • FIG. 2 is a schematic flowchart of a UE side according to Embodiment 1 of the present invention, where the process may include:
  • Step 201 The UE enters RRC (Radio Resource Control, according to requirements). Radio resource control) connection status.
  • RRC Radio Resource Control
  • Step 202 The UE in the RRC connection state reports the MBMS reception information (or the MBMS sense) to the serving eNB (base station) if the MBMS service that is interested in or is being changed changes or the new MBMS service is about to start. Interest information) and the terminal's ability to receive the MBMS service.
  • the UE may organize a dedicated RRC message to report the MBMS service receiving information or the MBMS service interest information to the serving eNB, and indicate the UE's receiving capability for the MBMS service by using the message.
  • the UE may receive the MBMS service according to the specific situation.
  • the specific conditions are as follows:
  • the UE automatically receives the service on the MBMS frequency point of interest;
  • the UE waits for the network to reconfigure the serving cell, and after the reconfiguration is completed, the UE directly receives the MBMS service from the MBMS frequency;
  • the MBMS frequency reported by the UE is outside the range of the UE's receiving capability, and the network side cannot change the serving cell of the UE to the state in which the MBMS service can be successfully received due to reasons such as MBMS frequency congestion: If the message indicates that the priority of the MBMS service is high, the unicast service is released by the network, and the UE enters the IDLE (idle) state to receive the MBMS service.
  • the UE continues to receive the unicast service; if the MBMS reception or the state of interest is unchanged, it can be maintained (after the MBMS frequency congestion is eliminated or considered during the handover), and if it changes, the update report is continued according to the flow shown in FIG. 2 above.
  • the content of the report message may follow the following principles: i.
  • the UE includes the MBMS frequency in the report message.
  • the information does not include the lbit indication information corresponding to the MBMS frequency.
  • the UE may include both the MBMS frequency information and the corresponding lbit indication information in the report message, but the value of the lbit indication information indicates the MBMS frequency.
  • the point is within the current receiving capability of the UE; Ii.
  • the UE When the frequency point corresponding to the latest MBMS service belongs to the case that the current UE capability cannot be directly received, the UE needs to include the corresponding MB information information in the report message, and the corresponding lbit indication information, where The indication information corresponds to the MBMS frequency point information, indicating that the MBMS frequency point exceeds the current receiving capability of the UE.
  • the MBMS frequency included in the report message cannot exceed the MBMS frequency range that the UE can receive at the same time. For example, the UE can only receive one MBMS frequency point, and the UE cannot include two MBMS frequency points in the report message.
  • the UE handles the priority of each MBMS frequency by itself, and further sets the priority by setting the MBMS frequency priority or by sorting (for example, the top MBMS frequency has high priority). Further, when the number of MBMS frequency points of interest is greater than the number of frequency points of the MBMS that are supported by the UE, the UE discards the low priority MBMS frequency and reports only the higher priority MBMS frequency.
  • step 202 of the above process for the triggering moment of the upper message, there is one of the following principles:
  • the UE waits for a certain stable reception duration and then reports to the eNB. For example, the UE receives the FMS frequency of the MBMS service and then reports the time to the eNB, where the T value is the network configuration or the UE setting or default. Further, in the range of the waiting T duration, if the measurement report needs to be performed, the UE immediately reports the MBMS reception status information;
  • the UE performs the MBMS reception status and the network to the network at the time when the service start time is pushed forward by the T duration.
  • the capability information is reported, where the T value is a network configuration or a UE setting or a default. Further, the T value may have different values for the frequency point corresponding to the MBMS service, which is located within the UE receiving capability and outside the UE receiving capability, and is generally located outside the receiving capability. The value is larger to allow sufficient time to transform the current serving cell.
  • the UE when the relationship between the MBMS frequency point and the receiving capability of the UE is changed, it is not necessary to trigger a new MBMS receiving state reporting process, because the network The side already has the corresponding information. For example, if the frequency of the MBMS of the UE is F1 and the frequency of the current unicast connection is F2, the UE does not need to report the MBMS reception status message again to inform the network F1 after the UE changes the service frequency to the F1. The point is within the capability range of the UE; if the MBMS frequency point of interest is outside the current UE capability, the network side considers that the UE is interested in the MBMS frequency point, unless the UE side changes the serving cell to the UE.
  • the MBMS reception status report will be sent again, that is, only the MBMS frequency point is changed independently with respect to the reception capability (ie, the MBMS frequency of interest is unchanged and the UE is caused by the change of the monthly service cell.
  • the change of the MBMS receiving capability does not need to be reported to the network side.
  • FIG. 3 it is a process flow on the eNB side according to Embodiment 1 of the present invention, where the process may include:
  • Step 301 The eNB configures the UE to enter the RRC connection state.
  • the UE is currently in the RRC connected state, this step can be omitted.
  • Step 302 The eNB receives a message that the MBMS receives status information sent by the UE.
  • the specific implementation can include the following:
  • the eNB learns that the MBMS frequency reported by the UE is within the current receiving capability range of the UE according to the display indication in the message, and does not need to perform any reconfiguration operation by the eNB, and only needs to record the MBMS frequency information that the UE is interested in, for The next step is to select the serving cell to use, so as to ensure the continuity of the MBMS service reception of the UE;
  • the eNB learns that the MBMS frequency reported by the UE is outside the UE's receiving capability range according to the display indication in the message, and allows the UE to perform the operation of changing the serving cell according to the network side load and algorithm, for example, the UE's Pcell (main The frequency point is switched to the frequency of the MBMS service to receive the unicast service and the MBMS service at the same time, and then the UE is reconfigured for the serving cell, and the MBMS frequency information of the UE is recorded;
  • the eNB learns that the MBMS frequency reported by the UE is outside the UE's receiving capability range according to the display indication in the message, and does not allow the UE to perform a desired serving cell change operation, such as MBMS frequency congestion, according to the network side load and algorithm.
  • the unicast service and the MBMS service cannot be guaranteed at the same time. In this case, if the received message of the UE is considered to have a high priority, the network side releases the unicast service, and the UE enters.
  • the IDLE state receives the MBMS service.
  • the network side records the MBMS frequency point information that the UE is interested in, and the MBMS frequency point congestion is released, or the UE switches, or the UE After the receiving status information is changed, the continuity of the MBMS reception is considered according to the recorded MBMS frequency information of the UE and the UE receiving capability, and corresponding processing is performed.
  • This example uses the LTE system as an example to describe the flow of the MBMS receiving and capability information reported by the UE through the MBMS frequency point or / and other identifiers corresponding to the MBMS service, and the corresponding processing flow on the network side.
  • FIG. 4 is a schematic flowchart of a UE side according to Embodiment 2 of the present invention, where the process may include:
  • Step 401 The UE enters an RRC connection state as needed. Of course, if the UE is currently in the RRC connected state, this step can be omitted.
  • Step 402 The UE in the RRC connected state reports MBMS receiving information (or MBMS interest information) to its serving eNB if the MBMS service that it is interested in or is changing, or the new MBMS service is about to start. And the terminal's receiving capability information for the MBMS.
  • the UE may organize a dedicated RRC message to report the MBMS service interest information or the MBMS service reception information to the serving eNB, and indicate the UE's receiving capability for the MBMS service by using the message.
  • the UE may receive the MBMS service according to the specific situation.
  • the specific conditions are as follows:
  • the UE automatically receives the service on the MBMS frequency point of interest;
  • the MBMS frequency reported by the UE is outside the receiving capability range of the UE, and the UE waits for the network to reconfigure its serving cell. After the reconfiguration is completed, the UE directly receives the MBMS service from the MBMS frequency point;
  • the MBMS service reported by the UE is in the range of the receiving capability of the UE, and the network side cannot change the serving cell of the UE to the state in which the MBMS service can be successfully received due to the congestion of the MBMS frequency, etc.: If the UE reports at this time Indicated in the message If the MBMS service has a high priority, the unicast service is released by the network, and the UE enters the IDLE state to receive the MBMS service. If the UE reports that the unicast service has a high priority, the UE continues to receive the unicast service. Or if the state of interest is unchanged, it can be maintained (after the MBMS frequency congestion is eliminated or considered during handover), and if it changes, the update report is continued according to the flow shown in FIG. 4 above.
  • the content of the report message may follow the following principles: i.
  • the frequency point corresponding to the latest MBMS service of interest belongs to the case that the current UE can directly receive
  • the UE includes the MBMS frequency in the report message.
  • the UE may not be able to know the MBMS frequency point where the service of interest is located at this time, and the UE may use the following three methods.
  • Mode 1 The MBMS service identifier that is of interest to the UE, that is, the Service ID;
  • Mode 2 The MBMS Service Area ID to which the MBMS service of interest belongs to the UE;
  • Mode 3 If the UE can learn other information related to the MBMS service of interest, such as a cell identifier, from the cell that can currently read the system message, the UE may report the other information, such as the cell identifier.
  • the UE may report the other information, such as the cell identifier.
  • the MBMS frequency included in the report message cannot exceed the MBMS frequency range that the UE can receive at the same time. For example, the UE can only receive one MBMS frequency point, and the UE cannot simultaneously include two MBMS service information (such as MBMS) in the report message. If the UE is unable to know the MBMS frequency information to which the service of interest belongs, the UE determines whether the MBMS frequency range that can be simultaneously received is exceeded according to the existing information;
  • the UE handles the priority of the MBMS service of interest by itself, and further sets the priority by setting the priority of the MBMS service or by sorting. Further, when the number of frequency points of the MBMS service in interest is greater than the number of frequency points that the UE can support while receiving the MBMS, the UE abandons the low priority MBMS service, only Report higher priority MBMS services.
  • the network side considers that the UE is interested in the service ID or the service area ID or the MBMS frequency corresponding to the cell identifier, regardless of whether the subsequent network side changes the serving cell to the UE.
  • the MBMS reception status report is sent again, that is, only the MBMS frequency point is changed separately from the reception capability (ie, the MBMS service is unchanged and the UE reception capability changes), and Reported to the network side.
  • FIG. 5 it is a process flow on the eNB side according to Embodiment 2 of the present invention, where the process may include:
  • Step 501 The eNB configures the UE to enter the RRC connection state.
  • the UE is currently in the RRC connected state, this step can be omitted.
  • Step 502 The eNB receives a message that the MBMS receives status information sent by the UE.
  • Step 503 The eNB performs corresponding processing according to the MBMS service indicated by the message and the receiving capability of the UE.
  • the specific implementation can include the following:
  • the eNB learns that the MBMS frequency reported by the UE is within the current receiving capability range of the UE according to the display indication in the message, and does not need to perform any reconfiguration operation by the eNB, and only needs to record the MBMS frequency information that the UE is interested in, for Refer to use when selecting the service cell in the next step;
  • the eNB learns that the frequency point corresponding to the MBMS service reported by the UE is outside the receiving capability range of the UE according to the display indication in the message, and allows the UE to perform the operation of changing the serving cell according to the network side load and algorithm, for example, the UE
  • the Pcdl is switched to the frequency of the MBMS service to receive the unicast service and the MBMS service at the same time, and then the UE is reconfigured with the monthly service cell, and the MBMS frequency information of the UE is recorded;
  • the eNB learns that the frequency point corresponding to the MBMS service reported by the UE is outside the receiving capability range of the UE according to the display indication in the message, and according to the load and algorithm on the network side, The UE is not allowed to perform the desired serving cell change operation, for example, MBMS frequency congestion, and cannot receive the unicast service and the MBMS service at the same time. In this case, if the received UE reports the message and considers that the MBMS service has a high priority, then The network side releases the unicast service, and the UE enters the IDLE state to receive the MBMS service.
  • the desired serving cell change operation for example, MBMS frequency congestion
  • the network side records the MBMS frequency information of the UE, and waits for the MBMS frequency congestion to be released. After the handover occurs, or the receiving state information of the UE is changed, the continuity of the MBMS reception is considered according to the recorded MBMS frequency information of the UE and the UE receiving capability, and corresponding processing is performed.
  • the LTE system is taken as an example to describe a process in which the UE separately reports the MBMS receiving capability information, and a corresponding processing procedure on the network side.
  • FIG. 6 is a schematic flowchart of a UE side according to Embodiment 3 of the present invention, where the process may include:
  • Step 601 The UE enters an RRC connection state as needed. Of course, if the UE is currently in the RRC connected state, this step can be omitted.
  • Step 602 The UE in the RRC connection state performs the reporting of the MBMS service receiving capability as needed.
  • the triggering manner for the UE to report the MBMS service receiving capability may have one of the following options:
  • the UE piggybacks the MBMS reception capability information in the response message.
  • the network switch control mode such as network side implicit (such as the new MBMS service continuity function design may add some new domain in the system message, then the new domain The presence switch is turned on, otherwise it is turned off) or the display switch (for example, the lbit additional indication in the system message indicates whether the eNB supports the MBMS capability report processing);
  • the UE When the UE reports the first MBMS reception status information in the connected state, the UE carries the MBMS service capability information by using the report message. Further, after the handover to the new cell, if the UE is configured to immediately re-report the MBMS reception status information, The MBMS service receiving capability information is also carried by the report message.
  • the MBMS receiving capability information reported by the UE may include a bit for indicating a relationship between the serving cell of the UE and the MBMS service receiving capability, such as indicating one or more of the following relationships by one or some bits:
  • the UE can only receive MBMS services on the Pcell (primary carrier);
  • the UE may receive the MBMS service on any serving cell; iii.
  • the UE may receive the MBMS service within the aggregate capability;
  • the UE can receive MBMS services (e.g., a separate MBMS receiver) on any carrier.
  • MBMS services e.g., a separate MBMS receiver
  • the MBMS receiving capability information reported by the UE includes a bit for indicating whether the UE can simultaneously receive the MBMS service on multiple carriers, or a bit for indicating the number of carriers that the UE can receive the MBMS service.
  • the MBMS receiving capability information reported by the UE may include the above two indicating bits.
  • the minimum encoding format is used as much as possible to indicate different receiving capabilities.
  • 3-bit information is used as a capability indication, where the first two bits indicate which carriers can receive the MBMS service, and the third bit indicates whether there are multiple carriers capable of simultaneously receiving the MBMS service.
  • the first two digits 00 represent that the UE can only receive the MBMS service on the Pcell
  • the 01 represents that the UE can receive the MBMS service on any Serving cell
  • the tenth that the UE can receive the MBMS service within the aggregation capability range and 11 represents the UE.
  • the MBMS service (e.g., a separate MBMS receiver) may be received on any carrier;
  • the third bit 1 or 0 represents whether the UE supports multiple carriers simultaneously receiving MBMS services within the range indicated above.
  • Step 603 The UE in the RRC connection state reports the MBMS receiving status information as needed.
  • the MBMS receiving status refers to an MBMS service that is of interest to the UE or an MBMS service that the UE is receiving.
  • the MBMS service may be identified by an MBMS frequency, or/and identified by other information corresponding to the MBMS service (eg, service ID, Service Area ID or cell ID).
  • the content of the MBMS reception status information reported may follow the following original 'J: i.
  • the MBMS frequency included in the report message cannot exceed the UE can receive at the same time.
  • the MBMS frequency range for example, the UE can only receive one MBMS frequency point, and the UE cannot simultaneously include two MBMS frequency points in the report message;
  • the UE handles the priority of each MBMS frequency point and further sets the priority of each MBMS frequency point. Further, when the number of MBMS frequencies of interest is greater than the number of frequency points of the MBMS that are supported by the UE, the UE discards the low-priority MBMS frequency and reports only the higher priority MBMS frequency.
  • the MBMS frequency point information of interest may exceed the number of MBMS frequency points that the UE can simultaneously support, and indicate the priority of the MBMS frequency point of interest of the UE according to the arrangement order. From high to low, to meet the needs of users on the network side from high to low;
  • Interested MBMS frequency information can exceed the number of MBMS frequency points that the UE can support at the same time.
  • the order of the MBMS does not represent any priority relationship, and any MBMS frequency reception can be satisfied.
  • the triggering time of the reporting of the MBMS receiving status information is the same as that in the first embodiment, and details are not described herein again.
  • the UE may perform subsequent operations according to the configuration of the eNB, such as reconfiguration or return to the IDLE state.
  • the above steps 602 and 603 do not have strict timing requirements.
  • FIG. 7 is a process flow on the eNB side according to Embodiment 3 of the present invention, the process may include:
  • Step 701 The eNB configures the UE to enter the RRC connection state.
  • the UE is currently in the RRC connected state, this step can be omitted.
  • Step 702 The eNB receives the MBMS service receiving capability information sent by the UE.
  • the eNB receives the MBMS service receiving capability information sent by the UE, corresponding to the triggering manner in which the UE reports the MBMS service receiving capability in the process shown in FIG. 6. If the eNB needs to trigger the UE to report the MBMS service receiving capability information (as received by the newly defined eNB query procedure). Then, after the UE is triggered to send the MBMS service receiving capability information, the corresponding information reported by the UE is received.
  • Step 703 the eNB receives the MBMS receiving status information sent by the UE, and according to the situation Conditional processing.
  • the eNB may perform the following processing according to specific conditions:
  • the eNB only needs to record the reception status of the UE, so as to ensure the continuity of the MBMS reception when the subsequent serving cell is replaced;
  • the MBMS service that is of interest to the UE is not within the current receiving range. If the eNB can re-allocate the serving cell of the UE according to the MBMS service receiving capability and the MBMS frequency load of the UE, the unicast service and the MBMS service are simultaneously received. The eNB reconfigures the serving cell of the UE, and records the MBMS service receiving information.
  • the MBMS service that is of interest to the UE is not within the current receiving range. If the eNB fails to reconfigure the serving cell of the UE to meet the unicast service and the MBMS service simultaneously according to the MBMS service receiving capability of the UE and the MBMS frequency load situation, The eNB further determines the priority between the unicast service and the MBMS service. If the priority of the MBMS service is high, the UE is released to return to the IDLE state to receive the MBMS service. If the unicast priority is high, the existing configuration is maintained, and the MBMS of the UE is recorded. Business reception situation;
  • the eNB In the case where there is more than one MBMS frequency of interest, the eNB tries to satisfy more and higher priority MBMS service reception according to whether there is a priority indication.
  • steps 702 and 703 do not have strict timing requirements, and the order of execution may be determined by the reporting order of the UE side.
  • the embodiment of the present invention further provides a terminal device and a network device applicable to the above process.
  • FIG. 8 is a schematic structural diagram of a terminal device according to an embodiment of the present disclosure, where the terminal device may include:
  • the sending module 803 is configured to send, to the network device, the MBMS information that the terminal is interested in or receiving, and the receiving capability information of the terminal to the corresponding MBMS service.
  • the sending module 803 is specifically configured to: send the MBMS information and the receiving capability information of the MBMS service to the network device by reporting a message to the network device, where:
  • the sending module sends The message reported by the network device includes the MBMS frequency to indicate that the terminal can receive the corresponding MBMS service in the current configuration; or the terminal includes the message to the network device.
  • An MBMS frequency point and corresponding indication information where the indication information indicates that the terminal is capable of receiving the MBMS service on the corresponding MBMS frequency point in the current configuration;
  • the message sent by the sending module to the network device includes the The MBMS frequency point and the corresponding indication information, the indication information indicates that the terminal cannot receive the MBMS service on the corresponding MBMS frequency point in the current configuration.
  • the sending module 803 is specifically configured to: send the MBMS information and the receiving capability information of the MBMS service to the network device by reporting a message to the network device, where:
  • the message sent by the sending module to the network device includes the MBMS frequency to indicate that the terminal can receive the MBMS service on the MBMS frequency point in the current configuration;
  • the sending module acquires other identifier information corresponding to the MBMS service, and is in the network device.
  • the reported message includes the identifier information corresponding to the MBMS service, to indicate that the terminal cannot receive the MBMS service corresponding to the identifier information in the current configuration.
  • the sending module 803 is specifically configured to: send the MBMS information and the receiving capability information of the MBMS service to the network device by reporting a message to the network device, where:
  • the sending module sends a first message to the network device, where the MBMS service receiving capability information of the terminal in the current configuration is carried; and the second message is sent to the network device, where the MBMS information is carried.
  • the MBMS receiving capability information sent by the sending module 803 includes a bit for indicating a relationship between the serving cell of the terminal and the MBMS service receiving capability.
  • the MBMS receiving capability information sent by the sending module 803 includes a bit for indicating whether the terminal can simultaneously receive the MBMS service on multiple carriers, or a bit for indicating the number of carriers that the terminal can receive the MBMS service. .
  • the sending module 803 sends the first message when the terminal receives the capability query request sent by the network device, or sends the first message when the terminal sends the first MBMS receiving status report after the terminal enters the connected state. Or a message; or, when the terminal is configured to report the MBMS reception status information after the handover to the target cell, the first message is sent after the handover to the target cell.
  • the MBMS information is set with a priority.
  • the message reported by the sending module 803 includes one or more MBMS information, where the number of MBMS frequency points corresponding to the MBMS information is within the range of the number of MBMS frequencies that the terminal can simultaneously receive.
  • the sending module 803 is specifically configured to: after the terminal learns that the user selects and receives the MBMS service that has been sent in the air interface, and waits for the set time period from the time when the user starts to browse for the selected MBMS service, and then goes to the network.
  • the device reports the message to the network device.
  • the terminal After the terminal learns that the user is interested in the MBMS service to be sent in the air interface, the terminal reports the message to the network device before the start time of the MBMS service and when the start time is the set time.
  • the sending module 803 is specifically configured to: if the terminal learns that the user is interested in the MBMS service to be sent in the air interface, and the terminal can receive the MBMS service in the current configuration, report the message to the network device.
  • the start time of the MBMS service is a first set duration; if the terminal knows that the user is interested in the MBMS service to be sent in the air interface, and the terminal cannot receive the MBMS service in the current configuration, then The time when the network device reports the message is the second set duration from the MBMS service start time; wherein the first set duration is less than the second set duration.
  • the foregoing terminal device may further include: an obtaining module 801, configured to acquire MBMS information that the user is receiving or turning off an interest; and a determining module 802, configured to determine, by the terminal, a receiving capability of the corresponding MBMS service.
  • FIG. 9 is a schematic structural diagram of a network device according to an embodiment of the present disclosure.
  • the network device may include:
  • the receiving module 901 is configured to receive MBMS information that is sent by the terminal or that is received by the terminal, and the receiving capability information of the terminal for the corresponding MBMS service.
  • the processing module 902 is configured to: according to the received MBMS information, and the terminal. The receiving capability information of the corresponding MBMS service is processed accordingly.
  • the processing module 902 is specifically configured to: if the terminal can receive the corresponding MBMS service in the current configuration, according to the received MBMS information and the receiving capability information of the terminal for the corresponding MBMS service, save the terminal reporting The MBMS information, and refer to the saved MBMS information when selecting a serving cell for the terminal;
  • the terminal is Performing service cell reconfiguration to ensure that the terminal can receive the corresponding MBMS service and the unicast service, save the MBMS information reported by the terminal, and refer to the saved MBMS information when selecting the serving cell for the terminal;
  • the terminal is unable to receive the corresponding MBMS service in the current configuration, and determines that the terminal does not allow the terminal to change the serving cell, according to the received MBMS information and the receiving capability information of the terminal for the corresponding MBMS service, The priority of the MBMS service and the unicast service reported by the terminal; if the priority of the MBMS service is higher than the unicast service, the unicast service of the terminal is released, and the terminal is configured to enter the idle state to receive the MBMS service, otherwise the saver Decoding the MBMS information reported by the terminal, and referring to the saved MBMS information when selecting a serving cell for the terminal.
  • the processing module 902 is specifically configured to: when the MBMS information sent by the terminal is multiple and the priority is set, when the serving cell is selected for the terminal, according to the multiple sent by the terminal.
  • the priority of the MBMS information is selected as the serving cell, and the selected serving cell can ensure that the number of MBMS services received by the terminal is high and the priority is high.
  • the foregoing network device may further include a configuration module 903, configured to perform the The receiving module receives the MBMS information sent by the terminal and the receiving capability information of the terminal for the corresponding MBMS service, and configures the terminal to enter a connection state.
  • the embodiment of the present invention provides a mechanism for reporting the MBMS receiving capability, which enables the network side to better distinguish different users and make a reasonable configuration, which is beneficial to the overall guarantee of system performance, and is more conducive to Improved user experience.
  • modules in the apparatus in the embodiments may be distributed in the apparatus of the embodiment according to the description of the embodiments, or may be correspondingly changed in one or more apparatuses different from the embodiment.
  • the modules of the above embodiments may be combined into one module, or may be further split into a plurality of sub-modules.
  • the present invention can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is a better implementation. the way.
  • the form of the software product is embodied, the computer software product being stored in a storage medium, including a plurality of instructions for causing a terminal device (which may be a mobile phone, a personal computer, a server, or a network device) to execute the present
  • a terminal device which may be a mobile phone, a personal computer, a server, or a network device

Landscapes

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

Abstract

本发明公开了一种MBMS接收和能力传输方法及其装置,该方法中,终端向网络设备发送所述终端感兴趣或正在接收的MBMS信息,以及所述终端对相应MBMS业务的接收能力信息;相应的,网络设备接收终端发送的所述终端感兴趣或正在接收的MBMS信息以及所述终端对相应MBMS业务的接收能力信息;网络设备根据接收到的MBMS信息以及所述终端对相应MBMS业务的接收能力信息进行相应处理。采用本发明可解决现有MBMS业务信息上报机制所上报的内容不够全面的问题,进而保证终端的MBMS接收连续性。

Description

一种 MBMS接收和能力传输方法及其装置 本申请要求于 2012年 1 月 30 日提交中国专利局, 申请号为 201210020923.4, 发明名称为 "一种 MBMS接收和能力传输方法及 其装置"的中国专利申请的优先权, 其全部内容通过引用结合在本申 请中。 技术领域
本发明涉及无线通信领域, 尤其涉及一种 MBMS接收和能力传 输方法及其装置。 背景技术
MBMS ( Multimedia Broadcast Multicast Service, 多媒体广播组 播服务)用于为无线小区中用户提供多媒体广播和组播服务。 目前的 LTE ( Long Term Evolution, 长期演进 ) ***中, 支持在 MBMS和单 播业务共享的频率层上提供 MBMS 业务, 该频率层上的小区为 MBMS/单播混合小区。能够提供 MBMS业务的频率层被成为 MBMS 频率层,在一个 MBMS频率层上, MBMS业务使用 MBSFN( Multicast Broadcast Single Frequency Network, 组播单频网)传输方式。
所谓 MBSFN是指在同一时间以相同频率在多个小区进行同步传 输(也就是说, 同一个 MBSFN区域中的小区, 均为同频)。 使用这 种传输方式可以节约频率资源, 提高频谱利用率。 它要求多个小区将 完全相同的内容同时发送。 这样一来, UE ( User Equipment, 终端 ) 接收机就能将多个 MBSFN小区视为一个大的小区。 因此, UE不仅 不会受到相邻小区传输的小区间干扰, 而且将受益于来自多个 MBSFN小区的信号的叠加。 另外, 如果利用先进的 UE接收机技术 还能解决多径传播的时间差问题, 从而消除小区内干扰。 这种多小区 同频传输所带来的分集效果还可以解决盲区覆盖等问题,增强接收的 可靠性, 提高覆盖率。
MBMS多小区传输的技术特点如下: MBSFN域内 MBMS的同 步传输; 支持多小区 MBMS传输的合并; MBSFN同步区域可以半静 态配置, ^口: 通过 O&M ( Operation and Management , 操作与管理) ***。
图 1示出了 MBMS业务区与 MBSFN同步区等的关系。 其中, MBMS 业务区由一个或多个业务标识进行区分, 每个标识映射至一 个或多个小区。 MBSFN区域由同步区域内一组小区组成, 这些小区 进行同步的 MBSFN发送, MBSFN区域根据运营商的策略进行规划。 MBSFN区域预留小区也属于同步区域,该小区不进行 MBSFN发送。
在 LTE Rd-11中, 允许有多个频率层同时提供 MBMS业务, 但 是在同一个地理位置上, 一个业务通常只能通过一个 MBMS频率层 发送。 MBMS的业务连续性只在一个 MBSFN区域内保证,也就是只 在一个频率层内保证连续性。不同频率之间的业务连续性或者多个频 率的业务连续性暂时不考虑。 对于连接态的 UE, 为了保证其业务连 续性, UE需要将其最新的 MBMS业务接收或感兴趣的状态上报给网 络, 由网络在切换时尽量保证 MBMS业务的接收连续性。
现有技术中, 仅规定 UE 需要实时上报其最新的接收或感兴趣 MBMS 业务的频点, 但是对于网络侧来讲, 仅通过接收或感兴趣 MBMS业务的频点, 网络侧并不能对 UE的能力和接收情况掌握充 分,以至于无法对 UE进行正确的服务小区的配置,破坏了用户体验。 例如 UE上报了一个当前感兴趣或正在接收的 MBMS频点, 该频点 为非服务频点, 对于接收能力强的 UE可能当前的配置下 UE就可以 直接接收该 MBMS业务,但对于接收能力较弱的 UE(如只能在 Pcell 上接收 MBMS )来讲, UE在当前的配置下无法直接接收 MBMS, 需 要网络侧重新配置服务小区之后才能接收。 发明内容
本发明实施例提供了一种 MBMS 接收和能力传输方法及其装 置, 用以解决现有 MBMS业务信息上 ^艮机制所上 >¾的内容不够全面 的问题, 进而保证终端的 MBMS接收连续性。
本发明实施例提供的 MBMS业务接收和能力信息上报方法, 包 括:
终端向网络设备发送所述终端感兴趣或正在接收的 MBMS 信 息, 以及所述终端对相应 MBMS业务的接收能力信息。
本发明实施例提供的基于上述实现的 MBMS接收和能力信息接 收方法, 包括:
网络设备接收终端发送的所述终端感兴趣或正在接收的 MBMS 信息以及所述终端对相应 MBMS业务的接收能力信息;
所述网络设备艮据接收到的 MBMS 信息以及所述终端对相应 MBMS业务的接收能力信息进行相应处理。
本发明实施例提供的终端设备, 包括:
发送模块, 用于向网络设备发送所述终端感兴趣或正在接收的 MBMS信息, 以及所述终端对相应 MBMS业务的接收能力信息。
本发明实施例提供的网络设备, 包括:
接收模块, 用于接收终端发送的所述终端感兴趣或正在接收的 MBMS信息以及所述终端对相应 MBMS业务的接收能力信息;
处理模块, 用于根据接收到的 MBMS信息以及所述终端对相应 MBMS业务的接收能力信息进行相应处理。
本发明的上述实施例, 通过将终端的 MBMS业务的接收能力信 息上报给网络设备, 使网络设备可根据终端的 MBMS业务接收能力 进行处理, 以保证终端的 MBMS业务接收连续性。 附图说明
图 1为现有技术中 MBMS业务区与 MBSFN同步区的关系示意 图;
图 2为本发明实施例一提供的 MBMS接收和能力上报流程中的 UE侧流程示意图;
图 3为本发明实施例一提供的 MBMS接收和能力上报流程中的 eNB侧流程示意图;
图 4为本发明实施例二提供的 MBMS接收和能力上报流程中的 UE侧流程示意图; 图 5为本发明实施例二提供的 MBMS接收和能力上报流程中的 eNB侧流程示意图;
图 6为本发明实施例三提供的 MBMS接收和能力上报流程中的 UE侧流程示意图;
图 7为本发明实施例三提供的 MBMS接收和能力上报流程中的 eNB侧流程示意图;
图 8为本发明实施例提供的终端设备的结构示意图;
图 9为本发明实施例提供的网络设备的结构示意图。 具体实施方式
下面结合附图和实施例,对本发明的具体实施方式作进一步详细 描述:
针对现有技术存在的问题, 本发明实施例对 UE的 MBMS业务 相关信息上报机制进行了改进。 本发明实施例中, UE上报其接收或 感兴趣 MBMS信息给网络侧,并告知感兴趣的 MBMS业务或频点是 否在 UE的接收能力范围之内,如果 UE感兴趣的 MBMS业务所对应 的频点位于目前的配置下的接收能力之外,则网络可以根据负荷情况 和算法等将该 UE的服务小区进行重配, 以保证该用户的 MBMS业 务接收连续性。
概括来说, 本发明实施例所提供的 MBMS业务接收和能力上报 方式主要包括:
方式一: UE通过对感兴趣或接收的 MBMS频点 /业务信息, 与 接收能力绑定的方式上报接收能力信息
一种具体实现是:终端上报 MBMS频点 +可选指示信息,优选的, 该可选指示信息的长度是 lbit。 如果携带 lbit指示信息, 则表明 UE 对该 MBMS频点感兴趣但在当前配置下没有能力接收; 如果不携带 lbit指示信息, 则表明 UE在当前配置下可直接接收或者正在接收该 频点的 MBMS业务;
另一种具体实现是: 终端上艮 MBMS频点或 /和 MBMS业务对 应的其它标识信息。 其中 MBMS频点表示 UE在当前配置下可以直 接接收其上的 MBMS业务, 其它标识信息代表 UE在当前配置下无 法接收对应的 MBMS业务。 所述其它标识信息可以是 service ID (业 务标识 ) 或者 Service Area ID (业务区域标识 )或者 载该业务的 小区标识等。
在上述方式一中, 所述 MBMS业务接收能力是指 UE在当前配 置下是否可以接收该 UE上报的对应 MBMS频点上的 MBMS业务, 即 UE感兴趣或正在接收的 MBMS业务所对应的 MBMS频点, 是否 在该 UE当前配置下的接收能力范围之内。 MBMS业务接收能力信息 可通过显示方式或隐式方式发送给网络侧。
方式二: UE单独上报关于 MBMS业务的接收能力
一种具体实现是: UE通过独立的过程或者网络触发的过程上报 MBMS业务接收能力。
在上述方式二中,所述 MBMS业务接收能力是针对小区而言的, UE可在上报的 MBMS业务接收能力信息中指示出如下内容之一或 组合:
i. UE只能在 Pcdl (主载波 )上接收 MBMS业务;
ii. UE可以在任何 Serving cell (服务小区 )上接收 MBMS业务; iii. UE可以在聚合能力范围之内接收 MBMS业务;
iv. UE可以在任何载波接收 MBMS业务(例如单独的 MBMS接 收机 );
v. UE可以在多个载波同时接收 MBMS业务等。
下面结合附图, 对本发明实施例提供的上述两种上报 MBMS接 收和能力信息的方式进行详细描述。
实施例一
本实施例以 LTE***为例,描述了 UE通过 MBMS频点 +lbit可 选指示来上报 MBMS接收和能力信息的流程, 以及网络侧的相应处 理流程。
参见图 2, 为本发明实施例一中在 UE侧的流程示意图, 该流程 可包括:
步骤 201 , UE根据需要, 进入 RRC ( Radio Resource Control, 无线资源控制)连接状态。 当然, 如果 UE当前处于 RRC连接状态, 则该步骤可以省略。
步骤 202, 处于 RRC连接状态的 UE, 如果其感兴趣或者正在接 收的 MBMS业务发生变化,或者有新的感兴趣 MBMS业务即将开始, 则向其服务 eNB (基站 )上报 MBMS接收信息(或 MBMS感兴趣信 息)以及终端对该 MBMS业务的接收能力信息。 具体实施时, UE可 组织一个专用的 RRC消息向其服务 eNB上报 MBMS业务接收信息 或 MBMS业务感兴趣信息, 并通过该消息指示出 UE对该 MBMS业 务的接收能力。
此后, UE可根据具体情况, 接收 MBMS业务。 具体情况有以下 几种:
i. UE上报的 MBMS频点在 UE的接收能力范围之内时, UE自 行对感兴趣的 MBMS频点上的业务进行接收;
ii. UE上报的 MBMS频点在 UE的接收能力范围之外时, UE等 待网络重配其服务小区, 重配完成之后, UE自行到该 MBMS频点接 收 MBMS业务;
iii. UE上报的 MBMS频点在 UE的接收能力范围之外, 且网络 侧由于 MBMS频点拥塞等原因无法变更 UE的服务小区至能顺利接 收 MBMS业务的状态的情况下: 如果此时 UE上报的消息中指示出 MBMS业务优先级高,则由网络侧释放单播业务, UE进入 IDLE (空 闲)状态接收 MBMS业务; 如果此时 UE上报的信息中指示出单播 业务的优先级高, 则 UE继续接收单播业务; MBMS接收或者感兴趣 状态如果不变, 可以维持(等 MBMS频点拥塞消除之后或者切换时 考虑), 如果变化, 则根据上述图 2所示流程继续进行更新上报。
上述流程的步骤 202中, 关于上报消息内容可以遵循以下原则: i. 当最新的感兴趣 MBMS业务所对应的频点属于当前 UE直接 可以接收的情况时, UE在上报消息中包含该 MBMS频点信息, 不包 含与该 MBMS频点对应的 lbit指示信息; 当然, UE在上报消息中也 可以既包含 MBMS频点信息也包含对应的 lbit指示信息,只是该 lbit 指示信息的取值表明该 MBMS频点在 UE当前的接收能力之内; ii.当最新的感兴趣 MBMS业务所对应的频点属于当前 UE能力 无法直接接收的情况时, UE除了需要在上报消息中包含该 MBMS频 点信息,还包含对应的 lbit的指示信息,其中该指示信息与该 MBMS 频点信息对应, 表明该 MBMS频点超出 UE当前的接收能力。
在此基础上, 上报消息内容还可进一步遵循以下原则之一或组 合:
iii.包含在上报消息中的 MBMS频点不能超出 UE能够同时接收 的 MBMS频点范围, 例如 UE只能接收一个 MBMS频点, 则 UE不 能在上报消息中同时包含两个 MBMS频点;
iv. UE 自行处理各个 MBMS频点的优先级, 并进一步通过设置 MBMS频点优先级的方式或通过排序方式(如排在前面的 MBMS频 点具有高优先级)显示设置优先级。 进一步的, 当感兴趣的 MBMS 频点数目大于 UE可支持的同时接收 MBMS的频点数目时, UE自行 放弃低优先级的 MBMS频点, 只上报较高优先级的 MBMS频点。
上述流程的步骤 202中, 对于上 消息的触发时刻, 有如下原则 之一:
i.如果 UE对现有正在空口传输的 MBMS业务进行浏览和选择, 则 UE等待一定的稳定接收时长后再向 eNB上报。 例如 UE接收 F1 频点的 MBMS业务达到 T时长后再向 eNB上报, 其中, T值为网络 配置或者 UE设置或者默认。 进一步的, 在等待的 T时长范围内, 如 果需要进行测量上报, 则 UE立即上报 MBMS接收状态信息;
ii.如果属于定制或者自动接收的 MBMS业务(即 UE获知用户 对即将在空口发送的 MBMS业务感兴趣 ), 则 UE在该业务开始时刻 向前推 T时长的时刻,向网络进行 MBMS接收状态和能力信息上报, 其中, T值为网络配置或者 UE设置或者默认。 进一步的, T值针对 该 MBMS业务所对应的频点位于 UE接收能力之内和位于 UE接收能 力之外两种情况下, 可以有不同的取值, 一般情况下, 位于接收能力 之外时 T值更大, 以留够充足的时间来变换当前的服务小区。
需要说明的是, 当 UE感兴趣的 MBMS频点与接收能力的关系 发生变化时, 不需要触发新的 MBMS接收状态上报过程, 因为网络 侧已经具有相应的信息。 例如 UE上 ^艮感兴趣的 MBMS频点为 F1 , 而当前单播连接的频点为 F2, 则网络为 UE改变服务频点至 F1后, UE无需再次上报 MBMS接收状态消息来告知网络 F1频点为 UE能 力范围之内; 对于感兴趣的 MBMS频点位于当前 UE能力之外的情 况, 则无论后续网络侧是否给 UE变更服务小区, 网络侧均认为 UE 对 MBMS频点感兴趣, 则除非感兴趣频点变更或者其它变更, 才会 再次发送 MBMS接收状态上报,即仅仅是 MBMS频点相对于接收能 力的单独变化(即感兴趣 MBMS频点不变而 UE因为月良务小区变更 而引起的 MBMS接收能力的变化), 不需要上报网络侧。
参见图 3, 为本发明实施例一在 eNB侧的处理流程, 该流程可包 括:
步骤 301 , eNB对 UE进行配置, 使 UE进入 RRC连接状态。 当 然, 如果 UE当前已经处于 RRC连接状态, 则该步骤可以省略。
步骤 302, eNB接收 UE发来的 MBMS接收状态信息的消息。 步骤 303, eNB根据该消息所指示的 MBMS频点和 UE的接收能 力, 进行相应处理。 具体实施时可包括以下情况:
i. eNB根据消息中的显示指示获知 UE上报的 MBMS频点在 UE 当前的接收能力范围之内, 则不需 eNB做任何重配操作, 只需记录 UE感兴趣的 MBMS频点信息, 以供下一步选择服务小区时参考使 用, 从而保证 UE的 MBMS业务接收连续性;
ii. eNB根据消息中的显示指示获知 UE上报的 MBMS频点在 UE 的接收能力范围之外, 且根据网络侧的负荷和算法, 允许 UE进行变 更服务小区的操作, 例如将 UE的 Pcell (主频点)切换到 MBMS业 务所在频点, 以同时接收单播业务和 MBMS业务, 则对 UE进行服 务小区重配置, 并记录 UE感兴趣的 MBMS频点信息;
iii. eNB根据消息中的显示指示获知 UE上报的 MBMS频点在 UE 的接收能力范围之外, 且根据网络侧的负荷和算法, 不允许 UE进行 期望的服务小区变更操作, 例如 MBMS频点拥塞, 无法同时保证接 收单播业务和 MBMS业务, 在这种情况下, 如果接收到的 UE上报 消息中认为 MBMS业务优先级高, 则网络侧释放单播业务, UE进入 IDLE状态接收 MBMS业务, 如果接收到的 UE上报消息中认为单播 业务的优先级高, 网络侧记录 UE感兴趣的 MBMS 频点信息, 待 MBMS频点拥塞解除, 或者 UE发生切换, 或者 UE的接收状态信息 改变后,再根据所记录的 UE感兴趣的 MBMS频点信息和 UE接收能 力, 考虑 MBMS接收的连续性, 并进行相应处理。
实施例二
本实施例以 LTE***为例, 描述了 UE通过 MBMS频点或 /和 MBMS业务对应的其它标识来上报 MBMS接收和能力信息的流程, 以及网络侧的相应处理流程。
参见图 4, 为本发明实施例二中在 UE侧的流程示意图, 该流程 可包括:
步骤 401 , UE根据需要, 进入 RRC连接状态。 当然, 如果 UE 当前处于 RRC连接状态, 则该步骤可以省略。
步骤 402, 处于 RRC连接状态的 UE, 如果其感兴趣或者正在接 收的 MBMS业务发生变化,或者有新的感兴趣 MBMS业务即将开始, 则向其服务 eNB上报 MBMS接收信息(或 MBMS感兴趣信息 ) 以 及终端对该 MBMS的接收能力信息。具体实施时, UE可组织一个专 用的 RRC 消息向其服务 eNB 上报 MBMS 业务感兴趣信息或者 MBMS业务接收信息, 并通过该消息指示出 UE对该 MBMS业务的 接收能力。
此后, UE可根据具体情况, 接收 MBMS业务。 具体情况有以下 几种:
i. UE上报的 MBMS频点在 UE的接收能力范围之内时, UE自 行对感兴趣的 MBMS频点上的业务进行接收;
ii. UE上报的 MBMS频点在 UE的接收能力范围之外, UE等待 网络重配其服务小区, 重配完成之后, UE自行到该 MBMS频点接收 MBMS业务;
iii. UE上报的 MBMS业务在 UE的接收能力范围之夕卜,且网络侧 由于 MBMS频点拥塞等原因无法变更 UE的服务小区至能顺利接收 MBMS 业务的状态的情况下: 如果此时 UE 上报的消息中指示出 MBMS业务优先级高, 则由网络侧释放单播业务, UE进入 IDLE状 态接收 MBMS业务; 如果此时 UE上报消息中指示出单播业务的优 先级高, 则 UE继续接收单播业务; MBMS接收或者感兴趣状态如果 不变, 可以维持(等 MBMS频点拥塞消除之后或者切换时考虑), 如 果变化, 则根据上述图 4所示流程继续进行更新上报。
上述流程的步骤 402中, 关于上报消息内容可以遵循以下原则: i. 当最新的感兴趣 MBMS业务所对应的频点属于当前 UE直接 可以接收的情况时, UE在上报消息中包含该 MBMS频点信息;
ii.当最新的感兴趣 MBMS业务所对应的频点属于当前 UE能力 无法直接接收的情况时, UE此时可能无法获知感兴趣的业务所在的 MBMS频点,则 UE可以以下列三种方式之一来上 ^艮感兴趣的 MBMS 业务:
方式 1: UE上 4艮感兴趣的 MBMS业务标识, 即 Service ID; 方式 2: UE上 4艮感兴趣的 MBMS业务所属的 MBMS Service Area ID ( MBMS服务区域标识);
方式 3: UE如果可以从当前可以读取***消息的小区中获知关 于感兴趣的 MBMS业务所属的其它信息, 例如小区标识, 则 UE可 以上报所述其它信息, 如小区标识。
在此基础上, 上报消息内容还可进一步遵循以下原则之一或组 合:
iii.包含在上报消息中的 MBMS频点不能超出 UE能够同时接收 的 MBMS频点范围, 例如 UE只能接收一个 MBMS频点, 则 UE不 能在上报消息中同时包含两个 MBMS业务信息(如 MBMS频点或 / 和 MBMS业务的其它标识); 对于 UE无法获知感兴趣的业务所属的 MBMS频点信息的情况, UE根据现有信息判断是否超出能同时接收 的 MBMS频点范围;
iv. UE自行处理感兴趣 MBMS业务的优先级,并进一步通过设置 MBMS 业务优先级的方式或通过排序方式显示设置优先级。 进一步 的, 当感兴趣的 MBMS业务所处频点数目大于 UE可支持的同时接 收 MBMS的频点数目时, UE自行放弃低优先级的 MBMS业务, 只 上报较高优先级的 MBMS业务。
对于步骤 402中 UE上报消息的触发时刻, 其所遵循的原则同实 施例一, 在此不再赘述。
需要说明的是, 当 UE感兴趣的 MBMS频点 (或 MBMS业务) 与接收能力的关系发生变化时, 不需要触发新的 MBMS接收状态上 过程, 因为网络侧已经具有相应的信息。 对于感兴趣的 MBMS业 务位于当前 UE能力之外的情况, 则无论后续网络侧是否给 UE变更 服务小区, 网络侧均认为 UE对 service ID或者 Service Area ID或者 小区标识对应的 MBMS频点感兴趣, 则除非感兴趣频点变更或者其 它变更, 才会再次发送 MBMS接收状态上报, 即仅仅是 MBMS频点 相对于接收能力的单独变化(即感兴趣 MBMS业务不变而 UE接收 能力变化), 不需要上报网络侧。
参见图 5, 为本发明实施例二在 eNB侧的处理流程, 该流程可包 括:
步骤 501 , eNB对 UE进行配置, 使 UE进入 RRC连接状态。 当 然, 如果 UE当前已经处于 RRC连接状态, 则该步骤可以省略。
步骤 502, eNB接收 UE发来的 MBMS接收状态信息的消息。 步骤 503, eNB根据该消息所指示的 MBMS业务和 UE的接收能 力, 进行相应处理。 具体实施时可包括以下情况:
i. eNB根据消息中的显示指示获知 UE上报的 MBMS频点在 UE 当前的接收能力范围之内, 则不需 eNB做任何重配操作, 只需记录 UE感兴趣的 MBMS频点信息, 以供下一步选择服务小区时参考使 用;
ii. eNB根据消息中的显示指示获知 UE上报的 MBMS业务所对 应的频点在 UE的接收能力范围之外, 且根据网络侧的负荷和算法, 允许 UE进行变更服务小区的操作,例如将 UE的 Pcdl切换到 MBMS 业务所在频点, 以同时接收单播业务和 MBMS业务, 则对 UE进行 月良务小区重配置, 并记录 UE感兴趣的 MBMS频点信息;
iii. eNB根据消息中的显示指示获知 UE上报的 MBMS业务所对 应的频点在 UE的接收能力范围之外, 且根据网络侧的负荷和算法, 不允许 UE进行期望的服务小区变更操作, 例如 MBMS频点拥塞, 无法同时保证接收单播业务和 MBMS业务, 在这种情况下, 如果接 收到的 UE上报消息中认为 MBMS业务优先级高, 则网络侧释放单 播业务, UE进入 IDLE状态接收 MBMS业务, 如果接收到的 UE上 报消息中认为单播业务的优先级高,网络侧记录 UE感兴趣的 MBMS 频点信息, 待 MBMS频点拥塞解除, 或者 UE发生切换, 或者 UE 的接收状态信息改变后, 再根据所记录的 UE感兴趣的 MBMS频点 信息和 UE接收能力, 考虑 MBMS接收的连续性, 并进行相应处理。
实施例三
本实施例以 LTE***为例, 描述了 UE单独上报 MBMS接收能 力信息的流程, 以及网络侧的相应处理流程。
参见图 6, 为本发明实施例三中在 UE侧的流程示意图, 该流程 可包括:
步骤 601 , UE根据需要, 进入 RRC连接状态。 当然, 如果 UE 当前处于 RRC连接状态, 则该步骤可以省略。
步骤 602, 处于 RRC连接状态的 UE根据需要, 进行 MBMS业 务接收能力的上报。
具体实施时, UE上报 MBMS业务接收能力的触发方式可以有以 下选择之一:
i. 当 eNB进行传统的能力查询时, UE在响应消息中捎带 MBMS 接收能力信息。 当然是否需要捎带 MBMS接收能力信息, 也可以采 取网络开关控制的方式, 例如网络侧隐式(比如新的 MBMS业务连 续性功能设计可能会在***消息中增加某些新的域,则新的域出现代 表开关打开, 否则关闭) 或者显示开关 (例如在***消息中以 lbit 额外指示来代表 eNB是否支持 MBMS能力上报的处理);
ii.定义新的 eNB查询过程,即只有 eNB查询 MBMS接收能力时, UE才根据该查询请求上报 MBMS业务接收能力信息;
iii. UE在进入连接态的第一次 MBMS接收状态信息上报时,通过 上报消息携带 MBMS业务能力信息。 进一步的, 在切换到新小区之 后, 如果 UE被配置为需要立即重新上报一次 MBMS接收状态信息, 则也通过上报消息携带 MBMS业务接收能力信息。
UE上报的 MBMS接收能力信息中可包含用于指示 UE的服务小 区和 MBMS业务接收能力之间关系的比特, 如通过一个或一些比特 指示出以下关系中的一种或多种:
i. UE只能在 Pcell (主载波 )上接收 MBMS业务;
ii. UE可以在任何 Serving cell (服务小区 )上接收 MBMS业务; iii. UE可以在聚合能力范围之内接收 MBMS业务;
iv. UE可以在任何载波接收 MBMS业务(例如单独的 MBMS接 收机)。
另一实施例中, UE上报的 MBMS接收能力信息中包含用于指示 UE能否在多个载波同时接收 MBMS业务的比特,或者包含用于指示 UE能够接收 MBMS业务的载波数量的比特。
在另一实施例中, UE上报的 MBMS接收能力信息中可以包含上 述两种指示作用的比特。
对于 MBMS业务接收能力信息尽量采用最小的编码格式, 来指 示不同的接收能力。 例如以 3比特信息作为能力指示, 其中前两位指 示在哪些载波可以接收 MBMS业务, 第三个比特指示是否具有多个 载波同时接收 MBMS业务的能力。 例如前两位 00代表 UE只能在 Pcell上接收 MBMS业务, 01代表 UE可以在任何 Serving cell (服务 小区)上接收 MBMS业务, 10代表 UE可以在聚合能力范围之内接 收 MBMS业务, 11代表 UE可以在任何载波接收 MBMS业务(例如 单独的 MBMS接收机 ); 第三个比特 1或 0分别代表 UE在前面所指 示的范围内是否支持多个载波同时接收 MBMS业务。
步骤 603, 处于 RRC连接状态的 UE根据需要, 进行 MBMS接 收状态信息的上报。 所述 MBMS接收状态是指 UE感兴趣的 MBMS 业务或 UE正在接收的 MBMS业务, 该 MBMS业务可由 MBMS频 点进行标识, 或 /和由与该 MBMS业务对应的其它信息进行标识(如 service ID、 Service Area ID或者小区标识 )。
其中,关于上报的 MBMS接收状态信息内容可以遵循以下原贝' J : i.包含在上报消息中的 MBMS频点不能超出 UE能够同时接收的 MBMS频点范围, 例如 UE只能接收一个 MBMS频点, 则 UE不能 在上报消息中同时包含两个 MBMS频点;
ii. UE 自行处理各个 MBMS 频点的优先级, 并进一步设置各 MBMS频点的优先级。 进一步的, 当感兴趣的 MBMS频点数目大于 UE可支持的同时接收 MBMS的频点数目时, UE自行放弃低优先级 的 MBMS频点, 只上报较高优先级的 MBMS频点。
关于上报的 MBMS接收状态信息内容, 也可以遵循以下原则之 iii.感兴趣 MBMS频点信息可以超出 UE能够同时支持的 MBMS 频点个数, 并按照排列顺序指示 UE感兴趣 MBMS频点的优先级由 高到低, 以供网络侧由高到低的满足用户需要;
iv.感兴趣 MBMS频点信息可以超出 UE能够同时支持的 MBMS 频点个数, 排列顺序不代表任何优先级关系, 则任意满足 MBMS频 点的接收即可。
对于 MBMS接收状态信息的上报的触发时刻, 同实施例一, 在 此不再赘述。
此后, UE可根据 eNB的配置进行后续操作, 例如重配或者回到 IDLE状态等。
需要说明的是, 上述步骤 602和步骤 603没有严格的时序要求。 参见图 7, 为本发明实施例三在 eNB侧的处理流程, 该流程可包 括:
步骤 701 , eNB对 UE进行配置, 使 UE进入 RRC连接状态。 当 然, 如果 UE当前已经处于 RRC连接状态, 则该步骤可以省略。
步骤 702, eNB接收 UE发来的 MBMS业务接收能力信息。 具体实施时, 对应于图 6所示流程中 UE上报 MBMS业务接收 能力的触发方式, eNB接收 UE发来的 MBMS业务接收能力信息。 如果需要由 eNB触发 UE上报 MBMS业务接收能力信息(如通过新 定义的 eNB查询过程接收)。则在触发 UE发送 MBMS业务接收能力 信息后接收 UE上报的相应信息。
步骤 703, eNB接收 UE发来的 MBMS接收状态信息,并根据情 况处理。
具体实施时, eNB可根据具体情况进行如下处理:
i. UE感兴趣的 MBMS业务已经在 UE当前的接收能力范围之内 的情况下, eNB只需记录 UE的接收情况, 以备后续服务小区更换时 保证 MBMS接收连续性使用;
ii. UE感兴趣的 MBMS业务不在当前的接收范围之内,如果 eNB 根据 UE的 MBMS业务接收能力和 MBMS频点负荷情况, 可以重配 UE的服务小区, 保障单播业务和 MBMS业务同时接收, 则 eNB重 配 UE的服务小区, 并记录 MBMS业务接收信息;
iii. UE感兴趣的 MBMS业务不在当前的接收范围之内,如果 eNB 根据 UE的 MBMS业务接收能力和 MBMS频点负荷情况, 无法重配 UE的服务小区满足单播业务和 MBMS业务同时接收, 则 eNB进一 步判断单播业务和 MBMS业务之间的优先级,如果 MBMS业务优先 级高,则释放 UE回到 IDLE态接收 MBMS业务,如果单播优先级高, 则维持现有配置, 记录 UE的 MBMS业务接收情况;
iv.在感兴趣 MBMS频点多于一个的情况, eNB按照是否有优先 级指示的规定, 尽量满足较多的且较高优先级的 MBMS业务接收。
需要说明的是, 上述步骤 702和步骤 703没有严格的时序要求, 其执行顺序可由 UE侧的上报顺序决定。
基于相同的技术构思,本发明实施例还提供了可应用于上述流程 的终端设备和网络设备。
参见图 8, 为本发明实施例提供的终端设备的结构示意图, 该终 端设备可包括:
发送模块 803, 用于向网络设备发送所述终端感兴趣或正在接收 的 MBMS信息, 以及所述终端对相应 MBMS业务的接收能力信息。
具体的, 发送模块 803具体用于, 通过向网络设备上报消息, 将 所述 MBMS信息以及所述 MBMS业务的接收能力信息发送给所述网 络设备, 其中:
若所述终端感兴趣或正在接收的 MBMS业务所对应的 MBMS频 点, 在所述终端当前配置下的接收能力范围之内, 则所述发送模块向 所述网络设备上报的消息中包括所述 MBMS频点, 以表明所述终端 在当前配置下能够接收相应的 MBMS业务; 或者, 所述终端向所述 网络设备上 >¾的消息中包括所述 MBMS频点和对应的指示信息, 所 述指示信息表明所述终端在当前配置下能够接收对应的 MBMS频点 上的 MBMS业务;
若所述终端感兴趣或正在接收的 MBMS业务所对应的 MBMS频 点, 在所述终端当前配置下的接收能力范围之外, 则所述发送模块向 所述网络设备上报的消息中包括所述 MBMS 频点和对应的指示信 息,所述指示信息表明所述终端在当前配置下无法接收对应的 MBMS 频点上的 MBMS业务。
具体的, 发送模块 803具体用于, 通过向网络设备上报消息, 将 所述 MBMS信息以及所述 MBMS业务的接收能力信息发送给所述网 络设备, 其中:
若所述终端感兴趣或正在接收的 MBMS业务所对应的 MBMS频 点, 在所述终端当前配置下的接收能力范围之内, 则所述发送模块向 所述网络设备上报的消息中包括所述 MBMS频点, 以表明所述终端 在当前配置下能够接收该 MBMS频点上的 MBMS业务;
若所述终端在当前配置下无法接收其感兴趣的 MBMS业务, 并 且无法获取到该 MBMS业务的频点, 则所述发送模块获取该 MBMS 业务对应的其它标识信息,并在向所述网络设备上报的消息中包括所 述 MBMS业务对应的标识信息, 以表明所述终端在当前配置下无法 接收该标识信息对应的 MBMS业务。
具体的, 发送模块 803具体用于, 通过向网络设备上报消息, 将 所述 MBMS信息以及所述 MBMS业务的接收能力信息发送给所述网 络设备, 其中:
所述发送模块向所述网络设备发送第一消息,其中携带有所述终 端在当前配置下的 MBMS业务接收能力信息; 以及, 向所述网络设 备发送第二消息, 其中携带有 MBMS信息。
具体的, 发送模块 803发送的 MBMS接收能力信息中包含用于 指示所述终端的服务小区和 MBMS业务接收能力之间关系的比特。 具体的, 发送模块 803发送的 MBMS接收能力信息中包含用于 指示所述终端能否在多个载波同时接收 MBMS业务的比特, 或者包 含用于指示所述终端能够接收 MBMS业务的载波数量的比特。
具体的,发送模块 803在终端接收到所述网络设备发送的能力查 询请求时, 发送所述第一消息; 或者, 在终端进入连接状态后的第一 次 MBMS接收状态上报时, 发送所述第一消息; 或者, 在终端配置 为切换到目标小区后上报一次 MBMS接收状态信息的情况下, 在切 换到目标小区后发送所述第一消息。
具体的, 发送模块 803上报的消息中, MBMS信息对应设置有 优先级。
具体的, 发送模块 803上报的消息中包括一个或多个 MBMS信 息, 其中, MBMS信息对应的 MBMS频点的数量, 在所述终端能够 同时接收的 MBMS频点数量范围之内。
具体的, 发送模块 803具体用于, 在终端获知用户对已经在空口 发送的 MBMS 业务进行选择接收后, 在等待用户对选择接收的 MBMS 业务开始浏览时刻起的设定时长后, 向所述网络设备上报消 息; 或者, 在终端获知用户对即将在空口发送的 MBMS业务感兴趣 后, 在该 MBMS业务开始时刻之前且距离该开始时刻为设定时长的 时刻, 向所述网络设备上报消息。
具体的 , 发送模块 803具体用于, 若所述终端获知用户对即将在 空口发送的 MBMS业务感兴趣, 且所述终端在当前配置下能够接收 该 MBMS业务,则向所述网络设备上报消息的时刻,距离所述 MBMS 业务开始时刻为第一设定时长;若所述终端获知用户对即将在空口发 送的 MBMS 业务感兴趣, 且所述终端在当前配置下无法接收所述 MBMS业务, 则向所述网络设备上报消息的时刻, 距离所述 MBMS 业务开始时刻为第二设定时长; 其中, 第一设定时长小于第二设定时 长。
进一步的, 上述终端设备还可包括: 获取模块 801 , 用于获取用 户正在接收或关兴趣的 MBMS信息; 确定模块 802, 用于确定所述 终端对相应 MBMS业务的接收能力。 参见图 9, 为本发明实施例提供的网络设备的结构示意图, 该网 络设备可以^ ^站, 该网络设备可包括:
接收模块 901 , 用于接收终端发送的所述终端感兴趣或正在接收 的 MBMS信息以及所述终端对相应 MBMS业务的接收能力信息; 处理模块 902, 用于根据接收到的 MBMS信息以及所述终端对 相应 MBMS业务的接收能力信息进行相应处理。
具体的, 处理模块 902具体用于, 若根据接收到的 MBMS信息 以及所述终端对相应 MBMS业务的接收能力信息, 获知所述终端在 当前配置下能够接收相应 MBMS 业务, 则保存所述终端上报的该 MBMS 信息, 并在为所述终端选择服务小区时参考所保存的该 MBMS信息;
若根据收到的 MBMS信息以及所述终端对相应 MBMS业务的接 收能力信息, 获知所述终端在当前配置下无法接收相应的 MBMS业 务, 且判断允许所述终端变更服务小区, 则对所述终端进行服务小区 重配置, 以保障所述终端能够接收相应的 MBMS业务和单播业务, 保存所述终端上报的该 MBMS信息, 并在为所述终端选择服务小区 时参考所保存的该 MBMS信息;
若根据收到的 MBMS信息以及所述终端对相应 MBMS业务的接 收能力信息, 获知所述终端在当前配置下无法接收相应的 MBMS业 务, 且判断不允许所述终端变更服务小区, 则比较所述终端上报的 MBMS业务与单播业务的优先级; 若 MBMS业务的优先级高于单播 业务, 则释放所述终端的单播业务, 并配置所述终端进入空闲状态接 收 MBMS业务, 否则保存所述终端上报的该 MBMS信息, 并在为所 述终端选择服务小区时参考所保存的该 MBMS信息。
具体的, 处理模块 902具体用于, 在所述终端发送的 MBMS信 息为多个且设置有优先级的情况下, 在为所述终端选择服务小区时, 根据所述终端发送的所述多个 MBMS信息的优先级选择服务小区, 所选择的服务小区能够尽可能保证所述终端接收的 MBMS业务数量 多且优先级高。
进一步的, 上述网络设备还可包括配置模块 903, 用于在所述接 收模块接收终端发送的 MBMS信息以及所述终端对相应 MBMS业务 的接收能力信息之前, 配置所述终端进入连接状态。
综上所述, 本发明实施例给出了一种 MBMS接收能力上报的机 制, 可以使网络侧更好的区分不同用户的情况, 作出合理的配置, 有 利于***性能的整体保证, 更有利于用户体验的提高。
本领域技术人员可以理解实施例中的装置中的模块可以按照实 施例描述进行分布于实施例的装置中,也可以进行相应变化位于不同 于本实施例的一个或多个装置中。上述实施例的模块可以合并为一个 模块, 也可以进一步拆分成多个子模块。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解 到本发明可借助软件加必需的通用硬件平台的方式来实现, 当然也可 以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解, 软件产品的形式体现出来, 该计算机软件产品存储在一个存储介质 中, 包括若干指令用以使得一台终端设备(可以是手机,个人计算机, 服务器, 或者网络设备等)执行本发明各个实施例所述的方法。
以上所述仅是本发明的优选实施方式, 应当指出, 对于本技术领 域的普通技术人员来说, 在不脱离本发明原理的前提下, 还可以做出 若干改进和润饰, 这些改进和润饰也应视本发明的保护范围。

Claims

权利要求
1、一种多媒体广播组播服务 MBMS业务接收和能力信息上报方 法, 其特征在于, 该方法包括:
终端向网络设备发送所述终端感兴趣或正在接收的 MBMS 信 息, 以及所述终端对相应 MBMS业务的接收能力信息。
2、 如权利要求 1所述的方法, 其特征在于, 所述终端通过向网 络设备上报消息,将所述 MBMS信息以及所述 MBMS业务的接收能 力信息发送给所述网络设备, 其中:
若所述终端感兴趣或正在接收的 MBMS业务所对应的 MBMS频 点, 在所述终端当前配置下的接收能力范围之内, 则所述终端向所述 网络设备上报的消息中包括所述 MBMS频点, 以表明所述终端在当 前配置下能够接收该 MBMS频点上的 MBMS业务;
若所述终端在当前配置下无法接收其感兴趣的 MBMS业务, 并 且无法获取到该 MBMS业务的频点,则获取该 MBMS业务对应的其 它标识信息, 并在向所述网络设备上报的消息中包括所述 MBMS业 务对应的标识信息,以表明所述终端在当前配置下无法接收该标识信 息对应的 MBMS业务。
3、 如权利要求 2所述的方法, 其特征在于, 所述 MBMS对应的 标识信息为 MBMS业务标识、 MBMS 务区域标识或 MBMS业务 所属的小区标识。
4、 如权利要求 1所述的方法, 其特征在于, 所述终端通过向网 络设备上报消息,将所述 MBMS信息以及所述 MBMS业务的接收能 力信息发送给所述网络设备, 其中:
所述终端向所述网络设备发送第一消息,其中携带有所述终端在 当前配置下的 MBMS业务接收能力信息;
所述终端向所述网络设备发送第二消息, 其中携带有 MBMS信
5、 如权利要求 4所述的方法, 其特征在于, 所述终端在接收到 所述网络设备发送的能力查询请求时, 发送所述第一消息;
或者, 所述终端在进入连接状态后的第一次 MBMS接收状态上 报时, 发送所述第一消息;
或者, 所述终端在配置为切换到目标小区后上报一次 MBMS接 收状态信息的情况下, 在切换到目标小区后发送所述第一消息。
6、 如权利要求 2或 4所述的方法, 其特征在于, 所述终端上报 的消息中, MBMS信息对应设置有优先级。
7、 如权利要求 2或 4所述的方法, 其特征在于, 所述终端上报 的消息中包括一个或多个 MBMS信息, 其中, MBMS 信息对应的 MBMS频点的数量, 在所述终端能够同时接收的 MBMS频点数量范 围之内。
8、 一种基于如权利要求 1所述方法实现的多媒体广播组播业务 MBMS接收和能力信息接收方法, 其特征在于, 该方法包括:
网络设备接收终端发送的所述终端感兴趣或正在接收的 MBMS 信息以及所述终端对相应 MBMS业务的接收能力信息;
所述网络设备根据接收到的 MBMS 信息以及所述终端对相应 MBMS业务的接收能力信息进行相应处理。
9、 如权利要求 8所述的方法, 其特征在于, 所述网络设备根据 接收到的 MBMS信息以及所述终端对相应 MBMS业务的接收能力信 息进行相应处理的步骤, 包括:
若所述网络设备根据接收到的 MBMS信息以及所述终端对相应 MBMS 业务的接收能力信息, 获知所述终端在当前配置下能够接收 相应 MBMS业务, 则保存所述终端上报的该 MBMS信息, 并在为所 述终端选择服务小区时参考所保存的该 MBMS信息;
若所述网络设备根据收到的 MBMS 信息以及所述终端对相应 MBMS 业务的接收能力信息, 获知所述终端在当前配置下无法接收 相应的 MBMS业务, 且判断允许所述终端变更月良务小区, 则对所述 终端进行服务小区重配置, 以保障所述终端能够接收相应的 MBMS 业务和单播业务, 保存所述终端上报的该 MBMS信息, 并在为所述 终端选择服务小区时参考所保存的该 MBMS信息;
若所述网络设备根据收到的 MBMS 信息以及所述终端对相应 MBMS 业务的接收能力信息, 获知所述终端在当前配置下无法接收 相应的 MBMS业务, 且判断不允许所述终端变更月良务小区, 则比较 所述终端上报的 MBMS业务与单播业务的优先级;若 MBMS业务的 优先级高于单播业务, 则释放所述终端的单播业务, 并配置所述终端 进入空闲状态接收 MBMS业务, 否则保存所述终端上报的该 MBMS 信息,并在为所述终端选择服务小区时参考所保存的该 MBMS信息。
10、 如权利要求 9所述的方法, 其特征在于, 在所述终端发送的 MBMS信息为多个且设置有优先级的情况下, 所述网络设备在为所 述终端选择服务小区时, 根据所述终端发送的所述多个 MBMS信息 的优先级选择服务小区,所选择的服务小区能够尽可能保证所述终端 接收的 MBMS业务数量多且优先级高。
11、 如权利要求 8所述的方法, 其特征在于, 在所述网络设备接 收终端发送的 MBMS信息以及所述终端对相应 MBMS业务的接收能 力信息之前, 还配置所述终端进入连接状态。
12、 一种终端设备, 其特征在于, 包括:
发送模块, 用于向网络设备发送所述终端感兴趣或正在接收的 MBMS信息, 以及所述终端对相应 MBMS业务的接收能力信息。
13、 如权利要求 12所述的终端设备, 其特征在于, 所述发送模 块具体用于, 通过向网络设备上报消息, 将所述 MBMS信息以及所 述 MBMS业务的接收能力信息发送给所述网络设备, 其中:
若所述终端感兴趣或正在接收的 MBMS业务所对应的 MBMS频 点, 在所述终端当前配置下的接收能力范围之内, 则所述发送模块向 所述网络设备上报的消息中包括所述 MBMS频点, 以表明所述终端 在当前配置下能够接收该 MBMS频点上的 MBMS业务;
若所述终端在当前配置下无法接收其感兴趣的 MBMS业务, 并 且无法获取到该 MBMS业务的频点, 则所述发送模块获取该 MBMS 业务对应的其它标识信息,并在向所述网络设备上 ^¾的消息中包括所 述 MBMS业务对应的标识信息, 以表明所述终端在当前配置下无法 接收该标识信息对应的 MBMS业务。
14、 如权利要求 12所述的终端设备, 其特征在于, 所述发送模 块具体用于, 通过向网络设备上报消息, 将所述 MBMS信息以及所 述 MBMS业务的接收能力信息发送给所述网络设备, 其中:
所述发送模块向所述网络设备发送第一消息,其中携带有所述终 端在当前配置下的 MBMS业务接收能力信息; 以及, 向所述网络设 备发送第二消息, 其中携带有 MBMS信息。
15、 如权利要求 14所述的终端设备, 其特征在于, 所述发送模 块具体用于, 在终端接收到所述网络设备发送的能力查询请求时, 发 送所述第一消息; 或者, 在终端进入连接状态后的第一次 MBMS接 收状态上报时, 发送所述第一消息; 或者, 在终端配置为切换到目标 小区后上报一次 MBMS接收状态信息的情况下, 在切换到目标小区 后发送所述第一消息。
16、 一种网络设备, 其特征在于, 包括:
接收模块, 用于接收终端发送的所述终端感兴趣或正在接收的 MBMS信息以及所述终端对相应 MBMS业务的接收能力信息; 处理模块, 用于根据接收到的 MBMS信息以及所述终端对相应 MBMS业务的接收能力信息进行相应处理。
17、 如权利要求 16所述的网络设备, 其特征在于, 所述处理模 块具体用于, 若根据接收到的 MBMS 信息以及所述终端对相应 MBMS 业务的接收能力信息, 获知所述终端在当前配置下能够接收 相应 MBMS业务, 则保存所述终端上报的该 MBMS信息, 并在为所 述终端选择服务小区时参考所保存的该 MBMS信息;
若根据收到的 MBMS信息以及所述终端对相应 MBMS业务的接 收能力信息, 获知所述终端在当前配置下无法接收相应的 MBMS业 务, 且判断允许所述终端变更月良务小区, 则对所述终端进行月良务小区 重配置, 以保障所述终端能够接收相应的 MBMS业务和单播业务, 保存所述终端上报的该 MBMS信息, 并在为所述终端选择服务小区 时参考所保存的该 MBMS信息;
若根据收到的 MBMS信息以及所述终端对相应 MBMS业务的接 收能力信息, 获知所述终端在当前配置下无法接收相应的 MBMS业 务, 且判断不允许所述终端变更服务小区, 则比较所述终端上报的 MBMS业务与单播业务的优先级; 若 MBMS业务的优先级高于单播 业务, 则释放所述终端的单播业务, 并配置所述终端进入空闲状态接 收 MBMS业务, 否则保存所述终端上报的该 MBMS信息, 并在为所 述终端选择服务小区时参考所保存的该 MBMS信息。
18、 如权利要求 17所述的网络设备, 其特征在于, 所述处理模 块具体用于, 在所述终端发送的 MBMS信息为多个且设置有优先级 的情况下, 在为所述终端选择服务小区时, 根据所述终端发送的所述 多个 MBMS信息的优先级选择服务小区, 所选择的服务小区能够尽 可能保证所述终端接收的 MBMS业务数量多且优先级高。
19、 如权利要求 16所述的网络设备, 其特征在于, 还包括配置 模块;
所述配置模块, 用于在所述接收模块接收终端发送的 MBMS信 息以及所述终端对相应 MBMS业务的接收能力信息之前, 配置所述 终端进入连接状态。
PCT/CN2013/071031 2012-01-30 2013-01-28 一种mbms接收和能力传输方法及其装置 WO2013113268A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP13743636.6A EP2811764B1 (en) 2012-01-30 2013-01-28 Mbms service reception and capability transmission method and device
KR1020147024176A KR101636788B1 (ko) 2012-01-30 2013-01-28 Mbms 수신 및 능력 전송을 위한 방법 및 장치
US14/375,462 US9826417B2 (en) 2012-01-30 2013-01-28 MBMS service reception and ability transmission method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210020923.4A CN102572713B (zh) 2012-01-30 2012-01-30 一种mbms接收和能力传输方法及其装置
CN201210020923.4 2012-01-30

Publications (1)

Publication Number Publication Date
WO2013113268A1 true WO2013113268A1 (zh) 2013-08-08

Family

ID=46416945

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/071031 WO2013113268A1 (zh) 2012-01-30 2013-01-28 一种mbms接收和能力传输方法及其装置

Country Status (5)

Country Link
US (1) US9826417B2 (zh)
EP (1) EP2811764B1 (zh)
KR (1) KR101636788B1 (zh)
CN (1) CN102572713B (zh)
WO (1) WO2013113268A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016053066A1 (ko) * 2014-10-03 2016-04-07 엘지전자(주) 무선 통신 시스템에서 셀 단위 보고를 위한 방법 및 이를 위한 장치
EP3087764A4 (en) * 2013-12-23 2016-12-14 ERICSSON TELEFON AB L M (publ) METHODS, USER NODE, AND NETWORK NODE IN MULTIMEDIA BROADCAST MULTICAST SERVICE (MBMS) NETWORK

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102769827A (zh) * 2011-05-02 2012-11-07 上海贝尔股份有限公司 发起mbms业务接收状态报告的方法和设备
CN102572713B (zh) * 2012-01-30 2014-08-20 电信科学技术研究院 一种mbms接收和能力传输方法及其装置
TWI505726B (zh) * 2012-05-18 2015-10-21 Innovative Sonic Corp 在無線通訊系統中改善頻率優先次序的方法及裝置
CN104521251B (zh) * 2013-05-28 2018-12-25 华为技术有限公司 业务传输方法、装置、设备及***
CN104301931A (zh) * 2014-09-24 2015-01-21 中兴通讯股份有限公司 拥塞/过载的控制方法,***,装置和基站
US9622145B2 (en) * 2014-12-05 2017-04-11 At&T Intellectual Property I, L.P. Wireless network architecture for providing media content
JP6290458B2 (ja) * 2015-01-29 2018-03-07 株式会社Nttドコモ ユーザ端末および無線通信方法
US10362449B2 (en) 2015-08-04 2019-07-23 Lg Electronics Inc. Method for receiving broadcast/multicast message in wireless communication system and device therefor
WO2017090953A1 (ko) * 2015-11-26 2017-06-01 엘지전자 주식회사 단말이 관심 있는 mbms 서비스를 결정하는 방법 및 장치
CN109922517A (zh) * 2017-12-13 2019-06-21 成都鼎桥通信技术有限公司 一种降低组播终端功率的方法
EP3836620A4 (en) * 2018-09-19 2021-09-15 Guangdong Oppo Mobile Telecommunications Corp., Ltd. DATA TRANSMISSION PROCESS AND DEVICE, AND STORAGE MEDIA
CN111836210B (zh) * 2019-08-09 2022-03-08 维沃移动通信有限公司 多媒体多播广播业务的配置方法、终端和网络侧设备
CN111836311B (zh) * 2019-08-09 2024-03-19 维沃移动通信有限公司 能力协商方法、终端及网络设备
CN114424663A (zh) * 2019-12-30 2022-04-29 Oppo广东移动通信有限公司 一种业务调度方法及装置、终端设备、网络设备
KR20210156687A (ko) * 2020-06-18 2021-12-27 삼성전자주식회사 전자 장치 및 전자 장치에서의 인접 셀의 신호 품질 측정 방법
CN114079869A (zh) * 2020-08-13 2022-02-22 维沃移动通信有限公司 上报能力的方法、终端设备和网络设备
CN114501340B (zh) * 2020-10-23 2023-03-31 ***通信有限公司研究院 Mbs接收方法、发送方法、装置、终端及基站
CN116250259A (zh) * 2020-12-24 2023-06-09 Oppo广东移动通信有限公司 一种mbs业务的指示方法及装置、终端设备、网络设备
CN116367093A (zh) * 2021-12-27 2023-06-30 维沃移动通信有限公司 多播业务的传输方法、终端及网络侧设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1798063A (zh) * 2004-12-28 2006-07-05 华为技术有限公司 网络侧获知用户接收多媒体广播/组播业务情况的方法
CN102137430A (zh) * 2011-04-02 2011-07-27 电信科学技术研究院 一种上报mbms业务状态的方法及装置
CN102378113A (zh) * 2010-08-12 2012-03-14 中兴通讯股份有限公司 一种多媒体广播多播业务传输方式的转换方法和***
CN102572713A (zh) * 2012-01-30 2012-07-11 电信科学技术研究院 一种mbms接收和能力传输方法及其装置

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070136759A1 (en) * 2003-11-14 2007-06-14 Hai Zhang Method of implementing multicasting service
EP2051408A4 (en) * 2006-08-09 2012-09-12 Mitsubishi Electric Corp DATA COMMUNICATION METHOD AND MOBILE COMMUNICATION SYSTEM
EP2131603B1 (en) * 2007-03-23 2015-09-02 Panasonic Intellectual Property Corporation of America Radio communication base station device and radio communication method
CN101953181A (zh) * 2007-12-17 2011-01-19 三菱电机株式会社 移动通信***
US9173192B2 (en) * 2011-03-17 2015-10-27 Qualcomm Incorporated Target cell selection for multimedia broadcast multicast service continuity
US20130039250A1 (en) * 2011-08-12 2013-02-14 Mediatek, Inc. Method to Indicate MBMS Reception Status to Enable Service Continuity
EP3570606B1 (en) * 2011-08-16 2021-10-06 Telefonaktiebolaget LM Ericsson (publ) Capability extensions for multimedia broadcast multicast services
EP2761927A4 (en) * 2011-09-30 2015-08-12 Intel Corp METHODS OF SIMULTANEOUSLY TRANSPORTING INTERNET TRAFFIC ON MULTIPLE WIRELESS NETWORKS

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1798063A (zh) * 2004-12-28 2006-07-05 华为技术有限公司 网络侧获知用户接收多媒体广播/组播业务情况的方法
CN102378113A (zh) * 2010-08-12 2012-03-14 中兴通讯股份有限公司 一种多媒体广播多播业务传输方式的转换方法和***
CN102137430A (zh) * 2011-04-02 2011-07-27 电信科学技术研究院 一种上报mbms业务状态的方法及装置
CN102572713A (zh) * 2012-01-30 2012-07-11 电信科学技术研究院 一种mbms接收和能力传输方法及其装置

Non-Patent Citations (1)

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

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3087764A4 (en) * 2013-12-23 2016-12-14 ERICSSON TELEFON AB L M (publ) METHODS, USER NODE, AND NETWORK NODE IN MULTIMEDIA BROADCAST MULTICAST SERVICE (MBMS) NETWORK
WO2016053066A1 (ko) * 2014-10-03 2016-04-07 엘지전자(주) 무선 통신 시스템에서 셀 단위 보고를 위한 방법 및 이를 위한 장치
US10313909B2 (en) 2014-10-03 2019-06-04 Lg Electronics Inc. Method and device for cell granularity reporting in wireless communication system

Also Published As

Publication number Publication date
EP2811764A4 (en) 2014-12-31
US9826417B2 (en) 2017-11-21
US20150023243A1 (en) 2015-01-22
KR20140125410A (ko) 2014-10-28
KR101636788B1 (ko) 2016-07-20
CN102572713A (zh) 2012-07-11
EP2811764B1 (en) 2016-11-09
CN102572713B (zh) 2014-08-20
EP2811764A1 (en) 2014-12-10

Similar Documents

Publication Publication Date Title
WO2013113268A1 (zh) 一种mbms接收和能力传输方法及其装置
US9173149B2 (en) Method for adjusting cell reselection priority for avoiding IDC interference in wireless communication system and device for same
EP2852240B1 (en) Signalling about on-going and starting broadcast-service sessions on other frequency carriers
WO2017193380A1 (zh) 通信方法和装置
US20180234896A1 (en) Subband switching method, device, and system
US8195166B1 (en) Methods for mobility management of user equipment in a long term evolution system
EP3783994B1 (en) Communication method, device and system
WO2021164564A1 (zh) 传输组播业务的方法和装置
WO2011018037A1 (zh) 一种配置mbms控制信息的方法、设备和***
JP2017537534A (ja) Embmsセッション中断/停止通知
JPWO2015146285A1 (ja) 装置
WO2013170425A1 (zh) 上报业务指示消息的方法、装置及***
WO2017219363A1 (zh) 信息传输方法和设备
WO2014067465A1 (zh) 辅助信息上报及信息发送方法和设备
WO2022028338A1 (zh) 数据传输方法、终端及网络节点
WO2014082274A1 (zh) 一种基于长期演进***的载波聚合通信方法、装置及***
KR20120114964A (ko) 다중 안테나 무선 통신 시스템에서 단말의 신호 송수신 방법 및 이를 위한 장치
WO2021051320A1 (zh) 一种业务数据传输方法及装置、网络设备、终端设备
WO2022037441A1 (zh) Mbms业务的传输模式指示方法、装置及存储介质
WO2011079821A1 (zh) 进行mbsfn类小区测量的方法和装置
US20160020916A1 (en) Service indication processing method and apparatus
WO2023000334A1 (zh) Pdcch监听方法、装置、设备及存储介质
WO2021142646A1 (zh) 一种业务传输方法及装置、通信设备
WO2012122816A1 (zh) 一种确定用户设备切换的目标小区的方法和***
WO2024113951A1 (en) Systems and methods for supporting multicast reception in rrc_inactive state

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 14375462

Country of ref document: US

REEP Request for entry into the european phase

Ref document number: 2013743636

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2013743636

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 20147024176

Country of ref document: KR

Kind code of ref document: A