Method and equipment for supporting multicast service transmission
By dynamically managing the user plane in the 5G communication system, the problem of low utilization of multicast transmission resources under the shared access network architecture is solved, efficient resource utilization and service continuity are achieved, and the stability and efficiency of the system are improved.
Patent Information
- Application Number
- CN202410158815.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-09-21
- Filing Date
- 2024-02-04
- Publication Date
- 2024-11-12
AI Technical Summary
In 5G or quasi-5G communication systems, under the shared access network architecture, the resource utilization rate of multicast transmission is not high, resulting in resource waste and business continuity problems. Especially in the shared environment of multiple operators, the same MBS services are Different operators transmit with different resource identifiers, resulting in low network resource utilization.
By dynamically establishing and managing user planes, using the same resources to transmit MBS services of multiple operators, through coordination between CU-CP and CU-UP, it is established only on one user plane, while the user planes of other operators are not established , thereby saving access network and air interface resources, improving resource utilization efficiency, and realizing continuous data transmission on F1 tunnel.
It effectively improves the utilization rate of wireless network and air interface resources, ensures the continuity of MBS services, reduces resource consumption, avoids data loss and repeated transmission, and improves the stability and efficiency of the system.
Smart Images

Figure CN118945602A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to wireless communication technology, and in particular to an improved multicast transmission method and device. Background Art
[0002] In order to meet the increased demand for wireless data communication services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or quasi-5G communication systems. Therefore, 5G or quasi-5G communication systems are also referred to as "super 4G networks" or "post-LTE systems."
[0003] Wireless communication is one of the most successful innovations in modern history. The number of subscribers to wireless communication services recently exceeded 5 billion and continues to grow rapidly. The demand for wireless data services is growing rapidly due to the increasing popularity of smartphones and other mobile data devices (e.g., tablets, laptops, netbooks, e-book readers, and machine-type devices) among consumers and enterprises. In order to meet the high growth of mobile data services and support new applications and deployments, it is critical to improve the efficiency and coverage of the wireless interface. Summary of the invention
[0004] The present invention provides a method and a device for dynamically establishing a multicast transmission user plane when a shared access network is a separated architecture.
[0005] The present invention provides a method and device for multicast transmission. When the shared access network is a separated architecture, a user plane for transmitting broadcast and multicast services is dynamically established to save access network resources and air interface resources and improve the utilization efficiency of access network resources and air interface resources.
[0006] According to some embodiments of the present disclosure, a method performed by a first network node in a wireless communication system is provided, comprising: receiving a first message from a second network node, the first message comprising first indication information and user plane address information of a second broadcast session, wherein the first indication information indicates that an error has occurred in the user plane of the first broadcast session; and sending a second message to a third network node, the second message comprising the user plane address information of the second broadcast session.
[0007] In some examples, the method also includes storing context information for the second broadcast session.
[0008] In some examples, the method further includes sending a third message to a fourth network node, the third message including information indicating that the fourth network node receives data from the F1 tunnel corresponding to the second broadcast session. In some examples, the method further includes sending a fourth message to the fourth network node, the fourth message indicating whether the fourth network node establishes the F1 tunnel for the second broadcast session.
[0009] In some examples, the fourth message is a context modification request message for the first broadcast session or a context establishment request message for the second broadcast session.
[0010] In some examples, the method also includes sending a fifth message to the second network node, the fifth message including user plane address information for the second broadcast session.
[0011] In some examples, the method also includes sending a sixth message to the second network node, the sixth message indicating whether the second network node establishes an F1 tunnel for the second broadcast session.
[0012] In some examples, the sixth message is a bearer modification request message of the first broadcast session or a bearer establishment request message of the second broadcast session.
[0013] In some examples, the first message and the second message also include a sequence number.
[0014] According to some embodiments of the present disclosure, a method performed by a second network node in a wireless communication system is provided, comprising: discovering an error in a user plane; and sending a first message to a first network node, the first message comprising first indication information and user plane address information of a second broadcast session, wherein the first indication information indicates that an error has occurred in the user plane of the first broadcast session.
[0015] In some examples, discovering the user plane error includes: discovering the user plane error through a General Packet Radio Service GPRS Tunneling Protocol GTP-U mechanism of the user plane, or discovering the error through a received GTP-U sequence number.
[0016] In some examples, the first message also includes a sequence number.
[0017] According to some embodiments of the present disclosure, a method performed by a user equipment UE in a wireless communication system is provided, comprising: receiving a seventh message from a fifth network node, the seventh message comprising a multicast service MBS session identifier and second indication information, wherein the second indication information indicates that the UE wishes to remain in a radio resource control (RRC) connected mode to receive the MBS; receiving a group paging message from a sixth network node, the group paging message comprising a multicast service session identifier and third indication information, wherein the third indication information indicates that the UE remains in an RRC inactive state to receive the MBS; and according to the second indication information, entering the RRC connected mode to receive the MBS.
[0018] In some examples, the fifth network node is an access control and mobility management function entity AMF of the core network.
[0019] According to some embodiments of the present disclosure, a method performed by a sixth network node in a wireless communication system is provided, comprising: receiving an eighth message from a fifth network node, the eighth message comprising a multicast service MBS session identifier and second indication information, wherein the second indication information indicates that the UE wishes to remain in a radio resource control RRC connected mode to receive the MBS, receiving an MBS activation request from the fifth network node, and sending a group paging message to a user equipment UE, the group paging message comprising the MBS session identifier and third indication information, wherein the third indication information indicates that the UE remains in an RRC inactive state to receive the MBS.
[0020] In some examples, the fifth network node is an access control and mobility management function entity AMF of the core network.
[0021] In some examples, the method also includes sending a dedicated paging request message to the UE based on the second indication information.
[0022] In some examples, the method also includes sending a message to the UE to configure the UE to enter an RRC inactive state, the message carrying an MBS session identifier and fourth indication information, the fourth indication information instructing the UE to remain in the RRC inactive state to receive the MBS.
[0023] According to some embodiments of the present disclosure, a network node is further provided, the network node comprising: a transceiver; and a processor coupled to the transceiver and configured to execute the methods of some of the above embodiments.
[0024] According to some embodiments of the present disclosure, a computer-readable storage medium is further provided, on which one or more computer programs are stored, wherein when the one or more computer programs are executed by one or more processors, the methods of some embodiments described above are implemented. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] Figure 1 This is the system architecture diagram for System Architecture Evolution (SAE);
[0026] Figure 2 A schematic diagram of the initial overall architecture of 5G;
[0027] Figure 3A is a schematic diagram of the method of the present invention;
[0028] Figure 3B is a flow chart of a method performed by a first network node of the present invention;
[0029] Figure 3C is a flow chart of a method performed by a second network node of the present invention;
[0030] Figure 4is a schematic diagram of a method for establishing a broadcast service of the present invention;
[0031] Figure 5 is a schematic diagram of a method for modifying broadcast services of the present invention;
[0032] Figure 6 is a schematic diagram of a method for establishing an F1 user plane of the present invention;
[0033] Figure 7 is a schematic diagram of another method for establishing an E1 user plane of the present invention;
[0034] Figure 8 It is a schematic diagram of multicast service transmission of the present invention;
[0035] Fig. 9 is a schematic diagram of another method for transmitting multicast services of the present invention;
[0036] Fig.10 is a schematic diagram of another method for transmitting multicast services of the present invention;
[0037] Fig.11 is a block diagram of a communication device according to the present invention;
[0038] Fig.12 It is a schematic diagram of the method for establishing the F1 tunnel of the present invention. DETAILED DESCRIPTION
[0039] The following description with reference to the accompanying drawings is provided to facilitate a comprehensive understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. This description includes various specific details to facilitate understanding but should be considered as exemplary only. Therefore, one of ordinary skill in the art will recognize that various changes and modifications can be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. In addition, for the sake of clarity and conciseness, descriptions of well-known functions and structures may be omitted.
[0040] The terms and expressions used in the following specification and claims are not limited to their dictionary meanings, but are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Therefore, it should be apparent to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustration purposes only and not for the purpose of limiting the present disclosure as defined in the appended claims and their equivalents.
[0041] It should be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.
[0042] The term "include" or "may include" refers to the presence of the corresponding disclosed functions, operations or components that can be used in various embodiments of the present disclosure, rather than limiting the presence of one or more additional functions, operations or features. In addition, the term "include" or "have" may be interpreted as indicating certain characteristics, numbers, steps, operations, constituent elements, components or combinations thereof, but should not be interpreted as excluding the possibility of the presence of one or more other characteristics, numbers, steps, operations, constituent elements, components or combinations thereof.
[0043] The term "or" used in various embodiments of the present disclosure includes any of the listed terms and all combinations thereof. For example, "A or B" may include A, may include B, or may include both A and B. Unless defined differently, all terms (including technical terms or scientific terms) used in the present disclosure have the same meanings understood by those skilled in the art described in the present disclosure. Common terms as defined in dictionaries are interpreted as having meanings consistent with the context in the relevant technical field, and should not be interpreted ideally or overly formally unless explicitly defined in the present disclosure.
[0044] The following discussion Figures 1 to 11 The various embodiments used to describe the principles of the present disclosure in this patent document are for illustration only and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the present disclosure can be implemented in any appropriately arranged system or device.
[0045] Figure 1 It is an exemplary system architecture 100 of System Architecture Evolution (SAE). User Equipment (UE) 101 is a terminal device used to receive data. Evolved Universal Terrestrial Radio Access Network (E-UTRAN) 102 is a radio access network, which includes a macro base station (eNodeB / NodeB) that provides a wireless network interface for the UE to access. The Mobility Management Entity (MME) 103 is responsible for managing the mobility context, session context and security information of the UE. The Serving Gateway (SGW) 104 mainly provides user plane functions, and the MME 103 and SGW 104 may be in the same physical entity. The Packet Data Network Gateway (PGW) 105 is responsible for functions such as billing and lawful interception, and may also be in the same physical entity as the SGW 104. The Policy and Charging Rules Function Entity (PCRF) 106 provides Quality of Service (QoS) policies and charging criteria. The General Packet Radio Service Support Node (SGSN) 108 is a network node device that provides routing for data transmission in the Universal Mobile Telecommunications System (UMTS). The Home Subscriber Server (HSS) 109 is the home subsystem of the UE and is responsible for protecting user information including the current location of the user equipment, the address of the service node, user security information, and the packet data context of the user equipment.
[0046] Figure 2 is an exemplary system architecture 200 according to various embodiments of the present disclosure. Other embodiments of the system architecture 200 can be used without departing from the scope of the present disclosure.
[0047] User equipment (UE) 201 is a terminal device used to receive data. The next generation radio access network (NG-RAN) 202 is a radio access network, which includes a base station (gNB or eNB connected to the 5G core network 5GC, the eNB connected to the 5GC is also called ng-gNB) that provides the UE with an access wireless network interface. The access control and mobility management function entity (AMF) 203 is responsible for managing the mobility context and security information of the UE. The user plane function entity (UPF) 204 mainly provides user plane functions. The session management function entity SMF 205 is responsible for session management. The data network (DN) 206 includes services such as operators, Internet access, and third-party services.
[0048] In order to effectively utilize air interface resources, for services where multiple users receive the same data, broadcast and multicast are used to provide service data to users. This service is called Multimedia Broadcast and Multicast Service, hereinafter referred to as MBS (Multicast and Broadcast Service).
[0049] MBS services are divided into two types. One is multicast service. UE needs to join the multicast service first. Then, when the multicast service starts, if the UE is in PMM idle mode, the network sends a paging message to let the UE enter PMM connected mode to receive the service. The other is broadcast service. UE does not need to join a group. The service start information and configuration information will be sent to the UE by broadcast. All PMM connected mode and PMM idle mode can receive data.
[0050] When MBS is a broadcast service, the base station uses broadcasting to send data to the UE. UEs in RRC idle and connected modes can receive MBS service data. When the base station is a separated architecture, the Centralized Unit-Control Plane (CU-CP) provides MBS-related information to the Distributed Unit (DU). The DU generates an MBS control message and an MBS broadcast configuration message, which are sent to the UE via a common channel, such as MBS common control information (MCCH). For multicast services, the CU-CP sends MBS-related configuration information to the UE via an RRC message. Only UEs in RRC connected mode can receive MBS service data.
[0051] Under the deployment of shared access network, the same MBS service is deployed by two (or more than two) operators respectively, and each operator allocates a different temporary terminal group identifier TMGI, also known as a session identifier, to the MBS service. In the current mechanism, the access network identifies the MBS service through TMGI, and resource allocation is for one TMGI. If the TMGI is different, the access network will allocate different point-to-multipoint resources to transmit MBS data. However, the MBS data actually transmitted is for the same MBS service, but different resources are used to transmit data. The resource utilization of the network is not high, so an enhanced method is needed to improve resource utilization. When there is a problem with resources, an enhanced configuration method is needed to enable MBS data to continue to be transmitted to ensure service continuity. The following takes the example of an access network shared by two operators to describe the enhanced method. If the access network is shared by more than two operators, a similar method can be used.
[0052] The schematic diagram of the method of the present invention is as follows Figure 3A As shown, the access network takes a separation architecture as an example, CU-CP, Centralized Unit-User Plane (CU-UP) CU-UP and DU are shared by two operators, both of which operate the same MBS service. The operators allocate different MBS session identifiers TMGI for the same MBS service. For example, operator 1 uses TMGI1, and the core network is CN1, and operator 2 uses TMGI2, and the core network is CN2.
[0053] CU-CP receives broadcast session establishment request messages from CN1 and CN2 respectively. The two messages contain different MBS session identifiers TMGI. For example, the session identifier assigned by CN1 to MBS is TMGI1, and the session identifier assigned by CN2 to MBS is TMGI2. The broadcast session establishment request message also contains the identifier of the associated MBS. The identifier of the associated MBS is information that uniquely identifies an MBS service between operators. It can be the IP address of the MBS application, or other unique identifiers. According to the same associated MBS identifier contained in the broadcast session establishment request, CU-CP can know that MBS services with different session identifiers belong to the same MBS service. For associated MBS services, in order to save access network resources and reduce repeated data transmission, CU-CP determines the number of user planes between the access network and the core network. For example, CU-CP decides to establish only one user plane, that is, only establish a user plane between CU-UP and CN1, and do not establish a user plane between CU-UP and CN2. The establishment of the user plane is as follows: Figure 4 Described in.
[0054] CU-UP monitors the user plane of the established MBS and detects that an error occurs in the user plane, such as the interruption of the tunnel for transmitting user plane data between CU-UP and the core network, or the loss of data received by CU-UP. The tunnel interruption can be learned through the current mechanism of the transport layer, and the data loss can be learned through the sequence number included in the packet header. If this situation is detected, CU-UP sends the first message of step 301 to CU-CP. The first message includes the session identifier TMGI1 of the MBS. The first message also includes indication information, indicating that an error occurs in the user plane. The indication information can be indicated by including explicit indication information in the first message, or by setting the cause to a user plane error. The message can also carry an identifier of the associated MBS, and the message can also include an MBS session identifier TMGI2 under another operator, and carry the address information of the user plane allocated by CU-UP to TMGI2. The address information of the user plane includes an IP address and a tunnel endpoint identifier TEID.
[0055] In step 302, CU-CP sends a second message to the core network CN2. The message carries the service identifier TMGI2 of the MBS under operator 2, includes the identifier of the associated MBS, includes the user plane address information allocated by CU-UP to TMGI2, and may also include the serial number of the user plane.
[0056] CN2 allocates resources within the core network, and then can send a response message to CU-CP, which can send the response message to CU-UP. After that, CU-UP can receive MBS data from the CN2 core network.
[0057] Figure 3B is a flow chart of a method executed by a first network node of the present invention.
[0058] In step 301B, the first network node receives a first message from the second network node, the first message may include first indication information indicating that an error occurs in the user plane of the first broadcast session. The first message may also include user plane address information of the second broadcast session.
[0059] At step 302B, the first network node sends a second message to the third network node, where the second message includes user plane address information of the second broadcast session.
[0060] Figure 3C is a flow chart of a method executed by a second network node of the present invention.
[0061] In step 301C, the second network node discovers an error in the user plane.
[0062] In step 302C, the second network node sends a first message to the first network node, the first message may include first indication information indicating that an error occurs in the user plane of the first broadcast session. The first message may also include user plane address information of the second broadcast session.
[0063] In various embodiments of the present disclosure, CU-CP may also be referred to as the first network node, CU-UP may also be referred to as the second network node, AMF2 of operator 2 may also be referred to as the third network node, and DU may also be referred to as the fourth network node.
[0064] Figure 4 An embodiment of establishing a user plane for broadcast services is described. The access network is a separated architecture shared by two operators. The separated access network includes CU-CP, CU-UP, and DU. The same MBS broadcast session is provided in the networks of two operators, and the broadcast session identifiers allocated by the two operators for the broadcast session are TMGI1 and TMGI2 respectively. The GPRS tunneling protocol GTP (General Packet Radio Service GPRS Tunneling Protocol) user plane tunneling protocol is used in the NG interface user plane and the F1 interface user plane.
[0065] Step 401, CU-CP receives a first broadcast session establishment request message sent by the core network access mobility management function (AMF1).
[0066] The core network belonging to operator 1 sends a first broadcast session establishment request message to CU-CP. The broadcast session establishment request message includes the NG interface identifier allocated by core network 1 to TMGI1, the MBS session identifier, such as TMGI1, the service scope of MBS, such as the identifier of a group of service areas (such as SAI), or the identifier of a group of cells (such as CGI), or the identifier of a group of routing areas (such as TAI, or TAC), and the transport layer address information of the NG user plane, the transport layer address information includes the IP address and the tunnel port identifier TEID. The message also includes information about the MBS quality flow (QoS flow) to be established, such as the identifier of the QoS flow and the QoS requirements of the QoS flow.
[0067] In order to save the equipment investment of operators, network sharing is a common deployment method. Network sharing means that the same access network equipment is used by multiple operators. MBS services can be broadcast under multiple operators. Different operators can allocate different MBS session identifiers TMGI for the same MBS service. Currently, the access network uses TMGI to identify different MBS services. Different TMGIs are considered to be different MBS services. The access network allocates different access network resources and air interface resources to transmit MBS data that is actually the same service. In order to reduce the resource consumption of wireless networks and air interfaces, if a node supports multiple operators, for the same MBS service, the access network can allocate the same network resources and air interface resources to transmit data belonging to the same MBS service received from different core networks. To achieve this purpose, the message in step 401 can also include an identifier of the associated MBS, which is an MBS unique service identifier. The unique service identifier uniquely identifies an MBS service. For the same MBS service, the MBS unique service identifier is the same in different operator networks.
[0068] Step 402: Broadcast bearer establishment process between CU-CP and CU-UP.
[0069] The process includes the CU-CP sending a broadcast bearer establishment request message to the CU-UP and the CU-UP sending a response message to the CU-CP.
[0070] CU-CP obtains the operator identifier supported by CU-UP from the E1 establishment request process, and thus learns that CU-UP is a node shared by multiple operators. After CU-CP receives the step 401 message, CU-CP sends a broadcast bearer establishment request message to CU-UP. The message includes the E1 interface identifier assigned by CU-CP for TMGI1, the MBS session identifier TMGI1, the slice identifier, the transport layer address of the MBS session in the core network 5GC, and the list of MBS unlimited bearers (MRBs) to be established. The MRB list to be established includes the MRB identifier and QoS flow information.
[0071] CU-UP sends a broadcast bearer establishment response message to CU-CP. The message includes the E1 interface identifier assigned by CU-UP to TMGI1, the MBS session identifier TMGI1, and the NG user plane transport layer address assigned by CU-UP. The message also includes a list of successfully established MRBs, which includes the MRB identifier, the identifier of the successfully established QoF flow, and the transport layer address assigned by CU-UP to the F1 user plane. The transport layer address includes the IP address and TEID of the F1 user plane. Each MRB corresponds to an F1 tunnel.
[0072] Step 403: Broadcast context establishment process between CU-CP and DU.
[0073] The process includes the CU-CP sending a broadcast context establishment request message to the DU and the DU sending a broadcast context establishment response message to the CU-CP.
[0074] CU-CP receives the broadcast bearer establishment response message sent by CU-UP, obtains the transport layer address information of the F1 user plane allocated by CU-UP to MRB, and sends a broadcast context establishment request message to DU. The message includes the F1 interface identifier allocated by CU-CP for TMGI1, the MBS session identifier TMGI1, the service scope of MBS, such as the identifier of a group of service areas (such as SAI), or the identifier of a group of cells (such as CGI), or the identifier of a group of routing areas (such as TAI, or TAC), and the message includes MBS CU to DU RRC information. MBS CU to DU RRC information includes the list of cells broadcast by MBS and the list of neighboring cells broadcasting the MBS service. MBS CU to DU RRC information also includes MRB PDCP configuration. The broadcast service context establishment request message also includes the information of the MBS radio bearer to be established, such as the identifier of the MRB, the quality requirements of the MRB, the identifier of the QoS flow mapped to this MRB, the QoS requirements of the QoS flow, and the transport layer address of the broadcast bearer in CU-UP.
[0075] DU saves MBS context information, allocates resources according to the configuration, and sends a broadcast context establishment response message to CU-CP. The response message contains the F1 interface identifier assigned by DU to TMGI1, the MBS session identifier TMGI1, the successfully established MRB identifier, and the transport layer address information of the F1 user plane assigned by DU to the MRB of TMGI1.
[0076] Step 404: broadcast bearer modification process between CU-CP and CU-UP.
[0077] The process includes the CU-CP sending a broadcast bearer modification request message to the CU-UP and the CU-UP sending a broadcast bearer modification response message to the CU-CP.
[0078] CU-CP obtains the transport layer address of the F1 user plane allocated by DU to MRB from DU. CU-CP sends a broadcast bearer modification request to CU-UP. The message includes the E1 interface identifier allocated by CU-CP to TMGI1, the MBS session identifier TMGI1, the list of MRBs to be established or modified, the MRB list includes the MRB identifier, and the transport layer address allocated by DU to the F1 user plane.
[0079] CU-UP saves the received information and sends a broadcast bearer modification response message to CU-CP. The message includes the E1 interface identifier allocated by CU-UP for TMGI1, the MBS session identifier TMGI1, and the list of successfully established MRBs.
[0080] Step 405: CU-CP sends a broadcast session establishment response message to AMF1.
[0081] The message includes the NG interface identifier allocated by CU-CP to TMGI1, the MBS session identifier TMGI1, and the transport layer address of the NG user plane allocated by CU-UP to TMGI1.
[0082] Step 406, CU-CP receives a second broadcast session establishment request message from AMF2 of operator 2. The second broadcast message includes the NG interface identifier assigned by core network 2 to TMGI2, and the MBS session identifier TMGI2. The message may also include the identifier of the associated MBS. If the identifiers of the associated MBS included in the first broadcast session establishment request message and the second broadcast session establishment request message are the same, CU-CP can know that the MBSs corresponding to the two messages are the same MBS service. Since the same service is transmitted, the access network NG-RAN is shared, and CU-CP can decide whether to establish a user plane for transmitting MBS services between the access network and the core network 2. For efficient use of resources, CU-CP can decide to establish only the user plane between the access network and the core network 1, or decide to establish the user planes between the access network and the core network 1, and the access network and the core network 2, respectively.
[0083] If the CU-CP decides to establish only the user plane between the access network and the core network 1, and not to establish the user plane between the access network and the core network 2, the CU-CP may perform one of the following operations:
[0084] In one method, CU-CP saves the context information related to TMGI2, which includes the MBS session identifier TMGI2 received from the core network, the service scope of TMGI2, the identifier of the associated MBS, the slice identifier, the transport layer address of the MBS session in the core network 5GC, the information of the QoS flow of the MBS, the frequency information, etc. CU-CP does not send any message to CU-UP. CU-UP does not know the relevant information of TMGI2, so CU-UP cannot establish a user plane for transmitting MBS with the core network 2. When CU-CP uses the present invention, Figures 4 to 7According to the method shown, it is known that the MBS data content transmitted by TMGI1 and TMGI2 is the same, the RAN is shared, and an NG-U tunnel has been established between the CU-UP and the TMGI1 core network. However, there is an error in the established NG-U user plane. The CU-CP will send an MBS bearer establishment request for TMGI2 to the CU-UP. The CU-UP allocates the TNL address of the NG-U to TMGI2 and sends it to the CU-CP through a response message. Then, the CU-CP can send a message to the core network control node of TMGI2, such as the access mobile function entity AMF or the session management entity SMF or the MBS session management entity MBS-SMF. The message includes the MBS service identifier TMGI2 and the TNL address allocated by the NG-RAN, that is, the TNL address of the NG-U allocated by the CU-UP to the TMGI2. The message may also include the GTP-SN, which is sent by the CU-UP when indicating a user plane error. After receiving the message, the core network of TMGI2 can establish an NG-U tunnel between the core network user plane (UPF or MBS UPF) and CU-UP, and the user plane starts to send MBS data to CU-UP. If the message contains GTP-SN, the core network user plane starts sending from the data packet indicated by the GTP-SN. Because the MBS data of TMGI2 is actually the same as the MBS data content of TMGI1, when there is a problem with the TMGI1 user plane, data can be sent through the user plane of TMGI2 to ensure data continuity. Through the GTP-SN, the user plane of TMGI2 can be notified of which data packet to start sending, so that data transmission is more accurate, and the interruption between data transmission will not be reduced due to less data transmission, nor will the repeated transmission of data cause repeated transmission of data.
[0085] In another method, CU-CP saves the context information related to TMGI2, and CU-CP sends the MBS bearer modification request message of step 407 to CU-UP. The message includes the E1 interface identifier assigned by CU-CP to TMGI1, the MBS session identifier TMGI1, and the identifier of the associated MBS. The message also includes the MBS session identifier TMGI2, the transport layer address of the MBS session in the core network 2, and the indication information of not establishing the user plane. After receiving the indication information, CU-UP does not allocate the transport layer address of the NG-U interface to TMGI2, so that the user plane for transmitting MBS data between CU-UP and the core network 2 is not established. By associating the identifier of the MBS, CU-UP can know that the MBS services corresponding to TMGI1 and TMGI2 are the same, and CU-UP saves the context information related to TMGI2. The message can also include a list of MRBs to be established or modified, and the MRB list includes an MRB identifier. The MRB list can be the same as the MRB list included in step 402, that is, the MRB configurations of TMGI1 and TMGI2 are the same. CU-UP allocates the transport layer address of the F1 user plane to the MRB of TMGI2. CU-UP can reuse the transport layer address of the F1 user plane allocated to the MRB of TMGI1 in step 402, that is, the data of TMGI1 and TMGI2 are sent to the DU through the same F1 tunnel.
[0086] In another method, CU-CP saves the context information related to TMGI2, and CU-CP sends the MBS bearer request message of step 407 to CU-UP. The message includes the E1 interface identifier assigned by CU-CP to TMGI2, the MBS session identifier TMGI2, the identifier of the associated MBS, the slice identifier, the transport layer address of the MBS session in the core network 2, the list of MRBs to be established, and the MRB list to be established includes the MRB identifier and the information of the QoS flow. The message also includes the indication information of not establishing the user plane. After receiving the indication information, CU-UP does not allocate the transport layer address of the NG-U interface, so that the user plane for transmitting MBS data between CU-UP and the core network 2 is not established. By associating the MBS identifier, CU-UP can know that the MBS services corresponding to TMGI1 and TMGI2 are the same, and CU-UP saves the context information related to TMGI2. The MRB list can be different from the MRB list included in step 402, that is, the MRB configurations of TMGI1 and TMGI2 are different. CU-UP allocates the transport layer address of the F1 user plane to the MRB of TMGI2. CU-UP allocates different F1 user plane transport layer addresses to the MRB of TMGI2, that is, the data of TMGI1 and TMGI2 are sent to the DU through different F1 tunnels.
[0087] In the fourth method, CU-CP saves the context information related to TMGI2, and CU-CP sends the MBS bearer request message of step 407 to CU-UP. The message includes the E1 interface identifier assigned by CU-CP to TMGI2, the MBS session identifier TMGI2, the identifier of the associated MBS, the slice identifier, the transport layer address of the MBS session in the core network 2, the list of MRBs to be established, and the MRB list to be established includes the MRB identifier and the information of the QoS flow. The message also includes the third indication information, for example, the third indication information is the indication information that NG-U is not established. After receiving the indication information, CU-UP allocates the transport layer address of the NG-U interface, and CU-UP knows that the NG-U tunnel between CU-UP and the core network user plane is not established. Through the identifier of the associated MBS contained in the message, CU-UP can know that the MBS services corresponding to TMGI1 and TMGI2 are the same, and CU-UP saves the context information related to TMGI2. The MRB list can be the same as the MRB list contained in step 402, that is, the MRB configuration of TMGI1 and TMGI2 is the same. When the network is shared, and different TMGIs transmitted by multiple operators transmit the same MBS data, only one shared F1-U tunnel can be established between CU-UP and DU. Therefore, the third indication information may also indicate that CU-UP does not need to allocate CU-UP and F1-U tunnel information for TMGI2. On the NG interface, in this example, the MBS service identifier provided by operator 1 is TMGI, and the MBS service identifier provided by operator 2 is TMGI2. The MBS data content transmitted by TMGI1 and TMGI2 is the same. NG-RAN is shared by operator 1 and operator 2. Under this method, NG-RAN decides to establish an NG-U tunnel with the core network of operator 1, and the CU-CP node of NG-RAN indicates one or more of the following information to CU-UP through the first indication information:
[0088] - Instruct CU-UP to allocate the transport layer address (Transport Network Layer address) of the NG-U tunnel to the TMGI2, the TNL address includes an IP address and a GTP-TEID, and the third indication information also indicates that the NG-U tunnel between CU-UP and the core network of the TMGI2 has not been established, or will not be established, or has not been established temporarily. According to the third indication information, CU-UP knows that it will not receive the MBS data sent by the core network from the NG-U tunnel temporarily. After receiving the third indication information, CU-UP allocates the TNL address of the NG-U tunnel, and this NG-U tunnel is used to receive MBS data from the core network. The address is sent to CU-CP through the bearer establishment response message in step 408; CU-UP knows through the third indication information that CU-CP has not established the user plane between CU-UP and the TMGI2 core network, NG-U has not been actually established successfully, CU-UP will not receive the MBS data sent by the core network from the NG-U tunnel, and CU-UP will not judge that the failure to receive data on NG-U is an error.
[0089] -Indicates that CU-UP has not established NG-U. The third indication information indicates to CU-UP that the NG-U tunnel between CU-CU and the core network of TMGI2 has not been established, or will not be established, or has not been established temporarily. After receiving the third indication information, CU-UP will still allocate the TNL address of the NG-U tunnel to TMGI2. This NG-U tunnel is used to receive MBS data from the core network, and the address is included in the bearer establishment response message sent to CU-CP through step 408; CU-UP knows through the third indication information that CU-CP has not established the user plane between CU-UP and the TMGI2 core network, and NG-U has not been actually established successfully. CU-UP will not receive the MBS data sent by the core network from the NG-U tunnel, and CU-UP will not judge that the failure to receive data on NG-U is an error.
[0090] - Instruct CU-UP to allocate the TNL address of the F1-U tunnel to the MRB of the TMGI2.
[0091] The MBS bearer request message includes the configuration information of the MRB corresponding to TMGI2.
[0092] For resource sharing, the MRB configuration information corresponding to TMGI2 may be the same as the MRB configuration information corresponding to TMGI. The third indication information indicates that CU-UP needs to allocate the TNL address of the F1-U tunnel to the MRB of TMGI2. For resource sharing, the TNL address of the F1-U tunnel allocated by CU-UP to the MRB of TMGI2 may be the same as the TNL address of the F1-U tunnel allocated to the MRB of TMGI1 in step 402.
[0093] After receiving the response message of step 408, the CU-CP saves the address information. When the CU-CP decides to establish an NG-U tunnel with the TMGI2 core network, for example, when the CU-CP uses the present invention Figures 4 to 7 According to the method shown, it is known that the MBS data content transmitted by TMGI1 and TMGI2 is the same, RAN is shared, an NG-U tunnel has been established between CU-UP and the TMGI1 core network, and the established NG-U user plane has an error. CU-CP has saved the TNL address of the NG-U tunnel assigned by CU-UP to TMGI2. Then CU-CP can directly send a message to the core network control node of TMGI2, such as the access mobile function entity AMF or the session management entity SMF or the MBS session management entity MBS-SMF. The message includes the MBS service identifier TMGI2, the TNL address assigned by NG-RAN, that is, the TNL address of NG-U assigned by CU-UP to TMGI2. The message can also include GTP-SN, which is sent by CU-UP when indicating a user plane error. After receiving the message, the core network of TMGI2 can establish an NG-U tunnel between the core network user plane (UPF or MBS UPF) and CU-UP, and the user plane starts to send MBS data to CU-UP. If the message includes GTP-SN, the core network user plane starts sending from the data packet indicated by the GTP-SN. Because the MBS data of TMGI2 is actually the same as the MBS data content of TMGI1, when there is a problem with the TMGI1 user plane, data can be sent through the TMGI2 user plane to ensure data continuity. Through the GTP-SN, the TMGI2 user plane can be notified of which data packet to start sending, so that data is sent more accurately, and the interruption between data transmissions will not be reduced due to less data transmission, and the repeated transmission of data will not cause repeated transmission of data.
[0094] The above-mentioned CU-CP node sends the first indication information to indicate CU-UP, which may also occur in a later step, such as in the broadcast bearer modification process shown in step 411, and sends the first indication information to CU-UP through a broadcast bearer modification request message. This depends on when CU-CP can make a decision not to establish an NG-U tunnel. If the decision is made earlier, the first indication message can be sent to CU-UP in the bearer establishment request message. If the decision is made later, the first indication message can be sent to CU-UP in a subsequent broadcast bearer modification request.
[0095] If the CU-CP decides to establish a user plane between the access network and the core network 2 , the CU-CP may repeat the process of step 402 .
[0096] Step 408: CU-UP sends a broadcast bearer modification response or establishment response message to CU-CP.
[0097] Depending on the method in step 407, CU-UP can send a broadcast bearer modification response message to CU-CP, the message including the E1 interface identifier assigned by CU-UP to TMGI1, the MBS session identifier TMGI1, the MBS session identifier TMGI2, the list of successfully established MRBs, the list including the identifier of the MRB, and the transport layer address assigned by CU to the F1 user plane.
[0098] Depending on the method in step 407, CU-UP can send a broadcast bearer establishment response message to CU-CP, which includes the E1 interface identifier assigned by CU-UP to TMGI2, the MBS session identifier TMGI2, the list of successfully established MRBs, the list includes the identifier of the MRB, and the transport layer address assigned by CU-UP to the F1 user plane.
[0099] Step 409: CU-CP sends a broadcast service context modification or establishment request message to DU.
[0100] In one method, CU-CP sends a broadcast context modification request message to DU, the message includes the F1 interface identifier assigned by CU-CP for TMGI1, the MBS session identifier TMGI1, the identifier of the associated MBS (MBS associated ID), the service scope of the MBS, the MBS session identifier TMGI2, and the MBS CU to DU RRC information. The MBS CU to DU RRC information includes the cell list of TMGI2 and the list of adjacent cells broadcasting the MBS service. The MBS CU to DU RRC information also includes the MRB PDCP configuration. The broadcast service context establishment request message also includes information about the MBS radio bearer to be established, such as the identifier of the MRB, the quality requirements of the MRB, the identifier of the QoS flow mapped to this MRB, and the QoS requirements of the QoS flow. The broadcast bearer is at the transport layer address of CU-UP. The message can include multiple MBS CU to DU RRC information, corresponding to TMGI1 and TMGI2 respectively. For TMGI1 and TMGI2, the same MRB can be configured and the same F1 tunnel can be used.
[0101] In another method, CU-CP sends a broadcast context establishment request message to DU, the message includes the F1 interface identifier allocated by CU-CP for TMGI2, the MBS session identifier TMGI2, the identifier of the associated MBS, the service scope of the MBS, such as the identifier of a group of service areas (such as SAI), or the identifier of a group of cells (such as CGI), or the identifier of a group of routing areas (such as TAI, or TAC), and the message includes MBS CU to DU RRC information. The MBS CU to DU RRC information includes the list of cells broadcast by the MBS and the list of neighboring cells broadcasting the MBS service. The MBS CU to DU RRC information also includes the MRB PDCP configuration. The broadcast service context establishment request message also includes information about the MBS radio bearer to be established, such as the identifier of the MRB, the quality requirements of the MRB, the identifier of the QoS flow mapped to this MRB, and the QoS requirements of the QoS flow. The broadcast bearer is at the transport layer address of the CU-UP.
[0102] Step 410: DU sends a response message to CU-CP.
[0103] In one method, the DU sends a broadcast context modification response message to the CU-CP. The response message includes the F1 interface identifier assigned by the DU to TMGI1, the MBS session identifier TMGI1, the identifier of the associated MBS, the MBS session identifier TMGI2, the successfully established MRB identifier, and the transport layer address information of the F1 user plane assigned by the DU to TMGI1 and TMGI2. For TMGI1 and TMGI2, the same MRB can be configured and the same F1 tunnel can be used.
[0104] In another method, DU sends a broadcast context establishment response message to CU-CP. The response message contains the F1 interface identifier assigned by DU to TMGI2, the MBS session identifier TMGI2, the identifier of the associated MBS, the MRB identifier of the successful establishment, and the transport layer address information of the F1 user plane assigned by DU to TMGI2. For TMGI1 and TMGI2, the same or different MRBs can be configured and different F1 tunnels can be used.
[0105] Step 411, broadcast bearer modification process between CU-CP and CU-UP.
[0106] The process includes the CU-CP sending a broadcast bearer modification request message to the CU-UP and the CU-UP sending a broadcast bearer modification response message to the CU-CP.
[0107] CU-CP obtains the transport layer address assigned by DU for the F1 user plane from DU. CU-CP sends a broadcast bearer modification request to CU-UP. The message includes the E1 interface identifier assigned by CU-CP for TMGI2, the MBS session identifier TMGI2, the identifier of the associated MBS, the list of MRBs to be established or modified, the MRB list includes the MRB identifier, and the transport layer address assigned by DU for the F1 user plane.
[0108] Or the broadcast bearer modification request message includes the E1 interface identifier allocated by CU-CP for TMGI1, the MBS session identifier TMGI1, the identifier of the associated MBS, the MBS session identifier TMGI2, the list of MRBs to be established or modified, the MRB list includes the MRB identifier, and the transport layer address allocated by DU for the F1 user plane.
[0109] CU-UP saves the received information and sends a broadcast bearer modification response message to CU-CP. The message includes the E1 interface identifier assigned by CU-UP to TMGI2, the MBS session identifier TMGI2, the identifier of the associated MBS, and the list of successfully established MRBs.
[0110] Or the broadcast bearer modification response message includes the E1 interface identifier allocated by CU-UP to TMGI1, the MBS session identifier TMGI1, the identifier of the associated MBS, the MBS session identifier TMGI2, and a list of successfully established MRBs.
[0111] Step 412: CU-CP sends a broadcast session establishment response message or a service failure response message to the core network CN2.
[0112] The message includes the NG interface identifier assigned by CU-CP to TMGI2, the MBS session identifier TMGI2, the identifier of the associated MBS, and indication information that the NG user plane is not established. The indication information indicates that the NG interface user plane is not established, or indicates that the NG interface user plane is not established due to access network sharing.
[0113] Step 413, core network process: AMF notifies the MBS session management function MB-SMF and / or the user plane UPF that the NG interface user plane is not established, or notifies that the NG interface user plane is not established due to access network sharing.
[0114] Figure 5An embodiment of establishing a user plane for a broadcast service is described. The access network is a separated architecture shared by two operators. The separated access network includes a central unit control plane (CU-CP), a central unit user plane (CU-UP), and a distribution unit (DU). The same MBS broadcast session is provided in the networks of two operators, and the broadcast session identifiers assigned by the two operators to the broadcast session are TMGI1 and TMGI2, respectively. The GTP user plane tunneling protocol is used in the NG interface user plane and the F1 interface user plane. CU-CP has established a user plane for MBS between CU-UP and CN1, but has not established a user plane for MBS between CU-UP and CN2. CN1 transmits MBS data identified as TMGI1, and CN2 transmits MBS data identified as TMGI2. TMGI1 and TMGI2 are shared MBS services, and the transmitted data is actually the same.
[0115] Step 501: CU-UP sends an MBS modification request message to CU-CP.
[0116] CU-UP discovers that there are some errors in the NG interface user plane corresponding to TMGI1, and discovers the user plane errors through the GTP-U protocol itself, or discovers the errors through the received GTP-U sequence number. CU-UP sends a message to CU-CP, which includes the E1 interface identifier assigned by CU-UP to TMGI1, the MBS session identifier TMGI1, the identifier of the associated MBS, and the indication information of the NG user plane error, which indicates that an error has occurred in the user plane data reception. The message may also include the MBS session identifier TMGI2, and the NG interface user plane transport layer address assigned by CU-UP to TMGI2. The message may also include the MRB list of TMGI2, the MRB list includes the MRB identifier, and the F1 user plane transport layer address assigned by CU-UP to the MRB.
[0117] Or CU-UP sends a message to CU-CP, which includes the E1 interface identifier assigned by CU-UP to TMGI2, the MBS session identifier TMGI2, the identifier of the associated MBS, and the NG interface user plane transport layer address assigned by CU-UP to TMGI2. The message also includes indication information indicating that an error has occurred in the NG user plane, and the indication information indicates that an error has occurred in the user plane data reception of the NG interface of TMGI1. The message can also include the MRB list of TMGI2, the MRB list includes the MRB identifier, and the F1 user plane transport layer address assigned by CU-UP to the MRB.
[0118] The message in step 501 also includes a GTP-U sequence number, which indicates the highest GTP-U sequence number corresponding to the data packet received by the CU-UP, or indicates the GTP-U sequence number corresponding to the next data packet that the CU-UP hopes to receive. The GTP-U sequence number may also be other sequence numbers, such as a PDCP sequence number.
[0119] Step 502: CU-CP sends a broadcast modification request message to the core network AMF2. The message name may be other message names.
[0120] The message includes the E1 interface identifier assigned by CU-UP to TMGI2, the MBS session identifier TMGI2, the identifier of the associated MBS, and the NG interface user plane transport layer address assigned by CU-UP to TMGI2. The message also includes the GTP-U sequence number, which indicates the highest GTP-U sequence number corresponding to the data packet received by CU-UP, or indicates the GTP-U sequence number corresponding to the next data packet that CU-UP hopes to receive.
[0121] Step 503: AMF2 sends a message to the MBS session management function MB-SMF and / or the user plane UPF to notify the user plane transport layer address of the NG interface allocated by CU-UP.
[0122] Step 504: CU-CP sends a message to DU, notifying DU to receive data from the F1 tunnel corresponding to TMGI2. The message may be a broadcast context modification request or establishment request, or other message names.
[0123] The message includes the F1 interface identifier assigned by CU-CP to TMGI1, the MBS session identifier TMGI1, the identifier of the associated MBS, and the MBS session identifier TMGI2. The message may also include the MRB list of TMGI2, which includes the MRB identifier and the transport layer address of the F1 user plane assigned by CU-UP to the MRB. The message also includes indication information indicating that data is received from the F1 tunnel corresponding to TMGI2.
[0124] Or the message includes the NG interface identifier assigned by CU-CP to TMGI2, the MBS session identifier TMGI2, the identifier of the associated MBS, and the MRB list of TMGI2, the MRB list includes the MRB identifier, and the transport layer address of the F1 user plane assigned by CU-UP to the MRB. The message also includes indication information, indicating that data is received from the F1 tunnel corresponding to TMGI2.
[0125] Step 505: DU sends a response message to CU-CP.
[0126] The response message includes the F1 interface identifier assigned by DU to TMGI1, the MBS session identifier TMGI1, the identifier of the associated MBS, and the MBS session identifier TMGI2. The message may also include the MRB list of TMGI2, the MRB list includes the MRB identifier, and the transport layer address of the F1 user plane assigned by DU to MRB.
[0127] Alternatively, the response message includes the F1 interface identifier allocated by the DU to TMGI2, the MBS session identifier TMGI2, the identifier of the associated MBS, the MRB list of TMGI2, the MRB list includes the MRB identifier, and the transport layer address of the F1 user plane allocated by the DU to the MRB.
[0128] Step 506: CU-CP sends a message to CU-UP. The message may be a broadcast bearer modification request message, or other message names, such as a broadcast bearer modification confirmation message. This step message may be sent after step 502 and is a response message of step 502.
[0129] The message includes the E1 interface identifier assigned by CU-CP to TMGI1, the MBS session identifier TMGI1, the identifier of the associated MBS, and the MBS session identifier TMGI2. The message may also include the MRB list of TMGI2, which includes the MRB identifier and the NG interface user plane transport layer address assigned by DU to TMGI2. The MBS session identifier TMGI2 is a session associated with TMGI1, that is, TMGI2 and TMGI1 transmit the same MBS service data. It also includes indication information, indicating that the data will be transmitted from CN2 corresponding to TMGI2 to CU-UP.
[0130] Or the message includes the E1 interface identifier assigned by CU-CP to TMGI2, the MBS session identifier TMGI2, and the identifier of the associated MBS. The message may also include the MRB list of TMGI2, the MRB list includes the MRB identifier, and the NG interface user plane transport layer address assigned by DU to TMGI2. The MBS session identifier TMGI1 is a session associated with TMGI2, that is, TMGI1 and TMGI2 transmit the same MBS service data. It also includes indication information, indicating that the data will be transmitted from CN2 corresponding to TMGI2 to CU-UP.
[0131] The specific configuration in the MRB list of TMGI2 may be the same as the specific configuration in the MRB list previously allocated to TMGI1.
[0132] After receiving the message in step 506, the information is saved, and PDCP and MRB are configured according to the information. After receiving the confirmation message, CU-UP knows that it will receive MBS data from CN2.
[0133] Step 507: CU-CP sends an MBS release request message to AMF.
[0134] The message includes the E1 interface identifier allocated by CU-CP for TMGI1, the MBS session identifier TMGI1, and the release reason is due to access network sharing or an error in the NG user plane.
[0135] Step 508, AMF1 sends a message to MB-SMF1 or UPF1 to notify TMGI1 of the user plane error corresponding to the TMGI1, and UPF1 can stop sending data to CU-UP.
[0136] Figure 6 The process of establishing the F1 tunnel is described. TMGI1 and TMGI2 are for the same MBS service. For the same service, an F1 tunnel for the MRB of TMGI1 and an F1 tunnel for the MRB of TMGI2 can be established on F1 respectively, and the data of TMGI1 and TMGI2 can be transmitted through different tunnels. The MRB configurations of the two may be the same or different, and the DU only broadcasts the configuration information of one MRB on the air interface. In this embodiment, the user plane on F1 of TMGI1 and TMGI2 is to be established on F1, but there is no MBS data to be transmitted on the F1 user plane of TMGI2. Alternatively, only one F1 tunnel is established on F1 to transmit the data of the MRB for TMGI1 and TMGI2.
[0137] Step 601: CU-CP sends a broadcast context establishment request message to DU.
[0138] The message contains the F1 interface identifier assigned by CU-CP to TMGI1, the MBS session identifier TMGI1, the identifier of the associated MBS, the service scope of the MBS, and the MBS CU to DU RRC information. The MBS CU to DU RRC information contains the cell list of TMGI1 and the list of adjacent cells broadcasting the MBS service. The MBS CU to DU RRC information also contains the MRB PDCP configuration. The broadcast service context establishment request message also contains the information of the MBS radio bearer to be established, such as the identifier of the MRB, the quality requirements of the MRB, the identifier of the QoS flow mapped to this MRB, and the QoS requirements of the QoS flow. The broadcast bearer is at the transport layer address of the CU-UP.
[0139] If CU-CP also receives a broadcast session establishment request message of TMGI2 sent by CN2 before sending the message of step 601, CU-CP can send the information of TMGI1 and TMGI2 to DU through one message. The message can also include MBS session identifier TMGI2, the service scope of MBS corresponding to TMGI2, and MBS CU to DU RRC information related to TMGI2. At this time, the same tunnel is established for TMGI1 and TMGI2 to transmit data.
[0140] If TMGI1 and TMGI2 are sent through different CU-CPs, that is, CU-CP is not shared by TMGI1 and TMGI2. CU-CP sends broadcast context request messages to DUs respectively. Since different broadcast context request messages contain the same associated MBS identifier, DU can know that the different broadcast context request messages, the transmitted services are associated, and the actually transmitted service data is the same.
[0141] Step 602: DU sends a broadcast context establishment response message to CU-CP.
[0142] The message includes the F1 interface identifier allocated by the DU to TMGI1, the MBS session identifier TMGI1, the identifier of the associated MBS, the identifier of the successfully established MRB, and the transport layer address information of the F1 user plane allocated by the DU to TMGI1.
[0143] If CU-CP is not shared by TMGI1 and TMGI2, DU receives broadcast session establishment requests from TMGI1 and TMGI2 respectively. Through the same MBS association identifier contained in the session establishment request message, DU knows that TMGI1 and TMGI2 transmit the same MBS data. Then DU can decide to adopt a resource optimization method, such as not establishing the F1 user plane for TMGI2. DU sends broadcast context establishment response messages to CU-CP1 and CU-CP2 respectively.
[0144] The relevant information of TMGI2 and TMGI1 is sent through different F1 control signaling, and the CU-CP is different. Therefore, different F1 control signaling contains different information such as MRB identifier, MRB PDCP configuration, etc. The DU selects an MRB identifier and MRB PDCP configuration for use in the broadcast of the air interface. For example, if the MRB identifier and MRB PDCP configuration corresponding to TMGI 1 are selected, the DU sends a broadcast context establishment response message to CU-CP1, carrying the identifier of the successfully established MRB.
[0145] When the DU sends a response message to the request message sent by the non-selected service, that is, when the DU sends a broadcast context establishment response message to CU-CP2, the response message may carry the MBS session identifier selected by the DU (TMGI1 in this embodiment), the MRB identifier selected by the DU, the MRB PDCP configuration selected by the DU, and / or carry indication information that the F1 user plane is not established.
[0146] When CU-CP2 receives a response message carrying the MBS session identifier selected by the DU, or the MRB identifier, or the PDCP configuration selected by the DU, and / or carrying indication information that the F1 user plane has not been established, CU-CP2 knows that the DU is shared, the DU has selected another MBS session, and the F1 user plane has not been established. The PDCP configuration selected by the DU is saved, and the next time the MBS wireless data bearer of TMGI2 is configured, the PDCP configuration selected by the DU can be used to ensure the continuity of air interface data transmission. CU-CP2 sends an E1 message to the CU-UP (CU-UP2) controlled by CU-CP2. The message can be an MBS bearer context establishment request or an MBS bearer context modification request. The message contains indication information indicating that the DU has not established the F1 user plane.
[0147] Afterwards, if the DU needs to establish a user plane with CU-UP2, the DU sends an MBS service modification required message to CU-CP2. The message includes indication information, indicating that there is an error in the current F1 user plane, or indicating that the F1 user plane needs to be established with CU-CP2 or CU-UP2. The message also includes the downlink receiving address assigned by the DU to TMGI2, and the receiving address includes the IP address of the DU and the tunnel identifier TEID assigned by the DU. The message may also include the MBS service identifier TMGI2, the F1 interface identifier assigned by the DU to TMGI2, the PDCP configuration and / or the highest PDCP sequence number that has been successfully transmitted, or the PDCP sequence number corresponding to the next data packet to be transmitted. The PDCP configuration is the PDCP configuration recommended by the DU for CU-CP2, which can be the same as the currently used PDCP configuration. This can reduce the interruption and loss of data caused by different PDCP configurations in the new tunnel of the DU.
[0148] Upon receiving the MBS service modification required message, CU-CP2 can send an MBS bearer context establishment request or an MBS bearer context modification request to CU-UP2, carrying the downlink receiving address assigned by DU to TMGI2, PDCP configuration information, the highest PDCP sequence number that has been successfully transmitted, or the PDCP sequence number corresponding to the next data packet to be transmitted to CU-UP2. After CU-UP2 receives the message, CU-UP2 uses the PDCP configuration information to send data to the downlink receiving address assigned by the DU according to the PDCP sequence number.
[0149] Step 603: CU-CP sends another broadcast context establishment or modification request message to DU.
[0150] The message includes the F1 interface identifier assigned by CU-CP to TMGI2, the MBS session identifier TMGI2, the identifier of the associated MBS, the service scope of the MBS, and the MBS CU to DU RRC information. The MBS CU to DU RRC information includes the cell list of TMGI2 and the list of adjacent cells broadcasting the MBS service. The MBS CU to DU RRC information also includes the MRB PDCP configuration. The broadcast context establishment request message also includes information about the MBS radio bearer to be established, such as the identifier of the MRB, the quality requirements of the MRB, the identifier of the QoS flow mapped to this MRB, and the QoS requirements of the QoS flow. The transport layer address of the broadcast bearer is in CU-UP. The message also includes indication information indicating whether the F1 user plane has MBS data to send. In this embodiment, the indication information is set to no data to be sent.
[0151] If CU-CP receives a broadcast session establishment request from TMGI2, and knows that TMGI1 and TMGI2 transmit the same MBS data through the same MBS association identifier contained in the session establishment request message, CU-CP can decide not to establish a user plane with the core network for TMGI2. CU-CP also needs to decide whether to establish a user plane for the F1 interface between TMGI2 and the DU.
[0152] If you want to establish: Under one method, the relevant information of TMGI2 and TMGI1 is sent through different F1 control signaling, and CU-CP sends a broadcast context establishment request message to DU. The message contains the F1 interface identifier assigned by CU-CP to TMGI2, the MBS session identifier TMGI2, the identifier of the associated MBS, the service scope of the MBS, and the message also contains MBS CU to DU RRC information. The MBS CU to DU RRC information contains the cell list of TMGI2 and the list of adjacent cells broadcasting the MBS service. The MBS CUto DU RRC information also contains the MRB PDCP configuration. The broadcast service context establishment request message also contains information about the MBS radio bearer to be established, such as the identifier of the MRB, the quality requirements of the MRB, the identifier of the QoS flow mapped to this MRB, and the QoS requirements of the QoS flow. The broadcast bearer is at the transport layer address of the CU-UP. DU sends a response message to CU-CP, which includes the F1 interface identifier assigned by DU to TMGI2, the MBS session identifier TMGI2, the successfully established MRB identifier, and the transport layer address information of the F1 user plane assigned by DU to TMGI2. Among them, the F1 user plane transport layer address assigned by DU to TMGI2 can be the same as or different from the F1 user plane transport layer address assigned by DU to TMGI1. If the same, the F1 user plane of TMGI2 and the F1 user plane of TMGI1 use the same tunnel. If different, the F1 user plane of TMGI2 and the F1 user plane of TMGI1 use different tunnels.
[0153] In another method, the relevant information of TMGI2 and TMGI1 is sent through the same F1 control signaling, and the CU-CP sends a broadcast context modification request message to the DU. The message includes the F1 interface identifier assigned by the CU-CP to TMGI1, the MBS session identifier TMGI1, the identifier of the associated MBS, the MBS session identifier TMGI2, and the message also includes MBS CU to DU RRC information. The MBS CU toDU RRC information includes the cell list of TMGI2 and the list of adjacent cells broadcasting the MBS service. The MBS CU to DU RRC information also includes the MRB PDCP configuration. The message can include multiple CU to DU RRC information, including TMGI1 information and TMGI2 information respectively. The DU sends a response message to the CU-CP, and the message includes the F1 interface identifier assigned by the DU to TMGI1 and the MBS session identifier TMGI1.
[0154] If you do not want to establish: Under one method, the relevant information of TMGI2 and TMGI1 is sent through different F1 control signaling. CU-CP decides not to establish the F1 user plane of TMGI2 temporarily, but needs to send the information of TMGI2 to DU, so CU-CP sends a broadcast context establishment request message to DU. The message contains the F1 interface identifier allocated by CU-CP for TMGI2, MBS session identifier TMGI2, and the identifier of the associated MBS. The message also contains MBS CU to DU RRC information, MBS session identifier TMGI1 associated with TMGI2, and indication information that DU does not need to allocate F1 tunnel. DU sends a response message to CU-CP, and the message contains the F1 interface identifier allocated by DU for TMGI2 and MBS session identifier TMGI2.
[0155] In another method, the relevant information of TMGI2 and TMGI1 is sent through the same F1 control signaling. CU-CP decides not to establish the F1 user plane of TMGI2 temporarily, but needs to send the information of TMGI2 to DU, so CU-CP sends a broadcast context modification request message to DU. The message includes the F1 interface identifier allocated by CU-CP for TMGI1, MBS session identifier TMGI1, the identifier of the associated MBS, MBS session identifier TMGI2, and the message also includes MBS CU to DU RRC information. The MBS CU to DURRC information includes the cell list of TMGI2 and the list of adjacent cells broadcasting the MBS service, and includes indication information that DU does not need to allocate F1 tunnel for TMGI2. DU sends a response message to CU-CP, and the message includes the F1 interface identifier allocated by DU for TMGI1 and MBS session identifier TMGI1.
[0156] Step 604: The DU sends a broadcast context establishment response or modification response message to the CU-CP.
[0157] The message may include the F1 interface identifier assigned by the DU to TMGI2, the F1 interface identifier assigned by the DU to TMGI1, the MBS session identifier TMGI2, the MBS session identifier TMGI1, the identifier of the associated MBS, the MRB identifier of the successfully established, the transport layer address information of the F1 user plane assigned by the DU to TMGI2, and the transport layer address information of the F1 user plane assigned by the DU to TMGI1. If in step 601 and step 603, the CU-CP that sends the message in step 601 and the CU-CP that sends the message in step 603 are the same entity, the same entity can allocate the same MRB and MRB configuration information to TMGI1 and TMGI2.
[0158] If in step 601 and step 603, the CU-CP that sends the message in step 601 and the CU-CP that sends the message in step 603 are different entities, that is, the DU receives broadcast context establishment request messages from different CU-CPs, and the two messages contain different MRBs and different MRB configurations, then the DU selects one of the MRBs and the MRB configuration, and uses the MRB and the MRB configuration when broadcasting MBS data over the air interface. The DU may include the MRB and the MRB configuration information selected by the DU in the broadcast context establishment response and send it to the CU-CP. The CU-CP may further send the MRB and the MRB configuration information to the CU-UP. The CU-UP reconfigures the corresponding MRB and the MRB configuration.
[0159] Figure 7 Describes the process of establishing E1. TMGI1 and TMGI2 are for the same MBS service. CU-CP decides whether to establish the F1 user plane on F1 to transmit MBS data. When CU-CP decides not to establish the NG interface user plane, CU-CP can also decide not to establish the F1 interface user plane.
[0160] Step 701: CU-CP sends a broadcast bearer establishment request message to CU-UP.
[0161] The message includes the E1 interface identifier assigned by CU-CP to TMGI1, the MBS session identifier TMGI1, the identifier of the associated MBS, the service scope of the MBS, and the broadcast bearer establishment request message. It also includes the information of the MBS radio bearer to be established, such as the identifier of the MRB, the quality requirements of the MRB, the identifier of the QoS flow mapped to this MRB, and the QoS requirements of the QoS flow.
[0162] Step 702: CU-UP sends a broadcast bearer establishment response message to CU-CP.
[0163] The message includes the E1 interface identifier allocated by CU-UP to TMGI1, the MBS session identifier TMGI1, the identifier of the associated MBS, the identifier of the successfully established MRB, and the transport layer address information of the F1 user plane allocated by CU-UP to TMGI1.
[0164] Step 703: CU-CP sends another broadcast bearer establishment request or broadcast bearer modification request message to DU.
[0165] If CU-CP receives a broadcast session establishment request from TMGI1, and knows that TMGI1 and TMGI2 transmit the same MBS data through the same MBS association identifier contained in the session establishment request message, CU-CP decides not to establish a user plane with the core network for TMGI2. Then CU-CP also needs to decide whether to establish a user plane of the F1 interface between CU-UP and DU for TMGI2.
[0166] If you want to establish: Under one method, the relevant information of TMGI2 and TMGI1 is sent through different E1 control signaling, and CU-CP sends a broadcast bearer establishment request message to DU. The message contains the E1 interface identifier assigned by CU-CP to TMGI2, the MBS session identifier TMGI2, the identifier of the associated MBS, the service scope of the MBS, and the MRB PDCP configuration. The broadcast bearer establishment request message also contains the information of the MBS radio bearer to be established, such as the identifier of the MRB, the quality requirements of the MRB, the identifier of the QoS flow mapped to this MRB, and the QoS requirements of the QoS flow. CU-UP sends a response message to CU-CP, which contains the F1 interface identifier assigned by CU-UP to TMGI2, the MBS session identifier TMGI2, the identifier of the successfully established MRB, and the transport layer address information of the F1 user plane assigned by DU to TMGI2.
[0167] In another method, the relevant information of TMGI2 and TMGI1 is sent through the same E1 control signaling, and CU-CP sends a broadcast bearer modification request message to CU-UP. The message includes the E1 interface identifier assigned by CU-CP to TMGI1, the MBS session identifier TMGI1, the identifier of the associated MBS, the MBS session identifier TMGI2, and the MRB PDCP configuration. CU-UP sends a response message to CU-CP, which includes the E1 interface identifier assigned by CU-UP to TMGI1 and the MBS session identifier TMGI1.
[0168] If it is not to be established: Under one method, the relevant information of TMGI2 and TMGI1 is sent through different E1 control signaling. CU-CP decides not to establish the F1 user plane of TMGI2 temporarily, but needs to send the information of TMGI2 to CU-UP. CU-CP sends a broadcast bearer establishment request message to CU-UP. The message contains the E1 interface identifier allocated by CU-CP for TMGI2, the MBS session identifier TMGI2, the identifier of the associated MBS, the MBS session identifier TMGI1 associated with TMGI2, and the indication information that CU-UP does not need to allocate the F1 tunnel. CU-UP sends a corresponding message to CU-CP, and the message contains the E1 interface identifier allocated by CU-UP for TMGI2 and the MBS session identifier TMGI2.
[0169] The relevant information of TMGI2 and TMGI1 is sent through the same E1 control signaling. CU-CP decides not to establish the F1 user plane of TMGI2 temporarily, but needs to send the information of TMGI2 to CU-UP. CU-CP sends a broadcast bearer modification request message to DU. The message contains the E1 interface identifier allocated by CU-Cp for TMGI1, MBS session identifier TMGI1, the identifier of the associated MBS, and the MBS session identifier TMGI2. The message also contains indication information that CU-UP does not need to allocate an F1 tunnel. CU-UP sends a corresponding message to CU-CP, which contains the E1 interface identifier allocated by CU-UP for TMGI1 and the MBS session identifier TMGI1.
[0170] Step 704: CU-UP sends a broadcast bearer establishment response or modification response message to CU-CP.
[0171] The message may include the F1 interface identifier assigned by CU-UP to TMGI2, the F1 interface identifier assigned by CU-UP to TMGI1, the MBS session identifier TMGI2, the MBS session identifier TMGI1, the identifier of the associated MBS, the successfully established MRB identifier, the transport layer address information of the F1 user plane assigned by CU-UP to TMGI2, and the transport layer address information of the F1 user plane assigned by CU-UP to TMGI1. If in step 701 and step 703, the CU-CP that sends the message in step 701 and the CU-CP that sends the message in step 703 are the same entity, the same entity can allocate the same MRB and MRB configuration information to TMGI1 and TMGI2.
[0172] Fig.12The process of establishing an F1 tunnel is described. TMGI1 and TMGI2 are for the same MBS service, that is, the transmitted data is the same, but they belong to the operation scope of operators PLMN1 and PLMN2 respectively. In this embodiment, the DU is shared by PLMN1 and PLMN2, and the CU part is not shared. PLMN1 controls CU-CP1 and CU-UP1, and PLMN2 controls CU-CP2 and CU-UP2. Only one F1 tunnel is established on F1, for example, only an F1 tunnel is established between DU and CU-UP1, and MBS data is sent from the tunnel to DU. On the air interface, DU broadcasts the configuration information of the MRB corresponding to TMGI1 and the MRB configuration information corresponding to TMGI2. The MRB configuration information includes the configuration information of PDCP, the configuration information of RLC, the configuration information of the MAC layer, and the configuration information of the physical layer. In order to save resources, the MRB configuration information broadcasted on the air interface is the same for TMGI1 and TMGI2. On the air interface, only one copy of the data is transmitted. When the service of TMGI1 ends early, the F1 tunnel between DU and CU-UP1 also needs to be deleted. At this time, if TMGI2 has not ended, DU needs to initiate the establishment of the F1 tunnel with CU-UP2. When the F1 tunnel is switched, data may be lost. Fig.12 The process of DU initiating F1 tunnel establishment is described. Through the method of this process, it can be ensured that when the F1 tunnel is switched, the UE can continuously receive the MBS service and no data loss will be caused due to the switching of the F1 tunnel.
[0173] Step 1201, CU-CP1 sends a context release command to DU.
[0174] The context release request message is for TMGI1, that is, the message includes the MBS service identifier TMGI1 or includes the identifier of TMGI1 on the F1 interface.
[0175] After receiving the MBS context release command message sent by CU-CP1, DU deletes the context related to TMGI1. In the air interface, DU needs to stop broadcasting the relevant information of TMGI1 on the MBS control channel MCCH, and DU stops broadcasting the configuration information of TMGI1 MRB on MCCH at the beginning of the next most recent modification cycle.
[0176] At this point, TMGI2 has not ended, and there are still UEs that need to receive TMGI2 data. In order to ensure that UEs interested in TMGI2 can continue to receive MBS services, the DU needs to send a request message to CU-CP2, requesting the establishment of an F1 tunnel with CU-UP2 to transmit TMGI2 data. This step message indicates that an F1 tunnel is to be established. The message carries the service identifier TMGI2, or carries the identifier of TMGI2 on the F1 interface. The message can also carry the transport layer address information of the F1 tunnel allocated by the DU to TMGI2. The transport layer address information includes the IP address, tunnel identifier and other information.
[0177] In the air interface, before TMGI1 is released, the configuration information of the MRB corresponding to TMGI1 and the MRB configuration information corresponding to TMGI2 are broadcast on MCCH. The MRB configuration information they correspond to is the same. For the UE that wants to receive the data of TMGI2, the PDCP protocol layer, RLC layer and other protocol layers are configured according to the RMB configuration information. MBS data transmission is transmitted from the core network of PLMN1 to CU-UP1, and then sent to DU through the F1 tunnel between CU-UP1 and DU, and then to UE. The PDCP on the UE side receives MBS data based on the receiving window mechanism. If the PDCP sequence number of the MBS data is outside the receiving window, the UE needs to discard the data. The parameters related to the PDCP reception of the UE are set to the initial value when the PDCP protocol layer of CU-UP1 and the UE side is established. As the PDCP sequence number assigned by CU-UP1 increases, the parameters related to the PDCP reception on the UE side are also changing. When the sequence number carried by the PDCP data packet meets certain conditions, the UE considers that the PDCP data packet is legal and can proceed to the next step. Otherwise, the UE considers that the PDCP data packet needs to be discarded. That is, the sequence number carried by the PDCP data packet and the relevant parameters received by the PDCP at the receiving end are used to determine whether to discard the PDCP data packet. When the F1 tunnel is rebuilt between the DU and CU-UP2, the PDCP protocol on the CU-UP2 is newly established. When the PDCP protocol assigns sequence numbers to data, it starts from the PDCP SN initial value, which is generally equal to zero or 1. According to the sequence number carried by the PDCP data packet after PDCP processing by CU-UP2, and the relevant parameters received by the PDCP at the UE end, which are calculated based on the PDCP between CU-UP1, the sequence number carried by the PDCP data packet sent by CU-UP2 is likely not within the PDCP receiving window of the UE. According to the judgment conditions, the DU will discard the data packet sent by CU-UP2, which will cause the UE to discard the data sent by CU-UP2.
[0178] In order to solve this problem, one method (the first method) is that when CU-CP1 sends a context release command to DU, the message carries the MBS service identifier TMGI1 or includes the identifier of TMGI1 on the F1 interface, and the message also includes the status information of the MBS radio bearer MRB, wherein the MRB status information includes the identifier of the MRB, the Count Value information corresponding to the MRB, or the super frame number HFN information corresponding to the MRB, and may also include the configuration information of the PDCP corresponding to the MRB. The information can be sent to the DU as a container or a separate information element. If it is a container, the DU does not need to parse it. The Count Value information includes the HFN and the PDCP sequence number. The status information of the MRB is obtained by CU-CP1 from CU-UP1, that is, when CU-CP1 sends a bearer release request message, it indicates that CU-UP1 carries the status information of the MRB in the bearer release response message, and then CU-UP1 sends the MRB status information to CU-CP1 through the bearer release response message. It is also possible that CU-CP1 does not need to indicate, and CU-UP1 carries the status information of the MRB in the bearer release response message.
[0179] Step 1202, DU sends a context release completion message to CU-CP1.
[0180] DU sends a release response message to CU-CP1.
[0181] Step 1203, DU sends a transmission resource establishment request message to CU-CP2.
[0182] In order to solve the above-mentioned problem that when the F1 tunnel is switched, the data received from the new tunnel will be outside the UE receiving window and thus be discarded, under the first method, when the DU sends the F1 transmission resource establishment request message to CU-CP2, it carries the identifier of TMGI2, or the identifier of TMGI2 on the F1 interface, and the message carries the status information of MRB, the MRB status information received by the DU from CU-CP1, as mentioned above, the information can be a container, and the DU forwards it to CU-CP2 in step 1203. Or when the DU sends the message to CU-CP2, it also carries the identifier of MRB, the HFN information received by the DU from CU-CP1, and the PDCP configuration information, which is the PDCP configuration information selected by the DU for TMGI1 and TMGI2 and broadcast on the air interface, and also carries the information related to the PDCP sequence number, and the information related to the PDCP sequence number is as described above.
[0183] Under the second method, the DU does not need to obtain the MRB status information related to TMGI1 from CU-CP1. The DU can send the information stored on the DU to CU-CP2, so that the sequence numbers of the PDCP packets sent by CU-UP2 and CU-UP1 are continuous. When the DU sends the F1 transmission resource establishment request message to CU-CP2, it carries the identifier of TMGI2, or the identifier of TMGI2 on the F1 interface. The message also carries the information of the MRB, which includes the identifier of the MRB, PDCP configuration information, which is the PDCP configuration information selected by the DU for TMGI2 and has been broadcast on the air interface, and also carries information related to the PDCP sequence number. As shown in step 602, the information related to the PDCP sequence number can be the highest PDCP sequence number that has been successfully transmitted, or the PDCP sequence number corresponding to the next data packet to be transmitted, or the recommended PDCP sequence number for CU-CP2.
[0184] CU-CP2 sends PDCP configuration information, Count value, or information related to PDCP sequence number to CU-UP2 through the message of E1. CU-UP2 uses the configuration to configure the PDCP protocol. Through this method, CU-UP2 and CU-UP1 use the same PDCP configuration, and the PDCP sequence numbers are also related, for example, continuous, so as to ensure that the data packets sent by CU-UP2 can meet the conditions for correct reception by the UE end, and the data packets sent by CU-UP2 will not be discarded.
[0185] Step 1204, CU-CP2 sends an MBS bearer establishment or modification request message to CU-UP2.
[0186] The message carries the identifier of TMGI2 or TMGI2 on the E1 interface, contains the configuration information of PDCP, and also contains the information related to the Count value or PDCP sequence number. If the NG-U tunnel between CU-UP2 and the core network has not been established for TMGI2, the message may also carry the indication information of NG-U establishment or the indication information of allocating NG-U resources.
[0187] Step 1205, CU-UP2 sends an MBS bearer establishment or modification response message to CU-CP2.
[0188] CU-UP2 establishes the resources for the MBS bearer and allocates the transport layer address of the F1 tunnel. And sends the transport layer address of the F1 tunnel to CU-CP2 through the response message. If the NG-U tunnel between CU-UP2 and the core network has not been established for TMGI2, or according to the indication information carried by 1003, CU-UP2 allocates the transport layer address of NG-U, and includes the address information in the response message and sends it to CU-CP2.
[0189] Step 1206, CU-CP2 sends a context modification request message to DU.
[0190] The message carries TMGI2, the identifier of TMGI2 on the F1 interface, and the transport layer address of the F1 tunnel allocated by CU-UP2.
[0191] Step 1207, DU sends a context modification response message to CU-CP2.
[0192] The DU sends a message to confirm receipt of the message. If the transport layer address of the F1 tunnel allocated by the DU is not carried in step 1201, the transport layer address of the F1 tunnel allocated by the DU may be included in this step.
[0193] DU needs to broadcast the configuration information of TMGI2 MRB on the MCCH channel of the air interface. In order to solve the above-mentioned problem of PDCP data packet loss caused by the change of F1 tunnel, the third method is to instruct UE to re-establish the PDCP protocol stack and reset the relevant parameters received by PDCP to the initial values. CU-CP2 does not need to know the PDCP configuration selected by DU and the PDCP sequence number, HFN and other information of CU-UP1. CU-CP2 decides the PDCP configuration used by CU-UP2 by itself. CU-UP2 establishes the PDCP protocol and calculates the PDCP sequence number according to the existing method.
[0194] After DU receives the service release request sent by CU-CP1, it does not broadcast the MRB configuration information of TMGI1 on the MCCH channel at an appropriate time, such as starting from the next modification period. In step 1210, the DU broadcasts the MRB configuration information to the UE. For the first and second methods, the PDCP configuration information corresponding to TMGI2 has not changed, so the MRB configuration information broadcast by the DU has not changed. For the third method, the MRB configuration information of TMGI2 and the PDCP configuration information broadcast by the DU are the PDCP configuration information received by the DU from CU-CP2. The MRB configuration information of TMGI2 broadcast by the DU also includes the indication information for PDCP re-establishment. For example, if it is set to 1, it means that the UE needs to reset the PDCP protocol stack.
[0195] The UE receives the PDCP re-establishment indication information broadcast on the MCCH, and needs to re-establish the PDCP, including adopting the received new PDCP configuration parameters, and / or setting all PDCP reception-related parameters to initial values and other PDCP re-establishment operations.
[0196] When CU-UP2's PDCP sends data, under the first and second methods, it uses the same PDCP configuration and continuous PDCP sequence number as CU-UP1. In this way, the data packets sent by CU-UP2 fall within the PDCP receiving window of the UE, ensuring that the data can be received correctly and reducing data loss.
[0197] When the PDCP of CU-UP2 sends data, under the third method, the PDCP protocol calculates the PDCP sequence number from the initial value, and the UE also re-establishes the PDCP protocol and calculates the PDCP sequence number from the initial value. In this way, the data packet sent by CU-UP2 falls within the PDCP receiving window of the UE, ensuring that the data can be received correctly and reducing data loss.
[0198] Step 1208: CU-CP2 sends a message to the core network.
[0199] If the NG-U tunnel between CU-UP2 and the core network is not established, CU-CP2 also needs to send a message to the core network to request the establishment of the NG-U tunnel. The message contains TMGI2 and the transport layer address of the NG-U assigned by CU-UP2.
[0200] Step 1209: The core network sends a response message to CU-CP2.
[0201] Figure 8 , Fig. 9 , Fig.10 An enhanced group paging scheme is described to ensure that UE can receive data with higher quality.
[0202] Figure 8 The present invention describes the network configuration of UE to receive multicast services. The base station can decide whether the UE enters the RRC inactive state to receive the multicast services, or remains in the RRC connected state to receive the multicast services. When the multicast services are activated, or the multicast services data is activated, the MBS data is temporarily not sent. The base station configures the UE to enter the RRC inactive state. When the MBS data transmission changes from stop to start, how to wake up the UE to receive the multicast services data.
[0203] Step 801, the core network AMF sends a first message to the UE. The first message is a non-access layer message, which contains the session identifier TMGI of the multicast service. The message also contains indication information, indicating that the UE wants to remain in the RRC connection mode to receive the MBS service, or indicates the special characteristics or special identity of the UE, or indicates that the UE wants to obtain high-quality services to ensure stable and timely system resources for data transmission. According to the indication information, the UE will be kept in the RRC connection mode to receive the MBS service. The UE saves the TMGI and the indication information, and can send the information to the access layer of the UE for use by the access layer.
[0204] Step 802: The core network sends a second message to the base station. The second message is a message of the NG interface, which includes the session identifier TMGI of the multicast service, and also includes indication information, indicating that the UE wishes to remain in the RRC connection mode to receive the MBS service, or indicates the special features or special identity of the UE, or indicates that the UE wishes to obtain high-quality services to ensure stable and timely system resources for data transmission. The base station saves the information in the context of the UE, and according to the indication information, the base station can decide that the UE remains in the RRC connection mode to receive the MBS service.
[0205] Afterwards, when there is no other unicast service to be received and the MBS service is not activated, the base station can configure the UE to enter the RRC inactive mode, for example, by sending an RRC release request message to the UE to configure the UE to enter the RRC inactive mode. This step is omitted.
[0206] Step 803: The core network sends a multicast session activation request message to the base station, which includes the session identifier TMGI of the multicast service.
[0207] Step 804: The base station sends a group paging message to the UE.
[0208] When the base station finds that a UE is in the RRC inactive state or the RRC idle state, the base station sends a group paging message to wake up the UE. The group paging includes the session identifier TMGI of the multicast service and the indication information that the UE can remain in the RRC inactive state to receive the MBS service. After receiving the group paging, if the UE supports receiving the MBS service in the RRC inactive state and the UE does not receive the indication information in step 801, the UE can remain in the RRC inactive state to receive the multicast service.
[0209] If the UE supports receiving MBS services in the RRC inactive state, and the UE receives the indication information of step 801, the UE needs to send an RRC recovery request message to request to enter the RRC connected state to receive multicast services. Then, using the RRC recovery process, the UE enters the RRC connected state to receive MBS service data.
[0210] Fig. 9 The present invention describes the network configuration of UE to receive multicast services. The base station can decide whether the UE enters the RRC inactive state to receive the multicast services, or remains in the RRC connected state to receive the multicast services. When the multicast services are activated, or the multicast services data is activated, the MBS data is temporarily not sent. The base station configures the UE to enter the RRC inactive state. When the MBS data transmission changes from stop to start, how to wake up the UE to receive the multicast services data.
[0211] Step 901: The core network sends a first message to the base station. The first message is a message of the NG interface, which includes a session identifier TMGI of the multicast service, and also includes indication information, indicating that the UE wishes to remain in the RRC connection mode to receive the MBS service, or indicates a special feature or special identity of the UE, or indicates that the UE wishes to obtain high-quality services to ensure stable and timely system resources for data transmission. The base station saves the information in the context of the UE, and according to the indication information, the base station may decide that the UE remains in the RRC connection mode to receive the MBS service.
[0212] Afterwards, when there is no other unicast service to be received and the MBS service is not activated, the base station can configure the UE to enter the RRC inactive mode, for example, by sending an RRC release request message to the UE to configure the UE to enter the RRC inactive mode. This step is omitted.
[0213] Step 902: The core network sends a multicast session activation request message to the base station. The message includes the session identifier TMGI of the multicast service.
[0214] Step 903: The base station sends a dedicated paging request message to the UE.
[0215] According to the saved UE context, if the UE applies to join the multicast session indicated by the TMGI, the UE is in the RRC inactive state, and the indication information described in step 901 is saved in the UE context, the base station decides that the UE remains in the RRC connected mode to receive the MBS service, and the base station first initiates a dedicated paging request message to the UE. When the UE receives the dedicated paging request message, the UE initiates an RRC recovery request message, requesting to enter the RRC connected state to receive the multicast service. After that, using the RRC recovery process, the UE enters the RRC connected state to receive the data of the MBS service.
[0216] Step 904: The base station sends a group paging message to the UE.
[0217] When the base station finds that a UE is in the RRC inactive state or the RRC idle state, the base station sends a group paging message to wake up the UE. The group paging contains the session identifier TMGI of the multicast service, and also contains the indication information that the UE can remain in the RRC inactive state to receive the MBS service. After receiving the group paging, if the UE supports receiving the MBS service in the RRC inactive state, the UE remains in the RRC inactive state to receive the multicast service. Otherwise, the UE needs to send an RRC recovery request message to request to enter the RRC connected state to receive the multicast service. After that, using the RRC recovery process, the UE enters the RRC connected state to receive the MBS service data.
[0218] Fig.10 The present invention describes the network configuration of UE to receive multicast services. The base station can decide whether the UE enters the RRC inactive state to receive the multicast services, or remains in the RRC connected state to receive the multicast services. When the multicast services are activated, or the multicast services data is activated, the MBS data is temporarily not sent. The base station configures the UE to enter the RRC inactive state. When the MBS data transmission changes from stop to start, how to wake up the UE to receive the multicast services data.
[0219] Step 1001, the core network sends a first message to the base station. The first message is a message of the NG interface, the message includes the session identifier TMGI of the multicast service, and the message also includes indication information, indicating that the UE wants to remain in the RRC connection mode to receive the MBS service, or indicates the special characteristics or special identity of the UE, or indicates that the UE wants to obtain high-quality services to ensure stable and timely system resources for data transmission. The base station saves the information in the context of the UE. According to the indication information, the base station can decide that the UE remains in the RRC connection mode to receive the MBS service.
[0220] Step 1002: The base station sends a second message to the UE to configure the UE to enter an RRC inactive state.
[0221] When there is no other unicast service to be received and there is no data to be received for the MBS service, the base station can configure the UE to enter the RRC inactive mode, for example, by sending an RRC release request message to the UE to configure the UE to enter the RRC inactive mode. The second message also includes the session identifier TMGI of the multicast service and indication information, indicating that the UE wishes to remain in the RRC connected mode to receive the MBS service, or indicates the special features or special identity of the UE, or indicates that the UE wishes to obtain high-quality services and ensure stable and timely system resources for data transmission, or indicates that the base station decides that the UE remains in the RRC connected mode to receive the MBS service.
[0222] Step 1003: The core network sends a multicast session activation request message to the base station, wherein the message includes the session identifier TMGI of the multicast service.
[0223] Or in step 1003, the base station receives MBS data from the core network user plane.
[0224] If it is a separate base station architecture, CU-UP receives data from the user plane of the core network, and CU-UP sends a message to notify CU-CP that there is MBS data to be sent. The base station can perform the following steps, such as sending a group paging message to the UE.
[0225] Step 1004: The base station sends a group paging message to the UE.
[0226] When the base station finds that a UE is in the RRC inactive state or the RRC idle state, the base station sends a group paging message to wake up the UE. The group paging includes the session identifier TMGI of the multicast service and the indication information that the UE can remain in the RRC inactive state to receive the MBS service. After receiving the group paging, if the UE supports receiving the MBS service in the RRC inactive state and the UE does not receive the indication information in step 1002, the UE can remain in the RRC inactive state to receive the multicast service.
[0227] If the UE supports receiving MBS services in the RRC inactive state, and the UE receives the indication information of step 1002, the UE needs to send an RRC recovery request message to request to enter the RRC connected state to receive multicast services. Then, using the RRC recovery process, the UE enters the RRC connected state to receive MBS service data.
[0228] Fig.11 is a block diagram of a communication device according to the present invention. The communication device may be used to implement the user equipment, the first base station, the second base station, the DU of the first or second base station, the CU of the first or second base station, the CU-UP of the first or second base station, the CU-CP of the first or second base station, etc. of the present invention. Fig.11 , a communication device according to the present invention includes a transceiver 1110 and a processor 1120. The transceiver 1110 and the processor 1120 are configured to perform the operations of various embodiments of the present invention. Although the transceiver 1110 and the processor 1120 are shown as separate entities, they can be implemented as a single entity, such as a single chip. The transceiver 1110 and the processor 1120 can be electrically connected or coupled to each other. The transceiver 1110 can send signals to other network devices and receive signals from other network entities, such as UEs, base stations, or core network nodes. The processor 1120 may include one or more processing units and may control the network device to perform operations and / or functions according to at least one of the above-mentioned embodiments.
[0229] According to an embodiment of the present disclosure, a user equipment UE may also be provided, comprising: a transceiver; and a processor, coupled to the transceiver and configured to execute the method executed by the UE in the communication system as described above, in other words, configured to execute the method described above with reference to Figures 8 to 10 For details of the above operations, see Figures 8 to 10 The description of any of them will not be repeated here.
[0230] According to an embodiment of the present disclosure, an electronic device may also be provided, comprising: at least one processor; and at least one memory storing computer executable instructions, wherein the computer executable instructions, when executed by the at least one processor, cause the at least one processor to execute any one of the above methods.
[0231] As an example, the electronic device may be a PC, a tablet device, a personal digital assistant, a smart phone, or other device capable of executing the above instruction set. Here, the electronic device is not necessarily a single electronic device, but may also be any device or circuit capable of executing the above instruction (or instruction set) individually or in combination. The electronic device may also be part of an integrated control system or system manager, or may be configured as a portable electronic device interconnected with a local or remote (e.g., via wireless transmission) interface.
[0232] In electronic devices, the processor may include a central processing unit (CPU), a graphics processing unit (GPU), a programmable logic device, a dedicated processor system, a microcontroller or a microprocessor. As an example and not limitation, the processor may also include an analog processor, a digital processor, a microprocessor, a multi-core processor, a processor array, a network processor, etc.
[0233] The processor can execute instructions or codes stored in the memory, wherein the memory can also store data. Instructions and data can also be sent and received through the network via the network interface device, wherein the network interface device can adopt any known transmission protocol.
[0234] The memory may be integrated with the processor, for example, RAM or flash memory is arranged within an integrated circuit microprocessor or the like. In addition, the memory may include a separate device, such as an external disk drive, a storage array, or any other storage device that can be used by a database system. The memory and the processor may be operatively coupled, or may communicate with each other, such as through an I / O port, a network connection, etc., so that the processor can read files stored in the memory.
[0235] In addition, the electronic device may also include a video display (such as a liquid crystal display) and a user interaction interface (such as a keyboard, a mouse, a touch input device, etc.) All components of the electronic device may be connected to each other via a bus and / or a network.
[0236] According to an embodiment of the present disclosure, a computer-readable storage medium storing instructions may also be provided, wherein when the instructions are executed by at least one processor, the at least one processor is prompted to execute any one of the above methods according to the exemplary embodiments of the present disclosure. Examples of computer-readable storage media here include: read-only memory (ROM), random access programmable read-only memory (PROM), electrically erasable programmable read-only memory (EEPROM), random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), flash memory, non-volatile memory, CD-ROM, CD-R, CD+R, CD-RW, CD+RW, DVD-ROM, DVD-R, DVD+R, DVD-RW, DVD+RW, DVD-RAM, BD-ROM, BD-R, BD-R LTH, BD-RE, Blu-ray or optical disk storage, hard disk drive (HDD), solid state drive (SSD), card storage (such as, multimedia card, secure digital (SD) card or extreme digital (XD) card), magnetic tape, floppy disk, magneto-optical data storage device, optical data storage device, hard disk, solid state disk and any other device, any other device is configured to store computer programs and any associated data, data files and data structures in a non-transitory manner and provide the computer programs and any associated data, data files and data structures to a processor or computer so that the processor or computer can execute the computer program. The instructions or computer programs in the above-mentioned computer-readable storage medium can be run in an environment deployed in a computer device such as a client, a host, an agent device, a server, etc. In addition, in one example, the computer program and any associated data, data files and data structures are distributed on a networked computer system, so that the computer program and any associated data, data files and data structures are stored, accessed and executed in a distributed manner by one or more processors or computers.
[0237] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses or adaptations of the present disclosure, which follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present disclosure are defined by the claims.
Claims
1. A method performed by a first network node in a wireless communication system, include: Decide whether to establish an F1 tunnel with the third network node; sending a first message to the second network node, where the first message includes first indication information, wherein the first indication information indicates that a user plane between the third network node and the first network node is not established; and A second message is sent to the third network node, where the second message carries second indication information, wherein the second indication information indicates that a user plane between the third network node and the first network node is not established.
2. The method according to claim 1, further comprising the steps of: A fourth message is received from a fourth network node, the message including at least one of the following information: MRB logo; Packet Data Convergence Protocol PDCP configuration information; Hyperframe number HFN; Count value; Information related to the PDCP sequence number. 3 . The method according to claim 2 , characterized in that the information is obtained by the fourth network node from a user plane.
4. The method according to claim 1, further comprising: A third message is sent to the second network node, where the third message includes transport layer address information of the F1 tunnel.
5. The method according to claim 1, characterized in that: Send a third message to the second network node, where the third message includes at least one of the following information: MRB logo; Packet Data Convergence Protocol PDCP configuration information; Hyperframe number HFN; Count value; Information related to the PDCP sequence number.
6. The method according to claims 4 and 5 is characterized in that: the information related to the PDCP sequence number can be the highest PDCP sequence number that has been successfully transmitted, or the PDCP sequence number corresponding to the next data packet to be transmitted, or the recommended PDCP sequence number.
7. The method according to claims 1 to 6, characterized in that: At least one of the following information is sent by the second network node to the third network node: The transport layer address information message MRB identifier of the F1 tunnel; Packet Data Convergence Protocol PDCP configuration information; Hyperframe number HFN; Count value; Information related to the PDCP sequence number.
8. The method according to claims 2 to 7, wherein the PDCP configuration information and the PDCP sequence number are used by the three network nodes to configure PDCP and set the sequence number of the PDCP packet.
9. According to the method of claims 2 to 8, the UE does not need to re-establish the PDCP protocol.
10. The method according to claim 1, further comprising: include: The MBS service identifier, PDCP configuration information, and PDCP re-establishment indication information are broadcast over the air interface.
11. The method according to claim 10, further comprising: include: The UE re-establishes the PDCP protocol.
12. A method performed by a first network node in a wireless communication system, include: Sending a first message to the second network node, where the first message includes a service identifier of the broadcast session and first indication information, wherein the first indication information indicates that a user plane between the second network node and the core network is not established; and A second message is received from a second network node, where the second message includes a service identifier and user plane address information of the broadcast session, wherein the user plane address information is a transport layer address of a tunnel through which the second network node receives data from a core network.
13. The method according to claim 12, further comprising: include: A third message is sent to a third network node, where the third message includes the user plane address information and / or the GPRS tunneling protocol user plane sequence number.
14. The method according to claim 12, in: The first message is a broadcast bearer establishment request message or a broadcast bearer modification request message.
15. A network node, include: Transceiver; as well as A processor coupled to the transceiver and configured to execute the method of any one of claims 1-11 or 12-14.
