GB2624928A

GB2624928A - Message priority indication for subsequent communication

Info

Publication number: GB2624928A
Application number: GB2218060.8A
Authority: GB
Inventors: Little Jonathan; Wiehe Ulrich
Original assignee: Nokia Solutions and Networks Oy
Current assignee: Nokia Solutions and Networks Oy
Priority date: 2022-12-01
Filing date: 2022-12-01
Publication date: 2024-06-05
Also published as: GB202218060D0

Abstract

Methods are disclosed for (e.g. enabling/realizing) message priority indication for subsequent communication in a mobile communication system. A method of an initiator entity (Consumer – e.g. an NF service consumer) of the system comprises: specifying a message priority as a preferred/required priority for service-related messages relating to a service from a responder entity (Producer) of the system; and issuing a request message 1 relating to the service, the message including priority information, indicative of the specified priority, serving to indicate to the responder to apply the specified priority for service-related messages. A method at the responder entity comprises obtaining the priority information and utilizing it to apply the message priority for service-related messages relating to the service, wherein the messages may then be sent 2 to the initiator entity. The information may be included in a header or payload of the request message, and may comprise a priority value, a priority policy for deriving a priority value, or a content value to be used for creating content of parameters or information elements for applying the specified priority. The request message may be a subscription request for subscribing to notifications with respect to the service, and the service-related messages may be subscribed notifications.

Description

Intellectual Property Office Application No G132218060.8 RTM Date 1 May 2023 The following terms are registered trade marks and should be read as such wherever they occur in this document: 3 GP P Intellectual Property Office is an operating name of the Patent Office www.gov.uk/ipo Title Message Priority Indication for Subsequent Communication

Technical Field

Various example embodiments described herein relate to message priority indication for subsequent communication. More specifically, measures/mechanisms (e.g., including methods, apparatuses (e.g., devices, entities, elements, instances and/or functions) and computer program products) are described for enabling/realizing message priority indication for subsequent communication in a mobile communication system.

Background

List of acronyms and abbreviations: 3GPP 3rd Generation Partnership Project 5G 5th Generation AMF Access and Mobility Management Function API Application Programming Interface DSCP Differentiated Services Code Point HTTP Hypertext Transfer Protocol NF Network Function NFV Network Functions Virtualisation NFVI Network Functions Virtualisation Infrastructure NR New Radio NRF Network Function Repository SBI Service-Based Interface SCP Service Communication Proxy SDN Software-Defined Networking UDM Unified Data Manager UDR Unified Data Repository URI Universal Resource Indicator -1 -

Summary

Various example embodiments address, at least in part, issues, problems and/or drawbacks described herein as well as those recognized by a person skilled in the art.

Various example embodiments are set out in the claims.

According to an example embodiment, there is provided a method of (or, stated differently, operable or for use in/by) an initiator entity of a mobile communication system, the method comprising: specifying a message priority as a preferred or required priority for service-related messages relating to a service from a responder entity of the mobile communication system, and issuing a request message relating to the service, the request message including priority information indicative of the specified message priority, said priority information serving to indicate to the responder entity to apply the specified message priority for service-related messages relating to the service.

According to an example embodiment, there is provided an apparatus of (or, stated differently, operable or for use in/by) an initiator entity of a mobile communication system, the apparatus comprising: means for specifying a message priority as a preferred or required priority for service-related messages relating to a service from a responder entity of the mobile communication system, and means for issuing a request message relating to the service, the request message including priority information indicative of the specified message priority, said priority information serving to indicate to the responder entity to apply the specified message priority for service-related messages relating to the service.

According to an example embodiment, there is provided an apparatus of (or, stated differently, operable or for use in/by) an initiator entity of a mobile communication system, the apparatus comprising at least one processor, and at least one memory storing instructions that, when -2 -executed by the at least one processor, cause the apparatus at least to perform: specifying a message priority as a preferred or required priority for service-related messages relating to a service from a responder entity of the mobile communication system, and issuing a request message relating to the service, the request message including priority information indicative of the specified message priority, said priority information serving to indicate to the responder entity to apply the specified message priority for service-related messages relating to the service.

According to an example embodiment, there is provided an apparatus of (or, stated differently, operable or for use in/by) an initiator entity of a mobile communication system, the apparatus comprising: circuitry configured to specify a message priority as a preferred or required priority for service-related messages relating to a service from a responder entity of the mobile communication system, and circuitry configured to issue a request message relating to the service, the request message including priority information indicative of the specified message priority, said priority information serving to indicate to the responder entity to apply the specified message priority for service-related messages relating to the service.

According to various developments/modifications, any one of the aforementioned method-related and/or apparatus-related example embodiments may include one or more of the following features: the priority information is included in a header of the request 25 message or a payload of the request message, when the priority information is included in a header, the header is a dedicated header for carrying the priority information, when the priority information is included in a payload, the priority information is included in a dedicated section or information element for carrying the priority information in the payload, the priority information comprises or indicates at least one of the following: a priority value to be used by the responder entity for applying the specified message priority, a priority policy to be employed by the responder entity for deriving a priority value for applying the specified -3 -message priority, or a content value to be used by the responder entity for creating content of one or more parameters or information elements for applying the specified message priority, the priority information comprises at least one of the following: transmission-specific priority information for application of the specified message priority in transmission (e.g., prior to transmission, during transmission, and/or after transmission) of the service-related messages relating to the service by the responder entity, generation-specific priority information for application of the specified message priority in generation (e.g., prior to generation, during generation, and/or after generation) of the service-related messages relating to the service by the responder entity, or content-specific priority information for application of the specified message priority in creation (e.g., prior to creation, during creation, and/or after creation) of content of the service-related messages relating to the service by the responder entity, the transmission-specific priority information is configured to affect a sequence of message transmission and/or a guidance for message handling in transfer from the responder entity to the initiator entity, such as, e.g., in a dedicated header for message prioritization, the generation-specific priority information is configured to affect a sequence of message generation and/or a selection of messages to be generated, such as, e.g., in a high load or overload condition of one or more message generation resources, the content-specific priority information is configured to affect the 25 content of one or more parameters or information elements of messages, such as, e.g., a differentiated services code point value, the request message relating to the service is or comprises a subscription request for subscribing to notifications with respect to the service, and/or the service-related messages are or comprise subscribed notifications with respect to the service, the method, functionality, operability or configuration comprises or enables: sending the request message to the responder entity, and receiving the service-related messages from the responder entity, -4 -the request message relating to the service is or comprises a registration request for registering service-related information of the initiator entity at the responder entity, the priority information is registered as part of the service-related information of the initiator entity, the service-related information of the initiator entity represents an implicit notification subscription with respect to the service, and/or the service-related messages are or comprise notifications with respect to the service based on the implicit notification subscription, the method, functionality, operability or configuration comprises or enables: sending the request message to the responder entity, and receiving the service-related messages from the responder entity, the request message relating to the service is or comprises a registration request for registering profile information of the initiator entity at a registry or repository entity, the priority information is registered as part of the profile information of the initiator entity, the profile information of the initiator entity relates to a default notification subscription with respect to the service, and/or the service-related messages are or comprise notifications with respect to the service based on the default notification subscription, the method, functionality, operability or configuration comprises or enables: sending the request message to the registry or repository entity, and receiving the service-related messages from the responder entity, the initiator entity and the responder entity are involved in or based on a service-based architecture of the mobile communication system, the initiator entity is or comprises a service consumer or any entity configured to consume or use at least the service, the responder entity is or comprises a service producer or any entity configured to produce, expose and/or offer at least the service.

According to an example embodiment, there is provided a method of (or, stated differently, operable or for use in/by) a responder entity of a mobile -5 -communication system, the method comprising: obtaining priority information indicative of a message priority of an initiator entity of the mobile communication system, said message priority being specified by the initiator entity as a preferred or required priority for service-related messages relating to a service from the responder entity, and utilizing the priority information to apply the message priority of the initiator entity for service-related messages relating to the service.

According to an example embodiment, there is provided an apparatus of (or, stated differently, operable or for use in/by) a responder entity of a mobile communication system, the apparatus comprising: means for obtaining priority information indicative of a message priority of an initiator entity of the mobile communication system, said message priority being specified by the initiator entity as a preferred or required priority for service-related messages relating to a service from the responder entity, and means for utilizing the priority information to apply the message priority of the initiator entity for service-related messages relating to the service.

According to an example embodiment, there is provided an apparatus of (or, stated differently, operable or for use in/by) a responder entity of a mobile communication system, the apparatus comprising at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform: obtaining priority information indicative of a message priority of an initiator entity of the mobile communication system, said message priority being specified by the initiator entity as a preferred or required priority for service-related messages relating to a service from the responder entity, and utilizing the priority information to apply the message priority of the initiator entity for service-related messages relating to the service.

According to an example embodiment, there is provided an apparatus of (or, stated differently, operable or for use in/by) a responder entity of a mobile communication system, the apparatus comprising: circuitry -6 -configured to obtain priority information indicative of a message priority of an initiator entity of the mobile communication system, said message priority being specified by the initiator entity as a preferred or required priority for service-related messages relating to a service from the responder entity, and circuitry configured to utilize the priority information to apply the message priority of the initiator entity for service-related messages relating to the service.

According to various developments/modifications, any one of the 10 aforementioned method-related and/or apparatus-related example embodiments may include one or more of the following features: the priority information comprises or indicates a priority value, and utilizing the priority information comprises using the priority value for applying the message priority of the initiator entity, the priority information comprises or indicates a priority policy, and utilizing the priority information comprises employing the priority policy for deriving a priority value for applying the message priority of the initiator entity, the priority information comprises or indicates a content value, and utilizing the priority information comprises creating content of one or more parameters or information elements for applying the message priority of the initiator entity, the method, functionality, operability or configuration (of/regarding utilizing the priority information) comprises or enables: assigning the priority value to the service-related messages relating to the service, and/or including the content in the service-related messages relating to the service, the priority information comprises transmission-specific priority information, and utilizing the priority information comprises applying the message priority of the initiator entity in transmission (e.g., prior to transmission, during transmission, and/or after transmission) of the service-related messages relating to the service, -7 - the priority information comprises generation-specific priority information, and utilizing the priority information comprises applying the message priority of the initiator entity in generation (e.g., prior to generation, during generation, and/or after generation) of the service-related messages relating to the service, the priority information comprises content-specific priority information, and utilizing the priority information comprises applying the message priority of the initiator entity in creation (e.g., prior to creation, during creation, and/or after creation) of content of the service-related messages relating to the service, when applying the message priority of the initiator entity in transmission (e.g., prior to transmission, during transmission, and/or after transmission) of the service-related messages relating to the service, a sequence of message transmission and/or a guidance for message handling in transfer from the responder entity to the initiator entity, such as, e.g., in a dedicated header for message prioritization, is established based on the transmission-specific priority information, when applying the message priority of the initiator entity in generation (e.g., prior to generation, during generation, and/or after generation) of the service-related messages relating to the service, a sequence of message generation and/or a selection of messages to be generated, such as, e.g., in a high load or overload condition of one or more message generation resources, is established based on the generation-specific priority information, when applying the message priority of the initiator entity in creation (e.g., prior to creation, during creation, and/or after creation) of content of the service-related messages relating to the service, the content of one or more parameters or information elements of messages, such as, e.g., a differentiated services code point value, is established based on the content-specific priority information, the method, functionality, operability or configuration comprises or enables: determining applicability of the message priority of the initiator entity for service-related messages relating to the service, -8 -the priority information is utilized to apply the message priority of the initiator entity for service-related messages relating to the service when the applicability is affirmed, and a local policy or configuration is utilized to apply a message priority other than the message priority of the initiator entity or apply no message priority for service-related messages relating to

the service when the applicability is denied,

the method, functionality, operability or configuration comprises or enables: storing the priority information, the method, functionality, operability or configuration comprises or enables: receiving a request message relating to the service from the initiator entity, the request message including the priority information, wherein the priority information is obtained from the request message, and sending the service-related messages to the initiator entity, the priority information is included in a header of the request 15 message or a payload of the request message, when the priority information is included in a header, the header is a dedicated header for carrying the priority information, when the priority information is included in a payload, the priority information is included in a dedicated section or information element for carrying the priority information in the payload, the request message relating to the service is or comprises a subscription request for subscribing to notifications with respect to the service, and/or the service-related messages are or comprise subscribed notifications with respect to the service, the request message relating to the service is or comprises a registration request for registering service-related information of the initiator entity at the responder entity, the priority information is registered as part of the service-related information of the initiator entity, the service-related information of the initiator entity represents an implicit notification subscription with respect to the service, and/or the service-related messages are or comprise notifications with respect to the service based on the implicit notification subscription, -9 - the method, functionality, operability or configuration comprises or enables: acquiring profile information of the initiator entity from a registry or repository entity, wherein the priority information is part of and obtained from the profile information of the initiator entity, and sending the service-related messages to the initiator entity, the profile information of the initiator entity relates to a default notification subscription with respect to the service, and/or the service-related messages are or comprise notifications with respect to the service based on the default notification subscription, the initiator entity and the responder entity are involved in or based on a service-based architecture of the mobile communication system, the initiator entity is or comprises a service consumer or any entity configured to consume or use at least the service, the responder entity is or comprises a service producer or any entity configured to produce, expose and/or offer at least the service.

According to an example embodiment, there is provided a computer program product comprising (computer-executable) computer program code which, when the program code is executed (or run) on a computer or the program is run on a computer (e.g., a computer of an apparatus according to any one of the aforementioned apparatus-related example embodiments), is configured to cause the computer to carry out the method according to the aforementioned method-related example embodiments.

The computer program product may comprise or may be embodied as a (tangible/non-transitory) computer-readable (storage) medium or the like, on which the computer-executable computer program code is stored, and/or the program is directly loadable into an internal memory of the computer or a processor thereof.

The term "non-transitory," as used herein, is a limitation of the medium itself (e.g., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).

-10 -Further developments and/or modifications of the aforementioned example embodiments are set out in the following.

By way of example embodiments, a technique for (e.g., enabling/realizing) 5 message priority indication for subsequent communication (e.g., after/based on/in response to initial communication) in a mobile communication system can be enabled/realized.

Brief Description of the Drawings

In the following, various example embodiments will be described with reference to the accompanying drawings.

FIG. 1 shows a flowchart illustrating a method or process according to at 15 least one example embodiment, FIG. 2 shows a flowchart illustrating a method or process according to at least one example embodiment, FIG. 3 shows a sequence diagram illustrating a procedure according to at least one example embodiment, FIG. 4 shows a sequence diagram illustrating a procedure according to at least one example embodiment, FIG. 5 shows a sequence diagram illustrating a procedure according to at least one example embodiment, FIG. 6 shows a sequence diagram illustrating a procedure according to at 30 least one example embodiment, FIG. 7 shows a sequence diagram illustrating a procedure according to at least one example embodiment, FIG. 8 shows a sequence diagram illustrating a procedure according to at least one example embodiment, FIG. 9 shows a schematic block diagram illustrating a structure of 5 apparatuses according to at least one example embodiment, and FIG. 10 shows a schematic block diagram illustrating a structure of apparatuses according to at least one example embodiment.

Detailed Description

Various example embodiments are herein described with reference to particular non-limiting and illustrative examples. A person skilled in the art will appreciate that these various example embodiments are by no means limited to these non-limiting and illustrative examples, and may be more broadly applied.

It is to be noted that the detailed description, at times, refers to one or more specifications being used as non-limiting and illustrative examples for certain network configurations and system deployments. More specifically, the detailed description makes reference to 3GPP standards, being used as non-limiting and illustrative examples. As such, the example embodiments provided herein specifically can employ terminology which is directly related thereto. Such terminology is only used in the context of the non-limiting and illustrative examples, and is not intended to limit the various example embodiments in any way. Rather, any other system configuration or deployment may be utilized while complying with what is described herein, and/or example embodiment are applicable to it.

For example, various example embodiments are applicable in any (e.g., mobile/wireless) communication system, such as 5G/NR systems and next-generation systems beyond 5G. For example, various example embodiments are applicable in 3GPP-standardized mobile/wireless communication system of Release 18 onwards.

-12 -Hereinafter, various example embodiments are described using several variants and/or alternatives. It is generally to be noted that, according to certain implementations and constraints, all of the described variants and/or alternatives may be provided alone or in any conceivable combination (e.g., also including combinations of individual features of these various variants and/or alternatives).

As used herein, the words "comprising" and "including" should be understood as not limiting the example embodiments to consist of only those features that have been mentioned, and such example embodiments may also contain additional items (e.g. features, structures, units, modules, among other things) that have not been specifically mentioned.

As used herein, "at least one of the following: <a list of two or more elements>" and "at least one of <a list of two or more elements>" and similar wording, where the list of two or more elements are joined by "and" or "or", mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

In the drawings, it is to be noted that lines/arrows interconnecting individual blocks or entities are generally meant to illustrate an operational coupling there-between, which may be a physical and/or logical coupling, which on the one hand is implementation-independent (e.g., wired or wireless) and on the other hand may also comprise an arbitrary number of intermediary functional blocks or entities not shown. In flowcharts or sequence diagrams, the illustrated order of operations or actions is illustrative and non-limiting, and any other order of respective operations or actions is conceivable, where feasible.

Various example embodiments relate to prioritization of communication, such as prioritization of messages, in/for a mobile communication system, e.g., a 3GPP-standardized mobile/wireless communication system, such as a 5G/NR system and a next-generation system beyond 5G.

-13 -With reference to a service-based architecture in/of a 5G/NR system, for instance, a mechanism for prioritizing the processing of any received (service-related) messages from a consumer (e.g., an NF service consumer) may be applied at a recipient such as a producer (e.g., an NF service producer) or any intermediate network function (NF) and/or service communication proxy (SCP). This might occur when the receiving entity, e.g., the processor thereof, is experiencing a high load state or overload state. However, the priority associated with each (service-related) message in this case is not used for other purposes beyond handling during the high load state or the overload state.

Such a service-based architecture may define, for various APIs, a service-based interface (SBI) between a consumer and a producer, over which service-related communication is carried, either directly or via one or more intermediate network functions (NFs) and/or service communication proxies (SCP). Hence, the above-described technique may be regarded as an SBI message priority mechanism.

A consumer may subscribe, at a producer (e.g., a UDR), to notifications of resource data change or other events (e.g., relating to a service being consumed by the consumer and produced by the producer), using a subscription operation. Based thereon, the producer notifies the consumer of subscribed data, such as resource data change or other events (e.g., relating to the service), as appropriate.

By way of the SBI message priority mechanism, any message sent on a SBI (e.g., including a subscription also referred to as subscription request from the consumer to the producer and a notification from the producer to the consumer) may include priority information for this specific message (e.g., a 3gpp-Sbi-Message-Priority header). Thereby, it is indicated to the recipient (e.g., the producer, or an intermediate NFs/SCPs) how to handle or, stated differently, how to prioritize this specific message when making decisions related to high load or overload control or the like.

-14 -Accordingly, the consumer is to decide, e.g., based on a local policy and/or configuration, on the message priority (if any) to be applied for any messages sent from the consumer, such as subscriptions also referred to as subscription requests, and the producer is to decide, e.g., based on a local policy and/or configuration, on the message priority (if any) to be used for any messages sent from the producer, such as (e.g., subscribed) notifications.

However, there is no way for the consumer subscribing to notifications from the producer to indicate, at subscription time (e.g., in a subscription request message for notifications), a message priority (if any) to be used by the producer when sending notifications for the subscription. As the producer has to locally decide on a message priority (if any) to be used for the notifications, using local policy and/or configuration, potentially in view of characteristics of the consumer, which are derivable from information in the subscription, it is thus challenging for the producer to apply an appropriate priority for the notifications. Accordingly, an inappropriate prioritization of the notifications from the producer to the consumer may result at least in certain use cases or circumstances.

It is to be noted that the above issues, which are described with respect to the use case of notification subscription in a service-based architecture, are more generally applicable in mobile communication systems. More specifically, the above issues also relate to subsequent communication from a responder entity to an initiator entity when/as there is no way of indicating a message priority for the subsequent communication in the course of (e.g., at the time of) an initial communication by the initiator entity.

Therefore, a technique for (e.g., enabling/realizing) message priority indication for subsequent communication (e.g., after/based on/in response to initial communication) in a mobile communication system may be advantageous.

-15 -According to various example embodiments, there are provided measures/mechanisms for (e.g., enabling/realizing) message priority indication for subsequent communication (e.g., after/based on/in response to initial communication) in a mobile communication system.

FIG. 1 shows a flowchart illustrating a method or process according to at least one example embodiment. The method or process of FIG. 1 is a method or process of (or, stated differently, operable or for use in/by) an initiator entity, or an element, function or entity of specific functionality or operability, in/of a mobile communication system. Such initiator entity may, for example, be or relate to a (e.g., NF service) consumer, while the referenced responder entity may, for example, be or relate to a (e.g., NF service) producer, without being limited accordingly.

As shown in FIG. 1, the method or process comprises an operation (5110) of specifying a message priority as a preferred or required priority for one or more messages (e.g., service-related messages relating to a service) from a responder entity in/of the mobile communication system, and an operation (S120) of issuing a request message (e.g., a request message relating to the service), including priority information indicative of the specified message priority, said priority information serving to indicate to (e.g., control, instruct or influence) the responder entity to apply the specified message priority for one or more messages (e.g., service-related messages relating to the service).

In this regard, the request message (e.g., request message relating to the service) of/from the initiator entity may be regarded as an initial communication, while the one or more messages (e.g., service-related messages relating to the service) of/from the responder entity may be regarded as a subsequent communication. The subsequent communication may be somehow related to the initial communication, e.g., by relating to the same service, by exhibiting some inter-/dependence (e.g., a request-response-or a subscription-notification-relationship), or the like.

-16 -According to various example embodiments, the priority information may for example be included in a header of the request message (e.g., a dedicated header for carrying the priority information) or a payload or body of the request message (e.g., a dedicated section or information element for carrying the priority information in the payload or body).

According to various example embodiments, the priority information may be specified for different cases, use cases or circumstances. Thereby, the responder entity may utilize the priority information of the initiator entity depending on the present, actual or prevailing case, use case or circumstance, respectively. In an example embodiment, in a case relating to a subscription to notifications, it can be possible for a consumer to specify priority preference/s or requirement/s for different notification use cases, all such use cases being relevant to the subscription being requested/created, such as deletion of a resource or creation of a resource or update of a resource. Based thereon, it can be possible for a producer to utilize the thus indicated priority preference/s or requirement/s for related notifications, e.g., a notification relating to deletion of a resource or creation of a resource or update of a resource. In an example embodiment, in a case relating to a subscription to notifications, it can be possible for a consumer to specify priority preference/s or requirement/s for different network or processing conditions of a producer, such as high network load or high CPU load, different times of day, or the like. Based thereon, it can be possible for the producer to utilize the thus indicated priority preference/s or requirement/s for notifications relating to or complying with the associated condition/s, e.g., sending a notification in the event of high network load or high CPU load, at a certain time of day, or the like. It is to be noted that similar or corresponding principles can be applicable for example embodiments other than example embodiments relating to a subscription to notifications.

According to various example embodiments, the priority information may for example comprise transmission-specific priority information for -17 -application of the specified message priority in transmission (e.g., prior to, during and/or after transmission, and/or for transmission) of the one or more messages (e.g., service-related messages relating to the service) by the responder entity, and/or generation-specific priority information for application of the specified message priority in generation (e.g., prior to, during and/or after generation, and/or for generation) of the one or more messages (e.g., service-related messages relating to the service) at/by the responder entity, and/or content-specific priority information for application of the specified message priority in creation (e.g., prior to, during and/or after creation, and/or for creation) of content of the one or more messages (e.g., service-related messages relating to the service) by the responder entity.

FIG. 2 shows a flowchart illustrating a method or process according to at least one example embodiment. The method or process of FIG. 2 is a method or process of (or, stated differently, operable or for use in/by) a responder entity, or an element, function or entity of specific functionality or operability, in/of a mobile communication system. Such responder entity may for example be or relate to a (e.g., NF service) producer, while the referenced initiator entity may for example be or relate to a (e.g., NF service) consumer, without being limited accordingly.

As shown in FIG. 2, the method or process comprises an operation (5210) of obtaining priority information indicative of a message priority of an initiator entity of the mobile communication system, said message priority being specified by the initiator entity as a preferred or required priority for one or more messages (e.g., service-related messages relating to a service) from the responder entity, and an operation (5220) of utilizing the priority information to apply the message priority of the initiator entity for one or more messages (e.g., service-related messages relating to the service).

In this regard, the priority information may be obtained in/by or as a result of an initial communication (e.g., a request message (e.g., a request message relating to the service)) of/from the initiator entity, while the one -18 -or more messages (e.g., service-related messages relating to the service) of/from the responder entity may be regarded as a subsequent communication. The subsequent communication may be somehow related to the initial communication, e.g., by relating to the same service, by exhibiting some inter-/dependence (e.g., a request-response-or a subscription-notification-relationship), or the like.

According to various example embodiments, the priority information may, for example, comprise or indicate a priority value, wherein utilizing the priority information may comprise using the priority value for applying the message priority of the initiator entity, and/or a priority policy, wherein utilizing the priority information comprises employing the priority policy for deriving a priority value for applying the message priority of the initiator entity, and/or a content value, wherein utilizing the priority information comprises creating content of one or more parameters or information elements for applying the message priority of the initiator entity. In view thereof, utilizing the priority information may, for example, comprise assigning the priority value to the one or more messages (e.g., service-related messages relating to the service), and/or including the content in the one or more messages (e.g., service-related messages relating to the service).

According to various example embodiments, the priority information may be specified for different cases, use cases or circumstances. Accordingly, the applicable case, use case or circumstance of the priority information may be obtained, and the priority information of the initiator entity may be utilized depending on the present, actual or prevailing case, use case or circumstance, respectively. For certain example embodiments, reference is made to the above description with regard to FIG. 1, in which example functionalities of a consumer and a producer are described.

According to various example embodiments, the priority information may, for example, comprise transmission-specific priority information, wherein -19 -utilizing the priority information comprises applying the message priority of the initiator entity in transmission (e.g., prior to transmission, during transmission, and/or after transmission) of the one or more messages (e.g., service-related messages relating to the service), and/or generation-specific priority information, wherein utilizing the priority information comprises applying the message priority of the initiator entity in generation (e.g., prior to generation, during generation, and/or after generation) of the one or more messages (e.g., service-related messages relating to the service), and/or content-specific priority information, wherein utilizing the priority information comprises applying the message priority of the initiator entity in creation (e.g., prior to creation, during creation, and/or after creation) of content of the one or more messages (e.g., service-related messages relating to the service). For example, when applying the message priority of the initiator entity in transmission (e.g., prior to transmission, during transmission, and/or after transmission) of the one or more messages (e.g., service-related messages relating to the service), a sequence of message transmission and/or a guidance for message handling in transfer from the responder entity to the initiator entity, such as, for example, in a dedicated header for message prioritization, may be established based on the transmission-specific priority information. For example, when applying the message priority of the initiator entity in generation (e.g., prior to generation, during generation, and/or after generation) of the one or more messages (e.g., service-related messages relating to the service), a sequence of message generation and/or a selection of messages to be generated, such as, for example, in a high load or overload condition of one or more message generation resources, may be established based on the generation-specific priority information. For example, when applying the message priority of the initiator entity in creation (e.g., prior to creation, during creation and/or after creation) of content of the one or more messages (e.g., service-related messages relating to the service), the content of one or more parameters or information elements of messages, such as, for example, a differentiated services code point value, may be established based on the content-specific priority information.

-20 -In view thereof, the initiator entity may specify the message priority to use for transmission of messages (of subsequent communication), so as to allow the initiator entity to indicate or, stated differently, to control, instruct and/or influence the responder entity to use a specific message priority for all subsequent communication of any relevant types, including e.g., notifications (in the case of a notification subscription). Such transmission-specific priority information can generally be used, but could be advantageous (e.g., efficient) when the responder entity is experiencing high load, or overload, affecting the responder entity resources that are used for message transmission. Also, the initiator entity may specify the message priority to use for generation of messages (of subsequent communication), so as to allow the initiator entity to indicate to or, stated differently, to control, instruct and/or influence the responder entity to use a specific message priority for all subsequent communication of any relevant types, including e.g., notifications (in the case of a notification subscription). Such generation-specific priority information can generally be used, but could be advantageous (e.g., efficient) when the responder entity is experiencing high load, or overload, affecting the responder entity resources that are used for message generation. The priority information, e.g., priority-influencing parameters, with respect to message generation can be separate from the priority information, e.g., priority-influencing parameters, with respect to message transmission. Also, the initiator entity may specify the message priority to use for contents of messages (of subsequent communication), so as to allow the initiator entity to indicate to or, stated differently, to control, instruct and/or influence the responder entity to use a specific message content with regard to message priority for all subsequent communication of any relevant types, including e.g., notifications (in the case of a notification subscription). Namely, the initiator entity may influence a DSCP value used by the responder entity for/in messages (e.g., notifications). However, the set of DSCP values supported by the responder entity for messages (e.g., notifications) may not be known to the initiator entity, so the responder entity may not always be able to use -21 -the requested DSCP values (but the responder entity, for example, rather disregards/disregards the requested DSCP values).

As indicated by a dashed-line box in FIG. 2, the method or process may further comprise an operation (5212) of storing the priority information (in a local memory, storage, etc. of/at the responder entity and/or some connected other entity).

As indicated by a dashed-line box in FIG. 2, the method or process may further comprise an operation (5214) of determining applicability of the message priority of the initiator entity for one or more messages (e.g., service-related messages relating to the service). As a result of such determination, the priority information may be utilized to apply the message priority of the initiator entity, based on the applicability being affirmed (e.g., when the applicability is affirmed), and a local policy or configuration may be utilized to apply a message priority other than the message priority of the initiator entity or apply no message priority, based on the applicability being denied (e.g., when the applicability is denied). For example, when the preferred or required message priority specified by the initiator entity is applicable for some specific case, use case or circumstance, which is however not existing at the time priority information utilization, the (presently obtained) priority information can be disregarded/discarded. For example, when the preferred or required message priority specified by the initiator entity contradicts a (higher-ranking or superordinate) message priority resulting from a local policy or configuration (e.g., a message priority which is mandatory for a subscribed data resource or even in the case of a notification subscription), the responder entity may disregard/discard the (e.g., obtained) priority information, e.g., the preferred or required message priority of the initiator entity, and use another (e.g., higher-ranking or superordinate) message priority instead. In an example embodiment, in a case relating to a subscription to notifications, when a consumer specifies some specific condition for notifications relating to the subscription being requested/created, such as a condition a network or processing condition of -22 -a producer, such as high network load or high CPU load, different times of day, or the like, the producer can decide to disregard/discard such condition but instead generate and/or send corresponding notifications under different conditions, e.g., at another load level, at another time of day, or the like.

Accordingly, the responder entity may choose to ignore the (presently obtained) priority information, e.g., the preferred or required message priority of the initiator entity, and use another approach (e.g., predetermined approach or default approach) for applying a message priority for the one or more messages (e.g., service-related messages relating to the service). Thereby, the responder entity can have backward compatibility.

In view of the above, there are various example embodiments, in which an initiator entity is enabled to (e.g., optionally) specify and indicate in any request message (e.g., a subscription request for a subscription to notifications) priority information, e.g., a priority value for a responder entity to use for the related messages, e.g., subsequent communication, or a policy for a responder entity to assign priority values for the related messages, e.g., subsequent communication, in different cases or circumstances. The priority information may be dynamically specified and/or issued/provided by the initiator entity, e.g., depending on current circumstances, requirements, purposes or the like, such that the preferred or required message priority can be dynamically adapted/changed for any individual request (such as a subscription request, a registration request, etc.). In certain example embodiments, the message priority may refer to and/or define a sequence or order of messages (e.g., in transmission and/or generation thereof), a handling guidance of messages (e.g., in terms of differentiated service handling, overload handling), or the like. Further, the priority (preference or policy) information may be provided/included as appropriate, e.g., in an HTTP header, in the payload or body of the request message, or the like. The responder entity is enabled to store the priority information about the initiator entity's priority preference or requirements (e.g., in the subscription resource), and to use this priority information to make decisions about a message priority value to use for the related -23 -messages, e.g., subsequent communication (e.g., when sending a notification related to the subscription).

In the following, various use cases or applications of example embodiments are explained with regard to (e.g., assuming implementation in/for) a service-based architecture. Namely, a consumer (e.g., an NF service consumer) is, in some example embodiments, adopted/assumed/implemented as an initiator entity, and a producer (e.g., an NF service producer) is, in some example embodiments, adopted/assumed/implemented as a responder entity. It is to be noted that such explanations are merely of exemplary nature and are made for illustrative purposes only, without limiting the various example embodiments accordingly.

As explained above, any communication between consumer and producer can be a direct communication or a communication via one or more intermediate network functions (NFs) and/or service communication proxies (SCP). Accordingly, even if not explicitly illustrated or described the presence of any intermediate entities in the subsequent explanation, it is to be noted that any mentioned communication or message can be realized in a direct or indirect manner.

FIG. 3 shows a sequence diagram illustrating a procedure according to at least one example embodiment (assuming an architecture/deployment including a consumer and a producer).

As shown in FIG. 3, a consumer (e.g., after/based on/in response to specifying a message priority as a preferred or required priority for service-related messages relating to a service from a producer) issues and sends a request message relating to the service to the producer. This request message includes priority information indicative of the specified message priority, wherein the priority information (e.g., is configured, intended or designated to) serve to indicate to (e.g., control, instruct or influence) the producer to apply the specified message priority for service-related messages relating to the service. The priority information may be included -24 -in a header (e.g., a dedicated header for carrying the priority information) of the request message or a payload or body of the request message (e.g., a dedicated section or information element for carrying the priority information in the payload or body).

As shown in FIG. 3, the producer receives the request message from the producer, thereby obtaining the priority information indicative of the message priority of the consumer (e.g., the preferred or required priority for service-related messages relating to the service from the consumer), and utilizes the priority information to apply the message priority of the consumer for service-related message/s relating to the service. Then, the producer sends the service-related message/s based on the applied message priority or, stated differently, the application of the message priority to the consumer.

For example, when the request message is or comprises a subscription request for subscribing to notifications with respect to the service, the service-related messages are or comprise subscribed notifications with respect to the service. For example, when the request message is or comprises a registration request for registering service-related information of the initiator entity (e.g., an implicit notification subscription with respect to the service) at the responder entity, the service-related messages are or comprise corresponding messages based on the service-related information (e.g., notifications with respect to the service based on the implicit notification subscription).

For example, the request message from the consumer to the producer may be or comprise a registration request for registering service-related information of the consumer at the producer, which may e.g., be a UDM.

Then, the priority information may be registered as part of the service-related information of the consumer at the producer, the service-related information of the consumer may represent an implicit notification subscription with respect to the service, and the service-related messages -25 -may be or comprise notifications with respect to the service based on the implicit notification subscription.

As an example embodiment, this may be achieved by adding priority information, e.g., priority-influencing parameters, to any one or more of those data types that include relevant data/information, such as callback URI attributes, for implicit subscriptions. Namely, the deregCallbackUri field in an AmfAmf3GppAccessRegistration message from an AMF to a UDM may, for example, be extended to include similar priority information, e.g., priority-influencing parameters, as may be passed in (e.g., the header or payload or body of) a subscription request, registration request or the like.

Hereinafter, FIGS. 4 to 7 relate to at least one example embodiment relating to a subscription operation, in which the request message is or comprises a subscription request for subscribing to notifications with respect to the service and the service-related messages are or comprise subscribed notifications with respect to the service.

FIGS. 4 and 5 show a sequence diagrams illustrating associated procedures 20 according to example embodiments. Namely, FIG. 4 relates to a subscription procedure, and FIG. 5 relates to a notification procedure being based on the preceding subscription of FIG. 4.

As shown in FIG. 4, a consumer sends a subscription request to a producer using a POST (e.g., or any HTTP-based) method. In the subscription request, besides the subscription data, a header is included, exemplarily denoted by 3gpp-sbi-pref-notif-prio, as an example embodiment of a dedicated header for carrying the priority information. In this header (e.g., which may be an HTTP header), the priority information of the consumer is included. Based upon reception of the subscription request, the producer may store the priority information of the consumer and sends a confirmation for confirming establishment of the requested subscription, e.g., as a 201 Created message.

-26 - As shown in FIG. 5, assuming that a subscribed resource data change, event or the like (e.g., as defined by the subscription data in the subscription request of FIG. 4) occurs, the producer sends a notification as a service-related message to the consumer using a POST (e.g, or any HTTP-based) method. As an address/destination of the notification, the producer uses the consumer's callback reference, such as a callback URI, as is included in the subscription request of FIG. 4 or otherwise known (e.g., from a NRF profile of the consumer). In the notification, besides the notification data/information, a header is included, as denoted by 3gpp-Sbi-Message-Priority (e.g., according to the SBI message priority mechanism), as an example embodiment of a header for indicating to the consumer how to handle or, stated differently, how to prioritize this notification when making decisions related to overload control or the like. Based upon reception of the notification, the consumer sends a confirmation for confirming receipt of the notification, e.g., as a 204 message.

The priority-related indication (e.g., the corresponding prioritization of the notification) in the notification results from utilization of the priority information of the consumer (as included in the subscription request of FIG. 4), e.g., application of the message priority of the consumer (as included in the priority information in the subscription request of FIG. 4), by the producer. Namely, the producer has used a priority value and/or a priority policy, as included in the priority information of the consumer, for assigning an appropriate priority value to/for the notification, thereby ensuring that the notification is provided with the preferred or required priority for notifications, e.g., subsequent communication.

FIGS. 6 and 7 show sequence diagrams illustrating associated procedures according to example embodiments. Namely, FIG. 6 relates to a subscription procedure, and FIG. 7 relates to a notification procedure being based on the preceding subscription of FIG. 6.

As shown in FIG. 6, a consumer sends a subscription request to a producer using a POST (e.g., or any HTTP-based) method. In the subscription 35 request, besides the subscription data, a payload or body (e.g., -27 -part/section) is included, as denoted by preferredPriority, as an example embodiment of a dedicated section or information element for carrying the priority information in the payload or body. In this payload or body (e.g., which may be payload or body in an HTTP message), the priority information of the consumer is included. Based on reception of the subscription request, the producer may store the priority information of the consumer and sends a confirmation for confirming establishment of the requested subscription, e.g., as a 201 Created message.

As the procedure of FIG. 7 may, for certain example embodiments, be similar or equivalent to that of FIG. 5, reference is made to the above description of FIG. 5 accordingly.

In the foregoing, two example options/alternatives for carrying the priority information are given, namely in a header or in a payload or body of a request message, which may be applicable for any use case or application or implementation (e.g., not only in the context of notification subscription). Using a header may have the advantage that such mechanism is generally applicable to various APIs (or SBIs) without updating current specifications of the respective APIs (or SBIs), but can have the potential drawback that it may be challenging for an initiator entity (e.g., a consumer) to update the priority information, e.g., the preferred or required message priority, for a previously initiated communication, e.g., services or related actions, for which the underlying request message had already been sent (e.g., for existing/established subscriptions), but a new request message (e.g., a new subscription request) with correspondingly updated priority information is utilized. Using a payload or body may have the advantage that an initiator entity (e.g., a consumer) can read, remove or update the priority information, e.g., the preferred or required message priority, using corresponding processes/actions, e.g.. a subscription read/modify/delete request, e.g., an operation within a previously initiated communication, e.g., services or related actions, for which the underlying request message had already been sent (e.g., for existing/established subscriptions), but can have the potential drawback that any API (or SBI) is required to support -28 -this specific mechanism, e.g., the current specifications of the respective APIs (or SBIs) would thus be updated accordingly.

In the procedures of FIGS. 4 to 7, as an example embodiment, the priority information in the subscription request, comprises or is regarded/understood, and thus utilized, as transmission-specific priority information. That is, the priority information in the subscription request is used in/for transmission of the notification by the producer, thus affecting a guidance for message handling in transfer from the producer to the consumer, e.g., in the form of the 3gpp-Sbi-Message-Priority header in the notification. Alternatively, a sequence of message transmission, e.g., transmission of notifications from the producer to the consumer could also be affected accordingly. For example, in case the priority information for two subscriptions comprise priority values 1 and 2 (or priority polices leading to priority values 1 and 2), the notification corresponding to the subscription with the higher (or lower) value obtains a higher handling priority or is transmitted first, and the notification corresponding to the subscription with the lower (or higher) value obtains a lower handling priority or is transmitted second, or vice versa.

FIG. 8 shows a sequence diagram illustrating a procedure according to at least one example embodiment (assuming an architecture/deployment/implementation including a consumer, a producer and a registry/repository, such as, e.g., a NRF).

As shown in FIG. 8, a consumer (e.g., after/based on/in response to specifying a message priority as a preferred or required priority for service-related messages relating to a service from a producer) issues and sends a request message relating to the service to the registry/repository. This request message includes priority information indicative of the specified message priority, wherein the priority information (e.g., is configured, intended or designated to) serve to indicate to (e.g., control, instruct or influence) the producer to apply the specified message priority for service-related messages relating to the service. The priority information may be included in a header (e.g., a dedicated header for carrying the priority -29 -information) of the request message or a payload or body of the request message (e.g., a dedicated section or information element for carrying the priority information in the payload or body).

As shown in FIG. 8, the registry/repository receives the request message from the consumer, thereby obtaining the priority information indicative of the message priority of the consumer (e.g., the preferred or required priority for service-related messages relating to the service from the consumer). Then, the registry/repository stores the priority information of the consumer, e.g., in connection or association with profile information of the registry/repository, which is already held or amended or registered (e.g., after/based on/in response to the request message).

As shown in FIG. 8, the producer acquires the priority information of the consumer from the registry/repository, e.g., the profile information of the consumer in the registry/repository, thereby obtaining the priority information indicative of the message priority of the consumer (e.g., the preferred or required priority for service-related messages relating to the service from the consumer). Such acquisition may be effected after/based on/in response to a request from the producer to the register/repository, or triggered by the register/repository (e.g., without request from the producer), e.g., in a periodic or cyclic manner, after/based on/in response to some triggering event, or the like. Then, the producer utilizes the priority information to apply the message priority of the consumer for service-related message/s relating to the service. Based thereupon, the producer sends the service-related rnessage/s based on the applied message priority or, stated differently, the application of the message priority to the consumer.

For example, the request message may be or comprise a registration request for registering profile information of the consumer at the registry/repository, such as the NRF. Based thereon, the priority information may be registered as part of the profile information of the consumer, such -30 -as the NF profile of the consumer. Such profile information of the consumer may relate to a default notification subscription with respect to a service in question, and the service-related messages may accordingly be or comprise notifications with respect to the service based on the default notification subscription.

As an example embodiment, a default notification subscription that a consumer may register at the NRF (e.g., together with its NRF profile) may be extended to allow transmission to and storage in the NRF of priority information, e.g., message priority parameters, that the producer should use for notifications (namely, such default notifications). This may be achieved e.g., by extending the DefaultNotificationSubscription data type (e.g., as part of the NF profile of the consumer) to include similar priority information, e.g., priority-influencing parameters, as may be passed in (e.g., the header or payload or body of) a subscription request, registration request or the like. In this regard, the NRF may be used as a repository for information about a producer who registers this information as being usable for purposes of discovery by a consumer. A consumer may register a DefaultNotificationSubscription that a producer, e.g., a producer of notifications, may use as a destination to send notifications that do not have an explicit subscription set-up, configuration or establishment (e.g., for notifications that are not explicitly set up, configured or established), for example as part of an implicit subscription. A producer configured to send such a notification may ask or inquire the NRF for NF service instances, such as a consumer, that have registered a DefaultNotificationSubscription that applies to the specific type of notification that the NF is configured to send. Based thereon, the producer can acquire the related priority information and utilize the same for the application to service-related messages.

As evident from various example embodiments described herein, there are provided measures/mechanisms for (e.g., enabling/realizing) message priority indication for subsequent communication (e.g., after/based on/in response to initial communication) in a mobile communication system.

-31 -Various example embodiments provide a technique for enabling an initiator entity to indicate to a responder entity a preferred or required message priority to use for messages from the responder entity to the initiator entity.

Thereby, the responder entity is enabled to indicate to or, stated differently, control, instruct or influence the responder entity in the message priority to be applied in a subsequent communication, e.g., selecting or assigning a priority to use for messages (to be) sent to the initiator entity. While the applicability of the various example embodiments is not limited to (explicit) subscription operations, a consumer subscribing to notifications is provided with the ability to indicate to the producer a preferred or required message priority to use when sending notifications related to the subscription, for exam ple.

Various example embodiments provide for a more appropriate message priority for subsequent communication, e.g., a more appropriate assignment of message priority values. Thereby, for example, more effective overload protection may be provided, resulting in lower impact on communication/message or service delivery during overload and faster recovery. Accordingly, the responder entity is assisted in applying an appropriate priority for subsequent communication, e.g., notifications, such that no inappropriate prioritization of the subsequent communication, e.g., notifications, from the responder entity to the initiator entity will result.

The above-described functionality as well as its related operations, procedures, methods and processes may be implemented by respective functional elements, entities, modules, units, processors, or the like, as described below. These functional elements, entities, modules, units, processors, or the like, e.g., the implementation of one or more example embodiments, may be realized in a cloud environment, by SDN, by NFV/NFVI, or the like.

While the foregoing example embodiments are described mainly with reference to operations, procedures, methods and processes, these example -32 -embodiments also cover respective apparatuses, entities, modules, units, network nodes and/or systems, including software and/or hardware thereof.

Respective example embodiments are described below referring to FIGS. 9 and 10, while for the sake of brevity reference is made to the detailed description of respective corresponding configurations/setups, schemes, processes, sequences, methods as well as functionalities, principles and operations according to FIGS. 1 to 8.

In FIGS. 9 and 10, the blocks are configured to perform respective methods, procedures and/or functions as described above. The entirety of blocks are configured to perform the methods, procedures and/or functions as described above, respectively. With respect to FIGS. 9 and 10, it is to be noted that the individual blocks are meant to illustrate respective functional blocks implementing a respective function, process or procedure, respectively. Such functional blocks are implementation-independent, e.g., may be implemented by means of any kind of hardware or software or combination thereof, respectively.

Further, in FIGS. 9 and 10, functional blocks are illustrated, which relate to any one of the above-described methods, procedures and/or functions. A skilled person will acknowledge the presence of any other functional blocks utilized for an operation of respective structural arrangements, e.g., a power supply, a central processing unit, respective memories or the like.

Among others, one or more memories are provided for storing programs or program instructions for controlling or enabling the individual functional entities or any combination thereof to operate as described herein in relation to example embodiments.

FIG. 9 shows a schematic diagram illustrating a structure of apparatuses according to at least one example embodiment. Herein, an apparatus can represent a physical entity or component, e.g., a structural device implementing a specific network element, entity or function or the functionality thereof as such, or a functional or logical entity or component.

-33 -For example, the illustrated apparatus may be realized in or by a server or the like in a cloud environment, e.g., by a cloud-based implementation.

As indicated in FIG. 9, according to at least one example embodiment, an apparatus 900 may comprise or realize at least one processor 910 and at least one memory 920 (and possibly also at least one interface 930), which may be operationally connected or coupled, for example by a bus 940 or the like, respectively.

The processor 910 and/or the interface 930 of the apparatus 900 may also include a modem or the like to facilitate communication over a (e.g., hardwire or wireless) link, respectively. The interface 930 of the apparatus 900 may include a transmitter, receiver or transceiver connected or coupled to one or more antennas, antenna units, such as antenna arrays or communication facilities or means for (e.g., hardwire or wireless) communications with the linked, coupled or connected device(s), respectively. The interface 930 of the apparatus 900 is generally configured to communicate with at least one other apparatus, device, node or entity (in particular, the interface thereof).

The memory 920 of the apparatus 900 may represent a (nontransitory/tangible) storage medium (e.g., RAM, ROM, EPROM, EEPROM, etc.) and store respective software, programs, program products, macros or applets, etc. or parts of them, which may be assumed to comprise program instructions or computer program code that, when executed by the respective processor, enables the respective electronic device or apparatus to operate in accordance with example embodiments described herein. Further, the memory 920 of the apparatus 900 may (comprise a database to) store any data, information, or the like, which is used in the operation of the apparatus.

According to various example embodiments, respective apparatuses (and/or parts thereof) may represent means for performing respective operations and/or exhibiting respective functionalities, and/or the respective devices -34 - (and/or parts thereof) may have functions for performing respective operations and/or exhibiting respective functionalities.

In view of the above, the illustrated apparatus 900 can be used in practicing 5 one or more of the example embodiments, as described herein.

According to at least one example embodiment, the illustrated apparatus 900 may represent or realize/embody a (e.g., part of a) initiator entity, or an element, function or entity of specific functionality or operability, in/of a mobile communication system, e.g., being or relating to a (e.g., NF service) consumer. Hence, the apparatus 900 may be configured to perform a procedure and/or exhibit a functionality and/or implement a mechanism, as described (e.g., for an initiator entity or a consumer) in any one of FIGS. 1, 3 to 8.

Accordingly, the apparatus 900 may be caused or the apparatus 900 or its at least one processor 910 (e.g., together with instructions stored in its at least one memory 920) may be configured to specify a message priority as a preferred or required priority for service-related messages relating to a service from a responder entity of the mobile communication system, and to issue a request message relating to the service, the request including priority information indicative of the specified message priority, said priority information serving to instruct the responder entity to apply the specified message priority for service-related messages relating to the service.

According to at least one example embodiment, the illustrated apparatus 900 may represent or realize/embody a (e.g., part of a) responder entity, or an element, function or entity of specific functionality or operability, in/of a mobile communication system, e.g., being or relating to a (e.g., NF service) producer. Hence, the apparatus 900 may be configured to perform a procedure and/or exhibit a functionality and/or implement a mechanism, as described (e.g., for a responder entity or a producer) in any one of FIGS. 2 to 8.

-35 -Accordingly, the apparatus 900 may be caused or the apparatus 900 or its at least one processor 910 (e.g., together with instructions stored in its at least one memory 920) may be configured to obtain priority information indicative of a message priority of an initiator entity of the mobile communication system, said message priority being specified by the initiator entity as a preferred or required priority for service-related messages relating to a service from the responder entity, and to utilize the priority information to apply the message priority of the initiator entity for service-related messages relating to the service.

As mentioned above, an apparatus according to at least one example embodiment may be structured by comprising respective one or more units or means or circuitries for performing corresponding operations, procedures and/or functions. For example, such one or more units or means or circuitries may be implemented/realized on the basis of an apparatus structure, as illustrated in FIG. 9, e.g., by one or more processors 910, one or more memories 920, one or more interfaces 930, or any combination thereof.

FIG. 10 shows a schematic diagram illustrating a structure of apparatuses according to at least one example embodiment.

As shown in FIG. 10, an apparatus 1010 according to at least one example embodiment may represent or realize/embody a (e.g., part of a) initiator entity, or an element, function or entity of specific functionality or operability, in/of a mobile communication system, e.g., being or relating to a (e.g., NF service) consumer. Hence, the apparatus 1010 may be configured to perform a procedure and/or exhibit a functionality and/or implement a mechanism, as described (e.g., for an initiator entity or a consumer) in any one of FIGS. 1, 3 to 8.

The apparatus 1010 may comprise (at least) one or more unit/means/circuitry, denoted by specifying section 1011, which represent any implementation for (or configured to) specifying (specify) a message -36 -priority as a preferred or required priority for service-related messages relating to a service from a responder entity of the mobile communication system, and one or more unit/means/circuitry, denoted by issuing section 1012, which represent any implementation for (or configured to) issuing (issue) a request message relating to the service, the request including priority information indicative of the specified message priority, said priority information serving to instruct the responder entity to apply the specified message priority for service-related messages relating to the service.

Further, the apparatus 1010 may comprise one or more unit/means/circuitry, denoted by sending/receiving section 1013, which represent any implementation for (or configured to) sending (send) the request message to the responder entity, and/or receiving (receive) the service-related messages from the responder entity.

As shown in FIG. 10, an apparatus 1020 according to at least one example embodiment may represent or realize/embody a (e.g., part of a) responder entity, or an element, function or entity of specific functionality or operability, in/of a mobile communication system, e.g., being or relating to a (e.g., NF service) producer. Hence, the apparatus 1020 may be configured to perform a procedure and/or exhibit a functionality and/or implement a mechanism, as described (e.g., for a responder entity or a producer) in any one of FIGS. 2 to 8.

The apparatus 1020 may comprise (at least) one or more unit/means/circuitry, denoted by obtaining section 1021, which represent any implementation for (or configured to) obtaining (obtain) priority information indicative of a message priority of an initiator entity of the mobile communication system, said message priority being specified by the initiator entity as a preferred or required priority for service-related messages relating to a service from the responder entity, and (at least) one or more unit/means/circuitry, denoted by utilizing section 1022, which represent any implementation for (or configured to) utilizing (utilize) the -37 -priority information to apply the message priority of the initiator entity for service-related messages relating to the service.

Further, in the apparatus 1020, the utilizing section 1022 may comprise one or more unit/means/circuitry which represent any implementation for (or configured to) assigning (assign) the priority value to the service-related messages relating to the service, and/or including (include) the content in the service-related messages relating to the service.

Further, the apparatus 1020 may comprise at least one of the following: one or more unit/means/circuitry, denoted by storing section 1023, which represent any implementation for (or configured to) storing (store) the priority information; one or more unit/means/circuitry, denoted by determining section 1024, which represent any implementation for (or configured to) determining (determine) applicability of the message priority of the initiator entity for service-related messages relating to the service; one or more unit/means/circuitry, denoted by acquiring section 1025, which represent any implementation for (or configured to) acquiring (acquire) profile information of the initiator entity from a registry or repository entity, wherein the priority information may be part of and obtained from the profile information of the initiator entity; or one or more unit/means/circuitry, denoted by sending/receiving section 1026, which represent any implementation for (or configured to) receiving (receive) a request message relating to the service from the initiator entity, the request message including the priority information, wherein the priority information is obtained from the request message, and/or sending (send) the service-related messages to the initiator entity.

For further details regarding the operability/functionality of the apparatuses (or units/means thereof) according to example embodiments, reference is made to the above description in connection with any one of FIGS. 1 to 8, respectively.

-38 -According to example embodiments, any one of the (at least one) processor, the (at least one) memory and the (at least one) interface, as well as any one of the illustrated units/means, may be implemented as individual modules, chips, chipsets, circuitries or the like, or one or more of them can be implemented as a common module, chip, chipset, circuitry or the like, respectively.

As used herein, the term "circuitry" may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and (b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and/or digital hardware circuit(s) with software/firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions), and (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that utilizes software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

This definition of circuitry applies to all uses of this term herein, including in any claims. As a further example, as used herein, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

According to various example embodiments, a system may comprise any conceivable combination of any depicted or described apparatuses and other network elements or functional entities, which are configured to cooperate as described above.

-39 -In general, it is to be noted that respective functional blocks or elements according to various example embodiments described herein can be implemented by any means, either in hardware and/or software, respectively, where adapted to perform at least the described functions of the respective example embodiment (or portion thereof). The mentioned method steps can be realized in individual functional blocks or by individual devices, or one or more of the method steps can be realized in a single functional block or by a single device.

Generally, a system architecture of a (tele)communication network including a mobile communication system where various example embodiments are applicable may include an architecture of one or more communication networks including wireless access network sub-/system(s) and possibly core network(s). Such an architecture may include one or more communication network control elements or functions, e.g., access network elements, radio access network elements, access service network gateways or base transceiver stations, like a base station, an access point, a NodeB (NB), an eNB or a gNB, a distributed or a centralized unit, which controls a respective coverage area or cell(s) and with which one or more communication stations such as communication elements or functions, like user devices or terminal devices, like a UE, or another device having a similar function, such as a modem chipset, a chip, a module etc., which can also be part of a station, an element, a function or an application capable of conducting a communication, such as a UE, an element or function usable in a machine-to-machine communication architecture, or attached as a separate element to such an element, function or application capable of conducting a communication, or the like, are capable to communicate via one or more channels via one or more communication beams for transmitting several types of data in a plurality of access domains.

Furthermore, core network elements or network functions, such as gateway network elements/functions, mobility management entities, a mobile switching center, servers, databases and the like may be included.

The general functions and interconnections of the described elements and functions, which also depend on the actual network type, are described, in -40 -certain example embodiments, in corresponding specifications, so that a detailed description thereof is omitted herein. It should be appreciated that several additional network elements and signaling links may be employed for a communication to or from an element, function or application, like a communication endpoint, a communication network control element, such as a server, a gateway, a radio network controller, and other elements of the same or other communication networks besides those described in detail herein below.

A communication network architecture, in various example embodiments, may also be able to communicate with other networks, such as a public switched telephone network or the Internet, including the Internet-ofThings. The communication network may also be able to support the usage of cloud services for virtual network elements or functions thereof, wherein it is to be noted that the virtual network part of the (tele)communication network can also be provided by non-cloud resources, e.g., an internal network or the like. It should be appreciated that network elements of an access system, of a core network etc., and/or respective functionalities may be implemented by using any node, host, server, access node or entity etc. being suitable for such a usage. Generally, a network function can be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure.

Any method step is suitable to be implemented as software or by hardware without changing the idea of the present disclosure. Such software may be software code independent and can be specified using any known or future developed programming language, e.g., Java, C++, C, and Assembler, as long as the functionality defined by the method steps is preserved. Such hardware may be hardware type independent and can be implemented using any known or future developed hardware technology or any hybrids of these, such as MOS (Metal Oxide Semiconductor), CMOS (Complementary MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter Coupled -41 -Logic), TTL (Transistor-Transistor Logic), etc., using for example ASIC (Application Specific IC (Integrated Circuit)) components, FPGA (Field-programmable Gate Arrays) components, CPLD (Complex Programmable Logic Device) components or DSP (Digital Signal Processor) components. A device/apparatus may be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of a device/apparatus or module, instead of being hardware implemented, be implemented as software in a (software) module, such as a computer program or a computer program product, comprising executable software code portions for execution/being run on a processor. A device may be regarded as a device/apparatus or as an assembly of more than one device/apparatus, whether functionally in cooperation with each other or functionally independently of each other but in a same device housing, for example.

Apparatuses and/or units/means or parts thereof can be implemented as individual devices, but this does not exclude that they may be implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved.

Software in at least one example embodiment comprises software code as such comprising code means or portions or a computer program or a computer program product for performing the respective functions, as well as software (or a computer program or a computer program product) embodied on a tangible medium such as a computer-readable (storage) medium having stored thereon a respective data structure or code means/portions or embodied in a signal or in a chip, potentially during processing thereof.

Various example embodiments also cover any combination of method steps and operations described above, and any combination of nodes, apparatuses, modules or elements described above, as long as the above-described concepts of methodology and structural arrangement are applicable.

-42 -In view of the above, there are provided measures for (e.g., enabling/realizing) message priority indication for subsequent communication in a mobile communication system. Such measures may, for example, comprise that an initiator entity specifies a message priority as a preferred or required priority for service-related messages relating to a service from a responder entity of the mobile communication system, and issues a request message relating to the service, including priority information indicative of the specified message priority, said priority information serving to indicate to the responder entity to apply the specified message priority for service-related messages relating to the service. Such measures may, for example, comprise that the responder entity obtains the priority information of the initiator entity, and utilizes the priority information to apply the message priority of the initiator entity for service-related messages relating to the service.

Even though various example embodiments are described above with reference to the accompanying drawings, it is to be understood that the various example embodiments are not restricted thereto. Rather, it is apparent to those skilled in the art that the various example embodiments can be modified in many ways without departing from the intended scope.

-43 -

Claims

Claims 1. A method of an initiator entity of a mobile communication system, the method comprising: specifying a message priority as a preferred or required priority for service-related messages relating to a service from a responder entity of the mobile communication system, and issuing a request message relating to the service, the request message including priority information indicative of the specified message priority, said priority information serving to indicate to the responder entity to apply the specified message priority for service-related messages relating to the service.
2. The method according to claim 1, wherein the priority information is included in a header of the request message or a payload of the request message.
3. The method according to claim 2, wherein when the priority information is included in a header, the header is a dedicated header for carrying the priority information, or when the priority information is included in a payload, the priority information is included in a dedicated section or information element for carrying the priority information in the payload.
4. The method according to any one of claims 1 to 3, wherein the priority information comprises or indicates at least one of the following: a priority value to be used by the responder entity for applying the specified message priority, a priority policy to be employed by the responder entity for deriving a priority value for applying the specified message priority, or a content value to be used by the responder entity for creating content of one or more parameters or information elements for applying the specified message priority.
-44 - 5. The method according to any one of claims 1 to 4, wherein the priority information comprises at least one of the following: transmission-specific priority information for application of the specified message priority in transmission of the service-related messages relating to the service by the responder entity, generation-specific priority information for application of the specified message priority in generation of the service-related messages relating to the service by the responder entity, or content-specific priority information for application of the specified message priority in creation of content of the service-related messages relating to the service by the responder entity.
6. The method according to claim 5, wherein the transmission-specific priority information is configured to affect a sequence of message transmission and/or a guidance for message handling in transfer from the responder entity to the initiator entity" and/or the generation-specific priority information is configured to affect a sequence of message generation and/or a selection of messages to be 20 generated, and/or the content-specific priority information is configured to affect the content of one or more parameters or information elements of messages.
7. The method according to any one of claims 1 to 6, wherein the request message relating to the service is or comprises a subscription request for subscribing to notifications with respect to the service, and the service-related messages are or comprise subscribed notifications with respect to the service.
8. The method according to claim 7, further comprising: sending the request message to the responder entity, and receiving the service-related messages from the responder entity.
-45 - 9. The method according to any one of claims 1 to 6, wherein the request message relating to the service is or comprises a registration request for registering service-related information of the initiator entity at the responder entity.
10. The method according to claim 9, wherein the priority information is registered as part of the service-related information of the initiator entity.
11. The method according to claim 9 or 10, wherein the service-related information of the initiator entity represents an implicit notification subscription with respect to the service, and the service-related messages are or comprise notifications with respect to the service based on the implicit notification subscription.
12. The method according to any one of claims 9 to 11, further comprising: sending the request message to the responder entity, and receiving the service-related messages from the responder entity.
13. The method according to any one of claims 1 to 6, wherein the request message relating to the service is or comprises a registration request for registering profile information of the initiator entity at a registry or repository entity.
14. The method according to claim 13, wherein the priority information is registered as part of the profile information of the initiator entity.
15. The method according to claim 13 or 14, wherein the profile information of the initiator entity relates to a default notification subscription with respect to the service, and the service-related messages are or comprise notifications with respect to the service based on the default notification subscription.
-46 - 16. The method according to any one of claims 13 to 15, further comprising: sending the request message to the registry or repository entity, and receiving the service-related messages from the responder entity.
17. The method according to any one of claims 1 to 16, wherein the initiator entity and the responder entity are involved in or based on a service-based architecture of the mobile communication system, and/or the initiator entity is or comprises a service consumer or any entity configured to consume or use at least the service, and/or the responder entity is or comprises a service producer or any entity configured to produce, expose and/or offer at least the service.
18. A method of a responder entity of a mobile communication system, the method comprising: obtaining priority information indicative of a message priority of an initiator entity of the mobile communication system, said message priority being specified by the initiator entity as a preferred or required priority for service-related messages relating to a service from the responder entity, and utilizing the priority information to apply the message priority of the initiator entity for service-related messages relating to the service.
19. The method according to claim 18, wherein the priority information comprises or indicates a priority value, and utilizing the priority information comprises using the priority value for applying the message priority of the initiator entity, and/or the priority information comprises or indicates a priority policy, and utilizing the priority information comprises employing the priority policy for deriving a priority value for applying the message priority of the initiator entity, and/or -47 -the priority information comprises or indicates a content value, and utilizing the priority information comprises creating content of one or more parameters or information elements for applying the message priority of the initiator entity.
20. The method according to claim 19, wherein utilizing the priority information comprises: assigning the priority value to the service-related messages relating to the service, and/or including the content in the service-related messages relating to the service.
21. The method according to any one of claims 18 to 20, wherein the priority information comprises transmission-specific priority information, and utilizing the priority information comprises applying the message priority of the initiator entity in transmission of the service-related messages relating to the service, and/or the priority information comprises generation-specific priority information, and utilizing the priority information comprises applying the message priority of the initiator entity in generation of the service-related messages relating to the service, and/or the priority information comprises content-specific priority information, and utilizing the priority information comprises applying the message priority of the initiator entity in creation of content of the service-related messages relating to the service.
22. The method according to claim 21, wherein when applying the message priority of the initiator entity in transmission of the service-related messages relating to the service, a 30 sequence of message transmission and/or a guidance for message handling in transfer from the responder entity to the initiator entity, and/or when applying the message priority of the initiator entity in generation of the service-related messages relating to the service, a -48 -sequence of message generation and/or a selection of messages to be generated, and/or when applying the message priority of the initiator entity in creation of content of the service-related messages relating to the service, the 5 content of one or more parameters or information elements of messages.
23. The method according to any one of claims 18 to 22, further comprising: determining applicability of the message priority of the initiator entity for service-related messages relating to the service, wherein the priority information is utilized to apply the message priority of the initiator entity for service-related messages relating to the service when the applicability is affirmed, and a local policy or configuration is utilized to apply a message priority other than the message priority of the initiator entity or apply no message priority for service-related messages relating to the service when the applicability is denied.
24. The method according to any one of claims 18 to 23, further comprising: storing the priority information.
25. The method according to any one of claims 18 to 24, further comprising: receiving a request message relating to the service from the initiator entity, the request message including the priority information, wherein the priority information is obtained from the request message, and sending the service-related messages to the initiator entity.
26. The method according to claim 25, wherein the priority information is included in a header of the request message or a payload of the request message.
27. The method according to claim 26, wherein -49 -when the priority information is included in a header, the header is a dedicated header for carrying the priority information, or when the priority information is included in a payload, the priority information is included in a dedicated section or information element for carrying the priority information in the payload.
28. The method according to any one of claims 25 to 27, wherein the request message relating to the service is or comprises a subscription request for subscribing to notifications with respect to the service, and the service-related messages are or comprise subscribed notifications with respect to the service.
29. The method according to any one of claims 25 to 27, wherein the request message relating to the service is or comprises a registration request for registering service-related information of the initiator entity at the responder entity.
30. The method according to claim 29, wherein the priority information is registered as part of the service-related information of the initiator entity.
31. The method according to claim 29 or 30, wherein the service-related information of the initiator entity represents an implicit notification subscription with respect to the service, and the service-related messages are or comprise notifications with respect to the service based on the implicit notification subscription.
32. The method according to any one of claims 18 to 24, further comprising: acquiring profile information of the initiator entity from a registry or repository entity, wherein the priority information is part of and obtained from the profile information of the initiator entity, and sending the service-related messages to the initiator entity.
-50 - 33. The method according to claim 32, wherein the profile information of the initiator entity relates to a default notification subscription with respect to the service, and the service-related messages are or comprise notifications with respect to the service based on the default notification subscription.
34. The method according to any one of claims 18 to 33, wherein the initiator entity and the responder entity are involved in or based on a service-based architecture of the mobile communication system, and/or the initiator entity is or comprises a service consumer or any entity configured to consume or use at least the service, and/or the responder entity is or comprises a service producer or any entity configured to produce, expose and/or offer at least the service.
35. An apparatus of an initiator entity of a mobile communication system, the apparatus comprising: means for specifying a message priority as a preferred or required priority for service-related messages relating to a service from a responder entity of the mobile communication system, and means for issuing a request message relating to the service, the request message including priority information indicative of the specified message priority, said priority information serving to indicate to the responder entity to apply the specified message priority for service-related messages relating to the service.
36. The apparatus according to claim 35, wherein the priority information is included in a header of the request message or a payload of the request 30 message.
37. The apparatus according to claim 36, wherein when the priority information is included in a header, the header is a dedicated header for carrying the priority information, or -51 -when the priority information is included in a payload, the priority information is included in a dedicated section or information element for carrying the priority information in the payload.
38. The apparatus according to any one of claims 35 to 37, wherein the priority information comprises or indicates at least one of the following: a priority value to be used by the responder entity for applying the specified message priority, a priority policy to be employed by the responder entity for deriving a priority value for applying the specified message priority, or a content value to be used by the responder entity for creating content of one or more parameters or information elements for applying the specified message priority.
39. The apparatus according to any one of claims 35 to 38, wherein the priority information comprises at least one of the following: transmission-specific priority information for application of the specified message priority in transmission of the service-related messages relating to the service by the responder entity, generation-specific priority information for application of the specified message priority in generation of the service-related messages relating to the service by the responder entity, or content-specific priority information for application of the specified message priority in creation of content of the service-related messages relating to the service by the responder entity.
40. The apparatus according to claim 39, wherein the transmission-specific priority information is configured to affect a sequence of message transmission and/or a guidance for message handling in transfer from the responder entity to the initiator entity, and/or the generation-specific priority information is configured to affect a sequence of message generation and/or a selection of messages to be generated, and/or -52 -the content-specific priority information is configured to affect the content of one or more parameters or information elements of messages.
41. The apparatus according to any one of claims 35 to 40, wherein the request message relating to the service is or comprises a subscription request for subscribing to notifications with respect to the service, and the service-related messages are or comprise subscribed notifications with respect to the service.
42. The apparatus according to claim 41, further comprising: means for sending the request message to the responder entity, and means for receiving the service-related messages from the responder entity.
43. The apparatus according to any one of claims 35 to 40, wherein the request message relating to the service is or comprises a registration request for registering service-related information of the initiator entity at the responder entity.
44. The apparatus according to claim 43, wherein the priority information is registered as part of the service-related information of the initiator entity.
45. The apparatus according to claim 43 or 44, wherein the service-related information of the initiator entity represents an implicit notification subscription with respect to the service, and the service-related messages are or comprise notifications with respect to the service based on the implicit notification subscription.
46. The apparatus according to any one of claims 43 to 45, further comprising: means for sending the request message to the responder entity, and -53 -means for receiving the service-related messages from the responder entity.
47. The apparatus according to any one of claims 35 to 40, wherein the request message relating to the service is or comprises a registration request for registering profile information of the initiator entity at a registry or repository entity.
48. The apparatus according to claim 47, wherein the priority information is registered as part of the profile information of the initiator entity.
49. The apparatus according to claim 47 or 48, wherein the profile information of the initiator entity relates to a default notification subscription with respect to the service, and the service-related messages are or comprise notifications with respect to the service based on the default notification subscription.
50. The apparatus according to any one of claims 47 to 49, further comprising: means for sending the request message to the registry or repository entity, and means for receiving the service-related messages from the responder entity.
51. The apparatus according to any one of claims 35 to 50, wherein the initiator entity and the responder entity are involved in or based on a service-based architecture of the mobile communication system, and/or the initiator entity is or comprises a service consumer or any entity configured to consume or use at least the service, and/or the responder entity is or comprises a service producer or any entity configured to produce, expose and/or offer at least the service.
-54 - 52. An apparatus of a responder entity of a mobile communication system, the apparatus comprising: means for obtaining priority information indicative of a message priority of an initiator entity of the mobile communication system, said message priority being specified by the initiator entity as a preferred or required priority for service-related messages relating to a service from the responder entity, and means for utilizing the priority information to apply the message priority of the initiator entity for service-related messages relating to the 10 service.
53. The apparatus according to claim 52, wherein the priority information comprises or indicates a priority value, and utilizing the priority information comprises using the priority value for applying the message priority of the initiator entity, and/or the priority information comprises or indicates a priority policy, and utilizing the priority information comprises employing the priority policy for deriving a priority value for applying the message priority of the initiator entity, and/or the priority information comprises or indicates a content value, and utilizing the priority information comprises creating content of one or more parameters or information elements for applying the message priority of the initiator entity.
54. The apparatus according to claim 53, wherein utilizing the priority information comprises: assigning the priority value to the service-related messages relating to the service, and/or including the content in the service-related messages relating to the 30 service.
55. The apparatus according to any one of claims 52 to 54, wherein -55 -the priority information comprises transmission-specific priority information, and utilizing the priority information comprises applying the message priority of the initiator entity in transmission of the service-related messages relating to the service, and/or the priority information comprises generation-specific priority information, and utilizing the priority information comprises applying the message priority of the initiator entity in generation of the service-related messages relating to the service, and/or the priority information comprises content-specific priority information, and utilizing the priority information comprises applying the message priority of the initiator entity in creation of content of the service-related messages relating to the service.
56. The apparatus according to claim 55, wherein when applying the message priority of the initiator entity in transmission of the service-related messages relating to the service, a sequence of message transmission and/or a guidance for message handling in transfer from the responder entity to the initiator entity, and/or when applying the message priority of the initiator entity in generation of the service-related messages relating to the service, a sequence of message generation and/or a selection of messages to be generated, and/or when applying the message priority of the initiator entity in creation of content of the service-related messages relating to the service, the 25 content of one or more parameters or information elements of messages.
57. The apparatus according to any one of claims 52 to 56, further comprising: means for determining applicability of the message priority of the initiator entity for service-related messages relating to the service, wherein the priority information is utilized to apply the message priority of the initiator entity for service-related messages relating to the service when the applicability is affirmed, and a local policy or configuration -56 -is utilized to apply a message priority other than the message priority of the initiator entity or apply no message priority for service-related messages relating to the service when the applicability is denied.
58. The apparatus according to any one of claims 52 to 57, further comprising: means for storing the priority information.
59. The apparatus according to any one of claims 52 to 58, further 10 comprising: means for receiving a request message relating to the service from the initiator entity, the request message including the priority information, wherein the priority information is obtained from the request message, and means for sending the service-related messages to the initiator entity.
60. The apparatus according to claim 59, wherein the priority information is included in a header of the request message or a payload of the request message.
61. The apparatus according to claim 60, wherein when the priority information is included in a header, the header is a dedicated header for carrying the priority information, or when the priority information is included in a payload, the priority information is included in a dedicated section or information element for carrying the priority information in the payload.
62. The apparatus according to any one of claims 59 to 61, wherein the request message relating to the service is or comprises a subscription request for subscribing to notifications with respect to the service, and the service-related messages are or comprise subscribed notifications with respect to the service.
-57 - 63. The apparatus according to any one of claims 59 to 61, wherein the request message relating to the service is or comprises a registration request for registering service-related information of the initiator entity at the responder entity.
64. The apparatus according to claim 60, wherein the priority information is registered as part of the service-related information of the initiator entity.
65. The apparatus according to claim 63 or 64, wherein the service-related information of the initiator entity represents an implicit notification subscription with respect to the service, and the service-related messages are or comprise notifications with respect to the service based on the implicit notification subscription.
66. The apparatus according to any one of claims 52 to 60, further comprising: means for acquiring profile information of the initiator entity from a registry or repository entity, wherein the priority information is part of and obtained from the profile information of the initiator entity, and means for sending the service-related messages to the initiator entity.
67. The apparatus according to claim 66, wherein the profile information of the initiator entity relates to a default notification subscription with respect to the service, and the service-related messages are or comprise notifications with respect to the service based on the default notification subscription.
68. The apparatus according to any one of claims 52 to 67, wherein the initiator entity and the responder entity are involved in or based on a service-based architecture of the mobile communication system, and/or -58 -the initiator entity is or comprises a service consumer or any entity configured to consume or use at least the service, and/or the responder entity is or comprises a service producer or any entity configured to produce, expose and/or offer at least the service.
69. A computer program product comprising computer program code which, when the computer program code is executed on a computer, is configured to cause the computer to carry out the method according to any one of claims 1 to 17 or the method according to any one of claims 18 to 34.-59 -