WO2022227071A1 - 一种承载配置方法及装置、终端设备、网络设备 - Google Patents

一种承载配置方法及装置、终端设备、网络设备 Download PDF

Info

Publication number
WO2022227071A1
WO2022227071A1 PCT/CN2021/091695 CN2021091695W WO2022227071A1 WO 2022227071 A1 WO2022227071 A1 WO 2022227071A1 CN 2021091695 W CN2021091695 W CN 2021091695W WO 2022227071 A1 WO2022227071 A1 WO 2022227071A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
terminal device
released
srb2
data bearer
Prior art date
Application number
PCT/CN2021/091695
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 CN202311408809.3A priority Critical patent/CN117221966A/zh
Priority to PCT/CN2021/091695 priority patent/WO2022227071A1/zh
Priority to CN202180082804.9A priority patent/CN116602004A/zh
Priority to EP21938545.7A priority patent/EP4271040A4/en
Publication of WO2022227071A1 publication Critical patent/WO2022227071A1/zh
Priority to US18/359,050 priority patent/US20230370299A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • 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
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • 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/40—Connection management for selective distribution or broadcast
    • 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
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections

Definitions

  • the embodiments of the present application relate to the field of mobile communication technologies, and in particular, to a bearer configuration method and apparatus, terminal equipment, and network equipment.
  • the terminal equipment needs to enter the Radio Resource Control (RRC) connection state to receive unicast services.
  • RRC Radio Resource Control
  • the terminal equipment With the introduction of the Multimedia Broadcast Service (MBS) service, the terminal equipment also needs to enter the RRC connection state to receive the MBS service in the multicast mode. At this time, how to support mobility in the RRC connected state needs to be clarified.
  • MBS Multimedia Broadcast Service
  • Embodiments of the present application provide a bearer configuration method and apparatus, terminal equipment, and network equipment.
  • the terminal device receives a bearer configuration instruction sent by the network device, where the bearer configuration instruction is used to configure a signaling radio bearer (Signalling Radio Bearer, SRB) 2 and at least one data bearer for the terminal device, wherein the at least one data bearer It includes at least one data radio bearer (Data Radio Bearer, DRB) and/or at least one multicast radio bearer (Multicast Radio Bearer, MRB).
  • SRB Signaling radio Bearer
  • DRB Data Radio Bearer
  • MRB Multicast Radio Bearer
  • the network device sends a bearer configuration instruction to the terminal device, where the bearer configuration instruction is used to configure SRB2 and at least one data bearer for the terminal device, wherein the at least one data bearer includes at least one DRB and/or at least one MRB.
  • the bearer configuration apparatus provided by the embodiment of the present application is applied to a terminal device, and the apparatus includes:
  • a receiving unit configured to receive a bearer configuration instruction sent by a network device, where the bearer configuration instruction is used to configure SRB2 and at least one data bearer for the terminal device, wherein the at least one data bearer includes at least one DRB and/or at least one data bearer an MRB.
  • the bearer configuration apparatus provided by the embodiment of the present application is applied to network equipment, and the apparatus includes:
  • a sending unit configured to send a bearer configuration instruction to a terminal device, where the bearer configuration instruction is used to configure SRB2 and at least one data bearer for the terminal device, wherein the at least one data bearer includes at least one DRB and/or at least one data bearer MRB.
  • the terminal device provided by the embodiments of the present application includes a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and execute the computer program stored in the memory to execute the above-mentioned bearer configuration method.
  • the network device provided by the embodiments of the present application includes a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and execute the computer program stored in the memory to execute the above-mentioned bearer configuration method.
  • the chip provided by the embodiment of the present application is used to implement the above bearing configuration method.
  • the chip includes: a processor for invoking and running a computer program from the memory, so that the device on which the chip is installed executes the above-mentioned bearer configuration 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 bearer configuration method.
  • the computer program product provided by the embodiments of the present application includes computer program instructions, and the computer program instructions cause a computer to execute the above-mentioned bearer configuration method.
  • the computer program provided by the embodiment of the present application when it runs on the computer, causes the computer to execute the above-mentioned bearer configuration method.
  • the network device configures SRB2 and at least one data bearer for the terminal device, wherein the at least one data bearer includes at least one DRB and/or at least one MRB, so that the terminal device can support RRC based on SRB2 and at least one data bearer Mobility process in connected state.
  • FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application.
  • Fig. 2 is a transmission network architecture diagram of an MBS service provided by an embodiment of the present application
  • FIG. 3 is a schematic flowchart of a bearer configuration method provided by an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram 1 of a bearing configuration device provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram 2 of the structural composition of the bearing configuration device provided by the embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • FIG. 8 is a schematic block diagram of a communication system provided by an embodiment of the present application.
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • 5G communication systems or future communication systems etc.
  • the communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal 120 (or referred to as a communication terminal, a terminal).
  • the network device 110 may provide communication coverage for a particular geographic area and may communicate with terminals located within the coverage area.
  • the network device 110 may be an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the
  • the network device can be a mobile switching center, a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a network device in a future communication system.
  • the communication system 100 also includes at least one terminal 120 located within the coverage of the network device 110 .
  • Terminal includes, but is not limited to, connections via wired lines, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connections; and/or another data connection/network; and/or via a wireless interface, e.g. for cellular networks, Wireless Local Area Networks (WLAN), digital television networks such as DVB-H networks, satellite networks, AM-FM A broadcast transmitter; and/or a device of another terminal configured to receive/transmit a communication signal; and/or an Internet of Things (IoT) device.
  • PSTN Public Switched Telephone Networks
  • DSL Digital Subscriber Line
  • WLAN Wireless Local Area Networks
  • WLAN Wireless Local Area Networks
  • digital television networks such as DVB-H networks, satellite networks, AM-FM A broadcast transmitter
  • IoT Internet of Things
  • a terminal arranged to communicate through a wireless interface may be referred to as a "wireless communication terminal", “wireless terminal” or “mobile terminal”.
  • mobile terminals include, but are not limited to, satellite or cellular telephones; Personal Communications System (PCS) terminals that may combine cellular radio telephones with data processing, facsimile, and data communications capabilities; may include radio telephones, pagers, Internet/Intranet PDAs with networking access, web browsers, memo pads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or others including radiotelephone transceivers electronic device.
  • PCS Personal Communications System
  • GPS Global Positioning System
  • a terminal may refer to an access terminal, user equipment (UE), subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device.
  • the access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in 5G networks or terminals in future evolved PLMNs, etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • direct terminal (Device to Device, D2D) communication may be performed between the terminals 120 .
  • the 5G communication system or the 5G network may also be referred to as a new radio (New Radio, NR) system or an NR network.
  • New Radio NR
  • NR New Radio
  • FIG. 1 exemplarily shows one network device and two terminals.
  • the communication system 100 may include multiple network devices, and the coverage of each network device may include other numbers of terminals. This embodiment of the present application This is not limited.
  • the communication system 100 may further include other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.
  • network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.
  • a device having a communication function in the network/system may be referred to as a communication device.
  • the communication device may include a network device 110 and a terminal 120 with a communication function, and the network device 110 and the terminal 120 may be the specific devices described above, which will not be repeated here;
  • the device may further include other devices in the communication system 100, such as other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.
  • 5G 3rd Generation Partnership Project
  • eMBB Enhanced Mobile Broadband
  • URLLC Ultra-Reliable Low-Latency Communications
  • mMTC Massive Machine-Type Communications
  • eMBB still aims at users' access to multimedia content, services and data, and its demand is growing rapidly.
  • eMBB since eMBB may be deployed in different scenarios, such as indoor, urban, rural, etc., its capabilities and requirements are also quite different, so it cannot be generalized and must be analyzed in detail in combination with specific deployment scenarios.
  • Typical applications of URLLC include: industrial automation, power automation, telemedicine operations (surgery), traffic safety assurance, etc.
  • Typical features of mMTC include: high connection density, small data volume, latency-insensitive services, low cost and long service life of the module.
  • RRC_INACTIVE Radio Resource Control
  • RRC_INACTIVE Radio Resource Control
  • RRC_IDLE state (referred to as idle state): mobility is based on terminal device cell selection and reselection, paging is initiated by the core network (Core Network, CN), and the paging area is configured by the CN. There is no terminal device context and no RRC connection on the base station side.
  • RRC_CONNECTED state (referred to as connected (connected) state for short): there is an RRC connection, and a terminal device context exists on the base station side and the terminal device side.
  • the network side knows that the location of the terminal equipment is at the specific cell level. Mobility is the mobility controlled by the network side. Unicast data can be transmitted between the terminal equipment and the base station.
  • RRC_INACTIVE state (referred to as inactive state): mobility is based on terminal equipment cell selection reselection, there is a connection between CN-NR, terminal equipment context exists on a certain base station, paging is triggered by RAN , the RAN-based paging area is managed by the RAN, and the network side knows the location of the terminal device is based on the RAN-based paging area level.
  • MBMS is a technology that transmits data from a data source to multiple terminal devices by sharing network resources. This technology can effectively utilize network resources while providing multimedia services, and realize the broadcast of multimedia services at higher rates (such as 256kbps). and multicast.
  • 3GPP clearly proposes to enhance the support capability for downlink high-speed MBMS services, and determines the design requirements for the physical layer and air interface.
  • eMBMS evolved MBMS
  • SFN Single Frequency Network
  • MBSFN Multimedia Broadcast Multicast Service Single Frequency Network
  • MBSFN uses a uniform frequency to send service data in all cells at the same time, but To ensure synchronization between cells. In this way, the overall signal-to-noise ratio distribution of the cell can be greatly improved, and the spectral efficiency will also be greatly improved accordingly.
  • eMBMS implements service broadcast and multicast based on IP multicast protocol.
  • MBMS has only a broadcast bearer mode and no multicast bearer mode.
  • the reception of the MBMS service is applicable to the terminal equipment in the idle state or the connected state.
  • SC-PTM Single Cell Point To Multiploint
  • SC-MCCH Single Cell Multicast Control Channel
  • SC-MTCH Single Cell Multicast Transport Channel
  • SC-MCCH and SC-MTCH are mapped to downlink shared channel (Downlink-Shared Channel, DL-SCH), further, DL-SCH is mapped to physical downlink shared channel (Physical Downlink Shared Channel, PDSCH), wherein, SC - MCCH and SC-MTCH belong to logical channels, DL-SCH belongs to transport channels, and PDSCH belongs to physical channels.
  • SC-MCCH and SC-MTCH do not support hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ) operations.
  • Hybrid Automatic Repeat reQuest Hybrid Automatic Repeat reQuest
  • MBMS introduces a new system information block (System Information Block, SIB) type, namely SIB20.
  • SIB System Information Block
  • the configuration information of the SC-MCCH includes the modification period of the SC-MCCH, the repetition period of the SC-MCCH, and information such as the radio frame and subframe in which the SC-MCCH is scheduled.
  • SFN represents the system frame number of the radio frame
  • mcch-RepetitionPeriod represents the repetition period of SC-MCCH
  • mcch-Offset represents SC-MCCH offset.
  • the SC-MCCH is scheduled through the Physical Downlink Control Channel (PDCCH).
  • PDCCH Physical Downlink Control Channel
  • RNTI Radio Network Tempory Identity
  • SC-RNTI Single Cell RNTI
  • the fixed value of SC-RNTI is FFFC.
  • a new RNTI is introduced, that is, a single cell notification RNTI (Single Cell Notification RNTI, SC-N-RNTI) to identify the PDCCH (such as the notification PDCCH) used to indicate the change notification of the SC-MCCH, optionally, the SC
  • the fixed value of -N-RNTI is FFFB; further, one of the 8 bits (bits) of DCI 1C can be used to indicate the change notification.
  • the configuration information of the SC-PTM is based on the SC-MCCH configured by the SIB20, and then the SC-MCCH configures the SC-MTCH, and the SC-MTCH is used to transmit service data.
  • the SC-MCCH only transmits one message (ie, SCPTMConfiguration), which is used to configure the configuration information of the SC-PTM.
  • the configuration information of SC-PTM includes: Temporary Mobile Group Identity (TMGI), session identifier (session id), group RNTI (Group RNTI, G-RNTI), discontinuous reception (Discontinuous Reception, DRX) configuration information And the SC-PTM service information of neighboring cells, etc.
  • TMGI Temporary Mobile Group Identity
  • session id session identifier
  • group RNTI Group RNTI, G-RNTI
  • discontinuous reception discontinuous Reception
  • DRX discontinuous Reception
  • Downlink discontinuous reception of SC-PTM is controlled by the following parameters: onDurationTimerSCPTM, drx-InactivityTimerSCPTM, SC-MTCH-SchedulingCycle, and SC-MTCH-SchedulingOffset.
  • the downstream SC-PTM service is received only when the timer onDurationTimerSCPTM or drx-InactivityTimerSCPTM is running.
  • SC-PTM business continuity adopts the concept of MBMS business continuity based on SIB15, namely "SIB15+MBMSInterestIndication" mode.
  • SIB15 namely "SIB15+MBMSInterestIndication" mode.
  • the service continuity of terminal equipment in idle state is based on the concept of frequency priority.
  • the MBS service of the multicast type refers to the MBS service transmitted in a multicast manner.
  • the broadcast-type MBS service refers to the MBS service transmitted in a broadcast manner.
  • the MBS service is sent to all terminal devices in a certain group.
  • the terminal device receives the MBS service of the multicast type in the RRC connection state, and the terminal device can receive the MBS service data of the multicast type in the point-to-multipoint (Point To Multipoint, PTM) mode or the point-to-point (Point To Point, PTP) mode.
  • PTM Point To Multipoint
  • PTP Point To Point
  • the MBS service data in the PTM mode scrambles the corresponding scheduling information through the G-RNTI configured on the network side
  • the MBS service data in the PTP mode scrambles the corresponding scheduling information through the C-RNTI.
  • the MSB service is transmitted by multicast, in other words, the MSB service is a multicast MBS service.
  • the base station can deliver the MSB service to all terminal devices in a group through an air interface.
  • the base station may deliver the MSB service to all terminal devices in a group in a PTP manner and/or a PTM manner.
  • a group includes terminal equipment 1, terminal equipment 2 and terminal equipment 3.
  • the base station can deliver the MBS service to terminal equipment 1 through PTP, deliver the MBS service to terminal equipment 2 through PTP, and deliver the MBS service through PTP to terminal equipment 2.
  • the service is delivered to the terminal device 3; alternatively, the base station can deliver the MBS service to the terminal device 1 through the PTP mode, and the MBS service can be delivered to the terminal device 2 and the terminal device 3 through the PTM mode;
  • the MBS service is delivered to terminal equipment 1, terminal equipment 2 and terminal equipment 3.
  • a shared GTP tunnel (Shared GTP tunnel) is used between the core network and the base station to transmit the MBS service, that is, whether it is the MBS service of the PTM mode or the MBS service of the PTP mode, this GTP tunnel is shared.
  • the base station delivers the MBS service data to UE1 and UE2 according to the PTM mode, and delivers the MBS service data to the UE3 according to the PTP mode.
  • a terminal device For a terminal device that receives an MBS service, it also receives other non-MBS services, such as eMBB services. Therefore, when there is no MBS service transmission, the terminal device can be released to an idle state or an inactive state or kept in a connected state by the network side. When the terminal device is in an idle state or an inactive state, when the data of the MBS service arrives, the network side can wake up the terminal device through paging to receive the MBS service.
  • eMBB services non-MBS services
  • the terminal device When the terminal device is in the RRC connected state and there is a bearer for receiving unicast services, the terminal device supports mobility procedures in the RRC connected state, such as handover process, RRC connection reestablishment process, and terminal device context request process.
  • MBS services With the introduction of MBS services, the terminal equipment needs to enter the RRC connection state to receive services. There are scenarios where only MBS services are received but no unicast services are received, and there are scenarios where only unicast services are received but no MBS services are received. Scenarios of MBS service and unicast service. At this point, how to support the mobility of the terminal device needs to be clarified.
  • FIG. 3 is a schematic flowchart of a bearer configuration method provided by an embodiment of the present application. As shown in FIG. 3 , the bearer configuration method includes the following steps:
  • Step 301 The network device sends a bearer configuration instruction to the terminal device, and the terminal device receives the bearer configuration instruction sent by the network device, where the bearer configuration instruction is used to configure the signaling SRB2 and at least one data bearer for the terminal device, wherein the At least one data bearer includes at least one DRB and/or at least one MRB.
  • the network device may be a base station.
  • the types of radio bearers can be divided into: SRB, DRB, and MRB.
  • SRB belongs to signaling bearer
  • DRB and MRB belong to data bearer.
  • the DRB is a bearer for the terminal equipment to receive the unicast service.
  • the MRB is a bearer for the terminal equipment to receive a multicast service, and here, the multicast service refers to a multicast MBS service.
  • the SRB will be described below.
  • SRBs are used to transmit signaling.
  • SRB0 is the default bearer, and the bearer already exists when the terminal device is in the RRC idle state or the RRC inactive state.
  • the RRC entity is the entity that manages the bearer, and completes functions such as establishment, modification and release of the bearer through the interaction of RRC signaling. Because the SRB0 does not need to be established, the terminal device can obtain the configuration and resources of the SRB0 in the RRC idle state or the RRC inactive state, and can use it directly if necessary.
  • SRB1 can be established by transmitting signaling on SRB0.
  • the terminal device After SRB1 is established, the terminal device enters the RRC connection state, and then transmits signaling through SRB1 to establish SRB2, which is used to transmit non-access stratum (NAS) signaling; use SRB1 to transmit signaling
  • SRB2 which is used to transmit non-access stratum (NAS) signaling; use SRB1 to transmit signaling
  • a data bearer can also be established, and the data bearer is used to transmit service data.
  • the bearer is managed by the SRB1.
  • the signaling transmitted on the SRB1 can release all the data bearers and signaling bearers, so that the terminal device enters the RRC idle state. , the only resource that the UE can use when needed is SRB0, and it needs to be done after the random access is completed.
  • the RRC setup (RRC Setup) message is used to establish SRB1 and is carried in SRB0.
  • the RRC reconfiguration (RRCReconfiguration) message is used to modify the RRC connection and is carried in SRB1.
  • SRB2 and DRB the establishment of the SRB2 and the data bearer is initiated only after the access stratum (AS) security is activated.
  • AS access stratum
  • E-UTRAN will not establish these bearers until security is activated.
  • the bearer when a network device configures a bearer for a terminal device, the bearer is configured under certain configuration constraints.
  • the configuration constraint is: SRB2 and data bearer must be configured at the same time.
  • a network device cannot be configured with only one SRB2 or only at least one data bearer.
  • the bearer configuration instruction sent by the network device to the terminal device is used to configure SRB2 and at least one data bearer for the terminal device, wherein the at least one data bearer includes at least one DRB and/or at least one MRB.
  • the terminal device is the terminal device in the RRC connection state, that is, the SRB1 has been established.
  • the bearer configuration instruction is RRC dedicated signaling.
  • the bearer configuration instruction is carried in SRB1.
  • the network device due to the existence of the above configuration constraints, the network device also needs to comply with the configuration constraints when releasing the bearer. Based on this configuration constraint, if all the at least one data bearer is released, the SRB2 is also released; or, if the SRB2 is released, all of the at least one data bearer are also released. Optionally, further, if the SRB2 and all the at least one data bearer are released, the RRC connection is also released.
  • the network device releases the data bearer
  • the SRB2 also needs to be released.
  • the RRC connection of the terminal equipment also needs to be released (ie SRB1 is released).
  • the terminal device after the terminal device is configured with the above-mentioned bearer, it supports mobility procedures in the following multiple scenarios.
  • the terminal device can receive a synchronous reconfiguration, where the synchronous reconfiguration is carried in the RRC reconfiguration.
  • the at least one data bearer includes at least one DRB and/or at least one MRB.
  • reconfigurationWithSync synchronous reconfiguration
  • the masterCellGroup configuration is carried in an RRC reconfiguration (RRCReconfiguration) message.
  • the SRB2 and the at least one data bearer need not be in a suspended state before the terminal device can receive the synchronous reconfiguration .
  • Scenario 2 RRC connection reestablishment scenario
  • the terminal device can trigger an RRC connection re-establishment process after the AS security is activated and the SRB2 and the at least one data bearer are established based on the bearer configuration instruction, and the at least one data bearer includes at least one DRB and/or at least one MRB.
  • the terminal device does not support mobility procedures in the following scenarios.
  • the terminal device cannot receive synchronous reconfiguration, wherein the synchronous reconfiguration is carried in an RRC reconfiguration message. If the terminal device is configured with MRB and not configured with DRB, the terminal device cannot trigger the RRC connection re-establishment process.
  • the terminal device when the terminal device is only configured with MRB but not configured with DRB, regardless of whether AS security is activated at this time, the terminal device does not support receiving synchronous reconfiguration and triggering the RRC connection re-establishment process.
  • synchronous reconfiguration is called "reconfigurationWithSync", where reconfigurationWithSync is contained in the "masterCellGroup” configuration.
  • the masterCellGroup configuration is carried in an RRC reconfiguration (RRCReconfiguration) message.
  • the terminal device Since the terminal device does not support the above mobility procedure, if a failure event occurs, the terminal device directly enters the RRC idle state.
  • the failure event includes at least one of the following: radio link failure, RRC reconfiguration failure, and integrity protection verification failure.
  • the configuration constraints on the bearer and the behavior constraints on the terminal equipment are provided, so that the MBS configuration is reasonable and effective.
  • FIG. 4 is a schematic structural diagram 1 of a bearer configuration apparatus provided by an embodiment of the present application, which is applied to a terminal device.
  • the bearer configuration apparatus includes:
  • a receiving unit 401 configured to receive a bearer configuration instruction sent by a network device, where the bearer configuration instruction is used to configure SRB2 and at least one data bearer for the terminal device, wherein the at least one data bearer includes at least one DRB and/or At least one MRB.
  • the bearer configuration instruction is RRC dedicated signaling.
  • the terminal device can receive synchronous reconfiguration, wherein , the synchronous reconfiguration is carried in an RRC reconfiguration message, and the at least one data bearer includes at least one DRB and/or at least one MRB.
  • the terminal device can trigger an RRC connection re-establishment process
  • the at least one data bearer includes at least one DRB and/or at least one MRB.
  • the terminal device if the terminal device is configured with MRB and not configured with DRB, the terminal device cannot receive synchronous reconfiguration, wherein the synchronous reconfiguration is carried in the RRC reconfiguration message .
  • the terminal device if the terminal device is configured with MRB and not configured with DRB, the terminal device cannot trigger the RRC connection re-establishment process.
  • the device further includes:
  • a state control unit configured to control the terminal device to enter the RRC idle state if a failure event occurs.
  • the failure event includes at least one of the following:
  • Radio link failure RRC reconfiguration failure, integrity protection verification failure.
  • the SRB2 is also released; or,
  • the RRC connection is also released.
  • the MRB is a bearer for the terminal equipment to receive a multicast service.
  • FIG. 5 is a schematic structural diagram 2 of a bearer configuration apparatus provided by an embodiment of the present application, which is applied to a network device.
  • the bearer configuration apparatus includes:
  • a sending unit 501 configured to send a bearer configuration instruction to a terminal device, where the bearer configuration instruction is used to configure SRB2 and at least one data bearer for the terminal device, wherein the at least one data bearer includes at least one DRB and/or at least one data bearer an MRB.
  • the bearer configuration instruction is RRC dedicated signaling.
  • the SRB2 is also released; or,
  • the RRC connection is also released.
  • the MRB is a bearer for the terminal equipment to receive a multicast service.
  • FIG. 6 is a schematic structural diagram of a communication device 600 provided by an embodiment of the present application.
  • the communication device may be a terminal device or a network device.
  • the communication device 600 shown in FIG. 6 includes a processor 610, and the processor 610 can call and run a computer program from a memory to implement the methods in the embodiments of the present application.
  • the communication device 600 may further include a memory 620 .
  • the processor 610 may call and run a computer program from the memory 620 to implement the methods in the embodiments of the present application.
  • the memory 620 may be a separate device independent of the processor 610 , or may be integrated in the processor 610 .
  • the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, may send information or data to other devices, or receive other devices Information or data sent by the device.
  • the transceiver 630 may include a transmitter and a receiver.
  • the transceiver 630 may further include antennas, and the number of the antennas may be one or more.
  • the communication device 600 may specifically be the network device in this embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method in the embodiment of the present application. For the sake of brevity, details are not repeated here. .
  • the communication device 600 may specifically be the mobile terminal/terminal device of the embodiments of the present application, and the communication device 600 may implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, for the sake of brevity. , and will not be repeated here.
  • FIG. 7 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • the chip 700 shown in FIG. 7 includes a processor 710, and the processor 710 can call and run a computer program from a memory, so as to implement the method in this embodiment of the present application.
  • the chip 700 may further include a memory 720 .
  • the processor 710 may call and run a computer program from the memory 720 to implement the methods in the embodiments of the present application.
  • the memory 720 may be a separate device independent of the processor 710 , or may be integrated in the processor 710 .
  • the chip 700 may further include an input interface 730 .
  • the processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may acquire information or data sent by other devices or chips.
  • the chip 700 may further include an output interface 740 .
  • the processor 710 can control the output interface 740 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
  • the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which is not repeated here for brevity.
  • the chip can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application.
  • the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application.
  • the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application.
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.
  • FIG. 8 is a schematic block diagram of a communication system 800 provided by an embodiment of the present application. As shown in FIG. 8 , the communication system 800 includes a terminal device 810 and a network device 820 .
  • the terminal device 810 can be used to implement the corresponding functions implemented by the terminal device in the above method
  • the network device 820 can be used to implement the corresponding functions implemented by the network device in the above method. For brevity, details are not repeated here. .
  • the processor in this embodiment of the present application may be an integrated circuit chip, which has a signal processing capability.
  • each step of the above method embodiments may be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software.
  • the above-mentioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other available Programming logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.
  • the memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically programmable read-only memory (Erasable PROM, EPROM). Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be Random Access Memory (RAM), which acts as an external cache.
  • RAM Static RAM
  • DRAM Dynamic RAM
  • SDRAM Synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • enhanced SDRAM ESDRAM
  • synchronous link dynamic random access memory Synchlink DRAM, SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.
  • Embodiments of the present application further provide a computer-readable storage medium for storing a computer program.
  • the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application.
  • the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application.
  • the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application. , for brevity, will not be repeated here.
  • Embodiments of the present application also provide a computer program product, including computer program instructions.
  • the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. Repeat.
  • the computer program product can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiments of the present application, For brevity, details are not repeated here.
  • the embodiments of the present application also provide a computer program.
  • the computer program can be applied to the network device in the embodiments of the present application.
  • the computer program When the computer program is run on the computer, it causes the computer to execute the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity. , and will not be repeated here.
  • the computer program may be applied to the mobile terminal/terminal device in the embodiments of the present application, and when the computer program is run on the computer, the mobile terminal/terminal device implements the various methods of the computer program in the embodiments of the present application.
  • the corresponding process for the sake of brevity, will not be repeated here.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .

Landscapes

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

Abstract

本申请实施例提供一种承载配置方法及装置、终端设备、网络设备，该方法包括：终端设备接收网络设备发送的承载配置指令，所述承载配置指令用于为所述终端设备配置SRB2和至少一个数据承载，其中，所述至少一个数据承载包括至少一个DRB和/或至少一个MRB。

Description

一种承载配置方法及装置、终端设备、网络设备 技术领域
本申请实施例涉及移动通信技术领域，具体涉及一种承载配置方法及装置、终端设备、网络设备。
背景技术
终端设备接收单播业务需要进入无线资源控制(Radio Resource Control，RRC)连接状态，终端设备在RRC连接状态下并且存在用于单播业务接收的承载时，才支持RRC连接状态下的移动性过程。
随着多媒体广播服务(Multimedia Broadcast Service，MBS)业务的引入，终端设备接收组播方式的MBS业务也需要进入RRC连接状态。此时，如何支持RRC连接状态下的移动性需要明确。
发明内容
本申请实施例提供一种承载配置方法及装置、终端设备、网络设备。
本申请实施例提供的承载配置方法，包括：
终端设备接收网络设备发送的承载配置指令，所述承载配置指令用于为所述终端设备配置信令无线承载(Signalling Radio Bearer，SRB)2和至少一个数据承载，其中，所述至少一个数据承载包括至少一个数据无线承载(Data Radio Bearer，DRB)和/或至少一个多播无线承载(Multicast Radio Bearer，MRB)。
本申请实施例提供的承载配置方法，包括：
网络设备向终端设备发送承载配置指令，所述承载配置指令用于为所述终端设备配置SRB2和至少一个数据承载，其中，所述至少一个数据承载包括至少一个DRB和/或至少一个MRB。
本申请实施例提供的承载配置装置，应用于终端设备，所述装置包括：
接收单元，用于接收网络设备发送的承载配置指令，所述承载配置指令用于为所述终端设备配置SRB2和至少一个数据承载，其中，所述至少一个数据承载包括至少一个DRB和/或至少一个MRB。
本申请实施例提供的承载配置装置，应用于网络设备，所述装置包括：
发送单元，用于向终端设备发送承载配置指令，所述承载配置指令 用于为所述终端设备配置SRB2和至少一个数据承载，其中，所述至少一个数据承载包括至少一个DRB和/或至少一个MRB。
本申请实施例提供的终端设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述的承载配置方法。
本申请实施例提供的网络设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述的承载配置方法。
本申请实施例提供的芯片，用于实现上述的承载配置方法。
具体地，该芯片包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片的设备执行上述的承载配置方法。
本申请实施例提供的计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述的承载配置方法。
本申请实施例提供的计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行上述的承载配置方法。
本申请实施例提供的计算机程序，当其在计算机上运行时，使得计算机执行上述的承载配置方法。
通过上述技术方案，网络设备为终端设备配置SRB2和至少一个数据承载，其中，所述至少一个数据承载包括至少一个DRB和/或至少一个MRB，从而终端设备可以基于SRB2和至少一个数据承载支持RRC连接状态下的移动性过程。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1是本申请实施例提供的一种通信系统架构的示意性图；
图2是本申请实施例提供的MBS业务的传输网络架构图；
图3是本申请实施例提供的承载配置方法的流程示意图；
图4是本申请实施例提供的承载配置装置的结构组成示意图一；
图5是本申请实施例提供的承载配置装置的结构组成示意图二；
图6是本申请实施例提供的一种通信设备示意性结构图；
图7是本申请实施例的芯片的示意性结构图；
图8是本申请实施例提供的一种通信系统的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进 行描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请实施例的技术方案可以应用于各种通信系统，例如：长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)、系统、5G通信系统或未来的通信系统等。
示例性的，本申请实施例应用的通信系统100如图1所示。该通信系统100可以包括网络设备110，网络设备110可以是与终端120(或称为通信终端、终端)通信的设备。网络设备110可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端进行通信。可选地，该网络设备110可以是LTE系统中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该网络设备可以为移动交换中心、中继站、接入点、车载设备、可穿戴设备、集线器、交换机、网桥、路由器、5G网络中的网络侧设备或者未来通信系统中的网络设备等。
该通信系统100还包括位于网络设备110覆盖范围内的至少一个终端120。作为在此使用的“终端”包括但不限于经由有线线路连接，如经由公共交换电话网络(Public Switched Telephone Networks，PSTN)、数字用户线路(Digital Subscriber Line，DSL)、数字电缆、直接电缆连接；和/或另一数据连接/网络；和/或经由无线接口，如，针对蜂窝网络、无线局域网(Wireless Local Area Network，WLAN)、诸如DVB-H网络的数字电视网络、卫星网络、AM-FM广播发送器；和/或另一终端的被设置成接收/发送通信信号的装置；和/或物联网(Internet of Things，IoT)设备。被设置成通过无线接口通信的终端可以被称为“无线通信终端”、“无线终端”或“移动终端”。移动终端的示例包括但不限于卫星或蜂窝电话；可以组合蜂窝无线电电话与数据处理、传真以及数据通信能力的个人通信系统(Personal Communications System，PCS)终端；可以包括无线电电话、寻呼机、因特网/内联网接入、Web浏览器、记事簿、日历以及/或全球定位系统(Global Positioning System，GPS)接收器的PDA；以及常规膝上型和/或掌上型接收器或包括无线电电话收发器的其它电子装置。终端可以指接入终端、用户设备(User Equipment，UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、5G网络中的终端或者未来演进的PLMN中的终端等。
可选地，终端120之间可以进行终端直连(Device to Device，D2D)通信。
可选地，5G通信系统或5G网络还可以称为新无线(New Radio，NR)系统或NR网络。
图1示例性地示出了一个网络设备和两个终端，可选地，该通信系统100可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端，本申请实施例对此不做限定。
可选地，该通信系统100还可以包括网络控制器、移动管理实体等其他网络实体，本申请实施例对此不作限定。
应理解，本申请实施例中网络/系统中具有通信功能的设备可称为通信设备。以图1示出的通信系统100为例，通信设备可包括具有通信功能的网络设备110和终端120，网络设备110和终端120可以为上文所述的具体设备，此处不再赘述；通信设备还可包括通信系统100中的其他设备，例如网络控制器、移动管理实体等其他网络实体，本申请实施例中对此不做限定。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
为便于理解本申请实施例的技术方案，以下对本申请实施例相关的技术方案进行说明。
随着人们对速率、延迟、高速移动性、能效的追求以及未来生活中业务的多样性、复杂性，为此第三代合作伙伴计划(3 rd Generation Partnership Project，3GPP)国际标准组织开始研发5G。5G的主要应用场景为：增强移动超宽带(enhanced Mobile Broadband，eMBB)、低时延高可靠通信(Ultra-Reliable Low-Latency Communications，URLLC)、大规模机器类通信(massive Machine-Type Communications，mMTC)。
一方面，eMBB仍然以用户获得多媒体内容、服务和数据为目标，其需求增长十分迅速。另一方面，由于eMBB可能部署在不同的场景中，例如室内，市区，农村等，其能力和需求的差别也比较大，所以不能一概而论，必须结合具体的部署场景详细分析。URLLC的典型应用包括：工业自动化，电力自动化，远程医疗操作(手术)，交通安全保障等。mMTC的典型特点包括：高连接密度，小数据量，时延不敏感业务，模块的低成本和长使用寿命等。
在NR早期部署时，完整的NR覆盖很难获取，所以典型的网络覆盖是广域的LTE覆盖和NR的孤岛覆盖模式。而且大量的LTE部署在6GHz以下，可用于5G的6GHz以下频谱很少。所以NR必须研究6GHz以上的频 谱应用，而高频段覆盖有限、信号衰落快。同时为了保护移动运营商前期在LTE投资，提出了LTE和NR之间紧耦合(tight interworking)的工作模式。
Figure PCTCN2021091695-appb-000001
RRC状态
5G为了降低空口信令和快速恢复无线连接，快速恢复数据业务的目的，定义了一个新的无线资源控制(Radio Resource Control，RRC)状态，即RRC非激活(RRC_INACTIVE)状态。这种状态有别于RRC空闲(RRC_IDLE)状态和RRC激活(RRC_ACTIVE)状态。其中，
1)RRC_IDLE状态(简称为空闲(idle)态)：移动性为基于终端设备的小区选择重选，寻呼由核心网(Core Network，CN)发起，寻呼区域由CN配置。基站侧不存在终端设备上下文，不存在RRC连接。
2)RRC_CONNECTED状态(简称为连接(connected)态)：存在RRC连接，基站侧和终端设备侧存在终端设备上下文。网络侧知道终端设备的位置是具体小区级别的。移动性是网络侧控制的移动性。终端设备和基站之间可以传输单播数据。
3)RRC_INACTIVE状态(简称为非激活(inactive)态)：移动性为基于终端设备的小区选择重选，存在CN-NR之间的连接，终端设备上下文存在某个基站上，寻呼由RAN触发，基于RAN的寻呼区域由RAN管理，网络侧知道终端设备的位置是基于RAN的寻呼区域级别的。
Figure PCTCN2021091695-appb-000002
MBMS
MBMS是一种通过共享网络资源从一个数据源向多个终端设备传送数据的技术，该技术在提供多媒体业务的同时能有效地利用网络资源，实现较高速率(如256kbps)的多媒体业务的广播和组播。
由于MBMS频谱效率较低，不足以有效地承载和支撑手机电视类型业务的运营。因此在LTE中，3GPP明确提出增强对下行高速MBMS业务的支持能力，并确定了对物理层和空中接口的设计要求。
3GPP R9将演进的MBMS(evolved MBMS，eMBMS)引入到LTE中。eMBMS提出了单频率网络(Single Frequency Network，SFN)的概念，即多媒体广播多播服务单频率网络(Multimedia Broadcast multicast service Single Frequency Network，MBSFN)，MBSFN采用统一频率在所有小区同时发送业务数据，但是要保证小区间的同步。这种方式可以极大的提高小区整体信噪比分布，频谱效率也会相应的大幅提高。eMBMS基于IP多播协议实现业务的广播和多播。
在LTE或增强的LTE(LTE-Advanced，LTE-A)中，MBMS只有广播承载模式，没有多播承载模式。此外，MBMS业务的接收适用于空闲态或者连接态的终端设备。
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”方式。空闲态的终端设备的业务连续性基于频率优先级的概念。
需要说明的是，虽然上述方案是以MBMS为例进行说明的，但“MBMS”的描述也可以替换为“MBS”。本申请实施例以MBS为例进行说明，“MBS业务”的描述也可以被替换为“MBMS”。
在NR系统中，很多场景需要支持组播类型和广播类型的业务需求，例如车联网中，工业互联网中等。所以在NR中引入组播类型和广播类型的MBS业务是有必要的。需要说明的是，组播类型的MBS业务是指通过组播方式传输的MBS业务。广播类型的MBS业务是指通过广播方式传输的MBS业务。
在NR系统中，对于组播类型的MBS业务来说，MBS业务是发给某个组中的所有终端设备。终端设备在RRC连接状态下接收组播类型的MBS业务，终端设备可以通过点对多点(Point To Multipoint，PTM)方式或者点对点(Point To Point，PTP)方式接收组播类型的MBS业务数据。其中，PTM方式的MBS业务数据通过网络侧配置的G-RNTI来加扰对应的调度信息，PTP方式的MBS业务数据通过C-RNTI来加扰对应的调度信息。
MSB业务通过组播方式传输，换句话说，MSB业务为组播类型的MBS业务。具体地，基站从共享隧道(tunnel)接收核心网下发的MBS业务后，可以将该MSB业务通过空口下发给一个组中的所有终端设备。这里，基站可以通过PTP方式和/或PTM方式将MSB业务下发给一个组中的所有终端设备。例如：一个组包括终端设备1、终端设备2和终端设备3，基站可以通过PTP方式将MBS业务下发给终端设备1，通过PTP方式将MBS业务下发给终端设备2，通过PTP方式将MBS业务下发给终端设备3；或者，基站可以通过PTP方式将MBS业务下发给终端设备1，通过PTM方式将MBS业务下发给终端设备2和终端设备3；或者，基站可以通过PTM方式将MBS业务下发给终端设备1，终端设备2以及终端设备3。参照图2，在核心网到基站之间采用一个共享的GTP隧道(Shared GTP tunnel)来传输MBS业务，即无论是PTM方式的MBS业务还是PTP方式的MBS业务都是共享这个GTP隧道的。基站按照PTM方式下发MBS业务数据给UE1和UE2，以及按照PTP方式下发MBS业务数据给UE3。
对于接收MBS业务的终端设备来说，同时还会接收其他非MBS业务，例如eMBB业务。所以当没有MBS业务传输的时候，终端设备可以被网络侧释放到空闲态或者非激活态或者保持在连接态。在终端设备处于空闲态或者非激活态的情况下，当MBS业务的数据到达时，网络侧可以通过寻呼来唤醒终端设备来接收MBS业务。
当终端设备处于RRC连接状态，并存在用于接收单播业务的承载时，终端设备支持在RRC连接状态下移动性过程，例如切换过程、RRC连接重建过程、终端设备上下文索要过程。随着MBS业务的引入，终端设备接收业务需要进入RRC连接状态，存在只接收MBS业务但是没有接收单播业务的场景，也存在只接收单播业务但是没有接收MBS业务的场景，也存在同时接收MBS业务和单播业务的场景。此时，如何支持终端设备的移动性需要明确。
为此，提出了本申请实施例的以下技术方案。
图3是本申请实施例提供的承载配置方法的流程示意图，如图3所示，所述承载配置方法包括以下步骤：
步骤301：网络设备向终端设备发送承载配置指令，终端设备接收网络设备发送的承载配置指令，所述承载配置指令用于为所述终端设备配置信令SRB2和至少一个数据承载，其中，所述至少一个数据承载包括至少一个DRB和/或至少一个MRB。
在本申请一些可选实施方式中，所述网络设备可以是基站。
本申请实施例中，无线承载(Radio Bearer，RB)的类型可以分为：SRB、DRB、MRB。其中，SRB属于信令承载，DRB和MRB属于数据承载。进一步，所述DRB是终端设备接收单播业务的的承载。所述MRB为所述终端设备接收组播业务的承载，这里，组播业务是指组播方式的MBS业务。以下对SRB进行说明。
SRB用于传输信令。SRB0是缺省承载，终端设备在RRC空闲状态或者RRC非激活状态时该承载已经存在。RRC实体是管理承载的实体，通过RRC信令的交互完成承载的建立、修改以及释放等功能。因为SRB0是不需要建立的，终端设备在RRC空闲状态或者RRC非激活状态就可以获得SRB0的配置和资源，如果需要可以直接使用。通过SRB0上传输信令可以建立SRB1，SRB1建立之后，终端设备就进入RRC连接状态，进而通过SRB1传输信令以建立SRB2，SRB2用来传输非接入层(NAS)信令；利用SRB1传输信令也可以建立数据承载，数据承载用来传输业务数据。在业务过程中，通过SRB1对承载进行管理，当业务结束后，SRB1上传输的信令可以将所有的数据承载和信令承载释放，使得终端设备进入到RRC空闲状态。，在需要时UE唯一可以使用的资源就是SRB0，而且需要在完成随机接入之后进行。
RRC建立(RRC Setup)消息用于建立SRB1，承载在SRB0中。
RRC重配置(RRCReconfiguration)消息用于修改RRC连接，承载在SRB1中。
需要说明的是，接入层(AS)安全激活后，才会发起SRB2和数据承载的建立。对于SRB2和DRB，E-UTRAN不会在激活安全之前建立这些承载。
本申请实施例中，网络设备为终端设备配置承载时，在一定的配置约束下进行承载的配置，这里，配置约束为：SRB2和数据承载必须同时配置化。网络设备不能配置只有一个SRB2或者只有至少一个数据承载。
基于此配置约束，网络设备向终端设备发送的承载配置指令用于为所述终端设备配置SRB2和至少一个数据承载，其中，所述至少一个数据承载包括至少一个DRB和/或至少一个MRB。这里，终端设备为处于RRC连接状态的终端设备，也即SRB1已经建立了。
上述方案中，所述承载配置指令为RRC专用信令。所述承载配置指令承载在SRB1中。
本申请实施例中，由于上述配置约束的存在，网络设备在释放承载时，相应地也需要遵循该配置约束，基于此配置约束，若全部的所述至少一个数据承载被释放，则所述SRB2也被释放；或者，若所述SRB2被释放，则全部的所述至少一个数据承载也被释放。可选地，进一步，若所述SRB2和全部的所述至少一个数据承载被释放，则RRC连接也被释放。
举个例子：网络设备在释放数据承载时，如果终端设备所有的数据承载(如MRB和DRB)都被释放，则SRB2也需要被释放。进一步，终端设备的RRC连接也需要被释放(即SRB1被释放)。
本申请实施例中，终端设备被配置上述承载后，支持以下多种场景下的移动性过程。
场景一：切换场景
所述终端设备在AS安全激活后且基于所述承载配置指令建立所述SRB2和所述至少一个数据承载后，所述终端设备能够接收同步重配置，其中，所述同步重配置携带在RRC重配置消息中，所述至少一个数据承载包括至少一个DRB和/或至少一个MRB。
这里，同步重配置称为“reconfigurationWithSync”，其中，reconfigurationWithSync包含在“masterCellGroup”配置中。
这里，masterCellGroup配置携带在RRC重配置(RRCReconfiguration)消息中。
需要说明的是，上述方案中，建立所述SRB2和所述至少一个数据承载后，还需要所述SRB2和所述至少一个数据承载不处于悬挂(suspended)状态，终端设备才能够接收同步重配置。
本申请实施例上述方案的含义也可以参照以下表1的内容。
Figure PCTCN2021091695-appb-000003
表1
场景二：RRC连接重建场景
所述终端设备在AS安全激活后且基于所述承载配置指令建立所述SRB2和所述至少一个数据承载后，所述终端设备能够触发RRC连接重建过程，所述至少一个数据承载包括至少一个DRB和/或至少一个MRB。
本申请实施例上述方案的含义也可以参照以下表2的内容。
Figure PCTCN2021091695-appb-000004
表2
在本申请一些可选实施方式中，以下场景下终端设备不支持移动性过程。
若所述终端设备被配置了MRB且未配置DRB，则所述终端设备不能够接收同步重配置，其中，所述同步重配置携带在RRC重配置消息中。若所述终端设备被配置了MRB且未配置DRB，则所述终端设备不能够触发RRC连接重建过程。
这里，当终端设备只配置了MRB没有配置DRB，无论此时AS安全是否激活，终端设备都不支持接收同步重配置和触发RRC连接重建过程。这里，同步重配置称为“reconfigurationWithSync”，其中，reconfigurationWithSync包含在“masterCellGroup”配置中。masterCellGroup配置携带在RRC重配置(RRCReconfiguration)消息中。
由于终端设备不支持上述移动性过程，因此若发生了失败事件，则所述终端设备直接进入RRC空闲状态。作为示例，所述失败事件包括以下至少之一：无线链路失败、RRC重配置失败、完整性保护验证失败。
本申请实施例的技术方案，在引入组播方式的MBS业务的时，给出了对于承载的配置约束以及终端设备的行为约束，使得MBS配置合理有效。
图4是本申请实施例提供的承载配置装置的结构组成示意图一，应用于终端设备，如图4所示，所述承载配置装置包括：
接收单元401，用于接收网络设备发送的承载配置指令，所述承载配置指令用于为所述终端设备配置SRB2和至少一个数据承载，其中，所述至少一个数据承载包括至少一个DRB和/或至少一个MRB。
在本申请一些可选实施方式中，所述承载配置指令为RRC专用信令。
在本申请一些可选实施方式中，所述终端设备在AS安全激活后且基于所述承载配置指令建立所述SRB2和所述至少一个数据承载后，所述终端设备能够接收同步重配置，其中，所述同步重配置携带在RRC重配置 消息中，所述至少一个数据承载包括至少一个DRB和/或至少一个MRB。
在本申请一些可选实施方式中，所述终端设备在AS安全激活后且基于所述承载配置指令建立所述SRB2和所述至少一个数据承载后，所述终端设备能够触发RRC连接重建过程，所述至少一个数据承载包括至少一个DRB和/或至少一个MRB。
在本申请一些可选实施方式中，若所述终端设备被配置了MRB且未配置DRB，则所述终端设备不能够接收同步重配置，其中，所述同步重配置携带在RRC重配置消息中。
在本申请一些可选实施方式中，若所述终端设备被配置了MRB且未配置DRB，则所述终端设备不能够触发RRC连接重建过程。
在本申请一些可选实施方式中，所述装置还包括：
状态控制单元，用于若发生了失败事件，则控制所述终端设备进入RRC空闲状态。
在本申请一些可选实施方式中，所述失败事件包括以下至少之一：
无线链路失败、RRC重配置失败、完整性保护验证失败。
在本申请一些可选实施方式中，若全部的所述至少一个数据承载被释放，则所述SRB2也被释放；或者，
若所述SRB2被释放，则全部的所述至少一个数据承载也被释放。
在本申请一些可选实施方式中，若所述SRB2和全部的所述至少一个数据承载被释放，则RRC连接也被释放。
在本申请一些可选实施方式中，所述MRB为所述终端设备接收组播业务的承载。
本领域技术人员应当理解，本申请实施例的上述承载配置装置的相关描述可以参照本申请实施例的承载配置方法的相关描述进行理解。
图5是本申请实施例提供的承载配置装置的结构组成示意图二，应用于网络设备，如图5所示，所述承载配置装置包括：
发送单元501，用于向终端设备发送承载配置指令，所述承载配置指令用于为所述终端设备配置SRB2和至少一个数据承载，其中，所述至少一个数据承载包括至少一个DRB和/或至少一个MRB。
在本申请一些可选实施方式中，所述承载配置指令为RRC专用信令。
在本申请一些可选实施方式中，若全部的所述至少一个数据承载被释放，则所述SRB2也被释放；或者，
若所述SRB2被释放，则全部的所述至少一个数据承载也被释放。
在本申请一些可选实施方式中，若所述SRB2和全部的所述至少一个数据承载被释放，则RRC连接也被释放。
在本申请一些可选实施方式中，所述MRB为所述终端设备接收组播业务的承载。
本领域技术人员应当理解，本申请实施例的上述承载配置装置的相关 描述可以参照本申请实施例的承载配置方法的相关描述进行理解。
图6是本申请实施例提供的一种通信设备600示意性结构图。该通信设备可以是终端设备，也可以是网络设备，图6所示的通信设备600包括处理器610，处理器610可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图6所示，通信设备600还可以包括存储器620。其中，处理器610可以从存储器620中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器620可以是独立于处理器610的一个单独的器件，也可以集成在处理器610中。
可选地，如图6所示，通信设备600还可以包括收发器630，处理器610可以控制该收发器630与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器630可以包括发射机和接收机。收发器630还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该通信设备600具体可为本申请实施例的网络设备，并且该通信设备600可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该通信设备600具体可为本申请实施例的移动终端/终端设备，并且该通信设备600可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
图7是本申请实施例的芯片的示意性结构图。图7所示的芯片700包括处理器710，处理器710可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图7所示，芯片700还可以包括存储器720。其中，处理器710可以从存储器720中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器720可以是独立于处理器710的一个单独的器件，也可以集成在处理器710中。
可选地，该芯片700还可以包括输入接口730。其中，处理器710可以控制该输入接口730与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
可选地，该芯片700还可以包括输出接口740。其中，处理器710可以控制该输出接口740与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该芯片可应用于本申请实施例中的网络设备，并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该芯片可应用于本申请实施例中的移动终端/终端设备，并且该芯片可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
图8是本申请实施例提供的一种通信系统800的示意性框图。如图8所示，该通信系统800包括终端设备810和网络设备820。
其中，该终端设备810可以用于实现上述方法中由终端设备实现的相应的功能，以及该网络设备820可以用于实现上述方法中由网络设备实现的相应的功能为了简洁，在此不再赘述。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(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 (42)

  1. 一种承载配置方法，所述方法包括：
    终端设备接收网络设备发送的承载配置指令，所述承载配置指令用于为所述终端设备配置信令无线承载SRB2和至少一个数据承载，其中，所述至少一个数据承载包括至少一个数据无线承载DRB和/或至少一个多播无线承载MRB。
  2. 根据权利要求1所述的方法，其中，所述承载配置指令为无线资源控制RRC专用信令。
  3. 根据权利要求1或2所述的方法，其中，所述方法还包括：
    所述终端设备在AS安全激活后且基于所述承载配置指令建立所述SRB2和所述至少一个数据承载后，所述终端设备能够接收同步重配置，其中，所述同步重配置携带在RRC重配置消息中，所述至少一个数据承载包括至少一个DRB和/或至少一个MRB。
  4. 根据权利要求1或2所述的方法，其中，所述方法还包括：
    所述终端设备在AS安全激活后且基于所述承载配置指令建立所述SRB2和所述至少一个数据承载后，所述终端设备能够触发RRC连接重建过程，所述至少一个数据承载包括至少一个DRB和/或至少一个MRB。
  5. 根据权利要求1或2所述的方法，其中，所述方法还包括：
    若所述终端设备被配置了MRB且未配置DRB，则所述终端设备不能够接收同步重配置，其中，所述同步重配置携带在RRC重配置消息中。
  6. 根据权利要求1或2所述的方法，其中，所述方法还包括：
    若所述终端设备被配置了MRB且未配置DRB，则所述终端设备不能够触发RRC连接重建过程。
  7. 根据权利要求6所述的方法，其中，所述方法还包括：
    若发生了失败事件，则所述终端设备进入RRC空闲状态。
  8. 根据权利要求7所述的方法，其中，所述失败事件包括以下至少之一：
    无线链路失败、RRC重配置失败、完整性保护验证失败。
  9. 根据权利要求1至8中任一项所述的方法，其中，
    若全部的所述至少一个数据承载被释放，则所述SRB2也被释放；或者，
    若所述SRB2被释放，则全部的所述至少一个数据承载也被释放。
  10. 根据权利要求9所述的方法，其中，若所述SRB2和全部的所述至少一个数据承载被释放，则RRC连接也被释放。
  11. 根据权利要求1至10中任一项所述的方法，其中，所述MRB为所述终端设备接收组播业务的承载。
  12. 一种承载配置方法，所述方法包括：
    网络设备向终端设备发送承载配置指令，所述承载配置指令用于为所述终端设备配置SRB2和至少一个数据承载，其中，所述至少一个数据承载包括至少一个DRB和/或至少一个MRB。
  13. 根据权利要求12所述的方法，其中，所述承载配置指令为RRC专用信令。
  14. 根据权利要求12或13所述的方法，其中，
    若全部的所述至少一个数据承载被释放，则所述SRB2也被释放；或者，
    若所述SRB2被释放，则全部的所述至少一个数据承载也被释放。
  15. 根据权利要求14所述的方法，其中，若所述SRB2和全部的所述至少一个数据承载被释放，则RRC连接也被释放。
  16. 根据权利要求12至15中任一项所述的方法，其中，所述MRB为所述终端设备接收组播业务的承载。
  17. 一种承载配置装置，应用于终端设备，所述装置包括：
    接收单元，用于接收网络设备发送的承载配置指令，所述承载配置指令用于为所述终端设备配置SRB2和至少一个数据承载，其中，所述至少一个数据承载包括至少一个DRB和/或至少一个MRB。
  18. 根据权利要求17所述的装置，其中，所述承载配置指令为RRC专用信令。
  19. 根据权利要求17或18所述的装置，其中，所述终端设备在AS安全激活后且基于所述承载配置指令建立所述SRB2和所述至少一个数据承载后，所述终端设备能够接收同步重配置，其中，所述同步重配置携带在RRC重配置消息中，所述至少一个数据承载包括至少一个DRB和/或至少一个MRB。
  20. 根据权利要求17或18所述的装置，其中，所述终端设备在AS安全激活后且基于所述承载配置指令建立所述SRB2和所述至少一个数据承载后，所述终端设备能够触发RRC连接重建过程，所述至少一个数据承载包括至少一个DRB和/或至少一个MRB。
  21. 根据权利要求17或18所述的装置，其中，若所述终端设备被配置了MRB且未配置DRB，则所述终端设备不能够接收同步重配置，其中，所述同步重配置携带在RRC重配置消息中。
  22. 根据权利要求17或18所述的装置，其中，若所述终端设备被配置了MRB且未配置DRB，则所述终端设备不能够触发RRC连接重建过程。
  23. 根据权利要求22所述的装置，其中，所述装置还包括：
    状态控制单元，用于若发生了失败事件，则控制所述终端设备进入RRC空闲状态。
  24. 根据权利要求23所述的装置，其中，所述失败事件包括以下至少之一：
    无线链路失败、RRC重配置失败、完整性保护验证失败。
  25. 根据权利要求17至24任一项所述的装置，其中，
    若全部的所述至少一个数据承载被释放，则所述SRB2也被释放；或者，
    若所述SRB2被释放，则全部的所述至少一个数据承载也被释放。
  26. 根据权利要求25所述的装置，其中，若所述SRB2和全部的所述至少一个数据承载被释放，则RRC连接也被释放。
  27. 根据权利要求17至26任一项所述的装置，其中，所述MRB为所述终端设备接收组播业务的承载。
  28. 一种承载配置装置，应用于网络设备，所述装置包括：
    发送单元，用于向终端设备发送承载配置指令，所述承载配置指令用于为所述终端设备配置SRB2和至少一个数据承载，其中，所述至少一个数据承载包括至少一个DRB和/或至少一个MRB。
  29. 根据权利要求28所述的装置，其中，所述承载配置指令为RRC专用信令。
  30. 根据权利要求28或29所述的装置，其中，
    若全部的所述至少一个数据承载被释放，则所述SRB2也被释放；或者，
    若所述SRB2被释放，则全部的所述至少一个数据承载也被释放。
  31. 根据权利要求30所述的装置，其中，若所述SRB2和全部的所述至少一个数据承载被释放，则RRC连接也被释放。
  32. 根据权利要求28至31中任一项所述的装置，其中，所述MRB为所述终端设备接收组播业务的承载。
  33. 一种终端设备，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求1至11中任一项所述的方法。
  34. 一种网络设备，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求12至16中任一项所述的方法。
  35. 一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至11中任一项所述的方法。
  36. 一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求12至16中任一项所述的方法。
  37. 一种计算机可读存储介质，用于存储计算机程序，所述计算机 程序使得计算机执行如权利要求1至11中任一项所述的方法。
  38. 一种计算机可读存储介质，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求12至16中任一项所述的方法。
  39. 一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1至11中任一项所述的方法。
  40. 一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求12至16中任一项所述的方法。
  41. 一种计算机程序，所述计算机程序使得计算机执行如权利要求1至11中任一项所述的方法。
  42. 一种计算机程序，所述计算机程序使得计算机执行如权利要求12至16中任一项所述的方法。
PCT/CN2021/091695 2021-04-30 2021-04-30 一种承载配置方法及装置、终端设备、网络设备 WO2022227071A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
CN202311408809.3A CN117221966A (zh) 2021-04-30 2021-04-30 一种承载配置方法及装置、终端设备、网络设备
PCT/CN2021/091695 WO2022227071A1 (zh) 2021-04-30 2021-04-30 一种承载配置方法及装置、终端设备、网络设备
CN202180082804.9A CN116602004A (zh) 2021-04-30 2021-04-30 一种承载配置方法及装置、终端设备、网络设备
EP21938545.7A EP4271040A4 (en) 2021-04-30 2021-04-30 CARRIER CONFIGURATION METHOD AND APPARATUS, TERMINAL DEVICE AND NETWORK DEVICE
US18/359,050 US20230370299A1 (en) 2021-04-30 2023-07-26 Bearer configuration method and apparatus, terminal device, and network device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/091695 WO2022227071A1 (zh) 2021-04-30 2021-04-30 一种承载配置方法及装置、终端设备、网络设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/359,050 Continuation US20230370299A1 (en) 2021-04-30 2023-07-26 Bearer configuration method and apparatus, terminal device, and network device

Publications (1)

Publication Number Publication Date
WO2022227071A1 true WO2022227071A1 (zh) 2022-11-03

Family

ID=83847576

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/091695 WO2022227071A1 (zh) 2021-04-30 2021-04-30 一种承载配置方法及装置、终端设备、网络设备

Country Status (4)

Country Link
US (1) US20230370299A1 (zh)
EP (1) EP4271040A4 (zh)
CN (2) CN116602004A (zh)
WO (1) WO2022227071A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111200852A (zh) * 2018-11-20 2020-05-26 中兴通讯股份有限公司 一种语音呼叫方法、设备和存储介质
US10728812B2 (en) * 2016-08-11 2020-07-28 Lg Electronics Inc. Method and apparatus for supporting MBMS service continuity
CN111866751A (zh) * 2020-04-15 2020-10-30 中兴通讯股份有限公司 多播广播信息的传输方法、装置、存储介质及电子装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3869859B1 (en) * 2018-10-23 2022-09-07 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method and device for controlling mobility of terminal, and terminal
KR20210118610A (ko) * 2020-03-23 2021-10-01 삼성전자주식회사 무선 통신 시스템에서 방송 서비스의 연속성을 지원하는 방법 및 장치
EP4260622A1 (en) * 2020-12-08 2023-10-18 Toyota Jidosha Kabushiki Kaisha Targeted multicast broadcast services (mbs) notification signaling

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10728812B2 (en) * 2016-08-11 2020-07-28 Lg Electronics Inc. Method and apparatus for supporting MBMS service continuity
CN111200852A (zh) * 2018-11-20 2020-05-26 中兴通讯股份有限公司 一种语音呼叫方法、设备和存储介质
CN111866751A (zh) * 2020-04-15 2020-10-30 中兴通讯股份有限公司 多播广播信息的传输方法、装置、存储介质及电子装置

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
EP4271040A1 (en) 2023-11-01
CN117221966A (zh) 2023-12-12
EP4271040A4 (en) 2024-04-03
CN116602004A (zh) 2023-08-15
US20230370299A1 (en) 2023-11-16

Similar Documents

Publication Publication Date Title
WO2021134316A1 (zh) 一种业务调度方法及装置、终端设备、网络设备
WO2022056806A1 (zh) 一种mbs业务的管理方法及装置、终端设备、网络设备
WO2021051320A1 (zh) 一种业务数据传输方法及装置、网络设备、终端设备
WO2022006875A1 (zh) 建立mbs业务的方法及装置、终端设备、网络设备
WO2022006849A1 (zh) Mbs业务的tci状态管理方法及装置、终端设备
US20230361923A1 (en) Mbs service configuration method and terminal device
WO2022120837A1 (zh) Mbs业务的半静态调度方法及装置、终端设备、网络设备
WO2022141545A1 (zh) 一种mcch调度传输方法及装置、终端设备
WO2022141255A1 (zh) 一种mbs业务的配置方法及装置、网络设备、终端设备
WO2022141088A1 (zh) 一种mbs业务的传输方法及装置、终端设备
WO2022227071A1 (zh) 一种承载配置方法及装置、终端设备、网络设备
WO2021051321A1 (zh) 一种业务数据传输方法及装置、终端设备
WO2022165720A1 (zh) 提高mbs业务可靠性的方法及装置、终端设备、网络设备
WO2022226937A1 (zh) 一种mbs寻呼方法及装置、网络设备、终端设备
WO2022056669A1 (zh) 一种mbs业务的管理方法及装置、终端设备、网络设备
WO2022205454A1 (zh) 一种指示寻呼的方法及装置、终端设备、网络设备
WO2022006882A1 (zh) Mbs业务的传输方法及装置、网络设备、终端设备
WO2022198415A1 (zh) 提高mbs业务可靠性的方法及装置、终端设备、网络设备
WO2022126658A1 (zh) 一种mbs配置变更的方法及装置、终端设备、网络设备
WO2022133877A1 (zh) 一种mbs业务的指示方法及装置、终端设备、网络设备
WO2022056859A1 (zh) Mbs业务传输进度的控制方法及装置、通信设备
WO2022120749A1 (zh) 一种多播业务的调度方法及装置、终端设备、网络设备
WO2022006888A1 (zh) 一种mbs业务的接收方法及装置、终端设备
WO2023050185A1 (zh) 一种变量的维护方法及装置、终端设备
WO2022021024A1 (zh) 一种bwp切换的方法及装置、终端设备

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202180082804.9

Country of ref document: CN

ENP Entry into the national phase

Ref document number: 2021938545

Country of ref document: EP

Effective date: 20230726

NENP Non-entry into the national phase

Ref country code: DE