Apparatus, methods and computer programs
The apparatus and method for sending a request to the network to modify a single-access data session into a dual-boot data session solve the problem of low efficiency in subscription and energy management of existing dual-boot devices, and achieve more efficient data session conversion and resource management.
Patent Information
- Application Number
- CN202580028001.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-02-16
- Filing Date
- 2025-02-05
- Publication Date
- 2026-11-17
AI Technical Summary
Existing communication systems suffer from inefficiency and lack of flexibility in supporting the transition between single-access and dual-boot data sessions, particularly in the areas of subscription and energy management for dual-boot devices.
An apparatus and method are provided for sending a request to a network to modify a single-access data session into a dual-boot data session, including receiving and processing relevant rules and policies, managing energy conditions, and releasing or modifying the data session as needed to support subscription and energy management for dual-boot devices.
It improves the efficiency of dual-booting devices in switching between single-access and dual-booting data sessions, enhances system flexibility and energy management, and reduces resource waste.
Smart Images

Figure CN123125844A_ABST
Abstract
Description
Cross-references to related applications
[0001] This patent application claims priority to Indian Provisional Patent Application No. 202441011015, filed on February 16, 2024, the entire contents of which are incorporated herein by reference. Technical Field
[0002] This disclosure relates to methods, apparatus, and computer programs, and particularly, but not exclusively, to methods, apparatus, and computer programs related to dualsteer. Background Technology
[0003] A communication system can be viewed as a facility that enables a communication session between two or more entities (such as communication equipment, base stations, and / or other nodes) by providing carriers between various entities involved in the communication path.
[0004] Communication systems and related entities typically operate according to a given standard or specification that defines what the entities are allowed to do and how they should be implemented. The communication protocols and / or parameters that should be used for the connection are also usually defined. An example of a standard is the so-called 5G standard. Summary of the Invention
[0005] Some exemplary embodiments of this disclosure will be described with reference to certain aspects. These aspects are not intended to indicate key or essential features of the various exemplary embodiments of this disclosure, nor are they intended to limit its scope. Other features, aspects, and elements will be readily understood by those skilled in the art in light of this disclosure.
[0006] According to one aspect, an apparatus is provided, the apparatus comprising: means for sending a request to a network for a modification of a first data session supporting single access to a data session supporting dual bootstrapping, the first data session being associated with a first subscription of a dual bootstrapping device; and means for receiving a response from the network, the response indicating that the first data session supporting single access has been modified to a modified first data session supporting dual bootstrapping.
[0007] The device may include components for providing information identifying a first data session that supports dual booting, the information being used when a second data session is established to support dual booting, the second data session being associated with a second subscription of the dual booting device.
[0008] The first and second data sessions may include packet data unit sessions or protocol data unit sessions.
[0009] The component for sending can be used to send a request to the network for establishing a first data session supporting single access, the session establishment request including an indication that the first data session supporting single access is allowed to be modified into a data session supporting dual bootstrapping.
[0010] The device may include components for determining, in response to one or more of the following, that a first data session supporting single access will be modified to support a dual-boot data session: information received from the network; one or more rules or policies related to dual-boot; information related to the device; and information received from the controller of the dual-boot device.
[0011] One or more rules or policies related to dual booting may include one or more user equipment routing policies.
[0012] Information related to the device may include one or more energy-related conditions of the device.
[0013] The response from the network may include one or more rules and / or policies related to dual bootstrapping, indicating that the first data session supporting single access is modified to support dual bootstrapping.
[0014] The device may include a first user device, or a dual-boot device, associated with a first subscription.
[0015] The device may be a dual-boot device and may also include a second user device associated with a second subscription.
[0016] The device may include a user device that is either a dual-boot device or a first subscription and a second subscription associated with the user device.
[0017] The apparatus may include components for sending a request to the network to establish a second data session, the request including a request for a dual-boot data session and information associated with the modified first data session.
[0018] The information associated with the modified first data session may include the identity information of the modified first data session.
[0019] According to a second aspect, a method is provided, the method comprising: sending a request to a network for modification of a first data session supporting single access to a data session supporting dual bootstrapping, the first data session being associated with a first subscription of a dual bootstrapping device; and receiving a response from the network, the response indicating that the first data session supporting single access has been modified to a modified first data session supporting dual bootstrapping.
[0020] The method may include providing information identifying a first data session that supports dual booting, the information being used when establishing a second data session to support dual booting, the second data session being associated with a second subscription of the dual booting device.
[0021] The first and second data sessions may include packet data unit sessions or protocol data unit sessions.
[0022] The method may include sending a request to the network to establish a first data session supporting single access, the session establishment request including an indication that modifying the first data session supporting single access to a data session supporting dual bootstrapping is permitted.
[0023] The method may include a component that determines, in response to one or more of the following, that a first data session supporting single access will be modified to support a dual-boot data session: information received from the network; one or more rules or policies related to dual-boot; information related to the means of performing the method; and information received from the controller of the dual-boot device.
[0024] One or more rules or policies related to dual booting may include one or more user equipment routing policies.
[0025] Information related to the device may include one or more energy-related conditions of the device.
[0026] The response from the network may include one or more rules and / or policies related to dual bootstrapping, indicating that the first data session supporting single access is modified to support dual bootstrapping.
[0027] The method may include sending a request to the network to establish a second data session that supports dual bootstrapping, the request including a request for a data session that supports dual bootstrapping and information associated with a modified first data session.
[0028] The information associated with the modified first data session may include the identity information of the modified first data session.
[0029] This method can be performed by a device.
[0030] The device may include at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the device to perform at least any of the methods discussed with respect to the second aspect.
[0031] The device may include a first user device, or a dual-boot device, associated with a first subscription.
[0032] The device may be a dual-boot device and may also include a second user device associated with a second subscription.
[0033] The device may include a user device that is either a dual-boot device or a first subscription and a second subscription associated with the user device.
[0034] According to a third aspect, an apparatus is provided, comprising: components for determining that a first data session supporting dual booting is no longer needed to support dual booting, the first data session being associated with a first subscription of a dual booting device; and components for sending a request to a network to update the network that the first data session is no longer needed to support dual booting.
[0035] The component for sending can be used to send a session modification request to the network to modify a first data session that supports dual boots to a data session that supports single access, the request including an indication of the reason for the modification.
[0036] The component for sending can be used to send a session release request to the network for releasing a first data session that supports dual boots, the request including an indication of the reason for the release.
[0037] The component used for determination may be used to determine, in response to one or more of the following, that the first data session supporting dual boot is no longer needed to support dual boot: information received from the network; one or more rules or policies related to dual boot; information related to the device; and information received from the controller of the dual boot device.
[0038] One or more rules or policies related to dual booting may include one or more user equipment routing policies.
[0039] Information related to the device may include one or more energy-related conditions of the device.
[0040] The device may include a first user device, or a dual-boot device, associated with a first subscription.
[0041] The device may be a dual-boot device and may also include a second user device associated with a second subscription of the dual-boot device.
[0042] The device may include a user device that is either a dual-boot device or a first subscription and a second subscription associated with the user device.
[0043] According to the fourth aspect, a method is provided, the method comprising: determining that a first data session supporting dual booting is no longer needed to support dual booting, the first data session being associated with a first subscription of the dual booting device; and sending a request to the network to update the network that the first data session is no longer needed to support dual booting.
[0044] The method may include sending a session modification request to the network to modify a first data session that supports dual boots to a data session that supports single access, the request including an indication of the reason for the modification.
[0045] The method may include sending a session release request to the network for releasing a first data session that supports dual boots, the request including an indication of the reason for the release.
[0046] The method may include determining, in response to one or more of the following, that a first data session supporting dual boot is no longer needed to support dual boot: information received from the network; one or more rules or policies related to dual boot; information related to the apparatus performing the method; and information received from the controller of the dual boot device.
[0047] One or more rules or policies related to dual booting may include one or more user equipment routing policies.
[0048] Information related to the device may include one or more energy-related conditions of the device.
[0049] This method can be performed by a device.
[0050] The device may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the device to perform at least any of the methods discussed with respect to the fourth aspect.
[0051] The device may include a first user device, or a dual-boot device, associated with a first subscription.
[0052] The device may be a dual-boot device and may also include a second user device associated with a second subscription of the dual-boot device.
[0053] The device may include a user device that is either a dual-boot device or a first subscription and a second subscription associated with the user device.
[0054] According to a fifth aspect, an apparatus is provided, comprising: a component for receiving a session modification command from a network, the session modification command indicating that a first data session supporting dual boot will be modified to a data session supporting single access; and a component for sending a response to a request to the network, the response confirming that the first data session has been modified to support single access.
[0055] The session modification command can indicate that one or more rules related to dual boots should be removed.
[0056] The device may include a first user equipment, or a dual-boot device, associated with a first data session.
[0057] The device may be a dual-boot device and may also include a second user device associated with a second subscription of the dual-boot device.
[0058] The device may include a user device that is either a dual-boot device or a first subscription and a second subscription associated with the user device.
[0059] According to a sixth aspect, a method is provided, the method comprising: receiving a session modification command from a network, the session modification command indicating that a first data session supporting dual boot will be modified to a data session supporting single access; and sending a response to the network to the request, the response confirming that the first data session has been modified to support single access.
[0060] The session modification command can indicate that one or more rules related to dual boots should be removed.
[0061] This method can be performed by a device.
[0062] The device may include at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the device to perform at least any of the methods discussed with respect to the sixth aspect.
[0063] The device may include a first user equipment, or a dual-boot device, associated with a first data session.
[0064] The device may be a dual-boot device and may also include a second user device associated with a second subscription of the dual-boot device.
[0065] The device may include a user device that is either a dual-boot device or a first subscription and a second subscription associated with the user device.
[0066] According to a seventh aspect, a dual-booting device is provided, comprising: means for sending a request to a network for modifying a first data session supporting single access to a data session supporting dual bootstrapping, the first data session being associated with a first subscription of the dual-booting device; means for receiving from the network a response indicating that the first data session supporting single access has been modified to a data session supporting dual bootstrapping; and means for sending a request to the network for establishing a second data session supporting dual bootstrapping.
[0067] A session establishment request may include information identifying the first data session that supports dual bootstrapping.
[0068] The second data session can be associated with a second subscription of a dual-boot device.
[0069] The first and second data sessions include packet data unit sessions.
[0070] The component for sending a request to the network to modify the first data session can be used to send the request via the first access network, and the component for sending a session establishment request can be used to send the request via the second access network.
[0071] The component used to send a request to the network can also be used to send a request to the network to establish a first data session supporting single access, the session establishment request including an indication that the first data session supporting single access is allowed to be modified into a data session supporting dual bootstrapping.
[0072] A dual-booting device may include components for determining, in response to one or more of the following, that a first data session supporting single access will be modified to support a dual-booting data session: information received from the network; one or more rules or policies related to dual-booting; and information related to the dual-booting device.
[0073] One or more rules or policies related to dual booting may include one or more user equipment routing policies.
[0074] Information related to dual-boot devices may include one or more energy-related conditions for the dual-boot device.
[0075] The network response may include one or more rules and / or policies related to dual bootstrapping, indicating that a first data session supporting single access is modified to a data session supporting dual bootstrapping.
[0076] A dual-booting device may include a component for receiving a response from the network indicating that a second data session supporting dual-booting has been established, the response including one or more rules and / or policies related to dual-booting.
[0077] A dual-boot device may include a first user device, which is associated with a first subscription.
[0078] A dual-boot device may include a second user device associated with a second subscription.
[0079] A dual-boot device may include a user device, with a first subscription and a second subscription associated with the user device.
[0080] According to an eighth aspect, a method is provided, the method comprising: sending to a network a request for modification of a first data session supporting single access to a data session supporting dual bootstrapping, the first data session being associated with a first subscription of a dual bootstrapping device; receiving from the network a response indicating that the first data session supporting single access has been modified to a data session supporting dual bootstrapping; and sending to the network a request for establishing a second data session supporting dual bootstrapping.
[0081] The aforementioned second data session can be associated with a second subscription of the dual-boot device.
[0082] A session establishment request may include information identifying the first data session that supports dual bootstrapping.
[0083] The first and second data sessions include packet data unit sessions.
[0084] The method may include sending a request via a first access network, and sending a session establishment request may be used to send a request via a second access network.
[0085] The method may include sending a request to the network to establish a first data session supporting single access, the session establishment request including an indication that modifying the first data session supporting single access to a data session supporting dual bootstrapping is permitted.
[0086] The method may include determining, in response to one or more of the following, that a first data session supporting single access will be modified to support a dual-boot data session: information received from the network; one or more rules or policies related to dual-boot; and information related to the dual-boot device.
[0087] One or more rules or policies related to dual booting may include one or more user equipment routing policies.
[0088] Information related to dual-boot devices may include one or more energy-related conditions for the dual-boot device.
[0089] The response from the network may include one or more rules and / or policies related to dual bootstrapping, indicating that the first data session supporting single access is modified to support dual bootstrapping.
[0090] The method may include receiving a response from the network indicating that a second data session supporting dual bootstrapping has been established, the response including one or more rules and / or policies related to dual bootstrapping.
[0091] This method can be performed by a device.
[0092] The device may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the device to perform at least any of the methods discussed in relation to the eighth aspect.
[0093] The device can be a dual-boot device, in which a first user equipment is associated with a first data session.
[0094] A dual-boot device may include a first user device, which is associated with a first subscription.
[0095] A dual-boot device may include a second user device associated with a second subscription.
[0096] A dual-boot device may include a user device, with a first subscription and a second subscription associated with the user device.
[0097] According to a ninth aspect, a dual-booting device is provided, comprising: a component for removing a first dual-booting session when dual-booting is no longer needed, the first data session being associated with a first subscription of the dual-booting device; and a component for sending a modification request to a network for modifying a second data session supporting dual-booting to a data session supporting single access, the second data session being associated with a second subscription of the dual-booting device.
[0098] A session modification request may include an indication of the reason for the modification.
[0099] A dual-boot device may include a first user device, which is associated with a first subscription.
[0100] A dual-boot device may include a second user device associated with a second subscription.
[0101] A dual-boot device may include a user device, with a first subscription and a second subscription associated with the user device.
[0102] According to a tenth aspect, a method is provided, the method comprising: removing a first dual-boot session when dual-booting is no longer needed, the first data session being associated with a first subscription of the dual-booting device; and sending a modification request to the network for modifying a second data session supporting dual-booting to a data session supporting single access, the second data session being associated with a second subscription of the dual-booting device.
[0103] A session modification request may include an indication of the reason for the modification.
[0104] This method can be performed by a device.
[0105] The device may include at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the device to perform at least any of the methods discussed in relation to the tenth aspect.
[0106] A dual-boot device may include a first user device, which is associated with a first subscription.
[0107] A dual-boot device may include a second user device associated with a second subscription.
[0108] A dual-boot device may include a user device, with a first subscription and a second subscription associated with the user device.
[0109] According to the eleventh aspect, a dual-booting device is provided, comprising: a component for removing a first dual-booting session when dual-booting is no longer needed, the first data session being associated with a first subscription of the dual-booting device; and a component for receiving from a network information indicating that a second data session supporting dual-booting has been modified to support a single-access data session, the second data session being associated with a second subscription of the dual-booting device.
[0110] A dual-boot device may include components for determining that dual boot is no longer needed in response to one or more of the following: information received from the network; one or more rules or policies related to dual boot; and information related to the dual-boot device.
[0111] One or more rules or policies related to dual booting may include one or more user equipment routing policies.
[0112] Information related to a dual-guide device may include one or more energy-related conditions of the device.
[0113] The component for removing the first data session can be used to send a session release request to the network for the release of the first data session, the session release request including an indication of the reason for the release of the first data session.
[0114] The component for removing the first data session may remove the first data session by receiving a session release request from the network for releasing the first data session, the session release request including an indication of the reason for releasing the first data session.
[0115] According to the twelfth aspect, a method is provided, the method comprising: removing a first dual-boot session when dual-booting is no longer needed, the first data session being associated with a first subscription of the dual-booting device; and receiving from a network information indicating that a second data session supporting dual-booting has been modified to support a single-access data session, the second data session being associated with a second subscription of the dual-booting device.
[0116] The method may include determining that dual booting is no longer needed in response to one or more of the following: information received from the network; one or more rules or policies related to dual booting; and information related to the dual booting device.
[0117] One or more rules or policies related to dual booting may include one or more user equipment routing policies.
[0118] Information related to a dual-guide device may include one or more energy-related conditions of the device.
[0119] The method may include removing a first data session by sending a session release request to the network for the release of the first data session, the session release request including an indication of the reason for the release of the first data session.
[0120] The method may include removing a first data session by receiving a session release request from the network for releasing the first data session, the session release request including an indication of the reason for releasing the first data session.
[0121] This method can be performed by a device.
[0122] The device may include at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the device to perform at least any of the methods discussed in relation to the twelfth aspect.
[0123] A dual-boot device may include a first user device, which is associated with a first subscription.
[0124] A dual-boot device may include a second user device associated with a second subscription.
[0125] A dual-boot device may include a user device, with a first subscription and a second subscription associated with the user device.
[0126] According to a thirteenth aspect, an apparatus is provided, comprising: a component for receiving information identifying an address of a first data session supporting dual bootstrapping, the first data session being associated with a first subscription; and a component for sending a request to a network for establishing a second data session supporting dual bootstrapping, the session establishment request including information identifying an address of the first data session supporting dual bootstrapping, wherein the first data session and the second data session have the same address.
[0127] The address can be an Internet Protocol address.
[0128] Information identifying the address of the first data session supporting dual boot can be received from the control unit of the dual boot device.
[0129] The information identifying the address of the first data session that supports dual boots can be the packet data unit session identifier of the first data session that supports dual boots.
[0130] The first and second data sessions may include packet data unit sessions.
[0131] The device may include a component for receiving information from the network indicating that a second data session supporting dual boot has been established using an address.
[0132] The receiving component can be used to receive one or more rules or policies related to dual bootstrapping.
[0133] The device may include a first user device of a dual-boot device, the first user device being associated with a first subscription.
[0134] The device may be a dual-boot device and may also include a second user device associated with a second subscription.
[0135] The device may include a user device with dual boot devices, with a first subscription and a second subscription associated with the user device.
[0136] According to the fourteenth aspect, a method is provided, the method comprising: receiving information identifying an address of a first data session supporting dual bootstrapping, the first data session being associated with a first subscription; and sending a request to a network for establishing a second data session supporting dual bootstrapping, the session establishment request including information identifying an address of the first data session supporting dual bootstrapping, wherein the first data session and the second data session have the same address.
[0137] The address can be an Internet Protocol address.
[0138] Information identifying the address of the first data session supporting dual boot can be received from the control unit of the dual boot device.
[0139] The information identifying the address of the first data session that supports dual boots can be the packet data unit session identifier of the first data session that supports dual boots.
[0140] The first and second data sessions may include packet data unit sessions.
[0141] The device may include a component for receiving information from the network indicating that a second data session supporting dual boot has been established using an address.
[0142] The receiving component can be used to receive one or more rules or policies related to dual bootstrapping.
[0143] This method can be performed by a device.
[0144] The device may include at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the device to perform at least any of the methods discussed in relation to the fourteenth aspect.
[0145] The device may include a first user equipment, or a dual-boot device, associated with a first data session.
[0146] The device may be a dual-boot device and may also include a second user device associated with a second subscription of the dual-boot device.
[0147] The device may include a user device that is either a dual-boot device or a first subscription and a second subscription associated with the user device.
[0148] According to a fifteenth aspect, an apparatus is provided, comprising: components for receiving a request to establish a second data session for a dual-boot device, the second data session being associated with a second subscription; and components for allocating a first address to the second data session, the first address being associated with a first data session, the first data session supporting dual-booting for the dual-boot device.
[0149] The device may include components for providing a response to a request, the response including a first address and one or more dual-boot rules or policies.
[0150] According to a sixteenth aspect, an apparatus is provided, comprising: components for receiving a request for modifying a first data session supporting single access to a data session supporting dual bootstrapping, the first data session being associated with a first subscription of a dual bootstrapping device; and components for providing the dual bootstrapping device with one or more rules or policies related to dual bootstrapping.
[0151] The request may include identity information associated with the first data session.
[0152] According to the seventeenth aspect, an apparatus is provided, comprising: components for determining that a first data session supporting dual booting is modified to a single access session, the first data session being associated with a first subscription of a dual booting device; and components for providing a request or command that one or more dual booting device-related policies of the dual booting device will be removed or updated.
[0153] The apparatus of any one of aspects fifteen to seventeen may include components for implementing session management functions.
[0154] The apparatus of any one of aspects fifteen through seventeen can be a session management function.
[0155] According to the eighteenth aspect, a method is provided, the method comprising: receiving a request to establish a second data session for a dual-booting device, the second data session being associated with a second subscription; and assigning a first address to the second data session, the first address being associated with a dual-booting-enabled first data session of the dual-booting device.
[0156] The method may include providing a response to the request, the response including a first address and one or more dual-boot rules or policies.
[0157] According to the nineteenth aspect, a method is provided, the method comprising: receiving a request for modification of a first data session supporting single access to a data session supporting dual bootstrapping, the first data session being associated with a first subscription of a dual bootstrapping device; and providing the dual bootstrapping device with one or more rules or policies related to dual bootstrapping.
[0158] The request may include identity information associated with the first data session.
[0159] According to the twentieth aspect, a method is provided, the method comprising: determining that a first data session supporting dual booting is modified to a single access session, the first data session being associated with a first subscription of the dual booting device; and providing a request or command that one or more dual booting device-related policies of the dual booting device will be removed or updated.
[0160] The method of any one of aspects fifteen to seventeen can be performed by a device.
[0161] The apparatus may include at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to perform at least any of the methods discussed with respect to aspects fifteen through seventeen.
[0162] This device can perform session management functions.
[0163] According to one aspect, a computer-readable medium having program instructions stored thereon for performing at least one of the methods described above is provided.
[0164] According to one aspect, a non-transitory computer-readable medium having program instructions stored thereon for performing at least one of the methods described above is provided.
[0165] According to one aspect, a non-volatile tangible storage medium having program instructions stored thereon for performing at least one of the methods described above is provided.
[0166] Many different aspects have been described above. It should be understood that other aspects can be provided through any combination of two or more of the aspects described above.
[0167] Various other aspects are also described in the following detailed description and the appended claims. Attached Figure Description
[0168] Some exemplary embodiments will now be described by way of example only with reference to the accompanying drawings, in which: Figure 1 A schematic diagram of a 5G system is shown; Figure 2 The first example of a dual-boot device and a 5GC UPF is illustrated schematically; Figure 3 A second example of a dual-boot device and a 5GC UPF is schematically shown; Figure 4 A schematic diagram of the device is shown; Figures 5a to 5c The first process is illustrated schematically, in which a single-access PDU session is updated to act as a dual-boot PDU session; Figure 6a and Figure 6b The second process is illustrated schematically, in which a dual-booted PDU session is downgraded to a single-access PDU session; Figure 7 The first method of some example embodiments is shown: Figure 8 The second method is shown in some example embodiments; Figure 9 A third method is shown in some example embodiments; Figure 10 The fourth method is illustrated in some example embodiments; Figure 11 The fifth method is shown in some example embodiments; Figure 12 The sixth method is shown in some example embodiments; Figure 13 The seventh method is shown in some example embodiments; Figure 14 An eighth method is shown in some example embodiments; and Figure 15 The ninth method of some example embodiments is shown. Detailed Implementation
[0169] The following describes certain example embodiments with reference to a communication device capable of communicating via a wireless communication system (e.g., a cellular system or a mobile communication system) serving such a communication device. Example wireless communication systems include... Figure 1 As shown.
[0170] Figure 1A schematic representation of a communication network including a 5G system (5GS) is shown.
[0171] Communications may include a Public Land Mobile Network (PLMN). The PLMN may include a radio access network comprising multiple 5G (Radio) Access Networks (RANs) (illustrated as 5G-RAN 3GPP-1 and 5G-RAN 3GPP2), a 5G Core Network (5GC), one or more Application Functions (AFs), and one or more Data Networks (DNs) 210. Figure 1 In the examples shown, some example embodiments of the dual-steer devices 200 / 300 connect to the 5GC via two different RANs (e.g., 5G-RAN 3GPP-1 and 5G-RAN 3GPP2). Some example embodiments of the dual-steer devices 200 / 300 will be described in more detail later. However, it should be understood that dual-steer devices can connect to one or more different access networks. Figure 1 The example RAN shown.
[0172] Some examples of access networks are 5G (radio) access networks, such as 3GPP RANs. Other examples of access networks can be untrusted or wired non-3GPP access to the 3GPP core (Non-3GPP Interoperability Function (N3IWF) or Wired 5G Access Gateway Function (W-AGF)). In another example, one RAN can correspond to a terrestrial (radio access) network, and another RAN can correspond to a terrestrial (radio access) network. In yet another example, the two (R)ANs can be operated by different operators (e.g., (multiple) different PLMNs) and therefore can be controlled by (multiple) different AMFs.
[0173] A 3GPP access network can be a radio access network (RAN) specified in the 3GPP standard, such as a 5G RAN.
[0174] 5G RAN may include one or more base stations. Base stations may be evolved Node Bs (eNBs) or gNodeBs (gNBs). gNBs may include distributed units connected to one or more centralized units.
[0175] Figure 1 The 5GC shown includes network functions (NF). Figure 1The network functions shown include Unified Data Repository (UDR), Network Exposure Function (NEF), Network Repository Function (NRF), User Data Management (UDM), Policy Control Function (PCF), Access and Mobility Management Function (AMF), Authentication Server Function (AUSF), Session Management Function (SMF), and User Plane Function (UPF) 206. It should be understood that more than one network function of a given type can be provided in 5GC.
[0176] Some embodiments involve so-called "dual steer devices".
[0177] A dual-booting device is a device that supports service bootstrapping, service splitting, and / or service handover of user data across two access networks. The user data may involve user equipment data sessions. These two access networks can be different access networks. The access networks can be two 3GPP access networks. For example, in some embodiments, these two access networks can be two different 3GPP access networks. For example, these two different access networks can be provided by different RANs.
[0178] Service routing can direct a service to one or both of the two access networks. A service can be split between the two access networks. In another example, a service can be directed to only one of the access networks. In yet another example, a service can be switched from one access network to the other.
[0179] A dual-boot device can be associated with a first subscription and a second subscription. The first subscription is associated with a first subscriber identifier, and the second subscription is associated with a second subscriber identifier. The first subscriber identifier and the second subscriber identifier are different subscriber identifiers. The first subscriber identifier and the second subscriber identifier can be unique identifiers used to identify subscribers in the network. The first subscriber identifier and the second subscriber identifier can include SUPI (Subscription Permanent Identifier) or any other suitable subscriber identifier.
[0180] Each of the first and second identifiers can be stored in the corresponding subscriber identity module (SIM). For example, the SIM can be stored in a Universal SIM (USIM).
[0181] The first and second subscriber identities can be linked to a single subscription profile.
[0182] When a dual-booting device provides dual booting, it establishes a first data session with the network via a first access network, associated with a first subscriber identifier, and a second data session with the network via a second access network, associated with a second subscriber identifier. Services such as user data can be transmitted to the network via the first and second data sessions. Services can be booted, switched, and / or split between the first and second sessions.
[0183] For example, the business may include data from applications on dual-boot devices.
[0184] The first and second sessions can be Packet Data Unit (PDU) sessions.
[0185] refer to Figure 2 , Figure 2 A first example of a dual-booting device 200 is shown. In this example, the dual-booting device 200 includes a first UE (UE1) and a second UE (UE2). The first UE (UE1) is associated with a first subscriber identifier SUPI-1, and the second UE is associated with a second subscriber identifier SUPI-2. For example, the first UE (UE1) may have a first SIM (e.g., a USIM) storing the first subscriber identifier SUPI-1, and the second UE may have a second SIM (e.g., a USIM) storing the second subscriber identifier SUPI-2.
[0186] A so-called dual boot layer 204 is provided. The dual boot layer includes control functions. The dual boot layer can be implemented using computer-executable code running on at least one processor. The dual boot layer can be referred to as a controller. The dual boot layer can be implemented through, for example... Figure 4 The device shown is used to achieve this.
[0187] The first UE (UE1) has network access via the first access network 3GPP1, and the first UE (UE2) has network access via the second access network 3GPP2. The first access network and the second access network are different.
[0188] The dual bootstrapping layer will manage the bootstrapping, handover, and / or splitting of services to one or both access networks via the first UE and the second UE.
[0189] If needed, dual-boot devices can support simultaneous data transmission over two access networks.
[0190] Services managed by the dual bootstrap layer can include application services from application 202, or any other suitable services.
[0191] In some embodiments, the dual-guide device may be housed, for example, within a single housing.
[0192] In other embodiments, the dual-booting device can be implemented as a system. When the dual-booting device is implemented as a system, the dual-booting layer portion of the system is arranged to communicate with, for example, an application and a first UE and a second UE. This communication can be wired and / or wireless.
[0193] refer to Figure 3 , Figure 3 A second example of a dual-booting device 300 is shown. In this example, the dual-booting device includes a UE 302. The UE 302 is associated with a first subscriber identifier SUPI-2 and a second subscriber identifier SUPI-2. For example, the UE may have a first SIM (e.g., USIM) storing the first subscriber identifier SUPI-1 and a second SIM (e.g., USIM) storing the second subscriber identifier SUPI-2.
[0194] Similarly, as Figure 2 As shown, a dual bootstrapping layer 204 is provided. In some embodiments, the dual bootstrapping layer and the application can be located within the UE. The dual bootstrapping device can be implemented within the UE. In other embodiments, the application and / or the dual bootstrapping layer can be located outside the UE.
[0195] The UE has a first network access associated with a first subscriber identifier via a first access network 3GPP1 and a second network access associated with a second subscriber identifier via a second access network 3GPP2. The first access network and the second access network are different.
[0196] Regardless of the implementation of the dual-booting device, the dual-booting layer 204 can be configured with one or more rules / policies to control the bootstrapping, switching, and / or splitting of services. The dual-booting layer is responsible for bootstrapping UL (uplink) data, i.e., data from the dual-booting device to the network.
[0197] like Figure 2 and Figure 3 As shown, a User Plane Function (UPF) 206 is provided, which is responsible for bootstrapping DL (downlink) data, i.e., data from the network to the dual-boot device. The UPF is configured with one or more rules / policies 208 for controlling the bootstrapping, switching, and / or splitting of DL services.
[0198] Services from the dual-booting device can be provided to DN 210 by UPF 206. DN 210 can provide services to the UPF for the dual-booting device.
[0199] In some embodiments, a dual-booting device can support service booting, splitting, and / or switching of user data across two access networks.
[0200] Data anchoring can be set in an HPLMN (Household Public Land Mobile Network) or an SNPN (Standalone Non-Public Network). User data can be used for different services or for the same service.
[0201] In some embodiments, a dual-booting device may be designed to minimize service disruptions when switching user data between two access networks.
[0202] In some embodiments, a dual-booting device can support changing a 3GPP access network to a non-3GPP access network with the same subscription (and vice versa).
[0203] Some embodiments of dual-boot devices may support one or more of the following service boot, switching, and / or splitting examples: Used for service orientation, handover, and / or splitting between two 3GPP access networks belonging to the same or different PLMNs or SNPNs. These two 3GPP access networks can be associated with the same or different RATs (Radio Access Technologies). An example of using different types of 3GPP access is one 3GPP access corresponding to a terrestrial access network (TNT) and another 3GPP access corresponding to a non-terrestrial access network; Used for service bootstrapping, handover, and / or splitting between two 3GPP access networks, one PLMN and one PNI-NPN (Public Network Integration of Non-Public Network). These two 3GPP access networks can be associated with the same or different RATs (Radio Access Technologies); and / or Service bootstrapping, handover, and / or splitting occurs across LTE / EPC (Long Term Evolution / Evolved Packet Core) and NR / 5GC (New Radio / 5G Core), and is anchored to 5GC. In other words, one access network can be a 4G access network, and the other can be a 5G access network.
[0204] A dual-boot PDU (Packet Data Unit) session is a PDU session triggered by a dual-boot device and designed for dual-booting. Dual-booting is the bootstrapping, switching, and / or splitting of a service. The service can be an application's service.
[0205] In the following examples, a dual-booting device with two UEs is used to illustrate some example embodiments, each UE having its own subscriber identifier. However, it should be understood that the example embodiments can also be used with a dual-booting device having UEs, one portion of which is associated with a subscriber identifier, and another portion of which is associated with a different subscriber identifier. In the following text, reference to a portion of a UE refers to a dual-booting device having UEs, one portion of which is associated with a first subscriber identifier, and another portion of which is associated with a second subscriber identifier.
[0206] To enable dual-booting, the dual-booting device registers with each of two access networks (which may be the same or different). Each access network can be a 3GPP network access. Each registration is triggered by a different subscription, such as SUPI and / or IMSI (International Mobile Subscriber Identity). After registration, the dual-booting device establishes two dual-booting PDU sessions, one for each different subscription. The first dual-booting PDU session (PDU session 1) travels on the first access network, where the first dual-booting PDU session (PDU session 1) corresponds to the first identity SUPI-1. The first identity SUPI-1 corresponds to the first registration. The first dual-booting PDU session (PDU session 1) has a tributary (user plane resource) on the first access network.
[0207] The second dual-booted PDU session (PDU session 2) travels on the second access network, where the second dual-booted PDU session (PDU session 2) corresponds to the second identity SUPI-2. The second identity SUPI-2 corresponds to the second registration. The second dual-booted PDU session (PDU session 2) has a tributary (user plane resource) on the second access network.
[0208] In some embodiments, a dual-booting device may have public network access for two sessions associated with different subscriptions. The two UEs or two portions of a UE in a dual-booting device may be connected to the same cell. In other words, the two sessions may be via a public access network. The first and second access networks in the above example may be the same access network.
[0209] The first dual-boot PDU session and the second dual-boot PDU session can serve a specific application service.
[0210] In some embodiments, the core network can be the same for both registrations.
[0211] A single-access PDU session is a PDU session established by the UE and associated with only one access network. A single-access PDU session does not have any rules or policies for handover / bootstrapping / split application services. The PDU session has user plane resources on only one access network. This single-access PDU session does not support dual bootstrapping.
[0212] A dual-boot device can have two UEs or one UE (with two identities), where each UE can have a single access PDU session on the network access (like any regular UE), as discussed. For example, each UE can serve services specific to that UE's applications.
[0213] When a dual-boot device needs to start operating in dual-boot mode to serve applications requiring dual-booting, the same IP (Internet Protocol) address is assigned and used for two dual-boot PDU sessions. These two dual-boot PDU sessions are established to serve the application services of the applications requiring dual-booting. It should be understood that in other embodiments, the address may not be an IP address. For example, the same address can be used to support, for example, Ethernet sessions.
[0214] In some embodiments, a dual-boot device can update a single-access PDU session to serve as one of the dual-boot PDU sessions and add another dual-boot PDU session.
[0215] In some embodiments, the UE or a portion of the UE of a dual-boot device may provide the network with an indication during the establishment of a single-access PDU session that an upgrade to dual-boot is permitted during the lifetime of that PDU session. This indication may be a flag. The AMF uses this indication to ensure that the AMF selects an SMF that supports dual-boot.
[0216] When a dual-booting UE or a portion of a UE receives a request from the dual-booting layer, the UE or a portion of the UE can initiate a PDU session modification procedure for its single-access PDU session. The UE or a portion of the UE can provide an indication to the network that the single-access PDU session will be updated to a dual-booting PDU session. This indication can be a flag. This indication can be used by the SMF and / or AMF.
[0217] In some embodiments, as an alternative to the PDU session modification process, the SM (Session Management) NAS (Non-Access Stratum) or MM (Mobility Management) NAS process can be used to provide the network with an indication that a single-access PDU session will be updated to a dual-boot PDU session.
[0218] If a request from a UE or a portion of a UE to update a single-access PDU session to a dual-boot PDU session is accepted by the network, the network can provide dual-boot rules / policies to that UE or portion of the UE. The SMF can accept requests from a UE or a portion of the UE to update a single-access PDU session to a dual-boot PDU session. The SMF can provide dual-boot rules / policies to the UE or a portion of the UE. Providing dual-boot rules to the UE or a portion of the UE will indicate to the UE or a portion of the UE that the PDU session has been updated to a dual-boot PDU session. The UE or a portion of the UE can provide the dual-boot PDU session ID to the dual-boot server in the dual-boot device.
[0219] In some embodiments, if a request from the UE or a portion of the UE to update a single-access PDU session to a dual-boot PDU session is rejected by the network (e.g., SMF), a response indicating that the request has been rejected is provided. The response may be provided by the network. The response may include an indication to the UE or a portion of the UE of the reason for the rejection of the request. For example, the reason may indicate that the update is not allowed, the update is not supported, or the update is not possible. The indication may be in the form of one or more error codes.
[0220] For example, the request can be rejected if the network does not support PDU sessions for dual-booting. The request can also be rejected when, for example, operator policies and / or subscription policies disallow dual-booting PDU sessions for the UE or a portion of the UE. For instance, the request can be rejected if the network supports the capability but does not currently have the resources available to establish a dual-booting PDU session. The request can also be rejected due to one or more conditions in the network area associated with the UE or a portion of the UE. These conditions could be, for example, network congestion detected in the RAN.
[0221] Then, another UE or another part of the UE receives a request from the dual-booting layer along with the linked PDU session ID of the UE or part of the UE requesting to update the PDU session to a dual-booting PDU session. The other UE or another part of the UE can then initiate a PDU session establishment procedure to establish a second dual-booting PDU session.
[0222] In some embodiments, the triggering of a UE request to update a single-access PDU session to a dual-booting PDU session may be in response to the UE or a portion of the UE receiving a request from the dual-booting layer. The request from the dual-booting layer may be based on the dual-booting layer's evaluation of URSP (UE Routing Policy) rules / policies. For example, dual-booting may be preferred for some applications.
[0223] In some embodiments, the triggering of a UE or a portion of a UE requesting to update a single access PDU session to a dual-booted PDU session or to update to a dual-booted PDU session may be in response to an evaluation of URSP rules / policies by one or the other of the UE or a portion of a dual-booted device.
[0224] In some embodiments, it can be determined whether an established single-access PDU session is suitable to serve as a dual-booted PDU session. For example, it can be determined whether the parameters of the established single-access PDU session are the same as those required for a dual-booted PDU session. For example, one or more parameters may be DNN (Data Network Name), S-NSSAI (Single Network Slice Selection Auxiliary Information), PDU session type, etc.
[0225] In some embodiments, the power and / or energy conditions of one or more UEs or one or more portions of the UE and / or dual-booting device may be considered. For example, reusing an existing PDU session instead of creating a new PDU session for dual-booting can be more power efficient.
[0226] Some implementations can ensure that the same IP address is used for two dual-boot PDU sessions. In some embodiments, this may be necessary for processing certain application services.
[0227] Dual-boot devices can ensure that the same IP address is used for two dual-boot PDU sessions.
[0228] To maintain the same IP address for two dual-boot PDU sessions, when the second UE or another part of the two UEs in a dual-boot device receives a request from the dual-boot layer to establish a new dual-boot PDU session, the second UE or the other part of the UE provides an indication of the identity of the linked PDU session of the first UE or the part of the UE. This indication may be referred to as the "Linked Dual-Boot PDU Session ID". This indication can be provided by the second UE or the other part of the UE during the establishment of the new dual-boot PDU session. This indicates the identity of the dual-boot PDU session of the first UE or the part of the UE to the network (e.g., SMF). This allows the IP address associated with an existing dual-boot PDU session to be reused for a new dual-boot PDU session.
[0229] In some embodiments, one or more of the dual-booted PDU sessions can be downgraded to single-access PDU sessions. One of the two dual-booted PDU sessions can be released, leaving one single-access PDU session.
[0230] In some embodiments, one or more portions of the two UEs in a dual-booting device may trigger a PDU session release procedure to the network for a dual-booting PDU session. This PDU session release procedure may be triggered by the dual-booting layer. The PDU session release procedure may include a reason indicating the release in dual-booting mode.
[0231] In some embodiments, the network may trigger a PDU session release process for a PDU session within a PDU session. This may be due to network policies and / or resource conditions.
[0232] In some embodiments, the network can remove dual-boot rules from both the UE or a portion of the UE and the UPF.
[0233] In some embodiments, a dual-boot PDU session can be downgraded to a single-access PDU session when the application no longer requires dual booting. This could be due to an updated URSP policy.
[0234] In some embodiments, a dual-boot PDU session may be downgraded to a single-access PDU session, taking into account the power / energy conditions of the dual-boot device. For example, if the dual-boot device has low battery power or if it must enter a low-power mode, the dual-boot device may need to stop dual-booting.
[0235] In some embodiments, based on network considerations regarding power consumption, resource consumption, congestion, and / or overload, a dual-boot PDU session can be downgraded to a single-access PDU session. The network may request the dual-boot device to stop providing dual booting.
[0236] Refer to Figure 5A- Figure 5c This illustrates a first example of the process of some embodiments.
[0237] In this example process, the dual-boot device is able to update a single-access PDU session to act as a dual-boot PDU session.
[0238] In this example, the dual-boot device can ensure that the same IP address is used for two dual-boot PDU sessions. This allows for the processing of a specific application service.
[0239] In this example, there is a first access network (3GGP access 1) and a second access network (3GPP access 2).
[0240] As referenced at 0a, the first UE (UE-1) or the first part of the UE may optionally indicate, when establishing a single-access PDU session (PDU1), that upgrade to dual boot is permitted during the lifetime of that PDU session. This indication may be provided in the form of a flag.
[0241] This instruction can be provided to the AMF. It can be included in the NAS signaling message from the UE to the AMF. This instruction helps the AMF select an SMF that supports dual booting.
[0242] During the establishment of a single-access PDU session (PDU1), the AMF can provide the SMF with an indication that the PDU session can be upgraded to dual-boot during its lifetime. This indication can help the SMF select the PCF and / or UPF that support dual-boot.
[0243] During the successful establishment of a single-access PDU session (PDU1), the SMF can indicate to the first UE (UE-1) or the first part of the UE whether the single-access PDU session (PDU1) can be upgraded to a dual-booted PDU session. This allows the first UE (UE-1) or the first part of the UE to know in advance whether the UE or the part of the UE can later request the modification from the single-access PDU session (PDU1) to the dual-booted PDU session.
[0244] As referenced at 0b, the second UE (UE-2) or the second part of the UE is registered to the network via the second access network (3GPP Access 2). The second UE (UE-2) or the second part of the UE may or may not have established a second single access PDU session (PDU2) on the second access network (3GPP Access 2).
[0245] As referenced at point 1, the first UE (UE-1) or the first part of the UE and / or the second UE (UE-2) or the second part of the UE decide to modify the first single-access PDU session (PDU1) and / or the second single-access PDU session (PDU2) (if established). This can be based on a trigger from the dual-booting layer, a trigger from the network, and / or a determination by one or both of the first UE and the second UE (UE-1 and UE-2). This can be as described above. For example, the first UE (UE-1) or the second UE (UE-2) can determine the need for dual-booting based on an evaluation of URSP rules / policies.
[0246] As referenced at point 2, the first UE (UE-1) or a first part of the UE sends a request to modify or update the first single-access PDU session (PDU1) to a dual-booting PDU session. The request for modification may include an indication that dual booting is requested. This indication may include flags. The request may identify the first single-access PDU session (PDU1). The request may be provided to the AMF.
[0247] This indication can be provided in an MM message (e.g., transmitted via a UL NAS). Alternatively, it can be provided in an SM message (e.g., a PDU session modification request) sent within an MM message.
[0248] As referenced in section 3, the AMF provides the SMF with a request to modify or update the first single-access PDU session (PDU1) to a dual-boot PDU session. This includes an indication that dual booting is requested. The request may identify the first single-access PDU session (PDU1).
[0249] This instruction can be provided in the PDU session modification request. This request can also be provided in the PDU session update SM context request.
[0250] As cited in section 4, the SMF accepts the request and obtains the policies / rules related to the dual-boot device from the PCF.
[0251] As cited in point 5, the SMF will provide the UPF with the policies / rules related to the dual-boot device obtained from the PCF, which are used to serve the PDU session of the first UE or the first part of the UE.
[0252] As referenced at point 6, the SMF will provide the AMF with the policies / rules related to the dual-boot device obtained from the PCF. This can be provided in the PDU session modification command. This can be Common_N1N2MsgTransfer.
[0253] As referenced at point 7, the AMF provides the acquired policies / rules related to the dual-boot device to the first UE (UE-1) or the first part of the UE. This can be provided in the PDU session modification command. This can be done via DL NAS transmission.
[0254] As cited at point 8, the first UE (UE-1) or the first part of the UE considers the migration from a single-access PDU session to a dual-booting PDU session to be successful upon receiving the dual-booting rule / policy.
[0255] As referenced at point 9, the first UE (UE-1) or the first part of the UE sends a message to the AMF indicating that the PDU session modification is complete. This can be done via UL NAS transmission.
[0256] As referenced at point 10, the second UE (UE-2) or the second part of the UE decides to establish a new dual-booting PDU session (PDU3) that uses the same IP address as the dual-booting PDU session 1 (PDU 1) used for the first UE (UE-1) or the first part of the UE. The decision of the second UE (UE-2) or the second part of the UE can be based on rules / policies and / or requests from the dual-booting layer and / or requests from the network. This can be as previously described.
[0257] As referenced at 11, the second UE (UE-2) or the second part of the UE sends a PDU session establishment request to the AMF. This may include an indication that a dual-booted PDU session has been requested. This indication may be in the form of a flag. The request may include the identity of the linked dual-booted PDU session (PDU1). This may be done via UL NAS transmission.
[0258] As referenced at 12, the AMF selects the same SMF as the linked dual-boot PDU session (PDU1). This can be based on the linked dual-boot PDU session ID.
[0259] As referenced at 13, the AMF sends a PDU session establishment request to the SMF. This includes an indication that a dual-booting PDU session has been requested. The request may include the identity of the linked dual-booting PDU session (PDU1). This request may be provided in the PDU session update SM context request.
[0260] As referenced at 14, the SMF and UPF assign the same IP address to the linked dual-boot PDU session for the second UE (UE2) or the second part of the UE as to the linked dual-boot PDU session for the first UE (UE1). The SMF uses the identity of the linked dual-boot PDU session provided by the AMF to indicate which existing IP address will be used for the dual-boot PDU session for the second UE (UE2) or the second part of the UE.
[0261] The linked dual-boot PDU session ID is also mapped to the PDU session ID used for the dual-boot PDU session of the second UE (UE2) or the second part of the UE. This mapping can be performed by the SMF. This mapping can be provided when the SMF initiates a request for PDU resource establishment for the dual-boot PDU session for the second UE (UE2) or the second part of the UE. The RAN node can use this mapping to select the same or different gNBs (e.g., primary gNB and secondary gNB) for the two PDU sessions. This helps ensure that different gNBs can be selected for the two PDU sessions for redundancy and reliability. This mapping can be provided by the SMF in the N2 SM container on NGAP (Next Generation Application Protocol).
[0262] As cited at 15, the SMF obtains policies / rules related to dual-boot devices from the PCF.
[0263] As referenced at 16, the SMF will provide the dual-boot device-related policies / rules obtained from the PCF to the UPF serving the PDU sessions of both the first UE (UE-1) and the second UE (UE-2) or both parts of the UE.
[0264] As referenced at 17, the SMF provides the AMF with the dual-booting rules and assigned IP address for the second UE (UE-2). This can be provided in the PDU session establishment accept message. This can be Common_N1N2MsgTransfer.
[0265] As referenced at 18, the AMF provides the second UE (UE-2) or the second part of the UE with the dual boot rules and the assigned IP address of the second UE (UE-2) or the second part of the UE.
[0266] As referenced at 19, the AMF establishes user plane resources (e.g., access network resources) for a dual-booted PDU session (PDU3) for the second UE (UE2) or a second part of the UE. The user plane resources establish a dual-booted PDU session (PDU3) for the second UE (UE2) on the second access network (3GPP Access 2).
[0267] As referenced at 20, the second UE (UE-2) or the second part of the UE considers the establishment of the dual-booting PDU session to be successful upon receiving the dual-booting rule / policy. The dual-booting PDU session pair between the first UE (UE-1) and the second UE (UE-2) or both parts of the UE is successfully established. Therefore, the dual-booting device is configured with dual-booting.
[0268] refer to Figure 6a and Figure 6b This illustrates a second example of the process of some example embodiments.
[0269] In this example, the dual-boot device is able to downgrade a dual-boot PDU session to a single-access PDU session.
[0270] In this example, there is a first access network (3GPP Access 1) and a second access network (3GPP Access 2).
[0271] As referenced at 0a, the first UE (UE-1) or the first part of the UE is registered to the network via the first access network (3GPP Access 1). The first UE (UE-1) or the first part of the UE has established a dual-booted PDU session (PDU1) on the first access network (3GPP Access 1).
[0272] As referenced at 0b, the second UE (UE-2) or the second part of the UE is registered to the network via the second access network (3GPP Access 2). The second UE (UE-2) or the second part of the UE has established a dual-booted PDU session (PDU2) on the second access network (3GPP Access 2).
[0273] As referenced at 1a, the dual-booting device decides to exit dual-booting mode. In this example, the dual-booting device determines that a single-access PDU session is required and retains only the PDU session (PDU2) associated with the second UE (UE-2) or the second part of the UE. The exit decision can be based on a trigger from the dual-booting layer, a trigger from the network, and / or the first UE (UE-1) or the first part of the UE as previously described. For example, the first UE (UE-1) or the first part of the UE, or the second UE (UE-2) or the second part of the UE, can determine that dual-booting is no longer needed based on an evaluation of URSP rules / policies.
[0274] As referenced at 1b, the dual-booting device determines that a PDU session (PDU1) associated with the first UE (UE-1) or the first part of the UE is to be removed. For example, the dual-booting layer may determine that a PDU session (PDU1) associated with the first UE (UE-1) or the first part of the UE is to be removed.
[0275] As referenced at point 2, the first UE (UE-1) or the first part of the UE triggers a PDU session release procedure for the PDU session (PDU1) associated with the first UE (UE-1) or the first part of the UE. The PDU session (PDU1) associated with the first UE (UE-1) or the first part of the UE is released.
[0276] The first UE (UE-1) or the first part of the UE can provide an indication of the reason for releasing the PDU session. This indication can indicate that dual booting is no longer provided. For example, the first UE (UE-1) or the first part of the UE can include an indication of the reason for release during the PDU session release process. The reason for release could be exiting / ending dual booting mode and / or downgrading the dual booting PDU session to a single access PDU session.
[0277] As referenced at point 3, the SMF determines that the PDU session (PDU1) associated with the first UE (UE-1) or the first part of the UE is released, and that there is a link between the PDU session (PDU1) associated with the first UE (UE-1) or the first part of the UE and the PDU session (PDU2) associated with the second UE (UE-2) or the second part of the UE.
[0278] The release reason provided by the first UE (UE-1) or the first part of the UE can help the SMF. The SMF knows the reason for requesting the release of the PDU, and this can be used to trigger changes regarding the second UE (UE-2) or the second part of the UE.
[0279] As referenced at point 4, the SMF triggers a PDU session modification process for the dual-booting PDU session (PDU2) associated with the second UE (UE-2) or the second part of the UE. This will trigger an update or removal of the dual-booting rules at the UPF and at UE-2 or the second part of the UE. The dual-booting PDU session (PDU2) associated with the second UE (UE-2) or the second part of the UE will be modified to a single-access PDU session.
[0280] As referenced in point 5, PCF updates or removes dual-boot rules. For example, dual-boot support can be removed from a rule. SMF allows dual-boot rules to be updated or removed from UPF.
[0281] As referenced at point 6, the SMF provides the AMF with a request or command that policies / rules related to the dual-boot device be removed or updated. This can be provided in the PDU session modification command. This could be common_N1N2MsgTransfer.
[0282] As referenced at point 7, the AMF provides a request or command to the second UE (UE-2) or the second part of the UE to request that dual-boot device-related policies / rules be removed or updated. This can be provided in the PDU session modification command. This can be done via DL NAS transmission.
[0283] As referenced at point 8, the second UE (UE-2) or the second part of the UE considers the migration from a dual-booting PDU session to a single-access PDU session to be successful. This can be based on receiving a modified dual-booting rule / policy or the removal of a dual-booting rule / policy.
[0284] As referenced at point 9, the second UE (UE-2) or the second part of the UE sends a message to the AMF indicating that the PDU session modification is complete. This can be done via UL NAS transmission.
[0285] The section of the procedure referenced at points 3 to 8 describes an example of a network-initiated PDU session modification procedure for a dual-boot PDU session (PDU2) associated with a second UE or a second part of a UE.
[0286] In another example, the dual-booting device may decide to release or modify the PDU session (PDU2) associated with the second UE (UE2) or the second part of the UE to a single-access PDU session. In this example embodiment, the second UE (UE-2) or the second part of the UE will not need to wait for the network to trigger the modification of the PDU session (PDU2) associated with the second UE (UE-2) or the second part of the UE. The parts of the process referenced at points 3 to 8 may be omitted. For example, in a manner similar to the part of process 1b, the dual-booting device determines that the PDU session (PDU2) associated with the second UE (UE-2) or the second part of the UE will be updated to a single-access PDU session. In a manner similar to the part referenced at point 2 in the process, the second UE (UE-2) or the second part of the UE triggers a PDU session modification procedure for the PDU session (PDU2) associated with the second UE (UE-2). The PDU session modification procedure provides an indication that the PDU session (PDU2) associated with the second UE (UE-2) or the second part of the UE will be updated to a single-access PDU session.
[0287] In another example, both the release of the first PDU session (PDU1) and the modification of the second PDU session (PDU2) can be triggered from the network side. In this example, the network can update or remove dual-boot rules / policies and update the dual-boot device.
[0288] Some example implementations may allow existing single-access PDU sessions to be upgraded to dual-booted PDU sessions. This can be more energy-efficient for one or more of the dual-booted device, UE, or UE and / or network. This can provide better use of network resources.
[0289] Some example implementations may allow an existing dual-boot PDU session to be downgraded to a single-access PDU session. This can be more energy-efficient for one or more of the dual-boot device, the dual-boot device's UE, or the UE and / or the network. This can provide better use of network resources.
[0290] Some example implementations can ensure that the same IP address is used for both dual-boot PDU sessions.
[0291] Figure 4 An example of device 201 is illustrated.
[0292] Device 201 may include or implement Figure 1 One or more network functions are shown. Device 201 may have at least one processor and at least one memory storing... Figure 1 Instructions for one or more network functions, which, when executed by at least one of the at least one processor, cause the operation or action of one or more network functions to be performed.
[0293] Alternatively, device 201 may include or implement Figure 2 or Figure 3 At least a portion of a dual-boot device. Device 201 may have at least one processor and at least one memory storing instructions that, when executed by at least one of the at least one processor, cause at least a portion of the operation or action of the dual-boot device to be performed.
[0294] In this example, device 201 may include at least one random access memory (RAM) 211a and / or at least one read-only memory (ROM) 211b. Device 201 may include at least one processor 212, 213 and / or a network interface 214. At least one processor 212, 213 may be coupled to at least one memory, which in this example is RAM 211a and ROM 211b. At least one processor 212, 213 may be configured to execute appropriate software code 215.
[0295] For example, software code 215 may include software code for at least a portion of one or more network functions or dual-boot devices. The software code may include software code that allows the device to perform one or more operations of one or more aspects of this disclosure.
[0296] refer to Figure 7It illustrates methods in some example embodiments.
[0297] This method can be performed by a device.
[0298] This device can be installed in a dual-guide device.
[0299] The device may include a first user device, or a dual-boot device, associated with a first subscription.
[0300] The device may be a dual-boot device and may also include a second user device associated with a second subscription.
[0301] The device may include a dual-guide device.
[0302] The device may include a user device that is either a dual-boot device or a first subscription and a second subscription associated with the user device.
[0303] The device may include suitable components, such as a circuit system for providing the method.
[0304] Alternatively or additionally, the apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to provide at least the following methods.
[0305] Alternatively or otherwise, the device can be as follows Figure 2 , Figure 3 or Figure 4 As shown.
[0306] This method can be provided by computer program code or computer executable instructions.
[0307] The method may include, as referenced at A1, sending a request to the network to modify a first data session supporting single access to a session supporting dual bootstrapping, the first data session being associated with a first subscription of the dual bootstrapping device.
[0308] The method may include, as referenced at A2, receiving from the network a response indicating that a first data session supporting single access has been modified to support a dual-boot session.
[0309] It should be understood that Figure 7 The methods outlined herein can be modified to include any previously described features.
[0310] refer to Figure 8 It illustrates methods in some example embodiments.
[0311] This method can be performed by a device.
[0312] This device can be installed in a dual-guide device.
[0313] The device may include a first user device, or a dual-boot device, associated with a first subscription.
[0314] The device may be a dual-boot device and may also include a second user device associated with a second subscription.
[0315] The device may include a dual-guide device.
[0316] The device may include a user device that is either a dual-boot device or a first subscription and a second subscription associated with the user device.
[0317] The device may include suitable components, such as a circuit system for providing the method.
[0318] Alternatively or additionally, the apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to provide at least the following methods.
[0319] Alternatively or otherwise, the device can be as follows Figure 2 , Figure 3 or Figure 4 As shown.
[0320] This method can be provided by computer program code or computer executable instructions.
[0321] This method may include, as referenced at B1, determining that a first data session supporting dual boot is no longer needed to support dual boot, the first data session being associated with a first subscription of the dual boot device.
[0322] This method may include, as referenced at B2, sending a request to the network to update the network that the first data session is no longer needed to support dual bootstrapping.
[0323] It should be understood that Figure 8 The methods outlined herein can be modified to include any previously described features.
[0324] refer to Figure 9 It illustrates methods in some example embodiments.
[0325] This method can be performed by a device.
[0326] This device can be installed in a dual-guide device.
[0327] The device may include a first user device, or a dual-boot device, associated with a first subscription.
[0328] The device may be a dual-boot device and may also include a second user device associated with a second subscription.
[0329] The device may include a dual-guide device.
[0330] The device may include a user device that is either a dual-boot device or a first subscription and a second subscription associated with the user device.
[0331] The device may include suitable components, such as a circuit system for providing the method.
[0332] Alternatively or additionally, the apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to provide at least the following methods.
[0333] Alternatively or otherwise, the device can be as follows Figure 2 , Figure 3 or Figure 4 As shown.
[0334] This method can be provided by computer program code or computer executable instructions.
[0335] The method may include, as referenced at C1, receiving a session modification command from the network, the session modification command indicating that a first data session supporting dual boot will be modified to a session supporting single access.
[0336] This method may include, as referenced at C2, sending a response to the network acknowledging that the first data session has been modified to support single access.
[0337] It should be understood that Figure 9 The methods outlined herein can be modified to include any previously described features.
[0338] refer to Figure 10 It illustrates methods in some example embodiments.
[0339] This method can be performed by a device.
[0340] The device can be a dual-guide device.
[0341] A dual-boot device may include a first user device, which is associated with a first subscription.
[0342] A dual-boot device may include a second user device associated with a second subscription.
[0343] A dual-boot device may include a user device, with a first subscription and a second subscription associated with the user device.
[0344] The device may include suitable components, such as a circuit system for providing the method.
[0345] Alternatively or additionally, the apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to provide at least the following methods.
[0346] Alternatively or otherwise, the device can be as follows Figure 2 , Figure 3 or Figure 4 As shown.
[0347] This method can be provided by computer program code or computer executable instructions.
[0348] This method may include, as referenced at D1, sending a request to the network to modify a first data session supporting single access to a session supporting dual bootstrapping, the first data session being associated with a first subscription of the dual bootstrapping device.
[0349] This method may include, as referenced at D2, receiving from the network a response indicating that a first data session supporting single access has been modified to support a dual-boot session.
[0350] This method may include, as referenced at D3, sending a request to the network to establish a second data session that supports dual boots.
[0351] It should be understood that Figure 10 The methods outlined herein can be modified to include any previously described features.
[0352] refer to Figure 11 It illustrates methods in some example embodiments.
[0353] This method can be performed by a device.
[0354] The device can be a dual-guide device.
[0355] A dual-boot device may include a first user device, which is associated with a first subscription.
[0356] A dual-boot device may include a second user device associated with a second subscription.
[0357] A dual-boot device may include a user device, with a first subscription and a second subscription associated with the user device.
[0358] The device may include suitable components, such as a circuit system for providing the method.
[0359] Alternatively or additionally, the apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to provide at least the following methods.
[0360] Alternatively or otherwise, the device can be as follows Figure 2 , Figure 3 or Figure 4 As shown.
[0361] This method can be provided by computer program code or computer executable instructions.
[0362] This method may include, as referenced at E1, removing the first dual-boot session when dual-booting is no longer needed, the first data session being associated with the first subscription of the dual-boot device.
[0363] This method may include, as referenced at E2, sending a modification request to the network for modifying a second data session that supports dual booting to a session that supports single access, the second data session being associated with a second subscription of the dual booting device.
[0364] It should be understood that Figure 11 The methods outlined herein can be modified to include any previously described features.
[0365] refer to Figure 12 It illustrates methods in some example embodiments.
[0366] This method can be performed by a device.
[0367] The device can be a dual-guide device.
[0368] A dual-boot device may include a first user device, which is associated with a first subscription.
[0369] A dual-boot device may include a second user device associated with a second subscription.
[0370] A dual-boot device may include a user device, with a first subscription and a second subscription associated with the user device.
[0371] The device may include suitable components, such as a circuit system for providing the method.
[0372] Alternatively or additionally, the apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to provide at least the following methods.
[0373] Alternatively or otherwise, the device can be as follows Figure 2 , Figure 3 or Figure 4 As shown.
[0374] This method can be provided by computer program code or computer executable instructions.
[0375] This method may include, as referenced at F1, removing the first dual-boot session when dual-booting is no longer needed, the first data session being associated with the first subscription of the dual-booting device.
[0376] The method may include, as referenced at F2, receiving from the network information indicating that a second data session supporting dual boot has been modified to support a single access session, the second data session being associated with a second subscription of the dual boot device.
[0377] It should be understood that Figure 12 The methods outlined herein can be modified to include any previously described features.
[0378] refer to Figure 13 It illustrates methods in some example embodiments.
[0379] This method can be performed by a device.
[0380] This device can be installed in a dual-guide device.
[0381] The device may include a first user device, or a dual-boot device, associated with a first subscription.
[0382] The device may be a dual-boot device and may also include a second user device associated with a second subscription.
[0383] The device may include a dual-guide device.
[0384] The device may include a user device that is either a dual-boot device or a first subscription and a second subscription associated with the user device.
[0385] The device may include suitable components, such as a circuit system for providing the method.
[0386] Alternatively or additionally, the apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to provide at least the following methods.
[0387] Alternatively or otherwise, the device can be as follows Figure 2 , Figure 3 or Figure 4 As shown.
[0388] This method can be provided by computer program code or computer executable instructions.
[0389] The method may include, as referenced at G1, receiving information identifying the address of a first data session that supports dual bootstrapping, the first data session being associated with a first subscription.
[0390] The method may include, as referenced at G2, sending a request to the network to establish a second data session that supports dual booting, the session establishment request including information identifying the address of a first data session that supports dual booting, wherein the first data session and the second data session have the same address.
[0391] It should be understood that Figure 13 The methods outlined herein can be modified to include any previously described features.
[0392] refer to Figure 14 It illustrates methods in some example embodiments.
[0393] This method can be performed by a device.
[0394] The device may include or implement session management functions.
[0395] The device may include suitable components, such as a circuit system for providing the method.
[0396] Alternatively or additionally, the apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to provide at least the following methods.
[0397] Alternatively or otherwise, the device can be as follows Figure 4 As shown.
[0398] This method can be provided by computer program code or computer executable instructions.
[0399] The method may include, as referenced at H1, receiving a request for modification of a first data session supporting single access to a data session supporting dual bootstrapping, the first data session being associated with a first subscription of the dual bootstrapping device.
[0400] This method may include, as referenced at H2, providing the dual-boot device with one or more rules or policies related to dual-booting.
[0401] It should be understood that Figure 14 The methods outlined herein can be modified to include any previously described features.
[0402] refer to Figure 15 It illustrates methods in some example embodiments.
[0403] This method can be performed by a device.
[0404] The device may include or implement session management functions.
[0405] The device may include suitable components, such as a circuit system for providing the method.
[0406] Alternatively or additionally, the apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to provide at least the following methods.
[0407] Alternatively or otherwise, the device can be as follows Figure 4 As shown.
[0408] This method can be provided by computer program code or computer executable instructions.
[0409] The method may include, as referenced at J1, determining that a first data session supporting dual booting is modified to a single access session, the first data session being associated with a first subscription of the dual booting device.
[0410] This method may include, as referenced at J2, a request or command that provides one or more dual-boot device-related policies to be removed or updated.
[0411] It should be understood that Figure 14 The methods outlined herein can be modified to include any previously described features.
[0412] Computer program code can be downloaded and stored in one or more memories of the apparatus described herein.
[0413] Therefore, although certain embodiments have been described above by way of example and with reference to certain example architectures, technologies and standards of communication systems operated by mobile network operators, other example embodiments can be applied to any other suitable form of communication system besides those shown and described herein. For example, some example embodiments have been described for 5G communication systems (5GS). It should be understood that other embodiments may be provided in any other suitable communication system.
[0414] As used herein, “at least one of the following: ” and “at least one of ” 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, or at least any two or more of these elements, or at least all of these elements.
[0415] Generally, various embodiments can be implemented in hardware or special-purpose circuitry systems, software, logic, or any combination thereof. Some aspects of this disclosure can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, but this disclosure is not limited thereto. While various aspects of this disclosure may be illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it is well understood that, by way of non-limiting example, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, special-purpose circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.
[0416] As used in this application, the term "circuit system" may refer to one or more or all of the following: (a) Hardware circuit implementation only (such as implementation in analog and / or digital circuit systems only) and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) Any part of a hardware processor (including (multiple) digital signal processors), software, and (multiple) memories that work together to enable a device such as a mobile phone or server to perform various functions, and (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or portions thereof, which require software (e.g., firmware) to function, but may be absent when not needed.
[0417] This definition of circuit system applies to all uses of the term in this application, including in any claim. As another example, as used in this application, the term circuit system also covers only hardware circuitry or a processor (or processors) or a portion of hardware circuitry or a processor and its accompanying software and / or firmware. For example, if applicable to a particular claim element, the term circuit system also covers integrated circuits, such as baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.
[0418] Embodiments of this disclosure can be implemented by computer software executable by a mobile device's data processor, such as in a processor entity, or by hardware, or by a combination of software and hardware. Computer software or programs (also referred to as program products, including software routines, applets, and / or macros) can be stored in any device-readable data storage medium, and they include program instructions for performing specific tasks. A computer program product may include one or more computer-executable components that, when the program runs, are configured to execute the embodiment. The one or more computer-executable components may be at least one piece of software code or a portion thereof.
[0419] Furthermore, it should be noted in this regard that any block in the logic flow shown in the figure can represent a program step, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. Software can be stored on physical media, such as memory chips or blocks of memory implemented within a processor, magnetic media such as hard disks or floppy disks, and optical media (such as DVDs and their data variants, CDs). Physical media are non-transitory media.
[0420] The term “non-transient” as used in this article 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).
[0421] The memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor can be of any type suitable for the local technical environment and, by way of non-limiting example, can include one or more of the following: general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), FPGAs, gate-level circuits, and processors based on multi-core processor architectures.
[0422] The embodiments of this disclosure can be practiced in various components, such as integrated circuit modules. The design of integrated circuits is largely a highly automated process. Complex and powerful software tools can be used to translate logic-level designs into semiconductor circuit designs for etching and formation on semiconductor substrates.
[0423] The foregoing description has provided a complete and informative description of exemplary embodiments of the present disclosure by way of non-limiting example. However, various modifications and adaptations will be apparent to those skilled in the art when read in conjunction with the accompanying drawings and appended claims, given the foregoing description. Indeed, there are additional embodiments that combine one or more embodiments with any other embodiments discussed above. The scope of protection sought by some embodiments of the present disclosure is set forth in the claims. Embodiments and features described herein that are not within the scope of the claims, if any, should be interpreted as examples that aid in understanding the various embodiments of the present disclosure. It should be noted that different claims with different scopes may be pursued in related applications such as divisional applications or continuation applications.
Claims
1. A dual-guide device, comprising: A component for sending a request to the network for a modification from a first data session supporting single access to a data session supporting dual bootstrapping, the first data session being associated with a first subscription of the dual bootstrapping device; A component for receiving from the network a response indicating that the first data session supporting single access has been modified to a data session supporting dual bootstrapping; as well as A component for sending a request to the network to establish a second data session that supports dual boots.
2. The dual-booting device of claim 1, wherein the session establishment request includes information identifying the first data session supporting dual booting, and the second data session is associated with a second subscription of the dual-booting device.
3. The dual-boot device according to claim 1 or 2, wherein the first data session and the second data session include packet data unit sessions.
4. The dual-booting device according to any one of claims 1 to 3, wherein the component for sending the request for the modification of the first data session to the network is configured to send the request via a first access network, and the component for sending the session establishment request is configured to send the request via a second access network.
5. The dual-booting device according to any one of claims 1 to 4, wherein the component for sending the request to the network is further configured to send a request to the network for establishing a first data session supporting single access, the session establishment request including an indication that modifying the first data session supporting single access to a data session supporting dual booting is permitted.
6. The dual-booting device according to any one of the preceding claims, comprising components for determining, in response to one or more of the following: information received from the network; one or more rules or policies related to dual booting; and information related to the dual-booting device.
7. The dual-booting device of claim 6, wherein the one or more rules or policies associated with dual-booting include one or more user equipment routing policies.
8. The dual-guiding device according to claim 6 or 7, wherein the information associated with the dual-guiding device includes one or more energy-related conditions of the dual-guiding device.
9. The dual-booting device according to any one of claims 1 to 8, wherein the response from the network includes one or more rules and / or policies related to dual-booting, the response indicating that the first data session supporting single access is modified to a data session supporting dual-booting.
10. The dual-booting device according to any one of claims 1 to 9, comprising a component for receiving from the network a response indicating that a second data session supporting dual-booting has been established, the response including one or more rules and / or policies related to dual-booting.
11. The dual-booting device according to any one of claims 1 to 10, comprising a first user equipment associated with the first subscription.
12. The dual-boot device of claim 11, further comprising a second user device associated with the second subscription.
13. The dual-booting device according to any one of claims 1 to 10, comprising a user equipment, wherein the first subscription and the second subscription are associated with the user equipment.
14. A dual-guidance device, comprising: A component for removing a first dual-boot session when dual-booting is no longer needed, the first data session being associated with a first subscription of the dual-booting device; as well as A component for sending a modification request to the network for modifying a second data session that supports dual boots to a data session that supports single access, the second data session being associated with a second subscription of the dual boot device.
15. The dual-boot device of claim 14, wherein the session modification request includes an indication of the reason for the modification.
16. A dual-guidance device, comprising: A component for removing a first dual-boot session when dual-booting is no longer needed, the first data session being associated with a first subscription of the dual-booting device; as well as A component for receiving information from the network indicating that a second data session supporting dual boot has been modified to support a single-access data session, the second data session being associated with a second subscription of the dual boot device.
17. The dual-booting device according to any one of claims 14 to 16, comprising components for determining that dual-booting is no longer needed in response to one or more of the following: information received from a network; one or more rules or policies related to dual-booting; and information related to the dual-booting device.
18. The dual-booting device of claim 17, wherein the one or more rules or policies associated with dual-booting include one or more user equipment routing policies.
19. The dual-guide device of claim 17 or 18, wherein the information associated with the dual-guide device includes one or more energy-related conditions of the device.
20. The dual-booting device according to any one of claims 14 to 19, wherein the component for removing the first data session is configured to send a session release request to the network for the release of the first data session, the session release request including an indication of the reason for the release of the first data session.
21. The dual-booting device according to any one of claims 13 to 18, wherein the component for removing the first data session receives a session release request from the network for the release of the first data session, the session release request including an indication of the reason for the release of the first data session.
22. A method performed by a dual-boot device, the method comprising: Send a request to the network to modify a first data session that supports single access to a data session that supports dual bootstrapping, the first data session being associated with a first subscription of the dual bootstrapping device; The network receives a response indicating that the first data session supporting single access has been modified to support a dual-boot data session; and Send a request to the network to establish a second data session that supports dual bootstrapping.
23. A method performed by a dual-boot device, the method comprising: Remove the first dual boot session when dual boot is no longer needed; the first data session is associated with the first subscription of the dual boot device. as well as A modification request is sent to the network to modify a second data session that supports dual bootstrapping to a data session that supports single access, the second data session being associated with a second subscription of the dual bootstrapping device.
24. A method performed by a dual-boot device, the method comprising: Remove the first dual-boot session when dual-booting is no longer needed; the first data session is associated with the first subscription of the dual-booting device. as well as The network receives information indicating that a second data session supporting dual boot has been modified to support a single access data session, the second data session being associated with a second subscription of the dual boot device.
25. A computer program includes instructions, wherein when the program is run on a dual-boot device, the dual-boot device is caused to perform the method according to any one of claims 22 to 24.
26. A computer-readable medium comprising instructions that, when executed by at least one processor of a dual-boot device, cause the dual-boot device to perform the method according to any one of claims 22 to 24.
