WO2021051321A1 - 一种业务数据传输方法及装置、终端设备 - Google Patents

一种业务数据传输方法及装置、终端设备 Download PDF

Info

Publication number
WO2021051321A1
WO2021051321A1 PCT/CN2019/106510 CN2019106510W WO2021051321A1 WO 2021051321 A1 WO2021051321 A1 WO 2021051321A1 CN 2019106510 W CN2019106510 W CN 2019106510W WO 2021051321 A1 WO2021051321 A1 WO 2021051321A1
Authority
WO
WIPO (PCT)
Prior art keywords
cell
service data
mbms service
mbms
terminal device
Prior art date
Application number
PCT/CN2019/106510
Other languages
English (en)
French (fr)
Inventor
王淑坤
杨宁
刘建华
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to CN201980100055.0A priority Critical patent/CN114342421A/zh
Priority to PCT/CN2019/106510 priority patent/WO2021051321A1/zh
Publication of WO2021051321A1 publication Critical patent/WO2021051321A1/zh
Priority to US17/693,549 priority patent/US20220210614A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0007—Control or signalling for completing the hand-off for multicast or broadcast services, e.g. MBMS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • 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 technology, and in particular to a method and device for service data transmission, and terminal equipment.
  • Multimedia Broadcast Multicast Service is a technology that transmits data from one data source to multiple users by sharing network resources. This technology can effectively use network resources while providing multimedia services to achieve better performance. Broadcast and multicast of high-rate (such as 256kbps) multimedia services.
  • NR New Radio
  • MBMS service in NR when the terminal equipment is at the edge of the cell before and after the cell change, and the signal quality at the edge of the cell is poor, it will cause the problem of failure to receive the MBMS service.
  • the MBMS service data of the two cells are not aligned.
  • the MBMS service data will be lost due to the update of the MBMS configuration information.
  • the embodiments of the present application provide a service data transmission method and device, and terminal equipment.
  • the terminal device receives the MBMS service data of the first cell and the MBMS service data of the second cell before the cell change;
  • the terminal device stops receiving the MBMS service data of the first cell after the cell is changed;
  • the first cell is a cell before a cell change
  • the second cell is a cell after a cell change
  • the terminal device receives the first MBMS service data and the second MBMS service data of the first cell, the second MBMS service data is the same as the first MBMS service data, and the transmission start time of the second MBMS service data is later At the start time of the transmission of the first MBMS service data.
  • the receiving unit is configured to receive the MBMS service data of the first cell and the MBMS service data of the second cell before the cell change; stop receiving the MBMS service data of the first cell after the cell change;
  • the first cell is a cell before a cell change
  • the second cell is a cell after a cell change
  • the receiving unit is configured to receive the first MBMS service data and the second MBMS service data of the first cell, the second MBMS service data is the same as the first MBMS service data, and the transmission of the second MBMS service data starts The start time is later than the transmission start time of the first MBMS service data.
  • the terminal device provided in the embodiment of the present application includes a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the foregoing business data transmission method.
  • the chip provided in the embodiment of the present application is used to implement the foregoing service data transmission method.
  • the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes the above-mentioned service data transmission method.
  • the computer-readable storage medium provided by the embodiment of the present application is used to store a computer program, and the computer program enables a computer to execute the above-mentioned service data transmission method.
  • the computer program product provided by the embodiment of the present application includes computer program instructions that cause a computer to execute the above-mentioned service data transmission method.
  • the computer program provided in the embodiment of the present application when it runs on a computer, causes the computer to execute the above-mentioned service data transmission method.
  • the NR system supports broadcast and multicast of MBMS services.
  • a solution is proposed, that is, before the cell change, the terminal equipment simultaneously receives the MBMS of the cell before the cell change (ie the first cell)
  • the service data and the MBMS service data of the cell after the cell change ensure the reliability of MBMS service data transmission.
  • a solution is proposed, that is, a cell sends two copies of MBMS service data at the same time, one MBMS service data is used as the main service data, and the other MBMS service data is used as the auxiliary service data, so as to ensure the reliability of data transmission. .
  • 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 a first SIB related configuration provided by an embodiment of the present application
  • Fig. 3 is a schematic diagram of a PTM configuration transmission mechanism provided by an embodiment of the present application.
  • Fig. 4 is a PTM channel and its mapping diagram provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram 1 of the flow of a service data transmission method provided by an embodiment of the application.
  • FIG. 6 is a schematic diagram 2 of the flow of a service data transmission method provided by an embodiment of the application.
  • Figure 7-1 is the first schematic diagram of main service data and auxiliary service data provided by an embodiment of the application.
  • Figure 7-2 is a second schematic diagram of main service data and auxiliary service data provided by an embodiment of this application.
  • FIG. 8 is a schematic diagram 1 of the structural composition of a service data transmission device provided by an embodiment of the application.
  • FIG. 9 is a second schematic diagram of the structural composition of the service data transmission device provided by the embodiment of the application.
  • FIG. 10 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a chip of an embodiment of the present application.
  • FIG. 12 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 system 5G communication system or future communication system.
  • the communication system 100 applied in the embodiment of this application is shown in FIG. 1.
  • the communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal 120 (or called a communication terminal or terminal).
  • the network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminals located in 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 network equipment can be a mobile switching center, a relay station, an access point, an in-vehicle device, a wearable device, a hub, a switch, a bridge, a router, a network side device in a 5G network, or a network device in a future communication system, etc.
  • the communication system 100 also includes at least one terminal 120 located within the coverage area of the network device 110.
  • the "terminal” used here includes, but is not limited to, connection via a wired line, such as via a public switched telephone network (PSTN), digital subscriber line (Digital Subscriber Line, DSL), digital cable, and direct cable connection; And/or another data connection/network; and/or via a wireless interface, such as for cellular networks, wireless local area networks (WLAN), digital TV networks such as DVB-H networks, satellite networks, AM-FM Broadcast transmitter; and/or another terminal's device configured to receive/send communication signals; and/or Internet of Things (IoT) equipment.
  • PSTN public switched telephone network
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • DSL Digital Subscriber Line
  • a terminal set to communicate through a wireless interface may be referred to as a "wireless communication terminal", a “wireless terminal” or a “mobile terminal”.
  • mobile terminals include, but are not limited to, satellite or cellular phones; Personal Communications System (PCS) terminals that can combine cellular radio phones with data processing, fax, and data communication capabilities; can include radio phones, pagers, Internet/intranet PDA with internet access, web browser, memo pad, calendar, and/or Global Positioning System (GPS) receiver; and conventional laptop and/or palmtop receivers or others including radio telephone transceivers Electronic device.
  • PCS Personal Communications System
  • GPS Global Positioning System
  • Terminal can refer to access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user Device.
  • the access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA), with 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 the future evolution of PLMN, etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • direct terminal connection (Device to Device, D2D) communication may be performed between the terminals 120.
  • the 5G communication system or 5G network may also be referred to as a New Radio (NR) system or NR network.
  • 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 There is no restriction on this.
  • the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
  • network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
  • the devices with communication functions in the network/system in the embodiments of the present application may be referred to as communication devices.
  • the communication device may include a network device 110 and a terminal 120 with communication functions, and the network device 110 and the terminal 120 may be the specific devices described above, which will not be repeated here; communication
  • the device may also 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 the embodiment of the present application.
  • 5G Enhanced Mobile Broadband
  • URLLC Ultra-Reliable Low-Latency Communications
  • mMTC Massive Machine-Type Communications
  • eMBB is still targeting users to obtain multimedia content, services and data, and its demand is growing very rapidly.
  • eMBB may be deployed in different scenarios, such as indoors, urban areas, rural areas, etc., its capabilities and requirements are also quite different, so it cannot be generalized and must be analyzed in detail in conjunction with specific deployment scenarios.
  • Typical applications of URLLC include: industrial automation, power automation, telemedicine operations (surgery), traffic safety protection, etc.
  • the typical characteristics of mMTC include: high connection density, small data volume, delay-insensitive services, low cost and long service life of the module.
  • RRC Radio Resource Control
  • RRC_INACTIVE Radio Resource Control
  • RRC_IDLE state (abbreviated as idle state): mobility is UE-based 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 UE context on the base station side, and no RRC connection.
  • RRC_CONNECTED state (referred to as connected state for short): There is an RRC connection, and UE context exists on the base station side and the UE side. The network side knows that the location of the UE is of a specific cell level. Mobility is the mobility controlled by the network side. Unicast data can be transmitted between the UE and the base station.
  • Mobility is UE-based cell selection and reselection, there is a connection between CN-NR, UE context is stored on a certain base station, and paging is triggered by RAN, based on The paging area of the RAN is managed by the RAN, and the network side knows that the location of the UE is based on the paging area level of the RAN.
  • MBMS was introduced in 3GPP Release 6 (Release 6, R6).
  • 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. Realize the broadcast and multicast of multimedia services at a higher rate (such as 256kbps).
  • 3GPP Due to the low spectrum efficiency of MBMS in 3GPP R6, it is not sufficient to effectively carry and support the operation of mobile TV-type services. Therefore, in LTE, 3GPP clearly proposed to enhance the ability to support downlink high-speed MBMS services, and determined 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 unified frequency to send service data in all cells at the same time, but To ensure synchronization between the cells. This method can greatly improve the overall signal-to-noise ratio distribution of the cell, and the spectrum efficiency will be greatly improved accordingly.
  • eMBMS realizes the broadcast and multicast of services based on the IP multicast protocol.
  • MBMS has only a broadcast bearer mode, and no multicast bearer mode.
  • reception of MBMS services is suitable for UEs in idle state or connected state.
  • 3GPP R13 introduced the single cell point to multipoint (Single Cell Point To Multiploint, SC-PTM) concept, and SC-PTM is based on the MBMS network architecture.
  • 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), and further, DL-SCH is mapped to physical downlink shared channel (Physical Downlink Shared Channel, PDSCH), where 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 (HARQ) operations.
  • HARQ Hybrid Automatic Repeat reQuest
  • the 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 radio frames and subframes for scheduling the SC-MCCH.
  • SFN represents the system frame number of the radio frame
  • mcch-RepetitionPeriod represents the repetition period of SC-MCCH
  • mcch-Offset represents SC-MCCH The offset.
  • the subframe for scheduling SC-MCCH is indicated by sc-mcch-Subframe.
  • the SC-MCCH is scheduled through the Physical Downlink Control Channel (PDCCH).
  • a new radio network temporary identity Radio Network Tempory Identity, RNTI
  • SC-RNTI Single Cell RNTI
  • SC-N-RNTI Single Cell Notification RNTI
  • the SC -N-RNTI has a fixed value of FFFB; further, one of the 8 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 is configured with the SC-MTCH, and the SC-MTCH is used to transmit service data.
  • the SC-MCCH only transmits one message (that is, 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 (seession id), group RNTI (Group RNTI, G-RNTI), discontinuous reception (Discontinuous Reception, DRX) configuration information And the SC-PTM business information of the neighboring cell, etc.
  • TMGI Temporary Mobile Group Identity
  • SCPTMConfiguration Session id
  • group RNTI Group RNTI
  • G-RNTI Group RNTI
  • DRX discontinuous reception
  • the SC-PTM business information of the neighboring cell etc.
  • ROHC Robust Header Compression
  • the downlink discontinuous reception of SC-PTM is controlled by the following parameters: onDurationTimerSCPTM, drx-InactivityTimerSCPTM, SC-MTCH-SchedulingCycle, and SC-MTCH-SchedulingOffset.
  • SC-PTM service continuity adopts the concept of MBMS service continuity based on SIB15, namely "SIB15+MBMSInterestIndication" mode.
  • the service continuity of the UE in the idle state is based on the concept of frequency priority.
  • the first SIB includes the configuration information of the first MCCH.
  • the first MCCH is the control channel of the MBMS service.
  • the first SIB is used to configure the configuration information of the control channel of NR MBMS.
  • the control channel of NR MBMS may also be called NR MCCH (that is, the first MCCH).
  • the first MCCH is used to carry the first signaling.
  • 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 of the MBMS service (also referred to as a data channel or a transmission channel), and 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 NR MBMS traffic channel.
  • the NR MBMS traffic channel may also be called NR MTCH (that is, the first MTCH).
  • the first signaling is used to configure a NR MBMS service channel, service information corresponding to the service channel, and scheduling information corresponding to the service channel.
  • the service information corresponding to the service channel for example, TMGI, session id, and other identification information identifying the service.
  • 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, etc.
  • the transmission of the first MCCH and the first MTCH is scheduled based on the PDCCH.
  • the RNTI used for scheduling the PDCCH of the first MCCH uses a unique identifier of the entire network, that is, a fixed value.
  • the RNTI used by the PDCCH for scheduling the first MTCH is configured through the first MCCH.
  • the embodiment of the present application does not impose restrictions on 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.
  • the PDCCH used to schedule the MCCH is configured through the SIB. (Ie MCCH PDCCH) and notification PDCCH, wherein the DCI carried by MCCH PDCCH is used to schedule the PDSCH (ie MCCH PDSCH) used to transmit the MCCH.
  • M PDCCHs (ie MTCH 1PDCCH, MTCH 2PDCCH, ..., MTCH M PDCCH) for scheduling MTCH are configured through the MCCH, where the DCI carried by the MTCH n PDCCH schedules the PDSCH used to transmit the MTCH n (ie MTCH n PDSCH) , N is an integer greater than or equal to 1 and less than or equal to M. 4, MCCH and MTCH are mapped to DL-SCH, and further, DL-SCH is mapped to PDSCH, where MCCH and MTCH belong to logical channels, DL-SCH belongs to transport channels, and PDSCH belongs to physical channels.
  • Fig. 5 is a schematic flow chart 1 of the service data transmission method provided by an embodiment of the application. As shown in Fig. 5, the service data transmission method includes the following steps:
  • Step 501 The terminal device receives the MBMS service data of the first cell and the MBMS service data of the second cell before the cell change.
  • the first cell is the cell before the cell change
  • the second cell is the cell after the cell change.
  • the cell change refers to cell reselection or cell handover.
  • the terminal device has strong communication capabilities.
  • the terminal device can support multiple bands and/or band combinations.
  • the terminal device has the ability to support multiple radio frequency channels. Based on this, the terminal device has the ability to receive MBMS service data of two cells at the cell edge at the same time.
  • the terminal device when the terminal device is at the edge of a cell (such as the junction between the first cell and the second cell), the terminal device keeps receiving the current cell (that is, the second cell) before the cell change.
  • the MBMS service data of one cell Under the premise of the MBMS service data of one cell, the MBMS service data of the neighboring cell (that is, the second cell) is simultaneously received.
  • the terminal device in order to be able to receive the MBMS service data of the second cell, the terminal device needs to obtain the MBMS configuration information of the second cell before the cell change, and the MBMS configuration information of the second cell is used for The terminal device receives the MBMS service data of the second cell.
  • the terminal device may obtain the MBMS configuration information of the second cell in any of the following ways:
  • Manner 1 Before the cell change, the terminal device obtains the MBMS configuration information of the second cell from the first cell.
  • the first cell broadcasts the first SIB
  • the first SIB includes not only the configuration information of the first MCCH of the first cell, but also the configuration information of the second MCCH of the second cell
  • the terminal equipment The second MCCH is received based on the configuration information of the second MCCH, and the configuration information of the second MTCH is acquired based on the second MCCH.
  • the terminal device receives the second MTCH based on the configuration information of the second MTCH. Two MTCH, the second MTCH is used to transmit MBMS service data on the second cell side.
  • the first cell broadcasts a first SIB
  • the first SIB includes not only the configuration information of the first MCCH of the first cell, but also the configuration information of the second MTCH of the second cell
  • the terminal The device receives the second MTCH based on the configuration information of the second MTCH, where the second MTCH is used to transmit MBMS service data on the second cell side.
  • the second MCCH and the second MTCH here can be understood with reference to the description of the first MCCH and the first MTCH. Among them, “first” and “second” are used to distinguish two different cells, and the concepts are similar.
  • the terminal device Before the cell change, the terminal device obtains the MBMS configuration information of the second cell from the neighboring cell of the first cell.
  • the neighboring cell of the first cell is the second cell
  • the second cell broadcasts a second SIB
  • the second SIB includes the configuration information of the second MCCH of the second cell
  • the terminal device is based on the The configuration information of the second MCCH receives the second MCCH, and obtains the configuration information of the second MTCH based on the second MCCH, and then, the terminal device receives the second MTCH based on the configuration information of the second MTCH
  • the second MTCH is used to transmit MBMS service data on the second cell side.
  • the second MCCH and the second MTCH here can be understood with reference to the description of the first MCCH and the first MTCH. Among them, “first” and “second” are used to distinguish two different cells, and the concepts are similar.
  • Step 502 The terminal device stops receiving the MBMS service data of the first cell after the cell is changed.
  • the terminal device stops receiving the MBMS service data of the first cell after the cell is changed.
  • the terminal device continues to receive the MBMS service data of the second cell.
  • the MBMS service data of the first cell and the MBMS service data of the second cell have the same TMGI and/or session identifier, that is, the MBMS service data of the first cell and the MBMS service data of the second cell have the same TMGI and/or session identifier.
  • the MBMS service data of the second cell is the same in content.
  • the terminal device after the cell is changed, the terminal device has completely moved within the coverage area of the second cell. At this time, it can stop receiving the MBMS service data of the first cell, and optionally, continue to receive the first cell. MBMS service data of the second cell.
  • Fig. 6 is a schematic diagram of the second process of the service data transmission method provided by an embodiment of the application. As shown in Fig. 6, the service data transmission method includes the following steps:
  • Step 601 The terminal device receives the first MBMS service data and the second MBMS service data of the first cell, the second MBMS service data is the same as the first MBMS service data, and the transmission of the second MBMS service data starts The start time is later than the transmission start time of the first MBMS service data.
  • a cell transmits two copies of the same MBMS service data at the same time.
  • the two copies of MBMS service data have the same MBMS configuration information.
  • the difference is that there is a certain time interval between the two copies of MBMS service data in spatial transmission, such as As shown in Figure 7-1, the first cell transmits two copies of the same MBMS service data at the same time, that is, the first MBMS service data and the second MBMS service data.
  • the transmission start time of the second MBMS service data is later than the first MBMS service data.
  • the transmission start time, the time interval between the two is t.
  • the first MBMS service data is primary service data of the first cell
  • the second MBMS service data is secondary service data of the first cell.
  • the terminal device preferentially performs receiving processing on the first MBMS service data, and when it detects that the reception of the first MBMS service data fails, it performs receiving processing on the second MBMS service data.
  • the "receiving processing” here refers to processing related to decoding, detecting whether packets are lost, and presenting business data.
  • the detecting that the reception of the first MBMS service data fails includes: detecting that the first MBMS service data has packet loss; or, the decoding of the first MBMS service data fails.
  • the terminal device receives the main service data and the auxiliary service data at the same time in the first cell, wherein the transmission start time of the main service data is earlier than the transmission start time of the auxiliary service data, and the main service data is received and processed first If it is found that a certain data packet in the main service data is lost or the decoding fails, the missing data packet or the data packet that has failed to be decoded can be retrieved from the auxiliary service data, so as to meet the purpose of service data transmission reliability.
  • the terminal device changes from the first cell to the second cell, and receives third MBMS service data and fourth MBMS service data of the second cell, and the fourth MBMS service data It is the same as the third MBMS service data, and the transmission start time of the fourth MBMS service data is later than the transmission start time of the third MBMS service data.
  • the second cell is the same as the first cell, and also sends two copies of the same MBMS service data at the same time, that is, the third MBMS service data and the fourth MBMS service data, where the third MBMS service data is the second MBMS service data.
  • the primary service data of the cell, and the fourth MBMS service data is the secondary service data of the second cell.
  • the cell change in the embodiment of the present application refers to cell reselection or cell handover.
  • the terminal device receives and processes the fourth MBMS service data during the process of changing from the first cell to the second cell; after the terminal device changes from the first cell to the second cell, Perform receiving processing on the third MBMS service data.
  • the terminal device when the terminal device changes from the first cell to the second cell, the terminal device preferentially receives and processes the secondary service data of the second cell, which can compensate for the service interruption caused by the delay of the cell change Or business delays and other issues.
  • the terminal device After the terminal device changes from the first cell to the second cell, the terminal device preferentially receives and processes the main service data of the second cell, so as to ensure that if the terminal device finds that a certain data packet in the main service data is lost or decoded If it fails, you can retrieve the lost data packets or the data packets that have failed to decode from the auxiliary service data, so as to meet the purpose of service data transmission reliability; on the other hand, it can also make up for the next cell change. Problems such as business interruption or business delay brought by.
  • the terminal device always receives the main service data and the auxiliary service data sent by the cell.
  • the premise for the terminal device to receive the main service data and the auxiliary service data is to obtain the MBMS configuration information of the cell.
  • the corresponding MBMS configuration information can be understood with reference to the description of the foregoing solution.
  • FIG. 8 is a schematic diagram 1 of the structural composition of a service data transmission device provided by an embodiment of the application. As shown in FIG. 8, the service data transmission device includes:
  • the receiving unit 801 is configured to receive the MBMS service data of the first cell and the MBMS service data of the second cell before the cell change; stop receiving the MBMS service data of the first cell after the cell change;
  • the first cell is a cell before a cell change
  • the second cell is a cell after a cell change
  • the device further includes:
  • the obtaining unit 802 is configured to obtain the MBMS configuration information of the second cell before the cell change, and the MBMS configuration information of the second cell is used by the terminal device to receive the MBMS service data of the second cell.
  • the obtaining unit 802 is configured to obtain the MBMS configuration information of the second cell from the first cell before the cell change; or, before the cell change, obtain the MBMS configuration information from the first cell.
  • the neighboring cell of the cell obtains the MBMS configuration information of the second cell.
  • the MBMS service data of the first cell and the MBMS service data of the second cell have the same TMGI and/or session identifier.
  • the cell change refers to cell reselection or cell handover.
  • FIG. 9 is a schematic diagram 2 of the structural composition of the service data transmission device provided by the embodiment of the application. As shown in FIG. 9, the service data transmission device includes:
  • the receiving unit 901 is configured to receive first MBMS service data and second MBMS service data of the first cell, where the second MBMS service data is the same as the first MBMS service data, and the transmission of the second MBMS service data The start time is later than the transmission start time of the first MBMS service data.
  • the device further includes:
  • the processing unit 902 is configured to perform receiving processing on the first MBMS service data, and perform receiving processing on the second MBMS service data in a case where it is detected that the reception of the first MBMS service data fails.
  • the detecting that the reception of the first MBMS service data fails includes:
  • the decoding of the first MBMS service data fails.
  • the first MBMS service data is primary service data of the first cell
  • the second MBMS service data is secondary service data of the first cell
  • the receiving unit 901 is further configured to change from the first cell to the second cell, and receive the third MBMS service data and the fourth MBMS service data of the second cell, and the The fourth MBMS service data is the same as the third MBMS service data, and the transmission start time of the fourth MBMS service data is later than the transmission start time of the third MBMS service data.
  • the device further includes:
  • the processing unit 902 is configured to receive and process the fourth MBMS service data during the process of changing from the first cell to the second cell; after changing from the first cell to the second cell, perform processing on the first cell Three MBMS service data are received and processed.
  • the third MBMS service data is primary service data of the second cell
  • the fourth MBMS service data is secondary service data of the second cell.
  • the cell change refers to cell reselection or cell handover.
  • FIG. 10 is a schematic structural diagram of a communication device 1000 according to an embodiment of the present application.
  • the communication device may be a terminal device or a network device.
  • the communication device 1000 shown in FIG. 10 includes a processor 1010.
  • the processor 1010 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the communication device 1000 may further include a memory 1020.
  • the processor 1010 can call and run a computer program from the memory 1020 to implement the method in the embodiment of the present application.
  • the memory 1020 may be a separate device independent of the processor 1010, or it may be integrated in the processor 1010.
  • the communication device 1000 may further include a transceiver 1030, and the processor 1010 may control the transceiver 1030 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.
  • the transceiver 1030 may include a transmitter and a receiver.
  • the transceiver 1030 may further include an antenna, and the number of antennas may be one or more.
  • the communication device 1000 may specifically be a network device of an embodiment of the application, and the communication device 1000 may implement the corresponding process implemented by the network device in each method of the embodiment of the application. For the sake of brevity, details are not repeated here. .
  • the communication device 1000 may specifically be a mobile terminal/terminal device of an embodiment of the present application, and the communication device 1000 may implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application.
  • I won’t repeat it here.
  • FIG. 11 is a schematic structural diagram of a chip of an embodiment of the present application.
  • the chip 1100 shown in FIG. 11 includes a processor 1110, and the processor 1110 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the chip 1100 may further include a memory 1120.
  • the processor 1110 can call and run a computer program from the memory 1120 to implement the method in the embodiment of the present application.
  • the memory 1120 may be a separate device independent of the processor 1110, or may be integrated in the processor 1110.
  • the chip 1100 may further include an input interface 1130.
  • the processor 1110 can control the input interface 1130 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.
  • the chip 1100 may further include an output interface 1140.
  • the processor 1110 can control the output interface 1140 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
  • the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application.
  • the chip mentioned in the embodiment of the present application may also be referred to as a system-level chip, a system-on-chip, a system-on-chip, or a system-on-chip, etc.
  • FIG. 12 is a schematic block diagram of a communication system 1200 according to an embodiment of the present application. As shown in FIG. 12, the communication system 1200 includes a terminal device 1210 and a network device 1220.
  • the terminal device 1210 can be used to implement the corresponding function implemented by the terminal device in the above method
  • the network device 1220 can be used to implement the corresponding function implemented by the network device in the above method. For brevity, it will not be repeated here. .
  • the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability.
  • the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC application specific integrated circuit
  • FPGA Field Programmable Gate Array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • 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 the embodiments 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 can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • DDR SDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • Enhanced SDRAM, ESDRAM Enhanced Synchronous Dynamic Random Access Memory
  • Synchronous Link Dynamic Random Access Memory Synchronous Link Dynamic Random Access Memory
  • DR RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous 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 to say, the memory in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.
  • the embodiment of the present application also provides a computer-readable storage medium for storing computer programs.
  • the computer-readable storage medium can be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application , For the sake of brevity, I won’t repeat it here.
  • the 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 embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program product can be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, For the sake of brevity, I will not repeat them here.
  • the embodiment of the present application also provides a computer program.
  • the computer program can be applied to the network device in the embodiment of the present application.
  • the computer program runs on the computer, it causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • I won’t repeat it here.
  • the computer program can be applied to the mobile terminal/terminal device in the embodiment of the present application.
  • the computer program runs on the computer, the computer executes each method in the embodiment of the present application. For the sake of brevity, the corresponding process will not be repeated here.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, 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 the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: 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 code .

Landscapes

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

Abstract

本申请实施例提供一种业务数据传输方法及装置、终端设备，该方法包括：终端设备在小区变更前接收第一小区的多媒体广播多播服务MBMS业务数据以及第二小区的MBMS业务数据；所述终端设备在小区变更后停止接收所述第一小区的MBMS业务数据；其中，所述第一小区为小区变更前的小区，所述第二小区为小区变更后的小区。

Description

一种业务数据传输方法及装置、终端设备 技术领域
本申请实施例涉及移动通信技术领域，具体涉及一种业务数据传输方法及装置、终端设备。
背景技术
多媒体广播多播服务(Multimedia Broadcast Multicast Service，MBMS)是一种通过共享网络资源从一个数据源向多个用户传送数据的技术，该技术在提供多媒体业务的同时能有效地利用网络资源，实现较高速率(如256kbps)的多媒体业务的广播和组播。
在新无线(New Radio，NR)系统中，很多场景需要支持组播和广播的业务需求，例如车联网中，工业互联网中等。所以在NR中引入MBMS是有必要的。对于NR中的MBMS业务，当终端设备在小区变更前后，由于处于小区边缘，而小区边缘的信号质量很差，会导致MBMS业务接收失败的问题。另一方面，在小区变更前后，两个小区的MBMS业务的数据有不对齐的问题。此外，在小区变更前后，由于MBMS配置信息的更新会导致MBMS业务数据丢失的问题。
发明内容
本申请实施例提供一种业务数据传输方法及装置、终端设备。
本申请实施例提供的业务数据传输方法，包括：
终端设备在小区变更前接收第一小区的MBMS业务数据以及第二小区的MBMS业务数据；
所述终端设备在小区变更后停止接收所述第一小区的MBMS业务数据；
其中，所述第一小区为小区变更前的小区，所述第二小区为小区变更后的小区。
本申请实施例提供的业务数据传输方法，包括：
终端设备接收第一小区的第一MBMS业务数据和第二MBMS业务数据，所述第二MBMS业务数据与所述第一MBMS业务数据相同，且所述第二MBMS业务数据的传输起始时间晚于所述第一MBMS业务数据的传输起始时间。
本申请实施例提供的业务数据传输装置，包括：
接收单元，用于在小区变更前接收第一小区的MBMS业务数据以及第二小区的MBMS业务数据；在小区变更后停止接收所述第一小区的MBMS业务数据；
其中，所述第一小区为小区变更前的小区，所述第二小区为小区变更后的小区。
本申请实施例提供的业务数据传输装置，包括：
接收单元，用于接收第一小区的第一MBMS业务数据和第二MBMS业务数据，所述第二MBMS业务数据与所述第一MBMS业务数据相同，且所述第二MBMS业务数据的传输起始时间晚于所述第一MBMS业务数据的传输起始时间。
本申请实施例提供的终端设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述的业务数据传输方法。
本申请实施例提供的芯片，用于实现上述的业务数据传输方法。
具体地，该芯片包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片的设备执行上述的业务数据传输方法。
本申请实施例提供的计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述的业务数据传输方法。
本申请实施例提供的计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行上述的业务数据传输方法。
本申请实施例提供的计算机程序，当其在计算机上运行时，使得计算机执行上述的业务数据传输方法。
通过上述技术方案，使得NR系统中支持MBMS业务的广播和组播，与此同时，提出一种方案，即在小区变更前，终端设备同时接收小区变更前的小区(即第一小区)的MBMS业务数据以及小区变更后的小区(即第二小区)的MBMS业务数据，保证MBMS业务数据传输的可靠性。另一方面，提出一种方案，即一个小区同时发送两份MBMS业务数据，一份MBMS业务数据作为主业务数据，另一份MBMS业务数据作为辅业务数据，从而也可以保证数据传输的可靠性。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1是本申请实施例提供的一种通信系统架构的示意性图；
图2是本申请实施例提供的第一SIB相关配置的示意图；
图3是本申请实施例提供的PTM配置传输机制的示意图；
图4是本申请实施例提供的PTM信道及其映射图；
图5为本申请实施例提供的业务数据传输方法的流程示意图一；
图6为本申请实施例提供的业务数据传输方法的流程示意图二；
图7-1为本申请实施例提供的主业务数据和辅业务数据的示意图一；
图7-2为本申请实施例提供的主业务数据和辅业务数据的示意图二；
图8为本申请实施例提供的业务数据传输装置的结构组成示意图一；
图9为本申请实施例提供的业务数据传输装置的结构组成示意图二；
图10是本申请实施例提供的一种通信设备示意性结构图；
图11是本申请实施例的芯片的示意性结构图；
图12是本申请实施例提供的一种通信系统的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请实施例的技术方案可以应用于各种通信系统，例如：长期演进(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的典型特点包括：高连接密度，小数据量，时延不敏感业务，模块的低成本和长使用寿命等。
Figure PCTCN2019106510-appb-000001
RRC状态
5G为了降低空口信令和快速恢复无线连接，快速恢复数据业务的目的，定义了一个新的无线资源控制(Radio Resource Control，RRC)状态，即RRC非激活(RRC_INACTIVE)状态。这种状态有别于RRC空闲(RRC_IDLE)状态和RRC激活(RRC_ACTIVE)状态。其中，
1)RRC_IDLE状态(简称为空闲(idle)态)：移动性为基于UE的小区选择重选，寻呼由核心网(Core Network，CN)发起，寻呼区域由CN配置。基站侧不存在UE上下文，不存在RRC连接。
2)RRC_CONNECTED状态(简称为连接(connected)态)：存在RRC连接，基站侧和UE侧存在UE上下文。网络侧知道UE的位置是具体小区级别的。移动性是网络侧控制的移动性。UE和基站之间可以传输单播数据。
3)RRC_INACTIVE状态(简称为非激活(inactive)态)：移动性为基于UE的小区选择重选，存在CN-NR之间的连接，UE上下文存在某个基站上，寻呼由RAN触发，基于RAN的寻呼区域由RAN管理，网络侧知道UE的位置是基于RAN的寻呼区域级别的。
Figure PCTCN2019106510-appb-000002
MBMS
3GPP版本6(Release 6，R6)中引入了MBMS，MBMS是一种通过共享网络资源从一个数据源向多个UE传送数据的技术，该技术在提供多媒体业务的同时能有效地利用网络资源，实现较高速率(如256kbps)的多媒体业务的广播和组播。
由于3GPP R6中的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的业务连续性基于频率优先级的概念。
在NR中，很多场景需要支持组播和广播的业务需求，例如车联网中，工业互联网中等。所以在NR中引入MBMS是有必要的。对于NR中的MBMS业务，当终端设备在小区变更前后，由于处于小区边缘，而小区边缘的信号质量很差，会导致MBMS业 务接收失败的问题。另一方面，在小区变更前后，两个小区的MBMS业务的数据有不对齐的问题。此外，在小区变更前后，由于MBMS配置信息的更新会导致MBMS业务数据丢失的问题。为了确保MBMS业务数据接收的可靠性，需要引入一定的机制。为此，提出了本申请实施例的以下技术方案。
本申请实施例的技术方案中，定义一个新的SIB(称为第一SIB)，参照图2，第一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，参照图3，通过SIB配置用于调度MCCH的PDCCH(即MCCH PDCCH)以及通知PDCCH，其中，通过MCCH PDCCH携带的DCI调度用于传输MCCH的PDSCH(即MCCH PDSCH)。进一步，通过MCCH配置M个用于调度MTCH的PDCCH(即MTCH 1PDCCH、MTCH 2PDCCH、…、MTCH M PDCCH)，其中，MTCH n PDCCH携带的DCI调度用于传输MTCH n的PDSCH(即MTCH n PDSCH)，n为大于等于1且小于等于M的整数。参照图4，MCCH和MTCH被映射到DL-SCH上，进一步，DL-SCH被映射到PDSCH上，其中，MCCH和MTCH属于逻辑信道，DL-SCH属于传输信道，PDSCH属于物理信道。
图5为本申请实施例提供的业务数据传输方法的流程示意图一，如图5所示，所述业务数据传输方法包括以下步骤：
步骤501：终端设备在小区变更前接收第一小区的MBMS业务数据以及第二小区的MBMS业务数据。
本申请实施例中，所述第一小区为小区变更前的小区，所述第二小区为小区变更后的小区。进一步，可选地，所述小区变更指小区重选或小区切换。
本申请实施例中，所述终端设备具有较强的通信能力，例如所述终端设备能够支持多个频带(band)和/或band组合，例如所述终端设备具备支持多个射频通道的能力。基于此，所述终端设备具有在小区边缘同时接收两个小区的MBMS业务数据的能力。
本申请实施例中，所述终端设备处于小区边缘(如第一小区和第二小区之间的交界处)的情况下，所述终端设备在小区变更前，保持接收当前小区(即所述第一小区)的MBMS业务数据的前提下，同时接收邻区(即所述第二小区)的MBMS业务数据。
本申请实施例中，所述终端设备为了能够接收所述第二小区的MBMS业务数据， 需要在小区变更前获取所述第二小区的MBMS配置信息，所述第二小区的MBMS配置信息用于所述终端设备接收所述第二小区的MBMS业务数据。
进一步，在一可选实施方式中，所述终端设备可以通过以下任意一种方式来获取所述第二小区的MBMS配置信息：
方式一：所述终端设备在小区变更前，从所述第一小区获取所述第二小区的MBMS配置信息。
在一个示例中，第一小区广播第一SIB，所述第一SIB不仅包括所述第一小区的第一MCCH的配置信息，还包括所述第二小区的第二MCCH的配置信息，终端设备基于所述第二MCCH的配置信息接收所述第二MCCH，并基于所述第二MCCH获取第二MTCH的配置信息，而后，所述终端设备基于所述第二MTCH的配置信息接收所述第二MTCH，所述第二MTCH用于传输所述第二小区侧的MBMS业务数据。
在另一个示例中，第一小区广播第一SIB，所述第一SIB不仅包括所述第一小区的第一MCCH的配置信息，还包括所述第二小区的第二MTCH的配置信息，终端设备基于所述第二MTCH的配置信息接收所述第二MTCH，所述第二MTCH用于传输所述第二小区侧的MBMS业务数据。
需要说明的是，这里的第二MCCH第二MTCH可以参照第一MCCH第一MTCH的描述进行理解。其中，“第一”和“第二”是为了区分两个不同小区，其概念是类似的。
方式二：所述终端设备在小区变更前，从所述第一小区的邻区获取所述第二小区的MBMS配置信息。
在一个示例中，所述第一小区的邻区为第二小区，第二小区广播第二SIB，所述第二SIB包括所述第二小区的第二MCCH的配置信息，终端设备基于所述第二MCCH的配置信息接收所述第二MCCH，并基于所述第二MCCH获取第二MTCH的配置信息，而后，所述终端设备基于所述第二MTCH的配置信息接收所述第二MTCH，所述第二MTCH用于传输所述第二小区侧的MBMS业务数据。
需要说明的是，这里的第二MCCH第二MTCH可以参照第一MCCH第一MTCH的描述进行理解。其中，“第一”和“第二”是为了区分两个不同小区，其概念是类似的。
步骤502：所述终端设备在小区变更后停止接收所述第一小区的MBMS业务数据。
本申请实施例中，所述终端设备在小区变更后停止接收所述第一小区的MBMS业务数据，可选地，所述终端设备继续接收所述第二小区的MBMS业务数据。
本申请实施例中，所述第一小区的MBMS业务数据和所述第二小区的MBMS业务数据具有相同的TMGI和/或会话标识，也就是说所述第一小区的MBMS业务数据和所述第二小区的MBMS业务数据在内容上是相同的。
本申请实施例中，所述终端设备在小区变更后，完全移动了第二小区覆盖的范围内，此时可以停止接收所述第一小区的MBMS业务数据，可选地，继续接收所述第二小区的MBMS业务数据。
图6为本申请实施例提供的业务数据传输方法的流程示意图二，如图6所示，所述业务数据传输方法包括以下步骤：
步骤601：终端设备接收第一小区的第一MBMS业务数据和第二MBMS业务数据，所述第二MBMS业务数据与所述第一MBMS业务数据相同，且所述第二MBMS业务数据的传输起始时间晚于所述第一MBMS业务数据的传输起始时间。
本申请实施例中，一个小区同时传输两份相同的MBMS业务数据，这两份MBMS业务数据具有相同的MBMS配置信息，区别在于这两份MBMS业务数据在空间传输上 存在一定的时间间隔，如图7-1所示，第一小区同时传输两份相同的MBMS业务数据，即第一MBMS业务数据和第二MBMS业务数据，第二MBMS业务数据的传输起始时间晚于第一MBMS业务数据的传输起始时间，两者的时间间隔为t。进一步，所述第一MBMS业务数据为所述第一小区的主业务数据，所述第二MBMS业务数据为所述第一小区的辅业务数据。
本申请实施例中，所述终端设备优先对所述第一MBMS业务数据进行接收处理，检测到所述第一MBMS业务数据接收失败的情况下，对所述第二MBMS业务数据进行接收处理。这里的“接收处理”是指进行解码、检测是否丢包、以及对业务数据进行呈现等相关的处理。
在一可选实施方式中，所述检测到所述第一MBMS业务数据接收失败，包括：检测到所述第一MBMS业务数据存在丢包；或者，对所述第一MBMS业务数据解码失败。
具体地，终端设备在第一小区内，同时接收主业务数据和辅业务数据，其中，主业务数据的传输起始时间早于辅业务数据的传输起始时间，优先对主业务数据进行接收处理，如果发现主业务数据中的某个数据包丢失或者解码失败，则可以从辅业务数据中重新获取丢失的数据包或者解码失败的数据包，从而满足业务数据传输可靠性的目的。
在一可选实施方式中，所述终端设备从所述第一小区变更到第二小区，接收所述第二小区的第三MBMS业务数据和第四MBMS业务数据，所述第四MBMS业务数据与所述第三MBMS业务数据相同，且所述第四MBMS业务数据的传输起始时间晚于所述第三MBMS业务数据的传输起始时间。
这里，第二小区与第一小区同理，也是同时发送两份相同的MBMS业务数据，即第三MBMS业务数据和第四MBMS业务数据，其中，所述第三MBMS业务数据为所述第二小区的主业务数据，所述第四MBMS业务数据为所述第二小区的辅业务数据。
需要说明的是，本申请实施例中的所述小区变更指小区重选或小区切换。
进一步，所述终端设备从所述第一小区变更到第二小区的过程中，对所述第四MBMS业务数据进行接收处理；所述终端设备从所述第一小区变更到第二小区之后，对所述第三MBMS业务数据进行接收处理。
参照图7-2，终端设备从所述第一小区变更到第二小区的过程中，终端设备优先对第二小区的辅业务数据进行接收处理，这样可以弥补小区变更时延带来的业务中断或业务时延等问题。在终端设备从所述第一小区变更到第二小区之后，终端设备优先对第二小区的主业务数据进行接收处理，这样可以保证终端设备如果发现主业务数据中的某个数据包丢失或者解码失败，则可以从辅业务数据中重新获取丢失的数据包或者解码失败的数据包，从而满足业务数据传输可靠性的目的；另一方面，也可以弥补在下一次小区变更时依然能够弥补因小区变更带来的业务中断或业务时延等问题。
需要说明的是，无论终端设备接入哪个小区，终端设备始终接收该小区发送的主业务数据和辅业务数据。此外，终端设备接收主业务数据和辅业务数据的前提是，获取到该小区的MBMS配置信息，对应MBMS配置信息的获取，可以参照前述方案的描述进行理解。
图8为本申请实施例提供的业务数据传输装置的结构组成示意图一，如图8所示，所述业务数据传输装置包括：
接收单元801，用于在小区变更前接收第一小区的MBMS业务数据以及第二小区的MBMS业务数据；在小区变更后停止接收所述第一小区的MBMS业务数据；
其中，所述第一小区为小区变更前的小区，所述第二小区为小区变更后的小区。
在一可选实施方式中，所述装置还包括：
获取单元802，用于在小区变更前获取所述第二小区的MBMS配置信息，所述第二小区的MBMS配置信息用于所述终端设备接收所述第二小区的MBMS业务数据。
在一可选实施方式中，所述获取单元802，用于在小区变更前，从所述第一小区获取所述第二小区的MBMS配置信息；或者，在小区变更前，从所述第一小区的邻区获取所述第二小区的MBMS配置信息。
在一可选实施方式中，所述第一小区的MBMS业务数据和所述第二小区的MBMS业务数据具有相同的TMGI和/或会话标识。
在一可选实施方式中，所述小区变更指小区重选或小区切换。
本领域技术人员应当理解，本申请实施例的上述业务数据传输装置的相关描述可以参照本申请实施例的业务数据传输方法的相关描述进行理解。
图9为本申请实施例提供的业务数据传输装置的结构组成示意图二，如图9所示，所述业务数据传输装置包括：
接收单元901，用于接收第一小区的第一MBMS业务数据和第二MBMS业务数据，所述第二MBMS业务数据与所述第一MBMS业务数据相同，且所述第二MBMS业务数据的传输起始时间晚于所述第一MBMS业务数据的传输起始时间。
在一可选实施方式中，所述装置还包括：
处理单元902，用于对所述第一MBMS业务数据进行接收处理，检测到所述第一MBMS业务数据接收失败的情况下，对所述第二MBMS业务数据进行接收处理。
在一可选实施方式中，所述检测到所述第一MBMS业务数据接收失败，包括：
检测到所述第一MBMS业务数据存在丢包；或者，
对所述第一MBMS业务数据解码失败。
在一可选实施方式中，所述第一MBMS业务数据为所述第一小区的主业务数据，所述第二MBMS业务数据为所述第一小区的辅业务数据。
在一可选实施方式中，所述接收单元901，还用于从所述第一小区变更到第二小区，接收所述第二小区的第三MBMS业务数据和第四MBMS业务数据，所述第四MBMS业务数据与所述第三MBMS业务数据相同，且所述第四MBMS业务数据的传输起始时间晚于所述第三MBMS业务数据的传输起始时间。
在一可选实施方式中，所述装置还包括：
处理单元902，用于从所述第一小区变更到第二小区的过程中，对所述第四MBMS业务数据进行接收处理；从所述第一小区变更到第二小区之后，对所述第三MBMS业务数据进行接收处理。
在一可选实施方式中，所述第三MBMS业务数据为所述第二小区的主业务数据，所述第四MBMS业务数据为所述第二小区的辅业务数据。
在一可选实施方式中，所述小区变更指小区重选或小区切换。
本领域技术人员应当理解，本申请实施例的上述业务数据传输装置的相关描述可以参照本申请实施例的业务数据传输方法的相关描述进行理解。
图10是本申请实施例提供的一种通信设备1000示意性结构图。该通信设备可以是终端设备，也可以是网络设备，图10所示的通信设备1000包括处理器1010，处理器1010可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图10所示，通信设备1000还可以包括存储器1020。其中，处理器1010可以从存储器1020中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器1020可以是独立于处理器1010的一个单独的器件，也可以集成在处 理器1010中。
可选地，如图10所示，通信设备1000还可以包括收发器1030，处理器1010可以控制该收发器1030与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器1030可以包括发射机和接收机。收发器1030还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该通信设备1000具体可为本申请实施例的网络设备，并且该通信设备1000可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该通信设备1000具体可为本申请实施例的移动终端/终端设备，并且该通信设备1000可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
图11是本申请实施例的芯片的示意性结构图。图11所示的芯片1100包括处理器1110，处理器1110可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图11所示，芯片1100还可以包括存储器1120。其中，处理器1110可以从存储器1120中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器1120可以是独立于处理器1110的一个单独的器件，也可以集成在处理器1110中。
可选地，该芯片1100还可以包括输入接口1130。其中，处理器1110可以控制该输入接口1130与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
可选地，该芯片1100还可以包括输出接口1140。其中，处理器1110可以控制该输出接口1140与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该芯片可应用于本申请实施例中的网络设备，并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该芯片可应用于本申请实施例中的移动终端/终端设备，并且该芯片可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
图12是本申请实施例提供的一种通信系统1200的示意性框图。如图12所示，该通信系统1200包括终端设备1210和网络设备1220。
其中，该终端设备1210可以用于实现上述方法中由终端设备实现的相应的功能，以及该网络设备1220可以用于实现上述方法中由网络设备实现的相应的功能为了简洁，在此不再赘述。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(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 (31)

  1. 一种业务数据传输方法，所述方法包括：
    终端设备在小区变更前接收第一小区的多媒体广播多播服务MBMS业务数据以及第二小区的MBMS业务数据；
    所述终端设备在小区变更后停止接收所述第一小区的MBMS业务数据；
    其中，所述第一小区为小区变更前的小区，所述第二小区为小区变更后的小区。
  2. 根据权利要求1所述的方法，其中，所述方法还包括：
    终端设备在小区变更前获取所述第二小区的MBMS配置信息，所述第二小区的MBMS配置信息用于所述终端设备接收所述第二小区的MBMS业务数据。
  3. 根据权利要求2所述的方法，其中，所述终端设备在小区变更前获取所述第二小区的MBMS配置信息，包括：
    所述终端设备在小区变更前，从所述第一小区获取所述第二小区的MBMS配置信息；或者，
    所述终端设备在小区变更前，从所述第一小区的邻区获取所述第二小区的MBMS配置信息。
  4. 根据权利要求1至3中任一项所述的方法，其中，所述第一小区的MBMS业务数据和所述第二小区的MBMS业务数据具有相同的临时移动组标识TMGI和/或会话标识。
  5. 根据权利要求1至4中任一项所述的方法，其中，所述小区变更指小区重选或小区切换。
  6. 一种业务数据传输方法，所述方法包括：
    终端设备接收第一小区的第一MBMS业务数据和第二MBMS业务数据，所述第二MBMS业务数据与所述第一MBMS业务数据相同，且所述第二MBMS业务数据的传输起始时间晚于所述第一MBMS业务数据的传输起始时间。
  7. 根据权利要求6所述的方法，其中，所述方法还包括：
    所述终端设备对所述第一MBMS业务数据进行接收处理，检测到所述第一MBMS业务数据接收失败的情况下，对所述第二MBMS业务数据进行接收处理。
  8. 根据权利要求7所述的方法，其中，所述检测到所述第一MBMS业务数据接收失败，包括：
    检测到所述第一MBMS业务数据存在丢包；或者，
    对所述第一MBMS业务数据解码失败。
  9. 根据权利要求6至8中任一项所述的方法，其中，所述第一MBMS业务数据为所述第一小区的主业务数据，所述第二MBMS业务数据为所述第一小区的辅业务数据。
  10. 根据权利要求6至9中任一项所述的方法，其中，所述方法还包括：
    所述终端设备从所述第一小区变更到第二小区，接收所述第二小区的第三MBMS业务数据和第四MBMS业务数据，所述第四MBMS业务数据与所述第三MBMS业务数据相同，且所述第四MBMS业务数据的传输起始时间晚于所述第三MBMS业务数据的传输起始时间。
  11. 根据权利要求10所述的方法，其中，所述方法还包括：
    所述终端设备从所述第一小区变更到第二小区的过程中，对所述第四MBMS业务数据进行接收处理；
    所述终端设备从所述第一小区变更到第二小区之后，对所述第三MBMS业务数据进行接收处理。
  12. 根据权利要求10至11中任一项所述的方法，其中，所述第三MBMS业务数据为所述第二小区的主业务数据，所述第四MBMS业务数据为所述第二小区的辅业务数据。
  13. 根据权利要求10至12中任一项所述的方法，其中，所述小区变更指小区重选或小区切换。
  14. 一种业务数据传输装置，所述装置包括：
    接收单元，用于在小区变更前接收第一小区的MBMS业务数据以及第二小区的MBMS业务数据；在小区变更后停止接收所述第一小区的MBMS业务数据；
    其中，所述第一小区为小区变更前的小区，所述第二小区为小区变更后的小区。
  15. 根据权利要求14所述的装置，其中，所述装置还包括：
    获取单元，用于在小区变更前获取所述第二小区的MBMS配置信息，所述第二小区的MBMS配置信息用于所述终端设备接收所述第二小区的MBMS业务数据。
  16. 根据权利要求15所述的装置，其中，所述获取单元，用于在小区变更前，从所述第一小区获取所述第二小区的MBMS配置信息；或者，在小区变更前，从所述第一小区的邻区获取所述第二小区的MBMS配置信息。
  17. 根据权利要求14至16中任一项所述的装置，其中，所述第一小区的MBMS业务数据和所述第二小区的MBMS业务数据具有相同的TMGI和/或会话标识。
  18. 根据权利要求14至17中任一项所述的装置，其中，所述小区变更指小区重选或小区切换。
  19. 一种业务数据传输装置，所述装置包括：
    接收单元，用于接收第一小区的第一MBMS业务数据和第二MBMS业务数据，所述第二MBMS业务数据与所述第一MBMS业务数据相同，且所述第二MBMS业务数据的传输起始时间晚于所述第一MBMS业务数据的传输起始时间。
  20. 根据权利要求19所述的装置，其中，所述装置还包括：
    处理单元，用于对所述第一MBMS业务数据进行接收处理，检测到所述第一MBMS业务数据接收失败的情况下，对所述第二MBMS业务数据进行接收处理。
  21. 根据权利要求20所述的装置，其中，所述检测到所述第一MBMS业务数据接收失败，包括：
    检测到所述第一MBMS业务数据存在丢包；或者，
    对所述第一MBMS业务数据解码失败。
  22. 根据权利要求19至21中任一项所述的装置，其中，所述第一MBMS业务数据为所述第一小区的主业务数据，所述第二MBMS业务数据为所述第一小区的辅业务数据。
  23. 根据权利要求19至22中任一项所述的装置，其中，所述接收单元，还用于从所述第一小区变更到第二小区，接收所述第二小区的第三MBMS业务数据和第四MBMS业务数据，所述第四MBMS业务数据与所述第三MBMS业务数据相同，且所述第四MBMS业务数据的传输起始时间晚于所述第三MBMS业务数据的传输起始时间。
  24. 根据权利要求23所述的装置，其中，所述装置还包括：
    处理单元，用于从所述第一小区变更到第二小区的过程中，对所述第四MBMS业务数据进行接收处理；从所述第一小区变更到第二小区之后，对所述第三MBMS业务数据进行接收处理。
  25. 根据权利要求23至24中任一项所述的装置，其中，所述第三MBMS业务数据为所述第二小区的主业务数据，所述第四MBMS业务数据为所述第二小区的辅业务数据。
  26. 根据权利要求23至25中任一项所述的装置，其中，所述小区变更指小区重选或小区切换。
  27. 一种终端设备，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求1至5中任一项所述的方法，或者权利要求6至13中任一项所述的方法。
  28. 一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至5中任一项所述的方法，或者权利要求6至13中任一项所述的方法。
  29. 一种计算机可读存储介质，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1至5中任一项所述的方法，或者权利要求6至13中任一项所述的方法。
  30. 一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1至5中任一项所述的方法，或者权利要求6至13中任一项所述的方法。
  31. 一种计算机程序，所述计算机程序使得计算机执行如权利要求1至5中任一项所述的方法，或者权利要求6至13中任一项所述的方法。
PCT/CN2019/106510 2019-09-18 2019-09-18 一种业务数据传输方法及装置、终端设备 WO2021051321A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN201980100055.0A CN114342421A (zh) 2019-09-18 2019-09-18 一种业务数据传输方法及装置、终端设备
PCT/CN2019/106510 WO2021051321A1 (zh) 2019-09-18 2019-09-18 一种业务数据传输方法及装置、终端设备
US17/693,549 US20220210614A1 (en) 2019-09-18 2022-03-14 Service data transmission method and apparatus, and terminal device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/106510 WO2021051321A1 (zh) 2019-09-18 2019-09-18 一种业务数据传输方法及装置、终端设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/693,549 Continuation US20220210614A1 (en) 2019-09-18 2022-03-14 Service data transmission method and apparatus, and terminal device

Publications (1)

Publication Number Publication Date
WO2021051321A1 true WO2021051321A1 (zh) 2021-03-25

Family

ID=74883777

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/106510 WO2021051321A1 (zh) 2019-09-18 2019-09-18 一种业务数据传输方法及装置、终端设备

Country Status (3)

Country Link
US (1) US20220210614A1 (zh)
CN (1) CN114342421A (zh)
WO (1) WO2021051321A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11622239B2 (en) * 2019-11-01 2023-04-04 Qualcomm Incorporated TRS for multicast and broadcast

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102143434A (zh) * 2010-01-29 2011-08-03 电信科学技术研究院 发送系统信息和接收mbms的方法、系统及装置
CN102170610A (zh) * 2010-02-25 2011-08-31 电信科学技术研究院 发送指示信息和接收mbms的方法、系统及装置
US20140192702A1 (en) * 2011-08-12 2014-07-10 Kyocera Corporation Mobile communication method, mobile terminal, and processor

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102143434A (zh) * 2010-01-29 2011-08-03 电信科学技术研究院 发送系统信息和接收mbms的方法、系统及装置
CN102170610A (zh) * 2010-02-25 2011-08-31 电信科学技术研究院 发送指示信息和接收mbms的方法、系统及装置
US20140192702A1 (en) * 2011-08-12 2014-07-10 Kyocera Corporation Mobile communication method, mobile terminal, and processor

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SAMSUNG: "Corrections for MBMS reception in Receive Only Mode (ROM)", 3GPP DRAFT; 36.331_CR3886 (REL-15)_REV1 R2-1902452 CORRECTIONS FOR MBMS RECEPTION IN RECEIVE ONLY MODE (ROM), 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Athens, Greece; 20190225 - 20190301, 1 March 2019 (2019-03-01), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051597868 *

Also Published As

Publication number Publication date
CN114342421A (zh) 2022-04-12
US20220210614A1 (en) 2022-06-30

Similar Documents

Publication Publication Date Title
WO2021142647A1 (zh) 一种业务传输方法及装置、终端设备、网络设备
WO2021134316A1 (zh) 一种业务调度方法及装置、终端设备、网络设备
WO2021134298A1 (zh) 一种资源指示方法及装置、通信设备
WO2021056152A1 (zh) 一种信息配置方法及装置、终端设备、网络设备
WO2021051320A1 (zh) 一种业务数据传输方法及装置、网络设备、终端设备
WO2021138805A1 (zh) 一种业务同步调度方法及装置、通信设备
WO2021056155A1 (zh) 一种反馈资源配置方法及通信方法、装置、通信设备
WO2022006849A1 (zh) Mbs业务的tci状态管理方法及装置、终端设备
US20230361923A1 (en) Mbs service configuration method and terminal device
WO2022006875A1 (zh) 建立mbs业务的方法及装置、终端设备、网络设备
WO2021051312A1 (zh) 一种信息配置方法及装置、终端设备、网络设备
US20230276433A1 (en) Mcch scheduling transmission method and apparatus, and terminal device
WO2021051319A1 (zh) 一种drx配置方法及装置、终端设备、网络设备
WO2021056335A1 (zh) 一种接入控制方法及装置、终端设备、网络设备
US20220210614A1 (en) Service data transmission method and apparatus, and terminal device
WO2021142646A1 (zh) 一种业务传输方法及装置、通信设备
WO2022141088A1 (zh) 一种mbs业务的传输方法及装置、终端设备
WO2021051322A1 (zh) 一种bwp配置方法及装置、终端设备、网络设备
WO2021134291A1 (zh) 一种资源配置方法及装置、终端设备、网络设备
WO2021051316A1 (zh) 一种业务数据传输方法及装置、网络设备、终端设备
WO2021189458A1 (zh) 一种数据转发方法及装置、通信设备
WO2022165720A1 (zh) 提高mbs业务可靠性的方法及装置、终端设备、网络设备
WO2022226937A1 (zh) 一种mbs寻呼方法及装置、网络设备、终端设备
WO2022205454A1 (zh) 一种指示寻呼的方法及装置、终端设备、网络设备
WO2022141255A1 (zh) 一种mbs业务的配置方法及装置、网络设备、终端设备

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: 19945657

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: 19945657

Country of ref document: EP

Kind code of ref document: A1