WO2021189933A1 - 一种配置无线承载的方法、装置及系统 - Google Patents

一种配置无线承载的方法、装置及系统 Download PDF

Info

Publication number
WO2021189933A1
WO2021189933A1 PCT/CN2020/133362 CN2020133362W WO2021189933A1 WO 2021189933 A1 WO2021189933 A1 WO 2021189933A1 CN 2020133362 W CN2020133362 W CN 2020133362W WO 2021189933 A1 WO2021189933 A1 WO 2021189933A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
broadcast service
terminal
radio bearer
data
Prior art date
Application number
PCT/CN2020/133362
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 EP20927148.5A priority Critical patent/EP4114127A4/en
Publication of WO2021189933A1 publication Critical patent/WO2021189933A1/zh
Priority to US17/952,596 priority patent/US20230013500A1/en

Links

Images

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H04W28/0263—Traffic management, e.g. flow control or congestion control per individual bearer or channel involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]
    • 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
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • 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

Definitions

  • the embodiments of the present application relate to the field of communication technologies, and in particular, to a method, device, and system for configuring a radio bearer.
  • the base station may send a multicast service (Multicast Service) to the terminal in the manner of unicast transmission (that is, point to point) or multicast transmission (that is, point to multipoint).
  • Multicast Service multicast service
  • the base station when a base station sends data for a multicast service to multiple terminals, and some of the multiple terminals use unicast transmission, and another part of the terminals use multicast transmission, for the terminals that use unicast transmission, the base station generates data for unicast transmission.
  • the base station For the terminal using multicast transmission, the base station generates the data of the multicast service for multicast transmission. That is, for the same data of the multicast service, the base station needs to generate different types of data for terminals that support different transmission modes, which will increase the data complexity of the base station in processing the multicast service.
  • the embodiments of the present application provide a method, device, and system for configuring a radio bearer.
  • a multicast radio bearer By establishing a multicast radio bearer between a terminal and a base station for receiving multicast/broadcast services, the data complexity of the base station for processing multicast services can be reduced. .
  • an embodiment of the present application provides a method for configuring a radio bearer.
  • the method includes: a base station receiving a first request message for requesting that a first terminal join a multicast/broadcast service.
  • the base station sends the configuration information of the multicast radio bearer to the first terminal according to the quality of service QoS flow information of the multicast/broadcast service.
  • the configuration information is used to configure the multicast radio bearer, and the multicast radio bearer is used to transmit data of the multicast/broadcast service to the terminals that have joined the multicast/broadcast service.
  • the terminals that have joined the multicast/broadcast service include the first terminal.
  • the embodiment of the present application provides a method for configuring a radio bearer.
  • the base station receives the first request message for requesting the first terminal to join the multicast/broadcast service according to the quality of service of the multicast/broadcast service.
  • the QoS flow information configures the configuration information of the multicast radio bearer for the first terminal. In this way, it is convenient for the first terminal to establish a multicast radio bearer for transmitting multicast/broadcast services between the first terminal and the base station. Subsequently, when the base station sends the multicast/broadcast service data to the first terminal, the base station can use the multicast radio bearer to send the multicast/broadcast service data to the first terminal.
  • the base station can use the multicast radio bearer to send the multicast/broadcast
  • the data of the service can therefore simplify the data complexity of the base station to process the multicast service.
  • flexible switching of the base station from unicast transmission to multicast transmission can also be realized.
  • the method provided in the embodiment of the present application includes: the base station receives a second request message for requesting the second terminal to join the multicast/broadcast service.
  • the base station sends configuration information to the second terminal.
  • the terminals that have joined the multicast/broadcast service also include a second terminal.
  • the configuration information of the multicast radio bearer includes the first indication information.
  • the first indication information is used to indicate that the type of the radio bearer configured by the configuration information is a multicast radio bearer, or the first indication information is used to indicate that the type of the multicast radio bearer configured by the configuration information is a multicast type. This facilitates the first terminal to determine the type of the multicast radio bearer.
  • the configuration information of the multicast radio bearer further includes: the identifier of the multicast/broadcast service, or the identifier of the multicast session associated with the multicast/broadcast service. In this way, it is convenient for the first terminal to determine that the multicast radio bearer is associated with the multicast/broadcast service or the multicast session associated with the multicast/broadcast service.
  • the multicast radio bearer in the embodiment of the present application is used to transmit the data of the multicast/broadcast service.
  • the configuration information of the multicast radio bearer in the embodiment of the present application includes one or more of the following: an identifier of the multicast radio bearer, and an identifier of the first logical channel to which the multicast radio bearer is mapped.
  • the method provided in the embodiment of the present application further includes: the base station determines not to perform security protection on the data of the multicast/broadcast service.
  • the configuration information of the multicast radio bearer includes second indication information, and the second indication information is used to indicate that security protection is not performed on the data of the multicast/broadcast service transmitted on the multicast radio bearer.
  • the base station determines not to perform security protection on the data of the multicast/broadcast service, including: the base station receives from the core network element for indicating that the data of the multicast/broadcast service is not to be secured Third instruction information for protection. According to the third indication information, the base station determines not to perform security protection on the data of the multicast/broadcast service. In this way, it is convenient for the base station not to perform a security protection operation on the data of the multicast/broadcast service according to the third indication information.
  • the method provided in the embodiment of the present application further includes: the base station determines to perform security protection on the data of the multicast/broadcast service.
  • the configuration information of the multicast radio bearer further includes fourth indication information, which is used to indicate that the data of the multicast/broadcast service transmitted on the multicast radio bearer has performed security protection. Through the fourth indication information, it is convenient for the first terminal to determine that the data of the multicast/broadcast service needs to perform decryption processing.
  • the base station determining that the data of the multicast/broadcast service performs security protection includes: the base station receives the first data from the core network element for instructing the security protection of the data of the multicast/broadcast service. Five instructions. The base station determines to perform security protection on the data of the multicast/broadcast service according to the fifth instruction information. In this way, it is convenient for the base station to perform complete protection of the data of the multicast/broadcast service transmitted on the multicast radio bearer, and improve the security of the data.
  • the method provided in the embodiment of the present application further includes: a base station receives a security parameter corresponding to the multicast/broadcast service from a core network element, where the security parameter includes a security key and/or security protection
  • the security algorithm used is used to securely protect the data of the multicast/broadcast service.
  • the base station obtains the data of the multicast/broadcast service after security protection according to the security parameters.
  • the base station sends the secured data of the multicast/broadcast service to the first terminal on the multicast radio bearer.
  • the method provided in the embodiment of the present application further includes: the base station sends a security parameter to the first terminal, and the security parameter is used by the first terminal to obtain the multicast/broadcast transmitted on the multicast radio bearer.
  • the base station sends a security parameter to the first terminal, and the security parameter is used by the first terminal to obtain the multicast/broadcast transmitted on the multicast radio bearer.
  • the method provided in the embodiment of the present application further includes: the base station sends configuration information of the first media access control MAC entity to the first terminal, and the configuration information of the first MAC entity is used to configure multicast /The first MAC entity corresponding to the broadcast service.
  • the base station sends configuration information of the first media access control MAC entity to the first terminal, and the configuration information of the first MAC entity is used to configure multicast /The first MAC entity corresponding to the broadcast service.
  • the configuration information of the first MAC entity includes sixth indication information, and the sixth indication information is used to indicate that the first MAC entity is used to transmit the data of the multicast/broadcast service. It is convenient for the first terminal to determine the role of the first MAC entity configured for the first terminal.
  • the configuration information of the first MAC entity includes the identifier of the multicast radio bearer. It is convenient to determine that the multicast radio bearer is associated with the first MAC entity.
  • the identifier of the first logical channel mapped by the multicast radio bearer is the same as the identifier of the second logical channel
  • the second logical channel is the logical channel associated with the radio bearer corresponding to the second MAC entity.
  • the second MAC entity is used to send data of other services except the data of the multicast service to the terminal. It should be understood that the second MAC entity is used to send data of services other than the foregoing multicast/broadcast service.
  • the configuration information of the first MAC entity further includes a first wireless network temporary identifier RNTI, and the first RNTI corresponds to the foregoing multicast/broadcast service or the first RNTI corresponds to the first terminal.
  • the first RNTI corresponds to the multicast/broadcast service.
  • PTM point-to-multipoint
  • the first RNTI corresponds to the first terminal.
  • the first MAC entity is shared by one or more terminals.
  • the first terminal when the foregoing first RNTI corresponds to the first terminal, it further includes: the first RNTI also corresponds to the multicast/broadcast service. In this way, the first terminal determines according to the first RNTI that what is received through the first MAC entity is the multicast/broadcast service data. It should be understood that the base station allocates the first RNTI to the multicast/broadcast service of the first terminal.
  • the method provided in the embodiment of the present application further includes: the base station receives a second request message for adding the second terminal to the multicast/broadcast service.
  • the wireless resource configuration information sent by the base station to the second terminal includes the configuration information of the multicast radio bearer and the configuration information of the third MAC entity, the configuration information of the third MAC entity includes sixth indication information, and the configuration information of the third MAC entity includes For the identifier of the multicast radio bearer, the third MAC entity is associated with the second RNTI, and the second RNTI corresponds to the multicast/broadcast service or corresponds to the second terminal.
  • the second RNTI corresponds to the foregoing multicast/broadcast service
  • the second RNTI is the same as the first RNTI.
  • the configuration information of the third MAC entity is the same as the configuration information of the first MAC entity.
  • an embodiment of the present application provides a method for configuring a radio bearer.
  • the method includes: a first terminal receives configuration information of a multicast radio bearer from a base station, and the configuration information of the multicast radio bearer is used to configure multicast/ The multicast radio bearer corresponding to the broadcast service.
  • the multicast radio bearer is used to transmit data of the multicast/broadcast service to the terminals that have joined the multicast/broadcast service, and the terminals that have joined the multicast/broadcast service include the first terminal.
  • the first terminal configures the multicast radio bearer according to the configuration information of the multicast radio bearer.
  • the method provided in the embodiment of the present application further includes: the first terminal receives the multicast/broadcast service data from the base station on the multicast radio bearer.
  • the configuration information of the multicast radio bearer includes one or more of the following: the identifier of the multicast radio bearer, or the identifier of the first logical channel to which the multicast radio bearer is mapped.
  • the configuration information of the multicast radio bearer includes first indication information, and the first indication information is used to indicate that the type of the radio bearer for which the configuration information is configured is a multicast radio bearer.
  • the first terminal determines that the type of the multicast radio bearer is the multicast type according to the first indication information.
  • the configuration information of the multicast radio bearer further includes: the identifier of the multicast/broadcast service, or the identifier of the multicast session associated with the multicast/broadcast service.
  • the configuration information of the multicast radio bearer includes second indication information used to indicate that the data of the multicast/broadcast service transmitted on the multicast radio bearer has not performed security protection.
  • the first terminal determines, according to the second indication information, that the data of the multicast/broadcast service transmitted on the multicast radio bearer has not performed security protection.
  • the first terminal receiving the multicast/broadcast service data from the base station on the multicast radio bearer includes: the first terminal receives the unexecuted security from the base station on the multicast radio bearer The protected data of the multicast/broadcast service.
  • the configuration information of the multicast radio bearer includes third indication information, and the third indication information is used to indicate that the data of the multicast/broadcast service transmitted on the multicast radio bearer has performed security protection .
  • the first terminal receiving the multicast/broadcast service data from the base station on the multicast radio bearer includes: the first terminal receives the security protection information from the base station when the multicast radio bearer is changed. The data of the multicast/broadcast service.
  • the method provided in the embodiment of the present application further includes: the first terminal receives a security parameter, and the security parameter is used by the first terminal to obtain the foregoing multicast/broadcast service data.
  • the first terminal receives security-protected multicast/broadcast service data on the multicast radio bearer.
  • the first terminal obtains the multicast/broadcast service data according to the security parameters and the security-protected multicast/broadcast service data.
  • the first terminal determines, according to the third indication information or security parameter, that the data of the multicast/broadcast service transmitted on the multicast radio bearer performs security protection.
  • the method provided in the embodiment of the present application further includes: the first terminal receives the configuration information of the first medium access control MAC entity from the base station, and the configuration information of the first MAC entity is used to configure the group The MAC entity corresponding to the broadcast/broadcast service.
  • the first terminal configures the first MAC entity corresponding to the multicast/broadcast service according to the configuration information of the first MAC entity.
  • the configuration information of the first MAC entity includes sixth indication information used to instruct the first MAC entity to transmit multicast/broadcast services.
  • the first terminal determines according to the sixth indication information that the first MAC entity is used to transmit data of the multicast/broadcast service.
  • the configuration information of the first MAC entity includes the first wireless network temporary identifier RNTI corresponding to the first MAC entity, and the first RNTI corresponds to the foregoing multicast/broadcast service or the first RNTI corresponds to the first RNTI. Terminal correspondence.
  • the method provided in the embodiment of the present application further includes: when the multicast/broadcast service is sent in a point-to-multipoint (PTM) manner, the first RNTI corresponds to the multicast/broadcast service. Or, when the multicast/broadcast service is sent in a point-to-point (PTP) manner, the first RNTI corresponds to the first terminal.
  • PTM point-to-multipoint
  • PTP point-to-point
  • the first MAC entity is shared by one or more terminals that join the multicast/broadcast service.
  • the first RNTI when the foregoing first RNTI corresponds to the first terminal, it further includes: the first RNTI also corresponds to the multicast/broadcast service. According to the first RNTI, the first terminal determines that what is received through the first MAC entity is the multicast/broadcast service data. It should be understood that the first RNTI is different from the RNTI used by the first terminal to receive unicast data, and is also different from the RNTI used by the first terminal to receive data of other multicast/broadcast services.
  • the configuration information of the first MAC entity includes the identifier of the foregoing multicast radio bearer.
  • the identifier of the first logical channel is the same as the identifier of the second logical channel
  • the second logical channel is the logical channel associated with the radio bearer corresponding to the second MAC entity
  • the second MAC entity is used for Send data to the terminal. It should be understood that the second MAC entity is used to send data of other services besides the foregoing multicast/broadcast service.
  • an embodiment of the present application provides a method for configuring wireless resources.
  • the method includes: a base station receiving a first request message for requesting a first terminal to join a multicast/broadcast service.
  • the base station sends the configuration information of the first media access control MAC entity to the first terminal according to the quality of service QoS flow information of the multicast/broadcast service.
  • the configuration information of the first MAC entity is used to configure the MAC entity corresponding to the multicast/broadcast service.
  • the first MAC entity is associated with the first wireless network temporary identifier RNTI, the first RNTI corresponds to a multicast/broadcast service or the first RNTI corresponds to the first terminal.
  • the first RNTI corresponds to the multicast/broadcast service.
  • PTM point-to-multipoint
  • the first RNTI corresponds to the first terminal.
  • the first MAC entity is shared by one or more terminals that join the multicast/broadcast service, and the one or more terminals include the first terminal.
  • the configuration information of the first MAC entity of the one or more terminals is the same.
  • the configuration information of the first MAC entity of the one or more terminals may be different, but the configuration information of the multicast radio bearer of the one or more terminals is the same.
  • the first RNTI when the foregoing first RNTI corresponds to the first terminal, it further includes: the first RNTI also corresponds to the multicast/broadcast service. It is convenient for the first terminal to determine, according to the first RNTI, that the data of the multicast/broadcast service is received through the first MAC entity. The base station allocates the first RNTI to the multicast/broadcast service of the first terminal. It should be understood that the first RNTI is different from the RNTI used by the first terminal to receive unicast data, and is also different from the RNTI used by the first terminal to receive data of other multicast/broadcast services.
  • the method provided in the embodiment of the present application further includes: the base station sends configuration information of the multicast radio bearer to the first terminal, and the configuration information of the multicast radio bearer is used to configure the multicast radio bearer.
  • the multicast radio bearer is used to transmit data of the multicast/broadcast service to the terminals that have joined the multicast/broadcast service, and the terminals that have joined the multicast/broadcast service include the first terminal.
  • the method provided in the embodiment of the present application further includes: the base station determines not to perform security protection on the data of the multicast/broadcast service.
  • the configuration information of the multicast radio bearer includes second indication information, and the second indication information is used to indicate that security protection is not performed on the data of the multicast/broadcast service transmitted on the multicast radio bearer.
  • the base station determines not to perform security protection on multicast/broadcast service data, including: the base station receives third indication information from a core network element, and the third indication information is used to indicate the multicast/broadcast service data / The data of the broadcast service does not perform security protection. According to the third indication information, the base station determines not to perform security protection on the data of the multicast/broadcast service.
  • the method provided in the embodiment of the present application further includes: the base station determines to perform security protection on the data of the foregoing multicast/broadcast service.
  • the configuration information of the multicast radio bearer further includes fourth indication information, which is used to indicate that the data of the multicast/broadcast service transmitted on the multicast radio bearer has performed security protection.
  • the base station determining that the data of the multicast/broadcast service performs security protection includes: the base station receives fifth indication information from the core network element, the fifth indication information is used to indicate the multicast/broadcast Business data execution security protection. The base station determines to perform security protection on the data of the multicast/broadcast service according to the fifth instruction information.
  • the method provided in the embodiment of the present application further includes: the base station receives a security parameter corresponding to a multicast/broadcast service from a core network element, the security parameter includes a security key, and/or, security protection
  • the security algorithm used is used to securely protect the data of the multicast/broadcast service.
  • the base station performs security protection on the data of the multicast/broadcast industry according to the security parameters, and obtains the data of the multicast/broadcast service after security protection.
  • the base station sends the secured multicast/broadcast service data to the first terminal on the multicast radio bearer.
  • the method provided in the embodiment of the present application further includes: the base station sends a security parameter to the first terminal, and the security parameter is used by the first terminal to obtain the multicast/broadcast service transmitted on the multicast radio bearer The data.
  • the method provided in the embodiment of the present application further includes: the base station determines to add the second terminal to the multicast/broadcast service.
  • the base station sends the configuration information of the multicast radio bearer and the configuration information of the third MAC entity to the second terminal.
  • the configuration information of the third MAC entity includes the identifier of the multicast radio bearer.
  • the third MAC entity is associated with the second RNTI.
  • the RNTI corresponds to the multicast/broadcast service or corresponds to the second terminal. It should be understood that when the second RNTI corresponds to the foregoing multicast/broadcast service, the second RNTI is the same as the first RNTI. At this time, the configuration information of the third MAC entity is the same as the configuration information of the first MAC entity.
  • the base station determining to add the second terminal to the multicast/broadcast service includes: the base station receives a second request message that requests the second terminal to join the multicast/broadcast service.
  • an embodiment of the present application provides a method for configuring wireless resources.
  • the method includes: a first terminal receives configuration information of a first medium access control MAC entity from a base station.
  • the configuration information of the first MAC entity is used to configure the MAC entity corresponding to the multicast/broadcast service.
  • the first terminal configures the first MAC entity according to the configuration information of the first MAC entity.
  • the first MAC entity is used to receive multicast/broadcast service data
  • the method provided in the embodiment of the present application further includes: the first terminal uses the first MAC entity to receive multicast/broadcast service data .
  • the first MAC entity is associated with the first wireless network temporary identifier RNTI, the first RNTI corresponds to a multicast/broadcast service or the first RNTI corresponds to the first terminal.
  • the first RNTI corresponds to the multicast/broadcast service.
  • PTM point-to-multipoint
  • the first RNTI corresponds to the first terminal.
  • the first MAC entity is shared by one or more terminals that join the multicast/broadcast service, and the one or more terminals include The first terminal.
  • the configuration information of the first MAC entity of the one or more terminals is the same.
  • the configuration information of the first MAC entity of the one or more terminals may be different, but the configuration information of the multicast radio bearer of the one or more terminals is the same.
  • the first RNTI when the foregoing first RNTI corresponds to the first terminal, it further includes: the first RNTI also corresponds to the multicast/broadcast service. It is convenient for the first terminal to determine, according to the first RNTI, that the data of the multicast/broadcast service is received through the first MAC entity. The base station allocates the first RNTI to the multicast/broadcast service of the first terminal. It should be understood that the first RNTI is different from the RNTI used by the first terminal to receive unicast data, and is also different from the RNTI used by the first terminal to receive data of other multicast/broadcast services.
  • the method provided in the embodiment of the present application further includes: the first terminal receives configuration information of the multicast radio bearer from the base station.
  • the configuration information of the multicast radio bearer is used to configure the multicast radio bearer.
  • the multicast radio bearer is used to transmit data of the multicast/broadcast service to the terminals that have joined the multicast/broadcast service, and the terminals that have joined the multicast/broadcast service include the first terminal.
  • the first terminal configures the multicast radio bearer for the first terminal according to the configuration information of the multicast radio bearer.
  • the first terminal receives multicast/broadcast service data from the base station through a multicast radio bearer.
  • the configuration information of the multicast radio bearer includes second indication information, and the second indication information is used to indicate that the data of the multicast/broadcast service transmitted on the multicast radio bearer does not perform security protection.
  • the first terminal determines, according to the second indication information, that the data of the multicast/broadcast service transmitted on the multicast radio bearer has not performed security protection.
  • the first terminal uses the multicast radio bearer and the first MAC entity to receive unsecured multicast/broadcast data.
  • the configuration information of the multicast radio bearer further includes fourth indication information used to indicate that the data of the multicast/broadcast service transmitted on the multicast radio bearer has performed security protection.
  • the first terminal uses the multicast radio bearer and the first MAC entity to receive securely protected multicast/broadcast data.
  • the first terminal receives security parameters, the security parameters include a security key, and/or a security algorithm used for security protection, and the security parameters are used to securely protect multicast/broadcast service data .
  • the first terminal obtains the multicast/broadcast service data according to the security parameters and the security-protected multicast/broadcast service data.
  • the first terminal determines, according to the third indication information or security parameter, that the data of the multicast/broadcast service transmitted on the multicast radio bearer has performed security protection.
  • an embodiment of the present application provides a communication device.
  • the communication device may be a base station or a component (for example, a chip) built in the base station.
  • the communication device may include a communication unit.
  • the communication device may also include a processing unit and a storage unit.
  • the communication unit may be a transceiver.
  • the storage unit may be a memory.
  • the storage unit is used to store instructions.
  • the processing unit may be a processor. The processing unit executes the instructions stored in the storage unit, so that the base station implements the method for configuring the radio bearer described in the first aspect or any one of the possible implementation manners of the first aspect.
  • the processing unit may be a processor, and the communication unit may be a communication interface.
  • the communication interface in the chip can be an input/output interface, a pin, or a circuit.
  • the processing unit executes the instructions stored in the storage unit, so that the communication device implements the wireless bearer configuration method described in the first aspect or any one of the possible implementations of the first aspect.
  • the storage unit may be the chip
  • the storage unit (for example, register, cache, etc.) in the base station may also be a storage unit (for example, read-only memory, random access memory, etc.) located outside the chip in the base station.
  • an embodiment of the present application provides a communication device.
  • the communication device may be a terminal or a component (for example, a chip) built in the terminal.
  • the communication device may include a communication unit.
  • the communication device may also include a processing unit and a storage unit.
  • the communication unit when the communication device is a terminal, the communication unit may be a transceiver.
  • the storage unit may be a memory.
  • the storage unit is used to store instructions.
  • the processing unit may be a processor. The processing unit executes the instructions stored in the storage unit, so that the terminal implements the method for configuring the radio bearer described in the second aspect or any one of the possible implementation manners of the second aspect.
  • the processing unit may be a processor, and the communication unit may be a communication interface.
  • the communication interface in the chip can be an input/output interface, a pin, or a circuit.
  • the processing unit executes the instructions stored in the storage unit to enable the communication device to implement the wireless bearer configuration method described in the second aspect or any one of the possible implementations of the second aspect.
  • the storage unit may be the chip
  • the storage unit (for example, register, cache, etc.) in the terminal may also be a storage unit (for example, read-only memory, random access memory, etc.) located outside the chip in the terminal.
  • an embodiment of the present application provides a communication device.
  • the communication device may be a base station or a component (for example, a chip) built in the base station.
  • the communication device may include a communication unit.
  • the communication device may also include a processing unit and a storage unit.
  • the communication unit may be a transceiver.
  • the storage unit may be a memory.
  • the storage unit is used to store instructions.
  • the processing unit may be a processor. The processing unit executes the instructions stored in the storage unit, so that the base station implements the wireless resource configuration method described in the third aspect or any one of the possible implementation manners of the third aspect.
  • the processing unit may be a processor, and the communication unit may be a communication interface.
  • the communication interface in the chip can be an input/output interface, a pin, or a circuit.
  • the processing unit executes the instructions stored in the storage unit to enable the communication device to implement the wireless resource configuration method described in the third aspect or any one of the possible implementations of the third aspect.
  • the storage unit may be the chip
  • the storage unit (for example, register, cache, etc.) in the base station may also be a storage unit (for example, read-only memory, random access memory, etc.) located outside the chip in the base station.
  • an embodiment of the present application provides a communication device.
  • the communication device may be a terminal or a component (for example, a chip) built in the terminal.
  • the communication device may include a communication unit.
  • the communication device may also include a processing unit and a storage unit.
  • the communication unit when the communication device is a terminal, the communication unit may be a transceiver.
  • the storage unit may be a memory.
  • the storage unit is used to store instructions.
  • the processing unit may be a processor. The processing unit executes the instructions stored in the storage unit, so that the terminal implements a wireless resource configuration method described in the fourth aspect or any one of the possible implementation manners of the fourth aspect.
  • the processing unit may be a processor, and the communication unit may be a communication interface.
  • the communication interface in the chip can be an input/output interface, a pin, or a circuit.
  • the processing unit executes the instructions stored in the storage unit to enable the communication device to implement the wireless resource configuration method described in the fourth aspect or any one of the possible implementations of the fourth aspect.
  • the storage unit may be the chip
  • the storage unit (for example, register, cache, etc.) in the terminal may also be a storage unit (for example, read-only memory, random access memory, etc.) located outside the chip in the terminal.
  • the embodiments of the present application provide a computer-readable storage medium.
  • the computer-readable storage medium stores a computer program or instruction.
  • the computer can execute the operations as described in the first aspect to the first aspect.
  • an embodiment of the present application provides a computer-readable storage medium.
  • the computer-readable storage medium stores a computer program or instruction.
  • the computer program or instruction When the computer program or instruction is run on a computer, the computer executes operations such as the second aspect to the first aspect.
  • an embodiment of the present application provides a computer-readable storage medium.
  • the computer-readable storage medium stores a computer program or instruction.
  • the computer program or instruction When the computer program or instruction is run on a computer, the computer executes operations such as the third aspect to A method for configuring wireless resources described in any possible implementation manner of the third aspect.
  • the embodiments of the present application provide a computer-readable storage medium.
  • the computer-readable storage medium stores a computer program or instruction.
  • the computer program or instruction runs on the computer, the computer can execute the fourth aspect to A method for configuring wireless resources described in any one of the possible implementation manners of the fourth aspect.
  • the embodiments of the present application provide a computer program product including instructions.
  • the instructions run on a computer, the computer executes the configuration described in the first aspect or various possible implementations of the first aspect. Radio bearer method.
  • the present application provides a computer program product including instructions, which when the instructions run on a computer, cause the computer to execute the configuration radio bearer described in the second aspect or various possible implementations of the second aspect Methods.
  • the embodiments of the present application provide a computer program product including instructions.
  • the instructions run on a computer, the computer executes the configuration described in the third aspect or various possible implementations of the third aspect. Methods of wireless resources.
  • the embodiments of the present application provide a computer program product including instructions.
  • the instructions run on a computer, the computer executes the configuration described in the fourth aspect or various possible implementations of the fourth aspect. Methods of wireless resources.
  • an embodiment of the present application provides a communication system, which includes any one or more of the following: the communication device described in the fifth aspect and various possible implementation manners, and the sixth aspect and the sixth aspect Various possible implementations of the aspects described in the communication device.
  • the communication system may further include: a core network element configured to send the fifth indication information or the third indication information to the base station.
  • an embodiment of the present application provides a communication system, which includes any one or more of the following: the communication device described in the seventh aspect and various possible implementation manners, and the eighth aspect and the eighth aspect Various possible implementations of the aspects described in the communication device.
  • the communication system may further include: a core network element configured to send the fifth indication information or the third indication information to the base station.
  • an embodiment of the present application provides a communication device.
  • the communication device includes a processor and a storage medium.
  • the storage medium stores instructions. Possible implementations describe a method for configuring radio bearers.
  • an embodiment of the present application provides a communication device.
  • the communication device includes a processor and a storage medium.
  • the storage medium stores instructions. Possible implementations describe a method for configuring radio bearers.
  • an embodiment of the present application provides a communication device that includes a processor and a storage medium.
  • the storage medium stores instructions. When the instructions are executed by the processor, they implement the third aspect or the third aspect.
  • One possible implementation describes a method for configuring radio resources.
  • an embodiment of the present application provides a communication device that includes a processor and a storage medium.
  • the storage medium stores instructions. When the instructions are executed by the processor, they can implement the fourth aspect or the fourth aspect.
  • One possible implementation describes a method for configuring radio resources.
  • the present application provides a chip or chip system.
  • the chip or chip system includes at least one processor and a communication interface.
  • the communication interface and the at least one processor are interconnected through a wire, and the at least one processor is used to run a computer program or Instructions to perform a radio bearer configuration method described in any one of the first aspect to any one of the possible implementation manners of the first aspect.
  • the present application provides a chip or chip system.
  • the chip or chip system includes at least one processor and a communication interface.
  • the communication interface and the at least one processor are interconnected through a wire, and the at least one processor is used to run a computer program or Instructions to perform a radio bearer configuration method described in any one of the second aspect to any one of the possible implementation manners of the second aspect.
  • the present application provides a chip or chip system.
  • the chip or chip system includes at least one processor and a communication interface.
  • the communication interface and the at least one processor are interconnected through a wire, and the at least one processor is used to run a computer program or Instructions to perform a wireless resource configuration method described in any one of the third aspect to any one of the possible implementation manners of the third aspect.
  • the present application provides a chip or chip system.
  • the chip or chip system includes at least one processor and a communication interface. Instructions to perform a wireless resource configuration method described in any one of the possible implementation manners of the fourth aspect to the fourth aspect.
  • the communication interface in the chip can be an input/output interface, a pin, or a circuit.
  • the chip or chip system described above in this application further includes at least one memory, and instructions are stored in the at least one memory.
  • the memory may be a storage unit inside the chip, for example, a register, a cache, etc., or a storage unit of the chip (for example, a read-only memory, a random access memory, etc.).
  • an embodiment of the present application provides a communication device, the communication device includes a processor, the processor is coupled to a memory, and instructions are stored in the memory, and the processor is used to execute the instructions to implement the first aspect or the first aspect A method of configuring radio bearers described in the various possible implementations.
  • an embodiment of the present application provides a communication device that includes a processor, the processor is coupled to a memory, and instructions are stored in the memory, and the processor is used to execute the instructions to implement the second aspect or the second aspect A method for configuring radio bearers described in the various possible implementations.
  • an embodiment of the present application provides a communication device that includes a processor, the processor is coupled to a memory, and instructions are stored in the memory, and the processor is used to execute the instructions to implement the third aspect or the third aspect A method for configuring wireless resources described in the various possible implementations.
  • an embodiment of the present application provides a communication device.
  • the communication device includes a processor, the processor is coupled to a memory, and instructions are stored in the memory, and the processor is used to execute the instructions to implement the fourth aspect or the fourth aspect.
  • the memory described in the twenty-seventh aspect to the thirtieth aspect in the embodiments of the present application may be located inside the communication device or outside the communication device, which is not limited in the embodiment of the present application.
  • FIG. 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of this application.
  • FIGS. 2a and 2b are schematic diagrams of a 5G architecture provided by an embodiment of this application.
  • 3a and 3b are schematic diagrams of another 5G architecture provided by an embodiment of the application.
  • 4a and 4b are schematic structural diagrams of a base station provided by an embodiment of this application.
  • FIG. 5 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • 6 to 8 are schematic flowcharts of a method for configuring a radio bearer according to an embodiment of this application.
  • FIG. 9 is a schematic flowchart of a method for configuring wireless resources provided by an embodiment of this application.
  • FIG. 10 is a specific embodiment of a method for configuring a radio bearer provided by an embodiment of this application.
  • FIG. 11 is a specific embodiment of another method for configuring a radio bearer provided by an embodiment of this application.
  • FIG. 12 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • FIG. 13 is a schematic structural diagram of another communication device provided by an embodiment of this application.
  • FIG. 14 is a schematic structural diagram of a chip provided by an embodiment of the application.
  • words such as “first” and “second” are used to distinguish the same items or similar items that have substantially the same function and effect.
  • the first terminal and the second terminal are only used to distinguish different terminals, and the order of their sequence is not limited.
  • words such as “first” and “second” do not limit the quantity and order of execution, and words such as “first” and “second” do not limit the difference.
  • At least one refers to one or more, and “multiple” refers to two or more.
  • “And/or” describes the association relationship of the associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the associated objects before and after are in an “or” relationship.
  • the following at least one item (a)” or similar expressions refers to any combination of these items, including any combination of a single item (a) or a plurality of items (a).
  • at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple .
  • the communication system includes: a base station 10 and a plurality of terminals communicating with the base station 10 (for example, terminal 1, terminal 2, ..., terminal n ). Wherein, n is an integer greater than or equal to 1. Multiple terminals can receive multicast/broadcast service data from the base station 10.
  • the multicast/broadcast service in the embodiments of this application refers to: multicast service or broadcast (broadcast service) service.
  • the so-called multicast service may mean: a certain service can be sent to a certain communication group in a targeted manner, so that the service can be Received by terminals joining the same communication group.
  • the broadcast service can refer to: a certain service can be sent by broadcast, and multiple terminals within the broadcast range can receive the service sent by broadcast, but it does not limit the multiple terminals to belong to the same communication group .
  • the multiple terminals can join the same multicast/broadcast service.
  • multiple terminals can receive the same multicast/broadcast service or join different multicast/broadcast services.
  • the multicast/broadcast services joined by each of the multiple terminals are different.
  • the multicast in the embodiments of the present application may also be referred to as multicast.
  • the multiple terminals may form a communication group (for example, it may be called a broadcast group or a multicast group), and the terminals in the communication group Can receive the same data at the same time, that is, multicast/broadcast service data.
  • the base station 10 in the embodiment of the present application may configure a multicast radio bearer for the multicast/broadcast service, and send it to the terminals in the communication group. Send the configuration information of the multicast radio bearer.
  • the terminal can establish a multicast radio bearer between the terminal and the base station 10 according to the received configuration information of the multicast radio bearer. Then, the base station 10 can send multicast/broadcast service data to the terminal on the multicast radio bearer.
  • the communication system may further include: a core network element 20, configured to send a first request message or a second request message to the base station 10, or send security parameters to the base station 10.
  • a core network element 20 configured to send a first request message or a second request message to the base station 10, or send security parameters to the base station 10.
  • the communication system shown in FIG. 1 may be a communication system in the 3rd generation partnership project (3rd generation partnership project, 3GPP), for example, a long term evolution (LTE) communication system, or a fifth generation (The 5th generation (5G) communication system or the new radio (NR) communication system may also be a non-3GPP communication system, which is not limited.
  • 3rd generation partnership project 3rd generation partnership project, 3GPP
  • LTE long term evolution
  • NR new radio
  • the above-mentioned core network element may be a session management function (SMF) network element in the 5G communication system
  • the above-mentioned base station may be Radio access network (RAN) equipment in a 5G communication system.
  • SMF session management function
  • RAN Radio access network
  • the system may also include: access and mobility management function (AMF) network elements, policy control Function (policy control function, PCF) network element, session anchor (PDU session anchor, PSA) (also called user plane function (UPF) network element), authentication server function (authentication server function, AUSF) ) Network elements, network slice selection function (NSSF) network elements, unified data management (UDM) network elements, data network (DN), application function (AF) network Meta, multicast control function (Multicast Control Function, MCF), multicast user plane function (Multicast User Plane Function, MUF), etc.
  • AMF access and mobility management function
  • policy control function policy control function
  • PCF session anchor
  • PSA also called user plane function (UPF) network element
  • authentication server function authentication server function
  • NSSF network slice selection function
  • UDM network slice selection function
  • UDM network slice selection function
  • DN data network
  • AF application function
  • MCF multicast control function
  • MUF Multicast User Plane Function
  • MCF network elements can be used to control multicast/broadcast services.
  • the MCF network element has a communication interface with a content provider (Content Provider, CP) in order to receive multicast service information (for example, a description of the multicast service).
  • the MCF network element has a communication interface with the PCF to create resources for the multicast service.
  • the MUF network element is used to deliver the multicast message, that is, the multicast message (that is, the data of the multicast/multicast service) received from the CP is sent to the downstream node UPF network element.
  • the CP may be a kind of application function network element.
  • system shown in FIG. 2a may also include intermediate UPF (Intermediate UPF, I-UPF) network elements, which are used to implement service flow offloading.
  • I-UPF Intermediate UPF
  • the terminal communicates with the AMF network element through the N1 interface (N1 for short).
  • the AMF network element communicates with the SMF network element through the N11 interface (N11 for short).
  • the SMF network element communicates with one or more UPF network elements through the N4 interface (N4 for short). Any two UPF network elements in one or more UPF network elements communicate through the N9 interface (N9 for short), for example, the I-UPF network element and the UPF network element communicate through the N9 interface, (R)AN and the I-UPF network There is an N3 interface between the elements.
  • the UPF network element communicates with the data network (DN) managed and controlled by the AF network element through the N6 interface (N6 for short).
  • the terminal communicates with a 5G core network (5G Core, 5GC) through (R)AN, and communicates between (R)AN and AMF network elements through an N2 interface (N2 for short).
  • the SMF network element communicates with the PCF network element through the N7 interface (N7 for short), and the PCF network element communicates with the AF network element through the N5 interface.
  • (R) AN communicates with UPF network element through N3 interface (N3 for short). Any two AMF network elements communicate through the N14 interface (N14 for short).
  • the SMF network element communicates with the UDM network element through the N10 interface (N10 for short).
  • the AMF network element communicates with the AUSF network element through the N12 interface (N12 for short).
  • the AUSF network element communicates with the UDM network element through the N13 interface (N13 for short).
  • the AMF network element communicates with the UDM network element through the N8 interface (N8 for short).
  • the control plane network elements in the 5GC may also interact with each other using a service-oriented interface.
  • AMF network elements, SMF network elements, UDM network elements, or PCF network elements interact with each other using a service-based interface.
  • the service-oriented interface provided by the AMF network element to the outside may be Namf.
  • the service-oriented interface provided by the SMF network element to the outside may be Nsmf.
  • the service-oriented interface provided by the UDM network element to the outside may be Nudm.
  • the service-oriented interface provided by the PCF network element to the outside may be Npcf.
  • FIG. 2a or FIG. 2b is only an example of a UPF network element or an SMF network element.
  • multiple UPF network elements and SMF network elements may be included, such as SMF network element 1 and SMF network element 2, which are not specifically limited in the embodiment of the present application.
  • (R)AN, AMF network element, SMF network element, UDM network element, UPF network element, PCF network element, authentication server function (authentication server function, AUSF) network element, etc. in Figure 2a or Figure 2b It is just a name, and the name does not limit the device itself.
  • the network elements or entities corresponding to (R)AN, AMF network elements, SMF network elements, UDM network elements, UPF network elements, and PCF network elements can also have other names. This application The embodiment does not specifically limit this.
  • the UDM network element may also be replaced with a user home server (home subscriber server, HSS) or user subscription database (user subscription database, USD) or a database entity, etc., which will be uniformly explained here and will not be repeated in the following .
  • HSS home subscriber server
  • USD user subscription database
  • the MCF network element can be integrated into the PCF network element, and the MUF network element can be integrated into the UPF network element, which is not limited in the embodiment of the present application.
  • resources can be allocated for multicast/broadcast services through SMF network elements and AMF network elements serving the terminal. It is also possible to allocate resources for multicast/broadcast services through dedicated SMF network elements and AMF network elements, that is, the SMF network element/AMF network element is specifically responsible for the management and control of multicast/broadcast services.
  • SMF network element/AMF network element is specifically responsible for the management and control of multicast/broadcast services.
  • M-SMF and M-AMF in 3a are SMF network elements and AMF network elements responsible for the management and control of multicast services.
  • the M-SMF network element and M-AMF network element can also serve the terminal, but when managing multicast/broadcast services, the M-SMF network element/M-AMF network element does not It must serve the terminal that is receiving the multicast/broadcast service.
  • AMF network elements, SMF network elements, and UPF network elements are AMF network elements, SMF network elements, and UPF network elements that serve the terminal.
  • the UPF network element is only responsible for data transmission of the terminal unicast service. If the terminal accesses the multicast/broadcast service, the multicast/broadcast service is sent to the terminal via the MUF network element, M-UPF network element, and (R)AN.
  • M-SMF network elements, M-AMF network elements, and M-PCF network elements are used to manage the resources of multicast/broadcast services, and M-PCF network elements perform QoS for multicast/broadcast services according to the service description of the MCF network element
  • M-SMF and M-AMF are used to create a multicast context (or called a multicast session) on the (R)AN.
  • the SMF network element interfaces with the MCF network element (or interface with the M-PCF network element, not shown in the figure) to obtain multicast information, so as to add the terminal to the multicast/broadcast service.
  • the above-mentioned M-SMF, M-AMF, and M-PCF are SMF network elements, AMF network elements, and PCF network elements related to multicast/broadcast services. AMF network elements and PCF network elements are distinguished.
  • the architecture shown in Figure 2a or Figure 2b can also be transformed into the architecture shown in Figure 3b.
  • the MCF network element is similar to an SMF network element, and the MCF network element is responsible for the multicast service. manage. If the MCF network element is an SMF network element, the SMF network element can also provide services for the session of the terminal, which is not limited in the present invention.
  • the CP interfaces with the PCF network element/NEF network element to send multicast service information to the PCF network element. If the CP interfaces with the NEF network element, the CP first sends the multicast service information to the NEF network element, and then the NEF network element sends it to the PCF network element, or the CP directly interfaces with the PCF.
  • the MCF network element obtains the PCC rule corresponding to the multicast service from the PCF network element, so as to create a corresponding resource (that is, a multicast session) for the multicast service.
  • the MCF network element interfaces with the base station through the M-AMF network element.
  • the M-AMF network element can also provide services for the terminal.
  • the SMF network element serving the terminal is interfaced with the PCF network element to obtain information related to the multicast service.
  • a base station can also be called an access network device, which is an entity that can be used to transmit or receive signals in cooperation with a terminal. It is mainly used to realize functions such as physical layer functions, resource scheduling and management, terminal access control, and mobility management.
  • the access network device can be a device that supports wired access or a device that supports wireless access.
  • the access network equipment may be an access network (access network, AN)/radio access network (radio access network, RAN), which is composed of multiple 5G-AN/5G-RAN nodes.
  • 5G-AN/5G-RAN nodes can be: access point (AP), base station (nodeB, NB), enhanced base station (enhance nodeB, eNB), next-generation base station (NR nodeB, gNB), transmission and reception Point (transmission reception point, TRP), transmission point (transmission point, TP), or some other access node, etc.
  • AP access point
  • base station nodeB, NB
  • enhanced base station enhanced base station
  • NR nodeB, gNB next-generation base station
  • transmission and reception Point transmission reception point, TRP
  • transmission point transmission point
  • TP transmission point
  • the AMF network element mainly uses the N1 interface to access the terminal's NAS signaling (including session management (SM) signaling) and the N2 interface to access the RAN signaling to complete the user registration process and the forwarding of SM signaling and Mobility management.
  • NAS signaling including session management (SM) signaling
  • N2 interface to access the RAN signaling to complete the user registration process and the forwarding of SM signaling and Mobility management.
  • the SMF network element is used to implement procedures related to session establishment, release, and update.
  • the PCF network element is responsible for user policy management, including both mobility-related policies and PDU session-related policies, such as QoS policies and charging policies.
  • UDM network element used to save the user's subscription data.
  • the AUSF network element is used to implement authentication and authorization service functions, and is responsible for authentication and authorization of terminal access.
  • NEF network elements are used to support the security interaction between 3GPP networks and third-party applications. NEF network elements can safely expose network capabilities and events to third parties to enhance or improve application service quality. 3GPP networks can also safely The three parties obtain relevant data to enhance the intelligent decision-making of the network; at the same time, the network element supports the restoration of structured data from the unified database or the storage of structured data in the unified database.
  • the AF network element is used to implement interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network side.
  • NWDAF network elements are used to implement data analysis functions.
  • the NRF network element used to maintain real-time information of all network functions and services in the network.
  • the NRF network element saves the information of the deployed network function (NF) component, such as the identity and network address of the NF component, the identity of the supported network slice, or the information of the data plane instance, etc.
  • the NRF network element provides other NFs Services such as registration and discovery of NF components.
  • DN Data network
  • IMS IP Multi-media Service, IP multimedia service
  • Internet Internet
  • a terminal 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 devices connected to a wireless modem.
  • the wireless terminal can communicate with one or more core networks via the RAN.
  • Wireless terminals can be user equipment (UE), handheld terminals, notebook computers, subscriber units, cellular phones, smart phones, wireless data cards, and personal digital assistants. assistant, PDA) computer, tablet computer, wireless modem (modem), handheld device (handheld), laptop computer, cordless phone (wireless local loop, WLL) station , Machine type communication (MTC) terminals or other devices that can access the network.
  • a certain air interface technology for example, 3GPP access technology or non-3GPP access technology is used between the terminal and the access network device to communicate with each other.
  • FIG. 4a it is a schematic diagram of a network architecture provided by an embodiment of the application.
  • the network architecture includes core network (CN) equipment and access network (taking RAN as an example) equipment.
  • the RAN equipment includes a baseband device and a radio frequency device.
  • the baseband device can be implemented by one node or by multiple nodes.
  • the radio frequency device can be implemented remotely from the baseband device, and can also be integrated into the baseband device, or part of it. Integrated in the baseband device.
  • the RAN equipment includes a baseband device and a radio frequency device, where the radio frequency device can be arranged remotely relative to the baseband device (for example, a radio remote unit (RRU) is relative to the baseband processing unit ( building base band unit, BBU), RAN equipment is implemented by a node, which is used to implement radio resource control (radio resource control, RRC), packet data convergence protocol (PDCP), and radio link control Protocol layer functions such as (radio link control, RLC) and medium access control (medium access control, MAC).
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • RLC radio link control Protocol layer functions
  • the baseband device may include a CU and a DU, and multiple DUs may be centrally controlled by one CU.
  • CU and DU can be divided according to the protocol layer of the wireless network.
  • the functions of the protocol layer of the packet data convergence layer and the above protocol layer are set in the CU, the protocol layer below PDCP, such as the functions of the RLC layer and the MAC layer.
  • the protocol layer below PDCP such as the functions of the RLC layer and the MAC layer.
  • This type of protocol layer division is just an example, it can also be divided in other protocol layers, for example, in the RLC layer, the functions of the RLC layer and above protocol layers are set in the CU, and the functions of the protocol layers below the RLC layer are set in the DU; Or, in a certain protocol layer, for example, part of the functions of the RLC layer and the functions of the protocol layer above the RLC layer are set in the CU, and the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer are set in the DU. In addition, it can also be divided in other ways, for example, by time delay. The functions that need to meet the time delay requirement for processing time are set in the DU, and the functions that do not need to meet the time delay requirement are set in the CU.
  • the radio frequency device can be remote, not placed in the DU, can also be integrated in the DU, or part of the remote part is integrated in the DU, and there is no restriction here.
  • control plane (CP) and the user plane (UP) of the CU can also be separated and divided into different entities for implementation.
  • the data generated by the CU can be sent to the terminal through the DU, or the data generated by the terminal can be sent to the CU through the DU.
  • the DU may directly pass the protocol layer encapsulation to the terminal or CU without analyzing the data.
  • the RRC or PDCP layer data will eventually be processed as physical layer (PHY) data and sent to the terminal, or converted from the received PHY layer data.
  • PHY physical layer
  • the RRC or PDCP layer data can also be considered to be sent by the DU.
  • the CU is divided into access networks.
  • the CU may also be divided into core networks, which is not limited here.
  • the devices in the following embodiments of the present application may be located in a terminal or a base station according to the functions they implement.
  • the base station may be a CU node, or a DU node, or a RAN device including the functions of a CU node and a DU node.
  • FIG. 5 is a schematic diagram of the composition of a communication device provided by an embodiment of the application.
  • the base station and terminal can refer to the structure of the communication device as shown in FIG. 5.
  • the communication device may include at least one processor 41 and a memory 42.
  • the processor 41 is the control center of the communication device, and may be a processor or a collective name for multiple processing elements.
  • the processor 41 is a CPU, or a specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits configured to implement the embodiments of the present application, such as one or more micro-processing Digital Signal Processor (DSP), or one or more Field Programmable Gate Array (FPGA).
  • DSP Digital Signal Processor
  • FPGA Field Programmable Gate Array
  • the processor 41 can execute various functions of the access network device by running or executing a software program stored in the memory 42 and calling data stored in the memory 42, for example, for executing various method embodiments of the present application.
  • the processor 41 may include one or more CPUs, such as CPU 0 and CPU 1 shown in FIG. 5.
  • the communication device may include multiple processors, such as the processor 41 and the processor 45 shown in FIG. 5.
  • processors can be a single-core processor (single-CPU) or a multi-core processor (multi-CPU).
  • the processor here may refer to one or more devices, circuits, and/or processing cores for processing data (for example, computer program instructions).
  • the memory 42 may be a read-only memory (Read-Only Memory, ROM) or other types of static storage devices that can store static information and instructions, random access memory (Random Access Memory, RAM), or other types that can store information and instructions
  • the dynamic storage device can also be electrically erasable programmable read-only memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), CD-ROM (Compact Disc Read-Only Memory, CD-ROM) or other optical disc storage, optical disc storage (Including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program codes in the form of instructions or data structures and can be used by a computer Any other media accessed, but not limited to this.
  • the communication device further includes: a bus 44.
  • the memory 42 may exist independently, and is connected to the processor 41 through a bus 44.
  • the memory 42 may also be integrated with the processor 41.
  • the memory 42 is used to store a software program for executing the solution of the present application.
  • the communication device further includes: a transceiver 43.
  • the transceiver 43 is used to communicate with other devices or a communication network. For example, it is used to communicate with communication networks such as terminals, core network elements (for example, SMF network elements, etc.), Ethernet, RAN, and wireless local area networks (WLAN).
  • the transceiver 43 may include all or part of the baseband processor, and may also optionally include an RF processor.
  • the RF processor is used for sending and receiving RF signals
  • the baseband processor is used for processing the baseband signal converted from the RF signal or the baseband signal about to be converted into the RF signal.
  • the bus 44 may be an Industry Standard Architecture (ISA) bus, Peripheral Component Interconnect (PCI) bus, or Extended Industry Standard Architecture (EISA) bus, etc.
  • ISA Industry Standard Architecture
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into address bus, data bus, control bus and so on. For ease of presentation, only one thick line is used to represent in FIG. 5, but it does not mean that there is only one bus or one type of bus.
  • the device structure shown in FIG. 5 does not constitute a limitation on the communication device, and may include more or fewer components than shown, or a combination of some components, or a different component arrangement.
  • the communication method provided by the embodiment of the present application may be described below in conjunction with any one of the communication systems shown in FIG. 1 to FIG. 3b. It should be noted that the actions, terms, etc. involved in the various embodiments of the present application can be referred to each other and are not limited.
  • the names of messages or parameter names in the messages that are exchanged between devices in the embodiments of the present application are just an example, and other names may also be used in specific implementations, which are not limited.
  • the multicast described in the embodiments of the present application can be replaced with terms such as broadcast, multicast, multicast communication, multicast communication, multicast broadcast, and multicast broadcast.
  • the determination in the embodiments of this application can also be understood as creating (create) or generating (generate), and the "including” in the embodiments of this application can also be understood as "carrying". Specific restrictions.
  • the embodiment of the present application provides a method for configuring a radio bearer.
  • the subject of the method for configuring a radio bearer may be a base station or a chip applied to the base station.
  • the execution body of configuring the radio bearer may be the terminal, or may be a chip applied in the terminal.
  • the executor of the wireless bearer configuration method is the base station, and the executor of the wireless bearer configuration method is the terminal as an example.
  • FIG. 6 shows an interactive embodiment of a method for configuring a radio bearer provided by an embodiment of the present application, and the method includes:
  • Step 601 The base station receives a first request message, where the first request message is used to request the first terminal to join the multicast/broadcast service.
  • the first request message may carry the identifier of the multicast/broadcast service, and may also carry indication information.
  • the indication information may be used to indicate a request to the base station to add the first terminal to the multicast/broadcast service; the identifier of the multicast/broadcast service may be the multicast address corresponding to the multicast/broadcast service, or it may be the multicast/broadcast service.
  • the identifier of the multicast/broadcast service may also be referred to as the identification information of the data of the multicast/broadcast service.
  • the identification information of the data of the multicast/broadcast service may be used to uniquely identify the data of the multicast/broadcast service, and the identification information of the data of the multicast/broadcast service may be sent to the terminal by the application server (ie, CP).
  • the base station can receive the first request message through the signaling connection (for example, N2 signaling connection) between it and the first terminal, so that the base station can request the first terminal to join the multicast/broadcast according to the first request message. business.
  • the signaling connection for example, N2 signaling connection
  • the first terminal may be any terminal from terminal 1 to terminal n in FIG. 1.
  • the base station may be the base station 10 in FIG. 1, or may be a wireless access network device or an access network device.
  • the base station may receive the first request message from the session management network element (for example, the SMF network element).
  • the session management network element sends a first request message to an access management network element (for example, an AMF network element) accessed by the first terminal, and then the access management network element sends the first request message to the base station.
  • an access management network element for example, an AMF network element
  • Step 601 in the embodiment of the present application can be replaced by the following steps: the base station determines to add the first terminal to the multicast/broadcast service.
  • the determination by the base station to add the first terminal to the multicast/broadcast service may be determined by the base station according to the first request message.
  • the first request message carries instruction information, which is used to instruct the base station to request the first terminal to join the multicast/broadcast service, and the base station determines to add the first terminal to the multicast/broadcast service according to the instruction information.
  • Step 602 The base station sends configuration information of the multicast radio bearer to the first terminal according to the quality of service (QoS) flow information of the multicast/broadcast service.
  • QoS quality of service
  • the first terminal receives the configuration information of the multicast radio bearer from the base station.
  • the multicast radio bearer in the embodiments of the present application may also be referred to as a multicast broadcast radio bearer, which is described here in a unified manner.
  • the configuration information of the multicast radio bearer is used to configure the multicast radio bearer.
  • the multicast radio bearer is used to transmit data of the multicast/broadcast service to the terminals that have joined the multicast/broadcast service, and the terminals that have joined the multicast/broadcast service include the first terminal.
  • the configuration information may include packet data convergence protocol (packet data convergence protocol, PDCP) configuration information.
  • the PDCP configuration information may include one or more of the following information: PDCP sequence number (SN) Length, length of the discard timer, indication information indicating whether to perform header compression, indication information indicating whether the multicast radio bearer performs integrity protection, indication information indicating whether the multicast radio bearer performs encryption, etc.
  • the configuration information may also include radio link control (radio link control, RLC) configuration information.
  • the configuration information of the RLC may be that the transmission mode adopted by the multicast radio bearer is the unconfirmed mode, or the confirmed mode.
  • the data of the multicast/broadcast service may be data sent by the network side to one or more terminals belonging to the communication group.
  • the communication group can be a fleet receiving commands from the same command center or a group receiving the same TV program.
  • the terminal is a set-top box (STB), and the STB can display relevant information about these TV programs to the user.
  • STB1 terminal 1
  • STBn terminal n
  • the base station can send the TV program of CCTV1 to terminal 1 ⁇ terminal n on the multicast radio bearer, which is convenient for terminal 1.
  • Users of terminal n watch CCTV1 TV programs.
  • the multicast radio bearer is used to transmit data of the multicast/broadcast service to the terminals that have joined the multicast/broadcast service can be understood as: the multicast radio bearer is used to transmit the group to each terminal belonging to the same communication group. Broadcast business data.
  • the communication group can be understood as: including one or more terminals that have joined the multicast/broadcast service.
  • the base station may send configuration information of the multicast radio bearer to the terminal joining the multicast/broadcast service, so that the base station and the terminal of the multicast/broadcast service both establish a multicast radio bearer. Subsequently, the base station can use the multicast radio bearer to transmit data of the multicast/broadcast service to the terminals that have joined the multicast/broadcast service. The so-called base station can use the multicast radio bearer to transmit multicast/broadcast service data to terminals that have joined the multicast/broadcast service. It can be understood that the base station uses the same multicast radio bearer configuration information for the multicast/broadcast service. Data to be processed.
  • the base station sends the processed data of the multicast/broadcast service to the terminal joining the multicast/broadcast service.
  • the terminal joining the multicast/broadcast service can obtain the same multicast/broadcast service data by performing reverse processing according to the configuration information of the same radio bearer. It can be understood that the configuration information of the multicast radio bearer from the base station received by the terminal joining the multicast/broadcast service is the same.
  • some terminals may receive multicast/broadcast service data in a point-to-multipoint (PTM) manner, while some other terminals may receive multicast/broadcast service data in a point-to-multipoint (PTM) manner.
  • PTM point-to-multipoint
  • PTP Point to point
  • the QoS flow information of the multicast/broadcast service in the embodiment of the present application may refer to at least one QoS flow information corresponding to the multicast/broadcast service.
  • the base station has at least one quality of service QoS flow information corresponding to the multicast/broadcast service.
  • the at least one quality of service QoS flow information corresponding to the multicast/broadcast service may be provided to the base station by the SMF network element or the MCF network element corresponding to the multicast session (corresponding to the multicast/broadcast service).
  • the base station when the base station creates the multicast session corresponding to the multicast/broadcast service, the base station obtains at least one quality of service QoS flow information corresponding to the multicast/broadcast service from the SMF network element or the MCF network element.
  • the at least one quality of service QoS flow information corresponding to the multicast/broadcast service may be carried in the first request message, or the base station may have received the multicast/broadcast service before the base station receives the first request message.
  • Corresponding at least one quality of service QoS flow information may be carried in the first request message, or the base station may have received the multicast/broadcast service before the base station receives the first request message.
  • the QoS flow information involved in the embodiments of the present application includes the quality of service flow identifier (QoS Flow Identifier, QFI) corresponding to the QoS flow and/or the QoS parameters corresponding to the QoS flow.
  • QFI quality of service flow identifier
  • the QoS parameters may include: 5G QoS identifier (5G QoS Identifier, 5QI), scheduling priority (Priority level), the maximum bandwidth of the QoS flow, the guaranteed bandwidth corresponding to the QoS flow, and the allocation priority (Allocation and Retention) corresponding to the QoS flow.
  • Priority, ARP guaranteed rate (Guaranteed Bit Rate, GBR), non-guaranteed bit rate (Non-Guaranteed Bit Rate, Non-GBR), one or more of the delay corresponding to the QoS flow.
  • the base station sends the configuration information of the multicast radio bearer to the first terminal according to the QoS flow information, including: the base station determines the multicast radio bearer according to the QoS flow information of the multicast/broadcast service. The base station sends the determined configuration information of the multicast radio bearer to the first terminal.
  • the base station determining the multicast radio bearer according to the QoS flow information of the multicast/broadcast service can be implemented in the following manners 1 and 2:
  • Manner 1 The base station determines at least one QoS flow corresponding to the multicast/broadcast service according to at least one QoS flow information corresponding to the multicast/broadcast service.
  • the base station determines the multicast radio bearer of each QoS stream in at least one QoS stream corresponding to the multicast/broadcast service, and obtains the multicast radio bearer of the multicast/broadcast service.
  • the multicast radio bearer of the multicast/broadcast service includes the multicast radio bearer of each QoS flow corresponding to the multicast/broadcast service.
  • one multicast/broadcast service may correspond to at least one QoS flow (for example, a voice service flow and a video service flow).
  • the base station may allocate a different multicast radio bearer for each QoS flow in the at least one QoS flow, that is, the QoS flow and the multicast radio bearer have a one-to-one correspondence (for example, the multicast radio bearer is allocated for the voice service flow). 2. Allocate the multicast radio bearer for the video service stream 1).
  • the base station can also allocate the same multicast radio bearer for some QoS flows in at least one QoS flow, and allocate different multicast radio bearers for some QoS flows, that is, the relationship between the QoS flow and the multicast radio bearer is a many-to-one relationship
  • the base station may also allocate the same multicast radio bearer for each QoS flow in the at least one QoS flow, that is, all QoS flows of the multicast/broadcast service are mapped to the same multicast radio bearer.
  • the base station may determine whether the relationship between the QoS flow and the multicast radio bearer is a many-to-one relationship or a one-to-one correspondence relationship through the following manner two.
  • the base station may determine whether to map different QoS flows to the same multicast radio bearer according to the QoS parameters of each QoS flow in at least one QoS flow. For example, taking the QoS parameter as the scheduling priority as an example, the base station can map QoS flows with the same scheduling priority to the same first multicast radio bearer, and then the first multicast radio bearer can be determined as multicast/broadcast.
  • the multicast radio bearer of the service that is, the relationship between the QoS flow and the multicast radio bearer is a many-to-one relationship.
  • the base station can map QoS streams with different scheduling priorities to different second multicast radio bearers, and these different second multicast radio bearers are used as multicast radio bearers for multicast/broadcast services, that is, QoS streams and groups.
  • the relationship between broadcast radio bearers is a one-to-one correspondence.
  • the base station determines that the voice service stream and the video service stream require the same bandwidth according to the QoS parameters of the voice service stream and the QoS parameter of the video service stream, it can determine to map the voice service stream and the video service stream to the same multicast radio bearer. That is, the same multicast radio bearer is allocated for the voice service stream and the video service stream. If the base station determines that the voice service stream and the video service stream require different bandwidths according to the QoS parameters of the voice service stream and the QoS parameter of the video service stream, the base station can determine to map the voice service stream and the video service stream to different multicast radio bearers, That is, different multicast radio bearers are allocated for voice service streams and video service streams.
  • the base station can allocate multicast radio bearer 1 for voice service flow and multicast radio bearer for video service flow 2, so that the configuration information of the multicast radio bearer sent by the base station for the first terminal includes the configuration information of the multicast radio bearer 1 and the configuration information of the multicast radio bearer 2, where the multicast radio bearer 1 is used to establish the multicast radio Bearer 1.
  • Multicast radio bearer 2 is used to establish multicast radio bearer 2.
  • the base station can send the voice service stream of the multicast/broadcast service to the first terminal on the multicast radio bearer 1, and send the video service stream of the multicast/broadcast service to the first terminal on the multicast radio bearer 2.
  • multiple multicast radio bearers may be established between the base station and the first terminal, and different multicast radio bearers have different QoS parameters.
  • groups meeting the QoS parameter requirements can be established according to the QoS parameters.
  • Broadcast wireless bearer
  • the base station includes the QFI of one or more QoS flows mapped to the multicast radio bearer in the configuration information of the multicast radio bearer.
  • the method provided in the embodiment of the present application may further include: the base station determines the QoS parameter of the multicast radio bearer according to the QoS parameter information of all the multicast QoS streams mapped to the multicast radio bearer.
  • the QoS parameters may include one or more of 5QI, scheduling priority, maximum bandwidth, and guaranteed bandwidth of the multicast radio bearer.
  • the above method may further include: the base station determines the logical channel identifier corresponding to the multicast radio bearer.
  • the base station allocates a logical channel identifier for the multicast radio bearer of the multicast/broadcast service, the base station sends the configuration information of the multicast radio bearer carried by the logical channel identifier of the multicast radio bearer to the first terminal, or the base station sends the multicast radio bearer to the first terminal.
  • the logical channel identifier of the radio bearer is separately sent to the first terminal.
  • step 602 in the embodiment of the present application may be implemented in the following manner: the base station sends configuration information of the multicast radio bearer to the first terminal through an established RRC connection with the first terminal.
  • the base station sends a first message to the first terminal through an established RRC connection with the first terminal, and the first message includes configuration information of the multicast radio bearer.
  • the first message may be an RRC message, such as an RRC reconfiguration message (RRC Reconfiguration), and the RRC message includes configuration information of the radio bearer.
  • RRC Reconfiguration RRC reconfiguration message
  • the established RRC connection uses a specific signaling radio bearer (SRB), and the information can be encrypted.
  • the configuration information of the multicast radio bearer includes first indication information, and the first indication information is used to indicate that the type of the multicast radio bearer configured for the first terminal is a multicast type. In this way, it is convenient for the first terminal to determine that the type of the broadcast radio bearer is the multicast type according to the first indication information.
  • the first indication information may be carried in the configuration information of the multicast radio bearer.
  • the configuration information of the multicast radio bearer includes a bearer type field, and the bearer type field is set to the multicast type.
  • An indication information may also be sent by the base station to the first terminal through separate signaling.
  • the configuration information of the multicast radio bearer further includes: the identifier of the multicast/broadcast service, or the identifier of the multicast session associated with the multicast/broadcast service.
  • the first terminal can configure the multicast radio bearer with the base station according to the configuration information of the multicast radio bearer, and then use the identifier of the multicast/broadcast service or the identifier of the multicast session associated with the multicast/broadcast service. It is determined that the multicast radio bearer is associated with the identifier of the multicast/broadcast service, or the identifier of the multicast session associated with the multicast/broadcast service. In other words, the first terminal can determine that the multicast radio bearer is used to receive the data of the multicast/broadcast service indicated by the identifier of the multicast/broadcast service.
  • the multicast radio bearer in the embodiment of the present application is specifically established by the first terminal according to the configuration information of the radio bearer for receiving data of the multicast/broadcast service.
  • the configuration information of the multicast radio bearer includes one or more of the following: an identifier of the multicast radio bearer, and an identifier of the first logical channel to which the multicast radio bearer is mapped.
  • the first logical channel is a logical channel corresponding to the multicast radio bearer.
  • the data sent via the multicast radio bearer will carry the identifier of the first logical channel, so that the receiving end (first terminal) can determine the corresponding data packet according to the identifier of the first logical channel in the data packet Multicast radio bearer, so that the data packet is sent to the multicast radio bearer for further processing.
  • the logical channel corresponds to an identity (ID), the logical channel identity (LCID) can be used to identify the logical channel, and the logical channel identity can be the index number of the logical channel, etc.
  • Step 603 The first terminal configures the multicast radio bearer according to the configuration information of the multicast radio bearer.
  • the first terminal configures the PDCP of the multicast radio bearer according to the PDCP configuration information, and configures the RLC of the multicast radio bearer according to the configuration information of the RLC. For example, if the configuration information of PDCP indicates the indication information for the multicast radio bearer to perform encryption, the first terminal configures the multicast radio bearer as an encrypted multicast radio bearer.
  • the embodiment of the present application provides a method for configuring a radio bearer.
  • the base station receives the first request message requesting the first terminal to join the multicast/broadcast service according to the QoS flow of the multicast/broadcast service.
  • Information configuration information for configuring the multicast radio bearer for the first terminal.
  • the base station can use the multicast radio bearer to send the multicast/broadcast service data to the first terminal.
  • point-to-multipoint mode also called: multicast transmission
  • point-to-point mode also called: unicast transmission
  • the first terminal in the embodiment of the present application is configured with a first medium access control (medium access control, MAC) entity.
  • the first MAC entity may be used to transmit (for example, receive or send) data of the multicast/broadcast service.
  • the first MAC entity of the first terminal may be configured by the base station for the first terminal. Specifically, for the process of configuring the first MAC entity by the base station for the first terminal, reference may be made to the embodiment shown in FIG.
  • the first MAC entity is associated with a first radio network temporary identifier (RNTI).
  • RNTI radio network temporary identifier
  • the first RNTI corresponds to a multicast/broadcast service, or the first RNTI corresponds to a first terminal.
  • the association of the first MAC entity with the first RNTI means that the base station uses the first RNTI to scramble the data transmitted through the first MAC entity.
  • the terminal receives the data, if the data passes through the first MAC entity For transmission, the first RNTI is used to descramble the data.
  • the prior art refers the prior art.
  • the correspondence between the first RNTI and the multicast/broadcast service can be understood as: the first RNTI is the RNTI allocated by the core network element or the base station for the multicast/broadcast service; or, the first RNTI and the multicast/broadcast service Identify the association, or the first RNTI is associated with the multicast session.
  • the first MAC entity is shared by multiple terminals joining the multicast/broadcast service, that is, the base station configures the first MAC entity for the multiple terminals joining the multicast/broadcast service.
  • the configuration information of a MAC entity is the same.
  • the association between the first RNTI and the multicast session may also be understood as: there is a mapping relationship between the first RNTI and the identifier of the multicast session, or the first RNTI is the identifier of the multicast session.
  • the correspondence between the first RNTI and the first terminal can be understood as: the base station allocates the first RNTI to the first terminal.
  • the first RNTI may be the identity of the first terminal, or the first RNTI is associated with the identity of the first terminal. It should be understood that the base station allocates different first RNTIs to different terminals.
  • the first RNTI corresponds to the first terminal
  • the first RNTI also corresponds to the multicast/broadcast service, that is, the first RNTI corresponds to the multicast/broadcast service of the first terminal.
  • the first RNTI is the RNTI allocated by the base station for the multicast/broadcast service of the first terminal.
  • the first terminal may determine the multicast/broadcast service according to the first RNTI.
  • the identity association between the first RNTI and the first terminal can be understood as: the first RNTI and the identity of the first terminal have a mapping relationship, and the two are different.
  • the identifier of the terminal may be one or more of the following: Cell-RadioNetworkTemporaryIdentifier (C-RNTI), internet protocol address (Internet protocol, IP), subscription permanent identifier (SUPI) , Permanent equipment identifier (PEI), generic public subscription identifier (GPSI), international mobile subscriber identifier (IMSI), international mobile equipment identity (IMEI) ), IP quintuple (5-tuple) and mobile station international integrated service digital network number (mobile station international integrated service digital network number, MSISDN).
  • C-RNTI Cell-RadioNetworkTemporaryIdentifier
  • IP internet protocol address
  • IP subscription permanent identifier
  • PKI Permanent equipment identifier
  • GPSI generic public subscription identifier
  • IMSI international mobile subscriber identifier
  • IMEI international mobile equipment identity
  • IP quintuple mobile station international integrated service digital network number
  • MSISDN mobile station international integrated service digital network number
  • the first RNTI associated with the first MAC entity of the terminal a and the terminal b is RNTI1
  • the RNTI1 corresponds to a multicast/broadcast service.
  • the first RNTI associated with the first MAC entity of the terminal c is RNTI2, and the RNTI2 corresponds to the terminal c.
  • the base station first processes the data of the multicast/broadcast service through the multicast radio bearer, for example, performs header compression, encryption, encapsulation, fragmentation, encoding, adding logical channel identifiers, etc., for details, please refer to the existing With technology, the base station then scrambles the above-mentioned processed data through RNTI1 and sends it to terminal a and terminal b, and base station 10 scrambles the above-mentioned processed data through RNTI2 and sends it to terminal c.
  • terminal a and terminal b that support point-to-multipoint mode after receiving the data, they are descrambled through RNTI1, and then reversely processed through the multicast radio bearer, such as recovering the compressed header, decrypting, decapsulating, Fragmentation recombination, decoding, etc., in order to restore the data broadcast of the multicast/broadcast service.
  • the terminal c that supports the point-to-point mode after receiving the data, it is descrambled through RNTI2, and then reversely processed through the radio bearer, so as to restore the data of the multicast/broadcast service.
  • the RNTI2 may also be associated with the multicast/broadcast service, that is, the terminal c can determine that the data received through the RNTI2 is the data of the above-mentioned multicast/broadcast service.
  • the above-mentioned processing may include one or more of operations such as encryption, integrity protection, fragmentation, encapsulation, and encoding of the data.
  • the reverse processing includes: decryption, integrity verification, assembly, and One or more of encapsulation, decoding, and other operations.
  • the base station When the first RNTI corresponds to the multicast/broadcast service, the base station only needs to send one piece of data, and all terminals configured with the first MAC entity associated with the first RNTI can receive the data, thereby saving air interface bandwidth.
  • the first terminal in the embodiment of the present application is configured with a second MAC entity, and the second MAC entity is used to receive information about one or more services other than the multicast/broadcast service. data.
  • the identifier of the logical channel associated with the radio bearer corresponding to the second MAC entity may be the same as the identifier of the logical channel associated with the radio bearer corresponding to the first MAC entity.
  • the base station configures a MAC entity different from the second MAC entity (for example, the first MAC entity) for the multicast/broadcast service, so that the identification of the logical channel used by the multicast/broadcast service has an independent space and avoids the multicast/broadcast
  • the sharing of MAC entities between services and other services results in a limited number of logical channels.
  • the data of the other one or more services in the embodiment of the present application may be: data of other multicast/broadcast services other than the multicast/broadcast service, or data of the unicast service. It can be understood that, for the same terminal, different multicast/multicast service data correspond to different MAC entities.
  • terminal 1 is used to receive data of multicast/multicast service 1 and data of multicast/multicast service 2, then the base station may configure terminal 1 with a first MAC entity for receiving data of multicast/multicast service 1.
  • a second MAC entity is configured for the terminal 1 to receive data of the multicast/multicast service 2.
  • terminal 1 is used to receive data of multicast/multicast service 1 and data of unicast service, then the base station may configure the first MAC entity for terminal 1 to receive data of multicast/multicast service 1, in addition to the terminal 1 Configure the second MAC entity to receive unicast service data.
  • the first MAC entity and the second MAC entity can be used not only to receive data, but also to send data.
  • the method provided in the embodiment of the present application may further include: the base station receives a second request message, which requests the second terminal to join the foregoing multicast/broadcast service.
  • the base station sends the configuration information of the multicast radio bearer to the second terminal.
  • the second terminal may be a terminal different from the first terminal among the terminals 1 to n shown in FIG. 1.
  • the identifier of the first logical channel of the multicast radio bearer mapping is the same as the identifier of the second logical channel
  • the second logical channel is the logical channel associated with the radio bearer corresponding to the second MAC entity
  • the terminal may Use the second MAC entity to receive the data.
  • the data sent by the base station to the terminal through the second MAC entity is data of other services besides the foregoing multicast/broadcast service.
  • the logical channel associated with the radio bearer corresponding to the second MAC entity may refer to: there is a mapping relationship between the radio bearer corresponding to the second MAC entity and the second logical channel, that is, the data transmitted on the radio bearer corresponding to the second MAC entity passes through The second logical channel transmission.
  • a separate MAC entity ie, the first MAC entity
  • the first MAC entity is configured for the multicast/broadcast service so that the logical channel of the multicast/broadcast service can be independent of the MAC entities of other services, avoiding the fact that the multicast/broadcast service is different from other services.
  • the service sharing MAC entity results in a limited number of logical channels.
  • the base station may perform security protection on the multicast/broadcast service data transmitted on the multicast radio bearer, or may not perform security protection on the multicast/broadcast service data transmitted on the multicast radio bearer protect. But whether to securely protect the data of the multicast/broadcast service transmitted on the multicast radio bearer, the processing of the first terminal receiving the data of the multicast/broadcast service transmitted via the multicast radio bearer is different, as follows: Introduce separately:
  • security protection includes encryption protection and/or integrity protection.
  • the encryption protection can be used to encrypt the data of the multicast/broadcast service transmitted between the terminal and the base station to prevent the data of the multicast/broadcast service from being cracked.
  • Integrity protection can be used to protect the integrity of data transmitted between the terminal and the base station, thereby preventing the data of the multicast/broadcast service from being tampered with.
  • the method includes step 701, step 703, and step 705.
  • Step 701 is the same as step 601
  • step 703 is the same as step 602
  • step 704 is the same as step 603.
  • the difference between the embodiment shown in FIG. 7 and the embodiment shown in FIG. 6 is that the embodiment shown in FIG. 7 also includes steps 702 and step 705. Wherein, step 702 is before step 703.
  • step 702 the base station determines not to perform security protection on the data of the multicast/broadcast service.
  • step 702 in the embodiment of the present application can be implemented in the following manner: the base station receives the third indication information from the core network element, and the third indication information is used to indicate the data of the multicast/broadcast service. No security protection is performed. According to the third indication information, the base station determines not to perform security protection on the data of the multicast/broadcast service. If the base station determines that security protection is not performed on the data of the multicast/broadcast service, the base station may configure the multicast radio bearer to not perform security protection.
  • the core network element may send the third indication information to the base station when creating the multicast session of the multicast/broadcast service.
  • the multicast session in the embodiment of the present application may also be referred to as a multicast broadcast session, and the multicast session may be used to transmit multicast/broadcast services.
  • step 702 in the embodiment of the present application can be implemented in the following manner: the base station autonomously determines not to perform security protection on the data of the multicast/broadcast service. Or, the base station determines not to perform security protection on the data of the multicast/broadcast service according to the third indication information. For example, if the base station determines that the security requirement of the multicast/broadcast service data is lower than or equal to the preset security requirement, the base station determines not to perform security protection on the multicast/broadcast service data.
  • the configuration information of the multicast radio bearer sent by the base station to the first terminal in step 703 in the embodiment of the present application includes second indication information, and the second indication information is used for Indicates that the data of the multicast/broadcast service transmitted on the multicast radio bearer does not perform security protection.
  • the second indication information may be carried in the configuration information of the multicast radio bearer (for example, the second indication information is a field in the configuration information of the multicast radio bearer).
  • the second indication information and the multicast radio bearer can also be carried in the same message.
  • the second indication information and the multicast radio bearer can also be carried in a different message, which is not limited in this embodiment of the application. .
  • the base station in the embodiment of the present application may use an explicit manner to indicate to the first terminal that the data of the multicast/broadcast service transmitted on the multicast radio bearer does not perform security protection.
  • the base station sends second indication information to the first terminal.
  • the base station may also use an implicit manner to indicate to the first terminal that the data of the multicast/broadcast service transmitted on the multicast radio bearer does not perform security protection.
  • the first terminal may determine that the data of the multicast/broadcast service transmitted on the multicast radio bearer does not perform security protection.
  • the base station does not send the security parameter corresponding to the multicast/broadcast service to the first terminal, so the first terminal can also determine that the data of the multicast/broadcast service transmitted on the multicast radio bearer does not perform security protection.
  • Step 705 The first terminal determines that the data of the multicast/broadcast service transmitted on the multicast radio bearer does not perform security protection.
  • step 705 in the embodiment of the present application can be implemented in the following manner: the first terminal determines, according to the second indication information, that the data of the multicast/broadcast service transmitted on the multicast radio bearer has not performed security protection.
  • step 705 in the embodiment of the present application can be implemented in the following manner: the first terminal does not receive the security parameter corresponding to the multicast/broadcast service, then the first terminal determines that the data transmitted on the multicast radio bearer The data of the multicast/broadcast service is not secured.
  • step 705 in the embodiment of the present application can be implemented in the following manner: the first terminal negotiates with the base station or predefines the protocol to predefine that the data of the multicast/broadcast service transmitted on the multicast radio bearer does not perform security protection, Then the first terminal may also determine that the data of the multicast/broadcast service transmitted on the multicast radio bearer does not perform security protection.
  • the base station may not send the second indication information to the first terminal.
  • step 705 and step 704 in the embodiment of the present application are performed in no particular order. It is understandable that if the second indication information is carried in the configuration information of the multicast radio bearer, or the second indication information and the configuration information of the multicast radio bearer are carried in the same message, the first terminal establishes the multicast radio bearer Afterwards, it can be determined that the data of the multicast/broadcast service transmitted on the multicast radio bearer has not performed security protection. If the first terminal receives the second indication information after completing the establishment of the multicast radio bearer, step 705 is located after step 704.
  • step 702 may also be located after step 703.
  • the method provided in the embodiment of the present application may also include: when there is a multicast radio bearer between the first terminal and the base station:
  • Step 706 The base station sends the multicast/broadcast service data to the first terminal on the multicast radio bearer.
  • the first terminal receives the data of the multicast/broadcast service on the multicast radio bearer.
  • the base station when the base station receives the data for the multicast/broadcast service, it sends the data of the multicast/broadcast service on the multicast radio bearer, so as to access one or more of the multicast/broadcast service.
  • the terminal (including the first terminal) can receive multicast/broadcast service data.
  • the method includes step 801, step 803, and step 805.
  • Step 801 is the same as step 601
  • step 803 is the same as step 602
  • step 804 is the same as step 603.
  • step 802 is before step 803.
  • step 802 the base station determines to perform security protection on the data of the multicast/broadcast service.
  • step 802 in the embodiment of the present application can be implemented in the following manner: the base station receives the fifth indication information from the core network element (for example, SMF network element, M-SMF network element), and the fifth The instruction information is used to instruct to perform security protection on the data of the multicast/broadcast service.
  • the base station determines to perform security protection on the data of the multicast/broadcast service according to the fifth instruction information.
  • the core network element may send the fifth indication information to the base station when creating the multicast session.
  • step 802 in the embodiment of the present application can be implemented in the following manner:
  • the base station autonomously determines to perform security protection on the data of the multicast/broadcast service. For example, if the base station determines that the security requirement of the multicast/broadcast service data is higher than or equal to the preset security requirement, the base station determines to perform security protection on the multicast/broadcast service data.
  • the base station determines to perform security protection on the data of the multicast/broadcast service according to the fifth indication information.
  • the configuration information of the multicast radio bearer sent by the base station to the first terminal in step 803 in the embodiment of the present application further includes fourth indication information, and the fourth indication information is used to indicate transmission on the multicast radio bearer.
  • the data of the multicast/broadcast service has been secured or needs to be secured.
  • the fourth instruction information can be carried in the configuration information of the multicast radio bearer.
  • the fourth instruction information can also be sent to the first terminal through separate signaling, or the fourth instruction information can also be combined with the group.
  • the configuration information of the broadcast radio bearer is carried in the same message, which is not limited in the embodiment of the present application.
  • the base station may use an explicit manner to indicate to the first terminal that the data of the multicast/broadcast service transmitted on the multicast radio bearer performs security protection. For example, the base station sends fourth indication information to the first terminal.
  • the base station may also use an implicit manner to indicate to the first terminal that the data of the multicast/broadcast service transmitted on the multicast radio bearer performs security protection.
  • the base station sends security parameters corresponding to the multicast/broadcast service to the first terminal, so that the first terminal can also determine that the data on the multicast radio bearer used to send the multicast/broadcast service performs security protection.
  • the fourth indication information may be one or more of an encryption protection indication and/or an integrity protection indication.
  • the encryption protection instruction is used to instruct the data of the multicast/broadcast service transmitted on the multicast radio bearer to perform encryption processing.
  • the integrity protection indication is used to instruct the data of the multicast/broadcast service transmitted on the multicast radio bearer to perform integrity protection.
  • Step 805 The first terminal determines that the data of the multicast/broadcast service transmitted on the multicast radio bearer has performed security protection.
  • step 805 in the embodiment of the present application can be implemented in the following manner: the first terminal determines, according to the fourth indication information, that the data of the multicast/broadcast service transmitted on the multicast radio bearer has performed security protection.
  • step 805 in the embodiment of the present application can be implemented in the following manner: the first terminal receives the security parameter corresponding to the multicast/broadcast service, then the first terminal determines the group to be transmitted on the multicast radio bearer The data of the broadcasting/broadcasting service has been secured.
  • step 805 in the embodiment of the present application can be implemented in the following manner: the first terminal negotiates with the base station or pre-defines the protocol, and the base station performs security protection on the data of the multicast/broadcast service, then the first terminal can also determine The data of the multicast/broadcast service transmitted on the multicast radio bearer has been secured.
  • the base station may omit the step of sending the fourth indication information to the first terminal.
  • step 805 and step 804 in the embodiment of the present application are performed in no particular order. It is understandable that if the fourth indication information is carried in the configuration information of the multicast radio bearer, or the fourth indication information and the configuration information of the multicast radio bearer are carried in the same message, the first terminal establishes the multicast radio bearer After that, it can be determined that the data of the multicast/broadcast service transmitted on the multicast radio bearer has performed security protection. If the first terminal receives the fourth indication information after configuring the multicast radio bearer, step 805 is performed after step 804.
  • the action of performing security protection on the multicast/broadcast service data transmitted on the multicast radio bearer in the embodiment of the present application may be performed by the UPF network element or the base station, which is not limited in the embodiment of the present application.
  • the method provided in the embodiment of the present application further includes:
  • Step 806 The base station determines a security parameter corresponding to the multicast/broadcast service.
  • the security parameter includes a security key and/or a security algorithm used for security protection.
  • the security parameter is used to perform data on the multicast/broadcast service. safety protection.
  • the security parameter may include a security key for encrypting data of a multicast/broadcast service and/or an encryption algorithm for determining the security key.
  • the security parameters may also include integrity keys and/or integrity algorithms for integrity protection of multicast/broadcast service data. Integrity can be used to protect the integrity of data transmitted between the first terminal and the base station.
  • step 806 can be implemented in the following manner: the base station receives the security parameters corresponding to the multicast/broadcast service from the core network element. In this way, the base station can determine the security parameters corresponding to the multicast/broadcast service.
  • one or more security parameters are configured at the base station. The base station determines the security parameter corresponding to the multicast/broadcast service from one or more security parameters. For example, the base station can select one of one or more security parameters as the security parameter corresponding to the multicast/broadcast service. Or the base station may select the security parameter associated with the multicast/broadcast service from one or more security parameters as the security parameter corresponding to the multicast/broadcast service, which is not limited in the embodiment of the present application.
  • the first terminal can also directly receive the same security parameter from the core network element.
  • the security parameter can also be received by the base station from the core network element. It is then sent to the first terminal, which is not limited in the embodiment of the present application.
  • Step 807 The base station sends security parameters corresponding to the multicast/broadcast service to the first terminal.
  • the first terminal receives the security parameter corresponding to the multicast/broadcast service.
  • Step 808 The base station obtains the data of the multicast/broadcast service after security protection according to the security parameters.
  • step 808 in the embodiment of the present application can be implemented in the following manner: the base station performs security protection on the data of the multicast/broadcast industry according to the security parameters, and obtains the data of the multicast/broadcast service after security protection.
  • the process for the base station to securely protect data in the multicast/broadcast industry according to the security parameters can be referred to the description of the prior art, which will not be repeated in this embodiment.
  • the base station performs integrity protection on the data of the multicast/broadcast service according to the integrity key.
  • the base station encrypts the data of the multicast/broadcast service according to the encryption key.
  • Step 809 The base station sends the secured multicast/broadcast service data to the first terminal on the multicast radio bearer.
  • the first terminal receives security protected multicast/broadcast service data from the base station on the multicast radio bearer.
  • Step 810 The first terminal obtains the multicast/broadcast service data according to the security parameters and the security-protected multicast/broadcast service data.
  • the first terminal has security parameters corresponding to the multicast/broadcast service.
  • the security parameter corresponding to the multicast/broadcast service may be sent to the first terminal by the base station or core network element or application layer device (for example, the application server corresponding to the multicast/broadcast service).
  • the method provided in this embodiment of the present application may further include before step 809: the base station sends the security parameter to the first terminal.
  • the first terminal receives the security parameter from the base station, and the security parameter is used for the first terminal to obtain the multicast/broadcast service data transmitted on the multicast radio bearer.
  • the first terminal may decrypt the encrypted multicast/broadcast service data from the base station according to the encryption key.
  • the first terminal can verify the integrity of the decrypted multicast/broadcast service data according to the integrity key.
  • FIG. 9 shows a method for configuring radio resources provided by an embodiment of the present application, and the method includes:
  • Step 901 The base station receives a first request message, where the first request message is used to request the first terminal to join the multicast/broadcast service.
  • Step 902 The base station sends the configuration information of the first MAC entity to the first terminal according to the quality of service QoS flow information of the multicast/broadcast service.
  • the first terminal receives the configuration information of the first MAC entity from the base station.
  • the configuration information of the first MAC entity is used to configure the MAC entity corresponding to the multicast/broadcast service for the first terminal.
  • the first MAC entity is used to receive multicast/broadcast service data.
  • the first MAC entity is shared by multiple terminals that have joined the multicast/broadcast service, and the multiple terminals that have joined the multicast/broadcast service include the first terminal.
  • the MAC entity corresponding to the multicast/broadcast service refers to: the terminal receives the data of the multicast/broadcast service through the first MAC entity.
  • the base station may configure the first MAC entity corresponding to the multicast/broadcast service for each terminal in the communication group through step 902, so that each terminal in the communication group Each terminal can use the respective first MAC entity to receive multicast/broadcast service data from the base station.
  • Step 903 The first terminal configures the first MAC entity of the first terminal according to the configuration information of the first MAC entity.
  • the configuration information of the first MAC entity includes sixth indication information, and the sixth indication information is used to indicate that the first MAC entity is used to transmit data of the multicast/broadcast service.
  • the first terminal can determine, according to the sixth indication information, that the first MAC entity is used to transmit the data of the multicast/broadcast service.
  • the method provided in the embodiment of the present application may further include: the base station configures a second MAC entity for the first terminal.
  • the second MAC entity is used to send data other than the data of the multicast/broadcast service to the terminal.
  • the base station configures a separate MAC entity (ie, the first MAC entity) for the multicast/broadcast service so that the logical channel of the multicast/broadcast service can be independent of the logical channels of other services.
  • the MAC entity of other services is different from the first MAC entity, which can avoid the limitation of the number of logical channels caused by the sharing of the MAC entity between the multicast/broadcast service and other services.
  • the configuration information of the first MAC entity in the embodiment of the present application further includes a first RNTI, the first RNTI corresponding to a multicast/broadcast service or the first RNTI corresponding to the first terminal.
  • the first RNTI corresponding to the multicast/broadcast service can be understood as: the first RNTI is: for the multicast/broadcast service or the first RNTI is: the temporary identifier allocated for the multicast session of the multicast/broadcast service, For example, it may be a multicast wireless network temporary identifier (Group-Radio Network Temporary Identifier, G-RNTI).
  • G-RNTI Group-Radio Network Temporary Identifier
  • the first MAC entity is shared by one or more terminals that join the multicast/broadcast service.
  • the base station allocates a G-RNTI for each multicast session (multicast/broadcast service), so that each multicast session can be independently scheduled, which can avoid the limitation of the number of radio bearers causing a base station to The number of supported multicast/broadcast services is limited, and it can also avoid limiting the QoS level that the multicast/broadcast service can support.
  • the first RNTI corresponds to the multicast/broadcast service.
  • the correspondence between the first RNTI and the first terminal can be understood as: the base station allocates the RNTI to the first terminal. It should be understood that for the first terminal that receives the multicast/broadcast service data in a point-to-point manner, the first RNTI corresponds to the first terminal.
  • the first RNTI when the first RNTI corresponds to the first terminal, the first RNTI may be further associated with the multicast/broadcast service, that is, the first RNTI is associated with the multicast/broadcast service of the first terminal.
  • the first terminal may also determine the multicast/broadcast service used for transmission by the first MAC entity associated with the first RNTI according to the first RNTI.
  • the base station may allocate a first RNTI to the multicast/broadcast service of the first terminal, so that a multicast/broadcast service can be uniquely determined according to the first RNTI.
  • the first RNTI is different from the RNTI used by the terminal to receive unicast services, and also different from the RNTI used by the terminal to receive other multicast/broadcast services.
  • the first RNTI corresponds to the multicast/broadcast service.
  • the first RNTI corresponds to the first terminal. For example, taking one or more terminals as terminal 1, terminal 2, terminal 3, and terminal 4 as an example, if terminal 1, terminal 2 receives multicast/broadcast service data in PTM mode, the base stations are terminal 1 and terminal 2, respectively
  • the sent configuration information of the first MAC entity includes the first RNTI corresponding to the multicast/broadcast service.
  • the configuration information of the first MAC entity sent by the base station for the terminal 3 includes the first RNTI corresponding to the terminal 3. If the terminal 4 receives multicast/broadcast service data in a point-to-point manner, the configuration information of the first MAC entity sent by the base station for the terminal 4 includes the first RNTI corresponding to the terminal 4.
  • the method provided in this embodiment of the present application may further include before step 902: the base station determines the reception mode supported by the first terminal.
  • the receiving mode is point-to-point or point-to-multipoint.
  • the base station determines to use PTM or PTP mode to send multicast/broadcast service data according to the signal quality of the first terminal and the number of terminals receiving the multicast/broadcast service.
  • PTM or PTP mode to send multicast/broadcast service data according to the signal quality of the first terminal and the number of terminals receiving the multicast/broadcast service.
  • the method provided in the embodiment of the present application may further include: the base station receives a second request message, which requests the second terminal to join the multicast/broadcast service.
  • the configuration information of the third MAC entity sent by the base station to the second terminal includes the identifier of the multicast radio bearer, the third MAC entity is associated with a second RNTI, and the second RNTI corresponds to the multicast/broadcast service or Corresponding to the second terminal.
  • the base station configures the multicast radio bearer for the first terminal, and indicates to the first terminal whether the data of the multicast/broadcast radio bearer performs security protection.
  • the embodiment shown in FIG. 6 or FIG. 7 or FIG. 8 can be combined with the embodiment shown in FIG. 9 to form a new embodiment. That is, in the embodiment shown in FIG. 6 or FIG. 7 or FIG. 8, the base station may also perform step 901 to step 903.
  • the embodiment shown in FIG. 9 can be used as a separate embodiment, and its main purpose is to configure the first MAC entity for the first terminal by the base station.
  • the embodiment shown in FIG. 9 can be combined with the embodiment shown in FIG. 6 or FIG. 7 or FIG. 8 to form a new embodiment, in other words
  • the base station may also perform the steps performed by the base station in the embodiment shown in FIG. 6 or FIG. 7 or FIG. 8.
  • the first terminal may also perform the steps performed by the first terminal in the embodiment shown in FIG. 6 or FIG. 7 or FIG. Steps performed by the base station.
  • the base station determines that both the multicast radio bearer and the first MAC entity need to be configured for the first terminal, the base station can combine the configuration information of the multicast radio bearer and the configuration information of the first MAC entity It is carried in the same message and sent to the first terminal.
  • the identifier of the chip in the first terminal is the identifier of the first terminal.
  • the terminal that has joined the multicast/broadcast service includes the first terminal.
  • the chip in the first terminal means that the terminal that has joined the multicast/broadcast service includes the first terminal.
  • FIG. 10 shows a specific embodiment of a method for configuring a radio bearer in an embodiment of the present application, and the method includes:
  • Step 1001 The terminal 1 (for example, a TV) sends a request message 1 to an SMF network element, and correspondingly, the SMF network element receives the request message 1 from the terminal 1.
  • the request message 1 requests the terminal 1 to join (Join) the multicast/broadcast service.
  • the request message 1 may carry the multicast address corresponding to the multicast/broadcast service.
  • the request message 1 may also carry the source address corresponding to the multicast/broadcast service.
  • the request message 1 in the case that the terminal 1 has the identifier of the multicast/broadcast service, the request message 1 carries the identifier of the multicast/broadcast service and the identifier of the terminal 1.
  • the identification of the terminal 1 carried in the request message 1 is convenient for the SMF network element to identify the terminal to be added to the multicast/broadcast service.
  • the multicast address and/or source address corresponding to the multicast/broadcast service are used to identify the corresponding multicast/broadcast service.
  • the request message 1 may be an IGMP message
  • step 1001 may be implemented in the following manner: the terminal 1 sends an IGMP message to the UPF network element, and the IGMP message requests the terminal 1 to join the multicast/broadcast service.
  • the request message 1 from the terminal 1 is sent to the SMF network element through the UPF network element.
  • the terminal 1 sends a request message 1 to the UPF network element through a user having a PDU session with the UPF network element.
  • the request message 1 may be a PDU session modification request message.
  • the request message 1 can be carried in the NAS message.
  • the terminal 1 uses a non-access stratum (NAS) message to carry the request message 1
  • NAS non-access stratum
  • the terminal 1 can use the request message 1
  • the identifier of the multicast/broadcast service is sent to the network (SMF network element), or the terminal 1 sends the multicast address and optional source address corresponding to the multicast/broadcast service to identify the multicast/broadcast service.
  • the TV sends a request message 1 to the SMF network element through the RG.
  • the request message 1 is used to request the multicast service of the network element corresponding to DNN1 in the DN.
  • the request message 1 carries DNN1, and the SMF network element sends the get message to the UDM network element.
  • the acquisition message carries DNN1, then the UDM network element can determine according to the pre-configuration information that the network element corresponding to DNN1 provides the multicast service.
  • Step 1002 The SMF network element obtains the policy and charging control (PCC) rule corresponding to the multicast/broadcast service.
  • PCC policy and charging control
  • the PCC rule corresponding to the multicast service includes at least one of the following: description information of one or more multicast service streams, QoS information of each multicast service stream, and the QoS of the multicast service stream
  • the information includes at least one of the maximum bandwidth requirement of the multicast service flow, the ARP of the multicast service flow, and the 5QI of the multicast service flow.
  • step 1002 in the embodiment of the present application can be implemented in the following manner: the SMF network element sends message 2 to the PCF network element, and correspondingly, the PCF network element receives message 2 from the SMF network element.
  • This message 2 is used to request the PCC rule corresponding to the multicast/broadcast service.
  • the message 2 carries the identifier of the multicast/broadcast service, or the multicast address or source address of the multicast/broadcast service.
  • the PCF network element obtains the PCC rule corresponding to the multicast/broadcast service according to the multicast/broadcast service identifier carried in message 2, or the multicast address or source address of the multicast/broadcast service, and then the PCF network element sends the message to the SMF network
  • the element sends the PCC rules corresponding to the multicast/broadcast service. It is understandable that the PCF network element has PCC rules corresponding to the multicast/broadcast service.
  • the SMF network element sends the identifier of the multicast/broadcast service to the PCF network element so that the PCF network element can group
  • the identifier of the broadcast/broadcast service obtains the PCC rule corresponding to the multicast/broadcast service.
  • the SMF network element sends the multicast address and optional source address to the PCF network element so that the PCF network can The element obtains the PCC rule corresponding to the multicast/broadcast service according to the multicast address and the optional source address.
  • step 1002 in the embodiment of the present application can be implemented in the following manner: the SMF network element has PCC rules corresponding to the multicast/broadcast service, and the SMF network element determines that the terminal 1 is added to the multicast/broadcast service At this time, the PCC rules corresponding to the multicast/broadcast service can be obtained from the SMF network element. In this case, the SMF network element can omit the process of sending message 2 to the PCF network element.
  • the PCC rule corresponding to the multicast/broadcast service in the SMF network element can be configured in advance by the PCF network element to the SMF network element. For example, when the PCF network element generates the PCC rule corresponding to the multicast/broadcast service, it can actively configure the PCC rule corresponding to the multicast/broadcast service to the SMF network element.
  • Step 1003 The SMF network element obtains information about the multicast session corresponding to the multicast/broadcast service.
  • the information of the multicast session includes: the identifier of the multicast session, the information of each multicast QoS flow of the multicast session, and the description information of the multicast QoS flow.
  • the information of the multicast QoS flow is referred to the foregoing.
  • the description information of the QoS flow can be at least one of the destination address (ie, multicast address) of the QoS flow, the source address, the destination and source port number, and the protocol type of the data packet.
  • the description information of the QoS flow can also be Application ID, or the description information of the QoS flow can also be the ID of the policy control rule (that is, the ID corresponds to the description information of all service flows in the PCC rule) or the ID of the packet filter in the policy control rule (the ID of the packet filter) ID and optional PCC rule ID), which is not limited in the embodiment of the present application.
  • the SMF network element sends QFI and QOS parameters to the base station.
  • the base station accessed by the terminal 1 has created a multicast session for the multicast/broadcast service
  • the SMF network element obtains the foregoing multicast from the SMF network element or MCF network element that created the multicast session.
  • Information about the session For example, the SMF network element that creates the multicast session can save the identifier of the multicast session, the identifier of the base station, the identifier of the multicast/broadcast service, and the identifier of the SMF network element to a storage unit (such as UDM), and the SMF network element can store it from the storage unit.
  • a storage unit such as UDM
  • the unit (such as UDM) obtains the identifier of the SMF network element that created the multicast session, and obtains the multicast session information from the SMF network element that created the multicast session.
  • the SMF network element may obtain the MCF network element that created the multicast session according to the identifier of the base station, and obtain the multicast session information from the MCF network element.
  • the PCF network element saves the multicast session information, so when the SMF network element obtains the PCC rules corresponding to the multicast/broadcast service from the PCF network element, the PCF network element can also provide the SMF network element with the multicast session information information.
  • Step 1004 The SMF network element sends a request message 3 to the base station.
  • the base station receives the request message 3 from the SMF network element.
  • the request message 3 is used to request the base station to add the terminal 1 to the multicast/broadcast service (or, to join the multicast session corresponding to the multicast/broadcast service).
  • the request message 3 carries the identification of the terminal and the identification of the multicast/broadcast service.
  • the request message 3 carries the identification of the terminal and the multicast address and source address of the multicast/broadcast service.
  • the request message 3 carries the identifier of the multicast session corresponding to the multicast/broadcast service.
  • the request message 3 may also carry the identifier of the protocol data unit (PDU) session of the terminal 1, so that the base station associates the multicast session of the multicast/broadcast service with the PDU session of the terminal 1.
  • PDU protocol data unit
  • the request message 3 also includes a NAS message sent by the SMF network element to the terminal 1.
  • the NAS message includes the identifier of the multicast/broadcast service, the multicast address corresponding to the multicast/broadcast service, and optional Source address so that the terminal 1 can associate the multicast radio bearer with the multicast/broadcast service.
  • the NAS message is also used to indicate that the terminal successfully joins the multicast/broadcast service. It is understandable that the identifier of the multicast/broadcast service may be allocated by the SMF network element or the UPF network element for the multicast/broadcast service. After that, the SMF network element provides the identifier of the multicast/broadcast service to the base station and the terminal 1.
  • step 1004 in the embodiment of the present application may be implemented in the following manner: the SMF network element sends a request message 3 to the AMF network element that provides services for the terminal 1. Then the AMF network element base station sends the request message 3. Specifically, the AMF network element sends the request message 3 on the N2 signaling connection corresponding to the terminal 1, so that the base station can determine the terminal 1 based on the N2 signaling connection. Specifically, the N2 signaling connection corresponding to terminal 1 includes the identification of the N2 signaling connection allocated by the base station to the terminal 1 and the identification of the N2 signaling connection allocated to the terminal 1 by the AMF network element. The base station determines the N2 based on the above identification. The signaling connects to the corresponding terminal 1.
  • Step 1005 The base station adds the terminal 1 to the multicast/broadcast service.
  • the base station has already created a multicast session for the multicast/broadcast service.
  • the base station obtains the information from the core network element (such as SMF network element or MCF network element) that created the multicast session
  • the QoS flow information of the multicast session includes the QFI of the QoS flow of the multicast session and the QoS parameters corresponding to the QFI.
  • the base station determines the multicast radio bearer that needs to be created for the multicast/broadcast service according to the QoS information of the QoS flow of the multicast/broadcast service corresponding to the multicast session. For example, the base station maps different QoS flows to different multicast radio bearers or the same multicast radio bearer.
  • Step 1006 When the terminal 1 joins the multicast/broadcast service, the base station may generate configuration information of the multicast radio bearer according to the multicast radio bearer determined when the multicast session is created.
  • the configuration information of the multicast radio bearer is used to configure the terminal 1 to receive the multicast radio bearer of the multicast/broadcast service.
  • Step 1007 The base station sends configuration information of the multicast radio bearer to the terminal 1.
  • the terminal 1 receives the configuration information of the multicast radio bearer from the base station.
  • the configuration information of the multicast radio bearer includes multicast indication information (corresponding to the first indication information in the foregoing embodiment).
  • the multicast radio bearer configuration information sent by the base station to the terminal 1 includes multicast indication information, which is used to indicate that the multicast radio bearer is used to receive data of the multicast/broadcast service.
  • SRB signaling radio bearer
  • DRB data radio bearer
  • the configuration information of the multicast radio bearer indicates that the multicast radio bearer does not need to perform security protection.
  • the multicast radio bearer does not need to perform security protection can be understood as: the PDCP corresponding to the multicast radio bearer does not need to perform security protection.
  • any one of the following methods may be used to indicate that the PDCP corresponding to the multicast radio bearer does not require encryption and integrity protection:
  • Method 1 The radio bearer used for multicast/broadcast services is not encrypted by default
  • the configuration information of the radio bearer includes Service Data Adaptation Protocol (SDAP) configuration information.
  • SDAP Service Data Adaptation Protocol
  • the SDAP configuration information in the radio bearer configuration information is used to associate the radio bearer with the PDU session.
  • the SDAP configuration information includes the PDU session identifier corresponding to the radio bearer.
  • all radio bearers of a PDU session either all support encryption or all of them do not support encryption.
  • the radio bearers belonging to the same PDU session cannot partially support encryption and some do not.
  • the multicast radio bearer configuration information in order to support the non-encryption of the multicast radio bearer used to send the multicast/broadcast service, when the multicast radio bearer configuration information is used to configure the multicast radio bearer of the multicast/broadcast service, the multicast radio bearer
  • the SDAP configuration information in the configuration information does not include the PDU session identifier, that is, when the multicast radio bearer is not associated with the PDU session, the multicast radio bearer does not perform encryption and integrity protection by default.
  • the configuration information indicates that the type of the multicast radio bearer configured by the configuration information is a multicast type. At this time, it may also be assumed that the multicast radio bearer does not perform encryption and integrity protection. It is understandable that the non-encryption and integrity protection of the multicast radio bearer can be replaced with: the multicast/broadcast service data transmitted on the multicast radio bearer is not encrypted and integrity protected.
  • the configuration information of the multicast radio bearer is also used to instruct to associate the multicast radio bearer with the multicast/broadcast service.
  • the SDAP configuration information includes the identifier of the multicast/broadcast service. In this way, when the terminal 1 receives data from the multicast radio bearer, the data can be associated with the corresponding multicast/broadcast service.
  • the configuration information of the multicast radio bearer includes second indication information, where the second indication information is used to indicate that the multicast radio bearer does not perform encryption and integrity protection.
  • the multicast radio bearer configuration information sent by the base station to the terminal 1 includes multicast indication information, which is used to indicate that the multicast radio bearer is used to receive data for multicast/broadcast services, that is, multicast indication information (corresponding to The foregoing first indication information) is used to indicate that the type of the multicast radio bearer configured by the configuration information is a multicast type.
  • the SDAP configuration information of the multicast radio bearer may include the PDU session identifier, so as to associate the multicast radio bearer with the PDU session.
  • the configuration information of the multicast radio bearer in the second method may be used to instruct to associate the multicast radio bearer with the multicast/broadcast service.
  • the SDAP configuration information in the configuration information of the multicast radio bearer includes indication information for indicating that the multicast radio bearer is associated with the multicast/broadcast service.
  • the SDAP configuration information carries the identifier of the multicast/broadcast service.
  • the configuration information of the multicast radio bearer indicates that the multicast radio bearer needs to perform security protection.
  • the need to perform security protection for the multicast radio bearer can be understood as: the PDCP corresponding to the multicast radio bearer needs to perform security protection.
  • any one of the following methods may be used to indicate that the PDCP corresponding to the multicast radio bearer requires encryption and integrity protection:
  • the configuration information on the multicast radio bearer includes fourth indication information, and the fourth indication information is used to indicate that the multicast radio bearer needs to perform security protection.
  • the terminal 1 receives the security parameters corresponding to the multicast/broadcast service
  • the terminal 1 determines that the multicast radio bearer used to transmit the multicast/broadcast service has performed security protection.
  • the multicast radio bearer The configuration information includes the identifier of the multicast/broadcast service, so that the terminal 1 can learn from the configuration information of the multicast radio bearer that the multicast radio bearer is used to send the data of the multicast/broadcast service, or the above security parameters are included in In the configuration information of the multicast radio bearer.
  • the base station may also include the QFI mapped to the multicast QoS service of the multicast radio bearer in the configuration information of the multicast radio bearer.
  • the terminal 1 can perform QFI verification on the data received on the multicast radio bearer according to the QFI of the multicast QoS service.
  • the QFI mapped to the multicast QoS service of the multicast radio bearer may be carried in the SDAP configuration information in the configuration information of the multicast radio bearer.
  • the base station uses the RRC connection established between the terminal 1 and the base station to send the configuration information of the multicast radio bearer.
  • the configuration information of the multicast radio bearer is carried in the RRC message sent by the base station to the terminal 1, and the RRC message includes the multicast radio bearer's configuration information. Configuration information.
  • the base station sends the NAS message to the terminal 1. If the request message 1 sent by the terminal 1 in step 1001 is an IGMP message, then according to the NAS message and the configuration information of the multicast radio bearer, the terminal 1 can associate the multicast/broadcast service with the corresponding multicast radio bearer.
  • Step 1008 The base station sends a response message to the SMF network element.
  • the SMF network element receives the response message from the base station.
  • step 1008 may be implemented in the following manner: the base station sends the response message to the SMF network element through the AMF network element serving the terminal 1.
  • the response message may also carry indication information used to indicate whether the base station has successfully added the terminal 1 to the multicast/broadcast service. If the base station does not successfully join the terminal 1 to the multicast/broadcast service, the base station may also send a reason value to the SMF network element for unsuccessfully adding the terminal 1 to the multicast/broadcast service.
  • FIG. 11 shows a specific embodiment of another multicast configuration radio bearer method provided by an embodiment of the present application.
  • the difference between this method and the method shown in FIG. 10 is that as shown in FIG. 11
  • the method includes:
  • Steps 1101 to 1103 are the same as steps 1001 to 1003, and will not be repeated here.
  • the SMF network element is also obtained from the core network element that created the multicast session or from the application network element (which can be obtained from other network elements, such as PCF network element/NEF network element from application network element Obtaining) obtains the security parameters of the multicast session, including the security algorithm used in the multicast session, the security key used in the multicast session, and so on.
  • the SMF network element may use the security parameters of the multicast session as the parameters of the multicast/broadcast service.
  • Step 1104 The SMF network element sends a request message 3 to the base station, and correspondingly, the base station receives the request message 3 from the SMF network element.
  • the request message 3 is used to request the terminal 1 to join the multicast/broadcast service.
  • the security key of the multicast/broadcast service may also be carried in step 1104 of the embodiment of the present application.
  • the request message 3 may also include performing encryption and/or the multicast/broadcast service.
  • the security algorithm used for integrity protection For example, the security algorithm includes an encryption algorithm and/or an integrity protection algorithm.
  • the SMF network element may instruct the base station to perform encryption and/or integrity protection on the multicast/multicast service in the request message 3.
  • the request message 3 includes an encryption protection instruction and/or an integrity protection instruction.
  • the encryption protection instruction is used to indicate to encrypt the data of the multicast/broadcast service.
  • the integrity protection indication is used to indicate the integrity protection of the data of the multicast/multicast service.
  • the request message 3 does not include the above instructing the base station to encrypt and/or integrity protect the multicast/multicast service, and the core network element that creates the multicast session for the multicast/broadcast service will The security key and/or the security algorithm used to perform encryption and/or integrity protection on the multicast/broadcast service are sent to the base station.
  • the core network element may instruct the base station to encrypt and/or protect the integrity of the multicast/multicast service, so that the base station may also determine to encrypt and/or protect the data of the multicast/broadcast service. Data integrity protection for multicast/multicast services.
  • Steps 1105 to 1108 are the same as steps 1005 to 1008, and will not be repeated here.
  • the core network element will also send the security parameters corresponding to the multicast/broadcast service to the base station so that the base station can transfer the group corresponding to the multicast/broadcast service.
  • the broadcast radio bearer is configured for security protection.
  • the core network element also needs to configure the base station with a security algorithm for encryption and/or integrity protection corresponding to the multicast radio bearer.
  • the base station can indicate to the terminal 1 that the data transmitted on the multicast radio bearer needs to perform security protection in the following manner.
  • Method 3 The configuration information of the multicast radio bearer includes fourth indication information, and the fourth indication information is used to indicate that the multicast radio bearer needs to perform security protection. In this way, after receiving the configuration information of the multicast radio bearer, the terminal 1 determines that the subsequent data transmitted on the multicast radio bearer has performed security protection.
  • the configuration information of the multicast radio bearer includes an integrity indicator, which is used to indicate that the integrity protection of the multicast radio bearer has been performed. If the multicast radio bearer needs to perform encryption, the configuration information of the multicast radio bearer includes an encryption protection instruction. The encryption protection indication is used to indicate that the multicast radio bearer has been encrypted. If the multicast radio bearer needs to perform encryption and integrity protection, the configuration information of the multicast radio bearer includes an encryption protection instruction and an integrity protection instruction. At the same time, if the multicast radio bearer needs to perform encryption and/or integrity protection, the configuration information of the multicast radio bearer may also include a security algorithm corresponding to encryption and/or integrity protection.
  • the configuration information of a multicast radio bearer in the multicast session may include the security algorithm (multicast session shared security algorithm), or, the configuration information of all radio bearers corresponding to the multicast session may include the security algorithm (multicast session The security algorithm or shared security algorithm may not be shared), or the security parameters may be included in the configuration information of the multicast radio bearer and be carried by all the multicast radios of all the multicast sessions (that is, the multicast/broadcast service) shared.
  • the multicast radio bearer needs to perform encryption, which can be understood as: the data transmitted on the multicast radio bearer needs to perform encryption protection.
  • the base station sends the NAS message sent by the SMF network element to the terminal 1 to the terminal 1.
  • the NAS message may include the encryption key of the multicast session and/or the security parameters used for integrity protection . If the NAS message carries the encryption key for the multicast session and/or the security parameters used for integrity protection, the terminal 1 will use the encryption key and/or the integrity key and group for integrity protection in the NAS message.
  • the security algorithm in the configuration information of the broadcast radio bearer, the encryption protection instruction and the integrity protection instruction in the configuration information of the multicast radio bearer determine whether the multicast/multi-service data needs to be decrypted, how to decrypt it, and whether it is complete Verification, and how to perform integrity verification.
  • the terminal 1 also determines the encryption key corresponding to the multicast/broadcast service and/or the integrity used for integrity protection according to the multicast/broadcast service identifier in the configuration information of the multicast radio bearer and the multicast session identifier in the NAS message. Sex key.
  • security parameters used for encryption and integrity protection of the multicast/broadcast service data are different from the security parameters used for encryption and integrity protection for other data streams of the PDU session.
  • Method 4 The base station sends the security parameters corresponding to the multicast/broadcast radio bearer to the terminal 1.
  • the terminal 1 receives the security parameters corresponding to the multicast/broadcast radio bearer, it can be determined that the data on the multicast radio bearer used to transmit the multicast/broadcast service has performed security protection.
  • the configuration information of the multicast radio bearer includes the identifier of the multicast/broadcast service corresponding to the multicast radio bearer, so that the terminal 1 can associate the security parameters of the multicast/broadcast service with the multicast radio bearer.
  • the SDAP configuration information of the multicast radio bearer can also include the PDU session identifier, so as to associate the multicast radio bearer with the PDU session, but even if the multicast radio bearer is associated with the PDU session, it can also be associated with the PDU session.
  • Other non-multicast radio bearers of the PDU session use different encryption strategies and integrity protection strategies.
  • each network element such as a base station, a first terminal, etc.
  • each network element includes a hardware structure and/or software module corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • the base station and the first terminal may be divided into functional units according to the foregoing method example.
  • each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit. It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • the method of the embodiment of the present application is described above in conjunction with FIG. 6 to FIG. 11, and the communication device provided in the embodiment of the present application for performing the foregoing method is described below.
  • a communication device provided in an embodiment of the present application can execute the above-mentioned method for configuring a radio bearer and a method executed by a base station in the method for configuring a radio resource.
  • the communication device may execute the method executed by the first terminal in the method for configuring a radio bearer and the method for configuring a radio resource in the foregoing embodiment.
  • FIG. 12 shows a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication device includes: a communication unit 101 and a processing unit 102.
  • the communication unit 101 is used to support the communication device to perform the steps of sending or receiving information.
  • the processing unit 102 is used to support the communication device to perform information processing steps.
  • the communication device may be a base station, or the communication device may be a component (for example, a chip) applied to a base station, and the communication unit 101 is used for the communication device to communicate with an external network element.
  • the processing unit 102 is configured to perform signal processing operations of the base station in the foregoing embodiment.
  • the communication unit 101 is configured to perform the sending action performed by the base station in step 602 and the receiving action performed by the base station in step 601 in the foregoing embodiment.
  • the processing unit 102 is used to perform the processing actions performed by the base station in step 702 in the foregoing embodiment
  • the communication unit 101 is used to perform the sending actions performed by the base station in step 706 in the foregoing embodiment.
  • the processing unit 102 is configured to perform the processing actions performed by the base station in step 802, step 806, and step 808 in the foregoing embodiment, and the communication unit 101 is configured to perform step 806 and step 806 in the foregoing embodiment.
  • the communication unit 101 is further configured to perform the sending action performed by the base station in step 902 and the receiving action performed by the base station in step 901 in the foregoing embodiment.
  • the communication device may be a base station, or the communication device may be a component (for example, a chip) applied to a base station, and the communication unit 101 is used for the communication device to communicate with an external network element, for example, to perform the above-mentioned embodiment The signal transceiving operation of the base station.
  • the processing unit 102 is configured to perform signal processing operations of the base station in the foregoing embodiment.
  • the communication unit 101 is configured to support the communication device to perform the sending action performed by the base station in step 902 and the receiving action performed by the base station in step 901 of the foregoing embodiment.
  • the communication unit 101 is further configured to support the communication device to perform the sending action performed by the base station in step 602 and the receiving action performed by the base station in step 601 of the foregoing embodiment.
  • the processing unit 102 is further configured to support the communication device to perform the processing actions performed by the base station in step 702 in the foregoing embodiment
  • the communication unit 101 is further configured to support the communication device to perform the processing actions in the foregoing embodiment.
  • the processing unit 102 is also used to support the communication device to perform the processing actions performed by the base station in step 802, step 806, and step 808 in the foregoing embodiment, and the communication unit 101 is also used to support the communication.
  • the device executes step 806 in the foregoing embodiment and the sending action performed by the base station in step 809.
  • the communication device may be a terminal, or the communication device may be a component (for example, a chip) applied to a terminal, and the communication unit 101 is used for the communication device to communicate with an external network element (for example, a base station), for example , Execute the signal transceiving operation of the first terminal in the foregoing embodiment.
  • the processing unit 102 is configured to support the communication device to perform the signal processing operation of the first terminal in the foregoing embodiment.
  • the communication unit 101 is configured to support the communication device to perform the receiving action performed by the first terminal in step 602 of the foregoing embodiment.
  • the processing unit 102 is configured to perform the processing actions performed by the first terminal in step 603 supporting the above-mentioned embodiment of the communication device.
  • the processing unit 102 is further configured to support the communication device to execute the processing action performed by the first terminal in step 705 in the foregoing embodiment.
  • the communication unit 101 is further configured to support the communication device to execute the receiving action performed by the first terminal in step 706 in the above-mentioned embodiment.
  • the processing unit 102 is used to support the communication device to perform step 805 and the processing actions performed by the first terminal in step 810 in the foregoing embodiment
  • the communication unit 101 is used to support the communication device to perform the foregoing Step 807 in the embodiment and the receiving action performed by the first terminal in step 809.
  • the communication unit 101 is further configured to support the communication device to perform the receiving action performed by the first terminal in step 902 of the foregoing embodiment.
  • the processing unit 102 is further configured to support the communication device to execute the processing action executed by the first terminal in step 903 of the foregoing embodiment.
  • the communication device may be a first terminal, and the communication unit 101 is used for the communication device to communicate with an external network element (for example, a base station), for example, to perform the signal transceiving operation of the first terminal in the foregoing embodiment.
  • the processing unit 102 is configured to perform the signal processing operation of the first terminal in the foregoing embodiment.
  • the communication unit 101 is configured to perform the receiving action performed by the first terminal in step 902 of the foregoing embodiment.
  • the processing unit 102 is configured to support the communication device to execute the receiving action performed by the first terminal in step 903 in the foregoing embodiment.
  • the communication unit 101 is further configured to support the communication device to perform the receiving action performed by the first terminal in step 602 of the foregoing embodiment.
  • the processing unit 102 is further configured to support the communication device to execute the processing actions performed by the first terminal in step 603 of the foregoing embodiment.
  • the processing unit 102 is further configured to support the communication device to execute the processing action performed by the first terminal in step 705 in the foregoing embodiment.
  • the communication unit 101 is further configured to support the communication device to execute the receiving action performed by the first terminal in step 706 in the above-mentioned embodiment.
  • the processing unit 102 is used to support the communication device to perform step 805 and the processing actions performed by the first terminal in step 810 in the foregoing embodiment
  • the communication unit 101 is used to support the communication device to perform the foregoing Step 807 in the embodiment and the receiving action performed by the first terminal in step 809.
  • the communication device may further include: a storage unit.
  • the processing unit 102, the communication unit 101, and the storage unit are connected by a communication bus.
  • the storage unit may include one or more memories, and the memories may be devices for storing programs or data in one or more devices or circuits.
  • the storage unit may exist independently, and is connected to the processing unit 102 of the communication device through a communication bus.
  • the storage unit can also be integrated with the processing unit.
  • the communication device can be used in communication equipment, circuits, hardware components, or chips.
  • the communication device may be a chip in the base station/first terminal in the embodiment of the present application.
  • the communication unit 101 may be an input or output interface, pin or circuit, or the like.
  • the storage unit may store a computer execution instruction for sending the method on the base station/first terminal side, so that the processing unit 102 executes the method on the base station/first terminal side in the foregoing embodiment.
  • the storage unit may be a register, cache, or RAM, etc.
  • the storage unit may be integrated with the processing unit 102; the storage unit may be ROM or other types of static storage devices that can store static information and instructions, and the storage unit may be connected to the processing unit 102. Independence.
  • the embodiment of the present application provides a communication device.
  • the communication device includes one or more modules for implementing the above steps 601 to 602, or step 702, step 706, or step 802, step 806, step 808, and step 809.
  • the one or more modules can be combined with the above 601-step 602, or step 702, step 706, or step 802, step 806, step 808, and step 809, or step 901 corresponds to the steps executed by the base station in step 902.
  • the embodiment of the present application provides a communication device.
  • the communication device includes one or more modules for implementing the above steps 602 to 603 or steps 705 to 706, or step 805, step 810, step 807, step 809, Or the method executed by the first terminal in step 902 and step 903, the one or more modules can be combined with the above-mentioned 602-step 603 or step 705 to step 706, or step 805, step 810, step 807, step 809, or step 902 corresponds to the steps executed by the first terminal in step 903.
  • FIG. 13 shows a schematic diagram of a possible logical structure of the communication device involved in the foregoing embodiment, and the communication device may be the sending device in the foregoing embodiment. Or the communication device may be the receiving device in the above embodiment.
  • the communication device includes: a processing module 112 and a communication module 113.
  • the processing module 112 is used to control and manage the actions of the communication device, and the communication module 113 is used to execute the steps of message or data processing on the side of the communication device.
  • the communication device may further include a storage module 111 for storing program codes and data of the communication device.
  • the communication device may be a base station, or the communication device may be a component (for example, a chip) applied to a base station, and the communication module 113 is used for the communication device to communicate with an external network element.
  • the processing module 112 is configured to perform signal processing operations of the base station in the foregoing embodiment.
  • the communication module 113 is configured to perform the sending action performed by the base station in step 602 and the receiving action performed by the base station in step 601 in the foregoing embodiment.
  • the processing module 112 is used to execute the processing action performed by the base station in step 702 in the above embodiment
  • the communication module 113 is used to execute the sending action performed by the base station in step 706 in the above embodiment.
  • the processing module 112 is used to perform the processing actions performed by the base station in step 802, step 806, and step 808 in the foregoing embodiment, and the communication module 113 is used to perform step 806 and step 806 in the foregoing embodiment.
  • the communication module 113 is further configured to perform the sending action performed by the base station in step 902 and the receiving action performed by the base station in step 901 in the foregoing embodiment.
  • the communication device may be a base station, or the communication device may be a component (for example, a chip) applied to a base station, and the communication module 113 is used for the communication device to communicate with an external network element, for example, to perform the above-mentioned embodiment The signal transceiving operation of the base station.
  • the processing module 112 is configured to perform signal processing operations of the base station in the foregoing embodiment.
  • the communication module 113 is used to support the communication device to perform the sending action performed by the base station in step 902 and the receiving action performed by the base station in step 901 of the foregoing embodiment.
  • the communication module 113 is further configured to support the communication device to perform the sending action performed by the base station in step 602 and the receiving action performed by the base station in step 601 of the foregoing embodiment.
  • the processing module 112 is also used to support the communication device to perform the processing actions performed by the base station in step 702 in the foregoing embodiment
  • the communication module 113 is also used to support the communication device to perform the processing actions in the foregoing embodiment.
  • the processing module 112 is also used to support the communication device to perform the processing actions performed by the base station in step 802, step 806, and step 808 in the foregoing embodiment, and the communication module 113 is also used to support the communication.
  • the device executes step 806 in the foregoing embodiment and the sending action performed by the base station in step 809.
  • the communication device may be a terminal, or the communication device may be a component (for example, a chip) applied to a terminal, and the communication module 113 is used for the communication device to communicate with an external network element (for example, a base station), for example , Execute the signal transceiving operation of the first terminal in the foregoing embodiment.
  • the processing module 112 is configured to support the communication device to perform the signal processing operation of the first terminal in the foregoing embodiment.
  • the communication module 113 is configured to support the communication device to perform the receiving action performed by the first terminal in step 602 of the foregoing embodiment.
  • the processing module 112 is configured to perform the processing actions performed by the first terminal in step 603 of the foregoing embodiment of the communication device.
  • the processing module 112 is further configured to support the communication device to execute the processing action executed by the first terminal in step 705 in the foregoing embodiment.
  • the communication module 113 is also used to support the communication device to execute the receiving action performed by the first terminal in step 706 in the foregoing embodiment.
  • the processing module 112 is used to support the communication device to perform step 805 and the processing actions performed by the first terminal in step 810 in the foregoing embodiment
  • the communication module 113 is used to support the communication device to perform the foregoing Step 807 in the embodiment and the receiving action performed by the first terminal in step 809.
  • the communication module 113 is further configured to support the communication device to perform the receiving action performed by the first terminal in step 902 of the foregoing embodiment.
  • the processing module 112 is further configured to support the communication device to execute the processing actions performed by the first terminal in step 903 of the foregoing embodiment.
  • the communication device may be a first terminal, and the communication module 113 is used for the communication device to communicate with an external network element (for example, a base station), for example, to perform the signal transceiving operation of the first terminal in the foregoing embodiment.
  • the processing module 112 is configured to perform the signal processing operation of the first terminal in the foregoing embodiment.
  • the communication module 113 is configured to perform the receiving action performed by the first terminal in step 902 of the foregoing embodiment.
  • the processing module 112 is configured to support the communication device to execute the receiving action performed by the first terminal in step 903 in the foregoing embodiment.
  • the communication module 113 is further configured to support the communication device to perform the receiving action performed by the first terminal in step 602 of the foregoing embodiment.
  • the processing module 112 is further configured to support the communication device to execute the processing actions performed by the first terminal in step 603 of the foregoing embodiment.
  • the processing module 112 is further configured to support the communication device to execute the processing action executed by the first terminal in step 705 in the foregoing embodiment.
  • the communication module 113 is also used to support the communication device to execute the receiving action performed by the first terminal in step 706 in the foregoing embodiment.
  • the processing module 112 is used to support the communication device to perform step 805 and the processing actions performed by the first terminal in step 810 in the foregoing embodiment
  • the communication module 113 is used to support the communication device to perform the foregoing Step 807 in the embodiment and the receiving action performed by the first terminal in step 809.
  • the processing module 112 may be a processor or a controller, for example, a central processing unit, a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic devices, transistor logic devices, Hardware components or any combination thereof. It can implement or execute various exemplary logical blocks, modules, and circuits described in conjunction with the disclosure of the present invention.
  • the processor may also be a combination for realizing computing functions, for example, including a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and so on.
  • the communication module 113 may be a communication interface, a transceiver, a transceiver circuit or an interface circuit, etc.
  • the storage module 111 may be a memory.
  • the processing module 112 is the processor 41 or the processor 45
  • the communication module 113 is the transceiver 43
  • the storage module 111 is the memory 42
  • the communication device involved in this application may be the communication device shown in FIG. 5.
  • FIG. 14 is a schematic structural diagram of a chip 150 provided by an embodiment of the present application.
  • the chip 150 includes one or more (including two) processors 1510 and a communication interface 1530.
  • the chip 150 further includes a memory 1540.
  • the memory 1540 may include a read-only memory and a random access memory, and provides operation instructions and data to the processor 1510.
  • a part of the memory 1540 may also include a non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • the memory 1540 stores the following elements, executable modules or data structures, or their subsets, or their extended sets:
  • the corresponding operation is executed by calling the operation instruction stored in the memory 1540 (the operation instruction may be stored in the operating system).
  • One possible implementation is that the structures of the chips used by the base station and the first terminal are similar, and different devices can use different chips to realize their respective functions.
  • the processor 1510 controls the operations of the sending device and the receiving device.
  • the processor 1510 may also be referred to as a central processing unit (CPU).
  • the memory 1540 may include a read-only memory and a random access memory, and provides instructions and data to the processor 1510.
  • a part of the memory 1540 may also include a non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • the memory 1540, the communication interface 1530, and the memory 1540 are coupled together through a bus system 1520, where the bus system 1520 may include a power bus, a control bus, and a status signal bus in addition to a data bus.
  • various buses are marked as the bus system 1520 in FIG. 14.
  • the above communication unit may be an interface circuit or communication interface of the device for receiving signals from other devices.
  • the communication unit is an interface circuit or communication interface used by the chip to receive signals or send signals from other chips or devices.
  • the communication unit may include a sending unit and a receiving unit.
  • the sending unit is used to send signals to other devices.
  • the receiving unit is used to receive signals from other devices.
  • the methods disclosed in the foregoing embodiments of the present application may be applied to the processor 1510 or implemented by the processor 1510.
  • the processor 1510 may be an integrated circuit chip with signal processing capabilities. In the implementation process, the steps of the foregoing method can be completed by hardware integrated logic circuits in the processor 1510 or instructions in the form of software.
  • the aforementioned processor 1510 may be a general-purpose processor, a digital signal processing (digital signal processing, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (field-programmable gate array, FPGA), or Other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processing
  • ASIC application specific integrated circuit
  • FPGA field-programmable gate array
  • Other programmable logic devices discrete gates or transistor logic devices, discrete hardware components.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in combination with the embodiments of the present invention may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory 1540, and the processor 1510 reads the information in the memory 1540, and completes the steps of the foregoing method in combination with its hardware.
  • the communication interface 1530 is used to perform the receiving and sending steps of the base station and the first terminal in the embodiments shown in FIG. 6 to FIG. 9.
  • the processor 1510 is configured to execute the processing steps of the base station and the first terminal in the embodiments shown in FIG. 6 to FIG. 9.
  • the instructions stored in the memory for execution by the processor may be implemented in the form of a computer program product.
  • the computer program product can be written in the memory in advance, or it can be downloaded and installed in the memory in the form of software.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • Computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • computer instructions may be transmitted from a website, computer, server, or data center through a cable (such as Coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) to transmit to another website site, computer, server or data center.
  • a cable such as Coaxial cable, optical fiber, digital subscriber line (DSL)
  • wireless such as infrared, wireless, microwave, etc.
  • the computer-readable storage medium may be any available medium that can be stored by a computer or a data storage device such as a server or a data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk, SSD).
  • the embodiment of the present application also provides a computer-readable storage medium.
  • the methods described in the foregoing embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If implemented in software, the functions can be stored on a computer-readable medium or transmitted on a computer-readable medium as one or more instructions or codes.
  • Computer-readable media may include computer storage media and communication media, and may also include any media that can transfer a computer program from one place to another.
  • the storage medium may be any target medium that can be accessed by a computer.
  • the computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that is targeted to carry or use instructions or data structures.
  • the required program code is stored in the form of and can be accessed by the computer.
  • any connection is properly termed a computer-readable medium. For example, if you use coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology (such as infrared, radio and microwave) to transmit software from a website, server or other remote source, then coaxial cable, fiber optic cable , Twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of the medium.
  • DSL digital subscriber line
  • wireless technology such as infrared, radio and microwave
  • Magnetic disks and optical disks as used herein include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks and blu-ray disks, in which disks usually reproduce data magnetically, and optical disks use lasers to optically reproduce data. Combinations of the above should also be included in the scope of computer-readable media.
  • a computer-readable storage medium is provided, and instructions are stored in the computer-readable storage medium. When the instructions are executed, the functions of the base station as shown in FIG. 6 are realized.
  • the functions of the base station in FIG. 7 to FIG. 8 and FIG. 9 can also be realized.
  • a computer-readable storage medium stores instructions. When the instructions are executed, the functions of the first terminal as shown in FIG. 6 are realized.
  • the computer-readable storage medium when the instructions are executed, may also implement the functions of the first terminal as shown in FIGS. 7-9.
  • a computer-readable storage medium is provided, and instructions are stored in the computer-readable storage medium. When the instructions are executed, the functions of the base station as shown in FIG. 9 are realized.
  • the functions of the base station shown in Figs. 6 to 8 can also be realized.
  • a computer-readable storage medium stores instructions. When the instructions are executed, the functions of the first terminal as shown in FIG. 9 are realized.
  • the function of the first terminal shown in Figs. 6 to 8 can also be realized.
  • the embodiment of the present application also provides a computer program product.
  • the methods described in the foregoing embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If it is implemented in software, it can be fully or partially implemented in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the above computer program instructions are loaded and executed on the computer, the procedures or functions described in the above method embodiments are generated in whole or in part.
  • the above-mentioned computer may be a general-purpose computer, a special-purpose computer, a computer network, a base station, a terminal, or other programmable devices.
  • a computer program product including instructions.
  • the computer program product includes instructions. When the instructions are executed, the functions of the base station as shown in FIG. 6 are realized.
  • the computer program product including the instructions can also implement the functions of the base station as shown in FIGS. 7-9.
  • a computer program product including instructions.
  • the computer program product includes instructions. When the instructions are executed, the functions of the first terminal as shown in FIG. 6 are realized.
  • the computer program product including the instructions may also implement the functions of the first terminal as shown in FIGS. 7-9.
  • a computer program product including instructions.
  • the computer program product includes instructions. When the instructions are executed, the functions of the base station as shown in FIG. 9 are realized.
  • the computer program product including the instructions may also implement the functions of the base station in FIGS. 6-8.
  • a computer program product including instructions.
  • the computer program product includes instructions. When the instructions are executed, the functions of the first terminal as shown in FIG. 9 are realized.
  • the computer program product including the instructions may also implement the functions of the first terminal shown in FIGS. 6-8.
  • a chip is provided.
  • the chip is applied to a first terminal.
  • the chip includes at least one processor and a communication interface.
  • the communication interface is coupled to the at least one processor. The function of the terminal.
  • the processor in the chip is also used to run instructions to implement the functions of the first terminal in FIGS. 7-9.
  • a chip is provided.
  • the chip is used in a base station.
  • the chip includes at least one processor and a communication interface.
  • the communication interface is coupled to the at least one processor. .
  • the processor in the chip is also used to run instructions to implement the functions of the base station as shown in Figs. 7-9.
  • a chip is provided.
  • the chip is applied to a first terminal.
  • the chip includes at least one processor and a communication interface.
  • the communication interface is coupled to the at least one processor. The function of a terminal.
  • the processor in the chip is also used to run instructions to implement the functions of the first terminal shown in Figs. 6-8.
  • a chip is provided.
  • the chip is applied to a first terminal.
  • the chip includes at least one processor and a communication interface.
  • the communication interface is coupled to the at least one processor. Function.
  • the processor in the chip is also used to run instructions to implement the functions of the base station as shown in Figs. 6-8.
  • An embodiment of the present application provides a communication system.
  • the communication system includes a base station and a first terminal.
  • the base station is used to perform the steps performed by the base station in FIG. 6 to FIG. Steps performed by the first terminal.
  • the base station is further used to perform the steps performed by the base station in FIG. 9, and the first terminal is used to perform the steps performed by the first terminal in FIG. 9.
  • An embodiment of the present application provides a communication system that includes a base station and a first terminal, where the base station is used to perform the steps performed by the base station in FIG. 9 and the first terminal is used to perform the steps performed by the first terminal in FIG. 9 step.
  • the base station is further used to perform the steps performed by the base station in FIGS. 6 to 8, and the first terminal is also used to perform the steps performed by the first terminal in FIGS. 6 to 8.

Landscapes

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

Abstract

本申请实施例提供一种配置无线承载的方法、装置及系统，涉及通信技术领域，通过建立终端和基站之间用于接收组播/广播业务的组播无线承载，可以实现降低基站处理组播业务的数据复杂度。该方案包括：基站接收第一请求消息，第一请求消息用于请求将第一终端加入组播/广播业务；基站根据组播/广播业务的服务质量QoS流信息，向第一终端发送组播无线承载的配置信息；其中，配置信息用于配置组播无线承载，组播无线承载用于向已加入组播/广播业务的终端传输组播/广播业务的数据，已加入组播/广播业务的终端包括第一终端。

Description

一种配置无线承载的方法、装置及系统
本申请要求于2020年03月27日提交国家知识产权局、申请号为202010228271.8、申请名称为“一种配置无线承载的方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域，尤其涉及一种配置无线承载的方法、装置及系统。
背景技术
随着移动互联网的发展，视频业务占数据业务的比重越来越高，视频业务对移动网络的冲击越来越大，通过空口组播优化视频业务传输可以减少视频业务对移动网络的冲击。虽然第3代移动通信技术(3rd-Generation mobile communication technology，3G)网络和第4代移动通信技术(the 4 Generation mobile communication technology，4G)网络支持组播业务。
现有技术中，基站可以采用单播传输(即点到点，Point to point)或组播传输(即点到多点，Point to Multipoint)的方式向终端发送组播业务(Multicast Service)。例如，当基站向多个终端发送组播业务的数据，该多个终端中存在一部分终端采用单播传输，而另一部分终端采用组播传输时，对于采用单播传输的终端，基站生成针对单播传输的组播业务的数据，对于采用组播传输的终端，基站生成针对组播传输的组播业务的数据。即组播业务的同一个数据，针对支持不同传输方式的终端，基站需要生成不同类型的数据，这样会增加基站处理组播业务的数据复杂度。
发明内容
本申请实施例提供一种配置无线承载的方法、装置及系统，通过建立终端和基站之间用于接收组播/广播业务的组播无线承载，可以实现降低基站处理组播业务的数据复杂度。
为了实现上述目的，本申请实施例提供如下技术方案：
第一方面，本申请实施例提供一种配置无线承载的方法，该方法包括：基站接收用于请求将第一终端加入组播/广播业务的第一请求消息。基站根据该组播/广播业务的服务质量QoS流信息，向第一终端发送组播无线承载的配置信息。其中，配置信息用于配置组播无线承载，该组播无线承载用于向已加入组播/广播业务的终端传输组播/广播业务的数据，已加入组播/广播业务的终端包括第一终端。
本申请实施例提供一种配置无线承载的方法，该方法中基站在接收到用于请求将第一终端加入组播/广播业务的第一请求消息，便可以根据组播/广播业务的服务质量QoS流信息，为第一终端配置组播无线承载的配置信息。这样便于第一终端建立与基站之间的用于传输组播/广播业务的组播无线承载。后续在基站向第一终端发送的组播/广播业务的数据时，基站便可以利用该组播无线承载向第一终端发送组播/广播业务的数据。无论基站向第一终端发送该组播/广播业务的数据时采用点到多点(组播)方式 还是点到点(单播)方式，基站均可以利用该组播无线承载发送组播/广播业务的数据，因此可以简化基站处理组播业务的数据复杂度。此外，还可以实现基站从单播传输到组播传输的灵活切换。
在一种可能的实现方式中，本申请实施例提供的方法包括：基站接收用于请求将第二终端加入组播/广播业务的第二请求消息。基站向第二终端发送配置信息。已加入组播/广播业务的终端还包括第二终端。
在一种可能的实现方式中，组播无线承载的配置信息包括第一指示信息。该第一指示信息用于指示配置信息用于配置的无线承载的类型为组播无线承载，或者该第一指示信息用于指示配置信息配置的组播无线承载的类型为组播类型。这样便于第一终端确定该组播无线承载的类型。
在一种可能的实现方式中，组播无线承载的配置信息还包括：该组播/广播业务的标识，或该组播/广播业务关联的组播会话的标识。这样便于第一终端确定该组播无线承载与该组播/广播业务或该组播/广播业务关联的组播会话关联。
在一种可能的实现方式中，本申请实施例中的组播无线承载用于传输该组播/广播业务的数据。
在一种可能的实现方式中，本申请实施例中的组播无线承载的配置信息包括以下一个或多个：组播无线承载的标识，和组播无线承载映射的第一逻辑信道的标识。
在一种可能的实现方式中，本申请实施例提供的方法还包括：基站确定对该组播/广播业务的数据不执行安全保护。相应的，组播无线承载的配置信息包括第二指示信息，该第二指示信息用于指示对在组播无线承载上传输的组播/广播业务的数据不执行安全保护。这样便于第一终端确定通过该组播无线承载传输的组播/广播业务的数据未执行安全保护，因此对通过该无线承载接收到的组播/广播业务的数据无须执行解密操作。
在一种可能的实现方式中，基站确定对该组播/广播业务的数据不执行安全保护，包括：基站接收来自核心网网元的用于指示对该组播/广播业务的数据不执行安全保护的第三指示信息。基站根据第三指示信息，确定对该组播/广播业务的数据不执行安全保护。这样便于基站根据第三指示信息对该组播/广播业务的数据不执行安全保护操作。
在一种可能的实现方式中，本申请实施例提供的方法还包括：基站确定对该组播/广播业务的数据执行安全保护。相应的，组播无线承载的配置信息还包括第四指示信息，该第四指示信息用于指示在组播无线承载上传输的组播/广播业务的数据已执行安全保护。通过第四指示信息，便于第一终端确定组播/广播业务的数据需要执行解密处理。
在一种可能的实现方式中，基站确定该组播/广播业务的数据执行安全保护，包括：基站接收来自核心网网元的用于指示对该组播/广播业务的数据执行安全保护的第五指示信息。基站根据第五指示信息，确定对该组播/广播业务的数据执行安全保护。这样便于基站在组播无线承载上传输的该组播/广播业务的数据执行完全保护，提高数据的安全性。
在一种可能的实现方式中，本申请实施例提供的方法还包括：基站接收来自核心网网元的该组播/广播业务对应的安全参数，该安全参数包括安全密钥和/或安全保护所 使用的安全算法，安全算法用于对该组播/广播业务的数据进行安全保护。基站根据安全参数，获得安全保护后的组播/广播业务的数据。基站在组播无线承载上向第一终端发送安全保护后的该组播/广播业务的数据。
在一种可能的实现方式中，本申请实施例提供的方法还包括：基站向第一终端发送安全参数，该安全参数用于第一终端获取在组播无线承载上传输的该组播/广播业务的数据。
在一种可能的实现方式中，本申请实施例提供的方法还包括：基站为第一终端发送第一媒体接入控制MAC实体的配置信息，该第一MAC实体的配置信息用于配置组播/广播业务对应的第一MAC实体。这样便于第一终端利用第一MAC实体以及组播无线承载接收该组播/广播业务对应的数据。
在一种可能的实现方式中，第一MAC实体的配置信息包括第六指示信息，该第六指示信息用于指示第一MAC实体用于传输该组播/广播业务的数据。便于第一终端确定为第一终端配置的第一MAC实体的作用。
在一种可能的实现方式中，第一MAC实体的配置信息包括组播无线承载的标识。便于确定组播无线承载与第一MAC实体关联。
在一种可能的实现方式中，组播无线承载映射的第一逻辑信道的标识与第二逻辑信道的标识相同，该第二逻辑信道为第二MAC实体对应的无线承载关联的逻辑信道，该第二MAC实体用于向终端发送除组播多播业务的数据之外的其他业务的数据。应理解，第二MAC实体用于发送上述组播/广播业务之外的其他业务的数据。
在一种可能的实现方式中，第一MAC实体的配置信息还包括第一无线网络临时标识RNTI，该第一RNTI与上述组播/广播业务对应或第一RNTI与第一终端对应。
在一种可能的实现方式中，上述组播/广播业务通过点到多点(PTM)方式发送时，第一RNTI与组播/广播业务对应。或者，上述组播/广播业务通过点到点方式发送时，第一RNTI与第一终端对应。
在一种可能的实现方式中，第一RNTI与组播/广播业务对应时，第一MAC实体由一个或多个终端共享。
在一种可能的实现方式中，上述第一RNTI与第一终端对应时，还包括：第一RNTI还与该组播/广播业务对应。以便第一终端根据该第一RNTI确定通过该第一MAC实体接收的是该组播/广播业务的数据。应理解，基站为第一终端的该组播/广播业务分配第一RNTI。
在一种可能的实现方式中，本申请实施例提供的方法还包括：基站接收用于将第二终端加入该组播/广播业务的第二请求消息。基站向第二终端发送的无线资源配置信息包括上述组播无线承载的配置信息以及第三MAC实体的配置信息，第三MAC实体的配置信息包括第六指示信息，第三MAC实体的配置信息包括上述组播无线承载的标识，第三MAC实体与第二RNTI关联，该第二RNTI与组播/广播业务对应或与第二终端对应。应理解，当第二RNTI与上述组播/广播业务对应时，第二RNTI与第一RNTI相同，此时，第三MAC实体的配置信息与第一MAC实体的配置信息相同。
第二方面，本申请实施例提供一种配置无线承载的方法，该方法包括：第一终端接收来自基站的组播无线承载的配置信息，该组播无线承载的配置信息用于配置组播/ 广播业务对应的组播无线承载。组播无线承载用于向已加入组播/广播业务的终端传输组播/广播业务的数据，已加入组播/广播业务的终端包括第一终端。第一终端根据组播无线承载的配置信息，配置组播无线承载。
在一种可能的实现方式中，本申请实施例提供的方法还包括：第一终端在该组播无线承载上接收来自基站的该组播/广播业务的数据。
在一种可能的实现方式中，组播无线承载的配置信息包括以下一个或多个：组播无线承载的标识，或，组播无线承载所映射的第一逻辑信道的标识。
在一种可能的实现方式中，组播无线承载的配置信息包括第一指示信息，该第一指示信息用于指示配置信息用于配置的无线承载的类型为组播无线承载。第一终端根据第一指示信息确定组播无线承载的类型为组播类型。
在一种可能的实现方式中，组播无线承载的配置信息还包括：该组播/广播业务的标识，或该组播/广播业务关联的组播会话的标识。
在一种可能的实现方式中，组播无线承载的配置信息包括用于指示在组播无线承载上传输的组播/广播业务的数据未执行安全保护的第二指示信息。第一终端根据第二指示信息，确定在组播无线承载上传输的组播/广播业务的数据未执行安全保护。
在一种可能的实现方式中，第一终端在该组播无线承载上接收来自基站的该组播/广播业务的数据，包括：第一终端在该组播无线承载接收来自基站的未执行安全保护的该组播/广播业务的数据。
在一种可能的实现方式中，组播无线承载的配置信息包括第三指示信息，该第三指示信息用于指示在该组播无线承载上传输的组播/广播业务的数据已执行安全保护。
在一种可能的实现方式中，第一终端在该组播无线承载上接收来自基站的该组播/广播业务的数据，包括：第一终端在改组播无线承载接收来自基站的安全保护的该组播/广播业务的数据。
在一种可能的实现方式中，本申请实施例提供的方法还包括：第一终端接收安全参数，该安全参数用于第一终端获取上述组播/广播业务的数据。第一终端在该组播无线承载上接收经安全保护后的组播/广播业务的数据。第一终端根据安全参数和安全保护后的组播/广播业务的数据，获得组播/广播业务的数据。
在一种可能的实现方式中，第一终端根据第三指示信息或安全参数，确定在该组播无线承载上传输的组播/广播业务的数据执行安全保护。
在一种可能的实现方式中，本申请实施例提供的方法还包括：第一终端接收来自基站的第一媒体接入控制MAC实体的配置信息，该第一MAC实体的配置信息用于配置组播/广播业务对应的MAC实体。第一终端根据第一MAC实体的配置信息，配置该组播/广播业务对应的第一MAC实体。
在一种可能的实现方式中，第一MAC实体的配置信息包括用于指示第一MAC实体用于传输组播/广播业务的第六指示信息。第一终端根据第六指示信息确定第一MAC实体用于传输组播/广播业务的数据。
在一种可能的实现方式中，第一MAC实体的配置信息包括第一MAC实体对应的第一无线网络临时标识RNTI，该第一RNTI与上述组播/广播业务对应或第一RNTI与第一终端对应。
在一种可能的实现方式中，本申请实施例提供的方法还包括：当该组播/广播业务通过点到多点(PTM)方式发送时，第一RNTI与组播/广播业务对应。或者，当该组播/广播业务通过点到点(PTP)方式发送时，第一RNTI与第一终端对应。
在一种可能的实现方式中，第一RNTI与组播/广播业务对应时，第一MAC实体由加入该组播/广播业务的一个或多个终端共享。
在一种可能的实现方式中，上述第一RNTI与第一终端对应时，还包括：第一RNTI还与该组播/广播业务对应。第一终端根据该第一RNTI确定通过该第一MAC实体接收的是该组播/广播业务的数据。应理解，该第一RNTI与第一终端用于接收单播数据的RNTI不同，与第一终端用于接收其他组播/广播业务的数据的RNTI也不同。
在一种可能的实现方式中，第一MAC实体的配置信息包括上述组播无线承载的标识。
在一种可能的实现方式中，第一逻辑信道的标识与第二逻辑信道的标识相同，该第二逻辑信道为第二MAC实体对应的无线承载关联的逻辑信道，该第二MAC实体用于向终端发送数据。应理解，第二MAC实体用于发送除上述组播/广播业务之外的其他业务的数据。
第三方面，本申请实施例提供一种配置无线资源的方法，该方法包括：基站接收用于请求将第一终端加入组播/广播业务的第一请求消息。基站根据组播/广播业务的服务质量QoS流信息，向第一终端发送第一媒体接入控制MAC实体的配置信息。该第一MAC实体的配置信息用于配置组播/广播业务对应的MAC实体。
第三方面中关于第一MAC实体的配置信息的内容可以参考第一方面中的描述，此处不再赘述。
在一种可能的实现方式中，第一MAC实体与第一无线网络临时标识RNTI关联，第一RNTI与组播/广播业务对应或第一RNTI与第一终端对应。
在一种可能的实现方式中，组播/广播业务通过点到多点(PTM)方式发送时，第一RNTI与组播/广播业务对应。或者，组播/广播业务通过点到点方式发送时，第一RNTI与第一终端对应。
在一种可能的实现方式中，第一RNTI与组播/广播业务对应时，该第一MAC实体由加入该组播/广播业务的一个或多个终端共享，一个或多个终端包括第一终端。
应理解，当采用PTM方式发送该组播/广播业务时，该一个或多个终端的第一MAC实体的配置信息相同。当采用PTP方式发送该组播/广播业务时，该一个或多个终端的第一MAC实体的配置信息可以不同，但该一个或多个终端的组播无线承载的配置信息相同。
在一种可能的实现方式中，上述第一RNTI与第一终端对应时，还包括：第一RNTI还与该组播/广播业务对应。便于第一终端根据该第一RNTI确定通过该第一MAC实体接收的是该组播/广播业务的数据。基站为第一终端的该组播/广播业务分配第一RNTI。应理解，该第一RNTI与第一终端用于接收单播数据的RNTI不同，与第一终端用于接收其他组播/广播业务的数据的RNTI也不同。
在一种可能的实现方式中，本申请实施例提供的方法还包括：基站向该第一终端发送组播无线承载的配置信息，组播无线承载的配置信息用于配置组播无线承载，该 组播无线承载用于向已加入组播/广播业务的终端传输组播/广播业务的数据，已加入组播/广播业务的终端包括第一终端。
关于组播无线承载或组播无线承载的配置信息的描述可以参考第一方面中关于组播无线承载或组播无线承载的配置信息的描述，此处不再赘述。
在一种可能的实现方式中，本申请实施例提供的方法还包括：基站确定对组播/广播业务的数据不执行安全保护。相应的，组播无线承载的配置信息包括第二指示信息，该第二指示信息用于指示对在组播无线承载上传输的组播/广播业务的数据不执行安全保护。
在一种可能的实现方式中，基站确定对组播/广播业务的数据不执行安全保护，包括：基站接收来自核心网网元的第三指示信息，该第三指示信息用于指示对组播/广播业务的数据不执行安全保护。基站根据第三指示信息，确定对组播/广播业务的数据不执行安全保护。
在一种可能的实现方式中，本申请实施例提供的方法还包括：基站确定对上述组播/广播业务的数据执行安全保护。相应的，组播无线承载的配置信息还包括第四指示信息，该第四指示信息用于指示在组播无线承载上传输的组播/广播业务的数据已执行安全保护。
在一种可能的实现方式中，基站确定组播/广播业务的数据执行安全保护，包括：基站接收来自核心网网元的第五指示信息，该第五指示信息用于指示对组播/广播业务的数据执行安全保护。基站根据该第五指示信息，确定对组播/广播业务的数据执行安全保护。
在一种可能的实现方式中，本申请实施例提供的方法还包括：基站接收来自核心网网元的组播/广播业务对应的安全参数，安全参数包括安全密钥，和/或，安全保护所使用的安全算法，安全算法用于对组播/广播业务的数据进行安全保护。基站根据安全参数，对组播/广播业的数据进行安全保护，获得安全保护后的组播/广播业务的数据。基站在组播无线承载上向第一终端发送安全保护后的组播/广播业务的数据。
在一种可能的实现方式中，本申请实施例提供的方法还包括：基站向第一终端发送安全参数，该安全参数用于第一终端获取在组播无线承载上传输的组播/广播业务的数据。
在一种可能的实现方式中，本申请实施例提供的方法还包括：基站确定将第二终端加入组播/广播业务。基站向第二终端发送组播无线承载的配置信息，以及第三MAC实体的配置信息，第三MAC实体的配置信息包括组播无线承载的标识，第三MAC实体与第二RNTI关联，第二RNTI与组播/广播业务对应或与第二终端对应。应理解，当第二RNTI与上述组播/广播业务对应时，第二RNTI与第一RNTI相同，此时，第三MAC实体的配置信息与第一MAC实体的配置信息相同。
在一种可能的实现方式中，基站确定将第二终端加入组播/广播业务，包括：基站接收第二请求消息，该第二请求消息请求将第二终端加入组播/广播业务。
第四方面，本申请实施例提供一种配置无线资源的方法，该方法包括：第一终端接收来自基站的第一媒体接入控制MAC实体的配置信息。该第一MAC实体的配置信息用于配置组播/广播业务对应的MAC实体。第一终端根据第一MAC实体的配置信 息，配置第一MAC实体。
在一种可能的实现方式中，第一MAC实体用于接收组播/广播业务的数据，本申请实施例提供的方法还包括：第一终端利用第一MAC实体接收组播/广播业务的数据。
第四方面中关于第一MAC实体的配置信息的内容可以参考第一方面中的描述，此处不再赘述。
在一种可能的实现方式中，第一MAC实体与第一无线网络临时标识RNTI关联，第一RNTI与组播/广播业务对应或第一RNTI与第一终端对应。
在一种可能的实现方式中，组播/广播业务通过点到多点(PTM)方式发送时，第一RNTI与组播/广播业务对应。或者，组播/广播业务通过点到点方式发送时，第一RNTI与第一终端对应。
在一种可能的实现方式中，该第一RNTI与组播/广播业务对应时，该第一MAC实体由加入该组播/广播业务的一个或多个终端共享，该一个或多个终端包括第一终端。
应理解，当采用PTM方式发送该组播/广播业务时，该一个或多个终端的第一MAC实体的配置信息相同。当采用PTP方式发送该组播/广播业务时，该一个或多个终端的第一MAC实体的配置信息可以不同，但该一个或多个终端的组播无线承载的配置信息相同。
在一种可能的实现方式中，上述第一RNTI与第一终端对应时，还包括：第一RNTI还与该组播/广播业务对应。便于第一终端根据该第一RNTI确定通过该第一MAC实体接收的是该组播/广播业务的数据。基站为第一终端的该组播/广播业务分配第一RNTI。应理解，该第一RNTI与第一终端用于接收单播数据的RNTI不同，与第一终端用于接收其他组播/广播业务的数据的RNTI也不同。
在一种可能的实现方式中，本申请实施例提供的方法还包括：第一终端接收来自基站的组播无线承载的配置信息。该组播无线承载的配置信息用于配置组播无线承载。该组播无线承载用于向已加入组播/广播业务的终端传输组播/广播业务的数据，已加入组播/广播业务的终端包括第一终端。第一终端根据组播无线承载的配置信息，为第一终端配置组播无线承载。
关于组播无线承载或组播无线承载的配置信息的描述可以参考第一方面中关于组播无线承载或组播无线承载的配置信息的描述，此处不再赘述。
在一种可能的实现方式中，第一终端通过组播无线承载接收来自基站的组播/广播业务的数据。
在一种可能的实现方式中，组播无线承载的配置信息包括第二指示信息，该第二指示信息用于指示在组播无线承载上传输的组播/广播业务的数据未执行安全保护。第一终端根据第二指示信息确定在组播无线承载上传输的组播/广播业务的数据未执行安全保护。
在一种可能的实现方式中，第一终端利用组播无线承载和第一MAC实体接收未经安全保护的组播/广播的数据。
在一种可能的实现方式中，组播无线承载的配置信息还包括用于指示在组播无线承载上传输的组播/广播业务的数据已执行安全保护的第四指示信息。
在一种可能的实现方式中，第一终端利用组播无线承载和第一MAC实体接收安 全保护的组播/广播的数据。
在一种可能的实现方式中，第一终端接收安全参数，安全参数包括安全密钥，和/或，安全保护所使用的安全算法，安全参数用于对组播/广播业务的数据进行安全保护。第一终端根据安全参数和安全保护后的组播/广播业务的数据，获得组播/广播业务的数据。
在一种可能的实现方式中，第一终端根据第三指示信息或安全参数，确定在组播无线承载上传输的组播/广播业务的数据已执行安全保护。
第五方面，本申请实施例提供一种通信装置，该通信装置可以是基站，也可以是内置于基站内的部件(例如，芯片)。该通信装置可以包括通信单元。该通信装置还可以包括处理单元和存储单元。一种示例，当该通信装置是基站时，该通信单元可以为收发器。该存储单元可以是存储器。该存储单元用于存储指令。处理单元可以为处理器。该处理单元执行该存储单元所存储的指令，以使该基站实现第一方面或第一方面的任意一种可能的实现方式中描述的一种配置无线承载的方法。另一种示例，当该通信装置是内置于基站内的部件(例如，芯片)时，该处理单元可以是处理器，该通信单元可以是通信接口。例如芯片中的通信接口可以为输入/输出接口、管脚或电路等。该处理单元执行存储单元所存储的指令，以使该通信装置实现第一方面或第一方面的任意一种可能的实现方式中描述的一种配置无线承载的方法，该存储单元可以是该芯片内的存储单元(例如，寄存器、缓存等)，也可以是该基站内的位于该芯片外部的存储单元(例如，只读存储器、随机存取存储器等)。
第六方面，本申请实施例提供一种通信装置，该通信装置可以是终端，也可以是内置于终端内的部件(例如，芯片)。该通信装置可以包括通信单元。该通信装置还可以包括处理单元和存储单元。一种示例，当该通信装置是终端时，该通信单元可以为收发器。该存储单元可以是存储器。该存储单元用于存储指令。处理单元可以为处理器。该处理单元执行该存储单元所存储的指令，以使该终端实现第二方面或第二方面的任意一种可能的实现方式中描述的一种配置无线承载的方法。另一种示例，当该通信装置是内置于终端内的部件(例如，芯片)时，该处理单元可以是处理器，该通信单元可以是通信接口。例如芯片中的通信接口可以为输入/输出接口、管脚或电路等。该处理单元执行存储单元所存储的指令，以使该通信装置实现第二方面或第二方面的任意一种可能的实现方式中描述的一种配置无线承载的方法，该存储单元可以是该芯片内的存储单元(例如，寄存器、缓存等)，也可以是该终端内的位于该芯片外部的存储单元(例如，只读存储器、随机存取存储器等)。
第七方面，本申请实施例提供一种通信装置，该通信装置可以是基站，也可以是内置于基站内的部件(例如，芯片)。该通信装置可以包括通信单元。该通信装置还可以包括处理单元和存储单元。一种示例，当该通信装置是基站时，该通信单元可以为收发器。该存储单元可以是存储器。该存储单元用于存储指令。处理单元可以为处理器。该处理单元执行该存储单元所存储的指令，以使该基站实现第三方面或第三方面的任意一种可能的实现方式中描述的一种无线资源的配置方法。另一种示例，当该通信装置是内置于基站内的部件(例如，芯片)时，该处理单元可以是处理器，该通信单元可以是通信接口。例如芯片中的通信接口可以为输入/输出接口、管脚或电路等。 该处理单元执行存储单元所存储的指令，以使该通信装置实现第三方面或第三方面的任意一种可能的实现方式中描述的一种无线资源的配置方法，该存储单元可以是该芯片内的存储单元(例如，寄存器、缓存等)，也可以是该基站内的位于该芯片外部的存储单元(例如，只读存储器、随机存取存储器等)。
第八方面，本申请实施例提供一种通信装置，该通信装置可以是终端，也可以是内置于终端内的部件(例如，芯片)。该通信装置可以包括通信单元。该通信装置还可以包括处理单元和存储单元。一种示例，当该通信装置是终端时，该通信单元可以为收发器。该存储单元可以是存储器。该存储单元用于存储指令。处理单元可以为处理器。该处理单元执行该存储单元所存储的指令，以使该终端实现第四方面或第四方面的任意一种可能的实现方式中描述的一种无线资源的配置方法。另一种示例，当该通信装置是内置于终端内的部件(例如，芯片)时，该处理单元可以是处理器，该通信单元可以是通信接口。例如芯片中的通信接口可以为输入/输出接口、管脚或电路等。该处理单元执行存储单元所存储的指令，以使该通信装置实现第四方面或第四方面的任意一种可能的实现方式中描述的一种无线资源的配置方法，该存储单元可以是该芯片内的存储单元(例如，寄存器、缓存等)，也可以是该终端内的位于该芯片外部的存储单元(例如，只读存储器、随机存取存储器等)。
第九方面，本申请实施例提供一种计算机可读存储介质，计算机可读存储介质中存储有计算机程序或指令，当计算机程序或指令在计算机上运行时，使得计算机执行如第一方面至第一方面的任意一种可能的实现方式中描述的一种配置无线承载的方法。
第十方面，本申请实施例提供一种计算机可读存储介质，计算机可读存储介质中存储有计算机程序或指令，当计算机程序或指令在计算机上运行时，使得计算机执行如第二方面至第二方面的任意一种可能的实现方式中描述的一种配置无线承载的方法。
第十一方面，本申请实施例提供一种计算机可读存储介质，计算机可读存储介质中存储有计算机程序或指令，当计算机程序或指令在计算机上运行时，使得计算机执行如第三方面至第三方面的任意一种可能的实现方式中描述的一种配置无线资源的方法。
第十二方面，本申请实施例提供一种计算机可读存储介质，计算机可读存储介质中存储有计算机程序或指令，当计算机程序或指令在计算机上运行时，使得计算机执行如第四方面至第四方面的任意一种可能的实现方式中描述的一种配置无线资源的方法。
第十三方面，本申请实施例提供一种包括指令的计算机程序产品，当指令在计算机上运行时，使得计算机执行第一方面或第一方面的各种可能的实现方式中描述的一种配置无线承载的方法。
第十四方面，本申请提供一种包括指令的计算机程序产品，当指令在计算机上运行时，使得计算机执行第二方面或第二方面的各种可能的实现方式中描述的一种配置无线承载的方法。
第十五方面，本申请实施例提供一种包括指令的计算机程序产品，当指令在计算机上运行时，使得计算机执行第三方面或第三方面的各种可能的实现方式中描述的一种配置无线资源的方法。
第十六方面，本申请实施例提供一种包括指令的计算机程序产品，当指令在计算机上运行时，使得计算机执行第四方面或第四方面的各种可能的实现方式中描述的一种配置无线资源的方法。
第十七方面，本申请实施例提供一种通信系统，该通信系统包括如下中任一个或多个：第五方面及各种可能的实现方式中描述的通信装置，以及第六方面及第六方面的各种可能的实现方式中描述的通信装置。
在一种可能的实现中，该通信系统还可以包括：核心网网元，用于向基站发送第五指示信息或第三指示信息。
第十八方面，本申请实施例提供一种通信系统，该通信系统包括如下中任一个或多个：第七方面及各种可能的实现方式中描述的通信装置，以及第八方面及第八方面的各种可能的实现方式中描述的通信装置。
在一种可能的实现中，该通信系统还可以包括：核心网网元，用于向基站发送第五指示信息或第三指示信息。
第十九方面，本申请实施例提供一种通信装置，该通信装置包括处理器和存储介质，存储介质存储有指令，指令被处理器运行时，实现如第一方面或第一方面的各种可能的实现方式描述的一种配置无线承载的方法。
第二十方面，本申请实施例提供一种通信装置，该通信装置包括处理器和存储介质，存储介质存储有指令，指令被处理器运行时，实现如第二方面或第二方面的各种可能的实现方式描述的一种配置无线承载的方法。
第二十一方面，本申请实施例提供一种通信装置，该通信装置包括处理器和存储介质，存储介质存储有指令，指令被处理器运行时，实现如第三方面或第三方面的各种可能的实现方式描述的一种配置无线资源的方法。
第二十二方面，本申请实施例提供一种通信装置，该通信装置包括处理器和存储介质，存储介质存储有指令，指令被处理器运行时，实现如第四方面或第四方面的各种可能的实现方式描述的一种配置无线资源的方法。
第二十三方面，本申请提供一种芯片或者芯片系统，该芯片或者芯片系统包括至少一个处理器和通信接口，通信接口和至少一个处理器通过线路互联，至少一个处理器用于运行计算机程序或指令，以进行第一方面至第一方面的任一种可能的实现方式中任一项所描述的一种配置无线承载的方法。
第二十四方面，本申请提供一种芯片或者芯片系统，该芯片或者芯片系统包括至少一个处理器和通信接口，通信接口和至少一个处理器通过线路互联，至少一个处理器用于运行计算机程序或指令，以进行第二方面至第二方面的任一种可能的实现方式中任一项所描述的一种配置无线承载的方法。
第二十五方面，本申请提供一种芯片或者芯片系统，该芯片或者芯片系统包括至少一个处理器和通信接口，通信接口和至少一个处理器通过线路互联，至少一个处理器用于运行计算机程序或指令，以进行第三方面至第三方面的任一种可能的实现方式中任一项所描述的一种配置无线资源的方法。
第二十六方面，本申请提供一种芯片或者芯片系统，该芯片或者芯片系统包括至少一个处理器和通信接口，通信接口和至少一个处理器通过线路互联，至少一个处理 器用于运行计算机程序或指令，以进行第四方面至第四方面的任一种可能的实现方式中任一项所描述的一种配置无线资源的方法。
其中，芯片中的通信接口可以为输入/输出接口、管脚或电路等。
在一种可能的实现中，本申请中上述描述的芯片或者芯片系统还包括至少一个存储器，该至少一个存储器中存储有指令。该存储器可以为芯片内部的存储单元，例如，寄存器、缓存等，也可以是该芯片的存储单元(例如，只读存储器、随机存取存储器等)。
第二十七方面，本申请实施例提供一种通信装置，该通信装置包括处理器，该处理器和存储器耦合，存储器中存储有指令，处理器用于运行指令以实现第一方面或第一方面的各种可能的实现方式中描述的一种配置无线承载的方法。
第二十八方面，本申请实施例提供一种通信装置，该通信装置包括处理器，该处理器和存储器耦合，存储器中存储有指令，处理器用于运行指令以实现第二方面或第二方面的各种可能的实现方式中描述的一种配置无线承载的方法。
第二十九方面，本申请实施例提供一种通信装置，该通信装置包括处理器，该处理器和存储器耦合，存储器中存储有指令，处理器用于运行指令以实现第三方面或第三方面的各种可能的实现方式中描述的一种配置无线资源的方法。
第三十方面，本申请实施例提供一种通信装置，该通信装置包括处理器，该处理器和存储器耦合，存储器中存储有指令，处理器用于运行指令以实现第四方面或第四方面的各种可能的实现方式中描述的一种配置无线资源的方法。
可以理解的是，本申请实施例中第二十七方面～第三十方面描述的存储器可以位于通信装置内部，也可以位于通信装置外部，本申请实施例对此不做限定。
本申请中第二方面至第三十方面及其各种实现方式的有益效果，可以参考第一方面及其各种实现方式中的有益效果分析，此处不再赘述。
附图说明
图1为本申请实施例提供的一种通信系统的架构示意图；
图2a和图2b为本申请实施例提供的一种5G架构示意图；
图3a和图3b为本申请实施例提供的另一种5G架构示意图；
图4a和图4b为本申请实施例提供的一种基站的结构示意图；
图5为本申请实施例提供的一种通信设备的结构示意图；
图6～图8为本申请实施例提供的一种配置无线承载的方法的流程示意图；
图9为本申请实施例提供的一种配置无线资源的方法的流程示意图；
图10为本申请实施例提供的一种配置无线承载的方法的具体实施例；
图11为本申请实施例提供的另一种配置无线承载的方法的具体实施例；
图12为本申请实施例提供的一种通信装置的结构示意图；
图13为本申请实施例提供的另一种通信装置的结构示意图；
图14为本申请实施例提供的一种芯片的结构示意图。
具体实施方式
为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。例如，第 一终端和第二终端仅仅是为了区分不同的终端，并不对其先后顺序进行限定。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
需要说明的是，本申请中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。
本申请实施例描述的系统架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。本申请实施例中以提供的方法应用于NR系统或5G网络中为例进行说明。
如图1所示，为本申请实施例提供的一种通信系统的架构示意图，该通信系统包括：基站10以及与基站10通信的多个终端(例如，终端1、终端2、…、终端n)。其中，n为大于或等于1的整数。多个终端可以接收来自基站10的组播/广播业务的数据。
本申请实施例中的组播/广播业务指：组播业务或广播(broadcast Service)业务，所谓组播业务可以指：某一业务可以针对性地向某个通信群组发送，这样该业务可以被加入同一个通信群组的终端接收到。而广播业务可以指：某个业务可以以广播的方式发送，在广播范围内的多个终端均可以接收到以广播方式发送的该业务，但是并不限定该多个终端属于同一个通信群组。
以多个终端为例，该多个终端可以加入同一个组播/广播业务，换言之多个终端可以接收同一个组播/广播业务，也可以加入不同的组播/广播业务。例如，该多个终端中各个终端加入的组播/广播业务均不相同。本申请实施例中的组播也可以称为多播。
需要说明的是，当多个终端加入的组播业务相同时，该多个终端可以组成一个通信群组(例如，可以称为广播群组或组播群组)，该通信群组中的终端可以同时接收相同数据，即组播/广播业务的数据。
为了使得通信群组中的终端能够更好地接收组播/广播业务的数据，本申请实施例 中基站10可以为该组播/广播业务配置组播无线承载，以及向通信群组中的终端发送该组播无线承载的配置信息。相应地，终端可以根据接收到的组播无线承载的配置信息建立该终端与基站10之间的组播无线承载。然后，基站10可以在该组播无线承载上向终端发送组播/广播业务的数据。
如图1所示，该通信系统还可以包括：核心网网元20，用于向基站10发送第一请求消息或第二请求消息，或者向基站10发送安全参数。
具体的，图1所示通信系统可以为第三代合作伙伴计划(3rd generation partnership project，3GPP)中的通信系统，例如，长期演进(long term evolution，LTE)通信系统，或者，第五代(5th generation，5G)通信系统或者新空口(new radio，NR)通信系统，也可以是非3GPP通信系统，不予限制。
以图1所示的通信系统为5G通信系统为例，如图2a所示，上述核心网网元可以为5G通信系统中的会话管理功能(session management function，SMF)网元，上述基站可以为5G通信系统中的无线接入网(radio access network，RAN)设备。
此外，在图2a所示的通信系统中，除了包括SMF网元和RAN设备之外，该系统还可以包括：接入和移动性管理功能(access and mobility management function，AMF)网元、策略控制功能(policy control function，PCF)网元、会话锚点(PDU session anchor，PSA)(也可以称为用户面功能(user plane function，UPF)网元)、鉴权服务器功能(authentication server function，AUSF)网元、网络切片选择功能(network slice selection function，NSSF)网元、统一数据管理(unified data management，UDM)网元、数据网络(data network，DN)、应用功能(Application function，AF)网元、组播控制功能(Multicast Control Function，MCF)，组播用户面功能(Multicast User Plane Function，MUF)等。
其中，MCF网元可以用于对组播/广播业务进行控制。MCF网元与内容提供商(Content Provider，CP)存在通信接口，以便接收组播业务的信息(例如，组播业务的描述)。MCF网元与PCF存在通信接口，以便为组播业务创建资源。
其中，MUF网元用于传递组播报文，即将从CP接收到的组播报文(即组播/多播业务的数据)发送给下行节点UPF网元。
需要说明的是，CP可以是一种应用功能网元。
可选的，图2a所示的系统中还可以包括中间UPF(Intermediate UPF，I-UPF)网元，用于实现业务流分流。
如图2a所示，终端通过N1接口(简称N1)与AMF网元通信。AMF网元通过N11接口(简称N11)与SMF网元通信。SMF网元通过N4接口(简称N4)与一个或者多个UPF网元通信。一个或多个UPF网元中任意两个UPF网元通过N9接口(简称N9)通信，例如，I-UPF网元和UPF网元之间通过N9接口通信，(R)AN和I-UPF网元之间具有N3接口。UPF网元通过N6接口(简称N6)与AF网元管控的数据网络(data network，DN)通信。
终端通过(R)AN与5G核心网(5G Core，5GC)通信，(R)AN与AMF网元之间通过N2接口(简称N2)通信。SMF网元通过N7接口(简称N7)与PCF网元通信，PCF网元通过N5接口与AF网元通信。(R)AN通过N3接口(简称N3)与 UPF网元通信。任意两个AMF网元之间通过N14接口(简称N14)通信。SMF网元通过N10接口(简称N10)与UDM网元通信。AMF网元通过N12接口(简称N12)与AUSF网元通信。AUSF网元通过N13接口(简称N13)与UDM网元通信。AMF网元通过N8接口(简称N8)与UDM网元通信。
应理解，图2a所示的通信系统架构中，5GC中的控制面网元也可以采用服务化接口进行交互。例如，如图2b所示，AMF网元、SMF网元、UDM网元、或者PCF网元采用服务化接口(service based interface)进行交互。比如，AMF网元对外提供的服务化接口可以为Namf。SMF网元对外提供的服务化接口可以为Nsmf。UDM网元对外提供的服务化接口可以为Nudm。PCF网元对外提供的服务化接口可以为Npcf。应理解，各种服务化接口的名称的相关描述可以参考现有技术中的5G系统架构(5G system architecture)图，在此不予赘述。
需要说明的是，图2a或图2b仅是示例性的给出一个UPF网元、SMF网元。当然，该中可能包括多个UPF网元、SMF网元，如包括SMF网元1和SMF网元2，本申请实施例对此不作具体限定。
需要说明的是，图2a或图2b的(R)AN、AMF网元、SMF网元、UDM网元、UPF网元、PCF网元、鉴权服务功能(authentication server function，AUSF)网元等仅是一个名字，名字对设备本身不构成限定。在5G网络以及未来其它的网络中，(R)AN、AMF网元、SMF网元、UDM网元、UPF网元和PCF网元所对应的网元或实体也可以是其他的名字，本申请实施例对此不作具体限定。例如，该UDM网元还有可能被替换为用户归属服务器(home subscriber server，HSS)或者用户签约数据库(user subscription database，USD)或者数据库实体，等等，在此进行统一说明，后续不再赘述。
图2a或图2b所示的通信系统中，MCF网元可以集成到PCF网元中，MUF网元可集成到UPF网元中，本申请实施例对此不做限定。
在该图3a所示的架构中，可以通过为终端服务的SMF网元、AMF网元为组播/广播业务分配资源。也可以通过专门的SMF网元、AMF网元为组播/广播业务分配资源，即，该SMF网元/AMF网元专门负责组播/广播业务的管理和控制，为了更清晰描述方案，图3a中的M-SMF和M-AMF是负责组播业务的管理和控制的SMF网元和AMF网元。当然，在实际部署时，该M-SMF网元和M-AMF网元也可以为终端进行服务，只是，在管理组播/广播业务时，该M-SMF网元/M-AMF网元不一定服务于正在接收该组播/广播业务的终端。
其中，AMF网元、SMF网元、UPF网元是为终端服务的AMF网元、SMF网元和UPF网元。UPF网元仅负责终端单播业务的数据传递，若终端接入组播/广播业务，组播/广播业务经过MUF网元、M-UPF网元、(R)AN发送给终端。M-SMF网元、M-AMF网元、M-PCF网元用于对组播/广播业务的资源进行管理，M-PCF网元根据MCF网元的业务描述进行组播/广播业务的QoS参数的制定，M-SMF和M-AMF用于在(R)AN上创建组播上下文(或者称为组播会话)。SMF网元与MCF网元接口(或与M-PCF网元接口，图中未画出)获取组播信息，以便将终端加入组播/广播业务。上述M-SMF、M-AMF、M-PCF是组播/广播业务相关的SMF网元、AMF网元、PCF网元，加上“M-” 是为了与为上述终端服务的SMF网元、AMF网元、PCF网元进行区分。
可选的，图2a或图2b所示的架构也可以变形为图3b所示的架构，在图3b所示的架构中MCF网元类似一个SMF网元，该MCF网元负责组播业务的管理。若MCF网元为SMF网元，该SMF网元也可以为终端的会话提供服务，本发明对此不做限定。
在该图3b所示的架构中，CP与PCF网元/NEF网元接口，以便将组播业务信息发送给PCF网元。若CP与NEF网元接口，则CP先将组播业务信息发送给NEF网元，再由NEF网元发送给PCF网元，或者CP直接与PCF接口。MCF网元从PCF网元获取组播业务对应的PCC规则，以便为该组播业务创建相应的资源(即组播会话)。
MCF网元通过M-AMF网元与基站接口。该M-AMF网元也可以为终端提供服务。为终端服务的SMF网元与PCF网元接口，以便获得组播业务相关的信息。
下面对本申请涉及的网元进行介绍。
基站也可以称为接入网设备，为与终端配合使用的一种可以用于发射或接收信号的实体。主要用于实现物理层功能、资源调度和管理、终端的接入控制以及移动性管理等功能。接入网设备可以为支持有线接入的设备，也可以为支持无线接入的设备。示例性，接入网设备可以为接入网(access network，AN)/无线接入网(radio access network，RAN)，由多个5G-AN/5G-RAN节点组成。5G-AN/5G-RAN节点可以为：接入点(access point，AP)、基站(nodeB，NB)、增强型基站(enhance nodeB，eNB)、下一代基站(NR nodeB，gNB)、传输接收点(transmission reception point，TRP)、传输点(transmission point，TP)或某种其它接入节点等。
AMF网元，主要通过N1接口接入终端的NAS信令(包括会话管理(Session manage，SM)信令)和N2接口接入RAN的信令，完成用户的注册流程和SM信令的转发以及移动性管理。
SMF网元，用于实现会话相关的建立、释放、更新等流程。
PCF网元，负责用户策略管理，既包括移动性相关策略，也包括PDU会话相关策略，如QoS策略、计费策略等。
UDM网元，用于保存用户的签约数据。
AUSF网元，用于实现认证授权业务功能，负责对终端的接入进行认证授权。
DN，终端的PDU会话访问的目的地。
NEF网元，用于实现支持3GPP网络和第三方应用安全的交互，NEF网元能够安全的向第三方暴露网络能力和事件，用于加强或者改善应用服务质量，3GPP网络同样可以安全的从第三方获取相关数据，用以增强网络的智能决策；同时该网元支持从统一数据库恢复结构化数据或者向统一数据库中存储结构化数据。
AF网元，用于实现与3GPP核心网交互来提供服务，例如影响数据路由决策，策略控制功能或者向网络侧提供第三方的一些服务。
NWDAF网元用于实现数据分析功能。
NRF网元，用于维护网络中所有网络功能服务的实时信息。NRF网元保存有部署的网络功能(network function，NF)组件的信息，例如NF组件的标识和网络地址、支持的网络切片的标识、或者数据面实例的信息等，NRF网元向其它NF提供NF组件的注册和发现等服务。
数据网络(data network，DN)指的是为终端提供数据传输服务的运营商网络，如IMS(IP Multi-media Service，IP多媒体业务)、Internet等。
终端，可以是指向用户提供语音和/或数据连通性的设备，具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备。无线终端可以经RAN与一个或多个核心网进行通信。无线终端可以是用户设备(user equipment，UE)、手持终端、笔记本电脑、用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant，PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop，WLL)台、机器类型通信(machine type communication，MTC)终端或是其他可以接入网络的设备。终端与接入网设备之间采用某种空口技术(例如，3GPP接入技术或者非3GPP接入技术)相互通信。
由于未来接入网可以采用云无线接入网(cloud radio access network，C-RAN)架构来实现，一种可能的方式是将传统基站的协议栈架构和功能分割为两部分，一部分称为集中单元(central unit，CU)，另一部分称为分布单元(distributed unit，DU)，而CU和DU的实际部署方式比较灵活，例如多个基站的CU部分集成在一起，组成一个规模较大的功能实体。如图4a所示，其为本申请实施例提供的一种网络架构的示意图。
如图4a所示，该网络架构包括核心网(core network，CN)设备和接入网(以RAN为例)设备。其中RAN设备包括基带装置和射频装置，其中基带装置可以由一个节点实现，也可以由多个节点实现，射频装置可以从基带装置拉远独立实现，也可以集成基带装置中，或者部分拉远部分集成在基带装置中。例如，在LTE通信系统中，RAN设备(eNB)包括基带装置和射频装置，其中射频装置可以相对于基带装置拉远布置(例如射频拉远单元(radio remote unit，RRU)相对于基带处理单元(building base band unit，BBU))，RAN设备由一个节点实现，该节点用于实现无线资源控制(radio resource control，RRC)、分组数据汇聚层协议(packet data convergence protocol，PDCP)、无线链路控制(radio link control，RLC)、媒体接入控制(medium access control，MAC)等协议层的功能。再如，在一种演进结构中，基带装置可以包括CU和DU，多个DU可以由一个CU集中控制。如图4a所示，CU和DU可以根据无线网络的协议层划分，例如分组数据汇聚层协议层及以上协议层的功能设置在CU，PDCP以下的协议层，例如RLC层和MAC层等的功能设置在DU。
这种协议层的划分仅仅是一种举例，还可以在其它协议层划分，例如在RLC层划分，将RLC层及以上协议层的功能设置在CU，RLC层以下协议层的功能设置在DU；或者，在某个协议层中划分，例如将RLC层的部分功能和RLC层以上的协议层的功能设置在CU，将RLC层的剩余功能和RLC层以下的协议层的功能设置在DU。此外，也可以按其它方式划分，例如按时延划分，将处理时间需要满足时延要求的功能设置在DU，不需要满足该时延要求的功能设置在CU。
此外，射频装置可以拉远，不放在DU中，也可以集成在DU中，或者部分拉远部分集成在DU中，在此不作任何限制。
此外，请继续参考图4b，相对于图4b所示的架构，还可以将CU的控制面(control plane，CP)和用户面(user plane，UP)分离，分成不同实体来实现，分别为控制面CU实体(CU-CP实体)和用户面CU实体(CU-UP实体)。
在以上网络架构中，CU产生的数据可以通过DU发送给终端，或者终端产生的数据可以通过DU发送给CU。DU可以不对该数据进行解析而直接通过协议层封装后传给终端或CU。例如，RRC或PDCP层的数据最终会处理为物理层(physical layer，PHY)的数据发送给终端，或者，由接收到的PHY层的数据转变而来。在这种架构下，该RRC或PDCP层的数据，即也可以认为是由DU发送的。
在以上实施例中CU划分为接入网中，此外，也可以将CU划分为核心网，在此不做限制。
本申请以下实施例中的装置，根据其实现的功能，可以位于终端或基站。当采用以上CU-DU的结构时，基站可以为CU节点、或DU节点、或包括CU节点和DU节点功能的RAN设备。
图5为本申请实施例提供的一种通信设备的组成示意图。基站和终端可以参考如图5所示的通信设备的结构。如图5所示，通信设备可以包括至少一个处理器41和存储器42。
下面结合图5对通信设备的各个构成部件进行具体的介绍：
处理器41是通信设备的控制中心，可以是一个处理器，也可以是多个处理元件的统称。例如，处理器41是一个CPU，也可以是特定集成电路(Application Specific Integrated Circuit，ASIC)，或者是被配置成实施本申请实施例的一个或多个集成电路，例如：一个或多个微处理器(Digital Signal Processor，DSP)，或，一个或者多个现场可编程门阵列(Field Programmable Gate Array，FPGA)。
其中，处理器41可以通过运行或执行存储在存储器42内的软件程序，以及调用存储在存储器42内的数据，执行接入网设备的各种功能，例如，用于执行本申请各方法实施例中基站或终端的动作。
在具体的实现中，作为一种实施例，处理器41可以包括一个或多个CPU，例如图5中所示的CPU 0和CPU 1。
在具体实现中，作为一种实施例，通信设备可以包括多个处理器，例如图5中所示的处理器41和处理器45。这些处理器中的每一个可以是一个单核处理器(single-CPU)，也可以是一个多核处理器(multi-CPU)。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
存储器42可以是只读存储器(Read-Only Memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(Random Access Memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。
可选地，通信设备还包括：总线44。存储器42可以是独立存在，通过总线44与处理器41相连接。存储器42也可以和处理器41集成在一起。
其中，存储器42用于存储执行本申请方案的软件程序。
可选地，通信设备还包括：收发器43。
收发器43，用于与其他设备或通信网络通信。如用于与终端，核心网网元(例如，SMF网元等)，以太网，RAN，无线局域网(Wireless Local Area Networks，WLAN)等通信网络通信。收发器43可以包括基带处理器的全部或部分，以及还可选择性地包括RF处理器。RF处理器用于收发RF信号，基带处理器则用于实现由RF信号转换的基带信号或即将转换为RF信号的基带信号的处理。
总线44，可以是工业标准体系结构(Industry Standard Architecture，ISA)总线、外部设备互连(Peripheral Component Interconnect，PCI)总线或扩展工业标准体系结构(Extended Industry Standard Architecture，EISA)总线等。该总线可以分为地址总线、数据总线、控制总线等。为便于表示，图5中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
图5中示出的设备结构并不构成对通信设备的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
下面可以结合图1～图3b所示的任意一个通信系统，对本申请实施例提供的通信方法进行描述。需要说明的是，本申请的各实施例之间涉及的动作，术语等均可以相互参考，不予限制。本申请的实施例中各个设备之间交互的消息名称或消息中的参数名称等只是一个示例，具体实现中也可以采用其他的名称，不予限制。例如：本申请实施例所述的组播可以替换为广播、多播、多播通信、组播通信、组播广播、多播广播等术语。本申请实施例中的确定也可以理解为创建(create)或者生成(generate)，本申请实施例中的“包括”也可以理解为“携带”，在此统一说明，本申请实施例对此不作具体限定。
本申请实施例提供一种配置无线承载的方法，该配置无线承载的方法执行主体可以为基站，也可以为应用于基站中的芯片。或者该配置无线承载的执行主体可以为终端，也可以为应用于终端中的芯片。下述实施例以配置无线承载方法的执行主体为基站，以及以配置无线承载方法的执行主体为终端为例。
参考图6，图6示出了本申请实施例提供的一种配置无线承载的方法的交互实施例，该方法包括：
步骤601、基站接收第一请求消息，该第一请求消息用于请求将第一终端加入组播/广播业务。
其中，第一请求消息可以携带该组播/广播业务的标识，还可以携带指示信息。该指示信息可以用于指示向基站请求将第一终端加入组播/广播业务；该组播/广播业务的标识可以是该组播/广播业务对应的组播地址，也可以是该组播/广播业务对应的组播地址和源地址。
组播/广播业务的标识也可以称为组播/广播业务的数据的识别信息。该组播/广播业务的数据的识别信息可以用于唯一标识该组播/广播业务的数据，组播/广播业务的数据的识别信息可以由应用服务器(即CP)发送给终端。
其中，基站可以通过其与第一终端之间的信令连接(例如，N2信令连接)接收第一请求消息，这样基站便可以根据第一请求消息请求将第一终端加入该组播/广播业务。
其中，第一终端可以为图1中终端1～终端n中的任一终端。基站可以为图1中的基站10，也可以无线接入网设备或接入网设备。
具体地，基站可以接收来自会话管理网元(例如，SMF网元)的第一请求消息。例如，会话管理网元向第一终端接入的接入管理网元(例如，AMF网元)发送第一请求消息，然后由接入管理网元向基站发送第一请求消息。
本申请实施例中的步骤601可以通过以下步骤替换：基站确定将第一终端加入组播/广播业务。
其中，基站确定将第一终端加入组播/广播业务可以由基站根据第一请求消息确定。例如，第一请求消息中携带指示信息，该指示信息用于指示向基站请求将第一终端加入组播/广播业务，则基站根据指示信息确定将第一终端加入组播/广播业务。
步骤602、基站根据组播/广播业务的服务质量(quality of service，QoS)流信息，向第一终端发送组播无线承载的配置信息。
相应的，第一终端接收来自基站的组播无线承载的配置信息。
本申请实施例中的组播无线承载也可以称为组播广播无线承载，在此统一说明。
其中，该组播无线承载的配置信息用于配置组播无线承载。该组播无线承载用于向已加入组播/广播业务的终端传输组播/广播业务的数据，已加入组播/广播业务的终端包括第一终端。
其中，配置信息可以包括分组数据汇聚协议(packet data convergence protocol，PDCP)的配置信息，例如，PDCP的配置信息可以包括以下信息中的一种或多种：PDCP序列号(sequence number，SN)的长度、丢弃计时器的长度、指示是否进行头压缩的指示信息、指示该组播无线承载是否进行完整性保护的指示信息、指示该组播无线承载是否进行加密的指示信息等。该配置信息还可以包括无线链路控制层协议(radio link control，RLC)的配置信息。例如，RLC的配置信息可以为该组播无线承载所采用的传输模式为非确认模式，或者确认模式等。其中，组播/广播业务的数据可以为网络侧向属于通信群组中的一个或多个终端发送的数据。如：通信群组可以为接收同一指挥中心发出的命令的车队或者为接收同一电视节目的群组等。
例如，假设组播/广播业务的数据为某个电视节目，如：CCTV1、CCTV2等电视节目，终端为机顶盒(set top box，STB)，STB可以将这些电视节目的相关信息显示给用户。若分别使用终端1(STB1)～终端n(STBn)的用户均想观看CCTV1的电视节目，则基站可以在该组播无线承载上向终端1～终端n发送CCTV1的电视节目，这样便于终端1～终端n的用户收看CCTV1的电视节目。
其中，组播无线承载用于向已加入组播/广播业务的终端传输组播/广播业务的数据可以理解为：该组播无线承载用于向属于同一个通信群组中的各个终端传输组播业务的数据。该通信群组即可以理解为：包括一个或多个已加入组播/广播业务的终端。
本申请实施例中基站可以向加入该组播/广播业务的终端发送组播无线承载的配置信息，以使得基站与该组播/广播业务的终端均建立组播无线承载。后续，基站可以利用该组播无线承载向已加入组播/广播业务的终端传输组播/广播业务的数据。所谓的 基站可以利用该组播无线承载向已加入组播/广播业务的终端传输组播/广播业务的数据可以理解为：基站使用相同的组播无线承载的配置信息对该组播/广播业务的数据进行处理。基站将处理后的组播/广播业务的数据发送给加入该组播/广播业务的终端。加入该组播/广播业务的终端根据相同的无线承载的配置信息进行反向处理可得到相同的组播/广播业务的数据。可以理解的是，加入该组播/广播业务的终端接收到的来自基站的组播无线承载的配置信息相同。
需要说明的是，加入该组播/广播业务的终端中，可能存在部分终端以点到多点(Point to Multipoint，PTM)方式接收组播/广播业务的数据，而另外一部分终端以点到点(Point to point，PTP)方式接收组播/广播业务的数据。无论该加入该组播/广播业务的终端采用何种方式接收组播/广播业务的数据，基站可以在该组播无线承载上向终端传输组播/广播业务的数据。
可以理解的是，本申请实施例中组播/广播业务的QoS流信息可以指该组播/广播业务的对应的至少一个QoS流信息。本申请实施例中基站处具有组播/广播业务对应的至少一个服务质量QoS流信息。该组播/广播业务对应的至少一个服务质量QoS流信息可以由组播会话(与该组播/广播业务对应)对应的SMF网元或MCF网元提供给基站。例如，基站在创建该组播/广播业务对应的组播会话时，基站从SMF网元或MCF网元处获取该组播/广播业务对应的至少一个服务质量QoS流信息。具体地，该组播/广播业务对应的至少一个服务质量QoS流信息可以携带在第一请求消息中，或者，也可以在基站接收第一请求消息之前，基站已经接收到了该组播/广播业务对应的至少一个服务质量QoS流信息。
示例性的，本申请实施例中涉及到的QoS流信息包括该QoS流对应的业务质量流标识(QoS Flow Identifier，QFI)和/或该QoS流所对应的QoS参数。
其中，QoS参数可以包括：5G QoS标识(5G QoS Identifier，5QI)、调度优先级(Priority level)、QoS流的最大带宽、QoS流对应的保障带宽、QoS流对应的分配优先级(Allocation and Retention Priority，ARP)、保障速率(Guaranteed Bit Rate，GBR)，非保障速率(Non-Guaranteed Bit Rate，Non-GBR)、QoS流对应的时延中的一个或多个。
在一个示例中，步骤602中基站根据QoS流信息向第一终端发送组播无线承载的配置信息，包括：基站根据组播/广播业务的QoS流信息确定组播无线承载。基站向第一终端发送该确定的组播无线承载的配置信息。
进一步地，基站根据组播/广播业务的QoS流信息确定组播无线承载可以采用如下方式一和方式二实现：
方式一、基站根据组播/广播业务对应的至少一个QoS流信息确定该组播/广播业务对应的至少一个QoS流。基站确定组播/广播业务对应的至少一个QoS流中每个QoS流的组播无线承载，得到组播/广播业务的组播无线承载。换言之，组播/广播业务的组播无线承载包括组播/广播业务的对应的每个QoS流的组播无线承载。
本申请实施例中一个组播/广播业务可以对应至少一个QoS流(例如，语音业务流和视频业务流)。
例如，基站可以为该至少一个QoS流中的每个QoS流分配不同的组播无线承载， 即QoS流和组播无线承载是一一对应的关系(例如，为语音业务流分配组播无线承载2，为视频业务流分配组播无线承载1)。或者，基站也可以为至少一个QoS流中的部分QoS流分配相同的组播无线承载，部分QoS流分配不同的组播无线承载，即QoS流和组播无线承载的关系是多对一的关系，或者，基站也可以为至少一个QoS流中的每个QoS流分配相同的组播无线承载，即该组播/广播业务的所有QoS流均映射到相同的组播无线承载。
具体的，基站可以通过下述方式二确定QoS流和组播无线承载的关系是多对一的关系还是一一对应的关系。
方式二、基站可以根据至少一个QoS流中每个QoS流的QoS参数确定是否将不同的QoS流映射到相同的组播无线承载。例如，以QoS参数为调度优先级为例，基站可以将具有相同调度优先级的QoS流映射到相同的第一组播无线承载，这时可以将第一组播无线承载确定为组播/广播业务的组播无线承载，即QoS流和组播无线承载的关系是多对一的关系。又或者基站可以将具有不同调度优先级的QoS流映射到不同的第二组播无线承载，这些不同的第二组播无线承载作为组播/广播业务的组播无线承载，即QoS流和组播无线承载的关系是一一对应的关系。
例如，基站根据语音业务流的QoS参数和视频业务流的QoS参数确定语音业务流和视频业务流需要的带宽相同，则可以确定将语音业务流和视频业务流映射到同一组播无线承载，也即为语音业务流和视频业务流分配相同的组播无线承载。如果基站根据语音业务流的QoS参数和视频业务流的QoS参数确定语音业务流和视频业务流需要的带宽不同，则基站可以确定将语音业务流和视频业务流映射到不同的组播无线承载，也即为语音业务流和视频业务流分配不同的组播无线承载。例如，语音业务流需要的时延为时延1，而视频业务流需要的时延为时延2，则基站可以为语音业务流分配组播无线承载1，为视频业务流分配组播无线承载2，以便于基站为第一终端发送的组播无线承载的配置信息包括组播无线承载1的配置信息以及组播无线承载2的配置信息，其中，组播无线承载1用于建立组播无线承载1。组播无线承载2用于建立组播无线承载2。这样后续，基站可以在组播无线承载1上向第一终端发送组播/广播业务的语音业务流，在组播无线承载2上向第一终端发送组播/广播业务的视频业务流。
可以理解的是，本申请实施例中基站与第一终端之间可能建立有多个组播无线承载，不同组播无线承载对应的QoS参数不同，这样可以根据QoS参数建立满足QoS参数要求的组播无线承载。
可选的，基站在组播无线承载的配置信息中包括映射到该组播无线承载的一个或多个QoS流的QFI。
进一步的，本申请实施例提供的方法还可以包括：基站根据映射到一个组播无线承载上的所有组播QoS流的QoS参数信息确定该组播无线承载的QoS参数。
其中，QoS参数可以包括：该组播无线承载的5QI、调度优先级、最大带宽、保障带宽中的一项或多项。
进一步的，上述方法还可以包括：基站确定上述组播无线承载对应的逻辑信道标识。
例如，基站为该组播/广播业务的组播无线承载分配逻辑信道标识，基站将组播无 线承载的逻辑信道标识携带在组播无线承载的配置信息发送给第一终端，或者基站将组播无线承载的逻辑信道标识单独发送给第一终端。
在一种可能的实现方式中，本申请实施例中的步骤602可以通过以下方式实现：基站通过与第一终端之间的已经建立的RRC连接向第一终端发送组播无线承载的配置信息。例如，基站通过与第一终端之间的已经建立的RRC连接向第一终端发送第一消息，该第一消息中包括组播无线承载的配置信息。例如，第一消息可以为RRC消息，如RRC重配置消息(RRC Reconfiguration)，该RRC消息中包括无线承载的配置信息。已经建立的RRC连接使用的是特定的信令无线承载(signalling radio bearer，SRB)，并且，可以对信息进行加密。
在一种可能的实现方式中，组播无线承载的配置信息包括第一指示信息，该第一指示信息用于指示为第一终端配置的组播无线承载的类型为组播类型。这样便于第一终端根据第一指示信息确定播无线承载的类型为组播类型。
可以理解的是，该第一指示信息可以携带在组播无线承载的配置信息中，例如，组播无线承载的配置信息中包括承载类型字段，该承载类型字段设置为组播类型，当然该第一指示信息也可以由基站通过单独的信令发送给第一终端。
在一种可能的实现方式中，组播无线承载的配置信息还包括：组播/广播业务的标识，或组播/广播业务关联的组播会话的标识。这样第一终端便可以根据组播无线承载的配置信息配置好与基站之间的组播无线承载之后，通过组播/广播业务的标识，或组播/广播业务关联的组播会话的标识，确定该组播无线承载与组播/广播业务的标识，或组播/广播业务关联的组播会话的标识关联。换言之，第一终端便可以确定该组播无线承载用于接收组播/广播业务的标识指示的组播/广播业务的数据。
本申请实施例中的组播无线承载是第一终端根据无线承载的配置信息专门为接收组播/广播业务的数据建立的。
在一种可能的实现方式中，该组播无线承载的配置信息包括以下一个或多个：组播无线承载的标识，和组播无线承载映射的第一逻辑信道的标识。其中，第一逻辑信道是该组播无线承载对应的逻辑信道。具体的，经过该组播无线承载发送的数据会携带该第一逻辑信道的标识，这样，接收端(第一终端)可根据数据包中的第一逻辑信道的标识确定该数据包所对应的组播无线承载，从而将该数据包发送给该组播无线承载进行进一步的处理。逻辑信道对应一个标识(identity，ID)，逻辑信道的标识(logic channel identity，LCID)可以用于标识逻辑信道，逻辑信道的标识可以为逻辑信道的索引号等。
步骤603、第一终端根据组播无线承载的配置信息，配置组播无线承载。
本申请实施例中的步骤603的具体实现可以参考现有技术中的描述，此处不再赘述。例如，第一终端根据PDCP配置信息配置组播无线承载的PDCP，根据RLC的配置信息配置组播无线承载的RLC。例如，PDCP的配置信息指示该组播无线承载进行加密的指示信息，则第一终端配置该组播无线承载为进行加密的组播无线承载。
本申请实施例提供一种配置无线承载的方法，该方法中基站在接收到请求将第一终端加入组播/广播业务的第一请求消息，便可以根据组播/广播业务的服务质量QoS流信息，为第一终端配置组播无线承载的配置信息。这样便于第一终端建立与基站之 间的用于传输组播/广播业务的组播无线承载。后续存在待向第一终端发送的组播/广播业务的数据时，基站便可以利用该组播无线承载向第一终端发送组播/广播业务的数据。无论向第一终端发送该组播/广播业务的数据时采用点到多点方式(又可以称为：多播传输)还是点到点方式(又可以称为：单播传输)，基站可以生成一份相同的数据，并利用该组播无线承载发送数据，因此简化了基站的处理。
在一种可能的实现方式中，本申请实施例中的第一终端配置有第一媒体接入控制(medium access control，MAC)实体。该第一MAC实体可以用于传输(例如接收或发送)组播/广播业务的数据。第一终端的第一MAC实体可以由基站为第一终端配置。具体的，基站为第一终端配置第一MAC实体的过程可以参考图9所示的实施例，本申请实施例在此不再赘述。
示例性的，该第一MAC实体与第一无线网络临时标识(radio network temporary identifier，RNTI)关联，进一步，该第一RNTI与组播/广播业务对应，或第一RNTI与第一终端对应。此处，第一MAC实体与第一RNTI关联是指基站对通过该第一MAC实体进行传输的数据采用第一RNTI进行加扰处理，相应的，终端接收到数据后若数据通过第一MAC实体传输，则采用该第一RNTI对数据进行解扰处理，具体可以参见现有技术。
其中，第一RNTI与组播/广播业务对应可以理解为：第一RNTI为核心网网元或基站为该组播/广播业务分配的RNTI；或者，该第一RNTI和组播/广播业务的标识关联，或者该第一RNTI和组播会话关联。当第一RNTI与组播/广播业务对应时，该第一MAC实体由加入组播/广播业务的多个终端共享，也即基站为该加入该组播/广播业务的多个终端配置的第一MAC实体的配置信息相同。该第一RNTI和组播会话关联也可以理解为：第一RNTI和组播会话的标识之间具有映射关系，或者第一RNTI为组播会话的标识。
第一RNTI与第一终端对应可以理解为：基站为第一终端分配第一RNTI。其中，第一RNTI可以为第一终端的标识，或者第一RNTI与第一终端的标识关联。应理解，基站为不同终端分配不同的第一RNTI。当第一RNTI与第一终端的对应时，该第一RNTI也与该组播/广播业务对应，即，第一RNTI与第一终端的该组播/广播业务对应。此时，可以理解为，第一RNTI是基站为该第一终端的该组播/广播业务分配的RNTI。第一终端可以根据该第一RNTI可确定该组播/广播业务。第一RNTI与第一终端的标识关联可以理解为：第一RNTI与第一终端的标识具有映射关系，两者不同。
示例性的，终端的标识可以为以下一个或者多个：小区无线网络临时标识(Cell-RadioNetworkTemporaryIdentifier，C-RNTI)，网际协议地址(internet protocol，IP)、签约永久标识(subscription permanent identifier，SUPI)、永久设备标识(permanent equipment identifier，PEI)、通用公共签约标识(generic public subscription identifier，GPSI)、国际移动用户标识符(international mobile subscriber identifier，IMSI)、国际移动设备标识(international mobile equipment identity，IMEI)、IP五元组(5-tuple)和移动台国际综合业务数字网络号码(mobile station international integrated service digital network number，MSISDN)。下述实施例中但凡涉及到终端的标识均可以参考此处的描述，后续不再赘述。
举例说明，终端a和终端b具有的第一MAC实体关联的第一RNTI为RNTI1，该RNTI1与组播/广播业务对应。终端c具有的第一MAC实体关联的第一RNTI为RNTI2，该RNTI2与终端c对应。那么基站先通过该组播无线承载对该组播/广播业务的数据进行处理，例如，进行头压缩、加密、对数据包进行封装、分片、编码、添加逻辑信道标识等，具体可参见现有技术，然后，基站再将上述处理后的数据通过RNTI1进行加扰，并发送给终端a和终端b，基站10将上述处理后的数据通过RNTI2进行加扰后发送给终端c。这样对于支持点到多点方式的终端a和终端b，在接收到数据后通过RNTI1解扰，后再通过组播无线承载进行反向处理，例如，恢复被压缩的头、解密、解封装、分片重组、解编码等，以便恢复该组播/广播业务的数据广播。对于支持点到点方式的终端c，在接收到数据后通过RNTI2解扰，后再通过无线承载进行反向处理，以便恢复该组播/广播业务的数据。
需要说明的是，RNTI2除了与终端c关联之外，也可以关联该组播/广播业务，即终端c可确定通过RNTI2所接收的数据为上述组播/广播业务的数据。
此外，上述处理可以包括：对数据进行加密、完整性保护、分片、加封装、编码等操作中的一种或多种，相应的，反向处理包括：解密、完整性验证、组装、去封装、解码等操作中的一种或多种。
当第一RNTI与组播/广播业务对应时，基站仅需要发送一份数据，配置了与该第一RNTI关联的第一MAC实体的终端均可接收到该数据，从而可以节省空口带宽。
在一种可能的实现方式中，本申请实施例中的第一终端配置有第二MAC实体，该第二MAC实体用于接收除该组播/广播业务之外的其他一个或多个业务的数据。该第二MAC实体对应的无线承载所关联的逻辑信道的标识可以与上述第一MAC实体对应的无线承载所关联的逻辑信道的标识相同。基站通过为组播/广播业务配置与第二MAC实体不同的MAC实体(例如，第一MAC实体)，使得组播/广播业务所使用的逻辑信道的标识具有独立的空间，避免组播/广播业务与其他业务共享MAC实体导致逻辑信道的数量受限。本申请实施例中其他一个或多个业务的数据可以为：除该组播/广播业务之外的其余组播/广播业务的数据，或者单播业务的数据。可以理解的是，对于同一个终端，不同的组播/多播业务的数据对应的MAC实体不同。例如，终端1用于接收组播/多播业务1的数据以及组播/多播业务2的数据，则基站可以为终端1配置第一MAC实体用于接收组播/多播业务1的数据，此外为终端1配置第二MAC实体用于接收组播/多播业务2的数据。例如，终端1用于接收组播/多播业务1的数据以及单播业务的数据，则基站可以为终端1配置第一MAC实体用于接收组播/多播业务1的数据，此外为终端1配置第二MAC实体用于接收单播业务的数据。可以理解的是，第一MAC实体和第二MAC实体不仅可以用于接收数据，也可以用于发送数据。
在一种可能的实现方式中，本申请实施例提供的方法还可以包括：基站接收第二请求消息，该第二请求消息请求将第二终端加入上述组播/广播业务。基站向第二终端发送上述组播无线承载的配置信息。
例如，第二终端可以为图1所示的终端1～终端n中与第一终端不同的终端。
在一种可能的实现方式中，组播无线承载映射的第一逻辑信道的标识与第二逻辑信道的标识相同，第二逻辑信道为第二MAC实体对应的无线承载关联的逻辑信道， 终端可以利用第二MAC实体接收数据。这里，基站通过第二MAC实体向终端发送的数据是除上述组播/广播业务之外的其他业务的数据。第二MAC实体对应的无线承载关联的逻辑信道可以指：第二MAC实体对应的无线承载与第二逻辑信道之间具有映射关系，也即在第二MAC实体对应的无线承载上传输的数据通过第二逻辑信道传输。
本实施例中，为组播/广播业务配置单独的MAC实体(即第一MAC实体)使得该组播/广播业务的逻辑信道可以独立于其他业务的MAC实体，避免组播/广播业务与其他业务共享MAC实体导致逻辑信道的数量受限。
本申请实施例中基站可以对在该组播无线承载上传输的组播/广播业务的数据进行安全保护，也可以对在该组播无线承载上传输的组播/广播业务的数据不进行安全保护。但是是否对在该组播无线承载上传输的组播/广播业务的数据进行安全保护，第一终端接收到经该组播无线承载传输的组播/广播业务的数据的处理不同，下述将分别介绍：
示例1、不执行安全保护
例如，安全保护包括加密保护和/或完整性保护。其中，加密保护可以用于加密终端和基站间传输的组播/广播业务的数据，防止组播/广播业务的数据被破解。完整性保护可以用于保护终端和基站之间传输的数据的完整性，从而可以防止组播/广播业务的数据被篡改。
如图7所示，作为本申请的另一个实施例，该方法包括步骤701、步骤703以及步骤705。其中，步骤701同步骤601，步骤703同步骤602，步骤704同步骤603，图7所示的实施例与图6所示的实施例中的区别在于：图7所示的实施例还包括步骤702以及步骤705。其中，步骤702位于步骤703之前。
其中，步骤702、基站确定对组播/广播业务的数据不执行安全保护。
作为一种可能的实现方式，本申请实施例中的步骤702可以通过以下方式实现：基站接收来自核心网网元的第三指示信息，第三指示信息用于指示对组播/广播业务的数据不执行安全保护。基站根据第三指示信息，确定对组播/广播业务的数据不执行安全保护。如果基站确定对组播/广播业务的数据不执行安全保护，则基站可以将组播无线承载配置为不执行安全保护。
示例性的，核心网网元可以在创建该组播/广播业务的组播会话时，向基站发送第三指示信息。本申请实施例中的组播会话也可以称为组播广播会话，该组播会话可以用于传输组播/广播业务。
作为另一种可能的实现方式，本申请实施例中的步骤702可以通过以下方式实现：基站自主确定对组播/广播业务的数据不执行安全保护。或者，基站根据第三指示信息确定对组播/广播业务的数据不执行安全保护。例如，基站确定组播/广播业务的数据的安全要求低于或等于预设安全要求，则基站确定对组播/广播业务的数据不执行安全保护。
基于步骤702，在一种可能的实现方式中，本申请实施例中基站在步骤703中向第一终端发送的组播无线承载的配置信息中包括第二指示信息，该第二指示信息用于指示在组播无线承载上传输的组播/广播业务的数据不执行安全保护。
本申请实施例中第二指示信息可以携带在组播无线承载的配置信息中(例如，第 二指示信息为组播无线承载的配置信息中的一个字段)。当然该第二指示信息也可以和组播无线承载携带在同一个消息中，再者，该第二指示信息也可以和组播无线承载携带在不同消息中，本申请实施例对此不做限定。
此外，本申请实施例中基站可以采用显式方式向第一终端指示在组播无线承载上传输的组播/广播业务的数据不执行安全保护。例如，基站向第一终端发送第二指示信息。当然，基站也可以采用隐式方式向第一终端指示在组播无线承载上传输的组播/广播业务的数据不执行安全保护。例如，该组播无线承载的配置信息中未包括安全保护指示，则第一终端可以确定在组播无线承载上传输的组播/广播业务的数据未执行安全保护。或者基站向第一终端未发送组播/广播业务对应的安全参数，这样第一终端也可以确定在组播无线承载上传输的组播/广播业务的数据不执行安全保护。
步骤705、第一终端确定在组播无线承载上传输的组播/广播业务的数据未执行安全保护。
一种示例a，本申请实施例中的步骤705可以通过以下方式实现：第一终端根据第二指示信息确定在组播无线承载上传输的组播/广播业务的数据未执行安全保护。
另一种示例b，本申请实施例中的步骤705可以通过以下方式实现：第一终端未接收到该组播/广播业务对应的安全参数，则第一终端确定在组播无线承载上传输的组播/广播业务的数据未执行安全保护。
再一种示例c，本申请实施例中的步骤705可以通过以下方式实现：第一终端和基站协商或者协议预定义在组播无线承载上传输的组播/广播业务的数据不执行安全保护，则第一终端也可以确定在该组播无线承载上传输的组播/广播业务的数据未执行安全保护。
如果第一终端通过该示例b或示例c确定在组播无线承载上传输的组播/广播业务的数据未执行安全保护，则基站可以不向第一终端发送第二指示信息。
需要说明的是，本申请实施例中的步骤705和步骤704不分执行先后。可以理解的是，如果第二指示信息携带在组播无线承载的配置信息中，或者第二指示信息与组播无线承载的配置信息携带在同一个消息中，则第一终端建立组播无线承载之后便可以确定在组播无线承载上传输的组播/广播业务的数据未执行安全保护。如果第一终端在完成组播无线承载的建立之后，接收到第二指示信息，则步骤705位于步骤704之后。
需要说明的是，本申请实施例中如果基站向第一终端发送组播无线承载的配置信息之后，确定对组播/广播业务的数据不执行安全保护，则步骤702还可以位于步骤703之后。
在图7所示的实施例中，本申请实施例提供的方法还可以在第一终端和基站之间具有组播无线承载的情况下，包括：
步骤706、基站在组播无线承载上向第一终端发送组播/广播业务的数据。相应的，第一终端在组播无线承载上接收组播/广播业务的数据。
具体的，基站在接收到的针对组播/广播业务的数据的情况下，在该组播无线承载上发送组播/广播业务的数据，这样接入该组播/广播业务的一个或多个终端(包括第一终端)便可以接到的组播/广播业务的数据。
示例2、执行安全保护
如图8所示，作为本申请的另一个实施例，该方法包括步骤801、步骤803以及步骤805。其中，步骤801同步骤601，步骤803同步骤602，步骤804同步骤603，图7所示的实施例与图6所示的实施例中的区别在于：还可以包括步骤802和步骤805。其中，步骤802位于步骤803之前。
其中，步骤802、基站确定对组播/广播业务的数据执行安全保护。
作为一种可能的实现方式，本申请实施例中的步骤802可以通过以下方式实现：基站接收来自核心网网元(例如，SMF网元，M-SMF网元)的第五指示信息，第五指示信息用于指示对组播/广播业务的数据执行安全保护。基站根据第五指示信息，确定对组播/广播业务的数据执行安全保护。示例性的，核心网网元可以在创建组播会话时，向基站发送第五指示信息。
作为另一种可能的实现方式，本申请实施例中的步骤802可以通过以下方式实现：一种实现：基站自主确定对组播/广播业务的数据执行安全保护。例如，基站确定组播/广播业务的数据的安全要求高于或等于预设安全要求，则基站确定对组播/广播业务的数据执行安全保护。或者，另一种实现：基站根据第五指示信息确定对组播/广播业务的数据执行安全保护。
基于步骤802，本申请实施例中的步骤803中基站向第一终端发送的组播无线承载的配置信息中还包括第四指示信息，第四指示信息用于指示在组播无线承载上传输的组播/广播业务的数据已执行安全保护或需要执行安全保护。可以理解的是，该第四指示信息可以携带在组播无线承载的配置信息中，当然该第四指示信息也可以通过单独的信令发送给第一终端，或者第四指示信息也可以和组播无线承载的配置信息携带在同一个消息中，本申请实施例对此不作限定。
需要说明的是，本申请实施例中基站可以采用显式方式向第一终端指示在组播无线承载上传输的组播/广播业务的数据执行安全保护。例如，基站向第一终端发送第四指示信息。当然，基站也可以采用隐式方式向第一终端指示在组播无线承载上传输的组播/广播业务的数据执行安全保护。例如，基站向第一终端发送组播/广播业务对应的安全参数，这样第一终端也可以确定用于发送所述组播/广播业务的组播无线承载上的数据执行安全保护。
需要说明的是，第四指示信息可以为加密保护指示和/或完整性保护指示中的一个或多个。其中，加密保护指示用于指示在组播无线承载上传输的组播/广播业务的数据进行加密处理。完整性保护指示用于指示在组播无线承载上传输的组播/广播业务的数据进行完整性保护。
步骤805、第一终端确定在组播无线承载上传输的组播/广播业务的数据已执行安全保护。
一种示例d，本申请实施例中的步骤805可以通过以下方式实现：第一终端根据第四指示信息确定在组播无线承载上传输的组播/广播业务的数据已执行安全保护。
另一种示例e，本申请实施例中的步骤805可以通过以下方式实现：第一终端接收到该组播/广播业务对应的安全参数，则第一终端确定在组播无线承载上传输的组播/广播业务的数据已执行安全保护。
再一种示例f，本申请实施例中的步骤805可以通过以下方式实现：第一终端和基站协商或者协议预定义基站对组播/广播业务的数据执行安全保护，则第一终端也可以确定在组播无线承载上传输的组播/广播业务的数据已执行安全保护。
如果第一终端通过该示例e或示例f确定在组播无线承载上传输的组播/广播业务的数据已执行安全保护，则基站可以省略向第一终端发送第四指示信息的步骤。
需要说明的是，本申请实施例中的步骤805和步骤804不分执行先后。可以理解的是，如果第四指示信息携带在组播无线承载的配置信息中，或者第四指示信息与组播无线承载的配置信息携带在同一个消息中，则第一终端建立组播无线承载之后便可以确定在组播无线承载上传输的组播/广播业务的数据已执行安全保护。如果第一终端在配置好组播无线承载后才接收到第四指示信息，则步骤805晚于步骤804执行。
本申请实施例中对在组播无线承载上传输的组播/广播业务的数据执行安全保护的动作可以由UPF网元执行也可以由基站执行，本申请实施例对此不作限定。
在一种可能的实施例中，如图8所示，本申请实施例提供的方法还包括：
步骤806、基站确定组播/广播业务对应的安全参数，该安全参数包括安全密钥和/或安全保护所使用的安全算法，所述安全参数用于对所述组播/广播业务的数据进行安全保护。
例如，安全参数可以包括对组播/广播业务的数据进行加密的安全密钥和/或确定安全密钥的加密算法。安全参数还可以包括对组播/广播业务的数据进行完整性保护的完整性密钥和/或完整性算法。完整性可以用于保护第一终端和基站之间传输的数据的完整性。
一种示例，步骤806可以通过以下方式实现：基站接收来自核心网网元的组播/广播业务对应的安全参数。这样基站便可以确定组播/广播业务对应的安全参数。另一种示例，基站处配置有一个或多个安全参数。基站从一个或多个安全参数中确定组播/广播业务对应的安全参数。例如，基站可以从一个或多个安全参数中任选一个作为组播/广播业务对应的安全参数。或者基站可以从一个或多个安全参数中选择与组播/广播业务关联的安全参数，作为组播/广播业务对应的安全参数，本申请实施例对此不做限定。
若基站接收来自核心网网元的安全参数，则可选的，第一终端也可以直接从核心网网元接收相同的安全参数，当然，安全参数也可以由基站从核心网网元接收到后再发送给第一终端，本申请实施例对此不限定。
步骤807、基站向第一终端发送组播/广播业务对应的安全参数。相应的，第一终端接收组播/广播业务对应的安全参数。
步骤808、基站根据安全参数，获得安全保护后的组播/广播业务的数据。
具体的，本申请实施例中的步骤808可以通过以下方式实现：基站根据安全参数，对组播/广播业的数据进行安全保护，得到安全保护后的组播/广播业务的数据。具体地，基站根据安全参数，对组播/广播业的数据进行安全保护的过程可参见现有技术的描述，本实施例不再赘述。
例如，基站根据完整性密钥对组播/广播业务的数据进行完整性保护。基站根据加密密钥对组播/广播业务的数据进行加密。
步骤809、基站在组播无线承载上向第一终端发送安全保护后的组播/广播业务的数据。相应的，第一终端在组播无线承载上接收来自基站的安全保护后的组播/广播业务的数据。
步骤810、第一终端根据安全参数和安全保护后的组播/广播业务的数据，获得组播/广播业务的数据。
可以理解的是，第一终端处具有组播/广播业务对应的安全参数。该组播/广播业务对应的安全参数可以由基站或核心网网元或应用层设备(如该组播/广播业务对应的应用服务器)发送给第一终端。如果组播/广播业务对应的安全参数可以由基站配置给第一终端，则本申请实施例提供的方法在步骤809之前还可以包括：基站向第一终端发送安全参数。相应的，第一终端接收来自基站的安全参数，该安全参数用于第一终端获取在组播无线承载上传输的组播/广播业务的数据。
例如，第一终端可以根据加密密钥对来自基站的已加密的组播/广播业务的数据进行解密。第一终端可以根据完整性密钥验证解密后的组播/广播业务的数据的完整性。
如图9所示，图9示出了本申请实施例提供的一种配置无线资源的方法，该方法包括：
步骤901、基站接收第一请求消息，该第一请求消息用于请求将第一终端加入组播/广播业务。
此处关于第一请求消息的描述，可以参考步骤601处的描述，此处不再赘述。
步骤902、基站根据组播/广播业务的服务质量QoS流信息，向第一终端发送第一MAC实体的配置信息。相应的，第一终端接收来自基站的第一MAC实体的配置信息。该第一MAC实体的配置信息用于为第一终端配置组播/广播业务对应的MAC实体。其中，第一MAC实体用于接收组播/广播业务的数据。该第一MAC实体由已加入该组播/广播业务的多个终端共享，已加入该组播/广播业务的多个终端包括第一终端。组播/广播业务对应的MAC实体是指：终端通过该第一MAC实体接收该组播/广播业务的数据。
例如，对于同一个通信群组中的多个终端，基站可以通过步骤902为该通信群组中的每个终端配置组播/广播业务对应的第一MAC实体，以便于通信群组中的每个终端可以利用各自的第一MAC实体接收来自基站的组播/广播业务的数据。
步骤903、第一终端根据第一MAC实体的配置信息，配置第一终端的第一MAC实体。
在一种可能的实现方式中，第一MAC实体的配置信息包括第六指示信息，该第六指示信息用于指示第一MAC实体用于传输组播/广播业务的数据。这样第一终端便可以根据第六指示信息确定第一MAC实体用于传输组播/广播业务的数据。
在一种可能的实现方式中，本申请实施例提供的方法还可以包括：基站为该第一终端配置第二MAC实体。该第二MAC实体用于向终端发送除该组播/广播业务的数据以外的数据。可以理解的是，本申请实施例中，基站通过为该组播/广播业务配置单独的MAC实体(即第一MAC实体)使得该组播/广播业务的逻辑信道可以独立于其他业务的逻辑信道，其中，其他业务的MAC实体与第一MAC实体不同，这样可以避免组播/广播业务与其他业务共享MAC实体导致逻辑信道的数量受限。
在一种可能的实现方式中，本申请实施例中的第一MAC实体的配置信息还包括第一RNTI，第一RNTI与组播/广播业务对应或第一RNTI与第一终端对应。
其中，第一RNTI与组播/广播业务对应可以理解为：第一RNTI为：为该组播/广播业务或第一RNTI为：为该组播/广播业务的组播会话分配的临时标识，例如，可以是组播无线网络临时标识(Group-Radio Network Temporary Identifier，G-RNTI)。
作为一种示例，第一RNTI与组播/广播业务对应时，该第一MAC实体由加入该组播/广播业务的一个或多个终端共享。
作为一种具体实现：基站为每个组播会话(组播/广播业务)分配一个G-RNTI，使得每个组播会话可独立进行调度，这样可以避免由于无线承载数量的限制导致一个基站所支持的组播/广播业务数量的限制，并且也可以避免限制组播/广播业务能支持的QoS的级别。
应理解，对于采用点到多点((Point to Multipoint，PTM)方式接收该组播/广播业务数据的第一终端，该第一RNTI与组播/广播业务对应。
其中，第一RNTI与第一终端对应可以理解为：基站为该第一终端分配RNTI。应理解，对于采用点到点方式接收该组播/广播业务数据的第一终端，第一RNTI与该第一终端对应。
应理解，第一RNTI与第一终端对应时，第一RNTI还可以进一步地与该组播/广播业务关联，即，第一RNTI与第一终端的组播/广播业务关联。这样，第一终端也可以根据第一RNTI确定与该第一RNTI关联的第一MAC实体用于传输的该组播/广播业务。示例性的，基站可以为该第一终端的该组播/广播业务分配第一RNTI，这样，根据该第一RNTI可唯一确定一个组播/广播业务。例如，该第一RNTI不同于该终端用于接收单播业务的RNTI，也不同于该终端用于接收其他组播/广播业务的RNTI。
在一种可能的实现方式中，组播/广播业务通过点到多点(PTM)方式发送时，第一RNTI与组播/广播业务对应。或者，组播/广播业务通过点到点方式发送时，第一RNTI与第一终端对应。例如，以一个或多个终端为终端1、终端2、终端3以及终端4为例，如果终端1、终端2以PTM方式接收组播/广播业务的数据，则基站为终端1和终端2分别发送的第一MAC实体的配置信息中包括与组播/广播业务对应的第一RNTI。如果终端3以点到点方式接收组播/广播业务的数据，则基站为终端3发送的第一MAC实体的配置信息中包括与终端3对应的第一RNTI。如果终端4以点到点方式接收组播/广播业务的数据，则基站为终端4发送的第一MAC实体的配置信息中包括与终端4对应的第一RNTI。
可以理解的是，为了为第一终端配置正确接收组播/广播业务的数据的RNTI，本申请实施例提供的方法在步骤902之前还可以包括：基站确定第一终端支持的接收模式。例如，接收模式为点到点方式或点到多点方式。
可以理解的是，基站根据第一终端的信号质量、接收该组播/广播业务的终端的数量等信息确定采用PTM或PTP模式发送组播/广播业务的数据，具体可参见现有技术的描述，本实施例不再赘述。
在一种可能的实现方式中，如图9所示，本申请实施例提供的方法还可以包括：基站接收第二请求消息，该第二请求消息请求将第二终端加入组播/广播业务。基站向 第二终端发送第三MAC实体的配置信息包括所述组播无线承载的标识，所述第三MAC实体与第二RNTI关联，所述第二RNTI与所述组播/广播业务对应或与所述第二终端对应。
需要说明的是，1、在第一终端具有第一MAC实体的情况下，本申请实施例中的图6或图7或图8所示的实施例可以单独作为一个实施例，其主要目的是基站为第一终端配置组播无线承载，以及向第一终端指示组播/广播无线承载的数据是否执行安全保护。
2、在第一终端还需要被配置第一MAC实体的情况下，图6或图7或图8所示的实施例可以和图9所示的实施例组合形成一个新的实施例。也即在图6或图7或图8所示的实施例中基站还可以执行步骤901～步骤903。
3、在第一终端具有组播无线承载的情况下，图9所示的实施例可以作为一个单独的实施例，其主要目的是基站为第一终端配置第一MAC实体。
4、在第一终端还需要被配置组播无线承载的情况下，图9所示的实施例可以和图6或图7或图8所示的实施例结合形成一个新的实施例，换言之在步骤903之后基站还可以执行图6或图7或图8所示的实施例中由基站执行的步骤，第一终端也可以执行图6或图7或图8所示的实施例中由第一基站执行的步骤。
5、在基站确定既要为第一终端配置组播无线承载，又要为第一终端配置第一MAC实体的情况下，基站可以将组播无线承载的配置信息和第一MAC实体的配置信息携带在同一个消息中发送给第一终端。
需要说明的是，本申请实施例中如果上述第一终端由应用于第一终端中的芯片替换，则第一终端中的芯片的标识即为第一终端的标识。已加入所述组播/广播业务的终端包括第一终端中的芯片即为已加入所述组播/广播业务的终端包括第一终端。
如图10所示，图10示出了本申请实施例中一种配置无线承载的方法的具体实施例，该方法包括：
步骤1001、终端1(例如TV)向SMF网元发送请求消息1，相应的，SMF网元接收来自终端1的该请求消息1。该请求消息1请求将终端1加入(Join)组播/广播业务。其中，请求消息1中可以携带组播/广播业务对应的组播地址。可选的，该请求消息1中还可以携带组播/广播业务对应的源地址。可选的，在终端1具有组播/广播业务的标识的情况下，该请求消息1中携带组播/广播业务的标识以及终端1的标识。在请求消息1中携带终端1的标识便于SMF网元识别要加入组播/广播业务的终端。其中，组播/广播业务对应的组播地址和/或源地址用以标识所对应的组播/广播业务。
一种示例，该请求消息1可以为IGMP消息，则步骤1001可以通过以下方式实现：终端1向UPF网元发送IGMP消息，该IGMP消息请求将终端1加入组播/广播业务。来自终端1的请求消息1经过UPF网元发送给SMF网元。例如，终端1通过与UPF网元之间具有的PDU会话的用户面向UPF网元发送请求消息1。
另一种示例，请求消息1可以为PDU会话修改请求消息。或者请求消息1中可以携带在NAS消息中。
终端1利用非接入层(Non-access stratum，NAS)消息携带请求消息1时，若终端1已经获得了组播/广播业务对应的组播业务的标识，则终端1在请求消息1中可将 组播/广播业务的标识发送给网络(SMF网元)，或者，终端1发送组播/广播业务对应的组播地址和可选的源地址用以标识该组播/广播业务。示例性的，TV通过RG向SMF网元发送请求消息1，该请求消息1用于请求DN中DNN1对应网元的组播业务，请求消息1携带DNN1，SMF网元向UDM网元发送获取消息，获取消息携带DNN1，那么，UDM网元可根据预配置信息确定DNN1对应的网元提供组播业务。
步骤1002、SMF网元获取组播/广播业务所对应的策略与计费控制(policy and charging control，PCC)规则。
示例性的，组播业务所对应的PCC规则包括如下内容中的至少一项：一个或多个组播业务流的描述信息、每个组播业务流的QoS信息，其中组播业务流的QoS信息包括组播业务流的最大带宽需求、组播业务流的ARP、组播业务流的5QI中的至少一项。
一种示例，本申请实施例中的步骤1002可以通过以下方式实现：SMF网元向PCF网元发送消息2，相应的，PCF网元接收来自SMF网元的消息2。该消息2用于请求组播/广播业务所对应的PCC规则。该消息2中携带组播/广播业务的标识，或者组播/广播业务的组播地址或源地址。PCF网元根据消息2中携带的组播/广播业务的标识，或者组播/广播业务的组播地址或源地址获取该组播/广播业务所对应的PCC规则，之后PCF网元向SMF网元发送组播/广播业务所对应的PCC规则。可以理解的是，该PCF网元中具有组播/广播业务所对应的PCC规则。若终端1发送的请求加入组播/广播业务的请求消息中携带了组播/广播业务的标识，则SMF网元将组播/广播业务的标识发送给PCF网元，以便PCF网元根据组播/广播业务的标识获取组播/广播业务所对应的PCC规则。若终端1请求加入组播/广播业务的请求消息中携带了组播地址和可选的源地址，则SMF网元将该组播地址和可选的源地址发送给PCF网元，以便PCF网元根据该组播地址和可选的源地址获取组播/广播业务所对应的PCC规则。
另一种示例，本申请实施例中的步骤1002可以通过以下方式实现：SMF网元上具有该组播/广播业务所对应的PCC规则，在SMF网元确定将终端1加入组播/广播业务时，便可以从SMF网元上获取组播/广播业务所对应的PCC规则。在这种情况下，SMF网元可以省略向PCF网元发送消息2的过程。
需要说明的是，SMF网元中具有的组播/广播业务所对应的PCC规则可以由PCF网元提前配置给SMF网元。例如，PCF网元在生成组播/广播业务所对应的PCC规则时，便可以主动配置给SMF网元该组播/广播业务所对应的PCC规则。
步骤1003、SMF网元获取组播/广播业务所对应的组播会话的信息。
组播会话的信息包括：组播会话的标识、组播会话的各组播QoS流的信息和组播QoS流的描述信息。其中，组播QoS流的信息参见前述。QoS流的描述信息可以是该QoS流的目标地址(即组播地址)、源地址、目标和源端口号、该数据包的协议类型中的至少一项，Qo务流的描述信息也可以是应用标识，或者，QoS流的描述信息也可以是策略控制规则的标识(即该标识对应PCC规则中的所有业务流的描述信息)或策略控制规则中的包过滤器的标识(包过滤器的标识和可选的PCC规则的标识)，本申请实施例对此不做限定。
可以理解的是，SMF网元向基站发送QFI和QOS参数。
在本实施例中假设该终端1所接入的基站已经为该组播/广播业务创建了组播会话， SMF网元从创建该组播会话的SMF网元或MCF网元处获取上述组播会话的信息。例如，创建组播会话的SMF网元可将组播会话的标识、基站的标识、组播/广播业务的标识、SMF网元的标识保存到存储单元(如UDM)，SMF网元可从存储单元(如UDM)获取创建该组播会话的SMF网元的标识，并向创建该组播会话的SMF网元获取组播会话的信息。或者，SMF网元可根据基站的标识获取创建该组播会话的MCF网元，并从MCF网元处获取该组播会话的信息。或者，PCF网元保存了组播会话的信息，因此在SMF网元从PCF网元处获取组播/广播业务所对应的PCC规则时，PCF网元也可以向SMF网元提供组播会话的信息。
步骤1004、SMF网元向基站发送请求消息3。相应的，基站接收来自SMF网元的请求消息3。该请求消息3用于请求基站将终端1加入组播/广播业务(或者，加入该组播/广播业务对应的组播会话)。
示例性的，该请求消息3中携带终端的标识和组播/广播业务的标识。或者请求消息3中携带终端的标识和组播/广播业务的组播地址、源地址。或者请求消息3携带该组播/广播业务对应的组播会话的标识。
可选的，该请求消息3中还可以携带终端1的协议数据单元(protocol data unit，PDU)会话的标识，以便基站将该组播/广播业务的组播会话与终端1的PDU会话关联。
可选的，该请求消息3中还包括SMF网元向终端1发送的NAS消息，该NAS消息中包括该组播/广播业务的标识、组播/广播业务对应的组播地址和可选的源地址，以便终端1将组播无线承载与组播/广播业务进行关联。可选的，该NAS消息还用于指示终端成功加入该组播/广播业务。可以理解的是，组播/广播业务的标识可以由SMF网元或者UPF网元为组播/广播业务分配。之后SMF网元将组播/广播业务的标识提供给基站和终端1。
示例性的，本申请实施例中的步骤1004可以通过以下方式实现：SMF网元向为终端1提供服务的AMF网元发送请求消息3。然后由AMF网元基站发送请求消息3。具体的，AMF网元在该终端1对应的N2信令连接上发送该请求消息3，这样便于基站可根据N2信令连接确定终端1。具体的，终端1对应的N2信令连接包括该基站为该终端1分配的N2信令连接的标识和AMF网元为该终端1分配的N2信令连接的标识，基站根据上述标识确定该N2信令连接对应的终端1。
步骤1005、基站将终端1加入组播/广播业务。
本实施例假设基站已经为该组播/广播业务创建了组播会话，在创建组播会话时，基站从创建该组播会话的核心网元(如SMF网元或MCF网元)处获取了组播会话的QoS流信息，包括组播会话QoS流的QFI、该QFI对应的QoS参数。在创建组播会话时，基站根据组播会话对应的组播/广播业务的QoS流的QoS信息确定需要为该组播/广播业务创建的组播无线承载。例如，基站将不同的QoS流映射到不同的组播无线承载或者相同的组播无线承载。
步骤1006、当终端1加入组播/广播业务时，基站可根据在组播会话创建时确定的组播无线承载生成组播无线承载的配置信息。
其中，组播无线承载的配置信息用于配置终端1接收组播/广播业务的组播无线承 载(radio bearer)。
步骤1007、基站向终端1发送组播无线承载的配置信息。相应的，终端1接收来自基站的组播无线承载的配置信息。
一种示例，该组播无线承载的配置信息中包括组播指示信息(对应上述实施例中的第一指示信息)。
在该方法中，基站向终端1发送的组播无线承载配置信息中包括组播指示信息，用于指示该组播无线承载用于接收组播/广播业务的数据。
需要说明的是，已定义了终端和基站之间具有信令无线承载(SRB)和数据无线承载(DRB)，可以在这两种无线承载的基础上增加组播无线承载，与这两种无线承载并列。
一方面，当组播无线承载用于接收组播/广播业务时，组播无线承载的配置信息指示该组播无线承载不需要执行安全保护。组播无线承载不需要执行安全保护可以理解为：组播无线承载对应的PDCP不需要执行安全保护。具体的，可以采用以下方法任一个方法指示该组播无线承载对应的PDCP不需要加密和完整性保护：
方法一：用于组播/广播业务的无线承载默认不加密
通常无线承载的配置信息中包括业务数据适配层(Service DataAdaptation Protocol，SDAP)配置信息，在现有技术中，无线承载配置信息中的SDAP配置信息用于将无线承载与PDU会话关联。具体的，在SDAP配置信息中包括该无线承载所对应的PDU会话标识。在现有技术中，一个PDU会话的所有无线承载要不全部支持加密，要不全部不支持加密，属于同一PDU会话的无线承载不能部分支持加密，部分不支持。
本申请实施例中为了支持用于发送组播/广播业务的组播无线承载不加密，当组播无线承载配置信息用于配置组播/广播业务的组播无线承载时，该组播无线承载的配置信息中的SDAP配置信息中不包括PDU会话标识，即当该组播无线承载不与PDU会话关联时，默认该组播无线承载不进行加密和不进行完整性保护。或者，该配置信息指示该配置信息配置的组播无线承载的类型为组播类型，此时，也可以默认为该组播无线承载不执行加密和完整性保护。可以理解的是，该组播无线承载不进行加密和不进行完整性保护可以替换为：在该组播无线承载上传输的组播/广播业务的数据不进行加密保护和完整性保护。
可选的，该组播无线承载的配置信息还用于指示将该组播无线承载与组播/广播业务进行关联。例如，在组播无线承载的配置信息中SDAP配置信息中包括组播/广播业务的标识。这样，当终端1从该组播无线承载上接收到数据后可将数据与相应的组播/广播业务关联。
方法二：在组播无线承载的配置信息中包括第二指示信息，该第二指示信息用于指示该组播无线承载不进行加密和完整性保护。在该方法中，基站向终端1发送的组播无线承载配置信息中包括组播指示信息，用于指示该组播无线承载用于接收组播/广播业务的数据，即组播指示信息(对应上述第一指示信息)用于指示配置信息配置的组播无线承载的类型为组播类型。
在方法二中组播无线承载的SDAP配置信息中可包括PDU会话标识，以便将组播无线承载与PDU会话关联。
可选的，该方法二中组播无线承载的配置信息可用于指示将该组播无线承载与组播/广播业务进行关联。例如，在组播无线承载的配置信息中的SDAP配置信息中包括用于指示该组播无线承载与组播/广播业务进行关联的指示信息。例如，SDAP配置信息中携带组播/广播业务的标识。
另一方面，当组播无线承载用于发送或接收组播/广播业务时，组播无线承载的配置信息指示该组播无线承载需要执行安全保护。组播无线承载需要执行安全保护可以理解为：组播无线承载对应的PDCP需要执行安全保护。具体的，可以采用以下方法任一个方法指示该组播无线承载对应的PDCP需要加密和完整性保护：
在组播无线承载的配置信息包括第四指示信息，第四指示信息用于指示该组播无线承载需要执行安全保护。或者，当终端1收到针对该组播/广播业务对应的安全参数时，终端1确定用于发送该组播/广播业务的组播无线承载执行了安全保护，此时，组播无线承载的配置信息中包括该组播/广播业务的标识，以便终端1可以根据组播无线承载的配置信息获知该组播无线承载用于发送该组播/广播业务的数据，或者，上述安全参数包括在该组播无线承载的配置信息中。
此外，基站还可以在组播无线承载的配置信息中包括映射到该组播无线承载的组播QoS业务的QFI。终端1可根据该组播QoS业务的QFI对在该组播无线承载上接收到的数据进行QFI的校验。
例如，映射到该组播无线承载的组播QoS业务的QFI可以携带在组播无线承载的配置信息中的SDAP配置信息中。
基站采用终端1与基站建立的RRC连接发送上述组播无线承载的配置信息，例如，组播无线承载的配置信息携带在基站向终端1发送的RRC消息中，该RRC消息包括组播无线承载的配置信息。
若SMF网元向基站发送了NAS消息，基站将NAS消息发送给终端1。若在步骤1001中终端1发送的请求消息1为IGMP消息，则根据该NAS消息和组播无线承载的配置信息，终端1可将组播/广播业务与相应的组播无线承载进行关联。
步骤1008、基站向SMF网元发送响应消息。相应的，SMF网元接收来自基站的响应消息。
示例性的，步骤1008可以通过以下方式实现：基站将该响应消息通过为终端1服务的AMF网元发送给SMF网元。其中，在响应消息中还可以携带用于指示基站是否成功将终端1加入组播/广播业务的指示信息。如果基站未成功将终端1加入组播/广播业务，则基站还可以向SMF网元发送未成功将终端1加入组播/广播业务的原因值。
如图11所示，图11示出了本申请实施例提供的另一种组播配置无线承载的方法的具体实施例，该方法与图10所示的方法的区别在于，在图11所示的实施例中需要对组播/广播业务的数据执行安全保护，该方法包括：
步骤1101～步骤1103，同步骤1001～步骤1003，此处不再赘述。
区别在于，在步骤1003中SMF网元还从创建该组播会话的核心网网元处或从应用网元(可通过其他网元获取，如通过PCF网元/NEF网元从应用网元处获取)处获取了组播会话的安全参数，包括组播会话所使用的安全算法、组播会话所使用的安全 秘钥等。
具体的，SMF网元可以将组播会话的安全参数作为该组播/广播业务的参数。
步骤1104、SMF网元向基站发送请求消息3，相应的，基站接收来自SMF网元的请求消息3。该请求消息3用于请求将终端1加入组播/广播业务。为了支持加密，在本申请实施例的步骤1104中还可以携带该组播/广播业务的安全密钥，可选的，请求消息3中还可以包括对该组播/广播业务执行加密和/或完整性保护所使用的安全算法。例如，安全算法包括加密算法和/或完整性保护算法。
可选的，SMF网元在请求消息3中可指示基站对该组播/多播业务进行加密和/或完整性保护。例如，请求消息3中包括加密保护指示和/或完整性保护指示。其中，加密保护指示用于指示对该组播/广播业务的数据进行加密。完整性保护指示用于指示对该组播/多播业务的数据进行完整性保护。
或者可选的，在请求消息3中不包括上述指示基站对该组播/多播业务进行加密和/或完整性保护，由为该组播/广播业务创建组播会话的核心网网元将安全密钥和/或对该组播/广播业务执行加密和/或完整性保护所使用的安全算法发送给基站。可选的，该核心网网元可指示基站对该组播/多播业务进行加密和/或完整性保护，这样基站也可以确定对该组播/广播业务的数据进行加密和/或对该组播/多播业务的数据进行完整性保护。
步骤1105～步骤1108，同步骤1005～步骤1008，此处不再赘述。
如果创建组播会话的网元指示该组播会话需要执行安全保护，则核心网网元还将该组播/广播业务对应的安全参数发送给基站，以便基站将组播/广播业务对应的组播无线承载配置为进行安全保护。此外，核心网网元还需要为基站配置该组播无线承载对应的加密和/或完整性保护所使用的安全算法。
当组播/广播业务需要执行安全保护时，基站可以通过以下方式向终端1指示在组播无线承载上传输的数据需要执行安全保护。
方法三、组播无线承载的配置信息中包括第四指示信息，该第四指示信息用于指示组播无线承载需要执行安全保护。这样便于终端1接收到组播无线承载的配置信息之后，确定后续在该组播无线承载上传输的数据已执行安全保护。
若组播无线承载需要执行完整性保护，则组播无线承载的配置信息中包括完整性指示，用于指示对该组播无线承载已进行完整性保护。若组播无线承载需要执行加密，则组播无线承载的配置信息中包括加密保护指示。该加密保护指示用于指示该组播无线承载已加密。若组播无线承载需要执行加密和完整性保护，则组播无线承载的配置信息中包括加密保护指示和完整性保护指示。同时，若组播无线承载需要执行需要加密和/或完整性保护，则该组播无线承载的配置信息中还可包括加密和/或完整性保护对应的安全算法。可以在组播会话的一个组播无线承载的配置信息包括安全算法(组播会话共享安全算法)，或者，也可以在组播会话对应的全部无线承载的配置信息都包括安全算法(组播会话可以不共享安全算法或共享安全算法)，或者，安全参数可包括在组播无线承载的配置信息之外，并被所有该组播会话(即该组播/广播业务)的所有组播无线承载共享。本申请实施例中组播无线承载需要执行加密可以理解为：在组播无线承载上传输的数据需要执行加密保护。
除此之外，基站将SMF网元发送给终端1的NAS消息发送给终端1，可选的，该NAS消息中可包括组播会话的加密密钥和/或完整性保护所使用的安全参数。若NAS消息中携带组播会话的加密密钥和/或完整性保护所使用的安全参数，则终端1根据NAS消息中的加密密钥和/或完整性保护所使用的完整性密钥、组播无线承载的配置信息中的安全算法、组播无线承载的配置信息中的加密保护指示、完整性保护指示确定是否需要对组播/多业务的数据进行解密以及如何进行解密，是否进行完整性验证、以及如何进行完整性验证。终端1还根据组播无线承载的配置信息中的组播/广播业务标识和NAS消息中的组播会话的标识确定组播/广播业务对应的加密密钥和/或完整性保护所使用的完整性密钥。
可以理解的是，该组播/广播业务的数据进行加密和完整性保护所使用的安全参数与对PDU会话的其他数据流所使用的加密和完整性保护使用的安全参数不同。
方法四、基站向终端1发送组播/广播无线承载对应的安全参数。这样终端1接收到组播/广播无线承载对应的安全参数便可以确定后续用于发送该组播/广播业务的组播无线承载上的数据已执行安全保护。此时，组播无线承载的配置信息中包括该组播无线承载所对应的组播/广播业务的标识，以便终端1将该组播/广播业务的安全参数与该组播无线承载进行关联。
在方法三或方法四中组播无线承载的SDAP配置信息中还可包括PDU会话标识，以便将组播无线承载与PDU会话关联，但即使该组播无线承载与PDU会话关联，也可以与该PDU会话的其他非组播无线承载使用不同的加密策略和完整性保护策略。
上述主要从各个网元之间交互的角度对本申请实施例的方案进行了介绍。可以理解的是，各个网元，例如基站、第一终端等为了实现上述功能，其包括了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例基站、第一终端进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
上面结合图6至图11，对本申请实施例的方法进行了说明，下面对本申请实施例提供的执行上述方法的通信装置进行描述。本领域技术人员可以理解，方法和装置可以相互结合和引用，本申请实施例提供的一种通信装置可以执行上述配置无线承载的方法和无线资源的配置方法中由基站执行的方法。或者该通信装置可以执行上述实施例中的上述配置无线承载的方法和无线资源的配置方法中由第一终端执行的方法。
下面以采用对应各个功能划分各个功能模块为例进行说明：
如图12所示，图12示出了本申请实施例提供的通信装置的结构示意图，该通信装置包括：通信单元101和处理单元102。其中，通信单元101用于支持通信装置执 行信息发送或接收的步骤。处理单元102用于支持通信装置执行信息处理的步骤。
一种示例，该通信装置可以为基站，或者该通信装置可以为应用于基站的部件(例如，芯片)，该通信单元101用于该通信装置与外部网元通信，例如，执行上述实施例中基站的信号收发操作。处理单元102用于执行上述实施例中基站的信号处理操作。例如，通信单元101用于执行上述实施例的步骤602中由基站执行的发送动作以及步骤601中由基站执行的接收动作。
在一种可能的实现方式中，处理单元102用于执行上述实施例中的步骤702中由基站执行的处理动作，通信单元101用于执行上述实施例中的步骤706中由基站执行的发送动作。
在一种可能的实现方式中，处理单元102用于执行上述实施例中的步骤802、步骤806、步骤808中由基站执行的处理动作，通信单元101用于执行上述实施例中的步骤806以及步骤809中由基站执行的发送动作。
在一种可能的实现方式中，该通信单元101还用于执行上述实施例的步骤902中由基站执行的发送动作以及步骤901中由基站执行的接收动作。
另一种示例，该通信装置可以为基站，或者该通信装置可以为应用于基站的部件(例如，芯片)，该通信单元101用于该通信装置与外部网元通信，例如，执行上述实施例中基站的信号收发操作。处理单元102用于执行上述实施例中基站的信号处理操作。例如，通信单元101用于支持该通信装置执行上述实施例的步骤902中由基站执行的发送动作以及步骤901中由基站执行的接收动作。
在一种可能的实现方式中，通信单元101还用于支持该通信装置执行上述实施例的步骤602中由基站执行的发送动作以及步骤601中由基站执行的接收动作。
在一种可能的实现方式中，处理单元102还用于支持该通信装置执行上述实施例中的步骤702中由基站执行的处理动作，通信单元101还用于支持该通信装置执行上述实施例中的步骤706中由基站执行的发送动作。
在一种可能的实现方式中，处理单元102还用于支持该通信装置执行上述实施例中的步骤802、步骤806、步骤808中由基站执行的处理动作，通信单元101还用于支持该通信装置执行上述实施例中的步骤806以及步骤809中由基站执行的发送动作。
又一种示例，该通信装置可以为终端，或者该通信装置可以为应用于终端的部件(例如，芯片)，该通信单元101用于该通信装置与外部网元(例如，基站)通信，例如，执行上述实施例中第一终端的信号收发操作。处理单元102用于支持该通信装置执行上述实施例中第一终端的信号处理操作。例如，通信单元101用于支持该通信装置执行上述实施例的步骤602中由第一终端执行的接收动作。处理单元102用于执行支持该通信装置上述实施例的步骤603中由第一终端执行的处理动作。
在一种可能的实现方式中，处理单元102还用于支持该通信装置执行上述实施例中的步骤705中由第一终端执行的处理动作。通信单元101还用于支持该通信装置执行上述实施例中的步骤706中由第一终端执行的接收动作。
在一种可能的实现方式中，处理单元102用于支持该通信装置执行上述实施例中的步骤805以及步骤810中由第一终端执行的处理动作，通信单元101用于支持该通信装置执行上述实施例中的步骤807以及步骤809中由第一终端执行的接收动作。
在一种可能的实现方式中，该通信单元101还用于支持该通信装置执行上述实施例的步骤902中由第一终端执行的接收动作。处理单元102还用于支持该通信装置执行上述实施例的步骤903中由第一终端执行的处理动作。
另一种示例，该通信装置可以为第一终端，该通信单元101用于该通信装置与外部网元(例如，基站)通信，例如，执行上述实施例中第一终端的信号收发操作。处理单元102用于执行上述实施例中第一终端的信号处理操作。例如，通信单元101用于执行上述实施例的步骤902中由第一终端执行的接收动作。处理单元102用于支持该通信装置执行上述实施例中的步骤903中由第一终端执行的接收动作。
在一种可能的实现方式中，通信单元101还用于支持该通信装置执行上述实施例的步骤602中由第一终端执行的接收动作。处理单元102还用于支持该通信装置执行上述实施例的步骤603中由第一终端执行的处理动作。
在一种可能的实现方式中，处理单元102还用于支持该通信装置执行上述实施例中的步骤705中由第一终端执行的处理动作。通信单元101还用于支持该通信装置执行上述实施例中的步骤706中由第一终端执行的接收动作。
在一种可能的实现方式中，处理单元102用于支持该通信装置执行上述实施例中的步骤805以及步骤810中由第一终端执行的处理动作，通信单元101用于支持该通信装置执行上述实施例中的步骤807以及步骤809中由第一终端执行的接收动作。
可选的，通信装置还可以包括：存储单元。处理单元102、通信单元101、存储单元通过通信总线相连。
存储单元可以包括一个或者多个存储器，存储器可以是一个或者多个设备、电路中用于存储程序或者数据的器件。
存储单元可以独立存在，通过通信总线与通信装置具有的处理单元102相连。存储单元也可以和处理单元集成在一起。
通信装置可以用于通信设备、电路、硬件组件或者芯片中。
示例性的，通信装置可以是本申请实施例中的基站/第一终端中的芯片。通信单元101可以是输入或者输出接口、管脚或者电路等。可选的，存储单元可以存储发送基站/第一终端侧的方法的计算机执行指令，以使处理单元102执行上述实施例中基站/第一终端侧的方法。存储单元可以是寄存器、缓存或者RAM等，存储单元可以和处理单元102集成在一起；存储单元可以是ROM或者可存储静态信息和指令的其他类型的静态存储设备，存储单元可以与处理单元102相独立。
本申请实施例提供了一种通信装置，该通信装置包括一个或者多个模块，用于实现上述步骤601-步骤602，或步骤702、步骤706，或步骤802、步骤806、步骤808以及步骤809，或步骤901以及步骤902中由基站执行的方法，该一个或者多个模块可以与上述601-步骤602，或步骤702、步骤706，或步骤802、步骤806、步骤808以及步骤809，或步骤901以及步骤902中由基站执行的步骤相对应。具体的，本申请实施例中由基站执行的方法中的每个步骤，通信装置中存在执行该方法中每个步骤的单元或者模块。
本申请实施例提供了一种通信装置，该通信装置包括一个或者多个模块，用于实现上述步骤602-步骤603或步骤705～步骤706，或步骤805、步骤810、步骤807、步 骤809、或步骤902以及步骤903中由第一终端执行的方法，该一个或者多个模块可以与上述602-步骤603或步骤705～步骤706，或步骤805、步骤810、步骤807、步骤809、或步骤902以及步骤903中由第一终端执行的步骤相对应。具体的，本申请实施例中由第一终端执行的方法中的每个步骤，第一终端中存在执行该方法中每个步骤的单元或者模块。
示例性的，在采用集成的单元的情况下，图13示出了上述实施例中所涉及的通信装置的一种可能的逻辑结构示意图，该通信装置可以为上述实施例中发送装置。或者该通信装置可以为上述实施例中的接收装置。该通信装置包括：处理模块112和通信模块113。处理模块112用于对该通信装置的动作进行控制管理，通信模块113用于执行在通信装置侧进行消息或数据处理的步骤。
可选的，该通信装置还可以包括存储模块111，用于存储该通信装置的程序代码和数据。
一种示例，该通信装置可以为基站，或者该通信装置可以为应用于基站的部件(例如，芯片)，该通信模块113用于该通信装置与外部网元通信，例如，执行上述实施例中基站的信号收发操作。处理模块112用于执行上述实施例中基站的信号处理操作。例如，通信模块113用于执行上述实施例的步骤602中由基站执行的发送动作以及步骤601中由基站执行的接收动作。
在一种可能的实现方式中，处理模块112用于执行上述实施例中的步骤702中由基站执行的处理动作，通信模块113用于执行上述实施例中的步骤706中由基站执行的发送动作。
在一种可能的实现方式中，处理模块112用于执行上述实施例中的步骤802、步骤806、步骤808中由基站执行的处理动作，通信模块113用于执行上述实施例中的步骤806以及步骤809中由基站执行的发送动作。
在一种可能的实现方式中，该通信模块113还用于执行上述实施例的步骤902中由基站执行的发送动作以及步骤901中由基站执行的接收动作。
另一种示例，该通信装置可以为基站，或者该通信装置可以为应用于基站的部件(例如，芯片)，该通信模块113用于该通信装置与外部网元通信，例如，执行上述实施例中基站的信号收发操作。处理模块112用于执行上述实施例中基站的信号处理操作。例如，通信模块113用于支持该通信装置执行上述实施例的步骤902中由基站执行的发送动作以及步骤901中由基站执行的接收动作。
在一种可能的实现方式中，通信模块113还用于支持该通信装置执行上述实施例的步骤602中由基站执行的发送动作以及步骤601中由基站执行的接收动作。
在一种可能的实现方式中，处理模块112还用于支持该通信装置执行上述实施例中的步骤702中由基站执行的处理动作，通信模块113还用于支持该通信装置执行上述实施例中的步骤706中由基站执行的发送动作。
在一种可能的实现方式中，处理模块112还用于支持该通信装置执行上述实施例中的步骤802、步骤806、步骤808中由基站执行的处理动作，通信模块113还用于支持该通信装置执行上述实施例中的步骤806以及步骤809中由基站执行的发送动作。
又一种示例，该通信装置可以为终端，或者该通信装置可以为应用于终端的部件 (例如，芯片)，该通信模块113用于该通信装置与外部网元(例如，基站)通信，例如，执行上述实施例中第一终端的信号收发操作。处理模块112用于支持该通信装置执行上述实施例中第一终端的信号处理操作。例如，通信模块113用于支持该通信装置执行上述实施例的步骤602中由第一终端执行的接收动作。处理模块112用于执行支持该通信装置上述实施例的步骤603中由第一终端执行的处理动作。
在一种可能的实现方式中，处理模块112还用于支持该通信装置执行上述实施例中的步骤705中由第一终端执行的处理动作。通信模块113还用于支持该通信装置执行上述实施例中的步骤706中由第一终端执行的接收动作。
在一种可能的实现方式中，处理模块112用于支持该通信装置执行上述实施例中的步骤805以及步骤810中由第一终端执行的处理动作，通信模块113用于支持该通信装置执行上述实施例中的步骤807以及步骤809中由第一终端执行的接收动作。
在一种可能的实现方式中，该通信模块113还用于支持该通信装置执行上述实施例的步骤902中由第一终端执行的接收动作。处理模块112还用于支持该通信装置执行上述实施例的步骤903中由第一终端执行的处理动作。
另一种示例，该通信装置可以为第一终端，该通信模块113用于该通信装置与外部网元(例如，基站)通信，例如，执行上述实施例中第一终端的信号收发操作。处理模块112用于执行上述实施例中第一终端的信号处理操作。例如，通信模块113用于执行上述实施例的步骤902中由第一终端执行的接收动作。处理模块112用于支持该通信装置执行上述实施例中的步骤903中由第一终端执行的接收动作。
在一种可能的实现方式中，通信模块113还用于支持该通信装置执行上述实施例的步骤602中由第一终端执行的接收动作。处理模块112还用于支持该通信装置执行上述实施例的步骤603中由第一终端执行的处理动作。
在一种可能的实现方式中，处理模块112还用于支持该通信装置执行上述实施例中的步骤705中由第一终端执行的处理动作。通信模块113还用于支持该通信装置执行上述实施例中的步骤706中由第一终端执行的接收动作。
在一种可能的实现方式中，处理模块112用于支持该通信装置执行上述实施例中的步骤805以及步骤810中由第一终端执行的处理动作，通信模块113用于支持该通信装置执行上述实施例中的步骤807以及步骤809中由第一终端执行的接收动作。
其中，处理模块112可以是处理器或控制器，例如可以是中央处理器单元，通用处理器，数字信号处理器，专用集成电路，现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器也可以是实现计算功能的组合，例如包括一个或多个微处理器组合，数字信号处理器和微处理器的组合等等。通信模块113可以是通信接口、收发器、收发电路或接口电路等。存储模块111可以是存储器。
当处理模块112为处理器41或处理器45，通信模块113为收发器43时，存储模块111为存储器42时，本申请所涉及的该通信装置可以为图5所示的通信设备。
图14是本申请实施例提供的芯片150的结构示意图。芯片150包括一个或两个以上(包括两个)处理器1510和通信接口1530。
可选的，该芯片150还包括存储器1540，存储器1540可以包括只读存储器和随机存取存储器，并向处理器1510提供操作指令和数据。存储器1540的一部分还可以包括非易失性随机存取存储器(non-volatile random access memory，NVRAM)。
在一些实施方式中，存储器1540存储了如下的元素，可执行模块或者数据结构，或者他们的子集，或者他们的扩展集：
在本发明实施例中，通过调用存储器1540存储的操作指令(该操作指令可存储在操作系统中)，执行相应的操作。
一种可能的实现方式中为：基站、第一终端所用的芯片的结构类似，不同的装置可以使用不同的芯片以实现各自的功能。
处理器1510控制发送装置、接收装置的操作，处理器1510还可以称为中央处理单元(central processing unit，CPU)。存储器1540可以包括只读存储器和随机存取存储器，并向处理器1510提供指令和数据。存储器1540的一部分还可以包括非易失性随机存取存储器(non-volatile random access memory，NVRAM)。例如应用中存储器1540、通信接口1530以及存储器1540通过总线系统1520耦合在一起，其中总线系统1520除包括数据总线之外，还可以包括电源总线、控制总线和状态信号总线等。但是为了清楚说明起见，在图14中将各种总线都标为总线系统1520。
以上通信单元可以是一种该装置的接口电路或通信接口，用于从其它装置接收信号。例如，当该装置以芯片的方式实现时，该通信单元是该芯片用于从其它芯片或装置接收信号或发送信号的接口电路或通信接口。
示例性的，通信单元可以包括发送单元和接收单元。其中，发送单元用于向其它装置发送信号。接收单元用于从其它装置接收信号。
上述本申请实施例揭示的方法可以应用于处理器1510中，或者由处理器1510实现。处理器1510可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器1510中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1510可以是通用处理器、数字信号处理器(digital signal processing，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field-programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本发明实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器1540，处理器1510读取存储器1540中的信息，结合其硬件完成上述方法的步骤。
一种可能的实现方式中，通信接口1530用于执行图6～图9所示的实施例中的基站、第一终端的接收和发送的步骤。处理器1510用于执行图6～图9所示的实施例中的基站、第一终端的处理的步骤。
在上述实施例中，存储器存储的供处理器执行的指令可以以计算机程序产品的形式实现。计算机程序产品可以是事先写入在存储器中，也可以是以软件形式下载并安 装在存储器中。
计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一计算机可读存储介质传输，例如，计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存储的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘solid state disk，SSD)等。
本申请实施例还提供了一种计算机可读存储介质。上述实施例中描述的方法可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。如果在软件中实现，则功能可以作为一个或多个指令或代码存储在计算机可读介质上或者在计算机可读介质上传输。计算机可读介质可以包括计算机存储介质和通信介质，还可以包括任何可以将计算机程序从一个地方传送到另一个地方的介质。存储介质可以是可由计算机访问的任何目标介质。
作为一种可选的设计，计算机可读介质可以包括RAM，ROM，EEPROM，CD-ROM或其它光盘存储器，磁盘存储器或其它磁存储设备，或目标于承载的任何其它介质或以指令或数据结构的形式存储所需的程序代码，并且可由计算机访问。而且，任何连接被适当地称为计算机可读介质。例如，如果使用同轴电缆，光纤电缆，双绞线，数字用户线(DSL)或无线技术(如红外，无线电和微波)从网站，服务器或其它远程源传输软件，则同轴电缆，光纤电缆，双绞线，DSL或诸如红外，无线电和微波之类的无线技术包括在介质的定义中。如本文所使用的磁盘和光盘包括光盘(CD)，激光盘，光盘，数字通用光盘(DVD)，软盘和蓝光盘，其中磁盘通常以磁性方式再现数据，而光盘利用激光光学地再现数据。上述的组合也应包括在计算机可读介质的范围内。
一方面，提供一种计算机可读存储介质，计算机可读存储介质中存储有指令，当指令被运行时，实现如图6中基站的功能。
在一种可能的实施例中，当指令被运行时，还可以实现如图7～图8以及图9中基站的功能。
一方面，提供一种计算机可读存储介质，计算机可读存储介质中存储有指令，当指令被运行时，实现如图6中第一终端的功能。
在一种可能的实施例中，当指令被运行时，该计算机可读存储介质还可以实现如图7～图9中第一终端的功能。
一方面，提供一种计算机可读存储介质，计算机可读存储介质中存储有指令，当指令被运行时，实现如图9中基站的功能。
在一种可能的实施例中，当指令被运行时，还可以实现如图6～图8中基站的功能。
一方面，提供一种计算机可读存储介质，计算机可读存储介质中存储有指令，当 指令被运行时，实现如图9中第一终端的功能。
在一种可能的实施例中，当指令被运行时，还可以实现如图6～图8中第一终端的功能。
本申请实施例还提供了一种计算机程序产品。上述实施例中描述的方法可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。如果在软件中实现，可以全部或者部分得通过计算机程序产品的形式实现。计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行上述计算机程序指令时，全部或部分地产生按照上述方法实施例中描述的流程或功能。上述计算机可以是通用计算机、专用计算机、计算机网络、基站、终端或者其它可编程装置。
一方面，提供一种包括指令的计算机程序产品，计算机程序产品中包括指令，当指令被运行时，实现如图6中基站的功能。
在一种可能的实施例中，当指令被运行时，该包括指令的计算机程序产品还可以实现如图7～图9中基站的功能。
又一方面，提供一种包括指令的计算机程序产品，计算机程序产品中包括指令，当指令被运行时，实现如图6中第一终端的功能。
在一种可能的实施例中，当指令被运行时，该包括指令的计算机程序产品还可以实现如图7～图9中第一终端的功能。
又一方面，提供一种包括指令的计算机程序产品，计算机程序产品中包括指令，当指令被运行时，实现如图9中基站的功能。
在一种可能的实施例中，当指令被运行时，该包括指令的计算机程序产品还可以实现如图6～图8中基站的功能。
又一方面，提供一种包括指令的计算机程序产品，计算机程序产品中包括指令，当指令被运行时，实现如图9中第一终端的功能。
在一种可能的实施例中，当指令被运行时，该包括指令的计算机程序产品还可以实现如图6～图8中第一终端的功能。
一方面，提供一种芯片，该芯片应用于第一终端中，芯片包括至少一个处理器和通信接口，通信接口和至少一个处理器耦合，处理器用于运行指令，以实现如图6中第一终端的功能。
在一种可能的实现方式中，该芯片中的处理器还用于运行指令，以实现如图7～图9中第一终端的功能。
又一方面，提供一种芯片，该芯片应用于基站中，芯片包括至少一个处理器和通信接口，通信接口和至少一个处理器耦合，处理器用于运行指令，以实现如图6中基站的功能。
在一种可能的实现方式中，该芯片中的处理器还用于运行指令，以实现如图7～图9中基站的功能。
又一方面，提供一种芯片，该芯片应用于第一终端中，芯片包括至少一个处理器和通信接口，通信接口和至少一个处理器耦合，处理器用于运行指令，以实现如图9中第一终端的功能。
在一种可能的实现方式中，该芯片中的处理器还用于运行指令，以实现如图6～图 8中第一终端的功能。
又一方面，提供一种芯片，该芯片应用于第一终端中，芯片包括至少一个处理器和通信接口，通信接口和至少一个处理器耦合，处理器用于运行指令，以实现如图9中基站的功能。
在一种可能的实现方式中，该芯片中的处理器还用于运行指令，以实现如图6～图8中基站的功能。
本申请实施例提供一种通信系统，该通信系统包括基站以及第一终端，其中，基站用于执行图6～图8中由基站执行的步骤，第一终端用于执行图6～图8中由第一终端执行的步骤。在一种可能的实现方式中，基站还用于执行图9中由基站执行的步骤，第一终端用于执行图9中由第一终端执行的步骤。
本申请实施例提供一种通信系统，该通信系统包括基站以及第一终端，其中，基站用于执行图9中由基站执行的步骤，第一终端用于执行图9中由第一终端执行的步骤。
在一种可能的实现方式中，基站还用于执行图6～图8中由基站执行的步骤，第一终端还用于执行图6～图8中由第一终端执行的步骤。
以上所述的具体实施方式，对本发明的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本发明的具体实施方式而已，并不用于限定本发明的保护范围，凡在本发明的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本发明的保护范围之内。

Claims (46)

  1. 一种配置无线承载的方法，其特征在于，包括：
    基站接收第一请求消息，所述第一请求消息用于请求将第一终端加入组播/广播业务；
    所述基站根据所述组播/广播业务的服务质量QoS流信息，向所述第一终端发送组播无线承载的配置信息；
    其中，所述配置信息用于配置组播无线承载，所述组播无线承载用于向已加入所述组播/广播业务的终端传输所述组播/广播业务的数据，所述已加入所述组播/广播业务的终端包括所述第一终端。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述基站接收第二请求消息，所述第二请求消息用于请求将第二终端加入所述组播/广播业务；
    所述基站向所述第二终端发送所述配置信息；
    所述已加入所述组播/广播业务的终端还包括所述第二终端。
  3. 根据权利要求1或2所述的方法，其特征在于，所述配置信息包括以下信息的一种或多种：第一指示信息，所述组播/广播业务的标识，所述组播/广播业务关联的组播会话的标识，或所述组播无线承载映射的第一逻辑信道的标识；
    其中，所述第一指示信息用于指示所述配置信息用于配置的所述组播无线承载的类型为组播类型。
  4. 根据权利要求1～3任一项所述的方法，其特征在于，所述方法还包括：
    所述基站确定对所述组播/广播业务的数据不执行安全保护；
    相应的，所述组播无线承载的配置信息包括第二指示信息，所述第二指示信息用于指示在所述组播无线承载上传输的所述组播/广播业务的数据不执行安全保护。
  5. 根据权利要求4所述的方法，其特征在于，所述基站确定对所述组播/广播业务的数据不执行安全保护，包括：
    所述基站接收来自核心网网元的第三指示信息，所述第三指示信息用于指示对所述组播/广播业务的数据不执行安全保护；
    所述基站根据所述第三指示信息，确定对所述组播/广播业务的数据不执行安全保护。
  6. 根据权利要求1～3任一项所述的方法，其特征在于，所述方法还包括：
    所述基站确定对所述组播/广播业务的数据执行安全保护；
    相应的，所述组播无线承载的配置信息包括第四指示信息，所述第四指示信息用于指示在所述组播无线承载上传输的所述组播/广播业务的数据已执行安全保护。
  7. 根据权利要求6所述的方法，其特征在于，所述基站确定所述组播/广播业务的数据执行安全保护，包括：
    所述基站接收来自核心网网元的第五指示信息，所述第五指示信息用于指示对所述组播/广播业务的数据执行安全保护；
    所述基站根据所述第五指示信息，确定对所述组播/广播业务的数据执行安全保护。
  8. 根据权利要求7所述的方法，其特征在于，所述方法还包括：
    所述基站接收来自核心网网元的所述组播/广播业务对应的安全参数，所述安全参数包括安全密钥和/或安全算法，所述安全参数用于对所述组播/广播业务的数据进行安全保护；
    所述基站根据所述安全参数，获得安全保护后的所述组播/广播业务的数据；
    所述基站在所述组播无线承载上向所述第一终端发送所述安全保护后的所述组播/广播业务的数据。
  9. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    所述基站向所述第一终端发送所述安全参数。
  10. 根据权利要求1～9任一项所述的方法，其特征在于，所述方法还包括：
    所述基站向所述第一终端发送第一媒体接入控制MAC实体的配置信息，所述第一MAC实体的配置信息用于配置所述组播/广播业务对应的第一MAC实体。
  11. 根据权利要求10所述的方法，其特征在于，所述第一MAC实体的配置信息包括第六指示信息，所述第六指示信息用于指示所述第一MAC实体用于传输所述组播/广播业务的数据。
  12. 根据权利要求10或11所述的方法，其特征在于，所述第一MAC实体的配置信息还包括第一无线网络临时标识RNTI，所述第一RNTI与所述组播/广播业务对应或所述第一RNTI与所述第一终端对应。
  13. 一种配置无线承载的方法，其特征在于，包括：
    第一终端接收来自基站的组播无线承载的配置信息，所述配置信息用于配置组播无线承载，所述组播无线承载用于向已加入所述组播/广播业务的终端传输所述组播/广播业务的数据，所述已加入所述组播/广播业务的终端包括所述第一终端；
    所述第一终端根据所述配置信息，配置所述组播无线承载。
  14. 根据权利要求13所述的方法，其特征在于，所述配置信息包括以下信息的一种或多种：第一指示信息，所述组播/广播业务的标识，所述组播/广播业务关联的组播会话的标识，或，所述组播无线承载映射的第一逻辑信道的标识；
    其中，所述第一指示信息用于指示所述配置信息用于配置的所述组播无线承载的类型为组播类型。
  15. 根据权利要求13或14所述的方法，其特征在于，所述配置信息包括第二指示信息，所述第二指示信息用于指示在所述组播无线承载上传输的所述组播/广播业务的数据未执行安全保护；
    所述第一终端根据所述第二指示信息，确定对在所述组播无线承载上传输的所述组播/广播业务的数据未执行安全保护。
  16. 根据权利要求13或14所述的方法，其特征在于，所述配置信息包括第三指示信息，所述第三指示信息用于指示对在所述组播无线承载上传输的所述组播/广播业务的数据已执行安全保护。
  17. 根据权利要求16所述的方法，其特征在于，所述方法还包括：
    所述第一终端接收所述组播/广播业务对应的安全参数，所述安全参数包括安全密钥和/或安全算法，所述安全参数用于对所述组播/广播业务的数据进行安全保护。
  18. 根据权利要求17所述的方法，其特征在于，所述方法还包括：
    所述第一终端在所述组播无线承载上接收安全保护后的所述组播/广播业务的数据；
    所述第一终端根据所述安全参数和所述安全保护后的所述组播/广播业务的数据，获得所述组播/广播业务的数据。
  19. 根据权利要求13～18任一项所述的方法，其特征在于，所述方法还包括：
    所述第一终端接收来自所述基站的第一媒体接入控制MAC实体的配置信息，所述第一MAC实体的配置信息用于配置所述组播/广播业务对应的MAC实体；
    所述第一终端根据所述第一MAC实体的配置信息，配置所述组播/广播业务对应的第一MAC实体。
  20. 根据权利要求19所述的方法，其特征在于，所述第一MAC实体的配置信息包括第六指示信息，所述第六指示信息用于指示所述第一MAC实体用于传输所述组播/广播业务的数据。
  21. 根据权利要求19或20所述的方法，其特征在于，所述第一MAC实体的配置信息包括所述第一MAC实体对应的第一无线网络临时标识RNTI，所述第一RNTI与所述组播/广播业务对应或所述第一RNTI与所述第一终端对应。
  22. 一种通信装置，其特征在于，包括：通信单元，用于接收第一请求消息，所述第一请求消息用于请求将第一终端加入组播/广播业务；
    处理单元，用于根据所述组播/广播业务的服务质量QoS流信息，利用所述通信单元向所述第一终端发送组播无线承载的配置信息；
    其中，所述配置信息用于配置组播无线承载，所述组播无线承载用于向已加入所述组播/广播业务的终端传输所述组播/广播业务的数据，所述已加入所述组播/广播业务的终端包括所述第一终端。
  23. 根据权利要求22所述的装置，其特征在于，所述通信单元，还用于接收第二请求消息，所述第二请求消息用于请求将第二终端加入所述组播/广播业务；
    所述通信单元，还用于向所述第二终端发送所述配置信息；
    所述已加入所述组播/广播业务的终端还包括所述第二终端。
  24. 根据权利要求22或23所述的装置，其特征在于，所述配置信息包括以下信息的一种或多种：第一指示信息，所述组播/广播业务的标识，所述组播/广播业务关联的组播会话的标识，或所述组播无线承载映射的第一逻辑信道的标识；
    其中，所述第一指示信息用于指示所述配置信息用于配置的所述组播无线承载的类型为组播类型。
  25. 根据权利要求22～24任一项所述的装置，其特征在于，所述处理单元，还用于确定对所述组播/广播业务的数据不执行安全保护；
    相应的，所述组播无线承载的配置信息包括第二指示信息，所述第二指示信息用于指示在所述组播无线承载上传输的所述组播/广播业务的数据不执行安全保护。
  26. 根据权利要求25所述的装置，其特征在于，所述通信单元，还用于接收来自核心网网元的第三指示信息，所述第三指示信息用于指示对所述组播/广播业务的数据不执行安全保护；
    所述处理单元，用于根据所述第三指示信息，确定对所述组播/广播业务的数据不 执行安全保护。
  27. 根据权利要求22～24任一项所述的装置，其特征在于，所述处理单元，还用于确定对所述组播/广播业务的数据执行安全保护；
    相应的，所述组播无线承载的配置信息包括第四指示信息，所述第四指示信息用于指示在所述组播无线承载上传输的所述组播/广播业务的数据已执行安全保护。
  28. 根据权利要求27所述的装置，其特征在于，所述通信单元，还用于接收来自核心网网元的第五指示信息，所述第五指示信息用于指示对所述组播/广播业务的数据执行安全保护；
    所述处理单元，还用于根据所述第五指示信息，确定对所述组播/广播业务的数据执行安全保护。
  29. 根据权利要求28所述的装置，其特征在于，所述通信单元，还用于接收来自核心网网元的所述组播/广播业务对应的安全参数，所述安全参数包括安全密钥和/或安全算法，所述安全参数用于对所述组播/广播业务的数据进行安全保护；
    所述处理单元，用于根据所述安全参数，获得安全保护后的所述组播/广播业务的数据；
    所述通信单元，还用于在所述组播无线承载上向所述第一终端发送所述安全保护后的所述组播/广播业务的数据。
  30. 根据权利要求29所述的装置，其特征在于，所述通信单元，还用于向所述第一终端发送所述安全参数。
  31. 根据权利要求22～30任一项所述的装置，其特征在于，所述通信单元，还用于向所述第一终端发送第一媒体接入控制MAC实体的配置信息，所述第一MAC实体的配置信息用于配置所述组播/广播业务对应的第一MAC实体。
  32. 根据权利要求31所述的装置，其特征在于，所述第一MAC实体的配置信息包括第六指示信息，所述第六指示信息用于指示所述第一MAC实体用于传输所述组播/广播业务的数据。
  33. 根据权利要求31～32任一项所述的装置，其特征在于，所述第一MAC实体的配置信息还包括第一无线网络临时标识RNTI，所述第一RNTI与所述组播/广播业务对应或所述第一RNTI与所述第一终端对应。
  34. 一种通信装置，其特征在于，包括：
    通信单元，用于接收来自基站的组播无线承载的配置信息，所述配置信息用于配置组播无线承载，所述组播无线承载用于向已加入所述组播/广播业务的终端传输所述组播/广播业务的数据，所述已加入所述组播/广播业务的终端包括所述装置；
    处理单元，用于根据所述配置信息，配置所述组播无线承载。
  35. 根据权利要求34所述的装置，其特征在于，所述配置信息包括以下信息的一种或多种：第一指示信息，所述组播/广播业务的标识，所述组播/广播业务关联的组播会话的标识，或，所述组播无线承载映射的第一逻辑信道的标识；
    其中，所述第一指示信息用于指示所述配置信息用于配置的所述组播无线承载的类型为组播类型。
  36. 根据权利要求34～35任一项所述的装置，其特征在于，所述配置信息包括第 二指示信息，所述第二指示信息用于指示在所述组播无线承载上传输的所述组播/广播业务的数据未执行安全保护；
    所述处理单元，还用于根据所述第二指示信息，确定在所述组播无线承载上传输的所述组播/广播业务的数据未执行安全保护。
  37. 根据权利要求34～35任一项所述的装置，其特征在于，所述配置信息包括第三指示信息，所述第三指示信息用于指示在所述组播无线承载上传输的所述组播/广播业务的数据已执行安全保护。
  38. 根据权利要求37所述的装置，其特征在于，所述通信单元，还用于接收所述组播/广播业务对应的安全参数，所述安全参数包括安全密钥和/或安全算法，所述安全参数用于对所述组播/广播业务的数据进行安全保护。
  39. 根据权利要求38所述的装置，其特征在于，所述通信单元，还用于在所述组播无线承载上接收安全保护后的所述组播/广播业务的数据；
    所述处理单元，用于根据所述安全参数和所述安全保护后的所述组播/广播业务的数据，获得所述组播/广播业务的数据。
  40. 根据权利要求34～39任一项所述的装置，其特征在于，所述通信单元，还用于接收来自所述基站的第一媒体接入控制MAC实体的配置信息，所述第一MAC实体的配置信息用于配置所述组播/广播业务对应的MAC实体；
    所述处理单元，还用于根据所述第一MAC实体的配置信息，配置所述组播/广播业务对应的第一MAC实体。
  41. 根据权利要求40所述的装置，其特征在于，所述第一MAC实体的配置信息包括第六指示信息，所述第六指示信息用于指示所述第一MAC实体用于传输所述组播/广播业务的数据。
  42. 根据权利要求40或41所述的装置，其特征在于，所述第一MAC实体的配置信息包括所述第一MAC实体对应的第一无线网络临时标识RNTI，所述第一RNTI与所述组播/广播业务对应或所述第一RNTI与所述装置对应。
  43. 一种通信系统，其特征在于，包括：基站以及一个或多个终端，所述基站用于执行权利要求1～12任一项所述的方法，所述终端用于执行权利要求13～21任一项所述的方法。
  44. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有指令，当所述指令被运行时，实现上述权利要求1～12任一项所述的方法，或者实现权利要求13～21任一项所述的方法。
  45. 一种通信装置，其特征在于，包括：至少一个处理器，所述至少一个处理器与存储器耦合，所述存储器中存储有指令，所述处理器运行所述指令，以实现权利要求1～12任一项所述的方法，或者，以实现用于执行权利要求13～21任一项所述的方法。
  46. 一种芯片，其特征在于，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行计算机程序或指令，以实现如权利要求1～12任一项所述的方法，或者，以实现权利要求13～21任一项所述的方法，所述通信接口用于与所述芯片之外的其它模块进行通信。
PCT/CN2020/133362 2020-03-27 2020-12-02 一种配置无线承载的方法、装置及系统 WO2021189933A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20927148.5A EP4114127A4 (en) 2020-03-27 2020-12-02 METHOD, APPARATUS AND SYSTEM FOR CONFIGURING A RADIO CARRIER
US17/952,596 US20230013500A1 (en) 2020-03-27 2022-09-26 Radio bearer configuration method, apparatus, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010228271.8A CN113518315B (zh) 2020-03-27 2020-03-27 一种配置无线承载的方法、装置及系统
CN202010228271.8 2020-03-27

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/952,596 Continuation US20230013500A1 (en) 2020-03-27 2022-09-26 Radio bearer configuration method, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2021189933A1 true WO2021189933A1 (zh) 2021-09-30

Family

ID=77891532

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/133362 WO2021189933A1 (zh) 2020-03-27 2020-12-02 一种配置无线承载的方法、装置及系统

Country Status (4)

Country Link
US (1) US20230013500A1 (zh)
EP (1) EP4114127A4 (zh)
CN (1) CN113518315B (zh)
WO (1) WO2021189933A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11409671B2 (en) 2019-09-19 2022-08-09 Facebook Technologies, Llc Artificial reality system having multi-bank, multi-port distributed shared memory
US11520707B2 (en) * 2019-11-15 2022-12-06 Meta Platforms Technologies, Llc System on a chip (SoC) communications to prevent direct memory access (DMA) attacks
WO2024060189A1 (en) * 2022-09-23 2024-03-28 Apple Inc. New srb design for group rrc message transmission

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109769150A (zh) * 2017-11-09 2019-05-17 华为技术有限公司 一种传输组播业务的方法和设备
US20200092923A1 (en) * 2018-09-19 2020-03-19 Qualcomm Incorporated Multicast idle mode behavior and paging

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101170724B (zh) * 2006-10-27 2011-09-28 华为技术有限公司 一种承载模式转换的方法、系统及装置
CN101350948B (zh) * 2007-07-16 2011-08-24 中兴通讯股份有限公司 点到多点向点到点发送方式的切换方法
JP6503071B2 (ja) * 2015-01-30 2019-04-17 京セラ株式会社 サービングセル情報を用いる、ポイントツーマルチポイント（ｐｔｍ）互換サービスのための送信メカニズム選択
CN113411755B (zh) * 2017-12-28 2022-10-04 华为技术有限公司 一种通信方法、及相关产品

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109769150A (zh) * 2017-11-09 2019-05-17 华为技术有限公司 一种传输组播业务的方法和设备
US20200092923A1 (en) * 2018-09-19 2020-03-19 Qualcomm Incorporated Multicast idle mode behavior and paging

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Update of KI#1: MBS session management", 3GPP DRAFT; S2-2000487, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Incheon, South Korea; 20200113 - 20200117, 7 January 2020 (2020-01-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051842552 *
LG ELECTRONICS: "New MBS architecture and procedures", 3GPP DRAFT; S2-2000350, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Incheon, Korea; 20200113 - 20200117, 7 January 2020 (2020-01-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051842423 *
QUALCOMM INCORPORATED, NOKIA, NOKIA SHANGHAI BELL: "Solution: Integrated Multicast and Unicast Transport with Full Separation of MBS Service", 3GPP DRAFT; S2-2001427, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Incheon, South Korea; 20200113 - 20200117, 16 January 2020 (2020-01-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051844169 *
QUALCOMM INCORPORATED: "Architectural requirements for 5MBS", 3GPP DRAFT; S2-1910506_WAS_S2-1909901-PCR-23757_ARCHITECTURAL_REQUIREMENTS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Split, Croatia; 20191014 - 20191018, 17 October 2019 (2019-10-17), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051797180 *

Also Published As

Publication number Publication date
EP4114127A1 (en) 2023-01-04
CN113518315B (zh) 2023-03-24
US20230013500A1 (en) 2023-01-19
CN113518315A (zh) 2021-10-19
EP4114127A4 (en) 2023-09-13

Similar Documents

Publication Publication Date Title
US12010592B2 (en) Sidelink communications method and apparatus
US20200084631A1 (en) Key Configuration Method, Apparatus, and System
WO2021189933A1 (zh) 一种配置无线承载的方法、装置及系统
WO2020029938A1 (zh) 安全会话方法和装置
US11533610B2 (en) Key generation method and related apparatus
WO2020052414A1 (zh) 一种数据保护方法、设备及系统
CN110830993B (zh) 一种数据处理的方法、装置和计算机可读存储介质
WO2021164564A1 (zh) 传输组播业务的方法和装置
EP3691316A1 (en) Parameter protection method, device and system
US20230116578A1 (en) Data transmission method and apparatus
WO2022033558A1 (zh) 一种中继管理方法及通信装置
US20230019215A1 (en) TSC-5G QoS MAPPING WITH CONSIDERATION OF ASSISTANCE TRAFFIC INFORMATION AND PCC RULES FOR TSC TRAFFIC MAPPING AND 5G QoS FLOWS BINDING
WO2021135650A1 (zh) 通信方法及装置
CN113596929A (zh) 一种通信方法及装置
WO2020248709A1 (zh) 一种mdbv的确定方法、装置及系统
WO2021196051A1 (zh) 一种通信方法、装置及系统
WO2022166559A1 (zh) 通信方法及装置
WO2021031055A1 (zh) 通信方法及装置
WO2022022471A1 (zh) 一种媒体流切换方法及装置
WO2022027476A1 (zh) 密钥管理方法及通信装置
WO2020142884A1 (zh) 切换传输路径的方法及装置
US20220210690A1 (en) Data transmission method and apparatus, system, and storage medium
WO2021213000A1 (zh) 媒体报文的传输方法、装置及系统
WO2021138784A1 (zh) 一种接入网络的方法、装置及系统
WO2021212413A1 (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: 20927148

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020927148

Country of ref document: EP

Effective date: 20220927

NENP Non-entry into the national phase

Ref country code: DE