Method for handling multicast / broadcast service sessions
The use of temporary mobile group IDs in wireless communication systems addresses the challenge of managing MBS sessions, enabling seamless mobility and efficient resource allocation for multicast and broadcast services.
Patent Information
- Application Number
- KR1020227046440
- Authority / Receiving Office
- KR · KR
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2020-07-03
- Publication Date
- 2026-11-06
- Estimated Expiration
- 2040-07-03
AI Technical Summary
Existing wireless communication systems face challenges in establishing and managing multicast/broadcast service (MBS) sessions, particularly during UE movement, with unclear methods for session handling and resource allocation.
A wireless communication method involving the use of temporary mobile group IDs (TMGIs) to authorize and manage MBS sessions, including steps for session activation, resource allocation, and handover processes, utilizing point-to-point (PTP) and point-to-multipoint (PTM) wireless resources.
Enhances the management of MBS sessions by ensuring seamless UE mobility and efficient resource utilization, reducing packet loss during handovers, and optimizing the delivery of multicast and broadcast services.
Smart Images

Figure 112022142328716-PCT00001_ABST
Abstract
Description
Technology Field
[0001] This document is generally about wireless communication. Background Technology
[0002] Below, several technical terms are described to explain the background of the present disclosure.
[0003] Broadcast communication service: A communication service in which the same service and the same specific content data are provided simultaneously to all user equipment (UE) within a geographical area.
[0004] Multicast communication service: A communication service in which the same service and specific content data are simultaneously provided to a dedicated set of UEs (i.e., not all UEs within multicast coverage are authorized to receive data).
[0005] Multicast session: A session for delivering multicast communication services. Additionally, a multicast session is characterized by content transmitted in the multicast session, a list of UEs capable of receiving multicast communication services, and optionally a multicast area to distribute the multicast session.
[0006] Unicast session: A session for delivering communication services between a single UE and a data network.
[0007] Multicast / Broadcast Service (MBS) Session: Multicast session or broadcast session.
[0008] PTP (Point-to-Point) delivery method: A method in which a RAN (Random Access Network) node delivers separate copies of MBS data packets to individual UEs via wireless resources.
[0009] PTM (Point-to-Multipoint) delivery method: A method in which a RAN node delivers a single copy of an MBS data packet to a set of UEs via a wireless resource.
[0010] When MBS is provided to a UE, it is unclear how to establish the MBS session and how to handle the MBS session during UE movement.
[0011] This document relates to methods, systems, and devices for handling MBS sessions.
[0012] The present invention relates to a wireless communication method for use in a first wireless network node. The wireless communication method is:
[0013] A step of receiving a temporary mobile group ID (identity) associated with a multicast / broadcast service and a wireless terminal from a first session management function,
[0014] A step of receiving a request from a second session management function unit to activate a multicast / broadcast service session corresponding to the temporary mobile group ID, and
[0015] A step of transmitting a message containing information indicating the status of a multicast / broadcast service session at a first wireless network node to a first session management function unit.
[0016] Includes
[0017] Various embodiments can preferably implement the following features.
[0018] Preferably, the temporary mobile group ID indicates that the wireless terminal is authorized to receive data from a multicast / broadcast service corresponding to the temporary mobile group ID.
[0019] Preferably, information indicating the state of a multicast / broadcast service session corresponding to a temporary mobile group ID includes the temporary mobile group ID.
[0020] Preferably, the wireless communication method further includes the step of transmitting a handover request including a temporary mobile group identifier to a second wireless network node.
[0021] Preferably, the wireless communication method further includes the steps of receiving information of a forwarding tunnel from the second wireless network node, and transmitting data of a multicast / broadcast service to the second wireless network node through the forwarding tunnel.
[0022] Preferably, the wireless communication method further comprises the step of transmitting a termination marker to a second wireless network node after a timer has expired, wherein the timer is associated with transmitting data of a multicast / broadcast service to the second wireless network node through a forwarding tunnel.
[0023] Preferably, the wireless communication method further includes the step of receiving at least one wireless resource for transmitting data of a multicast / broadcast service from a second wireless network node.
[0024] Preferably, the wireless communication method further includes the step of transmitting at least one wireless resource of a multicast / broadcast service to a wireless terminal.
[0025] Preferably, at least one wireless resource includes at least one of a point-to-point wireless resource or a point-to-multipoint resource.
[0026] The present disclosure relates to a wireless communication method for use in a second wireless network node. The wireless communication method is:
[0027] Receiving a handover request including a temporary mobile group ID from a first wireless network node; and
[0028] The method includes the step of transmitting a message to the session management function unit that includes information indicating the status of a multicast / broadcast service session corresponding to a temporary mobile group ID at the second wireless network node.
[0029] Various embodiments can preferably implement the following features.
[0030] Preferably, information indicating the state of a multicast / broadcast service session corresponding to a temporary mobile group ID includes the temporary mobile group ID.
[0031] Preferably, the wireless communication method further comprises the steps of transmitting forwarding tunnel information to a first wireless network node, and receiving data of a multicast / broadcast service corresponding to the temporary mobile group ID through the forwarding tunnel from the first wireless network node.
[0032] Preferably, the wireless communication method further includes the steps of receiving a termination marker from a first wireless network node through a forwarding tunnel, and releasing the resources of the forwarding tunnel toward the first wireless network node.
[0033] Preferably, the wireless communication method further includes the step of transmitting at least one wireless resource to a first wireless network node for transmitting data for a multicast / broadcast service.
[0034] Preferably, at least one wireless resource includes at least one of a point-to-point wireless resource or a point-to-multipoint resource.
[0035] Preferably, the wireless communication method further includes the step of transmitting data of the multicast / broadcast service corresponding to the temporary mobile group ID to a wireless terminal through the at least one wireless resource.
[0036] The present disclosure relates to a wireless communication method for use in a session management function unit. The wireless communication method is:
[0037] A step of transmitting a temporary mobile group ID associated with a multicast / broadcast service and a wireless terminal to a wireless network node,
[0038] The step of receiving a message from a serving wireless network node of the wireless terminal, the message including information indicating the status of a multicast / broadcast service session corresponding to the temporary mobile group ID at the serving wireless network node, and
[0039] The method includes the step of transmitting a notification to at least one network function unit based on the status of a multicast / broadcast service session at the serving wireless network node.
[0040] Various embodiments can preferably implement the following features.
[0041] Preferably, the temporary mobile group ID indicates that the wireless terminal is authorized to receive data from a multicast / broadcast service corresponding to the temporary mobile group ID.
[0042] Preferably, at least one network function part includes at least one of a network exposure function part or an application function part.
[0043] Preferably, information indicating the state of a multicast / broadcast service session corresponding to a temporary mobile group ID includes the temporary mobile group ID.
[0044] Preferably, the notification includes at least one of the identification of the wireless terminal, a temporary mobile group ID, or information indicating the status of a multicast / broadcast service session at a serving wireless network node.
[0045] The present disclosure relates to a wireless communication method for use in a network function unit. The wireless communication method is,
[0046] A step of sending a request to activate a multicast / broadcast service session corresponding to a temporary mobile group ID to a session management function unit associated with a broadcast and multicast service center; and
[0047] It includes the step of receiving a notification associated with the status of a multicast / broadcast service session at a serving wireless network node of the wireless terminal from the serving session management function of the wireless terminal.
[0048] Various embodiments can preferably implement the following features.
[0049] Preferably, the network function part includes at least one of the network exposure function part or the application function part.
[0050] Preferably, the notification includes at least one of information indicating the identification of the wireless terminal, a temporary mobile group ID, or the status of a multicast / broadcast service session at the first wireless network node.
[0051] Preferably, the wireless communication method further includes the step of triggering at least one of a switch for using a unicast packet data unit session to modify a multicast / broadcast service session or transmit data of a multicast / broadcast service to a wireless terminal based on the notification, wherein the multicast / broadcast service corresponds to a temporary mobile group ID.
[0052] The present disclosure relates to a first wireless network node comprising a communication unit, wherein the communication unit is,
[0053] From the first session management function unit, receive a temporary mobile group ID associated with a multicast / broadcast service and a wireless terminal, and
[0054] A request to activate a multicast / broadcast service session corresponding to the temporary mobile group ID is received from the second session management function unit, and
[0055] The first session management function unit is configured to transmit a message containing information indicating the status of a multicast / broadcast service session at the first wireless network node.
[0056] Various embodiments can preferably implement the following features.
[0057] Preferably, the first wireless network node further includes a processor configured to perform any of the wireless communication methods described above.
[0058] The present disclosure relates to a second wireless network node comprising a communication unit, wherein the communication unit is,
[0059] Receive a handover request including a temporary mobile group ID from a first wireless network node, and
[0060] The session management function unit is configured to receive a message containing information indicating the status of a multicast / broadcast service session corresponding to a temporary mobile group ID at the second wireless network node.
[0061] Various embodiments can preferably implement the following features.
[0062] Preferably, the second wireless network node further includes a processor configured to perform any of the wireless communication methods described above.
[0063] The present disclosure relates to a wireless device comprising a communication unit, wherein the communication unit is,
[0064] Transmit a temporary mobile group ID associated with a multicast / broadcast service and a wireless terminal to a wireless network node, and
[0065] Receiving a message from a serving wireless network node of the above wireless terminal that includes information indicating the status of a multicast / broadcast service session corresponding to the temporary mobile group ID at the serving wireless network node, and
[0066] At least one network function is configured to transmit a notification based on the status of the multicast / broadcast service session at the serving wireless network node.
[0067] Various embodiments can preferably implement the following features.
[0068] Preferably, the wireless device further includes a processor configured to perform any of the wireless communication methods described above.
[0069] The present disclosure relates to a wireless device comprising a communication unit, wherein the communication unit is
[0070] Send a request to activate a multicast / broadcast service session corresponding to a temporary mobile group ID to the session management function unit associated with the broadcast and multicast service center, and
[0071] It is configured to receive a notification associated with the status of the multicast / broadcast service session at the serving wireless network node of the wireless terminal from the serving session management function of the wireless terminal.
[0072] Various embodiments can preferably implement the following features.
[0073] Preferably, the wireless device further includes a processor configured to perform any of the wireless communication methods described above.
[0074] The present disclosure relates to a computer program product in which computer-readable program media code is stored, and which, when executed by a processor, enables the processor to implement a wireless communication method mentioned in any of the aforementioned methods.
[0075] The exemplary embodiments disclosed herein relate to providing features that will become readily apparent by reference to the following description when taken together with the accompanying drawings. According to various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. However, while these embodiments are understood to be presented as examples rather than limitations, it will be apparent to those skilled in the art reading this disclosure that various modifications to the disclosed embodiments may be made while remaining within the scope of this disclosure.
[0076] Accordingly, the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Additionally, the specific order and / or hierarchy of steps in the method disclosed herein is merely an exemplary approach. Based on design preferences, the specific order or hierarchy of steps in the disclosed method or process may be rearranged while remaining within the scope of the present disclosure. Accordingly, those skilled in the art will understand that the method and technology disclosed herein present various steps or operations in a sample order and are not limited to the specific order or hierarchy presented unless otherwise specified. Brief explanation of the drawing
[0077] The above and other embodiments and their implementations are described in more detail in the drawings, detailed description, and claims. FIG. 1 illustrates a schematic diagram of a network according to an embodiment of the present disclosure. FIG. 2 illustrates an example of a schematic diagram of a wireless terminal according to an embodiment of the present disclosure. FIG. 3 illustrates an example of a schematic diagram of a wireless network node according to an embodiment of the present disclosure. FIG. 4 illustrates a schematic diagram of a process according to an embodiment of the present disclosure. FIG. 5 illustrates a schematic diagram of a process according to an embodiment of the present disclosure. FIGS. 6a and 6b are schematic diagrams of a process according to an embodiment of the present disclosure. FIGS. 7a and 7b are schematic diagrams of a process according to an embodiment of the present disclosure. FIGS. 8a and 8b are schematic diagrams of a process according to an embodiment of the present disclosure. FIG. 9 illustrates a schematic diagram of a process according to an embodiment of the present disclosure. FIG. 10 illustrates a schematic diagram of a process according to an embodiment of the present disclosure. FIG. 11 illustrates a flowchart of a process according to an embodiment of the present disclosure. FIG. 12 illustrates a flowchart of a process according to an embodiment of the present disclosure. FIG. 13 illustrates a flowchart of a process according to an embodiment of the present disclosure. FIG. 14 illustrates a flowchart of a process according to an embodiment of the present disclosure. Specific details for implementing the invention
[0078] In this specification, multicast / broadcast service is abbreviated as MBS.
[0079] In the present disclosure, multicast / broadcast service is abbreviated as MBS.
[0080] FIG. 1 illustrates a schematic diagram of a network according to an embodiment of the present disclosure. Network functions and components illustrated in FIG. 1 are further exemplified below.
[0081] 1) UE: User Equipment
[0082] 2) RAN: Wireless access network (node)
[0083] 3) AMF: Access and Mobility Management Unit
[0084] The AMF includes the following functions: registration management, connection management, reachability management, and mobility management. Additionally, the AMF performs access authentication and access authorization. The AMF is a non-access-stratum (NAS) security termination and relays a session management (SM) NAS between the UE and the SMF.
[0085] 4) SMF: Session Management Function
[0086] The SMF includes the following functions: session establishment, modification and release, UE Internet Protocol (IP) address allocation and management (including optional authorization functions), selection and control of UP functions, downlink data notification, etc.
[0087] 5) UPF: User Plane Function
[0088] UPF includes the following functions: anchor points for inter / intra-radio access technology (RAT) mobility, packet routing and forwarding, traffic usage reporting, quality of service (QoS) processing for the user plane, downlink packet buffering and downlink data notification triggering.
[0089] 6) NEF: Network Exposure Function
[0090] The NEF supports the exposure of network capabilities and events to application function parts (AFs). Third-party applications can call services provided by the network through the NEF, and the NEF performs authentication and authorization for third-party applications. The NEF also provides translation of information exchanged with AFs and information exchanged with internal network function parts.
[0091] 7) AF: Application Function Unit
[0092] The AF interacts with the 3GPP core network to provide services, for example, application impact on traffic routing, access to network exposure functions, and interaction with the policy framework for policy control. The AF may be trusted by the operator of the data network and may be allowed to interact directly with the relevant network function. An AF that is not allowed to directly access network functions must interact with the relevant network function using the external exposure framework through the NEF. In this disclosure, the AF is deployed in the data network.
[0093] 8) PCF: Policy Control Function Unit
[0094] PCF supports an integrated policy framework to manage network behavior. PCF provides access management policies to AMF, session management policies to SMF, or UE policies to UEs. PCF can access the Unified Data Repository (UDR) to obtain subscription information related to policy decisions.
[0095] 9) BMSC: Broadcast and Multicast Service Center
[0096] The BMSC is deployed to provide an MBS session to the AF. The BMSC can be separated (e.g., split) into BMSC-C, which is the control plane functional part of the BMSC, and BMSC-U, which is the user plane functional part of the BMSC. In an embodiment, BMSC-C and SMF (e.g., SMF2 shown in FIG. 1) can be deployed together, and BMSC-U and UPF (e.g., UPF2 in FIG. 1) can be deployed together. In an embodiment, BMSC-C can also be deployed together with NEF.
[0097] In FIG. 1, the numbers following the names of specific network functions are used to distinguish network functions of the same type. More specifically, AMF1, PCF1, SMF1, and UPF1 are used for unicast packet data unit (PDU) sessions. Additionally, AMF2, PCF2, SMF2, and UPF2 are used for MBS sessions that can be shared by a group of UEs. In the embodiment, RAN1 and RAN2 provide both unicast and MBS services to UEs simultaneously. For MBS sessions, a single N3 tunnel between RAN2 and UPF2 can be shared by a group of UEs.
[0098] FIG. 2 relates to a schematic diagram of a wireless terminal (20) according to an embodiment of the present disclosure. The wireless terminal (20) may be a user device (UE), a mobile phone, a laptop, a tablet computer, an e-book or portable computer system, but is not limited thereto. The wireless terminal (20) may include a processor (200), such as a microprocessor or an Application Specific Integrated Circuit (ASIC), a storage unit (210), and a communication unit (220). The storage unit (210) may be any data storage device that stores program code (212) accessed and executed by the processor (200). Embodiments of the storage unit (212) include, but are not limited to, a SIM (subscriber identity module), ROM (read-only memory), flash memory, RAM (random-access memory), a hard disk, and an optical data storage device. The communication unit (220) may be a transceiver and is used to transmit and receive signals (e.g., messages or packets) according to the processing result of the processor (200). In an embodiment, the communication unit (220) transmits and receives signals through at least one antenna (222) shown in FIG. 2.
[0099] In an embodiment, the storage unit (210) and the program code (212) may be omitted, and the processor (200) may include a storage unit in which the program code is stored.
[0100] The processor (200) can implement any one of the steps of the illustrated embodiment for the wireless terminal (20) by, for example, executing program code (212).
[0101] The communication unit (220) may be a transceiver. Alternatively, the communication unit (220) may be a combination of a transmitting unit and a receiving unit configured to transmit and receive signals to and from a wireless network node (e.g., a base station), respectively.
[0102] FIG. 3 relates to a schematic diagram of a wireless network node (30) according to an embodiment of the present disclosure. The wireless network node (30) may be a wireless device, a satellite, a base station (BS), a network entity, a Mobility Management Entity (MME), a Serving Gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), a radio access network (RAN), a next generation RAN (NG-RAN), a data network, a core network, or a Radio Network Controller (RNC), but is not limited thereto. Additionally, the wireless network node (30) may include (e.g., perform, implement, or realize) at least one network function such as an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a User Plane Function (UPF), a Policy Control Function (PCF), an Application Function (AF), a Broadcast and Multicast Service Center (BMSC), a Network Exposure Function (NEF), etc. A wireless network node (30) may include a processor (300), such as a microprocessor or ASIC, a storage unit (310), and a communication unit (320). The storage unit (310) may be any data storage device that stores program code (312) accessed and executed by the processor (300). Examples of the storage unit (312) include, but are not limited to, SIM, ROM, flash memory, RAM, hard disk, and optical data storage devices. The communication unit (320) may be a transceiver and is used to transmit and receive signals (e.g., messages or packets) according to the processing results of the processor (300). In one example, the communication unit (320) transmits and receives signals through at least one antenna (322) shown in FIG. 3.
[0103] In the embodiment, the storage unit (310) and the program code (312) may be omitted. The processor (300) may include a storage unit in which the program code is stored.
[0104] The processor (300) can implement any steps described in the exemplary embodiment for the wireless network node (30) by, for example, executing program code (312).
[0105] The communication unit (320) may be a transceiver. Alternatively, the communication unit (320) may be a combination of a transmitting unit and a receiving unit configured to transmit and receive signals to and from a wireless terminal (e.g., user equipment), respectively.
[0106] FIG. 4 illustrates a schematic diagram of a process according to an embodiment of the present disclosure. Note that PCF1, BMSC-C, NEF, and AF may be those illustrated in FIG. 1. In FIG. 4, AF requests the configuration of the MBS from the BMSC and provides the configuration of the MBS to the network. For example, the configuration of the MBS includes a Temporal Mobile Group ID (TMGI) and / or an associated Internet Protocol (IP) multicast address. The TMGI is used to uniquely identify the MBS at the wireless interface. Additionally, the IP multicast address is used to identify the MBS at the IP layer.
[0107] More specifically, when AF requests one or more TMGIs (i.e., at least one TMGI) from BMSC (e.g., BMSC-C shown in FIG. 4), AF transmits a TMGI request (message) to NEF (step 401). In the embodiment, the TMGI request (message) includes (e.g., indicates) the number of requested TMGIs.
[0108] In step 402, the NEF authorizes whether the AF is allowed to request the TMGI. In this embodiment, the NEF determines that the AF is allowed to request the TMGI and forwards the TMGI request to the BMSC (e.g., BMSC-C shown in FIG. 4).
[0109] In step 403, BMSC-C allocates a TMGI set, and a multicast IP address is assigned to each TMGI. Additionally, BMSC-C determines the expiration time of the TMGI. Next, BMSC-C returns the TMGI set and the associated multicast IP address(s) to NEF in the TMGI response.
[0110] In step 404, the NEF forwards the TMGI response to the AF (e.g., transmits it).
[0111] In step 405, the AF provides the MBS to the network. In an embodiment, the AF sends an AF request to the NEF (e.g., transmits), wherein the AF request includes application information, single network slice selection support information (S-NSSAI), data network name (DNN), TMGI, IP multicast address, and external group ID. The external group ID is configured to identify a group of UE(s) receiving the MBS. Additionally, the AF request may also include a notification address to receive RAN node information from the SMF. In an embodiment, the RAN node information may include TMGI. In an embodiment, the RAN node information indicates the status of the MBS session of the MBS in the UE's serving RAN. For example, the RAN node information may indicate whether the UE's serving RAN supports the MBS and / or whether the UE's serving RAN has an MBS session context of TMGI and / or whether an MBS session corresponding to TMGI is active in the UE's serving RAN.
[0112] In step 406, the NEF maps the external group ID to the internal group ID. Additionally, the NEF determines a self-notification address to receive RAN node information. The NEF stores the internal group ID and the AF request information in the UDR.
[0113] In step 407, NEF responds to AF using an acknowledgment (ACK) message for the AF request.
[0114] In step 408, when PCF1 subscribes to information about an AF request from UDR, UDR sends a notification (message) to PCF1 containing the internal group ID and information about the AF request. In the embodiment, PCF1 stores the AF request information.
[0115] FIG. 5 illustrates a schematic diagram of a process according to an embodiment of the present disclosure, wherein UE, AMF1, SMF1, UPF1, PCF1, NEF, and AF may be those shown in FIG. 1. Note that the RAN shown in FIG. 5 may be either RAN1 or RAN2 shown in FIG. 1. An embodiment shown in FIG. 5 illustrates a method for a UE to join an MBS. In the process shown in FIG. 5, the network must authorize whether the UE can join the MBS. In an embodiment, the process shown in FIG. 5 may be performed before the corresponding MBS session starts.
[0116] More specifically, the UE can obtain the IP multicast address of the MBS through application layer information exchange. When the UE wishes to join the MBS, the UE sends a message to the target IP multicast address identifying the MBS. For example, the UE checks the UE policy to determine the S-NSSAI and DNN associated with this IP multicast address and searches for existing PDU sessions with the associated S-NSSAI and DNN. If no PDU session is found, the UE establishes a PDU session with the associated S-NSSAI and DNN. During the PDU session establishment procedure, SMF1 establishes a session management (SM) policy association with PCF1 and provides the UE's internal group ID to PCF1 (step 501).
[0117] In this embodiment, there are two ways in which the UE transmits a message associated with joining an MBS session as described in step 502a (i.e., steps 502a.1 and 502a.2) and step 502b. That is, the UE can perform either step 502a (i.e., steps 502a.1 and 502a.2) or step 502b.
[0118] In step 502a.1, the UE can send an IGMP (internet group management protocol) join message to UPF1 through the user plane of the PDU session associated with the MBS.
[0119] In step 502a.2, UPF1 detects an IGMP subscribe message and reports the detected IP multicast address from the N4 report to SMF1.
[0120] In step 502b, the UE may send a NAS PDU session modification request (including an IP multicast address) to SMF1 via AMF1 to join the MBS.
[0121] In step 503, based on a NAS message (i.e., a NAS PDU session modification request) or an N4 report, SMF1 sends an SM policy association update request to PCF1, where the SM policy association update request includes an IP multicast address.
[0122] In step 504, PCF1 already has information regarding the internal group ID and the corresponding IP multicast address. Accordingly, PCF1 checks whether the UE internal group ID matches the internal group ID of the IP multicast address received from SMF1. If they match, the UE is authorized to join the MBS, and PCF1 returns an SM policy association update response (message) to SMF1. Note that the SM policy association update response (message) includes the IP multicast address and the associated TMGI. In the embodiment, the SM policy association update response (message) may also include the notification address of an NEF configured to receive RAN node information.
[0123] In step 505, SMF1 stores the authorized IP multicast address and the associated TMGI in the PDU session context. Then, SMF1 sends Namf_Communication_N1N2MessageTransfer to AMF1, which includes an N1 message container (e.g., a PDU session modification command) containing the authorized TMGI and IP multicast address, and an N2 message container that may contain the authorized TMGI.
[0124] In step 506, AMF1 sends an N2 PDU session request to RAN along with the N1 message container and the N2 message container.
[0125] In step 507, the RAN sends an N1 message container to the UE using AN specific signaling. Accordingly, the UE acknowledges that it is allowed to receive the MBS identified by the received TMGI.
[0126] In step 508, if the RAN supports MBS, the RAN also stores the TMGI in the UE context. Thus, the RAN knows that the UE is allowed to receive MBS. In this embodiment, the RAN returns an N2 PDU session response to AMF1. The N2 PDU session response may include RAN node information. In this embodiment, the RAN node information may include the TMGI. In this embodiment, the RAN node information may be configured to indicate whether the UE's serving RAN (e.g., the RAN shown in FIG. 5) has the TMGI's MBS session context (e.g., the state of the TMGI's MBS session in the RAN).
[0127] In step 509, AMF1 sends an Nsmf_PDUSession_UpdateSMContext request to SMF1, wherein the Nsmf_PDUSession_UpdateSMContext request includes an N2 PDU session response message. In an embodiment, the N2 PDU session response message may include RAN node information received from the RAN. In an embodiment, SMF1 determines that the RAN does not support MBS when the SMF does not receive RAN node information from the RAN.
[0128] In step 510, SMF1 sends the Nsmf_PDUSession_UpdateSMContext response to AMF1.
[0129] In step 511, SMF1 transmits a notification to NEF. In an embodiment, the notification includes the UE ID of the UE and RAN node information received from the RAN.
[0130] In step 512, the NEF transmits (e.g., forwards) the notification to the AF. In an embodiment, based on the RAN node information in the notification, the AF acknowledges that the UE has joined an MBS session and whether the UE's serving RAN supports MBS and / or whether the UE's serving RAN has an MBS session context and / or whether an MBS session corresponding to a TMGI is active in the UE's serving RAN. Based on the RAN node information in the notification, the AF decides to deliver the MBS to the UE using a unicast PDU session or an MBS session.
[0131] After the process illustrated in Fig. 5 is completed, the UE is authorized to receive MBS identified by the TMGI associated with the IP multicast address. When the UE enters an idle state (e.g., RRC IDLE), the UE context within the RAN may be released. When the UE enters a connected state (e.g., RRC CONNECTED) and the PDU session is activated, the SMF again provides the authorized TMGI to the RAN.
[0132] FIGS. 6a and 6b illustrate schematic diagrams of a process according to an embodiment of the present disclosure. The process illustrated in FIGS. 6a and 6b can be used to establish an MBS session. In this embodiment, SMF2 is placed together with BMSC-C and UPF2 is placed together with BMSC-U (e.g., SMF2, BMSC-C, UPF2, and BMSC-U illustrated in FIG. 1). Alternatively, SMF2 and BMSC-C may be placed separately, or UPF2 and BMSC-U may be placed separately. In the embodiment, AMF2, PCF2, NEF, and AF may be those illustrated in FIG. 1. Additionally, the RAN illustrated in FIGS. 6a and 6b may be RAN1 or RAN2 illustrated in FIG. 1. After the process illustrated in FIGS. 6a and 6b is completed, the RAN can receive MBS downlink data through the shared N3 tunnel of the MBS session.
[0133] More specifically, AF calls a session start (e.g., NEF service operation) to send an AF request (step 601) (see FIG. 6a). In an embodiment, the content of the service start (i.e., AF request) includes at least one of an AF transaction ID, a requested S-NSSAI (Single Network Slicing Selection Auxiliary), a requested DNN (Date Network Name), or a requested SSC (Session and Service Continuity) mode. The parameters included in the AF request are used to establish (e.g., activate) an MBS session. In an embodiment, the AF request may further include at least one of a TMGI, an IP multicast address, and a target area of the MBS session.
[0134] In step 602, the NEF authorizes whether the AF is allowed to start (e.g., activate) an MBS session. In an embodiment, the NEF converts the target area into a tracking area identity (TAI) list and forwards (e.g., transmits) the session start (i.e., AF request) to the SMF2. In this embodiment, the BSMC-C is placed with the SMF2.
[0135] In step 603, SMF2 creates an MBS session context associated with TMGI. Based on the local configuration, SMF2 assigns a PDU session ID to the MBS session. Additionally, SMF2 selects PCF2 to establish an SM policy association. SMF2 also sends the TMGI and IP multicast addresses to PCF2.
[0136] In step 604, SMF2 selects a UPF2 that supports an MBS session and establishes an N4 association with the selected UPF2. In this embodiment, SMF2 transmits a forwarding rule containing an IP multicast IP address to UPF2, and UPF2 can forward downlink MBS traffic (e.g., MBS downlink data) through a shared N3 tunnel toward the RAN. In one embodiment, information about the shared N3 tunnel is assigned by UPF2 and provided to SMF2.
[0137] In step 605, SMF2 discovers (e.g., determines, selects) AMF2 based on the TAI list received in step 602 and transmits Namf_Communication_N1N2MessageTransfer to AMF2. In the embodiment, Namf_Communication_N1N2MessageTransfer includes parameters such as a PDU session ID, a TAI list, and N2 SM information (e.g., PDU session ID, TMGI, QFI(s), QoS profile(s), N3 tunnel information of UPF2, S-NSSAI, etc.). Upon receiving Namf_Communication_N1N2MessageTransfer, AMF2 transmits a response to SMF2.
[0138] In an embodiment, SMF2 may select multiple AMFs (e.g., multiple AMF2s) based on a TAI list. In this case, SMF2 performs step 605 with each selected AMF.
[0139] In step 606, AMF2 selects a RAN according to the TAI list received in step 605 and transmits an N2 PDU session request to the RAN. In the embodiment, the N2 PDU session request carries an AMF NGAP (next-generation application protocol) UE ID and N2 SM information received from SMF2.
[0140] In an embodiment, the AMF may select multiple RAN nodes (e.g., multiple RANs) based on a TAI list. In this case, the AMF performs step 606 with each selected RAN node.
[0141] In step 607, the RAN creates an MBS session context associated with the TMGI and may issue an AN specific resource reservation for the MBS session. In an embodiment, the RAN may begin broadcasting the TMGI through the Uu interface. By reading the TMGI from the broadcast information, the UE determines whether it can receive the MBS associated with the TMGI.
[0142] In an embodiment, the RAN may issue an AN-specific resource reservation in a subsequent step. For example, if there are no UEs interested in these MBS under a cell, the RAN does not need to allocate MBS resources for these MBS. In this situation, when the RAN receives a downlink packet through the N3 tunnel, the RAN may discard the received downlink packet if no radio resources are reserved.
[0143] In an embodiment, the RAN transmits an N2 PDU session response to AMF2. In an embodiment, the N2 PDU session response includes a RAN NGAP UE ID. AMF2 uses the RAN NGAP UE ID for subsequent N2 messages transmitted to the RAN. In an embodiment, the N2 PDU session response may also include parameters such as a PDU session ID, cause, and a list of N2 SM information (e.g., including PDU session ID, N3 tunnel information, accepted / rejected QFI(s) (quality-of-service (QoS) flow ID, etc.).
[0144] In step 608, for each N2 PDU session response from RAN, AMF2 sends an Nsmf_PDUSession_UpdateSMContext request (e.g., including SMF SM context ID and N2 SM information) to SMF.
[0145] In step 609, for each Nsmf_PDUSession_UpdateSMContext request received from AMF2, SMF2 initiates an N4 session modification procedure with UPF2 to provide N3 tunnel information received from the RAN. Then, UPF2 associates the N3 tunnel information provided to the RAN with the MBS session.
[0146] In an embodiment, if there are multiple RANs associated with an MBS session, UPF2 replicates the MBS downlink traffic and forwards it to each of the RAN nodes through the corresponding N3 tunnel.
[0147] In an embodiment, if UPF2 with BMSC-U deployed does not assign an IP address and port number for an MBS session, UPF2 may also assign a UPF+BMSC-U IP address and port number for an MBS session and provide them to SMF2.
[0148] In step 610, SMF2 sends the Nsmf_PDUSession_UpdateSMContext response to AMF2.
[0149] In step 611, SMF2 returns a session start ACK to NEF. In the embodiment, the session start ACK includes a TMGI, a UPF+BMSC-U IP address, and a port number.
[0150] In step 612, NEF sends a session start ACK to AF, where the session start ACK includes TMGI, UPF+BMSC-U IP address and port number.
[0151] In step 613, referring to FIG. 6b, AF transmits downlink traffic (e.g., MBS downlink data) toward the UPF+BMSC-U IP address and port number. In this embodiment, UPF2 with BMSC-U generates MBS downlink traffic (e.g., using an IP multicast address as the target IP address) and forwards the MBS downlink data toward the RAN through the shared N3 tunnel of the MBS session.
[0152] In step 614, for each UE authorized to receive the TMGI's MBS (i.e., the TMGI within the UE's PDU session context), the RAN transmits a notification (e.g., a message containing RAN node information) to the UE's serving AMF1 (i.e., AMF1 is the UE's serving AMF). In the embodiment, the RAN node information includes the TMGI. In the embodiment, the RAN node information indicates that the MBS session is active and / or that the UE can receive the TMGI's MBS through the MBS session (e.g., the state of the MBS session in the RAN).
[0153] In step 615, AMF1 forwards the notification to SMF1.
[0154] In step 616, SMF1 forwards the notification to NEF.
[0155] In step 617, the NEF forwards the notification to the AF. As a result, the AF may decide to stop using the unicast PDU session to deliver the MBS (data) to the UE. That is, the AF may decide to start using the MBS session to deliver the MBS (i.e., MBS downlink data) to the UE.
[0156] FIGS. 7a and 7b illustrate schematic diagrams of a process according to an embodiment of the present disclosure. The process illustrated in FIGS. 7a and 7b can be used to move a UE to a new RAN node (e.g., handover) via an Xn-based handover procedure. Note that the UE, RAN1, RAN2, AMF1, SMF1, UPF1, and UPF2 illustrated in FIGS. 7a and 7b may be those illustrated in FIG. 1. In this embodiment, a forwarding tunnel for the MBS session may be established to reduce packet loss during the handover.
[0157] More specifically, prior to the handover, the UE receives MBS (e.g., MBS downlink data) through an MBS session via RAN1 (step 701) (see FIG. 7a).
[0158] In step 702, based on radio measurements, RAN1 may initiate an Xn-based handover toward RAN2 by transmitting a handover request (message). In an embodiment, the handover request may include a PDU session context that is the handover target, wherein the PDU session context may include a TMGI authorized for the UE to receive the associated MBS. When the MBS session is active for the MBS, based on the QoS profile(s) of the MBS session, the handover request message may include information indicating whether data forwarding is required to reduce packet loss for the MBS session.
[0159] In step 703, RAN2 reserves radio resource(s) for the QoS profile(s) of the PDU session received from RAN1. If RAN2 supports MBS and data forwarding for the MBS session is required, RAN2 allocates a data forwarding tunnel for the MBS session. When the MBS session is activated in RAN2, RAN2 may also allocate PTP radio resources to the MBS session.
[0160] In this embodiment, RAN2 returns a handover request ACK to RAN1. In this embodiment, the handover request ACK includes information about all radio resources successfully reserved for the UE in RAN2. Alternatively or additionally, the handover request ACK may include information about the data forwarding tunnel and PTP radio resources of the MBS session. In an embodiment where the MBS session is active in RAN2, the handover request ACK may also include the PTM radio resources of the MBS session identified by TMGI.
[0161] In step 704, RAN1 transmits a handover command to the UE. In an embodiment, the handover command includes radio resources received from RAN2.
[0162] In step 705, when a data forwarding tunnel assigned to an MBS session is received, RAN1 may begin forwarding MBS downlink data toward RAN2 through the data forwarding tunnel, and RAN2 may begin buffering the MBS downlink data received through the forwarding tunnel. In an embodiment, RAN1 may start a data forwarding timer.
[0163] In step 706, the UE accesses RAN2 based on the radio resources received from RAN1 and transmits a handover acknowledgment to RAN2.
[0164] In step 707, when a PTP radio resource is reserved for an MBS session in step 703, RAN2 begins delivering buffered downlink MBS data to the UE. In an embodiment, the UE receives a reserved PTM from RAN1 without receiving the reserved PTP radio resource. In this case, the UE can receive MBS downlink data via a PTM radio resource from RAN2.
[0165] In step 708, RAN2 transmits a route switching request containing N2 SM information to AMF1. In an embodiment, the N2 SM information includes N3 user plane information of the PDU session. In an embodiment of RAN2 receiving TMGI from RAN1, the route switching request may include RAN node information. In an embodiment, the RAN node information includes TMGI. In an embodiment, the RAN node information indicates whether an MBS session is active in RAN2 (e.g., the status of an MBS session in the serving RAN). In an embodiment, if RAN node information is not received from the RAN2 node, SMF1 detects (e.g., determines) that RAN2 does not support MBS, and then notifies NEF and AF that the UE's serving RAN (i.e., RAN2) does not support MBS.
[0166] In step 709, AMF1 sends an Nsmf_UpdateSMContext request to SMF1.
[0167] In step 710, SMF1 sends an N4 session modification to UPF1 to update the N3 user plane information of the RAN2 node (see Fig. 7b).
[0168] In step 711, SMF1 returns the Nsmf_PDUSession_UpdateSMContext response to AMF1.
[0169] In step 712, AMF returns a path switching response to RAN1.
[0170] In step 713, RAN2 confirms the success of the handover by sending a resource release message to RAN1.
[0171] In step 714, after the handover, RAN2 may send a message to AMF1 to indicate whether the MBS session is active in RAN2 when the state of the MBS session changes. In an embodiment, AMF1 may further forward the message to SMF1 (not shown in FIG. 7b).
[0172] In step 715, when the timer of step 705 is set and expires, RAN1 transmits a termination marker to RAN2 through the data forwarding tunnel. In this embodiment, the termination marker may trigger the release of resources allocated to RAN1 (e.g., the data forwarding tunnel).
[0173] In step 716, after receiving the termination marker, RAN2 releases the forwarding tunnel and begins transmitting the received MBS downlink data through the shared N3 tunnel of the MBS session and the PTP resource. In the embodiment, RAN2 may switch to using the PTM resource to transmit the MBS (data of the MBS).
[0174] In an embodiment, RAN1 may not support MBS, and SMF1 may not receive RAN node information from RAN2 after Xn handover. In this embodiment, after Xn handover, SMF1 initiates a PDU session modification procedure with RAN2, and TMGI is transmitted to RAN2 during the PDU session modification procedure. If RAN2 supports MBS, RAN2 returns RAN node information of a corresponding response message to SMF1. Based on the RAN node information, SMF1 detects (e.g., determines) whether RAN2 supports MBS and / or whether an MBS session is active in RAN2. In an embodiment, SMF1 may additionally transmit a notification to the NEF and / or AF to indicate the status of the MBS session in RAN2, for example.
[0175] FIGS. 8a and 8b illustrate schematic diagrams of a process according to an embodiment of the present disclosure. Note that UE, RAN1, RAN2, AMF1, SMF1, UPF1, and UPF2 may be those shown in FIG. 1. The process shown in FIGS. 8a and 8b may be used to handle an MBS session when a corresponding UE moves to a new RAN node via an N2-based handover procedure. In this embodiment, a forwarding tunnel for the MBS session is established directly between RAN1 and RAN2 to reduce packet loss during the handover. In the embodiment, a data forwarding tunnel may be established through one or two UPFs.
[0176] More specifically, the UE receives MBS (e.g., MBS downlink data) through an MBS session via RAN1 (step 801) (see FIG. 8a).
[0177] In step 802, based on radio measurements, RAN1 transmits a handover request message to AMF1 that includes handover target information and N2 SM information. In an embodiment, the N2 SM information includes a PDU session context that is the handover target. In an embodiment, the PDU session context includes a TMGI authorized for the UE to receive the associated MBS. In an embodiment, based on the QoS profile(s) of the MBS session, the N2 SM information may also include information indicating whether data forwarding is required to reduce packet loss for the MBS session.
[0178] In step 803, AMF1 sends an Nsmf_PDUSession_UpdateSMContext request to SMF1. In the embodiment, this request includes target information and N2 SM information received from RAN1.
[0179] In step 804, SMF1 checks (e.g., detects or determines) whether a handover (e.g., N2 handover) for the indicated PDU session is acceptable based on the target information. If the handover is acceptable, SMF1 returns an Nsmf_PDUSession_UpdateSMContext response (e.g., containing N2 SM information) to AMF1. In the embodiment, the N2 SM information includes the PDU session context that is the handover target, and the TMGI authorized for the UE to receive the associated MBS is included in the PDU session context. In the embodiment, the N2 SM information may also include information indicating whether data forwarding is required to reduce packet loss of the MBS session.
[0180] In step 805, AMF1 sends a handover request (e.g., including N2 SM information) to RAN2. Note that the N2 SM information is information received from SMF1.
[0181] In step 806, RAN2 reserves radio resource(s) for the QoS profile(s) of the PDU session received in step 805. In an embodiment, RAN2 allocates RAN N3 tunnel information for each accepted PDU session. In an embodiment, if RAN2 supports MBS and data forwarding is required for the MBS session, RAN2 allocates a data forwarding tunnel to the MBS session. When the MBS session is activated in RAN2, RAN2 also allocates PTP radio resources based on the QoS profile(s) of the MBS session.
[0182] In FIG. 8a, RAN2 returns a handover request ACK (e.g., including target-to-source transparent container and / or N2 SM information) to AMF1. In an embodiment, the target-to-source transparent container includes information on all radio resource(s) successfully reserved for the UE in RAN2. In an embodiment where the MBS session is active in RAN2, the target-to-source transparent container may also include PTP radio resources and / or PTM radio resources for the MBS session identified by TMGI. In an embodiment, the N2 SM information includes RAN N3 tunnel information for the PDU session. In an embodiment, the N2 SM information may include RAN node information and information on the data forwarding tunnel assigned to the MBS session in RAN2. In an embodiment, the RAN node information includes TMGI. In an embodiment, the RAN node information indicates whether the MBS session is active in RAN2 (e.g., the status of the MBS session in RAN2).
[0183] In step 807, AMF1 sends an Nsmf_PDUSession_UpdateSMContext request (e.g., including N2 SM information) to SMF1. In an embodiment, SMF1 may further send a notification (e.g., a message) based on RAN node information to NEF and / or AF. In an embodiment, SMF detects (e.g., determines) that the target RAN2 does not support MBS when it does not receive RAN node information from RAN2.
[0184] In step 808, SMF1 returns an Nsmf_PDUSession_UpdateSMContext response (e.g., containing N2 SM information). In an embodiment, the N2 SM information may include information about the data forwarding tunnel of the MBS session in RAN2.
[0185] In step 809, AMF1 sends a handover command (e.g., including target-to-source transparent container and / or N2 SM information) to RAN1.
[0186] In step 810, RAN1 transmits a handover command to the UE. In an embodiment, the handover command includes radio resources received from RAN2 by a target-to-source transparent container.
[0187] In step 811, if data forwarding for the MBS session is required, RAN1 forwards the MBS downlink data received from UPF2 to RAN2 through the data forwarding tunnel, and RAN2 begins buffering the MBS downlink data received through the data forwarding tunnel. In an embodiment, RAN1 may start a timer associated with forwarding the MBS downlink data.
[0188] In step 812, based on the radio resource(s) received from RAN1, the UE accesses RAN2 and sends a handover acknowledgment to RAN2 (see FIG. 8b).
[0189] In step 813, if a PTP radio resource is reserved, RAN2 delivers buffered MBS downlink data to the UE. In an embodiment, there is no reserved PTP radio resource and the UE receives a PTM radio resource from RAN1 in step 810, and the UE receives MBS downlink data from RAN2 via the PTM radio resource.
[0190] In step 814, RAN2 sends a handover notification to AMF1 (e.g., toward AMF1).
[0191] In step 815, AMF1 sends an Nsmf_PDUSession_UpdateSMContext request to SMF1 (e.g., toward SMF1) to notify that the handover is complete.
[0192] In step 816, SMF1 sends an N4 session modification to UPF1 to update the RAN N3 tunnel information in UPF1.
[0193] In step 817, SMF1 returns the Nsmf_PDUSession_UpdateSMContext response to AMF1.
[0194] In step 818, AMF sends a release resource (message) to RAN1 to confirm a successful handover.
[0195] In step 819, after the handover, the state of the MBS session changes, and RAN2 sends a notification to AMF1 (e.g., a message containing RAN node information). In an embodiment, the RAN node information includes TMGI. In an embodiment, the RAN node information indicates whether the MBS session is active on RAN2 (e.g., the state of the MBS session on RAN2). In an embodiment, AMF1 further forwards the notification to SMF1.
[0196] In step 820, when the timer in step 811 is set and expires, RAN1 transmits a termination marker to RAN2 through the data forwarding tunnel. In the embodiment, the termination marker is configured to trigger the release of resources allocated to RAN1.
[0197] In step 821, after receiving the termination marker, RAN2 releases the data forwarding tunnel and begins transmitting the MBS downlink data received through the shared N3 tunnel of the MBS session via the PTP resource. In the embodiment, RAN2 may switch to using the PTM resource to transmit the MBS (i.e., MBS downlink data).
[0198] FIG. 9 illustrates a schematic diagram of a process according to an embodiment of the present disclosure. Note that UE, RAN1, RAN2, SMF1, UPF1, SMF2, UPF2, NEF, and AF may be those shown in FIG. 1. The process shown in FIG. 9 may be used to handle an MBS session when a UE moves to a new RAN (e.g., RAN2) via an Xn / N2-based handover procedure. In this embodiment, SMF1 detects (e.g., determines) that the target RAN (e.g., RAN2) supports MBS and that the TMGI's MBS session is not active in the target RAN. In this case, SMF1 notifies NEF / AF, and AF can activate the MBS session in RAN2.
[0199] Specifically, RAN1 performs an Xn-based handover or an N2-based handover to move the UE to RAN2 (step 901). In the embodiment, RAN2 supports an MBS identified by TMGI and does not have the TMGI's MBS session context. In the embodiment, MBS downlink data of the MBS can be forwarded from RAN1 to RAN2, and RAN2 buffers the forwarded MBS downlink data. Because RAN2 does not have a corresponding MBS session context, RAN2 cannot allocate the MBS session's PTP resources and / or PTM resources to RAN1.
[0200] In step 902, during an XN / N2-based handover, SMF1 detects (e.g., determines) that the serving RAN (i.e., RAN2) supports MBS and that the TMGI's MBS session is not active on RAN2. In this situation, SMF1 transmits a notification (message) to the NEF. In an embodiment, the notification includes at least one of the UE ID, TMGI, or RAN node information. In an embodiment, the RAN node information refers to (e.g., includes) TMGI. In an embodiment, the RAN node information indicates that the serving RAN (i.e., RAN2) supports MBS and / or that the TMGI's MBS session is not active (e.g., the status of the MBS session on the serving RAN).
[0201] In step 903, NEF sends a notification (message) to AF.
[0202] In step 904, AF determines to activate an MBS session in RAN2 based on the received notification. In this embodiment, AF determines a new MBS area covering RAN2 and sends a session modification request (e.g., including the new MBS area) to NEF.
[0203] In step 905, NEF sends a session modification request to SMF2 to activate the MBS session through the new MBS area.
[0204] In step 906, SMF2 initiates an MBS session modification procedure to activate an MBS session through a new MBS area. During the MBS session modification procedure, RAN2 allocates PTP radio resources for the MBS session to the UE.
[0205] In step 907, SMF2 sends a session modification ACK to NEF after the MBS session modification procedure is successful.
[0206] In step 908, NEF sends a session modification ACK to AF.
[0207] In step 909, after the MBS session is activated in RAN2, RAN2 transmits the buffered MBS downlink data received from RAN1 via the PTP radio resource. Additionally, RAN2 begins receiving MBS downlink data from UPF2 via the shared N3 tunnel of the MBS session.
[0208] In step 910, after the timer associated with RAN1 forwarding MBS downlink data to RAN2 expires, RAN1 sends a termination marker to RAN2 through the data forwarding tunnel forwarding MBS downlink data. In the embodiment, the termination marker is configured to trigger the release of resources allocated to RAN1.
[0209] In step 911, after RAN2 receives a termination marker, RAN2 releases the data forwarding tunnel and transmits the MBS downlink data received through the shared N3 tunnel of the MBS session via the PTP radio resource. In the embodiment, RAN2 may switch to using the PTM radio resource to transmit the MBS (i.e., MBS downlink data).
[0210] FIG. 10 illustrates a schematic diagram of a process according to an embodiment of the present disclosure. Note that the UE, RAN1, RAN2, SMF1, UPF1, PCF, NEF, and AF shown in FIG. 10 may be those shown in FIG. 1. The process shown in FIG. 1 may be used to handle an MBS session when a UE moves to a new RAN node (e.g., RAN2) via an Xn / N2-based handover procedure. In this embodiment, SMF1 detects that the target RAN2 does not support MBS, and SMF1 notifies NEF / AF so that AF can deliver the MBS to the UE using a unicast PDU session.
[0211] Specifically, RAN1 performs an Xn-based handover or an N2-based handover associated with moving the UE to RAN2 (step 1001).
[0212] In step 1002, during an Xn / N2-based handover, SMF1 detects (e.g., determines) that the target RAN (i.e., RAN2) does not support MBS. In this situation, SMF1 transmits a notification (message) to the NEF. In an embodiment, the notification includes at least one of a UE ID, TMGI, or RAN node information. In an embodiment, the RAN node information indicates that the target RAN (i.e., RAN2) does not support MBS (e.g., the state of an MBS session corresponding to the MBS identified by the TMGI in RAN2).
[0213] In step 1003, NEF additionally sends a notification to AF.
[0214] In step 1004, the AF decides to use a unicast PDU session rather than an MBS session to deliver MBS (i.e., MBS downlink data) based on the information of the received notification. In this embodiment, the AF sends an AF request having a new service requirement to the NEF to request a modification of the PDU session.
[0215] In step 1005, NEF forwards the AF request to PCF.
[0216] In step 1006, PCF initiates an SM association update procedure with SMF1 to modify the PDU session.
[0217] In step 1007, SMF1 initiates a PDU session modification to add a new QoS flow and / or modify an existing QoS flow within the PDU session.
[0218] In step 1008, after the PDU session modification is successful, SMF1 sends an SM associated update ACK to PCF.
[0219] In step 1009, PCF sends an AF request ACK to NEF.
[0220] In step 1010, NEF sends an AF request ACK to AF.
[0221] In step 1011, AF uses a unicast PDU session to deliver MBS (i.e., MBS downlink data) to the UE.
[0222] FIG. 11 illustrates a flowchart of a process according to an embodiment of the present disclosure. The process may be used at a first wireless network node (e.g., RAN1 shown in FIG. 1) and includes the following steps:
[0223] Step 1101: Receive a temporary mobile group ID associated with a multicast / broadcast service and a wireless terminal from the first session management function.
[0224] Step 1102: Receive a request from the second session management function to activate a multicast / broadcast service session corresponding to a temporary mobile group ID.
[0225] Step 1103: Transmit a message containing information indicating the status of a multicast / broadcast service session at the first wireless network node to the first session management function unit.
[0226] In the process illustrated in FIG. 1, a first wireless network node receives a TMGI associated with an MBS and a wireless terminal (e.g., UE) from a first SMF (e.g., SMF1 illustrated in FIG. 1). Additionally, the first wireless network node receives a request to activate an MBS session corresponding to the TMGI (e.g., identified by the TMGI). In this situation, the first wireless network node transmits a message to the first SMF containing information (e.g., RAN node information) indicating the status of the MBS session at the first wireless network node. Regarding details of the process illustrated in FIG. 11, reference may be made to steps 506, 606, and 614, for example, and details disclosed herein are not described herein for the sake of simplification.
[0227] In an embodiment, the TMGI transmitted to the first wireless network node indicates that the wireless terminal is authorized to receive data of the MBS corresponding to the TMGI.
[0228] In the embodiment, information indicating the status of a multicast / broadcast service session corresponding to TMGI includes TMGI.
[0229] In an embodiment, the first wireless network further transmits a handover request to a second wireless network node (e.g., RAN2 shown in FIG. 1), wherein the handover request includes TMGI.
[0230] In an embodiment, after transmitting a handover request, the first wireless network node receives information about a forwarding tunnel from the second wireless network node and transmits data of the MBS to the second wireless network node through the forwarding tunnel.
[0231] In an embodiment, the first wireless network node may set a timer associated with transmitting data of the MBS to the second wireless network node through a forwarding tunnel. When the timer expires, the first wireless network node transmits a termination marker to the second wireless network node.
[0232] In an embodiment, after transmitting a handover request, the first wireless network node receives at least one wireless resource for transmitting MBS data. In an embodiment, the at least one wireless resource includes at least one of a PTP wireless resource or a PTM resource. In an embodiment, the first wireless network node transmits at least one resource to a wireless terminal.
[0233] FIG. 12 illustrates a flowchart of a process according to an embodiment of the present disclosure. The process illustrated in FIG. 12 may be used at a second wireless network node (e.g., RAN2 illustrated in FIG. 1) and includes the following steps:
[0234] Step 1201: Receive a handover request from the first wireless network node that includes a temporary mobile group ID.
[0235] Step 1202: Send a message to the session management function unit containing information indicating the status of a multicast / broadcast service session corresponding to a temporary mobile group ID at the second wireless network node.
[0236] In FIG. 12, a second wireless network node receives a handover request containing a TMGI from a first wireless network node (e.g., RAN1 shown in FIG. 1). In this embodiment, the second wireless network node transmits a message containing information (e.g., RAN node information) indicating the status of an MBS session corresponding to the TMGI at the second wireless network node. For details of the process shown in FIG. 12, reference may be made to steps 702 and 714, for example, and details disclosed herein are not repeated for brevity.
[0237] In the embodiment, information indicating the status of an MBS session corresponding to TMGI includes TMGI.
[0238] In an embodiment, the second wireless network node transmits information of the forwarding tunnel to the first wireless network node and receives data of the MBS corresponding to the TMGI (e.g., identified by the TMGI) through the forwarding tunnel. In an embodiment, the second wireless network node receives a termination marker through the forwarding tunnel and releases the resources of the forwarding tunnel toward the first wireless network node.
[0239] In an embodiment, the second wireless network node further transmits at least one wireless resource to the first wireless network node for transmitting data for a multicast / broadcast service. In an embodiment, the at least one wireless resource includes at least one of a PTP wireless resource or a PTM resource. In an embodiment, the second wireless network node transmits data of an MBS corresponding to a TMGI through the at least one wireless resource.
[0240] FIG. 13 illustrates a flowchart of a process according to an embodiment of the present disclosure. The process illustrated in FIG. 13 may be used in an SMF (e.g., SMF1 or SMF2 illustrated in FIG. 1) and includes the following steps:
[0241] Step 1301: Send a temporary mobile group ID associated with the multicast / broadcast service and the wireless terminal to the wireless network node.
[0242] Step 1302: Receive a first message from a serving wireless network node of a wireless terminal, the message including information indicating the status of a multicast / broadcast service session corresponding to a temporary mobile group ID at the serving wireless network node.
[0243] Step 1303: Send a notification to at least one network function based on the status of a multicast / broadcast service session at a serving wireless network node.
[0244] In FIG. 13, the SMF transmits the TMGI associated with the MBS and the wireless terminal (e.g., UE) to a wireless network node (e.g., RAN1 and / or RAN2 shown in FIG. 1). In this embodiment, the SMF receives a message from the wireless network node serving the wireless terminal (e.g., RAN1 or RAN2) containing information (e.g., RAN node information) indicating the status of the MBS session corresponding to the TMGI at the serving wireless network node. Additionally, the SMF transmits a notification based on the status of the multicast / broadcast service session at the serving wireless network node. For details of the process shown in FIG. 13, reference may be made to steps 507, 615 through 618, for example, and details disclosed herein are not described herein for brevity.
[0245] In an embodiment, a temporary mobile group ID is transmitted to indicate that the wireless terminal is authorized to receive data of the MBS corresponding to the TMGI.
[0246] In an embodiment, at least one network function unit includes at least one of NEF or AF.
[0247] In the embodiment, information indicating the status of an MBS session corresponding to TMGI includes TMGI.
[0248] In an embodiment, the notification includes at least one of the identification of the wireless terminal (e.g., UE ID), TMGI, or information indicating the status of the MBS session at the serving wireless network node.
[0249] FIG. 14 illustrates a flowchart of a process according to an embodiment of the present disclosure. The process illustrated in FIG. 14 may be used in a network function unit (e.g., the NEF or AF illustrated in FIG. 1) and includes the following steps:
[0250] Step 1401: Send a request to activate a multicast / broadcast service session corresponding to a temporary mobile group ID to the session management unit deployed in the broadcast and multicast service center.
[0251] Step 1402: Receive a notification from the wireless terminal's serving session management function unit regarding the status of a multicast / broadcast service session at the wireless terminal's serving wireless network node.
[0252] In FIG. 14, the network function unit transmits a request to activate an MBS session to an SMF associated with the BMSC (e.g., SMF2 shown in FIG. 1), said request including a TMGI corresponding to the MBS session. In this embodiment, the network function unit receives a notification from the serving SMF (e.g., SMF1) of the wireless terminal (e.g., UE) regarding the status of the MBS session at the serving wireless network node of the wireless terminal (e.g., RAN1 or RAN2 shown in FIG. 1). For details of the process shown in FIG. 14, reference may be made to steps 606, 617, and 618, for example, and details disclosed herein are not described herein for brevity.
[0253] In an embodiment, the network function unit includes at least one of NEF or AF.
[0254] In an embodiment, the notification includes at least one of information indicating the identification of the wireless terminal, TMGI, or the status of the MBS session at the serving wireless network node.
[0255] In an embodiment, based on the notification, the network function unit triggers (e.g., performs) at least one of an MBS modification or switch to use a unicast packet data unit session to transmit MBS data to the wireless terminal. In this embodiment, the MBS corresponds to a TMGI.
[0256] Although various embodiments of the present disclosure have been described above, it should be understood that they are presented merely as examples and are not intended to be limiting. Likewise, various diagrams may depict exemplary architectures or configurations provided to enable those skilled in the art to understand the exemplary features and functions of the present disclosure. However, such persons will understand that the present disclosure is not limited to the illustrated exemplary architectures or configurations and may be implemented using various alternative architectures and configurations. Additionally, as understood by those skilled in the art, one or more features of one embodiment may be combined with one or more features of other embodiments described herein. Accordingly, the breadth and scope of the present disclosure should not be limited by any of the exemplary embodiments described above.
[0257] It is understood that any reference to elements in this specification using designations such as “first,” “second,” etc., generally does not limit the quantity or order of these elements. Rather, such designations may be used as a convenient means of distinguishing between two or more elements or instances of elements in this specification. Accordingly, references to first and second elements do not imply that only two elements may be used, or that in some manner, the first element must precede the second element.
[0258] Additionally, those skilled in the art will understand that information and signals may be represented using any various different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols, etc., which may be referenced in the above description, may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0259] Those skilled in the art will also understand that any various exemplary logic blocks, units, processors, means, circuits, methods, and functions described in connection with the embodiments disclosed herein may be implemented by electronic hardware (e.g., digital implementations, analog implementations, or a combination of both), firmware, various forms of programs or design code including instructions (which may be referred to herein for convenience as “software” or “software units”), or any combination of such technologies.
[0260] To clearly illustrate such compatibility of hardware, firmware, and software, various exemplary components, blocks, units, circuits, and steps are generally described above in terms of their functions. Whether these functions are implemented as hardware, firmware, or software, or as a combination of these technologies, depends on the specific application and design constraints imposed on the overall system. Those skilled in the art may implement the functions described in various ways for each specific application, but such implementation decisions do not depart from the scope of this disclosure. According to various embodiments, processors, devices, components, circuits, structures, machines, units, etc., may be configured to perform one or more functions described herein. The terms “configured to” or “configured for” as used herein in relation to a specific action or function refer to being physically configured, programmed, and / or arranged to perform the specified action or function.
[0261] Furthermore, those skilled in the art will understand that the various exemplary logic blocks, units, devices, components, and circuits described herein may be implemented or performed within an integrated circuit (IC) that may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, or any combination thereof. The logic blocks, units, and circuits may further include antennas and / or transceivers to communicate with various components within a network or within a device. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. The processor may be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration for performing the functions described herein. When implemented in software, the functions may be stored as one or more instructions or code on a computer-readable medium. Accordingly, the steps of the method or algorithm disclosed in this specification may be implemented as software stored on a computer-readable medium.
[0262] Computer-readable media include all computer storage media and communication media, including any medium capable of transferring computer programs or code from one location to another. Storage media may be any available medium that can be accessed by a computer. As an example, not a limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and can be accessed by a computer.
[0263] In this document, the term “unit” as used herein refers to software, firmware, hardware, and any combination of these elements for performing the related functions described herein. Additionally, for the sake of discussion, various units are described as separate units, but as will be apparent to those skilled in the art, two or more units may be combined to form a single unit that performs the related functions according to the embodiments of this disclosure.
[0264] Additionally, communication components as well as memory or other storage devices may be used in the embodiments of this disclosure. For clarity, it will be understood that the above description refers to embodiments of this disclosure with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functions between different functional units, processing logic elements, or domains may be used without impairing this disclosure. For example, a function described as being performed by a separate processing logic element or controller may be performed by the same processing logic element or controller. Accordingly, a reference to a specific functional unit does not indicate a strict logical or physical structure or organization, but is merely a reference to a suitable means for providing the described function.
[0265] Various modifications to the implementations described in this disclosure will be readily apparent to those skilled in the art, and the general principles set forth in this specification may be applied to other implementations without departing from the scope of this disclosure. Accordingly, this disclosure is not intended to be limited to the implementations shown in this specification, but should be understood to the broadest extent consistent with the novel features and principles disclosed in this specification as incorporated in the claims below.
Claims
Claim 1 A wireless communication method comprising: receiving, by means of a first wireless network node, a temporary mobile group ID (identity) associated with a multicast / broadcast service and a wireless terminal from a first session management function; receiving, by means of the first wireless network node, a request from a second session management function to activate a multicast / broadcast service session corresponding to the temporary mobile group ID; and transmitting, by means of the first wireless network node, a message including information indicating the status of a multicast / broadcast service session at the first wireless network node to the first session management function. Claim 2 A wireless communication method according to claim 1, wherein the temporary mobile group ID indicates that the wireless terminal is authorized to receive data of the multicast / broadcast service corresponding to the temporary mobile group ID. Claim 3 A wireless communication method according to claim 1, wherein information indicating the status of the multicast / broadcast service session corresponding to the temporary mobile group ID includes the temporary mobile group ID. Claim 4 A wireless communication method according to claim 1, further comprising the step of transmitting a handover request including the temporary mobile group ID to a second wireless network node. Claim 5 A wireless communication method according to claim 4, further comprising: receiving information of a forwarding tunnel from the second wireless network node; and transmitting data of the multicast / broadcast service to the second wireless network node through the forwarding tunnel, wherein the method further comprises the step of transmitting a termination marker to the second wireless network node after a timer expires, wherein the timer is associated with transmitting data of the multicast / broadcast service to the second wireless network node through the forwarding tunnel. Claim 6 A wireless communication method according to claim 4 or 5, further comprising the step of receiving at least one wireless resource for transmitting data of the multicast / broadcast service from the second wireless network node. Claim 7 A wireless communication method according to claim 6, further comprising the step of transmitting at least one wireless resource of the multicast / broadcast service to the wireless terminal. Claim 8 A wireless communication method according to claim 6, wherein the at least one wireless resource comprises at least one of a point-to-point wireless resource and a point-to-multipoint resource. Claim 9 A wireless communication method comprising: a step of transmitting a temporary mobile group ID associated with a multicast / broadcast service and a wireless terminal to a wireless network node by means of a session management function unit; a step of receiving, by means of the session management function unit, a message including information indicating the status of a multicast / broadcast service session corresponding to the temporary mobile group ID at the serving wireless network node from a serving wireless network node of the wireless terminal; and a step of transmitting a notification to at least one network function unit by means of the session management function unit based on the status of the multicast / broadcast service session at the serving wireless network node. Claim 10 A wireless communication method according to claim 9, wherein the temporary mobile group ID indicates that the wireless terminal is authorized to receive data of the multicast / broadcast service corresponding to the temporary mobile group ID. Claim 11 A wireless communication method according to claim 9 or 10, wherein the at least one network function part comprises at least one of a network exposure function part and an application function part. Claim 12 A wireless communication method according to claim 9 or 10, wherein the information indicating the status of the multicast / broadcast service session corresponding to the temporary mobile group ID includes the temporary mobile group ID. Claim 13 A wireless communication method according to claim 9 or 10, wherein the notification comprises at least one of the identification of the wireless terminal, the temporary mobile group ID, and information indicating the status of the multicast / broadcast service session at the serving wireless network node. Claim 14 A first wireless network node comprising a communication unit, wherein the communication unit receives a temporary mobile group ID associated with a multicast / broadcast service and a wireless terminal from a first session management function unit, receives a request from a second session management function unit to activate a multicast / broadcast service session corresponding to the temporary mobile group ID, and is configured to transmit a message to the first session management function unit that includes information indicating the status of the multicast / broadcast service session in the first wireless network node. Claim 15 A session management function unit configured to transmit a temporary mobile group ID associated with a multicast / broadcast service and a wireless terminal to a wireless network node, receive a message from a serving wireless network node of the wireless terminal that includes information indicating the status of a multicast / broadcast service session corresponding to the temporary mobile group ID at the serving wireless network node, and transmit a notification to at least one network function unit based on the status of the multicast / broadcast service session at the serving wireless network node. Claim 16 delete Claim 17 delete Claim 18 delete Claim 19 delete Claim 20 delete Claim 21 delete Claim 22 delete Claim 23 delete Claim 24 delete Claim 25 delete Claim 26 delete Claim 27 delete Claim 28 delete Claim 29 delete Claim 30 delete Claim 31 delete Claim 32 delete Claim 33 delete Claim 34 delete
Citation Information
Patent Citations
Providing to a communication service node user plane timing information for an MBMS bearer
WO2019228856A1
