WO2024082294A1 - 组播业务接收、配置发送方法和装置 - Google Patents

组播业务接收、配置发送方法和装置 Download PDF

Info

Publication number
WO2024082294A1
WO2024082294A1 PCT/CN2022/126803 CN2022126803W WO2024082294A1 WO 2024082294 A1 WO2024082294 A1 WO 2024082294A1 CN 2022126803 W CN2022126803 W CN 2022126803W WO 2024082294 A1 WO2024082294 A1 WO 2024082294A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast service
terminal
bandwidth part
bandwidth
bandwidth portion
Prior art date
Application number
PCT/CN2022/126803
Other languages
English (en)
French (fr)
Inventor
刘晓菲
吴昱民
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to PCT/CN2022/126803 priority Critical patent/WO2024082294A1/zh
Publication of WO2024082294A1 publication Critical patent/WO2024082294A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to a multicast service receiving method, a configuration sending method, a multicast service receiving device, a configuration sending device, a multicast service receiving system, a communication device, and a computer-readable storage medium.
  • Multicast service can also be called multicast broadcast service or multimedia broadcast and multicast service (Multimedia Broadcast and Multicast Service, MBMS).
  • MBS Multicast Broadcast Service
  • MBMS Multimedia Broadcast and Multicast Service
  • the terminal When the terminal is configured with the BandWidth Part (BWP), the terminal can receive multicast services on the BWP. However, due to the mechanism of the BWP itself, there may be some problems in receiving the multicast services.
  • BWP BandWidth Part
  • the embodiments of the present disclosure propose a multicast service receiving method, a configuration sending method, a multicast service receiving device, a configuration sending device, a multicast service receiving system, a communication device and a computer-readable storage medium to solve the technical problems in the related art.
  • a method for receiving a multicast service is proposed, which is executed by a terminal, and the method includes: entering an inactive state and residing in the first bandwidth part; and receiving a multicast service based on a multicast service configuration associated with the first bandwidth part.
  • a configuration sending method is proposed, which is executed by a network device, and the method includes: sending a multicast service configuration associated with a first bandwidth part to a terminal, wherein the configuration of the first bandwidth part is used for, after the terminal enters an inactive state, a network device residing in the first bandwidth part to send a multicast service to the terminal based on the multicast service configuration associated with the first bandwidth part.
  • a multicast service receiving device comprising: a processing module, configured to enter an inactive state and reside in the first bandwidth part; a receiving module, configured to receive the multicast service based on the multicast service configuration associated with the first bandwidth part.
  • a configuration sending device comprising: a sending module, configured to send a multicast service configuration associated with a first bandwidth part to a terminal, wherein the configuration of the first bandwidth part is used for, after the terminal enters an inactive state, a multicast service residing in the first bandwidth part to send a multicast service to the terminal based on the multicast service configuration associated with the first bandwidth part.
  • a multicast service receiving system comprising a terminal and a network side device, wherein the terminal is configured to implement the above-mentioned multicast service receiving method, and the network device is configured to implement the above-mentioned configuration sending method.
  • a communication device comprising: a processor; a memory for storing a computer program; wherein, when the computer program is executed by the processor, the above-mentioned multicast service receiving method is implemented.
  • a communication device comprising: a processor; and a memory for storing a computer program; wherein, when the computer program is executed by the processor, the above-mentioned configuration sending method is implemented.
  • a computer-readable storage medium for storing a computer program.
  • the computer program is executed by a processor, the above-mentioned multicast service receiving method is implemented.
  • a computer-readable storage medium for storing a computer program.
  • the computer program is executed by a processor, the above-mentioned configuration sending method is implemented.
  • the terminal after entering the inactive state, the terminal can reside in the first bandwidth part instead of switching to the initial bandwidth part, so that in the inactive state, the multicast service can be received based on the multicast service configuration associated with the first bandwidth part, which is conducive to avoiding problems in the multicast service reception process.
  • FIG1 is a schematic flow chart of a method for receiving a multicast service according to an embodiment of the present disclosure.
  • FIG. 2 is a schematic flow chart showing another method for receiving a multicast service according to an embodiment of the present disclosure.
  • FIG3 is a schematic flow chart of yet another method for receiving a multicast service according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic flow chart showing yet another method for receiving a multicast service according to an embodiment of the present disclosure.
  • FIG5 is a schematic flowchart showing a configuration sending method according to an embodiment of the present disclosure.
  • FIG6 is a schematic flowchart showing another configuration sending method according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic flow chart showing yet another method for receiving a multicast service according to an embodiment of the present disclosure.
  • FIG8 is a schematic block diagram of a multicast service receiving device according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic block diagram showing a configuration sending device according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic block diagram showing an apparatus for configuration transmission according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic block diagram showing an apparatus for receiving a multicast service according to an embodiment of the present disclosure.
  • first, second, third, etc. may be used to describe various information in the disclosed embodiments, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information.
  • word "if” as used herein may be interpreted as "at the time of” or "when” or "in response to determining”.
  • the terms used herein to characterize size relationships are “greater than” or “less than”, “higher than” or “lower than”. However, those skilled in the art can understand that the term “greater than” also covers the meaning of “greater than or equal to”, and “less than” also covers the meaning of “less than or equal to”; the term “higher than” covers the meaning of “higher than or equal to”, and “lower than” also covers the meaning of "lower than or equal to”.
  • the network can configure multiple bandwidth parts for the terminal, which include the initial bandwidth part, and the initial bandwidth part can further include the downlink initial bandwidth part and the uplink initial bandwidth part.
  • the terminal can receive system messages, paging messages and other actions on the downlink initial bandwidth part, and initiate an initial access request on the uplink initial bandwidth part.
  • the initial access request includes but is not limited to an RRC (Radio Resource Control) establishment request and an RRC recovery request; for a terminal in a connected state, the initial access request includes but is not limited to initiating an RRC reconstruction request on the primary cell (Pcell).
  • RRC Radio Resource Control
  • the terminal When the terminal is in a non-connected state (including idle state and inactive state), the terminal can reside in the initial bandwidth part, send RRC establishment request, RRC recovery request, etc. to the network device, and can also receive system messages and paging messages sent by the network device to perform cell selection, cell reselection and other operations.
  • the network device can activate a bandwidth part among multiple bandwidth parts configured for the terminal, and configure the multicast service configuration associated with the activated bandwidth part.
  • the terminal resides in the activated bandwidth part and performs multicast service reception based on the multicast service configuration associated with the activated bandwidth part.
  • the terminal When the terminal enters the unconnected state from the connected state, it will fall back to the initial bandwidth part, that is, switch from residing in the activated bandwidth part to residing in the initial bandwidth part. At this time, if the multicast service configuration associated with the initial bandwidth part is not configured, the terminal may not be able to continue to receive multicast services.
  • this embodiment is mainly described for the inactive state, but this embodiment is also applicable to the idle state. That is, the technical solution for the terminal being in the inactive state can be adaptively adjusted to the technical solution for the terminal being in the idle state.
  • FIG1 is a schematic flow chart of a method for receiving a multicast service according to an embodiment of the present disclosure.
  • the method for receiving a multicast service shown in this embodiment can be executed by a terminal.
  • the terminal includes but is not limited to communication devices such as mobile phones, tablet computers, wearable devices, sensors, and Internet of Things devices.
  • the terminal can communicate with a network device, and the network device includes but is not limited to network devices in 4G, 5G, 6G and other communication systems, such as base stations, core networks, etc.
  • the multicast service receiving method may include the following steps:
  • step S101 the system enters an inactive state and resides in the first bandwidth portion.
  • step S102 a multicast service is received based on the multicast service configuration associated with the first bandwidth portion.
  • the multicast service configuration associated with the first bandwidth portion includes a common frequency resource (CFR) configuration.
  • CFR common frequency resource
  • the multicast service configuration is not limited to the CFR configuration, and may also include other configurations, such as time domain resource configuration.
  • the terminal when the terminal is in a connected state, it resides in the first bandwidth part.
  • the terminal When the terminal enters an inactive state, it can reside in the first bandwidth part without switching to the initial bandwidth part. In this way, the terminal can receive the multicast service based on the multicast service configuration associated with the first bandwidth part in the inactive state, which is conducive to avoiding problems in the multicast service reception process.
  • the terminal after the terminal enters the inactive state, it resides in the first bandwidth part, which may be stipulated by the protocol or configured by the network device. This disclosure does not limit this.
  • the first bandwidth part may refer to the activated bandwidth part where the terminal resides in the connected state before entering the inactive state.
  • the terminal Before entering the inactive state, the terminal may receive multicast services based on the multicast service configuration associated with the first bandwidth part. After entering the inactive state, since the terminal still resides in the first bandwidth part, it may continue to receive multicast services based on the multicast service configuration associated with the first bandwidth part, thereby avoiding interruption of multicast service reception.
  • the first bandwidth portion may be a bandwidth portion other than the initial bandwidth portion, or may be the initial bandwidth portion.
  • the first bandwidth portion includes at least one of the following:
  • connection-state multicast service bandwidth portion that is, the bandwidth portion configured for the terminal to receive multicast services in the connection state
  • the inactive multicast service bandwidth portion is the bandwidth portion configured for the terminal to receive the multicast service in the inactive state.
  • the terminal when the first bandwidth portion is an initial bandwidth portion, the terminal will reside in the initial bandwidth portion after entering the inactive state, and can receive multicast services based on the multicast service configuration associated with the initial bandwidth portion.
  • the network device only configures the associated multicast service configuration for the activated bandwidth part of the terminal in the connected state.
  • the terminal When the terminal enters the unconnected state, the terminal will switch to the initial bandwidth part, but since the initial bandwidth part is not configured as the associated multicast service configuration, the terminal cannot receive the multicast service based on the multicast service configuration associated with the initial bandwidth part on the initial bandwidth part, thereby interrupting the multicast service.
  • the associated multicast service configuration can be configured for the initial bandwidth part, so that when the terminal enters the unconnected state, the multicast service can be received on the initial bandwidth part based on the multicast service configuration associated with the initial bandwidth part, thereby ensuring the continuity of the multicast service.
  • the terminal when the first bandwidth portion is a connection-configuration multicast service bandwidth portion, the terminal can receive the multicast service configuration associated with the connection-configuration multicast service bandwidth portion when in the connection state, and after entering the inactive state, the terminal can continue to reside in the connection-configuration multicast service bandwidth portion and receive the multicast service based on the multicast service configuration associated with the connection-configuration multicast service bandwidth portion.
  • the terminal can also receive the multicast service configuration associated with the connection-configuration multicast service bandwidth portion in the inactive state, and then reside in the connection-configuration multicast service bandwidth portion in the inactive state, and receive the multicast service based on the multicast service configuration associated with the connection-configuration multicast service bandwidth portion.
  • connection-state multicast service bandwidth portion may be an initial bandwidth portion, or may be a bandwidth portion other than the initial bandwidth portion, for example, a dedicated bandwidth portion configured by the network device for the terminal after the terminal enters the connection state.
  • multiplexing of the multicast service configuration associated with the connection-configuration multicast service bandwidth portion can be achieved, that is, the terminal can receive the multicast service according to the multicast service configuration associated with the connection-configuration multicast service bandwidth portion in the connection state, and can also receive the multicast service according to the multicast service configuration associated with the connection-configuration multicast service bandwidth portion in the inactive state.
  • the terminal can receive the multicast service configuration associated with the inactive multicast service bandwidth portion when in a connected state, and after entering the inactive state, reside in the inactive multicast service bandwidth portion, and receive the multicast service based on the multicast service configuration associated with the inactive multicast service bandwidth portion.
  • the terminal may also receive the multicast service configuration associated with the inactive multicast service bandwidth portion in the inactive state, and then reside in the inactive multicast service bandwidth portion in the inactive state, and receive the multicast service based on the multicast service configuration associated with the inactive multicast service bandwidth portion.
  • the inactive multicast service bandwidth portion may be an initial bandwidth portion, or may be a bandwidth portion other than the initial bandwidth portion.
  • the network device only configures the multicast service configuration associated with the connection-state multicast service bandwidth portion for the terminal, but does not configure the multicast service configuration associated with the inactive-state multicast service bandwidth portion for the terminal, which causes the terminal to be unable to receive the multicast service due to the lack of the associated multicast service configuration when the terminal is in the inactive-state multicast service bandwidth portion, thereby interrupting the multicast service.
  • the multicast service configuration associated with the inactive-state multicast service bandwidth portion can be configured for the terminal, so that when the terminal is in the inactive-state multicast service bandwidth portion in the inactive state, it cannot receive the multicast service according to the multicast service configuration associated with the inactive-state multicast service bandwidth portion, which is conducive to avoiding the interruption of the multicast service.
  • FIG2 is a schematic flow chart of another method for receiving a multicast service according to an embodiment of the present disclosure. As shown in FIG2 , the method further includes:
  • step S201 a multicast service configuration associated with the first bandwidth portion is received in a connected state; and/or a multicast service configuration associated with the first bandwidth portion is received in a non-connected state.
  • the terminal may receive the multicast service configuration associated with the first bandwidth portion sent by the network device in a connected state, or may receive the multicast service configuration associated with the first bandwidth portion sent by the network device in a non-connected state.
  • the present disclosure does not limit this.
  • the multicast service configuration associated with the first bandwidth portion is carried in at least one of the following: proprietary signaling; public broadcast signaling.
  • the terminal when the terminal is in a connected state, it can obtain the multicast service configuration associated with the first bandwidth portion by receiving proprietary signaling, and it can also obtain the multicast service configuration associated with the first bandwidth portion by receiving public broadcast signaling; and when the terminal is in an inactive state, it can obtain the multicast service configuration associated with the first bandwidth portion by receiving public broadcast signaling.
  • the proprietary signaling includes at least one of the following:
  • the RRCRelease message includes at least one of the following: an RRCRelease message carrying a suspension configuration; an RRCRelease message not carrying a suspension configuration.
  • an RRCRelease message carrying a suspension configuration it can enter an inactive state.
  • the terminal receives a RRCRelease message not carrying a suspension configuration it can enter an idle state.
  • the terminal can receive multicast services in a non-connected state or in a connected state, wherein receiving multicast services in a non-connected state includes receiving multicast services in a non-activated state and receiving multicast services in an idle state.
  • the public broadcast signaling includes at least one of the following:
  • SIB System Information Block
  • Multicast service control channel MCCH (MBS Control Channel).
  • FIG3 is a schematic flow chart of another method for receiving a multicast service according to an embodiment of the present disclosure. As shown in FIG3 , the method further includes:
  • step S301 the first bandwidth portion is switched to the initial bandwidth portion in a first scenario, for example, the first bandwidth portion is deactivated and the initial bandwidth portion is activated.
  • the terminal when the first bandwidth part is different from the initial bandwidth part, the terminal may switch the bandwidth part in the first scenario, specifically, may switch from the first bandwidth part to the initial bandwidth part, so as to meet the requirements in the first scenario.
  • the initial bandwidth portion includes at least one of the following:
  • the terminal can switch to the Redcap exclusive initial bandwidth part or the regular initial bandwidth part.
  • the terminal when the terminal is a Redcap terminal with reduced capability, if the terminal is configured with a Redcap exclusive initial bandwidth portion, the first bandwidth portion is switched to the Redcap exclusive initial bandwidth portion in a first scenario. If the terminal is not configured with a Redcap exclusive initial bandwidth portion, the first bandwidth portion is switched to the regular initial bandwidth portion in the first scenario.
  • the network device can configure two types of initial bandwidth parts for the terminal, one is the regular initial bandwidth part, and the other is the Redcap exclusive initial bandwidth part (this bandwidth part is only configured for Redcap terminals).
  • the action of switching to the initial bandwidth part can be specifically switching to the Redcap exclusive initial bandwidth part, and if the Redcap terminal is not configured with the Redcap exclusive initial bandwidth part, then the action of switching to the initial bandwidth part is still switching to the regular initial bandwidth part.
  • the terminal when the terminal is a Redcap terminal, in the first scenario, the terminal can arbitrarily switch to any bandwidth part of the Redcap exclusive initial bandwidth part and the regular initial bandwidth part.
  • the first scenario includes at least one of the following:
  • the first event occurs, which may include the first event is occurring and the first event is about to occur;
  • the first timer expires.
  • the first event includes at least one of the following: radio resource control connection establishment; radio resource control connection recovery; random access; cell selection; cell reselection; receiving system message; receiving paging message; stopping receiving multicast service.
  • the determination method of stopping receiving multicast service includes but is not limited to the terminal moving out of the area receiving multicast service. It should be noted that the first event here may also include other events that require the terminal to switch from the first BWP to the initial BWP, which are not listed here one by one.
  • wireless resource control connection establishment, wireless resource control connection recovery, and random access are initial access operations
  • the terminal needs to perform these operations on the initial bandwidth part. Therefore, the terminal can switch from the first bandwidth part to the initial bandwidth part to perform operations such as wireless resource control connection establishment, wireless resource control connection recovery, and random access.
  • the terminal needs to perform operations such as cell selection, cell reselection, receiving system messages, receiving paging messages, etc. on the initial bandwidth part. Therefore, the terminal can switch from the first bandwidth part to the initial bandwidth part to perform operations such as cell selection, cell reselection, receiving system messages, receiving paging messages, etc.
  • the terminal after entering the inactive state, the terminal still resides on the first bandwidth portion, but does not switch to the initial bandwidth portion for residence.
  • One of the reasons is to receive the multicast service configuration using the multicast service configuration associated with the first bandwidth portion on the first bandwidth portion. Therefore, when the terminal stops receiving the multicast service, it does not need to continue to reside on the first bandwidth portion, and can switch to the initial bandwidth portion to perform operations such as initial access, cell selection, cell reselection, receiving system messages, and receiving paging messages.
  • the first information includes at least one of the following:
  • Physical layer control signaling such as downlink control information DCI (Downlink Control Information);
  • Media access control layer signaling such as media access control layer control element MAC CE (Media Access Control Element).
  • MAC CE Media Access Control Control Element
  • the first information can be used to instruct the terminal to switch from the first bandwidth part to the initial bandwidth part, or the first information can be used to indicate other content, but the protocol stipulates that the terminal switches from the first bandwidth part to the initial bandwidth part when receiving the first information.
  • the first timer includes at least one of the following:
  • the bandwidth part inactivity timer BWP-inactivitytimer (which can be determined according to the protocol provisions) can be an existing timer;
  • the terminal when the terminal resides on the first bandwidth portion, it can detect whether there is data transmission on the first bandwidth portion, and if there is no data transmission, a first timer can be started. During the operation of the first timer, if data transmission occurs on the first bandwidth portion, the first timer is restarted. When the first timer times out, it can be determined that there is no data transmission on the first bandwidth portion for a long time, and then switch to the initial bandwidth portion. Then, the network device can determine that when the first timer times out, the terminal switches to the initial bandwidth portion.
  • a first timer when the terminal enters an inactive state, if it resides on the first bandwidth part, a first timer may be started, and when the first timer times out, the terminal may determine that the residency time on the first bandwidth part is long, and thus switch to the initial bandwidth part. In some examples, during the operation of the first timer, if the terminal switches from the first bandwidth part to another bandwidth part (e.g., the initial bandwidth part or a bandwidth part other than the first bandwidth part and the initial bandwidth part), the first timer may terminate timing.
  • another bandwidth part e.g., the initial bandwidth part or a bandwidth part other than the first bandwidth part and the initial bandwidth part
  • the terminal may switch to the default bandwidth portion, and if the terminal is not configured with a default bandwidth portion, it may switch to the initial bandwidth portion.
  • the first timer may be an existing BWP-inactivity timer or a newly defined timer, which may be selected according to actual needs and is not limited in the present disclosure.
  • FIG4 is a schematic flow chart of another method for receiving a multicast service according to an embodiment of the present disclosure. As shown in FIG4 , the method further includes:
  • a common search space (CSS) of the first bandwidth portion is determined according to protocol provisions or configuration of a network device;
  • step S402 a process in an inactive state is performed on a common search space of the first bandwidth part.
  • the process in the inactive state includes processes that can be executed when the terminal is in the inactive state, including at least one of the following: radio resource control connection establishment; radio resource control connection recovery; random access; cell selection; cell reselection; receiving system messages; receiving paging messages.
  • the process in the inactive state can also include other processes, which are not listed here one by one.
  • the initial bandwidth part is configured with a common search space for performing operations such as wireless resource control connection establishment, wireless resource control connection recovery, random access, cell selection, cell reselection, receiving system messages, and receiving paging messages, and these operations belong to the process in the inactive state.
  • the terminal may not switch to the initial bandwidth part to execute the process in the inactive state, but continue to reside on the first bandwidth part to execute the process in the inactive state, but it is necessary to determine the public search space of the first bandwidth part according to the protocol provisions or the configuration of the network device, wherein the public search space of the first bandwidth part is used for the terminal to execute the process in the inactive state. Therefore, the terminal can continue to reside on the first bandwidth part and execute the process in the inactive state on the public search space of the first bandwidth part.
  • Figure 5 is a schematic flow chart of a configuration sending method according to an embodiment of the present disclosure.
  • the configuration sending method shown in this embodiment can be executed by a network device, and the network device can communicate with a terminal, the network device includes but is not limited to a base station in a communication system such as a 4G base station, a 5G base station, and a 6G base station, and the terminal includes but is not limited to a mobile phone, a tablet computer, a wearable device, a sensor, an Internet of Things device, and other communication devices.
  • the configuration sending method provided by the embodiment of the present disclosure may include the following steps:
  • step S501 a multicast service configuration associated with a first bandwidth part is sent to a terminal, and a multicast service is sent to the terminal based on the multicast service configuration associated with the first bandwidth part; wherein the configuration of the first bandwidth part is used for the terminal to receive the multicast service sent by the network device based on the multicast service configuration associated with the first bandwidth part after entering an inactive state.
  • the multicast service configuration associated with the first bandwidth portion includes a common frequency resource CFR configuration.
  • the multicast service configuration is not limited to the CFR configuration, and may also include other configurations, such as time domain resource configuration.
  • the multicast service by sending the multicast service configuration associated with the first bandwidth part to the terminal, the multicast service can be subsequently sent to the terminal based on the multicast service configuration associated with the first bandwidth part. And after entering the inactive state, the terminal can reside in the first bandwidth part and receive the multicast service based on the multicast service configuration associated with the first bandwidth part without switching to the initial bandwidth part, which is conducive to avoiding problems in the multicast service reception process.
  • the terminal after the terminal enters the inactive state, it resides in the first bandwidth part, which may be stipulated by the protocol or configured by the network device. This disclosure does not limit this.
  • the first bandwidth part may refer to the activated bandwidth part where the terminal resides in the connected state before entering the inactive state.
  • the terminal Before entering the inactive state, the terminal may receive multicast services based on the multicast service configuration associated with the first bandwidth part. After entering the inactive state, since the terminal still resides in the first bandwidth part, it may continue to receive multicast services based on the multicast service configuration associated with the first bandwidth part, thereby avoiding interruption of multicast service reception.
  • the first bandwidth portion may be a bandwidth portion other than the initial bandwidth portion, or may be the initial bandwidth portion.
  • the first bandwidth portion includes at least one of the following:
  • connection-state multicast service bandwidth portion that is, the bandwidth portion configured for the terminal to receive multicast services in the connection state
  • the inactive multicast service bandwidth portion is the bandwidth portion configured for the terminal to receive the multicast service in the inactive state.
  • the terminal when the first bandwidth portion is the initial bandwidth portion, by sending the multicast service configuration associated with the initial bandwidth portion to the terminal, the terminal can reside in the initial bandwidth portion after entering the inactive state and receive the multicast service based on the multicast service configuration associated with the initial bandwidth portion.
  • the network device only configures the associated multicast service configuration for the activated bandwidth part of the terminal in the connected state.
  • the terminal When the terminal enters the unconnected state, the terminal will switch to the initial bandwidth part, but since the initial bandwidth part is not configured as the associated multicast service configuration, the terminal cannot receive the multicast service based on the multicast service configuration associated with the initial bandwidth part on the initial bandwidth part, thereby interrupting the multicast service.
  • the associated multicast service configuration can be configured for the initial bandwidth part, so that when the terminal enters the unconnected state, the multicast service can be received on the initial bandwidth part based on the multicast service configuration associated with the initial bandwidth part, thereby ensuring the continuity of the multicast service.
  • a multicast service configuration associated with the connection-configuration multicast service bandwidth portion can be sent to the terminal when the terminal is in a connection state, so that after the terminal enters an inactive state, it can continue to reside in the connection-configuration multicast service bandwidth portion and receive multicast services based on the multicast service configuration associated with the connection-configuration multicast service bandwidth portion.
  • the network device can also send the multicast service configuration associated with the connection-configuration multicast service bandwidth part to the terminal when the terminal is in an inactive state, so that the terminal resides in the connection-configuration multicast service bandwidth part in the inactive state and receives the multicast service based on the multicast service configuration associated with the connection-configuration multicast service bandwidth part.
  • connection-state multicast service bandwidth portion may be an initial bandwidth portion, or may be a bandwidth portion other than the initial bandwidth portion, for example, a dedicated bandwidth portion configured by the network device for the terminal after the terminal enters the connection state.
  • multiplexing of the multicast service configuration associated with the connection-configuration multicast service bandwidth portion can be achieved, that is, the terminal can receive the multicast service according to the multicast service configuration associated with the connection-configuration multicast service bandwidth portion in the connection state, and can also receive the multicast service according to the multicast service configuration associated with the connection-configuration multicast service bandwidth portion in the inactive state.
  • the multicast service configuration associated with the inactive multicast service bandwidth part can be sent to the terminal when the terminal is in a connected state, so that after entering the inactive state, the terminal can continue to reside in the inactive multicast service bandwidth part and receive the multicast service based on the multicast service configuration associated with the inactive multicast service bandwidth part.
  • the network device may also send the multicast service configuration associated with the inactive multicast service bandwidth portion to the terminal when the terminal is in an inactive state, so that the terminal resides in the inactive multicast service bandwidth portion in the inactive state and receives the multicast service based on the multicast service configuration associated with the inactive multicast service bandwidth portion.
  • the inactive multicast service bandwidth portion may be an initial bandwidth portion, or may be a bandwidth portion other than the initial bandwidth portion.
  • the network device only configures the multicast service configuration associated with the connection-state multicast service bandwidth portion for the terminal, but does not configure the multicast service configuration associated with the inactive-state multicast service bandwidth portion for the terminal, which causes the terminal to be unable to receive the multicast service due to the lack of the associated multicast service configuration when the terminal is in the inactive-state multicast service bandwidth portion, thereby interrupting the multicast service.
  • the multicast service configuration associated with the inactive-state multicast service bandwidth portion can be configured for the terminal, so that when the terminal is in the inactive-state multicast service bandwidth portion in the inactive state, it cannot receive the multicast service according to the multicast service configuration associated with the inactive-state multicast service bandwidth portion, which is conducive to avoiding the interruption of the multicast service.
  • the sending of the multicast service configuration associated with the first bandwidth portion to the terminal includes at least one of the following:
  • a multicast service configuration associated with the first bandwidth portion is sent to the terminal.
  • the network device may send the multicast service configuration associated with the first bandwidth portion to the terminal when the terminal is in a connected state, or may send the multicast service configuration associated with the first bandwidth portion to the terminal when the terminal is in a disconnected state.
  • the present disclosure does not limit this.
  • the multicast service configuration associated with the first bandwidth portion is carried in at least one of the following: proprietary signaling; public broadcast signaling.
  • the proprietary signaling includes at least one of the following:
  • the RRCRelease message includes at least one of the following: an RRCRelease message carrying a suspension configuration; an RRCRelease message not carrying a suspension configuration.
  • the terminal can be put into an inactive state.
  • the terminal can be put into an idle state.
  • the terminal can receive multicast services in a non-connected state or in an idle state, wherein receiving multicast services in a non-connected state includes receiving multicast services in a non-activated state and receiving multicast services in an idle state.
  • the public broadcast signaling includes at least one of the following:
  • SIB System Information Block SIB
  • FIG6 is a schematic flow chart of another configuration sending method according to an embodiment of the present disclosure. As shown in FIG6 , the method further includes:
  • step S601 it is determined that the terminal switches from the first bandwidth part to the initial bandwidth part in a first scenario, for example, the terminal deactivates the first bandwidth part and activates the initial bandwidth part.
  • the terminal when the first bandwidth part is different from the initial bandwidth part, the terminal can switch the bandwidth part in the first scenario, specifically, can switch from the first bandwidth part to the initial bandwidth part, so as to meet the requirements in the first scenario.
  • the network device can determine that the terminal switches from the first bandwidth part to the initial bandwidth part in the first scenario, and then communicate with the terminal on the initial bandwidth part.
  • the initial bandwidth portion includes at least one of the following:
  • the terminal can switch to either the Redcap exclusive initial bandwidth part or the regular initial bandwidth part.
  • the terminal when the terminal is a Redcap terminal with reduced capability, if a Redcap-exclusive initial bandwidth portion is configured for the terminal, it is determined that the terminal switches from the first bandwidth portion to the Redcap-exclusive initial bandwidth portion in a first scenario. If a Redcap-exclusive initial bandwidth portion is not configured for the terminal, it is determined that the terminal switches from the first bandwidth portion to the regular initial bandwidth portion in the first scenario.
  • the network device can configure two initial bandwidth parts for the terminal, one is the regular initial bandwidth part, and the other is the Redcap exclusive initial bandwidth part (this bandwidth part is only configured for Redcap terminals).
  • this bandwidth part is only configured for Redcap terminals.
  • the Redcap exclusive initial bandwidth part when the Redcap exclusive initial bandwidth part is configured for the Redcap terminal, it can be determined that the terminal switches to the initial bandwidth part, specifically, switches to the Redcap exclusive initial bandwidth part, and when the Redcap exclusive initial bandwidth part is not configured for the Redcap terminal, it can be determined that the terminal switches to the initial bandwidth part, and still switches to the regular initial bandwidth part.
  • the terminal when the terminal is a Redcap terminal, in the first scenario, the terminal can arbitrarily switch to any bandwidth part of the Redcap exclusive initial bandwidth part and the regular initial bandwidth part.
  • the first scenario includes at least one of the following:
  • the first event occurs, which may include the first event is occurring and the first event is about to occur;
  • the first timer expires.
  • radio resource control connection establishment radio resource control connection recovery; random access; cell selection; cell reselection; receiving system message; receiving paging message; stopping receiving multicast service.
  • the determination method of stopping receiving multicast service includes but is not limited to the terminal moving out of the area receiving multicast service. It should be noted that the first event here can also include other events that require the terminal to switch from the first BWP to the initial BWP, which are not listed here one by one.
  • wireless resource control connection establishment, wireless resource control connection recovery, and random access are initial access operations
  • the terminal needs to perform these operations on the initial bandwidth part. Therefore, it can be determined that the terminal switches from the first bandwidth part to the initial bandwidth part to perform operations such as wireless resource control connection establishment, wireless resource control connection recovery, and random access.
  • the terminal needs to perform operations such as cell selection, cell reselection, receiving system messages, and receiving paging messages on the initial bandwidth part. Therefore, it can be determined that the terminal switches from the first bandwidth part to the initial bandwidth part to perform operations such as cell selection, cell reselection, receiving system messages, and receiving paging messages.
  • the terminal after entering the inactive state, the terminal still resides on the first bandwidth part, but does not switch to the initial bandwidth part to reside.
  • One of the reasons is to use the multicast service configuration associated with the first bandwidth part to receive the multicast service configuration on the first bandwidth part. Then when the terminal stops receiving the multicast service, it does not need to continue to reside on the first bandwidth part, and can switch to the initial bandwidth part to perform operations such as initial access, cell selection, cell reselection, receiving system messages, receiving paging messages, etc. Therefore, it can be determined that when the terminal stops receiving the multicast service, it switches from the first bandwidth part to the initial bandwidth part.
  • the first information includes at least one of the following:
  • Physical layer control signaling such as downlink control information DCI
  • Media access control layer signaling such as media access control layer control element MAC CE.
  • the first information can be used to instruct the terminal to switch from the first bandwidth part to the initial bandwidth part, or the first information can be used to indicate other content, but the protocol stipulates that the terminal switches from the first bandwidth part to the initial bandwidth part when receiving the first information.
  • the first timer includes at least one of the following:
  • the bandwidth part inactivity timer BWP-inactivitytimer may be an existing timer
  • the terminal when the terminal resides on the first bandwidth portion, it can detect whether there is data transmission on the first bandwidth portion, and if there is no data transmission, then a first timer can be started. During the operation of the first timer, if data transmission occurs on the first bandwidth portion, then the first timer is restarted. When the first timer times out, it can be determined that there is no data transmission on the first bandwidth portion for a long time, and then switch to the initial bandwidth portion. Then, the network device can determine that when the first timer times out, the terminal switches to the initial bandwidth portion.
  • a first timer when the terminal enters an inactive state, if it resides in the first bandwidth part, a first timer may be started, and when the first timer times out, the terminal may determine that the residency time in the first bandwidth part is long, and thus switch to the initial bandwidth part. Wherein, during the operation of the first timer, if the terminal switches from the first bandwidth part to another bandwidth part (for example, the initial bandwidth part or a bandwidth part other than the first bandwidth part and the initial bandwidth part), the first timer may terminate timing.
  • if a default bandwidth portion is configured for the terminal it may be determined that the terminal switches to the default bandwidth portion; if no default bandwidth portion is configured for the terminal, it may be determined that the terminal switches to the initial bandwidth portion.
  • the first timer may be an existing BWP-inactivity timer or a newly defined timer, which may be selected according to actual needs and is not limited in the present disclosure.
  • FIG7 is a schematic flow chart of another method for receiving a multicast service according to an embodiment of the present disclosure. As shown in FIG7, the method further includes:
  • step S701 a common search space of a first bandwidth part is configured for the terminal, wherein the common search space of the first bandwidth part is used for the terminal to perform a process in an inactive state.
  • the process in the inactive state includes processes that can be executed when the terminal is in the inactive state, including at least one of the following: radio resource control connection establishment; radio resource control connection recovery; random access; cell selection; cell reselection; receiving system messages; receiving paging messages.
  • the process in the inactive state can also include other processes, which are not listed here one by one.
  • one of the reasons why the terminal is determined to switch to the initial bandwidth part is that the initial bandwidth part is configured with a common search space for performing operations such as wireless resource control connection establishment, wireless resource control connection recovery, random access, cell selection, cell reselection, receiving system messages, and receiving paging messages, and these operations belong to the process in the inactive state.
  • operations such as wireless resource control connection establishment, wireless resource control connection recovery, random access, cell selection, cell reselection, receiving system messages, and receiving paging messages, and these operations belong to the process in the inactive state.
  • a common search space of the first bandwidth part may be configured for the terminal, wherein the common search space of the first bandwidth part is used for the terminal to perform a process in an inactive state, so the terminal may continue to reside on the first bandwidth part and perform a process in an inactive state on the common search space of the first bandwidth part. Then, it may be determined that the terminal continues to reside on the first bandwidth part.
  • the present disclosure also provides embodiments of a multicast service receiving device and a configuration sending device.
  • FIG8 is a schematic block diagram of a multicast service receiving device according to an embodiment of the present disclosure.
  • the multicast service receiving device shown in this embodiment may be a terminal, or a device composed of a module in a terminal, and the terminal includes but is not limited to a mobile phone, a tablet computer, a wearable device, a sensor, an Internet of Things device and other communication devices.
  • the terminal may communicate with a network device, and the network device includes but is not limited to a network device in a 4G, 5G, 6G and other communication systems, such as a base station, a core network and the like.
  • the multicast service receiving device includes:
  • the processing module 801 is configured to enter an inactive state and reside in the first bandwidth part
  • the receiving module 802 is configured to receive a multicast service based on the multicast service configuration associated with the first bandwidth portion.
  • the multicast service configuration associated with the first bandwidth portion includes a common frequency resource configuration.
  • the first bandwidth portion includes at least one of the following: an initial bandwidth portion; a connection-state multicast service bandwidth portion; and an inactive-state multicast service bandwidth portion.
  • the receiving module is further configured to receive the multicast service configuration associated with the first bandwidth portion in a connected state; and/or receive the multicast service configuration associated with the first bandwidth portion in a non-connected state.
  • the multicast service configuration associated with the first bandwidth portion is carried in at least one of the following: proprietary signaling; public broadcast signaling.
  • the dedicated signaling includes at least one of the following: a radio resource control release RRCRelease message; a radio resource control reconfiguration RRCReconfiguration message; a radio resource control resumption RRCResume message.
  • the public broadcast signaling includes at least one of the following: a system information block SIB; a multicast service control channel MCCH.
  • the processing module is further configured to switch from the first bandwidth part to the initial bandwidth part in a first scenario.
  • the initial bandwidth portion when the terminal is a Redcap terminal with reduced capabilities, includes at least one of the following: a Redcap-specific initial bandwidth portion; a regular initial bandwidth portion.
  • the first scenario includes at least one of the following: occurrence of a first event; receipt of first information; and timing out of a first timer.
  • the first event includes at least one of the following: radio resource control connection establishment; radio resource control connection recovery; random access; cell selection; cell reselection; receiving system message; receiving paging message; stopping receiving multicast service.
  • the first information includes at least one of the following: physical layer control signaling; radio resource control RRC signaling; media access control layer signaling.
  • the first timer includes at least one of the following: a bandwidth part inactivity timer BWP-inactivitytimer; or a newly defined timer.
  • the processing module is further configured to determine a common search space of the first bandwidth part according to protocol provisions or configuration of a network device; and execute a process in an inactive state on the common search space of the first bandwidth part.
  • the process in the inactive state includes at least one of the following: radio resource control connection establishment; radio resource control connection recovery; random access; cell selection; cell reselection; receiving system messages; receiving paging messages.
  • FIG9 is a schematic block diagram of a configuration sending device according to an embodiment of the present disclosure.
  • the configuration sending device shown in this embodiment may be a network device, or a device composed of modules in a network device, and the network device may communicate with a terminal.
  • the terminal includes but is not limited to communication devices such as mobile phones, tablet computers, wearable devices, sensors, and Internet of Things devices.
  • the terminal may communicate with a network device, and the network device includes but is not limited to network devices in 4G, 5G, 6G and other communication systems, such as base stations, core networks, etc.
  • the configuration sending device includes:
  • the sending module 901 is configured to send the multicast service configuration associated with the first bandwidth part to the terminal, and send the multicast service to the terminal based on the multicast service configuration associated with the first bandwidth part; wherein the configuration of the first bandwidth part is used for the terminal to receive the multicast service sent by the network device based on the multicast service configuration associated with the first bandwidth part after entering an inactive state.
  • the multicast service configuration associated with the first bandwidth portion includes a common frequency resource configuration.
  • the first bandwidth portion includes at least one of the following: an initial bandwidth portion; a connection-state multicast service bandwidth portion; and an inactive-state multicast service bandwidth portion.
  • the sending module is configured to perform at least one of the following: sending the multicast service configuration associated with the first bandwidth part to the terminal when the terminal is in a connected state; sending the multicast service configuration associated with the first bandwidth part to the terminal when the terminal is in a non-connected state.
  • the multicast service configuration associated with the first bandwidth portion is carried in at least one of the following: proprietary signaling; public broadcast signaling.
  • the dedicated signaling includes at least one of the following: a radio resource control release RRCRelease message; a radio resource control reconfiguration RRCReconfiguration message; a radio resource control resumption RRCResume message.
  • the public broadcast signaling includes at least one of the following: a system information block SIB; a multicast service control channel MCCH
  • the apparatus further comprises: a processing module configured to determine that the terminal switches from the first bandwidth part to the initial bandwidth part in a first scenario.
  • the initial bandwidth portion when the terminal is a Redcap terminal with reduced capabilities, includes at least one of the following: a Redcap-specific initial bandwidth portion; a regular initial bandwidth portion.
  • the first scenario includes at least one of the following: occurrence of a first event; receipt of first information; and timing out of a first timer.
  • the first event includes at least one of the following: radio resource control connection establishment; radio resource control connection recovery; random access; cell selection; cell reselection; receiving system message; receiving paging message; stopping receiving multicast service.
  • the first information includes at least one of the following: physical layer signaling; radio resource control RRC signaling; media access control layer signaling.
  • the first timer includes at least one of the following: a bandwidth part inactivity timer BWP-inactivitytimer; or a newly defined timer.
  • the apparatus further comprises: a sending module configured to configure a common search space of a first bandwidth part for the terminal, wherein the common search space of the first bandwidth part is used for the terminal to execute a process in an inactive state.
  • the process in the inactive state includes at least one of the following: radio resource control connection establishment; radio resource control connection recovery; random access; cell selection; cell reselection; receiving system messages; receiving paging messages.
  • the relevant parts refer to the partial description of the method embodiment.
  • the device embodiment described above is only schematic, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Those of ordinary skill in the art can understand and implement it without paying creative labor.
  • An embodiment of the present disclosure further proposes a multicast service receiving system, comprising a terminal and a network side device, wherein the terminal is configured to implement the multicast service receiving method described in any of the above embodiments, and the network device is configured to implement the configuration sending method described in any of the above embodiments.
  • An embodiment of the present disclosure further proposes a communication device, comprising: a processor; and a memory for storing a computer program; wherein when the computer program is executed by the processor, the multicast service receiving method described in any of the above embodiments is implemented.
  • An embodiment of the present disclosure further proposes a communication device, comprising: a processor; and a memory for storing a computer program; wherein when the computer program is executed by the processor, the configuration sending method described in any of the above embodiments is implemented.
  • the embodiments of the present disclosure further provide a computer-readable storage medium for storing a computer program.
  • the computer program is executed by a processor, the multicast service receiving method described in any of the above embodiments is implemented.
  • An embodiment of the present disclosure further provides a computer-readable storage medium for storing a computer program.
  • the computer program is executed by a processor, the configuration sending method described in any of the above embodiments is implemented.
  • FIG. 10 is a schematic block diagram of an apparatus 1000 for configuration transmission according to an embodiment of the present disclosure.
  • the apparatus 1000 may be provided as a base station.
  • the apparatus 1000 includes a processing component 1022, a wireless transmission/reception component 1024, an antenna component 1026, and a signal processing part specific to a wireless interface, and the processing component 1022 may further include one or more processors.
  • One of the processors in the processing component 1022 may be configured to implement the configuration transmission method described in any of the above embodiments.
  • the apparatus 1100 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.
  • the device 1100 may include one or more of the following components: a processing component 1102 , a memory 1104 , a power component 1106 , a multimedia component 1108 , an audio component 1110 , an input/output (I/O) interface 1112 , a sensor component 1114 , and a communication component 1116 .
  • the processing component 1102 generally controls the overall operation of the device 1100, such as operations associated with display, phone calls, data communications, camera operations, and recording operations.
  • the processing component 1102 may include one or more processors 1120 to execute instructions to complete all or part of the steps of the multicast service receiving method described above.
  • the processing component 1102 may include one or more modules to facilitate the interaction between the processing component 1102 and other components.
  • the processing component 1102 may include a multimedia module to facilitate the interaction between the multimedia component 1108 and the processing component 1102.
  • the memory 1104 is configured to store various types of data to support operations on the device 1100. Examples of such data include instructions for any application or method operating on the device 1100, contact data, phone book data, messages, pictures, videos, etc.
  • the memory 1104 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, or optical disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EPROM erasable programmable read-only memory
  • PROM programmable read-only memory
  • ROM read-only memory
  • the power supply component 1106 provides power to the various components of the device 1100.
  • the power supply component 1106 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device 1100.
  • the multimedia component 1108 includes a screen that provides an output interface between the device 1100 and the user.
  • the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.
  • the multimedia component 1108 includes a front camera and/or a rear camera. When the device 1100 is in an operating mode, such as a shooting mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
  • the audio component 1110 is configured to output and/or input audio signals.
  • the audio component 1110 includes a microphone (MIC), and when the device 1100 is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal.
  • the received audio signal can be further stored in the memory 1104 or sent via the communication component 1116.
  • the audio component 1110 also includes a speaker for outputting audio signals.
  • I/O interface 1112 provides an interface between processing component 1102 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, start buttons, and lock buttons.
  • the sensor assembly 1114 includes one or more sensors for providing various aspects of the status assessment of the device 1100.
  • the sensor assembly 1114 can detect the open/closed state of the device 1100, the relative positioning of components, such as the display and keypad of the device 1100, and the sensor assembly 1114 can also detect the position change of the device 1100 or a component of the device 1100, the presence or absence of user contact with the device 1100, the orientation or acceleration/deceleration of the device 1100, and the temperature change of the device 1100.
  • the sensor assembly 1114 can include a proximity sensor configured to detect the presence of a nearby object without any physical contact.
  • the sensor assembly 1114 can also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor assembly 1114 can also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • the communication component 1116 is configured to facilitate wired or wireless communication between the device 1100 and other devices.
  • the device 1100 can access a wireless network based on a communication standard, such as WiFi, 2G, 3G, 4G LTE, 5G NR, or a combination thereof.
  • the communication component 1116 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel.
  • the communication component 1116 also includes a near field communication (NFC) module to facilitate short-range communication.
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • the apparatus 1100 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to execute the above-mentioned multicast service receiving method.
  • ASICs application-specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays
  • controllers microcontrollers, microprocessors or other electronic components to execute the above-mentioned multicast service receiving method.
  • a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 1104 including instructions, and the instructions can be executed by the processor 1120 of the device 1100 to complete the multicast service receiving method.
  • the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

Landscapes

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

Abstract

本公开涉及组播业务接收、配置发送方法和装置，其中，所述组播业务接收方法包括：进入非激活态，驻留在所述第一带宽部分；基于所述第一带宽部分关联的组播业务配置接收组播业务。根据本公开，终端在进入非激活态后，可以驻留在第一带宽部分，而不会切换到初始带宽部分，从而在非激活态可以基于第一带宽部分关联的组播业务配置接收组播业务，有利于避免组播业务接收过程出现问题。

Description

组播业务接收、配置发送方法和装置 技术领域
本公开涉及通信技术领域，具体而言，涉及组播业务接收方法、配置发送方法、组播业务接收装置、配置发送装置、组播业务接收系统、通信装置和计算机可读存储介质。
背景技术
组播业务(Multicast Broadcast Service，MBS)，也可以称作多播广播业务或者多媒体广播多播业务(Multimedia Broadcast and Multicast Service，MBMS)。
在终端被配置了带宽部分(BandWidth Part，BWP)的情况下，终端可以在BWP上接收组播业务，但是由于BWP自身的机制，会导致对于组播业务的接收存在一些问题。
发明内容
有鉴于此，本公开的实施例提出了组播业务接收方法、配置发送方法、组播业务接收装置、配置发送装置、组播业务接收系统、通信装置和计算机可读存储介质，以解决相关技术中的技术问题。
根据本公开实施例的第一方面，提出一种组播业务接收方法，由终端执行，所述方法包括：进入非激活态，驻留在所述第一带宽部分；基于所述第一带宽部分关联的组播业务配置接收组播业务。
根据本公开实施例的第二方面，提出一种配置发送方法，由网络设备执行，所述方法包括：向终端发送第一带宽部分关联的组播业务配置，其中，所述第一带宽部分的配置用于供所述终端进入非激活态后，驻留在所述第一带宽部分基于所述第一带宽部分关联的组播业务配置向所述终端发送组播业务。
根据本公开实施例的第三方面，提出一种组播业务接收装置，所述装置包括：处理模块，被配置为进入非激活态，驻留在所述第一带宽部分；接收模块，被配置为基于所述第一带宽部分关联的组播业务配置接收组播业务。
根据本公开实施例的第四方面，提出一种配置发送装置，所述装置包括：发送模块，被配置为向终端发送第一带宽部分关联的组播业务配置，其中，所述第一带宽部分的配置用于供所述终端进入非激活态后，驻留在所述第一带宽部分基于所述第一带宽部分关联的组播业务配置向所述终端发送组播业务。
根据本公开实施例的第五方面，提出一种组播业务接收系统，包括终端、网络侧设备，其中所述终端被配置为实现上述组播业务接收方法，所述网络设备被配置为实现上述配置发送方法。
根据本公开实施例的第六方面，提出一种通信装置，包括：处理器；用于存储计算机程序的存储器；其中，当所述计算机程序被处理器执行时，实现上述组播业务接收方法。
根据本公开实施例的第七方面，提出一种通信装置，包括：处理器；用于存储计算机程序的存储器；其中，当所述计算机程序被处理器执行时，实现上述配置发送方法。
根据本公开实施例的第八方面，提出一种计算机可读存储介质，用于存储计算机程序，当所述计算机程序被处理器执行时，实现上述组播业务接收方法。
根据本公开实施例的第九方面，提出一种计算机可读存储介质，用于存储计算机程序，当所述计算机程序被处理器执行时，实现上述配置发送方法。
根据本公开的实施例，终端在进入非激活态后，可以驻留在第一带宽部分，而不会切换到初始带宽部分，从而在非激活态可以基于第一带宽部分关联的组播业务配置接收组播业务，有利于避免组播业务接收过程出现问题。
附图说明
为了更清楚地说明本公开实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是根据本公开的实施例示出的一种组播业务接收方法的示意流程图。
图2是根据本公开的实施例示出的另一种组播业务接收方法的示意流程图。
图3是根据本公开的实施例示出的又一种组播业务接收方法的示意流程图。
图4是根据本公开的实施例示出的又一种组播业务接收方法的示意流程图。
图5是根据本公开的实施例示出的一种配置发送方法的示意流程图。
图6是根据本公开的实施例示出的另一种配置发送方法的示意流程图。
图7是根据本公开的实施例示出的又一种组播业务接收方法的示意流程图。
图8是根据本公开的实施例示出的一种组播业务接收装置的示意框图。
图9是根据本公开的实施例示出的一种配置发送装置的示意框图。
图10是根据本公开的实施例示出的一种用于配置发送的装置的示意框图。
图11是根据本公开的实施例示出的一种用于组播业务接收的装置的示意框图。
具体实施方式
下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本公开保护的范围。
在本公开实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开实施例。在本公开实施例和所附权利要求书中所使用的单数形式的“一种”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本公开实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本公开实施例范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
出于简洁和便于理解的目的，本文在表征大小关系时，所使用的术语为“大于”或“小于”、“高于”或“低于”。但对于本领域技术人员来说，可以理解：术语“大于”也涵盖了“大于等于”的含义，“小于”也涵盖了“小于等于”的含义；术语“高于”涵盖了“高于等于”的含义，“低于”也涵盖了“低于等于”的含义。
网络可以为终端配置多个带宽部分，这多个带宽部分中包含初始带宽部分，初 始带宽部分又可以进一步包括下行初始带宽部分和上行初始带宽部分。终端可以在下行初始带宽部分上进行接收系统消息、接收寻呼消息等动作，在上行初始带宽部分上发起初始接入请求。例如对于非连接态(包括空闲态、非激活态)的终端而言，初始接入请求包括但不限于RRC(Radio Resource Control，无线资源控制)建立请求、RRC恢复请求；对于连接态的终端而言，初始接入请求包括但不限于在主小区(Pcell)上发起RRC重建请求。
当终端处于非连接态(包括空闲态、非激活态)时，终端可以驻留在初始带宽部分，向网络设备发送RRC建立请求、RRC恢复请求等，也可以接收网络设备发送的系统消息、寻呼消息，进行小区选择、小区重选等操作。
终端进入连接态后，网络设备可以在为终端配置的多个带宽部分中激活一个带宽部分，并配置与激活带宽部分相关联的组播业务配置，终端驻留在激活带宽部分，基于激活带宽部分相关联的组播业务配置执行组播业务接收。
而当终端从连接态进入非连接态，将会回退到初始带宽部分，也即从驻留在激活带宽部分切换为驻留在初始带宽部分。此时，如果没有配置初始带宽部分相关联的组播业务配置，可能会导致终端无法继续执行组播业务接收。
需要说明的，本实施例主要是针对非激活态的情况进行示例性描述，但是本实施例也适用于空闲态的情况。也就是说，有关终端处于非激活态的技术方案，可以适应性调整终端处于空闲态的技术方案。
图1是根据本公开的实施例示出的一种组播业务接收方法的示意流程图。本实施例所示的组播业务接收方法可以由终端执行。所述终端包括但不限于手机、平板电脑、可穿戴设备、传感器、物联网设备等通信装置。所述终端可以与网络设备通信，所述网络设备包括但不限于4G、5G、6G等通信系统中的网络设备，例如基站、核心网等。
如图1所示，本公开实施例提供组播业务接收方法可以包括以下步骤：
在步骤S101中，进入非激活态，驻留在第一带宽部分。
在步骤S102中，基于第一带宽部分关联的组播业务配置接收组播业务。
在一个实施例中，所述第一带宽部分关联的组播业务配置包括公共频率资源(Common Frequency Resource，CFR)配置。
当然，组播业务配置并不限于CFR配置，还可以包括其他配置，例如时域资源配置等。
根据本公开的实施例，终端在处于连接态时，驻留在第一带宽部分。当终端进入非激活态后，可以驻留在第一带宽部分，而不会切换到初始带宽部分。如此，终端在非激活态可以基于第一带宽部分关联的组播业务配置接收组播业务，有利于避免组播业务接收过程出现问题。
需要说明的是，终端进入非激活态后，驻留在第一带宽部分，可以是协议规定的，也可以是网路设备配置的。对此，本公开并不限制。
其中，第一带宽部分可以是指终端在进入非激活态之前，在连接态时驻留的激活的带宽部分。终端在进入非激活态之前，可以基于第一带宽部分关联的组播业务配置接收组播业务，在进入非激活态之后，由于仍然驻留在第一带宽部分，所以可以继续基于第一带宽部分关联的组播业务配置接收组播业务，从而避免组播业务接收中断。
另外，第一带宽部分可以是初始带宽部分以外的带宽部分，也可以是初始带宽部分。例如在一个实施例中，所述第一带宽部分包括以下至少之一：
初始带宽部分；
连接态组播业务带宽部分，也即配置给终端在连接态接收组播业务的带宽部分；
非激活态组播业务带宽部分，也即配置给终端在非激活态接收组播业务的带宽部分。
在一些示例中，在第一带宽部分为初始带宽部分的情况下，终端在进入非激活态之后，会驻留在初始带宽部分，可以基于初始带宽部分关联的组播业务配置接收组播业务。
在一些相关技术中，网络设备仅针对连接态下终端的激活带宽部分配置关联的组播业务配置，当终端进入非连接态时，由于终端会切换到初始带宽部分上，但是由于初始带宽部分并未被配置为关联的组播业务配置，导致终端在初始带宽部分上不能基于初始带宽部分关联的组播业务配置接收组播业务，从而组播业务中断。而根据本实施例，可以针对初始带宽部分配置关联的组播业务配置，从而当终端进入非连接态时，可以在初始带宽部分上基于初始带宽部分关联的组播业务配置接收组播业务，确保组播业务的连续性。
在另一些示例中，在第一带宽部分为连接态组播业务带宽部分的情况下，终端在连接态时，可以接收连接态组播业务带宽部分关联的组播业务配置，在进入非激活态之后，终端可以继续驻留在连接态组播业务带宽部分，并基于连接态组播业务带宽部分关联的组播业务配置接收组播业务。
也就是说，终端也可以在非激活态接收连接态组播业务带宽部分关联的组播业务配置，进而在非激活态驻留在连接态组播业务带宽部分，并基于连接态组播业务带宽部分关联的组播业务配置接收组播业务。
其中，连接态组播业务带宽部分可以为初始带宽部分，也可以为初始带宽部分以外的带宽部分，例如终端进入连接态后，网络设备为终端配置的专用带宽部分。
根据本实施例，可以实现对连接态组播业务带宽部分关联的组播业务配置的复用，也即终端可以在连接态下根据连接态组播业务带宽部分关联的组播业务配置接收组播业务，还可以在非激活态下根据连接态组播业务带宽部分关联的组播业务配置接收组播业务。
在又一些示例中，在第一带宽部分为非激活态组播业务带宽部分的情况下，终端在连接态时，可以接收非激活态组播业务带宽部分关联的组播业务配置，在进入非激活态之后，驻留在非激活态组播业务带宽部分，并基于非激活态组播业务带宽部分关联的组播业务配置接收组播业务。
或者，终端也可以在非激活态接收非激活态组播业务带宽部分关联的组播业务配置，进而在非激活态驻留在非激活态组播业务带宽部分，并基于非激活态组播业务带宽部分关联的组播业务配置接收组播业务。
其中，非激活态组播业务带宽部分可以为初始带宽部分，也可以为初始带宽部分以外的带宽部分。
在一些相关技术中，网络设备仅会为终端配置连接态组播业务带宽部分关联的组播业务配置，而没有为终端配置非激活态组播业务带宽部分关联的组播业务配置，这会导致终端在非激活态下处于非激活态组播业务带宽部分时，由于没有关联的组播业务配置而不能接收组播业务，从而组播业务中断。而根据本实施例，可以为终端配置非激活态组播业务带宽部分关联的组播业务配置，从而终端在非激活态下处于非激活态组播业务带宽部分时，可以根据非激活态组播业务带宽部分关联的组播业务配置而不能接收组播业务，有利于避免组播业务中断。
图2是根据本公开的实施例示出的另一种组播业务接收方法的示意流程图。如图2所示，所述方法还包括：
在步骤S201中，在连接态接收所述第一带宽部分关联的组播业务配置；和/或在非连接态接收所述第一带宽部分关联的组播业务配置。
终端可以在连接态接收网络设备发送的第一带宽部分关联的组播业务配置，也可以在非连接态接收网络设备发送的第一带宽部分关联的组播业务配置。对此本公开并不限制。
在一个实施例中，所述第一带宽部分关联的组播业务配置携带在以下至少之一中：专有信令；公共广播信令。
例如终端在连接态下，既可以通过接收专有信令来获取第一带宽部分关联的组播业务配置，也可以通过接收公共广播信令来获取第一带宽部分关联的组播业务配置；而终端在非激活态下，可以通过接收公共广播信令来获取第一带宽部分关联的组播业务配置。
在一个实施例中，所述专有信令包括以下至少之一：
无线资源控制释放RRCRelease消息；
无线资源控制重配置RRCReconfiguration消息；
无线资源控制恢复RRCResume消息。
需要说明的是，RRCRelease消息包括以下至少一项：携带挂起配置的RRCRelease消息；未携带挂起配置的RRCRelease消息。例如：终端接收到携带挂起配置的RRCRelease消息，可以进入非激活态。又例如：终端接收到未携带挂起配置的RRCRelease消息，可以进入空闲态。终端既可以在非连接态接收组播业务，也可以在连接态接收组播业务，其中，在非连接态接收组播业务包括在非激活态接收组播业务和在空闲态接收组播业务。
在一个实施例中，所述公共广播信令包括以下至少之一：
系统信息块SIB(System Information Block)；
组播业务控制信道MCCH(MBS Control Channel)。
图3是根据本公开的实施例示出的又一种组播业务接收方法的示意流程图。如图3所示，所述方法还包括：
在步骤S301中，在第一场景下从所述第一带宽部分切换到初始带宽部分，例如将第一带宽部分去激活(deactivate)，将初始带宽部分激活。
在一个实施例中，在第一带宽部分不同于初始带宽部分的情况下，终端可以在第一场景下进行带宽部分切换，具体可以从第一带宽部分切换到初始带宽部分，以便满足第一场景下的需求。
在一个实施例中，在所述终端为能力降低Redcap(Reduced Capability)终端的情况下，所述初始带宽部分包括以下至少之一：
Redcap专属初始带宽部分；
常规初始带宽部分。
也即终端既可以切换到Redcap专属初始带宽部分，也可以切换到常规初始带宽部分。
在一个示例中，在所述终端为能力降低Redcap终端的情况下，若所述终端被配置了Redcap专属初始带宽部分，在第一场景下从所述第一带宽部分切换到Redcap专属初始带宽部分。若所述终端未被配置Redcap专属初始带宽部分，第一场景下从所述第一带宽部分切换到常规初始带宽部分。
对于Redcap终端而言，网络设备可以为终端配置两种初始带宽部分，一种是常规初始带宽部分，一种是Redcap专属初始带宽部分(这种带宽部分仅配置给Redcap终端)。其中，当Redcap终端被配置了Redcap专属初始带宽部分时，切换到初始带宽部分的动作，具体可以是切换到Redcap专属初始带宽部分，而若Redcap终端未被配置Redcap专属初始带宽部分，那么切换到初始带宽部分的动作，仍然是切换到常规初始带宽部分。
在另一个示例中，当终端为Redcap终端时，在第一场景下，终端可以任意切换到Redcap专属初始带宽部分和常规初始带宽部分中任一带宽部分。
在一个实施例中，所述第一场景包括以下至少之一：
发生第一事件，可以包括正在发生第一事件和将要发生第一事件；
接收到第一信息；
第一定时器超时。
在一个实施例中，所述第一事件包括以下至少之一：无线资源控制连接建立； 无线资源控制连接恢复；随机接入；小区选择；小区重选；接收系统消息；接收寻呼消息；停止接收组播业务。其中，停止接收组播业务的判定方式，包括但不限于终端移出接收组播业务的区域。需要说明的是，这里第一事件还可以包括其他需要终端从第一BWP上切换到初始BWP上的事件，这里不再一一列举。
由于无线资源控制连接建立、无线资源控制连接恢复、随机接入属于初始接入操作，终端进行这些操作需要在初始带宽部分上进行，因此，终端可以从第一带宽部分切换到初始带宽部分上进行无线资源控制连接建立、无线资源控制连接恢复、随机接入等操作。
类似地，终端进行小区选择、小区重选、接收系统消息、接收寻呼消息等操作，也需要在初始带宽部分上进行，因此，终端可以从第一带宽部分切换到初始带宽部分上进行小区选择、小区重选、接收系统消息、接收寻呼消息等操作。
可以理解的，终端进入非激活态后仍然驻留在第一带宽部分上，而没有切换到初始带宽部分上进行驻留，原因之一是为了在第一带宽部分上使用第一带宽部分关联的组播业务配置接收组播业务配置。因此，当终端停止接收组播业务，就不必继续驻留在第一带宽部分上了，可以切换到初始带宽部分上，以便进行初始接入、小区选择、小区重选、接收系统消息、接收寻呼消息等操作。
在一个实施例中，所述第一信息包括以下至少之一：
物理层控制信令，例如下行控制信息DCI(Downlink Control Information)；
无线资源控制RRC信令；
媒体接入控制层信令，例如媒体接入控制层控制元素MAC CE(Media Access Control Control Element)。
在一个实施例中，第一信息可以用于指示终端从第一带宽部分切换到初始带宽部分，或者，第一信息可以用于指示其他内容，但是协议规定终端在接收到第一信息时，从第一带宽部分切换到初始带宽部分。
在一个实施例中，所述第一定时器包括以下至少之一：
带宽部分非激活定时器BWP-inactivitytimer(可以根据协议规定确定)，可以为现有的定时器；
新定义的定时器。
在一个实施例中，终端驻留在第一带宽部分上时，可以检测在第一带宽部分上是否存在数据传输，若不存在数据传输，那么可以启动第一定时器。在第一定时器运行期间，若在第一带宽部分上出现了数据传输，那么第一定时器重启。当第一定时器超时，可以确定在较长时间内，在第一带宽部分上没有数据传输，那么切换到初始带宽部分。那么网络设备可以确定在第一定时器超时时，终端切换到初始带宽部分。
在一个实施例中，当终端进入非激活态时，若驻留在第一带宽部分上，可以启动第一定时器，当第一定时器超时，终端可以确定在第一带宽部分上驻留时间较长，从而切换到初始带宽部分。在一些示例中，在第一定时器运行期间，若终端从第一带宽部分切换到了其他带宽部分(例如初始带宽部分或者第一带宽部分和初始带宽部分以外的带宽部分)，那么第一定时器可以终止计时。
在又一个实施例中，若终端配置有默认带宽部分，可以切换到默认带宽部分，如果没有配置默认带宽部分，那么切换到初始带宽部分。
第一定时器可以是现有的BWP-inactivitytimer，也可以新定义的定时器，具体可以根据需要选择，本公开不作限制。
图4是根据本公开的实施例示出的又一种组播业务接收方法的示意流程图。如图4所示，所述方法还包括：
在步骤S401中，根据协议规定或者网络设备的配置确定所述第一带宽部分的公共搜索空间(Common Search Space，CSS)；
在步骤S402中，在所述第一带宽部分的公共搜索空间上执行非激活态下的流程。
在一个实施例中，所述在非激活态下的流程包括终端处于非激活态时可以执行的流程，包括以下至少之一：无线资源控制连接建立；无线资源控制连接恢复；随机接入；小区选择；小区重选；接收系统消息；接收寻呼消息。当然，非激活态下的流程还可以包括其他流程，这里不再一一列举。
在图3所示的实施例中，终端之所以要切换到初始带宽部分，原因之一是因为初始带宽部分配置有用于进行无线资源控制连接建立、无线资源控制连接恢复、随机接入、小区选择、小区重选、接收系统消息、接收寻呼消息等操作的公共搜索空间，而这些操作属于非激活态下的流程。
根据本实施例，终端可以不切换到初始带宽部分执行非激活态下的流程，而是 继续驻留在第一带宽部分上执行非激活态下的流程，但是需要根据协议规定或者网络设备的配置确定第一带宽部分的公共搜索空间，其中，第一带宽部分的公共搜索空间用于供终端执行非激活态下的流程，因此，终端可以继续驻留在第一带宽部分上，在第一带宽部分的公共搜索空间上执行非激活态下的流程。
图5是根据本公开的实施例示出的一种配置发送方法的示意流程图。本实施例所示的配置发送方法可以由网络设备执行，所述网络设备可以与终端通信，所述网络设备包括但不限于4G基站、5G基站、6G基站等通信系统中的基站，所述终端包括但不限于手机、平板电脑、可穿戴设备、传感器、物联网设备等通信装置。
如图5所示，本公开实施例提供配置发送方法可以包括以下步骤：
在步骤S501中，向终端发送第一带宽部分关联的组播业务配置，基于所述第一带宽部分关联的组播业务配置向所述终端发送组播业务；其中，所述第一带宽部分的配置用于供所述终端进入非激活态后基于所述第一带宽部分关联的组播业务配置接收所述网络设备发送的所述组播业务。
在一个实施例中，第一带宽部分关联的组播业务配置包括公共频率资源CFR配置。当然，组播业务配置并不限于CFR配置，还可以包括其他配置，例如时域资源配置等。
根据本公开的实施例，通过向终端发送第一带宽部分关联的组播业务配置，后续可以基于所述第一带宽部分关联的组播业务配置向所述终端发送组播业务。并且使得终端在进入非激活态后，可以驻留在第一带宽部分，并基于第一带宽部分关联的组播业务配置接收组播业务，而不会切换到初始带宽部分，有利于避免组播业务接收过程出现问题。
需要说明的是，终端进入非激活态后，驻留在第一带宽部分，可以是协议规定的，也可以是网路设备配置的。对此，本公开并不限制。
其中，第一带宽部分可以是指终端在进入非激活态之前，在连接态时驻留的激活的带宽部分。终端在进入非激活态之前，可以基于第一带宽部分关联的组播业务配置接收组播业务，在进入非激活态之后，由于仍然驻留在第一带宽部分，所以可以继续基于第一带宽部分关联的组播业务配置接收组播业务，从而避免组播业务接收中断。
另外，第一带宽部分可以是初始带宽部分以外的带宽部分，也可以是初始带宽部分。例如在一个实施例中，所述第一带宽部分包括以下至少之一：
初始带宽部分；
连接态组播业务带宽部分，也即配置给终端在连接态接收组播业务的带宽部分；
非激活态组播业务带宽部分，也即配置给终端在非激活态接收组播业务的带宽部分。
在一些示例中，在第一带宽部分为初始带宽部分的情况下，通过向终端发送初始带宽部分关联的组播业务配置，使得终端在进入非激活态之后，可以驻留在初始带宽部分，并基于初始带宽部分关联的组播业务配置接收组播业务。
在一些相关技术中，网络设备仅针对连接态下终端的激活带宽部分配置关联的组播业务配置，当终端进入非连接态时，由于终端会切换到初始带宽部分上，但是由于初始带宽部分并未被配置为关联的组播业务配置，导致终端在初始带宽部分上不能基于初始带宽部分关联的组播业务配置接收组播业务，从而组播业务中断。而根据本实施例，可以针对初始带宽部分配置关联的组播业务配置，从而当终端进入非连接态时，可以在初始带宽部分上基于初始带宽部分关联的组播业务配置接收组播业务，确保组播业务的连续性。
在另一些示例中，在第一带宽部分为连接态组播业务带宽部分的情况下，可以在终端处于连接态时向终端发送连接态组播业务带宽部分关联的组播业务配置，使得终端在进入非激活态之后，可以继续驻留在连接态组播业务带宽部分，并基于连接态组播业务带宽部分关联的组播业务配置接收组播业务。
也就是说，网络设备也可以在终端处于非激活态时，向终端发送连接态组播业务带宽部分关联的组播业务配置，使得终端在非激活态驻留在连接态组播业务带宽部分，并基于连接态组播业务带宽部分关联的组播业务配置接收组播业务。
其中，连接态组播业务带宽部分可以为初始带宽部分，也可以为初始带宽部分以外的带宽部分，例如终端进入连接态后，网络设备为终端配置的专用带宽部分。
根据本实施例，可以实现对连接态组播业务带宽部分关联的组播业务配置的复用，也即终端可以在连接态下根据连接态组播业务带宽部分关联的组播业务配置接收组播业务，还可以在非激活态下根据连接态组播业务带宽部分关联的组播业务配置接收组播业务。
在又一些示例中，在第一带宽部分为非激活态组播业务带宽部分的情况下，可 以在终端处于连接态时向终端发送非激活态组播业务带宽部分关联的组播业务配置，使得终端在进入非激活态之后，可以继续驻留在非激活态组播业务带宽部分，并基于非激活态组播业务带宽部分关联的组播业务配置接收组播业务。
或者，网络设备也可以在终端处于非激活态时，向终端发送非激活态组播业务带宽部分关联的组播业务配置，使得终端在非激活态驻留在非激活态组播业务带宽部分，并基于非激活态组播业务带宽部分关联的组播业务配置接收组播业务。
其中，非激活态组播业务带宽部分可以为初始带宽部分，也可以为初始带宽部分以外的带宽部分。
在一些相关技术中，网络设备仅会为终端配置连接态组播业务带宽部分关联的组播业务配置，而没有为终端配置非激活态组播业务带宽部分关联的组播业务配置，这会导致终端在非激活态下处于非激活态组播业务带宽部分时，由于没有关联的组播业务配置而不能接收组播业务，从而组播业务中断。而根据本实施例，可以为终端配置非激活态组播业务带宽部分关联的组播业务配置，从而终端在非激活态下处于非激活态组播业务带宽部分时，可以根据非激活态组播业务带宽部分关联的组播业务配置而不能接收组播业务，有利于避免组播业务中断。
在一个实施例中，所述向终端发送第一带宽部分关联的组播业务配置包括以下至少之一：
在所述终端处于连接态时向所述终端发送所述第一带宽部分关联的组播业务配置；
在所述终端处于非连接态时向所述终端发送所述第一带宽部分关联的组播业务配置。
网络设备可以在终端处于连接态时，向终端发送第一带宽部分关联的组播业务配置，也可以在终端处于非连接态时，向终端发送第一带宽部分关联的组播业务配置。对此本公开并不限制。
在一个实施例中，所述第一带宽部分关联的组播业务配置携带在以下至少之一中：专有信令；公共广播信令。
在一个实施例中，所述专有信令包括以下至少之一：
无线资源控制释放RRCRelease消息；
无线资源控制重配置RRCReconfiguration消息；
无线资源控制恢复RRCResume消息。
需要说明的是，RRCRelease消息包括以下至少一项：携带挂起配置的RRCRelease消息；未携带挂起配置的RRCRelease消息。例如：通过向终端发送携带挂起配置的RRCRelease消息，可以使得终端进入非激活态。又例如：通过向终端发送未携带挂起配置的RRCRelease消息，可以使得终端进入空闲态。终端既可以在非连接态接收组播业务，也可以在空闲态接收组播业务，其中，在非连接态接收组播业务包括在非激活态接收组播业务和在空闲态接收组播业务。
在一个实施例中，所述公共广播信令包括以下至少之一：
系统信息块SIB；
组播业务控制信道MCCH
图6是根据本公开的实施例示出的另一种配置发送方法的示意流程图。如图6所示，所述方法还包括：
在步骤S601中，确定在第一场景下所述终端从所述第一带宽部分切换到初始带宽部分，例如终端将第一带宽部分去激活，将初始带宽部分激活。
在一个实施例中，在第一带宽部分不同于初始带宽部分的情况下，终端可以在第一场景下进行带宽部分切换，具体可以从第一带宽部分切换到初始带宽部分，以便满足第一场景下的需求。网络设备则可以确定在第一场景下终端从所述第一带宽部分切换到初始带宽部分，进而在初始带宽部分上与终端进行通信。
在一个实施例中，在所述终端为能力降低Redcap终端的情况下，所述初始带宽部分包括以下至少之一：
Redcap专属初始带宽部分；
常规初始带宽部分。
也即终端既可以切换到Redcap专属初始带宽部分，也可以切换到常规初始带宽部分
在一个示例中，在所述终端为能力降低Redcap终端的情况下，若为所述终端配置了Redcap专属初始带宽部分，确定在第一场景下所述终端从所述第一带宽部分切换到Redcap专属初始带宽部分。若未为所述终端被配置Redcap专属初始带宽部分， 确定在第一场景下所述终端从所述第一带宽部分切换到常规初始带宽部分。
对于Redcap终端而言，网络设备可以为终端配置两种初始带宽部分，一种是常规初始带宽部分，一种是Redcap专属初始带宽部分(这种带宽部分仅配置给Redcap终端)。其中，当为Redcap终端配置了Redcap专属初始带宽部分时，可以确定终端切换到初始带宽部分，具体是切换到Redcap专属初始带宽部分，而没有为Redcap终端被配置Redcap专属初始带宽部分时，那么可以确定终端切换到初始带宽部分，仍然是切换到常规初始带宽部分。
在另一个示例中，当终端为Redcap终端时，在第一场景下，终端可以任意切换到Redcap专属初始带宽部分和常规初始带宽部分中任一带宽部分。
在一个实施例中，所述第一场景包括以下至少之一：
发生第一事件，可以包括正在发生第一事件和将要发生第一事件；
接收到第一信息；
第一定时器超时。
在一个实施例中，无线资源控制连接建立；无线资源控制连接恢复；随机接入；小区选择；小区重选；接收系统消息；接收寻呼消息；停止接收组播业务。其中，停止接收组播业务的判定方式，包括但不限于终端移出接收组播业务的区域。需要说明的是，这里第一事件还可以包括其他需要终端从第一BWP上切换到初始BWP上的事件，这里不再一一列举。
由于无线资源控制连接建立、无线资源控制连接恢复、随机接入属于初始接入操作，终端进行这些操作需要在初始带宽部分上进行，因此，可以确定终端从第一带宽部分切换到初始带宽部分上进行无线资源控制连接建立、无线资源控制连接恢复、随机接入等操作。
类似地，终端进行小区选择、小区重选、接收系统消息、接收寻呼消息等操作，也需要在初始带宽部分上进行，因此，可以确定终端从第一带宽部分切换到初始带宽部分上进行小区选择、小区重选、接收系统消息、接收寻呼消息等操作。
可以理解的，终端进入非激活态后仍然驻留在第一带宽部分上，而没有切换到初始带宽部分上进行驻留，原因之一是为了在第一带宽部分上使用第一带宽部分关联的组播业务配置接收组播业务配置。那么终端当停止接收组播业务，就不必继续驻留 在第一带宽部分上了，可以切换到初始带宽部分上，以便进行初始接入、小区选择、小区重选、接收系统消息、接收寻呼消息等操作。因此，可以确定终端停止接收组播业务时，从第一带宽部分切换到了初始带宽部分。
在一个实施例中，所述第一信息包括以下至少之一：
物理层控制信令，例如下行控制信息DCI；
无线资源控制RRC信令；
媒体接入控制层信令，例如媒体接入控制层控制元素MAC CE。
在一个实施例中，第一信息可以用于指示终端从第一带宽部分切换到初始带宽部分，或者，第一信息可以用于指示其他内容，但是协议规定终端在接收到第一信息时，从第一带宽部分切换到初始带宽部分。
在一个实施例中，所述第一定时器包括以下至少之一：
带宽部分非激活定时器BWP-inactivitytimer，可以为现有的定时器；
新定义的定时器。
在一个实施例中，终端驻留在第一带宽部分上时，可以检测在第一带宽部分上是否存在数据传输，若不存在数据传输，那么可以启动第一定时器。在第一定时器运行期间，若在第一带宽部分上出现了数据传输，那么第一定时器重启。当第一定时器超时，可以确定在较长时间内，在第一带宽部分上没有数据传输，那么切换到初始带宽部分。那么网络设备可以确定在第一定时器超时时，终端切换到初始带宽部分。
在一个实施例中，当终端进入非激活态时，若驻留在第一带宽部分上，可以启动第一定时器，当第一定时器超时，终端可以确定在第一带宽部分上驻留时间较长，从而切换到初始带宽部分。其中，在第一定时器运行期间，若终端从第一带宽部分切换到了其他带宽部分(例如初始带宽部分或者第一带宽部分和初始带宽部分以外的带宽部分)，那么第一定时器可以终止计时。
在又一个实施例中，若为终端配置了默认带宽部分，可以确定终端切换到默认带宽部分，如果没有为配置默认带宽部分，可以确定终端切换到初始带宽部分。
而第一定时器可以是现有的BWP-inactivitytimer，也可以新定义的定时器，具体可以根据需要选择，本公开不作限制。
图7是根据本公开的实施例示出的又一种组播业务接收方法的示意流程图。如 图7所示，所述方法还包括：
在步骤S701中，为所述终端配置第一带宽部分的公共搜索空间，其中，所述第一带宽部分的公共搜索空间用于供所述终端执行非激活态下的流程。
在一个实施例中，所述在非激活态下的流程包括终端处于非激活态时可以执行的流程，包括以下至少之一：无线资源控制连接建立；无线资源控制连接恢复；随机接入；小区选择；小区重选；接收系统消息；接收寻呼消息。当然，非激活态下的流程还可以包括其他流程，这里不再一一列举。
在图6所示的实施例中，之所以确定终端切换到初始带宽部分，原因之一是因为初始带宽部分配置有用于进行无线资源控制连接建立、无线资源控制连接恢复、随机接入、小区选择、小区重选、接收系统消息、接收寻呼消息等操作的公共搜索空间，而这些操作属于非激活态下的流程。
根据本实施例，可以为终端配置第一带宽部分的公共搜索空间，其中，第一带宽部分的公共搜索空间用于供终端执行非激活态下的流程，因此，终端可以继续驻留在第一带宽部分上，在第一带宽部分的公共搜索空间上执行非激活态下的流程。那么可以确定终端继续驻留在第一带宽部分上。
与前述的组播业务接收方法、配置发送方法的实施例相对应，本公开还提供了组播业务接收装置、配置发送装置的实施例。
图8是根据本公开的实施例示出的一种组播业务接收装置的示意框图。本实施例所示的组播业务接收装置可以为终端，或者为终端中的模块构成的装置，所述终端包括但不限于手机、平板电脑、可穿戴设备、传感器、物联网设备等通信装置。所述终端可以与网络设备通信，所述网络设备包括但不限于4G、5G、6G等通信系统中的网络设备，例如基站、核心网等。
如图8所示，所述组播业务接收装置包括：
处理模块801，被配置为进入非激活态，驻留在所述第一带宽部分；
接收模块802，被配置为基于所述第一带宽部分关联的组播业务配置接收组播业务。
在一个实施例中，所述第一带宽部分关联的组播业务配置包括公共频率资源配置。
在一个实施例中，所述第一带宽部分包括以下至少之一：初始带宽部分；连接态组播业务带宽部分；非激活态组播业务带宽部分。
在一个实施例中，所述接收模块，还被配置为在连接态接收所述第一带宽部分关联的组播业务配置；和/或在非连接态接收所述第一带宽部分关联的组播业务配置。
在一个实施例中，所述第一带宽部分关联的组播业务配置携带在以下至少之一中：专有信令；公共广播信令。
在一个实施例中，所述专有信令包括以下至少之一：无线资源控制释放RRCRelease消息；无线资源控制重配置RRCReconfiguration消息；无线资源控制恢复RRCResume消息。
在一个实施例中，所述公共广播信令包括以下至少之一：系统信息块SIB；组播业务控制信道MCCH。
在一个实施例中，所述处理模块，还被配置为在第一场景下从所述第一带宽部分切换到初始带宽部分。
在一个实施例中，在所述终端为能力降低Redcap终端的情况下，所述初始带宽部分包括以下至少之一：Redcap专属初始带宽部分；常规初始带宽部分。
在一个实施例中，所述第一场景包括以下至少之一：发生第一事件；接收到第一信息；第一定时器超时。
在一个实施例中，所述第一事件包括以下至少之一：无线资源控制连接建立；无线资源控制连接恢复；随机接入；小区选择；小区重选；接收系统消息；接收寻呼消息；停止接收组播业务。
在一个实施例中，所述第一信息包括以下至少之一：物理层控制信令；无线资源控制RRC信令；媒体接入控制层信令。
在一个实施例中，所述第一定时器包括以下至少之一：带宽部分非激活定时器BWP-inactivitytimer；新定义的定时器。
在一个实施例中，所述处理模块，还被配置为根据协议规定或者网络设备的配置确定所述第一带宽部分的公共搜索空间；在所述第一带宽部分的公共搜索空间上执行非激活态下的流程。
在一个实施例中，所述在非激活态下的流程包括以下至少之一：无线资源控制 连接建立；无线资源控制连接恢复；随机接入；小区选择；小区重选；接收系统消息；接收寻呼消息。
图9是根据本公开的实施例示出的一种配置发送装置的示意框图。本实施例所示的配置发送装置可以为网络设备，或者为网络设备中的模块构成的装置，所述网络设备可以与终端通信。所述终端包括但不限于手机、平板电脑、可穿戴设备、传感器、物联网设备等通信装置。所述终端可以与网络设备通信，所述网络设备包括但不限于4G、5G、6G等通信系统中的网络设备，例如基站、核心网等。
如图9所示，所述配置发送装置包括：
发送模块901，被配置为向终端发送第一带宽部分关联的组播业务配置，基于所述第一带宽部分关联的组播业务配置向所述终端发送组播业务；其中，所述第一带宽部分的配置用于供所述终端进入非激活态后基于所述第一带宽部分关联的组播业务配置接收所述网络设备发送的所述组播业务。
在一个实施例中，所述第一带宽部分关联的组播业务配置包括公共频率资源配置。
在一个实施例中，所述第一带宽部分包括以下至少之一：初始带宽部分；连接态组播业务带宽部分；非激活态组播业务带宽部分。
在一个实施例中，所述发送模块，被配置为执行以下包括以下至少之一：在所述终端处于连接态时向所述终端发送所述第一带宽部分关联的组播业务配置；在所述终端处于非连接态时向所述终端发送所述第一带宽部分关联的组播业务配置。
在一个实施例中，所述第一带宽部分关联的组播业务配置携带在以下至少之一中：专有信令；公共广播信令。
在一个实施例中，所述专有信令包括以下至少之一：无线资源控制释放RRCRelease消息；无线资源控制重配置RRCReconfiguration消息；无线资源控制恢复RRCResume消息。
在一个实施例中，所述公共广播信令包括以下至少之一：系统信息块SIB；组播业务控制信道MCCH
在一个实施例中，所述装置还包括：处理模块，被配置为确定在第一场景下所述终端从所述第一带宽部分切换到初始带宽部分。
在一个实施例中，在所述终端为能力降低Redcap终端的情况下，所述初始带宽部分包括以下至少之一：Redcap专属初始带宽部分；常规初始带宽部分。
在一个实施例中，所述第一场景包括以下至少之一：发生第一事件；接收到第一信息；第一定时器超时。
在一个实施例中，所述第一事件包括以下至少之一：无线资源控制连接建立；无线资源控制连接恢复；随机接入；小区选择；小区重选；接收系统消息；接收寻呼消息；停止接收组播业务。
在一个实施例中，所述第一信息包括以下至少之一：物理层信令；无线资源控制RRC信令；媒体接入控制层信令。
在一个实施例中，所述第一定时器包括以下至少之一：带宽部分非激活定时器BWP-inactivitytimer；新定义的定时器。
在一个实施例中，所述装置还包括：发送模块，被配置为为所述终端配置第一带宽部分的公共搜索空间，其中，所述第一带宽部分的公共搜索空间用于供所述终端执行非激活态下的流程。
在一个实施例中，所述在非激活态下的流程包括以下至少之一：无线资源控制连接建立；无线资源控制连接恢复；随机接入；小区选择；小区重选；接收系统消息；接收寻呼消息。
关于上述实施例中的装置，其中各个模块执行操作的具体方式已经在相关方法的实施例中进行了详细描述，此处将不做详细阐述说明。
对于装置实施例而言，由于其基本对应于方法实施例，所以相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的模块可以是或者也可以不是物理上分开的，作为模块显示的部件可以是或者也可以不是物理模块，即可以位于一个地方，或者也可以分布到多个网络模块上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
本公开的实施例还提出一种组播业务接收系统，包括终端、网络侧设备，其中所述终端被配置为实现上述任一实施例所述的组播业务接收方法，所述网络设备被配置为实现上述任一实施例所述的配置发送方法。
本公开的实施例还提出一种通信装置，包括：处理器；用于存储计算机程序的存储器；其中，当所述计算机程序被处理器执行时，实现上述任一实施例所述的组播业务接收方法。
本公开的实施例还提出一种通信装置，包括：处理器；用于存储计算机程序的存储器；其中，当所述计算机程序被处理器执行时，实现上述任一实施例所述的配置发送方法。
本公开的实施例还提出一种计算机可读存储介质，用于存储计算机程序，当所述计算机程序被处理器执行时，实现上述任一实施例所述的组播业务接收方法。
本公开的实施例还提出一种计算机可读存储介质，用于存储计算机程序，当所述计算机程序被处理器执行时，实现上述任一实施例所述的配置发送方法。
如图10所示，图10是根据本公开的实施例示出的一种用于配置发送的装置1000的示意框图。装置1000可以被提供为一基站。参照图10，装置1000包括处理组件1022、无线发射/接收组件1024、天线组件1026、以及无线接口特有的信号处理部分，处理组件1022可进一步包括一个或多个处理器。处理组件1022中的其中一个处理器可以被配置为实现上述任一实施例所述的配置发送方法。
图11是根据本公开的实施例示出的一种用于组播业务接收的装置1100的示意框图。例如，装置1100可以是移动电话、计算机、数字广播终端、消息收发设备、游戏控制台、平板设备、医疗设备、健身设备、个人数字助理等。
参照图11，装置1100可以包括以下一个或多个组件：处理组件1102、存储器1104、电源组件1106、多媒体组件1108、音频组件1110、输入/输出(I/O)的接口1112、传感器组件1114以及通信组件1116。
处理组件1102通常控制装置1100的整体操作，诸如与显示、电话呼叫、数据通信、相机操作和记录操作相关联的操作。处理组件1102可以包括一个或多个处理器1120来执行指令，以完成上述的组播业务接收方法的全部或部分步骤。此外，处理组件1102可以包括一个或多个模块，便于处理组件1102和其他组件之间的交互。例如，处理组件1102可以包括多媒体模块，以方便多媒体组件1108和处理组件1102之间的交互。
存储器1104被配置为存储各种类型的数据以支持在装置1100的操作。这些数据的示例包括用于在装置1100上操作的任何应用程序或方法的指令、联系人数据、电 话簿数据、消息、图片、视频等。存储器1104可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)、电可擦除可编程只读存储器(EEPROM)、可擦除可编程只读存储器(EPROM)、可编程只读存储器(PROM)，只读存储器(ROM)、磁存储器、快闪存储器、磁盘或光盘。
电源组件1106为装置1100的各种组件提供电力。电源组件1106可以包括电源管理系统，一个或多个电源，及其他与为装置1100生成、管理和分配电力相关联的组件。
多媒体组件1108包括在所述装置1100和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件1108包括一个前置摄像头和/或后置摄像头。当装置1100处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件1110被配置为输出和/或输入音频信号。例如，音频组件1110包括一个麦克风(MIC)，当装置1100处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器1104或经由通信组件1116发送。在一些实施例中，音频组件1110还包括一个扬声器，用于输出音频信号。
I/O接口1112为处理组件1102和外围接口模块之间提供接口，上述外围接口模块可以是键盘、点击轮、按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件1114包括一个或多个传感器，用于为装置1100提供各个方面的状态评估。例如，传感器组件1114可以检测到装置1100的打开/关闭状态，组件的相对定位，例如所述组件为装置1100的显示器和小键盘，传感器组件1114还可以检测装置1100或装置1100一个组件的位置改变，用户与装置1100接触的存在或不存在，装置1100方位或加速/减速和装置1100的温度变化。传感器组件1114可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件1114 还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件1114还可以包括加速度传感器、陀螺仪传感器、磁传感器、压力传感器或温度传感器。
通信组件1116被配置为便于装置1100和其他设备之间有线或无线方式的通信。装置1100可以接入基于通信标准的无线网络，如WiFi、2G、3G、4G LTE、5G NR或它们的组合。在一个示例性实施例中，通信组件1116经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件1116还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术、红外数据协会(IrDA)技术、超宽带(UWB)技术、蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，装置1100可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述组播业务接收方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器1104，上述指令可由装置1100的处理器1120执行以完成上述组播业务接收方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
本领域技术人员在考虑说明书及实践这里公开的公开后，将容易想到本公开的其它实施方案。本公开旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。
需要说明的是，在本文中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。术语“包括”、“包含”或者其任何其他变体意 在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
以上对本公开实施例所提供的方法和装置进行了详细介绍，本文中应用了具体个例对本公开的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本公开的方法及其核心思想；同时，对于本领域的一般技术人员，依据本公开的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本公开的限制。

Claims (37)

  1. 一种组播业务接收方法，其特征在于，由终端执行，所述方法包括：
    进入非激活态，驻留在第一带宽部分；
    基于所述第一带宽部分关联的组播业务配置接收组播业务。
  2. 根据权利要求1所述的方法，其特征在于，所述第一带宽部分关联的组播业务配置包括公共频率资源配置。
  3. 根据权利要求1所述的方法，其特征在于，所述第一带宽部分包括以下至少之一：
    初始带宽部分；
    连接态组播业务带宽部分；
    非激活态组播业务带宽部分。
  4. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    在连接态接收所述第一带宽部分关联的组播业务配置；和/或
    在非连接态接收所述第一带宽部分关联的组播业务配置。
  5. 根据权利要求4所述的方法，其特征在于，所述第一带宽部分关联的组播业务配置携带在以下至少之一中：
    专有信令；
    公共广播信令。
  6. 根据权利要求5所述的方法，其特征在于，所述专有信令包括以下至少之一：
    无线资源控制释放RRCRelease消息；
    无线资源控制重配置RRCReconfiguration消息；
    无线资源控制恢复RRCResume消息。
  7. 根据权利要求5所述的方法，其特征在于，所述公共广播信令包括以下至少之一：
    系统信息块SIB；
    组播业务控制信道MCCH。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述方法还包括：
    在第一场景下从所述第一带宽部分切换到初始带宽部分。
  9. 根据权利要求8所述的方法，其特征在于，在所述终端为能力降低Redcap终端的情况下，所述初始带宽部分包括以下至少之一：
    Redcap专属初始带宽部分；
    常规初始带宽部分。
  10. 根据权利要求8所述的方法，其特征在于，所述第一场景包括以下至少之一：
    发生第一事件；
    接收到第一信息；
    第一定时器超时。
  11. 根据权利要求10所述的方法，其特征在于，所述第一事件包括以下至少之一：
    无线资源控制连接建立；
    无线资源控制连接恢复；
    随机接入；
    小区选择；
    小区重选；
    接收系统消息；
    接收寻呼消息；
    停止接收组播业务。
  12. 根据权利要求10所述的方法，其特征在于，所述第一信息包括以下至少之一：
    物理层控制信令；
    无线资源控制RRC信令；
    媒体接入控制层信令。
  13. 根据权利要求10所述的方法，其特征在于，所述第一定时器包括以下至少之一：
    带宽部分非激活定时器BWP-inactivitytimer；
    新定义的定时器。
  14. 根据权利要求1至7中任一项所述的方法，其特征在于，所述方法还包括：
    根据协议规定或者网络设备的配置确定所述第一带宽部分的公共搜索空间；
    在所述第一带宽部分的公共搜索空间上执行非激活态下的流程。
  15. 根据权利要求14所述的方法，其特征在于，所述在非激活态下的流程包括以下至少之一：
    无线资源控制连接建立；
    无线资源控制连接恢复；
    随机接入；
    小区选择；
    小区重选；
    接收系统消息；
    接收寻呼消息。
  16. 一种配置发送方法，其特征在于，由网络设备执行，所述方法包括：
    向终端发送第一带宽部分关联的组播业务配置，基于所述第一带宽部分关联的组播业务配置向所述终端发送组播业务；其中，所述第一带宽部分的配置用于供所述终端进入非激活态后基于所述第一带宽部分关联的组播业务配置接收所述网络设备发送的所述组播业务。
  17. 根据权利要求16所述的方法，其特征在于，所述第一带宽部分关联的组播业务配置包括公共频率资源配置。
  18. 根据权利要求16所述的方法，其特征在于，所述第一带宽部分包括以下至少之一：
    初始带宽部分；
    连接态组播业务带宽部分；
    非激活态组播业务带宽部分。
  19. 根据权利要求16所述的方法，其特征在于，所述向终端发送第一带宽部分关联的组播业务配置包括以下至少之一：
    在所述终端处于连接态时向所述终端发送所述第一带宽部分关联的组播业务配置；
    在所述终端处于非连接态时向所述终端发送所述第一带宽部分关联的组播业务配置。
  20. 根据权利要求19所述的方法，其特征在于，所述第一带宽部分关联的组播业务配置携带在以下至少之一中：
    专有信令；
    公共广播信令。
  21. 根据权利要求20所述的方法，其特征在于，所述专有信令包括以下至少之一：
    无线资源控制释放RRCRelease消息；
    无线资源控制重配置RRCReconfiguration消息；
    无线资源控制恢复RRCResume消息。
  22. 根据权利要求20所述的方法，其特征在于，所述公共广播信令包括以下至少之一：
    系统信息块SIB；
    组播业务控制信道MCCH。
  23. 根据权利要求16至21中任一项所述的方法，其特征在于，所述方法还包括：
    确定在第一场景下所述终端从所述第一带宽部分切换到初始带宽部分。
  24. 根据权利要求23所述的方法，其特征在于，在所述终端为能力降低Redcap终端的情况下，所述初始带宽部分包括以下至少之一：
    Redcap专属初始带宽部分；
    常规初始带宽部分。
  25. 根据权利要求23所述的方法，其特征在于，所述第一场景包括以下至少之一：
    发生第一事件；
    接收到第一信息；
    第一定时器超时。
  26. 根据权利要求25所述的方法，其特征在于，所述第一事件包括以下至少之一：
    无线资源控制连接建立；
    无线资源控制连接恢复；
    随机接入；
    小区选择；
    小区重选；
    接收系统消息；
    接收寻呼消息；
    停止接收组播业务。
  27. 根据权利要求25所述的方法，其特征在于，所述第一信息包括以下至少之一：
    物理层信令；
    无线资源控制RRC信令；
    媒体接入控制层信令。
  28. 根据权利要求25所述的方法，其特征在于，所述第一定时器包括以下至少之一：
    带宽部分非激活定时器BWP-inactivitytimer；
    新定义的定时器。
  29. 根据权利要求16至21中任一项所述的方法，其特征在于，所述方法还包括：
    为所述终端配置第一带宽部分的公共搜索空间，其中，所述第一带宽部分的公共 搜索空间用于供所述终端执行非激活态下的流程。
  30. 根据权利要求29所述的方法，其特征在于，所述在非激活态下的流程包括以下至少之一：
    无线资源控制连接建立；
    无线资源控制连接恢复；
    随机接入；
    小区选择；
    小区重选；
    接收系统消息；
    接收寻呼消息。
  31. 一种组播业务接收装置，其特征在于，所述装置包括：
    处理模块，被配置为进入非激活态，驻留在所述第一带宽部分；
    接收模块，被配置为基于所述第一带宽部分关联的组播业务配置接收组播业务。
  32. 一种配置发送装置，其特征在于，所述装置包括：
    发送模块，被配置为向终端发送第一带宽部分关联的组播业务配置，其中，所述第一带宽部分的配置用于供所述终端进入非激活态后，驻留在所述第一带宽部分基于所述第一带宽部分关联的组播业务配置向所述终端发送组播业务。
  33. 一种组播业务接收系统，其特征在于，包括终端、网络侧设备，其中所述终端被配置为实现权利要求1至15中任一项所述的组播业务接收方法，所述网络设备被配置为实现权利要求16至30中任一项所述的配置发送方法。
  34. 一种通信装置，其特征在于，包括：
    处理器；
    用于存储计算机程序的存储器；
    其中，当所述计算机程序被处理器执行时，实现权利要求1至15中任一项所述的组播业务接收方法。
  35. 一种通信装置，其特征在于，包括：
    处理器；
    用于存储计算机程序的存储器；
    其中，当所述计算机程序被处理器执行时，实现权利要求16至30中任一项所述的配置发送方法。
  36. 一种计算机可读存储介质，用于存储计算机程序，其特征在于，当所述计算 机程序被处理器执行时，实现权利要求1至15中任一项所述的组播业务接收方法。
  37. 一种计算机可读存储介质，用于存储计算机程序，其特征在于，当所述计算机程序被处理器执行时，实现权利要求16至30中任一项所述的配置发送方法。
PCT/CN2022/126803 2022-10-21 2022-10-21 组播业务接收、配置发送方法和装置 WO2024082294A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/126803 WO2024082294A1 (zh) 2022-10-21 2022-10-21 组播业务接收、配置发送方法和装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/126803 WO2024082294A1 (zh) 2022-10-21 2022-10-21 组播业务接收、配置发送方法和装置

Publications (1)

Publication Number Publication Date
WO2024082294A1 true WO2024082294A1 (zh) 2024-04-25

Family

ID=90736726

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/126803 WO2024082294A1 (zh) 2022-10-21 2022-10-21 组播业务接收、配置发送方法和装置

Country Status (1)

Country Link
WO (1) WO2024082294A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020057979A1 (en) * 2018-09-18 2020-03-26 Sony Corporation Communications device, infrastructure equipment and methods
CN113453343A (zh) * 2020-03-25 2021-09-28 展讯通信（上海）有限公司 业务的请求方法及装置
CN113747368A (zh) * 2020-05-28 2021-12-03 华为技术有限公司 多播信息的接收方法、指示信息的收发方法及相关装置
CN113950005A (zh) * 2020-07-17 2022-01-18 维沃移动通信有限公司 业务接收方法、终端及网络侧设备
US20220046690A1 (en) * 2020-08-06 2022-02-10 Lg Electronics Inc. Method and apparatus for transmitting/receiving wireless signal in wireless communication system
CN115190432A (zh) * 2021-04-01 2022-10-14 华为技术有限公司 一种通信方法及装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020057979A1 (en) * 2018-09-18 2020-03-26 Sony Corporation Communications device, infrastructure equipment and methods
CN113453343A (zh) * 2020-03-25 2021-09-28 展讯通信（上海）有限公司 业务的请求方法及装置
CN113747368A (zh) * 2020-05-28 2021-12-03 华为技术有限公司 多播信息的接收方法、指示信息的收发方法及相关装置
CN113950005A (zh) * 2020-07-17 2022-01-18 维沃移动通信有限公司 业务接收方法、终端及网络侧设备
US20220046690A1 (en) * 2020-08-06 2022-02-10 Lg Electronics Inc. Method and apparatus for transmitting/receiving wireless signal in wireless communication system
CN115190432A (zh) * 2021-04-01 2022-10-14 华为技术有限公司 一种通信方法及装置

Similar Documents

Publication Publication Date Title
WO2020056745A1 (zh) 带宽部分的切换触发方法及装置、信息配置方法及装置
WO2022041245A1 (zh) 寻呼原因发送方法和装置、寻呼原因获取方法和装置
WO2022021097A1 (zh) 一种小区重选方法、小区重选装置及存储介质
WO2021026824A1 (zh) 非活动定时器的控制方法和装置
WO2019113883A1 (zh) 用户设备省电方法、装置、用户设备和基站
WO2021081796A1 (zh) 寻呼信令接收方法和装置、寻呼信令发送方法和装置
WO2023279393A1 (zh) 信息发送、寻呼限制方法和装置、通信装置和存储介质
WO2020223931A1 (zh) 小区切换方法及装置、切换配置方法及装置和用户设备
WO2020029285A1 (zh) 信息发送、接收方法及装置、基站和用户设备
WO2023279394A1 (zh) 一种直连通信方法和装置
JP2021141561A (ja) デュアルｓｉｍ携帯電話のページング衝突を対処する方法、装置及び媒体
WO2024082294A1 (zh) 组播业务接收、配置发送方法和装置
WO2022198398A1 (zh) 控制指示方法和装置、行为控制方法和装置
WO2024082295A1 (zh) 小区处理、小区处理指示方法和装置
WO2020062083A1 (zh) 控制指令传输方法、基站、终端及存储介质
WO2024011528A1 (zh) 端口切换、端口切换指示方法和装置
WO2024020807A1 (zh) 非激活态组播业务接收、配置发送方法和装置
WO2023035121A1 (zh) 能力确定、指示方法和装置、通信装置和存储介质
WO2023123459A1 (zh) 信息接收、传输方法和装置、通信装置和存储介质
WO2022227075A1 (zh) 原因确定方法和装置、原因指示方法和装置
WO2023004602A1 (zh) 信息发送、寻呼限制方法和装置、通信装置和存储介质
WO2023035122A1 (zh) 能力指示、确定方法和装置、通信装置和存储介质
WO2023226055A1 (zh) 寻呼消息接收、发送方法和装置、通信装置及存储介质
WO2024020808A1 (zh) 非激活态组播业务接收、配置指示信息发送方法和装置
WO2023035123A1 (zh) 能力指示、确定方法和装置、通信装置和存储介质