Communication method and device

Abstract

A communication method and apparatus, the method comprising: when a first access network device opens a shunt rule to shunt uplink data, sending a first message to a core network element, the first message being used for instructing the first access network device to open the shunt rule, therefore, the network element of the core network can know that the first access network equipment performs uplink data distribution. Furthermore, the problems that the PDU session resource is released, the flow statistics of the UPF network element on the uplink data is inaccurate and the like due to the fact that the core network element does not know that the first access network equipment opens the shunting rule can be solved.

Description

Technical Field

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

[0002] With the development of wireless technology, the concept of "local service offloading" has been proposed. Local service offloading refers to the ability of the first access network device to decide to send uplink data to devices other than user plane function (UPF) network elements. How to implement local service offloading and ensure that the core network can detect when the first access device initiates local service offloading is a research direction. Summary of the Invention

[0003] A communication method and apparatus are provided to enable core network elements to know that a first access network device has enabled traffic splitting rules.

[0004] In a first aspect, a communication method is provided. The execution subject of the method is a first access network device, or a module, unit, or component (such as a chip, chip system, processor, circuit, or others) applied in the first access network device. The first access network device is directly connected to a first server, and the first access network device is connected to the first server through a first network element, where the first network element is a network element with user plane functionality. The method includes: enabling a traffic splitting rule, the traffic splitting rule being used by the first access network device to split uplink data; for example, the first access network device, according to the traffic splitting rule, directly sends a portion of the uplink data to the first server, and / or sends another portion of the uplink data to the first server through the first network element; sending a first message to a second network element, where the second network element is a network element with session management functionality, the first message being used to instruct the first access network device to enable the traffic splitting rule.

[0005] Through the above design, when the first access network device enables traffic offloading rules to offload uplink data, it sends a first message to the core network element. This first message instructs the first access network device to enable traffic offloading rules, thereby allowing the core network element to know that the first access network device is offloading uplink data. Furthermore, this solves the problems of PDU session resources being released and inaccurate uplink traffic statistics by the UPF element caused by the core network element being unaware that the first access network device has enabled traffic offloading rules.

[0006] In one possible implementation, the first message includes: first indication information and / or the identifier of the traffic splitting rule, wherein the first indication information is used to instruct the first access network device to enable the traffic splitting rule.

[0007] In one possible implementation, enabling the traffic splitting rule includes: receiving a second message from the second network element, the second message being used to instruct the first access network device to enable the traffic splitting rule; and enabling the traffic splitting rule according to the instruction of the second message.

[0008] In one possible implementation, the second message includes: second indication information and / or the identifier of the traffic splitting rule, wherein the second indication information is used to instruct the first access network device to enable the traffic splitting rule.

[0009] In one possible implementation, the method further includes: determining the amount of first uplink data to be directly sent to the first server; and sending a third message to the second network element, the third message being used to indicate the amount of the first uplink data.

[0010] Through the above design, the first access network device automatically counts the amount of uplink data directly sent to the first server and reports this count to the second network element. Furthermore, the first network element (such as a UPF network element) can count the amount of uplink data sent by the first access network device to the first server through the first network element and report this to the second network element. The second network element then sums these two data counts as the amount of data sent by the first access network device to the first server, thus accurately determining the amount of data sent by the first access network device to the first server.

[0011] In one possible implementation, the method further includes: copying first uplink data, wherein the first uplink data is uplink data sent by the first access network device to the first server; and sending the copied first uplink data to the first network element, wherein the copied first uplink data is used by the first network element to determine the amount of uplink data sent by the first access network device to the first server, or to determine by the first network element that the connection resource corresponding to the uplink data is in an active state.

[0012] Through the above design, the first access network device copies the first uplink data, which is the uplink data that the first access network device directly sends to the first server; the first access network device sends the copied first uplink data to the first network element, and the copied first uplink data is used by the first network element to determine the amount of uplink data sent by the first access network device to the first server, or to determine by the first network element that the connection resource corresponding to the uplink data is in an active state, thereby avoiding the accidental release of the connection resource corresponding to the uplink data.

[0013] In one possible implementation, the method further includes: sending a third indication message to the first network element, the third indication message being used to indicate that the copied first uplink data is used to determine the amount of uplink data sent by the first access network device to the first server.

[0014] In one possible implementation, the method further includes sending a fourth message to the first network element, the fourth message being used to indicate that the connection resource corresponding to the uplink data is in an active state.

[0015] In one possible implementation, it further includes: receiving a fifth message from the first network element, wherein the fourth message is used to inquire whether the connection resource corresponding to the uplink data of the first access network device is in an active state.

[0016] The second aspect is a method opposite to the first aspect, with beneficial effects as described in the first aspect. It provides a communication method in which the execution subject of the method is a second network element, or a module, unit or component (e.g., chip, chip system, circuit, processor, or others) applied in the second network element. The second network element is a network element with session management function. The method includes: receiving a first message from a first access network device, the first message being used to instruct the first access network device to enable traffic splitting rules.

[0017] In one possible implementation, the first message includes: first indication information and / or the identifier of the traffic splitting rule, wherein the first indication information is used to instruct the first access network device to enable the traffic splitting rule.

[0018] In one possible implementation, the method further includes: sending a second message to the first access network device, the second message being used to instruct the first access network device to enable the traffic splitting rule.

[0019] In one possible implementation, the second message includes: second indication information and / or the identifier of the traffic splitting rule, wherein the second indication information is used to instruct the first access network device to enable the traffic splitting rule.

[0020] In one possible implementation, the method further includes: receiving a third message from the first access network device, the third message being used to indicate the amount of first uplink data, the first uplink data being uplink data directly sent by the first access network device to the first server.

[0021] In one possible implementation, the method further includes sending a sixth message to the first network element, the sixth message being used to instruct the first network element to stop timing the inactivity time of the connection resource corresponding to the uplink data.

[0022] In one possible implementation, the method further includes: receiving a seventh message from the first network element, the seventh message being used to notify the second network element that the connection resources corresponding to the uplink data are inactive;

[0023] Thirdly, a communication method is provided, wherein the execution subject of the method is a second network element, or a module, unit, or component (e.g., chip, chip system, circuit, processor, or others) applied in the second network element, wherein the second network element is a network element with session management function, and the method includes: receiving an eighth message from a fourth network element, wherein the fourth network element is a network element with edge application server discovery function, the eighth message including the address of a first server, the first server being directly connected to a first access network device; determining that the first access network device enables a traffic splitting rule, the traffic splitting rule being used to split uplink data.

[0024] Through the above design, the second network element (such as the SMF network element) can detect the traffic offloading rules enabled by the first access network device, which can solve the problems of missed traffic statistics and user plane inactivity caused by the core network side not knowing the traffic offloading behavior of the first access network device. For example, before the terminal sends uplink data, the terminal queries the DNS server for the IP address of the destination node. When the destination node returned by the DNS server is directly connected to the first access network device, the second network element can detect that the first access network device has enabled traffic offloading rules, thus preventing the release of the PDU session or QoS flow.

[0025] Fourthly, an apparatus is provided capable of implementing the method described in the first aspect. For example, the apparatus includes modules, units, or components that perform the method described in the first aspect. Specifically, the modules, units, or components can be implemented in hardware, software, or a combination of hardware and software.

[0026] In one design, the device includes a unit that performs the method described in the first aspect.

[0027] In one design, the device includes a processor for implementing the method of the first aspect 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, such that the device implements the method of the first aspect described above.

[0028] In one design, the device includes 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 implements the method of the first aspect described above through logic circuits or executing code instructions.

[0029] In one design, the device may be the 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 first device to perform the methods / operations / steps / actions described in the first aspect, or a device that can be used in conjunction with the first device.

[0030] Fifthly, an apparatus is provided capable of implementing the methods of the second or third aspect described above. For example, the apparatus includes modules, units, or components corresponding to the methods described in the second or third aspect. The modules, units, or components may be implemented in hardware, software, or a combination of hardware and software.

[0031] In one design, the device includes a unit that performs the methods described in the second or third aspect.

[0032] In one design, the device includes a processor for implementing the methods of the second or third aspect 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 the second or third aspect described above.

[0033] In one design, the device includes 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 implements the methods of the second or third aspect described above through logic circuits or executing code instructions.

[0034] In one design, the device may be a second device, or a module, unit, or component (e.g., a chip, chip system, circuit, or processor, etc.) that corresponds one-to-one with the methods / operations / steps / actions described in the second or third aspect of the second device, or a device that can be used in conjunction with the second device.

[0035] Sixthly, 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 third aspects described above.

[0036] A seventh aspect provides a computer program product, including a computer program or instructions that, when executed by a computer, cause the methods of any one of the first to third aspects to be performed.

[0037] Eighthly, a chip is provided, 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 third aspects described above.

[0038] Ninth aspect, a communication system is provided, comprising: a first communication device and a second communication device; wherein the first communication device is used to implement the method of the first aspect; and the second communication device is used to implement the method of the second aspect. Attached Figure Description

[0039] Figure 1 A schematic diagram of the communication system provided in the embodiments of this application;

[0040] Figure 2 A schematic diagram of the service-oriented architecture provided in the embodiments of this application;

[0041] Figure 3 This is a flowchart illustrating how a UPF network element triggers the release of a UPF session, as provided in an embodiment of this application.

[0042] Figures 4 to 9 A flowchart illustrating an embodiment of this application;

[0043] Figure 10 and Figure 11 This is a schematic diagram of the device provided in an embodiment of this application. Detailed Implementation

[0044] To make the objectives, technical solutions, and advantages of this application clearer, the 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.

[0045] It is understood that, in the embodiments of 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 there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates that the related objects before and after are in an "or" relationship; in the formulas of this application, the character " / " indicates that the related objects before and after are in 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.

[0046] The various numerical designations used in the embodiments of this application are for descriptive convenience 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. Furthermore, the various processes described below may include more or fewer steps than those shown in the text or graphics, without limitation. The ordinal numbers such as "first" and "second" 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.

[0047] like Figure 1 As shown in the figure, this application provides a schematic diagram of a communication system 1000, including: a terminal, a radio access network (RAN), a core network (CN), and a data network (DN).

[0048] 1. Terminal

[0049] A terminal is a device with specific wireless transceiver capabilities. A terminal can also be called a terminal device, user equipment (UE), mobile station, mobile terminal, 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 homes, smart offices, smart wearables, intelligent 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. The embodiments of this application do not limit the device form of the terminal.

[0050] 2. Radio Access Network (RAN)

[0051] The Radio Access Network (RAN) is primarily responsible for air interface-side functions such as radio resource management, Quality of Service (QoS) management, data compression, and encryption. The RAN includes at least one RAN node; the RAN node, as part of the communication system, assists terminals in achieving radio access. Terminals connect to the RAN node wirelessly. The RAN node connects to the core network wirelessly or via a wired connection. Core network equipment in the core network and RAN nodes in the RAN can be different physical devices, or they can be the same physical device integrating core network logical functions and radio access network logical functions.

[0052] RAN can be used for cellular systems related to the 3rd Generation Partnership Project (3GPP), such as 4G (4G4). th generation, 4G), fifth generation (5 th RAN can be a generation (5G) mobile communication system, or a future-oriented evolution system (such as future communication networks). RAN can also be an open access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. RAN can also be a communication system that integrates two or more of the above systems.

[0053] In one possible scenario, a RAN node 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 WiFi system. A RAN node can be a macro base station, a micro base station, an indoor station, a relay node, a donor node, or a radio controller in a CRAN scenario. Optionally, a RAN node can also be a server, a wearable device, a vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of the RAN node in this application embodiment can be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node in this application embodiment can also be a logical node, logical module, or software capable of implementing all or part of the RAN node functions.

[0054] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with each RAN node performing a portion of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be separate entities or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

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

[0056] It is understood that RAN nodes are used to help terminals achieve wireless access, and they can also be referred to in other different ways, such as RAN entity, ORAN device, access node, access network device, etc. In the following description of the embodiments of this application, unless otherwise specified, the node or device that helps the terminal achieve wireless access will be described as "access network device".

[0057] 3. Core Network CN

[0058] The core network enables functions such as user access control, mobility management, session management, user security authentication, and accounting. The core network includes user plane (UP) network elements and control plane (CP) network elements. For example, UP network elements may include user plane functions (UPF); CP network elements may include access and mobility management functions (AMF), session management functions (SMF), policy control functions (PCF), unified data management (UDM), application functions (AF), and network exposure functions (NEF), among others.

[0059] The UPF (User Profiler Function) network element is primarily responsible for user data processing (such as forwarding, receiving, and billing). For example, in downlink transmission, the UPF network element can receive user data from the DN (Digital Domain Provider) and forward it to the terminal through the access network equipment. In uplink transmission, the UPF can receive user data from the terminal through the access network equipment and forward it to the DN. In a Protocol Data Unit (PDU) session, the UPF network element directly connected to the DN via the N6 interface is also called a Protocol Data Unit Session Anchor (PSA). In one possible implementation, the UPF network element can be inserted into an uplink classifier (ULCL), in which case the UPF network element can be called an ULCL UPF. In uplink transmission, the ULCL UPF network element can perform uplink data splitting. For example, according to the configured splitting rules, a portion of the uplink data can be sent to the remote server through the anchor UPF network element, while another portion can be sent to the local server.

[0060] AMF network elements mainly perform registration, connection, reachability and mobility management, provide session management message transmission channels for terminal devices and SMF network elements, provide authentication and authorization functions for terminal access, and are the access point for the terminal and the wireless core network control plane.

[0061] SMF network elements are responsible for handling user services such as session establishment, modification, and release, as well as interaction with user plane functions. Specific functions include assigning Internet Protocol (IP) addresses to users and selecting UPF network elements that provide packet forwarding capabilities.

[0062] The PCF network element is responsible for generating terminal access policies and QoS flow control policies.

[0063] UDM network elements are used for user contract management, access authorization, and authentication information generation.

[0064] AF (Automatic Front-End) network elements primarily support interaction with the core network to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network side. Trusted AF network elements can directly access various network elements within the core network, while untrusted AF network elements (such as third-party AF network elements) can access various network elements within the core network through NEF (Non-Trusted Front-End) network elements.

[0065] In one possible implementation, the CP (Content Provider) network elements in the core network are connected to the service bus, and each CP network element has a corresponding interface with the service bus. For example, Figure 2As shown: The CP network elements include UDM, PCF, AMF, SMF, and AF network elements, etc., and each of these network elements can be connected to the service bus. Each of these network elements has a corresponding interface with the service bus; the names of each interface are as follows... Figure 2 As shown. For example, the interface between the AMF network element and the service bus is the Namf interface.

[0066] It is understood that the names of the network elements in the core network are not limited. As technology and / or standards evolve, the names of these network elements may change. For example, in a 5G communication system, the network element that implements the signaling processing part is called an AMF (Active Signaling Function) network element. In a 6G communication system, the network element that implements the above functions may also be called by other names, etc., without limitation. In the following description, the names of the network elements in 5G will be used as examples to describe the scheme of the embodiments of this application.

[0067] 4. DN

[0068] DN refers to the operator's network that provides data transmission services to users. Examples include the Internet Protocol (IP), IP Multimedia Service (IMS), and the Internet. A DN can be an external network of the operator or a network controlled by the operator, used to provide services to terminals. Servers can be deployed within a DN to perform specific functions.

[0069] like Figure 1 As shown, DNs can be divided into local DNs and remote DNs. Local DNs deploy local servers, which can also be called near-end servers; remote DNs deploy remote servers. Local servers are closer to the terminals; for example, they may be located in the same campus. Remote servers are farther from the terminals; for example, they may be located in a central location.

[0070] It is understandable that terminals, access network equipment, and network elements in the core network can be referred to as communication devices. For example, a terminal can be understood as a communication device with terminal functions, access network equipment can be understood as a communication device with base station functions, and network elements in the core network can be understood as devices with core network element functions. For example, an SMF can be understood as a communication device with SMF functions.

[0071] exist Figure 1 In the network architecture shown, access network devices can be directly connected to the local server, and access network devices are also connected to the local server through the first network element. The local server can also be described as: a computing power board, or a network node with a certain special business function (such as computing power function), without restriction.

[0072] The first network element can be a network element that implements user plane functions, for example, a UPF network element. This UPF network element includes an uplink classifier (ULCL), and can be called an ULCL UPF network element. That is, the access network device can connect to local services through the ULCL UPF network element. Optionally, the access network device can also connect to a remote server through the aforementioned first network element and the UPF network element (or anchor UPF).

[0073] In one understanding, terminals, access network equipment, UPF network elements, and DNs are generally referred to as user plane functions and entities. User data flows can be transmitted through protocol data unit (PDU) sessions established between the terminal and the DN. The user plane is used for service data transport. Other network elements in the communication system 1000, such as SMF and AMF network elements, can be referred to as control plane functions and entities. The connection methods between the control plane CP and the user plane UP include:

[0074] 1. The AMF network element has a direct interface with the access network equipment, and the SMF network element and the UPF network element have a direct interface. Alternatively,

[0075] 2. Both AMF and SMF network elements have direct interfaces with access network equipment, and SMF and UPF network elements have direct interfaces. Alternatively,

[0076] 3. The AMF network element has a direct interface with the UPF network element and the access network equipment, and the SMF network element has a direct interface with the UPF network element and the access network equipment.

[0077] In current solutions, core network elements such as SMF elements deactivate sessions to release the session's user plane connection, but retain the control plane connection for quick restoration. In one solution, if a UPF element does not detect data transmission from a PDU session for an extended period, it can report an inactivity report for that PDU session to the SMF element. The SMF element can then reactivate the PDU session based on this report. For example, such as... Figure 3 As shown, a flowchart is provided, including:

[0078] Step 1: The UPF network element triggers a report event.

[0079] For example, during the establishment of a PDU session, the SMF network element can configure an inactivity timer for that PDU session. If the UPF network element detects that there is no data transmission in the PDU session during the timer's runtime, it will trigger a report to the SMF network element that the PDU session is inactive.

[0080] Step 2: The UPF network element sends an N4 session report to the SMF network element.

[0081] In one interpretation, the interface between the UPF network element and the SMF network element is the N4 interface, and the N4 session report includes the identifier of the N4 session and the identifier of user plane inactivity.

[0082] Step 3: The SMF network element replies to the UPF network element with an N4 session report acknowledgment (N4 sessionreportACK).

[0083] In one interpretation, the SMF network element obtains the N4 session context based on the N4 session identifier included in the N4 session report; and determines the corresponding PDU session based on the N4 session context. Based on the aforementioned user plane inactivity report, it deactivates and / or releases the resources of the PDU session. For example, it deactivates the UP connection of the PDU session, releases air interface resources, connections between the UPF network element and access network equipment, and connections between the SMF and UPF, etc.

[0084] exist Figure 1 In the network architecture shown, the access network device (hereinafter referred to as the first access network device) can receive uplink data from the terminal; the first access network device can send the uplink data to the local server through two paths. That is, the first access network device can split the uplink data from the terminal, sending a portion of the uplink data directly to the local server (which can be considered one path); and sending the other portion of the uplink data to the local server through the first network element (which can be considered another path). In one possible implementation, the first access network device can enable a splitting rule and split the uplink data based on the splitting rule. For example, based on the splitting rule, a portion of the uplink data can be sent directly to the local server, and the other portion of the uplink data can be sent to the local server through the first network element. If the core network cannot detect whether the first access network device has enabled a splitting rule to split the uplink data, the following problems may exist:

[0085] Question 1: In the current plan, can we refer to... Figure 3When a UPF network element detects that a PDU session has not transmitted data for a period of time, it reports the PDU session as inactive to the SMF network element. Upon receiving the report, the SMF network element can deactivate and / or release the PDU session. In scenarios where the first access network device uses traffic splitting rules to split uplink data: the first access network device can utilize the air interface resources of the PDU session to receive uplink data, and the first access network device can directly send the uplink data to the local server. In this case, according to the current scheme, if the core network is unaware that the first access network device is using traffic splitting rules to split uplink data, the UPF network element, upon detecting that the PDU session meets the above conditions, will report the PDU session as inactive to the SMF network element, which may result in the session being deactivated while the air interface connection resources of the PDU session are still in use.

[0086] Question 2: In the current solution, the UPF network element counts and reports the traffic of the terminal. In scenarios where the first access network device enables traffic splitting rules to split uplink data, if the first access network device directly sends the uplink data to the local server, the UPF network element cannot count the traffic corresponding to this part of the uplink data, resulting in inaccurate uplink traffic statistics by the UPF network element.

[0087] In view of the above, embodiments of this application provide a communication method and apparatus. In this method, when a first access network device enables a traffic splitting rule to split uplink data, it sends a first message to a core network element. This first message instructs the first access network device to enable the traffic splitting rule, thereby enabling the core network element to know that the first access network device is splitting uplink data. Furthermore, this solves the problems of PDU session resources being released due to the core network element not knowing that the first access network device has enabled the traffic splitting rule, and inaccurate uplink data traffic statistics by the UPF network element.

[0088] like Figure 4 As shown, a flowchart is provided, including:

[0089] Step 510: The first access network device enables the traffic splitting rule, which is used to split uplink data.

[0090] In one possible implementation, the traffic splitting rule is a predefined rule, for example, a traffic splitting rule that the first access network device implements itself or generates based on the configuration of a local server (such as a first server). The first access network device can enable the predefined traffic splitting rule. In one description, "enable" can also be replaced with: use. For example, the first access network device can use the traffic splitting rule.

[0091] Alternatively, the second network element may instruct the first access network device to enable traffic offloading rules. For example, the second network element sends a second message to the first access network device, and the first access network device receives the second message from the second network element. The second message instructs the first access network device to enable traffic offloading rules; the first access network device enables traffic offloading rules according to the instructions in the second message. For example, the name of the second message may implicitly instruct the first access network device to enable traffic offloading rules. Alternatively, the second message may include second instruction information and / or an identifier for the traffic offloading rule, whereby the second instruction information instructs the first access network device to enable traffic offloading rules, and the identifier for the traffic offloading rule implicitly instructs the first access network device to enable traffic offloading rules.

[0092] In one possible implementation, the first access network device receives uplink data from the terminal device. The first access network device can distribute the uplink data based on a distribution rule. For example, the first access network device may send a portion of the uplink data directly to the first server and another portion through a first network element; or, the first access network device may send all of the uplink data directly to the first server; or, the first access network device may send all of the uplink data through a first network element to the first server. It is understood that the first server can be... Figure 1 In the network architecture shown, the local server, specifically the first network element, can be a network element that implements user plane functions, such as a UPF network element. Further, optionally, this UPF network element can be an ULCL UPF network element. In one interpretation, an ULCLUPF network element refers to a UPF network element that is inserted into ULCL.

[0093] The following example illustrates the process by which the first access network device performs uplink data routing based on routing rules: The first access network device receives uplink data from a terminal. The first access network device can route the uplink data based on information carried in the uplink data (e.g., at least one of the following: destination media access control (MAC) address, application (APP) ID, and / or port number). For example, the first access network device can determine the corresponding port based on the destination MAC address and virtual local area network (VLAN) ID carried in the uplink data; for example, if the determined port is the first port, then the first access network device sends the uplink data through the first port. For example, if the first access network device is directly connected to the first server through the first port, then it is considered that the first access network device directly sends the uplink data to the first server. Alternatively, if the determined port is the second port, then the first access network device sends the uplink data through the second port. For example, if the first access network device can be directly connected to the first network element through the second port, then when the first network element receives the uplink data, the first network element sends the uplink data to the first server; at this time, it is considered that the first access network device sends uplink data to the first server through the first network element.

[0094] It is understandable that the first access network device can perform uplink data distribution based on distribution rules for a PDU session. For example, the first access network device receives uplink data from a terminal device through the PDU session, directly sends a portion of the uplink data from the PDU session to the first server, and sends another portion of the uplink data from the PDU session to the first server through the first network element. Alternatively, it can distribute uplink data based on distribution rules for a quality of service (QoS) flow. For example, the first access network device receives uplink data from a terminal device through a QoS flow, directly sends a portion of the uplink data from the QoS flow to the first server, and sends another portion of the uplink data from the QoS flow to the first server through the first network element, etc. Optionally, the first and second messages below may also include the identifier of the PDU session or the identifier of the QoS flow.

[0095] Step 520: The first access network device sends a first message to the second network element, and the second network element receives the first message from the first access network device.

[0096] The second network element is a network element with session management functions, such as an SMF network element. The first message is used to instruct the first access network device to enable traffic offloading rules. Specifically, it can enable traffic offloading rules for a specific PDU session or for a specific QoS flow; this invention does not limit this. The second network element is a network element in the core network. When the second network element receives the first message, it can determine that the first access network device has enabled traffic offloading rules, thereby enabling the core network to perceive the traffic offloading of uplink data by the first access network device, further resolving various problems caused by the core network's inability to perceive the traffic offloading by the first access network device.

[0097] The first message includes first indication information and / or a traffic splitting rule identifier. The first indication information is used to instruct the first access network device to enable a traffic splitting rule, or to indicate that the first access network device has successfully enabled a traffic splitting rule. The first indication information can be implemented in various ways, and this invention is not limited thereto. In one possible implementation, the first indication information is a bit indication information. When the value of this bit is 1, it indicates that the first access network device has enabled a traffic splitting rule or has successfully enabled a traffic splitting rule; when the value of this bit is 0, it indicates that the first access network device has not enabled / disabled a traffic splitting rule or has failed to enable a traffic splitting rule. In another possible implementation, the first indication information is a byte indication information, such as "on" indicating enabled, "off" indicating disabled, or "success" indicating success, and "failure" indicating failure. In yet another possible implementation, the first indication information is the name of the first message.

[0098] The following example illustrates the process of a first access network device sending a first message to a second network element: If there is a direct interface between the first access network device and the second network element, the first access network device can directly send the first message to the second network element. Alternatively, if there is a direct interface between the first access network device and the AMF network element, and a direct interface between the AMF network element and the second network element, then the first access network device can send the first message to the second network element through the AMF network element. In one interpretation, the first access network device sends the first message to the AMF network element, and the AMF network element forwards the first message to the second network element. The first message includes first indication information and / or the identifier of a traffic splitting rule. Alternatively, in another interpretation, the first access network device sends message X to the AMF network element, and message X includes first indication information and / or the identifier of a traffic splitting rule. When the AMF network element receives message X, it retrieves the first indication information and / or the identifier of a traffic splitting rule from message X. The AMF network element then sends message Y to the second network element, and message Y includes the first indication information and / or the identifier of a traffic splitting rule. In this case, the first message can be understood as message X and / or message Y. Understandably, there are no restrictions on the names of AMF network elements. For example, an AMF network element can be described as a "third network element," which is a network element with access and mobility management functions. Similarly, the second network element mentioned above can directly send a second message to the first access network device. Alternatively, the second network element can send a second message to the first access network device through the AMF network element, without restriction.

[0099] In one example, the first access network device can decide independently whether to use a traffic splitting rule to split uplink data, so the core network is unaware of whether the first access network device has split the data. In this embodiment, when the first access network device uses a traffic splitting rule to split uplink data, it sends a first message to the core network element (second network element), thereby enabling the core network element (second network element) to know that the first access network device has used a traffic splitting rule to split uplink data. For details, please refer to the description of scheme a in Embodiment 1 below.

[0100] In another example, the second network element can instruct the first access network device to enable the traffic offloading rule. For instance, if the PCF network element or the second network element discovers that the terminal has subscribed to a traffic offloading service through the terminal's subscription information, it can notify the first access network device to enable the traffic offloading rule through the second network element. The first access network device can then enable the traffic offloading rule according to the instruction of the second network element. For details, please refer to the descriptions of schemes b and c in Embodiment 1 below, and the description of Embodiment 3 below.

[0101] It is understandable that after the first access network device enables the traffic splitting rule, it can split the uplink data based on this rule. For example, the first access network device can receive uplink data from the terminal device and split the uplink data based on the splitting rule. For example, the first access network device may send a portion of the uplink data directly to the first server and send another portion of the uplink data to the first server through the first network element. In this case, the first network element (such as the UPF network element) can only count the uplink data traffic transmitted through it, which leads to inaccurate uplink data traffic counted by the UPF network element. To solve the above problem, the embodiments of this application provide the following two solutions:

[0102] One solution: The first access network device independently calculates the amount of uplink data directly sent to the first server and reports this calculated amount to the second network element. Further, the first network element (such as a UPF network element) can calculate the amount of uplink data sent by the first access network device to the first server through the first network element and report this to the second network element. The second network element sums these two data amounts as the amount of data sent by the first access network device to the first server, thus accurately determining the amount of data sent by the first access network device to the first server. For example:

[0103] The first access network device determines (or counts) the amount of uplink data (which may be referred to as the first uplink data) directly sent to the first server, and sends a third message to the second network element. This third message includes an indication of the amount of the first uplink data. Optionally, the name of this third message may be a traffic measurement message. It is understood that the first access network device may send the third message directly to the second network element, or it may send the third message to the second network element through a third network element (such as an AMF network element), without limitation. For details on this solution, please refer to the description in Embodiment 1.

[0104] Another solution: The first access network device copies the first uplink data, which is the uplink data directly sent by the first access network device to the first server. The first access network device sends the copied first uplink data to the first network element. The copied first uplink data is used by the first network element to determine the amount of uplink data sent by the first access network device to the first server, or to determine that the connection resource corresponding to the uplink data is active. Optionally, the first access network device sends third indication information to the first network element. This third indication information is used to indicate that the copied first uplink data is used to determine the amount of uplink data sent to the first server. Optionally, the copied first uplink data and the third indication information can be carried in one message or in different messages, without limitation. Alternatively, the third indication information can be carried in the copied first uplink data, such as by using an extended packet header to represent the third indication information. For details on this solution, please refer to the description in Embodiment 2.

[0105] In the current plan, as mentioned above Figure 3 Explanation: Each PDU session has a corresponding inactivity timer. If a PDU session does not transmit data during the inactivity timer's execution, the UPF network element reports an N4 session report to the SMF network element. Based on the N4 session report, the SMF network element will deactivate the PDU session, for example, by releasing the user plane resources corresponding to the PDU session, such as air interface resources and connection resources between the access network device and the UPF. In scenarios where the first access network device enables traffic splitting rules, although the PDU session does not transmit data between the access network device and the UPF network element, the first access network device may still use the PDU session to directly transmit data to the first server, meaning the air interface resources of the PDU session are still being used. The above solution may cause the SMF network element to release the connection resources corresponding to the uplink data, i.e., release the air interface resources used to transmit the uplink data. To address the above problems, this application provides the following solutions:

[0106] One solution: The first access network device proactively sends a fourth message to the first network element. This fourth message indicates that the connection resource corresponding to the uplink data is active. Upon receiving this indication, the first network element no longer sends a request message (such as an N4 session report) to the second network element to release the connection resource. For example, the connection resource corresponding to the uplink data may refer to the PDU session resource or the quality of service stream resource that transmits the uplink data.

[0107] In one description, the fourth message is used to indicate that the connection resource corresponding to the uplink data is active. This can be replaced by: the fourth message instructing the first network element not to / prohibiting requests to release the connection resource corresponding to the uplink data. After the first access network device directly sends uplink data to the first server based on the traffic splitting rules: the first access network device can periodically, or when certain conditions are met, send the fourth message to the first network element. This fourth message can be an empty packet, forwarded uplink data, or a message prohibiting the release of the connection resource corresponding to the uplink data, etc. This invention does not limit the specific implementation method. The fourth message implicitly instructs the UPF not to request the release of the connection resource.

[0108] Another solution: Before the first network element requests the release of the connection resource corresponding to the uplink data (e.g., before sending the N4 session report): the first network element sends a fifth message to the first access network device. The fifth message inquires whether the connection resource corresponding to the uplink data is active. When the first access network device receives the inquiry in the fifth message, in response, the first access network device sends a fourth message to the first network element. The fourth message indicates that the connection resource corresponding to the uplink data is active. In one description, the fourth message indicates that the connection resource corresponding to the uplink data is active; it can also be described as: the fourth message indicates that requesting the release of the connection resource corresponding to the uplink data should not / is prohibited, as described in the following embodiment 1.

[0109] For example, the above solution can be triggered proactively by the first network element. The first network element can periodically send a fifth message to the first access network device, which inquires whether the connection resources corresponding to the uplink data can be released. For example, the fifth message can be encapsulated using the GPRS tunneling protocol-userplane (GTP-U) protocol, and the header of the fifth message (which can be called the GTP-U header) can adopt an enhanced design. For example, an additional flag bit can be added to the extension bits of the GTP-U header. This flag bit is used to indicate whether the fifth message is a release request message or a connection activity detection message, or it can be used to inquire whether the connection resources can be released. Alternatively, an additional flag bit can be added to the reserved sequence number of the message type field in the GTP-U header. This flag bit is used to indicate whether the corresponding fifth message is a release request message or a connection activity detection message, or it can be used to inquire whether the connection resources can be released. If the first access network device enables traffic splitting rules, the first access network device sends a fourth message to the first network element. This fourth message is used to indicate that the first access network device is performing traffic splitting, or to instruct the first network element not to request the release of connection resources. For example, the fourth message can be encapsulated using the GTP-U protocol, and its header (which can be called the GTP-U header) can employ an enhanced design. For instance, an additional flag bit can be added to the extension bits of the GTP-U header. This flag bit is used to instruct the first access network device to enable traffic offloading rules, or to instruct the first network element not to request the release of the corresponding connection resources. In one possible implementation, the fourth message can be named a release request, and the fifth message can be named a release response, as detailed in Embodiment 1.

[0110] In one possible implementation, the solution provided in this application embodiment can be applied to the establishment process of a PDU session. For ease of understanding, the process of establishing a PDU session is described; however, it should be understood that this process is not intended to limit the embodiments of this application. Figure 5 The diagram shown illustrates the process of establishing a PDU session, including:

[0111] Step 1: The terminal sends a PDU sessionestablishment request to the AMF network element.

[0112] The specific transmission path for the PDU session establishment request is: terminal → access network device → AMF network element. For example, the terminal sends a message to the AMF network element, which includes information such as: S-NSSAI(s), DNN, PDU session identifier (ID), request type, and N1 SM container. The N1 SM container contains a PDU session establishment request, which includes information such as: PDU session identifier, requested PDU session type, and requested SSC mode.

[0113] Step 2: Select SMF network element from AMF network element.

[0114] For example, AMF network elements query the network repository function (NRF) based on S-NSSAI and DNN to select the appropriate SMF network element.

[0115] Step 3: The AMF network element sends a PDU session creation SM context request (Nsmf_PDUSession_CreateSMContext Request) message to the SMF network element.

[0116] For example, the PDU session creation SM context request includes information such as SUPI, DNN, S-NSSAI(s), PDU session ID, AMF ID, request type, N1 SM container, and user location. The N1 SM container includes the PDU session establishment request.

[0117] Step 4: The SMF network element initiates a PDU session registration with the UDM network element and obtains the subscription information.

[0118] The SMF network element obtains session-related subscription data, and the UDM network element sends a registration response to the SMF network element. This registration response includes: DNN, S-NSSAI, AllowedPDU Session Type, Allowed SSC Mode, 5QI, ARP, SessionAM, whether secondary authentication is required, and secondary authentication-related information such as the authentication server address.

[0119] Step 5: The SMF network element generates a session context and sends a PDU session creation SM context response (Nsmf_PDUSession_CreateSMContext Response) message to the AMF network element. This message indicates the session establishment result. If the establishment is successful, the session context ID information (including the SM Context ID) will be returned to the AMF. If the session establishment fails, a rejection reason will be returned.

[0120] Step 6: Optional, perform secondary authentication for PDU session establishment.

[0121] Step 7a: Optionally, the SMF network element performs PCF network element selection. If dynamic PCC is deployed, the SMF network element selects a PCF network element for policy control.

[0122] Step 7b: Optionally, the SMF network element and the PCF network element execute the session policy establishment process (SMF obtains PCC rules from PC). The PCF will issue relevant QoS control policies, charging control policies, UPF selection policies, and other information.

[0123] Step 8: SMF network elements perform UPF network element selection.

[0124] For example, the SMF network element performs UPF selection based on information such as terminal location, DNN, and S-NSSAI. The SMF network element assigns an IP address to the terminal based on the terminal's subscription information in the UDM, or the UPF network element assigns an IP address to the terminal based on its local address pool. If the SMF network element assigns the terminal's IP address, the SMF triggers the PCF update policy; if the UPF network element assigns the IP address, the PCF update policy is triggered only after the UPF network element has assigned the IP address.

[0125] Step 9: Optionally, the SMF network element initiates a session policy update process to the PCF network element.

[0126] For example, the SMF network element sends a policy update request to the PCF network element. This message carries information such as the selected UPF and the IP address assigned to the terminal. The PCF network element then provides the updated policy and QoS parameters to the SMF network element.

[0127] Step 10a. The SMF network element sends an N4 session establishment request to the selected UPF network element.

[0128] The N4 session establishment request includes: Core Network Tunnel Info (containing TEID (an endpoint used to uniquely identify a tunnel), IP address, and Packet Detection Rule (PDR).

[0129] Step 10b: The UPF network element sends an N4 session establishment response to the SMF network element. The N4 session establishment response includes the N4 session establishment result.

[0130] Step 11: The SMF network element sends a communication N1N2 message transfer message (Namf_Communication_N1N2MessageTransfer) to the AMF network element.

[0131] For example, the above message includes: PDU session identifier, access type, N1 SM container, and N2 SM information. The N1 SM container is the session establishment result sent by the SMF network element to the terminal, containing a PDU session establishment acceptance. This acceptance includes information such as Allowed IPv4 address, QoS Rules, S-NAASI, and selected SSC mode, notifying the access network device and the terminal that a PDU session needs to be established. The N2 SM information is a resource establishment request sent by the SMF network element to the access network device, containing information such as QFI(s) and CN tunnel information. Afterwards, the AMF network element sends a Namf_Communication_N1N2MessageTransfer response message to the SMF network element.

[0132] Step 12: The AMF network element sends an N2 PDU session request to the access network device. The N2 PDU session request includes NAS messages and N2 SM information.

[0133] Step 13: The access network device forwards the NAS message to the terminal.

[0134] In this process, the access network device initiates a signaling interaction with the terminal and forwards the NAS message from step 12 to the terminal.

[0135] Step 14: The access network device sends an N2 PDU session response message to the AMF network element, carrying downlink media plane tunnel endpoint information. At this time, the uplink data channel of the UE is established. The PDU session response message from the access network device to the AMF network element includes: PDU session ID, cause, and N2 SM information Info (PDU session ID).

[0136] Step 15: The AMF network element sends a PDU session update SM context request (Nsmf_PDUSession_UpdateSMContext Request) to the SMF network element, which carries information such as SM Context ID, Requested Type, and N2SM Info (e.g., access network tunnel information AN Tunnel Info).

[0137] Step 16a: The SMF network element sends an N4 Session Modification Request message to the UPF network element.

[0138] Step 16b: The UPF network element sends an N4 Session Modification Response message to the SMF network element. At this point, the downlink data channel is established.

[0139] Step 16c: SMF registers with UDM, carrying information such as SUPI, DNN, S-NSSAI, PDU Session ID, etc., and UDM saves the relevant data.

[0140] Step 17: The SMF sends a PDU session update SM context response message, Nsmf_PDUSession_UpdateSMContext Response, to the AMF to complete the SM context update.

[0141] Step 18: The SMF sends a PDU session SM context status notification (Nsmf_PDUSession_SMContextStatusNotify) message to the AMF, indicating that the session has been established.

[0142] Step 19: If the terminal requests to establish an IPv6 type PDU session, the SMF also needs to configure the IPv6 address for the terminal.

[0143] Step 20: If the terminal supports sending Port Management Information Containers, the SMF network element needs to notify the PCF network element that the 5G system (5GS) bridge information is available.

[0144] Step 21: If the session establishment fails after step 4, the SMF network element needs to initiate an unsubscription process to the UDM network element.

[0145] For ease of description and understanding, in the detailed descriptions of [Example 1] to [Example 3] below: the first network element is called the UPF network element, the second network element is called the SMF network element, and the third network element is called the AMF network element.

[0146] Example 1

[0147] In the first embodiment, when the first access network device enables traffic offloading rules, it reports corresponding information to the core network element to instruct it to enable the rules, thus allowing the core network device to know that the first access network device has enabled the rules. Specifically, the following three solutions are provided:

[0148] Option a: The first access network device automatically enables the traffic splitting rule, and the first access network device reports the corresponding message to the SMF network element when the PDU session is established, instructing the first access network device to enable the traffic splitting rule.

[0149] Option b: When a PDU session is established, if the PCF or SMF network element discovers that the terminal has subscribed to a traffic offloading service based on the terminal's subscription information, the PCF or SMF network element can instruct the first access network device to enable the traffic offloading rule. Based on this instruction, the first access network device enables the traffic offloading rule and sends a response message to the SMF network element to indicate that the first access network device has successfully enabled the traffic offloading rule.

[0150] Option c: After the PDU session is successfully established, the AF network element instructs the first access network device to enable the traffic splitting rule. This can be done through network elements such as NEF, UDR, PCF, and SMF. Based on this instruction, the first access network device enables the traffic splitting rule and sends a corresponding message to the SMF network element to indicate that the traffic splitting rule has been successfully enabled.

[0151] like Figure 6 As shown, a flowchart is provided, including:

[0152] Step 710: Establish the N4 tunnel.

[0153] In one possible implementation, the process of establishing the N4 tunnel can be referred to... Figure 6 Steps 1 to 10b in the above. In one interpretation, the interface between the UPF network element and the SMF network element is N4, and the transmission tunnel between the UPF network element and the SMF network element is called the N4 tunnel. This N4 tunnel is associated with the currently established PDU session. In one interpretation, the UP transmission path of a PDU session is: terminal—first access network device—UPF—DN (such as the first server). The N4 tunnel between the UPF network element and the SMF network element belongs to the CP connection of this PDU session.

[0154] Option a: During the establishment of a PDU session, the first access network device automatically enables the traffic splitting rule and reports it to the SMF network element.

[0155] Step 720a: The SMF network element can be configured to establish a PDU session with the first access network device, and the SMF network element sends a first request to the AMF network element.

[0156] In one possible implementation, the first request is used to request the AMF network element to notify the first access network device and the terminal to establish a PDU session. The first request includes a PDU session identifier, an N1 session management (SM) container, and N2 SM information. The N1 SM container is sent to the terminal to notify it of the PDU session establishment result; the N2 SM information is sent to the first access network device to request it to establish resources for the PDU session. For example, the first request may be a Namf_communication_N1N2 message transfer message.

[0157] Step 730a: The AMF network element sends a second request to the first access network device.

[0158] In one possible implementation, the second request is used to request the first access network device to establish resources for the PDU session. The second request includes a non-access stratum (NAS) message and the N2 SM information from step 720a. For example, the second request may be an N2 PDU session request message.

[0159] It is understandable that if there is a direct connection between the SMF network element and the first access network device, steps 720a and 730a can be combined into one step. For example, the SMF network element can directly send the second request to the first access network device.

[0160] Step 740a: The first access network device forwards a message to the terminal that represents the result of the PDU session establishment.

[0161] For example, the message could be a NAS message that includes a PDU session identifier and an N1 SM container. The N1 SM container includes a PDU session establishment accept.

[0162] Step 750a: The first access network device enables the traffic offloading rule and sends a second response to the AMF network element. This second response is a response to the second request in step 730a.

[0163] For example, the second response is used to notify the core network of the successful establishment of the uplink data path. For example, the name of the second response could be N2 PDU Session response. The second response includes first indication information and / or an identifier for the traffic offloading rule. For example, the first indication information is a bit indication information; a value of 1 indicates that the first access network device has enabled the traffic offloading rule, and a value of 0 indicates that the first access network device has not enabled / disabled the traffic offloading rule. In another possible implementation, the first indication information is a byte indication information, such as "on" indicating enabled and "off" indicating disabled. In yet another possible implementation, the first indication information is the message name.

[0164] Step 760a: The AMF network element sends a first response to the SMF network element, which may be a response to the first request in step 720a.

[0165] The first response includes a first indication message and / or an identifier for a traffic splitting rule. For example, the first response could be a response message for a communication N1N2 message transfer (Namf_communication_N1N2 messagetransfer).

[0166] It is understandable that if there is a direct interface between the SMF network element and the first access network device, steps 750a and 760a can be combined into one step. For example, the first access network device directly sends a message (such as the first message) to the SMF network element, which includes first indication information and / or the identifier of the traffic offloading rule.

[0167] Understandably, in Figure 5 The process is described as follows: A first access network device sends a first message to a second network element (such as an SMF network element), the first message including first indication information and / or the identifier of a traffic offloading rule. In case a above, the first message can be understood to include: a second response and a first response. That is, in case a above, the first access network device sends a second response to the AMF network element, the second response including the first indication information and / or the identifier of a traffic offloading rule. In the second response, the AMF network element obtains the first indication information and / or the identifier of the traffic offloading rule, and the AMF network element sends a first response to the SMF network element, the first response including the first indication information and / or the identifier of the traffic offloading rule.

[0168] Option b: During the PDU session establishment process, the PCF network element or SMF network element discovers that the terminal has subscribed to the offloading service through the terminal's subscription information. The SMF network element notifies the first access network device to enable the offloading rule. The first access network device enables the offloading rule according to the instruction of the SMF network element, offloads the uplink data, and indicates to the SMF network element that the offloading rule has been successfully enabled.

[0169] For example, if a PCF network element discovers that a terminal has subscribed to a traffic offloading service based on the terminal's subscription information, the PCF network element can send an indication message to the SMF network element. This indication message is used to instruct the first access network device to enable the traffic offloading rule. It is understandable that a new message can be designed to carry the above indication, or the PCF network element can carry the above indication message in the message sending the SM policy to the SMF during the PDU session establishment process. Alternatively, the SMF can discover that the terminal has subscribed to a traffic offloading service based on the terminal's subscription information.

[0170] Step 720b: The SMF network element configures the first access network device to establish a PDU session, and the SMF network element sends the first request to the AMF network element.

[0171] The first request includes second indication information and / or an identifier of a traffic splitting rule; wherein the second indication information is used to instruct the first access device to enable the traffic splitting rule. For example, the second indication information is a bit indication information, where a value of 1 indicates that the first access network device enables the traffic splitting rule, and a value of 0 indicates that the first access network device does not enable / disable the traffic splitting rule. Alternatively, the first indication information is a byte indication information, such as on indicating enabled and off indicating disabled. Alternatively, the first indication information is the name of the first request. In one possible implementation, the first request includes a PDU session identifier, an N1 SM container, and N2 SM information, where the N2 SM information includes the second indication information and / or an identifier of the traffic splitting rule.

[0172] Step 730b: The AMF network element sends a second request to the first access network device.

[0173] The second request includes second instruction information and / or an identifier of a traffic offloading rule. In one possible implementation, the second request includes a NAS message and N2 SM information, the N2 SM information including the second instruction information and / or an identifier of a traffic offloading rule.

[0174] It is understandable that if there is a direct interface between the SMF network element and the first access network device, steps 720b and 730b can be combined into one step. For example, the SMF network element can directly send the second indication information and / or the identifier of the traffic splitting rule to the SMF network element.

[0175] Understandably, in the preceding text Figure 5The process is described as follows: A second network element (such as an SMF network element) sends a second message to a first access network device. The second message includes second indication information and / or an identifier of a traffic splitting rule. In the above description, the second message can be N2SM information, which includes the second indication information and / or an identifier of a traffic splitting rule. That is, the SMF network element sends a first request to the AMF network element, which includes the N2SM information. The AMF network element obtains the N2SM information in the first request. The AMF network element sends a second request to the first access network device, which includes the N2SM information. Subsequently, the first access network device enables the traffic splitting rule according to the second indication information and / or the identifier of the traffic splitting rule included in the N2SM information, and sends an indication to the SMF network element that the traffic splitting rule has been successfully enabled.

[0176] Step 740b: The first access network device forwards a message to the terminal that represents the result of the PDU session establishment.

[0177] Step 750b: The first access network device sends a second response to the AMF network element, which is a response to the second request in step 730b.

[0178] For example, the second response may include first indication information and / or an identifier for a traffic offloading rule, wherein the first indication information is used to indicate that the first access network device has successfully enabled the traffic offloading rule. For example, the second response may include a bit; when the value of this bit is a first value, it indicates that the first access network device has successfully enabled the traffic offloading rule; when the value of this bit is a second value, it indicates that the first access network device has failed to enable the traffic offloading rule. The identifier for the aforementioned traffic offloading rule is used to implicitly indicate that the first access network device has successfully enabled the traffic offloading rule.

[0179] Step 760b: In response to the first request, the AMF network element sends a first response to the SMF network element, the first response including first indication information and / or the identifier of the traffic splitting rule.

[0180] Step 770: Continue the PDU session establishment process to establish a session between the terminal, the first access network device, and the UPF.

[0181] In scheme c, the AF network element instructs the first access network device to enable the traffic splitting rule through network elements such as NEF, UDR, PCF, and SMF. The first access network device then instructs the SMF network element that the first access network device has successfully enabled the traffic splitting rule.

[0182] Step a: The AF network element sends a third request to the NEF network element.

[0183] The third request is used to request the first access network device to enable traffic offloading rules. The third request message includes the terminal's identifier (such as a generic public subscription identifier (GPSI)) and third indication information, which instructs the first access network device to enable traffic offloading rules. In one possible implementation, the third request may be named a Transport Stream Influence Create / Update Request (Nnef_TrafficInfluence_Create / Update Request) message.

[0184] Step b: NEF network element updates UDR information.

[0185] For example, the NEF network element stores the information from the third request sent by the AF network element in the UDR network element. The data structure for storing the information corresponding to the third request in the UDR network element is not limited. For example, it can be stored under a dataset (application data), a data subset, a data key (AF internal identifier, terminal identifier), and / or DNN+S-NSSAI, indicating that under this AF network element with the terminal identifier, the first access network device needs to perform traffic splitting based on the splitting rules.

[0186] Step c: The UDR network element sends a first notification message to the PCF network element. This first communication message is used to communicate with the PCF network element to update the SM policy.

[0187] For example, the first notification message could be named a Data Management Notification (Nudr_DM_Notify) message. If the PCF determines that the request from the AF network element has a corresponding PDU session, it will trigger an SM policy update and send a second notification message to the SMF network element.

[0188] Step d: The PCF network element sends a second notification message to the SMF network element.

[0189] The second notification message is used to notify the SMF network element to update the policy. This second notification message includes a third instruction, which instructs the first access network device to enable traffic splitting rules. For example, the name of the second notification message could be Session Management Policy Control Update Notification (Npcf_SMPolicyControl_UpdateNotify).

[0190] Step e: The SMF network element instructs the first access network device to enable the traffic splitting rule through the AMF network element. The first access network device instructs the SMF network element through the AMF network element that the traffic splitting rule has been successfully enabled. For details, please refer to the description of steps 720b to 760b in scheme b.

[0191] It is understood that any one of the above schemes a, b, and c can be used. After scheme a or b is executed, step 770 can be executed without executing the steps of scheme c. Alternatively, the steps corresponding to scheme a or b do not need to be enhanced (that is, it is not necessary to instruct the first access network device to enable the traffic splitting rule in each step). For example, the specific steps can be found in [reference needed]. Figure 5 The description is as follows, and then the execution plan c is performed.

[0192] Step 780: The terminal sends uplink data to the first access network device.

[0193] Step 790: The first access network device sends uplink data to the first server based on the traffic splitting rules.

[0194] Because the first access network device enables traffic splitting rules, it can split uplink data based on these rules. For example, the first access network device might directly send a portion of the uplink data to the first server, while sending another portion via a UPF network element. Understandably, the first access network device can split uplink data based on the identifier of the PDU session or the identifier of the Quality of Service (QoS) flow. That is, it can split uplink data belonging to the same PDU session or QoS flow. For example, the first access network device might receive uplink data through a PDU session or QoS flow and, according to the splitting rules, send the uplink data directly to the first server; and / or send it via a UPF network element.

[0195] Step 7010: The first access network device determines the amount of uplink data (which may be referred to as the first uplink data) to be directly sent to the first server. The first access network device sends a third message to the SMF network element, which includes an indication of the amount of the first uplink data.

[0196] It is understandable that the first access network device can directly send a third message to the SMF network element, or it can send a third message to the SMF network element through the AMF network element, without restriction. In one description, "data volume" can also be referred to as "traffic". For example, the data volume of the first uplink data can be described as the traffic of the first uplink data.

[0197] Regarding the PDU session established above: In one understanding, during the inactivity timer of the PDU session, if the UPF network element does not detect data transmission of the PDU session, before requesting the SMF network element to release the PDU session, the UPF network element sends a fifth message to the first access network device. Alternatively, the UPF network element may periodically send a fifth message to the first access network device. This fifth message is used to detect whether the PDU session is in an active state, etc. The above process can be actively triggered by the UPF network element, as detailed in steps 7011 and 7012 below. Alternatively, the first access network device may actively report to the UPF network element whether the PDU session is in an active state, as detailed in step 7012 below.

[0198] Optionally, in step 7011: the UPF network element sends a fifth message (such as a release request message) to the first access network device, which is used to detect whether the PDU session is in an active state.

[0199] In one interpretation, an active PDU session means that data transmission is occurring, such as the first access network device directly sending the uplink data of the PDU session to the first server. An inactive PDU session means that no data transmission is occurring, such as the first access network device not directly sending the uplink data of the PDU session to the first server.

[0200] Step 7012: The first access network device sends a fourth message (such as a release response message) to the first network element. The fourth message is used to indicate that the PDU session is in an active state, or to indicate that the PDU session should not be released / prohibited.

[0201] In one possible implementation, if the first access network device enables the traffic splitting rule, the first access network device will periodically (e.g., periodically) or based on the fifth message to the first network element (e.g., release response). The fourth message can be an empty packet, forwarded uplink data, or a message that prohibits the release of connection resources, etc. The fourth message is used to indicate not to / prohibit the release of PDU sessions.

[0202] The solution described in Embodiment 1 addresses the issues of missed traffic statistics and user plane inactivity caused by the core network being unaware of the traffic offloading behavior of the first access network device. In Embodiment 1, the core network is aware that the first access network device has enabled traffic offloading rules. When the first access network device offloads uplink data based on these rules, it automatically calculates the amount of uplink data directly sent to the first server and reports this to the SMF network element, thus resolving the problem of inaccurate uplink data volume calculated by the UPF. Furthermore, before requesting the SMF network element to release the PDU session, the UPF network element queries the first access network device to determine whether to directly send the uplink data of the PDU session to the first access network device, thereby preventing the accidental release of the PDU session.

[0203]

Example 2

[0204] The difference between Embodiment 2 and Embodiment 1 is as follows: In Embodiment 1, the first access network device counts the amount of first uplink data it directly sends to the first server and reports it to the SMF network element. In Embodiment 2, the first access network device copies the first uplink data and sends the copied first uplink data to the UPF network element. The UPF network element counts the amount of first uplink data the first access network device directly sends to the first server based on this copied first uplink data. Figure 7 As shown, a flowchart is provided, including:

[0205] Step 810: The core network element senses that the first access network device has enabled the traffic splitting rule. For the specific process, please refer to the description of scheme a, scheme b or scheme c in Implementation Example 1.

[0206] Step 820: The terminal sends uplink data to the first access network device.

[0207] Step 830: The first access network device sends uplink data to the first server based on the traffic splitting rules.

[0208] For example, based on the traffic splitting rule, the first access network device directly sends a portion of the uplink data to the first server; the other portion of the uplink data is sent to the first server through the UPF network element. For ease of description, the uplink data that the first access network device directly sends to the first server is referred to as the first uplink data.

[0209] Step 840: The first access network device copies the first uplink data and sends the copied first uplink data to the UPF network element.

[0210] It is understandable that the replicated first uplink data is only used for data volume statistics and does not need to be forwarded. In one possible implementation, when the UPF network element receives a data packet, it determines that the replicated data packet cannot be forwarded based on the Internet Protocol (IP) address of the data packet. Therefore, it determines that the data packet is only used for data volume statistics and does not need to be forwarded. Alternatively, in another possible implementation, the first access network device may also send a third indication message to the UPF network element. This third indication message is used to indicate that the replicated first uplink data is used to determine the data volume of uplink data and does not need to be forwarded. This third indication message and the replicated first uplink data can be carried in the same message or in different messages, without restriction. Alternatively, the third indication message can be carried in the replicated first uplink data. For example, the replicated first uplink data can be encapsulated using the GTP-U protocol. The GTP-U header of the replicated first uplink data can adopt an enhanced design, such as adding an indication bit to the GTP-U header to indicate that the uplink data is only used for traffic statistics. Furthermore, if the aforementioned statistical data volume is used for billing, the first access network device can also send a fourth indication information to the UPF network element. This fourth indication information is used to indicate that the copied first uplink data is uplink data directly sent to the first server, and its corresponding rate can be #1, such as the corresponding 6G rate.

[0211] Step 850: The UPF network element determines the amount of uplink data to be sent to the first server and reports it to the SMF network element.

[0212] For example, the UPF network element receives the amount of first uplink data from the first access network device; the UPF network element determines the amount of uplink data sent to the first server through the UPF network element; the sum of the above two data amounts is the amount of uplink data sent by the first access network device to the first server; the UPF network element reports the amount of uplink data sent to the first server to the SMF network element.

[0213] In one possible implementation, when the UPF network element receives the first replicated uplink data, it can also determine that there is data transmission in the PDU session. The UPF network element will not request the SMF network element to release the PDU session, thereby solving the problem of erroneous release of the PDU session.

[0214] The above design primarily addresses the issue of the network side's inability to trust the traffic statistics reported by the first access network device. In Embodiment 2, the first access network device copies the first uplink data directly sent to the first server and sends it to the UPF network element, enabling the UPF network element to perform traffic statistics. This solves the problem of inaccurate traffic statistics from the UPF network element and, by placing the traffic statistics on the core network element (UPF), enhances the reliability of the traffic statistics results.

[0215]

Example 3

[0216] The core network can prevent erroneous deactivation of PDU sessions based on the core network control plane. Specifically, this can be achieved through the following solutions:

[0217] In the PDU session establishment or modification process, the second network element (such as the SMF network element) sends a second message to the first access network device. The second message is used to instruct the first access network device to enable the traffic splitting rule. The first access network device sends a first message to the second network element (such as the SMF network element). The first message is used to instruct the first access network device to successfully enable the rule. This embodiment three uses the PDU session modification process as an example for illustration. Instructing to enable the traffic splitting rule in the PDU session establishment process refers to the description of schemes a and b in embodiment one.

[0218] The SMF network element sends a sixth message to the UPF network element, which instructs the UPF network element to stop timing the inactivity time of the connection resource corresponding to the uplink data. Furthermore, during the operation of the inactivity timer, the UPF network element does not transmit data to the aforementioned connection resource. When the inactivity timer expires, the UPF network element will not request the SMF network element to release the corresponding connection resource, thereby resolving the issue of erroneous release of connection resources. For details, please refer to the following scheme a.

[0219] In another scheme, when the SMF network element receives the seventh message from the UPF network element, the seventh message is used to notify the UPF network element that the connection resource corresponding to the uplink data is inactive; the SMF network element does not release the connection resource, as described in scheme b below. It is understood that the connection resource corresponding to the uplink data can refer to the PDU session resource or the Quality of Service (QoS) flow resource corresponding to the uplink data. It is also understood that in the above embodiments one and two, which are mainly described using PDU session resources as an example, the PDU session resource used for transmitting uplink data can also be replaced with a QoS flow resource.

[0220] Among them, one of the above schemes a and b exists, that is, only one of schemes a or b can be executed.

[0221] like Figure 8 As shown, a flowchart is provided, including:

[0222] For example, based on the terminal's location and data network name (DNN), the SMF network element detects that the uplink data sent by the terminal may need to be offloaded. The SMF network element then sends an offload rule to the first access network device through the AMF network element. This offload rule instructs the first access network device to enable the offload rule. When the first access network device receives the offload rule, it enables the offload rule and sends a response message to the SMF network element through the AMF network element. This response message indicates that the offload rule was successfully enabled. For details, please refer to steps 1 to 3 below.

[0223] Step 910: The SMF network element discovers that the uplink data of the terminal may need to be offloaded, and the SMF network element sends a notification message of the offload rules to the AMF network element.

[0224] The notification message includes a traffic splitting rule, which instructs the first access network device to enable traffic splitting. Optionally, the notification message also includes a traffic statistics rule, which instructs the first access network device to perform traffic statistics. In one possible implementation, the notification message can be a Namf_Communication_N1N2 message transfer message. The traffic splitting rule can be a packet detection rule (PDR), and the traffic statistics rule can be a usage reporting rule (URR), which can be included in the PDR.

[0225] Step 920: The AMF network element sends an N2 PDU session request to the first access network device.

[0226] The N2 PDU session request includes a traffic splitting rule. When the first access network device receives this traffic splitting rule, it enables the traffic splitting rule. Optionally, the N2 PDU session request also includes a traffic statistics rule. When the first access network device receives this traffic statistics rule, it calculates the amount of uplink data it directly sends to the first server.

[0227] In one understanding, in the above Figure 5 In the process, the following description is adopted: A second network element (such as an SMF network element) sends a second message to a first access network device. The second message is used to instruct the first access network device to enable the traffic offloading rule. In the application embodiment, the second message can be understood as: the notification message of the aforementioned traffic offloading rule and the N2 PDU session request. It is understood that in the above description, the focus is on describing the second message including second indication information and / or the identifier of the traffic offloading rule, which is used to instruct the first access network device to enable the traffic offloading rule. Figure 9In the process, the second message may include a traffic splitting rule, which is used to implicitly indicate that the first access network device has successfully enabled the traffic splitting rule. It is understood that in the above description, "the second message includes the first indication information and / or the identifier of the traffic splitting rule" can be replaced with "the first message includes the traffic splitting rule".

[0228] Step 930: In response to the N2 PDU session request, the first access network device sends an N2 PDU session response to the AMF network element.

[0229] The N2 PDU session response includes a result, for example, indicating that the first access network device successfully enabled the traffic offloading rule. In one possible implementation, the N2 PDU session response includes second indication information and / or an identifier of the traffic offloading rule, which indicates that the first access network device successfully enabled the traffic offloading rule. Furthermore, the result also includes information indicating that the first access network device successfully enabled the traffic statistics rule.

[0230] Step 940: In response to the above notification message, the AMF network element sends a response message to the SMF network element.

[0231] The response message includes indications that the traffic splitting rule was successfully enabled. For example, the response may include second indications and / or the identifier of the traffic splitting rule. Furthermore, the response message may also include indications that the traffic statistics rule was successfully enabled.

[0232] Understandably, in Figure 5 In the process, the following description is adopted: The first access network device sends a first message to the second network element (such as the SMF network element), and the first message is used to indicate that the traffic splitting rule has been successfully enabled. In the embodiments of this application, the first message can be understood as the above-mentioned N2 PDU session response message.

[0233] Option a, step 950: The SMF network element learns that the first access device has successfully enabled the traffic splitting rule and sends a sixth message to the UPF network element. This sixth message instructs the UPF network element to disable the timer. For example, the timer can be an inactive timer. In one possible implementation, the sixth message includes indication information, and further, an identifier for the PDU session or a QoS flow. This indication information instructs the UPF network element to disable the timer for the PDU session or the QoS flow. Alternatively, the indication information instructs the first access network device to enable the traffic splitting rule, and the UPF network element disables the timer upon receiving this indication information. Alternatively, the indication information modifies the PDU session type to always-on, for example, changing the PDU session type to an always-on PDU session. Alternatively, the name of the sixth message can instruct the UPF network element to disable the timer, etc., without limitation.

[0234] It is understandable that when the UPF network element closes the inactive timer for the aforementioned PDU session or QoS stream, it will not request the SMF network element to release the PDU session or QoS connection resources when the inactive timer expires, thus avoiding the erroneous release of connection resources. Similarly, if the connection resource type of the aforementioned PDU session or QoS stream is changed to always running, then the connection resource will never be released.

[0235] Step 960: Continue the PDU session modification process.

[0236] Step 970: The terminal sends uplink data to the first access network device.

[0237] Step 980: The first access network device sends uplink data to the first server.

[0238] For example, based on the traffic splitting rules, the first access network device sends a portion of the uplink data directly to the first server, and sends the other portion of the uplink data to the first server through the first network element.

[0239] Step 990: The first access network device determines the amount of uplink data (referred to as the first uplink data) to be directly sent to the first server, and reports the amount of the first uplink data to the SMF network element through the AMF network element.

[0240] Case b, step 9010: The UPF network element sends the seventh message to the SMF network element.

[0241] For example, if a UPF network element does not transmit data during the operation of an inactive timer corresponding to a PDU session or QoS, it sends a seventh message to the SMF network element when the inactive timer expires. This seventh message is used to request the release of the PDU session or QoS stream. For example, the seventh message could be a resource release request, or as mentioned above. Figure 4 The N4 session report in the process. The seventh message may include the identifier of the PDU session or QoS flow. When the SMF network element receives the seventh message, it determines that the PDU session or QoS flow has a traffic splitting rule enabled. In this case, the SMF network element may not release the PDU session or QoS flow.

[0242] Step 9011: SMF network elements do not release connection resources such as PDU sessions or QoS streams that have enabled traffic splitting rules.

[0243] Through the above design, when the SMF network element discovers that the uplink data of the terminal needs to be offloaded, it instructs the first access network device to offload the uplink data according to the offloading rules. This solves the problems of traffic statistics omissions and user plane inactivity caused by the core network side not knowing the offloading behavior of the first access network device. Furthermore, since the core network can know that the first access network device has enabled the offloading rules, resource release will not be triggered for PDU sessions or QoS flows that have not received uplink data for a long time. Specifically, this can be achieved through scheme a above, where the SMF network element notifies the UPF network element to stop timing the inactivity timer for PDU sessions or QoS flows with offloading rules enabled, or the SMF network element, upon receiving a release request from the UPF network element, will not release the connection resources of PDU sessions or QoS flows with offloading rules enabled.

[0244] Example 4

[0245] During a DNS lookup, a second network element (such as an SMF network element) can detect when the first access network device has enabled traffic splitting rules. For example, before a terminal sends uplink data, it queries the DNS server for the IP address of the destination node for that uplink data. When the second network element (such as an SMF network element) receives the IP address of the destination node, it discovers that the destination node is directly connected to the first access network device. At this point, the second network element can determine that the first access network device has enabled traffic splitting rules.

[0246] It is understandable that in Example 4, Figure 1 In the communication system 1000 shown: the core network also includes an edge application server discovery function (EASDF) network element; the DN also includes a DNS server. For example, in one possible implementation:

[0247] The fourth network element can send an eighth message to the second network element. This eighth message includes the address of the first server, such as its IP address. The first server is directly connected to the first access network device. The second network element determines the traffic splitting rule enabled by the first access network device based on the first server address and the first access network device. This traffic splitting rule is used to split uplink data. It is understood that the second network element is a network element with session management capabilities, such as an SMF network element; the fourth network element is a network element with edge application server discovery capabilities, such as an EASDF network element.

[0248] Taking a network element where the first network element is a UPF network element, the second network element is an SMF network element, and the fourth network element is an EASDF network element as an example, such as Figure 9 As shown, a flowchart is provided, including:

[0249] Step 1001: The terminal sends a DNS query message to the EASDF network element.

[0250] For example, the DNS query message includes the fully qualified domain name (FQDN) of the destination node communicating with the terminal and the IP address of the terminal.

[0251] Step 1002: The EASDF network element sends a DNS notification message to the SMF network element.

[0252] For example, a DNS notification message includes the destination node's FQDN and the terminal's IP address. In one possible implementation, the DNS notification message can be a DNS context notification (Neasdf_DNSContext_Notify) message.

[0253] Step 1003: The SMF network element sends a DNS update message to the EASDF network element.

[0254] For example, when an SMF network element receives a DNS notification message, it determines the IP address of the first access network device based on the FQDN of the destination node and the IP address of the terminal included in the DNS notification message; the DNS update message includes the IP address of the first access network device. In one possible implementation, this DNS update message is a DNS context update (Neasdf_DNSContext_update) message, which includes a field, for example, named the edge configuration server (ECS) field (option), which includes the IP address of the first access network device.

[0255] Step 1004: The EASDF network element sends a DNS query message to the DNS server. The DNS query message includes the FQDN and the IP address of the first access network device.

[0256] For example, when a DNS server receives a DNS query message, it retrieves the FQDN and the IP address of the first access network device from the message. Based on these information, the DNS server determines the IP address of the destination node. For instance, the DNS server queries the IP address corresponding to a nearby FQDN of the first access network device; this IP address is the IP address of the destination node.

[0257] Step 1005: The DNS server sends a DNS response message to the EASDF network element, which includes the IP address of the destination node.

[0258] Step 1006: The EASDF network element sends a DNS notification message to the SMF network element, which includes the IP address of the destination node.

[0259] In one possible implementation, the aforementioned DNS notification message can be a DNS context query notification (Neasdf_DNSContext_Notify). When the SMF network element receives this DNS notification message, it obtains the IP address of the destination node. The SMF network element discovers that this destination node is directly connected to the first access network device. At this time, the SMF network element detects that the first access network device is implementing traffic splitting (or, as described, the first access network device has enabled traffic splitting rules). Alternatively, in another possible implementation, the aforementioned DNS notification message includes a list of destination nodes, which includes the IP addresses of at least one destination node. The SMF network element selects an IP address of a destination node from this list. The destination node selected by the SMF network element is directly connected to the first access network device. At this time, the SMF network element detects that the first access network device is implementing traffic splitting (or, as described, the first access network device has enabled traffic splitting rules).

[0260] When the SMF network element detects that the first access network device has enabled traffic splitting rules, the SMF network element can adopt the following two schemes to avoid accidentally releasing the connection resources corresponding to the PDU session or quality of service flow. For example, in scheme a, the SMF network element can notify the UPF network element to close the inactive timer of the UPF session or quality of service flow, as explained in step 1007. Alternatively, in scheme b, when the SMF network element receives a request from the UPF network element to release the PDU session or quality of service flow, it does not release the connection resources of that PDU session or quality of service flow, as explained in steps 1012 and 1013.

[0261] Step 1007: The SMF network element sends a sixth message to the UPF network element. This sixth message is used to instruct the UPF network element to turn off the timer. (See reference...) Figure 9 The explanation of step 950 in the text.

[0262] Step 1008: Continue the edge application server (EAS) discovery process.

[0263] Step 1009: The terminal sends uplink data to the first access network device.

[0264] Step 1010: The first access network device sends uplink data to the first server.

[0265] For example, based on the traffic splitting rules, the first access network device sends a portion of the uplink data directly to the first server, and sends the other portion of the uplink data to the first server through the first network element.

[0266] Step 1011: The first access network device determines the amount of uplink data (referred to as the first uplink data) to be directly sent to the first server, and reports the amount of the first uplink data to the SMF network element through the AMF network element.

[0267] Case b, step 1012: The UPF network element sends the seventh message to the SMF network element.

[0268] For example, if the UPF network element does not transmit data during the operation of the inactivity timer corresponding to the PDU session or QoS, then when the inactivity timer expires, the UPF network element sends a seventh message to the SMF network element. This seventh message is used to request the release of the PDU session or QoS stream. For details, please refer to the description of step 9010.

[0269] Step 1013: SMF network elements do not release connection resources such as PDU sessions or QoS streams that have enabled traffic splitting rules.

[0270] Through the above design, the SMF network element can detect when the first access network device has enabled traffic offloading rules, thus resolving issues such as missed traffic statistics and user plane inactivity caused by the core network being unaware of the traffic offloading behavior of the first access network device. For example, before sending uplink data, the terminal queries the DNS server for the IP address of the destination node. When the destination node returned by the DNS server is directly connected to the first access network device, the SMF network element can detect that the first access network device has enabled traffic offloading rules, thereby preventing the release of the PDU session or QoS flow.

[0271] In the embodiments provided above, the methods provided by this application are described from the perspective of the interaction between the first access network device and the core network element. To implement the functions of the methods provided in the embodiments of this application, the first access network device or the core network element 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 executed 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.

[0272] Based on the same concepts as the above-described method embodiments Figure 10 and Figure 11 This is a schematic diagram of the possible communication devices provided in the embodiments of this application. These communication devices can realize the functions implemented by the first access network device or core network element in the above method embodiments, and therefore may achieve the beneficial effects of the above method embodiments. In the embodiments of this application, the communication device may be a first access network device or core network element, or a unit, module, or component (such as a chip, chip system, circuit, processor, or others) applied in the first access network device or core network element. In the following description, the term "unit" is 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.

[0273] like Figure 10 As shown, the communication device 10000 includes a processing unit 10010 and a transceiver unit 10020. The communication device 10000 is used to implement the functions of the first access network device or the second network element in the above method flow.

[0274] Optionally, the transceiver unit 10020 may also be referred to as an output unit, an interface unit, or a communication unit, etc. In one possible implementation, the transceiver unit 10020 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.

[0275] In one possible implementation, the communication device 10000 is used to implement... Figure 4 , Figure 6 , Figure 7 or Figure 8 Functions, such as:

[0276] When communication device 10000 is used to achieve Figure 4 , Figure 6 , Figure 7 or Figure 8Specifically, the first access network device functions as follows: a processing unit 10010 is used to enable a traffic splitting rule, which is used to split uplink data; a transceiver unit 10020 is used to send a first message to a second network element, which is a network element with session management function, and the first message is used to instruct the first access network device to enable the traffic splitting rule.

[0277] In one possible implementation, the first message includes: first indication information and / or the identifier of the traffic splitting rule, wherein the first indication information is used to instruct the first access network device to enable the traffic splitting rule.

[0278] In one possible implementation, enabling the traffic splitting rule includes: receiving a second message from the second network element, the second message being used to instruct the first access network device to enable the traffic splitting rule; and enabling the traffic splitting rule according to the instruction of the second message.

[0279] In one possible implementation, the second message includes: second indication information and / or the identifier of the traffic splitting rule, wherein the second indication information is used to instruct the first access network device to enable the traffic splitting rule.

[0280] In one possible implementation, the processing unit 10010 is further configured to determine the amount of first uplink data to be directly sent to the first server; the transceiver unit 10020 is further configured to send a third message to the second network element, the third message being used to indicate the amount of the first uplink data.

[0281] In one possible implementation, the processing unit 10010 is further configured to copy the first uplink data, which is the uplink data sent by the first access network device to the first server; the transceiver unit 10020 is further configured to send the copied first uplink data to the first network element, wherein the copied first uplink data is used by the first network element to determine the amount of uplink data sent by the first access network device to the first server, or to determine by the first network element that the connection resource corresponding to the uplink data is in an active state.

[0282] In one possible implementation, the transceiver unit 10020 is further configured to send third indication information to the first network element, the third indication information being used to indicate that the copied first uplink data is used to determine the amount of uplink data sent by the first access network device to the first server.

[0283] In one possible implementation, the transceiver unit 10020 is further configured to send a fourth message to the first network element, the fourth message being used to indicate that the connection resource corresponding to the uplink data is in an active state.

[0284] In one possible implementation, the transceiver unit 10020 is further configured to receive a fifth message from the first network element, wherein the fourth message is used to inquire whether the connection resource corresponding to the uplink data of the first access network device is in an active state.

[0285] When communication device 10000 is used to achieve Figure 4 , Figure 6 , Figure 7 or Figure 8 When discussing the functions of the second network element (or SMF network element), the specifics are as follows:

[0286] The transceiver unit 10020 is used to receive a first message from the first access network device, the first message being used to instruct the first access network device to enable traffic splitting rules.

[0287] In one possible implementation, the first message includes: first indication information and / or the identifier of the traffic splitting rule, wherein the first indication information is used to instruct the first access network device to enable the traffic splitting rule.

[0288] In one possible implementation, the transceiver unit 10020 is further configured to send a second message to the first access network device, the second message being used to instruct the first access network device to enable the traffic splitting rule.

[0289] In one possible implementation, the second message includes: second indication information and / or the identifier of the traffic splitting rule, wherein the second indication information is used to instruct the first access network device to enable the traffic splitting rule.

[0290] In one possible implementation, the transceiver unit 10020 is further configured to receive a third message from the first access network device, the third message being used to indicate the amount of first uplink data, the first uplink data being uplink data directly sent by the first access network device to the first server.

[0291] In one possible implementation, the transceiver unit 10020 is further configured to send a sixth message to the first network element, the sixth message being used to instruct the first network element to stop timing the inactivity time of the connection resource corresponding to the uplink data.

[0292] In one possible implementation, the transceiver unit 10020 is further configured to receive a seventh message from the first network element, the seventh message being used to notify the second network element that the connection resources corresponding to the uplink data are inactive.

[0293] When communication device 10000 is used to achieve Figure 9 When discussing the function of the second network element (such as the SMF network element), the specific details are as follows:

[0294] The transceiver unit 10020 is used to receive an eighth message from a fourth network element, wherein the fourth network element is a network element with edge application server discovery function, and the eighth message includes the address of a first server, wherein the first server is directly connected to the first access network device; the processing unit 10010 is used to determine that the first access network device enables a traffic splitting rule, wherein the traffic splitting rule is used to split uplink data.

[0295] like Figure 11 As shown, the communication device 1100 includes a processor 1110 and an interface circuit 1120. The processor 1110 and the interface circuit 1120 are coupled to each other. It is understood that the interface circuit 1120 can be a transceiver or an input / output interface. Optionally, the communication device 11000 may also include a memory 1130 for storing instructions executed by the processor 1110, or storing input data required by the processor 1110 to execute instructions, or storing data generated after the processor 1110 executes instructions.

[0296] When the communication device 11000 is used to implement Figure 4 , Figure 6 , Figure 7 , Figure 8 or Figure 9 In the method shown, processor 1110 is used to implement the functions of the processing unit 10010, and interface circuit 1120 is used to implement the functions of the transceiver unit 10020.

[0297] When the aforementioned communication device is a module applied to a first access network device, the module implements the functions of the first access network device in the above method embodiments. Taking the first access network device as an example: the module receives information from other modules (such as radio frequency modules or antennas) in the first access network device, and this information is sent to the first access network device by the second network element; or, the module sends information to other modules (such as radio frequency modules or antennas) in the first access network device, and this information is sent to the second network element by the first access network device. Here, the module of the first access network device can be a chip of the first access network device, or a DU or other modules. Here, the DU can be a DU under the O-RAN architecture.

[0298] When the aforementioned communication device is a chip applied to the second network element, the chip implements the functions of the second network element in the above method embodiments. The chip receives information sent to the second network element by the first access network device through other modules (such as radio frequency modules or antennas) in the second network element; or, the chip sends information to other modules (such as radio frequency modules or antennas) in the second network element, which is information sent by the second network element to the first access network device.

[0299] This application also provides a communication device, which includes a processor for implementing the above-described embodiments. Figure 4 , Figure 6 , Figure 7 , Figure 8 or Figure 9 The communication device includes a memory, a processor coupled to the memory, and a processor for executing computer programs or instructions stored in the memory to implement the above-mentioned functions. Figure 4 , Figure 6 , Figure 7 , Figure 8 or Figure 9 The communication device can be a chip or a chip system. It can also function as the first access network device or the second network element.

[0300] This application 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 implements the above through logic circuits or executable code instructions. Figure 4 , Figure 6 , Figure 7 , Figure 8 or Figure 9 The function of the first access network device or the second network element.

[0301] 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 aforementioned... Figure 4 , Figure 6 , Figure 7 , Figure 8 or Figure 9 The function of the first access network device or the second network element.

[0302] This application also provides a computer program product, including a computer program or instructions, which, when run on a computer, implement the above-described functionality. Figure 4 , Figure 6 , Figure 7 , Figure 8 or Figure 9 The function of the first access network device or the second network element.

[0303] 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.

[0304] 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.

[0305] 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.

[0306] 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.

[0307] 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 a first access network device, which is directly connected to a first server, and the first access network device is connected to the first server through a first network element, wherein the first network element is a network element with user plane functionality. The method includes: Enable traffic splitting rules, which are used by the first access network device to split uplink data; A first message is sent to a second network element, which is a network element with session management function. The first message is used to instruct the first access network device to enable the traffic splitting rule.

2. The method as described in claim 1, characterized in that, The first message includes: first indication information and / or the identifier of the traffic splitting rule, wherein the first indication information is used to instruct the first access network device to enable the traffic splitting rule.

3. The method as described in claim 1 or 2, characterized in that, The enabled traffic splitting rules include: Receive a second message from the second network element, the second message being used to instruct the first access network device to enable the traffic splitting rule; The traffic splitting rule is activated according to the instructions in the second message.

4. The method as described in claim 3, characterized in that, The second message includes: second indication information and / or the identifier of the traffic splitting rule, wherein the second indication information is used to instruct the first access network device to enable the traffic splitting rule.

5. The method according to any one of claims 1 to 4, characterized in that, Also includes: Determine the amount of the first uplink data to be directly sent to the first server; A third message is sent to the second network element, the third message being used to indicate the amount of data in the first uplink data.

6. The method according to any one of claims 1 to 4, characterized in that, Also includes: Copy the first uplink data, which is the uplink data sent by the first access network device to the first server; The first network element sends a copy of the first uplink data, which is used by the first network element to determine the amount of uplink data sent by the first access network device to the first server, or to determine by the first network element that the connection resource corresponding to the uplink data is active.

7. The method as described in claim 6, characterized in that, Also includes: A third indication message is sent to the first network element, the third indication message being used to indicate that the copied first uplink data is used to determine the amount of uplink data sent by the first access network device to the first server.

8. The method according to any one of claims 1 to 7, characterized in that, Also includes: A fourth message is sent to the first network element, the fourth message being used to indicate that the connection resource corresponding to the uplink data is in an active state.

9. The method as described in claim 8, characterized in that, Also includes: The system receives a fifth message from the first network element, wherein the fourth message is used to inquire whether the connection resources corresponding to the uplink data of the first access network device are in an active state.

10. A communication method, characterized in that, The method is applied to a second network element, which is a network element with session management functions, including: Receive a first message from the first access network device, the first message being used to instruct the first access network device to enable traffic splitting rules.

11. The method as described in claim 10, characterized in that, The first message includes: first indication information and / or the identifier of the traffic splitting rule, wherein the first indication information is used to instruct the first access network device to enable the traffic splitting rule.

12. The method as described in claim 10 or 11, characterized in that, Also includes: A second message is sent to the first access network device, the second message being used to instruct the first access network device to enable the traffic splitting rule.

13. The method as described in claim 12, characterized in that, The second message includes: second indication information and / or the identifier of the traffic splitting rule, wherein the second indication information is used to instruct the first access network device to enable the traffic splitting rule.

14. The method according to any one of claims 10 to 13, characterized in that, Also includes: A third message is received from the first access network device, the third message being used to indicate the amount of first uplink data, the first uplink data being the uplink data directly sent by the first access network device to the first server.

15. The method according to any one of claims 10 to 14, characterized in that, Also includes: A sixth message is sent to the first network element, the sixth message being used to instruct the first network element to stop timing the inactivity time of the connection resource corresponding to the uplink data.

16. The method according to any one of claims 10 to 14, characterized in that, Also includes: A seventh message is received from the first network element, the seventh message being used to notify the second network element that the connection resources corresponding to the uplink data are inactive.

17. A communication method, characterized in that, The method is applied to a second network element, which is a network element with session management functions, including: The system receives an eighth message from a fourth network element, which is a network element with edge application server discovery function. The eighth message includes the address of a first server, which is directly connected to a first access network device. The first access network device is determined to enable a traffic splitting rule, which is used to split uplink data.

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

19. A communication device, characterized in that, Includes a processor configured to cause the communication device to perform the method as described in any one of claims 1 to 9.

20. A communication device, characterized in that, Includes units for implementing the method as described in any one of claims 10 to 17.

21. A communication device, characterized in that, Includes a processor configured to cause the communication device to perform the method as described in any one of claims 10 to 17.

22. 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 9, or the method as described in any one of claims 10 to 17.

23. 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 9, or the method as described in any one of claims 10 to 17.

Images