WO2018201476A1 - 多播承载的管理方法和终端设备 - Google Patents

多播承载的管理方法和终端设备 Download PDF

Info

Publication number
WO2018201476A1
WO2018201476A1 PCT/CN2017/083323 CN2017083323W WO2018201476A1 WO 2018201476 A1 WO2018201476 A1 WO 2018201476A1 CN 2017083323 W CN2017083323 W CN 2017083323W WO 2018201476 A1 WO2018201476 A1 WO 2018201476A1
Authority
WO
WIPO (PCT)
Prior art keywords
mrb
mtch
data
terminal device
tmgi
Prior art date
Application number
PCT/CN2017/083323
Other languages
English (en)
French (fr)
Inventor
单宝堃
于映辉
罗林杰⋅奥黛尔
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to RU2019139457A priority Critical patent/RU2739290C1/ru
Priority to JP2019560654A priority patent/JP6856774B2/ja
Priority to CN201780087199.8A priority patent/CN110326313B/zh
Priority to PCT/CN2017/083323 priority patent/WO2018201476A1/zh
Priority to EP17908374.6A priority patent/EP3641351B1/en
Publication of WO2018201476A1 publication Critical patent/WO2018201476A1/zh
Priority to US16/672,285 priority patent/US11240640B2/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/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group management
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/121—Wireless traffic scheduling for groups of terminals or users
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present invention relates to the field of multimedia broadcast multicast, and in particular, to a multicast bearer management method and a terminal device.
  • Multimedia Broadcast Multicast Service is a service introduced by the 3rd Generation Partnership Project (3GPP) in order to effectively utilize mobile communication network resources.
  • MBMS provides a mobile communication network.
  • a data source sends point-to-multipoint services to multiple users to share network resources and improve resource utilization.
  • MBMS can broadcast multimedia video information directly to all users, or to a group of charged subscribers.
  • the television business provides a means of technical realization.
  • Narrow Bandwidth-Internet of Things is an important branch of the Internet of Everything. It is a technology that uses narrowband technology to carry IoT services.
  • NB-IoT supports cellular data connections of low-power devices over the WAN. .
  • the service and terminal equipment of the NB-IoT network have the following characteristics: 1) The service rate of the NB-IoT is low and the period is long. Compared with the traditional cellular network, the data packet generated by the IoT service is smaller.
  • terminal equipment in NB-IoT generally does not have the ability to simultaneously receive data in multiple types of channels, if a single cell based on Long Term Evolution (LTE) is used.
  • LTE Long Term Evolution
  • SC-PTM Single Cell-Point To Multipoint
  • the terminal equipment in the NB-IoT cannot simultaneously receive the single-cell MBMS control channel ( Control information in the Single Cell-MBMS Control Channel, SC-MCCH) and service data in a Single Cell-MBMS Traffic Channel (SC-MTCH), where the terminal device receives the service data in the SC-MTCH
  • SC-MCCH Single Cell-MBMS Control Channel
  • SC-MTCH Single Cell-MBMS Traffic Channel
  • SC-MRB Single Cell-MBMS Point to Multipoint Radio Bearer
  • RLC radio link control
  • the embodiment of the present invention provides a multicast bearer management method and a terminal device, which saves network resources and power of the terminal device.
  • an embodiment of the present invention provides a method for managing a multicast bearer, including:
  • the SC-MRB is restored or released according to the temporary mobility group identifier TMGI and/or the session identifier corresponding to the SC-MRB.
  • the suspend refers to temporarily not closing or not releasing to perform other tasks, and can continue to use after performing other tasks, and suspending can be equivalent to freezing, sealing, and hibernation.
  • recovery is equivalent to operations such as thawing, unwrapping, and waking up.
  • the SC-MRB corresponding to the SC-MTCH is suspended, and then the first type of data is received, and the first type is received. After the type data is completed, the SC-MRB is restored, and the service data of the SC-MTCH is conveniently received. Suspending the SC-MRB means that the SC-MRB is not released for later use, and it is determined that the SC-MRB is no longer needed to be received. The SC-MRB is released only when the MBMS service is performed, so as to avoid repeated release and establishment of the SC-MRB, thereby saving network resources and power consumption of the terminal device.
  • the recovering the SC-MRB according to the TMGI and/or the session identifier corresponding to the SC-MRB includes: not completing service data of the SC-MTCH Retrieving the SC-MRB according to the TMGI and/or the session identifier corresponding to the SC-MRB; the releasing the SC-MRB according to the TMGI and/or the session identifier corresponding to the SC-MRB includes And: when the receiving of the service data of the SC-MTCH is completed, releasing the SC-MRB according to the TMGI and/or the session identifier corresponding to the SC-MRB.
  • the receiving of the service data of the SC-MTCH is not completed, and the receiving of the suspended SC-MRB is not completed, and the terminal device needs to continue to receive the service data corresponding to the suspended SC-MRB.
  • the completion of the reception of the service data of the SC-MTCH includes two cases: one means that the MBMS service corresponding to the suspended SC-MRB is currently ended; and the other refers to the SC-MRB corresponding to the suspension.
  • the MBMS service is not currently closed, but the terminal device no longer needs to receive the MBMS service corresponding to the suspended SC-MRB.
  • the suspending the SC-MRB corresponding to the SC-MTCH includes: retaining an RLC entity corresponding to the SC-MRB, and releasing the corresponding SC-MRB
  • the media access controls the configuration of the MAC layer and/or the configuration of the physical layer.
  • the method further includes: notifying, by indicating a TMGI and/or a session identifier corresponding to the SC-MRB, The protocol layer of the upper layer of the Radio Resource Control (RRC) has been suspended.
  • the TMGI and/or the session identifier corresponding to the SC-MRB is used to identify the SC-MRB.
  • the SC-MRB corresponding to the TMGI and/or the session identifier may be indicated by a status parameter.
  • the state of the protocol layer can be an application layer.
  • the recovering the SC-MRB according to the TMGI and/or the session identifier corresponding to the SC-MRB includes: according to the TMGI and/or corresponding to the SC-MRB.
  • the session identifier determines the SC-MRB, and determines an RLC entity corresponding to the SC-MRB according to the SC-MRB; and configures the SC-MRB according to information in a single cell multimedia broadcast multicast service control channel SC-MCCH MAC layer and / or physical layer.
  • the suspending SC-MRB process only the configuration of the medium access control MAC layer corresponding to the SC-MRB and/or the configuration of the physical layer are released, and the RLC entity corresponding to the SC-MRB is reserved, and correspondingly, is restored.
  • the MAC layer and/or the physical layer are configured with the reserved RLC entity corresponding to the SC-MRB to implement recovery of the SC-MRB.
  • the method further includes: by indicating, corresponding to the SC-MRB TMGI and/or session identification, notifying the protocol layer at the upper layer of the RRC layer that the SC-MRB has been restored. Specifically, after notifying the protocol layer of the upper layer of the RRC layer, the protocol layer of the upper layer of the RRC layer notifies the user in a user interaction manner.
  • the first type of data includes data whose transmission priority is higher than that of the SC-MTCH.
  • the data that has a higher transmission priority than the service data of the SC-MTCH includes: configuration information in the SC-MCCH or Information during the paging process.
  • the information in the paging process may be a paging message, or may be a system message change indication transmitted in a physical control channel PDCCH used for scheduling paging.
  • suspending the SC-MRB corresponding to the SC-MTCH includes: receiving an SC-MTCH change In the case of notification, the SC-MRB corresponding to the SC-MTCH is suspended; or the SC-MRB corresponding to the SC-MTCH is suspended before the paging is monitored.
  • the second aspect of the present invention provides a terminal device, including:
  • a receiving unit configured to receive service data of a single cell multimedia broadcast multicast service service channel SC-MTCH;
  • a processing unit configured to suspend the SC-MTCH corresponding to the service data of the single-cell multimedia broadcast multicast service service channel SC-MTCH in the process of receiving the first type of data to be received Single-cell multimedia broadcast multicast service point-to-multipoint radio bearer SC-MRB;
  • the processing unit is further configured to restore or release the SC according to the temporary mobility group identifier TMGI and/or the session identifier corresponding to the SC-MRB, if the receiving unit completes receiving the first type of data. -MRB.
  • the terminal device provided by the second aspect of the embodiments of the present invention is used to perform the method for managing the multicast bearer provided by the first aspect of the present invention.
  • the terminal device provided by the second aspect of the embodiments of the present invention is used to perform the method for managing the multicast bearer provided by the first aspect of the present invention.
  • the physical device corresponding to the processing unit is a processor, and the processor is configured to perform the management method of the multicast bearer provided by the first aspect of the embodiment of the present invention
  • the physical device corresponding to the receiving unit is a receiver
  • the receiver is configured to receive service data of a single cell multimedia broadcast multicast service service channel SC-MTCH
  • the terminal device may further include a memory, where the memory is used to store the processor to perform the foregoing An application code of a method, the processor being configured to execute an application stored in the memory.
  • an embodiment of the present invention provides a computer storage medium for storing computer program instructions for use in a computer, comprising: a program for performing the above first aspect.
  • an embodiment of the present invention provides a computer program for performing the various methods provided by the foregoing first aspect.
  • an embodiment of the present invention provides a communication system, including a network communication device, and the terminal device provided by the second aspect of the embodiment of the present invention.
  • FIG. 1 is a schematic structural diagram of a communication system according to an embodiment of the present invention.
  • FIG. 2 is a structural block diagram of an implementation manner of a terminal device
  • FIG. 3 is a schematic flowchart of a method for managing a multicast bearer according to an embodiment of the present invention
  • FIG. 4 is a schematic diagram of a hierarchical structure of a wireless communication protocol according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of changes in a logical transmission link and an RLC entity for performing a multicast bearer management method according to an embodiment of the present invention
  • FIG. 6 is a schematic structural diagram of a terminal device according to an embodiment of the present invention.
  • FIG. 1 is A schematic diagram of a communication system architecture provided by an embodiment of the present invention.
  • a refrigerator 101, a washing machine 102, a television set 103, an in-vehicle Internet of things device 104, and a house building 105 are all Internet of Things devices, and all have basic communication capabilities.
  • a base station 106 can connect tens of thousands of IoT devices, and these IoT devices communicate with other network nodes in the network through the base station 106 to realize collection and interaction of various information.
  • the terminal device in the embodiment of the present invention removes some unnecessary functions, has lower complexity and lower power consumption, and the terminal device does not reduce the overhead of the protocol stack processing flow.
  • the method of the embodiment of the present invention can avoid frequent release and establishment of the SC-MRB, and save network resources and terminal equipment.
  • the terminal device may be a device that provides voice and/or data connectivity to a user, a handheld device with a wireless connection function, or other processing device connected to a wireless modem.
  • the wireless terminal can communicate with one or more core networks via a Radio Access Network (RAN), which can be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal.
  • RAN Radio Access Network
  • RAN can be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal.
  • RAN Radio Access Network
  • it may be a portable, pocket, handheld, computer built-in or in-vehicle mobile device that exchanges language and/or data with a wireless access network.
  • the wireless terminal may also refer to an Internet of Things device that connects the sensing network layer and the transmission network layer, collects data, and transmits data to the network layer.
  • it may be a refrigerator, an air conditioner, a washing machine, or the like in a smart home system.
  • a wireless terminal may also be called a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, or an access point.
  • Remote Terminal Access Terminal, User Terminal, User Agent, User Device, Or User Equipment.
  • FIG. 2 is a structural block diagram of an implementation manner of the terminal device.
  • the terminal device 200 may include: a processing chip 210.
  • Memory 215 one or more computer readable storage media
  • RF radio frequency
  • peripheral system 217 These components can communicate over one or more communication buses 214.
  • the peripheral system 217 is mainly used to implement the interaction function between the terminal device 200 and the user/external environment, and mainly includes input and output devices of the terminal device 200.
  • the peripheral system 217 can include: a camera controller 218, an audio controller 219, and a sensor management module 220. Each controller may be coupled to a respective peripheral device (such as camera 221, audio circuit 222, and sensor 223).
  • camera 221 can be a 3D camera.
  • sensor 223 can be an infrared sensor, a fingerprint sensor, a displacement sensor, an energy sensor, a temperature sensor, a humidity sensor, a light sensor, and the like.
  • the peripheral system 217 may further include other I/O peripherals.
  • the peripheral system 217 further includes a Radio Frequency Identification (RFID) controller 224, wherein the RFID read/write controller and the RFID read and write The device 225 is coupled.
  • RFID Radio Frequency Identification
  • the processing chip 210 can be integrated to include a processor/microprocessor 211, a clock module 212, and a power management module 213.
  • the clock module 212 integrated in the processing chip 220 is primarily used to generate the clocks required for data transfer and timing control for the processor/microprocessor 211.
  • the power management module 213 integrated in the processing chip 210 is primarily used to provide a stable, high accuracy voltage to the processor/microprocessor 211, the radio frequency module 216, and the peripheral system 217.
  • the processor/microprocessor 211 may be a central processing unit (CPU), an embedded microcontroller (Micro Controller Unit (MCU), an embedded microprocessor (Micro Processor Unit, MPU). ), embedded system on chip (SoC) and so on.
  • the processor/microprocessor 211 may include one or more processors, for example, the processor/microprocessor 211 may include one or more microprocessors or include one or more microprocessors and one or more applications processor. When the processor/microprocessor 211 includes a plurality of processors, the plurality of processors may be integrated on the same processing chip or may be separate processing chips.
  • a processor can include one or more processor cores (or processing cores).
  • a radio frequency (RF) module 216 is used to receive and transmit radio frequency signals, primarily integrating the receiver and transmitter of the terminal device 200.
  • a radio frequency (RF) module 216 communicates with the communication network and other communication devices via radio frequency signals.
  • the radio frequency (RF) module 216 can include, but is not limited to: an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chip, a storage medium, etc.
  • a radio frequency (RF) module 216 can be implemented on a separate chip.
  • Memory 215 is coupled to processor/microprocessor 211 for storing various software programs and/or sets of instructions.
  • memory 215 can include high speed random access memory, and can also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid state storage devices.
  • the memory 215 can store an operating system (hereinafter referred to as a system) such as an embedded operating system such as ANDROID, IOS, WINDOWS or LINUX.
  • the memory 215 can also store a network communication program that can be used to communicate with one or more additional devices, one or more terminal devices, one or more network devices.
  • the memory 215 can also store a user interface program, which can realistically display the content of the application through a graphical operation interface, and receive user control operations on the application through input controls such as menus, dialog boxes, and keys. .
  • the memory 215 can also store one or more applications.
  • the program of the operating system includes a computer program that can implement the management method of the multicast bearer provided by the embodiment of the present invention, so that after the processor/microprocessor 211 reads the program and runs the operating system, the operating system can The management function of the multicast bearer provided by the embodiment of the present invention is provided.
  • the following embodiments describe a method and an apparatus for managing a multicast bearer provided by an embodiment of the present invention by using a terminal device as an execution entity.
  • the term “suspend” refers to temporarily not closing/releasing/deleting resources or parts corresponding to the current transaction, process, or session in the case that other tasks, processes, or sessions are currently required to be executed.
  • the resource may directly use the resource or part of the resource corresponding to the current transaction, process, or session after performing the other tasks, processes, or sessions to facilitate execution of the current task, process, or session.
  • the suspending SC-MRB may be replaced with a description of freezing the SC-MRB, storing the SC-MRB, making the SC-MRB dormant, locking the SC-MRB, and the like. Those skilled in the art can understand the meaning thereof.
  • the term “recovery” corresponds to the term “suspend”, and refers to being executed before the execution of the other transaction, process, or session, after the execution of other tasks, processes, or sessions.
  • Resources or parts of resources corresponding to idle/vacant transactions, processes, or sessions are reconfigured/used to provide execution environments or resources for tasks such as idle/vacant transactions, processes, or sessions.
  • the recovery SC-MRB may be replaced with a description of thawing the SC-MRB, unpacking the SC-MRB, waking up the SC-MRB, unlocking the SC-MRB, and the like. Those skilled in the art can understand the meaning thereof.
  • the following examples illustrate suspending and resuming.
  • memory resources are limited.
  • the operating system arranges the programs in the memory reasonably, and temporarily transfers some processes out of the memory so that they do not occupy memory resources. , that is, the process is suspended; when the condition allows (for example, some of the processes in the memory have finished running, the memory resources occupied by them are released, and the current memory resources are sufficient), the operating system resets the previously suspended processes back to the memory, that is, Recovery process.
  • FIG. 3 is a schematic flowchart of a method for managing a multicast bearer according to an embodiment of the present invention.
  • the method may be specifically implemented on the Internet of Things terminal device such as the refrigerator 101 and the washing machine 102 in FIG. It can be implemented on a terminal device that satisfies the structural block diagram of FIG. 2, the method comprising at least:
  • a terminal device with low complexity and low power consumption uses a small bandwidth, and data can only be transmitted on one carrier at a time.
  • the different physical layer channels of the terminal device are generally time-division multi-task, that is, different.
  • the physical layer channel can only be generated or established at different times.
  • the terminal device needs to release the currently established physical channel.
  • the physical channel of the terminal has a physical downlink control channel (Physical Downlink Control Channel, PDCCH), physical broadcast channel (PBCH), and physical downlink shared channel (PDSCH), the terminal can only establish or run PDCCH, PBCH or PDSCH at the same time or in the same time slot.
  • PDCCH Physical Downlink Control Channel
  • PBCH physical broadcast channel
  • PDSCH physical downlink shared channel
  • the terminal device can provide the resources of the physical layer of the upper layer protocol entity at the same time.
  • the terminal device only has the capability of providing a transmission link to a logical channel at the same time.
  • Second logic When receiving the data of the first logical channel, if it needs to receive Second logic
  • the data of the channel determines a target logical channel with a high transmission priority according to the transmission priority of the first logical channel and the second logical channel, and preferentially provides a transmission link for the target logical channel.
  • the transmission priority of the first type of data is higher than the service data of the SC-MTCH, and the first type of data includes configuration information in the SC-MCCH or information in the paging process.
  • the type data may be configuration information such as scheduling information in the SC-MCCH, timing information of the single-cell point-to-multipoint mechanism, and the like.
  • the first type of data may also be information in a paging process such as a paging message or a paging change indication.
  • the SC-MRB corresponding to the SC-MTCH may be suspended.
  • the change notification of the SC-MCCH indicates that the configuration information of the SC-MTCH included in the SC-MCCH has been or will be updated, the transmission priority of the configuration information of the SC-MTCH is higher than the service data of the SC-MTCH, and the terminal device needs to receive the SC- preferentially.
  • the SC-MRB corresponding to the SC-MTCH may be suspended before the paging is monitored.
  • the terminal device receives the paging information in a discontinuous reception (DRX) manner to save power consumption.
  • the RRC layer of the terminal device controls the physical layer to monitor the physical downlink control when the paging cycle arrives.
  • Channel Physical Downlink Control Channel, PDCCH
  • PDSCH Physical Downlink Shared Chinnel
  • the paging is an action initiated by the network side to determine the specific location of the terminal device or update the system message, and the transmission priority is higher than the service data of the SC-MTCH, so when the paging needs to be received,
  • the terminal device preferentially monitors the PDCCH and preferentially receives the paging message if there is a paging message.
  • the terminal device may suspend the SC-MRB corresponding to the SC-MTCH within a preset period of time before the paging cycle arrives.
  • the SC-MRB is a radio bearer established to receive the service data of the SC-MTCH.
  • the transmission priority of the first type of data to be received is higher than that of the SC-
  • the service data of the MTCH needs to preferentially transmit the first type of data, and preferentially provides a transmission link for the first type of data, that is, the corresponding physical layer and/or MAC layer needs to be configured for the first data.
  • the terminal device only has the capability of providing a transmission link to a logical channel at the same time. If the SC-MRB is not released, suspending the SC-MRB includes: retaining the RLC entity corresponding to the SC-MRB, and releasing the The configuration of the medium access control MAC layer and/or the configuration of the physical layer corresponding to the SC-MRB.
  • the suspending the SC-MRB further includes: notifying the protocol layer of the upper layer of the RRC layer by indicating a Temporary Mobile Group Identity (TMGI) and/or a session identifier corresponding to the SC-MRB The SC-MRB has been suspended.
  • TMGI Temporary Mobile Group Identity
  • TMGI is used to distinguish different MBMS services.
  • one MBMS service corresponds to one TMGI.
  • the session identifier is used to distinguish different MBMS sessions.
  • one MBMS service corresponds to one MBMS session identifier, that is, both the TGMI and the session identifier can be used to identify the SC-MRB and the MBMS service corresponding to the SC-MRB, and the upper layer of the RRC is
  • the protocol layer indicates the TMGI and/or the session identifier corresponding to the SC-MRB, so that the protocol layer of the upper layer of the RRC can know that the corresponding SC-MRB of the target MBMS service is currently suspended, and the terminal device cannot temporarily enter.
  • the target MBMS service is performed.
  • a state parameter may also be used to indicate the state of the SC-MRB. For example, if the value of the status parameter is 11, it indicates that the SC-MRB has been established; the value of the status parameter is 01, indicating that the SC-MRB has been suspended; and the value of the status parameter is 10, indicating the The SC-MRB has been restored; a status parameter of 00 indicates that the SC-MRB has been released.
  • the protocol layer of the upper layer of the RRC may be an application layer.
  • the user is currently using the client of the terminal device to watch the television program, that is, the MBMS service currently received by the terminal device is a television program, and the SC-MRB provides a receiving service for the television program.
  • the terminal device suspends the SC-MRB.
  • the terminal device temporarily cannot receive the MBMS service corresponding to the SC-MRB, and indicates that the TMGI and/or corresponding to the SC-MRB are indicated.
  • the client's user interface displays a message similar to "current service unavailable".
  • the method further includes: establishing a first radio bearer of the first type of data and receiving the first type of data by using the first radio bearer.
  • the first radio bearer may be a signaling radio bearer or a data radio bearer.
  • the establishing the first radio bearer includes: establishing a first RLC entity corresponding to the first type of data, and configuring a MAC layer and a physical layer corresponding to the first type of data.
  • the first radio bearer established for the first type of data is released, and the RLC entity corresponding to the first radio bearer and the corresponding MAC layer are released. And physical layer configuration.
  • the completion of receiving the first type of data may be completed for receiving all configuration information in the SC-MCCH, or may be completed for receiving information in the paging process.
  • the SC-MRB is restored according to the TMGI and/or the session identifier corresponding to the SC-MRB; and the SC-MTCH is completed.
  • the SC-MRB is released according to the TMGI and/or the session identifier corresponding to the SC-MRB.
  • the receiving of the service data of the SC-MTCH is not completed, and the receiving of the suspended SC-MRB is not completed, and the terminal device needs to continue to receive the service data corresponding to the suspended SC-MRB.
  • the completion of the reception of the service data of the SC-MTCH includes two cases: one means that the MBMS service corresponding to the suspended SC-MRB is currently ended; and the other refers to the SC-MRB corresponding to the suspension.
  • the MBMS service is not currently closed, but the terminal device no longer needs to receive the MBMS service corresponding to the suspended SC-MRB.
  • the terminal is currently receiving service data of the first MBMS service through the first SC-MRB, and the base station sends a change notification of the SC-MCCH, and the terminal device suspends the first SC-MRB and receives the SC-MCCH.
  • the configuration information is assumed to be that the base station updates the MBMS service by using the configuration information, and adds a second MBMS service. After the configuration information is received, the first MBMS service is not yet completed. If the user holding the terminal device has the second MBMS service Interestedly, it is desirable for the terminal device to receive the second MBMS service.
  • the terminal device does not need to receive the first MBMS service, that is, completes the service data of the SC-MTCH corresponding to the first SC-MRB.
  • the terminal device needs to continue to receive the first MBMS service, that is, the service data of the SC-MTCH corresponding to the first SC-MRB is not completed, and the terminal device restores the first SC-MRB and releases the first MBMS service.
  • An SC-MRB is an SC-MRB.
  • the terminal device is currently receiving service data of the first MBMS service through the first SC-MRB, and the terminal device currently needs to receive the paging, the terminal device suspends the first SC-MRB, and receives the paging; If the call does not involve the update of the MBMS service, after the paging is received, if the terminal device is not paged by the network, and the first MBMS service is not completed and the user is still interested in the first MBMS service, the terminal device needs to continue to receive the first The first SC-MRB is restored and the first SC-MRB is released when the first MBMS service ends; If the user finds that the network is advertised by receiving the paging message, the RRC connection needs to be established to respond to the network. In this case, the terminal device may not continue to receive the first MBMS service, that is, complete the reception of the service data of the SC-MTCH. The terminal device releases the first SC-MRB.
  • the recovering the SC-MRB includes: determining the SC-MRB according to a TMGI and/or a session identifier corresponding to the SC-MRB, and determining, according to the SC-MRB, an RLC entity corresponding to the SC-MRB;
  • the MAC layer and/or the physical layer are configured for the SC-MRB according to information in the SC-MCCH.
  • restoring the SC-MRB may use an RLC entity corresponding to the SC-MRB reserved in the SC-MRB suspend procedure.
  • configuring the MAC layer and/or the physical layer includes: receiving single cell point to multipoint configuration (SCPTMConfiguration) information, where the SCPTMConfiguration information includes an SC-MTCH information list sc-mtch-InfoList; One SC-MTCH corresponds to one sc-mtch-Info in the sc-mtch-InfoList, and the MAC layer and/or the physical layer are configured according to the sc-mtch-Info.
  • SCPTMConfiguration single cell point to multipoint configuration
  • the sc-mtch-Info includes parameter information such as a group-Radio Network Tempory Identity (G-RNTI) and an SC-MTCH scheduling information (sc-mtch-SchedulingInfo), where G- RNTI is used to scramble the channel, sc-mtch-SchedulingInfo is the DRX information set by the SC-MTCH.
  • G-RNTI group-Radio Network Tempory Identity
  • SC-MTCH scheduling information sc-mtch-SchedulingInfo
  • sc-mtch-SchedulingInfo is the DRX information set by the SC-MTCH.
  • the information of the SC-MTCH can be in any subframe. Was transferred.
  • the method further includes: notifying the protocol layer at the upper layer of the RRC layer that the SC-MRB has been restored by indicating a TMGI and/or a session identifier corresponding to the SC-MRB.
  • step S101 by executing the TMGI and/or session identifier corresponding to the SC-MRB, and notifying the protocol layer of the upper layer of the RRC layer that the SC-MRB has been suspended,
  • the corresponding SC-MRB of the protocol layer above the RRC layer may be notified that the SC-MRB has been restored.
  • the SC-MRB if receiving the first type of data in the process of receiving the service data of the SC-MTCH, suspending the SC-MRB corresponding to the SC-MTCH, and then receiving the first type of data, receiving First type of data After the completion, the SC-MRB is resumed, and the service data of the SC-MTCH is continuously received.
  • the SC-MRB is suspended, only the configuration of the MAC layer and/or the physical layer is released, and the RLC entity corresponding to the SC-MRB is reserved, and the RLC entity is retained.
  • the RLC PDU buffered by the RLC entity is reserved.
  • the MAC layer and/or the physical layer need to be reconfigured according to the information in the SC-MCCH, and the RLC entity corresponding to the SC-MRB does not need to be re-established, and the RLC PDU does not need to be re-received.
  • the MAC layer and/or the physical layer need to be reconfigured according to the information in the SC-MCCH, and the RLC entity corresponding to the SC-MRB does not need to be re-established, and the RLC PDU does not need to be re-received.
  • FIG. 4 is a schematic diagram showing a possible structure of a wireless communication protocol.
  • the wireless communication protocol is a network upper layer, an RLC layer, a MAC layer, and a physical layer from top to bottom, wherein a Radio Resource Control (RRC) layer is used.
  • RRC Radio Resource Control
  • the network layer, the transport layer, the application layer, and the non-access layer are all network upper layers
  • the RLC layer and the MAC layer are OSI layer 2 protocols
  • the physical layer is the OSI layer 1 protocol.
  • the establishment, suspension, recovery, and release of the SC-MRB in the embodiment of the present invention involve the RRC layer, the RLC layer, the MAC layer, and the physical layer.
  • the RRC layer can implement the MBMS service notification to implement the establishment, modification, and release of the radio bearer corresponding to the MBMS service.
  • the RRC layer completes the establishment, modification, and release of the radio bearer by instructing the RLC layer, the MAC layer, and the physical layer to perform corresponding operations. .
  • the RLC layer mainly implements functions such as segmentation and reassembly of protocol service data units, establishment, release, and configuration of various data logical links.
  • the RLC layer is composed of multiple RLC entities and control entities, and one RLC entity corresponds to one RB, and the RLC entity.
  • the RLC entity corresponding to the SC-MRB in the embodiment of the present invention is a non-acknowledgment mode RLC entity, and the RLC control is configured according to the type of the transmission service, the non-acknowledgement mode (UM), the acknowledgement mode (AM), and the transparent mode (TM).
  • the entity mainly implements the establishment, release, and parameter configuration of data logical links.
  • the MAC layer is located between the physical layer and the RLC layer, and provides services to the RLC layer upwards.
  • the RLC layer sends the PDUs of the RLC layer to the MAC layer for transmission through the logical channel, and the MAC layer uses the services provided by the physical layer downwards by using the physical channel.
  • the MAC layer mainly implements mapping of logical channels and physical channels, dynamic adaptation of MAC layer service data units (SDUs) and physical layer data transmission blocks, and dynamic configuration of physical layer transmission parameters, and is implemented in the present invention.
  • the MAC layer implements the PDU of the service data of the SC-MTCH to the RLC entity to enable the RLC entity to reassemble the PDU.
  • the physical layer implements functions such as physical channel codec decoding, physical channel multiplexing and demultiplexing, and radio frequency processing.
  • FIG. 5 is a logical transmission link for performing the management method of the multicast bearer according to the embodiment of the present invention. Schematic diagram of changes in RLC entities.
  • the terminal device is receiving the service data of the SC-MTCH through the SC-MRB, and the RLC entity A is the RLC entity corresponding to the SC-MRB, and the configurations in the MAC layer and the physical layer are all configurations corresponding to the SC-MTCH;
  • the first type of data if the transmission priority of the first type of data is higher than that of the SC-MTCH, the transmission link is preferentially provided for the first type of data, and the resources of the MAC layer and the physical layer of the terminal device are limited.
  • the configuration of the MAC layer and the physical layer is released, and the RLC entity A is reserved.
  • the SC-MRB is suspended, and then the RLC entity B is newly created, and the MAC layer and the released MAC layer are compared according to the logical channel type corresponding to the first type of data to be received.
  • the physical layer is reconfigured to receive the first type of data through the newly created radio bearer.
  • the RLC entity B is released, and the configuration of the MAC layer and the physical layer is released, and the MAC is configured for the SC-MTCH.
  • RLC entity A and configured MAC layer and physical layer constitute SC-MRB, at this time SC-MRB is restored, and the SC-MTCH service data is continuously received through the restored SC-MRB;
  • the release of the configuration of the MAC layer and the physical layer corresponding to the RLC entity A and the SC-MRB is released to the SC-MRB.
  • the MAC layer, and the physical configuration are released, if the service data of the SC-MTCH is not required to continue to be received, the information may be directly released.
  • the RLC entity A in which the service data of the SC-MTCH is not required to be received, has been exemplified in the above embodiments, and details are not described herein.
  • FIG. 6 is a schematic diagram showing a possible structure of a terminal device involved in the foregoing embodiment, where the terminal device includes a receiving unit 410 and a processing unit 420, wherein a detailed description of each unit is as follows:
  • the receiving unit 410 is configured to receive service data of a single cell multimedia broadcast multicast service service channel SC-MTCH;
  • the processing unit 420 is configured to suspend the SC-MTCH in the process that the receiving unit 410 receives the service data of the single-cell multimedia broadcast multicast service channel SC-MTCH and has the first type of data to be received.
  • the processing unit 420 is further configured to restore or release the temporary mobile group identifier TMGI and/or the session identifier corresponding to the SC-MRB if the receiving unit 410 completes receiving the first type of data. Said SC-MRB.
  • processing unit 420 is specifically configured to:
  • the SC-MRB Recovering the SC-MRB according to the TMGI and/or session identifier corresponding to the SC-MRB if the receiving unit 410 does not complete the reception of the service data of the SC-MTCH; or at the receiving unit In the case that the reception of the service data of the SC-MTCH is completed, the SC-MRB is released according to the TMGI and/or the session identifier corresponding to the SC-MRB.
  • processing unit 420 is specifically configured to:
  • processing unit 420 is specifically configured to:
  • processing unit 420 is specifically configured to:
  • the MAC layer and/or the physical layer are configured for the SC-MRB according to information in the single cell multimedia broadcast multicast service control channel SC-MCCH.
  • processing unit 420 is specifically configured to:
  • the first type of data includes data whose transmission priority is higher than the service data of the SC-MTCH.
  • the data whose transmission priority is higher than the service data of the SC-MTCH includes:
  • the processing unit 420 is specifically configured to:
  • the receiving unit 410 When the receiving unit 410 receives the SC-MTCH change notification, suspending the SC-MRB corresponding to the SC-MTCH; or
  • the SC-MRB corresponding to the SC-MTCH is suspended before the paging is monitored.
  • the processing unit 420 may correspond to the processor 211 or the processing chip 210 in the terminal shown in FIG. 2, and the receiving unit may correspond to the RF transceiver in the terminal shown in FIG. 2162 or RF module 216.
  • the processing unit 420 can also cooperate with the receiving unit 410 to perform all operations in the method embodiment shown in FIG. 3.
  • the controller/processor for performing the above functions of the terminal device of the embodiment of the present invention may be a central processing unit (CPU), a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), and a field programmable gate array. (FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor may also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the terminal device needs to receive the first type of data in the process of receiving the service data of the SC-MTCH, the SC-MRB corresponding to the SC-MTCH is suspended, and then the first type of data is received. After receiving the first type of data, the SC-MRB is resumed, and the service data of the SC-MTCH is continuously received, and the SC-MRB is suspended to release only the configuration of the MAC layer and/or the physical layer, and the SC-MRB is reserved.
  • the RLC entity only needs to reconfigure the MAC layer and/or the physical layer according to the information in the SC-MCCH, and does not need to re-establish the RLC entity corresponding to the SC-MRB, avoiding repeated release and establishment of the SC-MRB, and saving the network. Power consumption of resources and terminal equipment.
  • An embodiment of the present invention further provides a computer storage medium storing a computer program, the computer program comprising program instructions, the program instructions, when executed by a computer, causing the computer to execute as described in the foregoing embodiments Method, the computer may be part of the terminal device mentioned above.
  • Embodiments of the present invention also provide a computer program, including program instructions, which when executed by a computer, are used to perform the method as described in the foregoing embodiments.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).
  • the steps of a method or algorithm described in connection with the present disclosure may be implemented in a hardware, or may be implemented by a processor executing software instructions.
  • the software instructions may be comprised of corresponding software modules that may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable hard disk, CD-ROM, or any other form of storage well known in the art.
  • An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium.
  • the storage medium can also be an integral part of the processor.
  • the processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in the user equipment.
  • processors and storage media can also be used as Discrete components are present in the user device.
  • the functions described herein can be implemented in hardware, software, firmware, or any combination thereof.
  • the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium.
  • Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another.
  • a storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

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

Abstract

本发明实施例公开了多播承载的管理方法和终端设备。一种多播承载的管理方法，包括：在接收单小区多媒体广播组播服务业务信道SC-MTCH的业务数据的过程中，且存在待接收的第一类型数据的情况下，挂起所述SC-MTCH对应的单小区点对多点多媒体广播组播服务无线承载SC-MRB；在完成对所述第一类型数据的接收的情况下，根据所述SC-MRB对应的临时移动组标识TMGI和/或会话标识恢复或释放所述SC-MRB。采用本发明实施例的技术方案，可以避免频繁释放和建立SC-MRB，节省网络资源和终端设备的电量。

Description

多播承载的管理方法和终端设备 技术领域
本发明涉及多媒体广播组播领域，尤其涉及多播承载的管理方法和终端设备。
背景技术
多媒体广播组播服务(Multimedia Broadcast Multicast Service，MBMS)是第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)为了有效地利用移动通信网络资源而引入的一个服务，MBMS在移动通信网络中提供一个数据源向多个用户发送数据的点到多点服务，实现网络资源共享，提高资源利用率，MBMS可以将多媒体视频信息直接向所有用户广播，也可以发送给一组收费的签约用户，为终端电视业务提供了技术实现手段。
窄带物联网(Narrow Bandwidth-Internet of Things，NB-IoT)是万物互联的一个重要分支，是一种利用窄带技术来承载IoT业务的技术，NB-IoT支持低功耗设备在广域网的蜂窝数据连接。与传统蜂窝网络相比，NB-IoT网络的业务和终端设备具备以下特点：1)NB-IoT的业务速率低，周期较长，与传统蜂窝网络相比，IoT业务产生的数据包更小，对时延不敏感；2)一个NB-IoT基站下连接大量的终端设备；3)与传统蜂窝网络中的终端设备相比，NB-IoT中的终端设备成本更低，复杂性也更低；4)NB-IoT中的终端设备的功耗更低。
为了满足终端设备低成本和低复杂度的要求，NB-IoT中的终端设备一般不具备同时接收多种类型的信道中的数据的能力，如果基于长期演进(Long Term Evolution，LTE)的单小区点对多点(Single Cell-Point To Multipoint,SC-PTM)机制来设计NB-IoT的组播传输方案，则会出现如下场景：NB-IoT中的终端设备不能同时接收单小区MBMS控制信道(Single Cell-MBMS Control Channel，SC-MCCH)中的控制信息和单小区MBMS业务信道(Single Cell-MBMS Traffic Channel，SC-MTCH)中的业务数据，在终端设备接收SC-MTCH中的业务数据的过程中，若当前需要接收SC-MCCH中的控制信息，则需要释放SC-MTCH对应的单小区点对多点MBMS无线承载(Single Cell-MBMS Point to Multipoint Radio Bearer，SC-MRB)，在接收完SC-MCCH中的控制信息后，需重新建立SC-MRB。这样会引起以下问题：当释放SC-MRB对应的无线链路控制(Radio Link Control，RLC)实体，会删除已接收成功但尚未进行组包的无线链路控制协议数据单元(Radio Link Control Protocol Data Unit，RLC PDU)，当重新建立SC-MRB后，需要重新接收RLC PDU，消耗更多的电量；当多播业务未接收完毕时，可能会触发更高层向网络申请单播重传，频繁的单播重传同样会消耗更多的电量，同时耗费网络资源。
发明内容
为了解决上述问题，本发明实施例提供多播承载的管理方法和终端设备，节省网络资源和终端设备的电量。
第一方面，本发明实施例提供一种多播承载的管理方法，包括：
在接收单小区多媒体广播组播服务业务信道SC-MTCH的业务数据的过程中，且存在 待接收的第一类型数据的情况下，挂起所述SC-MTCH对应的单小区点对多点多媒体广播组播服务无线承载SC-MRB；
在完成对所述第一类型数据的接收的情况下，根据所述SC-MRB对应的临时移动组标识TMGI和/或会话标识恢复或释放所述SC-MRB。
其中，挂起指暂时不关闭或不释放而去执行其他任务，在执行完其他任务后可以继续使用，挂起可以等同于冻结、封存、使休眠等操作。
相应地，恢复等同于解冻、解开、唤醒等操作。
在本发明实施例中，若在接收SC-MTCH的业务数据的过程中需接收第一类型的数据，则挂起SC-MTCH对应的SC-MRB，然后接收第一类型数据，在接收第一类型数据完后，恢复SC-MRB，方便继续接收SC-MTCH的业务数据，将SC-MRB挂起表示暂时不释放SC-MRB以便后面继续使用，在确定不再需要接收所述SC-MRB对应的MBMS业务时才释放所述SC-MRB，这样避免反复释放和建立SC-MRB，节省网络资源和终端设备的功耗。
在第一方面的第一种可能的实现方式中，所述根据所述SC-MRB对应的TMGI和/或会话标识恢复所述SC-MRB包括：在未完成对所述SC-MTCH的业务数据的接收的情况下，根据所述SC-MRB对应的TMGI和/或会话标识恢复所述SC-MRB；所述根据所述SC-MRB对应的TMGI和/或会话标识释放所述SC-MRB包括：在完成对所述SC-MTCH的业务数据的接收的情况下，根据所述SC-MRB对应的TMGI和/或会话标识释放所述SC-MRB。具体地，未完成对所述SC-MTCH的业务数据的接收指所述挂起的SC-MRB对应的MBMS业务接收未结束且终端设备需继续接收所述挂起的SC-MRB对应的业务数据；完成对所述SC-MTCH的业务数据的接收包括两种情况：一种指所述挂起的SC-MRB对应的MBMS业务当前已经结束；另一种指所述挂起的SC-MRB对应的MBMS业务当前未结束，但终端设备不再需要接收所述挂起的SC-MRB对应的MBMS业务。
在第一方面的第二种可能的实现方式中，所述挂起所述SC-MTCH对应的SC-MRB包括：保留所述SC-MRB对应的RLC实体，以及释放所述SC-MRB对应的媒体接入控制MAC层的配置和/或物理层的配置。
在第一方面的第三种可能的实现方式中，所述挂起所述SC-MTCH对应的SC-MRB之后还包括：通过指示与所述SC-MRB对应的TMGI和/或会话标识，通知无线资源控制(Radio Resource Control，RRC)上层的协议层所述SC-MRB已经被挂起。其中，与所述SC-MRB对应的TMGI和/或会话标识用于标识所述SC-MRB，具体实现中，可以通过一个状态参数指示所述TMGI和/或会话标识对应的SC-MRB的挂起状态；具体地，RRC层上层的协议层可以为应用层。
在第一方面的第四种可能的实现方式中，所述根据所述SC-MRB对应的TMGI和/或会话标识恢复所述SC-MRB包括：根据所述SC-MRB对应的TMGI和/或会话标识确定所述SC-MRB，并根据所述SC-MRB确定所述SC-MRB对应的RLC实体；根据单小区多媒体广播组播服务控制信道SC-MCCH中的信息为所述SC-MRB配置MAC层和/或物理层。具体地，在挂起SC-MRB流程中，只释放SC-MRB对应的媒体接入控制MAC层的配置和/或物理层的配置，SC-MRB对应的RLC实体被保留，相应地，在恢复过程中可使 用保留下来的所述SC-MRB对应的RLC实体并配置MAC层和/或物理层，以实现对SC-MRB的恢复。
在第一方面的第五种可能的实现方式中，所述根据所述SC-MRB对应的TMGI和/或会话标识恢复所述SC-MRB之后还包括：通过指示与所述SC-MRB对应的TMGI和/或会话标识，通知RRC层上层的协议层所述SC-MRB已经被恢复。具体地，通知RRC层上层的协议层后，RRC层上层的协议层以用户交互的方式通知到用户。
在第一方面的第六种可能的实现方式中，所述第一类型数据包括传输优先级高于所述SC-MTCH的业务数据的数据。
结合第一方面的第六种可能的实现方式，在第七种可能的实现方式中，所述传输优先级高于所述SC-MTCH的业务数据的数据包括：SC-MCCH中的配置信息或寻呼过程中的信息。其中，所述寻呼过程中的信息可以为寻呼消息，也可以为在调度寻呼使用的物理控制信道PDCCH中传输的系统消息变更指示。
在第一方面的第八种可能的实现方式中，所述在存在待接收的第一类型数据的情况下，挂起所述SC-MTCH对应的SC-MRB包括：在接收到SC-MTCH变更通知的情况下，挂起所述SC-MTCH对应的SC-MRB；或在监听寻呼之前挂起所述SC-MTCH对应的SC-MRB。
第二方面，本发明实施例提供一种终端设备，包括：
接收单元，用于接收单小区多媒体广播组播服务业务信道SC-MTCH的业务数据；
处理单元，用于在接收单元接收单小区多媒体广播组播服务业务信道SC-MTCH的业务数据的过程中，且存在待接收的第一类型数据的情况下，挂起所述SC-MTCH对应的单小区多媒体广播组播服务点对多点无线承载SC-MRB；
所述处理单元还用于在所述接收单元完成对所述第一类型数据的接收的情况下，根据所述SC-MRB对应的临时移动组标识TMGI和/或会话标识恢复或释放所述SC-MRB。
本发明实施例第二方面提供的终端设备用于执行本发明实施例第一方面提供的多播承载的管理方法，具体的可参见本发明实施例第一方面的描述，在此不再赘述。
在一个可能的设计中，所述处理单元对应的实体设备为处理器，所述处理器用于执行本发明实施例第一方面提供的多播承载的管理方法，所述接收单元对应的实体设备为接收器，所述接收器用于接收单小区多媒体广播组播服务业务信道SC-MTCH的业务数据；可选的，所述终端设备还可以包括存储器，所述存储器用于存储所述处理器执行上述方法的应用程序代码，所述处理器被配置为用于执行所述存储器中存储的应用程序。
第三方面，本发明实施例提供一种计算机存储介质，用于储存为计算机所用的计算机程序指令，其包含用于执行上述第一方面所涉及的程序。
第四方面，本发明实施例提供一种计算机程序，用于执行上述第一方面提供的各种方法。
第五方面，本发明实施例提供一种通信系统，包括网络通信设备和如本发明实施例第二方面提供的所述终端设备。
附图说明
为了更清楚地说明本发明实施例中的技术方案，下面将对实施例中所需要使用的附图作简单地介绍。
图1是本发明实施例提供的一种通信系统架构示意图；
图2是终端设备的一种实现方式的结构框图；
图3是本发明实施例提供的一种多播承载的管理方法的流程示意图；
图4是本发明实施例提供的一种无线通信协议的层次结构示意图；
图5是本发明实施例提供的执行多播承载的管理方法的逻辑传输链路和RLC实体的变化示意图；
图6是本发明实施例提供的一种终端设备的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行描述。
本发明实施例的技术方案主要适用于复杂度低、功耗低的终端设备所在的无线通信系统，例如为IoT通信系统，本发明实施例的通信系统架构可以如图1所示，图1是本发明实施例提供的一种通信系统架构示意图，在图1中，冰箱101、洗衣机102、电视机103、车载物联网设备104、房屋建筑105等均属于物联网设备，均具备基本的通信能力，他们可以采集需要监控、连接或互动的物体的各种信息，通过无线通信技术(无线通信技术具体可以为3G、4G、GPRS等通信技术)将信息发送到网络中，实现物与物之间的相互通信，一个基站106下可以连接数以万计的物联网设备，这些物联网设备通过基站106与网络中的其他网络节点进行通信，实现各种信息的采集与交互。
本发明实施例中的终端设备与传统蜂窝网络中的终端设备相比，去掉了一些不必要的功能，复杂度更低、功耗也更低，为了减少协议栈处理流程的开销，终端设备不具备同时接收多种类型信道的数据的能力，通过本发明实施例的方法，可避免频繁释放和建立SC-MRB，节省网络资源和终端设备的开销。
本发明实施例涉及的终端设备，可以是指向用户提供语音和/或数据连通性的设备，具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备。无线终端可以经无线接入网(Radio Access Network，RAN)与一个或多个核心网进行通信，无线终端可以是移动终端，如移动电话(或称为“蜂窝”电话)和具有移动终端的计算机，例如，可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与无线接入网交换语言和/或数据。例如，个人通信业务(PCS，Personal Communication Service)电话、无绳电话、会话发起协议(SIP)话机、无线本地环路(WLL，Wireless Local Loop)站、个人数字助理(PDA，Personal Digital Assistant)等设备。无线终端也可以是指连接传感网络层和传输网络层、采集数据并向网络层发送数据的物联网设备，例如，可以是智能家居系统中的冰箱、空调、洗衣机等设备。无线终端也可以称为系统、订户单元(Subscriber Unit)、订户站(Subscriber Station)，移动站(Mobile Station)、移动台(Mobile)、远程站(Remote Station)、接入点(Access Point)、远程终端(Remote Terminal)、接入终端(Access Terminal)、用户终端(User Terminal)、用户代理(User Agent)、用户设备(User Device)、 或用户装备(User Equipment)。
下面介绍图1的系统中涉及的终端设备的一种实现方式，参见图2，图2是终端设备的一种实现方式的结构框图，如图2所示，终端设备200可包括：处理芯片210、存储器215(一个或多个计算机可读存储介质)、射频(RF)模块216、外围系统217。这些部件可在一个或多个通信总线214上通信。
外围系统217主要用于实现终端设备200和用户/外部环境之间的交互功能，主要包括终端设备200的输入输出装置。具体实现中，外围系统217可包括：摄像头控制器218、音频控制器219以及传感器管理模块220。其中，各个控制器可与各自对应的外围设备(如摄像头221、音频电路222以及传感器223)耦合。在一些实施例中，摄像头221可以是3D摄像头。在一些实施例中，传感器223可以是红外线传感器、指纹传感器、位移传感器、能耗传感器、温度传感器、湿度传感器、光传感器等等。需要说明的是，外围系统217还可以包括其他I/O外设，例如，外围系统217还包括无线射频识别(Radio Frequency Identification，RFID)控制器224、其中，RFID读写控制器与RFID读写器225耦合。
处理芯片210可集成包括：处理器/微处理器211、时钟模块212以及电源管理模块213。集成于处理芯片220中的时钟模块212主要用于为处理器/微处理器211产生数据传输和时序控制所需要的时钟。集成于处理芯片210中的电源管理模块213主要用于为处理器/微处理器211、射频模块216以及外围系统217提供稳定的、高精确度的电压。在一些实施例中，所述处理器/微处理器211可以是中央处理器(Center Processor Unit，CPU)、嵌入式微控制器(Micro Controller Unit，MCU)、嵌入式微处理器(Micro Processor Unit，MPU)、嵌入式片上系统(System on Chip，SoC)等等。
处理器/微处理器211可以包括一个或多个处理器，例如，处理器/微处理器211可以包括一个或多个微处理器，或者包括一个或者多个微处理器和一个或者多个应用处理器。当处理器/微处理器211包括多个处理器时，这多个处理器可以集成在同一块处理芯片上，也可以各自为独立的处理芯片。一个处理器可以包括一个或多个处理器核(或称处理核)。
射频(RF)模块216用于接收和发送射频信号，主要集成了终端设备200的接收器和发射器。射频(RF)模块216通过射频信号与通信网络和其他通信设备通信。具体实现中，射频(RF)模块216可包括但不限于：天线系统、RF收发器、一个或多个放大器、调谐器、一个或多个振荡器、数字信号处理器、CODEC芯片、存储介质等。在一些实施例中，可在单独的芯片上实现射频(RF)模块216。
存储器215与处理器/微处理器211耦合，用于存储各种软件程序和/或多组指令。具体实现中，存储器215可包括高速随机存取的存储器，并且也可包括非易失性存储器，例如一个或多个磁盘存储设备、闪存设备或其他非易失性固态存储设备。存储器215可以存储操作系统(下述简称系统)，例如ANDROID，IOS，WINDOWS或者LINUX等嵌入式操作系统。存储器215还可以存储网络通信程序，该网络通信程序可用于与一个或多个附加设备，一个或多个终端设备，一个或多个网络设备进行通信。存储器215还可以存储用户接口程序，该用户接口程序可以通过图形化的操作界面将应用程序的内容形象逼真的显示出来，并通过菜单、对话框以及按键等输入控件接收用户对应用程序的控制操作。存储器215还可以存储一个或多个应用程序。
操作系统的程序中包含了可实现本发明实施例提供的多播承载的管理方法的计算机程序，从而使得处理器/微处理器211读取到该程序并运行该操作系统后，该操作系统可具备本发明实施例提供的多播承载的管理功能。
下面的实施例将以终端设备为执行主体对本发明实施例提供的多播承载的管理方法及装置进行描述。
本发明实施例中，名词“挂起”指在当前有其他的事务、进程或会话等任务需要执行的情况下，暂时不关闭/释放/删除当前的事务、进程或会话所对应的资源或部分资源，在执行完所述其他的事务、进程或会话等任务后可以直接使用所述当前的事务、进程或会话所对应的资源或部分资源以便于继续执行当前的任务、进程或会话。在可选方式中，挂起SC-MRB可以替换为冻结SC-MRB、封存SC-MRB、使SC-MRB休眠、锁定SC-MRB等描述。本领域的技术人员可以理解其含义。
本发明实施例中，名词“恢复”与名词“挂起”相对应，指在对其他的事务、进程或会话等任务执行结束后，对执行所述其他的事务、进程或会话等任务之前被闲置/空置的事务、进程或会话等任务对应的资源或部分资源进行重新配置/使用，为其被闲置/空置的事务、进程或会话等任务提供执行环境或资源。在可选方式中，恢复SC-MRB可以替换为解冻SC-MRB、解开SC-MRB、唤醒SC-MRB、解锁SC-MRB等描述。本领域的技术人员可以理解其含义。
下面举例对挂起和恢复进行说明。例如，在计算机操作系统中，内存资源是有限的，当计算机的内存资源不足的情况下，操作系统将内存中的程序进行合理的安排，将一部分进程暂时调离出内存使其不占用内存资源，即挂起进程；当条件允许的时候(例如内存中的一部分进程运行已经结束，释放了其占用的内存资源，当前内存资源充足)，操作系统将之前挂起的进程重新调回内存，即恢复进程。
请参见图3，图3是本发明实施例提供的一种多播承载的管理方法的流程示意图，所述方法具体可以实现在图1中的冰箱101、洗衣机102等物联网终端设备上，也可以实现在满足图2的结构框图的终端设备上，所述方法至少包括：
S301、在接收单小区多媒体广播组播服务业务信道SC-MTCH的业务数据的过程中，且存在待接收的第一类型数据的情况下，挂起所述SC-MTCH对应的单小区点对多点多媒体广播组播服务无线承载SC-MRB。
示例性的，复杂度低、功耗低的终端设备使用的带宽较小，同一时间只能在一个载波上传输数据，终端设备的不同物理层通道之间一般为分时多任务，即不同的物理层通道只能在不同的时间出现或者被建立，当需要建立另一个物理信道时，终端设备需要释放当前建立的物理信道，例如终端的物理通道分别有物理下行控制信道(Physical Downlink Control Channel，PDCCH)、物理广播信道(Physical Broadcast Channel，PBCH)以及物理下行共享数据信道(Physical Downlink Shared Channel，PDSCH)，则在同一时刻或同一时隙上，终端只能建立或运行PDCCH、PBCH或PDSCH中的一个物理信道。终端设备在同一时刻能提供给上层协议实体的物理层的资源有限，终端设备只具备同时给一个逻辑信道提供传输链路的能力，当在接收第一逻辑信道的数据的过程中，若需要接收第二逻辑 信道的数据，则根据第一逻辑信道与第二逻辑信道的传输优先级确定传输优先级高的目标逻辑信道，优先为目标逻辑信道提供传输链路。
具体地，所述第一类型数据的传输优先级高于所述SC-MTCH的业务数据，第一类型数据包括SC-MCCH中的配置信息或寻呼过程中的信息，具体实现中，第一类型数据例如可以为SC-MCCH中的调度信息、单小区点对多点机制的定时信息等配置信息，第一类型数据也可以为寻呼消息、寻呼变更指示等寻呼过程中的信息。
具体地，可以在接收到SC-MCCH的变更通知的情况下，挂起所述SC-MTCH对应的SC-MRB。SC-MCCH的变更通知指示SC-MCCH中包含的SC-MTCH的配置信息已经或即将更新，SC-MTCH的配置信息的传输优先级高于SC-MTCH的业务数据，终端设备需优先接收SC-MTCH的配置信息并更新SC-MTCH的配置。
具体地，还可以在需要接收寻呼的情况下，在监听寻呼之前挂起所述SC-MTCH对应的SC-MRB。在空口寻呼机制中，终端设备以不连续接收(Discontinuous Reception，DRX)方式接收寻呼信息以达到节省耗电量的目的，终端设备的RRC层控制物理层在寻呼周期到来时监听物理下行控制信道(Physical Downlink Control Channel，PDCCH)，并根据PDCCH中的指示，在物理下行共享数据信道(Physical Downlink Shared Chnnel，PDSCH)中接收寻呼消息来确定是否有网络侧对自己的寻呼，或是否有网络发送的系统消息变更指示，寻呼是网络侧为了确定终端设备具体的位置或者更新系统消息而发起的动作，其传输优先级高于SC-MTCH的业务数据，所以当需要接收寻呼时，终端设备优先监听PDCCH并在有寻呼消息的情况下优先接收寻呼消息。在可选方式中，终端设备可以在寻呼周期到来前的预设的一段时间内挂起所述SC-MTCH对应的SC-MRB。
具体地，SC-MRB是为接收SC-MTCH的业务数据而建立的无线承载，在存在待接收的第一类型数据的情况下，因为待接收的第一类型数据的传输优先级高于SC-MTCH的业务数据，需要优先传输第一类型数据，优先为第一类型数据提供传输链路，即需要为第一数据配置对应的物理层和/或MAC层。
具体地，终端设备只具备同时给一个逻辑信道提供传输链路的能力，在不释放SC-MRB的情况下，挂起SC-MRB包括：保留所述SC-MRB对应的RLC实体，以及释放所述SC-MRB对应的媒体接入控制MAC层的配置和/或物理层的配置。
应当理解的是，在不释放SC-MRB的情况下，若仅释放所述SC-MRB对应的物理层配置，则在保留所述SC-MRB对应的RLC实体的同时还保留所述SC-MRB对应的MAC层的配置。
可选地，挂起SC-MRB之后还包括：通过指示与所述SC-MRB对应的临时移动组标识(Temporary Mobile Group Identity，TMGI)和/或会话标识，通知RRC层上层的协议层所述SC-MRB已经被挂起。
其中，TMGI用于区分不同的MBMS业务。例如，一个MBMS业务对应一个TMGI。会话标识用于区分不同的MBMS会话，例如，一个MBMS业务对应一个MBMS会话标识，即TGMI和会话标识均可以用于标识SC-MRB以及所述SC-MRB对应的MBMS业务，通过向RRC上层的协议层指示所述SC-MRB对应的TMGI和/或会话标识，可使RRC上层的协议层知道目标MBMS业务的对应的SC-MRB当前被挂起，终端设备暂时不能进 行所述目标MBMS业务。
具体地，向上层指示TMGI和/或会话标识的同时，还可用一个状态参数指示SC-MRB的状态。例如，状态参数的值为11，则指示所述SC-MRB已经被建立；状态参数的值为01，则指示所述SC-MRB已经被挂起；状态参数的值为10，则指示所述SC-MRB已经被恢复；状态参数为00，则指示所述SC-MRB已经被释放。
具体地，RRC上层的协议层可以为应用层。例如，用户当前正在利用终端设备的客户端收看电视节目，即终端设备当前接收的MBMS业务为电视节目，SC-MRB为电视节目提供接收服务。在存在待接收的第一类型数据的情况下，终端设备挂起SC-MRB，此时终端设备暂时不能接收SC-MRB对应的MBMS业务，则通过指示与所述SC-MRB对应的TMGI和/或会话标识通知应用层SC-MRB已经被挂起后，客户端的用户界面上显示类似“当前服务不可用”的提示信息。
可选地，在挂起所述SC-MRB后还包括：建立所述第一类型数据的第一无线承载并通过所述第一无线承载接收所述第一类型数据。
可选地，所述第一无线承载可以为信令无线承载，也可以为数据无线承载。
具体地，建立所述第一无线承载包括：建立所述第一类型数据对应的第一RLC实体，配置所述第一类型数据对应的MAC层和物理层。
S302、在完成对所述第一类型数据的接收的情况下，根据所述SC-MRB对应的临时移动组标识TMGI和/或会话标识恢复或释放所述SC-MRB。
可选地，在完成对所述第一类型数据的接收的情况下，释放为所述第一类型数据建立的第一无线承载，释放所述第一无线承载对应的RLC实体以及相应的MAC层和物理层配置。
具体地，完成对所述第一类型数据的接收可以为对SC-MCCH中的全部配置信息接收完成，也可以为对寻呼过程中的信息接收完成。
具体地，在未完成对所述SC-MTCH的业务数据的接收的情况下，根据所述SC-MRB对应的TMGI和/或会话标识恢复所述SC-MRB；在完成对所述SC-MTCH的业务数据的接收的情况下，根据所述SC-MRB对应的TMGI和/或会话标识恢复所述SC-MRB释放所述SC-MRB。
具体地，未完成对所述SC-MTCH的业务数据的接收指所述挂起的SC-MRB对应的MBMS业务接收未结束且终端设备需继续接收所述挂起的SC-MRB对应的业务数据；完成对所述SC-MTCH的业务数据的接收包括两种情况：一种指所述挂起的SC-MRB对应的MBMS业务当前已经结束；另一种指所述挂起的SC-MRB对应的MBMS业务当前未结束，但终端设备不再需要接收所述挂起的SC-MRB对应的MBMS业务。
下面结合第一类型数据举例对完成和未完成对所述SC-MTCH的业务数据的接收的情况进行说明。
在一种情况中，终端当前正在通过第一SC-MRB接收第一MBMS业务的业务数据，基站发来SC-MCCH的变更通知，则终端设备挂起第一SC-MRB，接收SC-MCCH中的配置信息，假设基站通过所述配置信息更新MBMS业务，增设第二MBMS业务，在对配置信息接收结束后第一MBMS业务仍未结束。若持有终端设备的用户对第二MBMS业务 感兴趣，希望终端设备接收第二MBMS业务，虽然第一MBMS业务未结束，但是终端设备当前不再需要接收第一MBMS业务，即完成对第一SC-MRB对应的SC-MTCH的业务数据的接收，释放第一SC-MRB，建立第二MBMS业务对应的第二SC-MRB；若持有终端设备的用户仍对第一MBMS业务感兴趣，希望终端设备继续接收第一MBMS业务，此时终端设备需要继续接收第一MBMS业务，即未完成对所述第一SC-MRB对应的SC-MTCH的业务数据的接收，终端设备恢复第一SC-MRB并在第一MBMS业务结束时释放第一SC-MRB。
在另一种情况中，终端设备当前正在通过第一SC-MRB接收第一MBMS业务的业务数据，终端设备当前需要接收寻呼，则终端设备挂起第一SC-MRB，接收寻呼；寻呼不涉及对MBMS业务的更新，则在寻呼接收后，若终端设备未被网络寻呼，同时第一MBMS业务未结束且用户对第一MBMS业务仍感兴趣，则终端设备需要继续接收第一MBMS业务，即未完成对所述SC-MTCH的业务数据的接收，终端设备恢复第一SC-MRB并在第一MBMS业务结束时释放第一SC-MRB；若第一MBMS业务未结束但是用户通过接收寻呼消息发现被网络寻呼，则需要建立RRC连接对网络进行响应，此时终端设备可能不能再继续接收第一MBMS业务，即完成对所述SC-MTCH的业务数据的接收，终端设备释放第一SC-MRB。
具体地，恢复所述SC-MRB包括：根据所述SC-MRB对应的TMGI和/或会话标识确定所述SC-MRB，并根据所述SC-MRB确定所述SC-MRB对应的RLC实体；根据SC-MCCH中的信息为所述SC-MRB配置MAC层和/或物理层。
具体地，恢复所述SC-MRB可以使用SC-MRB挂起流程中保留的与所述SC-MRB对应的RLC实体。
具体地，配置MAC层和/或物理层包括：接收单小区点对多点配置(Single Cell Point To Multipoint Configuration，SCPTMConfiguration)信息，所述SCPTMConfiguration信息包括SC-MTCH信息列表sc-mtch-InfoList；每一个SC-MTCH对应sc-mtch-InfoList中的一个sc-mtch-Info，根据所述sc-mtch-Info配置MAC层和/或物理层。
具体地，所述sc-mtch-Info包括组-无线网络临时标识(Group-Radio Network Tempory Identity，G-RNTI)、SC-MTCH调度信息(sc-mtch-SchedulingInfo)等参数信息，其中，G-RNTI用于对信道加扰，sc-mtch-SchedulingInfo为SC-MTCH设置的DRX信息，在sc-mtch-Info中不含sc-mtch-SchedulingInfo的情况下，SC-MTCH的信息可以在任何子帧中被传输。
可选地，恢复所述SC-MRB之后还包括：通过指示与所述SC-MRB对应的TMGI和/或会话标识，通知RRC层上层的协议层所述SC-MRB已经被恢复。
具体地，在步骤S101挂起SC-MRB的流程中执行通过指示与所述SC-MRB对应TMGI和/或会话标识，通知RRC层上层的协议层所述SC-MRB已经被挂起，则在所述SC-MRB恢复的情况下，相应地，可以通知RRC层上层的协议层相应的SC-MRB已经被恢复。
在图3所描述的方法中，在接收SC-MTCH的业务数据的过程中若需接收第一类型的数据，则挂起SC-MTCH对应的SC-MRB，然后接收第一类型数据，在接收第一类型数据 完成后，又恢复SC-MRB，继续接收SC-MTCH的业务数据，将SC-MRB挂起只释放MAC层和/或物理层的配置，保留SC-MRB对应的RLC实体，保留RLC实体也即保留RLC实体缓存的RLC PDU，在恢复SC-MRB时只需根据SC-MCCH中的信息重新配置MAC层和/或物理层，无需重新建立SC-MRB对应的RLC实体，也无需重新接收RLC PDU，避免反复释放和建立SC-MRB，节省网络资源和终端设备的功耗。
以上主要介绍了本发明实施例提供的方法的流程，下面结合协议结构对本发明实施例提供的方法的逻辑传输链路与RLC实体的变化进行介绍，参见图4-图5。
图4示出了一种无线通信协议的层次可能的结构示意图，无线通信协议从上往下为网络高层、RLC层、MAC层、物理层，其中，无线资源控制(Radio Resource Control，RRC)层、网络层、传输层、应用层、非接入层等均为网络高层，RLC层、MAC层为OSI第二层协议，物理层为OSI第一层协议。本发明实施例中的SC-MRB建立、挂起、恢复、释放涉及RRC层、RLC层、MAC层以及物理层。
RRC层可以实现MBMS业务通知，实现MBMS业务对应的无线承载的建立、修改与释放，其中，RRC层通过指示RLC层、MAC层以及物理层进行相应的操作完成对无线承载的建立、修改、释放。
RLC层主要实现对协议服务数据单元的分割和重组、各种数据逻辑链路的建立、释放、配置等功能，RLC层由多个RLC实体和控制实体组成，一个RLC实体对应一个RB，RLC实体可根据传输业务类型的不同，配置成非确认模式(UM)、确认模式(AM)以及透明模式(TM)，本发明实施例中SC-MRB对应的RLC实体为非确认模式RLC实体；RLC控制实体主要实现数据逻辑链路的建立、释放以及参数配置等。
MAC层处于物理层和RLC层之间，向上为RLC层提供服务，RLC层通过逻辑信道将RLC层的PDU发送给MAC层发送，MAC层向下利用物理信道使用物理层提供的服务。MAC层主要实现逻辑信道和物理信道的映射、MAC层服务数据单元(Service Data Unit，SDU)与物理层数据传输块的动态适配以及对物理层传输参数进行动态配置等功能，在本发明实施例中，MAC层实现将SC-MTCH的业务数据的PDU传递给RLC实体以使RLC实体对PDU进行重组。
物理层实现物理信道编解码、物理信道的复用与解复用、射频处理等功能。
在接收SC-MTCH的业务数据的过程中，终端设备中的逻辑传输链路的变化可以如图5所示，图5是本发明实施例提供的执行多播承载的管理方法的逻辑传输链路和RLC实体变化示意图。首先终端设备正在通过SC-MRB接收SC-MTCH的业务数据，RLC实体A为SC-MRB对应的RLC实体，MAC层和物理层中的配置均为SC-MTCH对应的配置；在存在待接收的第一类型数据的情况下，第一类型数据的传输优先级高于SC-MTCH的业务数据，则优先为第一类型数据提供传输链路，终端设备的MAC层和物理层的资源有限，则释放MAC层和物理层的配置，同时保留RLC实体A，此时SC-MRB被挂起，然后新建RLC实体B，根据待接收的第一类型数据对应的逻辑信道类型对释放后的MAC层和物理层进行重新配置，通过新建的无线承载接收第一类型数据；在完成对第一类型数据的接收后，释放RLC实体B，并释放MAC层和物理层的配置，同时为SC-MTCH配置MAC 层和物理层，RLC实体A与配置好的MAC层和物理层构成SC-MRB，此时SC-MRB被恢复，通过恢复的SC-MRB继续接收SC-MTCH的业务数据；在完成对SC-MTCH的业务数据的接收的情况下，则释放RLC实体A及SC-MRB对应的MAC层和物理层的配置完成对SC-MRB的释放。在可选情况中，在完成对第一类型数据的接收并释放RLC实体B、MAC层和物理的配置后，在不需要继续接收所述SC-MTCH的业务数据的情况下，也可直接释放RLC实体A，其中，不需要接收所述SC-MTCH的业务数据的情况已在上述实施例中举例阐述，不再赘述。
图6示出了上述实施例中所涉及的终端设备的一种可能的结构示意图，所述终端设备包括接收单元410和处理单元420，其中，各个单元的详细描述如下：
接收单元410，用于接收单小区多媒体广播组播服务业务信道SC-MTCH的业务数据；
处理单元420，用于在接收单元410接收单小区多媒体广播组播服务业务信道SC-MTCH的业务数据的过程中，且存在待接收的第一类型数据的情况下，挂起所述SC-MTCH对应的单小区多媒体广播组播服务点对多点无线承载SC-MRB；
所述处理单元420还用于在所述接收单元410完成对所述第一类型数据的接收的情况下，根据所述SC-MRB对应的临时移动组标识TMGI和/或会话标识恢复或释放所述SC-MRB。
可选地，所述处理单元420具体用于：
在所述接收单元410未完成对所述SC–MTCH的业务数据的接收的情况下，根据所述SC-MRB对应的TMGI和/或会话标识恢复所述SC-MRB；或者在所述接收单元410完成对所述SC-MTCH的业务数据的接收的情况下，根据所述SC-MRB对应的TMGI和/或会话标识释放所述SC-MRB。
可选地，所述处理单元420具体用于：
保留所述SC-MRB对应的RLC实体，以及释放所述SC-MRB对应的媒体接入控制MAC层的配置和/或物理层的配置。
可选地，所述处理单元420具体用于：
通过指示与所述SC-MRB对应的TMGI和/或会话标识，通知RRC层上层的协议层所述SC-MRB已经被挂起。
可选地，所述处理单元420具体用于：
根据所述SC-MRB对应的TMGI和/或会话标识确定所述SC-MRB，并根据所述SC-MRB确定所述SC-MRB对应的RLC实体；
根据单小区多媒体广播组播服务控制信道SC-MCCH中的信息为所述SC-MRB配置MAC层和/或物理层。
可选地，所述处理单元420具体用于：
通过指示与所述SC-MRB对应的TMGI和/或会话标识，通知RRC层上层的协议层所述SC-MRB已经被恢复。
具体地，所述第一类型数据包括传输优先级高于所述SC-MTCH的业务数据的数据。
具体地，所述传输优先级高于所述SC-MTCH的业务数据的数据包括：
SC-MCCH中的配置信息或寻呼过程中的信息。
所述处理单元420具体用于：
在接收单元410接收到SC-MTCH变更通知的情况下，挂起所述SC-MTCH对应的SC-MRB；或
在监听寻呼之前挂起所述SC-MTCH对应的SC-MRB。
在一种可能的实现方式中，所述处理单元420可以对应于图2所示的终端中的处理器211或处理芯片210，所述接收单元可以对应于图2所示的终端中的RF收发器2162或RF模块216。所述处理单元420还可以与所述接收单元410相配合，执行图3所示的方法实施例中的所有操作。
用于执行本发明实施例上述终端设备功能的控制器/处理器可以是中央处理器(CPU)，通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)，现场可编程门阵列(FPGA)或者其他可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。
在图6所述的实施例中，终端设备在接收SC-MTCH的业务数据的过程中若需接收第一类型的数据，则挂起SC-MTCH对应的SC-MRB，然后接收第一类型数据，在接收第一类型数据完成后，又恢复SC-MRB，继续接收SC-MTCH的业务数据，将SC-MRB挂起只释放MAC层和/或物理层的配置，保留了SC-MRB对应的RLC实体，在恢复SC-MRB时只需根据SC-MCCH中的信息重新配置MAC层和/或物理层，无需重新建立SC-MRB对应的RLC实体，避免反复释放和建立SC-MRB，节省网络资源和终端设备的功耗。
本发明实施例还提供一种计算机存储介质，所述计算机存储介质存储有计算机程序，所述计算机程序包括程序指令，所述程序指令当被计算机执行时使所述计算机执行如前述实施例所述的方法，所述计算机可以为上述提到的终端设备的一部分。
本发明实施例还提供一种计算机程序，包括程序指令，所述程序指令当被计算机执行时用于执行如前述实施例所述的方法。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，所述的程序可存储于一计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，所述的存储介质可为磁碟、光盘、只读存储记忆体(Read-Only Memory，ROM)或随机存储记忆体(Random Access Memory，RAM)等。
结合本发明公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于用户设备中。当然，处理器和存储介质也可以作为 分立组件存在于用户设备中。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本发明所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式，对本发明的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明的具体实施方式而已，并不用于限定本发明的保护范围，凡在本发明的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明的保护范围之内。

Claims (21)

  1. 一种多播承载的管理方法，其特征在于，包括：
    在接收单小区多媒体广播组播服务业务信道SC-MTCH的业务数据的过程中，且存在待接收的第一类型数据的情况下，挂起所述SC-MTCH对应的单小区点对多点多媒体广播组播服务无线承载SC-MRB；
    在完成对所述第一类型数据的接收的情况下，根据所述SC-MRB对应的临时移动组标识TMGI和/或会话标识恢复或释放所述SC-MRB。
  2. 如权利要求1所述的方法，其特征在于，所述根据所述SC-MRB对应的TMGI和/或会话标识恢复所述SC-MRB包括：
    在未完成对所述SC-MTCH的业务数据的接收的情况下，根据所述SC-MRB对应的TMGI和/或会话标识恢复所述SC-MRB；
    所述根据所述SC-MRB对应的TMGI和/或会话标识释放所述SC-MRB包括：
    在完成对所述SC-MTCH的业务数据的接收的情况下，根据所述SC-MRB对应的TMGI和/或会话标识释放所述SC-MRB。
  3. 如权利要求1或2所述的方法，其特征在于，所述挂起所述SC-MTCH对应的SC-MRB包括：
    保留所述SC-MRB对应的RLC实体，以及释放所述SC-MRB对应的媒体接入控制MAC层的配置和/或物理层的配置。
  4. 如权利要求1-3任一项所述的方法，其特征在于，所述挂起所述SC-MTCH对应的SC-MRB之后还包括：
    通过指示与所述SC-MRB对应的TMGI和/或会话标识，通知无线资源控制RRC层上层的协议层所述SC-MRB已经被挂起。
  5. 如权利要求3所述的方法，其特征在于，所述根据所述SC-MRB对应的TMGI和/或会话标识恢复所述SC-MRB包括：
    根据所述SC-MRB对应的TMGI和/或会话标识确定所述SC-MRB，并根据所述SC-MRB确定所述SC-MRB对应的RLC实体；
    根据单小区多媒体广播组播服务控制信道SC-MCCH中的信息为所述SC-MRB配置MAC层和/或物理层。
  6. 如权利要求1-5任一项所述的方法，其特征在于，所述根据所述SC-MRB对应的TMGI和/或会话标识恢复所述SC-MRB之后还包括：
    通过指示与所述SC-MRB对应的TMGI和/或会话标识，通知RRC层上层的协议层所述SC-MRB已经被恢复。
  7. 如权利要求1-6任一项所述的方法，其特征在于，所述第一类型数据包括传输优先级高于所述SC-MTCH的业务数据的数据。
  8. 如权利要求7所述的方法，其特征在于，所述传输优先级高于所述SC-MTCH的业务数据的数据包括：
    SC-MCCH中的配置信息或寻呼过程中的信息。
  9. 如权利要求1-8任一项所述的方法，其特征在于，所述在存在待接收的第一类型数据的情况下，挂起所述SC-MTCH对应的SC-MRB包括：
    在接收到SC-MCCH变更通知的情况下，挂起所述SC-MTCH对应的SC-MRB；或在监听寻呼之前挂起所述SC-MTCH对应的SC-MRB。
  10. 一种终端设备，其特征在于，包括：
    接收单元，用于接收单小区多媒体广播组播服务业务信道SC-MTCH的业务数据；
    处理单元，用于在接收单元接收SC-MTCH的业务数据的过程中，且存在待接收的第一类型数据的情况下，挂起所述SC-MTCH对应的单小区多媒体广播组播服务点对多点无线承载SC-MRB；
    所述处理单元还用于在所述接收单元完成对所述第一类型数据的接收的情况下，根据所述SC-MRB对应的临时移动组标识TMGI和/或会话标识恢复或释放所述SC-MRB。
  11. 如权利要求10所述的终端设备，其特征在于，所述处理单元具体用于：
    在所述接收单元未完成对所述SC-MTCH的业务数据的接收的情况下，根据所述SC-MRB对应的TMGI和/或会话标识恢复所述SC-MRB；或者
    在所述接收单元完成对所述SC-MTCH的业务数据的接收的情况下，根据所述SC-MRB对应的TMGI和/或会话标识释放所述SC-MRB。
  12. 如权利要求10或11所述的终端设备，其特征在于，所述处理单元具体用于：
    保留所述SC-MRB对应的RLC实体，以及释放所述SC-MRB对应的媒体接入控制MAC层的配置和/或物理层的配置。
  13. 如权利要求10-12任一项所述的终端设备，其特征在于，所述处理单元具体用于：
    通过指示与所述SC-MRB对应的TMGI和/或会话标识，通知无线资源控制RRC层上层的协议层所述SC-MRB已经被挂起。
  14. 如权利要求12所述的终端设备，其特征在于，所述处理单元具体用于：
    根据所述SC-MRB对应的TMGI和/或会话标识确定所述SC-MRB，并根据所述SC-MRB确定所述SC-MRB对应的RLC实体；或者
    根据单小区多媒体广播组播服务控制信道SC-MCCH中的信息为所述SC-MRB配置MAC层和/或物理层。
  15. 如权利要求10-14所述的终端设备，其特征在于，所述处理单元具体用于：
    通过指示与所述SC-MRB对应的TMGI和/或会话标识，通知RRC层上层的协议层所述SC-MRB已经被恢复。
  16. 如权利要求10-15任一项所述的设备，其特征在于，所述第一类型数据包括传输优先级高于所述SC-MTCH的业务数据的数据。
  17. 如权利要求16所述的设备，其特征在于，所述传输优先级高于所述SC-MTCH的业务数据的数据包括：
    SC-MCCH中的配置信息或寻呼过程中的信息。
  18. 如权利要求11所述的终端设备，其特征在于，所述处理单元具体用于：
    在所述接收单元接收到SC-MCCH变更通知的情况下，挂起所述SC-MTCH对应的SC-MRB；或
    在监听寻呼之前挂起所述SC-MTCH对应的SC-MRB。
  19. 一种计算机存储介质，其特征在于，所述计算机存储介质存储有计算机程序，所述计算机程序包括程序指令，所述程序指令当被计算机执行时使所述计算机执行如权利要求1-9任一项所述的方法。
  20. 一种计算机程序，其特征在于，包括程序指令，所述程序指令当被计算机执行时用于执行如权利要求1-9任一项所述的方法。
  21. 一种通信系统，其特征在于，包括网络通信设备和如权利要求10-18任一项所述的终端设备，其中：
    所述网络通信设备用于向所述终端设备发送单小区多媒体广播组播服务业务信道SC-MTCH的业务数据；
    所述终端设备用于执行如权利要求1-9任一项所述的方法。
PCT/CN2017/083323 2017-05-05 2017-05-05 多播承载的管理方法和终端设备 WO2018201476A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
RU2019139457A RU2739290C1 (ru) 2017-05-05 2017-05-05 Способ управления многоадресным однонаправленным каналом и оконечное устройство
JP2019560654A JP6856774B2 (ja) 2017-05-05 2017-05-05 マルチキャストベアラ管理方法及び端末デバイス
CN201780087199.8A CN110326313B (zh) 2017-05-05 2017-05-05 多播承载的管理方法和终端设备
PCT/CN2017/083323 WO2018201476A1 (zh) 2017-05-05 2017-05-05 多播承载的管理方法和终端设备
EP17908374.6A EP3641351B1 (en) 2017-05-05 2017-05-05 Multicast bearer management method and terminal device
US16/672,285 US11240640B2 (en) 2017-05-05 2019-11-01 Multicast bearer management method and terminal device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/083323 WO2018201476A1 (zh) 2017-05-05 2017-05-05 多播承载的管理方法和终端设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/672,285 Continuation US11240640B2 (en) 2017-05-05 2019-11-01 Multicast bearer management method and terminal device

Publications (1)

Publication Number Publication Date
WO2018201476A1 true WO2018201476A1 (zh) 2018-11-08

Family

ID=64016359

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/083323 WO2018201476A1 (zh) 2017-05-05 2017-05-05 多播承载的管理方法和终端设备

Country Status (6)

Country Link
US (1) US11240640B2 (zh)
EP (1) EP3641351B1 (zh)
JP (1) JP6856774B2 (zh)
CN (1) CN110326313B (zh)
RU (1) RU2739290C1 (zh)
WO (1) WO2018201476A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024077421A1 (zh) * 2022-10-09 2024-04-18 北京小米移动软件有限公司 组播业务数据的传输方法及装置、存储介质

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018084195A1 (ja) * 2016-11-04 2018-05-11 京セラ株式会社 無線端末及び基地局
US11399406B2 (en) * 2019-10-24 2022-07-26 Qualcomm Incorporated Maintaining a multicast/broadcast radio bearer in an idle state or an inactive state
CN113163342B (zh) * 2020-01-22 2022-06-07 维沃移动通信有限公司 承载建立方法、配置方法、终端及网络侧设备
CN113543040B (zh) * 2020-04-22 2023-04-07 维沃移动通信有限公司 数据处理方法、数据处理装置及通信设备
CN114071380B (zh) * 2020-08-05 2023-05-26 维沃移动通信有限公司 多播业务的接收方法、配置方法、终端及网络侧设备
WO2022082340A1 (en) * 2020-10-19 2022-04-28 Mediatek Singapore Pte. Ltd. Methods and apparatus to deliver reliable multicast services via mrb
CN115038048B (zh) * 2021-03-05 2023-07-07 维沃移动通信有限公司 多播业务的接收方法、配置方法、终端及网络侧设备
WO2023069709A1 (en) * 2021-10-21 2023-04-27 Google Llc Managing reception of multicast and/or broadcast services after a state transition
CN114554423B (zh) * 2022-03-30 2023-10-20 上海交通大学 一种mbs业务的挂起方法及收发装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102724636A (zh) * 2011-03-30 2012-10-10 中兴通讯股份有限公司 一种mbms业务处理方法和系统
CN102932743A (zh) * 2011-08-08 2013-02-13 华为技术有限公司 多媒体广播组播业务数据的传输控制方法、装置和系统
CN104349303A (zh) * 2013-08-05 2015-02-11 中兴通讯股份有限公司 设备到设备连接管理方法、装置及基站
CN105635984A (zh) * 2014-11-07 2016-06-01 中兴通讯股份有限公司 指示信息处理方法及装置
US20160192327A1 (en) * 2014-12-29 2016-06-30 Lg Electronics Inc. Method for informing mtch suspension information in a mbms wireless communication system and device therefor

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101010774B1 (ko) 2004-02-11 2011-01-25 엘지전자 주식회사 이동통신 시스템에서 점대다 서비스 데이터의 송수신방법
US20090124196A1 (en) * 2005-07-20 2009-05-14 Ntt Docomo, Inc. Multimedia content providing method and mobile station
US9277434B2 (en) * 2011-07-29 2016-03-01 Telefonaktiebolaget L M Ericsson (Publ) Identification of UE counting results in eMBMS
KR101935785B1 (ko) * 2011-08-16 2019-04-03 삼성전자 주식회사 무선통신시스템에서 멀티미디어 방송 서비스를 수신하는 방법 및 장치
WO2016072792A1 (ko) * 2014-11-07 2016-05-12 엘지전자 주식회사 Mbms 서비스를 중단 및 재개하는 방법 및 장치
CN106470498B (zh) * 2015-08-17 2020-09-29 中兴通讯股份有限公司 Sc-mcch发送方法、sc-ptm接收方法及其装置
WO2017196085A2 (ko) * 2016-05-11 2017-11-16 엘지전자 주식회사 무선 통신 시스템에서 v2v 통신을 위해 하향링크 방송을 향상시키는 방법 및 장치
WO2018084195A1 (ja) * 2016-11-04 2018-05-11 京セラ株式会社 無線端末及び基地局
US10966187B2 (en) * 2016-11-04 2021-03-30 Lg Electronics Inc. Method for transmitting and receiving data in wireless communication system and apparatus therefor
CN106454759A (zh) * 2016-12-07 2017-02-22 海能达通信股份有限公司 数据处理系统、方法、装置及用户设备及基站

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102724636A (zh) * 2011-03-30 2012-10-10 中兴通讯股份有限公司 一种mbms业务处理方法和系统
CN102932743A (zh) * 2011-08-08 2013-02-13 华为技术有限公司 多媒体广播组播业务数据的传输控制方法、装置和系统
CN104349303A (zh) * 2013-08-05 2015-02-11 中兴通讯股份有限公司 设备到设备连接管理方法、装置及基站
CN105635984A (zh) * 2014-11-07 2016-06-01 中兴通讯股份有限公司 指示信息处理方法及装置
US20160192327A1 (en) * 2014-12-29 2016-06-30 Lg Electronics Inc. Method for informing mtch suspension information in a mbms wireless communication system and device therefor

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3641351A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024077421A1 (zh) * 2022-10-09 2024-04-18 北京小米移动软件有限公司 组播业务数据的传输方法及装置、存储介质

Also Published As

Publication number Publication date
EP3641351A1 (en) 2020-04-22
JP2020519180A (ja) 2020-06-25
JP6856774B2 (ja) 2021-04-14
RU2739290C1 (ru) 2020-12-22
CN110326313B (zh) 2020-11-10
CN110326313A (zh) 2019-10-11
US20200068359A1 (en) 2020-02-27
EP3641351B1 (en) 2022-07-13
US11240640B2 (en) 2022-02-01
EP3641351A4 (en) 2020-04-22

Similar Documents

Publication Publication Date Title
WO2018201476A1 (zh) 多播承载的管理方法和终端设备
WO2017185867A1 (zh) 一种进行业务传输的方法和终端
TWI646849B (zh) 用於演進節點ｂ參數調諧的輔助資訊
WO2022205381A1 (zh) 广播多播业务传输方法、装置及存储介质
WO2022126546A1 (zh) 信息传输方法、装置、通信设备和存储介质
WO2017193766A1 (zh) 一种下行数据传输的方法及设备
CN114449043B (zh) 通信方法及通信装置
CN107046714B (zh) 一种数据传输方法、装置和系统
CN104105199A (zh) 一种进行寻呼的方法、装置及系统
TW201428481A (zh) 應用驅動之快速休眠
WO2021004191A1 (zh) 一种支持时间敏感网络的方法及装置
WO2022104542A1 (zh) 无线通信方法和通信装置
WO2022075912A1 (en) Group pdcp discard timer for low-latency services
WO2021056152A1 (zh) 一种信息配置方法及装置、终端设备、网络设备
US8792437B2 (en) Synchronized use of a wireless channel by multiple applications
WO2018001151A1 (zh) 寻呼方法、ran-up实体、ran-cp实体及ue
WO2021207899A1 (zh) 信息发送方法、用户设备、基站设备及计算机存储介质
WO2021134763A1 (zh) 一种恢复传输的方法、装置及设备
WO2014190839A1 (zh) 一种非接入层消息的发送方法、基站及核心网设备
WO2023179357A1 (zh) 一种通信方法及装置
WO2023010316A1 (zh) 通信配置方法、装置、通信设备及存储介质
CN113747550B (zh) 一种通信方法和装置
WO2023093696A1 (zh) 一种通信方法及装置
WO2022016338A1 (zh) 一种通信方法及装置
WO2017133282A1 (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: 17908374

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019560654

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017908374

Country of ref document: EP

Effective date: 20191127