WO2022133877A1

WO2022133877A1 - Mbs service indication method and apparatus, terminal device, and network device

Info

Publication number: WO2022133877A1
Application number: PCT/CN2020/138911
Authority: WO
Inventors: 王淑坤
Original assignee: Oppo广东移动通信有限公司
Priority date: 2020-12-24
Filing date: 2020-12-24
Publication date: 2022-06-30
Also published as: CN116250259A

Abstract

Embodiments of the present application provide a multicast broadcast service (MBS) indication method and apparatus, terminal device, and network device, said method comprising: a terminal device sending identification information of an MBS service to a network device, said MBS service being an MBS service expected, or an MBS service currently being received, by said terminal device; said identification information of the MBS service is used for the configuration of a dedicated downlink bandwidth part (BWP) of the terminal device and/or the identification information of the MBS service is used for determining a target cell pending handover of the terminal device.

Description

Method and device for indicating MBS service, terminal equipment, and network equipment

technical field

The embodiments of the present application relate to the field of mobile communication technologies, and in particular, to a method and apparatus for indicating a Multicast Broadcast Service (MBS) service, a terminal device, and a network device.

Background technique

In a Long Term Evolution (Long Term Evolution, LTE) system, a cell has only one bandwidth (ie, a system bandwidth), and a terminal device in the cell will work on the bandwidth. Different from the LTE system, in the New Radio (NR) system, after the terminal device enters the Radio Resource Control (RRC) connection state, the network side configures multiple dedicated bandwidth parts (Band Width Parts) for the terminal device. BWP), the terminal device can switch between these dedicated BWPs in the RRC connection state.

In the NR system, the broadcast MBS service is supported, and the terminal equipment can receive the broadcast MBS service in the RRC idle state or the RRC inactive state or the RRC connected state. After the terminal device enters the RRC connected state from the RRC idle state or the RRC inactive state, the network side does not know the MBS service previously received by the terminal device. If a dedicated BWP is configured for the terminal device according to the current method, the terminal device cannot receive the MBS service normally. .

SUMMARY OF THE INVENTION

The embodiments of the present application provide an MBS service indication method and apparatus, terminal equipment, and network equipment.

The MBS service indication method provided by the embodiment of the present application includes:

The terminal device sends the identification information of the MBS service to the network device, where the MBS service is the MBS service expected by the terminal device or the MBS service being received;

Wherein, the identification information of the MBS service is used for the configuration of the dedicated downlink BWP of the terminal device and/or the identification information of the MBS service is used to determine the target cell to be handed over by the terminal device.

The network device receives the identification information of the MBS service sent by the terminal device, where the MBS service is the MBS service expected by the terminal device or the MBS service being received;

The identification information of the MBS service is used by the network device to configure a dedicated downlink BWP for the terminal device and/or the identification information of the MBS service is used by the network device to select the target to be handed over for the terminal device community.

The device for indicating an MBS service provided by the embodiment of the present application is applied to a terminal device, and the device includes:

a communication unit, configured to send identification information of an MBS service to a network device, where the MBS service is an MBS service expected by the terminal device or an MBS service being received;

Wherein, the identification information of the MBS service is used for the configuration of the dedicated downlink BWP of the terminal equipment and/or the identification information of the MBS service is used to determine the target cell to be handed over by the terminal equipment.

The device for indicating an MBS service provided by the embodiment of the present application is applied to network equipment, and the device includes:

a communication unit, configured to receive identification information of an MBS service sent by a terminal device, where the MBS service is an MBS service expected by the terminal device or an MBS service being received;

The terminal device provided by the embodiments of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the above-mentioned instruction method of the MBS service.

The network device provided by the embodiments of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the above-mentioned instruction method of the MBS service.

The chip provided by the embodiment of the present application is used to implement the above-mentioned indication method of the MBS service.

Specifically, the chip includes: a processor for invoking and running a computer program from the memory, so that the device installed with the chip executes the above-mentioned instruction method of the MBS service.

The computer-readable storage medium provided by the embodiment of the present application is used to store a computer program, and the computer program enables a computer to execute the above-mentioned MBS service instruction method.

The computer program product provided by the embodiments of the present application includes computer program instructions, and the computer program instructions cause the computer to execute the above-mentioned MBS service instruction method.

The computer program provided by the embodiment of the present application, when it runs on a computer, enables the computer to execute the above-mentioned MBS service instruction method.

Through the above technical solution, the terminal device indicates to the network device the MBS service expected by the terminal device or the identification information of the MBS service being received, so that the network device can configure the terminal device with a reasonable dedicated service according to the identification information of the MBS service. The downlink BWP and/or the correct selection of the target cell to be handed over ensures that the terminal equipment can normally receive the MBS service.

Description of drawings

The drawings described herein are used to provide further understanding of the present application and constitute a part of the present application. The schematic embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation of the present application. In the attached image:

FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application;

2 is a schematic flowchart 1 of a method for indicating an MBS service provided by an embodiment of the present application;

3 is a second schematic flowchart of a method for indicating an MBS service provided by an embodiment of the present application;

FIG. 4 is a schematic flowchart 3 of a method for indicating an MBS service provided by an embodiment of the present application;

5 is a fourth schematic flowchart of a method for indicating an MBS service provided by an embodiment of the present application;

FIG. 6 is a schematic flowchart 5 of a method for indicating an MBS service provided by an embodiment of the present application;

7 is a schematic diagram 1 of the structure and composition of an indication device for an MBS service provided by an embodiment of the present application;

FIG. 8 is a second schematic diagram of the structure and composition of an indication device for an MBS service provided by an embodiment of the present application;

FIG. 9 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 10 is a schematic structural diagram of a chip according to an embodiment of the present application;

FIG. 11 is a schematic block diagram of a communication system provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (Long Term Evolution, LTE) system, LTE Frequency Division Duplex (Frequency Division Duplex, FDD) system, LTE Time Division Duplex (Time Division Duplex) , TDD), systems, 5G communication systems or future communication systems, etc.

Exemplarily, a communication system 100 to which this embodiment of the present application is applied is shown in FIG. 1 . The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal 120 (or referred to as a communication terminal, a terminal). The network device 110 may provide communication coverage for a particular geographic area and may communicate with terminals located within the coverage area. Optionally, the network device 110 may be an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the The network device can be a mobile switching center, a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a network device in a future communication system.

The communication system 100 also includes at least one terminal 120 located within the coverage of the network device 110 . "Terminal" as used herein includes, but is not limited to, connections via wired lines, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connections; and/or another data connection/network; and/or via a wireless interface, e.g. for cellular networks, Wireless Local Area Networks (WLAN), digital television networks such as DVB-H networks, satellite networks, AM-FM A broadcast transmitter; and/or a device of another terminal configured to receive/transmit a communication signal; and/or an Internet of Things (IoT) device. A terminal arranged to communicate through a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal" or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; Personal Communications System (PCS) terminals that may combine cellular radio telephones with data processing, facsimile, and data communication capabilities; may include radio telephones, pagers, Internet/Intranet PDAs with networking access, web browsers, memo pads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or others including radiotelephone transceivers electronic device. A terminal may refer to an access terminal, user equipment (UE), subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in 5G networks or terminals in future evolved PLMNs, etc.

Optionally, direct terminal (Device to Device, D2D) communication may be performed between the terminals 120 .

Optionally, the 5G communication system or the 5G network may also be referred to as a new radio (New Radio, NR) system or an NR network.

FIG. 1 exemplarily shows one network device and two terminals. Optionally, the communication system 100 may include multiple network devices, and the coverage of each network device may include other numbers of terminals. This embodiment of the present application This is not limited.

Optionally, the communication system 100 may further include other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.

It should be understood that, in the embodiments of the present application, a device having a communication function in the network/system may be referred to as a communication device. Taking the communication system 100 shown in FIG. 1 as an example, the communication device may include a network device 110 and a terminal 120 with a communication function, and the network device 110 and the terminal 120 may be the specific devices described above, which will not be repeated here; The device may further include other devices in the communication system 100, such as other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" in this article is only an association relationship to describe the associated objects, indicating that there can be three kinds of relationships, for example, A and/or B, it can mean that A exists alone, A and B exist at the same time, and A and B exist independently B these three cases. In addition, the character "/" in this document generally indicates that the related objects are an "or" relationship.

In order to facilitate the understanding of the technical solutions of the embodiments of the present application, the following describes the technical solutions related to the embodiments of the present application.

With people's pursuit of speed, delay, high-speed mobility, energy efficiency, and the diversity and complexity of services in future life, the ^3rd Generation Partnership Project (3GPP) international standards organization began to develop 5G . The main application scenarios of 5G are: Enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), Massive Machine-Type Communications (mMTC) ).

On the one hand, eMBB still aims at users' access to multimedia content, services and data, and its demand is growing rapidly. On the other hand, since eMBB may be deployed in different scenarios, such as indoor, urban, rural, etc., its capabilities and requirements are also quite different, so it cannot be generalized and must be analyzed in detail in combination with specific deployment scenarios. Typical applications of URLLC include: industrial automation, power automation, telemedicine operations (surgery), traffic safety assurance, etc. Typical features of mMTC include: high connection density, small data volume, latency-insensitive services, low cost and long service life of the module.

In the early deployment of NR, complete NR coverage is difficult to obtain, so typical network coverage is wide-area LTE coverage and NR island coverage mode. And a lot of LTE is deployed in sub-6GHz, and there is very little sub-6GHz spectrum available for 5G. Therefore, NR must study the spectrum application above 6GHz, while the high frequency band has limited coverage and fast signal fading. At the same time, in order to protect the early investment of mobile operators in LTE, a working mode of tight interworking between LTE and NR is proposed.

RRC status

5G defines a new Radio Resource Control (RRC) state, that is, RRC_INACTIVE state, in order to reduce air interface signaling, quickly restore wireless connections, and quickly restore data services. This state is different from the RRC idle (RRC_IDLE) state and the RRC active (RRC_ACTIVE) state. in,

1) RRC_IDLE state (referred to as idle state): mobility is UE-based cell selection reselection, paging is initiated by the core network (Core Network, CN), and the paging area is configured by the CN. There is no UE context and no RRC connection on the base station side.

2) RRC_CONNECTED state (referred to as connected state): there is an RRC connection, and a UE context exists on the base station side and the UE side. The network side knows that the location of the UE is at the specific cell level. Mobility is the mobility controlled by the network side. Unicast data can be transmitted between the UE and the base station.

3) RRC_INACTIVE state (referred to as inactive state): mobility is UE-based cell selection reselection, there is a connection between CN-NR, UE context exists on a certain base station, paging is triggered by RAN, based on The paging area of the RAN is managed by the RAN, and the network side knows the location of the UE based on the paging area level of the RAN.

Multimedia Broadcast Multicast Service (MBMS)

MBMS is a technology that transmits data from a data source to multiple terminal devices by sharing network resources. This technology can effectively utilize network resources while providing multimedia services, and realize the broadcast of multimedia services at higher rates (such as 256kbps). and multicast.

Due to the low spectral efficiency of MBMS, it is not enough to effectively carry and support the operation of mobile TV type services. Therefore, in LTE, 3GPP clearly proposes to enhance the support capability for downlink high-speed MBMS services, and determines the design requirements for the physical layer and air interface.

3GPP R9 introduced evolved MBMS (evolved MBMS, eMBMS) into LTE. eMBMS proposes the concept of Single Frequency Network (SFN), namely Multimedia Broadcast Multicast Service Single Frequency Network (MBSFN), MBSFN uses a uniform frequency to send service data in all cells at the same time, but To ensure synchronization between cells. In this way, the overall signal-to-noise ratio distribution of the cell can be greatly improved, and the spectral efficiency will also be greatly improved accordingly. eMBMS implements service broadcast and multicast based on IP multicast protocol.

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

The concept of Single Cell Point To Multiploint (SC-PTM) was introduced in 3GPP R13, and SC-PTM is based on the MBMS network architecture.

MBMS introduces new logical channels, including Single Cell Multicast Control Channel (SC-MCCH) and Single Cell Multicast Transport Channel (SC-MTCH). SC-MCCH and SC-MTCH are mapped to downlink shared channel (Downlink-Shared Channel, DL-SCH), further, DL-SCH is mapped to physical downlink shared channel (Physical Downlink Shared Channel, PDSCH), wherein, SC - MCCH and SC-MTCH belong to logical channels, DL-SCH belongs to transport channels, and PDSCH belongs to physical channels. SC-MCCH and SC-MTCH do not support hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ) operations.

MBMS introduces a new system information block (System Information Block, SIB) type, namely SIB20. Specifically, the configuration information of the SC-MCCH is transmitted through the SIB20, and a cell has only one SC-MCCH. The configuration information of the SC-MCCH includes the modification period of the SC-MCCH, the repetition period of the SC-MCCH, and information such as the radio frame and subframe in which the SC-MCCH is scheduled. Further, 1) the boundary of the modification period of SC-MCCH satisfies SFN mod m=0, where SFN represents the system frame number of the boundary, and m is the modification period of SC-MCCH configured in SIB20 (ie sc-mcch-ModificationPeriod). 2) The radio frame for scheduling SC-MCCH satisfies: SFN mod mcch-RepetitionPeriod=mcch-Offset, where SFN represents the system frame number of the radio frame, mcch-RepetitionPeriod represents the repetition period of SC-MCCH, and mcch-Offset represents SC-MCCH offset. 3) The subframe in which the SC-MCCH is scheduled is indicated by sc-mcch-Subframe.

The SC-MCCH is scheduled through the Physical Downlink Control Channel (PDCCH). On the one hand, a new wireless network temporary identity (Radio Network Tempory Identity, RNTI), that is, a single cell RNTI (Single Cell RNTI, SC-RNTI), is introduced to identify the PDCCH (such as SC-MCCH PDCCH) used for scheduling SC-MCCH, Optionally, the fixed value of SC-RNTI is FFFC. On the other hand, a new RNTI is introduced, that is, a single cell notification RNTI (Single Cell Notification RNTI, SC-N-RNTI) to identify the PDCCH (such as the notification PDCCH) used to indicate the change notification of the SC-MCCH, optionally, the SC The fixed value of -N-RNTI is FFFB; further, one of the 8 bits (bits) of DCI 1C can be used to indicate the change notification. In LTE, the configuration information of the SC-PTM is based on the SC-MCCH configured by the SIB20, and then the SC-MCCH configures the SC-MTCH, and the SC-MTCH is used to transmit service data.

Specifically, the SC-MCCH only transmits one message (ie, SCPTMConfiguration), which is used to configure the configuration information of the SC-PTM. The configuration information of SC-PTM includes: Temporary Mobile Group Identity (TMGI), session identifier (session id), group RNTI (Group RNTI, G-RNTI), discontinuous reception (Discontinuous Reception, DRX) configuration information And the SC-PTM service information of neighboring cells, etc. It should be noted that the SC-PTM in R13 does not support the Robust Header Compression (ROHC) function.

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

When [(SFN*10)+subframe number]modulo(SC-MTCH-SchedulingCycle)=SC-MTCH-SchedulingOffset is satisfied, the timer onDurationTimerSCPTM is started;

When receiving the downlink PDCCH scheduling, start the timer drx-InactivityTimerSCPTM;

The downstream SC-PTM service is received only when the timer onDurationTimerSCPTM or drx-InactivityTimerSCPTM is running.

SC-PTM business continuity adopts the concept of MBMS business continuity based on SIB15, namely "SIB15+MBMSInterestIndication" mode. The service continuity of terminal equipment in idle state is based on the concept of frequency priority.

According to the above description, the configuration of SC-PTM is to configure SC-MCCH based on SIB20, and then configure SC-MTCH based on SC-MCCH. A cell has one and only one SC-MCCH, that is, the terminal equipment needs to re-acquire the SC-MCCH after cell reselection, which will cause service interruption.

In the NR system, many scenarios need to support the service requirements of multicast and broadcast, such as the Internet of Vehicles, the Industrial Internet, etc. So it is necessary to introduce MBMS in NR.

It should be noted that the MBMS services in the above solution include but are not limited to multicast services, multicast services, and MBS services. The embodiments of the present application take the MBS service as an example for description, and the description of "MBS service" may also be replaced with "multicast service" or "multicast service" or "broadcast service" or "MBMS service".

NR supports broadcast MBS services, configures MCCH through BCCH, and configures MTCH through MCCT. Among them, the MCCH is used to transmit the configuration information of the MBS service, and the MTCH is used to transmit the MBS service data. A cell has only one MCCH, and the MCCH carries signaling (hereinafter referred to as MCCH signaling), and configuration information of multiple MBS services is configured through the MCCH signaling.

The terminal equipment in the RRC idle state, the RRC inactive state, and the RRC connected state can all receive the broadcast MBS service. In order to ensure the continuity of the broadcasted MBS service received by the terminal equipment in the RRC connection state, the terminal equipment needs to indicate the identification information of the MBS service that the network side terminal equipment is interested in or is receiving when the terminal equipment is in the RRC connection state, so that the network side can make a handover decision. The cell that supports the MBS service is preferentially considered as the target cell for handover.

In NR, different from LTE, after the terminal device enters the RRC connection state, the network side configures multiple dedicated BWPs (such as a maximum of 4 dedicated BWPs) for the terminal device, and the terminal device can switch between these dedicated BWPs in the RRC connection state , for example, switching between BWPs is implemented based on mechanisms such as DCI or timers. The terminal device receives the broadcasted MBS service in the RRC idle state or the RRC inactive state. After entering the RRC connected state from the RRC idle state or the RRC inactive state, the network side does not know the MBS service previously received by the terminal device. Configuring a dedicated BWP for a terminal device will cause the terminal device to fail to receive MBS services normally. To this end, the following technical solutions of the embodiments of the present application are proposed.

In the technical solutions of the embodiments of the present application, the terminal equipment reports the identification information of the MBS services that it is interested in or is receiving in the RRC idle state or the RRC inactive state, so as to facilitate the network side to configure an appropriate dedicated BWP and prevent the terminal equipment from performing unnecessary operations. BWP handover ensures that the MBS service is normally received.

FIG. 2 is a schematic flowchart 1 of a method for indicating an MBS service provided by an embodiment of the present application. As shown in FIG. 2 , the method for indicating an MBS service includes the following steps:

Step 201: The terminal device sends the identification information of the MBS service to the network device, and the network device receives the identification information of the MBS service sent by the terminal device, where the MBS service is the MBS service expected by the terminal device or the MBS service being received; wherein, The identification information of the MBS service is used for the configuration of the dedicated downlink BWP of the terminal device and/or the identification information of the MBS service is used to determine the target cell to be handed over by the terminal device.

In this embodiment of the present application, the identification information of the MBS service is used by the network device to configure a dedicated downlink BWP for the terminal device and/or the identification information of the MBS service is used by the network device to select for the terminal device The target cell to be handed over.

In the embodiment of the present application, the terminal device can receive the broadcast MBS service in the RRC idle state, the RRC inactive state, or the RRC connected state. In the case that the terminal device receives the broadcasted MBS service in the RRC idle state or the RRC inactive state, if the terminal device enters the RRC connected state from the RRC idle state or the RRC inactive state, the terminal device can enter the RRC connected state or enter the RRC connected state. In the process of the RRC connection state, the identification information of the MBS service is sent to the network device. The MBS service here refers to the MBS service expected by the terminal device in the previous RRC idle state or the RRC inactive state or the MBS service being received, so that the network The device may configure a dedicated downlink BWP for the terminal device and/or select a target cell to be handed over for the terminal device according to the identification information of the MBS service indicated by the terminal device.

In this embodiment of the present application, the identification information of the MBS service may be, but is not limited to, TMGI, G-RNTI, and the like.

In this embodiment of the present application, the description about "desired MBS service" may also be replaced with "interested MBS service".

The technical solutions of the embodiments of the present application will be described in detail below in combination with different situations.

(1) Situation 1

After entering the RRC connection state, the terminal device sends the identification information of the MBS service to the network device through an RRC message.

Here, the RRC message may be an RRC message that has not undergone security processing, or an RRC message that has undergone security processing. It should be noted that the RRC message transmitted before the AS layer security activation belongs to the RRC message without security processing, and the RRC message transmitted after the AS layer security activation belongs to the security processed RRC message. Among them, the security activation of the AS layer takes the security activation complete (Securtiy mode complete) message as the judgment standard.

In one scenario, the MBS service is the expected MBS service or the MBS service that the terminal device is receiving when the terminal device is in the RRC idle state; before the terminal device enters the RRC connected state, the terminal device sends a message to the network device. Sending an RRC setup request message, the network device receives the RRC setup request message sent by the terminal device; the network device sends an RRC setup message to the terminal device, and the terminal device receives the RRC setup message sent by the network device .

In another application scenario, the MBS service is the expected MBS service or the MBS service being received by the terminal device in the RRC inactive state; before the terminal device enters the RRC connected state, the terminal device sends the The network device sends an RRC recovery request message, and the network device receives the RRC recovery request message sent by the terminal device; wherein the RRC recovery process falls back to the RRC setup process; the network device sends the RRC setup message to the terminal device , the terminal device receives the RRC establishment message sent by the network device.

In an optional manner, the terminal device sends the identification information of the MBS service to the network device through a first RRC message, and the network device receives the identification information of the MBS service sent by the terminal device through the first RRC message, The first RRC message is an RRC message that has not undergone security processing. In an example, the first RRC message is an RRC setup complete message; or, the first RRC message is an MBS Interest Indication (MBSInterestingIndication) message.

In another optional manner, the terminal device sends the identification information of the MBS service to the network device through a second RRC message, and the network device receives the identification information of the MBS service sent by the terminal device through the second RRC message , the second RRC message is a RRC message that has undergone security processing. In an example, the second RRC message is a security activation complete message; alternatively, the second RRC message is a UEAssistanceInformation message; alternatively, the second RRC message is an MBS indication message, such as an MBS interest indication ( MBSInterestingIndication) message.

In the embodiment of the present application, after the terminal device enters the RRC connection state, the network device sends an RRC reconfiguration message to the terminal device, and the terminal device receives the RRC reconfiguration message sent by the network device, and the RRC reconfiguration message The message carries first configuration information, where the first configuration information is used to determine the configuration information of the dedicated downlink BWP.

(2) Case 2

In one scenario, the MBS service is the expected MBS service or the MBS service being received by the terminal device in the RRC inactive state; before the terminal device enters the RRC connected state, the terminal device sends the network to the network. The device sends an RRC recovery request message, and the network device receives the RRC recovery request message sent by the terminal device; the network device sends an RRC recovery message to the terminal device, and the terminal device receives the RRC recovery message sent by the network device message, and then, the terminal device enters the RRC connection state. After the terminal device enters the RRC connection state, the terminal device sends the identification information of the MBS service to the network device through the RRC recovery complete message, and the network device receives the identification information of the MBS service sent by the terminal device through the RRC recovery complete message. information.

In the above solution, optionally, the RRC recovery request message is used to determine first indication information, where the first indication information is used to indicate whether the terminal device is receiving the broadcasted MBS service. Here, the first indication information may be implemented in the following ways:

Mode I) The RRC recovery request message carries the first indication information; wherein, the value of the idle bit in the RRC recovery request message is used to represent the first indication information.

Manner II) The RRC recovery request message carries the first indication information; wherein, the value of the recovery cause in the RRC recovery request message is used to represent the first indication information.

Mode III) The value of the logical channel identifier of the CCCH corresponding to the RRC recovery request message is used to represent the first indication information.

Here, the logical channel identifier of the CCCH is carried in the header corresponding to the RRC recovery request message in the MAC TB.

In the above solution, optionally, the RRC recovery message carries second configuration information, and the second configuration information is used to determine the BWP configuration information of the PCell, wherein the bandwidth of the first activated downlink BWP of the PCell includes all the The bandwidth of the initial downlink BWP of the PCell and/or the bandwidth of the MBS BWP of the PCell. Here, the bandwidth of the MBS BWP of the PCell is determined by the network device according to the bandwidth of the MBS BWP corresponding to the MBS service identifier indicated by the terminal device. Specifically, the bandwidth of the MBS BWP of the PCell is the bandwidth of the MBS BWP corresponding to the MBS service identifier indicated by the terminal device.

In this embodiment of the present application, after the terminal device sends an RRC recovery complete message to the network device, the network device sends an RRC reconfiguration message to the terminal device, and the terminal device receives the RRC reconfiguration message sent by the network device, so the The RRC reconfiguration message carries first configuration information, where the first configuration information is used to determine the configuration information of the dedicated downlink BWP.

(3) Situation 3

In one scenario, the MBS service is the expected MBS service or the MBS service being received by the terminal device in the RRC inactive state; before the terminal device enters the RRC connected state, the terminal device sends the network to the network. The device sends an RRC recovery request message, and the network device receives the RRC recovery request message sent by the terminal device; the network device sends an RRC recovery message to the terminal device, and the terminal device receives the RRC recovery message sent by the network device message, and then, the terminal device enters the RRC connection state. After the terminal device enters the RRC connection state, the terminal device sends the identification information of the MBS service to the network device through an RRC recovery complete message.

In the above solution, optionally, the terminal device may send first indication information to the network device, where the first indication information is used to indicate whether the terminal device is receiving the broadcast MBS service.

In an optional manner, the RRC recovery request message is used to determine first indication information, where the first indication information is used to indicate whether the terminal device is receiving the broadcasted MBS service. Here, the first indication information may be implemented in the following ways:

In another optional manner, before the terminal device sends the RRC recovery request message to the network device, the method further includes: the terminal device sends MSG1 or MSGA to the network device, and the network device receives the message. MSG1 or MSGA sent by the terminal device, the MSG1 or MSGA is used to determine the first indication information, and the first indication information is used to indicate at least one of the following: whether the terminal device is receiving the broadcast MBS service; The identification information of the MBS service that the terminal device is receiving.

In the above solution, the preamble and/or RO resource corresponding to the MSG1 or MSGA have an associated relationship with whether the terminal device is receiving the broadcast MBS service; and/or, the preamble and/or the corresponding preamble of the MSG1 or MSGA The RO resource is associated with the identification information of the MBS service received by the terminal device. Here, optionally, the association relationship is configured through a system broadcast message. Based on this, the terminal device determines the preamble and/or RO resource corresponding to the MSG1 or MSGA according to whether the broadcasted MBS service is being received and/or the identification information of the received MBS service.

(4) Case 4

Before the terminal device enters the RRC connection state, it sends the identification information of the MBS service to the network device through MSG1 or MSGA; the network device receives the identification information of the MBS service sent by the terminal device through MSG1 or MSGA.

Specifically, the MSG1 or MSGA is used to determine first indication information, where the first indication information is used to indicate at least one of the following:

Whether the terminal device is receiving the broadcast MBS service;

Identification information of the MBS service being received by the terminal device.

In the above solution, for MSGA, including MSG1 and Payload (Payload is carried in PUSCH), the first indication information can be implicitly indicated by the preamble and/or RO resource of MSG1, or the first indication information can also be Carry explicit instructions in the payload.

In one scenario, the MBS service is the expected MBS service or the MBS service being received by the terminal device in the RRC inactive state; before the terminal device enters the RRC connected state, the terminal device passes MSG1 or MSGA Send the identification information of the MBS service to the network device, and the terminal device receives the MSG2 sent by the network device; then, the terminal device sends an RRC recovery request message to the network device, and the network device receives the RRC sent by the terminal device. A recovery request message; the network device sends an RRC recovery message to the terminal device, and the terminal device receives the RRC recovery message sent by the network device, the RRC recovery message carries first configuration information, and the first configuration information It is used to determine the configuration information of the dedicated downlink BWP; then, the terminal device enters the RRC connection state. After the terminal device enters the RRC connection state, the terminal device sends an RRC recovery complete message to the network device.

For the solutions described in the above cases 1 to 4, the network device can obtain the identification information of the MBS service sent by the terminal device, and the network device can configure the dedicated downlink BWP for the terminal device and/or select for the terminal device according to the identification information of the MBS service. The target cell to be handed over.

Wherein, for handover, the identification information of the MBS service is used by the network device to select a cell supporting the MBS service indicated by the identification information of the MBS service as the target cell of the handover. For the identification information of the MBS service, a cell supporting the MBS service indicated by the identification information of the MBS service is selected as the target cell for handover. Further, optionally, before the network device selects the cell supporting the MBS service indicated by the identification information of the MBS service as the target cell for handover, the cell and its neighbors interact with each other about the MBS service supported by each cell. Or the identification information of the MBS service being transmitted.

Wherein, for the dedicated downlink BWP, the configuration information of the dedicated downlink BWP is embodied by the first configuration information in the above solution. The first configuration information in the solutions described in the above cases 1 to 4 is described below.

A) In an optional manner, the first configuration information is used to determine the configuration information of the dedicated downlink BWP of the PCell, and the bandwidth of the dedicated downlink BWP of the PCell includes the bandwidth of the initial downlink BWP of the PCell and/or all The bandwidth of PCell's MBSBWP.

B) In another optional manner, the first configuration information is used to determine the configuration information of the dedicated downlink BWP of the SCell, and the bandwidth of the dedicated downlink BWP of the SCell includes the bandwidth of the initial downlink BWP of the SCell and/or The bandwidth of the MBSBWP of the SCell.

Optionally, the network device sends second indication information to the terminal device, and the terminal device receives the second indication information sent by the network device, where the second indication information is used to indicate that the terminal device is The broadcasted MBS service is received on the SCell.

In an example, if the terminal device receives the broadcasted MBS service on the SCell, the SCell is in an active state or in an active state with non-dormancy behavior.

In an example, if the terminal device receives the broadcasted MBS service on the SCell, and the SCell is in a deactivated state or in an activated state with dormancy behavior, the terminal device has the following behavior: The PDCCH scrambled by G-RNTI is monitored on the SCell and the PDSCH corresponding to the PDCCH is received; the PDCCH scrambled by the C-RNTI and the PDSCH corresponding to the PDCCH are not monitored on the SCell. Further, the bandwidth of the first activated downlink BWP of the SCell includes the bandwidth of the initial downlink BWP of the SCell and/or the bandwidth of the MBS BWP of the SCell.

It should be noted that the "MBS service identification information" described in the above solution of this application may refer to the identification information of one MBS service or may refer to the identification information of multiple MBS services (ie, the MBS identification information list).

The technical solutions of the embodiments of the present application are described below with reference to specific application examples. It should be noted that, in the following application examples, the terminal device is a UE as an example, and the network device is a gNB as an example for description.

Application example one

Application example 1 corresponds to situation 1 in the above solution. Referring to FIG. 3 , FIG. 3 is a schematic flowchart 2 of an MBS service indication method provided by an embodiment of the present application. As shown in FIG. 3 , the MBS service indication method includes the following step:

Step 301: The UE is in the RRC idle state and is receiving the broadcasted MBS service.

Here, the identification information of the broadcasted MBS service is TMGI-1.

Step 302: The UE sends an RRC setup request (RRCSetupRequest) message to the gNB.

Here, the UE sends an RRC setup request message to the gNB through SRB0.

Step 303: The gNB sends an RRC setup (RRCSetup) message to the UE.

Here, the gNB sends an RRC setup message to the UE through SRB1.

Step 304: The UE enters the RRC connected state.

Step 305: The UE reports to the gNB the identification information of the MBS service that the UE is interested in or is receiving.

Here, the identification information of the MBS service that the UE is interested in or is receiving is, for example, TMGI-1.

It should be noted that the identification information of the MBS service that the UE is interested in or is receiving is not limited to a TMGI, but may also be a TMGI list.

In the embodiment of this application, the UE reports the identification information of the MBS service that the UE is interested in or is receiving to the gNB, in the following ways:

Manner 1-1: The UE reports, through an RRC setup complete (RRCSetupComplete) message, the identification information of the MBS service that the UE is interested in or is receiving. Here, the RRC setup complete message (ie MSG5) is transmitted through SRB1.

Manner 1-2: The UE reports, through a new RRC message, the identification information of the MBS service that the UE is interested in or is receiving. Here, the new RRC message is, for example, an MBS Interest Indication (MBSInterestingIndication) message.

It should be noted that the above methods 1-1 and 1-2 do not consider security, that is, the RRC message carrying the identification information of the MBS service has not been processed securely, so the above method 1 can be used when there is no security problem. -1 or mode 1-2 to report the identification information of the MBS service.

Manner 2-1: The UE reports, through a security activation complete (SecurityModeComplete) message, the identification information of the MBS service that the UE is interested in or is receiving.

Manner 2-2: The UE reports the identification information of the MBS service that the UE is interested in or is receiving through a UE Assistance Information (UEAssistanceInformation) message.

Manner 2-3: The UE reports, through a new RRC message, the identification information of the MBS service that the UE is interested in or is receiving. Here, the new RRC message is, for example, an MBS Interest Indication (MBSInterestingIndication) message.

It should be noted that the above methods 2-1, 2-2 and 2-3 have taken security considerations, that is, the RRC message carrying the identification information of the MBS service is securely processed (that is, it is reported after the AS layer security is activated). RRC message), therefore, the above-mentioned mode 2-1 or mode 2-2 or mode 2-3 can be used to report the identification information of the MBS service if there is no security problem or there is a security problem.

Step 306: The gNB sends an RRC reconfiguration (RRCReconfiguration) message to the UE, which carries the configuration information of the dedicated downlink BWP.

Here, after obtaining the identification information about the MBS service that the UE is interested in or is receiving, the gNB configures the configuration information of the dedicated downlink BWP through the RRC reconfiguration message, specifically:

When the gNB configures the dedicated DL BWP of the PCell for the UE, the bandwidth of the dedicated DL BWP includes the bandwidth of the initial DL BWP of the PCell and/or the bandwidth of the MBS BWP of the PCell. or,

The gNB may instruct the UE to receive the MBS service on a certain SCell, and configure the bandwidth of the dedicated DL BWP of the SCell to include the bandwidth of the initial DL BWP of the SCell and/or the bandwidth of the MBS BWP of the SCell.

Further, if the UE receives the broadcast MBS service on the SCell, the SCell cannot be deactivated, and the dormant BWP cannot be configured (that is, the SCell cannot be in an active state with dormant behavior). Alternatively, if the UE receives the broadcast MBS service on the SCell, if the SCell is deactivated, or the dormant BWP is configured and the dormant BWP is activated, the UE is only allowed to continue to monitor the G-RNTI scrambled PDCCH and the corresponding PDSCH reception, but not C-RNTI scrambled PDCCH and corresponding PDSCH reception. And the bandwidth of the first activated DL BWP of the SCell must include the bandwidth of the initial DL BWP of the SCell and/or the bandwidth of the MBS BWP of the SCell.

Step 307: The UE sends an RRC reconfiguration complete (RRCReconfigurationComplete) message to the gNB.

Here, the UE sends an RRC reconfiguration complete message to the gNB through SRB1.

Application example two

Application example 2 corresponds to situation 2 in the above solution. Referring to FIG. 4 , FIG. 4 is a schematic flow chart 3 of an MBS service indication method provided by an embodiment of the present application. As shown in FIG. 4 , the MBS service indication method includes the following step:

Step 401: The UE is in the RRC inactive state, and the UE is receiving the broadcast MBS service.

Here, the identifier of the broadcasted MBS service is TMGI-1.

Step 402: The UE sends an RRC resume request (RRCResumeRequest) message to the target gNB, and the 1-bit indication information is used to indicate whether the UE is receiving the MBS service.

Here, the UE sends an RRC recovery request message to the target gNB through SRB0.

Here, the RRC recovery request message is used to determine 1-bit indication information, and the 1-bit indication information is used to indicate whether the UE is receiving the MBS service. For example, a value of 1 for the 1-bit indication information means that the UE is receiving an MBS service, and a value of 0 for the 1-bit indication information means that the UE is not receiving an MBS service. There are several ways to implement the 1-bit indication information:

1) The UE carries 1-bit indication information in the RRC recovery request message, for example, the 1-bit indication information is indicated by a spare bit (spare bit) in the RRC recovery request message.

2) The UE indicates that the UE is receiving the broadcasted MBS service through the LCID of the CCCH corresponding to the RRC recovery request message. For example, a new LCID is defined for the CCCH to indicate that the UE is receiving the broadcasted MBS service when the UE initiates the RRC connection recovery. At this time, the LCID indicated in the corresponding header of the RLC PDU of the RRC recovery request message in the MAC TB is the above-mentioned newly defined LCID.

3) The UE carries 1-bit indication information in the RRC resume request message, for example, the value of the resume cause (resume case) in the RRC resume request message is used to indicate that the UE is receiving the broadcast MBS service.

Step 403: The target gNB sends an RRC recovery message to the UE, which carries the configuration information of the BWP of the PCell.

Here, the target gNB sends an RRC recovery message to the UE through SRB1.

Here, after the target gNB obtains the 1-bit indication information about the MBS service that the UE is receiving from the RRC recovery request message sent by the UE, it configures the BWP of the PCell for the UE through the RRC recovery (RRCResume) message. The bandwidth of an activated DL BWP includes the bandwidth of the PCell's initial DL BWP and/or the bandwidth of the PCell's MBS BWP.

It should be noted that the network side will not trigger the UE to perform a BWP handover operation, at least for PCell, before receiving the 1-bit indication information of the MBS service that the UE is interested in or is receiving.

Step 404: The UE enters the RRC connected state.

Step 405: The UE reports the identification information of the MBS service that the UE is interested in or is receiving through an RRC recovery complete (RRCResumeComplete) message.

Here, the UE sends an RRC recovery complete message through SRB1.

Step 406: The gNB sends an RRC reconfiguration (RRCReconfiguration) message to the UE, which carries the configuration information of the dedicated downlink BWP.

Here, the gNB sends an RRC reconfiguration message to the UE through SRB1.

Step 407: The UE sends an RRC reconfiguration complete (RRCReconfigurationComplete) message to the gNB.

Application example three

Application example 3 corresponds to situation 3 in the above solution. Referring to FIG. 5 , FIG. 5 is a schematic flowchart of the MBS service indication method provided by the embodiment of the present application. As shown in FIG. 5 , the MBS service indication method includes the following step:

Step 501: The UE is in the RRC inactive state, and the UE is receiving the broadcast MBS service.

Here, the identifier of the broadcasted MBS service is TMGI-1.

Step 502: The UE receives the system broadcast message sent by the target gNB, and configures the first association relationship and/or the second association relationship.

Here, the "association relationship" may also be referred to as a "mapping relationship".

Here, the first association relationship is the association relationship between preamble and/or RO (rach occasion) resources and whether the MBS service is in progress. The second association relationship is the association relationship between the preamble and/or RO (rach occasion) resource and the MBS service identifier (that is, the identification information of the MBS service).

It should be noted that the above steps 501 and 502 are not in order.

Step 503: The UE sends MSG1 to the target gNB.

Here, the UE selects the corresponding preamble and/or RO resource to send MSG1 according to whether it is currently receiving the MBS service and/or the identification information of the received MBS service.

Step 504: The target gNB determines, according to the preamble and/or RO resource of MSG1, whether the UE is receiving the MBS service and/or the identification information of the MBS service being received.

Step 505: The target gNB sends MSG2 to the UE.

Step 506: The UE sends an RRC resume request (RRCResumeRequest) message to the target gNB.

Step 507: The target gNB sends an RRC recovery message to the UE, which carries the configuration information of the BWP of the PCell.

Here, the target gNB sends an RRC recovery message to the UE through SRB1.

Step 508: The UE enters the RRC connected state.

Step 509: The UE reports the identification information of the MBS service that the UE is interested in or is receiving through an RRC recovery complete (RRCResumeComplete) message.

Here, the UE sends an RRC recovery complete message through SRB1.

Step 510: The gNB sends an RRC reconfiguration (RRCReconfiguration) message to the UE, which carries the configuration information of the dedicated downlink BWP.

Here, the gNB sends an RRC reconfiguration message to the UE through SRB1.

Step 511: The UE sends an RRC reconfiguration complete (RRCReconfigurationComplete) message to the gNB.

Application example four

Application example 4 corresponds to situation 4 in the above solution. Referring to FIG. 6 , FIG. 6 is a schematic flowchart of the MBS service indication method provided by the embodiment of the present application. As shown in FIG. 6 , the MBS service indication method includes the following step:

Step 601: The UE is in the RRC inactive state, and the UE is receiving the broadcasted MBS service.

Here, the identifier of the broadcasted MBS service is TMGI-1.

Step 602: The UE receives the system broadcast message sent by the target gNB, and configures the first association relationship and/or the second association relationship.

It should be noted that the above steps 501 and 502 are not in order.

Step 603: The UE sends MSG1 to the target gNB.

Step 604: The target gNB determines, according to the preamble and/or RO resource of MSG1, whether the UE is receiving the MBS service and/or the identification information of the MBS service being received.

Step 605: The target gNB sends MSG2 to the UE.

Step 606: The UE sends an RRC resume request (RRCResumeRequest) message to the target gNB.

Step 607: The target gNB sends an RRC recovery message to the UE, which carries the configuration information of the dedicated downlink BWP.

Here, the target gNB sends an RRC recovery message to the UE through SRB1.

Here, after obtaining the identification information about the MBS service that the UE is interested in or is receiving, the gNB configures the configuration information of the dedicated downlink BWP through the RRC recovery message, specifically:

Further, if the UE receives the broadcast MBS service on the SCell, the SCell cannot be deactivated, and the dormant BWP cannot be configured (that is, the SCell cannot be in an active state with dormant behavior). Alternatively, if the UE receives the broadcast MBS service on the SCell, if the SCell is deactivated, or the dormant BWP is configured and the dormant BWP is activated, the UE is only allowed to continue to monitor the G-RNTI scrambled PDCCH and the corresponding PDCCH in the cell. PDSCH reception, but not C-RNTI scrambled PDCCH and corresponding PDSCH reception. And the bandwidth of the first activated DL BWP of the SCell must include the bandwidth of the initial DL BWP of the SCell and/or the bandwidth of the MBS BWP of the SCell.

Step 608: The UE enters the RRC connected state.

Step 609: The UE sends an RRC recovery complete (RRCResumeComplete) message.

Here, the UE sends an RRC recovery complete message through SRB1.

Step 610: The gNB sends an RRC reconfiguration (RRCReconfiguration) message to the UE,

Step 611: The UE sends an RRC reconfiguration complete (RRCReconfigurationComplete) message to the gNB.

FIG. 7 is a schematic diagram 1 of the structure and composition of an indication apparatus for an MBS service provided by an embodiment of the present application, which is applied to a terminal device. As shown in FIG. 7 , the indication apparatus for an MBS service includes:

A communication unit 701, configured to send identification information of an MBS service to a network device, where the MBS service is an MBS service expected by the terminal device or an MBS service being received;

In an optional manner, the communication unit 701 is configured to send the identification information of the MBS service to the network device through a first RRC message, where the first RRC message is an RRC message that has not undergone security processing.

In an optional manner, the first RRC message is an RRC setup complete message; or,

The first RRC message is an MBS indication message.

In an optional manner, the communication unit 701 is configured to send the identification information of the MBS service to the network device through a second RRC message, where the second RRC message is a securely processed RRC message.

In an optional manner, the second RRC message is a security activation complete message; or,

The second RRC message is a UEAssistanceInformation message; or,

The second RRC message is an MBS indication message.

In an optional manner, the MBS service is a desired MBS service or an MBS service being received by the terminal device in an RRC idle state;

The communication unit 701 is further configured to send an RRC establishment request message to the network device; and receive an RRC establishment message sent by the network device.

In an optional manner, the MBS service is a desired MBS service or an MBS service that is being received by the terminal device in an RRC inactive state;

The communication unit 701 is further configured to send an RRC recovery request message to the network device; wherein, the RRC recovery process falls back to the RRC establishment process; and receives the RRC establishment message sent by the network device.

In an optional manner, the communication unit 701 is configured to send the identification information of the MBS service to the network device through an RRC recovery complete message.

In an optional manner, the communication unit 701 is further configured to send an RRC recovery request message to the network device; and receive an RRC recovery message sent by the network device.

In an optional manner, the RRC recovery request message is used to determine first indication information, where the first indication information is used to indicate whether the terminal device is receiving the broadcasted MBS service.

In an optional manner, the RRC recovery request message carries the first indication information; wherein,

The value of the idle bit in the RRC recovery request message is used to represent the first indication information; or,

The value of the recovery cause in the RRC recovery request message is used to represent the first indication information.

In an optional manner, the value of the logical channel identifier of the CCCH corresponding to the RRC recovery request message is used to represent the first indication information.

In an optional manner, the logical channel identifier of the CCCH is carried in the header corresponding to the RRC recovery request message in the MAC TB.

In an optional manner, the communication unit 701 is further configured to send MSG1 or MSGA to the network device, where the MSG1 or MSGA is used to determine first indication information, and the first indication information is used to indicate at least the following: one:

Whether the terminal device is receiving the broadcast MBS service;

In an optional manner, the RRC recovery message carries second configuration information, and the second configuration information is used to determine the BWP configuration information of the PCell, wherein the bandwidth of the first activated downlink BWP of the PCell includes the The bandwidth of the initial downlink BWP of the PCell and/or the bandwidth of the MBS BWP of the PCell.

In an optional manner, the bandwidth of the MBS BWP of the PCell is determined by the network device according to the bandwidth of the MBS BWP corresponding to the MBS service identifier indicated by the terminal device.

In an optional manner, the communication unit 701 is further configured to receive an RRC reconfiguration message sent by the network device, where the RRC reconfiguration message carries first configuration information, and the first configuration information is used to determine the The configuration information of the dedicated downlink BWP described above.

In an optional manner, the communication unit 701 is configured to send the identification information of the MBS service to the network device through MSG1 or MSGA.

In an optional manner, the MSG1 or MSGA is used to determine first indication information, where the first indication information is used to indicate at least one of the following:

Whether the terminal device is receiving the broadcast MBS service;

In an optional manner, the communication unit 701 is further configured to send an RRC recovery request message to the network device; and receive an RRC recovery message sent by the network device, where the RRC recovery message carries the first configuration information, and the The first configuration information is used to determine the configuration information of the dedicated downlink BWP.

In an optional manner, the preamble and/or RO resource corresponding to the MSG1 or MSGA has an associated relationship with whether the terminal device is receiving the broadcast MBS service; and/or,

The preamble and/or RO resource corresponding to the MSG1 or MSGA has an associated relationship with the identification information of the MBS service received by the terminal device.

In an optional manner, the association relationship is configured through a system broadcast message.

In an optional manner, the device further includes:

The determining unit 702 is configured to determine the preamble and/or RO resource corresponding to the MSG1 or MSGA according to whether the broadcasted MBS service is being received and/or the identification information of the received MBS service.

In an optional manner, the first configuration information is used to determine the configuration information of the dedicated downlink BWP of the PCell, and the bandwidth of the dedicated downlink BWP of the PCell includes the bandwidth of the initial downlink BWP of the PCell and/or the PCell The bandwidth of the MBS BWP.

In an optional manner, the first configuration information is used to determine the configuration information of the dedicated downlink BWP of the SCell, and the bandwidth of the dedicated downlink BWP of the SCell includes the bandwidth of the initial downlink BWP of the SCell and/or the bandwidth of the SCell The bandwidth of the MBS BWP.

In an optional manner, the communication unit 701 is further configured to receive second indication information sent by the network device, where the second indication information is used to instruct the terminal device to receive broadcast MBS on the SCell business.

In an optional manner, if the terminal device receives the broadcasted MBS service on the SCell, the SCell is in an active state or an active state with non-dormancy behavior.

In an optional manner, if the terminal device receives the broadcasted MBS service on the SCell, and the SCell is in a deactivated state or in an activated state with dormancy behavior, the terminal device has the following behavior:

Monitor the PDCCH scrambled by the G-RNTI on the SCell and receive the PDSCH corresponding to the PDCCH;

The SCell does not monitor the PDCCH scrambled by the C-RNTI and does not receive the PDSCH corresponding to the PDCCH.

In an optional manner, the bandwidth of the first activated downlink BWP of the SCell includes the bandwidth of the initial downlink BWP of the SCell and/or the bandwidth of the MBS BWP of the SCell.

In an optional manner, the identification information of the MBS service is used by the network device to select the target cell to be handed over for the terminal device, including:

The identification information of the MBS service is used by the network device to select a cell supporting the MBS service indicated by the identification information of the MBS service as a target cell for handover.

In an optional manner, before the network device selects a cell supporting the MBS service indicated by the identification information of the MBS service as the target cell for handover, the cell and its neighbors interact with each other about the MBS supported by each cell. Identification information of the service or the MBS service being transmitted.

It should be understood by those skilled in the art that the related description of the device for indicating the MBS service in the embodiment of the present application can be understood with reference to the related description of the indicating method for the MBS service in the embodiment of the present application.

FIG. 8 is a schematic diagram 2 of the structure and composition of a device for indicating an MBS service provided by an embodiment of the present application, which is applied to a network device. As shown in FIG. 8 , the device for indicating an MBS service includes:

A communication unit 801, configured to receive identification information of an MBS service sent by a terminal device, where the MBS service is an MBS service expected by the terminal device or an MBS service being received;

In an optional manner, the communication unit 801 is configured to receive the identification information of the MBS service sent by the terminal device through a first RRC message, where the first RRC message is an RRC message that has not undergone security processing.

The first RRC message is an MBS indication message.

In an optional manner, the communication unit 801 is configured to receive the identification information of the MBS service sent by the terminal device through a second RRC message, where the second RRC message is an RRC message that has undergone security processing.

The second RRC message is a UEAssistanceInformation message; or,

The second RRC message is an MBS indication message.

The communication unit 801 is further configured to receive an RRC establishment request message sent by the terminal device; and send an RRC establishment message to the terminal device.

In an optional manner, the MBS service is the expected MBS service or the MBS service being received by the terminal device in the RRC inactive state; the communication unit 801 is further configured to receive the data sent by the terminal device. RRC recovery request message; wherein, the RRC recovery process falls back to the RRC setup process; and the RRC setup message is sent to the terminal device.

In an optional manner, the communication unit 801 is configured to receive the identification information of the MBS service sent by the terminal device through the RRC recovery complete message.

In an optional manner, the communication unit 801 is further configured to receive an RRC recovery request message sent by the terminal device; and send an RRC recovery message to the terminal device.

In an optional manner, the communication unit 801 is further configured to receive MSG1 or MSGA sent by the terminal device, where the MSG1 or MSGA is used to determine first indication information, and the first indication information is used to indicate At least one of the following:

Whether the terminal device is receiving the broadcast MBS service;

In an optional manner, the communication unit 801 is further configured to send an RRC reconfiguration message to the terminal device, where the RRC reconfiguration message carries first configuration information, and the first configuration information is used to determine the Configuration information of the dedicated downlink BWP.

In an optional manner, the communication unit 801 is configured to receive the identification information of the MBS service sent by the terminal device through MSG1 or MSGA.

Whether the terminal device is receiving the broadcast MBS service;

In an optional manner, the communication unit 801 is further configured to receive an RRC recovery request message sent by the terminal device; and send an RRC recovery message to the terminal device, where the RRC recovery message carries the first configuration information, and the The first configuration information is used to determine the configuration information of the dedicated downlink BWP.

In an optional manner, the communication unit 801 is further configured to send second indication information to the terminal device, where the second indication information is used to instruct the terminal device to receive the broadcasted MBS service on the SCell .

In an optional manner, if the terminal device receives the broadcast MBS service on the SCell, and the SCell is in a deactivated state or is in an activated state with dormancy behavior, the terminal device has the following behavior:

In an optional manner, the device further includes:

The selecting unit 802 is configured to select, according to the identification information of the MBS service, a cell supporting the MBS service indicated by the identification information of the MBS service as a target cell for handover.

FIG. 9 is a schematic structural diagram of a communication device 900 provided by an embodiment of the present application. The communication device may be a terminal device or a network device. The communication device 900 shown in FIG. 9 includes a processor 910, and the processor 910 can call and run a computer program from a memory to implement the methods in the embodiments of the present application.

Optionally, as shown in FIG. 9 , the communication device 900 may further include a memory 920 . The processor 910 may call and run a computer program from the memory 920 to implement the methods in the embodiments of the present application.

The memory 920 may be a separate device independent of the processor 910 , or may be integrated in the processor 910 .

Optionally, as shown in FIG. 9 , the communication device 900 may further include a transceiver 930, and the processor 910 may control the transceiver 930 to communicate with other devices, specifically, may send information or data to other devices, or receive other Information or data sent by a device.

Among them, the transceiver 930 may include a transmitter and a receiver. The transceiver 930 may further include antennas, and the number of the antennas may be one or more.

Optionally, the communication device 900 may specifically be a network device in this embodiment of the present application, and the communication device 900 may implement the corresponding processes implemented by the network device in each method in the embodiment of the present application. For brevity, details are not repeated here. .

Optionally, the communication device 900 may specifically be the mobile terminal/terminal device in the embodiments of the present application, and the communication device 900 may implement the corresponding processes implemented by the mobile terminal/terminal device in each method in the embodiments of the present application. , and will not be repeated here.

FIG. 10 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 1000 shown in FIG. 10 includes a processor 1010, and the processor 1010 can call and run a computer program from a memory, so as to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 10 , the chip 1000 may further include a memory 1020 . The processor 1010 may call and run a computer program from the memory 1020, so as to implement the methods in the embodiments of the present application.

The memory 1020 may be a separate device independent of the processor 1010, or may be integrated in the processor 1010.

Optionally, the chip 1000 may further include an input interface 1030 . The processor 1010 can control the input interface 1030 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.

Optionally, the chip 1000 may further include an output interface 1040 . The processor 1010 can control the output interface 1040 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.

Optionally, the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which is not repeated here for brevity.

Optionally, the chip can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application. For brevity, here No longer.

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

FIG. 11 is a schematic block diagram of a communication system 1100 provided by an embodiment of the present application. As shown in FIG. 11 , the communication system 1100 includes a terminal device 1110 and a network device 1120 .

The terminal device 1110 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1120 can be used to implement the corresponding functions implemented by the network device in the above method. For brevity, details are not repeated here. .

It should be understood that the processor in this embodiment of the present application may be an integrated circuit chip, which has a signal processing capability. In the implementation process, each step of the above method embodiments may be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software. The above-mentioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other available Programming logic devices, discrete gate or transistor logic devices, discrete hardware components. The methods, steps, and logic block diagrams disclosed in the embodiments of this application can be implemented or executed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art. The storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically programmable read-only memory (Erasable PROM, EPROM). Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. Volatile memory may be Random Access Memory (RAM), which acts as an external cache. By way of example and not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synchlink DRAM, SLDRAM) ) and direct memory bus random access memory (Direct Rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but not be limited to, these and any other suitable types of memory.

It should be understood that the above memory is an example but not a limitative description, for example, the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

Embodiments of the present application further provide a computer-readable storage medium for storing a computer program.

Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For brevity, here No longer.

Optionally, the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application. , and are not repeated here for brevity.

Embodiments of the present application also provide a computer program product, including computer program instructions.

Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. Repeat.

Optionally, the computer program product can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, For brevity, details are not repeated here.

The embodiments of the present application also provide a computer program.

Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity. , and will not be repeated here.

Optionally, the computer program may be applied to the mobile terminal/terminal device in the embodiments of the present application, and when the computer program is run on the computer, the mobile terminal/terminal device implements the various methods of the computer program in the embodiments of the present application. The corresponding process, for the sake of brevity, will not be repeated here.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution, and the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this. should be covered within the scope of protection of this application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

A method for indicating a multicast multicast service MBS service, the method comprising:

The terminal device sends the identification information of the MBS service to the network device, where the MBS service is the MBS service expected by the terminal device or the MBS service being received;

The identification information of the MBS service is used for the configuration of the dedicated downlink bandwidth part BWP of the terminal device and/or the identification information of the MBS service is used to determine the target cell to be handed over by the terminal device.
The method according to claim 1, wherein the terminal device sends the identification information of the MBS service to the network device, comprising:

The terminal device sends the identification information of the MBS service to the network device through a first RRC message, where the first RRC message is an RRC message that has not undergone security processing.
The method of claim 2, wherein,

The first RRC message is an RRC setup complete message; or,

The first RRC message is an MBS indication message.
The method according to claim 1, wherein the terminal device sends the identification information of the MBS service to the network device, comprising:

The terminal device sends the identification information of the MBS service to the network device through a second RRC message, where the second RRC message is an RRC message that has undergone security processing.
The method of claim 4, wherein,

The second RRC message is a security activation complete message; or,

The second RRC message is a UEAssistanceInformation message; or,

The second RRC message is an MBS indication message.
The method according to any one of claims 2 to 5, wherein the MBS service is a desired MBS service or an MBS service being received by the terminal device in an RRC idle state;

Before the terminal device enters the RRC connected state, the method further includes:

sending, by the terminal device, an RRC setup request message to the network device;

The terminal device receives the RRC setup message sent by the network device.
The method according to any one of claims 2 to 5, wherein the MBS service is a desired MBS service or an MBS service being received by the terminal device in an RRC inactive state;

Before the terminal device enters the RRC connected state, the method further includes:

The terminal device sends an RRC recovery request message to the network device; wherein, the RRC recovery process falls back to the RRC establishment process;

The terminal device receives the RRC setup message sent by the network device.
The method according to claim 1, wherein the terminal device sends the identification information of the MBS service to the network device, comprising:

The terminal device sends the identification information of the MBS service to the network device through an RRC recovery complete message.
The method according to claim 8, wherein before the terminal device sends an RRC recovery complete message, the method further comprises:

sending, by the terminal device, an RRC recovery request message to the network device;

The terminal device receives the RRC recovery message sent by the network device.
The method according to claim 9, wherein the RRC recovery request message is used to determine first indication information, and the first indication information is used to indicate whether the terminal device is receiving a broadcast MBS service.
The method according to claim 10, wherein the RRC recovery request message carries the first indication information; wherein,

The value of the idle bit in the RRC recovery request message is used to represent the first indication information; or,

The value of the recovery cause in the RRC recovery request message is used to represent the first indication information.
The method according to claim 10, wherein the value of the logical channel identifier of the CCCH corresponding to the RRC recovery request message is used to represent the first indication information.
The method according to claim 12, wherein the logical channel identifier of the CCCH is carried in a header corresponding to the RRC recovery request message in the MAC TB.
The method according to claim 9, wherein before the terminal device sends an RRC recovery request message to the network device, the method further comprises:

The terminal device sends MSG1 or MSGA to the network device, where the MSG1 or MSGA is used to determine first indication information, where the first indication information is used to indicate at least one of the following:

Whether the terminal device is receiving the broadcast MBS service;

Identification information of the MBS service being received by the terminal device.
The method according to any one of claims 9 to 14, wherein the RRC recovery message carries second configuration information, and the second configuration information is used to determine the BWP configuration information of the PCell, wherein the first configuration information of the PCell is The bandwidth of an activated downlink BWP includes the bandwidth of the initial downlink BWP of the PCell and/or the bandwidth of the MBS BWP of the PCell.
The method according to claim 15, wherein the bandwidth of the MBS BWP of the PCell is determined by the network device according to the bandwidth of the MBS BWP corresponding to the MBS service identifier indicated by the terminal device.
The method of any one of claims 2 to 16, wherein the method further comprises:

The terminal device receives an RRC reconfiguration message sent by the network device, where the RRC reconfiguration message carries first configuration information, where the first configuration information is used to determine the configuration information of the dedicated downlink BWP.
The method according to claim 1, wherein the terminal device sends the identification information of the MBS service to the network device, comprising:

The terminal device sends the identification information of the MBS service to the network device through MSG1 or MSGA.
The method according to claim 18, wherein the MSG1 or the MSGA is used to determine first indication information, and the first indication information is used to indicate at least one of the following:

Whether the terminal device is receiving the broadcast MBS service;

Identification information of the MBS service being received by the terminal device.
The method according to claim 18 or 19, wherein after the terminal device sends MSG1 or MSGA, the method further comprises:

sending, by the terminal device, an RRC recovery request message to the network device;

The terminal device receives an RRC recovery message sent by the network device, where the RRC recovery message carries first configuration information, where the first configuration information is used to determine configuration information of the dedicated downlink BWP.
The method of any one of claims 14, 18 to 20, wherein,

The preamble and/or RO resource corresponding to the MSG1 or MSGA has an associated relationship with whether the terminal device is receiving the broadcast MBS service; and/or,

The preamble and/or RO resource corresponding to the MSG1 or MSGA has an associated relationship with the identification information of the MBS service received by the terminal device.
The method of claim 21, wherein the association is configured through a system broadcast message.
The method of claim 21 or 22, wherein the method further comprises:

The terminal device determines the preamble and/or RO resource corresponding to the MSG1 or MSGA according to whether it is receiving the broadcasted MBS service and/or the identification information of the received MBS service.
The method according to claim 17 or 20, wherein the first configuration information is used to determine the configuration information of the dedicated downlink BWP of the PCell, and the bandwidth of the dedicated downlink BWP of the PCell includes the bandwidth of the initial downlink BWP of the PCell and/or the bandwidth of the PCell's MBS BWP.
The method according to claim 17 or 20, wherein the first configuration information is used to determine the configuration information of the dedicated downlink BWP of the SCell, and the bandwidth of the dedicated downlink BWP of the SCell includes the bandwidth of the initial downlink BWP of the SCell and/or the bandwidth of the MBS BWP of the SCell.
The method of claim 25, wherein the method further comprises:

The terminal device receives second indication information sent by the network device, where the second indication information is used to instruct the terminal device to receive the broadcasted MBS service on the SCell.
The method according to claim 25 or 26, wherein if the terminal device receives the broadcasted MBS service on the SCell, the SCell is in an active state or an active state with non-dormancy behavior.
The method according to claim 25 or 26, wherein if the terminal device receives the broadcasted MBS service on the SCell, and the SCell is in a deactivated state or in an activated state with dormancy behavior, the End devices have the following behavior:

Monitor the PDCCH scrambled by the G-RNTI on the SCell and receive the PDSCH corresponding to the PDCCH;

The SCell does not monitor the PDCCH scrambled by the C-RNTI and does not receive the PDSCH corresponding to the PDCCH.
The method according to claim 28, wherein the bandwidth of the first activated downlink BWP of the SCell includes the bandwidth of the initial downlink BWP of the SCell and/or the bandwidth of the MBS BWP of the SCell.
A method for indicating an MBS service, the method comprising:

The network device receives the identification information of the MBS service sent by the terminal device, where the MBS service is the MBS service expected by the terminal device or the MBS service being received;

The identification information of the MBS service is used by the network device to configure a dedicated downlink BWP for the terminal device and/or the identification information of the MBS service is used by the network device to select the target to be handed over for the terminal device community.
The method according to claim 30, wherein the identification information of the MBS service sent by the network device to receive the terminal device comprises:

The network device receives the identification information of the MBS service sent by the terminal device through a first RRC message, where the first RRC message is an RRC message that has not undergone security processing.
The method of claim 31, wherein,

The first RRC message is an RRC setup complete message; or,

The first RRC message is an MBS indication message.
The method according to claim 30, wherein the identification information of the MBS service sent by the network device to receive the terminal device comprises:

The network device receives the identification information of the MBS service sent by the terminal device through a second RRC message, where the second RRC message is a securely processed RRC message.
The method of claim 33, wherein,

The second RRC message is a security activation complete message; or,

The second RRC message is a UEAssistanceInformation message; or,

The second RRC message is an MBS indication message.
The method according to any one of claims 31 to 34, wherein the MBS service is a desired MBS service or an MBS service being received by the terminal device in an RRC idle state;

The method also includes:

receiving, by the network device, an RRC establishment request message sent by the terminal device;

The network device sends an RRC setup message to the terminal device.
The method according to any one of claims 31 to 34, wherein the MBS service is an MBS service expected or an MBS service being received by the terminal device in an RRC inactive state;

The method also includes:

receiving, by the network device, an RRC recovery request message sent by the terminal device; wherein the RRC recovery process falls back to the RRC establishment process;

The network device sends an RRC setup message to the terminal device.
The method according to claim 30, wherein the identification information of the MBS service sent by the network device to receive the terminal device comprises:

The network device receives the identification information of the MBS service sent by the terminal device through the RRC recovery complete message.
The method according to claim 37, wherein before the network device receives the RRC recovery complete message sent by the terminal device, the method further comprises:

receiving, by the network device, an RRC recovery request message sent by the terminal device;

The network device sends an RRC recovery message to the terminal device.
The method according to claim 38, wherein the RRC recovery request message is used to determine first indication information, and the first indication information is used to indicate whether the terminal device is receiving a broadcast MBS service.
The method according to claim 39, wherein the RRC recovery request message carries the first indication information; wherein,

The value of the idle bit in the RRC recovery request message is used to represent the first indication information; or,

The value of the recovery cause in the RRC recovery request message is used to represent the first indication information.
The method according to claim 39, wherein the value of the logical channel identifier of the CCCH corresponding to the RRC recovery request message is used to represent the first indication information.
The method according to claim 41, wherein the logical channel identifier of the CCCH is carried in a header corresponding to the RRC recovery request message in the MAC TB.
The method according to claim 38, wherein before the network device receives the RRC recovery request message sent by the terminal device, the method further comprises:

The network device receives the MSG1 or MSGA sent by the terminal device, where the MSG1 or MSGA is used to determine first indication information, where the first indication information is used to indicate at least one of the following:

Whether the terminal device is receiving the broadcast MBS service;

Identification information of the MBS service being received by the terminal device.
The method according to any one of claims 38 to 43, wherein the RRC recovery message carries second configuration information, and the second configuration information is used to determine the BWP configuration information of the PCell, wherein the first configuration information of the PCell is The bandwidth of an activated downlink BWP includes the bandwidth of the initial downlink BWP of the PCell and/or the bandwidth of the MBS BWP of the PCell.
The method according to claim 44, wherein the bandwidth of the MBS BWP of the PCell is determined by the network device according to the bandwidth of the MBS BWP corresponding to the MBS service identifier indicated by the terminal device.
The method of any one of claims 31 to 45, wherein the method further comprises:

The network device sends an RRC reconfiguration message to the terminal device, where the RRC reconfiguration message carries first configuration information, where the first configuration information is used to determine configuration information of the dedicated downlink BWP.
The method according to claim 30, wherein the identification information of the MBS service sent by the terminal device to be received by the network device comprises:

The network device receives the identification information of the MBS service sent by the terminal device through MSG1 or MSGA.
The method according to claim 47, wherein the MSG1 or MSGA is used to determine first indication information, and the first indication information is used to indicate at least one of the following:

Whether the terminal device is receiving the broadcast MBS service;

Identification information of the MBS service being received by the terminal device.
The method according to claim 47 or 48, wherein after the network device receives the MSG1 or MSGA sent by the terminal device, the method further comprises:

receiving, by the network device, an RRC recovery request message sent by the terminal device;

The network device sends an RRC recovery message to the terminal device, where the RRC recovery message carries first configuration information, where the first configuration information is used to determine configuration information of the dedicated downlink BWP.
The method of any one of claims 43, 47 to 49, wherein,

The preamble and/or RO resource corresponding to the MSG1 or MSGA has an associated relationship with whether the terminal device is receiving the broadcast MBS service; and/or,

The preamble and/or RO resource corresponding to the MSG1 or MSGA has an associated relationship with the identification information of the MBS service received by the terminal device.
The method of claim 50, wherein the association is configured through a system broadcast message.
The method according to claim 46 or 49, wherein the first configuration information is used to determine the configuration information of the dedicated downlink BWP of the PCell, and the bandwidth of the dedicated downlink BWP of the PCell includes the bandwidth of the initial downlink BWP of the PCell and/or the bandwidth of the PCell's MBS BWP.
The method according to claim 46 or 49, wherein the first configuration information is used to determine the configuration information of the dedicated downlink BWP of the SCell, and the bandwidth of the dedicated downlink BWP of the SCell includes the bandwidth of the initial downlink BWP of the SCell and/or the bandwidth of the MBS BWP of the SCell.
The method of claim 53, wherein the method further comprises:

The network device sends second indication information to the terminal device, where the second indication information is used to instruct the terminal device to receive the broadcasted MBS service on the SCell.
The method according to claim 53 or 54, wherein if the terminal device receives the broadcasted MBS service on the SCell, the SCell is in an active state or in an active state with non-dormancy behavior.
The method according to claim 53 or 54, wherein if the terminal device receives the broadcasted MBS service on the SCell, and the SCell is in a deactivated state or is in an activated state with dormancy behavior, the terminal device The device has the following behavior:

Monitoring the PDCCH scrambled by the G-RNTI on the SCell and receiving the PDSCH corresponding to the PDCCH;

The SCell does not monitor the PDCCH scrambled by the C-RNTI and does not receive the PDSCH corresponding to the PDCCH.
The method according to claim 56, wherein the bandwidth of the first activated downlink BWP of the SCell includes the bandwidth of the initial downlink BWP of the SCell and/or the bandwidth of the MBS BWP of the SCell.
The method of any one of claims 30 to 57, wherein the method further comprises:

The network device selects, according to the identification information of the MBS service, a cell supporting the MBS service indicated by the identification information of the MBS service as a target cell for handover.
The method according to claim 58, wherein before the network device selects a cell supporting the MBS service indicated by the identification information of the MBS service as a target cell for handover, the cell and its neighbors interact with each other about each The identification information of the MBS service supported by the cell or the MBS service being transmitted.
A device for indicating an MBS service, applied to terminal equipment, the device includes:

a communication unit, configured to send identification information of an MBS service to a network device, where the MBS service is an MBS service expected by the terminal device or an MBS service being received;

The identification information of the MBS service is used for the configuration of the dedicated downlink bandwidth part BWP of the terminal device and/or the identification information of the MBS service is used to determine the target cell to be handed over by the terminal device.
The apparatus according to claim 60, wherein the communication unit is configured to send the identification information of the MBS service to the network device through a first RRC message, where the first RRC message is an RRC message that has not undergone security processing.
The apparatus of claim 61, wherein,

The first RRC message is an RRC setup complete message; or,

The first RRC message is an MBS indication message.
The apparatus according to claim 60, wherein the communication unit is configured to send the identification information of the MBS service to the network device through a second RRC message, where the second RRC message is a securely processed RRC message.
The apparatus of claim 63, wherein,

The second RRC message is a security activation complete message; or,

The second RRC message is a UEAssistanceInformation message; or,

The second RRC message is an MBS indication message.
The apparatus according to any one of claims 61 to 64, wherein the MBS service is an MBS service expected or an MBS service being received by the terminal device in an RRC idle state;

The communication unit is further configured to send an RRC establishment request message to the network device; and receive an RRC establishment message sent by the network device.
The apparatus according to any one of claims 61 to 64, wherein the MBS service is an MBS service expected or an MBS service being received by the terminal device in an RRC inactive state;

The communication unit is further configured to send an RRC recovery request message to the network device; wherein, the RRC recovery process falls back to the RRC setup process; and receives the RRC setup message sent by the network device.
The apparatus according to claim 60, wherein the communication unit is configured to send the identification information of the MBS service to the network device through an RRC recovery complete message.
The apparatus according to claim 67, wherein the communication unit is further configured to send an RRC recovery request message to the network device; and receive an RRC recovery message sent by the network device.
The apparatus according to claim 68, wherein the RRC recovery request message is used to determine first indication information, and the first indication information is used to indicate whether the terminal device is receiving a broadcast MBS service.
The apparatus according to claim 69, wherein the RRC recovery request message carries the first indication information; wherein,

The value of the idle bit in the RRC recovery request message is used to represent the first indication information; or,

The value of the recovery cause in the RRC recovery request message is used to represent the first indication information.
The apparatus according to claim 69, wherein the value of the logical channel identifier of the CCCH corresponding to the RRC recovery request message is used to represent the first indication information.
The apparatus according to claim 71, wherein the logical channel identifier of the CCCH is carried in a header corresponding to the RRC recovery request message in the MAC TB.
The apparatus according to claim 69, wherein the communication unit is further configured to send MSG1 or MSGA to the network device, where the MSG1 or MSGA is used to determine first indication information, and the first indication information is used for Indicate at least one of the following:

Whether the terminal device is receiving the broadcast MBS service;

Identification information of the MBS service being received by the terminal device.
The apparatus according to any one of claims 68 to 73, wherein the RRC recovery message carries second configuration information, and the second configuration information is used to determine BWP configuration information of a PCell, wherein the first configuration information of the PCell is The bandwidth of an activated downlink BWP includes the bandwidth of the initial downlink BWP of the PCell and/or the bandwidth of the MBS BWP of the PCell.
The apparatus according to claim 74, wherein the bandwidth of the MBS BWP of the PCell is determined by the network device according to the bandwidth of the MBS BWP corresponding to the MBS service identifier indicated by the terminal device.
The apparatus according to any one of claims 61 to 75, wherein the communication unit is further configured to receive an RRC reconfiguration message sent by the network device, where the RRC reconfiguration message carries first configuration information, and the The first configuration information is used to determine the configuration information of the dedicated downlink BWP.
The apparatus according to claim 60, wherein the communication unit is configured to send the identification information of the MBS service to the network device through MSG1 or MSGA.
The apparatus according to claim 77, wherein the MSG1 or the MSGA is used to determine first indication information, and the first indication information is used to indicate at least one of the following:

Whether the terminal device is receiving the broadcast MBS service;

Identification information of the MBS service being received by the terminal device.
The apparatus according to claim 77 or 78, wherein the communication unit is further configured to send an RRC recovery request message to the network device; and receive an RRC recovery message sent by the network device, where the RRC recovery message carries the first RRC recovery message. Configuration information, where the first configuration information is used to determine the configuration information of the dedicated downlink BWP.
The apparatus of any one of claims 73, 77 to 79, wherein,

The preamble and/or RO resource corresponding to the MSG1 or MSGA has an associated relationship with whether the terminal device is receiving the broadcast MBS service; and/or,

The preamble and/or RO resource corresponding to the MSG1 or MSGA has an associated relationship with the identification information of the MBS service received by the terminal device.
The apparatus of claim 80, wherein the association is configured through a system broadcast message.
The apparatus of claim 80 or 81, wherein the apparatus further comprises:

A determining unit, configured to determine the preamble and/or RO resource corresponding to the MSG1 or MSGA according to whether the broadcasted MBS service is being received and/or the identification information of the received MBS service.
The apparatus according to claim 76 or 79, wherein the first configuration information is used to determine configuration information of a dedicated downlink BWP of a PCell, and the bandwidth of the dedicated downlink BWP of the PCell includes the bandwidth of the initial downlink BWP of the PCell and/or the bandwidth of the PCell's MBS BWP.
The apparatus according to claim 76 or 79, wherein the first configuration information is used to determine the configuration information of the dedicated downlink BWP of the SCell, and the bandwidth of the dedicated downlink BWP of the SCell includes the bandwidth of the initial downlink BWP of the SCell and/or the bandwidth of the MBS BWP of the SCell.
The apparatus according to claim 84, wherein the communication unit is further configured to receive second indication information sent by the network device, where the second indication information is used to instruct the terminal device to receive on the SCell Broadcast MBS service.
The apparatus according to claim 84 or 85, wherein if the terminal device receives the broadcasted MBS service on the SCell, the SCell is in an active state or an active state with non-dormancy behavior.
The apparatus according to claim 84 or 85, wherein if the terminal device receives the broadcasted MBS service on the SCell, and the SCell is in a deactivated state or in an activated state with dormancy behavior, the End devices have the following behavior:

Monitor the PDCCH scrambled by the G-RNTI on the SCell and receive the PDSCH corresponding to the PDCCH;

The SCell does not monitor the PDCCH scrambled by the C-RNTI and does not receive the PDSCH corresponding to the PDCCH.
The apparatus according to claim 87, wherein the bandwidth of the first activated downlink BWP of the SCell includes the bandwidth of the initial downlink BWP of the SCell and/or the bandwidth of the MBS BWP of the SCell.
A device for indicating an MBS service, applied to network equipment, the device includes:

a communication unit, configured to receive identification information of an MBS service sent by a terminal device, where the MBS service is an MBS service expected by the terminal device or an MBS service being received;

The identification information of the MBS service is used by the network device to configure a dedicated downlink BWP for the terminal device and/or the identification information of the MBS service is used by the network device to select the target to be handed over for the terminal device community.
The apparatus according to claim 89, wherein the communication unit is configured to receive the identification information of the MBS service sent by the terminal device through a first RRC message, where the first RRC message is an RRC message without security processing .
The apparatus of claim 90, wherein,

The first RRC message is an RRC setup complete message; or,

The first RRC message is an MBS indication message.
The apparatus according to claim 89, wherein the communication unit is configured to receive the identification information of the MBS service sent by the terminal device through a second RRC message, where the second RRC message is an RRC message that has undergone security processing.
The apparatus of claim 92, wherein,

The second RRC message is a security activation complete message; or,

The second RRC message is a UEAssistanceInformation message; or,

The second RRC message is an MBS indication message.
The apparatus according to any one of claims 90 to 93, wherein the MBS service is an MBS service expected or an MBS service being received by the terminal device in an RRC idle state;

The communication unit is further configured to receive an RRC establishment request message sent by the terminal device; and send an RRC establishment message to the terminal device.
The apparatus according to any one of claims 90 to 93, wherein the MBS service is an MBS service expected or an MBS service being received by the terminal device in an RRC inactive state; the communication unit further It is used for receiving the RRC recovery request message sent by the terminal device; wherein, the RRC recovery process falls back to the RRC establishment process; and the RRC establishment message is sent to the terminal device.
The apparatus according to claim 89, wherein the communication unit is configured to receive the identification information of the MBS service sent by the terminal device through the RRC recovery complete message.
The apparatus according to claim 96, wherein the communication unit is further configured to receive an RRC recovery request message sent by the terminal device; and send an RRC recovery message to the terminal device.
The apparatus according to claim 97, wherein the RRC recovery request message is used to determine first indication information, and the first indication information is used to indicate whether the terminal device is receiving a broadcast MBS service.
The apparatus according to claim 98, wherein the RRC recovery request message carries the first indication information; wherein,

The value of the idle bit in the RRC recovery request message is used to represent the first indication information; or,

The value of the recovery cause in the RRC recovery request message is used to represent the first indication information.
The apparatus according to claim 98, wherein the value of the logical channel identifier of the CCCH corresponding to the RRC recovery request message is used to represent the first indication information.
The apparatus according to claim 100, wherein the logical channel identifier of the CCCH is carried in a header corresponding to the RRC recovery request message in a MAC TB.
The apparatus according to claim 97, wherein the communication unit is further configured to receive MSG1 or MSGA sent by the terminal device, where the MSG1 or MSGA is used to determine first indication information, the first indication information Used to indicate at least one of the following:

Whether the terminal device is receiving the broadcast MBS service;

Identification information of the MBS service being received by the terminal device.
The apparatus according to any one of claims 97 to 102, wherein the RRC recovery message carries second configuration information, and the second configuration information is used to determine BWP configuration information of a PCell, wherein the first configuration information of the PCell is The bandwidth of an activated downlink BWP includes the bandwidth of the initial downlink BWP of the PCell and/or the bandwidth of the MBS BWP of the PCell.
The apparatus according to claim 103, wherein the bandwidth of the MBS BWP of the PCell is determined by the network device according to the bandwidth of the MBS BWP corresponding to the MBS service identifier indicated by the terminal device.
The apparatus according to any one of claims 90 to 104, wherein the communication unit is further configured to send an RRC reconfiguration message to the terminal device, where the RRC reconfiguration message carries first configuration information, the The first configuration information is used to determine the configuration information of the dedicated downlink BWP.
The apparatus according to claim 89, wherein the communication unit is configured to receive the identification information of the MBS service sent by the terminal device through MSG1 or MSGA.
The apparatus according to claim 106, wherein the MSG1 or the MSGA is used to determine first indication information, and the first indication information is used to indicate at least one of the following:

Whether the terminal device is receiving the broadcast MBS service;

Identification information of the MBS service being received by the terminal device.
The apparatus according to claim 106 or 107, wherein the communication unit is further configured to receive an RRC recovery request message sent by the terminal device; and send an RRC recovery message to the terminal device, the RRC recovery message carrying the first RRC recovery message. Configuration information, where the first configuration information is used to determine the configuration information of the dedicated downlink BWP.
The apparatus of any one of claims 102, 106 to 108, wherein,

The preamble and/or RO resource corresponding to the MSG1 or MSGA has an associated relationship with whether the terminal device is receiving the broadcast MBS service; and/or,

The preamble and/or RO resource corresponding to the MSG1 or MSGA has an associated relationship with the identification information of the MBS service received by the terminal device.
The apparatus of claim 109, wherein the association is configured through a system broadcast message.
The apparatus according to claim 105 or 108, wherein the first configuration information is used to determine configuration information of a dedicated downlink BWP of a PCell, and the bandwidth of the dedicated downlink BWP of the PCell includes the bandwidth of the initial downlink BWP of the PCell and/or the bandwidth of the PCell's MBS BWP.
The apparatus according to claim 105 or 108, wherein the first configuration information is used to determine the configuration information of the dedicated downlink BWP of the SCell, and the bandwidth of the dedicated downlink BWP of the SCell includes the bandwidth of the initial downlink BWP of the SCell and/or the bandwidth of the MBS BWP of the SCell.
The apparatus according to claim 112, wherein the communication unit is further configured to send second indication information to the terminal device, where the second indication information is used to instruct the terminal device to receive broadcast on the SCell MBS business.
The apparatus according to claim 112 or 113, wherein if the terminal device receives the broadcast MBS service on the SCell, the SCell is in an active state or in an active state with non-dormancy behavior.
The apparatus according to claim 112 or 113, wherein, if the terminal device receives the broadcasted MBS service on the SCell, and the SCell is in a deactivated state or is in an activated state with dormancy behavior, the terminal device The device has the following behavior:

Monitor the PDCCH scrambled by the G-RNTI on the SCell and receive the PDSCH corresponding to the PDCCH;

The SCell does not monitor the PDCCH scrambled by the C-RNTI and does not receive the PDSCH corresponding to the PDCCH.
The apparatus according to claim 115, wherein the bandwidth of the first activated downlink BWP of the SCell includes the bandwidth of the initial downlink BWP of the SCell and/or the bandwidth of the MBS BWP of the SCell.
The apparatus of any one of claims 98 to 116, wherein the apparatus further comprises:

The selecting unit is configured to select, according to the identification information of the MBS service, a cell supporting the MBS service indicated by the identification information of the MBS service as a target cell for handover.
The apparatus according to claim 117, wherein before the network device selects a cell supporting the MBS service indicated by the identification information of the MBS service as a target cell for handover, the cell and its neighbors interact with each other about each Identification information of the MBS service supported by the cell or the MBS service being transmitted.
A terminal device, comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and executes any one of claims 1 to 29. Methods.
A network device, comprising: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, and executes any one of claims 30 to 59. Methods.
A chip, comprising: a processor for calling and running a computer program from a memory, so that a device on which the chip is installed executes the method according to any one of claims 1 to 29.
A chip, comprising: a processor for invoking and running a computer program from a memory, so that a device on which the chip is installed performs the method as claimed in any one of claims 30 to 59.
A computer-readable storage medium storing a computer program that causes a computer to perform the method of any one of claims 1 to 29.
A computer-readable storage medium storing a computer program that causes a computer to perform the method of any one of claims 30 to 59.
A computer program product comprising computer program instructions that cause a computer to perform the method of any one of claims 1 to 29.
A computer program product comprising computer program instructions that cause a computer to perform the method of any one of claims 30 to 59.
A computer program that causes a computer to perform the method of any one of claims 1 to 29.
A computer program that causes a computer to perform the method of any one of claims 30 to 59.