WO2013113268A1 - 一种mbms接收和能力传输方法及其装置 - Google Patents
一种mbms接收和能力传输方法及其装置 Download PDFInfo
- 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
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/58—Message adaptation for wireless communication
-
- 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/75—Media network packet handling
- H04L65/765—Media network packet handling intermediate
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing 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/442—Monitoring 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/44209—Monitoring of downstream path of the transmission network originating from a server, e.g. bandwidth variations of a wireless network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network 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/63—Control 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/637—Control signals issued by the client directed to the server or network components
- H04N21/6371—Control signals issued by the client directed to the server or network components directed to network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network 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/63—Control 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/64—Addressing
- H04N21/6405—Multicasting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network 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/63—Control 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/647—Control 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/64723—Monitoring of network processes or resources, e.g. monitoring of network load
- H04N21/64738—Monitoring network characteristics, e.g. bandwidth, congestion level
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/40—Connection management for selective distribution or broadcast
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
- H04W8/24—Transfer 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
Description
Claims
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)
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)
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)
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)
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 |
-
2012
- 2012-01-30 CN CN201210020923.4A patent/CN102572713B/zh active Active
-
2013
- 2013-01-28 KR KR1020147024176A patent/KR101636788B1/ko active IP Right Grant
- 2013-01-28 WO PCT/CN2013/071031 patent/WO2013113268A1/zh active Application Filing
- 2013-01-28 US US14/375,462 patent/US9826417B2/en active Active
- 2013-01-28 EP EP13743636.6A patent/EP2811764B1/en active Active
Patent Citations (4)
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)
Title |
---|
See also references of EP2811764A4 * |
Cited By (3)
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 |