Patent Description:
In a New Radio (NR) system, an MBS service does not always exist in a cell. For example, there is no MBS service in a cell for a period of time, but after a period of time, the cell starts to send an MBS service again. From a point of view of a terminal device, after obtaining MBS configuration information, the terminal device will receive an MBS service according to the MBS configuration information, without considering whether the MBS service exists, which leads to a problem of power waste of the terminal device.

3GPP Draft S2-<NUM> and 3GPP Draft R2-<NUM> disclose art related to the present disclosure.

Accompanying drawings described herein are intended to provide further understanding of the present application, and constitute a part of the present application. Exemplary embodiments of the present application and descriptions thereof are intended to explain the present application, but do not constitute an inappropriate limitation to the present application.

Technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. It is apparent that the embodiments described are just a part of the embodiments of the present application, rather than all of the embodiments of the present application. Based on the embodiments of the present application, all other embodiments achieved by a person of ordinary skill in the art without making inventive efforts are within the protection scope of the present application.

The technical solutions of the embodiments of the present application may be applied to various communication systems, such as a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD) system, a system, a <NUM> system or a future communication system.

Illustratively, a communication system <NUM> to which an embodiment of the present application is applied is shown in <FIG>. The communication system <NUM> may include a network device <NUM>. The network device <NUM> may be a device that communicates with a terminal <NUM> (or referred to as a communication terminal, or a terminal). The network device <NUM> may provide communication coverage for a specific geographical area, and may communicate with a terminal located within the coverage area. Optionally, the network device <NUM> may be an Evolutional Node B (eNB or eNodeB) in an LTE system, or a radio controller in a Cloud Radio Access Network (CRAN), or the network device may be a mobile switching center, a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a network side device in a <NUM> network, or a network device in a future communication system, etc..

The communication system <NUM> further includes at least one terminal <NUM> located within the coverage area of the network device <NUM>. The "terminal" as used herein includes, but is not limited to, an apparatus configured to receive/send communication signals via a wired line connection, for example, via a Public Switched Telephone Networks (PSTN), a Digital Subscriber Line (DSL), a digital cable, or a direct cable; and/or another data connection/network; and/or via a wireless interface, for example, for a cellular network, a Wireless Local Area Network (WLAN), a digital television network such as a Digital Video Broadcasting-Handheld (DVB-H) network, a satellite network, or an Amplitude Modulation - Frequency Modulation (AM-FM) broadcast transmitter; and/or another terminal; and/or an Internet of Things (IoT) device. A terminal configured to communicate via a wireless interface may be referred to as "a wireless communication terminal", "a wireless terminal", or "a mobile terminal". Examples of the mobile terminal include, but are not limited to, a satellite or cellular phone; a Personal Communications System (PCS) terminal capable of combining a cellular radio phone with data processing, facsimile, and data communication capabilities; a Personal Digital Assistant (PDA) that may include a radio phone, a pager, internet/intranet access, a Web browser, a memo pad, a calendar, a Global Positioning System (GPS) receiver; and a conventional laptop and/or palmtop receiver or another electronic apparatus including a radio phone transceiver. The terminal may refer to an access terminal, a User Equipment (UE), a subscriber unit, a subscriber station, a mobile station, a mobile platform, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user apparatus. The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with a wireless communication function, a computing device, or another processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal in a <NUM> network, or a terminal in future evolved Public Land Mobile Network (PLMN), etc..

Optionally, Device to Device (D2D) communication may be performed between terminals <NUM>.

Optionally, a <NUM> communication system or a <NUM> network may also be referred to as a New Radio (NR) system or an NR network.

<FIG> illustrates exemplarily one network device and two terminals. Optionally, the communication system <NUM> may include a plurality of network devices, and other numbers of terminals may be included within a coverage area of each network device, which is not limited in the embodiments of the present application.

Optionally, the communication system <NUM> may also include another network entity, such as a network controller, a mobile management entity, etc., which is not limited in the embodiments of the present application.

It should be understood that a device with a communication function in a network/system in the embodiments of the present application may also be referred to as a communication device. Taking the communication system <NUM> shown in <FIG> as an example, communication devices may include a network device <NUM> and a terminal <NUM> which have communication functions, and the network device <NUM> and the terminal <NUM> may be specific devices described above, and will not be described repeatedly herein. The communication device may further include another device in the communication system <NUM>, such as a network controller, a mobile management entity, and another network entity, which is not limited in the embodiments of the present application.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" herein refers to an association relationship describing associated objects only, which indicates that three kinds of relationships may exist, for example, A and/or B may indicate three cases: A alone, both A and B at the same time, and B alone. In addition, the symbol "/" herein generally indicates that objects before and after the symbol "/" have an "or" relationship.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions related to the embodiments of the present application will be explained below.

With people's pursuit for rate, latency, high-speed mobility, and energy efficiency, and diversity and complexity of services in the future life, therefore, 3rd Generation Partnership Project (3GPP) International Standardization Organization began the research and the development of <NUM>. Main application scenarios of the <NUM> are: enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), massive Machine-Type Communication (mMTC).

On one hand, the eMBB still aims at enabling users to obtain multimedia contents, services, and data, and demands thereof are growing very rapidly. On the other hand, because eMBBs may be deployed in different scenarios, such as indoor, an urban district, a rural area, or the like, and differences in their capabilities and demands are also relatively large, which cannot be generalized and must be analyzed in detail in combination with specific deployment scenarios. Typical applications of the URLLC include: industrial automation, power automation, telemedicine operation (surgery), traffic safety guarantee, etc. Typical characteristics of the mMTC include: a high connection density, a small data volume, a latency-insensitive service, a low cost and a long service life of modules, etc..

In an early deployment of the NR, a complete NR coverage is difficult to acquire, so typical network coverage is wide-area LTE coverage and isolated-island NR coverage mode. Moreover, a large amount of LTE deployments are below <NUM>, and there are few spectrums below <NUM> which may be used for the <NUM>. Therefore, spectrum applications above <NUM> must be studied for the NR, while coverage of the high frequent band is limited, and signal fade of the high frequent band is fast. Meanwhile, in order to protect early investments of mobile operators in LTE, a working mode of tight interworking between LTE and NR is proposed.

A Multimedia Broadcast Multicast Service (MBMS) is a technology of transmitting data from one data source to multiple terminal devices through shared network resources. This technology can effectively utilize network resources while providing multimedia services, achieving broadcast and multicast of multimedia services at a relatively high rate (e.g., <NUM> kbps).

Due to a relatively low spectrum efficiency of an MBMS, it is not enough to effectively carry and support operations of mobile TV services. Therefore, in LTE, 3GPP explicitly proposes to enhance a support capability for a downlink high-speed MBMS service, and determines design requirements for a physical layer and an air interface.

3GPP Release <NUM> (R9) introduces an evolved MBMS (eMBMS) into LTE. The eMBMS puts forward a concept of a Single Frequency Network (SFN), that is, a Multimedia Broadcast Multicast Service Single Frequency Network (MBSFN). The MBSFN uses a unified frequency to send service data in all cells at the same time, but it must ensure synchronization between cells. This method may greatly improve an overall signal-to-noise ratio distribution of the cells, and spectrum efficiency will be greatly improved accordingly. The eMBMS implements broadcast and multicast of services based on an Internet Protocol (IP) multicast protocol.

In LTE or LTE-Advanced (LTE-A), an MBMS has only a broadcast bearer mode, but no multicast bearer mode. In addition, reception of an MBMS service is applicable to a terminal device in an idle state or a connected state.

A concept of Single Cell Point to Multipoint (SC-PTM) is introduced in 3GPP Release <NUM> (R13), and the SC-PTM is based on MBMS network architecture.

An MBMS introduces new logical channels, including a Single Cell-Multicast Control Channel (SC-MCCH) and a Single Cell-Multicast Transport Channel (SC-MTCH). The SC-MCCH and the SC-MTCH are mapped onto a Downlink-Shared Channel (DL-SCH), and further, the DL-SCH is mapped onto a Physical Downlink Shared Channel (PDSCH), wherein the SC-MCCH and the SC-MTCH are logical channels, the DL-SCH is a transmission channel, and the PDSCH is a physical channel. The SC-MCCH and the SC-MTCH do not support a Hybrid Automatic Repeat reQuest (HARQ) operation.

The MBMS introduces a new System Information Block (SIB) type, i.e. an SIB20. Specifically, configuration information of the SC-MCCH is transmitted through the SIB20 and there is only one SC-MCCH for a cell. The configuration information of the SC-MCCH includes a modification period of the SC-MCCH, a repetition period of the SC-MCCH, a radio frame and a subframe for scheduling the SC-MCCH, and other information. Further, <NUM>) a boundary of the modification period of the SC-MCCH satisfies SFN mod m = <NUM>, wherein SFN represents a system frame number of the boundary, and m is the modification period of the SC-MCCH configured in the SIB20 (i.e. sc-mcch-ModificationPeriod). <NUM>) The radio frame for scheduling the SC-MCCH satisfies: SFN mod mcch-RepetitionPeriod = mcch-Offset, wherein SFN represents a system frame number of the radio frame, mcch-RepetitionPeriod represents a repetition period of the SC-MCCH, and mcch-Offset represents an offset of the SC-MCCH. <NUM>) The subframe for scheduling the SC-MCCH is indicated through sc-mcch-Subframe.

The SC-MCCH is scheduled through a Physical Downlink Control Channel (PDCCH). On one hand, a new Radio Network Temporary Identity (RNTI), namely a Single Cell RNTI (SC-RNTI), is introduced to identify a PDCCH (such as an SC-MCCH PDCCH) used for scheduling the SC-MCCH, and optionally, a fixed value of the SC-RNTI is FFFC. On the other hand, a new RNTI, i.e. a Single Cell Notification RNTI (SC-N-RNTI), is introduced to identify a PDCCH (e.g., a notification PDCCH) for indicating a change notification of the SC-MCCH, and optionally, a fixed value of the SC-N-RNTI is FFFB; further, the change notification may be indicated with one of eight bits of Downlink Control Information (DCI) 1C. In LTE, the configuration information of the SC-PTM is based on the SC-MCCH configured in the SIB20, and then the SC-MCCH configures the SC-MTCH, which is used for transmitting service data.

Specifically, the SC-MCCH transmits only one message (i.e., SCPTMConfiguration), which is used for configuring the configuration information of the SC-PTM. The configuration information of the SC-PTM includes: a Temporary Mobile Group Identity (TMGI), a session Identity (ID), a Group RNTI (G-RNTI), Discontinuous Reception (DRX) configuration information, and SC-PTM service information of a neighbor cell, etc. It should be noted that SC-PTM in R13 does not support a Robust Header Compression (ROHC) function.

Downlink discontinuous reception of SC-PTM is controlled through following parameters: onDurationTimerSCPTM, drx-InactivityTimerSCPTM, SC-MTCH-SchedulingCycle, and SC-MTCH-SchedulingOffset.

A timer onDurationTimerSCPTM is started when [(SFN * <NUM>) + subframe number] modulo (SC-MTCH-SchedulingCycle) = SC-MTCH-SchedulingOffset; a timer drx-InactivityTimerSCPTM is started when downlink PDCCH scheduling is received; a downlink SC-PTM service is received only when the timer onDurationTimerSCPTM or drx-InactivityTimerSCPTM runs.

A concept of MBMS service continuity based on an SIB15, that is, a mode "SIB15 + MBMSInterestIndication", is adopted for SC-PTM service continuity. Service continuity of a terminal device in an idle state is based on a concept of frequency priority.

In a technical solution of an embodiment of the present application, a new SIB (called a first SIB) is defined, the first SIB includes configuration information of a first MCCH, here, the first MCCH is a control channel of an MBMS service, in other words, the first SIB is used for configuring configuration information of a control channel of an NR MBMS, and optionally, the control channel of the NR MBMS may also be called an NR MCCH (i.e. the first MCCH).

Further, the first MCCH is used for carrying a first signaling, and a name of the first signaling is not limited in an embodiment of the present application, for example, the first signaling is a signaling A. The first signaling includes configuration information of at least one first MTCH, here, the first MTCH is a service channel of an MBMS service (also called a data channel or a transmission channel), and the first MTCH is used for transmitting MBMS service data (such as NR MBMS service data). In other words, the first MCCH is used for configuring configuration information of a service channel of an NR MBMS, and optionally, the service channel of the NR MBMS may also be referred to as an NR MTCH (i.e. the first MTCH).

Specifically, the first signaling is used for configuring a service channel of an NR MBMS, service information corresponding to the service channel, and scheduling information corresponding to the service channel. Further, optionally, the service information corresponding to the service channel, such as a TMGI, a session id, and other identification information for identifying a service. The scheduling information corresponding to the service channel, such as an RNTI used when MBMS service data corresponding to the service channel is scheduled, such as a G-RNTI and DRX configuration information.

It should be noted that transmission of the first MCCH and the first MTCH is based on PDCCH scheduling. Among them, a unique identify of a whole network is used for an RNTI used by a PDCCH for scheduling the first MCCH, that is, it is a fixed value. The RNTI used by the PDCCH for scheduling the first MTCH is configured through the first MCCH.

It should be noted that naming for the first SIB, the first MCCH, and the first MTCH is not limited in the embodiments of the present application. For convenience of description, the first SIB may also be abbreviated as SIB, the first MCCH may also be abbreviated as MCCH, the first MTCH may also be abbreviated as MTCH, a PDCCH for scheduling the MCCH (i.e., a MCCH PDCCH) is configured and notified through the SIB, wherein a PDSCH for transmitting the MCCH (i.e., a MCCH PDSCH) is scheduled through DCI carried by the MCCH PDCCH. Further, M PDCCHs for scheduling the MTCH (i.e., MTCH <NUM> PDCCH, MTCH <NUM> PDCCH,. , MTCH M PDCCH) are configured through the MCCH, wherein a PDSCH used for transmitting MTCH n (i.e., MTCH N PDSCH) is scheduled through DCI carried by MTCH n PDCCH, and n is an integer greater than or equal to <NUM> and less than or equal to M. The MCCH and the MTCH are mapped onto a DL-SCH, and further, the DL-SCH is mapped onto a PDSCH, wherein the MCCH and the MTCH are logical channels, the DL-SCH is a transmission channel, and the PDSCH is a physical channel.

It should be noted that the MBMS service in the above solution includes, but is not limited to, a multicast service and a multicast service. Embodiments of the present application are illustrated with an MBS service as an example, and description of the "MBS service" may also be replaced with the "multicast service" or the "multicast service" or the "MBMS service".

In an NR MBS service, an MBS service does not always exist in a cell. For example, there is no MBS service in a cell for a period of time, but after a period of time, the cell starts to send an MBS service again. From a point of view of a terminal device, after obtaining MBS configuration information, the terminal device will receive an MBS service according to the MBS configuration information, without considering whether the MBS service exists or not, which bring a problem of power waste to the terminal device. To this end, following technical solutions of the embodiments of the present application are proposed.

<FIG> is a first schematic flowchart of a method for managing an MBS service according to an embodiment of the present application. As shown in <FIG>, the method or managing an MBS service includes following acts.

In act <NUM>, a terminal device receives a first command sent by a network device, and the first command is used for deactivating at least one MBS service and/or activating at least one MBS service.

In an embodiment of the present application, the network device sends the first command to the terminal device, and accordingly, the terminal device receives the first command sent by the network device, wherein the first command is used for deactivating at least one MBS service and/or activating at least one MBS service.

Here, optionally, the network device may be a base station, such as a gNB.

In an optional manner, if a network device side does not have service data of an MBS service (i.e., the network device does not send service data of an MBS service), the network device decides to deactivate the MBS service and sends a first command to the terminal device, wherein the first command is used for deactivating the MBS service. Here, the first command may also be referred to as a command for deactivating the MBS service (simply referred to as a deactivation command).

It should be noted that the above solution is illustrated by taking deactivation of one MBS service as an example, and a situation of multiple MBSs is also applicable, for example, the network device decides to deactivate multiple MBS services and sends a first command to the terminal device, and the first command is used for deactivating the multiple MBS services.

In another optional manner, if service data of an MBS service arrives at the network device side and the MBS service is in a deactivated state, the network device decides to activate the MBS service and sends a first command to the terminal device, and the first command is used for activating the MBS service. Here, the first command may also be referred to as a command for activating the MBS service (simply referred to as an activation command).

It should be noted that the above solution is illustrated by taking activation of one MBS service as an example, and a situation of multiple MBSs is also applicable, for example, the network device decides to activate multiple MBS services and sends a first command to the terminal device, and the first command is used for activating the multiple MBS services.

It should be noted that activating an MBS service may also be understood as activating an MBS session. For example, activating an MBS service may also be understood as activating an MBS session, and activating multiple MBS services may also be understood as activating multiple MBS sessions. For example, deactivating one MBS service may also be understood as deactivating one MBS session, and deactivating multiple MBS services may also be understood as deactivating multiple MBS sessions.

In an embodiment of the present application, the first command is carried in Downlink Control Information (DCI), or in a Media Access Control Control Element (MAC CE), or in system broadcast information, or in a dedicated Radio Resource Control (RRC) signaling. Specific implementation of the first command will be described in detail below.

Specifically, the first command is used for deactivating one MBS service, and scheduling information of DCI or a MAC CE carrying the first command is scrambled through a first G-RNTI, which is a G-RNTI corresponding to the MBS service.

In an optional manner, in a case that the first command is carried in DCI, the DCI includes N1-bits indication information, N1 is a positive integer, and the N1-bits indication information is used for indicating to deactivate the MBS service.

For example, a value of N1 is <NUM>, and DCI includes <NUM>-bit indication information. A value of the <NUM>-bit indication information is "<NUM>", which is used for indicating to deactivate the MBS service, and the value of the <NUM>-bit indication information is "<NUM>", which is used for indicating to activate the MBS service; or, a value of the <NUM>-bitf indication information is "<NUM>", which is used for indicating to deactivate the MBS service, and the value of the <NUM>-bit indication information is "<NUM>", which is used for indicating to activate the MBS service.

In an optional manner, in a case that the first command is carried in a MAC CE, the MAC CE includes N2-bits indication information, N2 is a positive integer, and the N2-bits indication information is used for indicating to deactivate the MBS service.

For example, a value of N2 is <NUM>, and the MAC CE includes <NUM>-bit indication information. A value of the <NUM>-bit indication information is "<NUM>", which is used for indicating to deactivate the MBS service, and the value of the <NUM>-bit indication information is "<NUM>", which is used for indicating to activate the MBS service; or, a value of the <NUM>-bit indication information is "<NUM>", which is used for indicating to deactivate the MBS service, and the value of the <NUM>-bit indication information is "<NUM>", which is used for indicating to activate the MBS service.

In an optional manner, in a case that the first command is carried in a MAC CE, a first Logical Channel Identity (LCID) in a sub-header corresponding to the MAC CE is used for indicating to deactivate the MBS service.

For example, a value of the first LCID in the sub-header corresponding to the MAC CE is a first value, which is used for indicating to deactivate the MBS service, and the value of the first LCID in the sub-header corresponding to the MAC CE is a second value, which is used for indicating to activate the MBS service.

Specifically, the DCI or MAC CE includes a first bitmap, at least one bit in the first bitmap corresponds to at least one MBS service in a first MBS service list one-to-one, and a value of the bit is used for indicating whether an MBS service corresponding to the bit is in an activated state or a deactivated state. Further, optionally, the first MBS service list is configured through system broadcast information of the first cell.

In an example, the system broadcast information of the first cell is configured with an ongoing MBS service list of the first cell (i.e., the first MBS service list), wherein the first MBS service list includes a service identity of at least one MBS service, and a bit in the first bitmap in the MAC CE or DCI corresponds to an MBS service identity in the first MBS service list one-to-one. A value of the bit being <NUM> indicates that an MBS service indicated by the MBS service identity corresponding to the bit is in an activated state, and a value of the bit being <NUM> indicates that an MBS service indicated by the MBS service identity corresponding to the bit is in a deactivated state; or, a value of the bit being <NUM> indicates that an MBS service indicated by the MBS service identity corresponding to the bit is in an activated state, and a value of the bit being <NUM> indicates that an MBS service indicated by the MBS service identity corresponding to the bit is in a deactivated state.

B) In an optional manner, the first command is used for deactivating at least one MBS service and/or activating at least one MBS service, and scheduling information of DCI or a MAC CE carrying the first command is scrambled by a first Cell RNTI (C-RNTI), which is a C-RNTI of the terminal device.

Specifically, the DCI or MAC CE includes a first bitmap, at least one bit in the first bitmap corresponds to at least one MBS service in a first MBS service list one-to-one, and a value of the bit is used for indicating whether an MBS service corresponding to the bit is in an activated state or a deactivated state. Further, optionally, the first MBS service list is configured through an RRC dedicated signaling.

In an example, the network device configures one or more MBS services (i.e., the first MBS service list) to the terminal device through the RRC dedicated signaling, here, the first MBS service list includes a service identity of at least one MBS service, and a bit in the first bitmap in the MAC CE or DCI corresponds to an MBS service identity in the first MBS service list one-to-one. A value of the bit being <NUM> indicates that an MBS service indicated by the MBS service identity corresponding to the bit is in an activated state, and a value of the bit being <NUM> indicates that an MBS service indicated by the MBS service identity corresponding to the bit is in a deactivated state; or, a value of the bit being <NUM> indicates that an MBS service indicated by the MBS service identity corresponding to the bit is in an activated state, and a value of the bit being <NUM> indicates that an MBS service indicated by the MBS service identity corresponding to the bit is in a deactivated state.

In the above solution, at least one bit in the first bitmap corresponds to at least one MBS service in the first MBS service list one-to-one, which may be achieved through following manners.

Manner one: at least one MBS service in the first MBS service list with an order of MBS service identity from small to large corresponds to at least one bit in the first bitmap with an order of bit from low to high one-to-one.

Here, optionally, the MBS service identity is a G-RNTI or TMGI.

For example, the MBS service list includes: MBS service identity <NUM>, MBS service identity <NUM>, MBS service identity <NUM>, MBS service identity <NUM>, the first bitmap is "A<NUM>A<NUM>A<NUM>A<NUM>", A<NUM> corresponds to MBS service identity <NUM>, A<NUM> corresponds to MBS service identity <NUM>, A<NUM> corresponds to MBS service identity <NUM>, and A<NUM> corresponds to MBS service identity <NUM>. If "A<NUM>A<NUM>A<NUM>A<NUM>" = "<NUM>", it represents that MBS service <NUM> indicated by MBS service identity <NUM> is in an activated state, MBS service <NUM> indicated by MBS service identity <NUM> is in a deactivated state, MBS service <NUM> indicated by MBS service identity <NUM> is in a deactivated state, and MBS service <NUM> indicated by MBS service identity <NUM> is in an activated state.

Manner two: at least one MBS service in the first MBS service list with an order of MBS service identity from large to small corresponds to at least one bit in the first bitmap with an order of bit from low to high one-to-one.

For example, the MBS service list includes: MBS service identity <NUM>, MBS service identity <NUM>, MBS service identity <NUM>, MBS service identity <NUM>, the first bitmap is "A4A3A2A1", A<NUM> corresponds to MBS service identity <NUM>, A<NUM> corresponds to MBS service identity <NUM>, A<NUM> corresponds to MBS service identity <NUM>, and A<NUM> corresponds to MBS service identity <NUM>. If "A<NUM>A<NUM>A<NUM>A<NUM>" = "<NUM>", it represents that MBS service <NUM> indicated by MBS service identity <NUM> is in an activated state, MBS service <NUM> indicated by MBS service identity <NUM> is in a deactivated state, MBS service <NUM> indicated by MBS service identity <NUM> is in an activated state, and MBS service <NUM> indicated by MBS service identity <NUM> is in an activated state.

Prior to the act <NUM>, the method further includes: the network device transmits MBS configuration information to the terminal device, and accordingly, the terminal device receives the MBS configuration information transmitted by the network device, wherein the MBS configuration information is used for determining at least one of following.

Here, the terminal device receives the MBS service on the MBS BWP.

It should be noted that the MBS configuration information is used for determining configuration information of one MBS service, but it is not limited to this, and the network device may also configure configuration information of multiple MBS services to the terminal device. Contents contained in configuration information of each MBS service may refer to contents in the above solution.

In act <NUM>, the terminal device deactivates at least one MBS service and/or activates at least one MBS service based on the first command.

For an MBS service in a deactivated state, the terminal device executes at least one of following operations.

Operation <NUM>: stopping monitoring a first PDCCH, wherein the first PDCCH is a PDCCH scrambled by a G-RNTI corresponding to the MBS service.

Here, if an MBS service is in a deactivated state, the terminal device stops monitoring a PDCCH scrambled by a G-RNTI of the MBS service.

Specifically, the terminal device stops monitoring the first PDCCH in an MBS CORESET and/or an MBS searchspace, wherein the MBS CORESET is a CORESET corresponding to the MBS service, and the MBS searchspace is a searchspace corresponding to the MBS service.

Operation <NUM>: not switching to an MBS BWP, wherein the MBS BWP is a BWP corresponding to the MBS service.

Operation <NUM>: stopping a first timer for triggering switching of the MBS BWP.

Here, if the MBS service is in a deactivated state and switching of the MBS BWP depends on the first timer, the terminal device stops the first timer.

Operation <NUM>: ignoring a first TDM pattern configuration used for triggering switching of the MBS BWP.

Here, if the MBS service is in a deactivated state and the switching of the MBS BWP depends on the first TDM pattern configuration pre-configured by a network, the terminal device ignores the first TDM pattern configuration.

<FIG> is a second schematic flowchart of a method for managing an MBS service according to an embodiment of the present application. As shown in <FIG>, the method for managing the MBS service includes following acts.

In act <NUM>, a terminal device receives an RRC dedicated signaling sent by a network device, and acquires MBS configuration information through the RRC dedicated signaling.

Here, the terminal device supports an MBS service.

Here, the terminal device acquires the MBS configuration information sent by the network device through the RRC dedicated signaling, wherein the MBS configuration information includes at least one of following: an MBS service identity, a first TDM pattern configuration, information of a first timer, an MBS receiving time length, configuration information of an MBS CORESET, configuration information of an MBS searchspace, and configuration information of an MBS BWP.

In act <NUM>, if a network device side does not have service data of an MBS service, the network device may decide to deactivate the MBS service and send a command for deactivating the MBS service to the terminal device.

Here, the command for deactivating the MBS service may refer to the aforementioned description of the "first command".

Here, if the MBS service is in a deactivated state, the terminal device has at least one of following behaviors (i.e., operations).

In act <NUM>, if service data of an MBS service arrives at the network device side and the MBS service is in a deactivated state, the network device sends a command for activating the MBS service to the terminal device.

Here, the command for activating the MBS service may refer to the aforementioned description of the "first command".

<FIG> is a first schematic diagram of structure composition of an apparatus for managing an MBS service according to an embodiment of the present application, which is applied to a terminal device. As shown in <FIG>, the apparatus for managing the MBS service includes: a receiving unit <NUM>, configured to receive a first command sent by a network device, wherein the first command is used for deactivating at least one MBS service and/or activating at least one MBS service; and an activating-deactivating unit <NUM>, configured to deactivate at least one MBS service and/or activate at least one MBS service based on the first command.

In an optional manner, the first command is carried in DCI, or in a MAC CE, or in system broadcast information, or in an RRC signaling.

In an optional manner, the first command is used for deactivating an MBS service, and scheduling information of DCI or a MAC CE carrying the first command is scrambled through a first G-RNTI, which is a G-RNTI corresponding to the MBS service.

In an optional manner, in a case that the first command is carried in a MAC CE, the MAC CE includes N2-bits indication information, N2 is a positive integer, and the N2-bits indication information is used for indicating to deactivate the MBS service; or, a first LCID in a sub-header corresponding to the MAC CE is used for indicating to deactivate the MBS service.

In an optional manner, the first command is used for deactivating at least one MBS service and/or activating at least one MBS service. Scheduling information of DCI or a MAC CE carrying the first command is scrambled through a first RNTI or a first C-RNTI, wherein the first RNTI is an RNTI of a first cell and the first C-RNTI is a C-RNTI of the terminal device.

In an optional manner, the DCI or MAC CE includes a first bitmap, at least one bit in the first bitmap corresponds to at least one MBS service in a first MBS service list one-to-one, and a value of the bit is used for indicating whether an MBS service corresponding to the bit is in an activated state or a deactivated state.

In an optional manner, the first MBS service list and/or the first RNTI are configured through system broadcast information of the first cell in a case that scheduling information of the DCI or MAC CE carrying the first command is scrambled through the first RNTI.

In an optional manner, the first MBS service list is configured through an RRC dedicated signaling in a case that scheduling information of DCI or MAC CE carrying the first command is scrambled through the first C-RNTI.

In an optional manner, at least one bit in the first bitmap corresponds to at least one MBS service in the first MBS service list one-to-one, including:.

In an optional manner, the MBS service identity is a G-RNTI or TMGI.

The apparatus further includes: an execution unit (not shown in the figure), configured to execute at least one of following operations for an MBS service in a deactivated state: stopping monitoring a first PDCCH, wherein the first PDCCH is a PDCCH scrambled by a G-RNTI corresponding to the MBS service; not switching to an MBS BWP, wherein the MBS BWP is a BWP corresponding to the MBS service; stopping a first timer, wherein the first timer is used for triggering switching of an MBS BWP; ignoring a first TDM pattern configuration, wherein the first TDM pattern configuration is used for triggering switching of an MBS BWP.

The execution unit is configured to: stop monitoring a first PDCCH in an MBS control resource set CORESET and/or an MBS searchspace, wherein the MBS CORESET is a CORESET corresponding to the MBS service, and the MBS searchspace is a searchspace corresponding to the MBS service.

The receiving unit <NUM> is further configured to receive MBS configuration information sent by the network device, and the MBS configuration information is used for determining at least one of following: an MBS service identity; a first TDM pattern configuration used for determining a time of receiving an MBS service and a time of receiving a unicast service; a first timer used for determining a time to switch to an MBS BWP; an MBS receiving time length used for determining a time length for receiving an MBS service by the terminal device; an MBS CORESET which is a CORESET corresponding to an MBS service; an MBS searchspace which is a searchspace corresponding to an MBS service; an MBS BWP which is a BWP corresponding to an MBS service.

In an optional manner, the MBS service identity includes at least one of following: a TMGI, an MBS session identity, and a G-RNTI.

Those skilled in the art should understand that relevant description of the apparatus for managing the MBS service according to an embodiment of the present application may be understood with reference to relevant description of the method for managing the MBS service according to an embodiment of the present application.

<FIG> is a second schematic diagram of structure composition of an apparatus for managing an MBS service according to an embodiment of the present application, which is applied to a network device. As shown in <FIG>, the apparatus for managing the MBS service includes: a sending unit <NUM>, configured to send a first command to a terminal device, wherein the first command is used for deactivating at least one MBS service and/or activating at least one MBS service.

In an optional manner, at least one bit in the first bitmap corresponds to at least one MBS service in the first MBS service list one-to-one, including: at least one MBS service in the first MBS service list with an order of MBS service identity from small to large corresponds to at least one bit in the first bitmap with an order of bit from low to high one-to-one; or, at least one MBS service in the first MBS service list with an order of MBS service identity from large to small corresponds to at least one bit in the first bitmap with an order of bit from low to high one-to-one.

The sending unit <NUM> is further configured to send MBS configuration information to the terminal device, and the MBS configuration information is used for determining at least one of following: an MBS service identity; a first TDM pattern configuration used for determining a time of receiving an MBS service and a time of receiving a unicast service; a first timer used for determining a time to switch to an MBS BWP; an MBS receiving time length used for determining a time length for receiving an MBS service by the terminal device; an MBS CORESET which is a CORESET corresponding to an MBS service; an MBS searchspace which is a searchspace corresponding to an MBS service; an MBS BWP which is a BWP corresponding to an MBS service.

Those skilled in the art should understand that relevant description of the apparatus for managing the MBS service of an embodiment of the present application may be understood with reference to relevant description of the method for managing the MBS service of the embodiments of the present application.

<FIG> is a schematic structure diagram of a communication device <NUM> according to an embodiment of the present application. The communication device may be a terminal device or a network device. The communication device <NUM> shown in <FIG> includes a processor <NUM>, which may call and run a computer program from a memory to implement the method in the embodiments of the present application.

Optionally, as shown in <FIG>, the communication device <NUM> may further include a memory <NUM>. The processor <NUM> may invoke and run a computer program from the memory <NUM> to implement any of the methods in the embodiments of the present application.

Optionally, as shown in <FIG>, the communication device <NUM> may further include a transceiver <NUM>, and the processor <NUM> may control the transceiver <NUM> to communicate with another device. Specifically, the transceiver <NUM> may send information or data to another device or receive information or data sent by another device.

The transceiver <NUM> may further include antennas, a quantity of which may be one or more.

Optionally, the communication device <NUM> may specifically be the network device according to the embodiments of the present application, and the communication device <NUM> may implement corresponding processes implemented by the network device in various methods in the embodiments of the present application, which will not be repeated here for brevity.

Optionally, the communication device <NUM> may specifically be the mobile terminal/terminal device in accordance with the embodiments of the present application, and the communication device <NUM> may implement the corresponding processes implemented by the mobile terminal/terminal device in various methods in the embodiments of the present application, which will not be repeated herein for brevity.

<FIG> is a schematic diagram of a structure of a chip according to an embodiment of the present application. The chip <NUM> shown in <FIG> includes a processor <NUM>, wherein the processor <NUM> may call and run a computer program from a memory to implement a method in an embodiment of the present application.

Optionally, as shown in <FIG>, the chip <NUM> may further include a memory <NUM>. The processor <NUM> may invoke and run a computer program from the memory <NUM> to implement any of the methods in the embodiments of the present application.

Optionally, the chip <NUM> may further include an input interface <NUM>. The processor <NUM> may control the input interface <NUM> to communicate with another device or chip. Specifically, the processor <NUM> may acquire information or data sent by another device or chip.

The processor <NUM> may control the output interface <NUM> to communicate with another device or chip. Specifically, the processor <NUM> may output information or data to another device or chip.

Optionally, the chip may be applied to the network device in the embodiments of the present application, and the chip may implement the corresponding processes implemented by the network device in the various methods of the embodiments of the present application, which will not be repeated here for brevity.

Optionally, the chip may be applied to the mobile terminal/terminal device in the embodiments of the present application, and the chip may implement corresponding processes implemented by the mobile terminal/terminal device in various methods of the embodiments of the present application, which will not be repeated herein for brevity.

It should be understood that the chip mentioned in the embodiments of the present application may also be referred to as a system-level chip, a system chip, a chip system, or a system on chip, etc..

<FIG> is a schematic block diagram of a communication system <NUM> in accordance with an embodiment of the present application.

The terminal device <NUM> may be configured to implement the corresponding functions implemented by the terminal device in the above-mentioned methods, and the network device <NUM> may be configured to implement the corresponding functions implemented by the network device in the above-mentioned methods, which will not be repeated herein for brevity.

It should be understood that the processor in the embodiments of the present application may be an integrated circuit chip with a capability for processing signals. In an implementation process, various acts of the method embodiments described above may be completed through an integrated logic circuit of hardware in a processor or instructions in a form of software. The above processor may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or another programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The processor may implement various methods, acts, and logic block diagrams disclosed in the embodiments of the present application. The general purpose processor may be a microprocessor or the processor may be any conventional processor. The acts of the methods disclosed in connection with the embodiments of the present application may be directly embodied by execution of a hardware decoding processor, or by execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a storage medium commonly used in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, or a register. The storage medium is located in a memory, and a processor reads information in the memory and completes the acts of the above methods in combination with its hardware.

It should be understood that the memory in the embodiments of the present application may be a transitory memory or a non-transitory memory, or may include both transitory and non-transitory memory. The non-transitory memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically EPROM (EEPROM), or a flash memory. The transitory memory may be a Random Access Memory (RAM) which serves as an external cache. As an example, but not as a limitation, many forms of RAMs are available, such as a Static RAM (SRAM), a Dynamic RAM (DRAM), a Synchronous DRAM (SDRAM), a Double Data Rate SDRAM (DDR SDRAM), an Enhanced SDRAM (ESDRAM), a Synchlink DRAM (SLDRAM), and a Direct Rambus RAM (DR RAM). It should be noted that the memories of the systems and methods described herein are intended to include, but are not limited to, these and any other suitable types of memories.

It should be understood that the above memories are described as examples rather than limitations. For example, the memory in the embodiments of the present application may be a static RAM (SRAM), a dynamic RAM (DRAM), a synchronous DRAM (SDRAM), a double data rate SDRAM (DDR SDRAM), an enhanced SDRAM (ESDRAM), a synch link DRAM (SLDRAM) and a direct Rambus RAM (DR RAM), etc. That is to say, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

An embodiment of the present application further provides a computer readable storage medium, configured to store a computer program.

Optionally, the computer readable storage medium may be applied to the network device in the embodiments of the present application, and the computer program causes a computer to perform the corresponding processes implemented by the network device in various methods in accordance with the embodiments of the present application, which will not be repeated herein for brevity.

Optionally, the computer readable storage medium may be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program causes a computer to perform the corresponding processes implemented by the mobile terminal/terminal device in various methods in accordance with the embodiments of the present application, which will not be repeated herein for brevity.

An embodiment of the present application further provides a computer program product, including computer program instructions.

Optionally, the computer program product may be applied to the network device in the embodiments of the present application, and the computer program instructions cause a computer to perform the corresponding processes implemented by the network device in various methods in accordance with the embodiments of the present application, which will not be repeated herein for brevity.

Optionally, the computer program product may be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions cause a computer to perform the corresponding processes implemented by the mobile terminal/terminal device in various methods in accordance with the embodiments of the present application, which will not be repeated herein for brevity.

An embodiment of the present application further provides a computer program.

Optionally, the computer program may be applied to the network device in the embodiments of the present application. When the computer program is run on a computer, the computer is enabled to perform corresponding processes implemented by the network device in various methods according to the embodiments of the present application, which will not be repeated here for brevity.

Optionally, the computer program may be applied to the mobile terminal/terminal device in the embodiments of the present application. The computer program, when running on a computer, causes the computer to perform the corresponding processes implemented by the mobile terminal/terminal device in various methods in accordance with the embodiments of the present application, which will not be repeated herein for brevity.

Those of ordinary skills in the art will recognize that units and algorithm acts of various examples described in connection with the embodiments disclosed herein may be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in a form of hardware or software depends on a specific application and a design constraint of a technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present application.

Those skilled in the art may clearly understand that for convenience and conciseness of description, specific working processes of the systems, apparatuses, and units described above may refer to corresponding processes in the aforementioned method embodiments, and details will not be repeated here.

In several embodiments according to the present application, it should be understood that the disclosed systems, apparatuses, and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative, for example, the division of the units is only a logical function division, and there may be other division manners in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. In addition, coupling or direct coupling or communication connection shown or discussed between each other, which may be indirect coupling or communication connection between the devices or units via some interfaces, may be electrical, mechanical, or in other forms.

The units described as separate components may be or may be not physically separated, and the component shown as a unit may be or may be not a physical unit, i.e., it may be located in one place or may be distributed on multiple network units. Part or all of units may be selected according to actual needs to achieve purposes of technical solutions of the embodiments.

In addition, various functional units in various embodiments of the present application may be integrated in one processing unit, or various units may be physically present separately, or two or more units may be integrated in one unit.

The functions, if implemented in a form of software functional units and sold or used as an independent product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application, in essence, or parts of them which contribute to the prior art, or parts of the technical solutions, may be embodied in a form of a software product, which is stored in a storage medium, and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the acts of the methods of various embodiments of the present application. And the aforementioned storage medium includes various media, such as a U disk, a mobile hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk, etc., which may store program codes.

Claim 1:
A method for managing a Multimedia Broadcast Service, MBS, service, comprising:
receiving, by a terminal device, MBS configuration information sent by a network device, wherein the MBS configuration information is used for determining an MBS service identity; wherein the MBS service identity comprises a Group Radio Network Temporary Identity, G-RNTI;
receiving (<NUM>), by the terminal device, a first command sent by the network device, wherein the first command is used for deactivating at least one MBS service configured by the MBS configuration information and/or activating at least one MBS service configured by the MBS configuration information; and
deactivating (<NUM>), by the terminal device, at least one MBS service and/or activating at least one MBS service based on the first command;
wherein deactivating (<NUM>), by the terminal device, at least one MBS service further comprising:
stopping monitoring a first Physical Downlink Control Channel, PDCCH, wherein the first PDCCH is a PDCCH scrambled by the G-RNTI corresponding to the MBS service.