Patent Description:
The present application relates to the field of mobile communication, in particular to methods, apparatuses and computer program products for receiving/sending multimedia broadcast multicast service (MBMS), and a computer readable storage medium.

With the development of a communication technology and the enrichment of demands, and with increasing improvements to standard formulation of a fifth generation communication technology, a multimedia broadcast multicast service (MBMS) technology, as a means of efficiently utilizing physical resources, will be applied to the Internet of Vehicles, public safety and other technical fields in a <NUM> R17 version.

At present, for an application scenario of an MBMS service, transmission of MBMS data adopts a scheme of single transmission by a network and passive reception by a terminal. That is, whether the terminal is in a radio resource control (RRC) connected state or a non-RRC connected state, it may passively receive the MBMS data. However, when the data is received in the RRC connected state, a success rate of data reception may be reduced. Especially for the MBMS with high reliability requirements, if the terminal cannot receive the MBMS successfully, normal operation of a terminal service will be affected. 3GPP TS <NUM> (V16. <NUM>) (<NUM>-<NUM>), entitled "<NUM>rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description (Release <NUM>)". <CIT> relates to a data transmission method, apparatus, and system, where the method includes: receiving, by a base station, a Multimedia Broadcast Multicast Service MBMS service transmission request and MBMS service data that are sent by a core network device; after receiving the MBMS service transmission request or the MBMS service data, sending, by the base station, an MBMS service paging message in a cell served by the base station; and sending, by the base station, the MBMS service data to user equipment UE according to the MBMS service transmission request. According to the present invention, a dynamic notification message initiated by a network can be received, and when the network needs to send MBMS service data, a UE can receive the MBMS service data in time. <CIT> discloses that a method for performing a feedback for an evolved-multimedia broadcast multicast service (E-MBMS) by a terminal in a wireless communication system may comprise the steps of: receiving the E-MBMS from a base station; and transmitting feedback information for the E-MBMS in an uplink subframe, wherein the terminal operates in an RRC idle state.

Embodiments of the present application provide a multimedia broadcast multicast service (MBMS) receiving method and apparatus. The method and apparatus are used for improving the reliability of MBMS data transmission.

In a first aspect, a method for receiving a multimedia broadcast multicast service (MBMS) is provided, and includes:.

Optionally, the mapping relationship is carried in an MBMS control message received by the terminal; or the mapping relationship is pre-configured; and the non-RRC connected state comprises: an RRC idle state and/or an RRC inactive state.

Optionally, the mapping relationship includes: a mapping relationship among attribute information, the state instruction and a feedback instruction corresponding to the MBMS; the attribute information includes a name of the MBMS and the reliability requirements of the MBMS; the feedback instruction includes "yes" and "no", and is configured to indicate whether the terminal need to send a feedback message to the network device; and the state instruction comprises TRUE and FALSE.

Optionally, the method further includes:
receiving a retransmitted MBMS from the network device in response to a failure of reception of the first MBMS. The retransmitted MBMS includes the first MBMS or an MBMS obtained by the network device after adjusting a transmission scheme based on a feedback of the terminal on a receiving situation of the first MBMS.

In a second aspect, a method for sending a multimedia broadcast multicast service (MBMS) is provided, and includes:.

Optionally, the mapping relationship is carried in an MBMS control message sent by a network device; and the non-RRC connected state comprises: an RRC idle state and/or an RRC inactive state.

Optionally, the mapping relationship includes: a mapping relationship among attribute information, the state instruction and a feedback instruction corresponding to an MBMS; the attribute information comprises a name of the MBMS and the reliability requirements of the MBMS; the feedback instruction comprises "yes" and "no", and is configured to indicate whether the terminal need to send a feedback message to the network device; and the state instruction comprises TRUE and FALSE.

Optionally, the method further includes:
retransmitting an MBMS to the terminal in response to a failure of reception of the first MBMS. The retransmitted MBMS includes the first MBMS or an MBMS obtained by the network device after adjusting a transmission scheme based on a feedback of the terminal on a receiving situation of the first MBMS.

Optionally, the mapping relationship further includes a feedback instruction, and the feedback instruction is configured for instructing whether the terminal needs to feed back a receiving situation of the first MBMS.

In a third aspect, an apparatus for receiving a multimedia broadcast multicast service (MBMS) is provided, and includes:.

In a fourth aspect, an apparatus for sending a multimedia broadcast multicast service (MBMS) is provided, and includes:.

In a sixth aspect, a computer readable storage medium is provided, the computer readable storage medium stores computer executable instructions which are used for enabling a computer to execute the steps included by the method according to any one of the first aspect or the second aspect.

In a seventh aspect, a computer program product containing instructions is provided. when the computer program product runs on a computer, the computer is enabled to execute the multimedia broadcast multicast service (MBMS) receiving method described in various possible implementations above.

In the embodiments of the present application, the terminal first determines the first MBMS to be initiated, and then determines whether the terminal needs to receive the first MBMS in the RRC connected state or the non-RRC connected state according to the mapping relationship between the first MBMS and the corresponding state instruction. In response to determining that the terminal needs to receive in the RRC connected state, the terminal judges whether its current state is the RRC connected state or the non-RRC connected state. When the current state of the terminal is the non-RRC connected state, the terminal sends the RRC connection establishment request to the network device, and instructs in the request that the cause for establishing the present connection is to receive the MBMS.

That is, when the terminal determines that the first MBMS needs to be received in the RRC connected state, the RRC connection establishment request is sent to the network device, and it is indicated in the connection establishment request that the cause for establishing the connection is to receive the MBMS, so that the terminal may receive the first MBMS in the RRC connected state. In this way, when the terminal is in the non-RRC connected state and needs to receive an MBMS with a high reliability requirement, it may send the connection establishment request to the network device, and enter the RRC connected state to receive the MBMS with the high reliability requirement, so that the reliability of MBMS data transmission is improved.

In order to more clearly illustrate the embodiments of the present application or technical solutions in the prior art, the accompanying drawings needed in the description of the embodiments will be briefly introduced. Obviously, the accompanying drawings in the following description are only some embodiments of the present application.

In order to make the objectives, technical solutions and advantages of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of the present application. Under a condition of no conflict, the embodiments in the present application and the features in the embodiments can be combined arbitrarily with each other. Moreover, although a logical order is shown in the flow chart, in some cases, the steps shown or described may be executed in a different order than here.

The terms "first" and "second" in the description and claims of the present application and the above accompanying drawings are used to distinguish different objects, not to describe a specific order. In addition, the term "include" and any variations thereof are intended to cover non-exclusive protection. For example, a process, method, system, product or device containing a series of steps or units is not limited to the listed steps or units, but optionally also includes the steps or units not listed, or optionally also includes other steps or units fixed to these processes, methods, products or devices. "A plurality of" in the present application may mean at least two, such as two, three or more, which is not limited in the embodiments of the present application.

In addition, the term "and/or" herein is only an association relationship describing associated objects, indicating that there may be three kinds of relationships, for example, A and/or B may mean that there are three cases of A alone, A and B at the same time, and B alone. In addition, the character "/" herein, without special description, generally indicates that the front and rear associated objects are in an "or" relationship.

For ease of understanding, the technical background of the embodiments of the present application is introduced below.

As mentioned earlier, how to improve the reliability of MBMS data transmission is an urgent technical problem to be solved at present. At present, when a terminal receives MBMS data sent by a network device, the terminal does not consider its own state, and whether the terminal is in an RRC connected state or a non-RRC connected state, it always passively receives. Therefore, when the terminal receives MBMS data with high reliability requirements, it may fail to receive, which affects the normal operation of a terminal service, and consequently, it cannot meet the conditions with high reliability requirements during MBMS data transmission.

In order to improve the reliability of MBMS data transmission, the present application provides a scheme of a method for receiving a multimedia broadcast multicast service (MBMS). In the scheme, when the terminal determines that a first MBMS to be received needs to be received in the RRC connected state according to a mapping relationship, it sends a connection establishment request to the network device, and indicates in the request that a cause for establishing a connection is to receive an MBMS, so that the terminal can keep receiving the first MBMS in the RRC connected state, and the reliability of MBMS data transmission is improved.

After introducing the design idea of the embodiments of the present application, application scenarios applicable to the technical solutions of the embodiments of the present application are briefly introduced below. It should be noted that the application scenarios introduced below are only used to illustrate the embodiments of the present application, rather than to limit. During specific implementation, the technical solutions provided by the embodiments of the present application may be flexibly applied according to actual needs.

The claimed invention corresponds to <FIG> (methods) and <FIG>, <FIG> (devices) and to the related text in the description, the other figures and the remaining text of the description are only intended to better explain the claimed invention.

Please refer to <FIG> shows an application scenario that can be used by the technical solutions of the embodiments of the present application. In this application scenario, a terminal <NUM> and a network device <NUM> are included. The terminal <NUM> may be a mobile phone, a tablet computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), etc. The network device <NUM> may be a base station, and the base station may be a commonly used base station, an evolved node base station (eNB), a network side device (such as, a next generation node base station (gNB), or a transmission and reception point) in a <NUM> system, or a cell.

In the embodiments of the present application, the terminal <NUM> determines a first MBMS to be initiated, and it is determined whether the terminal <NUM> receives the first MBMS in an RRC connected state or a non-RRC connected state according to a state instruction in a mapping relationship. If it is determined according to the state instruction that the terminal <NUM> receives the first MBMS in the RRC connected state, the terminal <NUM> judges whether it is currently in the non-RRC connected state. When the terminal <NUM> determines that it is currently in the non-RRC connected state, the terminal <NUM> sends an RRC connection establishment request to the network device <NUM>. The connection establishment request includes first instruction information, which is used for instructing that a cause for establishing a present connection is to receive an MBMS. Therefore, when receiving an MBMS with a high reliability requirement, the terminal <NUM> may enter the RRC connected state to receive, so that the reliability of data transmission is enhanced.

The technical solutions provided by the embodiments of the present application are introduced below in combination with the accompanying drawings of the description.

Referring to <FIG> is an interactive flow of a method for receiving and sending a multimedia broadcast multicast service (MBMS) provided by the embodiments of the present application. The method flow described in <FIG> is as follows:.

In the embodiments of the present application, the mapping relationship may have a variety of situations, including but not limited to the following two mapping relationships.

First, the mapping relationship includes a mapping relationship between attribute information corresponding to an MBMS and an RRC state instruction corresponding to an MBMS. In this mapping relationship, the state instruction corresponding to RRC, for example, may be specifically set as "RrcStateInd". Exemplarily, the mapping relationship may be Table <NUM> below. It should be understood that Table <NUM> is only an example of the mapping relationship, not a limitation, and other forms of the mapping relationship are also feasible.

The attribute information corresponding to the MBMS may include a name of the MBMS and corresponding reliability requirements. For example, the name of the MBMS is first MBMS, it can be seen from Table <NUM> above that the RRC state instruction corresponding to the first MBMS is TRUE (correct), that is, the terminal needs to receive the first MBMS in an RRC connected state. For another example, the name of the MBMS is second MBMS, it can be seen from Table <NUM> above that the RRC state instruction corresponding to the second MBMS is FALSE (error), that is, the terminal does not need to receive the second MBMS in the RRC connected state.

Second, the mapping relationship refers to a mapping relationship among the attribute information, the RRC state instruction, and a feedback instruction corresponding to the MBMS. In this mapping relationship, the feedback instruction, for example, may be set as "HARQFeedbackInd". Accordingly, the mapping relationship may be Table <NUM> below, which is the same as the above Table <NUM>. It should be understood that Table <NUM> is only an example of the mapping relationship, not a limitation, and other forms of the mapping relationship are also feasible.

For example, the name of the MBMS is first MBMS, it can be seen from Table <NUM> above that the RRC state instruction corresponding to the first MBMS is TRUE, at this time, the corresponding feedback instruction is "yes or no", and when the corresponding feedback instruction is "yes", it indicates that the terminal needs to send a feedback message to the network device. When the corresponding feedback instruction is "no", it indicates that the terminal does not need to send the feedback message to the network device.

For another example, the name of the MBMS is second MBMS. It can be seen from Table <NUM> above that the RRC state instruction corresponding to the second MBMS is FALSE, and that the corresponding feedback instruction is "no", which indicates that the terminal does not need to send the feedback message to the network device. In other words, for an MBMS with a low reliability requirement, the terminal does not need to send the feedback message to the network device.

In a possible implementation, the mapping relationship is carried in an MBMS control message received by the terminal. The control message, for example, may be a system message or other MBMS relevant control messages. In another possible implementation, the mapping relationship is pre-configured in each MBMS service.

In the condition that the mapping relationship is carried in the MBMS control message received by the terminal, the terminal needs to receive the mapping relationship from the network device, and the network device can send the mapping relationship in an air interface message. Before the network device sends the mapping relationship, for the MBMS with the high reliability requirement, the network device may select terminals for reporting according to a current network resource condition. When network resources are rich, all terminals may be instructed to send feedback messages to the network device. When the network resources are scarce, the network device may select some terminals to send the feedback messages to the network device, that is, the rest of the terminals do not need to send the feedback messages to the network device. At this time, the feedback instruction determined by the terminals that do not need to send the feedback messages to the network device according to the mapping relationship is "no", and the feedback instruction determined by the terminals that need to send the feedback messages to the network device according to the mapping relationship is "yes".

In the condition that the mapping relationship is pre-configured in each MBMS service, the terminal does not need to receive the mapping relationship from the network device. The feedback instruction in the mapping relationship is also pre-configured, so that for the MBMS with the high reliability requirement, all terminals need to send the feedback messages to the network device. It should be noted that since the mapping relationship is not necessarily sent by the network device, the receiving mapping relationship is represented in the form of a dotted line in <FIG>.

Step <NUM>, determining, by the terminal, a state instruction corresponding to the first MBMS according to the mapping relationship.

In the embodiments of the present application, in the condition that the mapping relationship is Table <NUM> above, the terminal determines according to Table <NUM> that the state instruction corresponding to the first MBMS is that it needs to be received in the RRC connected state and the second MBMS does not need to be received in the RRC connected state. In the condition that the mapping relationship is Table <NUM> above, the terminal determines according to Table <NUM> that the state instruction corresponding to the first MBMS is that it needs to be received in the RRC connected state, the corresponding feedback instruction is that the terminal needs to send a feedback message of a receiving situation of the first MBMS to the network device, the second MBMS does not need to be received in the RRC connected state, and the corresponding feedback instruction is that the terminal does not need to send a feedback message of a receiving situation of the second MBMS to the network device.

In the invention, when the terminal determines the first MBMS to be initiated, the corresponding RRC state instruction may be determined through the mapping relationship corresponding to the first MBMS, so that it is determined that the first MBMS should be received in the RRC connected state or the non-RRC connected state.

Step <NUM>: judging, by the terminal, a current state of the terminal.

In the embodiments of the present application, if the terminal determines that the first MBMS needs to be received in the RRC connected state, the terminal needs to judge its current state. The current state of the terminal may be the RRC connected state or the non-RRC connected state. The non-RRC connected state includes an RRC idle state and/or an RRC inactive state. The RRC inactive state is an RRC state other than the RRC connected state and the RRC idle state. In principle, the RRC inactive state only acts on an access layer between a wireless access network node and a mobile terminal, and does not involve a non-access layer between the network device and a core network.

Step <NUM>: sending, by the terminal, an RRC connection establishment request.

In the embodiments of the present application, if the terminal determines according to the mapping relationship that the first MBMS to be initiated needs to be received in the RRC connected state, and the current state of the terminal is the non-RRC connected state, the terminal needs to send the connection establishment request to the network device, and indicates in the connection establishment request that a cause for establishing a present connection is to receive an MBMS.

In a possible implementation, the RRC state instruction of the terminal in the mapping relationship of the first MBMS to be initiated is that it needs to be received in the RRC connected state (that is, RrcStateInd corresponding to the first MBMS is TRUE), and the current state of the terminal is the RRC idle state. At this time, the terminal sends the connection establishment request to the network device, and adds to the RRC connection establishment request RRCConnectionRequest that the cause for establishing the present connection is to receive the MBMS (for example, a specific setting is RRCConnectionRequest (EstablishmentCause==MbmsServiceReceiving)).

For example, a specific setting mode is as follows:
EstablishmentCause: :=ENUMERATED {
emergency, highPriorityAccess, mt-Access, mo-Signalling,
mo-Data,mo-VoiceCall,mo-VideoCall,mo-SMS,mps-PriorityAccess,
mcs-Priority Access,
MbmsServiceReceiving,
spare5, spare4, spare3, spare2, spare1}.

In another possible implementation, the RRC state instruction of the terminal in the mapping relationship of the first MBMS to be initiated is that it needs to be received in the RRC connected state (that is, RecStateInd corresponding to the first MBMS is TRUE), and the current state of the terminal is the RRC inactive state. At this time, the terminal sends a connection resume request (for example, it may also be called a reconnection establishment request) to the network device, and sets a cell "resumeCause" as a new cause for receiving the MBMS in the reconnection establishment request RRCResumeRequest or RRCResumeRequest1 (for example, it may be specifically set as RRCResumeRequest/RRCResumeRequest1 (resumeCause=MbmsServiceReceiving)).

For example, the specific setting mode is as follows:
ResumeCause: :=ENUMERATED {
emergency, highPriorityAccess, mt-Access, mo-Signalling,
mo-Data,mo-VoiceCall,mo-VideoCall,mo-SMS,rna-Update,mps-PriorityAccess,
mcs-Priority Access,
MbmsServiceReceiving,
spare1, spare2, spare3, spare4, spare5}.

In some embodiments, the RRC state instruction of the terminal in the mapping relationship of the first MBMS to be initiated is that it needs to be received in the RRC connected state (that is, RrcStateInd corresponding to the first MBMS is True), and the current state of the terminal is the RRC connected state, so that the terminal does not need to send the connection establishment request to the network device, and may directly receive the first MBMS in the current state.

In a specific implementation process, when the terminal is in different states, the connection establishment requests sent to the network device are different, that is, cells in the connection establishment causes are different. In this way, the terminal may inform the network device of its own state through the cause for establishing the present connection, so that the network device is aware of the state of the terminal, and configures resources for the terminal according to the state of the terminal.

Step <NUM>, sending, by the network device, a configuration message used for instructing the terminal to connect to the network device to the terminal.

In the embodiments of the present application, after the network device receives the connection establishment request sent by the terminal, the state of the terminal may be determined from the connection establishment cause, then an accessible channel and other information is allocated for the terminal, and a configuration message of an accessed channel and other information is sent to the terminal.

In a specific implementation process, the terminal sends different connection establishment requests to the network device according to different states, so that the network device may be aware of the current state of the terminal, so as to reasonably allocate the resources.

Step <NUM>, the terminal connects to the network device and enters the RRC connected state based on the configuration message.

In the embodiments of the present application, the terminal connects to the network device and enters the RRC connected state according to the configuration message sent by the network device.

Step <NUM>: receiving, by the terminal, the first MBMS.

Step <NUM>: sending, by the terminal, feedback information aiming at a receiving situation of the first MBMS.

In the embodiments of the present application, after receiving the first MBMS sent by the network device, the terminal sends the feedback information of the receiving situation of the first MBMS to the network device, so that the network device may judge whether the terminal successfully receives the first MBMS according to the feedback information. Specifically, a process for the terminal to feed back the receiving situation of the first MBMS to the network device is that an RRC layer of the terminal instructs a physical layer to start hybrid automatic repeat request (HARQ) feedback for MBMS service data scheduled by corresponding G-RNTI mapped to the first MBMS, and when the physical layer receives MBMS user data scheduled by the G-RNTI, HARQ feedback is performed.

In a specific implementation process, the terminal feeds back a receiving situation of an MBMS to be received to the network device, so that the network device may accordingly adjust a transmission scheme according to the feedback information.

In a possible implementation, before sending the feedback information of the receiving situation of the first MBMS to the network device, the terminal may further judges that whether the terminal needs to send the feedback message to the network device according to the mapping relationship corresponding to the first MBMS (for example, when the mapping relationship is Table <NUM> above, whether the terminal needs to send the feedback message to the network device may be determined according to the mapping relationship of Table <NUM>). The receiving situation of the first MBMS is fed back to the network device when it is determined that the terminal needs to feed back the receiving situation of the first MBMS. For example, when the terminal receives the second MBMS sent by the network device in the RRC connected state, it can be seen from Table <NUM> above that the mapping relationship corresponding to the second MBMS is that the reliability requirement of the second MBMS is low, it does not need to be received in the RRC connected state, and the terminal does not need to send feedback information of a receiving situation of the second MBMS of the terminal to the network device. At this time, although the second MBMS is received in the RRC connected state, the terminal does not need to feed back the receiving situation of the second MBMS to the network device.

In a specific implementation process, the terminal selectively enters the RRC_CONNECTED state according to different reliability requirements of different MBMSs, and performs HARQ feedback, which meets different reliability requirements of the different MBMSs.

Step <NUM>: retransmitting, by the network device, an MBMS to the terminal in response to a failure of reception of the first MBMS.

In the embodiments of the present application, the terminal feeds back the receiving situation of the first MBMS to the network device. When the network device determines that the terminal fails to receive the first MBMS according to the feedback information sent by the terminal, the network device adjusts a transmission scheme of the first MBMS according to the feedback from the terminal. In a possible implementation, the network device retransmits old data (that is, retransmits the data that the terminal fails to receive) for data of the first MBMS on which the terminal feeds back failure of reception. In another possible implementation, the network device adjusts the transmission scheme of the first MBMS, for example, adjusts a transmit power, or adjusts a modulation and coding scheme (MCS), and then transmits the data through a new transmission scheme.

In a specific implementation process, the network device retransmits according to the feedback of the terminal on the receiving situation of the first MBMS data, or adjusts the transmission scheme according to the feedback of the terminal on the receiving situation of the first MBMS data, which can effectively improve the reliability of data transmission.

In some embodiments, the terminal determines according to the mapping relationship that the state instruction corresponding to the first MBMS further includes various cases. For ease of understanding, the following examples are used for description.

In step <NUM> in the above embodiments, when the terminal determines that the state instruction corresponding to the first MBMS is the non-RRC connected state, and current state of the terminal is the non-RRC connected state, the terminal does not need to switch the current state. At this time, the terminal does not need to send request information for switching the current state to the network device, and instead, directly receives the first MBMS in the current state.

In step <NUM> in the above embodiments, when the terminal determines that the state instruction corresponding to the first MBMS is the non-RRC connected state, and its current state is the RRC connected state, the terminal may choose to receive the first MBMS in the RRC connected state, and may also choose to receive by switching the current state to the non-RRC connected state. If the terminal chooses to receive the first MBMS in the current state (namely the RRC connected state), after receiving is completed, the terminal does not need to send the feedback message of the receiving situation of the first MBMS to the network device (it may be determined according to the mapping relationship that for the MBMS service received in the non-RRC connected state, the feedback message does not need to be sent to the network device). If the terminal chooses to switch the current state to the non-RRC connected state, the terminal sends a connection release request to the network device, and indicates in the request whether the current state needs to be switched to the RRC idle state or the RRC inactive state. After the terminal state is successfully switched, the first MBMS is received in the state after switching (the RRC idle state or the RRC inactive state).

In step <NUM> in the above embodiments, when the terminal determines that the state instruction corresponding to the first MBMS is the RRC connected state, and its current state is the RRC connected state, the terminal may directly receive the first MBMS, and does not need to send the connection establishment request to the network device.

In step <NUM> in the above embodiments, when the terminal determines that the state instruction corresponding to the first MBMS is the RRC connected state, and its current state is the non-RRC connected state, the terminal may execute step <NUM> to step <NUM>.

In a specific implementation process, when the terminal receives the MBMS service with the high reliability requirement, it may enter the RRC connected state to receive, and send the feedback message of the receiving situation of the MBMS to the network device, so that the network device may adjust the transmission scheme timely when the terminal fails to receive, and the reliability of data transmission is improved.

Based on the same inventive concept, the embodiments of the present application provide an apparatus for receiving a multimedia broadcast multicast service (MBMS). The apparatus receiving a multimedia broadcast multicast service (MBMS) can realize functions corresponding to the above-mentioned the method for receiving a multimedia broadcast multicast service (MBMS). The apparatus for receiving the multimedia broadcast multicast service (MBMS) may be a hardware structure, a software module, or a combination of the hardware structure and the software module. The apparatus may be realized by a chip system, and the chip system may be composed of chips, or may contain a chip and other discrete devices. Please refer to <FIG>, the multimedia broadcast multicast service (MBMS) receiving apparatus includes a processing module <NUM> and a communication module <NUM>.

The processing module <NUM> is configured to determine a first MBMS to be initiated;.

In a possible implementation, the mapping relationship is carried in an MBMS control message received by the terminal; or the mapping relationship is pre-configured.

In a possible implementation, the mapping relationship includes: a mapping relationship among attribute information, the state instruction and a feedback instruction corresponding to the MBMS.

In a possible implementation, the communication module <NUM> is further configured to:.

In a possible implementation, after the communication module <NUM> receives the first MBMS, the communication module <NUM> is further configured to:
send feedback information used for instructing whether the terminal successfully receives the first MBMS.

In a possible implementation, the communication module <NUM> is further configured to:
receive an MBMS retransmitted from the network device in response to a failure of reception of the first MBMS. The retransmitted MBMS includes an MBMS adjusted by the network device based on related information of the first MBMS.

In a possible implementation, the processing module <NUM> is further configured to:.

In a possible implementation, the non-RRC connected state includes: an RRC idle state and/or an RRC inactive state.

All relevant contents of the steps involved in the embodiments of the above-mentioned method for receiving the multimedia broadcast multicast service (MBMS) may be cited in the functional descriptions of functional modules corresponding to the multimedia broadcast multicast service (MBMS) receiving apparatus in the embodiment of the present application, which will not be repeated here.

Based on the same inventive concept, the embodiments of the present application provide an apparatus for sending a multimedia broadcast multicast service (MBMS). The multimedia broadcast multicast service (MBMS) sending apparatus can realize functions corresponding to the above-mentioned method for sending the multimedia broadcast multicast service (MBMS). The multimedia broadcast multicast service (MBMS) sending apparatus may be a hardware structure, a software module, or a combination of the hardware structure and the software module. The MBMS sending apparatus may be realized by a chip system, and the chip system may be composed of chips, or may contain a chip and other discrete devices. Please refer to <FIG>, the multimedia broadcast multicast service (MBMS) sending apparatus includes a communication module <NUM> and a processing module <NUM>.

The communication module <NUM> is configured to send a mapping relationship to a terminal, the mapping relationship includes a state instruction corresponding to a first MBMS, and the state instruction is used for instructing the terminal to receive the first MBMS in an RRC connected state or a non-RRC connected state;
the communication module <NUM> is further configured to receive an RRC connection establishment request sent by the terminal, the RRC connection establishment request includes first instruction information, and the first instruction information is configured for instructing that a cause for the terminal to establish a present connection is to receive an MBMS.

In a possible implementation, the mapping relationship is carried in an MBMS control message sent by a network device.

In a possible implementation, after the communication module <NUM> sends the first MBMS to the terminal, the communication module <NUM> is further configured to:
receive feedback information sent by the terminal and used for instructing whether the terminal successfully receives the first MBMS.

In a possible implementation, the apparatus further includes:
a processing module <NUM>, configured to control the communication module to retransmit an MBMS to the terminal in response to a failure of reception of the first MBMS, and the retransmitted MBMS includes an MBMS adjusted by the processing module based on related information of the first MBMS.

In a possible implementation, the mapping relationship further includes a feedback instruction, and the feedback instruction is used for instructing whether the terminal needs to feed back a receiving situation of the first MBMS.

All relevant contents of the steps involved in the embodiments of the above-mentioned MBMS sending method may be cited in the functional descriptions of functional modules corresponding to the MBMS sending apparatus in the embodiment of the present application, which will not be repeated here.

The division of modules in the embodiments of the present application is schematic, which is only a logical function division, and there may be other division modes in actual implementation. In addition, the functional modules in each embodiment of the present application may be integrated in one processor, or may exist physically alone; or two or more modules may be integrated in one module. The above integrated modules may be realized in the form of hardware, and may also be realized in the form of software functional modules.

Based on the same inventive concept, the embodiments of the present application provide an electronic device. Please refer to <FIG>, the electronic device includes at least one processor <NUM> and a memory <NUM> connected to the at least one processor, and a specific connection medium between the processor <NUM> and the memory <NUM> is not limited in the embodiment of the present application. <FIG> takes the situation that the processor <NUM> and the memory <NUM> are connected through a bus <NUM> as an example, the bus <NUM> is represented by a thick line in <FIG>, and a connection mode between other components is only for schematic illustration, rather than to generate limitation. The bus <NUM> may be divided into an address but, a data bus, a control bus, etc. For ease of representation, only one thick line is used in <FIG> for representation, but it does not mean that there is only one bus or one type of bus.

In the embodiments of the present application, the memory <NUM> stores instructions that may be executed by the at least one processor <NUM>. By executing the instructions stored in the memory <NUM>, the at least one processor <NUM> may execute the steps included in the above-mentioned MBMS receiving or sending method.

The processor <NUM> is a control center of the electronic device, which may use various interfaces and lines to connect various parts of the whole electronic device. The electronic device is monitored as a whole by running or executing the instructions stored in the memory <NUM> and calling data stored in the memory <NUM>, and various functions and processing data of the electronic device. Optionally, the processor <NUM> may include one or more processing units, the processor <NUM> may integrate an application processor and a modem processor. The application processor mainly processes an operation system, an application program, etc., and the modem processor mainly processes wireless communication. It can be understood that the above modem processor may also not be integrated into the processor <NUM>. In some embodiments, the processor <NUM> and the memory <NUM> may be implemented on the same chip, and in some embodiments, they may be implemented separately on separate chips.

The processor <NUM> may be a general-purpose processor, such as a central processing unit (CPU), a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device and a discrete hardware component, which can realize or execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the MBMS receiving or sending method disclosed in combination with the embodiments of the present application may be directly reflected in the execution of the hardware processor, or a combination of hardware and software modules in the processor.

As a non-transitory computer-readable storage medium, the memory <NUM> may be configured to store a nonvolatile software program, a nonvolatile computer executable program and a module. The memory <NUM> may include at least one type of storage medium, such as a flash memory, a hard disk, a multimedia card, a card type memory, a random access memory (RAM), a static random access memory (SRAM), a programmable read only memory (PROM), a read only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic memory, a magnetic disk, an optical disk, etc. The memory <NUM> is any other medium that may be configured to carry or store desired program codes in the form of instructions or data structures and may be accessed by a computer, but is not limited thereto. The memory <NUM> in the embodiments of the present application may further be a circuit or any other apparatus capable of realizing a storage function for storing program instructions and/or data.

By designing and programming the processor <NUM>, the codes corresponding to the MBMS receiving or sending method introduced in the above-mentioned embodiments may be solidified into a chip, so that the chip may execute the steps of the above-mentioned MBMS receiving or sending method during running, and how to design and program the processor <NUM> is a well-known technology known to those skilled in the art, which will not be repeated here.

Based on the same inventive concept, the embodiments of the present application further provides a non-transitory computer readable storage medium, which stores computer instructions, and when the computer instructions run on a computer, the computer is enabled to execute the steps of the above-mentioned MBMS receiving or sending method.

In some possible implementations, various aspects of the MBMS receiving or sending method provided by the present application may further be realized in the form of a program product, which includes a program code. When the program product runs on an electronic device, the program code is used for enabling a detection device to execute the steps in the MBMS receiving or sending method according to various exemplary embodiments of the present application described above in this specification.

Those skilled in the art will appreciate that embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may take the form of full hardware embodiments, full software embodiments, or embodiments combining software and hardware aspects. Further, the present application may take the form of computer program products implemented on one or more computer usable storage media (including but not limited to a disk memory, a CD-ROM, an optical memory, etc.) containing computer usable program codes.

The present application is described with reference to flow charts and/or block diagrams of methods, devices (systems) and computer program products according to the present application. It should be understood that each flow and/or block in the flow charts and/or block diagrams and the combination of flows and/or blocks in the flow charts and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing devices to generate a machine, so that an apparatus for realizing functions specified in one or more flows of the flow charts and/or one or more blocks of the block diagrams is generated by the instructions executed by the processor of a computer or other programmable data processing devices.

These computer instructions may also be stored in a computer-readable memory that can guide a computer or other programmable data processing devices to work in a specific mode, so that the instructions stored in the computer-readable memory generate a manufactured product including an instruction apparatus, and the instruction apparatus realizes the functions specified in one or more flows of the flow charts and/or one or more blocks of the block diagrams.

Claim 1:
A method for receiving a multimedia broadcast multicast service, MBMS, applied to a terminal, and comprising:
determining (<NUM>) a first MBMS to be initiated;
characterized in that, the method further comprises: determining (<NUM>) a state instruction corresponding to the first MBMS according to a mapping relationship, wherein the state instruction is configured for instructing the terminal to receive the first MBMS in an RRC connected state or a non-RRC connected state;
determining (<NUM>), by the terminal, whether the terminal is currently in the non-RRC connected state in a case that the state instruction is configured for instructing the terminal to receive the first MBMS in the RRC connected state; and
sending (<NUM>) an RRC connection establishment request to a network device in a case that the terminal is currently in the non-RRC connected state, wherein the RRC connection establishment request comprises first instruction information, and the first instruction information is configured for instructing that a cause for establishing a present connection is to receive the first MBMS.