MBS service transmission method and device, network equipment, and terminal equipment

Abstract

The embodiment of the present application provides a transmission method and apparatus for MBS services, a network device, and a terminal device. The method includes: the network device uses a first protocol stack to send the MBS service in a multicast manner, and uses a second protocol stack to send the MBS service in a unicast manner.

Description

[0001] This application is a divisional application of the PCT international patent application PCT / CN2020 / 101419 with an application date of July 10, 2020, which has entered the Chinese national phase with Chinese patent application number 202080101106.4 and the invention name being “Transmission method and device, network equipment, and terminal equipment for MBS services”. Technical Field

[0002] The embodiments of the present application relate to the field of mobile communication technology, and specifically to a transmission method and apparatus, network equipment, and terminal equipment for a Multimedia Broadcast Service (MBS) service. Background Art

[0003] In a cell, the base station sends MBS services in multicast mode, and also sends MBS services to a specific user in unicast mode. How to design the protocol stack to implement the simultaneous delivery of MBS services in multicast and unicast mode needs to be solved. On the other hand, when receiving MBS services, the terminal device may also receive non-MBS services. How to design the protocol stack to implement the simultaneous reception of MBS services and non-MBS services needs to be solved. Summary of the invention

[0004] The embodiments of the present application provide a method and apparatus for transmitting MBS services, a network device, and a terminal device.

[0005] The MBS service transmission method provided in the embodiment of the present application includes:

[0006] The network device uses a first protocol stack to send the MBS service in a multicast manner, and uses a second protocol stack to send the MBS service in a unicast manner.

[0007] The MBS service transmission method provided in the embodiment of the present application includes:

[0008] The terminal device uses the first protocol stack to receive the MBS service in a multicast manner or a unicast manner, and uses the second protocol stack to receive the first type of service in a unicast manner, where the first type of service is different from the MBS service.

[0009] The MBS service transmission device provided in the embodiment of the present application includes:

[0010] The sending unit is configured to send the MBS service in a multicast manner using the first protocol stack, and to send the MBS service in a unicast manner using the second protocol stack.

[0011] The MBS service transmission device provided in the embodiment of the present application includes:

[0012] The receiving unit is configured to receive the MBS service in a multicast or unicast manner using a first protocol stack, and receive a first type of service in a unicast manner using a second protocol stack, where the first type of service is different from the MBS service.

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

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

[0015] The chip provided in the embodiment of the present application is used to implement the above-mentioned MBS service transmission method.

[0016] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned MBS service transmission method.

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

[0018] 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 above-mentioned MBS service transmission method.

[0019] The computer program provided in the embodiment of the present application, when executed on a computer, enables the computer to execute the above-mentioned MBS service transmission method.

[0020] Through the above technical solution, the base station uses the first protocol stack to implement sending the MBS service in a multicast manner, and uses the second protocol stack to implement sending the MBS service in a unicast manner, thereby realizing that a cell supports sending the MBS service in both multicast and unicast modes. On the other hand, the terminal device uses the first protocol stack to implement receiving the MBS service in a multicast or unicast manner, and uses the second protocol stack to implement receiving the first type of service (i.e., non-MBS service) in a unicast manner, thereby realizing that the terminal device simultaneously receives the MBS service and the non-MBS service. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0022] Figure 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application;

[0023] Figure 2 It is a schematic diagram of the MBS service provided by the embodiment of the present application being transmitted in a multicast manner and a unicast manner;

[0024] Figure 3 This is a flow diagram of the MBS service transmission method provided in the embodiment of the present application. Figure 1 ;

[0025] Figure 4-1 This is a schematic diagram of the structure of the protocol stack on the network device side provided in the embodiment of the present application. Figure 1 ;

[0026] Figure 4-2 This is a schematic diagram of the structure of the protocol stack on the network device side provided in the embodiment of the present application. Figure 2 ;

[0027] Figure 4-3 This is a schematic diagram of the structure of the protocol stack on the network device side provided in the embodiment of the present application. Figure 3 ;

[0028] Figure 4-4 Schematic diagram 4 of the structure of the protocol stack on the network device side provided in an embodiment of the present application;

[0029] Figure 4-5 This is a schematic diagram of the structure of the protocol stack on the network device side provided in the embodiment of the present application. Figure 5 ;

[0030] Figure 5 This is a flow diagram of the MBS service transmission method provided in the embodiment of the present application. Figure 2 ;

[0031] Figure 6-1 This is a schematic diagram of the structure of the protocol stack on the terminal device side provided in the embodiment of the present application. Figure 1 ;

[0032] Figure 6-2 This is a schematic diagram of the structure of the protocol stack on the terminal device side provided in the embodiment of the present application. Figure 2 ;

[0033] Figure 6-3 This is a schematic diagram of the structure of the protocol stack on the terminal device side provided in the embodiment of the present application. Figure 3 ;

[0034] Figure 6-4 Schematic diagram 4 of the structure of the protocol stack on the terminal device side provided in an embodiment of the present application;

[0035] Figure 7This is a schematic diagram of the structure of the transmission device of the MBS service provided in the embodiment of the present application. Figure 1 ;

[0036] Figure 8 This is a schematic diagram of the structure of the transmission device of the MBS service provided in the embodiment of the present application. Figure 2 ;

[0037] Fig. 9 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0038] Fig.10 is a schematic structural diagram of a chip according to an embodiment of the present application;

[0039] Fig.11 It is a schematic block diagram of a communication system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0040] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

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

[0042] For example, the communication system 100 used in the embodiment of the present application is as follows: Figure 1 As shown. The communication system 100 may include a network device 110, which may be a device that communicates with a terminal 120 (or referred to as a communication terminal, terminal). The network device 110 may provide communication coverage for a specific geographical area, and may communicate with terminals located within the coverage area. Optionally, the network device 110 may be an evolved base station (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, etc.

[0043] The communication system 100 also includes at least one terminal 120 located within the coverage of the network device 110. As used herein, "terminal" includes but is not limited to connecting via a wired line, such as via a Public Switched Telephone Networks (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, such as, 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 another terminal configured to receive / send communication signals; and / or an Internet of Things (IoT) device. A terminal configured to communicate via a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal" or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; Personal Communications System (PCS) terminals that may combine cellular radiotelephones with data processing, fax, 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 radiotelephone transceivers. A terminal may refer to an access terminal, User Equipment (UE), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. The access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with 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.

[0044] Optionally, the terminals 120 may perform device-to-device (D2D) communication.

[0045] Optionally, the 5G communication system or 5G network may also be referred to as a New Radio (NR) system or NR network.

[0046] Figure 1 One network device and two terminals are shown exemplarily. Optionally, the communication system 100 may include multiple network devices and each network device may include another number of terminals within its coverage area, which is not limited in the embodiments of the present application.

[0047] Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.

[0048] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be referred to as a communication device. Figure 1 Taking the communication system 100 shown as an example, the communication equipment may include a network device 110 and a terminal 120 with communication functions. The network device 110 and the terminal 120 may be the specific devices described above and will not be repeated here. The communication equipment may also include other devices in the communication system 100, such as a network controller, a mobile management entity and other network entities, which is not limited in the embodiments of the present application.

[0049] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0050] 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.

[0051] With the pursuit of speed, latency, high-speed mobility, energy efficiency and the diversity and complexity of services in future life, the Third Generation Partnership Project (3GPP) rd The 3rd Generation Partnership Project (3GPP) international standard organization has begun to develop 5G. The main application scenarios of 5G are: enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC).

[0052] On the one hand, eMBB still aims at users to obtain multimedia content, services and data, and its demand is growing rapidly. On the other hand, since eMBB may be deployed in different scenarios, such as indoors, in urban areas, and in rural areas, its capabilities and requirements vary greatly, so it cannot be generalized and must be analyzed in detail in combination with specific deployment scenarios. Typical applications of URLLC include: industrial automation, power automation, remote medical operations (surgery), traffic safety, etc. Typical features of mMTC include: high connection density, small data volume, latency-insensitive services, low cost and long service life of modules, etc.

[0053] In the early days of NR deployment, complete NR coverage was difficult to obtain, so the typical network coverage was wide-area LTE coverage and NR island coverage. In addition, a large number of LTEs are deployed below 6GHz, and there is little spectrum below 6GHz available for 5G. Therefore, NR must study spectrum applications above 6GHz, but high-frequency bands have limited coverage and fast signal fading. At the same time, in order to protect mobile operators' early investments in LTE, a tight interworking working mode between LTE and NR was proposed.

[0054] RRC Status

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

[0056] 1) RRC_IDLE state (abbreviated as idle state): Mobility is based on cell selection and reselection of terminal equipment, paging is initiated by the core network (CN), and the paging area is configured by the CN. There is no terminal equipment context on the base station side, and there is no RRC connection.

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

[0058] 3) RRC_INACTIVE state (abbreviated as inactive state): Mobility is based on cell selection reselection of the terminal device, there is a connection between CN-NR, the terminal device context exists on a certain base station, paging is triggered by RAN, and the paging area based on RAN is managed by RAN. The network side knows the location of the terminal device based on the paging area level of RAN.

[0059] MBMS

[0060] MBMS is a technology that transmits data from one data source to multiple UEs by sharing network resources. This technology can effectively utilize network resources while providing multimedia services, and realize broadcast and multicast of multimedia services at a higher rate (such as 256kbps).

[0061] Since MBMS spectrum efficiency is low, it is not enough to effectively carry and support the operation of mobile TV services. Therefore, in LTE, 3GPP explicitly proposed to enhance the support capability for downlink high-speed MBMS services and determined the design requirements for the physical layer and air interface.

[0062] 3GPP R9 introduced evolved MBMS (eMBMS) into LTE. eMBMS proposed the concept of Single Frequency Network (SFN), namely Multimedia Broadcast multicast service Single Frequency Network (MBSFN). MBSFN uses a unified frequency to send service data in all cells at the same time, but synchronization between cells must be guaranteed. This method can greatly improve the overall signal-to-noise ratio distribution of the cell, and the spectrum efficiency will also be greatly improved accordingly. eMBMS implements broadcast and multicast of services based on the IP multicast protocol.

[0063] In LTE or enhanced LTE (LTE-Advanced, LTE-A), MBMS has only a broadcast bearer mode, but no multicast bearer mode. In addition, the reception of MBMS services is applicable to UEs in an idle state or a connected state.

[0064] 3GPP R13 introduced the concept of Single Cell Point To Multipoint (SC-PTM), which is based on the MBMS network architecture.

[0065] MBMS introduces new logical channels, including Single Cell-Multicast Control Channel (SC-MCCH) and Single Cell-Multicast Transport Channel (SC-MTCH). SC-MCCH and SC-MTCH are mapped to Downlink Shared Channel (DL-SCH), and further, DL-SCH is mapped to Physical Downlink Shared Channel (PDSCH), where SC-MCCH and SC-MTCH are logical channels, DL-SCH is a transport channel, and PDSCH is a physical channel. SC-MCCH and SC-MTCH do not support Hybrid Automatic Repeat reQuest (HARQ) operation.

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

[0067] SC-MCCH is scheduled through the Physical Downlink Control Channel (PDCCH). On the one hand, a new Radio Network Temporary Identity (RNTI), namely the Single Cell RNTI (SC-RNTI), is introduced to identify the PDCCH (such as SC-MCCHPDCCH) used to schedule SC-MCCH. Optionally, the SC-RNTI is fixed to FFFC. On the other hand, a new RNTI, namely the Single Cell Notification RNTI (SC-N-RNTI), is introduced to identify the PDCCH (such as the notification PDCCH) used to indicate the change notification of SC-MCCH. Optionally, the SC-N-RNTI is fixed to FFFB; further, one of the 8 bits of DCI 1C can be used to indicate the change notification. In LTE, the configuration information of SC-PTM is based on the SC-MCCH configured by SIB20, and then the SC-MCCH configures the SC-MTCH, which is used to transmit service data.

[0068] Specifically, SC-MCCH only transmits one message (i.e., SCPTMConfiguration), which is used to configure the configuration information of SC-PTM. The configuration information of SC-PTM includes: Temporary Mobile Group Identity (TMGI), session id, group RNTI (G-RNTI), discontinuous reception (DRX) configuration information, and SC-PTM service information of neighboring cells. It should be noted that SC-PTM in R13 does not support the robust header compression (ROHC) function.

[0069] The downlink discontinuous reception of SC-PTM is controlled by the following parameters: onDurationTimerSCPTM, drx-InactivityTimerSCPTM, SC-MTCH-SchedulingCycle, and SC-MTCH-SchedulingOffset.

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

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

[0072] Downlink SC-PTM services are received only when the timer onDurationTimerSCPTM or drx-InactivityTimerSCPTM is running.

[0073] SC-PTM service continuity adopts the MBMS service continuity concept based on SIB15, namely "SIB15+MBMSInterestIndication". The service continuity of idle UE is based on the concept of frequency priority.

[0074] In the technical solution of the embodiment of the present application, a new SIB (called the first SIB) is defined. The first SIB includes configuration information of the first MCCH. Here, the first MCCH is the control channel of the MBMS service. In other words, the first SIB is used to configure the configuration information of the control channel of NRMBMS. Optionally, the control channel of NR MBMS can also be called NR MCCH (i.e., the first MCCH).

[0075] Further, the first MCCH is used to carry the first signaling. The embodiment of the present application does not limit the name of the first signaling. For example, the first signaling is signaling A. The first signaling includes configuration information of at least one first MTCH. Here, the first MTCH is a service channel (also called a data channel or a transmission channel) of the MBMS service. The first MTCH is used to transmit MBMS service data (such as service data of NR MBMS). In other words, the first MCCH is used to configure the configuration information of the service channel of NR MBMS. Optionally, the service channel of NR MBMS can also be called NR MTCH (i.e., the first MTCH).

[0076] Specifically, the first signaling is used to configure the service channel of NR MBMS, the service information corresponding to the service channel, and the scheduling information corresponding to the service channel. Further, optionally, the service information corresponding to the service channel, such as identification information of the service such as TMGI and session id. The scheduling information corresponding to the service channel, such as the RNTI used when the MBMS service data corresponding to the service channel is scheduled, such as G-RNTI, DRX configuration information, etc.

[0077] It should be noted that the transmission of the first MCCH and the first MTCH are both based on PDCCH scheduling. The RNTI used by the PDCCH for scheduling the first MCCH uses a network-wide unique identifier, that is, a fixed value. The RNTI used by the PDCCH for scheduling the first MTCH is configured through the first MCCH.

[0078] It should be noted that the embodiments of the present application do not limit the naming of the first SIB, the first MCCH and the first MTCH. For ease of description, the first SIB may also be referred to as SIB, the first MCCH may also be referred to as MCCH, and the first MTCH may also be referred to as MTCH. The PDCCH for scheduling MCCH (i.e., MCCHPDCCH) and notifying PDCCH are configured through SIB, wherein the DCI carried by MCCH PDCCH is scheduled for transmitting the PDSCH (i.e., MCCH PDSCH) for MCCH. Further, M PDCCHs for scheduling MTCH (i.e., MTCH 1PDCCH, MTCH2PDCCH, ..., MTCH MPDCCH) are configured through MCCH, wherein the DCI carried by MTCH n PDCCH is scheduled for transmitting the PDSCH for 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. MCCH and MTCH are mapped to DL-SCH, and further, DL-SCH is mapped to PDSCH, wherein MCCH and MTCH belong to logical channels, DL-SCH belongs to a transport channel, and PDSCH belongs to a physical channel.

[0079] It should be noted that the MBMS service in the above solution includes but is not limited to multicast service and groupcast service. The embodiment of the present application takes the MBS service as an example for explanation, and the description of "MBS service" can also be replaced by "multicast service" or "groupcast service" or "MBMS service".

[0080] In the NR MBS service, in addition to sending the MBS service in multicast mode, the same cell may also transmit the MBS service to a specific user in unicast mode. For example, if the channel of the user is poor, the MBS service needs to be transmitted to the user in unicast mode. In a cell, there may be several users receiving a certain MBS service at the same time, but the base station sends the MBS service to each user in unicast mode. For example, if there are few users receiving MBS services in the cell, sending MBS services to each user in unicast mode can effectively improve the service transmission efficiency.

[0081] Reference Figure 2For a packet data unit (PDU) session of a certain MBS service, a shared GTP tunnel may be used between the 5G Core network (5GC) and the gNB to transmit the MBS service, that is, both unicast services and MBS services share this GTP tunnel. The gNB sends the MBS service to the multicast group in a multicast manner, and sends the MBS service to a certain UE in a unicast manner. Figure 2 Take UE3 as an example). The multicast group includes one or more UEs ( Figure 2 Take the multicast group including UE1 and UE2 as an example). It is necessary to solve the problem of how to design the protocol stack for transmitting MBS services in unicast mode and transmitting MBS in multicast mode. To this end, the following technical solutions of the embodiments of the present application are proposed.

[0082] Figure 3 This is a flow diagram of the MBS service transmission method provided in the embodiment of the present application. Figure 1 ,like Figure 3 As shown, the MBS service transmission method includes the following steps:

[0083] Step 301: The network device uses a first protocol stack to send an MBS service in a multicast manner, and uses a second protocol stack to send the MBS service in a unicast manner.

[0084] In the embodiment of the present application, the network device may be a base station, such as a gNB. The network device may implement sending the MBS service in a multicast manner in the same cell, and also send the MBS service in a unicast manner.

[0085] It should be noted that, in the case where the network device sends the MBS service in unicast mode, if the channel of a terminal device is relatively poor, the network device can send the MBS service to the terminal device in unicast mode. Of course, in order to improve the reception efficiency of the MBS service, the network device can also send the MBS service to one or more terminal devices in unicast mode.

[0086] In the embodiment of the present application, the scheduling information of the MBS service sent in a multicast manner is scrambled by the G-RNTI; the scheduling information of the MBS service sent in a unicast manner is scrambled by the G-RNTI or the C-RNTI.

[0087] In the embodiment of the present application, the network device uses the first protocol stack to send the MBS service in a multicast manner, and uses the second protocol stack to send the MBS service in a unicast manner. The specific implementation of the protocol stack on the network device side is described below.

[0088] In an embodiment of the present application, the first protocol stack includes a first physical (PHY) entity, and the second protocol stack includes a second PHY entity; the network device uses the first PHY entity to send the MBS service in a multicast manner, and uses the second PHY entity to send the MBS service in a unicast manner.

[0089] The first protocol stack includes not only the first PHY entity but also other protocol stack entities. The second protocol stack includes not only the second PHY entity but also other protocol stack entities. The following describes the above in detail.

[0090] ●Situation 1

[0091] The first protocol stack and the second protocol stack have a common Media Access Control (MAC) entity; wherein the common MAC entity is used to copy the MAC PDU of the MBS service, transmit the MAC PDU to the first PHY entity, and transmit the copied MAC PDU to the second PHY entity.

[0092] Further, in an optional manner, the first protocol stack and the second protocol stack also have at least one of the following common protocol stack entities: a Service Data Adaptation Protocol (SDAP) entity, a Packet Data Convergence Protocol (PDCP) entity, and a Radio Link Control (RLC) entity.

[0093] ●Situation 2

[0094] The first protocol stack and the second protocol stack have a common SDAP entity; wherein the common SDAP entity is used to copy the SDAP PDU of the MBS service, transmit the SDAP PDU to the PDCP entity or RLC entity in the first protocol stack, and transmit the copied SDAP PDU to the PDCP entity or RLC entity in the second protocol stack.

[0095] Further, in an optional manner, the first protocol stack and the second protocol stack have independent PDCP entities and / or RLC entities.

[0096] ●Situation 3

[0097] The first protocol stack and the second protocol stack have a common PDCP entity; wherein the common PDCP entity is used to copy the PDCP PDU of the MBS service, transmit the PDCP PDU to the RLC entity in the first protocol stack, and transmit the copied PDCP PDU to the RLC entity in the second protocol stack.

[0098] Further, in an optional manner, the first protocol stack and the second protocol stack also have a common SDAP entity, and the first protocol stack and the second protocol stack have an independent RLC entity.

[0099] ●Situation 4

[0100] The first protocol stack and the second protocol stack have a common RLC entity; wherein the common RLC entity is used to copy the RLC PDU of the MBS service, transmit the RLC PDU to the MAC entity in the first protocol stack, and transmit the copied RLC PDU to the MAC entity in the second protocol stack.

[0101] Further, in an optional manner, the first protocol stack and the second protocol stack also have a common SDAP entity and / or PDCP entity.

[0102] ●Situation 5

[0103] The first protocol stack and the second protocol stack have independent SDAP entities, PDCP entities, RLC entities and MAC entities; or, the first protocol stack and the second protocol stack have independent SDAP entities, RLC entities and MAC entities.

[0104] For any of the above situations 2 to 4, the MAC entity on the network device side can be implemented in the following two ways:

[0105] 1) Method 1:

[0106] The first protocol stack and the second protocol stack have a common MAC entity; the common MAC entity is used to map the RLC PDU corresponding to the multicast mode into the first MAC PDU, and map the RLC PDU corresponding to the unicast mode into the second MAC PDU.

[0107] Here, the multicast mode and the unicast mode share a MAC entity, and the network device needs to ensure that when assembling the MAC PDU, the RLC PDU corresponding to the multicast mode is mapped to one MAC PDU, and the RLC PDU corresponding to the unicast mode is mapped to another MAC PDU.

[0108] 2) Method 2:

[0109] The first protocol stack and the second protocol stack have independent MAC entities; the first MAC entity in the first protocol stack is used to map the RLC PDU corresponding to the multicast mode into the first MAC PDU; the second MAC entity in the second protocol stack is used to map the RLC PDU corresponding to the multicast mode into the second MAC PDU.

[0110] Here, the multicast mode and the unicast mode independently configure their own MAC entities. Each MAC entity can use its own MAC layer function, such as DRX function.

[0111] The above-mentioned various situations of the embodiments of the present application are illustrated below with reference to specific examples.

[0112] Example 1 (corresponding to the above situation 1)

[0113] Reference Figure 4-1 , Figure 4-1 A structural diagram of the protocol stack on the network device side. Figure 4-1 The description of "entity" is omitted, for example Figure 4-1 The "SDAP" in the specification refers to the "SDAP entity".

[0114] The PDU session of the MBS service includes one or more QoS streams, and one or more QoS streams of the PDU session can be mapped to one or more DRBs through the SDAP entity, wherein the mapping relationship between the QoS stream and the DRB can be one-to-one or many-to-one. Each DRB corresponds to a logical channel, wherein different DRBs are transmitted through different PDCP entities and RLC entities, that is, different logical channels correspond to different PDCP entities and RLC entities.

[0115] It should be noted that Figure 4-1 For each DRB, there may be no PDCP entity or SDAP entity. That is, for each DRB, there may be a PDCP entity, or there may be a PDCP entity + SDAP entity, or there may be an SDAP entity.

[0116] The MAC entity copies each MAC PDU (i.e., one TB of data) to the PHY2 entity (i.e., the second PHY entity), and the original MAC PDU to the PHY1 entity (i.e., the first PHY entity), and sends the MBS service in a multicast manner through the PHY1 entity and in a unicast manner through the PHY2 entity.

[0117] from Figure 4-1 It can be seen that the first protocol stack (i.e., the protocol stack corresponding to the MBS service sent in multicast mode) and the second protocol stack (i.e., the protocol stack corresponding to the MBS service sent in unicast mode) have the following common protocol stack entities: SDAP entity, PDCP entity, RLC entity and MAC entity, and the first protocol stack and the second protocol stack have independent PHY entities. It should be noted that one or more of the common protocol stack entities may not exist.

[0118] In the above scheme, the network device does not need to implement the functions of the SDAP entity, PDCP entity, RLC entity, and MAC entity twice for the same MBS session. The terminal device can improve the reliability of MBS service reception by simultaneously receiving multicast MBS services and unicast MBS services.

[0119] Example 2 (corresponding to the above situation 2)

[0120] Reference Figure 4-2 , Figure 4-2 A structural diagram of the protocol stack on the network device side. Figure 4-2 The description of "entity" is omitted, for example Figure 4-2 The "SDAP" in the specification refers to the "SDAP entity".

[0121] The PDU session of the MBS service includes one or more QoS streams, and one or more QoS streams of the PDU session can be mapped to one or more DRBs through the SDAP entity, wherein the mapping relationship between the QoS stream and the DRB can be one-to-one or many-to-one. Each DRB corresponds to a logical channel, wherein different DRBs are transmitted through different PDCP entities and RLC entities, that is, different logical channels correspond to different PDCP entities and RLC entities.

[0122] It should be noted that Figure 4-2 For each DRB, there may be no PDCP entity or SDAP entity. That is, for each DRB, there may be a PDCP entity, or there may be a PDCP entity + SDAP entity, or there may be an SDAP entity.

[0123] like Figure 4-2As shown in (a), the SDAP entity copies each SDAP PDU to the PDCP2 entity, and the original SDAP PDU to the PDCP1 entity. Then, the PDCP1 entity transmits the corresponding PDCP PDU to the RLC1 entity, the RLC1 entity transmits the corresponding RLC PDU to the MAC1 entity, the MAC1 entity transmits the corresponding MAC PDU to the PHY1 entity, and the MBS service is sent through the PHY1 entity in a multicast manner; at the same time, the PDCP2 entity transmits the corresponding PDCP PDU to the RLC2 entity, the RLC2 entity transmits the corresponding RLC PDU to the MAC2 entity, the MAC2 entity transmits the corresponding MAC PDU to the PHY2 entity, and the MBS service is sent through the PHY2 entity in a unicast manner.

[0124] like Figure 4-2 As shown in (b), the SDAP entity copies each SDAP PDU to the PDCP2 entity, and the original SDAP PDU to the PDCP1 entity. Then, the PDCP1 entity transmits the corresponding PDCP PDU to the RLC1 entity, the RLC1 entity transmits the corresponding RLC PDU to the MAC entity, the MAC entity transmits the corresponding MAC PDU to the PHY1 entity, and the MBS service is sent through the PHY1 entity in a multicast manner; at the same time, the PDCP2 entity transmits the corresponding PDCP PDU to the RLC2 entity, the RLC2 entity transmits the corresponding RLC PDU to the MAC entity, the MAC entity transmits the corresponding MAC PDU to the PHY2 entity, and the MBS service is sent through the PHY2 entity in a unicast manner.

[0125] It should be noted that Figure 4-2 The PDCP1 entity includes a PDCP11 entity, a PDCP12 entity, ..., a PDCP1n entity, wherein different PDCP entities correspond to different DRBs (ie, correspond to different logical channels). Figure 4-2 The PDCP2 entity in the PDCP2 includes a PDCP21 entity, a PDCP22 entity, ..., a PDCP2n entity, wherein different PDCP entities correspond to different DRBs (that is, to different logical channels). Figure 4-2 The RLC1 entity includes RLC11 entity, RLC12 entity, ..., RLC1n entity, wherein different RLC entities correspond to different DRBs (ie, to different logical channels). Figure 4-2 The RLC2 entity includes an RLC21 entity, an RLC22 entity, ..., an RLC2n entity, wherein different RLC entities correspond to different DRBs (ie, to different logical channels).

[0126] from Figure 4-2 As can be seen from (a), the first protocol stack (i.e., the protocol stack corresponding to the MBS service sent in multicast mode) and the second protocol stack (i.e., the protocol stack corresponding to the MBS service sent in unicast mode) have the following common protocol stack entities: SDAP entity, and the first protocol stack and the second protocol stack have independent PDCP entity, RLC entity, MAC entity and PHY entity. It should be noted that one or more of the independent protocol stack entities may not exist.

[0127] from Figure 4-2 As can be seen from (b), the first protocol stack (i.e., the protocol stack corresponding to the MBS service sent in multicast mode) and the second protocol stack (i.e., the protocol stack corresponding to the MBS service sent in unicast mode) have the following common protocol stack entities: SDAP entity and MAC entity, and the first protocol stack and the second protocol stack have independent PDCP entity, RLC entity and PHY entity. It should be noted that one or more of the independent protocol stack entities may not exist.

[0128] In the above scheme, if the multicast mode and the unicast mode share the PDCP entity, the network device does not need to implement two QoS flow to DRB mappings for the same MBS service. In addition, if the multicast mode and the unicast mode share the MAC entity, the network device does not need to implement the function of the MAC entity twice for the same MBS session; if the multicast mode and the unicast mode are configured with independent MAC entities respectively, the implementation complexity can be effectively reduced.

[0129] Example 3 (corresponding to the above situation 3)

[0130] Reference Figure 4-3 , Figure 4-3 A structural diagram of the protocol stack on the network device side. Figure 4-3 The description of "entity" is omitted, for example Figure 4-3 The "SDAP" in the specification refers to the "SDAP entity".

[0131] The PDU session of the MBS service includes one or more QoS streams, and one or more QoS streams of the PDU session can be mapped to one or more DRBs through the SDAP entity, wherein the mapping relationship between the QoS stream and the DRB can be one-to-one or many-to-one. Each DRB corresponds to a logical channel, wherein different DRBs are transmitted through different PDCP entities and RLC entities, that is, different logical channels correspond to different PDCP entities and RLC entities.

[0132] It should be noted that Figure 4-3For each DRB, there may be no PDCP entity or SDAP entity. That is, for each DRB, there may be a PDCP entity, or there may be a PDCP entity + SDAP entity, or there may be an SDAP entity.

[0133] like Figure 4-3 As shown in (a), the PDCP entity copies each PDCP PDU to the RLC2 entity, and the original PDCP PDU to the RLC1 entity. Then, the RLC1 entity transmits the corresponding RLC PDU to the MAC1 entity, and the MAC1 entity transmits the corresponding MAC PDU to the PHY1 entity, and the MBS service is sent through the PHY1 entity in a multicast manner; at the same time, the RLC2 entity transmits the corresponding RLC PDU to the MAC2 entity, and the MAC2 entity transmits the corresponding MAC PDU to the PHY2 entity, and the MBS service is sent through the PHY2 entity in a unicast manner.

[0134] like Figure 4-3 As shown in (b), the PDCP entity copies each PDCP PDU to the RLC2 entity, and the original PDCP PDU to the RLC1 entity. Then, the RLC1 entity transmits the corresponding RLC PDU to the MAC entity, and the MAC entity transmits the corresponding MAC PDU to the PHY1 entity, and the PHY1 entity sends the MBS service in a multicast manner; at the same time, the RLC2 entity transmits the corresponding RLC PDU to the MAC entity, and the MAC entity transmits the corresponding MAC PDU to the PHY2 entity, and the PHY2 entity sends the MBS service in a unicast manner.

[0135] It should be noted that Figure 4-3 The RLC1 entity includes RLC11 entity, RLC12 entity, ..., RLC1n entity, wherein different RLC entities correspond to different DRBs (ie, to different logical channels). Figure 4-3 The RLC2 entity includes an RLC21 entity, an RLC22 entity, ..., an RLC2n entity, wherein different RLC entities correspond to different DRBs (ie, to different logical channels).

[0136] from Figure 4-3 As can be seen from (a) in FIG. 1 , the first protocol stack (i.e., the protocol stack corresponding to the MBS service sent in multicast mode) and the second protocol stack (i.e., the protocol stack corresponding to the MBS service sent in unicast mode) have the following common protocol stack entities: SDAP entity and PDCP entity, and the first protocol stack and the second protocol stack have independent RLC entity, MAC entity and PHY entity. It should be noted that one or more of the common protocol stack entities may not exist.

[0137] from Figure 4-3 As can be seen from (b) in the figure, the first protocol stack (i.e., the protocol stack corresponding to the MBS service sent in multicast mode) and the second protocol stack (i.e., the protocol stack corresponding to the MBS service sent in unicast mode) have the following common protocol stack entities: SDAP entity, PDCP entity and MAC entity, and the first protocol stack and the second protocol stack have independent RLC entity and PHY entity. It should be noted that one or more of the common protocol stack entities may not exist.

[0138] In the above scheme, if the multicast mode and the unicast mode share the SDAP entity and the PDCP entity, in addition to the network device not needing to implement the functions of the SDAP entity and the PDCP entity twice for the same MBS session, the terminal device can also improve the reliability of MBS service reception by simultaneously receiving the MBS service in the multicast mode and the MBS service in the unicast mode. In addition, if the multicast mode and the unicast mode share the MAC entity, the network device does not need to implement the functions of the MAC entity twice for the same MBS session; if the multicast mode and the unicast mode are configured with independent MAC entities respectively, the implementation complexity can be effectively reduced.

[0139] Example 4 (corresponding to the above situation 4)

[0140] Reference Figure 4-4 , Figure 4-4 A structural diagram of the protocol stack on the network device side. Figure 4-4 The description of "entity" is omitted, for example Figure 4-4 The "SDAP" in the specification refers to the "SDAP entity".

[0141] The PDU session of the MBS service includes one or more QoS streams, and one or more QoS streams of the PDU session can be mapped to one or more DRBs through the SDAP entity, wherein the mapping relationship between the QoS stream and the DRB can be one-to-one or many-to-one. Each DRB corresponds to a logical channel, wherein different DRBs are transmitted through different PDCP entities and RLC entities, that is, different logical channels correspond to different PDCP entities and RLC entities.

[0142] It should be noted that Figure 4-4 For each DRB, there may be no PDCP entity or SDAP entity. That is, for each DRB, there may be a PDCP entity, or there may be a PDCP entity + SDAP entity, or there may be an SDAP entity.

[0143] like Figure 4-4As shown in (a), the RLC entity copies each RLC PDU to the MAC2 entity, and the original RLC PDU to the MAC1 entity. Then, the MAC1 entity transmits the corresponding MAC PDU to the PHY1 entity, and the MBS service is sent through the PHY1 entity in a multicast manner; at the same time, the MAC2 entity transmits the corresponding MAC PDU to the PHY2 entity, and the MBS service is sent through the PHY2 entity in a unicast manner.

[0144] like Figure 4-4 As shown in (b), the RLC entity copies each RLC PDU to the MAC entity, and the original RLC PDU is given to the MAC entity. Then, the MAC entity transmits the corresponding MAC PDU to the PHY1 entity, and the MBS service is sent through the PHY1 entity in a multicast manner; at the same time, the MAC entity transmits the corresponding MAC PDU to the PHY2 entity, and the MBS service is sent through the PHY2 entity in a unicast manner.

[0145] from Figure 4-4 As can be seen from (a) in FIG. 1 , the first protocol stack (i.e., the protocol stack corresponding to the MBS service sent in multicast mode) and the second protocol stack (i.e., the protocol stack corresponding to the MBS service sent in unicast mode) have the following common protocol stack entities: SDAP entity, PDCP entity and RLC entity, and the first protocol stack and the second protocol stack have independent MAC entity and PHY entity. It should be noted that one or more of the common protocol stack entities may not exist.

[0146] from Figure 4-4 As can be seen from (b) in the figure, the first protocol stack (i.e., the protocol stack corresponding to the MBS service sent in multicast mode) and the second protocol stack (i.e., the protocol stack corresponding to the MBS service sent in unicast mode) have the following common protocol stack entities: SDAP entity, PDCP entity, RLC entity and MAC entity, and the first protocol stack and the second protocol stack have independent PHY entities. It should be noted that one or more of the common protocol stack entities may not exist.

[0147] In the above scheme, if the multicast mode and the unicast mode share the SDAP entity, PDCP entity and RLC entity, the network device does not need to implement the functions of the SDAP entity, PDCP entity and RLC entity twice for the same MBS session. It should be noted that this situation does not apply to the AM RLC mode. In addition, if the multicast mode and the unicast mode share the MAC entity, the network device does not need to implement the functions of the MAC entity twice for the same MBS session; if the multicast mode and the unicast mode are configured with independent MAC entities respectively, the implementation complexity can be effectively reduced.

[0148] Example 5 (corresponding to the above situation 5)

[0149] Reference Figure 4-5 , Figure 4-5 A structural diagram of the protocol stack on the network device side. Figure 4-5 The description of "entity" is omitted, for example Figure 4-5 The "SDAP" in the specification refers to the "SDAP entity".

[0150] The PDU session of the MBS service includes one or more QoS streams, and one or more QoS streams of the PDU session can be mapped to one or more DRBs through the SDAP entity, wherein the mapping relationship between the QoS stream and the DRB can be one-to-one or many-to-one. Each DRB corresponds to a logical channel, wherein different DRBs are transmitted through different PDCP entities and RLC entities, that is, different logical channels correspond to different PDCP entities and RLC entities.

[0151] It should be noted that Figure 4-5 For each DRB, there may be no PDCP entity or SDAP entity. That is, for each DRB, there may be a PDCP entity, or there may be a PDCP entity + SDAP entity, or there may be an SDAP entity.

[0152] The QoS flow of the PDU session of the MBS service is copied, the original QoS flow is transmitted to the first protocol stack, and the copied QoS flow is transmitted to the second protocol stack. The first protocol stack and the second protocol stack are completely independent and have their own protocol stack entities.

[0153] In the above scheme, the multicast mode and the unicast mode are respectively configured with independent protocol stacks, and the implementation is relatively simple.

[0154] Figure 5 This is a flow diagram of the MBS service transmission method provided in the embodiment of the present application. Figure 2 ,like Figure 5 As shown, the MBS service transmission method includes the following steps:

[0155] Step 501: The terminal device uses a first protocol stack to receive an MBS service in a multicast or unicast manner, and uses a second protocol stack to receive a first type of service in a unicast manner, where the first type of service is different from the MBS service.

[0156] In the embodiment of the present application, from the perspective of the terminal device, the terminal device receives non-MBS services (hereinafter referred to as first-category services) while receiving MBS services. The first-category services are, for example, eMBB services. The terminal device can receive MBS services in a unicast manner or in a multicast manner, depending on the network side configuration.

[0157] In an embodiment of the present application, a terminal device uses a first protocol stack to receive MBS services in a multicast or unicast manner, and uses a second protocol stack to receive first-category services in a unicast manner. The specific implementation of the protocol stack on the terminal device side is described below.

[0158] In an embodiment of the present application, the first protocol stack includes a first PHY entity, and the second protocol stack includes a second PHY entity; the terminal device uses the first PHY entity to receive the MBS service in a multicast manner or a unicast manner, and uses the second PHY entity to receive the first type of service in a unicast manner.

[0159] The first protocol stack includes not only the first PHY entity but also other protocol stack entities. The second protocol stack includes not only the second PHY entity but also other protocol stack entities. The following describes the above in detail.

[0160] ●Situation A

[0161] The first protocol stack and the second protocol stack have a common MAC entity, and the logical channel identifier of the MBS service is unique within a cell.

[0162] ●Situation B

[0163] The first protocol stack and the second protocol stack have independent MAC entities.

[0164] In an embodiment of the present application, when the terminal device receives the MBS service in a multicast manner, the terminal device uses a first key configured by a network device to decrypt the MBS service, and the first key is a multicast key. Further, the first key is associated with at least one of the following: a logical channel identifier, a data radio bearer DRB identifier, and a PDCP entity.

[0165] In an embodiment of the present application, when the terminal device receives the MBS service in unicast mode, the terminal device uses a second key configured by the network device to decrypt the MBS service, and the second key is a multicast key or a unicast key. Further, the second key is associated with at least one of the following: a logical channel identifier, a DRB identifier, and a PDCP entity.

[0166] The above-mentioned various situations of the embodiments of the present application are illustrated below with reference to specific examples.

[0167] Example 6 (corresponding to the above situation A, and the terminal device receives the MBS service in a multicast manner)

[0168] Reference Figure 6-1 , Figure 6-1 A schematic diagram of the structure of the protocol stack on the terminal device side is shown in FIG. Figure 6-1 The description of "entity" is omitted, for example Figure 6-1 The "SDAP" in the specification refers to the "SDAP entity".

[0169] The terminal device receives MBS services through multicast according to the network configuration, and at the same time, receives eMBB services through unicast. MBS services and eMBB services have independent PHY entities and a common MAC entity. In this case, the protocol stipulates that the logical channel identifier for MBS services is reserved, or the network side ensures that the logical channel identifier of the MBS service is unique within the cell.

[0170] The scheduling information of MBS services is scrambled by G-RNTI, and the terminal device receives the scheduling information of MBS services according to the G-RNTI configured on the network side, and then receives the MBS services by broadcast according to the scheduling information. The scheduling information of eMBB services is scrambled by C-RNTI, and the terminal device receives the scheduling information of eMBB services according to the C-RNTI configured on the network side, and then receives the eMBB services by unicast according to the scheduling information.

[0171] Example 7 (corresponding to the above situation A, and the terminal device receives the MBS service in unicast mode)

[0172] Reference Figure 6-2 , Figure 6-2 A schematic diagram of the structure of the protocol stack on the terminal device side is shown in FIG. Figure 6-2 The description of "entity" is omitted, for example Figure 6-2 The "SDAP" in the specification refers to the "SDAP entity".

[0173] The terminal device receives the MBS service in unicast mode according to the network side configuration, and at the same time, receives the eMBB service in unicast mode. The MBS service and the eMBB service have independent PHY entities and a common MAC entity. In this case, the protocol stipulates that the logical channel identifier for the MBS service is reserved, or the network side ensures that the logical channel identifier of the MBS service is unique within the cell.

[0174] The scheduling information of MBS services is scrambled by G-RNTI or C-RNTI, and the terminal device receives the scheduling information of MBS services according to the G-RNTI or C-RNTI configured on the network side, and then receives the MBS services in unicast mode according to the scheduling information. The scheduling information of eMBB services is scrambled by C-RNTI, and the terminal device receives the scheduling information of eMBB services according to the C-RNTI configured on the network side, and then receives the eMBB services in unicast mode according to the scheduling information.

[0175] Furthermore, the network device can configure the terminal device to use a multicast key or a unicast key when receiving MBS services in unicast mode. Each logical channel identifier or each DRB identifier or each PDCP entity is associated with a key, which can be a unicast key or a multicast key, for the terminal device to decrypt the MBS service.

[0176] Example 8 (corresponding to the above situation B, and the terminal device receives the MBS service in a multicast manner)

[0177] Reference Figure 6-3 , Figure 6-3 A schematic diagram of the structure of the protocol stack on the terminal device side is shown in FIG. Figure 6-3 The description of "entity" is omitted, for example Figure 6-3 The "SDAP" in the specification refers to the "SDAP entity".

[0178] The terminal device receives the MBS service in a multicast manner according to the network side configuration, and at the same time, receives the eMBB service in a unicast manner. The MBS service and the eMBB service have independent PHY entities and MAC entities. In this case, each MAC entity has its own MAC function, such as DRX function.

[0179] The scheduling information of MBS services is scrambled by G-RNTI, and the terminal device receives the scheduling information of MBS services according to the G-RNTI configured on the network side, and then receives the MBS services by broadcast according to the scheduling information. The scheduling information of eMBB services is scrambled by C-RNTI, and the terminal device receives the scheduling information of eMBB services according to the C-RNTI configured on the network side, and then receives the eMBB services by unicast according to the scheduling information.

[0180] Example 9 (corresponding to the above situation B, and the terminal device receives the MBS service in unicast mode)

[0181] Reference Figure 6-4 , Figure 6-4 A schematic diagram of the structure of the protocol stack on the terminal device side is shown in FIG. Figure 6-4 The description of "entity" is omitted, for example Figure 6-4The "SDAP" in the specification refers to the "SDAP entity".

[0182] The terminal device receives the MBS service in unicast mode according to the network side configuration, and at the same time, receives the eMBB service in unicast mode. The MBS service and the eMBB service have independent PHY entities and MAC entities. In this case, each MAC entity has its own MAC function, such as DRX function.

[0183] The scheduling information of MBS services is scrambled by G-RNTI or C-RNTI, and the terminal device receives the scheduling information of MBS services according to the G-RNTI or C-RNTI configured on the network side, and then receives the MBS services in unicast mode according to the scheduling information. The scheduling information of eMBB services is scrambled by C-RNTI, and the terminal device receives the scheduling information of eMBB services according to the C-RNTI configured on the network side, and then receives the eMBB services in unicast mode according to the scheduling information.

[0184] Furthermore, the network device can configure the terminal device to use a multicast key or a unicast key when receiving MBS services in unicast mode. Each logical channel identifier or each DRB identifier or each PDCP entity is associated with a key, which can be a unicast key or a multicast key, for the terminal device to decrypt the MBS service.

[0185] Figure 7 This is a schematic diagram of the structure of the transmission device of the MBS service provided in the embodiment of the present application. Figure 1 , applied to network equipment (such as base stations), such as Figure 7 As shown, the transmission device of the MBS service includes:

[0186] The sending unit 701 is configured to send the MBS service in a multicast manner using a first protocol stack, and to send the MBS service in a unicast manner using a second protocol stack.

[0187] In an optional manner, the first protocol stack includes a first PHY entity, and the second protocol stack includes a second PHY entity;

[0188] The sending unit 701 is configured to use the first PHY entity to send the MBS service in a multicast manner, and use the second PHY entity to send the MBS service in a unicast manner.

[0189] In an optional manner, the first protocol stack and the second protocol stack have a common MAC entity;

[0190] The common MAC entity is used to copy the MAC PDU of the MBS service, transmit the MAC PDU to the first PHY entity, and transmit the copied MAC PDU to the second PHY entity.

[0191] In an optional manner, the first protocol stack and the second protocol stack further have at least one of the following common protocol stack entities: an SDAP entity, a PDCP entity, and an RLC entity.

[0192] In an optional manner, the first protocol stack and the second protocol stack have a common SDAP entity;

[0193] The public SDAP entity is used to copy the SDAP PDU of the MBS service, transmit the SDAP PDU to the PDCP entity or RLC entity in the first protocol stack, and transmit the copied SDAP PDU to the PDCP entity or RLC entity in the second protocol stack.

[0194] In an optional manner, the first protocol stack and the second protocol stack have independent PDCP entities and / or RLC entities.

[0195] In an optional manner, the first protocol stack and the second protocol stack have a common PDCP entity;

[0196] The public PDCP entity is used to copy the PDCP PDU of the MBS service, transmit the PDCP PDU to the RLC entity in the first protocol stack, and transmit the copied PDCP PDU to the RLC entity in the second protocol stack.

[0197] In an optional manner, the first protocol stack and the second protocol stack further have a common SDAP entity, and the first protocol stack and the second protocol stack have an independent RLC entity.

[0198] In an optional manner, the first protocol stack and the second protocol stack have a common RLC entity;

[0199] The common RLC entity is used to copy the RLC PDU of the MBS service, transmit the RLC PDU to the MAC entity in the first protocol stack, and transmit the copied RLC PDU to the MAC entity in the second protocol stack.

[0200] In an optional manner, the first protocol stack and the second protocol stack further have a common SDAP entity and / or PDCP entity.

[0201] In an optional manner, the first protocol stack and the second protocol stack have a common MAC entity;

[0202] The common MAC entity is used to map the RLC PDU corresponding to the multicast mode into the first MAC PDU, and to map the RLC PDU corresponding to the unicast mode into the second MAC PDU.

[0203] In an optional manner, the first protocol stack and the second protocol stack have independent MAC entities;

[0204] The first MAC entity in the first protocol stack is used to map the RLC PDU corresponding to the multicast mode into the first MAC PDU;

[0205] The second MAC entity in the second protocol stack is used to map the RLC PDU corresponding to the multicast mode into the second MAC PDU.

[0206] In an optional manner, the first protocol stack and the second protocol stack have independent SDAP entities, PDCP entities, RLC entities and MAC entities; or,

[0207] The first protocol stack and the second protocol stack have independent SDAP entities, RLC entities and MAC entities.

[0208] In an optional manner, the scheduling information of the MBS service sent in a multicast manner is scrambled by the G-RNTI; the scheduling information of the MBS service sent in a unicast manner is scrambled by the G-RNTI or the C-RNTI.

[0209] Those skilled in the art should understand that the relevant description of the above-mentioned MBS service transmission device in the embodiment of the present application can be understood by referring to the relevant description of the MBS service transmission method in the embodiment of the present application.

[0210] Figure 8 This is a schematic diagram of the structure of the transmission device of the MBS service provided in the embodiment of the present application. Figure 2 , applied to terminal devices such as Figure 8 As shown, the transmission device of the MBS service includes:

[0211] The receiving unit 801 is configured to receive the MBS service in a multicast or unicast manner using a first protocol stack, and receive a first type of service in a unicast manner using a second protocol stack, where the first type of service is different from the MBS service.

[0212] In an optional manner, the first protocol stack includes a first PHY entity, and the second protocol stack includes a second PHY entity;

[0213] The receiving unit 801 is configured to use the first PHY entity to receive the MBS service in a multicast manner or a unicast manner, and use the second PHY entity to receive the first type of service in a unicast manner.

[0214] In an optional manner, the first protocol stack and the second protocol stack have a common MAC entity, and the logical channel identifier of the MBS service is unique within a cell.

[0215] In an optional manner, the first protocol stack and the second protocol stack have independent MAC entities.

[0216] In an optional manner, the device further includes: a decryption unit (not shown in the figure);

[0217] When the receiving unit receives the MBS service in a multicast manner, the decryption unit decrypts the MBS service using a first key configured by a network device, where the first key is a multicast key.

[0218] In an optional manner, the first key is associated with at least one of the following: a logical channel identifier, a DRB identifier, and a PDCP entity.

[0219] In an optional manner, the device further includes: a decryption unit;

[0220] When the receiving unit receives the MBS service in a unicast manner, the decryption unit decrypts the MBS service using a second key configured by a network device, where the second key is a multicast key or a unicast key.

[0221] In an optional manner, the second key is associated with at least one of the following: a logical channel identifier, a DRB identifier, and a PDCP entity.

[0222] Those skilled in the art should understand that the relevant description of the above-mentioned MBS service transmission device in the embodiment of the present application can be understood by referring to the relevant description of the MBS service transmission method in the embodiment of the present application.

[0223] Fig. 9 900 is a schematic structural diagram of a communication device provided in an embodiment of the present application. The communication device may be a terminal device or a network device. Fig. 9 The communication device 900 shown includes a processor 910, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0224] Alternatively, if Fig. 9As shown, the communication device 900 may further include a memory 920. The processor 910 may call and run a computer program from the memory 920 to implement the method in the embodiment of the present application.

[0225] The memory 920 may be a separate device independent of the processor 910 , or may be integrated into the processor 910 .

[0226] Alternatively, if Fig. 9 As shown, the communication device 900 may further include a transceiver 930, and the processor 910 may control the transceiver 930 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.

[0227] The transceiver 930 may include a transmitter and a receiver. The transceiver 930 may further include an antenna, and the number of antennas may be one or more.

[0228] Optionally, the communication device 900 may specifically be a network device of an embodiment of the present application, and the communication device 900 may implement corresponding processes implemented by the network device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0229] Optionally, the communication device 900 may specifically be a mobile terminal / terminal device of an embodiment of the present application, and the communication device 900 may implement the corresponding processes implemented by the mobile terminal / terminal device in each method of the embodiment of the present application, which will not be described again for the sake of brevity.

[0230] Fig.10 It is a schematic structural diagram of the chip of an embodiment of the present application. Fig.10 The chip 1000 shown includes a processor 1010, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0231] Alternatively, if Fig.10 As shown, the chip 1000 may further include a memory 1020. The processor 1010 may call and run a computer program from the memory 1020 to implement the method in the embodiment of the present application.

[0232] The memory 1020 may be a separate device independent of the processor 1010 , or may be integrated into the processor 1010 .

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

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

[0235] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0236] Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0237] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

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

[0239] Among them, the terminal device 1110 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1120 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they are not repeated here.

[0240] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0241] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0242] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.

[0243] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0244] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0245] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0246] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0247] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0248] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0249] The embodiment of the present application also provides a computer program.

[0250] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods in the embodiments of the present application. For the sake of brevity, they are not described here.

[0251] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0252] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0253] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0254] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

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

[0257] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0258] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for transmitting a multimedia multicast service (MBS) service, the method comprising: The network device uses the first protocol stack to send the MBS service in a multicast manner, and uses the second protocol stack to send the MBS service in a unicast manner; The first protocol stack includes a first physical PHY entity, and the second protocol stack includes a second PHY entity; the network device uses the first PHY entity to send the MBS service in a multicast manner, and uses the second PHY entity to send the MBS service in a unicast manner; The first protocol stack and the second protocol stack have a common media access control MAC entity; wherein the common MAC entity is used to copy the MAC PDU of the MBS service, transmit the MAC PDU to the first PHY entity, and transmit the copied MAC PDU to the second PHY entity.

2. The method according to claim 1, wherein: The first protocol stack and the second protocol stack also have at least one of the following common protocol stack entities: a Service Data Adaptation Protocol SDAP entity, a Packet Data Convergence Protocol PDCP entity, and a Radio Link Control RLC entity.

3. The method according to claim 1, wherein: The first protocol stack and the second protocol stack have a common PDCP entity; The public PDCP entity is used to copy the PDCP PDU of the MBS service, transmit the PDCP PDU to the RLC entity in the first protocol stack, and transmit the copied PDCP PDU to the RLC entity in the second protocol stack.

4. The method according to claim 3, wherein: The first protocol stack and the second protocol stack also have a common SDAP entity, and the first protocol stack and the second protocol stack have an independent RLC entity.

5. The method according to any one of claims 1 to 4, wherein: The first protocol stack and the second protocol stack have a common MAC entity; The common MAC entity is used to map the RLC PDU corresponding to the multicast mode into the first MAC PDU, and to map the RLC PDU corresponding to the unicast mode into the second MAC PDU.

6. The method according to any one of claims 1 to 4, wherein: The scheduling information of the MBS service sent in a multicast manner is scrambled by the group radio network temporary identifier G-RNTI; the scheduling information of the MBS service sent in a unicast manner is scrambled by the G-RNTI or the cell radio network temporary identifier C-RNTI.

7. A method for transmitting an MBS service, the method comprising: The terminal device uses the first protocol stack to receive the MBS service in a multicast manner or a unicast manner, and uses the second protocol stack to receive the first type of service in a unicast manner, where the first type of service is different from the MBS service; The first protocol stack includes a first PHY entity, and the second protocol stack includes a second PHY entity; the terminal device uses the first PHY entity to receive the MBS service in a multicast manner or a unicast manner, and uses the second PHY entity to receive the first type of service in a unicast manner; The first protocol stack and the second protocol stack have a common MAC entity.

8. A transmission device for MBS service, the device comprising: A sending unit, configured to send the MBS service in a multicast manner using a first protocol stack, and to send the MBS service in a unicast manner using a second protocol stack; The sending unit is specifically configured to send the MBS service in a multicast manner by using the first PHY entity, and to send the MBS service in a unicast manner by using the second PHY entity, when the first protocol stack includes a first PHY entity and the second protocol stack includes a second PHY entity; The first protocol stack and the second protocol stack have a common MAC entity, and the common MAC entity is used to copy the MAC PDU of the MBS service, transmit the MAC PDU to the first PHY entity, and transmit the copied MAC PDU to the second PHY entity.

9. The device according to claim 8, wherein: The first protocol stack and the second protocol stack also have at least one of the following common protocol stack entities: an SDAP entity, a PDCP entity, and an RLC entity.

10. The device according to claim 8, wherein: The first protocol stack and the second protocol stack have a common PDCP entity; The public PDCP entity is used to copy the PDCP PDU of the MBS service, transmit the PDCP PDU to the RLC entity in the first protocol stack, and transmit the copied PDCP PDU to the RLC entity in the second protocol stack.

11. The device according to claim 10, wherein: The first protocol stack and the second protocol stack also have a common SDAP entity, and the first protocol stack and the second protocol stack have an independent RLC entity.

12. The device according to any one of claims 8 to 11, wherein: The first protocol stack and the second protocol stack have a common MAC entity; The common MAC entity is used to map the RLC PDU corresponding to the multicast mode into the first MAC PDU, and to map the RLC PDU corresponding to the unicast mode into the second MAC PDU.

13. The device according to any one of claims 8 to 11, wherein: The scheduling information of the MBS service sent in a multicast manner is scrambled by the G-RNTI; the scheduling information of the MBS service sent in a unicast manner is scrambled by the G-RNTI or the C-RNTI.

14. A transmission device for MBS service, the device comprising: a receiving unit, configured to receive the MBS service in a multicast manner or a unicast manner using a first protocol stack, and to receive a first type of service in a unicast manner using a second protocol stack, wherein the first type of service is different from the MBS service; The receiving unit, when the first protocol stack includes a first PHY entity and the second protocol stack includes a second PHY entity, is specifically configured to use the first PHY entity to receive the MBS service in a multicast manner or a unicast manner, and use the second PHY entity to receive the first type of service in a unicast manner; The first protocol stack and the second protocol stack have a common MAC entity.

Images