Method and system for multiple access protocol data unit sessions

Abstract

A wireless communication method for session management functions is disclosed. The method includes: sending to a wireless terminal a guidance rule for uplink data associated with a first protocol data unit session anchor point of a multi-access protocol data unit session, wherein the multi-access protocol data unit session is associated with a first protocol data unit session anchor point and a second protocol data unit session anchor point.

Description

Technical Field

[0001] This document generally relates to wireless communications, and in particular to Multiaccess Protocol Data Unit (MAPDU) sessions. Background Technology

[0002] Access Traffic Steering, Switching and Splitting (ATSSS) features can be supported by user equipment (UE) and / or 5G core (5GC) networks capable of implementing MAPDU services, which are achieved through the simultaneous use of a third-generation partner program (3GPP). rd Multiple PDUs are exchanged between the UE and the data network using a Generation Partner Project (3GPP) access network, a non-3GPP access network, and two independent N3 / N9 tunnels between the PDU Session Anchor (PSA) and the Radio Access Network / Access Network (RAN / AN). Multi-access PDU connection service is achieved by establishing MAPDU sessions (i.e., PDU sessions with user plane resources on two access networks).

[0003] When a UE is registered via both 3GPP and non-3GPP access, or when a UE is registered via only one access, the UE may request a MAPDU session.

[0004] After establishing a MAPDU session, and when user plane resources exist on both access networks, the UE applies the network-provided policy (i.e., ATSSS rules) and considers local conditions (such as network interface availability, signal loss conditions, user preferences, etc.) to determine how to allocate uplink traffic across the two access networks. Similarly, the PSA of the MAPDU session applies the network-provided policy (i.e., N4 rules) and feedback information received from the UE via the user plane (such as access network unavailability or availability) to determine how to allocate downlink traffic across two N3 / N9 tunnels and two access networks. When user plane resources exist only on one access network, the UE applies the ATSSS rules and considers local conditions to trigger the establishment or activation of user plane resources on the other access network.

[0005] In some scenarios, a Branching Point (BP) or Uplink Classifier (UL CL) can be inserted into one or more data paths of a MAPDU session. However, it is unclear how to execute or adjust ATSSS rules when a BP / UL CL is inserted into one or more data paths of a MAPDU session. Summary of the Invention

[0006] This document relates to methods, systems, and devices for MAPDU sessions, and in particular to methods, systems, and devices for updating bootstrapping rules for MAPDU sessions.

[0007] This disclosure relates to a wireless communication method used in a session management function. The method includes: sending to a wireless terminal a bootstrapping rule for uplink data associated with a first protocol data unit session anchor point of a multiple access protocol data unit (MAU) session, wherein the MAU session is associated with a first MAU session anchor point and a second MAU session anchor point.

[0008] Various embodiments can preferably achieve the following features:

[0009] Preferably, the bootstrapping rule is sent in response to the insertion of a branch point or uplink classifier into the multi-access protocol data unit session.

[0010] Preferably, the guidance rule instructs the use of access service guidance, switching, and splitting ATSSS functions to guide the uplink data associated with the first protocol data unit session anchor.

[0011] Preferably, the guidance rule instructs against using the Multipath Transmission Control Protocol (MPTCP) feature to guide the uplink data associated with the first protocol data unit session anchor.

[0012] Preferably, the guidance rule instructs the uplink data associated with the first protocol data unit session anchor to be guided to a branch point or uplink classifier.

[0013] Preferably, the branch point or the uplink classifier is included in the first protocol data unit session anchor point or is deployed independently.

[0014] Preferably, the uplink data associated with the first protocol data unit session anchor includes at least one of the following: a prefix associated with the first protocol data unit session anchor or at least one Internet Protocol address associated with the first protocol data unit session anchor.

[0015] Preferably, the wireless communication method further includes: sending tunnel information associated with a branch point or uplink classifier related to the first protocol data unit session anchor point to a wireless network node and a gateway, wherein the wireless terminal accesses the data network via the wireless network node and the gateway.

[0016] Preferably, the wireless communication method further includes sending the guidance rule to the second protocol data unit session anchor.

[0017] Preferably, the wireless communication method further includes: after the branch point or uplink classifier associated with the first protocol data unit session anchor point is removed, sending an instruction to remove the bootstrapping rule to at least one of the wireless terminal or the second protocol data unit session anchor point.

[0018] This disclosure relates to a wireless communication method used in a wireless terminal. The method includes: receiving a guidance rule from a session management function for uplink data associated with a first protocol data unit session anchor point of a multiple access protocol data unit session; and guiding the uplink data associated with the first protocol data unit session anchor point based on the guidance rule, wherein the multiple access protocol data unit session is associated with the first protocol data unit session anchor point and a second protocol data unit session anchor point.

[0019] Various embodiments can preferably achieve the following features:

[0020] Preferably, the bootstrapping rule is received in response to the insertion of a branch point or uplink classifier into the multi-access protocol data unit session.

[0021] Preferably, the guidance rule instructs the use of access service guidance, switching, and splitting ATSSS functions to guide the uplink data associated with the first protocol data unit session anchor.

[0022] Preferably, the guidance rule instructs to avoid using the Multipath Transmission Control Protocol (MPTCP) functionality to guide the uplink data associated with the first protocol data unit session anchor.

[0023] Preferably, the guidance rule instructs the uplink data associated with the first protocol data unit session anchor to be guided to a branch point or uplink classifier.

[0024] Preferably, the branch point or the uplink classifier is included in the first protocol data unit session anchor point or is deployed independently.

[0025] Preferably, the uplink data associated with the first protocol data unit session anchor includes at least one of the following: a prefix associated with the first protocol data unit session anchor or at least one Internet Protocol address associated with the first protocol data unit session anchor.

[0026] Preferably, the wireless communication method further includes: receiving an instruction from the session management function to remove the bootstrapping rule after the branch point or uplink classifier associated with the first protocol data unit session anchor point is removed.

[0027] This disclosure relates to a wireless device including session management functionality. The wireless device includes a communication unit configured to send guidance rules to a wireless terminal for uplink data associated with a first protocol data unit session anchor point of a multiple access protocol data unit (MAU) session, wherein the MAU session is associated with both the first MAU session anchor point and a second MAU session anchor point.

[0028] Various embodiments can preferably achieve the following features:

[0029] Preferably, the wireless device further includes a processor configured to perform any of the aforementioned wireless communication methods.

[0030] This disclosure relates to a wireless terminal. The wireless terminal includes:

[0031] The communication unit is configured to receive bootstrapping rules from the session management function for uplink data associated with the first protocol data unit session anchor point of the multi-access protocol data unit session; and

[0032] The processor is configured to guide the uplink data associated with the first protocol data unit session anchor point based on the guidance rules.

[0033] The multi-access protocol data unit session is associated with the first protocol data unit session anchor and the second protocol data unit session anchor.

[0034] Various embodiments can preferably achieve the following features:

[0035] Preferably, the processor is further configured to execute any of the aforementioned wireless communication methods.

[0036] This disclosure relates to a computer program product, including a computer-readable program medium on which code is stored, the code, when executed by a processor, causes the processor to implement the wireless communication method described in any of the foregoing methods.

[0037] The exemplary embodiments disclosed herein relate to providing features that will become apparent when taken in conjunction with the accompanying drawings and the following description. Exemplary systems, methods, apparatuses, and computer program products are disclosed herein according to various embodiments. However, it should be understood that these embodiments are presented by way of example and not by way of limitation, and that various modifications may be made to the disclosed embodiments while remaining within the scope of this disclosure, as will be apparent to those skilled in the art who have read this disclosure.

[0038] Therefore, this disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, the specific order and / or hierarchy of steps in the methods disclosed herein are merely exemplary methods. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes may be rearranged while remaining within the scope of this disclosure. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or actions in an exemplary order, and unless otherwise expressly stated, this disclosure is not limited to the specific order or hierarchy presented.

[0039] The above and other aspects and their embodiments are described in more detail in the accompanying drawings, specification and claims. Attached Figure Description

[0040] Figure 1 A schematic diagram of a network architecture according to an embodiment of the present disclosure is shown.

[0041] Figure 2 A schematic diagram of a network architecture according to an embodiment of the present disclosure is shown.

[0042] Figure 3 A schematic diagram of a network architecture according to an embodiment of the present disclosure is shown.

[0043] Figure 4 A schematic diagram of a process according to an embodiment of the present disclosure is shown.

[0044] Figure 5 A schematic diagram of a process according to an embodiment of the present disclosure is shown.

[0045] Figure 6 A schematic diagram of an example of a wireless terminal according to an embodiment of the present disclosure is shown.

[0046] Figure 7 A schematic diagram illustrating an example of a wireless network node according to an embodiment of the present disclosure is shown.

[0047] Figure 8 A flowchart of a method according to an embodiment of this disclosure is shown.

[0048] Figure 9 A flowchart of a method according to an embodiment of this disclosure is shown. Detailed Implementation

[0049] Figure 1 and Figure 2 A schematic diagram of a network architecture according to an embodiment of the present disclosure is shown. Figure 1 and Figure 2 The network architecture shown includes the following network functions and entities:

[0050] 1. UE (User Equipment):

[0051] The UE can be a wireless terminal, such as a tablet computer, smartphone, or laptop. Figure 1 and Figure 2 In this context, the UE accesses the data network (e.g., the core network) via 3GPP access and non-3GPP access. Furthermore, the UE can use the Access Service Bootstrapping, Handover, and Split (ATSSS) Lower Layer (ATSSS-LL) function or the Multipath Transmission Control Protocol (MPTCP) function to bootstrap / allocate uplink and / or downlink services via 3GPP access and non-3GPP access.

[0052] 2. NG-RAN (Next Generation Radio Access Network):

[0053] The NG-RAN (node) is responsible for the air interface resource scheduling and air interface connection management of the network accessed by the UE. In this disclosure, NG-RAN (node) may refer to RAN (node) or gNB.

[0054] 3. AMF (Access and Mobility Management Function)

[0055] AMF includes the following functions: registration management, connection management, reachability management, and mobility management. AMF also performs access authentication and access authorization.

[0056] 4. SMF (Session Management Function)

[0057] SMF includes the following functions: session management (e.g., session establishment, modification, and release), UE Internet Protocol (IP) address allocation and management, selection and control of User Plane (UP) functions, downlink data notification, etc.

[0058] 5. UPF (User Plane Function)

[0059] UPF includes the following functions: anchor point for mobility within / between RATs (Radio Access Technology), packet routing and forwarding, service usage reporting, Quality of Service (QoS) processing for UPs, downlink packet buffering, and downlink data notification triggering.

[0060] 6. N3IWF (Non-3GPP Interworking Function):

[0061] N3IWF is responsible for interoperability between untrusted non-3GPP networks and data networks.

[0062] 7. I-SMF (inserted SMF):

[0063] When the UE is outside the service area of ​​the SMF, the I-SMF is inserted between the SMF and the AMF.

[0064] exist Figure 1 In this embodiment, the BP / UL CL is inserted into the data path of the MAPDU session (i.e., the data path via NG-RAN). In this embodiment, the UE may initially have a MAPDU session on both NG-RAN (i.e., 3GPP access) and N3IWF (i.e., non-3GPP access), where the MAPDU session has a PDU session anchor point PSA1. In this embodiment, PSA1 is located in a centralized UPF. Based on certain events (e.g., UE mobility), the SMF can establish another PDU session anchor point PSA2 for the MAPDU session. PSA2 may be located in a local UPF. In this case, the SMF inserts the BP / UL CL into the MAPDU session to correctly allocate data from / to the UE. Figure 1 In this process, BP / UL CL is inserted into the data path via NG-RAN.

[0065] Unlike Figure 1 BP / UL CL in Figure 2The BP / ULCL is inserted into the two data paths corresponding to NG-RAN and N3IWF (i.e., both 3GPP access and non-3GPP access).

[0066] In this disclosure, the MAPDU session type can be one of the following: Internet Protocol version 4 (IPv4), Internet Protocol version 6 (IPv6), IPv4v6, and Ethernet.

[0067] Figure 3 A schematic diagram of a network architecture according to an embodiment of the present disclosure is shown. Figure 3 The architecture shown includes the following features:

[0068] A) The UE supports one or more boot functions, such as the MPTCP function and / or the ATSSS-LL (ATSSS lower layer) function. Each boot function in the UE can perform service booting, handover, and splitting across 3GPP access and non-3GPP access according to the ATSSS rules provided by the network. The ATSSS-LL function is mandatory for Ethernet-type MAPDU sessions in the UE.

[0069] B) The UPF can support the MPTCP proxy function, which communicates with the MPTCP function in the UE using the MPTCP protocol.

[0070] C) The UPF may support the ATSSS-LL function, which is similar to the ATSSS-LL function defined for the UE. There is no defined user plane protocol between the ATSSS-LL function in the UE and the ATSSS-LL function in the UPF. Figure 3 The ATSSS-LL function in UPF is not shown.

[0071] D) The UPF supports the Performance Measurement Functionality (PMF), which can be used by the UE to obtain access performance measurements on the user plane of 3GPP access and / or non-3GPP access.

[0072] Figure 4 A schematic diagram illustrates a process for inserting a BP / UL CL into the data path of a MAPDU session according to an embodiment of this disclosure. In this process, the BP / UL CL is inserted into, for example... Figure 1The user plane path of the MAPDU session on the NG-RAN is shown. Due to the insertion of BP / UL CL, the network needs to adjust the ATSSS policy (e.g., ATSSS rules) to ensure that allocated traffic is routed correctly. Specifically, the process includes the following steps:

[0073] Step 401: The UE has an established MAPDU session or the UE establishes a MAPDU session on NG-RAN (i.e., 3GPP access) and N3IWF (i.e., non-3GPP access), wherein the MAPDU session has a PDU session anchor (i.e., such as...). Figure 1 The PSA1 shown is a (centralized) UPF. The UE allocates uplink services for the MAPDU session on NG-RAN and N3IWF based on the ATSSS rules provided by the SMF. The PSA1 allocates downlink services for the MAPDU session on NG-RAN and N3IWF based on the ATSSS N4 rules provided by the SMF.

[0074] Step 402: For example, due to UE mobility or new flow detection, the SMF decides to establish a new PDU session anchor (i.e., such as...). Figure 1 (See PSA2). The SMF selects the (local) UPF and uses N4 to establish a new PSA2 for the MAPDU session. In the case of an IPv6 multihomed PDU session, the SMF also ensures that the new IPv6 prefix corresponding to PSA2 is allocated. Furthermore, if the PCF has already subscribed to IP allocation / release events, the SMF performs a session management policy modification process to provide the PCF with the newly allocated IPv6 prefix.

[0075] Step 403: The SMF selects a local UPF and uses N4 to establish a BP (in the case of IPv6 multihoming) or ULCL for the MAPDU session. The SMF provides the necessary uplink forwarding rules to PSA1 and PSA2, which include PSA1 CN (Core Network) tunnel information (Info) and PSA2 CN tunnel Info. Additionally, AN (i.e., NG-RAN) tunnel Info is provided for downlink forwarding. In the case of IPv6 multihoming, the SMF provides service filters for the IPv6 prefixes corresponding to PSA1 and PSA2, where the service filters indicate which services should be forwarded to PSA1 and PSA2 respectively.

[0076] In the case of ULCL, SMF provides the following service filter: This service filter indicates which services should be forwarded to PSA1 and PSA2 respectively.

[0077] In embodiments where BP / UL CL and PSA2 are both located in a single UPF (i.e., a local UPF), steps 402 and 403 can be combined.

[0078] In embodiments where BP has already been assigned, step 403 is skipped.

[0079] Step 404: The SMF updates the BP / UL CL information to PSA1 via N4. For example, the SMF provides PSA1 with CN tunnel Info for downlink services, where the CN tunnel Info includes BP / UL CL information.

[0080] In embodiments where BP / UL CL and PSA1 are both located in a single UPF (i.e., a centralized UPF), steps 403 and 404 can be combined.

[0081] Step 405: The SMF updates the BP / UL CL information to PSA2 via N4. For example, the SMF provides PSA2 with CN tunnel Info for downlink services, where the CN tunnel Info includes BP / UL CL information.

[0082] In embodiments where BP / UL CL and PSA2 are both located in a single UPF (i.e., a local UPF), step 405 can be omitted.

[0083] Step 406: The SMF updates the BP / ULCL information to the NG-RAN via N2 SM information on N11. For example, the SMF provides a new CN tunnel Info corresponding to the UPF (i.e., corresponding to BP or UL CL).

[0084] Step 407: In the case of IPv6 multihoming, the SMF notifies the UE of the availability of the new IP prefix corresponding to PSA2, for example, by using an IPv6 router advertisement message (e.g., RFC 4861 Neighbor Discovery in IPv6). Furthermore, the SMF sends the IPv6 multihoming routing rules and the IPv6 prefix to the UE by using an IPv6 router advertisement message (e.g., RFC 4191 Neighbor Discovery in IPv6).

[0085] Step 408: In the case of IPv6 multihoming, the SMF can reconfigure the UE for the original IP prefix corresponding to PSA1. That is, the SMF sends the IPv6 multihoming routing rules and the IPv6 prefix corresponding to PSA1 to the UE using an IPv6 router advertisement message.

[0086] Step 409: The SMF notifies the UE of the updated ATSSS rules. In the case of IPv6 multihoming, the updated ATSSS rules should include the following rule: This rule ensures that all uplink traffic with the new IP prefix (assigned to PSA2 in step 407) as the source IP address is guided by a bootstrapping function other than MPTCP (e.g., ATSSS-LL function) and / or routed on the NG-RAN. In the case of UL CL, the updated ATSSS rules should include the following rule: This rule ensures that all uplink traffic forwarded to PSA2 via UL CL with a destination IP address or prefix is ​​guided by a bootstrapping function other than MPTCP (e.g., ATSSS-LL function) and / or routed on the NG-RAN.

[0087] For example, the ATSSS rule used to guide uplink traffic from BP to PSA2 can be represented as (in this embodiment, the new prefix for PSA2 is 2001:: / 64):

[0088] “Traffic Descriptor:SourceAddress 2001::”, “Steering Mode:Load-Balancing,3GPP=100%,non-3GPP=0%”, “Steering Functionality:ATSSS-LL”.

[0089] The rule states that "100% of services with the prefix 2001:: as the source IP address are transmitted to 3GPP access using the ATSSS-LL function".

[0090] In one embodiment, the ATSSS rule used to guide uplink traffic through UL CL to PSA2 can be represented as:

[0091] “Traffic Descriptor:TCP,DestAddress 1.2.3.4”, “Steering Mode:Active-Standby,Active=3GPP,Standby=NA”, “Steering Functionality:ATSSS-LL”.

[0092] In this embodiment, the destination IP address 1.2.3.4 is in the forwarding rule to PSA2 in the UL CL. This rule indicates that "TCP traffic with destination address 1.2.3.4 will be routed to access for active access (3GPP) only by using the ATSSS-LL function".

[0093] Step 410: SMF then notifies PSA1 of the updated N4 rules for ATSSS downlink service allocation.

[0094] Figure 5 A schematic diagram illustrating the process of inserting a BP or UL CL into the data path of a MAPDU session according to an embodiment of this disclosure is shown. Figure 5 In the process shown, BP / UL CL is inserted into, as... Figure 2 The user plane path of the MA PDU session on NG-RAN and N3IWF is shown. In this case, due to this BP / UL CL insertion, the network needs to adjust the ATSSS policy (i.e., ATSSS rules) to ensure that the allocated traffic is routed correctly.

[0095] Specifically, steps 501 to 504 are similar to Figure 4 Steps 401 to 404 are shown, but with the following additional content:

[0096] - In step 503, AN tunnel Info is sent not only to NG-RAN but also to N3IWF. AN tunnel Info for both NG-RAN and N3IWF is provided for downlink forwarding.

[0097] - After step 504, downlink services are allocated on NG-RAN and N3IWF via BP / ULCL based on ATSSS N4 rules.

[0098] Steps 505 to 508 are similar to steps 405 to 408, but with the following additional content:

[0099] - In step 506, the SMF updates the BP / UL CL information to the NG-RAN and N3IWF respectively via the N2 SM information on N11. For example, the SMF provides a new CN tunnel Info corresponding to the local UPF (e.g., BP or UL CL).

[0100] Step 509: The SMF notifies the UE of the updated ATSSS rules.

[0101] In the case of IPv6 multihoming, the updated ATSS rule (should) include the following rule: This rule ensures that all uplink traffic with the new IP prefix (assigned in step 507) as the source IP address is guided by a bootstrapping function other than the MPTCP function (e.g., the ATSSS-LL function).

[0102] In the case of ULCL, the updated ATSSS rule (should) include the following rule: This rule ensures that all uplink traffic with a destination IP address or prefix forwarded to PSA2 (via UL CL) is guided by a guidance function other than MPTCP.

[0103] In one embodiment, the ATSSS rule for uplink traffic via BP to PSA2 can be represented as (in this embodiment, the new prefix for PSA2 is 2001:: / 64):

[0104] “Traffic Descriptor:SourceAddress 2001::”, “Steering Mode:Active-Standby,Active=3GPP,Standby=non-3GPP”, “Steering Functionality:ATSSS-LL”.

[0105] In this embodiment, the ATSSS rule means "If the active access (3GPP) is available, the ATSSS-LL function is used to route services with source IP address 2001:: to the active access (3GPP). If the active access is unavailable, a non-3GPP access is used."

[0106] In one embodiment, the ATSSS rule for uplink traffic via UL CL to PSA2 can be represented as:

[0107] “Traffic Descriptor:TCP,DestAddress 1.2.3.4”, “Steering Mode:3GPP is high priority access”, “Steering Functionality:ATSSS-LL”.

[0108] In this embodiment, the destination IP address 1.2.3.4 is in the forwarding rule to PSA2 in UL CL. This rule states that "unless congestion occurs on 3GPP access, the ATSSS-LL function will be used to route TCP services with destination address 1.2.3.4 to 3GPP access."

[0109] Step 510: The SMF notifies PSA1 of the updated N4 rules for ATSSS downlink service allocation. Additionally, if PSA2 supports the ATSSS-LL function, the SMF can send the N4 rules for ATSSS downlink service allocation to PSA2.

[0110] In one embodiment, when the BP or UL CL in the data path of the MAPDU session is removed, the SMF updates the ATSSS rules stored in the UE and the N4 rules stored in the PSA1.

[0111] In this disclosure, when a BP / UL CL is inserted into one or more data paths of a MAPDU session, the SMF notifies the UE of the updated ATSSS rules.

[0112] In an embodiment where BP / UL CL is inserted into a data path of a MAPDU session:

[0113] In the case of IPv6 multihoming, the updated ATSSS rule includes the following rule: This rule instructs all uplink traffic with the new IP prefix (which is assigned to PSA2) as the source IP address to be guided by a guidance function other than MPTCP (e.g., ATSSS-LL function) and / or routed on the data path of the inserted BP.

[0114] In the case of ULCL, the updated ATSSS rule includes the following rule: This rule indicates that all uplink traffic with a specific destination IP address or prefix associated with PSA2 (i.e., uplink traffic forwarded to PSA2 (via UL CL)) is guided by a guidance function other than MPTCP (e.g., ATSSS-LL function) and / or routed on the data path inserted into ULCL.

[0115] In an example where BP / UL CL is inserted into two data paths of a MAPDU session:

[0116] In the case of IPv6 multihoming, the updated ATSSS rules include the following rule: This rule ensures that all uplink traffic with the new IP prefix (assigned to PSA2) as the source IP address is guided by a bootstrapping function other than MPTCP (e.g., ATSSS-LL function).

[0117] In the case of ULCL, the updated ATSSS rule includes the following rule: This rule indicates that all uplink traffic with a destination IP address or prefix associated with PSA2 (i.e., uplink traffic forwarded to PSA2 (via UL CL)) is guided by a guidance function other than MPTCP (e.g., ATSSS-LL function).

[0118] In addition, if PSA2 supports the ATSSS-LL function, SMF can send N4 rules to PSA2 for ATSSS downlink service allocation.

[0119] In this disclosure, the source IP address / prefix or local IP address / prefix can be a type of service descriptor component in an ATSSS rule. The source / local IP address / prefix refers to the source address of uplink packets sent by the UE.

[0120] In one embodiment, when a BP or UL CL inserted into one or more data paths of a MAPDU session is removed, the SMF updates the ATSSS rules stored in the UE and / or the N4 rules stored in the PSA1.

[0121] Figure 6 This is a schematic diagram relating to a wireless terminal 60 according to an embodiment of the present disclosure. The wireless terminal 60 may be a user equipment (UE), mobile phone, laptop computer, tablet computer, e-book reader, or portable computer system, but is not limited thereto. The wireless terminal 60 may include a processor 600 (such as a microprocessor or application-specific integrated circuit (ASIC)), a storage unit 610, and a communication unit 620. The storage unit 610 may be any data storage device storing program code 612, which can be accessed and executed by the processor 600. Embodiments of the storage unit 610 include, but are not limited to, a Subscriber Identity Module (SIM), Read-Only Memory (ROM), Flash memory, Random-Access Memory (RAM), hard disk, and optical data storage devices. The communication unit 620 may be a transceiver and is used to send and receive signals (e.g., messages or packets) based on the processing results of the processor 600. In one embodiment, the communication unit 620 communicates via… Figure 6 At least one antenna 622 shown transmits and receives signals.

[0122] In one embodiment, storage unit 610 and program code 612 may be omitted, and processor 600 may include storage unit with stored program code.

[0123] The processor 600 can implement any of the steps in the exemplary embodiment on the wireless terminal 60, for example by executing program code 612.

[0124] The communication unit 620 may be a transceiver. Alternatively or additionally, the communication unit 620 may combine a transmitting unit and a receiving unit, which are respectively configured to transmit signals to and receive signals from a wireless network node (e.g., a base station).

[0125] Figure 7 This diagram relates to a wireless network node 70 according to an embodiment of the present disclosure. The wireless network node 70 may be a satellite, base station (BS), network entity, mobility management entity (MME), serving gateway (S-GW), packet data network (PDN) gateway (P-GW), radio access network (RAN) node, next-generation RAN (NG-RAN) node, gNB, eNB, gNB central unit (gNB-CU), gNB distributed unit (gNB-DU), data network, core network, or radio network controller (RNC), and is not limited thereto. Furthermore, the wireless network node 70 may include (execute) at least one network function, such as access and mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), application function (AF), etc. The wireless network node 70 may include a processor 700 (such as a microprocessor or ASIC), a storage unit 710, and a communication unit 720. Storage unit 710 can be any data storage device storing program code 712, which can be accessed and executed by processor 700. Examples of storage unit 710 include, but are not limited to, SIM, ROM, flash memory, RAM, hard disk, and optical data storage devices. Communication unit 720 can be a transceiver and is used to send and receive signals (e.g., messages or packets) based on the processing results of processor 700. In one example, communication unit 720 via... Figure 7 At least one antenna 722 shown transmits and receives signals.

[0126] In one embodiment, the storage unit 710 and the program code 712 may be omitted. The processor 700 may include a storage unit containing stored program code.

[0127] The processor 700 can implement any of the steps described in the exemplary embodiments on the wireless communication node 70, for example, via executing program code 712.

[0128] The communication unit 720 may be a transceiver. Alternatively or additionally, the communication unit 720 may combine a transmitting unit and a receiving unit, which are respectively configured to transmit signals to a wireless terminal (e.g., a user equipment or another wireless network node) and receive signals from a wireless terminal (e.g., a user equipment or another wireless network node).

[0129] Figure 8 A flowchart of a method according to an embodiment of this disclosure is shown. Figure 8 The method shown can be used in an SMF (e.g., a wireless device that includes an SMF or performs SMF functions), and the method includes the following steps:

[0130] Step 801: Send the bootstrapping rules to the wireless terminal for uplink data associated with the first PSA of the MAPDU session.

[0131] Specifically, the SMF sends the first PSA (e.g., for the MAPDU session) Figure 1 or Figure 2 The routing rules for uplink data associated with PSA2 are shown in the diagram. In this embodiment, a MAPDU session is associated with (e.g., includes, has) two PSAs, namely, a first PSA and a second PSA (e.g., Figure 1 or Figure 2 PSA1 as shown in the figure.

[0132] For example, a MAPDU session can be established for the UE, and this MAPDU session includes a second PSA. Due to certain events (e.g., UE mobility), the SMF establishes a first PSA in the MAPDU session. In this case, the SMF inserts a BP or UL CL into one or more data paths of the MA PDU. In response to the insertion of the BP / UL CL and / or the establishment of the first PSA, the SMF sends a bootstrapping rule associated with the first PSA to the radio terminal, for example, to enable the radio terminal to correctly allocate uplink data associated with the first PSA.

[0133] In one embodiment, the bootstrapping rule instructs the use of an ATSSS function (e.g., an ATSSS-LL function) to bootstrap uplink data associated with the first PSA.

[0134] In one embodiment, the bootstrapping rule instructs against using the MPTCP feature to bootstrap uplink data associated with the first PSA.

[0135] In one embodiment, the bootstrapping rule instructs the bootstrapping of uplink data associated with the first PSA to the BP / ULCL.

[0136] In one embodiment, the BP / UL CL may be included in the first PSA or deployed independently.

[0137] In one embodiment, the uplink data associated with the first PSA includes a prefix associated with the first PSA (e.g., a prefix assigned to the first PSA). For example, the prefix associated with the first PSA refers to the source IP prefix of the uplink data (e.g., UE packets).

[0138] In one embodiment, the uplink data associated with the first PSA includes at least one IP address associated with the first PSA. For example, the IP address associated with the first PSA refers to the destination IP address of the uplink data (e.g., UE packets). In one embodiment, the at least one IP address associated with the first PSA may include one or more destination IP addresses associated with the BP / UL CL.

[0139] In one embodiment, the SMF may also send tunneling information associated with the inserted BP / UL CL associated with the first PSA to wireless network nodes (e.g., NG-RAN nodes) and gateways (e.g., N3IWF), wherein the wireless terminal accesses the data network via the wireless network nodes and gateways (i.e., 3GPP access and non-3GPP access).

[0140] In one embodiment, the SMF sends a bootstrapping rule to the second PSA.

[0141] In one embodiment, after the BP or UL CL associated with the first PSA, and / or the first PSA is removed from the MAPDU session (e.g., when the BP or UL CL associated with the first PSA, and / or the first PSA is removed from the MAPDU session, no later than or in response to the removal of the BP or UL CL associated with the first PSA, and / or the first PSA from the MAPDU session), the SMF sends an instruction to the wireless terminal and / or the second PSA to remove the guiding rule.

[0142] Figure 9 A flowchart of a method according to an embodiment of this disclosure is shown. Figure 9 The method shown can be used in a wireless terminal (e.g., a UE) and includes the following steps:

[0143] Step 901: Receive the bootstrapping rules from SMF for uplink data associated with the first PSA of the MAPDU session.

[0144] Step 902: Based on the guidance rules, guide the uplink data associated with the first PSA.

[0145] exist Figure 9 In this embodiment, the wireless terminal receives bootstrapping rules from the SMF for uplink data associated with the first PSA of the MAPDU session. In this embodiment, the MAPDU session includes / comprises two PSAs, namely, the first PSA (e.g., such as...). Figure 1 or Figure 2 The PSA2 shown) and the second PSA (e.g., as shown) Figure 1 or Figure 2 (PSA1 shown). The wireless terminal guides the uplink data associated with the first PSA based on the guidance rules.

[0146] In one embodiment, a radio terminal may establish or have a MAPDU session that includes / includes a second PSA. Due to certain events (e.g., UE mobility), an additional PSA (i.e., a first PSA) may be established within the MAPDU session. In this case, a BP or UL CL may be inserted into the MAPDU session (one or more data paths). In response to the insertion of the BP or UL CL and / or the establishment of the first PSA, a bootstrapping rule is received by the radio terminal.

[0147] In one embodiment, the bootstrapping rule instructs the use of an ATSSS function (e.g., an ATSSS-LL function) to bootstrap uplink data associated with the first PSA.

[0148] In one embodiment, the bootstrapping rule instructs against using the MPTCP feature to bootstrap uplink data associated with the first PSA.

[0149] In one embodiment, the bootstrapping rule instructs the bootstrapping of uplink data associated with the first PSA to the BP / ULCL.

[0150] In one embodiment, the BP / UL CL may be included in the first PSA or deployed independently.

[0151] In one embodiment, the uplink data associated with the first PSA includes a prefix associated with the first PSA (e.g., a prefix assigned to the first PSA). For example, the prefix associated with the first PSA refers to the source IP prefix of the uplink data (e.g., UE packets).

[0152] In one embodiment, the uplink data associated with the first PSA includes at least one IP address associated with the first PSA. For example, the IP address associated with the first PSA refers to the destination IP address of the uplink data (e.g., UE packets). In one embodiment, the at least one IP address associated with the first PSA may include one or more destination IP addresses associated with the BP / UL CL.

[0153] In one embodiment, after the first PSA and / or BP / ULCL is removed from the MAPDU session (e.g., when the first PSA and / or BP / ULCL is removed from the MAPDU session, no later than or in response to the removal of the first PSA and / or BP / ULCL from the MAPDU session), the wireless terminal receives an instruction from the SMF for the removal guidance rule.

[0154] While various embodiments of the present disclosure have been described above, it should be understood that these embodiments are presented by way of example only and not by way of limitation. Similarly, the various figures may depict exemplary architectures or configurations, provided to enable those skilled in the art to understand the exemplary features and functionality of the present disclosure. However, those skilled in the art should understand that the present disclosure is not limited to the illustrated exemplary architectures or configurations, but can be implemented using various alternative architectures and configurations. Furthermore, as those skilled in the art should understand, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of the present disclosure should not be limited to any of the exemplary embodiments described above.

[0155] It should also be understood that any references to elements in this document using names such as "first," "second," etc., generally do not restrict the number or order of these elements. Rather, these names may be used in this document as a convenient way to distinguish between two or more elements or instances of elements. Therefore, a reference to the first element and the second element does not imply that only two elements can be used, or that the first element must somehow precede the second element.

[0156] Furthermore, those skilled in the art should understand that information and signals can be represented using a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols, as may be mentioned in the above description, can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[0157] Those skilled in the art should also understand that any of the various illustrative logic blocks, units, processors, means, circuits, methods, and functions described in conjunction with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination thereof), firmware, various forms of program or design code containing instructions (which may be referred to herein as "software" or "software unit" for convenience), or any combination of these techniques.

[0158] To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, units, circuits, and steps have generally been described above according to their functions. Whether this function is implemented in hardware, firmware, software, or a combination of these technologies depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art can implement the described functions in various ways for each specific application, but such implementation decisions will not deviate from the scope of this disclosure. According to various embodiments, processors, devices, components, circuits, structures, machines, units, etc., can be configured to perform one or more of the functions described herein. As used herein with respect to a specified operation or function, the terms "configured to" or "configured for" refer to processors, devices, components, circuits, structures, machines, units, etc., that are physically constructed, programmed, and / or arranged to perform the specified operation or function.

[0159] Furthermore, those skilled in the art should understand that the various illustrative logic blocks, units, devices, components, and circuits described herein can be implemented within or executed by an integrated circuit (IC), which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, or any combination thereof. Logic blocks, units, and circuits may also include antennas and / or transceivers for communicating with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors combined with a DSP core, or any other suitable combination of configurations for performing the functions described herein. If implemented in software, these functions may be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium.

[0160] Computer-readable media include both computer storage media and communication media, with the latter including any medium capable of transferring computer programs or code from one location to another. Storage media can be any usable medium that can be accessed by a computer. For example, but not limited to, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to store required program code in the form of instructions or data structures and is accessible to a computer.

[0161] In this document, the term "unit" as used herein refers to software, firmware, hardware, and any combination of such elements for performing the associated functions described herein. Furthermore, for purposes of discussion, various units are described as discrete units; however, it will be apparent to those skilled in the art that two or more units can be combined to form a single unit performing the associated functions according to embodiments of this disclosure.

[0162] Additionally, memory or other storage devices, as well as communication components, may be employed in embodiments of this disclosure. It will be understood that, for clarity, the foregoing description has referenced various functional units and processors to embodiments of this disclosure. However, it will be apparent that any suitable functional distribution among different functional units, processing logic elements, or domains may be used without departing from this disclosure. For example, a function shown to be performed by a separate processing logic element or controller may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to suitable means for providing the described functionality and do not indicate a strict logical or physical structure or organization.

[0163] Various modifications to the embodiments described herein will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to limit the embodiments shown herein, but should be given the widest scope consistent with the novel features and principles disclosed herein as described in the claims.

Claims

1. A wireless communication method used in a session management function, the method comprising: A bootstrapping rule is sent to a wireless terminal for uplink data associated with a first protocol data unit session anchor point of a multi-access protocol data unit session, wherein the multi-access protocol data unit session is associated with a first protocol data unit session anchor point and a second protocol data unit session anchor point, and wherein the bootstrapping rule is sent in response to the insertion of a branch point or an uplink classifier in the multi-access protocol data unit session. Send the bootstrapping rule to the second protocol data unit session anchor; and After the branch point or uplink classifier associated with the first Protocol Data Unit (PDU) session anchor is removed, an instruction to remove the bootstrapping rule is sent to at least one of the wireless terminal or the second PDU session anchor. The guidance rule indicates that the use of the Multipath Transmission Control Protocol (MPTCP) function should be avoided when guiding the uplink data associated with the first protocol data unit session anchor.

2. The wireless communication method according to claim 1, wherein, The guidance rules instruct the use of access service guidance, switching, and splitting ATSSS functions to guide the uplink data associated with the first protocol data unit session anchor.

3. The wireless communication method according to claim 1 or 2, wherein, The guidance rule instructs the uplink data associated with the first protocol data unit session anchor to be guided to the branch point or the uplink classifier.

4. The wireless communication method according to claim 3, wherein, The branch point or the uplink classifier is included in the first protocol data unit session anchor or is deployed independently.

5. The wireless communication method according to any one of claims 1 to 4, wherein, The uplink data associated with the first protocol data unit session anchor includes at least one of the following: a prefix associated with the first protocol data unit session anchor or at least one Internet Protocol address associated with the first protocol data unit session anchor.

6. The wireless communication method according to any one of claims 1 to 5, further comprising: The wireless terminal sends tunnel information associated with the branch point or the uplink classifier associated with the first protocol data unit session anchor to the wireless network node and the gateway, wherein the wireless terminal accesses the data network via the wireless network node and the gateway.

7. A wireless communication method used in a wireless terminal, the method comprising: Receive bootstrapping rules from the session management function for uplink data associated with the first protocol data unit session anchor point of the multi-access protocol data unit session; Based on the guidance rule, the uplink data associated with the first protocol data unit session anchor is guided, wherein the multi-access protocol data unit session is associated with the first protocol data unit session anchor and the second protocol data unit session anchor, and wherein the guidance rule is received in response to the insertion of a branch point or uplink classifier in the multi-access protocol data unit session; and After the branch point or uplink classifier associated with the first protocol data unit session anchor point is removed, an instruction to remove the bootstrapping rule is received from the session management function. The guidance rule indicates that the use of the Multipath Transmission Control Protocol (MPTCP) function should be avoided when guiding the uplink data associated with the first protocol data unit session anchor.

8. The wireless communication method according to claim 7, wherein, The guidance rules instruct the use of access service guidance, switching, and splitting ATSSS functions to guide the uplink data associated with the first protocol data unit session anchor.

9. The wireless communication method according to claim 7 or 8, wherein, The guidance rule instructs the uplink data associated with the first protocol data unit session anchor to be guided to the branch point or uplink classifier.

10. The wireless communication method according to claim 9, wherein, The branch point or the uplink classifier is included in the first protocol data unit session anchor or is deployed independently.

11. The wireless communication method according to any one of claims 7 to 10, wherein, The uplink data associated with the first protocol data unit session anchor includes at least one of the following: a prefix associated with the first protocol data unit session anchor or at least one Internet Protocol address associated with the first protocol data unit session anchor.

12. A wireless device including session management functionality, the wireless device comprising: The communication unit is configured as follows: A bootstrapping rule is sent to a wireless terminal for uplink data associated with a first protocol data unit session anchor point of a multi-access protocol data unit session, wherein the multi-access protocol data unit session is associated with a first protocol data unit session anchor point and a second protocol data unit session anchor point, and wherein the bootstrapping rule is sent in response to the insertion of a branch point or an uplink classifier in the multi-access protocol data unit session. Send the bootstrapping rule to the second protocol data unit session anchor; and After the branch point or uplink classifier associated with the first Protocol Data Unit (PDU) session anchor is removed, an instruction to remove the bootstrapping rule is sent to at least one of the wireless terminal or the second PDU session anchor. The guidance rule indicates that the use of the Multipath Transmission Control Protocol (MPTCP) function should be avoided when guiding the uplink data associated with the first protocol data unit session anchor.

13. The wireless device of claim 12, further comprising a processor configured to perform the wireless communication method of any one of claims 2 to 6.

14. A wireless terminal, comprising: The communication unit is configured to receive bootstrapping rules from the session management function for uplink data associated with the first protocol data unit session anchor point of the multi-access protocol data unit session; The processor is configured to guide the uplink data associated with the first protocol data unit session anchor point based on the guidance rule, wherein the multi-access protocol data unit session is associated with the first protocol data unit session anchor point and a second protocol data unit session anchor point, wherein the guidance rule is received in response to the insertion of a branch point or uplink classifier in the multi-access protocol data unit session; and The communication unit is also configured to receive an instruction from the session management function to remove the bootstrapping rule after the branch point or uplink classifier associated with the first protocol data unit session anchor point is removed. The guidance rule indicates that the use of the Multipath Transmission Control Protocol (MPTCP) function should be avoided when guiding the uplink data associated with the first protocol data unit session anchor.

15. The wireless terminal according to claim 14, wherein, The processor is also configured to perform the wireless communication method according to any one of claims 8 to 11.

16. A computer-readable storage medium on which code is stored, the code, when executed by a processor, causes the processor to implement the wireless communication method according to any one of claims 1 to 11.

Images