Method for handling multicast / broadcast service sessions

Abstract

A method of wireless communication for a first wireless network node is disclosed. The method includes receiving, from a first session management function, a temporary mobile group identity associated with a multicast / broadcast service and a wireless terminal; receiving, from a second session management function, a request to activate a multicast / broadcast service session corresponding to the temporary mobile group identity; and sending, to the first session management function, a message including information indicating a status of the multicast / broadcast service session in the first wireless network node.

Description

Technical Field

[0001] This article mainly deals with wireless communication. Background Technology

[0002] To illustrate the background of this disclosure, several technical terms are explained below.

[0003] Broadcast communication service: A communication service that simultaneously provides the same services and the same specific content data to all user equipment (UE) within a geographical area.

[0004] Multicast communication service: A communication service that simultaneously provides the same service and the same specific content data to a group of dedicated UEs (i.e., not all UEs within the multicast coverage area are authorized to receive data).

[0005] Multicast session: A session that transmits multicast communication services. Furthermore, a multicast session is characterized by the content transmitted within the session, a list of UEs capable of receiving multicast communication services, and optionally, a multicast area from which the multicast session is distributed.

[0006] Unicast session: A session in which communication services are delivered between a single UE and the data network.

[0007] Multicast / Broadcast Service (MBS) Session: A multicast session or a broadcast session.

[0008] Point-to-Point (PTP) delivery method: A method in which a Random Access Network (RAN) node delivers a separate copy of an MBS data packet to a single UE via radio resources.

[0009] Point-to-Multipoint (PTM) delivery method: A method in which the RAN node delivers a single copy of the MBS data packet to a group of UEs via radio resources.

[0010] When providing MBS to a UE, it is unclear how to establish an MBS session and how to handle the MBS session during UE mobility. Summary of the Invention

[0011] This article relates to methods, systems, and devices for processing MBS sessions.

[0012] This disclosure relates to a wireless communication method for a first wireless network node. The wireless communication method includes:

[0013] Receive a temporary mobile group identifier associated with the multicast / broadcast service and the wireless terminal from the first session management function.

[0014] Receive a request from the second session management function to activate a multicast / broadcast service session corresponding to a temporary mobile group identifier, and

[0015] A message is sent to the first session management function, the message including information indicating the status of the multicast / broadcast service session in the first wireless network node.

[0016] Various embodiments can preferably achieve the following features:

[0017] Preferably, the temporary mobile group identifier indicates that the wireless terminal is authorized to receive data from multicast / broadcast services corresponding to the temporary mobile group identifier.

[0018] Preferably, the information indicating the status of the multicast / broadcast service session corresponding to the temporary mobile group identifier includes the temporary mobile group identifier.

[0019] Preferably, the wireless communication method further includes sending a handover request, including the temporary mobile group identifier, to the second wireless network node.

[0020] Preferably, the wireless communication method further includes receiving information from the forwarding tunnel from the second wireless network node, and sending multicast / broadcast service data to the second wireless network node via the forwarding tunnel.

[0021] Preferably, the wireless communication method further includes sending an end marker to the second wireless network node after a timer expires, wherein the timer is associated with data for sending multicast / broadcast services to the second wireless network node via a forwarding tunnel.

[0022] Preferably, the wireless communication method further includes receiving at least one wireless resource from the second wireless network node for transmitting data for multicast / broadcast services.

[0023] Preferably, the wireless communication method further includes at least one wireless resource for transmitting multicast / broadcast services to the wireless terminal.

[0024] Preferably, the at least one wireless resource includes at least one of point-to-point wireless resources or point-to-multipoint wireless resources.

[0025] This disclosure relates to a wireless communication method for use in a second wireless network node. The wireless communication method includes:

[0026] Receive a handover request including a temporary mobile group identifier from the first wireless network node, and

[0027] A message is sent to the session management function, which includes information indicating the status of a multicast / broadcast service session in the second radio network node corresponding to a temporary mobile group identifier.

[0028] Various embodiments can preferably achieve the following features:

[0029] Preferably, the information indicating the status of the multicast / broadcast service session corresponding to the temporary mobile group identifier includes the temporary mobile group identifier.

[0030] Preferably, the wireless communication method further includes sending information about a forwarding tunnel to a first wireless network node, and receiving data from the first wireless network node via the forwarding tunnel that corresponds to a temporary mobile group identifier for multicast / broadcast services.

[0031] Preferably, the wireless communication method further includes receiving an end marker from the first wireless network node via a forwarding tunnel, and releasing resources of the forwarding tunnel pointing to the first wireless network node.

[0032] Preferably, the wireless communication method further includes sending at least one wireless resource to the first wireless network node for transmitting data for multicast / broadcast services.

[0033] Preferably, the at least one wireless resource includes at least one of point-to-point wireless resources or point-to-multipoint wireless resources.

[0034] Preferably, the wireless communication method further includes transmitting data corresponding to a temporary mobile group identifier to a wireless terminal via the at least one wireless resource.

[0035] This disclosure relates to a wireless communication method for session management functions. The wireless communication method includes:

[0036] Send a temporary mobile group identifier associated with multicast / broadcast services and wireless terminals to the wireless network nodes.

[0037] Receive a message from the serving radio network node of the wireless terminal. This message includes information indicating the status of a multicast / broadcast service session corresponding to a temporary mobile group identifier within the serving radio network node.

[0038] Based on the state of the multicast / broadcast service sessions in the serving wireless network node, send notifications to at least one network function.

[0039] Various embodiments can preferably achieve the following features:

[0040] Preferably, the temporary mobile group identifier indicates that the wireless terminal is authorized to receive data from multicast / broadcast services corresponding to the temporary mobile group identifier.

[0041] Preferably, at least one network function includes at least one of network openness function or application function.

[0042] Preferably, the information indicating the status of the multicast / broadcast service session corresponding to the temporary mobile group identifier includes the temporary mobile group identifier.

[0043] Preferably, the notification includes at least one of the following: an identifier of the wireless terminal, a temporary mobile group identifier, or information indicating the status of a multicast / broadcast service session in the serving wireless network node.

[0044] This disclosure relates to a wireless communication method for network functions. The wireless communication method includes:

[0045] Send a request to the session management function associated with the broadcast / multicast service center to activate a multicast / broadcast service session corresponding to a temporary mobile group identifier, and

[0046] Receive notifications related to the status of multicast / broadcast service sessions in the serving wireless network node of the wireless terminal from the service session management function of the wireless terminal.

[0047] Various embodiments can preferably achieve the following features:

[0048] Preferably, the network function includes at least one of network openness function or application function.

[0049] Preferably, the notification includes at least one of the following: an identifier of the wireless terminal, a temporary mobile group identifier, or information indicating the status of a multicast / broadcast service session in the first wireless network node.

[0050] Preferably, the wireless communication method further includes, based on the notification, triggering at least one of multicast / broadcast service session modification or switching to send multicast / broadcast service data to the wireless terminal using a unicast packet data unit session, wherein the multicast / broadcast service corresponds to a temporary mobile group identifier.

[0051] This disclosure relates to a first wireless network node, including a communication unit configured to:

[0052] Receive a temporary mobile group identifier associated with the multicast / broadcast service and the wireless terminal from the first session management function.

[0053] Receive a request from the second session management function to activate a multicast / broadcast service session corresponding to a temporary mobile group identifier, and

[0054] A message is sent to the first session management function, the message including information indicating the status of the multicast / broadcast service session in the first wireless network node.

[0055] Various embodiments can preferably achieve the following features:

[0056] Preferably, the first wireless network node further includes a processor configured to perform any of the wireless communication methods described above.

[0057] This disclosure relates to a second wireless network node, including a communication unit configured to:

[0058] Receive a handover request including a temporary mobile group identifier from the first wireless network node, and

[0059] A message is sent to the session management function, which includes information indicating the status of a multicast / broadcast service session in the second radio network node corresponding to a temporary mobile group identifier.

[0060] Various embodiments may preferably achieve the following features:

[0061] Preferably, the second wireless network node further includes a processor configured to perform any of the wireless communication methods described above.

[0062] This disclosure relates to a wireless device, including a communication unit configured to:

[0063] Send a temporary mobile group identifier associated with multicast / broadcast services and wireless terminals to the wireless network nodes.

[0064] Receive a message from the serving radio network node of the wireless terminal. This message includes information indicating the status of a multicast / broadcast service session corresponding to a temporary mobile group identifier within the serving radio network node.

[0065] Based on the state of the multicast / broadcast service sessions in the serving wireless network node, send notifications to at least one network function.

[0066] Various embodiments may preferably achieve the following features:

[0067] Preferably, the wireless device further includes a processor configured to perform any of the wireless communication methods described above.

[0068] This disclosure relates to a wireless device, including a communication unit configured to:

[0069] Send a request to the session management function associated with the broadcast / multicast service center to activate a multicast / broadcast service session corresponding to a temporary mobile group identifier, and

[0070] Receive notifications related to the status of multicast / broadcast service sessions in the serving wireless network node of the wireless terminal from the service session management function of the wireless terminal.

[0071] Various embodiments can preferably achieve the following features:

[0072] Preferably, the wireless device further includes a processor configured to perform any of the wireless communication methods described above.

[0073] This disclosure relates to a computer program product including computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement any of the aforementioned wireless communication methods.

[0074] The exemplary embodiments disclosed herein are intended to provide features that will become apparent from the following description taken in conjunction with the accompanying drawings. Exemplary systems, methods, apparatuses, and computer program products are disclosed herein according to various embodiments. However, it should be understood that these embodiments are presented by way of example and not limitation, and that various modifications may be made to the disclosed embodiments without departing from the scope of this disclosure, as will be apparent to those skilled in the art upon reading this disclosure.

[0075] Therefore, this disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, the specific order and / or hierarchy of steps in the methods disclosed herein are merely exemplary methods. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes may be rearranged without departing from the scope of this disclosure. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or actions in an exemplary order, but this disclosure is not limited to the specific order or hierarchy presented, unless otherwise expressly stated. Attached Figure Description

[0076] The above and other aspects and their implementations are described in more detail in the accompanying drawings, specification and claims.

[0077] Figure 1 A schematic diagram of a network according to an embodiment of the present disclosure is shown.

[0078] Figure 2 An example of a schematic diagram of a wireless terminal according to an embodiment of the present disclosure is shown.

[0079] Figure 3 An example of a schematic diagram of a wireless network node according to an embodiment of the present disclosure is shown.

[0080] Figure 4 A schematic diagram of a process according to an embodiment of the present disclosure is shown.

[0081] Figure 5 A schematic diagram of a process according to an embodiment of the present disclosure is shown.

[0082] Figure 6A and 6B This is a schematic diagram of a process according to an embodiment of the present disclosure.

[0083] Figure 7A and 7B This is a schematic diagram of a process according to an embodiment of the present disclosure.

[0084] Figure 8A and 8B This is a schematic diagram of a process according to an embodiment of the present disclosure.

[0085] Figure 9 A schematic diagram of a process according to an embodiment of the present disclosure is shown.

[0086] Figure 10 A schematic diagram of a process according to an embodiment of the present disclosure is shown.

[0087] Figure 11 A flowchart of a process according to an embodiment of the present disclosure is shown.

[0088] Figure 12 A flowchart of a process according to an embodiment of the present disclosure is shown.

[0089] Figure 13 A flowchart of a process according to an embodiment of the present disclosure is shown.

[0090] Figure 14 A flowchart of a process according to an embodiment of the present disclosure is shown. Detailed Implementation

[0091] In this disclosure, the abbreviation for Multicast / Broadcast Service is MBS.

[0092] Figure 1 A schematic diagram of a network according to an embodiment of the present disclosure is shown. Figure 1 The network functions and components shown will be described further below.

[0093] 1) User Equipment (UE)

[0094] 2) Radio Access Network (RAN)

[0095] 3) Access and Mobility Management Function (AMF)

[0096] The AMF includes the following functions: registration management, connection management, reachability management, and mobility management. In addition, the AMF performs access authentication and access authorization. The AMF is a Non-Access Stratum (NAS) secure termination service and relays session management (SM) between the UE and the SMF, among others.

[0097] 4) Session Management Function (SMF)

[0098] 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 User Plane (UP) functions, downlink data notification, etc.

[0099] 5) User Plane Function (UPF)

[0100] UPF includes the following functions: serving as a mobility anchor point within / between Radio Access Technology (RAT), packet routing and forwarding, traffic usage reporting, Quality of Service (QoS) processing on the user plane, downlink packet buffering, and downlink data notification triggering.

[0101] 6) Network Exposure Function (NEF)

[0102] NEF supports opening network capabilities and events to Application Functions (AFs). Third-party applications can invoke services provided by the network via NEF, and NEF performs authentication and authorization for third-party applications. NEF also provides translation of information exchanged with AFs and with internal network functions.

[0103] 7) Application Function (AF)

[0104] The Application Front-End (AF) interacts with the 3rd Generation Partnership Project (3GPP) core network to provide services, such as supporting application impacts on traffic routing, accessing network open functions, and interacting with the policy framework for policy control. The AF can gain the trust of the data network operator and can be allowed to interact directly with relevant network functions. AFs that are not permitted direct access to network functions by the operator should interact with relevant network functions through an external open framework via the Network Provider Framework (NEF). In this disclosure, the AF is deployed in the data network.

[0105] 8) Policy Control Function (PCF)

[0106] The PCF supports a unified policy framework for managing network behavior. The PCF provides access management policies to the AMF, session management policies to the SMF, or UE policies to the UE. The PCF can access the Unified Data Repository (UDR) to obtain subscription information related to policy decisions.

[0107] 9) Broadcast and Multicast Service Center (BMSC)

[0108] The BMSC is deployed to provide MBS sessions to the AF. The BMSC can be decoupled (e.g., partitioned) into BMSC-C and BMSC-U, where BMSC-C is the control plane function of the BMSC and BMSC-U is the user plane function of the BMSC. In one embodiment, BMSC-C and SMF (e.g., Figure 1 The SMF2 shown can be deployed together, and BMSC-U and UPF (e.g., Figure 1 The UPF2 shown can be deployed together. In one embodiment, the BMSC-C can also be deployed together with the NEF.

[0109] exist Figure 1 In this context, the numbers following certain network function names 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. Furthermore, AMF2, PCF2, SMF2, and UPF2 are used for MBS sessions that can be shared by a group of UEs. In one embodiment, RAN1 and RAN2 simultaneously provide unicast and MBS services to the UEs. For MBS sessions, a single N3 tunnel between RAN2 and UPF2 can be shared by this group of UEs.

[0110] Figure 2 This diagram relates to a wireless terminal 20 according to an embodiment of the present disclosure. The wireless terminal 20 may be a user equipment (UE), mobile phone, laptop, tablet computer, e-book reader, or portable computer system, and is not limited thereto. The wireless terminal 20 may include a processor 200 such as a microprocessor or application-specific integrated circuit (ASIC), a storage unit 210, and a communication unit 220. The storage unit 210 may be any data storage device storing program code 212 accessed and executed by the processor 200. Embodiments of the storage unit 210 include, but are not limited to, a Subscribing Identity Module (SIM), Read-Only Memory (ROM), flash memory, Random-Access Memory (RAM), hard disk, and optical data storage devices. The communication unit 220 may be a transceiver and is used to send and receive signals (e.g., messages or data packets) according to the processing results of the processor 200. In one embodiment, the communication unit 220 communicates via… Figure 2 At least one antenna 222 shown transmits and receives signals.

[0111] In one embodiment, storage unit 210 and program code 212 may be omitted, and processor 200 may include storage unit storing program code.

[0112] The processor 200 can implement any of the steps in the example embodiment on the wireless terminal 20, for example, by executing program code 212.

[0113] The communication unit 220 may be a transceiver. Alternatively or as a supplement, the communication unit 220 may combine a transmitting unit and a receiving unit, which are respectively configured to transmit signals to a wireless network node (e.g., a base station) and receive signals from a wireless network node.

[0114] Figure 3The diagram relates to a wireless network node 30 according to one embodiment of the present disclosure. The wireless network node 30 may be a wireless device, satellite, base station (BS), network entity, mobility management entity (MME), serving gateway (S-GW), packet data network (PDN) gateway (P-GW), radio access network (RAN), next-generation RAN (NG-RAN), data network, core network, or radio network controller (RNC), and is not limited thereto herein. Furthermore, the wireless network node 30 may include (e.g., execute, implement, or realize) at least one network function, such as Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Application Function (AF), Broadcast and Multicast Service Center (BMSC), Network Exposure Function (NEF), etc. The 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 storing program code 312 accessed and executed by the processor 300. Examples of storage units 310 include, but are not limited to, SIM, ROM, flash memory, RAM, hard disk, and optical data storage devices. The communication unit 320 can be a transceiver and is used to send and receive signals (e.g., messages or data packets) based on the processing results of the processor 300. In one example, the communication unit 320 is connected via... Figure 3 At least one antenna 322 shown transmits and receives signals.

[0115] In one embodiment, storage unit 310 and program code 312 may be omitted. Processor 300 may include storage unit storing program code.

[0116] The processor 300 can implement any of the steps described in the example embodiment on the wireless network node 30, for example, by executing program code 312.

[0117] The communication unit 320 may be a transceiver. Alternatively or as a supplement, the communication unit 320 may combine a transmitting unit and a receiving unit, which are respectively configured to transmit signals to a wireless terminal (e.g., a user equipment) and receive signals from a wireless terminal.

[0118] Figure 4 A schematic diagram of a process according to an embodiment of the present disclosure is shown. Note that PCF1, BMSC-C, NEF, and AF can be as follows: Figure 1 Those shown. In Figure 4 In this process, the AF requests the MBS configuration from the BMSC and provides the MBS configuration to the network. For example, the MBS configuration includes a Temporary Mobile Group Identity (TMGI) and / or an associated Internet Protocol (IP) multicast address. The TMGI is used to uniquely identify the MBS on the radio interface. Additionally, the IP multicast address is used to identify the MBS at the IP layer.

[0119] More specifically, when AF needs to come from BMSC (e.g., Figure 4 When one or more TMGIs (i.e., at least one TMGI) of the BMSC-C shown are available, the AF sends a TMGI request (message) to the NEF (step 401). In one embodiment, the TMGI request (message) includes (e.g., an indication) the number of TMGIs requested.

[0120] In step 402, the NEF authorizes whether to allow the AF to request TMGI. In this embodiment, the NEF determines that the AF request for TMGI is allowed and forwards the TMGI request to the BMSC (e.g., Figure 4 (BMSC-C shown in the figure).

[0121] In step 403, BMSC-C allocates a set of TMGIs, with each TMGI assigned a multicast IP address. Furthermore, BMSC-C determines the expiration time of each TMGI. Next, BMSC-C returns the set of TMGIs and their associated multicast IP addresses to NEF in a TMGI response.

[0122] In step 404, NEF forwards (e.g., sends) a TMGI response to AF.

[0123] In step 405, the AF provides MBS in the network. In one embodiment, the AF sends (e.g., transmits) an AF request to the NEF, wherein the AF request includes application information, Single Network Slice Selection Assignment (S-NSSAI), Data Network Name (DNN), TMGI, IP multicast address, and External Group Identification (ID). The External Group ID is configured to identify the UE group receiving the MBS. Additionally, the AF request may also include a notification address for receiving RAN node information from the SMF. In one embodiment, the RAN node information may include the TMGI. In one embodiment, the RAN node information indicates the status of the MBS session in the UE's serving RAN. For example, the RAN node information may indicate whether the UE's serving RAN supports MBS and / or whether the UE's serving RAN has an MBS session context with a TMGI and / or whether the MBS session corresponding to the TMGI is active in the UE's serving RAN.

[0124] In step 406, the NEF maps the external group ID to the internal group ID. Furthermore, the NEF determines its own notification address to receive RAN node information. The NEF stores the internal group ID and AF request information in the UDR.

[0125] In step 407, NEF responds to AF with an Acknowledge (ACK) message.

[0126] In step 408, if PCF1 has subscribed to AF request information from UDR, then UDR sends a notification (message) to PCF1, wherein the notification (message) includes the internal group ID and AF request information. In one embodiment, PCF1 stores the AF request information.

[0127] Figure 5 The diagram illustrates a process according to an embodiment of the present disclosure, wherein the UE, AMF1, SMF1, UPF1, PCF1, NEF, and AF can be as follows: Figure 1 Those shown. Note that... Figure 5 The RAN shown can be Figure 1 One of RAN1 or RAN2 shown. Figure 5 The illustrated embodiment demonstrates how a UE can join an MBS. Figure 5 During the process shown, the network needs to authorize the UE to join the MBS. In one embodiment, Figure 5 The procedure shown can be performed before the corresponding MBS session begins.

[0128] More specifically, the UE can obtain the IP multicast address of the MBS through application layer information exchange. When the UE wants to join the MBS, it sends a message with the target IP multicast address identifying the MBS. For example, the UE checks its UE policy to determine the S-NSSAI and DNN associated with the IP multicast address and checks if an existing PDU session with the associated S-NSSAI and DNN exists. If no PDU session is found, the UE establishes a PDU session with the associated S-NSSAI and DNN. During the PDU session establishment process, SMF1 establishes a Session Management (SM) policy association with PCF1 and provides the UE's internal group ID to PCF1 (step 501).

[0129] In this embodiment, the UE sends the message associated with joining the MBS session in two ways, as described in steps 502a (i.e., steps 502a.1 and 502a.2) and 502b. That is, the UE can perform one of steps 502a (i.e., steps 502a.1 and 502a.2) and 502b.

[0130] In step 502a.1, the UE may send an Internet Group Management Protocol (IGMP) join message to UPF1 via the user of the PDU session associated with the MBS.

[0131] In step 502a.2, UPF1 detects the IGMP join message and reports the detected IP multicast address to SMF1 in the N4 report.

[0132] In step 502b, the UE can send a NAS PDU session modification request (including the IP multicast address) to SMF1 via AMF1 to join MBS.

[0133] In step 503, based on the NAS message (i.e., NAS PDU session modification request) or N4 report, SMF1 sends an SM policy association update request to PCF1, wherein the SM policy association update request includes the IP multicast address.

[0134] In step 504, PCF1 already has information about the internal group ID and the corresponding IP multicast address. Therefore, PCF1 checks whether the UE's 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 one embodiment, the SM policy association update response (message) may also include the notification address of the NEF configured to receive RAN node information.

[0135] In step 505, SMF1 stores the authorized IP multicast address and associated TMGI in the PDU session context. Then, SMF1 sends Namf_Communication_N1N2MessageTransfer to AMF1. Namf_Communication_N1N2MessageTransfer includes an N1 message container (e.g., a PDU session modification command) and an N2 message container. The N1 message container includes the authorized TMGI and IP multicast address, and the N2 message container may also include the authorized TMGI.

[0136] In step 506, AMF1 sends an N2 PDU session request, along with N1 message containers and N2 message containers, to the RAN.

[0137] In step 507, the RAN sends an N1 message container to the UE using AN-specific signaling. Therefore, the UE acknowledges that it is permitted to receive the MBS identified by the received TMGI.

[0138] In step 508, if the RAN supports MBS, the RAN also stores the TMGI in the UE context. Therefore, 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 one embodiment, the RAN node information may include the TMGI. In one embodiment, the RAN node information may be configured to indicate the UE's serving RAN (e.g., ...). Figure 5 Does the RAN shown have an MBS session context for TMGI (e.g., the state of the MBS session for TMGI in the RAN)?

[0139] 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 one embodiment, the N2 PDU session response message may include RAN node information received from the RAN. In one embodiment, when the SMF1 does not receive RAN node information from the RAN, the SMF1 determines that the RAN does not support MBS.

[0140] In step 510, SMF1 sends an Nsmf_PDUSession_UpdateSMContext response to AMF1.

[0141] In step 511, the SMF sends a notification to the NEF. In one embodiment, the notification includes the UE ID of the UE and RAN node information received from the RAN.

[0142] In step 512, the NEF sends (e.g., forwards) the notification to the AF. In one embodiment, based on the RAN node information in the notification, the AF confirms that the UE has joined the MBS session and confirms whether the UE's serving RAN supports MBS and / or whether the UE's serving RAN has an MBS session context and / or whether the MBS session corresponding to the TMGI is active in the UE's serving RAN. Based on the RAN node information in the notification, the AF determines whether to use a unicast PDU session or an MBS session to deliver the MBS to the UE.

[0143] exist Figure 5 After the illustrated process is completed, the UE is authorized to receive an MBS identified by the TMGI, which is associated with an IP multicast address. When the UE enters an idle state (e.g., RRC I DLE), the UE context in the RAN can 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.

[0144] Figure 6A and 6B A schematic diagram of a process according to an embodiment of the present disclosure is shown. Figure 6A and 6B The illustrated procedure can be used to establish an MBS session. In this embodiment, SMF2 is deployed concurrently with BMSC-C, and UPF2 is deployed concurrently with BMSC-U (e.g., Figure 1(SMF2, BMSC-C, UPF2, and BMSC-U are shown). Alternatively, SMF2 and BMSC-C can be deployed separately and / or UPF2 and BMSC-U can also be deployed separately. In one embodiment, AMF2, PCF2, NEF, and AF can also be as shown. Figure 1 Those shown. Furthermore... Figure 6A and 6B The RAN shown can be Figure 1 RAN1 or RAN2 as shown. In Figure 6A and 6B After the process shown is completed, the RAN is able to receive MBS downlink data via the shared N3 tunnel of the MBS session.

[0145] More specifically, see Figure 6A The AF invokes a session start (e.g., NEF service operation) to send an AF request (step 601). In one embodiment, the service start (i.e., the AF request) includes at least one of the following: AF transaction ID, requested slice-aided selection information (S-NSSAI), requested data network name (DNN), or requested session and service continuity (SSC) mode. Note that the parameters included in the AF request are used to establish (e.g., activate) the MBS session. In one embodiment, the AF request may also include at least one of the following items: the TMGI of the MBS session, the IP multicast address, and the destination area.

[0146] In step 602, the NEF authorizes whether to allow the AF to begin (e.g., activate) an MBS session. In one embodiment, the NEF converts the target area into a list of Tracking Area Identifiers (TAIs) and forwards (e.g., sends) a session start (i.e., AF request) to the SMF2. In this embodiment, the BSMC-C and SMF2 are deployed together.

[0147] In step 603, SMF2 creates an MBS session context associated with the TMGI. Based on local configuration, SMF2 assigns a PDU session ID to the MBS session. Furthermore, SMF2 selects PCF2 to establish an SM policy association. SMF2 also sends the TMGI and IP multicast addresses to PCF2.

[0148] In step 604, SMF2 selects a UPF2 that supports MBS sessions and establishes an N4 association with the selected UPF2. In this embodiment, SMF2 sends forwarding rules including IP multicast addresses to UPF2, and UPF2 can forward downlink MBS traffic (e.g., MBS downlink data) to the RAN via the shared N3 tunnel. In one embodiment, the information of the shared N3 tunnel is allocated by UPF2 and provided to SMF2.

[0149] In step 605, SMF2 discovers (e.g., determines, selects) AMF2 based on the TAI list received in step 602, and sends Namf_Communication_N1N2MessageTransfer to AMF2. In one embodiment, Namf_Communication_N1N2MessageTransfer includes parameters such as PDU session ID, TAI list, and N2 SM information (e.g., including PDU session ID, TMGI, QFI, QoS profile, UPF2's N3 tunnel information, S-NSSAI, etc.). Upon receiving Namf_Communication_N1N2MessageTransfer, AMF2 sends a response to SMF2.

[0150] In one embodiment, SMF2 may select multiple AMFs (e.g., multiple AMF2s) based on the TAI list. In this case, SMF2 performs step 605 for each selected AMF.

[0151] In step 606, AMF2 selects a RAN based on the TAI list received in step 605 and sends an N2 PDU session request to the RAN. In one embodiment, the N2 PDU session request carries the AMF Next-Generation Application Protocol (NGAP) UE ID and N2 SM information received from SMF2.

[0152] In one 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 for each selected RAN node.

[0153] In step 607, the RAN creates an MBS session context associated with the TMGI and can publish AN-specific resource reservations for the MBS session. In one embodiment, the RAN can begin broadcasting the TMGI via the Uu interface. By reading the TMGI in the broadcast information, the UE determines whether it can receive the MBS associated with the TMGI.

[0154] In one embodiment, the RAN can publish AN-specific resource reservations at a later stage. For example, when there are no UEs interested in the MBS in the cell, the RAN does not need to allocate MBS resources for it. In this case, when the RAN receives downlink packets via the N3 tunnel, it can discard the received downlink packets if no radio resources are reserved.

[0155] In one embodiment, the RAN sends an N2 PDU session response to the AMF2. In one embodiment, the N2 PDU session response includes the RAN NGAP UE ID. The AMF2 uses the RAN NGAP UE ID to send subsequent N2 messages to the RAN. In one embodiment, the N2 PDU session response may also include parameters such as the PDU session ID, reason, and N2 SM information (e.g., including the PDU session ID, N3 tunnel information, and a list of accepted / rejected Quality of Service (QoS) flow IDs, QFIs, etc.).

[0156] In step 608, for each N2 PDU session response from the RAN, AMF2 sends an Nsmf_PDUSession_UpdateSMContext request to the SMF (e.g., including the SMF SM context ID and N2 SM information).

[0157] In step 609, for each Nsmf_PDUSession_UpdateSMContext request received from AMF2, SMF2 initiates an N4 session modification procedure with UPF2 to provide the N3 tunnel information received from the RAN. UPF2 then associates the provided N3 tunnel information pointing to the RAN with the MBS session.

[0158] In one embodiment, if there are multiple RANs associated with an MBS session, the UPF2 replicates the MBS downlink traffic and forwards it to each RAN node via the corresponding N3 tunnel.

[0159] In one embodiment, if the UPF2 with BMSC-U deployed has not yet assigned an IP address and port number to the MBS session, the UPF2 can also assign a UPF+BMSC-U IP address and port number to the MBS session and provide it to the SMF2.

[0160] In step 610, SMF2 sends an Nsmf_PDUSession_UpdateSMContext response to AMF2.

[0161] In step 611, SMF2 returns a session start ACK to NEF. In one embodiment, the session start ACK includes TMGI, UPF+BMSC-U IP address, and port number.

[0162] In step 612, NEF sends a session start ACK to AF, which includes TMGI, UPF+BMSC-UI P address and port number.

[0163] In step 613, see Figure 6B The AF sends downlink traffic (e.g., MBS downlink data) to the UPF+BMSC-U IP address and port number. In this embodiment, the UPF2 with BMSC-U generates MBS downlink traffic (e.g., by using an IP multicast address as the target IP address) and forwards the MBS downlink data to the RAN via the shared N3 tunnel of the MBS session.

[0164] In step 614, for each UE authorized to receive the TMGI (i.e., the TMGI in the PDU session context of the UE) in an MBS, the RAN sends a notification (e.g., a message including RAN node information) to the UE's serving AMF1 (i.e., AMF1 is the UE's serving AMF). In one embodiment, the RAN node information includes the TMGI. In another embodiment, the RAN node information indicates that the MBS session is activated and / or the UE can receive the TMGI via the MBS session (e.g., the status of the MBS session in the RAN).

[0165] In step 615, AMF1 forwards the notification to SMF1.

[0166] In step 616, SMF1 forwards the notification to NEF.

[0167] In step 617, the NEF forwards the notification to the AF. Therefore, the AF can determine to stop using unicast PDU sessions to transmit MBS (data) to the UE. In other words, the AF can determine to start using MBS sessions to transmit MBS (i.e., MBS downlink data) to the UE.

[0168] Figure 7A and 7B A schematic diagram of a process according to an embodiment of the present disclosure is shown. Figure 7A and 7B The procedure shown can be used to move (e.g., handover) a UE to a new RAN node via an Xn-based handover process. Note that... Figure 7A and 7B The UE, RAN1, RAN2, AMF1, SMF1, UPF1, and UPF2 shown can be as follows: Figure 1Those shown in the diagram. In this embodiment, a forwarding tunnel for the MBS session can be established to reduce packet loss during handover.

[0169] More specifically, before the handover, the UE receives MBS (e.g., MBS downlink data) via RAN1 through the MBS session (step 701), see [link to relevant documentation]. Figure 7A .

[0170] In step 702, based on radio measurements, RAN1 can initiate an Xn-based handover to RAN2 by sending a handover request (message). In one embodiment, the handover request may include the PDU session context from which the handover is being performed, wherein the PDU session context may include a TMGI from which the UE is authorized to receive the associated MBS. If the QoS profile for the MBS session has activated the MBS session, the handover request message may also include information indicating whether data forwarding is required to reduce packet loss in the MBS session.

[0171] In step 703, RAN2 reserves radio resources for the QoS profile of the PDU session received from RAN1. If RAN2 supports MBS and needs to forward data for the MBS session, RAN2 allocates a data forwarding tunnel for the MBS session. If the MBS session is activated in RAN2, RAN2 can also allocate PTP radio resources for the MBS session.

[0172] In this embodiment, RAN2 returns a handover request ACK to RAN1. In one embodiment, the handover request ACK includes information on all radio resources successfully reserved for the UE in RAN2. Alternatively or supplementarily, the handover request ACK may include information on the data forwarding tunnel and PTP radio resources of the MBS session. In embodiments where the MBS session is activated in RAN2, the handover request ACK may also include the PTM radio resources of the MBS session identified by TMGI.

[0173] In step 704, RAN1 sends a handover command to the UE. In one embodiment, the handover command includes radio resources received from RAN2.

[0174] In step 705, if RAN1 receives a data forwarding tunnel allocated to the MBS session, it can begin forwarding downlink MBS downlink data to RAN2 via that data forwarding tunnel, and RAN2 begins buffering the MBS downlink data received via the forwarding tunnel. In one embodiment, RAN1 can start a data forwarding timer.

[0175] In step 706, based on the radio resources received from RAN1, the UE accesses RAN2 and sends a handover confirmation to RAN2.

[0176] In step 707, if PTP radio resources were reserved for the MBS session in step 703, RAN2 begins transmitting buffered downlink MBS data to the UE. In one embodiment, the UE does not receive reserved PTP radio resources, but instead receives reserved PTM from RAN1. In this case, the UE can receive MBS downlink data from RAN2 via PTM radio resources.

[0177] In step 708, RAN2 sends a path handover request including N2 SM information to AMF1. In one embodiment, the N2 SM information includes N3 user plane information of the PDU session. In an embodiment where RAN2 receives TMGI from RAN1, the path handover request may include RAN node information. In one embodiment, the RAN node information includes TMGI. In one embodiment, the RAN node information indicates whether the MBS session is active in RAN2 (e.g., the status of the MBS session in the serving RAN). In one 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 further notifies NEF and AF that the UE's serving RAN (i.e., RAN2) does not support MBS.

[0178] In step 709, AMF1 sends an Nsmf_UpdateSMContext request to SMF1.

[0179] In step 710, SMF1 sends an N4 session modification to UPF1 to update the N3 user plane information of the RAN2 node. See [link to relevant documentation]. Figure 7B .

[0180] In step 711, SMF1 returns an Nsmf_PDUSession_UpdateSMContext response to AMF1.

[0181] In step 712, the AMF returns a path switching response to RAN1.

[0182] In step 713, RAN2 confirms the successful handover by sending a resource release message to RAN1.

[0183] In step 714, after the handover, when the state of the MBS session changes, RAN2 can send a message to AMF1 to indicate whether the MBS session is active in RAN2. In one embodiment, AMF1 can also forward this message to SMF1 (…). Figure 7B (Not shown in the image).

[0184] In step 715, if a timer was set in step 705 and the timer expires, RAN1 sends an end marker to RAN2 via the data forwarding tunnel. In this embodiment, the end marker can trigger the release of resources allocated to RAN1 (e.g., the data forwarding tunnel).

[0185] In step 716, after receiving the end marker, RAN2 releases the forwarding tunnel and begins transmitting MBS downlink data received via the shared N3 tunnel and PTP resources of the MBS session. In one embodiment, RAN2 may switch to using PTM resources to transmit MBS (data).

[0186] In one embodiment, after the Xn handover, RAN1 may not support MBS, and SMF1 may not receive RAN node information from RAN2. In this embodiment, after the Xn handover, SMF1 initiates a PDU session modification procedure with RAN2 and sends a TMGI to RAN2 during the PDU session modification procedure. If RAN2 supports MBS, RAN2 returns RAN node information to SMF1 in the corresponding response message. Based on this RAN node information, SMF1 detects (e.g., determines) whether RAN2 supports MBS and / or whether an MBS session is active in RAN2. In one embodiment, SMF1 may also send notifications to NEF and / or AF, for example, to indicate the status of the MBS session in RAN2.

[0187] Figure 8A and 8B A schematic diagram of a process according to an embodiment of the present disclosure is shown. Note that UE, RAN1, RAN2, AMF1, SMF1, UPF1, and UPF2 can be as follows: Figure 1 Those shown. Figure 8A and 8B The process shown can be used to handle MBS sessions when a corresponding UE switches to a new RAN node via an N2-based handover procedure. In this embodiment, a forwarding tunnel for the MBS session is directly established between RAN1 and RAN2 to reduce packet loss during the handover process. In one embodiment, a data forwarding tunnel can be established using one or two UPFs.

[0188] More specifically, the UE receives MBS (e.g., MBS downlink data) via RAN1 through the MBS session (step 801), see [link to relevant documentation]. Figure 8A .

[0189] In step 802, based on radio measurements, RAN1 sends a handover request message to AMF1. This handover request message includes handover target information and N2 SM information. In one embodiment, the N2 SM information includes the PDU session context from which the handover is taking place. In another embodiment, the PDU session context includes a TMGI from which the UE is authorized to receive the associated MBS. In yet another embodiment, based on the MBS session's QoS profile, the N2 SM information may further include information indicating whether data forwarding is needed to reduce packet loss in the MBS session.

[0190] In step 803, AMF1 sends an Nsmf_PDUSession_UpdateSMContext request to SMF1. In one embodiment, this request includes target information and N2 SM information received from RAN1.

[0191] In step 804, based on the target information, SMF1 checks (e.g., detects or determines) whether a handover (e.g., N2 handover) for the indicated PDU session is acceptable. If the handover is acceptable, SMF1 returns an Nsmf_PDUSession_UpdateSMContext response (e.g., including N2 SM information) to AMF1. In one embodiment, the N2 SM information includes the PDU session context in which the handover takes place, and the TMGI is included in that PDU session context, from which the UE is authorized to receive the associated MBS. In one embodiment, the N2 SM information may also include information indicating whether data forwarding is needed to reduce packet loss in the MBS session.

[0192] In step 805, AMF1 sends a handover request to RAN2 (e.g., including N2 SM information). Note that the N2 SM information is received from SMF1.

[0193] In step 806, RAN2 reserves radio resources for the QoS profile of the PDU session received in step 805. In one embodiment, RAN2 allocates RAN N3 tunnel information for each received PDU session. In one embodiment, if RAN2 supports MBS and needs to forward data for the MBS session, RAN2 allocates a data forwarding tunnel for the MBS session. If the MBS session is activated in RAN2, RAN2 also allocates PTP radio resources based on the QoS profile of the MBS session.

[0194] exist Figure 8AIn this process, RAN2 returns a handover request ACK to AMF1 (e.g., including target-to-source transparent container and / or N2SM information). In one embodiment, the target-to-source transparent container includes information on all radio resources successfully reserved for the UE in RAN2. In embodiments where an MBS session is activated in RAN2, the target-to-source transparent container may further include PTP radio resources and / or PTM radio resources of the MBS session identified by the TMGI. In one embodiment, the N2SM information includes RANN3 tunnel information for the PDU session. In one embodiment, the N2SM information may further include RAN node information and data forwarding tunnel information allocated to the MBS session in RAN2. In one embodiment, the RAN node information includes the TMGI. In one embodiment, the RAN node information indicates whether the MBS session is activated in RAN2 (e.g., the status of the MBS session in RAN2).

[0195] In step 807, AMF1 sends an Nsmf_PDUSession_UpdateSMContext request (e.g., including N2 SM information) to SMF1. In one embodiment, SMF1 may also send notifications (e.g., messages) to NEF and / or AF based on RAN node information. In one embodiment, when RAN node information is not received from RAN2, SMF detects (e.g., determines) that target RAN2 does not support MBS.

[0196] In step 808, SMF1 returns an Nsmf_PDUSession_UpdateSMContext response (e.g., including N2SM information). In one embodiment, the N2SM information may include information about the data forwarding tunnel for the MBS session in RAN2.

[0197] In step 809, AMF1 sends a handover command to RAN1 (e.g., including target-to-source transparent container and / or N2SM information).

[0198] In step 810, RAN1 sends a handover command to the UE. In one embodiment, the handover command includes radio resources received from RAN2 by the target-to-source transparent container.

[0199] In step 811, if data forwarding for the MBS session is required, RAN1 forwards the MBS downlink data received from UPF2 to RAN2 via the data forwarding tunnel, and RAN2 begins buffering the MBS downlink data received via the data forwarding tunnel. In one embodiment, RAN1 may start a timer associated with forwarding the MBS downlink data.

[0200] In step 812, based on the radio resources received from RAN1, the UE accesses RAN2 and sends a handover confirmation to RAN2, see [link to relevant documentation]. Figure 8B .

[0201] In step 813, if PTP radio resources are reserved, RAN2 transmits the buffered MBS downlink data to the UE. In one embodiment, in step 810, if PTP radio resources are not reserved and the UE receives PTM radio resources from RAN1, the UE receives MBS downlink data from RAN2 via the PTM radio resources.

[0202] In step 814, RAN2 sends a handover notification to (e.g., toward) AMF1.

[0203] In step 815, AMF1 sends an Nsmf_PDUSSession_UpdateSMContext request to (e.g., toward) SMF1 to notify that the handover is complete.

[0204] In step 816, SMF1 sends an N4 session modification to UPF1 to update the RAN N3 tunnel information in UPF1.

[0205] In step 817, SMF1 returns an Nsmf_PDUSession_UpdateSMContext response to AMF1.

[0206] In step 818, AMF sends a resource release (message) to RAN1 to confirm a successful handover.

[0207] In step 819, the state of the MBS session changes after the handover, and RAN2 sends a notification to AMF1 (e.g., a message including RAN node information). In one embodiment, the RAN node information includes TMGI. In another embodiment, the RAN node information indicates whether the MBS session is active in RAN2 (e.g., the state of the MBS session in RAN2). In yet another embodiment, AMF1 also forwards the notification to SMF1.

[0208] In step 820, if a timer was set in step 811 and the timer expires, RAN1 sends an end marker to RAN2 via the data forwarding tunnel. In one embodiment, the end marker is configured to trigger the release of resources allocated to RAN1.

[0209] In step 821, after receiving the end marker, RAN2 releases the data forwarding tunnel and begins transmitting MBS downlink data received via the shared N3 tunnel of the MBS session via PTP resources. In one embodiment, RAN2 may switch to using PTM resources to transmit MBS (i.e., MBS downlink data).

[0210] Figure 9 A schematic diagram of a process according to an embodiment of the present disclosure is shown. Note that UE, RAN1, RAN2, SMF1, UPF1, SMF2, UPF2, NEF, and AF can be as follows: Figure 1 Those shown. Figure 9 The illustrated procedure can be used to process MBS sessions when a UE switches to a new RAN (e.g., RAN2) via an Xn / N2-based handover procedure. In this embodiment, the SMF1 detects (e.g., determines) that the target RAN (e.g., RAN2) supports MBS, and the TMGI's MBS session is not active in the target RAN. In this case, the SMF1 notifies the NEF / AF, and the AF can activate the MBS session in RAN2.

[0211] Specifically, RAN1 performs an Xn-based handover or an N2-based handover to switch the UE to RAN2 (step 901). In one embodiment, RAN2 supports the MBS identified by the TMGI but does not have an MBS session context with the TMGI. In one embodiment, MBS downlink data can be forwarded from RAN1 to RAN2, and RAN2 buffers the forwarded MBS downlink data. Because RAN2 does not have the corresponding MBS session context, RAN2 cannot allocate PTP resources and / or PTM resources for the MBS session to RAN1.

[0212] In step 902, during the 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 in RAN2. In this case, SMF1 sends a notification (message) to NEF. In one embodiment, the notification includes at least one of the following items: the UE's ID, TMGI, or RAN node information. In one embodiment, the RAN node information references (e.g., includes) TMGI. In one 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 in the serving RAN).

[0213] In step 903, NEF also sends a notification (message) to AF.

[0214] In step 904, based on the received notification, the AF determines to activate an MBS session in RAN2. In this embodiment, the AF determines a new MBS area covering RAN2 and sends a session modification request (e.g., including the new MBS area) to the NEF.

[0215] In step 905, NEF sends a session modification request to SMF2 to activate the MBS session on the new MBS area.

[0216] In step 906, SMF2 initiates an MBS session modification procedure to activate the MBS session in the new MBS area. During the MBS session modification procedure, RAN2 allocates the PTP radio resources of the MBS session to the UE.

[0217] In step 907, after the MBS session modification process is successful, SMF2 sends a session modification ACK to NEF.

[0218] In step 908, NEF sends a session modification ACK to AF.

[0219] In step 909, after activating the MBS session in RAN2, RAN2 transmits the buffered MBS downlink data received from RAN1 via PTP radio resources. Furthermore, RAN2 begins receiving MBS downlink data from UPF2 via the shared N3 tunnel of the MBS session.

[0220] In step 910, after the timer associated with RAN1 forwarding MBS downlink data to RAN2 expires, RAN1 sends an end marker to RAN2 via the data forwarding tunnel for forwarding MBS downlink data. In one embodiment, the end marker is configured to trigger the release of resources allocated to RAN1.

[0221] In step 911, after receiving the end marker, RAN2 releases the data forwarding tunnel and transmits the MBS downlink data received via the shared N3 tunnel of the MBS session via PTP radio resources. In one embodiment, RAN2 may switch to using PTM radio resources to deliver MBS (i.e., MBS downlink data).

[0222] Figure 10 A schematic diagram of a process according to an embodiment of the present disclosure is shown. Note that... Figure 10 The UE, RAN1, RAN2, SMF1, UPF1, PCF, NEF, and AF shown can be as follows: Figure 1 Those shown. Figure 10 The illustrated procedure can be used to process MBS sessions when a UE switches 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 use a unicast PDU session to deliver MBS to the UE.

[0223] Specifically, RAN1 performs a handover based on Xn or a handover based on N2, which is associated with moving the UE to RAN2 (step 1001).

[0224] In step 1002, during the Xn / N2-based handover, SMF1 detects (e.g., determines) that the target RAN (i.e., RAN2) does not support MBS. In this case, SMF1 sends a notification (message) to NEF. In one embodiment, the notification includes at least one of the following items: UE ID, TMGI, or RAN node information. In one embodiment, the RAN node information indicates that the target RAN (i.e., RAN2) does not support MBS (e.g., the status of the MBS session corresponding to the MBS identified by the TMGI in RAN2).

[0225] In step 1003, NEF also sends a notification to AF.

[0226] In step 1004, based on the information in the received notification, the AF determines to use a unicast PDU session instead of an MBS session to deliver MBS (i.e., MBS downlink data). In this embodiment, the AF sends an AF request with new service requirements to the NEF to request modification of the PDU session.

[0227] In step 1005, NEF forwards the AF request to PCF.

[0228] In step 1006, PCF initiates an SM association update process with SMF1 to modify the PDU session.

[0229] In step 1007, SMF1 initiates a PDU session modification to add new QoS flows and / or modify existing QoS flows in the PDU session.

[0230] In step 1008, after the PDU session is successfully modified, SMF1 sends an SM association update ACK to PCF.

[0231] In step 1009, the PCF sends an AF request ACK to the NEF.

[0232] In step 1010, NEF sends an AF request ACK to AF.

[0233] In step 1011, the AF uses a unicast PDU session to transmit MBS (i.e., MBS downlink data) to the UE.

[0234] Figure 11 A flowchart of a process according to an embodiment of the present disclosure is shown. This process can be used in a first wireless network node (e.g., Figure 1 As shown in RAN1), and includes the following steps.

[0235] Step 1101: Receive the temporary mobile group identifier associated with the multicast / broadcast service and the wireless terminal from the first session management function.

[0236] Step 1102: Receive a request from the second session management function to activate a multicast / broadcast service session corresponding to the temporary mobile group identifier.

[0237] Step 1103: Send a message to the first session management function, the message including information indicating the status of the multicast / broadcast service session in the first wireless network node.

[0238] exist Figure 11 In the process shown, the first wireless network node receives data from the first SMF (e.g., Figure 1 The SMF1 shown receives the TMGI associated with the MBS and the radio terminal (e.g., UE). Furthermore, the first radio network node receives a request to activate the MBS session corresponding to the TMGI (e.g., identified by the TMGI). In this case, the first radio network node sends a message to the first SMF including information indicating the status of the MBS session in the first radio network node (e.g., RAN node information). Regarding... Figure 11 For details of the process shown, please refer to steps 506, 606 and 614, for example. For the sake of brevity, the details disclosed therein will not be described here.

[0239] In one embodiment, the TMGI sent to the first wireless network node indicates that the wireless terminal is authorized to receive data from the MBS corresponding to the TMGI.

[0240] In one embodiment, the information indicating the state of a multicast / broadcast service session corresponding to a TMGI includes the TMGI itself.

[0241] In one embodiment, the first wireless network also sends signals to a second wireless network node (e.g., Figure 1 The RAN2 shown sends a handover request, which includes TMGI.

[0242] In one embodiment, after sending a handover request, the first wireless network node receives information about the forwarding tunnel from the second wireless network node and sends MBS data to the second wireless network node via the forwarding tunnel.

[0243] In one embodiment, the first wireless network node may set a timer associated with sending MBS data to the second wireless network node via a forwarding tunnel. When the timer expires, the first wireless network node sends an end marker to the second wireless network node.

[0244] In one embodiment, after sending a handover request, the first wireless network node receives at least one radio resource for transmitting MBS data. In one embodiment, the at least one radio resource includes at least one of PTP radio resources or PTM radio resources. In one embodiment, the first wireless network node transmits the at least one resource to the wireless terminal.

[0245] Figure 12 A flowchart of a process according to an embodiment of the present disclosure is shown. Figure 12 The process shown can be used for a second wireless network node (e.g., Figure 1 As shown in RAN2), and includes the following steps.

[0246] Step 1201: Receive a handover request from the first wireless network node, the handover request including a temporary mobile group identifier.

[0247] Step 1202: Send a message to the session management function, the message including information indicating the status of the multicast / broadcast service session corresponding to the temporary mobile group identifier in the second radio network node.

[0248] exist Figure 12 In this process, the second wireless network node receives data from the first wireless network node (e.g., ...). Figure 1 The RAN1 shown receives a handover request including the TMGI. In this embodiment, the second radio network node sends a message including information (e.g., RAN node information) indicating the status of the MBS session corresponding to the TMGI within the second radio network node. Regarding... Figure 12 For details of the process shown, please refer to steps 702 and 714, for example. For the sake of brevity, the contents disclosed therein will not be repeated here.

[0249] In one embodiment, the information indicating the state of the MBS session corresponding to the TMGI includes the TMGI.

[0250] In one embodiment, the second wireless network node sends forwarding tunnel information to the first wireless network node and receives data corresponding to the TMGI (e.g., the MBS identified by the TMGI) via the forwarding tunnel. In another embodiment, the second wireless network node receives an end marker via the forwarding tunnel and releases the resources of the forwarding tunnel pointing to the first wireless network node.

[0251] In one embodiment, the second wireless network node further transmits at least one radio resource to the first wireless network node for transmitting data for multicast / broadcast services. In one embodiment, the at least one radio resource includes at least one of PTP radio resources or PTM radio resources. In one embodiment, the second wireless network node transmits MBS data corresponding to TMGI via the at least one radio resource.

[0252] Figure 13 A flowchart of a process according to an embodiment of the present disclosure is shown. Figure 13 The process shown can be used in SMF (e.g., Figure 1 The SMF1 or SMF2 shown is included, and the following steps are also included.

[0253] Step 1301: Send a temporary mobile group identifier to the wireless network node, which is associated with the multicast / broadcast service and the wireless terminal.

[0254] Step 1302: Receive a first message from the serving radio network node of the wireless terminal, the first message including information indicating the status of a multicast / broadcast service session corresponding to a temporary mobile group identifier in the serving radio network node.

[0255] Step 1303: Based on the state of the multicast / broadcast service session in the serving wireless network node, send a notification to at least one network function.

[0256] exist Figure 13 In the process, SMF directs data to wireless network nodes (e.g., Figure 1 The RAN1 and / or RAN2 shown transmit the TMGI associated with the MBS and the radio terminal (e.g., UE). In this embodiment, the SMF receives a message from the serving radio network node (e.g., RAN1 or RAN2) of the radio terminal, which includes information (e.g., RAN node information) indicating the status of the MBS session corresponding to the TMGI in the serving radio network node. Furthermore, the SMF sends notifications based on the status of the multicast / broadcast service sessions in the serving radio network node. Regarding... Figure 13 For details of the process shown, please refer to steps 507, 615 to 618, for example. For the sake of brevity, the disclosed content will not be described here.

[0257] In one embodiment, a temporary mobile group identifier is sent to indicate that the wireless terminal is authorized to receive data corresponding to the MBS of the TMGI.

[0258] In one embodiment, the at least one network function includes at least one of NEF or AF.

[0259] In one embodiment, the information indicating the state of the MBS session corresponding to the TMGI includes the TMGI.

[0260] In one embodiment, the notification includes at least one of the following items: the identifier of the wireless terminal (e.g., UEID), TMGI, or information indicating the status of the MBS session in the serving wireless network node.

[0261] Figure 14A flowchart of a process according to an embodiment of the present disclosure is shown. Figure 14 The process shown can be used for network functions (e.g.) Figure 1 The NEF or AF shown includes the following steps.

[0262] Step 1401: Send a request to the session management function that has deployed the broadcast / multicast service center. This request is used to activate the multicast / broadcast service session corresponding to the temporary mobile group identifier.

[0263] Step 1402: Receive a notification from the service session management function of the wireless terminal, which is associated with the status of the multicast / broadcast service session in the service wireless network node of the wireless terminal.

[0264] exist Figure 14 In this context, network functions are directed to the SMF associated with the BMSC (e.g., Figure 1 The SMF2 shown sends a request to activate the MBS session, wherein the request includes a TMGI corresponding to the MBS session. In this embodiment, the network function receives information from the serving SMF (e.g., SMF1) of the wireless terminal (e.g., UE) and the serving wireless network node (e.g., ...). Figure 1 Notifications related to the status of the MBS session in RAN1 or RAN2 (as shown). Regarding Figure 14 For details of the process shown, please refer to steps 606, 617 and 618, for example. For the sake of brevity, the contents disclosed therein will not be described here.

[0265] In one embodiment, the network function includes at least one of NEF or AF.

[0266] In one embodiment, the notification includes at least one of the following: the identifier of the wireless terminal, TMGI, or information indicating the MBS session status in the serving wireless network node.

[0267] In one embodiment, based on the notification, a network function triggers (e.g., executes) at least one of an MBS modification or switch to transmit MBS data to the wireless terminal using a unicast packet data unit session. In this embodiment, MBS corresponds to TMGI.

[0268] While various embodiments of this disclosure have been described above, it should be understood that these embodiments are presented by way of example only and not by way of limitation. Similarly, various figures may depict exemplary architectures or configurations, and these figures are provided to enable those skilled in the art to understand the exemplary features and functions of this disclosure. However, those skilled in the art should understand that this disclosure is not limited to the example architectures or configurations shown, but can be implemented using various alternative architectures and configurations. Furthermore, as will be understood by those skilled in the art, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of this disclosure should not be limited to any of the exemplary embodiments described above.

[0269] It should also be understood that any reference to elements in this document using names such as "first," "second," etc., generally does not restrict the number or order of these elements. Rather, these names may be used herein as a convenient means of distinguishing two or more elements or instances of elements. Therefore, references to first and second elements do not imply that only two elements can be used, or that the first element must somehow precede the second element.

[0270] Furthermore, those skilled in the art will understand that information and signals can be represented using any of a variety of different technologies and processes. For example, data, instructions, commands, information, signals, bits, and symbols referenced in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0271] Those skilled in the art will also understand that any of the various illustrative logic blocks, units, processors, devices, circuits, methods, and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code containing instructions (referred to herein as “software” or “software unit” for convenience), or any combination of these processes.

[0272] To clearly illustrate this interchangeability of hardware, firmware, and software, it has been generally described above in terms of the functionality of various illustrative components, blocks, units, circuits, and steps. Whether this functionality is implemented as hardware, firmware, or software, or a combination of these processes, depends on the specific application and design constraints of the system as a whole. Those skilled in the art can implement the described functionality in various ways for each specific application, but such implementation decisions will not depart from the scope of this disclosure. According to various embodiments, processors, devices, components, circuits, structures, machines, units, etc., can be configured to perform one or more of the functions described herein. The terms “configured to” or “configured for” as used herein in relation to a particular operation or function mean that the processor, device, component, circuit, structure, machine, unit, etc., is physically constructed, programmed, and / or set up to perform the particular operation or function.

[0273] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, cells, devices, components, and circuits described herein can be implemented within or executed by an integrated circuit (IC), which 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. Logic blocks, cells, and circuits may also include antennas and / or transceivers for communicating with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, it may also be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration performing the functions described herein. If implemented in software, these functions may be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium.

[0274] Computer-readable media include computer storage media and communication media, including any medium capable of transferring computer programs or code from one place to another. Storage media can be any available medium that is accessible to a computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage 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 that is accessible to a computer.

[0275] In this document, the term "unit" refers to software, firmware, hardware, and any combination of these elements used to perform the relevant functions described herein. Furthermore, for ease of discussion, various units are described as discrete units; however, it will be apparent to those skilled in the art that two or more units can be combined to form a single unit that performs the relevant functions according to embodiments of this disclosure.

[0276] Furthermore, memories or other storage devices and communication components may be employed in the embodiments of this disclosure. It should be understood that, for clarity, the above description has referenced various functional units and processors in the embodiments of this disclosure. However, it will be apparent that any suitable functional distribution among different functional units, processing logic elements, or domains may be used without departing from 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. Therefore, references to specific functional units are merely references to suitable means for providing said function and do not indicate a strict logical or physical structure or organization.

[0277] Various modifications to the implementations described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other implementations without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the implementations shown herein, but rather to be consistent with the widest scope of the novel features and principles disclosed herein, as set forth in the following claims.

Claims

1. A wireless communication method, the method being performed by a first wireless network node, the method comprising: Receive a temporary mobile group identifier from the first session management function. This temporary mobile group identifier is associated with a multicast / broadcast service and a wireless terminal. A request is received from the second session management function, the request being used to activate a multicast / broadcast service session corresponding to the temporary mobile group identifier, and Send a message to the first session management function, the message including first wireless network node information, the first wireless network node information indicating whether the first wireless network node supports multicast / broadcast services.

2. The wireless communication method according to claim 1, wherein, The temporary mobile group identifier indicates that the wireless terminal is authorized to receive data from the multicast / broadcast service corresponding to the temporary mobile group identifier.

3. The wireless communication method according to claim 1, wherein, The information indicating the state of the multicast / broadcast service session corresponding to the temporary mobile group identifier includes the temporary mobile group identifier.

4. The wireless communication method according to claim 1, further comprising: A handover request is sent to the second wireless network node, the handover request including the temporary mobile group identifier.

5. The wireless communication method according to claim 4, further comprising: Receive information about the forwarding tunnel from the second wireless network node, and The multicast / broadcast service data is sent to the second wireless network node via the forwarding tunnel.

6. The wireless communication method according to claim 5, further comprising: An end marker is sent to the second wireless network node after the timer expires, wherein the timer is associated with sending the multicast / broadcast service data to the second wireless network node via the forwarding tunnel.

7. The wireless communication method according to claim 4, further comprising: Receive at least one wireless resource from the second wireless network node, the at least one wireless resource being used to transmit data for the multicast / broadcast service.

8. The wireless communication method according to claim 7, further comprising: Send at least one wireless resource of the multicast / broadcast service to the wireless terminal.

9. The wireless communication method according to claim 7 or 8, wherein, The at least one radio resource includes at least one of point-to-point radio resources or point-to-multipoint radio resources.

10. A wireless communication method, the method being performed by a second wireless network node, the method comprising: A handover request is received from the first wireless network node, the handover request including a temporary mobile group identifier, and A message is sent to the session management function, the message including information indicating the status of a multicast / broadcast service session in the second radio network node corresponding to the temporary mobile group identifier.

11. The wireless communication method according to claim 10, wherein, Information indicating the state of the multicast / broadcast service session corresponding to the temporary mobile group identifier includes the temporary mobile group identifier.

12. The wireless communication method according to claim 10, further comprising: Send the forwarding tunnel information to the first wireless network node, and Data corresponding to the temporary mobile group identifier of the multicast / broadcast service is received from the first wireless network node via the forwarding tunnel.

13. The wireless communication method according to claim 12, further comprising: Receive an end marker from the first wireless network node via the forwarding tunnel, and Release the resources of the forwarding tunnel pointing to the first wireless network node.

14. The wireless communication method according to claim 10, further comprising: At least one radio resource is sent to the first wireless network node, the at least one radio resource being used to send data for the multicast / broadcast service.

15. The wireless communication method according to claim 14, wherein, The at least one radio resource includes at least one of point-to-point radio resources or point-to-multipoint radio resources.

16. The wireless communication method according to claim 14 or 15, further comprising: Data of the multicast / broadcast service corresponding to the temporary mobile group identifier is transmitted to the wireless terminal via the at least one radio resource.

17. A wireless communication method, the method being performed by a session management function, the method comprising: A temporary mobile group identifier is sent to the wireless network node. This temporary mobile group identifier is associated with multicast / broadcast services and wireless terminals. The wireless terminal receives a message from its serving radio network node, the message including information indicating the status of a multicast / broadcast service session corresponding to the temporary mobile group identifier in the serving radio network node, and... Based on the state of the multicast / broadcast service sessions in the service wireless network node, a notification is sent to at least one network function.

18. The wireless communication method according to claim 17, wherein, The temporary mobile group identifier indicates that the wireless terminal is authorized to receive data from the multicast / broadcast service corresponding to the temporary mobile group identifier.

19. The wireless communication method according to claim 17, wherein, The at least one network function includes at least one of network openness function or application function.

20. The wireless communication method according to claim 17, wherein, The information indicating the state of the multicast / broadcast service session corresponding to the temporary mobile group identifier includes the temporary mobile group identifier.

21. The wireless communication method according to any one of claims 17 to 20, wherein, The notification includes at least one of the following: the identifier of the wireless terminal, the temporary mobile group identifier, or information indicating the status of the multicast / broadcast service session in the serving wireless network node.

22. A wireless communication method, the wireless communication method being performed by a network function, the wireless communication method comprising: A request is sent to the session management function associated with the broadcast / multicast service center, the request being used to activate a multicast / broadcast service session corresponding to a temporary mobile group identifier, and A notification is received from the service session management function of the wireless terminal, the notification being associated with the status of the multicast / broadcast service session in the service wireless network node of the wireless terminal.

23. The wireless communication method according to claim 22, wherein, The network function includes at least one of network open function or application function.

24. The wireless communication method according to claim 22, wherein, The notification includes at least one of the following: the identifier of the wireless terminal, the identifier of the temporary mobile group, or information indicating the status of the multicast / broadcast service session in the first wireless network node.

25. The wireless communication method according to any one of claims 22 to 24, further comprising: Based on the notification, at least one of the following is triggered: multicast / broadcast service session modification or switching, to send multicast / broadcast service data to the wireless terminal via a unicast packet data unit session. The multicast / broadcast service mentioned therein corresponds to the temporary mobile group identifier.

26. A first wireless network node, comprising: The communication unit is configured as follows: Receive a temporary mobile group identifier from the first session management function. This temporary mobile group identifier is associated with a multicast / broadcast service and a wireless terminal. A request is received from the second session management function, the request being used to activate a multicast / broadcast service session corresponding to the temporary mobile group identifier, and A message is sent to the first session management function, the message including first wireless network node information, the first wireless network node information indicating whether the first wireless network node supports the multicast / broadcast service.

27. The first wireless network node of claim 26, further comprising a processor configured to perform the wireless communication method of any one of claims 2 to 9.

28. A second wireless network node, comprising: The communication unit is configured as follows: A handover request is received from the first wireless network node, the handover request including a temporary mobile group identifier, and A message is sent to the session management function, the message including information indicating the status of a multicast / broadcast service session in the second radio network node corresponding to the temporary mobile group identifier.

29. The second wireless network node of claim 28, further comprising a processor configured to perform the wireless communication method of any one of claims 11 to 16.

30. A wireless device, comprising: The communication unit is configured as follows: A temporary mobile group identifier is sent to the wireless network node. This temporary mobile group identifier is associated with multicast / broadcast services and wireless terminals. The wireless terminal receives a message from its serving radio network node, the message including information indicating the status of a multicast / broadcast service session corresponding to the temporary mobile group identifier in the serving radio network node, and... Based on the state of the multicast / broadcast service session in the serving wireless network node, a notification is sent to at least one network function.

31. The wireless device of claim 30, further comprising a processor configured to perform the wireless communication method of any one of claims 18 to 21.

32. A wireless device, comprising: The communication unit is configured as follows: A request is sent to the session management function, which is associated with the broadcast / multicast service center, to activate a multicast / broadcast service session corresponding to a temporary mobile group identifier. A notification is received from the service session management function of the wireless terminal, the notification being associated with the status of the multicast / broadcast service session in the service wireless network node of the wireless terminal.

33. The wireless device of claim 32, further comprising a processor configured to perform the wireless communication method of any one of claims 23 to 25.

34. A computer program product comprising computer-readable program medium code stored thereon, the code, when executed by a processor, causing the processor to perform the wireless communication method as claimed in any one of claims 1 to 25.

Images