CN115699650A - TCI state management method and device of MBS (multicast broadcast multicast service) service and terminal equipment - Google Patents

TCI state management method and device of MBS (multicast broadcast multicast service) service and terminal equipment Download PDF

Info

Publication number
CN115699650A
CN115699650A CN202080101109.8A CN202080101109A CN115699650A CN 115699650 A CN115699650 A CN 115699650A CN 202080101109 A CN202080101109 A CN 202080101109A CN 115699650 A CN115699650 A CN 115699650A
Authority
CN
China
Prior art keywords
tci
tci state
mac
service
pdsch
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202080101109.8A
Other languages
Chinese (zh)
Inventor
王淑坤
陈文洪
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Publication of CN115699650A publication Critical patent/CN115699650A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation

Abstract

The embodiment of the application provides a TCI state management method and device of MBS service and terminal equipment, and the method comprises the following steps: the method comprises the steps that terminal equipment receives a first MAC CE sent by network equipment, wherein the first MAC CE is used for activating a first TCI state in a first TCI state list; and the terminal equipment receives the PDCCH of the MBS service based on the first TCI state under the condition that the first TCI state is determined to be the PDCCH TCI state of the MBS service.

Description

TCI state management method and device of MBS (multicast broadcast multicast service) service and terminal equipment Technical Field
The embodiment of the present application relates to the field of mobile communication technologies, and in particular, to a method and an apparatus for managing a Transmission Configuration Indicator (TCI) state of a Multimedia multicast Service (MBS) Service, and a terminal device.
Background
In the process of transmitting the MBS service in the multicast mode, because a plurality of users receive one MBS service together and the coverage areas of beams (beams) of different users are different, how to receive the MBS service in the multicast mode in the beam mode is a problem to be solved.
Disclosure of Invention
The embodiment of the application provides a TCI state management method and device for MBS service and terminal equipment.
The TCI state management method for the MBS service provided by the embodiment of the application comprises the following steps:
a terminal device receives a first Media Access Control Element (MAC CE) sent by a network device, where the first MAC CE is used to activate a first TCI state in a first TCI state list;
and the terminal equipment receives a Physical Downlink Control Channel (PDCCH) of the MBS service based on the first TCI state under the condition that the first TCI state is determined to be the PDCCH of the MBS service.
The TCI state management method for the MBS service provided by the embodiment of the application comprises the following steps:
the terminal equipment receives a second MAC CE sent by the network equipment, wherein the second MAC CE is used for activating N TCI states in a second TCI state list, and N is a positive integer;
and the terminal equipment receives the PDSCH of the MBS service based on one TCI state in the N TCI states under the condition that the N TCI states are determined as Physical Downlink Shared Channel (PDSCH) TCI states of the MBS service.
The TCI state management device for MBS services provided in an embodiment of the present application includes:
a receiving unit, configured to receive a first MAC CE sent by a network device, where the first MAC CE is used to activate a first TCI state in a first TCI state list; and receiving the PDCCH of the MBS service based on the first TCI state under the condition that the first TCI state is determined to be the PDCCH TCI state of the MBS service.
The TCI status management apparatus for MBS service provided in an embodiment of the present application includes:
a receiving unit, configured to receive a second MAC CE sent by a network device, where the second MAC CE is used to activate N TCI states in a second TCI state list, and N is a positive integer; and under the condition that the N TCI states are determined to be PDSCH TCI states of the MBS service, receiving the PDSCH of the MBS service based on one TCI state in the N TCI states.
The terminal device provided by the embodiment of the application comprises a processor and a memory. The memory is used for storing computer programs, and the processor is used for calling and running the computer programs stored in the memory to execute the TCI state management method of the MBS service.
The network equipment provided by the embodiment of the application comprises a processor and a memory. The memory is used for storing computer programs, and the processor is used for calling and running the computer programs stored in the memory to execute the TCI state management method of the MBS service.
The chip provided by the embodiment of the application is used for realizing the TCI state management method of the MBS service.
Specifically, the chip includes: and the processor is used for calling and running the computer program from the memory so that the equipment provided with the chip executes the TCI state management method of the MBS service.
The computer-readable storage medium provided in the embodiments of the present application is used for storing a computer program, where the computer program enables a computer to execute the above-mentioned TCI state management method for MBS service.
The computer program product provided in the embodiment of the present application includes computer program instructions, and the computer program instructions enable a computer to execute the TCI state management method for MBS service.
When the computer program provided by the embodiment of the application runs on a computer, the computer is enabled to execute the TCI state management method of the MBS service.
Through the technical scheme, the method for managing the TCI state of the MBS service in the multicast transmission is provided, the TCI state list is configured for the terminal equipment, and one or more TCI states in the TCI state list are activated through the MAC CE, so that the physical downlink channel (such as PDCCH or PDSCH) of the MBS service is received based on the activated TCI state. Here, the TCI state is used to determine a downlink receive beam, and the terminal device receives a physical downlink channel of the MBS service using the downlink receive beam corresponding to the TCI state, thereby implementing receiving the MBS service in a beam manner in a multicast manner.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1 is a schematic diagram of an architecture of a communication system provided in an embodiment of the present application;
fig. 2 is a schematic diagram of Beam surfing provided in an embodiment of the present application;
FIG. 3 is a schematic representation of an SSB provided by an embodiment of the present application;
FIG. 4 is a diagram illustrating an SSB burst set period according to an embodiment of the present application;
fig. 5 is a schematic diagram illustrating that MBS services provided in the embodiment of the present application are transmitted in a multicast manner and a unicast manner;
fig. 6 is a schematic diagram of MBS service transmission via a beam according to an embodiment of the present application;
fig. 7 is a first flowchart illustrating a TCI state management method for MBS services according to an embodiment of the present application;
fig. 8 is a structural diagram of a first MAC CE provided in an embodiment of the present application;
fig. 9 is a flowchart illustrating a second method for TCI state management of MBS services according to an embodiment of the present application;
fig. 10 is a structural diagram of a second MAC CE provided in an embodiment of the present application;
fig. 11 is a first schematic structural diagram of a TCI state management device of an MBS service according to an embodiment of the present application;
fig. 12 is a schematic structural component diagram of a TCI status management device of an MBS service according to an embodiment of the present application;
fig. 13 is a schematic structural diagram of a communication device according to an embodiment of the present application;
FIG. 14 is a schematic structural diagram of a chip of an embodiment of the present application;
fig. 15 is a schematic block diagram of a communication system according to an embodiment of the present application.
Detailed Description
Technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD) system, a 5G communication system, a future communication system, or the like.
Illustratively, a communication system 100 applied in the embodiment of the present application 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). 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 Node B (eNB or eNodeB) in an LTE system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the Network device may be a mobile switching center, a relay station, an Access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a Network-side device in a 5G Network, or a Network device in a future communication system, and the like.
The communication system 100 further comprises at least one terminal 120 located within the coverage area of the network device 110. As used herein, "terminal" includes, but is not limited to, connection via a wireline, such as via a Public Switched Telephone Network (PSTN), a Digital Subscriber Line (DSL), a Digital cable, a direct cable connection; and/or another data connection/network; and/or via a Wireless interface, e.g., for a cellular Network, a Wireless Local Area Network (WLAN), a digital television Network such as a DVB-H Network, a satellite Network, an AM-FM broadcast transmitter; and/or means of another terminal arranged to receive/transmit communication signals; and/or Internet of Things (IoT) devices. A terminal that is arranged to communicate over 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 Systems (PCS) terminals that may combine cellular radiotelephones with data processing, facsimile, and data Communications capabilities; PDAs that may include radiotelephones, pagers, internet/intranet access, web browsers, notepads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. A terminal can refer to an access terminal, user Equipment (UE), a subscriber unit, a subscriber station, mobile, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having Wireless communication capabilities, a computing device or other processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, a terminal in a 5G network, or a terminal in a future evolved PLMN, etc.
Optionally, the terminals 120 may perform direct-to-Device (D2D) communication therebetween.
Alternatively, the 5G communication system or the 5G network may also be referred to as a New Radio (NR) system or an NR network.
Fig. 1 exemplarily shows one network device and two terminals, and optionally, the communication system 100 may include a plurality of network devices and may include other numbers of terminals within the coverage of each network device, which is not limited in this embodiment of the present application.
Optionally, the communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like, which is not limited in this embodiment.
It should be understood that, in the embodiments of the present application, a device having a communication function in a 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 having a communication function, and the network device 110 and the terminal 120 may be the specific devices described above and are not described again here; the communication device may also include other devices in the communication system 100, such as other network entities, for example, a network controller, a mobility management entity, and the like, which is not limited in this embodiment.
It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" herein is merely an association relationship describing an associated object, and means that there may be three relationships, for example, a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
In order to facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions related to the embodiments of the present application are described below.
With the pursuit of speed, delay, high-speed mobility, energy efficiency and the diversity and complexity of services in future life, the third generation cooperation is used for the pursuit of speed, delay, high-speed mobility and energy efficiencyPartner program (3) rd Generation Partnership Project,3 GPP) the international organization for standardization began developing 5G. The main application scenarios of 5G are: enhanced Mobile Ultra wide band (eMBB), low-Latency high-reliability communication (URLLC), and massive Machine-Type communication (mMTC).
On the one hand, the eMBB still targets users to obtain multimedia content, services and data, and its demand is growing very rapidly. On the other hand, because the eMBB may be deployed in different scenarios, such as indoor, urban, rural, etc., and the difference between the capabilities and the requirements is relatively large, it cannot be said that it must be analyzed in detail in conjunction with a specific deployment scenario. Typical applications of URLLC include: industrial automation, power automation, remote medical operations (surgery), traffic safety, etc. Typical characteristics of mtc include: high connection density, small data volume, insensitive time delay service, low cost and long service life of the module, etc.
When NR is deployed early, complete NR coverage is difficult to obtain, so typical network coverage is wide area LTE coverage and islanding coverage mode of NR. Moreover, a large amount of LTE is deployed below 6GHz, and the spectrum below 6GHz available for 5G is rare. NR must therefore be studied for spectrum applications above 6GHz, with limited high band coverage and fast signal fading. Meanwhile, in order to protect the early LTE investment of a mobile operator, a light interworking (TIGHT) working mode between LTE and NR is provided.
Figure PCTCN2020101320-APPB-000001
RRC state
In order to reduce air interface signaling, quickly recover wireless connection, and quickly recover data service, 5G defines a new Radio Resource Control (RRC) state, that is, an RRC INACTIVE (RRC _ INACTIVE) state. This state is distinguished from the RRC IDLE (RRC IDLE) state and the RRC ACTIVE (RRC ACTIVE) state. Wherein, the first and the second end of the pipe are connected with each other,
1) RRC _ IDLE state (IDLE state for short): the mobility is cell selection and reselection based on terminal equipment, paging is initiated by a Core Network (CN), and a paging area is configured by the CN. The base station side has no terminal equipment context and no RRC connection.
2) RRC _ CONNECTED state (CONNECTED state for short): the RRC connection exists, and the base station side and the terminal device side have a terminal device context. The network side knows that the location of the terminal device is at a particular cell level. Mobility is network side controlled mobility. Unicast data may be communicated between the terminal device and the base station.
3) RRC _ INACTIVE state (INACTIVE state for short): mobility is based on cell selection reselection of terminal equipment, connection between CN-NR exists, context of the terminal equipment exists on a certain base station, paging is triggered by RAN, a paging area based on the RAN is managed by the RAN, and the network side knows that the position of the terminal equipment is based on the paging area level of the RAN.
Figure PCTCN2020101320-APPB-000002
Beam scanning (beam sweeping)
NR will be deployed at high frequency in the future, and in order to improve coverage, in 5G, the requirement of coverage (coverage by space and space by time) is satisfied by introducing a beam surfing mechanism, as shown in fig. 2. After the beam sweeping is introduced, a synchronization Signal needs to be transmitted in each beam direction, and a 5G synchronization Signal is given in the form of SSB, which includes a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH), as shown in fig. 3. The synchronization signal of 5G appears periodically in the time domain in the form of a burst set of synchronization signals (SS burst set), as shown in fig. 4.
Figure PCTCN2020101320-APPB-000003
MBMS
MBMS is a technology for transmitting data from one data source to a plurality of UEs by sharing network resources, which enables broadcasting and multicasting of a multimedia service at a higher rate (e.g., 256 kbps) by effectively using network resources while providing the multimedia service.
Because the MBMS spectrum efficiency is low, it is not enough to effectively carry and support the operation of the mobile tv type service. Therefore, in LTE, 3GPP explicitly proposes to enhance the support capability for downlink high-speed MBMS services, and determines the design requirements for the physical layer and air interface.
The 3GPP R9 introduces evolved MBMS (eMBMS) into LTE. eMBMS proposes a Single Frequency Network (SFN) concept, that is, a Multimedia Broadcast multicast service Single Frequency Network (MBSFN), which uses a uniform Frequency to simultaneously transmit service data in all cells, but needs to ensure synchronization between cells. The method can greatly improve the distribution of the overall signal-to-noise ratio of the cell, and the frequency spectrum efficiency can be correspondingly and greatly improved. eMBMS implements broadcast and multicast of services based on IP multicast protocol.
In LTE or 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 idle-state or connected-state UE.
A Single Cell Point To multipoint (SC-PTM) concept is introduced into a 3GPP R13, and the SC-PTM is based on an MBMS network architecture.
MBMS introduces new logical channels including a Single Cell-Multicast Control Channel (SC-MCCH) and a Single Cell-Multicast Transport Channel (SC-MTCH). The SC-MCCH and SC-MTCH are mapped to a Downlink-Shared Channel (DL-SCH), and the DL-SCH is further mapped to a Physical Downlink Shared Channel (PDSCH), wherein the SC-MCCH and SC-MTCH belong to a logical Channel, the DL-SCH belongs to a transport Channel, and the PDSCH belongs to a Physical Channel. The SC-MCCH and SC-MTCH do not support Hybrid Automatic Repeat reQuest (HARQ) operation.
MBMS introduces a new System Information Block (SIB) type, SIB20. Specifically, the configuration information of the SC-MCCH is transmitted through the SIB20, and one cell has only one SC-MCCH. The configuration information of the SC-MCCH comprises: the modification period of the SC-MCCH, the repetition period of the SC-MCCH, the wireless frame and the subframe for scheduling the SC-MCCH and the like. Further, 1) the boundary of the modification period of the SC-MCCH satisfies SFN mod m =0, where SFN represents the system frame number of the boundary, and m is the modification period of the SC-MCCH configured in SIB20 (i.e., SC-MCCH-modification period). 2) And scheduling the radio frame of the SC-MCCH to meet the following requirements: SFN mod MCCH-repetition period = MCCH-Offset, where SFN represents a system frame number of a radio frame, MCCH-repetition period represents a repetition period of the SC-MCCH, and MCCH-Offset represents an Offset of the SC-MCCH. 3) And the sub-frame for scheduling the SC-MCCH is indicated by SC-MCCH-Subframe.
The SC-MCCH is scheduled through a Physical Downlink Control Channel (PDCCH). On one hand, a new Radio Network Temporary Identity (RNTI), that is, a Single Cell RNTI (SC-RNTI) is introduced to identify a PDCCH (such as SC-MCCH PDCCH) for scheduling an SC-MCCH, and optionally, the SC-RNTI is fixedly valued as FFFC. On the other hand, a new RNTI, namely a Single Cell Notification RNTI (SC-N-RNTI) is introduced to identify a PDCCH (e.g., notification PDCCH) for indicating a change Notification of the SC-MCCH, and optionally, the SC-N-RNTI is fixedly valued as FFFB; further, the change notification may be indicated by one bit of 8 bits (bits) of the DCI 1C. In LTE, the configuration information of SC-PTM is based on SC-MCCH configured by SIB20, and then SC-MCCH configures SC-MTCH which is used for transmitting service data.
Specifically, the SC-MCCH transmits only one message (i.e., SCPTMConfiguration) for configuring configuration information of the SC-PTM. The configuration information of SC-PTM includes: temporary Mobile Group Identity (TMGI), session Identity (session id), group RNTI (G-RNTI), discontinuous Reception (DRX) configuration information, SC-PTM service information of the neighbor cell, and the like. It should be noted that SC-PTM in R13 does not support Robust Header Compression (ROHC) function.
The downlink discontinuous reception of SC-PTMs is controlled by the following parameters: ondurationtimerscmp, drx-inactivetiimerscmp, SC-MTCH-scheduling cycle, and SC-MTCH-scheduling offset.
When [ (SFN x 10) + subframe number ] module (SC-MTCH-scheduling cycle) = SC-MTCH-scheduling offset is satisfied, a timer onDurationTimerSCPTM is started;
when receiving downlink PDCCH dispatching, starting a timer drx-InactivetyTimerSCPTM;
the downlink SC-PTM service is received only when the timer onDurationTimerSCPTM or drx-inactivityttimerscptm is running.
SC-PTM service continuity adopts SIB 15-based MBMS service continuity concept, namely SIB15+ MBMSIntestrIndication mode. The traffic continuity of idle UEs is based on the concept of frequency priority.
In the technical solution of the embodiment of the present application, a new SIB (referred to as a first SIB) is defined, where the first SIB includes configuration information of a first MCCH, where the first MCCH is a control channel of an MBMS service, in other words, the first SIB is used to configure configuration information of a control channel of an NR MBMS, and optionally, the control channel of the NR MBMS may also be referred to as an NR MCCH (i.e., the first MCCH).
Further, the first MCCH is used to carry a first signaling, and in this embodiment of the present application, the name of the first signaling is not limited, for example, the first signaling is signaling a, the first signaling includes configuration information of at least one first MTCH, where the first MTCH is a traffic channel (also referred to as a data channel or a transport channel) of an MBMS service, and the first MTCH is used to transmit MBMS service data (e.g., service data of NR MBMS). In other words, the first MCCH is used to configure configuration information of a traffic channel of the NR MBMS, which may also be called NR MTCH (i.e., the first MTCH) optionally.
Specifically, the first signaling is used to configure a service channel of the NR MBMS, service information corresponding to the service channel, and scheduling information corresponding to the service channel. Further, optionally, the service information corresponding to the service channel, for example, the identification information for identifying the service, such as the TMGI, the session id, and the like. The scheduling information corresponding to the traffic channel, for example, the RNTI used when the MBMS service data corresponding to the traffic channel is scheduled, such as G-RNTI, DRX configuration information, and the like.
It should be noted that the transmission of the first MCCH and the first MTCH is scheduled based on PDCCH. Wherein, the RNTI used by the PDCCH for scheduling the first MCCH uses a network-wide unique identifier, which is a fixed value. The RNTI used by the PDCCH for scheduling the first MTCH is configured through the first MCCH.
It should be noted that, in the embodiment of the present application, naming of the first SIB, the first MCCH, and the first MTCH is not limited. For convenience of description, the first SIB may also be abbreviated as SIB, the first MCCH may also be abbreviated as MCCH, the first MTCH may also be abbreviated as MTCH, and a PDCCH for scheduling MCCH (i.e., MCCH PDCCH) and a notification PDCCH are configured through SIB, wherein PDSCH for transmitting MCCH (i.e., MCCH PDSCH) is scheduled through DCI carried by MCCH PDCCH. Further, M PDCCHs for scheduling MTCH (i.e., MTCH 1PDCCH, MTCH 2PDCCH, …, MTCH M PDCCH) are configured through the MCCH, wherein DCI carried by the MTCH n PDCCH schedules a PDSCH for transmitting MTCH n (i.e., MTCH n PDSCH), and n is an integer greater than or equal to 1 and less than or equal to M. The MCCH and MTCH are mapped to DL-SCH, which belongs to a logical channel, and further mapped to PDSCH, which belongs to a physical channel.
It should be noted that the MBMS service in the above scheme includes, but is not limited to, a multicast service and a multicast service. In the embodiment of the present application, an MBS service is taken as an example for description, and the description of the "MBS service" may also be replaced by a "multicast service" or an "MBMS service".
In the NR MBS service, besides that the same cell needs to send the MBS service in multicast transmission, it may also transmit the MBS service in unicast for a specific user, for example, when the channel of the user is poor, the MBS service needs to be transmitted in unicast for the user. In a cell, there may also be several users receiving a certain MBS service at the same time, but the base station sends the MBS service to each user in a unicast manner, for example, the efficiency of service transmission can be effectively improved by sending the MBS service to each user in a unicast manner when there are fewer users receiving the MBS service in the cell.
Referring to fig. 5, for a Packet Data Unit (PDU) session of a certain MBS service, a Shared GTP tunnel (Shared GTP tunnel) may be used between a 5G Core network (5G Core network,5 gc) and a gNB to transmit the MBS service, that is, the GTP tunnel is Shared for both unicast service and MBS service. The gNB issues the MBS service to a multicast group (multicast group) in a multicast (multicast) manner, and issues the MBS service to a certain UE in a unicast (unicast) manner (fig. 5 takes UE3 as an example). Wherein, the multicast group includes one or more UEs (fig. 5 takes the example that the multicast group includes UE1 and UE 2).
In the process of transmitting the MBS service in the multicast mode, because a plurality of users receive one MBS service together and coverage areas of beams of different users are different, it is clear how to receive the MBS service in the multicast mode in the beam mode. Therefore, the following technical scheme of the embodiment of the application is provided.
Referring to fig. 6, fig. 6 is a schematic diagram of MBS service transmission through beams provided in the embodiment of the present application, where MBS data 1 is transmitted through 4 beams, MBS data 2 is transmitted through 3 beams, and MBS3 is transmitted through 2 beams. In the embodiment of the present application, the TCI status is used to determine a beam, and different beams correspond to different TCI statuses, and the "TCI status" may be understood as a "beam". In fig. 6, taking MBS data 1 as an example, MBS data 1 is transmitted through 4 PDSCHs, and 4 PDSCHs (i.e. PDSCH1, PDSCH2, PDSCH3, and PDSCH 4) are in one-to-one correspondence with 4 TCI states (i.e. TCI state 1, TCI state 2, TCI state 3, and TCI state 4), where each TCI state in the 4 TCI states corresponds to one beam, and UE1, UE2, UE3, and UE4 are located in a beam coverage range respectively, that is, different UEs are under different beam coverage ranges. Considering mobility, the beam on which each UE is located is dynamically changed, taking MBS data 2 as an example, UE1 and UE4 are located under the same beam coverage, UE2 is located under another beam coverage, and UE3 is located under another coverage. Taking MBS data 3 as an example, UE1 and UE4 are located under the same beam coverage, and UE2 and UE3 are located under another beam coverage.
Fig. 7 is a first flowchart illustrating a TCI state management method for an MBS service provided in an embodiment of the present application, where as shown in fig. 7, the TCI state management method for an MBS service includes the following steps:
step 701: the terminal equipment receives a first MAC CE sent by the network equipment, wherein the first MAC CE is used for activating a first TCI state in a first TCI state list.
In this embodiment, the network device may be a base station, such as a gbb.
In this embodiment of the present application, before the terminal device receives a first MAC CE sent by a network device, the terminal device receives first configuration information sent by the network device, where the first configuration information is used to determine a first TCI state list, where the first TCI state list includes at least one TCI state identifier, and the at least one TCI state identifier belongs to a TCI state identifier of an MBS service. In an optional manner, the first configuration information is carried in RRC signaling.
In the above scheme, the first TCI status list may also be referred to as a PDCCH TCI status list, where the PDCCH TCI status list includes at least one PDCCH TCI status identifier, and the PDCCH TCI status refers to a TCI status for receiving a PDCCH or a TCI status for determining a reception beam of the PDCCH.
In the embodiment of the application, in order to enable the terminal device to distinguish the TCI state identifier of the MBS service from the TCI state identifier of the unicast service, the TCI state identifier may be implemented by any one of two schemes.
The first scheme is as follows: the at least one TCI state identifier is selected from a first number range in a public number range, and a second number range in the public number range is used for determining the TCI state identifier of the unicast service.
Here, a TCI status identification range (i.e. the first number range) is reserved by the protocol specification or the network side exclusively for MBS services. For example: the current TCI status identification range (i.e. common number range) is {0,1,2, … …, N }, and the protocol specifies or the network side reserves a TCI status identification range (i.e. first number range) from the current TCI status identification range as {0,1,2, … …, k }, which is dedicated to MBS services. Further, the remaining TCI status flag range (i.e., the second number range) is { k +1, K +2, K +3, … …, N }, which may be used for unicast traffic.
Based on this, the network device may configure a PDCCH TCI status list (i.e., a first TCI status list) for MBS services within the first number range. Specifically, the network device selects one or more TCI status identifiers within a first number range to form a first TCI status list.
It should be noted that, when the network side configures the TCI state identifier of the MBS service, it is ensured that the configured TCI state identifier of each terminal device in the multicast group where the MBS service is located is unique in the cell.
Scheme II: the at least one TCI state identifier is selected from the independent number range for MBS service.
Here, an independent TCI status identification range (i.e., an independent number range) is configured by protocol specification or network side specifically for MBS service. The independent numbering range for MBS service and the independent numbering range for unicast service are independent from each other, and can be numbered respectively. For example: the independent numbering range for the MBS service is {0,1,2, … …, N1}, the independent numbering range for the unicast service is {0,1,2, … …, N2}, and the values of N1 and N2 can be the same or different.
Based on this, the network device may configure a PDCCH TCI status list (i.e., a first TCI status list) for the MBS service in an independent number range for the MBS service. Specifically, the network device selects one or more TCI status identifiers within an independent numbering range for the MBS service to form a first TCI status list.
Step 702: and the terminal equipment receives the PDCCH of the MBS service based on the first TCI state under the condition that the first TCI state is determined to be the PDCCH TCI state of the MBS service.
In this embodiment of the application, after receiving the first MAC CE sent by the network device, how to determine whether the first TCI state activated by the first MAC CE is the TCI state of the MBS service or the TCI state of the unicast service needs to be clear, which may be specifically clear by any one of the following manners.
Any one of the following first to fourth modes may be implemented in combination with "mode one" of the above-described modes. Any one of the following first, second, and fourth modes may be implemented in combination with "mode two" in the above-described modes.
● In a first mode
The PDSCH where the first MAC CE is located is scheduled through first DCI, and if the first DCI is scrambled through G-RNTI, the terminal equipment determines that a first TCI state activated by the first MAC CE is a PDCCH TCI state of an MBS service; and if the first DCI is scrambled by the C-RNTI, the terminal equipment determines that the first TCI state activated by the first MAC CE is the PDCCH TCI state of the unicast service.
In one example, the structure of the first MAC CE is shown with reference to fig. 8, and the first MAC CE includes a TCI status flag, which is used to determine the activated first TCI status. Further, the first MAC CE further includes a Serving Cell (Serving Cell) identifier and a Control Resource Set (CORESET) identifier. The serving cell identifier is used for determining a serving cell where the PDCCH is located, and the CORESET identifier is used for determining a CORESET where the PDCCH is located. If the first MAC CE is used for scheduling the DCI of the PDSCH where the first MAC CE is located by the G-RNTI scrambling, the first MAC CE activates the PDCCH TCI state of the MBS service (namely the MBS PDCCH TCI state). If the first MAC CE is activated by the C-RNTI scrambling for scheduling the DCI of the PDSCH where the first MAC CE is located, the PDCCH TCI state of the unicast service (namely, the unicast PDCCH TCI state) is activated by the first MAC CE.
● Mode two
The first MAC CE is associated with a first LCID, and the terminal equipment determines whether the first TCI state activated by the first MAC CE is the PDCCH TCI state of MBS service or the PDCCH TCI state of unicast service based on the first LCID.
In one example, a new MAC CE is defined as a first MAC CE, and the first TCI state activated by the first MAC CE is distinguished by the LCID associated with the first MAC CE as the TCI state of the MBS service (i.e., MBS PDCCH TCI state) or the TCI state of the unicast service (i.e., unicast PDCCH TCI state). For example: if the LCID associated with the first MAC CE is the first LCID, the first MAC CE activates the PDCCH TCI state of the MBS service (i.e., the MBS PDCCH TCI state). If the LCID associated with the first MAC CE is the second LCID, the first MAC CE activates the PDCCH TCI status of the unicast service (i.e., the unicast PDCCH TCI status). Here, the structure of the new MAC CE may be defined as shown in fig. 8, or may be different from fig. 8.
● Mode III
And the terminal equipment determines whether the first TCI state activated by the first MAC CE is the PDCCH TCI state of the MBS service or the PDCCH TCI state of the unicast service based on the TCI state identifier corresponding to the first TCI state.
Here, it should be noted that, the TCI status identifier of the MBS service and the TCI status identifier of the unicast service are differentiated (refer to the above "scheme one"), and it can be determined whether the corresponding TCI status is the PDCCH TCI status of the MBS service or the PDCCH TCI status of the unicast service through the TCI status identifier.
In one example, a first number range in the common number ranges is dedicated to MBS service, a second number range in the common number ranges is dedicated to unicast service, the first number range and the second number range have no overlapping portion, and if the TCI state identifier of the first TCI state belongs to the first number range, the first MAC CE activates a PDCCH TCI state (i.e., MBS PDCCH TCI state) of the MBS service. If the TCI status flag of the first TCI status belongs to the second number range, the first MAC CE activates the PDCCH TCI status of the unicast service (i.e., unicast PDCCH TCI status).
● Mode IV
The first MAC CE carries a CORESET identifier, and as shown in fig. 8, the terminal device determines, based on the CORESET identifier, whether the first TCI state activated by the first MAC CE is a PDCCH TCI state of an MBS service or a PDCCH TCI state of a unicast service.
In one example, a separate CORESET is configured for the PDCCH of MBS traffic (distinguished from the CORESET of the PDCCH of unicast traffic), and the first TCI state activated distinguished by CORESET identification is specific to MBS traffic. If the core set identifier in the first MAC CE is the first core set identifier, the first MAC CE activates the PDCCH TCI state of the MBS service (i.e., MBS PDCCH TCI state). If the core set identifier in the first MAC CE is the second core set identifier, the first MAC CE activates the PDCCH TCI state of the unicast service (i.e., the unicast PDCCH TCI state).
Fig. 9 is a flowchart illustrating a second flowchart of a TCI state management method for an MBS service provided in an embodiment of the present application, where as shown in fig. 9, the TCI state management method for an MBS service includes the following steps:
step 901: and the terminal equipment receives a second MAC CE sent by the network equipment, wherein the second MAC CE is used for activating N TCI states in a second TCI state list, and N is a positive integer.
In this embodiment, the network device may be a base station, such as a gbb.
In this embodiment of the present application, before the terminal device receives the second MAC CE sent by the network device, the terminal device receives second configuration information sent by the network device, where the second configuration information is used to determine a second TCI status list, where the second TCI status list includes at least one TCI status identifier, and the at least one TCI status identifier belongs to a TCI status identifier of an MBS service. In an optional manner, the second configuration information is carried in RRC signaling.
In the above scheme, the first TCI status list may also be referred to as a PDSCH TCI status list, where the PDSCH TCI status list includes at least one PDSCH TCI status identifier, and the PDSCH TCI status refers to a TCI status for receiving a PDSCH or a TCI status for determining a receiving beam of the PDSCH.
In the embodiment of the present application, in order to enable the terminal device to distinguish the TCI status identifier of the MBS service from the TCI status identifier of the unicast service, the TCI status identifier may be implemented by any one of two schemes.
Scheme a: the at least one TCI state identifier is selected from a first number range in a public number range, and a second number range in the public number range is used for determining the TCI state identifier of the unicast service.
Here, a TCI status identification range (i.e. the first number range) is reserved by the protocol specification or the network side exclusively for MBS services. For example: the current TCI state identification range (i.e. common number range) is {0,1,2, … …, N }, and the protocol specifies that or the network side reserves a TCI state identification range (i.e. first number range) from the range, which is {0,1,2, … …, k }, and is specifically used for MBS services. Further, the remaining TCI status flag range (i.e., the second number range) is { k +1, K +2, K +3, … …, N }, which may be used for unicast traffic.
Based on this, the network device may configure a PDSCH TCI status list (i.e., a second TCI status list) for MBS services within the first number range. Specifically, the network device selects one or more TCI status identifiers within a first number range to form a first TCI status list.
Scheme B: the at least one TCI state identifier is selected from the independent number range for MBS service.
Here, an independent TCI status identification range (i.e., an independent number range) is configured by protocol specification or network side specifically for MBS service. The independent numbering range for MBS service and the independent numbering range for unicast service are independent from each other, and can be numbered respectively. For example: the independent numbering range for the MBS service is {0,1,2, … …, M1}, the independent numbering range for the unicast service is {0,1,2, … …, M2}, and values of M1 and M2 may be the same or different.
Based on this, the network device may configure the PDSCH TCI status list (i.e., the second TCI status list) for MBS services within the independent number range for MBS services. Specifically, the network device selects one or more TCI state identifiers in an independent numbering range for MBS services to form a first TCI state list.
Step 902: and the terminal equipment receives the PDSCH of the MBS service based on one TCI state in the N TCI states under the condition that the N TCI states are determined to be the PDSCH TCI states of the MBS service.
In this embodiment of the present application, after receiving a second MAC CE sent by a network device, how to determine whether N TCI states activated by the second MAC CE are TCI states of an MBS service or TCI states of a unicast service needs to be clear, which may be specifically clear by any one of the following manners.
Any of the following modes I to IV can be implemented in combination with "mode a" in the above-described modes. Any of the following modes I, II, and IV can be implemented in combination with "mode B" in the above-described modes.
Mode I:
the PDSCH where the second MAC CE is located is scheduled through second DCI, and if the second DCI is scrambled through G-RNTI, the terminal equipment determines that N TCI states activated by the second MAC CE are PDSCH TCI states of MBS business; and if the second DCI is scrambled by the C-RNTI, the terminal equipment determines that the N TCI states activated by the second MAC CE are PDSCH TCI states of unicast service.
In an example, referring to fig. 10, the structure of the second MAC CE is shown, where the first MAC CE includes 8 (N-1) × 8 bits, each bit corresponds to one TCI state identifier, and a value of the bit is used to characterize whether the TCI state indicated by the TCI state identifier corresponding to the comparison is activated, for example, a value of the bit is 1 to characterize that the TCI state indicated by the TCI state identifier corresponding to the comparison is activated (or in an activated state), and a value of the bit is 0 to characterize that the TCI state indicated by the TCI state identifier corresponding to the comparison is not activated (or in a deactivated state). Further, the second MAC CE further includes reserved (R) bit, serving Cell (Serving Cell) identity, BWP identity. The serving cell identifier is used to determine a serving cell in which the PDSCH is located, and the BWP identifier is used to determine a BWP in which the PDSCH is located. If the second MAC CE is used for scheduling the DCI of the PDSCH where the second MAC CE is located by the G-RNTI scrambling, the second MAC CE activates the PDSCH TCI state (namely the MBS PDSCH TCI state) of the MBS service. If the C-RNTI is used for scrambling the DCI used for scheduling the PDSCH where the second MAC CE is located, the second MAC CE activates the PDSCH TCI state of unicast traffic (namely the unicast PDSCH TCI state).
Mode II:
and the terminal equipment determines that the N TCI states activated by the second MAC CE are PDSCH TCI states of MBS service or PDSCH TCI states of unicast service based on the second LCID.
In one example, a new MAC CE is defined as a second MAC CE, and it is distinguished by an LCID associated with the second MAC CE whether a TCI state activated by the second MAC CE is a TCI state of MBS traffic (i.e., MBS PDSCH TCI state) or a TCI state of unicast traffic (i.e., unicast PDSCH TCI state). For example: if the LCID associated with the second MAC CE is the first LCID, the second MAC CE activates the PDSCH TCI state of the MBS service (i.e., MBS PDSCH TCI state). If the LCID associated with the second MAC CE is the second LCID, the second MAC CE activates the PDSCH TCI status of the unicast service (i.e., unicast PDSCH TCI status). Here, the structure of the new MAC CE may be defined as shown in fig. 10, or may be different from fig. 10.
Mode III:
and the terminal equipment determines whether the N TCI states activated by the second MAC CE are PDSCH TCI states of MBS service or PDSCH TCI states of unicast service based on the TCI state identifications corresponding to the N TCI states.
Here, it should be noted that, the TCI status identifier of the MBS service and the TCI status identifier of the unicast service are differentiated (refer to the above "scheme a"), and whether the corresponding TCI status is the PDSCH TCI status of the MBS service or the PDSCH TCI status of the unicast service can be determined by the TCI status identifier.
In one example, a first number range of the common number ranges is dedicated to MBS services, a second number range of the common number ranges is dedicated to unicast services, and the first number range and the second number range have no overlapping portion, and if the TCI status identifier of the TCI status activated by the second MAC CE belongs to the first number range, the second MAC CE activates the PDCCH TCI status (i.e., MBS PDCCH TCI status) of the MBS services. If the TCI status identifier of the TCI status activated by the second MAC CE belongs to the second number range, the second MAC CE activates the PDCCH TCI status of the unicast service (i.e., the unicast PDCCH TCI status).
Mode IV:
the second MAC CE carries a first bit field, and the terminal equipment determines whether the N TCI states activated by the second MAC CE are PDSCH TCI states of MBS service or PDSCH TCI states of unicast service based on the value of the first bit field.
In one example, as shown in fig. 10, the structure of the second MAC CE, the first bit field may be implemented by R bits, and a value of the R bits is used to indicate whether the second MAC CE activates the PDSCH TCI state of the MBS service or the PDSCH TCI state of the unicast service. For example: the value of the R bit is 1 to represent that the second MAC CE activates the PDSCH TCI state of the MBS service, and the value of the R bit is 0 to represent that the second MAC CE activates the PDSCH TCI state of the unicast service.
In this embodiment of the application, the terminal device receives a first DCI sent by the network device, where the first DCI is used to indicate M TCI states among the N TCI states, where M is an integer greater than or equal to 1 and less than or equal to N or M is equal to 1; and the terminal equipment receives the PDSCH of the MBS service based on one TCI state in the M TCI states.
In one example, M is equal to 1. In this case, the terminal device receives the PDSCH of the MBS service based on the 1 TCI status indicated by the first DCI.
In one example, M is an integer greater than 1, e.g., M is equal to 8. Without being limited thereto, the value of M may also be other values. In this case, the terminal device selects one TCI state from the M TCI states, and receives the PDSCH of the MBS service based on the TCI state. In an optional manner, the terminal device measures M reference signals based on the M TCI states, and selects the one TCI state used for receiving the PDSCH from the M TCI states based on the measurement results of the M reference signals, for example, selects the TCI state corresponding to the reference signal with the best measurement result, for determining the receive beam of the PDSCH.
In the above scheme, the first DCI is used to schedule the PDSCH, that is, the first DCI carries scheduling information of the PDSCH. The first DCI also carries indication information for indicating M TCI states in the N TCI states.
In the embodiment of the application, if the first DCI is scrambled by the G-RNTI, the terminal device determines that the M TCI states indicated by the first DCI are PDSCH TCI states of the MBS service; and if the first DCI is scrambled by the C-RNTI, the terminal equipment determines that the M TCI states indicated by the first DCI are PDSCH TCI states of unicast service.
Fig. 11 is a schematic structural diagram of a first TCI state management device for MBS services provided in an embodiment of the present application, which is applied to a terminal device, and as shown in fig. 11, the TCI state management device for MBS services includes:
a receiving unit 1101, configured to receive a first MAC CE sent by a network device, where the first MAC CE is used to activate a first TCI state in a first TCI state list; and receiving the PDCCH of the MBS service based on the first TCI state under the condition that the first TCI state is determined to be the PDCCH TCI state of the MBS service.
In an optional manner, the PDSCH where the first MAC CE is located is scheduled through a first DCI, and the apparatus further includes:
a determining unit 1102, configured to determine that a first TCI state activated by the first MAC CE is a PDCCH TCI state of an MBS service if the first DCI is scrambled by the G-RNTI; and if the first DCI is scrambled by the C-RNTI, determining that the first TCI state activated by the first MAC CE is a PDCCH TCI state of a unicast service.
In an optional manner, the first MAC CE associates an LCID, and the apparatus further includes:
a determining unit 1102, configured to determine, based on the first LCID, whether the first TCI status activated by the first MAC CE is a PDCCH TCI status of an MBS service or a PDCCH TCI status of a unicast service.
In an optional manner, the apparatus further comprises:
a determining unit 1102, configured to determine, based on the TCI status identifier corresponding to the first TCI status, whether the first TCI status activated by the first MAC CE is a PDCCH TCI status of an MBS service or a PDCCH TCI status of a unicast service.
In an optional manner, the first MAC CE carries a CORESET identifier, and the apparatus further includes:
a determining unit 1102, configured to determine, based on the CORESET identifier, whether the first TCI state activated by the first MAC CE is a PDCCH TCI state of an MBS service or a PDCCH TCI state of a unicast service.
In an optional manner, the receiving unit 1101 is further configured to receive first configuration information sent by the network device, where the first configuration information is used to determine a first TCI state list, where the first TCI state list includes at least one TCI state identifier, and the at least one TCI state identifier belongs to a TCI state identifier of an MBS service;
wherein the at least one TCI state identifier is selected from a first number range in a common number range, and a second number range in the common number range is used for determining the TCI state identifier of the unicast service.
In an optional manner, the receiving unit 1101 is further configured to receive first configuration information sent by the network device, where the first configuration information is used to determine a first TCI state list, where the first TCI state list includes at least one TCI state identifier, and the at least one TCI state identifier belongs to a TCI state identifier of an MBS service;
wherein the at least one TCI state identifier is selected in an independent number range for MBS service.
Those skilled in the art should understand that the description of the TCI state management apparatus for MBS service in the embodiment of the present application may be understood by referring to the description of the TCI state management method for MBS service in the embodiment of the present application.
Fig. 12 is a schematic structural diagram of a TCI state management device for MBS services provided in an embodiment of the present application, which is applied to a terminal device, and as shown in fig. 12, the TCI state management device for MBS services includes:
a receiving unit 1201, configured to receive a second MAC CE sent by a network device, where the second MAC CE is used to activate N TCI states in a second TCI state list, and N is a positive integer; and under the condition that the N TCI states are determined to be PDSCH TCI states of the MBS service, receiving the PDSCH of the MBS service based on one TCI state in the N TCI states.
In an optional manner, the PDSCH where the second MAC CE is located is scheduled through a second DCI, and the apparatus further includes:
a determining unit 1202, configured to determine that the N TCI states activated by the second MAC CE are PDSCH TCI states of an MBS service if the second DCI is scrambled by the G-RNTI; and if the second DCI is scrambled by the C-RNTI, determining that the N TCI states activated by the second MAC CE are PDSCH TCI states of unicast service.
In an optional manner, the second MAC CE associates a second LCID, and the apparatus further includes:
a determining unit 1202, configured to determine, based on the second LCID, whether the N TCI states activated by the second MAC CE are PDSCH TCI states of MBS services or PDSCH TCI states of unicast services.
In an optional manner, the apparatus further comprises:
a determining unit 1202, configured to determine, based on the TCI status identifiers corresponding to the N TCI statuses, whether the N TCI statuses activated by the second MAC CE are PDSCH TCI statuses of MBS services or PDSCH TCI statuses of unicast services.
In an optional manner, the second MAC CE carries a first bit field, and the apparatus further includes:
a determining unit 1202, configured to determine, based on the value of the first bit field, whether the N TCI states activated by the second MAC CE are PDSCH TCI states of an MBS service or PDSCH TCI states of a unicast service.
In an optional manner, the receiving unit 1201 is further configured to receive second configuration information sent by the network device, where the second configuration information is used to determine a second TCI state list, where the second TCI state list includes at least one TCI state identifier, and the at least one TCI state identifier belongs to a TCI state identifier of an MBS service;
wherein the at least one TCI state identifier is selected from a first number range in a common number range, and a second number range in the common number range is used for determining the TCI state identifier of the unicast service.
In an optional manner, the receiving unit 1201 is further configured to receive second configuration information sent by the network device, where the second configuration information is used to determine a second TCI state list, where the second TCI state list includes at least one TCI state identifier, and the at least one TCI state identifier belongs to a TCI state identifier of an MBS service;
wherein the at least one TCI state identifier is selected in an independent number range for MBS service.
In an optional manner, the receiving unit 1201 is further configured to receive a first DCI sent by the network device, where the first DCI is used to indicate M TCI states of the N TCI states, where M is an integer greater than or equal to 1 and less than or equal to N or M is equal to 1; and receiving the PDSCH of the MBS service based on one TCI state in the M TCI states.
In an optional manner, the apparatus further comprises:
a determining unit 1202, configured to determine, if the first DCI is scrambled by the G-RNTI, that the M TCI states indicated by the first DCI are PDSCH TCI states of an MBS service; and if the first DCI is scrambled by the C-RNTI, determining that the M TCI states indicated by the first DCI are PDSCH TCI states of unicast service.
In an optional manner, the apparatus further comprises:
a measurement unit (not shown in the figure) for measuring the M reference signals based on the M TCI states;
the determining unit 1202 is further configured to select the one TCI state for receiving the PDSCH from the M TCI states based on the measurement results of the M reference signals.
Those skilled in the art should understand that the description of the TCI state management apparatus for MBS service in the embodiment of the present application may be understood by referring to the description of the TCI state management method for MBS service in the embodiment of the present application.
Fig. 13 is a schematic structural diagram of a communication device 1300 according to an embodiment of the present application. The communication device may be a terminal device or a network device, and the communication device 1300 shown in fig. 13 includes a processor 1310, and the processor 1310 may call and execute a computer program from a memory to implement the method in the embodiment of the present application.
Optionally, as shown in fig. 13, the communication device 1300 may further include a memory 1320. From the memory 1320, the processor 1310 may call and run a computer program to implement the method of the embodiment of the present application.
The memory 1320 may be a separate device from the processor 1310, or may be integrated into the processor 1310.
Optionally, as shown in fig. 13, the communication device 1300 may further include a transceiver 1330, and the processor 1310 may control the transceiver 1330 to communicate with other devices, and specifically, may transmit information or data to other devices or receive information or data transmitted by other devices.
The transceiver 1330 may include a transmitter and a receiver, among others. The transceiver 1330 can further include an antenna, and the number of the antennas can be one or more.
Optionally, the communication device 1300 may specifically be a network device in this embodiment, and the communication device 1300 may implement a corresponding process implemented by the network device in each method in this embodiment, which is not described herein again for brevity.
Optionally, the communication device 1300 may specifically be a mobile terminal/terminal device according to this embodiment, and the communication device 1300 may implement a corresponding process implemented by the mobile terminal/terminal device in each method according to this embodiment, which is not described herein again for brevity.
Fig. 14 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 1400 shown in fig. 14 includes a processor 1410, and the processor 1410 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
Optionally, as shown in fig. 14, the chip 1400 may further include a memory 1420. From memory 1420, processor 1410 may invoke and execute a computer program to implement the methods of the embodiments of the present application.
The memory 1420 may be a separate device from the processor 1410, or may be integrated into the processor 1410.
Optionally, the chip 1400 may further include an input interface 1430. The processor 1410 can control the input interface 1430 to communicate with other devices or chips, and in particular, can obtain information or data transmitted by other devices or chips.
Optionally, the chip 1400 may further include an output interface 1440. The processor 1410 can control the output interface 1440 to communicate with other devices or chips, and in particular, can output information or data to other devices or chips.
Optionally, the chip may be applied to the network device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.
Optionally, the chip may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, and for brevity, no further description is given here.
It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip.
Fig. 15 is a schematic block diagram of a communication system 1500 provided in an embodiment of the present application. As shown in fig. 15, the communication system 1500 includes a terminal device 1510 and a network device 1520.
The terminal device 1510 may be configured to implement corresponding functions implemented by the terminal device in the foregoing method, and the network device 1520 may be configured to implement corresponding functions implemented by the network device in the foregoing method, which is not described herein again for brevity.
It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off the shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. 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 connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.
It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), enhanced Synchronous SDRAM (ESDRAM), synchronous link SDRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
It should be understood that the above memories are exemplary but not limiting illustrations, for example, the memories in the embodiments of the present application may also be Static Random Access Memory (SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (enhanced SDRAM, ESDRAM), synchronous Link DRAM (SLDRAM), direct Rambus RAM (DR RAM), and the like. That is, the memory in the embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.
The embodiment of the application also provides a computer readable storage medium for storing the computer program.
Optionally, the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.
Optionally, the computer-readable storage medium may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.
Embodiments of the present application also provide a computer program product comprising computer program instructions.
Optionally, the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions enable the computer to execute corresponding processes implemented by the network device in the methods in the embodiment of the present application, which are not described herein again for brevity.
Optionally, the computer program product may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiment of the present application, which are not described herein again for brevity.
The embodiment of the application also provides a computer program.
Optionally, the computer program may be applied to the network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.
Optionally, the computer program may be applied to the mobile terminal/terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one type of logical functional division, and other divisions may be realized in practice, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, an optical disk, or other various media capable of storing program codes.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (39)

  1. A Transmission Configuration Indication (TCI) state management method for multimedia multicast service (MBS) service comprises the following steps:
    the method comprises the steps that terminal equipment receives a first media access control unit (MAC CE) sent by network equipment, wherein the first MAC CE is used for activating a first TCI state in a first TCI state list;
    and the terminal equipment receives the PDCCH of the MBS service based on the first TCI state under the condition that the first TCI state is determined to be the PDCCH TCI state of the Physical Downlink Control Channel (PDCCH) of the MBS service.
  2. The method according to claim 1, wherein the PDSCH where the first MAC CE is located is scheduled by first downlink control information, DCI, the method further comprising:
    if the first DCI is scrambled by a group radio network temporary identifier (G-RNTI), the terminal equipment determines that a first TCI state activated by the first MAC CE is a PDCCH TCI state of an MBS service;
    and if the first DCI is scrambled by a cell radio network temporary identifier (C-RNTI), the terminal equipment determines that the first TCI state activated by the first MAC CE is a PDCCH TCI state of a unicast service.
  3. The method of claim 1, wherein the first MAC CE is associated with a first logical channel identification, LCID, the method further comprising:
    and the terminal equipment determines whether the first TCI state activated by the first MAC CE is the PDCCH TCI state of the MBS service or the PDCCH TCI state of the unicast service based on the first LCID.
  4. The method of claim 1, wherein the method further comprises:
    and the terminal equipment determines whether the first TCI state activated by the first MAC CE is the PDCCH TCI state of the MBS service or the PDCCH TCI state of the unicast service based on the TCI state identifier corresponding to the first TCI state.
  5. The method of claim 1, wherein the first MAC CE carries a control resource set, CORESET, identity, the method further comprising:
    and the terminal equipment determines whether the first TCI state activated by the first MAC CE is the PDCCH TCI state of the MBS service or the PDCCH TCI state of the unicast service based on the CORESET identifier.
  6. The method of any of claims 1-5, wherein the method further comprises:
    the terminal device receives first configuration information sent by the network device, wherein the first configuration information is used for determining a first TCI state list, the first TCI state list comprises at least one TCI state identifier, and the at least one TCI state identifier belongs to a TCI state identifier of an MBS service;
    wherein the at least one TCI state identifier is selected from a first number range in a common number range, and a second number range in the common number range is used for determining the TCI state identifier of the unicast service.
  7. The method of any of claims 1-3, 5, wherein the method further comprises:
    the terminal device receives first configuration information sent by the network device, wherein the first configuration information is used for determining a first TCI state list, the first TCI state list comprises at least one TCI state identifier, and the at least one TCI state identifier belongs to a TCI state identifier of an MBS service;
    wherein the at least one TCI state identifier is selected in an independent number range for MBS service.
  8. A TCI state management method of MBS service, the method includes:
    the terminal equipment receives a second MAC CE sent by the network equipment, wherein the second MAC CE is used for activating N TCI states in a second TCI state list, and N is a positive integer;
    and the terminal equipment receives the PDSCH of the MBS service based on one TCI state in the N TCI states under the condition that the N TCI states are determined as the PDSCH TCI state of the Physical Downlink Shared Channel (PDSCH) of the MBS service.
  9. The method of claim 8, wherein the PDSCH where the second MAC CE is scheduled with a second DCI, the method further comprising:
    if the second DCI is scrambled by the G-RNTI, the terminal equipment determines that the N TCI states activated by the second MAC CE are PDSCH TCI states of MBS service;
    and if the second DCI is scrambled by the C-RNTI, the terminal equipment determines that the N TCI states activated by the second MAC CE are PDSCH TCI states of unicast service.
  10. The method of claim 8, wherein the second MAC CE is associated with a second LCID, the method further comprising:
    and the terminal equipment determines whether the N TCI states activated by the second MAC CE are PDSCH TCI states of MBS service or PDSCH TCI states of unicast service based on the second LCID.
  11. The method of claim 8, wherein the method further comprises:
    and the terminal equipment determines whether the N TCI states activated by the second MAC CE are PDSCH TCI states of MBS service or PDSCH TCI states of unicast service based on the TCI state identifications corresponding to the N TCI states.
  12. The method of claim 8, wherein the second MAC CE carries a first bit field, the method further comprising:
    and the terminal equipment determines whether the N TCI states activated by the second MAC CE are PDSCH TCI states of MBS service or PDSCH TCI states of unicast service based on the value of the first bit field.
  13. The method of any of claims 8 to 12, wherein the method further comprises:
    the terminal device receives second configuration information sent by the network device, wherein the second configuration information is used for determining a second TCI state list, the second TCI state list comprises at least one TCI state identifier, and the at least one TCI state identifier belongs to a TCI state identifier of an MBS service;
    wherein the at least one TCI state identifier is selected from a first number range in a common number range, and a second number range in the common number range is used for determining the TCI state identifier of the unicast service.
  14. The method of any of claims 8-10, 12, wherein the method further comprises:
    the terminal device receives second configuration information sent by the network device, wherein the second configuration information is used for determining a second TCI state list, the second TCI state list comprises at least one TCI state identifier, and the at least one TCI state identifier belongs to a TCI state identifier of an MBS service;
    wherein the at least one TCI state identifier is selected within an independent number range for MBS services.
  15. The method of any of claims 8 to 14, wherein the receiving a PDSCH of MBS traffic based on one of the N TCI states comprises:
    the terminal equipment receives first DCI sent by the network equipment, wherein the first DCI is used for indicating M TCI states in the N TCI states, and M is an integer which is more than or equal to 1 and less than or equal to N or is equal to 1;
    and the terminal equipment receives the PDSCH of the MBS service based on one TCI state in the M TCI states.
  16. The method of claim 15, wherein the method further comprises:
    if the first DCI is scrambled by the G-RNTI, the terminal equipment determines that M TCI states indicated by the first DCI are PDSCH TCI states of MBS service;
    and if the first DCI is scrambled by the C-RNTI, the terminal equipment determines that the M TCI states indicated by the first DCI are PDSCH TCI states of unicast service.
  17. The method of claim 15 or 16, wherein the method further comprises:
    the terminal device measures M reference signals based on the M TCI states, and selects the one TCI state for receiving the PDSCH from the M TCI states based on measurement results of the M reference signals.
  18. A TCI status management apparatus for MBS service, the apparatus comprising:
    a receiving unit, configured to receive a first MAC CE sent by a network device, where the first MAC CE is used to activate a first TCI state in a first TCI state list; and receiving the PDCCH of the MBS service based on the first TCI state under the condition that the first TCI state is determined to be the PDCCH TCI state of the MBS service.
  19. The apparatus of claim 18, wherein the PDSCH on which the first MAC CE is located is scheduled by a first DCI, the apparatus further comprising:
    a determining unit, configured to determine that a first TCI state activated by the first MAC CE is a PDCCH TCI state of an MBS service if the first DCI is scrambled by the G-RNTI; and if the first DCI is scrambled by the C-RNTI, determining that the first TCI state activated by the first MAC CE is a PDCCH TCI state of a unicast service.
  20. The apparatus of claim 18, wherein the first MAC CE is associated with an LCID, the apparatus further comprising:
    a determining unit, configured to determine, based on the first LCID, whether the first TCI status activated by the first MAC CE is a PDCCH TCI status of an MBS service or a PDCCH TCI status of a unicast service.
  21. The apparatus of claim 18, wherein the apparatus further comprises:
    a determining unit, configured to determine, based on the TCI status identifier corresponding to the first TCI status, whether the first TCI status activated by the first MAC CE is a PDCCH TCI status of an MBS service or a PDCCH TCI status of a unicast service.
  22. The apparatus of claim 18, wherein the first MAC CE carries a CORESET identity, the apparatus further comprising:
    a determining unit, configured to determine, based on the CORESET identifier, whether the first TCI state activated by the first MAC CE is a PDCCH TCI state of an MBS service or a PDCCH TCI state of a unicast service.
  23. The apparatus of any one of claims 18 to 22, wherein the receiving unit is further configured to receive first configuration information sent by the network device, where the first configuration information is used to determine a first TCI status list, where the first TCI status list includes at least one TCI status identifier, and the at least one TCI status identifier belongs to a TCI status identifier of an MBS service;
    wherein the at least one TCI state identifier is selected from a first number range in a common number range, and a second number range in the common number range is used for determining the TCI state identifier of the unicast service.
  24. The apparatus according to any one of claims 18 to 20 and 22, wherein the receiving unit is further configured to receive first configuration information sent by the network device, where the first configuration information is used to determine a first TCI status list, where the first TCI status list includes at least one TCI status identifier, and the at least one TCI status identifier belongs to a TCI status identifier of an MBS service;
    wherein the at least one TCI state identifier is selected in an independent number range for MBS service.
  25. A TCI status management apparatus for MBS service, the apparatus comprising:
    a receiving unit, configured to receive a second MAC CE sent by a network device, where the second MAC CE is used to activate N TCI states in a second TCI state list, and N is a positive integer; and under the condition that the N TCI states are determined to be PDSCH TCI states of the MBS service, receiving the PDSCH of the MBS service based on one TCI state in the N TCI states.
  26. The apparatus of claim 25, wherein the PDSCH where the second MAC CE is scheduled with a second DCI, the apparatus further comprising:
    a determining unit, configured to determine that the N TCI states activated by the second MAC CE are PDSCH TCI states of an MBS service if the second DCI is scrambled by the G-RNTI; and if the second DCI is scrambled by the C-RNTI, determining that the N TCI states activated by the second MAC CE are PDSCH TCI states of unicast service.
  27. The apparatus of claim 25, wherein the second MAC CE is associated with a second LCID, the apparatus further comprising:
    a determining unit, configured to determine, based on the second LCID, whether the N TCI states activated by the second MAC CE are PDSCH TCI states of MBS services or PDSCH TCI states of unicast services.
  28. The apparatus of claim 25, wherein the apparatus further comprises:
    a determining unit, configured to determine, based on the TCI status identifiers corresponding to the N TCI statuses, whether the N TCI statuses activated by the second MAC CE are PDSCH TCI statuses of MBS services or PDSCH TCI statuses of unicast services.
  29. The apparatus of claim 25, wherein the second MAC CE carries a first bit field, the apparatus further comprising:
    a determining unit, configured to determine, based on the value of the first bit field, whether the N TCI states activated by the second MAC CE are PDSCH TCI states of an MBS service or PDSCH TCI states of a unicast service.
  30. The apparatus of any one of claims 25 to 29, wherein the receiving unit is further configured to receive second configuration information sent by the network device, where the second configuration information is used to determine a second TCI status list, where the second TCI status list includes at least one TCI status identifier, and the at least one TCI status identifier belongs to a TCI status identifier of an MBS service;
    wherein the at least one TCI state identifier is selected from a first number range in a common number range, and a second number range in the common number range is used for determining the TCI state identifier of the unicast service.
  31. The apparatus according to any one of claims 25 to 27 and 29, wherein the receiving unit is further configured to receive second configuration information sent by the network device, where the second configuration information is used to determine a second TCI status list, where the second TCI status list includes at least one TCI status identifier, and the at least one TCI status identifier belongs to a TCI status identifier of an MBS service;
    wherein the at least one TCI state identifier is selected within an independent number range for MBS services.
  32. The apparatus according to any one of claims 25 to 31, wherein the receiving unit is further configured to receive a first DCI transmitted by the network device, where the first DCI is configured to indicate M TCI states of the N TCI states, where M is an integer greater than or equal to 1 and less than or equal to N or M is equal to 1; and receiving the PDSCH of the MBS service based on one TCI state in the M TCI states.
  33. The apparatus of claim 32, wherein the apparatus further comprises:
    a determining unit, configured to determine that M TCI states indicated by the first DCI are PDSCH TCI states of an MBS service if the first DCI is scrambled by a G-RNTI; and if the first DCI is scrambled by the C-RNTI, determining that the M TCI states indicated by the first DCI are PDSCH TCI states of unicast service.
  34. The apparatus of claim 32 or 33, wherein the apparatus further comprises:
    a measurement unit for measuring M reference signals based on the M TCI states;
    the determining unit is further configured to select the one TCI state for receiving the PDSCH from the M TCI states based on the measurement results of the M reference signals.
  35. A terminal device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory, to perform the method of any of claims 1 to 7, or to perform the method of any of claims 8 to 17.
  36. 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 performs the method of any of claims 1 to 7, or the method of any of claims 8 to 17.
  37. A computer readable storage medium storing a computer program for causing a computer to perform the method of any one of claims 1 to 7, or the method of any one of claims 8 to 17.
  38. A computer program product comprising computer program instructions to cause a computer to perform the method of any of claims 1 to 7, or the method of any of claims 8 to 17.
  39. A computer program for causing a computer to perform the method of any one of claims 1 to 7, or the method of any one of claims 8 to 17.
CN202080101109.8A 2020-07-10 2020-07-10 TCI state management method and device of MBS (multicast broadcast multicast service) service and terminal equipment Pending CN115699650A (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/101320 WO2022006849A1 (en) 2020-07-10 2020-07-10 Mbs service tci state management method and apparatus, and terminal device

Publications (1)

Publication Number Publication Date
CN115699650A true CN115699650A (en) 2023-02-03

Family

ID=79552182

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202080101109.8A Pending CN115699650A (en) 2020-07-10 2020-07-10 TCI state management method and device of MBS (multicast broadcast multicast service) service and terminal equipment

Country Status (2)

Country Link
CN (1) CN115699650A (en)
WO (1) WO2022006849A1 (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11778625B2 (en) * 2021-01-13 2023-10-03 Qualcomm Incorporated Downlink control information indication for multicast and unicast transmissions
US11937270B2 (en) * 2021-08-04 2024-03-19 Qualcomm Incorporated Techniques for configuring TCI states for MBS transmissions

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3682582A1 (en) * 2017-09-11 2020-07-22 Telefonaktiebolaget LM Ericsson (publ) Unified ul and dl beam indication
ES2960749T3 (en) * 2018-01-19 2024-03-06 Ntt Docomo Inc User equipment in wireless communication system
EP3641461B1 (en) * 2018-05-17 2021-09-08 LG Electronics Inc. Method for determining transmission configuration indicator for terminal in wireless communication system and device using same method
JP7042904B2 (en) * 2018-08-06 2022-03-28 エルジー エレクトロニクス インコーポレイティド A method of receiving a signal in the core set of a wireless communication system and a device using the above method.
CN111327411B (en) * 2018-12-14 2021-08-10 华硕电脑股份有限公司 Method and apparatus for beam indication in wireless communication system

Also Published As

Publication number Publication date
WO2022006849A1 (en) 2022-01-13

Similar Documents

Publication Publication Date Title
CN114651453B (en) Service transmission method and device, terminal equipment, network equipment and related products
CN114424663A (en) Service scheduling method and device, terminal equipment and network equipment
CN114424626A (en) Resource indication method and device, and communication equipment
CN113661722B (en) Service data transmission method and device, network equipment and terminal equipment
CN113661746A (en) Information configuration method and device, terminal equipment and network equipment
CN117480857A (en) MBS service management method and device, terminal equipment and network equipment
CN114600473A (en) Service synchronous scheduling method and device, and communication equipment
CN113678500A (en) Feedback resource allocation method, communication method, device and communication equipment
CN115699650A (en) TCI state management method and device of MBS (multicast broadcast multicast service) service and terminal equipment
CN113728663B (en) DRX configuration method and device, terminal equipment and network equipment
CN113647150B (en) Information configuration method and device, terminal equipment and network equipment
CN115668993A (en) Method and device for receiving local MBS (multicast broadcast multicast service), terminal equipment and network equipment
EP4228189A1 (en) Mcch scheduling transmission method and apparatus, and terminal device
WO2022006875A1 (en) Method and apparatus for establishing mbs service, and terminal device and network device
CN113728683B (en) BWP configuration method and device, terminal equipment and network equipment
CN114342421A (en) Service data transmission method and device, and terminal device
CN116261902A (en) MBS service configuration method and device, terminal equipment and network equipment
CN114902758A (en) Resource configuration method and device, terminal equipment and network equipment
CN114616840A (en) Service transmission method and device, and communication equipment
CN114402634A (en) Access control method and device, terminal equipment and network equipment
US20220210616A1 (en) Data retransmission method and apparatus, and terminal device
CN113711689A (en) Service data transmission method and device, network equipment and terminal equipment
WO2021134761A1 (en) Cell reselection method and apparatus, terminal device, and network device
CN114846825A (en) Data forwarding method and device, and communication equipment
CN114600474A (en) Information indication method and device, terminal equipment and network equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination