Communication method and apparatus

Abstract

A communication method and apparatus. The method comprises: when an SMF network element receives first information used for instructing an access network to participate in calculation / processing of a data packet of a current protocol data unit (PDU) session, the SMF network element configures, for the access network, a PDR corresponding to the first information. For example, the SMF network element sends a configuration of the PDR corresponding to the first information, and on the basis of the configured PDR, an RAN can filter / classify a data packet calculated / processed by the RAN, and map said data packet to a corresponding quality of service flow, thereby meeting the requirement of introducing a new service function to an access network side.

Description

A communication method and apparatus

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411531333.7, filed on October 29, 2024, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0004] As radio access network (RAN) architecture evolves, the RAN will integrate more new service functions beyond communication, such as artificial intelligence (AI) and sensing. Under these new service functions, the RAN will perform calculations / processing on data packets. Therefore, the RAN also needs to classify / filter data packets. How the RAN classifies / filters the data packets after calculation / processing is a research direction. Summary of the Invention

[0005] In a first aspect, a communication method is provided, which is applied to a session management function network element. The execution subject of the method is the session management function network element, or a module, unit, or component (e.g., chip, chip system, circuit, processor, or others) applied in the session management function network element. The method includes: receiving first information, which is used to instruct the access network to calculate / process data packets participating in the current Protocol Data Unit (PDU) session; and sending the configuration of a data packet detection rule (PDR) corresponding to the first information, wherein the PDR is used to map the data packets calculated / processed by the access network to a first quality of service (QoS) flow, and the first QoS flow is included in the PDU session.

[0006] Based on the above design, taking the Session Management Function (SMF) network element as an example, when the SMF network element receives the first information used to instruct the access network to participate in the current PDU session, it configures the PDR corresponding to the first information for the access network. For example, the SMF network element sends the configuration of the PDR corresponding to the first information, and the RAN can filter / classify the data packets calculated / processed by the RAN according to the configured PDR, mapping the data packets calculated / processed by the RAN to the corresponding Quality of Service (QoS) stream, thus meeting the requirements of the access network side for introducing new service functions.

[0007] In one possible implementation, the first information includes a first indication, a slice identifier, or a data network name, wherein the first indication is used to indicate the calculation / processing of data packets by which the access network participates in the PDU session.

[0008] In one possible implementation, the method further includes: sending a service quality flow list corresponding to the PDU session, wherein the service quality flow list contains one or more service quality flows with a second indication, the second indication being used to instruct the central unit to send the data packet to the service unit when the service quality flow receives the data packet.

[0009] In one possible implementation, the method further includes: determining the configuration of the PDR based on the first information.

[0010] In one possible implementation, determining the configuration of the PDR based on the first information includes: determining the configuration of the PDR based on the address information of the central unit or service unit and the first information.

[0011] In one possible implementation, receiving the first information includes: receiving first information from a central unit or an access and mobility management function network element; sending the configuration of the PDR corresponding to the first information includes: sending the configuration of the PDR corresponding to the first information to the central unit.

[0012] In one possible implementation, receiving the first information includes: receiving first information from an access and mobility management function network element; sending the configuration of the PDR corresponding to the first information includes: sending the configuration of the PDR corresponding to the first information to a service unit or a central unit.

[0013] Through the above design, the Session Management Function (SMF) network element can configure the PDR to the service unit (SU) or the centralized unit (SU). The service unit or centralized unit can then classify / filter the data packets calculated / processed by the access network (SU) according to the configured PDR, so as to meet the service quality flow requirements of different types of data packets.

[0014] In one possible implementation, the method further includes determining the service unit based on the slice identifier or data network name.

[0015] In one possible implementation, the method further includes: receiving address information of the service unit related to a first tunnel, wherein the first tunnel is a tunnel between the service unit and the central unit.

[0016] In one possible implementation, the method further includes sending the address information of the service unit associated with the first tunnel to the central unit.

[0017] In one possible implementation, the method further includes: sending a second message to the user plane function network element, the second message being used to instruct / request the user plane function network element to establish at least two tunnels, the at least two tunnels including a second tunnel and a third tunnel, the second tunnel being the tunnel between the user plane function network element and the centralization unit, and the third tunnel being the tunnel between the user plane function network element and the service unit.

[0018] Through the above design, the session management function network element (such as the SMF network element) can request the user plane function network element (such as the UPF network element) to establish at least two tunnels. One tunnel is the third tunnel connecting the UPF network element and the SU, and the other tunnel is the second tunnel connecting the UPF network element and the CU. Through the above design, user plane data packets can be directly transmitted between the UPF network and the SU without the need for CU forwarding, which simplifies the data packet transmission path and improves the data packet transmission efficiency.

[0019] In one possible implementation, the method further includes sending the identifier of the quality of service flow associated with the second tunnel and the identifier of the quality of service flow associated with the third tunnel to the user plane function network element.

[0020] In one possible implementation, the method further includes: receiving address information of the user plane function network element associated with the second tunnel and address information of the user plane function network element associated with the third tunnel from the user plane function network element.

[0021] In one possible implementation, the method further includes: sending the address information of the user plane function network element associated with the second tunnel and the address information of the user plane function network element associated with the third tunnel to the centralizing unit; or, sending the address information of the user plane function network element associated with the second tunnel to the centralizing unit and sending the address information of the user plane function network element associated with the third tunnel to the serving unit.

[0022] In one possible implementation, the method further includes: sending third information to the service unit, the third information being used to instruct / request the service unit to establish at least two tunnels, the at least two tunnels including a third tunnel and a first tunnel, the third tunnel being a tunnel between the user plane function network element and the service unit, and the first tunnel being a tunnel between the central unit and the service unit.

[0023] In one possible implementation, the method further includes sending to the service unit the identifier of the quality of service flow associated with the third tunnel and the identifier of the quality of service flow associated with the first tunnel.

[0024] In one possible implementation, the method further includes receiving address information of the service unit associated with the third tunnel and address information of the service unit associated with the first tunnel from the service unit.

[0025] In one possible implementation, the method further includes: sending the address information of the service unit related to the third tunnel to the user plane function network element; and sending the address information of the service unit related to the first tunnel to the centralization unit.

[0026] The second aspect, a method corresponding to the first aspect, with beneficial effects as described in the first aspect, provides a communication method. This method is applied to a centralized unit or a service unit, and the executing entity of the method is a centralized unit or a service unit, or is applied to a module, unit, or component (e.g., chip, chip system, circuit, processor, or others) within a centralized unit or service unit. The method includes: receiving the configuration of a Packet Detection Rule (PDR) corresponding to first information, where the first information is used to instruct the access network to calculate / process packets participating in the current Protocol Data Unit (PDU) session, and the PDR is used to map the packets calculated / processed by the access network to a first Quality of Service (QoS) stream, which is included in the PDU session.

[0027] In one possible implementation, the method further includes: mapping the data packets calculated / processed by the access network to the first quality of service flow according to the PDR.

[0028] In one possible implementation, the method further includes sending the first information.

[0029] In one possible implementation, the first information includes a first indication, a slice identifier, or a data network name, wherein the first indication is used to indicate the calculation / processing of data packets by which the access network participates in the PDU session.

[0030] In one possible implementation, the method is applied to a central unit and further includes: receiving a service quality flow list corresponding to the PDU session from a session management function network element, wherein the service quality flow list contains one or more service quality flows with a second indication, the second indication being used to instruct the central unit to send the data packet to the service unit when the service quality flow receives a data packet.

[0031] In one possible implementation, the method is applied to a centralized unit, and receiving the configuration of the PDR corresponding to the first information includes: receiving the configuration of the PDR corresponding to the first information from a session management function network element.

[0032] In one possible implementation, the PDR configuration is also included: sending the configuration to the service unit.

[0033] In one possible implementation, the method further includes: receiving address information of the user plane function network element related to the second tunnel and address information of the user plane function network element related to the third tunnel from the session management function network element, wherein the second tunnel is the tunnel between the user plane function network element and the centralization unit, and the third tunnel is the tunnel between the user plane function network element and the service unit.

[0034] In one possible implementation, the method further includes sending the address information of the user plane function network element related to the third tunnel to the service unit.

[0035] In one possible implementation, it further includes: receiving address information of the service unit related to the third tunnel from the service unit.

[0036] In one possible implementation, the method further includes sending the address information of the service unit related to the third tunnel to the session management function network element.

[0037] In one possible implementation, the method is applied to a central unit or a service unit, and receiving the configuration of the PDR corresponding to the first information includes: receiving the configuration of the PDR corresponding to the first information from a session management function network element.

[0038] In one possible implementation, the method is applied to the service unit and further includes: sending the address information of the service unit related to the first tunnel to the session management function network element, wherein the first tunnel is a tunnel between the service unit and the central unit.

[0039] In one possible implementation, the method is applied to the service unit and further includes: receiving third information from the session management function network element, the third information being used to instruct / request the service unit to establish at least two tunnels, the at least two tunnels including a third tunnel and a first tunnel, the third tunnel being a tunnel between the user plane function network element and the service unit, and the first tunnel being a tunnel between the centralization unit and the service unit.

[0040] In one possible implementation, it further includes: receiving the identifier of the third tunnel-related quality of service flow and the identifier of the first tunnel-related quality of service flow from the session management function network element.

[0041] In one possible implementation, the method further includes sending the address information of the service unit associated with the third tunnel and the address information of the service unit associated with the first tunnel to the session management function network element.

[0042] In one possible implementation, the method is applied to a central unit and further includes: receiving uplink data packets from a terminal through the PDU session; sending the uplink data packets to the service unit; receiving calculated / processed uplink data packets from the service unit; and sending the calculated / processed uplink data packets to the user plane function network element.

[0043] In one possible implementation, receiving uplink data packets from the terminal through the PDU session includes: receiving uplink data packets from the terminal through a second quality of service stream included in the PDU session; if the second quality of service stream contains the second indication, then the step of sending the uplink data packets to the service element is performed; the method further includes: if the second quality of service stream does not contain the second indication, then the uplink data packets are sent to the user plane function network element.

[0044] In one possible implementation, the method is applied to a centralized unit and further includes: receiving downlink data packets from a user plane function network element through the PDU session; sending the downlink data packets to the service unit; receiving calculated / processed downlink data packets from the service unit; and sending the calculated / processed downlink data packets to the terminal.

[0045] In one possible implementation, receiving downlink data packets from the user plane function network element through the PDU session includes: receiving downlink data packets from the user plane function network element through a third quality of service flow included in the PDU session; if the third quality of service flow has the second indication, then the step of sending the downlink data packets to the service unit is performed; the method further includes: if the third quality of service flow does not have the second indication, then the downlink data packets are sent to the terminal.

[0046] In one possible implementation, the method is applied to a service unit and further includes: receiving uplink data packets from a central unit; calculating / processing the uplink data packets; and sending the calculated / processed uplink data packets to the central unit.

[0047] In one possible implementation, the method is applied to a service unit and further includes: receiving downlink data packets from a central unit; performing calculations / processing on the downlink data packets; and sending the calculated / processed downlink data packets to the central unit.

[0048] In one possible implementation, the method is applied to a central unit and further includes: receiving uplink data packets from a terminal; and sending the uplink data packets to the service unit.

[0049] In one possible implementation, receiving uplink data packets from a terminal includes: receiving uplink data packets from the terminal via a fourth Quality of Service (QoS) flow; if the fourth QoS flow has the second indication, performing the step of sending the uplink data packets to the service element; the method further includes: if the fourth QoS flow does not have the second indication, sending the uplink data packets to the user plane function network element.

[0050] In one possible implementation, the method is applied to a central unit and further includes: receiving processed / computed downlink data packets from a service unit; and sending the processed / computed downlink data packets to a terminal.

[0051] In one possible implementation, the method is applied to a service unit and further includes: receiving uplink data packets from a central unit; performing calculations / processing on the uplink data packets; and sending the calculated / processed uplink data packets to a user plane function network element.

[0052] In one possible implementation, the method is applied to a service unit and further includes: receiving downlink data packets from a user plane function network element; performing calculations / processing on the downlink data packets; and sending the calculated / processed downlink data packets to a central unit.

[0053] In one possible implementation, the method is applied to a centralized unit, wherein the calculated / processed uplink data packet contains indication information for indicating the uplink transmission direction, and the calculated / processed uplink data packet is sent to the user plane function network element according to the indication information of the uplink transmission direction; or, the calculated / processed downlink data packet contains indication information for indicating the downlink transmission direction, and the calculated / processed downlink data packet is sent to the terminal according to the indication information of the downlink transmission direction.

[0054] In one possible implementation, the method is applied to a service unit and further includes: adding indication information for indicating the uplink transmission direction to the calculated / processed uplink data packet; or, adding indication information for indicating the downlink transmission direction to the calculated / processed downlink data packet.

[0055] Thirdly, a communication method is provided, which is applied to a session management function network element. The execution subject of the method is the session management function network element, or it is applied to a module, unit, or component (such as a chip, chip system, circuit, processor, or others) in the session management function network element. The method includes: sending second information to a user plane function network element, the second information being used to request / instruct the user plane function network element to establish at least two tunnels, the at least two tunnels including a second tunnel and a third tunnel, the second tunnel being a tunnel between the user plane function network element and a centralization unit, and the third tunnel being a tunnel between the user plane function network element and a service unit; receiving address information of the user plane function network element related to the second tunnel and address information of the user plane function network element related to the third tunnel from the user plane function network element.

[0056] Through the above design, the session management function network element (such as the SMF network element) requests the user plane function network element (such as the UPF network element) to establish at least two tunnels. These at least two tunnels include a second tunnel connecting the UPF network element to the CU and a third tunnel connecting the UPF network element to the SU. The UPF network element communicates directly with the SU through the third tunnel, without the need for CU forwarding, thus improving data transmission efficiency.

[0057] In one possible implementation, the method further includes sending the identifier of the quality of service flow associated with the second tunnel and the identifier of the quality of service flow associated with the third tunnel to the user function network element.

[0058] In one possible implementation, the method further includes sending the address information of the user plane function network element associated with the second tunnel and the address information of the user plane function network element associated with the third tunnel to the central unit.

[0059] In one possible implementation, it further includes: receiving address information of the central unit associated with the second tunnel and address information of the service unit associated with the third tunnel from the central unit.

[0060] In one possible implementation, the method further includes sending the address information of the centralized unit related to the second tunnel and the address information of the service unit related to the third tunnel to the user plane function network element.

[0061] In one possible implementation, the method further includes: sending the address information of the user plane function network element associated with the second tunnel to the central unit; and sending the address information of the user plane function network element associated with the third tunnel to the service unit.

[0062] In one possible implementation, the method further includes: sending third information to the service unit, the third information being used to instruct / request the service unit to establish at least two tunnels, the at least two tunnels including a third tunnel and a first tunnel, the third tunnel being a tunnel between the user plane function network element and the service unit, and the first tunnel being a tunnel between the central unit and the service unit.

[0063] In one possible implementation, the method further includes sending to the service unit the identifier of the quality of service flow associated with the third tunnel and the identifier of the quality of service flow associated with the first tunnel.

[0064] In one possible implementation, the method further includes receiving address information of the service unit associated with the third tunnel and address information of the service unit associated with the first tunnel from the service unit.

[0065] In one possible implementation, the method further includes: sending the address information of the service unit related to the third tunnel to the user plane function network element; and sending the address information of the service unit related to the first tunnel to the centralization unit.

[0066] In one possible implementation, the method further includes: receiving first information, the first information being used to instruct the access network to participate in the calculation / processing of data packets in the current Protocol Data Unit (PDU) session; and sending the configuration of a Packet Detection Rule (PDR) corresponding to the first information, the PDR being used to map the data packets calculated / processed by the access network to a first Quality of Service (QoS) flow, the first QoS flow being included in the PDU session.

[0067] Fourthly, as a counterpart to the third aspect, and with beneficial effects referring to the description of the third aspect, a communication method is provided. This method is applied to a user plane function network element, and the executing entity of the method is the user plane function network element, or it is applied to a module, unit, or component (such as a chip, chip system, circuit, processor, or others) within the user plane function network element. The method includes: receiving second information from a session management function network element, the second information being used to request / instruct the user plane function network element to establish at least two tunnels, the at least two tunnels including a second tunnel and a third tunnel, the second tunnel being a tunnel between the user plane function network element and a centralization unit, and the third tunnel being a tunnel between the user plane function network element and a service unit; and sending to the session management function network element the address information of the user plane function network element related to the second tunnel and the address information of the user plane function network element related to the third tunnel.

[0068] In one possible implementation, it further includes: receiving the identifier of the second tunnel-related quality of service flow and the identifier of the third tunnel-related quality of service flow from the session management function network element.

[0069] In one possible implementation, it further includes: receiving address information of the centralized unit associated with the second tunnel and address information of the service unit associated with the third tunnel from the session management function network element.

[0070] Fifthly, as a counterpart to the third aspect, and with beneficial effects referring to the description of the third aspect, a communication method is provided. This method is applied to a service unit, and the executing entity of the method is the service unit, or it is applied to a module, unit, or component (such as a chip, chip system, circuit, processor, or others) within the service unit. The method includes: receiving third information from a session management function, the third information being used to instruct / request the service unit to establish at least two tunnels, the at least two tunnels including a third tunnel and a first tunnel, the third tunnel being a tunnel between a user plane function network element and the service unit, and the first tunnel being a tunnel between a centralization unit and the service unit; and sending to the session management function network element the address information of the service unit associated with the third tunnel and the address information of the service unit associated with the first tunnel.

[0071] In one possible implementation, it further includes: receiving the identifier of the third tunnel-related quality of service flow from the session management function, and the identifier of the first tunnel-related quality of service flow.

[0072] In one possible implementation, it further includes: receiving address information of the user plane function network element associated with the third tunnel from the session management function and address information of the central unit associated with the first tunnel.

[0073] In one possible implementation, it further includes: configuring a Packet Detection Rule (PDR) corresponding to the first information, wherein the PDR is used to map the data packets calculated / processed by the access network to the first quality of service flow.

[0074] In one possible implementation, the method further includes: mapping the data packets calculated / processed by the access network to the first quality of service flow according to the PDR.

[0075] Sixthly, an apparatus is provided capable of implementing the methods of any one of the first to fifth aspects described above. For example, the apparatus includes modules, units, or components corresponding to the methods described in any one of the first to fifth aspects. The modules, units, or components may be implemented in hardware, software, or a combination of hardware and software.

[0076] In one design, the device includes a unit that performs the methods of any one of the first to fifth aspects described above.

[0077] In one design, the device includes a processor for implementing the methods of any one of the first to fifth aspects described above. Optionally, the device further includes a memory, with the processor coupled to the memory, the processor executing computer programs or instructions stored in the memory, causing the device to implement the methods of any one of the first to fifth aspects described above.

[0078] In one design, the device includes a processor and an interface circuit, the interface circuit being used to receive signals from other devices outside the device and transmit them to the processor or to send signals from the processor to other devices outside the device, the processor being used to implement the methods of any one of the first to fifth aspects described above through logic circuits or executing code instructions.

[0079] In one design, the device may be a first device, or a module, unit, or component (e.g., a chip, chip system, circuit, or processor, etc.) that corresponds one-to-one with the method / operation / step / action described in any of the first to fifth aspects of the first device, or a device that can be used in conjunction with the first device.

[0080] In a seventh aspect, a computer-readable storage medium is provided, storing a computer program or instructions that, when executed on a computer, cause the computer to implement the methods of any one of the first to fifth aspects described above.

[0081] Eighthly, a computer program product is provided, comprising a computer program or instructions that, when executed by a computer, cause the methods of any one of the first to fifth aspects to be performed.

[0082] A ninth aspect provides a chip including a processor for implementing the methods of any one of the first to fifth aspects described above. Optionally, the chip further includes a memory, the processor being coupled to the memory, the processor being configured to execute computer programs or instructions stored in the memory, such that the chip implements the methods of any one of the first to fifth aspects described above.

[0083] A tenth aspect provides a communication system, comprising: a first communication device and a second communication device; wherein the first communication device is configured to implement the method of the first aspect; and the second communication device is configured to implement the method of the second aspect. Alternatively, the first communication device is configured to implement the method of the third aspect; and the second communication device is configured to implement the method of the fourth aspect. Optionally, the system further comprises a third communication device configured to implement the method of the fifth aspect. Attached Figure Description

[0084] Figures 1a to 1d are schematic diagrams of the network architecture provided in the embodiments of this application;

[0085] Figure 2 is a flowchart illustrating the communication method provided in Embodiment 1 of this application;

[0086] Figures 3 and 5 are schematic diagrams of the specific application process of the process shown in Figure 2;

[0087] Figures 4 and 6 show the data plane protocol stack provided in the embodiments of this application;

[0088] Figure 7 is a flowchart illustrating the communication method provided in Embodiment 2 of this application;

[0089] Figures 8 and 9 are schematic diagrams of the specific application process of the process shown in Figure 7;

[0090] Figure 10 is a flowchart provided in Embodiment 3 of this application;

[0091] Figure 11 is a schematic diagram of the ORAN architecture provided in an embodiment of this application;

[0092] Figures 12 and 13 are schematic diagrams of the structure of the device provided in the embodiments of this application. Detailed Implementation

[0093] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings. The specific operating methods and functional descriptions in the method embodiments can also be applied to the device embodiments or system embodiments.

[0094] In this application, the number of nouns, unless otherwise specified, refers to "singular nouns or plural nouns," that is, "one or more." "At least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates that the preceding and following related objects have an "or" relationship; in the formulas of this application, the character " / " indicates that the preceding and following related objects have a "division" relationship. "Including at least one of A, B, or C" or similar expressions can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B, and C, where A, B, and C can be singular or plural.

[0095] In the embodiments of this application, the various numerical designations are used for ease of description and are not intended to limit the scope of the embodiments of this application. The order of the process numbers does not imply the order of execution; the execution order of each process should be determined by its function and internal logic. The ordinal numbers such as "first" and "second" used in the embodiments of this application are used to distinguish multiple objects and do not limit the size, order, timing, priority, or importance of the multiple objects. Furthermore, for ease of description, the embodiments of this application use descriptions such as "Embodiment 1," "Embodiment 2," and "Embodiment 3." It is understood that the textual descriptions in different embodiments can be referred to mutually.

[0096] To advance the evolution of next-generation radio access network (RAN) architectures, the RAN will integrate more new service functions beyond communication, such as artificial intelligence (AI) and sensing. These new functions are typically based on general-purpose hardware designs, exhibiting heterogeneity from the dedicated hardware architectures upon which traditional communication is based. To meet the needs of rapid deployment and independent evolution of these new service functions on the basis of the existing highly integrated dedicated RAN architecture, a new RAN functional architecture based on service units (SUs) is introduced. In this architecture, new service functions are integrated through SUs, while central units (CUs) / distributed units (DUs) maintain existing communication functions. SUs and CUs communicate via Si interfaces. SUs can function as functional network elements within a base station or as independent functional network elements outside the base station. The connection relationship between SUs and CUs can be 1:1 or 1:n. Depending on the interface type between the SU / CU and the core network (CN), this application provides four network architectures, as detailed in Figures 1a to 1d below.

[0097] As shown in Figure 1a, a network architecture applicable to embodiments of this application is provided. As shown in Figure 1a, the access network includes logical nodes such as CU, DU, and SU. A CU can control at least one DU, and the CU can be connected to the DU via an interface, for example, this interface can be called an F1 interface. Further, the control plane (CP) interface can be called F1-C, and the user plane (UP) interface can be called F1-U. Optionally, the access network also includes a radio unit (RU), where a DU can control at least one RU, and the DU can be connected to the RU via an interface, for example, this interface can be a fronthaul interface. The RU is connected to a terminal. CU and DU, etc., can undertake the communication functions of the access network. SU can carry new service functions of the access network, such as AI, sensing, and positioning, etc. The SU is connected to the CU via an interface, for example, this interface can be a Si interface.

[0098] 1. CU

[0099] A CU can be a logical node that carries the radio resource control (RRC) layer, service data adaptation protocol (SDAP) layer, packet data convergence protocol (PDCP) layer, and other control functions of the access network. In other words, a CU can implement the functions of the RRC layer, SDAP layer, PDCP layer, and some control functions.

[0100] Furthermore, the CU can be divided into CU-CP and CU-UP. CU-CP is a logical node carrying the control plane (control plane part of PDCP, PDCP-C) of the RRC and PDCP layers, used to implement the CU's control plane functions. CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements in the core network can be access and mobility function network elements, such as the access and mobility management function (AMF) network elements in a 5G communication system. CU-UP is a logical node carrying the data plane (user plane part of PDCP, PDCP-U) of the SDAP and PDCP layers, used to implement the CU's user plane functions. CU-UP can interact with network elements in the core network used to implement user plane functions, such as the user plane function (UPF) in a 5G communication system.

[0101] 2. DU

[0102] A DU (Distributed Unit) can be a logical node carrying functions from the radio link control (RLC) layer, media access control (MAC) layer, higher physical layer (PHY) layer, and other functionalities. For example, the higher physical layer may include some of the processing functions of the physical layer (PHY), such as forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation. In other words, a DU can implement the functions of the RLC layer, MAC layer, higher physical layer, and other functionalities.

[0103] It is understood that the above CU and DU configurations are merely examples, and the functions of the CU and DU can be configured as needed. For instance, the CU or DU can be configured to have more protocol layer functions, or it can be configured to have only some protocol layer processing functions. For example, some functions of the RLC layer and the protocol layer functions above the RLC layer can be placed in the CU, while the remaining functions of the RLC layer and the protocol layer functions below the RLC layer can be placed in the DU. Furthermore, the functions of the CU or DU can be divided according to service type or other system requirements, such as by latency, placing functions that need to meet low latency requirements in the DU and functions that do not need to meet such latency requirements in the CU.

[0104] 3. RU

[0105] An RU can be a logical node that carries both lower physical layer (PHY) and radio frequency (RF) chain processing. For example, the lower physical layer includes some of the processing functions of the physical layer, such as fast Fourier transform (FFT), inverse fast Fourier transform (IFFT), digital beamforming, and filtering. In other words, an RU can implement both physical layer and RF functions.

[0106] In one possible implementation, the RU can be a 3GPP transmission reception point (TRP), a remote radio head (RRH), or other similar entity. The RU communicates with one or more terminals via a wireless link.

[0107] In this context, DU and RU can be co-located or non-co-located, without restriction. For example, the interaction between DU and RU may include the O-RAN control user and synchronization (CUS-Plane) and the O-RAN management plane (M-Plane). The O-RAN CUS plane can be abbreviated as CUS plane, and the O-RAN management plane can be abbreviated as management plane. O-RAN stands for Open RAN (O-RAN), and O-RAN can be abbreviated as ORAN. Furthermore, the CUS plane can be divided into the control plane (C-Plane) and the user plane (U-Plane). Optionally, the control plane refers to the real-time control plane between DU and RU. The management plane refers to the non-real-time management operations between DU and RU.

[0108] In one possible implementation, the DU and RU exchange control plane and user plane information via a lower-layer split CUS-Plane (LLS-CUS) interface through a fronthaul link. Further, the LLS-CUS interface may include an LLS-C interface corresponding to the control plane and an LLS-U interface corresponding to the user plane. The DU and RU exchange management plane information through the LLS-M interface of the fronthaul link. Optionally, the LLS-M interface can also be used to connect to an external management system.

[0109] It is understandable that DUs and RUs can cooperate to implement physical layer functions. A DU can be connected to one or more RUs. The functions of DUs and RUs can be configured in various ways depending on the design. For example, a DU can be configured to implement baseband functions, and an RU can be configured to implement mid-RF functions. Another example is that a DU can be configured to implement higher-level functions in the physical layer, and an RU can be configured to implement lower-level functions in the physical layer, or to implement both lower-level and RF functions. Higher-level functions in the physical layer may include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions may include another portion of the physical layer's functions that are closer to the mid-RF side.

[0110] 4. SU

[0111] The SU (Subscriber Unit) can carry / be responsible for new functions of the access network besides communication. These new functions may include sensing, positioning, AI prediction, and AI computing. For example, sensing can refer to the access network using the transmission, reflection, and scattering of radio waves to perceive the physical world and obtain sensing data. For instance, an access network device emits an electromagnetic signal; when this signal reaches a target, it is reflected by the target, forming a reflected signal. The access network device receives this reflected signal, which can be used as sensing data. Sensing data can exist in the form of a sensing point cloud, which is a data set composed of three-dimensional coordinate points. The SU can obtain the sensing point cloud when implementing the sensing function. Alternatively, the SU can determine the sensing result based on the sensing point cloud, which includes information such as the position, speed, angle, and trajectory of the perceived target. Positioning can refer to the access network device obtaining the location information of a terminal through a positioning algorithm. This location information includes three dimensions: longitude, latitude, and altitude. AI prediction refers to the access network device's ability to make predictions. For example, the access network device can use AI models, combined with various parameters, to predict the performance of the communication network. AI computing functionality refers to the ability of access network devices to assist terminals or networks in completing AI computing tasks.

[0112] In different systems, CU (or CU-CP and CU-UP), DU, RU, or SU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, RU can also be called O-RU, and SU can also be called O-SU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, RU, and SU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, RU, and SU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0113] In Figure 1a, the CU is connected to the AMF network element on the core network side via an interface, for example, the N2 interface. Interactions between the CU and various control network elements in the core network are relayed through the AMF network element. It is understood that the core network includes control plane network elements such as AMF, session management function (SMF), and network exposure function (NEF), as well as user plane network elements, such as user plane function (UPF) network elements. Each control network element in the core network is connected to the service bus, and direct communication occurs between the various core network control plane network elements through the service bus. There are no restrictions on the names of the network elements in the core network. For example, in a 5G communication system, the network element implementing the signaling processing part is called an AMF network element. As the network evolves, the network element implementing the above functions may also be called by other names in future communication networks. In this application embodiment, the scheme of this application embodiment is mainly described using the names of various network elements in 5G as examples. Optionally, in addition to the above description, the core network may also include other control plane network elements, such as unified data management (UDM) network elements, without limitation.

[0114] In Figure 1a, the DU is connected to the terminal via a wireless link. A terminal is a device with wireless transceiver capabilities. Terminals can also be called terminal equipment, user equipment (UE), mobile station, mobile terminal equipment, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. This application does not limit the device form of the terminal.

[0115] In the network architecture of Figure 1a, the access network includes logical nodes such as SU, CU, and DU. The access network can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a base station in a future communication network, or an access node in a wireless fidelity (WiFi) system. The access network can be a macro base station, a micro base station or indoor station, a relay node or donor node, or a wireless controller in a cloud radio access network (CRAN) scenario. Optionally, the access network can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network device in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of the access network in this embodiment can be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The access network in this application embodiment can also be a logical node, logical module, or software that can implement all or part of the access network functions.

[0116] In the network architecture of Figures 1a to 1d of this application, the DU is connected to the terminal. It can be understood that the DU and the terminal may also include the RU, meaning that the access network includes not only logical nodes such as SU, CU, and DU, but also RU. One side of the RU is connected to the DU, and the other side of the RU is connected to the terminal. The network architecture of Figures 1a to 1d also includes a server. The server may be included in the data network (DN). The destination of uplink data transmission can be the server. For example, the UPF network element sends the received uplink data packets to the server. The starting point of downlink data transmission can be the server. For example, the server sends downlink data packets to the UPF network element. Specific uplink / downlink transmission paths can have different implementations, as described below.

[0117] As shown in Figure 1b, another network architecture applicable to embodiments of this application is provided. The difference between the network architecture in Figure 1b and Figure 1a is that in Figure 1b, the CU accesses the service-based bus through a service-based interface (SBI), and the CU communicates directly with the control plane network elements of the core network without the need for relay by the AMF network elements.

[0118] Understandably, in the network architectures of Figures 1a and 1b, the SU is invisible to the core network side, and the core network side is unaware of the SU's existence. The core network side can only perceive that the access network side has certain new service capabilities, but is unaware of the integration methods of the various logical nodes within the access network side. In the network architectures of Figures 1a and 1b, the SU can serve as a functional network element / unit within the access network.

[0119] As shown in Figure 1c, another network architecture applicable to embodiments of this application is provided. The difference between the network architecture of Figure 1c and Figure 1a is that in Figure 1a, the SU interacts with the various control plane network elements of the core network through the CU. In Figure 1c, the SU connects to the service bus through the SBI interface, and the SU can directly interact with the various control plane network elements of the core network. For example, the SU can directly access the various control plane network elements of the core network.

[0120] As shown in Figure 1d, another network architecture applicable to embodiments of this application is provided. The difference between the network architecture in Figure 1d and Figure 1a is that in Figure 1d, there is a Ni interface between the SU and AMF network elements. The SU interacts directly with the AMF through the Ni interface without needing to go through the CU for relay. The SU interacts with various control plane network elements of the core network, which are forwarded by the AMF network elements.

[0121] Understandably, in the network architectures of Figures 1c and 1d, the CU is visible to the core network side, and the core network side can perceive the existence of the SU, as well as the new service functions possessed by the SU. In the network architectures of Figures 1c and 1d, the SU can serve as a functional network element / unit within the access network (this is mainly illustrated in Figures 1c and 1d), or the SU can serve as a functional network element / unit outside the access network.

[0122] Optionally, in the network architecture of Figures 1a to 1d, the SU and UPF network elements can be directly connected / communicate. Thus, in data plane transmission, the SU and UPF network elements can directly transmit data without the need for CU relay.

[0123] In the current scheme, the terminal can filter / classify uplink data packets, mapping them to corresponding quality of service (QoS) flows, and then sending the uplink data packets to the UPF network element through the corresponding QoS flows. The UPF network element can filter / classify downlink data packets, mapping them to corresponding QoS flows, and then sending the downlink data packets to the terminal through the corresponding QoS flows.

[0124] For example, for uplink data packets, the terminal filters / classifies the uplink data packets based on the packet filter in the QoS rule, mapping the uplink data packets to the corresponding QoS flow. This QoS rule can be configured to the terminal by the SMF network element during the PDU session establishment or modification process. For instance, the SMF network element configures the QoS rule for the terminal through non-access stratum (NAS) messages. Alternatively, the terminal can derive the QoS rule through a reflection QoS mechanism.

[0125] For example, for downlink data packets, the UPF network element filters / classifies the data packets based on the packet filter in the Packet Detection Rule (PDR) and maps them to the corresponding Quality of Service (QoS) flow. The PDR can be configured by the SMF network element to the UPF network element during the creation or modification of the PDU session. For instance, if the interface between the SMF and UPF network elements is the N4 interface, the SMF network element sends an N4 message to the terminal to configure the PDR.

[0126] In one implementation, the packet filter can be an Internet Protocol (IP) packet filter. The classification criteria for IP packet filters mainly include: the IP address / port of the sender and receiver, and the protocol type (IPv4, IPv6). Taking the IP address of the sender and receiver as a classification criterion, for example, an IP packet filter stores a mapping relationship between (source IP address + destination IP address) and Quality of Service (QoS) flows. When a terminal or UPF network element receives a packet, it can query the corresponding QoS flow from the stored mapping relationship based on the source and destination IP addresses contained in the packet.

[0127] In another implementation, the packet filter can be an Ethernet packet filter. Ethernet packet filters are classified primarily based on information such as the MAC addresses of the sending and receiving ends. For example, the classifier of an Ethernet packet filter stores a mapping relationship between (source MAC address + destination MAC address) and Quality of Service (QoS) flows. When a terminal or UPF network element receives a packet, it can look up the corresponding QoS flow in its stored mapping relationship based on the source and destination MAC addresses included in the packet.

[0128] As the RAN architecture evolves, the RAN side can integrate new service functions beyond traditional communication functions, such as AI, sensing, and positioning, as mentioned above. In these new service function scenarios, the RAN side needs to process data packets (such as uplink / downlink data packets). The service quality flow requirements of the data packets before and after RAN processing may differ. For example, the data types of the data packets before and after RAN processing may be different, and different types of data packets have different service quality flow requirements. Therefore, the RAN side needs to have data packet classification / filtering capabilities to map the processed data packets to the corresponding service quality flow and transmit them to the corresponding receiver through the corresponding data radio bearer (DRB) or tunnel. How the RAN side obtains the PDR and maps the processed data packets to the corresponding service quality flow is the problem to be solved in this application.

[0129] In view of the above, embodiments of this application provide a communication method and apparatus. The method includes: when an SMF network element receives first information for calculating / processing a data packet that instructs the access network to participate in a current protocol data unit (PDU) session, the SMF network element configures a PDR corresponding to the first information for the access network. For example, the SMF network element sends the configuration of the PDR corresponding to the first information, and the RAN can filter / classify the data packets calculated / processed by the RAN according to the configured PDR, mapping the data packets calculated / processed by the RAN to the corresponding quality of service stream, thereby meeting the requirements of the access network side for introducing new service functions.

[0130] It is understood that the communication method provided in this application embodiment has different processes under different network architectures. For example, under the network architectures of Figures 1a and 1b, the corresponding processes can be found in Embodiment 1 below. Under the network architectures of Figures 1c and 1d, the corresponding processes can be found in Embodiment 2 below.

[0131] In this application, "sending information to (such as an SMF)" can be understood as the destination of the information being the SMF. This can include sending information directly or indirectly to (such as an SMF). "Receiving information from (such as an SMF)" can be understood as the source of the information being the SMF, which can include receiving information directly or indirectly from the SMF. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly, and will not be elaborated further here.

[0132] In the various flowcharts of this application, the executing entity can be an SMF, CU, SU, etc., or a module, unit, or component (such as a chip, chip system, processor, circuit, or others) within an SMF, CU, SU, etc. The following description uses SMF, CU, and SU as examples of executing entities. When the executing entity is a module, unit, or component within an SMF, CU, SU, receiving / transmitting can be understood as input / output, that is, the module communicates with other modules or components. For example, "transmitting" can also be understood as the "output" of a chip interface, and "receiving" can also be understood as the "input" of a chip interface. "Transmitting" or "receiving" can also occur within a device, for example, through a bus, wiring, or interface between components, modules, chips, software modules, or hardware modules within the device.

[0133] Example 1

[0134] The scheme of this embodiment can be applied to the network architecture shown in Figure 1a or Figure 1b. In the network architecture of Figure 1a or Figure 1b, the SU interacts with the control plane network elements (such as SMF) on the core network side through the CU.

[0135] Figure 2 shows the flow of a communication method, including:

[0136] Step 210: The CU / AMF network element sends the first information to the SMF network element, and the SMF network element receives the first information from the CU / AMF network element.

[0137] In one possible implementation, the terminal sends first information to the access network, which may be carried / included in the PDU session establishment request in step 310 below. When / after the CU, as a logical node of the access network, obtains the first information: In the network architecture shown in Figure 1a, since the CU has an interface with the AMF network element, such as the N2 interface, the CU can send (e.g., transparently transmit) the first information to the AMF network element, and the AMF network element can send the first information to the SMF network element. This first information may be carried / included in the PDU session context establishment request in step 330 below. Alternatively, in the network architecture shown in Figure 1b, the CU is directly connected to the SMF network element, and the CU sends the first information to the SMF network element.

[0138] The first information is used to instruct the access network to participate in the calculation / processing of data packets in the current PDU session. For example, the first information includes a first indication, a slice identifier, or a Data Network Name (DNN), where the first indication instructs the access network to participate in the calculation / processing of data packets in the PDU session. In one description, when the access network supports / possesses new functions other than communication functions, the access network device performs calculation / processing on the data packets corresponding to the new functions. The specific process of the access network (such as the SU) calculating / processing data packets is related to the new functions provided by the access network. For example, the new function could be the sensing function, positioning function, AI prediction function, or AI calculation function mentioned above. Taking the AI ​​calculation function as an example, the access network receives data packets (such as receiving uplink data packets from a terminal or downlink data packets from a UPF network element), and the access network uses an AI model to calculate the received data packets to obtain the AI ​​calculation result. For example, the access network inputs the received data packets into the AI ​​model, and the output of the AI ​​model can be considered the AI ​​calculation result. The AI ​​calculation result is considered the data packet calculated / processed by the access network. In one description, the new function provided by the access network may be referred to as access network (e.g., RAN) / local service, and the first indication may be referred to as access network (e.g., RAN) / local service indication.

[0139] Optionally, in step 220: the SMF network element determines the PDR configuration based on the first information.

[0140] For example, the SMF network element determines the PDR configuration based on the address information of the CU or SU and the first information. In one possible implementation, the SMF network element provides the aforementioned CU or SU address information and the first information to the Unified Data Management (UDM) network element. The UDM network element stores the PDR configuration. The UDM network element searches for the PDR configuration that matches the information provided by the SMF network element and returns the searched PDR configuration to the SMF network element. For example, the SMF network element can obtain the CU or SU address information in the following way: As described above, the CU or AMF network element sends the first information to the SMF network element. For example, if the CU sends the first information to the SMF network element, the SMF network element, as the receiving end, can obtain the address of the sending end CU corresponding to the first information. Alternatively, the CU or AMF network element can also send the CU address or CU identifier to the SMF network element. The CU address or CU identifier and the first information can be carried / included in a message, for example, the message name is PDU Session Context Establishment Request. In scenarios where the SMF network element obtains the CU's identifier, the SMF network element can determine the CU's address information based on the CU's identifier. Optionally, the mapping between the CU's identifier and its address information can be configured by the Operation Administration and Maintenance (OAM) network element for the SMF network element. In scenarios where the CU and SU are in a 1:1 ratio, the SMF network element can obtain the SU's address based on the CU's address or identifier. In scenarios where the CU and SU are in a 1:n ratio, where n is an integer greater than 1, the SMF network element can select a SU as the appropriate SU and obtain its address information. Optionally, the mapping between CU and SU is configured by the OAM network element for the SMF network element.

[0141] Step 230: The SMF network element sends the PDR configuration to the CU, and the CU receives the PDR configuration from the SMF network element.

[0142] In one possible implementation, the CU can perform packet classification / filtering. For example, the CU determines the PDR based on the PDR configuration. The PDR is used to map packets calculated / processed by the access network (e.g., the SU) to corresponding Quality of Service (QoS) flows (e.g., referred to as the first QoS flow), which are contained in the PDU session. The CU classifies / filters packets according to the PDR. For example, it maps packets calculated / processed by the access network (e.g., the SU) to corresponding QoS flows (e.g., the first QoS flow) based on the PDR. Alternatively, the SU can perform packet classification or filtering. In this case, the method in the flow of Figure 2 further includes:

[0143] Optionally, in step 240: the CU sends the configuration of the PDR to the SU, and the SU receives the configuration of the PDR from the CU.

[0144] For example, the SU determines the PDR based on the PDR configuration. Based on the PDR, the SU maps the data packets calculated / processed by the access network (such as the SU) to the corresponding Quality of Service (QoS) flow (such as the first QoS flow).

[0145] In other words, the PDR configured by the SMF network element can be sent / configured to the CU for packet mapping, or it can be further sent / configured to the SU by the CU for packet mapping.

[0146] In one possible implementation, the CU or SU can classify / filter the data packets (hereinafter referred to as data packets) calculated / processed by the access network according to the PDR configured in the SMF network element, and map the data packets to the corresponding Quality of Service (QoS) flows. For example, the PDR includes at least one piece of information and a mapping relationship between it and the QoS flows. This at least one piece of information can be a single piece of information or a collection of multiple pieces of information, without limitation. For example, this at least one piece of information can be a data type. For example, the CU or SU can extract the data type corresponding to the data packet from the packet header, look up the QoS flow corresponding to the current data type in the mapping relationship between the data type and the QoS flows stored in the PDR, and map the current data packet to the corresponding QoS flow for transmission. Alternatively, this at least one piece of information can be a port address, which can also be called a port number. Optionally, the port address can include a source port address and a destination port address. For example, data packets for different programs (or services or applications) can be transmitted through different ports. For example, some program data packets require intermediate / secondary processing in the access network, while data packets for other programs do not require intermediate / secondary processing in the access network. The CU or SU can determine the Quality of Service (QoS) flow corresponding to the port address information of the current data packet based on the mapping relationship between port addresses and QoS flows stored in the PDR, and transmit the current data packet through the corresponding QoS flow. For example, the aforementioned information may include: IP address (or Ethernet address), data type (or port address), etc. In other words, the PDR includes: IP address (or Ethernet address), data type (or port address), and the mapping relationship between QoS flows, etc. The CU or SU can determine the QoS flow corresponding to the current data packet based on the mapping relationship between IP address and data type, etc., and QoS flows included in the PDR.

[0147] The following description primarily uses the mapping relationship between addresses and Quality of Service (QoS) flows in PDR as an example. This address can include source and destination addresses, and further, it also includes intermediate addresses, which can be understood as addresses of access networks (such as SU or CU). The addresses mentioned above can refer to IP addresses or MAC addresses, without restriction. The CU or SU maps data packets to the corresponding QoS flows based on the address information included in the data packets. Of course, in one implementation, in addition to considering the address information of the data packets, other information carried / contained in the data packets may also need to be considered, without restriction. For example, the port address or data type of the data packet, etc.

[0148] For example, in one possible implementation, the PDR includes packet filters, such as IP packet filters or Ethernet packet filters. The CU or SU can classify or filter packets (such as uplink or downlink packets) according to the packet filters included in the PDR. Specifically, the packet filters store mapping relationships. For example, for an IP packet filter, the mapping relationship can be a mapping relationship between (source IP address + destination IP address) and the Quality of Service (QoS) flow; for an Ethernet packet filter, the mapping relationship can be a mapping relationship between (source MAC address + destination MAC address) and the QoS flow. The CU or SU can extract the corresponding source address information and destination address information from the received packets, input the above source address information and destination address information into the packet filter, and query the corresponding QoS flow. Alternatively, the mapping relationship stored in the packet filter can be: (source address + access network address + destination address). For uplink packets, the source address can refer to the terminal's address, and the destination address can refer to the server's address. For downlink packets, the source address can refer to the server's address, and the destination address can refer to the terminal's address. For example, in this embodiment, the packet carries three address information: the source address, the access network address, and the destination address. Of course, the aforementioned access network address specifically refers to the address of the access network that performs intermediate / secondary processing on the data packet, such as the address of the SU. Alternatively, in one interpretation, the mapping relationship stored in the data packet filter can be a mapping relationship between (source address + destination address) and the Quality of Service (QoS) flow. Naturally, the source address and destination address can be IP addresses, MAC addresses, etc., without restriction. For uplink data transmission, the source address can be the terminal's address, and the destination address can be the access network's address. In this case, the access network device performs secondary / intermediate processing on the uplink data packet before sending it to the UPF network element. For downlink data transmission, the source address can be the server's address, and the destination address can be the access network's address (such as the SU). The access network performs secondary / intermediate processing on the downlink data packet before sending it to the terminal.

[0149] In the description of this application, the data packet calculated / processed by the access network can be alternatively described as: the data packet calculated / processed by the SU. It is understood that the access network / SU can perform calculations / processing on uplink data packets, or on downlink data packets. Specifically, the data packet calculated / processed by the access network / SU can refer to either the uplink data packet calculated / processed by the access network / SU, or the downlink data packet calculated / processed by the access network / SU.

[0150] The following explains PDU sessions and Quality of Service (QoS) flows: A PDU session is a data transmission channel between a terminal and a server, used for communication between them. For example, the data transmission path corresponding to a PDU session is: terminal—access network—UPF network element—server. The server can be located in the data network (DN). A PDU session is established between each terminal and the server. This PDU session can contain / be configured with one or more QoS flows. In one understanding, QoS flows are mechanisms used to manage network quality and determine the priority of data traffic transmission. They ensure that different types of data flows, such as voice, video, and data, receive matching levels of service. Their main goal is to enable the network to prioritize traffic, including providing dedicated bandwidth, controlling latency jitter, and reducing delays. In another understanding, the one or more QoS flows contained in a PDU session may have different priorities, or the one or more QoS flows contained in a PDU session may have different transmission parameters (such as bandwidth, latency, etc.), resulting in different priorities for these one or more QoS flows. In this application, since the access network (such as the SU) processes the received data packets, the data packets before and after processing have different requirements for the Quality of Service (QoS) stream. Therefore, the access network needs to re-filter / classify the calculated / processed data packets and map them to the corresponding QoS stream. For example, in one implementation, the access network (such as the SU) provides AI services, specifically text-to-image / video conversion. The access network converts received text-related data packets into image / video-related data packets. Before filtering / classifying the data packets, the SU or CU transmits the data packets through QoS stream M. That is, the SU or CU can receive the data packets through QoS stream M. There are no restrictions on the entity that performs the mapping of the data packets to QoS stream M. For example, for downlink data transmission, the UPF network element can map the data packets to QoS stream M for transmission. Or, for uplink data transmission, the terminal can map the data packets to QoS stream M for transmission. The SU calculates / processes the data packets received through QoS stream M, converting the data packets into image / video-related data packets, or, as described, converting the data packet type from text to image or video. The SU or CU maps image / video type data packets to Quality of Service (QoS) stream N according to the configured PDR. For example, the PDR stores the mapping relationship between data types and QoS streams. The SU or CU can send image / video type data packets to the receiving end through QoS stream N. M and N are both positive integers, and their values ​​are not equal. For instance, the SU performs data packet filtering according to the configured PDR. The SU can receive text-related data packets through QoS stream M, and through calculation / processing, convert the text-related data packets into image / video-related data packets.The SU maps image / video related data packets to Quality of Service (QoS) flow N according to the configured PDR. The SU then sends these image / video related data packets to the receiving end via QoS flow N. Alternatively, the CU performs packet filtering according to the configured PDR. The SU can send the calculated / processed image / video related data packets to the CU, in which case the data packets can be transmitted via QoS flow M. The CU maps image / video related data packets to QoS flow N according to the configured PDR and sends them to the receiving end via QoS flow N. The receiving end can be understood as a terminal or a UPF network element. The image / video related data packets mentioned above are simply referred to as data packets. In different implementations, the paths for the SU / CU to send data packets to the receiving end may differ. For example, when the receiving end is a terminal: the CU sends data packets to the terminal via QoS flow N. For the SU, it needs to send data packets to the CU via QoS flow N, and the CU uses QoS flow N to send / forward the data packets to the terminal. Alternatively, when the receiving end is a UPF network element, the CU can send data packets to the UPF network element via QoS flow N. For the SU, data packets need to be sent to the CU via QoS flow N, and the CU then sends the data packets to the UPF network element via QoS flow N. Alternatively, when the SU is directly connected to / communicates with the UPF network element, the SU sends data packets directly to the UPF network element via QoS flow N, etc.

[0151] Optionally, in step 250: the SMF network element sends the service quality flow list corresponding to the PDU session to the CU, and the CU receives the service quality flow list corresponding to the PDU session from the SMF network element.

[0152] For example, a Quality of Service (QoS) flow list is a list of requested QoS flows. The QoS flow list contains one or more identifiers (such as QFI) for requesting the establishment of QoS flows. In this application, the following two descriptions are used: "The QoS flow list contains one or more QoS flows," or "The QoS flow list contains one or more identifiers (such as QFI) for QoS flows." These two descriptions convey the same meaning and essentially describe that the QoS flow list may include one or more identifiers for QoS flows, which are used to identify the aforementioned one or more QoS flows.

[0153] When / after receiving the Quality of Service (QoS) flow list from an SMF network element, the CU can establish one or more corresponding QoS flows based on the list. In one possible implementation, the QoS flow list contains one or more QoS flows with a second indication. This second indication instructs the CU to send the data packet to the SU when it receives a data packet from the QoS flow included in the list, or it instructs the data packet of the corresponding QoS flow to undergo secondary / intermediate processing on the access network side. In one description, the second indication may be called a secondary / intermediate processing indication. In other words, the secondary / intermediate processing performed by the SU or the access network side can be limited to data packets transmitted on the QoS flows for which the second indication exists in the QoS flow list. If the CU receives a data packet from a QoS flow that does not have a second indication or is not in the list, the CU may not need to send the data packet to the SU or perform secondary / intermediate processing on the access network side. For example, the CU can directly send the data packet to the receiving end (e.g., a terminal or a UPF network element).

[0154] For example, the Quality of Service (QoS) flow list contains identifiers for QoS flows 1 through QoS flows 5, and the identifiers for QoS flows 1 and 2 have a second indication. During data transmission: When the CU receives a data packet through QoS flow 1 or QoS flow 2, it sends the data packet to the SU according to the second indication corresponding to the identifier of QoS flow 1 or QoS flow 2. The SU processes / calculates the data packet and sends the processed data packet to the receiving end. When the CU receives a data packet through QoS flows 3, 4, or 5, since the identifiers of these QoS flows do not have a second indication, the CU can directly send the data packet to the receiving end without processing by the SU.

[0155] In this process, the Quality of Service (QoS) flow list in step 250 and the PDR configuration in step 230 can be carried / included in the same message, or carried / included in separate messages, without restriction. For example, in the process shown in Figure 3 below, the PDR configuration and the QoS flow list are both included in the PDU session resource establishment request.

[0156] During the establishment of a PDU session, the method provided in Figure 2 is applied, specifically referring to the flow in Figure 3 of Example 1 and the flow in Figure 4 of Example 2 below. It should be understood that the flows shown in Figures 3 and 4 are specific examples of the flow shown in Figure 2.

[0157] Example 1, as shown in Figure 3, provides a flow chart of a communication method applicable to the scenario in Figure 1a or Figure 1b where the SU is connected / communicates with the UPF network element via the CU, including:

[0158] Step 310: The terminal sends a PDU session establishment request to the AMF network element, and the AMF network element receives the PDU session establishment request from the terminal.

[0159] For example, the English name for a PDU session establishment request is (PDU Session Establishment Req). The PDU session establishment request includes first information, such as a slice identifier, a Data Network Name (DNN), or a first indication. The slice identifier and DNN indicate the access network's (e.g., RAN) involvement in the processing / calculation of data packets for the current PDU session. The first indication instructs the access network (e.g., RAN) to participate in the calculation / processing of data packets for the current PDU session. Alternatively, the PDU session establishment request sent by the terminal may include a slice identifier or DNN, and the AMF network element can determine the first indication based on the slice identifier or DNN. The first information described in this process can be understood as a slice identifier, DNN, or first indication, without limitation.

[0160] In the description of this application, the calculation / processing of data packets in the current PDU session by the access network can be replaced with: access network (such as RAN) service, or local service, or access network local service. For example, the first indication used to indicate the calculation / processing of data packets in the current PDU session by the access network (such as RAN) can be replaced with: the first indication used to indicate access network / local service, and the name of the first indication can be replaced with: access network (such as RAN) service indication, or local service indication.

[0161] Optionally, in step 320: the AMF network element performs access control based on the terminal's location information and the first information.

[0162] For example, the English name for the terminal's location information is (User location info, ULI), and the English name for access control is (access control). For example, the terminal's location information could be the identifier of the cell the terminal is currently accessing. The AMF network element can determine the access network (such as the RAN) the terminal is accessing based on the terminal's location information. Further, it determines whether the service type requested by the terminal is consistent with the service type supported by the access network the terminal is currently accessing. If they are consistent, the terminal's service request is approved, and step 330 continues; otherwise, the terminal's service request is rejected. For example, the AMF network element sends a PDU session establishment response to the terminal, which carries an indication of rejection or failure. In one interpretation, the service type requested by the terminal is the service type indicated by the first information, that is, the service type requested by the terminal is access network / local service. If the access network the terminal is currently accessing does not support local services, it is considered that the service type requested by the terminal is inconsistent with the service type supported by the access network, and the terminal's service request is rejected. Alternatively, if the access network the terminal is currently accessing supports local services, it is considered that the service type requested by the terminal is consistent with the service type supported by the access network, and the AMF network element approves the terminal's service request and continues step 330. For example, the process by which an AMF network element obtains whether the access network currently accessed by a terminal supports or does not support local services may include: As mentioned earlier, the AMF network element can determine the access network accessed by the terminal based on the terminal's location information. The AMF network element can then determine whether the access network currently accessed by the terminal supports local services. For instance, when the access network accesses the AMF network element, it reports information about whether the access network supports local services to the AMF network element.

[0163] Step 330: The AMF network element sends a PDU session context establishment request to the SMF network element, and the SMF network element receives the PDU session context establishment request from the AMF network element.

[0164] For example, the English name of a PDU session context creation request could be (Nsmf_PDUSession_CreateSMContext Request). This PDU session context creation request contains initial information, such as a slice identifier, DNN, or initial indication.

[0165] Step 340: The SMF network element determines the PDR configuration based on the first information.

[0166] For example, the SMF network element can determine the type of service requested by the terminal based on the first information. The type of service requested by the terminal can be: access network (such as RAN) / local service, that is, the access network equipment participates in the calculation / processing of the current PDU session. The SMF network element obtains the PDR configuration corresponding to the service requested by the terminal, which is the PDR configuration corresponding to the first information. In this application, the process by which the SMF network element obtains the PDR configuration corresponding to the access network / local service is not limited. For example, as described in the flowchart of Figure 2, the SMF network element can obtain the PDR configuration in the UDM network element.

[0167] In one possible implementation, the PDR corresponding to the first information, or the PDR corresponding to the access network / local service, satisfies the following condition: the PDR stores the correspondence between (source address + destination address) and the quality of service flow. For example, the PDR contains a packet filter, and the packet filter stores the correspondence between (source address + destination address) and the quality of service flow. In this application, the type of packet filter is not limited; it can be an IP packet filter, an Ethernet packet filter, or other types of packet filters. The source address and destination address can refer to IP addresses, such as source IP address and destination IP address; or they can refer to MAC addresses, such as source MAC address and destination MAC address; or they can refer to port addresses, such as source port address and destination port address. For example, for uplink data transmission, the (source address and destination address) can be (terminal address and access network / server address), respectively. For downlink data transmission, the (source address and destination address) can be (access network / server address and terminal address), respectively.

[0168] Alternatively, the PDR stores the mapping between (source address + access network address + destination address) and the Quality of Service (QoS) flow. The access network address can refer to the IP address, MAC address, or port address of the access network (e.g., SU). For uplink data transmission, the (source address, access network address, and destination address) stored in the PDR are respectively (terminal address, access network (e.g., SU) address, and server address). For downlink data transmission, the (source address, access network address, and destination address) stored in the PDR are respectively (server address, access network address, and terminal address).

[0169] Step 350: The SMF network element sends the PDR configuration to the UPF network element, and the UPF network element receives the PDR configuration from the SMF network element.

[0170] For example, the interface between the SMF network element and the UPF network element is an N4 interface. During the process of establishing an N4 session between the SMF and UPF network elements, the SMF network element sends a PDR configuration to the UPF network element. For instance, the SMF network element sends an N4 session Establishment request to the UPF network element, which includes the PDR configuration. In response to the N4 session Establishment request, the UPF network element sends an N4 session Establishment response to the SMF network element; through this process, an N4 session is established between the SMF and UPF network elements.

[0171] In this application, there is no restriction on whether the PDR configuration sent by the SMF network element to the UPF network element is the same as the PDR corresponding to the first information obtained by the SMF network element in step 340. For example, the SMF network element can configure the PDR for the UPF network element according to the current scheme, or the SMF network element can configure the PDR corresponding to the first information obtained in step 340 to the UPF network element, etc., without restriction. Regarding the case where the SMF network element configures the same PDR for the UPF network element and the access network, that is, the SMF network element configures the PDR corresponding to the first information to both the UPF network element and the access network, it can be understood that the PDR corresponding to the first information is a very broad range of PDRs, which includes both the PDR required / corresponding to the UPF network element and the PDR required / corresponding to the access network. When the access network side performs filtering / classification / mapping based on this PDR, it can use the PDR related to the access network side. When the UPF network element performs filtering / classification / mapping based on this PDR, it can use the PDR related to the UPF network element.

[0172] Step 360: The SMF network element sends a PDU session resource establishment request to the CU through the AMF network element, and the CU receives the PDU session resource establishment request from the SMF network element through the AMF network element.

[0173] For example, the English name of a PDU session resource setup request is (PDU Session Resource Setup Request). The PDU session resource setup request includes the configuration of the PDR corresponding to the first information. Optionally, the PDU session resource setup request also includes a QoS flow list. The QoS flow list contains one or more QoS flows, which are the QoS flows requested by the CU to establish. In one description, the QoS flow list included in the PDU session resource setup request can be described as: QoS Flow Setup Request List. One or more QoS flows included in the QoS flow list have a second indication. The process by which the SMF network element determines whether a QoS flow in the QoS flow list exists / contains a second indication is not limited. For example, for a QoS flow used to transmit communication data, the QoS flow does not exist / does not contain a second indication. Or, if the QoS flow is used to transmit data requiring secondary / intermediate processing by the access network, the QoS flow contains / contains a second indication. Alternatively, if a Quality of Service (QoS) stream is used to transmit data for a first application (or service or program), and the data for the first application does not require intermediate / secondary processing by the access network, then the QoS stream does not have a second indication. Alternatively, if the QoS stream is used to transmit data for a second application (or service or program), and the data for the second application requires intermediate / secondary processing by the access network, then the QoS stream has a second indication.

[0174] In one possible implementation, if the CU supports filtering / classification / mapping functions, then the CU can perform packet filtering / classification / mapping according to the PDR configuration. For example, during data plane data transmission, the CU can filter / classify / mapping the received packets according to the PDR configuration. Understandably, this packet could be an uplink packet originating from the terminal, or it could be a downlink packet originating from a UPF network element.

[0175] Alternatively, in another possible implementation, if the SU supports filter cartridge / sorting / mapping functions, the CU can send the PDR configuration received in step 360 to the SU. In this case, optionally, the method in the flowchart of Figure 3 further includes:

[0176] Step 370: The CU sends the PDR configuration to the SU, and the SU receives the PDR configuration from the CU.

[0177] Step 380: Establish a session for local services between the terminal / CU / SU.

[0178] The English name for establishing a local service session can be "local service session establishment." Since the access network (such as the SU) provides local services, the CU sends received data packets (such as uplink or downlink data packets) to the SU for calculation / processing. The SU then sends the calculated / processed data packets back to the CU, and the CU then sends the calculated / processed data packets back to the receiving end. The process of establishing a local service session in step 380 includes at least establishing a tunnel between the CU and the SU. For example, the CU and SU can exchange their respective address information. For instance, the CU sends its address information to the SU, and the SU sends its address information to the CU.

[0179] As is understandable, the process shown in Figure 3 is mainly based on the network architecture shown in Figure 1a. In the network architecture shown in Figure 1a, the CU interacts with the control network elements (such as the SMF) on the core network side through the AMF network element. Therefore, in step 310, the terminal sends a PDU session establishment request to the AMF through the CU, and the AMF network element interacts with the SMF network element. For example, in step 330, the AMF network element sends a PDU session context establishment request to the SMF network element, and in step 360, the SMF network element sends a PDU session resource establishment request to the CU through the AMF network element.

[0180] In the network architecture shown in Figure 1b, the CU can directly interact with the core network control elements (such as the SMF) through the SBI interface. Therefore, step 310 in the flowchart of Figure 3 can be replaced by: the terminal sending a message containing first information to the SMF element, such as a PDU session establishment request or other message names. Step 320 can be replaced by: the CU or SMF element performing access control based on the terminal's location information and the first information. Step 330 can be omitted. Step 360 can be replaced by: the SMF element directly sending a message containing PDR configuration to the CU, such as a PDU session resource establishment request or other message names.

[0181] In the network architecture of Figure 1a or Figure 1b, control plane interactions between the SU and the core network are forwarded by the CU, and data plane interactions between the SU and the core network are forwarded by the CU. For example, the transmission path for uplink data is: Terminal → DU / CU → SU → CU → UPF → Server. The transmission path for downlink data is: Server → UPF → CU → SU → CU / DU → Terminal. The user plane protocol stack between the terminal, DU / CU, DU, and server is shown in Figure 4.

[0182] Uplink data transmission

[0183] According to the process shown in Figure 3, a PDU session can be established between the terminal and the server. During the establishment of the PDU session, the SMF network element can configure a PDR for the CU or SU. The CU or SU can filter / classify uplink data packets according to the configured PDR, mapping the uplink data packets to the corresponding Quality of Service (QoS) stream. The process of the CU or SU filtering / classifying uplink data packets is explained below. In uplink data transmission: The terminal sends uplink data packets to the CU (via the DU) through the PDU session; correspondingly, the CU receives uplink data packets from the terminal (via the DU) through the PDU session. The CU sends uplink data packets to the SU, and the SU receives uplink data packets from the CU. The SU performs calculations / processing on the uplink data packets. There are no restrictions on the specific calculation / processing process of the SU. For example, the specific calculation / processing process of the SU is related to the specific new service functions provided by the access network. The SU sends the calculated / processed uplink data packets to the CU, and the CU receives the calculated / processed uplink data packets from the SU. The CU sends the calculated / processed uplink data packets to the UPF network element, and the UPF forwards the received uplink data packets to the server.

[0184] In one possible implementation, the CU receives uplink data packets from the terminal via a PDU session, including: the CU receiving uplink data packets from the terminal through a Quality of Service (QoS) flow (e.g., a second QoS) included in the PDU session. The CU determines whether the data packets transmitted on the second QoS flow require secondary / intermediate processing by the access network (e.g., the SU). For example, the CU determines whether the second QoS flow contains a second indication. Whether the second QoS flow included in the current PDU session contains a second indication is configured to the CU by the SMF network element in step 360 of the flowchart in Figure 3. If the data packets corresponding to the second QoS flow require secondary / intermediate processing by the access network (e.g., the SU), the CU sends the uplink data packets to the SU for corresponding calculation / processing. Alternatively, if the second QoS flow does not contain a second indication, it means that the data packets corresponding to the second QoS flow do not require secondary / intermediate processing by the access network (e.g., the SU), and the CU can directly send the uplink data packets to the UPF network element at the receiving end.

[0185] Downlink data transmission

[0186] According to the process shown in Figure 3, a PDU session can be established between the terminal and the service. During the establishment of the PDU session, the SMF network element can configure a PDR for the CU or SU. The CU or SU can filter / classify downlink data packets according to the configured PDR, mapping the downlink data packets to the corresponding quality of service flow. The process of the CU or SU filtering / classifying downlink data packets is explained below. In downlink data transmission: The CU receives downlink data packets from the UPF network element through the PDU session. Of course, this downlink data packet is sent from the server to the UPF network element. The CU sends downlink data packets to the SU, and the SU receives downlink data packets from the CU. The SU performs calculations / processing on the downlink data packets. The SU sends the calculated / processed downlink data packets to the CU, and the CU receives the calculated / processed downlink data packets from the SU. The CU (via DU) sends the calculated / processed downlink data packets to the terminal, and the terminal (via DU) receives the calculated / processed downlink data packets from the CU.

[0187] In one possible implementation, the CU receives downlink data packets from the UPF network element via a PDU session. This includes the CU receiving downlink data packets from the UPF network element through a Quality of Service (QoS) flow (e.g., a third QoS flow) included in the PDU session. The CU determines whether the data packets transmitted on the third QoS flow require secondary / intermediate processing by the access network (e.g., the SU). For example, the CU determines whether a second indication exists in the third QoS flow. It is understood that in step 360 of the flowchart in Figure 3, the SMF network element can configure the CU to determine whether a second indication exists in the third QoS flow. If a second indication exists in the third QoS flow, it indicates that the data packets corresponding to the third QoS flow require secondary / intermediate processing by the access network (e.g., the SU). The CU sends the downlink data packets to the SU, which performs the corresponding calculations / processing on the downlink data packets. Alternatively, if a second indication does not exist in the third QoS flow, it indicates that the data packets corresponding to the third QoS flow do not require secondary / intermediate processing by the access network (e.g., the SU), and the CU can send the downlink data packets to the terminal via the DU.

[0188] As described above, the CU can forward data packets to the SU for secondary / intermediate processing based on the presence of a second indication in the Quality of Service (QoS) flow, or directly send the data packets to the receiving end (such as a UPF network element or terminal). In another possible implementation, if the CU supports parsing the packet header, the CU can forward the received data packets based on the destination address carried / contained in the packet header. This method is applicable to both uplink and downlink data transmission. For example, when the CU receives a data packet from a UPF network element or terminal: if the destination address carried / contained in the packet header is the address of the access network (such as the SU), the packet is forwarded to the SU for secondary / intermediate processing; or, if the destination address carried / contained in the packet header is the address of the terminal or the address of the server, the packet is forwarded to the terminal or the UPF network element. Optionally, the SMF or AMF network elements can be configured with the terminal address, server address, and access network address for the CU. Alternatively, the data packets described herein may be IP data packets, and the source address and destination address carried / contained by the data packets may be the source IP address and the destination IP address, respectively.

[0189] As described above, regardless of whether it's uplink or downlink data transmission, after the SU performs calculations / processing on the data packets, it sends the calculated / processed data packets back to the CU. The CU then sends the calculated / processed data packets to the receiving end (such as a UPF network element or terminal). In one possible implementation, the CU supports parsing the packet header. When the CU receives the calculated / processed data packets from the SU, it can forward the data packets to the corresponding receiving end based on the destination address carried / contained in the data packets. For example, if the destination address carried / contained in the data packets is a terminal, the data packets are sent to the terminal. Or, if the destination address carried / contained in the data packets is a server, the data packets are sent to the UPF network element. Of course, the CU needs to know the addresses of the terminal and the UPF network element. In another possible implementation, the CU does not support parsing the packet header (in this case, the SU performs packet filtering / classification and adds the corresponding Quality of Service Flow (QFI) identifier to the data packets). The SU can indicate the transmission direction of the data packets. For example, in uplink data transmission, the SU can add indication information to the calculated / processed uplink data packets to indicate the uplink transmission direction. In downlink data transmission, the SU can add indication information to the calculated / processed downlink data packet to indicate the downlink transmission direction. The CU can forward the calculated / processed data packet based on the transmission direction indication information carried in the received calculated / processed data packet from the SU. For example, if the calculated / processed uplink data packet contains indication information for the uplink transmission direction, the CU will send the calculated / processed uplink data packet to the UPF network element according to the uplink transmission direction indication information; or, if the calculated / processed downlink data packet contains indication information for the downlink transmission direction, the CU will send the calculated / processed downlink data packet to the terminal according to the downlink transmission direction indication information.

[0190] In this application, the CU can perform packet classification / filtering according to the PDR configuration. For example, the CU receives a calculated / processed data packet from the SU, which can be a downlink or uplink data packet, without restriction. Based on the PDR, the CU maps the calculated / processed data packet from the access network (e.g., the SU) to a Quality of Service (QoS) flow (e.g., referred to as the first QoS flow). Further, the CU adds an identifier of the first QoS flow (e.g., QFI) to the calculated / processed data packet. The CU then sends the calculated / processed data packet to the receiving end (e.g., a UPF network element or terminal) through the first QoS flow.

[0191] Alternatively, the SU can perform packet classification / filtering according to the PDR configuration. For example, the SU receives packets from the CU, which can be downlink or uplink packets, without restriction. The SU performs calculations / processing on the packets; according to the PDR, the SU maps the calculated / processed packets from the access network (e.g., the SU) to a Quality of Service (QoS) flow (e.g., the first QoS flow). Further, the SU adds the identifier of the first QoS flow (e.g., QFI) to the calculated / processed packets. The SU sends the calculated / processed packets to the CU through the first QoS flow. The CU sends the calculated / processed packets to the receiving end (e.g., a UPF network element or terminal) through the first QoS flow.

[0192] In one example, the CU / SU determines a quality of service flow (referred to as the first quality of service flow) corresponding to the calculated / processed data packet based on the mapping relationship between (source address + destination address) and quality of service flow stored in the PDR, or the mapping relationship between (source address + access network address + destination address) and quality of service flow stored in the PDR.

[0193] Optionally, the tunnel between the CU and SU can be a GTP User Plane (GTP-U) tunnel. GTP stands for GPRS Tunneling Protocol, and GPRS stands for General Packet Radio Service. The CU and SU can transmit corresponding data or information through this GTP-U tunnel. For example, the CU can forward received data packets to the SU through the GTP-U tunnel, and the SU can calculate / process the received data packets and then send the calculated / processed data / information back to the CU through the GTP-U tunnel. The CU and the terminal can also transmit corresponding data through a data radio bearer (DRB). For example, when the data packets received by the CU do not require intermediate / secondary processing in the access network, the CU can forward data packets received from the UPF network element to the terminal through the DRB. The CU and UPF network element can also transmit corresponding data through a GTP-U tunnel. For example, when the data packets received by the CU do not require intermediate / secondary processing in the access network, the CU can forward data packets from the terminal to the UPF network element through the GTP-U tunnel.

[0194] In one possible implementation, referring to step 350 in Figure 3 above, the SMF network element configures a PDR for the UPF network element. The UPF network element can filter / classify downlink data packets according to the configured PDR. For example, the PDR stores the mapping relationship between (source address + destination address) and quality of service flow. For instance, if the downlink data packet received by the UPF network element from the server carries / contains (server address + access network address) as its (source address + destination address), it indicates that the downlink data packet needs secondary / intermediate processing by the access network (such as SU). The UPF network element can map the downlink data packet to the quality of service flow that requires intermediate processing and send it to the CU through the corresponding tunnel. Alternatively, if the downlink data packet received by the UPF network element carries / contains (server address + terminal address) as its (source address + destination address), the downlink data packet is mapped to the quality of service flow transparently transmitted by the access network and forwarded to the CU through a tunnel. Optionally, in step 350 above, in addition to configuring PDR for the UPF network element, the SMF network element can also configure a Quality of Service (QoS) flow list for the UPF network element. One or more QoS flows included in this QoS flow list have a second indication. If a QoS flow has a second indication, it means that the data packets of that QoS flow require secondary / intermediate processing by the access network. Alternatively, if a QoS flow does not have a second indication, it means that the data packets of that QoS flow do not require secondary / intermediate processing by the access network; that is, the access network transparently transmits the data packets corresponding to that QoS flow.

[0195] Through the above design, during the establishment of a PDU session, the terminal requests the service type that the access network will participate in for calculation / processing. The SMF network element configures the corresponding PDR for the access network (such as CU or SU) according to the service type requested by the terminal. This enables the access network to filter / classify the calculated / processed data packets when participating in the calculation / processing of the current service, so as to meet the service quality flow requirements of different types of data packets and ensure the user's service experience.

[0196] Example 2, in the network architecture of Figure 1a or Figure 1b. In addition to being connected to the CU, the SU is also directly connected to the UPF network element. Uplink and downlink data transmission between the SU and the UPF network element no longer goes through the CU; the SU directly transmits uplink and downlink data with the UPF network element. The transmission path for uplink data is: Terminal → DU / CU → SU → UPF → Server. The transmission path for downlink data is: Server → UPF → SU → CU / DU → Terminal.

[0197] In Example 2, the SU establishes two tunnels: one for connecting to the CU and the other for connecting to the UPF network element. The UPF network element establishes two tunnels: one for connecting to the CU and the other for connecting to the SU. In the description of this application, the tunnel between the CU and SU is referred to as the first tunnel, the tunnel between the UPF network element and the CU as the second tunnel, and the tunnel between the UPF network element and the SU as the third tunnel.

[0198] In Example 2, the SMF network element can instruct / request the UPF network element to establish at least two tunnels. For example, the SMF network element sends a second message to the UPF network element, and the UPF network element receives the second message from the SMF network element. The second message instructs / requests the UPF network element to establish at least two tunnels, which include a second tunnel and a third tunnel. In response to the SMF network element's instruction / request, the UPF network element returns the address information of the aforementioned at least two tunnels to the SMF network element. For example, in response to the second message, the UPF network element sends the address information of the UPF network element related to the second tunnel and the address information of the UPF network element related to the third tunnel to the SMF network element. Correspondingly, the SMF network element receives the address information of the UPF network element related to the second tunnel and the address information of the UPF network element related to the third tunnel from the UPF network element. The SMF network element then sends the address information of the UPF network element related to the aforementioned at least two tunnels returned by the UPF network element to the CU. For example, the SMF network element sends the address information of the UPF network element related to the second tunnel and the address information of the UPF network element related to the third tunnel to the CU. The CU receives the address information of the UPF network element related to the second tunnel and the address information of the UPF network element related to the third tunnel from the SMF. It can be understood that the address information of the UPF network element related to the second tunnel is used to establish the second tunnel between the UPF network element and the CU. The CU can establish the second tunnel between itself and the UPF network element based on the address information of the UPF network element related to the second tunnel. The address information of the UPF network element related to the third tunnel is used to establish the third tunnel between the UPF network element and the SU. The CU sends the address information of the UPF network element related to the third tunnel to the SU. The SU can establish the third tunnel between itself and the UPF network element based on the address information of the UPF network element related to the third tunnel. Furthermore, the SU can also send the address information of the SU related to the third tunnel to the UPF network element, thereby the SU obtains the address information of the UPF network element related to the third tunnel, and the UPF network element obtains the address information of the SU related to the third tunnel, thus successfully establishing the third tunnel between the UPF network element and the SU. The CU sends its address information related to the second tunnel to the UPF network element, allowing the CU to obtain the address information of the UPF network element related to the second tunnel, and the UPF network element to obtain the address information of the CU related to the second tunnel. The second tunnel is successfully established between the CU and the UPF network element. Furthermore, a first tunnel can also be established between the SU and the CU. In this process: the SU sends its address information related to the first tunnel to the CU, and the CU sends its address information related to the first tunnel to the SU.

[0199] As can be understood, in the above description, the SMF network element sends a second message to the UPF network element to instruct / request the UPF network element to establish at least two tunnels, including a second tunnel and a third tunnel. Optionally, the SMF network element also sends the identifier of the quality of service flow (such as QFI) associated with the second tunnel and the identifier of the quality of service flow (such as QFI) associated with the third tunnel to the UPF network element; correspondingly, the UPF network element receives the identifier of the quality of service flow associated with the second tunnel and the identifier of the quality of service flow associated with the third tunnel from the SMF network element.

[0200] Figure 5 shows a flowchart of a communication method applicable to the case where the SU and UPF network elements are directly connected in Figure 1a or Figure 1b, including:

[0201] Step 510: The terminal sends a PDU session establishment request to the AMF network element, and the AMF network element receives the PDU session establishment request from the terminal.

[0202] For example, the PDU session establishment request may include a slice identifier, a DNN, or a first indication. Alternatively, the PDU session establishment request may include a slice identifier or a DNN. The AMF network element determines the first indication based on the slice identifier or DNN. In this embodiment of the process, the first information can be understood as the slice identifier, DNN, or first indication, etc. The meaning of the first indication can be found in the description of Figure 2.

[0203] Optionally, in step 520: the AMF network element performs access control based on the terminal's location and the first information.

[0204] Step 530: The AMF network element sends a PDU session context establishment request to the SMF network element, and the SMF network element receives the PDU session context establishment request from the AMF network element.

[0205] Step 540: The SMF network element determines the PDR configuration based on the first information.

[0206] For an explanation of steps 510 to 540, please refer to the explanation of steps 310 to 340 in the flowchart of Figure 3.

[0207] Step 550: The SMF network element sends an N4 session establishment request to the UPF network element, and the UPF network element receives the N4 session establishment request from the SMF network element.

[0208] The English name for an N4 session establishment request is (N4 session Establishment Req). For example, an N4 session establishment request includes PDR configuration and second information. The second information is used to request / instruct the UPF network element to establish at least two tunnels, including a second tunnel between the UPF network element and the CU, and a third tunnel between the UPF network element and the SU. For example, the second information can be instruction information, instructing the UPF network element to establish at least two tunnels; or, the second information can be a multiple tunnels request information, requesting the UPF network element to establish at least two tunnels. Optionally, the N4 session establishment request also includes: the QFI associated with each tunnel, for example, the QFI associated with the second tunnel and the QFI associated with the third tunnel. In one understanding, when the SMF network element sends a request to the UPF network element for the establishment of each tunnel's associated QFI, it can be understood as the SMF network element requesting the UPF network element to establish different tunnels for the service quality flows corresponding to different QFIs. For example, for Quality of Service (QoS) flow A, if the data transmitted in QoS flow A requires intermediate / secondary processing by the access network, then the identifier of QoS flow A (such as QFIA) is associated with the third tunnel, or it can be described as: the third tunnel is used to transmit the data of QoS flow A, or the third tunnel is used to transmit data that requires intermediate / secondary processing by the access network. For QoS flow B, if the data transmitted in QoS flow B does not require intermediate / secondary processing by the access network, then the identifier of QoS flow B (such as QFIB) is associated with the second tunnel, or it can be described as: the second tunnel is used to transmit the data of QoS flow B, or the second tunnel is used to transmit data that does not require intermediate / secondary processing by the access network.

[0209] Step 560: The UPF network element sends an N4 session establishment response to the SMF network element, and the SMF network element receives the N4 session establishment response from the UPF network element.

[0210] For example, in response to an N4 session establishment request, the UPF network element sends an N4 session establishment response. The full English name of the N4 session establishment response is (N4 session Establishment Resp). The N4 session establishment response contains the address information of the UPFs corresponding to / associated with each of the multiple tunnels requested by the SMF network element. For example, the address information of the UPF network elements associated with the second tunnel and the third tunnel. The address information can be transparent network layer (TNL) information, such as the Fully Qualified Tunnel Endpoint Identifier (F-TEID).

[0211] Understandably, the UPF network element returns address information for two UPF network elements: the address information for the UPF network element related to the second tunnel and the address information for the UPF network element related to the third tunnel. Optionally, the address information of the UPF network element related to the third tunnel may contain an identifier to indicate that the data transmitted in the tunnel corresponding to that address information needs to be transmitted intermediately / secondarily in the access network.

[0212] Step 570: The SMF network element sends a PDU session resource establishment request to the CU via the AMF network element, and the CU receives the PDU session resource establishment request from the SMF network element via the AMF network element.

[0213] The English name for a PDU session resource setup request is (PDU Session Resource Setup Request). This request includes a list of requested Quality of Service (QoS) flows and the configuration of the PDR corresponding to the first piece of information. One or more QoS flows included in the requested list have a second indication. Optionally, the PDU session resource setup request also includes the address information of the UPF network elements corresponding to multiple tunnels, such as the address information of the UPF network elements related to the second tunnel and the address information of the UPF network elements related to the third tunnel. In one possible implementation, the requested QoS flow list includes identifiers (such as QFIs) for one or more QoS flows, and each QFI has corresponding tunnel address information. For example, if the data transmitted by a QoS flow corresponding to a QFI requires secondary / intermediate processing by the access network, then the tunnel information corresponding to that QFI is the address information of the UPF network element corresponding to the third tunnel. If the data transmitted by a QoS flow corresponding to a QFI does not require secondary / intermediate processing by the access network, meaning that the QoS flow is a transparent QoS flow, then the tunnel information corresponding to that QFI is the address information of the UPF network element corresponding to the second tunnel.

[0214] It is understood that the address information of the UPF network element related to the second tunnel is used to establish the second tunnel between the UPF network element and the CU. The CU establishes the second tunnel between itself and the UPF network element based on the address information of the UPF network element related to the second tunnel. The CU sends the address information of the UPF network element related to the third tunnel to the SU, as explained in step 580 below. The SU establishes the third tunnel between itself and the UPF network element based on the address information of the UPF network element related to the third tunnel. Further, the SU sends the address information of the SU related to the third tunnel to the CU, and the CU sends the address information of the SU related to the third tunnel and the address information of the CU related to the second tunnel to the SMF. The SMF sends the above two address information to the UPF network element, as explained in steps 590 to 5011 below. Further, a first tunnel between the CU and the SU can be established. For example, the CU sends the address information of the CU related to the first tunnel to the SU (refer to the explanation in step 580), and the SU sends the address information of the SU related to the first tunnel to the CU (refer to the explanation in step 590).

[0215] Step 580: The CU sends a Si session establishment request to the SU, and the SU receives the Si session establishment request from the CU.

[0216] The interface between the CU and SU is called Si, and the full English name of the Si session establishment request is (Si session Establishment Req). The Si session establishment request includes: the address information of the CU related to the first tunnel (used to establish the first tunnel between the CU and SU) and the address information of the UPF network element related to the third tunnel (used to establish the third tunnel between the UPF network element and SU). Optionally, if the SU performs packet classification / filtering, the Si session establishment request also includes PDR configuration.

[0217] Step 590: SU sends a Si session establishment response to CU, and CU receives the Si session establishment response from SU.

[0218] For example, in response to a Si session establishment request, the SU sends a Si session establishment response to the CU. The full English name of the Si session establishment response is (Si session Establishment Resp). The Si session establishment response includes at least the address information of two SUs: one SU's address information is used to establish a first tunnel with the CU, and the other SU's address information is used to establish a third tunnel with the UPF network element. For example, the Si session establishment response includes at least the address information of the SU related to the first tunnel and the address information of the SU related to the third tunnel. The CU establishes a first tunnel between the CU and the SU based on the address information of the SU related to the first tunnel. The CU sends the received address information of the SU related to the third tunnel and the address information of the CU related to the second tunnel to the SMF network element. The SMF network element then sends the aforementioned address information to the UPF network element, as detailed in steps 5010 and 5011.

[0219] It is understandable that the SU returns the address information of two SUs: the address information of the SU related to the first tunnel and the address information of the SU related to the third tunnel. The address information of the SU related to the third tunnel may contain an identifier to indicate that the data transmitted in the tunnel corresponding to that address information needs to be processed by the access network in the intermediate / secondary manner.

[0220] Step 5010: The CU sends a PDU session resource establishment response to the SMF network element via the AMF network element, and the SMF network element receives the PDU session resource establishment response from the CU via the AMF network element.

[0221] In response to the PDU session resource establishment request, the CU sends a PDU session resource establishment response. The English name of the PDU session resource establishment response is (PDU Session Resource Setup Response). The PDU session resource establishment response contains the address information of the CU side related to the second tunnel (this address information is used to establish the second tunnel between the CU and the UPF network element) and the address information of the SU side related to the third tunnel (this address information is used to establish the third tunnel between the SU and the UPF network element).

[0222] Step 5011: During the N4 session modification process, the SMF network element sends the address information of the CU related to the second tunnel and the address information of the SU related to the third tunnel to the UPF network element.

[0223] The English name for N4 session modification is (N4 session modification).

[0224] Through the above interaction process, the UPF network element can obtain the address information of the CU in the second tunnel, and the CU can obtain the address information of the UPF network element in the second tunnel. The second tunnel between the UPF network element and the CU is successfully established / completed. Similarly, the UPF network element can obtain the address information of the SU in the third tunnel, and the SU can obtain the address information of the UPF network element in the third tunnel. The third tunnel between the UPF network element and the SU is successfully established / completed. The CU can obtain the address information of the SU in the first tunnel, and the SU can obtain the address information of the CU in the first tunnel. The first tunnel between the CU and the SU is successfully established / completed.

[0225] In this application, the SU can be directly connected to the UPF network element, and the SU and the UPF network element can directly transmit data. For example, the uplink data transmission path is: terminal → DU / CU → SU → UPF → server. The downlink data transmission path is: server → UPF network element → SU → CU / DU → terminal. The user plane protocol stack between the terminal, DU / CU, SU, UPF network element, and server can be seen in Figure 6.

[0226] Uplink data transmission

[0227] The uplink data transmission path is: Terminal → DU / CU → SU → UPF → Server. Specifically, through a PDU session, the CU (via DU) receives uplink data packets from the terminal. For example, the above PDU session is established in the flow shown in Figure 5. The CU sends uplink data packets to the SU, and the SU receives the uplink data packets from the CU. The SU performs calculations / processing on the uplink data packets. The SU sends the calculated / processed uplink data packets to the UPF network element. The UPF network element forwards the received uplink data packets to the server.

[0228] In one possible implementation, the CU can determine whether to send the uplink data packet to the SU for secondary / intermediate processing based on whether the quality of service flow transmitting the uplink data packet requires secondary / intermediate processing by the access network (e.g., the SU). For example, whether the quality of service flow has a second indication. Alternatively, the CU can directly send the uplink data packet to the receiving end UPF network element. Of course, the UPF network element forwards the uplink data packet to the server upon receiving it. For example, the CU receives the uplink data packet from the terminal through the fourth quality of service flow contained in the PDU session. If the fourth quality of service flow has a second indication, the CU sends the uplink data packet to the SU, the SU calculates / processes the uplink data packet, and sends the calculated / processed uplink data packet to the UPF network element. Or, if the fourth quality of service flow does not have the second indication, the CU sends the uplink data packet to the UPF network element. Whether the fourth quality of service flow has a second indication is configured by the SMF network element for the CU (e.g., in step 570, the SMF network element configures it for the CU). Alternatively, the CU can forward the uplink data packet based on the destination address carried / included in the packet header. For example, if the destination address carried / contained by the uplink data packet is a UPF network element, then the UPF network element will send the uplink data packet to the UPF network element. Alternatively, if the destination address carried / contained by the uplink data packet is an access network (such as a SU), then the UPF network element will send the uplink data packet to the access network (such as a SU), and the SU will perform secondary / intermediate processing on the uplink data packet.

[0229] During uplink data transmission, the SU can send processed / computed uplink data packets to the UPF network element through the tunnel between the SU and the UPF network element. For example, the tunnel between the SU and the UPF network element can be a GTP-U tunnel. Before the SU sends the processed / computed uplink data packets to the UPF network element, the SU performs packet filtering / classification: for example, the SU filters / classifies the uplink data packets according to the PDR configuration, maps the uplink data packets to the corresponding Quality of Service (QoS) flow, and adds the identifier of the corresponding QoS flow (such as QFI) to the uplink data packets. In one interpretation, the tunnel between the SU and the UPF can contain at least one QoS flow, and the SU can specifically send uplink data packets to the terminal through the mapped QoS flow.

[0230] Downlink data transmission

[0231] The downlink data transmission path is: Server → UPF network element → SU → CU / DU → Terminal. For example, the server sends a downlink data packet to the UPF network element. The UPF network element forwards the downlink data packet to the SU, and the SU receives the downlink data packet from the UPF network element; the SU performs calculations / processing on the downlink data packet; the SU sends the calculated / processed downlink data packet to the CU, and the CU receives the calculated / processed downlink data packet from the SU; the CU (via DU) sends the calculated / processed downlink data packet to the terminal.

[0232] In downlink data transmission, the SU performs downlink packet filtering / classification. For example, the SU filters / classifies computationally / processed downlink packets according to the configured PDR, maps the downlink packets to the corresponding Quality of Service (QoS) stream, and adds the identifier of the corresponding QoS stream (such as QFI) to the downlink packets. The downlink packets are then sent to the terminal via the CU and DU through the corresponding QoS stream. Alternatively, the CU performs downlink packet filtering / classification. For example, the CU receives computationally / processed downlink packets from the SU. The CU filters / classifies the downlink packets according to the configured PDR, maps the downlink packets to the corresponding QoS stream, and adds the identifier of the corresponding QoS stream (such as QFI) to the downlink packets. The downlink packets are then sent to the terminal (via the DU) through the corresponding QoS stream. In one understanding, the CU and the terminal transmit data via a DRB. The DRB includes at least one QoS stream. The CU sends downlink packets to the terminal through the mapped QoS stream.

[0233] In this application, the UPF network element can filter / classify downlink data packets according to the configured PDR. For example, the UPF network element receives downlink data packets from the server. If the destination address of the downlink data packet is the access network, the downlink data packet is mapped to a QoS flow with a second indication and forwarded to the SU through a GTP-U tunnel. Alternatively, if the destination address of the downlink data packet is the terminal, the downlink data packet is mapped to a QoS flow without a second indication (or described as a transparent QoS flow) and forwarded to the SU through a GTP-U tunnel.

[0234] In this application, when the CU receives a data packet, if the CU does not support parsing the packet header, the CU cannot obtain the destination IP address of the data packet. The CU cannot determine whether to forward the data packet to the SU (if the data packet is an uplink data packet) or to the terminal (if the data packet is a downlink data packet). In one implementation, the SU adds indication information for indicating the transmission direction to the data packet during / after calculation / processing. For example, the SU adds indication information for indicating the uplink transmission direction to uplink data packets and indication information for indicating the downlink transmission direction to downlink data packets. The CU decides whether to forward the data packet to the SU or to the terminal based on the transmission direction indication information carried / contained in the data packet. For example, if the CU receives a data packet and the data packet carries / contains indication information for the uplink transmission direction (the data packet can be considered an uplink data packet), the CU forwards the data packet to the SU; or, if the data packet carries / contains indication information for the downlink transmission direction (the data packet is considered downlink data), the CU forwards the data packet to the terminal.

[0235] Through the above design, the SU and UPF network elements are directly connected, and data transmission between the SU and UPF network elements does not need to go through the CU for relay. For example, in uplink data transmission, the SU can directly send the calculated / processed uplink data packets to the UPF network element. In downlink data transmission, the UPF network element can directly send downlink data packets to the SU, etc., simplifying the data transmission path and improving data transmission efficiency.

[0236]

Example 2

[0237] The scheme in Embodiment 2 is applicable to the network architecture shown in Figure 1c or Figure 1d. In the network architecture of Figure 1c or Figure 1d, the SU interacts directly with each control plane network element on the core network side. For example, in the network architecture of Figure 1c, the SU accesses the service bus through the SBI interface and interacts directly with the control plane network elements without the need for forwarding by the AMF network element. In the network architecture of Figure 1d, the SU is connected to the AMF network element through the Ni interface, and the SU interacts with each control plane network element on the core network side through the AMF network element. In the scheme of Embodiment 2, the data plane transmission path is the same as in Embodiment 1.

[0238] Figure 7 shows a flowchart of a communication method, including:

[0239] Step 710: The AMF network element sends the first information to the SMF network element, and the SMF network element receives the first information from the AMF network element.

[0240] For example, the terminal sends first information to the AMF network element, such as the first information being carried / included in the PDU session establishment request, as described in step 810 below; when the AMF network element receives the first information, it sends / forwards the first information to the SMF network element, such as the first information being carried in the PDU session context establishment request, as described in step 830 below.

[0241] Optionally, in step 720: the SMF network element determines the PDR configuration based on the first information.

[0242] For a detailed description of steps 710 and 720, please refer to the description of steps 210 and 220 in Figure 2.

[0243] Optionally, in step 730: the SMF network element determines the SU based on the slice identifier or DNN.

[0244] For example, an SMF network element selects a suitable SU based on the slice identifier or DNN. This suitable SU may refer to the SU that provides access network / local services to the terminal.

[0245] Step 740: The SMF network element sends the configuration of the PDR corresponding to the first information to the SU or CU, and the CU or SU receives the configuration of the PDR corresponding to the first information from the SMF network element.

[0246] In one possible implementation, the SMF network element sends the PDR configuration corresponding to the first information to the SU. For example, in the network architecture of Figure 1c, the SU accesses the service bus through the SBI interface and communicates directly with the SMF network element. The SMF network element directly sends the PDR configuration corresponding to the first information to the SU. Alternatively, in the network architecture of Figure 1d, the SU is connected to the AMF network element and communicates with the SMF network element through the AMF network element. The SMF network element sends the PDR configuration corresponding to the first information to the SU through the AMF network element. The SU can map data packets to the corresponding Quality of Service (QoS) flow according to the PDR configuration corresponding to the first information. That is, the SU filters / classifies data packets according to the PDR corresponding to the first information.

[0247] In another possible implementation, the SMF network element sends the PDR configuration corresponding to the first information to the CU. For example, in the network architecture of Figure 1c / 1d, the SMF network element communicates with the CU through the AMF network element. The SMF can send the PDR configuration corresponding to the first information to the CU through the AMF network element. The CU maps data packets to the corresponding Quality of Service (QoS) flow according to the PDR configuration corresponding to the first information. That is, the CU filters / classifies data packets according to the PDR corresponding to the first information. Alternatively, the CU can send the PDR configuration corresponding to the first information to the SU, and the SU performs data packet classification / filtering without restriction.

[0248] During the establishment of a PDU session, the method provided in Figure 7 is applied, specifically referring to the process in Figure 8 of Example 1 and the process in Figure 9 of Example 2 below.

[0249] Example 1, as shown in Figure 8, provides a flow chart for a communication method applicable to the network architecture of Figure 1c or Figure 1d, where the SU is connected / communicates with the UPF network element through the CU, including:

[0250] Step 810: The terminal sends a PDU session establishment request to the AMF network element, and the AMF network element receives the PDU session establishment request from the terminal.

[0251] For example, the PDU session establishment request may include first information, such as a slice identifier, DNN, or first indication. Alternatively, the PDU session establishment request may include a slice identifier, DNN, etc. The AMF network element can determine the first indication based on the slice identifier or DNN. The first information described in this process can be understood as a slice identifier, DNN, or first information, etc., without restriction.

[0252] Optionally, in step 820: the AMF network element performs access control based on the terminal's location information and the first information.

[0253] Step 830: The AMF network element sends a PDU session context establishment request to the SMF network element, and the SMF network element receives the PDU session context establishment request from the AMF network element.

[0254] For example, the PDU session context establishment request contains the first information.

[0255] Step 840: The SMF network element determines the PDR configuration based on the first information; and the SMF network element determines the SU based on the slice identifier or DNN.

[0256] Step 850: The SMF network element sends the PDR configuration to the UPF network element, and the UPF network element receives the PDR configuration from the SMF network element.

[0257] For the specific process of steps 810 to 850, refer to the description of steps 310 to 350 in the flowchart of Figure 3.

[0258] Step 860a: The SMF network element sends a session establishment request to the SU through the AMF network element, and the SU receives the session establishment request from the SMF network element through the AMF network element.

[0259] The English name for a session establishment request is (Session Establishment Request). Optionally, the session establishment request includes the PDR corresponding to the first information. Through step 860a, the SMF network element configures the PDR corresponding to the first information to the SU, and the SU can perform packet filtering / classification.

[0260] Step 860b: The SU sends a session establishment response to the SMF network element through the AMF network element, and the SMF network element receives the session establishment response from the SU through the AMF network element.

[0261] The English name for the session establishment response is (Session Establishment Response). The session establishment response includes the address information of the SU related to the first tunnel, such as the SU's TNL information, and more specifically, the SU's F-TEID. In the flowchart of Figure 8, the SU's address information is described as: Address Information [SU]. The SU's address information related to the first tunnel is used to establish the first tunnel between the CU and the SU.

[0262] Step 870a: The SMF network element sends a session resource establishment request to the CU through the AMF network element, and the CU receives the session resource establishment request from the SMF network element through the AMF network element.

[0263] The English name for a Session Resource Setup Request is (SERAP). The SERAP includes a Quality of Service (QoS) flow list and the address information of the Unit (SU) associated with the first tunnel. The QoS flow list can be considered as the list of QoS flows to be established, and one or more QoS flows included in the QoS flow list have a second indication. The address information of the SU associated with the first tunnel is used to establish the first tunnel between the SU and the CU. Through step 870a, the SMF network element notifies the CU of the address information of the SU associated with the first tunnel. Through step 870b below, the SMF network element receives the address information of the CU associated with the first tunnel from the CU and notifies the SU of the address information of the CU associated with the first tunnel, thereby successfully / completely establishing the first tunnel between the CU and the SU. Optionally, the SERAP also includes the configuration of the PDR corresponding to the first information. The CU can filter / classify data packets according to the configuration of the PDR corresponding to the first information.

[0264] Step 870b: The CU sends a session resource establishment response to the SMF network element through the AMF network element, and the SMF network element receives the session resource establishment response from the CU through the AMF network element.

[0265] For example, the English name for the Session Resource Setup Response is (Session Resource Setup Response). The Session Resource Setup Response contains the address information of the CU associated with the first tunnel, such as the CU's TNL information. In the flowchart of Figure 8, the address information of the CU associated with the first tunnel is described as address information [CU]. The address information of the CU associated with the first tunnel is used to establish the first tunnel between the CU and the SU. The SMF network element sends the address information of the CU associated with the first tunnel to the SU (this process is not shown in the flowchart of Figure 8).

[0266] Step 880: Establish a session for local services between the terminal / CU / SU.

[0267] It is understandable that the process shown in Figure 8 is mainly for illustrating the network architecture shown in Figure 1d. In the network architecture shown in Figure 1d, the SU communicates with the SMF network element through the AMF network element. In the network architecture shown in Figure 1c, the SU can communicate directly with the SMF network element, and the communication between the two does not need to be forwarded through the AMF network element.

[0268] In this application, the SU / CU maps the data packets calculated / processed by the SU to the corresponding Quality of Service (QoS) stream according to the PDR configured in the SMF network element. The data transmission process is the same as in Example 1 of Embodiment 1. For example, the transmission path for uplink data is: Terminal → DU / CU → SU → CU → UPF → Server. The transmission path for downlink data is: Server → UPF → CU → SU → CU / DU → Terminal. The user plane protocol stack between the terminal, DU / CU, SU, UPF network elements, and server can be seen in Figure 4. During data transmission, the processing of data packets by the CU / SU, etc., can be referred to the description in Example 1 of Embodiment 1, and will not be repeated here.

[0269] Through the above design, the SU interacts directly with the SMF network element on the core network side. The SMF network element can directly configure the corresponding PDR for the SU without the need for CU forwarding, thus ensuring the service quality flow requirements of different types of data and guaranteeing the user's service experience.

[0270] Example 2, in the network architecture of Figure 1c or 1d. In addition to being connected to the CU, the SU is also directly connected to the UPF network element. Uplink and downlink data transmission between the SU and the UPF network element does not go through the CU for relay; the SU directly transmits uplink and downlink data with the UPF network element. For example, the transmission path for uplink data is: Terminal → DU / CU → SU → UPF → Server. The transmission path for downlink data is: Server → UPF → SU → CU / DU → Terminal. The user plane protocol stack between the terminal, DU / CU, SU, UPF network element, and server can be seen in Figure 6.

[0271] The SU establishes two tunnels: one for connecting to the CU and the other for connecting to the UPF. The UPF network element establishes two tunnels: one for connecting to the CU and the other for connecting to the SU. In the description of this application, the tunnel between the CU and SU is referred to as the first tunnel, the tunnel between the UPF network element and the CU as the second tunnel, and the tunnel between the CU and SU as the third tunnel.

[0272] The SMF network element can instruct / request the UPF network element to establish at least two tunnels. The specific process can be referred to Example 2 in Embodiment 1. Unlike Embodiment 1, the SMF network element can send the address information of the UPF network element related to the third tunnel to the SU, without the need for CU relay. The SMF network element instructs / requests the SU to establish at least two tunnels. For example, the SMF network element sends third information to the SU, and the SU receives the third information from the SMF network element. The third information is used to instruct / request the SU to establish at least two tunnels, which include a third tunnel and a first tunnel. The third tunnel is the tunnel between the UPF network element and the SU, and the first tunnel is the tunnel between the CU and the SU. For example, the third information can be an instruction message used to instruct the SU to establish at least two tunnels, or a multiple tunnels request message used to request the SU to establish at least two tunnels. The SU sends the address information of the SU related to the third tunnel and the address information of the SU related to the first tunnel to the SMF network element, and the SMF network element receives the address information of the SU related to the third tunnel and the address information of the SU related to the first tunnel from the SU. The SMF network element sends the address information of the SU related to the third tunnel to the UPF network element, and the UPF network element receives the address information of the SU related to the third tunnel from the SMF network element. The SMF network element sends the address information of the SU related to the first tunnel to the CU, and the CU receives the address information of the SU related to the first tunnel from the SMF network element. Optionally, the SMF network element sends the identifier of the service quality flow related to the third tunnel and the identifier of the service quality flow related to the first tunnel to the SU; the SU receives the identifier of the service quality flow related to the third tunnel and the identifier of the service quality flow related to the first tunnel from the SMF network element.

[0273] Based on the network architecture shown in Figure 1d, and as illustrated in Figure 9, a communication method flow is provided. This flow is applicable to the case where the SU and UPF network elements are directly connected / communicate in the network architecture shown in Figure 1d, including:

[0274] Step 910: The terminal sends a PDU session establishment request to the AMF network element, and the AMF network element receives the PDU session establishment request from the terminal.

[0275] Optionally, in step 920: the AMF network element performs access control based on the terminal's location information and the first information.

[0276] Step 930: The AMF network element sends a PDU session context establishment request to the SMF network element, and the SMF network element receives the PDU session context establishment request from the AMF network element.

[0277] Step 940: The SMF network element determines the PDR configuration based on the first information; and the SMF network element determines the SU based on the slice identifier or DNN.

[0278] For the specific process of steps 910 to 940, refer to the description of steps 310 to 340 in the flowchart of Figure 3.

[0279] Step 950: The SMF network element sends an N4 session establishment request to the UPF network element, and the UPF network element receives the N4 session establishment request from the SMF network element.

[0280] The English name for an N4 session establishment request is (N4 Session Establishment Req). The N4 session establishment request includes PDR configuration and secondary information, such as multi-tunnel request information. Optionally, the N4 session establishment request also includes the QFI associated with each tunnel to be established, such as the QFI associated with the second tunnel and the QFI associated with the third tunnel, etc.

[0281] Step 960: The UPF network element sends an N4 session establishment response to the SMF network element, and the SMF network element receives the N4 session establishment response from the UPF network element.

[0282] The English name for an N4 session establishment response is (N4 Session Establishment Resp). The N4 session establishment response contains the address information of the UPF network element corresponding to / associated with each tunnel requested by the SMF network element. For example, the address information of the UPF network element associated with the second tunnel and the address information of the UPF network element associated with the third tunnel. In the description of this application, the address information can be TNL information, such as FTEID.

[0283] Step 970: The SMF network element sends a Ni session establishment request to the SU through the AMF network element, and the SU receives the Ni session establishment request from the SMF network element through the AMF network element.

[0284] In the network architecture shown in Figure 1d, the interface between the SU and AMF network elements is the Si interface. The SU and SMF network elements communicate through the AMF network element.

[0285] The English name for a Ni session establishment request is (Ni Session Establishment Req). This request includes third-party information, such as a multi-tunneling request. Optionally, the Ni session establishment request may also include the PDR configuration corresponding to the first-party information. In this case, it can be understood that the SMF network element configures the PDR corresponding to the first-party information to the SU. The SU then maps data packets to the corresponding Quality of Service (QoS) flow based on the PDR configuration.

[0286] Step 980: The SU sends a Ni session establishment response to the SMF network element through the AMF network element, and the SMF network element receives the Ni session establishment response from the SU through the AMF network element.

[0287] For example, the English name of the Ni session establishment response is (Ni Session Establishment Resp). The Ni session establishment response contains the address information of each tunnel requested by the SMF network element to be established, such as the address information of the SU related to the first tunnel and the address information of the SU related to the third tunnel.

[0288] Step 990: The SMF network element sends a PDU session resource establishment request to the CU through the AMF network element, and the CU receives the PDU session resource establishment request from the SMF network element through the AMF network element.

[0289] For example, the Chinese name of a PDU session resource setup request is (PDU Session Resource Setup Request). The PDU session resource setup request contains a list of service quality flows to be established. This list contains one or more service quality flow identifiers (such as QFI). One or more service quality flow identifiers in this service quality flow list have a second indicator, which can also be described as a QFI-based intermediate processing indicator, or simply an intermediate indicator. Furthermore, the PDU session resource setup request also contains the address information of the UPF network element and the SU. For example, if the identifier of one service quality flow in the service quality flow list has the address information of a corresponding SU related to a third tunnel, it can be understood that the data transmitted by this service quality flow requires intermediate / secondary processing by the access network (such as the SU). Or, if the identifier of another service quality flow in the service quality flow list has the address information of a corresponding UPF network element related to a second tunnel, it can be understood that the data transmitted by this service quality flow is transparently transmitted by the access network.

[0290] Optionally, the PUD session resource establishment request also includes the PDR configuration corresponding to the first information. This can be understood as follows: the SMF network element configures the PDR corresponding to the first information to the CU. The CU maps the data packets to the corresponding quality of service flow according to the PDR corresponding to the first information.

[0291] Step 9010: The CU sends a PDU session resource establishment response to the SMF network element through the AMF network element, and the SMF network element receives the PDU session resource establishment response from the CU through the AMF network element.

[0292] The English name for the PDU session resource setup response is (PDU Session Resource Setup Response). The PDU session resource setup response contains the address information of the CU related to the second tunnel and the address information of the CU related to the first tunnel. Optionally, the address information of the CU related to the second tunnel may have a corresponding identifier to identify that this address information is the address information of the tunnel that needs to access the network for intermediate / secondary data processing. The SMF network element sends the address information of the CU related to the first tunnel to the SU via the AMF network element, as described in step 9012. The SMF sends the address information of the CU related to the second tunnel and the address information of the SU related to the third tunnel together to the UPF network element, as described in step 9011.

[0293] Step 9011: During the N4 session modification process, the SMF network element sends the address information of the CU related to the second tunnel and the address information of the SU related to the third tunnel to the UPF network element. The UPF network element receives the address information of the CU related to the second tunnel and the address information of the SU related to the third tunnel from the SMF network element.

[0294] For example, the Chinese name for N4 session modification is (N4 session modification). Optionally, the address information of the SU related to the third tunnel may have an identifier to identify that the address information is the address information of the tunnel that needs to transmit data that requires intermediate / secondary processing by the access network.

[0295] Step 9012: During the Ni session modification process, the SMF network element sends the address information of the CU related to the first tunnel to the SU through the AMF network element, and the SU receives the address information of the CU related to the first tunnel from the SMF network element through the AMF network element.

[0296] For example, the English name for Ni session modification is (Ni session modification).

[0297] Through the above interaction, the SMF network element can configure the corresponding PDR for the SU or CU. The SU or CU can then map the data packets calculated / processed by the access network (e.g., the SU) to the corresponding Quality of Service (QoS) flow according to the configured PDR, meeting the QoS flow requirements of different types of data packets and improving the user's service experience. Furthermore, in this application, the SU obtains the address information of the UPF related to the third tunnel, and the UPF network element obtains the address information of the SU related to the third tunnel. The SU and UPF successfully establish / complete the establishment of the third tunnel. The CU obtains the address information of the UPF network element related to the second tunnel, and the UPF network element obtains the address information of the CU related to the second tunnel. The CU and UPF network element successfully establish / complete the establishment of the second tunnel. The UPF network element connects to the SU through the third tunnel, and the UPF network element connects to the CU through the second tunnel. In uplink data transmission, the CU sends uplink data packets requiring intermediate / secondary processing by the access network to the SU, and sends uplink data packets requiring no intermediate / secondary processing directly to the UPF network element. In downlink data transmission, the UPF network element sends downlink data packets requiring intermediate / secondary processing by the access network directly to the SU through the third tunnel, without requiring forwarding by the CU. The UPF network element sends downlink data packets that do not require intermediate / secondary processing in the access network to the CU through the second tunnel. The SU and the UPF network element communicate directly through the third tunnel, eliminating the need for CU forwarding and improving data transmission efficiency. Furthermore, in this application, the CU obtains the SU's address information related to the first tunnel, and the SU obtains the CU's address information related to the first tunnel; the first tunnel is successfully established between the SU and the CU.

[0298] In this application, the process of Figure 9 can be applied to the network architecture of Figure 1c, and is applicable to the case where the SU and UPF network elements are directly connected / communicate in the network architecture of Figure 1c. In the network architecture of Figure 1c, the SU accesses the service bus through the SBI interface, and the SU can directly communicate with the control plane network elements on the core network side. Step 970 above can be replaced by: the SMF network element directly sends a Ni session establishment request to the SU, and the SU directly receives a Si session establishment request from the SMF network element. Step 980 above can be replaced by: the SU directly sends a Ni session establishment response to the SMF network element, and the SMF network element directly receives a Ni session establishment response from the SU. Of course, there are no restrictions on the names of the Si session establishment request and the Si session establishment response, and they can be replaced with other names. Step 9012 above can be replaced by: the SMF network element directly sends the address information of the CU related to the first tunnel to the SU.

[0299] In this application, the CU or SU can map the data packets calculated / processed by the access network (such as the SU) to the corresponding quality of service flow according to the PDR configured in the SMF network element. The data transmission process is the same as in Example 2 of Embodiment 1. For example, the transmission path for uplink data is: terminal → DU / CU → SU → UPF → server. The transmission path for downlink data is: server → UPF → SU → CU / DU → terminal. During data transmission, the processing of data packets by the CU or SU can be referred to the description in Example 1 of Embodiment 1, and will not be repeated here.

[0300]

Example 3

[0301] This application also provides a communication method, comprising: an SMF network element requesting a UPF network element to establish at least two tunnels, wherein the at least two tunnels include a second tunnel connecting the UPF network element to the CU and a third tunnel connecting the UPF network element to the SU. The UPF network element communicates directly with the SU through the third tunnel, without the need for CU forwarding, thereby improving data transmission efficiency.

[0302] Figure 10 shows a flowchart of a communication method, including:

[0303] Step 1010: The SMF network element sends the second information to the UPF network element, and the UPF network element receives the second information from the SMF network element.

[0304] The second information is used to request / instruct the UPF network element to establish at least two tunnels, the at least two tunnels including a second tunnel and a third tunnel, the second tunnel being the tunnel between the UPF network element and the CU, and the third tunnel being the tunnel between the UPF network element and the SU.

[0305] Optionally, the SMF network element can also send the identifier of the second tunnel-related Quality of Service (QoS) flow (e.g., QFI) and the identifier of the third tunnel-related QoS flow (e.g., QFI) to the UPF network element. Correspondingly, the UPF network element receives the identifiers of the second tunnel-related QoS flow and the third tunnel-related QoS flow from the SMF network element. The second information, the identifiers of the second tunnel-related QoS flow and the third tunnel-related QoS flow can be carried / included in one message or in different messages.

[0306] Step 1020: The UPF network element sends the address information of the UPF network element related to the second tunnel and the address information of the UPF network element related to the third tunnel to the SMF network element. The SMF network element receives the address information of the UPF network element related to the second tunnel and the address information of the UPF network element related to the third tunnel from the UPF network element.

[0307] In one possible implementation, the process in Figure 10 can be applied to the network architecture of Figure 1a or Figure 1b. In the network architecture of Figure 1a or Figure 1b, the SU interacts with the SMF network element through the CU. The SMF network element can send the address information of the UPF network element related to the second tunnel and the address information of the UPF network element related to the third tunnel to the CU, and the CU sends the address information of the UPF network element related to the third tunnel to the SU. Further, the SU can send the address information of the SU related to the third tunnel to the CU. The CU sends the address information of the CU related to the second tunnel and the address information of the SU related to the third tunnel to the SMF network element. The SMF network element sends the address information of the CU related to the second tunnel and the address information of the SU related to the third tunnel to the UPF network element. For the specific implementation process, please refer to the process descriptions of Examples 1 and 2 in Embodiment 1.

[0308] Alternatively, the process in Figure 10 can be applied to the network architecture of Figure 1c or Figure 1d. In the network architecture of Figure 1c or Figure 1d, the SU interacts directly (or through the AMF network element) with the SMF network element. The SMF network element can send the address information of the UPF network element related to the third tunnel directly (or through the AMF network element) to the SU, and send the address information of the UPF network element related to the second tunnel directly (or through the AMF network element) to the CU. Further, the SU sends the address information of the SU related to the third tunnel to the SMF network element. The CU sends the address information of the CU related to the second tunnel to the SMF network element. The SMF network element sends the address information of the SU related to the third tunnel and the address information of the CU related to the second tunnel to the UPF network element. For the specific implementation process, please refer to the process descriptions of Examples 1 and 2 in Embodiment 2.

[0309] The solutions described in Embodiments 1 to 3 of this application can be applied to ORAN architecture. For example, as shown in Figure 11, an ORAN architecture is provided: the access network includes a RAN Intelligent Controller (RIC), a CU, and a DU, etc. The CU and DU are described above. The RIC can be a near-real-time (NRT) RIC or a non-real-time (Non-real-time) RIC. The interface between the RIC and the CU is E2, and the RIC communicates with the core network control plane elements through the CU. The CU is connected to the AMF network elements through the N2 interface.

[0310] The network architecture shown in Figure 11 is similar to that shown in Figure 1a. The main difference is that SU is replaced with RIC. The interface between RIC and CU is E2. Therefore, the scheme or process described in Embodiment 1 can be applied to the ORAN architecture shown in Figure 11. Specifically, simply replace the SU-related descriptions in Embodiment 1 with RIC.

[0311] In the embodiments provided above, the methods provided by the embodiments of this application are described from the perspective of the interaction between SMF, CU, and SU. To implement the functions in the methods provided by the embodiments of this application, SMF, CU, or DU may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is implemented in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the design constraints of the specific application of the technical solution.

[0312] Based on the same conceptual framework as the above-described method embodiments, Figures 12 and 13 are schematic diagrams of possible communication devices provided in the embodiments of this application. These communication devices can implement the functions of the session management function network element, centralized unit, or service unit in the above-described method embodiments, and therefore may achieve the beneficial effects of the above-described method embodiments. In the embodiments of this application, the communication device may be a session management function network element, a centralized unit, or a service unit, or a unit, module, or component (such as a chip, chip system, circuit, processor, or others) applied in the session management function network element, centralized unit, or service unit. In the following description, the term "unit" will be used as an example. For example, in the following description, the communication device includes a processing unit and a transceiver unit as an example. The processing unit in the following description can also be replaced by: processing module or processing component, etc. The transceiver unit can also be replaced by: transceiver unit or transceiver component. For example, the transceiver component may refer to a communication module.

[0313] As shown in Figure 12, the communication device 1200 includes a processing unit 1210 and a transceiver unit 1220. The communication device 1200 is used to implement the functions of the first terminal device or the first network device in Figure 4.

[0314] Optionally, the transceiver unit 1220 may also be referred to as an output unit, an interface unit, or a communication unit, etc. In one possible implementation, the transceiver unit 1220 includes at least one of a transmitting unit or a receiving unit. The transmitting unit and the receiving unit may be integrated together, or they may be two independent units, etc.

[0315] When the communication device 1200 is used to implement the functions of the SMF network elements in Figures 2, 3, 5, 7, 8, or 9, specifically: the transceiver unit 1220 is used to receive first information, which is used to instruct the access network to calculate / process data packets participating in the current Protocol Data Unit (PDU) session; the transceiver unit 1220 is also used to send the configuration of the Packet Detection Rule (PDR) corresponding to the first information, which is used to map the data packets calculated / processed by the access network to a first Quality of Service (QoS) flow, which is included in the PDU session. Optionally, the processing unit 1210 is used to determine the PDR configuration based on the first information.

[0316] When the communication device 1200 is used to implement the functions of the CU or DU in Figures 2, 3, 5, 7, 8, or 9, specifically: the transceiver unit 1220 is used to receive the configuration of the Packet Detection Rule (PDR) corresponding to the first information. The first information is used to instruct the access network to calculate / process the packets of the current Protocol Data Unit (PDU) session. The PDR is used to map the packets calculated / processed by the access network to a first Quality of Service (QoS) stream, which is included in the PDU session. Optionally, the processing unit 1210 is used to map the packets calculated / processed by the access network to the first QoS stream according to the PDR.

[0317] When the communication device is used to implement the functions of the SMF network element in Figure 10, Figure 5, or Figure 9, specifically: the transceiver unit 1220 is used to send second information to the user plane function network element. The second information is used to request / instruct the user plane function network element to establish at least two tunnels. The at least two tunnels include a second tunnel and a third tunnel. The second tunnel is the tunnel between the user plane function network element and the centralization unit, and the third tunnel is the tunnel between the user plane function network element and the service unit. The transceiver unit receives address information of the user plane function network element related to the second tunnel and address information of the user plane function network element related to the third tunnel from the user plane function network element.

[0318] When the communication device implements the functions of the UPF network element in Figure 10, Figure 5, or Figure 9, specifically: the transceiver unit 1220 is used to receive second information from the session management function network element. The second information is used to request / instruct the user plane function network element to establish at least two tunnels. The at least two tunnels include a second tunnel and a third tunnel. The second tunnel is the tunnel between the user plane function network element and the centralization unit, and the third tunnel is the tunnel between the user plane function network element and the service unit. The transceiver unit sends the address information of the user plane function network element related to the second tunnel and the address information of the user plane function network element related to the third tunnel to the session management function network element.

[0319] When the communication device implements the function of the SU corresponding to Figure 10, Figure 5, or Figure 9, specifically: the transceiver unit 1220 is used to receive third information from the session management function, the third information being used to instruct / request the service unit to establish at least two tunnels, the at least two tunnels including a third tunnel and a first tunnel, the third tunnel being a tunnel between the user plane function network element and the service unit, and the first tunnel being a tunnel between the centralization unit and the service unit; and sends the address information of the service unit associated with the third tunnel and the address information of the service unit associated with the first tunnel to the session management function network element.

[0320] For details on the implementation of the transceiver unit 1220 and the processing unit 1210, please refer to the description of the method embodiments above.

[0321] It is understood that the division of units in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. In addition, the functional units in this application embodiment can be integrated into a physical device (e.g., in a processor), or each functional unit can be a separate physical device, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional module, etc.

[0322] As shown in Figure 13, the communication device 1300 includes a processor 1310 and an interface circuit 1320. The processor 1310 and the interface circuit 1320 are coupled to each other. It is understood that the interface circuit 1320 can be a transceiver or an input / output interface. Optionally, the communication device 1300 may also include a memory 1330 for storing instructions executed by the processor 1310, or storing input data required by the processor 1310 to execute instructions, or storing data generated after the processor 1310 executes instructions.

[0323] When the communication device 1300 is used to implement the method shown in Figures 2, 3, 5, 7, 8, 9 or 10, the processor 1310 is used to implement the function of the processing unit 1210, and the interface circuit 1320 is used to implement the function of the transceiver unit 1220.

[0324] When the aforementioned communication device is a chip applied to a session management function network element (such as an SMF network element), the chip implements the functions of the SMF network element in the above method embodiments. The chip receives information (such as first information) through other modules (such as radio frequency modules or antennas) in the SMF network element. Alternatively, the chip sends information (such as PDR configuration) to other modules (such as radio frequency modules or antennas) in the SMF network element, which is information sent by the SMF network element to the CU or DU.

[0325] When the aforementioned communication device is a chip applied to a centralized unit (such as a CU) or a distributed unit (such as a DU), the chip implements the functions of the CU or DU in the above method embodiments. For example, the chip receives information (such as PDR configuration) from other modules (such as radio frequency modules or antennas) in the DU or CU, which is sent to the CU or DU by the SMF network element. Alternatively, the module sends information to other modules (such as radio frequency modules or antennas) in the CU or DU, which is sent to the SMF network element by the CU or DU. Optionally, the CU or DU here can be a CU or DU under an O-RAN architecture.

[0326] This application embodiment also provides a communication device, which includes a processor for implementing the functions of the SMF network element, CU, DU, or UPF network element in Figures 2, 3, 4, 7, 8, 9, or 10. Optionally, the communication device further includes a memory, with the processor coupled to the memory. The processor executes computer programs or instructions stored in the memory to implement the functions of the SMF network element, CU, DU, or UPF network element in Figures 2, 3, 4, 7, 8, 9, or 10. Optionally, the communication device may be a chip or a chip system.

[0327] This application embodiment also provides a communication device, including a processor and an interface circuit. The interface circuit is used to receive signals from other devices outside the device and transmit them to the processor, or to send signals from the processor to other devices outside the device. The processor is used to implement the functions of the SMF network element, CU, DU, or UPF network element in Figures 2, 3, 4, 7, 8, 9, or 10 through logic circuits or execution code instructions.

[0328] This application also provides a computer-readable storage medium storing instructions, which may also be referred to as computer programs, computer program code, etc. These instructions, when executed on a computer, cause the computer to perform the functions of the SMF network element, CU, DU, or UPF network element shown in Figures 2, 3, 4, 7, 8, 9, or 10.

[0329] This application also provides a computer program product, including a computer program or instructions, which, when run on a computer, implement the functions of the SMF network element, CU, DU, or UPF network element in Figures 2, 3, 4, 7, 8, 9, or 10.

[0330] It is understood that the processor in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor.

[0331] The memory in the embodiments of this application may be random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), register, hard disk, portable hard disk, CD-ROM, or any other form of storage medium known in the art.

[0332] The method steps in the embodiments of this application can be implemented in hardware or in software instructions executable by a processor. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium well known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. The storage medium can also be a component of the processor. The processor and the storage medium can reside in an ASIC.

[0333] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. This computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center integrating one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0334] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

Claims

1. A communication method, characterized in that, The method is applied to the session management function network element, including: Receive first information, which is used to instruct the access network to calculate / process data packets participating in the current Protocol Data Unit (PDU) session; The configuration of the Packet Detection Rule (PDR) corresponding to the first information is sent. The PDR is used to map the data packets calculated / processed by the access network to a first Quality of Service (QoS) flow, which is included in the PDU session.

2. The method as described in claim 1, characterized in that, The first information includes a first indication, a slice identifier, or a data network name. The first indication is used to indicate the calculation / processing of data packets in which the access network participates in the PDU session.

3. The method as described in claim 1 or 2, characterized in that, Also includes: Send the service quality flow list corresponding to the PDU session. The service quality flow list contains one or more service quality flows with a second indication. The second indication is used to instruct the central unit to send the data packet to the service unit when the service quality flow receives the data packet.

4. The method according to any one of claims 1 to 3, characterized in that, Also includes: Based on the first information, the configuration of the PDR is determined.

5. The method as described in claim 4, characterized in that, Determining the configuration of the PDR based on the first information includes: The configuration of the PDR is determined based on the address information of the central unit or service unit and the first information.

6. The method according to any one of claims 1 to 5, characterized in that, Receiving the first information includes: receiving the first information from the central unit or the access and mobility management function network element; sending the configuration of the PDR corresponding to the first information includes: sending the configuration of the PDR corresponding to the first information to the central unit.

7. The method according to any one of claims 1 to 5, characterized in that, Receiving the first information includes: receiving the first information from the access and mobility management function network element; sending the configuration of the PDR corresponding to the first information includes: sending the configuration of the PDR corresponding to the first information to the service unit or the central unit.

8. The method as described in claim 7, characterized in that, Also includes: The service unit is determined based on the slice identifier or data network name.

9. The method as described in claim 7 or 8, characterized in that, Also includes: Receive address information of the service unit related to the first tunnel from the service unit, wherein the first tunnel is the tunnel between the service unit and the central unit.

10. The method as described in claim 9, characterized in that, Also includes: The address information of the service unit related to the first tunnel is sent to the centralized unit.

11. The method according to any one of claims 1 to 10, characterized in that, Also includes: Send a second message to the user plane function network element. The second message is used to instruct / request the user plane function network element to establish at least two tunnels. The at least two tunnels include a second tunnel and a third tunnel. The second tunnel is the tunnel between the user plane function network element and the central unit, and the third tunnel is the tunnel between the user plane function network element and the service unit.

12. The method as described in claim 11, characterized in that, Also includes: Send the identifier of the quality of service flow associated with the second tunnel and the identifier of the quality of service flow associated with the third tunnel to the user plane function network element.

13. The method as described in claim 11 or 12, characterized in that, Also includes: Receive the address information of the user plane function network element related to the second tunnel and the address information of the user plane function network element related to the third tunnel from the user plane function network element.

14. The method as described in claim 13, characterized in that, Also includes: Send the address information of the user plane function network element related to the second tunnel and the address information of the user plane function network element related to the third tunnel to the central unit; or, The address information of the user plane function network element related to the second tunnel is sent to the central unit, and the address information of the user plane function network element related to the third tunnel is sent to the service unit.

15. The method according to any one of claims 1 to 14, characterized in that, Also includes: A third message is sent to the service unit, the third message being used to instruct / request the service unit to establish at least two tunnels, the at least two tunnels including a third tunnel and a first tunnel, the third tunnel being the tunnel between the user plane function network element and the service unit, and the first tunnel being the tunnel between the central unit and the service unit.

16. The method as described in claim 15, characterized in that, Also includes: Send the identifier of the quality flow associated with the third tunnel and the identifier of the quality flow associated with the first tunnel to the service unit.

17. The method as described in claim 15 or 16, characterized in that, Also includes: Receive the address information of the service unit related to the third tunnel and the address information of the service unit related to the first tunnel from the service unit.

18. The method as described in claim 17, characterized in that, Also includes: Send the address information of the service unit related to the third tunnel to the user plane function network element; The address information of the service unit related to the first tunnel is sent to the centralized unit.

19. A communication method, characterized in that, include: The configuration of the Packet Detection Rule (PDR) corresponding to the first information is received. The first information is used to instruct the access network to calculate / process the packets of the current Protocol Data Unit (PDU) session. The PDR is used to map the packets calculated / processed by the access network to a first Quality of Service (QoS) flow, which is included in the PDU session.

20. The method as described in claim 19, characterized in that, Also includes: According to the PDR, the data packets calculated / processed by the access network are mapped to the first quality of service flow.

21. The method as described in claim 19 or 20, characterized in that, Also includes: Send the first message.

22. The method according to any one of claims 19 to 21, characterized in that, The first information includes a first indication, a slice identifier, or a data network name. The first indication is used to indicate the calculation / processing of data packets in which the access network participates in the PDU session.

23. The method according to any one of claims 19 to 22, characterized in that, The method is applied to a centralized unit and further includes: The system receives a service quality flow list corresponding to the PDU session from the session management function network element. The service quality flow list contains one or more service quality flows with a second indication. The second indication is used to instruct the central unit to send the data packet to the service unit when the service quality flow receives the data packet.

24. The method according to any one of claims 19 to 23, characterized in that, The method is applied to a centralized unit, and receiving the configuration of the PDR corresponding to the first information includes: receiving the configuration of the PDR corresponding to the first information from the session management function network element.

25. The method as described in claim 24, characterized in that, Also includes: Send the configuration of the PDR to the service unit.

26. The method as described in claim 24 or 25, characterized in that, Also includes: The system receives address information of the user plane function network element related to the second tunnel and the address information of the user plane function network element related to the third tunnel from the session management function network element. The second tunnel is the tunnel between the user plane function network element and the central unit, and the third tunnel is the tunnel between the user plane function network element and the service unit.

27. The method as described in claim 26, characterized in that, Also includes: Send the address information of the user plane function network element related to the third tunnel to the service unit.

28. The method as described in claim 26 or 27, characterized in that, Also includes: Receive the address information of the service unit related to the third tunnel from the service unit.

29. The method as described in claim 28, characterized in that, Also includes: Send the address information of the service unit related to the third tunnel to the session management function network element.

30. The method according to any one of claims 19 to 23, characterized in that, The method is applied to a centralized unit or a service unit, and receiving the configuration of the PDR corresponding to the first information includes: receiving the configuration of the PDR corresponding to the first information from a session management function network element.

31. The method as described in claim 30, characterized in that, The method is applied to the service unit and further includes: The address information of the service unit related to the first tunnel is sent to the session management function network element. The first tunnel is the tunnel between the service unit and the central unit.

32. The method as described in claim 30, characterized in that, The method is applied to the service unit and further includes: The system receives third information from the session management function network element. The third information is used to instruct / request the service unit to establish at least two tunnels. The at least two tunnels include a third tunnel and a first tunnel. The third tunnel is the tunnel between the user plane function network element and the service unit, and the first tunnel is the tunnel between the centralization unit and the service unit.

33. The method as described in claim 32, characterized in that, Also includes: Receive the identifier of the quality of service flow related to the third tunnel and the identifier of the quality of service flow related to the first tunnel from the session management function network element.

34. The method as described in claim 32 or 33, characterized in that, Also includes: The address information of the service unit related to the third tunnel and the address information of the service unit related to the first tunnel are sent to the session management function network element.

35. The method according to any one of claims 19 to 34, characterized in that, The method is applied to a centralized unit and further includes: Through the PDU session, uplink data packets are received from the terminal; Send the uplink data packet to the service unit; Receive the calculated / processed uplink data packets from the service unit; The calculated / processed uplink data packet is sent to the user plane function network element.

36. The method as described in claim 35, characterized in that, Receiving uplink data packets from the terminal through the PDU session includes: receiving uplink data packets from the terminal through a second quality of service flow included in the PDU session; if the second quality of service flow contains the second indication, then the step of sending the uplink data packets to the service element is performed; the method further includes: if the second quality of service flow does not contain the second indication, then the uplink data packets are sent to the user plane function network element.

37. The method according to any one of claims 19 to 34, characterized in that, The method is applied to a centralized unit and further includes: Through the PDU session, downlink data packets are received from user plane function network elements; Send the downlink data packet to the service unit; Receive downlink data packets after calculation / processing from the service unit; The calculated / processed downlink data packet is sent to the terminal.

38. The method as described in claim 37, characterized in that, Receiving downlink data packets from the user plane function network element through the PDU session includes: receiving downlink data packets from the user plane function network element through a third quality of service flow included in the PDU session; if the third quality of service flow has the second indication, then the step of sending the downlink data packets to the service unit is performed; the method further includes: if the third quality of service flow does not have the second indication, then the downlink data packets are sent to the terminal.

39. The method according to any one of claims 19 to 34, characterized in that, The method is applied to a service unit and further includes: Receive uplink data packets from the central unit; Calculate / process the uplink data packets; The calculated / processed uplink data packet is sent to the centralized unit.

40. The method according to any one of claims 19 to 34, characterized in that, The method is applied to a service unit and further includes: Receive downlink data packets from the central unit; The downlink data packets are calculated / processed. The downlink data packet for computation / processing is sent to the centralized unit.

41. The method according to any one of claims 19 to 34, characterized in that, The method is applied to a centralized unit and further includes: Receive uplink data packets from the terminal; The uplink data packet is sent to the service unit.

42. The method as described in claim 41, characterized in that, The method of receiving uplink data packets from a terminal includes: receiving uplink data packets from the terminal via a fourth quality of service flow; if the fourth quality of service flow has the second indication, performing the step of sending the uplink data packets to the service element; the method further includes: if the fourth quality of service flow does not have the second indication, sending the uplink data packets to the user plane function network element.

43. The method according to any one of claims 19 to 34, characterized in that, The method is applied to a centralized unit and further includes: Receive downlink data packets after processing / computation from the service unit; The calculated / processed downlink data packet is sent to the terminal.

44. The method according to any one of claims 19 to 34, characterized in that, The method is applied to a service unit and further includes: Receive uplink data packets from the central unit; The uplink data packets are calculated / processed; The calculated / processed uplink data packet is sent to the user plane function network element.

45. The method according to any one of claims 19 to 34, characterized in that, The method is applied to a service unit and further includes: Receive downlink data packets from user plane function network elements; The downlink data packets are calculated / processed; Send the calculated / processed downlink data packets to the centralized unit.

46. ​​The method according to any one of claims 19 to 45, characterized in that, The method is applied to a centralized unit, where the calculated / processed uplink data packet contains indication information for indicating the uplink transmission direction. Based on the uplink transmission direction indication information, the calculated / processed uplink data packet is sent to the user plane function network element; or... The calculated / processed downlink data packet contains indication information for indicating the downlink transmission direction. Based on the indication information for the downlink transmission direction, the calculated / processed downlink data packet is sent to the terminal.

47. The method according to any one of claims 19 to 46, characterized in that, The method is applied to a service unit and further includes: Add indication information to the calculated / processed uplink data packet to indicate the uplink transmission direction; or, Add indication information to the calculated / processed downlink data packet to indicate the downlink transmission direction.

48. A communication device, characterized in that, Includes units for implementing the method as described in any one of claims 1 to 18, or the method as described in any one of claims 19 to 47.

49. A communication device, characterized in that, Includes a processor configured to cause the communication device to perform the method as claimed in any one of claims 1 to 18, or the method as claimed in any one of claims 19 to 47.

50. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed, cause the communication device to perform the method as described in any one of claims 1 to 18, or the method as described in any one of claims 19 to 47.

51. A computer program product, characterized in that, The computer program product includes instructions that, when executed, cause the communication device to perform the method as described in any one of claims 1 to 18, or the method as described in any one of claims 19 to 47.

Images