Method, apparatus and computer program

Abstract

There is provided an apparatus comprising means for providing a request for information related to a multicast / broadcast service (MBS) session, the MBS session being available in a public land mobile network, the request comprising an indication of a service category; receiving information related to an MBS session, the MBS session being available in a public land mobile network, the MBS session being associated with a service category; and receiving data associated with the MBS session based on the information.

Description

Cross-reference to related applications

[0001] This patent application claims priority to UK Patent Application No. 2315016.2, filed on 29 September 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0002] Various exemplary embodiments of this disclosure relate to methods, apparatus, and computer programs for communication systems. Background Technology

[0003] A communication network can be viewed as a facility that enables communication between two or more communication devices, or provides communication devices with access to a data network. Mobile or wireless communication networks are an example of communication networks. Communication devices can be provided with services through application servers.

[0004] Such communication networks operate according to standards provided by organizations such as 3GPP (3rd Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). Examples of these standards include the so-called 5G (fifth generation) standard provided by 3GPP. Summary of the Invention

[0005] Some exemplary embodiments of this disclosure will be described with reference to certain aspects. These aspects are not intended to indicate key or essential features of embodiments of this disclosure, nor are they intended to limit the scope of this disclosure. Other features, aspects, and elements will be apparent to those skilled in the art in light of this disclosure.

[0006] Various example embodiments relate to storing information at the network associated with multicast / broadcast service (MBS) sessions, where each MBS session is associated with a service category. Example embodiments also relate to the discovery of MBS sessions available to user equipment, where this discovery is based on service category.

[0007] According to one aspect, an apparatus is provided, the apparatus comprising components for: providing a request for information relating to a multicast / broadcast service MBS session, the MBS session being available in a public land mobile network, the request including an indication of a service class; receiving information relating to the MBS session, the MBS session being available in the public land mobile network and associated with the service class; and receiving data associated with the MBS session based on the information.

[0008] In the example, the request is provided to a storage device associated with a public land mobile network, or to at least one of the following: access and mobility management functions of the public land mobile network, or session management functions of the public land mobile network.

[0009] In the example, the information related to an MBS session available in a public terrestrial mobile network includes at least one of the following: an identifier for the MBS session, additional information related to the MBS service announcement, a textual description of the MBS session, or a Uniform Resource Identifier of an additional storage device, in which additional information about the MBS session is stored and available.

[0010] In the example, receiving also includes: retrieving additional information about the MBS session from another storage device based on the Uniform Resource Identifier when the information related to the MBS session includes a Uniform Resource Identifier.

[0011] In the example, receiving also includes: receiving information related to a plurality of MBS sessions available in a public terrestrial mobile network, each of the plurality of MBS sessions being associated with the service class; selecting an MBS session from the plurality of MBS sessions; and receiving data associated with the selected MBS session.

[0012] In the example, the MBS session is a multicast MBS session, and the receiving of data associated with the MBS session based on information includes components for: requesting to join the multicast MBS session based on the received information; and receiving data associated with the multicast MBS session.

[0013] In the example, the request includes the identifier of a public land mobile network, so that an MBS session is requested that is available at the public land mobile network, associated with a service class, and associated with the identifier of the public land mobile network.

[0014] In the example, the identifier of a public land mobile network includes at least one of the following: a mobile country code or a mobile network code.

[0015] In the example, a request is one of the following: a request included in the session-related signaling of the Protocol Data Unit (PDU) for the session management function, a query request, or a registration request.

[0016] In the example, PDU session-related signaling includes at least one of the following: PDU session establishment request or PDU modification request.

[0017] In the example, the component is also configured to: receive at least one user equipment routing policy rule, the at least one user equipment routing policy rule including: a data network name, and an identifier of a network slice to be used for accessing the storage device in the public land mobile network, and wherein the component for providing the request includes: a component for providing the request to the storage device using a PDU session with the received identifier of the data network name and the network slice received by the application.

[0018] In the example, the public land mobile network includes the visited public land mobile network.

[0019] In the example, one of the following is true: the device is used in the user equipment, the device is included in the user equipment, or the device is the user equipment.

[0020] According to one aspect, an apparatus for a public land mobile network is provided, the apparatus comprising: a network function configured to at least perform: discovering a server associated with the public land mobile network by querying a network repository function or using a domain name system query; providing the server with a request for information related to a multicast / broadcast service (MBS) session available at the public land mobile network, the request including an indication of a service class; receiving from the server the information related to the MBS session available at the public land mobile network, the MBS session being associated with a service class; and forwarding the information related to the MBS session to a user equipment.

[0021] In the example, the information related to an MBS session available in a public terrestrial mobile network includes at least one of the following: an identifier for the MBS session, additional information related to the MBS service announcement, a textual description of the MBS session, or a Uniform Resource Identifier of an additional storage device, in which additional information about the MBS session is stored and available.

[0022] In the example, the network function is also configured to perform: receiving requests from user equipment to join a multicast MBS session.

[0023] In the example, the network function is also configured to perform: receiving additional requests from the user equipment for an MBS session available in a public terrestrial mobile network, wherein the additional requests include service classes, and server discovery is performed in response to the additional requests received from the user equipment.

[0024] In the example, the network function is either AMF or SMF.

[0025] According to one aspect, a storage device for at least one public land mobile network is provided, the storage device comprising components for: receiving information related to a multicast / broadcast service MBS session, the information related to the MBS session including a service category associated with the MBS session; storing the information related to the MBS session for the MBS session; receiving a request for information related to the MBS session, the MBS session being available in the public land mobile network, the request including an indication of the service category; and providing the stored information related to the MBS session, the MBS session being available in the public land mobile network, the MBS session being associated with the service category.

[0026] In the example, the information related to an MBS session available in a public terrestrial mobile network includes at least one of the following: an identifier for the MBS session, additional information related to the MBS service announcement, a textual description of the MBS session, or a Uniform Resource Identifier of an additional storage device, in which additional information about the MBS session is stored and available.

[0027] In the example, the storage device is associated with multiple different public land mobile networks.

[0028] In the example, the stored information provided includes: information related to multiple MBS sessions that are available in the public land mobile network, and each of the multiple MBS sessions is associated with a service class.

[0029] In the example, information related to the MBS session is received either directly from the application function or via the network function.

[0030] In the example, the component is also used to: store information about multiple MBS sessions for a service category; and provide information about all MBS sessions for a service category.

[0031] In the example, the received information related to the MBS session also includes: an identifier of the public land mobile network associated with the MBS session, wherein the request also includes: an indication of the public land mobile network, and wherein the stored information related to the MBS session provided is associated with the public land mobile network indicated in the request, in which the MBS session is available.

[0032] In the example, one of the following is true: the storage device is a standalone device, or the storage device’s functionality is included in the network functionality.

[0033] In the example, the request includes an identifier for the PLMN.

[0034] In the example, the storage device is the server, or is provided by the server.

[0035] According to one aspect, an apparatus is provided, the apparatus comprising components for: providing information related to a multicast / broadcast service (MBS) session to a network open function or storage device of a public terrestrial mobile network, the information being stored at the storage device, the information related to the MBS session including the service category associated with the MBS session.

[0036] According to one aspect, an apparatus is provided, comprising: an application function configured to at least perform: providing information related to a multicast / broadcast service (MBS) session to a network open function or storage device of a public terrestrial mobile network, the information being stored at the storage device, the MBS session-related information including the service category associated with the MBS session.

[0037] In the example, the information related to an MBS session available in a public terrestrial mobile network includes at least one of the following: an identifier for the MBS session, additional information related to the MBS service announcement, a textual description of the MBS session, or a Uniform Resource Identifier of an additional storage device, in which additional information about the MBS session is stored and available.

[0038] In the example, the application function is also configured to perform: providing information related to the MBS session to the storage device, including the service category for the MBS session, such that the MBS session-related information is stored at the storage device.

[0039] In the example, the application functionality is also configured to perform: a component for establishing an MBS session; and a component for providing MBS session-related information to network open functions or multicast / broadcast session management functions, including the service category for the MBS session, such that the MBS session-related information is stored on a storage device.

[0040] According to one aspect, an apparatus is provided, comprising: a network function configured to at least perform: receiving from an application function a request for creating a multicast / broadcast service (MBS) session, the request including information related to the MBS session, the information including a service category associated with the MBS session; creating the MBS session based on the information related to the MBS session; authorizing the application function to use the MBS session; and providing the information related to the MBS session to a storage device such that the information related to the MBS session is stored at the storage device.

[0041] According to one aspect, an apparatus is provided, comprising components for: receiving from an application function a request for creating a multicast / broadcast service MBS session, the request including information related to the MBS session, the information related to the MBS session including a service category associated with the MBS session; creating the MBS session based on the information related to the MBS session; authorizing the application function to use the MBS session; and providing the information related to the MBS session to a storage device such that the information related to the MBS session is stored at the storage device.

[0042] In the example, the information related to an MBS session available in a public terrestrial mobile network includes at least one of the following: an identifier for the MBS session, additional information related to the MBS service announcement, a textual description of the MBS session, or a Uniform Resource Identifier of an additional storage device, in which additional information about the MBS session is stored and available.

[0043] In the example, application feature authorization is based on a request from the application feature. In the example, application feature authorization is based on pre-configured permissions associated with the application feature.

[0044] In the example, the component is also used to: receive a deletion request related to an MBS session; and provide the storage device with information related to the deletion of the MBS session, so that the information related to the MBS session is removed from the storage device.

[0045] In the example, one of the following is true: the device is used for a network function, the device is included in a network function, the network function is included in the device, or the device is a network function.

[0046] In the example, the network function is MB-SMF or NEF.

[0047] According to one aspect, a method is provided, comprising: providing a request for information relating to a multicast / broadcast service MBS session, the MBS session being available in a public land mobile network, the request including an indication of a service class; receiving information relating to the MBS session, the MBS session being available in the public land mobile network and associated with a service class; and receiving data associated with the MBS session based on the information.

[0048] In the example, the request is provided to a storage device associated with a public land mobile network, or to at least one of the following: access and mobility management functions of the public land mobile network, or session management functions of the public land mobile network.

[0049] In the example, the information related to an MBS session available in a public terrestrial mobile network includes at least one of the following: an identifier for the MBS session, additional information related to the MBS service announcement, a textual description of the MBS session, or a Uniform Resource Identifier for another storage device, in which additional information about the MBS session is stored and available.

[0050] In the example, the method includes retrieving additional information about the MBS session from another storage device based on the Uniform Resource Identifier when the information related to the MBS session includes a Uniform Resource Identifier.

[0051] In the example, receiving also includes: receiving information related to multiple MBS sessions available in a public terrestrial mobile network, each of the multiple MBS sessions being associated with a service class; selecting an MBS session from the multiple MBS sessions; and receiving data associated with the selected MBS session.

[0052] In the example, the MBS session is a multicast MBS session, and receiving data associated with the MBS session based on information includes: requesting to join the multicast MBS session based on the received information; and receiving data associated with the multicast MBS session.

[0053] In the example, the request includes the identifier of a public land mobile network, so that an MBS session is requested that is available at the public land mobile network, associated with a service class, and associated with the identifier of the public land mobile network.

[0054] In the example, the identifier of a public land mobile network includes at least one of the following: a mobile country code or a mobile network code.

[0055] In the example, a request is one of the following: a request included in the session-related signaling of the Protocol Data Unit (PDU) for the session management function, a query request, or a registration request.

[0056] In the example, PDU session-related signaling includes at least one of the following: PDU session establishment request or PDU modification request.

[0057] In the example, the method includes: receiving at least one user equipment routing policy rule, the at least one user equipment routing policy rule including: a data network name, and an identifier of a network slice to be used for accessing a storage device in a public land mobile network, and wherein providing a request includes: providing a request to the storage device using a PDU session with the data network name and the received identifier of the network slice received by the application.

[0058] In the example, the public land mobile network is the visited public land mobile network.

[0059] In the example, the method is executed by the user device.

[0060] According to one aspect, an apparatus is provided, comprising: at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform: providing a request for information relating to a multicast / broadcast service MBS session, the MBS session being available in a public land mobile network, the request including an indication of a service class; receiving information relating to the MBS session, the MBS session being available in the public land mobile network and associated with a service class; and, based on the information, receiving data associated with the MBS session.

[0061] In the example, the request is provided to a storage device associated with a public land mobile network, or to at least one of the following: access and mobility management functions of the public land mobile network, or session management functions of the public land mobile network.

[0062] In the example, the information related to an MBS session available in a public terrestrial mobile network includes at least one of the following: an identifier for the MBS session, additional information related to the MBS service announcement, a textual description of the MBS session, or a Uniform Resource Identifier for another storage device, in which additional information about the MBS session is stored and available.

[0063] In the example, the device is made to perform the following: when the information related to the MBS session includes a Uniform Resource Identifier, retrieve additional information about the MBS session from another storage device based on the Uniform Resource Identifier.

[0064] In the example, receiving also includes: receiving information related to multiple MBS sessions available in a public terrestrial mobile network, each of the multiple MBS sessions being associated with a service class; selecting an MBS session from the multiple MBS sessions; and receiving data associated with the selected MBS session.

[0065] In the example, the MBS session is a multicast MBS session, and receiving data associated with the MBS session based on information includes: requesting to join the multicast MBS session based on the received information; and receiving data associated with the multicast MBS session.

[0066] In the example, the request includes the identifier of a public land mobile network, so that an MBS session is requested that is available at the public land mobile network, associated with a service class, and associated with the identifier of the public land mobile network.

[0067] In the example, the identifier of a public land mobile network includes at least one of the following: a mobile country code or a mobile network code.

[0068] In the example, a request is one of the following: a request included in the session-related signaling of the Protocol Data Unit (PDU) for the session management function, a query request, or a registration request.

[0069] In the example, PDU session-related signaling includes at least one of the following: PDU session establishment request or PDU modification request.

[0070] In an embodiment, the apparatus is configured to perform: receiving at least one user equipment routing policy rule, the at least one user equipment routing policy rule including: a data network name, and an identifier of a network slice to be used for accessing a storage device in a public land mobile network, and wherein providing a request includes: providing a request to the storage device using a PDU session with the data network name and the received identifier of the network slice received by the application.

[0071] In the example, the public land mobile network is the visited public land mobile network.

[0072] In the example, one of the following is true: the device is used in the user equipment, the device is included in the user equipment, or the device is the user equipment.

[0073] According to one aspect, a method is provided, comprising: discovering a server associated with a public land mobile network by querying a network repository function or using a domain name system query; providing the server with a request for information related to a multicast / broadcast service (MBS) session available at the public land mobile network, the request including an indication of a service class; receiving the information related to the MBS session from the server, the MBS session being available at the public land mobile network and associated with a service class; and forwarding the information related to the MBS session to a user equipment.

[0074] In the example, the information related to an MBS session available in a public terrestrial mobile network includes at least one of the following: an identifier for the MBS session, additional information related to the MBS service announcement, a textual description of the MBS session, or a Uniform Resource Identifier of an additional storage device, in which additional information about the MBS session is stored and available.

[0075] In the example, the method includes receiving a request from the user equipment to join a multicast MBS session.

[0076] In the example, the method includes: receiving from a user equipment an additional request for an MBS session available in a public terrestrial mobile network, wherein the additional request includes a service class, and server discovery is performed in response to the additional request received from the user equipment.

[0077] In the example, the method is executed by a network function. In the example, this network function is either AMF or SMF.

[0078] According to one aspect, an apparatus is provided, comprising: at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to: discover a server associated with a public land mobile network by querying a network repository function or using a domain name system query; provide the server with a request for information related to a multicast / broadcast service (MBS) session available at the public land mobile network, the request including an indication of a service class; receive from the server the information related to the MBS session available at the public land mobile network and associated with a service class; and forward the information related to the MBS session to a user equipment.

[0079] In the example, the information related to an MBS session available in a public terrestrial mobile network includes at least one of the following: an identifier for the MBS session, additional information related to the MBS service announcement, a textual description of the MBS session, or a Uniform Resource Identifier of an additional storage device, in which additional information about the MBS session is stored and available.

[0080] In the example, the device is made to perform: receive a request from the user equipment to join a multicast MBS session.

[0081] In the example, the device is made to perform: receiving from a user equipment an additional request for an MBS session available in a public land mobile network, wherein the additional request includes a service class, and server discovery is performed in response to the additional request received from the user equipment.

[0082] In the example, one of the following is true: the device is used for a network function, the device is included in a network function, the network function is included in the device, or the device is a network function.

[0083] In the example, the network function is either AMF or SMF.

[0084] According to one aspect, a method is provided, comprising: receiving information related to a multicast / broadcast service MBS session, the information related to the MBS session including a service category associated with the MBS session; storing the information related to the MBS session for the MBS session; receiving a request for information related to the MBS session, the MBS session being available in a public land mobile network, the request including an indication of the service category; and providing the stored information related to the MBS session, the MBS session being available in the public land mobile network, the MBS session being associated with the service category.

[0085] In the example, the information related to an MBS session available in a public terrestrial mobile network includes at least one of the following: an identifier for the MBS session, additional information related to the MBS service announcement, a textual description of the MBS session, or a Uniform Resource Identifier of an additional storage device, in which additional information about the MBS session is stored and available.

[0086] In the example, the storage device is associated with multiple different public land mobile networks.

[0087] In the example, the stored information provided includes: information related to multiple MBS sessions that are available in the public land mobile network, and each of the multiple MBS sessions is associated with a service class.

[0088] In the example, information related to the MBS session is received either directly from the application function or via the network function.

[0089] In the example, information about multiple MBS sessions for a service category is stored; and information about all MBS sessions for a service category is provided.

[0090] In the example, the received information related to the MBS session also includes: an identifier of the public land mobile network associated with the MBS session, wherein the request also includes: an indication of the public land mobile network, and wherein the stored information related to the MBS session provided is associated with the public land mobile network indicated in the request, in which the MBS session is available.

[0091] In the example, one of the following is true: the storage device is a standalone device, or the storage device’s functionality is included in the network functionality.

[0092] In the example, the request includes an identifier for the PLMN.

[0093] According to one aspect, an apparatus is provided, comprising: at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform: receiving information related to a multicast / broadcast service (MBS) session, the information related to the MBS session including a service class associated with the MBS session; storing the information related to the MBS session for the MBS session; receiving a request for information related to the MBS session, the MBS session being available in a public land mobile network, the request including an indication of the service class; and providing the stored information related to the MBS session, the MBS session being available in the public land mobile network, the MBS session being associated with the service class.

[0094] In the example, the information related to an MBS session available in a public terrestrial mobile network includes at least one of the following: an identifier for the MBS session, additional information related to the MBS service announcement, a textual description of the MBS session, or a Uniform Resource Identifier of an additional storage device, in which additional information about the MBS session is stored and available.

[0095] In the example, the device is associated with several different public land mobile networks.

[0096] In the example, the stored information provided includes: information related to multiple MBS sessions that are available in the public land mobile network, and each of the multiple MBS sessions is associated with a service class.

[0097] In the example, information related to the MBS session is received either directly from the application function or via the network function.

[0098] In the example, the device is made to perform: storing information about multiple MBS sessions for a service class; and providing information about all MBS sessions stored for a service class.

[0099] In the example, the received information related to the MBS session also includes: an identifier of the public land mobile network associated with the MBS session, wherein the request also includes: an indication of the public land mobile network, and wherein the stored information related to the MBS session provided is associated with the public land mobile network indicated in the request, in which the MBS session is available.

[0100] In the example, one of the following is true: the device is used for the storage device, the device is included in the storage device, the storage device is included in the device, or the device is the storage device.

[0101] In the example, one of the following is true: the storage device is a standalone device, or the storage device’s functionality is included in the network functionality.

[0102] In the example, the request includes an identifier for the PLMN.

[0103] According to one aspect, a method is provided, comprising: providing information related to a multicast / broadcast service (MBS) session to a network open function or storage device of a public terrestrial mobile network, the information being stored at the storage device, the MBS session-related information including the service category associated with the MBS session.

[0104] In the example, the information related to an MBS session available in a public terrestrial mobile network includes at least one of the following: an identifier for the MBS session, additional information related to the MBS service announcement, a textual description of the MBS session, or a Uniform Resource Identifier of an additional storage device, in which additional information about the MBS session is stored and available.

[0105] In the example, the method includes: providing information related to the MBS session to a storage device, the information related to the MBS session including the service category for the MBS session, such that the information related to the MBS session is stored at the storage device.

[0106] In the example, the method includes: establishing an MBS session; and providing information related to the MBS session to network open functions or multicast / broadcast session management functions, including the service category for the MBS session, such that the information related to the MBS session is stored on a storage device.

[0107] In the example, the method is executed by the application function.

[0108] According to one aspect, an apparatus is provided, the apparatus comprising: 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 perform: providing information related to a multicast / broadcast service (MBS) session to a network open function or storage device of a public land mobile network, the information to be stored at the storage device, the information related to the MBS session including the service category associated with the MBS session.

[0109] In the example, the information related to an MBS session available in a public terrestrial mobile network includes at least one of the following: an identifier for the MBS session, additional information related to the MBS service announcement, a textual description of the MBS session, or a Uniform Resource Identifier of an additional storage device, in which additional information about the MBS session is stored and available.

[0110] In the example, the device is made to perform: provide information related to the MBS session to the storage device, including the service category for the MBS session, such that the information related to the MBS session is stored at the storage device.

[0111] In the example, the device is made to perform: establish an MBS session; and provide information related to the MBS session to network opening functions or multicast / broadcast session management functions, including the service category for the MBS session, such that the information related to the MBS session is stored at a storage device.

[0112] According to one aspect, a method is provided, comprising: receiving from an application function a request for creating a multicast / broadcast service MBS session, the request including information related to the MBS session, the information related to the MBS session including a service category associated with the MBS session; creating the MBS session based on the information related to the MBS session; authorizing the application function to use the MBS session; and providing the information related to the MBS session to a storage device such that the information related to the MBS session is stored at the storage device.

[0113] In the example, the information related to an MBS session available in a public terrestrial mobile network includes at least one of the following: an identifier for the MBS session, additional information related to the MBS service announcement, a textual description of the MBS session, or a Uniform Resource Identifier of an additional storage device, in which additional information about the MBS session is stored and available.

[0114] In the example, application feature authorization is based on a request from the application feature. In the example, application feature authorization is based on pre-configured permissions associated with the application feature.

[0115] In the example, the method includes: receiving a deletion request related to an MBS session; and providing the storage device with deletion-related information for the MBS session, such that the information related to the MBS session is removed from the storage device.

[0116] In the example, the method is executed by a network function. In the example, the network function is either MB-SMF or NEF.

[0117] According to one aspect, an apparatus is provided, comprising: at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform: receiving from an application function a request for creating a multicast / broadcast service (MBS) session, the request including information related to the MBS session, the information including a service category associated with the MBS session; creating the MBS session based on the information related to the MBS session; authorizing the application function to use the MBS session; and providing the information related to the MBS session to a storage device, such that the information related to the MBS session is stored at the storage device.

[0118] In the example, the information related to an MBS session available in a public terrestrial mobile network includes at least one of the following: an identifier for the MBS session, additional information related to the MBS service announcement, a textual description of the MBS session, or a Uniform Resource Identifier of an additional storage device, in which additional information about the MBS session is stored and available.

[0119] In the example, application feature authorization is based on a request from the application feature. In the example, application feature authorization is based on pre-configured permissions associated with the application feature.

[0120] In the example, the device is made to perform: receive a deletion request related to an MBS session; and provide the storage device with information related to the deletion of the MBS session, such that the information related to the MBS session is removed from the storage device.

[0121] In the example, one of the following is true: the device is used for a network function, the device is included in a network function, the network function is included in the device, or the device is a network function. In the example, the network function is MB-SMF or NEF.

[0122] According to one aspect, a computer program is provided, the computer program including instructions that, when executed by a device, cause the device to perform at least the following: providing a request for information relating to a multicast / broadcast service MBS session, the MBS session being available in a public land mobile network, the request including an indication of a service class; receiving information relating to the MBS session, the MBS session being available in a public land mobile network, the MBS session being associated with the service class; and, based on the information, receiving data associated with the MBS session.

[0123] According to one aspect, a computer program is provided, the computer program including instructions that, when executed by a device, cause the device to perform at least the following: discover a server associated with a public land mobile network by querying a network repository function or using a domain name system query; provide the server with a request for information related to a multicast / broadcast service (MBS) session available at the public land mobile network, the request including an indication of a service category; receive from the server the information related to the MBS session available at the public land mobile network, the MBS session being associated with a service category; and forward the information related to the MBS session to a user equipment.

[0124] According to one aspect, a computer program is provided, the computer program including instructions that, when executed by a device, cause the device to perform at least the following: receiving information related to a multicast / broadcast service MBS session, the information related to the MBS session including a service category associated with the MBS session; storing the information related to the MBS session for the MBS session; receiving a request for information related to the MBS session, the MBS session being available in a public land mobile network, the request including an indication of the service category; and providing the stored information related to the MBS session, the MBS session being available in a public land mobile network, the MBS session being associated with the service category.

[0125] According to one aspect, a computer program is provided, the computer program including instructions that, when executed by a device, cause the device to perform at least the following: providing information related to a multicast / broadcast service (MBS) session to a network open function or storage device of a public land mobile network, the information being stored at the storage device, the information related to the MBS session including the service category associated with the MBS session.

[0126] According to one aspect, a computer program is provided, the computer program including instructions that, when executed by a device, cause the device to perform at least the following: receiving from an application function a request for creating a multicast / broadcast service MBS session, the request including information related to the MBS session, the information related to the MBS session including a service category associated with the MBS session; creating the MBS session based on the information related to the MBS session; authorizing the application function to use the MBS session; and providing the information related to the MBS session to a storage device, such that the information related to the MBS session is stored at the storage device.

[0127] According to one aspect, an apparatus is provided, comprising: a circuit system configured to perform: providing a request for information relating to a multicast / broadcast service MBS session, the MBS session being available in a public land mobile network, the request including an indication of a service class; a circuit system configured to perform: receiving information relating to an MBS session, the MBS session being available in a public land mobile network, the MBS session being associated with a service class; and a circuit system configured to perform: receiving data associated with the MBS session based on the information.

[0128] Computer products stored on a medium can enable devices to perform the methods described herein.

[0129] A non-transitory computer-readable medium includes program instructions that, when executed by a device, cause the device to perform the methods described herein.

[0130] Electronic devices may include devices as described herein.

[0131] In the preceding text, various aspects have been described. It should be understood that additional aspects can be provided through any combination of two or more of the aforementioned aspects.

[0132] Various other aspects and additional embodiments are described in the following detailed description and the appended claims.

[0133] The subject matter of the independent claims is provided according to several aspects. Several other aspects are defined in the dependent claims. Embodiments not falling within the scope of the claims should be interpreted as examples that aid in understanding this disclosure.

[0134] List of abbreviations: AF: Application Functions AMF: Access and Mobility Management Function AN: Access Network BS: Base Station CN: Core Network DL: Downlink DNS: Domain Name System eNB: eNodeB gNB: gNodeB IIoT: Industrial Internet of Things LTE: Long Term Evolution NEF: Network Open Functionality NG-RAN: Next-Generation Radio Access Network NF: Network Functions NR: New Radio NRF: Network Repository Functionality NW: Network MBS: Multicast / Broadcast Service MB-SMF: Multicast / Broadcast Session Management Function MBSF: Multicast / Broadcast Service Function MCC: Mobile Country Code MNC: Mobile Network Code MS: Mobile Site PCF: Policy Control Function PLMN: Public Land Mobile Network RAN: Radio Access Network RF: Radio Frequency SMF: Session Management Function SNPN: Independent Non-Public Network UE: User Equipment UDR: Unified Data Repository UDM: Unified Data Management UL: Uplink URL: Uniform Resource Locator URSP: UE Routing Policy UPF: User-Face Functionality VPLMN: Access to Public Land Mobile Networks 3GPP: Third Generation Partnership Project 5G: Fifth Generation 5GC: 5G Core Network 5G-AN: 5G Radio Access Network 5GS: 5G system Attached Figure Description

[0135] Some exemplary embodiments will now be described with reference to the accompanying drawings, which are merely illustrative and non-limiting examples, in which:

[0136] Figure 1 This shows a schematic representation of a 5G system;

[0137] Figure 2 A schematic representation of the control device is shown;

[0138] Figure 3 A schematic representation of the terminal is shown;

[0139] Figure 4 A first example process is shown, including signaling and operations performed by an entity;

[0140] Figure 5 A second example process is shown, including signaling and operations performed by an entity;

[0141] Figure 6 A third example process is shown, including signaling and operations performed by the entity;

[0142] Figure 7 A fourth example process is shown, including signaling and operations performed by the entity;

[0143] Figure 8 A fifth example process is shown, including signaling and operations performed by the entity;

[0144] Figure 9 A flowchart of an example method executed by the device is shown;

[0145] Figure 10 A flowchart of another example method executed by the device is shown;

[0146] Figure 11 A flowchart of another example method executed by the device is shown;

[0147] Figure 12 This diagram illustrates a non-volatile memory medium for storing instructions, which, when executed by the processor, allow the processor to perform... Figure 9 , Figure 10 and / or Figure 11 One or more steps in the method. Detailed Implementation

[0148] Multicast / broadcast service (MBS) is a point-to-multipoint service provided by a communication system, in which data is sent from a single source entity to multiple receivers, for example, to all users (e.g., User Equipment (UE)) in a broadcast service area, or to users (e.g., UEs) in a multicast group. A session is a logical connection between a communication device (e.g., a UE) and a data network. An MBS session is the MBS counterpart of a Protocol Data Unit (PDU) session used by 5GC for unicast services. Corresponding MBS session types include broadcast MBS sessions or multicast MBS sessions. MBS sessions provided by 5GC can improve network efficiency and user experience when sending the same content to multiple users. An MBS service area is an area in which data for a multicast or broadcast MBS session can be sent. For location-related MBS, for each MBS service area, an identifier for the area session (e.g., an area session ID) is assigned. This identifier is unique for each MBS session, and the same location-related content data for the MBS session is delivered to (multiple) UEs within the MBS service area. The Area Session ID is a unique identifier within an MBS session and is used for MBS sessions with location-related content. When an Area Session ID exists, it is used, along with the Temporary Mobility Group Identifier (TMGI), to uniquely identify data streams of MBS sessions within a specific MBS service area.

[0149] For the purpose of providing MBS services to different users (e.g., different UEs), such as in scenarios where a UE is roaming, a “service category” for an MBS session has been defined. MBS sessions can be provided to users for many purposes and can transmit various types of information. For example, some MBS sessions may be used for traffic information, while others may be used for entertainment or news services. A service category represents a classification of MBS sessions based on their intended use. For a service category, in an example roaming use case, a user might wish to access services as follows: 1) A user might wish to be able to activate services provided locally on the visited network, such as those permitted by the user's home environment (e.g., local travel information); 2) A user who subscribes to a service category in their Home Public Land Mobile Network (HPLMN) might wish to enjoy services equivalent to those provided by the same service category as those provided by the Visited Public Land Mobile Network (VPLMN), without needing to explicitly subscribe in the VPLMN (e.g., weather forecasts).

[0150] In this way, users who subscribe to a service category in an HPLMN can expect to have access to home services provided via the visited PLMN without explicitly subscribing in a VPLMN (e.g., enjoying a subscribed service while roaming). However, users may not be able to determine the availability of MBS sessions within the service category. This issue may also occur for roaming users. Currently, there is no way to allow such MBS access based on service category (e.g., while roaming).

[0151] One or more of the identified issues are resolved in one or more of the examples below.

[0152] In the example, an apparatus (e.g., for a user equipment) is provided, including components for: providing a request for information related to a multicast / broadcast service MBS session, which is available in a public land mobile network, the request including an indication of a service class; a circuit system configured to perform: receiving information related to an MBS session, which is available in a public land mobile network and associated with a service class; and a circuit system configured to perform: receiving data associated with the MBS session based on the information.

[0153] In some examples, each PLMN (e.g., VPLMN) provides a storage device (or server) to allow the UE to discover / obtain information related to an MBS session within a service class that is available at the PLMN. In some examples, the storage device may be referred to as a server or a database. The database within the server can store information related to the MBS session within the storage service class. The storage device / server may be provided in hardware, software, or a combination of both.

[0154] In some examples, for multiple PLMNs, a storage device / server (which may be referred to as a "central storage device" or "central server") stores information related to MBS sessions available at the respective PLMNs across multiple PLMNs. Each MBS session is associated with a service class. The information associated with the MBS session may be stored along with the PLMN ID associated with that MBS session. In some examples, the "central" storage device / server may be operated by the GSMA (Global System for Mobile Communications Association).

[0155] In some examples, when an MBS session is created by the AF (or requested to be created by the AF), the AF registers the MBS session with the storage device.

[0156] In some examples, the storage device is standalone, or its functionality is included / integrated into an existing NF (e.g., performed by an existing NF). For example, the storage device may be integrated into a Multicast / Broadcast Service Function (MBSF) or a Multicast / Broadcast SMF (MB-SMF). In some examples, the UE directly requests / queries service category information for an MBS session or service information for a specific service category from the storage device. In some examples, the UE may utilize an AMF or SMF to query a server on behalf of the UE.

[0157] These examples will be referenced below from 5G communication systems capable of providing MBS sessions (e.g., such as...). Figure 1 (As shown in the diagram) will be discussed in more detail.

[0158] The various exemplary embodiments disclosed below are explained with reference to communication devices capable of communicating via wireless cellular systems, and communication systems serving such communication devices. Before explaining the various exemplary embodiments in detail, certain general aspects of wireless communication systems and communication devices are referenced. Figures 1 to 3 The explanations are brief to help understand the technology upon which the examples are based.

[0159] Figure 1 A schematic representation of a wireless communication system 100 is shown. The wireless communication system 100 includes one or more communication devices 102, such as user equipment (UE) or terminals. The wireless communication system 100 includes a 5G system (5GS). The 5GS includes a 5G radio access network (5G-RAN) 106, a 5G core network (5GC) 104 including one or more network functions (NFs), one or more application functions (AFs) 108, and one or more data networks (DNs) 110. The 5G-RAN 106 may include one or more gNodeB (gNB) distributed unit (DU) functions connected to one or more gNodeB (gNB) centralized unit (CU) functions. The 5GC 104 includes access management functions (AMF) 112, session management functions (SMF) 114, authentication server functions (AUSF) 116, user data management (UDM) 118, user plane functions (UPF) 120, network open functions (NEF) 122, and / or other NFs. Some examples shown below are applicable to the 3GPP 5G standard. However, some examples can also be applied to 5G-advanced, 4G, 3G and other 3GPP standards.

[0160] In the wireless communication system 100 (such as Figure 1In the system shown, communication device 102 (e.g., mobile communication device, terminal, user equipment, UE, machine-type communication device) is provided with wireless access via at least one base station or similar wireless transmitting and / or receiving node or point. Communication device 102 is provided with suitable signal receiving and transmitting means for enabling communication, such as enabling access to a communication network or direct communication with other devices. Communication device 102 can access a carrier provided by the base station or access point and transmit and / or receive communication on that carrier.

[0161] Figure 2 An example of device 200 is shown. Device 200 may include or implement Figure 1 The network function is one or more network functions of the 5GC shown above. The device 200 includes at least one random access memory (RAM) 211a, at least one read-only memory (ROM) 211b, at least one processor 212, 213, and an input / output interface 214. At least one processor 212, 213 is coupled to the RAM 211a and ROM 211b. At least one processor 212, 213 can be configured to execute appropriate software code 215. For example, software code 215 may allow the execution of one or more steps to perform one or more aspects or examples of this aspect or example. Software code 215 may be stored in ROM 211b.

[0162] Figure 3 An example of a communication device 300 is shown, such as Figure 1 The terminal shown is an example (e.g., communication device 102). Communication device 300 can be provided by any device capable of transmitting and receiving radio signals. Non-limiting examples of communication device 300 include user equipment, terminals, mobile stations (MS) or mobile devices (such as mobile phones or so-called "smartphones"), computers provided with wireless interface cards or other wireless interface facilities (e.g., USB dongles), personal data assistants (PDAs) or tablets provided with wireless communication capabilities, machine-type communication (MTC) devices, cellular Internet of Things (CIoT) devices, or any combination thereof. For example, communication device 300 can provide data communication for carrying communication. Communication can carry one or more of voice, email, SMS, multimedia, data, machine data, etc.

[0163] Communication device 300 can receive signals via air or radio interface 307 through suitable receiving means, and can transmit signals via suitable transmitting means. Figure 3In the diagram, the transceiver device is schematically represented by block 306. For example, the transceiver device 306 can be provided via radio components and an associated antenna arrangement. The antenna arrangement can be located inside or outside the mobile device.

[0164] The communication device 300 may be provided with at least one processor 301, at least one memory ROM 302a, at least one RAM 302b, and other possible components 303 for performing tasks designed to be performed with software and hardware assistance, including control of access to and communication with access systems and other communication devices. At least one processor 301 is coupled to RAM 302b and ROM 302a. At least one processor 301 may be configured to execute appropriate software code 308. For example, software code 308 may allow execution of one or more aspects of this aspect. Software code 308 may be stored in ROM 302a. The communication device 300 may include one or more circuits, or a circuit system (not shown) that may be configured to execute one or more aspects or examples of this aspect or examples.

[0165] Processors, memory, and other related control devices may be provided on a suitable circuit board and / or chipset. This feature is indicated by reference numeral 304. Communication device 300 may optionally have a user interface, such as a keyboard 305, a touchscreen or touchpad, or a combination thereof. Depending on the type of device, optionally, one or more of a display, speaker, and microphone may be provided.

[0166] Figure 4 The first example process is shown, including signaling and operations performed by the entity.

[0167] At S401, AF requests the establishment (or creation) of an MBS session. An MBS session is associated with a service category.

[0168] An AF can request the establishment (or creation) of an MBS session by submitting a request to the NEF (if the AF is untrusted) or to the MBSF (if the AF is trusted), whereby the request includes information related to the MBS session, including at least one of the following: an identifier for the MBS session (MBS session ID, also known as the "ID associated with the MBS session"), an indication of the service class used for the MBS session, or service information for the MBS. This request can be an Nnef_MBSSession_Create_Request message or any other suitable message.

[0169] In this example, the MBS session is for "MBS Session ID 1" and includes an indication of the service category and service information. In this example, NEF is addressed to receive messages from AF.

[0170] At S402, the NEF authorizes the AF to request the establishment (or creation) of an MBS session. The NEF can authorize the AF based on the received request. The NEF uses the service category indicated by the AF for that MBS session to register information related to the MBS session included in the request at the server. Figure 4 Examples and others Figures 5 to 8 In this document, the term "server" is used. It should be understood that, in the context of this disclosure, the term "storage device" may be used interchangeably with the term "server".

[0171] At S403, the NEF provides the MB-SMF with a request (from the AF) including information related to the MBS session provided by the AF in S401. The request can be provided as an Nmbsmf_MBSSession_Create_Request message or any other suitable message.

[0172] At S404, MB-SMF causes an MBS session to be created. MB-SMF can authorize the creation of an MBS session for use by AF. MB-SMF can cause an MBS session to be created based on a received request. MB-SMF can cause an MBS session to be created based on information related to the MBS session in the received request. MB-SMF registers information related to the MBS session with the server using the service category indicated by AF for that MBS session.

[0173] The NEF and / or MBSF may include information related to permissions (or authorization) for the AF, or may have access to information related to permissions for the AF. For example, information related to permissions for the AF may identify one or more PLMNs in which the AF is authorized to request an MBS session. The NEF and / or MBSF may use the information related to permissions for the AF to determine whether the AF is authorized to create an MBS session.

[0174] exist Figure 4 In the example, both NEF and MBSF perform authorization against AF. In other examples, either NEF or MBSF performs authorization. For example, when NEF performs authorization in S402, MBSF does not perform authorization, and vice versa.

[0175] At S405, the MB-SMF queries the Domain Name System (DNS) server to obtain information related to the server, such as the server's IP address. The DNS server is configured to store identification information for network functions, network entities, servers, etc. The server (or storage device) is configured to store information related to the MBS session, which is available in the PLMN. The MB-SMF can be configured with information used for discovery by the DNS server.

[0176] At S406, the MB-SMF sends a request to the server using the server's IP address to store information related to the MBS session created on the server. This request may be referred to as a "store" request. It should be understood that other appropriate terms are used in other examples. The storage request includes at least one of the following information related to the MBS session created on the server: MBS session ID, service category, or service information.

[0177] In some examples, the server can be implemented in hardware. In other examples, the server can be implemented in software, or a combination of hardware and software. The server stores information related to MBS sessions.

[0178] At S407, the UE has information that will be used for DNS server discovery. This information can be included in the UE's configuration. The configuration can be a pre-configured UE configuration. In other examples, the configuration is received by the UE.

[0179] At S408, the UE has a UE Routing Policy (URSP) rule that indicates the data network name (DNN) and network slice information to be used when querying the server IP address from the DNS server.

[0180] At S409, a UE user can request to determine the available MBS sessions associated with a service category.

[0181] At S410, in order to determine the available MBS sessions with the service class, the UE queries the DNS server to determine the server's IP address. The server's IP address is provided to the UE from the DNS server.

[0182] At S411, the UE provides the server with a request for information related to an MBS session available in the PLMN, where the request includes an indication of the service class. In other examples, the UE provides indications of multiple different service classes. The UE provides the server's IP address to the request. The server is associated with the PLMN. In some examples, the PLMN can be a VPLMN.

[0183] In this way, at S411, the UE queries the server to learn about MBS sessions for a specific service category.

[0184] At S412, the UE receives information from the server related to at least one MBS session, which is available in the PLMN. The at least one MBS session available in the PLMN is associated with a service class. The information may include at least one of the following: an identifier for the MBS session (e.g., MBS session identifier (ID)), service information, MBS session information, a Uniform Resource Locator (URL), and the server's Fully Qualified Domain Name (FQDN) (which the UE can use to determine the server's Internet Protocol address using a Domain Name Server procedure).

[0185] When the UE provides an indication for multiple different service categories at S411, the server provides information related to the MBS session associated with the multiple service categories.

[0186] At S413, when the information received from the server includes a URL, the UE retrieves additional information about the MBS session from the URL.

[0187] At S414, when information from the server indicates the existence of multiple available MBS sessions associated with a service category, these multiple available MBS sessions are available at the PLMN, and the UE can select (or pick) an MBS session from these multiple available MBS sessions. In other examples, a single MBS session is available, so the UE does not select or pick an MBS session.

[0188] The UE selects an MBS session from multiple available MBS sessions associated with a service class and receives data from it. The MBS session is selected from multiple available (available) MBS sessions associated with a service class. In some examples, the UE will present a graphical user interface on its display, which includes optional icons associated with each available MBS session related to the service class. The UE's user can select an available MBS session by choosing one of the optional icons on the UE's display.

[0189] At S415, when the MBS session is a multicast MBS session, the UE provides a join request to the SMF to join the MBS session. The join request identifies the selected multicast MBS session. For example, the multicast MBS session is identified using the MBS session ID (e.g., MBS session ID1).

[0190] At S416, the UE receives data associated with the MBS session. In some examples (e.g., after the join request at S415), the MBS session can be a multicast MBS session. In other examples, the MBS session can be a broadcast MBS session. When the session is a broadcast MBS session, the data used for the broadcast MBS session will be received via broadcast within the MBS service area.

[0191] Figure 5 A second example process is shown, which includes signaling and operations performed by an entity.

[0192] At S500, the server associated with the PLMN is integrated into / included in the MB-SMF. The MB-SMF registers with the NRF and acts as a server.

[0193] At S501, AF requests the establishment (or creation) of an MBS session. An MBS session is associated with a service category.

[0194] The AF provides a request to the NEF or MBSF, which includes information related to the MBS session, including at least one of the following: MBS session ID (also referred to as "ID associated with the MBS session"), service category, or service information. The request can be an Nnef_MBSSession_Create_Request message or any other suitable message.

[0195] In this example, the MBS session is for MBS session ID 1 and includes service category information and service information. In this example, NEF is addressed.

[0196] At S502, the NEF authorizes the AF to request the establishment (or creation) of an MBS session. The NEF can authorize the AF based on the received request. The NEF uses the service class indicated by the AF for that MBS session to register information related to the MBS session included in the request at the server.

[0197] In some examples, the server can be implemented in hardware. In other examples, the server can be implemented in software, or a combination of hardware and software. The server is capable of storing information related to MBS sessions.

[0198] At S503, NEF provides the MB-SMF with a request (from AF) along with information provided by AF in S501. This request can be provided as an Nmbsmf_MBSSession_Create_Request message or any other suitable message.

[0199] At S504, the MB-SMF authorizes the AF to create an MBS session. The MB-SMF can authorize the AF based on a received request. The MB-SMF causes the MBS session to be created. The MB-SMF can authorize the creation of the MBS session for use by the AF. The MB-SMF can cause the MBS session to be created based on a received request. The MB-SMF can cause the MBS session to be created based on information related to the MBS session in the received request. The MB-SMF registers information related to the MBS session with the server using the service category indicated by the AF for this MBS session.

[0200] The NEF and / or MBSF may include information related to permissions (or authorization) for the AF, or may have access to information related to permissions for the AF. For example, information related to permissions for the AF may identify one or more PLMNs in which the AF is authorized to request an MBS session. The NEF and / or MBSF may use the information related to permissions for the AF to determine whether the AF is authorized to create an MBS session.

[0201] exist Figure 5 In the example, both NEF and MBSF perform authorization against AF. In other examples, either NEF or MBSF performs authorization. For example, when NEF performs authorization in S502, MBSF does not perform authorization, and vice versa.

[0202] At S505, information about MBS sessions and service categories is stored on the server and / or in the MB-SMF. This information may include at least one of the following: MBS session ID, service category, or service information. The server is integrated with the MB-SMF. In other examples, the MB-SMF requests storage at another MB-SMF with an integrated server.

[0203] At S506, the UE has a UE Routing Policy (URSP) rule that indicates the data network name (DNN) and network slice information to be used when querying the server IP address from the DNS server.

[0204] At S507, the UE's user can request to determine the available MBS sessions in the service category.

[0205] At S508, the UE sends a query or request to the SMF that includes the service category.

[0206] At S509, the SMF discovery server is integrated into the MB-SMF. The SMF can discover the server by querying the NRF.

[0207] At S510, the SMF provides a request to the server or MB-SMF for information related to an MBS session available in the PLMN, where the request includes an indication of the service class. In other examples, the SMF provides indications for multiple different service classes. The SMF provides the request based on server discovery. The server is associated with the PLMN. In some examples, the PLMN can be a VPLMN.

[0208] In this way, at S510, the SMF queries the server to learn about sessions for a specific service category.

[0209] At S511, the SMF receives information from the server related to at least one MBS session, which is available in the PLMN. At least one MBS session is associated with a service class. The information may include at least one of the following: MBS session ID, service information, session information, MBS session ID, or Uniform Resource Locator (URL).

[0210] When the SMF provides indications for multiple different service categories in S510, the server provides information related to MBS sessions associated with multiple service categories in S511.

[0211] At S512, the SMF provides a response to the UE, which includes information related to at least one MBS session within at least one service class, which is available in the PLMN. This information may be provided in the Ndb_Query_Response message or any other suitable message.

[0212] At S513, when the information received from the server includes a URL, the UE retrieves additional information about the MBS session from the URL.

[0213] At S514, when information from the server indicates the existence of multiple available MBS sessions associated with a service category, these multiple available MBS sessions are available at the PLMN, and the UE can select (or pick) an MBS session from these multiple available MBS sessions. In other examples, a single MBS session is available, so the UE does not select or pick an MBS session.

[0214] In some examples, the UE user will be offered an available MBS session to choose from (e.g., on the UE's display).

[0215] At S515, when the session is a multicast MBS session, the UE provides a join request to the SMF to join the MBS session. The join request identifies the selected multicast MBS session. For example, the multicast MBS session is identified using the MBS session ID (e.g., MBS session ID 1).

[0216] At S516, the UE receives data associated with the MBS session. In some examples, the session can be a multicast MBS session. In other examples, the session can be a broadcast MBS session. When the session is a broadcast MBS session, the data used for the session will be received via broadcast within the MBS service area.

[0217] Figure 6 A third example process is shown, which includes signaling and operations performed by an entity.

[0218] At S600, a server associated with the PLMN is provided. The server registers with the NRF. In some examples, the server can be implemented in hardware. In other examples, the server can be implemented in software, or a combination of hardware and software. The server is capable of storing information related to MBS sessions.

[0219] At S601, AF communicates (directly) with the server and registers the MBS session with the server. Registering the MBS session with the server can be referred to as a "storage request" for the MBS session at the server.

[0220] An AF can create / establish an MBS session. In other examples, another NF establishes the MBS session. An MBS session is associated with a service class.

[0221] As part of the storage request, the AF provides information related to the MBS session. This information includes at least one of the following: the MBS session ID (also referred to as the "ID associated with the MBS session"), the service category, or service information. The AF may provide the server with an Ndb_Storage_Request message or any other suitable message along with the MBS session-related information.

[0222] In this example, the MBS session is for MBS session ID 1, and the information associated with the MBS session includes service category information and service information.

[0223] At S602, the server authorizes the AF. The server can authorize the AF to use (or create) an MBS session. The server can authorize the AF based on the received message. In this way, the server authorizes the AF for such registration for an MBS session.

[0224] At S603, information related to the MBS session (including the service category associated with the MBS session) is stored on the server.

[0225] At S604, the UE provides the AMF with a request for information related to an MBS session available in the PLMN, where the request includes an indication of the service category. In this way, the UE queries the AMF to learn about MBS sessions for a specific service category. In some examples, the request or query may be included in the registration request message. In other examples, the UE provides indications for multiple different service categories.

[0226] At S605, the AMF discovers the server. The SMF can discover the server by querying the NRF. In some examples, the AMF already knows the server, so server discovery is avoided at S605.

[0227] At S606, the AMF provides the server with a request for information related to an MBS session available in the PLMN, including an indication of the service class. The AMF provides the request based on the discovery of the server. The server is associated with the PLMN. In some examples, the PLMN can be a VPLMN.

[0228] In this way, at S606, the AMF queries the server to learn about MBS sessions for a specific service category.

[0229] At S607, the AMF receives information from the server related to at least one MBS session, which is available in the PLMN. At least one MBS session is associated with a service class. The information may include at least one of the following: MBS session ID, service information, session information, MBS session ID, or Uniform Resource Locator (URL).

[0230] At S608, the AMF provides a response to the UE, which includes information related to at least one MBS session available in the PLMN. This information may be included in a registration response message or any other suitable message.

[0231] At S609, when the information received from the server includes a URL, the UE retrieves additional information about the MBS session from the URL.

[0232] At S610, when information from the server indicates the existence of multiple available MBS sessions associated with a service category, these multiple available MBS sessions are available at the PLMN, and the UE can select (or pick) an MBS session from these multiple available MBS sessions. In other examples, a single MBS session is available, so the UE does not select or pick an MBS session.

[0233] In some examples, the UE user will be offered an available MBS session to choose from (e.g., on the UE's display).

[0234] At S611, when the session is a multicast MBS session, the UE provides a join request to the SMF to join the MBS session. The join request identifies the selected multicast MBS session. For example, the multicast MBS session is identified using the MBS session ID (e.g., MBS session ID 1).

[0235] At S612, the UE receives data associated with the MBS session. In some examples, the session can be a multicast MBS session. In other examples, the session can be a broadcast MBS session. When the session is a broadcast MBS session, the data used for the session will be received via broadcast within the MBS service area.

[0236] Figure 7 A fourth example process is shown, which includes signaling and operations performed by an entity.

[0237] At S701, AF requests the establishment (or creation) of an MBS session. An MBS session is associated with a service class. In other words, the MBS session exists within a service class.

[0238] The creation of an MBS session involves the AF providing a request to the NEF, which includes at least one of the following: the MBS session ID (also referred to as the "ID associated with the MBS session"), the service category, or service information. The request also includes at least one PLMN ID in which the service should be available. In this example, the MBS session will be available in PLMN A. The request may include an indication of the PLMN A ID used for the MBS session. The request can be an Nnef_MBSSession_Create_Request message, or any other suitable message.

[0239] In this example, the MBS session is for MBS session ID 1 and includes service category information and service information.

[0240] At S702, the NEF authorizes the AF to request the establishment (or creation) of an MBS session. The NEF can authorize the AF based on the received request. The NEF uses the service class indicated by the AF for that MBS session to register information related to the MBS session included in the request at the server.

[0241] In some examples, the server can be implemented in hardware. In other examples, the server can be implemented in software, or a combination of hardware and software. The server is capable of storing information related to MBS sessions.

[0242] At S703, NEF provides the MB-SMF with a request (from AF) along with information provided by AF in S701. This request can be provided as an Nmbsmf_MBSSession_Create_Request message or any other suitable message.

[0243] At S704, the MB-SMF authorizes the AF to create an MBS session. The MB-SMF can authorize the AF based on a received request. The MB-SMF causes the MBS session to be created. The MB-SMF can authorize the creation of the MBS session for use by the AF. The MB-SMF can cause the MBS session to be created based on a received request. The MB-SMF can cause the MBS session to be created based on information related to the MBS session in the received request. The MB-SMF registers information related to the MBS session with the server using the service category indicated by the AF for this MBS session.

[0244] The NEF and / or MBSF may include information related to permissions (or authorization) for the AF, or may have access to information related to permissions for the AF. For example, information related to permissions for the AF may identify one or more PLMNs in which the AF is authorized to request an MBS session. The NEF and / or MBSF may use the information related to permissions for the AF to determine whether the AF is authorized to create an MBS session.

[0245] exist Figure 7 In the example, both NEF and MBSF perform authorization against AF. In other examples, either NEF or MBSF performs authorization. For example, when NEF performs authorization in S702, MBSF does not perform authorization, and vice versa.

[0246] At S705, the MB-SMF queries a Domain Name System (DNS) server to determine information related to the server, such as the server's IP address. The MB-SMF can be configured with information about DNS server discovery. The DNS server is configured to store identification information for network functions, network entities, servers, etc. A server (or storage device) is configured to store information related to the MBS session, which is available in the PLMN.

[0247] In this example, the server is associated with a first PLMN (“PLMN A”) and one or more other PLMNs. In some examples, PLMN A may be a VPLMN. The server is able to store MBS session information for PLMN A and for one or more other PLMNs.

[0248] At S706, the MB-SMF uses the server's IP address to send a request to the server that the created MBS session will be stored on the server. This request may be referred to as a "storage" request. It should be understood that other appropriate terms are used in other examples.

[0249] Since the server is associated with multiple PLMNs, the request identifies the associated PLMN. In this example, since an MBS session will be available for PLMN A, the request identifies PLMN A. The storage request includes at least one of the following: the PLMN's identifier (e.g., PLMN A ID), the MBS session ID, the service category, or service information.

[0250] At S707, the server performs an authorization check on the MB-SMF to store MBS session information for PLMN A. When the authorization check succeeds, the server stores the received information. In other examples, the server may have already pre-authorized the MB-SMF for PLMN A. In this example, the server will store the MBS session information for PLMN A upon receiving a storage request.

[0251] At S708, the UE has information that will be used for DNS server discovery. This information can be included in the UE's configuration. The configuration can be a pre-configured UE configuration. In other examples, the configuration is received by the UE. The UE is associated with PLMN A. In some examples, the UE is being served by PLMN A.

[0252] At S709, a UE user can request to determine the available MBS sessions within a service category. For example, a user can request available MBS sessions associated with the service category "TV Channels".

[0253] At S710, in order to determine the available MBS sessions with the service class, the UE queries the DNS server to determine the server's IP address. The server's IP address is provided to the UE from the DNS server.

[0254] At S711, the UE provides the server with information related to an MBS session available in a PLMN (e.g., PLMN A), where the request includes an indication of the service category. The UE uses the server's IP address to provide the request. Since the server is associated with multiple PLMNs, the request can identify the associated PLMN. In this example, since the UE is associated with PLMN A, the request identifies PLMN A. In some examples, the request includes the PLMN A ID. In other examples, the UE provides indications of multiple different service categories.

[0255] In this way, at S711, the UE queries the server to learn about MBS sessions for a specific service category.

[0256] At S712, the UE receives information from the server related to at least one MBS session, which is available in PLMN A. The at least one MBS session is associated with a service category. The information may include at least one of the following: MBS session ID, service information, session information, MBS session ID, PLMN A identifier, and Uniform Resource Locator (URL).

[0257] At S713, when the information received from the server includes a URL, the UE retrieves additional information about the MBS session from the URL.

[0258] At S714, when information from the server indicates the existence of multiple available MBS sessions associated with a service category, these multiple available MBS sessions are available at the PLMN, and the UE can select (or pick) an MBS session from these multiple available MBS sessions. In other examples, a single MBS session is available, so the UE does not select or pick an MBS session.

[0259] In some examples, the UE user will be offered an available MBS session to choose from (e.g., on the UE's display).

[0260] At S715, when the session is a multicast MBS session, the UE provides a join request to the SMF to join the MBS session. The join request identifies the selected multicast MBS session. For example, the multicast MBS session is identified using a session ID (e.g., MBS session ID 1).

[0261] At S716, the UE receives data associated with the MBS session. In some examples, the session can be a multicast MBS session. In other examples, the session can be a broadcast MBS session. When the session is a broadcast MBS session, the data used for the session will be received via broadcast within the MBS service area.

[0262] Figure 8 The fifth example process is shown, which includes signaling and operations performed by an entity.

[0263] At S801, AF provides a request for registration of an MBS session (e.g., a registration request). MBS sessions are associated with service categories.

[0264] The request is provided to NEF and includes at least one of the following: MBS session ID (also referred to as "ID associated with the MBS session"), service category, or service information. The request also includes at least one PLMN ID in which the service should be available. In this example, the MBS session will be available in PLMN A and / or PLMN B. The request may include indications of the PLMN A ID and PLMN B ID used for the MBS session. The request may be an Nnef_MBSSession_Register_Request message, or any other suitable message.

[0265] In this example, the MBS session is for MBS session ID1 and includes service category information and service information.

[0266] At S802, the NEF authorizes the AF to register an MBS session. The NEF can authorize the AF based on a received request. The NEF can authorize the AF based on information related to the MBS session in the received request. The NEF can include information related to permissions (or authorization) for the AF, or can have access to information related to permissions for the AF. For example, the information related to permissions for the AF can identify one or more PLMNs in which the AF is authorized to request an MBS session. The NEF can use the information related to permissions for the AF to determine whether to authorize the AF to create an MBS session. The NEF uses the service category indicated by the AF for the MBS session to register the MBS session-related information included in the request at the server.

[0267] In some examples, the server can be implemented in hardware. In other examples, the server can be implemented in software, or a combination of hardware and software. The server is capable of storing information related to MBS sessions.

[0268] At S803, the NEF queries the Domain Name System (DNS) server to determine information related to the server, such as the server's IP address. The NEF can be configured with information about DNS server discovery. The DNS server is configured to store identification information for network functions, network entities, servers, etc. The server (or storage device) is configured to store information related to the MBS session, which is available in the PLMN.

[0269] In this example, the server is associated with a first PLMN (“PLMN A”) and a second PLMN (“PLMN B”). The server may also be associated with one or more other PLMNs. In some examples, PLMN A and / or PLMN B may be VPLMNs. The server is able to store MBS session information for PLMN A and PLMN B.

[0270] At S804, NEF uses the server's IP address to send a request to the server that the created MBS session will be stored on the server. This request may be referred to as a "storage" request. It should be understood that other appropriate terms are used in other examples.

[0271] Because the server is associated with multiple PLMNs, the request identifies the MBS session that will be registered to be available to the associated PLMN(s). In this example, since the MBS session will be indicated as available for PLMN A and PLMN B, the request identifies PLMN A and PLMN B. The storage request includes at least one of the following: the identifier of the PLMN (e.g., PLMN A ID and PLMNB ID), the MBS session ID, the service category, or service information.

[0272] At S805, the server performs an authorization check on the NEF to store MBS session information for PLMN A and PLMN B. When the authorization check succeeds, the server stores the received information. In other examples, the server may have already pre-authorized the NEF for PLMN A and / or PLMN B. In the case of pre-authorization, the server will store the MBS session information for PLMN A and PLMN B upon receiving a storage request.

[0273] At S806, the UE has information that will be used for DNS server discovery. This information can be included in the UE's configuration. The configuration can be a pre-configured UE configuration. In other examples, the configuration is received by the UE. The UE is associated with PLMN A. In some examples, the UE is being served by PLMN A.

[0274] At S807, a UE user can request to determine the available MBS sessions within a service category. For example, a user can request available MBS sessions associated with the service category "TV Channels".

[0275] At S808, in order to determine the available MBS sessions with the service class, the UE queries the DNS server to determine the server's IP address. The server's IP address is provided to the UE from the DNS server.

[0276] At S809, the UE provides the server with information related to an MBS session available in a PLMN (e.g., PLMN A), where the request includes an indication of the service category. The UE uses the server's IP address to provide the request. Since the server is associated with multiple PLMNs, the request can identify the associated PLMN. In this example, since the UE is associated with PLMN A, the request identifies PLMN A. In some examples, the request includes the PLMN A ID. In other examples, the UE provides indications of several different service categories.

[0277] In this way, at S809, the UE queries the server to learn about MBS sessions for a specific service category.

[0278] At S810, the UE receives information from the server related to at least one MBS session, which is available in PLMN A. The at least one MBS session is associated with a service class. The information may include at least one of the following: MBS session ID, service information, session information, MBS session ID, PLMN A identifier, and Uniform Resource Locator (URL).

[0279] When the UE provides indications for multiple different service categories, the server provides information related to the MBS session associated with the multiple service categories.

[0280] At S811, when the information received from the server includes a URL, the UE retrieves additional information about the MBS session from the URL.

[0281] At S812, when information from the server indicates the existence of multiple available MBS sessions associated with a service category, these multiple available MBS sessions are available at the PLMN, and the UE can select (or pick) an MBS session from these multiple available MBS sessions. In other examples, a single MBS session is available, so the UE does not select or pick an MBS session.

[0282] In some examples, the UE user will be offered an available MBS session to choose from (e.g., on the UE's display).

[0283] At S813, when the session is a multicast MBS session, the UE provides a join request to the SMF to join the MBS session. The join request identifies the selected multicast MBS session. For example, the multicast MBS session is identified using a session ID (e.g., MBS session ID 1).

[0284] At S814, the UE receives data associated with the MBS session. In some examples, the session can be a multicast MBS session. In other examples, the session can be a broadcast MBS session. When the session is a broadcast MBS session, the data used for the session will be received via broadcast within the MBS service area.

[0285] In some examples, Figures 4 to 8 The aforementioned features apply to roaming between Independent Non-Public Networks (SNPNs). In this way, each of the Public Land Mobile Networks (PLMNs) discussed above can be replaced by an SNPN.

[0286] In each example, each PLMN provides a server through which the UE can discover MBS sessions within the service class that are available in the corresponding PLMN. Alternatively, a central server is provided for several PLMNs. In some examples, this can be operated by the GSMA.

[0287] The server can provide information about the MBS sessions available for each service class in the PLMN. The server can be queried by the UE or an NF representing the UE, using the service class as an input parameter. The server provides information about all registered MBS sessions within the service class. Information about the MBS sessions may include at least one of the following: an MBS session identifier, additional information about the MBS session (e.g., as included in a service announcement in TS 23.247), a human-readable description of the MBS session, or the URL of the server (e.g., AF) where additional information about the MBS session is available.

[0288] In an example where the server serves multiple PLMNs (e.g., ... Figure 8 As shown, the PLMNID of (multiple) PLMNs is also part of the information about the MBS session available in that PLMN(s). The PLMN ID can be used with the service category to query a server, for example, the PLMN by which the UE is currently served. The server can perform authentication checks on the registration requests it receives. For example, by allowing registration of the MBS session from a given PLMN, or by allowing the PLMN to register services in a configured set of PLMNs (e.g., PLMNs with operator groups).

[0289] In each example, the UE (or the NF representing the UE) may be provided with information to query whether the server requires a PLMN ID. In other examples, the query includes at least one PLMN ID.

[0290] When the information about the MBS session provided to the UE includes the URL of the server, additional information about the session is available on that server, and the UE retrieves the additional information from the server.

[0291] In the examples, the AF providing the MBS session can register the MBS service with the server via NEF or MBSF (e.g., in the case of an external / untrusted AF). Alternatively, the AF registers the MBS session directly with the server (e.g., in the case of a trusted AF). During the registration of the MBS session, the AF provides the MBS service category for the MBS session, as well as information about the MBS session (e.g., by including the MBS service category for the MBS session, as well as information about the MBS session in the request, which is for registering the MBS session provided by the AF to the server).

[0292] In each example, AF registers multiple MBS sessions simultaneously, where all MBS sessions belong to the same service category, or each MBS session belongs to a different service category.

[0293] In various examples, the NEF verifies the AF, for instance, by authorizing the registration of one (or more) MBS sessions based on a business agreement. After authorization, the AF registers information about the MBS session with the service. In some examples, the AF is operated by a third party rather than the PLMN operator. The permissions associated with the AF (operated by a third party) can be agreed upon between the third party and the PLMN operator via a business agreement / contract / (multiple) rules, etc.

[0294] In each example, the AF provides service category information for a specific MBS session or service information for a specific service category as part of the service operation for creating the MBS session. The registration of the service category information for the specific MBS session or service information for a specific service category at the server can then be performed by the NEF, MBSF, or MB-SMF.

[0295] In each example, AF can update and / or unregister service category information for MBS sessions or service information for specific service categories used by the server.

[0296] In each example, when registration is performed as part of the service operation to create an MBS session (e.g., Figure 6 Updates and deregistration can be performed as part of the service operations for updating and deleting MBS sessions. In this way, interactions with the server can also be handled by NEF, MBSF, or MB-SMF.

[0297] In each example, as part of the authorization check (of the AF), the NEF, MBSF, or MB-SMF may allow the AF to register MBS sessions in the PLMN where the NEF or MB-SMF resides. Alternatively or additionally, this can be achieved by allowing the AF to register MBS sessions in a configured set of PLMNs (e.g., a PLMN with operator groups).

[0298] In each example, when the AF releases the MBS session, the AF requests the cancellation of the MBS session.

[0299] In each example, when the AF's registration request is combined with a request to create an MBS session, and when the AF releases the MBS session, the NEF and MBSF, or MB-SMF, that handle the request to release the MBS session perform the deregistration of the MBS session at the server.

[0300] In the examples, when a server is serving multiple PLMNs (e.g., a central server), the central server performs authentication checks on requests to register MBS sessions received by the central server, for example, by allowing the registration of MBS sessions from a given PLMN of that PLMN, or by allowing the PLMN to register MBS sessions in a configured set of PLMNs (e.g., PLMNs with operator groups).

[0301] In the example, AF registers MBS sessions available in several PLMNs (e.g., such as...). Figure 8 As shown in the diagram), and in the registration request for registering the MBS session, the PLMN ID of those PLMNs is indicated. The NEF, MBSF, MB-SMF, and / or server processing the registration request determine whether the AF (or the NF on behalf of the AF) is authorized to register the MBS session for the indicated PLMN.

[0302] In each example, server (e.g., database) functionality is integrated into the MB-SMF (e.g., as shown in the example). Figure 5 (as shown in the diagram), for example in a PLMN where only a single MB-SMF is deployed.

[0303] In the examples, in a deployment with multiple MB-SMFs, one MB-SMF or a set of MB-SMFs can be selected to act as the server / database for the MBS service category. The selected MB-SMF(s) can then be registered with the NRF to act as the server / database for the MBS service category. If other NFs (including other MB-SMFs) need to register an MBS session, they discover the MB-SMF(s) used as the database via the NRF.

[0304] In various examples, servers are integrated into MBSFs, such as in a PLMN where a single MBSF is deployed. In other examples, in a 5GC comprising multiple MBSFs, one MBSF or a set of MBSFs can be selected to act as a server database for the MBS service category. The selected MBSF(s) can then register with the NRF as a server / database for the MBS service category. If other NFs (including other MBSFs) need to register an MBS session, they discover the MBSF(s) acting as the server / database via the NRF. The MBSF can then store information about the MBS session and service category during the creation of the MBS session.

[0305] In each example, the UE sends a query to the SMF in the Protocol Data Unit (PDU) session-related signaling regarding the available MBS sessions for each service class. The SMF then queries the server and forwards the response (from the server) to the UE.

[0306] In each example, the UE sends a query to the AMF regarding the available MBS sessions for each service category. This query can be included in the registration request. The AMF then queries the server and forwards the response (from the server) to the UE in the registration acceptance message.

[0307] In each example, another NF (e.g., SMF or AMF) performs a query on behalf of the UE (e.g., such as...). Figure 5 As shown in the example, the server can be registered at the NRF and detected by another NF via an NRF query. In other examples, when another NF performs a query on behalf of the UE, the UE can be configured with one or more URSP rules, as well as the DNN and network slice used to access that other NF.

[0308] In each example, the UE is configured with information related to the discovery server. For example, the information may include the server's name and / or IP address. The information may include information for different PLMNs. The UE may be pre-configured with this information; for example, the information may be pre-configured in the SIM card. Alternatively, the UE may receive information from the network.

[0309] In each example, the server can have a similar name across all PLMNs, such as "mbsserviceinfo". <mnc> . <mcc>",in <mnc>and <mcc>These are the PLMN's mobile network code and mobile country code, respectively. MNC and MCC can be resolved to IP addresses via DNS.

[0310] In each example, one or more URSP rules can be provided to the UE, which include the identifier of the DNN and the network slice, which will be used to access the server in the PLMN.

[0311] One or more of the examples above have the advantage that the UE can identify MBS sessions within a service category that are available in the PLMN. The UE can query the server based on the service category. A service category can include different MBS sessions providing similar applications; for example, different TV channels may be in the same service category provided by different MBS sessions within the same service category. The example use case is for a roaming UE. A roaming UE may be interested in MBS sessions within a service category available in the VPLMN, and therefore the UE can discover sessions within the service category available in the VPLMN.

[0312] Figure 9 Example method flows performed by a device are illustrated. In each example, one of the following is true: the device is used for a user equipment, the device is included in a user equipment, or the device is a user equipment. The device may include methods for performing... Figure 9 One or more components having the following features. A non-limiting example of a component for performing the following features is: at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the device to perform... Figure 9 The following characteristics.

[0313] In S901, the method includes: providing a request for information relating to a multicast / broadcast service MBS session available in a public terrestrial mobile network, the request including an indication of the service category.

[0314] In S903, the method includes: receiving information related to an MBS session, which is available in a public land mobile network and is associated with a service class.

[0315] In S905, the method includes: receiving data associated with an MBS session based on information.

[0316] Figure 10 An example method flow executed by a device is illustrated. In the example, the device is used for a storage device, the device is included in a storage device, or the device is a storage device. For example, the storage device may be a server. In some examples, the storage device may be a standalone entity. In other examples, the storage device may be integrated with network functions. The device may include components for performing... Figure 10 One or more components having the following features. A non-limiting example of a component for performing the following features is: at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the device to perform... Figure 10 The following characteristics.

[0317] In S1001, the method includes: receiving information related to a multicast / broadcast service MBS session, the information including a service category associated with the MBS session. In S1003, the method includes: storing information related to the MBS session for the MBS session. In S1005, the method includes: receiving a request for information related to the MBS session, which is available in a public land mobile network, the request including an indication of the service category. In S1007, the method includes: providing the stored information related to the MBS session, which is available in a public land mobile network and associated with the service category.

[0318] Figure 11 An example method flow executed by a device is illustrated. In the example, one of the following is true: the device is used for a network function; the device is included in a network function; the network function is included in the device; the device provides a network function; or the device is a network function. For example, the network function could be MB-SMF or NEF. In this way, in some examples, the network function can perform... Figure 11 The method and process.

[0319] In some embodiments, the apparatus may include means for performing Figure 11 One or more components having the following features. A non-limiting example of a component for performing the following features is: at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the device to perform... Figure 11 The following characteristics.

[0320] In S1101, the method includes: receiving a request from an application function for creating a multicast / broadcast service MBS session, the request including information related to the MBS session, including the service category associated with the MBS session.

[0321] In S1103, the method includes: creating an MBS session based on information related to the MBS session.

[0322] In S1105, the method includes: authorizing application functions to use MBS sessions.

[0323] In S1107, the method includes: providing information related to the MBS session to a storage device, such that the information related to the MBS session is stored at the storage device.

[0324] Figure 12 A schematic representation of non-volatile storage media 1200a (e.g., Blu-ray disc, computer optical disc (CD), or digital versatile optical disc (DVD)) and 1200b (e.g., flash memory, solid-state memory, Universal Serial Bus (USB) memory stick) is shown, storing instructions and / or parameters 1202, which, when executed by the processor, allow the processor to perform... Figure 9 , Figure 10 or Figure 11 One or more steps in the method.

[0325] It should be noted that although exemplary embodiments have been described above, several variations and modifications can be made to the disclosed solutions without departing from the scope of the invention. Therefore, embodiments can be varied within the scope of the appended claims. Generally, some embodiments can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented in firmware or software, which can be executed by a controller, microprocessor, or other computing device, although the embodiments are not limited thereto. While various embodiments may be shown and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0326] Examples can be implemented by computer software stored in memory and executed by at least one data processor of the relevant entity, or by hardware, or by a combination of software and hardware. Furthermore, it should be noted in this regard that any process can represent program steps, or interconnected logic circuits, blocks, and functions, or combinations of program steps and logic circuits, blocks, and functions. Software can be stored on physical media such as memory blocks implemented within memory chips or processors, magnetic media (such as hard disks or floppy disks), and optical media (such as DVDs and their data variants, CDs).

[0327] As used in this article, the term "non-transient" refers to the limitations of the medium itself (i.e., tangible, not signal-based), rather than limitations on the persistence of data storage (e.g., RAM and ROM).

[0328] As used herein, "at least one of the following: " and "at least one of " and similar wording, where the list of two or more elements is connected by "and" or "or", means at least any one element, or at least any two or more elements, or at least all elements.

[0329] The memory can be of any type suitable for the local technological environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor can be of any type suitable for the local technological environment and, by way of non-limiting example, can include one or more of the following: general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), gate-level circuits, and processors based on multi-core processor architectures.

[0330] As used herein, "component for performing" or "component configured to perform" (or similar) can be any component applicable to the performance feature. A "component" can be configured to perform one or more of the previously described functional and / or method steps. For example, a "component" can include one or more of the following: at least one processor, at least one memory, a transceiver circuit system, an antenna circuit system, etc. It should be understood that these are provided as non-limiting examples.

[0331] Alternatively or additionally, some examples can be implemented using a circuit system. This circuit system can be configured to perform one or more of the previously described functional and / or method steps. This circuit system can be provided in a base station and / or communication equipment.

[0332] As used in this application, the term "circuit system" may refer to one or more of the following: (a) a hardware circuit implementation only (such as an implementation only in analog and / or digital circuit systems); and (b) a combination of hardware circuits and software, such as (if applicable): (i) a combination of (multiple) analog and / or digital hardware circuits with software / firmware, and (ii) any portion of (multiple) hardware processors (including (multiple) digital signal processors), software, and (multiple) memories having software, which work together to enable a device (such as a mobile phone or a server) to perform various functions; and (c) (multiple) hardware circuits and / or (multiple) processors (such as (multiple) microprocessors or portions thereof) that require software (e.g., firmware) to operate, but may be absent when the software is not required to operate.

[0333] This definition of "circuit system" applies to all uses of the term in this application, including in any claim. As another example, as used in this application, the term "circuit system" also covers only the implementation of hardware circuitry or a processor (or multiple processors), or portions of hardware circuitry or a processor and its accompanying software and / or firmware. For example, if applicable to a particular claim element, the term "circuit system" also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

[0334] The foregoing description, through exemplary and non-limiting examples, has provided a comprehensive and detailed description of some embodiments. However, various modifications and adaptations will become apparent to those skilled in the art when read in conjunction with the accompanying drawings and appended claims, given the foregoing description. Nevertheless, all such and similar modifications will still fall within the scope defined in the appended claims.< / mcc> < / mnc> < / mcc> < / mnc>

Claims

1. A user equipment, comprising: A component providing a request for information related to a multicast / broadcast service MBS session available in a public terrestrial mobile network, the request including an indication of the service category; A component that receives information related to an MBS session, the MBS session being available in the public terrestrial mobile network and associated with the service class; and A component that receives data associated with the MBS session based on the information.

2. The user equipment of claim 1, wherein the request is provided to a storage device associated with the public land mobile network, or is provided to at least one of the following: the access and mobility management function of the public land mobile network, or the session management function of the public land mobile network.

3. The user equipment according to claim 1 or claim 2, wherein the information related to an MBS session available in the public land mobile network includes at least one of the following: an identifier for the MBS session, additional information related to the MBS service announcement, a text description of the MBS session, or a Uniform Resource Identifier of an additional storage device in which additional information about the MBS session is stored and available.

4. The user equipment according to any one of claims 1 to 3, further comprising: A component for retrieving additional information about the MBS session from the additional storage device based on the Uniform Resource Identifier when the information associated with the MBS session includes the Uniform Resource Identifier.

5. The user equipment according to any one of claims 1 to 4, further comprising: A component for receiving information related to multiple MBS sessions, which are available in the public land mobile network, and each of the multiple MBS sessions is associated with the service class; A component for selecting an MBS session from the plurality of MBS sessions; as well as A component for receiving data associated with the selected MBS session.

6. The user equipment according to any one of claims 1 to 5, wherein the MBS session is a multicast MBS session, and wherein the component for receiving data associated with the MBS session based on the information comprises: A component for requesting to join the multicast MBS session based on the received information; as well as Components for receiving the data associated with the multicast MBS session.

7. The user equipment according to any one of claims 1 to 6, wherein the request includes an identifier of a public land mobile network, such that an MBS session is requested, the MBS session being available at the public land mobile network, associated with the service class, and associated with the identifier of the public land mobile network.

8. The user equipment according to any one of claims 1 to 7, wherein the request is one of the following: a request, a query request, or a registration request included in the protocol data unit (PDU) session-related signaling to the session management function.

9. The user equipment according to any one of claims 1 to 8, further comprising: A component for receiving at least one user equipment routing policy rule, the at least one user equipment routing policy rule including: a data network name, and an identifier of a network slice to be used for accessing a storage device in the public terrestrial mobile network, wherein the component for providing the request includes: A component for providing the request to the storage device using a PDU session containing the received identifier of the data network name and network slice received by the application.

10. The user equipment according to any one of claims 1 to 9, wherein the public land mobile network includes the visited public land mobile network.

11. A storage device for at least one public terrestrial mobile network, the storage device comprising: A component for receiving information related to a multicast / broadcast service MBS session, the information related to the MBS session including the service category associated with the MBS session; A component for storing information related to the MBS session; A component for receiving a request for information related to an MBS session available in a public terrestrial mobile network, the request including an indication of a service class; A component for providing stored information related to an MBS session, which is available in the public terrestrial mobile network and associated with the service class.

12. The storage device of claim 12, wherein the stored information provided includes: Information related to multiple MBS sessions, which are available in the public land mobile network, and each of the multiple MBS sessions is associated with the service class.

13. The storage device of claim 12 or claim 13, wherein the information related to the MBS session is received directly from the application function or via a network function.

14. The storage device according to any one of claims 12 to 14, further comprising: A component for storing information about multiple MBS sessions for the service category; as well as A component used to provide information about all stored MBS sessions for the service category.

15. The storage device according to any one of claims 12 to 15, wherein the received information related to the MBS session further comprises: The request further includes an identifier of the public land mobile network associated with the MBS session, wherein the request also includes an indication of the public land mobile network, and wherein the stored information provided in connection with the MBS session is associated with the public land mobile network indicated in the request, in which the MBS session is available.

16. An apparatus comprising: A component for receiving a request from an application function for creating a multicast / broadcast service (MBS) session, the request including information related to the MBS session, the information including the service category associated with the MBS session; A component for creating the MBS session based on the information associated with the MBS session; Components used to authorize the application functions to use the MBS session; as well as Components for providing the information related to the MBS session to the storage device, such that the information related to the MBS session is stored at the storage device.

17. The apparatus of claim 18, further comprising: A component for receiving deletion requests, which are related to the MBS session; as well as This is used to provide the storage device with information related to the deletion of the MBS session, so that the information related to the MBS session stored at the storage device is removed from the storage component.

18. A method for a user equipment, the method comprising: A request is made for information relating to a multicast / broadcast service MBS session that is available in a public terrestrial mobile network, the request including an indication of the service class; Receive information related to an MBS session, which is available in the public terrestrial mobile network and associated with the service class; and Based on the information, data associated with the MBS session is received.

19. The method of claim 20, wherein the request is provided to a storage device associated with the public land mobile network, or is provided to at least one of the following: access and mobility management functions of the public land mobile network, or session management functions of the public land mobile network.

20. The method of claim 20 or claim 21, wherein the information relating to an MBS session available in the public land mobile network includes at least one of the following: an identifier for the MBS session, additional information relating to an MBS service announcement, a textual description of the MBS session, or a Uniform Resource Identifier of an additional storage device in which additional information about the MBS session is stored and is available.

21. The method according to any one of claims 20 to 22, further comprising: When the information associated with the MBS session includes a Uniform Resource Identifier, additional information about the MBS session is retrieved from the additional storage device based on the Uniform Resource Identifier.

22. The method according to any one of claims 20 to 23, wherein the receiving further comprises: Receive information related to multiple MBS sessions, which are available in the public land mobile network, and each of the multiple MBS sessions is associated with the service class; Select an MBS session from the plurality of MBS sessions; as well as Receive data associated with the selected MBS session.

23. The method of any one of claims 20 to 24, wherein the MBS session is a multicast MBS session, and wherein receiving data associated with the MBS session based on the information comprises: Based on the received information, a request is made to join the multicast MBS session; as well as Receive the data associated with the multicast MBS session.

24. The method of any one of claims 20 to 25, wherein the request includes an identifier of a public land mobile network, such that an MBS session is requested, the MBS session being available at the public land mobile network, associated with the service class, and associated with the identifier of the public land mobile network.

25. The method according to any one of claims 20 to 26, wherein the request is one of the following: a request, a query request, or a registration request included in the session-related signaling of the Protocol Data Unit (PDU) for the session management function.

26. The method according to any one of claims 20 to 27, further comprising: The system receives at least one user equipment routing policy rule, the at least one user equipment routing policy rule including: a data network name, and an identifier of a network slice to be used for accessing a storage device in the public terrestrial mobile network, wherein the component for providing the request includes: The request is provided to the storage device using the PDU session containing the data network name and the identifier of the network slice received by the application.

27. The method according to any one of claims 20 to 28, wherein the public land mobile network includes the visited public land mobile network.

28. A method for a storage device in at least one public terrestrial mobile network, comprising: Receive information related to a multicast / broadcast service MBS session, the information related to the MBS session including the service category associated with the MBS session; For the MBS session, store the information related to the MBS session; Receive a request for information related to an MBS session that is available in a public terrestrial mobile network, the request including an indication of the service class; Provides stored information related to an MBS session that is available in the public land mobile network and that is associated with the service class.

29. The method of claim 30, wherein the stored information provided comprises: Information related to multiple MBS sessions, which are available in the public land mobile network, and each of the multiple MBS sessions is associated with the service class.

30. The method of claim 30 or claim 31, wherein the information related to the MBS session is received directly from the application function or via a network function.

31. The method according to any one of claims 30 to 32, further comprising: Store information about multiple MBS sessions for the service category; as well as Provides information about all stored MBS sessions for the said service category.

32. The method according to any one of claims 30 to 33, wherein the received information related to the MBS session further comprises: The request further includes an identifier of the public land mobile network associated with the MBS session, wherein the request also includes an indication of the public land mobile network, and wherein the stored information provided in connection with the MBS session is associated with the public land mobile network indicated in the request, in which the MBS session is available.

33. A method comprising: The application function receives a request for creating a multicast / broadcast service (MBS) session, the request including information related to the MBS session, the information including the service category associated with the MBS session; The MBS session is created based on the information associated with the MBS session; Authorize the application functionality to use the MBS session; as well as The information related to the MBS session is provided to the storage device, such that the information related to the MBS session is stored at the storage device.

34. The method of claim 35, further comprising: Receive a deletion request, which is related to the MBS session; as well as Information related to the deletion of the MBS session is provided to the storage device, such that the information related to the MBS session stored on the storage device is removed from storage.

35. A computer program comprising instructions, wherein when executed by a user equipment, the user equipment is caused to perform the method according to any one of claims 20 to 29.

36. A computer-readable medium instruction comprising instructions that, when executed by a user equipment, cause the user equipment to perform the method according to any one of claims 20 to 29.

37. A computer program comprising instructions, wherein when executed by a storage device, the storage device is caused to perform the method according to any one of claims 30 to 34.

38. A computer-readable medium comprising instructions that, when executed by a storage device, cause the storage device to perform the method according to any one of claims 30 to 34.

39. A computer program comprising instructions, wherein when executed by a means, the means is caused to perform the method according to any one of claims 35 to 36.

40. A computer-readable medium comprising instructions that, when executed by a device, cause the device to perform the method according to any one of claims 35 to 36.

Images