Communication methods, communication devices and communication systems

Abstract

A communication method, communication device, and communication system are disclosed, relating to the field of communication technology. In this method, a serving session function (SSF) network element triggers a local session function (LSF) network element to create a first session for a first device. This first session is different from a second session already created for the first device by an anchor session function (ASP) network element. The SSF network element sends information to the ASP network element instructing the first device to request the creation of a Quality of Service (QoS) flow for the first session. Based on this information, the ASP network element allocates a Quality of Service Flow (QFI) for the first session's QoS flow. This QFI is different from the QFI allocated by the ASP network element for the second session's QoS flow. The SSF network element then sends this QFI to the first device. Through this method, the first device obtains QFIs belonging to multiple sessions. Different QFIs can distinguish different QoS flows, thereby achieving differentiated QoS assurance when the first device accesses different networks through the first and second sessions.

Description

Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a communication method, communication device, and communication system. Background Technology

[0002] A Protocol Data Unit (PDU) session defines the logical connection between a terminal device and an external data network, providing an end-to-end data transmission channel. For example, a PDU session can provide a data transmission channel for a terminal device to access the Internet or a corporate intranet.

[0003] Fifth generation (5) th The 5G core network can create multiple quality of service (QoS) flows for a single PDU session. Different QoS flows can be distinguished by a quality of service identifier (QFI) and each corresponds to a specific set of QoS parameters, thereby meeting the QoS requirements of different applications or services. In other words, the 5G core network can meet the QoS differentiation guarantee requirements of a single PDU session.

[0004] When the 5G core network establishes multiple PDU sessions for a terminal device simultaneously, the terminal device can access different networks through different PDU sessions. For example, the terminal device can access a public network through PDU session 1 and a private network through PDU session 2. However, the existing 5G core network cannot provide differentiated QoS guarantees for these multiple PDU sessions. Summary of the Invention

[0005] This application provides a communication method, communication device, and communication system that can provide QoS differentiation guarantees for multiple sessions of a user.

[0006] Firstly, a communication method is provided. This method can be executed by a service session function network element, or by a module (such as a chip system) within the service session function network element, or by a logical node, logical module, or software capable of implementing all or part of the functions of the service session function network element. For ease of description, the following description uses a service session function network element as an example. The method includes: a serving session function network element sending session creation request information to a local session function network element, the session creation request information being used to request the local session function network element to create a first session for a first device, the first session being different from a second session already created for the first device by an anchor session function network element; the serving session function network element receiving session creation response information from the local session function network element, the session creation response information being used to instruct the first device to create a QoS flow for the first session, the session creation response information including a first QFI allocated by the local session function network element for the QoS flow; the serving session function network element sending a first session modification request information to the anchor session function network element, the first session modification request information being used to instruct the first device to request the creation of the QoS flow, the first session modification request information including a third QFI allocated by the serving session function network element for the QoS flow, the third QFI being 0, 0 being used to request the anchor session function network element to allocate a QFI for the QoS flow; and the serving session function network element receiving a first session modification command information from the anchor session function network element, the first session modification command information being used to instruct the first device to create the QoS flow. The first session modification command information includes the second QFI allocated by the anchor session function network element for the QoS flow, which is different from the QFI allocated by the anchor session function network element for the QoS flow of the second session; the service session function network element sends QoS flow creation information to the first device, which is used to instruct the first device to create the QoS flow, and the QoS flow creation information includes the second QFI.

[0007] After the anchor session function network element has created a second session for the first device, it assigns different QFIs to different QoS flows within the second session. For example, the anchor session function network element assigns QFI=1 to QoS flow1 and QFI=2 to QoS flow2. When the serving session function network element determines that the first device has a service offloading requirement (i.e., it determines that the first device needs to access different networks through different sessions), the serving session function network element triggers the local session function network element to create a first session for the first device and sends a first session modification request to the anchor session function network element. The anchor session function network element then assigns a second QFI to the QoS flow of the first session based on the first session modification request. This second QFI is different from the QFI assigned by the anchor session function network element to the QoS flow of the second session, such as second QFI=3. The first device participates in the creation process of the second session but is unaware of the creation process of the first session.

[0008] Using the above method, under the premise that the anchor session function network element has created a second session for the first device, the service session function network element triggers the local session function network element to create a first session for the first device, and sends the second QFI allocated by the anchor session function network element for the QoS flow of the first session to the first device. The second QFI is different from the QFI allocated by the anchor session function network element for the QoS flow of the second session. This can support the first device to obtain the QFI of the QoS flow belonging to multiple sessions. Different QFIs distinguish different QoS flows, thereby realizing the differentiated QoS guarantee when the first device accesses different networks through the first session and the second session.

[0009] In some implementations of the first aspect, when the session creation response information includes a first filter parameter indicating access to any target address, the first session modification request information also includes a second filter parameter indicating access to the target address corresponding to the first session. This ensures that the anchor session function network element and the service session function network element maintain consistency regarding the target address information of the first session.

[0010] In some implementations of the first aspect, the method further includes: the service session function network element storing the mapping relationship between the first QFI and the second QFI. After the service session function network element stores the mapping relationship between the first QFI and the second QFI, the service session function network element can manage the QoS flow of the first session according to the mapping relationship, such as updating the QoS flow of the first session or deleting the QoS flow of the first session.

[0011] In some implementations of the first aspect, the method further includes: the serving session function network element sending a mapping relationship between the first QFI and the second QFI to the serving user plane function network element. This mapping relationship is used by the serving user plane function network element to forward data transmitted by the first device through the QoS to the local user plane function network element. After the serving session function network element sends the mapping relationship between the first QFI and the second QFI to the serving user plane function network element, this enables the serving user plane function network element to forward data transmitted by the first device through the QoS flow of the first session to the corresponding local user plane function network element according to the mapping relationship, thereby enabling the local user plane function network element to perform forwarding processing on the data of the first device.

[0012] In some implementations of the first aspect, the method further includes: the serving session function network element receiving first QoS flow modification information from the local session function network element, the first QoS flow modification information including a first QFI, the first QoS flow modification information being used to instruct the first device to update the QoS parameters of the QoS flow; the serving session function network element sending second QoS flow modification information to the first device according to the mapping relationship between the first QFI and the second QFI, the second QoS flow modification information including a second QFI, the second QoS flow modification information being used to instruct the first device to update the QoS parameters of the QoS flow. Through the above process, the serving session function network element can complete the update management of the QoS flow of the first session according to the aforementioned mapping relationship, thereby achieving synchronization of the update management of the QoS flow of the first session between the first device and the local session function network element.

[0013] In some implementations of the first aspect, before the serving session function network element sends the second QoS flow modification information to the first device, the method further includes: the serving session function network element sending a second session modification request message to the anchor session function network element according to the mapping relationship; the second session modification request message including a second QFI, the second session modification request message being used to instruct the first device to request an update of the QoS parameters of the QoS flow; the serving session function network element receiving a second session modification command message from the anchor session function network element, the second session modification command message being used to instruct the first device to update the QoS parameters of the QoS flow. Through the above process, synchronization between the serving session function network element and the anchor session function network element in the update management of the QoS flow of the first session can be achieved.

[0014] In some implementations of the first aspect, the method further includes: the serving session function network element receiving first QoS flow deletion information from the local session function network element, the first QoS flow deletion information including a first QFI, the first QoS flow deletion information being used to instruct the first device to delete the QoS flow; the serving session function network element sending second QoS flow deletion information to the first device according to the mapping relationship between the first QFI and the second QFI, the second QoS flow deletion information including a second QFI, the second QoS flow deletion information being used to instruct the first device to delete the QoS flow. Through the above process, the serving session function network element can complete the deletion management of the QoS flow of the first session according to the aforementioned mapping relationship, thereby achieving synchronization between the first device and the local session function network element in the deletion management of the QoS flow of the first session.

[0015] In some implementations of the first aspect, before the serving session function network element sends the second QoS flow deletion information to the first device, the method further includes: the serving session function network element sending a third session modification request information to the anchor session function network element according to the mapping relationship; the third session modification request information includes the second QoS FI and is used to instruct the first device to request the deletion of the QoS flow; the serving session function network element receiving a third session modification command information from the anchor session function network element, the third session modification command information being used to instruct the first device to delete the QoS flow. Through the above process, synchronization between the serving session function network element and the anchor session function network element in the deletion management of the QoS flow in the first session can be achieved.

[0016] In some implementations of the first aspect, the method further includes: the serving session function network element sending session deletion information to the local session function network element, the session deletion information being used to instruct the local session function network element to delete the first session; the serving session function network element sending third QoS flow deletion information to the first device according to the mapping relationship between the first QFI and the second QFI, the third QoS flow deletion information including the second QFI, the third QoS flow deletion information being used to instruct the first device to delete the QoS flow. Through the above process, the serving session function network element can complete the deletion management of the QoS flow of the first session according to the aforementioned mapping relationship, thereby achieving synchronization between the first device and the local session function network element in the deletion management of the QoS flow of the first session.

[0017] In some implementations of the first aspect, before the serving session function network element sends the third QoS flow deletion information to the first device, the method further includes: the serving session function network element sending a fourth session modification request information to the anchor session function network element according to the mapping relationship; the fourth session modification request information includes a second QFI and is used to instruct the first device to request the deletion of the QoS flow; the serving session function network element receiving a fourth session modification command information from the anchor session function network element, the fourth session modification command information being used to instruct the first device to delete the QoS flow. Through the above process, synchronization between the serving session function network element and the anchor session function network element in the deletion management of the QoS flow in the first session can be achieved.

[0018] In some implementations of the first aspect, the method further includes: a serving session function (SSC) network element receiving context acquisition request information from a target SSC network element, the context acquisition request information being used to request the mapping relationship between the first QFI and the second QFI; the SSC network element sending the mapping relationship to the target SSC network element; the SSC network element being a source SSC network element serving the first device. When the first device executes a SSC network element handover procedure, the source SSC network element sends the mapping relationship between the first QFI and the second QFI to the target SSC network element through the above procedure, thereby enabling the target SSC network element to manage the QoS flow of the first session according to the mapping relationship between the first QFI and the second QFI, thus ensuring the continuity of QoS flow management for the first session.

[0019] In some implementations of the first aspect, the method further includes: the serving session function network element receiving a fifth session modification command message from the anchor session function network element, the fifth session modification command message including a second QFI, the fifth session modification command message being used to instruct the first device to delete the QoS flow; the serving session function network element sending fourth QoS flow deletion information to the local session function network element according to the mapping relationship between the first QFI and the second QFI, the fourth QoS flow deletion information including the first QFI, the fourth QoS flow deletion information being used to instruct the local session function network element to delete the QoS flow; the serving session function network element sending fifth QoS flow deletion information to the first device, the fifth QoS flow deletion information including the second QFI, the fifth QoS flow deletion information being used to instruct the first device to delete the QoS flow. Through the above process, the serving session function network element can complete the deletion management of the QoS flow of the first session according to the aforementioned mapping relationship, thereby achieving synchronization between the first device and the local session function network element in the deletion management of the QoS flow of the first session.

[0020] Secondly, a communication system is provided, including: a serving session function network element and an anchor session function network element. The serving session function network element is configured to: send session creation request information to a local session function network element, the session creation request information requesting the local session function network element to create a first session for a first device, the first session being different from a second session already created for the first device by the anchor session function network element; receive session creation response information from the local session function network element, the session creation response information instructing the first device to create a QoS flow for the first session, the session creation response information including a first QFI allocated by the local session function network element for the QoS flow; and send a first session modification request information to the anchor session function network element, the first session modification request information instructing the first device to request the creation of the QoS flow, the first session modification request information including a third QFI allocated by the serving session function network element for the QoS flow, the third QFI being 0, and 0 being used to request the anchor session function network element to allocate a QFI for the QoS flow. The anchor session function network element is used to: receive a first session modification request; allocate a second QFI for the QoS flow according to the third QFI; and send a first session modification command to the serving session function network element, wherein the first session modification command is used to instruct the first device to create the QoS flow, and the first session modification information includes the second QFI; the serving session function network element is also used to: receive the first session modification command; and send QoS flow creation information to the first device, wherein the QoS flow creation information is used to instruct the first device to create the QoS flow, and the QoS flow creation information includes the second QFI.

[0021] For further descriptions of the service session function network elements in the above communication system, please refer to the relevant descriptions in the first part, which will not be repeated here.

[0022] For a description of the beneficial effects of the aforementioned communication system, please refer to the description of the beneficial effects in the first aspect.

[0023] In some implementations of the second aspect, the communication system further includes: a serving user plane function network element, used to receive the mapping relationship between the first QFI and the second QFI; and according to the mapping relationship, forwarding the data transmitted by the first device through the QoS flow to the local user plane function network element.

[0024] Thirdly, a communication device is provided, which may be the aforementioned service session function network element, and the communication device is used to perform the method described in the first aspect or any implementation thereof.

[0025] One possible implementation is that the communication device may include modules or units corresponding to the methods / operations / steps / actions described in the first aspect or any implementation of the first aspect. These modules or units may be hardware circuits, software, or a combination of hardware circuits and software.

[0026] For example, the communication device includes a transceiver unit and a processing unit.

[0027] Fourthly, a communication device is provided, including a processor, which is configured to cause the communication device to perform the above-described method by executing a computer program or instructions, or by means of logic circuitry.

[0028] In one possible implementation, the communication device also includes a memory for storing the computer program or instructions.

[0029] In one possible implementation, the communication device also includes a communication interface for inputting and / or outputting signals.

[0030] One possible implementation is that the communication device can also be a chip or a chip system.

[0031] Fifthly, a communication device is provided, including logic circuitry and an input / output interface, the input / output interface being used for inputting and / or outputting signals, and the logic circuitry being used for performing the methods described above.

[0032] One possible implementation is that the communication device can also be a chip or a chip system.

[0033] In a sixth aspect, a computer-readable storage medium is provided, on which a computer program or instructions are stored, which, when executed on a computer, cause the above-described method to be performed.

[0034] In a seventh aspect, a computer program product is provided, comprising instructions that, when executed on a computer, cause the above-described methods to be performed.

[0035] Eighthly, a chip or chip system is provided, comprising: one or more processors for executing computer programs or instructions in the memory, such that the chip or chip system implements the above-described method.

[0036] Ninthly, a chip is provided that is installed in a communication device. The chip includes a processor and a communication interface. The processor reads and executes instructions through the communication interface, causing the communication device to perform the above-described method.

[0037] For a description of the beneficial effects of any of the second to ninth aspects, please refer to the description of the beneficial effects of the first aspect, which will not be repeated here. Attached Figure Description

[0038] Figure 1 This is a schematic diagram of the architecture of an applicable communication system according to an embodiment of this application.

[0039] Figure 2 yes Figure 1 The diagram shows a communication system applied to a network architecture.

[0040] Figure 3 yes Figure 1 The diagram shows a communication system applied to another network architecture.

[0041] Figure 4 This is a schematic diagram of the interaction flow of a communication method according to an embodiment of this application.

[0042] Figure 5 This is a schematic diagram of the interaction flow of another communication method according to an embodiment of this application.

[0043] Figure 6 This is a schematic diagram of the interaction flow of another communication method according to an embodiment of this application.

[0044] Figure 7 This is a schematic diagram of the interaction flow of another communication method according to an embodiment of this application.

[0045] Figure 8 This is a schematic diagram of the interaction flow of another communication method according to an embodiment of this application.

[0046] Figure 9 This is a schematic diagram of the interaction flow of another communication method according to an embodiment of this application.

[0047] Figure 10 This is a schematic diagram of the interaction flow of another communication method according to an embodiment of this application.

[0048] Figure 11 This is a schematic block diagram of a communication device according to an embodiment of this application.

[0049] Figure 12 This is a schematic block diagram of another communication device according to an embodiment of this application. Detailed Implementation

[0050] To facilitate understanding of the embodiments of this application, the following points will be explained first.

[0051] 1. Unless otherwise stated, "multiple" means two or more. "At least one" means "one or more".

[0052] 2. Unless otherwise specified or in case of logical conflict, the terms and / or descriptions in different embodiments of this application are consistent and can be referenced in each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0053] III. The various numerical designations used in this application are merely for descriptive convenience and are not intended to limit the scope of protection of this application. The magnitude of the serial numbers used in this application does not imply a sequential order of execution; the execution order of each process should be determined by its function and internal logic. For example, the terms "first," "second," and other various terminology (if present) in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. Where appropriate, such data can be interchanged so that the embodiments described herein can be implemented in a sequence other than that illustrated or described herein.

[0054] Furthermore, any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner for ease of understanding.

[0055] IV. The terms “comprising” and “having” and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are expressly listed, but may include other steps or units that are not expressly listed or that are inherent to such process, method, product or device.

[0056] V. In this application, "for indicating" can be understood as "enabling", and "enabling" includes direct enabling and indirect enabling. When describing information for enabling A, it may include whether the information directly enables A or indirectly enables A, but it does not mean that the information necessarily carries A.

[0057] The information that enables the information is called the information to be enabled. In the specific implementation process, there are many ways to enable the information to be enabled, such as, but not limited to, directly enabling the information to be enabled, such as the information to be enabled itself or its index. It can also be indirectly enabled by enabling other information, where there is a relationship between the other information and the information to be enabled. It can also enable only a part of the information to be enabled, while the other parts are known or pre-agreed upon. For example, enabling specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing enabling overhead to some extent. Simultaneously, common parts of various pieces of information can be identified and enabled uniformly to reduce the enabling overhead caused by individually enabling the same information.

[0058] In addition, "instruction" can include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing a certain instruction information to indicate A, it can be understood that the instruction information carries A, directly indicates A, or indirectly indicates A.

[0059] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is a relationship between the other information and the information to be instructed. It can also indicate only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. Furthermore, the information to be instructed can be sent as a whole or divided into multiple sub-information pieces, and the sending period and / or timing of these sub-information pieces can be the same or different.

[0060] VI. The term "storage" or "preservation" in this application can refer to storage in one or more memory devices. These memory devices can be separately configured or integrated into an encoder, decoder, processor, or communication device. Alternatively, some memory devices can be separately configured, while others can be integrated into a decoder, processor, or communication device. The type of memory can be any form of storage medium, and this is not limited.

[0061] VII. The arrows or boxes indicated by dashed lines in the schematic diagrams in the accompanying drawings of this application represent optional steps or optional modules.

[0062] 8. In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which may include direct transmission via the air interface or indirect transmission by other units or modules via the air interface. "Receive information from YY" can be understood as the source of the information being YY, which may include direct reception from YY via the air interface or indirect reception from YY by other units or modules via the air interface. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface. In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.

[0063] The following sections describe the communication system, communication method, and communication device.

[0064] Figure 1 This is a schematic diagram of the architecture of a communication system applicable to embodiments of this application. For example... Figure 1 As shown, the communication system includes: a service session function network element, an anchor session function network element, and a local session function network element. Optionally, the communication system further includes a service user plane function network element, which interacts with the service session function network element. Optionally, the communication system further includes a local user plane function network element, which interacts with the local session function network element. Optionally, the communication system further includes a first device, which may include a terminal device, an access-side device, or both; the specific inclusion of the first device is not limited.

[0065] Service session function network elements are used to perform global policy control and coordination, and end-to-end session management functions. Anchor session function network elements are used to manage PDU session anchor points, ensure the stability of Internet Protocol (IP) addresses, and ensure wide-area service continuity; they are deployed at the core network central node. Local session function network elements are used to perform localized traffic offloading and optimize edge service latency; they are deployed at edge nodes.

[0066] Service user plane function network elements are used to perform functions such as packet routing and forwarding. Their deployment location is flexible; they can handle centralized traffic at central nodes or provide low-latency services at edge nodes. Local user plane function network elements are used to perform functions such as local traffic offloading and resource isolation for services. They are deployed close to the user or enterprise site.

[0067] An example of a service session function network element is the service session management function (S-SMF) in the 5G core network, or it can be an entity with the same or similar function as the S-SMF in future communication networks. An example of an anchor session function network element is the anchor session management function (A-SMF) in the 5G core network, or it can be an entity with the same or similar function as the A-SMF in future communication networks. An example of a local session management function network element is the local session management function (L-SMF) in the 5G core network, or it can be an entity with the same or similar function as the L-SMF in future communication networks. An example of a service user plane function network element is the service user plane function (S-UPF) in the 5G core network, or it can be an entity with the same or similar function as the S-UPF in future communication networks. An example of a local user plane function (L-UPF) network element is the local user plane function (L-UPF) network element in the 5G core network. It can also be an entity in future communication networks that has the same or similar functions as the L-UPF.

[0068] The terminal device can be a terminal equipment, a module within a terminal equipment (such as a chip or chip system), or a logic node, logic module, or software capable of implementing all or part of the functions of the terminal equipment. Optionally, the terminal device can be installed in or used in conjunction with a terminal equipment. In this application, the chip system can be composed of chips or include chips and other discrete devices.

[0069] A terminal device is a device with wireless transceiver capabilities, including but not limited to: user equipment (UE), access terminal, subscriber unit, user station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication equipment, user agent or user device, satellite phone, cellular phone, smartphone, wireless data card, wireless modem, machine-type communication equipment, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), customer-premises equipment (CPE), point-of-sale (POS) machine, handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle equipment, communication equipment mounted on high-altitude aircraft, wearable device, drone, robot, terminal in device-to-device (D2D) communication, terminal in vehicle-to-everything (V2X) connectivity, and virtual reality (VR) device. Wireless terminals can be categorized into various types, including VR (virtual reality) terminals, AR (augmented reality) terminals, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in telemedicine or telehealth services, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, and terminals in future communication networks, without limitation. Furthermore, terminal devices can also be devices with communication functions within future communication networks, and their form within these networks is not restricted.

[0070] Access-side devices can be access network equipment, modules within access network equipment (such as chip systems), or logical nodes, modules, or software capable of implementing all or part of the functions of access network equipment. Access network equipment, also known as access nodes, helps terminal devices achieve wireless network access. In one possible application scenario, access-side equipment can be a base station (BS), an evolved NodeB (eNB), an access point (AP), a transmitting and receiving point (TRP), a next-generation NodeB (gNB), or a base station in a future mobile communication system. Additionally, access-side equipment can also be macro base stations, micro base stations, indoor stations, relay nodes, or donor nodes. All or part of the functions of the access-side device can be implemented through software functions running on hardware or through virtualization functions instantiated on a platform (such as a cloud platform).

[0071] In one possible scenario, multiple access-side devices collaborate to assist a terminal device in achieving wireless access, with each access-side device implementing a portion of the base station's functions. For example, the access-side devices can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), 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). In different communication systems, CUs (or CU-CPs and CU-UPs), DUs, or RUs may have different names, the meaning of which will be understood by those skilled in the art. For example, in an open RAN (ORAN) system, a CU can also be called an O-CU (open CU), a DU can also be called an O-DU, a CU-CP can also be called an O-CU-CP, a CU-UP can also be called an O-CU-UP, and a RU can also be called an O-RU.

[0072] Figure 1 In this context, service session function network elements, anchor point session function network elements, and local session function network elements can exchange information as follows:

[0073] The service session function network element sends a session creation request to the local session function network element. This request requests the local element to create session 1 (e.g., the first session) for the first device. Session 1 is different from session 2 (e.g., the second session) already created for the first device by the anchor session function network element. The local element receives the session creation request and creates session 1 for the first device based on it, then determines the session creation response. Alternatively, the session creation request requests the creation of session 1 for the first device. The session may include a PDU session; for example, session 1 includes PDU session 1.

[0074] The local session function network element sends a session creation response message to the serving session function network element. This message instructs the first device to create a QoS flow for the first session (described below using QoS* as an example). The session creation response message includes the QFI1 corresponding to QoS* (e.g., the first QFI), meaning it includes the QFI1 allocated by the local session function network element for QoS*. The serving session function network element receives the session creation response message and determines, based on it, that the local session function network element has created session 1 for the first device.

[0075] The serving session function network element sends session modification request information 1 (such as the first session modification request information) to the anchor session function network element. Session modification request information 1 instructs the first device to request the creation of a QoS flow*. Session modification request information 1 includes a QFI3 (such as the third QFI) allocated by the serving session function network element for the QoS flow*. QFI3 is 0, and 0 is used to request the anchor session function network element to allocate a QFI for the QoS flow*. The anchor session function network element receives session modification request information 1 and allocates QFI2 (such as the second QFI) for the QoS flow* based on QFI3. QFI2 is different from the QFI already allocated by the anchor session function network element for the QoS flow of session 2. Alternatively, the anchor session function network element determines, based on session modification request information 1, that the first device is requesting the creation of a QoS flow for session 2 (the aforementioned QoS flow*). That is, the anchor session function network element is unaware that the local session function network element is creating session 1 for the first device, and therefore reallocates a QFI different from the one already allocated by the anchor session function network element for the QoS flow of session 2.

[0076] Once the anchor session function network element has allocated a QFI to each of the different QoS flows of session 2, the anchor session function network element can determine to allocate a new QFI for QoS flow* based on QFI3=0, as shown in Table 1. The content shown in Table 1 is for illustrative purposes only and is not intended as a final limitation.

[0077] Table 1

[0078] QoS flow QFI QoS flow1 QFI=1 QoS flow2 QFI=2

[0079] As shown in Table 1, taking Session 2, which includes QoS flow1 and QoS flow2, as an example, the anchor session function network element allocates QFI=1 for QoS flow1 and QFI=2 for QoS flow2.

[0080] When the anchor session function network element receives session modification request information 1, the anchor session function network element allocates QFI=3 for QoSflow* so that different QoS flows can be distinguished.

[0081] Optionally, QFI3 can also be other values ​​or specific symbols, etc., and there are no restrictions on this.

[0082] The anchor session function network element sends session modification command information 1 (such as first session modification information) to the serving session function network element. Session modification command information 1 is used to instruct the first device to create QoS flow*. Session modification command information 1 includes QFI2. The serving session function network element receives session modification command information 1.

[0083] The Serving Session Function (SSF) network element sends QoS flow creation information to the first device. This QoS flow creation information instructs the first device to create a QoS flow*, which includes QFI2. The first device receives the QoS flow creation information and creates the QoS flow* accordingly. Since the first device is unaware that the local SSF network element is creating session 1 for it, the first device can determine that it is creating a QoS flow for session 2 based on the QoS flow creation information; that is, the first device determines that QoS flow* belongs to session 2. The Serving Session Function network element can send the QoS flow creation information to the first device through the Access and Mobility Management Function (AMF) providing services to the first device.

[0084] In the aforementioned information exchange process, after the anchor session function network element creates session 2 for the first device, it assigns different QFIs to different QoS flows of session 2. For example, the anchor session function network element assigns QFI=1 to QoS flow1 of session 2 and QFI=2 to QoS flow2 of session 2. When the serving session function network element determines that the first device has a service offloading requirement, that is, it determines that the first device has a requirement to access different networks through different sessions, the serving session function network element triggers the local session function network element to create session 1 for the first device and sends session modification request information 1 to the anchor session function network element. The anchor session function network element assigns QFI2 to QoS flow* according to session modification request information 1, such as QFI2=3. That is, the QFI2 assigned by the anchor session function network element to QoS flow* is different from the QFI already assigned by the anchor session function network element to the QoS flow of session 2. The first device participates in the creation process of session 2 but is unaware of the creation process of session 1.

[0085] Using the above method, under the premise that the anchor session function network element has already created session 2 for the first device, the service session function network element triggers the local session function network element to create session 1 for the first device, and sends the QFI2 allocated by the anchor session function network element for the QoS flow of session 1 to the first device. QFI2 is different from the QFI already allocated by the anchor session function network element for the QoS flow of session 2. This can support the first device to obtain the QFI of the QoS flow belonging to multiple sessions. Different QFIs distinguish different QoS flows, thereby realizing the differentiated QoS guarantee when the first device accesses different networks through the first session and the second session.

[0086] One possible implementation is that when the session creation response information includes filter parameter 1 (such as the first filter parameter) indicating access to any target address, the session modification request information 1 also includes filter parameter 2 (such as the second filter parameter), which indicates access to the target address corresponding to session 1. This ensures that the anchor session function network element and the service session function network element maintain consistency in the target address information of session 1.

[0087] When QoS flow* is the default load of session 1 (default load means that QoS flow* remains established throughout the entire lifecycle of session 1, and QoS flow* is a non-guaranteed flow bit rate (Non-GBR) QoS flow), the target address of filter parameter 1 assigned by the local session function network element to QoS flow* is either "any to any" or "any to assigned". The serving session function network element modifies filter parameter 1 to filter parameter 2, and the target address of filter parameter 2 is "any to the target address of session 1". The serving session function network element obtains the target address information of session 1 from the policy control function (PCF) network element.

[0088] When QoS flow* is not the default load of session 1 (described below as a dedicated load), the service session function network element will not change the target address information of filter parameter 1.

[0089] One possible implementation is that the QoS flow creation information includes filter parameter 2. In this way, the first device can perform data transmission based on the target address information in filter parameter 2.

[0090] One possible implementation is that the Service Session Function (SSF) network element stores the mapping relationship between QFI1 and QFI2 (hereinafter referred to as mapping relationship 1). After the SSF network element stores mapping relationship 1, it can manage QoS flows* according to mapping relationship 1, such as updating or deleting QoS flows*.

[0091] One possible implementation involves the Serving Session Function (SPF) network element sending mapping relationship 1 to the Serving User Plane Function (FPF) network element. The FPF network element receives mapping relationship 1, which is used by the FPF to forward data transmitted by the first device via QoS flow* to the local FPF network element. When the SPF network element sends mapping relationship 1 to the FPF network element, this enables the FPF network element to forward data transmitted by the first device via QoS flow* to the corresponding local FPF network element based on mapping relationship 1, thereby supporting the local FPF network element in forwarding and processing the data from the first device.

[0092] One possible implementation involves a first device sending data 1 and QFI2 to a serving user plane function network element via QoS flow*. The serving user plane function network element receives data 1 and QFI2 via QoS flow*, and according to mapping relationship 1, sends data 1 and QFI1 to a local user plane function network element. The local user plane function network element receives data 1 and QFI1, and forwards data 1 to the target network element according to QFI1.

[0093] The above description uses the creation of QoS flow* by the first device as an example. The following description covers the service session function network element, the local session function network element, and the management of QoS flow* between the first devices.

[0094] In one possible implementation, the service session function network element and the local session function network element can also exchange information in the following ways:

[0095] The local session function network element sends QoS flow modification information 1 (such as the first QoS flow modification information) to the serving session function network element. QoS flow modification information 1 includes QFI1 and is used to instruct the first device to update the QoS parameters of QoS flow*. In other words, QoS flow modification information 1 includes the updated QoS parameters of QoS flow*. The serving session function network element receives QoS flow modification information 1. The QoS parameters include, but are not limited to: allocation and retention priority (ARP), used to identify the priority of resource allocation, the ability to preempt resources, and the ability to be preempted; and 5G QoS Identifier (5QI), including: resource type, priority level, packet delay budget (PDB), packet error rate (PER), averaging window, and maximum data burst volume, etc.

[0096] The service session function network element, according to mapping relationship 1, sends QoS flow modification information 2 (such as second QoS flow modification information) to the first device. QoS flow modification information 2 includes QFI2 and is used to instruct the first device to update the QoS parameters of QoS flow*. In other words, QoS flow modification information 2 includes the updated QoS parameters of QoS flow*. The first device receives QoS flow modification information 2 and updates the QoS parameters of QoS flow* accordingly.

[0097] Through the above process, the service session function network element can complete the update management of QoS flow* according to mapping relationship 1, thereby realizing the synchronization of the first device and the local session function network element in terms of QoS flow* update management.

[0098] One possible implementation is that the service session function network element and the anchor point session function network element can also exchange information in the following ways:

[0099] The service session function network element, according to mapping relationship 1, sends session modification request information 2 (such as second session modification request information) to the anchor session function network element. Session modification request information 2 includes QFI2 and is used to indicate that the first device requests to update the QoS parameters of QoS flow*. The anchor session function network element receives session modification request information 2.

[0100] The anchor session function network element sends session modification command information 2 (such as second session modification information) to the service session function network element. Session modification command information 2 is used to instruct the first device to update the QoS parameters of QoS flow*.

[0101] Through the above process, synchronization of QoS flow* update management can be achieved between the service session function network element and the anchor session function network element. Optionally, the session modification request information 2 includes the updated QoS parameters of the QoS flow*. In this way, the anchor session function network element can also save the updated QoS parameters of the QoS flow* or update the QoS parameters of the QoS flow*.

[0102] One possible implementation is that the service session function network element and the local session function network element can also exchange information in the following ways:

[0103] The local session function network element sends QoS flow deletion information 1 (such as the first QoS flow deletion information) to the serving session function network element. QoS flow deletion information 1 includes QFI1 and is used to instruct the first device to delete QoS flow*. The serving session function network element receives QoS flow deletion information 1.

[0104] The service session function network element, according to mapping relationship 1, sends QoS flow deletion information 2 (such as second QoS flow deletion information) to the first device. QoS flow deletion information 2 includes QFI2 and is used to instruct the first device to delete QoS flow*. The first device receives QoS flow deletion information 2 and deletes QoS flow* according to QoS flow deletion information 2.

[0105] Through the above process, the service session function network element can complete the deletion management of QoS flow* according to the aforementioned mapping relationship, thereby achieving synchronization between the first device and the local session function network element in terms of QoS flow* deletion management.

[0106] One possible implementation is that the service session function network element and the anchor point session function network element can also exchange information in the following ways:

[0107] The service session function network element, according to mapping relationship 1, sends session modification request information 3 (such as third session modification request information) to the anchor session function network element. Session modification request information 3 includes QFI2 and is used to instruct the first device to request the deletion of QoS flow*. The anchor session function network element receives session update request information 3.

[0108] The anchor session function network element sends session modification command information 3 (such as the third session modification command information) to the serving session function network element. Session modification command information 3 is used to instruct the first device to delete QoS flow*. In addition, the anchor session function network element can also delete QoS flow*.

[0109] Through the above process, synchronization of QoS flow* deletion management between the service session function network element and the anchor session function network element can be achieved. One possible implementation involves the following information exchange between the service session function network element and the local session function network element:

[0110] The service session function network element sends session deletion information to the local session function network element. This session deletion information instructs the local session function network element to delete session 1. The local session function network element receives the session deletion information. The session deletion information includes the identification information of session 1.

[0111] The service session function network element sends QoS flow deletion information 3 (such as third QoS flow deletion information) to the first device according to mapping relationship 1. QoS flow deletion information 3 includes QFI2 and is used to instruct the first device to delete QoS flow*. The first device receives QoS flow deletion information 3 and deletes QoS flow* according to QoS flow deletion information 3.

[0112] Through the above process, the service session function network element can complete the deletion management of QoS flow* according to the aforementioned mapping relationship, thereby achieving synchronization between the first device and the local session function network element in terms of QoS flow* deletion management.

[0113] One possible implementation is that the service session function network element and the anchor point session function network element can also exchange information in the following ways:

[0114] The service session function network element, according to mapping relationship 1, sends session modification request information 4 (such as the fourth session modification request information) to the anchor session function network element. Session modification request information 4 includes QFI2 and is used to instruct the first device to request the deletion of QoS flow*. The anchor session function network element receives session modification request information 4.

[0115] The anchor session function network element sends session modification command information 4 (such as the fourth session modification command information) to the serving session function network element. Session modification command information 4 is used to instruct the first device to delete QoS flow*. In addition, the anchor session function network element can also delete QoS flow*.

[0116] Through the above process, synchronization of QoS flow* deletion management can be achieved between service session function network elements and anchor session function network elements.

[0117] One possible implementation is that the service session function network element, the anchor point session function network element, and the local session function network element can exchange information as follows:

[0118] The anchor session function network element sends session modification command information 5 (such as the fifth session modification command information) to the serving session function network element. Session modification command information 5 includes QFI2 and is used to instruct the first device to delete QoS flow*. In addition, the anchor session function network element can also delete QoS flow*.

[0119] The service session function network element sends QoS flow deletion information 4 (such as the fourth QoS flow deletion information) to the local session function network element according to the mapping relationship 1. The QoS flow deletion information 4 includes QFI1 and is used to instruct the local session function network element to delete QoS flow*.

[0120] The service session function network element sends QoS flow deletion information 5 (such as the fifth QoS flow deletion information) to the first device. QoS flow deletion information 5 includes QFI2 and is used to instruct the first device to delete QoS flow*.

[0121] Through the above process, the service session function network element can complete the deletion management of QoS flow* according to the aforementioned mapping relationship, thereby achieving synchronization between the first device and the local session function network element in terms of QoS flow* deletion management.

[0122] The above description uses the example of a service session function network element serving the source service session function network element serving the first device. The following description describes the scenario where the first device performs a service session function network element handover.

[0123] One possible implementation is that the service session function network element and the target service session function network element can exchange information as follows:

[0124] The target service session function network element sends a context retrieve request to the service session function network element. The context retrieve request is used to request the retrieve of mapping relationship 1. The service session function network element receives the context retrieve request.

[0125] The service session function network element sends mapping relationship 1 to the target service session function network element. The target service session function network element receives mapping relationship 1.

[0126] When the first device executes the service session function network element handover process, the source service session function network element sends mapping relationship 1 to the target service session function network element through the above process, thereby enabling the target service session function network element to manage QoS flow* according to mapping relationship 1, and thus ensuring the continuity of QoS flow* management.

[0127] In this embodiment, the communication system described above can be applied to the following systems: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Universal Mobile Telecommunication System (UMTS), 5G systems, Future Communication Systems, inter-satellite communication, and satellite communication, etc., which are non-terrestrial network (NTN) systems. Among them, the satellite communication system includes satellite base stations and terminal equipment. The satellite base station provides communication services to the terminal equipment. The satellite base station can also communicate with terrestrial base stations. A satellite can act as a base station or as a terminal equipment. Satellites can refer to non-terrestrial base stations or non-terrestrial equipment such as drones, hot air balloons, low-Earth orbit satellites, medium-Earth orbit satellites, and high-Earth orbit satellites.

[0128] The following text is incomplete and cannot be translated. Figure 1 The communication system shown is described using a 5G network architecture as an example.

[0129] Figure 2 yes Figure 1 The diagram illustrates a communication system applied to a network architecture. (As shown...) Figure 2 As shown, the network architecture includes AMF, SMF, PCF, unified data repository (UDR), unified data management (UDM), application function (AF), UPF, radio (R) access network (AN), and data network (DN). The following mainly describes the functions of the network elements related to this application:

[0130] 1. AMF. The AMF is responsible for the following functions: mobility management, access authentication / authorization, receiving relevant signaling from access network devices (such as next generation (NG) 2 interface signaling), completing the user registration process, and forwarding session management (SM) signaling.

[0131] 2. SMF. SMF is mainly used for session management, IP address allocation and management of terminal devices, selection of manageable user plane functions, policy control and charging function interface endpoints, downlink data notification, and completion of processes related to PDU session establishment, release, and update.

[0132] 3. PCF. PCF is responsible for user policy management, including both mobility-related policies and PDU session-related policies, such as QoS policies.

[0133] 4. UPF. As the interface with the data network, the UPF performs functions such as user plane data forwarding, session / flow-based billing and statistics, and bandwidth limiting. This includes packet routing and forwarding, as well as QoS processing for user plane data.

[0134] 5. (R)AN. (R)AN can manage radio resources and provide access services for terminal devices.

[0135] In the above description, the network element can be a network component in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (e.g., a cloud platform). The network element can be divided into one or more services; furthermore, services that exist independently of network functions may also exist. Instances of the network element, instances of services included in the network element, or instances of services that exist independently of network functions can all be referred to as service instances.

[0136] Figure 2 In this context, Npcf, Nudr, Nudm, Naf, Namf, and Nsmf are the service interfaces provided by PCF, UDR, UDM, AF, AMF, and SMF, respectively, used to invoke the corresponding service operations. The UE communicates with the AMF through the NG1 interface (N1), the (R)AN communicates with the AMF through the NG2 interface (N2), the (R)AN communicates with the UPF through the NG3 interface (N3), the SMF communicates with the UPF through the NG4 interface (N4), and the UPF accesses the DN through the NG6 interface (N6).

[0137] Figure 2 The network structure shown is for illustrative purposes only. Figure 2 The network structure shown may also include other network elements, such as authentication server function (AUSF) elements.

[0138] The following text combines Figure 3 right Figure 1 Another network architecture for the communication system application shown is described.

[0139] like Figure 3As shown in (a), the UE is connected to the RAN, the UE is connected to the AMF, the RAN is connected to the AMF, the RAN is connected to the UPF, the UPF is connected to the SMF, the UPF is connected to the DN, the SMF is connected to the UDM, the SMF is connected to the L-SMF, the SMF is connected to the AMF, the SMF is connected to the PCF, the L-SMF is connected to the UDM, the L-SMF is connected to the L-UPF, the L-SMF is connected to the UDM, the L-SMF is connected to the PCF, and the L-UPF is connected to the L-DN. Among these, the L-SMF, L-UPF, and L-DN belong to private networks, while the SMF, UPF, and DN belong to public networks or other networks.

[0140] like Figure 3 As shown in (b), the UE is connected to the RAN, the UE is connected to the Mobility Management (MM) system, the RAN is connected to the MM system, the RAN is connected to the Service User Plane (S-UP), the S-UP is connected to the Service Session Management (S-SM) system, the S-SM is connected to the SM system, the SM is connected to the UP system, the SM is connected to the Policy Function (PCF), and the UP is connected to the DN system. The S-SM can manage multiple sessions for a single user and supports selecting different service SMs (such as public network SM, local SM / L-SM, private network SM, etc.) to establish connections for the terminal device to different network domains (public network, campus network, private network, subnet, etc.). The S-UP supports offloading user data streams to UPs in different network domains. Among these, the SM, UP, DN, and Policy belong to the subnet (which can also be understood as the private network), while the S-SM and S-UP belong to the main network or the public network, etc.

[0141] The following text combines Figures 4 to 8 The interaction between the above network elements is further described. For ease of description, the following description uses the following example: the service session function network element is S-SMF, the anchor point session function network element is A-SMF, the local session function network element is L-SMF, the first device is UE, session 1 is PDU session 1, and session 2 is PDU session 2.

[0142] Figure 4 This is a schematic diagram of the interaction flow of a communication method according to an embodiment of this application. Figure 4 This example uses QoS flow* as the default load for PDU session 1. Figure 4 As shown, the method includes:

[0143] Create PDU session 2 between S401, UE, S-SMF and A-SMF.

[0144] The description of creating PDU session 2 between the UE, S-SMF, and A-SMF can be found in the existing standard and will not be repeated here. Among them, A-SMF allocates QFI=1 to QoS flow1 (the default carrier of PDU session 2) and QFI=2 to QoS flow2 (the dedicated carrier of PDU session 2).

[0145] S402: The S-SMF sends a PDU session create request to the L-SMF. The L-SMF receives the session create request. The session create request is used to request the L-SMF to create PDU session 1 for the UE.

[0146] For example, when the S-SMF determines that the PDU session 2 created by the A-SMF for the UE cannot meet the UE's cross-network requirements or determines that the UE has a service offloading requirement, the S-SMF selects the L-SMF and sends the aforementioned session creation request to the L-SMF selected by the S-SMF.

[0147] S403 and L-SMF send a control create request to PCF. PCF receives the control create request, which is used to request the QoS policy of PDU session 1.

[0148] S404, PCF sends a control create response to L-SMF. L-SMF receives the control create response, which includes the QoS policy for PDU session 1.

[0149] For example, the PCF determines the QoS policy for PDU session 1 based on the UE's user subscription information, as detailed in existing standards.

[0150] S405, L-SMF and L-UPF establish N4 session interaction.

[0151] For example, L-SMF sends a request to L-UPF to establish an N4 session, and L-UPF sends a response to L-SMF to indicate the establishment of an N4 session. The N4 session is used to carry PDU session 1.

[0152] S406, L-SMF sends a session creation response (PDU) to S-SMF. S-SMF receives the session creation response.

[0153] The session creation response instructs the UE to create a QoS flow* for PDU session 1. The session creation response includes the QoS parameters for the QoS flow*, which include QFI1 assigned by the L-SMF to the QoS flow*, i.e., QFI1 = 1. The QoS parameters for the QoS flow* also include filter parameter 1, where the target address is either "any to any" or "any to assigned".

[0154] In addition, L-SMF determines the aforementioned session creation response based on the QoS policy of PDU session 1.

[0155] S407: The S-SMF sends a PDU session modification request (e.g., update PDU session parameters or Nsmf_PDUSession_UpdatePduSession_Request message, taking Nsmf_PDUSession_UpdatePduSession_Request as an example) to the A-SMF. The A-SMF receives the PDU session modification request, which instructs the UE to request the creation of a QoS flow*. The PDU session modification request is an example of session modification request information 1.

[0156] For example, when S-SMF determines that QoS flow* is the default carrier of PDU session 1 based on QFI1 being 1, S-SMF first determines filter parameter 2 based on the traffic splitting rules, that is, it modifies the target address of filter parameter 1 to the target address of PDU1 session. In addition, S-SMF replaces QFI1 with QFI3 = 0, while other parameters in the QoS parameters of QoS flow* remain unchanged.

[0157] S408 and A-SMF allocate QFI2 for QoS flow*. See Table 1 for details.

[0158] S409. The A-SMF sends a PDU session modification command to the S-SMF (e.g., update PDU session parameters or Nsmf_PDUSession_ModifyPduSessionIsmf_Request message, taking Nsmf_PDUSession_ModifyPduSessionIsmf_Request as an example). The S-SMF receives the PDU session modification command. The PDU session modification command is an example of session modification command information 1.

[0159] PDU session modification commands are used to instruct the UE to create a QoS flow*. PDU session modification commands include QFI2, with QFI2=3 as an example.

[0160] S410 and S-SMF store the mapping relationship between QFI1 and QFI2.

[0161] S411, S-SMF sends mapping relationship 1 to S-UPF. S-UPF receives mapping relationship 1.

[0162] S412 and S-SMF send QoS flow creation information to the UE. The UE receives the QoS flow creation information.

[0163] The S-SMF sends QoS flow creation information to the UE via the AMF. For example, the S-SMF sends an N1N2 message (such as an N1N2 transfer message) to the AMF, which receives the N1N2 message, which includes QoS flow creation information. The AMF sends a PDU session resource modify request to the RAN, which receives the PDU session resource modify request, which also includes QoS flow creation information. The RAN then sends a PDU session modify command to the UE. The UE receives the PDU session modify command, which also includes QoS flow creation information.

[0164] Optionally, the RAN sends a PDU session resource modify response to the AMF. The AMF receives the PDU session resource modify response, which is used to indicate to the RAN that the QoS flow* was successfully created.

[0165] Optionally, the AMF sends an Update Session Request message (Nsmf_PDUSession_UpdateSMContext_Request) to the S-SMF. The S-SMF receives the Update Session Request message, which is used to indicate that the RAN has successfully created the QoS flow*. The S-SMF then returns an Update Session Response message (Nsmf_PDUSession_UpdateSMContext_Response) to the AMF.

[0166] S413. The UE sends a QoS flow creation success message to the S-SMF. The S-SMF receives the QoS flow creation success message, which indicates that the UE has successfully created the QoS flow*.

[0167] After the UE successfully creates a QoS flow*, the UE sends a QoS flow creation success message to the S-SMF via the AMF. For example, the UE sends a PDU session modification complete message to the RAN, which includes the QoS flow creation success message. The RAN receives the PDU session modification complete message. The RAN then sends the PDU session modification complete message to the AMF, and the AMF receives it. The AMF sends an update session request message to the S-SMF, which receives the update session request message. The update session request message includes the QoS flow creation success message, and the S-SMF returns an update session response message to the AMF.

[0168] After the UE successfully creates a QoS flow*, the UE sends data 1 and QFI2 to the S-UPF through the QoS flow*. The S-UPF sends data 1 and QFI1 to the corresponding L-UPF according to the mapping relationship 1, and the L-UPF performs data routing.

[0169] S414, S-SMF and S-UPF perform N4 session modification interaction.

[0170] For example, the S-SMF sends a request to the S-UPF to modify the N4 session, and the S-UPF sends a response to the S-SMF to instruct the modification of the N4 session.

[0171] S415, the S-SMF sends a PDU session modification response (e.g., Nsmf_PDUSession_ModifyPduSessionIsmf_Response message, taking Nsmf_PDUSession_ModifyPduSessionIsmf_Response as an example) to the A-SMF. The A-SMF receives the PDU session modification response, which is used to indicate that the UE has successfully created a QoS flow*.

[0172] Through the above process, assuming that A-SMF has already created PDU session 2 for UE, S-SMF triggers L-SMF to create PDU session 1 for UE and sends QFI2, which is allocated by A-SMF for QoS flow* of PDU session 1, to UE. QFI2 is different from the QFI already allocated by A-SMF for QoS flow of PDU session 2. This can support UE to obtain QFI belonging to QoS flow of multiple PDU sessions. Different QFI distinguish different QoS flows, thereby realizing QoS differentiation guarantee when UE accesses different networks through PDU session 1 and PDU session 2.

[0173] The execution order from S401 to S415 above is for illustrative purposes only and is not a final limitation. Furthermore, some steps in the above process may be optional and are not limited thereto.

[0174] Figure 4 This description uses the example of L-SMF instructing the UE to create a default carrier. The following text combines... Figure 5 The scenario in which L-SMF instructs the UE to create a dedicated payload is described.

[0175] Figure 5 This is a schematic diagram of the interaction flow of another communication method according to an embodiment of this application. Figure 5 This example uses QoS flow* as the dedicated transport for PDU session 1. Figure 5 As shown, the method includes:

[0176] S501, UE, S-SMF, and A-SMF establish PDU session 2. For details, please refer to S401.

[0177] Create a PDU session 1 between S502, S-SMF, A-SMF and L-SMF.

[0178] For example, L-SMF has created a default carrier for PDU session 1 for the UE, and L-SMF has allocated QFI=1 to the default carrier for PDU session 1.

[0179] S503, PCF sends an update notify request to L-SMF. L-SMF receives the update notify request, which instructs L-SMF to create a QoS flow* for the UE. The QoS flow* is a dedicated carrier for PDU session 1.

[0180] For example, the PCF determines the update notification request based on the UE's user subscription information, as detailed in existing standards.

[0181] S504, L-SMF sends an update notify response to PCF. PCF receives the update notify response, which indicates that L-SMF has received the update notify request.

[0182] S505 and L-SMF send a modification request to S-SMF. S-SMF receives the modification request. The modification request instructs the UE to create a QoS flow*. The modification request includes the QoS parameters of the QoS flow*, such as QFI1=2 assigned by L-SMF for the QoS flow*.

[0183] S506, S-SMF sends a modify response to L-SMF. L-SMF receives the modify response, which indicates that S-SMF has received the modification request.

[0184] S507, L-SMF and L-UPF perform N4 session modification interaction.

[0185] For example, L-SMF sends a request to L-UPF to modify the N4 session, and L-UPF sends a response to L-SMF to indicate that the N4 session has been modified. The updated N4 session is used to carry the QoS flow* of PDU session 1.

[0186] S508, S-SMF sends a PDU session modification request (Nsmf_PDUSession_UpdatePduSession_Request) to A-SMF. A-SMF receives the PDU session modification request. The PDU session modification request is an example of session modification request information 1.

[0187] For example, S-SMF replaces QFI1 in QoS flow* with QFI3, QFI3=0, while the other parameters in the QoS parameters of QoS flow* remain unchanged.

[0188] S509 and A-SMF allocate QFI2 for QoS flow*. See Table 1 for details. QFI2 = 4.

[0189] S510, A-SMF sends a PDU session modification command (Nsmf_PDUSession_ModifyPduSessionIsmf_Request) to S-SMF. S-SMF receives the PDU session modification command, which instructs the UE to create a QoS flow*. The PDU session modification command includes QFI2. The PDU session modification command is an example of session modification command information 1.

[0190] S511 and S-SMF store the mapping relationship between QFI1 and QFI2.

[0191] S512, S-SMF sends mapping relationship 2 to S-UPF. S-UPF receives mapping relationship 2.

[0192] S513, S-SMF sends QoS flow creation information to UE. UE receives QoS flow creation information. See S412 for details.

[0193] S514, the UE sends a QoS flow creation success message to the S-SMF. The S-SMF receives the QoS flow creation success message. See S413 for details.

[0194] S515, S-SMF and S-UPF interact to establish N4 sessions.

[0195] For example, the S-SMF sends a request to the S-UPF to establish an N4 session, and the S-UPF sends a response to the S-SMF to indicate that an N4 session should be established.

[0196] S516, S-SMF sends a PDU session modification response (Nsmf_PDUSession_ModifyPduSessionIsmf_Response) to A-SMF. A-SMF receives the PDU session modification response, which is used to indicate that the UE has successfully created a QoS flow*.

[0197] Through the above process, assuming that A-SMF has already created PDU session 2 for UE, S-SMF triggers L-SMF to create PDU session 1 for UE and sends QFI2, which is allocated by A-SMF for QoS flow* of PDU session 1, to UE. QFI2 is different from the QFI already allocated by A-SMF for QoS flow of PDU session 2. This can support UE to obtain QFI belonging to QoS flow of multiple PDU sessions. Different QFI distinguish different QoS flows, thereby realizing QoS differentiation guarantee when UE accesses different networks through PDU session 1 and PDU session 2.

[0198] The execution order of S501 to S516 above is for illustrative purposes only and is not a final limitation. Furthermore, some steps in the above process may be optional and are not limited thereto.

[0199] Figure 4 and Figure 5 This description uses the example of one L-SMF creating a PDU session for the UE, but it is not limited to the scenario where multiple L-SMFs each establish one or more sessions for the UE. Each L-SMF supports... Figure 4 and Figure 5 The process described above.

[0200] Taking the creation of default traffic as an example, if the QoS created by sessions on A-SMF and multiple L-SMFs exceeds the UE's maximum flow specification (meaning the number of filters carried in the issued QoS exceeds the maximum number of filters supported by the UE for a single QoS, or the number of created QoS flows exceeds 64), A-SMF cannot allocate QFIs for the newly created QoS flows. Accordingly, one of the following two solutions can be adopted:

[0201] Option 1: S-SMF rolls back the L-SMF session and releases the current L-SMF session. L-SMF does not create a PDU session 1 for the UE.

[0202] Option 2: S-SMF does not roll back L-SMF sessions, and S-SMF establishes a mapping relationship between the default carrier of PDU session 1 and the default carrier of PDU session 2. That is, QFI1 of L-SMF is mapped to QFI=1 of A-SMF. Alternatively, S-SUP will forward the data transmitted by the UE through the default carrier of PDU session 2 to L-UPF.

[0203] Taking the creation of a dedicated load as an example, if the QoS created by the session on the A-SMF and multiple L-SMFs exceeds the UE's maximum flow specification, the A-SMF will be unable to allocate a QFI for the newly created QoS flow and can reply that the QFI failed. The S-SMF will reply to the L-SMF that the creation of the QoS flow failed, and the L-SMF will not create the dedicated load.

[0204] Figure 4 and Figure 5 This description uses L-SMF to create a QoS flow for the UE as an example. The following text will combine... Figures 6 to 10 The scenarios for S-SMF and L-SMF to manage QoS flow* are described.

[0205] Figure 6 This is a schematic diagram of the interaction flow of another communication method according to an embodiment of this application. For example... Figure 6 As shown, the method includes:

[0206] S601, PDU session 2 is established between UE, S-SMF and A-SMF. For details, please refer to S401.

[0207] QoS flow* for creating PDU session 1 between S602, S-SMF, A-SMF, and L-SMF.

[0208] S603, PCF sends an update notify request to L-SMF. L-SMF receives the update notify request, which instructs L-SMF to update the QoS parameters of QoS flow*. The update notify request includes the updated QoS parameters of QoS flow*.

[0209] S604, L-SMF sends an update notify response to PCF. PCF receives the update notify response, which indicates that L-SMF has received the update notify request.

[0210] S605 and L-SMF send a modification request to S-SMF. S-SMF receives the modification request, which includes QFI1 and the updated QoS parameters for QoS flow*. The modification request can be an example of QoS flow modification information 1.

[0211] S606, S-SMF sends a modify response to L-SMF. L-SMF receives the modify response, which indicates that S-SMF has received the modification request.

[0212] S607, L-SMF and L-UPF perform N4 session modification interaction.

[0213] For example, the L-SMF sends a request to the L-UPF to modify the N4 session, and the L-UPF sends a response to the L-SMF to instruct the modification of the N4 session.

[0214] S608, S-SMF sends a PDU session modification request (Nsmf_PDUSession_UpdatePduSession_Request) to A-SMF. A-SMF receives the PDU session modification request. The PDU session modification request includes QFI2, and is used to instruct the UE to request an update to the QoS parameters of QoS flow*. The PDU session modification request can be an example of session modification request information 2.

[0215] Optionally, the PDU session modification request may include the QoS parameters of the updated QoS flow*.

[0216] Optionally, S609 and A-SMF update QoS parameters for QoS flow*.

[0217] S610, A-SMF sends a PDU session modification command (Nsmf_PDUSession_ModifyPduSessionIsmf_Request) to S-SMF. S-SMF receives the PDU session modification command, which instructs the UE to update the QoS parameters of QoS flow*. The PDU session modification command includes QFI2. The PDU session modification command can be an example of session modification command information 2.

[0218] S611 and S-SMF send QoS flow modification information to the UE. The UE receives the QoS flow modification information. The QoS flow modification information is used to instruct the UE to update the QoS parameters of QoS flow*. The QoS flow modification information includes QFI2 and the updated QoS parameters of QoS flow*.

[0219] The S-SMF sends QoS flow modification information to the UE via the AMF. For example, the S-SMF sends an N1N2 message to the AMF, which receives the N1N2 message, which includes QoS flow modification information. The AMF sends a PDU session resource modification request to the RAN, which receives the PDU session resource modification request, which includes QoS flow modification information. The RAN sends a PDU session modification command to the UE, which receives the PDU session modification command, which includes QoS flow modification information.

[0220] Optionally, the RAN sends a PDU session resource modification response (e.g., PDU session resourcemodify response) to the AMF. The AMF receives the PDU session resource modification response, which is used to indicate that the RAN has successfully updated the QoS parameters of the QoS flow*.

[0221] Optionally, the AMF sends an Update Session Request message (Nsmf_PDUSession_UpdateSMContext_Request) to the S-SMF. The S-SMF receives the Update Session Request message, which indicates that the RAN has successfully updated the QoS parameters of QoS flow*. The S-SMF then returns an Update Session Response message (Nsmf_PDUSession_UpdateSMContext_Response) to the AMF.

[0222] S612, the UE sends a QoS flow modification success message to the S-SMF. The S-SMF receives the QoS flow modification success message.

[0223] After the UE successfully updates the QoS parameters of the QoS flow*, the UE sends a QoS flow modification success message to the S-SMF via the AMF. For example, the UE sends a PDU session modification completion message to the RAN, which includes the QoS flow modification success message. The RAN receives the PDU session modification completion message and sends it to the AMF, which in turn receives it. The AMF then sends an update session request message to the S-SMF, which receives the update session request message, which includes the QoS flow modification success message. Finally, the S-SMF returns an update session response message to the AMF.

[0224] S613, S-SMF, and S-UPF perform N4 session modification interactions.

[0225] For example, the S-SMF sends a request to the S-UPF to modify the N4 session, and the S-UPF sends a response to the S-SMF to instruct the modification of the N4 session.

[0226] S614, S-SMF sends a PDU session modification response to A-SMF. A-SMF receives the PDU session modification response, which indicates that the UE has successfully updated the QoS parameters of QoS flow*.

[0227] The execution order from S601 to S614 above is merely an example and not a final limitation. Furthermore, some steps in the above process may be optional and are not limited thereto.

[0228] Through the above process, S-SMF can complete the update management of QoS flow* according to mapping relationship 1, thereby realizing the synchronization of QoS flow* update management between UE and L-SMF.

[0229] Figure 7 This is a schematic diagram of the interaction flow of another communication method according to an embodiment of this application. For example... Figure 7 As shown, the method includes:

[0230] S701, UE, S-SMF, and A-SMF establish PDU session 2. For details, please refer to S401.

[0231] QoS flow* for creating PDU session 1 between S702, S-SMF, A-SMF, and L-SMF.

[0232] S703, PCF sends an update notify request to L-SMF. L-SMF receives the update notify request, which instructs L-SMF to delete the QoS flow*.

[0233] S704, L-SMF sends an update notify response to PCF. PCF receives the update notify response, which indicates that L-SMF has received the update notify request.

[0234] S705, L-SMF sends a modification request to S-SMF. S-SMF receives the modification request, which includes QFI1. The modification request instructs the UE to delete QoS flow*. The modification request is an example of the aforementioned QoS flow deletion information 1.

[0235] S706, S-SMF sends a modify response to L-SMF. L-SMF receives the modify response, which indicates that S-SMF has received the modification request.

[0236] S707, L-SMF and L-UPF perform N4 session modification interaction.

[0237] For example, the L-SMF sends a request to the L-UPF to modify the N4 session, and the L-UPF sends a response to the L-SMF to instruct the modification of the N4 session.

[0238] S708, S-SMF sends a PDU session modification request (Nsmf_PDUSession_UpdatePduSession_Request) to A-SMF. A-SMF receives the PDU session modification request, which includes QFI2. The PDU session modification request is used to instruct the UE to request the deletion of QoS flow*. The PDU session modification request can be an example of session modification request information 3.

[0239] S709, A-SMF removes QoS flow*.

[0240] S710, A-SMF sends a PDU session modification command (Nsmf_PDUSession_ModifyPduSessionIsmf_Request) to S-SMF. S-SMF receives the PDU session modification command, which instructs the UE to delete QoS flow*. The PDU session modification command includes QFI2. The PDU session modification command can be an example of session modification command information 3.

[0241] S711 and S-SMF send QoS flow deletion information to the UE. The UE receives the QoS flow deletion information, which instructs the UE to delete the QoS flow*.

[0242] For a description of how S-SMF sends QoS flow deletion information to the UE, please refer to the description in S611, which will not be repeated here.

[0243] S712, the UE sends a QoS flow deletion success message to the S-SMF. The S-SMF receives the QoS flow deletion success message.

[0244] For a description of how the UE sends QoS flow deletion success information to the S-SMF, please refer to the description in S612, which will not be repeated here.

[0245] S713, S-SMF, and S-UPF perform N4 session modification interactions. For example, S-SMF sends a request to S-UPF to modify the N4 session, and S-UPF sends a response to S-SMF indicating that the N4 session should be modified.

[0246] S714, S-SMF sends a PDU session modification response (Nsmf_PDUSession_ModifyPduSessionIsmf_Response) to A-SMF. A-SMF receives the PDU session modification response, which is used to indicate to the UE that the QoS flow* was successfully deleted.

[0247] The execution order of S701 to S714 described above is for illustrative purposes only and is not intended as a final limitation. Furthermore, some steps in the above process may be optional and are not limited thereto.

[0248] Through the above process, S-SMF can complete the deletion management of QoS flow* according to mapping relationship 1, thereby achieving synchronization between UE and L-SMF in the deletion management of QoS flow*.

[0249] Figure 8 This is a schematic diagram of the interaction flow of another communication method according to an embodiment of this application. For example... Figure 8 As shown, the method includes:

[0250] S801, UE, S-SMF, and A-SMF establish PDU session 2. For details, please refer to S401.

[0251] QoS flow* for creating PDU session 1 between S802, S-SMF, A-SMF, and L-SMF.

[0252] S803, S-SMF confirms deletion of PDU session 1.

[0253] For example, after the UE completes the mobility procedure, the S-SMF re-obtains the QoS policy from the PCF, the PCF issues the QoS policy, and the S-SMF confirms the deletion of PDU session 1.

[0254] S804, S-SMF sends a release request to L-SMF. L-SMF receives the release request, which indicates the deletion of PDU session 1. The release request can be understood as an example of the aforementioned session deletion information.

[0255] S805, L-SMF and L-UPF perform N4 session deletion interaction. For example, L-SMF sends a request to L-UPF to delete the N4 session, and L-UPF sends a response to L-SMF to indicate that the N4 session has been deleted.

[0256] S806, L-SMF sends a release response to S-SMF. S-SMF receives the release response, which indicates that L-SMF has received the release request.

[0257] S807, the S-SMF sends a PDU session modification request (Nsmf_PDUSession_UpdatePduSession_Request) to the A-SMF. The A-SMF receives the PDU session modification request. The PDU session modification request includes QFI2, and is used to instruct the UE to request the deletion of QoS flow*. The PDU session modification request can be understood as an example of session modification request information 4.

[0258] S808, A-SMF delete QoS flow*.

[0259] S809, A-SMF sends a PDU session modification command (Nsmf_PDUSession_ModifyPduSessionIsmf_Request) to S-SMF. S-SMF receives the PDU session modification command. The PDU session modification command is used to instruct the UE to delete QoS flow*. The PDU session modification command includes QFI2. The PDU session modification command can be understood as an example of session modification command information 4.

[0260] S810 and S-SMF send QoS flow deletion information to the UE. The UE receives the QoS flow deletion information. The QoS flow deletion information is used to instruct the UE to delete the QoS flow*. For a description of how S-SMF sends QoS flow deletion information to the UE, please refer to the description in S611, which will not be repeated here.

[0261] S811, the UE sends a QoS flow deletion success message to the S-SMF. The S-SMF receives the QoS flow deletion success message. For a description of the UE sending the QoS flow deletion success message to the S-SMF, please refer to the description in S612, which will not be repeated here.

[0262] S812, S-SMF and S-UPF perform N4 session modification interaction. For example, S-SMF sends a request to S-UPF to modify the N4 session, and S-UPF sends a response to S-SMF to indicate that the N4 session has been modified.

[0263] S813, S-SMF sends a PDU session modification response (Nsmf_PDUSession_ModifyPduSessionIsmf_Response) to A-SMF. A-SMF receives the PDU session modification response, which is used to indicate to the UE that the QoS flow* was successfully deleted.

[0264] The execution order from S801 to S813 described above is merely an example and not a final limitation. Furthermore, some steps in the above process may be optional and are not limited thereto.

[0265] Through the above process, the S-SMF completes the deletion management of QoS flow* according to mapping relationship 1, thereby achieving synchronization between the UE and L-SMF in the deletion management of QoS flow*.

[0266] Figure 9 This is a schematic diagram of the interaction flow of another communication method according to an embodiment of this application. For example... Figure 9 As shown, the method includes:

[0267] S901, UE, S-SMF, and A-SMF establish PDU session 2. For details, please refer to S401.

[0268] QoS flow* for creating PDU session 1 between S902, S-SMF, A-SMF and L-SMF.

[0269] S903, PCF sends an update notify request to A-SMF. A-SMF receives the update notify request, which instructs A-SMF to delete the QoS corresponding to QoS rule 1. The QoS corresponding to QoS rule 1 includes QoS flow*. The update notify request includes QoS rule 1.

[0270] S904. The A-SMF sends an update notify response to the PCF. The PCF receives the update notify response, which indicates that the A-SMF has received the update notify request.

[0271] S905, A-SMF sends a PDU session modification command (Nsmf_PDUSession_ModifyPduSessionIsmf_Request) to S-SMF. S-SMF receives the PDU session modification command, which instructs S-SMF to delete QoS flows*. The PDU session modification command includes QFI2. The PDU session modification command can be understood as an example of session modification command information 5.

[0272] S906, the S-SMF sends QoS flow deletion information to the UE. The UE receives the QoS flow deletion information. The QoS flow deletion information is used to instruct the UE to delete the QoS flow*. For a description of how the S-SMF sends QoS flow deletion information to the UE, please refer to the description in S611, which will not be repeated here.

[0273] S907: The UE sends a QoS flow deletion success message to the S-SMF. The S-SMF receives the QoS flow deletion success message. For a description of the UE sending the QoS flow deletion success message to the S-SMF, please refer to the description in S612, which will not be repeated here.

[0274] S908, S-SMF, and S-UPF interact to modify the N4 session. For example, S-SMF sends a request to S-UPF to modify the N4 session, and S-UPF sends a response to S-SMF indicating that the N4 session should be modified.

[0275] S909 and S-SMF send a modification request to L-SMF. A-SMF receives the modification request, which instructs L-SMF to delete the QoS flow*.

[0276] S910, L-SMF and L-UPF perform N4 session modification interaction. For example, L-SMF sends a request to L-UPF to modify the N4 session, and L-UPF sends a response to L-SMF to indicate that the N4 session has been modified.

[0277] S911, L-SMF sends a modify response to S-SMF. S-SMF receives the modify response, which indicates that L-SMF has successfully removed the QoS flow*.

[0278] The execution order of S901 to S911 described above is for illustrative purposes only and is not intended as a final limitation. Furthermore, some steps in the above process may be optional and are not limited thereto.

[0279] Through the above process, S-SMF can complete the deletion management of QoS flow* according to mapping relationship 1, thereby achieving synchronization between UE and L-SMF in the deletion management of QoS flow*.

[0280] Figure 10 This is a schematic diagram of the interaction flow of another communication method according to an embodiment of this application. For example... Figure 10 As shown, the method includes:

[0281] S1001. A PDU session 2 is established between the UE, the source S-SMF, and the source A-SMF. For details, please refer to S401.

[0282] QoS flow* for creating PDU session 1 between S1002, source S-SMF, A-SMF, and L-SMF.

[0283] The first handover procedure is executed between S1003, the source S-SMF, the source AMF, the target AMF, and the target S-SMF.

[0284] For example, the source RAN sends a Handover Required request to the source AMF, which includes the UE's location / target RAN information. Based on the UE's location / target RAN information, the source AMF selects a target AMF and sends a UE context establishment request (Namf_Communication_CreateUEContext Request). The UE context establishment request includes the source S-SMF's context ID and the UE's location / target RAN information. Based on the UE's location / target RAN information, the target AMF selects a target S-SMF and sends an SM context establishment request to the target S-SMF. The SM context establishment request includes the source S-SMF's context ID and the UE's location information.

[0285] S1004. The target S-SMF sends a context retrieval request to the source S-SMF. The source S-SMF receives the context retrieval request, which is used to request the retrieval of mapping relationship 1.

[0286] For example, the target S-SMF sends a context acquisition request to the source S-SMF. The context acquisition request is used to request the acquisition of the UE's context (including mapping relationship 1). The context acquisition request includes the context ID of the source S-SMF.

[0287] S1005, The source S-SMF sends mapping relationship 1 to the target S-SMF.

[0288] For example, the source S-SMF sends context acquisition information to the target S-SMF. The context acquisition information includes the context of PDU session 1 and mapping relationship 1.

[0289] S1006, the second handover procedure is performed between the source RAN, target RAN, source AMF, target AMF, target S-SMF, source S-SMF, A-SMF, A-UPF, and L-SMF.

[0290] For example, the target S-SMF selects the target S-UPF based on the UE's location information, requests the establishment of an N4 session, and allocates N3 and N9 tunnel information.

[0291] For example, the target S-SMF replies to the target AMF, carrying the N3 tunnel information of the target S-UPF.

[0292] For example, the target AMF sends a handover request to the target RAN based on the target RAN information, carrying the N3 tunnel information of the target S-UPF.

[0293] For example, the target RAN responds with a handover response, carrying the target RAN's N3 tunnel information.

[0294] For example, the target AMF requests an update from the target S-SMF, carrying the N3 tunnel information of the target RAN.

[0295] For example, the target S-SMF replies with an update response to the target AMF.

[0296] For example, the target AMF replies to the source AMF with a UE context establishment response.

[0297] For example, the source AMF sends a handover command to the source RAN.

[0298] For example, the source RAN sends a handover command to the UE.

[0299] For example, the UE switches to the target RAN and sends a handover confirmation to the target RAN.

[0300] For example, the target RAN sends a handover notification to the target AMF.

[0301] For example, the target AMF notifies the source AMF and the target S-SMF that the N2 handover is complete.

[0302] For example, the target AMF updates the N3 tunnel information of the target RAN to the target S-SMF.

[0303] For example, the target S-SMF updates the N3 tunnel information of the target RAN to the target S-UPF.

[0304] For example, the target S-SMF updates the N9 tunnel of the target S-UPF and the location information of the UE to the A-SMF.

[0305] For example, A-SMF updates the N9 tunnel and UE location information to the anchor (A)-UPF.

[0306] For example, A-SMF responds with an update response.

[0307] For example, the target S-SMF updates the N9 tunnel of the target S-UPF and the location information of the UE to the L-SMF.

[0308] For example, the target S-SMF response.

[0309] For example, the UE initiates a mobility registration update process.

[0310] For a detailed description of the above switching process, please refer to the existing standards; it will not be repeated here.

[0311] Using the above method, when the UE performs the S-SMF handover procedure, the source S-SMF sends mapping relationship 1 to the target S-SMF through the above procedure, thereby enabling the target S-SMF to manage the QoS flow of the first session according to the mapping relationship 1, thus ensuring the continuity of QoS flow management.

[0312] Finally, the device embodiments of this application will be described.

[0313] To implement the functions in the method provided in this application, the service session function network element, the local session function network element, and the anchor point session function network element may each include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is implemented in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0314] Figure 11This is a schematic block diagram of a communication device according to an embodiment of this application. The communication device includes a processing circuit 1110 and a transceiver circuit 1120, which can be interconnected or coupled, for example, interconnected via a bus 1130. The communication device can be a serving session function network element, a local session function network element, or an anchor session function network element.

[0315] Optionally, the communication device may also include a memory 1140. The memory 1140 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), which is used for related instructions and data.

[0316] The processing circuit 1110 may be all or part of the processing circuitry in one or more processors, or it may be one or more processors. The processor may be a central processing unit (CPU). If the processing circuit 1110 is a CPU, the CPU may be a single-core CPU or a multi-core CPU. The processing circuit 1110 may be a signal processor, a chip, or other integrated circuit capable of implementing the methods of this application, or a portion of the circuitry within the aforementioned processor, chip, or integrated circuit that performs processing functions. Additionally, the transceiver circuit 1120 may be a transceiver, or an input / output interface. An input / output interface is used for inputting or outputting signals or data and may also be referred to as an input / output circuit.

[0317] When the communication device is a service session function network element, for example, the processing circuit 1110 is used to perform the following operations: send session creation request information to the local session function location; receive session creation response information from the local session function location, etc.

[0318] When the communication device is a local session function network element, for example, the processing circuit 1110 is used to perform the following operations: receive session creation request information; send session creation response information, etc.

[0319] When the communication device is an anchor session management network element, for example, the processing circuit 1110 is used to perform the following operations: receive session modification request information 1 from the service session function network element; send session modification command information 1, etc.

[0320] When the communication device is a service session function network element, a local session function network element, or an anchor point session function network element, it will be responsible for executing the methods or steps related to the service session function network element, local session function network element, or anchor point session function network element in the aforementioned method embodiments.

[0321] When the communication device is a service session function network element, a local session function network element, or an anchor point session function network element, the transceiver circuit 1020 can be a transceiver.

[0322] When the communication device is a chip used for a service session function network element, a local session function network element, or an anchor point session function network element, the transceiver circuit 1020 can be an input / output circuit.

[0323] The above description is merely exemplary. For details, please refer to the content shown in the above method embodiments.

[0324] Figure 11 The implementation of each operation can also be found by referring to... Figures 4 to 10 The corresponding description of the method embodiments shown.

[0325] Figure 12 This is a schematic block diagram of another communication device according to an embodiment of this application. The communication device can be a serving session function network element, a local session function network element, or an anchor session function network element, used to implement the methods involved in the above embodiments.

[0326] The communication device includes a transceiver unit 1210 and a processing unit 1220. The transceiver unit 1210 may include a sending unit and a receiving unit. The sending unit is used to perform the sending action of the communication device, and the receiving unit is used to perform the receiving action of the communication device. For ease of description, the sending unit and the receiving unit are combined into one transceiver unit in this embodiment. This will be explained uniformly here and will not be repeated later.

[0327] When the communication device is a Service Session Function (SSC) network element, exemplarily, the transceiver unit 1210 is configured to perform the following operations: send a session creation request to the local session function location; receive a session creation response from the local session function location, etc. The processing unit 1220 is configured to maintain the mapping relationship 1 between QFI1 and QFI2.

[0328] When the communication device is a local session function network element, exemplarily, the transceiver unit 1210 is used to perform the following operations: receiving session creation request information; sending session creation response information, etc. The processing unit 1220 is used to create session 1.

[0329] When the communication device is an anchor session management network element, exemplarily, the transceiver unit 1210 is used to perform the following operations: receive session modification request information 1 from the service session function network element; send session modification command information 1, etc. The processing unit 1220 is used to allocate QFI2.

[0330] When the communication device is a service session function network element, a local session function network element, or an anchor point session function network element, it will be responsible for executing one or more of the methods or steps related to the service session function network element, local session function network element, or anchor point session function network element in the aforementioned method embodiments.

[0331] Optionally, the communication device further includes a storage unit 1230 for storing programs or code for executing the aforementioned methods.

[0332] Figure 12 The transceiver unit in the middle can correspond to Figure 11 The transceiver circuit in the middle, Figure 12 The processing unit in can correspond to Figure 11 The processing circuitry within.

[0333] Figure 11 and Figure 12 The illustrated device embodiment is used to implement Figures 4 to 10 The content described. Figure 11 and Figure 12 The specific execution steps and methods of the device shown can be found in the content described in the foregoing method embodiments.

[0334] This application also provides a chip, including a processor, for calling and executing instructions stored in a memory, causing a communication device on which the chip is installed to perform the methods described in the examples above. The memory may be integrated within the chip or located externally.

[0335] This application also provides another chip, including: an input interface, an output interface, and a processing circuit, wherein the input interface, the output interface, and the processor are connected through an internal connection path, and the processing circuit is used to execute code in memory. When the code is executed, the processing circuit is used to execute the methods in the above examples.

[0336] Optionally, the chip also includes a memory for storing computer programs or code. The input and output interfaces can be independent of each other, or they can be integrated into a single input / output interface.

[0337] The processing circuitry can be all or part of the processing circuitry in one or more processors, or one or more processors.

[0338] This application also provides a processor coupled to a memory for executing the methods and functions of the service session function network element, local session function network element, or anchor session function network element involved in any of the above embodiments.

[0339] In another embodiment of this application, a computer program product containing instructions is provided, which, when run on a computer, enables the implementation of the methods described in the foregoing embodiments.

[0340] This application also provides a computer program that, when run on a computer, enables the implementation of the methods described in the foregoing embodiments.

[0341] In another embodiment of this application, a computer-readable storage medium is provided, which stores a computer program that, when executed by a computer, implements the methods described in the foregoing embodiments.

[0342] It should be understood that in the embodiments of this application, the processor can be a central processing unit (CPU), but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0343] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced synchronous SDRAM (ESDRAM), synchronous linked DRAM (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0344] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0345] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0346] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for example, the division of units is merely a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection of devices or units may be electrical, mechanical, or other forms.

[0347] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. If the above functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory, random access memory, magnetic disks, or optical disks.

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

Claims

1. A communication method, characterized in that, Applied to network elements for service session functions, including: Send a session creation request message to the local session function network element. The session creation request message is used to request the local session function network element to create a first session for the first device. The first session is different from the second session that the anchor session function network element has already created for the first device. The device receives session creation response information from the local session function network element. The session creation response information is used to instruct the first device to create a quality of service flow for the first session. The session creation response information includes a first quality of service flow identifier assigned by the local session function network element to the quality of service flow. Send a first session modification request to the anchor session function network element. The first session modification request is used to instruct the first device to request the creation of the quality of service flow. The first session modification request includes a third quality of service flow identifier allocated by the service session function network element for the quality of service flow. The third quality of service flow identifier is 0. The 0 is used to request the anchor session function network element to allocate a quality of service flow identifier for the quality of service flow. The device receives a first session modification command message from the anchor session function network element. The first session modification command message is used to instruct the first device to create the quality of service flow. The first session modification command message includes a second quality of service flow identifier allocated by the anchor session function network element for the quality of service flow. The second quality of service flow identifier is different from the quality of service flow identifier already allocated by the anchor session function network element for the quality of service flow of the second session. A Quality of Service (QoS) flow creation information is sent to the first device. The QoS flow creation information is used to instruct the first device to create the QoS flow, and the QoS flow creation information includes the second QoS flow identifier.

2. The method according to claim 1, characterized in that, When the session creation response information includes a first filter parameter for indicating access to any target address, the first session modification request information also includes a second filter parameter, which is used to indicate access to the target address corresponding to the first session.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Save the mapping relationship between the first quality of service flow identifier and the second quality of service flow identifier.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The mapping relationship between the first quality of service flow identifier and the second quality of service flow identifier is sent to the serving user plane function network element. The mapping relationship is used by the serving user plane function network element to forward the data transmitted by the first device through the quality of service flow to the local user plane function network element.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: The device receives first quality of service flow modification information from the local session function network element. The first quality of service flow modification information includes the first quality of service flow identifier and is used to instruct the first device to update the quality of service flow parameters of the quality of service flow. Based on the mapping relationship between the first QoS flow identifier and the second QoS flow identifier, a second QoS flow modification information is sent to the first device. The second QoS flow modification information includes the second QoS flow identifier and is used to instruct the first device to update the QoS parameters of the QoS flow.

6. The method according to claim 5, characterized in that, Before sending the second quality of service flow modification information to the first device, the method further includes: According to the mapping relationship, a second session modification request information is sent to the anchor session function network element. The second session modification request information includes the second quality of service flow identifier. The second session modification request information is used to instruct the first device to request an update of the quality of service parameters of the quality of service flow. The device receives a second session modification command from the anchor session function network element, the second session modification command being used to instruct the first device to update the quality of service parameters of the quality of service flow.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: The device receives first quality of service flow deletion information from the local session function network element. The first quality of service flow deletion information includes a first quality of service flow identifier and is used to instruct the first device to delete the quality of service flow. Based on the mapping relationship between the first QoS flow identifier and the second QoS flow identifier, a second QoS flow deletion information is sent to the first device. The second QoS flow deletion information includes the second QoS flow identifier and is used to instruct the first device to delete the QoS flow.

8. The method according to claim 7, characterized in that, Before sending the second quality of service flow deletion information to the first device, the method further includes: According to the mapping relationship, a third session modification request information is sent to the anchor session function network element. The third session modification request information includes the second quality of service flow identifier. The third session modification request information is used to instruct the first device to request the deletion of the quality of service flow. The first device receives a third session modification command from the anchor session function network element, the third session modification command being used to instruct the first device to delete the quality of service flow.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: Send session deletion information to the local session function network element, the session deletion information being used to instruct the local session function network element to delete the first session; Based on the mapping relationship between the first QoS flow identifier and the second QoS flow identifier, a third QoS flow deletion information is sent to the first device. The third QoS flow deletion information includes the second QoS flow identifier and is used to instruct the first device to delete the QoS flow.

10. The method according to claim 9, characterized in that, Before sending the third quality of service flow deletion information to the first device, the method further includes: According to the mapping relationship, a fourth session modification request information is sent to the anchor session function network element. The fourth session modification request information includes the second quality of service flow identifier. The fourth session modification request information is used to instruct the first device to request the deletion of the quality of service flow. The first device receives a fourth session modification command from the anchor session function network element, the fourth session modification command being used to instruct the first device to delete the quality of service flow.

11. The method according to any one of claims 1 to 10, characterized in that, The method further includes: Receive context acquisition request information from the target service session function network element, wherein the context acquisition request information is used to request the acquisition of the mapping relationship between the first service quality flow identifier and the second service quality flow identifier; The mapping relationship is sent to the target service session function network element; The service session function network element is the source service session function network element that serves the first device.

12. The method according to any one of claims 1 to 11, characterized in that, The method further includes: The first device receives a fifth session modification command from the anchor session function network element. The fifth session modification command includes the second quality of service flow identifier and is used to instruct the first device to delete the quality of service flow. Based on the mapping relationship between the first QoS flow identifier and the second QoS flow identifier, a fourth QoS flow deletion information is sent to the local session function network element. The fourth QoS flow deletion information includes the first QoS flow identifier and is used to indicate the deletion of the QoS flow. A fifth quality of service flow deletion message is sent to the first device. The fifth quality of service flow deletion message includes the second quality of service flow identifier and is used to instruct the first device to delete the quality of service flow.

13. A communication system, characterized in that, This includes service session function network elements and anchor point session function network elements; The service session function network element is configured to: send a session creation request to a local session function network element, the session creation request being used to request the local session function network element to create a first session for the first device, the first session being different from the second session already created for the first device by the anchor session function network element; and receive a session creation response from the local session function network element, the session creation response being used to instruct the first device to create a quality of service flow for the first session, the session creation response including a first quality of service flow identifier allocated by the local session function network element for the quality of service flow. Send a first session modification request to the anchor session function network element. The first session modification request is used to instruct the first device to request the creation of the quality of service flow. The first session modification request includes a third quality of service flow identifier allocated by the service session function network element for the quality of service flow. The third quality of service flow identifier is 0. The 0 is used to request the anchor session function network element to allocate a quality of service flow identifier for the quality of service flow. The anchor session function network element is used to: receive the first session modification request information; The third QFI assigns a second quality of service flow identifier to the quality of service flow, and the second quality of service flow identifier is different from the quality of service flow identifier already assigned to the quality of service flow of the second session by the anchor session function network element. Send a first session modification command to the service session function network element. The first session modification information is used to instruct the first device to create the quality of service flow. The first session modification information includes the second quality of service flow identifier. The service session function network element is further configured to: receive the first session modification command information; send service quality flow creation information to the first device, wherein the service quality flow creation information is used to instruct the first device to create the service quality flow, and the service quality flow creation information includes the second service quality flow identifier.

14. The communication system according to claim 13, characterized in that, The service session function network element is further configured to: store the mapping relationship between the first service quality flow identifier and the second service quality flow identifier; and send the mapping relationship to the service user plane function network element. The communication system also includes: The service user plane function network element is configured to: receive the mapping relationship; and forward the data transmitted by the first device through the quality of service stream to the local user plane function network element according to the mapping relationship.

15. The communication system according to claim 13 or 14, characterized in that, The service session function network element is further configured to: receive context acquisition request information from the target service session function network element, wherein the context acquisition request information is used to request the acquisition of the mapping relationship between the first service quality flow identifier and the second service quality flow identifier; The mapping relationship is sent to the target service session function network element; The service session function network element is the source service session function network element that provides services to the first device.

16. A communication device, characterized in that, Includes a processor, the processor being configured to cause the communication device to perform the method of any one of claims 1 to 12 by executing a computer program or instructions, or by using logic circuitry.

17. A communication device, characterized in that, Includes units for performing the method according to any one of claims 1 to 12.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed on a computer, cause the method of any one of claims 1 to 12 to be performed.

19. A computer program product, characterized in that, It includes instructions that, when executed on a computer, cause the method of any one of claims 1 to 12 to be performed.

Images