Bearer configuration, context information management, release method, apparatus and device

Abstract

The application provides a bearer configuration, context information management, release method, device, equipment and storage medium, including: receiving first information; configuring a wireless bearer of a multicast broadcast (MBS) based on the first information; wherein the wireless bearer includes a point-to-point (PTP) bearer and / or a point-to-multipoint (PTM) bearer.

Description

TECHNICAL FIELD

[0001] The present application relates to a wireless communication network, in particular to a bearer configuration, context information management, release method, device, equipment and storage medium. BACKGROUND

[0002] 5G related technologies are mainly about unicast service scenarios, i.e. point-to-point (PTP) service mode. The scheme of point-to-multipoint (PTM) service mode has not yet appeared. In addition, with the rapid growth of user quantity and the multi-dimension of application scenarios, the point-to-multipoint service mode will inevitably become one of the indispensable service modes. How to reasonably and effectively realize the multicast service under the technical framework of 5G-NR is a problem to be solved at present. SUMMARY

[0003] The present application provides a bearer configuration, context information management, release method, device, equipment and storage medium.

[0004] In a first aspect, an embodiment of the present application provides a bearer configuration method, which is applied to a first communication node and includes the following steps:

[0005] receiving first information;

[0006] configuring a wireless bearer of multicast broadcast (MBS) based on the first information; wherein the wireless bearer includes a point-to-point (PTP) bearer and / or a point-to-multipoint (PTM) bearer.

[0007] In a second aspect, an embodiment of the present application provides a context message management method, which is applied to a second communication node and includes the following steps:

[0008] sending a context application message of the first communication node; wherein the context application message includes a context establishment application message and a context change application message;

[0009] managing a wireless bearer of an MBS session based on the context application message.

[0010] In a third aspect, an embodiment of the present application provides a release method, which includes the following steps:

[0011] releasing a wireless bearer associated with an MBS session when a release condition is met;

[0012] releasing an SDAP entity;

[0013] The release condition includes one or more of the following:

[0014] the MBS session ends;

[0015] receive first information, wherein the first information carries a radio bearer identifier to be released.

[0016] In a fourth aspect, an embodiment of the present application provides a bearer configuration apparatus, configured in a first communication node, comprising:

[0017] a receiving module, configured to receive first information;

[0018] a configuration module, configured to configure a radio bearer of a multicast broadcast (MBS) based on the first information; wherein the radio bearer comprises a point-to-point (PTP) bearer and / or a point-to-multipoint (PTM) bearer; and the configuration comprises one or more of the following: establishment, modification, and release.

[0019] In a fifth aspect, an embodiment of the present application provides a context message management apparatus, configured in a second communication node, comprising:

[0020] a first sending module, configured to send a context application message of the first communication node; wherein the context application message comprises a context establishment application message and a context change application message;

[0021] a management module, configured to manage a radio bearer of an MBS session based on the context application message.

[0022] In a sixth aspect, an embodiment of the present application provides a radio bearer release apparatus, comprising:

[0023] a first release module, configured to release a radio bearer associated with an MBS session when a release condition is met;

[0024] a second release module, configured to release an SDAP entity;

[0025] wherein the release condition comprises one or more of the following:

[0026] an end of the MBS session;

[0027] receiving first information, wherein the first information carries a radio bearer identifier to be released.

[0028] In a seventh aspect, an embodiment of the present application provides an apparatus, comprising:

[0029] one or more processors;

[0030] a memory, configured to store one or more programs;

[0031] In an eighth aspect, when the one or more programs are executed by the one or more processors, the one or more processors implement any one of the methods in embodiments of the present application.

[0032] The embodiment of the present application provides a storage medium, the storage medium stores a computer program, and the computer program is executed by a processor to realize any one of the methods in the embodiment of the present application.

[0033] More details about the above embodiments and other aspects of the present application and implementation manners thereof are provided in the description of drawings, specific embodiments and claims. BRIEF DESCRIPTION OF DRAWINGS

[0034] Figure 1 A structure schematic diagram of a wireless network system is provided for the embodiment of the present application.

[0035] Figure 2 A flowchart of a bearer configuration method is provided for the embodiment of the present application.

[0036] Figure 3 A flowchart of a context message management method is provided for the embodiment of the present application.

[0037] Figure 4 A flowchart of a release method is provided for the embodiment of the present application.

[0038] Figure 5 It is a control plane flowchart in which a base station configures a radio bearer for an MBS service for a UE.

[0039] Figure 6 It is a user plane flowchart in which a base station configures a radio bearer for an MBS service for a UE.

[0040] Figure 7 It is a flowchart of radio bearer establishment.

[0041] Figure 8 It is a flowchart of broadcast message acquisition.

[0042] Figure 9 It is a flowchart of interaction between a base station and a terminal.

[0043] Figure 10 It is a flowchart in which a gNB-CU sends a UE context establishment application message to a gNB-DU.

[0044] Figure 11 It is a flowchart in which a gNB-CU sends a UE context change application message to a gNB-DU.

[0045] Figure 12 A structure schematic diagram of a bearer configuration information device is provided for the embodiment of the present application.

[0046] Figure 13 A structure schematic diagram of a context message management device is provided for the embodiment of the present application.

[0047] Figure 14 A structural schematic diagram of a release device provided by an embodiment of the present application is shown in FIG. 1.

[0048] Figure 15 A structural schematic diagram of a device provided by an embodiment of the present application is shown in FIG. 2. DETAILED DESCRIPTION

[0049] To make the objectives, technical solutions and advantages of the present application clearer, the embodiments of the present application will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments can be combined with each other as long as there is no conflict.

[0050] The steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Moreover, although the logical order is shown in the flowchart, in some cases, the steps shown or described herein can be executed in an order different from that shown.

[0051] The technical solutions of the present application can be applied to various communication systems, such as Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced long term evolution (LTE-A) system, Universal Mobile Telecommunication System (UMTS), and 5th generation wireless systems (5G) system, etc. The embodiments of the present application are not limited. In the present application, the 5G system is taken as an example for description.

[0052] The embodiments of the present application can be used in different types of wireless networks. The wireless access network can include different communication nodes in different systems. Figure 1 A structural schematic diagram of a wireless network system provided by an embodiment of the present application is shown in FIG. 3. As shown in FIG. 3, the wireless network system includes a core network and a radio access network. Figure 1As shown, 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.

[0053] First, it needs to be pointed out that in the embodiments of the present application, the base station can be a device capable of communicating with a user terminal. The base station can be any kind of device with wireless transceiver function. Including but not limited to: base station NodeB, evolved base station eNodeB, base station in 5G communication system, base station in future communication system, access node in WiFi system, wireless relay node, wireless backhaul node, etc. The base station can also be a wireless controller in the cloud radio access network (CRAN) scenario; the base station can also be a small station, a transmission node (TRP), etc. The embodiments of the present application do not limit.

[0054] In the embodiments of the present application, the user terminal is a kind of device with wireless transceiver function, which can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; It can also be deployed on the water surface (such as ships, etc.); It can also be deployed in the air (such as airplanes, balloons and satellites, etc.). The user terminal can be a mobile phone, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. The embodiments of the present application do not limit the application scenario. The user terminal can also be called terminal, access terminal, UE unit, UE station, mobile station, mobile station, remote station, remote terminal, mobile device, UE terminal, wireless communication device, UE agent or UE device, etc. The embodiments of the present application do not limit.

[0055] With the continuous development of 5G technology, the 5G solutions for various application scenarios are accelerating the completion. The groupcast service scenario exists to meet the needs of most users for the same service. At present, the 5G related technology is mainly about the unicast service scenario, that is, the point-to-point (PTP) service mode. The standardization discussion of the point-to-multipoint (PTM) service mode has not yet started. In addition, with the rapid growth of the number of users and the multi-dimensionality of application scenarios, the point-to-multipoint service mode will inevitably become one of the indispensable service modes. Therefore, how to reasonably and effectively realize the groupcast service under the technical framework of 5G-NR is a problem that needs to be discussed and solved at present.

[0056] A mobile network can be divided into a core network, a radio access network (base station), and a user equipment (UE). The bearer between the radio access network and the user equipment is called a radio bearer (RB). In the third and fourth generation mobile networks, the user equipment in a cell can receive groupcast services through a point-to-multipoint (PTM) mode radio bearer. If a specific user equipment wants to establish a point-to-point (PTP) mode radio bearer, the network needs to provide the user equipment with a point-to-point bearer between the core network element, the radio access network element, and the user equipment. The user equipment needs to establish a bearer of which mode needs to be determined by the core network.

[0057] In one embodiment, the present application provides a bearer configuration method, Figure 2 A flowchart of a bearer configuration method provided by an embodiment of the present application. The method can be applied to the establishment and modification of a radio bearer by a user. The method can be executed by a bearer configuration information device provided by the present application, which can be realized by software and / or hardware. The method is applied in a first communication node.

[0058] As Figure 2 shown, the bearer configuration method provided by the embodiment of the present application mainly includes steps S11 and S12.

[0059] S11, receiving first information;

[0060] S12, configuring a radio bearer of a groupcast 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: establishment, modification, and release.

[0061] In the present application, the point-to-point (PTP) bearer can refer to a unicast bearer, which can be understood as a bearer used when the base station sends data to a single first communication node (e.g., a UE). The point-to-multipoint (PTM) bearer can refer to a multicast or broadcast bearer, which can be understood as a bearer used when the base station sends data to a group of first communication nodes or all first communication nodes in a cell.

[0062] There are two modes of communication between the base station and the first communication node, one being a PTP mode and the other being a PTM mode. The PTP mode represents a point-to-point communication mode between the first communication node and the base station, and the bearer of the PTP mode can be a 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, and the bearer of the PTM mode can be a groupcast RB or a broadcast RB or a PTM radio bearer or a PTM bearer.

[0063] In the present embodiment, the first communication node can be any of the user equipment described in the above system, which is only described in the present embodiment and is not limited.

[0064] Further, the first information is sent by the base station to the user equipment. The base station can be any of the base stations described in the above system, which is only described in the present embodiment and is not limited.

[0065] In an exemplary embodiment, the first information includes PTP bearer configuration information, and the PTP bearer is configured based on the PTP bearer configuration information, and the PTP bearer configuration information includes one or more of the following information:

[0066] PTP radio bearer identification, service data adaptation protocol (SDAP) configuration information, packet data convergence protocol (PDCP) configuration information, RLC bearer configuration information.

[0067] In an exemplary embodiment, the first information includes second information, and the PTM bearer is configured based on the second information, and the second information includes one or more of the following:

[0068] a list of ongoing MBS identification information, MBS identification information, scheduling information corresponding to each MBS identification information, a radio network temporary identifier for a broadcast / multicast service, scheduling information of a multicast service channel, physical layer parameters required for configuring the multicast service channel, and second bearer configuration.

[0069] The second bearer configuration includes one or more of the following: PTM radio bearer identification, logical channel identification, SDAP configuration information, PDCP configuration information, and RLC bearer configuration information.

[0070] In the embodiment, the PTM bearer configuration information includes one or more of the following:

[0071] The first bearer configuration and the second bearer configuration, wherein the first bearer configuration adopts a default configuration, and the second bearer configuration is obtained from the received second information.

[0072] In an exemplary embodiment, the SDAP configuration information includes one or more of the following:

[0073] An indication of whether the radio bearer is a default radio bearer, an indication of whether downlink data on the radio bearer has an SDAP header, an indication of whether uplink data of the radio bearer has an SDAP header, MBS identification information, a list of uplink QoS flows in an MBS session that need to be added to the radio bearer, and a list of QoS flows in an MBS session that have been mapped to the radio bearer and need to be released.

[0074] In an exemplary embodiment, the MBS identification information includes one or more of the following:

[0075] An MBS session identifier, a temporary mobile group identifier TMGI of a multicast service, an identifier of a multicast service, and a PDU session identifier indicating an MBS session.

[0076] In an exemplary embodiment, when the SDAP configuration includes PDU session identification information, a PDU session is established and associated with an MBS session in the SDAP configuration.

[0077] In an exemplary embodiment, when the SDAP configuration information is carried in the PTP bearer configuration information, one or more of the following operations are performed:

[0078] A first SDAP entity is established;

[0079] The first SDAP entity is configured based on the carried SDAP configuration information;

[0080] The first SDAP entity is associated with a radio bearer corresponding to the PTP radio bearer identifier;

[0081] The first SDAP entity is used for mapping of QoS flows in the MBS identification information to a PTP radio bearer.

[0082] In an exemplary embodiment, the first bearer configuration includes one or more of the following information:

[0083] A PTM radio bearer identifier, a logical channel identifier, an SDAP configuration, a PDCP configuration, and an RLC configuration.

[0084] In an example implementation, in case the PTM bearer configuration information contains SDAP configuration information, one or more of the following operations are performed:

[0085] establishing a second SDAP entity;

[0086] configuring the second SDAP entity based on the SDAP configuration information in the first bearer configuration and / or the second bearer configuration;

[0087] establishing an association between the second SDAP entity and the radio bearer corresponding to the PTP radio bearer identifier or the PTM radio bearer identifier;

[0088] wherein the second SDAP entity is configured to map the QoS flow within the MBS identifier information to the PTP radio bearer.

[0089] In an example implementation, in case the PTP bearer configuration information or the PTM bearer configuration information contains SDAP configuration information, one or more of the following operations are performed:

[0090] establishing a third SDAP entity;

[0091] configuring the third SDAP entity based on the SDAP configuration information;

[0092] establishing an association between the third SDAP entity and the radio bearer corresponding to the PTP radio bearer identifier or the PTM radio bearer identifier;

[0093] wherein the third SDAP entity is configured to map the QoS flow within the MBS identifier information to the PTP radio bearer and the PTM radio bearer.

[0094] In an example implementation, the PDCP configuration information comprises one or more of the following:

[0095] an indication of whether to use encryption algorithm, a timer to discard PDCP packets, whether the PDCP entity continues or resets ROHC header compression protocol upon re-establishment, header compression configuration, whether the radio bearer is configured with integrity protection, a maximum value of header compression CID parameter, whether the PDCP entity is associated with more than one RLC entity in uplink data transmission, whether out-of-order is allowed, whether uplink PDCP duplication is configured and activated, downlink PDCP sequence number size, uplink PDCP sequence number size, an indication of a cell group ID and LCID of a primary RLC entity when the PDCP entity is associated with more than one RLC entity in uplink data transmission, whether the radio bearer is configured to transmit PDCP status report, reordering time, a data volume threshold for uplink data using split bearer.

[0096] In an exemplary embodiment, the RLC bearer configuration information comprises: LCID, radio bearer identity served by the RLC bearer, logical channel identity, radio bearer identity served by the RLC bearer, RLC configuration, logical channel configuration, whether to reestablish RLC identity, maximum retransmission number, poll byte number, poll PDU, sn-Field length, timer under RLC AM, reassembly timer, status reporting timer.

[0097] In an exemplary embodiment, the first information is a radio resource control (RRC) message; or, the first information is a broadcast message.

[0098] All QoS flows of one MBS identity information are mapped into one PTM radio bearer, and different PTM radio bearers corresponding to different MBS identity information use the same logical channel identity.

[0099] In an exemplary embodiment, all QoS flows of one MBS identity information are mapped into one or more PTM radio bearers, and different PTM radio bearers of the same MBS identity information use different logical channel identities.

[0100] In an exemplary embodiment, one or more of the following operations are performed for each MBS identity information:

[0101] establishing a PDCP entity based on the first bearer configuration and / or the second bearer configuration;

[0102] establishing an RLC entity based on the first bearer configuration and / or the second bearer configuration;

[0103] configuring a broadcast / multicast service logical channel corresponding to the radio bearer in the MAC entity;

[0104] establishing an association between the PDCP entity and the broadcast / multicast service logical channel;

[0105] the broadcast / multicast service logical channel uses a default logical channel identity;

[0106] establishing an association between the PDCP entity and the broadcast / multicast service logical channel.

[0107] In an exemplary embodiment, one or more of the following operations are performed for each PTM radio bearer identity:

[0108] establishing a PDCP entity;

[0109] establishing a PDCP entity;

[0110] establishing an RLC entity;

[0111] a corresponding broadcast / multicast service logical channel is configured in the MAC entity corresponding to the PTM radio bearer identifier;

[0112] an association between the PDCP entity and the broadcast / multicast service logical channel is established.

[0113] In an exemplary embodiment, all QoS flows of one MBS session are mapped into one PTM radio bearer, and different PTM radio bearers corresponding to different MBS sessions use a default logical channel identifier.

[0114] In an exemplary embodiment, all QoS flows of one MBS session are mapped into one or more PTM radio bearers, and different PTM radio bearers corresponding to the same MBS session use different logical channel identifiers; for each PTM radio bearer, the second bearer configuration contains a PTM radio bearer identifier and / or a logical channel identifier.

[0115] In an exemplary embodiment, 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.

[0116] In an exemplary embodiment, in the case where the first bearer configuration and the second bearer configuration overlap, the SDAP entity, the PDCP entity, and the RLC entity are configured using the information contained in the second bearer configuration, respectively.

[0117] In this embodiment, the content in the SDAP configuration information can be partially or entirely in the first bearer configuration (default configuration), or partially or entirely in the second bearer configuration (obtained through the first information). When the parameters overlap, the relevant parameters are configured using the second bearer configuration.

[0118] In an embodiment, the present application provides a context message management method, Figure 3 A flowchart of a context message management method provided by an embodiment of the present application is shown. The method can be applied to the case of bearer configuration information within a base station. The method can be executed by a context message management device provided by the present application, which can be implemented by software and / or hardware, and the method is applied in a second communication node.

[0119] As shown in Figure 3 The context message management method provided by an embodiment of the present application mainly includes steps S21 and S22.

[0120] S21, a context application message of a first communication node is sent; wherein the context application message includes a context establishment application message and a context change application message;

[0121] S22, managing radio bearers of the MBS session based on the context application message.

[0122] In the embodiment, the second communication node can be understood as a centralized unit (gNB-CU) in a base station, and the context application message is sent by a separated unit (gNB-DU) in the base station to the gNB-CU. That is, the context message management method provided by the application is executed by the centralized unit (gNB-CU) in the base station.

[0123] In an exemplary embodiment, the list of radio bearers required to be modified includes radio bearer information required to be established for the MBS session, wherein the list of radio bearers required to be modified is carried by the context establishment application message or by the context change application message.

[0124] In an exemplary embodiment, the radio bearer information includes MBS session identification information, wherein the MBS session identification information is associated with a radio bearer identification and a list of QoS flows mapped to the radio bearer.

[0125] In an exemplary embodiment, the MBS session identification is associated with a radio bearer identification and a list of QoS flows mapped to the radio bearer.

[0126] In an exemplary embodiment, for each QoS flow in the list of QoS flows mapped to the radio bearer, one or more of the following are included:

[0127] QoS flow identification, QoS flow level QoS parameter, QoS flow mapping indication parameter, MBS session identification information.

[0128] The MBS session identification information is associated with the QoS flow identification.

[0129] In an exemplary embodiment, the QoS flow level QoS parameter includes MBS session identification information, used to indicate the MBS session to which the QoS flow belongs.

[0130] In an embodiment, the application provides a release method, Figure 4 A flowchart of a release method provided by the embodiment of the application. The method can be applied to the case where the user equipment releases the radio bearer and the SDAP. The method can be executed by the release device provided by the application, which can be realized by software and / or hardware, and the method is applied in the first communication node.

[0131] As Figure 4 shown, the release method provided by the embodiment of the application mainly includes steps S31 and S32.

[0132] S31, release the radio bearers associated with the MBS session in a case that a release condition is met;

[0133] S32, release the SDAP entity;

[0134] The release condition comprises one or more of the following:

[0135] The MBS session ends;

[0136] The first information is received, and the first information carries a radio bearer identifier to be released.

[0137] In the embodiment, the first communication node can be any of the user equipment in the system, and the embodiment is only illustrative but not limited.

[0138] Further, the first information is sent by a base station to the user equipment. The base station can be any of the base stations in the system, and the embodiment is only illustrative but not limited.

[0139] In an exemplary embodiment, the release of the radio bearers associated with the MBS session comprises:

[0140] When the MBS session ends, all PTP radio bearers and PTM radio bearers associated with the MBS session are released.

[0141] In an exemplary embodiment, the release of the SDAP entity comprises:

[0142] When the MBS session ends, all SDAP entities associated with the MBS session are released.

[0143] In an exemplary embodiment, the release of the SDAP entity comprises:

[0144] When the upper layer indicates to release the SDAP entity associated with the PTM radio bearer for one MBS session, all SDAP entities associated with the MBS session are released.

[0145] In an exemplary embodiment, the release of the SDAP entity comprises:

[0146] In a case that the radio bearer associated with the SDAP entity is released, the SDAP entity is released.

[0147] Firstly, it should be noted that one MBS session has at least one QoS flow. The MBS session identification information is used to uniquely distinguish one MBS session, and the QoS flow identification is used to uniquely distinguish one QoS flow within 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 service, MBS service identification information, PDU session identification. All QoS flows within one MBS session can come from one MBS service or multiple MBS services, and one MBS service identification information is used to uniquely distinguish one MBS service. One MBS service identification information contains one or more of the following information: one MBS session identification, a list of at least one QoS flow identification within one MBS session, one MBS service identification, one IP multicast address, one IP source address, and one TMGI.

[0148] It should be noted that the MBS session identification information and the MBS identification information in the present application refer to the same information, only different in expression.

[0149] The communication between the base station and the UE has two modes, one is PTP mode and the other is PTM mode. The PTP mode represents the point-to-point communication mode between the UE and the base station, and the PTP mode bearer can be DRB or unicast RB or PTP radio bearer or PTP bearer. The PTM mode represents the point-to-multipoint communication mode between the UE and the base station, and the PTM mode bearer can be groupcast RB or broadcast RB or PTM radio bearer or PTM bearer. The base station can send the PTP mode and / or PTM mode bearer configuration information to the UE, and then transmit the MBS service data to the UE through the PTP or PTM mode. The UE can correspondingly configure the PTP mode bearer or the PTM mode bearer to receive the MBS service 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.

[0150] In one embodiment, the present application provides a bearer configuration method, Figure 5 A control plane flow diagram of a bearer configuration method provided by an embodiment of the present application is shown in FIG. 5. As shown in FIG. 5, the embodiment of the present application includes the following steps or all of the steps: step 510, step 511, step 520 and step 530. Figure 5

[0151] The trigger condition for the base station to configure (such as establish, modify or release) the bearer for the MBS service can be any one of the following steps 510 and 511:

[0152] ​In step 510, the base station receives a MBS session management message from the core network (e.g., AMF). The MBS session management message can be one of the following: a MBS session setup request message, a MBS session start message, a MBS session update message, a MBS session modification request message, a MBS session end message, and a MBS session release message.

[0153] The MBS session setup request message or the MBS session start message carries any combination of the following information: a MBS session identity, one MBS service identity or a list of MBS service identities, a list of QoS flow identities that need to be established in the MBS session, QoS parameters corresponding to the QoS flow level of each QoS flow identity, and a list of UE identities that join the MBS session. For each UE that joins the MBS session, the message can further include the following information: a cell identity to which the UE belongs, and / or an indication of whether to use PTP or PTM to receive MBS data.

[0154] The MBS session modification request message or the MBS session update message carries any combination of the following information: a MBS session identity, one MBS service identity or a list of MBS service identities, a list of QoS flow identities that need to be added or modified in the MBS session, QoS parameters corresponding to the QoS flow level of each QoS flow identity, and a list of UEs that join the MBS session. For each UE that joins the MBS session, the message can further include the following information: a cell identity to which each UE belongs, and / or an indication of whether to use PTP or PTM to receive MBS data.

[0155] The MBS session release message or the MBS session end message carries a MBS session identity. The base station decides to release all bearers in the MBS session.

[0156] In step 511, the base station sends an MBS session management response message to the core network after receiving the MBS session management message. 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. 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. 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. After the base station receives the MBS session start message from the core network, the base station sends an MBS session start response message to the core network as a reply. 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.

[0157] In step 520, 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. When the base station configures a radio bearer for MBS service for the UE, it needs to configure the mapping relationship of the QoS flow in the MBS session to the radio bearer. The bearer can be a radio bearer in PTP mode or a radio bearer in PTM mode.

[0158] In step 530, in one embodiment, the base station can send PTP bearer configuration information for receiving MBS data to the UE, which can be used to instruct the UE to establish, modify, or release the PTP bearer. The UE configures the PTP radio bearer for MBS service according to the received PTP bearer configuration information and sends an RRC complete message to the base station. In another embodiment, in step 530, the base station can also send PTM bearer configuration information corresponding to the MBS session to the UE, which can be sent to the UE through broadcasting or unicast.

[0159] Figure 6 is a user plane flow chart for the base station to configure a radio bearer for MBS service for the UE, as shown in Figure 6 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, and the UE receives MBS service data in the corresponding radio bearer from the base station.

[0160] In one application embodiment, a method is provided for how the base station internally maps the QoS flow of one MBS session to the PTM bearer and the PTP radio bearer of different UEs.

[0161] The procedure on the control plane of the base station side includes: for one MBS session, the base station establishes the corresponding SDAP entity in the following one or more ways.

[0162] Way 1: For one MBS session, the base station establishes one SDAP entity for each UE using 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.

[0163] Way 2: For one MBS session, the base station establishes one SDAP entity for all UEs using 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.

[0164] Way 3: For one MBS session, the base station establishes one 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 mapping of the QoS flow of the MBS session to the PTM radio bearer.

[0165] The procedure on the user plane of the base station side includes:

[0166] 1) 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.

[0167] 2) 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.

[0168] In one embodiment, a method for UE to establish an SDAP entity associated with one MBS session is provided. For one MBS session, the UE establishes the SDAP entity associated with the MBS session in the following one or more ways.

[0169] Way 1: For one MBS session, the UE establishes a first SDAP entity, which is responsible for the mapping of the QoS flow of the MBS session to the PTP radio bearer.

[0170] Way 2: For one MBS session, the UE establishes a second SDAP entity, which is responsible for the mapping of the QoS flow of the MBS session to the PTM radio bearer.

[0171] Option 3: For one MBS session, the UE establishes one third SDAP entity, which is responsible for the mapping of QoS flows of this MBS session to radio bearers, including the mapping of QoS flows of this MBS session to PTP radio bearers and the mapping of QoS flows of this MBS session to PTM radio bearers.

[0172] In the following embodiments, methods are provided for how the UE configures PTP radio bearers for receiving MBS traffic.

[0173] In one application embodiment, the UE receives radio bearer configuration information for receiving MBS traffic from the base station, which carries any combination of the following information: radio bearer identity (such as RB ID), cast mode indication, SDAP configuration, PDCP configuration, RLC bearer configuration. The cast mode indication includes at least one of the following: unicast, groupcast, broadcast.

[0174] In another application embodiment, the UE receives radio bearer configuration information from the base station, which contains a list of PTP radio bearers to be established and modified, including radio bearer (i.e. DRB) information for PTP mode for MBS traffic data transmission. For each DRB for MBS traffic data, the radio bearer configuration information further contains one or more of the following information: radio bearer identity (such as DRB ID), SDAP configuration, PDCP configuration, RLC bearer configuration.

[0175] The SDAP configuration is associated with one radio bearer identity. The SDAP configuration contains any combination of the following information: an indication of whether this radio bearer is the default radio bearer, an indication of whether downlink data on this radio bearer has an SDAP header, an indication of whether uplink data on this radio bearer has an SDAP header, session identification information, a list of uplink QoS flows within the MBS session that need to be added to this radio bearer, a list of QoS flows within the MBS session that have been mapped to this radio bearer and need to be released.

[0176] The session identification information in the SDAP configuration is used to identify the MBS session associated with this SDAP configuration, which has the following three options.

[0177] Manner 1: The session identification information is PDU session identification. Both PDU session for unicast service and MBS session for MBS service are uniquely distinguished by PDU session identification. The value space of the PDU session identification can be divided into two subspaces, the session identification for unicast service takes value in one subspace, the session identification for MBS service takes value in another subspace. For example, PDU session identification takes value 0~X to represent unicast service, takes value X+1~Y to identify multicast service, Y=255, X is any value in 0~254. The PDU session identification is used to identify which PDU session's QoS flow is mapped to the radio bearer associated with this SDAP configuration.

[0178] Manner 2: The session identification information is MBS session identification information. The session for MBS service is distinguished by the MBS session identification information, the session for unicast service is distinguished by PDU session identification. The MBS session identification information indicates which MBS session's QoS flow is mapped to the radio bearer associated with this SDAP configuration.

[0179] Manner 3: The session identification information contains PDU session identification and MBS session identification information. The MBS session identification information indicates which MBS session's QoS flow is mapped to the radio bearer associated with this SDAP configuration. The PDU session identification indicates which PDU session is associated with the MBS session.

[0180] The PDCP configuration is associated with a radio bearer identity, and the PDCP configuration contains any combination of the following information: cipheringDisabledkey (indicating whether to use ciphering algorithm), discardTimer (timer for discarding PDCP data packets), drb-ContinueROHC (whether the PDCP entity continues or resets the ROHC header compression protocol upon reestablishment), headerCompression (header compression configuration), integrityProtection (whether the radio bearer is configured for integrity protection), maxCID (maximum value of header compression CID parameter), moreThanOneRLC (PDCP entity is associated with more than one RLC entity in uplink data transmission), outOfOrderDelivery (allowing out-of-order delivery), pdcp-Duplication (whether uplink PDCP duplication 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 of the primary RLC entity when the PDCP entity is associated with more than one RLC entity in uplink data transmission), statusReportRequired (whether the radio bearer is configured for transmitting PDCP status report), t-Reordering (reordering time), ul-DataSplitThreshold (data volume threshold for using split bearer in uplink data transmission).

[0181] The RLC bearer configuration contains: LCID, radio bearer identity served by the RLC bearer, RLC configuration, logical channel configuration, and whether to reestablish the RLC identity. The RLC configuration indicates the RLC mode (UM, AM) used by the radio bearer and provides parameters for the corresponding RLC mode. The RLC configuration contains any combination of the following information: maxRetxThreshold (maximum number of retransmissions), pollByte (indicating how many bytes of the AM RLC entity transmitter to trigger a poll), pollPDU (indicating how many poll PDUs of the AM RLC entity transmitter to trigger a poll), sn-FieldLength (indicating the RLC SN size), t-PollRetransmit (timer in RLC AM), t-Reassembly (reassembly timer), t-StatusProhibit (status report timer).

[0182] In one application embodiment, a method for UE to establish or modify radio bearers is provided. The radio bearer configuration information received by the UE contains a list of PTP radio bearer identities to be established or modified, and the UE performs the following bearer establishment or bearer modification operations.

[0183] For each radio bearer identity to be established or modified included in the radio bearer configuration information, if this radio bearer is not part of the UE's existing configuration, the UE shall perform one or more of the following steps:

[0184] 1> establish a PDCP entity and configure it according to the received PDCP configuration;

[0185] 2> if the bearer configuration information carries SDAP configuration, the UE's operation has the following options.

[0186] Option 1: if the first SDAP entity corresponding to the received session identity information does not exist, establish a first SDAP entity.

[0187] Option 2: if the third SDAP entity corresponding to the received session identity information does not exist, establish a third SDAP entity.

[0188] 3> if the SDAP entity corresponding to the session identity information did not exist before the reception of this configuration information: inform upper layers of the establishment of user plane resources for this MBS session; optionally, if the MBS session identity information contains both MBS session identity and PDU session identity, associate this PDU session with this MBS session.

[0189] 4> configure the SDAP entity according to the received SDAP configuration, and associate this radio bearer with this SDAP entity;

[0190] For each radio bearer identity to be established or modified included in the radio bearer configuration information, if this radio bearer is part of the UE's existing configuration, the UE shall perform one or more of the following steps:

[0191] 1> if the bearer configuration carries PDCP re-establishment indication: re-establish the PDCP entity according to the PDCP configuration;

[0192] 2> if the bearer configuration carries PDCP resume indication: trigger the PDCP entity of this radio bearer to perform PDCP data resume procedure;

[0193] 3> if the bearer configuration carries PDCP configuration: reconfigure the PDCP entity of this radio bearer according to the PDCP configuration;

[0194] 4> if the bearer configuration carries SDAP configuration: reconfigure the SDAP entity according to the received SDAP configuration;

[0195] 5> for the list of uplink QoS flows within the MBS session that need to be added to this radio bearer, if any of the QoS flows has been configured previously, the UE needs to release the QoS flow from the original radio bearer.

[0196] In one application embodiment, a method for UE to release radio bearers is provided.

[0197] In the radio bearer release procedure, the UE performs one or more of the following operations:

[0198] If the radio bearer configuration information received by the UE contains a list of PTP radio bearer identities to be released, the UE shall perform the following radio bearer release operations:

[0199] For each radio bearer identity to be released, the UE shall:

[0200] release the PDCP entity and this radio bearer identity;

[0201] If the SDAP entity associated with this radio bearer has been configured: inform the SDAP entity associated with this radio bearer of the release of this radio bearer;

[0202] When an MBS session ends, the UE shall release all radio bearers associated with this MBS session.

[0203] In one application embodiment, a method for SDAP entity to release is provided, the SDAP entity release related operations include one or more of the following steps:

[0204] When the RRC requests the SDAP entity to release, the UE shall release the SDAP entity;

[0205] When the RRC indicates that a radio bearer is released, the SDAP entity shall remove all QoS flows mapped to this released radio bearer.

[0206] The UE can be aware of the end time of an MBS session according to the context information of the MBS session, when the MBS session ends, the UE shall release the SDAP entity associated with this MBS session.

[0207] In the following embodiments, methods for the base station to inform the UE of the PTM bearer configuration information for receiving MBS services are provided.

[0208] Before the UE is configured with a PTM radio bearer for receiving MBS service data, the UE needs to acquire any combination of the following configuration information: MBS session identity information, radio network temporary identifier for groupcast / multicast service, scheduling information of multicast service channel, physical layer parameters required for configuring multicast service channel, PTM bearer configuration. Each of the PTM bearer configuration contains any combination of the following information: PTM radio bearer identity, SDAP configuration, PDCP configuration, RLC bearer configuration. The RLC bearer configuration contains any combination of the following information: RLC configuration, logical channel identity, logical channel configuration.

[0209] For the PTM bearer configuration, all of its information can be acquired in two ways: one way is to let the UE use a default configuration, which will be referred to as the first bearer configuration in this application; the other way is to let the base station send it to the UE, which will be referred to as the second bearer configuration in this application. The first bearer configuration contains part or none or all of the PTM bearer configuration. The second bearer configuration contains part or none or all of the PTM radio bearer information. In one embodiment, the second bearer configuration contains information different from the information contained in the PTM bearer configuration. In another embodiment, the second bearer configuration can also overlap with the information contained in the first bearer configuration, i.e., the second bearer configuration has the same parameters as the first bearer configuration.

[0210] In one embodiment, the base station sends first information indicating a list of ongoing MBS sessions / services in the cell and the scheduling information of the corresponding sessions / services. For each MBS session, the first information contains one or more of the following information: MBS session identity information, radio network temporary identifier for groupcast / multicast service, scheduling information of multicast service channel, physical layer parameters required for configuring multicast service channel.

[0211] In one application embodiment, 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 the same logical channel identity. In one embodiment, the first bearer configuration contains a default logical channel identity and or radio bearer identity; the MAC entity distinguishes the PTM bearers of different MBS sessions by the radio network temporary identifier for groupcast / multicast service. The PTM bearer configuration only uses the default configuration. For each MBS session identity information in the received first information, the UE establishes the corresponding PTM radio bearer in the following steps:

[0212] 1> Establish a PDCP entity according to the first bearer configuration;

[0213] 2> Establish an RLC entity according to the first bearer configuration;

[0214] 3> configure a corresponding broadcast / multicast service logical channel for this radio bearer, and inform the MAC to receive the downlink shared channel in the cell where the first information is received, and the MAC uses the radio network temporary identifier for broadcast / multicast service and the scheduling information of the multicast service channel in the first information to receive the corresponding MBS service;

[0215] 4> establish the association between the logical channel and the PDCP entity corresponding to the radio bearer identifier or the MBS session identifier information.

[0216] 5> configure the physical layer parameters according to the information in the first information;

[0217] 6> inform the upper layer of the establishment of the PTM radio bearer in the following three ways:

[0218] Method 1: inform the upper layer of the establishment of the PTM radio bearer through the corresponding MBS session identifier information;

[0219] Method 2: establish a second SDAP entity for the MBS session, the second SDAP entity is used for the mapping between the QoS flow and the PTM radio bearer in the MBS session, and the SDAP entity is associated with the radio bearer, and the establishment of the user plane resource for the MBS session is informed to the upper layer.

[0220] Method 3: if the third SDAP entity corresponding to the MBS session does not exist, a third SDAP entity is established for the MBS session, the second SDAP entity is used for the mapping between the QoS flow and the PTM radio bearer in the MBS session and the mapping between the QoS flow and the PPT radio bearer in the MBS session.

[0221] The SDAP entity is associated with the radio bearer, and the establishment of the user plane resource for the MBS session is informed to the upper layer.

[0222] In an application embodiment, a method for releasing a PTM radio bearer is provided.

[0223] When the PTM radio bearer is released, the UE should perform one or more of the following steps:

[0224] Release the RLC entity and the related MAC and physical layer configuration;

[0225] Release the PDCP entity;

[0226] Inform the upper layer of the release of the PTM radio bearer through the corresponding MBS session identifier information;

[0227] Release the SDAP entity associated with the radio bearer;

[0228] In one application embodiment, a method for releasing an SDAP entity is provided.

[0229] Upon releasing a PTM radio bearer, the SDAP entity shall:

[0230] Upon receiving an indication from RRC (RRC entity within the UE) that a PTM radio bearer is released, the SDAP entity shall:

[0231] Release the SDAP entity associated with the PTM radio bearer.

[0232] In one embodiment, the first information comprises one or more of the following: MBS session identification information, radio network temporary identifier for group / multicast traffic, scheduling information of multicast traffic channel, physical layer parameters required for configuring multicast traffic channel, second bearer configuration. All QoS flows of one MBS session are mapped into one PTM radio bearer, different PTM radio bearers corresponding to different MBS sessions use the same logical channel identifier.

[0233] In one embodiment, the first bearer configuration comprises a default logical channel identifier and / or radio bearer identifier.

[0234] In another embodiment, the second bearer configuration can comprise any radio bearer identifier and / or logical channel identifier. The MAC entity distinguishes different PTM bearers of different MBS sessions by the radio network temporary identifier for group / multicast traffic.

[0235] For each MBS session identification information in the received first information, the procedure for establishing the corresponding PTM radio bearer by the UE comprises one or more of the following steps:

[0236] 1> For each MBS session identification, if the UE does not have a configured PTM radio bearer associated with this MBS session identification, the receiver shall:

[0237] 2> Establish a PDCP entity and configure it according to the first bearer configuration and / or the second bearer configuration;

[0238] 3> Establish an RLC entity and configure it according to the first bearer configuration and / or the second bearer configuration;

[0239] 4> Configure a group / multicast traffic logical channel corresponding to this radio bearer, instruct the MAC to receive the downlink shared channel in the cell where the first information is received, and use the radio network temporary identifier for group / multicast traffic and the scheduling information of multicast traffic channel in the first information to receive the corresponding MBS traffic;

[0240] 5> establish the association of this logical channel with the PDCP entity corresponding to this radio bearer identity or this MBS session identity information.

[0241] 6> configure the physical layer parameters according to the relevant information in the first information;

[0242] 7> inform the upper layer of the establishment of the PTM radio bearer in the following three ways:

[0243] Way 1: inform the upper layer of the establishment of the PTM radio bearer through the corresponding MBS session identity information;

[0244] Way 2: if the second SDAP entity corresponding to the received MBS session identity information does not exist, the second SDAP entity is used for the mapping of QoS flows in this MBS session to PTM radio bearers, establish a second SDAP entity; if the SDAP entity corresponding to the MBS session identity information does not exist before receiving this configuration information; inform the upper layer of the establishment of the user plane resources for this MBS session;

[0245] According to the first bearer configuration and / or the second bearer configuration, configure the second SDAP entity. Let this SDAP entity establish an association with this PTM radio bearer, and inform the upper layer of the establishment of the user plane resources for this MBS session.

[0246] Way 3: if the third SDAP entity corresponding to the received MBS session identity information does not exist, the third SDAP entity is used for the mapping of QoS flows in this MBS session to PTM radio bearers and the mapping of QoS flows in this MBS session to PTP radio bearers, establish a third SDAP entity; if the SDAP entity corresponding to the MBS session identity information does not exist before receiving this configuration information; inform the upper layer of the establishment of the user plane resources for this MBS session;

[0247] According to the first bearer configuration and / or the second bearer configuration, configure the third SDAP entity. Let this SDAP entity establish an association with this PTM radio bearer, and inform the upper layer of the establishment of the user plane resources for this MBS session.

[0248] 8> In this application, the configuration according to the first bearer configuration and / or the second bearer configuration includes the following ways:

[0249] Way 1: use the first bearer configuration to configure the corresponding parameters of the RLC entity or the PDCP entity or the SDAP entity.

[0250] Way 2: use the second bearer configuration to configure the corresponding parameters of the RLC entity or the PDCP entity or the SDAP entity.

[0251] Option 3: If the received second bearer configuration has parameters that are mutually overlapped or identical with the first bearer configuration, the received second bearer configuration is used to configure the part of parameters.

[0252] In one application embodiment, for each MBS session identity, if the UE has a configured PTM radio bearer associated with this MBS session identity, the receiver should:

[0253] If the received first information contains a second bearer configuration;

[0254] If this second bearer configuration carries a PDCP re-establishment indication; re-establish the PDCP entity according to the PDCP configuration contained in the first bearer configuration and / or the second bearer configuration;

[0255] If this second bearer configuration carries a PDCP configuration; reconfigure the PDCP entity of this radio bearer according to the PDCP configuration contained in the second bearer configuration;

[0256] If this second bearer configuration carries an RLC re-establishment indication: re-establish the RLC entity according to the RLC configuration contained in the first bearer configuration and / or the second bearer configuration;

[0257] If this second bearer configuration carries an RLC configuration: reconfigure the RLC entity of this radio bearer according to the RLC configuration contained in the second bearer configuration;

[0258] If this second bearer configuration carries an SDAP configuration: reconfigure the SDAP entity according to the SDAP configuration contained in the second bearer configuration.

[0259] In one embodiment, the first information contains one or more of the following: MBS session identity information, radio network temporary identifier for group / multicast traffic, scheduling information of multicast traffic channel, physical layer parameters required for configuring multicast traffic channel, second bearer configuration. All QoS flows of one MBS session are mapped into one or more PTM radio bearers, different PTM radio bearers within one MBS session use different logical channel identifiers. For each PTM bearer, the second bearer configuration contains any combination of the following: PTM radio bearer identifier, SDAP configuration, PDCP configuration, RLC bearer configuration, PTM radio bearer identifier, logical channel identifier. In one embodiment, the logical channel identifier used by a PTM bearer is mutually exclusive with the logical channel identifier used by a PTP, and the MAC entity distinguishes different radio bearers by logical channel identifier. In another embodiment, the MAC entity distinguishes different radio bearers of different MBS sessions by radio network temporary identifier for group / multicast traffic (e.g. g-RNTI) and logical channel identifier.

[0260] The configuration information in the second bearer configuration is the same as the information of the second bearer configuration provided in the above embodiments, and specific descriptions can be referred to the descriptions in other embodiments, which will not be described herein again.

[0261] The procedure of the UE establishing the PTM radio bearer is as follows:

[0262] 1> For each PTM radio bearer identity in the second bearer configuration, if this radio bearer is not part of the UE's existing configuration, the UE shall perform one or more of the following steps:

[0263] 2> Establish a PDCP entity and configure it according to the first bearer configuration and / or the second bearer configuration;

[0264] 3> Establish an RLC entity and configure it according to the first bearer configuration and / or the second bearer configuration;

[0265] 4> Configure a corresponding broadcast / multicast traffic logical channel according to the received logical channel configuration information, inform the MAC entity to receive the downlink shared channel in the cell where the first information is received, and use the radio network temporary identifier for broadcast / multicast traffic and the scheduling information of the multicast traffic channel in the first information to receive the corresponding MBS service;

[0266] 5> Associate the logical channel with the PDCP entity corresponding to the PTM radio bearer identity;

[0267] 6> Configure the physical layer parameters according to the information in the first information;

[0268] 7> The ways to inform the upper layer of the establishment of the PTM radio bearer are as follows:

[0269] Method 1: Inform the upper layer of the establishment of the PTM radio bearer through the corresponding MBS session identification information;

[0270] Method 2: If the second SDAP entity corresponding to the received MBS session identification information does not exist, establish a second SDAP entity for the mapping of the QoS flow and the PTM radio bearer in the MBS session; if the SDAP entity corresponding to the MBS session identification information does not exist before the reception of the configuration information: inform the upper layer of the establishment of the user plane resource for the MBS session;

[0271] Configure the second SDAP entity according to the first bearer configuration and / or the second bearer configuration. Associate the SDAP entity with the PTM radio bearer, and inform the upper layer of the establishment of the user plane resource for the MBS session.

[0272] Option 3: If the second SDAP entity corresponding to the received MBS session identification information does not exist, establish a second SDAP entity for the mapping of QoS flows to PTM radio bearers within this MBS session; if the SDAP entity corresponding to the MBS session identification information does not exist before receiving this configuration information: inform the upper layer of the establishment of user plane resources for this MBS session.

[0273] Configure the second SDAP entity according to the first bearer configuration and / or the second bearer configuration. Let this SDAP entity establish an association with this PTM radio bearer, and inform the upper layer of the establishment of user plane resources for this MBS session.

[0274] In one embodiment, a release method for releasing a PTM radio bearer is provided. The UE receives from the base station the first information carrying a list of PTM radio bearer identities to be released or a list of MBS session identification information corresponding to the PTM radio bearers to be released.

[0275] In one application embodiment, for each PTM radio bearer identity to be released, the UE should perform one or more of the following steps:

[0276] Release the PDCP entity and the PTM radio bearer identity;

[0277] If the SDAP entity associated with this radio bearer has been configured: inform the SDAP entity associated with this PTM radio bearer of the release of this radio bearer;

[0278] In one application embodiment, for each MBS session identification information to be released, the UE should perform one or more of the following steps:

[0279] Release all PTM radio bearers associated with this MBS session;

[0280] Release one or more of the following associated with this MBS session: radio resources, first SDAP entity, second SDAP entity, third SDAP entity, PDCP entity, RLC entity, PTP radio bearer identity, PTP radio bearer, PTM radio bearer identity, and PTM radio bearer.

[0281] In one application embodiment, a release method includes one or more of the following steps:

[0282] When the RRC (such as the RRC entity within the UE) applies to release the SDAP entity, the UE should: release the SDAP entity;

[0283] When the RRC (e.g., the RRC entity within the UE) indicates that one PTM radio bearer is released, the SDAP entity shall: remove all QoS flows mapped to this released PTM radio bearer;

[0284] When the MBS session ends, the following one or more associated with the MBS session are released: radio resources, the first SDAP entity, the second SDAP entity, the third SDAP entity, the PDCP entity, the RLC entity, the PTP radio bearer identifier, the PTP radio bearer, the PTM radio bearer identifier, and the PTM radio bearer.

[0285] In one application embodiment, Figure 8 is a flowchart of obtaining a broadcast message, as Figure 8 The base station sends a broadcast message to the UE, and the broadcast message carries the first information.

[0286] In one application embodiment, Figure 9 is a flowchart of base station and terminal interaction, as Figure 9 The base station sends an RRC message to the UE, and the RRC message carries the first information.

[0287] In the above two embodiments, two methods of the base station sending the first information to the UE are provided. In this embodiment, only the method of the base station sending the first information to the UE is described, and it is not limited. In actual application, any one of the above two methods can be selected.

[0288] It should be noted that in this application, only the method of the base station sending the first information to the UE is different, and the method of configuring the radio bearer after the UE receives the first message is the same, which can be referred to the description in other embodiments of the application. This embodiment will not be described again.

[0289] The following embodiments provide a scheme for how the gNB-CU and gNB-DU F1 interface manages the PTP radio bearer corresponding to the MBS service.

[0290] In one application embodiment, the context of the PTP RB is handed over by the UE-associated F1AP signaling interaction.

[0291] The gNB-CU maintains an MBS session context (including MBS session identifier information, a list of UEs joining the MBS session, and QoS parameters of QoS flow levels) and a UE context for each UE (including a list of PTP radio bearers of the UE).

[0292] The gNB-DU maintains one UE Context (containing the PTP radio bearer list of the UE) for each RRC connected UE, and maintains one MBS session context (containing the PTM radio bearer list of the session). The PTP radio bearer is handed over by the UE Context management, wherein the PTP radio bearer is associated with the MBS session corresponding to the radio bearer.

[0293] The interaction of PTP radio bearer on F1 is placed in each UE Context. The F1 interface needs to contain the IE for PTP radio bearer regarding the establishment, change, release of UE Context. The configuration of PTP radio bearer in the DRB to Be Setup List in the F1AP signaling contains the MBS session identification information (MBS session ID / TMGI).

[0294] Figure 10 is a flow chart of gNB-CU sending UE Context setup application message to gNB-DU, as shown in Figure 10 The gNB-CU sends the UE Context setup application message to the gNB-DU, and the gNB-DU sends the UE Context setup reply message to the gNB-CU.

[0295] The UE Context setup application message contains: the list of radio bearers to be established, the tunnel information corresponding to the radio bearer, and other UE context information. The list of radio bearers to be established contains PTP radio bearer information for MBS service to be established, which contains any of the following: radio bearer identifier, radio bearer QoS information, S-NSSAI, Notification Control, QoS flow list mapped to the radio bearer.

[0296] The PTP radio bearer information for MBS service contains MBS session identification information, which is associated with the radio bearer identifier and the QoS flow list mapped to the radio bearer, indicating which session's QoS flow is mapped to this PTP radio bearer.

[0297] Each QoS flow in the QoS flow list mapped to the radio bearer contains any combination of the following information: QoS flow identifier indicating that it is mapped to this radio bearer, QoS parameter indicating the QoS flow level, indication indicating that the QoS flow is mapped to this radio bearer, MBS session identification information. The MBS session identification information is associated with the QoS flow identifier, indicating which MBS session's QoS flow corresponding to this QoS flow identifier is mapped to this radio bearer.

[0298] The QoS parameters of the QoS flow level can include MBS session identification information, indicating which MBS session the relevant QoS flow belongs to.

[0299] Figure 11 The flowchart of the gNB-CU sending a UE context change application message to the gNB-DU is shown in FIG. 6. Figure 11 The gNB-CU sends a UE context change application message to the gNB-DU, and the gNB-DU sends a UE context change reply message to the gNB-CU, as shown in FIG. 6.

[0300] The UE context change application message includes a list of radio bearers to be established, tunnel information corresponding to the radio bearers, a list of radio bearers to be changed, and other UE context information.

[0301] The list of radio bearers to be established includes PTP radio bearer information for MBS services that need to be established. For each radio bearer to be established, the PTP radio bearer information for MBS services includes any of the following: radio bearer identification, radio bearer QoS information, S-NSSAI, Notification Control, and QoS flow list mapped to the radio bearer.

[0302] The PTP radio bearer information for MBS services includes MBS session identification information, which is associated with the radio bearer identification and the QoS flow list mapped to the radio bearer, indicating which session's QoS flow is mapped to this PTP radio bearer.

[0303] Each QoS flow in the QoS flow list mapped to the radio bearer includes any combination of the following information: QoS flow identification indicating that it is mapped to this radio bearer, QoS parameters of the QoS flow level, an indication indicating that the QoS flow is mapped to this radio bearer, and MBS session identification information. The MBS session identification information is associated with the QoS flow identification, indicating which MBS session's QoS flow corresponding to the QoS flow identification is mapped to this radio bearer.

[0304] The QoS parameters of the QoS flow level can include MBS session identification information, indicating which MBS session the relevant QoS flow belongs to.

[0305] The list of wireless bearers that need to be changed contains PTP wireless bearer information for MBS services that need to be changed. For each wireless bearer that needs to be changed, the PTP wireless bearer information for MBS services contains any of the following: wireless bearer identifier, wireless bearer QoS information, S-NSSAI, Notification Control, QoS flow list mapped to the wireless bearer. Each QoS flow information in the QoS flow list mapped to the wireless bearer contains any combination of the following information: QoS flow identifier indicating that it is mapped to this wireless bearer, QoS parameter of QoS flow level, and indication indicating that the QoS flow is mapped to this wireless bearer in uplink or downlink.

[0306] The PTP wireless bearer information for MBS services contains MBS session identifier information, which is associated with the wireless bearer identifier and the QoS flow list mapped to this wireless bearer, indicating which session's QoS flow is mapped to this PTP wireless bearer.

[0307] Each QoS flow information in the QoS flow list mapped to the wireless bearer contains MBS session identifier information. The MBS session identifier information is associated with the QoS flow identifier, indicating which MBS session's QoS flow corresponding to this QoS flow identifier is mapped to this wireless bearer.

[0308] The QoS parameter of the QoS flow level can contain MBS session identifier information, indicating which MBS session the relevant QoS flow belongs to.

[0309] In one embodiment, the present application provides a bearer configuration device, Figure 12 A structural schematic diagram of a bearer configuration device provided by an embodiment of the present application. The device can be suitable for the case where a user establishes or modifies a wireless bearer. The bearer configuration device can be realized by software and / or hardware, and the device is configured in a first communication node.

[0310] As Figure 12 shown, the bearer configuration device provided by the embodiment of the present application mainly includes a receiving module 121 and an establishing module 122.

[0311] The receiving module 121 receives first information.

[0312] The establishing and modifying module 122 is configured to configure wireless bearers of a multicast MBS based on the first information, wherein the wireless bearers include point-to-point PTP bearers and / or point-to-multipoint PTM bearers, and the configuration includes one or more of the following: establishment, modification, and release.

[0313] In an example embodiment, the first information comprises PTP bearer configuration information based on which the PTP bearer is configured, and the PTP bearer configuration information comprises one or more of the following:

[0314] PTP radio bearer identity, service data adaptation protocol (SDAP) configuration information, packet data convergence protocol (PDCP) configuration information, RLC bearer configuration information.

[0315] In an example embodiment, the first information comprises second information based on which the PTM bearer is configured, and the second information comprises one or more of the following:

[0316] a list of ongoing MBS identity information, MBS identity information, scheduling information corresponding to each MBS identity information, radio network temporary identity for the multicast / broadcast service, scheduling information of the multicast service channel, physical layer parameters required for configuring the multicast service channel, second bearer configuration.

[0317] The second bearer configuration comprises one or more of the following: PTM radio bearer identity, logical channel identity, SDAP configuration information, PDCP configuration information, RLC bearer configuration information.

[0318] In an example embodiment, the PTM bearer configuration information required for configuring the PTM bearer comprises one or more of the following:

[0319] first bearer configuration, second bearer configuration;

[0320] The first bearer configuration adopts a default configuration, and the first bearer configuration comprises one or more of the following: PTM radio bearer identity, logical channel identity, SDAP configuration information, PDCP configuration information, RLC bearer configuration information.

[0321] In an example embodiment, the SDAP configuration information comprises one or more of the following:

[0322] an indication of whether the radio bearer is a default radio bearer, an indication of whether downlink data on the radio bearer has an SDAP header, an indication of whether uplink data of the radio bearer has an SDAP header, MBS identity information, a list of uplink QoS flows in an MBS session that need to be added to the radio bearer, a list of QoS flows in an MBS session that have been mapped to the radio bearer and need to be released.

[0323] In an example embodiment, the MBS identity information comprises one or more of the following:

[0324] MBS session identity, a temporary mobile group identity TMGI of a multicast service, a multicast service identity, a PDU session identity indicating the MBS session.

[0325] In an example embodiment, in case that the SDAP configuration information is carried in the PTP bearer configuration information, one or more of the following operations are performed:

[0326] establishing a first SDAP entity;

[0327] configuring the first SDAP entity based on the carried SDAP configuration information;

[0328] establishing an association between the first SDAP entity and a radio bearer corresponding to the PTP radio bearer identity;

[0329] wherein the first SDAP entity is used for mapping of QoS flows within the MBS identity information to PTP radio bearers.

[0330] In an example embodiment, in case that the SDAP configuration information is included in the PTM bearer configuration information, one or more of the following operations are performed:

[0331] establishing a second SDAP entity;

[0332] configuring the second SDAP entity based on the SDAP configuration information in the first bearer configuration and / or the second bearer configuration;

[0333] establishing an association between the second SDAP entity and a radio bearer corresponding to the PTP radio bearer identity;

[0334] wherein the second SDAP entity is used for mapping of QoS flows within the MBS identity information to PTM radio bearers.

[0335] In an example embodiment, in case that the SDAP configuration information is included in the PTP bearer configuration information or the PTM bearer configuration information, one or more of the following operations are performed:

[0336] establishing a third SDAP entity;

[0337] configuring the third SDAP entity based on the SDAP configuration information;

[0338] establishing an association between the third SDAP entity and a radio bearer corresponding to the PTP radio bearer identity or the PTM radio bearer identity;

[0339] wherein the third SDAP entity is used for mapping of QoS flows within the MBS identity information to PTP radio bearers and PTM radio bearers.

[0340] In one example embodiment, the PDCP configuration information comprises one or more of the following:

[0341] an indication of whether to use ciphering algorithm, a timer for discarding PDCP packets, whether to continue or reset ROHC header compression protocol at PDCP entity re-establishment, header compression configuration, whether the radio bearer is configured with integrity protection, a maximum value of header compression CID parameter, whether the PDCP entity is associated with more than one RLC entity in uplink data transmission, whether to allow out-of-order, whether uplink PDCP duplication is configured and activated, downlink PDCP sequence number size, uplink PDCP sequence number size, an indication of the primary RLC entity corresponding to the cell group ID and LCID in uplink data transmission when the PDCP entity is associated with more than one RLC entity, whether the radio bearer is configured to transmit PDCP status report, reordering time, a data volume threshold for uplink data using split bearer.

[0342] In one example embodiment, the RLC bearer configuration information comprises one or more of the following: logical channel identity, radio bearer identity served by the RLC bearer, RLC configuration, logical channel configuration, whether to re-establish the RLC identity, maximum number of retransmission, poll byte number, poll PDU, sn-Field length, timer under RLC AM, reassembly timer, status report timer.

[0343] In one example embodiment, all QoS flows of one MBS identity information are mapped to one PTM radio bearer, and different PTM radio bearers corresponding to different MBS identity information use the same logical channel identity.

[0344] In one example embodiment, all QoS flows of one MBS identity information are mapped to one or more PTM radio bearers, and different PTM radio bearers corresponding to the same MBS identity information use different logical channel identities.

[0345] In one example embodiment, one or more of the following operations are performed for each MBS identity information:

[0346] establishing a PDCP entity based on the first bearer configuration and / or the second bearer configuration;

[0347] establishing a RLC entity based on the first bearer configuration and / or the second bearer configuration;

[0348] configuring a corresponding broadcast / multicast service logical channel for the radio bearer in the MAC entity;

[0349] establishing an association between the PDCP entity and the broadcast / multicast service logical channel;

[0350] the broadcast / multicast service logical channel uses a default logical channel identity.

[0351] establishing an association between the PDCP entity and the G / MC logical channel.

[0352] In one exemplary embodiment, one PDCP entity is established for each PTM radio bearer identity;

[0353] establishing one PDCP entity;

[0354] establishing one RLC entity;

[0355] configuring one G / MC logical channel corresponding to the PTM radio bearer identity in the MAC entity;

[0356] establishing an association between the PDCP entity and the G / MC logical channel.

[0357] The bearer configuration apparatus provided in the embodiment can execute the bearer configuration method provided in any embodiment of the application, and has the corresponding function modules and beneficial effects for executing the method. Technical details not described in detail in the embodiment can be referred to the bearer configuration method provided in any embodiment of the application.

[0358] It is worth noting that, in the above embodiment of the bearer configuration apparatus, each unit and module included is only divided according to functional logic, but is not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of each functional unit are only for convenient mutual distinction, and do not limit the protection scope of the application.

[0359] In one embodiment, the application provides a context message management apparatus, Figure 13 A structural schematic diagram of a context message management apparatus provided in an embodiment of the application. The method can be applied to the case of bearer configuration information inside a base station. The context message management apparatus can be realized by software and / or hardware, and the apparatus is configured in a second communication node.

[0360] As Figure 13 shown, the context message management apparatus provided in an embodiment of the application mainly includes a first sending module 131 and a management module 132.

[0361] The first sending module is configured to send a context application message of a first communication node; wherein the context application message includes a context establishment application message and a context change application message;

[0362] The management module is configured to manage a radio bearer of an MBS session based on the context application message.

[0363] In an exemplary embodiment, the list of required modified radio bearers comprises radio bearer information for the MBS session required to be established, wherein the list of required modified radio bearers is carried by the context setup request message, or by the context change request message.

[0364] In an exemplary embodiment, the radio bearer information comprises MBS session identification information, wherein the MBS session identification information is associated with a radio bearer identity, a list of QoS flows mapped to the radio bearer.

[0365] In an exemplary embodiment, the MBS session identification is associated with a radio bearer identity, a list of QoS flows mapped to the radio bearer.

[0366] In an exemplary embodiment, for each QoS flow in the list of QoS flows mapped to the radio bearer, one or more of the following are included:

[0367] a QoS flow identity, a QoS flow priority, a QoS flow mapping indication parameter, MBS session identification information.

[0368] wherein the MBS session identification information is associated with the QoS flow identity.

[0369] In an exemplary embodiment, the QoS flow priority comprises MBS session identification information, for indicating the MBS session to which the QoS flow belongs.

[0370] The context message management apparatus provided in the embodiment can perform the context message management method provided in any embodiment of the present application, and has the corresponding function modules and beneficial effects of performing the method. Technical details not described in detail in the embodiment can be referred to the context message management method provided in any embodiment of the present application.

[0371] It is worth noting that, in the embodiments of the above context message management apparatus, each unit and module included is only divided according to the function logic, but is not limited to the above division, as long as the corresponding function can be realized; in addition, the specific name of each functional unit is only for the convenience of mutual differentiation, and does not limit the protection scope of the present application.

[0372] In an embodiment, the present application provides a releasing device, Figure 14 A structural schematic diagram of a releasing device provided in an embodiment of the present application. The device can be suitable for the case that the user equipment releases the radio bearer and SDAP. The releasing device can be realized by software and / or hardware, and the device is configured in the first communication node.

[0373] As Figure 14As shown, the release method provided by the embodiments of the present application mainly includes a first release module 141 and a second release module 142.

[0374] The first release module 141 is configured to release a radio bearer associated with the MBS session when a release condition is met.

[0375] The second release module 142 is configured to release an SDAP entity.

[0376] The release condition includes one or more of the following:

[0377] The MBS session ends;

[0378] The first information is received, and the first information carries a radio bearer identifier to be released.

[0379] In an exemplary embodiment, 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.

[0380] In an exemplary embodiment, the second release module 142 is configured to release all SDAP entities associated with the MBS session when the MBS session ends.

[0381] In an exemplary embodiment, the second release module 142 is configured to release all SDAP entities associated with the MBS session when the upper layer indicates to release the SDAP entities associated with the PTM radio bearer of the MBS session.

[0382] In an exemplary embodiment, the second release module 142 is configured to release the SDAP entity when the radio bearer associated with the SDAP entity is released.

[0383] The release device provided in the embodiments can perform the access control method provided by any of the embodiments of the present application, and has the corresponding function modules and beneficial effects of performing the method. Technical details not described in detail in the embodiments can be referred to the release method provided by any of the embodiments of the present application.

[0384] It is worth noting that in the above embodiments of the release device, each unit and module included is only divided according to the function logic, but is not limited to the above division, as long as the corresponding function can be realized; in addition, the specific name of each functional unit is only for easy distinction, and does not limit the protection scope of the present application.

[0385] The embodiments of the present application also provide a device, Figure 15 is a structural schematic diagram of a device provided by the embodiments of the present application, like Figure 15As shown, the device includes a processor 151, a memory 152, an input device 153, an output device 154, and a communication device 155; the number of processors 151 in the device can be one or more, Figure 15 The processor 151 in the device is taken as an example in this embodiment; the processor 151, the memory 152, the input device 153, and the output device 154 in the device can be connected through a bus or other means, Figure 15 The connection through the bus is taken as an example in this embodiment.

[0386] The memory 152, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the bearer configuration method in this embodiment (for example, the receiving module 121 and the establishment and modification module 122 in the bearer configuration apparatus), and such as program instructions / modules corresponding to the context message management method in this embodiment (for example, the first sending module 131 and the management module 132 in the context message management apparatus), and such as program instructions / modules corresponding to the release method in this embodiment (for example, the first release module 141 and the second release module 142 in the release apparatus). The processor 151 executes various function applications and data processing of the device by running the software programs, instructions, and modules stored in the memory 152, that is, implements any method provided in this embodiment.

[0387] The memory 152 can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system and at least one application required by a function; the data storage area can store data created according to the use of the device, etc. In addition, the memory 152 can include a high-speed random access memory, and can also include a non-volatile memory, for example, at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some examples, the memory 152 can further include a memory remotely arranged with respect to the processor 151, which can be connected to the device through a network. Examples of the above network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0388] The input device 153 can be used to receive input digital or character information, and generate key signal input related to the user settings and function control of the device. The output device 154 can include a display device such as a display screen.

[0389] The communication device 155 can include a receiver and a transmitter. The communication device 155 is set to perform information receiving and transmitting communication according to the control of the processor 151.

[0390] It should be noted that, in the case of the above device being the first communication node, the processor 151 performs various function applications and data processing by running programs stored in the system memory 152, such as implementing the bearer configuration method provided by the embodiments of the present application, which is applied to the first communication node, including:

[0391] receiving first information;

[0392] configuring a radio bearer of a 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.

[0393] Of course, those skilled in the art can understand that the processor 151 can also implement the technical solutions of the bearer configuration information method provided by any of the embodiments of the present application. The hardware structure and functions of the device can be referred to the content explained in the present embodiment.

[0394] It should be noted that, in the case of the above device being the second communication node, the processor 151 performs various function applications and data processing by running programs stored in the system memory 152, such as implementing the context message management method provided by the embodiments of the present application, which is applied to the second communication node, including:

[0395] sending a context application message of the first communication node; wherein the context application message includes a context establishment application message and a context change application message;

[0396] managing a radio bearer of an MBS session based on the context application message.

[0397] Of course, those skilled in the art can understand that the processor 151 can also implement the technical solutions of the context message management method provided by any of the embodiments of the present application. The hardware structure and functions of the device can be referred to the content explained in the present embodiment.

[0398] It should be noted that, in the case of the above device being the first communication node, the processor 151 performs various function applications and data processing by running programs stored in the system memory 152, such as implementing the release method provided by the embodiments of the present application, including:

[0399] releasing a radio bearer associated with the MBS session in the case of meeting a release condition;

[0400] releasing an SDAP entity;

[0401] wherein the release condition includes one or more of the following:

[0402] the MBS session is ended;

[0403] receiving the first information, wherein the first information carries an identifier of a radio bearer to be released.

[0404] Of course, those skilled in the art can understand that the processor 151 can also implement the technical solutions of the release method provided by any of the embodiments of the present application. The hardware structure and functions of the device can be understood from the content of the present embodiment.

[0405] The present embodiment also provides a storage medium containing computer executable instructions, which, when executed by a computer processor, are used to execute a bearer configuration method, the method being applied to a first communication node, comprising:

[0406] receiving first information;

[0407] configuring a radio bearer of a multicast broadcast (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.

[0408] Of course, the storage medium containing computer executable instructions provided by the present embodiment is not limited to the operation of the radio bearer configuration method as described above, but can also perform related operations in the radio bearer configuration method provided by any of the embodiments of the present application.

[0409] The present embodiment also provides a storage medium containing computer executable instructions, which, when executed by a computer processor, are used to execute a context message management method, the method being applied to a second communication node, comprising:

[0410] sending a context application message of a first communication node; wherein the context application message includes a context establishment application message and a context change application message;

[0411] managing a radio bearer of an MBS session based on the context application message.

[0412] Of course, the storage medium containing computer executable instructions provided by the present embodiment is not limited to the operation of the context message management method as described above, but can also perform related operations in the context message management method provided by any of the embodiments of the present application.

[0413] The present embodiment also provides a storage medium containing computer executable instructions, which, when executed by a computer processor, are used to execute a release method, comprising:

[0414] releasing a radio bearer associated with an MBS session if a release condition is met;

[0415] releasing an SDAP entity;

[0416] The release condition comprises one or more of the following:

[0417] The MBS session ends;

[0418] The first information is received, and the first information carries a radio bearer identifier to be released.

[0419] Of course, the storage medium provided by the embodiment of the present application contains computer executable instructions, which are not limited to the release method operations described above, but can also perform related operations in the release method provided by any embodiment of the present application.

[0420] From the above description of the embodiments, those skilled in the art can clearly understand that the present application can be realized by means of software and necessary universal hardware, and of course can also be realized by hardware, but in many cases the former is a better embodiment. Based on such understanding, the technical solutions of the present application or the part that contributes to the prior art can be embodied in the form of a software product, which can be stored in a computer readable storage medium, such as a floppy disk, a read-only memory (ROM), a random access memory (RAM), a FLASH memory, a hard disk or an optical disk, etc., including a plurality of instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) execute the methods described in various embodiments of the present application.

[0421] The above is only exemplary embodiments of the present application, and is not intended to limit the protection scope of the present application.

[0422] Those skilled in the art will appreciate that the term user terminal encompasses any suitable type of wireless user device, such as a mobile phone, a portable data processing apparatus, a portable web browser, or a vehicle-mounted mobile station.

[0423] Generally, various embodiments of the present application can be implemented in hardware or special-purpose circuitry, software, logic or any combination thereof. For example, some aspects can be implemented in hardware, while other aspects can be implemented in firmware or software which can be executed by a controller, microprocessor or other computing device, although the present application is not limited thereto.

[0424] Embodiments of the application can be implemented by computer program instructions on a data processor of a mobile device, for example in a processor entity, or by hardware, or by a combination of software and hardware. Computer program instructions can be in the form of assembly language, instructions for an instruction-set-architecture (ISA), machine code, machine dependent instructions, microcode, firmware instructions, state-setting data, or in any combination of one or more programming languages, written in any combination of one or more of low-level programming languages, high-level programming languages, and / or declarative programming languages.

[0425] Any flow diagrams of the figures can represent program steps in a particular implementation. Alternatively, the flow diagrams of the figures can represent modules, segments, or portions of code which include one or more executable instructions for implementing specific logic functions (or steps in a procedure). The program steps, modules, segments, or portions of code can be erased after the program steps have been executed one or more times. The flow diagrams of the figures can also represent logical operations, modules, and functions, which can be implemented in hardware, software, or a combination of hardware and software.

[0426] The detailed description of the exemplary embodiments of the application has been provided above with reference to the accompanying drawings, but various modifications and alterations of the above embodiments are obvious to those skilled in the art, without departing from the scope of the present application. Thus, the proper scope of the present application should be determined by the following claims.

Claims

1. A method of bearer configuration, characterized by, The method is applied to a first communication node, comprising: receiving first information; configuring a wireless bearer of a multicast broadcast service (MBS) based on the first information; wherein the wireless bearer comprises a point-to-point (PTP) bearer and / or a point-to-multipoint (PTM) bearer; wherein the first information contains second information; configuring the wireless bearer of the MBS based on the first information, comprising: configuring a PTM bearer based on the second information; wherein the second information comprises MBS identification information and second bearer configuration; the second bearer configuration comprises a PTM wireless bearer identifier, a logical channel identifier, and PDCP configuration information; wherein all QoS flows of one MBS identification information are mapped into one PTM wireless bearer, and different PTM wireless bearers corresponding to different MBS identification information use the same logical channel identifier; or all QoS flows of one MBS identification information are mapped into one or more PTM wireless bearers, and different PTM wireless bearers of the same MBS identification information use different logical channel identifiers.

2. The method of claim 1, wherein, The first information contains PTP bearer configuration information, and a PTP bearer is configured based on the PTP bearer configuration information, wherein the PTP bearer configuration information comprises one or more of the following information: a PTP wireless bearer identifier, service data adaptation protocol (SDAP) configuration information, packet data convergence protocol (PDCP) configuration information, and RLC bearer configuration information.

3. The method of claim 1, wherein, The second bearer configuration further contains one or more of the following:

4. The method of claim 3, wherein, SDAP configuration information and RLC bearer configuration information. The PTM bearer configuration information required for configuring a PTM bearer comprises one or more of the following: first bearer configuration and second bearer configuration; 5. The method according to any one of claims 2-4, characterized in that, wherein the first bearer configuration adopts a default configuration, and the first bearer configuration comprises one or more of the following: a PTM wireless bearer identifier, a logical channel identifier, SDAP configuration information, PDCP configuration information, and RLC bearer configuration information.

6. The method of claim 5, wherein, The SDAP configuration information comprises one or more of the following: an indication of whether the wireless bearer is a default wireless bearer, an indication of whether downlink data on the wireless bearer has an SDAP header, an indication of whether uplink data of the wireless bearer has an SDAP header, MBS identification information, a list of uplink QoS flows within an MBS session that need to be added to the wireless bearer, and a list of QoS flows within an MBS session that have been mapped to the wireless bearer and need to be released.

7. The method of claim 2, wherein, The MBS identification information comprises one or more of the following: an MBS session identifier, a temporary mobile group identifier (TMGI) of a multicast broadcast service, an identifier of a multicast broadcast service, and a PDU session identifier indicating an MBS session. In the case where the SDAP configuration information is carried in the PTP bearer configuration information, one or more of the following operations are performed: establishing a first SDAP entity; configuring the first SDAP entity based on the carried SDAP configuration information; establishing an association between the first SDAP entity and a wireless bearer corresponding to the PTP wireless bearer identifier; wherein the first SDAP entity is used for mapping QoS flows within the MBS identification information to a PTP wireless bearer.

8. The method of claim 4 wherein, In the case that the PTM bearer configuration information contains SDAP configuration information, one or more of the following operations are performed: establishing a second SDAP entity; configuring the second SDAP entity based on the SDAP configuration information in the first bearer configuration and / or the second bearer configuration; establishing an association between the second SDAP entity and the radio bearer corresponding to the PTP radio bearer identifier; wherein the second SDAP entity is used for mapping of QoS flows within the MBS identification information to the PTM radio bearer.

9. The method of claim 2 or 4, wherein, In the case that the PTP bearer configuration information or the PTM bearer configuration information contains SDAP configuration information, one or more of the following operations are performed: establishing a third SDAP entity; configuring the third SDAP entity based on the SDAP configuration information; establishing an association between the third SDAP entity and the radio bearer corresponding to the PTP radio bearer identifier or the PTM radio bearer identifier; wherein the third SDAP entity is used for mapping of QoS flows within the MBS identification information to the PTP radio bearer and the PTM radio bearer.

10. The method of any of claims 2-4, wherein, The PDCP configuration information includes one or more of the following: an indication of whether to use an encryption algorithm, a timer for discarding PDCP packets, whether the PDCP entity continues or resets the ROHC header compression protocol upon reestablishment, header compression configuration, whether the radio bearer is configured with integrity protection, a maximum value of the header compression CID parameter, whether the PDCP entity is associated with more than one RLC entity in uplink data transmission, whether to allow out-of-order, whether uplink PDCP duplication is configured and activated, downlink PDCP sequence number size, uplink PDCP sequence number size, an indication of the cell group ID and LCID corresponding to the primary RLC entity when more than one RLC entity is associated in uplink data transmission, whether the radio bearer is configured to transmit PDCP status reports, reordering time, and a data volume threshold for using split bearers in uplink data.

11. The method of any of claims 2-4, wherein, The RLC bearer configuration information contains one or more of the following: a logical channel identifier, a radio bearer identifier served by the RLC bearer, RLC configuration, logical channel configuration, whether to reestablish the RLC identifier, maximum number of retransmissions, poll byte number, poll PDU, sn-Field length, timer under RLC AM, reassembly timer, and status report timer.

12. The method of claim 1 or 4, wherein, For each MBS identification information, one or more of the following operations are performed: establishing a PDCP entity based on the first bearer configuration and / or the second bearer configuration; establishing an RLC entity based on the first bearer configuration and / or the second bearer configuration; configuring a broadcast / multicast service logical channel corresponding to the radio bearer in the MAC entity; establishing an association between the PDCP entity and the broadcast / multicast service logical channel; the broadcast / multicast service logical channel uses a default logical channel identifier.

13. The method of any one of claims 1 or 4, wherein, For each PTM radio bearer identifier, one or more of the following operations are performed: establishing a PDCP entity; establishing an RLC entity; configuring a broadcast / multicast service logical channel corresponding to the PTM radio bearer identifier in the MAC entity; establishing an association between the PDCP entity and the broadcast / multicast service logical channel.

14. A context message management method characterized by, The method is applied to a second communication node, and comprises: sending a context application message of the first communication node; wherein the context application message comprises a context establishment application message or a context modification application message; managing radio bearers of the MBS based on the context application message; wherein the context application message contains one or more of the following information: a list of radio bearers for the MBS required to be established, a list of radio bearers for the MBS session required to be modified; wherein each item of the radio bearer information comprises one or more of the following information: MBS identification information, radio bearer identification, a list of QoS flows mapped to the radio bearer, QoS flow identification, QoS flow level QoS parameter, QoS flow mapping indication parameter; wherein, in the case that the radio bearer comprises a point-to-multipoint (PTM) bearer, all QoS flows of one MBS identification information are mapped into one PTM radio bearer, and different PTM radio bearers corresponding to different MBS identification information use the same logical channel identification; or in the case that the radio bearer comprises a point-to-multipoint (PTM) bearer, all QoS flows of one MBS identification information are mapped into one or more PTM radio bearers, and different PTM radio bearers of the same MBS identification information use different logical channel identifications.

15. The method of claim 14, wherein, The MBS identification information comprises one or more of the following: MBS session identification, temporary mobile group identification (TMGI) of the multicast service, multicast service identification, PDU session identification indicating the MBS session.

16. The method of claim 14, wherein, The MBS identification information is associated with the radio bearer identification and / or the list of QoS flows mapped to the radio bearer.

17. The method of claim 14, wherein, The MBS identification information is associated with the QoS flow identification.

18. The method of claim 14, wherein, The QoS parameter of the QoS flow level comprises: MBS identification information used to indicate the MBS session to which the QoS flow belongs.

19. A bearer configuration apparatus, characterized by The device is configured in a first communication node, comprising: a receiving module configured to receive first information; an establishment and modification module configured to configure radio bearers of a multicast broadcast service (MBS) based on the first information; wherein the radio bearers comprise point-to-point (PTP) bearers and / or point-to-multipoint (PTM) bearers; wherein the first information contains second information; the configuration of the radio bearers of the multicast broadcast service (MBS) based on the first information comprises: configuration of the PTM bearers based on the second information; wherein the second information comprises MBS identification information and second bearer configuration; the second bearer configuration comprises PTM radio bearer identification, logical channel identification, and PDCP configuration information; wherein, in the case that the radio bearer comprises a point-to-multipoint (PTM) bearer, all QoS flows of one MBS identification information are mapped into one PTM radio bearer, and different PTM radio bearers corresponding to different MBS identification information use the same logical channel identification; or in the case that the radio bearer comprises a point-to-multipoint (PTM) bearer, all QoS flows of one MBS identification information are mapped into one or more PTM radio bearers, and different PTM radio bearers of the same MBS identification information use different logical channel identifications.

20. A context message management apparatus characterized by comprising: The device is configured in a second communication node, comprising: The first sending module is configured to send a context application message of the first communication node; wherein the context application message comprises a context establishment application message and a context change application message; The management module is configured to manage radio bearers of the MBS session based on the context application message; The context application message contains one or more of the following information: a list of radio bearers for MBS required to be established, a list of radio bearers for MBS session required to be modified; wherein each item of the radio bearer information comprises one or more of the following information: MBS identification information, radio bearer identification, QoS flow list mapped to the radio bearer, QoS flow identification, QoS parameter of QoS flow level, QoS flow mapping indication parameter; In the case where the radio bearer comprises a point-to-multipoint (PTM) bearer, all QoS flows of one MBS identification information are mapped into one PTM radio bearer, and different PTM radio bearers corresponding to different MBS identification information use the same logical channel identification; or, In the case where the radio bearer comprises a point-to-multipoint (PTM) bearer, all QoS flows of one MBS identification information are mapped into one or more PTM radio bearers, and different PTM radio bearers of the same MBS identification information use different logical channel identifications.

21. An apparatus, comprising: Comprise: One or more processors; 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 implement the method of any one of claims 1-18.

22. A storage medium, characterized by The storage medium stores a computer program, and the computer program is executed by a processor to implement the method of any one of claims 1-18.

Images