Authentication of terminal entity and mobile network entity

Abstract

A method, an apparatus, and a computer program product for authentication between a mobile network entity and a terminal entity are provided. Such methods, apparatuses, and computer program products provided may include authentication and / or identification based on sending and / or receiving at least one security parameter and / or at least one authenticator.

Description

Technical Field

[0001] Embodiments of the present application relate to an apparatus and / or method for authentication of a terminal entity and a movable network entity. Background Art

[0002] The present disclosure as a whole relates to apparatus and / or methods for authentication involving at least one mobile network entity and a terminal entity.An example of such a mobile network entity may be a satellite deployed in a non-terrestrial network NTN.

[0003] <Example Communication System>

[0004] In various communication systems, at least one mobile network entity is deployed. Examples for mobile network entities may be non-terrestrial base stations, e.g. base stations provided on satellites and / or next generation NodeB gNBs. So far, the corresponding entities provided on satellites provide (complete) gNB functionality, i.e. the satellite comprises e.g. a gNB as an entity, which supports all necessary radio network layer (RNL) protocols.

[0005] Alternatively, the mobile network entity is not limited to a gNB provided at a satellite, but may also refer to such a gNB device that may be provided at an aircraft or a marine vessel (such as a ship) and correspondingly supports the required RNL protocol.

[0006] Some examples for scenarios including at least one mobile network entity provided at a satellite are described in the 3rd Generation Partnership Project (3GPP) TR 22.865 specification. For example, use cases for data exchange based on a store and forward concept (mobile oriented and / or mobile originated (MO)) or use cases for store and forward (mobile terminated (MT)) can be considered as example scenarios.

[0007] However, the example embodiments described in the present disclosure are not limited to such example scenarios or example communication systems, but for better readability, at least some of the terms used herein are also used in this specification.

[0008] In the above example, a store and forward (S&F) service for data exchange between a user equipment with satellite access and an application server, i.e., data delivery and / or reception, is considered, e.g. in a delay tolerant / non-real-time (such as the "Internet of Things" (IoT))-non-terrestrial network (NTN).

[0009] An example of establishing a connection between a mobile network entity and a terminal entity (such as a user equipment (UE)) is as follows: Figure 8As shown in . In such a scenario, a base station or gNB (referred to as SAT(gNB) 200 in some example embodiments) typically provided on a satellite may have a communication link to a core network (CN) or home network (HN) entity via a gateway (GW). In some example embodiments, the link between a mobile network entity and a core network or home network entity may be referred to as a feeder link. In some example embodiments, the core network or home network may be simply referred to as a core network. However, the core network may also be replaced (or represented) by a home network. In addition, the link between a mobile network entity and a terminal (such as a UE) may be referred to as a service link.

[0010] In an example related to NTN, the satellite includes a base station or gNB provided on the satellite (SAT(gNB) 200), which can move into the coverage of the UE (or vice versa, i.e., the terminal UE and the mobile entity SAT(gNB) are within or move into the coverage of each other). In such a scenario, it is also conceivable that the satellite is temporarily inaccessible, i.e., there is no available link to the core network. That is, when the corresponding base station or gNB on the satellite establishes a connection with the UE, the feeder link may not be available. In some embodiments, the connection between the corresponding base station or gNB on the satellite and the UE may be referred to as a radio resource control (RRC) connection and / or a service link. In this regard, the RRC connection and the service link may be used synonymously for a communication link or connection between a UE and a base station or a next generation NodeB (such as a gNB).

[0011] In known communication networks, the establishment of a (RRC) connection is usually followed by authentication of the UE and / or base station or gNB using entities in the core network. However, if there is no feeder link, i.e., no connection is available between the core network and the base station (gNB), authentication of the UE and / or base station cannot be performed using or based on entities in the core network. Therefore, after the establishment of the RRC connection, the UE and the base station gNB can communicate with each other, but no trusted (authenticated) connection or communication link is available between them.

[0012] In the above example communication system, as mentioned above, links between different devices and / or between a device and a core network may be (temporarily) unavailable, mainly because the base station or gNB is provided at a movable and / or mobile entity (such as a satellite, etc.). That is, in various scenarios, end-to-end connectivity may not be achieved between a terminal entity and an entity in the core network (which may include an application function in the core network).

[0013] Therefore, there is a need to improve such situations and provide authentication in situations where no end-to-end connection is available between the terminal entity and the entity in the core network. Summary of the invention

[0014] Various example embodiments are directed to addressing at least some of the above-mentioned difficulties and / or problems and disadvantages.

[0015] Therefore, at least some embodiments disclosed herein do solve this problem. Some example embodiments enable and / or implement authentication between a mobile network entity and a terminal entity and are described / disclosed below. According to at least some embodiments, the authentication can be considered as a local authentication because no core network entity is (directly) involved and / or because during authentication, no connection to the core network entity is required.

[0016] Various aspects of example embodiments are set out in the accompanying claims.

[0017] According to an exemplary aspect, a method is provided, comprising: in a scenario, wherein a link to a core network entity (400) is established in a mobile network entity (200), but a link to a terminal entity (100) is not established, and wherein the mobile network entity moves into a coverage area of ​​the terminal entity, allowing a link to be established between the mobile network entity and the terminal entity, and obtaining security parameters of the terminal entity; when the mobile network entity moves into the coverage area of ​​the terminal entity, providing at least the security parameters of the terminal entity to the mobile network entity.

[0018] According to at least some example embodiments, the security parameter of the terminal entity is an identifier of the terminal entity.

[0019] According to at least some example embodiments, obtaining further comprises: obtaining a shared key.

[0020] According to at least some example embodiments, the obtained shared key is generated using a key derivation function based on at least the shared secret.

[0021] According to at least some example embodiments, the acquired shared key is generated using a key derivation function based on a counter value and a shared secret, the counter value depending on the number of connection establishments between the terminal entity and the mobile network entity, or another mobile network entity.

[0022] According to at least some example embodiments, identifying the terminal entity is further based on a shared key.

[0023] According to at least some example embodiments, there is further provided: receiving data from a terminal entity at a mobile network entity; and decrypting the received data using the acquired shared key.

[0024] According to at least some example embodiments, there is further provided: buffering the decrypted data when the link to the core network entity (400) is established, and forwarding the decrypted data to the application via the link to the core network entity (400).

[0025] According to at least some example embodiments, obtaining also includes obtaining a plurality of unassigned terminal security parameters, and also providing: when decrypting the received data using a shared key, sending one of the plurality of unassigned terminal security parameters to the terminal entity, and using the shared key, optionally encrypting the terminal security parameter sent to the terminal.

[0026] According to at least some example embodiments, there is further provided that, in response to a connection between the terminal entity and the mobile network entity being established, a certificate of the mobile network entity is sent from the mobile network entity to the terminal entity.

[0027] According to at least some example embodiments, a method is provided, the method comprising: in a scenario, wherein a link to a core network entity (400) is established in a mobile network entity (200), but a link to a terminal entity (100) is not established, and wherein the mobile network entity moves into a coverage area of ​​the terminal entity, allowing a link to be established between the mobile network entity and the terminal entity, and obtaining security parameters of the terminal entity; when the mobile network entity moves into the coverage area of ​​the terminal entity, providing at least the security parameters of the terminal entity to the mobile network entity.

[0028] According to at least some example embodiments, providing further comprises obtaining a shared key, and providing the shared key to the mobile network entity.

[0029] According to at least some example embodiments, the shared key is generated using a key derivation function based on at least the shared secret.

[0030] According to at least some example embodiments, the method further comprises, in response to a connection between the mobile network entity and the terminal entity being established, incrementing a counter value, and generating a shared key using a key derivation function based on the counter value and the shared key.

[0031] According to at least some example embodiments, the method further includes receiving data.

[0032] According to at least some example embodiments, providing further comprises providing a plurality of unassigned terminal security parameters.

[0033] According to at least some example embodiments, a method is provided, the method comprising: in a scenario, wherein a terminal entity (100) has no established link to a movable network entity (200), the movable network entity moves into a coverage area of ​​the terminal entity, allowing a link to be established between the movable network entity and the terminal entity, and wherein the terminal entity has security parameters, sending a connection setup request from the terminal entity to the movable network entity including the security parameters, and establishing a connection between the terminal entity and the movable network entity based on the security parameters.

[0034] According to at least some example embodiments, the method further includes obtaining a shared secret, and generating the shared secret using a key derivation function based on at least the shared secret.

[0035] According to at least some example embodiments, the method further includes, in response to a connection between the mobile network entity and the terminal entity being established, incrementing a counter value, and generating a shared key based on the counter value and the shared key using a key derivation function.

[0036] According to at least some example embodiments, the method further comprises encrypting the data using the shared key, and sending the encrypted data to the mobile network entity.

[0037] According to at least some example embodiments, the method further comprises receiving another security parameter from the mobile network entity, and buffering the received security parameter.

[0038] According to at least some example embodiments, the method further comprises obtaining at least one of the root certificates issued from the certificate authentication and path, and verifying the received certificate of the mobile network entity using at least one of the root certificates issued from the certificate authentication and path.

[0039] According to at least some example embodiments, a method is provided, the method comprising: in a scenario, wherein a link to a mobile network entity (200) is established at a terminal entity (100), and wherein the terminal entity is provided with its own certificate, and information for verifying other certificates, sending a registration request to the mobile network entity, the mobile network entity including its own certificate, and an indication indicating support for authentication with the mobile network entity; receiving an authentication request from the mobile network entity including the certificate of the mobile network entity as a response to the registration request; and verifying the received certificate of the mobile network entity based on the information provided for verifying the other certificates.

[0040] According to at least some example embodiments, the terminal entity is also provided with its own asymmetric key pair, the asymmetric key pair comprising a public key and a private key, and the method further comprises: generating an authenticator by encrypting its own public key using its own private key, and sending the authenticator to the mobile network entity.

[0041] According to at least some example embodiments, the received authentication request further includes a public key of the mobile network entity, and the method further includes: encrypting data using the received public key of the mobile network entity, and sending further includes sending the encrypted data to the mobile network entity.

[0042] According to at least some example embodiments, a method is provided, the method comprising: in a scenario, wherein a mobile network entity (200) has not established a link to a core network entity (400) and has established a link to a terminal entity (100), and wherein the mobile network entity is provided with its own certificate and information for verifying other certificates, in response to receiving a registration request from the terminal entity, sending an authentication request to the terminal entity, the terminal entity including a first certificate and an indication indicating support for authentication with the mobile network entity, the authentication request including at least its own certificate; and verifying the received certificate of the mobile network entity based on the provided information for verifying other certificates.

[0043] According to at least some example embodiments, the method further comprises: receiving an authentication response including an authenticator; buffering the received authenticator and the first certificate; and forwarding the buffered authenticator and the buffered first certificate to the core network entity (400) when the link to the core network entity (200) is established.

[0044] According to at least some example embodiments, the mobile network entity is also provided with its own asymmetric key pair, the asymmetric key pair including a private key and a public key, and the sent authentication request also includes its own public key, the received authentication response also includes data, the method also includes: using its own private key, decrypting the received data and buffering the decrypted data, and forwarding also includes: forwarding the decrypted data to the core network entity (400) when the link to the core network entity (400) is established.

[0045] According to at least some example embodiments, a method is provided, the method comprising: in a scenario, wherein a core network entity (400) is provided with information for verifying a certificate, receiving a message from a mobile network entity (200) via a gateway (300), the message comprising a certificate and an authenticator of a terminal entity (100); verifying the certificate of the terminal entity, wherein successful verification comprises obtaining a public key of the terminal entity, decrypting the authenticator using the obtained public key of the terminal entity, and comparing the decrypted authenticator with the obtained public key of the terminal entity.

[0046] According to at least some example embodiments, the received message also includes data, and the method further includes forwarding the data to an application in response to a scenario in which the decrypted authenticator matches the obtained public key of the terminal entity when the decrypted authenticator is compared with the obtained public key of the terminal entity.

[0047] According to at least some example embodiments, the mobile network entity is a non-terrestrial network entity provided on one of a satellite or an aircraft, or at a maritime vessel.

[0048] According to at least some example embodiments, an apparatus is provided, the apparatus comprising at least one processor (210), at least one memory (220) including computer program code, and at least one interface (230), the at least one interface (230) being configured to communicate with at least one other apparatus, wherein in a scenario, wherein a link to a core network entity (400) is established at a mobile network entity (200), but a link to a terminal entity (100) is not established, and wherein the mobile network entity moves into a coverage area of ​​the terminal entity, allowing a link to be established between the mobile network entity and the terminal entity, the at least one processor, the at least one memory and the computer program code, and the at least one interface being configured to cause the apparatus to execute: obtaining security parameters of at least the terminal entity at the mobile network entity; establishing a connection between the terminal entity and the mobile network entity based on the security parameters of the terminal entity in response to receiving a connection setup request including the security parameters of the terminal entity; and identifying the terminal entity based on a comparison of the security parameters of the terminal entity received when establishing the connection with the acquired security parameters of the terminal entity.

[0049] According to at least some example embodiments, at least one processor, at least one memory and computer program code, and at least one interface are configured to cause the apparatus to further perform: obtaining a shared key.

[0050] According to at least some example embodiments, the obtained shared key is generated using a key derivation function based on at least the shared secret.

[0051] According to at least some example embodiments, the acquired shared key is generated using a key derivation function based on a counter value and a shared secret, the counter value depending on the number of connection establishments between the terminal entity and the mobile network entity, or another mobile network entity.

[0052] According to at least some example embodiments, identifying the terminal entity is further based on a shared key.

[0053] According to at least some example embodiments, at least one processor, at least one memory and computer program code, and at least one interface are configured so that the device further performs: receiving data from a terminal entity at a mobile network entity, and decrypting the received data using the acquired shared key.

[0054] According to at least some example embodiments, at least one processor, at least one memory and computer program code, and at least one interface are configured such that the device further performs: when the link to the core network entity (400) is established, buffering the decrypted data, and forwarding the decrypted data to the application via the link to the core network entity (400).

[0055] According to at least some example embodiments, at least one processor, at least one memory and computer program code, and at least one interface are configured to cause the device to further perform: obtaining multiple unassigned terminal security parameters, and when decrypting received data using a shared key, sending one of the multiple unassigned terminal security parameters to a terminal entity, and using the shared key, optionally encrypting the terminal security parameter sent to the terminal.

[0056] According to at least some example embodiments, at least one processor, at least one memory and computer program code, and at least one interface are configured to cause the device to further execute: in response to a connection between the terminal entity and the mobile network entity being established, sending a certificate of the mobile network entity from the mobile network entity to the terminal entity.

[0057] According to at least some example embodiments, a device is provided, the device comprising at least one processor (410), at least one memory (420) including computer program code, and at least one interface (430), the at least one interface (430) being configured to communicate with at least one other device, wherein in a scenario, a link to a core network entity (400) is established in a mobile network entity (200), but a link to a terminal entity (100) is not established, and wherein the mobile network entity moves into a coverage area of ​​the terminal entity, allowing a link to be established between the mobile network entity and the terminal entity, the at least one processor and at least one memory and computer program code, and at least one interface are configured to cause the device to execute: obtaining security parameters of the terminal entity; and providing at least the security parameters of the terminal entity to the mobile network entity when the mobile network entity moves into the coverage area of ​​the terminal entity. The at least one processor and at least one memory and computer program code, and at least one interface are configured to cause the device to execute: obtaining security parameters of the terminal entity; and providing at least the security parameters of the terminal entity to the mobile network entity when the mobile network entity moves into the coverage area of ​​the terminal entity.

[0058] According to at least some example embodiments, at least one processor with at least one memory and computer program code, and with at least one interface are configured to cause the apparatus to further perform: obtaining a shared key, and providing the shared key to the mobile network entity.

[0059] According to at least some example embodiments, the shared key is generated using a key derivation function based on at least the shared secret.

[0060] According to at least some example embodiments, at least one processor, at least one memory and computer program code, and at least one interface are configured to cause the apparatus to further perform: in response to a connection between the mobile network entity and the terminal entity being established, incrementing a counter value, and generating a shared key using a key derivation function based on the counter value and the shared key.

[0061] According to at least some example embodiments, at least one processor, at least one memory and computer program code, and at least one interface are configured to cause the apparatus to further perform: receiving data.

[0062] According to at least some example embodiments, at least one processor with at least one memory and computer program code, and with at least one interface are configured to cause the apparatus to further perform: providing a plurality of unassigned terminal security parameters to a mobile network entity.

[0063] According to at least some example embodiments, an apparatus is provided, the apparatus comprising at least one processor (110), at least one memory (120) including computer program code, and at least one interface (130), the at least one interface (130) being configured to communicate with at least another apparatus, wherein in a scenario, wherein a terminal entity (100) has not established a link to a mobile network entity (200), the mobile network entity moves into a coverage area of ​​the terminal entity, allowing a link to be established between the mobile network entity and the terminal entity, and wherein the terminal entity has security parameters, the at least one processor, the at least one memory and the computer program code, and the at least one interface being configured such that the apparatus further executes: sending a connection setup request from the terminal entity to the mobile network entity including the security parameters, and establishing a connection between the terminal entity and the mobile network entity based on the security parameters.

[0064] According to at least some example embodiments, at least one processor with at least one memory and computer program code, and with at least one interface are configured to cause the apparatus to further perform: obtaining a shared key, and generating the shared key using a key derivation function based on at least the shared secret.

[0065] According to at least some example embodiments, at least one processor and at least one memory and computer program code, and at least one interface are configured to cause the apparatus to further perform: in response to a connection between the mobile network entity and the terminal entity being established, incrementing a counter value, and generating a shared key based on the counter value and the shared key using a key derivation function.

[0066] According to at least some example embodiments, at least one processor with at least one memory and computer program code, and with at least one interface are configured to cause the apparatus to further perform: encrypting data using a shared key, and sending the encrypted data to a mobile network entity.

[0067] According to at least some example embodiments, at least one processor with at least one memory and computer program code, and with at least one interface are configured to cause the apparatus to further perform receiving another security parameter from the mobile network entity and buffering the received security parameter.

[0068] According to at least some example embodiments, at least one processor, at least one memory and computer program code, and at least one interface are configured to cause the apparatus to further perform obtaining at least one of the root certificates issued from the certificate authentication and path, and verifying the received certificate of the mobile network entity using at least one of the root certificates issued from the certificate authentication and path.

[0069] According to at least some example embodiments, a device is provided, the device comprising at least one processor (110), at least one memory (120) including computer program code, and at least one interface (130), the at least one interface (130) being configured to communicate with at least another device, wherein in a scenario, wherein a link to a mobile network entity (200) is established at a terminal entity (100), and wherein the terminal entity is provided with its own certificate and information for verifying other certificates, the at least one processor, the at least one memory and the computer program code, and the at least one interface are configured to cause the device to execute: sending a registration request to the mobile network entity, the mobile network entity including its own certificate and an indication indicating support for authentication with the mobile network entity; receiving an authentication request from the mobile network entity including the certificate of the mobile network entity as a response to the registration request; and verifying the received certificate of the mobile network entity based on the information provided for verifying the other certificates.

[0070] According to at least some example embodiments, the terminal entity is also provided with its own asymmetric key pair, the asymmetric key pair comprising a public key and a private key, and at least one processor, at least one memory and computer program code, and at least one interface are configured to cause the apparatus to further perform: generating an authenticator by encrypting its own public key using its own private key, and sending the authenticator to the mobile network entity.

[0071] According to at least some example embodiments, the received authentication request also includes a public key of the mobile network entity, and at least one processor, at least one memory and computer program code, and at least one interface are configured to cause the device to further perform: encrypting data using the received public key of the mobile network entity, and sending the encrypted data to the mobile network entity.

[0072] According to at least some example embodiments, a device is provided, the device comprising at least one processor (210), at least one memory (220) including computer program code, and at least one interface (230), the at least one interface (230) being configured to communicate with at least another device, wherein in a scenario, a mobile network entity (200) does not establish a link to a core network entity (400) and establishes a link to a terminal entity (100), and wherein the mobile network entity is provided with its own certificate and information for verifying other certificates, the at least one processor and the at least one memory and the computer program code, and the at least one interface being configured to cause the device to execute: in response to receiving a registration request from the terminal entity, sending an authentication request to the terminal entity, the terminal entity including a first certificate and an indication indicating support for authentication with the mobile network entity, the authentication request including at least its own certificate; and verifying the received certificate of the mobile network entity based on the provided information for verifying other certificates.

[0073] According to at least some example embodiments, at least one processor, at least one memory and computer program code, and at least one interface are configured such that the apparatus further performs: receiving an authentication response including an authenticator; buffering the received authenticator and the first certificate; and forwarding the buffered authenticator and the buffered first certificate to the core network entity (400) when the link to the core network entity (200) is established.

[0074] According to at least some example embodiments, the mobile network entity is also provided with its own asymmetric key pair, the asymmetric key pair comprising a private key and a public key, and the sent authentication request also comprises its own public key, the received authentication response also comprises data, and at least one processor and at least one memory and computer program code, and at least one interface are configured so that the device further performs: using its own private key, decrypting the received data and buffering the decrypted data, and forwarding the decrypted data to the core network entity (400) when the link to the core network entity (400) is established.

[0075] According to at least some example embodiments, an apparatus is provided, the apparatus comprising at least one processor (410), at least one memory (420) comprising computer program code, and at least one interface (430), the at least one interface (430) being configured to communicate with at least another apparatus, wherein in a scenario, a core network entity (400) is provided with information for verifying a certificate, the at least one processor, the at least one memory and the computer program code, and the at least one interface being configured to cause the apparatus to perform: receiving a message from a mobile network entity (200) via a gateway (300), the message comprising a certificate and an authenticator of a terminal entity (100); verifying the certificate of the terminal entity, wherein successful verification comprises obtaining a public key of the terminal entity, decrypting the authenticator using the obtained public key of the terminal entity, and comparing the decrypted authenticator with the obtained public key of the terminal entity.

[0076] According to at least some example embodiments, the received message also includes data, and at least one processor, at least one memory and computer program code, and at least one interface are configured to cause the device to further perform: in response to a scenario in which the decrypted authenticator matches the obtained public key of the terminal entity when the decrypted authenticator is compared with the obtained public key of the terminal entity, forwarding the data to an application.

[0077] According to at least some example embodiments, the mobile network entity is a non-terrestrial network entity provided on one of a satellite or an aircraft, or at a maritime vessel.

[0078] According to at least some example embodiments, a computer program product is provided, the computer program product comprising a computer executable computer program code, the computer program product being configured to cause the computer to perform any of the disclosed methods when the program is run on a computer.

[0079] According to at least some example embodiments, a computer program product comprises a non-transitory computer readable medium on which a computer executable computer program code is stored and / or wherein the program is directly loaded into an internal memory of a computer or a processor thereof.

[0080] Any of the above aspects enables (local) authentication without an end-to-end connection between a terminal entity and an entity in a core network, thereby solving at least some of the problems and disadvantages associated with the prior art.

[0081] As an example embodiment, methods, apparatus and computer program codes configured and / or adapted for providing (local) authentication in the absence of an end-to-end connection between a terminal entity and an entity in a core network are provided. More specifically, as an example embodiment, measures and mechanisms for implementing (local) authentication and / or mutual authentication of the entities and / or apparatuses involved are provided.

[0082] By means of at least some of the above embodiments, one or more of the following advantages can be obtained:

[0083] - Authenticating a terminal entity (such as a user equipment) even if a communication link between the terminal entity and an entity in the core network is (temporarily) unavailable and / or an end-to-end connection is unavailable;

[0084] - Authenticating a mobile network entity even if a communication link between the terminal entity and an entity in the core network is (temporarily) unavailable and / or an end-to-end connection is unavailable;

[0085] - identifying a terminal entity (such as a user equipment) even if a communication link between the terminal entity and an entity in the core network is (temporarily) unavailable and / or an end-to-end connection is unavailable;

[0086] - establishing a trusted and / or authenticated RRC connection between the terminal entity and the mobile network entity even if (temporarily) end-to-end connectivity between the terminal entity and entities in the core network is not available;

[0087] - integrity checking of the exchanged data even if the communication link between the terminal entity and the entity in the core network is (temporarily) unavailable and / or the end-to-end connection is unavailable;

[0088] - Generate a shared key, at least in some scenarios, for authentication, even if the communication link is (temporarily) unavailable and / or the end-to-end connection is unavailable;

[0089] - Securely exchange, i.e. forward and / or receive data, even if the communication link between the terminal entity and the entity in the core network is (temporarily) unavailable and / or the end-to-end connection is unavailable, based on a store and forward (S&F) architecture or concept that may be deployed in, for example, an NTN scenario or other scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0090] In the following, the present disclosure will be described in more detail by way of non-limiting examples with reference to the accompanying drawings, in which:

[0091] exist Figure 1 A signaling sequence of an exemplary mechanism for local authentication between a terminal entity and a movable network entity is illustrated in FIG.

[0092] exist Figure 2 A signaling sequence of another exemplary mechanism for local authentication between a terminal entity and a mobile network entity is illustrated in FIG.

[0093] exist Figure 3 A signaling sequence of another exemplary mechanism for local authentication between a terminal entity and a mobile network entity is illustrated in FIG.

[0094] exist Figure 4 An alternative illustration of a terminal device, such as a user equipment UE, according to an example embodiment is depicted in FIG.

[0095] exist Figure 5 An alternative illustration of a movable entity device (e.g., SAT(gNB)) according to an example embodiment is depicted.

[0096] exist Figure 6 An alternative diagram of a core network entity arrangement (eg, a CN entity) according to an example embodiment is depicted in FIG.

[0097] exist Figure 7 The middle figure shows a block diagram illustrating the input and output of a key derivation function (KDF) (which may be implemented as program code or hardwired circuitry or modules) according to at least some example embodiments.

[0098] exist Figure 8 The connection establishment example mentioned in the introduction is illustrated in Figure . DETAILED DESCRIPTION

[0099] The present disclosure is described herein with reference to certain non-limiting examples and embodiments that are presently considered to be conceivable. It will be appreciated by those skilled in the art that the present disclosure is not limited to these examples and can be more broadly applied.

[0100] Note that the following description of the present disclosure and its embodiments mainly refers to specifications used as non-limiting examples of certain exemplary network configurations and deployments. That is, the present disclosure and its embodiments are mainly described with respect to 3GPP specifications, which are used as non-limiting examples of certain exemplary network configurations and deployments. Therefore, the description of the example embodiments given herein specifically refers to terms directly related thereto. Such terms are used only in the context of the proposed non-limiting examples and naturally do not limit the present disclosure in any way. On the contrary, any other communication or communication-related system deployment, etc. may also be used as long as it meets the features described herein.

[0101] In the following, several variants and / or alternatives are used to describe various embodiments and implementations of the present disclosure and aspects or embodiments thereof. It should generally be noted that, according to certain needs and constraints, all of the described variants and / or alternatives may be provided individually or in any possible combination (including combinations of individual features of various variants and / or alternatives).

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

[0103] In addition, a computer program including instructions may be provided, which, when executed by the device, causes the device to perform each method step. The instructions may also be stored on a non-transitory computer-readable medium. The term "non-transitory" as used herein is a limitation on the medium itself (i.e., tangible, not a signal), rather than a limitation on the persistence of data storage (e.g., random access memory (RAM) and read-only memory (ROM)).

[0104] As used in this application, the term "obtaining corresponding data" may refer to one of the following:

[0105] a) received within the corresponding entity, but not generated by the corresponding entity, and

[0106] b) obtaining corresponding data from a connected entity (such as a server), and

[0107] c) generating corresponding data within the corresponding entity. In this context, obtaining the corresponding item or data may also refer to loading or obtaining previously stored items or data. Any of receiving, obtaining, generating may be triggered by internal or external events and / or conditions, such as, for example, receiving a message or a program call or program instruction stored in at least one memory and executed by at least one processor.

[0108] According to example embodiments, generally speaking, corresponding methods and apparatus for enabling / implementing (local) authentication are provided as described below.

[0109] <First Embodiment>

[0110] Figure 1 A first embodiment of a mechanism for (local) authentication between a terminal entity, such as a user equipment (UE), and a mobile network entity is illustrated. Figure 1 In the figure, a signaling sequence of an exemplary mechanism is illustrated, the mechanism comprising a method and corresponding apparatus for performing (local) authentication between a device (eg a terminal entity such as a UE) and a movable network entity.

[0111] In at least some example embodiments, such as in the first embodiment, a satellite deployed in a non-terrestrial network (NTN) may be referred to as an example of a mobile network entity. In at least some examples, the mobile network entity may therefore be referred to as a SAT (gNB). However, the SAT (gNB) represents only an example, and the present disclosure is not limited thereto. Instead, the present disclosure may also be applicable to a communication system in which the mobile network entity may be represented by a device that may be provided on an aircraft or at a marine vessel (such as a ship), and correspondingly supports the corresponding RNL protocol deployed and / or required in such a scenario.

[0112] Furthermore, some example embodiments may relate generally to a store and forward (S&F) architecture or concept that may be deployed, for example, in an NTN scenario or other scenario. The S&F architecture may facilitate situations where a feeder link (between a mobile network entity and a core network (one or more entities)) and / or a gateway connecting a core network with a mobile network entity may be temporarily unavailable. Store and forward in the sense of the present disclosure only relates to the ability to store received data and to later forward the stored data.

[0113] Although in some example embodiments, it refers to user equipment and / or IoT devices, the corresponding mechanism is applicable to any kind of user equipment (UE), basically any device that can establish a connection with a mobile network entity and can send and / or receive data, such as a phone, a car, an IoT device, a robot, or any other UE device with cellular protocol stack support. Such devices and other examples corresponding to UE may also be referred to as terminal entities.

[0114] for Figure 1The method and apparatus shown in do not require prior authentication and end-to-end connection between a terminal entity and an entity in a core network (which may include application functions in the core network). That is, the mechanism described in this example embodiment is applicable to any scenario in which a mobile network entity provided on a satellite (such as a base station or next generation NodeB, gNB, which may be referred to as, for example, SAT (gNB) 200) moves into the coverage of another entity (such as UE 100). Although the present disclosure and at least some example embodiments are applicable to any kind of terminal entity that can establish a connection with a mobile network entity, at least in some example embodiments, for simplicity, it may be referred to as a terminal entity UE 100. As described above, at least some example embodiments are applicable to any kind of mobile network entity that can be provided at an aircraft or a marine vessel (such as a ship) and correspondingly supports the required RNL protocol, that is, any device. Nevertheless, for descriptive reasons and simplicity in an example communication system consistent with a non-terrestrial network, the mobile network entity may be referred to as SAT (gNB) 200. However, this does not limit the example embodiments to such a SAT(gNB) 200, and as described above, the example embodiments including such a SAT(gNB) 200 are not limited to non-terrestrial networks, but for better readability, at least some of the terms used herein are also used in the present description.

[0115] Throughout the drawings, entities involved in signaling are illustrated and represented as boxes 100 (UE), 200 (SAT / gNB), 300 (gateway GW), 400 (core network CN entity) and 500 (application function). The signals exchanged between them are marked by arrows S* illustrated in the horizontal direction. The processing performed by the corresponding entities is illustrated as boxes in the vertical direction, below the corresponding entities. The processing sequence is usually (but not necessarily always) represented in the vertical direction of the drawing. The boxes in the dashed lines indicate situations or conditions where certain links or connections are generally available or unavailable.

[0116] In general, both or only one of the UE 100 and the SAT (gNB) 200 may be pre-configured with its own certificates, such as Figure 1 As shown in steps S1101 and S1201, the certificate of the user is previously issued by a certificate authority (CA). Figure 1As illustrated in steps S1101 and S1201 of , respectively, both or only one of the UE 100 and the SAT (gNB) 200 may also be pre-configured with a root CA certificate as information for verifying other certificates. The root CA certificate may include or be provided with a corresponding root path as information for verifying other certificates. Information for verifying other certificates may also be referred to as a chain of trust. In at least some example embodiments, the corresponding certificate and / or information for verifying other certificates may be provided via / from a public CA, or via / from a local CA, which may be any known CA.

[0117] In addition, UE 100 and SAT (gNB) 200 may each be pre-configured with their own asymmetric key pair, which includes a public key and a private key (but omitted in the illustration of S1101 and / or S1201).

[0118] After the RRC connection between UE 100 and SAT (gNB) 200 is established, i.e., an untrusted connection is available, Figure 1 In step S1102, UE 100 Figure 1 , a registration request is sent to the SAT (gNB) 200. The registration request includes an indication that (local) authentication using a mobile network entity is supported. Such an indication may be included at least in an existing field of an existing header, or in a new field of an existing header, or in a new header. In addition, the registration request also includes the UE's own certificate. However, given that the connection is not protected or trusted at this time, preferably no security parameters are included in the registration request.

[0119] After receiving a registration request (S1102) with an indication indicating support for (local) authentication using a mobile network entity, in response thereto, the SAT (gNB) 200 sends an authentication request to the UE 100, wherein according to some example embodiments such as the first embodiment, the authentication request includes the SAT (gNB) 200's own certificate (S1202).

[0120] In the authentication request S1202, the SAT (gNB) 200 may also share, ie, send its public key to the UE 100. Alternatively, the SAT (gNB) 200 may also share its public key based on or via other mechanisms or messages independent of the authentication request.

[0121] After receiving the corresponding messages (registration request (S1102) and authentication request (S1202)), according to at least the first exemplary embodiment, both the UE 100 and the SAT (gNB) 200 use the information used to verify the other certificates in steps S1103 and S1203, respectively, to verify the received corresponding certificates. In this regard, the SAT (gNB) 200 also stores the UE's certificate in a memory (S1203).

[0122] At least in the example according to the first exemplary embodiment, as described with respect to steps S1101 and S1201, the UE 100 and the SAT (gNB) 200 are each pre-configured with their own certificates, as well as information for verifying the other's certificates. The corresponding transmission and verification of the certificates of the pre-configured UE 100 and the SAT (gNB) 200 allow mutual authentication.

[0123] Alternatively, only one of the UE 100 and the SAT (gNB) 200 may be pre-configured with its own certificate, and the other of the UE 100 and the SAT (gNB) 200 may be pre-configured with information for verifying the other certificate. This still allows at least one-sided authentication.

[0124] After verifying the certificate of SAT(gNB)200 in step S1103, in step S1104, UE 100 uses the public key of SAT(gNB)200 to encrypt data (such as a message including a payload), which will be sent to an application or any other entity in the core network or home network. The type of data or its source is irrelevant, such as the embodiments and authentication methods described herein. By way of example only, in the case where the terminal UE is an IoT terminal, the message / payload may contain measurement data of a sensor provided at the terminal, and the measurement results are reported wirelessly.

[0125] Additionally, the UE 100 generates an authenticator by applying its own private key to its public key in step S1104. That is, the authenticator is encrypted using the UE's private key, and after encrypting the UE's public key, it becomes the UE's public key.

[0126] In step S1105, the UE 100 sends a message including the generated authenticator and the encrypted (payload) data to the SAT (gNB) 200. The message including the generated authenticator and the encrypted data may also be referred to as an authentication response.

[0127] After receiving the authentication response, in step S1204, the SAT (gNB) 200 uses its own private key to decrypt the received data and stores or buffers the decrypted data in a memory (not shown here). In addition, the SAT (gNB) 200 also stores the received authenticator in step S1204.

[0128] Additionally, in step S1205, SAT(gNB)200 sends a registration response after verifying the UE's certificate in step S1203.

[0129] At some point, the connection between the SAT (gNB) 200 and the core network (also called the feeder link) will be available (again). When the feeder link is available, the SAT (gNB) 200 still stores the authenticator, the decrypted data and the UE's certificate in memory.

[0130] When the feeder link to the core network is available (again), for example, via the gateway GW 300, the SAT (gNB) 200 sends a message N1 to an entity in the core network 400 via the GW 300 in step S1206, the message N1 including the authenticator, the decrypted data and the certificate of the UE. Sending the message N1 may also be referred to as sending a registration request or forwarding a received registration request.

[0131] In addition, entities in core network 400 are pre-configured with information for verifying other certificates (S1401). For example, entities in core network 400 may be pre-configured with a root CA certificate and / or a corresponding root path.

[0132] Subsequently, in step S1402, the entity in the core network 400 according to at least the first exemplary embodiment will use the information for verifying other certificates to verify the certificate of the UE received in the message N1. If the verification of the certificate of the UE is successful, the entity in the core network 400 may also use the information for verifying other certificates as the expected public key of the UE to obtain the public key of the UE. If the verification of the certificate of the UE is unsuccessful, the corresponding registration request will not be accepted and / or deleted.

[0133] In addition, if the UE's certificate verification is successful, then in step S1402, the entity in the core network 400 uses the obtained public key (i.e., the expected public key of the UE) to decrypt the received authenticator. The decrypted authenticator is then compared with the expected public key of the UE in step S1402, and if the decrypted authenticator matches the expected public key of the UE, the UE is successfully authenticated. The reason is that the entity in the core network 400 implicitly verifies the proof of possession, because the UE 100 that generates the authenticator needs to possess the private key corresponding to the public key of the UE obtained when verifying the successfully authenticated certificate.

[0134] In at least some example embodiments, the entity in core network 400 may be an access and mobility management function (AMF), but alternatively, the entity in core network 400 may also be any other entity in the core network / any other entity of the core network, any other entity being able to verify the certificate of the UE and forward the data to the corresponding application. For example, the entity in core network 400 may also be an entity that is communicatively connected to the AMF via the core network.

[0135] If the decrypted authenticator matches the expected public key of the UE, that is, if the UE is successfully authenticated, then in step S1403, the entity in the core network 400 will also forward the data received from the SAT (gNB) 200 to the corresponding target application, which may be located in the core network or the home network or connected to the core network or the home network.

[0136] With the help of Figure 1 At least some methods and corresponding apparatus for performing (local) authentication between devices described herein can perform initial (local) authentication and mutual authentication between a user equipment and a mobile network entity despite the (temporary) unavailability of an end-to-end connection between the terminal entity and an entity in the core network. Furthermore, a final authentication can be performed in the core network. As described above, an integrity check of the exchanged data can also be performed in at least the first exemplary embodiment.

[0137] In this way, data can be sent from the user equipment to the application in the core network or the home network via a secure and trusted connection via the mobile network entity without establishing an end-to-end connection between the terminal entity (such as the user equipment) and the entity or application in the core network or the home network via the mobile network entity (e.g., SAT(gNB) 200).

[0138] In this regard, those skilled in the art also understand that in a storage and forwarding service or architecture, for data exchange, that is, data transmission and / or reception, such as with respect to Figure 1 The first example embodiment described does not require an end-to-end connection between the terminal entity and the core network entity (which may include application functions in the core network) to securely send data from the terminal entity to an entity or application in the core network.

[0139] <Second Embodiment>

[0140] Figure 2 A second embodiment of a mechanism for (local) authentication between an example terminal entity, such as a user equipment (UE), and a mobile network entity is illustrated. Figure 2In the figure, according to a second embodiment, a signaling sequence of an exemplary mechanism is illustrated, the exemplary mechanism comprising a method and corresponding apparatus for performing (local) authentication between apparatuses such as a terminal entity (such as a UE) and a movable network entity.

[0141] In at least some example communication systems involving at least one mobile network entity, the at least one mobile network entity being a base station or next generation NodeB, gNB, such as a base station or gNB in ​​a non-terrestrial network (which may be referred to as SAT(gNB) 200, for example), it may happen that a terminal entity such as a user equipment (UE) and the mobile network entity are disconnected after an initial authentication between the UE and the mobile network entity or an entity in a core network (CN) 400 has been completed.

[0142] In at least some example embodiments, such as in the second embodiment, a satellite deployed in a non-terrestrial network NTN may be referred to as an example of a mobile network entity. However, the present disclosure is not limited thereto. Instead, the present disclosure may also be applicable to a communication system, in which a mobile network entity may be represented by a device, which may be provided at an aircraft or a marine vessel (such as a ship), and correspondingly supports the required RNL protocol.

[0143] In addition, some example embodiments may generally relate to a store and forward (S&F) service and / or architecture for data exchange (i.e., data delivery and / or reception), which may be deployed, for example, in an NTN scenario or other scenario. The S&F architecture may facilitate situations where a feeder link (between a mobile network entity and a core network (one or more entities)) and / or a gateway connecting the core network with the mobile network entity may be temporarily unavailable.

[0144] Although in some example embodiments, it is referred to as a user equipment and / or an IoT device as an example device, the corresponding mechanism is applicable to any kind of user equipment (UE), and basically every device that can establish a connection with a mobile network entity and can send and / or receive data, such as a phone, a car, an IoT device, a robot, or any other UE device with cellular protocol stack support. Such devices and other examples corresponding to UE may also be referred to as terminal entities.

[0145] As described above, at least some example embodiments are applicable to any kind of mobile network entity, i.e., any device, that can be provided at an aircraft or a marine vessel (such as a ship) and that correspondingly supports the required RNL protocol. Nevertheless, for descriptive reasons and simplicity in an example communication system consistent with a non-terrestrial network, the mobile network entity may be referred to as a SAT (gNB) 200. However, this does not limit the example embodiments to such a SAT (gNB) 200, and as described above, example embodiments including such a SAT (gNB) 200 are not limited to non-terrestrial networks, but for better readability, at least some of the terms used herein are also used in the present description.

[0146] Throughout the drawings, entities involved in signaling are illustrated and represented as boxes 100 (UE), 200 (SAT (gNB)), 300 (gateway GW), 400 (core network CN entity) and 500 (application function). Signals exchanged between processing steps are represented by arrows S* illustrated in the horizontal direction. The processing performed by the respective entities is illustrated as boxes below the respective entities in the vertical direction. The processing sequence is usually (but not necessarily always) represented in the vertical direction of the drawing. Boxes in dashed lines indicate situations or conditions where certain links or connections are generally available or unavailable.

[0147] For re-authentication after initial authentication between the UE and entities in the core network (CN) 400, it can be assumed that Figure 2 As shown in steps S2101 and S2401 of the present invention, the UE and the entities in the core network 400 are configured with a shared secret RAND established or shared respectively in a previous and / or initial authentication. SAT 、Counter value COUNT SAT (to be introduced later) and the key K AMF Key K AMF The key K may be generated within the initial authentication, for example based on the functionality of the Access and Mobility Management Function (AMF). AMF The derivation or generation of may be according to any known generation method as defined in, for example, 3GPP TS 33.501 Release 15, version 15.4.0, but may also be replaced by any other shared key generation or derivation.

[0148] Furthermore, it can be assumed that for re-authentication after initial authentication between the UE 100 and an entity in the core network (CN) 400, such as Figure 2As shown in steps S2101 and S2401, UE 100 is configured with security parameters as security parameters of the terminal entity, for example, it is configured with an identifier (UE_SAT_ID) as an identifier of the terminal entity or is configured with a password or some other code or signature that is also known to the entity in the core network 400. Although the identifier and password are only examples of security parameters, in some embodiments, for the sake of responsibility, it may simply refer to the identifier and / or the identifier of the terminal entity. However, it is to be understood that the present disclosure is not limited to such an identifier, and other security parameters may also be applied. That is, the identifier (UE_SAT_ID) is respectively assigned or distributed to UE 100 during or after a previous authentication and / or a previous connection establishment between the terminal entity and the mobile network entity, and the entity in the core network 400 knows the identifier (UE_SAT_ID) or can obtain the identifier from, for example, AMF. In addition, the entity in the core network 400 has stored or can obtain from another entity a plurality of terminal entity identifiers that are not assigned to any UE or terminal entity at the corresponding time. UE_SAT_ID, shared key RAND SAT and the counter value COUNT SAT Assigned in a secure manner during initial authentication. For example, UE_SAT_ID, shared key RAND SAT 、Counter value COUNT SAT Can be assigned during initial authentication in the Non-Access Stratum NAS security mode procedure.

[0149] In at least some example embodiments, such as the second embodiment, a mechanism for (local) authentication between a terminal entity (i.e., UE 100) and a mobile network entity (i.e., SAT (gNB) 200) is provided. Figure 2 In the figure, an exemplary mechanism sequence for (local) authentication between a terminal entity and a movable network entity according to a second embodiment is illustrated. In the second embodiment, it is also assumed that it can be foreseen or expected when the movable network entity moves into the coverage of a UE or terminal entity, which has been authenticated at the core network but is temporarily not connected to a movable network entity, such as SAT (gNB) 200. This may occur at any time when a connection (i.e., a communication link between SAT (gNB) 200 and the core network is available but not connected, i.e., a communication link between movable network entities is available but not connected, such as a communication link between SAT (gNB) 200 and UE 100 is available but not connected, the communication link is also called a feeder link) is available. At this time, before the connection between SAT (gNB) 200 and the core network may be lost due to the movement of the movable network entity, the entities in the core network 400 according to at least some example embodiments (such as the second embodiment) are in Figure 2In step S2402b, the shared key K is provided to SAT(gNB) 200 SAT The shared key KSAT can be used with the shared key RAND SAT 、Counter value COUNT SAT (to be introduced later) and the key K AMF Generated as input to the key derivation function KDF (S2402a). Figure 7 A block diagram is shown, which illustrates the input of KDF (RAND SAT 、COUNT SAT and K AMF ) and output (shared key K SAT ). In this regard, any known or new KDF may be used, such as, for example, the KDF for key derivation in version 15.4.0 of 3GPP TS 33.501 Release 15, but other known or new key derivation functions may also be used.

[0150] In step S2402a, a shared key K is generated. SAT Then, in step S2402b, the entity in the core network 400 generates the shared key K SAT Sent to the mobile network entity SAT (gNB) 200. Additionally, in step S2402b, the entity in the core network 400 also sends the identifier (UE_SAT_ID) of the UE 100 to the SAT (gNB) 200.

[0151] When SAT (gNB) 200 moves into the coverage of UE 100 (or alternatively, if UE 100 moves into the coverage of SAT (gNB) 200), a radio resource control RRC connection (i.e., a communication link also referred to as a service link) between SAT (gNB) 200 and UE 100 becomes available and can be established in step S2001.

[0152] In response to (re)connection to the SAT (gNB) 200 or any other mobile network entity, such as a mobile base station or a next generation NodeB, gNB, i.e., after the RRC connection between the SAT (gNB) 200 and the UE 100 is established, the UE 100 in step S2102 sets the previously mentioned counter value COUNT SAT During initial authentication between UE 100 and an entity in the core network, the counter value COUNT SAT is initialized to zero and increases by 1 for each connection establishment between the UE 100 and a mobile network entity, which connects the UE 100 to the core network or stores and forwards data from the UE 100 to the core network.

[0153] Therefore, the entities in the core network 400 (configured with the shared secret RAND SAT 、Counter value COUNT SAT and key K AMF ) also tracks the connection establishment between the UE 100 and any mobile network entity. For example, due to an entity in the core network 400, and the counter value COUNT SAT The shared key K provided by the mobile network entity is used as input SAT , which may occur. When generating a shared key K for establishing a connection between the UE 100 and the mobile network entity SAT Previously, the entity in the core network 400 also increased the counter value by 1.

[0154] Similar to the entities in the core network 400, the UE 100 in step S2102 uses Figure 7 The shared key RAND is shown SAT 、Counter value COUNT SAT and key K AMF As input to the key derivation function KDF to generate the shared key K SAT As previously described with respect to key generation performed by entities in the core network 400, any known or new KDF may be used, such as, for example, the KDF for key derivation in version 15.4.0 of 3GPP TS 33.501 Release 15, but other known or new key derivation functions may also be used.

[0155] In this way, the entities in the UE 100 and the core network 400 will always use the updated but synchronized counter value COUNT SAT As the shared key K SAT The KDF input during the key generation (S2102, S2402) of UE 100 makes it possible for a new shared key K to be established for each connection between UE 100 and a mobile network entity (such as SAT (gNB) 200). SAT Therefore, when communicating between the mobile network entity and the terminal entity, a secure symmetric key can always be relied upon.

[0156] Generate a new shared key K SAT Afterwards, UE 100 uses the key K generated in step S2102 SAT, encrypting data (such as messages) to be sent to an application or any other entity in a core network or home network. For the example embodiments and authentication methods described herein, the kind of data or its source is irrelevant. As an example only, in the case where the terminal UE is an IoT terminal, the message / payload may contain measurement data of a sensor provided at the terminal, the measurement result being reported wirelessly.

[0157] Thereafter, in S2103, the UE 100 sends its security parameters (such as an identifier (UE_SAT_ID) and the encrypted data to the SAT (gNB) 200. In at least some example embodiments such as the second embodiment, the UE 100 may send its security parameters or identifier (UE_SAT_ID), and the encrypted data within the message to the SAT (gNB) 200. However, the UE 100 may alternatively send its security parameters and the encrypted data to the SAT (gNB) 200 in two separate messages. For example, the UE 100 may also send the encrypted data to the SAT (gNB) 200 after at least one of the authentication procedure and the identification procedure is completed.

[0158] After receiving security parameters (such as the identifier UE_SAT_ID) from the UE 100, the SAT (gNB) 200 may identify the UE 100 and thus also authenticate the UE 100. In some example embodiments, for example relying on the identifier UE_SAT_ID as a security parameter, in step S2201, identification and authentication may be performed by comparing the identifier UE_SAT_ID received from the UE 100 with the identifier UE_SAT_ID of the terminal entity received from an entity in the core network 400.

[0159] If the identifier UE_SAT_ID received from the UE 100 matches the identifier UE_SAT_ID of the terminal entity received from the entity in the core network 400, the UE 100 is authenticated and the integrity is also implicitly verified. That is, if the corresponding identifier UE_SAT_ID is received at the SAT (gNB) 200, after receiving the identifier UE_SAT_ID from the entity in the core network 400, the corresponding identifier UE_SAT_ID is known to the UE 100 in addition to the core network 400 and the SAT (gNB) 200, then the message cannot be tampered with or manipulated.

[0160] In step S2203, the SAT (gNB) 200, after valid authentication and / or integrity verification, when the connection to the core network, i.e., the so-called feeder link, is available again, decrypts the received data and forwards it to an entity in the core network 400 or an application in the core network or an application in the home network via the gateway (GW).

[0161] In some example embodiments, for example, in addition to the above-described mechanism according to the second embodiment, when the entity in the core network 400 sends the shared key KSAT and the identifier (UE_SAT_ID) of the UE 100 to the SAT (gNB) 200 in step S2402, the entity in the core network 400 may also send a plurality of identifiers to the SAT (gNB) 200 in S2402, and the plurality of identifiers are not allocated to any UE or terminal entity at the corresponding time. Then, after the SAT (gNB) 200 successfully performs authentication and / or integrity verification of the UE 100, the SAT (gNB) 200 allocates to the UE 100 in step S2202, and sends an identifier (UE_SAT_ID) among the plurality of identifiers that is not allocated to any UE or terminal entity at the corresponding time. When the link between the SAT (gNB) 200 and the core network is available again, for example in step S2203, the SAT (gNB) 200 will also report to the entity in the core network the new allocation of the identifier (UE_SAT_ID) of the UE 100. In this way, the newly allocated identifier (UE_SAT_ID) can be used for authentication in subsequent connections between the UE 100 and the SAT (gNB) 200 or any other movable network entity.

[0162] In this exemplary embodiment, a mechanism for establishing a connection between one UE 100 and one SAT (gNB) 200 is described. However, it is obvious to those skilled in the art that a terminal entity such as UE 100 may establish several connections with different movable network entities (such as SAT (gNB) 200) one after another, for example, because several movable network entities move into or out of the coverage of UE 100 one after another (or vice versa, i.e., the terminal UE and the mobile entity SAT (gNB) are within or move into each other's coverage). In this scenario, the mechanism and / or method described in accordance with the second embodiment may be repeated for each connection establishment. Likewise, it is obvious to those skilled in the art that a movable network entity such as SAT (gNB) 200 may be connected to multiple terminal entities in parallel or sequentially.

[0163] In the second exemplary embodiment, Figure 2At least some methods and apparatus disclosed herein may perform (local) identification and authentication between a user equipment and a mobile network entity despite the (temporary) unavailability of an end-to-end connection between the terminal entity and an entity in a core network (which may include an application function in the core network). As described above, an integrity check of the exchanged data may also be performed in at least the second example embodiment.

[0164] In addition, in the second exemplary embodiment, Figure 2 At least some of the disclosed methods and apparatus allow data from a user device to be sent to an application in a core network or a home network via a secure and trusted connection via a mobile network entity, without requiring an end-to-end connection between a terminal entity (such as a user device) and an entity or application in the core network or a home network via a mobile network entity (e.g., SAT(gNB) 200).

[0165] In this regard, those skilled in the art also understand that in a storage and forwarding service and / or architecture, for data exchange, that is, data transmission and / or reception, such as with respect to Figure 2 The second example embodiment described does not require an end-to-end connection between the terminal entity and an entity in the core network (which may include an application function in the core network) to securely send data from the terminal entity to an entity or application in the core network.

[0166] <Third Embodiment>

[0167] Figure 3 A third embodiment of a mechanism for (local) authentication between, for example, a terminal entity, such as a user equipment (UE), and a mobile network entity is illustrated. Figure 3 In the figure, a signaling sequence of an exemplary mechanism is illustrated, the exemplary mechanism comprising a method and corresponding apparatus for performing (local) authentication between apparatuses such as a terminal entity (such as a UE) and a movable network entity.

[0168] In at least some example communication systems involving at least one mobile network entity, the at least one mobile network entity being a base station such as a next generation NodeB, gNB, for example, a base station or gNB such as may be referred to as SAT(gNB) 200 in a non-terrestrial network, it may occur that a terminal entity such as a user equipment (UE) and a mobile network entity may be disconnected after an initial authentication between the UE and the mobile network entity or an entity in a core network (CN) 400 has been completed.

[0169] In at least some example embodiments, such as in the third embodiment, a satellite deployed in a non-terrestrial network NTN may be referred to as an example of a mobile network entity. However, the present disclosure is not limited thereto. Instead, the present disclosure may also be applicable to a communication system, in which a mobile network entity may be represented by a device, which may be provided on an aircraft or at a marine vessel (such as a ship), and correspondingly supports the required RNL protocol.

[0170] In addition, some example embodiments may be generally directed to a store and forward (S&F) service and / or architecture for data exchange (i.e., data delivery and / or reception), which may be deployed, for example, in an NTN scenario or other scenario. The S&F architecture may facilitate situations where a feeder link (between a mobile network entity and a core network (one or more entities)) and / or a gateway connecting the core network to the mobile network entity may be temporarily unavailable.

[0171] Although in some example embodiments, it is referred to as a user equipment and / or an IoT device, the corresponding mechanism is applicable to any kind of user equipment (UE), basically every device that can establish a connection with a mobile network entity and can send and / or receive data, such as a phone, a car, an IoT device, a robot, or any other UE device with cellular protocol stack support. Such devices and other examples corresponding to UE may also be referred to as terminal entities.

[0172] As described above, at least some of the example embodiments are applicable to any kind of mobile network entity, i.e., any device that can be provided at an aircraft or a marine vessel (such as a ship) and that supports the required RNL protocol accordingly. Nevertheless, for descriptive reasons and simplicity in an example communication system consistent with a non-terrestrial network, the mobile network entity may be referred to as a SAT (gNB) 200. However, this does not limit the example embodiments to such a SAT (gNB) 200, and as described above, the example embodiments including such a SAT (gNB) 200 are not limited to non-terrestrial networks, but for better readability, at least some of the terms used herein are also used in the present description.

[0173] Throughout the drawings, entities involved in signaling are illustrated and represented as boxes 100 (UE), 200 (SAT (gNB)), 300 (gateway GW), 400 (core network CN entity) and 500 (application function). Signals exchanged between processing steps are represented by arrows S* illustrated in the horizontal direction. The processing performed by the respective entities is illustrated as boxes below the respective entities in the vertical direction. The processing sequence is usually (but not necessarily always) represented in the vertical direction of the drawing. Boxes in dashed lines represent situations or conditions where certain links or connections are generally available or unavailable.

[0174] In a system involving at least one mobile network entity, the at least one mobile network entity being a base station such as a next generation NodeB or a gNB, such as a base station or a gNB in ​​a non-terrestrial network which may be referred to as a SAT(gNB) 200, it may happen that a terminal entity such as a user equipment (UE) and a mobile network entity may be disconnected after an initial authentication between the UE and the mobile network entity or an entity in a core network (CN) 400 has been completed.

[0175] In a third embodiment, a mechanism for (local) authentication between a user equipment (UE) and a mobile network entity is provided. Figure 3 In the figure, an exemplary mechanism sequence for (local) authentication between a terminal entity (e.g., UE 100) and a movable network entity (e.g., SAT(gNB) 200) according to the third embodiment is illustrated.

[0176] The third embodiment includes a mechanism, that is, the second embodiment with respect to Figure 2 Therefore, in the second embodiment, the device and method described are Figure 2 Description of described elements and steps is omitted.

[0177] Additionally, if Figure 3 As shown in step S3201 of the present invention, the SAT (gNB) 200 according to the third embodiment is pre-configured with its own certificate previously issued by a certificate authentication authority (CA). Figure 3 As shown in step S3101 of , the UE 100 according to the third embodiment is pre-configured with a root CA certificate and / or a corresponding root path as information for verifying other certificates. The information for verifying other certificates may also be referred to as a trust chain.

[0178] When the connection between UE 100 and SAT (gNB) 200 is established, SAT (gNB) 200 also Figure 3 In step S3202 of SAT(gNB) 200, the UE sends its own certificate to UE 100. After receiving the certificate from SAT(gNB) 200, the UE uses Figure 3 The received certificate is verified using the information used to verify other certificates in step S3102.

[0179] In the third exemplary embodiment, Figure 3At least some of the disclosed methods and apparatus may perform (local) identification and authentication, as well as mutual authentication, between a user equipment and a mobile network entity despite the (temporary) unavailability of an end-to-end connection between the terminal entity and an entity in a core network (which may include an application function in the core network). As described above, an integrity check of the exchanged data may also be performed in at least the third example embodiment.

[0180] In this way, data from a user device can be sent to an application in a core network or a home network via a secure and trusted connection via a mobile network entity without establishing an end-to-end connection between a terminal entity (such as a user device) and an entity or application in a core network or a home network via a mobile network entity (e.g., SAT(gNB) 200).

[0181] In this regard, those skilled in the art also understand that in a storage and forwarding service and / or architecture for data exchange (ie, data transmission and / or reception), such as with respect to Figure 3 The third example embodiment described does not require an end-to-end connection between the terminal entity and an entity of the core network (which may include an application function in the core network) to securely send data from the terminal entity to an entity or application in the core network.

[0182] <Other embodiments>

[0183] The above-mentioned procedures and functions may be implemented by corresponding functional elements, processors, etc. as described below.

[0184] exist Figure 4 In FIG. 1 , an alternative diagram of an apparatus according to an example embodiment is depicted. Figure 4 As shown, according to an example embodiment, a terminal entity such as UE 100 includes a processor 110, a memory 120, and an interface 130, which may be connected via a direct connection, a bus, or the like.

[0185] In addition, Figure 5 In FIG. 1 , an alternative diagram of an apparatus according to an example embodiment is depicted. Figure 5 As shown in , a mobile network entity such as SAT (gNB) 200 includes a processor 210, a memory 220, and an interface 230 that can be connected via a direct connection, a bus, etc.

[0186] exist Figure 6 In FIG. 1 , an alternative diagram of an apparatus according to an example embodiment is depicted. Figure 6 As shown in FIG. 4 , entities in the core network 400 include a processor 410, a memory 420, and an interface 430, which may be connected via a direct connection, a bus, etc. Optionally, the entities in the core network 400 may also include a modem to facilitate sending and receiving data.

[0187] The gateway 300 (not shown) may include a processor, a memory, a receiver and a transmitter, or alternatively a router or a modem, for forwarding data and messages between the core network and the mobile network entity.

[0188] Any of the processors 110, 210 and 410 and / or the interfaces 130, 230 and 430 may also include a modem or the like to facilitate communication via a (hardwired or wireless) link, respectively. The interfaces 130, 230 and 430 may include a suitable transceiver coupled to one or more antennas or communication components for communicating (hardwired or wireless) with the linked or connected device(s), respectively. The interfaces 130, 230 and 430 are typically configured to communicate with at least one other device (i.e., its interface).

[0189] The memories 120 , 220 , and 420 may store respective programs assumed to include program instructions or computer program codes, which, when executed by respective processors, enable respective electronic devices or apparatuses to operate according to example embodiments.

[0190] Generally speaking, the corresponding devices / apparatuses (and / or parts thereof) may represent parts for performing corresponding operations and / or displaying corresponding functions, and / or the corresponding devices (and / or parts thereof) may have functions for performing corresponding operations and / or displaying corresponding functions.

[0191] When it is stated that a processor (or some other component) is configured to perform some function, this should be interpreted as equivalent to a description indicating that at least one processor can cooperate with computer program code stored in the memory of the corresponding device, configured to cause the device to perform at least the functions mentioned thereby. In addition, such functions should be interpreted as being equivalently implementable by components specifically configured to perform the corresponding functions (i.e., the expression "a processor configured to [cause the device] to perform xxx-ing" is interpreted as equivalent to expressions such as "components for xxx-ing". Alternatively, such functions should be interpreted as being equivalently implementable by units specifically configured to perform the corresponding functions (i.e., the expression "a processor configured to [cause the device] to perform xxx-ing" is interpreted as equivalent to expressions such as "xxx unit configured to xxx").

[0192] According to at least some example embodiments, an apparatus representing UE 100 includes at least one processor 110, at least one memory 120, and at least one interface 130, the at least one interface 130 being configured to communicate with at least another apparatus. In a scenario, where the terminal entity does not have a link established to a mobile network entity, the mobile network entity moves into a coverage area of ​​the terminal entity, thereby allowing a link to be established between the mobile network entity and the terminal entity, and where the terminal entity has security parameters, the processor (i.e., at least one processor 110 and at least one memory 120 and computer program code, and at least one interface 130) is configured to perform sending a connection setup request from the terminal entity to the mobile network entity including the security parameters (therefore, the apparatus includes corresponding components for sending a connection setup request from the terminal entity to the mobile network entity including the security parameters), and perform establishing a connection between the terminal entity and the mobile network entity based on the security parameters (therefore, the apparatus includes corresponding components for establishing a connection between the terminal entity and the mobile network entity based on the security parameters).

[0193] According to at least some example embodiments, an apparatus representing a SAT (gNB) 200 includes at least one processor 210, at least one memory 220, and at least one interface 230, the at least one interface being configured to communicate with at least another apparatus. In a scenario, in which a mobile network entity has established a link to a core network entity but has not established a link to a terminal entity, and the mobile network entity moves into a coverage area of ​​the terminal entity, allowing a link to be established between the mobile network entity and the terminal entity, the processor (i.e., at least one processor 210 with at least one memory 220 and computer program code and at least one interface 230) is configured to perform: at the mobile network entity, obtaining at least one security parameter of the terminal entity (therefore, the apparatus includes a corresponding component for obtaining at least one security parameter of the terminal entity at the mobile network entity); in response to receiving a security parameter including the terminal entity, The device may receive a connection setup request including a number of security parameters of the terminal entity, establish a connection between the terminal entity and the movable network entity based on the security parameters of the terminal entity (therefore, the device includes a corresponding component for establishing a connection between the terminal entity and the movable network entity based on the security parameters of the terminal entity in response to receiving the connection setup request including the security parameters of the terminal entity); and perform identification of the terminal entity based on a comparison of the security parameters of the terminal entity received when the connection is established with the security parameters of the terminal entity obtained (therefore, the device includes a corresponding component for identifying the terminal entity based on a comparison of the security parameters of the terminal entity received when the connection is established with the security parameters of the terminal entity obtained).

[0194] According to at least some example embodiments, an apparatus representing an entity in a core network 400 includes at least one processor 410, at least one memory 420, and at least one interface 430, the at least one interface being configured to communicate with at least another apparatus. In a scenario, where a mobile network entity has established a link to a core network entity but has not established a link to a terminal entity, and the mobile network entity moves into a coverage area of ​​the terminal entity, allowing a link to be established between the mobile network entity and the terminal entity, the processor (i.e., at least one processor 410 and at least one memory 420 and computer program code) is configured to perform: obtaining security parameters of the terminal entity (therefore, the apparatus includes corresponding components for obtaining security parameters of the terminal entity); and performing, when the mobile network entity moves into the coverage area of ​​the terminal entity, at least providing the security parameters of the terminal entity to the mobile network entity (therefore, the apparatus includes corresponding components for providing the security parameters of the terminal entity to the mobile network entity when the mobile network entity moves into the coverage area of ​​the terminal entity).

[0195] According to at least some example embodiments, an apparatus representing a UE 100 includes at least one processor 110, at least one memory 120, and at least one interface 130, the at least one interface being configured to communicate with at least another apparatus. In a scenario, in which the terminal entity has established a link to a mobile network entity, and in which the terminal entity is provided with its own certificate and information for verifying other certificates, the processor (i.e., at least one processor 110 and at least one memory 120 and computer program code, and at least one interface 130) is configured to perform: sending a registration request to the mobile network entity, the mobile network entity including its own certificate and an indication indicating support for authentication with the mobile network entity (therefore, the device includes a corresponding component for sending a registration request to the mobile network entity, the mobile network entity including its own certificate and an indication indicating support for authentication with the mobile network entity); performing receiving an authentication request from the mobile network entity including the certificate of the mobile network entity as a response to the registration request (therefore, the device includes a corresponding component for receiving an authentication request from the mobile network entity including the certificate of the mobile network entity as a response to the registration request); and performing verification of the received certificate of the mobile network entity based on the provided information for verifying other certificates (therefore, the device includes a corresponding component for verifying the received certificate of the mobile network entity based on the provided information for verifying other certificates).

[0196] According to at least some example embodiments, an apparatus representing a SAT (gNB) 200 includes at least one processor 210, at least one memory 220, and at least one interface 230, the at least one interface being configured to communicate with at least another apparatus. In a scenario, in which the mobile network entity has not established a link to the core network entity or to the terminal entity, and the mobile network entity is provided with its own certificate and information for verifying other certificates, the processor (i.e., at least one processor 210 using at least one memory 220 and computer program code and at least one interface 230) is configured to, in response to receiving a registration request from the terminal entity, execute sending an authentication request to the terminal entity, the terminal entity including a first certificate and an indication indicating support for authentication with the mobile network entity, wherein the authentication request includes at least its own certificate (therefore, the device includes a corresponding component for sending an authentication request to the terminal entity in response to receiving a registration request from the terminal entity, the terminal entity including a first certificate and an indication indicating support for authentication with the mobile network entity, wherein the authentication request includes at least its own certificate); and execute verification of the received certificate of the mobile network entity based on the provided information for verifying other certificates (therefore, the device includes a corresponding component for verifying the received certificate of the mobile network entity based on the provided information for verifying other certificates).

[0197] According to at least some example embodiments, an apparatus representing an entity in a core network 400 includes at least one processor 410, at least one memory 420, and at least one interface 430, the at least one interface being configured to communicate with at least another apparatus. In a scenario, in which a core network entity is provided with information for verifying a certificate, a processor (i.e., at least one processor 410 utilizing at least one memory 420 and computer program code) is configured to perform receiving a message from a mobile network entity via a gateway, the message including a certificate and an authenticator of a terminal entity (thus, the apparatus includes a corresponding component for receiving a message from a mobile network entity via a gateway, the message including a certificate and an authenticator of the terminal entity); performing verification of the certificate of the terminal entity, wherein successful verification includes obtaining a public key of the terminal entity (thus, the apparatus includes a corresponding component for verifying the certificate of the terminal entity, wherein successful verification includes obtaining a public key of the terminal entity); performing decryption of the authenticator using the obtained public key of the terminal entity (thus, the apparatus includes a component for decrypting the authenticator using the obtained public key of the terminal entity); and performing comparison of the decrypted authenticator with the obtained public key of the terminal entity (thus, the apparatus includes a component for comparing the decrypted authenticator with the obtained public key of the terminal entity).

[0198] Furthermore, it should be understood that when it is stated that a processor (or some other component) is configured to perform a certain function, such function should be interpreted as being equivalently implementable by a specifically configured circuit system (i.e., the expression "a processor configured to [cause the device] to perform xxx-ing" is interpreted as being equivalent to an expression such as "xxx-circuitry configured to perform xxx-ing".

[0199] As used in this application, the term "circuitry" may refer to one or more of the following:

[0200] (a) pure hardware circuit implementation (such as implementation in analog and / or digital circuitry only) and

[0201] (b) a combination of hardware circuitry and software such as (where applicable):

[0202] (i) a combination of analog and / or digital hardware circuits and software / firmware, and

[0203] (ii) any portion of hardware processor(s) (including digital signal processors) with software, software and memory(s) that work together to enable a device (such as a mobile phone or server) to perform various functions, and (c) hardware circuit(s) and / or processor(s), such as microprocessor(s) or portion(s) of microprocessor(s), which requires software (e.g. firmware) to operate, but which may be absent when not required for operation.

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

[0205] For more detailed information on the operability / functionality of the individual devices please refer to the above combined Figures 1 to 6 Description of any of .

[0206] For the purposes of the present disclosure described herein above, it should be noted that:

[0207] - method steps that can be implemented as software code parts and executed using a processor at a network server or network entity (as an example of a device, means and / or module, or as an example of an entity that thus includes means and / or modules), are independent of software code and can be specified using any known or future developed programming language, as long as the functionality defined by the method steps is preserved;

[0208] - generally, any method step is suitable to be implemented as software or by hardware without changing the idea of ​​the embodiment and its modification in terms of the implemented functions;

[0209] - the method steps and / or devices, units or means (e.g., devices that perform the functions of the apparatus according to the above embodiments) that may be implemented as hardware components in the above-defined apparatus or any module thereof are independent of hardware and may be implemented using any known or future developed hardware technology or any hybrid technology thereof, such as MOS (Metal Oxide Semiconductor), CMOS (Complementary MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter Coupled Logic), TTL (Transistor-to-Transistor Logic), etc., using, for example, ASIC (Application Specific IC) components, FPGA (Field Programmable Gate Array) components, CPLD (Complex Programmable Logic Device) components or DSP (Digital Signal Processor) components;

[0210] - the device such as the terminal entity and the mobile network entity may be represented by a semiconductor chip, a chipset or a (hardware) module including such a chip or chipset; however, this does not exclude the possibility that the functions of the device or module are not implemented by hardware but are implemented as software in a (software) module (such as a computer program or a computer program product including an executable software code portion for execution / running on a processor);

[0211] - An entity may be considered as a device or a component of more than one device, whether they cooperate with each other in functionality or are functionally independent of each other, but are for example in the same device housing.

[0212] In general, it should be noted that if it is only adapted to perform the functions of the corresponding components described, the corresponding functional blocks or elements described in the above aspects can be implemented in hardware and / or software by any known method. The above method steps can be implemented in separate functional blocks or by separate devices, or one or more method steps can be implemented in a single functional block or by a single device.

[0213] Generally, any method step is suitable for being implemented as software or by hardware without changing the idea of ​​the present disclosure. Devices and components can be implemented as separate devices, but this does not exclude that they are implemented in a distributed manner throughout the system, as long as the functionality of the device is preserved. These principles and similar principles should be considered to be known to the skilled person.

[0214] Software in the sense of this specification includes software code itself, including code components or parts or computer programs or computer program products for performing corresponding functions, as well as software (or computer programs or computer program products) embodied on tangible media (such as computer-readable (storage) media on which corresponding data structures or code components / parts are stored) or software that may be embodied in signals or chips during its processing.

[0215] The present disclosure also covers any conceivable combination of the above method steps and operations, and any conceivable combination of the above nodes, devices, modules or elements, as long as the concepts of the above method and structural steps are applicable.

[0216] Although the present disclosure has been described above with reference to examples according to the accompanying drawings, it should be understood that the present disclosure is not limited thereto. On the contrary, it is obvious to those skilled in the art that the present disclosure can be modified in many ways without departing from the scope of the inventive concept disclosed herein.

[0217] Methods, apparatuses and computer program products for performing authentication between a mobile network entity and a terminal entity are provided. Such provided methods, apparatuses and computer program products may include performing authentication and / or identification based on sending and / or receiving at least one security parameter and / or at least one authenticator.

[0218] List of abbreviations and acronyms

[0219] 3GPP Third Generation Partnership Project

[0220] 5GC 5G Core

[0221] 5G GUTI 5G Globally Unique Temporary Identifier

[0222] AMF Access and Mobility Management Function

[0223] AS Access Layer

[0224] CA certificate authentication

[0225] CN Core Network

[0226] gNB Next Generation NodeB / 5G NodeB

[0227] GW Gateway

[0228] HN Home Network

[0229] IoT

[0230] ISL Inter-Satellite Link

[0231] KDF Key Derivation Function

[0232] MO for mobile devices

[0233] MT Mobile Device Termination

[0234] NAS Non-Access Layer

[0235] NTN Non-Terrestrial Network

[0236] RAN Radio Access Network

[0237] RNL Radio Network Layer

[0238] RRC Radio Resource Control

[0239] SAT Satellite

[0240] S&F Store and Forward

[0241] UE User Equipment

[0242] UPF User Plane Function

Claims

1. A device for communication, comprising: at least one processor (210); at least one memory (220) comprising computer program code; as well as at least one interface (230) configured to communicate with at least one other device, wherein In one scenario, The mobile network entity (200) establishes a link to the core network entity (400), but does not establish a link to the terminal entity (100), and wherein The mobile network entity moves into a coverage area of ​​the terminal entity, allowing a link to be established between the mobile network entity and the terminal entity, The at least one processor, the at least one memory, the computer program code, and the at least one interface are configured to cause the apparatus to perform: Acquiring, at the mobile network entity, security parameters of at least the terminal entity; In response to receiving the connection setup request including the security parameters of the terminal entity, establishing a connection between the terminal entity and the mobile network entity based on the security parameters of the terminal entity; as well as The terminal entity is identified based on a comparison of the security parameters of the terminal entity received when the connection is established with the obtained security parameters of the terminal entity.

2. The device according to claim 1, wherein The at least one processor, the at least one memory, the computer program code, and the at least one interface are configured to cause the apparatus to further perform: obtaining a shared key. 3 . The apparatus of claim 2 , wherein the acquired shared key is generated using a key derivation function based on at least a shared secret.

4. The device according to claim 3, wherein The acquired shared key is generated using the key derivation function and the shared secret based on a counter value, the value of the counter value depending on the number of connection establishments between the terminal entity and the mobile network entity, or another mobile network entity.

5. The apparatus according to any one of claims 2 to 4, wherein the identifying the terminal entity is also based on the shared key.

6. The device according to any one of claims 2 to 5, wherein The at least one processor, the at least one memory, the computer program code, and the at least one interface are configured to cause the apparatus to further perform: receiving, at the mobile network entity, data from the terminal entity; and The received data is decrypted using the acquired shared key.

7. The device according to claim 6, wherein The at least one processor, the at least one memory, the computer program code, and the at least one interface are configured so that the device further performs: when the link to the core network entity (400) is established, buffering the decrypted data, and forwarding the decrypted data to an application via the link to the core network entity (400).

8. The device according to any one of claims 1 to 7, wherein The at least one processor, the at least one memory, the computer program code, and the at least one interface are configured to cause the apparatus to further perform: Obtain multiple unassigned endpoint security parameters, and When decrypting the received data using the shared key, sending a terminal security parameter from the plurality of unassigned terminal security parameters to the terminal entity, and The terminal security parameters sent to the terminal are optionally encrypted using the shared key.

9. The device according to any one of claims 1 to 8, wherein The at least one processor, the at least one memory, the computer program code, and the at least one interface are configured to cause the apparatus to further perform: In response to the connection between the terminal entity and the mobile network entity being established, a certificate of the mobile network entity is sent from the mobile network entity to the terminal entity.

10. An apparatus for communication, comprising: at least one processor (410), at least one memory (420) including computer program code, and at least one interface (430) configured to communicate with at least one other device, wherein In one scenario, The mobile network entity (200) establishes a link to the core network entity (400), but does not establish a link to the terminal entity (100), and wherein The mobile network entity moves into a coverage area of ​​the terminal entity, allowing a link to be established between the mobile network entity and the terminal entity, The at least one processor, the at least one memory, the computer program code, and the at least one interface are configured to cause the apparatus to perform: Obtaining security parameters of the terminal entity; When the movable network entity moves into the coverage area of ​​the terminal entity, at least the security parameter of the terminal entity is provided to the movable network entity.

11. The device according to claim 10, wherein The at least one processor, the at least one memory, the computer program code, and the at least one interface are configured to cause the apparatus to further perform: Get the shared secret key, and The shared key is provided to the mobile network entity.

12. The device according to claim 11, wherein The at least one processor, the at least one memory and the computer program code, and the at least one interface are configured to cause the apparatus to further perform: generating the shared key using a key derivation function based on at least the shared secret.

13. The device according to claim 12, wherein The at least one processor, the at least one memory, the computer program code, and the at least one interface are configured to cause the apparatus to further perform: In response to a connection between the mobile network entity and the terminal entity being established, incrementing a counter value, and The shared key is generated using the key derivation function based on the counter value and the shared key.

14. The device according to any one of claims 11 to 13, wherein The at least one processor, the at least one memory, the computer program code, and the at least one interface are configured to cause the apparatus to further perform: receiving data.

15. The device according to any one of claims 11 to 13, wherein The at least one processor, the at least one memory, the computer program code, and the at least one interface are configured to cause the apparatus to further perform: providing a plurality of unallocated terminal security parameters to the mobile network entity.

16. An apparatus for communication, comprising: at least one processor (110), at least one memory (120) including computer program code, and at least one interface (130) configured to communicate with at least one other device, wherein In one scenario, The terminal entity (100) has no link established to the mobile network entity (200), the mobile network entity moves into the coverage area of ​​the terminal entity, allowing a link to be established between the mobile network entity and the terminal entity, and wherein The terminal entity has security parameters, The at least one processor, the at least one memory, the computer program code, and the at least one interface are configured to cause the apparatus to further perform: sending a connection setup request from the terminal entity to the mobile network entity including the security parameters, and A connection is established between the terminal entity and the mobile network entity based on the security parameter.

17. The device according to claim 16, wherein The at least one processor, the at least one memory, the computer program code, and the at least one interface are configured to cause the apparatus to further perform: Get the shared secret key, and A shared key is generated using a key derivation function based on at least the shared secret.

18. The device according to claim 17, wherein The at least one processor, the at least one memory, the computer program code, and the at least one interface are configured to cause the apparatus to further perform: In response to a connection between the mobile network entity and the terminal entity being established, incrementing a counter value, and wherein The generating the shared key using the key derivation function is based on the counter value and the shared key.

19. The device according to claim 17 or 18, wherein The at least one processor, the at least one memory, the computer program code, and the at least one interface are configured to cause the apparatus to further perform: Using the shared key, encrypting the data, and The encrypted data is sent to the mobile network entity.

20. The device according to any one of claims 17 to 19, wherein The at least one processor, the at least one memory and the computer program code, and the at least one interface are configured to cause the apparatus to further perform: receiving another security parameter from the mobile network entity, and buffering the received security parameter.

21. The device according to any one of claims 16 to 20, wherein The at least one processor, the at least one memory, the computer program code, and the at least one interface are configured to cause the apparatus to further perform: obtaining at least one root certificate from the root certificates issued by the certificate authority and the path, and The received certificate of the mobile network entity is verified using at least one of the root certificates issued from the certificate authentication and the path.

22. An apparatus for communication, comprising: at least one processor (110), at least one memory (120) including computer program code, and at least one interface (130) configured to communicate with at least one other device, wherein In a scenario, in which a link is established at a terminal entity (100) to a mobile network entity (200), and in which the terminal entity is provided with its own certificate and information for verifying other certificates, The at least one processor, the at least one memory, the computer program code, and the at least one interface are configured to cause the apparatus to perform: sending a registration request to the mobile network entity, the mobile network entity including its own certificate and an indication indicating support for authentication with the mobile network entity; receiving, as a response to the registration request, an authentication request from the mobile network entity including a certificate of the mobile network entity; as well as The received certificate of the mobile network entity is verified based on the information provided for verifying other certificates.

23. The apparatus of claim 22, wherein: The terminal entity is also provided with its own asymmetric key pair, the asymmetric key pair comprising a public key and a private key, and the at least one processor, the at least one memory and the computer program code, and the at least one interface are configured to cause the apparatus to further execute: Generates an authenticator by encrypting its own public key with its own private key, and The authenticator is sent to the mobile network entity.

24. The device according to claim 23, wherein The received authentication request further comprises a public key of the mobile network entity, and the at least one processor, the at least one memory, the computer program code, and the at least one interface are configured to cause the apparatus to further perform: encrypting data using the received public key of the mobile network entity, and The encrypted data is sent to the mobile network entity.

25. An apparatus for communication, comprising: at least one processor (210), at least one memory (220) including computer program code, and at least one interface (230) configured to communicate with at least one other device, wherein In one scenario, The mobile network entity (200) does not establish a link to the core network entity (400) and establishes a link to the terminal entity (100), and wherein The mobile network entity is provided with its own certificate and information for verifying other certificates, The at least one processor, the at least one memory, the computer program code, and the at least one interface are configured to cause the apparatus to perform: In response to receiving a registration request from the terminal entity, sending an authentication request to the terminal entity, the terminal entity including a first certificate and an indication indicating support for authentication with a mobile network entity, wherein the authentication request includes at least its own certificate; as well as The received certificate of the mobile network entity is verified based on the provided information for verifying other certificates.

26. The device according to claim 25, wherein The at least one processor, the at least one memory, the computer program code, and the at least one interface are configured to cause the apparatus to further perform: receiving an authentication response including an authenticator; buffering the received authenticator and the first certificate; as well as When the link to the core network entity (200) is established, the buffered authenticator and the buffered first certificate are forwarded to the core network entity (400).

27. The apparatus of claim 26, wherein: The mobile network entity is also provided with its own asymmetric key pair, the asymmetric key pair comprising a private key and a public key, The authentication request sent also includes its own public key, The received authentication response also includes data, and The at least one processor, the at least one memory, the computer program code, and the at least one interface are configured to cause the apparatus to further perform: decrypting the received data using its own private key and buffering the decrypted data, and When the link to the core network entity (400) is established, the decrypted data is forwarded to the core network entity (400).

28. An apparatus for communication, comprising: at least one processor (410), at least one memory (420) including computer program code, and at least one interface (430) configured to communicate with at least one other device, wherein In a scenario, wherein the core network entity (400) is provided with information for verifying a certificate, The at least one processor, the at least one memory, the computer program code, and the at least one interface are configured to cause the apparatus to perform: receiving a message from a mobile network entity (200) via a gateway (300), the message including a certificate and an authenticator of a terminal entity (100); verifying the certificate of the terminal entity, wherein successful verification includes obtaining a public key of the terminal entity, Decrypting the authenticator using the obtained public key of the terminal entity, and The decrypted authenticator is compared with the obtained public key of the terminal entity.

29. The apparatus of claim 28, wherein: The received message also includes data, and the at least one processor, the at least one memory, the computer program code, and the at least one interface are configured to cause the apparatus to further perform: Responsive to a scenario in which the decrypted authenticator matches the obtained public key of the terminal entity when the decrypted authenticator is compared to the obtained public key of the terminal entity, the data is forwarded to an application.

30. The apparatus of any one of claims 1 to 29, wherein the mobile network entity is a non-terrestrial network entity provided on one of a satellite or an aircraft, or at a maritime vessel.

31. A method for communication, comprising: In one scenario, The mobile network entity (200) establishes a link to the core network entity (400), but does not establish a link to the terminal entity (100), and wherein The mobile network entity moves into a coverage area of ​​the terminal entity, allowing a link to be established between the mobile network entity and the terminal entity, Acquiring, at the mobile network entity, security parameters of at least the terminal entity; In response to receiving the connection setup request including the security parameters of the terminal entity, establishing a connection between the terminal entity and the mobile network entity based on the security parameters of the terminal entity; as well as The terminal entity is identified based on a comparison of the security parameters of the terminal entity received when the connection is established with the obtained security parameters of the terminal entity.

32. The method of claim 31 , wherein the acquiring further comprises: Get the shared key.

33. The method of claim 32, wherein the obtained shared key is generated using a key derivation function based on at least a shared secret.

34. The method of claim 33, wherein The acquired shared key is generated using the key derivation function and the shared secret based on a counter value, the value of the counter value depending on the number of connection establishments between the terminal entity and the mobile network entity, or another mobile network entity.

35. The method according to any one of claims 32 to 34, wherein said identifying said terminal entity is further based on said shared key.

36. The method according to any one of claims 32 to 35, further comprising: receiving, at the mobile network entity, data from the terminal entity; as well as The received data is decrypted using the acquired shared key.

37. The method of claim 36, further comprising: When the link to the core network entity (400) is established, the decrypted data is buffered and the decrypted data is forwarded to an application via the link to the core network entity (400).

38. A method according to any one of claims 31 to 37, wherein: The obtaining further comprises: obtaining a plurality of unassigned terminal security parameters, and wherein the method further comprises: sending a terminal security parameter of the plurality of unassigned terminal security parameters to the terminal entity when decrypting the received data using the shared key, and The terminal security parameters sent to the terminal are optionally encrypted using the shared key.

39. The method according to any one of claims 31 to 38, further comprising: In response to the connection between the terminal entity and the mobile network entity being established, a certificate of the mobile network entity is sent from the mobile network entity to the terminal entity.

40. A method for communication, comprising: In one scenario, The mobile network entity (200) establishes a link to the core network entity (400), but does not establish a link to the terminal entity (100), and wherein The mobile network entity moves into a coverage area of ​​the terminal entity, allowing a link to be established between the mobile network entity and the terminal entity, Obtaining security parameters of the terminal entity; When the movable network entity moves into the coverage area of ​​the terminal entity, at least the security parameter of the terminal entity is provided to the movable network entity.

41. The method of claim 40, wherein said providing further comprises: Get the shared secret key, and The shared key is provided to the mobile network entity.

42. The method of claim 41 further comprising: The shared key is generated using a key derivation function based on at least the shared secret.

43. The method of claim 42, further comprising: In response to a connection between the mobile network entity and the terminal entity being established, incrementing a counter value, and The shared key is generated using the key derivation function based on the counter value and the shared key.

44. The method according to any one of claims 41 to 43, further comprising: Receive data.

45. The method according to any one of claims 41 to 44, wherein said providing further comprises: Provides multiple unassigned endpoint security parameters.

46. ​​A method for communication, comprising: In one scenario, The terminal entity (100) has no link established to the mobile network entity (200), the mobile network entity moves into the coverage area of ​​the terminal entity, allowing a link to be established between the mobile network entity and the terminal entity, and wherein The terminal entity has security parameters, sending a connection setup request from the terminal entity to the mobile network entity including the security parameters, and A connection is established between the terminal entity and the mobile network entity based on the security parameter.

47. The method of claim 46, further comprising: Get the shared secret key, and A shared key is generated using a key derivation function based on at least the shared secret.

48. The method of claim 47, further comprising: In response to a connection between the mobile network entity and the terminal entity being established, incrementing a counter value, and wherein The generating the shared key using the key derivation function is based on the counter value and the shared key.

49. The method according to claim 47 or 48, further comprising: Using the shared key, encrypting the data, and The encrypted data is sent to the mobile network entity.

50. The method according to any one of claims 46 to 49, further comprising: Another security parameter is received from the mobile network entity, and the received security parameter is buffered.

51. The method according to any one of claims 46 to 50, further comprising: obtaining at least one root certificate from the root certificates issued by the certificate authority and the path, and The received certificate of the mobile network entity is verified using at least one of the root certificates issued from the certificate authentication and the path.

52. A method for communication, comprising: In a scenario, in which a link is established at a terminal entity (100) to a mobile network entity (200), and in which the terminal entity is provided with its own certificate and information for verifying other certificates, sending a registration request to the mobile network entity, the mobile network entity including its own certificate and an indication indicating support for authentication with the mobile network entity; receiving, as a response to the registration request, an authentication request from the mobile network entity including a certificate of the mobile network entity; as well as The received certificate of the mobile network entity is verified based on the information provided for verifying other certificates.

53. The method of claim 52, wherein: The terminal entity is also provided with its own asymmetric key pair, the asymmetric key pair comprising a public key and a private key, and the method further comprises: Generates an authenticator by encrypting its own public key with its own private key, and The authenticator is sent to the mobile network entity.

54. The method of claim 53, wherein: The received authentication request also includes a public key of the mobile network entity, The method further comprises: encrypting data using the received public key of the mobile network entity, and The sending further comprises sending the encrypted data to the mobile network entity.

55. A method for communication, comprising: In one scenario, The mobile network entity (200) does not establish a link to the core network entity (400) and establishes a link to the terminal entity (100), and wherein The mobile network entity is provided with its own certificate and information for verifying other certificates, In response to receiving a registration request from the terminal entity, sending an authentication request to the terminal entity, the terminal entity including a first certificate and an indication indicating support for authentication with a mobile network entity, wherein the authentication request includes at least its own certificate; as well as The received certificate of the mobile network entity is verified based on the provided information for verifying other certificates.

56. The method of claim 55, further comprising: receiving an authentication response including an authenticator; buffering the received authenticator and the first certificate; as well as When the link to the core network entity (200) is established, the buffered authenticator and the buffered first certificate are forwarded to the core network entity (400).

57. The method of claim 56, wherein: The mobile network entity is also provided with its own asymmetric key pair, the asymmetric key pair comprising a private key and a public key, and wherein The authentication request sent also includes its own public key, The received authentication response also includes data, The method further comprises: decrypting the received data using its own private key and buffering the decrypted data, and The forwarding further comprises: forwarding the decrypted data to the core network entity (400) when the link to the core network entity (400) is established.

58. A method for communication, comprising: In a scenario, wherein the core network entity (400) is provided with information for verifying a certificate, receiving a message from a mobile network entity (200) via a gateway (300), the message including a certificate and an authenticator of a terminal entity (100); Verifying the certificate of the terminal entity, wherein successful verification comprises: obtaining a public key of the terminal entity, decrypting the authenticator using the obtained public key of the terminal entity, and The decrypted authenticator is compared with the obtained public key of the terminal entity.

59. The method of claim 58, wherein: The received message also includes data, and The method further includes forwarding the data to an application in response to a scenario in which the decrypted authenticator matches the obtained public key of the terminal entity when the decrypted authenticator is compared to the obtained public key of the terminal entity.

60. The method of any one of claims 1 to 59, according to which the mobile network entity is a non-terrestrial network entity provided on one of a satellite or an aircraft, or at a maritime vessel.

61. A computer program product, comprising a computer executable computer program code, the computer program product being configured to cause a computer to perform a method according to any one of claims 31 to 60 when the program is run on the computer.

62. A non-transitory computer readable medium comprising program instructions which, when executed by a device, cause the device to perform the method according to any one of claims 31 to 60.

Images