[go: up one dir, main page]

WO2024156159A1 - Systèmes et procédés d'association de session de services de multidiffusion et de diffusion (mbs) - Google Patents

Systèmes et procédés d'association de session de services de multidiffusion et de diffusion (mbs) Download PDF

Info

Publication number
WO2024156159A1
WO2024156159A1 PCT/CN2023/093171 CN2023093171W WO2024156159A1 WO 2024156159 A1 WO2024156159 A1 WO 2024156159A1 CN 2023093171 W CN2023093171 W CN 2023093171W WO 2024156159 A1 WO2024156159 A1 WO 2024156159A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
network node
network
association
mbs
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/093171
Other languages
English (en)
Inventor
Zhendong Li
Xiaojian YAN
Jinguo Zhu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to PCT/CN2023/093171 priority Critical patent/WO2024156159A1/fr
Priority to CN202380097989.XA priority patent/CN121079996A/zh
Publication of WO2024156159A1 publication Critical patent/WO2024156159A1/fr
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services

Definitions

  • the disclosure relates generally to wireless communications, including but not limited to systems and methods for multicast and broadcast services (MBS) session association.
  • MMS multicast and broadcast services
  • the standardization organization Third Generation Partnership Project (3GPP) is currently in the process of specifying a new Radio Interface called 5G New Radio (5G NR) as well as a Next Generation Packet Core Network (NG-CN or NGC) .
  • the 5G NR will have three main components: a 5G Access Network (5G-AN) , a 5G Core Network (5GC) , and a User Equipment (UE) .
  • 5G-AN 5G Access Network
  • 5GC 5G Core Network
  • UE User Equipment
  • the elements of the 5GC also called Network Functions, have been simplified with some of them being software based, and some being hardware based, so that they could be adapted according to need.
  • example embodiments disclosed herein are directed to solving the issues relating to one or more of the problems presented in the prior art, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompany drawings.
  • example systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these embodiments are presented by way of example and are not limiting, and it will be apparent to those of ordinary skill in the art who read the present disclosure that various modifications to the disclosed embodiments (e.g., including combining features from various disclosed examples, embodiments and/or implementations) can be made while remaining within the scope of this disclosure.
  • a first network node may receive a first message requesting to establish a first network session (e.g., an application function (AF) /N5 session) from a second network node (e.g., an application function (AF) , a network exposure function (NEF) , or a Multicast/Broadcast Service Function (MBSF) ) .
  • the first message may include an association request indication.
  • the first network node may send a second message including an Association ID in response to receiving the association request indication.
  • the first network node may receive a third message requesting to establish a second network session (e.g., multicast and broadcast services (MBS) /N7 session) from a third network node (e.g., a multicast-broadcast session management function (MB-SMF) ) .
  • the third message may include the Association ID.
  • the first network node may associate the first network session with the second network session based at least on the Association ID.
  • a N5 session/AF session can be between AF/NEF/MBSF and PCF.
  • the N5 session/AF session may be not only used for MBS service, but also used for other services, e.g., internet, IMS, vertical industry, or IoT.
  • a N7 session/SM policy association can be between SMF/MB-SMF and PCF.
  • the N7 session/SM policy association may be not only used for MBS session, but also used for other PDU sessions.
  • There can be a signaling path for the MBS session (e.g., from AF/NEF/MBSF to MB-SMF to AMF to NG-RAN) .
  • the association request indication can be a location dependent indication.
  • the first network node may include a Policy Control Function (PCF) .
  • the second network node may include one of an Application Function (AF) , a Network Exposure Function (NEF) , or a Multicast/Broadcast Service Function (MBSF) .
  • the third network node may include a Multicast-Broadcast Session Management Function (MB-SMF) .
  • the first network session may include an AF session, and the second network session may include an SM Policy Association.
  • the first message may further include a Multicast/Broadcast Service (MBS) session ID, and optional MBS Service Information.
  • MBS Multicast/Broadcast Service
  • the first network node may generate the Association ID for the second network session based on at least one of: the association request indication, the MBS session ID, or the optional MBS Service Information.
  • the second network node may send the Association ID, together with the MSB session ID, to the third network node.
  • the first network node may associate the first network session with the second network session further at least based on the Association ID.
  • the third network node can be configured to allocate an Area session ID and send the Area session ID to the first network node.
  • the first network node can be configured to store the Area session ID, together with the Association ID, for the second network session.
  • the first network node may receive a fourth message requesting to update the first network session from the second network node.
  • the fourth message may include the Association ID.
  • the first network node may receive a fifth message requesting to update the second network session from the third network node.
  • the fifth message may include the Association ID.
  • a second network node may send a first message requesting to establish a first network session to a first network node.
  • the first message may include an association request indication.
  • the second network node may receive a second message including an Association ID in response to the first network node receiving the association request indication from the first network node.
  • the second network node may send a third message requesting to establish a third network session between the second network node and the third network node to a third network node.
  • the third message may include the Association ID.
  • the first network session and a second network session can be configured to be associated with each other based at least on the Association ID.
  • the third network node may send a fourth message requesting to establish a second network session to the first network node.
  • the first network session may include an AF session
  • the second network session may include an SM Policy Association.
  • FIG. 1 illustrates an example cellular communication network in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure
  • FIG. 2 illustrates a block diagram of an example base station and a user equipment device, in accordance with some embodiments of the present disclosure
  • FIG. 3 illustrates an example multicast and broadcast services (MBS) architecture, in accordance with some embodiments of the present disclosure
  • FIG. 4 illustrates a sequence diagram for a multicast and broadcast services (MBS) session creation procedure, in accordance with some embodiments of the present disclosure
  • FIG. 5 illustrates a sequence diagram for a session binding issue for a location dependent multicast and broadcast services (MBS) session, in accordance with some embodiments of the present disclosure
  • FIG. 6 illustrates a sequence diagram for a multicast and broadcast services (MBS) session creation procedure, in accordance with some embodiments of the present disclosure
  • FIG. 7 illustrates a sequence diagram for a multicast and broadcast services (MBS) session update procedure, in accordance with some embodiments of the present disclosure.
  • MMS multicast and broadcast services
  • FIG. 8 illustrates a flow diagram for multicast and broadcast services (MBS) session association, in accordance with an embodiment of the present disclosure.
  • MMS multicast and broadcast services
  • FIG. 1 illustrates an example wireless communication network, and/or system, 100 in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure.
  • the wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of things (NB-IoT) network, and is herein referred to as “network 100.
  • NB-IoT narrowband Internet of things
  • Such an example network 100 includes a base station 102 (hereinafter “BS 102” ; also referred to as wireless communication node) and a user equipment device 104 (hereinafter “UE 104” ; also referred to as wireless communication device) that can communicate with each other via a communication link 110 (e.g., a wireless communication channel) , and a cluster of cells 126, 130, 132, 134, 136, 138 and 140 overlaying a geographical area 101.
  • the BS 102 and UE 104 are contained within a respective geographic boundary of cell 126.
  • Each of the other cells 130, 132, 134, 136, 138 and 140 may include at least one base station operating at its allocated bandwidth to provide adequate radio coverage to its intended users.
  • the BS 102 may operate at an allocated channel transmission bandwidth to provide adequate coverage to the UE 104.
  • the BS 102 and the UE 104 may communicate via a downlink radio frame 118, and an uplink radio frame 124 respectively.
  • Each radio frame 118/124 may be further divided into sub-frames 120/127 which may include data symbols 122/128.
  • the BS 102 and UE 104 are described herein as non-limiting examples of “communication nodes, ” generally, which can practice the methods disclosed herein. Such communication nodes may be capable of wireless and/or wired communications, in accordance with various embodiments of the present solution.
  • FIG. 2 illustrates a block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM/OFDMA signals) in accordance with some embodiments of the present solution.
  • the system 200 may include components and elements configured to support known or conventional operating features that need not be described in detail herein.
  • system 200 can be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment such as the wireless communication environment 100 of Figure 1, as described above.
  • the System 200 generally includes a base station 202 (hereinafter “BS 202” ) and a user equipment device 204 (hereinafter “UE 204” ) .
  • the BS 202 includes a BS (base station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each module being coupled and interconnected with one another as necessary via a data communication bus 220.
  • the UE 204 includes a UE (user equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each module being coupled and interconnected with one another as necessary via a data communication bus 240.
  • the BS 202 communicates with the UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for transmission of data as described herein.
  • system 200 may further include any number of modules other than the modules shown in Figure 2.
  • modules other than the modules shown in Figure 2.
  • Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are described generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software can depend upon the particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionality in a suitable manner for each particular application, but such implementation decisions should not be interpreted as limiting the scope of the present disclosure
  • the UE transceiver 230 may be referred to herein as an "uplink" transceiver 230 that includes a radio frequency (RF) transmitter and a RF receiver each comprising circuitry that is coupled to the antenna 232.
  • a duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in time duplex fashion.
  • the BS transceiver 210 may be referred to herein as a "downlink" transceiver 210 that includes a RF transmitter and a RF receiver each comprising circuity that is coupled to the antenna 212.
  • a downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in time duplex fashion.
  • the operations of the two transceiver modules 210 and 230 may be coordinated in time such that the uplink receiver circuitry is coupled to the uplink antenna 232 for reception of transmissions over the wireless transmission link 250 at the same time that the downlink transmitter is coupled to the downlink antenna 212. Conversely, the operations of the two transceivers 210 and 230 may be coordinated in time such that the downlink receiver is coupled to the downlink antenna 212 for reception of transmissions over the wireless transmission link 250 at the same time that the uplink transmitter is coupled to the uplink antenna 232. In some embodiments, there is close time synchronization with a minimal guard time between changes in duplex direction.
  • the UE transceiver 230 and the base station transceiver 210 are configured to communicate via the wireless data communication link 250, and cooperate with a suitably configured RF antenna arrangement 212/232 that can support a particular wireless communication protocol and modulation scheme.
  • the UE transceiver 210 and the base station transceiver 210 are configured to support industry standards such as the Long Term Evolution (LTE) and emerging 5G standards, and the like. It is understood, however, that the present disclosure is not necessarily limited in application to a particular standard and associated protocols. Rather, the UE transceiver 230 and the base station transceiver 210 may be configured to support alternate, or additional, wireless data communication protocols, including future standards or variations thereof.
  • LTE Long Term Evolution
  • 5G 5G
  • the BS 202 may be an evolved node B (eNB) , a serving eNB, a target eNB, a femto station, or a pico station, for example.
  • eNB evolved node B
  • the UE 204 may be embodied in various types of user devices such as a mobile phone, a smart phone, a personal digital assistant (PDA) , tablet, laptop computer, wearable computing device, etc.
  • PDA personal digital assistant
  • the processor modules 214 and 236 may be implemented, or realized, with a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein.
  • a processor may be realized as a microprocessor, a controller, a microcontroller, a state machine, or the like.
  • a processor may also be implemented as a combination of computing devices, e.g., a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.
  • the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in firmware, in a software module executed by processor modules 214 and 236, respectively, or in any practical combination thereof.
  • the memory modules 216 and 234 may be realized as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
  • memory modules 216 and 234 may be coupled to the processor modules 210 and 230, respectively, such that the processors modules 210 and 230 can read information from, and write information to, memory modules 216 and 234, respectively.
  • the memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230.
  • the memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during execution of instructions to be executed by processor modules 210 and 230, respectively.
  • Memory modules 216 and 234 may also each include non-volatile memory for storing instructions to be executed by the processor modules 210 and 230, respectively.
  • the network communication module 218 generally represents the hardware, software, firmware, processing logic, and/or other components of the base station 202 that enable bi-directional communication between base station transceiver 210 and other network components and communication nodes configured to communication with the base station 202.
  • network communication module 218 may be configured to support internet or WiMAX traffic.
  • network communication module 218 provides an 802.3 Ethernet interface such that base station transceiver 210 can communicate with a conventional Ethernet based computer network.
  • the network communication module 218 may include a physical interface for connection to the computer network (e.g., Mobile Switching Center (MSC) ) .
  • MSC Mobile Switching Center
  • the Open Systems Interconnection (OSI) Model (referred to herein as, “open system interconnection model” ) is a conceptual and logical layout that defines network communication used by systems (e.g., wireless communication device, wireless communication node) open to interconnection and communication with other systems.
  • the model is broken into seven subcomponents, or layers, each of which represents a conceptual collection of services provided to the layers above and below it.
  • the OSI Model also defines a logical network and effectively describes computer packet transfer by using different layer protocols.
  • the OSI Model may also be referred to as the seven-layer OSI Model or the seven-layer model.
  • a first layer may be a physical layer.
  • a second layer may be a Medium Access Control (MAC) layer.
  • MAC Medium Access Control
  • a third layer may be a Radio Link Control (RLC) layer.
  • a fourth layer may be a Packet Data Convergence Protocol (PDCP) layer.
  • PDCP Packet Data Convergence Protocol
  • a fifth layer may be a Radio Resource Control (RRC) layer.
  • a sixth layer may be a Non Access Stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer being the other layer.
  • RLC Radio Link Control
  • a fourth layer may be a Packet Data Convergence Protocol (PDCP) layer.
  • PDCP Packet Data Convergence Protocol
  • RRC Radio Resource Control
  • a sixth layer may be a Non Access Stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer being the other layer.
  • NAS Non Access Stratum
  • IP Internet Protocol
  • a session binding mechanism plays a crucial role in the context of Policy Control Function (PCF) operations.
  • PCF Policy Control Function
  • AF Application Function
  • NEF Network Exposure Function
  • M-SMF multicast-broadcast session management function
  • AF session can be equivalent to "N5 session”
  • SM policy association can be equivalent to "N7 session” .
  • MBS Mobile Broadcast Services
  • MBS session ID serves as a key element for MBS session binding within the PCF.
  • MBS session ID serves as a key element for MBS session binding within the PCF.
  • the existing session binding mechanism encounters challenges when dealing with location-dependent MBS sessions. In these scenarios, relying solely on the MBS session ID proves insufficient for accomplishing the session binding process. Additionally, the assignment of an area session ID by MB-SMF subsequent to the session binding does not provide a viable solution to address this limitation. In present disclosure, an accurate multiple and broadcast services session association can be performed.
  • FIG. 3 illustrates an example 5G multicast and broadcast services (MBS) architecture, in accordance with some embodiments of the present disclosure.
  • MBS multicast and broadcast services
  • common network functions may include: a user equipment (UE) , a next generation radio access network (NG-RAN) , an access and mobility management function (AMF) , a session management function (SMF) , a user plane function (UPF) , a unified data management (UDM) , a policy control function (PCF) , a network exposure function (NEF) , and an application function /application server (AF/AS) .
  • the user equipment (UE) can be accessing 5GS, may obtain services via NG-RAN, and may interact with the access and mobility control function (AMF) of a core network via a non-access stratum (NAS) signaling.
  • NAS non-access stratum
  • the NG-RAN (e.g., 5G Radio Access Network) can be responsible for air interface resource scheduling and air interface connection management of the network to which the UE is accessed to.
  • the Access and Mobility Management function may include the following functionalities: a registration management, a connection management, a reachability management, and a mobility management.
  • the AMF may also perform an access authentication and access authorization.
  • the AMF can be a NAS security termination and may relay the SM NAS between the UE and the SMF.
  • the Session Management function may include the following functionalities: a session management (e.g., session establishment, modify and release) , a UE IP address allocation and management, a selection and control of UP function, and a downlink data notification.
  • the user plane function may include the following functionalities: an anchor point for Intra-/Inter-radio access technology (RAT) mobility, a packet routing and forwarding, a traffic usage reporting, a QoS handling for user plane, and a downlink packet buffering and downlink data notification triggering.
  • the Unified Data Management may manage a subscription profile for the UEs. The subscription may include data used for mobility management, session management. The AMF and SMF may get a subscription from the UDM.
  • the Network Exposure Function (NEF) can be deployed optionally for exchanging information between 5G core network (5GC) and an external third party.
  • the Application Function /Application Server may provide a service over a 5G system.
  • MBS particular network function may include: a multicast-broadcast SMF (MB-SMF) , a multicast-broadcast UPF (MB-UPF) , a Multicast/Broadcast Service Function (MBSF) (optional) , and Multicast/Broadcast Service Transport Function (MBSTF) (optional) .
  • the multicast-broadcast SMF (MB-SMF) which is responsible for MBS session management, may include: QoS control, configuring the MB-UPF, interacting with SMF to modify PDU session associated with MBS session, and/or interacting with RAN (via AMF and SMF) to establish shared delivery tunnel (data transmission resources) between a MB-UPF and RAN nodes.
  • the multicast-broadcast UPF can be responsible for Packet filtering of incoming downlink packets for multicast and broadcast flows, QoS enforcement, and/or delivery of multicast and broadcast data to RAN nodes.
  • the Multicast/Broadcast Service Function may interact with AF and MB-SMF for MBS session operations, determination of transport parameters.
  • the MBSF may select MB-SMF to serve an MBS session, and control Multicast/Broadcast Service Transport Function (MBSTF) .
  • MBSTF Multicast/Broadcast Service Transport Function
  • the MBSTF may provide generic packet transport functionalities available to any IP multicast enabled application such as framing, multiple flows, and/or packet forward error correction (FEC) (encoding) .
  • FEC packet forward error correction
  • the MBS session/service can be identified by an MBS session ID.
  • MBS session ID There can be two kinds of MBS session IDs: a Temporary Mobile Group Identity (TMGI) and a Source Specific Multicast (SSM) address.
  • TMGI Temporary Mobile Group Identity
  • SSM Source Specific Multicast
  • a MBS session ID, a TMGI, and a SSM address can be equivalent.
  • the TMGI can be used, which is also can be replaced by the SSM.
  • the first step can be: a 5G network may initiate the MBS session Create.
  • FIG. 4 illustrates a sequence diagram for a multicast and broadcast services (MBS) session creation procedure (e.g., how the 5G network creates the MBS session, when the PCC is deployed) , in accordance with some embodiments of the present disclosure. For simplicity, unrelated steps have been omitted.
  • MBS multicast and broadcast services
  • an application function may send Allocate TMGI Request message to trigger a Temporary Mobile Group Identity (TMGI) allocation procedure.
  • the multicast-broadcast SMF (MB-SMF) may allocate the TMGI for this multicast and broadcast services (MBS) session.
  • the AF may initiate the service Announcement procedure to send MBS service information to a UE.
  • the AF may send Network Exposure Function (NEF) /Multicast/Broadcast Service Function (MBSF) MBS session create request, which may include the MBS session ID (e.g., TMGI) , MBS Service Information, UE authorization information. If the MBS session is for location dependent MBS session, there can be location dependent indication. If the AF is trusted and MBSF is not deployed, the step 404, 405 and 406 can be performed by the AF directly. In the following figures, this principle can also be applied.
  • NEF Network Exposure Function
  • MBSF Multicast/Broadcast Service Function
  • the NEF may use the MBS session ID (e.g., TMGI) to check with Binding Support Function (BSF) to find a MB-PCF.
  • MBS session ID e.g., TMGI
  • BSF Binding Support Function
  • PCFs Policy Control Functions
  • the NEF may use the MBS session ID to check with a NF repository function (NRF) , to find a PCF.
  • NEF NF repository function
  • the NEF may invoke a Npcf_MBSPolicy_Authorization_Create Request to establish an AF session (N5 session) with the MB-PCF.
  • the MBS session ID, MBS Service Information can be included in the request.
  • the PCF may determine the policy information (e.g., Qos parameters, packet filter) based on the received MBS Service Information, and may store the policy information together with the MBS Session ID.
  • the PCF may invoke a Nbsf_management_Register Request (MBS Session ID, PCF ID) to register at the BSF that handles the MBS session.
  • MBS Session ID MBS Session ID
  • PCF ID Nbsf_management_Register Request
  • the PCF may send an Npcf_MBSPolicy_Authorization_Create Response to the NEF/MBSF.
  • the NEF/MBSF may use the MBS session ID to check with the NRF, to find a MB-SMF which is serving the MBS session.
  • the NEF/MBSF may send a Nmbsmf_MBSSession_Create Request (MBS Session ID, MBS service information) to the MB-SMF.
  • MBS Session ID MBS service information
  • a location dependent indication can be included if received in step 403. If the AF is trusted and MBSF is not deployed, the step 410 can be performed by the AF directly.
  • the MB-SMF may use the MBS session ID (e.g., TMGI) to check with the BSF to find the PCF.
  • MBS session ID e.g., TMGI
  • the MB-SMF may send an Npcf_MBSPolicyControl_Create Request towards the PCF to establish the N7 session (SM Policy association) .
  • the MB-SMF may forward the MBS Service Information to the PCF discovered in step 411.
  • the PCF may use the MBS session ID for the session binding, e.g., associating the AF session create in the step 406 and N7 session in the step 412.
  • the PCF may respond with a Npcf_MBSPolicyControl_Create Response (policy information for the MBS session created in the step 406) .
  • the MB-SMF may send a Nmbsmf_MBSSession_Create Response to the NEF/MBSF. If a location dependent indication is received in step 410, the MB-SMF may allocate an area session ID and may include this ID in the response.
  • the NEF/MBSF may respond to the AF/AS. If an area session ID is received in the step 415, it can also be included in the response.
  • the session binding mechanism introduced in the step 413 holds significant importance. This mechanism plays a crucial role in ensuring the proper functioning of the system or process. By establishing session bindings, the system can accurately associate different components or entities with their respective sessions. For one PCF, there can be many AF sessions from AF (s) /NEF (s) side and also many N7 sessions from MB-SMF (s) side. The PCF may know which AF session is associated with which N7 session.
  • the MBS session ID is the key word for MBS session binding in the PCF.
  • Location-dependent MBS service is a kind of important MBS service which is provided in several MBS service areas.
  • the location dependent MBS service enables distribution of different content data to different MBS service areas.
  • the different content may have different packet address (e.g., IP address/port) .
  • the same MBS Session ID can be used to identify the MBS session.
  • An additional area session ID can be used for each MBS service area.
  • the area session ID can be used in combination with MBS Session ID, to uniquely identify the service area specific part of the MBS service within 5GS.
  • steps 403 and 410 of FIG. 4 there can be a location dependent indication.
  • the MB-SMF may allocate the area session ID and may return the area session ID to the AF in steps 415 and 416.
  • the session binding mechanism may not work for the location dependent MBS session, because the session binding cannot be accomplished only relying on the MBS session ID.
  • the area session ID is assigned by the MB-SMF after the session binding, which may not help.
  • FIG. 5 illustrates a sequence diagram for a session binding issue for a location dependent multicast and broadcast services (MBS) session, in accordance with some embodiments of the present disclosure.
  • MBS location dependent multicast and broadcast services
  • steps 506 and 510 can be performed by the AF directly.
  • steps 501 to 505 the procedures can be the same as steps 401 to 405.
  • a NEF/MBSF may establish an AF session (N5 session) with a MB-PCF.
  • a TMGI and content-1 Information e.g., IP address/port, QoS
  • IP address/port e.g., IP address/port, QoS
  • the NEF/MBSF may provide the TMGI and content-2 Information (e.g., IP address/port, QoS) to the PCF.
  • TMGI TMGI and content-2 Information
  • steps 507 to 509 the procedures can be the same as steps 407 to 409.
  • the NEF/MBSF may send a Nmbsmf_MBSSession_Create Request to the MB-SMF.
  • a location dependent indication can be included.
  • the NEF/MBSF may also send a MBS session request to the MB-SMF.
  • a location dependent indication can be included.
  • the MB-SMF may send an Npcf_MBSPolicyControl_Create Request towards the PCF to establish the N7 session (SM Policy association) .
  • the PCF may need to know the N7 session request in the step 512a is associated with AF session received in the step 506a, and N7 session request in the step 512b is associated with AF session received in the step 506b.
  • the PCF may not make this decision, because only using the TMGI cannot achieve this purpose.
  • the PCF receives the TMGI in step 512a, the PCF does not know how to correlate the TGMI to the AF session in step 306a and 306b, because both AF sessions in steps 306a and 306b include the same TMGI.
  • the location dependent MBS session there is an issue in the existing session binding mechanism in the PCF.
  • the AF/NEF/MBSF may send a location dependent indication (e.g., Association request indication) to the PCF when establishing the AF session or updating the AF session.
  • a location dependent indication e.g., Association request indication
  • an AF, NEF or MBSF can send the request to PCF depending on the deployment, or whether AF is trusted by the operator.
  • the PCF may respond an Association ID according to the received indication.
  • the AF/NEF/MBSF may send the Association ID along with the MBS session ID to the MB-SMF in the MBS session request.
  • the MB-SMF may send the Association ID along with the MBS session ID to the PCF when the MB-SMF establishes the N7 session or update the N7 session.
  • the PCF may associate the N7 session and the N5 session according to the MBS session ID and the Association ID.
  • the MB-SMF may allocate the Area session ID, and may respond to the NEF/MBSF/AF.
  • the NEF/MBSF may store the Area session ID and the Association ID for this MBS session.
  • the AF/NEF/MBSF may send the request to MB-PCF, with MBS session ID and Area session ID.
  • the AF/NEF/MBSF may send the Association ID along with the MBS session ID to MB-SMF in the MBS session request.
  • the MB-SMF may send the Association ID along with the MBS session ID to the PCF when the MB-SMF updates the N7 session.
  • the PCF may associate the N7 session and N5 session according to the MBS session ID and the Association ID.
  • FIG. 6 illustrates a sequence diagram for a multicast and broadcast services (MBS) session creation procedure (e.g., how a 5G network MBS session is created for a location dependent MBS session when PCC is deployed) , in accordance with some embodiments of the present disclosure. For simplicity, unrelated steps have been omitted.
  • MBS multicast and broadcast services
  • Step 601 to step 606 are same with step 401 to step 406.
  • an AF may send an Allocate TMGI Request message to trigger a TMGI allocation procedure.
  • a MB-SMF may allocate the TMGI for this MBS session.
  • the AF may initiate a service Announcement procedure to send MBS service information to a UE.
  • the AF may send a NEF/MBSF MBS session create request, which includes a MBS session ID, MBS Service Information, UE authorization information, location dependent indication. If the AF is trusted and a MBSF is not deployed, steps 604, 605 and 606 can be performed by the AF directly.
  • a NEF may use the MBS session ID (e.g., TMGI) to check with a BSF to find a MB-PCF.
  • MBS session ID e.g., TMGI
  • the NEF may use the MBS session ID to check with a NRF, to find a PCF.
  • the NEF may invoke a Npcf_MBSPolicy_Authorization_Create Request to establish an AF session (N5 session) with the MB-PCF.
  • location dependent indication e.g., Association request indication
  • the PCF may create an Association ID for the MBS session according to the received indication. If this QoS is allowed, the PCF may determine the policy information (e.g., QoS parameters, packet filter) based on the received MBS Service Information, and may store the policy information together with the MBS Session ID and the Association ID.
  • the PCF may invoke a Nbsf_management_Register Request (MBS Session ID, PCF ID) to register at the BSF that handles the MBS session.
  • MBS Session ID MBS Session ID
  • PCF ID Nbsf_management_Register Request
  • the PCF may send an Npcf_MBSPolicy_Authorization_Create Response to the NEF/MBSF.
  • the Association ID can be included in the response.
  • the NEF/MBSF may use the MBS session ID to check with the NRF, to find a MB-SMF which is serving the MBS session.
  • the NEF/MBSF may send a Nmbsmf_MBSSession_Create Request (MBS Session ID, MBS service information, location dependent indication, Association ID) to the MB-SMF. If the AF is trusted and a MBSF is not deployed, step 610 can be performed by the AF directly.
  • MBS Session ID MBS service information
  • location dependent indication Association ID
  • the MB-SMF may use the MBS session ID (e.g., TMGI) to check with the BSF to find the PCF.
  • MBS session ID e.g., TMGI
  • the MB-SMF may send an Npcf_MBSPolicyControl_Create Request (MBS session ID, Association ID) towards the PCF to establish the N7 session (SM Policy association) .
  • the MB-SMF may forward the MBS Service Information to the PCF discovered in step 611.
  • the PCF may use the MBS session ID and Association ID for the session binding, e.g., associating the AF session create in step 606 and N7 session in step 612.
  • the PCF may respond with a Npcf_MBSPolicyControl_Create Response (policy information for the MBS session created in step 606) .
  • the MB-SMF may send a Nmbsmf_MBSSession_Create Response to the NEF/MBSF.
  • the MB-SMF may allocate an area session ID and may include this ID in the response.
  • the NEF/MBSF may store the area session ID and the Association ID relationship for this MBS session.
  • the NEF/MBSF may respond to the AF/AS with area session ID received in step 615.
  • FIG. 7 illustrates a sequence diagram for a multicast and broadcast services (MBS) session update procedure (e.g., how a 5G network MBS session is updated for a location dependent MBS session when PCC is deployed) , in accordance with some embodiments of the present disclosure. For simplicity, unrelated steps have been omitted.
  • MBS multicast and broadcast services
  • an AF may send a NEF/MBSF MBS session update request, which includes the MBS session ID, MBS Service Information, UE authorization information, Area session ID. If the AF is trusted and a MBSF is not deployed, step 702 can be performed by the AF directly.
  • a NEF may invoke a Npcf_MBSPolicy_Authorization_Update Request to update an AF session (N5 session) with a MB-PCF.
  • the MBS session ID, MBS Service Information and Association ID can be included in the request.
  • the NEF may determine the Association ID according to the Area session ID and the Association ID relation stored in the step 615.
  • the PCF may determine policy information (e.g., QoS parameters, packet filter) based on the received MBS Service Information, and may store the policy information together with the MBS Session ID and the Association ID.
  • policy information e.g., QoS parameters, packet filter
  • the PCF may send an Npcf_MBSPolicy_Authorization_Update Response to the NEF/MBSF.
  • the NEF/MBSF may send a Nmbsmf_MBSSession_Update Request (MBS Session ID, MBS service information, Area session ID, Association ID) to the MB-SMF. If the AF is trusted and a MBSF is not deployed, step 705 can be performed by the AF directly.
  • the MB-SMF may send an Npcf_MBSPolicyControl_Update Request (MBS session ID, Association ID) towards the PCF to update the N7 session (MBS Policy association) .
  • the PCF may respond with a Npcf_MBSPolicyControl_Update Response (policy information for the MBS session created in step 703) .
  • the MB-SMF may send a Nmbsmf_MBSSession_Update Response to the NEF/MBSF.
  • the NEF/MBSF may respond to the AF/AS.
  • FIG. 8 illustrates a flow diagram for multicast and broadcast services (MBS) session association, in accordance with an embodiment of the present disclosure.
  • the method 800 may be implemented using any one or more of the components and devices detailed herein in conjunction with FIGs. 1–2.
  • the method 800 may be performed by a network node, in some embodiments. Additional, fewer, or different operations may be performed in the method 800 depending on the embodiment. At least one aspect of the operations is directed to a system, method, apparatus, or a computer-readable medium.
  • a first network node may receive a first message requesting to establish a first network session (e.g., an application function (AF) /N5 session) from a second network node (e.g., an application function (AF) , a network exposure function (NEF) , or a Multicast/Broadcast Service Function (MBSF) ) .
  • the first message may include an association request indication.
  • the first network node may send a second message including an Association ID in response to receiving the association request indication.
  • the first network node may receive a third message requesting to establish a second network session (e.g., multicast and broadcast services (MBS) /N7 session) from a third network node (e.g., a multicast-broadcast session management function (MB-SMF) ) .
  • the third message may include the Association ID.
  • the first network node may associate the first network session with the second network session based at least on the Association ID.
  • a N5 session/AF session can be between AF/NEF/MBSF and PCF.
  • the N5 session/AF session may be not only used for MBS service, but also used for other services, e.g., internet, IMS, vertical industry, or IoT.
  • a N7 session/SM policy association can be between SMF/MB-SMF and PCF.
  • the N7 session/SM policy association may be not only used for MBS session, but also used for other PDU sessions.
  • There can be a signaling path for the MBS session (e.g., from AF/NEF/MBSF to MB-SMF to AMF to NG-RAN) .
  • the association request indication can be a location dependent indication.
  • the first network node may include a Policy Control Function (PCF) .
  • the second network node may include one of an Application Function (AF) , a Network Exposure Function (NEF) , or a Multicast/Broadcast Service Function (MBSF) .
  • the third network node may include a Multicast-Broadcast Session Management Function (MB-SMF) .
  • the first network session may include an AF session, and the second network session may include an SM Policy Association.
  • the first message may further include a Multicast/Broadcast Service (MBS) session ID, and optional MBS Service Information.
  • MBS Multicast/Broadcast Service
  • the first network node may generate the Association ID for the second network session based on at least one of: the association request indication, the MBS session ID, or the optional MBS Service Information.
  • the second network node may send the Association ID, together with the MSB session ID, to the third network node.
  • the first network node may associate the first network session with the second network session further at least based on the Association ID.
  • the third network node can be configured to allocate an Area session ID and send the Area session ID to the first network node.
  • the first network node can be configured to store the Area session ID, together with the Association ID, for the second network session.
  • the first network node may receive a fourth message requesting to update the first network session from the second network node.
  • the fourth message may include the Association ID.
  • the first network node may receive a fifth message requesting to update the second network session from the third network node.
  • the fifth message may include the Association ID.
  • a second network node may send a first message requesting to establish a first network session to a first network node.
  • the first message may include an association request indication.
  • the second network node may receive a second message including an Association ID in response to the first network node receiving the association request indication from the first network node.
  • the second network node may send a third message requesting to establish a third network session between the second network node and the third network node to a third network node.
  • the third message may include the Association ID.
  • the first network session and a second network session can be configured to be associated with each other based at least on the Association ID.
  • the third network node may send a fourth message requesting to establish a second network session to the first network node.
  • the first network session may include an AF session
  • the second network session may include an SM Policy Association.
  • any reference to an element herein using a designation such as “first, “ “second, “ and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.
  • any of the various illustrative logical blocks, modules, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two) , firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as "software” or a "software module) , or any combination of these techniques.
  • firmware e.g., a digital implementation, an analog implementation, or a combination of the two
  • firmware various forms of program or design code incorporating instructions
  • software or a “software module”
  • IC integrated circuit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the logical blocks, modules, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device.
  • a general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine.
  • a processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein.
  • Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another.
  • a storage media can be any available media that can be accessed by a computer.
  • such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic 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 can be accessed by a computer.
  • module refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various modules are described as discrete modules; however, as would be apparent to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs the associated functions according embodiments of the present solution.
  • memory or other storage may be employed in embodiments of the present solution.
  • memory or other storage may be employed in embodiments of the present solution.
  • any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present solution.
  • functionality illustrated to be performed by separate processing logic elements, or controllers may be performed by the same processing logic element, or controller.
  • references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Sont présentés des systèmes et des procédés d'association de session de services de multidiffusion et de diffusion (MBS). Un premier nœud de réseau peut recevoir un premier message demandant l'établissement d'une première session de réseau depuis un deuxième nœud de réseau. Le premier message peut comprendre une indication de demande d'association. Le premier nœud de réseau peut envoyer un deuxième message comprenant un ID d'association en réponse à la réception de l'indication de demande d'association. Le premier nœud de réseau peut recevoir un troisième message demandant l'établissement d'une deuxième session de réseau depuis un troisième nœud de réseau. Le troisième message peut comprendre l'ID d'association. Le premier nœud de réseau peut associer la première session de réseau à la deuxième session de réseau sur la base au moins de l'ID d'association.
PCT/CN2023/093171 2023-05-10 2023-05-10 Systèmes et procédés d'association de session de services de multidiffusion et de diffusion (mbs) Pending WO2024156159A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2023/093171 WO2024156159A1 (fr) 2023-05-10 2023-05-10 Systèmes et procédés d'association de session de services de multidiffusion et de diffusion (mbs)
CN202380097989.XA CN121079996A (zh) 2023-05-10 2023-05-10 用于多播和广播服务会话关联的系统和方法

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/093171 WO2024156159A1 (fr) 2023-05-10 2023-05-10 Systèmes et procédés d'association de session de services de multidiffusion et de diffusion (mbs)

Publications (1)

Publication Number Publication Date
WO2024156159A1 true WO2024156159A1 (fr) 2024-08-02

Family

ID=91969882

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/093171 Pending WO2024156159A1 (fr) 2023-05-10 2023-05-10 Systèmes et procédés d'association de session de services de multidiffusion et de diffusion (mbs)

Country Status (2)

Country Link
CN (1) CN121079996A (fr)
WO (1) WO2024156159A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022034050A1 (fr) * 2020-08-13 2022-02-17 Telefonaktiebolaget Lm Ericsson (Publ) Mbs à option de qos individuelle
WO2022233024A1 (fr) * 2021-05-07 2022-11-10 Zte Corporation Procédé d'établissement d'une session se service de multidiffusion/diffusion, et système et appareil associés
WO2022236448A1 (fr) * 2021-05-08 2022-11-17 Zte Corporation Procédé de création de session mbs, et système et appareil associés
US20220417709A1 (en) * 2021-06-25 2022-12-29 Samsung Electronics Co., Ltd. Method and apparatus for controlling mbs in wireless communication system
US20230028404A1 (en) * 2021-07-23 2023-01-26 Apple Inc. Application function initiated multicast session join procedures for multicast broadcast services

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022034050A1 (fr) * 2020-08-13 2022-02-17 Telefonaktiebolaget Lm Ericsson (Publ) Mbs à option de qos individuelle
WO2022233024A1 (fr) * 2021-05-07 2022-11-10 Zte Corporation Procédé d'établissement d'une session se service de multidiffusion/diffusion, et système et appareil associés
WO2022236448A1 (fr) * 2021-05-08 2022-11-17 Zte Corporation Procédé de création de session mbs, et système et appareil associés
US20220417709A1 (en) * 2021-06-25 2022-12-29 Samsung Electronics Co., Ltd. Method and apparatus for controlling mbs in wireless communication system
US20230028404A1 (en) * 2021-07-23 2023-01-26 Apple Inc. Application function initiated multicast session join procedures for multicast broadcast services

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
SHABNAM SULTANA, ERICSSON: "Correction to PCC procedures for location dependent MBS service", 3GPP DRAFT; S2-2304139; TYPE CR; CR 0200; 5MBS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP SA 2, no. Online; 20230417 - 20230421, 7 April 2023 (2023-04-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052290806 *
SHABNAM SULTANA, ERICSSON: "Correction to PCC procedures for location dependent MBS service", 3GPP DRAFT; S2-2304140; TYPE CR; CR 0201; 5MBS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP SA 2, no. Online; 20230417 - 20230421, 7 April 2023 (2023-04-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052290807 *

Also Published As

Publication number Publication date
CN121079996A (zh) 2025-12-05

Similar Documents

Publication Publication Date Title
US11558813B2 (en) Apparatus and method for network automation in wireless communication system
CN113473634A (zh) 用于为nr操作配置多小区调度的装置和方法
JP2020504517A (ja) 無線通信システムにおいてサービス品質（ＱｏＳ）フロー基盤のＵＬパケットを送信する方法及びそのための装置
US20230015755A1 (en) System and method for sidelink communications in wireless communication networks
US20240372684A1 (en) Systems and methods for signaling scheme for cast-type indication and resource indication
WO2024098632A1 (fr) Systèmes et procédés de détermination de capacité réseau par l'intermédiaire d'un plan de contrôle
US11611899B2 (en) Method of quality of service control for a specific user equipment in a slice
CN120419236A (zh) 用于在无线通信系统中连接基于qos流的终端的方法和装置
CN117413616A (zh) 用于在无线通信系统中管理基于回程信息的会话的方法和设备
CN117296355A (zh) 用于有效处理服务/相邻小区信息的更新的方法和装置
CN113825234A (zh) 用在用户设备中的装置
WO2024156159A1 (fr) Systèmes et procédés d'association de session de services de multidiffusion et de diffusion (mbs)
WO2024113069A1 (fr) Systèmes et procédés de gestion de qualité de service pour un trafic de réalité étendue
CN113541902B (zh) 用在用户设备中的装置
WO2023015517A1 (fr) Systèmes et procédés pour établir un tunnel n3 partagé
CN120856292A (zh) 用于提高nr多播传输的可靠性，以及用于单小区nr多播传输的组调度的系统和方法
WO2024169004A1 (fr) Systèmes et procédés de réactivation d'une session d'unité de données de protocole (pdu) pour remplacement de nom de réseau de données (dnn)
WO2024216823A1 (fr) Systèmes et procédés de transfert
WO2022239289A1 (fr) Dispositif de communication et procédé de communication
WO2024230037A1 (fr) Systèmes et procédés de gestion de session
WO2024230030A1 (fr) Systèmes et procédés de transfert
WO2025236499A1 (fr) Systèmes et procédés d'authentification et de gestion de clé pour désactivation de service d'applications
WO2024156140A1 (fr) Systèmes et procédés de détermination de capacité de réseau par l'intermédiaire d'un plan d'utilisateur
WO2025076714A1 (fr) Systèmes et procédés d'enregistrement d'équipements utilisateurs
WO2025091480A1 (fr) Systèmes et procédés de collecte de données d'énergie

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23918161

Country of ref document: EP

Kind code of ref document: A1