Method, apparatus and computer program for establishing multi-access data session in mobile network

Abstract

A method for an apparatus, the method comprising: receiving a policy, the policy comprising policy information indicating preferences on which access paths from a plurality of access paths a multi-access data session for applying traffic will be established, the plurality of access paths are through at least two accesses operating according to a first standard or at least two accesses operating according to a further standard; selecting at least two access paths from a plurality of access paths for the multi-access data session based on the policy information; and requesting establishment of a multi-access data session for applying traffic through the selected at least two access paths, the selected at least two access paths being through at least two accesses operating according to a first standard or at least two accesses operating according to a further standard.

Description

[0001] Cross - reference to related applications

[0002] This patent application claims priority to UK Patent Application No. 2218433.7, filed on December 8, 2022, which is incorporated herein by reference in its entirety as if reproduced in full. Technical Field

[0003] Embodiments of the present application relate to a method, apparatus, system, and computer program for establishing a multi-access data session in a mobile network. Background Art

[0004] A communication system can be regarded as a facility that enables communication between two or more entities, such as terminals or other nodes, or between a terminal and other nodes, or provides connection services to the entities. The communication can carry, for example, voice, video, email, text messages, multimedia data, or content data. Non-limiting examples of the connection services provided by the communication system can include enhanced mobile broadband, ultra-reliable low-latency communication, mission-critical communication, massive Internet of Things (IoT), and multimedia services.

[0005] A mobile network can include one or more communication systems and one or more compatible terminals (also referred to as communication devices). Examples of mobile networks include public land mobile networks or stand-alone non-public networks. In a communication system, at least a portion of the communication between at least two entities is carried out via a wireless link. A communication system typically includes an access network and a core network. The access network can be a radio access network, such as a terrestrial radio access network or a non-terrestrial radio access network (e.g., a satellite network), a wireless local network, such as a wireless local area network (WLAN), or a fixed network. A mobile network can include cells and is thus commonly referred to as a cellular network.

[0006] A terminal can be referred to as a user equipment (UE) or a user device. The terminal is provided with appropriate signal receiving and transmitting means for enabling wireless communication, such as enabling access to a mobile network or directly communicating with other terminals. The terminal can access a carrier provided by a base station (e.g., a base station of a radio access network) and send or receive, or send and receive communication on the carrier.

[0007] Communication systems and their associated compatible terminals typically operate according to a given standard or specification, which defines what the various network entities in the communication system are allowed to do and how this should be achieved. The communication protocols or parameters, or both, to be used for communication are also typically defined. An example of a communication system is the Universal Mobile Telecommunications System (UMTS) system (e.g., a communication system using 3G radio access technology). Other examples of communication systems are the so-called 4G systems (e.g., communication systems using 4G radio access technology) and 5G or New Radio (NR) systems (e.g., communication systems operating using 5G or NR radio access technology). The radio access technologies used by communication systems are standardized by the 3rd Generation Partnership Project (3GPP). SUMMARY OF THE INVENTION

[0008] According to one aspect, a method for a device in a mobile network is provided. The method includes: receiving a policy that includes policy information indicating a preference regarding which access paths from a plurality of access paths will be established for a multi-access data session for application traffic, the plurality of access paths being at least two accesses operating according to a first criterion or at least two accesses operating according to an additional criterion; selecting, based on the policy information, at least two access paths from the plurality of access paths for the multi-access data session; and requesting establishment of the multi-access data session including the selected at least two access paths, the selected at least two access paths being at least two accesses operating according to a first criterion or at least two accesses operating according to an additional criterion.

[0009] The at least two accesses operating according to the first criterion may be 3GPP accesses, and the at least two accesses operating according to the additional criterion may be non-3GPP accesses.

[0010] The policy information including policy information indicating a preference regarding which access paths from a plurality of access paths will be established for a multi-access data session for application traffic may include at least one of the following: a description of the application traffic; an identifier identifying the access path through which the device registers with the mobile network; an identifier identifying the type of access; an identifier identifying the radio access technology of the access; a combination of a source IP address, a destination IP address, a source port number, a destination port number, and a protocol of the multi-access data session; an identifier identifying the mobile network; and an identifier identifying the network operator of the mobile network.

[0011] The identifier identifying the mobile network may include at least one of the following: an identifier identifying a public land mobile network; and an identifier identifying an independent non-public network.

[0012] Selecting at least two access paths from a plurality of access paths for a multi-access data session based on policy information may include: selecting at least two access paths from a plurality of access paths where the plurality of access paths correspond to the access paths identified within the policy information; and the plurality of access paths are registered with a mobile network via the device.

[0013] Selecting at least two access paths from a plurality of access paths for a multi-access data session based on policy information may include: selecting at least two access paths from the plurality of access paths corresponding to the access paths identified within the policy information.

[0014] Requesting the establishment of a multi-access data session including the selected at least two access paths may further include: requesting registration with a mobile network via at least one of the accesses on which the multi-access data session is to be established through the selected at least two access paths; and requesting the establishment of the selected at least two access paths.

[0015] The policy may include a user equipment routing selection policy, and the policy information may be a routing descriptor component type identifier, the routing descriptor component type identifier including: a preference for which access paths from a plurality of access paths will be established for a multi-access data session.

[0016] The routing descriptor component type identifier may include one octet indicating the number of multi-access preference fields, followed by octets of the multi-access preference fields, where the octets of the multi-branch preference fields may include at least one of the following: an indicator indicating the type of access; an indicator indicating the radio access technology; a registration identity corresponding to registration with a mobile network via the access; an indicator indicating a preference for selecting a public land mobile network or an independent non-public network; and an indicator indicating a preference for prohibiting the selection of a public land mobile network or an independent non-public network.

[0017] Receiving a policy that includes policy information indicating a preference regarding which access paths from a plurality of access paths will be established for a multi-access data session for application traffic, including receiving policy information via one of the following: control plane signaling; and user plane signaling.

[0018] The policy information may include user subscription information that indicates that a multi-access data session can be requested to be established by the device via at least one of the following: a defined type of access; and a defined radio access technology, where the multi-access data session is for at least one of the following: defined single network slice selection assistance information; and a defined data network name.

[0019] The method may further include: requesting release of at least one of the selected at least two access paths for a multi-access data session.

[0020] Requesting release of one of the selected at least two access paths for a multi-access data session may include: requesting release of the one access path based on determining a substantial loss of connectivity to the access network in the one access path.

[0021] According to a second aspect, there is provided a method for a device in a mobile network, the method including: generating a policy that includes policy information indicating a preference regarding which of a plurality of access paths will be established for a multi-access data session for application traffic, the plurality of access paths being at least two accesses operating according to a first criterion, or at least two accesses operating according to an additional criterion; and sending the policy to another device registered with the mobile network.

[0022] The at least two accesses operating according to the first criterion may be 3GPP accesses, and the at least two accesses operating according to the additional criterion may be non-3GPP accesses.

[0023] For each access path, the policy information indicating a preference regarding which of a plurality of access paths will be established for a multi-access data session for application traffic may include at least one of the following: a description of the application traffic using the multi-access data session; an identifier identifying the access via which the other device is registered; an identifier identifying the type of access; an identifier identifying the radio access technology of the access; a combination of the source IP address, destination IP address, source port number, destination port number, and protocol of the multi-access data session; an identifier identifying the mobile network in which the access path is located (or to which it belongs); and an identifier identifying the network operator of the mobile network in which the access path is located (or to which it belongs).

[0024] The identifier identifying the network may include at least one of the following: an identifier identifying a public land mobile network; an identifier identifying an independent non-public network.

[0025] The method may further include: receiving, from another device, a request for establishment of a multi-access data session via at least two accesses operating according to the first criterion, or at least two accesses operating according to the additional criterion; and based on the received request, establishing the multi-access data session via at least two accesses operating according to the first criterion, or at least two accesses operating according to the additional criterion.

[0026] The method may further include: receiving a request to register an additional device to a mobile network via at least two accesses operating according to a first criterion, or at least two accesses operating according to an additional criterion; and based on the received request, registering the additional device to the mobile network via at least two accesses operating according to a first criterion, or at least two accesses operating according to an additional criterion.

[0027] The policy may include a user equipment routing policy, and the policy information may be a routing descriptor component type identifier, which includes: a preference for on which access path among multiple access paths from a communication network a multi-access data session will be established.

[0028] The routing descriptor component type identifier may include one octet indicating the number of multi-access preference fields, followed by octets of the multi-access preference fields, where the octets of the multi-branch preference fields may include at least one of the following: an indicator indicating the type of access; an indicator indicating the radio access technology; a registration identity corresponding to registration to the mobile network via the access; an indicator indicating a preference for selecting a public land mobile network or an independent non-public network; and an indicator indicating a preference for prohibiting the selection of a public land mobile network or an independent non-public network.

[0029] Sending the policy to an additional device may include sending the policy information via one of the following: control plane signaling; and user plane signaling.

[0030] The policy information may include user subscription information, which indicates that a multi-access data session can be requested to be established by an additional device via at least one of the following: a defined type of access; and a defined radio access technology, where the multi-access data session is for at least one of the following: a defined single network slice selection assistance information; and a defined data network name.

[0031] The method may further include: receiving a request for release of at least one access path among the selected at least two access paths for a multi-access data session; and authorizing the release of at least one access path among the selected at least two access paths for the multi-access data session.

[0032] According to a third aspect, there is provided an apparatus for a mobile network, the apparatus comprising means for: receiving a policy that includes policy information indicating a preference regarding which access paths from a plurality of access paths will be established for a multi-access data session for application traffic, the plurality of access paths being at least two accesses operating according to a first criterion, or at least two accesses operating according to another criterion; selecting at least two access paths from the plurality of access paths for the multi-access data session based on the policy information; and requesting establishment of the multi-access data session including the selected two access paths, the selected at least two access paths being at least two accesses operating according to a first criterion, or at least two accesses operating according to another criterion.

[0033] The at least two accesses operating according to the first criterion may be 3GPP accesses, and the at least two accesses operating according to the another criterion may be non-3GPP accesses.

[0034] For each access path, the policy information indicating a preference regarding which access paths from the plurality of access paths will be established for the multi-access data session for application traffic may include at least one of the following: a description of the application traffic using the multi-access data session; an identifier identifying the access via which the apparatus is registered with the communication network; an identifier identifying the type of the access; an identifier identifying the radio access technology of the access; a combination of a source IP address, a destination IP address, a source port number, a destination port number, and a protocol of the multi-access data session; an identifier identifying the mobile network in which (or to which) the access path is located; and an identifier identifying the network operator of the mobile network in which (or to which) the access path is located.

[0035] The identifier identifying the network may include at least one of the following: an identifier identifying a public land mobile network; and an identifier identifying an independent non-public network.

[0036] The means for selecting at least two access paths from the plurality of access paths for the multi-access data session based on the policy information may be means for selecting at least two access paths from a plurality of access paths that: correspond to the access paths identified within the policy information; and are registered with the mobile network via the apparatus.

[0037] The means for selecting at least two access paths from the plurality of access paths for the multi-access data session based on the policy information may be means for selecting at least two access paths from the plurality of access paths corresponding to the access paths identified within the policy information.

[0038] The component for requesting the establishment of a multi-access data session including at least two selected access paths may be a component for: requesting registration with the mobile network via at least one of the at least two selected access paths; and requesting the establishment of a multi-access data session via at least one of the at least two selected access paths.

[0039] The policy may include a user equipment routing selection policy, and the policy information may be a routing descriptor component type identifier, which includes: the preference for on which of the multiple access paths from the communication network the multi-access data session will be established.

[0040] The routing descriptor component type identifier may include an octet indicating the number of multi-access preference fields, followed by octets of the multi-access preference fields, where the octets of the multi-branch preference fields may include at least one of the following: an indicator indicating the type of access; an indicator indicating the radio access technology; a registration identity corresponding to registration with the mobile network via the access; an indicator indicating the preference for selecting a public land mobile network or an independent non-public network; and an indicator indicating the preference for prohibiting the selection of a public land mobile network or an independent non-public network.

[0041] The component for receiving the policy may be a component for receiving policy information via one of the following: control plane signaling; and user plane signaling, where the policy includes policy information indicating the preference for on which of the multiple access paths the multi-access data session will be established for application traffic.

[0042] The policy information may include user subscription information, which indicates that the multi-access data session can be requested to be established by the device via at least one of the following: a defined type of access; and a defined radio access technology, where the multi-access data session is for at least one of the following: defined single network slice selection assistance information; and a defined data network name.

[0043] The component may also be a component for requesting the release of at least one of the at least two selected access paths for the multi-access data session.

[0044] The component for requesting the release of one of the at least two selected access paths for the multi-access data session may be used to: request the release of the at least one of the at least two selected access paths based on determining a substantial loss of connectivity to one of the at least two selected access paths.

[0045] According to a fourth aspect, a device for a mobile network is provided, the device including components for: generating a policy that includes policy information indicating a preference regarding which access paths from a plurality of access paths will be established for a multi-access data session for application traffic, the plurality of access paths being at least two accesses operating according to a first criterion, or at least two accesses operating according to an additional criterion; and sending the policy to another device registered with the mobile network.

[0046] The at least two accesses operating according to the first criterion may be 3GPP accesses, and the at least two accesses operating according to the additional criterion may be non-3GPP accesses.

[0047] For each access path, the policy information indicating a preference regarding which access paths from the plurality of access paths will be established for the multi-access data session for application traffic may include at least one of the following: a description of the application traffic using the multi-access data session; an identifier identifying the access via which the other device is registered; an identifier identifying the type of access; an identifier identifying the radio access technology of the access; a combination of a source IP address, a destination IP address, a source port number, a destination port number, and a protocol of the multi-access data session; an identifier identifying the mobile network in which the access path is located (or to which it belongs); and an identifier identifying the network operator of the mobile network in which the access path is located (or to which it belongs).

[0048] The identifier identifying the network may include at least one of the following: an identifier identifying a public land mobile network; an identifier identifying an independent non-public network.

[0049] The components may also be used for: receiving, from another device, a request for the establishment of a multi-access data session via at least two accesses operating according to the first criterion, or at least two accesses operating according to the additional criterion; and based on the received request, establishing a multi-access data session via at least two access networks operating according to the first criterion or at least two accesses operating according to the additional criterion.

[0050] The components may also be used for: receiving a request to register another device to the mobile network via at least two accesses operating according to the first criterion, or at least two accesses operating according to the additional criterion; and based on the received request, registering the other device to the mobile network via at least two accesses operating according to the first criterion, or at least two accesses operating according to the additional criterion.

[0051] The policy may include a user equipment routing policy, and the policy information may be a routing descriptor component type identifier that includes a preference regarding on which access paths from a plurality of access paths of a communication network the multi-access data session will be established.

[0052] The routing descriptor component type identifier may include an octet indicating the number of multi-access preference fields, followed by octets of multi-access preference fields, where the octets of multi-branch preference fields may include at least one of the following: an indicator indicating the type of access; an indicator indicating the radio access technology; a registration identity corresponding to registration to a mobile network via the access; an indicator indicating a preference for selecting a public land mobile network or an independent non-public network; and an indicator indicating a preference for prohibiting the selection of a public land mobile network or an independent non-public network.

[0053] The component for sending policies to another device may be a component for sending policy information via one of the following: control plane signaling; and user plane signaling.

[0054] The policy information may include user subscription information indicating that a multi-access data session can be requested to be established by another device via at least one of the following: a defined type of access; and a defined radio access technology, where the multi-access data session is for at least one of the following: defined single network slice selection assistance information; and a defined data network name.

[0055] The component may also be used to: receive a request for release of at least one of the selected at least two access paths for a multi-access data session; and authorize the release of at least one of the selected at least two access paths for a multi-access data session.

[0056] According to a fifth aspect, there is provided a device for a mobile network, the device including 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 device to at least perform: receiving a policy including policy information indicating a preference regarding which access paths from a plurality of access paths will be established for a multi-access data session for application traffic, the plurality of access paths being at least two accesses operating according to a first criterion or at least two accesses operating according to another criterion; selecting at least two access paths from the plurality of access paths for the multi-access data session based on the policy information; and requesting establishment of the multi-access data session via the selected at least two access paths, the selected at least two access paths being at least two accesses operating according to a first criterion or at least two accesses operating according to another criterion.

[0057] The at least two accesses operating according to the first criterion may be 3GPP accesses, and the at least two accesses operating according to the other criterion may be non-3GPP accesses.

[0058] For each access path, policy information indicating preferences regarding which access paths from among multiple access paths will be established for a multi-access data session for application traffic may include at least one of the following: a description of the application traffic using the multi-access data session; an identifier identifying the access path via which the device is registered with the communication network; an identifier identifying the type of access; an identifier identifying the radio access technology of the access; a combination of the source IP address, destination IP address, source port number, destination port number, and protocol of the multi-access data session; an identifier identifying the mobile network in which the access path is located (or to which it belongs); and an identifier identifying the network operator of the mobile network in which the access path is located (or to which it belongs).

[0059] The identifier identifying the network may include at least one of the following: an identifier identifying a public land mobile network; and an identifier identifying an independent non-public network.

[0060] A device caused to select at least two access paths from among multiple access paths for a multi-access data session based on policy information may be caused to perform: selecting at least two access paths from among multiple access paths, where the multiple access paths correspond to the access paths identified within the policy information; and the multiple access paths are registered with the communication network via the device.

[0061] A device caused to select at least two access paths from among multiple access paths for a multi-access data session based on policy information may be caused to perform: selecting at least two access paths from among the multiple access paths corresponding to the access paths identified within the policy information.

[0062] A device caused to request the establishment of a multi-access data session over the selected at least two access paths may be caused to perform: requesting registration with the communication network via at least one of the selected at least two access paths; and requesting the establishment of the multi-access data session via at least one of the selected at least two access paths.

[0063] The policy may include a user equipment routing policy, and the policy information may be a routing descriptor component type identifier that includes preferences regarding on which of the multiple access paths from the communication network the multi-access data session will be established.

[0064] The routing descriptor component type identifier may include an octet indicating the number of multi-access preference fields, followed by octets of the multi-access preference fields, where the octets of the multi-branch preference fields may include at least one of the following: an indicator indicating the type of network accessed; an indicator indicating the radio access technology; a registration identity corresponding to registration with the communication network via the access path; an indicator indicating a preference for selecting a public land mobile network or an independent non-public network; and an indicator indicating a preference for prohibiting the selection of a public land mobile network or an independent non-public network.

[0065] The apparatus caused to execute a reception policy may be caused to execute a reception policy information via one of the following: control plane signaling; and user plane signaling, the policy including policy information indicating a preference regarding which access paths from multiple access paths will be established for a multi-access data session for application traffic.

[0066] The policy information may include user subscription information indicating that the multi-access data session can be requested to be established by the apparatus via at least one of the following: a defined type of access network; and a defined radio access technology, where the multi-access data session is for at least one of the following: defined single network slice selection assistance information; and a defined data network name.

[0067] The apparatus may also be caused to execute: request a release of at least one of the selected at least two access paths for a multi-access data session.

[0068] The apparatus caused to execute a request for a release of one of the selected at least two access paths for a multi-access data session may be caused to execute: request a release of the at least one of the selected at least two access paths based on determining a substantial loss of connectivity of the at least one of the selected at least two access paths.

[0069] According to a sixth aspect, there is provided an apparatus for a communication network, the apparatus including 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 at least execute: generate a policy, the policy including policy information indicating a preference regarding which access paths from multiple access paths will be established for a multi-access data session for application traffic, the multiple access paths being via at least two accesses operating according to a first criterion, or at least two accesses operating according to an additional criterion; and send the policy to another apparatus registered with the mobile network.

[0070] At least two access networks operating according to a first criterion can be 3GPP accesses, and at least two accesses operating according to another criterion can be non-3GPP accesses.

[0071] For each access path, the policy information indicating a preference regarding which access paths from among multiple access paths will be established for a multi-access data session for application traffic can include at least one of the following: a description of the application traffic using the multi-access data session; an identifier identifying the access via which the device is registered; an identifier identifying the type of access; an identifier identifying the radio access technology of the access; a combination of a source IP address, a destination IP address, a source port number, a destination port number, and a protocol of the multi-access data session; an identifier identifying the mobile network; and an identifier identifying the network operator of the mobile network.

[0072] The identifier identifying the mobile network can include at least one of the following: an identifier identifying a public land mobile network; an identifier identifying an independent non-public network.

[0073] The apparatus can also be caused to perform: receiving a request for establishment of a multi-access data session via at least two access networks operating according to a first criterion, or at least two access networks operating according to another criterion, from another apparatus; and based on the received request, establishing the multi-access data session via at least two access networks operating according to a first criterion, or at least two access networks operating according to another criterion.

[0074] The apparatus can also be caused to perform: receiving a request for registering another apparatus to a communication network via at least two access networks operating according to a first criterion, or at least two access networks operating according to another criterion; and based on the received request, registering another apparatus to the communication network via at least two access networks operating according to a first criterion, or at least two access networks operating according to another criterion.

[0075] The policy can include a user equipment routing selection policy, and the policy information can be a routing descriptor component type identifier, and the routing descriptor component type identifier includes: a preference for on which access path among multiple access paths from a communication network the multi-access data session will be established.

[0076] The routing descriptor component type identifier may include an octet indicating the number of multi-access preference fields, followed by octets of the multi-access preference fields, where the octets of the multi-branch preference fields may include at least one of the following: an indicator indicating the type of access network; an indicator indicating the radio access technology; a registration identity corresponding to registration to the communication network via the access network; an indicator indicating a preference for selecting a public land mobile network or an independent non-public network; and an indicator indicating a preference for prohibiting the selection of a public land mobile network or an independent non-public network.

[0077] The apparatus caused to perform sending a policy to another device may be caused to perform a component for sending policy information via one of the following: control plane signaling; and user plane signaling.

[0078] The policy information may include user subscription information indicating that a multi-access data session can be requested to be established by another device via at least one of the following: a defined type of access network; and a defined radio access technology, where the multi-access data session is for at least one of the following: defined single network slice selection assistance information; and a defined data network name.

[0079] The apparatus may also be caused to perform: receiving a request for release of at least one access path among at least two selected access paths for a multi-access data session; and authorizing the release of at least one access path among at least two selected access paths for a multi-access data session.

[0080] According to a seventh aspect, there is provided an apparatus for a mobile network, the apparatus including: a component for receiving a policy, the policy including policy information indicating a preference regarding which access paths from multiple access paths will be established for a multi-access data session for application traffic, the multiple access paths being at least two accesses operating according to a first criterion, or at least two accesses operating according to another criterion; a component for selecting at least two access paths from the multiple access paths for the multi-access data session based on the policy information; and a component for requesting establishment of a multi-access data session including the selected at least two access paths, the selected at least two access paths being at least two accesses operating according to a first criterion, or at least two accesses operating according to another criterion.

[0081] According to an eighth aspect, there is provided an apparatus for a mobile network, the apparatus comprising: means for generating a policy, the policy including policy information that indicates a preference regarding which access paths from a plurality of access paths will be established for a multi-access data session for application traffic, the plurality of access paths being at least two accesses operating according to a first criterion, or at least two accesses operating according to an additional criterion; and means for sending the policy to another apparatus registered with the mobile network.

[0082] According to a ninth aspect, there is provided an apparatus for a mobile network, the apparatus comprising: receiving circuitry configured to receive a policy, the policy including policy information that indicates a preference regarding which access paths from a plurality of access paths will be established for a multi-access data session for application traffic, the plurality of access paths being at least two accesses operating according to a first criterion, or at least two accesses operating according to an additional criterion; selection circuitry configured to select, based on the policy information, at least two access paths from the plurality of access paths for the multi-access data session; and request circuitry configured to request establishment of the multi-access data session including the selected at least two access paths, the selected at least two access paths being at least two accesses operating according to a first criterion, or at least two accesses operating according to an additional criterion.

[0083] According to a tenth aspect, there is provided an apparatus for a mobile network, the apparatus comprising: generating circuitry configured to generate a policy, the policy including policy information that indicates a preference regarding which access paths from a plurality of access paths will be established for a multi-access data session for application traffic, the plurality of access paths being at least two accesses operating according to a first criterion, or at least two accesses operating according to an additional criterion; and sending circuitry configured to send the policy to another apparatus registered with the mobile network.

[0084] According to an eleventh aspect, there is provided a computer program [or a computer-readable medium including instructions] for causing a device for a communication network to perform at least the following: receiving a policy that includes policy information indicating a preference regarding which access paths from among a plurality of access paths will be established for a multi-access data session for application traffic, the plurality of access paths being at least two accesses operating according to a first criterion, or at least two accesses operating according to an additional criterion; selecting, based on the policy information, at least two access paths from among the plurality of access paths for the multi-access data session; and requesting establishment of the multi-access data session including the selected at least two access paths, the selected at least two access paths being at least two accesses operating according to a first criterion, or at least two accesses operating according to an additional criterion.

[0085] According to a twelfth aspect, there is provided a computer program [or a computer-readable medium including instructions] for causing a device for a mobile network to perform at least the following: generating a policy that includes policy information indicating a preference regarding which access paths from among a plurality of access paths will be established for a multi-access data session for application traffic, the plurality of access paths being at least two accesses operating according to a first criterion, or at least two accesses operating according to an additional criterion; and sending the policy to another device registered with the mobile network.

[0086] According to a thirteenth aspect, there is provided a non-transitory computer-readable medium including program instructions for causing a device for a communication network to perform at least the following: receiving a policy that includes policy information indicating a preference regarding which access paths from among a plurality of access paths will be established for a multi-access data session for application traffic, the plurality of access paths being at least two accesses operating according to a first criterion, or at least two accesses operating according to an additional criterion; selecting, based on the policy information, at least two access paths from among the plurality of access paths for the multi-access data session; and requesting establishment of the multi-access data session including the selected at least two access paths, the selected at least two access paths being at least two accesses operating according to a first criterion, or at least two accesses operating according to an additional criterion.

[0087] According to a fourteenth aspect, a non-transitory computer-readable medium is provided, including program instructions for causing a device for a mobile network to perform at least the following: generating a policy that includes policy information indicating a preference regarding which access paths from a plurality of access paths will be established for a multi-access data session for application traffic, the plurality of access paths being at least two accesses operating according to a first criterion, or at least two accesses operating according to an additional criterion; and sending the policy to another device registered with the mobile network.

[0088] A device includes components for performing the actions of the method as described above.

[0089] A device is configured to perform the actions of the method as described above.

[0090] A computer program includes program instructions for causing a computer to perform the method as described above.

[0091] A computer program product stored on a medium can cause a device to perform the method described herein.

[0092] According to one aspect, a non-transitory computer-readable medium is provided, including program instructions for causing a device to at least perform the method according to any of the foregoing aspects.

[0093] In the foregoing, many different embodiments have been described. It should be understood that further embodiments can be provided by any combination of two or more of the above-described embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0094] Embodiments will now be described by way of example only with reference to the drawings, in which:

[0095] Figure 1 A representation of a mobile network according to some example embodiments is shown;

[0096] Figure 2 A representation of a device implementing one or more network functions of a core network according to some example embodiments is shown;

[0097] Figure 3 A representation of a device according to some example embodiments is shown;

[0098] Figure 4 A flowchart showing the establishment of a process for a multi-data session including a plurality of branches through multi-access of the same access type in a mobile network according to an example embodiment is shown;

[0099] Figure 5Shows a flowchart for establishing a process for a multi-data session including multiple branches through multi-access of the same access type in a mobile network according to some other example embodiments; and

[0100] Figure 6 Shows a flowchart for establishing a process for a multi-data session including multiple branches through multi-access of the same access type in a mobile network according to another example embodiment. Detailed implementation

[0101] Hereinafter, certain embodiments are explained with reference to a device capable of communicating with a communication system serving such a device. Before explaining the exemplary embodiments in detail, certain general principles of a communication system (e.g., a 5G communication system that can include one or more access networks (ANs) and a core network) and a device (e.g., a terminal served by the communication system) are briefly explained with reference to Figure 1 、 Figure 2 and Figure 3 to assist in understanding the technology on which the examples are based.

[0102] Figure 1 Shows a schematic diagram of a mobile network according to an example embodiment of the present disclosure. The mobile network includes components of a 5G wireless communication system (5GS) and an evolved packet system (EPS). The 5GS can be composed of an access network (AN) and a 5G core network (5GC). The access network of the 5GS can include 3GPP access networks, such as a 5G radio access network (5G-RAN), also known as a next-generation radio access network (NG-RAN). The 5G-RAN or NG-RAN can include a terrestrial network (TN) and / or a non-terrestrial network (NTN). The AN of the 5GS can alternatively include a non-3GPP access network. Examples of the non-3GPP access network 103 include: an untrusted wireless local area network (WLAN) capable of accessing the 5GC via a non-3GPP interworking function (N3IWF), a trusted WLAN accessing the 5GC via a trusted non-3GPP gateway function (TNGF), and a wired network accessing the 5GC via a wired access gateway function (W-AGF).

[0103] In some embodiments, an AF that is a customer of the 5GC is connected to the user plane function (UPF) of the 5GC via a DN and is connected to various network functions (NFs) of the 5GC via the network exposure function (NEF) of the 5GC. In some embodiments, the AF is a trusted application function, so the trusted AF is implemented in the 5GC and is directly connected to other NFs of the 5GC. It will be noted that although only one UPF is shown in Figure 1Shown in, but 5GS can be composed of a UFP chain that includes a UPF anchor point connected to the DN. The AF can send and receive control plane signaling to and from various NFs of the 5GC directly or via the NEF. The AF can also send and receive user plane traffic to and from the anchor UPF of the 5GC via the DN. Figure 1 The connections between the elements drawn in are via the interfaces defined in 3GPP standards TS23.501 and 23.502. As Figure 1 The mobile network shown can also include components of the EPC, including another access network (AN) 105, such as a 4G radio access network (commonly referred to as E-UTRAN). The E-UTRAN is connected to the MME (Mobility Management Entity) of the EPC of the mobile network. The MME sends control plane signaling that enables low-level connection management. The MME communicates with the eNodeB of the AN 105 using the S1-MME interface. The MME is responsible for, for example, NAS layer signaling (non-access stratum), user authentication and authorization, supporting the connection of a terminal (e.g., UE) to the EPC, setting up and managing bearers, selecting the PGW and SGW for a given connection, selecting a different MME when switching between eNodeBs, TA (Tracking Area) management, roaming support, and the SGW. Additionally, in Figure 1 The SGW (Serving Gateway) is also shown, which transfers user plane traffic from another AN 105 (e.g., E-UTRAN) to the UPF via the SGW. The SGW is responsible for routing user plane traffic, forwarding user plane traffic, packet marking and buffering of packets, user mobility management, and switching connections between two eNodeBs.

[0104] The 5GC can include, for example, the following network functions (NFs) (otherwise known as network entities): Network Slice Selection Function (NSSF); Network Exposure Function (NEF); Network Repository Function (NRF); Network Data Analytics Function (NWDAF), Policy Control Function (PCF); Unified Data Management (UDM); Authentication Server Function (AUSF); Access and Mobility Management Function (AMF); Session Management Function (SMF), and User Plane Function (UPF). The NFs of the 5GC can have a service-based architecture as described in 3GPP standard TS23.501. The NF services that can be provided by the NFs of the 5GC and the service-based interfaces for the NFs of the 5GC are described in 3GPP standards, particularly in 3GPP standards TS23.501 and 23.502.

[0105] A terminal such as Figure 1The terminal (e.g., UE) in it can support (i.e., be capable of) registering with the 5GC of the mobile network through one or more accesses using a registration process. When the terminal (e.g., UE) triggers a registration process to register with the 5GC through an access, the terminal (e.g., UE) generates a registration request to register with the 5GC and sends the registration request to the access network. The access network sends the received registration request together with an indication of the access type of the access network to the AMF of the 5GC. The access type can be 3GPP access or non-3GPP access. Thus, the indication of the access type sent by the access to the AMF indicates to the AMF that the terminal (e.g., UE) is registering with the AMF of the 5GC through a 3GPP access network or a non-3GPP access network. When the AMF of the 5GC accepts the UE's registration request and registers the terminal (e.g., UE) with the 5GC, the AMF responds to the registration request with a registration acceptance message. The registration acceptance message indicates that the terminal (e.g., UE) has been registered with the mobile network through the access. In some embodiments, the registration request can be a NAS signaling message or can be included in a NAS signaling message, and the registration acceptance can be a NAS signaling message or can be included in a NAS signaling message. The registration request can include an indication of the capabilities of the terminal (e.g., UE), an indication of the network slice to be accessed, and an identifier of the terminal (e.g., UE).

[0106] In Figure 1 In the example shown, when the terminal (e.g., UE) triggers a registration process to register with the AMF of the 5GC of the mobile network, the terminal (e.g., UE) sends a registration request to the 3GPP access network 101 (e.g., 5G Radio Access Network (5G-RAN) (also known as Next Generation Radio Access Network (NG-RAN))), and the 3GPP access network 101 sends the registration request together with an indication of the access type of the 3GPP access network 101 to the AMF, as described above. The 5G-RAN (otherwise known as NG-RAN) can include one or more base stations (e.g., gNodeB (gNB)). The gNB of the 5G-RAN can include a gNB distributed unit connected to the gNB central unit and a remote radio head connected to the gNB distributed unit. The 5G-RAN can also include NTN, which includes a plurality of satellites that can be located in various orbits, such as Low Earth Orbit (LEO), Medium Earth Orbit (MEO), and Geostationary Orbit (GEO). The AMF accepts the terminal (UE) registration request and sends a registration acceptance message to the terminal (e.g., UE), and the registration acceptance message indicates that the terminal (e.g., UE) has been registered with the AMF through 3GPP access. In the present disclosure, a terminal (e.g., UE) registered through 3GPP access refers to a terminal (e.g., UE) that registers with the AMF of the 5GC via a 3GPP access network. The 3GPP access network can employ any radio access technology, such as 3G, LTE, NTN, or 5G (otherwise known as NR).

[0107] In some embodiments, a terminal (e.g., a UE), such as Figure 1 the terminal (e.g., a UE) shown in, may support (i.e., be capable of) registering with the MME of a mobile network via 3GPP access. In these embodiments, the terminal (e.g., a UE) may register with the MME via 3GPP access by sending a registration request to the MME via a connection between the 3GPP access network 105 (e.g., E-UTRAN) and the MME. The 3GPP access network 105 (e.g., E-UTRAN) may include one or more base stations (e.g., evolved Node B, also referred to as eNodeB (eNB)).

[0108] In addition, the terminal (e.g., a UE) may support (i.e., be capable of) registering with the AMF of the 5GC via non-3GPP access. In these embodiments, the terminal (e.g., a UE) may register with the AMF of the 5GC via non-3GPP access by sending a registration request to the AMF via an access path that includes the non-3GPP access network 103, an interworking function, connections between the non-3GPP access network 103 and the interworking function, and the interworking function and the AMF. The non-3GPP access network 103 may be any wireless or wired access network. The interworking function may be N3IWF, TNFG, or W-AGF. In this specification, a terminal (e.g., a UE) registered via non-3GPP access refers to a terminal (e.g., a UE) that registers with the AMF of the 5GC via a non-3GPP access network and an interworking function (e.g., N3IWF, TNFG, or W-AGF).

[0109] 5GS supports certain functions to provide multi-access data connectivity to a UE at a higher layer of the 5G protocol stack (in other words, in layers above the media access control layer). In other words, 5GS supports (i.e., is capable of) establishing a data session via multi-access (i.e., a multi-access data session via more than two accesses) in order to simultaneously exchange user plane traffic between a terminal (e.g., a UE) and a data network (DN). However, current 3GPP specifications limit 5GS to providing a function to the 5GC that only supports establishing a multi-access data session via one 3GPP access and one non-3GPP access.

[0110] A process is desired for the establishment of a multi-access data session (e.g., a multi-access PDU session) that provides a PDU connectivity service capable of accessing more than one 3GPP access network and / or more than one non-3GPP access network simultaneously (either in one mobile network or in two different mobile networks). In other words, a process is desired for the establishment of a multi-access data session that includes multiple legs over multiple 3GPP accesses or multiple non-3GPP accesses, where the multiple 3GPP accesses can have the same radio access technology (RAT) or different RATs.

[0111] In some embodiments, the process for the establishment of a multi-access data session that includes multiple legs over multiple accesses of the same access type includes the terminal (e.g., UE) requesting the creation of a multi-access data session that includes multiple legs over multiple accesses of the same access type. In this embodiment, one leg of the MA PDU session is established over each of the multiple accesses of the same type. In some embodiments, the process for the establishment of a multi-access data session that includes multiple legs over multiple accesses of the same access type includes: the terminal (e.g., UE) requesting the modification of an existing PDU session that includes one leg over one access of an access type to establish another leg over another access of the same access type as the one access. The establishment of a leg over an access (otherwise referred to as an access path) means that the access network over that access provides end-to-end connectivity between the terminal (e.g., UE) and the user plane function.

[0112] In the following example, the terminal (e.g., UE) can register with the core network over multiple accesses, and the terminal (e.g., UE) can request the establishment of a multi-access data session that includes multiple legs over at least two accesses of the same access type (or the same radio access technology (RAT)).

[0113] In the first example, the terminal (e.g., UE) registers with the core network over a first access that includes a 5G non-terrestrial access network (e.g., 3GPP NTN), which can be part of a first mobile network (e.g., PLMN1). The terminal (e.g., UE) also registers with the core network over a second access that includes a 5G terrestrial access network (e.g., 3GPP NG-RAN), which is part of the same mobile network (PLMN1) of which the first access is a part. In this first example, the first access and the second access are in the same mobile network, have the same access type (3GPP access), and have different RATs (NTN and NR).

[0114] In a second example, a terminal (e.g., a UE) registers with a core network via a first access that includes a 5G terrestrial access network (e.g., 3GPP NG-RAN), which is part of a first mobile network (e.g., PLMN1). The terminal (e.g., a UE) also registers with the core network via a second access that includes an LTE terrestrial access network (e.g., 3GPPE-UTRAN), which is part of the same mobile network (PLMN1). In this example where the first access and the second access are in the same mobile network, they have the same access type (3GPP access) and different RATs (NR and LTE).

[0115] In a third example, a terminal (e.g., a UE) registers with a core network via a first access that includes a 5G terrestrial access network (e.g., 3GPP NG-RAN), which is part of a first mobile network (PLMN1). The terminal (e.g., a UE) also registers with the core network via a second access that includes a 5G terrestrial access network (e.g., 3GPP NG-RAN), which is part of a second mobile network (PLMN2). In this example, the first access and the second access are in different mobile networks and have the same access type (3GPP access) and the same RAT (NR).

[0116] In a fourth example, a terminal (e.g., a UE) registers with a core network via a first access that includes a non-3GPP access network and an N3IWF, both of which are part of a first network (PLMN1). The terminal (e.g., a UE) also registers via a second access that includes a non-3GPP access network and another N3IWF that is part of a second network (PLMN2). In this fourth example, the first access and the second access are in two different mobile networks and have the same access type (non-3GPP access).

[0117] Other examples can include procedures for establishing a multi-access data session that includes multiple legs via multiple accesses, where the multiple accesses have the same access type, different access types, and / or the same or different RATs. For example, a procedure for establishing a multi-access data session that includes multiple legs via multiple accesses can result in a multi-access data session that includes two legs via two 3GPP accesses, where the two 3GPP accesses have the same RAT (e.g., NR and NR or NTN and NTN) or different RATs (e.g., NR and LTE).

[0118] Enable the UE to request the establishment of a multi-access data session including multiple branches through multiple different accesses, where the accesses have different access types and different RATs, which can improve the transmission of user plane traffic from the UE to the data network, because the established MAPDU session will have multiple branches through varying accesses, through which the user plane traffic is sent to the data network. Additionally, the establishment of a multi-access data session including multiple branches through multiple accesses with various different RATs and access types can improve network resource utilization. This utilization can be measured in terms of resources and performance metrics associated with the access network of the access, such as capacity (defining how much resources (such as available bandwidth) remain unutilized), coverage (defining the boundaries or scope or area within which the UE can access the (multiple) mobile network), reliability (defining the credibility of the access network), and quality of experience (QoE) (which can be a multi-factor-based measurement of the access network, including factors such as reliability, capacity, network latency, throughput, etc.). Network resources and performance metrics such as the above are explained in more detail in documents such as 3GPP TS23.501, TS23.502, TS24.501, TS24.526, and TS24.501.

[0119] An actual example of improving the transmission of user plane traffic from the UE to the data network can be railway communication that requires extremely high communication reliability.

[0120] For example, when a UE registers with a core network of a mobile network (e.g., a PLMN) via a first access (including a first access network that is a terrestrial access network (TN)) and via a second access (including a second access network that is a non-terrestrial network (NTN)), the additional resources available in the second access network (i.e., the NTN) can be used to expand the capacity, or throughput, or both capacity and throughput of the user plane traffic transmitted via the first access network (i.e., the TN), and vice versa. The transmission of user plane traffic via various different access networks, RATs, and access types can be based on the demand for network resources (e.g., for greater network bandwidth, or lower average latency for MA data sessions, etc., or to immediately switch from one leg of an MA data session to another leg of the data session in case of failure or overload via the first access) or to provide temporary coverage (e.g., to increase or enhance network capacity in case of an emergency). For example, a terminal (e.g., a UE) located in a train, cruise ship, or aircraft that is arriving at a layover where dual coverage from the NTN and TN is available (which is typically served by the NTN) can be configured to use traffic aggregation to lower the average latency or increase the bandwidth of a (multi-access) data session. Another example could be when a terminal (e.g., a UE) is located in a car that is typically served by the TN and the car gets stuck in a traffic jam after a severe accident. In this example, the terminal (e.g., a UE) can enable the transmission of user plane traffic via various different legs of a multi-access data session by using traffic aggregation between the TN and an additional access network such as the NTN to ensure that the bandwidth for the multi-access data session does not drop to an unacceptable level (since a large number of other terminals (e.g., UEs in other cars) are in the same physical area as the terminal (e.g., the UE)).

[0121] Another example would be the ability for a UE or a UPF, or both the UE and the UPF, to use traffic aggregation for user plane traffic received via multiple legs of multiple accesses, where each access includes satellite access (in the same or different mobile networks (e.g., a PLMN)). In other words, there are two or more accesses in the same or different mobile networks provided by two or more different satellite constellations or satellite access networks. For example, this can provide expanded bandwidth or throughput, or both bandwidth and throughput, when compared to a single leg including a single satellite access network. Additionally, in some examples, different types of satellite access networks can be employed to provide, for example, application latency or delay (e.g., by switching from a GEO access network to an LEO access network to reduce latency) or coverage improvement (e.g., by switching from an LEO access network to a GEO access network to prevent coverage or access loss, since LEO satellite coverage can change significantly over time as satellites in the satellite access network rise above and fall below the horizon, while GEO satellites provide constant accessibility).

[0122] Another example of an improvement that can be implemented based on the embodiments discussed herein can be a dual terrestrial access network example, where a wide area access network (e.g., which can be a designated PLMN1 or NPN1) is deployed in a first mobile network, and a local access network (e.g., which can be designated as PLMN2 or NPN2) is deployed in a second mobile network for a specific area or venue (e.g., in a stadium). In this example, during high data traffic events, the available resources from the local access network in the second mobile network (PLMN2 or NPN2) can be used to provide additional capacity to the wide area access network in the first mobile network (PLMN1 or NPN1), and vice versa. This example can be applied to other environments, such as campuses, enterprises, factories, and homes.

[0123] Figure 2 An example of an apparatus 200 that can implement one or more NFs of the Figure 1 illustrated 5GC is shown. The apparatus 200 may include at least one random access memory (RAM) 211a, at least one read only memory (ROM) 211b, at least one processor 212, processor 213, and a network interface 214. The at least one processor 212, processor 213 may be coupled to the RAM 211a and the ROM 211b. The at least one processor 212, processor 213 may be configured to execute software code 215. The software code 215 may include, for example, instructions for performing actions or operations of one or more NFs of the 5GC, including actions or operations of a policy control function (PCF). In some embodiments, the software code 215 may include actions or operations for generating UE policies for UEs registered with the 5GC. The UE policies include access traffic steering, switching, splitting (ATSSS) rules and UE routing selection policies. The software code 215 may be stored in the ROM 211b. The apparatus 200 may implement one or more NFs of the 5GC and may be interconnected with another apparatus 200 that implements one or more other NFs of the 5GC. In such an embodiment, the apparatus 200 may be part of a distributed computing system. In some embodiments, each NF of the 5GC may be implemented on a single apparatus 200. In such an embodiment, the apparatus 200 may be a cloud computing system.

[0124] Figure 3 An example of Figure 1An example of the apparatus 300 is shown. The apparatus 300 can be any wireless communication device capable of sending and receiving radio signals. Non-limiting examples of the apparatus 300 include a terminal, a wireless communication device, a user equipment (UE), a mobile station (MS), or a mobile device (such as a mobile phone or a so-called "smartphone"), a computer provided with a wireless interface card or other wireless interface facilities (e.g., a USB dongle), a personal data assistant (PDA) or a tablet computer provided with wireless communication capabilities, a machine type communication (MTC) device, an Internet of Things (IoT) communication device, or any combination of these devices, etc. In the following discussion, the examples generally relate to user equipment, but it should be understood that the same principles can be applied to the examples of any of the above apparatuses.

[0125] The apparatus 300 can be configured to communicate with a base station of an access network such as 5G-RAN and 5GC via non-access stratum (NAS) signaling through a base station of an access network such as 5G-RAN and 5GC (e.g., an NG-eNB or a gNB) of the 5G-RAN, for example, for the communication of data. Additionally, in some embodiments, the apparatus 300 can be configured to communicate with other access network nodes (e.g., satellites (NEO, MEO, or GEO) of NT-AN).

[0126] The communication can include or carry one or more of voice, email, text messages, multimedia, data, machine data, etc.

[0127] The apparatus 300 can receive wireless signals (e.g., radio or cellular signals) via an air interface or a radio interface 307 (commonly referred to as the Uu interface) through a suitable apparatus 306 for receiving wireless signals, and can send wireless signals (e.g., radio or cellular signals) via a suitable apparatus for sending wireless signals. In Figure 3 this case, the apparatus 306 includes one or more antennas (or an antenna array including multiple antennas) and a transceiver, and is schematically designated by block 306. The apparatus 306 can be provided, for example, by radio components and an associated antenna arrangement including one or more antennas. The antenna arrangement can be arranged inside or outside the mobile device.

[0128] The apparatus 300 may include at least one processor 301, at least one memory ROM 302a, at least one RAM 302b, and other possible components 303 for assisting in performing, in software and hardware, the tasks it is designed to perform, including controlling access to and communication with an access network (such as a 5G-RAN access network or an NTN access network) and other apparatuses 300. The at least one processor 301 is coupled to the RAM 311a and the ROM 311b. The at least one processor 301 may be configured to execute appropriate software code 308. The software code 308 may include, for example, instructions that, when executed by the at least one processor 301, perform one or more actions or operations of this aspect. For example, the software code can include instructions suitable for implementing one or more actions or operations in accordance with the aspects of the present disclosure. The software code 308 may be stored in the ROM 311b.

[0129] The at least one processor 301, the memory, and other related apparatuses can be provided on a suitable circuit board or chipset, or on a circuit board and a chipset. This feature is represented by the reference numeral 304. The terminal 300 may optionally have a user interface, such as a keyboard 305, a touch-sensitive display screen or touchpad, a combination thereof, etc. Optionally, depending on the type of device, one or more displays, speakers, and microphones may be provided.

[0130] The following example explains the process of establishing a multi-access data session in one or more mobile networks, the multi-access data session including multiple branches through multiple accesses of the same access type (e.g., multiple branches through multiple 3GPP accesses and / or multiple branches through multiple non-3GPP accesses). In the following example, the policy control function (PCC) of the core network (e.g., 5GC) of the mobile network provides a UE policy to a terminal (e.g., UE), the UE policy including UE policy information that is used by the terminal (e.g., UE) when the terminal (e.g., UE) requests the establishment of a multi-access data session (e.g., MA PDU session) including multiple branches through multiple 3GPP accesses and / or multiple non-3GPP accesses. In addition, the following example describes how the terminal (e.g., UE) determines which accesses from those accesses to which the UE is registered to request the establishment of a multi-access data session including multiple branches. Additionally, in the following example, the terminal (e.g., UE) is capable of determining whether there is a dependency between the branches of the multi-access data session (in other words, whether there is a dependency between multi-access data sessions because of information indicating a dependency between branches, including branches through access pairs or groups of branches).

[0131] Additionally, in the following examples, a terminal (e.g., a UE) may determine whether there are any conflicts among UE policy information used by the UE to determine which accesses to employ to request the establishment of a multi-access data session (e.g., a MA PDU session), where the multi-access data session includes multiple accesses and ATSSS rules provided by the PCF.

[0132] In some embodiments, the core network (5GC) of a mobile network is configured to provide a UE policy to the UE, where the UE policy includes UE policy information that indicates preferences regarding which legs of a multi-access data session are to be established for a particular application traffic. In some embodiments, the UE policy information includes information regarding each leg of the multi-access data session that should be established. In some embodiments, the UE policy information includes a description of each leg of the multi-access data session that should be established.

[0133] When a terminal (e.g., a UE) requests the establishment of a multi-access data session, the UE policy information may be adopted (or used) by the terminal (e.g., the UE). When (e.g., the UE) requests the establishment of a multi-access data session, the terminal (e.g., the UE) requests the establishment of a multi-access data session that includes only the legs indicated in the UE policy information. For example, preferences regarding which legs (access paths) of a multi-access data session are to be established for a particular application traffic may be represented using a 5-tuple; which is an address; source IP port number; destination IP port number; and protocol). In this example, the UE requests the establishment of a multi-access data session that includes a leg established via NR, a leg established via LTE, and a leg established via non-3GPP access, but no leg established via NTN.

[0134] In some embodiments, the UE policy information includes information regarding each leg of a plurality of access data sessions that should be established. In some embodiments, the information regarding each leg of the plurality of access data sessions that should be established includes information indicating the access type of the access on which the corresponding leg is established and the RAT of the access. In some embodiments, the UE policy information includes an identifier of the mobile network (e.g., network ID) in which the access is located. The network ID may be a PLMNID or an SNPNID. Alternatively or additionally, in some embodiments, the information regarding each leg of the multi-access data session that should be established further includes a registered identifier (e.g., a registration ID) that identifies the registration corresponding to the access on which the leg is established.

[0135] Thus, in some embodiments, subject to the core network being able to establish a branch (access path) (e.g., the access network to which the branch is established has a scope for the UE or the UE has a corresponding access to the access network), the UE is configured to request the establishment of a multi-access data session (e.g., a MA PDU session), the multi-access data session including multiple branches (access paths) through multiple accesses of the same access type, wherein the multiple branches (access paths) correspond to the branches indicated in the UE policy information received from the core network of the mobile network.

[0136] In some embodiments, the UE can be configured to request the establishment of a multi-PDU session, the multi-PDU session including multiple branches corresponding to the accesses indicated in the UE policy information and the accesses for which the UE has registered.

[0137] In some other embodiments, the UE policy information can also be adopted (or used) by the terminal (e.g., the UE) to determine whether to trigger, initiate, or request a new registration of the terminal (e.g., the UE) with the core network of the mobile network through an access for which the terminal (e.g., the UE) has not yet registered and which is indicated in the UE policy information.

[0138] In some embodiments, the UE policy information can be provided in a User Equipment Routing Selection Policy (URSP) rule.

[0139] However, in some embodiments, the UE policy information can be provided to the UE in some other way, such as via control plane signaling or via user plane signaling. In some embodiments, the UE policy information can be provided via a policy transmitted by the PCF on the control plane (e.g., NAS messages exchanged between the UE and the AMF). In some embodiments, the UE policy information can be provided in a policy other than URSP.

[0140] In some embodiments, the user subscription information associated with the terminal (e.g., the UE) includes information indicating that the terminal (e.g., the UE) can request the establishment of a multi-access data session regardless of whether it is for a single Network Slice Selection Assistance Information (S-NSSAI) or for a Data Network Name (DNN), such as a multi-access session including multiple branches through multiple accesses of the same access type (e.g., through multiple 3GPP accesses or through multiple non-3GPP accesses). In addition, in some embodiments, the user subscription information associated with the terminal (e.g., the UE) includes information indicating the access type of the branches of the multi-access data session that may be established.

[0141] Thus, for example, the policy information can include an indication of whether a leg of a multi-access data session can be established via access in a mobile network (PLMN or SNPN) or via access in two different mobile networks (two PLMNs, one PLMN and one SNPN, or two SNPNs).

[0142] Additionally, in some embodiments, a terminal (e.g., a UE) may request the release of a leg of a multi-access data session. In these embodiments, when it is detected based on measurements that the terminal (e.g., a UE) is no longer able to communicate with the access network of the access via which the leg was established (e.g., the terminal (e.g., a UE) is outside the coverage area of the access network of the access via which the leg was established), the terminal (e.g., a UE) may initiate a process to modify the multi-access data session to release the leg of the multi-access data session.

[0143] A first example of a flowchart showing a process for establishing a multi-data session including multiple legs via multiple accesses of the same access type in a mobile network is shown in Figure 4 In this example, the policy information is provided within the URSP sent by the PCF 408 (PLMN1) of the mobile network to the terminal (such as the UE 300 shown in Figure 4 In other words, in this example, the UE 300 receives the URSP including the policy information from the PCF 408. The policy information includes information indicating preferences regarding which legs should be established via which accesses for the multi-access data session. In this example, the UE 300 is able to establish a multi-access data session (e.g., a MA PDU session) that includes a first leg via a first access (3GGP access 1) and a second leg via a second access (3GPP access 2), where the first access includes a first access network (shown as 3GPP1 (NG-RAN) 401) belonging to the mobile network (PLMN1), and the second access includes a second access network (shown as 3GPP2 (E-UTRAN) 402) also belonging to the mobile network (PLMN1). Figure 4 Also shown are the AMF (Access and Mobility Management Function) 404, the MME (Mobility Management Entity) 406, and the PGW-C+SMF (Packet Data Network Gateway and Session Management Function) 410, which are similar to those described above Figure 1 above.

[0144] In Figure 4 the example shown, the UE 300 registers with the AMF 404 via the first access (3GPP access 1) and with the MME 406 via the second access (3GPP access 2) to establish a dual NR or LTE registration with the AMF 404 and the MME 406 of the mobile network (PLMN1).

[0145] This is shown in Figure 4 the "registration" of the UE 300 with the AMF 404 via the first access (3GPP access 1) at 401 and the "registration" of the UE 300 with the MME 406 via the second access (3GPP access 2) at 403. The "registration" of the UE 300 with the AMF 404 via the first access (3GPP access 1) at 401 is a process in which the UE 300 registers with the AMF 404 via the first access (3GPP access 1) via the first access network (3GPP1 (NG-RAN) 400) belonging to the mobile network (PLMN1). The process in which the UE 300 registers with the AMF 404 is described above with respect to Figure 1 the description. In some embodiments, when the UE 300 requests to register with the AMF 404 via the first access (3GPP access 1), the UE 300 may send a registration request to the AMF 404, which includes the identifier of the mobile network (PLMN1) that the UE 300 is requesting to register with and / or an identifier indicating which registration (REG_ID1) in the dual registration is being requested.

[0146] The "registration" of the UE 300 with the MME 406 via the second access (3GPP access 2) at 403 is a process in which the UE 300 registers with the MME 406 via the second access (3GPP access 2) via the second access network (3GPP2 (E-UTRAN) 402) belonging to the mobile network (PLMN1). In some embodiments, when the UE 300 requests to register with the MME 406 via the second access (3GPP access 2), the UE 300 sends a registration request to the MME 406, which includes the identifier of the mobile network (PLMN1) that the UE 300 is requesting to register with and / or an identifier indicating which registration (REG_ID2) in the dual registration is being requested.

[0147] In this example, the PCF 408 can then perform a UE policy management process, as shown at 405. The UE policy management process performed by the PCF 408 can, for example, include (as shown at 407) the PCF 408 sending a UE policy management command message to the UE 300. In this example, the UE policy command sent by the UE 300 includes a URSP, and the URSP includes policy information regarding the preference for the branches for establishing a multi-access data session via the first access (3GPP access 1) and the second access (3GPP access 2).

[0148] The UE 300 can confirm the receipt of the UE policy command message at 409, where the UE sends a UE policy management completion message to the PCF 408.

[0149] Thus, in this example, the PCF 408 is configured to send a URSP including policy information that indicates a preference for establishing a leg for a multi-access data session (e.g., a MA PDU session) via a first access and a second access (3GPP access 1 and 3GPP access 2). In other words, the policy information indicates a preference for establishing a multi-access data session (e.g., a MA PDU session) that includes a first leg via a first access (3GPP access 1) and a second leg via a second access (3GPP access 2). In some embodiments, the policy information may be a URSP rule (or URSP rules).

[0150] Furthermore, the UE 300 is configured to follow the policy information (e.g., URSP rules) included in the URSP as shown at 411. For example, the UE 300 is configured to use the policy information included in the URSP to select the access from which to send a request to establish a leg for a multi-access data session (e.g., a MA PDU session).

[0151] The UE 300 is configured to request the establishment of a multi-access data session (e.g., the same MA PDU session) based on the policy information included in the received URSP, the multi-access data session including a first leg via a first access (3GPP access 1) and a second leg via a second access (3GPP access 2). This is shown at 413, where the process of requesting the establishment of the first leg of a multi-access data session (e.g., a PDU session with PDU session ID = 5) via the first access (3GPP access 1), and at 415, where the UE 300 requests the establishment of a multi-access data session (e.g., a PDU session with PDU session ID = 5) via the second access (3GPP access 2).

[0152] A second example of a process for establishing a multi-data session including multiple legs via multi-access of the same access type in a mobile network is shown in Figure 5 which is shown in. In this example, the policy information is provided within a URSP sent by the PCF 408 of the mobile network (PLMN1) to the terminal (as Figure 5is shown as UE 300). In other words, in this example, the UE receives a URSP including policy information from the PCF 408. The policy information includes information indicating preferences regarding which branches should be established for a multi-access data session (e.g., MA PDU session) via which accesses. In this example, the UE 300 is capable of establishing a multi-access data session (e.g., MA PDU session) that includes: a first branch via a first access (3GGP access 1) that includes a first access network (shown as 3GPP1 (NG-RAN) 401) belonging to a mobile network (PLMN1), a second branch via a second access (3GPP access 2) that includes a second access network (shown as 3GPP2 (E-UTRAN) 402) also belonging to the mobile network (PLMN1), and a third branch via a third access (non-3GGP access) that includes an N3IWF and a third access network (shown as non-3GPP (I3IWF) 500). Figure 5 Also shown is an AMF (Access and Mobility Management Function) 404, an MME (Mobility Management Entity) 406, a PCF (Policy Control Function) 408, and a PGW-C+SMF (Packet Data Network Gateway and Session Management Function) 410 similar to those described above Figure 1

[0153] In Figure 5 the example shown, the UE 300 registers with the AMF 404 via the first access (3GPP access 1), registers with the MME 406 via the second access (3GPP access 2), and registers with the AMF 404 via the third access (non-3GPP access) to establish multiple registrations with the mobile network (PLMN1).

[0154] This is at Figure 5 shown at 401 by the "registration" of the UE 300 with the AMF 404 via the first access (3GPP access 1), at 403 by the "registration" of the UE 300 with the MME 406 via the second access (3GPP access 2), and at 501 by the "registration" of the UE 300 with the AMF 404 via the third access (non-3GPP). The "registration" of the UE 300 with the AMF 404 at 401 via the first access (3GPP access 1) refers to the process in which the UE 300 registers with the AMF 404 via the first access (3GPP access 1) via the first access network (3GPP1 (NG-RAN) 400) belonging to the mobile network (PLMN1). The process in which the UE registers with the AMF 404 has been described above with respect to Figure 1 ​The description is described. In some embodiments, when the UE 300 requests registration with the AMF 404 via the first access (3GPP access 1), the UE 300 may send a registration request to the AMF 404, which includes the identifier of the mobile network (PLMN1) to which the UE 300 is requesting registration and / or an identifier indicating which registration (Reg_ID1) among multiple registrations is being requested.

[0155] The "registration" of the UE 300 with the MME 406 at 403 via the second access (3GPP access 2) refers to the process in which the UE 300 registers with the MME 406 via the second access (3GPP access 2) through the second access network (3GPP2 (E-UTRAN) 402) belonging to the mobile network (PLMN1). In some embodiments, when the UE 300 requests registration with the MME 406 via the second access (3GPP access 2), the UE 300 may send a registration request to the MME 406, which includes the identifier of the mobile network (PLMN1) to which the UE 300 is requesting registration and / or an identifier indicating which registration (Reg_ID2) among multiple registrations is being requested.

[0156] The "registration" of the UE 300 with the AMF 404 at 501 via the third access (non-3GPP access) is the process in which the UE 300 registers with the AMF 404 via the third access (non-3GPP) through the N3IWF and the third access network (non-3GPP (N3IWF) 500) belonging to the mobile network (PLMN1). In some embodiments, when the UE 300 requests registration with the AMF 404 6 via the third access (non-3GPP access), the UE 300 may send a registration request to the AMF 404, which includes the identifier of the mobile network (PLMN1) to which the UE 300 is requesting registration and / or an identifier indicating which registration (Reg_ID3) among multiple registrations is being requested.

[0157] As Figure 5As shown, the PCF 408 can execute a UE policy management process 505 similar to the UE policy management process 405. The UE policy management process 505 can include (as shown at 507) the PCF 408 sending a UE policy command message to the UE 300. The UE policy command message in this example includes a URSP, and the URSP includes policy information that indicates a preference for establishing a multi-access data session (e.g., an MA PDU session) that includes legs only through a first access (3GPP access 1) and a third access (non-3GPP access). In other words, the URSP includes policy information that indicates a preference to prohibit or restrict or not request the establishment of a leg of the multi-access data session (e.g., an MA PDU session) through a second access (3GPP access 2).

[0158] The UE 300 can confirm the receipt of the UE policy command at 509, where the UE 300 sends a UE policy management completion message to the PCF 408.

[0159] Therefore, the PCF 408 in this example is configured to send a new URSP that includes policy information (i.e., multi-access preference information) that indicates a preference for the UE to request the establishment of a multi-access data session (e.g., an MA PDU session) that includes legs only through a first access (3GPP access 1) and a third access (non-3GPP access).

[0160] The UE 300 as shown at 511 is configured to follow the received URSP (i.e., follow the policy information included in the received URSP). For example, the UE 300 is configured to use the policy information included in the URSP to select the access from which to send a request to establish a leg for a multi-access data session (e.g., an MA PDU session).

[0161] The UE 300 is configured to request the establishment of a multi-access data session (e.g., the same MA PDU session) based on the policy information included in the received URSP, and the multi-access data session includes a first leg through a first access (3GPP access 1) and a second leg through a third access (non-3GPP access). This is shown at 413, where the UE requests the establishment of the first leg of the multi-access data session (e.g., a PDU session with PDU session ID = 5) through the access path 3GPP1, and at 515, where the UE requests the establishment of the second leg for the same multi-access data session (e.g., a PDU session with PDU session PDU session ID = 5) through a non-3GPP access path.

[0162] Shows a third example of a flowchart depicting the process for establishing a multi-data session including multiple branches through multi-access of the same access type in a mobile network. In Figure 6 it is shown. In Figure 6 the flowchart shown, operations or actions 401, 403, 405, 407, 409, and 411 are the same operations as those described in the flowchart for Figure 4 and thus will not be elaborated further.

[0163] In Figure 5 the flowchart shown, after a multi-access data session (with PDU session ID = 5) is established (i.e., a multi-access data session including a first branch through a first access (3GPP access 1) and a second branch through the first access (3GPP access 1) is established), UE 300 determines to release one of the two branches of the multi-access data session (e.g., the MA PDU session) based on a suitable trigger event. In this example, the UE determines to release the branch through the first access (3GPP access 1) based on a suitable trigger event. In some embodiments, the trigger event may include: UE 300 detects that it is about to lose coverage from the access network (3GPP1 (NG-RAN 400)) of the first access (3GPP access 1) or has lost coverage from the access network (3GPP1 (NG-RAN 400)) of the first access (3GPP access 1) based on a measurement of the signal strength of the access network (3GPP1 (NG-RAN 400)) of the first access (3GPP access 1).

[0164] In some examples, the trigger event can be coverage-related, such as the NTN or satellite network of the access network (3GPP1 NG-RAN 400) of the first access (3GPP access 1), where the LEO or MEO satellite constellation of the NTN or satellite network cannot provide an appropriate number or distribution of satellites within the reach of the UE antenna beam, and thus UE 300 can determine that the coverage from the NTN or satellite network is lost or degraded below an acceptable bandwidth or reliability measurement, and determines to release the branch of the multi-access data session through the first access (3GPP access 1). In some examples, the trigger event can be capacity-related, where UE 300 determines that one of the branches through the (overloaded) access has become unable to maintain a sufficient bit rate or keep the error rate below a defined threshold error rate. In this example, UE 300 determines to request the release of the branch through the overloaded access (e.g., release the branch of the multi-access data session through 3GGP access 1).

[0165] After the UE 300 releases one of the two branches of a multi-access data session (e.g., a MA PDU session), the UE 300 triggers or initiates a process to release that one branch from the multi-access data session. In Figure 6 the example shown, the UE 300 can trigger or initiate a PDU session release process and request the PGW-C+SMF 410 to release the branch via the first access (3GPP access 1) from the multi-access data session (e.g., a MA PDU session). This is shown at Figure 6 601, where the UE 300 determines to release the branch of the multi-access data session (e.g., a MA PDU session) via the first 3GPP access (3GGP1) and triggers or initiates a process to modify the multi-access data session (e.g., a MA PDU session) by sending a PDU session release message to the PGW-C+SMF 410. The PDU session release message can include an indication of the branch of the multi-access data session that the UE 300 is requesting the PGW-C+SMF 410 to release from the multi-access data session, as shown at 603.

[0166] In the example described above with respect to Figure 4 、 Figure 5 and Figure 6 , the UE 300 registers with the AMF 404 and the MME 406 via different accesses (3GPP access 1, 3GPP access 2, and non-3GPP access), all of these different accesses belonging to the same mobile network (PLMN) and requesting the establishment of branches of a multi-access data session (e.g., a MA PDU session) via multiple accesses. It should be understood that in some embodiments, the AMF 404 and the MME 406 can belong to different mobile networks (e.g., PLMN 1 and PLMN2), and the UE 300 can register with the AMF 404 and the MME 406 via different accesses (3GPP access 1, 3GPP access 2, and non-3GPP access) and establish branches via multiple different accesses (3GPP access 1, 3GPP access 2, and non-3GPP access) belonging to different mobile networks as described above.

[0167] The policy information included in the URSP can be the URSP rules as described above. The URSP rules can be as shown in 3GPP TS 24.526, Table 5.2.1. In an example embodiment, the UE policy includes URSP rules, and the URSP rules include a routing descriptor component type identifier that includes an element marked in bold below and designated as "multi-branch preference type", which can include preference information for assisting the UE 300 in selecting a suitable access and requesting the establishment of a branch of a multi-access data session via the selected access.

[0168] Routing descriptor component type identifier

[0169] Bits 8 7 6 5 4 3 2 1

[0171] 0 0 0 0 0 0 0 1 SSC mode type

[0172] 0 0 0 0 0 0 1 0 S-NSSAI type

[0173] 0 0 0 0 0 1 0 0 DNN type

[0174] 0 0 0 0 1 0 0 0 PDU session type

[0175] 0 0 0 1 0 0 0 0 Preferred access type

[0176] 0 0 0 1 0 0 0 1 Multi-access preference type

[0177] 0 0 0 1 0 0 1 1 Multi-branch preference type

[0178] 0 0 1 0 0 0 0 0 Non-seamless non-3GPP offload indication type

[0179] 0 1 0 0 0 0 0 0 Location criteria type

[0180] 1 0 0 0 0 0 0 0 Time window type

[0181] 1 0 0 0 0 0 0 1 5G Prose layer 3 UE-to-network relay offload indication type

[0182] 1 0 0 0 0 0 1 0 PDU session pair ID type

[0183] 1 0 0 0 0 0 1 1 RSN type

[0184] All other values are reserved. If received, they shall be interpreted as unknown.

[0185] For "Multi-branch preference type", the routing descriptor component value field can be encoded as an octet that indicates the number of multi-branch preference fields, followed by the octets of the multi-branch preference fields.

[0186] The octet of the multi-branch preference field contains information identifying the access type and information identifying the RAT. In some embodiments, the octet includes a registration ID that corresponds to the registration identifier included in the respective registration request sent by the UE 300 when the UE 300 registers with the AMF 404 and the MME 406 via different accesses and that corresponds to a preferred or prohibited access. In some embodiments, the octet of the multi-branch preference field contains information indicating whether the branch of the multi-access data session is to be established prior to an access belonging to (or located in) one mobile network (or located in different mobile networks). In some embodiments, the octet of the multi-branch preference field contains information indicating a negative preference or prohibition for establishing a branch via a particular access.

[0187] For example:

[0188] Octet 1 (multi-branch preference field 1) contains the access type / RAT type

[0189] Octet 2 (multi-branch preference field 2) contains the access type / RAT type

[0190] Octet 3 (multi-branch preference field 3) contains the access type / RAT type

[0191] …

[0192] Or:

[0193] Octet 1 (multi-branch preference field 1) contains registration ID 1

[0194] Octet 2 (multi-branch preference field 2) contains registration ID 2

[0195] Octet 3 (multi-branch preference field 3) contains registration ID 3

[0196] …

[0197] In some embodiments, each octet indicates an identifier of a mobile network, such as a PLMN ID or an SNPN ID, which identifies whether the branch of the multi-access session is via an access in the same mobile network or in different mobile networks.

[0198] In some embodiments, if the PCF includes "multi-branch preference type" in the routing descriptor, the PCF is not expected to include "preferred access type" or "multi-access preference type" in the routing descriptor.

[0199] In addition, in some embodiments, where the information includes both a "multi-branch preference type" value identifying an access within a routing descriptor and a "preferred access type" value identifying a single preferred access or a "multi-access preference type" value identifying multiple access preferences, the UE is then configured to select an access based on the "multi-branch preference type" value and request the establishment of a branch for a multi-access data session via the selected access, and to ignore the "preferred access type" value or the "multi-access preference type" value from the routing descriptor. Further, if both a "multi-branch preference type" value and a "preferred access type" value or a "multi-access preference type" value are present in the routing descriptor components of a single routing descriptor, the UE can be configured to consider only the "preferred access type" value or the "multi-access preference type" value for routing descriptor where the UE does not support requesting the establishment of a multi-access data session in the manner described herein.

[0200] The preferred access type and preferred multi-access type information are further defined in TS 24.526 and accordingly indicate the access type and the access type for a multi-access data session (i.e., a data session via multi-access). For example, when the UE establishes a PDU session for a matching application, the preferred access type indicates the preferred access type (3GPP access or non-3GPP access), while the multi-access type information indicates that the PDU session should be established as a multi-access PDU session using both 3GPP access and non-3GPP access.

[0201] It should be understood that the base stations described herein may include units or modules for transmitting, receiving, or both transmitting and receiving, such as radio components or radio heads. Although the base station has been described as a single entity, different modules and memories may be implemented in one or more physical or logical entities.

[0202] It should be noted that while some embodiments have been described with respect to 5G systems, similar principles can also be applied to other networks and communication systems. Thus, although certain embodiments have been described above by way of example with reference to certain exemplary architectures for radio access and core networks, radio access technologies, and standards, these embodiments can be applied to any other suitable form of communication system implementing other radio access technologies in addition to the technologies shown and described herein.

[0203] It should also be noted herein that while example embodiments have been described above, various variations and modifications can be made to the disclosed solutions without departing from the scope of the present invention.

[0204] In general, the various embodiments, functions, and operations described above can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Certain aspects of the present disclosure may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device, but the present disclosure is not limited thereto. Although the various aspects of the present disclosure may be shown and described as block diagrams, flowcharts, or using some other graphical representation, it is well understood that, by way of non-limiting example, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or a controller or other computing device, or some combination thereof.

[0205] In general, the various embodiments of the present invention can be implemented in hardware or dedicated circuitry, software, logic circuitry, or any combination thereof. For example, some aspects can be implemented in hardware, while other aspects can be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device, but the present invention is not limited thereto. Although the various aspects of the present invention may be shown and described as block diagrams, flowcharts, or using some other graphical representation, it is well understood that, by way of non-limiting example, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or a controller or other computing device, or some combination thereof.

[0206] Embodiments of the present invention can be implemented by computer software executable by a data processor of a mobile device (such as in a processor entity), can also be implemented by hardware, or can be implemented by a combination of software and hardware. In addition, in this regard, it should be noted that any block of the logical flow shown in the figures can represent a program step, or an interconnected logical circuit, block, and function, or a combination of a program step and a logical circuit, block, and function. The software can be stored on a physical medium, such as a memory chip or a memory block implemented within a processor, a magnetic medium (such as a hard disk or a floppy disk), and an optical medium (such as, for example, a DVD and its data variant CD).

[0207] The memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor can be of any type suitable for the local technical environment and, by way of non-limiting example, can include one or more of the following: a general-purpose computer, a dedicated computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), gate-level circuitry, and a processor based on a multi-core processor architecture.

[0208] Embodiments of the present invention may be practiced in various components such as integrated circuits. The design of an integrated circuit is generally a highly automated process. Sophisticated and powerful software tools are available to transform a logic-level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate.

[0209] Programs such as those provided by Synopsys, Inc. of Mountain View, California and Cadence Design, Inc. of San Jose, California use well-established design rules and libraries of pre-stored design modules to automatically route and place components on a semiconductor chip. Once the design for a semiconductor circuit has been completed, the final design can be sent in a standardized electronic format (e.g., Opus, GDSII, etc.) to a semiconductor fabrication plant or "fab" for manufacturing.

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

[0211] (a) Only hardware circuit implementations (such as implementations in only analog and / or digital circuitry) and

[0212] (b) Combinations of hardware circuits and software, such as (where applicable):

[0213] (i) Combinations of analog or digital or mixed analog and digital hardware circuits with software or firmware or software and firmware and

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

[0215] This definition of circuitry applies to all uses of the term "component" and / or "circuitry" in this application (including in any claims). As a further example, as used in this application, the term "circuitry" also encompasses implementations of only a hardware circuit or a processor (or processors) or a portion of a hardware circuit or processor and its (or their) attendant software or firmware or software and firmware. For example, if applicable to a particular claim element, the term "circuitry" also encompasses a baseband integrated circuit or a processor integrated circuit for a mobile device, or a similar integrated circuit in a server, a cellular network device, or other computing or network device.

[0216] As used herein, the term "non-transitory" is a limitation of the medium itself (i.e., tangible, rather than a signal), rather than a limitation on data storage persistence (e.g., RAM vs. ROM).

[0217] As used herein, "at least one of the following: <list of two or more elements>" and "at least one of <list of two or more elements>" and similar phrasings (where the list of two or more elements is joined by "and" or "or") means at least any one element, or at least any two or more elements, or at least all of the elements.

[0218] The foregoing description has provided a complete and detailed description of exemplary embodiments of the invention by way of exemplary and non-limiting examples. However, various modifications and adaptations may become apparent to those skilled in the relevant art when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings of the invention will still fall within the scope of the invention as defined by the appended claims.

Claims

1. A method for a device, the method comprising: Receiving a policy from a core network of a mobile network, the policy including policy information that indicates a preference regarding which access paths from a plurality of access paths will be established for a multi-access data session for application traffic, the plurality of access paths being at least two accesses operating according to a first criterion, or at least two accesses operating according to an additional criterion; Selecting at least two access paths from the plurality of access paths for the multi-access data session based on the policy information; And Requesting establishment of the multi-access data session including the selected at least two access paths, the selected at least two access paths being the at least two accesses operating according to the first criterion, or at least two accesses operating according to the additional criterion.

2. The method according to claim 1, wherein the at least two accesses operating according to the first criterion are 3GPP accesses, and the at least two accesses operating according to the additional criterion are non-3GPP accesses.

3. The method according to any one of claims 1 or 2, wherein for each access path, the policy information indicating a preference regarding which access paths from a plurality of access paths will be established for a multi-access data session for application traffic includes at least one of the following: A description of the application traffic for the multi-access data session; An identifier identifying the access through which the device registers with the mobile network; An identifier identifying the type of access of the access path; An identifier identifying the radio access technology of the access; A combination of a source IP address, a destination IP address, a source port number, a destination port number, and a protocol of the multi-access data session; An identifier identifying the mobile network in which the access path is located; And An identifier identifying the network operator of the mobile network in which the access path is located.

4. The method according to any one of claims 1 to 3, wherein selecting at least two access paths from the plurality of access paths for a multi-access data session based on the policy information includes: Selecting the at least two access paths from the following plurality of access paths: The plurality of access paths corresponding to the access paths identified within the policy information; And The plurality of access paths via which the device registers with the mobile network.

5. The method according to any one of claims 1 to 4, wherein selecting at least two access paths from the plurality of access paths for a multi-access data session based on the policy information comprises: Selecting at least two access paths from a plurality of access paths corresponding to the access paths identified within the policy information.

6. The method according to claim 5, wherein requesting establishment of the multi-access data session including the selected at least two access paths further comprises: Requesting registration with the mobile network through at least one of the accesses on which the multi-access data session is to be established through the selected at least two access paths; And Requesting establishment of the selected at least two access paths.

7. The method according to any one of claims 1 to 6, wherein the policy includes a user equipment routing selection policy, and the policy information is a routing descriptor component type identifier, the routing descriptor component type identifier including: The preference regarding on which access paths from the plurality of access paths the multi-access data session for the application traffic will be established.

8. The method according to any one of claims 1 to 6, wherein the policy information includes user subscription information, and the user subscription information indicates that a multi-access data session can be requested to be established by the apparatus through at least one of: a defined type of access; and a defined radio access technology, wherein the multi-access data session is for at least one of: defined single network slice selection assistance information; and a defined data network name.

9. The method according to any one of claims 1 to 8, further comprising: Requesting release of at least one of the selected at least two access paths for the multi-access data session.

10. The method according to claim 9, wherein requesting release of at least one of the at least two selected access paths for the multi-access data session comprises: Based on determining a substantial loss of connectivity to an access network in one of the selected at least two access paths, requesting release of the at least one of the selected at least two access paths.

11. A method for a device in a mobile network, the method comprising: Generating a policy, the policy including policy information that indicates a preference regarding which access paths from a plurality of access paths will be established for a multi-access data session for application traffic, the plurality of access paths being at least two accesses operating according to a first criterion, or at least two accesses operating according to an additional criterion; And Sending the policy to another device registered with the mobile network.

12. The method according to claim 11, wherein the at least two accesses operating according to the first criterion are 3GPP accesses, and the at least two accesses operating according to the additional criterion are non-3GPP accesses.

13. The method according to any one of claims 11 or 12, wherein for each access path, the information indicating the preference regarding which access paths from the plurality of access paths will be established for the multi-access data session for application traffic includes at least one of: A description of the application traffic for the multi-access data session; An identifier identifying the access through which the other device registers with the core network; An identifier identifying the type of access; An identifier identifying the radio access technology of the access; A combination of a source IP address, a destination IP address, a source port number, a destination port number, and a protocol for the multi-access data session; An identifier identifying the mobile network in which the access path is located; And An identifier identifying the network operator of the mobile network in which the access path is located.

14. The method according to any one of claims 11 to 13, wherein the policy includes a user equipment routing selection policy, the policy information is a routing descriptor component type identifier, and the routing descriptor component type identifier includes: The preference regarding on which of the access paths from the plurality of access paths the multi-access data session will be established.

15. The method according to any one of claims 11 to 14, wherein the policy information includes user subscription information, and the user subscription information indicates that a multi-access data session can be requested to be established by the other device through at least one of: a defined type of access; and a defined radio access technology, wherein the multi-access data session is for at least one of: defined single network slice selection assistance information; and a defined data network name.

16. A device comprising components for performing the method according to any one of claims 1 to 15.

17. A device, comprising: At least one processor and at least one memory, the at least one memory storing instructions which, when executed by the at least one processor, cause the device to perform the method according to any one of claims 1 to 15.

18. A computer program comprising instructions which, when executed by at least one processor of a device, cause the device to perform the method according to any one of claims 1 to 15.

19. A computer-readable medium comprising instructions which, when executed by at least one processor of a device, cause the device to perform the method according to any one of claims 1 to 15.

Images