Data transmission method

Abstract

The embodiment of the invention discloses a wireless communication method used in a wireless network node. The method includes transmitting a Data Radio Bearer (DRB) mapping rule to a wireless terminal, the rule indicating that a first Quality of Service (QoS) flow of a first Protocol Data Unit (PDU) session is mapped to a common DRB to which a second QoS flow of a second PDU session is mapped.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate generally to wireless communication, and in particular to 5G communication. BACKGROUND

[0002] In existing 5G systems (5 Generation System, 5GS), each Data Radio Bearer (DRB) is used to transport one or multiple Quality-of-Service (QoS) flows belonging to the same Protocol Data Unit (PDU) session. In other words, a single DRB cannot be shared by a QoS flow of PDU session #1 and a QoS flow of another PDU session #2, resulting in inefficient use of scarce radio resources in the air interface. SUMMARY

[0003] Embodiments of the present application relate to methods, systems and apparatuses for transmitting data, and in particular to methods, systems and apparatuses for allowing one DRB to be shared by QoS flows of different PDU sessions.

[0004] The present disclosure relates to a wireless communication method for use in a wireless network node. The method comprises:

[0005] transmitting, to a wireless terminal, a Data Radio Bearer (DRB) mapping rule indicating that a first Quality-of-Service (QoS) flow of a first Protocol Data Unit (PDU) session is mapped to a common DRB to which a second QoS flow of a second PDU session is mapped.

[0006] Various embodiments can optionally implement the following features:

[0007] Optionally, the wireless communication method further comprises modifying a Maximum Bit Rate (MBR) of the common DRB based on the first QoS flow of the first PDU session.

[0008] Optionally, the first QoS flow of the first PDU session is a non-guaranteed-bit-rate (Non-GBR) QoS flow.

[0009] Optionally, the wireless communication method further comprises:

[0010] receiving, from the wireless terminal, uplink data on the common DRB, a PDU session identifier of the uplink data, and a QoS Flow Identifier (QFI) of the uplink data,

[0011] The N3 tunnel is determined based on the PDU session ID from the uplink data, and

[0012] Uplink data is sent to the user plane function using the determined N3 tunnel.

[0013] Optionally, the wireless communication method further includes:

[0014] Receive downlink data configured to be transmitted via the public DRB from the user plane function, and

[0015] Sends downlink data located on the public DRB, the PDU session identifier of the downlink data, and the QoS flow identifier (QFI) of the downlink data to the wireless terminal.

[0016] Optionally, the PDU session identifier and QFI are located in the Service Data Adaptation Protocol (SDAP) header.

[0017] This disclosure relates to a wireless communication method for use in a wireless network node. The method includes:

[0018] Receive data radio bearer (DRB) mapping rules from the wireless network node. These rules indicate that the first quality of service (QoS) flow of the first protocol data unit (PDU) session is mapped to the public DRB to which the second QoS flow of the second PDU session is mapped.

[0019] Various implementation methods may optionally achieve the following features:

[0020] Optionally, the maximum bit rate (MBR) of the public DRB is modified based on the first QoS flow of the first PDU session.

[0021] Optionally, the first QoS stream of the first PDU session is a non-guaranteed bit rate QoS stream.

[0022] Optionally, the wireless communication method further includes: sending uplink data located on a public DRB, a PDU session identifier of the uplink data, and a QoS flow identifier (QFI) of the uplink data to the wireless network node.

[0023] Optionally, the wireless communication method further includes receiving downlink data located on a public DRB, a PDU session identifier of the downlink data, and a QoS flow identifier (QFI) of the downlink data from a wireless network node.

[0024] Optionally, the PDU session identifier and QFI are located in the Service Data Adaptation Protocol (SDAP) header.

[0025] This disclosure relates to a wireless network node. The wireless network node includes:

[0026] The communication unit is configured to send a data radio bearer (DRB) mapping rule to the wireless terminal, the rule indicating that a first quality of service (QoS) flow of a first protocol data unit (PDU) session is mapped to a public DRB to which a second QoS flow of a second PDU session is mapped.

[0027] Various implementation methods may optionally achieve the following features:

[0028] Optionally, the wireless network node also includes a processor configured to perform any of the aforementioned wireless communication methods.

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

[0030] The communication unit is configured to receive data radio bearer (DRB) mapping rules from a wireless network node, the rules indicating that a first quality of service (QoS) flow of a first protocol data unit (PDU) session is mapped to a public DRB to which a second QoS flow of a second PDU session is mapped.

[0031] Various implementation methods may optionally achieve the following features:

[0032] Optionally, the wireless terminal also includes a processor configured to perform any of the aforementioned wireless communication methods.

[0033] This disclosure relates to a computer program product including computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement any of the preceding methods of wireless communication.

[0034] The exemplary embodiments disclosed herein relate to features that will become readily 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 as a limitation, and that various modifications can 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 read this disclosure.

[0035] 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 that this disclosure is not limited to the specific order or hierarchy presented, unless otherwise expressly stated.

[0036] The embodiments of this application are defined by the independent claims. Optional embodiments are defined in the dependent claims. In the following description, although numerous features may be specified as optional, it is acknowledged that all features included in the independent claims should not be considered optional.

[0037] The above and other aspects, as well as their implementations, are described in more detail in the accompanying drawings, specification, and claims. Attached Figure Description

[0038] Figure 1 A schematic diagram of a network according to an embodiment of the present disclosure is shown;

[0039] Figure 2 A schematic diagram of a QoS model in 5GS according to an embodiment of the present disclosure is shown;

[0040] Figure 3 A schematic diagram of a wireless side data plane protocol stack according to an embodiment of the present disclosure is shown;

[0041] Figure 4 A schematic diagram of a QoS mapping model (UL) according to an embodiment of the present disclosure is shown;

[0042] Figure 5 A schematic diagram of a PDU session establishment process according to an embodiment of the present disclosure is shown;

[0043] Figure 6 A schematic diagram of a UE-requested PDU session modification process according to an embodiment of the present disclosure is shown;

[0044] Figure 7 A schematic diagram of a UE-requested PDU session release process according to an embodiment of the present disclosure is shown;

[0045] Figure 8 A schematic diagram of a UL message transmission process according to an embodiment of the present disclosure is shown;

[0046] Figure 9 A schematic diagram of a UL message transmission process according to an embodiment of the present disclosure is shown;

[0047] Figure 10 An example of a schematic diagram of a wireless terminal according to an embodiment of the present disclosure is shown;

[0048] Figure 11 An example of a schematic diagram of a wireless network node according to an embodiment of the present disclosure is shown;

[0049] Figure 12 A flowchart of a method according to an embodiment of the present disclosure is shown;

[0050] Figure 13 A flowchart of a method according to an embodiment of the present disclosure is shown. Detailed Implementation

[0051] In this disclosure, the terms “info” or “Info” may refer to information.

[0052] In this disclosure, the terms “Ack” or “ACK” may refer to acknowledgment (message).

[0053] Figure 1 A schematic diagram of a network (architecture) according to an embodiment of this disclosure is shown. Figure 1 In this context, a network includes the following network functions / entities:

[0054] 1) User Equipment (UE)

[0055] 2) Radio Access Network (RAN)

[0056] In this disclosure, the RAN manages radio resources, delivers user data received via the N3 interface to the UE, and delivers user data from the UE via the N3 interface. The RAN performs mapping between DRBs (Dedicated Radio Bearers) and QoS (Quality of Service) flows in PDU sessions.

[0057] In this disclosure, RAN can be equal to AN or RAN node.

[0058] 3) Access and Mobility Management Function (AMF)

[0059] The AMF includes the following functions: registration management, connection management, reachability management, and mobility management. The AMF also performs access authentication and access authorization. The AMF is a non-access stratum (NAS) secure termination service and relays session management (SM) between the UE and the SMF, etc.

[0060] 4) Session Management Function (SMF)

[0061] The SMF includes the following functions: session establishment, modification, and release; UE Internet Protocol (IP) address allocation and management (including optional authorization functions); selection and control of User Plane (UP) functions; and downlink data notification. The SMF is associated with the UPF via N4. The SMF provides the UPF with one or more Packet Detection Rules (PDR messages) to instruct how to detect user data traffic; Forwarding Action Rules (FAR), QoS Enforcement Rules (QER), and Usage Reporting Rules (URR) to instruct the UPF how to perform user data traffic forwarding, QoS processing, and usage reporting on user data traffic detected through the use of PDR.

[0062] 5) User Plane Function (UPF)

[0063] The UPF includes the following functions: acting as an anchor point for mobility within / between Radio Access Technologies (RATs) and an external session interconnection point to the data network, such as message routing and forwarding indicated by the SMF, traffic usage reporting, Quality of Service (QoS) processing for the UP, downlink message buffering, and downlink data notification triggering, etc. Additionally, a GTP-U (GPRS UP) tunnel is used over the N3 interface between the RAN and the UPF. Each PDU session has its corresponding GTP-U tunnel. For downlink traffic, the UPF binds the downlink traffic to the QoS flow within the PDU session's GTP-U tunnel using the FAR received from the SMF. For uplink traffic, the RAN forwards user plane traffic to the QoS flow identified by the UE.

[0064] 6) Policy Control Function (PCF)

[0065] The PCF provides QoS policy rules to control plane functions to enforce these rules. The PCF translates AF requests into PCC rules applicable to PDU sessions.

[0066] 7) Unified Data Management (UDM)

[0067] The UDM performs tasks such as generating 3GPP AKA authentication credentials, granting access based on subscription data, managing UE service NF registration (e.g., storing the UE's service AMF, storing the UE's service SMF for PDU sessions), and subscription management, etc. The UDM accesses the UDR to retrieve UE subscription data and stores the UE context in the UDR. The UDM and UDR can be deployed together.

[0068] In one implementation, the 5G core (5GC) supports PDU connectivity services, which provide a service for exchanging PDUs between the UE and a data network identified by a Data Network Name (DNN). PDU connectivity services are supported via PDU sessions. A PDU session is an association between the UE and the data network that provides PDU connectivity services.

[0069] In one implementation, the 5G QoS model is based on QoS flows. The 5G QoS model supports both QoS flows that require guaranteed bit-rate (GBR) (i.e., GBR QoS flows) and QoS flows that do not require guaranteed bit-rate (i.e., Non-GBR QoS flows). A QoS flow is the finest granularity for QoS forwarding processing in 5GS. All traffic mapped to the same 5G QoS flow receives the same forwarding processing (e.g., scheduling policies, queue management policies, rate shaping policies, Radio Link Control (RLC) configuration, etc.). That is, in this implementation, providing different QoS forwarding processing requires separate 5G QoS flows.

[0070] In one implementation, the DRB is the logical channel between the (R)AN and the UE and is responsible for QoS streaming. The DRB implements widely used 5G services such as enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). Figure 2 A schematic diagram of a QoS model in 5GS according to an embodiment of the present disclosure is shown. Figure 2 This illustrates the relationship between the DRB and PDU session models in 5GS. Specifically, in Figure 2In this process, three QoS flows belong to the same PDU session (i.e., PDU session A). These three QoS flows are mapped to two DRBs (i.e., DRB#1 and DRB#2) for data transmission between the UE and the (R)AN.

[0071] In one implementation, an SDAP (Service Data Adaptation Protocol) sublayer is used between the UE and the RAN. The main functions of the SDAP sublayer include mapping QoS flows to DRBs in downlink (DL) and uplink (UL) message transmissions, and marking QoS flow IDs (QFIs). Figure 3 A schematic diagram of a wireless side data plane protocol stack according to an embodiment of the present disclosure is shown. Figure 3 In this context, a single protocol entity for SDAP is configured for each individual PDU session. For example... Figure 3 As shown, the SDAP layer is located at the top of the wireless side data plane protocol stack.

[0072] In one implementation, a DRB may not be shared by QoS flows from different PDU sessions, leading to inefficient use of radio resources in the air interface between the UE and the RAN. This disclosure provides a data transmission method that allows a DRB to be shared by QoS flows from different PDU sessions.

[0073] In one implementation, QoS flows from different PDU sessions can be mapped to the same DRB for UL and / or DL ​​message transmission. That is, a DRB can be shared by QoS flows from different PDU sessions. Alternatively, if these QoS flows have the same QoS characteristics (e.g., resource type, packet delay budget (PDB), packet error rate (PER), etc.), then a single DRB can be shared by QoS flows from different PDU sessions.

[0074] Figure 4 A schematic diagram of a QoS mapping model (UL) according to an embodiment of this disclosure is shown. Figure 4 In this context, the second QoS flow (i.e., the QoS flow with QFI=2) in PDU session A and the third QoS flow (i.e., the QoS flow with QFI=3) in PDU session B share a common DRB#2 for UL and / or DL ​​message transmission between the UE and the RAN.

[0075] In the implementation for UL data transmission, the UE maps the uplink service data stream to the QoS stream of the PDU session based on the QoS rules provided by the network, and provides the corresponding QFI and PDU session ID to the Access Stratum (AS) layer in the UE. The AS layer in the UE determines the DRB used to carry the uplink data. The UE encapsulates the QFI and PDU session ID in the SDAP (sub) layer and sends the uplink data to the RAN. The RAN then determines the N3 tunnel based on the encapsulated PDU session ID and forwards the uplink data to the UPF through the determined N3 tunnel.

[0076] In one implementation, for DL ​​data transmission, the UPF maps the downlink service data stream to the QoS stream of the PDU session based on the message detection rules provided by the SMF, and sends the downlink data to the RAN through the N3 tunnel of the PDU session. The RAN encapsulates the QFI and PDU session ID in the SDAP (sub) layer and sends the downlink data to the UE. The UE then sends the downlink data to the application associated with the PDU session.

[0077] In this disclosure, a single SDAP (entity) is configured for the UE. When the RAN determines that the DRB is shared by QoS flows from different PDU sessions, the RAN provides the UE with the PDU session ID and the QFI in the DRB mapping rule via RRC signaling.

[0078] In one implementation, when / if the RAN determines that a new QoS flow is mapped to an existing DRB, the RAN modifies the DRB's MBR (Maximum Bit Rate) to accommodate the traffic of this new QoS flow. In one implementation, the QoS flow can be a non-GBR QoS flow. In one implementation, a GBR QoS flow may not be mapped to an existing DRB because the bit rate of the GBR QoS flow may not be guaranteed. In one implementation, all traffic for this new QoS flow shares the same QoS characteristics of the DRB (i.e., the same type of resource).

[0079] In one implementation, the reflective QoS function enables the UE to map UL user plane traffic to QoS flows. This is achieved by the UE creating UE-derived QoS rules based on received DL traffic. For UEs supporting reflective QoS, if the reflective QoS function is used for some traffic flows, the UE creates UE-derived QoS rules for uplink traffic based on received DL traffic. The UE can use the UE-derived QoS rules to determine the mapping of UL traffic to QoS flows. In one implementation, the UE receives a PDU session ID in the SDAP (sub) layer and determines the UE-derived QoS rules for the PDU session identified by the PDU session ID. In one implementation, the UE-derived QoS rules include / include at least one UL packet filter, QFI, and priority value.

[0080] PDU Session Establishment

[0081] Figure 5 A schematic diagram of a PDU session establishment process according to an embodiment of the present disclosure is shown. Specifically, Figure 5 The PDU session establishment process shown includes the following steps:

[0082] Step 501: The UE sends a PDU session establishment request to the AMF in the form of a NAS message, including the following information: request S-NSSAI, DNN, PDU session ID, request type, and N1 SM container.

[0083] Step 502: The AMF selects an SMF for the PDU session via the NRF or local configuration. In the case of via the NRF, the AMF provides the NRF with the DNN and S-NSSAI. Based on the received parameters, the NRF selects an SMF for the AMF and returns the service area of ​​the selected SMF.

[0084] Step 503: The AMF sends a request to the selected SMF to create an SM context, along with the PDU session ID, UE location information, access type, RAT type, operation type, and other information.

[0085] Step 504: The SMF sends a response to the AMF to create an SM context, which includes the SM context ID, in response to the SM context creation request in step 503.

[0086] Step 505: The SMF determines that PCC authorization is required and requests to establish an SM policy association with the PCF by calling the "Npcf_SMPolicyControl_Create" operation.

[0087] Step 506: The PCF makes authorization and policy decisions. Subsequently, in step 505, the PCF responds to the request via the "Npcf_SMPolicyControl_Create" response. In this response, the PCF may provide the PCC rules to the SMF. The SMF selects the appropriate UPF and requests the UPF to allocate an N3 tunnel for uplink data transmission.

[0088] Step 507: The SMF sends a “Namf_Communication_N1N2MessageTransfer” message to the AMF. This message contains items such as the PDU session ID, N2 SM information (PDU session ID, QFI, QoS profile, N3 tunnel of the UPF), and N1 SM container (PDU session establishment acceptance).

[0089] Step 508: The AMF receives the “N1N2MessageTransfer” request from the SMF. Then, the AMF sends a PDU session request and forwards the following items to the (R)AN: N2 PDU session request (N2 SM information, NAS message (PDU session ID, N1 SM container (PDU session establishment accepted))).

[0090] Step 509: The (R)AN can initiate an AN-specific signaling exchange with the UE, which is related to information received from the SMF. For example, in the case of a Next Generation RAN (NG-RAN) node, RRC reconfiguration can be performed after the UE establishes the necessary NG-RAN resources associated with the QoS profile. If the (R)AN determines that the QoS flows of this PDU session can be mapped to an existing DRB, the (R)AN adjusts the MBR (Maximum Bit Rate) of the DRB to ensure that the total bit rate of all QoS flows mapped to the DRB does not exceed the MBR of the DRB. Afterwards, the RAN sends the updated DRB mapping rules to the UE via the RRC reconfiguration process. The RAN can also send a NAS message (PDU session ID, N1 SM container (PDU session establishment accepted)) to the UE.

[0091] Step 510: (R)AN also assigns (R)AN tunnel information to the PDU session and returns an N2 PDU session response to the AMF, along with the PDU session ID, AN tunnel information, and a list of accepted and rejected QFIs.

[0092] Step 511: After receiving the N2 PDU session response from the RAN in step 510, the AMF decides to update the user's SM context. To this end, the AMF sends an update request and forwards N2 SM information, including / including the SM context ID, N2 SM information, and request type, to the SMF. The SMF receives the update request from the AMF and can return an update success response. On the other hand, the SMF can subscribe to UE mobility notifications from the AMF, which may include information such as the UE's location information and whether the UE is in a region of interest.

[0093] PDU Session Modification

[0094] Figure 6 A schematic diagram illustrating a UE-requested PDU session modification process according to an embodiment of this disclosure is shown. Specifically, Figure 6 The PDU session modification process shown includes the following steps:

[0095] Step 601: The UE initiates the PDU session modification process by transmitting a NAS message (N1 SM container (PDU session modification request (PDU session ID, packet filter, operation, requested QoS, isolation)) and / or a PDU session ID message.

[0096] Step 602: If the UE requests specific QoS processing for the selected Service Data Flow (SDF), a PDU session modification request is sent to the SMF, along with a message filter describing the SDF, the requested message filter operation on the indicated message filter, and the requested QoS.

[0097] The SMF receives the request and responds to the AMF via "Nsmf_PDUSession_UpdateSMContext". The response message includes the following items: [N2 SM Information (PDU Session ID, QFI, QoS Profile, [Alternative QoS Profile], Session-AMBR], [CN Tunnel Information], N1 SM Container (PDU Session Modification Command (PDU Session ID, QoS Rule, QoS Rule Operation, QoS Flow Level QoS Parameters Provided for QoS Flows Associated with QoS Rules When Required, Session-AMBR))].

[0098] Step 603: AMF can send N2 messages ([N2 SM information received from SMF], NAS messages (PDU session ID, N1 SM container (PDU session modification command))) to (R)AN.

[0099] Step 604: The (R)AN may initiate an AN-specific signaling exchange with the UE, which is related to information received from the SMF. For example, in the case of NG-RAN, RRC connection reconfiguration may be performed if the UE modifies the necessary (R)AN resources associated with the PDU session. Alternatively, if only an N1 SM container is received from the AMF in step 603, the (R)AN will only transmit the N1 SM container to the UE.

[0100] If the (R)AN determines that the QoS flows of this PDU session can be mapped to an existing DRB, the (R)AN adjusts the MBR of the DRB to ensure that the total bit rate of all QoS flows mapped to this DRB does not exceed the MBR of the DRB. The RAN sends the updated DRB mapping rules to the UE via the RRC reconfiguration procedure. The RAN also sends a NAS message (PDU session ID, N1 SM container (PDU session modification accepted)) to the UE.

[0101] Step 605: (R)AN can confirm the N2 PDU session request by sending an N2 PDU session confirmation (N2 SM information (list of accepted / rejected QFIs, AN tunnel information, PDU session ID, auxiliary RAT usage data), user location information) message to AMF.

[0102] Step 606: The AMF forwards the N2 SM information and user location information received from the (R)AN to the SMF via the "Nsmf_PDUSession_UpdateSMContext" service operation. The SMF responds to the AMF via the "Nsmf_PDUSession_UpdateSMContext" response.

[0103] Step 607: The SMF can update the N4 session of the UPF involved in the PDU session modification by sending an N4 session modification request message to the UPF. The UPF returns an N4 session modification / establishment response message (if any) with the updated information to the SMF.

[0104] Step 608: The UE confirms the PDU session modification command by sending a NAS message (PDU session ID, N1 SM container (PDU session modification command confirmation)) to the (R)AN.

[0105] PDU session release

[0106] Figure 7 A schematic diagram of a UE-requested PDU session release procedure according to an embodiment of this disclosure is shown. The PDU session release procedure can be used for non-roaming and roaming with Local Breakout (LBO). Specifically, Figure 7The PDU session release process shown includes the following steps:

[0107] Step 701: The UE initiates the PDU session release process by transmitting a NAS message (N1 SM container (PDU session release request (PDU session ID)), PDU session ID). The NAS message is forwarded by (R)AN to AMF and carries user location information indication.

[0108] Step 702: AMF calls the “Nsmf_PDUSession_UpdateSMContext” service operation and provides the User Location Information (ULI) received from (R)AN to SMF along with the N1 SM container.

[0109] Step 703: The SMF releases the IP address / prefix assigned to the PDU session and releases the corresponding user plane resources.

[0110] a. The SMF sends an N4 session release request (N4 session ID) message to the UPF of the PDU session. The UPF discards any remaining packets of the PDU session and releases all tunnel resources and context associated with the N4 session.

[0111] b. The UPF acknowledges the N4 session release request by transmitting an N4 session release response (N4 session ID, [small data rate control status], [APN rate control status]) message to the SMF.

[0112] Step 704: The SMF responds to the AMF via the “Nsmf_PDUSession_UpdateSMContext” response (N2 SM resource release request, N1 SM container (PDU session release command)). Note that the N2 SM resource release request is included.

[0113] Step 705: If the UE is in CM-CONNECTED state and the message received from the SMF in step 704 includes an N2SM resource release request, then the AMF transmits the SM information (N2 SM resource release request, N1 SM container) received from the SMF to the (R)AN.

[0114] Step 706: When / if the (R)AN receives an N2 SM request to release the AN resources associated with the PDU session, the (R)AN sends an AN-specific signaling exchange with the UE to release the corresponding AN resources.

[0115] When (R)AN is NG-RAN, the NAS message is sent to the UE in an RRC message and can occur if the UE releases NG-RAN resources associated with the PDU session. If NG-RAN resources (e.g., DRB) are shared by QoS flows of other existing PDU sessions, the NG-RAN does not release the NG-RAN resources, adjusts the MBR (Maximum Bit Rate) of the DRB to ensure that the total bit rate of all QoS flows mapped to the DRB does not exceed the MBR of the DRB, and sends updated DRB mapping rules to the UE via the RRC reconfiguration procedure.

[0116] Step 707: (R)AN confirms the N2 SM resource release request by sending an N2 SM resource release confirmation message to AMF containing user location information and auxiliary RAT usage data.

[0117] Step 708: The AMF calls "Nsmf_PDUSession_UpdateSMContext" (N2 SM resource release confirmation (auxiliary RAT usage data), user location information) to the SMF. The SMF responds to the AMF with the "Nsmf_PDUSession_UpdateSMContext" response.

[0118] Step 709: The UE confirms the PDU session release command by sending a NAS message (PDU session ID, N1 SM container (PDU session release confirmation)) to the (R)AN.

[0119] Figure 8 A schematic diagram of a UL message transmission process according to an embodiment of this disclosure is shown. Figure 8 The entire process shown begins with a PDU session establishment process (e.g., Figure 5 (Step 800) Establishing a PDU session and DRB. Next, the UL service data stream will be transmitted from the UE to the UPF (Step 801). For UL data transmission, in step 802, the UE maps the uplink service data stream to the QoS stream of the PDU session based on the QoS rules provided by the network, and provides the QFI and PDU session ID to the AS layer in the UE. In step 803, the AS layer in the UE determines the DRB used to carry uplink data based on the DRB mapping rules provided by the RAN. In step 804, the UE encapsulates the QFI and PDU session ID in the SDAP (sub) layer and sends the uplink data to the RAN through the air interface. In step 805, the RAN determines the corresponding N3 tunnel based on the PDU session ID and forwards the uplink data to the UPF through the determined N3 tunnel.

[0120] Figure 9A schematic diagram of a UL message transmission process according to an embodiment of this disclosure is shown. Figure 9 The entire process shown begins with a PDU session establishment process (e.g., Figure 5 (The process described in step 900) establishes a PDU session and DRB. Then, the DL service data stream / packet is transmitted from the UPF to (step 901). For DL ​​data transmission, in step 902, the UPF maps the downlink service data stream to the QoS stream of the PDU session based on the packet detection rules provided by the SMF, and in step 903, sends downlink data to the RAN through the corresponding N3 tunnel of the PDU session. In step 904, the RAN determines the DRB used to carry downlink data based on the DRB mapping rules. In step 905, the RAN encapsulates the QFI and PDU session ID in the SDAP (sub) layer and sends downlink data to the UE. The UE sends downlink data to the application associated with the PDU session.

[0121] In one implementation, the RAN may perform at least one of the following:

[0122] Receive QoS profiles for QoS flows from SMF;

[0123] Determine if the QoS flow is mapped to a new DRB or an existing DRB for another PDU session; or

[0124] Send a new DRB mapping rule to the UE, wherein the DRB mapping rule indicates that the QoS flow of this PDU session is mapped to a new DRB or an existing DRB.

[0125] In one implementation, the RAN may also perform at least one of the following:

[0126] Receive uplink data from the UE, as well as the PDU session ID and QFI;

[0127] The N3 tunnel for the PDU session is determined based on the received PDU session ID; or

[0128] Uplink data is forwarded to the UPF via the PDU session.

[0129] Alternatively, or otherwise, the RAN may perform at least one of the following:

[0130] Receive downlink data from the UPF through the N3 tunnel of the PDU session;

[0131] Determine the DRB based on the DRB mapping rules; or

[0132] The downlink data, along with the PDU session ID and QFI, is forwarded to the UE.

[0133] In one implementation, the UE may perform at least one of the following:

[0134] Receive QoS rules from SMF;

[0135] Receive DRB mapping rules from RAN, where the DRB mapping rules indicate whether the QoS flow of this PDU session is mapped to a new DRB or an existing DRB;

[0136] Receive uplink data from the application;

[0137] The QoS flow configured to carry uplink data is determined based on the QoS rules received from the SMF.

[0138] The DRB configured to carry uplink data is determined based on the DRB mapping rules received from the RAN;

[0139] Forward uplink data, as well as PDU session ID and QFI.

[0140] Figure 10 This is a schematic diagram relating to a wireless terminal 100 according to an embodiment of the present disclosure. The wireless terminal 100 may be a user equipment (UE), mobile phone, laptop computer, tablet computer, e-book reader, or portable computer system, and is not limited thereto in this embodiment. The wireless terminal 100 may include a processor 1000 (such as a microprocessor or application-specific integrated circuit (ASIC)), a storage unit 1010, and a communication unit 1020. The storage unit 1010 may be any data storage device storing program code 1012, which is accessed and executed by the processor 1000. Embodiments of the storage unit 1010 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 1020 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 1000. In one embodiment, the communication unit 1020 communicates via… Figure 10 At least one antenna 1022 shown transmits and receives signals.

[0141] In one embodiment, the storage unit 1010 and the program code 1012 may be omitted, and the processor 1000 may include a storage unit storing the program code.

[0142] The processor 1000 may implement any of the steps in the exemplary embodiments of this application on the wireless terminal 100, for example, by executing program code 1012.

[0143] The communication unit 1020 may be a transceiver. Alternatively or additionally, the communication unit 1020 may be a combination of a transmitting unit and a receiving unit configured to transmit signals to and receive signals from a wireless network node (e.g., a base station).

[0144] Figure 11 The diagram relates to a wireless network node 110 according to an embodiment of the present disclosure. The wireless network node 110 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 herein. Furthermore, the wireless network node 110 may include (perform) at least one network function, such as access and mobility management function (AMF), session management function (SMF), user location function (UPF), policy control function (PCF), application function (AF), etc. Wireless network node 110 may include processor 1100 (such as a microprocessor or ASIC), storage unit 1110, and communication unit 1120. Storage unit 1110 may be any data storage device storing program code 1112, which is accessed and executed by processor 1100. Examples of storage unit 1110 include, but are not limited to, SIM, ROM, flash memory, RAM, hard disk, and optical data storage devices. Communication unit 1120 may be a transceiver and is used to send and receive signals (e.g., messages or packets) based on the processing results of processor 1100. In this example, communication unit 1120 communicates via... Figure 11 At least one antenna 1122 shown transmits and receives signals.

[0145] In one embodiment, storage unit 1110 and program code 1112 may be omitted. Processor 1100 may include storage unit storing program code.

[0146] The processor 1100 may implement any of the steps described in the exemplary embodiments of this application on the wireless network node 110, for example, via executable program code 1112.

[0147] The communication unit 1120 may be a transceiver. Alternatively or additionally, the communication unit 1120 may be a combination of a transmitting unit and a receiving unit configured to transmit signals to and receive signals from a wireless terminal (e.g., a user equipment or another wireless network node).

[0148] Figure 12 A flowchart of a method according to an embodiment of the present disclosure is shown. Figure 12 The method shown can be used in a wireless network node (e.g., (R)AN (node) or gNB) and includes the following steps:

[0149] Step 1201: Send a DRB mapping rule to the wireless terminal, the rule indicating that the first QoS flow of the first PDU session is mapped to the common DRB to which the second QoS flow of the second PDU session is mapped.

[0150] exist Figure 12 In this context, QoS flows from different PDU sessions can share the same DRB. For example, a wireless network node can map a first QoS flow from a first PDU session to a common DRB to which a second QoS flow from a second PDU session is mapped, and send a DRB mapping rule indicating such a mapping to a wireless terminal (e.g., a UE) associated with the first PDU session.

[0151] In one implementation, a wireless network node can modify / adjust the MBR of a public DRB based on a first QoS flow of a first PDU session, for example, to ensure that the total bit rate of all QoS flows mapped to the public DRB does not exceed the MBR of the DRB.

[0152] In one implementation, the first QoS flow and / or the second QoS flow are non-GBR QoS flows.

[0153] In one implementation, the wireless network node receives uplink data from a wireless terminal on a public DRB. In this implementation, the uplink data is received along with the corresponding PDU session ID and the corresponding QFI. Based on the received PDU session ID, the wireless network node can determine the N3 tunnel and send uplink data to the UPF on the determined N3 tunnel.

[0154] In one implementation, the wireless network node receives downlink data configured to be transmitted over a public DRB. For example, the downlink data may belong to a first QoS stream or a second QoS stream. In this implementation, the wireless network node sends the downlink data located on the public DRB, along with the corresponding PDU session ID and the corresponding QFI, to the wireless terminal.

[0155] In one implementation, the PDU session ID and QFI sent / received along with the data are encapsulated in the SDAP (sub) layer. For example, the PDU session ID and QFI may be included in the SDAP header of the data.

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

[0157] Step 1301: Receive DRB mapping rules from the wireless network node, which indicate that the first QoS flow of the first PDU session is mapped to the public DRB to which the second QoS flow of the second PDU session is mapped.

[0158] In this implementation, a DRB can be shared by QoS flows from different PDU sessions. For example, a wireless terminal can receive a DRB mapping rule from a wireless network node, which indicates that a first QoS flow of a first PDU session is mapped to a common DRB to which a second QoS flow of a second PDU session is mapped.

[0159] In one implementation, the MBR of the public DRB can be adjusted / modified based on the first QoS flow (after the first QoS flow is mapped to the public DRB).

[0160] In one implementation, the first QoS flow and / or the second QoS flow are non-GBR QoS flows.

[0161] In one implementation, when uplink data (located on a public DRB) is sent to a wireless network node, the wireless terminal sends the uplink data along with the corresponding PDU session ID and QFI to indicate the PDU session associated with the uplink data.

[0162] In one implementation, the wireless terminal receives downlink data (located on a public DRB) from a wireless network node, along with the corresponding PDU session ID and QFI. The wireless terminal can thus determine the PDU session associated with the downlink data. In this implementation, the wireless terminal can also determine the QoS rules for the corresponding PDU session based on the received downlink data.

[0163] In one implementation, the PDU session ID and QFI sent / received along with the data are encapsulated in the SDAP (sub) layer. For example, the PDU session ID and QFI may be included in the SDAP header of the data.

[0164] While various embodiments of this disclosure have been described above, it should be understood that they 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 this disclosure. However, those skilled in the art will understand that this disclosure is not limited to the exemplary architectures or configurations shown, but can be implemented using various alternative architectures and configurations. Furthermore, as those skilled in the art will 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 this disclosure should not be limited to any of the exemplary embodiments described above.

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

[0166] Furthermore, those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, and symbols that may be referenced 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.

[0167] Those skilled in the art will further understand that any of the various illustrative logic blocks, units, processors, devices, circuits, methods, and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, design code of various forms of program or merged instructions (which may be referred to herein as "software" or "software unit" for convenience), or any combination of these technologies.

[0168] To clearly illustrate this interchangeability of hardware, firmware, and software, the illustrative components, blocks, units, circuits, and steps have been described above in general terms of their functionality. Whether such functionality is implemented as hardware, firmware, software, or a combination of these technologies depends on the specific application and the design constraints imposed on the system as a whole. Skilled artisans can implement the described functionality in various ways for each specific application, but such implementation decisions do not depart 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 a specified operation or function.

[0169] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, cells, 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, cells, 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, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration 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 in embodiments of this application can be implemented as software stored on a computer-readable medium.

[0170] Computer-readable media include both computer storage media and communication media. Communication media include any medium that enables the transfer of computer programs or code from one place to another. Storage media can be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.

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

[0172] Additionally, memory or other storage devices and communication components may be employed in embodiments of this disclosure. It will be understood that, for clarity, the above description has referenced various functional units and processors in describing 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, functionality illustrated as being 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 not indications of a strict logical or physical structure or organization.

[0173] Various modifications to the implementations described herein will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other implementations without departing from the scope of the claims. Therefore, this disclosure is not intended to be limited to the implementations shown herein, but is to be accorded the broadest scope consistent with the novel features and principles disclosed herein (as set forth in the claims below).

Claims

1. A wireless communication method for use in a wireless network node, the method comprising: Send a data radio bearer DRB mapping rule to the wireless terminal. The DRB mapping rule indicates that the first quality of service (QoS) flow of the first protocol data unit (PDU) session is mapped to the common DRB to which the second QoS flow of the second PDU session is mapped.

2. The wireless communication method according to claim 1, further comprising: The maximum bit rate (MBR) of the public DRB is modified based on the first QoS flow of the first PDU session.

3. The wireless communication method according to claim 1 or 2, wherein, The first QoS stream of the first PDU session is a non-guaranteed bit rate QoS stream.

4. The wireless communication method according to any one of claims 1 to 3, further comprising: The wireless terminal receives uplink data located on the public DRB, the PDU session identifier of the uplink data, and the QoS flow identifier (QFI) of the uplink data. The N3 tunnel is determined based on the PDU session ID in the uplink data, and The uplink data is sent to the user plane function using the determined N3 tunnel.

5. The wireless communication method according to any one of claims 1 to 4, further comprising: Receive downlink data configured to be transmitted via the public DRB from the user plane function, and The wireless terminal is sent downlink data located on the public DRB, the PDU session identifier of the downlink data, and the QoS flow identifier (QFI) of the downlink data.

6. The wireless communication method according to claim 4 or 5, wherein, The PDU session identifier and the QFI are located in the Service Data Adaptation Protocol (SDAP) header.

7. A wireless communication method used in a wireless network node, the method comprising: The data radio bearer DRB mapping rule is received from the wireless network node. The DRB mapping rule indicates that the first quality of service (QoS) flow of the first protocol data unit (PDU) session is mapped to the common DRB to which the second QoS flow of the second PDU session is mapped.

8. The wireless communication method according to claim 7, wherein, The maximum bit rate (MBR) of the public DRB is modified based on the first QoS flow of the first PDU session.

9. The wireless communication method according to claim 7 or 8, wherein, The first QoS stream of the first PDU session is a non-guaranteed bit rate QoS stream.

10. The wireless communication method according to any one of claims 7 to 9, further comprising: Send uplink data located on the public DRB, the PDU session identifier of the uplink data, and the QoS flow identifier (QFI) of the uplink data to the wireless network node.

11. The wireless communication method according to any one of claims 7 to 10, further comprising: The wireless network node receives downlink data located on the public DRB, the PDU session identifier of the downlink data, and the QoS flow identifier (QFI) of the downlink data.

12. The wireless communication method according to claim 10 or 11, wherein, The PDU session identifier and the QFI are located in the Service Data Adaptation Protocol (SDAP) header.

13. A wireless network node, comprising: The communication unit is configured to send a data radio bearer DRB mapping rule to a wireless terminal, the DRB mapping rule indicating that a first quality of service (QoS) flow of a first protocol data unit (PDU) session is mapped to a common DRB to which a second QoS flow of a second PDU session is mapped.

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

15. A wireless terminal, comprising: The communication unit is configured to receive data radio bearer DRB mapping rules from a wireless network node, the DRB mapping rules indicating that a first quality of service (QoS) flow of a first protocol data unit (PDU) session is mapped to a common DRB to which a second QoS flow of a second PDU session is mapped.

16. The wireless terminal of claim 15, further comprising a processor configured to perform the wireless communication method of any one of claims 8 to 12.

17. A computer program product comprising computer-readable program medium code stored thereon, the code, when executed by a processor, causing the processor to implement the wireless communication method according to any one of claims 1 to 16.

Images