Application function initiated multicast session join procedure for multicast broadcast service

Abstract

The present disclosure relates to application function initiated multicast session join procedures for multicast broadcast services. Embodiments of application function (AF) initiated multicast session join procedures for multicast broadcast services (MBS) are disclosed, where a user equipment (UE) initiates a session leave procedure. An AF server can receive a request from the UE to get content and determine that the content is provided by the AF server via a multicast session of a MBS. The AF server can transmit another request to a core network (e.g., a next generation core network) to enable the UE to join the multicast session of the MBS. If the UE does not already have a protocol data unit (PDU) session to a data network name / single network slice selection assistance information (DNN / S-NSSAI) that provides the multicast session of the MBS, the AF server can invoke an application trigger and / or an application level redirection to enable the UE to access an AF instance on the DNN / S-NSSAI that provides the multicast session of the MBS.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 225,028, filed July 23, 2021, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The overall implementation plan involves multicast broadcast service (MBS) in wireless communication systems. Background Technology

[0004] User equipment uses Non-Access Stratum (NAS) layer session management signaling to trigger multicast session join / leave procedures for Multicast-Broadcast Service (MBS). Summary of the Invention

[0005] Some implementations include apparatus, methods, and computer program products for a multicast session joining procedure initiated by an application function (AF) for a multicast broadcast service (MBS), wherein a user equipment (UE) initiates a session leaving procedure. The AF server may receive a request from the UE to retrieve content and determine that the content is provided by the AF server via the MBS multicast session. The AF server may transmit a request to the core network (e.g., a next-generation core network) to enable the UE to join the MBS multicast session via an existing Protocol Data Unit (PDU) session to Data Network Name / Single Network Slice Selection Auxiliary Information (DNN / S-NSSAI). If the UE does not already have a PDU session to the DNN / S-NSSAI providing the MBS multicast session, the AF server may invoke application triggering and / or application-level redirection to enable the UE to access the AF instance on the DNN / S-NSSAI providing the MBS multicast session.

[0006] Some implementations include a core network (CN) node, which includes a policy control function (PCF) and a network open function (NEF) communicatively coupled to the PCF. The NEF receives a first request from an application function (AF) server to add the UE to a multicast session of the MBS, where the AF server provides the MBS. The NEF may transmit a second request to the PCF, which manages the policy for the PDU sessions of the UE to be provided with the multicast session. The CN node may include a session management function (SMF) communicatively coupled to the PCF, whereby the PCF may transmit a signal corresponding to the UE's PDU session to the SMF, wherein the signal includes a multicast MBS session ID corresponding to the multicast session of the MBS. The SMF may modify the UE's PDU session to add the UE to the multicast session of the MBS.

[0007] The CN node may include an Access and Mobility Management Function (AMF) communicatively coupled to the SMF, wherein the AMF receives an allow list of AFs for MBS session control from the UE and transmits the AF's allow list to the SMF. To modify the UE's PDU session, the SMF may determine whether the AF server is included in the AF's allow list. The AMF may store the AF's allow list as part of the UE context. In some implementations, the SMF may store the list of AFs.

[0008] In some implementations, the PCF may determine that the UE's PDU session does not correspond to the Data Network Name / Single Network Slice Selection Auxiliary Information (DNN / S-NSSAI) providing the multicast session for the MBS, and based on this determination, transmit a notification to the AF server. The NEF processor may receive an application-triggered message, including the UE's General Public Subscription Identifier (GPSI), after transmitting a second request to the PCF. Upon receiving the application trigger, the UE establishes a PDU session corresponding to the DNN / S-NSSAI providing the multicast session for the MBS. Attached Figure Description

[0009] The accompanying drawings, which are incorporated herein and form part of the specification, illustrate the disclosed contents and, together with the specification, further serve to explain the principles of this disclosure and enable those skilled in the art to make and use the disclosure.

[0010] Figure 1 An exemplary system for a multicast session joining procedure initiated by an application function (AF) for a multicast broadcast service (MBS) is shown according to some embodiments of the present disclosure.

[0011] Figure 2A and Figure 2B An exemplary system supporting AF-initiated multicast session joining procedures for MBS is shown according to some embodiments of this disclosure.

[0012] Figure 3A and Figure 3B An exemplary system is shown that supports multicast session joining procedures initiated by an AF with an application-triggered MBS, according to some embodiments of the present disclosure.

[0013] Figure 4 An exemplary system is shown that supports multicast session joining procedures initiated by an AF for an MBS with application-level redirection, according to some embodiments of the present disclosure.

[0014] Figure 5 Examples of user equipment (UE) consent for a multicast session joining procedure supported by an AF are shown in some embodiments of this disclosure.

[0015] Figure 6 Exemplary methods for performing a multicast session joining procedure for an AF to perform an MBS are shown according to some embodiments of this disclosure.

[0016] Figure 7 A block diagram of an exemplary wireless system operating in an MBS environment according to some embodiments of the present disclosure is shown.

[0017] Figure 8 It is an exemplary computer system for implementing some implementation schemes or parts thereof.

[0018] This disclosure is described with reference to the accompanying drawings. In the drawings, the same reference numerals generally denote the same or similarly functional elements. Additionally, the leftmost numeral of the reference numerals generally appears first in the drawings. Detailed Implementation

[0019] Next-generation (e.g., fifth-generation (5G)) multicast broadcast services (MBS) may include application function (AF) servers that perform session join / leave procedures for user equipment (UE). Some implementations include procedures for providing MBS to systems when a protocol data unit (PDU) session has not yet been established, and describe UE identifiers that can be used to perform session join / leave procedures. Some implementations describe corresponding UE control regarding MBS multicast sessions (e.g., how a UE can control which AFs are authorized to enable the UE to join an MBS multicast session). AFs may include content provider functionalities.

[0020] Figure 1 An exemplary system 100 for a multicast session joining procedure initiated by an application function (AF) for a multicast broadcast service (MBS) is illustrated according to some embodiments of this disclosure. System 100 includes a UE 110, a radio access network (RAN) 120, a core network (CN) 130, a network 140, AF 150, and AF 160. In some embodiments, RAN 120 may include a next-generation RAN, and CN 130 may include the functionality of a next-generation core network (e.g., a core network node). UE 110 may be an electronic device including, but not limited to, a cellular phone, smartphone, tablet, personal digital assistant (PDA), or laptop computer. RAN 120 may include one or more base stations, including but not limited to fifth-generation node Bs (gNBs) operating in frequency range 1 (FR1) and / or frequency range 2 (FR2). Examples of next-generation communications include, but are not limited to, fifth-generation (5G) or new radio (NR) communications as defined by the 3rd Generation Partnership Project (3GPP) standards. For example, UE 110 and RAN 120 may include electronic devices configured to operate using 3GPP versions (such as version 17 (Rel-17)) or other 3GPP standards.

[0021] Network 140 may include, but is not limited to, any combination of data networks, local area networks (LANs), metropolitan area networks (MANs), public land mobile networks (PLMNs), wireless local area networks (WLANs), and / or the Internet. In some embodiments, network 140 includes one or more data networks that may correspond to one or more data network name / single network slice selection assistance information (DNN / S-NSSAI). AF 150 and AF 160 may include one or more AF servers that perform application functions.

[0022] Figure 2A and Figure 2B An exemplary system 200 supporting an AF-initiated multicast session join procedure for MBS is shown according to some embodiments of this disclosure. For convenience, and not limitation, reference may be made to... Figure 1 The elements are used to describe system 200. For example, Figure 1 CN 130 may include Access and Mobility Management Function (AMF) 210, Session Management Function (SMF) 220, User Plane Function (UPF) 230, Policy Control Function (PCF) 240, and Network Opening Function (NEF) 250. UE 110 may communicate with AMF 210 via RAN 120 using Non-Access Stratum (NAS) signaling messages (e.g., session management messages). AMF 210 may transmit NAS signaling messages (e.g., session management messages) to SMF 220, where session management messages can be used to establish a PDU session with AF 160 via UPF 230. The PDU session may be a connection between UE 110 and UPF 230 coupled to DNN / S-NSSAI within network 140. AF 160 may be coupled to DNN / S-NSSAI within network 140.

[0023] At 260, UE 110 establishes a PDU session with AF 160 and begins a unicast connection with AF 160.

[0024] At 263, UE 110 may transmit a request to AF 160 to obtain content (e.g., video from content provider AF 160).

[0025] At 265, AF 160 can receive a request from UE 110 to retrieve content. AF 160 can perform permission control (e.g., perform an authorization check) to determine whether UE 110 is authorized to access the requested content. If UE 110 is authorized to access the requested content, AF 160 can determine whether the requested content is provided by AF 160 as a multicast session of a Multicast Broadcast Service (MBS) or as a unicast session. If the requested content is not provided as a multicast session of MBS, AF 160 can provide the requested content (e.g., via an established PDU session through a unicast connection). If the requested content is provided as a multicast session of MBS, AF 160 can determine an MBS session identifier (ID) corresponding to the requested content.

[0026] At 270, based on a request, AF 160 can determine the unicast connection point of UE 110 in CN 130, and AF 160 can determine the corresponding Internet Protocol (IP) address and port number. In some implementations, RAN 120 and CN 130 may be part of a Public Land Mobile Network (PLMN). AF 160 can also determine the Quality of Service (QoS) flow associated with the MBS session ID.

[0027] At position 275, AF 160 requests CN 130 to add the QoS flow associated with the MBS session ID of the multicast session of the MBS to UE 110, identified by the corresponding IP address and port number. In some implementations, AF 160 may transmit the request to PCF 240 (e.g., via NEF 250) to add the QoS flow associated with the corresponding MBS session ID of the multicast session of the MBS to UE 110, identified by the IP address and port number. If Network Address Translation (NAT) is used within CN 130, NEF 250 may map an IP address, which may be an external IP address, to an internal IP address of UE 110.

[0028] At position 277, for example, AF 160 can transmit signals to NEF 250 such as MBS session add requests (IP address, port number, and MBS session ID).

[0029] At 280, if NAT is implemented, NEF 250 can use the IP address and port number to obtain the internal address of UE 110. NEF 250 can then route the request to PCF 240, which manages the PDU session of UE 110.

[0030] At 283, for example, NEF 250 can transmit signals to PCF 240 such as Npcf_PolicyAuthorizationCreate / Update(UE 110's internal IP address, port number, MBS session ID).

[0031] At 285, PCF 240 may notify SMF 220 of the PDU session anchored to UE 110 of the MBS session ID to be added to the PDU session (e.g., via SMPolicyControlUpdateNotification operation).

[0032] At 287, for example, PCF 240 can transmit signals to SMF 220, such as Npcf_SMPolicyControlUpdateNotify(SM policy association ID, MBS session ID).

[0033] At 290, SMF 220 modifies the PDU session to add UE 110 to the multicast session. For example, SMF 220 can add a QoS flow associated with the corresponding MBS session ID of the multicast session of the MBS to UE 110.

[0034] At position 295, PDU session modification can occur. In some implementations, only UE 110 triggers the subsequent session departure procedure for leaving the multicast session of the MBS.

[0035] Figure 3A and Figure 3B An exemplary system 300 is shown that supports an AF-initiated multicast session join procedure with an application-triggered MBS, according to some embodiments of this disclosure. For convenience, and not limitation, reference may be made to... Figure 1 The elements of Figure 2 are used to describe system 300. For example, system 300 includes... Figure 1 CN 130 may include AMF 210, SMF 220, UPF 230, PCF 240, and NEF250. In System 300, unlike System 200, UE 110 has not yet established a PDU session on the DNN / S-NSSAI providing the MBS multicast session. Some implementations include AF 160 using Mobile Termination (MT) Short Message Service (SMS) to invoke application triggering, enabling UE 110 to establish a PDU session on the DNN / S-NSSAI providing the MBS multicast session.

[0036] At 310, UE 110 establishes a PDU session and begins a unicast connection with AF (e.g., AF 150 coupled to a different DNN / S-NSSAI than AF 160). In other words, UE 110 has not yet established a PDU session with AF 160 on the DNN / S-NSSAI that provides the MBS multicast session.

[0037] At 313, UE 110 may transmit a request to AF 160 to obtain content (e.g., video from content provider AF 160).

[0038] At 315, AF 160 can receive a request from UE 110. AF 160 can perform permission control (e.g., authorization) to determine whether UE 110 is authorized to access the requested content. If UE 110 is authorized to access the requested content, AF 160 can determine whether to provide the requested content as a multicast session or a unicast session of the MBS. If the requested content is provided as a multicast session of the MBS, AF 160 can determine the corresponding MBS session ID.

[0039] At 320, based on a request, AF 160 can determine the unicast connection point of UE 110 in CN 130, and AF 160 can determine the corresponding Internet Protocol (IP) address and port number. In some implementations, RAN 120 and CN 130 may be part of a PLMN. AF 160 can also determine the QoS flow associated with the MBS session ID.

[0040] At 325, AF 160 may request CN 130 to add the QoS flow associated with the MBS session ID of the multicast session of the MBS to UE 110, identified by the corresponding IP address and port number. In some implementations, AF 160 may transmit a request to PCF 240 (e.g., via NEF 250) to add the QoS flow associated with the corresponding MBS session ID of the multicast session of the MBS to UE 110, identified by the IP address and port number. If NAT is used within CN 130, NEF 250 may map an IP address, which may be an external IP address, to an internal IP address of UE 110.

[0041] At 327, for example, AF 160 can transmit signals to NEF 250 such as MBS session add requests (IP address, port number, and MBS session ID).

[0042] At 330, if NAT is implemented, the NEF 250 can use the IP address and port number to obtain the internal address of the UE 110. The NEF 250 can then route the request to the PCF 240. The PCF 240 is responsible for managing the policies for the PDU sessions of the UE 110 that are to provide multicast sessions.

[0043] At 333, for example, NEF 250 can transmit signals to PCF 240 such as Npcf_PolicyAuthorizationCreate / Update(UE 110’s internal IP address, port number, MBS session ID).

[0044] At point 345, PCF 240 determines whether a PDU session has been established for UE110 corresponding to the DNN / S-NSSAI providing the MBS multicast session. For example, PCF 240 determines whether a Session Management (SM) Policy Association ID corresponding to UE110 has been established for the DNN / S-NSSAI providing the MBS multicast session. If no corresponding SM Policy Association ID exists, PCF 240 determines that no corresponding SM Policy Association ID has been established.

[0045] At 360, PCF 240 can notify AF 160 that UE 110 does not have a PDU session established for the DNN / S-NSSAI that provides the MBS multicast session.

[0046] At point 365, for example, PCF 240 can transmit signals to notify AF 160, such as MBS session addition failure (IP address, port number, no PDU session in the required DNN / S-NSSAI). If NAT is used, the IP address can be the external IP address of UE 110.

[0047] At 370, AF 160 receives a signal from PCF 240. In response, AF 160 can use the UE 110's Common Public Subscription Identifier (GPSI) to invoke application triggering, enabling UE 110 to establish a PDU session with the DNN / S-NSSAI providing the multicast session for MBS. For example, AF 160 can set the application port ID field identifying the MBS client and use UE 110's GPSI to request UE 110 to initiate a PDU session on the DNN / S-NSSAI providing the multicast session for MBS.

[0048] At 375, for example, AF 160 can transmit signals such as Nnef_Trigger_Delivery requests (UE 110's GPSI, port number (MBS client), MBS session ID).

[0049] At 380, NEF 250 invokes an application trigger. For example, NEF 250 obtains a mapping from UE 110's GPSI to UE 110's Subscription Permanent Identifier (SUPI). NEF 250 may obtain the mapping from Unified Data Management (UDM) (not shown). NEF 250 may contact an SMS Service Center (SC) (not shown) to send an MT SMS to UE 110. The application port ID targets UE 110's MBS client, which triggers UE 110 to establish a PDU session with the DNN / S-NSSAI providing the MBS multicast session. In some implementations, the PDU session may include a multicast session (e.g., a QoS stream) corresponding to an MBS session ID (e.g., an MBS session ID corresponding to the requested content).

[0050] Figure 4 An exemplary system 400 is shown that supports an AF-initiated multicast session join procedure for an MBS with application-level redirection, according to some embodiments of this disclosure. For convenience, and not limitation, the system 400 may be described with reference to elements of the preceding figures. For example, the system 400 includes... Figure 1 CN 130 may include AMF 210, SMF 220, UPF 230, PCF240, and NEF 250. In system 400, unlike system 200, UE 110 has not yet established a PDU session on the DNN / S-NSSAI providing the multicast session for MBS. Some implementations include AF 160 using application-level redirection to cause the application client in UE 110 to begin transmitting a signal (e.g., application service based on the service descriptor), which triggers the establishment of a PDU session on the DNN / S-NSSAI providing the multicast session for MBS.

[0051] At 410, UE 110 establishes a PDU session and begins a unicast connection with AF (e.g., AF 150 coupled to a different DNN / S-NSSAI than AF 160). In other words, UE 110 has not yet established a PDU session with AF 160 on the DNN / S-NSSAI that provides the MBS multicast session.

[0052] At 413, UE 110 may transmit a request to AF 160 to obtain content (e.g., video from content provider AF 160).

[0053] At 415, AF 160 can receive a request from UE 110 to retrieve content. AF 160 can perform permission control (e.g., authorization) to determine whether UE 110 is authorized to access the requested content. If UE 110 is authorized to access the requested content, AF 160 can determine whether to provide the requested content as a multicast session or a unicast session of the MBS. If the requested content is provided as a multicast session of the MBS, AF 160 can determine the corresponding MBS session ID.

[0054] At 420, based on a request, AF 160 can determine the unicast connection point of UE 110 in CN 130, and AF 160 can determine the corresponding Internet Protocol (IP) address and port number. In some implementations, RAN 120 and CN 130 may be part of a PLMN. AF 160 can also determine the QoS flow associated with the MBS session ID.

[0055] At position 425, AF 160 requests CN 130 to associate the QoS flow with the MBS session ID of the MBS multicast session.

[0056] The request is added to UE 110, identified by the corresponding IP address and port number. In some implementations, AF 160 may transmit a request to PCF 240 (e.g., via NEF 250) to add a QoS flow associated with the corresponding MBS session ID of the MBS multicast session to UE 110, identified by the IP address and port number. If NAT is used within CN 130, NEF 250 can map an IP address, which may be an external IP address, to the internal IP address of UE 110. For example, AF 160 may transmit signals such as an MBS session add request (IP address, port number, and MBS session ID) to NEF 250. If NAT is implemented, NEF 250 can use the IP address and port number to obtain the internal address of UE 110. NEF 250 can then route the request to PCF 240, which manages the PDU session corresponding to UE 110. For example, NEF 250 can transmit signals to PCF 240, such as Npcf_PolicyAuthorizationCreate / Update(UE 110's internal IP address, port number, MBS session ID).

[0057] At 435, PCF 240 may notify SMF 220, which anchors the PDU session of UE 110, of the MBS session ID to be added to the PDU session. For example, PCF 240 may transmit a signal to SMF 220 (not shown), such as Npcf_SMPolicyControlUpdateNotify(SM policy association ID, MBS session ID). SMF 220 may determine that UE 110 does not have an existing PDU session corresponding to AF 160. SMF 220 may transmit a signal to PCF 240 indicating a failure to add UE 110 to the QoS flow corresponding to the MBS session ID.

[0058] At 440, PCF 240 can notify AF 160 that UE 110 does not have a PDU session established with DNN / S-NSSAI for the multicast session providing MBS. For example, PCF 240 can transmit signals to AF 160 such as MBS session addition failure (IP address, port number, no PDU session in the required DNN / S-NSSAI). If NAT is used, the IP address can be the external IP address of UE 110.

[0059] At 450, when AF 160 is unaware of UE 110's GPSI, AF 160 can invoke application-level redirection to enable UE 110's application client to establish a PDU session on the DNN / S-NSSAI providing the multicast session for MBS. For example, UE 110 may be configured with UE Route Selection Policy (URSP) rules that map application services (e.g., service descriptors) to corresponding PDU session parameters for the multicast PDU session. For example, the application service may target a different Fully Qualified Domain Name (FQDN) reachable via the DNN / S-NSSAI providing the multicast session for MBS. Therefore, AF 160 can use application-level redirection to enable the application client in the UE to begin transmitting the application service, which triggers PDU session establishment on the DNN / S-NSSAI providing the multicast session for MBS. For example, the application-level redirection message may include the MBS session ID and / or the DNN / S-NSSAI for connecting to AF 160 providing the multicast session for MBS.

[0060] Figure 5 Examples of user equipment (UE) consent procedures supporting AF-initiated multicast session joining procedures according to some embodiments of this disclosure are shown. For convenience, and not limitation, system 500 may be described with reference to elements of the preceding figures. For example, system 500 includes... Figure 1CN 130 may include AMF 210, SMF 220, and PCF 240. Some implementations address how UE110 controls or authorizes an AF (e.g., AF 160) to initiate a multicast session join procedure. Authorization can prevent, for example, UE 110 from joining a multicast session initiated by an unauthorized AF.

[0061] At 510, Alternative 1 illustrates providing a multicast session of MBS corresponding to the requested content when UE 110 is unaware of the mapping from AF 160 to DNN / S-NSSAI. For example, UE 110 may provide this information during registration.

[0062] At 512, UE 110 indicates that it is authorized to add UE 110 to the allowed list of the AF in the multicast session (e.g., include AF 160). The indication may be transmitted from UE 110 to AMF 210 in a NAS message (e.g., registration complete (allowed list of AFs controlled by MBS session)). In some implementations, the new information element (IE) may include "allowed list of AFs controlled by MBS session".

[0063] At 514, AMF 210 receives a registration completion message with a new IE indicating the allowed list of AFs controlled by the MBS session, and stores the allowed list of MBS session-controlled AFs as part of the UE context. Subsequently, when a PDU session is established, AMF 210 may retrieve and transmit to SMF 220 a list of relevant AFs associated with DNN / S-NSSAI (e.g., a subset of AFs from the allowed list of MBS session-controlled AFs). In some implementations, the entire allowed list of MBS session-controlled AFs is transmitted when a PDU session is established.

[0064] At 516, for example, AMF 210 may transmit signals such as Nsmf_PDUSession_CreateSMContext(Allowed list of AFs controlled by MBS session), where the new IE may include a list of associated AFs (e.g., a subset of the allowed list of AFs controlled by MBS session) or the entire allowed list of AFs controlled by MBS session. In some implementations, AMF 210 may determine the associated allowed list of AFs based on local configuration information (e.g., AFs associated with the MBS session anchored in SMF 220).

[0065] At 520, Alternative 2 shows that when UE 110 knows the mapping from AF 160 to DNN / S-NSSAI, it can provide a multicast session of MBS corresponding to the requested content, for example via URSP or application layer signaling.

[0066] At 522, since UE 110 is aware of the mapping, UE 110 can transmit new IEs in NAS Session Management (SM) signals, such as the allow list of AFs controlled by the MBS session according to the PDU session. For example, UE 110 can transmit signals to AMF210 such as PDU session establishment requests (allow list of AFs controlled by the MBS session).

[0067] At 524, AMF 210 can receive a PDU session establishment request with an allow list of AFs controlled by MBS session control. AMF 210 can transmit signals to SMF 220, such as Nsmf_PDUSession_CreateSMContext(allow list of AFs controlled by MBS session control).

[0068] At 526, SMF 220 can receive signals from AMF 210 and can store a list of AFs that authorize control of MBS sessions of UE 110.

[0069] At position 530, after 516 or 524, SMF 220 can receive a signal from PCF 240 to add the MBS session ID to the established PDU session. For example, SMF 220 can receive a signal from PCF 240 such as Npcf_SMPolicyControlUpdateNotify(SM policy association ID, MBS session ID). For example, the signal could be similar to... Figure 2B 287 or Figure 3B 347.

[0070] At 540, SMF 220 can determine whether the AF initiating the request (e.g., AF 160) is in the allowed list of AFs for MBS session control of UE 110. If AF 160 is included, the content corresponding to the requested content (e.g., from...) can be... Figure 2A 265, Figure 3A 315 or Figure 4 The MBS session ID (415) is added to the established PDU session. For example, the QoS flow corresponding to the MBS session ID can be associated with UE 110. Otherwise, the MBS session ID is not added to the established PDU session.

[0071] Figure 6 An exemplary method 600 for performing a multicast session joining procedure for an AF (Active Front-End System) according to some embodiments of this disclosure is shown. For convenience, and not limitation, the method may be described with reference to elements of the preceding figures. For example, method 600 may be... Figure 1 The AF 160 is executed, and the AF can be used with Figure 1 UE 110 and Figure 2A and / or Figure 2B Communication between PCF 240 and NEF 250.

[0072] At 605, AF 160 can receive a request from UE 110 to obtain content, where the request includes an IP address and port number.

[0073] At 610, AF 160 can perform permission control (e.g., authorization) to determine whether UE 110 is authorized to receive the requested content.

[0074] At 615, AF 160 determines whether the requested content is provided as a multicast session of the MBS. If the requested content is provided as a multicast session of the MBS, method 600 proceeds to 625. Otherwise, method 600 proceeds to 620.

[0075] At 620, when the requested content is provided as a unicast session, AF 160 provides the content as requested (e.g., via a unicast session).

[0076] Returning to 625, when the requested content is provided as a multicast session, AF 160 can transmit the request (e.g., via NEF 250) to PCF 240 to add a QoS flow associated with the corresponding MBS session ID of the multicast session of the MBS to UE 110, identified by the IP address and port number.

[0077] At 630, AF 160 determines that a failure message regarding the addition of a QoS flow with the corresponding MBS session ID has been received. For example, AF 160 may determine whether a message indicating that the MBS session addition failed has been received (e.g., the UE does not have a Protocol Data Unit (PDU) session established on the Data Network Name / Single Network Slice Selection Assistance Information (DNN / S-NSSAI) providing the MBS). If no failure message is received, method 600 proceeds to 635. Otherwise, method 600 proceeds to 640.

[0078] At 635, when no failure message is received (e.g., SMF 220 successfully adds the QoS flow corresponding to the MBS session ID to the PDU session), UE 110 continues to receive content requested from MBS (e.g., from AF 160).

[0079] Returning to 640, upon receiving a failure message, AF 160 determines whether the UE's General Public Subscription Identifier (GPSI) is known. If AF 160 knows the GPSI, method 600 proceeds to 645. Otherwise, method 600 proceeds to 650.

[0080] At 645, AF 160 can use the UE's GPSI to invoke application triggering so that UE 110 can establish a PDU session with the DNN / S-NSSAI that provides the MBS multicast session.

[0081] Returning to 650, when AF 160 is unaware of UE 110's GPSI, AP 160 can utilize application-level redirection to enable UE 110 to trigger the establishment of a PDU session to access the AF instance on DNN / S-NSSAI that provides the MBS multicast session.

[0082] Figure 7 A block diagram of an exemplary wireless system 700 operating in an MBS environment according to some embodiments of the present disclosure is shown. Reference may be made for illustrative purposes and not for limiting purposes. Figure 1 To describe the elements Figure 7 For example, system 700 can be any of the electronic devices in system 100 (e.g., UE 110, RAN 120, CN 130, or AF 160).

[0083] System 700 includes one or more processors 765, transceiver 770, communication interface 775, communication infrastructure 780, memory 785, and antenna 790. Memory 785 may include random access memory (RAM) and / or cache, and may include control logic (e.g., computer instructions) and / or data. One or more processors 765 may execute instructions stored in memory 785 to perform operations that enable wireless system 700 to transmit and receive wireless communications, including functions for supporting the AF-initiated multicast session join procedure for MBS described herein. In some embodiments, one or more processors 765 may be "hard-coded" to perform the functions described herein. According to some embodiments, transceiver 770 transmits and receives wireless communication signals including wireless communications supporting the AF-initiated multicast session join procedure for MBS, and may be coupled to one or more antennas 790 (e.g., 790a, 790b). In some embodiments, transceiver 770a (not shown) may be coupled to antenna 790a, and different transceivers 770b (not shown) may be coupled to antenna 790b. Communication interface 775 allows system 700 to communicate with other devices (which may be wired and / or wireless). Communication infrastructure 780 may be a bus. Antenna 790 may include one or more antennas, which may be the same or different types.

[0084] For example, it can use such as Figure 8The computer system 800 shown is implemented using one or more well-known computer systems. The computer system 800 can be any well-known computer capable of performing the functions described herein. For example, but not limited to, Figure 1 The device of system 100; performing operations in system 200 (Figure 2) and system 300 (Figure 3). Figure 4 System 400 Figure 5 Devices that perform the functions described in System 500; and devices that perform the functions described in System 500. Figure 6 The device (and / or other devices and / or components shown in the figure) that performs the function of method 600 can be implemented using computer system 800 or a portion thereof.

[0085] Computer system 800 includes one or more processors (also called central processing units or CPUs), such as processor 804. Processor 804 is connected to a communication infrastructure 806, which may be a bus. The one or more processors 804 may each be a graphics processing unit (GPU). In embodiments, a GPU is a processor designed for processing dedicated electronic circuitry for mathematically intensive applications. GPUs may have efficient parallel architectures for parallel processing of large blocks of data, such as general mathematically intensive data in computer graphics applications, images, videos, etc.

[0086] The computer system 800 also includes user input / output devices 803, such as a monitor, keyboard, pointing device, etc., that communicate with the communication infrastructure 806 via a user input / output interface 802. The computer system 800 also includes main memory or primary memory 808, such as random access memory (RAM). Main memory 808 may include one or more levels of cache. Main memory 808 stores control logic (e.g., computer software) and / or data.

[0087] The computer system 800 may also include one or more auxiliary storage devices or memories 810. Auxiliary storage 810 may include, for example, a hard disk drive 812 and / or a removable storage device or drive 814. The removable storage drive 814 may be a floppy disk drive, a magnetic tape drive, an optical disk drive, an optical storage device, a magnetic tape backup device, and / or any other storage device / drive.

[0088] Removable storage drive 814 can interact with removable storage unit 818. Removable storage unit 818 includes a computer-usable or readable storage device on which computer software (control logic components) and / or data are stored. Removable storage unit 818 can be a floppy disk, magnetic tape, optical disc, DVD, optical storage disk, and / or any other computer data storage device. Removable storage drive 814 reads from and / or writes to removable storage unit 818 in a well-known manner.

[0089] According to some embodiments, auxiliary storage 810 may include other means, tools, or other methods for allowing computer programs and / or other instructions and / or data to be accessed by computer system 800. Such means, tools, or other methods may include, for example, removable storage unit 822 and interface 820. Examples of removable storage unit 822 and interface 820 may include a program box and box interface (such as those found in video game devices), a removable memory chip (such as EPROM or PROM) and associated sockets, memory sticks and USB ports, memory cards and associated memory card slots, and / or any other removable storage unit and associated interface.

[0090] Computer system 800 may also include a communication or network interface 824. Communication interface 824 enables computer system 800 to communicate and interact with any combination of remote devices, remote networks, remote entities, etc. (individually and collectively referred to by reference numeral 828). For example, communication interface 824 may allow computer system 800 to communicate with remote device 828 via communication path 826, which may be wired and / or wireless, and may include any combination of LAN, WAN, Internet, etc. Control logic and / or data may be transmitted to and from computer system 800 via communication path 826.

[0091] The operations described in the foregoing embodiments can be implemented with a wide variety of configurations and architectures. Therefore, some or all of the operations described in the foregoing embodiments can be performed in hardware, software, or both. In some embodiments, tangible, non-transitory means or articles of art include tangible, non-transitory computer-usable or readable media on which control logic components (software) are stored, also referred to herein as computer program products or program storage devices. This includes, but is not limited to, computer system 800, main memory 808, secondary memory 810, and removable storage units 818 and 822, and tangible articles embodying any combination thereof. When executed by one or more data processing devices (such as computer system 800), such data processing devices cause such data processing devices to operate as described herein.

[0092] Based on the teachings contained in this disclosure, it will be apparent to those skilled in the art how to use [other methods]. Figure 8 The embodiments of this disclosure may be made and used with data processing devices, computer systems, and / or computer architectures other than those shown herein. In particular, the embodiments may operate with software, hardware, and / or operating system implementations other than those described herein.

[0093] It should be understood that the Detailed Description of Embodiments section, rather than the Summary and Abstract section, is intended to be used to interpret the claims. The Summary and Abstract section may set forth one or more, but not all, exemplary embodiments of this disclosure as contemplated by the inventors, and therefore is not intended to limit this disclosure or the appended claims in any way.

[0094] Although this disclosure has been described herein with reference to exemplary embodiments in exemplary fields and applications, it should be understood that this disclosure is not limited thereto. Other embodiments and modifications are possible and are within the scope and spirit of this disclosure. For example, and without limiting the generality of this paragraph, embodiments are not limited to the software, hardware, firmware, and / or entities shown in the figures and / or described herein. Furthermore, embodiments (whether or not explicitly described herein) have significant utility for fields and applications beyond those described herein.

[0095] The implementation scheme has been described herein using functional building blocks that demonstrate the implementation of specific functions and their relationships. For ease of description, the boundaries of these functional building blocks have been arbitrarily defined herein. Alternative boundaries may be defined as long as the specified functions and relationships (or their equivalents) are performed appropriately. Furthermore, alternative implementation schemes may use a different order of execution for functional blocks, steps, operations, methods, etc., than that described herein.

[0096] References to “an implementation,” “implementation,” “exemplary implementation,” or similar phrases herein indicate that the described implementation may include specific feature structures, structures, or characteristics, but each implementation need not necessarily include such feature structures, structures, or characteristics. Furthermore, such terminology need not refer to the same implementation. Additionally, when a specific feature structure, structure, or characteristic is described in connection with an implementation, whether or not it is explicitly mentioned or described herein, such feature structure, structure, or characteristic must be within the knowledge of a person skilled in the art to incorporate it into other implementations.

[0097] The breadth and scope of this disclosure should not be limited by any of the exemplary embodiments described above, but should be defined solely by the appended claims and their equivalents.

[0098] This disclosure assumes that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as data collection and / or use change. Personal information from users should be collected for the entity's lawful and reasonable purposes and not shared or sold outside of these lawful uses. Furthermore, such collection / sharing should only occur upon receipt of the user's informed consent. In addition, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data and ensure that others with access to such personal information data comply with their privacy policies and processes. Additionally, such entities may be subject to third-party evaluations to demonstrate their compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be adapted to the specific types of personal information data collected and / or accessed, and to applicable laws and standards, including specific considerations regarding jurisdiction. For example, in the United States, the collection or access to certain health data may be governed by federal and / or state laws, such as the Health Insurance Transfer and Accountability Act (HIPAA); while in other countries, health data may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained for different types of personal data in each country.

Claims

1. An application function (AF) server, comprising: Memory; as well as A processor, coupled to the memory, is configured to: Receive a first request from the user equipment (UE) to obtain content; It is determined that the content is provided by the AF server via a multicast session of the Multicast Broadcast Service (MBS). A second request is sent to the Policy Control Function (PCF) via the Network Open Function (NEF) to add a Quality of Service (QoS) flow to the UE, wherein the QoS flow is associated with the MBS Session Identifier ID corresponding to the multicast session of the MBS and is used by the UE. Receive a message indicating that MBS session addition failed; Configure the application port ID field that identifies the MBS client of the UE; and In response to the message, a signal including the UE's General Public Subscription Identifier (GPSI) and the port number identifying the UE's MBS client is sent to invoke application triggering, wherein the UE establishes a Protocol Data Unit (PDU) session with the Data Network Name / Single Network Slice Selection Auxiliary Information (DNN / S-NSSAI) that provides the multicast session of the MBS.

2. The AF server according to claim 1, wherein the processor is further configured to: At least based on the first request, determine the Internet Protocol IP address and the port number corresponding to the UE.

3. The AF server according to claim 1, wherein the processor is further configured to: Receive a second message indicating that the MBS session addition failed; and In response to the second message, an application-level redirect is used to enable the UE to access the AF instance on the DNN / S-NSSAI that provides the multicast session of the MBS.

4. The AF server according to claim 1, wherein the UE initiates a session exit procedure for the multicast session of the MBS.

5. A core network (CN) node, comprising: Policy control function (PCF); as well as Network Open Function (NEF), which is communicatively coupled to the PCF, wherein the NEF includes: NEF memory; and The NEF processor, coupled to the NEF memory, is configured as follows: Receive a first request from the Application Function (AF) server to add the User Equipment (UE) to a multicast session of the Multicast Broadcast Service (MBS), wherein the AF server provides the MBS; and A second request is sent to the PCF to add a Quality of Service (QoS) flow associated with the MBS session identifier ID corresponding to the multicast session of the MBS to the UE, wherein the PCF corresponds to the Protocol Data Unit (PDU) session of the UE; The PCF is configured as follows: It is determined that the PDU session does not correspond to the data network name / single network slice selection auxiliary information DNN / S-NSSAI that provides the multicast session; Based on the determination, a notification is sent to the AF server; The NEF processor is configured as follows: After the second request is sent to the PCF, a message including the UE's General Public Subscription Identifier (GPSI) and the port number identifying the UE's MBS client is received from the AF server to invoke the application trigger, wherein the UE establishes a second PDU session corresponding to the DNN / S-NSSAI that provides the multicast session of the MBS; Obtain the mapping from the GPSI to the UE's subscription permanent identifier SUPI; and The SMS service center (SC) is contacted to send a Mobile Termination (MT) SMS to the UE, wherein the MBS client triggers the UE to establish the second PDU session.

6. The CN node according to claim 5 further includes a Session Management Function (SMF) communicatively coupled to the PCF, wherein the PCF is further configured to: Send a signal to the SMF corresponding to the PDU session of the UE, wherein the signal includes a multicast MBS session ID corresponding to the multicast session of the MBS.

7. The CN node according to claim 6, wherein the SMF is further configured as follows: Modify the PDU session of the UE to add the UE to the multicast session of the MBS.

8. The CN node according to claim 7, further comprising an Access and Mobility Management Function (AMF) communicatively coupled to the SMF, wherein the AMF is configured to: Receive the allowed list of AF for MBS session control from the UE; and Send the allowed list of the AF to the SMF; and In order to modify the PDU session of the UE, the SMF is further configured as follows: Determine whether the AF server is included in the AF's allowed list.

9. The CN node according to claim 8, wherein the AMF is further configured as follows: The allowed list of the AF is stored as part of the UE's UE context.

10. The CN node according to claim 7, wherein the SMF is further configured as follows: Store a list of the AFs.

11. A method for using an application function (AF) server, the method comprising: Receive a first request from the user equipment (UE) to obtain content; It is determined that the content is provided by the AF server via a multicast session of the Multicast Broadcast Service (MBS). A second request is sent to the Policy Control Function (PCF) via the Network Open Function (NEF) to add a Quality of Service (QoS) flow to the UE, wherein the QoS flow is associated with the MBS Session Identifier ID corresponding to the multicast session of the MBS and is used by the UE. Receive a message indicating that MBS session addition failed; Configure the application port ID field that identifies the MBS client of the UE; and In response to the message, a signal including the UE's General Public Subscription Identifier (GPSI) and the port number identifying the UE's MBS client is sent to invoke application triggering, wherein the UE establishes a Protocol Data Unit (PDU) session with the Data Network Name / Single Network Slice Selection Auxiliary Information (DNN / S-NSSAI) that provides the multicast session of the MBS.

12. The method of claim 11, further comprising: At least based on the first request, determine the Internet Protocol IP address and port number corresponding to the UE.

13. The method of claim 11, further comprising: Received a second message indicating that MBS session addition failed; as well as In response to the second message, an application-level redirect is used to enable the UE to access the AF instance on the DNN / S-NSSAI that provides the multicast session of the MBS.

14. The method of claim 11, wherein the UE initiates a session departure procedure for the multicast session of the MBS.

Images