Merging network connections with different network address types

Abstract

Methods, apparatuses, and non-transitory computer-readable media for wireless communication. One method includes detecting that multiple single-address network connections are connected between the UE and a same first third generation partnership project (3GPP) data network access point, and in response to detecting that the multiple single-address network connections are connected between the UE and the same first 3GPP data network access point, establishing a multi-address network connection between the UE and the same first 3GPP data network access point, to merge the multiple single-address network connections between the UE and the first 3GPP data network access point to the multi-address network connection between the UE and the first 3GPP data network access point.

Description

[0001] Attorney Ref. No.: 554258WO MERGING NETWORK CONNECTIONS WITH DIFFERENT NETWORK ADDRESS TYPES

[0002] TECHNICAL FIELD

[0003] [1] The present disclosure relates to wireless communications.

[0004] BACKGROUND

[0005] [2] For legacy mobile networks such as universal mobile telecommunication system (UMTS), only single-address network connections such as single internet protocol (IP) version bearers are allowed. For example, cause #52 in specification TS24.008 or TS24.301 is used by a network (NW) to indicate that a requested packet data network (PDN) connectivity is accepted with a restriction that only single IP version bearers are allowed. Under such a cause, if a user equipment (UE) requests a multi-address bearer such as a PDN or packet data protocol (PDP) connection with a PDN type “IPv4v6”, the NW needs to assign two PDN or PDP connections, one for IPv4 and the other for IPv6, to fulfill the IPv4v6 data connection request from the UE.

[0006] SUMMARY

[0007] [3] Aspects of the disclosure provide a method of wireless communication at a user equipment (UE). The method includes detecting that multiple single-address network connections are connected between the UE and a same first third generation partnership project (3 GPP) data network access point, and in response to detecting that the multiple single-address network connections are connected between the UE and the same first 3 GPP data network access point, establishing a multi-address network connection between the UE and the same first 3GPP data network access point to merge the multiple single-address network connections between the UE and the first 3 GPP data network access point to the multi-address network connection between the UE and the first 3 GPP data network access point.

[0008] [4] Aspects of the disclosure provide an apparatus. The apparatus includes processing circuitry configured to detect that multiple single-address network connections are connected between the UE and a same first 3 GPP data network access point, and in response to detecting that the multiple single-address network connections are connected between the UE and the same first 3GPP data network access point, establish a multi-address network connectionAttorney Ref No.: 554258WO between the UE and the same first 3 GPP data network access point to merge the multiple singleaddress network connections between the UE and the first 3 GPP data network access point to the multi-address network connection between the UE and the first 3 GPP data network access point.

[0009] [5] Aspects of the disclosure provide a non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform a method. The method includes detecting that multiple single-address network connections are connected between the UE and a same first 3 GPP data network access point, and in response to detecting that the multiple single-address network connections are connected between the UE and the same first 3GPP data network access point, establishing a multi-address network connection between the UE and the same first 3 GPP data network access point to merge the multiple single-address network connections between the UE and the first 3 GPP data network access point to the multiaddress network connection between the UE and the first 3GPP data network access point.

[0010] BRIEF DESCRIPTION OF THE DRAWINGS

[0011] [6] Various embodiments of this disclosure that are proposed as examples will be described in detail with reference to the following figures, wherein like numerals reference like elements, and wherein:

[0012] [7] FIG. 1 shows a process of requesting a packet data network (PDN) connection to a network (NW) that allows only single-address bearers;

[0013] [8] FIG. 2 shows an example of handover of a user equipment (UE) from a legacy NW to a current NW;

[0014] [9] FIG. 3A shows a signal flow according to embodiments of the disclosure;

[0015]

[0010] FIG. 3B shows a signal flow according to embodiments of the disclosure;

[0016]

[0011] FIG. 3C shows a flowchart outlining a process according to embodiments of the disclosure;

[0017]

[0012] FIG. 4 shows an apparatus according to embodiments of the disclosure; and

[0013] FIG. 5 shows an exemplary computer system according to embodiments of the disclosure.

[0018] DETAILED DESCRIPTION OF EMBODIMENTS

[0019]

[0014] The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailedAttorney Ref. No.: 554258WO description includes specific details for the purpose of providing an understanding of various concepts. However, these concepts may be practiced without these specific details.

[0020]

[0015] Several aspects of wireless communication will now be presented with reference to various apparatuses and methods. These apparatuses and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, processes, algorithms, etc. (collectively referred to as “elements”). These elements may be implemented using electronic hardware or a combination of hardware and computer software.

[0021]

[0016] As noted above, the present disclosure relates to wireless communications. Specifically, the present disclosure relates to merging multiple single-address network connections with different network address types into a single multi-address network connection.

[0022]

[0017] In legacy mobile networks such as universal mobile telecommunication system (UMTS), only single-address network connections such as single internet protocol (IP) version bearers are allowed. For example, cause #52 in third generation partnership project (3GPP) specification TS24.008 or TS24.301 is used by a network (NW) to indicate that a requested packet data network (PDN) connectivity is accepted with a restriction that only single IP version bearers are allowed. Under such a cause, if a user equipment (UE) requests a multi-address bearer such as a PDN or packet data protocol (PDP) connection with a PDN type “IPv4v6”, the NW needs to assign two PDN or PDP connections, one for IPv4 and the other for IPv6, to fulfill the IPv4v6 data connection request from the UE.

[0023]

[0018] FIG. 1 shows a process 100 of requesting a PDN connection to an NW that allows only single-address bearers. In the process 100, a UE 101 can send to an NW 102 a first PDN connection request message PDN_CONNECT_REQ with a PDN type “IPv4v6” to request a PDN connection with both IPv4 and IPv6 addresses. Since the NW 102 allows only singleaddress bearers and does not support multi-address bearers, the NW 102 can send to the UE 101 a PDN connection rejection message PDN_CONNECT_REJ to reject the first PDN connection request. Then, the UE 101 can send to the NW 102 a second PDN connection request message PDN_CONNECT_REQ with a PDN type “IPv4” to request a PDN connection with an IPv4 address. To accept the second PDN connection request message, the NW 102 can send to the UE 101 a PDN connection accept message ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST with a PDN type “IPv4”. To acknowledge the PDN connection accept message, theAttorney Ref. No.: 554258WO UE 101 can send to the NW 102 an acknowledge message ACTIVATE DEFAULT EPS BEARER CONTEXT ACC. The UE 101 can also send to the NW 102 a third PDN connection request message PDN CONNECT REQ with a PDN type “IPv6” to request a PDN connection with an IPv6 address. To accept the third PDN connection request message, the NW 102 can send to the UE 101 a PDN connection accept message ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST with a PDN type “IPv6”. To acknowledge the PDN connection accept message, the UE 101 can send to the NW 102 an acknowledge message ACTIVATE DEFAULT EPS BEARER CONTEXT ACC.

[0024]

[0019] In an example, in response to the first PDN connection request message with the PDN type “IPv4v6” sent by the UE 101, instead of rejecting the first PDN connection request by sending the PDN connection rejection message, the NW 102 can allow a PDN connection with an IPv4 address by sending to the UE 101 a PDN connection accept message with a PDN type “IPv4”. If the UE 101 still needs a PDN connection with an IPv6 address, the UE 101 can send to the NW 102 a PDN connection request message with a PDN type “IPv6” to request a PDN connection with an IPv6 address. To accept the PDN connection request message with the PDN type “IPv6”, the NW 102 can send to the UE 101 a PDN connection accept message with a PDN type “IPv6” to allow a PDN connection with an IPv6 address.

[0025]

[0020] The 3GPP specification TS24.008 (or TS24.301) defines a behavior if an NW cannot support multiple bearers or a number of bearers is up to a maximum allowed number. In TS24.008 (or TS24.301), cause #55 defines that multiple PDN connections for a given access point name (APN) are not allowed, and cause #65 defines a maximum allowed number of PDP contexts.

[0026]

[0021] The 3GPP specification TS24.008 (or TS24.301) also defines abnormal cases on the NW side. If one or more information elements in a current PDN CONNECTIVITY REQUEST message differ from the ones received in a previous PDN CONNECTIVITY REQUEST message, and multiple PDN connections for a given APN are not allowed, the NW may deactivate the existing evolved packet system (EPS) bearer contexts for the PDN connection locally without notifying the UE and proceed with the requested PDN connectivity procedure, or the NW may reject the PDN connectivity request by sending a PDN CONNECTIVITY REJECT message that includes the cause #55 “multiple PDN connections for a given APN not allowed”.Attorney Ref No.: 554258WO

[0022] As described above, when only single-address network connections are allowed, the UE needs to retain two network connections (e.g., PDN or PDP) with different network address types (e.g., different IP types) for a multi-address (e.g., IPv4v6) network connection request. However, the cause #52 “single-address bearers only allowed” has been removed from new radio (NR) non-access stratum (NAS) specification TS24.501, and thus a 4G or 5GNW can support multi-address bearers.

[0027]

[0023] In some scenarios, a UE first establishes two PDN (or PDP) connections with a legacy NW (e.g., 2G or 3G NW) that supports only single-address bearers, and then is handed over to a current NW (e.g., 4G or 5G NW) that can support multi-address bearers. If the UE still retains two PDN (or PDP) connections with the current NW that can support multi-address bearers, various resources such as power consumption and network connection resource (e.g., PDN and resource block) can be wasted. Besides, the UE may meet cause #55 or cause #65 in the specification TS24.008 or TS24.301. That is, the current NW may not allow multiple PDN connections for a given APN to the UE, or a maximum number of the multiple PDN connections to the UE is reached.

[0028]

[0024] FIG. 2 shows an example 200 of handover of a UE 201 from a legacy NW 202 to a current NW 203. In the example 200, the legacy NW 202 can be a 2G or 3G NW, and the current NW 203 can be a 4G or 5G NW. To connect the legacy NW 202 with both IPv4 and IPv6 connections, the UE 201 needs to establish two PDN (or PDP) connections, one for IPv4 and the other for IPv6, since the legacy NW 202 allows only single-address bearers. After the UE 201 is handed over to the current NW 203, the UE 201 still retains the two PDN connections, wasting resources since the current NW 203 can support multi-address bearers. Accordingly, it is desired to merge multiple single-address PDN connections with different IP types to a single multi-address PDN connection.

[0029]

[0025] The 3GPP specification 24.501 describes procedures of handling PDN connection transfer between long term evolution (LTE) and NR. The below examples are based on the procedure of transferring the PDN connection from LTE to NR. In an example, when an NW has an N26 interface to connect mobility management entity (MME) and access and mobility management function (AMF), a PDN connection can be transferred to a packet data unit (PDU) session based on mapping rules provided by the NW. In such an example, two singleaddress PDN connections can be mapped to two single-address PDU sessions, respectively, andAttorney Ref No.: 554258WO merging the two single-address PDN connections to a multi-address PDU session is not allowed. In an example, when an NW does not have an N26 interface to connect MME and AMF, a PDN connection can be transferred to a PDU session based on UE sending a PDU session establishment request with a request type “existing PDU session”.

[0030]

[0026] The 3GPP specification 24.501 describes a procedure of handling PDN connection transfer between 3GPP access point and non-3GPP access point. For example, an IPv4v6 connection can be transferred from LTE to Wi-Fi based on UE sending a PDN connection establishment request with a request type “existing PDN connection”.

[0031]

[0027] As described above, merging multiple single-address network connections with different network address types to a single multi-address network connection can save power consumption and network connection resources. However, 3 GPP specification does not provide procedures for merging multiple single-address network connections with different network address types to a single multi-address network connection. This disclosure provides embodiments of merging multiple single-address network connections with different network address types to a single multi-address network connection.

[0032]

[0028] According to aspects of the disclosure, in response to detecting that multiple single-address network connections are connected to a same 3GPP data network access point such as APN for LTE or data network name (DNN) for NR, a UE can establish a multi-address network connection with the 3 GPP data network access point so that the multiple single-address network connections can be merged as the multi-address network connection. It is noted that a number of the single-address network connections is not limited in this disclosure.

[0033]

[0029] According to some embodiments of the disclosure, the UE can establish the multi-address network connection with the 3 GPP data network access point in an indirect manner.

[0034]

[0030] FIG. 3A shows a signal flow 300 according to embodiments of the disclosure. In the signal flow 300, at step S351, a UE 301 can detect that multiple single-address network connections 304(l)-304(N) are connected between the UE 301 and a same 3 GPP data network access point 302. In response to detecting that multiple single-address network connections 304(l)-304(N) are connected to the same 3 GPP data network access point 302, the UE 301 can first establish a multi-address network connection 305 with a non-3GPP data network access point 303 such as a Wi-Fi access point. The multi-address network connection 305 can includeAttorney Ref. No.: 554258WO network addresses of the multiple single-address network connections 304(l)-304(N) and an identifier of the 3GPP data network access point 302. Then, at step S352, the UE 301 can transfer the multi-address network connection 305 from the non-3GPP data network access point 303 to the 3GPP data network access point 302. The transferred multi-address network connection 306 can include the network addresses of the multiple single-address network connections 304(l)-304(N) and the identifier of the 3GPP data network access point 302.

[0035]

[0031] In an example, the 3GPP data network access point 302 can be an APN over LTE, the non-3GPP data network access point 303 can be a non-3GPP data network access point connected to an evolved packet core (EPC) network, and the multiple single-address network connections 304(l)-304(N) can include two single-address bearers that can be used for IPv4 and IPv6, respectively. In such an example, in response to detecting that the two single-address bearers are connected to the same APN over LTE, the UE 301 can transfer the two singleaddress bearers from the APN over LTE to the non-3GPP data network access point connected to the EPC network. The UE 301 can establish with the non-3GPP data network access point a multi-address PDN connection with a PDN type “IPv4v6”. The multi-address PDN connection can include IPv4 and IPv6 addresses of the two single-address bearers and an identifier of the APN. In this way, the two single-address bearers can be merged into one multi-address bearer. Then, the UE 301 can transfer the multi-address bearer back to the APN over LTE.

[0036]

[0032] In an example, the 3 GPP data network access point 302 can be a DNN over NR, the non-3GPP data network access point 303 can be a non-3GPP data network access point connected to a 5G core network (5GC), and the multiple single-address network connections 304(l)-304(N) can include two single-address PDU sessions that can be used for IPv4 and IPv6, respectively. In such an example, in response to detecting that the two single-address PDU sessions are connected to the same DNN over NR, the UE 301 can transfer the two singleaddress PDU sessions from the DNN over NR to the non-3GPP data network access point connected to the 5GC. The UE 301 can establish with the non-3GPP data network access point 303 a multi-address PDU session with a PDN type “IPv4v6”. The multi-address PDU session can include IPv4 and IPv6 addresses of the two single-address PDU sessions and an identifier of the DNN. In this way, the two single-address PDU sessions can be merged as the multi-address PDU session. Then, the UE 301 can transfer the multi-address PDU session back to the DNN over NR.Attorney Ref. No.: 554258WO

[0033] In some cases, a network server associated with a first 3 GPP data network access point may not be directly connected to a network server associated with a non-3GPP data network access point, so that a multi-address network connection cannot be directly transferred from non-3GPP data network access point to the first 3 GPP data network access point. In such cases, a second 3GPP data network access point can be used. A network server associated with the second 3 GPP data network can be directly connected to both the network server associated with the first 3 GPP data network access point and the network server associated with the non- 3 GPP network access point. Accordingly, the multi-address connection can be transferred from the non-3GPP data network access point to the first 3GPP data network access point via the second 3 GPP data network access point. FIG. 3B provides an example of using the second 3GPP data network access point as a transfer point between the first 3GPP data network access point and the non-3GPP data network access point.

[0037]

[0034] FIG. 3B shows a signal flow 310 according to embodiments of the disclosure. In the signal flow 310, at step S361, a UE 311 can detect that multiple single-address network connections 315( 1 )-315(N) are connected between the UE 311 and a same first 3GPP data network access point 312. In response to detecting that the multiple single-address network connections 315(1 )-315(N) are connected to the same first 3GPP data network access point 312, at step S362, the UE 311 can first transfer (or hand over) the multiple single-address network connections 315( 1 )-315(N) to a second 3GPP data network access point 313. The transferred single-address network connections 316(1)-316(N) can correspond to the single-address network connections 315( 1 )-315(N), respectively. For example, each transferred single-address network connection 316 and the corresponding single-address network connection 315 can have a same network address. Then, the UE 311 can establish a multi-address network connection 317 with a non-3GPP data network access point 314 such as a Wi-Fi access point. The multi-address network connection 317 can include the network addresses of the multiple single-address network connections 316(1 )-316(N) (which are the same as the network addresses of the multiple single-address network connections 315(1)-315(N)) and an identifier of the second 3GPP data network access point 313. Then, at step S363, the UE 311 can transfer the multiaddress network connection 317 from the non-3GPP data network access point 314 to the second 3 GPP data network access point 313. The transferred multi-address network connection 318 can include the network addresses of the multiple single-address network connections 315(1)-Attorney Ref No.: 554258WO 315(N). At step S364, the UE 311 can further transfer the multi-address network connection 318 from the second 3 GPP data network access point 313 to the first 3 GPP data network access point 312. The transferred multi-address network connection 319 can include the network addresses of the multiple single-address network connections 315(1)-315(N) and an identifier of the first 3GPP data network access point 312.

[0038]

[0035] In an example, the first 3 GPP data network access point 312 can be a DNN over NR, the second 3 GPP data network access point 313 can be an APN over LTE, the non-3GPP data network access point 314 can be a non-3GPP data network access point connected to an EPC, and the multiple single-address network connections 315(1)-315(N) can include two single-address PDU sessions that can be used for IPv4 and IPv6, respectively. In such an example, in response to detecting that the two single-address PDU sessions for the same DNN over NR, the UE can first hand over the two single-address PDU sessions to the APN over LTE. The UE 311 can transfer the two single-address PDU sessions from the APN to the non-3GPP access point connected to the EPC, by establishing with the non-3GPP data network access point 314 a multi-address PDN connection with a PDN type “IPv4v6”. The multi-address PDN connection can include network addresses of the two single-address PDU sessions and an identifier of the APN. In this way, the two single-address PDU sessions can be merged as the multi-address PDU session. Then, the UE 311 can transfer the multi-address PDU session from the non-3GPP access point 314 to the APN over LTE and further transfer the multi-address PDU session from the APN over LTE to the DNN over NR.

[0039]

[0036] It is noted that transferring a network connection between two 3GPP data network access points can be referred to as a handover process. Based on the involved network technologies and the data network access points, types of handover processes can include intra-RAT handover (e.g., LTE-to-LTE, or 5G-to-5G), inter-RAT handover (e.g., LTE-to-5G, or LTE-to-3G), inter-frequency handover (e.g., LTE band 1 to band 4), and intra-frequency handover (e.g., between different cells on the same frequency).

[0040]

[0037] Transferring a network connection between a 3 GPP data network access point to a non-3GPP data network access point can also involve a handover process that maintains service continuity while switching between the networks. This capability is part of the 3GPP interworking architecture, which enables seamless mobility between 3 GPP and non-3GPP networks. Steps of transferring the connection between the 3 GPP data network access point andAttorney Ref No.: 554258WO the non-3GPP data network access point can include initiating an authentication process for the non-3GPP data network access point, evaluating whether the non-3GPP data network access point satisfies quality of service (QoS), executing a handover process between the 3GPP data network access point and the non-3GPP data access point, and performing a mobility management protocol (e.g., GPRS tunneling protocol) to ensure session continuity during the handover process.

[0041]

[0038] According to some embodiments of the disclosure, the UE can establish the multi-address network connection with the 3 GPP data network access point in a direct manner. Through the direct manner, the UE can directly establish the multi-address network connection with the 3 GPP data network access point.

[0042]

[0039] In an embodiment, in response to detecting that two single-address bearers are connected to a same APN over LTE and the two single-address bearers were not established on LTE with a same public land mobile network (PLMN), the UE can directly establish with the APN a PDN connection with a PDN type “!Pv4v6” if a current PLMN corresponding to the APN over LTE can support multi-address bearers.

[0043]

[0040] In an embodiment, in response to detecting that two single-address PDU sessions are connected to a same DNN over NR, the UE can directly establish with the DNN a multi-address PDU session with a PDN type “IPv4v6”.

[0044]

[0041] Thus, compared to the direct manner, a benefit of the indirect manner is that the IP address of the network connection can be retained and thus data communication (e.g., user traffic) of the network connection can be maintained during a handover process. Accordingly, in an embodiment, the indirect manner can be initiated first and, if the indirect manner fails, the direct manner can then be utilized.

[0045]

[0042] In an example, in response to detecting that multiple single-address network connections are connected to a same 3 GPP data network access point, the UE can first initiate an establishment of a multi-address network connection with a non-3GPP data network access point such as a Wi-Fi access point. If the establishment succeeds, for example, if the non-3GPP data network access point provides the same IP address as provided by the 3GPP data network access point, the UE can then transfer back the multi-address network connection from the non-3GPP data network access point to the 3GPP data network access point. If the establishment fails, for example, if the non-3GPP data network access point rejects the establishment request, or theAttorney Ref No.: 554258WO multi-address network connection with the non-3GPP data network access point corrupts, or the non-3GPP data network access point does not provide the same IP address as provided by the 3GPP data network access point, the UE can then directly establish the multi-address network connection with the 3 GPP data network access point.

[0046]

[0043] In an example, in response to detecting that multiple single-address network connections are connected to a same first 3 GPP data network access point, the UE can first initiate a handover of the multiple single-address network connections from the first 3 GPP data network access point to a second 3 GPP data network access point. If the handover succeeds, for example, if the second 3GPP data network access point provides the same IP address as provided by the first 3GPP data network access point, the UE can then establish a multi-address network connection with a non-3GPP data network access point, transfer back the multi-address network connection from the non-3GPP data network access point to the second 3 GPP data network access point, and further transfer the multi-address network connection from the second 3 GPP data network access point to the first 3 GPP data network access point. However, if the handover fails, for example, if the second 3GPP data network access point rejects the handover request, or at least one of the multiple single-address network connections with the second 3 GPP data network access point corrupts, or the second 3GPP data network access point does not provide the same IP address as provided by the first 3 GPP data network access point, the UE can then directly establish the multi-address network connection with the 3GPP data network access point.

[0047]

[0044] FIG. 3C shows a flowchart outlining a process 320 according to embodiments of the disclosure. In various embodiments, the process 320 can be executed by processing circuitry, such as the processing circuitry 410 in the apparatus 400. For example, the process 320 can be implemented in software instructions, and, when the processing circuitry 410 executes the software instructions, the processing circuitry 410 can perform the process 320.

[0048]

[0045] The process 320 may generally start at step S321, where the process 320 can detect that multiple single-address network connections (e.g., multiple single-address connections 304 or 315) are connected between a UE (e g., UE 301 or 311) and a same first 3GPP data network access point (e.g., 3GPP data network access point 302 or 312). Then, the process 320 can proceed to step S322.Attorney Ref No.: 554258WO

[0046] At step S322, in response to detecting that the multiple single-address network connections are connected between the UE and the same first 3 GPP data network access point, the process 320 can establish a multi-address network connection (e.g., multi-address network connection 306 or 319) between the UE and the same first 3 GPP data network access point to merge the multiple single-address network connections between the UE and the first 3GPP data network access point to the multi-address network connection between the UE and the first 3GPP data network access point.

[0049]

[0047] In an embodiment, the process 320 can establish the multi-address network connection with a non-3GPP data network access point (e g., non-3GPP data network access point 303 or 314) and transfer the multi-address network connection from the non-3GPP data network access point to the first 3 GPP data network access point.

[0050]

[0048] In an embodiment, the multiple single-address network connections are handed over from the first 3 GPP data network access point to a second 3 GPP data network access point (e.g., 3GPP data network access point 313), and the process 320 can transfer the multi-address network connection from the non-3GPP data network access point to the first 3 GPP data network access point via the second 3 GPP data network access point.

[0051]

[0049] In an embodiment, the multi-address network connection includes network addresses of the multiple single-address network connections and an identifier of the first 3 GPP data network access point.

[0052]

[0050] In an embodiment, network address types of the network addresses of the multiple single-address network connections are different from each other.

[0053]

[0051] In an embodiment, the network address types of the network addresses of the multiple single-address network connections include IPv4 and IPv6.

[0054]

[0052] In an embodiment, the first 3GPP data network access point is an APN over LTE or a DNN over NR. A PLMN corresponding to the APN over LTE supports multi-address network connections.

[0055]

[0053] FIG. 3D shows a flowchart outlining a process 330 according to embodiments of the disclosure. In various embodiments, the process 330 can be executed by processing circuitry, such as the processing circuitry 410 in the apparatus 400. For example, the process 330 can be implemented in software instructions, and, when the processing circuitry 410 executes the software instructions, the processing circuitry 410 can perform the process 330.Attorney Ref. No.: 554258WO

[0054] The process 330 may generally start at step S331, where in response to detecting that multiple single-address network connections (e.g., multiple single-address connections 304 or 315) are connected between a UE (e.g., UE 301 or 311) and a same first 3GPP data network access point (e.g., 3GPP data network access point 302 or 312), the process 330 can establish a multi-address network connection (e.g., multi-address network connection 305 or 317) between the UE and a non-3GPP data network access point (e.g., non-3GPP data network access point 303 or 314). Then, the process 330 can proceed to step S332.

[0056]

[0055] At step S332, the process 330 can determine whether it is able to directly transfer the multi-address network connection from the non-3GPP data network access point to the first 3GPP data network access point. In response to determining that it is able to directly transfer the multi-address network connection from the non-3GPP data network access point to the first 3GPP data network access point, the process 330 can proceed to step S333. Otherwise, the process 300 can proceed to step S334.

[0057]

[0056] In an embodiment, the process 330 can determine whether it is able to directly transfer the multi-address network connection from the non-3GPP data network access point to the first 3GPP data network access point by determining whether a network server associated with the non-3GPP data network access point is directly connected to a network server associated with the first 3 GPP data network access point. In response to determining that the network server associated with the non-3GPP data network access point is directly connected to the network server associated with the first 3 GPP data network access point, the process 330 can determine that it is able to directly transfer the multi-address network connection from the non- 3 GPP data network access point to the first 3 GPP data network access point. Otherwise, the process 330 can determine that it is not able to directly transfer the multi-address network connection from the non-3GPP data network access point to the first 3 GPP data network access point.

[0058]

[0057] At step S333, the process 330 can transfer the multi-address network connection from the non-3GPP data network access point to the first 3 GPP data network access point. Then, the process 330 can terminate.

[0059]

[0058] At step S334, the process 330 can determine whether it is able to directly transfer the multi-address network connection from the non-3GPP data network access point to a second 3 GPP data network access point (e.g., 3 GPP data network access point 313). In responseAttorney Ref. No.: 554258WO to determining that it is able to directly transfer the multi-address network connection from the non-3GPP data network access point to the second 3 GPP data network access point, the process 330 can proceed to step S335. Otherwise, the process 330 can terminate.

[0060]

[0059] In an embodiment, the process 330 can determine whether it is able to directly transfer the multi-address network connection from the non-3GPP data network access point to the second 3 GPP data network access point by determining whether a network server associated with the non-3GPP data network access point is directly connected to a network server associated with the second 3 GPP data network access point. In response to determining that the network server associated with the non-3GPP data network access point is directly connected to the network server associated with the second 3 GPP data network access point, the process 330 can determine that it is able to directly transfer the multi-address network connection from the non-3GPP data network access point to the second 3GPP data network access point. Otherwise, the process 330 can determine that it is not able to directly transfer the multi-address network connection from the non-3GPP data network access point to the second 3 GPP data network access point.

[0061]

[0060] At step S335, the process 330 can transfer the multi-address network connection from the non-3GPP data network access point to the second 3GPP data network access point. Then, the process 330 can proceed to step S336.

[0062]

[0061] At step S336, the process 330 can transfer the multi-address network connection from the second 3 GPP data network access point to the first 3 GPP data network access point. Then, the process 330 can terminate.

[0063]

[0062] In an embodiment, the multi-address network connection includes network addresses of the multiple single-address network connections and an identifier of the first 3 GPP data network access point.

[0064]

[0063] In an embodiment, network address types of the network addresses of the multiple single-address network connections are different from each other.

[0065]

[0064] In an embodiment, the network address types of the network addresses of the multiple single-address network connections include IPv4 and IPv6.

[0066]

[0065] In an embodiment, the first 3GPP data network access point is an APN over LTE or a DNN over NR. A PLMN corresponding to the APN over LTE supports multi-address network connections.Attorney Ref No.: 554258WO

[0066] As described above, this disclosure provides embodiments of merging multiple single-address network connections (e.g., multiple single-address connections 304 or 315) with different network address types into a single multi-address network connection (e.g., multiaddress network connection 306 or 319), in order to save power consumption and network connection resources of a UE (e.g., UE 301 or 311).

[0067]

[0067] FIG. 4 shows an apparatus 400 according to embodiments of the disclosure. The apparatus 400 can be configured to perform various functions in accordance with one or more embodiments or examples described herein. Thus, the apparatus 400 can provide the implementation of techniques, processes, functions, components, and systems described herein. For example, the apparatus 400 can be used to implement functions of a UE or a base station (BS) (e.g., gNB) in various embodiments and examples described herein. The apparatus 400 can include a processor or specially designed circuits to implement various functions, components, or processes described herein in various embodiments. The apparatus 400 can include processing circuitry 410, a memory 420, a radio frequency (RF) module 430, and an antenna 440.

[0068]

[0068] In various examples, the processing circuitry 410 can include one or more circuits configured to perform the functions and processes described herein. In various examples, the processing circuitry 410 can be a digital signal processor (DSP), an application specific integrated circuit (ASIC), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), digitally enhanced circuits, or comparable device(s) or a combination thereof.

[0069]

[0069] In some examples, the processing circuitry 410 or circuitry can be a central processing unit (CPU) configured to execute program instructions to perform various functions and processes described herein. Accordingly, the memory 420 can be configured to store program instructions. The processing circuitry 410, when executing the program instructions, can perform the functions and processes. The memory 420 can further store other programs or data, such as operating systems, application programs, and the like. The memory 420 can include a read only memory (ROM), a random access memory (RAM), a flash memory, a solid state memory, a hard disk drive, an optical disk drive, and the like.

[0070]

[0070] The RF module 430 can receive a processed data signal from the processing circuitry 410 and convert the data signal to beamforming wireless signals that are then transmitted via the antenna 440, or vice versa. The RF module 430 can include a digital to analog converter (DAC), an analog to digital converter (ADC), a frequency up converter, aAttorney Ref No.: 554258WO frequency down converter, filters and amplifiers for reception and transmission operations. The RF module 430 can include multi-antenna circuitry for beamforming operations. For example, the multiantenna circuitry can include an uplink spatial filter circuit, and a downlink spatial filter circuit for shifting analog signal phases or scaling analog signal amplitudes. The antenna 440 can include one or more antenna arrays.

[0071]

[0071] The apparatus 400 can optionally include other components, such as input and output devices, additional or signal processing circuitry, and the like. Accordingly, the apparatus 400 may be capable of performing other additional functions, such as executing application programs, and processing alternative communication protocols.

[0072]

[0072] The techniques described above, can be implemented as computer software using computer-readable instructions and physically stored in one or more computer-readable media. For example, FIG. 5 shows a computer system 500 suitable for implementing certain embodiments of the disclosed subject matter.

[0073]

[0073] The computer software can be coded using any suitable machine code or computer language, that may be subject to assembly, compilation, linking, or like mechanisms to create code comprising instructions that can be executed directly, or through interpretation, micro-code execution, and the like, by one or more CPUs, Graphics Processing Units (GPUs), and the like.

[0074]

[0074] The instructions can be executed on various types of computers or components thereof, including, for example, personal computers, tablet computers, servers, smartphones, gaming devices, internet of things devices, and the like.

[0075]

[0075] The components shown in FIG. 5 for computer system 500 are exemplary in nature and are not intended to suggest any limitation as to the scope of use or functionality of the computer software implementing embodiments of the present disclosure. Neither should the configuration of components be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary embodiment of a computer system (500).

[0076]

[0076] Computer system 500 may include certain human interface input devices. Such a human interface input device may be responsive to input by one or more human users through, for example, tactile input (such as: keystrokes, swipes, data glove movements), audio input (such as: voice, clapping), visual input (such as: gestures), olfactory input (not depicted). The humanAttorney Ref. No.: 554258WO interface devices can also be used to capture certain media not necessarily directly related to conscious input by a human, such as audio (such as: speech, music, ambient sound), images (such as: scanned images, photographic images obtained from a still image camera), video (such as two-dimensional video, three-dimensional video including stereoscopic video).

[0077]

[0077] Input human interface devices may include one or more of (only one of each depicted): keyboard 501, mouse 502, trackpad 503, touch screen 510, data-glove (not shown), joystick 505, microphone 506, scanner 507, and camera 508.

[0078]

[0078] Computer system 500 may also include certain human interface output devices. Such human interface output devices may be stimulating the senses of one or more human users through, for example, tactile output, sound, light, and smell / taste. Such human interface output devices may include tactile output devices (for example tactile feedback by the touch-screen 510, data-glove (not shown), or joystick 505, but there can also be tactile feedback devices that do not serve as input devices), audio output devices (such as: speakers 509, headphones (not depicted)), visual output devices (such as screens 510 to include CRT screens, LCD screens, plasma screens, OLED screens, each with or without touch-screen input capability, each with or without tactile feedback capability — some of which may be capable to output two dimensional visual output or more than three dimensional output through means such as stereographic output; virtual-reality glasses (not depicted), holographic displays and smoke tanks (not depicted)), and printers (not depicted). These visual output devices (such as screens 510) can be connected to a system bus 548 through a graphics adapter 550.

[0079]

[0079] Computer system 500 can also include human accessible storage devices and their associated media such as optical media including CD / DVD ROM / RW 520 with CD / DVD or the like media 521, thumb-drive 522, removable hard drive or solid state drive 523, legacy magnetic media such as tape and floppy disc (not depicted), specialized ROM / ASIC / PLD based devices such as security dongles (not depicted), and the like.

[0080]

[0080] Those skilled in the art should also understand that the term “computer readable media” as used in connection with the presently disclosed subject matter does not encompass transmission media, carrier waves, or other transitory signals.

[0081]

[0081] Computer system 500 can also include a network interface 554 to one or more communication networks 555. The one or more communication networks 555 can for example be wireless, wireline, optical. The one or more communication networks 555 can further beAttorney Ref. No.: 554258WO local, wide-area, metropolitan, vehicular and industrial, real-time, delay-tolerant, and so on. Examples of the one or more communication networks 555 include local area networks such as Ethernet, wireless LANs, cellular networks to include GSM, 3G, 4G, 5G, LTE and the like, TV wireline or wireless wide area digital networks to include cable TV, satellite TV, and terrestrial broadcast TV, vehicular and industrial to include CANBus, and so forth. Certain networks commonly require external network interface adapters that attached to certain general purpose data ports or peripheral buses 549 (such as, for example USB ports of the computer system 500); others are commonly integrated into the core of the computer system 500 by attachment to a system bus as described below (for example Ethernet interface into a PC computer system or cellular network interface into a smartphone computer system). Using any of these networks, computer system 500 can communicate with other entities. Such communication can be unidirectional, receive only (for example, broadcast TV), uni-directional send-only (for example CANbus to certain CANbus devices), or bi-directional, for example to other computer systems using local or wide area digital networks. Certain protocols and protocol stacks can be used on each of those networks and network interfaces as described above.

[0082]

[0082] The aforementioned human interface devices, human-accessible storage devices, and network interfaces can be attached to a core 540 of the computer system 500.

[0083]

[0083] The core 540 can include one or more CPUs 541, GPUs 542, specialized programmable processing units in the form of Field Programmable Gate Areas (FPGA) 543, hardware accelerators for certain tasks 544, graphics adapters 550, and so forth. These devices, along with Read-only memory (ROM) 545, Random-access memory 546, internal mass storage 547 such as internal non-user accessible hard drives, SSDs, and the like, may be connected through the system bus 548. In some computer systems, the system bus 548 can be accessible in the form of one or more physical plugs to enable extensions by additional CPUs, GPUs, and the like. The peripheral devices can be attached either directly to the core’s system bus 548, or through a peripheral bus 549. In an example, the screen 510 can be connected to the graphics adapter 550. Architectures for a peripheral bus include PCI, USB, and the like.

[0084]

[0084] CPUs 541, GPUs 542, FPGAs 543, and accelerators 544 can execute certain instructions that, in combination, can make up the aforementioned computer code. That computer code can be stored in ROM 545 or RAM 546. Transitional data can also be stored in RAM 546, whereas permanent data can be stored for example, in the internal mass storage 547.Attorney Ref No.: 554258WO Fast storage and retrieval to any of the memory devices can be enabled through the use of cache memory that can be closely associated with one or more CPUs 541, GPUs 542, mass storage 547, ROM 545, RAM 546, and the like.

[0085]

[0085] The computer readable media can have computer code thereon for performing various computer-implemented operations.

[0086]

[0086] As an example and not by way of limitation, the computer system having architecture 500, and specifically the core 540 can provide functionality as a result of processor(s) (including CPUs, GPUs, FPGA, accelerators, and the like) executing software embodied in one or more tangible, computer-readable media. Such computer-readable media can be media associated with user-accessible mass storage as introduced above, as well as certain storage of the core 540 that are of non-transitory nature, such as core-internal mass storage 547 or ROM 545. The software implementing various embodiments of the present disclosure can be stored in such devices and executed by core 540. A computer-readable medium can include one or more memory devices or chips, according to particular needs. The software can cause the core 540 and specifically the processors therein (including CPU, GPU, FPGA, and the like) to execute particular processes or particular parts of particular processes described herein, including defining data structures stored in RAM 546 and modifying such data structures according to the processes defined by the software. In addition or as an alternative, the computer system can provide functionality as a result of logic hardwired or otherwise embodied in a circuit (for example: accelerator 544), which can operate in place of or together with software to execute particular processes or particular parts of particular processes described herein. Reference to software can encompass logic, and vice versa, where appropriate. Reference to a computer-readable media can encompass a circuit (such as an integrated circuit (IC)) storing software for execution, a circuit embodying logic for execution, or both, where appropriate.

[0087]

[0087] Aspects of the disclosure provide a method of wireless communication at a UE. The method includes detecting that multiple single-address network connections are connected between the UE and a same first 3 GPP data network access point, and in response to detecting that the multiple single-address network connections are connected between the UE and the same first 3GPP data network access point, establishing a multi-address network connection between the UE and the same first 3 GPP data network access point to merge the multiple single-addressAttorney Ref No.: 554258WO network connections between the UE and the first 3GPP data network access point to the multiaddress network connection between the UE and the first 3GPP data network access point.

[0088]

[0088] In an embodiment, the establishing includes establishing the multi-address network connection with a non-3GPP data network access point and transferring the multiaddress network connection from the non-3GPP data network access point to the first 3 GPP data network access point.

[0089]

[0089] In an embodiment, the multiple single-address network connections are handed over from the first 3 GPP data network access point to a second 3 GPP data network access point, and the transferring includes transferring the multi-address network connection from the non- 3 GPP data network access point to the first 3 GPP data network access point via the second 3 GPP data network access point.

[0090]

[0090] In an embodiment, the multi-address network connection includes network addresses of the multiple single-address network connections and an identifier of the first 3 GPP data network access point.

[0091]

[0091] In an embodiment, network address types of the network addresses of the multiple single-address network connections are different from each other.

[0092]

[0092] In an embodiment, the network address types of the network addresses of the multiple single-address network connections include IPv4 and IPv6.

[0093]

[0093] In an embodiment, the first 3GPP data network access point is an APN over LTE or a DNN over NR. A PLMN corresponding to the APN over LTE supports multi-address network connections.

[0094]

[0094] Aspects of the disclosure provide an apparatus. The apparatus includes processing circuitry configured to detect that multiple single-address network connections are connected between the UE and a same first 3 GPP data network access point, and in response to detecting that the multiple single-address network connections are connected between the UE and the same first 3GPP data network access point, establish a multi-address network connection between the UE and the same first 3 GPP data network access point to merge the multiple singleaddress network connections between the UE and the first 3GPP data network access point to the multi-address network connection between the UE and the first 3 GPP data network access point.

[0095]

[0095] In an embodiment, the processing circuitry is configured to establish the multiaddress network connection with a non-3GPP data network access point and transfer the multi-Attorney Ref No.: 554258WO address network connection from the non-3GPP data network access point to the first 3 GPP data network access point.

[0096]

[0096] In an embodiment, the multiple single-address network connections are handed over from the first 3 GPP data network access point to a second 3 GPP data network access point, and the processing circuitry is configured to transfer the multi-address network connection from the non-3GPP data network access point to the first 3GPP data network access point via the second 3 GPP data network access point.

[0097]

[0097] In an embodiment, the multi-address network connection includes network addresses of the multiple single-address network connections and an identifier of the first 3GPP data network access point.

[0098]

[0098] In an embodiment, network address types of the network addresses of the multiple single-address network connections are different from each other.

[0099]

[0099] In an embodiment, the network address types of the network addresses of the multiple single-address network connections include IPv4 and IPv6.

[0100]

[0100] In an embodiment, the first 3GPP data network access point is an APN over LTE or a DNN over NR. A PLMN corresponding to the APN over LTE supports multi-address network connections.

[0101]

[0101] Aspects of the disclosure provide a non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform a method. The method includes detecting that multiple single-address network connections are connected between the UE and a same first 3 GPP data network access point, and in response to detecting that the multiple single-address network connections are connected between the UE and the same first 3GPP data network access point, establishing a multi-address network connection between the UE and the same first 3 GPP data network access point to merge the multiple single-address network connections between the UE and the first 3GPP data network access point to the multiaddress network connection between the UE and the first 3GPP data network access point.

[0102]

[0102] In an embodiment, the establishing includes establishing the multi-address network connection with a non-3GPP data network access point and transferring the multiaddress network connection from the non-3GPP data network access point to the first 3 GPP data network access point.Attorney Ref No.: 554258WO

[0103] In an embodiment, the multiple single-address network connections are handed over from the first 3 GPP data network access point to a second 3 GPP data network access point, and the transferring includes transferring the multi-address network connection from the non- 3 GPP data network access point to the first 3 GPP data network access point via the second 3 GPP data network access point.

[0103]

[0104] In an embodiment, the multi-address network connection includes network addresses of the multiple single-address network connections and an identifier of the first 3 GPP data network access point.

[0104]

[0105] In an embodiment, network address types of the network addresses of the multiple single-address network connections are different.

[0105]

[0106] In an embodiment, the network address types of the network addresses of the multiple single-address network connections include IPv4 and IPv6.

[0106]

[0107] While this disclosure has described several exemplary embodiments, there are alterations, permutations, and various substitute equivalents, which fall within the scope of the disclosure. It will thus be appreciated that those skilled in the art will be able to devise numerous systems and methods which, although not explicitly shown or described herein, embody the principles of the disclosure and are thus within the spirit and scope thereof.

Claims

Attorney Ref. No.: 554258WO WHAT IS CLAIMED IS:

1. A method of wireless communication at a user equipment (UE), the method comprising:detecting that multiple single-address network connections are connected between the UE and a same first third generation partnership project (3 GPP) data network access point; and in response to detecting that the multiple single-address network connections are connected between the UE and the same first 3 GPP data network access point,establishing a multi-address network connection between the UE and the same first 3GPP data network access point, to merge the multiple single-address network connections between the UE and the first 3 GPP data network access point to the multi-address network connection between the UE and the first 3 GPP data network access point.

2. The method of claim 1, wherein the establishing includes:establishing the multi-address network connection with a non-3GPP data network access point; andtransferring the multi-address network connection from the non-3GPP data network access point to the first 3 GPP data network access point.

3. The method of claim 2, wherein the multiple single-address network connections are handed over from the first 3GPP data network access point to a second 3GPP data network access point, and the transferring includes transferring the multi-address network connection from the non-3GPP data network access point to the first 3GPP data network access point via the second 3 GPP data network access point.

4. The method of claim 2, wherein the multi-address network connection includes network addresses of the multiple single-address network connections and an identifier of the first 3GPP data network access point.

5. The method of claim 4, wherein network address types of the network addresses of the multiple single-address network connections are different from each other.Attorney Ref No.: 554258WO 6. The method of claim 5, wherein the network address types of the network addresses of the multiple single-address network connections include IPv4 and IPv6.

7. The method of claim 1, wherein the first 3GPP data network access point is an access point name (APN) over long term evolution (LTE) or a data network name (DNN) over new radio (NR).

8. The method of claim 7, wherein a public land mobile network (PLMN) corresponding to the APN over LTE supports multi-address network connections.

9. An apparatus, comprising:processing circuitry configured todetect that multiple single-address network connections are connected between the UE and a same first third generation partnership project (3 GPP) data network access point, andin response to detecting that the multiple single-address network connections are connected between the UE and the same first 3 GPP data network access point,establish a multi-address network connection between the UE and the same first 3 GPP data network access point, to merge the multiple single-address network connections between the UE and the first 3 GPP data network access point to the multiaddress network connection between the UE and the first 3 GPP data network access point.

10. The apparatus of claim 9, wherein the processing circuitry is configured to: establish the multi-address network connection with a non-3GPP data network access point; andtransfer the multi-address network connection from the non-3GPP data network access point to the first 3 GPP data network access point.

11. The apparatus of claim 10, wherein the multiple single-address network connections are handed over from the first 3GPP data network access point to a second 3GPP data networkAttorney Ref No.: 554258WO access point, and the processing circuitry is configured to transfer the multi-address network connection from the non-3GPP data network access point to the first 3 GPP data network access point via the second 3 GPP data network access point.

12. The apparatus of claim 10, wherein the multi-address network connection includes network addresses of the multiple single-address network connections and an identifier of the first 3GPP data network access point.

13. The apparatus of claim 12, wherein network address types of the network addresses of the multiple single-address network connections are different from each other.

14. The apparatus of claim 13, wherein the network address types of the network addresses of the multiple single-address network connections include IPv4 and IPv6.

15. The apparatus of claim 9, wherein the first 3GPP data network access point is an access point name (APN) over long term evolution (LTE) or a data network name (DNN) over new radio (NR).

16. The apparatus of claim 15, wherein a public land mobile network (PLMN) corresponding to the APN over LTE supports multi-address network connections.

17. A non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform a method, the method comprising:detecting that multiple single-address network connections are connected between the UE and a same first third generation partnership project (3 GPP) data network access point; and in response to detecting that the multiple single-address network connections are connected between the UE and the same first 3 GPP data network access point,establishing a multi-address network connection between the UE and the same first 3GPP data network access point, to merge the multiple single-address network connections between the UE and the first 3 GPP data network access point to the multi-address network connection between the UE and the first 3 GPP data network access point.Attorney Ref. No.: 554258WO18. The non-transitory computer-readable medium of claim 17, wherein the establishing includes:establishing the multi-address network connection with a non-3GPP data network access point; andtransferring the multi-address network connection from the non-3GPP data network access point to the first 3 GPP data network access point.

19. The non-transitory computer-readable medium of claim 18, wherein the multiple single-address network connections are handed over from the first 3GPP data network access point to a second 3GPP data network access point, and the transferring includes transferring the multi-address network connection from the non-3GPP data network access point to the first 3 GPP data network access point via the second 3 GPP data network access point.

20. The non-transitory computer-readable medium of claim 18, wherein the multi-address network connection includes network addresses of the multiple single-address network connections and an identifier of the first 3GPP data network access point.

Images