Multicast and broadcast service continuity during mobility
By managing multicast sessions and allocating shared tunnels in the 5G system, the service continuity problem of multicast services by user equipment when switching wireless access nodes is solved, and the stability and reliability of multicast services are achieved.
Patent Information
- Application Number
- CN202080099526.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-04-08
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2040-04-08
AI Technical Summary
In 5G systems, when a user equipment switches from one wireless access node to another wireless access node, the service continuity of the multicast service is difficult to guarantee, especially during the switching of a multicast session, which may lead to packet loss or service. Interrupt.
Receive handover requests from the source wireless access node (S-RAN) or access and mobility management function (AMF) through the target wireless access node (T-RAN), manage multicast sessions, check the establishment of the MBS session, and Allocate shared tunnels when necessary to ensure service continuity. If the MBS session has been established, bind the shared tunnel and the stream in the Unicast Protocol Data Unit (PDU) session; if not established, allocate the MBS DL shared tunnel to avoid packet loss, and update the path conversion request between AMF and SMF to Support switching.
It realizes the continuity of multicast services during the mobile process of wireless devices, avoids data packet loss and service interruption, and ensures the stability and reliability of multicast services in 5G systems.
Smart Images

Figure CN115398973B_ABST
Abstract
Description
Technical Field
[0001] This patent application relates generally to wireless communications. Background Art
[0002] Mobile communication technology is moving the world towards an increasingly connected and networked society. The rapid growth of mobile communications and technological advances have led to greater demands for capacity and connectivity. Other aspects such as energy consumption, equipment cost, spectrum efficiency, and latency are also important to meet the needs of various communication scenarios. Various technologies, including new methods to provide higher quality of service, longer battery life, and improved performance, are under discussion. Summary of the invention
[0003] This patent application describes, inter alia, techniques for enabling switching of multicast data streams in different scenarios. The disclosed techniques can be used to manage multicast sessions when a user equipment (UE) switches from one radio access node to another.
[0004] In one aspect, the method includes: receiving, by a target radio access node (T-RAN) from a source radio access node (S-RAN) or from an access and mobility management function (AMF), a handover request including a multicast or broadcast context for handing over a multicast and broadcast service (MBS) to the T-RAN. The method also includes: in a case where an MBS session identified in the multicast or broadcast context has been established at the T-RAN, binding a shared tunnel for the MBS and a stream in a unicast protocol data unit (PDU) session; and sending a message including a handover request confirmation or a path conversion to the AMF.
[0005] In another aspect, another wireless communication method is disclosed. The method includes: receiving a handover request by a target radio access node (T-RAN) from a source radio access node (S-RAN) or from an access and mobility management function (AMF), the handover request including a multicast or broadcast context for handing over a multicast and broadcast service (MBS) to the T-RAN. The method also includes checking the establishment of the MBS at the T-RAN, wherein in the case where the MBS has not been established, the T-RAN allocates a shared tunnel for the MBS, and in another case where the MBS has been established at the T-RAN, the shared tunnel for the MBS is bound to a flow in a unicast protocol data unit (PDU) session.
[0006] These and other aspects are described throughout this application. BRIEF DESCRIPTION OF THE DRAWINGS
[0007] Figure 1 The architecture of a 5G system according to some example embodiments is depicted.
[0008] Figure 2An enhanced 5G system architecture for providing broadcast / multicast services to user equipment according to some example embodiments is depicted.
[0009] Figure 3 Depicted are stages in a process for providing multicast services according to some example embodiments.
[0010] Figure 4 Depicted are processes for establishing a shared tunnel for delivering multicast services in a 5G system according to some example embodiments.
[0011] Figure 5 Depicted is an Xn-based process for delivering multicast / broadcast services according to some example embodiments.
[0012] Figure 6 An N2-based process for delivering multicast / broadcast services is shown according to some example embodiments.
[0013] Figure 7 Processes for wireless communications are described in accordance with some example embodiments.
[0014] Figure 8
[0013] Another process for wireless communications is depicted in accordance with some example embodiments.
[0015] Fig. 9 A wireless communication system is depicted in accordance with some example embodiments.
[0016] Fig.10 A block diagram of a portion of a wireless system is depicted in accordance with some example embodiments. DETAILED DESCRIPTION
[0017] Certain features are described using the example of a fifth generation (5G) wireless protocol. However, the applicability of the disclosed technology is not limited to 5G wireless systems.
[0018] The 5G system (5GS) includes multicast / broadcast services. One aspect of these services is multicast discovery and the start and end of multicast services. User equipment (UE) can operate using unicast (also known as unicast) and multicast services simultaneously. When a UE moves from one radio access network (RAN) node to another RAN node, service continuity for broadcast and multicast services is required. This article discloses a technology for providing service continuity for broadcast and multicast services.
[0019] In some example embodiments, a multicast service is a communication service in which the same service and the same content data are provided to a group of authorized user devices at the same time (i.e., not all user devices within the multicast coverage are authorized to receive the data). A broadcast service is a communication service in which the same service and the same content data are provided to all UEs in a geographic area at the same time (i.e., all UEs in the broadcast coverage area are authorized to receive the data).
[0020] Figure 1 An example architecture 100 for a 5G system is depicted. The 5G system architecture consists of network functions (NFs) as well as other functions described below.
[0021] The access and mobility management function (AMF) 125 performs functions including UE mobility management, reachability management, connection management and other functions. The AMF terminates the radio access network control plane (RAN CP) interface (also known as the N2 interface 142) and the non-access layer (NAS) (also known as the N1 interface 137), NAS encryption and integrity protection. The AMF also distributes the session management (SM) NAS to the appropriate session management function (SMF) via the N11 interface 127.
[0022] The session management function (SMF) 130 includes user equipment (UE) Internet Protocol (IP) address allocation and management, UP function selection and control, PDU connection management, etc.
[0023] The user plane function (UPF) 145 is the host point for mobility within / between radio access technologies (RATs) and the external protocol data unit (PDU) session point for interconnecting with data networks. The UPF also routes and forwards data packets as instructed by the SMF, and when the UE is in idle mode, the UPF caches downlink (DL) data.
[0024] The unified data management (UDM) 110 manages subscription profiles for the UE. The subscription includes data for mobility management (e.g., restricted areas), session management (e.g., quality of service (QoS) profiles for each slice of each data network name (DNN)). The subscription data also includes slice selection parameters used by the AMF to select the SMF. The AMF and SMF obtain subscriptions from the UDM, and the subscription data is stored in the unified data repository (UDR). The UDM uses these data after receiving a request from the AMF or SMF.
[0025] The Policy Control Function (PCF) 115 manages network behavior based on subscriptions and instructions from the Application Function (AF) 120. The PCF provides policy rules to be enforced by the Control Plane (CP) functions such as AMF and / or SMF. The PCF accesses the UDR to retrieve policy data.
[0026] A network open function (NEF) (not shown) may be included in a system for exchanging information between 5GC and an external third party. For example, AF 120 may store application information in UDR via NEF.
[0027] The Multicast / Broadcast Multimedia Subsystem (MBMS) was developed for video broadcasting and streaming services. Since its initial development, the MBMS system has been updated to support new services such as public safety, Consumer Internet of Things (CIoT), and Vehicle-to-Everything (V2X). As 5GS develops and matures, it is likely that 5GS will provide multicast broadcast services for vertical businesses.
[0028] Figure 2 An example of an enhanced 5G system architecture 200 that provides broadcast / multicast services to user equipment 230 is depicted.
[0029] Multicast / Broadcast Service Function (MBSF) 235 is a network function (NF) that handles the signaling portion of the service layer functions and provides an interface to the application server 245. It can be an independent entity or collocated with the MB-SMF.
[0030] The multicast / broadcast service user plane (MBSU) 240 handles the payload portion of the service layer capabilities and may be a standalone entity or collocated with the MBSF or MB-UPF.
[0031] SMF and UPF can be enhanced to support multicast / broadcast services. AMF can also be enhanced to make the signaling for multicast / broadcast services between RAN / UE and multicast / broadcast SMF (MB-SMF) 225 transparent.
[0032] Figure 3 An example of stages in a process for providing multicast services is depicted.
[0033] At the service subscription stage 310, subscription is an agreement by the user to accept the services provided by the operator. The relationship between the user and the service provider is established during the subscription. The relationship can be statically stored in the unified data repository (UDR) or dynamically pushed from the MBS server to the relevant PCF.
[0034] At the multicast service start phase 320, the MBS server triggers the MBSF to start a session to send multicast data. The MBSF triggers the MBS session establishment in the 5GS. The session start occurs independently of the user's activation of the service (i.e., a given user can activate the service before the session starts or after the session starts). The session start is a trigger for the establishment of bearer resources for MBMS data delivery.
[0035] At the PDU session establishment phase 330, the UE may initiate a unicast PDU session establishment to retrieve the multicast service configuration or establish an association with the MBSF. This may occur before phase 310. The UE may dynamically subscribe to the multicast service via the established PDU session. This phase may also occur after phase 340 in the case where the multicast service starts before the UE joins the multicast service.
[0036] The multicast service announcement / discovery mechanism allows users to request or be informed of the range of available multicast services at the multicast service announcement stage 340. The announcement is also used to distribute information to users about service parameters (e.g., IP multicast address) and possible other service-related parameters (e.g., service start time) required for service activation.
[0037] At the multicast join phase 350, the UE initiates a join procedure to become a member of the multicast group.
[0038] At data transmission phase 360, data is transmitted to the UE.
[0039] Figure 4 An example of a process for establishing a shared tunnel for delivering a multicast service in a 5G system is depicted. In some example embodiments, the process occurs after the UE has established a PDU session.
[0040] At 410, the UE initiates a unicast PDU session establishment procedure. In this procedure, an MBS-SMF supporting unicast and multicast is selected based on a specific DNN and single network slice selection assistance information (S-NSSAI). After completing the establishment procedure, the UE can retrieve the multicast service configuration.
[0041] At 420, the UE initiates a join request via UP data or NAS message to join the multicast communication service.
[0042] At 430, when the MB-SMF detects the request, the MB-SMF requests the MBSF to authorize the UE. The MBSF checks whether the UE is allowed to access the service. If so, the MBSF checks whether the multicast context for the multicast group exists (i.e., whether the UE has already joined the multicast group). If the multicast context for the multicast group does not exist, the SMF creates it when the first UE joins the multicast group. This check may involve the MBS server, PCF and / or UDM. The MBS server may store the group membership in the UDM or send it to the PCF before 430. The MBSF or MB-SMF may then retrieve the information during the association establishment between the MBSF / MB-SMF and the PCF / UDM. If there is no interaction between the MBSF and the PCF / UDM, the MBSF may retrieve the information from the MB-SMF.
[0043] At 440, the MBSF triggers the MB-SMF to establish a virtual multicast flow into the unicast PDU session.
[0044] At 450, the MBSF triggers the MB-SMF to establish a shared tunnel for UEs belonging to the same multicast group under the same NG-RAN node. The virtual stream included in the unicast PDU session is not used to transmit multicast service data. The multicast service data is transmitted to the NG-RAN node via the shared tunnel. If there is a shared tunnel for the same multicast service (i.e., before this process, other UEs have joined the multicast group via the NG-RAN node), 450 can be skipped.
[0045] At 460, the information from 440 and / or 450 is provided to the NG-RAN node to bind the shared tunnel and the virtual flow linked in the unicast PDU session. The information may include a flow identifier and / or a TMSI and / or a session identifier.
[0046] At 470, when the NG-RAN node receives the multicast data, the NG-RAN may determine whether to transmit the multicast stream via broadcast mode or unicast mode. If unicast mode is used, a virtual multicast stream is used to transmit the multicast stream over the wireless interface.
[0047] When a UE moves to another RAN node, service continuity of unicast services can be performed during handover, but providing service continuity of multicast services is challenging. The present disclosure provides a technique for ensuring service continuity of multicast services for mobile UEs.
[0048] Figure 5 An example of an Xn-based process for delivering multicast / broadcast services is depicted.The preceding description focuses on the processing of multicast services.
[0049] At 505, the UE receives multicast service data from the source RAN (S-RAN). When the UE moves to the edge of the S-RAN coverage, the S-RAN selects a target RAN (T-RAN) for transmitting the UE including the multicast service. The S-RAN initiates a handover procedure and sends a handover request message to the T-RAN. The T-RAN performs admission control and reserves resources based on the context from the S-RAN. The context may also include an indication of the multicast service. If the UE has multiple multicast services, the UE context transmitted from the S-RAN to the T-RAN includes an MBS context, such as a TMGI, an MBS session identifier, an MBS service flow identifier, or an MBS service identifier. Based on the MBS context, the T-RAN determines whether an MBS session for the same MBS service has been established. If an MBS session for the same MBS service has been established (e.g., the UE multicast service is joining at least one other UE that has obtained the multicast service from the T-RAN), the T-RAN binds the virtual streams in the shared tunnel and unicast PDU session for the MBS session. If an MBS session for the same MBS service (e.g., no other UE is getting multicast service from T-RAN) has not been established, T-RAN can allocate an MBS DL shared tunnel for the MBS service. To avoid packet loss, T-RAN can allocate a tunnel for data forwarding. For MBS services, the virtual flow linked in the unicast PDU session associated with the MBS session can be dropped in T-RAN to transmit the forwarded data.
[0050] If the T-RAN cannot establish a shared tunnel for the MBS service, the T-RAN notifies the S-RAN of the failure and the reason for the failure. Virtual flows linked in unicast PDU sessions associated with the MBS session may be indicated as unaccepted flows.
[0051] If the UE has multiple MBS services, the T-RAN can allocate multiple shared tunnels for each MBS service. The T-RAN can allocate one shared tunnel for multiple MBS services indicated by the MBSF or MB-SMF.
[0052] At 510, T-RAN sends an N2 path switching request to AMF, which includes a list of PDU sessions to be switched with N2 SM information, a list of PDU sessions that failed to be established, and the failure reason given for each session in the N2 SM information element, and UE location information. If MBS DL session information is allocated for each MBS session at 505, one or more MBS DL sessions / flows associated with the MBS service identifier, MBS session identifier or MBS service flow identifier or TMGI are also included and transmitted to the MBS-SMF or further transmitted to the MBSF.
[0053] If the T-RAN cannot establish a shared tunnel for the MBS service, the accepted Quality of Service (QoS) flow list shall not include the virtual flow bound to the MBS service.
[0054] At 520, a context request (e.g., Nsmf_PDUSession_UpdateSMContextRequest) from the AMF to the SMF includes one or more of the N2 SM information received from the T-RAN at 510 and the N2 SM information from the source NG-RAN (Secondary RAT Usage Data), the UE location information, and the presence of the UE in the LADN service area. The AMF sends the N2 SM information by calling a request service operation (e.g., Nsmf_PDUSession_UpdateSMContext) for each PDU session in the PDU session list received in the N2 path switch request. If MBS DL session information is allocated at 510, the AMF transmits the MBS DL session information to the MB-SMF. If multiple MBS sessions are involved, the AMF transmits the MBS DL session information to the MB-SMF for each MBS session in the MBS session list received in the N2 path switch request.
[0055] At 530-540, if the MBS DL session information is included in the request, the SMF determines whether the UE is authorized to receive the MBS service. If the UE is authorized to receive the MBS service identified by one or more of the MBS service ID, MBS session ID or TMGI, the SMF further determines whether a shared tunnel for the MBS service is established in the UPF. If the shared tunnel is established in the UPF, the SMF notifies the UPF of the updated MBS DL information in the T-RAN via the N4 session modification. If the SMF decides to allocate a new shared tunnel to transmit the MBS service, the SMF sends an N4 session establishment request to the UPF. The parameters of the MBS session include the MBS service identifier, the MBS session identifier and / or the TMGI.
[0056] If the shared tunnel information is updated at 530-540, the SMF notifies the MBSF at 550, and the MBSF updates the information at the MBSU at 560.
[0057] At 570, for the successfully transmitted PDU session, the SMF sends a context response (e.g., Nsmf_PDUSession_UpdateSMContext response) to the AMF.
[0058] At 580, once responses (e.g., Nsmf_PDUSession_UpdateSMContext responses) are received from all SMFs, the AMF aggregates the received core network (CN) tunnel information and sends the aggregated information to the T-RAN as part of the N2 SM information along with the failed PDU session in the N2 Path Switch Request Acknowledgement (Ack).
[0059] In some cases, an intermediate SMF (I-SMF) and / or an intermediate user plane function (I-UPF) may be included in the handover process. The I-SMF and / or I-UPF may be inserted, changed, or removed during the handover process. For example, an existing or new I-SMF and / or I-UPF may be involved in the establishment or update of an MBS shared tunnel. Shared tunnel information may be exchanged between the T-RAN and UPF, the I-UPF and UPF, and / or the UPF and MBSF.
[0060] If the MBSF is co-located with the MB-SMF, the signaling between the MB-SMF and the MBSF is inside the MBSF and MB-SMF devices co-located.
[0061] Figure 6 An example of an N2-based process for delivering multicast / broadcast services is described. The foregoing description describes the processing of broadcast and multicast services in detail.
[0062] At 615, the UE receives multicast service data from the S-RAN. When the UE moves to the edge of the S-RAN coverage, the S-RAN selects the T-RAN to transmit the UE including the multicast service. The S-RAN initiates a handover procedure.
[0063] At 601, the S-RAN sends a message to the AMF requesting a handover, the message requesting a handover includes a target identifier, a source-to-target transparent container, a list of SM N2 information, a PDU session identifier, and an intra-system handover indication. The source-to-target transparent container includes NG-RAN information created by the S-RAN for use by the T-RAN, which is transparent to the 5G Core (5GC). The source-to-target transparent container also includes corresponding user plane security enforcement information, QoS flow / DRB information, which is subject to data forwarding for each PDU session.
[0064] The PDU sessions handled by the S-RAN (i.e., all existing PDU sessions with active UP connections) are included in the message requiring handover, indicating which PDU session or sessions the S-RAN requests for handover. If direct data forwarding is available, the SM N2 information includes direct forwarding path availability. Direct forwarding path availability indicates whether direct forwarding from the S-RAN to the T-RAN is available. This indication from the S-RAN may be based on, for example, the existence of an IP connection and one or more security associations between the S-RAN and the T-RAN.
[0065] The context may also include an indication of a multicast service. If the UE has multiple multicast services, the UE context transmitted from the S-RAN to the T-RAN includes an MBS context such as a TMGI, an MBS session identifier, an MBS flow identifier, or an MBS service identifier. Based on the MBS context, the T-RAN checks whether an MBS session for the same MBS service has already been established.
[0066] At 602, when the S-AMF can no longer serve the UE, the S-AMF selects a target AMF (T-AMF). When the T-AMF is selected, the S-AMF sends a handover message such as a Namf_Communication_CreateUEContext request message to the T-AMF, which includes N2 information such as a target identifier, a source-to-target transparent container, an SM N2 information list, a PDU session identifier and / or UE context information. For each PDU session indicated by the S-RAN, the T-AMF calls a request such as a Nsmf_PDUSession_UpdateSMContext request to the associated SMF. Based on the target identifier, the SMF checks whether the N2 handover for the indicated PDU session can be accepted. The SMF also checks the selection criteria of the UPF. If the SMF selects a new intermediate UPF, the SMF sends an N4 session modification request to the PSA, and then sends an N4 session establishment request to the T-UPF upon receiving a response from the PSA. The SMF sends a Nsmf_PDUSession_UpdateSMContext response message including the PDU session identifier, N2 SM information and / or the reason for non-acceptance to the T-AMF.
[0067] At 603, if T-AMF is selected, 603 and 609 are performed by T-AMF. Otherwise, 603 and 609 are performed by S-AMF.
[0068] The AMF determines the T-RAN based on the target identity. It sends a handover request message including a source-to-target transparent container, N2 MM information, a list of N2 SM information, a tracking requirement and / or a UE radio capability identifier to the T-RAN. The source-to-target transparent container is forwarded to the T-RAN when received from the S-RAN. The N2 MM information includes, for example, security information and a list of mobility restrictions (if available at the AMF).
[0069] If the context included in the source-to-target transparent container includes an indication of a multicast service, the T-RAN checks whether an MBS session for the same MBS service has been established based on the TMGI, the MBS session identifier, the MBS flow identifier, or the MBS service identifier.
[0070] If an MBS session for the same MBS service has already been established (e.g., a UE is joining a group already served by T-RAN for a multicast service), T-RAN binds the shared tunnel for the MBS session to the streams linked in the unicast PDU session (sometimes referred to as virtual streams). If an MBS session for the MBS service has not yet been established (e.g., a user not served by T-RAN is served by T-RAN for the same multicast service), T-RAN allocates an MBS DL shared tunnel for the MBS service.
[0071] To avoid packet loss and support direct data forwarding, T-RAN can allocate tunnels for data forwarding. For MBS services, the streams (pseudo) linked in the unicast PDU session associated with the MBS session can be torn down at T-RAN to transmit the forwarded data.
[0072] If the T-RAN cannot establish a shared tunnel for the MBS service, the T-RAN informs the S-RAN of the appropriate failure cause in the target-to-source transparent container.
[0073] If the UE has multiple MBS services, the T-RAN may allocate multiple shared tunnels separately for the MBS services.
[0074] At 604, the T-RAN sends a handover request confirmation to the AMF, which includes one or more of the following: a target to source transparent container, a list of PDU sessions to be switched with N2 SM information, a list of PDU sessions that failed to be established, and the failure reason given for each session in the N2 SM information element. The N2 SM information in the list of PDU sessions to be switched contains T-RAN N3 addressing information for each PDU session identifier, such as the N3 UP address of the T-RAN for the PDU session and the tunnel identifier.
[0075] If MBS DL session information is allocated for each MBS session at 603, the MBS DL session associated with the MBS service identifier or the MBS session identifier or the TMGI is also included and transmitted to the MBS-SMF or further to the MBSF.
[0076] If the T-RAN cannot establish a shared tunnel for the MBS service, the accepted QoS flow list shall not include flows bound to the MBS service (virtual).
[0077] At 605, the AMF sends a context request such as an Nsmf_PDUSession_UpdateSMContext request message to the SMF, which includes one or more of the PDU session identifier and the N2 SM response received from the T-RAN at 604. For each N2 SM response received from the T-RAN including one or more N2 SM information (included in the handover request confirmation), the AMF sends the received N2 SM response to the SMF indicated by the corresponding PDU session identifier.
[0078] If no new T-UPF is selected, if the N2 handover is accepted by T-RAN, the SMF stores the N3 tunnel information of T-RAN from the N2 SM response message.
[0079] At 606, the SMF / UPF allocates an N3 UP address and a tunnel identifier for indirect data forwarding corresponding to the data forwarding tunnel endpoint established with the T-RAN.
[0080] At 607-608, if the MBS DL session information is included, the SMF checks whether the UE is authorized to receive the MBS service. If the UE is authorized to receive the MBS service identified by the MBS service identifier or the MBS session identifier or the TMGI, the SMF checks whether the shared tunnel for the MBS service is established in the UPF. If the shared tunnel is established in the UPF, the SMF notifies the UPF of the updated MBS DL information in the T-RAN via the N4 session modification. If the SMF decides to allocate a new shared tunnel to transmit the MBS service, the SMF sends an N4 session establishment request to the UPF. Parameters of the MBS session, such as the MBS service identifier or the MBS session identifier or the TMGI.
[0081] If the shared tunnel information is updated, SMF notifies MBSF, and MBSF updates the information in MBSU.
[0082] The aforementioned steps 607-608 may be performed after step 614. The SMF only stores the received MBS DL session information here.
[0083] At 609, the SMF sends a context response message such as Nsmf_PDUSession_UpdateSMContext response to the AMF, which may include N2 SM information. In the case of indirect data forwarding, the DL forwarding tunnel information is included in the N2 SM information.
[0084] In case of AMF change, T-AMF sends a context response message such as Namf_Communication_CreateUEContext response message to S-AMF, the Namf_Communication_CreateUEContext response message includes one or more of the N2 information required for S-AMF to send a handover command to AMF, the N2 information required for the handover command includes the target to source transparent container, the list of failed PDU sessions to be established, the N2 SM information including the N3 DL forwarding information and / or the PCF ID. The target to source transport container is received from T-RAN. The N2 SM information is received from SMF.
[0085] At 610, the AMF sends a handover command to the S-RAN, which includes a target to source transparent container, a list of PDU sessions to be switched with N2SM information (the N2 SM information contains information received from the T-RAN during the handover preparation phase), and a list of PDU sessions that failed to be established.
[0086] The target-to-source transparent container received from the S-AMF is forwarded. The SM forwarding information list includes the T-RAN SM N3 forwarding information list for direct forwarding or the S-UPF SM N3 forwarding information list for indirect data forwarding.
[0087] At 611, the S-RAN sends a handover command message (UE container) to the UE.
[0088] At 612, the UE sends a handover confirmation message to the T-RAN. After the UE has successfully synchronized to the target cell, the UE sends a handover confirmation message to the T-RAN. The message indicates that the handover is successful at the UE.
[0089] At 613, the T-RAN sends a handover notification message to the (T-)AMF. The message indicates that the handover is successful at the T-RAN.
[0090] At 614, the T-AMF sends a context request message such as an Nsmf_PDUSession_UpdateSMContext request to the SMF, the Nsmf_PDUSession_UpdateSMContext request including one or more of a handover complete indication for the PDU session identity, UE presence in the LADN service area, and / or N2 SM information including secondary RAT usage data.
[0091] If 607 - 608 are not performed, the SMF performs an operation on the MBSF using the MBS DL information stored in 606 .
[0092] If the UE has multiple MBS services, more than one SMF may interact with the MBSFs respectively.
[0093] If 607-608 are executed, the downlink data packets for the MBS service are sent from the MBSU to the S-RAN via the UPF after 613, otherwise, after the shared tunnel is established or updated, the downlink data packets for the MBS service are sent from the MBSU to the S-RAN via the UPF.
[0094] Additional switching procedures may also be performed.
[0095] In some cases, during the handover process, the I-SMF may be inserted, changed or removed. In that case, the (existing or new) I-SMF and I-UPF participate in establishing or updating the MBS shared tunnel. Shared tunnel information may be exchanged between T-RAN and I-UPF, UPF and UPF, UPF and MBSF.
[0096] Figure 7 An example of a process 700 for wireless communication according to some example embodiments is depicted. At 710, the method 700 includes: receiving, by a target radio access node (T-RAN) from a source radio access node (S-RAN) or from an access and mobility management function (AMF), a handover request including a multicast or broadcast context for handing over a multicast and broadcast service (MBS) to the T-RAN. At 720, the method includes: binding a shared tunnel for the MBS with a flow in a unicast protocol data unit (PDU) session if an MBS session identified in the multicast or broadcast context has been established at the T-RAN. At 730, the method includes: sending a message including a handover request confirmation or a path switch to the AMF.
[0097] Figure 8Another example of a process 800 for wireless communication according to some example embodiments is shown. At 810, the method 800 includes: receiving, by a target radio access node (T-RAN) from a source radio access node (S-RAN) or from an access and mobility management function (AMF), a handover request including a multicast or broadcast context for handing over a multicast and broadcast service (MBS) to the T-RAN. At 820, the method includes: checking for establishment of the MBS at the T-RAN, wherein in a case where the MBS has not been established, allocating a shared tunnel for the MBS by the T-RAN, and in another case where the MBS has been established at the T-RAN, binding the shared tunnel for the MBS to a flow in a unicast protocol data unit (PDU) session.
[0098] Fig. 9 An example of a wireless communication system 900 is shown in which the techniques according to one or more embodiments of the present technique may be applied. The wireless communication system 900 may include one or more base stations (BSs) 905a, 905b, one or more wireless devices 910a, 910b, 910c, 910d, and a core network 925. The base stations 905a, 905b may provide wireless services to the wireless devices 910a, 910b, 910c, and 910d in one or more wireless sectors. In some embodiments, the base stations 905a, 905b include directional antennas that generate two or more directional beams to provide wireless coverage in different sectors.
[0099] The core network 925 can communicate with one or more base stations 905a, 905b. The core network 925 provides connections with other wireless communication systems and wired communication systems. The core network may include one or more service subscription databases to store information related to subscribed wireless devices 910a, 910b, 910c and 910d. The first base station 905a can provide wireless services based on a first wireless access technology, and the second base station 905b can provide wireless services based on a second wireless access technology. Depending on the deployment scenario, base stations 905a and 905b can be quasi-co-located or installed separately on site. Wireless devices 910a, 910b, 910c and 910d can support a variety of different wireless access technologies. The techniques and embodiments described in this application can be implemented by the base stations of the wireless devices described in this application.
[0100] Fig.101 is a block diagram representation of a portion of a wireless station according to one or more embodiments of the present technology that may be applied. A radio 1005, such as a base station or a wireless device (or UE), may include a processor electronics 1010, such as a microprocessor that implements one or more wireless technologies presented herein. The radio 1005 may include a transceiver electronics 1015 to send and / or receive wireless signals through one or more communication interfaces such as an antenna 1020. The radio 1005 may include other communication interfaces for sending and receiving data. The radio 1005 may include one or more memories (not explicitly shown) that are configured to store information such as data and / or instructions. In some embodiments, the processor electronics 1010 may include at least a portion of the transceiver electronics 1015. In some embodiments, at least some of the disclosed techniques, modules, or functions are implemented using the radio 1005. In some embodiments, the radio 1005 may be configured to perform the methods described in this application.
[0101] It should be understood that the present application discloses techniques that can be embodied in various embodiments to establish and manage multicast sessions. The disclosed and other embodiments, modules and functional operations described in the present application can be implemented in digital electronic circuits, or in computer software, firmware or hardware (including the structures disclosed in the present application and their equivalents), or in a combination of one or more of them. The disclosed and other embodiments can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer-readable medium for execution by a data processing device or control of the operation of the data processing device. The computer-readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter that affects a machine-readable propagation signal, or one or more of them. The term "data processing device" covers all devices, equipment and machines for processing data, including, for example, a programmable processor, a computer or multiple processors or computers. In addition to hardware, the device may also include code that creates an execution environment for the computer program in question, such as code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagated signal is an artificially generated signal, eg, a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.
[0102] A computer program (also referred to as a program, software, software application, script, or code) may be written in any form of programming language, including compiled or interpreted languages, and may be deployed in any form, including stand-alone programs or modules, components, subroutines, or other units suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program may be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple collaborative files (e.g., files storing one or more modules, subroutines, or portions of code). A computer program may be deployed to execute on one computer, or on multiple computers located at one site or distributed at multiple sites and interconnected by a communications network.
[0103] The processes and logic flows described in this application can be performed by one or more programmable processors that execute one or more computer programs to implement functions by operating on input data and generating outputs. The processes and logic flows can also be performed by dedicated logic circuits such as FPGAs (field programmable gate arrays) or ASICs (application-specific integrated circuits), and the apparatus can also be implemented as dedicated logic circuits such as FPGAs (field programmable gate arrays) or ASICs (application-specific integrated circuits).
[0104] Processors suitable for executing computer programs include both general-purpose microprocessors and special-purpose microprocessors by way of example, and any one or more processors of any kind of digital computer. Typically, the processor will receive instructions and data from a read-only memory or a random access memory or both. The basic elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include or be operably coupled to one or more mass storage devices (such as magnetic disks, magneto-optical disks, or optical disks) for storing data to receive data from the mass storage device or transfer data to the mass storage device, or both. However, a computer need not have such a device. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, including, for example, semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD ROM and DVD-ROM disks. The processor and memory may be supplemented by or incorporated into a dedicated logic circuit.
[0105] Although this patent application contains many details, these details should not be interpreted as limitations on any invention or the scope of what may be claimed, but rather as descriptions of features that may be unique to a particular embodiment of a particular invention. Certain features described in the context of separate embodiments in this patent application may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. In addition, although features may be described above as working in certain combinations and even initially claimed as such, in some cases, one or more features from the claimed combination may be deleted from the combination, and the claimed combination may be directed to a sub-combination or variant of a sub-combination.
[0106] Similarly, although operations are depicted in a particular order in the figures, this should not be understood as requiring that the operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve the desired results. Furthermore, the separation of various system components in the embodiments described in this patent document should not be understood as requiring such separation in all embodiments.
[0107] Only a few implementations and examples are described, and other implementations, enhancements, and variations may be made based on what is described and illustrated in this patent application.
Claims
1. A wireless communication method, include: The target radio access node T-RAN receives a handover request from the source radio access node S-RAN or from the access and mobility management function AMF, wherein the handover request includes a multicast or broadcast context for handing over a multicast and broadcast service MBS to the T-RAN; determining, by the T-RAN, whether an MBS session identified in a multicast or broadcast context has been established; In case that the MBS session identified in the multicast or broadcast context has been established at the T-RAN, binding a shared tunnel for MBS with a virtual flow in a unicast protocol data unit (PDU) session to send multicast service data through the shared tunnel; or If the MBS session identified in the multicast or broadcast context has not been established at the T-RAN, establishing a shared tunnel for the MBS session; and In response to receiving the handover request from the S-RAN, sending a message including a handover request confirmation to the AMF, or in response to receiving the handover request from the AMF, sending a message including a path conversion to the AMF.
2. The wireless communication method according to claim 1, in, The message also includes an indication of successful handover and that the shared tunnel has been established at the T-RAN, the multicast or broadcast context not being included in the message.
3. The wireless communication method according to claim 1, in, Also included in the message is an indication that the handover was successful and that the shared tunnel has not been established at the T-RAN, the multicast or broadcast context being included in the message.
4. The wireless communication method according to claim 1, in, In case a handover failure is indicated, the list of flows that failed and the reason are included in the message.
5. The wireless communication method according to claim 1, in, The MBS context for a multicast or broadcast downlink flow includes an MBS identity, or a multicast or broadcast flow identity, or a temporary mobile group identity TMGI, and wherein the MBS context corresponds to one or more multicast or broadcast downlink flows associated with an MBS session including the multicast or broadcast downlink flows.
6. The wireless communication method according to claim 1, in, The T-RAN allocates a tunnel for data forwarding.
7. The wireless communication method according to claim 6, in, The S-RAN forwards the buffered multicast or broadcast downlink data by using the flow identified by the 5QI in the unicast PDU session.
8. The wireless communication method according to claim 1, in, The multicast or broadcast context is included in a source-to-destination container.
9. The wireless communication method according to claim 1, further comprising: include: receiving a handover confirmation from the UE at the T-RAN; as well as Send a handover complete message to the target AMF.
10. A wireless communication method, include: The target radio access node T-RAN receives a handover request from the source radio access node S-RAN or from the access and mobility management function AMF, wherein the handover request includes a multicast or broadcast context for handing over a multicast and broadcast service MBS to the T-RAN; as well as checking establishment of the MBS at the T-RAN; In a case where the MBS has not been established, the T-RAN allocates a shared tunnel for the MBS; or In another case where the MBS has been established at the T-RAN, a shared tunnel for the MBS is bound to a virtual flow in a unicast protocol data unit (PDU) session, Wherein, in a case where the shared tunnel for the MBS is not established by the target wireless access network, the quality of service flow acceptance list does not include the identifier of the flow bound to the MBS.
11. The wireless communication method according to claim 10, in, The MBS context for the multicast or broadcast downlink flow includes an MBS identity, or a multicast or broadcast flow identity, or a temporary mobile group identity TMGI, and wherein the MBS context corresponds to one or more multicast or broadcast downlink flows associated with an MBS session including the multicast or broadcast downlink flow. 12 . A communication device, comprising a processor and a memory, wherein the processor is configured to read instructions from the memory so that the processor implements the method according to claim 1 .
13. A computer program product having stored thereon codes which, when executed by a processor, cause the processor to carry out the method according to any one of claims 1 to 11.
Citation Information
Patent Citations
Method for establishing control side tunnel in mobile communication system multicast service
CN101087249A
Multicast broadcast service dispatching method
CN101090525A
Method and system for implementing broadcast multicast business
CN101232387A
UE GROUPS, UE GROUP MANAGER UEs AND UE GROUP MEMBER UEs
CN110945936A
Handover method in mobile communication network based on evolved multimedia broadcast multicast services (e-mbms) architecture
EP2200367A1
