Method, user equipment, telecommunications network and computer-readable medium for operating user equipment or modifying the operation of the user equipment

Abstract

The present invention relates to a method for operating or modifying the operation of a user equipment within or as part of a telecommunications network, wherein the operation of the user equipment or the modification of the operation is performed using control plane functionality, wherein the telecommunications network comprises or is associated with or assigned to an access network and a core network, wherein the core network provides data connectivity towards a data network for the user equipment, wherein the user equipment comprises or provides at least one functional and addressable service endpoint for providing or exposing a service or functionality to a requester entity or requester network node external to the user equipment, wherein the requester entity or requester network node is part of the access network or the core network, wherein the service endpoint is associated with or corresponds to the control plane functionality, and wherein the service endpoint as or associated with the control plane functionality is communicated via A control plane channel communicates with or is accessible to a control plane network element of a telecommunications network, wherein, in order to operate a user equipment or modify the operation of the user equipment and in view of a specific service or specific functionality being provided by a specific service endpoint of the user equipment to a requesting entity or a requesting network node, the method comprises the following steps: - in a first step, the user equipment receives a request message from or on behalf of the requesting entity or the requesting network node, the request message being related to the specific service endpoint and wherein the request message - relates to or uses specific application programming interface functionality provided by the specific service endpoint and / or - relates to or includes specific address information related to the specific service endpoint, - in a second step, the specific service endpoint processes the received request message according to its content.

Description

Background Art

[0001] The present invention relates to a method for operating or modifying the operation of a user equipment within or as part of a telecommunications network, wherein the operation of the user equipment or the modification of the operation is performed using control plane functionality, wherein the user equipment comprises or provides at least one functional and addressable service endpoint for providing or exposing services or functionality to a requestor entity or requestor network node external to the user equipment, wherein the requestor entity or requestor network node is part of an access network or a core network.

[0002] Furthermore, the present invention relates to a user equipment for being operated or applying a modified mode of operation within or as part of a telecommunications network, wherein the operation of the user equipment or the modification of the operation is performed using control plane functionality, wherein the user equipment comprises or provides at least one functional and addressable service endpoint for providing or exposing services or functionality to a requestor entity or a requestor network node external to the user equipment, wherein the requestor entity or the requestor network node is part of an access network or a core network.

[0003] Additionally, the present invention relates to a system or a telecommunications network for operating or modifying the operation of a user equipment within or as part of a telecommunications network, wherein the operation of the user equipment or the modification of the operation is performed using control plane functionality, wherein the user equipment comprises or provides at least one functional and addressable service endpoint for providing or exposing services or functionality to a requestor entity or requestor network node external to the user equipment, wherein the requestor entity or requestor network node is part of an access network or a core network.

[0004] Furthermore, the invention relates to a program and a computer-readable medium for operating or modifying the operation of user equipment within or as part of a telecommunications network according to the method according to the invention.

[0005] In conventionally known telecommunications networks, the functionality and / or current or future operating mode of user equipment (within or as part of the telecommunications network) is typically accessible via the so-called control plane (i.e., by using control plane functionality or mechanisms)—in particular, control plane network elements of the telecommunications network exchange messages with relevant parts of the user equipment according to the control plane protocol stack—and the user equipment, in particular, its functional parts, elements, or modules, can be configured to implement a certain behavior or to operate in a certain manner. The functionality of the user equipment (i.e., how the user equipment is operated or configured, or how its operating mode can be modified) is also conventionally accessible via the so-called user plane (i.e., a non-control plane), however, this is essentially "over the top" (OTT) rather than through the use of the control plane. In order to use the control plane functionality or mechanisms to configure the user equipment (or modify its configuration), the core network entity (i.e., the network elements of the core network of the telecommunications network) is aware that messages intended for the user equipment need to be sent via a control plane element (e.g., an access and mobility management function in, for example, a 5G network (as part of the core network)). The access and mobility management function responsible for a given connected user equipment can be found by querying the unified data management (corresponding to the home subscriber server in 4G), as the access and mobility management function responsible for each registered user equipment is registered there as part of the user equipment's network registration procedure. For example, the following messages or message types are tunneled by the access and mobility management function via non-access stratum mechanisms or messages: user equipment - session management function, user equipment - policy and charging function, user equipment - unified data management (e.g., user equipment parameter update UPU). Conventionally, each message container is uniquely identified by a non-access stratum message type, which indicates to the receiving user equipment which functionality / code / function is responsible for decoding the message. Therefore, there is conventionally a fixed 1:1 relationship between non-access stratum message types and message destinations, and it is generally not possible to have multiple instances of the same destination type (e.g., to explicitly support addressing / operating on multiple credential stores or application programming interfaces for directing UE behavior).

[0006] Additionally, in conventional telecommunication networks, the manner in which user equipment parameters are accessed and / or modified (i.e., how the user equipment is configured or its operation is modified) is variable-based, i.e., certain variables can be read / written by the (user equipment's) home public land mobile network HPLMN and / or visited public land mobile network VPLMN, i.e., a parameter read / write request (of known parameters) is transmitted by the access and mobility management function via the gNB (or base station entity of the user equipment) to the user equipment in question, and the read / write operation result is transmitted back by the user equipment. Therefore, the manner in which user equipment parameters are accessed and / or modified is quite static (based on 3GPP specifications, which include parameter lists and parameter classifications in HPLMN and / or VPLMN parameters). Summary of the Invention

[0007] The present invention aims to provide a technically simple, efficient and cost-effective solution for operating or modifying the operation of a user equipment within or as part of a telecommunications network, wherein the operation of the user equipment or the modification of the operation is performed using control plane functionality. A further object of the present invention is to provide corresponding user equipment, a system or mobile communications network, user equipment service endpoint registration functionality, and corresponding programs and computer-readable media.

[0008] The object of the present invention is achieved by a method for operating or modifying the operation of a user equipment within or as part of a telecommunications network, wherein the operation of the user equipment or the modification of the operation is performed using control plane functionality,

[0009] wherein the telecommunications network comprises or is associated with or assigned to an access network and a core network, wherein the core network provides data connectivity towards a data network (e.g., the Internet) to the user equipment,

[0010] wherein the user equipment comprises or provides at least one functional and addressable service endpoint for providing or exposing services or functionality to a requestor entity or requestor network node external to the user equipment, wherein the requestor entity or requestor network node is part of an access network or a core network,

[0011] wherein the service endpoint is associated with or corresponds to a control plane functionality, and wherein the service endpoint being or associated with the control plane functionality communicates with or is accessible to a control plane network element of the telecommunications network via a control plane channel,

[0012] In order to operate a user equipment or modify the operation of the user equipment, and in view of providing a specific service or specific functionality to a requesting entity or a requesting network node by a specific service endpoint of the user equipment, the method comprises the following steps:

[0013] In a first step, the user equipment receives a request message from or on behalf of a requesting entity or a requesting network node, the request message being related to a specific service endpoint, and wherein the request message

[0014] --Relates to or uses specific API functionality provided by a specific service endpoint

[0015] and / or

[0016] --relating to or including specific address information associated with a specific service endpoint,

[0017] --In the second step, the specific service endpoint processes the received request message according to its content.

[0018] Thus, according to the present invention, it is advantageously possible to configure user equipment (i.e., to operate the user equipment in a certain manner) and / or to modify the operation of the user equipment in a much more flexible manner than conventionally known. Furthermore, it is advantageously possible to apply the principles of the present invention to the case of user equipment having a more complex structure or functionality, in particular including or providing a plurality of different service endpoints for providing or exposing similar services or functionality. Alternatively or cumulatively, according to the present invention, it is also advantageously possible to access such service endpoints in a more flexible manner than based solely on variables.

[0019] According to the present invention, the operation (or operating mode) of a user equipment (within or as part of a telecommunications network) should be defined and / or influenced and / or modified in a relatively easy, flexible, forward-looking (or modification-proof) manner. According to the present invention, the operation (or operating mode) is defined (or the modification of the operation of the user equipment is performed) using control plane functionality (i.e., in particular not user plane functionality (and in particular not user plane functionality alone (i.e., without any control plane involvement))).

[0020] A telecommunications network typically includes an access network and a core network. However, the present invention also relates to the following situations: strictly speaking, the telecommunications network does not include the access network and the core network, but rather the telecommunications network is associated with or assigned to the access network only (and in particular includes the core network), or the telecommunications network is associated with or assigned to the core network only (and in particular includes the access network), or the telecommunications network is associated with or assigned to both the access network and the core network. According to the present invention, the core network provides data connectivity to the user equipment towards the data network.

[0021] According to the present invention, a user equipment comprises or provides at least one functional and addressable service endpoint for providing or exposing a service or functionality to a requestor entity or requestor network node external to the user equipment, the requestor entity or requestor network node being part of an access network or a core network. Generally, according to the present invention, a user equipment comprises a plurality of functional and addressable service endpoints for providing or exposing a service or functionality to a requestor entity or requestor network node external to the user equipment; in particular, any functional or logical part, module or entity within or associated with the user equipment, such as one or more subscriber identity modules, subscriptions or parameters / configurations capable of being defined and / or modified.

[0022] According to the present invention, the service endpoint is associated with or corresponds to control plane functionality, and the service endpoint—being or associated with control plane functionality—communicates with or is accessible to control plane network element(s) of the telecommunications network via a control plane channel. In particular, the control plane element corresponds to the access and mobility management functions of the core network, and the control plane channel corresponds to the interface between the user equipment and the control plane element, i.e., the signaling channel. According to the present invention, this is in contrast to the use of user plane functionality, for example, between a user equipment application and a data network.

[0023] According to an embodiment of the present invention, the method comprises (for operating a user equipment or modifying the operation of the user equipment and in view of providing a specific service or specific functionality to a requesting entity or a requesting network node by a specific service endpoint of the user equipment):

[0024] - in a first step, the user equipment receives a request message from or on behalf of a requesting entity or a requesting network node, the request message relating to a specific service endpoint and the request message involving or using a specific application programming interface functionality provided by the specific service endpoint, and

[0025] - In a second step, the specific service endpoint processes the received request message according to its content, ie the content of the request message specifically corresponds to an application programming interface call related to or intended to be received (and processed) by the specific service endpoint.

[0026] According to a further embodiment of the invention, the method comprises (for operating a user equipment or modifying the operation of the user equipment and in view of providing a specific service or specific functionality to a requesting entity or a requesting network node by a specific service endpoint of the user equipment):

[0027] - in a first step, the user equipment receives a request message from or on behalf of a requesting entity or a requesting network node, the request message being related to a specific service endpoint and the request message relating to or including specific address information related to the specific service endpoint, and

[0028] --In a second step, the specific service endpoint processes the received request message according to its content, i.e., the content of the request message specifically includes specific address information, with the help of which the specific service endpoint can be specifically addressed, even in the case where the specific service endpoint is one of multiple service endpoints of the same kind or nature (such as different instances of the same service or functionality).

[0029] According to yet another further embodiment of the present invention, the method comprises (for operating a user equipment or modifying the operation of the user equipment and in view of providing a specific service or specific functionality to a requesting entity or a requesting network node by a specific service endpoint of the user equipment):

[0030] - in a first step, the user equipment receives a request message from or on behalf of a requesting entity or a requesting network node, the request message relating to a specific service endpoint and the request message involving (or using or including) both specific application programming interface functionality provided by the specific service endpoint and specific address information relating to the specific service endpoint, and

[0031] --In a second step, the specific service endpoint processes the received request message according to its content, i.e., the content of the request message specifically corresponds to an application programming interface call involving or intended to be received (and processed) by the specific service endpoint and includes specific address information, by means of which the specific service endpoint can be specifically addressed.

[0032] In particular, in situations where the request message relates to or uses specific application programming interface functionality provided by a specific service endpoint, the following advantages can be achieved:

[0033] -- Advantageously, a modular functional representation of a user equipment can be implemented as a service producer in the form of exposed application programming interfaces, which can be addressed by (an entity or network element of) the core network and / or (an entity or network element of) the radio access network and / or (an entity or network element of) a third party (e.g., a hyperscale cloud service provider, an application provider, an enterprise) to interact with certain user equipment and use the functionality exposed by them (in 3GPP terminology, the entity that calls the application programming interface is called a consumer (who consumes the result), and the entity that exposes the functionality via the application programming interface (i.e., in the context of the present invention: the user equipment) is the producer; in order to implement notifications, corresponding messages are transmitted from the user equipment to the consumer).

[0034] Advantageously, exposure of an application programming interface endpoint to a radio resource control and / or to a non-access layer and / or to a third party entity via a network exposure function may be provided.

[0035] --In particular, cross-layer access to (application programming interface) functionality of a service endpoint of a user equipment (or within a user equipment or as part of a user equipment) may advantageously be achieved (e.g., the same application programming interface can be exposed at the radio resource control layer and the non-access layer).

[0036] Furthermore, it is advantageous to flexibly authorize certain APIs depending on the trust level (i.e., a flexible delegated service-based authorization model). For example, a visited PLMN may be able to operate on certain user equipment APIs (e.g., read only, change only certain parameters), while a home PLMN may have broader access. This also enables, for example, multiple instances of a given API (or multiple instances of a given (type of) service endpoint) applicable to different subscriptions to be accessible to each subscription owner (e.g., PLMN) (e.g., if there is an agreement between them).

[0037] --In particular, according to the present invention it is advantageously possible, in particular in cases where a request message relates to or uses a specific application programming interface functionality provided by a specific service endpoint, that one or more of the following already existing functionalities (in particular regarding the definition and / or modification of parameters) are operated via an application programming interface (provided by a service endpoint in the user equipment) instead of the current model of reading or reading / writing of (parameter) variables, in particular based on the following non-access layer messages: IP Multimedia Subsystem (IMS) Management Objects (MO), User Equipment Routing Policy (URSP) (which allows traffic within the user equipment to be routed to a specific destination), parameters stored in the Universal Subscriber Identity Module (USIM) and the Mobile Equipment (ME) (for example, some parameters used in a Standalone Non-Public Network (SNPN) do not require a SIM card; for example, a specific example is the SNPN certificate), procedures supported by the Mobile Equipment (ME), Over-the-Air (OTA) procedures (such as device updates).

[0038] According to the present invention, it is further advantageous that the user equipment is able to communicate with the core network (in particular the 5G core) and / or with the functional entities using a service-based infrastructure (e.g. instead of non-access stratum messages).

[0039] In particular, in the case where the request message involves or includes specific address information related to a specific service endpoint, the following advantages can be achieved:

[0040] -- Advantageously, the possibility can be provided to modularly separate user equipment and / or local devices (e.g. SIM cards), functional entities or service endpoints (in particular providing services accessible via different application programming interfaces) with different parameters, and still be able to address each one (in particular each instance) separately by means of dynamically locating their destination (e.g. the destination of each instance); in conventional known telecommunication networks, it is currently not possible to dynamically locate the destination of tunneled messages.

[0041] --Furthermore, new user equipment functionality can advantageously be added without requiring changes to the non-access stratum protocol and / or other protocol changes; thus, this makes it possible to define a "baseline" that essentially contains no functionality and dynamically add further functionality on top of it without backward compatibility issues.

[0042] --In particular, such addressing can be advantageously used to enable API-based exposure of user equipment services, i.e., where in addition to the request message relating to or including specific address information associated with a specific service endpoint, the request message also relates to or uses specific application programming interface functionality provided by a specific service endpoint.

[0043] -- Additionally, non-API (service) endpoints can advantageously be added within the user equipment, such as, for example, SIM devices, variables within the user equipment device, etc.

[0044] -- Additionally, the access and mobility management function as signaling anchor can advantageously be further simplified so that signaling flows more directly between the actual functional entities involved (e.g., especially in the case of non-3GPP access, where currently everything flows via the access and mobility management function and then towards the user plane functions).

[0045] In particular, in situations where the request message relates to or uses a specific application programming interface functionality provided by a specific service endpoint and relates to or includes specific address information associated with the specific service endpoint, the following advantages may be achieved:

[0046] -- Advantageously, addressing (ie, address information) can be used to enable API-based exposure of user equipment services.

[0047] Conventionally known telecommunications networks typically include an access network and a core network, with user equipment connected to the access network and the access network connected to the core network. User equipment can connect to a data network via the core network. User equipment typically communicates with the access network (or radio access network) via an interface (typically a radio interface). This is used to convey both signaling information and data traffic, but there is typically a logical separation (logical channels) for the transmission of these two types of traffic. Between the access network (particularly the radio access network, and in particular the gNB base station entity) and the core network, signaling information and user data are separated across different interfaces (e.g., N1 / N2 and N3 in the 5G case); signaling traffic or information (in the core network, typically handled by access and mobility management functions) is typically transported using the SCTP / NG-AP / NAS protocol stack, and user data (in the core network, typically handled by user plane functions) is typically transported using the UDP / GTPU-U protocol stack. Conventionally, there are typically different levels of signaling (per protocol), each with a different anchor (e.g., NAS / N1 between the user equipment and the core network, and RC between the user equipment and the access network or radio access network). Different logical control plane links can be tunneled between each link, with intermediate (network) elements playing only a forwarding role. A similar approach is implemented for the user plane.

[0048] To establish a data connection that enables a user equipment to communicate with a data network, a Protocol Data Unit (PDU) session is required. A PDU session is a logical data transmission channel that terminates at the core network, providing connectivity to the data network. The termination point for a given PDU session (e.g., a user plane function according to the 5G standard) is called a PDU Session Anchor (PSA). The PDU Session Anchor is generally and typically expected to remain constant as the user equipment moves (e.g., during handover procedures between the user equipment and different gNB or base station entities). A PDU session may have one or more associated qualities of service (e.g., one or more QoS flows within the PDU session) for the underlying transport data.

[0049] In conventional known telecommunication networks, it is possible to communicate with terminal applications (within, i.e. running on, the user equipment) via the user plane (over-the-top (OTT)). However, the purpose according to the present invention is to access the user equipment itself (i.e., not via an Internet Protocol (IP) address accessible via a PDU session created for the data network connectivity of the user equipment, for example). In such an OTT scenario, an application installed on the user equipment can communicate with a third-party OTT (e.g., connected to or providing a data network) and then interact locally with the user equipment (e.g., via AT commands (Hayes command set or ITU V.250 standard) or a similar local interface (usually proprietary)).

[0050] Typically, in conventional telecommunications networks, how user equipment parameters are accessed and / or modified (i.e., how the user equipment is configured or its operation is modified) is variable-based. Specifically, (similar to how the Simple Network Management Protocol (SNMP) works) certain variables can be read / written by the user equipment's home public land mobile network (HPLMN) and / or visited public land mobile network (VPLMN). This involves the access and mobility management function transmitting a parameter read / write request (for known parameters) to the user equipment in question via the gNB (or base station entity of the user equipment), and the user equipment transmitting the read / write result back. Access permissions are static (based on 3GPP specifications). Conventionally, only the core network (or a network element of the core network) is allowed to parameterize user equipment, as only the core network has a security context that allows secure communication with the user equipment via or using the non-access stratum protocol. This read / write variable access is always accomplished via the access and mobility management function. Depending on the parameters being accessed, the access and mobility management function may only forward secure messages (e.g., guidance of roaming (for the user equipment) authenticated by unified data management). However, such messages may also ultimately come from a third party outside the core network (of the telecommunications network), i.e., via an intermediate network function such as a network exposure function. In either case, the communication is always achieved via the access and mobility management function, and the radio access network-user equipment communication layer (radio resource control RRC) has no access to this information exchange.

[0051] In contrast, within the core network (particularly the 5G core network), network functions are accessed via application programming interface (API) calls, where available APIs are registered on the network repository function so that they can be discovered by other network functions. The API means that the operations that can be called are defined based on an API description that describes the operation (e.g., add, delete, query, subscribe, notify), parameters (mandatory, optional, allowed values), expected output, and any necessary data structures, so that the definition of functionality is self-contained in the API definition and machine-readable.

[0052] Currently, only network functions can access application programming interfaces in the core network (especially the 5G core network).

[0053] According to the present invention, the user equipment itself can expose one or more application programming interfaces that can be accessed by network functions or network elements of the telecommunications network. The exchange of information related to the application programming interfaces is performed via a control plane channel (for example, integrating a general structure similar to or equivalent to the HTTP protocol within the non-access layer protocol).

[0054] According to the present invention, it is advantageously possible and preferred that the telecommunication network comprises a user equipment service endpoint registration functionality, wherein in a third step prior to the first step, endpoint related information fragments regarding:

[0055] -- API functionality for specific service endpoints and / or

[0056] -- address information related to a specific service endpoint, in particular, information about a specific instance of a specific service endpoint,

[0057] being provided with user equipment service endpoint registration functionality and in particular being exposed thereby for use by other nodes or instances of the telecommunications network,

[0058] The endpoint-related information segment specifically enables the user equipment service endpoint registration functionality to implement at least one of the following:

[0059] --Register a specific application programming interface provided by a specific service endpoint,

[0060] -- provide address information about how a specific service endpoint can be accessed, in particular address information about a specific instance of a specific service endpoint,

[0061] wherein in particular endpoint-related information—information about service endpoints exposed by a user equipment—can be provided to a plurality of requester entities or requester network nodes, in particular third-party network functions, by means of user equipment service endpoint registration functionality.

[0062] Therein, in particular, the user equipment service endpoint registration functionality is part of an access network of the telecommunication network or part of a core network of the telecommunication network.

[0063] By registering functionality with the user equipment service endpoint, the user equipment provides endpoint-related information fragments regarding:

[0064] -- API functionality for specific service endpoints and / or

[0065] -- address information related to a specific service endpoint, in particular, information about a specific instance of a specific service endpoint,

[0066] According to the invention it is advantageously possible that, by means of the endpoint related information fragment, application programming interface functionality of a specific service endpoint and / or address information related to the specific service endpoint is exposed for use by other nodes or instances (or network elements) of the telecommunication network.

[0067] This means that according to this embodiment of the invention (wherein the telecommunications network comprises user equipment service endpoint registration functionality, and wherein in the third step the endpoint-related information fragment is provided by the user equipment), the endpoint-related information fragment is related to the application programming interface functionality of the specific service endpoint, or to the address information about the specific service endpoint, or to both the application programming interface functionality of the specific service and the address information about the specific service endpoint. According to the invention, the latter possibility is also possible in that the first endpoint-related information fragment is related to the application programming interface functionality of the specific service, and the second endpoint-related information fragment is related to the address information about the specific service endpoint.

[0068] In particular, according to such embodiments of the present invention, it is advantageously possible (in situations where the endpoint-related information fragment is related to an application programming interface functionality of a specific service) that the user equipment is implemented to register the exposed (i.e. available) application programming interfaces of the available services (i.e. available service endpoints) into a user equipment service endpoint registration functionality, which serves as a registration function accessible via the radio access network and / or core network (and / or third-party network elements), enabling such network elements (or radio access network / core / third-party components) to query the corresponding user equipment service endpoint (or multiple service endpoints) matching specific parameters and communicate with them.

[0069] This also makes it advantageously possible according to the present invention (in cases where the endpoint-related information piece is related to the API functionality of a specific service) that a third-party entity (e.g. an application provider (such as for example Netflix) or a hyperscale cloud provider (such as for example Google or Facebook), or an enterprise network) is implemented to register the API endpoint in the telecommunications network so that other network components can find it and interact with it.

[0070] Furthermore, according to the present invention, it is also advantageously possible (in the case where the endpoint-related information piece is related to the API functionality of a specific service) for a third party (e.g., exposing functionality via a network) to be enabled to access the API exposed by the user equipment based on specific parameters (e.g., only user equipment supporting the "Netflix API").

[0071] Furthermore, according to the present invention, it is advantageously possible (in the case where the endpoint-related information piece is related to the application programming interface functionality of a specific service) to allow the implementation or creation of a relationship within the telecommunication network between what a subscription is allowed to do (knowledge about what a subscription is allowed to do is usually already available in conventionally known telecommunication networks) and what a user equipment can do (or is capable of doing); in conventionally known telecommunication networks, this latter knowledge is not available, or at least not fully available; essentially, this relationship between what a subscription is allowed to do and what a user equipment can do allows, in particular, the implementation of a flexible authorization model based on delegated services within the telecommunication network.

[0072] The exposure of the application programming interface - by means of using the user equipment service endpoint registration functionality and the corresponding endpoint related information fragments - also provides the possibility to more easily define device classes and the exposure of device capabilities: according to the present invention, instead of a set of explicit device classes (currently used in conventional known telecommunication networks), a device can be defined by a set of services and service information that it registers as supported in the network (i.e. registered to the user equipment service endpoint registration functionality).

[0073] Additional advantages are as follows:

[0074] -- May allow for a more simplified user equipment registration procedure, as network attachments can be reduced to a minimum and service registration can then be separated (and even performed separately via PDU sessions)

[0075] --Register a single subscriber on multiple devices, where it is clear to the network what each device supports (e.g. one user equipment may support IP Multimedia Subsystem while another does not), and therefore only the relevant user equipments are paged; in short: allowing an explicit 1:N relationship between "registered subscribers" and "registered user equipments".

[0076] -- Modular addition of new services without extending the N1 interface (currently every available information element needs to be explicitly defined in the NAT specification), e.g. "Netflix API".

[0077] --Applications / enablement (IMS, Facebook, Google, etc.), user device capabilities (voice, data, operating system, download, IoT / machine type communication capabilities).

[0078] --Interaction with a third party via an application programming interface exposed by the user equipment (e.g., via an intermediary element that exposes similar network functionality) so that the third party can operate and / or be notified when certain triggers are set (e.g., certain behaviors of the user equipment functionality).

[0079] --Search / interact / guide user devices that support specific services.

[0080] --Be notified when user equipment supporting certain capabilities is active in the telecommunications network.

[0081] --Instead of the currently used capability negotiation method (typically a binary mask indicating what features are supported (0 / 1)), user equipment will be able to explicitly declare what specific services are supported. This provides a very easily extensible method to add backwards compatible functionality (at some point, the bits in the specified bit mask are full).

[0082] --In addition to adding APIs, APIs can also be explicitly versioned so that a given service can be versioned without affecting other service definitions.

[0083] --According to the present invention, service-based signaling can be used in cases where the user equipment is the service producer: the user equipment can therefore directly use the service-based infrastructure instead of the non-access layer to communicate with, for example, the 5G core functional entities, and also expose capabilities, procedures and settings to third parties.

[0084] According to the invention, it is further advantageously possible and preferred that the transmission of endpoint related information pieces, in particular information pieces about specific application programming interface functionality of a specific service endpoint, is part of a network registration procedure of the user equipment with the telecommunication network.

[0085] Thus, according to the present invention, the transmission of endpoint-related information pieces, in particular information pieces about specific application programming interface functionality of a specific service endpoint, can advantageously be integrated with the registration procedure.

[0086] Furthermore, according to the present invention, it is advantageously possible and preferred that the control plane channel serves as a transport channel for the user plane channel by means of encapsulation and vice versa (in particular for the transmission of request messages and / or for the transmission of endpoint related information fragments).

[0087] Furthermore, according to the present invention, it is advantageously possible and preferred that the request message corresponds to at least one of the following:

[0088] -- Non-access stratum messages, in particular non-access stratum messages including containers (in particular UE parameter update containers),

[0089] - Non-access stratum messages, in particular non-access stratum messages including containers (in particular UE parameter update containers) sent encapsulated on specific PDU sessions (in particular Wi-Fi PDU sessions),

[0090] --Radio Resource Control messages.

[0091] Thus, established mechanisms can advantageously be used to implement the method of the invention.

[0092] Furthermore, according to the present invention, it is advantageously possible and preferred that the requesting entity or the requesting network node corresponds to at least one of the following components within a 5G system or an IP Multimedia Subsystem or an IMS system:

[0093] --gNB or base station entity,

[0094] --Access and mobility management function AMF, session management function SMF, user plane function UPF, unified data management UDM, policy and charging function PCF, short message service function SMSF, non-3GPP interworking function N3IWF, charging function CHF, network exchange function NEF, network data analysis function NWDAF, network repository function NRF, gateway mobile location center GMLC,

[0095] --Service Call State Control Function S-CSCF, Proxy Call State Control Function P-CSCF, Interrogation Call State Control Function I-CSCF.

[0096] According to a further preferred embodiment of the present invention, the specific service endpoint and / or the specific application programming interface functionality provided by the specific service endpoint within the user equipment exposes one or more of the following functionalities within the mobile communication system:

[0097] --Mobility management, session management, short message service, user equipment strategy, positioning service,

[0098] --USIM,

[0099] --IP Multimedia Subsystem Management Object IMS MO.

[0100] Thereby, it is advantageously possible to easily and efficiently configure the user equipment and / or modify its operating mode.

[0101] According to a further preferred embodiment of the present invention, the user equipment exposes at least two specific service endpoints and / or specific application programming interface functionalities of the same type, or exposes at least two instances of a specific service endpoint or specific application programming interface functionalities, in particular at least two USIM service endpoints and / or specific application programming interface functionalities.

[0102] Thus, it is advantageously possible to efficiently distinguish between such different functionalities and / or instances of the same type within the user equipment, and it is advantageously possible - in particular by means of corresponding request messages and / or corresponding endpoint-related information fragments involving or including specific address information related to a specific service endpoint - to selectively address or locate such different functionalities of the same type individually or to address or locate such different instances of a specific service endpoint individually.

[0103] According to a further preferred embodiment of the present invention, the endpoint-related information fragment about the application programming interface functionality of a specific service endpoint defines an application programming interface that the specific service endpoint can provide to multiple requester entities or requester network nodes, in particular, third-party network functions.

[0104] wherein, in particular, a request message involving or using a specific application programming interface functionality provided by a specific service endpoint corresponds to an application programming interface call message, and

[0105] Therein, in particular, the user equipment service endpoint registration functionality corresponds to a user equipment application programming interface registration functionality, in particular located at an access network level and / or a core network level of the telecommunication network.

[0106] It is therefore particularly advantageous that the user equipment service endpoint registration functionality can be located at the access network level and / or the core network level of the telecommunications network.

[0107] Furthermore, according to the present invention, it is advantageously possible and preferred that the endpoint-related information fragment regarding address information associated with a specific service endpoint comprises means for single addressing of the specific service endpoint, wherein the specific service endpoint corresponds in particular to a functionality of the user equipment and / or a variable of the user equipment and / or a device or module of the user equipment,

[0108] Therein, in particular the user equipment service endpoint registration functionality corresponds to a user equipment endpoint registration functionality, in particular located at a core network level of the telecommunication network.

[0109] Furthermore, the present invention relates to a user equipment for being operated or applying a modified mode of operation within or as part of a telecommunications network, wherein the operation of the user equipment or the modification of the operation is performed using control plane functionality,

[0110] wherein the telecommunications network comprises or is associated with or assigned to an access network and a core network, wherein the core network provides data connectivity towards a data network to the user equipment,

[0111] wherein the user equipment comprises or provides at least one functional and addressable service endpoint for providing or exposing services or functionality to a requestor entity or requestor network node external to the user equipment, wherein the requestor entity or requestor network node is part of an access network or a core network,

[0112] wherein the service endpoint is associated with or corresponds to a control plane functionality, and wherein the service endpoint being or associated with the control plane functionality communicates with or is accessible to a control plane network element of the telecommunications network via a control plane channel,

[0113] wherein, in order for the user equipment to be operated or to apply the modified operating mode, and in view of providing a specific service or specific functionality to the requesting entity or requesting network node by a specific service endpoint of the user equipment, the user equipment is configured such that:

[0114] The user equipment receives a request message from or on behalf of a requesting entity or a requesting network node, the request message being associated with a particular service endpoint, and wherein the request message

[0115] --Relates to or uses specific API functionality provided by a specific service endpoint

[0116] and / or

[0117] --relating to or including specific address information associated with a specific service endpoint,

[0118] --A specific service endpoint processes the received request message based on its content.

[0119] Furthermore, the present invention relates to a system or a telecommunications network for operating or modifying the operation of a user equipment within or as part of a telecommunications network, wherein the operation of the user equipment or the modification of the operation is performed using control plane functionality.

[0120] wherein the telecommunications network comprises or is associated with or assigned to an access network and a core network, wherein the core network provides data connectivity towards a data network to the user equipment,

[0121] wherein the user equipment comprises or provides at least one functional and addressable service endpoint for providing or exposing services or functionality to a requestor entity or requestor network node external to the user equipment, wherein the requestor entity or requestor network node is part of an access network or a core network,

[0122] wherein the service endpoint is associated with or corresponds to a control plane functionality, and wherein the service endpoint being or associated with the control plane functionality communicates with or is accessible to a control plane network element of the telecommunications network via a control plane channel,

[0123] wherein, in order to operate a user equipment or modify the operation of the user equipment and in view of providing a specific service or specific functionality to a requesting entity or a requesting network node by a specific service endpoint of the user equipment, the system or telecommunications network is configured such that:

[0124] -- a telecommunications network or a requesting entity or a requesting network node or on behalf of a requesting entity or a requesting network node transmits a request message to a user equipment, the request message being associated with a specific service endpoint, wherein the request message

[0125] --Relates to or uses specific API functionality provided by a specific service endpoint

[0126] and / or

[0127] --relating to or including specific address information associated with a specific service endpoint,

[0128] --A specific service endpoint processes the received request message based on its content.

[0129] With regard to the system or telecommunication network, it is particularly preferred that the system or telecommunication network comprises user equipment service endpoint registration functionality, wherein the endpoint related information pieces regarding:

[0130] -- API functionality for specific service endpoints and / or

[0131] -- address information related to a specific service endpoint, in particular, information about a specific instance of a specific service endpoint,

[0132] The user equipment is provided with service endpoint registration functionality and in particular is thereby exposed for use by other nodes or instances of the telecommunications network.

[0133] Still additionally, the present invention relates to a user equipment service endpoint registration functionality of the inventive system or the inventive telecommunication network.

[0134] Additionally, the present invention also relates to a program comprising computer-readable program code and / or a computer-readable medium comprising instructions, which, when executed on a computer, and / or on a user equipment, and / or on user equipment service endpoint registration functionality, and / or on a network node of a telecommunications network, or partly on the user equipment, and / or partly on the user equipment service endpoint registration functionality, and / or partly on the network node of the telecommunications network, cause the computer and / or the user equipment and / or the user equipment service endpoint registration functionality and / or the network node of the telecommunications network to perform the method of the present invention.

[0135] These and other characteristics, features and advantages of the present invention will become apparent from the following detailed description taken in conjunction with the accompanying drawings, which illustrate, by way of example, the principles of the invention. This description is intended for illustrative purposes only and is not intended to limit the scope of the invention. The reference figures cited below serve as a reference to the accompanying drawings.

[0136] BRIEF DESCRIPTION OF THE DRAWINGS

[0137] Figure 1 Schematically illustrated is a telecommunication network comprising an access network, a core network and a user equipment, wherein the user equipment comprises or provides at least one functional and addressable service endpoint for providing or exposing a service or functionality to a requester entity or requester network node external to the user equipment.

[0138] Figure 2 Schematically illustrates the separation of the control plane and the user plane in communications between user equipment, a radio access network and a core network of a telecommunications network.

[0139] Figure 3 Schematically illustrated is the communication between user equipment and a network function using a control plane communication mechanism.

[0140] Figure 4 The communication between user equipment, access and mobility management functions and unified data management is schematically illustrated in order to configure and / or modify the operation of the user equipment according to the present invention.

[0141] Figure 5 A user equipment service endpoint registration functionality that stores endpoint-related information segments regarding address information related to a particular service endpoint of the user equipment is schematically illustrated.

[0142] Figure 6 The communication between a user equipment according to the invention and a radio access network and / or a core network of a telecommunication network is schematically illustrated.

[0143] Figure 7Schematically illustrated is a user equipment service endpoint registration functionality storing endpoint related information pieces about an application programming interface functionality of a specific service endpoint of a user equipment, the user equipment service endpoint registration functionality being located in a radio access network of a telecommunications network.

[0144] Figure 8 Schematically illustrated is a user equipment service endpoint registration functionality storing endpoint related information pieces about an application programming interface functionality of a specific service endpoint of a user equipment, the user equipment service endpoint registration functionality being located in a core network of a telecommunication network.

[0145] Figure 9 and 10 Schematically illustrated is a communication diagram related to registration of a user equipment with a telecommunications network according to the present invention, involving registration of an application programming interface of one or more service endpoints of the user equipment.

[0146] Figures 11 to 14 Schematically illustrating a communication diagram associated with various application programming interface call scenarios or use cases using API registration according to the present invention.

[0147] Detailed description

[0148] The present invention will be described with respect to specific embodiments and with reference to certain drawings, but the invention is not limited thereto but only by the claims. The drawings described are merely illustrative and non-limiting. In the drawings, the size of some of the elements may be exaggerated and not drawn to scale for illustrative purposes.

[0149] When referring to a singular noun an indefinite or definite article is used, for example "a", "an", "the" include a plural of that noun unless something else is stated.

[0150] Furthermore, the terms first, second, third, etc. in the description and claims are used to distinguish between similar elements and not necessarily to describe a sequential or chronological order. It should be understood that the terms so used are interchangeable under appropriate circumstances, and that the embodiments of the invention described herein are capable of operation in a sequence different from that described or illustrated herein.

[0151] exist Figure 1 In FIG, a telecommunication network 100 is schematically shown, comprising an access network 110 and a core network 120. The access network 110 comprises a plurality of radio cells 11, 12. Figure 1In the exemplary case or scenario shown, a first base station entity 111 is generated or associated with or spans a first radio cell 11, and a second base station entity 112 is generated or associated with or spans a second radio cell 12. The user equipment 20 comprises or provides at least one functional and addressable service endpoint 25 for providing or exposing services or functionality to a requester entity or requester network node 190 external to the user equipment 20. In particular, the requester entity or requester network node 190 is part of the access network 110 or the core network 120. The user equipment 20 is typically, but not necessarily, mobile, i.e. capable of moving relative to the (typically, but not necessarily, static) radio cells 11, 12 or the corresponding base station entities 111, 112 of the access network 110. In Figure 1 In the exemplary illustration of , the core network 120 includes a user equipment service endpoint registration functionality 190. Furthermore, the core network 120 is connected to a data network 130. The core network 120 provides data connectivity towards the data network 130 to the user equipment 20.

[0152] According to the present invention, the control plane functionality of the telecommunications network 100 is used to operate or configure the user equipment 20, or to modify its operation or operating mode.

[0153] exist Figure 2 , the separation of the control plane 101 and the user plane 102 in the communication between user equipment 20, access network 110 (or radio access network 110), and core network 120 of a telecommunications network 100 is schematically shown. As in conventionally known telecommunications networks, the telecommunications network 100 includes different levels of signaling, each with a different anchor (the non-access stratum / N1 interface between the user equipment 20 and the core network 120, and the radio resource control between the user equipment 20 and the radio access network 110 (or access network 110)). The access and mobility management function 121 serves as the control plane anchor, and the user plane function 122 serves as the user plane anchor. As the interface between the core network 120 and the access network 110, SCTP is used for the control plane 101, and GTP-U is used for the user plane 102.

[0154] According to the present invention, the user equipment 20 includes or provides at least one functional and addressable service endpoint 25 for providing or exposing services or functionality to a requesting entity or requesting network node 190 external to the user equipment 20, wherein the requesting entity or requesting network node 190 is part of the access network 110 or the core network 120.

[0155] The service endpoint 25 is related to or corresponds to control plane functionality and, as a control plane functionality or related thereto, communicates with or is accessible to the control plane network element 121 of the telecommunications network 100 via a control plane channel.

[0156] In order to operate the user equipment 20 or modify the operation of the user equipment 20, and in view of the provision of a particular service or a particular functionality by a particular service endpoint 25 of the user equipment 20 to the requesting entity or requesting network node 190, the user equipment 20 receives a request message 250 from or on behalf of the requesting entity or requesting network node 190, the request message 250 being associated with the particular service endpoint 25 and the request message 250 being associated with the particular service endpoint 25.

[0157] --Relates to or uses specific application programming interface functionality provided by a specific service endpoint 25

[0158] and / or

[0159] --relating to or including specific address information associated with a specific service endpoint 25.

[0160] Then, the specific service endpoint 25 processes the received request message 250 according to the content of the received request message 250 .

[0161] Therefore, according to the present invention, the request message 250 involves or uses a specific application programming interface functionality provided by the specific service endpoint 25, or the request message 250 involves or includes specific address information related to the specific service endpoint 25, or the request message 250 involves or uses a specific application programming interface functionality provided by the specific service endpoint 25 and involves or includes specific address information related to the specific service endpoint 25.

[0162] For situations where the request message 250 involves or uses a specific application programming interface functionality provided by a specific service endpoint 25, this is done in Figure 6 It is schematically shown in Figure 6 The present invention schematically illustrates the communication between a user equipment 20 and network functions or network elements of a radio access network 110 and / or a core network 120 of a telecommunications network 100, as well as the exposure of application programming interfaces of the user 20. The user equipment 20 includes a plurality of different service endpoints 25, which are indicated by reference numerals API 1, API 2, ..., API N. According to the present invention, the capabilities of the user equipment 20 (i.e., the corresponding specific service endpoints 25) are defined by the application programming interfaces exposed by the user equipment 20. Figure 6Components of the access network 110 (or radio access network 110) indicated by reference numerals Comp A, Comp B, ..., Comp N and / or Figure 6 The network functions of the core network 120 indicated by the reference numerals NF A, NF B, ..., NFN (corresponding to the requesting entity or requesting network node 190, respectively) are capable of sending a signaling message (request message 250) to the user equipment 20 involving or using one of the specific application programming interface functionalities provided by the service endpoint 25 of the user equipment 20.

[0163] For situations where the request message 250 relates to or includes specific address information associated with a specific service endpoint 25, this is Figure 3 It is schematically shown in Figure 3 The communication between the user equipment 20 and the network function 190 (corresponding to the requesting entity or requesting network node 190) using the control plane communication mechanism is schematically illustrated. Figure 3 2 (devices 1 and 2). A plurality of different service endpoints 25 are indicated by reference numerals F1, F2 (functionality A1, A2), Var A (variable A), Dev 1, Dev 2 (devices 1 and 2) in FIG. A user equipment stack or user equipment protocol stack is indicated by reference numeral 21. In a first processing step 201, a network function 190 (corresponding to a requesting entity or requesting network node 190) decides whether to send a signaling message (request message 250) via the control plane anchor 121 (or indirectly via the user plane anchor 122 if the control plane is encapsulated within the user plane) and includes endpoint address information in the request message 250—i.e., specific address information associated with a specific service endpoint 25 of the user equipment 20. Within the user equipment 20, and in a processing step 202, routing occurs (i.e., based on the user equipment endpoint address in message 250) toward the destination endpoint addressed by the address information (i.e., the corresponding service endpoint).

[0164] This means that, according to the present invention, a message (request message 250) containing an endpoint address is sent toward the user equipment 20, enabling the user equipment stack 21 to determine the target of the transmitted message (i.e., the service endpoint 25 indicated by the endpoint address or address information). Unlike conventionally known "non-access stratum message types" (e.g., SM, MM), it also includes an instance address, which allows different instances of the same endpoint type to be distinguished, such as different paths (or endpoint addresses) of different service endpoints 25 (such as, for example, an application programming interface service endpoint within the user equipment 20, multiple SIM cards and / or subscriber-related information when multiple subscriptions exist in the user equipment 20, multiple radios in the same user equipment 20, such as 5G-NR radios).

[0165] Figure 4 The communication between the user equipment 20, the access and mobility management function 121, and the unified data management 123 is schematically illustrated for configuring and / or modifying the operation of the user equipment 20 according to the present invention. In a first processing step 203, a user equipment parameter update (UPU) message (container) is transmitted from the unified data management 123 to the access and mobility management function 121 as a request message 250. In a second processing step 204, the UPU container is sent over the non-access stratum (i.e., via a non-access stratum message), and the UPU container indicates an "endpoint address" (i.e., specific address information associated with a specific service endpoint 25 (e.g., corresponding to a variable)), which indicates the destination of the UPU container.

[0166] Similar to how IPv6 can provide the same functionality as IPv4 by using designated ranges for well-known purposes, specific (i.e., standardized, well-known) addresses can be used to cover all use cases of the "NAS message types" currently in use (e.g., "currently active SIM devices"), while also allowing dynamic allocation of addresses to UE endpoints and / or repeated transmission of control plane messages via different control plane paths.

[0167] According to the present invention, preferably, the telecommunication network 100 comprises a user equipment service endpoint registration functionality 180 and in a third step prior to the first step, endpoint related information fragments regarding:

[0168] --Application programming interface functionality of a specific service endpoint 25 and / or

[0169] -- address information related to a specific service endpoint 25, in particular about a specific instance of a specific service endpoint 25,

[0170] is provided to the user equipment service endpoint registration functionality 180 and in particular is thereby exposed for use by other nodes or instances of the telecommunications network 100, in particular by a corresponding requestor entity or requestor network node 190,

[0171] According to such embodiments, the endpoint-related information fragment specifically enables the user equipment service endpoint registration functionality 180 to at least one of:

[0172] --Register a specific application programming interface provided by a specific service endpoint 25,

[0173] --Provide address information about how a specific service endpoint 25 can be accessed, in particular address information about a specific instance of a specific service endpoint 25.

[0174] Figure 7 and 8An example of a user equipment service endpoint registration functionality 180 for registering information about an application programming interface of a service endpoint 25 of a user equipment 20 is schematically provided. Figure 7 , a user equipment service endpoint registration functionality 180 is schematically shown that stores endpoint related information pieces about one or more application programming interface functionalities of at least one, but typically a plurality of, specific service endpoints 25 of the user equipment 20 . Figure 7 The service endpoint 25 is not explicitly shown in FIG. Figure 7 In the exemplary embodiment shown, user equipment service endpoint registration functionality 180 is located in the radio access network 110 of the telecommunications network 100, i.e., radio resource control application programming interface registration is performed. Exemplarily, a gNB base station entity is schematically shown as part of the radio access network 110 and is connected to the user equipment service endpoint registration functionality 180.

[0175] exist Figure 8 , a user equipment service endpoint registration functionality 180 is schematically shown that stores endpoint related information pieces about one or more application programming interface functionalities of at least one, but typically a plurality of, specific service endpoints 25 of the user equipment 20 . Figure 8 The service endpoint 25 is not explicitly shown in FIG. Figure 8 In the exemplary embodiment shown, user equipment service endpoint registration functionality 180 is located in the core network 120 of the telecommunications network 100, i.e., non-access stratum application programming interface registration is performed. Exemplarily, a gNB base station entity is schematically shown as part of the radio access network 110, and access and mobility management functions 121 and user plane functions 122 are shown as part of the core network 120 connected to the user equipment service endpoint registration functionality 180.

[0176] therefore, Figure 7 and 8 It is shown that the exposed user equipment application programming interface can be registered at the radio access network 110 level (radio resource control) or the core network 120 level (non-access stratum), i.e., the user equipment service endpoint registration functionality 180 is part of the access network 110 of the telecommunication network 100 and / or part of the core network 120 of the telecommunication network 100. In this case (i.e., the endpoint-related information fragment is associated with the application programming interface functionality of the corresponding service endpoint 25), the user equipment service endpoint registration functionality 180 implements the functionality of the user equipment (UE) application programming interface (API) registration (UAR).

[0177] It is therefore advantageously possible that endpoint-related information - information exposed about the service endpoint 25 of the user equipment 20 - can be provided to multiple requesting entities or requesting network nodes, in particular network functions or network elements of a telecommunications network and third-party network functions, by means of the user equipment service endpoint registration functionality 180.

[0178] By means of user equipment API registration (i.e., providing endpoint-related information snippets, in particular information snippets about the API functionality of a specific service endpoint 25, to the user equipment service endpoint registration functionality 180), the radio access network 110 and / or the core network 120 can implicitly be aware of the user equipment capabilities: for example, for user equipment 20 with reduced capabilities or capabilities, such user equipment 20 may register fewer APIs, while for user equipment 20 with greater or increased capabilities or capabilities, such user equipment 20 will register more APIs. Thus, according to the present invention, information can advantageously be provided to the telecommunications network 100 (i.e., to the radio access network 110 and / or to the core network 120) about which feature or features the respective user equipment 20 supports. Thus, a user equipment 20 with fewer capabilities will be able to indicate to the radio access network 110 and / or the core network 120 that it does not support certain features, such as features X, Y, and Z.

[0179] If the default scenario is set to no application programming interface registration occurs if no capabilities are supported, the problem of capability negotiation can be eliminated.

[0180] Figure 5 An example of a user equipment service endpoint registration functionality 180 for registering information regarding address information associated with a specific service endpoint 25, in particular, address information regarding a specific instance of the specific service endpoint 25, is schematically provided. The mechanisms and descriptions associated with an embodiment in which the endpoint-related information fragment is an endpoint-related information fragment of the application programming interface functionality regarding the specific service endpoint 25 can also be applied to an embodiment in which the endpoint-related information fragment is an endpoint-related information fragment regarding address information associated with the specific service endpoint 25 (in particular, regarding a specific instance of the specific service endpoint 25). In this case as well, the endpoint-related information fragment is provided to the user equipment service endpoint registration functionality 180, i.e., the endpoint address (or address information associated with the corresponding service endpoint 25) is registered with an entity (the user equipment service endpoint registration functionality 180) in the core network 120, i.e., the exposed endpoint address or address information can thus be registered again at the radio access network level (radio resource control) and / or the core network level (non-access stratum) (e.g., at the user equipment (UE) control plane (CP) endpoint registration (UCER) or user equipment endpoint registry). Figure 5A scenario is shown of such a user equipment (UE) control plane (CP) endpoint registration (i.e., user equipment service endpoint registration functionality 180, in particular in the case where the endpoint related information fragment is an endpoint related information fragment about address information related to the corresponding service endpoint 25) as part of the core network 120: by storing information related to how the endpoint (i.e., the corresponding service endpoint 25 of the user equipment 20) can be accessed (e.g., via the non-access stratum, a specific PDU session, or both) in the user equipment service endpoint registration functionality 180 (or UCER or UE endpoint registration), the core network function is able to find an appropriate access and mobility management function and / or user plane function to act as a gateway to send a corresponding message (request message 250) to the user equipment 20. If a given user equipment functionality (i.e. a given service endpoint 25) is exposed via several methods (e.g. via Wifi PDU sessions and / or 5G-NR (New Radio) non-access stratum), the corresponding signaling towards the user equipment 20 (i.e. the request message 250) can be sent towards the user equipment 20 via redundant channels, without necessarily passing through the access and mobility management function (which would be the case in a conventional telecommunications network 20, as all signaling information would have to flow via the access and mobility management function).

[0181] Therefore, similar to the case where the endpoint-related information fragment is related to the application programming interface functionality of the corresponding service endpoint 25 (i.e., the corresponding information of the available application programming interface is stored in the core network in a service-based infrastructure manner), in the case where the endpoint-related information fragment is related to the address information about the corresponding service endpoint 25, the corresponding user equipment 20 can register the control plane endpoint (service endpoint 25) in the core network 120. Figure 5 , where the user equipment service endpoint registration functionality 180 stores endpoint related information pieces regarding address information of at least one, but typically a plurality of, specific service endpoints 25 for the user equipment 20 . Figure 5 The service endpoint 25 is not explicitly shown in FIG. Figure 5 In the exemplary embodiment shown, the user equipment service endpoint registration functionality 180 is located in the core network 120 of the telecommunications network 100. Exemplarily, a gNB base station entity is schematically shown as part of the radio access network 110, and an access and mobility management function 121 and a user plane function 122 are shown as part of the core network 120 connected to the user equipment service endpoint registration functionality 180.

[0182] An important use case of the user equipment service endpoint registration functionality 180 according to the present invention (particularly in the case where it implements a user equipment (UE) application programming interface (API) registration (UAR), i.e. in the case where the endpoint related information fragment is related to the application programming interface functionality of the corresponding service endpoint 25) is related to the registration of the user equipment with the telecommunication network 100. According to the present invention, it is proposed that in particular the transmission of the endpoint related information fragment to the user equipment service endpoint registration functionality 180 (in the third step of the method according to the present invention) is related to the registration of the user equipment 20 with the telecommunication network 100. Figure 9 and 10 In the figure, an example of such a UE API registration (i.e., registration of an application programming interface of one or more service endpoints of a user equipment) as part of or in connection with a registration procedure is schematically shown by means of schematically illustrating the communication between the user equipment 20, the access and mobility management function 121 and the user equipment service endpoint registration functionality 180 (in this case also referred to as the user equipment (UE) application programming interface (API) registration UAR).

[0183] Figure 9 It shows:

[0184] - In a first processing step 205, a user equipment registration request (message) is transmitted from the user equipment 20 to the access and mobility management function 121;

[0185] - in a second processing step 206, a registration accept is transmitted from the access and mobility management function 121 to the user equipment 20; and

[0186] In a third processing step 207 , a UE AP registration initiated by the user equipment 20 towards the user equipment service endpoint registration functionality 180 is transmitted or performed, ie registration of the application programming interface of the service endpoint of the user equipment 20 .

[0187] Figure 10 It shows:

[0188] - In a first processing step 208, a user equipment registration request (message) is transmitted from the user equipment 20 to the access and mobility management function 121, and a UE AP registration initiated by the user equipment 20 towards the access and mobility management function 121 is transmitted or performed;

[0189] - in the second processing step 209, the supported application programming interfaces are used as criteria for admitting the user equipment 20 to the telecommunication network 100 - in the case where it is determined that the user equipment 20 is admitted (e.g. due to the fact that a certain (category of) application programming interface is available or exposed), the flow continues with a fourth processing step 211, otherwise, i.e. the user equipment 20 is not to be admitted (e.g. due to the fact that one or more (category of) application programming interfaces are not available or exposed), the flow continues with the third processing step 210;

[0190] - in a third processing step 210, a registration reject is transmitted from the access and mobility management function 121 to the user equipment 20;

[0191] In a fourth processing step 211 , a UE AP registration initiated by the access and mobility management function 121 (but on behalf of the user equipment 20 ) towards the user equipment serving endpoint registration functionality 180 is transferred or performed, ie registration of the application programming interface of the serving endpoint of the user equipment 20 .

[0192] In a fifth processing step 212 , a Registration Accept (message) is transmitted from the Access and Mobility Management Function 121 to the User Equipment 20 .

[0193] Therefore, according to Figure 10 The communication diagram shown performs a registration procedure for the user equipment 20, providing the possibility of allowing the access and mobility management function 121 to assess the user equipment capabilities before or at the time of admitting the user equipment 20 to the telecommunication network 100; Figure 9 Communication diagram of UE API registration performed after registration acceptance.

[0194] According to the present invention, preferably, in order to still support capability support as an access condition, the telecommunication network 100 indicates to the user equipment 20 that UE API registration must be included as part of the registration request.

[0195] In the following, a number of different use cases are provided using the API registration according to the present invention:

[0196] exist Figure 11 , schematically illustrates an implementation of a scenario or use case where user equipment functionality is triggered by UE API registration, particularly for moving a given user equipment 20 to a specific network slice and enabling low latency communication with a specific FQDN. In this regard, Figure 11 Communications between a user equipment 20 (of the telecommunications network 100 ), a user equipment service endpoint registration functionality 180 (or user equipment (UE) application programming interface (API) registration UAR), a requesting entity or requesting network node 190 and unified data management 123 are shown.

[0197] In a first processing step 213, the requesting entity or requesting network node 190 subscribes to be informed that such user equipment has or exposes the corresponding functionality in question, here: low latency registration is supported by means of a command of, for example, the type "Subscribe (UE supports low latency registration)"; this is done by means of a message from the requesting entity or requesting network node 190 to the user equipment service endpoint registration functionality 180 (or UAR).

[0198] In a second processing step 214, the user equipment 20 registers its application programming interface functionality with the user equipment service endpoint registration functionality 180 (or UAR) by means of a registration message (eg involving the command "Register (Low Latency API, Subscriber API + Subscriber Parameters)".

[0199] In a third processing step 216, the user equipment service endpoint registration functionality 180 (or UAR) notifies the requesting entity or requesting network node 190 (due to the subscription it initiated in the first processing step 213) that the user equipment 20 exposes the application programming interface or has the capability or functionality (Notification (Registration Data)).

[0200] In a fourth processing step 217 , subscriber parameters are retrieved by the requesting entity or requesting network node 190 from the unified data management 123 node or instance.

[0201] In a fifth process step 218 , the user equipment service endpoint registration functionality 180 (or UAR) evaluates whether the subscriber (ie the user equipment 20 ) is allowed to use the feature in question, here: the low latency feature. If yes, flow continues towards a sixth process step 219 .

[0202] In a sixth processing step 219, the requesting entity or requesting network node 190 transmits an application programming interface call regarding the functionality in question towards the user equipment 20, here for example according to the following command: "Instructions to authenticate to network slice X with additional credentials Y and to re-establish the PDU session with parameter set Z".

[0203] therefore, Figure 11 An example of triggering API calls towards the user equipment 20 based on a user equipment application programming interface (service) registered on the UAR (or user equipment service endpoint registration functionality 180) is shown.

[0204] According to a further example, and similar to Figure 11 The scene shown in Figure 12 The addition of a User Equipment Routing Policy (URSP) is shown in which a given third party application programming interface is supported regardless of subscriber information. Again, Figure 12Communications between the user equipment 20, the user equipment service endpoint registration functionality 180 (or UAR), and a requesting entity or requesting network node 190 are shown.

[0205] In a first processing step 220, the requesting entity or requesting network node 190 subscribes to be informed that such user equipment has or exposes the corresponding functionality in question, here: the user equipment supports the UAV application programming interface; this is done by means of a message from the requesting entity or requesting network node 190 to the user equipment service endpoint registration functionality 180 (or UAR).

[0206] In a second processing step 221, the user equipment 20 registers its application programming interface functionality with the user equipment service endpoint registration functionality 180 (or UAR) by means of a registration message (eg involving the command "Register (UAV Application Programming Interface, URSP Application Programming Interface)").

[0207] In a third processing step 222, the user equipment service endpoint registration functionality 180 (or UAR) notifies the requesting entity or requesting network node 190 (due to the subscription it initiated in the first processing step 220) that the user equipment 20 exposes the application programming interface or has the capability or functionality (Notification (Registration Data)).

[0208] In a sixth processing step 223 , the requesting entity or requesting network node 190 transmits an application programming interface call towards the user equipment 20 regarding the functionality in question, here for example according to the following command: “Set URSP rules so that streaming uplink UAV video gets the specific quality of service applied”.

[0209] therefore, Figure 12 An example of triggering a URSP API call based on a registered API combination is shown (in this case, no subscriber information is required).

[0210] According to a further example, and similar to Figure 11 and 12 The scene shown in Figure 13 The writing of parameters belonging to another subscription, in particular to another public land mobile network, is shown. Again, Figure 13 Communication between the user equipment 20, a user equipment service endpoint registration functionality 180 (or UAR) and a requesting entity or requesting network node 190 (particularly of the other public land mobile network) is shown.

[0211] In a first processing step 224, the requesting entity or requesting network node 190 subscribes to be informed that such user equipment has or exposes the corresponding functionality in question, here: the user equipment supports subscription to a specific public land mobile network (e.g. PLMN X) by means of a command of the type “Subscribe (UE supports subscription to PLMN X and PLMN Y)” for example; this is done by means of a message from the requesting entity or requesting network node 190 to the user equipment service endpoint registration functionality 180 (or UAR).

[0212] In a second processing step 225, the user equipment 20 registers its application programming interface functionality with the user equipment service endpoint registration functionality 180 (or UAR) by means of a registration message (e.g. involving the command "Register (Subscribe API, Subscribe Data X [i.e. for PLMN X], Subscribe Data Y [i.e. for PLMN Y])").

[0213] In a third processing step 226, the user equipment service endpoint registration functionality 180 (or UAR) notifies the requesting entity or requesting network node 190 (due to the subscription it initiated in the first processing step 224) that the user equipment 20 exposes the application programming interface or has the capability or functionality (Notification (Registration Data)).

[0214] In a fourth processing step 227, the requesting entity or requesting network node 190 evaluates the consistency of parameters between the two networks (i.e., PLMN X and PLMN Y); if the subscriber (i.e., user equipment 20) is allowed to use the feature in question (or if the subscriber credentials or parameters are consistent), here: to use PLMN X, the flow continues towards a fifth processing step 228.

[0215] In a fifth processing step 228, the requesting entity or requesting network node 190 transmits an application programming interface call regarding the functionality in question towards the user equipment 20, here for example according to the following command: “instruct subscriber API-Y (in the user equipment 20) to set PLMN X as the allowed preferred roaming partner for the given location”, which requires interaction with the subscriber identity module (SIM card) of PLMN Y in the user equipment 20.

[0216] therefore, Figure 13 An example is shown where credential data is set on the user equipment 20 by a third party network provider.

[0217] For the last example, Figure 14It is shown that the exposed application programming interface (of the user equipment 20) may require authentication and / or authorization, so that network functions belonging to PLMN X (the term PLMN is intended here only as an example of a network; it also covers the general meaning of "network" as this may also apply to private networks that are not PLMNs) are only allowed to operate on certain parts of the subscriber API-Y of the user equipment 20, but not on all parts.

[0218] This approach will also be applicable when there is an intermediate API gateway function (e.g. NEF, SCEF) and when service-based infrastructure messages are transmitted via the non-access stratum protocol. For this purpose, a method for addressing endpoints on the non-access stratum within the user equipment 20 is required, which is provided separately (this can be used independently of whether the endpoint is an API).

[0219] Figure 14 The communication between the user equipment 20, the access and mobility management function 121, the network exposure function NEF and a requesting entity or requesting network node 190 is shown.

[0220] In a first processing step 229, the requesting entity or requesting network node 190 requests parameters and transmits a message to the Network Exposure Function NEF.

[0221] In a second processing step 230 , the Network Exposure Function NEF requests the parameters and transmits a message to the Access and Mobility Management Function 121 .

[0222] In a third process step 231 , the access and mobility management function 121 tunnels the API messages over the NAT transport protocol.

[0223] In a fourth processing step 232, the access and mobility management function 121 transmits a non-access stratum message including a request for parameters to the user equipment 20, thereby enabling indirect API access via an intermediate GW (eg, NEF) and tunneling of SBI messages over the non-access stratum.

Claims

1. A method for operating or modifying the operation of a user equipment (20) within or as part of a telecommunications network (100) using control plane functionality, wherein the telecommunication network (100) comprises an access network (110) and a core network (120), wherein the core network (120) provides data connectivity to the user equipment (20) towards a data network (130), wherein the telecommunications network (100) comprises a user equipment service endpoint registration function (180), wherein the user equipment (20) comprises at least one function and an addressable service endpoint for providing or exposing a service or function to a requester entity or a requester network node (190) external to the user equipment (20), wherein the requester entity or the requester network node (190) is part of the access network (110) or the core network (120), wherein the service endpoint is associated with or corresponds to a control plane function, and wherein the service endpoint as or associated with the control plane function communicates with or is accessible to a control plane network element of the telecommunication network (100) via a control plane channel, in, In order to operate the user equipment (20) or to modify the operation of the user equipment (20), and in view of providing a specific service or a specific functionality to the requesting entity or the requesting network node (190) by a specific service endpoint (25) of the user equipment (20), the method is characterized by the following steps: In a first step, the user equipment (20) receives a request message (250) from or on behalf of the requesting entity or the requesting network node (190), the request message (250) being related to the specific service endpoint (25) and wherein the request message (250) - involving or using a specific application programming interface functionality provided by the specific service endpoint (25), wherein the content of the request message (250) corresponds to an application programming interface call message intended to be received and processed by the specific service endpoint (25), and / or - relates to or includes specific address information associated with said specific service endpoint (25), wherein the content of said request message (250) includes means for uniquely addressing said specific service endpoint (25), In a second step, the specific service endpoint (25) processes the request message (250) according to the content of the received request message (250), and in a third step before the first step, endpoint-related information fragments about: -- the application programming interface functionality of the specific service endpoint (25) and / or -- address information associated with the specific service endpoint (25), is provided to the user equipment service endpoint registration function (180) and thereby exposed for use by other nodes or instances of the telecommunications network (100), and wherein the endpoint-related information fragment enables the user equipment service endpoint registration function (180) to at least one of: --registering the specific application programming interface provided by the specific service endpoint (25), --Provides address information on how the specific service endpoint (25) can be accessed.

2. The method of claim 1, wherein the user equipment service endpoint registration function (180) is part of the access network (110) of the telecommunications network (100) or part of the core network (120) of the telecommunications network (100).

3. The method according to claim 1, wherein The transmission of the endpoint related information fragment is part of a network registration procedure of the user equipment (20) with the telecommunications network (100).

4. The method of claim 3, wherein the transmission of the endpoint-related information segments regarding the specific application programming interface functionality of the specific service endpoint (25) is part of a network registration procedure of the user equipment (20) with the telecommunications network (100).

5. The method according to claim 1, wherein The control plane channel serves as a transmission channel for the user plane channel for transmission of the request message (250) and / or for transmission of the endpoint related information segment by means of encapsulation, or the user plane channel serves as a transmission channel for the control plane channel for transmission of the request message (250) and / or for transmission of the endpoint related information segment by means of encapsulation.

6. The method of claim 1 , wherein the request message (250) corresponds to at least one of: -- NAS message -- NAS message sent encapsulated on a specific PDU session. --Radio Resource Control messages.

7. The method of claim 6, wherein the NAS message is a NAS message including a container. The method of claim 7 , wherein the container is a UE parameter update container.

9. The method of claim 6, wherein the specific PDU session is a Wifi PDU session.

10. The method of claim 1, wherein the requesting entity or the requesting network node (190) corresponds to at least one of the following components within a 5G system or an IP Multimedia Subsystem (IMS) system: --gNB --Access and mobility management function AMF, session management function SMF, user plane function UPF, unified data management UDM, policy and charging function PCF, short message service function SMSF, non-3GPP interworking function N3IWF, charging function CHF, network exchange function NEF, network data analysis function NWDAF, network repository function NRF, gateway mobile location center GMLC, --Service Call State Control Function S-CSCF, Proxy Call State Control Function P-CSCF, Interrogation Call State Control Function I-CSCF.

11. The method of claim 1 , wherein the specific service endpoint (25) and / or specific application programming interface functionality provided by the specific service endpoint (25) within the user equipment (20) exposes one or more of the following functionalities within a mobile communication system: --Mobility management, session management, short message service, user equipment strategy, positioning service, --USIM, --IP Multimedia Subsystem Management Object IMS MO.

12. The method of claim 1, wherein the user equipment (20) exposes at least two specific service endpoints (25) and / or specific application programming interface functions of the same type, or exposes at least two instances of the specific service endpoint (25) or specific application programming interface function.

13. The method of claim 12, wherein the user equipment (20) exposes at least two USIM service endpoints and / or specific application programming interface functions.

14. The method according to claim 1 , wherein the endpoint-related information segment about the application programming interface function of the specific service endpoint (25) defines an application programming interface that the specific service endpoint (25) can provide to multiple requester entities or requester network nodes, in, The user equipment service endpoint registration function (180) corresponds to a user equipment application programming interface registration function located at the access network (110) level and / or the core network (120) level of the telecommunication network (100).

15. The method according to claim 14, wherein the endpoint-related information segment defines an application programming interface that the specific service endpoint (25) can provide to a third-party network function.

16. The method of claim 1, wherein the specific service endpoint (25) corresponds to a function of the user equipment (20) and / or a variable of the user equipment (20) and / or a device or module of the user equipment (20), and / or where The user equipment service endpoint registration function (180) corresponds to a user equipment endpoint registration function located at the core network (120) level of the telecommunication network (100).

17. A user equipment (20) for being operated or applying a modified mode of operation using a control plane function within or as part of a telecommunications network (100), wherein the telecommunication network (100) comprises an access network (110) and a core network (120), wherein the core network (120) provides data connectivity to the user equipment (20) towards a data network (130), wherein the telecommunications network (100) comprises a user equipment service endpoint registration function (180), wherein the user equipment (20) comprises at least one function and an addressable service endpoint for providing or exposing a service or function to a requester entity or a requester network node (190) external to the user equipment (20), wherein the requester entity or the requester network node (190) is part of the access network (110) or the core network (120), wherein the service endpoint is associated with or corresponds to a control plane function, and wherein the service endpoint as or associated with the control plane function communicates with or is accessible to a control plane network element of the telecommunication network (100) via a control plane channel, in, In order to operate the user equipment (20) or apply a modified mode of operation, and in view of providing a specific service or a specific function to the requesting entity or the requesting network node (190) by a specific service endpoint (25) of the user equipment (20), It is characterized by: The user equipment (20) is configured such that: a request message (250) is received from or on behalf of the requesting entity or the requesting network node (190), the request message (250) being related to the specific service endpoint (25), and wherein the request message (250) - involving or using a specific application programming interface functionality provided by the specific service endpoint (25), wherein the content of the request message (250) corresponds to an application programming interface call message intended to be received and processed by the specific service endpoint (25), and / or - relates to or includes specific address information associated with said specific service endpoint (25), wherein the content of said request message (250) includes means for uniquely addressing said specific service endpoint (25), wherein the specific service endpoint (25) is configured to process the received request message (250) according to the content of the received request message (250), wherein the user equipment (20) is configured to provide the user equipment service endpoint registration function (180) with endpoint related information segments regarding: -- the application programming interface functionality of the specific service endpoint (25) and / or -- address information associated with the specific service endpoint (25), wherein the endpoint-related information fragment is thereby exposed for use by other nodes or instances of the telecommunications network (100), and wherein the endpoint-related information segment enables the user equipment service endpoint registration function (180) to implement at least one of the following: --registering the specific application programming interface provided by the specific service endpoint (25), --Provides address information on how the specific service endpoint (25) can be accessed.

18. A telecommunications network (100) for operating or modifying the operation of user equipment (20) within or as part of a telecommunications network (100) using control plane functionality, wherein the telecommunications network (100) comprises an access network (110) and a core network (120), wherein the core network (120) provides data connectivity to the user equipment (20) towards a data network (130), wherein the telecommunications network (100) comprises a user equipment service endpoint registration function (180), wherein the user equipment (20) comprises at least one function and an addressable service endpoint for providing or exposing a service or function to a requesting entity or a requesting network node (190) external to the user equipment (20), wherein the requesting entity or the requesting network node (190) is part of the access network (110) or the core network (120), wherein the service endpoint is associated with or corresponds to a control plane function, and wherein the service endpoint as or associated with the control plane function communicates with or is accessible to a control plane network element of the telecommunication network (100) via a control plane channel, in, In order to operate the user equipment (20) or to modify the operation of the user equipment (20), and in view of the provision of a specific service or a specific functionality to the requesting entity or the requesting network node (190) by a specific service endpoint (25) of the user equipment (20), Its characteristics are: The telecommunications network (100) or the requesting entity or the requesting network node (190) is configured to transmit a request message (250) to the user equipment (20), the request message (250) being associated with the specific service endpoint (25), wherein the request message (250) - involving or using a specific application programming interface functionality provided by the specific service endpoint (25), wherein the content of the request message (250) corresponds to an application programming interface call message intended to be received and processed by the specific service endpoint (25), and / or - relates to or includes specific address information associated with said specific service endpoint (25), wherein the content of said request message (250) includes means for uniquely addressing said specific service endpoint (25), wherein the specific service endpoint (25) is configured to process the received request message (250) according to the content of the received request message (250), wherein the user equipment service endpoint registration function (180) is configured to provide endpoint related information segments relating to: -- the application programming interface functionality of the specific service endpoint (25) and / or -- address information associated with the specific service endpoint (25), wherein the user equipment service endpoint registration function (180) is further configured to expose the endpoint related information segment for use by other nodes or instances of the telecommunications network (100), and wherein the user equipment service endpoint registration function (180) is further configured to perform at least one of the following based on the endpoint related information segment: --registering the specific application programming interface provided by the specific service endpoint (25), --Provides address information on how the specific service endpoint (25) can be accessed.

19. A computer-readable medium comprising instructions which, when executed on a computer, and / or on a user equipment (20), and / or on a user equipment service endpoint registration function (180), and / or on a network node of a telecommunications network (100), or partly on the user equipment (20), and / or partly on the user equipment service endpoint registration function (180), and / or partly on a network node of the telecommunications network (100), cause the computer and / or the user equipment (20) and / or the user equipment service endpoint registration function (180), and / or the network node of the telecommunications network (100) to perform the method according to any one of claims 1 to 16.

Images