WO2022006882A1 - Procédé et appareil de transmission de service mbs, dispositif de réseau et dispositif terminal - Google Patents

Procédé et appareil de transmission de service mbs, dispositif de réseau et dispositif terminal Download PDF

Info

Publication number
WO2022006882A1
WO2022006882A1 PCT/CN2020/101419 CN2020101419W WO2022006882A1 WO 2022006882 A1 WO2022006882 A1 WO 2022006882A1 CN 2020101419 W CN2020101419 W CN 2020101419W WO 2022006882 A1 WO2022006882 A1 WO 2022006882A1
Authority
WO
WIPO (PCT)
Prior art keywords
protocol stack
entity
mbs service
mac
pdu
Prior art date
Application number
PCT/CN2020/101419
Other languages
English (en)
Chinese (zh)
Inventor
王淑坤
石聪
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to CN202080101106.4A priority Critical patent/CN115668992A/zh
Priority to CN202310507535.7A priority patent/CN116471552A/zh
Priority to PCT/CN2020/101419 priority patent/WO2022006882A1/fr
Publication of WO2022006882A1 publication Critical patent/WO2022006882A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services

Definitions

  • the embodiments of the present application relate to the field of mobile communication technologies, and in particular, to a method and apparatus for transmitting a media multicast service (Multimedia Broadcast Service, MBS) service, network equipment, and terminal equipment.
  • MBS Multimedia Broadcast Service
  • the base station delivers the MBS service according to the multicast mode, and also delivers the MBS service to a specific user according to the unicast mode. How to design the protocol stack to realize the simultaneous delivery of MBS services according to the multicast mode and the unicast mode needs to be solved.
  • the terminal device when the terminal device receives the MBS service, it may also receive the non-MBS service. How to design the protocol stack to realize the simultaneous reception of the MBS service and the non-MBS service needs to be solved.
  • Embodiments of the present application provide a method and apparatus for transmitting an MBS service, a network device, and a terminal device.
  • 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 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 a first type of service in a unicast manner, where the first type of service is different from the MBS service.
  • a sending unit configured to use the first protocol stack to send the MBS service in a multicast manner, and use the second protocol stack to send the MBS service in a unicast manner.
  • a receiving unit configured to use the first protocol stack to receive the MBS service in a multicast manner or a unicast manner, and use the 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 .
  • the network device provided by the embodiments of the present application includes a processor and a memory.
  • the memory is used for storing a computer program
  • the processor is used for calling and running the computer program stored in the memory to execute the above-mentioned transmission method of the MBS service.
  • the terminal device provided by the embodiments of the present application includes a processor and a memory.
  • the memory is used for storing a computer program
  • the processor is used for calling and running the computer program stored in the memory to execute the above-mentioned transmission method of the MBS service.
  • the chip provided by the embodiment of the present application is used to implement the above-mentioned transmission method of the MBS service.
  • the chip includes: a processor for invoking and running a computer program from the memory, so that the device installed with the chip executes the above-mentioned MBS service transmission method.
  • the computer-readable storage medium provided by the embodiment of the present application is used to store a computer program, and the computer program enables a computer to execute the above-mentioned method for transmitting an MBS service.
  • the computer program product provided by the embodiments of the present application includes computer program instructions, and the computer program instructions cause a computer to execute the above-mentioned method for transmitting an MBS service.
  • the computer program provided by the embodiment of the present application when it runs on the computer, causes the computer to execute the above-mentioned MBS service transmission method.
  • the base station adopts the first protocol stack to realize sending the MBS service according to the multicast mode, and adopts the second protocol stack to realize the sending of the MBS service according to the unicast mode, thereby realizing that a cell supports both the multicast mode and the unicast mode at the same time. mode to deliver MBS services.
  • the terminal device uses the first protocol stack to receive MBS services in a multicast or unicast manner, and uses the second protocol stack to receive the first type of services (ie, non-MBS services) in a unicast manner, thereby realizing The terminal equipment simultaneously receives MBS services and non-MBS services.
  • FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of the transmission of MBS services provided by an embodiment of the present application in a multicast mode and a unicast mode;
  • FIG. 3 is a schematic flowchart 1 of a method for transmitting an MBS service provided by an embodiment of the present application
  • 4-1 is a schematic structural diagram 1 of a protocol stack on the network device side provided by an embodiment of the present application;
  • 4-2 is a second schematic structural diagram of a protocol stack on the network device side provided by an embodiment of the present application.
  • 4-3 is a third schematic structural diagram of a protocol stack on the network device side provided by an embodiment of the present application.
  • 4-4 is a fourth schematic structural diagram of a protocol stack on the network device side provided by an embodiment of the present application.
  • FIGS. 4-5 are schematic structural diagrams 5 of a protocol stack on the network device side provided by an embodiment of the present application.
  • FIG. 5 is a second schematic flowchart of a method for transmitting an MBS service provided by an embodiment of the present application
  • FIG. 6-1 is a schematic structural diagram 1 of a protocol stack on a terminal device side provided by an embodiment of the present application;
  • 6-2 is a second schematic structural diagram of a protocol stack on the terminal device side provided by an embodiment of the present application.
  • FIG. 6-3 is a third schematic structural diagram of a protocol stack on the terminal device side provided by an embodiment of the present application.
  • 6-4 is a fourth schematic structural diagram of a protocol stack on the terminal device side provided by an embodiment of the present application.
  • FIG. 7 is a schematic diagram 1 of the structure and composition of an apparatus for transmitting an MBS service provided by an embodiment of the present application;
  • FIG. 8 is a schematic diagram 2 of the structure and composition of an apparatus for transmitting an MBS service provided by an embodiment of the present application;
  • FIG. 9 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • FIG. 11 is a schematic block diagram of a communication system provided by an embodiment of the present application.
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • 5G communication systems or future communication systems etc.
  • the communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal 120 (or referred to as a communication terminal, a terminal).
  • the network device 110 may provide communication coverage for a particular geographic area and may communicate with terminals located within the coverage area.
  • the network device 110 may be an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the
  • the network device can be a mobile switching center, a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a network device in a future communication system.
  • the communication system 100 also includes at least one terminal 120 located within the coverage of the network device 110 .
  • Terminal includes, but is not limited to, connections via wired lines, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connections; and/or another data connection/network; and/or via a wireless interface, e.g. for cellular networks, Wireless Local Area Networks (WLAN), digital television networks such as DVB-H networks, satellite networks, AM-FM A broadcast transmitter; and/or a device of another terminal configured to receive/transmit a communication signal; and/or an Internet of Things (IoT) device.
  • PSTN Public Switched Telephone Networks
  • DSL Digital Subscriber Line
  • WLAN Wireless Local Area Networks
  • WLAN Wireless Local Area Networks
  • digital television networks such as DVB-H networks, satellite networks, AM-FM A broadcast transmitter
  • IoT Internet of Things
  • a terminal arranged to communicate through a wireless interface may be referred to as a "wireless communication terminal", “wireless terminal” or “mobile terminal”.
  • mobile terminals include, but are not limited to, satellite or cellular telephones; Personal Communications System (PCS) terminals that may combine cellular radio telephones with data processing, facsimile, and data communications capabilities; may include radio telephones, pagers, Internet/Intranet PDAs with networking access, web browsers, memo pads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or others including radiotelephone transceivers electronic device.
  • PCS Personal Communications System
  • GPS Global Positioning System
  • a terminal may refer to an access terminal, user equipment (UE), subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device.
  • the access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in 5G networks or terminals in future evolved PLMNs, etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • direct terminal (Device to Device, D2D) communication may be performed between the terminals 120 .
  • the 5G communication system or the 5G network may also be referred to as a new radio (New Radio, NR) system or an NR network.
  • New Radio NR
  • NR New Radio
  • FIG. 1 exemplarily shows one network device and two terminals.
  • the communication system 100 may include multiple network devices, and the coverage of each network device may include other numbers of terminals. This embodiment of the present application This is not limited.
  • the communication system 100 may further include other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.
  • network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.
  • a device having a communication function in the network/system may be referred to as a communication device.
  • the communication device may include a network device 110 and a terminal 120 with a communication function, and the network device 110 and the terminal 120 may be the specific devices described above, which will not be repeated here;
  • the device may further include other devices in the communication system 100, such as other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.
  • 5G Enhanced Mobile Broadband
  • URLLC Ultra-Reliable Low-Latency Communications
  • mMTC Massive Machine-Type Communications
  • eMBB still aims at users' access to multimedia content, services and data, and its demand is growing rapidly.
  • eMBB since eMBB may be deployed in different scenarios, such as indoor, urban, rural, etc., its capabilities and requirements are also quite different, so it cannot be generalized and must be analyzed in detail in combination with specific deployment scenarios.
  • Typical applications of URLLC include: industrial automation, power automation, telemedicine operations (surgery), traffic safety assurance, etc.
  • Typical features of mMTC include: high connection density, small data volume, latency-insensitive services, low cost and long service life of the module.
  • RRC_INACTIVE Radio Resource Control
  • RRC_INACTIVE Radio Resource Control
  • RRC_IDLE state (referred to as idle state): mobility is based on terminal device cell selection and reselection, paging is initiated by the core network (Core Network, CN), and the paging area is configured by the CN. There is no terminal device context and no RRC connection on the base station side.
  • RRC_CONNECTED state (referred to as connected (connected) state for short): there is an RRC connection, and a terminal device context exists on the base station side and the terminal device side.
  • the network side knows that the location of the terminal equipment is at the specific cell level. Mobility is the mobility controlled by the network side. Unicast data can be transmitted between the terminal equipment and the base station.
  • RRC_INACTIVE state (referred to as inactive state): mobility is based on terminal equipment cell selection reselection, there is a connection between CN-NR, terminal equipment context exists on a certain base station, paging is triggered by RAN , the RAN-based paging area is managed by the RAN, and the network side knows the location of the terminal device is based on the RAN-based paging area level.
  • 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 the broadcasting and multicast.
  • 3GPP clearly proposes to enhance the support capability for downlink high-speed MBMS services, and determines the design requirements for the physical layer and air interface.
  • eMBMS evolved MBMS
  • SFN Single Frequency Network
  • MBSFN Multimedia Broadcast Multicast Service Single Frequency Network
  • MBSFN uses a uniform frequency to send service data in all cells at the same time, but To ensure synchronization between cells. In this way, the overall signal-to-noise ratio distribution of the cell can be greatly improved, and the spectral efficiency will also be greatly improved accordingly.
  • eMBMS implements service broadcast and multicast based on IP multicast protocol.
  • MBMS has only a broadcast bearer mode and no multicast bearer mode.
  • reception of MBMS services is applicable to UEs in idle state or connected state.
  • SC-PTM Single Cell Point To Multiploint
  • SC-MCCH Single Cell Multicast Control Channel
  • SC-MTCH Single Cell Multicast Transport Channel
  • SC-MCCH and SC-MTCH are mapped to downlink shared channel (Downlink-Shared Channel, DL-SCH), further, DL-SCH is mapped to physical downlink shared channel (Physical Downlink Shared Channel, PDSCH), wherein, SC - MCCH and SC-MTCH belong to logical channels, DL-SCH belongs to transport channels, and PDSCH belongs to physical channels.
  • SC-MCCH and SC-MTCH do not support hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ) operations.
  • Hybrid Automatic Repeat reQuest Hybrid Automatic Repeat reQuest
  • MBMS introduces a new system information block (System Information Block, SIB) type, namely SIB20.
  • SIB System Information Block
  • the configuration information of the SC-MCCH includes the modification period of the SC-MCCH, the repetition period of the SC-MCCH, and information such as the radio frame and subframe in which the SC-MCCH is scheduled.
  • SFN represents the system frame number of the radio frame
  • mcch-RepetitionPeriod represents the repetition period of SC-MCCH
  • mcch-Offset represents SC-MCCH offset.
  • the SC-MCCH is scheduled through the Physical Downlink Control Channel (PDCCH).
  • PDCCH Physical Downlink Control Channel
  • RNTI Radio Network Tempory Identity
  • SC-RNTI Single Cell RNTI
  • the fixed value of SC-RNTI is FFFC.
  • a new RNTI is introduced, that is, a single cell notification RNTI (Single Cell Notification RNTI, SC-N-RNTI) to identify the PDCCH (such as the notification PDCCH) used to indicate the change notification of the SC-MCCH, optionally, the SC
  • the fixed value of -N-RNTI is FFFB; further, one of the 8 bits (bits) of DCI 1C can be used to indicate the change notification.
  • the configuration information of the SC-PTM is based on the SC-MCCH configured by the SIB20, and then the SC-MCCH configures the SC-MTCH, and the SC-MTCH is used to transmit service data.
  • the SC-MCCH only transmits one message (ie, SCPTMConfiguration), which is used to configure the configuration information of the SC-PTM.
  • the configuration information of SC-PTM includes: Temporary Mobile Group Identity (TMGI), session identifier (session id), group RNTI (Group RNTI, G-RNTI), discontinuous reception (Discontinuous Reception, DRX) configuration information And the SC-PTM service information of neighboring cells, etc.
  • TMGI Temporary Mobile Group Identity
  • session id session identifier
  • group RNTI Group RNTI, G-RNTI
  • discontinuous reception discontinuous Reception
  • DRX discontinuous Reception
  • Downlink discontinuous reception of SC-PTM is controlled by the following parameters: onDurationTimerSCPTM, drx-InactivityTimerSCPTM, SC-MTCH-SchedulingCycle, and SC-MTCH-SchedulingOffset.
  • the downstream SC-PTM service is received only when the timer onDurationTimerSCPTM or drx-InactivityTimerSCPTM is running.
  • SC-PTM business continuity adopts the concept of MBMS business continuity based on SIB15, namely "SIB15+MBMSInterestIndication" mode.
  • SIB15 namely "SIB15+MBMSInterestIndication" mode.
  • the service continuity of the UE in idle state is based on the concept of frequency priority.
  • a new SIB (called the first SIB) is defined, and the first SIB includes the configuration information of the first MCCH.
  • the first MCCH is the control channel of the MBMS service.
  • An SIB is used to configure the configuration information of the control channel of the NR MBMS.
  • the control channel of the NR MBMS may also be called the NR MCCH (that is, the first MCCH).
  • the first MCCH is used to carry the first signaling, and the embodiment of this application does not limit the name of the first signaling.
  • the first signaling is signaling A
  • the first signaling includes at least one first MTCH.
  • 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 NR MBMS service data).
  • the first MCCH is used to configure the configuration information of the traffic channel of the NR MBMS.
  • the traffic channel of the NR MBMS may also be called the NR MTCH (that is, the first MTCH).
  • 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.
  • the service information corresponding to the service channel such as TMGI, session id and other identification information for identifying services.
  • 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.
  • the transmissions of the first MCCH and the first MTCH are both scheduled based on the PDCCH.
  • the RNTI used for scheduling the PDCCH of 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.
  • this embodiment of the present application does not limit the naming of the first SIB, the first MCCH, and the first MTCH.
  • 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.
  • M PDCCHs (ie, MTCH 1PDCCH, MTCH2PDCCH, ..., MTCH M PDCCH) for scheduling MTCH are configured through the MCCH, wherein the DCI carried by the MTCH n PDCCH is scheduled for transmitting the PDSCH of MTCH n (ie, MTCH n PDSCH), 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 transport channels, and PDSCH belongs to physical channels.
  • MBMS services in the above solution include but are not limited to multicast services and multicast services.
  • the embodiments of the present application are described by taking the MBS service as an example, and the description of "MBS service” may also be replaced with "multicast service” or “multicast service” or "MBMS service”.
  • the same cell needs to deliver the MBS service in the multicast mode, and may also transmit the MBS service in the unicast mode for a specific user.
  • the MBS service is transmitted for the user in a unicast manner.
  • the base station sends the MBS service to each user in unicast mode. For example, when there are few users receiving MBS service in the cell, the unicast mode is used. Sending MBS service to each user can effectively improve service transmission efficiency.
  • a shared GTP tunnel (Shared GTP tunnel) may be used between the 5G core network (5G Core network, 5GC) and the gNB.
  • the transmission of MBS services that is, both unicast services and MBS services share this GTP tunnel.
  • the gNB delivers MBS services to a multicast group in a multicast (multicast) manner, and delivers MBS services to a certain UE in a unicast (unicast) manner (UE3 is taken as an example in FIG. 2 ).
  • the multicast group includes one or more UEs (in FIG. 2 , the multicast group includes UE1 and UE2 as an example). How to design a protocol stack for transmitting MBS services in a unicast mode and in a multicast mode needs to be solved. To this end, the following technical solutions of the embodiments of the present application are proposed.
  • FIG. 3 is a schematic flowchart 1 of a method for transmitting an MBS service provided by an embodiment of the present application. As shown in FIG. 3 , the method for transmitting an MBS service includes the following steps:
  • Step 301 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 network device may be a base station, such as a gNB.
  • the network device can realize that in the same cell, the MBS service is sent according to the multicast method, and the MBS service is also sent according to the unicast method.
  • the network device sends the MBS service in a unicast manner
  • the network device can send the MBS service to the terminal device in a unicast manner.
  • the network device may also send the MBS service to one or more terminal devices in a unicast manner.
  • the scheduling information of the MBS service sent in the multicast mode is scrambled by G-RNTI; the scheduling information of the MBS service sent in the unicast mode is scrambled by G-RNTI or C-RNTI.
  • the network device uses the first protocol stack to send the MBS service in a multicast mode, and uses the second protocol stack to send the MBS service in a unicast mode.
  • the specific implementation of the protocol stack on the network device side is described below. .
  • the first protocol stack includes a first physical (PHY) entity
  • the second protocol stack includes a second PHY entity
  • the network device uses the first PHY entity to send the the MBS service
  • the second PHY entity is used to send the MBS service in a unicast manner.
  • the first protocol stack also includes other protocol stack entities.
  • the second protocol stack also includes other protocol stack entities. The following situations are explained.
  • the first protocol stack and the second protocol stack have a common media access control (Media Access Control, MAC) entity; wherein, the common MAC entity is used for duplicating the MAC PDU of the MBS service, The MAC PDU is transmitted to the first PHY entity, and the duplicated MAC PDU is transmitted to the second PHY entity.
  • Media Access Control Media Access Control
  • the first protocol stack and the second protocol stack also have at least one of the following common protocol stack entities: service data adaptation protocol (Service Data Adaptation Protocol, SDAP) entity, packet Data Convergence Protocol (Packet Data Convergence Protocol, PDCP) entity, Radio Link Control (Radio Link Control, RLC) entity.
  • service data adaptation protocol Service Data Adaptation Protocol, SDAP
  • Packet Data Convergence Protocol Packet Data Convergence Protocol
  • RLC Radio Link Control
  • the first protocol stack and the second protocol stack have a public SDAP entity; wherein, the public SDAP entity is used to replicate the SDAP PDU of the MBS service, and transmit the SDAP PDU to the first SDAP PDU.
  • the public SDAP entity is used to replicate the SDAP PDU of the MBS service, and transmit the SDAP PDU to the first SDAP PDU.
  • PDCP entity or RLC entity in a protocol stack and transmit the duplicated SDAP PDU to the PDCP entity or RLC entity in the second protocol stack.
  • the first protocol stack and the second protocol stack have independent PDCP entities and/or RLC entities.
  • 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, and transmit the PDCP PDU to the first protocol stack.
  • 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 independent RLC entities.
  • the first protocol stack and the second protocol stack have a public RLC entity; wherein, the public RLC entity is used for duplicating the RLC PDU of the MBS service, and transmitting the RLC PDU to the first protocol stack.
  • the public RLC entity is used for duplicating the RLC PDU of the MBS service, and transmitting the RLC PDU to the first protocol stack.
  • the first protocol stack and the second protocol stack also have a common SDAP entity and/or PDCP entity.
  • 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 entity and MAC entity.
  • the MAC entity on the network device side can be implemented in the following two ways:
  • 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 in the first MAC PDU, and to map the corresponding RLC PDU to the unicast mode.
  • the RLC PDU is mapped in the second MAC PDU.
  • the multicast mode and the unicast mode share a MAC entity.
  • 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.
  • MAC PDUs are only mapped to the MAC PDU.
  • 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 in 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 in the second MAC PDU.
  • Each MAC entity may use respective MAC layer functions, such as DRX functions.
  • Figure 4-1 is a schematic structural diagram of a protocol stack on the network device side.
  • entity is omitted in Figure 4-1.
  • SDAP in Figure 4-1 means " SDAP entity”.
  • the PDU session of the MBS service includes one or more QoS flows, and the one or more QoS flows of the PDU session can be mapped to one or more DRBs through the SDAP entity, wherein the mapping relationship between the QoS flow and the DRB can be a pair of 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.
  • each DRB there may be no PDCP entity or SDAP entity. That is, for each DRB, there may be a PDCP entity, or a PDCP entity+SDAP entity, or an SDAP entity.
  • the MAC entity copies each MAC PDU (that is, a TB of data) to the PHY2 entity (that is, the second PHY entity), and the original MAC PDU is sent to the PHY1 entity (that is, the first PHY entity), through the PHY1 entity in a multicast manner.
  • the MBS service is sent and the MBS service is sent in a unicast manner through the PHY2 entity.
  • the first protocol stack (that is, the protocol stack corresponding to sending MBS services in multicast mode) and the second protocol stack (that is, the protocol stack corresponding to sending MBS services in unicast mode) have the following common protocol stacks Entities: SDAP entity, PDCP entity, RLC entity and MAC entity, the first protocol stack and the second protocol stack have independent PHY entities. It should be noted that, for a common protocol stack entity, one or more of the protocol stack entities may not exist.
  • the network device does not need to implement the functions of the SDAP entity, the PDCP entity, the RLC entity, and the MAC entity twice for the same MBS session, and the terminal device can simultaneously receive the multicast MBS service and the unicast MBS service. To improve the reliability of MBS service reception.
  • Figure 4-2 is a schematic structural diagram of a protocol stack on the network device side.
  • entity is omitted in Figure 4-2.
  • SDAP in Figure 4-2 means " SDAP entity”.
  • the PDU session of the MBS service includes one or more QoS flows, and the one or more QoS flows of the PDU session can be mapped to one or more DRBs through the SDAP entity, wherein the mapping relationship between the QoS flow and the DRB can be a pair of 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.
  • each DRB there may be no PDCP entity or SDAP entity. That is, for each DRB, there may be a PDCP entity, or a PDCP entity+SDAP entity, or an SDAP entity.
  • the SDAP entity copies each SDAP PDU to the PDCP2 entity, and the original SDAP PDU is sent to the PDCP1 entity.
  • 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 sends the MBS service through the PHY1 entity in a multicast manner
  • 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 sends the MBS service in a unicast manner through the PHY2 entity .
  • the SDAP entity copies each SDAP PDU to the PDCP2 entity, and the original SDAP PDU is sent to the PDCP1 entity.
  • 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 sends the MBS service through the PHY1 entity in a multicast manner
  • 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 sends the MBS service in a unicast manner through the PHY2 entity .
  • the PDCP1 entities in FIG. 4-2 include PDCP11 entities, PDCP12 entities, . . . , PDCP1n entities, wherein different PDCP entities correspond to different DRBs (ie, correspond to different logical channels).
  • the PDCP2 entities in FIG. 4-2 include PDCP21 entities, PDCP22 entities, . . . , PDCP2n entities, wherein different PDCP entities correspond to different DRBs (ie, correspond to different logical channels).
  • the RLC1 entities in FIG. 4-2 include RLC11 entities, RLC12 entities, ..., RLC1n entities, wherein different RLC entities correspond to different DRBs (ie, correspond to different logical channels).
  • the RLC2 entities in Figure 4-2 include RLC21 entities, RLC22 entities, ..., RLC2n entities, wherein different RLC entities correspond to different DRBs (ie, correspond to different logical channels).
  • the first protocol stack that is, the protocol stack corresponding to the MBS service sent in multicast mode
  • the second protocol stack that is, the protocol stack corresponding to the MBS service sent in unicast mode
  • the following common protocol stack entities SDAP entity
  • 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, for an independent protocol stack entity, one or more of the protocol stack entities may not exist.
  • the first protocol stack that is, the protocol stack corresponding to the MBS service sent in multicast mode
  • the second protocol stack that is, the protocol stack corresponding to the MBS service sent in unicast mode
  • the following common protocol stack entities SDAP entity and MAC entity
  • the first protocol stack and the second protocol stack have independent PDCP entity, RLC entity and PHY entity. It should be noted that, for an independent protocol stack entity, one or more of the protocol stack entities may not exist.
  • the network equipment does not need to implement the same MBS service, and realize the mapping of the QoS flow to the DRB twice.
  • the network device does not need to implement the function of the MAC entity twice for the same MBS session; the complexity.
  • Figure 4-3 is a schematic structural diagram of a protocol stack on the network device side.
  • entity is omitted in Figure 4-3.
  • SDAP in Figure 4-3 means " SDAP entity”.
  • the PDU session of the MBS service includes one or more QoS flows, and the one or more QoS flows of the PDU session can be mapped to one or more DRBs through the SDAP entity, wherein the mapping relationship between the QoS flow and the DRB can be a pair of 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.
  • each DRB there may be no PDCP entity or SDAP entity. That is, for each DRB, there may be a PDCP entity, or a PDCP entity+SDAP entity, or an SDAP entity.
  • 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, the MAC1 entity transmits the corresponding MAC PDU to the PHY1 entity, and sends the MBS service through the PHY1 entity in a multicast mode; at the same time, 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 sends the MBS service in a unicast manner through the PHY2 entity.
  • the PDCP entity copies each PDCP PDU to the RLC2 entity, and the original PDCP PDU is sent to the RLC1 entity. Then, 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 sends the MBS service through the PHY1 entity in a multicast mode; at the same time, 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 sends the MBS service in a unicast manner through the PHY2 entity.
  • RLC1 entities in FIG. 4-3 include RLC11 entities, RLC12 entities, ..., RLC1n entities, wherein different RLC entities correspond to different DRBs (ie, correspond to different logical channels).
  • the RLC2 entities in FIG. 4-3 include RLC21 entities, RLC22 entities, . . . , RLC2n entities, wherein different RLC entities correspond to different DRBs (ie, correspond to different logical channels).
  • the first protocol stack that is, the protocol stack corresponding to the MBS service sent in multicast mode
  • the second protocol stack that is, the protocol stack corresponding to the MBS service sent in unicast mode
  • the following common protocol stack entities SDAP entity and PDCP entity
  • the first protocol stack and the second protocol stack have independent RLC entity, MAC entity and PHY entity. It should be noted that, for a common protocol stack entity, one or more of the protocol stack entities may not exist.
  • the first protocol stack that is, the protocol stack corresponding to the MBS service sent in multicast mode
  • the second protocol stack that is, the protocol stack corresponding to the MBS service sent in unicast mode
  • the following common protocol stack entities SDAP entity, PDCP entity and MAC entity
  • the first protocol stack and the second protocol stack have independent RLC entity and PHY entity. It should be noted that, for a common protocol stack entity, one or more of the protocol stack entities may not exist.
  • the terminal device can also receive the multicast data at the same time.
  • the MBS service in the mode and the MBS service in the unicast mode are used to improve the reliability of receiving the MBS service.
  • the network device does not need to implement the function of the MAC entity twice for the same MBS session; the complexity.
  • Figure 4-4 is a schematic structural diagram of a protocol stack on the network device side.
  • entity is omitted in Figure 4-4.
  • SDAP in Figure 4-4 means " SDAP entity”.
  • the PDU session of the MBS service includes one or more QoS flows, and the one or more QoS flows of the PDU session can be mapped to one or more DRBs through the SDAP entity, wherein the mapping relationship between the QoS flow and the DRB can be a pair of 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.
  • each DRB there may be no PDCP entity or SDAP entity. That is, for each DRB, there may be a PDCP entity, or a PDCP entity+SDAP entity, or an SDAP entity.
  • the RLC entity copies each RLC PDU to the MAC2 entity, and the original RLC PDU is sent to the MAC1 entity. Then, the MAC1 entity transmits the corresponding MAC PDU to the PHY1 entity, and sends the MBS service through the PHY1 entity in a multicast mode; at the same time, the MAC2 entity transmits the corresponding MAC PDU to the PHY2 entity, and through the PHY2 entity in a unicast mode Send MBS services.
  • the RLC entity copies each RLC PDU to the MAC entity, and the original RLC PDU is sent to the MAC entity. Then, the MAC entity transmits the corresponding MAC PDU to the PHY1 entity, and sends the MBS service through the PHY1 entity in a multicast mode; at the same time, the MAC entity transmits the corresponding MAC PDU to the PHY2 entity, and through the PHY2 entity in a unicast mode Send MBS services.
  • the first protocol stack that is, the protocol stack corresponding to the MBS service sent in multicast mode
  • the second protocol stack that is, the protocol stack corresponding to the MBS service sent in unicast mode
  • the following common protocol stack entities SDAP entity, PDCP entity and RLC entity
  • the first protocol stack and the second protocol stack have independent MAC entity and PHY entity. It should be noted that, for a common protocol stack entity, one or more of the protocol stack entities may not exist.
  • the first protocol stack (that is, the protocol stack corresponding to the MBS service sent in multicast mode) and the second protocol stack (that is, 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, the first protocol stack and the second protocol stack have independent PHY entities. It should be noted that, for a common protocol stack entity, one or more of the protocol stack entities may not exist.
  • the network device does not need to implement the functions of the SDAP entity, the PDCP entity and the RLC entity twice for the same MBS session. It should be noted that, This situation does not apply to AM RLC mode.
  • the network device does not need to implement the function of the MAC entity twice for the same MBS session; the complexity.
  • Figure 4-5 is a schematic structural diagram of a protocol stack on the network device side, the description of "entity” is omitted in Figure 4-5, for example, "SDAP” in Figure 4-5 means " SDAP entity”.
  • the PDU session of the MBS service includes one or more QoS flows, and the one or more QoS flows of the PDU session can be mapped to one or more DRBs through the SDAP entity, wherein the mapping relationship between the QoS flow and the DRB can be a pair of 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.
  • each DRB there may be no PDCP entity or SDAP entity. That is, for each DRB, there may be a PDCP entity, or a PDCP entity+SDAP entity, or an SDAP entity.
  • the QoS stream of the PDU session of the MBS service is copied, the original QoS stream is transmitted to the first protocol stack, and the copied QoS stream is transmitted to the second protocol stack.
  • the first protocol stack and the second protocol stack are completely independent and have their own protocols. stack entity.
  • the multicast mode and the unicast mode are respectively configured with independent protocol stacks, and the implementation is relatively simple.
  • FIG. 5 is a second schematic flowchart of a method for transmitting an MBS service provided by an embodiment of the present application. As shown in FIG. 5 , the method for transmitting an MBS service includes the following steps:
  • Step 501 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 a first type of service in a unicast manner, where the first type of service is different from the MBS service .
  • the terminal device when receiving an MBS service, the terminal device also receives a non-MBS service (hereinafter referred to as the first type of service), for example, the first type of service is an eMBB service.
  • the terminal equipment may receive the MBS service in a unicast manner or in a multicast manner, depending on the configuration on the network side.
  • the terminal device uses the first protocol stack to receive the MBS service in a multicast or unicast mode, and uses the second protocol stack to receive the first type of service in a unicast mode.
  • the specific implementation will be described.
  • the first protocol stack includes a first PHY entity
  • the second protocol stack includes a second PHY entity
  • the terminal device uses the first PHY entity to receive in a multicast or unicast manner the MBS service, and the second PHY entity to receive the first type of service in a unicast manner.
  • the first protocol stack also includes other protocol stack entities.
  • the second protocol stack also includes other protocol stack entities. The following situations are explained.
  • 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.
  • the first protocol stack and the second protocol stack have independent MAC entities.
  • the terminal device when the terminal device receives the MBS service in a multicast manner, the terminal device decrypts the MBS service by using the first key configured by the network device, and the first key is used to decrypt the MBS service. is the multicast key. Further, the first secret key is associated with at least one of the following: a logical channel identifier, a data radio bearer DRB identifier, and a PDCP entity.
  • the terminal device when the terminal device receives the MBS service in a unicast manner, uses the second key configured by the network device to decrypt the MBS service, and the second key is used to decrypt the MBS service. It 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.
  • Example 6 (corresponding to the above case A, and the terminal device receives the MBS service in the multicast mode)
  • Figure 6-1 is a schematic structural diagram of a protocol stack on the terminal device side.
  • entity is omitted in Figure 6-1.
  • SDAP in Figure 6-1 means " SDAP entity”.
  • the terminal device receives the MBS service through multicast according to the configuration on the network side, and at the same time, receives the eMBB service through unicast.
  • the MBS service and the eMBB service have independent PHY entities and a common MAC entity.
  • 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.
  • the scheduling information of the MBS service is scrambled by the G-RNTI, and the terminal device receives the scheduling information of the MBS service according to the G-RNTI configured on the network side, and then receives the MBS service by broadcasting according to the scheduling information.
  • the scheduling information of the eMBB service is scrambled by the C-RNTI, and the terminal device receives the scheduling information of the eMBB service according to the C-RNTI configured on the network side, and then receives the eMBB service in a unicast manner according to the scheduling information.
  • Example 7 (corresponding to the above case A, and the terminal device receives the MBS service in a unicast manner)
  • Figure 6-2 is a schematic structural diagram of a protocol stack on the terminal device side, the description of "entity” is omitted in Figure 6-2, for example, "SDAP” in Figure 6-2 means " SDAP entity”.
  • the terminal device receives the MBS service through unicast according to the configuration on the network side, and at the same time, receives the eMBB service through unicast.
  • the MBS service and the eMBB service have independent PHY entities and a common MAC entity.
  • 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.
  • the scheduling information of the MBS service is scrambled by G-RNTI or C-RNTI.
  • the terminal device receives the scheduling information of the MBS service according to the G-RNTI or C-RNTI configured on the network side, and then receives the MBS service through unicast according to the scheduling information.
  • the scheduling information of the eMBB service is scrambled by the C-RNTI, and the terminal device receives the scheduling information of the eMBB service according to the C-RNTI configured on the network side, and then receives the eMBB service in a unicast manner according to the scheduling information.
  • the network device may configure for the terminal device whether the key used when receiving the MBS service in a unicast manner is a multicast key or a unicast key.
  • each logical channel identifier or each DRB identifier or each PDCP entity is associated with a key, and the key may be a unicast key or a multicast secret, which is used by the terminal device to decrypt the MBS service.
  • Example 8 (corresponding to the above case B, and the terminal device receives the MBS service in a multicast manner)
  • Figure 6-3 is a schematic structural diagram of a protocol stack on the terminal device side.
  • entity is omitted in Figure 6-3.
  • SDAP in Figure 6-3 means " SDAP entity”.
  • the terminal device receives the MBS service through multicast according to the configuration on the network side, and at the same time, receives the eMBB service through unicast.
  • MBS service and eMBB service have independent PHY entity and MAC entity.
  • each MAC entity has its own MAC function, such as DRX function.
  • the scheduling information of the MBS service is scrambled by the G-RNTI, and the terminal device receives the scheduling information of the MBS service according to the G-RNTI configured on the network side, and then receives the MBS service by broadcasting according to the scheduling information.
  • the scheduling information of the eMBB service is scrambled by the C-RNTI, and the terminal device receives the scheduling information of the eMBB service according to the C-RNTI configured on the network side, and then receives the eMBB service in a unicast manner according to the scheduling information.
  • Example 9 (corresponding to the above case B, and the terminal device receives the MBS service in a unicast manner)
  • Figure 6-4 is a schematic structural diagram of a protocol stack on the terminal device side, the description of "entity” is omitted in Figure 6-4, for example, "SDAP” in Figure 6-4 means " SDAP entity”.
  • the terminal device receives the MBS service through unicast according to the configuration on the network side, and at the same time, receives the eMBB service through unicast.
  • MBS service and eMBB service have independent PHY entity and MAC entity.
  • each MAC entity has its own MAC function, such as DRX function.
  • the scheduling information of the MBS service is scrambled by G-RNTI or C-RNTI.
  • the terminal device receives the scheduling information of the MBS service according to the G-RNTI or C-RNTI configured on the network side, and then receives the MBS service through unicast according to the scheduling information.
  • the scheduling information of the eMBB service is scrambled by the C-RNTI, and the terminal device receives the scheduling information of the eMBB service according to the C-RNTI configured on the network side, and then receives the eMBB service in a unicast manner according to the scheduling information.
  • the network device may configure for the terminal device whether the key used when receiving the MBS service in a unicast manner is a multicast key or a unicast key.
  • each logical channel identifier or each DRB identifier or each PDCP entity is associated with a key, and the key may be a unicast key or a multicast secret, which is used by the terminal device to decrypt the MBS service.
  • FIG. 7 is a schematic diagram 1 of the structure and composition of an apparatus for transmitting an MBS service provided by an embodiment of the present application, which is applied to a network device (such as a base station).
  • a network device such as a base station.
  • the apparatus for transmitting an MBS service includes:
  • the sending unit 701 is configured to use the first protocol stack to send the MBS service in a multicast manner, and use the second protocol stack to send the MBS service in a unicast manner.
  • the first protocol stack includes a first PHY entity
  • the second protocol stack includes a second PHY entity
  • 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.
  • the first protocol stack and the second protocol stack have a common MAC entity
  • the common MAC entity is used for duplicating the MAC PDU of the MBS service, transmitting the MAC PDU to the first PHY entity, and transmitting the duplicated MAC PDU to the second PHY entity.
  • the first protocol stack and the second protocol stack also share at least one of the following protocol stack entities: SDAP entity, PDCP entity, and RLC entity.
  • the first protocol stack and the second protocol stack have a common SDAP entity
  • the public SDAP entity is used to duplicate the SDAP PDU of the MBS service, transmit the SDAP PDU to the PDCP entity or the RLC entity in the first protocol stack, and transmit the duplicated SDAP PDU to the The PDCP entity or the RLC entity in the second protocol stack.
  • the first protocol stack and the second protocol stack have independent PDCP entities and/or RLC entities.
  • the first protocol stack and the second protocol stack have a common PDCP entity
  • the public PDCP entity is used for duplicating the PDCP PDU of the MBS service, transmitting the PDCP PDU to the RLC entity in the first protocol stack, and transmitting the duplicated PDCP PDU to the second protocol RLC entities in the stack.
  • 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 independent RLC entities.
  • the first protocol stack and the second protocol stack have a common RLC entity
  • the public RLC entity is used for duplicating the RLC PDU of the MBS service, transmitting the RLC PDU to the MAC entity in the first protocol stack, and transmitting the duplicated RLC PDU to the second protocol MAC entities in the stack.
  • the first protocol stack and the second protocol stack also have a common SDAP entity and/or PDCP entity.
  • the first protocol stack and the second protocol stack have a common MAC entity
  • the common MAC entity is used for mapping the RLC PDU corresponding to the multicast mode in the first MAC PDU, and mapping the RLC PDU corresponding to the unicast mode in the second MAC PDU.
  • 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 in 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.
  • 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.
  • the scheduling information of the MBS service sent in the multicast mode is scrambled by G-RNTI; the scheduling information of the MBS service sent in the unicast mode is scrambled by G-RNTI or C-RNTI .
  • FIG. 8 is a schematic diagram 2 of the structure and composition of an apparatus for transmitting an MBS service provided by an embodiment of the present application, which is applied to a terminal device.
  • the apparatus for transmitting an MBS service includes:
  • a receiving unit 801 configured to use a first protocol stack to receive an MBS service in a multicast manner or a unicast manner, and use a second protocol stack to receive a first type of service in a unicast manner, the first type of service and the MBS service different.
  • the first protocol stack includes a first PHY entity
  • the second protocol stack includes a second PHY entity
  • 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.
  • 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.
  • the first protocol stack and the second protocol stack have independent MAC entities.
  • the apparatus further includes: a decryption unit (not shown in the figure);
  • the decryption unit decrypts the MBS service by using a first secret key configured by a network device, where the first secret key is a multicast secret key.
  • the first key is associated with at least one of the following: a logical channel identifier, a DRB identifier, and a PDCP entity.
  • the apparatus further includes: a decryption unit;
  • the decryption unit decrypts the MBS service by using a second secret key configured by the network device, where the second secret key is a multicast secret key or Unicast key.
  • the second key is associated with at least one of the following: a logical channel identifier, a DRB identifier, and a PDCP entity.
  • FIG. 9 is a schematic structural diagram of a communication device 900 provided by an embodiment of the present application.
  • the communication device may be a terminal device or a network device.
  • the communication device 900 shown in FIG. 9 includes a processor 910, and the processor 910 can call and run a computer program from a memory to implement the methods in the embodiments of the present application.
  • the communication device 900 may further include a memory 920 .
  • the processor 910 may call and run a computer program from the memory 920 to implement the methods in the embodiments of the present application.
  • the memory 920 may be a separate device independent of the processor 910 , or may be integrated in the processor 910 .
  • the communication device 900 may further include a transceiver 930, and the processor 910 may control the transceiver 930 to communicate with other devices, specifically, may send information or data to other devices, or receive other devices Information or data sent by a device.
  • the transceiver 930 may include a transmitter and a receiver.
  • the transceiver 930 may further include antennas, and the number of the antennas may be one or more.
  • the communication device 900 may specifically be the network device of the embodiment of the present application, and the communication device 900 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, details are not repeated here. .
  • the communication device 900 may specifically be the mobile terminal/terminal device in the embodiments of the present application, and the communication device 900 may implement the corresponding processes implemented by the mobile terminal/terminal device in each method in the embodiments of the present application. , and will not be repeated here.
  • FIG. 10 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • the chip 1000 shown in FIG. 10 includes a processor 1010, and the processor 1010 can call and run a computer program from a memory, so as to implement the method in the embodiment of the present application.
  • 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 methods in the embodiments of the present application.
  • the memory 1020 may be a separate device independent of the processor 1010, or may be integrated in the processor 1010.
  • the chip 1000 may further include an input interface 1030 .
  • the processor 1010 can control the input interface 1030 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.
  • the chip 1000 may further include an output interface 1040 .
  • the processor 1010 can control the output interface 1040 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
  • the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which is not repeated here for brevity.
  • the chip can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application.
  • the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application.
  • the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application.
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip, or the like.
  • FIG. 11 is a schematic block diagram of a communication system 1100 provided by an embodiment of the present application. As shown in FIG. 11 , the communication system 1100 includes a terminal device 1110 and a network device 1120 .
  • the terminal device 1110 can be used to implement the corresponding functions implemented by the terminal device in the above method
  • the network device 1120 can be used to implement the corresponding functions implemented by the network device in the above method. For brevity, details are not repeated here. .
  • the processor in this embodiment of the present application may be an integrated circuit chip, which has a signal processing capability.
  • each step of the above method embodiments may be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software.
  • the above-mentioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other available Programming logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.
  • the memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically programmable read-only memory (Erasable PROM, EPROM). Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be Random Access Memory (RAM), which acts as an external cache.
  • RAM random access memory
  • SRAM Static RAM
  • DRAM Dynamic RAM
  • SDRAM Synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • enhanced SDRAM ESDRAM
  • synchronous link dynamic random access memory Synchlink DRAM, SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.
  • Embodiments of the present application further provide a computer-readable storage medium for storing a computer program.
  • 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.
  • 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.
  • the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application. , and are not repeated here for brevity.
  • Embodiments of the present application also provide a computer program product, including computer program instructions.
  • the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. Repeat.
  • the computer program product can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, For brevity, details are not repeated here.
  • the embodiments of the present application also provide a computer program.
  • the computer program can be applied to the network device in the embodiments of the present application.
  • the computer program When the computer program is run on the computer, it causes the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity. , and will not be repeated here.
  • the computer program may be applied to the mobile terminal/terminal device in the embodiments of the present application, and when the computer program is run on the computer, the mobile terminal/terminal device implements the various methods of the computer program in the embodiments of the present application.
  • the corresponding process for the sake of brevity, will not be repeated here.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .

Landscapes

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

Abstract

Des modes de réalisation de la présente demande concernent un procédé et un appareil de transmission de service MBS, un dispositif de réseau et un dispositif terminal. Le procédé comprend les étapes suivantes : un dispositif de réseau transmet un service MBS dans un mode multidiffusion à l'aide d'une première pile de protocoles, et transmet le service MBS dans un mode monodiffusion à l'aide d'une seconde pile de protocoles.
PCT/CN2020/101419 2020-07-10 2020-07-10 Procédé et appareil de transmission de service mbs, dispositif de réseau et dispositif terminal WO2022006882A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN202080101106.4A CN115668992A (zh) 2020-07-10 2020-07-10 Mbs业务的传输方法及装置、网络设备、终端设备
CN202310507535.7A CN116471552A (zh) 2020-07-10 2020-07-10 Mbs业务的传输方法及装置、网络设备、终端设备
PCT/CN2020/101419 WO2022006882A1 (fr) 2020-07-10 2020-07-10 Procédé et appareil de transmission de service mbs, dispositif de réseau et dispositif terminal

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/101419 WO2022006882A1 (fr) 2020-07-10 2020-07-10 Procédé et appareil de transmission de service mbs, dispositif de réseau et dispositif terminal

Publications (1)

Publication Number Publication Date
WO2022006882A1 true WO2022006882A1 (fr) 2022-01-13

Family

ID=79552217

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/101419 WO2022006882A1 (fr) 2020-07-10 2020-07-10 Procédé et appareil de transmission de service mbs, dispositif de réseau et dispositif terminal

Country Status (2)

Country Link
CN (2) CN116471552A (fr)
WO (1) WO2022006882A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110505160A (zh) * 2018-05-17 2019-11-26 华为技术有限公司 一种通信方法及装置
WO2020035795A1 (fr) * 2018-08-14 2020-02-20 Nokia Technologies Oy Procédé de distribution de données de multidiffusion dans une architecture infonuagique prenant en charge 5g
WO2020131932A2 (fr) * 2018-12-17 2020-06-25 Apple Inc. Procédés de prise en charge simultanée de modes de sélection de ressources et de mécanismes de configuration pour liaison latérale de v2x nr

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110505160A (zh) * 2018-05-17 2019-11-26 华为技术有限公司 一种通信方法及装置
WO2020035795A1 (fr) * 2018-08-14 2020-02-20 Nokia Technologies Oy Procédé de distribution de données de multidiffusion dans une architecture infonuagique prenant en charge 5g
WO2020131932A2 (fr) * 2018-12-17 2020-06-25 Apple Inc. Procédés de prise en charge simultanée de modes de sélection de ressources et de mécanismes de configuration pour liaison latérale de v2x nr

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on architectural enhancements for 5G multicast-broadcast services (Release 17)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.757, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V0.4.0, 22 June 2020 (2020-06-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 157, XP051924090 *
DAVID VARGAS, JORDI J. GIMENEZ, MIKKO SäILY, DAVID NAVRáTIL, ATHUL PRASAD, FASIL B. TESEMA, PETER SANDERS, WEI GUO, DE M: "RAN Logical Architecture and Interfaces for 5G-Xcast", 28 February 2019 (2019-02-28), pages 1 - 95, XP055646813, Retrieved from the Internet <URL:http://5g-xcast.eu/wp-content/uploads/2019/03/5G-Xcast_D3.3_v2.0_web.pdf> [retrieved on 20191127] *
TENCENT: "Annex #A: MBS Control Plane and User Plane Stack", 3GPP DRAFT; S2-2003989, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Elbonia; 20200601 - 20200612, 22 May 2020 (2020-05-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051889996 *

Also Published As

Publication number Publication date
CN116471552A (zh) 2023-07-21
CN115668992A (zh) 2023-01-31

Similar Documents

Publication Publication Date Title
WO2021142647A1 (fr) Procédé et appareil de transmission de service, dispositif terminal et dispositif réseau
WO2021134316A1 (fr) Appareil et procédé de planification de service, équipement terminal et dispositif de réseau
WO2021056152A1 (fr) Appareil et procédé de configuration d&#39;informations, dispositif terminal et dispositif réseau
WO2021134298A1 (fr) Procédé et dispositif d&#39;indication de ressources et appareil de communication
WO2022056806A1 (fr) Procédé et appareil de gestion pour un service mbs, dispositif terminal et dispositif de réseau
WO2021051320A1 (fr) Procédé et appareil de transmission de données de service, dispositif de réseau et dispositif terminal
WO2021051312A1 (fr) Procédé et appareil de configuration d&#39;informations, équipement terminal et dispositif de réseau
WO2021056155A1 (fr) Appareil et procédé configuration de ressources de rétroaction, procédé de communication et dispositif de communication
WO2022141255A1 (fr) Procédé et appareil de configuration mbs, dispositif de réseau et dispositif de terminal
WO2022006849A1 (fr) Procédé et appareil de gestion d&#39;état tci de service mbs et dispositif terminal
WO2022006875A1 (fr) Procédé et appareil permettant d&#39;établir un service mbs, ainsi que dispositif terminal et dispositif de réseau
WO2021051321A1 (fr) Procédé et appareil de transmission de données de service et dispositif terminal
WO2021051319A1 (fr) Procédé et appareil de configuration drx, dispositif terminal et dispositif de réseau
WO2022141545A1 (fr) Procédé et appareil de transmission de planification de mcch, et dispositif terminal
WO2022155978A1 (fr) Procédé et appareil de configuration de service mbs, dispositif terminal et dispositif de réseau
WO2022120837A1 (fr) Procédé et appareil de planification semi-persistante pour un service mbs, dispositif terminal et dispositif réseau
WO2022141088A1 (fr) Procédé et appareil d&#39;émission de service mbs et dispositif terminal
WO2021138801A1 (fr) Procédé et appareil de transmission de service sécurisée, dispositif terminal, et dispositif réseau
WO2021142646A1 (fr) Procédé et dispositif de transmission de service, et dispositif de communication
WO2022006882A1 (fr) Procédé et appareil de transmission de service mbs, dispositif de réseau et dispositif terminal
WO2021051322A1 (fr) Procédé et appareil de configuration de bwp, dispositif terminal et dispositif de réseau
WO2021134761A1 (fr) Procédé et appareil de resélection de cellule, équipement terminal et dispositif de réseau
WO2022226937A1 (fr) Procédé et appareil de radiomessagerie mbs, dispositif de réseau et dispositif terminal
WO2022198415A1 (fr) Procédé et appareil pour améliorer la fiabilité d&#39;un mbs, dispositif terminal et dispositif de réseau
WO2022227071A1 (fr) Procédé et appareil de configuration de support, dispositif terminal et dispositif de réseau

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20944030

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20944030

Country of ref document: EP

Kind code of ref document: A1