Radio telecommunications system with multiple mobile access nodes

Abstract

A mobile access node apparatus includes components for: providing a radio connection between the mobile access node apparatus and a user equipment; providing a radio connection between the mobile access node apparatus and a network; suspending the radio connection between the mobile access node apparatus and the user equipment after the radio connection between the mobile access node apparatus and the network is lost, and storing a UE context including a security context for the user equipment; and transmitting the UE context including the security context for the user equipment to the network via the radio connection between the mobile access node apparatus and the network after the radio connection between the mobile access node apparatus and the network is re-established.

Description

Technical Field

[0001] Examples of this disclosure relate to radio telecommunications systems having multiple mobile access nodes (e.g., non-geostationary satellites). Background Technology

[0002] In some examples, a radio telecommunications system may include a network of multiple interconnected transceiver points, multiple mobile access nodes, and multiple user equipment 110.

[0003] The transceiver point can form a radio connection with one or more mobile access nodes 130_i. The mobile access node 130_i can form a radio connection with one or more transceiver points.

[0004] Each mobile access node has a coverage area. When each mobile access node moves, its corresponding coverage area 132_i also moves.

[0005] Mobile access nodes can have multiple different connection states: It can connect to both user devices and networks simultaneously.

[0006] It can connect to user equipment but not to a network.

[0007] It can connect to the network but not to user devices.

[0008] It can neither connect to the network nor to user devices.

[0009] This could cause problems in managing data transmission between user equipment and the network. Summary of the Invention

[0010] Examples as claimed in the appended claims are provided according to various, but not necessarily all, embodiments.

[0011] While the examples and optional features of this disclosure have been described separately, it should be understood that they are included within this disclosure in all possible combinations and permutations. It should be understood that various examples of this disclosure may include any or all of the features described with respect to other examples of this disclosure, and vice versa. Furthermore, it should be understood that any one or more features in any combination may be implemented / included / performed by means of an apparatus, method, and / or computer program instructions as needed and appropriate. The description of a function should also be considered as disclosing any components suitable for performing that function. Attached Figure Description

[0012] Some examples will now be described with reference to the accompanying drawings, in which: Figures 1A to 1E Examples of the topics described in this article are shown; Figures 2A to 2E Examples of the topics described in this article are shown; Figures 3A to 3E Examples of the topics described in this article are shown; Figure 4 Another example of the topic described in this article is shown; Figure 5 This article presents another example of the topic described in it; Figure 6 This article presents another example of the topic described in it; Figure 7 Another example of the topic described in this article is shown.

[0013] The accompanying drawings are not necessarily drawn to scale. For clarity and brevity, some features and views in the drawings may be shown schematically or enlarged to scale. For example, the dimensions of some elements in the drawings may be enlarged relative to other elements to aid illustration. Similar reference numerals are used in the accompanying drawings to indicate similar features. For clarity, not all reference numerals may be shown in all drawings. Detailed Implementation

[0014] Figures 1A to 1E An example of a telecommunications system that combines store-and-forward with suspend-and-resume is shown.

[0015] The radio telecommunications system includes a network 120, a mobile access node 130_i, and user equipment 110. Although one user equipment 110 is shown, the system may include multiple user equipment 110s.

[0016] Network 120 includes multiple interconnected transceiver points 120_i. Transceiver points 120_i are configured to form radio connections with one or more mobile access nodes 130_i.

[0017] Mobile access node 130_i is configured to establish a radio connection with one or more transceiver points 120_i. Mobile access node 130_i is configured to establish a radio connection with one or more user equipment 110.

[0018] Each mobile access node 130_i has a coverage area 132_i. When each mobile access node 130_i moves, its respective coverage area 132_i also moves.

[0019] Mobile access node 130_i is configured to form radio connections with one or more transceiver points 120_i within its coverage area 132_i. Mobile access node 130_i does not form radio connections with any transceiver point 120_i outside its coverage area 132_i.

[0020] Mobile access node 130_i is configured to establish a radio connection with one or more user equipment 110s within its coverage area 132_i. Mobile access node 130_i does not establish a radio connection with any user equipment 110 outside its coverage area 132_i.

[0021] Figures 1A to 1E A communication system is illustrated, wherein a first mobile access node 130_1 and a second mobile access node 130_2 are movable relative to a first transceiver point 120_1 and a second transceiver point 120_2. The first mobile access node 130_1 and the second mobile access node 130_2 move from left to right. The user equipment 110 may be fixed or movable.

[0022] exist Figure 1A In this configuration, the first mobile access node 130_1 is located at the transceiver point 120_1. The first transceiver point 120_1 is situated within the first coverage area 132_1 of the first mobile access node 130_1. A radio connection is established between the first mobile access node 130_1 and the first transceiver point 120_1.

[0023] User equipment 110 is located outside the first coverage area 132_1 of the first mobile access node 130_1, and the second transceiver point 120_2 is also located outside the first coverage area 132_1 of the first mobile access node 130_1. There is no radio connection between the first mobile access node 130_1 and user equipment 110. There is no radio connection between the first mobile access node 130_1 and the second transceiver point 120_2.

[0024] In this example, downlink (DL) data for user equipment 110 cannot be transmitted to user equipment 110 via the first mobile access node 130_1 because there is no radio connection between the first mobile access node 130_1 and user equipment 110. Downlink data DL_1 is transmitted from the first transceiver point 120_1 to the first mobile access node 130_1 and stored in the first mobile access node 130_1 for subsequent forwarding from the first mobile access node 130_1 to user equipment 110 at a later time (see [link to example]). Figure 1C ).

[0025] Downlink data DL_1 is transmitted from mobility entity 124_1 in network 120 to mobility entity 134_1 in first mobile access node 130_1. Mobility entity 134_1 in first mobile access node 130_1 controls the storage of downlink data DL_1 and its subsequent forwarding from first mobile access node 130_1 (see [link to mobile access node 130_1]). Figure 1C ).

[0026] The second mobile access node 130_2 is on the user equipment 110. The user equipment 110 is located within the second coverage area 132_2 of the second mobile access node 130_2. A radio connection is formed between the second mobile access node 130_2 and the user equipment 110.

[0027] The first transceiver point 120_1 is located outside the second coverage area 132_2 of the second mobile access node 130_2, and the second transceiver point 120_2 is also located outside the second coverage area 132_2 of the second mobile access node 130_2. There is no radio connection between the second mobile access node 130_2 and the first transceiver point 120_1. There is no radio connection between the second mobile access node 130_2 and the second transceiver point 120_2.

[0028] In this example, uplink (UL) data from user equipment 110 cannot be transmitted to the network via the second mobile access node 130_2 because there is no radio connection between the second mobile access node 130_2 and the network 120. Uplink data UL_1 is transmitted from user equipment 110 to the second mobile access node 130_2 and stored therefor subsequent forwarding from the second mobile access node 130_2 to the network 120 at a later time (see [link to example]). Figure 1C ).

[0029] Uplink data UL_1 is transmitted to mobility entity 134_2 in the second mobile access node 130_2. Mobility entity 134_2 in the second mobile access node 130_2 controls the storage of uplink data UL_1 and its subsequent forwarding from the second mobile access node 130_2 to network 120 (see [link]). Figure 1C ).

[0030] exist Figure 1B In this scenario, the first mobile access node 130_1 and the second mobile access node 130_2 have moved. The first coverage area 132_1 of the first mobile access node 130_1 no longer covers the first transceiver point 120_1, and has not yet covered the user equipment 110. There is no longer a radio connection between the first mobile access node 130_1 and the first transceiver point 120_1. There is also no radio connection between the first mobile access node 130_1 and the user equipment 110.

[0031] The second coverage area 132_2 of the second mobile access node 130_2 no longer covers the user equipment 110, and has not yet covered the second transceiver point 120_2. There is no longer a radio connection between the second mobile access node 130_2 and the user equipment 110. There is also no radio connection between the second mobile access node 130_2 and the second transceiver point 120_2. Prior to the loss of the radio connection between the second mobile access node 130_2 and the user equipment 110, the user equipment 110 was autonomously placed into a suspended mode by the second mobile access node 130_2.

[0032] exist Figure 1C In this context, the first mobile access node 130_1 and the second mobile access node 130_2 have moved. The first coverage area 132_1 of the first mobile access node 130_1 covers the user equipment 110. A radio connection exists between the first mobile access node 130_1 and the user equipment 110.

[0033] The second coverage area 132_2 of the second mobile access node 130_2 covers the second transceiver point 120_2. A radio connection exists between the second mobile access node 130_2 and the second transceiver point 120_2.

[0034] The user equipment is restored from suspended mode by the first mobile access node 130_1.

[0035] exist Figure 1C In this configuration, the first mobile access node 130_1 is located on the user equipment. The user equipment 110 is located within the first coverage area 132_1 of the first mobile access node 130_1. A radio connection is established between the first mobile access node 130_1 and the user equipment 110.

[0036] The first transceiver point 120_1 is located outside the first coverage area 132_1 of the first mobile access node 130_1, and the second transceiver point 120_2 is located outside the first coverage area 132_1 of the first mobile access node 130_1. There is no radio connection between the first mobile access node 130_1 and the first transceiver point 120_1. There is no radio connection between the first mobile access node 130_1 and the second transceiver point 120_2.

[0037] In this example, data cannot be transmitted to or from network 120 via the first mobile access node 130_1 because there is no radio connection between the first mobile access node 130_1 and network 120.

[0038] Downlink data DL_1 stored in the first mobile access node 130_1 is forwarded to user equipment 110. This downlink data is transmitted from the first mobile access node 130_1 to the user equipment 110. Mobility entity 134_1 in the first mobile access node 130_1 controls the storage and forwarding of downlink data DL1.

[0039] Uplink data UL_2 is transmitted from user equipment 110 to the first mobile access node 130_1 and stored in the first mobile access node 130_1 for subsequent forwarding from the first mobile access node 130_1 to network 120 at a later time (see [link]). Figure 1E ).

[0040] Uplink data UL_2 is transmitted to mobility entity 134_1 in the first mobile access node 130_1. Mobility entity 134_1 in the first mobile access node 130_1 controls the storage of uplink data UL_2 and its subsequent forwarding from the first mobile access node 130_1 to network 120 (see [link]). Figure 1E ).

[0041] The second mobile access node 130_2 is located at the second transceiver point 120_2. The second transceiver point 120_2 is situated within the second coverage area 132_2 of the second mobile access node 130_2. A radio connection is established between the second mobile access node 130_2 and the second transceiver point 120_2.

[0042] The first transceiver point 120_1 is located outside the second coverage area 132_2 of the second mobile access node 130_2, and the user equipment 110 is also located outside the second coverage area 132_2 of the second mobile access node 130_2. There is no radio connection between the second mobile access node 130_2 and the first transceiver point 120_1. There is also no radio connection between the second mobile access node 130_2 and the user equipment 110.

[0043] In this example, uplink (UL) data UL_1 stored in the second mobile access node 130_2 is forwarded to the second transceiver point 120_2. Uplink data UL_1 is transmitted from the second mobile access node 130_2 to the second transceiver point 120_2.

[0044] Uplink data UL_1 is transmitted from mobility entity 134_2 in the second mobile access node 130_2 to mobility entity 124_2 in the second transceiver point 120_2. Mobility entity 134_2 in the second mobile access node 130_2 controls the storage and forwarding of uplink data UL1.

[0045] exist Figure 1DIn this context, the first mobile access node 130_1 and the second mobile access node 130_2 have moved. The first coverage area 132_1 of the first mobile access node 130_1 no longer covers the user equipment 110, and has not yet covered the second transceiver point 120_2. There is no longer a radio connection between the first mobile access node 130_1 and the user equipment 110. There is also no radio connection between the first mobile access node 130_1 and the second transceiver point 120_2.

[0046] The second coverage area 132_2 of the second mobile access node 130_2 no longer covers the second transceiver point 120_2. There is no longer a radio connection between the second mobile access node 130_2 and the second transceiver point 120_2.

[0047] Before the radio connection between the first mobile access node 130_1 and the user equipment 110 is lost, the user equipment 110 is autonomously placed into a suspended mode by the first mobile access node 130_1.

[0048] exist Figure 1E In this configuration, the first mobile access node 130_1 is located at the second transceiver point 120_2. The second transceiver point 120_2 is situated within the first coverage area 132_1 of the first mobile access node 130_1. A radio connection is established between the first mobile access node 130_1 and the second transceiver point 120_2.

[0049] The first transceiver point 120_1 and the user equipment 110 are located outside the first coverage area 132_1 of the first mobile access node 130_1. There is no radio connection between the first mobile access node 130_1 and the first transceiver point 120_1 or between the first mobile access node 130_1 and the user equipment 110.

[0050] In this example, data cannot be transmitted to or from user equipment 110 via the second mobile access node 130_2 because there is no radio connection between the first mobile access node 130_1 and user equipment 110.

[0051] The uplink data UL_2 stored in the first mobile access node 130_1 is forwarded to the second transceiver point 120_2. This uplink data is transmitted from the first mobile access node 130_1 to the second transceiver point 120_2. The mobility entity 134_1 in the first mobile access node 130_1 controls the storage and forwarding of the uplink data UL_2.

[0052] After user equipment 110 is suspended, the downlink data pipeline for user equipment 110 from network 120 to user equipment 110 is suspended at network 120.

[0053] In at least some examples, the downlink data pipeline for user equipment 110 from network 120 to user equipment 110 is unsuspended at network 120 before user equipment 110 resumes from suspension. The downlink data transmitted by the pipeline may be buffered at the network (e.g., at a mobility entity or radio access entity) or at mobile access node 130 (e.g., at a mobility entity or radio access entity).

[0054] The UE context of the user equipment is maintained and reused to re-establish the radio connection between the user equipment 110 and the mobile access node 130.

[0055] When the second mobile access node 130_2 disconnects from the network 120, the second mobile access node 130_2 suspends the user equipment and stores the UE context. The UE context is stored in the mobility entity 134_2 of the second mobile access node 130_2.

[0056] When the second mobile access node 130_2 reconnects to the network 120, the second mobile access node 130_2 provides the UE context to the network 120. The mobility entity 134_2 of the second mobile access node 130_2 transmits the UE context to the mobility entity 124 of the network 120.

[0057] When the first mobile access node 130_1 is identified as the next mobile access node serving the user equipment 110 and is connected to the network 120, the network transmits the UE context to the first mobile access node 130_1. The mobility entity 124_1 of the network 120 transmits the stored UE context to the mobility entity 134 of the first mobile access node 130_1.

[0058] Reference Figures 2A to 2E To explain the process, in these examples, user equipment (UE) 110 first connects to the first mobile access node 130_1, and then connects to the second mobile access node 130_2.

[0059] exist Figure 2A In this configuration, UE 110 is connected to the first mobile access node 130_1, and the first mobile access node 130_1 is connected to the network 120. A data pipeline exists between UE 110 and the network via the first mobile access node 130_1. The data pipeline transmits uplink (UL) data and / or downlink (DL) data.

[0060] Next, in Figure 2B In this case, UE 110 is connected to the first mobile access node 130_1, and the first mobile access node 130_1 is no longer connected to network 120.

[0061] In at least some examples, the first mobile access node 130_1 can continue to receive UL data. The first mobile access node 130_1 stores the received UL data in memory, which may be buffered in memory, for example, by buffer 252.

[0062] The first mobile access node 130_1 is configured to suspend UE 110 autonomously and store the UE context for UE 110 in memory.

[0063] Next, in Figure 2C In this scenario, UE 110 is suspended. First Mobile Access Node 130_1 is not connected to UE 110. Initially, First Mobile Access Node 130_1 is not connected to Network 120. However, First Mobile Access Node 130_1 subsequently reconnects to Network 120.

[0064] The first mobile access node 130_1 is configured to transmit a UE suspension notification message 211 to the network 120. The UE suspension notification message 211 to the network 120 notifies the network that UE 110 has been suspended and provides the network 120 with the stored UE context.

[0065] Network 120 stores UE context In some examples, the UE suspension notification message 211 may include suspension information, such as the suspension ID of UE 110.

[0066] In some examples, the UE hang-up notification message 211 may include buffered UL data.

[0067] It should be noted that the UE context is stored at the mobile access node 130_1 and transmitted to the network when the connection with the mobile access node 130_1 is re-established.

[0068] UE suspension notification message 211 causes the network to: Store 212 UE context; Suspend 214 downlink data pipeline from network 120 to user equipment 110 for user equipment 110.

[0069] Next, in Figure 2D In this configuration, network preparation 218 connects to user equipment 110 via second mobile access node 130_2. Second mobile access node 130_2 connects to network 120.

[0070] Network 120 is configured to transmit a UE context recovery notification message 217 to the second mobile access node 130_2. The UE context recovery notification message 217 notifies the second mobile access node 130_2 that the user equipment has been suspended and should be resumed from suspension when possible.

[0071] The UE suspension notification message 217 includes the UE context. The second mobile access node 130_2 stores this UE context.

[0072] In at least some examples, the UE hangup notification message 217 includes DL data transfer parameters for establishing a DL data pipeline from the network to the second mobile access node 130_2. The second mobile access node 130_2 may store the DL data transfer parameters. The second mobile access node 130_2 may use the DL data transfer parameters to establish a DL data pipeline from the network to the second mobile access node 130_2.

[0073] In some examples, the UE context recovery notification message 217 may include buffered DL data.

[0074] The received DL data can be stored in memory (254 bytes), or it can be buffered.

[0075] In some examples, the UE context recovery notification message 217 may include recovery information, such as the suspend ID for UE 110.

[0076] When the second mobile access node 130_2 becomes connected to the user equipment, such as Figure 2E As shown, UE 110 is restored from suspend mode 230 and can communicate with UE 110 using the UE context.

[0077] UE 110 is connected to the second mobile access node 130_2, and the second mobile access node 130_2 is connected to the network 120. A data pipeline exists between UE 110 and the network 120 via the second mobile access node 130_2. The data pipeline transmits uplink (UL) data and / or downlink (DL) data.

[0078] exist Figures 2A to 2E Another example of the process shown in the corresponding Figures 3A to 3E As shown in the image.

[0079] against Figures 2A to 2E The provided description is also consistent with Figures 3A to 3E Related.

[0080] exist Figure 3B In this configuration, UE 110 is connected to the first mobile access node 130_1, and the first mobile access node 130_1 is no longer connected to network 120. In at least some examples, the first mobile access node 130_1 can continue to receive UL data. The mobility entity 134_1 of the first mobile access node 130_1 stores the received UL data in memory, which may be buffered in memory, for example, by buffer 252.

[0081] The mobility entity 134_1 of the first mobile access node 130_1 is configured to autonomously suspend UE 110 and store the UE context for UE 110 in memory.

[0082] exist Figure 2C In this scenario, UE 110 is suspended. First Mobile Access Node 130_1 is not connected to UE 110. Initially, First Mobile Access Node 130_1 is not connected to Network 120. However, First Mobile Access Node 130_1 subsequently reconnects to Network 120.

[0083] The mobility entity 134_1 of the first mobile access node 130_1 is configured to transmit a UE suspension notification message 211 to the mobility entity 124 of the network 120. The UE suspension notification message 211 to the mobility entity 124 of the network 120 notifies the mobility entity 124 of the network 120 that the UE 110 has been suspended and provides the stored UE context to the mobility entity 124 of the network 120.

[0084] The mobility entity 134_1 of network 120 stores the UE context.

[0085] In some examples, the UE suspension notification message 211 may include suspension information, such as the suspension ID of UE 110. In some examples, the UE suspension notification message 211 may include buffered UL data.

[0086] It should be noted that when the connection between the mobility entity 124 of network 120 and the mobility entity 134_1 of the first mobile access node 130_1 is re-established, the UE context is stored at the mobility entity 134_1 of the mobile access node 130_1 and transmitted to the mobility entity 124 of network 120.

[0087] UE suspension notification message 211 causes network mobility entity 124 to: Store 212 UE context; This causes a pause 214 in the downlink data pipeline from network 120 to user equipment 110.

[0088] Mobility entity 124 of network 120 sends a pause command 213 to data control entity 126, pausing the downlink data pipeline from network 120 to user equipment 110.

[0089] In at least some examples, the data control entity 126 of network 120 provides DL data transfer parameters to the network's mobility entity 124 for re-establishing the DL data pipeline from the network to the mobile access node 130. Mobility entity 124 may store the DL data transfer parameters.

[0090] Next, in Figure 3D In this context, network mobility entity 124 prepares 218 to connect to user equipment 110 via second mobile access node 130_2. Second mobile access node 130_2 connects to network 120.

[0091] The mobility entity 124 of network 120 is configured to transmit a UE context recovery notification message 217 to the mobility entity 134_2 of the second mobile access node 130_2. The UE context recovery notification message 217 notifies the mobility entity 134_2 of the second mobile access node 130_2 that the user equipment 110 has been suspended and should be resumed from suspension when possible.

[0092] The UE suspension notification message 217 includes the UE context. The mobility entity 134_2 of the second mobile access node 130_2 stores the UE context.

[0093] In at least some examples, the UE hangup notification message 217 includes DL data transfer parameters for establishing a DL data pipeline from the network to the second mobile access node 130_2. The second mobile access node 130_2 may store the DL data transfer parameters. The second mobile access node 130_2 may use the DL data transfer parameters to establish a DL data pipeline from the network to the second mobile access node 130_2.

[0094] In some examples, the UE context recovery notification message 217 may include buffered DL data.

[0095] The received DL data can be stored in memory (254 bytes), or it can be buffered.

[0096] In some examples, the UE context recovery notification message 217 may include recovery information, such as the suspend ID of UE 110.

[0097] In this example, the mobility entity 124 of network 120 sends a cancel pause command 221 to the data control entity 126, canceling the pause 222 of the downlink data pipeline from network 120 to user equipment 110.

[0098] When the second mobile access node 130_2 becomes connected to the user equipment, such as Figure 3EAs shown, UE 110 is restored from suspend mode 230 and can communicate with UE 110 using the UE context.

[0099] UE 110 is connected to the second mobile access node 130_2, and the second mobile access node 130_2 is connected to the network 120. A data pipeline is established between UE 110 and the network 120 via the second mobile access node 130_2. The data pipeline transmits uplink (UL) data and / or downlink (DL) data.

[0100] After user equipment 110 is suspended, the downlink data pipeline from network 120 to user equipment 110 is paused at network 120. In at least some examples, the downlink data pipeline from network 120 to user equipment 110 is unsuspended at network 222 before user equipment 110 resumes from suspension 230. The downlink data transmitted by the pipeline may be buffered at network 130 (e.g., at a mobility entity or radio access entity) or at mobile access node 130 (e.g., at a mobility entity or radio access entity).

[0101] Forwarding from data control entity 126 to new / candidate mobile access node 130 occurs before the actual recovery 230 at the access layer, and this requires buffering and different configurations at network 120.

[0102] In some examples, DL data transmission parameters include DL tunnel information and / or information used to establish the user plane.

[0103] In some examples (e.g., Figure 4 Mobility entity 130 is a mobility management entity (MME). In some examples, data control entity 126 is a serving gateway (S-GW).

[0104] In some examples (e.g., Figure 5 Mobility entity 130 is the Access and Mobility Management Function (AMF). In some examples, data control entity 126 is the Session Management Function (SMF). exist Figure 4 and Figure 5 The diagram illustrates the interaction between mobility entities (AMF / MME). Mobility entity 134 at mobile access node 130 transmits a UE suspension notification message 211 to mobility entity 124 at network 120. Mobility entity 124 at network 120 transmits a UE context recovery notification message 217 to one or more mobility entities 134 at the corresponding mobile access node 130.

[0105] Messages 211 and 217 both include the UE context. These two messages can also include a recovery ID to assist in the restoration of UE 110's connection (230).

[0106] UE Context Recovery Notification Message 217 may include DL tunnel information for UPF (or S-GW) used to transmit DL services from network 120.

[0107] Mobility entity 124 at network 120 requests data control entity 126 to modify the established bearer and buffer DL packets destined for the suspended UE 110. The buffered DL packets are then transmitted to the newly established link with the new mobile access node 130_2, which is intended to provide coverage to UE 110. These buffered DL packets are sent to the new mobile access node 130_2 via the established user plane to the new mobile access node 130.

[0108] Network 120 can be a terrestrial network (land network), and the mobile access node can be a satellite (non-terrestrial access node). In such a non-terrestrial network (NTN), one or more candidate satellites 130 need to be selected to forward UE context, establish a data plane, and forward buffered packets from the UPF so that the connection between the (one or more) new satellites 130 and UE 110 can be effectively restored. Furthermore, data forwarding from the UPF to the (multiple) new / candidate satellites 130 occurs before the actual restoration at the access layer, and this requires buffering and different configurations at the terrestrial network 120.

[0109] In some examples, the mobile access node can be non-geostationary, such as a non-geostationary satellite. Other mobile access nodes can be balloons or airplanes.

[0110] The UE context may include, for example, information used to maintain access layer (AS) security.

[0111] In some examples, the UE context may additionally include Radio Resource Control (RRC) configuration.

[0112] The UE context may include, for example, information for maintaining the synchronization of security keys. The UE context may include, for example, the parameter nextHopChainingCount, which is used to derive one or more security keys.

[0113] The suspend process is the process of placing the user equipment into suspend mode. The user equipment can resume from suspend mode to transmit user data or control data.

[0114] The suspension process is a connection suspension process that suspends the Radio Resource Control (RRC) connection, which results in the suspension of the control (C) and user (U) planes.

[0115] Suspended mode maintains access layer (AS) security.

[0116] In LTE: If the UE and the network support user plane CIoT EPS optimization, the network uses a suspension procedure to suspend the connection (see TS 36.300[5]). - Clause “5.3.4 A Connection Suspension Procedure”, TS 23.401.

[0117] In LTE: by using a suspend procedure, see Clause 5.3.5A in TS 23.401 and TS 36.300: The UE stores AS information when switching to ECM-IDLE; The eNodeB stores the UE's AS information, S1AP association, and bearer context; The MME stores the UE's S1AP association and bearer context and enters it into ECM-IDLE.

[0118] In 5G: "When the UE is in CM-CONNECTED and has at least one PDU session with an active user plane connection, and the NG-eNB has received from the AMF the user plane CIoT 5GS optimization as defined in Clause 5.31.18 of TS 23.501[2], the suspension procedure may be initiated by the serving NG-RAN node." - Clause "Connection Suspension Procedure (Clause 4.8.1.2 of TS 23.502)".

[0119] In 5G: (23.501, Clause 5.31.18) By using the connection suspension process: UEs that have switched to CM-IDLE store AS information; NG-RAN stores the UE's AS information, NGAP UE association, and PDU session context; The AMF stores NGAP UE associations and other information needed for later UE recovery, interacts with (multiple) SMFs to disable user plane resources of the UE's PDU session, and enters CM-IDLE… Resume connection using CM-IDLE with suspend process: The UE uses the AS information stored during the connection suspension to restore its connection to the network from CM-IDLE; NG-RAN notifies the AMF that the connection between the UE and the UE has been restored; The AMF enters CM-CONNECTED and interacts with the SMF to activate the user plane resources of the UE's PDU session.

[0120] In LTE: "If the UE and the network support user plane CIoT EPS optimization and the UE has stored the necessary information for the connection recovery procedure (see TS 36.300[5]), the UE uses the recovery procedure to recover ECM-CONNECTED; otherwise, it uses the service request procedure, see Clause 5.3.4." - Clause 5.3.5A Connection Recovery Procedure, TS 23.401.

[0121] In 5G: "For UEs that support user plane CIoT 5GS optimization, the UE uses a connection recovery procedure to perform a state transition from RRC_IDLE to RRC_CONNECTED with a pending state. Clause 5.31.18 of TS 23.501 defines the triggering of this procedure by the UE." - Clause 4.8.2.3 of TS 23.502 "Connection Recovery Procedure".

[0122] In LTE, the UE context includes: IMSI, MSISDN, ME identifier, UE security context, UE network capabilities, AMBR, selected CN operator ID, APN restrictions, service GW address and TEID for control signaling, (multiple) EPS bearer contexts, and UE radio capability ID.

[0123] The EPS bearer context includes the PDN GW address and TEID (for GTP-based S5 / S8) or GRE key (for PMIP-based S5 / S8) at (multiple) PDN GWs for uplink services, APN, service GW address and TEID for uplink services, and TI.

[0124] In 5GS, a long list of UE contexts is described in Table 5.2.2.2.2-1 of the TS 23.502 example related to NTN, which may include: UE radio capabilities for paging information, UE radio capability information, UE radio capability ID, security information for CP, security information for UP, and UE ID.

[0125] Store and Forward Satellite (S&F) operations provide communication services to the UE (via stored and forwarded information) during periods and / or geographical areas when the serving satellite is not simultaneously connected to the terrestrial network via a feeder link or ISL. For UL, "store" refers to onboard storage of UL information from the UE, and "forward" refers to forwarding the stored UL information to the terrestrial network 120. For DL, "store" refers to onboard storage of DL information from the terrestrial network 120, and "forward" refers to forwarding the stored DL information to the UE 110.

[0126] The storage and forwarding scheme relies on a regenerative architecture, in which the RAN will be placed in satellite 130.

[0127] Mobile entity 134 at satellite 130 is responsible for providing storage and forwarding characteristics.

[0128] This solution is designed for both 4G (EPS) and 5G (5GS) deployments, as NTN is defined for NB-IoT, eMTC, and NR type devices. In this disclosure, aspects are described in the context of 5G (e.g., AMF instead of MME) and / or 4G (e.g., MME instead of AMF), but this should not be considered limiting.

[0129] The RRC suspension and resumption process avoids the need for the UE to re-establish the RRC connection. Suspension / resumption operations significantly reduce bearer establishment time, especially in S&F scenarios.

[0130] When a UE loses a connection to satellite 1 (e.g., RAN-Satellite 1, AMF-T1) 130_1, the connection is suspended (using an RRC connection suspension message from satellite 1 130_1 to UE 110). When the UE re-establishes an access layer link with another satellite 130_2, the connection is restored (using an RRC connection restoration message from satellite 130_2 to UE 110).

[0131] The UE can be suspended by the first satellite 130_1 and resumed by the second satellite 130_2. However, the UE context may not necessarily be able to be transferred from the first satellite 130_1 to the second satellite 130_2.

[0132] Therefore, when satellite connectivity to the terrestrial network 120 is intermittently / temporarily available, enhanced suspension and recovery procedures are needed to support S&F satellite operations. When the UE restores connectivity to the corresponding satellite(s) 130, procedures for forwarding data services are required.

[0133] The following example describes configuring the suspension and recovery process for a store-and-forward satellite scenario. More specifically, when the feeder link is available and after the UE has suspended its connection to satellite (Satellite 1) 130_1, the terrestrial network 120 will suspend DL data forwarding to satellite (Satellite 1) 130_1 in the SGW (or UPF). The terrestrial network 120 (e.g., MME-T or AMF-T) then identifies the next satellite (e.g., Satellite 2) 130_2 that will reach UE 110, and then connects to that same satellite before UE 110 connects to satellite (i.e., Satellite 2) 130_2. The terrestrial network 120 restores the UE context to that satellite (Satellite 2) 130_2 to enable a fast and efficient recovery of the connection to UE 110 and the transmission of DL services. Satellite 130_2 may be the same as or different from the satellite to which UE 110 initially connected.

[0134] The following functionalities are proposed at satellite (i.e., NT-RAN, MME / AMF-NT) and ground-based NFs (such as MME / AMF-T and S-GW (or SMF, UPF in the case of 5GS)): Satellite 130_1: Once UE 110 disconnects from the currently attached satellite 130_1 (i.e., the UE has received an RRC connection release indicating that the RRC has been suspended), NT-RAN transmits UE Suspension Notification Message 203 211 to MME-NT, including UE context information.

[0135] Satellite 130_1 to Ground Network 120: Once the satellite can reach the ground station, the MME-NT (or AMF-NT in the case of 5GS) transmits the UE hang-up notification message 211, including UE context information, to the ground MME-T (or AMF-T in the case of 5GS).

[0136] Terrestrial network 120: MME-T (or AMF-T) stores 212 UE context information. Once MME-T (or AMF-T) discovers (identifies) one or more suitable satellites 130_2 (i.e., target satellites), which can reach UE 110 (with a pending connection) in the shortest possible time, the UE context information can be retrieved.

[0137] Terrestrial network 120: MME-T (AMF-T) sends request 213 to S-GW (or SMF in 5GS) to modify (e.g., release) the S1-U bearer (or NG-U in 5GS) for UE 110 and begin buffering / storing DL data, which is transmitted to UE 110 when the connection between UE 110 and satellite 130_2 is restored.

[0138] Terrestrial network 120 to satellite 130_2: MME-T (or AMF-NT) transmits UE context recovery notification message 217 to one or more suitable satellites 130_2 (i.e., target satellites), including UE context information, recovery ID for assisting in the recovery of UE 110's connection, and DL tunnel information for transmitting DL services from the terrestrial network (or UPF in the case of 5S).

[0139] Satellite 130_2: Once the target satellite 130_2 can provide coverage / connectivity services to UE 110, the MME-NT transmits the UE context recovery notification to the NT-RAN, which is responsible for establishing the access network bearer to receive DL services from the terrestrial network (S-GW or UPF) and also maintains the UE context information and recovery ID for the UE recovery process.

[0140] Terrestrial Network: MME-T (or AMF-T) transmits to S-GW (or SMF, then UPF in 5GS) to modify (e.g., establish) the user plane with the target satellite and transmits buffered / stored DL packets from GW (or UPF in 5GS) to the NT-RAN of the target satellite 130_2.

[0141] Mobility entity 134 at mobile access node 130 is a mobility anchor point for the UE and is divided into two network elements, MME-NT (MME on satellite) and MME-T (MME on the ground). MME-NT will act as the mobility anchor point for the UE and will only perform a subset of MME functions, such as auxiliary store and forwarding operations, i.e., a combination of two steps that are not in time.

[0142] The MME-T on the ground is responsible for maintaining the UE context, including the security context. The MME-T is also responsible for NAS encryption / decryption and integrity protection.

[0143] The MME-NT is responsible for maintaining S1 connections to the RAN node and maintaining the associated connection ID for each UE to the MME-T. The MME-NT is responsible for encoding NAS messages received from the MME-T into S1AP payloads to the RAN, and decoding NAS payloads from messages received from the RAN and sending them to the MME-T.

[0144] Store and forward satellite (S&F) operations in EPC systems with satellite access are designed to provide a degree of delayed communication services to UEs under satellite coverage with intermittent / temporary satellite connections (e.g., when the satellite is not connected to the terrestrial network via a feeder link or ISL).

[0145] Figure 4 An example of a procedure for suspending a connection is shown when the UE and network support user plane CIoT EPS optimization (as described in TS 36.300 & 23.401).

[0146] UE 110 transmits data service 201 to satellite 1130_1 and receives data service 201 from satellite 1130_1.

[0147] Due to certain triggers, such as the anticipated disconnection of the UE from the moving satellite 1130_1, the latter decides to suspend the RRC connection at 202. The RAN suspends the UE autonomously.

[0148] NT RAN 1 136_1 initiates an S1-AP UE context suspension notification 203 to notify MME-NT-1 134_1 that the RRC connection is suspended 204, and the transmitted message includes the UE context. The UE context includes relevant AS security, such as the next-hop chain count (NCC) value, which is required to re-establish AS security in order to restore the connection with UE 110 via another satellite 130_2.

[0149] Satellite 1 (RAN 1) 130_1 suspends the RRC connection to UE 110 by sending an RRCConnectionRelease message, where releaseCause is set to rrc-Suspend. The UE stores the AS context, suspends all bearers, and changes its state to RRC-IDLE.

[0150] UE-Satellite_1 connection is "disconnected" from UE.

[0151] Once satellite 1130_1 can reach ground network 120, the Satellite_1-Ground Network connection is established. MME-NT-1134_1 transmits S10 message 211 to ground MME (MME-T) 124. This message includes a "UE context suspension notification" and includes UE context information and AS security information as a transparent payload.

[0152] The MME-T 124 stores UE context information 212. Once the MME-T 124 finds a suitable satellite 130_i containing an MME-NT 134_i that can reach UE 110 in the shortest possible time, it can retrieve this UE context information. The MME-T 124 marks UE 110 as ECM-idle, but the data related to S1AP association, UE context, and bearer context remain intact, which is necessary for restoring the connection between the UE and satellite 130_i (at a future point in time).

[0153] MME-T 124 sends a Release Access Bearer Request Message 213 (with a pause indication) to the serving GW 126, which requests the release of all S1-U bearers for UE 110 and the start of buffering DL data (if any) without notification (i.e., no downlink data notification) to MME-T 124.

[0154] Service GW 126 releases all eNodeB (RAN NT1) U-plane related information (address and downlink TEID) for UE 110 and responds to MME 124 with Release Access Bearer Response Message 215. Other elements of the UE's service GW context are unaffected.

[0155] The ground-based MME (MME-T) 124 determines 216 when UE 110 is reachable and by which non-terrestrial network elements (i.e., (multiple) satellites 130_i) can reach it. The MME-T triggers a recovery notification procedure for one or more satellites based on the identified satellite 130_2 (e.g., MME-NT-2).

[0156] (MME-T to MME-NT-2) MME-T 124 transmits S10 message 217 (including UE context recovery notification) to MME-NT-2 134_2. This message includes UE context information, a recovery ID for assisting in the recovery of UE connectivity, DL tunnel information of the S-GW toward the selected satellite (e.g., satellite 2 130_2), and an E-RAB request for creating UL tunnel resources in the RAN. Information about other non-terrestrial network elements (i.e., satellites) identified by the terrestrial MME (MME-T) may optionally be included in message 217.

[0157] MME-NT2 134_2 sends an S1-AP message to NT-RAN 2. Once satellite 2 130_2 is able to provide coverage / connectivity services to the UE, NT-RAN 2 is responsible for establishing the 218 access network bearer to receive DL services from S-GW 126 and maintaining UE context information and recovery IDs for the UE recovery process. RAN-2 136_2 creates the necessary UL U-plane resources and allocates IP / TEIDs (AN tunnel information).

[0158] MME-NT2 134_2 transmits acknowledgment 219, indicating that the AN bearer has been established, to MME-T, providing AN tunneling information for providing DL services from S-GW 126 to satellite 2 130_2.

[0159] An AN tunnel is created within the RAN to receive DL data for storage until the RAN reaches the UE location and the RRC is restored.

[0160] MME-T 124 transmits Modify Bearer Request 221 to S-GW, which includes AN tunnel information (i.e., NT-RAN of satellite 2) to establish a user plane with satellite 2 130_2.

[0161] S-GW 126 transmits buffered / stored DL packets to the RAN in Satellite 2.

[0162] Once satellite 2 130_2 is in a position where a link can be established with UE 110, the following steps can be initiated. Note that satellite 2 130_2 is no longer connected to the ground station.

[0163] NT-RAN 2 136_2, based on the received messages used to restore the connection, Alt1: Triggers the UE (e.g., via a paging message) to restore the connection.

[0164] Using the received UE context, Satellite 2 can verify the UE identity and authenticate the UE that sent the RRCConnectionResumeRequest message, as well as the recovery ID indicated by the corresponding recovery ID information provided by MME-T.

[0165] Alt2: According to clause “7.3a.3 User Plane CIoT EPS / 5GS Optimization” in TS 36.300, the UE initiates RACH and attempts to connect to a new cell (in RAN-NT-2).

[0166] The UE restores all SRBs and DRBs, re-establishes AS security, and enters the RRC_Connected state. The UE can now transmit UL data, and the RAN can send the stored DL data received in step 13.

[0167] Satellite 2 may optionally notify other satellites (e.g., via an inter-satellite link or via a terrestrial network) of the successful transmission of the DL data received in step 13. Other satellites may decide to delete the stored UE context information and / or DL ​​data.

[0168] Figure 5 An example of a procedure for suspending a connection is shown when the UE and network support user plane CIoT 5GS optimization (as described in TS 38.300 & 23.501).

[0169] UE 110 transmits data service 201 to satellite 1130_1 and receives data service 201 from satellite 1130_1.

[0170] Due to certain triggers, such as the anticipated disconnection of UE 110 from the moving satellite 1130_1, the latter decides to suspend the RRC connection at 202. The RAN suspends the UE autonomously.

[0171] NT RAN 1 136_1 initiates UE context suspension notification 203 to notify AMF-NT 134_1 that the RRC connection is being suspended and that the transmitted message includes the UE context.

[0172] The UE context includes relevant AS security, such as the next-hop chain count (NCC) value, which is required to re-establish AS security in order to restore the connection with the UE via another satellite.

[0173] Satellite 1 130_1 (RAN 1 136_1) suspends the 204 RRC connection by sending an RRCConnectionRelease message, where releaseCause is set to rrc-Suspend. The UE stores the AS context, suspends all bearers, and changes its state to RRC-IDLE.

[0174] UE-Satellite_1 connection "disconnected".

[0175] Once satellite 1130_1 can reach ground network 120, the Satellite_1-Ground Network connection is established.

[0176] AMF-NT-1 134_1 transmits a “UE context suspension notification” 211 to the ground AMF (AMF-T) 124, which includes UE context information and AS security information.

[0177] The AMF-T 124 stores UE context information 212. This UE context information can be retrieved once the AMF-T 124 finds a suitable satellite 130_i containing AMF-NT 134_i that can reach UE 110 in the shortest possible time. The AMF-T 124 marks UE 110 as CM-idle, but the data related to the UE context and bearer context is necessary to restore the connection between the UE and the satellite (at a future point in time).

[0178] AMF-T 124 sends a PDUSESsion_UpdateSMContext request message 213 (with a pause indication) to SMF 126. Accordingly, SMF 126 requests UPF (not shown) to release the NG-U tunnel of UE 110 and start buffering DL data (if any) without notifying AMF-T 124 (i.e., without sending downlink data notification).

[0179] Once the UPF releases all base station (RAN NT1) related information (address and downlink TEID) used for user plane communication with the UE and notifies the SMF, the latter responds with PDUSession_UpdateSMContext 215 AMF-T 124. Other elements of the UE's UPF context are unaffected.

[0180] The ground-based AMF (AMF-T) 124 determines 216 when the UE 110 is reachable and by which non-terrestrial network elements (i.e., (multiple) satellites) it can reach. The AMF-T triggers a recovery notification procedure for one or more satellites based on the identified satellites.

[0181] AMF-T 134 transmits UE context recovery notification message 217 to AMF-NT-2 134_2. This message includes UE context information, a recovery ID for assisting in the recovery of UE 110's connection, and DL tunnel information of the UPF toward the selected satellite (e.g., satellite 2) for transmitting DL information. Information about other non-terrestrial network elements (i.e., satellites) determined by the terrestrial AMF (AMF-T) may optionally be included in message 217.

[0182] AMF-NT2 134_2 sends an N2 message to NT-RAN 2. Once satellite 2 130_2 is able to provide coverage / connectivity services to UE 110, NT-RAN 2 is responsible for establishing the 218 access network bearer to receive DL services from the UPF and maintaining UE context information and recovery ID for the UE recovery process.

[0183] AMF-NT2 134_2 transmits acknowledgment 219, indicating that an AN bearer has been established, to AMF-T 124, thereby providing AN tunneling information for providing DL services from UPF to satellite 2.

[0184] AMF-T 124 transmits Session Modification Request 221 to SMF 126, including AN tunnel information (i.e., NT-RAN of satellite 2) to establish a user plane between UPF and satellite 2 and to transmit buffered / stored DL packets from UPF to RAN in satellite 2130_2.

[0185] Although not shown in the figure, the SMF requests the UPF to establish a tunnel with satellite 2130_2 and transmit buffered / stored DL packets (if any) via the N4 interface and session modification messages.

[0186] Once satellite 2 130_2 is in a position where a link can be established with UE 110, the following steps can be initiated. Note that satellite 2 is no longer connected to ground station 120.

[0187] NT-RAN 2 136_2, based on the received messages used to restore the 230 connection, Alt1: Triggers the UE (e.g., via a paging message) to restore the connection.

[0188] Using the received UE context, Satellite 2 can verify the UE identity and authenticate UE 110 that sent the RRCConnectionResumeRequest message, as well as the recovery ID indicated by the corresponding recovery ID information provided by AMF-T 124.

[0189] Alt2: According to clause “7.3a.3 User plane CIoT EPS / 5GS optimization” in TS 36.300, UE 110 initiates RACH and attempts to connect to a new cell (in RAN-NT-2).

[0190] UE 110 restores all SRBs and DRBs, re-establishes AS security, and enters the RRC_Connected state. UE 110 can now transmit UL data, and the RAN can send the received stored DL data.

[0191] Satellite 2 may optionally notify other satellites (e.g., via an inter-satellite link or via a terrestrial network) that the DL data received in step 13 has been successfully transmitted. Other satellites may decide to delete the stored UE context information and / or DL ​​data.

[0192] When the satellite is equipped with eNodeB or ng-eNode RAN and MME-T (i.e., LTE / EPS-based satellite) and the terrestrial network is 5GS (with AMF-T), the N26 interface can be used for interaction between the terrestrial network 120 and the satellite 130.

[0193]

[0194] The following are independent features: • The recovery / suspend process can be performed in Evolved Packet System (EPS) or 5G System (5GS).

[0195] • The UE context includes AS security-related information, such as the next-hop chain count (NCC) value.

[0196] • For EPS, the MME-NT-1 transmits a message including the UE context suspension notification in S10.

[0197] • The session function can be either the Service Gateway (S-GW) in EPS or the Session Management Function (SMF) in 5GS.

[0198] • For EPS, MME-T sends a Modify Bearer Request with a pause indication to SGW, which requests the release of all S1-U bearers for the UE and the start of buffering DL data (if any), without notifying MME-T of downlink data.

[0199] • For 5GS, AMF-T sends a session modification request with a pause indication to SMF, and SMF requests UPF to release the NG-U tunnel for the UE and start buffering DL data (if any), without downlink data notification at AMF-T.

[0200] • For EPS, MME-T transmits S10 UE context recovery notification, which includes UE context information, recovery ID for assisting in restoring UE connectivity, DL tunnel information of S-GW toward the target satellite, and E-RAB request for creating UL tunnel resources in RAN.

[0201] • For 5GS, AMF-T transmits UE context recovery notification messages, including UE context information, recovery ID for assisting in restoring the UE's connection, and DL tunnel information for the transmission of DL information from the UPF toward the target satellite.

[0202] • MME-NT2 sends an S1-AP message with UE context recovery notification to NT-RAN 2, or AMF-NT2 sends an N2 message with UE context recovery notification to NT-RAN 2.

[0203] • Once the target satellite can provide coverage / connectivity services to the UE, NT-RAN 2 establishes an access bearer to receive DL services from the S-GW or SMF and maintains UE context information and recovery ID for use in the UE recovery process.

[0204] • If the satellite is deployed with eNodeB or ng-eNodeb RAN and MME-T (EPS), and the terrestrial network is 5GS (with AMF-T), then the N26 interface is used for interaction between the terrestrial network and the satellite.

[0205] • When satellite connectivity is intermittent / temporarily unavailable, the suspension / resumption process helps prevent the UE from re-establishing the connection, thereby minimizing signaling and core network ground interactions.

[0206] • When the UE restores its connection with the corresponding satellite, this proposal helps configure the satellite to successfully forward data services.

[0207] • For UEs with U-plane services, suspend / resume operations help reduce bearer setup time, especially in S&F scenarios.

[0208] Multiple satellites can have the same information delivered by the network. A) Due to uncertainty, the terrestrial network may select two or more satellites to serve the UE; B) Ground-based networks can enable each satellite to know about other satellites with the same information; C) Once a satellite has successfully delivered data to the UE's satellite, it can then notify neighboring satellites to delete the same buffered / stored information via an inter-satellite link or a terrestrial network. The neighboring satellite receives this notification and deletes the buffered / stored UE information.

[0209] refer to Figures 2A-2E , Figures 3A-3E , Figure 4 and Figure 5 The example shown, in various examples, the mobile access node device 130_1 includes components for: Provide a radio connection between the mobile access node device 130_1 and the user equipment 110; A radio connection is provided between the mobile access node device 130_1 and the network 120; After the radio connection between the mobile access node device 130_1 and the network 120 is lost, the radio connection between the mobile access node device 130_1 and the user equipment 110 is suspended 204, and the UE context including the security context for the user equipment 110 is stored 250. After the radio connection between the mobile access node device 130_1 and the network 120 is re-established, the UE context including the security context for the user equipment 110 is transmitted to the network 120 via the radio connection between the mobile access node device 130_1 and the network 120.

[0210] In some examples, the components for suspending a 204 radio connection include components for performing a connection suspension process that suspends the radio resource control connection but maintains access layer security.

[0211] In some examples, the mobile access node device 130_1 includes a mobility entity 134_1, which is configured to: suspend 202, 204 the radio connection between the mobile access node device 130_1 and the user equipment 110, and store 250 a UE context including a security context for the user equipment 110; and is configured to: transmit 211 the UE context including a security context for the user equipment 110 to the network 120 via a radio connection between the mobile access node device 130_1 and the network 120.

[0212] In some examples, mobility entity 134_1 is configured to transmit UE hang-up notification message 211 to deliver a UE context, including a security context for user equipment 110, to network 120.

[0213] In some examples, the UE suspension notification message 211 includes suspension identification information for the user equipment 110.

[0214] In some examples, the mobile access node device 130_1 includes a component 252 for buffering uplink data received via the radio connection between the mobile access node device 130_1 and the user equipment 110 in the event of a loss of radio connection between the mobile access node device 130_1 and the network 120; and Components for transmitting buffered uplink data 211 to network 120 when the radio connection between mobile access node device 130_1 and network 120 is re-established.

[0215] In some examples, the mobile access node device 130_1 is included in the satellite.

[0216] refer to Figures 2A-2E , Figures 3A-3E , Figure 4 and Figure 5 The example shown, in various examples, the mobile access node device 130_2 includes components for: Provide a radio connection between the mobile access node device 130_2 and the user equipment 110; A radio connection is provided between the mobile access node device 130_2 and the network 120; After establishing a radio connection between the mobile access node device 130_2 and the network 120, 217 UE context including the security context for the user equipment 110 and data transmission parameters are transmitted from the network 120 via the radio connection between the mobile access node device 130_2 and the network 120; and Use data transfer parameters to establish a data pipeline; After establishing a radio connection between the mobile access node device 130_2 and the suspended user equipment 110, the suspended radio connection between the mobile access node device 130_2 and the user equipment 110 is restored using a UE context that includes a security context for the user equipment 110.

[0217] In some examples, the components for restoring the suspended radio connection of 230 include components for performing a connection restoration process that restores the radio resource control connection without re-establishing access layer security.

[0218] In some examples, the mobile access node device 130_2 includes a mobility entity 134_2, which is configured to: 217 UE context and data transmission parameters, including the security context for user equipment 110, are transmitted from network 120 via radio connection between mobile access node device 130_2 and network 120.

[0219] In some examples, the mobility entity 134_2 of the mobile access node device 130_2 is configured to restore the suspended radio connection between the mobile access node device 130_2 and the user equipment 110 using a UE context that includes a security context for the user equipment 110.

[0220] In some examples, the mobility entity 134_2 of the mobile access node device 130_2 is configured to receive a UE context recovery notification message 217 to transmit a UE context including a security context for the user equipment 110 to the mobility entity 134_2.

[0221] In some examples, the UE suspension notification message includes suspension identification information for user equipment 110.

[0222] In some examples, the mobile access node device 130_2 includes a component 254 for buffering downlink data received via the radio connection between the mobile access node device 130_2 and the network 120 in the event of a loss of radio connection between the mobile access node device 130_2 and the user equipment 110; and Components for transmitting buffered downlink data to the user equipment when a radio connection is established between the mobile access node device 130_2 and the user equipment.

[0223] In some examples, the mobile access node device 130_2 is included in the satellite.

[0224] refer to Figures 2A-2E , Figures 3A-3E , Figure 4 and Figure 5 The examples shown, in various examples, A terrestrial network 120 includes components for: Provide radio connectivity to the first mobile access node 130_1; Provide radio connectivity to the second mobile access node 130_2; After re-establishing the radio connection between the first mobile access node 130_1 and the network 120 211 UE context including security context for user equipment 110 is received from the first mobile access node 130_1 via the radio connection between the first mobile access node 130_1 and the network 120; Storage 212 includes the UE context for the security context of user equipment 110; Suspend the downlink data pipeline of user equipment 110 for users 213 and 214; and After establishing a radio connection between the second mobile access node 130_2 and the network 120 The UE context, including the security context for the user equipment 110, and the downlink data pipeline parameters for the user equipment 110 are transmitted from the network 120 via the radio connection between the second mobile access node 130_2 and the network 120.

[0225] In some examples, the terrestrial network 120 includes components for communicating with the data control entity 126 to cancel the suspension of the downlink data pipeline of the user equipment 110 before confirming the establishment of a radio connection between the second mobile access node 130_2 and the network 120.

[0226] In some examples, the terrestrial network 120 includes a mobility entity 124 configured to receive a UE context, including a security context for the user equipment 110, from the mobility entity 134_1 of the first mobile access node 130_1; and The mobility entity 134_2 of the second mobile access node 130_2 transmits data transmission parameters, including the UE context for the security context of the user equipment 110 and the downlink data pipeline for the user equipment 110.

[0227] In some examples, the mobility entity 124 of the terrestrial network device 120 is configured to receive a UE suspension notification message 211, which transmits a UE context including a security context for the user equipment 110.

[0228] In some examples, the UE suspension notification message 211 includes suspension identification information for the user equipment 110.

[0229] In some examples, the terrestrial network 120 includes: components for buffering downlink data in the event of a loss of radio connection from the mobile access node 130 to the user equipment 110; and Components for transmitting buffered downlink data to the second mobile access node 130_2 when a radio connection is established between the second mobile access node 130_2 and the network 120.

[0230] In some examples, the terrestrial network 120 includes a mobility entity 124 configured to transmit a UE context recovery notification message 217 to the mobility entity 134_2 of the second mobile access node 130_2, which transmits a UE context including a security context for the user equipment 110.

[0231] In some examples, the UE suspension notification message 217 includes suspension identification information for the user equipment 110.

[0232] Figure 6 An example of a controller 400 applicable to devices 130, 120 is shown. Controller 400 may be implemented as controller circuitry. Controller 400 may be implemented solely in hardware, have certain aspects only in software including firmware, or may be a combination of hardware and software (including firmware).

[0233] like Figure 6 As shown, the controller 400 can be implemented using instructions that implement hardware functions, for example, by using executable instructions 406 in a general-purpose or special-purpose processor 402, which can be stored on a machine-readable storage medium (disk, memory, etc.) for execution by such processor 402.

[0234] Processor 402 is configured to read from and write to memory 404. Processor 402 may also include an output interface and an input interface, through which processor 402 outputs data and / or commands and through which data and / or commands are input to processor 402.

[0235] Memory 404 stores instructions, programs, or code 406 that control the operation of the device when loaded into processor 402. The computer program instructions, programs, or code 406 provide logic and routines that enable the device to perform the methods shown in the figures. Processor 402 is configured to load and execute the instructions, programs, or code 406 by reading memory 404.

[0236] Mobile access device 130 includes: At least one processor 402; and At least one memory 404 stores instructions that, when executed by at least one processor 402, cause the device to at least: Perform the method of claims 8 and / or 20.

[0237] Device 120 includes: At least one processor 402; and At least one memory 404 stores instructions that, when executed by at least one processor 402, cause the device to at least: Perform the method of claim 32.

[0238] like Figure 7As shown, instructions, programs, or code 406 can reach the device via any suitable delivery mechanism 408. Delivery mechanism 408 can be, for example, a machine-readable medium, a computer-readable medium, a non-transitory computer-readable storage medium, a computer program product, a memory device, a recording medium such as an optical disc read-only memory (CD-ROM) or digital versatile optical disc (DVD) or solid-state storage, or an article of manufacture that includes or tangibly embodies the computer program 406. The delivery mechanism can be a signal configured to reliably transmit the computer program 406. The device can propagate or transmit the computer program 406 as a computer data signal.

[0239] As used herein, the term “non-transient” refers to a limitation on the medium itself (i.e., tangible, not signaling), rather than a limitation on the persistence of data storage (e.g., RAM vs. ROM).

[0240] Computer program instructions for causing the mobile access device 130 to perform at least the following operations or for performing at least the following operations: the method of claim 8 and / or the method of claim 20.

[0241] Computer program instructions are used to cause network device 120 to perform at least the following or to perform at least the following: the method of claim 32.

[0242] Computer program instructions may be contained in a computer program, a non-transitory computer-readable medium, a computer program product, or a machine-readable medium. In some, but not all, examples, computer program instructions may be distributed across more than one computer program.

[0243] Although memory 404 is shown as a single component / circuit, it can be implemented as one or more separate components / circuits, some or all of which may be integrated / removable and / or provide permanent / semi-permanent / dynamic / cacheable storage.

[0244] Although processor 402 is shown as a single component / circuit, it can be implemented as one or more separate components / circuits, some or all of which may be integrated / removable. Processor 402 may be a single-core or multi-core processor.

[0245] References to “computer-readable storage medium,” “computer program product,” “tangible computer program,” or “controller,” “computer,” “processor,” etc., should be understood to encompass not only computers with different architectures (such as single / multiprocessor architectures and sequential (von Neumann) / parallel architectures) but also special-purpose circuits (such as field-programmable gate arrays (FPGAs), special-purpose circuits (ASICs), signal processing devices, and other processing circuits). References to computer programs, instructions, code, etc., should be understood to encompass software or firmware for programmable processors, such as the programmable content of hardware devices, whether instructions for processors or configuration settings for fixed-function devices, gate arrays, or programmable logic devices, etc.

[0246] As used in this application, the term "circuit" may refer to one or more of the following: (a) Hardware circuit implementation only (e.g., implementation only in analog and / or digital circuits), and (b) A combination of hardware circuitry and software, such as (if applicable): A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and Any part of a hardware processor with software (including (multiple) digital signal processors, software, and one or more memories, which work together to enable a device (such as a mobile phone or server) to perform various functions), and (c) The operation requires software (e.g., firmware) for the operation of (multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, but the software may be absent when the operation does not require the software.

[0247] This definition of "circuit" applies to all uses of the term in this application (including in any claim). As another example, as used in this application, the term "circuit" also covers only the implementation of hardware circuits or processors and their accompanying software and / or firmware. For example, when applied to elements of the claims, the term "circuit" also covers baseband integrated circuits for mobile devices or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

[0248] The boxes shown in the accompanying drawings may represent steps in the method and / or code segments in computer program 406. The description of a specific order of boxes does not necessarily imply a required or preferred order, and the order and arrangement of boxes can vary. Furthermore, some boxes may be omitted.

[0249] As used herein, a module refers to a unit or device that excludes certain parts / components that will be added by the final manufacturer or user. Such a device can be, for example, a module. The controller 400 of the device can be, for example, a module.

[0250] Where a structural feature has been described, it may be replaced by a component that performs one or more functions of that structural feature, whether or not those functions are explicitly or implicitly described.

[0251] The above example can be applied to implement the following components: Automotive systems; telecommunications systems; electronic systems including consumer electronics; distributed computing systems; media systems for generating or rendering media content including audio, visual and audiovisual content, as well as mixed, mediated, virtual and / or augmented reality media content; personal systems including personal health systems or personal fitness systems; navigation systems; user interfaces also known as human-machine interfaces; networks including cellular, non-cellular and optical networks; self-organizing networks; the Internet; the Internet of Things; virtualized networks; and related software and services.

[0252] According to the examples of this disclosure, the device can be provided in an electronic device (e.g., a mobile terminal). However, it should be understood that the mobile terminal is merely an illustration of an electronic device that will benefit from the implementation of this disclosure and should therefore not be construed as limiting the scope of this disclosure. While the device may be provided in a mobile terminal in some implementation examples, other types of electronic devices, such as, but not limited to, mobile communication devices, handheld portable electronic devices, wearable computing devices, portable digital assistants (PDAs), pagers, mobile computers, desktop computers, televisions, gaming devices, laptop computers, cameras, video recorders, GPS devices, and other types of electronic systems, can readily adopt the examples of this disclosure. Furthermore, devices can readily adopt the examples of this disclosure regardless of their intention to provide mobility.

[0253] The term “includes” as used in this document has an inclusive rather than exclusive meaning. That is, any reference to X that includes Y indicates that X may include only one Y or may include more than one Y. If the intention is to use “includes” with an exclusive meaning, it will become clear in the context by referring to “includes only one…” or by using “consisting of…”.

[0254] In this specification, the terms “connection,” “coupling,” and “communication,” and their derivatives, mean operatively connecting / coupling / communicating. It should be understood that any number or combination of intermediate components (including none) may be present to provide direct or indirect connection / coupling / communication. Any such intermediate component may include hardware and / or software components.

[0255] As used herein, the term "determine / identify" (and its grammatical variations) can include at least: calculation, operation, processing, derivation, measurement, investigation, identification, lookup (e.g., searching in a table, database, or other data structure), ascertainment, etc. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), obtaining, etc. Additionally, "determine" can include parsing, selecting, picking, building, etc.

[0256] Various examples have been referenced in this specification. Descriptions of features or functions of an example indicate which features or functions exist in that example. The use of the terms "example," "for example," "able," or "may" in the text indicates that, whether explicitly stated or not, these features or functions exist at least in the described example, and may, but not necessarily, exist in some or all other examples. Thus, "example," "for example," "able," or "may" refers to a specific instance of a class of examples. An instance's property can be a property of only that instance, or a property of the class, or a property of a subclass of a class that includes some, but not all, instances of that class. Therefore, it is implicitly disclosed that features described with reference to one example, and not another, may be used as part of a working composition in that other example where possible, but are not necessarily required to be used in that other example.

[0257] As used herein, “at least one of the following” and “at least one of the following” and similar wording (where a list of two or more elements is connected by “and” or “or”) means: at least any one of these elements, at least any two or more of these elements, or at least all of these elements.

[0258] Although examples have been described with reference to various examples in the preceding paragraphs, it should be understood that modifications may be made to the given examples without departing from the scope of the claims.

[0259] The features described above can be used in combinations other than those explicitly described above.

[0260] Although some features have been described with reference to certain characteristics, these functions can be performed by other features, whether or not they are described.

[0261] A description of a feature (such as a device or a component of a device) configured to perform a function or for performing a function should also be considered as disclosing a method for performing that function. For example, a description of a device configured to perform one or more actions or for performing one or more actions should also be considered as disclosing a method for performing those one or more actions with or without the device.

[0262] Although features have been described with reference to some examples, these features may also exist in other examples, whether or not they are described.

[0263] The terms “a,” “an,” or “the” are used in this document in an inclusive rather than exclusive sense. That is, any reference to X that includes a Y may include only one Y or more Ys unless the context explicitly indicates otherwise. If a “a,” “an,” or “the” is intended to be used in an exclusive sense, it will be explicit in the context. In some cases, “at least one” or “one or more” may be used to emphasize an inclusive meaning, but no exclusive meaning should be inferred from the absence of these terms.

[0264] The presence of a feature (or combination of features) in a claim is a reference to that feature or combination of features itself, as well as to features that achieve substantially the same technical effect (equivalent features). Equivalent features include, for example, features that are variations and achieve substantially the same result in substantially the same manner. Equivalent features include, for example, features that perform substantially the same function in substantially the same manner to achieve substantially the same result.

[0265] In this specification, various examples have been referenced to describe the characteristics of the examples using adjectives or adjective phrases. Such descriptions of the characteristics associated with the examples indicate that the characteristics exist exactly as described in some examples, and substantially as described in others.

[0266] The foregoing description illustrates some examples of this disclosure; however, those skilled in the art will recognize possible alternative structures and methodological features that provide equivalent functionality to the specific examples of such structures and features described above, and for the sake of brevity and clarity, have been omitted from the foregoing description. Nevertheless, the foregoing description should be understood to implicitly include references to such alternative structures and methodological features that provide equivalent functionality, unless such alternative structures or methodological features are explicitly excluded in the foregoing description of the examples of this disclosure.

[0267] Although efforts have been made in the foregoing specification to draw attention to those features deemed important, an applicant may seek protection by means of the claims for any patentable feature or combination of features shown in the foregoing references and / or the accompanying drawings, whether or not they have been emphasized.

Claims

1. A mobile access node device, comprising components for: A radio connection is provided between the mobile access node device and the user equipment; A radio connection is provided between the mobile access node device and the network; After the radio connection between the mobile access node device and the network is lost, the radio connection between the mobile access node device and the user equipment is suspended, and a UE context including the security context for the user equipment is stored. After the radio connection between the mobile access node device and the network is re-established, the UE context, including the security context for the user equipment, is transmitted to the network via the radio connection between the mobile access node device and the network.

2. The apparatus of claim 1, wherein the component for suspending the radio connection includes a component for performing a connection suspension process that suspends the radio resource control connection but maintains access layer security.

3. The apparatus of claim 1 or 2, further comprising a mobility entity configured to: suspend the radio connection between the mobile access node device and the user equipment, and store the UE context including the security context for the user equipment; and the mobility entity configured to: transmit the UE context including the security context for the user equipment to the network via the radio connection between the mobile access node device and the network.

4. The apparatus of claim 3, wherein the mobility entity is configured to transmit a UE hang-up notification message to the network to transmit the UE context including the security context for the user equipment.

5. The apparatus of claim 4, wherein the UE suspension notification message includes suspension identification information for the user equipment.

6. The apparatus according to any one of the preceding claims, comprising components for buffering uplink data received via the radio connection between the mobile access node device and the network when the radio connection between the mobile access node device and the network is lost; and Components for transmitting buffered uplink data to the network when the radio connection between the mobile access node device and the network is re-established.

7. A satellite comprising the apparatus of any of the preceding claims.

8. A method comprising: Provides a radio connection between the mobile access node device and the user equipment; A radio connection is provided between the mobile access node device and the network; After the radio connection between the mobile access node device and the network is lost, the radio connection between the mobile access node device and the user equipment is suspended, and a UE context including the security context for the user equipment is stored. After the radio connection between the mobile access node device and the network is re-established, the UE context, including the security context for the user equipment, is transmitted to the network via the radio connection between the mobile access node device and the network.

9. A computer program comprising instructions that, when executed by one or more processors, enable a device to: Provides a radio connection between the mobile access node device and the user equipment; A radio connection is provided between the mobile access node device and the network; After the radio connection between the mobile access node device and the network is lost, the radio connection between the mobile access node device and the user equipment is suspended, and a UE context including the security context for the user equipment is stored. After the radio connection between the mobile access node device and the network is re-established, the UE context, including the security context for the user equipment, is transmitted to the network via the radio connection between the mobile access node device and the network.

10. A mobile access node device, comprising components for: A radio connection is provided between the mobile access node device and the user equipment; A radio connection is provided between the mobile access node device and the network; After establishing a radio connection between the mobile access node device and the network, the UE context, including the security context for the user equipment, is transmitted from the network via the radio connection between the mobile access node device and the network. Data transmission parameters ; as well as Use the data transmission parameters to establish a data pipeline; After establishing a radio connection between the mobile access node device and the suspended user equipment, the suspended radio connection between the mobile access node device and the user equipment is restored using a UE context that includes a security context for the user equipment.

11. The apparatus of claim 10, wherein the components for restoring a suspended radio connection include components for performing a connection restoration process that restores the radio resource control connection without re-establishing access layer security.

12. The apparatus of claim 10 or 11, further comprising a mobility entity configured to transmit from the network, via the radio connection between the mobile access node device and the network, the UE context and data transmission parameters including the security context for the user equipment.

13. The apparatus of claim 12, wherein the mobility entity is configured to: restore a suspended radio connection between the mobile access node device and the user equipment using the UE context including a security context for the user equipment.

14. The apparatus of claim 12 or 13, wherein the mobility entity is configured to receive a UE context recovery notification message to transmit to the mobility entity the UE context including the security context for the user equipment.

15. The apparatus of claim 14, wherein the UE suspension notification message includes suspension identification information for the user equipment.

16. The apparatus according to any one of claims 10 to 15, comprising means for buffering downlink data received via the radio connection between the mobile access node device and the user equipment when the radio connection between the mobile access node device and the network is lost; and Components for transmitting buffered downlink data to the user equipment when the radio connection between the mobile access node device and the user equipment is established.

17. The apparatus according to any one of claims 10 to 16, configured as a satellite, and including components for notifying other satellites that data has been successfully delivered via an inter-satellite link or via the network after data has been successfully delivered to the user equipment.

18. The apparatus according to any one of claims 10 to 17, configured as a satellite, and including components for receiving instructions to delete buffered data from another satellite via an inter-satellite link or via the network.

19. A satellite comprising the means of any one of claims 10 to 17.

20. A method comprising: Provides a radio connection between the mobile access node device and the user equipment; A radio connection is provided between the mobile access node device and the network; After establishing a radio connection between the mobile access node device and the network, the UE context, including the security context for the user equipment, is transmitted from the network via the radio connection between the mobile access node device and the network. Data transmission parameters; and Use the data transmission parameters to establish a data pipeline; After establishing a radio connection between the mobile access node device and the suspended user equipment, the suspended radio connection between the mobile access node device and the user equipment is restored using a UE context that includes a security context for the user equipment.

21. A computer program comprising instructions that, when executed by one or more processors of a device, enable the device to: Provides a radio connection between the mobile access node device and the user equipment; A radio connection is provided between the mobile access node device and the network; After establishing a radio connection between the mobile access node device and the network, the UE context, including the security context for the user equipment, is transmitted from the network via the radio connection between the mobile access node device and the network. Data transmission parameters; and Use the data transmission parameters to establish a data pipeline; After establishing a radio connection between the mobile access node device and the suspended user equipment, the suspended radio connection between the mobile access node device and the user equipment is restored using a UE context that includes a security context for the user equipment.

22. A terrestrial network device comprising components for: Provide radio connectivity to the first mobile access node; Provide radio connectivity to the second mobile access node; After re-establishing the radio connection between the first mobile access node and the network The UE context, including a security context for the user equipment, is received from the first mobile access node via the radio connection between the first mobile access node and the network. The storage includes the UE context, which includes the security context for the user equipment. as well as After establishing a radio connection between the second mobile access node device and the network... The UE context, including the security context for the user equipment, and the downlink data pipeline parameters for the user equipment are transmitted from the network via the radio connection between the second mobile access node and the network.

23. The apparatus of claim 22, further comprising: suspending the downlink data pipeline of the user equipment after re-establishing a radio connection between the first mobile access node and the network; and comprising: communicating with a data control entity to cancel the suspension of the downlink data pipeline of the user equipment before confirming the establishment of a radio connection between the second mobile access node and the network.

24. The apparatus of claim 22 or 23, further comprising a mobility entity configured to: Receive the UE context, including the security context for the user equipment, from the mobility entity of the first mobile access node; and The mobility entity of the second mobile access node transmits the UE context, which includes the security context of the user equipment, and the data transmission parameters of the downlink data pipeline for the user equipment.

25. The apparatus of claim 24, wherein the mobility entity is configured to receive a UE suspension notification message, the UE suspension notification message transmitting the UE context including the security context for the user equipment.

26. The apparatus of claim 25, wherein the UE suspension notification message includes suspension identification information for the user equipment.

27. The apparatus according to any one of claims 22 to 26, comprising: Components for buffering downlink data when radio connection to the user equipment is lost via mobile access node; as well as Components for transmitting buffered downlink data to the second mobile access node when the radio connection between the second mobile access node device and the network is established.

28. The apparatus of any one of claims 22 to 27, wherein the mobility entity is configured to transmit a UE context recovery notification message to the mobility entity of the second mobile access node to transmit the UE context including the security context for the user equipment.

29. The apparatus of claim 28, wherein the UE suspension notification message includes suspension identification information for the user equipment.

30. The apparatus according to any one of claims 22 to 27, comprising components for: Provide radio connectivity to third mobile access nodes; After establishing a radio connection between the third mobile access node device and the network... Data transmission parameters, including the UE context for the security context of the user equipment and the downlink data pipeline for the user equipment, are transmitted from the network via the radio connection between the second mobile access node and the network.

31. The apparatus of claim 30, wherein the apparatus is configured to notify the second mobile access node and the third mobile access node that they are competing for access to the user equipment.

32. A method comprising: Provide radio connectivity to the first mobile access node; Provide radio connectivity to the second mobile access node; After re-establishing the radio connection between the first mobile access node and the network UE context, including the security context for the user equipment, is received from the first mobile access node via the radio connection between the first mobile access node and the network; The storage includes the UE context, which includes the security context for the user equipment. as well as After establishing a radio connection between the second mobile access node device and the network... The UE context, including the security context for the user equipment, and the downlink data pipeline parameters for the user equipment are transmitted from the network via the radio connection between the second mobile access node and the network.

33. A computer program comprising instructions that, when executed by one or more processors of a device, enable the device to: Provide radio connectivity to the first mobile access node; Provide radio connectivity to the second mobile access node; After re-establishing the radio connection between the first mobile access node and the network UE context, including the security context for the user equipment, is received from the first mobile access node via the radio connection between the first mobile access node and the network; The storage includes the UE context, which includes the security context for the user equipment. as well as After establishing a radio connection between the second mobile access node device and the network... The UE context, including the security context for the user equipment, and the downlink data pipeline parameters for the user equipment are transmitted from the network via the radio connection between the second mobile access node and the network.

Images