WO2022006888A1 - 一种mbs业务的接收方法及装置、终端设备 - Google Patents
一种mbs业务的接收方法及装置、终端设备 Download PDFInfo
- Publication number
- WO2022006888A1 WO2022006888A1 PCT/CN2020/101433 CN2020101433W WO2022006888A1 WO 2022006888 A1 WO2022006888 A1 WO 2022006888A1 CN 2020101433 W CN2020101433 W CN 2020101433W WO 2022006888 A1 WO2022006888 A1 WO 2022006888A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- multicast
- unicast
- mbs service
- cell
- terminal device
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 103
- 238000001514 detection method Methods 0.000 claims abstract description 24
- 238000004590 computer program Methods 0.000 claims description 35
- 230000008569 process Effects 0.000 claims description 24
- 238000012545 processing Methods 0.000 claims description 21
- 230000003252 repetitive effect Effects 0.000 claims description 9
- 238000012790 confirmation Methods 0.000 claims description 4
- 238000007596 consolidation process Methods 0.000 claims 1
- 238000004891 communication Methods 0.000 description 43
- 238000010586 diagram Methods 0.000 description 14
- 230000005540 biological transmission Effects 0.000 description 11
- 230000001360 synchronised effect Effects 0.000 description 9
- 230000006870 function Effects 0.000 description 8
- 230000011664 signaling Effects 0.000 description 7
- 102100022734 Acyl carrier protein, mitochondrial Human genes 0.000 description 6
- 101000678845 Homo sapiens Acyl carrier protein, mitochondrial Proteins 0.000 description 6
- 230000001413 cellular effect Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000003595 spectral effect Effects 0.000 description 3
- 230000003068 static effect Effects 0.000 description 3
- 101100520018 Ceratodon purpureus PHY2 gene Proteins 0.000 description 2
- 101150005660 PHY1 gene Proteins 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000001228 spectrum Methods 0.000 description 2
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005562 fading Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 229920001690 polydopamine Polymers 0.000 description 1
- 238000001356 surgical procedure Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/04—Arrangements for maintaining operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
- H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
-
- 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 receiving a Multimedia Broadcast Service (MBS) service, and a terminal device.
- MMS Multimedia Broadcast Service
- the base station can deliver the MBS service in the multicast mode, or can also deliver the MBS service for a specific user in the unicast mode. How to improve the reliability of the terminal equipment receiving MBS services in a cell needs to be solved.
- Embodiments of the present application provide a method and apparatus for receiving an MBS service, and a terminal device.
- the terminal device receives the MBS service sent by the first cell in a unicast manner, and receives the MBS service sent by the first cell in a multicast manner;
- the terminal device combines the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the physical layer or performs repeated detection at the Packet Data Convergence Protocol (PDCP) layer.
- PDCP Packet Data Convergence Protocol
- a receiving unit configured to receive the MBS service sent by the first cell in a unicast manner, and receive the MBS service sent by the first cell in a multicast manner;
- the processing unit is configured to combine the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the physical layer or perform duplicate detection at the PDCP layer.
- the terminal device provided by the embodiments of the present application includes a processor and a memory.
- the memory is used to store a computer program
- the processor is used to call and run the computer program stored in the memory to execute the above-mentioned method for receiving an MBS service.
- the chip provided by the embodiment of the present application is used to implement the above-mentioned method for receiving an MBS service.
- the chip includes: a processor for invoking and running a computer program from the memory, so that a device installed with the chip executes the above-mentioned method for receiving an MBS service.
- the computer-readable storage medium provided by the embodiment of the present application is used to store a computer program, and the computer program enables a computer to execute the above-mentioned method for receiving 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 receiving an MBS service.
- the computer program provided by the embodiment of the present application when running on a computer, enables the computer to execute the above-mentioned method for receiving an MBS service.
- the terminal device simultaneously receives the MBS service in the unicast mode and the MBS service in the multicast mode in the first cell, and combines the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the physical layer or Repeat detection at the PDCP layer can improve the reception reliability of the MBS service.
- 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 of a method for receiving an MBS service provided by an embodiment of the present application
- FIG. 4 is a schematic structural diagram of a protocol stack on a network device side provided by an embodiment of the present application.
- FIG. 5 is a schematic diagram of a cell handover provided by an embodiment of the present application.
- FIG. 6 is a schematic structural composition diagram of an apparatus for receiving an MBS service provided by an embodiment of the present application.
- FIG. 7 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
- FIG. 8 is a schematic structural diagram of a chip according to an embodiment of the present application.
- FIG. 9 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 for scheduling MTCH are configured through MCCH (ie MTCH 1 PDCCH, MTCH 2 PDCCH, ..., MTCH M PDCCH), wherein the DCI carried by MTCH n PDCCH schedules the PDSCH used for transmitting 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 improve the reliability of the terminal equipment receiving MBS services in a cell 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 of a method for receiving an MBS service provided by an embodiment of the present application. As shown in FIG. 3 , the method for receiving an MBS service includes the following steps:
- Step 301 The terminal device receives the MBS service sent by the first cell in a unicast manner, and receives the MBS service sent by the first cell in a multicast manner.
- the first cell may refer to the current serving cell of the terminal device.
- the terminal device receives the MBS service in a unicast mode in the first cell, and at the same time, the terminal device may also receive the MBS service in a multicast mode, thereby improving the reliability of receiving the MBS service sex.
- Step 302 The terminal device combines the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the physical layer or performs repetitive detection at the PDCP layer.
- the terminal device combines the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the physical layer or performs repeated detection at the PDCP layer, which will be described separately below.
- the terminal equipment improves the reception reliability gain by combining the physical layers. Specifically, the terminal device combines the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the physical layer.
- the terminal device receives first indication information sent by the first cell, where the first indication information is used to instruct the terminal device to simultaneously receive the MBS service and multi-multicast service corresponding to the unicast mode.
- MBS service corresponding to the broadcast mode.
- the terminal device receives third indication information sent by the first cell, where the third indication information is used to instruct the terminal device to respond to the MBS service and the unicast corresponding to the unicast mode.
- the MBS services corresponding to the multicast mode are combined at the physical layer, or the repeated detection of the MBS services corresponding to the unicast mode and the MBS services corresponding to the multicast mode is performed at the PDCP layer.
- the terminal device receives the unicast transmission and multicast transmission of a certain MBS service according to the indication information (ie, the first indication information) configured by the network device, for example, the network device can display the first indication information to indicate the terminal device At the same time, the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode are received. Further, the network device further instructs the terminal device whether the unicast MBS service and the multicast MBS service received at the same time are combined at the physical layer or repeatedly received at the PDCP layer through the third indication information.
- the indication information ie, the first indication information
- the terminal device When the terminal device receives a certain MBS service in a unicast mode according to the first indication information, it simultaneously receives the MBS service in a multicast mode.
- the terminal device combines the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the physical layer according to the third indication information.
- the network device further instructs the terminal device to retain the configuration information of the multicast bearer when establishing the unicast bearer. Specifically, when the network device instructs the terminal device to receive a certain MBS service in a unicast mode, if the terminal device previously received the MBS service in a multicast mode, the terminal device establishes a unicast bearer to receive the MBS service while retaining the multicast service. Bearer configuration information. In this way, the terminal device retains the configuration information of the multicast bearer when establishing the unicast bearer based on the instruction of the network device.
- the network device may explicitly instruct the terminal device to retain the configuration information of the multicast bearer when establishing the unicast bearer, or may implicitly instruct the terminal device to retain the configuration information of the multicast bearer when establishing the unicast bearer. , which are described below.
- the terminal device receives second indication information sent by the first cell, where the second indication information is used to instruct the terminal device to retain configuration information of a multicast bearer when establishing a unicast bearer, wherein the unicast bearer
- the terminal equipment is used to receive the MBS service in a unicast manner
- the multicast bearer is used for the terminal equipment to receive the MBS service in a multicast manner.
- the implicit indication can be indicated by referring to the first indication or the second indication in the foregoing solution.
- the first indication information is used to instruct the terminal device to retain the configuration information of the multicast bearer when establishing the unicast bearer. , wherein the unicast bearer is used for the terminal equipment to receive the MBS service in a unicast manner, and the multicast bearer is used for the terminal equipment to receive the MBS service in a multicast manner.
- the transport block (Transport Block, TB) of the MBS service corresponding to the unicast mode is called a unicast TB
- the TB of the MBS service corresponding to the multicast mode is called a multicast TB.
- the premise of combining the service and the MBS service corresponding to the multicast mode at the physical layer is to associate the unicast TB and the multicast TB, that is, to associate the multicast TB and the unicast TB belonging to the same TB. It should be noted that belonging to the same TB means that the content of the TB is the same.
- Associating a unicast TB with a multicast TB can be achieved in any of the following ways.
- the scheduling information of the unicast TB of the MBS service corresponding to the unicast mode is the first scheduling information
- the scheduling information of the multicast TB of the MBS service corresponding to the multicast mode is the second scheduling information
- the unicast TB and the The multicast TB is the same TB
- the first scheduling information includes the second scheduling information
- the terminal device associates the multicast TB and the unicast TB belonging to the same TB based on the first scheduling information
- the associated multicast TBs and unicast TBs are combined at the physical layer.
- the scheduling information corresponding to the multicast TB is added to the scheduling information of the unicast TB.
- the multicast TB and the unicast TB can be associated, so that the physical layer can be combined.
- the scheduling information of the unicast TB carries the first scheduling information and the second scheduling information, wherein the first scheduling information is used to schedule the unicast TB, and the second scheduling information is used to schedule the multicast TB corresponding to the unicast TB.
- the scheduling information may associate unicast TBs with corresponding multicast TBs.
- the scheduling information of the unicast TB of the MBS service corresponding to the unicast mode is the first scheduling information
- the scheduling information of the multicast TB of the MBS service corresponding to the multicast mode is the second scheduling information
- the unicast TB and the The multicast TBs are the same TB
- the first scheduling information includes first identification information
- the second scheduling information includes second identification information
- the first identification information and the second identification information have an associated relationship
- the terminal device associates the multicast TB and the unicast TB belonging to the same TB based on the first identification information and the second identification information, and associates the associated multicast TB and the unicast TB in the physical layer. Merge.
- an indication information is added to the scheduling information of the unicast TB, and an indication information is also added to the scheduling information of the multicast TB corresponding to the unicast TB, and the unicast TB and the multicast TB are associated by these two indication information, Thus, the associated multicast TBs and unicast TBs are combined at the physical layer.
- the indication information in the scheduling information of the unicast TB and the multicast TB is a bit stream, or an integer value, or an information stamp. If the indication information in the two scheduling information is the same, the TBs corresponding to the two scheduling information can be associated merged together at the physical layer.
- the network device can use the protocol stack architecture shown in Figure 4 to ensure that the content of the unicast TB and the multicast TB is the same (or the network device ensures that the unicast group packet and the multicast group package, is for the same TB).
- FIG. 4 is a schematic structural diagram of a protocol stack on the network device side.
- entity is omitted in FIG. 4 .
- SDAP in FIG. 4 represents “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, and the original MAC PDU is sent to the PHY1 entity.
- the PHY1 entity sends the MBS service in a multicast mode and the PHY2 entity sends the MBS service in a unicast mode. .
- the terminal device associates the unicast TB and the multicast TB belonging to the same TB according to the serial number (Serial Number, SN) associated with the unicast TB and the SN associated with the multicast TB.
- serial Number Serial Number, SN
- unicast TB1 is associated with SN1
- unicast TB2 is associated with SN2
- unicast TB3 is associated with SN3
- multicast TB1 is associated with SN1
- multicast TB2 is associated with SN2
- multicast TB3 is associated with SN3.
- unicast TB1 and multicast TB1 can be associated
- unicast TB2 and multicast TB2 can be associated
- unicast TB3 and multicast TB3 can be associated.
- the terminal device determines the feedback information of the unicast mode based on the reception conditions of the associated unicast TB and the multicast TB. Specifically, if the terminal device successfully receives at least one of the unicast TB and the multicast TB, the terminal device replies a positive confirmation message for the unicast mode; wherein the unicast TB refers to The TB of the MBS service corresponding to the unicast mode, the multicast TB refers to the TB of the MBS service corresponding to the multicast mode, and the unicast TB and the multicast TB are the same TB.
- the TB is associated with an SN, and the SN is carried in at least one of the following: the scheduling information of the TB, the MAC CE of the MAC PDU where the TB is located, and the MAC header of the MAC PDU where the TB is located. .
- the terminal device when a certain TB is successfully received through multicast, but fails to be received through unicast, the terminal device performs feedback according to an affirmative acknowledgment (ACK) in the HARQ feedback of unicast.
- ACK affirmative acknowledgment
- the terminal device when a certain TB is successfully received in a unicast manner, but fails to be received in a multicast manner, the terminal device performs feedback according to an affirmative acknowledgment (ACK) in the HARQ feedback in the unicast manner.
- ACK affirmative acknowledgment
- the terminal device when a certain TB is successfully received in a unicast manner and successfully received in a multicast manner, the terminal device performs feedback according to an affirmative acknowledgment (ACK) in the HARQ feedback in the unicast manner.
- ACK affirmative acknowledgment
- the terminal device when a certain TB succeeds and fails in the unicast mode, and fails to receive in the multicast mode, the terminal device performs feedback according to a negative acknowledgement (NACK) in the HARQ feedback in the unicast mode.
- NACK negative acknowledgement
- the terminal device will feed back an ACK; if both the unicast TB and the multicast TB fail to receive, the terminal device will feed back a NACK.
- unnecessary unicast retransmission can be avoided, that is, the probability of unicast retransmission can be reduced, and the spectral efficiency can be improved.
- the terminal device simultaneously receives the MBS service in the unicast mode and the MBS service in the multicast mode in one cell, and combines the MBS service in the unicast mode and the MBS service in the multicast mode at the physical layer, The receiving reliability of the MBS service is improved.
- the terminal equipment improves reception reliability by repeating reception at the PDCP layer. Specifically, the terminal device performs repetitive detection at the PDCP layer on the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode.
- the terminal device receives first indication information sent by the first cell, where the first indication information is used to instruct the terminal device to simultaneously receive the MBS service and multi-multicast service corresponding to the unicast mode.
- MBS service corresponding to the broadcast mode.
- the terminal device receives third indication information sent by the first cell, where the third indication information is used to instruct the terminal device to respond to the MBS service and the unicast corresponding to the unicast mode.
- the MBS services corresponding to the multicast mode are combined at the physical layer, or the repeated detection of the MBS services corresponding to the unicast mode and the MBS services corresponding to the multicast mode is performed at the PDCP layer.
- the terminal device receives the unicast transmission and multicast transmission of a certain MBS service according to the indication information (ie, the first indication information) configured by the network device.
- the network device can display the first indication information to indicate the terminal device
- the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode are received.
- the network device also instructs the terminal device whether the unicast MBS service and the multicast MBS service received at the same time are combined at the physical layer or repeatedly received at the PDCP layer through the third indication information.
- the terminal device When the terminal device receives a certain MBS service in a unicast mode according to the first indication information, it simultaneously receives the MBS service in a multicast mode.
- the terminal device combines the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the physical layer according to the third indication information.
- the network device further instructs the terminal device to retain the configuration information of the multicast bearer when establishing the unicast bearer. Specifically, when the network device instructs the terminal device to receive a certain MBS service in a unicast mode, if the terminal device previously received the MBS service in a multicast mode, the terminal device establishes a unicast bearer to receive the MBS service while retaining the multicast service. Bearer configuration information. In this way, the terminal device retains the configuration information of the multicast bearer when establishing the unicast bearer based on the instruction of the network device.
- the network device may explicitly instruct the terminal device to retain the configuration information of the multicast bearer when establishing the unicast bearer, or may implicitly instruct the terminal device to retain the configuration information of the multicast bearer when establishing the unicast bearer. , which are described below.
- the terminal device receives second indication information sent by the first cell, where the second indication information is used to instruct the terminal device to retain configuration information of a multicast bearer when establishing a unicast bearer, wherein the unicast bearer
- the terminal equipment is used to receive the MBS service in a unicast manner
- the multicast bearer is used for the terminal equipment to receive the MBS service in a multicast manner.
- the implicit indication can be indicated by referring to the first indication or the second indication in the foregoing solution.
- the first indication information is used to instruct the terminal device to retain the configuration information of the multicast bearer when establishing the unicast bearer. , wherein the unicast bearer is used for the terminal equipment to receive the MBS service in a unicast manner, and the multicast bearer is used for the terminal equipment to receive the MBS service in a multicast manner.
- the terminal device performs repetitive detection at the PDCP layer on the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode according to the SN associated with the MBS service data.
- the terminal device simultaneously receives the unicast MBS service and the multicast MBS service in one cell, and performs repetitive detection on the unicast MBS service and the multicast MBS service at the PDCP layer. , which improves the receiving reliability of MBS services.
- the terminal device considering the mobility of the terminal device, there may be a scenario where the terminal device switches from the first cell to the second cell.
- the following describes how the terminal device receives the MBS service in this scenario.
- the terminal device in the process of switching from the first cell to the second cell, retains the multicast configuration information of the MBS service on the side of the first cell.
- the terminal device maintains the multicast configuration information about the MBS service on the original side (ie, the first cell side).
- the terminal device simultaneously receives the multicast data sent by the first cell in the process of switching from the first cell to the second cell and/or after switching to the second cell.
- the MBS service and the MBS service sent by the second cell in a multicast mode and/or a unicast mode; the terminal device repeatedly detects the received MBS service according to the SN associated with the MBS service data.
- the terminal device still simultaneously receives the transmission of the MBS service in the target cell (ie the second cell) and the transmission of the MBS service from the original side (ie the first cell side).
- the terminal device performs repeated detection on the received MBS service according to the SN associated with the MBS service data.
- the terminal device releases the multicast configuration information of the MBS service on the side of the first cell and stops receiving the multicast configuration information sent by the first cell when the target condition is met.
- the target condition includes at least one of the following: 1. The terminal device can successfully receive the MBS service of the second cell; 2. The terminal device detects the MBS service of the first cell The signal quality is below the specified threshold.
- the terminal device itself decides to release the multicast configuration information about the MBS service on the original side (ie, the first cell side), and stops receiving the MBS service on the original side.
- the terminal device can successfully receive the MBS service of the target cell (ie the second cell), and in the absence of an SN gap, release the multicast configuration information about the MBS service on the original side (ie the first cell side), and Stop receiving MBS services on the original side.
- the terminal device detects that the signal quality of the original side (ie, the first cell side) is lower than a certain threshold, it releases the original side multicast configuration information about the MBS service, and stops receiving the original side MBS service.
- the network architectures of the first cell and the second cell may be implemented in the following manners:
- the first cell and the second cell have independent distributed units (Distributed Unit, DU), and have the same centralized unit (Centralized Unit, CU).
- DU distributed Unit
- CU Centralized Unit
- the protocol stack entities implemented by the DU include: an RLC entity, a MAC entity, a MAC entity and a PHY entity.
- the protocol stack entities implemented by the CU include: an RRC entity and a PDCP entity.
- the first cell and the second cell implement an intra-CU scenario.
- the first cell and the second cell belong to the same MBS area, and the base station corresponding to the first cell and the base station corresponding to the second cell share an anchor point, and the anchor point is used to generate MBS services
- the PDCP PDU is forwarded to all base stations in the MBS area.
- the above technical solutions of the embodiments of the present application realize that the terminal device receives the MBS service during the handover process, while improving the receiving reliability of the MBS service, and can reduce the packet loss rate to ensure the continuity of the MBS service.
- FIG. 6 is a schematic structural composition diagram of an apparatus for receiving an MBS service provided by an embodiment of the present application, which is applied to a terminal device.
- the apparatus for receiving an MBS service includes:
- a receiving unit 601 configured to receive an MBS service sent by a first cell in a unicast manner, and receive an MBS service sent by the first cell in a multicast manner;
- the processing unit 602 is configured to combine the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode at the physical layer or perform duplicate detection at the PDCP layer.
- the receiving unit 601 is further configured to receive first indication information sent by the first cell, where the first indication information is used to instruct the terminal device to simultaneously receive the MBS corresponding to the unicast manner The service and the MBS service corresponding to the multicast mode.
- the first indication information is further used to instruct the terminal device to retain configuration information of a multicast bearer when establishing a unicast bearer, wherein the unicast bearer is used by the terminal device to follow the unicast bearer.
- the multicast bearer is used for the terminal device to receive the MBS service in a multicast manner.
- the receiving unit 601 is further configured to receive second indication information sent by the first cell, where the second indication information is used to instruct the terminal device to reserve multicast when establishing a unicast bearer Configuration information of the bearer, wherein the unicast bearer is used for the terminal device to receive the MBS service in a unicast manner, and the multicast bearer is used for the terminal device to receive the MBS service in a multicast manner.
- the receiving unit 601 is further configured to receive third indication information sent by the first cell, where the third indication information is used to instruct the terminal device to The MBS service and the MBS service corresponding to the multicast mode are combined at the physical layer, or the repeated detection is performed at the PDCP layer for the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode.
- the scheduling information of the unicast TB of the MBS service corresponding to the unicast mode is the first scheduling information
- the scheduling information of the multicast TB of the MBS service corresponding to the multicast mode is the second scheduling information
- the unicast TB and the multicast TB are the same TB
- the first scheduling information includes the second scheduling information
- the processing unit 602 is configured to associate the multicast TB and the unicast TB belonging to the same TB based on the first scheduling information, and combine the associated multicast TB and the unicast TB at the physical layer.
- the scheduling information of the unicast TB of the MBS service corresponding to the unicast mode is the first scheduling information
- the scheduling information of the multicast TB of the MBS service corresponding to the multicast mode is the second scheduling information
- the unicast TB and the multicast TB are the same TB
- the first scheduling information includes first identification information
- the second scheduling information includes second identification information
- the identification information has an associated relationship;
- the processing unit 602 is configured to associate the multicast TB and the unicast TB belonging to the same TB based on the first identification information and the second identification information, and associate the associated multicast TB with the unicast TB.
- TB is merged at the physical layer.
- the device further includes:
- a sending unit (not shown in the figure), configured to reply a positive confirmation message for the unicast mode if the receiving unit successfully receives at least one of the unicast TB and the multicast TB; wherein the The unicast TB refers to the TB of the MBS service corresponding to the unicast mode, the multicast TB refers to the TB of the MBS service corresponding to the multicast mode, and the unicast TB and the multicast TB are the same TB .
- the TB is associated with an SN, and the SN is carried in at least one of the following: scheduling information of the TB, the MAC CE of the MAC PDU where the TB is located, and the MAC PDU where the TB is located.
- MAC header is carried in at least one of the following: scheduling information of the TB, the MAC CE of the MAC PDU where the TB is located, and the MAC PDU where the TB is located.
- the processing unit 602 is further configured to associate the unicast TB and the multicast TB belonging to the same TB according to the SN associated with the unicast TB and the SN associated with the multicast TB, and based on the association The reception conditions of the unicast TB and the multicast TB determine the feedback information of the unicast mode.
- the processing unit 602 is configured to perform repetitive detection at the PDCP layer on the MBS service corresponding to the unicast mode and the MBS service corresponding to the multicast mode according to the SN associated with the MBS service data.
- the processing unit 602 is further configured to retain the multicast configuration information of the MBS service on the side of the first cell during the handover process of the terminal device from the first cell to the second cell.
- the receiving unit 601 is configured to simultaneously receive the first cell according to the process of and/or after the terminal equipment is handed over from the first cell to the second cell.
- the processing unit 602 is configured to perform repetitive detection on the received MBS service according to the SN associated with the MBS service data.
- processing unit 602 is further configured to release the multicast configuration information of the MBS service on the first cell side when it is determined that the target condition is met;
- the receiving unit 601 is further configured to stop receiving the MBS service sent by the first cell in a multicast manner.
- the target condition includes at least one of the following:
- the terminal device can successfully receive the MBS service of the second cell
- the terminal device detects that the signal quality of the MBS service of the first cell is lower than a specified threshold.
- the first cell and the second cell have independent DUs and have the same CU.
- the first cell and the second cell belong to the same MBS area, and the base station corresponding to the first cell and the base station corresponding to the second cell share an anchor point, and the anchor point
- the PDCP PDU used to generate the MBS service is forwarded to all base stations in the MBS area.
- FIG. 7 is a schematic structural diagram of a communication device 700 provided by an embodiment of the present application.
- the communication device may be a terminal device or a network device.
- the communication device 700 shown in FIG. 7 includes a processor 710, and the processor 710 can call and run a computer program from a memory to implement the methods in the embodiments of the present application.
- the communication device 700 may further include a memory 720 .
- the processor 710 may call and run a computer program from the memory 720 to implement the methods in the embodiments of the present application.
- the memory 720 may be a separate device independent of the processor 710 , or may be integrated in the processor 710 .
- the communication device 700 may further include a transceiver 730, and the processor 710 may control the transceiver 730 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 processor 710 may control the transceiver 730 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 730 may include a transmitter and a receiver.
- the transceiver 730 may further include antennas, and the number of the antennas may be one or more.
- the communication device 700 may specifically be the network device in this embodiment of the present application, and the communication device 700 may implement the corresponding processes implemented by the network device in each method in the embodiment of the present application. For the sake of brevity, details are not repeated here. .
- the communication device 700 may specifically be the mobile terminal/terminal device of the embodiments of the present application, and the communication device 700 may implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, for the sake of brevity. , and will not be repeated here.
- FIG. 8 is a schematic structural diagram of a chip according to an embodiment of the present application.
- the chip 800 shown in FIG. 8 includes a processor 810, and the processor 810 can call and run a computer program from a memory, so as to implement the methods in the embodiments of the present application.
- the chip 800 may further include a memory 820 .
- the processor 810 may call and run a computer program from the memory 820 to implement the methods in the embodiments of the present application.
- the memory 820 may be a separate device independent of the processor 810 , or may be integrated in the processor 810 .
- the chip 800 may further include an input interface 830 .
- the processor 810 may control the input interface 830 to communicate with other devices or chips, and specifically, may acquire information or data sent by other devices or chips.
- the chip 800 may further include an output interface 840 .
- the processor 810 may control the output interface 840 to communicate with other devices or chips, and specifically, may 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-chip, or a system-on-a-chip, or the like.
- FIG. 9 is a schematic block diagram of a communication system 900 provided by an embodiment of the present application. As shown in FIG. 9 , the communication system 900 includes a terminal device 910 and a network device 920 .
- the terminal device 910 can be used to implement the corresponding functions implemented by the terminal device in the above method
- the network device 920 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 can be directly embodied as being executed by a hardware decoding processor, or 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 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)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请实施例提供一种MBS业务的接收方法及装置、终端设备,该方法包括:终端设备接收第一小区按照单播方式发送的MBS业务,以及接收所述第一小区按照多播方式发送的MBS业务;所述终端设备对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在物理层进行合并或者在分组数据汇聚协议PDCP层进行重复检测。
Description
本申请实施例涉及移动通信技术领域,具体涉及一种多媒体多播服务(Multimedia Broadcast Service,MBS)业务的接收方法及装置、终端设备。
在一个小区中,基站可以按照组播方式下发MBS业务,也可以按照单播方式为某个特定的用户下发MBS业务。如何提高终端设备在一个小区里接收MBS业务的可靠性需要解决。
发明内容
本申请实施例提供一种MBS业务的接收方法及装置、终端设备。
本申请实施例提供的MBS业务的接收方法,包括:
终端设备接收第一小区按照单播方式发送的MBS业务,以及接收所述第一小区按照多播方式发送的MBS业务;
所述终端设备对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在物理层进行合并或者在分组数据汇聚协议(Packet Data Convergence Protocol,PDCP)层进行重复检测。
本申请实施例提供的MBS业务的接收装置,包括:
接收单元,用于接收第一小区按照单播方式发送的MBS业务,以及接收所述第一小区按照多播方式发送的MBS业务;
处理单元,用于对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在物理层进行合并或者在PDCP层进行重复检测。
本申请实施例提供的终端设备,包括处理器和存储器。该存储器用于存储计算机程序,该处理器用于调用并运行该存储器中存储的计算机程序,执行上述的MBS业务的接收方法。
本申请实施例提供的芯片,用于实现上述的MBS业务的接收方法。
具体地,该芯片包括:处理器,用于从存储器中调用并运行计算机程序,使得安装有该芯片的设备执行上述的MBS业务的接收方法。
本申请实施例提供的计算机可读存储介质,用于存储计算机程序,该计算机程序使得计算机执行上述的MBS业务的接收方法。
本申请实施例提供的计算机程序产品,包括计算机程序指令,该计算机程序指令使得计算机执行上述的MBS业务的接收方法。
本申请实施例提供的计算机程序,当其在计算机上运行时,使得计算机执行上述的MBS业务的接收方法。
通过上述技术方案,终端设备在第一小区同时接收单播方式的MBS业务以及多播方式的MBS业务,通过对单播方式对应的MBS业务和多播方式对应的MBS业务在物理层进行合并或者在PDCP层进行重复检测,可以提高MBS业务的接收可靠性。
此处所说明的附图用来提供对本申请的进一步理解,构成本申请的一部分,本申请的示意性实施例及其说明用于解释本申请,并不构成对本申请的不当限定。在附图中:
图1是本申请实施例提供的一种通信系统架构的示意性图;
图2是本申请实施例提供的MBS业务按照多播方式和单播方式传输的示意图;
图3是本申请实施例提供的MBS业务的接收方法的流程示意;
图4是本申请实施例提供的网络设备侧的协议栈的结构示意图;
图5是本申请实施例提供的小区切换的示意图;
图6是本申请实施例提供的MBS业务的接收装置的结构组成示意图;
图7是本申请实施例提供的一种通信设备示意性结构图;
图8是本申请实施例的芯片的示意性结构图;
图9是本申请实施例提供的一种通信系统的示意性框图。
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行描述,显然,所描述的实施例是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本申请保护的范围。
本申请实施例的技术方案可以应用于各种通信系统,例如:长期演进(Long Term Evolution,LTE)系统、LTE频分双工(Frequency Division Duplex,FDD)系统、LTE时分双工(Time Division Duplex,TDD)、系统、5G通信系统或未来的通信系统等。
示例性的,本申请实施例应用的通信系统100如图1所示。该通信系统100可以包括网络设备110,网络设备110可以是与终端120(或称为通信终端、终端)通信的设备。网络设备110可以为特定的地理区域提供通信覆盖,并且可以与位于该覆盖区域内的终端进行通信。可选地,该网络设备110可以是LTE系统中的演进型基站(Evolutional Node B,eNB或eNodeB),或者是云无线接入网络(Cloud Radio Access Network,CRAN)中的无线控制器,或者该网络设备可以为移动交换中心、中继站、接入点、车载设备、可穿戴设备、集线器、交换机、网桥、路由器、5G网络中的网络侧设备或者未来通信系统中的网络设备等。
该通信系统100还包括位于网络设备110覆盖范围内的至少一个终端120。作为在此使用的“终端”包括但不限于经由有线线路连接,如经由公共交换电话网络(Public Switched Telephone Networks,PSTN)、数字用户线路(Digital Subscriber Line,DSL)、数字电缆、直接电缆连接;和/或另一数据连接/网络;和/或经由无线接口,如,针对蜂窝网络、无线局域网(Wireless Local Area Network,WLAN)、诸如DVB-H网络的数字电视网络、卫星网络、AM-FM广播发送器;和/或另一终端的被设置成接收/发送通信信号的装置;和/或物联网(Internet of Things,IoT)设备。被设置成通过无线接口通信的终端可以被称为“无线通信终端”、“无线终端”或“移动终端”。移动终端的示例包括但不限于卫星或蜂窝电话;可以组合蜂窝无线电电话与数据处理、传真以及数据通信能力的个人通信系统(Personal Communications System,PCS)终端;可以包括无线电电话、寻呼机、因特网/内联网接入、Web浏览器、记事簿、日历以及/或全球定位系统(Global Positioning System,GPS)接收器的PDA;以及常规膝上型和/或掌上型接收器或包括无线电电话收发器的其它电子装置。终端可以指接入终端、用户设备(User Equipment,UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol,SIP)电话、无线本地环路(Wireless Local Loop,WLL)站、个人数字处理(Personal Digital Assistant,PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、5G网络中的终端或者未来演进的PLMN中的终端等。
可选地,终端120之间可以进行终端直连(Device to Device,D2D)通信。
可选地,5G通信系统或5G网络还可以称为新无线(New Radio,NR)系统或NR网络。
图1示例性地示出了一个网络设备和两个终端,可选地,该通信系统100可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端,本申请实施例对此不做限定。
可选地,该通信系统100还可以包括网络控制器、移动管理实体等其他网络实体,本申请实施例对此不作限定。
应理解,本申请实施例中网络/系统中具有通信功能的设备可称为通信设备。以图1示出的通信系统100为例,通信设备可包括具有通信功能的网络设备110和终端120,网络设备110和终端120可以为上文所述的具体设备,此处不再赘述;通信设备还可包括通信系统100中的其他设备,例如网络控制器、移动管理实体等其他网络实体,本申请实施例中对此不做限定。
应理解,本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”,仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。另外,本文中字符“/”,一般表示前后关联对象是一种“或” 的关系。
为便于理解本申请实施例的技术方案,以下对本申请实施例相关的技术方案进行说明。
随着人们对速率、延迟、高速移动性、能效的追求以及未来生活中业务的多样性、复杂性,为此第三代合作伙伴计划(3
rd Generation Partnership Project,3GPP)国际标准组织开始研发5G。5G的主要应用场景为:增强移动超宽带(enhanced Mobile Broadband,eMBB)、低时延高可靠通信(Ultra-Reliable Low-Latency Communications,URLLC)、大规模机器类通信(massive Machine-Type Communications,mMTC)。
一方面,eMBB仍然以用户获得多媒体内容、服务和数据为目标,其需求增长十分迅速。另一方面,由于eMBB可能部署在不同的场景中,例如室内,市区,农村等,其能力和需求的差别也比较大,所以不能一概而论,必须结合具体的部署场景详细分析。URLLC的典型应用包括:工业自动化,电力自动化,远程医疗操作(手术),交通安全保障等。mMTC的典型特点包括:高连接密度,小数据量,时延不敏感业务,模块的低成本和长使用寿命等。
在NR早期部署时,完整的NR覆盖很难获取,所以典型的网络覆盖是广域的LTE覆盖和NR的孤岛覆盖模式。而且大量的LTE部署在6GHz以下,可用于5G的6GHz以下频谱很少。所以NR必须研究6GHz以上的频谱应用,而高频段覆盖有限、信号衰落快。同时为了保护移动运营商前期在LTE投资,提出了LTE和NR之间紧耦合(tight interworking)的工作模式。
5G为了降低空口信令和快速恢复无线连接,快速恢复数据业务的目的,定义了一个新的无线资源控制(Radio Resource Control,RRC)状态,即RRC非激活(RRC_INACTIVE)状态。这种状态有别于RRC空闲(RRC_IDLE)状态和RRC激活(RRC_ACTIVE)状态。其中,
1)RRC_IDLE状态(简称为空闲(idle)态):移动性为基于终端设备的小区选择重选,寻呼由核心网(Core Network,CN)发起,寻呼区域由CN配置。基站侧不存在终端设备上下文,不存在RRC连接。
2)RRC_CONNECTED状态(简称为连接(connected)态):存在RRC连接,基站侧和终端设备侧存在终端设备上下文。网络侧知道终端设备的位置是具体小区级别的。移动性是网络侧控制的移动性。终端设备和基站之间可以传输单播数据。
3)RRC_INACTIVE状态(简称为非激活(inactive)态):移动性为基于终端设备的小区选择重选,存在CN-NR之间的连接,终端设备上下文存在某个基站上,寻呼由RAN触发,基于RAN的寻呼区域由RAN管理,网络侧知道终端设备的位置是基于RAN的寻呼区域级别的。
MBMS是一种通过共享网络资源从一个数据源向多个UE传送数据的技术,该技术在提供多媒体业务的同时能有效地利用网络资源,实现较高速率(如256kbps)的多媒体业务的广播和组播。
由于MBMS频谱效率较低,不足以有效地承载和支撑手机电视类型业务的运营。因此在LTE中,3GPP明确提出增强对下行高速MBMS业务的支持能力,并确定了对物理层和空中接口的设计要求。
3GPP R9将演进的MBMS(evolved MBMS,eMBMS)引入到LTE中。eMBMS提出了单频率网络(Single Frequency Network,SFN)的概念,即多媒体广播多播服务单频率网络(Multimedia Broadcast multicast service Single Frequency Network,MBSFN),MBSFN采用统一频率在所有小区同时发送业务数据,但是要保证小区间的同步。这种方式可以极大的提高小区整体信噪比分布,频谱效率也会相应的大幅提高。eMBMS基于IP多播协议实现业务的广播和多播。
在LTE或增强的LTE(LTE-Advanced,LTE-A)中,MBMS只有广播承载模式,没有多播承载模式。此外,MBMS业务的接收适用于空闲态或者连接态的UE。
3GPP R13中引入了单小区点对多点(Single Cell Point To Multiploint,SC-PTM)概念,SC-PTM基于MBMS网络架构。
MBMS引入了新的逻辑信道,包括单小区多播控制信道(Single Cell-Multicast Control Channel,SC-MCCH)和单小区多播传输信道(Single Cell-Multicast Transport Channel,SC-MTCH)。SC-MCCH和SC-MTCH被映射到下行共享信道(Downlink-Shared Channel,DL-SCH)上,进一步,DL-SCH被映射到物理下行共享信道(Physical Downlink Shared Channel,PDSCH)上,其中,SC-MCCH和SC-MTCH属于逻辑信道,DL-SCH属于传输信道,PDSCH属于物理信道。SC-MCCH和SC-MTCH不支持混合自动重传请求(Hybrid Automatic Repeat reQuest,HARQ)操作。
MBMS引入了新的系统信息块(System Information Block,SIB)类型,即SIB20。具体地,通 过SIB20来传输SC-MCCH的配置信息,一个小区只有一个SC-MCCH。SC-MCCH的配置信息包括:SC-MCCH的修改周期、SC-MCCH的重复周期、以及调度SC-MCCH的无线帧和子帧等信息。进一步,1)SC-MCCH的修改周期的边界满足SFN mod m=0,其中,SFN代表边界的系统帧号,m是SIB20中配置的SC-MCCH的修改周期(即sc-mcch-ModificationPeriod)。2)调度SC-MCCH的无线帧满足:SFN mod mcch-RepetitionPeriod=mcch-Offset,其中,SFN代表无线帧的系统帧号,mcch-RepetitionPeriod代表SC-MCCH的重复周期,mcch-Offset代表SC-MCCH的偏移量。3)调度SC-MCCH的子帧通过sc-mcch-Subframe指示。
SC-MCCH通过物理下行控制信道(Physical Downlink Control Channel,PDCCH)调度。一方面,引入新的无线网络临时标识(Radio Network Tempory Identity,RNTI),即单小区RNTI(Single Cell RNTI,SC-RNTI)来识别用于调度SC-MCCH的PDCCH(如SC-MCCH PDCCH),可选地,SC-RNTI固定取值为FFFC。另一方面,引入新的RNTI,即单小区通知RNTI(Single Cell Notification RNTI,SC-N-RNTI)来识别用于指示SC-MCCH的变更通知的PDCCH(如通知PDCCH),可选地,SC-N-RNTI固定取值为FFFB;进一步,可以用DCI 1C的8个比特(bit)中的一个bit来指示变更通知。在LTE中,SC-PTM的配置信息基于SIB20配置的SC-MCCH,然后SC-MCCH配置SC-MTCH,SC-MTCH用于传输业务数据。
具体地,SC-MCCH只传输一个消息(即SCPTMConfiguration),该消息用于配置SC-PTM的配置信息。SC-PTM的配置信息包括:临时移动组标识(Temporary Mobile Group Identity,TMGI)、会话标识(seession id)、组RNTI(Group RNTI,G-RNTI)、非连续接收(Discontinuous Reception,DRX)配置信息以及邻区的SC-PTM业务信息等。需要说明的是,R13中的SC-PTM不支持健壮性包头压缩(Robust Header Compression,ROHC)功能。
SC-PTM的下行非连续的接收是通过以下参数控制的:onDurationTimerSCPTM、drx-InactivityTimerSCPTM、SC-MTCH-SchedulingCycle、以及SC-MTCH-SchedulingOffset。
当满足[(SFN*10)+subframe number]modulo(SC-MTCH-SchedulingCycle)=SC-MTCH-SchedulingOffset时,启动定时器onDurationTimerSCPTM;
当接收到下行PDCCH调度时,启动定时器drx-InactivityTimerSCPTM;
只有当定时器onDurationTimerSCPTM或drx-InactivityTimerSCPTM运行时才接收下行SC-PTM业务。
SC-PTM业务连续性采用基于SIB15的MBMS业务连续性概念,即“SIB15+MBMSInterestIndication”方式。空闲态的UE的业务连续性基于频率优先级的概念。
本申请实施例的技术方案中,定义一个新的SIB(称为第一SIB),第一SIB包括第一MCCH的配置信息,这里,第一MCCH为MBMS业务的控制信道,换句话说,第一SIB用于配置NR MBMS的控制信道的配置信息,可选地,NR MBMS的控制信道也可以叫做NR MCCH(即所述第一MCCH)。
进一步,第一MCCH用于承载第一信令,本申请实施例对第一信令的名称不做限定,如第一信令为信令A,所述第一信令包括至少一个第一MTCH的配置信息,这里,第一MTCH为MBMS业务的业务信道(也称为数据信道或传输信道),第一MTCH用于传输MBMS业务数据(如NR MBMS的业务数据)。换句话说,第一MCCH用于配置NR MBMS的业务信道的配置信息,可选地,NR MBMS的业务信道也可以叫做NR MTCH(即所述第一MTCH)。
具体地,所述第一信令用于配置NR MBMS的业务信道、该业务信道对应的业务信息以及该业务信道对应的调度信息。进一步,可选地,所述业务信道对应的业务信息,例如TMGI、session id等标识业务的标识信息。所述业务信道对应的调度信息,例如业务信道对应的MBMS业务数据被调度时使用的RNTI,例如G-RNTI、DRX配置信息等。
需要说明的是,第一MCCH和第一MTCH的传输都是基于PDCCH调度的。其中,用于调度第一MCCH的PDCCH使用的RNTI使用全网唯一标识,即是一个固定值。用于调度第一MTCH的PDCCH使用的RNTI通过第一MCCH进行配置。
需要说明的是,本申请实施例对所述第一SIB、所述第一MCCH和所述第一MTCH的命名不做限制。为便于描述,所述第一SIB也可以简称为SIB,所述第一MCCH也可以简称为MCCH,所述第一MTCH也可以简称为MTCH,通过SIB配置用于调度MCCH的PDCCH(即MCCH PDCCH)以及通知PDCCH,其中,通过MCCH PDCCH携带的DCI调度用于传输MCCH的PDSCH(即MCCH PDSCH)。进一步,通过MCCH配置M个用于调度MTCH的PDCCH(即MTCH 1 PDCCH、MTCH 2 PDCCH、…、MTCH M PDCCH),其中,MTCH n PDCCH携带的DCI调度用于传输MTCH n的PDSCH(即MTCH n PDSCH),n为大于等于1且小于等于M的整数。MCCH和MTCH被映射到 DL-SCH上,进一步,DL-SCH被映射到PDSCH上,其中,MCCH和MTCH属于逻辑信道,DL-SCH属于传输信道,PDSCH属于物理信道。
需要说明的是,上述方案中的MBMS业务包括但不局限于多播业务、组播业务。本申请实施例以MBS业务为例进行说明,“MBS业务”的描述也可以被替换为“多播业务”或者“组播业务”或者“MBMS业务”。
NR MBS业务中,同一个小区需要下发组播传播方式的MBS业务外,可能还会为某个特定的用户按照单播方式传输该MBS业务,例如该用户的信道比较差的情况下就需要为该用户按照单播方式传输该MBS业务。在一个小区中,也可能存在几个用户同时接收某MBS业务,但是基站都是按照单播方式发送MBS业务给每个用户,例如小区内接收MBS业务的用户比较少的情况下使用单播方式发送MBS业务给每个用户可以有效提高业务传输效率。
参照图2,针对某个MBS业务的分组数据单元(Packet Data Unit,PDU)会话,在5G核心网(5G Core network,5GC)到gNB之间可能采用一个共享的GTP隧道(Shared GTP tunnel)来传输MBS业务,即无论是单播业务还是MBS业务都是共享这个GTP隧道的。gNB按照多播(multicast)方式下发MBS业务给多播组(multicast group),以及按照单播(unicast)方式下发MBS业务给某个UE(图2以UE3为例)。其中,多播组包括一个或多个UE(图2以多播组包括UE1和UE2为例)。如何提高终端设备在一个小区里接收MBS业务的可靠性需要解决。为此,提出了本申请实施例的以下技术方案。
图3是本申请实施例提供的MBS业务的接收方法的流程示意图,如图3所示,所述MBS业务的接收方法包括以下步骤:
步骤301:终端设备接收第一小区按照单播方式发送的MBS业务,以及接收所述第一小区按照多播方式发送的MBS业务。
本申请实施例中,所述第一小区可以是指终端设备当前的服务小区。
本申请实施例中,终端设备在第一小区中按照单播方式接收MBS业务,与此同时,所述终端设备也有可能按照多播方式接收所该MBS业务,从而提高所述MBS业务接收的可靠性。
步骤302:所述终端设备对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在物理层进行合并或者在PDCP层进行重复检测。
本申请实施例中,所述终端设备对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在物理层进行合并或者在PDCP层进行重复检测,以下分别进行说明。
●所述终端设备通过物理层合并方式来提高接收可靠性增益。具体地,所述终端设备对单播方式对应的MBS业务和多播方式对应的MBS业务在物理层进行合并。
在本申请一可选方式中,所述终端设备接收所述第一小区发送的第一指示信息,所述第一指示信息用于指示所述终端设备同时接收单播方式对应的MBS业务和多播方式对应的MBS业务。
在本申请一可选方式中,所述终端设备接收所述第一小区发送的第三指示信息,所述第三指示信息用于指示所述终端设备对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在物理层进行合并,还是对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在PDCP层进行重复检测。
这里,终端设备根据网络设备配置的指示信息(即第一指示信息),同时接收某个MBS业务的单播方式发送和多播方式发送,例如网络设备可以显示的通过第一指示信息指示终端设备同时接收单播方式对应的MBS业务和多播方式对应的MBS业务。进一步,网络设备还通过第三指示信息指示终端设备对同时接收到的单播方式的MBS业务和组播方式的MBS业务是在物理层合并还是在PDCP层进行重复接收。
终端设备根据第一指示信息,按照单播方式接收某个MBS业务时,同时按照组播方式接收该MBS业务。终端设备根据第三指示信息,对单播方式对应的MBS业务和多播方式对应的MBS业务在物理层进行合并。
在本申请一可选方式中,网络设备还指示所述终端设备建立单播承载时保留多播承载的配置信息。具体地,当网络设备指示终端设备按照单播方式接收某个MBS业务时,如果之前终端设备按照多播方式接收该MBS业务,则终端设备在建立单播承载接收该MBS业务同时,保留多播承载的配置信息。如此,终端设备基于网络设备的指示,建立单播承载时保留多播承载的配置信息。
上述方案中,网络设备可以显式的指示所述终端设备建立单播承载时保留多播承载的配置信息,也可以隐式的指示所述终端设备建立单播承载时保留多播承载的配置信息,以下分别说明。
1)显式指示方式
所述终端设备接收所述第一小区发送的第二指示信息,所述第二指示信息用于指示所述终端设备建立单播承载时保留多播承载的配置信息,其中,所述单播承载用于所述终端设备按照单播方式接收所述MBS业务,所述多播承载用于所述终端设备按照多播方式接收所述MBS业务。
2)隐式指示方式
隐式指示可以引用前述方案中的第一指示或者第二指示来指示,在一可选方式中,通过所述第一指示信息指示所述终端设备建立单播承载时保留多播承载的配置信息,其中,所述单播承载用于所述终端设备按照单播方式接收所述MBS业务,所述多播承载用于所述终端设备按照多播方式接收所述MBS业务。
本申请实施例中,单播方式对应的MBS业务的传输块(Transport Block,TB)称为单播TB,多播方式对应的MBS业务的TB称为多播TB,对单播方式对应的MBS业务和多播方式对应的MBS业务在物理层进行合并的前提是,将单播TB和多播TB进行关联,即将属于同一TB的多播TB和单播TB进行关联。需要说明的是,属于同一TB是指TB内容相同。将单播TB和多播TB进行关联可以通过以下任意一种方式实现。
方式一:
所述单播方式对应的MBS业务的单播TB的调度信息为第一调度信息,所述多播方式对应的MBS业务的多播TB的调度信息为第二调度信息,所述单播TB和所述多播TB为同一TB,所述第一调度信息包含所述第二调度信息;所述终端设备基于所述第一调度信息,将属于同一TB的多播TB和单播TB进行关联,并将关联在一起的多播TB和单播TB在物理层进行合并。
这里,在单播TB的调度信息中添加对应多播TB的调度信息。这样,就可以将多播TB和单播TB进行关联,从而可以进行物理层的合并。
例如:单播TB的调度信息携带第一调度信息和第二调度信息,其中,第一调度信息用于调度单播TB,第二调度信息用于调度该单播TB对应的多播TB,通过该调度信息可以将单播TB和对应的多播TB关联起来。
方式二:
所述单播方式对应的MBS业务的单播TB的调度信息为第一调度信息,所述多播方式对应的MBS业务的多播TB的调度信息为第二调度信息,所述单播TB和所述多播TB为同一TB,所述第一调度信息包含第一标识信息,所述第二调度信息包含第二标识信息,所述第一标识信息和所述第二标识信息具有关联关系;所述终端设备基于所述第一标识信息和所述第二标识信息,将属于同一TB的多播TB和单播TB进行关联,并将关联在一起的多播TB和单播TB在物理层进行合并。
这里,单播TB的调度信息中添加一个指示信息,该单播TB对应的多播TB的调度信息中也添加一个指示信息,通过这两个指示信息将单播TB和多播TB进行关联,从而将关联在一起的多播TB和单播TB在物理层进行合并。
例如:单播TB和多播TB的调度信息中的指示信息是一个比特流、或者整数值、或者信息戳,如果两个调度中的指示信息相同,则两个调度信息对应的TB是可以关联在一起在物理层进行合并的。
本申请实施例中,为了能够达到单播TB和多播TB可以关联,首先要保证TB内容是相同的(即单播TB和多播TB属于同一TB)。网络设备在发送单播TB和多播TB时,可以采用图4所示的协议栈架构来保证单播TB和多播TB的内容相同(或者说网络设备保证在单播组包和多播组包时,是针对相同的TB)。
参照图4,图4为网络设备侧的协议栈的一种结构示意图,图4中省略了“实体”的描述,例如图4中的“SDAP”表示的是“SDAP实体”。MBS业务的PDU会话包括一个或多个Qos流,PDU会话的一个或多个Qos流可以通过SDAP实体映射到一个或者多个DRB上,其中,Qos流与DRB之间的映射关系可以是一对一,也可以是多对一。每个DRB对应一个逻辑信道,其中,不同的DRB通过不同的PDCP实体和RLC实体传输,也即不同的逻辑信道对应不同的PDCP实体和RLC实体。
需要说明的是,图4中,对于每个DRB,也可以不存在PDCP实体或者SDAP实体。也就是说,对于每个DRB,可以存在PDCP实体、或者存在PDCP实体+SDAP实体、或者存在SDAP实体。
MAC实体将每个MAC PDU(即一个TB数据)复制一份给PHY2实体,原来的MAC PDU给PHY1实体,通过PHY1实体按照多播方式进行发送MBS业务以及通过PHY2实体按照单播方式发送MBS业务。
方式三:
所述终端设备根据单播TB关联的序列号(Serial Number,SN)和多播TB关联的SN,将属 于同一TB的单播TB和多播TB进行关联。
例如:单播TB1关联SN1,单播TB2关联SN2,单播TB3关联SN3,多播TB1关联SN1,多播TB2关联SN2,多播TB3关联SN3。根据SN,可以将单播TB1和多播TB1进行关联,将单播TB2和多播TB2进行关联,将单播TB3和多播TB3进行关联。
进一步,所述终端设备基于关联在一起的单播TB和多播TB的接收情况确定单播方式的反馈信息。具体地,若所述终端设备成功接收到单播TB和多播TB中的至少之一,则所述终端设备回复针对所述单播方式的肯定确认消息;其中,所述单播TB是指所述单播方式对应的MBS业务的TB,所述多播TB是指所述多播方式对应的MBS业务的TB,所述单播TB和所述多播TB为同一TB。
上述方案中,所述TB关联一个SN,所述SN携带在以下至少之一中:所述TB的调度信息、所述TB所在的MAC PDU的MAC CE、所述TB所在的MAC PDU的MAC包头。
在一个示例中,当某个TB通过多播方式成功接收,但是通过单播方式接收失败,则终端设备在单播方式的HARQ反馈中,按照肯定确认(ACK)进行反馈。
在一个示例中,当某个TB通过单播方式成功接收,但是通过多播方式接收失败,则终端设备在单播方式的HARQ反馈中,按照肯定确认(ACK)进行反馈。
在一个示例中,当某个TB通过单播方式成功接收,且通过多播方式接收成功,则终端设备在单播方式的HARQ反馈中,按照肯定确认(ACK)进行反馈。
在一个示例中,当某个TB通过单播方式成功失败,且通过多播方式接收失败,则终端设备在单播方式的HARQ反馈中,按照否定确认(NACK)进行反馈。
通过上述方案,单播TB和多播TB任意一方接收成功,则终端设备就反馈ACK;单播TB和多播TB均接收失败,则终端设备反馈NACK。如此,可以避免不必要的单播重传,即降低单播重传的概率,提高了频谱效率。
本申请实施例的上述技术方案,终端设备在一个小区同时接收单播方式的MBS业务和多播方式的MBS业务,对单播方式的MBS业务和多播方式的MBS业务在物理层进行合并,提高了MBS业务的接收可靠性。
●所述终端设备通过PDCP层重复接收来提高接收可靠性。具体地,所述终端设备对单播方式对应的MBS业务和多播方式对应的MBS业务在PDCP层进行重复检测。
在本申请一可选方式中,所述终端设备接收所述第一小区发送的第一指示信息,所述第一指示信息用于指示所述终端设备同时接收单播方式对应的MBS业务和多播方式对应的MBS业务。
在本申请一可选方式中,所述终端设备接收所述第一小区发送的第三指示信息,所述第三指示信息用于指示所述终端设备对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在物理层进行合并,还是对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在PDCP层进行重复检测。
这里,终端设备根据网络设备配置的指示信息(即第一指示信息),同时接收某个MBS业务的单播方式发送和多播方式发送,例如网络设备可以显示的通过第一指示信息指示终端设备同时接收单播方式对应的MBS业务和多播方式对应的MBS业务。进一步,网络设备还通过第三指示信息指示终端设备对同时接收到的单播方式的MBS业务和组播方式的MBS业务是在物理层合并还是在PDCP层进行重复接收。
终端设备根据第一指示信息,按照单播方式接收某个MBS业务时,同时按照组播方式接收该MBS业务。终端设备根据第三指示信息,对单播方式对应的MBS业务和多播方式对应的MBS业务在物理层进行合并。
在本申请一可选方式中,网络设备还指示所述终端设备建立单播承载时保留多播承载的配置信息。具体地,当网络设备指示终端设备按照单播方式接收某个MBS业务时,如果之前终端设备按照多播方式接收该MBS业务,则终端设备在建立单播承载接收该MBS业务同时,保留多播承载的配置信息。如此,终端设备基于网络设备的指示,建立单播承载时保留多播承载的配置信息。
上述方案中,网络设备可以显式的指示所述终端设备建立单播承载时保留多播承载的配置信息,也可以隐式的指示所述终端设备建立单播承载时保留多播承载的配置信息,以下分别说明。
1)显式指示方式
所述终端设备接收所述第一小区发送的第二指示信息,所述第二指示信息用于指示所述终端设备建立单播承载时保留多播承载的配置信息,其中,所述单播承载用于所述终端设备按照单播方式接收所述MBS业务,所述多播承载用于所述终端设备按照多播方式接收所述MBS业务。
2)隐式指示方式
隐式指示可以引用前述方案中的第一指示或者第二指示来指示,在一可选方式中,通过所述第一指示信息指示所述终端设备建立单播承载时保留多播承载的配置信息,其中,所述单播承载用于所述终端设备按照单播方式接收所述MBS业务,所述多播承载用于所述终端设备按照多播方式接收所述MBS业务。
本申请实施例中,所述终端设备按照MBS业务数据关联的SN,对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在PDCP层进行重复检测。
本申请实施例的上述技术方案,终端设备在一个小区同时接收单播方式的MBS业务和多播方式的MBS业务,对单播方式的MBS业务和多播方式的MBS业务在PDCP层进行重复检测,提高了MBS业务的接收可靠性。
本申请实施例中,考虑到终端设备的移动性,会出现终端设备从所述第一小区切到第二小区的场景,以下对这种场景下终端设备如何接收MBS业务进行说明。
如图5所示,对于切换过程中保持MBS业务的连续接收,存在如下四种场景:
表1
在本申请一可选方式中,所述终端设备从所述第一小区切到第二小区的过程中,保留所述第一小区侧的MBS业务的多播配置信息。
这里,终端设备在切换过程中,保持原侧(即第一小区侧)关于MBS业务的多播配置信息。
在本申请一可选方式中,所述终端设备从所述第一小区切到第二小区的过程中和/或切换到第二小区后,同时接收所述第一小区按照多播方式发送的MBS业务和所述第二小区按照多播方式和/或单播方式发送的MBS业务;所述终端设备按照MBS业务数据关联的SN,对接收到的MBS业务进行重复检测。
这里,在切换过程中或者切换后一段时间内,终端设备仍然同时接收目标小区(即第二小区)中MBS业务的发送,以及原侧(即第一小区侧)关于MBS业务的发送。终端设备按照MBS业务数据关联的SN,对接收到的MBS业务进行重复检测。
在本申请一可选方式中,所述终端设备确定满足目标条件的情况下,释放所述第一小区侧的MBS业务的多播配置信息,并停止接收所述第一小区按照多播方式发送的MBS业务。进一步,可选地,所述目标条件包括以下至少之一:1、所述终端设备能够成功接收所述第二小区的MBS业务;2、所述终端设备检测到所述第一小区的MBS业务的信号质量低于指定门限。
这里,终端设备自己决定释放原侧(即第一小区侧)关于MBS业务的多播配置信息,并停止接收原侧的MBS业务。例如:终端设备能够成功接收目标小区(即第二小区)的所述MBS业务,并不存在SN gap的情况下,释放原侧(即第一小区侧)关于MBS业务的多播配置信息,并停止接收原侧的MBS业务。再例如:终端设备检测到原侧(即第一小区侧)的信号质量低于某一门限的情况下,释放原侧关于MBS业务的多播配置信息,并停止接收原侧的MBS业务。
本申请实施例中,从网络侧的角度来说,所述第一小区和所述第二小区的网络架构可以有如下实现方式:
I)所述第一小区和所述第二小区具有独立的分布单元(Distributed Unit,DU),以及具有相同的集中单元(Centralized Unit,CU)。
这里,可选地,DU实现的协议栈实体有:RLC实体、MAC实体、MAC实体和PHY实体。
这里,可选地,CU实现的协议栈实体有:RRC实体、PDCP实体。
上述方式来说,所述第一小区和所述第二小区实现了intra-CU的场景。
II)所述第一小区和所述第二小区属于同一MBS区域,且所述第一小区对应的基站和所述第二小区对应的基站公用一个锚点,所述锚点用于生成MBS业务的PDCP PDU并转发给所述MBS区域内的所有基站。
本申请实施例的上述技术方案,实现了终端设备在切换过程接收MBS业务的同时,提高了MBS业务的接收可靠性,并且可以降低丢包率保障MBS业务的连续性。
图6是本申请实施例提供的MBS业务的接收装置的结构组成示意图,应用于终端设备,如图6 所示,所述MBS业务的接收装置包括:
接收单元601,用于接收第一小区按照单播方式发送的MBS业务,以及接收所述第一小区按照多播方式发送的MBS业务;
处理单元602,用于对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在物理层进行合并或者在PDCP层进行重复检测。
在一可选方式中,所述接收单元601,还用于接收所述第一小区发送的第一指示信息,所述第一指示信息用于指示所述终端设备同时接收单播方式对应的MBS业务和多播方式对应的MBS业务。
在一可选方式中,所述第一指示信息还用于指示所述终端设备建立单播承载时保留多播承载的配置信息,其中,所述单播承载用于所述终端设备按照单播方式接收所述MBS业务,所述多播承载用于所述终端设备按照多播方式接收所述MBS业务。
在一可选方式中,所述接收单元601,还用于接收所述第一小区发送的第二指示信息,所述第二指示信息用于指示所述终端设备建立单播承载时保留多播承载的配置信息,其中,所述单播承载用于所述终端设备按照单播方式接收所述MBS业务,所述多播承载用于所述终端设备按照多播方式接收所述MBS业务。
在一可选方式中,所述接收单元601,还用于接收所述第一小区发送的第三指示信息,所述第三指示信息用于指示所述终端设备对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在物理层进行合并,还是对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在PDCP层进行重复检测。
在一可选方式中,所述单播方式对应的MBS业务的单播TB的调度信息为第一调度信息,所述多播方式对应的MBS业务的多播TB的调度信息为第二调度信息,所述单播TB和所述多播TB为同一TB,所述第一调度信息包含所述第二调度信息;
所述处理单元602,用于基于所述第一调度信息,将属于同一TB的多播TB和单播TB进行关联,并将关联在一起的多播TB和单播TB在物理层进行合并。
在一可选方式中,所述单播方式对应的MBS业务的单播TB的调度信息为第一调度信息,所述多播方式对应的MBS业务的多播TB的调度信息为第二调度信息,所述单播TB和所述多播TB为同一TB,所述第一调度信息包含第一标识信息,所述第二调度信息包含第二标识信息,所述第一标识信息和所述第二标识信息具有关联关系;
所述处理单元602,用于基于所述第一标识信息和所述第二标识信息,将属于同一TB的多播TB和单播TB进行关联,并将关联在一起的多播TB和单播TB在物理层进行合并。
在一可选方式中,所述装置还包括:
发送单元(图中未示出),用于若所述接收单元成功接收到单播TB和多播TB中的至少之一,则回复针对所述单播方式的肯定确认消息;其中,所述单播TB是指所述单播方式对应的MBS业务的TB,所述多播TB是指所述多播方式对应的MBS业务的TB,所述单播TB和所述多播TB为同一TB。
在一可选方式中,所述TB关联一个SN,所述SN携带在以下至少之一中:所述TB的调度信息、所述TB所在的MAC PDU的MAC CE、所述TB所在的MAC PDU的MAC包头。
在一可选方式中,所述处理单元602,还用于根据单播TB关联的SN和多播TB关联的SN,将属于同一TB的单播TB和多播TB进行关联,基于关联在一起的单播TB和多播TB的接收情况确定单播方式的反馈信息。
在一可选方式中,所述处理单元602,用于按照MBS业务数据关联的SN,对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在PDCP层进行重复检测。
在一可选方式中,所述处理单元602,还用于在终端设备从所述第一小区切到第二小区的过程中,保留所述第一小区侧的MBS业务的多播配置信息。
在一可选方式中,所述接收单元601,用于在终端设备从所述第一小区切到第二小区的过程中和/或切换到第二小区后,同时接收所述第一小区按照多播方式发送的MBS业务和所述第二小区按照多播方式和/或单播方式发送的MBS业务;
所述处理单元602,用于按照MBS业务数据关联的SN,对接收到的MBS业务进行重复检测。
在一可选方式中,所述处理单元602,还用于在确定满足目标条件的情况下,释放所述第一小区侧的MBS业务的多播配置信息;
所述接收单元601,还用于停止接收所述第一小区按照多播方式发送的MBS业务。
在一可选方式中,所述目标条件包括以下至少之一:
所述终端设备能够成功接收所述第二小区的MBS业务;
所述终端设备检测到所述第一小区的MBS业务的信号质量低于指定门限。
在一可选方式中,所述第一小区和所述第二小区具有独立的DU,以及具有相同的CU。
在一可选方式中,所述第一小区和所述第二小区属于同一MBS区域,且所述第一小区对应的基站和所述第二小区对应的基站公用一个锚点,所述锚点用于生成MBS业务的PDCP PDU并转发给所述MBS区域内的所有基站。
本领域技术人员应当理解,本申请实施例的上述MBS业务的接收装置的相关描述可以参照本申请实施例的MBS业务的接收方法的相关描述进行理解。
图7是本申请实施例提供的一种通信设备700示意性结构图。该通信设备可以是终端设备,也可以是网络设备,图7所示的通信设备700包括处理器710,处理器710可以从存储器中调用并运行计算机程序,以实现本申请实施例中的方法。
可选地,如图7所示,通信设备700还可以包括存储器720。其中,处理器710可以从存储器720中调用并运行计算机程序,以实现本申请实施例中的方法。
其中,存储器720可以是独立于处理器710的一个单独的器件,也可以集成在处理器710中。
可选地,如图7所示,通信设备700还可以包括收发器730,处理器710可以控制该收发器730与其他设备进行通信,具体地,可以向其他设备发送信息或数据,或接收其他设备发送的信息或数据。
其中,收发器730可以包括发射机和接收机。收发器730还可以进一步包括天线,天线的数量可以为一个或多个。
可选地,该通信设备700具体可为本申请实施例的网络设备,并且该通信设备700可以实现本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该通信设备700具体可为本申请实施例的移动终端/终端设备,并且该通信设备700可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程,为了简洁,在此不再赘述。
图8是本申请实施例的芯片的示意性结构图。图8所示的芯片800包括处理器810,处理器810可以从存储器中调用并运行计算机程序,以实现本申请实施例中的方法。
可选地,如图8所示,芯片800还可以包括存储器820。其中,处理器810可以从存储器820中调用并运行计算机程序,以实现本申请实施例中的方法。
其中,存储器820可以是独立于处理器810的一个单独的器件,也可以集成在处理器810中。
可选地,该芯片800还可以包括输入接口830。其中,处理器810可以控制该输入接口830与其他设备或芯片进行通信,具体地,可以获取其他设备或芯片发送的信息或数据。
可选地,该芯片800还可以包括输出接口840。其中,处理器810可以控制该输出接口840与其他设备或芯片进行通信,具体地,可以向其他设备或芯片输出信息或数据。
可选地,该芯片可应用于本申请实施例中的网络设备,并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该芯片可应用于本申请实施例中的移动终端/终端设备,并且该芯片可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程,为了简洁,在此不再赘述。
应理解,本申请实施例提到的芯片还可以称为系统级芯片,系统芯片,芯片系统或片上系统芯片等。
图9是本申请实施例提供的一种通信系统900的示意性框图。如图9所示,该通信系统900包括终端设备910和网络设备920。
其中,该终端设备910可以用于实现上述方法中由终端设备实现的相应的功能,以及该网络设备920可以用于实现上述方法中由网络设备实现的相应的功能为了简洁,在此不再赘述。
应理解,本申请实施例的处理器可能是一种集成电路芯片,具有信号的处理能力。在实现过程中,上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor,DSP)、专用集成电路(Application Specific Integrated Circuit,ASIC)、现成可编程门阵列(Field Programmable Gate Array,FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器 执行完成,或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器,闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器,处理器读取存储器中的信息,结合其硬件完成上述方法的步骤。
可以理解,本申请实施例中的存储器可以是易失性存储器或非易失性存储器,或可包括易失性和非易失性存储器两者。其中,非易失性存储器可以是只读存储器(Read-Only Memory,ROM)、可编程只读存储器(Programmable ROM,PROM)、可擦除可编程只读存储器(Erasable PROM,EPROM)、电可擦除可编程只读存储器(Electrically EPROM,EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory,RAM),其用作外部高速缓存。通过示例性但不是限制性说明,许多形式的RAM可用,例如静态随机存取存储器(Static RAM,SRAM)、动态随机存取存储器(Dynamic RAM,DRAM)、同步动态随机存取存储器(Synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM,DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM,SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM,DR RAM)。应注意,本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解,上述存储器为示例性但不是限制性说明,例如,本申请实施例中的存储器还可以是静态随机存取存储器(static RAM,SRAM)、动态随机存取存储器(dynamic RAM,DRAM)、同步动态随机存取存储器(synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM,DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(synch link DRAM,SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM,DR RAM)等等。也就是说,本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读存储介质,用于存储计算机程序。
可选的,该计算机可读存储介质可应用于本申请实施例中的网络设备,并且该计算机程序使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该计算机可读存储介质可应用于本申请实施例中的移动终端/终端设备,并且该计算机程序使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程,为了简洁,在此不再赘述。
本申请实施例还提供了一种计算机程序产品,包括计算机程序指令。
可选的,该计算机程序产品可应用于本申请实施例中的网络设备,并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该计算机程序产品可应用于本申请实施例中的移动终端/终端设备,并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程,为了简洁,在此不再赘述。
本申请实施例还提供了一种计算机程序。
可选的,该计算机程序可应用于本申请实施例中的网络设备,当该计算机程序在计算机上运行时,使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该计算机程序可应用于本申请实施例中的移动终端/终端设备,当该计算机程序在计算机上运行时,使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程,为了简洁,在此不再赘述。
本领域普通技术人员可以意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的系统、装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的系统、装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它 的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(Read-Only Memory,)ROM、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述,仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本申请揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本申请的保护范围之内。因此,本申请的保护范围应所述以权利要求的保护范围为准。
Claims (39)
- 一种多媒体多播服务MBS业务的接收方法,所述方法包括:终端设备接收第一小区按照单播方式发送的MBS业务,以及接收所述第一小区按照多播方式发送的MBS业务;所述终端设备对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在物理层进行合并或者在分组数据汇聚协议PDCP层进行重复检测。
- 根据权利要求1所述的方法,其中,所述方法还包括:所述终端设备接收所述第一小区发送的第一指示信息,所述第一指示信息用于指示所述终端设备同时接收单播方式对应的MBS业务和多播方式对应的MBS业务。
- 根据权利要求2所述的方法,其中,所述第一指示信息还用于指示所述终端设备建立单播承载时保留多播承载的配置信息,其中,所述单播承载用于所述终端设备按照单播方式接收所述MBS业务,所述多播承载用于所述终端设备按照多播方式接收所述MBS业务。
- 根据权利要求1或2所述的方法,其中,所述方法还包括:所述终端设备接收所述第一小区发送的第二指示信息,所述第二指示信息用于指示所述终端设备建立单播承载时保留多播承载的配置信息,其中,所述单播承载用于所述终端设备按照单播方式接收所述MBS业务,所述多播承载用于所述终端设备按照多播方式接收所述MBS业务。
- 根据权利要求1至4中任一项所述的方法,其中,所述方法还包括:所述终端设备接收所述第一小区发送的第三指示信息,所述第三指示信息用于指示所述终端设备对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在物理层进行合并,还是对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在PDCP层进行重复检测。
- 根据权利要求1至5中任一项所述的方法,其中,所述单播方式对应的MBS业务的单播传输块TB的调度信息为第一调度信息,所述多播方式对应的MBS业务的多播TB的调度信息为第二调度信息,所述单播TB和所述多播TB为同一TB,所述第一调度信息包含所述第二调度信息;所述终端设备对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在物理层进行合并,包括:所述终端设备基于所述第一调度信息,将属于同一TB的多播TB和单播TB进行关联,并将关联在一起的多播TB和单播TB在物理层进行合并。
- 根据权利要求1至5中任一项所述的方法,其中,所述单播方式对应的MBS业务的单播TB的调度信息为第一调度信息,所述多播方式对应的MBS业务的多播TB的调度信息为第二调度信息,所述单播TB和所述多播TB为同一TB,所述第一调度信息包含第一标识信息,所述第二调度信息包含第二标识信息,所述第一标识信息和所述第二标识信息具有关联关系;所述终端设备对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在物理层进行合并,包括:所述终端设备基于所述第一标识信息和所述第二标识信息,将属于同一TB的多播TB和单播TB进行关联,并将关联在一起的多播TB和单播TB在物理层进行合并。
- 根据权利要求1至6中任一项所述的方法,其中,所述方法还包括:若所述终端设备成功接收到单播TB和多播TB中的至少之一,则所述终端设备回复针对所述单播方式的肯定确认消息;其中,所述单播TB是指所述单播方式对应的MBS业务的TB,所述多播TB是指所述多播方式对应的MBS业务的TB,所述单播TB和所述多播TB为同一TB。
- 根据权利要求8所述的方法,其中,所述TB关联一个序列号SN,所述SN携带在以下至少之一中:所述TB的调度信息、所述TB所在的MAC PDU的MAC CE、所述TB所在的MAC PDU的MAC包头。
- 根据权利要求8所述的方法,其中,所述方法还包括:所述终端设备根据单播TB关联的SN和多播TB关联的SN,将属于同一TB的单播TB和多播TB进行关联,基于关联在一起的单播TB和多播TB的接收情况确定单播方式的反馈信息。
- 根据权利要求1至5中任一项所述的方法,其中,所述终端设备对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在PDCP层进行重复检测,包括:所述终端设备按照MBS业务数据关联的SN,对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在PDCP层进行重复检测。
- 根据权利要求1至11中任一项所述的方法,其中,所述方法还包括:所述终端设备从所述第一小区切到第二小区的过程中,保留所述第一小区侧的MBS业务的多播配置信息。
- 根据权利要求1至12中任一项所述的方法,其中,所述方法还包括:所述终端设备从所述第一小区切到第二小区的过程中和/或切换到第二小区后,同时接收所述第一小区按照多播方式发送的MBS业务和所述第二小区按照多播方式和/或单播方式发送的MBS业务;所述终端设备按照MBS业务数据关联的SN,对接收到的MBS业务进行重复检测。
- 根据权利要求13所述的方法,其中,所述方法还包括:所述终端设备确定满足目标条件的情况下,释放所述第一小区侧的MBS业务的多播配置信息,并停止接收所述第一小区按照多播方式发送的MBS业务。
- 根据权利要求14所述的方法,其中,所述目标条件包括以下至少之一:所述终端设备能够成功接收所述第二小区的MBS业务;所述终端设备检测到所述第一小区的MBS业务的信号质量低于指定门限。
- 根据权利要求12至15中任一项所述的方法,其中,所述第一小区和所述第二小区具有独立的分布单元DU,以及具有相同的集中单元CU。
- 根据权利要求12至15中任一项所述的方法,其中,所述第一小区和所述第二小区属于同一MBS区域,且所述第一小区对应的基站和所述第二小区对应的基站公用一个锚点,所述锚点用于生成MBS业务的PDCP PDU并转发给所述MBS区域内的所有基站。
- 一种MBS业务的接收装置,所述装置包括:接收单元,用于接收第一小区按照单播方式发送的MBS业务,以及接收所述第一小区按照多播方式发送的MBS业务;处理单元,用于对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在物理层进行合并或者在PDCP层进行重复检测。
- 根据权利要求18所述的装置,其中,所述接收单元,还用于接收所述第一小区发送的第一指示信息,所述第一指示信息用于指示所述终端设备同时接收单播方式对应的MBS业务和多播方式对应的MBS业务。
- 根据权利要求19所述的装置,其中,所述第一指示信息还用于指示所述终端设备建立单播承载时保留多播承载的配置信息,其中,所述单播承载用于所述终端设备按照单播方式接收所述MBS业务,所述多播承载用于所述终端设备按照多播方式接收所述MBS业务。
- 根据权利要求18或19所述的装置,其中,所述接收单元,还用于接收所述第一小区发送的第二指示信息,所述第二指示信息用于指示所述终端设备建立单播承载时保留多播承载的配置信息,其中,所述单播承载用于所述终端设备按照单播方式接收所述MBS业务,所述多播承载用于所述终端设备按照多播方式接收所述MBS业务。
- 根据权利要求18至21中任一项所述的装置,其中,所述接收单元,还用于接收所述第一小区发送的第三指示信息,所述第三指示信息用于指示所述终端设备对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在物理层进行合并,还是对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在PDCP层进行重复检测。
- 根据权利要求18至22中任一项所述的装置,其中,所述单播方式对应的MBS业务的单播TB的调度信息为第一调度信息,所述多播方式对应的MBS业务的多播TB的调度信息为第二调度信息,所述单播TB和所述多播TB为同一TB,所述第一调度信息包含所述第二调度信息;所述处理单元,用于基于所述第一调度信息,将属于同一TB的多播TB和单播TB进行关联,并将关联在一起的多播TB和单播TB在物理层进行合并。
- 根据权利要求18至22中任一项所述的装置,其中,所述单播方式对应的MBS业务的单播TB的调度信息为第一调度信息,所述多播方式对应的MBS业务的多播TB的调度信息为第二调度信息,所述单播TB和所述多播TB为同一TB,所述第一调度信息包含第一标识信息,所述第二调度信息包含第二标识信息,所述第一标识信息和所述第二标识信息具有关联关系;所述处理单元,用于基于所述第一标识信息和所述第二标识信息,将属于同一TB的多播TB和单播TB进行关联,并将关联在一起的多播TB和单播TB在物理层进行合并。
- 根据权利要求18至23中任一项所述的装置,其中,所述装置还包括:发送单元,用于若所述接收单元成功接收到单播TB和多播TB中的至少之一,则回复针对所述单播方式的肯定确认消息;其中,所述单播TB是指所述单播方式对应的MBS业务的TB,所述多播TB是指所述多播方式对应的MBS业务的TB,所述单播TB和所述多播TB为同一TB。
- 根据权利要求25所述的装置,其中,所述TB关联一个SN,所述SN携带在以下至少之一中:所述TB的调度信息、所述TB所在的MAC PDU的MAC CE、所述TB所在的MAC PDU的MAC包头。
- 根据权利要求25所述的装置,其中,所述处理单元,还用于根据单播TB关联的SN和多播TB关联的SN,将属于同一TB的单播TB和多播TB进行关联,基于关联在一起的单播TB和多播TB的接收情况确定单播方式的反馈信息。
- 根据权利要求18至22中任一项所述的装置,其中,所述处理单元,用于按照MBS业务数据关联的SN,对所述单播方式对应的MBS业务和所述多播方式对应的MBS业务在PDCP层进行重复检测。
- 根据权利要求18至28中任一项所述的装置,其中,所述处理单元,还用于在终端设备从所述第一小区切到第二小区的过程中,保留所述第一小区侧的MBS业务的多播配置信息。
- 根据权利要求18至29中任一项所述的装置,其中,所述接收单元,用于在终端设备从所述第一小区切到第二小区的过程中和/或切换到第二小区后,同时接收所述第一小区按照多播方式发送的MBS业务和所述第二小区按照多播方式和/或单播方式发送的MBS业务;所述处理单元,用于按照MBS业务数据关联的SN,对接收到的MBS业务进行重复检测。
- 根据权利要求30所述的装置,其中,所述处理单元,还用于在确定满足目标条件的情况下,释放所述第一小区侧的MBS业务的多播配置信息;所述接收单元,还用于停止接收所述第一小区按照多播方式发送的MBS业务。
- 根据权利要求31所述的装置,其中,所述目标条件包括以下至少之一:所述终端设备能够成功接收所述第二小区的MBS业务;所述终端设备检测到所述第一小区的MBS业务的信号质量低于指定门限。
- 根据权利要求29至32中任一项所述的装置,其中,所述第一小区和所述第二小区具有独立的DU,以及具有相同的CU。
- 根据权利要求29至32中任一项所述的装置,其中,所述第一小区和所述第二小区属于同一MBS区域,且所述第一小区对应的基站和所述第二小区对应的基站公用一个锚点,所述锚点用于生成MBS业务的PDCP PDU并转发给所述MBS区域内的所有基站。
- 一种终端设备,包括:处理器和存储器,该存储器用于存储计算机程序,所述处理器用于调用并运行所述存储器中存储的计算机程序,执行如权利要求1至17中任一项所述的方法。
- 一种芯片,包括:处理器,用于从存储器中调用并运行计算机程序,使得安装有所述芯片的设备执行如权利要求1至17中任一项所述的方法。
- 一种计算机可读存储介质,用于存储计算机程序,所述计算机程序使得计算机执行如权利要求1至17中任一项所述的方法。
- 一种计算机程序产品,包括计算机程序指令,该计算机程序指令使得计算机执行如权利要求1至17中任一项所述的方法。
- 一种计算机程序,所述计算机程序使得计算机执行如权利要求1至17中任一项所述的方法。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2020/101433 WO2022006888A1 (zh) | 2020-07-10 | 2020-07-10 | 一种mbs业务的接收方法及装置、终端设备 |
CN202310506696.4A CN116744240A (zh) | 2020-07-10 | 2020-07-10 | 一种mbs业务的接收方法及装置、终端设备 |
CN202080102718.5A CN115804064A (zh) | 2020-07-10 | 2020-07-10 | 一种mbs业务的接收方法及装置、终端设备 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2020/101433 WO2022006888A1 (zh) | 2020-07-10 | 2020-07-10 | 一种mbs业务的接收方法及装置、终端设备 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022006888A1 true WO2022006888A1 (zh) | 2022-01-13 |
Family
ID=79553561
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2020/101433 WO2022006888A1 (zh) | 2020-07-10 | 2020-07-10 | 一种mbs业务的接收方法及装置、终端设备 |
Country Status (2)
Country | Link |
---|---|
CN (2) | CN116744240A (zh) |
WO (1) | WO2022006888A1 (zh) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102148797A (zh) * | 2010-02-08 | 2011-08-10 | 上海贝尔股份有限公司 | 合并的多数据流的传输技术 |
CN102595326A (zh) * | 2011-01-04 | 2012-07-18 | 上海贝尔股份有限公司 | 在无线通信网络的基站中用于切换多媒体广播多播业务用户终端的方法 |
US20130258935A1 (en) * | 2012-03-28 | 2013-10-03 | Qualcomm Incorporated | Extending cyclic prefix length in wireless communication network having mixed carrier |
CN104919756A (zh) * | 2013-01-04 | 2015-09-16 | 高通股份有限公司 | 演进多媒体广播/多播服务(eMBMS)群集管理 |
-
2020
- 2020-07-10 WO PCT/CN2020/101433 patent/WO2022006888A1/zh active Application Filing
- 2020-07-10 CN CN202310506696.4A patent/CN116744240A/zh active Pending
- 2020-07-10 CN CN202080102718.5A patent/CN115804064A/zh active Pending
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102148797A (zh) * | 2010-02-08 | 2011-08-10 | 上海贝尔股份有限公司 | 合并的多数据流的传输技术 |
CN102595326A (zh) * | 2011-01-04 | 2012-07-18 | 上海贝尔股份有限公司 | 在无线通信网络的基站中用于切换多媒体广播多播业务用户终端的方法 |
US20130258935A1 (en) * | 2012-03-28 | 2013-10-03 | Qualcomm Incorporated | Extending cyclic prefix length in wireless communication network having mixed carrier |
CN104919756A (zh) * | 2013-01-04 | 2015-09-16 | 高通股份有限公司 | 演进多媒体广播/多播服务(eMBMS)群集管理 |
Non-Patent Citations (1)
Title |
---|
BDBOS: "Broadcast / multicast requirements supporting Mission Critical Services in 5G", 3GPP DRAFT; S1-192133, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG1, no. Sophia Antipolis, France; 20190819 - 20190823, 19 August 2019 (2019-08-19), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051760196 * |
Also Published As
Publication number | Publication date |
---|---|
CN116744240A (zh) | 2023-09-12 |
CN115804064A (zh) | 2023-03-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2021134316A1 (zh) | 一种业务调度方法及装置、终端设备、网络设备 | |
WO2021056152A1 (zh) | 一种信息配置方法及装置、终端设备、网络设备 | |
US11949598B2 (en) | Window adjustment method and apparatus, network device, terminal device | |
WO2021134298A1 (zh) | 一种资源指示方法及装置、通信设备 | |
US20230361923A1 (en) | Mbs service configuration method and terminal device | |
WO2021051320A1 (zh) | 一种业务数据传输方法及装置、网络设备、终端设备 | |
WO2022141255A1 (zh) | 一种mbs业务的配置方法及装置、网络设备、终端设备 | |
WO2022006875A1 (zh) | 建立mbs业务的方法及装置、终端设备、网络设备 | |
WO2022006849A1 (zh) | Mbs业务的tci状态管理方法及装置、终端设备 | |
US20230283498A1 (en) | Method for improving reliability of mbs service and network device | |
CN113678500B (zh) | 一种反馈资源配置方法及通信方法、装置、通信设备 | |
WO2021051321A1 (zh) | 一种业务数据传输方法及装置、终端设备 | |
WO2022205454A1 (zh) | 一种指示寻呼的方法及装置、终端设备、网络设备 | |
WO2022120837A1 (zh) | Mbs业务的半静态调度方法及装置、终端设备、网络设备 | |
WO2022141545A1 (zh) | 一种mcch调度传输方法及装置、终端设备 | |
WO2021142646A1 (zh) | 一种业务传输方法及装置、通信设备 | |
WO2022006888A1 (zh) | 一种mbs业务的接收方法及装置、终端设备 | |
WO2021051322A1 (zh) | 一种bwp配置方法及装置、终端设备、网络设备 | |
WO2022021235A1 (zh) | 一种mbs业务的传输方法及装置、通信设备 | |
WO2022165720A1 (zh) | 提高mbs业务可靠性的方法及装置、终端设备、网络设备 | |
WO2022021410A1 (zh) | 一种mbs业务传输方法及装置、终端设备、网络设备 | |
WO2022006882A1 (zh) | Mbs业务的传输方法及装置、网络设备、终端设备 | |
WO2022226937A1 (zh) | 一种mbs寻呼方法及装置、网络设备、终端设备 | |
WO2022056859A1 (zh) | Mbs业务传输进度的控制方法及装置、通信设备 | |
WO2021189458A1 (zh) | 一种数据转发方法及装置、通信设备 |
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: 20944715 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: 20944715 Country of ref document: EP Kind code of ref document: A1 |