Radio access network node, session establishment method, session data usage statistics method, communication device, and storage medium

By introducing data plane application functionality into the wireless access network nodes, the problem of cellular networks being unable to support AI, ISAC, and DT data transmission was solved, enabling large data packets and high-speed end-to-end transmission, as well as traffic statistics and billing, thereby improving the network's data service capabilities.

WO2026232555A1PCT designated stage Publication Date: 2026-11-12SHENZHEN TCL NEW-TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2025/094025
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-09
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

In existing technologies, cellular networks cannot effectively support the new data transmission requirements after the introduction of AI, ISAC and DT, including arbitrary topology, in-band processing, large data packet transmission, low latency and high speed, etc., and BS lacks session processing capabilities and traffic statistics functions, and cannot perform data service billing.

Method used

Introducing data plane application functions into wireless access network nodes, including data management function (DMF), data processing function (DPF), and data storage function (DSF), supports data flow orchestration, traffic statistics, and data processing, enabling end-to-end data transmission and billing.

Benefits of technology

It enables support for large data packets and high-speed data transmission, and can perform traffic statistics and billing, meeting the data transmission needs of AI, ISAC and DT, and improving the network's data service capabilities.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025094025_12112026_PF_FP_ABST
    Figure CN2025094025_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present application provides a radio access network node, a session establishment method, a session data usage statistics method, a communication device, and a storage medium. The radio access network node is configured to have a data plane application function. The data plane application function comprises: a data management function (DMF) node, a data processing function (DPF) node, and a data storage function (DSF) node. The DMF node is used for managing the DPF node and / or the DSF node, and is used for at least one of the following functions: data flow orchestration; data traffic statistics; a data collection task configuration; or data reporting triggering. The DPF node is used for performing a DPF. The DSF node is used for performing the DPF.
Need to check novelty before this filing date? Find Prior Art

Description

Wireless access network nodes, session establishment methods, methods for calculating session data usage, communication equipment, and storage media. Technical Field

[0001] This application relates to the field of wireless communication technology, specifically to a wireless access network node, a session establishment method, a method for statistically analyzing session data usage, a communication device, and a storage medium. Background Technology

[0002] With the continuous development of mobile cellular networks, in order to meet the ever-increasing business needs of users, cellular networks no longer only provide communication services, but also further enhance communication capabilities and user experience by introducing more new technologies (such as artificial intelligence (AI), communication-sensing integration (ISAC), and digital twins (DT)).

[0003] However, the introduction of AI, ISAC, and DT has also brought new demands to the network. Specifically, in the past, the transmitted data was either signaling data used for network transmission control (i.e., control plane data) or user service data (i.e., user plane data). With the introduction of AI, ISAC, and DT, the network now transmits AI, ISAC, and DT-related data (such as AI model parameter data, AI model gradient information, training data, inference data, monitoring data, and sensing data). This data is neither control plane data nor user plane data, but a new type of data. At the same time, the transmission requirements of this new data type differ from the existing control plane and user plane data transmission requirements. These requirements include: arbitrary topology, in-path processing, large packet transmission, low latency, high speed, and high reliability. Existing control plane and user plane data transmission schemes cannot fully support these requirements.

[0004] Therefore, communication networks need to support data service functions to provide data services to data requesters. Summary of the Invention

[0005] This application provides a wireless access network node, a session establishment method, a method for calculating session data usage, a communication device, and a storage medium to address the problems existing in the prior art.

[0006] On one hand, this application provides a wireless access network node. The wireless access network node is configured with data plane application functions; these functions include: a data management function (DMF) node, a data processing function (DPF) node, and a data storage function (DSF) node; the DMF node manages the DPF node and / or the DSF node, and performs at least one of the following functions: orchestrating data flow; data traffic statistics; data collection task configuration; or data reporting triggering; the DPF node performs data processing functions; and the DSF node performs data processing functions.

[0007] On the other hand, this application provides a session establishment method, executed by a first node. The method includes: receiving a session establishment request from a second node, wherein the session establishment request includes: transmission type information, which indicates whether the transmission type is user plane transmission or data plane transmission; and / or data task information, which indicates the data task corresponding to the session.

[0008] On the other hand, this application provides a session establishment method, executed by a second node. The method includes: sending a session establishment request to a first node, wherein the session establishment request includes transmission type information and / or data task information, the transmission type information indicating whether the transmission type is user plane transmission or data plane transmission; the data task information indicating the data task corresponding to the session; the first node is a radio access network node, and the second node is a user equipment.

[0009] On the other hand, this application provides a method for statistically analyzing session data usage, executed by a radio access network node. The method includes: acquiring a Data Resource Usage Reporting Rule (URR); performing data usage statistics based on the URR; and sending a data usage report based on the statistical data usage.

[0010] On the other hand, this application provides a communication device including a processor and a memory, wherein the memory stores program instructions that, when executed by the processor, can implement any of the aforementioned methods.

[0011] On the other hand, this application provides a storage medium storing program instructions that, when executed by a processor, can implement any of the aforementioned methods. Attached Figure Description

[0012] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0013] Figure 1 illustrates a use case diagram of an OAM unit requesting air interface data from a data service function network element in a mobile network.

[0014] Figure 2 illustrates a use case diagram of an AI function network element requesting air interface data from a data service function network element in a mobile network.

[0015] Figure 3 shows a schematic diagram of the architecture of a wireless access network node (e.g., a base station, BS) that includes internal data plane application functions.

[0016] Figure 4 shows an example of an interface scheme when a wireless access network node contains data plane application functions.

[0017] Figure 5 shows a schematic diagram of the protocol stack for the control plane interface between base stations.

[0018] Figure 6 shows a schematic diagram of one implementation of the protocol stack for the data plane interface between base stations.

[0019] Figure 7 illustrates another implementation of the protocol stack for the data plane interface between base stations.

[0020] Figure 8 shows a schematic diagram of the protocol stack for the control plane interface between the base station and the core network.

[0021] Figure 9 shows another example of an interface scheme when a wireless access network node contains data plane application functions.

[0022] Figure 10 illustrates one implementation of the protocol stack for the control plane interface and / or data plane interface involved in Figure 9.

[0023] Figure 11 illustrates another implementation of the protocol stack for the control plane interface and / or data plane interface involved in Figure 9.

[0024] Figure 12 shows a schematic diagram of the architecture when multiple radio access network nodes (e.g., base stations BS) share independent RAN data plane application functions.

[0025] Figure 13 shows an example of an interface scheme when deploying data plane application functions outside a wireless access network node.

[0026] Figure 14 illustrates one implementation of the protocol stack for the control plane interface (such as Xm-C) between the BS and RAN data plane application functions.

[0027] Figure 15 illustrates one implementation of the protocol stack for the control plane interface (such as NGD-C) between the RAN data plane application functions and the CN.

[0028] Figure 16 shows another example of an interface scheme when deploying data plane application functions outside a wireless access network node.

[0029] Figure 17 illustrates a flowchart of a session establishment method according to an embodiment of this application.

[0030] Figure 18 illustrates a session establishment request flow that introduces data plane application functionality according to an embodiment of this application.

[0031] Figure 19 illustrates a flowchart of the connection establishment or restoration process prior to the session establishment process according to an embodiment of this application.

[0032] Figure 20 illustrates a schematic diagram of the request and response process for user subscription data according to an embodiment of this application.

[0033] Figure 21 illustrates a flowchart of the authentication / authorization process for a session according to an embodiment of this application.

[0034] Figure 22 illustrates a flowchart of the request and response of a session dynamic policy according to an embodiment of this application.

[0035] Figure 23 illustrates a flowchart of session configuration and response according to an embodiment of this application.

[0036] Figure 24 illustrates a flowchart of a method for statistical analysis of session data usage according to an embodiment of this application.

[0037] Figure 25 illustrates a traffic statistics and reporting process applied to a wireless access network node according to an embodiment of this application.

[0038] Figure 26 illustrates a flowchart of a wireless access network node obtaining a data usage report rule according to an embodiment of this application.

[0039] Figure 27 illustrates a traffic statistics and reporting process applied to a wireless access network node according to another embodiment of this application.

[0040] Figure 28 illustrates a flowchart of a wireless access network node obtaining a data usage report rule according to another embodiment of this application.

[0041] Figure 29 illustrates a flowchart of a full lifecycle data management scheme according to an embodiment of this application.

[0042] Figure 30 illustrates a flowchart of a full lifecycle data management scheme according to another embodiment of this application.

[0043] Figure 31 shows a schematic diagram of the structure of a communication device according to an embodiment of this application. Detailed Implementation

[0044] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0045] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0046] The main abbreviations involved in this application and their explanations are as follows:

[0047] This application mainly focuses on the scenario requirements of data transmission in access networks. The following uses will illustrate the new requirements of data transmission in access network scenarios.

[0048] Use Case 1:

[0049] The OAM (Operation, Administration, and Maintenance) unit needs to optimize the network, requiring a large amount of air interface channel information as the basis for optimization. Therefore, the OAM requests air interface data from the data service function network elements in the mobile network. A use case scenario is shown in Figure 1. The data service function can be located within the BS (Base Station).

[0050] The data service function network element sends data collection requests to one or more designated BSs (base stations) based on the data requirements of the OAM. The BS then configures data collection and reporting rules for designated UEs (User Equipment / Users) or UEs that meet the criteria, based on the data collection requests. If the designated UE or a UE that meets the criteria is in an idle or inactive state, the BS must first restore such UEs to a connected state.

[0051] When the UE completes data acquisition and meets the reporting rules, it transmits the collected air interface channel information to the BS. If necessary, the BS then transmits it to the data processing unit for further data processing (such as fusion and extraction). After processing, the data processing unit delivers the processed data to the OAM for network optimization.

[0052] Use Case 2:

[0053] The data requesting UE needs to deploy an AI-based beam management model and requests the corresponding AI model from the AI ​​function network element. If the AI ​​function network element does not have a model that meets the UE's requirements locally, it needs to train a model for the UE to meet its needs. First, the AI ​​function network element needs a large amount of relevant air interface channel data for training. Therefore, the AI ​​function network element requests air interface channel data for beam management model training from the data service function network element. The use case scenario is shown in Figure 2. The data service function and the AI ​​function can reside within the BS (Browser / Server).

[0054] Similar to Use Case 1, the data service function network element requests data collection from one or more designated BSs based on the needs of the AI ​​function network element. The BS then configures data collection and reporting rules for designated UEs or UEs that meet the criteria, based on the data collection request. When the UE completes data collection and meets the reporting rules, the UE transmits the collected air interface channel information to the BS.

[0055] Since the air interface data transmission during the data acquisition process serves the needs of the data requesting UE, the UE can be charged based on the usage of network resources during air interface transmission.

[0056] Additionally, if necessary, the BS can transmit the data to the data processing unit for further data processing (such as fusion and extraction). After processing, the data processing unit delivers the processed data to the AI ​​functional network element for model training.

[0057] Analysis of the above use cases reveals the following requirements:

[0058] 1) The network needs to support data service functions to provide data services to data requesters and complete the full lifecycle management of data by orchestrating data collection and processing processes.

[0059] 2) The UE and BS need to support the transmission of large data packets or high-speed data.

[0060] 3) When data services benefit the UE or AF, the network can perform traffic statistics and billing based on network resource usage.

[0061] In existing technical standards, the establishment of a PDU session is initiated by the User Equipment (UE). The following is a brief explanation of the steps:

[0062] 1) Step 1: The UE first sends a session establishment request (PDU Session Establishment Request) to the AMF.

[0063] 2) Step 2: If there is no available SMF locally in the AMF, the AMF will request an SMF from the NRF based on the DNN (Destination Network Address), S-NSSAI (Slice Information), PLMN ID and other information in the UE's session establishment request. The NRF will then return one or more available SMF addresses.

[0064] 3) Step 3: AMF sends a PDU session establishment request message to SMF through the SBI interface.

[0065] 4) Step 4: If the SMF does not have user contract data locally, the SMF needs to obtain user contract data from the UDM. For details, please refer to the supplementary explanation of this process later.

[0066] 5) Step 5: The SMF responds to the AMF with the SM context establishment request. From the message content, this means informing the AMF that the SM context establishment request was successfully responded to and sending the SM context identifier (ID) to the AMF.

[0067] 6) Step 6: During the session establishment process, the SMF needs to authenticate and authorize the session initiated by the UE. For details, please refer to the supplementary explanation of this process later.

[0068] 7) Step 7a: If dynamic PCC is used, SMF needs to select PCF; otherwise, SMF can directly apply the local policy.

[0069] 8) Step 7b: SMF obtains dynamic policies from PCF. For details, please refer to the supplementary explanation of this process later.

[0070] 9) Step 8: SMF first selects the SSC mode of the PDU session, and then selects UPF.

[0071] 10) Step 9: When the Policy Control Request Trigger condition is met, the SMF will initiate the SM Policy Association Modification process, which involves obtaining the updated PCC rules.

[0072] 11) Step 10a: The SMF configures session parameters (N4 Session Establishment / Modification Request) to the UPF based on the PCC rules obtained from the PCF, which involves PDR, FAR, URR (Usage Report Rule), QER, etc.

[0073] 12) Step 10b: The UPF responds to the SMF's configuration, and at the same time, the UPF will feed back the TEID of the N3 interface to the SMF for the uplink GTP-U transmission of the gNB.

[0074] 13) Step 11: The SMF transmits session configuration to the gNB and UE according to the PCC rules and the GTP-U parameters fed back by the UPF. This transmission is forwarded by the AMF.

[0075] 14) Step 12: The AMF transmits the session configuration obtained from the SMF to the gNB. This message includes the gNB's configuration information and the UE's configuration information. The gNB configures the uplink N3 interface according to the SMF's session configuration information, establishes the uplink link from the gNB to the UPF, and generates the air interface configuration for the session.

[0076] 15) Step 13: The gNB forwards the NAS message received from the AMF in step 12 to the UE, and establishes a bidirectional session bearer with the UE through RRC configuration. The RRC configuration setting depends on the QoS rules in the N2 session management information received by the gNB from the SMF in step 12.

[0077] 16) Step 14: The gNB responds to the AMF, including sending the gNB downlink session receive parameters on the N3 interface to the SMF.

[0078] 17) Step 15: The AMF forwards the N2 session management information received from the gNB in ​​step 14 to the SMF, including the downlink session reception parameters of the gNB on the N3 interface.

[0079] 18) Step 16a: The SMF configures the UPF with the downlink session receive parameters (AN Tunnel Info) of the gNB on the N3 interface through the N4 interface (N4 Session Modification procedure). After the UPF obtains the downlink session receive parameters of the gNB on the N3 interface, it can establish a downlink link between the UPF and the gNB.

[0080] 19) Step 16b: UPF responds to SMF (N4 Session Modification Response).

[0081] 20) Step 17: The SMF responds to the AMF, indicating whether the SM context update was successful or failed.

[0082] The existing standard specifies the following procedure for requesting and responding to user subscription data: During session establishment, the Session Management Function (SMF) requests subscription data from the User Data Management (UDM) via Nudr_DM_Query. If the UDM does not have this data, it requests the subscription data from the User Data Repository (UDR) via Nudm_SDM_Get and forwards the obtained subscription data to the SMF. Simultaneously, the SMF can also use Nudm_SDM_Subscribe to notify the UDM when subscription data changes, and the UDM can also use Nudr_DM_subscribe to notify the UDR when subscription data changes.

[0083] The existing standards specify the following regarding session authentication / authorization procedures: During session establishment, the SMF needs to authenticate and authorize the User Equipment (UE) initiating the session. This authentication and authorization is primarily handled by Data Network Authentication, Authorization, and Accounting (DN-AAA), which can be performed either within the 5G core network (5GC) or externally (i.e., the data network, DN).

[0084] The existing standards specify the following regarding the session policy request and response process:

[0085] 1) During the session establishment process, the SMF requests the policy and charging control (PCC) rules corresponding to the session from the Policy Association Establishment (Npcf_SMPolicyControl_Create request) process.

[0086] 2) If PCF does not have subscribed data, it needs to query and retrieve it from UDR through the Nudr_DM_Query service process.

[0087] 3) If the PCF's policy decisions depend on the policy counter status of the Charging Function (CHF), the PCF needs to initialize a policy counter status report to the CHF or retrieve an existing policy counter status report.

[0088] 4) PCF makes strategic decisions.

[0089] 5) PCF sends the PCC rules corresponding to the session to SMF through Npcf_SMPolicyControl_Create Response.

[0090] Furthermore, the existing standard specifies the following procedure for network resource usage statistics and reporting: The SMF collects traffic usage information from the UPF and sends the results to the CHF for billing. Simultaneously, the PCF and CHF also exchange billing information, and the PCF adjusts transmission policies (rate limiting, session termination, etc.) based on the user's remaining quota.

[0091] Specifically, the following is the process of UPF reporting data usage reports from SMF to CHF:

[0092] 1) UPF will detect traffic (such as by QoS flow, PDU session or user level) and record usage (such as data volume and duration) according to URR (Usage Reporting Rules).

[0093] 2) When the triggering conditions (such as threshold, time, command, event) are met, the UPF sends a usage report to the SMF through the N4 interface, which includes: user ID, PDU session ID, timestamp, data volume, traffic type, QoS indicators, etc.

[0094] 3) The SMF receives the usage report from the UPF and transmits traffic statistics to the CHF in real time through the Nchf_ConvergedCharging service to achieve online billing.

[0095] The following is the process by which the PCF specifies dynamic rules based on real-time billing information, network status, and static user subscription data, and then distributes them to the UPF via the SMF:

[0096] 1) The PCF generates billing and transmission policies (such as those based on service type, DNN, and S-NSSAI) based on operator configuration, network status, user subscription data, and remaining user quota, and distributes them to the SMF through PCC (Policy and Charging Control) rules. PCC rules include transmission policy control and billing control.

[0097] 2) SMF converts PCC rules into UPF-executable detection and reporting rules (such as PDR / FAR / URR / QER, etc.), and configures the UPF through the N4 interface. URR contains information such as detection type, quota, and triggering conditions (such as quota exhaustion). QER contains QoS rule information such as maximum rate and guaranteed rate.

[0098] Furthermore, CHF can send billing information to PCF based on threshold-triggered reporting. Since it uses the SBI interface, PCF will respond with a response message. CHF can report billing information to PCF according to specified thresholds.

[0099] The applicant has discovered several technical problems in the prior art.

[0100] One potential technical issue is that the existing RAN architecture does not support data plane functions. Specifically, in the current standard, the BS (Base Station) lacks session handling capabilities (i.e., PDU handling), thus it cannot serve as the endpoint of session transmissions and can only act as a forwarding node. Furthermore, the BS does not internally support various data plane functions, such as data management, data processing, data storage, and data transmission. Simultaneously, the BS cannot perform traffic statistics on data transmissions to influence user billing processes. On the other hand, for the RAN, there is no independent data plane function node to support the RAN's related data tasks.

[0101] Another potential technical issue is that the existing session establishment process does not support end-to-end direct data transmission between the BS and UE. Existing standards support data transmission based on the control plane and user plane; however, the control plane's transmission capacity is limited and cannot support the needs of large data packets or high-speed data transmission. For user plane-based data transmission, existing standards only support session establishment between the UE and UPF, not between the UE and BS.

[0102] Another potential technical issue is that existing standards do not support traffic statistics and reporting for data service billing between the BS and UE. Currently, the related billing functions for traffic statistics are only implemented in the UPF, which then reports data usage to the SMF based on the URR. The UPF's URR can also be configured by the SMF. However, when data transmission only occurs between the UE and BS, the data does not pass through the UPF, making it impossible for the UPF to perform data usage statistics. Furthermore, existing BSs only perform transparent forwarding of user plane data and do not support data usage statistics and reporting, thus failing to support data service billing.

[0103] To address one or more of the technical problems described above, this application designs a RAN architecture scheme and corresponding interfaces that support data plane functions for the scenario requirements of data transmission between UE and BS, thereby supporting the RAN's data plane management / processing / storage / transmission functions.

[0104] Specifically, this application provides a wireless access network node. The wireless access network node is configured with data plane application functions. These data plane application functions include: a Data Management Function (DMF) node, a Data Processing Function (DPF) node, and a Data Storage Function (DSF) node. The DMF node manages the DPF node and / or the DSF node, and performs at least one of the following functions: orchestrating data flow; data traffic statistics; configuring data collection tasks; or triggering data reporting. The DPF node performs the data processing function. The DSF node performs the data processing function.

[0105] The data plane application function is deployed inside the radio access network node, or in a data plane application function network element shared by multiple radio access network nodes.

[0106] In some embodiments, the radio access network node includes a control plane interface and a data plane interface for connecting to other radio access network nodes or other independent data plane application function nodes. The control plane interface provides one or more of the following functions: data transmission session management, data acquisition configuration, data retrieval, data storage, data processing, data node management, and data orchestration. The data plane interface is used for data transmission.

[0107] In some embodiments, the radio access network node includes a control plane interface and a data plane interface for connecting to the core network. The control plane interface provides one or more of the following functions: data transmission session management, data acquisition configuration, data retrieval, data storage, data processing, data node management, and data orchestration. The data plane interface is used for data transmission.

[0108] The following is a detailed description with reference to the accompanying drawings. Figure 3 shows a schematic diagram of the architecture of a radio access network node (e.g., a base station, BS) that includes internal data plane application functions. In the diagram, dashed lines represent control plane channels, double-dotted lines represent data plane channels, and solid lines represent user plane channels. This radio access network node may include one or more of the following network element functions.

[0109] 1) Radio Access Network Data Management Function (RAN DMF): Data management function.

[0110] a) Responsible for managing data plane application functions such as DPF and DSF within the data plane application functions, and responsible for orchestrating data flow (i.e., the data lifecycle).

[0111] b) Responsible for data traffic collection and reporting traffic statistics to CHF, i.e. possessing some of the functions of the original SMF, such as session management, billing, traffic data collection, policy and QoS control, etc.

[0112] c) Responsible for configuring data collection tasks and triggering data reporting.

[0113] Both the RAN and the core network (CN) can have DMFs. The RAN's DMF can be labeled as RAN DMF (meaning that the data plane application function is within the BS).

[0114] 2) DP: Data Plane Protocol Stack Process. Responsible for data transmission and data traffic statistics (i.e., possessing some of the functions of the original UPF).

[0115] 3) RAN DPF: Data processing function, scheduled by the DPF of RAN and / or CN.

[0116] 4) RAN DSF: Data storage function, scheduled by the DMF of RAN and / or CN.

[0117] 5) CP and UP correspond to the control plane protocol stack procedure and the user plane protocol stack procedure, respectively.

[0118] Figure 4 illustrates an example of an interface scheme when a radio access network node includes data plane application functions. As shown in Figure 4, the interface between the BS (10 in Figure 4) can include one or more of the following interfaces: control plane interface (e.g., Xn-C), user plane interface (e.g., Xn-U), and data plane interface (e.g., Xn-D). The explanation is as follows:

[0119] 1) The control plane interface (such as Xn-C) can provide one or more of the following functions: data transmission session management functions (such as establishing, updating, and / or releasing), data acquisition configuration functions, data retrieval functions, data storage functions, data processing functions, data node management functions, data orchestration functions, etc.

[0120] 2) Data plane interfaces (such as Xn-D) can provide one or more of the following functions: data transmission, etc. The content of the data transmission can include one or more of the following: AI model parameters, training data, inference data, monitoring data, perception data, etc.

[0121] Figure 5 shows a schematic diagram of the protocol stack for the control plane interface between base stations. For example, the control plane interface can be an Xn-C interface.

[0122] Figure 6 illustrates one implementation of the protocol stack for the data plane interface between base stations. Figure 7 illustrates another implementation of the protocol stack for the data plane interface between base stations. For example, the data plane interface could be an Xn-D interface.

[0123] Furthermore, the interface between the BS and CN (as shown in Figure 4, 20) can include one or more of the following interfaces: control plane interface (e.g., NG-C), user plane interface (e.g., NG-U), and data plane interface (e.g., NG-D). The explanation is as follows:

[0124] 1) The control plane interface (such as NG-C) can provide one or more of the following functions: data transmission session management functions (such as establishing, updating, and / or releasing), data acquisition configuration functions, data retrieval functions, data storage functions, data processing functions, data node management functions, data orchestration functions, etc.

[0125] 2) Data plane interfaces (such as NG-D) can provide one or more of the following functions: data transmission, etc. The content of the data transmission can include one or more of the following: AI model parameters, training data, inference data, monitoring data, perception data, etc.

[0126] 3) The BS can interact with one or more of the following functional network elements of the CN through the control plane interface (such as NG-C): AMF, DMF, DSF, DPF, etc.

[0127] 4) The BS can interact with one or more of the following functional network elements of the CN through the data plane interface (such as NG-D): DMF, DSF, DPF, etc.

[0128] Figure 8 illustrates the protocol stack of the control plane interface between the base station and the core network. For example, the control plane interface can be an NG-C interface. Furthermore, the protocol stack of the data plane interface (e.g., NG-D) between the base station and the core network can be as shown in Figure 6 or Figure 7.

[0129] Figure 9 illustrates another example of an interface scheme when a radio access network node includes data plane application functions. As shown in Figure 9, the BS interface (30 in Figure 9) and / or the CN interface (40 in Figure 9) can include one or more of the following interfaces: control plane interface and data plane interface. The explanation is as follows:

[0130] 1) The control plane interface can provide one or more of the following functions: data transmission session management (such as establishing, updating, and / or releasing), data acquisition configuration, data retrieval, data storage, data processing, data node management, and data orchestration.

[0131] 2) The data plane interface can provide one or more of the following functions: data transmission, etc. The content of the data transmission may include one or more of the following: AI model parameters, training data, inference data, monitoring data, perception data, etc.

[0132] 3) The BS can interact with one or more of the following functional network elements of the CN through the control plane interface and / or data plane interface: AMF, DMF, DSF, DPF, etc.

[0133] It should be understood that the control plane interface and data plane interface shown in Figure 9 can use different transmission protocols.

[0134] Figure 10 illustrates one implementation of the protocol stack for the control plane interface and / or data plane interface involved in Figure 9. Figure 11 illustrates another implementation of the protocol stack for the control plane interface and / or data plane interface involved in Figure 9.

[0135] Figure 12 illustrates the architecture of multiple radio access network nodes (e.g., base stations, BS) sharing independent RAN data plane application functions. In this implementation, the data plane application functions (RAN DF) are deployed outside the BS. Dashed lines represent control plane channels, double-dotted lines represent data plane channels, and solid lines represent user plane channels. This radio access network node may include one or more of the following network element functions.

[0136] 1) Radio Access Network Data Plane Application Function Data Management Function (RAN DF DMF): Data management function.

[0137] a) Responsible for managing data plane application functions such as DPF and DSF within the data plane application functions, and responsible for orchestrating data flow (i.e., the data lifecycle).

[0138] b) Responsible for data traffic collection and reporting traffic statistics to CHF, i.e. possessing some of the functions of the original SMF, such as session management, billing, traffic data collection, policy and QoS control, etc.

[0139] c) Responsible for configuring data collection tasks and triggering data reporting.

[0140] Both RAN and CN can have DMFs. The RAN's DMF can be labeled as RAN DF DMF (meaning that the data plane application function is outside the BS).

[0141] 2) DP: Data Plane Protocol Stack Process. Responsible for data transmission and data traffic statistics (i.e., possessing some of the functions of the original UPF).

[0142] 3) RAN DF DPF: Data processing function, scheduled by the DMF of RAN and / or CN.

[0143] 4) RAN DF DSF: Data storage function, scheduled by the DMF of RAN and / or CN.

[0144] 5) CP and UP correspond to the control plane protocol stack procedure and the user plane protocol stack procedure, respectively.

[0145] Figure 13 illustrates an example of an interface scheme when deploying data plane application functions externally to a radio access network node. As shown in Figure 13, the interface between the BS (as shown in 51 in Figure 13) can include one or more of the following interfaces: control plane interface (e.g., Xn-C), data plane interface (e.g., Xn-D), and user plane interface (e.g., Xn-U). The explanation is as follows:

[0146] 1) The control plane interface (such as Xn-C) can provide one or more of the following functions: data transmission session management functions (such as establishing, updating, and / or releasing), data acquisition configuration functions, data retrieval functions, data storage functions, data processing functions, data node management functions, data orchestration functions, etc.

[0147] 2) Data plane interfaces (such as Xn-D) can provide one or more of the following functions: data transmission, etc. The content of the data transmission can include one or more of the following: AI model parameters, training data, inference data, monitoring data, perception data, etc.

[0148] The protocol stack for the control plane interface (such as Xn-C) can be as shown in Figure 5. The protocol stack for the data plane interface (Xn-D) can be as shown in Figure 6 or Figure 7.

[0149] Furthermore, the interface between the BS and RAN data plane application functions (53 in Figure 13) can include one or more of the following interfaces: control plane interface (e.g., Xm-C), data plane interface (e.g., Xm-D), and user plane interface (e.g., Xm-U). The explanation is as follows:

[0150] 1) The control plane interface (such as Xm-C) can provide one or more of the following functions: data transmission session management functions (such as establishing, updating, and / or releasing), data acquisition configuration functions, data retrieval functions, data storage functions, data processing functions, data node management functions, data orchestration functions, etc.

[0151] 2) Data plane interfaces (such as Xm-D) can provide one or more of the following functions: data transmission, etc. The content of the data transmission can include one or more of the following: AI model parameters, training data, inference data, monitoring data, perception data, etc.

[0152] The protocol stack for the control plane interface (such as Xm-C) can be as shown in Figure 14. The protocol stack for the data plane interface (such as Xm-D) can be as shown in Figure 6 or Figure 7.

[0153] Furthermore, the interface between the BS and CN (as shown in 52 of Figure 13) can include one or more of the following interfaces: control plane interface (such as NG-C), data plane interface (such as NG-D), and user plane interface (such as NG-U). The explanation is as follows:

[0154] 1) The control plane interface (such as NG-C) can provide one or more of the following functions: data transmission session management functions (such as establishing, updating, and / or releasing), data acquisition configuration functions, data retrieval functions, data storage functions, data processing functions, data node management functions, data orchestration functions, etc.

[0155] 2) Data plane interfaces (such as NG-D) can provide one or more of the following functions: data transmission, etc. The content of the data transmission can include one or more of the following: AI model parameters, training data, inference data, monitoring data, perception data, etc.

[0156] 3) BS and / or RAN data plane application functions can interact with one or more of the following functional network elements of CN through the control plane interface (such as NG-C): AMF, DMF, DSF, DPF, etc.

[0157] 4) BS and / or RAN data plane application functions can interact with one or more of the following functional network elements of CN through data plane interfaces (such as NG-D): DMF, DSF, DPF, etc.

[0158] The protocol stack for the control plane interface (such as NG-C) can be as shown in Figure 8. The protocol stack for the data plane interface (such as NG-D) can be as shown in Figure 6 or Figure 7.

[0159] Furthermore, the interface between the RAN data plane application functions and the CN (as shown by 54 in Figure 13) can include one or more of the following interfaces: control plane interface (such as NGD-C), data plane interface (such as NGD-D), and user plane interface (such as NGD-U). The explanation is as follows:

[0160] 1) The control plane interface (such as NGD-C) can provide one or more of the following functions: data transmission session management functions (such as establishing, updating, and / or releasing), data acquisition configuration functions, data retrieval functions, data storage functions, data processing functions, data node management functions, data orchestration functions, etc.

[0161] 2) Data plane interfaces (such as NGD-D) can provide one or more of the following functions: data transmission, etc. The content of data transmission can include one or more of the following: AI model parameters, training data, inference data, monitoring data, perception data, etc.

[0162] 3) BS and / or RAN data plane application functions can interact with one or more of the following functional network elements of CN through the control plane interface (such as NGD-C): AMF, DMF, DSF, DPF, etc.

[0163] 4) BS and / or RAN data plane application functions can interact with one or more of the following functional network elements of CN through data plane interfaces (such as NGD-D): DMF, DSF, DPF, etc.

[0164] The protocol stack for the control plane interface (such as NGD-C) can be as shown in Figure 15. The protocol stack for the data plane interface (such as NGD-D) can be as shown in Figure 6 or Figure 7.

[0165] Figure 16 illustrates another example of an interface scheme when deploying data plane application functions externally to a radio access network node. As shown in Figure 16, the RAN data plane application function interface (63 in Figure 16), the CN interface (62 in Figure 16), and / or the BS interface (61 in Figure 16) can be one or more of the following interfaces: control plane interface, data plane interface. The explanation is as follows:

[0166] 1) The control plane interface can provide one or more of the following functions: data transmission session management (such as establishing, updating, and / or releasing), data acquisition configuration, data retrieval, data storage, data processing, data node management, and data orchestration.

[0167] 2) The data plane interface can provide one or more of the following functions: data transmission, etc. The content of the data transmission may include one or more of the following: AI model parameters, training data, inference data, monitoring data, perception data, etc.

[0168] 3) BS and / or RAN data plane application functions can interact with one or more of the following functional network elements of CN through the control plane interface and / or data plane interface: AMF, DMF, DSF, DPF, etc.

[0169] It should be understood that the control plane interface and data plane interface in the embodiment shown in Figure 16 can use different transmission protocols.

[0170] The protocol stack of the control plane interface and / or data plane interface can be implemented as shown in Figure 10 or Figure 11.

[0171] In this application, to facilitate the differentiation of data plane application functions in different scenarios and locations, when the data plane application function is within the BS, DMF, DPF, and DSF can be referred to as RAN DMF, RAN DPF, and RAN DSF. When the data plane application function is outside the BS, DMF, DPF, and DSF can be referred to as RAN DF DMF, RAN DF DPF, and RAN DF DSF. The core network's DMF is referred to as DMF. Additionally, the core network may also have data plane application function network elements such as DPF and DSF, and may also possess the ability to interact with RAN-side data plane application functions and / or data plane protocol stacks. The network elements and / or processes mentioned later in this application, such as RAN DMF, RAN DPF, RAN DSF, RAN DF DMF, RAN DF DPF, RAN DF DSF, DMF, DPF, DSF, DP, CP, and UP, are the same as the aforementioned functional definitions and will not be repeated here.

[0172] In this application, the data plane application function can be deployed either inside the base station (BS) or independently outside the base station, and includes one or more functions such as data management function (DMF), data processing function (DPF), and data storage function (DSF). The radio access network (RAN) supports control plane transmission, user plane transmission, and data plane transmission. Base stations exchange control signaling for the data plane through the Xn-C interface or transmit data through the Xn-D interface; base stations and data plane application functions exchange control signaling for the data plane through the Xm-C interface or transmit data through the Xm-D interface; base stations and core network functions (CN NF) exchange control signaling for the data plane through the NG-C interface or transmit data through the NG-D interface; data plane application functions and core network functions exchange control signaling for the data plane through the NGD-C interface or transmit data through the NGD-D interface. Furthermore, base stations, data plane application functions, and core network functions can also exchange control signaling for the data plane and / or transmit data through service-oriented interfaces. In this way, data plane application functions, data plane protocol stack, BS, UE, and core network can be linked together through control plane, data plane and / or user plane transmission paths, thereby supporting the transmission of various signaling and data.

[0173] Furthermore, this application also provides a session establishment method. It should be understood that some steps in this method can be implemented based on the RAN architecture described above, but are not limited to the aforementioned architecture. Figure 17 shows a flowchart of a session establishment method according to an embodiment of this application. As shown in Figure 17, the method includes operation S101.

[0174] In step S101, the second node sends a session establishment request to the first node, and the first node receives the session establishment request. The session establishment request includes transmission type information and / or data task information. The transmission type information indicates whether the transmission type is user plane transmission or data plane transmission; the data task information indicates the data task corresponding to the session.

[0175] The first node and the second node are two nodes in a wireless network. The second node initiates the session establishment, and the first node receives the session establishment. In one example, the first node is one of the Radio Access Network (RAN) node and the User Equipment (UE), while the second node is the other of the RAN and the UE. For ease of explanation, the RAN (e.g., a base station) will be referred to as the first node, and the UE as the second node in the following text.

[0176] In PDU session management, either the RAN or the UE can request the network to establish a PDU session. Accordingly, in this method, the session establishment request can be initiated by the RAN to the UE, or by the UE to the RAN. The following explanation will primarily use the example of the UE initiating a session to the RAN, but this should not be construed as a limitation on the scope of protection of this application.

[0177] In some embodiments, the session establishment request message includes transport type information. The transport type information is used to indicate different data transmission methods. For example, a transport type identifier (ID) can be used as the transport type information, or a specific field can be used to explicitly indicate the transport type. In this embodiment, the transport type information is used to indicate whether the transport type is user plane transport or data plane transport.

[0178] In some embodiments, the session establishment request message includes data task information. The data task information indicates the data task corresponding to the session. The data task information may be a data task identifier (Data Task ID), used to directly indicate the corresponding data task. Alternatively, the data task information may also indicate the corresponding data task in other explicit or implicit ways, without limitation herein. The data task may include or be associated with one or more data acquisition tasks, data processing tasks, data storage tasks, data retrieval tasks, and / or data transmission tasks.

[0179] By including transport type information in the session establishment request, the first and second nodes can exchange this information during the session establishment process. This allows the session management function handling the session establishment request to determine the data transmission method based on the transport type information, or to facilitate the selection of appropriate data transmission methods and interfaces by the relevant nodes based on the transport type determined by the session management function.

[0180] Alternatively, by including data task information in the session establishment request, the first and second nodes can exchange this information during the session establishment process. This allows the nodes involved in session establishment and management (e.g., UDM, PCF, and / or UDR) to match user subscription data and / or session policy information related to the data service based on the data task information, rather than solely relying on the information of the requesting UE. This results in a more accurate matching of data transmission task requirements.

[0181] In some embodiments, the session establishment request further includes a destination node identifier, used to indicate the destination node for data transmission in the session. The destination node may include the first node, which is a radio access network node configured with data plane application functionality. In other words, the session establishment request can be an end-to-end session initiated by the UE to the BS, i.e., the destination node points to the BS. The BS can be a radio access network node configured with data plane application functionality as described above. Specifically, the data plane application functionality can be deployed within the radio access network node or deployed in a data plane application functionality network element shared by multiple radio access network nodes.

[0182] The data plane application functionality may include: a Data Management Function (DMF) node, a Data Processing Function (DPF) node, and a Data Storage Function (DSF) node. The DMF node manages the DPF node and / or the DSF node and performs at least one of the following functions: orchestrating data flow; data traffic statistics; data collection task configuration; or triggering data reporting. The DPF node performs the data processing function. The DSF node performs the data processing function.

[0183] It should be understood that in other embodiments, the destination node can be other nodes. For example, the destination node can be a BS, a data plane application function node, or other nodes. The BS can be the UE's serving cell BS or other BSs. The data plane application function may not be configured within the destination BS.

[0184] Figure 18 illustrates the session establishment request flow for introducing data plane application functionality. The session establishment request message sent by the UE to the BS may contain one or more of the following information: the target network requested by the UE (UE Requested DNN), the destination node identifier for data transmission (UE Requested Target Node ID), the transmission type, and / or data task information, etc.

[0185] The target network requested by the UE identifies the target network, which can point to the destination node for data transmission, such as the BS (Base Station). The destination node identifier for data transmission can indicate the BS identifier or the identifier of other destination nodes; this identifier can be a unique identifier within the mobile network, such as an IP address or MAC address. The transmission type information indicates the transmission type, which can indicate one or more of the following: data plane transmission, user plane transmission, etc. Optionally, this field can also indicate that the destination node of the session is within the mobile network, i.e., not within the DN (Network Domain Name).

[0186] If the transmission type information indicates data plane transmission, it means the UE needs to establish a direct transmission channel with the destination node (such as the BS). This field option allows the UE-BS to use the data plane protocol stack for configuration and transmission, and the Data Management Function (DMF) needs to perform session configuration for the UE and BS. If the transmission type information indicates user plane transmission, it means the UE needs to establish a transmission channel with the destination node (such as the BS) through the User Plane Function (UPF), and the UE forwards data with the BS through the UPF. This field option allows the UE-BS to use the user plane protocol stack for configuration and transmission, and the DMF needs to perform session configuration for the UE, BS, and UPF.

[0187] Data task information (e.g., Data Task ID) is used to indicate the data task corresponding to the session. For example, the data task information may serve one or more of the following purposes: indicating a data task identifier (ID), indicating a data task type, indicating an associated data task (e.g., one or more data acquisition, storage, retrieval, transmission, and / or processing tasks), indicating the object of an associated data service, serving as a basis for retrieving user-subscribed data, serving as a basis for session authentication or authorization, or serving as a basis for session dynamic policy decisions. If data task information is included in the session establishment request, the UDM, PCF, and / or UDR can match user-subscribed data and / or session policy information related to the data service based on the data task information, instead of performing the above matching solely based on the information of the requesting UE, thereby more accurately matching the data transmission task requirements.

[0188] In some embodiments, the session establishment request message may also include Single Network Slice Selection Assistance Information (S-NSSAI), Protocol Data Unit Session Identifier (PDU Session ID), Request Type, Session Management Protocol Data Unit Data Network Request Container (SM PDU DN Request Container), UE Integrity Protection Maximum Data Rate (UE Integrity Protection Maximum Data Rate), 5G session management capabilities, number of packet filters, etc.

[0189] In addition to the content of the session establishment request message sent by the BS to the session management node, it may also include one or more of the following information: Subscription Permanent Identifier (SUPI), user location information, Selected Data Network Name (Selected DNN), etc.

[0190] In the embodiment shown in Figure 18, the BS can interact with the RAN DF DMF via the Xm-C interface and / or service-oriented interface described above. Alternatively, the BS can interact with the DMF via the NG-C interface and / or service-oriented interface described above. The session management function in the above operations can be the RAN DMF, RAN DF DMF, or DMF. The RAN DMF is located within the BS. Based on this embodiment, the UE can send a session establishment request to the RAN DMF, RAN DF DMF, or DMF to establish a data transmission path between the UE and the BS (or, the data plane application function node, or other nodes).

[0191] This method is applicable to situations where the UE is in a non-connected state (e.g., RRC idle state or RRC inactive state) and also to situations where the UE is in a connected state.

[0192] 1) When the core network, BS, and / or UE need to transmit data, if the UE is in an RRC-IDLE or RRC-INACTIVE state, a connection needs to be established between the UE and BS to allow the UE to switch to an RRC connected state. If the data transmission method is data plane or user plane transmission, the UE can send a session establishment request to the session management function through the BS. New fields are added to the paging messages, connection establishment / recovery request messages, connection establishment / recovery messages, and connection establishment / recovery completion messages during the connection establishment / recovery process to indicate the data transmission method (through control plane, user plane, or data plane). Additionally, new fields can be added to carry information such as paging / establishment / recovery reasons (signaling configuration, data transmission), data reporting requests, and session establishment requests.

[0193] 2) When the core network, BS, and / or UE need to transmit data, if the UE is in an RRC-connected state, the UE can send a session establishment request to the session management function through the BS. The session establishment request can include a transmission type field to carry the aforementioned transmission type information. The session management function can determine whether to use user plane or data plane transmission methods based on the newly added transmission type field. Furthermore, the session establishment request can also include a BS identifier field and / or a data task identifier field, where the session management function can associate the session with the data task based on the newly added data task identifier field.

[0194] Before the session establishment process, if the second node (UE) is in an RRC disconnected state, the second node can send a connection establishment / restore request message to the first node (BS), and the first node sends a connection establishment / restore response message to the second node. The connection establishment / restore request message and / or the connection establishment / restore response message contain transmission mode information and / or data task information for the data transmission. If the second node proceeds with the subsequent session process based on the data transmission-related configuration included in the connection establishment / restore process, the transmission type information in the session establishment request sent by the second node can correspond to the transmission mode information for the data transmission (e.g., the transmission type information in the session establishment request is the same as the transmission mode indicated in the data transmission mode information, or belongs to one of the multiple transmission modes indicated in the data transmission mode information); and / or, the data task information in the session establishment request sent by the second node can correspond to the data task information for the data transmission (e.g., the data task information in the session establishment request is the same as the data task indicated in the data transmission task information, or belongs to one of the multiple data tasks indicated in the data transmission task information). In some embodiments, before the second node sends a connection establishment / restore request message to the first node, the first node may send a paging message to the second node. The paging message indicates a paging reason, which may include data transmission. The connection establishment or restore process before the session establishment process will be described in detail below with reference to Figure 19. The connection establishment or restore process before the session establishment process shown in Figure 19 includes one or more of the following operations:

[0195] 1) The data management function can send data transmission requests to the BS.

[0196] In some embodiments, before sending a session establishment request to the UE, the BS may also receive a data transmission request from a data management function node. The data transmission request includes transmission mode information and / or data task information. Furthermore, the data transmission request may also include a destination node identifier to indicate the destination node for the data transmission. The destination node may be a BS, a data plane application function node, or another node. In some embodiments, the destination node is a BS, and the BS is a radio access network node configured with data plane application functions.

[0197] Specifically, a data transmission request may include one or more of the following: the transmission method of the data transmission (i.e., indicating whether the collected data is reported and transmitted through the control plane, user plane, or data plane), the destination node identifier of the data transmission, and the data task identifier.

[0198] Specifically, if the BS configures the UE's subsequent session process based on the transmission mode information and / or data task information in the data transmission request, then the transmission type information in the session establishment request subsequently sent by the UE can correspond to the transmission mode information in the data transmission request (for example, the transmission type information in the session establishment request is the same as the transmission mode indicated in the transmission mode information of the data transmission request, or belongs to one of the multiple transmission modes indicated in the transmission mode information of the data transmission request); and / or, the data task information in the session establishment request subsequently sent by the UE can correspond to the data task information of the data transmission request (for example, the data task information in the session establishment request is the same as the data task indicated in the data task information of the data transmission request, or belongs to one of the multiple data tasks indicated in the data task information of the data transmission request).

[0199] 2) The BS can send paging messages to the UE.

[0200] The paging message may include one or more of the following: UE paging ID information, paging reason, etc. The UE paging ID information may include one or more of the following: 5G-TMSI and / or I-RNTI, etc. The 5G-TMSI can be used to trigger the connection establishment process, and the I-RNTI can be used to trigger the connection recovery process. The paging reason may include one or more of the following: signaling configuration, data transmission, etc. Data transmission may be data acquisition data transmission.

[0201] It should be understood that the above two steps are not mandatory, and the UE can directly initiate the connection establishment / restore request.

[0202] 3) The UE sends a connection establishment / restore request message to the BS.

[0203] A connection establishment / recovery request message may contain one or more of the following: establishment / recovery reason, data task identifier, etc. The establishment / recovery reason may include one or more of the following: data acquisition, user plane, data plane, control plane, etc.

[0204] Data acquisition transmission can indicate that the UE is preparing to report acquired data. User plane transmission can indicate forwarding transmission via UPF. Data plane transmission can indicate direct point-to-point data transmission, such as data transmission between the UE and BS. Control plane transmission can indicate transmission via RRC messages.

[0205] 4) The BS sends a connection establishment / restore message to the UE.

[0206] Connection establishment / recovery messages may contain one or more of the following: data task identifier, destination node identifier for data transmission, user plane transmission, data plane transmission, control plane transmission, etc.

[0207] 5) The UE sends a connection establishment / recovery completion message to the BS.

[0208] The connection establishment / recovery completion message may contain one or more of the following: data task identifier, data reporting request, session establishment request message, collected data, etc.

[0209] A data reporting request may include one or more of the following: duration of data collection, amount of data collected, etc. A session establishment request message may include one or more of the following: transmission type (i.e., indicating whether the collected data is transmitted via the user plane or the data plane), destination node identifier for data transmission, and data task identifier.

[0210] 6) If the UE sends a session establishment request message to the BS, the BS will send the UE's session establishment request to the session management function.

[0211] Using the above method, when the User Equipment (UE) is in RRC-IDLE or RRC-INACTIVE state, if the UE needs to transmit data to the BS, or if the UE receives a session establishment request trigger message from the BS, the UE can initiate a connection establishment or recovery process with the BS. Through this process, the UE can switch to the RRC-CONNECTED state and establish a new session or report collected data.

[0212] It should be understood that if the second node (UE) is already in RRC connected state before the session establishment process, it can skip the paging, connection establishment / recovery request and corresponding procedures described above, and directly initiate a session establishment request to the first node. This session establishment request can be initiated proactively by the second node, or it can be initiated by the second node in response to a data transmission request from the first node and / or the data management function. In this case, the content carried by the data transmission request can be similar to that described above, and will not be repeated here.

[0213] Furthermore, in some cases, data transmission initiated by a data plane application function node or a BS may not be implemented through a session. Accordingly, this application provides a data transmission method. The method includes: a radio access network node (BS) receiving a first data transmission request from a data plane application function node; and sending a second data transmission request to a user equipment (UE). The first and second data transmission requests include transmission mode information and / or data task information. The transmission mode information indicates whether the data transmission is a control plane transmission, user plane transmission, or data plane transmission. The data task information indicates the data task corresponding to the data transmission. In this method, the data plane application function may be deployed within the radio access network node or deployed in a shared data plane application function network element of multiple radio access network nodes. Additionally, the first and second data transmission requests may also include a destination node identifier to indicate the destination node for data transmission. The destination node includes the radio access network node or other independent data plane application function nodes, and the radio access network node is configured with the data plane application function node. In this method, the UE may not perform a subsequent session establishment process but instead transmit data to the BS or data plane application function node through other means. For example, the BS can indicate in the data transmission request sent to the UE that the transmission method is through the control plane. Accordingly, the UE can transmit data through the control plane to the BS (or other nodes indicated by the destination node identifier). For descriptions of data transmission requests, transmission method information, and / or data task information, please refer to the relevant descriptions above, which will not be repeated here.

[0214] Furthermore, the session establishment method provided in this application embodiment may also include user subscription data request and response operations. In some embodiments, the method shown in FIG17 may further include a first node sending a user subscription data request message to a Unified Data Management (UDM) node through a data plane application function. The user subscription data request message includes the transport type information and / or the data task information. In this way, the UDM node and its associated User Data Repository (UDR) node can match the corresponding available user subscription data based on the transport type information and / or data task information contained in the user subscription data request message, thereby more accurately matching the data task requirements. The user subscription data request and response process will be described below with reference to FIG20.

[0215] Figure 20 illustrates a request and response flow for user subscription data according to an embodiment of this application. The flow includes one or more of the following operations:

[0216] 1) The session management function sends user subscription data request messages (such as Nudr_DM_Query) to the UDM.

[0217] 2) If the UDM does not have corresponding available user subscription data, the UDM will request the user subscription data from the UDR (e.g., via the Nudm_SDM_Get message). If the UDM has corresponding available user subscription data, the corresponding step will be skipped.

[0218] Specifically, UDM matches available user-subscribed data based on parameters in the user's subscription data request (such as selected DNN, transmission type, data task ID, SUPI, S-NSSAI, etc.). For example, UDM can match subscription data based on the object ID of the data service (such as the data consumer ID) in the data task ID.

[0219] 3) The UDR sends the requested user subscription data to the UDM.

[0220] UDR matches available user-subscribed data based on parameters in the user's subscription data request (such as selected DNN, transmission type, data task ID, SUPI, S-NSSAI, etc.).

[0221] 4) UDM sends a user subscription data response to the session management function, which includes the requested user subscription data.

[0222] The aforementioned user subscription data request may include one or more of the following information: selected target network (DNN), transmission type, data task ID, SUPI, S-NSSAI, etc. The selected target network identifies the target network and can point to a BS, a data plane application function node, or other nodes. The transmission type information indicates the transmission type, which can indicate one or more of the following: data plane transmission, user plane transmission, etc. Optionally, this field may also indicate that the destination node of the session is within the mobile network, i.e., not in the DN. Data task information (e.g., data task identifier, Data Task ID) indicates the data task corresponding to the session. For example, the data task information may serve one or more of the following purposes: indicating the data task identifier ID, indicating the data task type, indicating the associated data task (e.g., associating one or more data collection, storage, retrieval, transmission, and / or processing tasks), indicating the object of the associated data service, serving as the basis for retrieving user subscription data, serving as the basis for session authentication or authorization, or serving as the basis for session dynamic policy decisions. UDM and / or UDR can match user subscription data related to the data service based on the data task information (e.g., data task ID).

[0223] In some embodiments, the aforementioned user subscription data request may also include one or more of the following information: QoS transmission parameters (such as 5QI), resource allocation priority (such as ARP), maximum aggregation rate of the session (such as Session-AMBR), etc.

[0224] In the process shown in Figure 20, the session management function can be RAN DMF, RAN DF DMF, or DMF. The RAN DMF resides within the BS. The session management function can also notify the UDM when subscribed data changes via subscription messages (such as Nudm_SDM_Subscribe), and the UDM can also notify the UDR when subscribed data changes via subscription messages (such as Nudr_DM_subscribe). The RAN DMF and / or RAN DF DMF can interact with the UDM via signaling through the NG-C interface and / or service-oriented interface described earlier in this application. Based on this embodiment, the RAN DMF, RAN DF DMF, or DMF can obtain the user subscription data required to establish a data transmission path between the UE and the BS (or, the data plane application function node, or other nodes) from the UDM or via the UDM from the UDR.

[0225] Furthermore, the session establishment method provided in this application embodiment may also include session authentication / authorization operations. Figure 21 shows a schematic flowchart of the session authentication / authorization process. As shown in the figure, the process includes one or more of the following operations:

[0226] 1) The session management function can identify the data network authentication and authorization server (DN-AAA) based on the local configuration or the data network-specific identity in the session management protocol data unit data network request container (SM PDU DN Request Container) carried by the UE in the session establishment request.

[0227] 2) If there is no N4 session to transmit data between the session management function and the data network (DN), the session management function will select UPF and establish an N4 session.

[0228] 3) The session management function sends a data network-specific identity to DN-AAA to perform the authentication process.

[0229] 4) DN-AAA sends authentication / authorization messages to the session management function.

[0230] 5) The session management function will send the data network request container information (DN Request Container information) received from DN-AAA to the UE via the BS. The session management function and the BS will communicate using HTTP / 2 and / or HTTP / 3 messages.

[0231] 6) The UE receives data network request container information from DN-AAA and responds to the session management function. The session management function and the BS communicate using HTTP / 2 and / or HTTP / 3 messages.

[0232] 7) The session management function sends data network request container information to DN-AAA through UPF.

[0233] 8) DN-AAA successfully confirms the authentication and authorization of the session. At this point, DN-AAA can provide one or more of the following:

[0234] a) Session Management Protocol Data Unit (SM PDU) DN Response Container: Indicates that the DMF has successfully completed authentication and authorization.

[0235] b) Data Network Authorization Data (DN Authorization Data): Used to control the policies and charging rules (PCC) and session parameters between the UE and the BS (or, data plane application function node or other nodes).

[0236] c) Request information for the IP or MAC information of the UE corresponding to the session.

[0237] 9) Continue establishing subsequent sessions until completion.

[0238] 10) If the IP or MAC information of the UE corresponding to the session is requested during the above process, the session management function sends the corresponding information to DN-AAA and carries the Global Public Land Mobile Network User Plane Service Identifier (GPSI).

[0239] In the process shown in Figure 21, the session management function can be RAN DMF, RAN DF DMF, or DMF. The RAN DMF is located within the BS. The RAN DMF and / or RAN DF DMF can interact with the UPF via signaling through the NG-C interface and / or service-oriented interface described earlier in this application. The BS can interact with the RAN DF DMF via the Xm-C interface and / or service-oriented interface described earlier in this application. The BS can interact with the DMF via the NG-C interface and / or service-oriented interface described earlier in this application. Based on this embodiment, the RAN DMF, RAN DF DMF, or DMF can initiate an authentication / authorization process for the data transmission path between the UE and the BS (or, the data plane application function node, or other nodes).

[0240] Furthermore, the session establishment method provided in this application embodiment may also include request and response operations for session dynamic policies. In some embodiments, the first node is a radio access network node configured with data plane application functions, an independent data plane application function node, or a DMF belonging to the core network, and the method shown in FIG17 may further include: the first node sending a session policy request message to a policy control function (PCF) node through the data plane application function. The session policy request message includes the transmission type information and / or the data task information. In this way, the PCF node can match the corresponding available session dynamic policies according to the transmission type information and / or data task information contained in the session policy request message, thereby more accurately matching the needs of data tasks. The request and response process for user subscription data will be described below with reference to FIG22.

[0241] Figure 22 illustrates a flowchart of the request and response process for a session dynamic policy according to an embodiment of this application. As shown in Figure 22, the request and response process for a session dynamic policy may include one or more of the following operations.

[0242] 1) The session management function sends a session policy request message (such as Npcf_SMPolicyControl_Create request) to the PCF. The request content includes the session policy and charging control (PCC) rules.

[0243] The Session Policy Request message includes one or more of the following: transmission type information, and / or data task indication, as well as SUPI, Protocol Data Unit Session ID (PDU Session ID), DNN, S-NSSAI, Session Aggregated Maximum Bit Rate (Session-AMBR), subscribed default QoS information, 5QI (5 Generation Quality Indicator), 5QI Priority Level, and Allocation and Reservation Priority (ARP). Transmission type information indicates the transmission type, which may include one or more of the following: data plane transmission, user plane transmission, etc. Optionally, this field may also indicate that the destination node of the session is within the mobile network, i.e., not in the DN. Data task information (e.g., Data Task ID) indicates the data task corresponding to the session. For example, the data task information may serve one or more of the following purposes: indicating the data task identifier ID, indicating the data task type, indicating the associated data task (e.g., associating one or more data collection, storage, retrieval, transmission, and / or processing tasks), indicating the object of the associated data service, serving as the basis for retrieving user-subscribed data, serving as the basis for session authentication or authorization, or serving as the basis for session dynamic policy decisions. UDM and / or UDR can match user subscription data related to the data service based on data task information (e.g., data task ID). Based on the session policy request message, PCF and / or UDR can match session policy information related to the data service based on data task indication (e.g., data task ID).

[0244] 2) If the PCF does not have corresponding available session policy data, the PCF queries and / or subscribes to the UDR for session policy data (e.g., via the Nudr_DM_Query message and / or the Nudr_DM_Subscribe message). The UDR returns the corresponding session policy data. If the PCF has corresponding available session policy data, the corresponding operation is skipped.

[0245] The session policy data request message may contain one or more of the following: SUPI, DNN, S-NSSAI, transmission type, data task indication, etc. Session policy data may include policy data, etc.

[0246] 3) If the PCF's policy decision depends on the CHF's policy counter status, then the PCF needs to initialize a policy counter status report to the CHF or retrieve an existing policy counter status report.

[0247] 4) PCF makes policy decisions based on user subscription data, existing policy data, policy counter status reports, and other information, and generates PCC rules.

[0248] 5) PCF sends a session policy response message (such as the Npcf_SMPolicyControl_Create response message) to the session management function, which includes the session's PCC rules.

[0249] In the process shown in Figure 22, the session management function can be RAN DMF, RAN DF DMF, or DMF. The RAN DMF is located within the BS. The RAN DMF and / or RAN DF DMF can interact with the PCF via signaling through the NG-C interface and / or service-oriented interface described earlier in this application. Based on this embodiment, the RAN DMF, RAN DF DMF, or DMF can obtain the session policy information required to establish a data transmission path between the UE and the BS (or, the data plane application function node, or other nodes) from the PCF or via the PCF from the UDR.

[0250] Furthermore, the session establishment method provided in this application embodiment may also include session configuration and response operations. In some embodiments, the method shown in FIG17 may further include: a first node determining a session transmission configuration and / or a charging configuration according to a dynamic policy or a local policy; and sending the session transmission configuration and / or the charging configuration to a second node. Wherein, if the transmission type information indicates that the transmission type is a data plane transmission, the session transmission configuration and / or the charging configuration can be determined through the data plane application function. Wherein, if the transmission type information indicates that the transmission type is a user plane transmission, the method may further include: the first node sending the session transmission configuration and / or the charging configuration to a User Plane Function (UPF) node; and the first node receiving a response message from the UPF node. The session configuration and response process will be described below with reference to FIG23.

[0251] Figure 23 illustrates a schematic flowchart of session configuration and response according to an embodiment of this application. As shown in Figure 23, the session configuration and response flow may include one or more of the following operations.

[0252] 1) The session management function sends session transport configuration and / or billing configuration (such as packet inspection rule PDR, forwarding action rule FAR, usage report rule URR, quality of service enforcement rule QER, buffer action rule BAR, etc.) to the BS based on dynamic policies (such as PCC rules) or local policies.

[0253] Specifically, the session transport configuration and / or accounting configuration message may contain one or more of the following:

[0254] a) PDR: Primarily used for matching data streams. It includes Packet Detection Information (PDI), which provides parameters for packet matching, including the source interface, local F-TEID, network instance, and UE IP address. Additionally, PDR includes PDR ID, FAR ID, URR ID, and / or QER ID.

[0255] b) FAR, URR, QER, BAR.

[0256] c) The RAN uses this as the basis for establishing air interface bearers, such as Quality of Service (QoS) profiles(s). This may include Data Plane Security Enforcement information, indicating whether data plane transmissions require integrity protection and encryption protection. If integrity protection is required, the maximum data rate for integrity protection carried by the user equipment in the session establishment request must also be included in this message.

[0257] d) UE transmission configuration information (such as IP address, rate limit, etc.). For example: assigned IPv4 address, session AMBR, etc.

[0258] If the transmission type is data plane session (e.g., the transmission type in the UE's session establishment request is data plane transmission), then the session management function can be performed as described above.

[0259] If the transport type is a user plane session (e.g., the transport type in the UE's session establishment request is user plane transport), the session management function needs to send session transport configuration and / or charging configuration (e.g., PDR, FAR, URR, QER, BAR, etc.) to the UPF according to dynamic policies (e.g., PCC rules) or local policies. After receiving the configuration message, the UPF sends a response message to the session management function. Furthermore, the session transport configuration and / or charging configuration message may also carry the UPF's uplink session reception parameters on the N3 interface.

[0260] 2) The BS sends session bearer configuration to the UE to establish the air interface bearer between the UE and the BS. Alternatively, the BS can forward transport configuration information from the session management node to the UE. The air interface bearer configuration is determined by the QoS rules in the session transport configuration message received by the BS from the session management function.

[0261] 3) After completing the session bearer establishment, the BS sends a session configuration response to the session management function.

[0262] The session configuration response message may contain one or more of the following:

[0263] a) List of accepted / rejected QoS flow identifiers. The list of accepted / rejected QoS flow identifiers can indicate which QoS flows the BS rejects (add or update QoS flows) configured by the session management function. The session management function can then update or release the corresponding QoS flows, QoS rules, and / or parameters.

[0264] b) Data Plane Enforcement Policy Notification. When the BS cannot meet the data plane security execution requirements and session management is mandatory, the base station uses this field to reject the session management function. When the base station cannot meet the data plane security execution requirements and session management is preferred, the base station uses this field to inform the session management function. This field is used for data plane transmission.

[0265] If the transport type is user plane session (e.g., the transport type in the UE's session establishment request is user plane transport), the session configuration response message will also carry the downlink session reception parameters of the BS on the N3 interface. Then, it is forwarded to the UPF via the session management function.

[0266] In the process shown in Figure 23, the session management function can be RAN DMF, RAN DF DMF, or DMF. The RAN DMF is located within the BS. The BS can interact with the RAN DF DMF via the Xm-C interface and / or service-oriented interface described earlier in this application. The BS can also interact with the DMF via the NG-C interface and / or service-oriented interface described earlier in this application. Based on this embodiment, the RAN DMF, RAN DF DMF, or DMF can establish a data transmission path between the UE and the BS, enabling data transmission between the UE and the BS (or, the data plane application function node or other nodes), and allowing the BS to obtain statistics and reporting rules regarding network resource usage.

[0267] The methods for determining user subscription data, session authentication / authorization, determining session dynamic policies, and configuring sessions described above can be implemented using other methods. In some embodiments, before receiving the session establishment request from the second node in S101, the method may further include: when the second node registers with the network, the first node obtains the second node's subscription data, session authentication information, session authorization information, and / or session policies under one or more session types. The session types include one or more of the following: task type, slice information, and target address.

[0268] Specifically, when a UE registers with the network, it can report its data transmission capabilities and / or data acquisition capabilities to the network side. The network side can pre-acquire and store the UE's subscription data, session authentication information, session authorization information, and / or session policies for one or more session types based on the UE's capabilities (such as data transmission capabilities and data acquisition capabilities) on the RAN side (e.g., BS and / or RAN DF). When the UE initiates a session establishment request, the RAN can directly complete the session establishment and bearer configuration based on the existing subscription data, session authentication information, session authorization information, and / or session policies corresponding to the requested session type.

[0269] The session type can include one or more of the following: task type, slice information, and destination address. For example, the task type can include one or more of the following: model training, model inference, model monitoring, etc. For example, slice information can include one or more of the following: high rate, large capacity, low latency, and / or high reliability, etc. For example, the destination address represents the address of the destination node for UE data transmission and can include one or more of the following: IP address, port information, node ID, etc.

[0270] The aforementioned embodiments can be implemented based on the two RAN architecture schemes shown in Figures 3 and 12. The data plane application function (RAN DF) on the BS or RAN side, independent of the BS, can have the session management function of the core network DMF. Specifically, the session management function used for UE-BS session establishment can be located in three scenarios:

[0271] 1) Scenario 1: Regardless of whether the RAN data plane application function is inside the BS or inside the RAN side node independent of the BS, the session management function in the session establishment process between UE and BS is the responsibility of the DMF network element of the core network.

[0272] 2) Scenario 2: When the RAN data plane application function is inside the BS, the session management function in the session establishment process between UE and BS is handled by the RAN DMF network element.

[0273] 3) Scenario 3: When the RAN data plane application function is outside the BS and inside the RAN-side node independent of the BS, the session management function in the session establishment process between UE and BS is handled by the RAN DF DMF network element.

[0274] In other words, the UE and BS can establish a session based on the functions of the core network and RAN, or they can establish a session based solely on the functions of the RAN side.

[0275] This application also provides a method for statistically analyzing session data usage. This method can be performed by a radio access network node. As shown in Figure 24, the method includes operations S201 to S203.

[0276] In S201, obtain the Data Resource Usage Reporting Rule (URR).

[0277] Data resource usage reporting rules can also be called data usage reporting rules. Let's take a BS (Broadcast Base Station) node as an example. The BS has traffic statistics and reporting functions, and it can receive data usage reporting rules from various data management functions. For example, the BS can perform traffic statistics and reporting based on network resource usage reporting rules (URRs) obtained from data management functions (such as DMF, RAN DMF, and / or RAN DF DMF).

[0278] In some embodiments, the URR includes a measurement method indication for indicating the measurement method of the data usage (network resource usage). For example, the measurement method may be based on data capacity, duration, and / or events.

[0279] In some embodiments, the URR includes a reporting trigger mode indication to indicate the trigger mode for the data usage report. This could be periodic triggering, threshold-based triggering, and / or BS reporting triggering based on DMF, RAN DMF, and / or RAN DF DMF indications.

[0280] In some embodiments, the URR includes a statistical method indication for indicating the statistical method of the data usage. For example, data usage can be statistically analyzed according to one or more of the following methods: radio bearer (RB) based statistics; quality of service (QoS) stream based statistics; session based statistics; UE based statistics; slice or transmission demand based statistics; task type based statistics (such as location, network optimization, etc.); and / or session endpoint based statistics (such as OAM, etc.).

[0281] In addition, the URR may also include measurement period, capacity threshold, event threshold, time threshold, capacity quota, event quota, time quota, monitoring time, etc. The difference between thresholds and quotas is that when the statistics exceed the quota, the BS not only needs to report but also needs to stop transmission. When the statistics exceed the threshold, the BS only needs to report and can continue to provide transmission services.

[0282] In S202, the data usage is statistically analyzed based on the URR.

[0283] In S203, a data usage report (e.g., a network resource usage report) is sent based on statistics of data usage.

[0284] The BS can perform corresponding capacity, time, and / or event statistics according to the measurement methods in the URR. When the reporting / triggering conditions are met, the UE reports a data usage report. For example, when the corresponding statistics exceed the threshold and / or quota, the BS reports a network resource usage report.

[0285] In some embodiments, the data usage report includes data volume information and / or data task information. By carrying data task information, network resource usage can be associated with the objects of data services, thereby enabling processes such as billing for data service objects.

[0286] In some embodiments, the data usage report may also include one or more of the following: user identifier ID, protocol data unit (PDU) session ID, timestamp, traffic type, or quality of service (QoS) metric.

[0287] In addition, if the BS does not transmit any data during the monitoring period, it can also report a network resource usage report. This report can include information indicating that data transmission was idle.

[0288] According to this method, wireless access network nodes (such as BSs) can perform traffic statistics and reporting. Therefore, regardless of the destination of the data flow, the network resource usage of air interface transmission can be effectively counted. If the traffic statistics and reporting function is deployed in other locations or functional network elements, due to the arbitrary topology of the data transmission path, a large number of other functional network elements would also need to have traffic statistics and reporting functions, which does not conform to the goal of system simplification. Based on this method, the BS can perform traffic statistics and reporting according to specified network resource usage reporting rules, thereby providing a basis for data service billing.

[0289] The BS can receive data usage reporting rules from different data management functions and can also submit data usage reports to different data management functions.

[0290] In one implementation, the method shown in Figure 24 can be implemented in conjunction with the RAN architecture shown in Figure 3 or Figure 12. That is, the radio access network node can be configured with data plane application functions, or have a communicable connection with a node configured with said data plane application functions, and the aforementioned URR can be obtained via said data plane application functions. Details are as follows.

[0291] Figure 25 illustrates a traffic statistics and reporting process applied to a radio access network (KARN) node according to an embodiment of this application. The KARN node reports its data usage to the Charging Function (CHF) node via the data plane application function. As shown in Figure 25, the KARN node reports its data usage to the Charging Function (CHF) node via the DMF or RAN DF DMF. The specific steps are as follows:

[0292] 1) The BS will detect the data transmission process (such as by RB, QoS stream, PDU session, user level, transmission requirements, or task type) according to the URR rules and make corresponding records (such as data volume, duration, and events).

[0293] 2) When a trigger condition is met (such as a threshold, time, command, or event), the BS sends a usage report to the DMF or RAN DF DMF via the SBI or other interfaces. This report may include one or more of the following: user ID, data task ID, PDU session ID, timestamp, data volume, traffic type, QoS metrics, etc. The trigger condition can be a command from the DMF or RAN DF DMF. By carrying the data task ID, network resource usage can be associated with the data service object, thereby enabling processes such as billing for the data service object.

[0294] 3) DMF or RAN DF DMF receives the BS's usage report.

[0295] 4) DMF or RAN DF: DMF transmits traffic statistics to CHF in real time through the SBI interface or other interfaces to enable online billing.

[0296] If the DMF or RAN DF DMF is transmitted via SBI, then the DMF or RAN DF DMF can transmit traffic statistics in real time through the Nchf_ConvergedCharging service to enable online billing. The traffic statistics may include data task IDs, etc.

[0297] Figure 26 illustrates a flowchart of a radio access network node obtaining data usage report (URR) rules according to an embodiment of this application. In this embodiment, the method for obtaining URR includes: obtaining dynamic rules from the Policy Control Function (PCF) node via the data plane application function; wherein the data plane application function converts the dynamic rules into detection, reporting, and transmission rules executable by the radio access node. As shown in Figure 26, the PCF specifies the dynamic rules based on real-time billing information, network status, and static user subscription data, and distributes them to the BS via the DMF or RAN DF DMF. The specific steps are as follows:

[0298] 1) PCF generates billing and transmission policies (such as policies based on service type, DNN, and S-NSSAI) based on operator configuration, network status, user subscription data, and user remaining quota.

[0299] Among them, the PCC rules include transmission policy control and billing control.

[0300] 2) PCF is issued to DMF or RAN DF DMF via PCC rules.

[0301] PCF transmits PCC rules to DMF or RANDF DMF via SBI or other interfaces.

[0302] 3) DMF or RAN DF DMF receives PCC rules from PCF.

[0303] 4) DMF or RAN DF DMF converts PCC rules into BS-executable detection, reporting, and transmission rules (such as PDR / FAR / URR / QER, etc.).

[0304] The PDR (Program Detection Parameter) includes the data flow detection method, such as UE IP, QoS flow ID, session ID, TEID, etc. FAR (Failure Detection Parameter) includes the data flow processing method, such as transmission, buffering, and dropping. URR (Usage Response Rate) includes information such as detection type, quota, and triggering conditions (e.g., quota exhaustion). QER (Quality Response Rate) includes QoS rule information such as maximum rate and guaranteed rate.

[0305] 5) DMF or RAN DF: DMF configures the billing and transport rules to BS through SBI or other interfaces.

[0306] 6) After receiving the billing rules and transmission rules issued by the DMF or RAN DF DMF, the BS performs traffic detection and data transmission according to the rules.

[0307] In the aforementioned method, the BS can interact with the RAN DF DMF via the Xm-C interface and / or serviced interface described above in this application. The BS can also interact with the DMF via the NG-C interface and / or serviced interface described above in this application.

[0308] Based on this embodiment, the BS can report data usage to the CHF via DMF or RAN DF DMF, thereby providing a basis for data service billing.

[0309] In another implementation, as shown in Figure 24, the radio access network node can directly report data to the CHF and / or directly obtain PCC rules from the PCF and convert them into executable data resource usage report rules. Details are as follows.

[0310] Figure 27 illustrates a traffic statistics and reporting process applied to a radio access network node according to another embodiment of this application. In this embodiment, the radio access network node directly reports the data usage report to the billing function (CHF) node. As shown in Figure 27, the BS reports the data usage report / traffic statistics information to the CHF. The specific steps are as follows:

[0311] 1) The BS will detect the data transmission process (such as by RB, QoS stream, PDU session, user level, transmission requirements, or task type) according to the URR rules and make corresponding records (such as data volume, duration, and events).

[0312] 2) When the triggering conditions (such as threshold, time, command, event) are met, the BS sends a usage report / traffic statistics information to the CHF, which may include one or more of the following: user ID, data task ID, PDU session ID, timestamp, data volume, traffic type, QoS indicators, etc.

[0313] 3) The BS transmits data usage reports / traffic statistics to the CHF in real time via the SBI interface or other interfaces to achieve online billing. Specifically, if the BS transmits via SBI, it can also use the Nchf_ConvergedCharging service to transmit data usage reports / traffic statistics in real time for online billing.

[0314] Figure 28 illustrates a flowchart of a wireless access network node acquiring data usage report (URR) rules according to another embodiment of this application. In this embodiment, the steps for a wireless access network node to acquire URR include: acquiring dynamic rules from a policy control function (PCF) node; and converting the dynamic rules into detection, reporting, and transmission rules executable by the wireless access network node. As shown in Figure 28, the PCF specifies the dynamic rules and issues them to the BS based on real-time billing information, network status, and static user subscription data. The specific steps are as follows:

[0315] 1) PCF generates billing and transmission policies (such as policies based on service type, DNN, and S-NSSAI) based on operator configuration, network status, user subscription data, and user remaining quota.

[0316] Among them, the PCC rules include transmission policy control and billing control.

[0317] 2) PCF is sent to BS via PCC rules.

[0318] PCF can transmit PCC rules to BS through SBI or other interfaces.

[0319] 3) The BS receives PCC rules from the PCF.

[0320] 4) BS converts PCC rules into executable detection, reporting, and transmission rules (such as PDR / FAR / URR / QER, etc.).

[0321] 5) The BS performs traffic detection and data transmission according to the billing and transmission rules.

[0322] In the aforementioned method, the BS can interact with the CHF and / or PCF through the NG-C interface and / or service-oriented interface described above in this application.

[0323] Based on this embodiment, the BS can report data usage to the CHF, thereby providing a basis for data service billing.

[0324] Based on the methods described above, this application further provides a full lifecycle data management solution, namely, the complete process from data request to data acquisition by the data requester. As shown in Figure 29, the complete process from data request to data acquisition by the data requester may include one or more of the following operations.

[0325] S301: A Network Function (NF) node needs data for a local task. The NF sends a data request message to the RAN DMF or RAN DF DMF.

[0326] The data request message may contain one or more of the following: data type, data format, data volume, data collection scope, task type, etc.

[0327] Data types can include one or more of the following: channel data, sensing data, etc. Data collection scope can include one or more of the following: geographical location range, cell ID list, etc. Task types can include one or more of the following: model training, model inference, model monitoring, network optimization, etc.

[0328] S302: RAN DMF or RAN DF DMF receives data request messages from NF and performs task decomposition and function orchestration based on the data request messages.

[0329] Among them, RAN DMF or RAN DF DMF can associate decomposed tasks with corresponding task IDs assigned based on the task and / or data requester.

[0330] For example, RAN DMF or RAN DF DMF can decompose a data request from an NF into one or more tasks, which can be one or more of the following: data acquisition tasks, data retrieval tasks, data storage tasks, data transmission tasks, and / or data processing tasks. Then, RAN DMF or RAN DF DMF can assign corresponding task IDs to these one or more tasks based on the task type of the NF's data request and / or the data requester, thereby allowing the decomposed tasks to be correlated with each other.

[0331] S303: The RAN DMF or RAN DF DMF sends a data processing task message to the RAN DPF or RAN DF DPF based on the results of task decomposition and functional orchestration.

[0332] In this context, data processing task messages and data acquisition configurations and reporting rules for operations S303 and S304 can be associated using the same task ID. Data processing task messages may contain one or more of the following: task ID, data type, input and / or output data format, data volume, task type, etc.

[0333] S304: RAN DMF or RAN DF DMF generates the corresponding data acquisition configuration and reporting rules based on the results of task decomposition and function orchestration.

[0334] S305: RAN DMF or RAN DF DMF sends the data acquisition configuration and reporting rules to UE via BS.

[0335] The data acquisition configuration and reporting rules may include one or more of the following: task ID, data acquisition object, acquisition time, data format, data volume, data acquisition range, and data reporting destination address. The task ID indicates which task the data acquisition process serves.

[0336] In other words, before executing the session establishment process, the data application management function can obtain a data request message from the data requester and determine one or more candidate tasks based on the data request message. When sending collection configuration and reporting rules to the UE, these collection configurations and reporting rules can be associated with these candidate tasks, so that the UE can explicitly know the collection and reporting configuration for each candidate task. During the subsequent session establishment process, the UE can indicate one or more of these candidate tasks through data task information, thereby informing the BS or data application management function which candidate task corresponds to the session transmission.

[0337] S306: The UE performs data collection. When the data meets the reporting conditions, the UE triggers the reporting process (such as triggering the session establishment process).

[0338] S307: Proceed with the session establishment process.

[0339] S308: The UE transmits the collected data to the RAN DPF or RAN DF DPF through the established session.

[0340] The data collected by the UE can include the task ID.

[0341] S309: RAN DPF or RAN DF DPF matches the data processing task based on the task ID corresponding to the data uploaded by the UE, and performs the corresponding data processing.

[0342] S310: RAN DPF or RAN DF DPF sends the processed data to NF.

[0343] The aforementioned task ID may have one or more of the following functions: indicating data task ID, indicating data task type, associating with data tasks (e.g., associating with one or more data collection, storage, retrieval, transmission and / or processing tasks), associating with data service objects, serving as the basis for retrieving user-subscribed data, serving as the basis for session authentication / authorization, serving as the basis for session dynamic policy decisions, etc.

[0344] In this embodiment, the RAN DMF and RAN DPF are configured within the BS. The RAN DF DMF and RAN DF DPF can be configured in independent RAN data plane application function nodes shared by multiple BSs. In the above steps, the BS can interact with the RAN DF DMF and / or RAN DF DPF through the Xm-C interface and / or service-oriented interface described earlier in this application. Based on this embodiment, the data requester can initiate a data request to the data service function, which will then complete the task orchestration, data acquisition, and data processing processes, and finally deliver the requested data to the data requester.

[0345] Figure 30 illustrates a flowchart of a full lifecycle data management scheme according to another embodiment of this application. Specifically, the process of establishing a session between the UE and the BS may include one or more of the following operations. Option a includes the operation of establishing a session when the UE is in an RRC disconnected state, while option b includes the operation of establishing a session when the UE is in an RRC connected state.

[0346] 1) Operations S401a-1 (or S401a-2), S402a, S403a, S404a, S405a, and S406a: When the core network, BS, and / or UE need to transmit data, if the UE is in RRC-IDLE or RRC-INACTIVE state, a connection needs to be established between the UE and BS to switch the UE to RRC-CONNECTED state. If the data transmission method is data plane or user plane transmission, the UE can send a session establishment request to the session management function through the BS.

[0347] In some embodiments of this application, fields such as paging / establishment / restore reason (signaling configuration, data transmission), transmission method, data reporting request, and session establishment request can be added to the paging message, connection establishment / restore request message, connection establishment / restore message, and connection establishment / restore completion message during the connection establishment / restore process.

[0348] 2) Operation S401b-1 (or S401b-2), S402b, S403b and S404b: When the core network, BS and / or UE need to transmit data, if the UE is in the RRC-CONNECTED state, the UE can send a session establishment request to the session management function through the BS.

[0349] In some embodiments of this application, a destination node (e.g., BS, data plane application function node, or other node) identifier field, a transmission type field, and a data task identifier field can be added to the session establishment request. The session management function can determine whether to use user plane transmission or data plane transmission mode for data transmission based on the newly added transmission type field. The session management function can associate the session with the data task based on the newly added data task identifier field.

[0350] 3) Operation S407: If the session management function has user subscription data, it can use the local user subscription data. If the session management function does not have user subscription data, it can perform operation S407 to request user subscription data. For example, it can retrieve user subscription data from the UDM.

[0351] In some embodiments of this application, a transmission type field and a data task identifier field may be added to the user subscription data request. UDM and / or UDR can match available user subscription data based on the transmission type field in the user subscription data request. UDM and / or UDR can match user subscription data related to the data service based on the data task identifier field in the user subscription data request.

[0352] 4) Operation S408: The session management function performs the session authentication / authorization process for this session.

[0353] In some embodiments of this application, the session authentication / authorization process can determine the session policy and charging rules (PCC) and session parameters between the UE and the BS (or, the data plane application function node or other nodes).

[0354] 5) Operation S409: If the session uses dynamic PCC rules, the session management function needs to select PCF; otherwise, the session management function can directly apply the local policy and jump directly to operation S412.

[0355] If the session management function directly applies local policies, i.e., it is not associated with the PCF, then it is not associated with the CHF and the charging function is not enabled. Applicable scenarios include data transmission tasks such as MDT that do not directly benefit the UE.

[0356] 6) Operation S410: Session management function requests and responses for dynamic session policies.

[0357] In some embodiments of this application, a transport type field and a data task identifier field may be added to the session policy request message and / or session policy data query and / or subscription message. The PCF and / or UDR can match the corresponding available user subscription data based on the transport type field in the session policy request message and / or session policy data query and / or subscription message. The PCF and / or UDR can match session policy information related to the data service based on the data task identifier field in the session policy request message and / or session policy data query and / or subscription message.

[0358] 7) Operations S411, S412, and S413: The session management function sends session transport configuration and / or charging configuration to the BS and UE. The BS sends session bearer configuration to the UE.

[0359] In some embodiments of this application, the session management function sends session transport configuration and / or accounting configuration to the BS based on dynamic policies and / or local policies and / or the transport type of the session. The BS can send a corresponding session configuration response message to the session management function based on the transport type of the session.

[0360] 8) Operation S414: Session establishment is complete, and data transmission can be performed between the UE and the BS (or, the data plane application function node or other nodes).

[0361] If the transmission type is user plane session (e.g., the transmission type in the UE's session establishment request is user plane transmission), the UE transmits data with the BS through the UPF.

[0362] 9) Operation S415: During data transmission, the BS performs statistics and reports on data usage according to the configuration.

[0363] In some embodiments of this application, the BS can perform traffic statistics and reporting processes according to Data Usage Reporting Rules (URRs). Specifically, the BS can report data usage reports to and / or receive data usage reporting rules from different data management functions.

[0364] The session management function in the above operations can be RAN DMF, RAN DF DMF, or DMF. The RAN DMF resides within the BS. Communication between the session management function and the BS can be achieved using HTTP / 2 and / or HTTP / 3 messages.

[0365] The above solution combines multiple approaches and their implementation methods to present a comprehensive data lifecycle management solution. It should be understood that not all steps in this solution are mandatory; the necessary steps and operations can be selected based on actual needs, resulting in different final solutions.

[0366] The embodiments of this application can be used for various types of data transmission in mobile cellular networks. For example, they can be applied to the management and transmission of data such as AI or sensing data, which are neither traditional user plane service data nor traditional control plane signaling data.

[0367] In summary, this application designs two data plane radio access network architecture schemes and corresponding interfaces to meet the data transmission requirements between user equipment and base stations. These schemes support the RAN's data management, processing, storage, and transmission functions. Based on these architectures, this application further designs the session establishment process between the UE and the BS (or, data plane application function node, or other nodes), as well as the data usage statistics, reporting, and configuration schemes during data transmission. These designs not only enable the BS (or, data plane application function node, or other nodes) to establish end-to-end sessions with the UE and perform efficient data transmission, but also allow for accurate statistics and reporting of data usage, thereby providing a basis for data service billing.

[0368] Furthermore, this application achieves unified management of the entire process—from data session establishment and data transmission to traffic billing—by adding a data task identifier, significantly improving the efficiency and accuracy of data processing. Simultaneously, by adding a transmission type identifier, this application can flexibly indicate different data transmission methods, meeting diverse data transmission needs. In summary, this application provides an innovative wireless communication solution that achieves efficient data transmission, accurate traffic billing support, and flexible transmission methods.

[0369] Figure 31 is a schematic block diagram of a communication device 500 provided in an embodiment of this application. As shown in Figure 31, the communication device 500 includes a processor 502 and a memory 504, which are communicatively connected. The communication device 500 can be, for example, but not limited to, a wireless access network node (e.g., a base station), a user equipment, etc. In some embodiments, the communication device 500 may also include a transceiver for transmitting / receiving data, or may only include a transmitting circuit for transmitting data, or only include a receiving circuit for receiving data. The memory 504 of the communication device 500 is used to store program instructions, which can be executed by the processor 502 to implement the wireless communication method (session establishment method and / or session data usage statistics method) described in any of the preceding embodiments.

[0370] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by software instructions.

[0371] It is understood that the memory in the embodiments of this application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory. Embodiments of this application also provide a computer-readable storage medium for storing a computer program.

[0372] Optionally, the computer-readable storage medium can be applied to the communication device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the communication device in the various methods of the embodiments of this application. For simplicity, further details are omitted here.

[0373] This application also provides a computer program product, including computer program instructions.

[0374] Optionally, the computer program product can be applied to the communication device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the communication device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0375] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0376] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A wireless access network node, wherein: The wireless access network node is configured with data plane application functionality; The data plane application functions include: DMF node for data management, DPF node for data processing, and DSF node for data storage. The DMF node is used to manage the DPF node and / or the DSF node, and is used for at least one of the following functions: orchestrating data flow; data traffic statistics; data collection task configuration; or triggering data reporting; The DPF node is used to perform data processing functions; The DSF node is used to perform data processing functions.

2. The wireless access network node as described in claim 1, wherein: The data plane application function is deployed inside the radio access network node, or deployed in a data plane application function network element shared by multiple radio access network nodes.

3. The wireless access network node as described in claim 1, wherein: The wireless access network node includes a control plane interface and / or a data plane interface for connecting to other wireless access network nodes or other independent data plane application function nodes. The control plane interface is used to provide one or more of the following functions: data transmission session management, data acquisition configuration, data retrieval, data storage, data processing, data node management, and data orchestration; The data plane interface is used for data transmission.

4. The wireless access network node as described in claim 1, wherein: The wireless access network node includes a control plane interface and / or a data plane interface for connecting to the core network. The control plane interface is used to provide one or more of the following functions: data transmission session management, data acquisition configuration, data retrieval, data storage, data processing, data node management, and data orchestration; The data plane interface is used for data transmission.

5. A session establishment method, executed by the first node, comprising: Receive a session establishment request from the second node, wherein the session establishment request includes: Transmission type information, which indicates whether the transmission type is user plane transmission or data plane transmission; and / or Data task information, which is used to indicate the data task corresponding to the session.

6. The method of claim 5, wherein: The session establishment request also includes a destination node identifier, which indicates the destination node for the session's data transmission; The destination node includes the first node, which is a wireless access network node configured with data plane application functions.

7. The method of claim 6, wherein: The data plane application functions include: DMF node for data management, DPF node for data processing, and DSF node for data storage. The DMF node is used to manage the DPF network element and / or the DPF node, and is used for at least one of the following functions: orchestrating data flow; data traffic statistics; data collection task configuration; or triggering data reporting; The DPF node is used to perform data processing functions; The DSF node is used to perform data processing functions.

8. The method of claim 6, wherein: The data plane application function is deployed inside the radio access network node, or deployed in a data plane application function network element shared by multiple radio access network nodes.

9. The method of claim 5, wherein, The data task information serves one or more of the following purposes: indicating the data task identifier ID, indicating the data task type, indicating the associated data task, indicating the object of the associated data service, serving as the basis for retrieving user-subscribed data, serving as the basis for session authentication or authorization, or serving as the basis for session dynamic policy decisions.

10. The method of claim 5, further comprising, before receiving the session establishment request from the second node: The data management function node receives a data transmission request, which includes the transmission method information and / or data task information of the data transmission.

11. The method of claim 10, wherein, The data transmission request also includes a destination node identifier, used to indicate the destination node for data transmission. The destination node includes the first node, which is a wireless access network node configured with data plane application functions.

12. The method of claim 5, further comprising: Send a user subscription data request message to the Unified Data Management (UDM) node; The user-subscribed data request message includes the transmission type information and / or the data task information.

13. The method of claim 12, wherein: The user subscription data request message may also include one or more of the following: Quality of Service (QoS) transmission parameters, resource allocation priority, or maximum session aggregation rate.

14. The method of claim 5, wherein, The first node is a radio access network node configured with data plane application capabilities, and the method further includes: The data plane application function sends a session policy request message to the policy control function PCF node. The session policy request message includes the transmission type information and / or the data task information.

15. The method of claim 14, further comprising: Determine session transport configuration and / or billing configuration based on dynamic or local policies; as well as Send the session transport configuration and / or the billing configuration to the second node.

16. The method of claim 15, wherein, If the transmission type information indicates that the transmission type is data plane transmission, the session transmission configuration and / or the billing configuration are determined by the data plane application function.

17. The method of claim 15, wherein, If the transmission type information indicates that the transmission type is a user plane transmission, it further includes: Send the session transport configuration and / or the charging configuration to the User Plane Function (UPF) node; and Receive response messages from the UPF node.

18. The method of claim 5, wherein, Before receiving the session establishment request from the second node, the method further includes: When the second node registers with the network, it obtains the second node's contract data, session authentication information, session authorization information and / or session policy under one or more session types; The session type includes one or more of the following: task type, slice information, and target address.

19. The method of claim 5, wherein, Before receiving the session establishment request from the second node, the following is also included: Obtain the data request message from the data requester; One or more candidate tasks are determined based on the data request message, wherein the candidate tasks include the data task corresponding to the session; Send the data collection and reporting configuration corresponding to the one or more candidate tasks to the second node.

20. The method of claim 5, wherein, Before receiving the session establishment request from the second node, the following is also included: Receive connection establishment / restore request messages from the second node; and Send a connection establishment / restore response message to the second node; The connection establishment / restore request message and / or the connection establishment / restore response message contain the transmission mode information and / or data task information of the data transmission.

21. The method of claim 20, wherein, Before receiving the connection establishment / restore request message from the second node, the method further includes: A paging message is sent to the second node, the paging message indicating the paging reason, which includes data transmission.

22. A session establishment method, executed by a second node, comprising: Send a session establishment request to the first node, wherein the session establishment request includes: transmission type information and / or data task information; The transmission type information is used to indicate whether the transmission type is user plane transmission or data plane transmission; The data task information is used to indicate the data task corresponding to the session; The first node is a wireless access network node, and the second node is a user equipment.

23. The method of claim 22, wherein: The session establishment request also includes a destination node identifier, which indicates the destination node for the session's data transmission; The destination node includes the first node, which is a wireless access network node configured with data plane application functions.

24. The method of claim 22, wherein, The data task information serves one or more of the following purposes: indicating the data task identifier ID, indicating the data task type, indicating the associated data task, indicating the object of the associated data service, serving as the basis for retrieving user-subscribed data, serving as the basis for session authentication or authorization, or serving as the basis for session dynamic policy decisions.

25. The method of claim 22, further comprising: Receive session transport configuration and / or accounting configuration from the first node; The first node is a radio access network node configured with data plane application functions, and the session transmission configuration and / or the billing configuration are determined by the first node through the data plane application functions.

26. The method of claim 22, wherein, Before sending the session establishment request to the first node, the method also includes: Send data transmission capability and / or data acquisition capability to the first node; The data transmission capability and / or data acquisition capability are used by the first node to determine the second node's contract data, session authentication information, session authorization information, and / or session policy under one or more session types.

27. The method of claim 22, wherein, Before sending the session establishment request to the first node, the method further includes: sending a connection establishment / restore request message to the first node; and Receive connection establishment / restore response messages from the first node; The connection establishment / restore request message and / or the connection establishment / restore response message contain the transmission mode information and / or data task information of the data transmission.

28. The method of claim 27, wherein, Before sending the connection establishment / restore request message to the first node, the method further includes: A paging message is received from the first node, the paging message indicating the paging reason, the paging reason including data transmission.

29. A method for calculating session data usage, performed by a radio access network node, comprising: URR (Usage Rules for Data Resources) The data usage is statistically analyzed based on the URR. as well as A data usage report is sent based on the statistics of the data usage.

30. The method of claim 29, wherein: The URR includes a measurement method indication for indicating the measurement method used for the amount of data used.

31. The method of claim 29, wherein: The URR includes a reporting trigger mode indicator, which indicates the trigger mode for the data to use the report.

32. The method of claim 29, wherein: The URR includes the statistical method indication, which is used to indicate the statistical method for the amount of data used.

33. The method of claim 32, wherein, The statistical methods include one or more of the following: Statistical methods based on radio bearer (RB); Statistical methods based on Quality of Service (QoS) flow; Session-based statistical methods; Statistical methods based on user devices; Statistical methods based on slicing or transmission requirements; Statistical methods based on task type; or Statistical methods based on session endpoints.

34. The method of claim 29, wherein, The data usage report includes data volume information and / or data task information.

35. The method of claim 34, wherein, The data usage report may also include one or more of the following: user identifier ID, protocol data unit (PDU) session ID, timestamp, traffic type, or quality of service (QoS) metrics.

36. The method of claim 29, wherein: The wireless access network node is configured with data plane application functions, or has a communicable connection with a node configured with the data plane application functions. The URR is obtained via the data plane application function.

37. The method of claim 36, wherein: The wireless access network node reports the data usage report to the billing function CHF node through the data plane application function.

38. The method of claim 36, in, The acquisition of URR includes: acquiring dynamic rules from the policy control function (PCF) node via the data plane application function; The data plane application function transforms the dynamic rules into detection, reporting, and transmission rules that can be executed by the wireless network access node.

39. The method of claim 29, wherein: The wireless access network node directly reports the data usage report to the billing function CHF node.

40. The method of claim 39, wherein, The acquisition of URR includes: Retrieve dynamic rules from the policy control function PCF node; and The dynamic rules are transformed into detection, reporting, and transmission rules that can be executed by the wireless network access node.

41. A data transmission method, performed by a wireless access network node, comprising: Receive the first data transmission request from the data plane application function node; and Send a second data transmission request to the user equipment (UE); in, The first data transmission request and the second data transmission request include transmission mode information and / or data task information; The transmission mode information is used to indicate whether the data transmission method is control plane transmission, user plane transmission, or data plane transmission. The data task information is used to indicate the data task corresponding to the data transmission.

42. The method of claim 41, wherein: The data plane application function is deployed inside the radio access network node, or deployed in a data plane application function network element shared by multiple radio access network nodes.

43. The method of claim 41, wherein: The first data transmission request and the second data transmission request also include a destination node identifier, which is used to indicate the destination node of the data transmission. The destination node includes the radio access network node or other independent data plane application function node, and the radio access network node is configured with the data plane application function node.

44. A communication device comprising a processor and a memory, the memory storing program instructions which, when executed by the processor, implement the method as claimed in any one of claims 5 to 43.

45. A storage medium storing program instructions that, when executed by a processor, implement the method as claimed in any one of claims 5 to 43.