Apparatus, methods and computer programs
By transmitting dual-booting information between user plane functions and policy control functions, a consistent packet forwarding control protocol session is established, which solves the problem of low efficiency in communication session management between access networks in dual-booting devices, and achieves more efficient traffic management and reduced service interruptions.
Patent Information
- Application Number
- CN202580028526.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-02-23
- Filing Date
- 2025-02-19
- Publication Date
- 2026-11-17
AI Technical Summary
Existing communication systems struggle to effectively manage and coordinate communication sessions between two or more access networks in dual-boot devices, resulting in inefficient traffic booting, switching, and offloading.
By sending and receiving dual bootstrap information between user plane functions and policy control functions, packet forwarding control protocol sessions are established or modified to ensure address consistency between the two packet data unit sessions, and corresponding packet processing rules are applied to achieve traffic bootstrap, switching and diversion.
It improves the efficiency and reliability of traffic management in dual-boot devices, reduces service interruptions, and ensures smooth switching and traffic offloading between different access networks.
Smart Images

Figure CN123126019A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to methods, apparatus, and computer programs, and specifically, but not exclusively, to methods, apparatus, and computer programs related to dual booting. Background Technology
[0002] A communication system can be viewed as a facility that enables communication sessions between two or more entities, such as communication devices, base stations, and / or other nodes, by providing carriers between various entities involved in the communication path.
[0003] Communication systems and associated entities typically operate according to a given standard or specification that defines what the associated 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. Examples of standards include the so-called 5G standard. Summary of the Invention
[0004] 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 the scope of this disclosure. Other features, aspects, and elements will become apparent to those skilled in the art in light of this disclosure.
[0005] According to a first aspect, a method is provided, comprising: sending a request to a user plane function to establish or modify a second Packet Forwarding Control Protocol (PTP) session, the request including second dual-booting information, the dual-booting information including: providing dual-booting information for a link to a first PTP session for a first Packet Data Unit (PaDN) session, the second PTP session being used for the second PTP session, the first PTP session and the second PTP session supporting dual-booting; and in response to the request to establish or modify the second PTP session, receiving from the user plane function an address for the second PTP session that is the same as the address used for the first PTP session.
[0006] The method may include: sending a request to a user plane function to establish or modify a first packet forwarding control protocol session before sending a request to establish or modify a second packet forwarding control protocol session, the request to establish or modify the first packet forwarding control protocol session including first dual boot information; and receiving an address for a first packet data unit session from the user plane function in response to the request to establish or modify the first packet forwarding control protocol session.
[0007] The method may include: sending a request to a policy control function for a session management policy association for a first packet data unit session, the request for a session management policy association for a first packet data unit session including dual-bootstrapping related information; and receiving policy information from the policy control function.
[0008] The dual-booting related information provided in the request for the session management policy association for the first Packet Data Unit (BDN) session may include at least one of the following indicators: the session management policy association is for a dual-booting BDN session; the dual-booting bundle identifier of the associated BDN session supporting dual-booting; the dual-booting identifier for the first session management policy association session; the common dual-booting identifier for the first session management policy association session and the second session management policy association associated with the second BDN session; the dual-booting identifier of the link to the second session management policy association session; or the session management policy association session identifier of the first session management policy association session.
[0009] The method may include: sending a request to a policy control function for a session management policy association for a second packet data unit session, the request for a session management policy association for a second packet data unit session including dual-bootstrapping related information; and receiving policy information from the policy control function.
[0010] A request for a session management policy association for a grouped data unit session can correspond to one of the following: a request to establish a session management policy association, a request to modify a session management policy association, or a request to notify of an event related to a session management policy association.
[0011] The dual-booting related information provided in the request for the session management policy association for the second Packet Data Unit (BDN) session may include at least one of the following: the following indicators: the session management policy association is for a dual-booting BDN session; the dual-booting bundle identifier of the associated BDN session supporting dual-booting; the dual-booting identifier for the second session management policy association session; the common dual-booting identifier for the first session management policy association session and the second session management policy association; the dual-booting identifier of the link of the first session management policy association session; or the session management policy association session identifier of the second session management policy association session.
[0012] The policy may include at least one of the following: one or more rules applicable to the first packet data unit session and the second packet data unit session; one or more rules applicable to the first packet data unit session; or one or more rules applicable to the second packet data unit session.
[0013] The method may include: providing one or more packet processing rules to the user plane function, wherein the packet processing rules may include at least one of the following: one or more rules applicable to a first packet forwarding control protocol session and a second packet forwarding control protocol session; one or more rules applicable to the first packet forwarding control protocol session; or one or more rules applicable to the second packet forwarding control protocol session.
[0014] This method can be performed by a device.
[0015] The apparatus may include components for implementing the method.
[0016] 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 perform at least one of the methods discussed in relation to the first aspect.
[0017] This device can perform session management functions.
[0018] According to a second aspect, a method is provided, the method comprising: receiving from a session management function a request to establish or modify a second Packet Forwarding Control Protocol (PTP) session, the request including second dual-booting information, the dual-booting information including: dual-booting information providing a link to a first PTP session for a first Packet Data Unit (PaDN) session, the second PTP session being used for the second PTP session, the first PTP session and the second PTP session being associated PTP sessions supporting dual-booting; storing the association between the first PTP session and the second PTP session; and, in response to the request, sending to the session management function an address for the second PTP session that is the same as the address used for the first PTP session.
[0019] The method may include, before receiving a request to establish or modify a second Packet Forwarding Control Protocol (BTP) session: receiving a request to establish or modify a first Packet Forwarding Control Protocol (BTP) session from the same or different session management functions, the request to establish or modify the first BTP session including first dual boot information; and in response to the request to establish or modify the first BTP session, sending an address for the first Packet Data Unit (BDN) session to the same or different session management functions.
[0020] This method can be performed by a device.
[0021] The apparatus may include components for implementing the method.
[0022] 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 perform at least one of the methods discussed in connection with the second aspect.
[0023] This device can enable user-facing functionality.
[0024] One or more of the following features may be used in combination with the first aspect and / or the second aspect.
[0025] The first dual-booting information may include at least one of the following: indicating that the first Packet Forwarding Control Protocol (PTCP) session is a PTCP session for dual-booting Packet Data Unit (PDU) sessions; a dual-booting bundle identifier for an associated PUDP session supporting dual-booting; a dual-booting identifier for the first PTCP session; a common dual-booting identifier for the first PTCP session and the second PTCP session; a linked dual-booting identifier for the second PTCP session; or a PTCP identifier for the first PTCP session.
[0026] The second dual-booting information may include at least one of the following: an indication that the second Packet Forwarding Control Protocol (PTCP) session is a PTCP session for dual-booting Packet Data Unit (PDU) sessions; a dual-booting bundle identifier for an associated PPD session supporting dual-booting; a dual-booting identifier for the second PTCP session; a common dual-booting identifier for both the first and second PTCP sessions; a dual-booting identifier for a link in the first PTCP session; or a PTCP identifier for the second PTCP session.
[0027] The corresponding dual-boot identifier for the corresponding session can be based on the corresponding subscriber identifier of the dual-boot device and the identifier associated with the corresponding packet data unit session.
[0028] The corresponding dual-boot identifier can be based on the corresponding subscriber identifier of the dual-boot device and the identifier associated with the corresponding other packet data unit session.
[0029] A request to establish or modify a second packet forwarding control protocol session may include an address that is requested to be used by user plane functions for a second packet data unit session.
[0030] According to a third aspect, a method is provided, comprising: sending a request to a user plane function to establish or modify a first Packet Forwarding Control Protocol (PTCP) session, the request including: specifying an address to be used for the first Packet Data Unit (BDS) session, the PTCP session being associated with the first BDS session; receiving a response to the request from the user plane function; sending a request to the user plane function to establish or modify a second PTCP session, the request including: specifying an address to be used for the second BDS session, the same address used for the second BDS session as the address used for the first BDS session, the first BDS session and the second BDS session being associated BDS sessions supporting dual bootstrapping; and receiving a response to the request from the user plane function, the response acknowledging that the same address is being used for the second BDS session.
[0031] The method may include: providing one or more packet processing rules to a user plane function, wherein the packet processing rules include at least one of the following: one or more rules applicable to a first packet forwarding control protocol session and a second packet forwarding control protocol session; one or more rules applicable to the first packet forwarding control protocol session; or one or more rules applicable to the second packet forwarding control protocol session.
[0032] This method can be performed by a device.
[0033] The apparatus may include components for implementing the method.
[0034] 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 perform at least one of the methods discussed in connection with the third aspect.
[0035] This device can perform session management functions.
[0036] According to a fourth aspect, a method is provided, comprising: receiving from a session management function a request to establish or modify a first Packet Forwarding Control Protocol (PTP) session, the request including: specifying an address to be used in the first Packet Data Unit (PDU) session, the PTP session being associated with the first PTP session; sending a response to the session management function to the request; receiving from the same or different session management functions a request to establish or modify a second PTP session, the request including: specifying an address to be used in the second PTP session, an address used in the second PTP session that is the same as the address used in the first PTP session, the first PTP session and the second PTP session being associated PTP sessions supporting dual bootstrapping; and sending a response to the same or different session management function to the request, the response accepting that the same address is being used in the second PTP session.
[0037] This method can be performed by a device.
[0038] The apparatus may include components for implementing the method.
[0039] 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 perform at least one of the methods discussed in connection with the fourth aspect.
[0040] This device can enable user-facing functionality.
[0041] One or more of the following features may be used in combination with the third and / or fourth aspects.
[0042] A request to establish or modify a second packet forwarding control protocol session may include the following indication: the second packet forwarding control protocol session is used for a dual-boot packet data unit session.
[0043] The same address can include: IP address, Internet Protocol (IP) address prefix, or Media Access Control (MAC) address.
[0044] The same address can include: the address associated with a dual-boot device that supports dual booting.
[0045] The method may include: providing one or more packet processing rules to a user plane function, wherein the one or more packet processing rules include at least one of the following: one or more rules applicable to a first packet forwarding control protocol session and a second packet forwarding control protocol session; one or more rules applicable to the first packet forwarding control protocol session; or one or more rules applicable to the second packet forwarding control protocol session.
[0046] According to a fifth aspect, a method is provided, comprising: receiving a packet associated with a first packet forwarding control protocol session; determining which packet detection rule among packet detection rules associated with the first packet forwarding control protocol session and a second packet forwarding control protocol session has the highest priority, wherein the first packet forwarding control protocol session and the second packet forwarding control protocol session are used to support associated packet data unit sessions with dual bootstrapping; and applying one or more instructions from the packet detection rule with the highest priority to the packet.
[0047] The group can be a downlink group.
[0048] The method may include: determining that a packet matches a first packet forwarding control protocol session, and finding a second packet forwarding control protocol session that supports dual bootstrapping with the first packet forwarding control protocol session.
[0049] Instructions associated with packet detection rules can define packet routing, splitting, and / or switching between the first and second sessions. DL packet data records may include dual-routines identifiers.
[0050] The instructions associated with the grouping detection rules can define the guiding functions that will be used.
[0051] The guidance function may include at least one of the following: access traffic guidance, switching, traffic splitting at lower layers, multipath transmission control protocol, or multipath QUIC.
[0052] Instructions associated with group detection rules can define the guidance mode.
[0053] The bootstrap mode may include at least one of the following: active / standby; minimum latency; load balancing; priority-based; or redundancy.
[0054] According to a sixth aspect, a method is provided, comprising: determining that a first session management function serving a first packet data unit session and a second packet data unit session is no longer able to support the first packet data unit session and the second packet data unit session, the first packet data unit session and the second packet data unit session being associated packet data unit sessions supporting dual bootstrapping; and moving the first packet data unit session and the second packet data unit session to a second session management function, the second session management function belonging to the same set of session management functions as the first session management function.
[0055] According to the seventh aspect, a method is provided, comprising: determining that a first session management function for a first packet data unit session that supports dual bootstrapping is no longer able to support the first packet data unit session; and moving the first packet data unit session to a second session management function that supports the second packet data unit session, wherein the first packet data unit session and the second packet data unit session support dual bootstrapping.
[0056] According to the eighth aspect, a method is provided, comprising: determining that a first session management function serving a first packet data unit session and a second packet data unit session is no longer able to support the first packet data unit session and the second packet data unit session, the first packet data unit session and the second packet data unit session supporting dual bootstrapping; and associating a session management policy for the first packet data unit session and the second packet data unit session with a second session management function, the second session management function belonging to the same set of session management functions as the first session management function.
[0057] According to the ninth aspect, a method is provided, comprising: determining that a first session management function for a first packet data unit session that supports dual bootstrapping is no longer able to support the first packet data unit session; and associating a session management policy for the first packet data unit session with a second session management function that supports the second packet data unit session, wherein the first packet data unit session and the second packet data unit session support dual bootstrapping.
[0058] According to a tenth aspect, a method is provided, comprising: providing a first dual-booting packet forwarding control protocol session for a first packet data unit session, the first dual-booting packet forwarding control protocol session being associated with a first subscriber identifier associated with a dual-booting device; providing a second dual-booting packet forwarding control protocol session for a second packet data unit session, the second dual-booting packet forwarding control protocol session being associated with a second subscriber identifier associated with a dual-booting device, the first packet data unit session and the second packet data unit session supporting dual-booting; and using one of the first identifier and the second identifier to intercept or trace dual-booting traffic, thereby intercepting or tracing dual-booting traffic of both the first packet data unit session and the second packet data unit session.
[0059] According to the eleventh aspect, a method is provided, comprising: providing a first session management policy for a first packet data unit (BDN) session, the first session management policy being associated with a first subscriber identifier associated with a dual-booting device; providing a second session management policy for a second BDN session, the second session management policy being associated with a second subscriber identifier associated with a dual-booting device, the first BDN session and the second BDN session supporting dual-booting; and using one of the first identifier and the second identifier to intercept or trace dual-booting traffic, thereby intercepting or tracing dual-booting traffic for both the first BDN session and the second BDN session.
[0060] According to the twelfth aspect, a method is provided, the method comprising: retrieving information about a first packet data unit session and a second packet data unit session based on a public address or a public dual-boot identifier, the first packet data unit session and the second packet data unit session together supporting dual booting and binding the information about the first packet data unit session and the second packet data unit session together to form a dual-boot binding.
[0061] For one or more of the fifth, sixth, seventh, and tenth aspects, the method may be performed by a device.
[0062] 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 perform at least one of the methods discussed in relation to the relevant aspect.
[0063] The apparatus may include components for implementing the method.
[0064] This device can enable user-facing functionality.
[0065] For one or more of aspects eight, nine, eleven, and twelfth, the method may be performed by an apparatus.
[0066] 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 perform at least one of the methods discussed in relation to the relevant aspect.
[0067] The apparatus may include components for implementing the method.
[0068] This device can implement strategy control functions.
[0069] According to one aspect, a computer-readable medium is provided, including program instructions stored thereon for performing at least one of the methods described above.
[0070] According to one aspect, a non-transitory computer-readable medium is provided, comprising program instructions stored thereon for performing at least one of the methods described above.
[0071] According to one aspect, a non-transitory tangible memory medium is provided, including program instructions stored thereon for performing at least one of the methods described above.
[0072] Many different aspects have been described above. It should be understood that additional aspects can be provided through any two or more combinations of the aspects mentioned above.
[0073] Various other aspects are also described in the following detailed description and in the appended claims. Attached Figure Description
[0074] Some exemplary embodiments of this disclosure will now be described with reference to the accompanying drawings, which are non-limiting and illustrative, in which:
[0075] Figure 1 This illustrates a schematic representation of a 5G system;
[0076] Figure 2 The first example of a dual-boot device and a 5GC UPF is illustrated schematically;
[0077] Figure 3 A second example of a dual-boot device and a 5GC UPF is schematically shown;
[0078] Figure 4 A schematic representation of the device is shown;
[0079] Figure 5a and Figure 5b The first process is illustrated schematically, in which the same address is used for two PFCP sessions;
[0080] Figure 6 The downlink DL packet processing flow is illustrated schematically.
[0081] Figure 7 The first method of some example embodiments is shown;
[0082] Figure 8 The second method is shown in some example embodiments;
[0083] Figure 9 A third method is shown in some example embodiments;
[0084] Figure 10 The fourth method is shown in some example embodiments;
[0085] Figure 11 The fifth method is shown in some example embodiments;
[0086] Figure 12 The sixth method is shown in some example embodiments;
[0087] Figure 13 The seventh method is shown in some example embodiments;
[0088] Figure 14 An eighth method is shown in some example embodiments;
[0089] Figure 15 The ninth method is shown in some example embodiments;
[0090] Figure 16 The tenth method of some example embodiments is shown;
[0091] Figure 17 An eleventh method is shown in some example embodiments; and
[0092] Figure 18 The twelfth method is shown in some example embodiments. Detailed Implementation
[0093] In the following, various exemplary embodiments of this disclosure refer to communication devices capable of communicating via a wireless communication system (e.g., a cellular system or a mobile communication system) that serves such communication devices. Figure 1 An example wireless communication system is shown in the figure.
[0094] Figure 1 A schematic representation of a communication network including a 5G system (5GS) is shown.
[0095] This communication may include a Public Land Mobile Network (PLMN). The PLMN may include: a radio access network comprising multiple access nodes (ANs), 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-boot device 200 / 300 are connected to the 5GC via two different ANs. Some example embodiments of the dual-boot device 200 / 300 will be described in more detail later.
[0096] The access network can be a 3GPP access network. For example, the access network can be a Radio Access Network (RAN) as defined in 3GPP standards, such as a 5G RAN. Other examples of access networks can be untrusted or wired non-3GPP access to the 3GPP core (N3IWF - Non-3GPP Interoperability Function, or W-AGF - Wired 5G Access Gateway Function). In another example, one RAN can correspond to a terrestrial (radio access) network, while another RAN can correspond to a non-terrestrial (radio access) network. In yet another example, these two (RANs) can be operated by different operators (e.g., different (multiple) PLMNs). In the latter case, the RAN can be controlled by different (multiple) AMFs.
[0097] A 5G RAN may include one or more base stations. A base station may be an evolved NodeB (eNB) or a gNodeB (gNB). A gNB may include distributed units connected to one or more centralized units.
[0098] Figure 1 The 5GC shown includes network functions (NF). Figure 1 The network functions shown include: Unified Data Repository (UDR), Network Open 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.
[0099] Some example implementations involve so-called "dual-boot devices".
[0100] A dual-booting device is a device that supports traffic bootstrapping, traffic offloading, and / or traffic switching of user data across two access networks. User data can be associated with a user equipment data session. The two access networks can be different access networks. The access networks can be two 3GPP access networks. For example, in some example embodiments, the two access networks can be two different 3GPP access networks. For example, the two different access networks can be provided by different RANs.
[0101] Traffic routing can direct traffic to one or both of two access networks. Traffic can be offloaded between the two access networks. In another example, traffic can be directed to only one of the access networks. In yet another example, traffic can be switched from one of the two access networks to the other of the two access networks.
[0102] 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, while 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 represent the identity of a subscriber in the network. The first subscriber identifier and the second subscriber identifier can include: SUPI (Subscription Persistent Identifier) or any other suitable subscriber identifier.
[0103] 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).
[0104] The first subscriber identifier and the second subscriber identifier can be linked to a single subscription profile.
[0105] When a dual-booting device provides dual booting, it has a first data session and a second data session. The first data session has a network associated with a first subscriber identifier and via a first access network, and the second data session has a network associated with a second subscriber identifier and via a second access network. Traffic (such as user data) can be sent to the network via the first and second data sessions. Traffic can be booted, switched, and / or offloaded between the first and second sessions.
[0106] For example, traffic can include data from applications on dual-boot devices.
[0107] The first and second sessions can be Packet Data Unit (PDU) sessions.
[0108] refer to Figure 2The figure illustrates a first example of a dual-boot device 200. In this example, the dual-boot 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, while the second UE (UE2) is associated with a second subscriber identifier SUPI-2. For example, the first UE (UE1) may have a first SIM (e.g., USIM) storing the first subscriber identifier SUPI-1, while the second UE (UE2) may have a second SIM (e.g., USIM) storing the second subscriber identifier SUPI-2.
[0109] 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 composed of, for example... Figure 4 The device shown is used to achieve this.
[0110] The first UE (UE1) has network access via the first access network 3GPP1, while the second UE (UE2) has network access via the second access network 3GPP2. The first access network and the second access network are different.
[0111] The dual bootstrapping layer manages the bootstrapping, switching, and / or offloading of traffic via a first UE and a second UE to one or both of the two access networks.
[0112] If needed, dual-boot devices can support simultaneous data transmission on two access networks.
[0113] Traffic managed by the dual bootstrap layer can include application traffic from application 202 or any other suitable traffic.
[0114] In some example embodiments, the dual-guide device may be housed, for example, within a single housing.
[0115] In other example 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, for example, communicate with an application and a first UE and a second UE. This communication can be wired and / or wireless.
[0116] refer to Figure 3 The figure illustrates a second example of a dual-booting device 300. The dual-booting device in this example 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, such as a USIM, storing the first subscriber identifier SUPI-1 and a second SIM, such as a USIM, storing the second subscriber identifier SUPI-2.
[0117] Similarly, as about Figure 2 The discussion focuses on a dual bootstrap layer 204. In some example embodiments, the dual bootstrap layer and the application can be located within the UE. The dual bootstrap device can be implemented within the UE. In other example embodiments, the application and / or the dual bootstrap layer can be located outside the UE.
[0118] 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.
[0119] The dual bootstrap layer 204 can be configured with one or more rules / policies for controlling the bootstrap, switching, and / or offloading of traffic, regardless of the dual bootstrap device implementation. The dual bootstrap layer is responsible for bootstrapping UL (uplink) data, which is the data from the dual bootstrap device to the network.
[0120] like Figure 2 and Figure 3 As shown in both examples, a User Plane Function (UPF) 206 is configured, which is responsible for bootstrapping DL (downlink) data, which is 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 offloading of DL traffic.
[0121] Traffic from the dual-boot device can be supplied to DN 210 by UPF 206. DN 210 can supply traffic to the UPF for the dual-boot device.
[0122] In some example embodiments, dual-booting devices can support traffic bootstrapping, offloading, and / or switching of user data across two access networks.
[0123] Data anchoring can be provided in either HPLMN (Home Public Land Mobile Network) or SNPN (Standalone Non-Public Network). User data can be for different services or for the same service.
[0124] In some example embodiments, dual-boot devices may be designed to minimize service disruptions when switching user data between two access networks.
[0125] In some example implementations, dual-booting devices can support changing a 3GPP access network to a non-3GPP access network with the same subscription (and vice versa).
[0126] Some example implementations of dual-boot devices may support one or more of the following traffic booting, switching, and / or offloading examples: Traffic routing, handover, and / or offloading 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 where one 3GPP access corresponds to a terrestrial access network (TNT), and the other to a non-terrestrial access network. Traffic routing, handover, and / or offloading between two 3GPP access networks: a PLMN and a PNI-NPN (Public Network Integration-NPN). These two 3GPP access networks may be associated with the same or different RATs (Radio Access Technologies); and / or Traffic routing, handover, and / or offloading across LTE / EPC (Long Term Evolution / Evolved Packet Core) and NR / 5GC (New Radio / 5G Core) are anchored within the 5GC. In other words, one access network can be a 4G access network, while the other can be a 5G access network.
[0127] A dual-boot PDU (Packet Data Unit) session is a PDU session triggered by a dual-boot device and intended for use in dual-booting. Dual-booting involves bootstrapping, switching, and / or offloading traffic. The traffic can be application traffic.
[0128] In the following examples, a dual-booting device with two UEs (each with its own subscriber identifier) is used to illustrate some exemplary embodiments. However, it should be understood that the exemplary embodiments can also be used with a dual-booting device having a UE that is associated with a first subscriber identifier and another part with a second subscriber identifier. In the following text, references to the parts of the UE are references to a dual-booting device having a UE that is associated with a first subscriber identifier and a second subscriber identifier.
[0129] For a dual-booting device used to implement dual-booting, the dual-booting device registers with each of two access networks (which can be the same or different). These two access networks can be 3GPP network accesses.
[0130] Each registration is triggered by a different subscription (e.g., SUPI and / or IMSI (International Mobile Subscriber Identity)). After registration, the dual-boot device establishes two dual-boot PDU sessions, one for each different subscription.
[0131] The first dual-booted PDU session (PDU session 1) is conducted through the first access network, and the first dual-booted PDU session (PDU session 1) corresponds to the first identifier SUPI-1. The first identifier SUPI-1 corresponds to the first registration. The first dual-booted PDU session (PDU session 1) has a branch (user plane resources) on the first access network.
[0132] The second dual-booted PDU session (PDU session 2) is conducted through the second access network, and the second dual-booted PDU session (PDU session 2) corresponds to the second identifier SUPI-2. The second identifier SUPI-2 corresponds to the second registration. The second dual-booted PDU session (PDU session 2) has a branch (user plane resources) on the second access network.
[0133] In some example 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 the dual-booting device may be connected to the same cell. In other words, the two sessions can be conducted via a public access network. In the example above, the first and second access networks may be the same access network.
[0134] The first and second dual-boot PDU sessions can serve specific application traffic.
[0135] In some example implementations, the core network can be the same for both registrations. When a dual-boot device needs to start operating in dual-boot mode to serve applications that require dual-booting, the same address is assigned to and used for both dual-boot PDU sessions.
[0136] Some example implementations can ensure that the same UE IP address is used for two dual-boot PDU sessions. This may be necessary in some example implementations used to handle specific application traffic.
[0137] PDU sessions that need to be linked together for dual bootstrapping can be provided as dual boot bundles. In an example embodiment, two bundled PDU sessions can be provided for dual bootstrapping. However, it should be understood that in some example embodiments, more than two bundled PDU sessions may also exist.
[0138] In some example implementations, these two dual-boot PDU sessions can be served by the same SMF service.
[0139] In some example embodiments, the two dual-boot PDU sessions can be served by different SMF services from the same SMF set.
[0140] In some example implementations, these two dual-boot PDU sessions can be served by the same UPF.
[0141] In some example implementations, these two dual-boot PDU sessions can be served by the same PCF.
[0142] In some example implementations, for two dual-boot PDU sessions, two PFCP (Packet Forwarding Control Protocol) sessions can be established, with one PFCP session for each dual-boot PDU session.
[0143] In some example implementations, for two dual-boot PDU sessions, two PFCP sessions can be established in the UPF, with one PFCP session for each dual-boot PDU session.
[0144] The two dual-boot PDU sessions and the two associated PFCP sessions are assigned the same UE IP address.
[0145] SMF can provide dual-boot related information when a PFCP session is created / modified. This dual-boot related information may include association information that enables UPF to associate the two dual-boot PFCP sessions. The term "dual-boot PFCP session" refers to the PFCP session established for the dual-boot PDU session.
[0146] The SMF can provide information to the UPF that instructs the UPF to assign the same UE IP address to both PFCP sessions.
[0147] In some example embodiments, for each PFCP session, the SMF may provide the UPF with one or more of the following: The following indicates that the PFCP session is a dual-booted PFCP session; Dual-boot ID (identifier); and / or The linked dual-boot ID is set to the dual-boot ID of another dual-boot PFCP session.
[0148] In other example embodiments, for each PFCP session, the SMF may provide the UPF with one or more of the following: The following indicates that the PFCP session is a dual-booted PFCP session; and / or Each PFCP session has a dual-boot ID that is the same dual-boot ID assigned to two dual-boot PFCP sessions.
[0149] These two dual-boot PDU sessions and the two associated PFCP sessions are assigned the same UE IP address.
[0150] In some example embodiments, the dual-boot ID can be set to, or associated with, the SUPI and PDU session IDs of the dual-boot PFCP session. In other example embodiments, the dual-boot ID can be set to an identifier selected by the SMF or provided by the PCF.
[0151] In some example implementations, the linked dual boot ID can be set to, or associated with, the SUPI and PDU session ID of another dual boot PDU session in order to uniquely identify a specific dual boot PDU session within a specific UE.
[0152] In some example implementations, the dual-boot ID and the linked dual-boot ID can be defined in a DL DR (Packet Detection Rule) or a DL traffic endpoint that includes the UE IP address.
[0153] In some example implementations, the linked dual-boot ID is not provided; instead, a dual-boot ID is provided for each dual-boot PFCP session and the same dual-boot ID is provided, thus enabling UPF to associate the two dual-boot PFCP sessions using the same dual-boot ID.
[0154] In some example implementations, the UPF can assign the same UE IP address to two dual-boot PFCP sessions. This can be based on information received from the SMF (such as the aforementioned information).
[0155] In other example embodiments, when a second dual-booting PFCP session is established, the SMF can provide the UPF with the UE IP address that has already been assigned to the first dual-booting PFCP session.
[0156] In other example embodiments, in a 5GC deployment where the UE IP address is typically assigned by the UPF, the SMF may provide the UE IP address to the UPF. For example, the UPF may be instructed to assign a specific UE IP address (provided by the SMF) to a dual-boot PFCP session. The UPF will recognize that the PFCP session is a dual-boot PFCP session based on one or more dual-boot indicators. These one or more dual-boot indicators may be as described above.
[0157] In 5GC deployments, UE IP addresses can be assigned by the UPF (e.g., for SMF aggregation deployments) or by the SMF. This can be based on the network operator's policy.
[0158] In some example embodiments of UPF assigning UE IP addresses, if one of two PFCP sessions has already been established, the UPF can assign the same UE IP address to the second PFCP session when it is established later. If neither of the two PFCP sessions has already been established, the UPF assigns a new UE IP address to the PFCP session being established. In either case, the UPF indicates the UE IP address assigned to each PFCP session in its response to the SMF(s).
[0159] In some example implementations of SMF assigning UE IP addresses, when establishing a PFCP session for a second dual-booting PDU session, the SMF provides the UE IP address that has already been assigned to the first dual-booting PDU session.
[0160] In deployments where the UE IP address is assigned by the SMF, the following instruction can be used by the UPF: the PFCP session is a dual-booted PFCP session to accept the same UE IP address for which the SMF applies the PFCP session.
[0161] In deployments where the UE IP address is assigned by the UPF, the following instruction can be used by the UPF: the PFCP session is a dual-boot PFCP session, to assign the same UE IP address to two PFCP sessions.
[0162] In some example embodiments, the dual boot binding ID and / or dual boot ID values used on the UPF and PCF interfaces do not need to have the same value (for the PCF interface and for the UPF interface).
[0163] refer to Figure 5a and Figure 5b These figures illustrate the process of UPF assigning the same UE IP address to two PFCP sessions in some example embodiments.
[0164] Signaling between (multiple) UEs and the SMF is transmitted via different access networks (e.g., 3GPP Access 1 and 3GPP Access 2) and the AMF to reach the SMF. However, it should be noted that this... Figure 5a and Figure 5b It is not shown in the text.
[0165] exist Figure 5a and Figure 5b In the example embodiments shown, a first UE and a second UE are illustrated for ease of reference. However, it should be understood that some example embodiments can alternatively be used with dual-boot devices, such as... Figure 3 As shown, it is used with a UE. In the latter case, UE 1 should be regarded as the first part corresponding to the UE, and UE 2 should be regarded as the second part corresponding to the UE.
[0166] As mentioned at point 0, the first UE (UE-1) registers through the first network access 3GPP access 1 and establishes the first dual-boot PDU session PDU1 through the first network access 3GPP access 1.
[0167] As mentioned at point 1, the SMF establishes an SM (Session Management) policy association for the first PDU session, PDU1. The SMF may send an SM policy association request to the PCF, which includes one or more of the following: the first subscriber identifier SUPI1; the UE IP address and / or prefix; the dual-boot binding ID; the dual-boot session ID; and / or the dual-boot SM policy association indication.
[0168] The establishment of an SM policy association can generally be as described in Clause 4.16.4 of TS 23.502, but the SM policy association is modified to include the information discussed above that is sent by the SMF to the PCF. The information can be sent in messages such as the Npcf_SMPolicyControl_Create message. Alternatively or additionally, at least part of the information can be sent in the Npcf_SMPolicyControl_Update message.
[0169] PCF uses policy information to respond to requests. This can include policy information for bundles indicated by a special tag in the corresponding PCC rule, or policy information related to the PDU session (e.g., session MBR information can be applied to bundles). This can include (multiple) DL PDRs and their dual-bootstrapping rules.
[0170] The part of the process mentioned at point 2 can be performed before or after the part of the process mentioned at point 3. This order can depend on the local policy of the SMF. Typically, SM policy control creation is performed before the PFCP session (e.g., as shown in part 6 of the process).
[0171] As mentioned in point 2, the SMF establishes a PFCP session for the first PDU session, PDU1. As part of this, the SMF may send a dual-boot PFCP session indication and / or a dual-boot bundle ID and / or a dual-boot session ID to the UPF. The SMF may also send a request to the UPF to allocate a UE IP address and / or an IPv6 prefix. This may be sent along with the dual-boot PFCP session indication and / or the dual-boot bundle ID and / or the dual-boot session ID.
[0172] The dual-boot global binding ID can be assigned by SMF. The same value is used in the second PFCP session in the section of the process mentioned at point 6.
[0173] The dual-boot session ID can be assigned by SMF to the PDU session. The same value is used for the second PFCP session in the section of the process mentioned in 6.
[0174] UPF uses the UE IP address and / or prefix already assigned by UPF to respond to requests from SMF.
[0175] After the PFCP session is established, the SM policy control update process can be optionally executed (e.g., as shown in part 3 of the process).
[0176] As mentioned in point 3, the SMF updates the SM (Session Management) policy association for the first PDU session, PDU1. The SMF may send an SM policy association request to the PCF, which includes one or more of the following: the first subscriber identifier SUPI 1; the UE IP address and / or prefix; the dual-boot binding ID; the dual-boot session ID; and the dual-boot SM policy association indication.
[0177] The establishment or updating of an SM policy association can generally be as described in Clause 4.16.4 of TS 23.502, but the SM policy association is modified to include the aforementioned information sent by the SMF to the PCF. The information can be sent in messages such as the Npcf_SMPolicyControl_Create message. Alternatively or additionally, at least a portion of the information can also be sent in the Npcf_SMPolicyControl_Update message.
[0178] The PCF utilizes policy information to respond to requests from the SMF. This can include policy information for bundles indicated by a dedicated tag in the corresponding PCC (Policy and Charging Control) rule, or policy information related to the PDU session (e.g., session MBR (Maximum Bit Rate) information can be applied to the bundle). This can include (multiple) DL PDRs and their associated dual-booting rules.
[0179] As mentioned in point 4, the PDU session establishment process continues, and the SMF responds to the first UE (UE1)'s PDU session establishment request. The establishment of the first PDU session, PDU1, is now complete. The SMF's response to the PDU session establishment request may include: the dual-booting related rules sent to the UE and the bundling policy information received in step 3.
[0180] As mentioned in point 5, the second UE (UE-2) registers through the second network access 3GPP access 2 and establishes a second dual-boot PDU session PDU2 through the second network access 3GPP access 2.
[0181] As mentioned in point 6, the SMF establishes an SM (Session Management) policy association for the second PDU session, PDU2. The SMF may send an SM policy association request to the PCF, which includes one or more of the following: second subscriber identifier SUPI 2; UE IP address and / or prefix; dual boot binding ID; dual boot session ID; linked dual boot session ID; and / or dual boot SM policy association indication.
[0182] The dual-boot binding ID can be the same value used in the section of the process mentioned in point 3.
[0183] The dual-boot session ID can be assigned by SMF to the value of the second PDU session PDU2, and then the same value can be sent as the dual-boot ID of the link in the first SM policy association.
[0184] The linked dual-boot session ID can be the same value as the dual-boot session ID used in the section of the process mentioned in point 3.
[0185] The establishment of an SM policy association can typically be as described in Clause 4.16.4 of TS 23.502, but the SM policy association is modified to include the aforementioned information sent by the SMF to the PCF. The information can be sent in a message such as the Npcf_SMPolicyControl_Create message. Alternatively or additionally, at least a portion of the information can also be sent in the Npcf_SMPolicyControl_Update message.
[0186] PCF responds to the request using policy information. This may include policy information for bundles indicated by a special tag in the corresponding PCC rule, or policy information related to the PDU session (e.g., session MBR information may be applied to the bundle). This may include (multiple) DL PDRs and their dual-bootstrapping rules.
[0187] As mentioned in point 7, the SMF establishes a PFCP session for the second PDU session. As part of this process, the SMF may send one or more of the following to the UPF: UE IP address and / or prefix; dual-boot PFCP session indication; dual-boot binding ID; and / or dual-boot session ID.
[0188] The dual-boot binding ID can be the same value used in the section on the process mentioned at point 3. This same value is used for the first PFCP session.
[0189] The dual-boot session ID can be a value assigned by SMF to the second PDU session PDU 2, and then, as mentioned at point 8 and in the section of the process described below, that same value is sent as the dual-boot ID for the link to the first PFCP session.
[0190] The linked dual-boot session ID can be the same value as the dual-boot session ID used in the section of the process mentioned in point 3.
[0191] As mentioned at point 8, the SMF can update the first PFCP session, for example, to provide a linked dual-boot ID. This could be the dual-boot session ID assigned in the part of the process mentioned in step 7.
[0192] As mentioned at point 9, the PDU session establishment process continues, and the SMF responds to the second UE (UE2)'s PDU session establishment request. The establishment of the second PDU session, PDU2, is now complete. The SMF's response to the PDU session establishment request may include: dual-booting related rules sent to the UE, and the bundling policy information received in the part of the process mentioned at point 6.
[0193] As for Figure 5a and Figure 5b In an alternative to the described example embodiment, the dual-boot session ID can be assigned by the SMF or by the PCF.
[0194] UPF is configured to handle DL packets, where two dual-booted PFCP sessions share the same UE IP address.
[0195] The PFCP model currently does not allow PFCP sessions used for regular PDU sessions to have overlapping DL PDRs, and therefore DL PDRs with the same UE IP address. Therefore, some example embodiments extend the PFCP model to allow two dual-boot PFCP sessions to be configured with overlapping PDRs (i.e., having the same UE IP address). As an example of such an embodiment, PDI (Packet Detection Information) may include dual-boot information. Dual-boot information may include one or more of the following: dual-boot ID; linked dual-boot ID; and / or dual-boot bundle ID. UPF takes dual-boot information into account and allows overlapping PDRs (i.e., having the same UE IP address).
[0196] If the UPF understands that the two PFCP sessions are part of a bundle, the PDR / PDI may not provide bundle information.
[0197] In some example implementations, session binding is the association of session information with a PDU session or dual-boot binding. The PCF can perform session binding, which may consider the following PDU session parameters: a) For IP-type PDU sessions, the UE IPv4 address and / or IPv6 prefix. In some example embodiments, for Ethernet-type PDU sessions, multiple UE MAC addresses are considered. In other example embodiments, any other suitable UE address may be considered; b) UE identifier (e.g., SUPI) (if present); c) Information about the data network (DN) that the user is accessing, such as DNN (data network name) and slice information (S-NSSAI) (if present).
[0198] Once the PCF has identified the affected PDU sessions(s), and hereby identifies one PDU session instead, in the case of bundled PDU sessions, the PCF can identify more than one PDU session. The PCF can identify the PCC rules affected by the AF session information, including new PCC rules to be installed and existing PCC rules to be modified or removed.
[0199] For each PDU session, the SMF establishes a PFCP session in the UPF using the PFCP protocol, thereby providing the UPF with a set of rules. These rules may include one or more of the following: Packet Detection Rules (PDR), QoS Enforcement Rules (QER), Usage Reporting Rules (URR), Forwarding Action Rules (FAR), and Multiple Access Rules (MAR).
[0200] refer to Figure 6 The figure schematically illustrates the downlink DL packet processing flow for a dual-booted PFCP session performed by the UPF in some example embodiments.
[0201] As mentioned at 600, the packet is received by the UPF.
[0202] As mentioned at 602, UPF determines that DL packets match a dual-boot PFCP session. This can be based on the target IP address and the dual-boot information associated with that target IP address. UPF performs a lookup for a second (which is a linked dual-boot session) dual-boot PFCP session (if it has already been established).
[0203] As mentioned at 604, the UPF performs a lookup for DL PDR 606, which matches the DL packet with the highest priority among all DL PDRs in the two dual-boot PFCP sessions.
[0204] As mentioned at 610, the UPF further processes the DL packets according to the packet processing rule 608 associated with the DL PDR. This processing may include routing, switching, or offloading traffic according to dual-booting rules.
[0205] When supporting simultaneous transmission of two dual-booted PDU sessions, different Service Data Streams (SDFs) of the PDU sessions can be bootstrapped to different dual-booted PDU sessions, such as SDF A and SDF B bootstrapped to dual-booted PDU session 1, and SDF C and SDF D bootstrapped to dual-booted PDU session 2.
[0206] When simultaneous transmission of two dual-booted PDU sessions is not supported, all traffic of a PDU session is transmitted on a single dual-booted PDU session at any given time. The dual-booted PDU session used to transmit traffic can change over time. For example, which dual-booted PDU session will be used can be defined according to the dual-booting rules that the SMF has obtained from the PCF and distributed to the UPF.
[0207] In some example implementations, dual-booting rules are defined in the PFCP protocol. This can be used in UPF, as per [reference needed]. Figure 6 The rule in question can support dual-boot functionality with simultaneous traffic in at least two dual-boot PDU sessions.
[0208] Some example implementations of dual-booting rules can indicate how DL traffic should be bootstrapped between two PDU sessions (e.g., two 3GPP accesses), the bootstrapping function used (e.g., ATSSS-LL (e.g., access traffic bootstrapping, handover, offloading lower layers), MPTCP (Multi-path Transmission Control Protocol), or MPQUIC (Multi-path QUIC)) and / or bootstrapping mode (e.g., active-standby; minimum latency; load balancing; priority-based; or redundancy).
[0209] In some example implementations, dual-booting rules can enable bootstrapping, switching, and offloading of DL traffic between two (dual-booting) PDU sessions (and therefore between two 3GPP access paths).
[0210] In some example implementations, a dual-booting rule can be associated with two FARs (Forwarding Action Rules) for two dual-booting PFCP sessions, one FAR for each dual-booting PFCP session.
[0211] The SMF can provide the UPF with common packet processing rules (e.g., dual-booting rules, QER (Quality of Service Enforcement rules), and / or URR (Usage Reporting rules)) only once. Common packet processing rules can be provided via either of the two dual-booting PFCP sessions. The UPF can apply the common packet processing rules to both dual-booting PFCP sessions. This can be achieved, for example, by associating the DL PDRs of the two PFCP sessions with these common rules. For example, the DL PDRs of the two PFCP sessions may include the dual-booting rule ID, QER ID, and / or URR ID. Alternatively, the common packet processing rules can explicitly indicate in the rule that the rule applies to any N4 / PDU session in the dual-booting packet.
[0212] Common packet processing rules can be modified or deleted via the same PFCP session used to supply the common packet processing rule, or via another dual-boot PFCP session. When one of the dual-boot PDU sessions is deleted, the common rule is maintained. The common rule is only deleted when both dual-boot PDU sessions are deleted.
[0213] In other example embodiments, the SMF can provide one or more QERs and / or one or more URRs specific to a given dual-booted PDU session. For example, this can allow for different QoS requirements for each PDU session / 3GPP access path, and / or support for measuring / billing traffic based on the PDU session / 3GPP access path used to transmit traffic.
[0214] These public rules can be modified or deleted via the same PFCP session used to configure them, or via another dual-boot PFCP session. When one of the dual-boot PDU sessions is deleted, the public rule is maintained. The public rule is only deleted when both dual-boot PDU sessions are deleted.
[0215] Alternatively, the SMF can supply QER and URR specific to a given dual-booted PDU session, for example, to support different QoS requirements for each PDU session / 3GPP access path, or to support measurement / billing traffic based on the PDU session / 3GPP access path used to transmit traffic.
[0216] In some example implementations, when two dual-boot PFCP sessions are established within the same SMF, if the SMF serving the dual-boot PFCP session is detected to be no longer responding, the UPF can move both dual-boot PFCP sessions to the same alternative SMF in the SMF set. The UPF can use a dual-boot PFCP session indication, a dual-boot binding ID, a dual-boot ID, and / or a linked dual-boot ID to assist in moving the two dual-boot PFCP sessions to the same alternative SMF in the SMF set.
[0217] In some example embodiments, when different SMFs in the same set are associated with two dual-boot PFCP sessions, if it is detected that one of the SMFs serving one of the PFCP sessions in the dual-boot PFCP session is no longer responding, the UPF can move the dual-boot PFCP session to an SMF serving the other dual-boot PFCP session. The UPF can use a dual-boot PFCP session indication, a dual-boot binding ID, a dual-boot ID, and / or a linked dual-boot ID to assist in moving the dual-boot PFCP session to another SMF.
[0218] In some example embodiments, the same PCF can be selected to control all dual-booted PDU sessions that need to be bundled. In some example embodiments, each PDU session can have a (e.g., N7) SM policy association, which can be established when the PDU session is established and released when the PDU session is released.
[0219] SMF can provide information related to dual bootstrapping when creating / modifying SM policy associations.
[0220] In some example implementations, for each SM policy association, the SMF may provide the PCF with at least one of the following: The following indicates that the SM policy is associated with dual-boot PFCP sessions; Dual-boot binding ID; Dual-boot ID (identifier); or The linked dual-boot ID is set to the dual-boot ID associated with another dual-boot SM policy.
[0221] In some example implementations, when the PCF provides multiple PCC rules related to the SM policy, the PCF can indicate whether the multiple PCC rules apply only to the corresponding PDU session or to all PDU sessions in the dual-boot bundle.
[0222] In some example implementations, common rules can be maintained when one of the PDU sessions in a dual-booting PDU session is deleted. Common rules are only deleted when all dual-booting PDU sessions in a dual-booting bundle are deleted.
[0223] In some example implementations, this reflects SMF behavior. A simpler SMF behavior might be required.
[0224] In some example implementations, since PDU sessions associated with dual-booting bundles and established on the DNN / S-NSSAI combination share the same IP address, the PCF is able to retrieve all PDU sessions that are part of the same dual-booting bundle when the session is bound.
[0225] In some example embodiments, PCC rule information may indicate how DL traffic should be routed between two PDU sessions (e.g., two 3GPP accesses), the routing function used (e.g., ATSSS-LL (e.g., access traffic routing, handover, offloading lower layers); MPTCP (Multi-Path Transmission Control Protocol), or MPQUIC (Multi-Path QUIC)), and / or the routing mode (e.g., active-standby; minimum latency; load balancing; priority-based; or redundancy). This PCC rule information may at least support dual-routing functionality with simultaneous traffic on two dual-routing PDU sessions.
[0226] In some example implementations, when it is detected that the SMF of a PDU session with a service dual-booting bundle is no longer responding, the PCF can move all SM policy associations associated with that dual-booting bundle to the same alternative SMF in the SMF set. The PCF can use dual-booting related information received when the SM policy associations were created / modified to determine which SM policy associations were affected.
[0227] In some example embodiments, when different SMFs in the same set are associated with two dual-boot PDU sessions, if it is detected that one SMF serving one of the PFCP sessions in the dual-boot PFCP session is no longer responding, the PCF can move the corresponding SM policy association to another SMF serving the other dual-boot PDU session. The PCF can use dual-boot related information received when the SM policy association is created / modified to determine which SM policy associations are affected.
[0228] In some example implementations, each dual-booted PFCP session is configured with its own user identifier in the UPF. This user identifier can be a SUPI, such as SUPI-1 and SUPI-2. For example, this could be when a network operator's policy requires that a user identifier be sent to the UPF.
[0229] Interception or tracing of UL / DL traffic for a given user identifier (e.g., SUPI) may result in the interception of all UL / DL traffic exchanged on either of the two dual-boot PDU sessions.
[0230] In some example embodiments, each dual-boot SM policy association is configured with its own subscriber identifier in the PCF. This subscriber identifier can be a SUPI, such as SUPI-1 and SUPI-2.
[0231] Interception or tracking of the UE IP address at the PCF for a given user identifier (e.g., SUPI) or DNN / S-NSSAI (Single Network Slice Selection Auxiliary Information) combination may result in the interception of exchanges associated with either of the PDU sessions in the dual-booting bundle.
[0232] Some example implementations can ensure that the same IP address is used for two dual-boot PDU sessions.
[0233] Figure 4 An example of device 201 is shown.
[0234] Device 201 may include or implement Figure 1One or more of the network functions shown are network functions. Device 201 may have at least one processor and at least one memory, the at least one memory storing... Figure 1 The instructions for one or more network functions shown, when executed by at least one of at least one processor, cause the operation or action of one or more network functions to be performed.
[0235] Alternatively, device 201 may include or implement Figure 2 or Figure 3 At least a portion of the 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.
[0236] 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.
[0237] For example, software code 215 may include software code for one or more network functions in the network functions, or software code for at least a portion of a dual-boot device. This software code may include software code that allows the device to perform one or more operations of one or more aspects of this document.
[0238] refer to Figure 7 and Figure 9 They showed some example implementations of the methods.
[0239] This method can be performed by a device.
[0240] The device may include or implement session management functions.
[0241] The device may include suitable components, such as a circuit system for providing the method.
[0242] Alternatively or additionally, the apparatus may include: at least one processor and at least one memory, the 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.
[0243] Alternatively or additionally, the device may be, for example, regarding Figure 4The apparatus under discussion.
[0244] This method can be provided by computer program code or computer executable instructions.
[0245] refer to Figure 7 :
[0246] The method may include, as mentioned at A1, sending a request to a user plane function to establish or modify a second Packet Forwarding Control Protocol (PTCP) session, the request to establish or modify the second PTCP session including second dual-booting information, the dual-booting information including: dual-booting information providing a link to a first PTCP session for a first Packet Data Unit (BDS) session, the second PTCP session being used for the second BDS session, the first BDS session and the second BDS session supporting dual-booting.
[0247] The method may include, as mentioned at A2, receiving from the user plane function an address for the second packet data unit session that is the same as the address used for the first packet data unit session, in response to a request to establish or modify a second packet forwarding control protocol session.
[0248] refer to Figure 9 :
[0249] The method may include, as mentioned at C1, sending a request to the user plane function to establish or modify a first packet forwarding control protocol session, the request to establish or modify the first packet forwarding control protocol session including: using an address for the first packet data unit session, the first packet forwarding control protocol session being associated with the first packet data unit session.
[0250] This method may include, as mentioned in C2, receiving a response to the request from a user-plane function.
[0251] The method may include, as mentioned in C3, sending a request to the user plane function to establish or modify a second Packet Forwarding Control Protocol (BTP) session, the request to establish or modify the second BTP session including: using an address for the second Packet Data Unit (BData) session, the same address used for the first BData session, the first BData session and the second BData session being associated BData sessions that support dual bootstrapping.
[0252] The method may include, as mentioned at C4, receiving a response to the request from a user plane function, the response accepting that the same address is being used for a second packet data unit session.
[0253] refer to Figure 8 , Figures 10 to 13 and Figure 16 These figures illustrate methods in some example embodiments.
[0254] This method can be performed by a device.
[0255] The device may include or implement user-plane functionality.
[0256] The device may include suitable components, such as a circuit system for providing the method.
[0257] Alternatively or additionally, the apparatus may include: at least one processor and at least one memory, the 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.
[0258] Alternatively or additionally, the device may be, for example, regarding Figure 4 The apparatus under discussion.
[0259] This method can be provided by computer program code or computer executable instructions.
[0260] refer to Figure 8 :
[0261] The method may include, as mentioned in B1, receiving from a session management function a request to establish or modify a second Packet Forwarding Control Protocol (PTCP) session, the request to establish or modify the second PTCP session including second dual-booting information, the dual-booting information including: dual-booting information providing a link to a first PTCP session for a first Packet Data Unit (PaDN) session, the second PTCP session being used for the second PTCP session, the first PTCP session and the second PTCP session being associated PTCP sessions supporting dual-booting.
[0262] The method may include, as mentioned in B2, storing the association between the first packet forwarding control protocol session and the second packet forwarding control protocol session.
[0263] The method may include, as mentioned in B3, sending, in response to the request, an address for a second packet data unit session that is the same as the address used for the first packet data unit session to the session management function.
[0264] refer to Figure 10 :
[0265] The method may include, as mentioned at D1, receiving a request from a session management function to establish or modify a first packet forwarding control protocol session, the request to establish or modify the first packet forwarding control protocol session including: using an address for the first packet data unit session, the first packet forwarding control protocol session being associated with the first packet data unit session.
[0266] This method may include, as mentioned in D2, sending a response to the request to the session management function.
[0267] The method may include: receiving a request to establish or modify a second Packet Forwarding Control Protocol (BTP) session from the same or different session management functions, as mentioned in D3, wherein the request to establish or modify the second BTP session includes: using an address for the second Packet Data Unit (BDN) session, an address used for the second BDN session that is the same as the address used for the first BDN session, and the first BDN session and the second BDN session are associated BDN sessions that support dual bootstrapping.
[0268] The method may include: as mentioned at D4, sending a response to the request to the same or different session management function, the response accepting that the same address is being used for a second packet data unit session.
[0269] refer to Figure 11 :
[0270] The method may include, as mentioned in E1, receiving packets associated with the first packet forwarding control protocol session.
[0271] The method may include, as mentioned at E2, determining which of the packet detection rules associated with the first packet forwarding control protocol session and the second packet forwarding control protocol session has the highest priority, wherein the first packet forwarding control protocol session and the second packet forwarding control protocol session are used to support the associated packet data unit sessions of dual bootstrapping.
[0272] This method may include applying one or more instructions from the highest priority group detection rules to the group, as mentioned in E3.
[0273] refer to Figure 12 :
[0274] The method may include, as mentioned at F1, determining that the first session management function for serving the first packet data unit session and the second packet data unit session is no longer able to support the first packet data unit session and the second packet data unit session, which are associated packet data unit sessions that support dual bootstrapping.
[0275] The method may include, as mentioned at F2, moving the first packet data unit session and the second packet data unit session to a second session management function, the second session management function belonging to the same set of session management functions as the first session management function.
[0276] refer to Figure 13 :
[0277] The method may include, as mentioned in G1, determining that the first session management function of the service-supported first packet data unit session is no longer able to support the first packet data unit session.
[0278] The method may include, as mentioned in G2, moving the first packet data unit session to a second session management function, the second session management function supporting the second packet data unit session, and the first packet data unit session and the second packet data unit session supporting dual bootstrapping.
[0279] refer to Figure 16 :
[0280] The method may include, as mentioned at J1, providing a first dual-boot packet forwarding control protocol session for a first packet data unit session, the first dual-boot packet forwarding control protocol session being associated with a first subscriber identifier associated with the dual-boot device.
[0281] The method may include, as mentioned at J2, providing a second dual-boot packet forwarding control protocol session for a second packet data unit session, the second dual-boot packet forwarding control protocol session being associated with a second subscriber identifier associated with a dual-boot device, the first packet data unit session and the second packet data unit session supporting dual booting.
[0282] The method may include: using one of the first identifier and the second identifier, as mentioned in J3, to intercept or trace dual-boot traffic, to intercept or trace dual-boot traffic of both the first packet data unit session and the second packet data unit session.
[0283] refer to Figure 14 , Figure 15 , Figure 17 and Figure 18 These figures illustrate methods in some example embodiments.
[0284] This method can be performed by a device.
[0285] The device may include or implement policy control functions.
[0286] The device may include suitable components, such as a circuit system for providing the method.
[0287] Alternatively or additionally, the apparatus may include: at least one processor and at least one memory, the 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.
[0288] Alternatively or additionally, the device may be, for example, regarding Figure 4 The apparatus under discussion.
[0289] This method can be provided by computer program code or computer executable instructions.
[0290] refer to Figure 14 :
[0291] The method may include, as mentioned at H1, determining that the first session management function for serving the first packet data unit session and the second packet data unit session is no longer able to support the first packet data unit session and the second packet data unit session, and that the first packet data unit session and the second packet data unit session support dual bootstrapping.
[0292] The method may include, as mentioned at H2, moving the session management policies associated with the first packet data unit session and the second packet data unit session to a second session management function, the second session management function belonging to the same set of session management functions as the first session management function.
[0293] refer to Figure 15 :
[0294] The method may include, as mentioned in I1, determining that the first session management function of the service-supported first packet data unit session is no longer able to support the first packet data unit session.
[0295] The method may include, as mentioned at I2, moving the session management policy associated with the first packet data unit session to a second session management function, the second session management function supporting the second packet data unit session, and the first packet data unit session and the second packet data unit session supporting dual bootstrapping.
[0296] refer to Figure 17 :
[0297] The method may include, as mentioned at K1, providing a first session management policy for the first packet data unit session, the first session management policy being associated with a first subscriber identifier associated with the dual-boot device.
[0298] The method may include, as mentioned at K2, providing a second session management policy for the second packet data unit session, the second session management policy being associated with a second subscriber identifier associated with the dual-boot device, the first packet data unit session and the second packet data unit session supporting dual booting.
[0299] The method may include, as mentioned at K3, using one of the first identifier and the second identifier to intercept or trace dual-boot traffic, in order to intercept or trace dual-boot traffic of both the first packet data unit session and the second packet data unit session.
[0300] refer to Figure 18 :
[0301] The method may include: as mentioned at L1, retrieving information about a first packet data unit session and a second packet data unit session based on a public address and / or a public dual boot identifier, wherein the first packet data unit session and the second packet data unit session together support dual boot and binding the information about the first packet data unit session and the second packet data unit session together to form a dual boot bundle.
[0302] It should be understood that Figures 7 to 18 Any one or more of the methods outlined in the preceding text can be modified to include any of the features described above.
[0303] Computer program code can be downloaded and stored in one or more memories of the apparatus described herein.
[0304] Therefore, although certain example embodiments have been described above by way of non-limiting and illustrative examples, and with reference to specific 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 the communication systems illustrated and described herein. For example, some example embodiments have been described with respect to 5G communication systems (5GS). It should be understood that other example embodiments can be provided in any other suitable communication system(s), or in any suitable combination with 5GS.
[0305] As used herein, “at least one of the following: ” and “at least one of ” and similar wording (where the two or more elements in the list are 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 the elements.
[0306] As used herein, the expression “and / or” includes any and all combinations of the listed terms, including at least one of these elements, or at least any two or more of these elements, or at least all of these elements.
[0307] As used herein, the term “or” means non-exclusive “or” unless otherwise indicated (e.g., “otherwise” or “or in an alternative”).
[0308] As used herein, unless explicitly stated otherwise, performing a corresponding feature, step, or function in response to A does not indicate that the corresponding feature, step, or function is performed immediately after A occurs, because one or more intermediate features, steps, or functions may be performed (at least partially) between the occurrence of A and the corresponding feature, step, or function. Similarly, performing a corresponding feature, step, or function based on A does not indicate that the corresponding feature, step, or function is performed solely based on A, because the corresponding feature, step, or function may also be based on one or more other features, steps, or functions besides A.
[0309] In general, the various exemplary embodiments of this disclosure can be implemented in hardware or special-purpose circuit 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 (which can be executed by a controller, microprocessor, or other computing device), but this disclosure is not limited thereto. Although the 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 the blocks, apparatuses, systems, techniques, or methods described herein can be implemented (by way of non-limiting and illustrative example) in hardware, software, firmware, special-purpose circuits or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.
[0310] As used herein, the term "circuit system" can refer to one, more, or all of the following: (a) Hardware-only circuit implementations (such as implementations using only analog and / or digital circuits) and (b) A combination of hardware circuitry and software, such as (where applicable): (i) A combination of (multiple) analog and / or digital hardware circuits with software / firmware; and (ii) Any part of a hardware processor (including a digital signal processor), software, and memory (including a plurality of) working 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 a portion of (multiple) microprocessors) that require software (e.g. firmware) to operate, but may be absent if the software is not required to operate.
[0311] The definition of "circuit system" applies to its use herein (including in any claim). As another example, as used herein, the term "circuit system" also covers implementations consisting solely of hardware circuitry or a processor (or multiple processors), or portions thereof, and their accompanying software and / or firmware. For example, and 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, and / or other computing or network devices.
[0312] The various exemplary embodiments of this disclosure can be implemented by computer software executed by a data processor of a mobile device, such as in a processor entity, or by hardware or 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 a specific task. A computer program product may include one or more computer-executable components that are configured to perform the various exemplary embodiments of this disclosure when the program is run. The one or more computer-executable components may include software code or any portion thereof.
[0313] Additionally, it should be noted that any box in the logic flow diagram may represent a program step, or interconnected logic circuits, boxes and functions, or a combination of program steps and logic circuits, boxes and functions. Software may be stored on a physical medium such as a memory chip, or a block of memory implemented within a processor, a magnetic medium such as a hard disk or floppy disk, or an optical medium (e.g., DVD and its data variant CD). This physical medium is non-transitory.
[0314] As used herein, the term “non-transitory” refers to a limitation on the medium itself (i.e., tangible, not tactile), rather than a limitation on the persistence of data storage (e.g., RAM versus ROM).
[0315] 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 storage devices, magnetic storage devices and systems, optical storage 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 and illustrative example, can include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an FPGA, gate-level circuits, and processors based on multi-core processor architectures.
[0316] The various example embodiments of this disclosure can be implemented in various components such as integrated circuit modules. The design of integrated circuits is generally a highly automated process. Complex and powerful software tools can be used to convert logic-level designs into semiconductor circuit designs for etching and formation on semiconductor substrates.
[0317] The foregoing description has provided a complete and informative description of various exemplary embodiments of this disclosure through non-limiting and illustrative examples. However, various modifications and adaptations may become apparent to those skilled in the art when read in conjunction with the accompanying drawings and claims, given the foregoing description. Indeed, there are additional exemplary embodiments that include any combination of one or more exemplary embodiments with other exemplary embodiments. The scope of protection sought in some of the various exemplary embodiments of this disclosure is defined by the claims. Various exemplary embodiments not falling within the scope of the claims, other than the corresponding aspects and features described herein, should be interpreted as examples that contribute to the understanding of the various exemplary embodiments of this disclosure. It should be noted that different claims with different scopes may be sought in related applications, such as divisional or successive applications.
Claims
1. A method comprising: A request to establish or modify a second Packet Forwarding Control Protocol (PTCP) session is sent to the user plane function. This request includes second dual-booting information, which includes: dual-booting information providing a link to a first PTCP session used for a first Packet Data Unit (PaDN) session, wherein the second PTCP session is used for the second PaDN session, and both the first and second PaDN sessions support dual-booting; and In response to the request to establish or modify the second packet forwarding control protocol session, the address for the second packet data unit session, which is the same as the address used for the first packet data unit session, is received from the user plane function.
2. The method according to claim 1, comprising: Before sending the request to establish or modify the second packet forwarding control protocol session: Send a request to the user plane function to establish or modify the first packet forwarding control protocol session, the request to establish or modify the first packet forwarding control protocol session including first dual bootstrap information; as well as In response to the request to establish or modify the first packet forwarding control protocol session, the address for the first packet data unit session is received from the user plane function.
3. The method according to claim 2, comprising: Send a request to the policy control function for a session management policy association for the first packet data unit session, the request for the session management policy association for the first packet data unit session including dual-bootstrapping related information; and Receive policy information from the policy control function.
4. The method of claim 3, wherein the dual-booting related information provided in the request for association of a session management policy for the first packet data unit session includes at least one of the following: The following indicator indicates that the session management policy association is used for dual-booting packet data unit sessions; The identifier for the dual-booting bundle of the associated packet data unit session that supports dual booting; A dual-bootstrap identifier used for the session associated with the first session management policy; A common dual-boot identifier used for the first session management policy associated session and the second session management policy associated with the second packet data unit session; The second session management policy associates the dual-bootstrapping identifier of the session link; or The first session management policy is associated with the session identifier of the session management policy.
5. The method according to any one of the preceding claims, comprising: Send a request to the policy control function for a session management policy association for the second packet data unit session, the request for the session management policy association for the second packet data unit session including the dual-bootstrapping related information; and Receive policy information from the policy control function.
6. The method of claim 5, wherein the dual-bootstrapping related information provided in the request for association of session management policy for the second packet data unit session includes at least one of the following: The following indicator indicates that the session management policy association is used for dual-booting packet data unit sessions; The identifier for the dual-booting bundle of the associated packet data unit session that supports dual booting; The dual bootstrap identifier used to associate the session with the second session management policy; A common dual-bootstrap identifier used for the session associated with the first session management policy and the session associated with the second session management policy; or The first session management policy is associated with a dual-bootstrapping identifier for the linked session; The second session management policy is associated with the session identifier of the session management policy.
7. The method according to any one of claims 3 to 6, wherein the strategy comprises at least one of the following: One or more rules applicable to the first packet data unit session and the second packet data unit session; One or more rules applicable to the first packet data unit session; or One or more rules applicable to the second packet data unit session.
8. A method comprising: The request to establish or modify a second Packet Forwarding Control Protocol (PTCP) session is received from the session management function. The request to establish or modify the second PTCP session includes second dual-booting information, which includes dual-booting information providing a link to a first PTCP session for a first Packet Data Unit (BDN) session. The second PTCP session is used for the second BDN session, and the first BDN session and the second BDN session are associated BDN sessions that support dual-booting. Store the association between the first packet forwarding control protocol session and the second packet forwarding control protocol session; and In response to the request, the same address used for the second packet data unit session as the address used for the first packet data unit session is sent to the session management function.
9. The method of claim 8, comprising: Before receiving the request to establish or modify the second packet forwarding control protocol session: Receive a request to establish or modify the first packet forwarding control protocol session from the same or different session management functions, wherein the request to establish or modify the first packet forwarding control protocol session includes first dual bootstrap information; as well as In response to the request to establish or modify the first packet forwarding control protocol session, the address for the first packet data unit session is sent to the same or different session management functions.
10. The method according to any one of the preceding claims, wherein the first dual-guiding information comprises at least one of the following: The following indicates that the first packet forwarding control protocol session is a packet forwarding control protocol session used for dual-booted packet data unit sessions; The identifier for the dual-booting bundle of the associated packet data unit session that supports dual booting; Dual bootstrap identifier used for the first packet forwarding control protocol session; Common dual bootstrap identifiers used for the first packet forwarding control protocol session and the second packet forwarding control protocol session; or The dual bootstrap identifier of the connection for the second Packet Forwarding Control Protocol session; or The packet forwarding control protocol identifier of the first packet forwarding control protocol session.
11. The method according to any one of the preceding claims, wherein the second dual-guiding information comprises at least one of the following: The following indicates that the second packet forwarding control protocol session is a packet forwarding control protocol session used for dual-booted packet data unit sessions; The identifier for the dual-booting bundle of the associated packet data unit session that supports dual booting; The dual bootstrap identifier of the second packet forwarding control protocol session; The common dual bootstrap identifier used for the first packet forwarding control protocol session and the second packet forwarding control protocol session; or The dual bootstrap identifier of the connection in the first Packet Forwarding Control Protocol session; or The packet forwarding control protocol identifier of the second packet forwarding control protocol session.
12. The method of claim 10 or 11, wherein the corresponding dual-boot identifier for the corresponding session is based on the corresponding subscriber identifier of the dual-boot device and the identifier associated with the corresponding packet data unit session.
13. The method of claim 10, 11 or 12, wherein the dual-boot identifier of the corresponding link is based on the corresponding subscriber identifier of the dual-boot device and an identifier associated with the corresponding other packet data unit session.
14. The method according to any one of the preceding claims, wherein the request to establish or modify the second packet forwarding control protocol session includes the address, which is requested to be used by the user plane function for the second packet data unit session.
15. A method comprising: Sending a request to the user plane function to establish or modify a first packet forwarding control protocol session, the request to establish or modify the first packet forwarding control protocol session includes: using the address to be used for the first packet data unit session, the first packet forwarding control protocol session being associated with the first packet data unit session; Receive a response to the request from the user plane function; Sending a request to the user plane function to establish or modify a second Packet Forwarding Control Protocol (BTP) session, the request to establish or modify the second BTP session includes: using an address used for the second Packet Data Unit (BDN) session, an address used for the second BDN session that is the same as the address used for the first BDN session, where the first BDN session and the second BDN session are associated BDN sessions supporting dual bootstrapping; and The user plane function receives a response to the request, the response acknowledging that the same address is being used for the second packet data unit session.
16. A method comprising: Receive a request from the session management function to establish or modify a first packet forwarding control protocol session. The request to establish or modify the first packet forwarding control protocol session includes: using an address that is used for the first packet data unit session, and associating the first packet forwarding control protocol session with the first packet data unit session. Send a response to the request to the session management function; Receive a request to establish or modify a second Packet Forwarding Control Protocol (PTCP) session from the same or different session management functions. The request to establish or modify the second PTCP session includes: using an address for the second Packet Data Unit (BDN) session, an address used for the second BDN session that is the same as the address used for the first BDN session, where the first BDN session and the second BDN session are associated BDN sessions supporting dual bootstrapping; and Send a response to the request to the same or different session management functions, the response acknowledging that the same address is being used for the second packet data unit session.
17. The method of claim 15 or claim 16, wherein the request to establish or modify the second packet forwarding control protocol session includes an indication that the second packet forwarding control protocol session is for a dual-booted packet data unit session.
18. The method according to any one of the preceding claims, wherein the same address comprises: IP address, Internet Protocol IP address prefix, or Media Access Control (MAC) address.
19. The method according to any one of the preceding claims, wherein the same address comprises: The address associated with a dual-boot device that supports dual booting.
20. The method according to any one of claims 1 to 7, 10 to 15, and 17 to 19, comprising: One or more grouping rules are provided to the user plane function, wherein the one or more grouping rules include at least one of the following: One or more rules applicable to the first packet forwarding control protocol session and the second packet forwarding control protocol session; One or more rules applicable to the first packet forwarding control protocol session; or One or more rules applicable to the second packet forwarding control protocol session.
21. A computer program comprising computer-executable instructions that, when executed, provide the method according to any one of claims 1 to 20.
22. An apparatus comprising components for performing the method according to any one of claims 1 to 20.
23. An apparatus comprising at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform at least the method according to any one of claims 1 to 20.
