WO2021218375A1 - 承载配置方法及装置、上下文信息管理方法及装置、释放方法及装置、设备 - Google Patents
承载配置方法及装置、上下文信息管理方法及装置、释放方法及装置、设备 Download PDFInfo
- Publication number
- WO2021218375A1 WO2021218375A1 PCT/CN2021/079117 CN2021079117W WO2021218375A1 WO 2021218375 A1 WO2021218375 A1 WO 2021218375A1 CN 2021079117 W CN2021079117 W CN 2021079117W WO 2021218375 A1 WO2021218375 A1 WO 2021218375A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- bearer
- radio bearer
- mbs
- information
- configuration
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 113
- 238000007726 management method Methods 0.000 title claims abstract description 42
- 238000004891 communication Methods 0.000 claims description 55
- 238000013507 mapping Methods 0.000 claims description 34
- 230000015654 memory Effects 0.000 claims description 20
- 238000012508 change request Methods 0.000 claims description 12
- 230000006835 compression Effects 0.000 claims description 11
- 238000007906 compression Methods 0.000 claims description 11
- 238000012986 modification Methods 0.000 claims description 11
- 230000004048 modification Effects 0.000 claims description 11
- 230000005540 biological transmission Effects 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 7
- 230000006978 adaptation Effects 0.000 claims description 6
- 102100022734 Acyl carrier protein, mitochondrial Human genes 0.000 claims 34
- 101000678845 Homo sapiens Acyl carrier protein, mitochondrial Proteins 0.000 claims 34
- 238000012790 confirmation Methods 0.000 claims 1
- 230000008521 reorganization Effects 0.000 claims 1
- 230000000875 corresponding effect Effects 0.000 description 75
- 230000006870 function Effects 0.000 description 14
- 238000010586 diagram Methods 0.000 description 12
- 230000004044 response Effects 0.000 description 7
- 238000012545 processing Methods 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 5
- 230000003993 interaction Effects 0.000 description 4
- 238000010295 mobile communication Methods 0.000 description 4
- 238000011144 upstream manufacturing Methods 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 230000002596 correlated effect Effects 0.000 description 3
- 238000013500 data storage Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 230000000977 initiatory effect Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000007774 longterm Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000011084 recovery Methods 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 230000003190 augmentative effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 1
Images
Classifications
-
- 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
-
- 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
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/16—Multipoint routing
-
- 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
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
-
- 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
- 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/30—Connection release
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
- H04W76/32—Release of transport tunnels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/30—Resource management for broadcast services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/11—Allocation or use of connection identifiers
Definitions
- This application relates to the field of wireless communication networks, such as a bearer configuration method and device, a context information management method and device, a release method and device, equipment, and storage medium.
- 5G-related technologies are mainly about unicast business scenarios, that is, a point-to-point (PTP) service model.
- PTP point-to-point
- PTM point-to-multipoint
- the point-to-multipoint business model will inevitably become one of the indispensable service models. How to reasonably and effectively implement multicast broadcast services under the technical framework of 5G-New Radio Access Technology (NR) is an urgent problem to be solved.
- NR 5G-New Radio Access Technology
- This application provides methods and devices for bearer configuration, context information management methods and devices, release methods and devices, equipment, and storage media.
- the embodiment of the present application provides a bearer configuration method, which is applied to a first communication node, and includes:
- Multicast Broadcast Service MBS
- MBS Multicast Broadcast Service
- the embodiment of the present application also provides a context message management method, which is applied to a second communication node, and includes:
- the context request message includes a context establishment request message and a context change request message; the radio bearer of the MBS session is managed based on the context request message.
- the embodiment of the present application also provides a release method, including:
- release the radio bearer associated with the MBS session When the release conditions are met, release the radio bearer associated with the MBS session; release the Service Data Adaptation Protocol (SDAP) entity; where the release conditions include one or more of the following: MBS session ends; A piece of information, wherein the first piece of information carries an identifier of the radio bearer to be released.
- SDAP Service Data Adaptation Protocol
- An embodiment of the present application also provides a bearer configuration device, which is configured on a first communication node and includes:
- the receiving module is configured to receive the first information; the establishment and modification module is configured to configure the radio bearer of the MBS based on the first information; wherein the radio bearer includes a point-to-point PTP bearer and/or a point-to-multipoint PTM bearer.
- the configuration includes one or more of the following: establishment, modification, and release.
- An embodiment of the present application also provides a context message management device, which is configured on a second communication node and includes:
- the first sending module is configured to send a context request message of the first communication node; wherein the context request message includes a context establishment request message and a context change request message; the management module is configured to send a request to the MBS based on the context request message
- the radio bearer of the session is managed.
- An embodiment of the present application also provides a radio bearer release device, including:
- the first release module is configured to release the radio bearer associated with the MBS session when the release conditions are met; the second release module is configured to release the SDAP entity; wherein the release conditions include one or more of the following: MBS session ends ; Receive the first information, where the first information carries the radio bearer identification to be released.
- An embodiment of the present application also provides a device, and the device includes:
- One or more processors a memory for storing one or more programs; when the one or more programs are executed by the one or more processors, the one or more processors can realize Any one of the methods in the embodiment.
- the embodiments of the present application also provide a storage medium, where the storage medium stores a computer program, and when the computer program is executed by a processor, any one of the methods in the embodiments of the present application is implemented.
- FIG. 1 is a schematic structural diagram of a wireless network system provided by an embodiment of this application.
- FIG. 2 is a schematic flowchart of a bearer configuration method provided by an embodiment of this application.
- FIG. 3 is a schematic flowchart of a context message management method provided by an embodiment of the application.
- FIG. 4 is a schematic flowchart of a release method provided by an embodiment of the application.
- FIG. 5 is a flow chart of the control plane of the base station configuring the radio bearer for MBS for the UE;
- Fig. 6 is a flow chart of a user plane of a base station configuring a radio bearer for MBS for a UE;
- Figure 7 is a flow chart of a radio bearer establishment
- Figure 8 is a flow chart of acquiring a broadcast message
- Figure 9 is a flow chart of interaction between a base station and a terminal
- Figure 10 is a flow chart of the next generation NodeB-Central Unit (gNB-CU) sending a UE context establishment application message to the gNB-Distributed Unit (DU);
- gNB-CU next generation NodeB-Central Unit
- DU gNB-Distributed Unit
- Figure 11 is a flow chart of the gNB-CU sending a UE context change request message to the gNB-DU;
- FIG. 12 is a schematic structural diagram of a bearer configuration device provided by an embodiment of the application.
- FIG. 13 is a schematic structural diagram of a context message management apparatus provided by an embodiment of this application.
- FIG. 14 is a schematic structural diagram of a release device provided by an embodiment of the application.
- FIG. 15 is a schematic structural diagram of a device provided by an embodiment of the present application.
- GSM Global System of Mobile Communication
- CDMA Code Division Multiple Access
- Wideband Code Division Multiple Access Wideband Code Division Multiple Access
- WCDMA Wideband Code Division Multiple Access
- GPRS General Packet Radio Service
- LTE Long Term Evolution
- LIE-A Advanced long term evolution
- UMTS Universal Mobile Telecommunication System
- 5G 5th generation wireless systems
- FIG. 1 is a schematic structural diagram of a wireless network system provided by an embodiment of this application.
- the wireless network system 100 includes a base station 101, a user equipment 110, a user equipment 120, and a user equipment 130.
- the base station 101 performs wireless communication with the user equipment 110, the user equipment 120, and the user equipment 130, respectively.
- the base station may be a device that can communicate with a user terminal.
- the base station can be any device with wireless transceiver function. Including but not limited to: base station (NodeB), evolved base station (evolved NodeB, eNodeB), base station in 5G communication system, base station in future communication system, access node in wireless fidelity (Wireless Fidelity, WiFi) system, Wireless relay node, wireless backhaul node, etc.
- the base station may also be a wireless controller in a cloud radio access network (Cloud Radio Access Network, CRAN) scenario; the base station may also be a small station, a transmission reference point (TRP), etc., which are not limited in this embodiment of the application.
- CRAN Cloud Radio Access Network
- TRP transmission reference point
- the user terminal is a device with wireless transceiver function. It can be deployed on land, including indoor or outdoor, handheld, wearable, or vehicle-mounted; it can also be deployed on the water (such as a ship); it can also be deployed on In the air (for example, airplanes, balloons, satellites, etc.).
- the user terminal may be a mobile phone (mobile phone), a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, an industrial control (industrial control) Wireless terminals in ), wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, and wireless terminals in transportation safety , Wireless terminals in smart cities, wireless terminals in smart homes, etc.
- the embodiments of this application do not limit the application scenarios.
- a user terminal may sometimes be called a terminal, an access terminal, a UE unit, a UE station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a UE terminal, a wireless communication device, a UE agent, or a UE device.
- the embodiments of the application are not limited.
- the multicast broadcast service scenario is a traditional service scenario that exists to meet the needs of most users for the same service.
- 5G-related technologies are mainly about unicast business scenarios, that is, a point-to-point (PTP) service model.
- PTP point-to-point
- PTM Point-to-Multipoint
- the discussion on the standardization of the Point-to-Multipoint (PTM) service model has not yet started.
- PTM Point-to-Multipoint
- the point-to-multipoint business model will inevitably become one of the indispensable service models. Therefore, how to reasonably and effectively realize the multicast broadcast service under the 5G-NR technical framework is a problem that needs to be discussed and solved urgently.
- Mobile networks can be divided into core network (Core Network, core network), radio access network (Radio Access Network, base station) and user equipment (User Equipment, UE).
- the bearer between the radio access network and user equipment is called wireless Bearer (Radio Bearer, RB).
- Radio Bearer Radio Bearer
- user equipment in a cellular cell can receive multicast broadcast services through a radio bearer in a Point-to-Multipoint (PTM) mode.
- PTM Point-to-Multipoint
- PTM Point-to-Multipoint
- PTM Point-to-Multipoint
- PTP point-to-point
- the network needs to provide the user equipment with core network elements, wireless access network elements, user equipment, and other network elements.
- the point-to-point bearer of the user equipment needs to be determined by the core network.
- this application provides a bearer configuration method
- FIG. 2 is a schematic flowchart of a bearer configuration method provided in an embodiment of this application. This method can be applied to situations where users establish and modify radio bearers. The method can be executed by the bearer configuration device provided in the present application, and the bearer configuration device can be implemented by software and/or hardware, and the method is applied to the first communication node.
- the bearer configuration method provided by the embodiment of the present application mainly includes steps S11 and S12.
- Radio bearer includes a point-to-point PTP bearer and/or a point-to-multipoint PTM bearer
- the configuration includes one or more of the following: establishment, Modify and release.
- a point-to-point PTP bearer may refer to a unicast bearer, which may be understood as a bearer used when a base station sends data to a single first communication node (eg, UE).
- the point-to-multipoint PTM bearer may refer to a multicast or broadcast bearer, and may be understood as a bearer used when a base station sends data to a group of first communication nodes or all first communication nodes in a cell.
- the PTP mode represents the point-to-point communication mode between the first communication node and the base station.
- the bearer of the PTP mode can be a data radio bearer (DRB) or a unicast RB or a PTP radio bearer or a PTP bearer.
- the PTM mode represents a point-to-multipoint communication mode between the first communication node and the base station.
- the bearer of the PTM mode may be a multicast RB or a broadcast RB or a PTM radio bearer or a PTM bearer.
- the first communication node may be any user equipment described in the aforementioned system, and this embodiment is only for illustration and not limitation.
- the first information is sent by the base station to the user equipment.
- the base station may be any of the base stations described in the above-mentioned system, and this embodiment is only for illustration and not limitation.
- the first information includes PTP bearer configuration information
- the PTP bearer is configured based on the PTP bearer configuration information
- the PTP bearer configuration information includes one or more of the following information:
- PTP radio bearer identification service data adaptation protocol SDAP configuration information
- packet data convergence protocol Packet Data Convergence Protocol
- RLC Radio Link Control
- the first information includes second information
- a PTM bearer is configured based on the second information
- the second information includes one or more of the following:
- the second bearer configuration includes one or more of the following: PTM radio bearer identifier, logical channel identifier (Logical Channel IDentifier, LCID), SDAP configuration information, PDCP configuration information, and RLC bearer configuration information.
- PTM radio bearer identifier logical channel identifier (Logical Channel IDentifier, LCID)
- LCID Logical Channel IDentifier
- SDAP configuration information PDCP configuration information
- RLC bearer configuration information includes one or more of the following: PTM radio bearer identifier, logical channel identifier (Logical Channel IDentifier, LCID), SDAP configuration information, PDCP configuration information, and RLC bearer configuration information.
- the PTM bearer configuration information includes one or more of the following:
- the SDAP configuration information includes one or more of the following:
- the list of upstream Quality of Service (QoS) flows in the MBS session, and the list of QoS flows in the MBS session mapped to this radio bearer that need to be released.
- QoS Quality of Service
- the MBS identification information includes one or more of the following:
- MBS session identifier TMGI (Tempory Mobile Group Identity) of the multicast broadcast service
- multicast broadcast service identifier indicating the protocol data unit (PDU) session identifier of the MBS session.
- PDU protocol data unit
- the PDU session is established to be associated with the MBS session in the SDAP configuration.
- the PTP bearer configuration information carries SDAP configuration information
- one or more of the following operations are performed:
- the first bearer configuration includes one or more of the following information:
- PTM radio bearer identification logical channel identification, SDAP configuration, PDCP configuration, RLC configuration.
- the PTM bearer configuration information includes SDAP configuration information
- one or more of the following operations are performed:
- Establish a second SDAP entity ; configure the second SDAP entity based on the SDAP configuration information in the first bearer configuration and/or the second bearer configuration; establish an association between the second SDAP entity and the radio bearer corresponding to the PTP radio bearer identity; Wherein, the second SDAP entity is used for mapping between the QoS flow in the MBS identification information and the PTM radio bearer.
- the PTP bearer configuration information or the PTM bearer configuration information includes SDAP configuration information
- Establish a third SDAP entity ; configure the third SDAP entity based on SDAP configuration information; establish an association between the third SDAP entity and the PTP radio bearer identity or the radio bearer corresponding to the PTM radio bearer identity; wherein, the third SDAP The entity is used for the mapping between the QoS flow in the MBS identification information and the PTP radio bearer and PTM radio bearer.
- the PDCP configuration information includes one or more of the following:
- the PDCP entity Indicate whether to use the encryption algorithm, the timing of discarding PDCP packets, whether the PDCP entity continues or resets robust header compression (Robust Header Compression, ROHC) protocol, header compression configuration, whether the radio bearer is configured with integrity protection, header
- the maximum value of the compression context identifier (Context Identifier, CID) parameter the PDCP entity is associated with more than one RLC entity in the uplink data transmission, disorder is allowed, whether the uplink PDCP repetition is configured and activated, the downlink PDCP sequence number size, the uplink PDCP sequence number size, indication
- the cell group ID and LCID corresponding to the primary RLC entity, whether the radio bearer is configured to transmit PDCP status reports, reordering time, and the data volume threshold of the split bearer used for uplink data.
- the RLC bearer configuration information includes: LCID, radio bearer identifier served by the RLC bearer, logical channel identifier, radio bearer identifier served by the RLC bearer, RLC configuration, logical channel configuration, whether to reestablish RLC identifier, maximum number of retransmissions, poll bytes, pollPDU, sequence number (SN)-field length, timer in RLC acknowledged mode (Acknowledged Mode, AM), reassembly timer, status report timer.
- the first information is a radio resource control (Radio Resource Control, RRC) message; or, the first information is a broadcast message.
- RRC Radio Resource Control
- All QoS flows of one MBS identification information are mapped to one PTM radio bearer, and different PTM radio bearers corresponding to different MBS identification information use the same logical channel identifier.
- all QoS flows of one MBS identification information are mapped to one or more PTM radio bearers, and different PTM radio bearers of the same MBS identification information use different logical channel identifiers.
- one or more of the following operations are performed for each MBS identification information:
- the broadcast/multicast service logical channel of the radio bearer establishes the association between the PDCP entity and the broadcast/multicast service logical channel; the broadcast/multicast service logical channel uses the default logical channel identifier; establishes the PDCP entity and the broadcast service logical channel / Multicast service logical channel association.
- Establish a PDCP entity establish an RLC entity; configure a broadcast/multicast service logical channel corresponding to the PTM radio bearer identifier in the MAC entity; establish an association between the PDCP entity and the broadcast/multicast service logical channel.
- all QoS flows of one MBS session are mapped to one PTM radio bearer, and different PTM radio bearers corresponding to different MBS sessions use default logical channel identifiers.
- all QoS flows of an MBS session are mapped to one or more PTM radio bearers, and different PTM radio bearers of the same MBS session use different logical channel identifiers; for each PTM radio bearer, the The second bearer configuration includes a PTM radio bearer identifier and/or a logical channel identifier.
- an SDAP entity corresponding to the MBS session is established, and the SDAP entity is configured based on the SDAP configuration in the first bearer configuration and/or the second bearer configuration.
- the information contained in the second bearer configuration is used to perform the SDAP entity, PDCP entity, and RLC entity respectively. Configuration.
- part or all of the content in the SDAP configuration information may be in the first bearer configuration (default configuration), or part or all of the content in the second bearer configuration (obtained through the first information).
- the second bearer configuration is used to configure the related parameters.
- this application provides a context message management method
- FIG. 3 is a schematic flowchart of a context message management method provided by an embodiment of this application. This method can be applied to the situation of carrying out the bearer configuration inside the base station.
- the method may be executed by the context message management apparatus provided in the present application, and the context message management apparatus may be implemented by software and/or hardware, and the method is applied to the second communication node.
- the context message management method provided by the embodiment of the present application mainly includes steps S21 and S22.
- S21 Send a context request message of the first communication node; wherein the context request message includes a context establishment request message and a context change request message.
- the second communication node can be understood as the centralized unit (gNB-CU) in the base station, and the context request message is sent to the gNB-CU by the separate unit (gNB-DU) in the base station. That is, the context message management method provided by this application is executed by the centralized unit (gNB-CU) in the base station.
- the radio bearer list that needs to be modified includes the radio bearer information that needs to be established for the MBS session, and the radio bearer list that needs to be modified is carried by the context establishment request message, or is determined by the context. Change the application message carrying.
- the radio bearer information includes: MBS session identification information, where the MBS session identification information is associated with a radio bearer identification and a QoS flow list mapped to the radio bearer.
- the MBS identifier is associated with a radio bearer identifier and a QoS flow list mapped to the radio bearer.
- each QoS flow in the QoS flow list mapped to the radio bearer includes one or more of the following:
- QoS flow identification QoS parameters of QoS flow level, QoS flow mapping indication parameters, MBS session identification information.
- the MBS session identification information and the QoS flow identification are associated with each other.
- the QoS parameters of the QoS flow level include: MBS session identification information, which is used to indicate the MBS session to which the QoS flow belongs.
- this application provides a release method
- FIG. 4 is a schematic flowchart of a release method provided in an embodiment of this application. This method can be applied to the situation where the user equipment releases the radio bearer and SDAP. The method may be executed by the release device provided in the present application, and the release device may be implemented by software and/or hardware, and the method is applied to the first communication node.
- the release method provided by the embodiment of the present application mainly includes steps S31 and S32.
- the MBS session ends; the first message is received, where the first message carries the identification of the radio bearer to be released.
- the first communication node may be any user equipment described in the aforementioned system, and this embodiment is only for illustration and not limitation.
- the first information is sent by the base station to the user equipment.
- the base station may be any of the base stations described in the above-mentioned system, and this embodiment is only for illustration and not limitation.
- releasing the radio bearer associated with the MBS session includes:
- releasing the SDAP entity includes:
- releasing the SDAP entity includes:
- releasing the SDAP entity includes:
- the SDAP entity is released.
- an MBS session has at least one QoS flow.
- One MBS session identification information is used to uniquely distinguish one MBS session, and one QoS flow identification is used to uniquely distinguish one QoS flow in one MBS session.
- the MBS session identification information includes one or more of the following: MBS session identification, temporary mobile group identification TMGI of the multicast broadcast service, MBS identification information, and PDU session identification. All QoS flows in an MBS session may come from one MBS or multiple MBS, and one MBS identification information is used to uniquely distinguish one MBS.
- An MBS identification information contains one or more of the following information: an MBS session identification, at least one QoS flow identification list in an MBS session, an MBS identification, an Internet Protocol (IP) multicast address, and an IP source address , A TMGI.
- IP Internet Protocol
- the MBS session identification information and MBS identification information in this application refer to the same information, and they are only different in terms of expression.
- the PTP mode represents the point-to-point communication mode between the UE and the base station.
- the bearer of the PTP mode can be DRB or unicast RB or PTP radio bearer or PTP bearer.
- the PTM mode represents a point-to-multipoint communication mode between the UE and the base station.
- the bearer of the PTM mode can be a multicast RB or a broadcast RB or a PTM radio bearer or a PTM bearer.
- the base station may send the bearer configuration information of the PTP mode and/or the PTM mode to the UE, and then transmit the MBS data to the UE in the PTP or PTM mode.
- the UE can configure the bearer in the PTP mode or the bearer in the PTM mode accordingly to receive the MBS data sent by the base station.
- the configuration of the bearer includes the establishment of the bearer, the modification of the bearer, and the release of the bearer.
- FIG. 5 is a schematic diagram of a control plane flow of a bearer configuration method provided in an embodiment of this application. As shown in FIG. 5, the embodiment of the present application includes several or all of the following steps: step 510, step 511, step 520, and step 530.
- the trigger condition of the base station configuration (such as establishment, modification or release) for the MBS bearer can be any one of step 510 and step 511:
- the base station receives the MBS session management message from the core network (such as Access Management Function (AMF)).
- the MBS session management message may be one of the following information: MBS session establishment request message, MBS session start message, MBS session update message, MBS session modification request information, MBS session end message, MBS session release message.
- the MBS session establishment request message or the MBS session initiation message carries any combination of the following information: MBS session identifier, a list of MBS identification information or MBS identification information, and a list of QoS flow identifiers that need to be established in the MBS session, corresponding to each QoS
- the QoS parameters of the QoS flow class of the flow identifier are added to the UE identifier list of the MBS session.
- the following information may also be included: the identity of the cell to which the UE belongs, and/or indication information whether to use PTP or PTM to receive MBS data.
- the MBS session modification request message or the MBS session update message carries any combination of the following information: MBS session identification information, an MBS identification information or MBS identification information list, and the list of QoS flow identifications that need to be added or modified in the MBS session corresponds to The QoS parameters of the QoS flow class identified by each QoS flow are added to the UE list of the MBS session.
- the following information may also be included: the identity of the cell to which each UE belongs, and/or indication information whether to use a PTP bearer or a PTM bearer to receive MBS data.
- the MBS session release message or the MBS session end message carries MBS session identification information.
- the base station decides to release all the bearers in the MBS session.
- the base station after receiving the MBS session management message, the base station sends an MBS session management response message to the core network.
- the base station After the base station receives the MBS session establishment request message from the core network, the base station sends an MBS session establishment response message to the core network as a reply.
- the base station After the base station receives the MBS session modification request message from the core network, the base station sends an MBS session modification response message to the core network as a reply.
- the base station After the base station receives the MBS session release message from the core network, the base station sends an MBS session release response message to the core network as a reply.
- the base station After the base station receives the MBS session initiation message from the core network, the base station sends an MBS session initiation response message to the core network as a reply.
- the base station After the base station receives the MBS session update message from the core network, the base station sends an MBS session update response message to the core network as a reply. After the base station receives the MBS session end message from the core network, the base station sends an MBS session end response message to the core network as a reply.
- the base station decides to configure a bearer for the corresponding UE based on the MBS session management message and/or resource usage in step 510.
- the base station configures the radio bearer for the MBS for the UE, it needs to configure the mapping relationship between the QoS flow in the MBS session and the radio bearer.
- the bearer may be a radio bearer in PTP mode or a radio bearer in PTM mode.
- the base station may send PTP bearer configuration information including received MBS data to the UE.
- the PTP bearer configuration information may be used to instruct the UE to establish, modify, and release the PTP bearer.
- the UE configures a PTP radio bearer for MBS according to the received PTP bearer configuration information, and sends an RRC complete message to the base station.
- the base station may also send to the UE the PTM bearer configuration information corresponding to the MBS session, and the information may be sent to the UE in a broadcast or unicast manner.
- Figure 6 is a flow chart of the user plane of the base station configuring the UE for the MBS radio bearer.
- the base station receives at least one QoS flow in the MBS session from the core network and maps the QoS flow to the corresponding radio bearer ;
- the UE receives the MBS data in the corresponding radio bearer from the base station.
- a method is provided for how to map the QoS flow of an MBS session to the PTM bearer and the PTP radio bearer of different UEs within the base station.
- the process on the control plane on the base station side includes: for an MBS session, the manner in which the base station establishes a corresponding SDAP entity includes but is not limited to one or more of the following.
- Method 1 For an MBS session, the base station establishes an SDAP entity for each UE that uses the PTP radio bearer, and the SDAP entity established for a specific UE is responsible for the mapping of the QoS flow of the MBS session to the PTP radio bearer of the UE .
- the base station For an MBS session, the base station jointly establishes an SDAP entity for all UEs using the PTM radio bearer, and the SDAP entity is responsible for the mapping of the QoS flow of the MBS session to the PTM radio bearer.
- Method 3 For an MBS session, the base station establishes an SDAP entity, which is responsible for the mapping of the QoS flow of the MBS session to the radio bearer, including the mapping of the QoS flow of the MBS session to the PTP radio bearer and the QoS flow of the MBS session Mapping to PTM radio bearer.
- SDAP entity responsible for the mapping of the QoS flow of the MBS session to the radio bearer, including the mapping of the QoS flow of the MBS session to the PTP radio bearer and the QoS flow of the MBS session Mapping to PTM radio bearer.
- the process on the user plane at the base station side includes:
- the base station receives the QoS flow data in the MBS session from the core network, and delivers the received QoS flow data to each SDAP entity associated with the MBS session.
- Each SDAP entity of the base station maps the data received from the upper layer to the corresponding radio bearer, and the mapping rule is determined by the control plane.
- a method for the UE to establish an SDAP entity associated with an MBS session is provided.
- the manner in which the UE establishes an SDAP entity associated with the MBS session includes but is not limited to one or more of the following.
- Manner 1 For an MBS session, the UE establishes a first SDAP entity, and the first SDAP entity is responsible for mapping the QoS flow of the MBS session to the PTP radio bearer.
- Manner 2 For an MBS session, the UE establishes a second SDAP entity, and the second SDAP entity is responsible for mapping the QoS flow of the MBS session to the PTM radio bearer.
- Manner 3 For an MBS session, the UE establishes a third SDAP entity, and the third SDAP entity is responsible for the mapping of the QoS flow of the MBS session to the radio bearer, including the mapping of the QoS flow of the MBS session to the PTP radio bearer and the Mapping of the QoS flow of the MBS session to the PTM radio bearer.
- a method is provided for how the UE configures the PTP radio bearer for receiving MBS.
- the UE receives the radio bearer configuration information sent by the base station for receiving MBS, and the radio bearer configuration information carries any combination of the following information: radio bearer identifier (such as RB ID), cast mode indicator, SDAP Configuration, PDCP configuration, RLC bearer configuration.
- the cast mode indication includes at least one of the following: unicast, multicast, and broadcast.
- the UE receives the radio bearer configuration information sent by the base station, including a list of PTP radio bearers to be established and modified, and the list includes radio bearer (ie, DRB) information of the PTP mode used for MBS data transmission .
- the radio bearer configuration information further includes one or more of the following information: radio bearer identification (such as DRB ID), SDAP configuration, PDCP configuration, and RLC bearer configuration.
- the SDAP configuration is associated with a radio bearer identity.
- the SDAP configuration includes any combination of the following information: an indication of whether this radio bearer is the default radio bearer, whether the downlink data on this radio bearer has an indication of SDAP header, whether the uplink data of this radio bearer has an indication of SDAP header, session The identification information, the list of upstream QoS flows that need to be added and mapped to the MBS session of this radio bearer, and the list of QoS flows that need to be released that have been mapped to the MBS session of this radio bearer.
- the session identification information in the SDAP configuration is used to identify the MBS session associated with this SDAP configuration, and its design and meaning have the following three ways.
- the session identification information is a PDU session identification. Both the PDU session used for unicast services and the MBS session used for MBS are uniquely distinguished by the PDU session identifier.
- the PDU session identifier is used to identify which QoS flow of the PDU session is mapped to the radio bearer associated with the SDAP configuration.
- the session identification information is MBS session identification information. Sessions used for MBS are distinguished using the MBS session identification information, and sessions used for unicast services are distinguished using PDU session identification.
- the MBS session identification information indicates which MBS session QoS flow is mapped to the radio bearer associated with the SDAP configuration.
- the session identification information includes PDU session identification and MBS session identification information.
- the MBS session identification information indicates which MBS session QoS flow is mapped to the radio bearer associated with the SDAP configuration.
- the PDU session identifier indicates which PDU session is associated with the MBS session.
- the PDCP configuration is associated with a radio bearer identifier, and the PDCP configuration includes any combination of the following information: cipheringDisabledkey (indicating whether to use an encryption algorithm), discardTimer (the timing of discarding PDCP packets), drb-ContinueROHC (the PDCP entity is rebuilding Whether to continue or reset the ROHC protocol), headerCompression (header compression configuration), integrityProtection (whether integrity protection is configured for this radio bearer), maxCID (the maximum value of the header compression CID parameter), moreThanOneRLC (the PDCP entity in the uplink data transmission is more associated For an RLC entity), outOfOrderDelivery (out of order allowed), pdcp-Duplication (uplink PDCP repetition is configured and activated), pdcp-SN-SizeDL (downlink PDCP sequence number size), pdcp-SN-SizeUL (uplink PDCP sequence number size), primaryPath (indicating the cell group ID and LCID
- the RLC bearer configuration includes: LCID, the radio bearer identity served by the RLC bearer, the RLC configuration, the logical channel configuration, and whether to rebuild the RLC identity.
- the RLC configuration indicates the RLC mode (Unacknowledged Mode (UM), AM) used by this radio bearer and provides the parameters of the corresponding RLC mode.
- UM Unacknowledged Mode
- the RLC configuration includes any combination of the following information: maxRetxThreshold (the maximum number of retransmissions), pollByte (indicating how many bytes the AM RLC entity sender triggers poll once), pollPDU (indicating the AM RLC entity sender triggers every pollPDU every how many bytes One poll), sn-FieldLength (indicating RLC SN size), t-PollRetransmit (timer under RLC AM), t-Reassembly (reassembly timer), t-StatusProhibit (status report timer).
- maxRetxThreshold the maximum number of retransmissions
- pollByte indicating how many bytes the AM RLC entity sender triggers poll once
- pollPDU indicating the AM RLC entity sender triggers every pollPDU every how many bytes One poll
- sn-FieldLength indicating RLC SN size
- t-PollRetransmit timer under RLC AM
- a method for a UE to establish or modify a radio bearer is provided.
- the radio bearer configuration information received by the UE includes a list of PTP radio bearer identities to be established or modified, and the UE performs the following bearer establishment or bearer modification operations.
- the UE For each radio bearer identity to be established or modified included in the radio bearer configuration information, if the radio bearer is not part of the UE's existing configuration, the UE should perform one or more of the following steps:
- the SDAP entity corresponding to the session identification information does not exist before receiving the configuration information: inform the upper layer of the establishment of user plane resources for this MBS session; optionally, if the MBS session identification information includes the MBS session The identifier and the PDU session identifier are used to establish an association between this PDU session and this MBS session.
- the UE For each radio bearer identity to be established or modified included in the radio bearer configuration information, if the radio bearer is part of the UE's existing configuration, the UE should perform one or more of the following steps:
- this bearer configuration carries a PDCP recovery indication: trigger the PDCP entity of this radio bearer to perform the PDCP data recovery process.
- this bearer configuration carries the PDCP configuration: reconfigure the PDCP entity of this radio bearer according to the PDCP configuration.
- this bearer configuration carries SDAP configuration: reconfigure the SDAP entity according to the received SDAP configuration.
- a method for UE to release radio bearers is provided.
- the UE performs one or more of the following operations:
- the UE shall perform the following radio bearer release operation: For each radio bearer identity to be released, the UE shall release the PDCP entity and the radio bearer identity ; If the SDAP entity associated with this radio bearer has been configured: notify the SDAP entity associated with this radio bearer of the release of this radio bearer; when the MBS session ends, the UE should release all radio bearers associated with the MBS session .
- SDAP entity release method In an applicable implementation manner, a SDAP entity release method is provided, and the SDAP entity release related operations include one or more of the following steps:
- the UE When RRC applies to release the SDAP entity, the UE should release the SDAP entity; when the RRC indicates that a radio bearer is released, the SDAP entity should remove all QoS flows mapped to the released radio bearer.
- the UE can know the end time of the MBS session according to the context information of the MBS session. When the MBS session ends, the UE should release the SDAP entity associated with the MBS session.
- a method is provided for how the base station informs the UE of PTM bearer configuration information for receiving MBS.
- each PTM bearer configuration includes any combination of the following information: PTM radio bearer identifier, SDAP configuration, PDCP configuration, and RLC bearer configuration.
- the RLC bearer configuration includes any combination of the following information: RLC configuration, logical channel identifier, and logical channel configuration.
- the PTM bearer configuration all its information can be obtained in two ways: one way is to let the UE adopt the default configuration, this application refers to the related information obtained through the default configuration as the first bearer configuration; the other way is Let the base station send to the UE, and this application refers to part of the information obtained in this way as the second bearer configuration.
- the first bearer configuration includes part or none or all of the PTM bearer configuration.
- the second bearer configuration includes part or none or all of the PTM radio bearer information.
- the information included in the second bearer configuration is different from the information included in the PTM bearer configuration.
- the information included in the second bearer configuration may also overlap with the information included in the first bearer configuration, that is, the second bearer configuration and the first bearer configuration have the same parameters.
- the base station sends the first information to indicate the ongoing MBS session/service list in the cell and the scheduling information of the corresponding session/service.
- the first information includes one or more of the following information: MBS session identification information, wireless network temporary identification used for broadcast/multicast services, multicast service channel scheduling information, and multicast service configuration Physical layer parameters required by the channel.
- the first bearer configuration includes a default logical channel identifier and or radio bearer identifier; the MAC entity distinguishes the PTM bearers of different MBS sessions through the temporary identifier of the wireless network used for the broadcast/multicast service.
- the PTM bearer configuration only uses the default configuration. For each MBS session identification information in the received first information, the procedure for the UE to establish a corresponding PTM radio bearer includes one or more of the following steps:
- Manner 1 Notify the upper layer of the establishment of the PTM radio bearer through the corresponding MBS session identification information.
- Method 2 Establish a second SDAP entity for this MBS session.
- the second SDAP entity is used to map the QoS flow in this MBS session to the PTM radio bearer, and let this SDAP entity establish an association with this radio bearer, which will target this MBS
- the establishment of the user plane resources of the session informs the upper layer.
- a method for releasing the PTM radio bearer is provided.
- the UE When releasing the PTM radio bearer, the UE should perform one or more of the following steps:
- a release method of the SDAP entity is provided.
- the SDAP entity When releasing the PTM radio bearer, the SDAP entity should:
- the SDAP entity should release the SDAP entity associated with the PTM radio bearer.
- the first information includes one or more of the following information: MBS session identification information, wireless network temporary identification used for broadcasting/multicasting services, scheduling information for multicasting service channels, and configuring multicasting services Physical layer parameters and second bearer configuration required by the channel. All QoS flows of an MBS session are mapped to a PTM radio bearer, and different PTM radio bearers corresponding to different MBS sessions use the same logical channel identifier.
- the first bearer configuration includes a default logical channel identifier and or radio bearer identifier.
- the second bearer configuration may include any radio bearer identifier and or logical channel identifier.
- the MAC entity distinguishes the PTM bearers of different MBS sessions through the temporary identification of the wireless network used for the broadcast/multicast service.
- the procedure for the UE to establish a corresponding PTM radio bearer includes one or more of the following steps:
- Manner 1 Notify the upper layer of the establishment of the PTM radio bearer through the corresponding MBS session identification information.
- the second SDAP entity corresponding to the received MBS session identification information does not exist, the second SDAP entity is used to map the QoS flow in the MBS session to the PTM radio bearer to establish a second SDAP entity; if The SDAP entity corresponding to the MBS session identification information does not exist before receiving this configuration information, and informs the upper layer of the establishment of user plane resources for this MBS session; according to the first bearer configuration and/or the second bearer configuration 2.
- the SDAP entity is configured to establish an association between the SDAP entity and the PTM radio bearer, and notify the upper layer of the establishment of user plane resources for the MBS session.
- the configuration according to the first bearer configuration and/or the second bearer configuration includes the following methods:
- Manner 1 Use the first bearer configuration to configure the corresponding parameters of the RLC entity or the PDCP entity or the SDAP entity.
- Manner 2 Use the second bearer configuration to configure the corresponding parameters of the RLC entity or PDCP entity or SDAP entity.
- the receiving end should:
- the received first information includes the second bearer configuration: if the second bearer configuration carries the PDCP re-establishment indication, the PDCP entity is re-established according to the PDCP configuration contained in the first bearer configuration and/or the second bearer configuration; if the second bearer configuration The configuration carries the PDCP configuration, and the PDCP entity of this radio bearer is reconfigured according to the PDCP configuration included in the second bearer configuration; if the second bearer configuration carries the RLC re-establishment indication, according to the first bearer configuration and/or the second bearer configuration The included RLC configuration rebuilds the RLC entity; if the second bearer configuration carries the RLC configuration, the RLC entity of this radio bearer is reconfigured according to the RLC configuration included in the second bearer configuration; if the second bearer configuration carries the SDAP configuration, The SDAP entity is reconfigured according to the SDAP configuration included in the second bearer configuration.
- the first information includes one or more of the following information: MBS session identification information, wireless network temporary identification used for broadcasting/multicasting services, scheduling information for multicasting service channels, and configuring multicasting services Physical layer parameters and second bearer configuration required by the channel. All QoS flows of an MBS session are mapped to one or more PTM radio bearers, and different PTM radio bearers in an MBS session use different logical channel identifiers.
- the second bearer configuration includes any combination of the following information: PTM radio bearer ID, SDAP configuration, PDCP configuration, RLC bearer configuration, PTM radio bearer ID, logical channel ID.
- the value spaces of the logical channel identifier used by the PTM bearer and the logical channel identifier used by the PTP do not intersect each other, and the MAC entity distinguishes different radio bearers through the logical channel identifier.
- the MAC entity uses a radio network temporary identity for broadcast/multicast services (for example, a global system for mobile communication system radio network temporary identity (GSM-Radio Network Tempory Identity, G-RNTI)) and a logical channel identity To distinguish different radio bearers of different MBS sessions.
- GSM-Radio Network Tempory Identity GSM-Radio Network Tempory Identity
- the configuration information in the second bearer configuration is the same as the information about the second bearer configuration provided in the above-mentioned embodiments, and descriptions in other embodiments can be referred to, and details are not repeated in this embodiment.
- the procedure for UE to establish a PTM radio bearer is as follows:
- the UE should perform one or more of the following steps:
- Manner 1 Notify the upper layer of the establishment of the PTM radio bearer through the corresponding MBS session identification information.
- the second SDAP entity corresponding to the received MBS session identification information does not exist, the second SDAP entity is used to map the QoS flow in the MBS session to the PTM radio bearer to establish a second SDAP entity; if The SDAP entity corresponding to the MBS session identification information does not exist before receiving this configuration information, and informs the upper layer of the establishment of user plane resources for this MBS session; according to the first bearer configuration and/or the second bearer configuration 2.
- the SDAP entity is configured to establish an association between the SDAP entity and the PTM radio bearer, and notify the upper layer of the establishment of user plane resources for the MBS session.
- the second SDAP entity corresponding to the received MBS session identification information does not exist, the second SDAP entity is used to map the QoS flow in the MBS session to the PTM radio bearer to establish a second SDAP entity; if The SDAP entity corresponding to the MBS session identification information does not exist before receiving this configuration information, and informs the upper layer of the establishment of user plane resources for this MBS session; according to the first bearer configuration and/or the second bearer configuration 2.
- the SDAP entity is configured to establish an association between the SDAP entity and the PTM radio bearer, and notify the upper layer of the establishment of user plane resources for the MBS session.
- a release method of releasing the PTM radio bearer is provided.
- the UE receives the first information from the base station, and the first information carries a list of PTM radio bearer identifiers that need to be released or a list of MBS session identifier information corresponding to the PTM radio bearers that need to be released.
- the UE should perform one or more of the following steps:
- the UE should perform one or more of the following steps:
- a release method includes one or more of the following steps:
- the UE When RRC (such as the RRC entity in the UE) requests to release the SDAP entity, the UE should: release the SDAP entity; when the RRC (such as the RRC entity in the UE) indicates that a PTM radio bearer is released, the SDAP entity should: remove All QoS flows mapped to the released PTM radio bearer; when the MBS session ends, release one or more of the following associated with the MBS session: wireless resources, the first SDAP entity, the second SDAP entity, and the third SDAP entity , PDCP entity, RLC entity, PTP radio bearer identity, PTP radio bearer, PTM radio bearer identity and PTM radio bearer.
- FIG. 8 is a flow chart of acquiring a broadcast message. As shown in FIG. 8, the base station sends a broadcast message to the UE, and the broadcast message carries the first information.
- FIG. 9 is a flow chart of interaction between a base station and a terminal. As shown in FIG. 9, the base station sends an RRC message to the UE, and the RRC message carries first information.
- two methods for the base station to send the first information to the UE are provided.
- the method for the base station to send the first information to the UE is described, but not limited. In practical applications, you can choose either of the above two methods.
- the following embodiment provides a solution for how to manage the PTP radio bearer corresponding to the MBS on the F1 interface inside the base station (gNB-CU and gNB-DU).
- the context of the PTP RB is handed over to the UE-associated F1 Application Protocol (F1 Application Protocol, F1AP) signaling interaction.
- F1 Application Protocol F1 Application Protocol, F1AP
- the gNB-CU maintains an MBS session context (including MBS session identification information, a list of UEs that join the MBS session, and QoS parameters of the QoS flow level) and the UE context of each UE (including the PTP radio bearer list of the UE).
- MBS session context including MBS session identification information, a list of UEs that join the MBS session, and QoS parameters of the QoS flow level
- UE context of each UE including the PTP radio bearer list of the UE.
- the gNB-DU maintains a UE context (including the PTP radio bearer list of the UE) for each RRC connected UE, and maintains an MBS session context (including the PTM radio bearer list of the session).
- the PTP radio bearer is managed by the UE context, where the PTP radio bearer is associated with the MBS session corresponding to the radio bearer.
- the interaction of the PTP radio bearer on the F1 is placed in each UE Context.
- the establishment, modification, and release of the UE Context on the F1 interface need to include the Information Element (IE) for the PTP radio bearer.
- the configuration of the PTP radio bearer in the DRB to Be Setup List in the F1AP signaling includes MBS session identification information (MBS session ID/TMGI).
- Figure 10 is a flow chart of gNB-CU sending a UE context establishment request message to gNB-DU. As shown in Fig. 10, gNB-CU sends a UE context establishment request message to gNB-DU, and gNB-DU sends UE context to gNB-CU Create a reply message.
- the UE context establishment request message includes: a list of radio bearers to be established, tunnel information corresponding to the radio bearers, and other UE context information.
- the list of radio bearers to be established includes PTP radio bearer information for MBS that needs to be established, and the PTP radio bearer information for MBS includes any of the following items: radio bearer identifier, radio bearer QoS information, and network slice identifier (Single Network Slice Selection Assistance Information (S-NSSAI), Notification Control, and a list of QoS flows mapped to the radio bearer.
- S-NSSAI Single Network Slice Selection Assistance Information
- the PTP radio bearer information used for MBS includes MBS session identification information.
- the MBS session identification information is associated with the radio bearer identification and the list of QoS flows mapped to this radio bearer, indicating which session’s QoS flow is mapped to this PTP radio bearer .
- Each QoS flow in the QoS flow list mapped to the radio bearer includes any combination of the following information: indicating the QoS flow identifier mapped to the radio bearer, the QoS parameter of the QoS flow level, and the QoS flow mapping indicating the uplink or downlink Up to this radio bearer indication and MBS session identification information.
- the MBS session identification information and the QoS flow identification are correlated with each other, and indicate which QoS flow corresponding to this QoS flow identification in which MBS session is mapped to this radio bearer.
- the QoS parameter of the QoS flow level may include MBS session identification information, indicating which MBS session the related QoS flow belongs to.
- FIG 11 is a flow chart of gNB-CU sending a UE context change request message to gNB-DU. As shown in Figure 11, gNB-CU sends a UE context change request message to gNB-DU, and gNB-DU sends UE context to gNB-CU Change the reply message.
- the UE context change request message includes: a radio bearer list to be established, tunnel information corresponding to the radio bearer, a radio bearer list to be changed, and other UE context information.
- the list of radio bearers that need to be established includes PTP radio bearer information for MBS that needs to be established.
- the PTP radio bearer information for MBS includes any of the following items: radio bearer identification, radio bearer QoS information, S-NSSAI, Notification Control, and a list of QoS flows mapped to the radio bearer.
- the PTP radio bearer information used for MBS includes MBS session identification information.
- the MBS session identification information is associated with the radio bearer identification and the list of QoS flows mapped to this radio bearer, indicating which session’s QoS flow is mapped to this PTP radio bearer .
- Each QoS flow in the QoS flow list mapped to the radio bearer includes any combination of the following information: indicating the QoS flow identifier mapped to the radio bearer, the QoS parameter of the QoS flow level, and the QoS flow mapping indicating the uplink or downlink Up to this radio bearer indication and MBS session identification information.
- the MBS session identification information and the QoS flow identification are correlated with each other, and indicate which QoS flow corresponding to this QoS flow identification in which MBS session is mapped to this radio bearer.
- the QoS parameter of the QoS flow level may include MBS session identification information, indicating which MBS session the related QoS flow belongs to.
- the list of radio bearers that need to be changed includes PTP radio bearer information for MBS that needs to be changed.
- the PTP radio bearer information for MBS includes any of the following items: radio bearer identification, radio bearer QoS information, S-NSSAI, Notification Control, and a list of QoS flows mapped to the radio bearer.
- Each QoS flow information in the QoS flow list mapped to the radio bearer includes any combination of the following information: indicating the QoS flow identifier mapped to the radio bearer, the QoS parameter of the QoS flow level, and the QoS flow mapping indicating the uplink or the downlink To this radio bearer instructions.
- the PTP radio bearer information used for MBS includes MBS session identification information.
- the MBS session identification information is associated with the radio bearer identification and the list of QoS flows mapped to this radio bearer, indicating which session’s QoS flow is mapped to this PTP radio bearer .
- Each QoS flow information in the QoS flow list mapped to the radio bearer includes MBS session identification information.
- the MBS session identification information and the QoS flow identification are correlated with each other, and indicate which QoS flow corresponding to this QoS flow identification in which MBS session is mapped to this radio bearer.
- the QoS parameter of the QoS flow level may include MBS session identification information, indicating which MBS session the related QoS flow belongs to.
- the present application provides a bearer configuration device
- FIG. 12 is a schematic structural diagram of a bearer configuration device provided in an embodiment of this application.
- the device can be suitable for users to establish and modify radio bearers.
- the bearer configuration device may be implemented by software and/or hardware, and the device is configured in the first communication node.
- the bearer configuration apparatus provided by the embodiment of the present application mainly includes a receiving module 121 and a configuration module 122.
- the receiving module 121 is configured to receive first information.
- the configuration module 122 is configured to configure a radio bearer of the multicast broadcast service MBS based on the first information, wherein the radio bearer includes a point-to-point PTP bearer and or a point-to-multipoint PTM bearer, and the configuration includes one or more of the following One: create, modify, release.
- the first information includes PTP bearer configuration information
- the PTP bearer is configured based on the PTP bearer configuration information
- the PTP bearer configuration information includes one or more of the following information:
- PTP radio bearer identification service data adaptation protocol SDAP configuration information
- packet data convergence protocol PDCP configuration information packet data convergence protocol PDCP configuration information
- RLC bearer configuration information packet data convergence protocol
- the first information includes second information
- a PTM bearer is configured based on the second information
- the second information includes one or more of the following:
- the second bearer configuration includes one or more of the following: PTM radio bearer identifier, logical channel identifier, SDAP configuration information, PDCP configuration information, and RLC bearer configuration information.
- the PTM bearer configuration information required to configure the PTM bearer includes one or more of the following:
- the SDAP configuration information includes one or more of the following:
- An indication of whether the radio bearer is the default radio bearer, whether the downlink data on the radio bearer has an indication of the SDAP header, whether the uplink data of the radio bearer has an indication of the SDAP header, the MBS identification information, and the mapping that needs to be added to this radio bearer The list of upstream QoS flows in the MBS session, and the list of QoS flows in the MBS session mapped to this radio bearer that need to be released.
- the MBS identification information includes one or more of the following:
- MBS session identifier temporary mobile group identifier TMGI of the multicast broadcast service, and multicast broadcast service identifier, indicating the PDU session identifier of the MBS session.
- the PTP bearer configuration information carries SDAP configuration information
- one or more of the following operations are performed:
- the PTM bearer configuration information includes SDAP configuration information
- one or more of the following operations are performed:
- Establish a second SDAP entity ; configure the second SDAP entity based on the SDAP configuration information in the first bearer configuration and/or the second bearer configuration; establish an association between the second SDAP entity and the radio bearer corresponding to the PTP radio bearer identity; Wherein, the second SDAP entity is used for mapping between the QoS flow in the MBS identification information and the PTM radio bearer.
- the PTP bearer configuration information or the PTM bearer configuration information includes SDAP configuration information
- Establish a third SDAP entity ; configure the third SDAP entity based on SDAP configuration information; establish an association between the third SDAP entity and the PTP radio bearer identity or the radio bearer corresponding to the PTM radio bearer identity; wherein, the third SDAP The entity is used for the mapping between the QoS flow in the MBS identification information and the PTP radio bearer and PTM radio bearer.
- the PDCP configuration information includes one or more of the following:
- the PDCP entity is associated with more than one RLC entity, random sequence is allowed, whether uplink PDCP repetition is configured and activated, downlink PDCP sequence number size, uplink PDCP sequence number size, indicating the primary RLC entity when more than one RLC entity is associated in the uplink data transmission
- the cell group ID and LCID whether this radio bearer is configured to transmit PDCP status reports, reordering time, and the data volume threshold of the split bearer used for uplink data.
- the RLC bearer configuration information includes one or more of the following: logical channel identifier, radio bearer identifier served by the RLC bearer, RLC configuration, logical channel configuration, whether to rebuild the RLC identifier, and maximum retransmission Times, poll bytes, pollPDU, SN-Field length, timer under RLC AM, reassembly timer, status report timer.
- all QoS flows of one MBS identification information are mapped to one PTM radio bearer, and different PTM radio bearers corresponding to different MBS identification information use the same logical channel identifier.
- all QoS flows of one MBS identification information are mapped to one or more PTM radio bearers, and different PTM radio bearers of the same MBS identification information use different logical channel identifiers.
- one or more of the following operations are performed for each MBS identification information:
- a PDCP entity is established for each PTM radio bearer identity; an RLC entity is established; a broadcast/multicast service logical channel corresponding to the PTM radio bearer identity is configured in the MAC entity; the PDCP is established The entity is associated with the logical channel of the broadcast/multicast service.
- the bearer configuration apparatus provided in this embodiment can execute the bearer configuration method provided in any embodiment of the present application, and has the corresponding functional modules and effects for executing the method.
- the bearer configuration method provided in any embodiment of this application please refer to the bearer configuration method provided in any embodiment of this application.
- the units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding function can be realized; in addition, the name of each functional unit is also It is just for the convenience of distinguishing each other, and is not used to limit the scope of protection of this application.
- the present application provides a context message management apparatus
- FIG. 13 is a schematic structural diagram of a context message management apparatus provided in an embodiment of this application. This method can be applied to the situation where the base station carries configuration information inside.
- the context message management device may be implemented by software and/or hardware, and the device is configured in the second communication node.
- the context message management apparatus mainly includes a first sending module 131 and a management module 132.
- the first sending module 131 is configured to send a context request message of the first communication node; wherein the context request message includes a context establishment request message and a context change request message; the management module 132 is configured to be based on the context request message Manage the radio bearer of the MBS session.
- the radio bearer list that needs to be modified includes the radio bearer information that needs to be established for the MBS session, where the radio bearer list that needs to be modified is carried by the following establishment request message, or is determined by the context Change the application message carrying.
- the radio bearer information includes: MBS session identification information, where the MBS session identification information is associated with a radio bearer identification and a QoS flow list mapped to the radio bearer.
- the MBS identifier is associated with a radio bearer identifier and a QoS flow list mapped to the radio bearer.
- each QoS flow in the QoS flow list mapped to the radio bearer includes one or more of the following:
- QoS flow identification QoS parameters of QoS flow level, QoS flow mapping indication parameters, MBS session identification information.
- the MBS session identification information and the QoS flow identification are associated with each other.
- the QoS parameters of the QoS flow level include: MBS session identification information, which is used to indicate the MBS session to which the QoS flow belongs.
- the context message management apparatus provided in this embodiment can execute the context message management method provided in any embodiment of the present application, and has the corresponding functional modules and effects for executing the method.
- the context message management method provided in any embodiment of this application please refer to the context message management method provided in any embodiment of this application.
- the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding function can be realized; in addition, the name of each functional unit It is only for the convenience of distinguishing each other, and is not used to limit the scope of protection of this application.
- the present application provides a release device
- FIG. 14 is a schematic structural diagram of a release device provided in an embodiment of the application.
- the device can be applied to the situation where the user equipment releases the radio bearer and SDAP.
- the release device may be implemented by software and/or hardware, and the device is configured in the first communication node.
- the release method provided by the embodiment of the present application mainly includes a first release module 141 and a second release module 142.
- the first release module 141 is configured to release the radio bearer associated with the MBS session when the release conditions are met; the second release module 142 is configured to release the SDAP entity; wherein the release conditions include one or more of the following: MBS The session ends; the first message is received, where the first message carries the identification of the radio bearer to be released.
- the first release module 141 is configured to release all PTP radio bearers and PTM radio bearers associated with the MBS session when the MBS session ends.
- the second release module 142 is configured to release all SDAP entities associated with the MBS session when the MBS session ends.
- the second release module 142 is configured to release all SDAP entities associated with the MBS session when the upper layer instructs to release the SDAP entity associated with the PTM radio bearer for an MBS session.
- the second release module 142 is configured to release the SDAP entity when the radio bearer associated with the SDAP entity is released.
- the release device provided in this embodiment can execute the access control method provided in any embodiment of the present application, and has the corresponding functional modules and effects for executing the method.
- the release method provided in any embodiment of this application please refer to the release method provided in any embodiment of this application.
- the various units and modules included are only divided according to the functional logic, but are not limited to the above division, as long as the corresponding function can be realized; in addition, the name of each functional unit is only In order to facilitate mutual distinction, it is not used to limit the protection scope of this application.
- FIG. 15 is a schematic structural diagram of a device provided by an embodiment of the application.
- the device includes a processor 151, a memory 152, an input device 153, an output device 154, and Communication device 155; the number of processors 151 in the device can be one or more.
- one processor 151 is taken as an example; the processor 151, memory 152, input device 153 and output device 154 in the device can be connected via a bus or Other ways of connection, Figure 15 takes the bus connection as an example.
- the memory 152 can be used to store software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the carrier configuration method in the embodiment of the present application (for example, the receiving module in the carrier configuration device). 121 and configuration module 122), and the program instructions/modules corresponding to the context message management method in the embodiment of the present application (for example, the first sending module 131 and the management module 132 in the context message management apparatus), and then implemented as in the present application
- the program instructions/modules corresponding to the release method in the example for example, the first release module 141 and the second release module 142 in the release device).
- the processor 151 executes various functional applications and data processing of the device by running software programs, instructions, and modules stored in the memory 152, that is, implements any method provided in the embodiments of the present application.
- the memory 152 may mainly include a program storage area and a data storage area.
- the program storage area may store an operating system and an application program required by at least one function; the data storage area may store data created according to the use of the device, and the like.
- the memory 152 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices.
- the memory 152 may include a memory remotely provided with respect to the processor 151, and these remote memories may be connected to the device through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
- the input device 153 may be used to receive inputted numeric or character information, and generate key signal input related to user settings and function control of the device.
- the output device 154 may include a display device such as a display screen.
- the communication device 155 may include a receiver and a transmitter.
- the communication device 155 is configured to perform information transceiving and communication according to the control of the processor 151.
- the processor 151 executes various functional applications and data processing by running programs stored in the system memory 152, such as implementing the bearer configuration method provided in the embodiments of the present application.
- the method is applied to the first communication node and includes:
- Radio bearer includes a point-to-point PTP bearer and/or a point-to-multipoint PTM bearer.
- the processor 151 may also implement the technical solution of the method for carrying configuration information provided by any embodiment of the present application.
- the hardware structure and function of the device please refer to the content explanation of this embodiment.
- the processor 151 executes various functional applications and data processing by running programs stored in the system memory 152, for example, to implement a context message management provided by the embodiments of the present application
- the method, which is applied to the second communication node includes:
- the context request message includes a context establishment request message and a context change request message; the radio bearer of the MBS session is managed based on the context request message.
- the processor 151 may also implement the technical solution of the context message management method provided by any embodiment of the present application.
- the hardware structure and function of the device please refer to the content explanation of this embodiment.
- the processor 151 executes various functional applications and data processing by running programs stored in the system memory 152, for example, to implement a release method provided in an embodiment of the present application, include:
- release the radio bearers associated with the MBS session When the release conditions are met, release the radio bearers associated with the MBS session; release the SDAP entity; where the release conditions include one or more of the following: the MBS session ends; the first message is received, where the first message carries the message to be released The radio bearer identity.
- the processor 151 may also implement the technical solution of the release method provided by any embodiment of the present application.
- the hardware structure and function of the device please refer to the content explanation of this embodiment.
- the embodiment of the present application also provides a storage medium containing computer-executable instructions, when the computer-executable instructions are executed by a computer processor, are used to execute a bearer configuration method, the method being applied to a first communication node, including :
- Radio bearer includes a point-to-point PTP bearer and/or a point-to-multipoint PTM bearer.
- An embodiment of the present application provides a storage medium containing computer-executable instructions.
- the computer-executable instructions are not limited to the above-mentioned wireless bearer configuration method operations, and can also execute the wireless bearer configuration method provided in any embodiment of the present application. Related operations in.
- the embodiment of the present application also provides a storage medium containing computer-executable instructions, the computer-executable instructions are used to execute a context message management method when executed by a computer processor, and the method is applied to a second communication node, include:
- the context request message includes a context establishment request message and a context change request message; the radio bearer of the MBS session is managed based on the context request message.
- An embodiment of the present application provides a storage medium containing computer-executable instructions.
- the computer-executable instructions are not limited to the operation of the context message management method described above, and can also execute the context message management method provided by any embodiment of the present application. Related operations in.
- An embodiment of the present application also provides a storage medium containing computer-executable instructions, which are used to perform a release method when the computer-executable instructions are executed by a computer processor, including:
- release the radio bearer associated with the MBS session When the release conditions are met, release the radio bearer associated with the MBS session; release the SDAP entity; where the release conditions include one or more of the following: the MBS session ends; the first message is received, where the first message carries the message to be released The radio bearer identity.
- An embodiment of the present application provides a storage medium containing computer-executable instructions.
- the computer-executable instructions are not limited to the release method operations described above, and can also perform related operations in the release method provided in any embodiment of the present application. .
- this application can be implemented by software and necessary general-purpose hardware, or can be implemented by hardware.
- the technical solution of this application can essentially be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access Memory (Random Access Memory, RAM), flash memory (FLASH), hard disk or optical disk, etc., including multiple instructions to make a computer device (may be a personal computer, server, or network device, etc.) The method described.
- the term user terminal encompasses any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicular mobile stations.
- the various embodiments of the present application can be implemented in hardware or dedicated circuits, software, logic or any combination thereof.
- some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, although the present application is not limited thereto.
- Computer program instructions can be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or written in any combination of one or more programming languages Source code or object code.
- ISA Instruction Set Architecture
- the block diagram of any logic flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions.
- the computer program can be stored on the memory.
- the memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as but not limited to read only memory (ROM), random access memory (RAM), optical storage devices and systems (digital multi-function optical discs) (Digital Video Disc, DVD) or Compact Disk (CD)), etc.
- Computer-readable media may include non-transitory storage media.
- the data processor can be any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (Digital Signal Processing, DSP), application specific integrated circuits (ASICs) ), programmable logic devices (Field-Programmable Gate Array, FPGA), and processors based on multi-core processor architecture.
- DSP Digital Signal Processing
- ASICs application specific integrated circuits
- FPGA Field-Programmable Gate Array
- FPGA Field-Programmable Gate Array
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (31)
- 一种承载配置方法,应用于第一通信节点,包括:接收第一信息;基于所述第一信息配置多播广播业务MBS的无线承载;其中,所述无线承载包括点对点PTP承载和点对多点PTM承载中的至少之一。
- 根据权利要求1所述的方法,其中,所述第一信息包含PTP承载配置信息;所述基于所述第一信息配置MBS的无线承载,包括:基于所述PTP承载配置信息配置所述PTP承载,所述PTP承载配置信息包括如下信息中的至少之一:PTP无线承载标识,服务数据适配协议SDAP配置信息,分组数据聚汇协议PDCP配置信息,无线链路控制RLC承载配置信息。
- 根据权利要求1所述的方法,其中,所述第一信息包含第二信息;所述基于所述第一信息配置MBS的无线承载,包括:基于所述第二信息配置所述PTM承载,所述第二信息包括如下至少之一:正在进行的MBS标识信息列表,MBS标识信息,每个MBS标识信息对应的调度信息,用于MBS的无线网络临时标识,多播业务信道的调度信息,配置多播业务信道所需的物理层参数,第二承载配置;所述第二承载配置包含如下至少之一:PTM无线承载标识,逻辑信道标识,SDAP配置信息,PDCP配置信息,RLC承载配置信息。
- 根据权利要求3所述的方法,其中,配置所述PTM承载所需的PTM承载配置信息包括如下至少之一:第一承载配置,所述第二承载配置;其中,所述第一承载配置采用默认配置,所述第一承载配置包括如下至少之一:PTM无线承载标识,逻辑信道标识,SDAP配置信息,PDCP配置信息,RLC承载配置信息。
- 根据权利要求2-4中任一项所述的方法,其中,所述SDAP配置信息包括如下至少之一:所述无线承载是否为默认无线承载的指示,所述无线承载上的下行数据是否有SDAP头的指示,所述无线承载的上行数据是否有SDAP头的指示,MBS标识信息,需要添加的映射到所述无线承载的MBS会话内的上行服务质量QoS流列表,需要释放的已映射到所述无线承载的MBS会话内的QoS流列表。
- 根据权利要求5中所述的方法,其中,所述MBS标识信息包括如下至少之一:MBS会话标识,MBS的临时移动组标识TMGI,MBS标识,指示MBS会话的协议数据单元PDU会话标识。
- 根据权利要求5所述的方法,其中,在PTP承载配置信息中携带所述SDAP配置信息的情况下,进行如下操作中的至少之一:建立第一SDAP实体;基于携带的所述SDAP配置信息配置所述第一SDAP实体;建立所述第一SDAP实体与所述PTP无线承载标识所对应的无线承载的关联;其中,所述第一SDAP实体用于所述MBS标识信息内QoS流与PTP无线承载的映射。
- 根据权利要求4所述方法,其中,在所述PTM承载配置信息中包含所述SDAP配置信息的情况下,进行如下操作中的至少之一:建立第二SDAP实体;基于所述第一承载配置和所述第二承载配置中的至少之一中的SDAP配置信息对所述第二SDAP实体进行配置;建立所述第二SDAP实体与所述PTM无线承载标识所对应的无线承载的关联;其中,所述第二SDAP实体用于所述MBS标识信息内QoS流与PTM无线承载的映射。
- 根据权利要求2或4所述的方法,其中,在所述PTP承载配置信息或所述PTM承载配置信息中包含所述SDAP配置信息的情况下,进行如下操作中的至少之一:建立第三SDAP实体;基于所述SDAP配置信息对所述第三SDAP实体进行配置;建立所述第三SDAP实体与所述PTP无线承载标识或所述PTM无线承载标识所对应的无线承载的关联;其中,所述第三SDAP实体用于所述MBS标识信息内QoS流与PTP无线承载或PTM无线承载的映射。
- 根据权利要求2-4中任一项所述的方法,其中,所述PDCP配置信息包 括如下至少之一:指示是否使用加密算法,丢弃PDCP数据包的计时,PDCP实体在重建的情况下是否继续或重置健壮性报头压缩ROHC协议,头压缩配置,所述无线承载是否配置完整性保护,头压缩上下文标识CID参数的最大值,上行数据传输中PDCP实体关联多于一个RLC实体,允许乱序,上行PDCP重复是否配置和激活,下行PDCP序号尺寸,上行PDCP序号尺寸,指示上行数据传输中关联多于一个RLC实体的情况下的主RLC实体所对应的小区组标识ID和逻辑信道标识,所述无线承载是否配置可以传输PDCP状态报告,重排序时间,上行数据使用分裂承载的数据量门限。
- 根据权利要求2-4中任一项所述的方法,其中,所述RLC承载配置信息包含如下至少之一:逻辑信道标识,RLC承载所服务的无线承载标识,RLC配置,逻辑信道配置,是否重建RLC标识,最大重传次数,poll字节数,pollPDU,序列号SN-Field长度,RLC确认模式AM下的计时器,重组计时器,状态报告计时器。
- 根据权利要求4所述的方法,其中,一个MBS标识信息的所有QoS流映射到一个PTM无线承载中,不同MBS标识信息对应的不同PTM无线承载使用同一个逻辑信道标识。
- 根据权利要求4所述的方法,其中,一个MBS标识信息的所有QoS流映射到至少一个PTM无线承载中,同一MBS标识信息的不同PTM无线承载使用不同逻辑信道标识。
- 根据权利要求4或12所述的方法,其中,针对每个MBS标识信息进行如下操作中的至少之一:基于第一承载配置和第二承载配置中的至少之一建立一个PDCP实体;基于第一承载配置和第二承载配置中的至少之一建立一个RLC实体;在介质访问控制MAC实体中配置一个对应所述无线承载的MBS逻辑信道;建立所述PDCP实体与所述MBS逻辑信道的关联;所述MBS逻辑信道使用默认逻辑信道标识。
- 根据权利要求4或13所述的方法,其中,针对每个PTM无线承载标识进行如下操作中的至少之一:建立一个PDCP实体;建立一个RLC实体;在MAC实体中配置一个对应所述PTM无线承载标识的MBS逻辑信道;建立所述PDCP实体与所述MBS逻辑信道的关联。
- 一种上下文消息管理方法,应用于第二通信节点,包括:发送第一通信节点的上下文申请消息;其中,所述上下文申请消息包括上下文建立申请消息或上下文更改申请消息;基于所述上下文申请消息对多播广播业务MBS的无线承载进行管理。
- 根据权利要求16所述的方法,其中,所述上下文申请消息包含以下信息中的至少之一:所需建立的用于MBS的无线承载信息列表,所需修改的用于MBS会话的无线承载信息列表;其中,每一项无线承载信息包括以下信息中的至少之一:MBS标识信息,无线承载标识、映射到无线承载的服务质量QoS流列表、QoS流标识、QoS流等级的QoS参数、QoS流映射指示参数。
- 根据权利要求17所述的方法,其中,所述MBS标识信息包括如下至少之一:MBS会话标识,MBS的临时移动组标识TMGI,MBS标识,指示MBS会话的协议数据单元PDU会话标识。
- 根据权利要求17所述的方法,其中,所述MBS标识信息与所述无线承载标识和所述映射到无线承载的QoS流列表中的至少之一关联。
- 根据权利要求17所述的方法,其中,所述MBS标识信息与所述QoS流标识相互关联。
- 根据权利要求17所述的方法,其中,所述QoS流等级的QoS参数包括:MBS会话标识信息,所述MBS会话标识信息用于指示QoS流所属的MBS会话。
- 一种释放方法,包括:在满足释放条件的情况下,释放多播广播业务MBS会话关联的无线承载;释放服务数据适配协议SDAP实体;其中,所述释放条件包括如下至少之一:MBS会话结束;接收到第一信息,其中,所述第一信息中携带待释放的无线承载标识。
- 根据权利要求22所述的方法,其中,所述释放MBS会话关联的无线承 载,包括:在所述MBS会话结束的情况下,释放与所述MBS会话关联的点对点PTP无线承载和点对多点PTM无线承载中的至少之一。
- 根据权利要求22所述的方法,其中,所述释放SDAP实体,包括:在所述MBS会话结束的情况下,释放与所述MBS会话关联的所有SDAP实体。
- 根据权利要求22所述的方法,其中,所述释放SDAP实体,包括:在上层指示释放针对一个MBS会话的PTM无线承载所关联的SDAP实体的情况下,释放所述MBS会话关联的所有SDAP实体。
- 根据权利要求22所述的方法,其中,所述释放SDAP实体,包括:在所述SDAP实体所关联的无线承载被释放的情况下,释放所述SDAP实体。
- 一种承载配置装置,配置于第一通信节点,包括:接收模块,被配置为接收第一信息;建立修改模块,被配置为基于所述第一信息配置多播广播业务MBS的无线承载;其中,所述无线承载包括点对点PTP承载和点对多点PTM承载中的至少之一。
- 一种上下文消息管理装置,配置于第二通信节点,包括:第一发送模块,被配置为发送第一通信节点的上下文申请消息;其中,所述上下文申请消息包括上下文建立申请消息和上下文更改申请消息;管理模块,被配置为基于所述上下文申请消息对多播广播业务MBS会话的无线承载进行管理。
- 一种释放装置,包括:第一释放模块,被配置为在满足释放条件的情况下,释放多播广播业务MBS会话关联的无线承载;第二释放模块,被配置为释放服务数据适配协议SDAP实体;其中,所述释放条件包括如下至少之一:MBS会话结束;接收到第一信息,其中,第一信息中携带待释放的无线承载标识。
- 一种设备,包括:至少一个处理器;存储器,被配置为存储至少一个程序;当所述至少一个程序被所述至少一个处理器执行,使得所述至少一个处理器实现如权利要求1-26中任一项所述的方法。
- 一种存储介质,存储有计算机程序,所述计算机程序被处理器执行时实现权利要求1-26中任一项所述的方法。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020227041348A KR102649878B1 (ko) | 2020-04-27 | 2021-03-04 | 베어러 구성 방법 및 장치, 컨텍스트 정보 관리 방법 및 장치, 해제 방법 및 장치, 설비 |
EP21797922.8A EP4145869A4 (en) | 2020-04-27 | 2021-03-04 | MEDIUM CONFIGURATION METHOD AND APPARATUS, CONTEXT INFORMATION MANAGEMENT METHOD AND APPARATUS, RELEASE METHOD AND APPARATUS, AND DEVICE |
US17/921,938 US20230180349A1 (en) | 2020-04-27 | 2021-03-04 | Bearer configuration method and apparatus, context information management method and apparatus, releasing method and apparatus, and device |
CA3186644A CA3186644A1 (en) | 2020-04-27 | 2021-03-04 | Bearer configuration method and apparatus, context information management method and apparatus, releasing method and apparatus, and device |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010345823.3 | 2020-04-27 | ||
CN202010345823.3A CN111901766A (zh) | 2020-04-27 | 2020-04-27 | 承载配置、上下文信息管理、释放方法、装置和设备 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021218375A1 true WO2021218375A1 (zh) | 2021-11-04 |
Family
ID=73206558
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2021/079117 WO2021218375A1 (zh) | 2020-04-27 | 2021-03-04 | 承载配置方法及装置、上下文信息管理方法及装置、释放方法及装置、设备 |
Country Status (6)
Country | Link |
---|---|
US (1) | US20230180349A1 (zh) |
EP (1) | EP4145869A4 (zh) |
KR (1) | KR102649878B1 (zh) |
CN (1) | CN111901766A (zh) |
CA (1) | CA3186644A1 (zh) |
WO (1) | WO2021218375A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2023069695A1 (en) * | 2021-10-21 | 2023-04-27 | Google Llc | Managing multicast radio resources in distributed base stations |
Families Citing this family (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110430599B (zh) * | 2018-09-28 | 2020-10-16 | 华为技术有限公司 | 数据传输的方法和装置 |
CN111901766A (zh) * | 2020-04-27 | 2020-11-06 | 中兴通讯股份有限公司 | 承载配置、上下文信息管理、释放方法、装置和设备 |
CN113630726B (zh) * | 2020-05-07 | 2022-07-29 | 大唐移动通信设备有限公司 | Mbms业务处理方法、基站、用户终端及存储介质 |
WO2022011515A1 (en) | 2020-07-13 | 2022-01-20 | Nec Corporation | Method, device and computer storage medium of communication |
WO2022099586A1 (en) * | 2020-11-13 | 2022-05-19 | Nec Corporation | Method, device and computer readable medium for communication |
CN114499771B (zh) * | 2020-11-13 | 2023-07-18 | 成都鼎桥通信技术有限公司 | Mbs的ack/nack信息的反馈与重传方法和装置 |
WO2022120546A1 (en) * | 2020-12-08 | 2022-06-16 | Zte Corporation | Multicast and broadcast service session reception mode switching in wireless communication networks |
WO2022135400A1 (en) * | 2020-12-21 | 2022-06-30 | FG Innovation Company Limited | Method and user equipment for handling reception of multicast-broadcast service |
WO2022141087A1 (zh) * | 2020-12-29 | 2022-07-07 | 捷开通讯(深圳)有限公司 | 一种广播多播业务的传输方法 |
WO2022141548A1 (zh) * | 2020-12-31 | 2022-07-07 | 华为技术有限公司 | 一种数据传输方法及装置 |
CN114727231B (zh) * | 2021-01-06 | 2023-04-07 | 大唐移动通信设备有限公司 | 一种广播多播服务会话的传输控制方法及装置 |
CN114765747B (zh) * | 2021-01-15 | 2023-04-18 | 维沃移动通信有限公司 | 逻辑信道配置方法、装置及设备 |
CN115038049B (zh) * | 2021-03-05 | 2024-01-23 | 维沃移动通信有限公司 | 多播业务的接收方法、配置方法、终端及网络侧设备 |
US20220312525A1 (en) * | 2021-03-25 | 2022-09-29 | FG Innovation Company Limited | Method of triggering packet data convergence protocol status report and related device |
CN116889081A (zh) * | 2021-04-01 | 2023-10-13 | Tcl通讯(宁波)有限公司 | 无线通信方法、用户设备和基站 |
WO2022236594A1 (en) * | 2021-05-10 | 2022-11-17 | Apple Inc. | Access control |
EP4167604A1 (en) * | 2021-10-14 | 2023-04-19 | MediaTek Singapore Pte. Ltd. | Methods and apparatus to set initial pdcp state variables for multicast |
WO2023130298A1 (en) * | 2022-01-06 | 2023-07-13 | Zte Corporation | Lossless handover of multicast broadcast services |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101155328A (zh) * | 2006-09-26 | 2008-04-02 | 华为技术有限公司 | 通信系统中删除/修改组播广播业务的方法 |
CN101166306A (zh) * | 2006-10-13 | 2008-04-23 | 华为技术有限公司 | 承载控制、承载删除及数据分发的方法、系统及网络节点 |
US20090219850A1 (en) * | 2006-09-19 | 2009-09-03 | Huawei Technologies Co., Ltd. | Method for terminal to join multicast broadcast service in wireless network and system using thereof |
CN102595328A (zh) * | 2011-01-14 | 2012-07-18 | 中兴通讯股份有限公司 | Mbms承载方式转化信息的配置发送方法及装置 |
US20170013433A1 (en) * | 2014-03-13 | 2017-01-12 | Lg Electronics Inc. | Method and apparatus for transmitting multimedia broadcast supplement for public warning system in wireless communication system |
CN108260162A (zh) * | 2018-01-29 | 2018-07-06 | 重庆邮电大学 | 一种5g系统的sdap层功能实现方法 |
CN111901766A (zh) * | 2020-04-27 | 2020-11-06 | 中兴通讯股份有限公司 | 承载配置、上下文信息管理、释放方法、装置和设备 |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20180050192A (ko) * | 2016-11-04 | 2018-05-14 | 삼성전자주식회사 | 차세대 이동 통신 시스템을 지원하기 위한 mac 서브 헤더의 구조와 이를 적용하는 방법 및 장치 |
CN110447146A (zh) * | 2016-12-21 | 2019-11-12 | 英特尔公司 | 无线通信技术、装置和方法 |
-
2020
- 2020-04-27 CN CN202010345823.3A patent/CN111901766A/zh active Pending
-
2021
- 2021-03-04 WO PCT/CN2021/079117 patent/WO2021218375A1/zh unknown
- 2021-03-04 KR KR1020227041348A patent/KR102649878B1/ko active IP Right Grant
- 2021-03-04 EP EP21797922.8A patent/EP4145869A4/en active Pending
- 2021-03-04 CA CA3186644A patent/CA3186644A1/en active Pending
- 2021-03-04 US US17/921,938 patent/US20230180349A1/en active Pending
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090219850A1 (en) * | 2006-09-19 | 2009-09-03 | Huawei Technologies Co., Ltd. | Method for terminal to join multicast broadcast service in wireless network and system using thereof |
CN101155328A (zh) * | 2006-09-26 | 2008-04-02 | 华为技术有限公司 | 通信系统中删除/修改组播广播业务的方法 |
CN101166306A (zh) * | 2006-10-13 | 2008-04-23 | 华为技术有限公司 | 承载控制、承载删除及数据分发的方法、系统及网络节点 |
CN102595328A (zh) * | 2011-01-14 | 2012-07-18 | 中兴通讯股份有限公司 | Mbms承载方式转化信息的配置发送方法及装置 |
US20170013433A1 (en) * | 2014-03-13 | 2017-01-12 | Lg Electronics Inc. | Method and apparatus for transmitting multimedia broadcast supplement for public warning system in wireless communication system |
CN108260162A (zh) * | 2018-01-29 | 2018-07-06 | 重庆邮电大学 | 一种5g系统的sdap层功能实现方法 |
CN111901766A (zh) * | 2020-04-27 | 2020-11-06 | 中兴通讯股份有限公司 | 承载配置、上下文信息管理、释放方法、装置和设备 |
Non-Patent Citations (1)
Title |
---|
See also references of EP4145869A4 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2023069695A1 (en) * | 2021-10-21 | 2023-04-27 | Google Llc | Managing multicast radio resources in distributed base stations |
Also Published As
Publication number | Publication date |
---|---|
KR102649878B1 (ko) | 2024-03-22 |
KR20230003065A (ko) | 2023-01-05 |
EP4145869A1 (en) | 2023-03-08 |
EP4145869A4 (en) | 2023-11-29 |
CA3186644A1 (en) | 2021-11-04 |
CN111901766A (zh) | 2020-11-06 |
US20230180349A1 (en) | 2023-06-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2021218375A1 (zh) | 承载配置方法及装置、上下文信息管理方法及装置、释放方法及装置、设备 | |
WO2021218897A1 (zh) | 模式配置方法、装置、设备和存储介质 | |
US11438941B2 (en) | Communication method and communications apparatus | |
US20200260233A1 (en) | Communications system, communication method, and apparatus thereof | |
EP3965440A1 (en) | Sidelink communication method and apparatus, and storage medium | |
US10397012B2 (en) | Evolved multimedia broadcast/multicast service (EMBMS) system and EMBMS system management method | |
WO2020020209A1 (zh) | 一种通信方法及装置 | |
US20230179958A1 (en) | Multicast/broadcast information transmission method and device, storage medium, and electronic device | |
WO2021004182A1 (zh) | 数据传输方法、装置、第一通信节点及第二通信节点 | |
WO2021213491A1 (zh) | 广播/组播业务的管理方法、装置、电子设备和存储介质 | |
US20230018974A1 (en) | Multicast communication method and communication apparatus | |
WO2022052851A1 (zh) | 一种服务质量QoS的监测方法 | |
WO2016095175A1 (zh) | 网络设备、用户设备和接入网络的方法 | |
US20230224679A1 (en) | Handover schemes in multicast broadcast services | |
WO2021190233A1 (zh) | 数据传输方法及装置 | |
US20190208383A1 (en) | V2x message transmission method and related network element | |
WO2023169451A1 (zh) | 一种通信方法、装置以及存储介质 | |
WO2022227071A1 (zh) | 一种承载配置方法及装置、终端设备、网络设备 | |
WO2022067795A1 (zh) | 一种通信方法及装置 | |
EP4369745A1 (en) | Communication method and apparatus | |
WO2023207555A1 (zh) | 一种通信方法及装置 | |
WO2023185956A1 (zh) | 基于侧行链路的通信方法、装置、存储介质和芯片系统 | |
WO2022222736A1 (zh) | 业务处理方法、装置、系统、可读取存储介质和电子设备 | |
US20240188104A1 (en) | Communication method and apparatus | |
WO2023066188A1 (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: 21797922 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 20227041348 Country of ref document: KR Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2021797922 Country of ref document: EP Effective date: 20221128 |
|
ENP | Entry into the national phase |
Ref document number: 3186644 Country of ref document: CA |