Multicast broadcast service authorization for inbound and outbound rovers

Abstract

Systems, methods, apparatuses, and computer program products for roaming of multicast (MBS) services. A method may include attaching, by a user equipment as an inbound rover, to a visited public land mobile network; receiving, by the user equipment, a service announcement from the application function, the service announcement comprising at least one of: a multicast service session indication allowed to be accessed by the inbound rover, or a multicast service category; determining, by the user equipment, whether the user equipment is allowed to access a multicast session or multicast service category in the visited public land mobile network based on the service announcement; sending, by the user equipment, a request to join the multicast session in response to determining that the user equipment is allowed to access, the request comprising an identifier of the multicast session and / or a multicast service category; and receiving, by the user equipment, an indication of acceptance or rejection of the request to join the multicast session.

Description

Technical Field

[0001] Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE), 5th Generation (5G) Radio Access Technology (RAT), New Radio (NR) access technology, 6th Generation (6G), and / or other communication systems. For example, certain example embodiments may relate to systems and / or methods for roaming of multicast MBS services. Background Art

[0002] Examples of mobile or wireless telecommunication systems may include radio frequency (RF) 5G RAT, universal mobile telecommunication system (UMTS) terrestrial radio access network (UTRAN), LTE Evolution UTRAN (E-UTRAN), LTE-Advanced (LTE-A), LTE-APro, NR access technology and / or MulteFire Alliance. 5G wireless system refers to the next generation (NG) radio system and network architecture. 5G systems are typically built on 5G NR, but 5G (or NG) networks can also be built on E-UTRA radio. NR is expected to support service categories such as enhanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC), and massive machine type communication (mMTC). NR is expected to provide ultra-wideband, ultra-robust, low latency connectivity and large-scale networking to support the Internet of Things (IoT). The next generation radio access network (NG-RAN) represents a radio access network (RAN) for 5G, which can provide radio access for NR, LTE, and LTE-A. It is important to note that a node in 5G that provides radio access functionality to user equipment (e.g., similar to a Node B in UTRAN or an evolved Node B (eNB) in LTE) may be referred to as a next-generation Node B (gNB) when built on an NR radio, and as a next-generation eNB (NG-eNB) when built on an E-UTRA radio. Summary of the invention

[0003] According to some example embodiments, a method may include attaching, by a user equipment, to a visited PLMN as an inbound roamer. The method may also include receiving, by the user equipment, a service announcement from an application function, the service announcement including at least one of a multicast service session indication or a multicast service category that is allowed to be accessed by the inbound roamer. The method may also include determining, by the user equipment based on the service announcement, whether the user equipment is allowed to access the multicast session or the multicast service category in the visited PLMN. The method may also include sending, by the user equipment, a request to join the multicast session in response to determining that the user equipment is allowed to access, the request including an identifier of the multicast session and / or the multicast service category. The method may also include receiving, by the user equipment, an indication of acceptance or rejection of the request to join the multicast session.

[0004] According to certain example embodiments, an apparatus may include a component for attaching to a visited PLMN as an inbound roamer. The apparatus may also include a component for receiving a service announcement from an application function, the service announcement including at least one of a multicast service session indication or a multicast service category that is allowed to be accessed by the inbound roamer. The apparatus may also include a component for determining whether the apparatus is allowed to access the multicast session or the multicast service category in the visited PLMN based on the service announcement. The apparatus may also include a component for sending a request to join the multicast session in response to determining that the apparatus is allowed to access, the request including an identifier of the multicast session and / or the multicast service category. The apparatus may also include a component for receiving an indication of acceptance or rejection of the request to join the multicast session.

[0005] According to various example embodiments, a non-transitory computer-readable medium may include program instructions that, when executed by a device, cause the device to perform at least one method. The method may include attaching to a visited PLMN as an inbound roamer. The method may also include receiving a service announcement from an application function, the service announcement including at least one of a multicast service session indication or a multicast service category that is allowed to be accessed by the inbound roamer. The method may also include determining whether the device is allowed to access a multicast session or a multicast service category in the visited PLMN based on the service announcement. The method may also include sending a request to join a multicast session in response to determining that the device is allowed to access, the request including an identifier of the multicast session and / or a multicast service category. The method may also include receiving an indication of acceptance or rejection of the request to join the multicast session.

[0006] According to some example embodiments, a computer program product may perform a method. The method may include attaching to a visited PLMN as an inbound roamer. The method may also include receiving a service announcement from an application function, the service announcement including at least one of a multicast service session indication or a multicast service category that is allowed to be accessed by the inbound roamer. The method may also include determining whether the device is allowed to access the multicast session or the multicast service category in the visited PLMN based on the service announcement. The method may also include sending a request to join the multicast session in response to determining that the device is allowed to access, the request including an identifier of the multicast session and / or the multicast service category. The method may also include receiving an indication of acceptance or rejection of the request to join the multicast session.

[0007] According to certain example embodiments, an apparatus may include at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least attach to a visited PLMN as an inbound roamer. The at least one memory and instructions, when executed by the at least one processor, may also cause the apparatus to at least receive a service announcement from an application function, the service announcement including at least one of a multicast service session indication or a multicast service category that is allowed to be accessed by the inbound roamer. The at least one memory and instructions, when executed by the at least one processor, may also cause the apparatus to at least determine whether the apparatus is allowed to access a multicast session or a multicast service category in the visited PLMN based on the service announcement. The at least one memory and instructions, when executed by the at least one processor, may also cause the apparatus to at least send a request to join a multicast session in response to determining that the apparatus is allowed to access, the request including an identifier of the multicast session and / or a multicast service category. The at least one memory and instructions, when executed by the at least one processor, may also cause the apparatus to at least receive an indication of acceptance or rejection of the request to join the multicast session.

[0008] According to various example embodiments, an apparatus may include an attachment circuit system configured to perform attachment to a visited PLMN as an inbound roamer. The apparatus may also include a receiving circuit system configured to perform receiving a service announcement from an application function, the service announcement including at least one of a multicast service session indication or a multicast service class that is allowed to be accessed by the inbound roamer. The apparatus may also include a determining circuit system configured to perform determining whether the apparatus is allowed to access a multicast session or a multicast service class in the visited PLMN based on the service announcement. The apparatus may also include a sending circuit system configured to perform sending a request to join a multicast session in response to determining that the apparatus is allowed to access, the request including an identifier of the multicast session and / or a multicast service class. The apparatus may also include a receiving circuit system configured to perform receiving an indication of acceptance or rejection of the request to join the multicast session.

[0009] According to certain example embodiments, a method may include processing, by a network entity, a local grooming packet data unit session for an inbound roamer user equipment. The method may also include receiving, by the network entity, a join request for a multicast service session or a multicast service class by the inbound roamer user equipment. The method may also include determining whether to accept the join request based on multicast roaming authorization information for the multicast service session or the multicast service class and / or the inbound roamer. The method may also include sending a join reply message indicating whether the join request is accepted or rejected.

[0010] According to certain example embodiments, an apparatus may include means for processing a local grooming packet data unit session for an inbound roamer user equipment. The apparatus may also include means for receiving a join request from the inbound roamer user equipment for a multicast service session or a multicast service class. The apparatus may also include means for determining whether to accept the join request based on multicast roaming authorization information for the multicast service session or the multicast service class and / or the inbound roamer. The apparatus may also include means for sending a join reply message indicating whether the join request was accepted or rejected.

[0011] According to various example embodiments, a non-transitory computer-readable medium may include program instructions that, when executed by an apparatus, cause the apparatus to perform at least one method. The method may include processing a local grooming packet data unit session for an inbound roamer user equipment. The method may also include receiving a join request for a multicast service session or a multicast service class from the inbound roamer user equipment. The method may also include determining whether to accept the join request based on multicast roaming authorization information for the multicast service session or the multicast service class and / or the inbound roamer. The method may also include sending a join reply message indicating whether the join request is accepted or rejected.

[0012] According to some example embodiments, a computer program product may perform a method. The method may include processing a local grooming packet data unit session for an inbound roamer user equipment. The method may also include receiving a join request for a multicast service session or a multicast service class by the inbound roamer user equipment. The method may also include determining whether to accept the join request based on multicast roaming authorization information for the multicast service session or the multicast service class and / or the inbound roamer. The method may also include sending a join reply message indicating whether the join request is accepted or rejected.

[0013] According to certain example embodiments, an apparatus may include at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least process a local grooming packet data unit session for an inbound roamer user equipment. The at least one memory and instructions, when executed by the at least one processor, may also cause the apparatus to at least receive a join request from the inbound roamer user equipment for a multicast service session or a multicast service class. The at least one memory and instructions, when executed by the at least one processor, may also cause the apparatus to at least determine whether to accept the join request based on at least multicast roaming authorization information for the multicast service session or the multicast service class and / or the inbound roamer. The at least one memory and instructions, when executed by the at least one processor, may also cause the apparatus to at least send a join reply message indicating whether the join request is accepted or rejected.

[0014] According to various example embodiments, an apparatus may include processing circuitry configured to perform processing a local grooming packet data unit session for an inbound roamer user equipment. The apparatus may also include receiving circuitry configured to perform receiving a join request for a multicast service session or a multicast service class by the inbound roamer user equipment. The apparatus may also include determining circuitry configured to perform determining whether to accept the join request based on multicast roaming authorization information for the multicast service session or the multicast service class and / or the inbound roamer. The apparatus may also include sending circuitry configured to perform sending a join reply message indicating whether the join request was accepted or rejected.

[0015] According to some example embodiments, a method may include determining, by a network entity, whether a multicast session or a multicast service class is open to an inbound roamer. The method may also include sending, by the network entity, a service announcement for the multicast session or the service class based on the determination, the service announcement indicating whether the inbound roamer is allowed to access the multicast service or the multicast service class.

[0016] According to certain example embodiments, an apparatus may include means for determining whether a multicast session or a multicast service class is open to an inbound roamer. The apparatus may also include means for sending a service announcement for the multicast session or the service class based on the determination, the service announcement indicating whether the inbound roamer is allowed to access the multicast service or the multicast service class.

[0017] According to various example embodiments, a non-transitory computer-readable medium may include program instructions that, when executed by an apparatus, cause the apparatus to perform at least one method. The method may include determining whether a multicast session or a multicast service class is open to an inbound roamer. The method may also include, based on the determination, sending a service announcement for the multicast session or service class, the service announcement indicating whether the inbound roamer is allowed to access the multicast service or the multicast service class.

[0018] According to some example embodiments, a computer program product may perform a method. The method may include determining whether a multicast session or a multicast service class is open to an inbound roamer. The method may also include sending a service announcement for the multicast session or the service class based on the determination, the service announcement indicating whether the inbound roamer is allowed to access the multicast service or the multicast service class.

[0019] According to certain example embodiments, an apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least determine whether a multicast session or a multicast service class is open to an inbound roamer. The at least one memory and the instructions, when executed by the at least one processor, may further cause the apparatus to at least send a service announcement for the multicast session or the service class based on the determination, the service announcement indicating whether the inbound roamer is allowed to access the multicast service or the multicast service class.

[0020] According to various example embodiments, an apparatus may include determining circuitry configured to perform a determination of whether a multicast session or a multicast service class is open to an inbound roamer. The apparatus may also include sending circuitry configured to send a service announcement for the multicast session or the service class based on the determination, the service announcement indicating whether the inbound roamer is allowed to access the multicast service or the multicast service class.

[0021] According to some example embodiments, a method may include receiving, from a first network entity, a request for establishment of a multicast session from a second network entity. The method may also include determining, by the first network entity, whether an inbound roamer is allowed to access the multicast session. The method may also include sending, by the first network entity, a response to the request, the response indicating whether the inbound roamer is allowed to access the multicast session.

[0022] According to certain example embodiments, an apparatus may include means for receiving a request for establishment of a multicast session from a network entity. The apparatus may also include means for determining whether an inbound roamer is allowed to access the multicast session. The apparatus may also include means for sending a response to the request, the response indicating whether the inbound roamer is allowed to access the multicast session.

[0023] According to various example embodiments, a non-transitory computer-readable medium may include program instructions that, when executed by an apparatus, cause the apparatus to perform at least one method. The method may include receiving a request for establishment of a multicast session from a network entity. The method may also include determining whether an inbound roamer is allowed to access the multicast session. The method may also include sending a response to the request, the response indicating whether the inbound roamer is allowed to access the multicast session.

[0024] According to certain example embodiments, a computer program product may perform a method. The method may include receiving a request for establishment of a multicast session from a network entity. The method may also include determining whether an inbound roamer is allowed to access the multicast session. The method may also include sending a response to the request, the response indicating whether the inbound roamer is allowed to access the multicast session.

[0025] According to certain example embodiments, an apparatus may include at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least receive a request for establishment of a multicast session from a network entity. The at least one memory and instructions, when executed by the at least one processor, may also cause the apparatus to at least determine whether an inbound roamer is allowed to access the multicast session. The at least one memory and instructions, when executed by the at least one processor, may also cause the apparatus to at least send a response to the request, the response indicating whether the inbound roamer is allowed to access the multicast session.

[0026] According to various example embodiments, an apparatus may include receiving circuitry configured to perform receiving a request for establishment of a multicast session from a network entity. The apparatus may also include determining circuitry configured to perform determining whether an inbound roamer is allowed to access the multicast session. The apparatus may also include sending circuitry configured to perform sending a response to the request indicating whether the inbound roamer is allowed to access the multicast session.

[0027] According to some example embodiments, a method may include receiving, by a first network entity, a request to establish a multicast session or service from a second network entity. The method may also include receiving, by the first network entity, a request for user service registration for a multicast service from a user device. The method may also include determining, by the first network entity, whether the user device is an inbound roaming user device. The method may also include determining, in response to determining that the user device is an inbound roaming user device, whether the user device is allowed to access the multicast session or service. The method may also include accepting a request from a user device based on a determination of whether the user device is allowed to access the multicast session or service, and providing a multicast broadcast service key to the user device, or rejecting a request from the user device.

[0028] According to certain example embodiments, an apparatus may include a component for receiving a request to establish a multicast session or service from a network entity. The apparatus may also include a component for receiving a request for a user service registration for a multicast service from a user device. The apparatus may also include a component for determining whether the user device is an inbound roaming user device. The apparatus may also include a component for determining whether the user device is allowed to access the multicast session or service in response to determining that the user device is an inbound roaming user device. The apparatus may also include a component for performing the following items based on the determination of whether the user device is allowed to access the multicast session or service: accepting the request from the user device and providing the multicast broadcast service key to the user device, or rejecting the request from the user device.

[0029] According to various example embodiments, a non-transitory computer-readable medium may include program instructions that, when executed by an apparatus, cause the apparatus to perform at least one method. The method may include receiving a request to establish a multicast session or service from a network entity. The method may also include receiving a request from a user device for a user service registration for a multicast service. The method may also include determining whether the user device is an inbound roaming user device. The method may also include determining whether the user device is allowed to access the multicast session or service in response to determining that the user device is an inbound roaming user device. The method may also include accepting a request from a user device based on a determination of whether the user device is allowed to access the multicast session or service, and providing a multicast broadcast service key to the user device, or rejecting a request from the user device.

[0030] According to some example embodiments, a computer program product may perform a method. The method may include receiving a request to establish a multicast session or service from a network entity. The method may also include receiving a request for user service registration for a multicast service from a user device. The method may also include determining whether the user device is an inbound roaming user device. The method may also include determining whether the user device is allowed to access the multicast session or service in response to determining that the user device is an inbound roaming user device. The method may also include accepting a request from a user device based on a determination of whether the user device is allowed to access the multicast session or service, and providing a multicast broadcast service key to the user device, or rejecting a request from the user device.

[0031] According to certain example embodiments, an apparatus may include at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least receive a request to establish a multicast session or service from a network entity. The at least one memory and instructions, when executed by the at least one processor, may also cause the apparatus to at least receive a request for user service registration for a multicast service from a user device. The at least one memory and instructions, when executed by the at least one processor, may also cause the apparatus to at least determine whether the user device is an inbound roaming user device. The at least one memory and instructions, when executed by the at least one processor, may also cause the apparatus to at least determine whether the user device is allowed to access the multicast session or service in response to determining that the user device is an inbound roaming user device. The at least one memory and instructions, when executed by the at least one processor, may also cause the apparatus to at least accept a request from the user device based on at least the determination of whether the user device is allowed to access the multicast session or service, and provide a multicast broadcast service key to the user device, or reject a request from the user device.

[0032] According to various example embodiments, an apparatus may include a receiving circuit system configured to perform receiving a request to establish a multicast session or service from a network entity. The apparatus may also include a receiving circuit system configured to perform receiving a request for user service registration for a multicast service from a user device. The apparatus may also include a determining circuit system configured to perform determining whether the user device is an inbound roaming user device. The apparatus may also include a determining circuit system configured to perform determining whether the user device is allowed to access the multicast session or service in response to determining that the user device is an inbound roaming user device. The apparatus may also include an accepting or rejecting circuit system configured to perform accepting a request from a user device based on a determination of whether the user device is allowed to access the multicast session or service, and providing a multicast broadcast service key to the user device, or rejecting a request from the user device.

[0033] According to some example embodiments, a method may include storing, by a network entity, user equipment multicast service subscription data of a user equipment, the user equipment multicast service subscription data including at least one of the following: an indication of whether the user equipment is authorized to access multicast services while roaming, an identification of an access PLMN in which the user equipment is authorized to access multicast services while roaming, an identification of an access PLMN in which the user equipment is not authorized to access multicast services while roaming, a class of multicast services that the user equipment is authorized to access while roaming, or a class of multicast services that the user equipment is not authorized to access while roaming. The method may also include receiving, by the network entity, a query or subscription for the user equipment multicast service subscription data of the user equipment. The method may also include providing, by the network entity, the user equipment multicast service subscription data of the user equipment in response to the query or subscription.

[0034] According to certain example embodiments, an apparatus may include means for storing user equipment multicast service subscription data of a user equipment, the user equipment multicast service subscription data including at least one of the following: an indication of whether the user equipment is authorized to access multicast services while roaming, an identification of an access PLMN in which the user equipment is authorized to access multicast services while roaming, an identification of an access PLMN in which the user equipment is not authorized to access multicast services while roaming, a class of multicast services that the user equipment is authorized to access while roaming, or a class of multicast services that the user equipment is not authorized to access while roaming. The apparatus may also include means for receiving a query or subscription for the user equipment multicast service subscription data of the user equipment. The apparatus may also include means for providing the user equipment multicast service subscription data of the user equipment in response to the query or subscription.

[0035] According to various example embodiments, a non-transitory computer-readable medium may include program instructions that, when executed by an apparatus, cause the apparatus to perform at least one method. The method may include storing user equipment multicast service subscription data of a user equipment, the user equipment multicast service subscription data including at least one of the following: an indication of whether the user equipment is authorized to access multicast services while roaming, an identification of an access PLMN in which the user equipment is authorized to access multicast services while roaming, an identification of an access PLMN in which the user equipment is not authorized to access multicast services while roaming, a multicast service class that the user equipment is authorized to access while roaming, or a multicast service class that the user equipment is not authorized to access while roaming. The method may also include receiving a query or subscription for the user equipment multicast service subscription data of the user equipment. The method may also include providing the user equipment multicast service subscription data of the user equipment in response to the query or subscription.

[0036] According to some example embodiments, a computer program product may perform a method. The method may include storing user equipment multicast service subscription data of a user equipment, the user equipment multicast service subscription data including at least one of the following: an indication of whether the user equipment is authorized to access the multicast service while roaming, an identification of an access PLMN in which the user equipment is authorized to access the multicast service while roaming, an identification of an access PLMN in which the user equipment is not authorized to access the multicast service while roaming, a multicast service class that the user equipment is authorized to access while roaming, or a multicast service class that the user equipment is not authorized to access while roaming. The method may also include receiving a query or subscription for the user equipment multicast service subscription data of the user equipment. The method may also include providing the user equipment multicast service subscription data of the user equipment in response to the query or subscription.

[0037] According to some example embodiments, an apparatus may include at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least store user equipment multicast service subscription data of a user equipment, the user equipment multicast service subscription data comprising at least one of the following: an indication of whether the user equipment is authorized to access multicast services while roaming, an identification of a visited PLMN in which the user equipment is authorized to access multicast services while roaming, an identification of a visited PLMN in which the user equipment is not authorized to access multicast services while roaming, a multicast service category that the user equipment is authorized to access while roaming, or a multicast service category that the user equipment is not authorized to access while roaming. The at least one memory and the instructions, when executed by the at least one processor, may also cause the apparatus to at least receive a query or subscription for the user equipment multicast service subscription data of the user equipment. The at least one memory and the instructions, when executed by the at least one processor, may also cause the apparatus to at least provide the user equipment multicast service subscription data of the user equipment in response to the query or subscription.

[0038] According to various example embodiments, an apparatus may include a storage circuit system configured to perform storage of user equipment multicast service subscription data of a user equipment, the user equipment multicast service subscription data including at least one of the following: an indication of whether the user equipment is authorized to access multicast services while roaming, an identification of an access PLMN in which the user equipment is authorized to access multicast services while roaming, an identification of an access PLMN in which the user equipment is not authorized to access multicast services while roaming, a multicast service class that the user equipment is authorized to access while roaming, or a multicast service class that the user equipment is not authorized to access while roaming. The apparatus may also include a receiving circuit system configured to perform receiving a query or subscription for the user equipment multicast service subscription data of the user equipment. The apparatus may also include a providing circuit system configured to perform providing the user equipment multicast service subscription data of the user equipment in response to the query or subscription. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] For a proper understanding of the example embodiments, reference should be made to the accompanying drawings, in which:

[0040] Figure 1 shows an example of a signaling diagram for multicast MBS service authorization for inbound and outbound roaming UEs in accordance with certain example embodiments;

[0041] Figure 2 illustrates an example of a signaling diagram for multicast MBS service authorization for an inbound roaming UE with a service announcement indicating whether the inbound roamer is allowed to access the MBS service in accordance with certain example embodiments;

[0042] Figure 3An example of a flow chart illustrating a method according to certain example embodiments;

[0043] Figure 4 An example of a flow chart illustrating a method according to some example embodiments;

[0044] Figure 5 An example of a flow chart illustrating a method according to various example embodiments;

[0045] Figure 6 An example of a flow chart illustrating a method according to certain example embodiments;

[0046] Figure 7 An example of a flow chart illustrating a method according to some example embodiments;

[0047] Figure 8 An example of a flow chart illustrating a method according to various example embodiments;

[0048] Fig. 9 illustrates examples of various network devices according to some example embodiments; and

[0049] Fig.10 Examples of 5G network and system architectures are shown in accordance with certain example embodiments. DETAILED DESCRIPTION

[0050] It will be readily appreciated that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a variety of different configurations. Therefore, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for roaming of multicast MBS services is not intended to limit the scope of certain example embodiments, but rather represents selected example embodiments.

[0051] Typically, MBS services can enable communication with multiple user devices. However, roaming is currently not supported for multicast MBS services. The visited public land mobile network (VPLMN) and / or the visited public land mobile network application function (V-AF) needs to allow or disallow multicast MBS services to inbound roamers, such as services provided locally in the VPLMN (e.g., local travel information) and / or service categories in the VPLMN from the same services subscribed by users in the HPLMN (e.g., weather forecast). In addition, the HPLMN needs to allow or disallow multicast MBS services to outbound roamers, such as, for example, services provided in the VPLMN (e.g., from the same service category subscribed by users in the HPLMN, such as weather forecast).

[0052] Certain example embodiments described herein may have various benefits and / or advantages to overcome the above-mentioned disadvantages. For example, certain example embodiments may enable the HPLMN operator to allow or disallow all or specific multicast MBS services when the UE is roaming (outbound) in the VPLMN, and may enable the VPLMN operator to allow or disallow all or specific multicast MBS services to UEs roaming (inbound) in the VPLMN. In addition, some example embodiments may enable the V-AF to allow or disallow specific multicast MBS services to UEs roaming (inbound) in the VPLMN. In addition, multicast MBS services may be identified by MBS service categories, thereby allowing different TMGIs or source-specific multicast addresses to be used in the HPLMN and each VPLMN. Various example embodiments may also save signaling by preventing the UE from unnecessarily attempting to join a multicast MBS session and then being rejected due to unauthorized roaming. Therefore, certain example embodiments discussed below are improvements to computer-related technologies.

[0053] Although the description below is provided using a PLMN, any of these example embodiments may instead be applied using an SNPN. In certain example embodiments, the VPLMN may be configured with authorization information indicating whether the multicast MBS service provided by the VPLMN is allowed to be accessed by inbound roamers of all or certain specific HPLMNs with which the VPLMN operator has a roaming / SLA agreement. The MBS service authorization configured in the VPLMN may be associated with an MBS session ID (e.g., a TMGI or a source-specific IP multicast address), may be associated with an MBS service category (e.g., weather forecast), and / or may be applicable to all MBS services provided by the VPLMN that are not restricted to specific users. In addition, the VPLMN MBS service authorization information may be configured in the MB-SMF of the VPLMN, in the SMF of the VPLMN, and / or in a database of the VPLMN.

[0054] During the establishment of a multicast MBS session, the AF attached to the VPLMN (V-AF) may indicate to the NEF / MB-SMF whether the MBS session is open to (i.e., allowed to be accessed by) inbound roamers from all or specific HPLMNs and / or the MBS service class of the MBS service it can provide. Alternatively, the NEF may be configured with a mapping of AF ID and / or MBS session ID to service class, and / or the service class may be added when forwarding the MBS session establishment request to the MB-SMF. In addition, the mapping of MBS session ID to service class may be configured in the VPLMN's database and looked up by the NEF, MB-SMF, and / or SMF in the VPLMN.

[0055] In the response to the MBS session establishment request, the MB-SMF / NEF may provide the service category to the NEF / AF. The NEF or MB-SMF may also indicate in the response to the establishment of the MBS session whether the inbound roamer is allowed to access the multicast MBS service, possibly together with the PLMN of the inbound roamer that is allowed (or not allowed).

[0056] A service announcement from the V-AF (or from the MBSF / MBSTF) may indicate whether the inbound roamer is allowed to access the multicast MBS service, possibly together with the PLMN of the inbound roamer that is allowed (or not allowed), and / or the service category of the MBS service. A service announcement may be provided by the V-AF to a roaming user only if the roaming user is authorized to use the service. An AF attached to a VPLMN may be configured with MBS service category and / or authorization information, or it may obtain authorization from the VPLMN when requesting to establish an MBS broadcast session, as described above. If the V-AF encrypts the broadcast data it provides, it may only provide the key to enable the description to roaming users who are authorized to use the service. In addition, the UE may be configured with information about the MBS service categories that it can access when roaming, which may be related to a specific VPLMN.

[0057] The UE MBS subscription in the UDM (e.g., HPLMN) may be extended with new roaming authorization information indicating whether the UE is allowed to access a specific multicast MBS service, a specific MBS service class, or all MBS services when the UE is roaming. The new authorization information may apply to a specific VPLMN stored as part of the UE MBS subscription information, or to any VPLMN (if no specific VPLMN is stored). Different specific MBS services or specific MBS service classes may be authorized for different VPLMNs.

[0058] The MBS service authorization configured in the user subscription may be associated with a list of MBS session IDs (eg, TMGI or source-specific IP multicast address) and / or an MBS service category (eg, weather forecast).

[0059] When a UE requests to join an MBS session, the UE may indicate a service class in addition to or instead of the MBS session ID.

[0060] The SMF in the VPLMN may authorize an inbound roamer requesting to join the multicast MBS service provided in the VPLMN, taking into account the VPLMN and / or HPLMN MBS service authorization information, and the MBS service category of the multicast MBS service (if available). The SMF may request the UDM in the HPLMN for UE MBS subscription information including new roaming authorization information. When requesting information about the MBS multicast service, the SMF may obtain information about the MBS service category for the MBS service and / or the VPLMN MBS service authorization information from the MB-SMF handling the MBS service, and / or the SMF may obtain the VPLMN MBS service authorization information from the database.

[0061] When a roaming UE requests to join a multicast MBS session in a VPLMN and the SMF finds that the UE is not authorized (as described above), the SMF may reject the UE request with a new cause indicating that access to the MBS service is not allowed / authorized in the VPLMN.

[0062] Figure 1 An example of a signaling diagram 100 is shown, which depicts multicast MBS service authorization for inbound and outbound roaming UEs. According to certain example embodiments, UE 120 may be similar to UE 920, and SMF 130, MB-SMF 140, NEF 150, V-AF 160, and UDM 170 may be similar to NE 910, such as Fig. 9 shown.

[0063] Typically, the UE 120 may establish a local break out (LBO) PDU session and request to join a multicast MBS session to access a multicast MBS service provided in the VPLMN. A call flow for establishing an LBO PDU session and a multicast MBS session in the VPLMN, and a call flow for the UE 120 to join a multicast MBS service in the VPLMN for non-roaming operation may be predefined. This may include an AMF, an SMF 130, an MB-SMF 140, an AF (not shown), an NEF 150, and / or an MBSF (not shown) located in the VPLMN, and a UDM 170 located in the HPLMN.

[0064] At operation 101, the VPLMN (i.e., SMF 130, MB-SMF 140, NEF 150) may be configured with authorization information for a multicast MBS service for an inbound roamer. Specifically, the VPLMN may be configured with authorization information indicating whether the multicast MBS service provided by the VPLMN is allowed to be accessed by inbound roamers of all or some HPLMNs with which the VPLMN operator has a roaming / SLA agreement. The authorization information may be configured in the VPLMN (e.g., at SMF 130, MB-SMF 140, and / or in a database (e.g., V-UDR or V-UDM for non-subscriber related information)).

[0065] The MBS service authorization configured in the VPLMN may be associated with an MBS session ID (e.g., TMGI or source-specific IP multicast address) or an MBS service category (e.g., weather forecast). In addition, there may be a default configuration (e.g., default rejection / acceptance) for all multicast MBS services not explicitly configured above. The VPLMN multicast MBS service authorization information may be configured at the MB-SMF 140 of the VPLMN, in the SMF of the VPLMN, or in a database of the VPLMN.

[0066] At operation 102, the V-AF 160 may provide the NEF 150 with a service category and / or multicast MBS service authorization information for an inbound roamer when establishing (or modifying) a multicast MBS session. For example, when establishing (or modifying) a multicast MBS session, the V-AF 160 (or the NEF 150 / MB-SMF 140 in the VPLMN) may indicate to the NEF 150 / MB-SMF 140 whether the MBS session is open to (i.e., allowed to be accessed by) inbound roamers from all or specific HPLMNs, and / or the MBS service category of the MBS service that may also be provided.

[0067] At optional operation 103, the VPLMN (i.e., NEF 150) may derive the service class when processing a request for establishing an MBS session and / or processing an MBS session join request. Alternatively, NEF 150 may be configured with a mapping of AF ID or MBS session ID to service class, and may add the service class when forwarding the MBS session establishment request to MB-SMF 140. In various example embodiments, the mapping may be configured in MB-SMF 140. In certain example embodiments, the mapping of MBS session ID to service class is configured in a database of the VPLMN and is looked up by NEF 150, MB-SMF 140, or SMF 130 in the VPLMN.

[0068] At operation 104, the V-AF 160 may send a create MBS session request to the MB-SMF 140, which may include an optional MBS session allowed to be accessed by the inbound roamer (optionally from a specific PLMN) and / or an optional MBS service class. Specifically, the V-AF 160 may provide the service class and / or VPLMN multicast MBS service authorization information in the service announcement. The service announcement from the V-AF 160 may indicate whether the inbound roamer is allowed to access the multicast MBS service (possibly together with the PLMN of the allowed (or not allowed) inbound roamer) and / or the service class of the MBS service. The MBS service announcement may indicate the service class and / or whether the inbound roamer is allowed (or not allowed) to access the multicast MBS service (optionally together with the HPLMN ID of the allowed (or not allowed) inbound roamer). Inbound roaming UEs may use this information to determine whether they can access the multicast MBS service provided by the VPLMN, and therefore whether they can request to join the multicast MBS service. The MBS service announcement may alternatively indicate whether the inbound roamer is allowed (or not allowed) to access the MBS service class corresponding to this multicast MBS service, optionally with the HPLMN ID of the allowed (or not allowed) inbound roamer for this MBS service class.

[0069] In various example embodiments, V-AF 160 may derive this information from configuration, or MB-SMF 140 / NEF 150 may provide this information to V-AF 160 in a response to an MBS session establishment request. If MBSF is deployed in a VPLMN, the service announcement may be provided by the MBSF, including the authorization information as described above, which may be obtained from V-AF 160 or from MB-SMF 140.

[0070] At optional operation 105, the MB-SMF 140 may determine the service class and / or look up the MBS session roaming authorization. For example, the VPLMN (i.e., the MB-SMF 140) may determine whether the multicast MBS service is accessible by an inbound roamer from other HPLMNs by determining whether the inbound roamer is allowed to access the MBS service, and if so, for inbound roamers from all HPLMNs or a specific HPLMN, considering the VPLMN authorization information configured in the VPLMN (at operation 101) and / or the authorization information for the multicast MBS service received from the V-AF (at operation 102). Based on operator policy, when both information are available, the multicast MBS service may be accessed by a UE from the HPLMN that is allowed by the VPLMN or by the V-AF 160, or by both the VPLMN and the V-AF 160.

[0071] At operations 106 and 107, MB-SMF 140 may send a create MBS session request to NEF 150 and V-AF 160, respectively, which may include an optional MBS session allowed to be accessed by an inbound roamer (optionally from a specific PLMN), and / or an optional MBS service class.

[0072] When SMF 130 subscribes to the multicast MBS session context state from MB-SMF 140 (when UE 120 requests to join a multicast MBS session, see Figure 1 In step 3b), MB-SMF 140 may indicate in a response to SMF 130 whether the multicast MBS session is accessible by inbound roamers from all or specific HPLMNs, or whether the MBS service class corresponding to this multicast MBS session is accessible by inbound roamers from all or specific HPLMNs. Alternatively, SMF 130 may look up VPLMN MBS session authorization information from a database based on the MBS service class or the MBS session ID.

[0073] When an inbound roaming UE requests to join an MBS session, SMF 130 (in the VPLMN) may check whether the multicast MBS service provided by the VPLMN is allowed to be accessed by UE 120, as defined in 3.

[0074] At operation 108, UE 120 may register with the VPLMN and establish an LBO PDU session. Specifically, the UE MBS subscription in the UDM may be extended with new authorization information indicating whether UE 120 is allowed to access a specific multicast MBS service, a specific multicast MBS service category, or all multicast MBS services when UE 120 is roaming, optionally with a list of VPLMNs in which the access is allowed (or not allowed). The new authorization information may also alternatively indicate a list of multicast MBS services or multicast MBS service categories that are not allowed when the UE is roaming, optionally with a list of VPLMNs in which they are not allowed.

[0075] The MBS service authorization in the subscription may be associated with an MBS session ID (eg, TMGI or source-specific IP multicast address) or an MBS service category (eg, weather forecast).

[0076] When the UE is roaming, at operation 110, SMF 130 in the VPLMN may retrieve the HPLMN MBS authorization information from UDM 170, and at operation 111, UDM 170 may indicate back to SMF 130 whether the UE MBS subscription allows UE 120 to access the multicast MBS session provided by the VPLMN. UE 120 may have received service announcements in its HPLMN, including a list of unauthorized MBS services, MBS service categories when roaming, and optionally unauthorized VPLMNs, and may therefore avoid sending requests to join MBS sessions when roaming in these unauthorized VPLMNs.

[0077] At operation 112, V-AF 160 may send a service announcement to UE 120, which may include optional MBS sessions and / or optional MBS service classes that are allowed to be accessed by an inbound roamer (optionally from a specific PLMN).

[0078] At operation 113, UE 120 may send a request to SMF 130 to join a multicast session, which may include an optional MBS service class.

[0079] At operation 114 , the SMF 130 may send an MBS context status subscription request to the MB-SMF 140 .

[0080] At operation 115, MB-SMF 140 may send an MBS context status subscription response to SMF 130, which may include optional MBS sessions allowed to be accessed by the inbound roamer (optionally from a specific PLMN) and optional MBS service categories.

[0081] At operation 116, the SMF 160 may check whether the multicast MBS service provided by the VPLMN is allowed to be accessed by an inbound roamer from the HPLMN of the UE, and whether the user's subscription received from the HPLMN (UDM) allows the UE to access the multicast MBS service in the VPLMN.

[0082] At operation 117, SMF 130 may send an acceptance or rejection to UE 120, which may indicate a reason, such as MBS service not allowed / authorized in the VPLMN response. If the VPLMN and / or V-AF 160 allow multicast MBS service to be accessed by UE 120 HPLMN, and if the user subscription received from the HPLMN allows the user to access the multicast MBS service in the VPLMN, then UE 120 may be accepted to join the multicast service. Otherwise, the UE request may be rejected with a new reason indicating that access to the MBS service (or MBS service class) is not allowed / authorized in the VPLMN (the reason may further distinguish whether the rejection is due to the VPLMN or the HPLMN not allowing access to the MBS service or service class in the VPLMN).

[0083] Figure 2 An example of a signaling diagram 200 for multicast MBS service authorization for an inbound roaming UE is shown, wherein a service announcement indicates whether the inbound roamer is allowed to access the MBS service. According to certain example embodiments, UE 210 may be similar to UE 920, and SMF 220, MB-SMF 230, NEF 150, V-AF / NEF 240, and UDM 250 may be similar to NE 910, such as Fig. 9 shown.

[0084] At operation 201, UE 210 may send a service announcement with an indication of whether an inbound roamer is allowed to access a multicast MBS service (and optionally, the PLMN of the allowed (or not allowed) inbound roamer).

[0085] At operation 202, if the service announcement indicates that UE 210 is not authorized to roam, UE 210 may not trigger the joining process.

[0086] However, at operation 203, the UE may trigger the joining process and Figure 1 The same process as described in .

[0087] Figure 3 1 and 2 according to various exemplary embodiments. Fig. 9 An example of a flowchart of a method 300 performed by a UE 920) shown in FIG.

[0088] At step 301 , the method may include attaching, by a user equipment, to a visited PLMN as an inbound roamer.

[0089] At step 302, the method may also include receiving, by the user equipment from the application function, a service announcement including at least one of a multicast service session indication or a multicast service class allowed to be accessed by the inbound roamer. The service announcement may indicate at least one PLMN of the inbound roamer that is allowed or not allowed.

[0090] At step 303, the method may further include determining, by the user equipment based on the service announcement, whether the user equipment is allowed to access the multicast session or multicast service class in the visited PLMN.

[0091] At step 304, the method may further include: in response to determining that the user equipment is allowed to access, sending, by the user equipment, a request to join the multicast session, the request including an identifier of the multicast session and / or a multicast service class.

[0092] At step 305, the method may further include receiving, by the user equipment, an indication of acceptance or rejection of the request to join the multicast session. The indication of rejection of the request to join the multicast session may include an indication that access to the multicast session is not permitted for an inbound roamer.

[0093] At step 306, the method may further include: registering, by the user equipment, with the visited PLMN.

[0094] At step 307, the method may further include establishing a local grooming protocol data unit session.

[0095] Figure 4 It shows that a NE (such as Fig. 9 An example of a flowchart of a method 400 performed by NE 910) shown in FIG.

[0096] At step 401, the method may include processing, by a network entity, a local breakout packet data unit session for an inbound roamer user equipment.

[0097] At step 402, the method may also include receiving, by the network entity, a request to join a multicast service session or a multicast service class from an inbound roamer user equipment.

[0098] At step 403, the method may further include determining whether to accept the join request based on multicast roaming authorization information for the multicast service session or multicast service class and / or the inbound roamer.

[0099] At step 404, the method may also include sending a join reply message indicating whether the join request is accepted or rejected.

[0100] At step 405, the method may further include retrieving, by the network entity, user equipment multicast service subscription data from the unified data manager, the user equipment multicast service subscription data including at least one of the following: an indication of whether the user equipment is authorized to access the multicast service while roaming, and an identifier of the access PLMN to which the user equipment is authorized to access the multicast service while roaming, and an identifier of the access PLMN to which the user equipment is not authorized to access the multicast service while roaming; and a multicast service category to which the user equipment is authorized to access while roaming, and a multicast service category to which the user equipment is not authorized to access while roaming. The user equipment multicast service subscription data may be used to determine whether to accept the join request.

[0101] At step 406, the method may also include obtaining, by the network entity, information about the context state of the multicast service session or multicast service class from the multicast session management function, the information including at least one of the following: an indication of whether the multicast service session or multicast service class is allowed to be accessed by the inbound roaming user equipment, and an identification of the home PLMN of the inbound roaming user equipment that is authorized to access the multicast service session or multicast service class, and an identification of the home PLMN of the inbound roaming user equipment that is not authorized to access the multicast service session or multicast service class, and the multicast service class for the multicast service session. The user equipment multicast service subscription data may be used to determine whether to accept the join request. The join reply message may indicate that the join request is rejected, the join reply message including an error reason, the error reason indicating that access to the multicast service session or multicast service class is not permitted for the inbound roamer.

[0102] Figure 5 It is shown that according to various example embodiments, a NE (such as Fig. 9 An example of a flowchart of method 500 performed by NE 910) shown in FIG.

[0103] At step 501, the method may include determining, by a network entity, whether a multicast session or a multicast service class is open to an inbound roamer. The determination may be based on configured information.

[0104] At step 502, the method may also include, based on the determination, sending, by the network entity, a service announcement for the multicast session or service class, the service announcement indicating whether the inbound roamer is allowed to access the multicast service or the multicast service class. The service announcement may also indicate at least one home PLMN of the inbound roamer that is allowed or not allowed.

[0105] At step 503, the method may further include requesting the second network entity to establish the multicast service, and indicating in the request whether the inbound roamer is allowed to access the multicast service.

[0106] At step 504, the method may further include requesting the second network entity to establish a multicast session.

[0107] At step 505, the method may further include receiving a reply to the request, the reply including at least one of: a second indication of whether the inbound roamer is allowed to access the multicast service session, an identification of a home PLMN of the inbound roaming user equipment that is authorized to access the multicast service session, and an identification of a home PLMN of the inbound roaming user equipment that is not authorized to access the multicast service session. The determination may be based on the second indication.

[0108] At step 506, the method may also include indicating the service class in the request for establishment of the multicast session.

[0109] Figure 6 It is shown that according to various example embodiments, a NE (such as Fig. 9 An example of a flowchart of method 600 performed by NE 910) shown in FIG.

[0110] At step 601, the method may include receiving, by a first network entity from a second network entity, a request for establishment of a multicast session. The request for establishment of a multicast session may include a multicast service class.

[0111] At step 602, the method may also include determining, by the first network entity, whether the inbound roamer is allowed to access the multicast session. The determination may be based on at least one of an identification of the second network entity, a multicast service class, configured information, or information obtained from a database.

[0112] At step 603, the method may further include sending, by the first network entity, a response to the request, the response indicating whether the inbound roamer is allowed to access the multicast session.

[0113] At step 604, the method may also include sending a request for establishment of a multicast session, wherein the request includes an indication of whether the inbound roamer is allowed to access the multicast service.

[0114] At step 605, the method may further include deriving, by the first network entity, a service class for the multicast session based on configuration information related to a service class for the second network entity and / or a service class for an identifier of the multicast session and / or a default service class.

[0115] At step 606, the method may further include sending, by the first network entity, a request for establishment of a multicast session, or a reply to the request for establishment of a multicast session, wherein the request or the reply includes the service class.

[0116] At step 607, the method may further include receiving, by the first network entity from a session management function, a subscription request for a context state of a multicast service session or a multicast service class.

[0117] At step 608, the method may also include: sending, by the first network entity, a context state of the multicast service session or the multicast service class, the context state including at least one of the following: an indication of whether the multicast service session or the multicast service class is allowed to be accessed by an inbound roaming user equipment, and an identifier of the home PLMN of the inbound roaming user equipment that is authorized to access the multicast service session or the multicast service class, and an identifier of the home PLMN of the inbound roaming user equipment that is not authorized to access the multicast service session or the multicast service class, and the multicast service class used for the multicast service session.

[0118] Figure 7 1 shows a method that can be performed by a NE or a UE (such as Fig. 9 An example of a flowchart of a method 700 performed by a NE 910 or a UE 920) shown in FIG.

[0119] At step 701 , the method may include receiving, by a first network entity from a second network entity, a request to establish a multicast session or service.

[0120] At step 702, the method may also include receiving, by the first network entity from a user equipment, a request for user service registration for a multicast service.

[0121] At step 703, the method may further include determining, by the first network entity, whether the user equipment is an inbound roaming user equipment.

[0122] At step 704, the method may also include, in response to determining that the user equipment is an inbound roaming user equipment, determining whether the user equipment is allowed to access the multicast session or service.

[0123] In some example embodiments, the determination may be based on at least one of: an identification of the second network entity, a home public land mobile network of the user equipment, roaming restriction information for the multicast session or service received within a request for establishment of the multicast session or service, a service class received in the request for establishment of the multicast session or service, configured roaming restriction information for at least one service class, at least one multicast session or service, or at least one home public land mobile network retrieved from a database, or roaming restriction information for at least one service class, at least one multicast session or service, or at least one home public land mobile network.

[0124] At step 705, the method may also include: based on the determination of whether the user equipment is allowed to access the multicast session or service, accepting the request from the user equipment and providing the user equipment with a multicast broadcast service key, or rejecting the request from the user equipment. For example, accepting may include providing the user equipment with an MBS service key. In various example embodiments, rejecting the user equipment's request may include at least a cause value that configures the user equipment to stop retrying user service registration for the multicast service.

[0125] At step 706, the method may further include sending an indication to the user equipment, the indication configuring the user equipment to stop retrying the user service registration and MBS service key for multicast.

[0126] Figure 8 It shows that a NE (such as Fig. 9 An example of a flowchart of method 800 performed by NE 910) shown in FIG.

[0127] In step 801, the method may include storing, by a network entity, user equipment multicast service subscription data of a user equipment, the user equipment multicast service subscription data of the user equipment including at least one of the following: an indication of whether the user equipment is authorized to access the multicast service while roaming, an identifier of an access PLMN in which the user equipment is authorized to access the multicast service while roaming, an identifier of an access PLMN in which the user equipment is not authorized to access the multicast service while roaming, a multicast service category that the user equipment is authorized to access while roaming, or a multicast service category that the user equipment is not authorized to access while roaming.

[0128] At step 802, the method may further include: receiving, by the network entity, a query or subscription for user equipment multicast service subscription data for the user equipment.

[0129] At step 803, the method may further include: providing, by the network entity in response to the query or subscription, user equipment multicast service subscription data of the user equipment.

[0130] Fig. 9 An example of a system according to certain example embodiments is shown. In an example embodiment, a system may include a plurality of devices, such as, for example, a NE 910 and / or a UE 920 .

[0131] NE 910 may be one or more of a base station (e.g., a 3G UMTS NodeB, a 4G LTE Evolution NodeB, or a 5G NR Next Generation NodeB), a serving gateway, a server, and / or any other access node or a combination thereof.

[0132] The NE 910 may also include at least one gNB centralized unit (CU), which may be associated with at least one gNB distributed unit (DU). The at least one gNB-CU and the at least one gNB-DU may communicate with each other via at least one F1 interface, at least one X n -C interface and / or communicate via at least one NG interface of the fifth generation core (5GC).

[0133] UE 920 may include one or more mobile devices, such as mobile phones, smart phones, personal digital assistants (PDAs), tablet computers or portable media players, digital cameras, pocket cameras, video game consoles, navigation units (such as global positioning system (GPS) devices), desktop or laptop computers, single-location devices (such as sensors or smart meters), or any combination thereof. In addition, NE 910 and / or UE 920 may be one or more Citizen Broadband Radio Service Devices (CBSDs).

[0134] NE 910 and / or UE 920 may include at least one processor, respectively denoted as 911 and 921. Processors 911 and 921 may be embodied by any computing or data processing device, such as a central processing unit (CPU), an application specific integrated circuit (ASIC), or the like. The processor may be implemented as a single controller, or multiple controllers or processors.

[0135] As shown in 912 and 922, at least one memory may be provided in one or more devices. The memory may be fixed or removable. The memory may include computer program instructions or computer codes contained therein. The memories 912 and 922 may be independently any suitable storage device, such as a non-transient computer-readable medium. The term "non-transient" used herein may correspond to the limitations of the medium itself (i.e., tangible, rather than a signal), rather than the limitations of data storage persistence (e.g., random access memory (RAM) versus read-only memory (ROM)). A hard disk drive (HDD), random access memory (RAM), flash memory or other suitable memory may be used. The memory may be combined on a single integrated circuit as a processor, or may be separated from one or more processors. In addition, the computer program instructions stored in the memory and processable by the processor may be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language.

[0136] Processors 911 and 921, memories 912 and 922, and any subset thereof may be configured to provide Figures 1 to 8Components corresponding to the various blocks. Although not shown, the device may also include positioning hardware, such as GPS or micro-electromechanical system (MEMS) hardware, which can be used to determine the location of the device. Other sensors are also allowed and can be configured to determine location, altitude, speed, direction, etc., such as a barometer, compass, etc.

[0137] like Fig. 9 As shown, transceivers 913 and 923 may be provided, and one or more devices may also include at least one antenna, shown as 914 and 924, respectively. The device may have many antennas, such as an antenna array configured for multiple-input multiple-output (MIMO) communication, or multiple antennas for multiple RATs. For example, other configurations of these devices may be provided. Transceivers 913 and 923 may be transmitters, receivers, both transmitters and receivers, or may be configured as units or devices for both transmission and reception.

[0138] The memory and the computer program instructions may be configured, together with the processor of a specific device, to cause a hardware device (such as a UE) to perform any of the above processes (ie, Figures 1 to 8 ). Thus, in certain example embodiments, a non-transitory computer readable medium may be encoded with computer instructions that, when executed in hardware, perform a process such as one of the processes described herein. Alternatively, certain example embodiments may be implemented entirely in hardware.

[0139] In certain example embodiments, an apparatus may include a device configured to perform Figures 1 to 8As used in this application, the term "circuitry" may refer to one or more or all of the following: (a) a pure hardware circuit implementation (such as, implemented only in analog and / or digital circuits); (b) a combination of hardware circuits and software, such as (as applicable): (i) a combination of (multiple) analog and / or digital hardware circuits and software / firmware and (ii) any portion of (multiple) hardware processors (including (multiple) digital signal processors), software and (multiple) memories with software, which together enable a device (such as a mobile phone or server) to perform various functions; (c) (multiple) hardware circuits and / or (multiple) processors (such as (multiple) microprocessors or portions of (multiple) microprocessors) that require software (e.g., firmware) to operate, but the software may not be present when the software is not required for operation. This definition of circuitry applies to all uses of the term in this application, including in any claims. As a further example, as used in this application, the term "circuitry" also covers implementations of only hardware circuits or processors (or multiple processors) or portions of hardware circuits or processors and their accompanying software and / or firmware. The term "circuitry" also covers, for example, a baseband integrated circuit or a processor integrated circuit for a mobile device or a similar integrated circuit in a server, cellular network device, or other computing or networking device, if applicable to a particular claim element.

[0140] Fig.10 An example of a 5G network and system architecture according to certain example embodiments is shown. Multiple network functions are shown that can be implemented as software operating as part of a network device or dedicated hardware, as a network device itself or dedicated hardware, or as virtual functions operating as a network device or dedicated hardware. Fig.10 The NE and UE shown in the figure may be similar to NE 910 and UE 920, respectively. The user plane function (UPF) may provide services such as intra-RAT and inter-RAT mobility, routing and forwarding of data packets, inspection of packets, user plane quality of service (QoS) processing, buffering of downlink packets and / or triggering of downlink data notifications. The application function (AF) may mainly interface with the core network to facilitate application use of traffic routing and interact with the policy framework.

[0141] According to some example embodiments, processors 911 and 921 and memories 912 and 922 may be included in a processing circuit system or a control circuit system or may form a part of a processing circuit system or a control circuit system. In addition, in some example embodiments, transceivers 913 and 923 may be included in a transceiver circuit system or may form a part of a transceiver circuit system.

[0142] In some example embodiments, an apparatus (e.g., NE 910 and / or UE 920) may include components for performing the methods, processes, or any variants discussed herein. Examples of components may include one or more processors, memories, controllers, transmitters, receivers, and / or computer program codes for causing the execution of operations.

[0143] The features, structures or characteristics of the example embodiments described in this specification may be combined in one or more example embodiments in any suitable manner. For example, the use of the phrases "various embodiments", "certain embodiments", "some embodiments" or other similar language in this specification refers to the specific features, structures or characteristics described in connection with the example embodiments may be included in at least one example embodiment. Therefore, the appearance of the phrases "in various embodiments", "in certain embodiments", "in some embodiments" or other similar language in this specification does not necessarily refer to the same set of example embodiments, and the features, structures or characteristics may be combined in one or more example embodiments in any suitable manner.

[0144] As used herein, “at least one of: ” and “at least one of ” and similar expressions, where a list of two or more elements is connected by “and” or “or”, mean at least any one element, or at least two or more elements, or at least all elements.

[0145] In addition, if necessary, the above-mentioned different functions or processes can be performed in different orders and / or concurrently with each other. In addition, if necessary, one or more of the functions or processes can be optional or can be combined. Therefore, the above description should be regarded as an explanation of the principles and teachings of some example embodiments, rather than a limitation thereof.

[0146] Those skilled in the art will readily appreciate that the above exemplary embodiments may be practiced with processes in a different order and / or hardware elements that are different from the disclosed configurations. Therefore, although some embodiments have been described based on these exemplary embodiments, it will be apparent to those skilled in the art that certain modifications, variations, and alternative configurations will be apparent while still falling within the spirit and scope of the exemplary embodiments.

[0147] Partial Glossary

[0148] 3GPP Third Generation Partnership Project

[0149] 5G Fifth Generation

[0150] 5GC Fifth Generation Core

[0151] 6G Sixth Generation

[0152] AF Application Function

[0153] AMF Access and Mobility Management Function

[0154] ASIC Application-Specific Integrated Circuit

[0155] CBSD Citizens Broadband Radio Service Device

[0156] CPU Central Processing Unit

[0157] CU Centralized Unit

[0158] DU Distributed Unit

[0159] eMBB Enhanced Mobile Broadband

[0160] eNB Evolved Node B

[0161] gNB Next Generation Node B

[0162] GPS Global Positioning System

[0163] HDD Hard Drive

[0164] HPLMN Home Public Land Mobile Network

[0165] IoT

[0166] LBO Local Banking

[0167] LTE Long Term Evolution

[0168] LTE-A Long Term Evolution Advanced

[0169] MBS Multicast / Broadcast Service

[0170] MBSF Multicast / Broadcast Service Function

[0171] MBSTF Multicast / Broadcast Service Delivery Function

[0172] MB-SMF Multicast / Broadcast Session Management Function

[0173] MEMS Micro-Electro-Mechanical Systems

[0174] MIMO Multiple Input Multiple Output

[0175] mMTC massive machine type communication

[0176] NE Network Entity

[0177] NEF Network Exposure Function

[0178] NG Next Generation

[0179] NG-eNB Next Generation Evolved Node B

[0180] NG-RAN Next Generation Radio Access Network

[0181] NR New Radio

[0182] PDA Personal Digital Assistant

[0183] PDU Protocol Data Unit

[0184] PLMN Public Land Mobile Network

[0185] QoS Quality of Service

[0186] RAM Random Access Memory

[0187] RAN Radio Access Network

[0188] RAT Radio Access Technology

[0189] RF

[0190] ROM Read Only Memory

[0191] SLA Service Level Agreement

[0192] SMF session management functions

[0193] SNPN Standalone Non Public Network

[0194] TMGI Temporary Mobility Group Identifier

[0195] UDM Unified Data Manager

[0196] UE User Equipment

[0197] UMTS Universal Mobile Telecommunications System

[0198] UPF User Plane Function

[0199] URLLC Ultra-Reliable Low Latency Communications

[0200] UTRAN Universal Mobile Telecommunications System Terrestrial Radio Access Network

[0201] V-AF Visited Public Land Mobile Network Application Function

[0202] VPLMN Visited Public Land Mobile Network

[0203] WLAN Wireless Local Area Network

Claims

1. A device for communication, the device comprising: means for attaching to a visited public land mobile network as an inbound roamer; means for receiving a service announcement from an application function, the service announcement comprising at least one of: a multicast service session indication allowed to be accessed by an inbound roamer, or a multicast service class; means for determining, based on the service advertisement, whether the device is allowed to access a multicast session or a multicast service class in the visited public land mobile network; means for sending a request to join a multicast session in response to determining that the apparatus is allowed access, the request including an identifier of the multicast session and / or a multicast service class; as well as Means for receiving an indication of an acceptance or a rejection of the request to join the multicast session.

2. The apparatus according to claim 1, further comprising: means for registering with said visited public land mobile network; as well as Components for establishing a local grooming protocol data unit session.

3. The apparatus of claim 1 or 2, wherein the service announcement indicates at least one public land mobile network that allows or does not allow inbound roamers.

4. The apparatus of any of claims 1-3, wherein the indication of the denial of the request to join the multicast session comprises an indication that access to the multicast session is not permitted for inbound roamers.

5. A device for communication, the device comprising: means for handling a locally-brought-out packet data unit session for an inbound roamer user equipment; means for receiving a request from the inbound roamer user equipment to join a multicast service session or a multicast service class; means for determining whether to accept the join request based on multicast roaming authorization information for the multicast service session or multicast service class, and / or the inbound roamer; as well as Means for sending a join reply message indicating whether the join request is accepted or rejected.

6. The apparatus according to claim 5, further comprising: A component for retrieving user equipment multicast service subscription data from a unified data manager, wherein the user equipment multicast service subscription data includes at least one of the following: an indication of whether the user equipment is authorized to access multicast services while roaming; an identification of a visited public land mobile network in which the user equipment is authorized to access multicast services while roaming; an identification of a visited public land mobile network in which the user equipment is not authorized to access a multicast service while roaming; The multicast service class to which the user equipment is authorized to access while roaming; or a class of multicast services that the user equipment is not authorized to access while roaming, wherein the user equipment multicast service subscription data is used to determine whether to accept the join request.

7. The device according to claim 5 or 6, further comprising: means for retrieving information about the context state of the multicast service session or multicast service class from a multicast session management function, the information comprising at least one of: an indication of whether the multicast service session or multicast service class is allowed to be accessed by an inbound roaming user equipment; the identity of the home public land mobile network of the inbound roaming user equipment that is authorized to access the multicast service session or multicast service class; the identity of the home public land mobile network of the inbound roaming user equipment that is not authorized to access the multicast service session or multicast service class; or the multicast service class for the multicast service session, The user equipment multicast service subscription data is used to determine whether to accept the join request.

8. The apparatus of any one of claims 5 to 7, wherein the join reply message indicating that the join request is rejected includes an error cause indicating that access to the multicast service session or multicast service class is not permitted for an inbound roamer.

9. An apparatus for communication, the apparatus comprising: means for determining whether a multicast session or a multicast class of service is open to an inbound roamer; as well as Means for sending a service announcement for a multicast session or class of service based on the determination, the service announcement indicating whether an inbound roamer is allowed to access the multicast service or class of multicast service.

10. The apparatus of claim 9, wherein the service announcement further indicates at least one home public land mobile network of an allowed or not allowed inbound roamer.

11. The apparatus according to any one of claims 9 or 10, wherein the determination is based on configured information.

12. The device according to any one of claims 9 to 11, further comprising: Means for requesting a network entity to establish the multicast service and indicating in the request whether an inbound roamer is allowed to access the multicast service.

13. The device according to any one of claims 9 to 12, further comprising: A component for requesting a network entity to establish the multicast session; as well as means for receiving a reply to the request, the reply comprising at least one of: a second indication of whether the inbound roamer is allowed to access the multicast service session, an identification of a home public land mobile network of the inbound roaming user equipment that is authorized to access the multicast service session, and an identification of a home public land mobile network of the inbound roaming user equipment that is not authorized to access the multicast service session, Wherein the determining is based on the second indication.

14. The device according to any one of claims 9 to 13, further comprising: Means for indicating the class of service in the request for the establishment of the multicast session.

15. An apparatus for communication, the apparatus comprising: means for receiving a request for establishment of a multicast session from a network entity; means for determining whether an inbound roamer is allowed access to the multicast session; as well as Means for sending a response to the request, the response indicating whether an inbound roamer is allowed to access the multicast session.

16. The apparatus of claim 15, wherein the request for the establishment of the multicast session comprises a multicast service class.

17. The apparatus according to claims 15 to 16, wherein the determination is based on at least one of: an identification of the network entity; the multicast service class; Configuration information; or Information obtained from the database.

18. The device according to any one of claims 15 to 17, further comprising: Means for sending a request for the establishment of the multicast session, wherein the request includes an indication of whether an inbound roamer is allowed to access the multicast service.

19. The device according to any one of claims 15 to 18, further comprising: means for deriving a class of service for the multicast session based on configuration information relating to: a class of service for the network entity, and / or a class of service for the identifier of the multicast session, and / or a default class of service; as well as Means for sending: a request for the establishment of the multicast session, or a reply to the request for the establishment of the multicast session, wherein the request or the reply comprises the service class.

20. The device according to any one of claims 15 to 19, further comprising: means for receiving, from a session management function, a subscription request for a context state of said multicast service session or multicast service class; as well as means for sending a context state of the multicast service session or multicast service class, the context state of the multicast service session or multicast service class comprising at least one of: an indication of whether the multicast service session or multicast service class is allowed to be accessed by an inbound roaming user equipment; the identity of the home public land mobile network of the inbound roaming user equipment that is authorized to access the multicast service session or multicast service class; the identity of the home public land mobile network of the inbound roaming user equipment that is not authorized to access the multicast service session or multicast service class; or The multicast service class to be used for the multicast service session.

21. An apparatus for communication, the apparatus comprising: means for receiving a request from a network entity to establish a multicast session or service; means for receiving, from a user equipment, a request for user service registration for said multicast service; component for determining whether the user equipment is an inbound roaming user equipment; means for determining, in response to determining that the user equipment is an inbound roaming user equipment, whether the user equipment is permitted to access the multicast session or service; as well as Means for performing, based on determining whether the user equipment is allowed to access the multicast session or service: accepting the request from the user equipment and providing the multicast broadcast service key to the user equipment, or The request from the user device is denied.

22. The apparatus of claim 21, wherein the rejection of the request of the user equipment comprises at least a cause value, the cause value configuring the user equipment to stop retrying the user service registration for the multicast service.

23. The apparatus of claim 21, wherein the rejection further comprises: Means for sending an indication to the user equipment, the indication configuring the user equipment to stop retrying the user service registration for the multicast, and an MBS service key.

24. The apparatus according to any one of claims 21 to 23, wherein the determination is based on at least one of: an identification of the network entity; a home public land mobile network of the user equipment; roaming restriction information for the multicast session or service, the roaming restriction information being received within the request for the establishment of the multicast session or service; a service class received in said request for said establishment of said multicast session or service; configured roaming restriction information retrieved from a database for: said at least one service class, said at least one multicast session or service, or at least one home public land mobile network; or Roaming restriction information for: the at least one service class, the at least one multicast session or service, or the at least one home public land mobile network.

25. An apparatus for communication, the apparatus comprising: A component for storing user equipment multicast service subscription data of a user equipment, wherein the user equipment multicast service subscription data comprises at least one of the following: an indication of whether the user equipment is authorized to access multicast services while roaming, an identification of a visited public land mobile network in which the user equipment is authorized to access a multicast service while roaming, an identification of a visited public land mobile network in which the user equipment is not authorized to access a multicast service while roaming, the multicast service class to which the user equipment is authorized to access while roaming, or a multicast service class that the user equipment is not authorized to access while roaming; means for receiving a query or subscription for said user equipment multicast service subscription data of said user equipment; as well as Means for providing the user equipment multicast service subscription data for the user equipment in response to the query or subscription.

Images